Getting Class Name in the Audit message for OOTB Audits

This behavior typically occurs when the audit message is pulling the full property reference instead of just the localized label or description. In Constellation (starting with Pega 24.x), some OOTB audit rules reference pyHistoryMemo directly, which may include the class prefix.

The simplest way to resolve this is to override the OOTB pyHistoryMemo or audit note in your application. For each specific property, include a reference to the function @getLocalizedText() or a field value instead of the raw property reference.

Another point to note: there were recent updates to how audit handling works in Pega 24.1.x. If this issue started after an upgrade, review the release notes or hotfixes for changes to audit message formatting.

Finally, if you’d like to keep OOTB functionality intact, you can use a Data Transform (preferred) or Activity in the case lifecycle to strip out class names before writing to history. This approach adds complexity and may impact maintainability, so weigh that trade-off carefully.

Hope this helps! Let me know if you need more details.

To see attachments, please log in.

Question