This content has been marked as final. Show 5 replies
I remember a bug with the user step when using xPath to assign the user dynamic ally and using Oracle for the DB.
Is this similar to your environment?
Amazing, this is EXACTLY the case with our environment. I think we'd be glad to hear anything you can still remember regarding that bug ;-)
Thanks a million,
Support created a patch and I beleive it was rolled out as part of service pack 1 (SP1).
Your best bet is to contact support to get the appropriate patch to fix the issue.
The temporary work around is to have (each) user to login to workspace client at least once for now.
Thank you all for your quick responses!
After playing around for a while, I noticed that the issue really only occurs with one specific user account. When I directly assigned the task to this account everything worked just fine. After that, the xPath option worked as well. It really looks like if something is being synchronized into the LC database when a user account has it's first contact with a workflow. If that step could be completed the issue never occurs again - which sounds pretty much in line with what Yog said.
The only difference with the "erroneous" user account seems to be that the family name contains a whitespace - I have no idea if this is relevant.
I'm not able to apply the service pack immediately for some reason, but we'll soon be able to see if that fixes the issue.