| Section | |||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
|
...
| Note |
|---|
Dropdown, radio and checkbox control values are text types. So you must quote values when performing comparison operations: Ex: if (Building.value === 1) will evaluate to true. You must quote the 1 as in if (Building.value === '1') to make the one a text type. |
Control Control Name
Rules usually need to reference form controls. You assign a control a name using the control's name property.
...
| Warning |
|---|
Use English alphabet characters only when naming controls. For example, controls named with ó as in Póliza may cause issues when the control is used in a business rule and with submission data. |
JavaScript Keywords and Reserved Words
It is highly recommended that you avoid using JavaScript keywords and Reserved Words as control names. For Example, a section named New in your form will cause rule validation errors if explicitly referenced in a rule. The only way to fix this is to change the name of the control. Here is a partial list of JavaScript keywords and Reserved Words to avoid:
| Section | |||||
|---|---|---|---|---|---|
|
Accessing Control Properties
...
- form.load : This property is true when the form is first loading. It is useful for setting default values via rules that you need to be set before the user starts interacting with the form. This also holds true for flows. This property is true when each step of a workflow is first loading.
- form.unload : This property is true when users click the form's submit button. It is useful for setting control values just prior to the execution of the form's Doc Actions and Form Actions. This also holds true for flows. This property is true when the user clicks the continue button for each workflow step.
- form.positionUpdated : This property is used for the Geo location feature. You can fire a rule using this special identifier every time the position is updated.
Examples of identifiers used in rules are:
...