This article was created in response to a support issue logged with K2. The content may include typographical errors and may be revised at any time without notice. This article is not considered official documentation for K2 software and is provided "as is" with no warranties.
This article has been archived, and/or refers to legacy products, components or features. The content in this article is offered "as is" and will no longer be updated. Archived content is provided for reference purposes only. 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.
User task is assigned to invalid Active Directory user when the email address Local-part (codi
@denallix.com) is not the same as the Down-Level Logon Name (DENALLIX\c1234
User's down-level logon name is: DENALLIX\c1234
Email address is: Codi@denallix.com
When using the email address (Codi@denallix.com) for user task assignment, it was assigning it to the string 'K2:DENALLIX\Codi', which is not a valid K2 FQN. The correct K2 FQN should be 'K2:DENALLIX\c1234'.
This does work if the down-level username and email local-part is the same, i.e.
This behavior is currently as designed. When assigning user task, the value should be in the K2 FQN format 'K2:DENALLIX\c1234'.
1. Re-design the SmartObject, View/Form, and Workflow to store/assign the task to the K2 FQN format 'K2:DENALLIX\c1234'.
2. Or add an additional step/configuration before the user task assignment that would resolve the email address to the correct FQN/K2 FQN (DENALLIX\c1234 or K2:DENALLIX\c1234) format; via perhaps an AD Service2 > AD User SmartObject or URM Service > UMUser SmartObject.
3. If integrating with SharePoint and making use a SharePoint 'Person or Group' column, the 'Name' field should return the correct user FQN/K2 FQN base on the Active Directory down-level logon name.