[MERGE] Forward-port of branch 12.0 to 13.0
This commit is contained in:
commit
87ab494b42
@ -44,5 +44,5 @@ For Exim
|
||||
- `Exim <https://www.exim.org/docs.html>`_
|
||||
|
||||
.. tip::
|
||||
If you don't have access/manage your email server, use `inbound messages
|
||||
<https://www.odoo.com/documentation/user/13.0/discuss/advanced/email_servers.html#how-to-manage-outbound-messages>`_.
|
||||
If you don't have access/manage your email server, use :ref:`inbound messages
|
||||
<discuss/email_servers/inbound_messages>`.
|
||||
|
@ -167,7 +167,7 @@ In the above commands, the argument:
|
||||
* ``--stop-after-init`` will immediately shutdown the server instance after it completed the operations you asked.
|
||||
|
||||
More options are available and detailed in the
|
||||
`CLI documentation <https://www.odoo.com/documentation/13.0/reference/cmdline.html>`_.
|
||||
:doc:`CLI documentation </developer/reference/cmdline>`.
|
||||
|
||||
You can find in the logs (*~/logs/odoo.log*) the addons path used by Odoo.sh to run your server.
|
||||
Look for "*odoo: addons paths*":
|
||||
|
@ -42,7 +42,7 @@ instance will be held temporarily unavailable for maintenance reason.
|
||||
|
||||
This method is equivalent to perform an upgrade of the module through the Apps menu,
|
||||
or through the :code:`-u` switch of
|
||||
`the command line <https://www.odoo.com/documentation/13.0/reference/cmdline.html>`_.
|
||||
:doc:`the command line </developer/reference/cmdline>`.
|
||||
|
||||
In the case the changes in the commit prevent the server to restart,
|
||||
or if the modules update fails,
|
||||
@ -257,16 +257,16 @@ This server only keeps one month of backups: 7 daily and 4 weekly backups.
|
||||
Dedicated backup servers keep the same backups, as well as 3 additional monthly backups.
|
||||
To restore or download one of these monthly backups, please `contact us <https://www.odoo.com/help>`_.
|
||||
|
||||
If you merge a commit updating the version of one or several modules (in :file:`__manifest__.py`), or their linked python
|
||||
dependencies (in :file:`requirements.txt`), then Odoo.sh performs a backup automatically (flagged with type Update in the list),
|
||||
as either the container will be changed by the installation of new pip packages, either the database itself will be
|
||||
changed with the module update triggered afterwards. In these two cases, we are doing a backup as it may potentially
|
||||
If you merge a commit updating the version of one or several modules (in :file:`__manifest__.py`), or their linked python
|
||||
dependencies (in :file:`requirements.txt`), then Odoo.sh performs a backup automatically (flagged with type Update in the list),
|
||||
as either the container will be changed by the installation of new pip packages, either the database itself will be
|
||||
changed with the module update triggered afterwards. In these two cases, we are doing a backup as it may potentially
|
||||
break things.
|
||||
|
||||
If you merge a commit that only changes some code without the above-mentioned modifications, then no backup is done
|
||||
by Odoo.sh, as neither the container nor the database is modified so the platform considers this safe enough. Of course,
|
||||
as an extra precaution, you can make a backup manually before making big changes in your production sources in case
|
||||
something goes wrong (those manual backups are available for about one week). To avoid abuse, we limit manual backups
|
||||
If you merge a commit that only changes some code without the above-mentioned modifications, then no backup is done
|
||||
by Odoo.sh, as neither the container nor the database is modified so the platform considers this safe enough. Of course,
|
||||
as an extra precaution, you can make a backup manually before making big changes in your production sources in case
|
||||
something goes wrong (those manual backups are available for about one week). To avoid abuse, we limit manual backups
|
||||
to 5 per day.
|
||||
|
||||
The *import database* feature accepts database archives in the format provided by:
|
||||
@ -318,15 +318,15 @@ Staging builds duplicate the production build and the production build only inst
|
||||
**Test suite**
|
||||
|
||||
For development branches, you can choose to enable or disable the test suite. It's enabled by default.
|
||||
When the test suite is enabled, you can restrict them by specifying test tags `test tags
|
||||
<https://www.odoo.com/documentation/12.0/reference/testing.html#test-selection>`_.
|
||||
When the test suite is enabled, you can restrict them by specifying test tags :ref:`test tags
|
||||
<developer/reference/testing/selection>`.
|
||||
|
||||
**Odoo Version**
|
||||
|
||||
For development branches only, you can change the version of Odoo, should you want to test upgraded code or develop
|
||||
features while your production database is in the process of being upgraded to a newer version.
|
||||
|
||||
In addition, for each version you have two options regarding the code update.
|
||||
In addition, for each version you have two options regarding the code update.
|
||||
|
||||
* You can choose to benefit from the latest bug, security and performance fixes automatically. The
|
||||
sources of your Odoo server will be updated weekly. This is the 'Latest' option.
|
||||
|
@ -108,8 +108,7 @@ Access the URL :file:`/web/database/manager` of your on-premise database and dow
|
||||
.. Warning::
|
||||
|
||||
If you cannot access the database manager, it may have been disabled by your system administrator.
|
||||
See the `database manager security documentation
|
||||
<https://www.odoo.com/documentation/13.0/setup/deploy.html#database-manager-security>`_.
|
||||
See the :ref:`database manager security documentation <db_manager_security>`.
|
||||
|
||||
You will need the master password of your database server. If you do not have it, contact your system administrator.
|
||||
|
||||
@ -152,7 +151,7 @@ Check your outgoing email servers
|
||||
There is a default mail server provided with Odoo.sh.
|
||||
To use it, there must be no enabled outgoing mail server configured in your database in
|
||||
:menuselection:`Settings --> Technical --> Outgoing Mail Servers`
|
||||
(:doc:`Developer mode <../../../../applications/general/developer_mode/activate>` must be activated).
|
||||
(:doc:`Developer mode </applications/general/developer_mode/activate>` must be activated).
|
||||
|
||||
After the import of your database,
|
||||
all outgoing email servers are disabled so you use the Odoo.sh email server provided by default.
|
||||
|
@ -88,8 +88,7 @@ From the Odoo.sh editor, in a terminal:
|
||||
|
||||
$ odoo-bin scaffold my_module ~/src/user/
|
||||
|
||||
Or, from your computer, if you have an `installation of Odoo
|
||||
<https://www.odoo.com/documentation/13.0/setup/install.html#source-install>`_:
|
||||
Or, from your computer, if you have an :ref:`installation of Odoo <setup/install/source>`:
|
||||
|
||||
.. code-block:: bash
|
||||
|
||||
@ -150,7 +149,7 @@ Manually
|
||||
--------
|
||||
|
||||
If you want to create your module structure manually,
|
||||
you can follow `Build an Odoo module <https://www.odoo.com/documentation/13.0/howtos/backend.html>`_ to understand
|
||||
you can follow :doc:`Build an Odoo module </developer/howtos/backend>` to understand
|
||||
the structure of a module and the content of each file.
|
||||
|
||||
Push the development branch
|
||||
@ -264,7 +263,7 @@ and on your production you would not like your module to be installed automatica
|
||||
|
||||
Your module may not appear directly in your apps to install either, you need to update your apps list first:
|
||||
|
||||
* activate the :doc:`Developer mode <../../../applications/general/developer_mode/activate>`
|
||||
* activate the :doc:`Developer mode </applications/general/developer_mode/activate>`
|
||||
* in the apps menu, click the *Update Apps List* button,
|
||||
* in the dialog that appears, click the *Update* button.
|
||||
|
||||
|
@ -122,7 +122,7 @@ database, please `submit a support ticket <https://www.odoo.com/help>`_.
|
||||
How can I update my bank credentials?
|
||||
-------------------------------------
|
||||
You can update your credentials in
|
||||
:doc:`Developer mode <../../../../../applications/general/developer_mode>`.
|
||||
:doc:`Developer mode </applications/general/developer_mode>`.
|
||||
|
||||
Then go to :menuselection:`Accounting --> Configuration --> Online Synchronization`, and open the
|
||||
Institution you want to edit, and click on *Update Credentials*.
|
||||
|
@ -82,7 +82,7 @@ Update your synchronization credentials
|
||||
|
||||
You might have to update your Ponto credentials or modify the synchronization settings.
|
||||
|
||||
To do so, activate the :doc:`Developer Mode <../../../../../applications/general/developer_mode>`, and go to
|
||||
To do so, activate the :doc:`Developer Mode </applications/general/developer_mode>`, and go to
|
||||
:menuselection:`Accounting --> Configuration --> Online Synchronization`.
|
||||
|
||||
Click on *Update Accounts* to enter your new Client ID and Secret ID, or click on *Edit* to modify
|
||||
|
@ -275,7 +275,7 @@ Sequences
|
||||
~~~~~~~~~
|
||||
In case that you want to synchronize the next number in the sequence in Odoo based on the next
|
||||
number in the AFIP POS, the next button that is visible under :doc:`developer mode
|
||||
<../../../../../applications/general/developer_mode>` can be used:
|
||||
</applications/general/developer_mode>` can be used:
|
||||
|
||||
.. image:: media/argentina_edi_05.png
|
||||
:align: center
|
||||
|
@ -142,7 +142,7 @@ Journals
|
||||
Once the DIAN has assigned the official sequence and prefix for the
|
||||
electronic invoice resolution, the Sales journals related to your
|
||||
invoice documents need to be updated in Odoo. The sequence can be
|
||||
accessed using the :doc:`Developer mode <../../../../../applications/general/developer_mode>`: :menuselection:`Accounting -->
|
||||
accessed using the :doc:`Developer mode </applications/general/developer_mode>`: :menuselection:`Accounting -->
|
||||
Settings --> Configuration Setting --> Journals`.
|
||||
|
||||
.. image:: media/colombia09.png
|
||||
|
@ -52,7 +52,7 @@ of conformity testifying that your software complies with the anti-fraud
|
||||
legislation. This certificate is granted by Odoo SA to Odoo Enterprise users
|
||||
`here <https://www.odoo.com/my/contract/french-certification/>`_.
|
||||
If you use Odoo Community, you should
|
||||
`upgrade to Odoo Enterprise <https://www.odoo.com/documentation/13.0/setup/enterprise.html>`_
|
||||
:doc:`upgrade to Odoo Enterprise </administration/enterprise>`
|
||||
or contact your Odoo service provider.
|
||||
|
||||
In case of non-conformity, your company risks a fine of €7,500.
|
||||
@ -74,7 +74,7 @@ To get the certification just follow the following steps:
|
||||
.. note::
|
||||
* To install the module in any system created before
|
||||
December 18th 2017, you should update the modules list.
|
||||
To do so, activate the :doc:`Developer mode <../../../../../applications/general/developer_mode>`.
|
||||
To do so, activate the :doc:`Developer mode </applications/general/developer_mode>`.
|
||||
Then go to the *Apps* menu and press *Update Modules List* in the top-menu.
|
||||
* In case you run Odoo on-premise, you need to update your installation
|
||||
and restart your server beforehand.
|
||||
@ -156,7 +156,7 @@ Invoicing and Accounting apps.
|
||||
it will be counted in the very next closing.
|
||||
|
||||
.. tip:: For test & audit purposes such closings can be manually generated in the
|
||||
:doc:`Developer mode <../../../../../applications/general/developer_mode>`. Then go to
|
||||
:doc:`Developer mode </applications/general/developer_mode>`. Then go to
|
||||
:menuselection:`Settings --> Technical --> Automation --> Scheduled Actions`.
|
||||
|
||||
|
||||
|
@ -25,7 +25,7 @@ elettronica sono i seguenti:
|
||||
di posta elettronica certificata sono fornite dal tuo fornitore o dal
|
||||
Ministero. Lo stesso server deve essere configurato come server che
|
||||
gestisce tutta la corrispondenza mail in Odoo, per saperne di più si
|
||||
puo’ consultare la relativa :doc:`guida <../../../../productivity/discuss/advanced/email_servers>`.
|
||||
puo’ consultare la relativa :doc:`guida </applications/productivity/discuss/advanced/email_servers>`.
|
||||
|
||||
- Indirizzo PEC dell’ Azienda, tale indirizzo deve essere lo stesso
|
||||
registrato presso l’Agenzia delle Entrate per l’utilizzo dei servizi
|
||||
|
@ -111,7 +111,7 @@ Enabling CFDI Version 3.3
|
||||
SaaS instance please ask for an upgrade by submitting a ticket to support in
|
||||
https://www.odoo.com/help.
|
||||
|
||||
Enable the :doc:`Developer mode <../../../../../applications/general/developer_mode>`.
|
||||
Enable the :doc:`Developer mode </applications/general/developer_mode>`.
|
||||
|
||||
Go and look the following technical parameter, on
|
||||
:menuselection:`Settings --> Technical --> Parameters --> System Parameters`
|
||||
@ -630,7 +630,7 @@ Enabling Explicit errors on the CFDI using the XSD local validator (CFDI 3.3)
|
||||
Frequently you want receive explicit errors from the fields incorrectly set
|
||||
on the xml, those errors are better informed to the user if the check is
|
||||
enable, to enable the Check with xsd feature follow the next steps (with the
|
||||
:doc:`Developer mode <../../../../../applications/general/developer_mode>` enabled).
|
||||
:doc:`Developer mode </applications/general/developer_mode>` enabled).
|
||||
|
||||
- Go to :menuselection:`Settings --> Technical --> Actions --> Server Actions`
|
||||
- Look for the Action called "Download XSD files to CFDI"
|
||||
|
@ -73,7 +73,7 @@ of measures.
|
||||
:align: center
|
||||
|
||||
For more information on how to create a sales order based on time and
|
||||
material please see :doc:`../../../../sales/sales/invoicing/time_materials`.
|
||||
material please see :doc:`/applications/sales/sales/invoicing/time_materials`.
|
||||
|
||||
We save a Sales Order with the service product **External Consulting**. An
|
||||
analytical account will automatically be generated once the **Sales Order**
|
||||
|
@ -1,10 +1,9 @@
|
||||
===========
|
||||
=========
|
||||
Inventory
|
||||
===========
|
||||
=========
|
||||
|
||||
.. toctree::
|
||||
:titlesonly:
|
||||
|
||||
inventory/avg_price_valuation
|
||||
../../../inventory_and_mrp/inventory/management/reporting/inventory_valuation_config
|
||||
|
||||
/applications/inventory_and_mrp/inventory/management/reporting/inventory_valuation_config
|
||||
|
@ -12,7 +12,7 @@ amount is first credited on a debt account before a later payment reconciliation
|
||||
.. note::
|
||||
Expenses paid by employees can be managed with **Odoo Expenses**, an app dedicated to the
|
||||
approval of such expenses and the payments management. Click :doc:`here
|
||||
<../../../expense/expense>` for more information on how to use Odoo Expenses.
|
||||
</applications/finance/expense/expense>` for more information on how to use Odoo Expenses.
|
||||
|
||||
Register a receipt
|
||||
==================
|
||||
@ -42,4 +42,4 @@ needs, and click on *Post*.
|
||||
|
||||
.. seealso::
|
||||
- :doc:`manage`
|
||||
- :doc:`../../../expense/expense`
|
||||
- :doc:`/applications/finance/expense/expense`
|
||||
|
@ -42,7 +42,7 @@ lines, invoice a fixed advance.
|
||||
This process is good for both services and physical products.
|
||||
|
||||
.. seealso::
|
||||
- :doc:`../../../../sales/sales/invoicing/proforma`
|
||||
- :doc:`/applications/sales/sales/invoicing/proforma`
|
||||
|
||||
Sales Order ‣ Delivery Order ‣ Invoice
|
||||
--------------------------------------
|
||||
@ -58,7 +58,7 @@ later), the customer will receive two invoices, one for each delivery
|
||||
order.
|
||||
|
||||
.. seealso::
|
||||
- :doc:`../../../../sales/sales/invoicing/invoicing_policy`
|
||||
- :doc:`/applications/sales/sales/invoicing/invoicing_policy`
|
||||
|
||||
eCommerce Order ‣ Invoice
|
||||
-------------------------
|
||||
@ -91,9 +91,9 @@ mostly based on time and material. For services companies that invoice
|
||||
on fix price, they use a regular sales order.
|
||||
|
||||
.. seealso::
|
||||
- :doc:`../../../../sales/sales/invoicing/time_materials`
|
||||
- :doc:`../../../../sales/sales/invoicing/expense`
|
||||
- :doc:`../../../../sales/sales/invoicing/milestone`
|
||||
- :doc:`/applications/sales/sales/invoicing/time_materials`
|
||||
- :doc:`/applications/sales/sales/invoicing/expense`
|
||||
- :doc:`/applications/sales/sales/invoicing/milestone`
|
||||
|
||||
Recurring Contracts ‣ Invoices
|
||||
------------------------------
|
||||
@ -103,7 +103,7 @@ The frequency of the invoicing and the services/products invoiced are
|
||||
defined on the contract.
|
||||
|
||||
.. seealso::
|
||||
- :doc:`../../../../sales/sales/invoicing/subscriptions`
|
||||
- :doc:`/applications/sales/sales/invoicing/subscriptions`
|
||||
|
||||
Others
|
||||
======
|
||||
|
@ -17,7 +17,7 @@ Configuration
|
||||
Make sure your :ref:`Payment Acquirers are correctly configured <payment_acquirers/configuration>`.
|
||||
|
||||
.. note::
|
||||
By default, ":doc:`Wire Transfer <../../../../general/payment_acquirers/wire_transfer>`" is the only
|
||||
By default, ":doc:`Wire Transfer </applications/general/payment_acquirers/wire_transfer>`" is the only
|
||||
Payment Acquirer activated, but you still have to fill out the payment details.
|
||||
|
||||
To activate the Invoice Online Payment, go to :menuselection:`Accounting --> Configuration -->
|
||||
@ -42,4 +42,4 @@ They can choose which Payment Acquirer to use by clicking on *Pay Now*.
|
||||
|
||||
.. seealso::
|
||||
|
||||
- :doc:`../../../../general/payment_acquirers/payment_acquirers`
|
||||
- :doc:`/applications/general/payment_acquirers/payment_acquirers`
|
||||
|
@ -14,7 +14,7 @@ Activate the developer mode
|
||||
===========================
|
||||
|
||||
In order to have access to the financial report creation interface, the
|
||||
:doc:`Developer mode <../../../../../applications/general/developer_mode>` needs to be activated.
|
||||
:doc:`Developer mode </applications/general/developer_mode>` needs to be activated.
|
||||
|
||||
Create your financial report
|
||||
============================
|
||||
|
@ -24,7 +24,7 @@ IAP accounts
|
||||
|
||||
Credits to use IAP services are stored on IAP accounts, which are specific to each service and
|
||||
database. By default, IAP accounts are common to all companies, but can be restricted to specific
|
||||
ones. Activate the :doc:`Developer mode <../../../../applications/general/developer_mode>`, then go to
|
||||
ones. Activate the :doc:`Developer mode </applications/general/developer_mode>`, then go to
|
||||
:menuselection:`Technical Settings --> IAP Account`.
|
||||
|
||||
.. image:: media/image2.png
|
||||
@ -67,5 +67,5 @@ Offering my own services
|
||||
|
||||
I am more than welcome to offer my own IAP services through Odoo Apps! It is the perfect opportunity
|
||||
to get recurring revenue for an ongoing service use rather than — and possibly instead of — a sole
|
||||
initial purchase. Please, find more information at: `In-App Purchase
|
||||
<https://www.odoo.com/documentation/13.0/webservices/iap.html>`_
|
||||
initial purchase. Please, find more information at: :doc:`In-App Purchase
|
||||
</developer/webservices/iap>`.
|
||||
|
@ -128,5 +128,5 @@ at an invoice/bills level or at a sales/purchase orders level.
|
||||
Remember to test all workflows as an user other than the administrator.
|
||||
|
||||
.. seealso::
|
||||
- `Multi-company Guidelines <https://www.odoo.com/documentation/13.0/howtos/company.html>`_
|
||||
- :doc:`Multi-company Guidelines </developer/howtos/company>`
|
||||
- :doc:`../../finance/accounting/others/multicurrencies/how_it_works`
|
||||
|
@ -39,7 +39,7 @@ the user. The user must click on it to accept the invitation and create a login.
|
||||
`pricing page <https://www.odoo.com/pricing>`_
|
||||
for more information.
|
||||
|
||||
With the :doc:`Developer mode <../../../../applications/general/developer_mode>` activated, *User Types* can
|
||||
With the :doc:`Developer mode </applications/general/developer_mode>` activated, *User Types* can
|
||||
be selected.
|
||||
|
||||
.. image:: users/user-type.png
|
||||
@ -121,7 +121,7 @@ can reaccess your database using your new password.
|
||||
Access Rights in detail
|
||||
=======================
|
||||
|
||||
Activate the :doc:`Developer mode <../../../../applications/general/developer_mode>`, then go to
|
||||
Activate the :doc:`Developer mode </applications/general/developer_mode>`, then go to
|
||||
:menuselection:`Settings --> Users & Companies --> Groups`.
|
||||
|
||||
Groups
|
||||
@ -194,7 +194,7 @@ the user can have access.
|
||||
.. note::
|
||||
Note that if not handled correctly, it may be the source of a lot of inconsistent multi-company
|
||||
behaviors. Therefore, a good knowledge of Odoo is required. For technical explanations refer
|
||||
to `this <https://www.odoo.com/documentation/13.0/howtos/company.html>`_ documentation.
|
||||
to :doc:`this </developer/howtos/company>` documentation.
|
||||
|
||||
.. image:: users/multi-companies.png
|
||||
:align: center
|
||||
|
@ -14,7 +14,7 @@ Create a Barcode Nomenclature
|
||||
|
||||
Odoo supports Barcode Nomenclatures, which determine the mapping and
|
||||
interpretation of the encoded information. You can configure your barcode nomenclature being in
|
||||
:doc:`Developer mode <../../../../../applications/general/developer_mode>`.
|
||||
:doc:`Developer mode </applications/general/developer_mode>`.
|
||||
To do so, go to :menuselection:`Inventory --> Configuration --> Barcode Nomenclature`.
|
||||
|
||||
You can create a barcode nomenclature from there, and then add a line to
|
||||
|
@ -66,4 +66,4 @@ Please read documentation on :doc:`three_steps`
|
||||
|
||||
.. seealso::
|
||||
- :doc:`../delivery/inventory_flow`
|
||||
- :doc:`../../../purchase/purchases/rfq/analyze`
|
||||
- :doc:`/applications/inventory_and_mrp/purchase/purchases/rfq/analyze`
|
||||
|
@ -45,7 +45,7 @@ Configure and run the scheduler (for advanced users)
|
||||
----------------------------------------------------
|
||||
|
||||
To use this feature, you have to enable the
|
||||
:doc:`Developer mode <../../../../../applications/general/developer_mode>` mode.
|
||||
:doc:`Developer mode </applications/general/developer_mode>` mode.
|
||||
|
||||
Then, go to :menuselection:`Settings --> Technical --> Automation --> Scheduled Actions`
|
||||
and modify the *Run MRP Scheduler Configuration*. There, you can set
|
||||
|
@ -9,4 +9,4 @@ Valuation Methods
|
||||
reporting/inventory_valuation_config
|
||||
reporting/using_inventory_valuation
|
||||
reporting/integrating_landed_costs
|
||||
../../../finance/accounting/others/inventory/avg_price_valuation
|
||||
/applications/finance/accounting/others/inventory/avg_price_valuation
|
||||
|
@ -184,7 +184,7 @@ accounting modes.
|
||||
|
||||
Usually, based on your country, the correct accounting mode will be
|
||||
chosen by default. If you want to verify your accounting mode, activate
|
||||
the :doc:`Developer mode <../../../../../applications/general/developer_mode>` and open your accounting
|
||||
the :doc:`Developer mode </applications/general/developer_mode>` and open your accounting
|
||||
settings.
|
||||
|
||||
Manual Inventory Valuation
|
||||
|
@ -54,4 +54,4 @@ shipped.
|
||||
|
||||
.. seealso::
|
||||
|
||||
* :doc:`../../../purchase/replenishment/flows/setup_stock_rule`
|
||||
* :doc:`/applications/inventory_and_mrp/purchase/replenishment/flows/setup_stock_rule`
|
||||
|
@ -30,7 +30,7 @@ quantity it will replenish your stock to your **maximum quantity**.
|
||||
*Inventory* module runs. By default in Odoo, the schedulers will run
|
||||
every night at 12:00PM.
|
||||
|
||||
See also: :doc:`../../../inventory/management/planning/schedulers`
|
||||
See also: :doc:`/applications/inventory_and_mrp/inventory/management/planning/schedulers`
|
||||
|
||||
From now on, every time a product with a reordering rule reaches the
|
||||
minimum stock, the system will automatically see how to fulfill that
|
||||
|
@ -96,7 +96,7 @@ a transfer or when manufacturing it.
|
||||
|
||||
.. tip::
|
||||
This process can be simplified by using a connected :doc:`camera
|
||||
<../../../productivity/iot/devices/measurement_tool>`.
|
||||
</applications/productivity/iot/devices/measurement_tool>`.
|
||||
|
||||
Pass-Fail
|
||||
---------
|
||||
@ -153,7 +153,7 @@ gives instructions to the worker.
|
||||
:alt:
|
||||
|
||||
.. tip::
|
||||
This process can be simplified by using connected :doc:`measurement tools <../../../productivity/iot/devices/camera>`.
|
||||
This process can be simplified by using connected :doc:`measurement tools </applications/productivity/iot/devices/camera>`.
|
||||
|
||||
Register Consumed Materials
|
||||
---------------------------
|
||||
@ -204,4 +204,4 @@ to the product during the manufacturing process.
|
||||
:alt:
|
||||
|
||||
.. tip::
|
||||
This process can be simplified by using a connected :doc:`printer <../../../productivity/iot/devices/printer>`.
|
||||
This process can be simplified by using a connected :doc:`printer </applications/productivity/iot/devices/printer>`.
|
||||
|
@ -82,6 +82,6 @@ Manage campaigns
|
||||
menu within those applications. All of this is possible because the applications work integrated.
|
||||
|
||||
.. seealso::
|
||||
- :doc:`../../../productivity/discuss/advanced/email_servers`
|
||||
- :doc:`/applications/productivity/discuss/advanced/email_servers`
|
||||
- :doc:`../../social_marketing/overview/campaigns`
|
||||
|
||||
|
@ -64,7 +64,7 @@ Speakers*.
|
||||
.. note::
|
||||
Credits are required to be able to send SMSs. For more information about Pricing :doc:`click here
|
||||
<../../sms_marketing/pricing/pricing_and_faq>`, and, about IAP Services :doc:`here
|
||||
<../../../general/in_app_purchase/in_app_purchase>`.
|
||||
</applications/general/in_app_purchase/in_app_purchase>`.
|
||||
|
||||
|
||||
|
||||
|
@ -50,4 +50,4 @@ among the payment methods you chose to have available.
|
||||
:alt: View of website transaction for Odoo Events
|
||||
|
||||
.. seealso::
|
||||
- :doc:`../../../general/payment_acquirers/payment_acquirers`
|
||||
- :doc:`/applications/general/payment_acquirers/payment_acquirers`
|
||||
|
@ -64,4 +64,4 @@ Use cases
|
||||
|
||||
.. seealso::
|
||||
- :doc:`automate_actions`
|
||||
- :doc:`../../../general/tags/take_tags`
|
||||
- :doc:`/applications/general/tags/take_tags`
|
||||
|
@ -47,7 +47,7 @@ all the contacts needed, and under *Action* select *Send SMS*.
|
||||
Set up SMS templates
|
||||
====================
|
||||
|
||||
To set up *SMS Templates*, activate the :doc:`Developer mode <../../../general/developer_mode/activate>`,
|
||||
To set up *SMS Templates*, activate the :doc:`Developer mode </applications/general/developer_mode/activate>`,
|
||||
then go to :menuselection:`Technical --> SMS Templates`.
|
||||
|
||||
.. image:: ./media/sms_marketing17.png
|
||||
@ -77,4 +77,4 @@ then go to :menuselection:`Technical --> SMS Templates`.
|
||||
|
||||
.. seealso::
|
||||
- :doc:`../../social_marketing/overview/campaigns`
|
||||
- :doc:`../../../productivity/discuss/advanced/email_template`
|
||||
- :doc:`/applications/productivity/discuss/advanced/email_template`
|
||||
|
@ -100,7 +100,7 @@ More common questions
|
||||
|
||||
Yes, the SMS is logged as a note under the chatter of the corresponding record, and a complete
|
||||
history of the SMSs sent is available on
|
||||
:doc:`Developer mode <../../../general/developer_mode/activate>` under
|
||||
:doc:`Developer mode </applications/general/developer_mode/activate>` under
|
||||
:menuselection:`Technical --> SMS`.
|
||||
|
||||
|
||||
|
@ -57,4 +57,4 @@ on the respective pages.
|
||||
:alt: Choose the pages to be tracked in the website application for Odoo Social Marketing
|
||||
|
||||
.. seealso::
|
||||
- :doc:`../../../websites/livechat/overview/get_started`
|
||||
- :doc:`/applications/websites/livechat/overview/get_started`
|
||||
|
@ -108,6 +108,8 @@ Restriction
|
||||
-----------
|
||||
Please note that the port 25 is blocked for security reasons. Try using 587, 465 or 2525.
|
||||
|
||||
.. _discuss/email_servers/inbound_messages:
|
||||
|
||||
How to manage inbound messages
|
||||
==============================
|
||||
|
||||
@ -161,10 +163,10 @@ alias in your mail server.
|
||||
You should set redirections for all the email addresses to Odoo's domain name in your
|
||||
email server (e.g. *catchall@mydomain.ext* to *catchall@mycompany.odoo.com*).
|
||||
|
||||
.. tip:: All the aliases are customizable in Odoo.
|
||||
.. tip:: All the aliases are customizable in Odoo.
|
||||
Object aliases can be edited from their respective configuration view.
|
||||
To edit catchall and bounce aliases, you first need to activate the
|
||||
:doc:`Developer mode <../../../../applications/general/developer_mode>`.
|
||||
:doc:`Developer mode </applications/general/developer_mode>`.
|
||||
|
||||
Then go to :menuselection:`Settings --> Technical --> Parameters --> System Parameters`
|
||||
to customize the aliases (*mail.catchall.alias* & * mail.bounce.alias*).
|
||||
@ -172,11 +174,11 @@ alias in your mail server.
|
||||
.. image:: media/system_parameters.png
|
||||
:align: center
|
||||
|
||||
.. note:: By default inbound messages are fetched every 5 minutes in Odoo on-premise.
|
||||
You can change this value in :doc:`Developer mode <../../../../applications/general/developer_mode>`.
|
||||
Go to :menuselection:`Settings --> Technical --> Automation -->
|
||||
.. note:: By default inbound messages are fetched every 5 minutes in Odoo on-premise.
|
||||
You can change this value in :doc:`Developer mode </applications/general/developer_mode>`.
|
||||
Go to :menuselection:`Settings --> Technical --> Automation -->
|
||||
Scheduled Actions` and look for *Mail: Fetchmail Service*.
|
||||
|
||||
|
||||
.. _Office 365 documentation:
|
||||
https://support.office.com/en-us/article/how-to-set-up-a-multifunction-device-or-application-to-send-email-using-office-365-69f58e99-c550-4274-ad18-c805d654b4c4
|
||||
|
||||
@ -195,7 +197,7 @@ or Sendgrid for mass mailings.
|
||||
unless you want to use a specific external outgoing email server for technical reasons.
|
||||
|
||||
To do this, you should first enable the :doc:`Developer mode
|
||||
<../../../../applications/general/developer_mode>` and then go to :menuselection:`Settings --> Technical
|
||||
</applications/general/developer_mode>` and then go to :menuselection:`Settings --> Technical
|
||||
--> Outgoing` e-mail servers. There you have to create two e-mail MTA server settings. One for
|
||||
transactional e-mails and one for mass mail servers. Be sure to mark the priority of transactional
|
||||
e-mail servers as low as the mass email servers.
|
||||
|
@ -11,7 +11,7 @@ improving their overall experience with the company.
|
||||
Enable it and understand a few concepts
|
||||
=======================================
|
||||
|
||||
The :doc:`Developer mode <../../../../applications/general/developer_mode>` must be activated. Then, go to
|
||||
The :doc:`Developer mode </applications/general/developer_mode>` must be activated. Then, go to
|
||||
:menuselection:`Settings --> Technical --> Templates`. A view of the existing templates is shown.
|
||||
|
||||
.. warning::
|
||||
|
@ -11,7 +11,7 @@ Choose your notifications preference
|
||||
====================================
|
||||
|
||||
Access your *Preferences* and choose how you would like your
|
||||
:doc:`Chatter <../../../services/project/tasks/collaborate>` notifications to be handled.
|
||||
:doc:`Chatter </applications/services/project/tasks/collaborate>` notifications to be handled.
|
||||
|
||||
.. image:: media/change_preferences.png
|
||||
:align: center
|
||||
@ -61,7 +61,7 @@ You can also create :doc:`public and private channels <team_communication>`.
|
||||
Mentions in the chat and on the Chatter
|
||||
---------------------------------------
|
||||
|
||||
| To mention a user within a chat or the :doc:`chatter <../../../services/project/tasks/collaborate>` type
|
||||
| To mention a user within a chat or the :doc:`chatter </applications/services/project/tasks/collaborate>` type
|
||||
*@user-name*; to refer to a channel, type *#channel-name*.
|
||||
| A notification is sent to the user mentioned either to his *Inbox* or through email, depending
|
||||
on his settings.
|
||||
@ -72,7 +72,7 @@ Mentions in the chat and on the Chatter
|
||||
|
||||
.. tip::
|
||||
When a user is mentioned, the search list (list of names) suggests values first based on the
|
||||
task’s :doc:`followers <../../../services/project/tasks/collaborate>`, and secondly on *Employees*. If the
|
||||
task’s :doc:`followers </applications/services/project/tasks/collaborate>`, 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.
|
||||
|
||||
@ -94,6 +94,6 @@ sidebar and on the *Messaging menu*.
|
||||
:alt: View of the contacts’ status for Odoo Discuss
|
||||
|
||||
.. seealso::
|
||||
- :doc:`../../../services/project/tasks/collaborate`
|
||||
- :doc:`/applications/services/project/tasks/collaborate`
|
||||
- :doc:`team_communication`
|
||||
- :doc:`../advanced/email_servers`
|
||||
|
@ -19,7 +19,7 @@ Access and manage your activities wherever you are in Odoo by the *Activities* m
|
||||
Plan activities
|
||||
===============
|
||||
|
||||
Activities can be planned and managed from the :doc:`Chatter <../../../services/project/tasks/collaborate>`
|
||||
Activities can be planned and managed from the :doc:`Chatter </applications/services/project/tasks/collaborate>`
|
||||
by clicking on *Schedule activity*, or through Kanban views.
|
||||
|
||||
.. image:: media/schedule_activity.png
|
||||
|
@ -55,7 +55,7 @@ Then, you have to connect the peripheral devices to your IoT Box.
|
||||
|
||||
- **Payment terminal**: The connection process depends on the terminal,
|
||||
please refer to the :doc:`payment terminals documentation
|
||||
<../../../sales/point_of_sale/payment>`.
|
||||
</applications/sales/point_of_sale/payment>`.
|
||||
|
||||
Once it's done, you can connect the IoT Box to your PoS. For this, go in
|
||||
:menuselection:`Point of Sale --> Configuration --> PoS`, tick *IoT Box*
|
||||
|
@ -48,10 +48,10 @@ For every Trigger option, **conditions** can be applied, such as:
|
||||
- *Update a Record*: updates the record that triggered the action.
|
||||
- *Execute several actions*: defines an action that triggers other server actions.
|
||||
- *Send Email*: an automatic :doc:`email <../../discuss/advanced/email_template>` is sent.
|
||||
- *Add Followers*: :doc:`followers <../../../services/project/tasks/collaborate>` are notified of changes in
|
||||
- *Add Followers*: :doc:`followers </applications/services/project/tasks/collaborate>` are notified of changes in
|
||||
the task.
|
||||
- *Create Next Activity*: creates an activity such as: *Call*, *Email*, *Reminder*.
|
||||
- *Send SMS Text Message*: sends an :doc:`SMS <../../../marketing/sms_marketing/pricing/pricing_and_faq>`.
|
||||
- *Send SMS Text Message*: sends an :doc:`SMS </applications/marketing/sms_marketing/pricing/pricing_and_faq>`.
|
||||
|
||||
Example
|
||||
~~~~~~~
|
||||
|
@ -34,7 +34,7 @@ them. Fields with related objects have their directives shown on *Field Expressi
|
||||
| Under **Visible if**, define the rule(s) to set visibility conditions to fields.
|
||||
| Example: if choosing to display a product image, you could set a visibility rule to only display
|
||||
the ones that are *set* in the product form, avoiding having a plain icon when they are not set.
|
||||
| **Visible for** is used to set which :doc:`groups <../../../general/odoo_basics/users>`
|
||||
| **Visible for** is used to set which :doc:`groups </applications/general/odoo_basics/users>`
|
||||
can have access to specific elements in the report. **Limit visibility to groups**, under
|
||||
*Report*, sets the visibility of the report to specifics groups, meaning that users belonging to
|
||||
other groups do not see the same final document.
|
||||
@ -50,7 +50,7 @@ added to the *Print* menu list on its respective document form.
|
||||
:align: center
|
||||
:alt: View of an invoice form emphasizing the menu print for Odoo Studio
|
||||
|
||||
If activating the :doc:`Developer mode <../../../general/developer_mode/activate>`, additional fields
|
||||
If activating the :doc:`Developer mode </applications/general/developer_mode/activate>`, additional fields
|
||||
such as *Class* under *Options*, and *Reload from attachment* under *Report*, become visible.
|
||||
|
||||
- *Class*: add custom CSS classes to the selected element (e.g. Bootstrap classes such as
|
||||
|
@ -116,7 +116,7 @@ Administrator* or managers.
|
||||
|
||||
- **Case scenario 5: change the tooltip of a field for all views.**
|
||||
|
||||
| Activate the :doc:`Developer mode <../../../general/developer_mode/activate>` and open Studio.
|
||||
| Activate the :doc:`Developer mode </applications/general/developer_mode/activate>` and open Studio.
|
||||
| Select the necessary field and, under *Properties*, click on *More* to write your tooltip message
|
||||
on *Field Help*. The tooltip message is the explanatory message shown when the user hovers the
|
||||
field. The message here written is displayed on all views forms where the field is added.
|
||||
|
@ -68,5 +68,5 @@ Credits`; or go to :menuselection:`Settings --> In-App Purchases --> View my Ser
|
||||
If you are on Odoo Online (SAAS) and have the Enterprise version, you benefit from free trial credits to test the feature.
|
||||
|
||||
.. seealso::
|
||||
* :doc:`In-App Purchases (IAP) <../../../general/in_app_purchase/in_app_purchase>`
|
||||
* :doc:`In-App Purchases (IAP) </applications/general/in_app_purchase/in_app_purchase>`
|
||||
|
||||
|
@ -122,8 +122,8 @@ If everything is correct, validate the session and post the closing entries.
|
||||
.. tip::
|
||||
To connect the PoS hardware with an Odoo IoT Box, please refer to these
|
||||
docs: :doc:`Connect an IoT Box to your database
|
||||
<../../../productivity/iot/config/connect>` and :doc:`Use the IoT Box for the PoS
|
||||
<../../../productivity/iot/config/pos>`.
|
||||
</applications/productivity/iot/config/connect>` and :doc:`Use the IoT Box for the PoS
|
||||
</applications/productivity/iot/config/pos>`.
|
||||
|
||||
View your statistics
|
||||
====================
|
||||
|
@ -16,7 +16,7 @@ Connect an IoT Box
|
||||
|
||||
Connecting an Ingenico Payment Terminal to Odoo is a feature that
|
||||
requires an IoT Box. For more information on how to connect an IoT Box
|
||||
to your database, please refer to the :doc:`IoT documentation <../../../productivity/iot/config/connect>`.
|
||||
to your database, please refer to the :doc:`IoT documentation </applications/productivity/iot/config/connect>`.
|
||||
|
||||
Configure the Lane/5000 for Ingenico BENELUX
|
||||
--------------------------------------------
|
||||
|
@ -19,14 +19,14 @@ Seller Central and notify the customer.
|
||||
|
||||
.. note::
|
||||
To force the synchronization of an order whose status has not changed since the last
|
||||
synchronization, activate the :doc:`Developer mode <../../../../applications/general/developer_mode>`,
|
||||
synchronization, activate the :doc:`Developer mode </applications/general/developer_mode>`,
|
||||
navigate to your Amazon account and modify the date under
|
||||
:menuselection:`Orders Follow-up --> Last Order Sync`. Pick a date anterior to the last status
|
||||
change of the order that you wish to synchronize and save.
|
||||
|
||||
.. tip::
|
||||
To synchronize immediately the orders of your Amazon account switch to
|
||||
:doc:`Developer mode <../../../../applications/general/developer_mode>`, head to your Amazon account and click on
|
||||
:doc:`Developer mode </applications/general/developer_mode>`, head to your Amazon account and click on
|
||||
**SYNC ORDERS**. The same can be done with order cancellations and pickings by clicking
|
||||
on **SYNC CANCELLATIONS** and **SYNC PICKINGS**.
|
||||
|
||||
|
@ -98,7 +98,7 @@ code, a default database product **Amazon Sale** is used. The same is done with
|
||||
|
||||
.. note::
|
||||
To modify the default products, activate the
|
||||
:doc:`Developer mode <../../../../applications/general/developer_mode>` and navigate to
|
||||
:doc:`Developer mode </applications/general/developer_mode>` and navigate to
|
||||
:menuselection:`Sales --> Configuration --> Settings --> Connectors --> Amazon Sync -->
|
||||
Default Products`.
|
||||
|
||||
@ -131,7 +131,7 @@ marketplaces.
|
||||
must belong to the same region as that of your seller account.
|
||||
|
||||
To add a new marketplace, you must first enable :doc:`Developer mode
|
||||
<../../../../applications/general/developer_mode>`.
|
||||
</applications/general/developer_mode>`.
|
||||
|
||||
Once that is done, go to :menuselection:`Sales --> Configuration --> Settings --> Connectors -->
|
||||
Amazon Sync --> Amazon Marketplaces`.
|
||||
|
@ -32,7 +32,7 @@ you can proceed to the next step.
|
||||
|
||||
If you use Odoo with an on-premise setup or through a partner, then you must update
|
||||
your installation as detailed in
|
||||
`this documentation page <https://www.odoo.com/documentation/13.0/setup/update.html>`_
|
||||
:doc:`this documentation page </administration/update>`
|
||||
or by contacting your integrating partner.
|
||||
|
||||
Update the list of available modules
|
||||
@ -41,7 +41,7 @@ Update the list of available modules
|
||||
New modules must be *discovered* by your Odoo instance to be available in the **Apps**
|
||||
menu.
|
||||
|
||||
To do so, activate the :doc:`Developer Mode <../../../../../applications/general/developer_mode>`, and go to
|
||||
To do so, activate the :doc:`Developer Mode </applications/general/developer_mode>`, and go to
|
||||
:menuselection:`Apps --> Update Apps List`. A wizard will ask for confirmation.
|
||||
|
||||
Install the Amazon/Authentication Patch
|
||||
@ -51,7 +51,7 @@ Install the Amazon/Authentication Patch
|
||||
You should never install new modules in your production database without testing
|
||||
them in a duplicate or staging environment. For Odoo.com customers, a duplicate database
|
||||
can be created from the database management page as explained in
|
||||
:doc:`this documentation page <../../../../administration/db_management/db_online>`. For
|
||||
:doc:`this documentation page </administration/db_management/db_online>`. For
|
||||
Odoo.sh users, you should use a staging or duplicate database. For on-premise users,
|
||||
you should use a staging environment - you should contact your integrating partner for
|
||||
more information regarding how to test a new module in your particular setup.
|
||||
|
@ -48,7 +48,7 @@ parallel in existing installations.
|
||||
|
||||
To switch to the new synchronization mechanism:
|
||||
|
||||
#. Enable the :doc:`Developer mode <../../../../applications/general/developer_mode>`.
|
||||
#. Enable the :doc:`Developer mode </applications/general/developer_mode>`.
|
||||
#. Go to :menuselection:`Settings --> Technical --> Scheduled Actions`
|
||||
#. Archive the old synchronization actions (both are named *Ebay: update product status*)
|
||||
#. Activate the new synchronization actions (*Ebay: get new orders* which runs every 15min by default and *Ebay: synchronise stock (for 'get new orders' synchronisation)* which runs once a day per default)
|
||||
|
@ -138,4 +138,4 @@ In case of discount, you can show the public price and the computed discount % o
|
||||
.. seealso::
|
||||
|
||||
* :doc:`currencies`
|
||||
* :doc:`../../../../websites/ecommerce/maximizing_revenue/pricing`
|
||||
* :doc:`/applications/websites/ecommerce/maximizing_revenue/pricing`
|
||||
|
@ -221,5 +221,5 @@ When you have entered all the extra values, click on **Save**.
|
||||
|
||||
.. seealso::
|
||||
- `Accounting Memento: Details of Journal Entries
|
||||
<../../../accounting/overview/main_concepts/memento.html#journal-entries>`_
|
||||
- :doc:`../../../../finance/accounting/overview/process_overview/supplier_bill`
|
||||
</applications/finance/accounting/overview/main_concepts/memento.html#journal-entries>`_
|
||||
- :doc:`/applications/finance/accounting/overview/process_overview/supplier_bill`
|
||||
|
@ -1,12 +1,12 @@
|
||||
=================
|
||||
=========
|
||||
Set taxes
|
||||
=================
|
||||
=========
|
||||
|
||||
.. toctree::
|
||||
:titlesonly:
|
||||
|
||||
../../../finance/accounting/taxation/taxes/default_taxes
|
||||
../../../finance/accounting/taxation/taxes/fiscal_positions
|
||||
../../../finance/accounting/taxation/taxes/taxes
|
||||
../../../finance/accounting/taxation/taxes/taxcloud
|
||||
../../../finance/accounting/taxation/taxes/B2B_B2C
|
||||
/applications/finance/accounting/taxation/taxes/default_taxes
|
||||
/applications/finance/accounting/taxation/taxes/fiscal_positions
|
||||
/applications/finance/accounting/taxation/taxes/taxes
|
||||
/applications/finance/accounting/taxation/taxes/taxcloud
|
||||
/applications/finance/accounting/taxation/taxes/B2B_B2C
|
||||
|
@ -22,9 +22,9 @@ feature.
|
||||
There, you will have direct access to the **Payment Acquirers** page. It will allow you to select
|
||||
and configure your acquirers of choice. Before creating or modifying a payment acquirer, be sure to
|
||||
check out our documentation about how to be paid with payment acquirers such as
|
||||
:doc:`../../../general/payment_acquirers/paypal`,
|
||||
:doc:`../../../general/payment_acquirers/authorize`, and others in the
|
||||
:doc:`../../../general/payment_acquirers` documentation.
|
||||
:doc:`/applications/general/payment_acquirers/paypal`,
|
||||
:doc:`/applications/general/payment_acquirers/authorize`, and others in the
|
||||
:doc:`/applications/general/payment_acquirers` documentation.
|
||||
|
||||
.. note::
|
||||
If you are familiar with this documentation: :doc:`quote_template`; you
|
||||
@ -48,8 +48,8 @@ possibilities to make their online payments. For example:
|
||||
|
||||
.. seealso::
|
||||
- :doc:`quote_template`
|
||||
- :doc:`../../../general/payment_acquirers`
|
||||
- :doc:`../../../general/payment_acquirers/paypal`
|
||||
- :doc:`../../../general/payment_acquirers/authorize`
|
||||
- :doc:`/applications/general/payment_acquirers`
|
||||
- :doc:`/applications/general/payment_acquirers/paypal`
|
||||
- :doc:`/applications/general/payment_acquirers/authorize`
|
||||
|
||||
|
||||
|
@ -57,4 +57,4 @@ Convenient feature as it allows accountants to easily access all finished tasks
|
||||
:alt: Invoice Task in Odoo Field Service
|
||||
|
||||
.. seealso::
|
||||
* :doc:`../../../services/project/advanced/feedback`
|
||||
* :doc:`/applications/services/project/advanced/feedback`
|
||||
|
@ -39,4 +39,4 @@ person he can be assigned.
|
||||
Create projects per team, or per working site, and have a more accurate and dynamic database.
|
||||
|
||||
.. seealso::
|
||||
* :doc:`../../../services/project/overview/setup`
|
||||
* :doc:`/applications/services/project/overview/setup`
|
||||
|
@ -66,4 +66,4 @@ same way as if you were on the *Field Service* application.
|
||||
.. seealso::
|
||||
- :doc:`../../fsm/overview/invoicing_time`
|
||||
- `Coupons <https://www.odoo.com/slides/slide/coupon-programs-640?fullscreen=1>`_
|
||||
- :doc:`../../../inventory_and_mrp/manufacturing/repair/repair`
|
||||
- :doc:`/applications/inventory_and_mrp/manufacturing/repair/repair`
|
||||
|
@ -61,4 +61,4 @@ or use the stage.
|
||||
:alt: View of a team’s kanban view in Odoo Helpdesk
|
||||
|
||||
.. seealso::
|
||||
- :doc:`../../../general/odoo_basics/users`
|
||||
- :doc:`/applications/general/odoo_basics/users`
|
||||
|
@ -32,7 +32,7 @@ customer.
|
||||
:align: center
|
||||
:alt: View of a standard helpdesk customer review email template for Odoo Helpdesk
|
||||
|
||||
Ratings can be seen on the :doc:`chatter <../../../services/project/tasks/collaborate>` of each ticket, under
|
||||
Ratings can be seen on the :doc:`chatter </applications/services/project/tasks/collaborate>` of each ticket, under
|
||||
the *See Customer Satisfaction* link on the main dashboard, and through *Reporting*.
|
||||
|
||||
Ratings visible on the customer portal
|
||||
|
@ -58,7 +58,7 @@ Live Chat
|
||||
| Through live interactions with your website visitors, helpdesk tickets can be instantly created
|
||||
and redirected to the right person.
|
||||
| Click on your helpdesk team's name - for the example below: *Customer Care* -
|
||||
and :doc:`set up your channel <../../../websites/livechat/overview/get_started>`.
|
||||
and :doc:`set up your channel </applications/websites/livechat/overview/get_started>`.
|
||||
|
||||
.. image:: media/live_chat.png
|
||||
:align: center
|
||||
@ -66,7 +66,7 @@ Live Chat
|
||||
in Odoo Helpdesk
|
||||
|
||||
Now, your operators can create tickets by using the
|
||||
:doc:`command <../../../websites/livechat/overview/responses>` */helpdesk (subject_of_ticket)*.
|
||||
:doc:`command </applications/websites/livechat/overview/responses>` */helpdesk (subject_of_ticket)*.
|
||||
|
||||
Prioritize tickets
|
||||
==================
|
||||
@ -86,4 +86,4 @@ the Kanban view.
|
||||
.. seealso::
|
||||
- :doc:`sla`
|
||||
- :doc:`../advanced/close_tickets`
|
||||
- :doc:`../../../productivity/discuss/advanced/email_servers`
|
||||
- :doc:`/applications/productivity/discuss/advanced/email_servers`
|
||||
|
@ -109,4 +109,4 @@ order.
|
||||
|
||||
.. seealso::
|
||||
- :doc:`reinvoice_from_project`
|
||||
- :doc:`../../../inventory_and_mrp/inventory/management/products/uom`
|
||||
- :doc:`/applications/inventory_and_mrp/inventory/management/products/uom`
|
||||
|
@ -28,7 +28,7 @@ of re-planning it.
|
||||
|
||||
.. note::
|
||||
Repeated shifts are generated for the next six months. A modification is possible in
|
||||
:doc:`Developer mode <../../../../applications/general/developer_mode>`, from *Settings*.
|
||||
:doc:`Developer mode </applications/general/developer_mode>`, from *Settings*.
|
||||
|
||||
.. image:: media/rate_shift_generation.png
|
||||
:align: center
|
||||
|
@ -100,7 +100,7 @@ Share stages across projects
|
||||
|
||||
| In order to have a clean Kanban view that works across projects, and to avoid duplicates,
|
||||
delineate specific stages for different projects.
|
||||
| :doc:`Activate the Developer mode <../../../../applications/general/developer_mode>` then go to
|
||||
| :doc:`Activate the Developer mode </applications/general/developer_mode>` then go to
|
||||
:menuselection:`Project --> Configuration --> Stages`. Choose the respective one and add
|
||||
the projects among which you would like to share stages.
|
||||
|
||||
|
@ -29,7 +29,7 @@ by people according to the billable hours recorded, and even a timesheet table.
|
||||
If you do not have the Timesheets application installed
|
||||
-------------------------------------------------------
|
||||
|
||||
| Activate the :doc:`Developer mode <../../../../applications/general/developer_mode>`. Then go to
|
||||
| Activate the :doc:`Developer mode </applications/general/developer_mode>`. Then go to
|
||||
*Manager Users* and enable *Analytic Accounting*. Now, go to :menuselection:`Project -->
|
||||
Configuration --> Projects` and specify an *Analytic Account* under the needed project.
|
||||
| A *Profitability* menu to the costs and revenues of this analytic account is directly available
|
||||
@ -51,6 +51,6 @@ or do your analysis through a pivot view.
|
||||
:alt: Overview of the reporting page showing costs and revenues in Odoo Project
|
||||
|
||||
.. seealso::
|
||||
- :doc:`../../../finance/accounting/others/analytic/usage`
|
||||
- :doc:`../../../finance/accounting/others/analytic/timesheets`
|
||||
- :doc:`../../../finance/accounting/others/analytic/purchases_expenses`
|
||||
- :doc:`/applications/finance/accounting/others/analytic/usage`
|
||||
- :doc:`/applications/finance/accounting/others/analytic/timesheets`
|
||||
- :doc:`/applications/finance/accounting/others/analytic/purchases_expenses`
|
||||
|
@ -67,5 +67,5 @@ Once the task is complete, click on *Sales Order* and *Create Invoice*.
|
||||
Settings`, and enable *Approved timesheets only*.
|
||||
|
||||
.. seealso::
|
||||
- :doc:`../overview/setup`
|
||||
- :doc:`../../../sales/sales/invoicing/subscriptions`
|
||||
* :doc:`../overview/setup`
|
||||
* :doc:`/applications/sales/sales/invoicing/subscriptions`
|
||||
|
@ -12,7 +12,7 @@ Set up an incoming email server
|
||||
|
||||
| On the *Settings* application, enable *External Email Servers* and define the incoming email
|
||||
alias you would like to use.
|
||||
| **For more information**: :doc:`../../../productivity/discuss/advanced/email_servers`
|
||||
| **For more information**: :doc:`/applications/productivity/discuss/advanced/email_servers`
|
||||
|
||||
Configure the email alias in your project
|
||||
-----------------------------------------
|
||||
|
@ -80,7 +80,7 @@ Drag and drop tasks to change their stage and define colors to help you identify
|
||||
:alt: Choose a color to identify your task in Odoo Project
|
||||
|
||||
.. seealso::
|
||||
- :doc:`../../../general/tags/take_tags`
|
||||
- :doc:`/applications/general/tags/take_tags`
|
||||
|
||||
|
||||
|
||||
|
@ -6,7 +6,7 @@ Odoo automatically timesheets on project/tasks upon time off requests. This allo
|
||||
overall control over the validation of timesheets, as it does not leave place for forgetfulness
|
||||
and questions after hours that have not been timesheeted by the employee.
|
||||
|
||||
Activate the :doc:`Developer mode <../../../../applications/general/developer_mode>`, go to *Timesheets*,
|
||||
Activate the :doc:`Developer mode </applications/general/developer_mode>`, go to *Timesheets*,
|
||||
and change the *Project* and *Task* set by default, if you like.
|
||||
|
||||
.. image:: media/record_time_off.png
|
||||
|
@ -24,7 +24,7 @@ See how to configure your products from links here below.
|
||||
.. seealso::
|
||||
|
||||
* :doc:`../managing_products/variants`
|
||||
* :doc:`../../../sales/sales/products_prices/taxes`
|
||||
* :doc:`/applications/sales/sales/products_prices/taxes`
|
||||
* :doc:`../managing_products/stock`
|
||||
* :doc:`../maximizing_revenue/cross_selling`
|
||||
* :doc:`../maximizing_revenue/reviews`
|
||||
|
@ -9,7 +9,7 @@ This section sheds light on pricing features found in the eCommerce app:
|
||||
* let the customer choose the currency.
|
||||
|
||||
As a pre-requisite, check out how to managing product pricing:
|
||||
:doc:`../../../sales/sales/products_prices/prices/pricing`).
|
||||
:doc:`/applications/sales/sales/products_prices/prices/pricing`).
|
||||
|
||||
Geo-IP automatically applies the right price
|
||||
============================================
|
||||
@ -32,6 +32,6 @@ can be found in *Pricelists* under the *Products* menu, located in the Website a
|
||||
|
||||
.. seealso::
|
||||
|
||||
* :doc:`../../../sales/sales/products_prices/prices/pricing`
|
||||
* :doc:`../../../sales/sales/products_prices/prices/currencies`
|
||||
* :doc:`/applications/sales/sales/products_prices/prices/pricing`
|
||||
* :doc:`/applications/sales/sales/products_prices/prices/currencies`
|
||||
* :doc:`promo_code`
|
||||
|
@ -56,7 +56,7 @@ orders straight on.
|
||||
Select your **bank account** if you get paid immediately on your bank account. If you don't you
|
||||
can create a specific journal for the payment acquirer (type = Bank). That way, you can track
|
||||
online payments in an intermediary account of your books until you get paid into your bank
|
||||
account (see :doc:`../../../general/payment_acquirers/payment_acquirers`).
|
||||
account (see :doc:`/applications/general/payment_acquirers/payment_acquirers`).
|
||||
|
||||
|
||||
Capture the payment after the delivery
|
||||
|
@ -52,5 +52,5 @@ clicks.
|
||||
get access to the *Link Tracker* module and its back-end functionalities.
|
||||
#. Integrated with :doc:`Google Analytics <google_analytics>`, those trackers allow you to see
|
||||
the number of clicks and visitors to keep you on top of your marketing campaigns.
|
||||
#. The integration with the :doc:`CRM <../../../sales/crm/track_leads/prospect_visits>` application allows
|
||||
you to understand where your leads and opportunities are coming from.
|
||||
#. The integration with the :doc:`CRM </applications/sales/crm/track_leads/prospect_visits>` application allows
|
||||
you to understand where your leads and opportunities are coming from.
|
||||
|
@ -480,7 +480,7 @@ page. As these files are shared across all pages, further clicks by the
|
||||
same visitor will not load any other Javascript resource.
|
||||
|
||||
.. note::
|
||||
If you work on :doc:`Developer mode <../../../../applications/general/developer_mode>`, the CSS and
|
||||
If you work on :doc:`Developer mode </applications/general/developer_mode>`, the CSS and
|
||||
Javascript are neither concatenated, nor minified. Thus, it's much slower. But it allows you to
|
||||
easily debug with the Chrome debugger as CSS and Javascript resources are not transformed from
|
||||
their original versions.
|
||||
@ -639,6 +639,6 @@ and there is no other indexing rule than specified in the sitemap
|
||||
to be found at following address.
|
||||
|
||||
You can customize the file *robots* in
|
||||
:doc:`Developer mode <../../../../applications/general/developer_mode>` from *Settings --> Technical -->
|
||||
:doc:`Developer mode </applications/general/developer_mode>` from *Settings --> Technical -->
|
||||
User Interface --> Views* (exclude robots, exclude some pages, redirect to a custom Sitemap).
|
||||
Make the Model Data of the view *Non Updatable* to not reset the file after system upgrades.
|
||||
|
@ -2,14 +2,14 @@
|
||||
How to use my own domain name
|
||||
=============================
|
||||
|
||||
By default, your Odoo Online instance and website have a *.odoo.com* domain name,
|
||||
for both the URL and the emails.
|
||||
By default, your Odoo Online instance and website have a *.odoo.com* domain name,
|
||||
for both the URL and the emails.
|
||||
But you can change to a custom one (e.g. www.yourcompany.com).
|
||||
|
||||
What is a good domain name
|
||||
==========================
|
||||
Your website address is as important to your branding as the name of your
|
||||
business or organization, so put some thought into changing it for a proper
|
||||
Your website address is as important to your branding as the name of your
|
||||
business or organization, so put some thought into changing it for a proper
|
||||
domain. Here are some tips:
|
||||
|
||||
- Simple and obvious
|
||||
@ -24,18 +24,18 @@ How to buy a domain name
|
||||
========================
|
||||
Buy your domain name at a popular registrar:
|
||||
|
||||
- `GoDaddy <https://www.godaddy.com>`__
|
||||
- `Namecheap <https://www.namecheap.com>`__
|
||||
- `OVH <https://www.ovh.com>`__
|
||||
- `GoDaddy <https://www.godaddy.com>`__
|
||||
- `Namecheap <https://www.namecheap.com>`__
|
||||
- `OVH <https://www.ovh.com>`__
|
||||
|
||||
.. note:: Steps to buy a domain name are pretty much straight forward.
|
||||
.. note:: Steps to buy a domain name are pretty much straight forward.
|
||||
In case of issue, check out those easy tutorials:
|
||||
|
||||
- `GoDaddy <https://roadtoblogging.com/buy-domain-name-from-godaddy>`__
|
||||
- `Namecheap <https://www.loudtips.com/buy-domain-name-hosting-namecheap//>`__
|
||||
|
||||
Feel free to buy an email server to have email addresses using your domain name.
|
||||
However don't buy any extra service to create or host your website.
|
||||
However don't buy any extra service to create or host your website.
|
||||
This is Odoo's job!
|
||||
|
||||
.. _custom_domain:
|
||||
@ -60,7 +60,7 @@ First let's authorize the redirection (yourcompany.com -> yourcompany.odoo.com):
|
||||
.. image:: media/domain_name03.png
|
||||
:align: center
|
||||
|
||||
* A database domain prompt will appear. Enter your custom domain
|
||||
* A database domain prompt will appear. Enter your custom domain
|
||||
(e.g. www.yourcompany.com).
|
||||
|
||||
|
||||
@ -72,7 +72,7 @@ We can now apply the redirection from your domain name's manager account:
|
||||
* Log in to your account and search for the DNS Zones management page.
|
||||
|
||||
* Create a CNAME record *www.yourdomain.com* pointing to *mywebsite.odoo.com*.
|
||||
If you want to use the naked domain (e.g. yourdomain.com), you need to redirect
|
||||
If you want to use the naked domain (e.g. yourdomain.com), you need to redirect
|
||||
*yourdomain.com* to *www.yourdomain.com*.
|
||||
|
||||
.. note:: Here are some specific guidelines to create a CNAME record:
|
||||
@ -100,7 +100,7 @@ How to make sure that all my URLs use my custom domain?
|
||||
|
||||
To set up the root URL of your website and of all the links sent in emails, you can ask an administrator of your database (any user in the *Settings* group) to perform a login from the login screen. It's as simple as that!
|
||||
|
||||
If you want to do it manually, you can go to :menuselection:`Settings --> Technical --> System Parameters` .
|
||||
If you want to do it manually, you can go to :menuselection:`Settings --> Technical --> System Parameters` .
|
||||
Find the entry called ``web.base.url`` (you can create it if it does not exist) and enter the full URL of your website, like ``https://www.myodoowebsite.com``.
|
||||
|
||||
.. warning::
|
||||
@ -117,4 +117,4 @@ Google indexes your website under both names. This is a limitation of the Odoo c
|
||||
|
||||
.. seealso::
|
||||
|
||||
* :doc:`../../../productivity/discuss/advanced/email_servers`
|
||||
* :doc:`/applications/productivity/discuss/advanced/email_servers`
|
||||
|
@ -33,11 +33,11 @@ Installation
|
||||
./odoo-bin --geoip-db= ~/Downloads/GeoLite2-City.mmdb
|
||||
|
||||
.. seealso::
|
||||
- `CLI documentation <https://www.odoo.com/documentation/13.0/reference/cmdline.html>`_.
|
||||
- :doc:`CLI documentation </developer/reference/cmdline>`.
|
||||
|
||||
.. warning::
|
||||
``GeoIP`` Python library can also be used. However this version is discontinued since January
|
||||
2019. See `GeoLite Legacy databases are now discontinued
|
||||
1. See `GeoLite Legacy databases are now discontinued
|
||||
<https://support.maxmind.com/geolite-legacy-discontinuation-notice/>`_
|
||||
|
||||
How To Test GeoIP Geolocation In Your Odoo Website
|
||||
@ -59,11 +59,6 @@ You should end up with a dictionary indicating the location of the IP address.
|
||||
If the curly braces are empty ``{}``, it can be for any of the following reasons :
|
||||
|
||||
- The browsing IP address is the localhost (``127.0.0.1``) or a local area network one (``192.168.*.*``)
|
||||
- If a reversed proxy is used, make sure to configure it correctly. See `--proxy-mode <https://www.odoo.com/documentation/13.0/reference/cmdline.html#cmdoption-odoo-bin-proxy-mode>`__
|
||||
- If a reversed proxy is used, make sure to configure it correctly. See :option:`proxy mode <odoo-bin --proxy-mode>`
|
||||
- ``geoip2`` is not installed or the GeoIP database file wasn't found
|
||||
- The GeoIP database was unable to resolve the given IP address
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
@ -103,6 +103,8 @@ Odoo server.
|
||||
|
||||
.. _unittest documentation: https://docs.python.org/3/library/unittest.html
|
||||
|
||||
.. _developer/reference/testing/selection:
|
||||
|
||||
Test selection
|
||||
--------------
|
||||
|
||||
|
@ -290,7 +290,9 @@ Adding a new fiscal position to my Chart of Accounts
|
||||
####################################################
|
||||
|
||||
.. note::
|
||||
If you need more information about what is a fiscal position and how it works in Odoo, please refer to `How to adapt taxes to my customer status or localization <https://www.odoo.com/documentation/user/online/accounting/others/taxes/application.html>`_.
|
||||
|
||||
If you need more information about what is a fiscal position and how it works in Odoo,
|
||||
please refer to :doc:`/applications/finance/accounting/taxation/taxes/fiscal_positions`.
|
||||
|
||||
To create a new fiscal position, simply use the ``account.fiscal.position.template`` model:
|
||||
|
||||
@ -361,7 +363,8 @@ How to create a new bank operation model?
|
||||
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
|
||||
|
||||
.. note::
|
||||
How a bank operation model works exactly in Odoo? See `Configure model of entries <https://www.odoo.com/documentation/user/online/accounting/bank/reconciliation/configure.html>`_.
|
||||
|
||||
How a bank operation model works exactly in Odoo? See :doc:`/applications/finance/accounting/bank/reconciliation/reconciliation_models`.
|
||||
|
||||
Since ``V10``, a new feature is available in the bank statement reconciliation widget: the bank operation model.
|
||||
This allows the user to pre-fill some accounting entries with a single click.
|
||||
|
@ -28,5 +28,5 @@ Here are some resources that might help you:
|
||||
|
||||
- Our `documentation pages <https://www.odoo.com/page/docs>`_.
|
||||
- Ask your question on the `community forum <https://www.odoo.com/forum/help-1>`_.
|
||||
- `Buy Odoo Enterprise <https://www.odoo.com/documentation/13.0/setup/enterprise.html>`_ to get the
|
||||
- :doc:`Buy Odoo Enterprise </administration/enterprise>` to get the
|
||||
support and bugfix services.
|
||||
|
@ -30,6 +30,7 @@ contributing/documentation/guidelines.rst contributing/documentation/rst_guideli
|
||||
|
||||
# Redirections introduced in 12.0 :
|
||||
|
||||
administration/odoo_sh/documentation.rst administration/odoo_sh.rst # moved during doc-apocalypse (#945)
|
||||
support/user_doc.rst contributing/documentation/introduction_guide.rst # removed in forward-port of #544 (b109c3af)
|
||||
|
||||
# Redirections introduced in 13.0 :
|
||||
|
Loading…
Reference in New Issue
Block a user