Skip to main content


         This documentation site is for previous versions. Visit our new documentation site for current releases.      
 

Service interaction logging

Updated on February 9, 2022

If service request and response logging is enabled, Pega Smart Dispute for Issuers captures all MasterCom service interaction events in the audit log available for each case in the Third Party tab under the Audit tab. All error messages are listed in the external logs with the ERROR log level.

For more information, see “Enabling service request and response logging” in the Pega Smart Dispute for Issuers 7.4 Implementation Guide.

Event logging customization

With the LogMCOMClaimsMgrSvcInvocationExtension data transform, you can override and add any custom logging functionality that might be required for your implementation.

For more information, see “Customizing audit logging” in the Pega Smart Dispute for Issuers 7.4 Implementation Guide.

Sensitive information in the audit logs

With the GetSanitizedJSONForMCOMLogging data transform, you can hide any sensitive information, such as customers' account and card numbers, from audit logs.

For more information, see “Hiding sensitive information from audit logs” in the Pega Smart Dispute for Issuers 7.4 Implementation Guide.

Tags

Smart Dispute for Issuers 7.4 - 7.48 Smart Dispute for Issuers Low-Code App Development Financial Services

Have a question? Get answers now.

Visit the Support Center to ask questions, engage in discussions, share ideas, and help others.

Did you find this content helpful?

Want to help us improve this content?

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

Pega.com is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us