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.

Resolving pre-existing rule conflicts

Updated on April 5, 2022

If your import archive includes rule instances that are already present in the target system, resolve the conflict before you continue the import.

It is a best practice to resolve conflicts before importing these rules, either by refactoring the application on your target system to remove the references to these rules, or by repackaging your import archive so that it does not contain these rules. Work with your application team to determine which rule set should contain the rules.

If you continue the import and replace the existing rules on the target system with the rules with the same name in the archive, Pega Platform applications on the target system that reference these rules may no longer work correctly. If you chose not to import these rules, rules in the Import archive that reference these rules may not work correctly.

Follow these steps to overwrite the existing rules:

  1. Select the rule instances to overwrite.
  2. Click Next.
    • Previous topic Scheduling indexes for population
    • Next topic Changing the built-on version of an application to the current version

    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. is not optimized for Internet Explorer. For the optimal experience, please use:

    Close Deprecation Notice
    Contact us