SLA Agent Behavior in 6.1 SP2 is incorrect
After upgrading from PRPC 5.1 to PRPC 6.1sp2, users see that custom Service Level Agreement (SLA) functionality is not working, and updated SLA Goal values are not taking effect.
Steps to Reproduce
Attempt to update the Goal time for a custom SLA, and observe the time the SLA processes.
The root cause of this problem is a defect in customer application code/rules that did not take into account the changes to SLA processing between 5.1 and 6.1.
The explanation for this behavior is as follows: SLA processing is now done via the Queue Manager, directly updating the SLA properties on the assignment will not affect the assignment's associated System-Queue-ServiceLevel instance (SLA queue item). To update the SLA queue item, use the out of the box activities ActionChangeWorkSLAProps and ActionChangeAssignmentSLAProps.
0% found this useful