Is there any drawback in deleting history tables content?
Our client asked us for a custom work item history, so we don't show them the OOTB history in GUI.
Is there any drawback in deleting old history records for work items? (i.e. older than 30 days)
Our history tables are becoming bigger and bigger and we are not using that information, but we aren't sure if OOTB feature expect to find them and deleting them could create any exception.
Accepted Solution
Updated: 21 Feb 2022 8:02 EST
Lventur
IN
You will not have any negative impact if you are deleting audit history record of work object.. But instead of deleting the history why can't you disable the un-wanted history category..
Pega will be having a decision tree via which history table insert logic will get handled.. If you don't want the pega OOTB history, then just turn off the logic in decision tree not to add audit history for OOTB categories.
Decision Tree Name = FilterHistory.
Please refer below mentioned article also..
History writes and case auditing in Pega – Pega Knowledge Sharing (myknowpega.com)
Pegasystems Inc.
GB
When 'Bypass History on Save' is set to true, you will still get history memo instances but you will not get instances containing snapshots of the data.
The majority of the content of the pr_history table are likely application specific history data. You should be mapping this content to an application specific history table (class) instead of using pr_history.
For the pr_history table please run this query from query runner: SELECT count(pxobjclass), pxobjclass FROM pegadata.pr_history GROUP BY PXOBJCLASS
The cleanup of that table depends on whether you need to keep those history records or not.
You might be also interested in articles from pega comunity: