Rule Extract
With this extract, business rules can be extracted from a particular cube or defined directly in Jedox Integrator.
Settings
Mode |
|
||||||
Connection | This is the OLAP connection for the cube. This field is only available if you selected Extract from cube in the Mode setting. | ||||||
Query cube | Select the cube from the dropdown box. The cubes shown are from the OLAP connection specified under Connection (above). This field is only available if you selected Extract from cube mode in the Mode setting. | ||||||
Manual definition | if you have selected Manual definition mode (see above), you can write a rule in the Rule extract. It is important to use the correct syntax used by the OLAP server. See Managing Rules for more information on rule syntax in Jedox. | ||||||
Included rule types (at least one must be selected) |
|
Note: if an extract has been filtered for generated rule instances, then it cannot be used as the source for a rule load that uses load mode "update". This is because update mode deletes all existing rules in the target cube. Rule instances cannot run without rules or rule templates, and so the load cannot run.
Example
If you add a rule like this:
['Turnover'] = C:['Units']/100.
the Jedox OLAP server will change this rule using the right syntax into:
['Turnover'] = C:['Units'] / 100.
If you use this as a source in a rule load with INSERT mode, then the rule will be added as a new rule, because it is not the same as in OLAP. Therefore, it is better to create the rule in the Rule Editor and then copy the definition with correct syntax to the Rule Extract.
Note: rule templates use the same syntax for variables as Integrator projects: ${varname}. If a rule template and an Integrator project use a variable with the same name, the variable will be handled by the Integrator task, not the rule template. Problems can be averted by changing the Integrator variable name on a project level.
Updated April 14, 2025