Skip to main content

This content is closed to future replies and is no longer being maintained or updated.
Links may no longer function. If you have a similar request, please write a new post.

Question

 abhishek khanna (AbhishekkKhanna)
OCBC Bank
abhishek khanna
OCBC Bank
SG
AbhishekkKhanna Member since 2015 10 posts
OCBC Bank
Posted: Oct 31, 2018
Last activity: Nov 1, 2018
Posted: 31 Oct 2018 0:10 EDT
Last activity: 1 Nov 2018 3:06 EDT
Closed
Solved

Field Level Auditing requirement for 100 fields

Our client has requirements where they need to log the field changes. The number of fields are around 100 and most will be committed along the case flow ,not at once.

Is there any other optimized approach other than Field Level Auditing.

To see attachments, please log in.
Case Management
Reporting

Posted: 6 years ago
Posted: 1 Nov 2018 3:06 EDT
abhishek khanna (AbhishekkKhanna)
OCBC Bank
abhishek khanna
OCBC Bank
SG

Hey Marc,

This seems to be exactly what Field Level Auditing is for. 
[Abhishek] I have used this for key fields in my previous implementations. But my current requirement wants to use the same to Log everything in the case(50 > properties). I think it will be a performance hit for the application for each save\commit.Any inputs?

What are the reasons for looking for an alternative solution?
[Abhishek] Keeping in Performance in mind, i was thinking if there could be another way to implement the same.

 
To see attachments, please log in.

We'd prefer it if you saw us at our best.

Pega Collaboration Center has detected you are using a browser which may prevent you from experiencing the site as intended. To improve your experience, please update your browser.

Close Deprecation Notice