Skip to main content


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

This content has been archived and is no longer being updated.

Links may not function; however, this content may be relevant to outdated versions of the product.

Customizing the Decision Data rule form

Updated on April 5, 2022

If you use a custom form, you must manually maintain the associated section rule, which renders the decision data form. When you finish customizing the form, save the decision data rule.

The pyEditElements section @baseclass must be manually specialized by class and ruleset, and saved under the same class as that of pyEditElemen t. This section defines the items themselves (for example, proposition and description). This section includes the standard add and delete item actions, and operates on the basis of the pyEditElement flow action to register the new parameters.

The data source that is used in the repeating grid layout of the pyEditElements section is the pxResults property. On the Pages & Classes tab, you must define the pxResults page.

  1. In Dev Studio, click RecordsDecisionDecision Data.
  2. From the list of Decision Data rule instances, click the record that you want to edit.
  3. Click the Form tab.
  4. In the Form options section, click Use custom form.
  5. Confirm that you want to switch to the custom form by clicking Submit.
    Note: You can switch back to the default form by clicking Use generated form.
  6. Click Customize form to edit the layout of the Decision Data rule instance form.
  7. Edit the form so that it reflects your business preferences or objectives.
  8. Click Save after you finish customizing the rule form.

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.

Pega.com is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us