Identify when a task SLA record reaches a specific percentage value and perform other actions or flow logic that is based on the SLA percentage. For example, send a notification when an SLA percentage timer completes.
You can apply the decision table rules and subflow or flow that executes the decision table to automate claims processes in the Insurance claims application.
Specify the priority that you want a background flow to have in relation to other flows waiting to be run. Run a group of higher priority flows before running any lower priority flows.
You can trigger a Smart Assessment Engine assessment from the Workflow Studio or from a script. With either method, you specify a published assessment template, the assessors who respond, and other optional inputs.
You can test a subflow alone, or when added to a flow. When testing a subflow alone, you must define the inputs that the subflow uses in its actions. Because a subflow does not have a trigger, testing a subflow runs the actions using the defined input values.
You can’t convert existing flows directly into playbooks in Workflow Studio. Each flow designer step that creates a response task to guide the analyst must be broken down into separate actions or subflows.
Start a flow when a MetricBase trigger is met. MetricBase triggers track time series data and can monitor when a threshold is reached, when a trend is detected, or when a system stops reporting data.
Copies an attachment from the Attachments [sys_attachment] table to a target record.
Using an agent or building an integration?
The same documentation is available through the public REST API.
GET /api/docs/search?q=GlideRecord&limit=20
GET /api/docs/document?path=…
GET /api/docs/:id?revision=…
Search returns document paths, IDs, snippets, and an index revision. Read by path for a stable reference; numeric IDs should be used with the returned revision. Document bodies are Markdown.