Action Checks

Action Checks allow you to add custom validations on manager layouts before data is saved to the database. This is useful when a screen has conditional mandatory fields — for example, requiring either a pre-existing location XID or a full set of address fields, but not both.

Example Scenario:

A custom manager layout allows users to enter PO details. The destination can be set by selecting an existing Location XID, or by entering a new address (address line 1, zip code, etc.) using custom attributes. The validation must ensure that at least one of these two options is populated before the record is saved.

Configuration Steps:

Manage User Access > Enter 'Action Checks' as User Access Type > Enter the User Role > Click 'Edit User Access'

In the screen, configure the following fields:

Audit Action ID: Covers all standard user actions. For this scenario, select ADD ORDER BASE as the audit action.

Allow Condition: The SQL condition that must pass in order for the error NOT to display. In the example below, the condition allows the save to proceed if source_location_gid <> 'DEFAULT' OR the custom attribute OB.Attribute2 (Address Line 1) is not null — meaning at least one destination detail is present.

Cause: A label that provides the error reason text shown to the user when the validation fails. Set the label Type to ERROR.

Post Action Check: When checked, validation runs after the action executes but before data is committed to the database. For Delete Record validations, this should be unchecked. You can also add the same Audit Action twice — once with Post Action Check enabled and once without — to cover both pre- and post-action scenarios.

Testing:

If the user tries to save a PO without entering either destination detail, the following error is displayed:

Questions & Discussion

Have a question about this topic? Post it below using your GitHub account. Comments are visible to everyone and help other OTM consultants with the same question.