When you publish an eSpace containing modified process flows, all of the executing process instances that were based on the former process flows are automatically upgraded by the OutSystems Platform. This topic lists some examples of the impact of removed activities on executing process instances.

Process Instance is Executing the Removed Activity

In this case the process instance is executing the deleted activity: the execution is suspended.

The process instance has to be analyzed in Service Center to decide whether it can continue or should be stopped.

In this case, you avoid having a process instance suspended if you change the process in the following way:

  1. Use the Decision tool to branch the flow in two: Deprecated and New;
  2. Put the activities to be deleted in the Deprecated branch;
  3. Open the flow of the Decision element and design it to always return New, i.e., no more processes will follow the Deprecated branch;
  4. Connect the New branch to the first activity that is not to be deleted.

This way, processes are not suspended because activities continue to exist in the process flow. All new processes will stop executing the deprecated branch. When there are not more active instances of activities to be deleted, those activities can effectively be deleted without suspending any process.

To check for active instances of activities, use one of the following (by order of importance):

Process Instance is Executing Before the Deleted Activity

In this case the execution of the process instance has not passed the deleted activity and executes the new flow without it.

Process Instance is Executing After the Deleted Activity

In this case the execution of the process instance has already passed the deleted activity and continues executing.

See Also

Overview of Upgrading Processes | Overview of Designing Processes