How is audit history written when Assignment is routed
I understand audit history is recorded using different ways throughout the case lifecycle. There is "History-Add" method, AddWorkHistory activity called from CompleteAssignment, AddHistoryPage function used by SLA agents etc. Of these AddWorkHistory gives a way to extend the properties written to history table (AddWorkHistoryDefaults). I want to understand how is the history written when assignment is just routed (pyHistoryMemo AssignmentRouted) is added in the Memo. I searched a lot but could not find the exact invocation point. I am trying to find this to understand if I could use AddWorkHistory inorder to add more fields to the work history table when the assignment is newly created and routed to a WL/WB.
If someone knows about this invocation point, please let me know. meanwhile I shall continue my search for the invocation point
***Edited by Moderator Marissa to update platform capability tags****
I believe that specific history entry is written by the process engine, so is probably not readily extensible. That said, you might be able to do something with field values to customize the content of the history entry, though I've never tried it myself, so I'm not sure if it would really work for you.
Thanks Mike for taking time for my query. The idea of playing with field values sounds good. In my current requirement it might not help, since I need to store the assignment status in the history table for reporting as the assignment is assigned and completed. I did the part when the assignment is completed by extending pyAddWorkHistoryDefaults activity