It often happens that a rule must not run until another rule has completely finished execution. A typical example of this is when a WHERE Clause condition references a different column in order to place appropriate data in another column.
All Data Masker rules can be made dependent on any one other rule. The Data Masker will note the dependency conditions and will not execute the rule until the parent rule has completely finished running and has committed its data.
Dependency conditions are displayed by indenting the dependent child rules underneath the parent rule. In the example above, rules 3000 and 3001 will not run until the Insertion rule (1000) that is their parent has executed. It is quite possible to implement lengthy chains of dependencies. In the above example, both rules 3000 and 3001 could have further dependent rules.
To implement a dependency, select the proposed child rule on the Set Rules tab and click on the Set Dependency button there. This Rule Dependency dialog box will start to offer you the option of choosing the parent rule.
Once this Rule Dependency box has started, select the proposed parent rule with the mouse and press the Apply Dependency button. The screen will update and the new dependency relationship will be implemented.
Note: The ID of the proposed child rule (referred to as the Active Rule in the image above is fixed and is always the currently selected rule in the Set Rules tab when this dialog box is launched.
To break a dependency relationship, select the dependent child rule with the mouse on the Set Rules tab. A dialog box will appear which offers the option of removing the dependency relationship.