Table of Contents

Packaging rules and data that contain field-level auditing information


Only available versions of this content are shown in the dropdown

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.
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
Did you find this content helpful?

Have a question? Get answers now.

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