Skip to main content


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

This content has been archived and is no longer being updated.

Links may not function; however, this content may be relevant to outdated versions of the product.

Packaging rules and data that contain field-level auditing information

Updated on November 22, 2021

To save time and maintain consistency when you deploy your application in another environment, ensure that the field-level auditing data in your cases persists, by packaging specific rules and classes.

For example, when you move your application from a staging to a production environment, you can move the auditing data for the fields in your case types at the same time.
Note: To ensure optimal migration of data when you package an application, exclude non-versioned rules from the content of product rules, and include the rules that carry field-level auditing data as individual instances. For more information about packaging your application rules, see Specifying the content of a product rule.

Ensure that you package the following rules of a Rule-Obj-Class rule type:

  • A full class of a case type with enabled field-level auditing, for example FLAudit-PegaProjMgmt-Work-UserStory-Epic
  • A class group of a class with enabled field-level auditing, for example FLAudit-PegaProjMgmt-Work

Ensure that you package the following data instances:

  • DataAdmin-DataBase-ClassGroup, for example FLAudit-PegaProjMgmt-Work
  • DataAdmin-DataBase, for example FLAudit-PegaProjMgmt-Work

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