Question
MBAFC
CN
Last activity: 14 Jun 2016 10:53 EDT
Version Management And Release
I have some question about the version Management as follow:
Or somebody have good experience about the version management and release on the other scenario?
Scenario 1
Existed Class was modified on the development environment for a customer requirement.
However before the modified release to the product environment , a bug should be resolved.
At this situation,please confirm the follow questions:
ã»If there is a way to rollback all the modified on the non-versioned rules?
ã»If there is a way to avoid the modified class been released to the product environment ?
ã»If there is a way to rollback the development environment to un-modified status.
Scenario 2
New Class was Added on the development environment for a customer requirement.
However before the modified release to the product environment , a bug should be resolved.
At this situation,please confirm the follow questions:
ã»If there is a way to avoid the Added class been released to the product environment ?
Scenario 3
There is an minor fixes(no non-version ruleset was modified) added in a new ruleset version.
ã»How to release the modified content?
ã»If the best way is just import the added ruleset version?
Scenario 4
ã»How to deal the non-versioned rules when create theãproduct?
Message was edited by: Lochan to add Category
Pegasystems Inc.
IN
Hello Tian,
For scenario 1 & 2 :
>> Generally, Bug fixing and new development needs to be done under separate ruleset versions in order to take care this kind of challenges. This is a good practice to follow.
There is no such way to rollback the modified and non versioned rule other than delete or withdrawn them, But that might spoil all your developers effort. So instead go for withdraw or rollback proper ruleset versioning management will help you.
Refer this article for details : https://docs-previous.pega.com/reuse-and-version-management
For Scenario 3:
>> Minor fixes can be imported via periodic patch releases. You can create a RAP of the ruleset version and move it to prod. Make sure that the ruleset version you use for this minor change has only patch version changed.
For Scenario 4 :
>> In order to deal with non versioned rule , you have to give the pzInskey of the rules under the Individual instances to include”” Tab of the product rule.
Refer these article for details :
Hello Tian,
For scenario 1 & 2 :
>> Generally, Bug fixing and new development needs to be done under separate ruleset versions in order to take care this kind of challenges. This is a good practice to follow.
There is no such way to rollback the modified and non versioned rule other than delete or withdrawn them, But that might spoil all your developers effort. So instead go for withdraw or rollback proper ruleset versioning management will help you.
Refer this article for details : https://docs-previous.pega.com/reuse-and-version-management
For Scenario 3:
>> Minor fixes can be imported via periodic patch releases. You can create a RAP of the ruleset version and move it to prod. Make sure that the ruleset version you use for this minor change has only patch version changed.
For Scenario 4 :
>> In order to deal with non versioned rule , you have to give the pzInskey of the rules under the Individual instances to include”” Tab of the product rule.
Refer these article for details :
https://community.pega.com/sites/default/files/help_v72/procomhelpmain.htm
https://community.pega.com/sites/default/files/help_v72/procomhelpmain.htm