Event Catalog
Definition
The event catalog lists all the type of events that can affect a service or a configuration item (CI).
EndDefinition
It is built using a tree structure of categories. Each event will automatically inherit the attributes of the associated category.
Each catalog entry is used to identify:
- The process for the return to normal functioning, through a workflow.
- The priority assigned to the type of event, via the impact level and the urgency level.
Example
Internet catalog entry divided into two sublevels:
- Attack detected by Firewall sublevel
- Download File greater than 10 MB sublevel
Notes
- You can modify the parent category once the catalog entry has been created using the Reorganize wizard.
- Modifications made to the parent category will be inherited by the associated lower-level catalog entries, except if they contain specific information.
- Workflows related to events do not contain steps requiring user intervention. As a general rule, they only contain conditional steps, notification steps (email sending), Web Service steps and internal update steps (using SQL queries).
See Table of action types.
Best Practice
- To qualify an event quickly, specify the code of each category.
- Each catalog entry with a parent will automatically inherit the parent's information, such as its workflow. You should only enter information specific to the category.
Screen description
Menu access: Operation > Catalogs > Event Catalog
Code
Code: Alphanumeric code used to select the catalog entry quickly during manual data entry. In this case, the description is automatically displayed.
- The code must be unique in the catalog.
Description
Description: Description of the catalog entry.
Workflow
Workflow: Standard workflow applied when the object associated with the catalog entry cannot be solved during its creation in the quick call and requires a transfer.
- By default, the workflow is inherited from the higher-level catalog entry.
Impact
Impact: When an object associated with the catalog entry is created, this is the default impact level used to calculate the priority level assigned to the object.
- Priority = Impact + Urgency - 1
DefaultUrgency
Default Urgency: When an object associated with the catalog entry is created, this is the default urgency level used to calculate the priority level assigned to the object.
- Priority = Impact + Urgency - 1
- When the recipient is associated with a VIP level or when the equipment is associated with a critical level (indicated by
in forms), the urgency level and the priority level will automatically be decremented by one.
StartEndValidity
Start of Validity/End of Validity: Validity period of the catalog entry.
- When the end date is reached, the catalog entry will automatically be archived and will no longer be proposed.
- You can define overrides depending on the user's location in the Application Perimeter - Locations tab.
Enter a start date greater than the current date to prepare the implementation of a new catalog entry. Once you have specified all elements, make the catalog entry visible by entering a date less than or equal to the current date. You can also delete the date.
Note
Note: Comments on the catalog entry. You can also add images or tables using HTML tags.
List of tabs
Discussions
Discussions: List of discussions related to the current catalog entry, which users can access based on their domain and discussion visibility.
- Enter the keywords you want in the Search field and press Enter.
- To cancel the search criteria and return to the complete list of discussions, provided you have the relevant rights, click within the box and then click
.
Attachments
Attachments: List of documents associated with the current catalog entry.
- Update: Click
in this tab. - To cancel an existing link:
Procedure and Wizards
How to create an entry in the catalog
1. Select Operation > Catalogs > Event Catalog and click . Specify the fields in the form and click 
.
2. Complete the fields of the form then click on .
3. Create a new event for one of the categories in the catalog and check that it automatically inherits the information of the catalog entry.