Field Level Auditing on CSV Bulk Import
Hello, We have a requirement to perform field level auditing on any additions/changes made to a table via CSV Import. Currently FLA works as intended for manual changes, which are correctly shown in our history class. Is there a suitable extension point or method to enable auditing to occur on all records imported via CSV? Thanks
Accepted Solution
Updated: 2 Oct 2023 8:20 EDT
Pegasystems Inc.
GB
@MarijeSchillernThanks for the input. Solution reached via the use of a Committed Save Declare Trigger that executes a modified TrackSecurityChanges. Within the modified Activity History-Add step was used for basic logging and the Java code (step 6) was tweaked to pull additional params needed from primary page.
Pegasystems Inc.
GB
@ojinc Here is the response from an AI-bot's search of our documentation:
To enable field-level auditing for records imported via CSV, you can create a custom activity or data transform that processes the imported data and applies the necessary auditing logic. In this custom activity or data transform, you can use the Add-History method or leverage the existing field-level auditing mechanism by invoking the pySave activity from the FLAudit- class. Make sure to call this custom activity or data transform after the CSV import process to ensure that all changes are captured and audited.
References
The extension point for field-level auditing
Field-level auditing > Field-level audit implementation
Field Level Auditing Customization is not working
Similar questions such as Is field level auditing available for page group properties have been raised in the past.
@ojinc Here is the response from an AI-bot's search of our documentation:
To enable field-level auditing for records imported via CSV, you can create a custom activity or data transform that processes the imported data and applies the necessary auditing logic. In this custom activity or data transform, you can use the Add-History method or leverage the existing field-level auditing mechanism by invoking the pySave activity from the FLAudit- class. Make sure to call this custom activity or data transform after the CSV import process to ensure that all changes are captured and audited.
References
The extension point for field-level auditing
Field-level auditing > Field-level audit implementation
Field Level Auditing Customization is not working
Similar questions such as Is field level auditing available for page group properties have been raised in the past.
Please have a look internally at AS item "Enhance Field Level Auditing For Pagelists" (US-442635) to see discussions around FLA changes. You may want to contact the relevant parties to 'vote' for it.
@picada is this something you might be able to comment on?
Accepted Solution
Updated: 2 Oct 2023 8:20 EDT
Pegasystems Inc.
GB
@MarijeSchillernThanks for the input. Solution reached via the use of a Committed Save Declare Trigger that executes a modified TrackSecurityChanges. Within the modified Activity History-Add step was used for basic logging and the Java code (step 6) was tweaked to pull additional params needed from primary page.