Throw Error trigger

The purpose of the Throw Error trigger is to allow the user to specify a custom error message to be displayed when something goes wrong. The error can be generic or linked to a specific field. Also, this trigger can be used to start an error transaction when a user-defined condition is not met.

This trigger is accessible from the Application panel, Server Behaviors -> + -> MX Kollection -> Forms -> Throw Error.

The user interface has two tabs. The Basic tab alone is sufficient in order to define the error message and eventually the associated transaction field, while the Advanced is only required in order to alter the list of transactions to which the trigger is registered, or the trigger's properties. Directions about the tabs correct configuration are given below.

 

To set the dialog box options for the first tab, follow the next steps:

  1. In the Error message textarea enter the custom message to be displayed when the error occurs. This message will be displayed on top of the page. You can use the InterAKT Dynamic Data (the lighting bolt icon) to build the generic error message.
  2. In the Transaction field drop-down menu select the field which will have the error message associated to and get highlighted. If this field is left to None, then the error message will be displayed whenever the transaction fails, without highlighting any particular field.
  3. In the Field error message text box, enter the error message that will be displayed next to the field's page element. You can also use the InterAKT Dynamic Data to build the specific error message.

  4. The three buttons in the top right corner of the interface offer you the next functionalities:
    · Click OK when you are done configuring the trigger.
    · Click Cancel to exit without applying the new settings.
    · The Help button opens this help page.
    These buttons are common to both tabs of the Throw Error trigger.

  5. Click on the Advanced tab to continue with configuring the trigger.
 

 

For instructions on completing this step, see the Advanced tab. The difference is that for the Throw Error trigger, the Type drop-down menu is not read-only and it gives you the opportunity to choose the trigger type. By default, it is set to BEFORE as it should execute before the transaction takes place. Also, the Priority is by default set to 50.