New toplevel property not available for existing propositions
Hello,
While adding new proposition properties at top level we found that the new properties are not automatically added to the generated form for existing issue/groups. We are able to manually add the property to each issue/group combination, but this is quite laborious.
Is there any way to automatically propagate the new properties to existing issue/groups?
Context: We are using versioned propositions in 7.31
***Updated by moderator: Lochan to add Categories; tag SR***
Accepted Solution
Pega Systems Inc.
IN
As per the product specialist, the design, Rule architecture is behaving correctly, which means Updates in the Custom form section will not replicate in DD rule. As client has huge rule list to update, the provided utility can solve the problem.
What does this Utility do:
As per the product specialist, the design, Rule architecture is behaving correctly, which means Updates in the Custom form section will not replicate in DD rule. As client has huge rule list to update, the provided utility can solve the problem.
What does this Utility do:
- Will browse the DD rules as per the class name given. 2.Filters the Browsed rule list by checking form option and Prepares the filtered DD rule list to Update.
- Opens the property rule according to the parameter values.
- Check out the DD rule and Update it with property and Will check in the Rule.
Prerequisites for Using the utility:
All DD rules need to be updated should be in Unlocked rule set and Should be check out enabled.
Make sure that Property will not be duplicated in the form tab of DD rule.
Steps to perform the local fix:
- Import the "SE38412Fix" Jar using application import.
- Open the Application rule and Add SE38412 rule set to the appilcation. 3.Open AdjustDDConfig activity and run it. 4.Need to pass three parameters a. Class name(Can be Sr class or Issue class or, Group class it self). b.Property name, c. Applies to class of Property.
Pegasystems Inc.
IN
Hi ,
Thank you for posting your query in PSC.
Even I could observe the same thing [i.e. Added a top level property, in Decisioning-->Hirarchy Landing page, , if we open the Form tab of the DecisionData [i.e Group] , I dont see the new property that I had added], in our inhouse environments.
This is an expected behaviour.It will not be added to the Form tab automatically. We do not expect the properties added at the top level be added to all the groups.Only the relevant properties to be added to each group.All the groups need not have the same properties.
Though ,if you create a new group post creating the property, it will have this property, but not existing ones.
Thanks
Sibani Saidarsini
Pegasystems Inc.
IN
Hi Again,
For your question "We are able to manually add the property to each issue/group combination, but this is quite laborious."-->
You can convert the Decision Data rule to Use custom form and include a common section to all the group DD rules.And Include these new properties in the common section and it will reflect it all rules.
Regards
Sibani Saidarsini
A Dutch Bank
NL
Hi Sibani,
What are we doing wrong? Creating a subsection and dragging and dropping did not work. It stays there OK, but when importing the CSV it fails to load it.
We also tried to delete the generated pyEditElement and save a similar one at the SR superclass, but it did not work either with uploading the CSV.
Some of these worked OK with the manual editing via form (I think the first one), but we use CSVs here.
Regards, Andre'
Updated: 19 Apr 2018 7:50 EDT
Eclat Prime
IN
Hi @Sibani_GCS
Could please refer SE-38412, which raised on similar lines.
Looks like we do have a fix for you to achieve your requirement. Please create an SR with Pega Support and reference this post. Do let us know the SR# here for our reference.
Thanks!
Accepted Solution
Pega Systems Inc.
IN
As per the product specialist, the design, Rule architecture is behaving correctly, which means Updates in the Custom form section will not replicate in DD rule. As client has huge rule list to update, the provided utility can solve the problem.
What does this Utility do:
As per the product specialist, the design, Rule architecture is behaving correctly, which means Updates in the Custom form section will not replicate in DD rule. As client has huge rule list to update, the provided utility can solve the problem.
What does this Utility do:
- Will browse the DD rules as per the class name given. 2.Filters the Browsed rule list by checking form option and Prepares the filtered DD rule list to Update.
- Opens the property rule according to the parameter values.
- Check out the DD rule and Update it with property and Will check in the Rule.
Prerequisites for Using the utility:
All DD rules need to be updated should be in Unlocked rule set and Should be check out enabled.
Make sure that Property will not be duplicated in the form tab of DD rule.
Steps to perform the local fix:
- Import the "SE38412Fix" Jar using application import.
- Open the Application rule and Add SE38412 rule set to the appilcation. 3.Open AdjustDDConfig activity and run it. 4.Need to pass three parameters a. Class name(Can be Sr class or Issue class or, Group class it self). b.Property name, c. Applies to class of Property.