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 user attempts to redirect a work list item to a user whose identity belongs to a domain with a name that is very similar to the current domain, the worklist item is not redirected but remains on the current user’s worklist.

Error Scenario

Note: The circumstances described in this article are one scenario under which this issue may, or is known to occur. The description is intended to be specific to the scenario described and does not take into account all possible scenarios or circumstances.
When a user from e.g. Domain.COM attempts to redirect a worklist item to a user to e.g. Domain.CO.ZA, a search for the identity of the destination user is performed. The distinguished name of the user is retrieved from Active Directory. This is then used to extract the destination user’s identity For example, using the two domains mention Domain.co.za, and Domain.com the LDAP path for the two domains would be the following, respectively:
  • LDAP://DC=Domain, DC=CO,DC=ZA
  • LDAP://DC= Domain, DC=COM

When a search for the user’s identity was made, only the first part of the FQDN (Fully-Qualified Domain Name) i.e. Domain was used to ensure the Distinguished Name of the user matched up with the FQDN of the domain.

To prevent this from occurring, the relevant part of the user’s distinguished name is extracted and compared to the FQDN of the correct domain to ensure the correct NetBIOSName is returned.

Steps to Reproduce

Step 1

  1. Create a process with a client event with a worklist item and set the destination to a user from the first domain i.e. DOMAIN\Administrator

  2. In K2 Workspace, redirect the worklist item to a user in the second domain i.e. DC2\Anelle

    Note: The user from DC2 has the incorrect domain of DOMAIN instead of DC2

  3. Apply the hotfix

Step 2

  1. Redirect a worklist item, then view the results below:

    Note: The user from DC2 now has the correct domain

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: http://portal.k2.com/downloads/bp/default.aspx