Component: PROCESS_EXECUTION

This component will combine all the rules to create single or multiple merge queries. Only rules defined on the same dataset can be merged. For creation of queries the current order of the rules inside the process or sub-process will be taken into consideration. Following validations are performed to determine single or multiple DMLs for merging Rules that is, validation on subsequent rules.

• For classification-classification or classification-computation rule combination, the target column of the prior classification rule must not be used in any of the subsequent rules as source hierarchies in the executable process or sub-process. Also the same target hierarchy must not be used as a target in the subsequent rule.
• For computation-computation rule combination, the target measures of the prior computation rule must not be used in any of the subsequent computation rules in the executable process or sub-process.

All the merge queries created after satisfying all the conditions will be executed in a single transaction.

Note:

• RRF framework cannot validate the semantic correctness of the rules grouped for merge. It is left to the application developer/user to make a conscious choice.
• If the merge results in an ill-formed or runaway SQL, the framework will not be able to detect it at design time. This is again left to application developer/user to design the grouping that is syntactically valid.

The following table describes the fields in the Process Execution.

Table 11-12 Fields in the Process Execution and their Description

Field	Description
Process Code	Display the codes of the RRF Processes defined under the selected Infodom. Select the required Process from the drop-down list.
Sub Process Code	Display the codes of the Sub Processes available under the selected Process. Select the required Sub Process from the drop-down list.
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.