=============
Field Service
=============
..
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!! This file is generated by oca-gen-addon-readme !!
!! changes will be overwritten. !!
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!! source digest: sha256:f91345d87ff6f94627a220e9783b7ea879f72ba1ee4c44d50e5b28489205d597
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
.. |badge1| image:: https://img.shields.io/badge/maturity-Production%2FStable-green.png
:target: https://odoo-community.org/page/development-status
:alt: Production/Stable
.. |badge2| image:: https://img.shields.io/badge/licence-AGPL--3-blue.png
:target: http://www.gnu.org/licenses/agpl-3.0-standalone.html
:alt: License: AGPL-3
.. |badge3| image:: https://img.shields.io/badge/github-OCA%2Ffield--service-lightgray.png?logo=github
:target: https://github.com/OCA/field-service/tree/14.0/fieldservice
:alt: OCA/field-service
.. |badge4| image:: https://img.shields.io/badge/weblate-Translate%20me-F47D42.png
:target: https://translation.odoo-community.org/projects/field-service-14-0/field-service-14-0-fieldservice
:alt: Translate me on Weblate
.. |badge5| image:: https://img.shields.io/badge/runboat-Try%20me-875A7B.png
:target: https://runboat.odoo-community.org/builds?repo=OCA/field-service&target_branch=14.0
:alt: Try me on Runboat
|badge1| |badge2| |badge3| |badge4| |badge5|
This module is the base of the Field Service application in Odoo.
**Table of contents**
.. contents::
:local:
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.
#. Go to *Field Service > Configuration > Stages*
#. Create or edit a stage
#. Set the name for the stage.
#. Set the sequence order for the stage.
#. Select *Order* type to apply this stage to your orders.
#. Additonally, you can set a color for the stage.
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
-----------------
#. Go to Settings > Users & Companies > Territories*
#. Create or select a territory
#. Set the territory Name and description
#. Select or create a branch which this territory serves
#. Choose a type of zip, country whichs defines the boundary used
#. Input a list of zip codes, 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.
#. Go to *Field Service > Configuration > Settings*
#. Enable additional options
#. 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.
#. Go to *Field Service > Configuration > Workers > Teams*
#. Create or select a team
#. Set the team name, description, and sequence
You can now define custom stages for each team processing orders.
#. Go to *Field Service > Configuration > Stages*
#. Create or edit a stage
#. 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.
#. Go to *Field Service > Configuration > Workers > Categories*
#. Create or select a category
#. Set the name and description of category
#. Additionally, you can select a parent category if required
Manage Tags
-----------
Tags can be used to filter and report on field service orders
#. Go to *Field Service > Configuration > Orders > Tags*
#. Create or select a tag
#. Set the tag name
#. Set a color index for the tag
Manage Order Templates
----------------------
Order templates allow you to create standard templates for your orders.
#. Go to *Field Service > Master Data > Templates*
#. Create or select a template
#. Set the name
#. 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.
#. Go to *Field Service > Master Data > Locations*
#. 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.
#. Go to *Field Service > Master Data > Workers*
#. Create a worker
Process Orders
~~~~~~~~~~~~~~
Once you have established your data, you can begin processing field service
orders.
#. Go to *Field Service > Dashboard > Orders*
#. Create or select an order
#. Enter relevant details for the order
#. 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 <https://github.com/OCA/field-service/issues/1>`_.
Bug Tracker
===========
Bugs are tracked on `GitHub Issues <https://github.com/OCA/field-service/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 <https://github.com/OCA/field-service/issues/new?body=module:%20fieldservice%0Aversion:%2014.0%0A%0A**Steps%20to%20reproduce**%0A-%20...%0A%0A**Current%20behavior**%0A%0A**Expected%20behavior**>`_.
Do not contact contributors directly about support or help with technical issues.
Credits
=======
Authors
~~~~~~~
* Open Source Integrators
Contributors
~~~~~~~~~~~~
* Wolfgang Hall <whall@opensourceintegrators.com>
* Maxime Chambreuil <mchambreuil@opensourceintegrators.com>
* Steve Campbell <scampbell@opensourceintegrators.com>
* Bhavesh Odedra <bodedra@opensourceintegrators.com>
* Michael Allen <mallen@opensourceintegrators.com>
* Sandip Mangukiya <smangukiya@opensourceintegrators.com>
* Serpent Consulting Services Pvt. Ltd. <support@serpentcs.com>
* Brian McMaster <brian@mcmpest.com>
* Raphaƫl Reverdy <raphael.reverdy@akretion.com>
* Ammar Officewala <ammar.o.serpentcs@gmail.com>
* Yves Goldberg <yves@ygol.com>
* Alex Comba <alex.comba@agilebg.com>
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.
.. image:: https://odoo-community.org/logo.png
:alt: Odoo Community Association
:target: https://odoo-community.org
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.
.. |maintainer-wolfhall| image:: https://github.com/wolfhall.png?size=40px
:target: https://github.com/wolfhall
:alt: wolfhall
.. |maintainer-max3903| image:: https://github.com/max3903.png?size=40px
:target: https://github.com/max3903
:alt: max3903
Current `maintainers <https://odoo-community.org/page/maintainer-role>`__:
|maintainer-wolfhall| |maintainer-max3903|
This module is part of the `OCA/field-service <https://github.com/OCA/field-service/tree/14.0/fieldservice>`_ project on GitHub.
You are welcome to contribute. To learn how please visit https://odoo-community.org/page/Contribute.
Raw data
{
"_id": null,
"home_page": "https://github.com/OCA/field-service",
"name": "odoo14-addon-fieldservice",
"maintainer": "",
"docs_url": null,
"requires_python": ">=3.6",
"maintainer_email": "",
"keywords": "",
"author": "Open Source Integrators, Odoo Community Association (OCA)",
"author_email": "support@odoo-community.org",
"download_url": "",
"platform": null,
"description": "=============\nField Service\n=============\n\n.. \n !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!\n !! This file is generated by oca-gen-addon-readme !!\n !! changes will be overwritten. !!\n !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!\n !! source digest: sha256:f91345d87ff6f94627a220e9783b7ea879f72ba1ee4c44d50e5b28489205d597\n !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!\n\n.. |badge1| image:: https://img.shields.io/badge/maturity-Production%2FStable-green.png\n :target: https://odoo-community.org/page/development-status\n :alt: Production/Stable\n.. |badge2| image:: https://img.shields.io/badge/licence-AGPL--3-blue.png\n :target: http://www.gnu.org/licenses/agpl-3.0-standalone.html\n :alt: License: AGPL-3\n.. |badge3| image:: https://img.shields.io/badge/github-OCA%2Ffield--service-lightgray.png?logo=github\n :target: https://github.com/OCA/field-service/tree/14.0/fieldservice\n :alt: OCA/field-service\n.. |badge4| image:: https://img.shields.io/badge/weblate-Translate%20me-F47D42.png\n :target: https://translation.odoo-community.org/projects/field-service-14-0/field-service-14-0-fieldservice\n :alt: Translate me on Weblate\n.. |badge5| image:: https://img.shields.io/badge/runboat-Try%20me-875A7B.png\n :target: https://runboat.odoo-community.org/builds?repo=OCA/field-service&target_branch=14.0\n :alt: Try me on Runboat\n\n|badge1| |badge2| |badge3| |badge4| |badge5|\n\nThis module is the base of the Field Service application in Odoo.\n\n**Table of contents**\n\n.. contents::\n :local:\n\nConfiguration\n=============\n\nThe base Field Service module can be used with minimal initial configuration.\nIt also allows for many advanced features, which require a more in-depth\nconfiguration.\n\nOrder Stages\n~~~~~~~~~~~~\n\nThe stage of an order is used to monitor its progress. Stages can be configured\nbased on your company's specific business needs. A basic set of order stages\ncomes pre-configured for use.\n\n#. Go to *Field Service > Configuration > Stages*\n#. Create or edit a stage\n#. Set the name for the stage.\n#. Set the sequence order for the stage.\n#. Select *Order* type to apply this stage to your orders.\n#. Additonally, you can set a color for the stage.\n\nField Service Areas\n~~~~~~~~~~~~~~~~~~~\n\nYou can manage designated areas or locales for your field service workers,\nsalesmen, and other resources. For example, salesmen may serve a particular\nTerritory. There may be multiple Territories served by a single Branch office\nlocation. Multiple Branches are managed within a District and these Districts\nare managed under an encompassing Region.\n\nSetup a Territory\n-----------------\n\n#. Go to Settings > Users & Companies > Territories*\n#. Create or select a territory\n#. Set the territory Name and description\n#. Select or create a branch which this territory serves\n#. Choose a type of zip, country whichs defines the boundary used\n#. Input a list of zip codes, countries based on your desired\n configuration\n\nSetup Branches, Districts, and Regions\n--------------------------------------\n\nIf your business requires, define your Branches, Districts, and Regions.\nThese are found under *Field Service > Configuration > Locations*\n\nAdvanced Configurations\n~~~~~~~~~~~~~~~~~~~~~~~\n\nAdditional features, automations, and GeoEngine features can be enabled in\nthe General Settings panel for Field Service.\n\n#. Go to *Field Service > Configuration > Settings*\n#. Enable additional options\n#. Configure new options\n\nManage Teams\n------------\n\nTeams can be used to organize the processing of field service orders into\ngroups. Different teams may have different workflows that a field service\norder needs to follow.\n\n#. Go to *Field Service > Configuration > Workers > Teams*\n#. Create or select a team\n#. Set the team name, description, and sequence\n\nYou can now define custom stages for each team processing orders.\n\n#. Go to *Field Service > Configuration > Stages*\n#. Create or edit a stage\n#. Select the teams for which this stage should be used\n\nManage Categories\n-----------------\n\nCategories are used to group workers and the type of orders a worker can do.\n\n#. Go to *Field Service > Configuration > Workers > Categories*\n#. Create or select a category\n#. Set the name and description of category\n#. Additionally, you can select a parent category if required\n\nManage Tags\n-----------\n\nTags can be used to filter and report on field service orders\n\n#. Go to *Field Service > Configuration > Orders > Tags*\n#. Create or select a tag\n#. Set the tag name\n#. Set a color index for the tag\n\nManage Order Templates\n----------------------\n\nOrder templates allow you to create standard templates for your orders.\n\n#. Go to *Field Service > Master Data > Templates*\n#. Create or select a template\n#. Set the name\n#. Set the standard order instructions\n\nUsage\n=====\n\nTo use this module, you need to:\n\nAdd Field Service Locations\n~~~~~~~~~~~~~~~~~~~~~~~~~~~\n\nLocations are the specific places where a field service order is performed.\n\n#. Go to *Field Service > Master Data > Locations*\n#. Create a location\n\nAdd Field Service Workers\n~~~~~~~~~~~~~~~~~~~~~~~~~\n\nWorkers are the people responsible for performing a field service order.\nThese workers may be subcontractors or a company's own employees.\n\n#. Go to *Field Service > Master Data > Workers*\n#. Create a worker\n\nProcess Orders\n~~~~~~~~~~~~~~\n\nOnce you have established your data, you can begin processing field service\norders.\n\n#. Go to *Field Service > Dashboard > Orders*\n#. Create or select an order\n#. Enter relevant details for the order\n#. Process order through each stage as defined by your business requirements\n\nKnown issues / Roadmap\n======================\n\nThe roadmap of the Field Service application is documented on\n`Github <https://github.com/OCA/field-service/issues/1>`_.\n\nBug Tracker\n===========\n\nBugs are tracked on `GitHub Issues <https://github.com/OCA/field-service/issues>`_.\nIn case of trouble, please check there if your issue has already been reported.\nIf you spotted it first, help us to smash it by providing a detailed and welcomed\n`feedback <https://github.com/OCA/field-service/issues/new?body=module:%20fieldservice%0Aversion:%2014.0%0A%0A**Steps%20to%20reproduce**%0A-%20...%0A%0A**Current%20behavior**%0A%0A**Expected%20behavior**>`_.\n\nDo not contact contributors directly about support or help with technical issues.\n\nCredits\n=======\n\nAuthors\n~~~~~~~\n\n* Open Source Integrators\n\nContributors\n~~~~~~~~~~~~\n\n* Wolfgang Hall <whall@opensourceintegrators.com>\n* Maxime Chambreuil <mchambreuil@opensourceintegrators.com>\n* Steve Campbell <scampbell@opensourceintegrators.com>\n* Bhavesh Odedra <bodedra@opensourceintegrators.com>\n* Michael Allen <mallen@opensourceintegrators.com>\n* Sandip Mangukiya <smangukiya@opensourceintegrators.com>\n* Serpent Consulting Services Pvt. Ltd. <support@serpentcs.com>\n* Brian McMaster <brian@mcmpest.com>\n* Rapha\u00ebl Reverdy <raphael.reverdy@akretion.com>\n* Ammar Officewala <ammar.o.serpentcs@gmail.com>\n* Yves Goldberg <yves@ygol.com>\n* Alex Comba <alex.comba@agilebg.com>\n\nOther credits\n~~~~~~~~~~~~~\n\nThe development of this module has been financially supported by:\n\n* Open Source Integrators <https://opensourceintegrators.com>\n\nMaintainers\n~~~~~~~~~~~\n\nThis module is maintained by the OCA.\n\n.. image:: https://odoo-community.org/logo.png\n :alt: Odoo Community Association\n :target: https://odoo-community.org\n\nOCA, or the Odoo Community Association, is a nonprofit organization whose\nmission is to support the collaborative development of Odoo features and\npromote its widespread use.\n\n.. |maintainer-wolfhall| image:: https://github.com/wolfhall.png?size=40px\n :target: https://github.com/wolfhall\n :alt: wolfhall\n.. |maintainer-max3903| image:: https://github.com/max3903.png?size=40px\n :target: https://github.com/max3903\n :alt: max3903\n\nCurrent `maintainers <https://odoo-community.org/page/maintainer-role>`__:\n\n|maintainer-wolfhall| |maintainer-max3903| \n\nThis module is part of the `OCA/field-service <https://github.com/OCA/field-service/tree/14.0/fieldservice>`_ project on GitHub.\n\nYou are welcome to contribute. To learn how please visit https://odoo-community.org/page/Contribute.\n\n\n",
"bugtrack_url": null,
"license": "AGPL-3",
"summary": "Manage Field Service Locations, Workers and Orders",
"version": "14.0.1.30.1",
"project_urls": {
"Homepage": "https://github.com/OCA/field-service"
},
"split_keywords": [],
"urls": [
{
"comment_text": "",
"digests": {
"blake2b_256": "0579cc4e7281c4779616f05a0201dfac3c9d8ccb9cfa2465e5f180330b6e16dc",
"md5": "7952b0645187756ee319ff547fb2ae32",
"sha256": "0b28ee2b2cfa7757ab43d2392df6ae6aa36e5cd8b934fb640b647c062c76f900"
},
"downloads": -1,
"filename": "odoo14_addon_fieldservice-14.0.1.30.1-py3-none-any.whl",
"has_sig": false,
"md5_digest": "7952b0645187756ee319ff547fb2ae32",
"packagetype": "bdist_wheel",
"python_version": "py3",
"requires_python": ">=3.6",
"size": 307600,
"upload_time": "2023-10-28T17:43:52",
"upload_time_iso_8601": "2023-10-28T17:43:52.635364Z",
"url": "https://files.pythonhosted.org/packages/05/79/cc4e7281c4779616f05a0201dfac3c9d8ccb9cfa2465e5f180330b6e16dc/odoo14_addon_fieldservice-14.0.1.30.1-py3-none-any.whl",
"yanked": false,
"yanked_reason": null
}
],
"upload_time": "2023-10-28 17:43:52",
"github": true,
"gitlab": false,
"bitbucket": false,
"codeberg": false,
"github_user": "OCA",
"github_project": "field-service",
"travis_ci": false,
"coveralls": false,
"github_actions": true,
"lcname": "odoo14-addon-fieldservice"
}