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 are integral to the functionality of workflows within ServiceNow. They trigger actions based on specific operations conducted on GlideRecords, such as inserting, updating, deleting, or querying. Understanding these events helps customers leverage workflows effectively within their applications.
Show less
Key Features
- Insert Event: Activates when a GlideRecord is inserted, waking the workflow engine to start associated workflows.
- Update Event: Triggers when a GlideRecord is updated, allowing the workflow engine to advance running workflows based on the updated record.
- Delete Event: Initiated upon the deletion of a GlideRecord, prompting the workflow engine to progress through transitions associated with the record.
- Query Event: Occurs when a GlideRecord is queried, enabling the workflow engine to advance workflows linked to the queried record.
Key Outcomes
These Glide events facilitate the automation of workflows without explicit customer-facing interactions. By understanding the triggers and their purposes, ServiceNow customers can ensure that workflows operate seamlessly in response to database changes, enhancing efficiency and responsiveness in their applications.
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 |