Difference between revisions of "Eclipse plugin: Usage"

From OpenKM Documentation
Jump to: navigation, search
Line 2: Line 2:
  
  
<center>[[File:Eclipse.plugin.new.png|459px]]</center>
+
[[File:Eclipse.plugin.new.png|459px|center]]
  
  
Line 10: Line 10:
  
  
<center>[[File:Eclipse.plugin.main.png|681px]]</center>
+
[[File:Eclipse.plugin.main.png|681px|center]]
  
  
Line 16: Line 16:
  
  
<center>[[File:Eclipse.plugin.deployment.png|588px]]</center>
+
[[File:Eclipse.plugin.deployment.png|588px|center]]
  
  
Line 22: Line 22:
  
  
<center>[[File:Eclipse.plugin.design.png|589px]]</center>
+
[[File:Eclipse.plugin.design.png|589px|center]]
  
  
Line 28: Line 28:
  
  
<center>[[File:Eclipse.plugin.source.png|588px]]</center>
+
[[File:Eclipse.plugin.source.png|588px|center]]
 +
 
  
 
[[Category: Workflow Guide]]
 
[[Category: Workflow Guide]]

Revision as of 22:21, 27 January 2010

To create a new process definition, go to File → New → Other and select "Process Definition". Will appear another form where you need to specify the source folder and the process name. Lets call it simply "hello".



Once the wizard has finished, you can see an Eclipse environment with a central panel divided in four tabs:

  • Diagram: This is the main work zone. Here you can construct your process definitions on a visual way.



  • Deployment: Here you can deploy the created process definition directly to the server or save it to deploy manually. The file extension should be ".par".



  • Design: Is the source code of the process definition. It is an hierarchical representation of the XML which describe the nodes and transitions. See jPDL xml schema chapter in jBPM jPDL User Guide for more info.



  • Source: Is the source code of the process definition. It is an XML which describe the nodes and transitions. See jPDL xml schema chapter in jBPM jPDL User Guide for more info.