Question 180
An approval waits indefinitely after the approver becomes inactive and no escalation branch exists. Which configuration or administrative response BEST addresses the primary issue?
Explanation
Correct Answer
Use an approval action and an explicit wait/resumption condition for long-running decisions, ensuring rejection and cancellation paths are handled without premature fulfillment. Waiting for approval is a durable lifecycle state; successful notification delivery and final approval are separate events. Verify prerequisites with: Inspect approval record generation, approver resolution, flow wait state, timeout handling, rejection branches and downstream task creation. Scenario: An approval waits indefinitely after the approver becomes inactive and no escalation branch exists.
Incorrect Answers
Build a supported Workflow Studio flow with an appropriate record, schedule, or service catalog trigger and narrowly scoped actions; test its conditions before activation. This approach instead addresses Workflow Studio trigger and action design. A Flow must have matching triggers and properly mapped actions; an inactive flow or false condition will not run merely because it exists. The targeted response is: Use an approval action and an explicit wait/resumption condition for long-running decisions, ensuring rejection and cancellation paths are handled without premature fulfillment. Scenario: An approval waits indefinitely after the approver becomes inactive and no escalation branch exists.
Provide an explicit Virtual Agent escalation to an available human support channel when automation cannot resolve a case, preserving context without exposing unrelated private transcript data. This approach instead addresses Virtual Agent human handoff and fallback. A chat session ending without a supported answer is not a successfully completed service request; escalation must be observable. The targeted response is: Use an approval action and an explicit wait/resumption condition for long-running decisions, ensuring rejection and cancellation paths are handled without premature fulfillment. Scenario: An approval waits indefinitely after the approver becomes inactive and no escalation branch exists.
Choose the appropriate ServiceNow workspace or platform UI for the user's task and verify view/context selection rather than assuming a classic form and a configured workspace always render the same layout. This approach instead addresses Unified navigation between workspaces and platform views. Workspace experience and traditional platform form views can differ in component layout and configuration, even when they operate on shared records. The targeted response is: Use an approval action and an explicit wait/resumption condition for long-running decisions, ensuring rejection and cancellation paths are handled without premature fulfillment. Scenario: An approval waits indefinitely after the approver becomes inactive and no escalation branch exists.


