Managing events

Events are system occurrences triggered by new or updated change requests, such as creating or approving a change. Events can trigger special processing, such as alerts and messages. When an alert condition becomes true, Change Management treats it as an event, and sends predefined notifications. You can create other customized routines to run as part of event processing.

The Events file contains the names and definitions of all valid Change Management events.

Change Management includes several default events, such as cm3r approved and cm3r closed. You can add others, according to your business requirements. For example, there may be activities or conditions to be checked or unique events that require user notification.

What controls events?

Event controls are options for processing messages and events. The change or task Phase definition record contains control information that defines when Change Management processes events for the named phase.

The cm3rmessages file

You must define all event names in the cm3rmessages file, or else no event processing can occur. Events are processed when the phase of the change or task is defined in the Phases field of the cm3rmessages file.

The ocmevents record

If the Phase field is NULL on the ocmevents record, the event is processed for all phases.

Checklist: Adding new events

You can perform the following software management tasks to add new events:

1. Activate the Change Management background processor (cm3r)
2. Activate the Change Management (cm3r) alerts schedule record
3. Set the environment record
4. Define the Messages/Events option for the phase
5. Set any RAD or Format Control definition to track a custom event
6. Define the operator groups in the cm3rmessages record in the cm3rgroups file
7. Define the appropriate operator records
8. Define the event in the cm3rmessages file
9. Define the Format Name in the format file
10. Validate the Message Notification controls