webMethods and Intelligent Business Operations 10.2 | Designing and Implementing Business Process Models | ARIS Method manual | Business process modeling | Elements of the business process diagram | Modeling guidelines for activities
 
Modeling guidelines for activities
Process
*If the Ad hoc attribute is = True, the Completion condition attribute must be specified.
*If an ad hoc process is refined, no sequence flows must be modeled within the assigned model.
Subprocess
*If the value Independent is set for the Subprocess type attribute, the Process reference attribute must also be specified.
*If the Transaction attribute is enabled for a subprocess, the Transaction ID attribute must also be available.
*If the Loop type attribute is specified, the Loop condition attribute is also required.
*If models are to be transferred to BPEL4WS, a check is recommended to determine whether the Loop type attribute is set to Maximum for processes with the value Standard.
*If the value Standard is specified for the Loop type attribute, the Test before attribute is also required. The Test before attribute should be disabled by default.
*If the value Multi-instance is specified for the Loop type attribute, the Parallel instance generation attribute is also required. The Parallel instance generation attribute should be disabled by default.
*If the Loop type attribute of a subprocess has the value Multi-instance and, at the same time, the Parallel instance generation attribute is enabled, the Loop flow condition attribute must be specified as well.
*If the value Complex is set for the Loop flow condition attribute in a process, an expression that determines when and how many process markers are passed on after the subprocess is complete must be specified for the Complex attribute.
Task
*If the value Receive is specified for the Task type attribute, the function should not have any outgoing message flow connections.
*If the value Send is specified for the Task type attribute, the function should not have any incoming message flow connections.
*If the Task type attribute is not specified or the values Script or Manual are set, the function should not have any incoming or outgoing message flow connections.
*For functions whose Task type attribute is set to Abstract, the Abstract type attribute must also be specified. In addition, these functions may be used only in pools of the Abstract type or in Collaborations.

Copyright © 2018 | Software AG, Darmstadt, Germany and/or Software AG USA, Inc., Reston, VA, USA, and/or its subsidiaries and/or its affiliates and/or their licensors.
Innovation Release