ValidateExpressions

The opening and closing tag for the business rule.

Required /Repeatable Element:

This tag specifies the error messages to be displayed on the screen when a specific condition is evaluated to be True/ False.

Required Element Value:

Expression: Specifies the condition that needs to be evaluated upon trying to process the transaction.

Optional Attribute:

ErrorOnTrue/ErrorOnFalse: Tells the math engine to error if the expression is evaluated to True or False.

ErrorOnTrue: If the Expression is true then displays the error message.

ErrorOnFalse: If the Expression is false then displays the error message.

Note: ErrorOnFalse is a default value if TYPE="ErrorOnTrue" is not specified.

Optional Attribute:

Yes: Error messages will be able to be overridden by checking the Override? checkbox. This is the default behavior.

No: The Override? checkbox will be disabled, preventing errors from being overridden.

Auto: Defines the ability to automatically override the error.

Note: If this attribute is omitted from the configuration, the Override? checkbox will be enabled, allowing errors to be overridden.

Optional Attribute:

ErrorNumber:  This value may match an error number from the Error Catalog (AsErrorCatalog). There are two features controlled by the attribute. One of the two or both features may be invoked within the same rule-transaction combination.

When the attribute’s value matches an error number from the catalog, the error number may provide instructions to the user as an aid to correct the issue causing the error. The instructions are provided by the Error Fix Tip column from the catalog. The column may be blank so that no instructions display.

Regardless of matching the attribute’s value to an error number in the catalog, the attribute’s value allows security group set-up for error overrides. Specific security groups may be configured to allow error overriding capabilities to associated users whereas other security groups may not be configured for the same. By default, all security groups are able to override “overridable” messages. Specific entry into the security tables modify the default behavior.

Example: LH001, U001, V000, V001, V012, V020

Note: If the OVERRIDABLE attribute is set to "Yes," the error numbers entered as values of this attribute will display in the Overridable Errors section of the Transaction Security pane. The security group's ability to override each error can be configured on this pane.

Required Attribute:

ErrorMessage: This attribute is used to specify the error message that should be displayed upon evaluating the condition.

Note: The value of a Math Variable or a Segment Field can be substituted in the error message surrounded by $$$. See General Structure and Best Practices

Optional Attribute:

Yes: The expression is defined as a warning. If defined as a warning, the expression will not display with an Override? checkbox on the Activity Error pop-up.

No: The expression is defined as an error. This is the default value.

Note: If this attribute is present in the configuration, but the VerificationScreen rule has not been configured for the transaction, then the attribute will be ignored. If the attribute is absent from the configuration, then the expression will be defined as an error, by default.

Optional:

This attribute identifies the workflow task that is generated when the workflow feature is "turned on" (system property) and the error is generated. This has no dependence on the <WorkflowTask> transaction element.

Values: Workflow task name

(the WorkflowTaskName, which is created under WorflowTaskTypeDefinition in rules-palette)

The attribute indicates when the Workflow Task is generated. When the named workflow task does not exist, this attribute is ignored.

By default, Workflow Tasks are generated by cycle, DI and AsFile post insert processes and not by user initiated activity execution.

The rules of this attribute are applicable at company, plan, policy, and client levels.

Values

Yes - workflow task is generated by all execution methods including user initiated activity execution.

No - workflow task is generated only by cycle, DI and AsFile post insert processes. This is the default.