A.3. Defining an EKM Process Template XML File

An EKM process is defined in terms of the following constructs:

Variables are used for storing the state of a process. Variables can be assigned default values in the process definition. When a task gets completed for a process that is being run in EKM, users may be prompted to enter values of output variables. Validation can be performed on variable values to ensure that only valid values are entered. The value of a variable can also be used to determine when a transition is triggered, and when an iteration gets completed.

Nodes are used to model a single step in an EKM process. The following node types are provided for modeling various conditions:

Transitions are used to specify the path of the process. A transition is a connection between a starting node (source) and an ending node (destination). A transition can have a trigger expression associated with it. The trigger expression determines whether the transition will be triggered (or traversed) in a process. If no trigger expression is specified then the transition is always triggered.

The following rules apply to transitions:

If a node has more than one outgoing transition, then depending on the trigger expression, any number of the transitions may be triggered. If more than one transition is triggered, then the tasks will be processed concurrently. If a node has more than one incoming transition, then the task corresponding to that node will wait until all of the incoming transitions have been traversed. For example, suppose a process has nodes A, B, C and D with transitions from A to B, A to C, B to D and C to D. The start node is A with two outgoing transitions, and D is the end node with two incoming transitions. In this case, the task corresponding to node D will be activated only once the tasks corresponding to both nodes B and D have been completed.

Blocks are used primarily to model iterations and can be used to avoid cycles in the process. Conceptually, a block represents the sequence of steps that are executed as part of an iteration. A block can have nodes and transitions. Variables are not defined at the block level. Variables that are defined at the process level can be accessed by any node or transition in any block.

The following rules apply to blocks:

Expressions are used to evaluate conditions such as whether a variable supplied in a task is valid, whether an iteration should continue, or whether a transition should be traversed. Like macros, expressions are defined in a supported scripting language in the script element.

Macros are used in process definitions to automate certain tasks. For example, macros can be used to define complex logic in expressions, tasks that will be executed in an auto node, and custom dialog boxes for a task. Macros are defined using a supported scripting language in the script element, and can be referenced in any expression in a process definition.

Now, let's look at the each of these constructs in more detail in the following sections.


Release 18.2 - © ANSYS, Inc. All rights reserved.