4 Alert Creator Editor

The Alert Creator Editor administration tool is used to automatically group matches that share similar information into a single alert that is centered on the same focal entity. You can create new rules, modify the logic behind existing rules, and delete rules.

The tool also displays the job ID and job template ID associated with each rule.

This chapter focuses on the following topics:

About the Alert Creator Editor

By design, the application is configured to run a system job that generates an alert for every match detected. To increase work efficiency, you can use this tool to create custom jobs to run before the system job that group matches and share similar information into a single multi-match alert. The system job runs last to generate alerts for any matches that cannot be grouped.

The Alert Creator Editor enables you to view the logic used to group matches into alerts and allows you to add, delete, or update the logic. In addition, the Alert Creator Editor creates and updates the jobs that execute the rules and creates and updates job templates associated to the job for the particular rule.

Alert Creator Rule Guidelines

The following guidelines apply to the Alert Creator Editor:

  • Each Alert Creation Rule is associated with a focus type. Matches grouped into an alert must share the same value for a given focus type. For example, account-focused matches that share the account identifier 12345 are grouped to create one alert, while account-focused matches with the account identifier 12346 are grouped into another alert.
  • Each Alert Creation rule can also specify zero (0) or more additional bindings that must be shared by all matches. Bindings are variables captured in a scenario pattern. Each binding must be attributed as mandatory (!) or conditional (?). If a binding is specified as mandatory, all matches grouped together must have the same binding and the same value for that binding. If a binding is specified as conditional, matches that have that binding and have the same value for that binding is grouped together; matches that do not have this binding is grouped together.For example, !FIRM ?ISSUE, wherein FIRM is the mandatory binding and ISSUE is conditional binding. In other words, for an alert to be created, each group must have a FIRM binding in which the values for that binding must match. In addition to FIRM binding, each group must either have an ISSUE binding in which the values match or each must be missing the ISSUE binding.

    Note:

    You can select only those bindings that represent focal entities.
  • One of three strategies must be selected for each Alert Creation rule. The strategies specify whether the same pattern, scenario, or scenario class must have generated all matches.
When you have finished using the Alert Creator Editor, you need to adjust the sequencing of the associated jobs. The following guidelines apply to job sequencing:
  • To adjust the sequencing of the jobs, refer to your scheduling tool’s documentation (for example, Control-M) to resequence the associated jobs. The Job ID and Job Template ID’s associated with each rule are identified in both the Alert Creator Rule List and the Alert Creator Editor pages.
  • Alert Creation jobs must run in a specified order (most specific to most general). If general jobs are run first, the matches would be grouped into one large (general group) alert as opposed to multiple (specific group) alerts.
  • The system job must run after all other grouping jobs to create alerts for each match that could not be grouped, based on the defined grouping rules.

Note:

Job Template IDs for all jobs are provided at deployment.