How can i restrict the application pick my private rules?
I know the private ruleset ie:OperatorName, gets added to the top of the ruleset stack.
Is there a way to tell PEGA to skip any rules in the private ruleset?
I can make the availability of the rule in private to "Not Availablt" to make it skip.
But I have lot of rules that i need to change that way...And doing so for testing purpose often is tideous.
I know this can be achieved with another operator ID for whom the Application will pick only the checked in rules.
But is there a way to achieve what I mentioned by any other way?
Any OOTB changes, ect???
***Updated by moderator: Lochan to update platform capability***
Pegasystems Inc.
GB
I don't think that there is a way to do this OOTB. The whole point of private checkout is to be able to test changes only as the specific user that you are logged in with. What is the requirement here? I guess that you want to use the same user to edit rules in private checkout, but continue to use the same user to use the system with the original functionality? I would say that using another user would be the way to go really.
Do you need to keep the rules checked out at all? You can use the checked out rules bulk actions functionality to discard all the rules that you have checked out if you don't want them checked out.
Otherwise I think marking them as unavailable is probably the way to do it, but you would need to be careful that they don't accidentally get checked in as unavailable. You could create an activity to loop through the checked out rules and set pyRuleAvailability to "No" as a custom bulk action.
How about looking at branch functionality? If you had a development branch then you could use the same user and switch between the regular application and a dev version of the application with branches for development.