Problem Statement
In this article, we will discuss various process designs with performance and user experience at the back of our minds.
Figure 1: Process Flow with Long Running Tools in Between Activities
In Figure 1, when the user completes Activity 1, it will take 15 seconds long to execute all tools before reaching Activity 2.
Figure 2: User Started a Process Instance
In the eye of the user, the user will be presented with "Please wait..." as shown in Figure 2, and needed to wait for a considerable long time before reaching the next activity assignment, Activity 2.
We will discuss possible solutions to eliminate the need to wait for the users.
Possible Solutions
Solution 1 - Use Synchronous Deadline (No Dependency on Tools)
In this solution, we are adding a parallel route and a new activity (Activity 3).
Upon completing Activity 1, the user will see Activity 2 immediately without the need to wait for all 3 tools to execute as shown in Figure 3 below.
Figure 3: Process Flow with the Use of Synchronous Deadline
The tools will only be executed upon the maturity of a synchronous deadline. This will not interfere with the end users' screen and they do not need to wait for their executions.
Figure 4: Process Flow with the Use of Synchronous Deadline - Deadlines
This solution is viable if Activity 2 does not have a dependency on the outcome of the tools' executions.
Read on how to handle the use case where executions of tools are needed in order to move to the next activity.
Solution 2 - Use Synchronous Deadline (With Dependency on Tools)
Figure 5: Process Flow with the Use of Synchronous Deadline to Cater to Dependency on Tools' Executions