How to Disable Processes?

Process Inactivation When Using Version Management

If the process to be inactive is associated in the models of other processes, it cannot be passive, the relations must be removed first. In addition, if there is a sub-process of the process to be inactive, it is necessary to delete the sub-processes first or to clean / change the parent process information of these sub-processes. Information about these situations that prevent inactivation can be viewed when performing the operation from the application interface.

In the process of deactivation, the approval flow is monitored, so the approval matrix of the process must be full. The process goes to approvers of revocation. If approved, the process is inactive and is included in the list of inactive processes.

If the use authorization parameter is active in the processes, only the user authorized in the process can perform the process of inactivation

When Version Management Is Not Used

The approval flow that is in effect when using version management will not apply in this case. The process can be directly deactivated. If the use authorization parameter is active in the processes, only the user authorized in the process can perform the process of inactivation. Processes that have been successfully deactivated are included in the Passive Processes list.