Condition CHECK_ACTIVITIES finding activities in other Clients

Document ID : KB000087913
Last Modified Date : 14/04/2018
Show Technical Document Details
Issue:
Error Message :
N/A

With the conditions CHECK_ACTIVITIES, it is possible to check for activities with a specific state.

This check is not client specific and may also find activities in other clients, if they have the same name. This could lead to an invalid results during the condition check.

Investigation

The workflow includes a pre-condition in the DUMMY script object, defined as follows:

IF WAIT_6000 resides = 0 with status ANY_ACTIVE in activity window RUN TASK
ELSE THEN redo evaluation in 1 minute

  1. Import the objects in two separate Clients within the same AE system.
  2. Start the Script WAIT_6000 object in both Clients.
  3. In one of the Clients also execute the Workflow object.
  4. END the script WAIT_6000 object in both Clients.
  5. Observe that the pre-condition within the Workflow is still not met, although there are no further instances of the script object active within the Client.
  6. END the script WAIT_6000 in the other Client as well.
  7. Observe that now the pre-condition is considered to be met and the Workflow ends.
As you can see invalid results may be displayed when the condition is checked due to the activity in another Client. 
Cause:
Cause type:
Defect
Root Cause: With the conditions CHECK_ACTIVITIES, it is possible to check for activities with a specific state. This check is not client specific and may also find activities in other clients, if they have the same name. This could lead to a wrong results.
Resolution:
This field was added on 30/03/2017. This article has not been updated yet. Refer to the "Description" or "Workaround" sections for solution information.

Fix Status: Released

Fix Version(s):
Automation Engine 11.2.1 - Available
Automation Engine 11.1.3 – Available
Automation Engine 10.0.7 - Available
Additional Information:
Workaround :
N/A