Trigger (None | Message | Timer

| Error | Cancel | Link | Compensation | Rule | Multiple) Message : 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 advantages; however the modeling is more convenient with the symbol-number based approach.

See Trigger Specific event symbol numbers.

 

Target (0-1) : Object

 

This BPMN Attribute defines the Activity or Sub Process which may throw the Compensation / Timeout or Error Event that is represented by this Intermediate Event. This activity is specified inside ARIS with a can trigger connection from the activity towards the intermediate event

[Message Trigger only]

Message : Message

 

Same behavior as the Message attribute at the Start Event

(The direction of the ARIS Connection defines if the message is being sent or received.

[Message Trigger only]

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

AT_BPMN_IMPLEMENTATION (3398)

 

[Timer Trigger only]

Timedate (0-1) : Date

AT_BPMN_TIMEDATE (2140)

 

[Timer Trigger only]

TimeCycle (0-1) : String

AT_BPMN_TIMECYCLE (2141)

 

[Error Trigger only]

ErrorCode : String

AT_BPMN_ERROR_CODE

The error code is being used to link an error throwing end event with an intermediate event that catches the error. This connection can also be established with two occurrences of the same ARIS event (The first occurrence would be the triggering end event; the second occurrence represents the catching intermediate event).

If multiple error IDs should be catched by the same intermediate event the error code field of the catching intermediate event SHALL be empty.

[Compensation Trigger only]

Activity : Object

AT_BPMN_COMPENSATION (2146)

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

The connection between an intermediate event that triggers the compensation and the intermediate event that is the starting point of the compensation (attached to the activity boundary) should be created via ARIS occurrence copies.

The activity that needs to be compensated is therefore specified by a can trigger connection from the activity towards the second (attached) intermediated event.

[Rule Trigger only]

RuleName : Rule

The Abstract BPMN Type Rule is defined by a rule name and a rule expression:

AT_BPMN_RULE_ATG (3397)

AT_BPMN_RULE_EXPRESSION (2142)

 

[Link Trigger only]

LinkId : String

AT_BPMN_LINK_NAME (2143)

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

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 reach’s one of the occurrences it is automatically transferred to the other occurrence. (This only works if you place exactly two occurrences of the link event!)

[Link Trigger only]

ProcessRef : Process

AT_BPMN_PROC_REF

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

If you model a link event with two occurrences of the same object definition the process of the second link event can be discovered automatically because the second occurrence has a connection towards its embedding pool and from there on towards the embedding process.

[Multiple Trigger only]

Triggers (2-n) : Trigger

 

Multiple Triggers are modeled as a combination of other triggers. A possible Scenario for an intermediate event would be:

two incoming message connection for two possible trigger messages

an incoming message and a maintained Time date attribute (event is triggered if the message arrives OR at the given timestamp)

a link event and a possible starting message