Generating a rule set executable

You will generate a rule set executable from the rule set definition.

Next, you generate a rule set executable by selecting actual data to be used for each term or variable in the rule set variables. If the data references involve multiple data sources or data tables, you can specify the required joining of data to perform the rule set execution. Use the Bindings and Output tab to associate rule logic variable information, join keys, and output criteria for the rule set.

Important: A rule set constraint is that every data rule definition or executable data rule selected must use the same source data (that is, table or joined table). You can also define the output conditions that cause a source data record to be added to the output table for the data rule set.

The following information provides a high-level overview of the process you will use to generate an executable rule set.

Open the rule set definition and select the Bindings and Output tab.
Figure 1. Example of the Open Rule Set window with the Binding and Output tab selected
Select the actual data references with which you want to replace the logical variables in the rule set definition.
Note: The rule set definition can be used to create multiple executable rule sets by binding the logical variables to different source data. This enables the same rule logic to be used by different data sources (tables) where applicable. If required by the data rule logic, you can also enables joins of data from different data sources (tables) during this binding process.
Finally, you define the output table conditions and output columns required for producing an output table during rule set execution.

The result is the executable rule set. You can repeat this task multiple times binding a single data rule set definition into multiple executable rule sets each by using different actual data (for example, a data rule to verify city-state-zip code used for customer, billing, shipping and vendor addresses).

System capabilities

All rules sets are executed in the same way. The system retrieves all of the source data records, including the join of records if required, which are then tested one-by-one against the logic of each data rule in the rule set. Each source record either meets or does not meet the logical conditions expressed in a data rule. The statistics (by individual data rule and for the rule set) are updated accordingly. If the source record matches the output conditions of the rule set, it is added to the output table for that rule set. If the rule set has a benchmark for results, the actual results are compared against the benchmark and a variance is calculated. This information is included in the statistics update.

The statistics generated from the execution of a data rule set include:

Data Rule Set record-based statistics
- Number of records tested
- Number of records that met the data rule conditions
- Number of records that did not meet the data rule conditions
- Percentage of records that met the data rule conditions
- Percentage of records that did not meet the data rule conditions
- Number of records in the variance from the data rule benchmark (optional)
- Percentage of records in the variance from the data rule benchmark (optional)
Rule set source-based statistics
- Number of records that met all rules
- Number of records that failed one or more rules
- Average number of rule failures per record
- Standard deviation of the number of rule failures per record
- Percentage of records that met all rules
- Percentage of records that failed one or more rules
- Average percentage of rule failures per record
- Standard deviation of the percentage of rule failures per record