Alerts, events, and messages

Events are system occurrences, triggered by user activity or certain conditions, that require additional user action. Examples of events in Request Management include open, update, close, and approval (of quotes).

Events in Request Management send messages to designated parties (operators or groups) within the system. For example, messages indicate that someone opened a quote and start the approval process by notifying an approver.

If a time limit set for accomplishing an approval is not met, an alert runs. An alert is an optional time-delayed event, which causes another event to send out a message.

As soon as a request is approved, that action constitutes an event. The event sends a message that indicates the state of the request.

Events, alerts, and messages build a chain of communication, notifying users of pending quotes and orders and the status of requested items throughout their life cycles.

Note: Setting up alerts, events, messages, and approvals requires the operation of the ocm background scheduler. The scheduler must be included in the system start-up schedule record. See Background processing and Generating orders for help in setting up these processes.

Related topics
Events and messages
Alerts