Process Hub · Lifecycle stages and record actions
Configure Operational Queue views and overdue highlighting
Show active lifecycle work with useful deadlines and filters.
On this page
Before you start
- Enable and deploy a business lifecycle. Agree which active records the team should see and whether lateness is measured from a date field, creation, submission or claim.
Duration precision
Elapsed deadlines support minute precision, including fractional hours, from one minute to 365 days. Choose a business duration users can understand rather than relying on a display colour as a service commitment.
Follow these steps
Screenshots use fictional training data. Names, dates and amounts are examples. Select an image to view it at full size.
- Open the draft’s record views and add/configure an Operational Queue view. Choose the fields that help users identify and act on each record.
- Enable overdue highlighting when needed. Select a Deadline field or elapsed time after submission, creation or claim; enter the appropriate duration.
- Review date-only behaviour in the profile scheduling timezone: a date-only deadline stays on time for that entire date. Use DateTime when a specific hour matters.

Choose the live stages, actions and fields the queue should expose. Configure due highlighting separately from actual notification delivery. - Add supported queue filters and choose AND/OR deliberately. Relative Today is evaluated in the profile scheduling timezone. Keep the filter set within the supported limit of 20.
- Publish and deploy the structural process. Test records before/after their deadline and a terminal record, which should leave the active queue.
- If users need reminders, configure actual work-item due dates and a published Due soon/Overdue notification policy separately. Test both the queue display and message delivery.
Example: unresolved care cases
Create a queue for active cases, show customer reference, stage and due date, and highlight after one day from submission. Close a test case and confirm it leaves the active queue; inspect its history through the normal record/history views.
What you should see
The queue highlights the intended late active records and gives users an actionable view of their work.
If something goes wrong
A red/late record sends no reminder
Queue highlighting does not schedule notifications. Set work due dates and a supported due-event notification policy.
A record due today looks on time after the browser’s local midnight
Check the profile scheduling timezone and whether the deadline is Date or DateTime. Browser timezone is not the governing queue date.