2) CREATING A NEW APPLICATION VERSION
Application versioning
Pega provides two methods for creating new versions of an application. Each method preserves prior application versions. 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.
What tasks must you perform after the skim is complete?
Update the application rules, the Requires RuleSets and Versions prerequisites array in RuleSet version rules, and the access groups to reference the new major or minor version.
You can also use Create a new version of my application to
allow people access to more than one version of the application (for example, during a phased roll-out or a test period).
What is the importance of application versioning? -Application versioning provides the ability to version data classes without impacting existing data classes. -Application versioning preserves prior application versions. -Application versioning provides the ability to clone rules. -Application versioning provides a means to organize applications by priority.
Application versioning preserves prior application versions.
What advantage does skimming provide over lock and roll as a versioning option? -Pega provides a skimming wizard but not a lock and roll wizard. -Skimming saves checked out rules. Lock and roll does not save checked out rules. -Skimming carries blocked rules forward. Lock and roll does not carry blocked rules forward. -Skimming is most efficient for major and minor updates. Lock and roll is most useful for patches.
Skimming is most efficient for major and minor updates. Lock and roll is most useful for patches.
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. A rule's availability status determines if the rule is carried forward.
Why would you use skimming instead of lock and roll when versioning an application?
Skimming is the process of saving the highest version of a rule into a new, higher ruleset version. Skimming streamlines application versions where rule changes follow a logical sequence.
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. Minor and major versions require application record and access group updates. Patches usually do not need the updates. If you roll 01-01-01 to 02-03-01, Pega will start at 02-03-01 and look back to the previous minor version, 02-01-01, to find rules. As long as the rule is present in one of the versions, Pega can find it. If a rule is only in 01-03-05, rule resolution will not find it because it is in a different major version.
When creating a new ruleset version, what extra step must the system architect perform? -Change the decision table item numbers. -Rulesets cannot be versioned. -There are no extra steps if the ruleset version is up-to-date. -Lock the ruleset to prevent automatic versioning.
There are no extra steps if the ruleset version is up-to-date.
When using lock and roll, what is the purpose of selecting the new version option?
You use create a new version when you want to lock and roll the version and create a new application rule. You can also create a new application version when you want to have people access more than one version of the application (for example, a phased roll-out or a test period).
versioning methods are....
lock and roll skimming.
Within lock and roll, you have three choices for updating the application rule:
no change, edit the current version, and create a new version.
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 current application is locked, enter the application password.
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 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 current application is locked, enter the application password.
