[MERGE] Forward-port of branch 13.0 to 14.0
This commit is contained in:
Victor Feyens
commit
8ad392222b
7
Makefile
7
Makefile
@ -55,13 +55,10 @@ latexpdf:
|
||||
cp $(BUILD_DIR)/latex/*.pdf $(BUILD_DIR)/html/
|
||||
@echo "Build finished."
|
||||
|
||||
l10n:
|
||||
gettext:
|
||||
@echo "Generating translatable files..."
|
||||
$(SPHINX_BUILD) -c $(CONFIG_DIR) -b gettext $(SOURCE_DIR) $(BUILD_DIR)/gettext
|
||||
$(SPHINX_BUILD) -c $(CONFIG_DIR) -b gettext $(SOURCE_DIR) locale/sources
|
||||
@echo "Generation finished."
|
||||
@echo "Localizing translation strings..."
|
||||
sphinx-intl update -p $(BUILD_DIR)/gettext -l $(L10N_LANGUAGES)
|
||||
@echo "Localization finished."
|
||||
|
||||
extensions/odoo_theme/static/style.css: extensions/odoo_theme/static/style.scss extensions/odoo_theme/static/scss/*.scss
|
||||
@echo "Compiling stylesheets..."
|
||||
|
||||
9
conf.py
9
conf.py
@ -5,6 +5,7 @@ from pathlib import Path
|
||||
|
||||
from pygments.lexers import JsonLexer, XmlLexer
|
||||
from sphinx.util import logging
|
||||
import sphinx
|
||||
|
||||
_logger = logging.getLogger(__name__)
|
||||
|
||||
@ -128,7 +129,13 @@ intersphinx_mapping = {
|
||||
github_user = 'odoo'
|
||||
github_project = 'documentation'
|
||||
|
||||
locale_dirs = ['locale/']
|
||||
locale_dirs = ['../locale/']
|
||||
|
||||
# custom docname_to_domain to devide the translations of applications in subdirectories
|
||||
sphinx.transforms.i18n.docname_to_domain = (
|
||||
sphinx.util.i18n.docname_to_domain
|
||||
) = lambda docname, compact: docname.split('/')[1 if docname.startswith('applications/') else 0]
|
||||
|
||||
supported_languages = {
|
||||
'de': 'Deutsch',
|
||||
'en': 'English',
|
||||
|
||||
@ -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/14.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/14.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/14.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,
|
||||
@ -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/14.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/14.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/14.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.
|
||||
|
||||
|
||||
@ -276,7 +276,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
|
||||
|
||||
@ -2,44 +2,44 @@
|
||||
France
|
||||
======
|
||||
|
||||
FEC
|
||||
FEC
|
||||
===
|
||||
|
||||
If you have installed the French Accounting, you will be able to download the FEC.
|
||||
For this, go in :menuselection:`Accounting --> Reporting --> France --> FEC`.
|
||||
For this, go in :menuselection:`Accounting --> Reporting --> France --> FEC`.
|
||||
|
||||
.. tip::
|
||||
If you do not see the submenu **FEC**, go in **Apps** and search for the module
|
||||
called **France-FEC** and verify if it is well installed.
|
||||
called **France-FEC** and verify if it is well installed.
|
||||
|
||||
French Accounting Reports
|
||||
=========================
|
||||
|
||||
If you have installed the French Accounting, you will have access to some accounting reports specific to France:
|
||||
If you have installed the French Accounting, you will have access to some accounting reports specific to France:
|
||||
|
||||
- Bilan comptable
|
||||
- Compte de résultats
|
||||
- Plan de Taxes France
|
||||
- Plan de Taxes France
|
||||
|
||||
Get the VAT anti-fraud certification with Odoo
|
||||
==============================================
|
||||
|
||||
As of January 1st 2018, a new anti-fraud legislation comes into effect
|
||||
in France and DOM-TOM. This new legislation stipulates certain criteria
|
||||
concerning the inalterability, security, storage and archiving of sales data.
|
||||
These legal requirements are implemented in Odoo, version 9 onward,
|
||||
As of January 1st 2018, a new anti-fraud legislation comes into effect
|
||||
in France and DOM-TOM. This new legislation stipulates certain criteria
|
||||
concerning the inalterability, security, storage and archiving of sales data.
|
||||
These legal requirements are implemented in Odoo, version 9 onward,
|
||||
through a module and a certificate of conformity to download.
|
||||
|
||||
Is my company required to use an anti-fraud software?
|
||||
-----------------------------------------------------
|
||||
|
||||
Your company is required to use an anti-fraud cash register software like
|
||||
Your company is required to use an anti-fraud cash register software like
|
||||
Odoo (CGI art. 286, I. 3° bis) if:
|
||||
|
||||
* You are taxable (not VAT exempt) in France or any DOM-TOM,
|
||||
* Some of your customers are private individuals (B2C).
|
||||
|
||||
This rule applies to any company size. Auto-entrepreneurs are exempted from
|
||||
This rule applies to any company size. Auto-entrepreneurs are exempted from
|
||||
VAT and therefore are not affected.
|
||||
|
||||
Get certified with Odoo
|
||||
@ -47,34 +47,34 @@ Get certified with Odoo
|
||||
|
||||
Getting compliant with Odoo is very easy.
|
||||
|
||||
Your company is requested by the tax administration to deliver a certificate
|
||||
Your company is requested by the tax administration to deliver a certificate
|
||||
of conformity testifying that your software complies with the anti-fraud
|
||||
legislation. This certificate is granted by Odoo SA to Odoo Enterprise users
|
||||
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/14.0/setup/enterprise.html>`_
|
||||
If you use Odoo Community, you should
|
||||
: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.
|
||||
|
||||
To get the certification just follow the following steps:
|
||||
|
||||
* Install the anti-fraud module fitting your Odoo environment from the
|
||||
* Install the anti-fraud module fitting your Odoo environment from the
|
||||
*Apps* menu:
|
||||
|
||||
* if you use Odoo Point of Sale: *l10n_fr_pos_cert*: France - VAT Anti-Fraud Certification for Point of Sale (CGI 286 I-3 bis)
|
||||
* in any other case: *l10n_fr_certification*: France - VAT Anti-Fraud Certification (CGI 286 I-3 bis)
|
||||
|
||||
* Make sure a country is set on your company, otherwise your entries won’t be
|
||||
encrypted for the inalterability check. To edit your company’s data,
|
||||
go to :menuselection:`Settings --> Users & Companies --> Companies`.
|
||||
* Make sure a country is set on your company, otherwise your entries won’t be
|
||||
encrypted for the inalterability check. To edit your company’s data,
|
||||
go to :menuselection:`Settings --> Users & Companies --> Companies`.
|
||||
Select a country from the list; Do not create a new country.
|
||||
* Download the mandatory certificate of conformity delivered by Odoo SA `here <https://www.odoo.com/my/contract/french-certification/>`__.
|
||||
|
||||
.. 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.
|
||||
@ -91,52 +91,52 @@ Anti-fraud features
|
||||
|
||||
The anti-fraud module introduces the following features:
|
||||
|
||||
* **Inalterability**: deactivation of all the ways to cancel or modify
|
||||
* **Inalterability**: deactivation of all the ways to cancel or modify
|
||||
key data of POS orders, invoices and journal entries;
|
||||
* **Security**: chaining algorithm to verify the inalterability;
|
||||
* **Storage**: automatic sales closings with computation of both period
|
||||
* **Storage**: automatic sales closings with computation of both period
|
||||
and cumulative totals (daily, monthly, annually).
|
||||
|
||||
Inalterability
|
||||
~~~~~~~~~~~~~~
|
||||
|
||||
All the possible ways to cancel and modify key data of paid POS orders,
|
||||
confirmed invoices and journal entries are deactivated,
|
||||
if the company is located in France or in any DOM-TOM.
|
||||
All the possible ways to cancel and modify key data of paid POS orders,
|
||||
confirmed invoices and journal entries are deactivated,
|
||||
if the company is located in France or in any DOM-TOM.
|
||||
|
||||
.. note:: If you run a multi-companies environment, only the documents of
|
||||
.. note:: If you run a multi-companies environment, only the documents of
|
||||
such companies are impacted.
|
||||
|
||||
Security
|
||||
~~~~~~~~
|
||||
|
||||
To ensure the inalterability, every order or journal entry is encrypted
|
||||
upon validation.
|
||||
This number (or hash) is calculated from the key data of the document as
|
||||
To ensure the inalterability, every order or journal entry is encrypted
|
||||
upon validation.
|
||||
This number (or hash) is calculated from the key data of the document as
|
||||
well as from the hash of the precedent documents.
|
||||
|
||||
The module introduces an interface to test the data inalterability.
|
||||
If any information is modified on a document after its validation,
|
||||
the test will fail. The algorithm recomputes all the hashes and compares them
|
||||
against the initial ones. In case of failure, the system points out the first
|
||||
The module introduces an interface to test the data inalterability.
|
||||
If any information is modified on a document after its validation,
|
||||
the test will fail. The algorithm recomputes all the hashes and compares them
|
||||
against the initial ones. In case of failure, the system points out the first
|
||||
corrupted document recorded in the system.
|
||||
|
||||
Users with *Manager* access rights can launch the inalterability check.
|
||||
For POS orders, go to
|
||||
:menuselection:`Point of Sales --> Reporting --> French Statements`.
|
||||
For invoices or journal entries,
|
||||
Users with *Manager* access rights can launch the inalterability check.
|
||||
For POS orders, go to
|
||||
:menuselection:`Point of Sales --> Reporting --> French Statements`.
|
||||
For invoices or journal entries,
|
||||
go to :menuselection:`Invoicing/Accounting --> Reporting --> French Statements`.
|
||||
|
||||
Storage
|
||||
~~~~~~~
|
||||
|
||||
The system also processes automatic sales closings on a daily, monthly
|
||||
The system also processes automatic sales closings on a daily, monthly
|
||||
and annual basis.
|
||||
Such closings distinctly compute the sales total of the period as well as
|
||||
the cumulative grand totals from the very first sales entry recorded
|
||||
Such closings distinctly compute the sales total of the period as well as
|
||||
the cumulative grand totals from the very first sales entry recorded
|
||||
in the system.
|
||||
|
||||
Closings can be found in the *French Statements* menu of Point of Sale,
|
||||
Closings can be found in the *French Statements* menu of Point of Sale,
|
||||
Invoicing and Accounting apps.
|
||||
|
||||
.. note::
|
||||
@ -144,33 +144,33 @@ Invoicing and Accounting apps.
|
||||
|
||||
* For multi-companies environments, such closings are performed by company.
|
||||
|
||||
* POS orders are posted as journal entries at the closing of the POS session.
|
||||
Closing a POS session can be done anytime.
|
||||
To prompt users to do it on a daily basis, the module prevents from resuming
|
||||
a session opened more than 24 hours ago.
|
||||
* POS orders are posted as journal entries at the closing of the POS session.
|
||||
Closing a POS session can be done anytime.
|
||||
To prompt users to do it on a daily basis, the module prevents from resuming
|
||||
a session opened more than 24 hours ago.
|
||||
Such a session must be closed before selling again.
|
||||
|
||||
* A period’s total is computed from all the journal entries posted after the
|
||||
previous closing of the same type, regardless of their posting date.
|
||||
If you record a new sales transaction for a period already closed,
|
||||
* A period’s total is computed from all the journal entries posted after the
|
||||
previous closing of the same type, regardless of their posting date.
|
||||
If you record a new sales transaction for a period already closed,
|
||||
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`.
|
||||
|
||||
|
||||
Responsibilities
|
||||
----------------
|
||||
|
||||
Do not uninstall the module! If you do so, the hashes will be reset and none
|
||||
Do not uninstall the module! If you do so, the hashes will be reset and none
|
||||
of your past data will be longer guaranteed as being inalterable.
|
||||
|
||||
Users remain responsible for their Odoo instance and must use it with
|
||||
due diligence. It is not permitted to modify the source code which guarantees
|
||||
Users remain responsible for their Odoo instance and must use it with
|
||||
due diligence. It is not permitted to modify the source code which guarantees
|
||||
the inalterability of data.
|
||||
|
||||
Odoo absolves itself of all and any responsibility in case of changes
|
||||
|
||||
Odoo absolves itself of all and any responsibility in case of changes
|
||||
in the module’s functions caused by 3rd party applications not certified by Odoo.
|
||||
|
||||
|
||||
|
||||
@ -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
|
||||
|
||||
@ -469,7 +469,7 @@ Landed Costs`. There you will find the option to attach the Pedimentos number.
|
||||
with the transfer(s).
|
||||
|
||||
.. seealso::
|
||||
:doc:`../../../../inventory_and_mrp/inventory/management/reporting/integrating_landed_costs`.
|
||||
:doc:`/applications/inventory_and_mrp/inventory/management/reporting/integrating_landed_costs`.
|
||||
|
||||
Payment Terms
|
||||
~~~~~~~~~~~~~
|
||||
@ -1333,7 +1333,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 <../../../../general/developer_mode/activate>` 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,12 +24,12 @@ 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
|
||||
:align: center
|
||||
|
||||
|
||||
IAP Portal
|
||||
==========
|
||||
|
||||
@ -62,10 +62,10 @@ Different services are available depending on the hosting type of your Database:
|
||||
- *Odoo.sh and Odoo Enterprise (on-premise)*: both the services provided by Odoo and by third-party
|
||||
apps can be used.
|
||||
|
||||
Offering my own services
|
||||
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/14.0/webservices/iap.html>`_
|
||||
initial purchase. Please, find more information at: :doc:`In-App Purchase
|
||||
</developer/webservices/iap>`.
|
||||
|
||||
@ -127,5 +127,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/14.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/14.0/howtos/company.html>`_ documentation.
|
||||
to :doc:`this </developer/howtos/company>` documentation.
|
||||
|
||||
.. image:: users/multi-companies.png
|
||||
:align: center
|
||||
@ -203,4 +203,4 @@ the user can have access.
|
||||
|
||||
.. seealso::
|
||||
- :doc:`../multi_companies/manage_multi_companies`
|
||||
- :doc:`../../settings/users_and_features`
|
||||
- :doc:`../../settings/users_and_features`
|
||||
|
||||
@ -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
|
||||
|
||||
@ -38,7 +38,7 @@ The principles are the following:
|
||||
correspond to the quality requirements agreed with the
|
||||
suppliers. Adding a quality control step in the goods receipt
|
||||
process can become essential.
|
||||
|
||||
|
||||
You receive the goods in an input area, then transfer them into
|
||||
quality area for quality control. When your quality check
|
||||
process finishes then you can move the goods from QC to stock.
|
||||
@ -66,4 +66,4 @@ Please read documentation on :doc:`three_steps`
|
||||
|
||||
.. seealso::
|
||||
- :doc:`../delivery/inventory_flow`
|
||||
- :doc:`../../../purchase/advanced/analyze`
|
||||
- :doc:`/applications/inventory_and_mrp/purchase/advanced/analyze`
|
||||
|
||||
@ -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
|
||||
|
||||
@ -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`.
|
||||
|
||||
|
||||
|
||||
@ -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::
|
||||
|
||||
@ -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*
|
||||
|
||||
@ -50,7 +50,7 @@ For every Trigger option, **conditions** can be applied, such as:
|
||||
- *Send Email*: an automatic :doc:`email <../../discuss/advanced/email_template>` is sent.
|
||||
- *Add Followers*: followers 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
|
||||
--------------------------------------------
|
||||
|
||||
@ -17,14 +17,14 @@ order is automatically canceled in Odoo.
|
||||
|
||||
.. 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
|
||||
:doc:`Developer mode </applications/general/developer_mode>`, head to your Amazon account and
|
||||
click on **SYNC ORDERS**. The same can be done with pickings by clicking on **SYNC PICKINGS**.
|
||||
|
||||
Manage deliveries in FBM
|
||||
|
||||
@ -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`.
|
||||
|
||||
@ -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`
|
||||
|
||||
|
||||
|
||||
@ -64,4 +64,4 @@ same way as if you were on the *Field Service* application.
|
||||
:height: 300
|
||||
|
||||
.. seealso::
|
||||
- `Coupons <https://www.odoo.com/slides/slide/coupon-programs-640?fullscreen=1>`_
|
||||
- `Coupons <https://www.odoo.com/slides/slide/coupon-programs-640?fullscreen=1>`_
|
||||
|
||||
@ -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`
|
||||
|
||||
@ -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`
|
||||
|
||||
@ -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
|
||||
-----------------------------------------
|
||||
|
||||
@ -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:`../maximizing_revenue/cross_selling`
|
||||
* :doc:`../maximizing_revenue/reviews`
|
||||
* :doc:`../maximizing_revenue/pricing`
|
||||
|
||||
@ -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`
|
||||
|
||||
@ -52,5 +52,5 @@ country of origin for those 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/14.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/14.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
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
@ -108,6 +108,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/14.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