Question
Cognizant
US
Last activity: 10 Jul 2017 3:19 EDT
Unable to open an instance using the given inputs: pxObjClass = "Data-Admin-Operator-ID", pyUserIdentifier = "System" issue for SLA execution
HI ,
I have a requirement to keep an assignment in the Worklist for certian time ( based on a DateTime Filed) and once the time pass the Assignment should move to the next Step .
Here is what I am doing .
Assignent "WaitingForInterview" is where Asignment should wait till "FinalInterviewDatetime" is reached(So, I am not finishing the assignment on this UI , and on click on save and exit on the screen ( Custom button) I am closing the screen using Cancel in Action )
Once "FinalInterviewDatetime" is reached, SLA "MoveToObserversation" should be triggered ( So, My SLA is crweated with GOAL as Property and Property name as "FinalInterviewDatetime" and I am using "Advance Flow" on the Action section of the SLA to move the Assignment from "WaitingForINterview" Assignment.
My Next Assignment is a screen flow "InterviewObservation" , where I have routed it a user worklist ( Ex:- Admin@CTS) .
The expected out is :- post "FinalInterviewDatetime" the User refered in the Screenflow Router configuration(Ex:- Admin@CTS)
Actual output :- SLA runs but throws error as seen in the SMA as
Unable to open an instance using the given inputs: pxObjClass = "Data-Admin-Operator-ID", pyUserIdentifier = "System"
Could anyone help on this .
I have attached a screenshot of my details as discussed above for reference .
Thanks
BUPA
AU
Hi,
Is this happening for child case which is created via agent or dependency network? If so then by default PRPC provides 'System' as a value of pxcreateoperator of the case. But PRPC doesn't have any Operator ID data instance with name system. This is expected behavior. In this scenario, Pega suggested 2 solutions.
1. Create a dummy operator 'System' in your application. (see "https://pdn.pega.com/support-articles/pxcheckflowdependencies-does-not-work-different-accessgroups)
2. Check your application code for next assignment getting routed to Current Operator in the flow path (parent + child flow). Change the code to assign it to a named user. (see https://community.pega.com/support/support-articles/not-able-run-custom-agents)
Hope it will solve your problem.
Cognizant
US
Hi Swarnendu ,
Thank you for the response . My scenario , the child case is getting created by operator and then they click get next to fetch the child case and work on them till this scenario comes when it stays in work list for certain time period . Coming to XYZ data transform - I did not find any such is Data-party (7.1.9 version ) class . Also my next assignment is not to current operator it's to a named work list as you could refer to the attachment I have provided .any further advice in debug will definite help me . Thanks
BUPA
AU
Hi,
Can you pls check both the cases and their clipboard to point where System is being stored as an operator information. As Pega suggested, you can try creating a dummy system operator and check if it solves your problem.