Custom Rules picking RuleFormLegacy Harness instead of Ruleform
We are creating custom rule type for a specific requirement . There we created a new class ( inherits from Rule- ) & corresponding RuleForm Harness . This new rule type is visible in the landing pages under the defined category , but while creating the actual rule , RuleFormLegacy harness is getting loaded instead of RuleForm ( same issue mentioned as part of https://collaborate.pega.com/question/custom-rules-picking-ruleformlegacy-harness-instead-ruleform : SA-17487 ) . Is there any local change (or) hotfix available for this issue ? We are using pega 7.2
***Moderator Edit: Vidyaranjan| Updated Categories***
Accepted Solution
DCS
AU
Thanks Santanu . It worked fine after saving the RuleForm harness from any OOB class into the newly created class & moving the required dependent section rules ( Like RuleFormLayout) . Seems when I used manually created Harness rule instead of RuleForm harness , the required dependent rules to render ruleform were missing & hence it showed XML .
Pegasystems Inc.
IN
Hi
you need to have a section named RuleFormLayout at the custom class. This ideally would be copied from @baseclass.RuleFormLayout.
Accepted Solution
DCS
AU
Thanks Santanu . It worked fine after saving the RuleForm harness from any OOB class into the newly created class & moving the required dependent section rules ( Like RuleFormLayout) . Seems when I used manually created Harness rule instead of RuleForm harness , the required dependent rules to render ruleform were missing & hence it showed XML .
Pegasystems Inc.
IN
Hi Vamseek,
Yes i could see the similar behaviour inhouse .
Could observe the RuleFormLegacy has been rendering .
Now on performing the localchange suggested by santanu : i.e save-as ootb RuleFormLayout of @baseclass into the custom class Rule-Obj-Mappings , resolves the issue . Refer the below screenshot .
Hi Vamseek,
Yes i could see the similar behaviour inhouse .
Could observe the RuleFormLegacy has been rendering .
Now on performing the localchange suggested by santanu : i.e save-as ootb RuleFormLayout of @baseclass into the custom class Rule-Obj-Mappings , resolves the issue . Refer the below screenshot .
