Quik! Forms Automation

The main purpose of this document is to provide guidance on designing forms that are ideally suited for forms automation processes. The Quik! Forms Automation processes make use of all the features described in forms automation within this reference guide. For your reference, the Quik! Forms Automation solution is discussed below in order to provide a context for how forms are ideally automated and why the Quik! Tips throughout this document are well-founded and suited to a forms automation environment.

Where Automation Occurs

QUIK! TIP: Perform server-side automation whenever possible because programming forms directly is costly and subject to the changing design of the form. When it comes to automating the form, there are at least three areas in which the automation can occur: server-side, document level, and field level. Where the automation occurs depends on the type of automation required.

Server Side Automation

Automation that can occur on a back-office server is considered server-side automation. This means that the form and form data is either processed on a server before or after the form is generated. Ifthe data is processed after the form is generated and used by the user, then the user must trigger an
event to submit the data to the back-office server in order to start the process. Once the back-office
process is run, the data can be sent back to the form (in real-time) to update it with new information
(including hiding and displaying new data and document objects).