Result (None | Message | Error | Cancel | Compensation

| Link | Terminate | Multiple) None :

String

AT_BPMN_EV_TYPE (2137)

There are two possible ways to describe the trigger of an event – the first one (which defines the trigger effectively at the object definition level) is using the ARIS Attribute AT_BPMN_EV_TYPE.

The ARIS value not maintained has the BPMN Semantic None

The second approach uses separate ARIS symbol (at occurrence level) to distinguish the different event types. Both approaches have their advantages; however the modeling is more convenient with the symbol-number based approach.

See Trigger Specific event symbol numbers

[Message Result only]

Message : Message

Same behavior as the Message attribute at the Start Event

Same behavior as the message attribute at the Start Event

[Message Trigger only]

Implementation (Web Service | Other | Unspecified) Web Service : String

AT_BPMN_IMPLEMENTATION (3398)

 

[Error Result only]

ErrorCode : String

AT_BPMN_ERROR_CODE (2145)

 

[Compensation Result only]

Activity : Object

AT_BPMN_COMPENSATION (2146)

If maintained the Attribute value MUST be the ARIS GUID of the activity which needs to be compensated.

DEPRECATED: The usage of the attribute is not recommended because the same semantic can be archived with the ARIS Occurrence Copy approach described in the next column

This BPMN attribute specifies the activity that needs to be compensated.

Because Compensation Results are always paired with a Compensation Trigger the recommended approach is to use 2 occurrences of the same ARIS Event definition.

The first occurrence is an intermediate or an end event which can be reached via a normal sequence flow (incoming occurs before or activates connection – this event is the trigger that activates a compensation flow.

The second occurrence is an intermediate event which is attached to the boundary of an activity with a can trigger connection.

Because the two occurrence of the event have an internal ARIS connection the connection from the triggering event towards the activity that needs to be compensated is created (without the need to use AT_BPMN_COMPENSATION)

[Link Result only]

LinkId : String

AT_BPMN_LINK_NAME (2143)

The LinkID is being used to create a virtual connection between two separate link events. This connection can be created in ARIS in a more convenient way with two occurrences of the same object definition. Whenever the token reaches one of the occurrences it is automatically transferred to the other occurrence. (a modeler SHALL only place two occurrences of the same link event definition)

[Link Result only]

ProcessRef : Process

AT_BPMN_PROC_REF (2155)

The process has to be specified with the GUID of the pool that contains the process!

DEPRECATED: The usage of the attribute is not recommended because the same semantic can be archived with the ARIS Occurrence Copy approach described in the next column

Same behavior as the ProcessRef Attribute at the Start Event

[Multiple Result only]

Results (2-n) : Result

 

Multiple Results are modeled as a combination of other Results. A possible scenario would be:

two outgoing message connection to represent that two messages are send

a combination of a second occurrence (link event) and an outgoing message to represent a combination of a link result and a message result

…