Collision Checks for a Process

Use

You use this function to determine whether your process is part of a collision check. During the collision check, the system checks whether the process is allowed to start after a different process was started for the same object, for example, the same employee.

Features

You can determine the running processes that a process may not collide with.
You can determine the completed processes that a process may not collide with.
You can determine whether the system displays an information, warning, or error message when there is a collision. The system reacts as follows:
- Information
  
  A message appears drawing the user’s attention to the collision. The process can still be run.
- Warning
  
  A message appears warning the user that he or she has called a process that is not permitted. The process can still be run.
- Error
  
  An error message appears. The process cannot be run.
You can mark a process as relevant for the collision check. Meaning that you assign a collision group to the process. This allows you to check whether other processes collide with the process.

Activities

Determine Collision Checks for a Process

In the object hierarchy area, choose Start of the navigation path <Process Name> Next navigation step <Validity Period> Process Start Collision Definition End of the navigation path , and make the following settings:

Specify the collision group that contains the processes with which your process may not collide.
Determine how the system reacts when there is a collision with the processes from the collision group.
To also include completed processes in the collision check, set the Include Completed Processes indicator.

Define Process As Relevant for the Collision Check

In the object hierarchy area, choose Start of the navigation path <Process Name> Next navigation step <Validity Period> Process Start Assignment to Collision Groups End of the navigation path , and make the following settings:

Assign the desired collision group to your process.
To create a new collision group, double-click the Collision Group field to go to the view for creating process groups.

Example

You want to stop more than one process for changing the organizational assignment of an employee being run at the same time.

Create the collision group ORG. You assign all processes that change the organizational assignment of an employee to the group ORG. This marks these processes as relevant for the collision check.

Then you assign this group as a collision group to each individual process from the group ORG. You determine that the system issues an error message if there is a collision with running processes of the group.

If a user now wants to start a process from the ORG group, the system checks whether a different process from the group is already running for the same employee. If this is the case, the system displays an error message. The user cannot run the process until the other process with which it collides is completed.