This article refers to legacy products, components or features. Therefore, the content in this article is offered "as is" and will no longer be updated. This content does not infer that the product, component or feature is supported, or that the product, component or feature will continue to function as described herein.


When a number of IPC (Inter Process Communication) child processes are instantiated and then the results are later consolidated in the same parent process, the Preceding rule does not evaluate as expected.
Note: No error or exception is thrown, the outcome is evident of the error.

Error Scenario

The error scenario can be reproduced by following the steps below:
  1. Create a new Parent process
    • The Parent Process creates a "split", where multiple child processes are instantiated
    • The Parent Process later consolidates the child processes

      [Figure 1. Parent Process]
    • The preceding rule is configured as shown in the images for the Default Activity that consolidates the Client Events

      [Figure 2. Preceding Rule]
  2. Create a new Child Process

    [Figure 3. Example Child Process]
  3. Ensure the process splits into a few activities, does not matter which activities, but the activity where the lines join should be a client event to be able to easily see the behavior specified
  4. Go to workspace and start a new instance of the parent process, the child processes will list in the user's worklist as shown in the image below

    [Figure 4. Workspace Listing, displaying the child process that have not consolidated]

Error Resolution

This Hotfix is contained within the latest K2 blackpearl 0807 Update. Install the update package to resolve the error.

The latest K2 blackpearl 0807 Update is available as an independent installation package which can be found here: https://portal.k2.com/downloads/bp/default.aspx.