Enabling the Pega repository type
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:
Click pyCanRebase rule that applies to @baseclass.and open the
Choose a ruleset in your application, then click Create and open.
In the Conditions tab, clickand change the condition to
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 Pega repositories for rebasing.
- Creating a repository
Create connections between Pega Platform and repositories to provide centralized storage, versioning, and metadata support for file storage and knowledge management, for example, to store and source file attachments in cases, or for use in DevOps.
- Integrating with file and content management systems
File storage and knowledge management repositories store assets and provide versioning and metadata support. Pega Platform can communicate with common repository technologies and can also act as a binary repository.