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
This content outlines the various Glide events used within workflows in ServiceNow. These events help initiate and manage workflows based on changes to GlideRecords, though they are primarily part of the Glide engine and have no direct customer-facing applications in workflows.
Show less
Key Features
- Insert Event: Triggered upon inserting a GlideRecord, this event wakes the script engine and initiates associated workflows.
- Update Event: Activated on updating a GlideRecord, this event allows workflows to progress through their transitions based on the document ID.
- Delete Event: Fired when a GlideRecord is deleted, this event enables workflows to continue transitioning as needed.
- Query Event: Occurs during a query of the Glide database, allowing workflows to advance through their transitions linked to the queried GlideRecord.
Key Outcomes
Understanding these events enables ServiceNow customers to leverage the Glide engine effectively for workflow management. While there is no explicit customer-facing use for these events, they provide critical behind-the-scenes functionality to ensure workflows operate smoothly in response to database changes.
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 |