Contact Support
|
Community
|
Feedback Attributes | ARIS Attribute Name (en) API_NAME (Attr. Number) | Other Semantic equivalent in ARIS Description |
Trigger (None | Message | Timer | Rule | Link | Multiple) None : String | Trigger/Result 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. |
[Message Trigger only] Message : Message | Message AT_BPMN_MESSAGE (2138) DEPRECATED: The usage of this attribute is not recommended because it doesn’t allow you to reference a complete ARIS Message Element. You should use the mechanism described in the next column instead. | Message events must have an incoming ARIS connection receives or an outgoing ARIS connection sends. Those connections may lead towards an ARIS Message object (ST_BPMN_MESSAGE). The message of a Message Trigger is therefore defined by the message object which is placed at the other side of the sends or receives connection. If the message is not specified with the above mechanism an empty (no properties defined) message will be assumed. The Name of this empty unspecified message is defined by the Attribute Connection role (AT_CXN_ROLE) which can be maintained directly at the ARIS Message flow connection |
[Message Trigger only] Implementation (Web Service | Other | Unspecified) Web Service : String | Implementation AT_BPMN_IMPLEMENTATION (3398) | |
[Timer Trigger only] TimeDate (0-1) : Date | Time date AT_BPMN_TIMEDATE (2140) | |
[Timer Trigger only] TimeCycle (0-1) : String | Time cycle AT_BPMN_TIMECYCLE (2141) | |
[Rule Trigger only] RuleName : Rule | The Abstract BPMN Type Rule is defined by a rule name and a rule expression: Rule name: AT_BPMN_RULE_ATG (3397) Rule expression: AT_BPMN_RULE_EXPRESSION (2142) | |
[Link Trigger only] LinkId : String | Link ID 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 place exactly two occurrences of the same link event definition) |
[Link Trigger only] ProcessRef : Process | Process reference 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 | 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 belongs to connection towards its embedding pool and from there on towards the embedding process. |
[Multiple Trigger only] Triggers (2-n) : Trigger | Multiple Triggers are modelled as a combination of other triggers. A possible Scenario would be: two incoming message connection for two possible start messages an incoming message and a maintained Time date attribute (process is started if the message arrives or at the given timestamp) a link event and a possible starting message any combination of the above |