These actions act on the form itself - saving it, moving around it, and controlling how a sequence of actions runs.

Perform E-form Action

Does what one of the form's own buttons does.

Action - Which one:

  • Save - Saves the form.
  • Save for Later - Saves a partly completed form so the user can come back to it.
  • Cancel - Abandons the form.
  • Reset - Returns every field to the value it started with.
  • Print - Prints the form.
  • Show all Pages - Puts every page on screen at once, which is how a multi-page form is printed in full.
  • Save with Workflow - Saves and clicks a workflow button in one step.


Workflow Button Name - Shown for Save with Workflow: the name of the workflow button to click, such as Approve or Reject. This is what lets a form's own button stand in for a workflow decision, so the user makes one click instead of saving and then answering a prompt.


Go To E-form Page

Moves to a page of the form.


Page Number - Which page, counting from 1. {FieldName} references work here, so the page can be worked out rather than fixed.


Note that pages hidden by a condition still count in the numbering. Inserting a page shifts every page after it, so check any Go To Page actions after reordering a form.


Refresh Form Data

Reloads the form's data from the record. Use it after something has changed the record behind the form - an Action Set, a workflow step, an upload - so the user sees the current values rather than what was there when the form opened. It takes no settings.


Run Action Set

Runs a named Action Set on the server. This is the bridge from the form to everything the system can do: creating records, sending email, calling other systems, running any workflow action.

Action Set - The Action Set to run.


Fields to Use - The names of the fields, one per line, whose values are sent into it. The alias:name form sends a field's value under a different name, which is useful when the Action Set expects names the form does not use.


Send Record and Document - Sends the current record and document into the Action Set as the active objects.


Requires workflow to be licensed; without it the action does not appear.


Because it makes a round trip to the server, put a Show/Hide Please Wait around it in any sequence where the user might otherwise wonder whether their click registered.


Show/Hide Please Wait

Shows or hides a waiting message. Only available inside a Multi-Action field.


Title and Message - The wording shown.


It must be turned off again by a later action in the same list. A sequence that shows a Please Wait and never hides it leaves the form stuck behind it.


Confirm / Stop Actions

Asks the user to confirm before going on. If they decline, the rest of the list does not run. Only available inside a Multi-Action field.


Confirmation Prompt - The question to ask. Write it so the consequence is clear - "Delete these three documents?" rather than "Are you sure?".


Put it first in any sequence that changes or removes data. Placed halfway down, it asks the user to confirm something that has already partly happened.


Validate Fields

Checks the form and stops the sequence if anything is wrong. Only available inside a Multi-Action field.


Message - The message shown when validation fails.


This applies the form's own rules - required fields, double entry, minimum and maximum values, regular expressions. Put it at the top of any sequence that saves or submits, so a form that is not ready never reaches the server.