Skip to content

Commit 0857eb3

Browse files
guillaume gallant (guga)auva-odoo
authored andcommitted
[REF] Planning: create new field service page in planning
task-6009439
1 parent e81cb46 commit 0857eb3

12 files changed

Lines changed: 300 additions & 275 deletions

File tree

content/applications/inventory_and_mrp/manufacturing/workflows/continuous_improvement.rst

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -140,15 +140,15 @@ Product |BoMs| can continue to be updated, as needed. The :doc:`version control
140140
<../../plm/manage_changes/version_control>` features of the |PLM| app allow for easy management of
141141
all versions of a given |BoM|.
142142

143-
Field Service
143+
Field service
144144
-------------
145145

146146
The |PLM| app is a great way to make changes to product |BoMs|. However, these changes only affect
147147
products produced using the new |BoM|. If a defective product has already been sold to a customer,
148148
it may be necessary to repair (or update) that product.
149149

150-
In such a case, the *Field Service* app can be used to schedule :doc:`onsite interventions
151-
<../../../services/field_service/creating_tasks>`. These interventions allow service
150+
In such a case, the Planning app can be used to schedule :doc:`onsite interventions
151+
</applications/services/planning/field_service>`. These interventions allow service
152152
technicians (or other employees) to be sent to a customer's location to address an issue with a
153153
product.
154154

content/applications/services.rst

Lines changed: 0 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -10,5 +10,4 @@ Services
1010
services/project
1111
services/timesheets
1212
services/planning
13-
services/field_service
1413
services/helpdesk

content/applications/services/field_service.rst

Lines changed: 0 additions & 19 deletions
This file was deleted.

content/applications/services/field_service/creating_tasks.rst

Lines changed: 0 additions & 30 deletions
This file was deleted.

content/applications/services/field_service/planning_itinerary.rst

Lines changed: 0 additions & 36 deletions
This file was deleted.

content/applications/services/field_service/product_management.rst

Lines changed: 0 additions & 89 deletions
This file was deleted.
Binary file not shown.

content/applications/services/field_service/worksheets.rst

Lines changed: 0 additions & 66 deletions
This file was deleted.
Binary file not shown.

content/applications/services/planning.rst

Lines changed: 43 additions & 31 deletions
Original file line numberDiff line numberDiff line change
@@ -211,54 +211,61 @@ Create a shift
211211
To create a shift, go to any schedule, then click :guilabel:`New`. In the pop-up window that opens,
212212
fill in the following details:
213213

214-
- **Templates**: If there is one or more templates existing in your database, they are
214+
- **Templates**: If there is one or more templates existing in the database, they are
215215
displayed in the upper section of the pop-up window. Once selected, a template prefills the
216216
shift form accordingly.
217-
- :guilabel:`Resource`: Resources can be both employees or materials. If this field is left empty,
217+
- :guilabel:`Resources`: Resources can be both employees or materials. If this field is left empty,
218218
the shift is considered an :ref:`open shift <planning/open-shifts>`.
219-
- :guilabel:`Role`: Select the role that the resource assigned will be performing. This field is
220-
used when :ref:`auto-planning <planning/open-shifts>` shifts. Once you select a role, the shift
221-
templates associated with it are displayed in the upper section of the pop-up window.
222-
- :guilabel:`Project`: If the Project app is installed in your database, this field allows you to
223-
link the project to the shift is available, allowing you to plan and track shifts dedicated to
224-
work on the selected project.
225-
- :guilabel:`Sales Order Item`: If the Sales app is installed in your database, this field allows
226-
you to link a sales order to the shift.
219+
- :guilabel:`Date`: Choose the date and time of the shift. This is the only mandatory field when
220+
creating a shift.
227221
- :guilabel:`Repeat`: Click the :icon:`fa-repeat` :guilabel:`(repeat)` button and configure the
228-
:guilabel:`Repeat every` fields according to your needs. The following rules apply to recurring
229-
shifts:
222+
:guilabel:`Repeat every` fields as needed. The following rules apply to recurring shifts:
230223

231224
- All fields (e.g., :guilabel:`Resource`, :guilabel:`Role`, :guilabel:`Project`) are copied from
232-
the original shift except for the date, which is adjusted according to the
233-
:guilabel:`Repeat Every` field.
225+
the original shift except for the date, which is adjusted according to the :guilabel:`Repeat
226+
Every` field.
234227
- Recurrences are planned but not published.
235228
- By default, planned shifts are created six months in advance, after which they are created
236-
gradually. To change the time frame, :ref:`activate the Developer mode <developer-mode>`, then
237-
go to :menuselection:`Planning --> Configuration --> Settings` and edit the
238-
:guilabel:`Recurring Shifts`.
229+
gradually. To change the time frame, :ref:`activate the developer mode <developer-mode>`, then
230+
go to :menuselection:`Planning --> Configuration --> Settings` and edit the :guilabel:`Recurring
231+
Shifts`.
239232

240-
- :guilabel:`Additional note sent to the employee`: Click on the field to add a note.
241-
- :guilabel:`Date`: Choose the date and time of your shift. This is the only mandatory field when
242-
creating a shift.
243-
- :guilabel:`Allocated time`: Is calculated based on the date and the employee’s :guilabel:`Working
244-
Schedule`. See more in :ref:`Shift Templates <planning/templates>`.
233+
- :guilabel:`Allocated time`: Is calculated based on the date and the employee's :guilabel:`Working
234+
Schedule`.
235+
- :guilabel:`Role`: Select the role that the resources assigned will be performing. This field is
236+
used when :ref:`auto-planning <planning/open-shifts>` shifts. Once you select a role, the shift
237+
templates associated with it are displayed in the upper section of the pop-up window.
245238

246-
Click :guilabel:`Publish & Save` to confirm the shift and send the assigned employee their schedule
247-
by email.
239+
Additionally, the following fields may also be available:
248240

249-
.. note::
250-
The draft is visible on the admin planning view and can be identified by diagonal lines. The
251-
employee is only notified of the shift once it's published.
241+
- :guilabel:`Project`: If the :guilabel:`Project planning` setting is enabled, select the relevant
242+
project to link to the shift. Shifts dedicated to the selected project are then planned and
243+
tracked accordingly.
244+
- :guilabel:`Task`: If a project is selected, optionally select a task within that project.
245+
- :guilabel:`Sales Order`: If the Sales app is installed, select the relevant sales order to link to
246+
the shift.
247+
- :guilabel:`Customer`: If the :doc:`Field Service <planning/field_service>` setting is enabled and
248+
the shift is an onsite intervention, select the relevant customer to link to the shift.
249+
- :guilabel:`Worksheet`: If :ref:`field service worksheets <planning/field-service/worksheets>` are
250+
configured, optionally select the relevant :ref:`worksheet template
251+
<planning/field-service/worksheet-templates>`.
252+
253+
Click :guilabel:`Save` to confirm the shift, or :guilabel:`Publish` to confirm it and notify the
254+
assigned employee by email.
252255

253-
Two kinds of notifications are sent to the employees depending on their account configuration:
256+
.. note::
257+
Unpublished shifts are only visible on schedules for users with :guilabel:`Administrator`
258+
Planning :doc:`access rights </applications/general/users/access_rights>` and are identified by
259+
diagonal lines. The employee is notified of the shift only once it is published:
254260

255261
- Employees without user accounts are redirected to a dedicated **Planning portal**.
256262
- Employees with a user account are redirected to the :guilabel:`My Planning` view in the
257-
backend view of Odoo.
263+
backend.
258264

259265
.. tip::
260-
The **split shifts** tool allows to easily split a long shift into segments. To do so, hover the
261-
mouse over the desired shift and click the :icon:`fa-scissors` (:guilabel:`scissors`) icon.
266+
The **Split shifts** tool allows a long shift to be split into segments. To do so, hover over
267+
the desired shift between two day columns and click the :icon:`fa-scissors`
268+
(:guilabel:`scissors`) icon.
262269

263270
.. image:: planning/split-shifts.png
264271
:alt: Split shifts tool.
@@ -336,3 +343,8 @@ shift reverts to an open shift.
336343

337344
- Only the shifts matching the employee's roles are displayed in their schedule.
338345
- Unassigning shifts is not available for shifts in the past.
346+
347+
.. toctree::
348+
:titlesonly:
349+
350+
planning/field_service

0 commit comments

Comments
 (0)