Service Setup Lists

Five short lists describe how your service work is organised. They are used later on service orders and repair lines, so fill them in before you start receiving devices.

List	What it holds	Example
Service tasks	Named pieces of work that group lines on an order, so the technician and the customer see what is being done.	REPLACE-CAP: Replace the DC capacitor bank
Service stage reason codes	The explanations a user picks when moving an order to another stage.	DECLINED: Customer declined the quote
Service repair conditions	The situation in which a fault shows up, recorded on a repair line.	AFTER-CUT: After a power cut
Service repair resolutions	The outcome of a repair, recorded when a repair line is closed.	REPLACED: Part replaced
Service repair stages	The progress of one repair line.	WAITING: Waiting for parts

All five work like Service object groups: the same page layout, the same rules for the Code and Description, and the same toolbar. Read that guide for the step-by-step instructions; the differences are listed below.

Opening a list

Go to Service management > Setup and choose the list:

• Service tasks
• Service stage reason codes
• Service repair conditions
• Service repair resolutions
• Service repair stages

Each page needs its own privilege: read to see it, create to add, change or delete entries (for example read service tasks and create service tasks). Ask your system administrator to grant them to your role (see Roles). A role can maintain one list without the others.

The rules, in short

• Code: 1 to 20 letters, digits, hyphens or underscores. Saved in capital letters. Must be new in that list. Cannot be changed afterwards.
• Description: required, up to 200 characters. You can change it at any time.
• The same code can exist in different lists (a task OTHER and a condition OTHER).

Deleting an entry

Select the row and choose Delete. An entry that is already used cannot be deleted. You see a message such as The service task REPLACE-CAP is used by 4 record(s) and cannot be deleted. Change those records first, or keep the entry and edit its description instead.

Choosing what to put in each list

Service tasks

• Name the job, not the part: "Replace DC capacitor bank", "Clean and inspect".
• Keep the list short. A task that is used once is better typed as a line description.

Service stage reason codes

• Think of the questions you will be asked later: Why was this order cancelled? Why did it go back a stage? Typical entries: customer declined the quote, waiting for a part, not repairable, customer did not collect.
• A stage can be set to require a reason, so these entries appear exactly where your team needs to explain a decision.

Service repair conditions

• Record when the fault happens, independent of what part is affected: after a power cut, when hot, after a firmware update, intermittent.
• Good conditions help you notice patterns, such as many inverters failing after power cuts.

Service repair resolutions

• Describe how the repair ended: repaired, part replaced, no fault found, beyond economical repair, cancelled by customer.
• Reports can then show how many jobs end each way, for example how many TVs end as "beyond economical repair".

Service repair stages

• These track one repair line, while a service stage tracks the whole order. Typical stages: Open, Waiting for parts, Finished.
• The Finished column is a tick box on the row. A stage with Finished ticked closes any repair line that is moved into it, and the finish time is recorded. Tick it on exactly the stage(s) that mean "this repair is done", such as Finished.
• You can change the Finished tick later by editing the row. The code still cannot change.

If something goes wrong

The messages are the same as for Service object groups, with the name of the list in them. The one addition is the is used by … record(s) message above.