Skip to Content

Field Service

by ,
Odoo 5
v 11.0 v 12.0 Third Party 3306
Download for v 12.0 Deploy on Odoo.sh
Availability
Odoo Online
Odoo.sh
On Premise
Odoo Apps Dependencies • Contacts (contacts)
• Discuss (mail)
Community Apps Dependencies
Lines of code 5656
Technical Name fieldservice
LicenseAGPL-3
Websitehttps://github.com/OCA/field-service
Versions 11.0 12.0 13.0 14.0 15.0 16.0
You bought this module and need support? Click here!

Field Service

Beta License: AGPL-3 OCA/field-service Translate me on Weblate Try me on Runboat

This module is the base of the Field Service application in Odoo.

Table of contents

Installation

As of version 12, you can install Field Service alone without mapping features.

To install Field Service and have the mapping features, you need to install GeoEngine. GeoEngine requires you to have PostGIS installed and also install two additional python libs:

  • Shapely
  • geojson

Please refer to the installation instructions available at: https://github.com/OCA/geospatial/tree/12.0/base_geoengine

Configuration

The base Field Service module can be used with minimal initial configuration. It also allows for many advanced features, which require a more in-depth configuration.

Order Stages

The stage of an order is used to monitor its progress. Stages can be configured based on your company’s specific business needs. A basic set of order stages comes pre-configured for use.

  1. Go to Field Service > Configuration > Stages
  2. Create or edit a stage
  3. Set the name for the stage.
  4. Set the sequence order for the stage.
  5. Select Order type to apply this stage to your orders.
  6. Additonally, you can set a color for the stage.

You need to add attribute mention below with the tag <timeline> as base element.

  • colors (optional): it allows to set certain specific colors if the expressed condition (JS syntax) is met.
  • custom_color (optional): it allows to set custom color for fsm.stages example custom_color = “true”. And there is minor condition to follow to implement this as. Define any one stage color condition like colors=”#ffffff:stage_id==’New’;”

Field Service Areas

You can manage designated areas or locales for your field service workers, salesmen, and other resources. For example, salesmen may serve a particular Territory. There may be multiple Territories served by a single Branch office location. Multiple Branches are managed within a District and these Districts are managed under an encompassing Region.

Setup a Territory

  1. Go to Field Service > Configuration > Locations > Territories
  2. Create or select a territory
  3. Set the territory Name and description
  4. Select or create a branch which this territory serves
  5. Choose a type of zip, state, or country whichs defines the boundary used
  6. Input a list of zip codes, states, or countries based on your desired configuration

Setup Branches, Districts, and Regions

If your business requires, define your Branches, Districts, and Regions. These are found under Field Service > Configuration > Locations

Advanced Configurations

Additional features, automations, and GeoEngine features can be enabled in the General Settings panel for Field Service.

  1. Go to Field Service > Configuration > Settings
  2. Enable additional options
  3. Configure new options

Manage Teams

Teams can be used to organize the processing of field service orders into groups. Different teams may have different workflows that a field service order needs to follow.

  1. Go to Field Service > Configuration > Workers > Teams
  2. Create or select a team
  3. Set the team name, description, and sequence

You can now define custom stages for each team processing orders.

  1. Go to Field Service > Configuration > Stages
  2. Create or edit a stage
  3. Select the teams for which this stage should be used

Manage Categories

Categories are used to group workers and the type of orders a worker can do.

  1. Go to Field Service > Configuration > Workers > Categories
  2. Create or select a category
  3. Set the name and description of category
  4. Additionally, you can select a parent category if required

Manage Tags

Tags can be used to filter and report on field service orders

  1. Go to Field Service > Configuration > Orders > Tags
  2. Create or select a tag
  3. Set the tag name
  4. Set a color index for the tag

Manage Order Templates

Order templates allow you to create standard templates for your orders.

  1. Go to Field Service > Master Data > Templates
  2. Create or select a template
  3. Set the name
  4. Set the standard order instructions

Usage

To use this module, you need to:

Add Field Service Locations

Locations are the specific places where a field service order is performed.

  1. Go to Field Service > Master Data > Locations
  2. Create a location

Add Field Service Workers

Workers are the people responsible for performing a field service order. These workers may be subcontractors or a company’s own employees.

  1. Go to Field Service > Master Data > Workers
  2. Create a worker

Process Orders

Once you have established your data, you can begin processing field service orders.

  1. Go to Field Service > Dashboard > Orders
  2. Create or select an order
  3. Enter relevant details for the order
  4. Process order through each stage as defined by your business requirements

Known issues / Roadmap

The roadmap of the Field Service application is documented on Github.

Bug Tracker

Bugs are tracked on GitHub Issues. In case of trouble, please check there if your issue has already been reported. If you spotted it first, help us to smash it by providing a detailed and welcomed feedback.

Do not contact contributors directly about support or help with technical issues.

Credits

Authors

  • Open Source Integrators

Other credits

The development of this module has been financially supported by:

  • Open Source Integrators <https://opensourceintegrators.com>

Maintainers

This module is maintained by the OCA.

Odoo Community Association

OCA, or the Odoo Community Association, is a nonprofit organization whose mission is to support the collaborative development of Odoo features and promote its widespread use.

Current maintainers:

wolfhall max3903

This module is part of the OCA/field-service project on GitHub.

You are welcome to contribute. To learn how please visit https://odoo-community.org/page/Contribute.

Please log in to comment on this module

  • The author can leave a single reply to each comment.
  • This section is meant to ask simple questions or leave a rating. Every report of a problem experienced while using the module should be addressed to the author directly (refer to the following point).
  • If you want to start a discussion with the author, please use the developer contact information. They can usually be found in the description.
Please choose a rating from 1 to 5 for this module.
Bug Report
by
Darryl Gulson
on 8/24/20, 4:59 AM

Error when attempting to select a location when opening a new Field Service Order..

"Error:

Uncaught TypeError: value.split is not a function


http://****:8069/web/content/418-6f266d6/web.assets_backend.js:1213

Traceback:

TypeError: value.split is not a function

    at Class._getDisplayName (http://****:8069/web/content/418-6f266d6/web.assets_backend.js:1213:101)

    at http://****:8069/web/content/418-6f266d6/web.assets_backend.js:1218:219

    at Function._.map._.collect (http://****:8069/web/content/402-2cf107d/web.assets_common.js:13:270)

    at Object.<anonymous> (http://****:8069/web/content/418-6f266d6/web.assets_backend.js:1218:186)

    at Object.<anonymous> (http://****:8069/web/content/402-2cf107d/web.assets_common.js:802:681)

    at fire (http://****:8069/web/content/402-2cf107d/web.assets_common.js:796:299)

    at Object.fireWith [as resolveWith] (http://****:8069/web/content/402-2cf107d/web.assets_common.js:801:198)

    at Object.deferred.<computed> [as resolve] (http://****:8069/web/content/402-2cf107d/web.assets_common.js:803:56)

    at Object.<anonymous> (http://****:8069/web/content/402-2cf107d/web.assets_common.js:3589:448)

    at Object.<anonymous> (http://****:8069/web/content/402-2cf107d/web.assets_common.js:802:681)"

There are no comments yet!