How to define Form Actions

Form Actions are triggered from within a Form, for example the Incident Form.

Therefore, to define an Action you will need to access the Form Designer and select the relevant Form.

From within the Form Designer, click on Actions to open the Action Designer.

This Action Designer page contains ALL the actions which are triggered from a given Form.

Order in which Form Actions are triggered

The order in which Actions are triggered is determined by a range of factors.

1. Action Type

   The application has two types of Actions, which run either:

   • BEFORE the record is saved
     • Set Value
   • AFTER the record is saved, for example:
     • Email
     • System Notification
     • DB File transfer
     • Save to PDF
     • REST Callout
2. Order of the Action Groups

   Within each Action Type, you can define the Order in which Action Groups are being fired.

   The order can be adjusted at any time by using the 'Up' or 'Down' arrows.

   The primary use case for this is around controlling the order that Rest Callout actions fire. E.g. so that you can fire a GET callout first, save the results locally, and then use that saved data as part of the next POST call.

   NOTE: If the Actions within an Action Group are a mix of BEFORE and AFTER Save Actions, then the BEFORE Save Action will always be fired prior the AFTER save Actions.

Workflow Status

The Workflow status of the record will be reflected after save, depending on the condition that matches. For more information refer to Workflow Status.