SLA agent saves deleted assignment back ?
Is there a known Pege Defect in which SLA agent saves an assignment back into assignment table after the WO is resolved by user, and the assignment is deleted from assignment table? This causes dangling assignment, i.e. WO resolved and flow removed, but assignment remains.
I doubt this is what happens in our 6.2 SP2 production environment. In our SLA rule definition, no escalation activity is defined. And SLA agent and user are trying to work on the WO at the same time.
***Updated by moderator: Lochan to add Categories***