Home → Using LincDoc 3.1+ → Actions → Using Event Actions
Events occur on both a field and eForm basis. Each event can be configured to perform one or more actions. These actions may also be subject to a rule evaluation or condition.
Proceed to one of the following topics for more information:
The following events are available in LincDoc:
Event | Type | Description |
After declining | Field/eForm | Executes after any signature field is specifically declined by a user (not signed voluntarily). |
After generate | ||
After signing | Field/eForm | Executes after any signature field is signed by a user. |
After sync signing | ||
After viewing document | eForm | Executes when the document viewer is exiting. |
Before applying decline | Field/eForm | Executes immediately before the After declining event. It verifies that the signature date value is automatically set, even if a signature is declined, since this date value is required with most signature fields. |
Before applying signature | Field/eForm | Executes immediately before the After signing event. It verifies that the signature date value is automatically set, since this date value is required with most signature fields. |
On blur | Field | Executes when the user exits a field and the field loses focus. |
On change | Field | Executes when the value of a field changes. |
On load | Field/eForm | Executes when the data entry form is loaded into a user's browser. Also executes for a pre-existing form that a second user may open for editing via another method (such as an email link). |
On sync | eForm | Executes when the data is synchronized to the server in LincDoc's mobile implementation. |
The method for accessing the Events list is the same as the one used to access the Buttons list, since they are displayed on the same screen.
For more information, see Accessing the Buttons List.
You cannot edit events using the standard LincDoc interface.
If you need to edit a standard event, contact Technical Support for assistance.
Once you have determined which event you want to use, you can add an action to the specific event. This action will be executed when the corresponding event occurs.
For more information, see Applying an Action to a Button or Event.
Once you have determined which event you want to use, you can apply a rule to the event. This rule is then evaluated, and any associated actions are executed, when the corresponding event occurs in your form.
For more information on applying a rule, see Applying an Action to a Button or Event.
For more information on rules themselves, see About Rules.
You can add an event using the Add Event button at the top of the Actions tab.
Note: This button is only available on the Actions tab.
This type of event is only fired when adding an email link into a workflow. An email is sent and opened by the recipient, and it contains a link. When the link clicked, this newly added event is executed.
The use of added (custom) events is mostly for advanced users. For more information, contact Technical Support.
Example:
Typically, an email action is executed from a form's "Submit" button. Within the associated email, a standard "link" expression (written in DRAT) is present. You email action's body text may look similar to the following:
Hello Mr. <<lastName>>, we have a document for you to review: please use this link to view your document: <<:doc-link:edit>>
To execute a custom event, you would use <<:doc-link:edit:::myCustomEvent>> instead of <<:doc-link:edit>>. (Note that the double colons are necessary for the custom event syntax)
You cannot delete an actual event from the Events list. However, you can delete all of the event's associated actions or rules, which means that the event will not affect your form (it will not be executed, even though it is present in the Events list).
For more information, see Deleting an Applied Action or Event.