User task is assigned to invalid user when the email address Local-part is not the same as the Down-Level Logon Name
kbt140626
PRODUCTIssue
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 (DENALLIXc1234).Symptoms
User's down-level logon name is: DENALLIXc1234
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:DENALLIXCodi', which is not a valid K2 FQN. The correct K2 FQN should be 'K2:DENALLIXc1234'.
This does work if the down-level username and email local-part is the same, i.e.
DENALLIXBob
Bob@denallix.com
This behavior is currently as designed. When assigning user task, the value should be in the K2 FQN format 'K2:DENALLIXc1234'.
Resolution
1. Re-design the SmartObject, View/Form, and Workflow to store/assign the task to the K2 FQN format 'K2:DENALLIXc1234'.
2. Or add an additional step/configuration before the user task assignment that would resolve the email address to the correct FQN/K2 FQN (DENALLIXc1234 or K2:DENALLIXc1234) 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.