Question
S & P Global Company Ltd
IN
Last activity: 8 Apr 2019 9:27 EDT
Audit history for AssignmentRouted
Hi,
I just wanted to know at what point Filed Value named pyHistoryMemo.AssignmentRouted is being triggered. I tried finding the references of it and an all content search but no success.
This is being invoked though in my application which is resulting in storing the pyMessageKey in our DB for history table. Below is a sample
[<OurWorkClass>.pyHistoryMemo]AssignmentRouted <Param1> "
My intention is to find any extension activity to update the 2nd param. As of now this is not getting passed from the triggering point.
Any guidance regarding this would be appreciated.
Thanks
Praveen
***Edited by Moderator: Pallavi to update platform capability tags***
Pegasystems Inc.
US
I could see FilterHistory decision tree referencing "AssignmentRouted", it will be called if the production level is 2 and the System Setting FilterHistory value for level 2 is "WRITE_SOME", which is the default. I was looking at a Pega 8.1.x environment, not sure what version of Pega you are running.
S & P Global Company Ltd
IN
Thanks Kevin. But I am more interested in the invoking of this field value so that I can pass my intended param values. Decision tree reference is more on whether it can be invoked or not but not the actual triggering point.
Pegasystems Inc.
IN
Hi Praveen,
If you are looking to find a way to customize AssignmentRouted, currently there is no way as it is referred via Task_Assignmment --> AddHistory functions which are final. Probably you can call extension activity pyAddWorkHistoryDefaults before commiting history record which is commited in AddHistory. But AddHistory is common function invoked for history, care should be taken while overriding this activity as the same will be called from AddWOrkHistory.
Thanks.
S & P Global Company Ltd
IN
Hi Sreepriya,
I am unable to find the function AddHistory. Can you please let me know the ruleset name and version what you are referring to.
Also as I see pyAddWorkHistoryDefaults is only getting called once for completed task and no trace of it can be seen while assigning the new task. Can you please help understand it further.
Thanks
Praveen