Skip to main content
This content is now archived and is no longer updated. Progress is not calculated. Pega Cloud instances are disabled, and badges are no longer awarded. Click here to continue your progress in the latest version.

Creating a new application version

Creating a new application version

You determine the method to use to create a new application version. Your choice is based on the type of application change. Small bug fixes and incremental application enhancement patches are ideal for lock and roll. Skimming streamlines applications versions where rule changes follow a logical progression.

Pre-process best practice recommends confirming the rules for the new version are checked in. You can run a search for checked out rules from the Checked Out Rules page. An additional best practice is locking all but the highest ruleset versions.

Lock and roll

In Dev Studio, navigate to the Configure > Application > Structure > RuleSet Stack page to access the Lock & Roll button.

Within lock and roll, you have three choices for updating the application rule:

  • You use Do not update my application when you update the patch version number of a ruleset without updating the application ruleset list. By default, the application rule only lists the major and minor version numbers for a ruleset, so incrementing the patch version number does not require a change to the application rule.
  • You use Update my Application to include the new Ruleset Versions when you are rolling out an application and updating the minor version or when the application rule lists the ruleset patch version number. You may enter a new application description. The default application description is current. If the current application is locked, enter the application password.
  • You use Create a new version of my application when:
    • You want to lock and roll the version and create a new application rule. You may enter a new application version, if different than the default one increment higher. You may enter a new application description. The default application description is current. If the current application is locked, enter the application password.
    • You want to allow people access to more than one version of the application (for example, during a phased roll-out or a test period).

You must select the appropriate ruleset versions for the lock and roll before proceeding. Most selections will be the most recent version. However, an earlier version of a ruleset might be appropriate. Application requirements dictate this decision.

You can view the rulesets in the current application version on the Ruleset Stack page. You can select the appropriate ruleset versions, enter the ruleset passwords, and select the update option in the Lock & Roll window.


In Dev Studio, navigate to the Configure > System >Refactor > RuleSets page to access the link to the Skim a RuleSet page. Indicate whether the update is to be a major version (NN-01-01) or a minor version (NN-MM-01), the rulesets to skim, and the version number to be created. Click Skim to begin the process.

The system creates a new ruleset version and begins copying rules. A status area shows progress and the results of the skim. The actual duration of the skim could be several minutes.

Tip: If errors occur, select the Total Number of Errors link in the lower right corner of the display form to view error messages. The error list is difficult to access after the results form closes. Print the list if you wish to research and address the errors after closing the form.

You must update application rules, the Requires RuleSets and Versions prerequisites array in RuleSet version rules, and access groups to reference the new major version after the skim completes. Log out and log in to access the new version.

Note: Skimming only copies the rules in the major version you select. For example, if you skim 02-ZZ-ZZ into 03-01-01, rules in version 01-ZZ-ZZ are ignored.

You must have the zipMoveSkim privilege to perform the skim. Pega provides a default role for system architects which includes zipMoveSkim. SysAdm4 is the default system role for system architects and includes the zipMoveSkim privilege. When an application is in production, the SysAdm4 role becomes the Administrator role.

For more information on skimming, view the Help topic Skim to create a higher version.

This Topic is available in the following Module:

We'd prefer it if you saw us at our best.

Pega Academy has detected you are using a browser which may prevent you from experiencing the site as intended. To improve your experience, please update your browser.

Close Deprecation Notice