1

FR

Pega Certified Senior System Architect(v8)

Session 05
Agenda

• Application Versioning
• Introduction to creating a new application version
• Methods of Versioning
• Creating a new application version
Application Versioning

• Pega Platform provides the ability to preserve a version of an application. You can
edit application functionality in a new version of the application without changing the
initial version.
• Application versioning is a way to differentiate current and past application
configurations. Rule resolution can look through all the minor and patch versions for
the current major ruleset.
• Application components include the application ruleset stack — this contains the
rules and data types used by the application. To version an application, you must
version the application's rulesets.
Application Versioning

 Pega provides two methods for creating new versions of an application. Each
method preserves prior application versions.
• Lock and roll
• Skimming.
 The act of using a version method begins a release cycle. Every major version,
minor version, and patch version represents a release cycle. Both methods list the
highest version, and offers to roll the ruleset to a still-higher version by default.
Lock and Roll

• Small changes or patches are ideal for lock and roll. Application patches and minor
updates usually involve updating rules. When using lock and roll, you create a new
empty ruleset version. To update the configuration, you copy the necessary rules
into the new ruleset version.
• The rule in the higher ruleset version overrides the rule in the lower version. You
specify the new version number and whether to update the application record and
access groups to reflect the ruleset version.
Lock and Roll
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:
• Do not update my application
• Update my Application to include the new Ruleset Versions
• Create a new version of my application
Lock and Roll

• 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.

• 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.
Lock and Roll

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).
Skimming

• Skimming is the process of saving the highest version of a rule into a new, higher
ruleset version. Skimming applies mainly to resolved rules. Skimming is useful
when rule changes follow a logical sequence. The two types of skims are minor and
major. The skim types correspond with the update types (major or minor/patch).
• During a minor skim, rules are stored in a higher minor version, and during a major
skim, rules are stored in a higher major version.
• Pega provides a skimming wizard. For each rule instance in a specified ruleset, the
wizard identifies the highest-numbered version and creates a copy with the number
you specify.
Skimming
• A rule's availability status determines if the rule is carried forward. This table defines
the rules that are carried forward during a skim.

Rule Availability Status Carried forward?

Yes Yes
Blocked Yes
Final Yes
Withdrawn No - major update;
Yes - minor update
No (not available) No

• The key to skimming is you can start at a major version and skim all minor and
patch numbers into a new version, or you can start at some minor version and work
up from there.
Skimming
Skimming

• 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.
• 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.
Questions ??
Thank You