|
|
|
A process definition node represents one logical step in your business process. Nodes are connected by connection or transition lines that indicate the order the nodes are to be processed.
There are several types of nodes available for use. Each node provides different capabilities. In addition, with most node types, there is pre-processing, post-processing, and exception handling.
An Activity node indicates work to be done by a defined role.
A Branch node indicates the workflow process takes one path from a set of alternate paths; the path taken is the first transition where the guard condition evaluates to TRUE.
A Comment is a text annotation.
An Evaluation node is used to assign values to process attributes.
A Fork node indicates where the workflow takes parallel paths.
A Join node indicates where parallel workflow processes join; all of the paths must be completed before the transition out of a Join occurs.
A Merge node indicates where alternate workflow process paths merge into a single path. If any one of the paths completes, the transition out of a merge where alternate workflow process paths merge into a single path, occurs.
An Object node specifies an operation on an Object.
Some actors have Send Events defined. For example, the Global User List actor has one Send Event defined: Send E-mail. A Send Event node allows you to use the Send Event for an actor assigned to a role in the process definition.
Note: The email address used is the one stored in the CA EEM user record, not the one in the CA Service Catalog user record.
A Stop node in a main process in the process definition indicates that the process definition ends. A Stop node in a sub-activity indicates the sub-activity processing ends and returns back to next step in the calling process.
A Sub Activity node contains other process nodes. A Sub Activity can use iteration, repeatedly executing the contained process nodes until some end condition is reached.
A Throw Exception node can throw an exception (either an Actor Fault or a user-defined exception) which can be caught by another node executing in parallel.
A Timer node pauses the execution of that path of the process.
A Wait Event node can receive a message from a Simple Event sent by another process definition.
| Copyright © 2013 CA. All rights reserved. |
|