Closed
Running Segments
In PM 8.2, once you lock a ruleset (to package and deploy to another environment) in which you create a segment, the run button disappears. Is this intended? And if so, why?
This content is closed to future replies and is no longer being maintained or updated.
Links may no longer function. If you have a similar request, please write a new post.
In PM 8.2, once you lock a ruleset (to package and deploy to another environment) in which you create a segment, the run button disappears. Is this intended? And if so, why?
I saw you asked the same question before for 7.3.1 PM where SME already answered. PM does require an unlocked artifact ruleset, did you lock that ruleset? Would like to try your steps locally.
It is Pega best practice to lock a ruleset before packaging and deploying to another environment (from DEV to TEST say). It make no sense that once deployed that I should need to either do a save as to an open ruleset or have to unlock the the ruleset.
Please advise on how a Segment should be deployed to another environment; the user guide simply states that you should use the Application Packaging Wizard, which calls out if you have open rulesets.
Also, the previous SME stated that:
"This is not expected behavior. The Run button should still be available even if the ruleset is locked."
Question Solved
Question
Question
Question
Question
Question Solved
Question
Question
Question
Question
Pega Collaboration Center has detected you are using a browser which may prevent you from experiencing the site as intended. To improve your experience, please update your browser.