Posted: 3 Oct 2018 15:39 EDT Last activity: 30 Nov 2018 14:06 EST
Ruleset not showing up in Localization Wizard
I have my application ruleset name as “RULESETNAME_XX” and when I run the wizard, Pega is not showing this ruleset in the list rulesets to select for localization. I am thinking Pega may be skipping this ruleset by assuming the 2 chars (_XX) as localization ruleset. Can someone suggest how this can be addressed.
***Updated by moderator: Lochan to update platform capability***
I reviewed the behavior on my 7.3.1 system. You are right about the ruleset being filtered because it is treated as a localization ruleset. The pzAddApplicationAndRulesetsToStack activity has the following when condition in one of the loops and exits the iteration to add that ruleset if it is true.
I am not suggesting to add any code. I was pointing out the code that looks like it prevents that ruleset from being displayed. My suggestion is to try adding the ruleset on the access group as a production ruleset and then select it in the 'Include field value from other rulesets' section.
Posted: 2 years ago
Updated: 2 years ago
Posted: 9 Oct 2018 5:49 EDT Updated: 9 Oct 2018 8:57 EDT
Just to clarify - there is no HFIX-41580. This is not a formal hotfix developed for this scenario because this was not assessed as a BUG in the product.
What was suggested to the customer and confirmed working in the previous SR involving this issue was the below -
"When rule in the following rules (PegaAccel-Task-Localize. pzAddApplicationAndRulesetsToStack as well as PegaAccel-Task-Localize.AcquireHTMLParagraphs) were commented via privatecheckout before running the localization wizard to allow developer's ruleset that had a suffix of underscore '_'. "
So you will need to apply this solution first and let us know your feedback.
Thanks for the quick fix and I thought of this solution but not sure how Pega behaves at run time when French ruleset is created for the rulesets (Rulesetname_xx) like Rulesetname_xx_fr with this solution. I am doubtful this french ruleset will be recognized by Pega at run time.
Hence if Pega can provide any fix, would be helpful.
Hey Krishna, the solution provided was tried out and confirmed by a customer that is why I offered the same to you to unblock you from your development blockers, since it is a private checkout you should try and give this a shot. We can check with Engineering if they don't mind giving the same fix as a hotfix but like I mentioned before it was not categorized as a BUG in the previous scenario so I'm not sure of the outcome this time around. Thanks.
Can one of the Community Moderators (Marissa), for its worth, please spin off an enhancement request to accommodate this requirement in the product itself for any customer in a future release of Pega. You can mention the SE# mentioned in this post. Thanks.