Posted: 11 Dec 2019 13:18 EST Last activity: 16 Dec 2019 12:06 EST
Cascading approval inconsistency
I have configured a cascading approval step in a flow. It is based on authority matrix and it uses a page list property. The page list has 2 records. However the case is not routed to second approver. It continues as approved after the first approval. This behavior occur on production. I have reproduced the same scenario in the test environment and I validated that the case has been routed to the both approvers. Why does the flow behaves different in another environment ?
There is just "pxMultipleConnectorsOfHighestLikelihood not found" record that might be related to the action. Cause the timestamp and the operator are similar to the history log. And there is another log for the first approver which is very strange. WorkLock.Work_.Action) ERROR - Error in Obj-Open-By-Handle com.pega.pegarules.pub.database.AuthorizationException: You are not authorized to open instance
If he can not open the work object, how can he approve ?
I found a chance to reproduce tha scenario in anorher case on production. And it behaved correctly. The case has been routed to all the required approvers. Also there was not the authorization error for the approver in the log file.
But still I have no idea why the previous cases behaved wrong and pega raised an auth error.