Data traceability
Financial Services institutions are subject to a number of regulations that vary between jurisdictions. In addition to meeting these regulations across the globe, institutions need to prove to regulatory auditors how specific decisions were made. A large volume of data that drives those decisions is captured from a variety of sources, such as internal databases, customer self-service, manual entry by employees, and third party systems. It is important for the business to track where the data was initially captured and how it changes over time.
Use the data traceability feature to identify and track data objects and then configure auditable entries on a particular data object. The data change tracking engine will scan for changes and save them in an exposed, easily accessible data change repository.
To extend data traceability, do the Extending tracked security changes task.
For information about how data traceability is configured, see Data traceability.
Extending tracked security changes
Configure auditable entries on a particular data object that you want to track, for example, business goals.
In the header of Dev Studio, in the search text field, enter FSIFTrackSecurityChanges and select the PegaFS-Data-Party-MasterProfile data transform rule.
Save the rule into your implementation layer. For additional information about locked and unlocked rulesets, see Copying a rule or data instance.
Click Add a row.
Enter RelevantRelationshipList.LinkedChildren for both the Target and Source fields.
Click Save.
In the header of Dev Studio,, in the search text field, enter FSIFTrackSecurityChanges and select the PegaFS-Data-PartyPartyXref data transform rule.
Save the rule into your implementation layer. For additional information about locked and unlocked rulesets, see Copying a rule or data instance.
Click Add a row.
Enter LinkedChildren for both the Target and Source fields.
Click Save.
Previous topic Enhancing case searches Next topic Configuring the Case summary feature