Trigger Specific event symbol numbers (Updated with the last Service Release)
The above specified mechanism for the event trigger selection via the ARIS attribute AT_BPMN_EV_TYPE (Message, Link, Multiple etc…) has been extended with a new symbol number specific approach. Additionally to the above mentioned general event symbol numbers the following new (trigger specific) event symbols were added to the latest ARIS version:
BPMN event name | ARIS Symbol Number (API-Name) |
Message Start Event | ST_BPMN_MSG_SE |
Message Intermediate Event | ST_BPMN_MSG_IE |
Message End Event | ST_BPMN_MSG_EE |
| |
Link Start Event | ST_BPMN_LINK_SE |
Link Intermediate Event | ST_BPMN_LINK_IE |
Link End Event | ST_BPMN_LINK_EE |
| |
Multiple Start Event | ST_BPMN_MULTIPLE_SE |
Multiple Intermediate Event | ST_BPMN_MULTIPLE_IE |
Multiple End Event | ST_BPMN_MULTIPLE_EE |
| |
Error Intermediate Event | ST_BPMN_ERROR_IE |
Error End Event | ST_BPMN_ERROR_EE |
| |
Cancel Intermediate Event | ST_BPMN_CANCEL_IE |
Cancel End Event | ST_BPMN_CANCEL_EE |
| |
Compensation Intermediate Event | ST_BPMN_COMPENSATION_IE |
Compensation End Event | ST_BPMN_COMPENSATION_EE |
| |
Terminate End Event | ST_BPMN_TERMINATE_EE |
A modeling project should stick to one of the two trigger definition approaches (attribute based or symbol number based).
The symbol number based approach is more convinient for the modeler because he doesn’t have to maintain the trigger type attribute for each placed event. The attribute based approach has the advantage that ARIS ensures the same event type for every occurrence of the same object definition.
The provided BPMN semantic checks can handle both trigger definition approaches.
If the symbol number specific approach is being used the attribute AT_BPMN_EV_TYPE should either be set to the correct event type or should be left unmaintained (because the export logic can use the symbol number to determine the effective event type).
However, if the symbol number specific approach is being used the ARIS Attribute AT_BPMN_EV_TYPE MUST NOT be set to a conflicting event type.
Contact Support
|
Community
|
Feedback