Triggers
Event Triggers are provided by Quask WorkFlow that allow integrators and developers to hook into form events. Triggers can be written in:
- JavaScript
- VBScript
- .NET (VB or C#)
- COM Object
The following events currently support triggers and show some possible simple uses.
Trigger |
|
Usage Example |
Form Deploy |
|
Add form name to a list in your system. |
Form Request |
|
Login authentication. |
Form Load |
|
Put data from your system into specific form fields. |
Form Submit |
|
Intercept data as it is submitted and store it in your database. |
Form Recall |
|
Remove the form from a list in your system. |
|
|
eForms Management & Storage
Quask WorkFlow is an excellent forms repository. It can store active and archived forms and link these to other systems via a simple Form Instance ID.
You can create Form Instances via the API. A Form Instance is a 16 character string that includes a large random number to prevent fraudulent submissions. This uniquely identifies an Instance of one form type.
http://www.yourserver.com/InstID=
1778AF84CD2549AF
This sample URL would always display a unique Form Instance. Your systems would simply need to store the Instance ID to reference this form at any point in the future.
Using the API and the Instance ID you can also access specific fields within that Form Instance. |
Data Tables
By default, Quask WorkFlow has a single table that stores data in XML format for all forms.
It can optionally create a dedicated data table for a form so that 3rd party applications can interact with this table. |
|
The Quask WorkFlow API
The Quask WorkFlow API allows you to access all system properties such as:
- Forms
- Form Fields
- Response Data
- User Information
This allows you to get or set data from any response as you need it. Using this approach you can update form fields from your own application without the form ever needing to be loaded. |
