Related Action

Hi bestlinl, There are 2 ways you can go with:
1. Disabling the Related Action - Build a Process Report with the context of the Target Process Model, in such a way that it captures every process instance detail. Build an Expression Rule with a!queryAnalytics() function through which you will be able to capture the process instance details as a data subset. Build another expression rule for the visibility of the Related Action which returns true if there is no active instance otherwise false. This will disable the related action if there is an active instance for that process model. Configure this expression rule at the Visibility for the related action.
2. Handling in Process Model - Keep the Related Action always visible. Build a Process Report with the context of the Target Process Model, in such a way that it captures every process instance detail. Build an Expression Rule with a!queryAnalytics() function through which you will be able to capture the process instance details as a data subset. Inside the process model add an XOR gateway at the very beginning in order to verify whether there is any active instance for the process model at that moment (call the expression rule to fetch the process instance details). If there is any, end up the flow otherwise let the execution follow the normal flow.

If there are more number of users for whom the related action is available, you might need to add some more factor/factors (like the user/group context) to find more accurate details about the process instances.
Hope this helps!!

Hi bestlinl, There are 2 ways you can go with:
1. Disabling the Related Action - Build a Process Report with the context of the Target Process Model, in such a way that it captures every process instance detail. Build an Expression Rule with a!queryAnalytics() function through which you will be able to capture the process instance details as a data subset. Build another expression rule for the visibility of the Related Action which returns true if there is no active instance otherwise false. This will disable the related action if there is an active instance for that process model. Configure this expression rule at the Visibility for the related action.
2. Handling in Process Model - Keep the Related Action always visible. Build a Process Report with the context of the Target Process Model, in such a way that it captures every process instance detail. Build an Expression Rule with a!queryAnalytics() function through which you will be able to capture the process instance details as a data subset. Inside the process model add an XOR gateway at the very beginning in order to verify whether there is any active instance for the process model at that moment (call the expression rule to fetch the process instance details). If there is any, end up the flow otherwise let the execution follow the normal flow.

If there are more number of users for whom the related action is available, you might need to add some more factor/factors (like the user/group context) to find more accurate details about the process instances.
Hope this helps!!