System administrators can configure rules to produce custom messages for fields that only display for Hard and Soft errors.
When rules trigger, if a custom error is configured, the custom error is displayed. If no custom error is configured, the standard system message is displayed.
To configure a rule to generate custom messages:
| 1. |
Go to System Admin  > Advanced > Manage Rules.
|
The Custom Logic Rules dashboard opens.
| 2. | To add a business rule, click Add.
To edit an existing rule, click Edit. |
The Rule Details form opens.
| 3. | Complete the form: |
| Dataform | This is the dataform where this rule will execute when the dataform is saved. | |||||||||
| Method | Choose from the list. For a list of Methods, see Business Rule Methods. | |||||||||
| Rule Title | Provide an abbreviated explanation of what this rule does. | |||||||||
| Rule Type | ClientSpace controls this field automatically. Rule Type is determined by the Method. To customize messages, the Rule Type must be Hard Error or Soft Error. | |||||||||
| Description | Provide a more thorough explanation of what this rule is to accomplish. | |||||||||
|
Primary Source |
Select the dataform or tabbed child form to use as the source for the primary trigger evaluation. Note: To save a Primary Source field value, you must select a corresponding trigger field, operator, and value. If you do not, the source value clears upon saving. |
|||||||||
|
Secondary Source |
Select the dataform, tabbed child form, Server Data Proc 1 (SDP1) or Server Data Proc 2 (SDP2) to use as the source for the secondary trigger evaluation, if applicable. Note: To save a Secondary Source field value, you must select a corresponding trigger field, operator, and value. If you do not, the source value clears upon saving. |
|||||||||
| Primary Trigger Field | Select the field that is going to cause the change. | |||||||||
| Primary Trigger Value | Type the value of what is stored in the database for the Trigger Field. | |||||||||
| Secondary Trigger Field | Select an additional trigger condition that must be met, if necessary. | |||||||||
| Secondary Trigger Value | Set the secondary trigger value. | |||||||||
| Execution Pipeline | Leave this set to Default. | |||||||||
| Execution Order |
This field controls the order in which rules execute. Rules execute from the lowest to the highest number. It may be necessary to look at other rules already configured on this dataform to determine the order of precedence for executing rules. Execution Order of Precedence: Within the Rules system, there is a distinct order of precedence that occurs, that being HardError, SoftError, and BizLogic. This means that setting a field to a specific value automatically with BizLogic, then validating that field with a Hard Error will never occur in the correct order, as the Hard Error fires before the BizLogic fills the field. This order of precedence happens irrespective of the execution order placed on the configured rule:
|
|||||||||
| Save Action | Will this rule be applied on Insert of a new dataform, or the update of an existing dataform, or on both? | |||||||||
| Workspace Template | Select the Workspace Template to which this rule applies. | |||||||||
|
Error Message Override |
Type your custom message. This rich text area field supports advanced formatting options including font selection, size, color, as well as additional formatting, such as bold, italics, and bullet points. This field is available when the Rule Type is Hard Error or Soft Error. The text in this field displays when the rule fires. |
| 4. | Click Save. |