Audience: Dispatchers and administrators
Outcome causes define what options field technicians can use to debrief and close work orders (WO). When you configure outcome causes, you ensure that data, such as why a job was completed or why it failed, is standardized when it is collected from the field.
Prerequisite
Before you start, to understand more about outcomes, see Configure outcomes.
Follow the UI path
All following instructions start from this system path:
Configuration > Core > Work Order Management > Accounting
Create a new outcome cause
You can create the specific causes available to the technicians.
-
In the left panel, click Accounting > Outcome Causes.
-
At the bottom, click + New.
-
Fill out the following mandatory fields:
-
Code: Enter a unique alphanumeric identifier.
-
Description: Enter a clear name for the outcome cause.
-
Class: Select the appropriate class from the dropdown.
-
Cause type: Define if this is a standard or emergency outcome cause.
-
Outcome type: Choose the type, such as “Success” or “Failure”.
-
Membership: Choose if a cause is internal, external, or both.
-
-
Click Insert.
Manage outcome rules and logic
Optionally, you can define how these outcomes impact the status of the WO or trigger follow-up actions:
-
In the left panel, click Accounting > Outcome Causes.
-
Click the Three dots menu for a specific cause.
-
To define parameters, such as closures, triggers, or requirements, select Edit rules.
-
Enter the required logic values.
-
Click Save.
Link outcome causes to intervention groups
To define which technical data sheets appear in FSM Mobile based on the selected outcome:
-
In the left panel, click Accounting > Intervention Groups.
-
In the Search tab, enter any desired parameters.
-
Click Search.
-
Next to the group you want to associate, click the Three dots menu.
-
Select Edit rules.
-
In the Intervention group application rules window, click + New rule.
-
In the Rules management page, click all applicable rule application parameters in these tables:
-
Activities: Select the category, like “Success” or “Failure”.
-
Service types: Specify if it is a standard or specific cause.
-
Outcome causes: Select the exact cause that should trigger this group.
-
For example, a cause could be "Meter replaced".
-
-
-
Click Insert.
Link outcome causes to activity types
To define which outcomes are available for a specific type of work:
-
In the left panel, click Accounting > Outcome Causes.
-
Next to the outcome you want to associate, click the Associate encoded notes with outcome causes icon.
-
In the Outcome cause window, drag the relevant notes from the Non-associated notes column into the Associated notes column.
-
Click Save.
What’s next
-
To add a new reason a technician can use to debrief, see Configure outcome causes.
-
To add a new outcome cause type that groups interventions together, see Create outcome cause types.
-
To configure how the system reacts when you override skills, see Configure outcome causes for override skills.