Modifying BPAuditEvents Archiving Script

MaxMcConchie — Wed, 25 Mar 2020 02:29:00 GMT

Hi,

I am trying to work out the best way to manage the BPAuditEvents table in Blue Prism. We currently have a policy to delete anything > 6 months old via the trim-process-history.sql query. The problem with this is that process/object versions are deleted.
What I want to do is to ensure there is at least 1 historical version of a process/object at all times as it's important for our release manager to be able to compare to a previous version when importing.

Has anyone been able to modify the script or has an alternative way to manage this?

Any assistance would be appreciated.

Thanks

------------------------------
Max McConchie
Automation Manager
Australian Government Department of Finance
------------------------------

RE: Modifying BPAuditEvents Archiving Script

John__Carter — Wed, 25 Mar 2020 10:19:00 GMT

Hi Max - please ask advice from our support team, but I guess it would be a case of adding a condition to exclude the 'user x modified process y' rows.

------------------------------
John Carter
Professional Services
Blue Prism
------------------------------

topic RE: Modifying BPAuditEvents Archiving Script in Product Forum

Modifying BPAuditEvents Archiving Script

RE: Modifying BPAuditEvents Archiving Script