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.

Enabling the Pega repository type

Updated on April 5, 2022

When you use continuous integration and delivery (CI/CD pipelines) third-party automation servers, you use Pega Platform as a binary repository for rule artifacts during development. You also use Pega repositories when you are rebasing your development application when you are using third-party automation servers or Deployment Manager.

If you are using Deployment Manager, the Pega repository type is already enabled; otherwise, you must first enable it for your application by completing the following steps:

  1. Click RecordsDecisionWhen and open the pyCanRebase rule that applies to @baseclass.

  2. Click Save AsSpecialize by class or ruleset.

  3. Choose a ruleset in your application, then click Create and open.

  4. In the Conditions tab, click ActionsEdit and change the condition to true.

  5. Click Submit.

  6. Click Save.

  7. If you are rebasing rules to refresh your development system with the latest rulesets that are hosted on a remote development system, enable ruleset versions for Pega repositories. For more information, see Enabling ruleset versions for the Pega repository.

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