We have a high-volume standalone concrete table in our Production environment along with its associated history table. As part of a performance optimization effort, we are attempting to disable the creation of history records for this table.
We have set Bypass History on Save to true. This behaves as expected when performing an Obj-Save, as no records are written to the associated history table.
However, when the same data is saved using a Savable Data Page, history records are still being created.
We would appreciate guidance on the recommended approach to fully disable history writing when persisting records through a Savable Data Page. Specifically:
Is there additional configuration required beyond setting Bypass History on Save?
Does the Save Plan used by the Savable Data Page override or bypass this setting?
Are there known considerations or best practices for preventing history writes in this scenario?
Unfortunately, for data instances saved using Savable Data pages do not honor the flag of skipping the history entries as it does for you use Obj-Save methods.
However, you can make use of the extension points provided in the @baseclass.Save activity which is PreSave to set the param.SkipHistory = true.
However, if i look at the OOTB rule as shown below, the pass current parameter page is not checked. So even if you extend the PreSave in your specific Data class to set this SkipHistory parameter it is of no use.
If skipping the history for few data classes is crucial for your application, then you can raise an INC to pega to understand why this Pass current parameter page was not checked in this rule. If this was just a miss, then you can get a hotfix sort of thing and then you can implement the extension as per your need in specific classes based with proper security checks and conditions.
This Save activity is an available rule and hence you might be tempted to save as this to your application ruleset and make this change. Please do not do that.
Contact pega and then follow the best practices.
If the INC option does not work out, then you can go with Obj-Save option implemented in an activity and call this in your Savable data page data save options.
Your observation is correct. Even if the bypass history on save, it creates history entries. But its worth noting, its just the “memo” type history entries and not the snapshot history entries.
So technically its bypassing taking the history snapshots but just write the memo type entry.
If you do not want the memo as well, then the only option is to use activity for saveplan and use obj-save as JC mentioned.
@AnandrajT7685 Can you update the Application Setting pyDisableHistory to true and test the following, I remember we did this one of the project and then it stopped saving the history records in the history table.
I tried this for one of the data type for creating new entries from records manager landing page and still the history records for the data class are getting saved into database.
