I have a question about own defined localization rulesets. I want to skim them but when using the skim feature the localization rulesets are not showed. This looks like obvious behavior as the are not explicit defined in the application definition. Also same kind behavior (not showed) in the pulldown selection when try to copy/merge them.
Of course can I temporary add the localization ruleset (_nl in our case) to the application definition, but I assume this shouldn't be the way.
Can someone tell me what should be the correct way to skim a localization ruleset?
***Edited by Moderator Marissa to update platform capability tags****
Thank for your reply. But your are talking about the Delete Wizard. I didn't mentioned this one by purpose as the localization rulesets is showed in the pull down menu in the Delete Wizard. This is showed even without explicit defining the localization ruleset in the application definition. So why is it showed in the Delete Wizard but not in the copy/merge or Skim Wizard?
You are right. The delete wizard is different than Copy/Merge & Skim wizards, it is populating the rulesets list irrespective of the application.
I would assume it is different, as Copy/Merge & Skim requires managing existing rulesets & it's versioned, unlike delete wizard which just does delete. The under the hood process for skimming perform several checks w.r.t rule availability which might require application context to keep in view to move/flag certain rules to newer ruleset versions. But, I'm not entirely sure why it's different.
We don't usually add localisation rulesets in application rule-form. The rules in those rulesets get picked automatically based on the locale data.
It seems to me that localization rulesets are not purposefully shown for skimming. May be running the localization wizard on skimmed rulesets(suppose Test:01-03) would be same as skimming localization rulesets.