0% found this document useful (0 votes)
97 views

Locking and Rolling Ruleset Versions

To prepare for development, systems using ruleset prerequisite validation should lock existing rulesets and roll them to new versions. This ensures future development uses upgraded rulesets and applications consistently reference the latest features. The process involves locking each application's ruleset, reviewing and updating prerequisites, rolling rulesets to a new version number, and verifying prerequisites point to the correct platform version.

Uploaded by

srinivas
Copyright
© © All Rights Reserved
Available Formats
Download as PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
97 views

Locking and Rolling Ruleset Versions

To prepare for development, systems using ruleset prerequisite validation should lock existing rulesets and roll them to new versions. This ensures future development uses upgraded rulesets and applications consistently reference the latest features. The process involves locking each application's ruleset, reviewing and updating prerequisites, rolling rulesets to a new version number, and verifying prerequisites point to the correct platform version.

Uploaded by

srinivas
Copyright
© © All Rights Reserved
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 2

Locking and rolling ruleset versions

Note: The following content, referenced from Pega Community, is included here to help you better achieve the module
learning objectives.

If your system includes ruleset names that use ruleset prerequisite validation instead of application-based validation, lock
your existing ruleset and roll them into new versions before you continue your development. Locking ensures that future
development is based on the upgraded rulesets and that your applications consistently reference the latest features.

Note: The upgrade process automatically upgrades any prerequisite for Pega-ProCom to the highest version of the
ruleset in the system.

1. In the header of Dev Studio, click Configure Application Structure Referencing Applications .
2. Display the application page by clicking Lock and Roll for each application.
3. Review the ruleset version prerequisites for the application ruleset by selecting+ next to Prerequisites. To modify a
required rule form, click the name of the ruleset version to edit it.
4. Select the Lock checkbox and select Update my application to include the new ruleset versions.
5. Enter the password for this ruleset version and select the Roll checkbox.
6. In the Roll to Version field, enter a new ruleset version or accept the default version which increments the current
version by one.
7. In the NEW section of the Prerequisites verify the list of ruleset prerequisites.

In particular, verify that the lowest ruleset points to the appropriate version of Pega Platform
8. Apply the changes to your ruleset by clickingRun.
9. Repeat these steps for each application in your system.

If your system includes ruleset names that use ruleset prerequisite validation instead of application-based validation, lock
your existing ruleset and roll them into new versions before you continue your development. Locking ensures that future
development is based on the upgraded rulesets and that your applications consistently reference the latest features.

Note: The upgrade process automatically upgrades any prerequisite for Pega-ProCom to the highest version of the
ruleset in the system.

1. In the header of Dev Studio, click Configure Application Structure Referencing Applications .
2. Display the application page by clicking Lock and Roll for each application.
3. Review the ruleset version prerequisites for the application ruleset by selecting+ next to Prerequisites. To modify a
required rule form, click the name of the ruleset version to edit it.
4. Select the Lock checkbox and select Update my application to include the new ruleset versions.
5. Enter the password for this ruleset version and select the Roll checkbox.
6. In the Roll to Version field, enter a new ruleset version or accept the default version which increments the current
version by one.
7. In the NEW section of the Prerequisites verify the list of ruleset prerequisites.
In particular, verify that the lowest ruleset points to the appropriate version of Pega Platform
8. Apply the changes to your ruleset by clickingRun.
9. Repeat these steps for each application in your system.

Locking and rolling ruleset versions -- Tue, 05/04/2021 - 02:52


To get the full experience of this content, please visit Locking and rolling ruleset versions

You might also like