Technical Support
Have technical issues or suggestions? Please contact Visual Paradigm Support Team.
Sales Support
Have questions related to registration, licensing or payment? Feel free to contact Visual Paradigm Sales Team.
Sub-process
In BPMN, there are two kinds of activity - task and sub-process. To represent either an empty BPEL activity or an invoke of BPEL activity, you use a task with proper type set. Sub-process, on the other hand acts as a placeholder of a set of tasks. You can draw a sub-process, expand it and draw the tasks in the sub-process diagram. Note that only sub-process with type Embedded is considered in BPEL generation. The other types will be ignored.
 |
| A sub-process and its sub-process diagram |
When you generate BPEL, the flow modeled in sub-process diagram will be merged to the ordinary flow. The following code fragment shows a BPEL file generated from the above BPDs. The empty activities STask1 and STask2 were modeled in the sub-process diagram, and they follow the empty activty Task in the main flow.
<?xml version="1.0" encoding="UTF-8"?>
<process name="BusinessProcessDiagram1" targetNamespace="http://BusinessProcessDiagram1" xmlns="http://schemas.xmlsoap.org/ws/2003/03/business-process/" xmlns:Pool="http://a" xmlns:tns="http://BusinessProcessDiagram1" xmlns:xsd="http://www.w3.org/2001/XMLSchema">
<partnerLinks>
<partnerLink myRole="provider" name="Pool" partnerLinkType="Pool:PartnerLinkType"/>
</partnerLinks>
<variables>
<variable messageType="Pool:Message" name="Variable"/>
</variables>
<sequence>
<receive createInstance="yes" operation="perform" partnerLink="Pool" portType="Pool:ProviderPortType" variable="Variable"/>
<empty name="Task"/>
<empty name="STask1"/>
<empty name="STask2"/>
<reply operation="perform" partnerLink="Pool" portType="Pool:ProviderPortType" variable="Variable"/>
</sequence>
</process>
<process name="BusinessProcessDiagram1" targetNamespace="http://BusinessProcessDiagram1" xmlns="http://schemas.xmlsoap.org/ws/2003/03/business-process/" xmlns:Pool="http://a" xmlns:tns="http://BusinessProcessDiagram1" xmlns:xsd="http://www.w3.org/2001/XMLSchema">
<partnerLinks>
<partnerLink myRole="provider" name="Pool" partnerLinkType="Pool:PartnerLinkType"/>
</partnerLinks>
<variables>
<variable messageType="Pool:Message" name="Variable"/>
</variables>
<sequence>
<receive createInstance="yes" operation="perform" partnerLink="Pool" portType="Pool:ProviderPortType" variable="Variable"/>
<empty name="Task"/>
<empty name="STask1"/>
<empty name="STask2"/>
<reply operation="perform" partnerLink="Pool" portType="Pool:ProviderPortType" variable="Variable"/>
</sequence>
</process>
Creating an embedded sub-process
- Select Embedded Sub-process in diagram toolbar.
Selecting Embedded Sub-Process from diagram toolbar - Click inside the pool to create an embedded sub-process. If you tend to create a sub-process through the resource-centric interface of the previous flow object, you can change the type by right clicking on the sub-process and selecting Type > Embedded Sub-Process from the pop-up menu.
- Click on the + icon at the bottom of embedded sub-process. You can now model the sub-process in the diagram created.
To expand a sub-process
| 5. Task | Table of Contents | 7. Gateway with WS-BPEL |