Events

Question 1

What is an event?

Answer 1

A special log record the system generates when something notable has happened or when certain conditions occur

Question 2

What are examples of events?

Answer 2

• When a user logs in
• When someone approves a request
• When someone submits a new KB article

Question 3

What happens in the system when an event occurs?

Answer 3

The system responds to the event with pre-defined actions in response to the condition(s)

Question 4

What does the system use to monitor for system conditions?

Answer 4

Business Rules

Question 5

Which fields on the Business Rule form are used to configure / script trigger conditions and responding actions?

Answer 5

• When to run
• ** Actions**
• Advanced (for writing the script)

Question 6

What is the other strategy used by the system to generate an event?

Answer 6

The GlideSystem eventQueue() method

Question 7

What does the responding action do when a condition is met?

Answer 7

The responding action generates an event record in the Event [sysevent] table

Question 8

How are events named by convention?

Answer 8

**<table name>.<unique>**</unique>

(ex: event.updated, problem.closed)

Question 9

Where to navigate to see logs of generated events?

Answer 9

All > System Policy > Events > Event Log

Event table is also called event log or event queue

Question 10

How do Scheduled jobs work?

Answer 10

1. Read the event queue
2. Forward events to appropriate handler for processing
3. Handler uses info passed in from event records to take some action like:

• Send a notification
• Run a script action
• Trigger a flow

Question 11

Where to navigate to register a new event?

Answer 11

All > System Policy > Events > Registry

Question 12

Why must an event be registered before it can be used?

Answer 12

• Because event registration documents events definitions
• Event registration lets parts of the system see an event in their lists of events and react to it when it occurs