Skip to main content

Add sub-statuses to Field Service orders

Project description

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

Odoo and the Field Service App do not provide a way to track what is required and/or missing at the different stages of the FSM order process. Some organizations needs a way to track documentation, materials, signature and various activities.

This module allows you to have a list of sub-statuses and set them as default or potential sub-statuses on each FSM stage. The stage configuration will drive:

  • the sub-status set when entering a stage

  • the list of potential sub-statuses available depending on the stage

Table of contents

Installation

To install Field Service and have the mapping features, you need to install GeoEngine.

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

Configuration

To configure this module, you need to:

  • Go to Field Service > Configuration > Orders > Sub-Statuses

  • Create your list of sub-statuses

  • Go to Field Service > Configuration > Orders > Stages

  • Select a stage and set the default sub-statuses as well as the potential sub-statuses

Usage

To use this module, you need to:

  • Go to Field Service > Operations > Orders

  • Create a new service order.

    • The sub-status is set to the default sub-status of the New stage.

    • The list of sub-statuses is filtered based on the potential sub-statuses of the New stage.

  • Move the service order in the process. The sub-status is set and filtered according to the stage.

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

  • Brian McMaster

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:

max3903 brian10048 bodedra

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.

Project details


Download files

Download the file for your platform. If you're not sure which to choose, learn more about installing packages.

Source Distributions

No source distribution files available for this release.See tutorial on generating distribution archives.

Built Distribution

File details

Details for the file odoo12_addon_fieldservice_substatus-12.0.1.2.1-py3-none-any.whl.

File metadata

File hashes

Hashes for odoo12_addon_fieldservice_substatus-12.0.1.2.1-py3-none-any.whl
Algorithm Hash digest
SHA256 7c7b5c4376365b98f70a54d259493929fe22ccc082fa6fd9918913f4ff33400a
MD5 071d129edd1e007019c0a73438e34769
BLAKE2b-256 d0724d529ef06b5ee60143989db4a9047cd5cb3ea5c72b5152c5e2ce57921e41

See more details on using hashes here.

Supported by

AWS AWS Cloud computing and Security Sponsor Datadog Datadog Monitoring Fastly Fastly CDN Google Google Download Analytics Microsoft Microsoft PSF Sponsor Pingdom Pingdom Monitoring Sentry Sentry Error logging StatusPage StatusPage Status page