Considerations for Configuring Rules in Table Component

Note the following considerations when you configure SQL rules and/or UI rules for table component:

  • Set Process subsequent rules? option to Yes or No for different validations.

  • Dependencies field is not required for Apply on creation rule event, but required for Apply on field change rule event.

  • Dependencies field supports the following validations:

    • Text field

    • Auto-complete list

    • Drop-down list

    • Date field (short, medium, and long)

  • Results field supports the following validations:

    • Text field

    • Text area

    • Auto-complete list

    • Drop-down list

    • Radio buttons (yes/no)

    • Date field (short, medium, and long)

    • Web Address (URL)

    • Link

  • UI rules support the following JavaScript functions:

    • setFieldRequired ()

    • setFieldEditable ()

    • setFieldVisible ()

    • showMessage ()

    • setFieldStyle ()

      Note: To modify CSS styles, locate and access the RequestRulesUserCSS.css file in the following directory: /opt/ppm/[instance name]/server/[instance name]/deploy/itg.war/web/knta/crt/css/.

    For more information about these JavaScript functions, see Predefined JavaScript Functions (Advanced Rules Only) or access the Request Rules JavaScript Function Help by clicking the icon next to the Logic field in Rules window of the Validations Workbench.

  • You can set table component as a dependency to trigger request type rules.

  • When using SQL rule(s) on text field with Apply on creation rule event, make sure not to use strings "~^~^~" and/or "~&~&~" in any text field as they are reserved.

  • When SQL rule(s) with Apply on creation rule event are triggered to override default value of a table component column, the default value may still display for a very short period of time (say 0.5 second) due to server speed.