Using Release Toggle to turn off a feature in QA
Hi, my client often needs to back out changes deployed to QA. Today they do that by unlocking rulesets in DEV, marking all rules Not Available, and redeploying the same ruleset to QA. I believe this is not a Pega best practice, and this creates overhead in our process.
Can we potentially use the release toggle feature in Pega Platform?
***Edited by Moderator Marije to add Capability tags***
Lventur
IN
If you want to restrict the latest deployed features then instead of making rule status as "Not Avail" and re-deploying the code..
You could just update the RS version in application stack right..
For Ex:
Latest features deployed to staging avail in RS version 01-01-15
Now client is telling they don't want 01-01-15 code changes in staging, then you can just update the RS version to 01-01-14 in application stack then pega will not use latest features (01-01-15 ) code avail in staging environment...
Pegasystems Inc.
US
@Gunasekaran Baskaran They can also ask to keep 01-01-15 and remove 01-01-14. This question is more around whether using a Release Toggle would work in this type of situation.