Form Actions

The following section will explain what Form Actions are, and how you can define them in the Web Application.

Why do I need Form Actions, and what are they?

Form Actions are used to perform certain 'tasks' in the Web Application. They are one of the central components of the system, and for example are needed to:

• Send emails after a record has been created or modified.
  For example: once an Incident has been reported, the Manager of the affected Department needs to be notified.
• Set the Value of a field.
  For example, when creating a new Action and the Action Priority is 'Urgent', set the "Inform Manager about this Action" to YES.

What is required to define Form Actions?

Before you start defining Form Actions in the Web Application, you first will need to have analyzed and identified which Actions are necessary to meet your requirements. Once this is done, you will need to

• define the rule, or condition, which will actually trigger each Action.
• configure the Action itself, e.g. define the email details.

Once I have defined an Form Action, when will it be available to the End Users?

Every change made to a Form, being:

• Changes to the Form itself (adding/removing fields, changing labels etc.)
• Making changes to Actions, Validations and Default Values will require:
  • a Publish
  • a Tomcat restart.