{"componentChunkName":"component---src-templates-simple-markdown-js","path":"/cpm/developer/services/graphic/elements_subprocesses/","matchPath":"","result":{"data":{"markdownRemark":{"html":"

BPMN sub-processes and call activities

\n

Sub-processes and call activities are non-atomic pieces of work within a business process. They are - besides the tasks - a graphical representation of Activities.

\n

Sub-processes can occure with different types.

\n

The sub-provess types, that are defined by BPMN are:

\n\n

A sub-process is a non-atomic (compound) Activity that is included within a business process or a choreography. It is compound in that it can be broken down into a finer level of detail through a set of sub-Activities.

\n

A transaction is a sub-process that is supported by a special protocol that insures that all parties involved have complete agreement that the activity should be completed or cancelled. The attributes of the activity will determine if the activity is a transaction.

\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
No.JSON request / definitionJSON request / shapeGraphic displayBPMN definitionBPMN display
1\"properties\": {
  \"type\": \"subProcess\",
  \"kind\": \"OBJ\"
}

or:
\"properties\": {
  \"type\": \"subProcess\",
  \"kind\": \"OBJ\",
  \"processMarker\": \"none\"
}		\"properties\": {
  \"type\": \"subProcess\"
}
\n \n \n <subProcess> ...
</subProcess>
\n \n \n
2\"properties\": {
  \"type\": \"subProcess\",
  \"kind\": \"OBJ\",
  \"processMarker\": \"parallelMultiple\"
}		\"properties\": {
  \"type\": \"subProcess\"
}
\n \n \n
3\"properties\": {
  \"type\": \"subProcess\",
  \"kind\": \"OBJ\",
  \"processMarker\": \"loop\"
}		\"properties\": {
  \"type\": \"subProcess\"
}
\n \n \n <subProcess> ...
<standardLoop-
Characteristics/> ... </subProcess>
\n \n \n
4\"properties\": {
  \"type\": \"subProcess\",
  \"kind\": \"OBJ\",
  \"processMarker\": \"compensation\"
}		\"properties\": {
  \"type\": \"subProcess\"
}
\n \n \n <adHocSubProcess> ... </adHocSubProcess>
\n \n \n
6\"properties\": {
  \"type\": \"transaction\",
  \"kind\": \"OBJ\"
}

or:
\"properties\": {
  \"type\": \"transaction\",
  \"kind\": \"OBJ\",
  \"processMarker\": \"none\"
}		\"properties\": {
  \"type\": \"transaction\"
}
\n \n \n
\n

BPMN call activity

\n

A call activity identifies a point in the business process where a global (re-used) sub-process or a global (re-used) task is used. The call activity acts as a wrapper for the invocation of a global sub-process or a global task within the business process.

\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
No.JSON request / definitionJSON request / shapeGraphic displayBPMN definitionBPMN display
7\"properties\": {
  \"type\": \"callActivity\",
  \"kind\": \"OBJ\"
}

or:
\"properties\": {
  \"type\": \"callActivity\",
  \"kind\": \"OBJ\",
  \"processMarker\": \"none\"
}		\"properties\": {
  \"type\": \"callActivity\"
}
\n