Events and DVGs

Every event generated in the system (except for SLC events generated by SLCs with DVGs assigned) is compared to all criteria in all data visibility groups. If a match is found, the name of the data visibility group (DVG) is added to the event.

The following figure shows how an event is tagged with DVGs:

Image shows an event tagged with DVGs.

An event with a ProcessName of PayMay2010 is generated by the engine. The PAYROLL DVG Criteria1 ProcessName contains Pay which matches the event ProcessName. The ACCOUNTING DVG Criteria1 ProcessName contains Acct which does not match the event ProcessName. The HR DVG Criteria1 ProcessName contains 2010 which matches the event ProcessName. The PAYROLL and HR DVGs are added to the event.

Tip: Each event can be tagged with multiple data visibility groups (DVGs). Multiple DVG values are separated by vertical bars.

Each event is then passed through the metadata service rules and then the appropriate data visibility group rule sets and the GLOBAL rule set. If an event tagged with a data visibility group matches a corresponding rule, that rule is triggered as shown in the following figure:

Image shows event tagged with DVGs that match corresponding rules. The event triggers the matching DVG rules sets and GLOBAL rule set.

An event with a ProcessName of PayMay2010 and PAYROLL and HR DVGs is passed through the metadata service rules. The event is then passed to the PAYROLL rule set. In this rule set, the first rule, PayRule1, contains the parameter DVG which matches PAYROLL. The parameter ProcessName matches PayJune2010. The action is emailBob.

The event is passed to the ACCOUNTING rule set. In this rule set, the rule, AccountRule1, contains the parameter DVG, which matches ACCOUNTING. The parameter step name contains ACCTStep.

The event is passed to the HR rule set. In this rule set, the rule, HRRule1, contains the parameter DVG which matches HR. The parameter ProcessName matches YearEnd2010.

The event is passed to the GLOBAL rule set. In this rule set, the rule, AccountRule1, contains the parameter server group, which matches FTPServers.