Skip to main content

         This documentation site is for previous versions. Visit our new documentation site for current releases.      

Edits to the rule form layout are not propagated

Updated on July 5, 2022

You customized the layout of a Decision Data rule form through the pyEditElement section (either by adding or removing properties from the layout) and saved your changes. However, you do not see your changes in the rules that reference that decision data rule.


For example, you added a new property in a layout of a Proposition rule form and saved that rule, but the change is not reflected in the strategy rule that imports the data for that proposition.

Note: This condition applies only to decision data rules with customized rule forms.


This problem might have the following causes:

  • You added a property to the layout of the decision data rule, but this property is missing from the Form tab of the decision data rule.
  • You removed a property from the layout of a decision data rule, but the Form tab of the decision data rule still contains that property.

To correct this problem, you need to add or remove properties on the Form tab of the decision data rule.

Editing the layout on a Decision Data rule form
A dynamic layout on the rule form is highlighted and contains the Customer ID, Payment History, py Name, and Churn fields.


  1. In the navigation pane of Dev Studio, click Records.
  2. Expand the Decision category, and then click Decision Data.
  3. Select a decision data rule to edit.
  4. Click the Form tab.
  5. To unlock editing, click Check out.
  6. Perform one of the following actions:
    Add a property
    1. In the Form fields section, click Add field.
    2. Click the Down Arrow key and select a property from the list.
    Delete a propertyIn the Actions column, click the Trash can icon.
    Editing the Form tab on a Decision Data rule form
    The Form tab contains recently added fields: Churn, py Name, and Customer ID.
  7. Click Save.
  8. Check in the rule:
    1. Click Check in.
    2. Enter check-in comments, and then click Check in.
  • Previous topic Edits on the Form tab are not reflected on the Data tab
  • Next topic pyEditElement error: The code for the static initializer is exceeding the 65535 bytes limit

Have a question? Get answers now.

Visit the Support Center to ask questions, engage in discussions, share ideas, and help others.

Did you find this content helpful?

Want to help us improve this content?

We'd prefer it if you saw us at our best. is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us