Question
Tetrasoft India Private Limited
IN
Last activity: 22 Jan 2019 16:00 EST
How to Customize Audit Information of Fields in Work Object | PRPC 7.3.1
By default, on enabling Field Level Auditing on fields of a work type, we get complete Description as part of .pyMessageKey. (say "Changed <fieldName> from <oldName> to <newName>" in Description)
Instead of using Description column in History of Work Object, we need to display the Old Value,New Value and Field Name separately. (say <oldName> in Old Value , <newName> in New Value and <fieldName> in Field Name column seperately)
"HistoryListView" is used in displaying History of work object but we are not able to edit information in .pyMessageKey field to display information as specified above.
Any suggestions?
***Moderator Edit: Vidyaranjan | Updated Categories***
-
Like (0)
-
Share this page Facebook Twitter LinkedIn Email Copying... Copied!
Pegasystems Inc.
US
You can create field value rules as shown in this Help article.
-
Alexander Mendeev SaiKishore Yagnamurthy
Tetrasoft India Private Limited
IN
We tried customizing at UI level as suggested above but it happens to be costly if we use history table.
So, we created a separate table for auditing in DB. But we need to use this table instead of History table to store audit information.
Is there a way to do so?
Tetrasoft India Private Limited
IN
Can someone suggest if we can use a custom history table in database? If yes, how?
Pegasystems Inc.
IN
Hi Swati,
Greetings!!
What about using Data Type to store selective information as audit if history table is not the option.
Regards,
Ujjwal
Tetrasoft India Private Limited
IN
Hi Ujjwal,
We have option to use a separate DB table only for storing only required information.
Pegasystems Inc.
IN
Hi Swati,
Is it a table in PegaRules schema, if so then DataType approach should work.
If its a different DB then you may would like to review https://collaborate.pega.com/discussion/how-configure-external-db-connections-designer-studio
Regards,
Ujjwal
Tetrasoft India Private Limited
IN
Hi Ujjwal,
Actually, my question was different.
I will give you the background of what I already tried for a better understanding of the issue.
I have mapped a DB table to a class but need to set <oldName> in Old Value , <newName> in New Value and <fieldName> in Field Name column of this new class instead of history class.
In general, Declare Trigger pyTrackSecurityChanges uses TrackSecurityChanges Activity which has History- class properties set in Java step
As I have configured a separate class, I tried specifying this class and its properties in Java step of TrackSecurityChanges, but no luck.
So, I am looking for some alternative to do so.
Cigna
IN
Hi,
Have you received any update on this? I have similar requirement to separate the new and old value as well as action.
Pegasystems Inc.
US
Cigna
IN
This is the link to new post
https://collaborate.pega.com/question/pega-ootb-field-level-auditing
Tetrasoft India Private Limited
IN
Can someone share the possible ways of auditing properties in Pega?
Using history tables does not seem feasible for Page List and Page Group type of properties.
How to display each value separately from this type of properties while using history tables.
I have referred the following document.
If there are any updates on this please share.
Pegasystems Inc.
IN
FYI - Custom auditing of nested page/ Pagelist is not supported. It will be covered in future releases of PRPC.
Thanks,
Venkat
Tetrasoft India Private Limited
IN
Hi Venkat,
Can you please verify once again if the following can help for page list or page group type of properties?
For pagelist / pagegroups, what if we add an index table / class with updated date time as one of the keys? This would track all the changes done for the page list properties.
As we are on 7.3.1, can you please get a confirmation of possibility of this design in this version while trying to audit "page list" or "page group" type of properties?
Pegasystems Inc.
IN
Hi Dames,
From your reply I could understand, you want to use declare index which creates a separate index table for that property and you want to use update date time as key.
In that way, every time they change that property, it adds an entry into that table.
However, in this case performance will get effected and you should write your own logic on how to identify exact location of change.
As an alternative solution, you can have auditing enabled for specific properties within the page list. This will print the correct audit messages like "Account balance changed from '1000' to '2000' ". But again this has limitation that it doesn't print the nested path of the property i.e. Account balance of which Page list got updated.
Thanking you.
CollabPartnerz
IN
Below link might help you
https://collaborate.pega.com/question/work-object-migration-prpc-62-731