7.4.5 Sample Alert Purge Processes
This section includes examples of the Purge Alerts process based on input parameters. These example patterns are also applicable for filtering cases.
Example 1
<Alert>
………..
<Rule id="xyz">
<IdentifierList>3775,3731,3669,3663</IdentifierList>
<Status>CL</Status>
</Rule>
……..
</Alert>
<Alert>
……….
<Rule id="xyz">
<IdentifierList>3775,3731,3669,3663</IdentifierList>
<Status>CL</Status>
<ScenarioIdList>114697002, 114690106</ScenarioIdList>
<JobIds>456789</JobIds>
</Rule>
………..
</Alert>
The utility filters in the existing alerts for IDs 3775,3731,3669,3663 and* having status Closed (CL) and* having Scenario IDs 114697002,114690106 and having Job Id 456789.
Example 2
<Alert>
……….
<Rule id="pqr">
<IdentifierList>3775, 3731,3669,3663</IdentifierList>
<Status>CL</Status>
<JobIds>456789</JobIds>
</Rule>
<Rule id="xyz">
<ScenarioIdList>114697002,114690106</ScenarioIdList>
<CreateDate>
<StartDate>2011-05-25</StartDate>
<EndDate>2011-05-29</EndDate>
</CreateDate>
</Rule>
………..
</Alert>
The utility prepares a query to filter alerts so that rule 'pqr' (fetches alerts as per the single rule described above) or* rule 'xyz' (fetches alerts as per the single rule described above) or*... That is, union of the alerts from all the rules would be filtered.
Here or* specifies the logical or operation specified by sql.