Idea
Cognizant Technology Solutions
US
Last activity: 28 Jun 2017 16:17 EDT
Error in Approval flow
Hi Team,
I have configured a dependency wait shape and next flow is pzApprovalFlowWrapper with Approval type is single and Route to Work Group Manager (Manager is configured in WG ).
On completion of dependency flow is not moving when user role is user4 but the same is working with sysadmin4 ,But i can't use sysadmin4 for user.
Error log is attached.
Thnaks,
Lalit
***Edited by Moderator: Marissa to add Feedback ID***
Pegasystems Inc.
IN
Hello Lalit,
Thanks for posting your issue in PSC :)
From the error log snippet, I see below error reported:
2017-06-21 21:26:19,371 [ PegaRULES-Batch-3] [ STANDARD] [ ] [ IntTrackFW:01.01.01] ( FlowProblems.Work_.Action) ERROR - Problem flow abort due to system flow FlowProblems being the issue com.pega.pegarules.pub.PRAppRuntimeException: The flow WaitForEvaluation had a problem on step pyContinueAfterWait of: ** The flow pyCascadingGetApproval had a problem on step ASSIGNMENT63 of: No routing information was provided for this assignment.
I find below related posts in our PSC which refers to configuration for the assignment:
- https://pdn.pega.com/community/pega-product-support/question/route-work-object-manager
- https://collaborate.pega.com/discussion/interaction-driver-rule
Does this help?
Regards,
Rincy
Cognizant Technology Solutions
US
Hi Rincy,
Thanks for your Response..
I have already gone through the above link but no luck.
Thanks,
Lalit
Pegasystems Inc.
US
It looks like the issue is coming from the pzGetApproverName activity. When the approval type is Work Group Manager, it will go through step 3 to set the pyApproverName. The java code gets the work group from the OperatorID page. In the case of the Wait shape, it would be the service level agent processing the Wait shape. Do you see the same error when processing the Wait assignment manually as an end user?
Cognizant Technology Solutions
US
Hi Carissa,
Yes error because pyApproverName name not setting ,but its working with Admin role.
looks like to execute below java and get the manager from work group require some privilege which is missing in user role.
Database dbInf = tools.getDatabase();
HashStringMap oKeys = new HashStringMap();
String currentWorkGroup = tools.findPage("OperatorID").getString("pyWorkGroup");
String[] aColumns = {"pyManager"};
oKeys.putString("pxObjClass", "Data-Admin-WorkGroup");
oKeys.putString("pyWorkGroupName", currentWorkGroup);
try{
ClipboardPage tempPage = ((PegaDatabase)dbInf).openSelectedColumns(oKeys,aColumns);
if(tempPage != null)
{
myStepPage.putString("pyApproverName",tempPage.getString("pyManager"));
}
}catch(Exception e){}
Thanks,
Lalit
Pegasystems Inc.
US
Hi Lalit,
I tested the scenario on my system. It works for me when processing the Wait assignment as an end user with the PegaRULES:User4. It fails when processed by the SLA agent though because the OperatorID page would be different. You could add a custom activity after the Wait shape to get the appropriate operator to route to and then use that operator when calling pzApprovalFlowWrapper.
Cognizant Technology Solutions
US
Thanks Carissa ..Yea i am doing the same getting the manager id from some page and using route to specific user.
Can we add this as a bug ?
Thanks,
Lalit
Pegasystems Inc.
US
Hi Lalit,
An enhancement request can be submitted to have the functionality reviewed.
Pegasystems Inc.
US
Thanks Carissa & Lalit! I have gone ahead and submitted this enhancement on your behalf and updated the original post with the Feedback ID. You can now take this to your Account Executive for next steps.
Pegasystems Inc.
IN
This is a known issue when previous assignment (Could be wait shape or normal assignment) is moved by an agent and next assignment is configured as Route to current operator. As the current operator in Agent's case will be System and there is no operator with that name. Hence the issue.
Which Pega version are you using ? You can solve this issue by changing the routing of next assignment.
Let us know if this helps :)
Cognizant Technology Solutions
US
Hello,
No i am not using the current operator .
Its working with admin role means there is no problem in routing .
Thanks,
Lalit