Skip to main content

Field Service

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

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:

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 smashing 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

Contributors

Other credits

The development of this module has been financially supported by:

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.

Metadata

Release files for odoo12-addon-fieldservice 12.0.2.21.1

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Built distribution (wheel)

Table of built distributions (wheels) for odoo12-addon-fieldservice 12.0.2.21.1
File Interpreter ABI Platform
odoo12_addon_fieldservice-12.0.2.21.1-py3-none-any.whl Python 3 none any Details

Release files / odoo12_addon_fieldservice-12.0.2.21.1-py3-none-any.whl

Download URL odoo12_addon_fieldservice-12.0.2.21.1-py3-none-any.whl
Size 289.4 kB
Tags Python 3
SHA-256 checksum
How to use checksums
f45b46390f41988e8730ce0be4a1321a176941656eab8cdc59eec231e44dd0cc
BLAKE2b-256 checksum
How to use checksums
63c6ab42ff1486c2bc72d9cff749ccb5cc3618b2b8c540891a821cc2853877eb
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
No
Uploaded via twine/4.0.1 CPython/3.8.5

Release history Release notifications | RSS feed

This release

12.0.2.21.1 This release

1 release file

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page