Posted: 3 Aug 2016 5:19 EDT Last activity: 14 Dec 2016 8:14 EST
Adjusting Service Level (SLA) with pxAdjustSLATimes
Taking a somewhat different approach than the provided solution, has anyone ever tried to call the pxAdjustSLATimes activity (not to be confused with pyAdjustAssignmentSLA) directly as this activity is listed in PRPC's Process API? (see attached screenshot of Activity)
When I pass some pyWorkPage.pxFlow(<ID>).pxAssignmentKey as AssignmentID and set Fixed goal and deadline adjustments the activity messes up the original pyWorkPage. The case (transaction) can no longer continue; although the assignment 's new SLA got applied (see attached screenshot of Clipboard). Did something break in Pega 7.1.9 or do I need different parameters?
I would appreciate to see a working example for this feature that does not rely on the UI with manual form.
The activity is performing a commit therefore this would definitely have some affect on the case transaction. Suggest calling the activity without an active case as a commit will cause all deferred write operations to be commited to the database for the requestor which could upset desired transaction boundaries.
Instead of setting the parameters param.AdjustmentMode, param.GoalOverrideDateTime and param.DeadlineOverrideDateTime for the activity, try setting the properties.pyAdjustSLATimes , .pyAdjustSLAGoalDateTime and .pyAdjustSLADeadlineDateTime on the pyWorkPage, and passing it to the activity.