=============
Field Service
=============
..
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!! This file is generated by oca-gen-addon-readme !!
!! changes will be overwritten. !!
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!! source digest: sha256:6dab6445b1c6fcb5d5db979501fefb12597c270a914d89918eb91f895168776c
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
.. |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/17.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-17-0/field-service-17-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=17.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.
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.
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 Settings > Users & Companies > 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, country whichs defines the boundary used
6. 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.
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 <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:%2017.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>
- Freni Patel <fpatel@opensourceintegrators.com>
- `Tecnativa <https://www.tecnativa.com>`__:
- Víctor Martínez
- Nils Coenen <nils.coenen@nico-solutions.de>
- 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-max3903| image:: https://github.com/max3903.png?size=40px
:target: https://github.com/max3903
:alt: max3903
.. |maintainer-brian10048| image:: https://github.com/brian10048.png?size=40px
:target: https://github.com/brian10048
:alt: brian10048
Current `maintainers <https://odoo-community.org/page/maintainer-role>`__:
|maintainer-max3903| |maintainer-brian10048|
This module is part of the `OCA/field-service <https://github.com/OCA/field-service/tree/17.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": "odoo-addon-fieldservice",
"maintainer": null,
"docs_url": null,
"requires_python": ">=3.10",
"maintainer_email": null,
"keywords": null,
"author": "Open Source Integrators, Odoo Community Association (OCA)",
"author_email": "support@odoo-community.org",
"download_url": null,
"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:6dab6445b1c6fcb5d5db979501fefb12597c270a914d89918eb91f895168776c\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/17.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-17-0/field-service-17-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=17.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\nconfiguration. It also allows for many advanced features, which require\na more in-depth configuration.\n\nOrder Stages\n------------\n\nThe stage of an order is used to monitor its progress. Stages can be\nconfigured based on your company's specific business needs. A basic set\nof order stages comes pre-configured for use.\n\n1. Go to *Field Service > Configuration > Stages*\n2. Create or edit a stage\n3. Set the name for the stage.\n4. Set the sequence order for the stage.\n5. Select *Order* type to apply this stage to your orders.\n6. 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\nworkers, salesmen, and other resources. For example, salesmen may serve\na particular Territory. There may be multiple Territories served by a\nsingle Branch office location. Multiple Branches are managed within a\nDistrict and these Districts are managed under an encompassing Region.\n\nSetup a Territory\n~~~~~~~~~~~~~~~~~\n\n1. Go to Settings > Users & Companies > Territories\\*\n2. Create or select a territory\n3. Set the territory Name and description\n4. Select or create a branch which this territory serves\n5. Choose a type of zip, country whichs defines the boundary used\n6. 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\nin the General Settings panel for Field Service.\n\n1. Go to *Field Service > Configuration > Settings*\n2. Enable additional options\n3. Configure new options\n\nManage Teams\n~~~~~~~~~~~~\n\nTeams can be used to organize the processing of field service orders\ninto groups. Different teams may have different workflows that a field\nservice order needs to follow.\n\n1. Go to *Field Service > Configuration > Workers > Teams*\n2. Create or select a team\n3. Set the team name, description, and sequence\n\nYou can now define custom stages for each team processing orders.\n\n1. Go to *Field Service > Configuration > Stages*\n2. Create or edit a stage\n3. 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\ndo.\n\n1. Go to *Field Service > Configuration > Workers > Categories*\n2. Create or select a category\n3. Set the name and description of category\n4. 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\n1. Go to *Field Service > Configuration > Orders > Tags*\n2. Create or select a tag\n3. Set the tag name\n4. 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\n1. Go to *Field Service > Master Data > Templates*\n2. Create or select a template\n3. Set the name\n4. 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\nperformed.\n\n1. Go to *Field Service > Master Data > Locations*\n2. 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\n1. Go to *Field Service > Master Data > Workers*\n2. Create a worker\n\nProcess Orders\n--------------\n\nOnce you have established your data, you can begin processing field\nservice orders.\n\n1. Go to *Field Service > Dashboard > Orders*\n2. Create or select an order\n3. Enter relevant details for the order\n4. Process order through each stage as defined by your business\n 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:%2017.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- Freni Patel <fpatel@opensourceintegrators.com>\n- `Tecnativa <https://www.tecnativa.com>`__:\n\n - V\u00edctor Mart\u00ednez\n\n- Nils Coenen <nils.coenen@nico-solutions.de>\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-max3903| image:: https://github.com/max3903.png?size=40px\n :target: https://github.com/max3903\n :alt: max3903\n.. |maintainer-brian10048| image:: https://github.com/brian10048.png?size=40px\n :target: https://github.com/brian10048\n :alt: brian10048\n\nCurrent `maintainers <https://odoo-community.org/page/maintainer-role>`__:\n\n|maintainer-max3903| |maintainer-brian10048| \n\nThis module is part of the `OCA/field-service <https://github.com/OCA/field-service/tree/17.0/fieldservice>`_ project on GitHub.\n\nYou are welcome to contribute. To learn how please visit https://odoo-community.org/page/Contribute.\n",
"bugtrack_url": null,
"license": "AGPL-3",
"summary": "Manage Field Service Locations, Workers and Orders",
"version": "17.0.1.2.0.2",
"project_urls": {
"Homepage": "https://github.com/OCA/field-service"
},
"split_keywords": [],
"urls": [
{
"comment_text": "",
"digests": {
"blake2b_256": "0412a634d972bd2e72415ae3fabb12d30b7fa50c731d3d3a71da39ab82ca0ee1",
"md5": "c35d8bf26d5ac4027b77abf940d3145e",
"sha256": "21faa466a6ecf6af220ec66c2fbbb968afd8f0656cef07f6f4a942f499231583"
},
"downloads": -1,
"filename": "odoo_addon_fieldservice-17.0.1.2.0.2-py3-none-any.whl",
"has_sig": false,
"md5_digest": "c35d8bf26d5ac4027b77abf940d3145e",
"packagetype": "bdist_wheel",
"python_version": "py3",
"requires_python": ">=3.10",
"size": 318007,
"upload_time": "2024-04-30T03:55:06",
"upload_time_iso_8601": "2024-04-30T03:55:06.847413Z",
"url": "https://files.pythonhosted.org/packages/04/12/a634d972bd2e72415ae3fabb12d30b7fa50c731d3d3a71da39ab82ca0ee1/odoo_addon_fieldservice-17.0.1.2.0.2-py3-none-any.whl",
"yanked": false,
"yanked_reason": null
}
],
"upload_time": "2024-04-30 03:55:06",
"github": true,
"gitlab": false,
"bitbucket": false,
"codeberg": false,
"github_user": "OCA",
"github_project": "field-service",
"travis_ci": false,
"coveralls": false,
"github_actions": true,
"lcname": "odoo-addon-fieldservice"
}
JSON
