Assignment to specific user (7.3 version)
Hi,
I have a flow in which user selects, to which user the Facilities child case should be assigned to later. This value is stored in the .EventManager property. (e.g. User chooses Event Manager 2 in the UI, the .EventManager property value is stored as EventManager2.booking which is actual operator ID in the system). I have verified this is working.
Later in the flow, there is assignment shape. Assignment shape is configured to be routed to "Specific User" and User ID is mentioned as .EventManager property which was set above. However, at runtime it is giving error saying that "Unable to open assignee's Data-Admin-Operator-ID record .EventManager" which is telling me that Pega is treating it as literal value instead of reading the value out of property. Any suggestions how to make this work.
I suppose there are other ways to make it work. Its just that since Pega has explicitly provided this option of "Specific User" configuration, shouldn't it work as it is?
Attached is the flow configuration screenshot.
Pegasystems Inc.
IN
Hi Sachin,
This looks like a BUG in 7.3. Kindly raise an SR for further investigation. There might be an existing fix for this.
Synechron
US
I did not raise SR yet, as I came across this issue on LSA VM exercise setup on my laptop. As you said, there might be actually a fix available and it is just that I don't have correct/updated version. But I just wanted to bring it up to attention to see if this really is an issue and if someone is aware of existing fix or is it that for this particular option Pega does not support dynamic assignment?
Pegasystems Inc.
IN
Hello @SachinN6,
Please share the SR# once you've created it. This will help us to connect this thread with the SR.
Thanks,
Pegasystems Inc.
US
Agree. You can accomplish what you want using Custom routing + ToWorkParty.
When you use "Specific user" you are supposed to place cursor in the empty field that appears, click the down arrow, then choose a literal Operator ID.
pyWorkParty is a single property that can record the role and ID for multiple operators who are party to a case.
Why create a scalar property just to store an Operator ID as Text? As a linked property, perhaps.
But if you create a scalar property to store an Operator ID and then use the exact same Operator ID in pyWorkParty, what if the two become out-of-sync in the future? Data Integrity loss.
You would need to implement a Rule-Declare-OnChange or Rule-Declare-Trigger rule to ensure the two properties are kept in sync.
