Return User Error Action
Use the Return User Error action to display an error message to users. Use this action with field or record validation to prevent the user from saving the record with invalid data. To create the Return User Error action, create validation conditions on the action definition.
How the error message displays depends on the type of trigger used in the action definition:
Trigger Type |
Use Case |
Error Message Format |
---|---|---|
Before Record Load |
Validate record form field values before the record loads in the browser. |
Displays as browser page with a Go Back button. |
Any client trigger |
Validate record form field values as user interacts with the record form fields. |
Displays as popup window with an OK button. |
Before Record Submit |
Validate record form field values after the user clicks Save. |
Displays as browser page with a Go Back button. |
The following screenshot shows the Return User Error action on a client trigger:

The following screenshot shows the Return User Error action on a server trigger:

Workflow definitions require a trigger configuration that initiates the workflow, executes an action within a workflow or transitions the workflow from one state to another.
-
For more information about which workflow triggers the Return User Error action supports, see Workflow Triggers Quick Reference.
-
To understand when different workflow triggers execute and which trigger you should use, see Workflow Triggers and the SuiteFlow Trigger Execution Model.
Return User Error Action Parameters
The following table describes the Return User Error action parameters:
Parameter |
Description |
---|---|
Text |
The error message text. If the Multi-Language feature is enabled on your account, you can add text translations. For more information, see Configuring Multiple Languages |
For more information about adding actions to a workflow, including common action properties and conditions, see Action Conditions and Creating an Action.
Return User Error Action Guidelines
Use the following guidelines when working with the Return User Error action.
-
It is a better user experience to use client side triggers to detect errors on individual fields as they are entered, rather than server side triggers on save. With server side triggers, the user must re-enter all data since the last successful save.
-
The Return User Error action is not available on a Before Record Load trigger for a time entry record.
-
When the user clicks Go Back, all field values entered since the record was last saved are removed.