Question
Last activity: 15 Jan 2016 12:22 EST
Security audit for data instances is not working
We need a report to track data instances updates (Add, Change and Remove),so we have enabled the "Security Audit" feature for data class, but unable to view the records in report.
Configuration steps :
1) "OrgA-Customer-data-ProductInfo" and "History-OrgA-Customer-Data-ProductInfo" classes had been created.
2) Defined the data transform pyTrackSecurityChanges in the data class.Updated the following list of properties to be tracked.
3) Created the declare trigger rule named "TrackSecurityChanges"
4) the following data Instances were created in app flow
We need a report to track data instances updates (Add, Change and Remove),so we have enabled the "Security Audit" feature for data class, but unable to view the records in report.
Configuration steps :
1) "OrgA-Customer-data-ProductInfo" and "History-OrgA-Customer-Data-ProductInfo" classes had been created.
2) Defined the data transform pyTrackSecurityChanges in the data class.Updated the following list of properties to be tracked.
3) Created the declare trigger rule named "TrackSecurityChanges"
4) the following data Instances were created in app flow
5) Created the report definition rule names "TrackSecurity" with History-OrgA-Customer-Data-ProductInfo as the Applies To class .but the report has not returned any results ,and none of history instance was created.
I've followed the PRPC help and https://pdn.pega.com/security/how-to-audit-field-level-changes-to-security-rule-and-data-instances pdn article.
PRPC version :7.1.9.
Accepted Solution
Pegasystems Inc.
IN
>>> can't we separate the action portion (Add/remove/changed) from pyMemo and display it as new column?
we might need to customize the clipboard results to present action portion in a new column in repeat grid.
Please share your thoughts/comments, Thank you!
psahukaru
Pegasystems Inc.
IN
could you please share the observations after changing the option 'Trigger when an instance is' to 'Saved' from 'Comitted Save' in declare trigger rule (step #3) - Thank you!
Thanks Phani..History instances are being created after changing the option 'Trigger when an instance is' to 'Saved' .
The pyLabel & pyMemo columns are added to the report definition rule and below details returned ,but information is being scattered with respect to the properties.
Can't we bring up the audit information into the same row for every operation as mentioned below?
Updated: 18 Nov 2015 13:49 EST
Thanks Phani for sharing the updates.
Here is the outcome of the report definition after did above configuration.
I'm good with the view,but can't we separate the action portion (Add/remove/changed) from pyMemo and display it as new column?
Accepted Solution
Pegasystems Inc.
IN
>>> can't we separate the action portion (Add/remove/changed) from pyMemo and display it as new column?
we might need to customize the clipboard results to present action portion in a new column in repeat grid.
Please share your thoughts/comments, Thank you!
psahukaru
BNY Mellon
US
Would like a history table with the following columns:
- Class
- Key
- Operator
- Timestamp
- Operation
- FieldChanged
- FieldOldValue
- FieldNewValue
Merging together the last 4 items into a single Memo field isn't very scaleable. (e.g., typically we might want to filter on FieldChanged).
Pegasystems Inc.
IN
Hi Jon, Good Morning!
>>> Would like a history table with the following columns
- can we map the history-<class> through DADT to a cloned version of database table (pc_history_work) without Blob column?
Please share your thoughts/comments, Thank you!
psahukaru
Pegasystems Inc.
US
Jon,
Thank you for finding SA-1261 for Pega 7.1.4, advertising the fix in Pega 7.1.7.
Others might be interested in the SA and its Comment thread, https://community.pega.com/support/support-articles/pytracksecuritychanges-not-capturing-index-information
-Mary