You need to build a QC review process for a factory that allows a technician to review each production line on a regular basis. A QC technician has…

This scenario requires a mechanism that both interrupts a task after a specific duration and triggers an alternative process flow. An exception timer on the User Input Task is the correct implementation. When the 30-minute timer expires, the exception path is triggered, which cancels the active task, preventing the user from submitting. This exception flow can then be directed to a Send Email smart service to notify the supervisor. Because the main flow is bypassed, the subsequent node to save data to the database is never executed, fulfilling all requirements.

B. A quick task is designed for simple, immediate actions, not for a complex form-based review that requires the ability to save a draft and return later.

C. A send message event is used for inter-process communication. While it could be triggered by a timer, it would not cancel the original user input task, allowing a late submission.

D. An escalation can send a notification after a set time but does not interrupt or cancel the task. The technician could still complete the review after the 30-minute deadline has passed.

1. Official Appian Documentation

"User Input Task

" section on "Escalations and Exceptions": This section explicitly differentiates between the two. It states

"Exceptions are configured on the Exceptions tab of an activity. They allow you to redirect the process flow... When an exception is triggered

the activity is deactivated." This confirms that an exception timer (Option A) deactivates the task

while an escalation (Option D) does not.

2. Official Appian Documentation

"Ways to Trigger a Process

" section on "Timer": This documentation details how timers can be used to start a process or trigger an event within a process. It clarifies that a timer configured as an exception on a node will interrupt the node's execution

which is the required behavior.

3. Official Appian Documentation

"Quick Tasks": The documentation describes Quick Tasks as a way to "complete simple actions and tasks directly in Tempo

Sites

and embedded interfaces." This highlights their unsuitability for the described review process which implies a more complex form with draft functionality.