Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  • Description: A description field to provide an identifying name for this validation routine.
  • Table Name: The Database table name to which this validation is be applied.
  • Table Record: The specific RECID number that should be validated. Leave this blank to apply the validation to all records.
  • Action: Save or Delete options specifying the table action that should be validated.

CAUTION: When creating Custom Validations, it is better to have a handful of large Custom Logic than it is to have numerous amounts of short Custom Logics defined for your Organizations Custom Validations. This is because as the number of Custome Validations that trigger on the same form increases, application performance begins to suffer, and can eventually start risking application timeouts. It is also important to ensure the same Custom Logic is not running multiple times on the same records as this also will reduce application performance if a large number of records undergo this same change at once, such as the case with any Validations that might trigger from a Service Desk Action.

Logic tab

Example of Custom Validation Form

The Logic tab is where the Custom Logic can be written and reviewed.

...