The End activity is always the last activity in a process, and provides an exit point from a process. When you create a new process, the BPM system automatically creates an End activity. There can be only one End activity in a process.
The End activity transforms instance variables into arguments (See Argument Mapping) that can be then passed to another process or to an external application. Upon completion, the End activity can return flow to any of the following:
A Subflow activity that called the process.
When a process was started by another process using a Process Creation activity, the called process' End activity can return instances to the calling process' Termination Wait activity.
An external application.
The following table outlines some of the considerations when using the End Activity within ALBPM Studio.
| WorkSpace |
The End activity is an end point of the process. It will not appear in the WorkSpace. |
| Roles |
The End activity automatically appears when you add a new process. It can be moved around on the process design workspace, but it must reside in an Automatic role lane. |
| Variables |
The End activity can define instance variables to determine the argument mapping. See Argument mapping. The End activity transforms instance variables into outgoing arguments. |
| Pre Conditions |
Instances come into the End activity from the process. |
| Post Conditions |
When an instance completes the End activity, it is completed within the process. If the process was called by a Subflow or Process Creation activity, the instance variables are set to outgoing arguments, as defined in the Argument Mapping, and are passed back to the calling process from the End activity. |
| Transitions |
One or more incoming transitions are required. End activities can only transition to a Grab activity (outgoing transition). Instances can be grabbed from the End activity unless the instance status is aborted or terminated. |
| Tasks |
No tasks are available. |
| Business Process Methods |
To pass arguments between processes, the Argument Mapping function is available. Arguments are passed to the calling process to return information to it Advance scripting is available but because of compatibility with previous version. It is not recommended to add code either in the Begin or End PBLs. In case you need to execute some coding, you can include that in an automatic activity immediately before the End activity. The script is run first and then the argument mapping is set. |