A report which is based on a custom history work class, is using pxAssignmentPastDeadline as one of it's column to see which tasks/assignments did not meet the SLA.
While testing found that even though few assignments were resolved after the Deadline was crossed, pxAssignmentPastDeadline column's values are 0 for all the tasks. However, pxAssignmentElapsedtime is getting captured properly.
If someone can explain why pxAssignmentPastDeadline is not getting captured correctly or the possible root-cause, would be really helpful
***Edited by Moderator Marije to change type from Pega Academy to Product***
pxAssignmentPastDeadline & pxAssignmentPastGoal are set in Assign-.AddWorkHistory actvity when an assignment is completed.
These properties are set based on 2 properties in newAssignPage (pxDeadlineExecute & pxGoalExecute) which are in turn set by ServiceLevelEvents agent. Whenever SLA event is raised and corresponding action is run, assign page is updated with actual time the goal/deadline activity ran.
If you are noticing "0" in pxAssignmentPastDeadline in a history note, you have to check
1. SLA is correctly defined on that assignment.
2. If yes, trace SLA agent to see that pxGoalExecute/pxDeadlineExecute are correctly updated in newAssignPage and persisted to DB
3. Trace "Complete Assignment" step on that assignment and see if Assign-.AddWorkHistory is able to read pxGoalExecute/pxDeadlineExecute from that assignment