Component: RULE

Component: RULE_EXECUTION

The following table describes the fields in the Rule Execution.

Table 11-13 Fields in the Rule Execution and their Descriptions

Field	Description
Rule Code	Display the codes of the RRF Rules defined under the selected Infodom.
Build Flag	Select the required option from the drop-down list as “Yes” or “No”. Build Flag refers to the pre-compiled rules, which are executed with the query stored in database. While defining a Rule, you can make use of Build Flag to fasten the Rule execution process by making use of existing technical metadata details wherein the rule query is not rebuilt again during Rule execution. Built Flag status set to “No” indicates that the query statement is formed dynamically retrieving the technical metadata details. If the Build Flag status is set to “Yes” then the relevant metadata details required to form the rule query is stored in database on “Save” of a Rule definition. When this rule is executed, database is accessed to form the rule query based on stored metadata details, thus ensuring performance enhancement during Rule execution. For more information, refer Significance of Pre-Built Flag.
Optional Parameters	Refers to the set of parameters which would behave as filter criteria for the merge query.

Field

Description

Rule Code

Display the codes of the RRF Rules defined under the selected Infodom.

Build Flag

Select the required option from the drop-down list as “Yes” or “No”.

Build Flag refers to the pre-compiled rules, which are executed with the query stored in database. While defining a Rule, you can make use of Build Flag to fasten the Rule execution process by making use of existing technical metadata details wherein the rule query is not rebuilt again during Rule execution.

Built Flag status set to “No” indicates that the query statement is formed dynamically retrieving the technical metadata details. If the Build Flag status is set to “Yes” then the relevant metadata details required to form the rule query is stored in database on “Save” of a Rule definition. When this rule is executed, database is accessed to form the rule query based on stored metadata details, thus ensuring performance enhancement during Rule execution. For more information, refer Significance of Pre-Built Flag.

Optional Parameters

Refers to the set of parameters which would behave as filter criteria for the merge query.