Compare commits
1 Commits
master-16.
...
master-doc
| Author | SHA1 | Message | Date | |
|---|---|---|---|---|
|
|
f0548c755b |
[IMP] documentation: update many2many_binary widget
The widget now also display an image preview for the files of MIME type "image". A new option 'reverse_order' has been added to visually reverse the files order. |
|
|
@@ -61,8 +61,8 @@ To resolve the issue:
|
|||
your **network and firewall settings** allow the Odoo server to open outgoing connections
|
||||
towards:
|
||||
|
||||
- Odoo 18.0 and above: `services.odoo.com` on port `80`
|
||||
- Odoo 17.0 and below: `services.openerp.com` on port `80`
|
||||
- Odoo 18.0 and above: `services.odoo.com` on port `443` (or `80`)
|
||||
- Odoo 17.0 and below: `services.openerp.com` on port `443` (or `80`)
|
||||
|
||||
These ports must be kept open even after registering a database, as the update notification runs
|
||||
once a week.
|
||||
|
|
@@ -85,6 +85,12 @@ To resolve the issue, either:
|
|||
displayed in the message to validate the upsell quotation and pay for the extra users.
|
||||
- :ref:`Deactivate users <users/deactivate>` and **reject** the upsell quotation.
|
||||
|
||||
.. important::
|
||||
If you are on a monthly subscription plan, the database will automatically update to reflect the
|
||||
added user(s). If you are on a yearly or multi-year plan, an expiration banner will appear in the
|
||||
database. You can create the upsell quotation by clicking the banner to update the subscription
|
||||
or `send a support ticket <https://www.odoo.com/help>`_ to resolve the issue.
|
||||
|
||||
Once your database has the correct number of users, the expiration message disappears automatically
|
||||
after a few days, when the next verification occurs.
|
||||
|
||||
|
|
|
|||
|
|
@@ -4,163 +4,128 @@
|
|||
Fiscal localizations
|
||||
====================
|
||||
|
||||
Fiscal localizations are country-specific modules that allow you to be compliant with a country's
|
||||
fiscal requirements. Most of these modules are related to the :ref:`Accounting
|
||||
<fiscal_localizations/accounting>` or :ref:`Payroll <fiscal_localizations/payroll>` app, but they
|
||||
can also be necessary for other apps such as Point of Sale, eCommerce, etc., depending on a
|
||||
country's fiscal requirements.
|
||||
|
||||
.. _fiscal_localizations/packages:
|
||||
|
||||
Configuration
|
||||
=============
|
||||
Fiscal localization packages
|
||||
============================
|
||||
|
||||
Odoo should automatically install the required fiscal localization modules based on the company's
|
||||
country when the related app is installed. Refer to the :ref:`list of countries
|
||||
<fiscal_localizations/countries-list>` to view the currently supported countries and access their
|
||||
specific documentation.
|
||||
**Fiscal Localization Packages** are country-specific modules that install pre-configured taxes,
|
||||
fiscal positions, chart of accounts, and legal statements on your database. Some additional
|
||||
features, such as the configuration of specific certificates, are also added to your Accounting app,
|
||||
following your fiscal administration requirements.
|
||||
|
||||
.. note::
|
||||
Each company in a multi-company environment can use different fiscal localization modules.
|
||||
Odoo continuously adds new localizations and improves the existing packages.
|
||||
|
||||
.. _fiscal_localizations/accounting:
|
||||
Configuration
|
||||
-------------
|
||||
|
||||
Accounting
|
||||
----------
|
||||
Odoo automatically installs the appropriate package for your company, according to the country
|
||||
selected at the creation of the database.
|
||||
|
||||
Verify the right package of modules is installed by going to :menuselection:`Accounting -->
|
||||
Configuration --> Settings` and checking the :guilabel:`Package` field under the :guilabel:`Fiscal
|
||||
Localization` section. Select another one if necessary.
|
||||
.. important::
|
||||
As long as you haven't posted any entry, you can still select another package.
|
||||
|
||||
.. warning::
|
||||
Selecting another package is only possible if no entry has been posted.
|
||||
To select a fiscal localization package for your company, go to :menuselection:`Accounting -->
|
||||
Configuration --> Settings --> Fiscal Localization`, select the appropriate package from the list
|
||||
and save.
|
||||
|
||||
These packages require fine-tuning the chart of accounts, activating the taxes to be used,
|
||||
configuring the country-specific statements and certifications, and sometimes more.
|
||||
.. image:: fiscal_localizations/package-selection.png
|
||||
:alt: Select your country's fiscal localization package in Odoo Accounting.
|
||||
|
||||
.. _fiscal_localizations/payroll:
|
||||
Use
|
||||
---
|
||||
|
||||
Payroll
|
||||
-------
|
||||
These packages require you to fine-tune your chart of accounts according to your needs, activate the
|
||||
taxes you use, and configure your country-specific statements and certifications.
|
||||
|
||||
Localization settings can be accessed by going to :menuselection:`Payroll --> Configuration -->
|
||||
Settings` and searching for the country's **Localization** section.
|
||||
.. seealso::
|
||||
- :doc:`accounting/get_started/chart_of_accounts`
|
||||
- :doc:`accounting/taxes`
|
||||
|
||||
.. _fiscal_localizations/countries-list:
|
||||
|
||||
List of countries
|
||||
=================
|
||||
List of supported countries
|
||||
===========================
|
||||
|
||||
Fiscal localization modules are available for the countries listed below.
|
||||
Odoo Accounting can be used in many countries out of the box by installing the appropriate module.
|
||||
Here is a list of all :ref:`fiscal localization package <fiscal_localizations/packages>` that are
|
||||
available on Odoo.
|
||||
|
||||
.. note::
|
||||
New countries are frequently added to this list and Odoo keeps expanding and improving existing
|
||||
localizations and the related documentation.
|
||||
|
||||
- Algeria
|
||||
- :doc:`Argentina <fiscal_localizations/argentina>`
|
||||
- :doc:`Australia <fiscal_localizations/australia>`
|
||||
- :doc:`Austria <fiscal_localizations/austria>`
|
||||
- Bangladesh
|
||||
- :doc:`Belgium <fiscal_localizations/belgium>`
|
||||
- Benin
|
||||
- Bolivia
|
||||
- :doc:`Brazil <fiscal_localizations/brazil>`
|
||||
- Burkina Faso
|
||||
- Bulgaria
|
||||
- Cameroon
|
||||
- :doc:`Canada <fiscal_localizations/canada>`
|
||||
- Central African Republic
|
||||
- Chad
|
||||
- :doc:`Chile <fiscal_localizations/chile>`
|
||||
- China
|
||||
- :doc:`Colombia <fiscal_localizations/colombia>`
|
||||
- Comoros
|
||||
- Congo
|
||||
- Costa Rica
|
||||
- Croatia
|
||||
- Cyprus
|
||||
- Czech Republic
|
||||
- Democratic Republic of the Congo
|
||||
- Denmark
|
||||
- Dominican Republic
|
||||
- :doc:`Ecuador <fiscal_localizations/ecuador>`
|
||||
- :doc:`Egypt <fiscal_localizations/egypt>`
|
||||
- Equatorial Guinea
|
||||
- Estonia
|
||||
- Ethiopia
|
||||
- Finland
|
||||
- :doc:`France <fiscal_localizations/france>`
|
||||
- Gabon
|
||||
- Algeria - Accounting
|
||||
- :doc:`Argentina - Accounting <fiscal_localizations/argentina>`
|
||||
- :doc:`Australian - Accounting <fiscal_localizations/australia>`
|
||||
- :doc:`Austria - Accounting <fiscal_localizations/austria>`
|
||||
- :doc:`Belgium - Accounting <fiscal_localizations/belgium>`
|
||||
- Bolivia - Accounting
|
||||
- :doc:`Brazilian - Accounting <fiscal_localizations/brazil>`
|
||||
- :doc:`Canada - Accounting <fiscal_localizations/canada>`
|
||||
- :doc:`Chile - Accounting <fiscal_localizations/chile>`
|
||||
- China - Accounting
|
||||
- :doc:`Colombia - Accounting <fiscal_localizations/colombia>`
|
||||
- Costa Rica - Accounting
|
||||
- Croatia - Accounting (RRIF 2012)
|
||||
- Czech - Accounting
|
||||
- Denmark - Accounting
|
||||
- Dominican Republic - Accounting
|
||||
- :doc:`Ecuadorian - Accounting <fiscal_localizations/ecuador>`
|
||||
- :doc:`Egypt - Accounting <fiscal_localizations/egypt>`
|
||||
- Ethiopia - Accounting
|
||||
- Finnish Localization
|
||||
- :doc:`France - Accounting <fiscal_localizations/france>`
|
||||
- Generic - Accounting
|
||||
- :doc:`Germany <fiscal_localizations/germany>`
|
||||
- Guinea
|
||||
- Greece
|
||||
- Guatemala
|
||||
- Guinea-Bissau
|
||||
- Honduras
|
||||
- :doc:`Hong Kong <fiscal_localizations/hong_kong>`
|
||||
- Hungary
|
||||
- :doc:`India <fiscal_localizations/india>`
|
||||
- :doc:`Indonesia <fiscal_localizations/indonesia>`
|
||||
- :doc:`Italy <fiscal_localizations/italy>`
|
||||
- Ivory Coast
|
||||
- Japan
|
||||
- Jordan
|
||||
- Kazakhstan
|
||||
- :doc:`Kenya <fiscal_localizations/kenya>`
|
||||
- Kuwait
|
||||
- Latvia
|
||||
- Lithuania
|
||||
- :doc:`Luxembourg <fiscal_localizations/luxembourg>`
|
||||
- Mali
|
||||
- Malta
|
||||
- Mauritius
|
||||
- :doc:`Malaysia <fiscal_localizations/malaysia>`
|
||||
- :doc:`Mexico <fiscal_localizations/mexico>`
|
||||
- Mongolia
|
||||
- Morocco
|
||||
- Mozambique
|
||||
- :doc:`Netherlands <fiscal_localizations/netherlands>`
|
||||
- :doc:`New Zealand <fiscal_localizations/new_zealand>`
|
||||
- Niger
|
||||
- Nigeria
|
||||
- Norway
|
||||
- Pakistan
|
||||
- Panama
|
||||
- :doc:`Peru <fiscal_localizations/peru>`
|
||||
- :doc:`Philippines <fiscal_localizations/philippines>`
|
||||
- Poland
|
||||
- Portugal
|
||||
- Qatar
|
||||
- :doc:`Romania <fiscal_localizations/romania>`
|
||||
- Rwanda
|
||||
- :doc:`Saudi Arabia <fiscal_localizations/saudi_arabia>`
|
||||
- Senegal
|
||||
- Serbia
|
||||
- :doc:`Singapore <fiscal_localizations/singapore>`
|
||||
- Slovakia
|
||||
- Slovenia
|
||||
- South Africa
|
||||
- :doc:`Spain <fiscal_localizations/spain>`
|
||||
- Sweden
|
||||
- :doc:`Switzerland <fiscal_localizations/switzerland>`
|
||||
- Taiwan
|
||||
- Tanzania
|
||||
- :doc:`Thailand <fiscal_localizations/thailand>`
|
||||
- Tunisia
|
||||
- Türkiye
|
||||
- Uganda
|
||||
- Ukraine
|
||||
- :doc:`United Arab Emirates <fiscal_localizations/united_arab_emirates>`
|
||||
- :doc:`United Kingdom <fiscal_localizations/united_kingdom>`
|
||||
- :doc:`United States of America <fiscal_localizations/united_states>`
|
||||
- :doc:`Uruguay <fiscal_localizations/uruguay>`
|
||||
- Venezuela
|
||||
- :doc:`Vietnam <fiscal_localizations/vietnam>`
|
||||
- Zambia
|
||||
|
||||
.. seealso::
|
||||
:doc:`Employment Hero Payroll documentation <fiscal_localizations/employment_hero>`
|
||||
- Germany SKR03 - Accounting
|
||||
- Germany SKR04 - Accounting
|
||||
|
||||
- Greece - Accounting
|
||||
- Guatemala - Accounting
|
||||
- Honduras - Accounting
|
||||
- :doc:`Hong Kong - Accounting <fiscal_localizations/hong_kong>`
|
||||
- Hungarian - Accounting
|
||||
- :doc:`Indian - Accounting <fiscal_localizations/india>`
|
||||
- :doc:`Indonesian - Accounting <fiscal_localizations/indonesia>`
|
||||
- Ireland - Accounting
|
||||
- Israel - Accounting
|
||||
- :doc:`Italy - Accounting <fiscal_localizations/italy>`
|
||||
- Japan - Accounting
|
||||
- :doc:`Kenya - Accounting <fiscal_localizations/kenya>`
|
||||
- Lithuania - Accounting
|
||||
- :doc:`Luxembourg - Accounting <fiscal_localizations/luxembourg>`
|
||||
- :doc:`Malaysia - Accounting <fiscal_localizations/malaysia>`
|
||||
- Maroc - Accounting
|
||||
- :doc:`Mexico - Accounting <fiscal_localizations/mexico>`
|
||||
- Mongolia - Accounting
|
||||
- :doc:`Netherlands - Accounting <fiscal_localizations/netherlands>`
|
||||
- :doc:`New Zealand - Accounting <fiscal_localizations/new_zealand>`
|
||||
- Norway - Accounting
|
||||
- OHADA - Accounting
|
||||
- Pakistan - Accounting
|
||||
- Panama - Accounting
|
||||
- :doc:`Peru - Accounting <fiscal_localizations/peru>`
|
||||
- :doc:`Philippines - Accounting <fiscal_localizations/philippines>`
|
||||
- Poland - Accounting
|
||||
- Portugal - Accounting
|
||||
- :doc:`Romania - Accounting <fiscal_localizations/romania>`
|
||||
- :doc:`Saudi Arabia - Accounting <fiscal_localizations/saudi_arabia>`
|
||||
- :doc:`Singapore - Accounting <fiscal_localizations/singapore>`
|
||||
- Slovak - Accounting
|
||||
- Slovenian - Accounting
|
||||
- South Africa - Accounting
|
||||
- :doc:`Spain - Accounting (PGCE 2008) <fiscal_localizations/spain>`
|
||||
- Sweden - Accounting
|
||||
- :doc:`Switzerland - Accounting <fiscal_localizations/switzerland>`
|
||||
- Taiwan - Accounting
|
||||
- :doc:`Thailand - Accounting <fiscal_localizations/thailand>`
|
||||
- Turkey - Accounting
|
||||
- :doc:`United Arab Emirates - Accounting <fiscal_localizations/united_arab_emirates>`
|
||||
- :doc:`UK - Accounting <fiscal_localizations/united_kingdom>`
|
||||
- Ukraine - Accounting
|
||||
- :doc:`United States - Accounting <fiscal_localizations/united_states>`
|
||||
- :doc:`Uruguay - Accounting <fiscal_localizations/uruguay>`
|
||||
- Venezuela - Accounting
|
||||
- :doc:`Vietnam - Accounting <fiscal_localizations/vietnam>`
|
||||
|
||||
.. toctree::
|
||||
:titlesonly:
|
||||
|
|
|
|||
|
|
@@ -24,17 +24,6 @@ with AvaTax.
|
|||
The localization also includes taxes and a chart of accounts template that can be modified if
|
||||
needed.
|
||||
|
||||
.. seealso::
|
||||
Links to helpful resources for the Brazilian localization, including onboarding materials and
|
||||
videos:
|
||||
|
||||
- `Onboarding checklist for new users
|
||||
<https://docs.google.com/document/d/e/2PACX-1vSNYTYVnR_BzvQKL3kn5YdVzPjjHc-WHw_U3udk5tz_dJXo69woj9QrTMinH_siyOX2rLGjvspvc8AF/pub>`_.
|
||||
- `YouTube playlist - Brazil (Localization)
|
||||
<https://youtube.com/playlist?list=PL1-aSABtP6ADqexw4YNCbKPmpFggajxlX&si=RgmZR3Jco3223Np4>`_.
|
||||
- `YouTube playlist - Tutoriais Odoo em Português
|
||||
<https://youtube.com/playlist?list=PL1-aSABtP6ACGOW2UREePGjHQ2Bgdy-UZ&si=j6tiI36eB7BoKVQB>`_.
|
||||
|
||||
Configuration
|
||||
=============
|
||||
|
||||
|
|
|
|||
|
|
@@ -25,9 +25,6 @@ localization:
|
|||
* - :guilabel:`Indian E-waybill`
|
||||
- `l10n_in_edi_ewaybill`
|
||||
- :ref:`Indian E-way bill integration <india/e-waybill>`
|
||||
* - :guilabel:`Indian - Check GST Number Status`
|
||||
- `l10n_in_gstin_status`
|
||||
- :ref:`Indian Check GST Number Status <india/gstin_status>`
|
||||
* - :guilabel:`Indian - GSTR India eFiling`
|
||||
- `l10n_in_reports_gstr`
|
||||
- :ref:`Indian GST Return filing <india/gstr>`
|
||||
|
|
@@ -351,26 +348,6 @@ fill out the :guilabel:`Cancel reason` and :guilabel:`Cancel remarks` fields. Th
|
|||
the government portal. You can click :guilabel:`Process Now` if you want to process the invoice
|
||||
immediately.
|
||||
|
||||
.. _india/gstin_status:
|
||||
|
||||
Indian Check GSTIN Status
|
||||
=========================
|
||||
|
||||
The :guilabel:`Indian - Check GST Number Status` module allows you to verify the status of a
|
||||
:abbr:`GSTIN (Goods and Services Tax Identification Number)` directly from Odoo.
|
||||
|
||||
To verify the status of a contact's GST number, access the customer's/vendor's form and click
|
||||
:guilabel:`Check GSTIN Status` next to the :guilabel:`GSTIN` field.
|
||||
|
||||
To verify the status of a GST number entered on an invoice/bill, access the invoice/bill and click
|
||||
the :icon:`fa-refresh` (:guilabel:`refresh`) button next to the :guilabel:`GST Status` field.
|
||||
|
||||
.. image:: india/gstin-status-invoice.png
|
||||
:alt: Check GSTIN status of an invoice
|
||||
|
||||
A notification is displayed to confirm the status update and the GSTIN status and verification date
|
||||
are logged in the contact's chatter.
|
||||
|
||||
.. _india/gstr:
|
||||
|
||||
Indian GST Return filing
|
||||
|
|
|
|||
|
Before Width: | Height: | Size: 5.7 KiB |
|
After Width: | Height: | Size: 4.2 KiB |
|
|
@@ -29,8 +29,6 @@ The accounting section of the configuration menu relates to three options:
|
|||
created from all the accounting entries from the same period. This disables the generation of
|
||||
single payments.
|
||||
|
||||
.. _payroll-localizations:
|
||||
|
||||
Localizations
|
||||
-------------
|
||||
|
||||
|
|
|
|||
|
|
@@ -1,169 +1,105 @@
|
|||
:show-content:
|
||||
:hide-page-toc:
|
||||
:show-toc:
|
||||
|
||||
=======
|
||||
Discuss
|
||||
=======
|
||||
|
||||
Odoo **Discuss** is an internal communication app that allows users to connect through messages,
|
||||
notes, file sharing, and video calls. **Discuss** enables communication through a persistent chat
|
||||
window that works across applications, or through the dedicated *Discuss* dashboard.
|
||||
Odoo *Discuss* is an internal communication app that allows users to connect through messages,
|
||||
notes, and file sharing, either through a persistent chat window that works across applications, or
|
||||
through the dedicated *Discuss* dashboard.
|
||||
|
||||
Upon opening the :menuselection:`Discuss app`, the :guilabel:`Discuss` dashboard appears.
|
||||
.. _discuss_app/notification_preferences:
|
||||
|
||||
Inbox, starred, and history
|
||||
===========================
|
||||
Choose notifications preference
|
||||
===============================
|
||||
|
||||
Upon opening the :menuselection:`Discuss app`, the *Discuss* dashboard appears.
|
||||
Access user-specific preferences for the *Discuss* app by navigating to :menuselection:`Settings app
|
||||
--> Users --> User --> Preferences tab`.
|
||||
|
||||
On the :guilabel:`Discuss` dashboard, unread messages are visible in the :icon:`fa-inbox`
|
||||
:guilabel:`Inbox`. :icon:`fa-star-o` :guilabel:`Starred` is where starred messages are stored.
|
||||
:icon:`fa-history` :guilabel:`History` shows chatter updates for records in the Odoo database the
|
||||
user has been assigned to, or tagged on.
|
||||
.. image:: discuss/preferences-user.png
|
||||
:alt: View of the Preferences tab for Odoo Discuss.
|
||||
|
||||
Direct messages
|
||||
===============
|
||||
By default, the :guilabel:`Notification` field is set as :guilabel:`Handle by Emails`. With this
|
||||
setting enabled, a notification email will be sent by Odoo every time a message is sent from the
|
||||
chatter, a note is sent with an `@` mention (from chatter), or a notification is sent for a record
|
||||
that the user follows. Something that triggers a notification is changing of the stage (if an email\
|
||||
is configured to be sent, for example if the task is set to :guilabel:`Done`).
|
||||
|
||||
*Direct messages* allow the user to communicate privately with one or multiple team members. To
|
||||
start a new direct message, click the :icon:`fa-plus` icon, next to :guilabel:`Direct Messages` on
|
||||
the :guilabel:`Discuss` dashboard, and enter the name of the desired person in the :guilabel:`Start
|
||||
a conversation` search bar that appears.
|
||||
By choosing :guilabel:`Handle in Odoo`, the above notifications are shown in the *Discuss* app's
|
||||
*inbox*. Messages can have the following actions taken on them: respond with an emoji by clicking
|
||||
:guilabel:`Add a Reaction`, or reply to the message by clicking on :guilabel:`Reply`. Additional
|
||||
actions may include starring the message by clicking :guilabel:`Marked as Todo`, or pinning the
|
||||
message by selecting :guilabel:`Pin` or even mark the message as unread by selecting
|
||||
:guilabel:`Marked as unread`.
|
||||
|
||||
.. image:: discuss/reactions-discuss.png
|
||||
:alt: View of an inbox message and its action options in Odoo Discuss.
|
||||
|
||||
Clicking :guilabel:`Mark as Todo` on a message causes it to appear on the :guilabel:`Starred` page,
|
||||
while clicking :guilabel:`Mark as Read` moves the message to :guilabel:`History`.
|
||||
|
||||
.. image:: discuss/starred-messages.png
|
||||
:alt: View of messages marked as todo in Odoo Discuss.
|
||||
|
||||
Start chatting
|
||||
==============
|
||||
|
||||
The first time a user logs in to their account, OdooBot sends a message asking for permission to
|
||||
send desktop notifications for chats. If accepted, the user will receive push notifications on their
|
||||
desktop for the messages they receive, regardless of where the user is in Odoo.
|
||||
|
||||
.. image:: discuss/odoobot-push.png
|
||||
:alt: View of the messages under the messaging menu emphasizing the request for push
|
||||
notifications for Odoo Discuss.
|
||||
|
||||
.. tip::
|
||||
Multiple names can be selected in the :guilabel:`Start a conversation` search bar. Once all of
|
||||
the names have been entered, press :kbd:`Enter`.
|
||||
To stop receiving desktop notifications, reset the notifications settings of the browser.
|
||||
|
||||
Direct message actions
|
||||
----------------------
|
||||
To start a chat, go to the :menuselection:`Discuss` app and click on the :guilabel:`+ (plus)` icon
|
||||
next to :guilabel:`Direct Messages` or :guilabel:`Channels` in the left menu of the dashboard.
|
||||
|
||||
Hover over a direct message in the chat window to see a menu of actions to take on the message.
|
||||
.. image:: discuss/channels-direct-messages.png
|
||||
:height: 400
|
||||
:alt: View of Discuss's panel emphasizing the titles channels and direct messages in Odoo
|
||||
Discuss.
|
||||
|
||||
- :icon:`oi-smile-add` :guilabel:`(Add a Reaction)`: open a drop-down menu of emojis that can be
|
||||
used to react to the direct message.
|
||||
- :icon:`fa-reply` :guilabel:`(Reply)`: reply to the direct message in a thread.
|
||||
- :icon:`fa-star-o` :guilabel:`(Mark as Todo)`: add the message to the :guilabel:`Starred` tab.
|
||||
- :icon:`fa-ellipsis-h` :guilabel:`(Expand)`: reveals more message actions, including:
|
||||
A company can also easily create :doc:`public and private channels <discuss/team_communication>`.
|
||||
|
||||
- :icon:`fa-thumb-tack` :guilabel:`Pin`
|
||||
- :icon:`fa-eye-slash` :guilabel:`Mark as Unread`
|
||||
- :icon:`fa-pencil` :guilabel:`Edit`
|
||||
- :icon:`fa-trash` :guilabel:`Delete`
|
||||
Mentions in the chat and on the chatter
|
||||
---------------------------------------
|
||||
|
||||
Conversation actions
|
||||
--------------------
|
||||
To mention a user within a chat or the chatter, type `@user-name`; to refer to a channel, type
|
||||
`#channel-name`. The user mentioned will be notified in their *inbox* or through an email, depending
|
||||
on their communication settings.
|
||||
|
||||
The icons in the top-right corner of a direct message conversation represent different actions the
|
||||
user can take on that conversation.
|
||||
.. image:: discuss/chat-windows.png
|
||||
:alt: View of a couple of chat window messages for Odoo Discuss.
|
||||
|
||||
Click :icon:`fa-bell` :guilabel:`Notification Settings` to set up notification preferences for the
|
||||
conversation, or click :icon:`fa-phone` :guilabel:`Start a Call` to begin a meeting. See the
|
||||
:ref:`Meetings <discuss/meetings>` section for more information about meetings.
|
||||
|
||||
At the top of the direct message window, click the name of the direct message to change the group
|
||||
name, and choose to add a description in the adjacent :guilabel:`Add a description` field.
|
||||
|
||||
.. image:: discuss/conversation-actions.png
|
||||
:alt: View of the conversation actions.
|
||||
|
||||
|
||||
.. note::
|
||||
The :guilabel:`Add a description` field is **only** available for group messages with more than
|
||||
two participants.
|
||||
.. tip::
|
||||
When a user is mentioned, the search list (list of names) suggests values first based on the
|
||||
task's followers, and secondly on employees. If the record being searched does not match with
|
||||
either a follower or employee, the scope of the search becomes all partners.
|
||||
|
||||
User status
|
||||
-----------
|
||||
|
||||
It is helpful to see what colleagues are up to, and how quickly they can respond to messages, by
|
||||
checking their status. The status is displayed as a circle in the bottom-right corner of a contact's
|
||||
photo in the :icon:`fa-users` :guilabel:`(Members List)`.
|
||||
|
||||
The color of the circle represents the user's status:
|
||||
It is helpful to see what colleagues are up to and how quickly they can respond to messages by
|
||||
checking their *status*. The status is shown on the left side of a contact's name on the
|
||||
:guilabel:`Discuss` sidebar, on the *messaging menu* and when listed in the *chatter*.
|
||||
|
||||
- Green = online
|
||||
- Orange = away
|
||||
- White = offline
|
||||
- Airplane = out of the office
|
||||
|
||||
Leave a direct message conversation
|
||||
-----------------------------------
|
||||
|
||||
To leave a direct message conversations, click the :icon:`fa-times` :guilabel:`(Leave this channel)`
|
||||
icon next to the conversation name in the :guilabel:`Direct Messages` section of the sidebar.
|
||||
|
||||
.. note::
|
||||
Leaving a conversation does **not** delete the direct messages in the conversation. The direct
|
||||
message conversation's history is visible when another direct message with the same person, or
|
||||
group, is created.
|
||||
|
||||
.. _discuss/meetings:
|
||||
|
||||
Meetings
|
||||
========
|
||||
|
||||
In **Discuss**, *Meetings* are video calls. To start a meeting from the :guilabel:`Discuss`
|
||||
dashboard, click :guilabel:`Start a meeting` in the top-left corner, and select who to invite to the
|
||||
meeting, via the :guilabel:`Invite People` drop-down window that appears. To start a meeting from a
|
||||
direct message, click the :icon:`fa-phone` :guilabel:`Start a Call` icon in the top-right corner.
|
||||
|
||||
.. image:: discuss/meeting.png
|
||||
:alt: View of a Meeting in Odoo Discuss.
|
||||
|
||||
Once a meeting has been started, the following buttons can be used:
|
||||
|
||||
+-----------------------------+--------------------------------+
|
||||
| Icon | Use |
|
||||
+=============================+================================+
|
||||
| :icon:`fa-microphone` | :guilabel:`Mute` |
|
||||
+-----------------------------+--------------------------------+
|
||||
| :icon:`fa-microphone-slash` | :guilabel:`Unmute` |
|
||||
+-----------------------------+--------------------------------+
|
||||
| :icon:`fa-headphones` | :guilabel:`Deafen` |
|
||||
+-----------------------------+--------------------------------+
|
||||
| :icon:`fa-deaf` | :guilabel:`Undeafen` |
|
||||
+-----------------------------+--------------------------------+
|
||||
| :icon:`fa-video-camera` | :guilabel:`Turn camera on/off` |
|
||||
+-----------------------------+--------------------------------+
|
||||
| :icon:`fa-hand-paper-o` | :guilabel:`Raise Hand` |
|
||||
+-----------------------------+--------------------------------+
|
||||
| :icon:`fa-desktop` | :guilabel:`Share Screen` |
|
||||
+-----------------------------+--------------------------------+
|
||||
| :icon:`fa-arrows-alt` | :guilabel:`Enter Full Screen` |
|
||||
+-----------------------------+--------------------------------+
|
||||
|
||||
.. _discuss_app/notification_preferences:
|
||||
|
||||
User-specific notification preferences
|
||||
======================================
|
||||
|
||||
Access user-specific preferences for the **Discuss** app by navigating to :menuselection:`Settings
|
||||
app --> Manage Users`, select a user, then click the :guilabel:`Preferences` tab.
|
||||
|
||||
.. image:: discuss/preferences-user.png
|
||||
:alt: View of the Preferences tab for Odoo Discuss.
|
||||
|
||||
By default, the :guilabel:`Notification` field is set as :guilabel:`Handle by Emails`. With this
|
||||
setting enabled, a notification email is sent by Odoo every time a message is sent from the chatter
|
||||
of a record, a note is sent with an `@` mention (from the chatter of a record), or a notification is
|
||||
sent for a record the user follows.
|
||||
|
||||
By choosing :guilabel:`Handle in Odoo`, the above notifications are shown in the **Discuss** app's
|
||||
*Inbox*.
|
||||
|
||||
Chat from different applications
|
||||
================================
|
||||
|
||||
The **Discuss** application enables communication across all of Odoo's applications. To view chats
|
||||
and channels, or start a new message, select the speech bubbles that are consistently present in the
|
||||
upper-right corner of the database header.
|
||||
|
||||
.. image:: discuss/discuss-in-other-apps.png
|
||||
:alt: Use Discuss across other applications by clicking the speech bubbles.
|
||||
.. image:: discuss/status.png
|
||||
:height: 300
|
||||
:alt: View of the contacts' status for Odoo Discuss.
|
||||
|
||||
.. seealso::
|
||||
- :doc:`discuss/team_communication`
|
||||
- :doc:`/applications/essentials/activities`
|
||||
- :doc:`discuss/ice_servers`
|
||||
- :doc:`discuss/chatter`
|
||||
|
||||
.. toctree::
|
||||
:titlesonly:
|
||||
|
|
|
|||
|
After Width: | Height: | Size: 22 KiB |
BIN
content/applications/productivity/discuss/chat-windows.png
Normal file
|
After Width: | Height: | Size: 13 KiB |
|
Before Width: | Height: | Size: 1.2 KiB |
|
Before Width: | Height: | Size: 13 KiB |
|
Before Width: | Height: | Size: 8.1 KiB |
BIN
content/applications/productivity/discuss/odoobot-push.png
Normal file
|
After Width: | Height: | Size: 24 KiB |
|
Before Width: | Height: | Size: 6.8 KiB After Width: | Height: | Size: 8.6 KiB |
BIN
content/applications/productivity/discuss/reactions-discuss.png
Normal file
|
After Width: | Height: | Size: 5.3 KiB |
BIN
content/applications/productivity/discuss/starred-messages.png
Normal file
|
After Width: | Height: | Size: 14 KiB |
BIN
content/applications/productivity/discuss/status.png
Normal file
|
After Width: | Height: | Size: 37 KiB |
|
|
@@ -6,7 +6,7 @@ Introduction
|
|||
============
|
||||
|
||||
Odoo VoIP (Voice over Internet Protocol) can be set up to work together with `Axivox
|
||||
<https://www.axivox.com/>`_. In that case, a VoIP server is **not** necessary, as the
|
||||
<https://www.axivox.com/>`_. In that case, an Asterisk server is **not** necessary, as the
|
||||
infrastructure is hosted and managed by Axivox.
|
||||
|
||||
To use this service, `contact Axivox <https://www.axivox.com/en/contact>`_ to open an account.
|
||||
|
|
@@ -20,7 +20,7 @@ To configure Axivox in Odoo, go to the :menuselection:`Apps` application, and se
|
|||
Then, install the :guilabel:`VoIP` module.
|
||||
|
||||
Next, go to :menuselection:`Settings app --> General Settings --> Integrations section`, and fill
|
||||
out the :guilabel:`VoIP` field:
|
||||
out the :guilabel:`Asterisk (VoIP)` field:
|
||||
|
||||
- :guilabel:`OnSIP Domain`: set the domain created by Axivox for the account (e.g.,
|
||||
`yourcompany.axivox.com`)
|
||||
|
|
|
|||
|
Before Width: | Height: | Size: 10 KiB After Width: | Height: | Size: 5.9 KiB |
|
|
@@ -46,15 +46,15 @@ Odoo VoIP setting
|
|||
-----------------
|
||||
|
||||
After installing the *VOIP OnSIP* module, go to the :menuselection:`Settings app`, scroll down to
|
||||
the :guilabel:`Integrations` section, and locate the :guilabel:`VoIP` fields. Then, proceed to fill
|
||||
in those three fields with the following information:
|
||||
the :guilabel:`Integrations` section, and locate the :guilabel:`Asterisk (VoIP)` fields. Then,
|
||||
proceed to fill in those three fields with the following information:
|
||||
|
||||
- :guilabel:`OnSIP Domain`: the domain that was assigned when creating an account on `OnSIP
|
||||
<https://www.onsip.com/>`_.
|
||||
- :guilabel:`WebSocket`: `wss://edge.sip.onsip.com`
|
||||
- :guilabel:`VoIP Environment`: :guilabel:`Production`
|
||||
|
||||
.. image:: onsip/voip-setting.png
|
||||
.. image:: onsip/asterisk-setting.png
|
||||
:align: center
|
||||
:alt: VoIP configuration settings in Odoo Settings app.
|
||||
|
||||
|
|
|
|||
|
After Width: | Height: | Size: 5.7 KiB |
|
Before Width: | Height: | Size: 9.5 KiB |
|
|
@@ -7,8 +7,8 @@ customized PDF file for quotes, showcasing the company and products, with variou
|
|||
design elements, instead of just showing the price and total.
|
||||
|
||||
The PDF Quote Builder groups header pages, product descriptions, the price(s), and footer pages to
|
||||
create a detailed quote. It can also inject dynamic texts or custom notes in the PDF to personalize
|
||||
the offer for the customer.
|
||||
create a detailed quote. It can also inject dynamic texts in the PDF to personalize the offer for
|
||||
the customer.
|
||||
|
||||
Having a customized PDF in quotes provides a heightened conclusion to the shopping experience for
|
||||
customers, and adds an elegant level of professionalism to a company.
|
||||
|
|
@@ -30,45 +30,28 @@ To do that, navigate to :menuselection:`Sales app --> Configuration --> Settings
|
|||
:guilabel:`Settings` page, scroll to the :guilabel:`Quotations & Orders` section, and locate the
|
||||
:guilabel:`PDF Quote builder` feature.
|
||||
|
||||
Add PDF as Header/Footer
|
||||
========================
|
||||
.. image:: pdf_quote_builder/pdf-quote-builder-feature.png
|
||||
:align: center
|
||||
:alt: The PDF Quote Builder feature located on the Settings page of the Sales application.
|
||||
|
||||
In Odoo *Sales*, it's possible to add a custom PDF that can be used either as a header or a footer.
|
||||
When the PDF quote builder is activated in a quotation, you can then select as many headers and
|
||||
footers as you wish to use, these PDF will then also be inserted in the final PDF.
|
||||
|
||||
To add a custom PDF as header or footer, start by navigating to
|
||||
:menuselection:`Sales app --> Configuration --> Headers/Footers`. From this page, either click
|
||||
:guilabel:`New` or :guilabel:`Upload`.
|
||||
|
||||
Clicking :guilabel:`Upload` instantly provides the opportunity to upload the desired document. Then,
|
||||
the document can be further configured on the document card, or by clicking the three dots icon in
|
||||
the top right corner of the document card, and then clicking :guilabel:`Edit`.
|
||||
|
||||
Clicking :guilabel:`New` reveals a blank documents form, in which the desired PDF can be uploaded
|
||||
via the :guilabel:`Upload your file` button on the form, located in the :guilabel:`File Content`
|
||||
field.
|
||||
|
||||
Various information and configurations related to the uploaded document can be modified here.
|
||||
|
||||
The first field on the documents form is for the :guilabel:`Name` of the document, and it is
|
||||
grayed-out (not clickable) until a document is uploaded. Once a PDF has been uploaded, the
|
||||
:guilabel:`Name` field is auto-populated with the name of the PDF, and it can then be edited.
|
||||
|
||||
Then, in the :guilabel:`Document Type` field, click the drop-down menu, and select either:
|
||||
:guilabel:`Header`, or :guilabel:`Footer` to define whether these files would be selectable to be at
|
||||
the beginning or at the end of your quote.
|
||||
|
||||
Under this, in the :guilabel:`Quotation Templates` section, you can restrict this PDF to some quotation
|
||||
templates only.
|
||||
Here, custom :guilabel:`Header pages` and :guilabel:`Footer pages` can be uploaded. To upload
|
||||
either, click the :guilabel:`Upload your file` button, or the :guilabel:`✏️ (pencil)` icon to the
|
||||
right of the desired field, and proceed to locate, select, and upload the desired PDF file.
|
||||
|
||||
.. note::
|
||||
Alternatively, you can also navigate to
|
||||
:menuselection:`Sales app --> Configuration --> Quotation Templates`, select a template and
|
||||
directly :guilabel:`Add` or :guilabel:`Upload` a PDF to it in the :guilabel:`Quote Builder` tab.
|
||||
Headers and footers can also be added directly in a quotation template, so it's possible to have
|
||||
different variations per template.
|
||||
|
||||
Lastly, beside the :guilabel:`File Content` field, you have the possibility to
|
||||
:guilabel:`Configure dynamic fields`.
|
||||
Clicking the :guilabel:`🗑️ (trash)` icon deletes the current PDF file and replaces the blank field
|
||||
with an :guilabel:`Upload your file` button.
|
||||
|
||||
Once the desired PDF file(s) are uploaded in the appropriate fields in the :guilabel:`PDF Quote
|
||||
builder` section of the *Sales* :guilabel:`Settings` page, be sure to click :guilabel:`Save`.
|
||||
|
||||
The files uploaded here will be the default PDF used for all quotes.
|
||||
|
||||
.. note::
|
||||
Values set in the PDF Quote Builder settings are company-specific.
|
||||
|
||||
Dynamic text in PDFs
|
||||
====================
|
||||
|
|
@@ -82,10 +65,7 @@ automatically fills those values in with information related to the quote.
|
|||
Dynamic text values
|
||||
-------------------
|
||||
|
||||
Below are common dynamic text values used in custom PDFs that are already mapped to the correct
|
||||
fields, and what they represent.
|
||||
|
||||
For headers and footers PDF:
|
||||
Below are common dynamic text values used in custom PDFs, and what they represent:
|
||||
|
||||
- :guilabel:`name`: Sales Order Reference
|
||||
- :guilabel:`partner_id__name`: Customer Name
|
||||
|
|
@@ -96,8 +76,12 @@ For headers and footers PDF:
|
|||
- :guilabel:`validity_date`: Expiration Date
|
||||
- :guilabel:`client_order_ref`: Customer Reference
|
||||
|
||||
.. note::
|
||||
Double underscore notation for :guilabel:`partner_id__name` and :guilabel:`user_id__name` values
|
||||
are used in place of the typically used `.` symbol because the library currently does not support
|
||||
the `.` symbol.
|
||||
|
||||
For product PDF:
|
||||
Product-specific dynamic text values are as follows:
|
||||
|
||||
- :guilabel:`description`: Product Description
|
||||
- :guilabel:`quantity`: Quantity
|
||||
|
|
@@ -109,13 +93,6 @@ For product PDF:
|
|||
- :guilabel:`tax_excl_price`: Tax Excluded Price
|
||||
- :guilabel:`tax_incl_price`: Tax Included Price
|
||||
|
||||
After uploading a PDF, you can then :guilabel:`Configure dynamic fields`. This will allow you to map
|
||||
any field name found in your PDF to the field you want to show by writing down any existing path.
|
||||
Headers and footers starts from the current :guilabel:`sale_order` model, whereas product document
|
||||
follows their path from their :guilabel:`sale_order_line`.
|
||||
Leaving that path empty allows you to fill a custom notes, directly from the specific quote that
|
||||
requires it.
|
||||
|
||||
.. example::
|
||||
When a PDF is built, it's best practice to use common dynamic text values (:guilabel:`name` and
|
||||
:guilabel:`partner_id_name`). When uploaded into the database, Odoo auto-populates those fields
|
||||
|
|
@@ -129,20 +106,11 @@ requires it.
|
|||
:alt: PDF quote being built using common dynamic placeholders.
|
||||
|
||||
Once the PDF file(s) are complete, save them to the computer's hard drive, and proceed to upload
|
||||
them to Odoo via :menuselection:`Sales app --> Configuration --> Headers/Footers`.
|
||||
them to Odoo via :menuselection:`Sales app --> Configuration --> Settings --> PDF Quote builder`.
|
||||
|
||||
.. example::
|
||||
When uploading PDF containing the form field :guilabel:`invoice_partner_country`, which is an
|
||||
information available in the sales order, configure the :guilabel:`path` of the
|
||||
:guilabel:`Form Field Name` to:
|
||||
- :guilabel:`partner_invoice_id.country_id.name` for a header or footer document
|
||||
- :guilabel:`order_id.partner_invoice_id.country_id.name` for a product document
|
||||
fills the form with the invoice partner country's name when the PDF is built.
|
||||
Upload the created PDF in the :guilabel:`Header pages` or :guilabel:`Footer pages` field.
|
||||
|
||||
.. example::
|
||||
When uploading any PDF containing the form field :guilabel:`custom_note`, leaving the
|
||||
:guilabel:`path` empty allows the seller to write down any note where that form field is in that
|
||||
document and shown when the PDF is built.
|
||||
Once the upload(s) are complete, click :guilabel:`Save`.
|
||||
|
||||
Add PDF to product
|
||||
==================
|
||||
|
|
@@ -220,11 +188,6 @@ quote`.
|
|||
:align: center
|
||||
:alt: Sample of an uploaded pdf with the inside quote option chosen in Odoo Sales.
|
||||
|
||||
Beside the :guilabel:`File Content` field, you have the possibility to
|
||||
:guilabel:`Configure dynamic fields`. When doing so, remember that the starting model is the
|
||||
:guilabel:`sale_order_line`, unlike for headers and footers that start from the
|
||||
:guilabel:`sale_order`.
|
||||
|
||||
Lastly, in the :guilabel:`E-Commerce` section, decide whether or not to :guilabel:`Show on product
|
||||
page` on the front-end (in the online store).
|
||||
|
||||
|
|
@@ -242,13 +205,6 @@ page` on the front-end (in the online store).
|
|||
PDF quote
|
||||
=========
|
||||
|
||||
On a :guilabel:`Sales Order`, in the :guilabel:`Quote Builder` tab, select any document you want to
|
||||
be merged within the final PDF. If this document has custom fields, you'll then be able to write
|
||||
same notes to fill the PDF.
|
||||
|
||||
You can add as many headers, product documents and footers you want to customize your quote to the
|
||||
needs of your customers.
|
||||
|
||||
Once a quote with a pre-configured PDF has been confirmed, Odoo provides the option to print the
|
||||
confirmed quote to check for errors, or to keep for records.
|
||||
|
||||
|
|
|
|||
|
After Width: | Height: | Size: 9.2 KiB |
|
|
@@ -1202,6 +1202,8 @@ Many2many (`many2many`)
|
|||
Many2many Binary File (`many2many_binary`)
|
||||
This widget helps the user to upload or delete one or more files at the same time.
|
||||
|
||||
An image preview is available for files with the MIME type "image".
|
||||
|
||||
Note that this widget is specific to the model `ir.attachment`.
|
||||
|
||||
- Supported field types: `many2many`
|
||||
|
|
@@ -1212,6 +1214,8 @@ Many2many Binary File (`many2many_binary`)
|
|||
|
||||
(cf: ``accept`` attribute on `<input type="file" />`)
|
||||
|
||||
- `reverse_order`: set to `true` to add new files at the top of the list (default: `false`, new files are added at the bottom).
|
||||
|
||||
Many2many Tags (`many2many_tags`)
|
||||
Display a `many2many` field as a list of tags.
|
||||
|
||||
|
|
|
|||