Locking the release
After all merges are completed, the release engineer locks the applications and rulesets to be released. They are also responsible for creating the new, higher-level ruleset versions and higher-level application rules for the next release.
To lock the release, do the following steps:
Result: The application rules and ruleset versions for the current
release are locked and require passwords to make changes. Also, you will have created
the higher-level ruleset versions and application rules that will be used for the next
release. What to do next: Configure higher environments: Staging, BOE, and
Production. For more information, see Configuring higher environments.
- In Dev Studio, click .
- Click Lock & Roll.
Note: As a best practice, lock your built-on applications first, and then work your way up the stack to your top-level application. This way, as each higher version application rule is created, you can open that rule and update the version of the built-on application.
- For each ruleset:
- Click Lock and provide a password.
- Click Roll.
- Click Create a new version of my Application.
- Click Run.
Previous topic Implementing Pega Next-Best-Action Advisor Next topic Configuring higher environments