| Section | |||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
|
...
The rule validator described in detail below will help you detect this potential rule bug by displaying a validation error such as the one shown below. This form has two controls named HorseName.
| Warning |
|---|
does not currently support control names with unicode international characters in rules. The rule validation (in edit mode) will fail if any control has a name containing unicode international characters. This applies to any control in the form. At runtime, rule execution will fail if the rule attempts to access or change any property of a control named using international unicode characters. In the debug console it will report that the identifier/reference is not found. The only way to fix this is to rename the controls to ascii only. Visible control labels with unicode chars are fully supported.Use English alphabet characters only. 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. |
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:
...