Glide events relative to workflows
Summarize
Summarized using AI
This content was generated using new OpenAI-powered functionality. Results are provided on an as is basis and are not guaranteed to be accurate or complete.
Summary of Glide Events Relative to Workflows
Glide events play a crucial role in the operation of workflows within ServiceNow. These events are triggered by actions performed on GlideRecords, which are fundamental database records within the platform. Understanding these events helps customers effectively manage workflow processes associated with database operations.
Show less
Key Features
- Insert Event: Triggered when a GlideRecord is inserted, waking the workflow engine and allowing workflows linked to the GlideRecord to start. This event is not customer-facing but is foundational for initiating workflows.
- Update Event: Activated upon updating a GlideRecord, this event allows the workflow engine to advance through the next transitions of running workflows associated with the record.
- Delete Event: Occurs when a GlideRecord is deleted, similarly enabling the workflow engine to progress through subsequent transitions related to the record.
- Query Event: Triggered by querying the Glide database, it also facilitates the workflow engine's advancement through transitions connected to the GlideRecord.
Key Outcomes
By understanding these Glide events, ServiceNow customers can effectively manage and automate workflows based on database actions. While the events are not directly manipulated by users, they ensure that workflows function smoothly in response to record changes, enhancing operational efficiency.
Workflow uses several Glide events.
| Event | Description | Purpose | To Use | Source | Thread | Listeners |
|---|---|---|---|---|---|---|
| Insert | Global event set upon the insert of a GlideRecord that causes the script engine, and through that the workflow engine, to wake up. | Starts workflows that are associated with the current GlideRecord either by reference, as in request items and SLA timers, or by conditions associated with the GlideRecord's table. | There is no explicit customer-facing use for this in a workflow. It is part of the Glide engine, and with this event, the only thing workflows can do is start. Workflows can also be started manually using a script. | Workflow Engine, RunEngine | Current thread, current mutex | User action of insert |
| Update | Global event set upon the update of a GlideRecord that causes the script engine, and through that the workflow engine, to wake up. | Looks to the Workflow Context [wf_context] table to find running workflows that are associated with the current GlideRecord by document ID. | There is no explicit customer-facing use for this in a workflow. It is part of the Glide engine, and with this event, the only thing workflows can do is advance through the next set of transitions. | Workflow Engine, RunEngine | Current thread, current mutex | User action of update of a GlideRecord |
| Delete | Global event set upon the delete of a GlideRecord that causes the script engine, and through that the workflow engine, to wake up. | Looks to the Workflow Context [wf_context] table to find running workflows that are associated with the current GlideRecord by document ID. | There is no explicit customer-facing use for this in a workflow. It is part of the Glide engine, and with this event, the only thing workflows can do is advance through the next set of transitions. | Workflow Engine, RunEngine | Current thread, current mutex | User action of delete of a GlideRecord |
| Query | Global event set upon the query of the Glide database that causes the script engine, and through that the workflow engine, to wake up. | Looks to the Workflow Context [wf_context] table to find running workflows that are associated with the current GlideRecord by document ID. | There is no explicit customer-facing use for this in a workflow. It is part of the Glide engine, and with this event, the only thing workflows can do is advance through the next set of transitions. | Workflow Engine, RunEngine | Current thread, current mutex | User action of query of a GlideRecord |