Task Managementoperational
Service Requests & Unit Services
How are service requests logged and turned into assigned tasks?
Organization units publish the services they provide as a catalog, each service carrying predefined service tasks. A service request records the partner, the service, and the assigned employee — and generates the task that gets worked.
The sequence
5 stepsDefine unit services
Each unit catalogs its services with a type and a set of predefined service tasks.
Log the request
Record the partner, the requested employee where relevant, the service, and the employee assigned to deliver.
Generate the task
Pick one of the service’s predefined tasks or name a new one; the task record is created with its service-request link.
Work and track it
The generated task moves through statuses and activity reporting like any other task record.
Review the history
The request screen lists prior service requests per partner, keeping the client’s service record in one view.
How it works
The service catalog is maintained per organization unit: each service has a name, a description, an owning unit, and a service type from configured lookup values, plus a set of predefined service tasks that describe the standard work items the service involves.
A service request is the intake record. It names the partner or client, optionally the requested employee, the service being asked for, and the employee assigned to deliver it. The task itself either comes from the service’s predefined tasks — the form offers the tasks generated by the selected service — or is named ad hoc for this request, with free-text details attached.
Once saved, the generated task lands in the task register carrying its service-request link, and works like any other task: statuses, activities, documents, and time capture. The request screen keeps a history per partner, so what a client has asked for and received is readable in one place.
Worth knowing
- Per-unit service catalogServices belong to organization units, with a service type from configured lookup values and their own descriptions.
- Predefined service tasksEach service carries standard task definitions, offered at request time as the tasks generated by the selected service.
- Assignment at intakeThe request names the delivering employee, drawn from those available for the selected service task’s unit.
- Requests become task recordsThe generated task keeps its service-request link and runs the normal task lifecycle from there.
- Partner service historyRequests list per partner, so the service relationship with each client is reviewable without a report.
What this touches
- Organization model
Services are owned by organization units, and assignment pools resolve through the unit structure. - Human Capital Management
Requested and assigned employees are employee records, filtered by the service task’s unit. - System Administration
Service types are maintained as configurable lookup values. - Project Management
Service-generated tasks sit in the same task register as project tasks, with one execution model.
See service requests & unit services running in continON.
A guided walkthrough on a sanitized demo tenant — this capability inside its module, on the shared platform.