Case history forms for huge data over period of time. If you are planning to filter out the history/audit trail based on certain descriptions(eg: assignment completed, case saved) - the performance impact of this should be considered.If there are only certain actions through the case process which the business is interested in & need overview of (and feel the OOTB history is something they can't live with)
Have an extra flag in history table to differentiate certain milestones in the case history. Ensure the flag/field in the table is indexed for better performance & use it as filter to show the case history. You could add certain audit details to the case on say completion of certain assignment and thereby have "business approved" descriptions as milestones/history of case.
Need to dig in if the case narrative can be really be customized for it creates pyCaseNarrative when the WO is opened.
Thanks for this! It works on 50% for now and I think I'm doing something wrong.
So I added the AddHistory steps in my flows where I want to obtain the information for the Audit history. After that I saved a copy of theWork-.FilterHistory decision tree in my application RS and make the changes there so I can exclude most of the information collected and get only the steps defined in the flows.
However when I delete activities from the decision tree, that I don't want to see in the Audit, it does not remove the from the Audit trail.
I also set the settings in Pega-ProCom.FilterHistory to "WRITE_SOME" for all the production levels and started the "History-Work-.resetFilterHistory" activity. However the Audit trail still records all of the previous data + the newly added steps from me.
So my questions are - to remove activities from the Audit trail do I need to do a server restart or the filtering is entirely based on the Work-.FilterHistory decision tree?
If the filtering-out is entirely controlled by the decision tree - do I need to modify the original copy saved in Pega RS or my application RS copy will override the Pega one?
So with a bit of help from a Pega dev I got this one figured out:
When you follow the above steps from CarissaW_GCS be sure to not modify the name of the Filter History decision tree once you save it in your RS and be sure that the last step of the modified decision tree evaluates to "false" so you will have only the filtered information entered in it.
Also, there is no need to add a "Add History note" activity in the flow as in each connector there is a field "Audit note" which can add this information directly.
So, with this my issue is resolved and the moderators can close this topic. Thanks again for the help guys! :)