SLA not working properly
Hi, I have an SLA. The assignment to which SLA has been added have two flow action. One is visible to the user and user can perform action. Another flow action is made invisible using when condition in security option. When the assignment reaches GOAL we need to advance flow passin g the invisible flow action as a parameter. Now I have two problems.
1) I am setting "Set to the value of Property" in the Calculate Service Level field and giving a DateTime property of pyWorkPage in GOAL. Then I am adding the SLA in an assignment. But whenever any work item enter that assignment it is throwing the below error.
cannot be null/empty. page: pyWorkPage. Details: Invalid value for aReference passed to com.pega.pegarules.data.internal.clipboard.ClipboardPageImpl.getString(String)
2) I changed the Calculate Service Level field to "Interval from when the assignment is ready" and gave x min GOAL. In action I selected Advance Flow and gave the flow action name which was invisible to user. This time there is no error when the work iteem enters the assignment. But the "advance flow" saction was not working and the item remains in the assignment. I am using optim istic locking and whever I am refreshing the assignment its giving the below error.
com.pega.pegarules.pub.PRAppRuntimeException: Caused by Unable to authorize flow action execution: <pzInsKey of the flow action>
Require some help to resolve this.
Hi, I have an SLA. The assignment to which SLA has been added have two flow action. One is visible to the user and user can perform action. Another flow action is made invisible using when condition in security option. When the assignment reaches GOAL we need to advance flow passin g the invisible flow action as a parameter. Now I have two problems.
1) I am setting "Set to the value of Property" in the Calculate Service Level field and giving a DateTime property of pyWorkPage in GOAL. Then I am adding the SLA in an assignment. But whenever any work item enter that assignment it is throwing the below error.
cannot be null/empty. page: pyWorkPage. Details: Invalid value for aReference passed to com.pega.pegarules.data.internal.clipboard.ClipboardPageImpl.getString(String)
2) I changed the Calculate Service Level field to "Interval from when the assignment is ready" and gave x min GOAL. In action I selected Advance Flow and gave the flow action name which was invisible to user. This time there is no error when the work iteem enters the assignment. But the "advance flow" saction was not working and the item remains in the assignment. I am using optim istic locking and whever I am refreshing the assignment its giving the below error.
com.pega.pegarules.pub.PRAppRuntimeException: Caused by Unable to authorize flow action execution: <pzInsKey of the flow action>
Require some help to resolve this.
***Updated by Moderator: Lochan. Removed user added Ask the Expert tag. Apologies for confusion, shouldn't have been an end-user option***
Accepted Solution
Pegasystems Inc.
JP
For the first issue, Trace the Datetime property to see if it has a value when the flow reaches the assignment.
For the second issue, SLA agent processes an SLA queue item using the same access group as the operator who created the SLA queue item. Remove the security restriction with the flowaction will work. However, the flowaction will also appear in the action list on the screen.You may need a post action activity to perform certain validation to prevent human operators from executing the flowaction. Using ticket instead of flowaction to advance the flow is another approach.
Chunzhi
Allianz Technology
DE
1) I am setting "Set to the value of Property" in the Calculate Service Level field and giving a DateTime property of pyWorkPage in GOAL. Then I am adding the SLA in an assignment. But whenever any work item enter that assignment it is throwing the below error.
cannot be null/empty. page: pyWorkPage. Details: Invalid value for aReference passed to com.pega.pegarules.data.internal.clipboard.ClipboardPageImpl.getString(String)
I've experienced the same issue recently and it turned out that both Goal and Deadline properties must be provided even though they are not required in SLA rule form. So the solution is to provide the second property and it should work fine.