Service Request Status Workflows
Service Request Status Workflows (Document Status Workflows) let you define your own status sequences for Service Requests, instead of using a single flat list of statuses for every request. Each workflow groups, in the order you choose, statuses from the Service Request Statuses catalog that apply to a type of case (for example, "Preventive Maintenance", "Repair" or "Warranty"), and you then link each Service Request to the workflow that fits it.
What is it and what is it for?
A Status Workflow is simply a name plus an ordered list of statuses (taken from the Service Request Statuses catalog). It's meant to organize your service processes when you handle different types of cases that shouldn't necessarily share the exact same steps: a warranty repair may need a "Warranty Evaluation" status that doesn't make sense on a routine preventive maintenance job, for example.
Each Service Request is linked to a single workflow. As long as that link exists, the system protects data integrity: you can't delete the workflow, nor remove a status from it that some request currently has assigned.
How to use it
- Open the "Service Request Status Workflows" list (Customization), where you'll see each workflow with its Name and whether it's Inactive.
- Create a new workflow with the New button, entering its Name and, optionally, Notes.
- Add the statuses that make up the workflow on the "Document Status" tab: click a row to search for a status through autocomplete. The table starts with 3 empty rows, and you can add more with the insert (+) button or remove a row with the delete (–) button.
- Reorder the statuses by dragging them (drag-and-drop) into the order you want your service team to see them.
- Save the workflow. It becomes immediately available to link to Service Requests.
- Link the workflow to a Service Request: when creating or editing a request, select the workflow in the "Status Workflow" field. You can also change it afterward from the Change Status Workflow button on the request's detail screen.
- View, duplicate or delete an existing workflow from its Details screen, using the Edit, Duplicate and Delete toolbar buttons.
Key capabilities
- Unlimited workflows, each with its own combination and order of statuses.
- Drag-and-drop reordering of statuses inside a workflow, without having to re-enter them.
- Duplicating an existing workflow as a starting point to build a similar variant.
- An Inactive flag to retire a workflow from selection lists without losing its history or affecting requests that already use it.
- Changing the workflow of an already-created Service Request, from a direct menu on its Details screen.
- Integrity protection: a workflow can't be deleted, and a status can't be removed from it, while Service Requests still depend on that setup.
Key fields
| Field | What it's for |
|---|---|
| Name | Identifies the workflow (for example, "Repair"). Required, up to 200 characters. Can't be repeated between workflows. |
| Notes | Free text to explain to your team when to use this workflow. |
| Inactive | Hides the workflow from autocomplete lists when creating new Service Requests, without deleting it or affecting requests that already use it. |
| Document Status | Detail table with the statuses (from the Service Request Statuses catalog) that make up the workflow, in the order you dragged them into. Must include at least one. |
Validations on save
- Name is required.
- No other workflow can have the same Name.
- The workflow must include at least one Document Status. A workflow with no statuses can't be saved.
- If the workflow repeats the same status in more than one row, it's kept only once.
- A status can't be removed from the workflow while some linked Service Request currently has it assigned. The system shows up to 5 affected requests so you can fix them first.
- A workflow can't be deleted while there are Service Requests linked to it. The system shows up to 5 affected requests.
Availability
- Browsing, creating, editing and deleting Status Workflows requires the "Service Request Status Workflows" permission (Customization module) on your user group.
- This feature is only available on the Enterprise plan, with the Service module active on your company, and also requires the feature to be specifically enabled for your account.
- If you don't see this option under Customization, or the "Change Status Workflow" button on your Service Requests, contact AdmCloud support to confirm whether it can be enabled for your account.
Tips and common mistakes
Create the Service Request Statuses you need first in their own catalog, then build your Workflows by combining them: that way you can reuse the same status (for example, "Pending" or "Closed") across several different workflows instead of duplicating it.
Use "Duplicate" to create variants of an existing workflow (for example, a version of "Repair" with an extra parts-approval status) instead of building it from scratch.
A status in use can't be removed or deleted. If editing a workflow throws a dependency error, check the list of requests it mentions: change their status or workflow first, then retry the edit.
Mark it Inactive instead of deleting it when a workflow shouldn't be used on new requests but is still linked to older ones; deleting it will fail while those dependencies exist.