Aborting and Starting Processes

The Abort and Start functionality aborts an existing process instance and starts another process. The data associated with aborted process is passed by copy to the newly started process. The newly started process is not coupled at all with the originating (aborted) process regarding its life-cycle. However, the newly created process contains a link to the originating one and vice-versa. Target process definitions can be from other model versions.

Common Usage Pattern

Consider a scenario of an organization that has implemented Stardust Portal workflows to manage several of its mission critical business processes, most of which are document-centric. After using the system for several months, the company notices that approximately 4% of the process instances are started in the incorrect process definition, mostly due to user error. When this occurs, an operator downloads the documents referenced to the process instance, aborts it, starts a process instance in the correct process definition, and manually uploads the documents to the newly started process instance. This is quite time-consuming, and there is no link to show any relationship between the two process instances.

With the abort and start option these steps are performed in one functionality.

Usage Pattern coupled with Relocation

Assuming a company has a business process A, and active transactional jobs, process instances, exist with that process:

For details on relocation, refer to chapter Relocation of Activities.

Example Usage

For detail instructions, please refer to the tutorial Aborting and Starting Processes of the Developers Handbook.

Aborting and Starting Procedure

Aborting and starting a process is performed in the following sequence:

  1. A new process instance is started in the selected process definition.
  2. Data from the source (in scope) process instance is copied to the newly started process instance.
  3. The in-scope process instance is aborted.
  4. A link is created from the source process instance to the target process instance.
  5. A link is created from the target process instance to the source process instance.

Linked Processes

The newly started process is linked to the originating one. The link is an additional property of a process instance but does not influence the process hierarchy. API is provided to retrieve the linking information from an existing process instance. Refer to chapter Workflow Processing to Abort and Start Subprocess in the Programming Guide for details.

The links are established from the root process instance of the source process instance to the newly created process instance. They are established between root processes, even if the source and target process instances are not root process instances.

The links created for each process instance will have the following Link Types depending on if they are the source process instance or target process instance:

Aborting and Starting Processes in the Portal

The aborting action in the Stardust portal provides the option to abort and start a process. The process to be started can be selected along with a linking comment. For details refer to chapter Aborting a Process and Starting a new Instance of the Stardust Portal in the End User Handbook.

Linked processes can be viewed in the Process Details view of the process instance. Refer to chapter Linked Processes of the Stardust Portal in the End User Handbook for details.