Question
Localization ruleset branching
Hi all,
we switch now in my current project to use branching. The question I have refers to localization rulesets. We create at the moment for example field values directly in the localization rulesets (using an admin activity).
As we switch now to use branching, I don't see any possibility to create the localized branch rulesets. Only the non localized rulsets are available to be created in a branch.
How do you do this? Is there a possibility to create the localized branch rulesets? Or do you directly created them in the trunk?
Thanks and Best, Marcel
***Edited by Moderator Marissa to update platform capability tags****
Hello Vaspoz, to answer your questions:
1. As only the localized rulesets of my current operator language are in my ruleset stack (e.g. MYRULESET_en), we use an admin activity to create the rulesets in all (also not available) localized rulsets. So it has parameter and is creating a page which is the new field value and then saving the object.
2. What I mean is, if I go to my application and select "Create branch ruleset" and I want to select the "RuleSet to Branch", then only the non localized rulesets are available in this dropdown. So even the "_en" localized rulsets which are in my ruleset stack are not available here.
My idea was to created those manually before as then the admin activity we wrote would work again.
When you go to "my application", before selecting the "RuleSet to Branch", can you see those "_en" localized rulesets?
No, I can't see them. I hope, I looked at the right spot, as we are using Pega 7.1.9 and I assume that the labels are different.
1. It's correct that you're creating field values in localized RS. But what is the "admin activity"?
2. what do you mean by "Only the non localized rs are available to be created in a branch"? Rulesets are (normally) not created in a branch, but they already exist and they are branched.
3. localized RS are the same as normal rulesets. You can make a branch from them. The only requirement - the ruleset must be in your ruleset stack.