Service Request Workflow

On this page

Default Workflow: This page describes the service request workflow of a new Alloy Navigator 2026.1 database created with the Default Workflow. An upgraded database need not have this content, and an administrator may have changed it. See Default Workflow Configuration.

In this configuration, there is no general status-change action; you change a service request's status with named actions. For where a ticket's actions are and how to run them, see Work on a Ticket.

Assign, complete, and close a service request

  1. Assign the service request. Assign to me and Assign to... are offered in Unassigned, Assigned, In Progress, Approved, and Completed. To take the service request yourself, run Assign to me, which is offered while the service request has no assignee or another assignee: you become the assignee, and the status becomes In Progress. The action sets Assigned, and the service request moves on at once, with the activity "Assignee has begun work", because an Assigned service request that its assignee saves moves to In Progress. To assign it to someone else or to a group, run Assign to..., choose the assignee group, the assignee, or both, and click Submit. The status becomes Unassigned when only a group is set and Assigned when a new assignee is set.
  2. To schedule the work, run Schedule Work, which is offered in Assigned, In Progress, On Hold, and Approved while the scheduled start date or the scheduled end date is empty. In the "Schedule Work" form, enter the scheduled start date and the scheduled end date, which are required, and click Submit. The scheduled start date must be after the service request's submit date and before the scheduled end date, and the scheduled end date must be before the service request's due date; otherwise an error message stops the submission. Schedule Work writes the two dates and leaves the status as it is.
  3. Record your work with Log Work, which is offered in every status except Closed, and only to the service request's assignee. It sets In Progress when the service request is Assigned. Saving an Assigned service request while you are its assignee also moves it to In Progress.
  4. Run Complete Request, fill in the "Complete Request" form, and click Submit. Complete Request is offered in Assigned, In Progress, On Hold, Approved, and Rejected. The status becomes Completed, and the completed date is set if it is empty.
  5. Run Close Request, which is offered in Completed, choose a Closure Code, and click Submit. Close Request is not offered to the Service Request Technician role. The status becomes Closed.

To reply to the requester along the way, run Notify Requester; see Reply to the requester. Complete Request stops when the requester of the service request, or of a child work order that it sets to Completed, has no valid primary e-mail address; see Find out why an action stops on an e-mail address.

On a Completed service request, Assign to me moves it back to In Progress, and Assign to... moves it back to Assigned or Unassigned; its completed date stays as it is.

A service request that stays Completed without changes is closed automatically after a set number of days; see Automatic status changes.

Other service request tasks

Put a service request on hold

Run Place on Hold, which is offered in Assigned, In Progress, and Approved. The status becomes On Hold. To continue, run Take off Hold, which sets In Progress, whichever status the service request had before the hold. Both actions open the "Provide a Reason" form, whose Comment and Time Spent are not required.

Reopen a closed service request

Run Reopen Request. It is offered in Closed, and only to the Administrator (Full), Administrator (Workflow), and Service Request Manager roles. In the "Reopen this Request" form, the assignee group and the assignee are pre-filled with those of the service request, and the assignee can only be a member of the chosen group. The form also has Comment and Time Spent. Click Submit.

The action sets In Progress, or Unassigned when the service request has a group but no assignee, or Assigned when you change the assignee, who is then e-mailed. It also clears the completed date and the closure code. The action does not run auto-assignment: a service request reopened with a group and no assignee is Unassigned when the action completes, also during working hours, and the periodic check can assign it later; see Automatic status changes.

Convert a service request to an incident

Run Mark Incident, which is offered in Assigned and In Progress. In the Web App, Mark Incident is on the service request form's toolbar, not on the Action Bar.

In the "Convert to Incident" form, Summary, Description, Type, and Requester are required. Summary, Description, Project, Requester, and Related CI are pre-filled from the service request, and Service, Urgency, and Impact are pre-filled with Technical Support, 3 - No Rush, and 3 - Single Person. Assignee offers only the members of the chosen Assignee Group. Click Submit.

The service request is set to Closed with the closure code Ticket Converted, its completed date is set if it is empty, and the activity "Converted Request to Incident" is logged on it. A new incident is created in the service request's workspace, from the form and from the service request's medium and actual response date. The incident receives a copy of the service request's attachments, and the two records are related: the incident lists the service request under Converted from, and the service request lists the incident under Converted to. Auto-assignment then runs on the new incident and sets its status: Assigned when the incident has an assignee, and Unassigned when it has a group but no assignee. When you leave both the assignee group and the assignee empty on the form, auto-assignment gives the incident the support group of its service, while the workflow parameter Service Support Group Assignment is on, as it is for incidents in the supplied configuration. When you leave the assignee empty, auto-assignment also picks an assignee among the active members of the incident's group whose work calendar shows them available for the next 15 minutes, and the incident is Assigned: with the workflow parameter Assignee Load Balancing Method set to Least amount of tickets, as it is for incidents in the supplied configuration, it picks the member with the fewest incidents at Unassigned, Assigned, or In Progress. When no member is available, the incident stays Unassigned with the group. On an incident, Make Request does the reverse; see Incident Workflow.

Mark a duplicate

Run Mark Duplicate, which is offered in every status except Closed. In the Web App, Mark Duplicate is on the service request form's toolbar, not on the Action Bar. In the "Mark Request as Duplicate" form, choose in Duplicate of, which is required, the service request that this one duplicates; the service request itself is not offered. The form also has Comment and Time Spent. Click Submit.

The action sets the service request to Closed with the closure code Ticket Duplicated, notifies its followers, and logs "Marked duplicate of <ticket>" on it, with your comment as the details. It relates the two service requests: this one lists the other under Duplicate of, and the other lists this one under Duplicated by. It also sets the start date, when the service request has an assignee, and the actual response date and the completed date, each only if it is empty. On the other service request, it logs an activity that begins "Duplicate ticket related", with your comment and this service request's description in its details, and notifies that service request's assigned party.

Create a work order from a service request

Run Create Work Order, which is offered in Assigned, In Progress, On Hold, and Approved, to the Administrator (Full), Administrator (Workflow), Service Request Manager, and Service Request Technician roles. In the Web App, it is in the Relationships section of the Action Bar.

Its form, "Create a Work Order", requires a summary and a description, which are pre-filled with the service request's, a type, and a requester, who must be a technician and is pre-filled with you. The project and the related CI are pre-filled with the service request's, and the service with General Work Order. You can also set the category, the assignee group, the assignee, the urgency, the impact, and the scheduled start and end dates, and add attachments; the assignee can only be a member of the group chosen on the form.

When you submit the form, the action logs "Created Related Work Order" on the service request and creates a work order whose parent is the service request, in the service request's workspace, with the form's attachments. The work order takes the organization of its requester. Auto-assignment runs on the new work order: it is Unassigned when only a group is set, and Assigned, with an e-mail to the assignee, when an assignee is set. When you leave both the assignee group and the assignee empty, auto-assignment gives the work order the support group of its service, and the work order is Unassigned; the service General Work Order, with which the form starts, has a support group. A work order that ends up with neither a group nor an assignee has no status. The new work order does not open when the action completes. The service request's status does not change. For the work order's own workflow, see Work Order Workflow.

Reserve a library item for the requester

When the service request's related CI is a library item, run Create Reservation to reserve the item for the service request's requester. It is offered in every status except Closed, to the Administrator (Full), Administrator (Workflow), Service Request Manager, Service Request Technician, and Library Manager roles. In the "Create a Reservation" form, enter Reservation Date From and Reservation Date To and choose the Type; all three are required, and Type starts at Short Term. Both dates must be in the future, and Reservation Date To cannot be before Reservation Date From; otherwise the action is refused with a message. Click Submit.

The action creates a Pending reservation of the library item for the requester, with the dates and the type you chose, and logs "New Reservation Created" on the service request. A date range that overlaps a Pending reservation of the same library item is refused with "This reservation conflicts with an existing reservation date range." When the library item's owner is someone other than you, the owner is e-mailed. The status of the service request stays. For reservations, see Equipment Lending Library.

Use a consumable

Run Use Consumable, which is offered in Assigned, In Progress, and Approved while the service request's related CI is a computer or a hardware item. In the "Use a Consumable" form, choose the Consumable and the Reason, and fill in Quantity Used and Used On, which is pre-filled with the current date and time; all four are required. Click Submit. The Reason list offers two reasons, and the reason decides what is recorded:

  • Issuing to User issues the consumable to the service request's requester. The issue is logged on the service request, the consumable, and the requester, and the requester is related to the consumable.
  • Using in Asset uses the consumable in the related CI. The use is logged on the service request, the consumable, and the CI, and the CI is related to the consumable.

In both cases, the service request is related to the consumable, the consumable's quantity is lowered, and a stock movement is recorded; when you use all that was left, the consumable is set to Depleted. The action is refused when the consumable's quantity is empty or 0 or the consumable is Depleted ("There are no consumables currently available for use."), and when you enter more than is available ("You are attempting to use more consumables (<quantity used>) than are currently available (<quantity left>)."). The status of the service request stays. For consumables and stock movements, see Stock and Consumables.

Send a meeting request

Run Send Meeting Request, which is offered in every status except Closed. In the "Send Meeting Request" form, enter the Time, choose the Location, and type a Comment; all three are required. To is required and is pre-filled with the service request's requester; you can add other people to To, and people in CC and BCC. Click Submit.

The action sends one e-mail to the people in To, CC, and BCC: a meeting request whose subject is "Meeting Request (Service Request):" followed by the service request's summary, with a calendar file built from the chosen time. It logs the activity "Meeting request was sent" in the Communication category, with the meeting time, the meeting place, and the comment in its details, and publishes it to the Self Service Portal. While the workflow parameter Convert CC'd Persons in E-mail to Collaborators is on, as it is in the supplied configuration, the people in CC who are not technicians become collaborators; a person in BCC does not. Each new collaborator is e-mailed "Added as a Collaborator (Service Request):" followed by the service request's summary, while the workflow parameter Notify Collaborators on Creation is on, as it is in the supplied configuration. The status of the service request stays.

The action stops when a person in To, CC, or BCC, or an active collaborator of the service request, has no valid primary e-mail address; see Find out why an action stops on an e-mail address.

Request an approval

Create Approval is offered in Assigned and In Progress. Request Approval is offered in the same statuses while the service request has a pending approval stage and a pending approval request, and it sets Pending Approval. In Pending Approval, a pending approver of the pending approval stage votes with Approve Request or Reject Request. The approval outcome sets Approved or Rejected. Cancel Approvals is offered in Assigned, In Progress, and Pending Approval while an approval stage is Pending or Pending Approval, and only to the Administrator (Full), Administrator (Workflow), and Approval Manager roles; it returns the service request to In Progress. See Approvals.

Statuses and lifecycle stages

A service request uses nine statuses: Unassigned, Assigned, In Progress, On Hold, Completed, and Closed, and, for approvals, Pending Approval, Approved, and Rejected.

Unless a service request is created through the API, auto-assignment runs on it at creation. When the service request has neither an assignee group nor an assignee, it gets the support group of its service, while the workflow parameter Service Support Group Assignment is on, as it is in the supplied configuration. When it has no assignee, auto-assignment picks one among the active members of the group whose work calendar shows them available for the next 15 minutes, and the service request is Assigned: with the workflow parameter Assignee Load Balancing Method set to Least amount of tickets, as it is for service requests in the supplied configuration, it picks the member with the fewest service requests at Unassigned, Assigned, or In Progress. When no member is available, the service request is Unassigned with the group; see Automatic status changes.

Five catalog items then send the new service request for approval when its requester has a manager: Software Request, Printer Request, Hardware Request, Phone Request, and Network Share Access. The service request starts as Pending Approval and keeps the assignee and the group that auto-assignment gave it. It has one approval stage, named after its summary, with a deadline two days from now and one approval request for the manager, who is notified, and the activity "Approval Requested by <current user>" is logged; for the vote, see Request an approval. When the requester has no manager, a service request created by one of these five items starts like any other.

In the Web App, the progress bar at the top of a service request's full form shows five lifecycle stages (see Follow the ticket's progress):

Stage Statuses
Submission Unassigned, Assigned
Approval Pending Approval, Rejected
Planning Approved, On Hold
Completing In Progress
Close Completed, Closed

Action reference

Unless the row says otherwise, the actions in this table are offered to the Administrator (Full), Administrator (Workflow), Service Request Manager, and Service Request Technician roles. Mark Duplicate, Approve Request, Reject Request, Add Comment, and Notify Assignee are offered to every role of the supplied configuration except the Administrator (Log Management), Administrator (Security), Administrator (Services), Administrator (Views/Dashboards), Report Designer, Report Viewer, and Viewer roles.

Action Offered in What it does
Assign to me Unassigned, Assigned, In Progress, Approved, Completed, when the service request has no assignee or another assignee Makes you the assignee and your top-ranked group the assignee group, sets the status to Assigned, sets the start date if it is empty, logs "Current User assigned to self", and notifies the collaborators. The service request then moves on to In Progress, as an Assigned service request does when its assignee saves it. The action does not clear the completed date.
Assign to... Unassigned, Assigned, In Progress, Approved, and Completed Opens the form "Assign Request" with Assignee Group, Assignee, Comment, and Time Spent, none of them required. The status becomes Unassigned when only a group is set and Assigned when a new assignee is set. It does not clear the completed date.
Schedule Work Assigned, In Progress, On Hold, Approved, while the scheduled start date or the scheduled end date is empty Opens the form "Schedule Work", which requires the scheduled start date and the scheduled end date and also has Comment and Time Spent. Writes the two dates, logs "Work Scheduled" with the comment, and notifies the collaborators; the status stays.
Log Work Every status except Closed, and only to the service request's assignee Sets In Progress when the service request is Assigned; otherwise the status stays.
Add Comment Every status except Closed, when the service request has no assignee or another assignee Opens the form "Add a Comment", which requires a Comment and also has Publish to Self-Service Portal, which starts cleared, Time Spent, and attachments. The status stays.
Notify Requester Every status except Closed, when you are not the requester The status stays.
Notify Assignee Every status except Closed, when the service request has an assignee other than you The status stays.
Automatic Timer On, Automatic Timer Off Assigned, In Progress, Approved; Automatic Timer On while the timer is stopped, Automatic Timer Off while it is running The status stays.
Complete Request Assigned, In Progress, On Hold, Approved, Rejected Opens the form "Complete Request". Brings the service request to Completed and sets its completed date if it is empty.
Close Request Completed; not to the Service Request Technician role Sets Closed, logs "Marked as Closed", and sends notifications. The form requires a Closure Code.
Place on Hold Assigned, In Progress, Approved Opens the form "Provide a Reason", whose Comment and Time Spent are not required. Sets On Hold and logs "Marked as 'On Hold'".
Take off Hold On Hold Opens the form "Provide a Reason". Sets In Progress, whichever status the service request had before the hold, and logs "Taken off 'On Hold'".
Reopen Request Closed; only to the Administrator (Full), Administrator (Workflow), and Service Request Manager roles Opens the form "Reopen this Request" with the assignee group and the assignee, pre-filled with those of the service request, and Comment and Time Spent. Logs "Request was Reopened" and sets In Progress, or Unassigned when the service request has a group but no assignee, or Assigned when the assignee was changed, in which case the assignee is e-mailed. Clears the completed date and the closure code. Does not run auto-assignment.
Mark Incident Assigned, In Progress Opens the form "Convert to Incident". Sets Closed with the closure code Ticket Converted, sets the completed date if it is empty, logs "Converted Request to Incident", and creates an incident related to the service request, with a copy of the service request's attachments.
Mark Duplicate Every status except Closed Opens the form "Mark Request as Duplicate", which requires Duplicate of. Sets Closed with the closure code Ticket Duplicated and relates the service request to the one it duplicates; see Mark a duplicate.
Create Reservation Every status except Closed, while the related CI is a library item; also to the Library Manager role Opens the form "Create a Reservation". Creates a Pending reservation of the library item for the service request's requester and logs "New Reservation Created"; the status stays.
Use Consumable Assigned, In Progress, Approved, while the related CI is a computer or a hardware item Opens the form "Use a Consumable". Lowers the consumable's quantity and relates the service request to the consumable; the status stays.
Send Meeting Request Every status except Closed Opens the form "Send Meeting Request". E-mails a meeting request to the people in To, CC, and BCC, with a calendar file built from the chosen time, and logs "Meeting request was sent", published to the Self Service Portal; the status stays.
Create Work Order Assigned, In Progress, On Hold, Approved Opens the form "Create a Work Order" and creates a work order whose parent is the service request; the status of the service request stays. See Create a work order from a service request.
Create Approval Assigned, In Progress Creates an approval stage; the status stays.
Request Approval Assigned, In Progress, while the service request has a pending approval stage and a pending approval request Sets Pending Approval.
Approve Request, Reject Request Pending Approval, and only to a pending approver of the pending approval stage Records the vote; the action itself leaves the status as it is.
Cancel Approvals Assigned, In Progress, Pending Approval, while an approval stage is Pending or Pending Approval; only to the Administrator (Full), Administrator (Workflow), and Approval Manager roles Sets the approval stages that are Pending or Pending Approval, and their pending approval requests, to Not Required, and returns the service request to In Progress.

For the approval actions, see Approvals. For the Log Work form, the automatic timer, Notify Requester, and Notify Assignee, see Work on a Ticket.

The close action changes only the service request itself: its work orders and approvals stay as they are, and no warning appears when the service request still has open work orders.

Actions in the Web App

In the Web App, the Action Bar of a service request's full form shows these actions in these sections (listed here in alphabetical order):

Section Actions
Approvals Approve Request, Cancel Approvals, Create Approval, Reject Request, Request Approval
Communication Add Comment, Automatic Timer Off, Automatic Timer On, Log Work, Notify Assignee, Notify Requester, Send Meeting Request
General Assign to..., Assign to me, Close Request, Complete Request, Place on Hold, Reopen Request, Schedule Work, Take off Hold
Relationships Create Reservation, Create Work Order, Use Consumable

In the Web App, Collaborators, Copy Request, Follow, Mark Duplicate, Mark Incident, and Unfollow are not on the Action Bar; they are only on the form's toolbar. In a Web App list of service requests, the toolbar's Actions menu offers all of these actions, including the ones that are only on the form's toolbar, and each of them except Copy Request can run on several selected service requests. See Perform Actions on Records.

Automatic status changes

  • When an Assigned service request is saved while you are its assignee, it moves to In Progress.
  • When a service request is completed, its child work orders that are not Closed are set to Completed.
  • When the last of a service request's work orders that is not Closed is completed, the service request becomes Completed. This rule and the one above are each controlled by a workflow parameter of their own, and both are turned on in the supplied configuration.
  • While the workflow parameter Auto Assignment After Hours Handling is set to Auto-Assign Next Business Day and the workflow parameter Assignee Load Balancing Method is not set to Disable Load Balancing, as in the supplied configuration, a service request that is Unassigned is checked every 15 minutes during the hours of the Default Work Calendar: the activity "Auto-Assign Next Business Day" is logged, the service request's service is set to the service of its catalog item, and auto-assignment runs again. The service request becomes Assigned when that sets an assignee; otherwise it stays Unassigned. This check also picks up a service request that was created when no member of its group was available, or that was reopened without an assignee.
  • A service request that stays Completed without changes for the number of days in its workflow parameter is closed automatically. The day count is set to 14 in the supplied configuration, and a value of 0 turns the automatic closing off. The activity logged gives the number of days, for example "Automatically Closed after 14 day(s)".