Best practice to handle last minute issue in QA
Client often finds last minute issue in QA and the item is not ready for upcoming release for the week.
Currenlty they unlock the ruleset in DEV and mark all rules "Not available" and redeploy the same ruleset version to QA. I think this is not a best practice.
Any recommendation or best practice to handle this situation?
Client uses Pega Deployment Manager for deployment.
Pegasystems Inc.
US
Hi @Will Cho!
Did you see that our current Ask the Expert session is on Deployment Manager?
I'd ask your question there and our experts can help you!
Thanks!
Pegasystems Inc.
US
@MarissaRogers Hi thank you for the information. Do I just post a new question to the discussion thread?
Updated: 14 Apr 2022 3:28 EDT
Pegasystems Inc.
IN
Hello @Will Cho
Yes! Please post the question on the discussion thread of Ask the Expert session - Deployment Manager post
Thank you!
Anamata
NL
@Will Cho Has your team considered using feature toggles when developing new features? (https://community.pega.com/knowledgebase/release-note/enable-and-disable-functionality-feature-toggles)
Pegasystems Inc.
US
@Michel Kraaij Thanks for the idea. Does the Release Toggle requires the target components (like button, activity step) to reference the When rule generated in the Toggle manager?
Updated: 14 Apr 2022 3:40 EDT
Anamata
NL
@Will ChoYes, it does. It might not be a solution for this particular "already deployed" situation, but you might want to consider it for future situations.
Just a quick question. Why do they open up the existing ruleset version and make the changes? Why not create a new ruleset version on top of the "buggy" version, duplicate the rules and disable it in that version?
Pegasystems Inc.
US
@Michel Kraaij i don't know. I was just brought into as a new tech lead on DevOps and this was how they were doing before. I explained that unlocking rulesets in DEV to changes rules that were previously deployed to QA is risky and not best practice. So here i'm trying to find a new solution before deprecating the old practice.
I also suggested to open up a new version and withdraw the rules. One caveat is that this should work for new rules, but for existing rules it can also withdraw all rules in the same ruleset and can break the application.
If you see any alternative solution, that would be appreciated.