Activity Mappings for BPMN Models
Learn more about the activity mappings and supported attribute mappings for BPMN models.
Activity Mappings
The following mappings are done for standard BPMN models:
|
BPMN Type |
SAP Build Process Automation Type |
|---|---|
|
sendTask |
Placeholder (Generic) |
|
scriptTask |
Script Task |
|
userTask |
Form (Upto 5) or Placeholder (Form) |
|
serviceTask |
Placeholder (Action) |
|
businessRuleTask |
Placeholder (Decision) |
|
subProcesss |
Placeholder (Subprocess) |
|
BPMN Type |
SAP Build Process Automation Type |
|---|---|
|
sendTask (having "e:type" as "email") |
|
-
laneSet
-
association
-
textAnnotation
-
dataObject
-
dataObjectReference
-
ioSpecififcation
-
documentation
-
group
Any other type not mentioned above is transformed to a placeholder of Generic type in SAP Build Process Automation.
Maximum Number of Allowed Outgoing Sequence Flows
|
Targeted SAP Build Process Automation Type |
Maximum Number of Allowed Outgoing Sequence Flows |
|---|---|
|
|
1 |
|
Script Task |
1 |
|
Placeholder |
25 |
Key Points:
-
For all the nodes (except End event) with no outgoing sequence flow but at least one incoming sequence flow, create an End event and link to it.

-
Once the import is completed:
-
You might need to fix the formatting of the email body.
-
All scripts are in invalid state. Open the process editor for each script, fix any errors, then validate and apply the changes.
-
Supported Attribute Mappings
The following attributes for each type in a standard BPMN model are mapped to the activities in SAP Build Process Automation. Any other attributes are ignored.
|
BPMN Type |
Supported Attributes |
|---|---|
|
userTask |
name documentation |
|
subProcesss |
name documentation |
|
serviceTask |
name documentation |
|
sendTask |
name documentation |
|
scriptTask |
name documentation |
|
businessRuleTask |
name documentation |
|
<any other type> |
name documentation |
|
BPMN Type |
Supported Attributes |
|---|---|
|
sendTask |
e:type extensionElements.e:subject extensionElements.e:bodyText extensionElements.toEmailAddres.value |
|
userTask |
extensionElements.e:dueDateConfiguration extensionElements.e:taskName extensionElements.e:form |
|
scriptTask |
extensionElements.e:script |
User Task Mappings
When you import a BPMN model, a User Task is transformed into a Form activity in SAP Build Process Automation. An associated Form artifact is also created in the project.
Outcome Mappings
-
The number of buttons created in the SAP Build Process Automation form depends on the number of outgoing sequence flows from the user task. For models designed in SAP Signavio, if the user task is followed by a manual exclusive gateway where the user task has only one outgoing sequence flow and the manual exclusive gateway has only incoming sequence flow, the number of outgoing sequence flows from that manual exclusive gateway are considered.
-
A maximum of 5 buttons can be created in a SAP Build Process Automation form. After importing to SAP Build Process Automation, if there's a mismatch between the number of buttons in the form and the number of outgoing sequence flows from the Form activity, you need to fix the model in the process editor.
-
For models designed in SAP Signavio, if button names are available, the same names are used for naming the buttons in SAP Build Process Automation forms. In all other cases, default button names are used according to SAP Build Process Automation.
-
If the button name is Submit, the style is Positive. In all other cases, the style is Neutral.
Field Mappings
For models designed in SAP Signavio, fields are created in Form. The following table provides the mapping details for different types SAP Signavio fields:
|
SAP Signavio Form Element |
SAP Build Process Automation Form Element |
Transformation Notes |
|---|---|---|
|
Text |
Text |
|
|
Text (if Multi-line is checked) |
Text Area |
|
|
Link |
Text with a regex to validate links |
|
|
Email Address |
Text with a regex to validate email address |
|
|
Number |
Number |
|
|
Duration |
Number |
The field name is appended with (in seconds). |
|
Choice |
Dropdown |
|
|
Yes/No Checkbox |
Checkbox |
|
|
Date/Time |
Date |
|
|
File |
Not transformed |
|
|
User |
Not transformed |
|
|
Money |
Not transformed |
|
|
Form Group |
Not transformed |
Sequence Flow Mappings
The following attributes for a sequence flow in a standard BPMN model are mapped to the activities in SAP Build Process Automation. Any other attributes are ignored.
|
BPMN Type |
Supported Attributes |
|---|---|
|
sequenceFlow |
name sourceRef targetRef |
|
BPMN Type |
Supported Attributes |
|---|---|
|
sequenceFlow |
condition |