Skip to content

Trigger an Action When a Task Deadline Expires

Scenario

Use this example when a task must complete within a defined time and the process should react automatically when that time limit is exceeded.

What You Will Learn

  • configure a duration and deadline action for a task
  • observe how an active task becomes overdue
  • verify the automatic action path after the deadline expires

Difficulty and Estimated Time

  • Difficulty: Beginner
  • Estimated time: 15 minutes

Assumed Knowledge

You should be familiar with tasks, actions, routes, and starting a test process instance.

Required Reading

Prerequisites

  • permission to create folders and processes
  • access to the process editor and form designer
  • a test user who can run the created process

Steps

Create a Folder

  1. Open the folders area.
  2. Create a new application folder, for example Expense Form.

Create a Process

  1. Create a new process inside the folder.
  2. Open the process in edit mode.
  3. Select the default pool to start modeling.

Process editor open with the default pool selected.

Create the Tasks

  1. Rename the opening task to Expense Form.
  2. Add the Submit action to the opening task.
  3. Create the next task and rename it Manager Approval.
  4. Add Approve and Reject actions to the approval task.
  5. Route the Reject action back to the first task.

Second task with approval actions and return route options.

Add the Deadline

  1. Open the deadline menu by selecting the clock icon under Manager Approval.
  2. Set the deadline duration.
  3. Optionally enable the notification checkbox.
  4. Select the action that should run when the deadline expires.

The action list is populated from the task actions, so the deadline can advance the process automatically when the time limit is reached.

Deadline configuration with duration, notification, and action selection.

Create the Form

  1. Open the form under the same process.
  2. Add a row-content section.
  3. Add a text control inside the section.
  4. Save the form layout.

Form designer with a row-content section ready for input controls.

Save and Test the Process

  1. Close the designer tab.
  2. Commit the process changes.
  3. Start the process from the folder.
  4. Submit the first task so the approval task is created.
  5. Observe the task in the worklist before and after the deadline expires.

When the approval task is active, it appears in the orange queue because it has a deadline.

Worklist showing the task before the deadline expires.

After the deadline passes, the task moves to the red queue and the deadline information is shown in the task detail.

Worklist showing the overdue task after the deadline is exceeded.

Result

You now have a process task with an automatic deadline and an explicit action path for overdue work.

Verify the Result

Start the process, leave the timed task open, and confirm that the configured action is selected after the deadline. Also complete a second instance before its deadline and confirm that the normal route is used.

Security and Portability Notes

  • Configure a short duration only in a test domain; use a realistic service target in production.
  • Deadline execution uses the permissions and tenant context of the process instance. Do not use it to bypass task authorization.
  • Do not embed user IDs or environment-specific values in the deadline script or route.

What to Learn Next