Skip to content

Commit a2d3ea4

Browse files
committed
[IMP] Lunch: Update main doc
1 parent e96f600 commit a2d3ea4

File tree

3 files changed

+34
-29
lines changed

3 files changed

+34
-29
lines changed

content/applications/hr/lunch.rst

Lines changed: 34 additions & 29 deletions
Original file line numberDiff line numberDiff line change
@@ -4,30 +4,35 @@
44
Lunch
55
=====
66

7-
The *Lunch* application in Odoo allows users a convenient way to order food and pay for their meal
7+
The **Lunch** application in Odoo allows users to conveniently order food and pay for their meal
88
directly from the database.
99

10-
Before employees can use the *Lunch* application, there are a number of configurations to consider:
11-
settings, vendors, locations, products, product categories, and alerts. Once these are created,
12-
employees can view offerings and order food.
10+
Before employees can use the **Lunch** application, there are a number of configurations that need
11+
to be made: :ref:`settings <lunch/settings>`, :doc:`vendors <lunch/vendors>`, :ref:`locations
12+
<lunch/locations>`, :doc:`products <lunch/products>`, and :ref:`product categories
13+
<lunch/product-categories>`. Once these are created and configured, employees can view offerings and
14+
order food.
15+
16+
.. _lunch/settings:
1317

1418
Settings
1519
========
1620

17-
Only two settings are needed to configure in the *Lunch* app: overdraft settings and notifications.
18-
To access the settings, navigate to :menuselection:`Lunch app --> Configuration: Settings`.
21+
In the :guilabel:`Settings` menu, only two items need to be configured: overdraft settings and
22+
notifications. To access the settings, navigate to :menuselection:`Lunch app --> Configuration -->
23+
Settings`.
1924

2025
Configure the following:
2126

22-
- :guilabel:`Lunch Overdraft`: enter the maximum overdraft amount for employees. The currency
23-
format is determined by the localization setting of the company.
24-
- :guilabel:`Reception notification`: set the message users receive via the *Discuss* app when their
25-
food has been delivered. The default message `Your lunch has been delivered. Enjoy your meal!`
26-
populates this field, but can be modified, if desired.
27+
- :guilabel:`Lunch Overdraft`: enter the maximum overdraft amount for employees. The currency format
28+
is determined by the localization setting of the company.
29+
- :guilabel:`Reception notification`: set the message users receive via the **Discuss** app when
30+
their food has been delivered. The default message `Your lunch has been delivered. Enjoy your
31+
meal!` populates this field, but can be modified, if desired.
2732

2833
.. tip::
29-
If in a database with multiple languages installed, many forms in the *Lunch* application have
30-
the option of entering translations for various fields.
34+
If a database has multiple languages installed, many forms in the **Lunch** application have the
35+
option of entering translations for various fields.
3136

3237
If translations are available to be configured, a language code appears next to a translatable
3338
field on a form. To add translations for that field, click the two letter language code (for
@@ -36,8 +41,8 @@ Configure the following:
3641
The following is an example for the :guilabel:`Reception notification` field in the settings
3742
menu:
3843

39-
Navigate to :menuselection:`Lunch app --> Configuration: Settings`. Click the :guilabel:`EN` In
40-
the top-right of the text box beneath the :guilabel:`Reception notification` section. A
44+
Navigate to :menuselection:`Lunch app --> Configuration --> Settings`. Click the :guilabel:`EN`
45+
In the top-right of the text box beneath the :guilabel:`Reception notification` section. A
4146
:guilabel:`Translate: company_lunch_notify_message` pop-up window loads with the option to enter
4247
a translation for the other languages used by the database.
4348

@@ -48,17 +53,18 @@ Configure the following:
4853
Enter the text that should appear for each language, then click :guilabel:`Save`.
4954

5055
.. image:: lunch/translation.png
51-
:align: center
5256
:alt: The translation text box, with the current language highlighted, and the Arabic
5357
translation field highlighted.
5458

59+
.. _lunch/locations:
60+
5561
Locations
5662
=========
5763

58-
By default, Odoo creates an `HQ Office` location when the *Lunch* application is installed. If a
64+
By default, Odoo creates an `HQ Office` location when the **Lunch** application is installed. If a
5965
company has more than one location, they must be configured.
6066

61-
To add a location, navigate to :menuselection:`Lunch app --> Configuration: Locations`. The
67+
To add a location, navigate to :menuselection:`Lunch app --> Configuration --> Locations`. The
6268
currently configured locations appear in a list view. Click the :guilabel:`New` button in the
6369
top-left corner and a blank line appears beneath the last location in the list.
6470

@@ -69,32 +75,32 @@ address field.
6975
Repeat this for all locations that need to be added.
7076

7177
.. image:: lunch/locations.png
72-
:align: center
7378
:alt: A list view of the locations with the new button highlighted.
7479

7580
Alerts
7681
======
7782

78-
It is possible to set up alerts that can either be displayed in the *Lunch* app, or be sent to
79-
specific employees via the *Discuss* app.
83+
It is possible to set up alerts that can either be displayed in the **Lunch** app, or be sent to
84+
specific employees via the **Discuss** app.
8085

81-
No alerts are pre-configured by default. To set up an alert, navigate to :menuselection:`Lunch app
82-
--> Configuration: Alerts`. Click the :guilabel:`New` button in the top-left corner and a blank
86+
No alerts are preconfigured by default. To set up an alert, navigate to :menuselection:`Lunch app
87+
--> Configuration --> Alerts`. Click the :guilabel:`New` button in the top-left corner and a blank
8388
lunch alert form loads. Enter the following information on the form:
8489

8590
- :guilabel:`Alert Name`: enter a name for the alert. This should be short and descriptive, such as
86-
`New Lunch Vendor` or `Order by 11`. This field is **required**.
87-
- :guilabel:`Display`: select whether the alert is visible in the *Lunch* app (:guilabel:`Alert in
88-
app)` or sent to employees via the *Discuss* app in a chat window (:guilabel:`Chat notification`).
91+
`New Lunch Vendor` or `Order by 11:00 AM`. This field is **required**.
92+
- :guilabel:`Display`: select whether the alert is visible in the **Lunch** app (:guilabel:`Alert in
93+
app)` or sent to employees via the **Discuss** app in a chat window (:guilabel:`Chat
94+
notification`).
8995

9096
- :guilabel:`Recipients`: this field only appears if :guilabel:`Chat notification` is selected for
9197
the :guilabel:`Display` option. Select who receives the chat alert. The options are:
9298
:guilabel:`Everyone`, :guilabel:`Employee who ordered last week`, :guilabel:`Employee who
9399
ordered last month`, or :guilabel:`Employee who ordered last year`.
94100

95101
- :guilabel:`Location`: select the locations the alert should appear for from the drop-down menu.
96-
Multiple locations can be selected. This field is **required**, therefore, if the alert applies
97-
to all locations, select all the locations from the drop-down menu.
102+
Multiple locations can be selected. This field is **required**, therefore, if the alert applies to
103+
all locations, select all the locations from the drop-down menu.
98104
- :guilabel:`Show Until`: if the alert should expire on a specific date, select the date from the
99105
calendar picker.
100106
- :guilabel:`Active`: this option is on (appears green) by default. To turn off the alert, click the
@@ -109,7 +115,6 @@ lunch alert form loads. Enter the following information on the form:
109115
the :guilabel:`Time` field.
110116

111117
.. image:: lunch/alert.png
112-
:align: center
113118
:alt: An alert form with all of the information filled out for a chat alert sent at 10:30 AM,
114119
asking employees to submit orders by 11:30 AM.
115120

-165 Bytes
Loading
-4.5 KB
Loading

0 commit comments

Comments
 (0)