Skip to main content


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

Specifying product rule deployment options

Updated on July 8, 2022

To automatically revalidate and save the product rule on import, to provide a file with post-import information, and to specify classes to bypass during an update, configure the deployment options.

  1. On the Product rule form, click the Deployment tab.
  2. Optional: To specify a Read Me file to open automatically after deploying the product rule, enter the second key part (Stream Name) of an HTML rule that has Rule-Admin-Product as the applies to key part.
    The rule must belong to a ruleset and version included on the Contents tab, or be an HTML rule that is always present on the destination systems.
  3. Optional: To automatically revalidate class instances against an application version context and save those class instances after the import, complete the Revalidate and save section.
    1. Enter the name and version number of an application that is part of the product rule.
    2. Add class instances to revalidate and save after the import.
      If an application version already exists on the target system, the system does not revalidate and save.
    3. Optional: To define the context that the system uses to revalidate and save rules, in the Access Group field, enter the application access group.

      Specifying the context ensures that the system revalidates and saves rules with the correct application permissions.

    4. Optional: To validate all descendents of a class, select Include descendants.
  4. Optional: Specify classes to bypass for updates during an import. The import makes no changes to these classes.
  5. Click Save.

    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