Revision updates minor version not the patch
If user is performing their revision using the same Application Overlay multiple times, each time the revision ruleset is incremented by 1 in Minor version.
After committing two Revisions into the application (DecisionR1 is the revision ruleset name), Pega created 01-01-02 as part of first revision, and 01-02-02 as part of second revision.
So in that order, if the Revision management is done for 99 times, the final revision ruleset version will be : 01-99-02.
User's questions are:
1. After new revision what is the behavior:
2. Is there any Extension point Available during creation of Revision ruleset versions, so that instead of incrementing the Minor version, one can increment the patch version only, which would enable to have more revision under the same Major version (say 01).
Steps to Reproduce
1.Create an ApplicationOverlay.
3.Create and activate the revision.
4.Open the ApplicationOverlay edit available rules and add another rule.
5.Create and activate the revision.
Repeat the steps.
Here’s the explanation for the reported behavior:
1. The minor versions are used for application overlay updates. The patch versions are used for revision versions. In the above scenario by adding a different rule to present application overlay user is updating the ApplicationOverlay. Therefore minor version is getting updated.
2. After 01-99-02 when user performs one more revision major version number changes.
Published March 24, 2018 - Updated December 2, 2021
Was this useful?
0% found this useful
Have a question? Get answers now.
Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.