[IMP] manufacturing: add missing word in flexible_components_consumption

X-original-commit: 7b5de904aa

.github/CODEOWNERS

@@ -1,11 +0,0 @@
-# All changes to technical files (build environment and Sphinx extensions) have to be approved
-/extensions/         @odoo/doc-review
-.gitignore           @odoo/doc-review
-commit_template.txt  @odoo/doc-review
-conf.py              @odoo/doc-review
-Makefile             @odoo/doc-review
-requirements.txt     @odoo/doc-review
-
-# All changes to legal material have to be approved
-/content/legal/     @odoo/legal
-/content/legal.rst  @odoo/legal

.gitignore

@@ -4,7 +4,6 @@
 
 # Sphinx build files
 _build/
-extensions/odoo_theme/static/style.css
 
 # Dependencies
 odoo

Makefile

@@ -9,6 +9,10 @@ ifndef BUILD_DIR
   BUILD_DIR    = _build
 endif
 
+ifndef CURRENT_LANG
+  CURRENT_LANG = en
+endif
+
 SPHINX_BUILD   = sphinx-build
 CONFIG_DIR     = .
 SPHINXOPTS     = -D project_root=$(ROOT) -D canonical_version=$(CANONICAL_VERSION) \
@@ -18,7 +22,6 @@ SPHINXOPTS     = -D project_root=$(ROOT) -D canonical_version=$(CANONICAL_VERSIO
 				 -j $(WORKERS)
 SOURCE_DIR     = content
 
-
 HTML_BUILD_DIR = $(BUILD_DIR)/html
 ifdef VERSIONS
   HTML_BUILD_DIR := $(HTML_BUILD_DIR)/14.0
@@ -43,7 +46,7 @@ clean:
 	rm -rf $(BUILD_DIR)/*
 	@echo "Cleaning finished."
 
-html: $(BUILD_DIR)/html/_static/style.css
+html: $(HTML_BUILD_DIR)/_static/style.css
 	@echo "Starting build..."
 	$(SPHINX_BUILD) -c $(CONFIG_DIR) -b html $(SPHINXOPTS) $(SOURCE_DIR) $(HTML_BUILD_DIR)
 	@echo "Build finished."
@@ -63,10 +66,10 @@ gettext:
 	$(SPHINX_BUILD) -c $(CONFIG_DIR) -b gettext $(SOURCE_DIR) locale/sources
 	@echo "Generation finished."
 
-$(BUILD_DIR)/html/_static/style.css: extensions/odoo_theme/static/style.scss extensions/odoo_theme/static/scss/*.scss
+$(HTML_BUILD_DIR)/_static/style.css: extensions/odoo_theme/static/style.scss extensions/odoo_theme/static/scss/*.scss
 	@echo "Compiling stylesheets..."
-	mkdir -p $(BUILD_DIR)/html/_static
-	pysassc extensions/odoo_theme/static/style.scss $(BUILD_DIR)/html/_static/style.css
+	mkdir -p $(HTML_BUILD_DIR)/_static
+	pysassc extensions/odoo_theme/static/style.scss $(HTML_BUILD_DIR)/_static/style.css
 	@echo "Compilation finished."
 
 #=== Development and debugging rules ===#
@@ -74,6 +77,6 @@ $(BUILD_DIR)/html/_static/style.css: extensions/odoo_theme/static/style.scss ext
 fast: SPHINXOPTS += -A collapse_menu=True
 fast: html
 
-static: $(BUILD_DIR)/static/style.css
-	cp -r extensions/odoo_theme/static/* $(BUILD_DIR)/html/_static/
-	cp -r static/* $(BUILD_DIR)/html/_static/
+static: $(HTML_BUILD_DIR)/static/style.css
+	cp -r extensions/odoo_theme/static/* $(HTML_BUILD_DIR)/_static/
+	cp -r static/* $(HTML_BUILD_DIR)/_static/

README.md

@@ -39,10 +39,6 @@ For contributions to the content of the documentation, please refer to the
 To **report a content issue**, **request new content** or **ask a question**, use the
 [repository's issue tracker](https://github.com/odoo/documentation-user/issues) as usual.
 
-If you have a pull request that is ready for review, request one from the
-[odoo/doc-review](https://github.com/orgs/odoo/teams/doc-review) team.
-
-
 ## Learn More
 
 To learn more about Odoo, in addition to the documentation, have a look at

conf.py

@@ -58,34 +58,40 @@ extension_dir = Path('extensions')
 sys.path.insert(0, str(extension_dir.absolute()))
 
 # Search for the directory of odoo sources to know whether autodoc should be used on the dev doc
-odoo_dir = Path('odoo')
+odoo_sources_candidate_dirs = (Path('odoo'), Path('../odoo'))
+odoo_sources_dirs = [
+    d for d in odoo_sources_candidate_dirs if d.is_dir() and (d / 'odoo-bin').exists()
+]
 odoo_dir_in_path = False
-if not odoo_dir.is_dir():
-    parent_odoo_dir = Path('../odoo')
-    if parent_odoo_dir.is_dir():
-        _logger.info('Using parent dir to find odoo sources')
-        odoo_dir = parent_odoo_dir
-if not odoo_dir.is_dir():
+
+if not odoo_sources_dirs:
     _logger.warning(
-        f"Could not find Odoo sources directory at {odoo_dir.absolute()}.\n"
-        f"The 'Developer' documentation will be built but autodoc directives will be skipped.\n"
-        f"In order to fully build the 'Developer' documentation, clone the repository with "
-        f"`git clone https://github.com/odoo/odoo` or create a symbolink link."
+        "Could not find Odoo sources directory in neither of the following folders:\n"
+        "%(dir_list)s\n"
+        "The 'Developer' documentation will be built but autodoc directives will be skipped.\n"
+        "In order to fully build the 'Developer' documentation, clone the repository with "
+        "`git clone https://github.com/odoo/odoo` or create a symbolic link.",
+        {'dir_list': '\n'.join([f'\t- {d.resolve()}' for d in odoo_sources_candidate_dirs])},
     )
 else:
-    sys.path.insert(0, str(odoo_dir.absolute()))
+    odoo_dir = odoo_sources_dirs[0].resolve()
+    sys.path.insert(0, str(odoo_dir))
     from odoo import release as odoo_release  # Don't collide with Sphinx's 'release' config option
     odoo_version = odoo_release.version if 'alpha' not in odoo_release.version else 'master'
     if release != odoo_version:
         _logger.warning(
-            f"Found Odoo sources directory but with version '{odoo_version}' incompatible with "
-            f"documentation version '{version}'.\n"
-            f"The 'Developer' documentation will be built but autodoc directives will be skipped.\n"
-            f"In order to fully build the 'Developer' documentation, checkout the matching branch"
-            f" with `cd odoo && git checkout {version}`."
+            "Found Odoo sources in %(directory)s but with version '%(odoo_version)s' incompatible "
+            "with documentation version '%(doc_version)s'.\n"
+            "The 'Developer' documentation will be built but autodoc directives will be skipped.\n"
+            "In order to fully build the 'Developer' documentation, checkout the matching branch"
+            " with `cd odoo && git checkout %(doc_version)s`.",
+            {'directory': odoo_dir, 'odoo_version': odoo_version, 'doc_version': version},
         )
     else:
-        _logger.info(f"Found Odoo sources directory matching documentation version {release}.")
+        _logger.info(
+            "Found Odoo sources in %(directory)s matching documentation version '%(version)s'.",
+            {'directory': odoo_dir, 'version': release},
+        )
         odoo_dir_in_path = True
 
 # The Sphinx extensions to use, as module names.
@@ -290,7 +296,7 @@ def _generate_alternate_urls(app, pagename, templatename, context, doctree):
             for _alternate_version in sorted(_alternate_versions, reverse=True)
             if _alternate_version != version and (
                 _alternate_version != 'master' or pagename.startswith('developer')
-            )
+            ) and not _alternate_version.startswith('saas')
         ]
 
     def _localize():

content/administration.rst

@@ -18,4 +18,5 @@ These guides provide instructions on how to install, maintain and upgrade Odoo d
 
     administration/install
     administration/maintain
+    administration/upgrade
     administration/odoo_sh

content/administration/maintain.rst

@@ -7,8 +7,8 @@ Maintain
 .. toctree::
 
     maintain/update
-    maintain/db_upgrade
     maintain/enterprise
     maintain/hosting_changes
-    maintain/db_premise
+    maintain/online
+    maintain/on_premise
     maintain/supported_versions

content/administration/maintain/db_upgrade.rst

@@ -1,413 +0,0 @@
-
-.. |assistance-contact| replace::
-   If you need Odoo assistance on this matter, please contact your Odoo Account Manager or contact
-   our `Sales department`_.
-.. _Sales department: mailto:sales@odoo.com
-
-.. _db-upgrade:
-
-================
-Versions upgrade
-================
-
-.. _db-upgrade/overview:
-
-Overview
-========
-
-.. _db-upgrade/process:
-
-The upgrade process
--------------------
-
-This documentation is for our *On-Premise* (self-hosted) and *Odoo.sh* customers.
-
-.. _db-upgrade/definition:
-
-Definition
-~~~~~~~~~~
-
-An upgrade is switching to a newer version of Odoo (e.g., Odoo 13.0 to Odoo 14.0)
-
-An upgrade does not cover:
-
-* changing :ref:`Editions <db-upgrade/faq/editions-change>` (i.e., Community to Enterprise edition)
-* switching :ref:`hosting type <db-upgrade/faq/hosting-types-switch>` (i.e., On-Premise to Online or
-  Odoo.sh)
-* migration from another ERP to Odoo
-
-.. note:: |assistance-contact|
-
-.. _db-upgrade/process-workflow:
-
-Process workflow
-~~~~~~~~~~~~~~~~
-
-The upgrade process in a nutshell:
-
-#. You create a test upgrade request.
-#. | The request is processed by Odoo:
-   | This happens via an automated process that runs the database through an upgrade script and
-     takes between 20 and 120 minutes. Only if an issue(s) arises will we have to intervene
-     manually and adjust the script specifically to your database until the upgrade succeeds.
-#. Odoo delivers a test database.
-#. You test your database for possible discrepancies (see :ref:`db-upgrade/test-guidance`)
-#. If there are any discrepancies, you report them to the Upgrade support team via the
-   :ref:`Help portal <db-upgrade/test-assistance>`.
-#. We will fix the issues and send you a new test database.
-#. Once you completed the testing and are happy with the result, you decide on a date and time when
-   you stop users from accessing Odoo, freeze all data entries and create an upgrade request for the
-   production upgrade.
-#. Odoo delivers the production database through the automated process.
-#. You restore it in your Production environment a few short hours later and continue working on the
-   newly upgraded database.
-
-.. _db-upgrade/service-level:
-
-Service Level Agreement
------------------------
-
-What is covered by the Enterprise Licence?
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-
-Databases hosted on Odoo’s Cloud platforms (Saas and Odoo.sh) or On-Premise (Self-Hosting) enjoy the
-following service at all times.
-
-The upgrade of:
-
-* standard applications
-* Studio customization (as long as the Studio app is still active)
-* customizations done by our consulting and developer services *if* they are covered by a
-  ‘Maintenance of Customisations’ subscription
-
-The Upgrade Service is limited to the technical conversion and adaptation of your database (standard
-modules and data) to make it compatible with the targeted version.
-
-What upgrading does NOT cover
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-
-* The cleaning of pre-existing data & configuration while upgrading
-* Any new developments and/or upgrade of your own :ref:`custom modules
-  <db-upgrade/faq/custom-modules>`
-* `Training <https://www.odoo.com/learn>`_ on the new version
-
-You can get more information about your Enterprise Licence on our :ref:`Odoo Enterprise Subscription
-Agreement <upgrade>` page.
-
-.. note:: |assistance-contact|
-
-.. _db-upgrade/get-started:
-
-Get started
-===========
-
-The upgrade process varies depending on where your database is hosted.
-
-.. _db-upgrade/online:
-
-Online (SaaS)
--------------
-
-If you are hosted Online, please check your `database manager <https://www.odoo.com/my/databases>`_.
-
-.. _db-upgrade/odoo-sh:
-
-Odoo.sh
--------
-
-If you are Odoo.sh hosted, check our :doc:`specific instructions to be able to upgrade
-<../odoo_sh/advanced/upgrade_your_database>`.
-
-.. _db-upgrade/on-premise:
-
-On-Premise
-----------
-
-There are two possibilities:
-
-#. Via the interface of our `website form <https://upgrade.odoo.com>`_
-#. | For technically-advanced users and partners, via the following command line (to be used on the
-     machine where your database is hosted):
-   | ``python <(curl -s beta.upgrade.odoo.com/upgrade) test -d <your db name> -t 14.0``
-
-What does it do?
-~~~~~~~~~~~~~~~~
-
-The above command will dump your database to a file, then send it to the upgrade platform for
-upgrade, displaying you the live logs, then restore the upgraded database back on your server as a
-duplicate test database.
-
-.. _db-upgrade/steps:
-
-Steps
-=====
-
-.. _db-upgrade/steps-test:
-
-The testing phase
------------------
-
-.. _db-upgrade/test-process:
-
-Test process
-~~~~~~~~~~~~
-
-Also referred to as the pre-production phase, the test phase allows you to review an upgraded
-version of your database without affecting your production database in any way.
-
-We suggest that you run the test upgrade process at least once, but you can do it as often as you
-want (one at a time).
-
-Once you receive your upgraded test database, you should check that all data, processes and
-functionality are still correct and working as expected.
-
-If you do find discrepancies, you'll be able to:
-
-* | :ref:`Report your issues <db-upgrade/test-assistance>`
-  | and/or
-* Ask for a new :ref:`test request <db-upgrade/test-db-request>` after the reported issues have
-  been fixed in the upgrade script.
-
-When you do not find any discrepancies, you'll be able to:
-
-* Move on to the upgrade of your :ref:`production database <db-upgrade/production-live>`.
-
-.. _db-upgrade/test-db-request:
-
-Request a test database
-~~~~~~~~~~~~~~~~~~~~~~~
-
-When filling the `website form <https://upgrade.odoo.com>`_, select *Testing* purpose.
-
-.. image:: media/db-upgrade-test-purpose.png
-   :align: center
-   :alt: Selection of the "Testing" purpose in the upgrade form on Odoo
-
-.. _db-upgrade/test-guidance:
-
-Test guidance
-~~~~~~~~~~~~~
-
-Every business and organization has its own operational needs and will have to test its specific
-Odoo instance respectively. However, we recommend you look at `the test scenario
-<https://drive.google.com/open?id=1Lm4JqbsHBirB1wMi14UChoz_YHLjx5ec>`_ we created, a high-level idea
-of what you should test and look out for.
-
-.. todo:: change link "test scenario" once the related doc is published
-
-.. _db-upgrade/test-assistance:
-
-Assistance
-~~~~~~~~~~
-
-If you encounter issues or problems in the **test database**, please contact the Odoo Upgrade
-Support:
-
-#. Connect to our `Odoo Support page <https://www.odoo.com/help>`_.
-#. Under the *Ticket Description* section, select *An issue related to my upgrade* ticket type.
-
-   .. image:: media/db-upgrade-test-assistance.png
-      :align: center
-      :alt: Selection of "An issue related to my upgrade" as Ticket Type in the support form on Odoo
-
-   .. warning::
-      If you choose another *Ticket Description* type, the request will be redirected to another
-      team than the upgrade one and will slow down the processing and response time.
-
-#. Please provide as much detail as you can. Where applicable, illustrate the current and previous
-   flows with videos and/or screenshots. This will avoid clarifying questions and speed up the
-   resolution process significantly.
-
-   .. image:: media/db-upgrade-test-assistance-details.png
-      :align: center
-      :alt: "Detailed Description" field in the support form on Odoo
-
-.. note::
-   * The purpose of the test phase is not to correct existing data or configurations in your
-     database.
-   * |assistance-contact|
-
-.. _db-upgrade/steps-production:
-
-The production launch
----------------------
-
-.. _db-upgrade/production-live:
-
-Production goes live
-~~~~~~~~~~~~~~~~~~~~
-
-The production upgrade request is when you decide to upgrade your current database with all your
-production data (invoices, VAT returns, inventories, current orders) to a new version of your choice.
-
-After your :ref:`tests <db-upgrade/steps-test>` are completed to your satisfaction, submit the
-request to upgrade your production database via our `website form <https://upgrade.odoo.com>`_.
-Select *Production* purpose.
-
-.. image:: media/db-upgrade-production-purpose.png
-   :align: center
-   :alt: Selection of the "Production" purpose in the upgrade form on Odoo
-
-.. danger::
-   Going into production without first testing may lead to:
-
-   - business interruptions (e.g. no longer having the possibility to validate an action)
-   - poor customer experiences (e.g. an eCommerce website that does not work correctly)
-
-.. _db-upgrade/production-assistance:
-
-Assistance
-~~~~~~~~~~
-
-If you encounter issues or problems in the **production database**, please contact the **Odoo
-Support**:
-
-#. Connect to our `Odoo Support page <https://www.odoo.com/help>`_.
-#. Under the *Ticket Description* section, select the appropriate type related to your issue but
-   **do not select** the option *An issue related to my upgrade*.
-
-   .. note::
-      After upgrading to production, the support will be provided by the Support team instead of the
-      Upgrade team.
-
-#. Please provide as much detail as you can. Where applicable, illustrate the current and previous
-   flows with videos and/or screenshots. This will avoid clarifying questions and speed up the
-   resolution process significantly.
-
-   .. image:: media/db-upgrade-production-assistance-details.png
-      :align: center
-      :alt: "Detailed Description" field in the support form on Odoo
-
-   .. warning::
-      If you choose *An issue related to my upgrade* as ticket type, the request will be redirected
-      to another team than the support one and will slow down the processing and response time.
-
-.. _db-upgrade/faq:
-
-FAQ
-===
-
-.. _db-upgrade/faq/why:
-
-Why upgrade?
-------------
-
-* You benefit from the latest features of the :ref:`new major version
-  <db-upgrade/faq/release-notes>` released by Odoo.
-* If you are in an :ref:`unsupported version <db-upgrade/supported-versions>`, you get a new version
-  with support.
-
-.. _db-upgrade/faq/when:
-
-When to upgrade?
-----------------
-
-Whenever you want. You can make your upgrade request as soon as a new version is released on our
-`website form <https://upgrade.odoo.com>`_.
-
-.. _db-upgrade/faq/availability:
-
-Availability of the new version
--------------------------------
-
-Please kindly note that as soon as we announce the release of a new major version (usually at the
-end of year), the Upgrade Service team needs to adapt the upgrade scripts to it, which is why the
-new version is not immediately available for existing databases.
-
-.. _db-upgrade/faq/finalization:
-
-Finalization of the upgrade (:abbr:`ETA (Estimated Time of Arrival)`)
----------------------------------------------------------------------
-
-Unfortunately, it is impossible to give time estimates for every upgrade request. Odoo offers so
-many possibilities (e.g. branding, workflows, customization, etc) that it can get tricky to upgrade,
-and translate to the new structure. If you use multiple apps managing sensitive data (e.g.,
-Accounting, Inventory, etc.), some cases may still require a human intervention, making the process
-slower.
-
-This is especially true during the first months following the release of a new major version, which
-can significantly lengthen the upgrade delay.
-
-In general, the ‘smaller’ the database, the quickest the upgrade. A single-user database that uses
-only CRM will be processed faster than a multi-company, multi-user database that uses Accounting,
-Sales, Purchase, and Manufacturing.
-
-So, in a nutshell, what can impact your upgrade lead time?
-
-* Source & targeted versions
-* Installed apps
-* Volume of data
-* Amount of customization (models, fields, methods, workflows, reports, website, etc.)
-* Installation of new apps or configuration changes after the start of the test phase
-
-Usually, the delays experienced during the first request (waiting time between the time you
-submitted your first request for a test upgrade) can generally give you an idea of the time to wait
-for the production request.
-
-.. _db-upgrade/faq/custom-modules:
-
-Upgrade of the custom modules
------------------------------
-
-As stated in our :doc:`/legal/terms/enterprise`, section :ref:`charges_standard`, this optional
-service is subject to additional fees.
-
-If you have a custom code, you can choose to have it upgraded by our services, by one of our
-`partners <https://www.odoo.com/partners>`_ or you can do it yourself.
-
-.. note:: |assistance-contact|
-
-.. _db-upgrade/faq/editions-change:
-
-Editions change (from Community to Enterprise)
-----------------------------------------------
-
-An upgrade does not cover a change of `Editions <https://www.odoo.com/page/editions>`_
-
-.. note:: |assistance-contact|
-
-.. _db-upgrade/faq/hosting-types-switch:
-
-Switching the hosting types (Self-hosted vs Online vs Odoo.sh)
---------------------------------------------------------------
-
-An upgrade does not cover a change of `Hosting types <https://www.odoo.com/page/hosting-types>`_.
-
-Open the following link to get :doc:`more information about how to change your hosting type
-<hosting_changes>`.
-
-.. note:: |assistance-contact|
-
-.. _db-upgrade/faq/release-notes:
-
-Release Notes by version
-------------------------
-
-Open our `Release Note <https://www.odoo.com/page/release-notes>`_ page to get a summary of the new
-features and improvements made in each version.
-
-.. _db-upgrade/assistance:
-
-Assistance
-==========
-
-.. _db-upgrade/contact:
-
-Contact our Upgrade service support
------------------------------------
-
-Should you have any more questions about the upgrade, do not hesitate to send a message to `Odoo
-Upgrade Team <mailto:upgrade@odoo.com>`_. We will be very pleased to answer it as soon as possible.
-
-.. _db-upgrade/supported-versions:
-
-Supported versions
-------------------
-
-Please note that Odoo provides support and bug fixing only for the three last major versions of Odoo.
-
-This is a factor to take into consideration before upgrading. If you are on an older version, we
-suggest you to prefer the most recent version to benefit from a longer support (before having to
-upgrade again).
-
-You can get more information about our :doc:`supported versions <supported_versions>`.

content/administration/maintain/hosting_changes.rst

@@ -49,7 +49,7 @@ From Odoo.sh to Odoo Online
 
 1.  Uninstall all the **non-standard apps**: test it in a staging build first, then do it in your production build.
 2.  **If you have time constraints, contact us earlier to schedule the transfer.**
-3. `Create a support ticket <https://www.odoo.com/help>`_ and attach the dump (if the file is too large, use any file transfer service and attach the link to your ticket). Also include your subscription number and the URL you want to use for your database (e.g.: my-company.odoo.com).
+3. `Create a support ticket <https://www.odoo.com/help>`_ and include your subscription number and the URL you want to use for your database (e.g.: my-company.odoo.com).
 4.  We will make sure your database is compatible and upload it to our cloud. In case of technical issues, we will get in touch with you.
 5.  It's done!
 

content/administration/maintain/on_premise.rst

@@ -1,9 +1,6 @@
-
-.. _db_premise:
-
-===============================
-On-premises Database management
-===============================
+==============================
+On-premise database management
+==============================
 
 Register a database
 ===================
@@ -12,7 +9,7 @@ To register your database, you just need to enter your Subscription Code in the
 banner in the App Switcher. Make sure you do not add extra spaces before or after
 your subscription code. If the registration is successful, it will turn green and
 will provide you with the Expiration Date of your freshly-registered database. You
-can check this Epiration Date in the About menu (Odoo 9) or in the Settings Dashboard
+can check this Expiration Date in the About menu (Odoo 9) or in the Settings Dashboard
 (Odoo 10).
 
 Registration Error Message
@@ -21,7 +18,7 @@ Registration Error Message
 If you are unable to register your database, you will likely encounter this
 message:
 
-.. image:: media/error_message_sub_code.png
+.. image:: on_premise/error_message_sub_code.png
     :align: center
     :alt: Something went wrong while registering your database,
           you can try again or contact Odoo Help
@@ -44,14 +41,14 @@ Solutions
   * You can unlink the old database yourself on your `Odoo Contract
     <https://accounts.odoo.com/my/subscription>`__ with the button "Unlink database"
 
-    .. image:: media/unlink_single_db.png
+    .. image:: on_premise/unlink_single_db.png
         :align: center
 
 
     A confirmation message will appear; make sure this is the correct database as
     it will be deactivated shortly:
 
-    .. image:: media/unlink_confirm_enterprise_edition.png
+    .. image:: on_premise/unlink_confirm_enterprise_edition.png
         :align: center
 
 
@@ -65,7 +62,7 @@ Solutions
     <https://accounts.odoo.com/my/subscription>`__, a short message will appear
     specifying which database is problematic:
 
-    .. image:: media/unlink_db_name_collision.png
+    .. image:: on_premise/unlink_db_name_collision.png
         :align: center
 
 
@@ -96,7 +93,7 @@ Error message due to too many users
 If you have more users in your local database than provisionned in your
 Odoo Enterprise subscription, you may encounter this message:
 
-.. image:: media/add_more_users.png
+.. image:: on_premise/add_more_users.png
     :align: center
     :alt: This database will expire in X days, you
           have more users than your subscription allows
@@ -125,7 +122,7 @@ Database expired error message
 If your database reaches its expiration date before your renew your subscription,
 you will encounter this message:
 
-.. image:: media/database_expired.png
+.. image:: on_premise/database_expired.png
     :align: center
     :alt: This database has expired.
 
@@ -157,7 +154,7 @@ You can duplicate your database by accessing the database manager on your
 server (<odoo-server>/web/database/manager). In this page, you can easily
 duplicate your database (among other things).
 
-.. image:: media/db_manager.gif
+.. image:: on_premise/db_manager.gif
     :align: center
 
 
@@ -175,5 +172,5 @@ System Parameters`, we advise you to use a `uuid generator <https://www.uuidtool
 use the unix command ``uuidgen`` to generate a new uuid. You can then simply replace it like any
 other record by clicking on it and using the edit button.
 
-.. image:: media/db_uuid.png
+.. image:: on_premise/db_uuid.png
     :align: center

content/administration/maintain/online.rst

@@ -0,0 +1,143 @@
+=================================
+Online (SaaS) database management
+=================================
+
+To manage a database, sign in to https://www.odoo.com and access the `database management page
+<https://www.odoo.com/my/databases>`_ by clicking on the user icon, then on *My Databases*.
+
+.. image:: online/my-databases.png
+   :align: center
+   :alt: Clicking on the user icon opens a drop-down menu. "My databases" button is highlighted.
+
+.. note::
+   Make sure you are connected as the administrator of the database you want to manage.
+
+.. image:: online/dropdown-menu.png
+   :align: right
+   :alt: Clicking on the gear icon opens the drop-down menu.
+
+Open the drop-down menu next to the database you want to manage by clicking on the gear icon.
+
+Several actions are available:
+
+- :ref:`online/upgrade`
+- :ref:`online/duplicate`
+- :ref:`online/rename`
+- :ref:`online/download`
+- :ref:`online/domains`
+- :ref:`online/tags`
+- :ref:`online/delete`
+- :ref:`online/contact-support`
+- :ref:`online/users`
+
+.. _online/upgrade:
+
+Upgrade
+=======
+
+Upgrade the database to the latest Odoo version.
+
+.. warning::
+   Upgrading a database to a newer version of Odoo is a complex operation that requires time and
+   caution. It is essential to test the upgrade before upgrading the production database.
+
+.. seealso::
+   - :doc:`../upgrade/process`
+
+.. _online/duplicate:
+
+Duplicate
+=========
+
+Make an exact copy of the database to be able to perform testing without compromising the daily
+operations.
+
+.. important::
+   - By checking *For testing purposes*, all external communication (emails, payments, delivery
+     orders, etc.) are disabled by default on the duplicated database.
+   - Duplicate databases expire automatically after 15 days.
+
+.. _online/rename:
+
+Rename
+======
+
+Rename the database and its URL.
+
+.. _online/download:
+
+Download
+========
+
+Download instantly a ZIP file with a backup of the database.
+
+.. note::
+   Databases are backed up daily according to the `Odoo Cloud SLA
+   <https://www.odoo.com/cloud-sla>`_.
+
+.. _online/domains:
+
+Domains
+=======
+
+Configure custom domains to access the database via another URL.
+
+.. seealso::
+   - :doc:`/applications/websites/website/publish/domain_name`
+
+.. _online/tags:
+
+Tags
+====
+
+Add tags to sort your databases out. You can search the tags in the search bar.
+
+.. _online/delete:
+
+Delete
+======
+
+Delete a database instantly.
+
+.. danger::
+   Deleting a database means that all data is permanently lost. The deletion is instant and for all
+   users. It is recommended to create a backup of the database before deleting it.
+
+Read carefully the warning message that pops up and proceed only if you fully understand the
+implications of deleting a database:
+
+.. image:: online/delete.png
+   :align: center
+   :alt: A warning message is prompted before deleting a database.
+
+.. note::
+   - Only an administrator can delete a database.
+   - The database name is immediately available for a new database.
+   - It is not possible to delete a database if it is expired or linked to a subscription. If
+     needed, please get in touch with `Odoo Support <https://www.odoo.com/help>`_.
+   - To delete your account, please get in touch with `Odoo Support <https://www.odoo.com/help>`_.
+
+.. _online/contact-support:
+
+Contact Support
+===============
+
+Access the Odoo `support page <https://www.odoo.com/help>`_ with your database's details already
+pre-filled.
+
+.. _online/users:
+
+Invite / Remove Users
+=====================
+
+To invite users, fill out the email address of the new user and click on *Invite*. To add multiple
+users, click on *Add more users*.
+
+.. image:: online/invite-users.png
+   :align: center
+   :alt: Clicking on "Add more users" adds additional email fields.
+
+To remove users, select the users to remove and click on *Remove*.
+
+.. seealso::
+   - :doc:`/applications/general/users/manage_users`

content/administration/maintain/supported_versions.rst

@@ -20,37 +20,37 @@ This matrix shows the support status of every version.
 
 **Major releases are in bold type.**
 
-+--------------------+-------------+----------+--------------+----------------+----------------------------------------------+
-|                    | Odoo Online | Odoo.sh  | On-Premise   |   Release date |                                              |
-+====================+=============+==========+==============+================+==============================================+
-| **Odoo 14.0**      |    |green|  | |green|  |   |green|    | October 2020   |                                              |
-+--------------------+-------------+----------+--------------+----------------+----------------------------------------------+
-| Odoo 13.saas~4     |    |green|  | N/A      | N/A          | August 2019    |                                              |
-+--------------------+-------------+----------+--------------+----------------+----------------------------------------------+
-| **Odoo 13.0**      |    |green|  | |green|  |   |green|    | October 2019   |                                              |
-+--------------------+-------------+----------+--------------+----------------+----------------------------------------------+
-| Odoo 12.saas~3     |    |green|  | N/A      | N/A          | August 2019    |                                              |
-+--------------------+-------------+----------+--------------+----------------+----------------------------------------------+
-| **Odoo 12.0**      |    |green|  | |green|  |   |green|    | October 2018   | *End-of-support is planned for October 2021* |
-+--------------------+-------------+----------+--------------+----------------+----------------------------------------------+
-| Odoo 11.saas~3     |   |orange|  | N/A      | N/A          | April 2018     |                                              |
-+--------------------+-------------+----------+--------------+----------------+----------------------------------------------+
-| **Odoo 11.0**      |   |orange|  | |orange| |    |red|     | October 2017   |                                              |
-+--------------------+-------------+----------+--------------+----------------+----------------------------------------------+
-| Odoo 10.saas~15    |   |orange|  | N/A      | N/A          | March 2017     |                                              |
-+--------------------+-------------+----------+--------------+----------------+----------------------------------------------+
-| Odoo 10.saas~14    |   |orange|  | N/A      | N/A          | January 2017   |                                              |
-+--------------------+-------------+----------+--------------+----------------+----------------------------------------------+
-| **Odoo 10.0**      |   |orange|  | |orange| |    |red|     | October 2016   |                                              |
-+--------------------+-------------+----------+--------------+----------------+----------------------------------------------+
-| Odoo 9.saas~11     |   |orange|  | N/A      | N/A          | May 2016       |                                              |
-+--------------------+-------------+----------+--------------+----------------+----------------------------------------------+
-| **Odoo 9.0**       |   |orange|  | N/A      |    |red|     | October 2015   |                                              |
-+--------------------+-------------+----------+--------------+----------------+----------------------------------------------+
-| Odoo 8.saas~6      |   |orange|  | N/A      | N/A          | February 2015  |                                              |
-+--------------------+-------------+----------+--------------+----------------+----------------------------------------------+
-| **Odoo 8.0**       |   |orange|  | N/A      |    |red|     | September 2014 |                                              |
-+--------------------+-------------+----------+--------------+----------------+----------------------------------------------+
++-----------------+-------------+----------+-------------+----------------+------------------------+
+|                 | Odoo Online | Odoo.sh  | On-Premise  | Release date   | End of support         |
++=================+=============+==========+=============+================+========================+
+| **Odoo 15.0**   | |green|     | |green|  | |green|     | October 2021   | October 2024 (planned) |
++-----------------+-------------+----------+-------------+----------------+------------------------+
+| **Odoo 14.0**   | |green|     | |green|  | |green|     | October 2020   | October 2023 (planned) |
++-----------------+-------------+----------+-------------+----------------+------------------------+
+| **Odoo 13.0**   | |green|     | |green|  | |green|     | October 2019   | October 2022 (planned) |
++-----------------+-------------+----------+-------------+----------------+------------------------+
+| Odoo 12.saas~3  | |orange|    | N/A      | N/A         | August 2019    |                        |
++-----------------+-------------+----------+-------------+----------------+------------------------+
+| **Odoo 12.0**   | |orange|    | |orange| | |red|       | October 2018   | October 2021           |
++-----------------+-------------+----------+-------------+----------------+------------------------+
+| Odoo 11.saas~3  | |orange|    | N/A      | N/A         | April 2018     |                        |
++-----------------+-------------+----------+-------------+----------------+------------------------+
+| **Odoo 11.0**   | |orange|    | |orange| | |red|       | October 2017   | October 2020           |
++-----------------+-------------+----------+-------------+----------------+------------------------+
+| Odoo 10.saas~15 | |orange|    | N/A      | N/A         | March 2017     |                        |
++-----------------+-------------+----------+-------------+----------------+------------------------+
+| Odoo 10.saas~14 | |orange|    | N/A      | N/A         | January 2017   |                        |
++-----------------+-------------+----------+-------------+----------------+------------------------+
+| **Odoo 10.0**   | |orange|    | |orange| | |red|       | October 2016   | October 2019           |
++-----------------+-------------+----------+-------------+----------------+------------------------+
+| Odoo 9.saas~11  | |orange|    | N/A      | N/A         | May 2016       |                        |
++-----------------+-------------+----------+-------------+----------------+------------------------+
+| **Odoo 9.0**    | |orange|    | N/A      | |red|       | October 2015   | October 2018           |
++-----------------+-------------+----------+-------------+----------------+------------------------+
+| Odoo 8.saas~6   | |orange|    | N/A      | N/A         | February 2015  |                        |
++-----------------+-------------+----------+-------------+----------------+------------------------+
+| **Odoo 8.0**    | |orange|    | N/A      | |red|       | September 2014 | October 2017           |
++-----------------+-------------+----------+-------------+----------------+------------------------+
 
 
 .. note::
@@ -66,6 +66,9 @@ This matrix shows the support status of every version.
     🏁 Future version, not released yet
 
 
+.. This is an awful way to display colored circles but "Large Green Circle Emoji" was only released
+   in 2019 (see https://unicode-table.com/en/1F7E2/). Let's wait a few more years...
+
 .. |green| image:: data:image/svg+xml;base64,PHN2ZyB4bWxucz0iaHR0cDovL3d3dy53My5vcmcvMjAwMC9zdmciIHZpZXdCb3g9IjAgMCAyMzIuMTkgMjMyLjE5Ij48Y2lyY2xlIGN4PSIxMTYuMDkiIGN5PSIxMTYuMDkiIHI9IjExNi4wOSIgc3R5bGU9ImZpbGw6IzAwYTcwMCIvPjwvc3ZnPg==
    :width: 15
 

content/administration/odoo_sh/advanced.rst

@@ -9,5 +9,4 @@ Advanced
 
    advanced/containers
    advanced/submodules
-   advanced/upgrade_your_database
    advanced/frequent_technical_questions

content/administration/odoo_sh/getting_started/create.rst

@@ -184,4 +184,4 @@ as you can only have one database linked per subscription.
 
 If you plan to make it your production,
 unlink your former database from the subscription, and register the newly imported database.
-Read the :ref:`database registration documentation <db_premise>` for instructions.
+Read the :doc:`database registration documentation <../../maintain/on_premise>` for instructions.

content/administration/upgrade.rst

@@ -0,0 +1,12 @@
+:nosearch:
+
+=======
+Upgrade
+=======
+
+.. toctree::
+
+    upgrade/process
+    upgrade/odoo_sh
+    upgrade/service_level
+    upgrade/faq

content/administration/upgrade/faq.rst

@@ -0,0 +1,171 @@
+.. |assistance-contact| replace::
+   If you need Odoo assistance on this matter, please get in touch with your Odoo Account Manager or
+   our `Sales department`_.
+.. _Sales department: mailto:sales@odoo.com
+
+===
+FAQ
+===
+
+.. _upgrade-faq/why:
+
+Why upgrade
+===========
+
+* You benefit from the latest features of the :ref:`new major version
+  <upgrade-faq/release-notes>` released by Odoo.
+* If you are in an :ref:`unsupported version <upgrade/supported-versions>`, you get a new version
+  with support.
+
+.. _upgrade-faq/when:
+
+When to upgrade
+===============
+
+Whenever you want. You can make your upgrade request as soon as a new version is released or when
+your version turns unsupported, and you still wish to enjoy support.
+
+.. _upgrade-faq/availability:
+
+Availability of the new version
+===============================
+
+As soon as Odoo announces the release of a new major version, you can create a test upgrade request
+to try the latest version. Please note that at this point, the upgrade scripts will only have been
+tested with demo data. Please report any issue you might encounter while testing via the `Odoo
+Support page <https://www.odoo.com/help>`_ and make sure to be happy with your test version before
+requesting the upgrade of your database in production.
+
+.. _upgrade-faq/duration:
+
+Duration of the upgrade
+=======================
+
+It is impossible to give time estimates for every upgrade request.
+
+In general, the "smaller" the database, the quickest the upgrade request is completed. A single-user
+database that uses only CRM will be processed faster than a multi-company, multi-user database that
+uses Accounting, Sales, Purchase, and Manufacturing.
+
+You can expect the time it takes for the platform to upgrade the test database will be similar to
+the production upgrade.
+
+.. _upgrade-faq/project:
+
+The upgrade project
+===================
+
+It depends on the user involvement (the time spent on testing, reporting problems, etc.) and the
+issues encountered that might need to be addressed by our technical team.
+
+So, in a nutshell, what can impact your upgrade lead time?
+
+* Source & targeted versions
+* Installed apps
+* Volume of data
+* Amount of customization (models, fields, methods, workflows, reports, website, etc.)
+* Installation of new apps or configuration changes after the start of the test phase
+* User commitment
+
+.. _upgrade-faq/custom-modules:
+
+Upgrade of the custom modules
+=============================
+
+As stated in our :doc:`/legal/terms/enterprise`, section :ref:`charges_standard`, this optional
+service is subject to additional fees.
+
+Depending on your situation, the custom code could be upgraded by our services, by one of our
+partners, or you can do it yourself.
+
+.. note:: |assistance-contact|
+
+.. _upgrade-faq/editions-change:
+
+Editions change (from Community to Enterprise)
+==============================================
+
+The upgrade always returns an Enterprise edition of Odoo, whether the database you sent was a
+community or enterprise edition. It is required to have an enterprise subscription to upgrade.
+
+.. note:: |assistance-contact|
+
+.. seealso::
+   - `Editions <https://www.odoo.com/page/editions>`_
+
+.. _upgrade-faq/hosting-types-switch:
+
+Switching the hosting types (Self-Hosting vs. Online Hosting - SaaS vs. Cloud Platform - Odoo.sh)
+=================================================================================================
+
+An upgrade does not cover a change of `Hosting types <https://www.odoo.com/page/hosting-types>`_.
+
+Open the following link to get :doc:`more information about how to change your hosting type
+<../maintain/hosting_changes>`.
+
+.. note:: |assistance-contact|
+
+.. _upgrade-faq/release-notes:
+
+Release Notes by version
+========================
+
+Open our `Release Note <https://www.odoo.com/page/release-notes>`_ page to get a summary of the new
+features and improvements made in each version.
+
+How long is my test available for
+---------------------------------
+
+An Odoo Online (SaaS) test database is available for one month by default. We can extend this trial
+period upon request. For Odoo.sh or on-premise, there is no restriction.
+
+How many tests to perform before upgrading to production?
+---------------------------------------------------------
+
+As many as needed. When you are comfortable with the database, run a last test upgrade 48 hours
+before requesting your production upgrade and test your workflows one last time.
+
+How to/Where to report upgrade issues?
+--------------------------------------
+
+If you encounter issues during the upgrade process, please contact the Odoo Support through the
+`Odoo Support page <https://www.odoo.com/help>`_
+
+- To report an issue discovered during the testing phase, please select **An issue related to my
+  upgrade (test phase)**.
+- To report an issue discovered post-upgrade, please select **An issue related to my upgrade
+  (production)**
+
+Upgrading to production
+-----------------------
+
+Once you have completed testing and are happy with the result, you decide on a date and time when
+you stop users from accessing Odoo, freeze all data entries, and create an upgrade request for the
+production upgrade.
+
+
+How is my data handled in the Upgrade Platform?
+-----------------------------------------------
+
+The Odoo Upgrade platform uses the same Privacy Policy as the rest of Odoo.com services.
+
+Your data is hosted on servers that follow our security guidelines, namely:
+
+- SSL - All web connections to client instances are protected with 256-bit SSL encryption
+  (HTTPS with a 2048-bit modulus SSL certificate), and running behind Grade A SSL stacks. All our
+  certificate chains are using SHA-2 already.
+- Safe System - Our servers are running recent Linux distribution with up-to-date security patches,
+  with firewall and intrusion countermeasures (not disclosed for obvious reasons).
+
+Servers are located at the same locations as our Cloud providers with the following services:
+
+- Restricted perimeter, physically accessed by authorized data center employees only
+- Physical access control with security badges or biometrical security
+- Security cameras monitoring the data center locations 24/7
+- Security personnel on-site 24/7
+
+The uploaded and migrated databases uploaded to the Upgrade platform are kept for up to 3 months and
+are permanently deleted following that period.
+
+You can learn more about privacy and data handling at Odoo by visiting our `General Data Protection
+Regulation page <https://www.odoo.com/gdpr>`_.

content/administration/upgrade/odoo_sh.rst

@@ -1,9 +1,7 @@
 
-=====================
-Upgrade your database
-=====================
-
-.. _odoosh-advanced-upgrade_your_database:
+=======================
+Odoo.sh version upgrade
+=======================
 
 Download and Upload your database
 =================================

content/administration/upgrade/process.rst

@@ -0,0 +1,256 @@
+.. |assistance-contact| replace::
+   If you need Odoo assistance on this matter, please get in touch with your Odoo Account Manager or
+   our `Sales department`_.
+.. _Sales department: mailto:sales@odoo.com
+
+===============
+Upgrade process
+===============
+
+.. _upgrade/overview:
+
+Overview
+========
+
+An upgrade is switching to a newer version of Odoo (e.g., Odoo 14.0 to Odoo 15.0).
+
+An upgrade does not cover:
+
+* Changing :ref:`editions <upgrade-faq/editions-change>` (i.e., Community to Enterprise edition)
+* Switching :ref:`hosting type <upgrade-faq/hosting-types-switch>` (i.e., On-Premise to Online or
+  Odoo.sh)
+* Migration from another ERP to Odoo
+
+.. note:: |assistance-contact|
+
+.. _upgrade/process-workflow:
+
+Process workflow
+----------------
+
+The upgrade process in a nutshell:
+
+#. You create a test upgrade request.
+#. | Odoo processes the request:
+   | This happens via an automated process that runs the database through an upgrade script and
+     takes between 20 and 120 minutes. Only if an issue(s) arises will we have to intervene
+     manually and adjust the script specifically to your database until the upgrade succeeds.
+#. Odoo delivers a test database.
+#. You test your database for possible discrepancies (see :ref:`upgrade/test-guidance`)
+#. If there are any discrepancies, you report them to the Upgrade support team via the help portal
+   (see :ref:`upgrade/test-assistance`).
+#. We will fix the issues and send you a new test database.
+#. Once you have completed the testing and are happy with the result, you decide on a date and time
+   when you stop users from accessing Odoo, freeze all data entries, and create an upgrade request
+   for the production upgrade.
+#. Odoo delivers the production database through the automated process.
+#. You restore it in your Production environment a few short hours later and continue working on the
+   newly upgraded database (this is done automatically on SaaS).
+
+.. _upgrade/get-started:
+
+Get started
+===========
+
+The upgrade process varies depending on where your database is hosted.
+
+.. _upgrade/online:
+
+Online Hosting (SaaS)
+---------------------
+
+The upgrade request is made via your `database manager <https://www.odoo.com/my/databases>`_.
+
+.. image:: process/online-access-databases.png
+   :align: center
+   :alt: Click on the profile button then on "My Databases"
+
+.. image:: process/online-upgrade-button.png
+   :align: center
+   :alt: Click on the settings button next to your database, then on "Upgrade"
+
+.. _upgrade/odoo-sh:
+
+Cloud Platform (Odoo.sh)
+------------------------
+
+:doc:`odoo_sh`
+
+.. _upgrade/on-premise:
+
+Self-Hosting (On-Premise)
+-------------------------
+
+There are two possibilities:
+
+#. Via `Odoo Upgrade service <https://upgrade.odoo.com>`_
+#. | For technically advanced users and partners, via the following command line on the machine
+     where your database is hosted:
+   | ``python <(curl -s https://upgrade.odoo.com/upgrade) test -d <your db name> -t <target
+     version>``
+
+The above command will dump your database to a file, send it to the upgrade platform for an upgrade,
+display you the live logs, and restore the upgraded database back on your server as a duplicate test
+database.
+
+.. _upgrade/testing-phase:
+
+Testing Phase (pre-production phase)
+====================================
+
+This phase allows you to review an upgraded version of your database without affecting your
+production database in any way.
+
+We suggest that you run the test upgrade process at least once, but you can do it as many times as
+you need (one at a time).
+
+Once you receive your upgraded test database, check that all data, processes, and functionality are
+still correct and working as expected.
+
+If you do find discrepancies, report your issues (see :ref:`upgrade/test-assistance`) and request
+a new test database (see :ref:`upgrade/test-db-request`) when the reported issues are fixed in
+the upgrade script.
+
+If you do not find any discrepancies, you'll be able to move on to the upgrade of your
+:ref:`production database <upgrade/production-live>`.
+
+.. _upgrade/test-db-request:
+
+Request a test database
+-----------------------
+
+When filling the `website form <https://upgrade.odoo.com>`_, select *Testing* purpose.
+
+.. image:: process/test-purpose.png
+   :align: center
+   :alt: Selection of the "Testing" purpose in the upgrade form on Odoo
+
+.. _upgrade/test-guidance:
+
+Test guidance
+-------------
+
+Every business and organization has its own operational needs and has to test its specific Odoo
+instance respectively. We recommend you look at `the test scenario
+<https://docs.google.com/document/d/1ypNs7JKPOsjNbKpdiKFH7Al6g6whZ9jr7f7duAQ5E1w/>` for further
+information.
+
+.. todo:: change link "test scenario" once the related doc is published
+
+.. _upgrade/test-assistance:
+
+Assistance
+----------
+
+If you encounter an issue in the **test database**, please get in touch with Odoo Upgrade Support
+via the `Odoo Support page <https://www.odoo.com/help>`_.
+
+Under the *Ticket Description* section, select *An issue related to my upgrade* ticket type.
+
+   .. image:: process/test-assistance.png
+      :align: center
+      :alt: Selection of "An issue related to my upgrade" as Ticket Type in the support form on Odoo
+
+   .. warning::
+      If you choose another *Ticket Description* type, the request will be redirected to another
+      team. This will slow down the processing and response time.
+
+Please provide as much detail as you can (i.e., videos and screenshots to illustrate your issue).
+This will avoid clarifying questions and speed up the resolution process significantly.
+
+   .. image:: process/test-assistance-details.png
+      :align: center
+      :alt: "Detailed Description" field in the support form on Odoo
+
+.. note::
+   * The purpose of the test phase is not to correct existing data or configurations in your
+     database.
+   * |assistance-contact|
+
+.. _upgrade/steps-production:
+
+The production launch
+---------------------
+
+.. _upgrade/production-live:
+
+Production goes live
+~~~~~~~~~~~~~~~~~~~~
+
+The production upgrade request is when you decide to upgrade your current database with all your
+production data (invoices, VAT returns, inventories, current orders) to a new version of your
+choice.
+
+After your :ref:`tests <upgrade/testing-phase>` are completed to your satisfaction, submit the
+request to upgrade your production database via our `website form <https://upgrade.odoo.com>`_.
+Select *Production* purpose.
+
+.. image:: process/production-purpose.png
+   :align: center
+   :alt: Selection of the "Production" purpose in the upgrade form on Odoo
+
+.. danger::
+   Going into production without first testing may lead to:
+
+   - business interruptions (e.g., no longer having the possibility to validate an action)
+   - poor customer experiences (e.g., an eCommerce website that does not work correctly)
+
+.. _upgrade/production-assistance:
+
+Assistance
+~~~~~~~~~~
+
+If you encounter issues or problems in the **production database**, please get in touch with **Odoo
+Support**:
+
+#. Connect to our `Odoo Support page <https://www.odoo.com/help>`_.
+#. Under the *Ticket Description* section, select the appropriate type related to your issue but
+   **do not select** the option *An issue related to my upgrade*.
+
+   .. note::
+      After upgrading to production, the support will be provided by the Support team instead of the
+      Upgrade team.
+
+#. Please provide as much detail as you can (i.e., videos and screenshots to illustrate your issue).
+   This will avoid clarifying questions and speed up the resolution process significantly.
+
+   .. image:: process/production-assistance-details.png
+      :align: center
+      :alt: "Detailed Description" field in the support form on Odoo
+
+   .. warning::
+      If you choose *An issue related to my upgrade* as ticket type, the request will be redirected
+      to another team than the support one and will slow down the processing and response time.
+
+.. _upgrade/assistance:
+
+Assistance
+==========
+
+.. _upgrade/contact:
+
+Contact our Upgrade service support
+-----------------------------------
+
+Should you have any more questions about the upgrade, do not hesitate to send a message to `Odoo
+Upgrade Team <mailto:upgrade@odoo.com>`_. We will be happy to answer it as soon as possible.
+
+.. _upgrade/supported-versions:
+
+Supported versions
+------------------
+
+Please note that Odoo provides support and bug fixing only for the three last major versions of
+Odoo.
+
+This is a factor to take into consideration before upgrading. If you are on an older version, we
+suggest you to prefer the most recent version to benefit from longer support (before having to
+upgrade again).
+
+You can get more information about our :doc:`supported versions <../maintain/supported_versions>`.
+
+.. seealso::
+   - :doc:`faq`
+   - :doc:`odoo_sh`
+   - :doc:`service_level`
+   - :doc:`../maintain/supported_versions`

content/administration/upgrade/service_level.rst

@@ -0,0 +1,37 @@
+.. |assistance-contact| replace::
+   If you need Odoo assistance on this matter, please get in touch with your Odoo Account Manager or
+   our `Sales department`_.
+.. _Sales department: mailto:sales@odoo.com
+
+=======================
+Service Level Agreement
+=======================
+
+What is covered by the Enterprise Licence?
+==========================================
+
+Databases hosted on Odoo’s Cloud platforms (Saas and Odoo.sh) or On-Premise (Self-Hosting) enjoy the
+following service at all times.
+
+The upgrade of:
+
+* standard applications
+* Studio customization (as long as the Studio app is still active)
+* customizations done by our consulting and developer services *if* they are covered by a
+  ‘Maintenance of Customisations’ subscription
+
+The Upgrade Service is limited to your database's technical conversion and adaptation (standard
+modules and data) to make it compatible with the targeted version.
+
+What upgrading does NOT cover
+=============================
+
+* The cleaning of pre-existing data & configuration while upgrading
+* Any new developments and/or upgrades of your own :ref:`custom modules
+  <upgrade-faq/custom-modules>`
+* `Training <https://www.odoo.com/learn>`_ on the latest version
+
+You can get more information about your Enterprise Licence on our :ref:`Odoo Enterprise Subscription
+Agreement <upgrade>` page.
+
+.. note:: |assistance-contact|

content/applications/finance/accounting/fiscal_localizations/localizations/colombia.rst

@@ -19,7 +19,7 @@ requires the next modules:
    contains the default setup for: chart of accounts, taxes,
    retentions, identification document types
 #. **l10n_co_edi**: This module includes all the extra fields that are
-   required for the Integration with Carvajal T&S and generate the
+   required for the Integration with Carvajal and generate the
    electronic invoice, based on the DIAN legal requirements.
 
 
@@ -43,12 +43,12 @@ filter and search for "Colombia". Then click on *Install* for the first two modu
    :align: center
 
 
-Configure credentials for Carvajal T&S web service
---------------------------------------------------
+Configure credentials for Carvajal web service
+----------------------------------------------
 
 Once that the modules are installed, in order to be able to connect
-with Carvajal T&S Web Service, it's necessary to configure the user
-and credentials, this information will be provided by Carvajal T&S.
+with Carvajal Web Service, it's necessary to configure the user
+and credentials, this information will be provided by Carvajal.
 
 Go to :menuselection:`Accounting --> Configuration --> Settings` and
 look for the *Colombian Electronic Invoice* section.
@@ -56,12 +56,20 @@ look for the *Colombian Electronic Invoice* section.
 .. image:: media/colombia03.png
    :align: center
 
-Using the Testing mode it is possible to connect with a Carvajal T&S
+Using the Testing mode it is possible to connect with a Carvajal
 testing environment. This allows users to test the complete workflow
 and integration with the CEN Financiero portal, which is accessible
-here: https://cenfinancierolab.cen.biz
+here:
 
-Once that Odoo and Carvajal T&S is fully configured and ready for
+CTS (Carvajal T&S)
+  https://cenflab.cen.biz/site/
+
+CSC (Carvajal Servicios de Comunicación)
+  https://web-stage.facturacarvajal.com/
+
+CSC is the default for new databases.
+
+Once that Odoo and Carvajal are fully configured and ready for
 production the testing environment can be disabled.
 
 

content/applications/finance/accounting/fiscal_localizations/localizations/colombia_ES.rst

@@ -18,7 +18,7 @@ requiere los siguientes Módulos:
    - Tipos de Documentos de Identificación
 
 #. **l10n_co_edi**: Este módulo incluye todos los campos adicionales que son
-   requeridos para la Integración entre Carvajal T&S y la generación de la
+   requeridos para la Integración entre Carvajal y la generación de la
    Factura Electrónica, basado en los requisitos legales de la DIAN.
 
 
@@ -42,12 +42,12 @@ Instalar a los primeros dos módulos:
    :align: center
 
 
-Configuración de las credenciales del Servicio Web de Carvajal T&S
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+Configuración de las credenciales del Servicio Web de Carvajal
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 
 | Una vez que los módulos están instalados, para poderte conectar con el
-  Servicio Web de Carvajal T&S, es necesario configurar el Usuario y las
-  Credenciales. Esta información será provista por Carvajal T&S.
+  Servicio Web de Carvajal, es necesario configurar el Usuario y las
+  Credenciales. Esta información será provista por Carvajal.
 | Ve a :menuselection:`Facturación --> Configuración --> Configuración` y busca la sección
   **Facturación Electrónica Colombiana**
 
@@ -55,14 +55,21 @@ Configuración de las credenciales del Servicio Web de Carvajal T&S
   :align: center
 
 La funcionalidad de pruebas le permite conectarse e interactuar con el
-ambiente piloto de Carvajal T&S, esto permite a los usuarios probar el
+ambiente piloto de Carvajal, esto permite a los usuarios probar el
 flujo completo y la integración con el Portal Financiero CEN, al cual
-se accede a través de la siguiente liga: `Cenfinanciero <https://cenfinancierolab.cen.biz>`_.
+se accede a través de la siguiente liga:
+
+CTS (Carvajal T&S)
+   https://cenflab.cen.biz/site/
+
+CSC (Carvajal Servicios de Comunicación)
+   https://web-stage.facturacarvajal.com/
+
+CSC es el predeterminado para nuevas bases de datos.
 
 Una vez que el ambiente de producción está listo en Odoo y en Carvajal
-T&S el ambiente de pruebas debe ser deshabilitado para poder enviar la
-información al ambiente de producción de Carvajal, para el cual es
-utilizada la siguiente URL: `Cenfinanciero <https://cenfinancierolab.cen.biz>`_.
+el ambiente de pruebas debe ser deshabilitado para poder enviar la
+información al ambiente de producción de Carvajal.
 
 
 Configuración de Información para PDF

content/applications/finance/accounting/fiscal_localizations/localizations/mexico.rst

@@ -59,33 +59,20 @@ The following modules are necessary for all databases that require Mexican local
    | All the basic data to manage accounting, taxes and the chart of accounts. The installed chart
      of accounts is based on `the SAT account grouping code
      <https://www.gob.mx/cms/uploads/attachment/file/151586/codigo_agrupador.pdf>`_.
-#. | **EDI for Mexico (l10n_mx_edi)**
+#. | **EDI for Mexico (l10n_mx_edi & l10n_mx_edi_extended)**
    | Necessary for electronic transactions, CFDI 3.3, payment complement, and addenda on invoices.
-#. | **Odoo Mexican localization reports (l10n_mx_reports)**
+#. | **Odoo Mexican localization reports (l10n_mx_reports & l10n_mx_reports_closing)**
    | All mandatory reports for electronic accounting. (Requires the accounting application).
 
 The following modules are optional, and should be installed only if they meet a specific
 organization requirement. Installing these modules is not recommended unless you are sure they
 are needed as they add fields that can unnecessarily complicate form filling.
 
-#. | **EDI External Trade Complement for Mexico (l10n_mx_edi_external_trade)**
-   | For clients that export, add the foreign trade complement to the CFDI, and the logic for
-     filling it.
-#. | **Odoo Mexico Localization for Invoice with customs Number (l10n_mx_edi_customs)**
-   | For importing customers, this module allows adding to the CFDI the request number with which
-     the merchandise to be resold entered. When it is imported into Mexico, in the invoice that
-     comes from any foreign country it is necessary to specify which was the import document; This
-     is known as a "pedimento", and it is processed at customs.
 #. | **Odoo Mexico Localization for Stock / Landing (l10n_mx_edi_landing)**
-   | Related to the import module (*l10n_mx_edi_customs*), this module allows managing the requests
-     as part of the shipping costs.
-#. | **Bank account payment to Mexico (l10n_mx_edi_payment_bank)**
-   | Add optional attributes to the payment plugin, allowing the user to select the bank account
-     that was used to pay the bills.
-#. | **Odoo Mexico Localization for Sale Coupon (l10n_mx_edi_sale_coupon)**
-   | Complements the Odoo coupon module (*sale_coupon*) to avoid errors in the generation of CFDIs.
-#. | **Tax Cash Basis Entries at Payment Date (l10n_mx_tax_cash_basis)** Create journal entries for
-   | taxes on the payment date (instead of the issue date).
+   | This module allows managing the requests as part of the shipping costs.
+#. | **Odoo Mexican XML Polizas Export (l10n_mx_xml_polizas)**
+   | With this module, you will be able to export your Journal Entries in XML ready to be uploaded
+     to the SAT.
 
 Configuration
 =============

content/applications/finance/accounting/taxation/taxes/taxcloud.rst

@@ -43,6 +43,52 @@ In Odoo
   and the zip code). Go to :menuselection:`Settings --> Users & Companies --> Companies`
   to open and edit your Company record.
 
+Automatically post taxes to the correct Tax Payable account
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+* For each one of your companies that uses TaxCloud, it might be necessary to create a 
+  **User-Defined Default** so that the new taxes generated by the TaxCloud integration are created 
+  with the correct Tax Payable account:
+  
+.. warning::
+   A User-Defined Default impacts all records at creation.  It means that **every** new tax will be 
+   set up to record income in the specified Tax Payable account, unless the tax is manually edited
+   to specify a different income account (or there exists another User-Defined Default that takes 
+   precedence).
+
+* In :menuselection:`Accounting --> Configuration --> Chart of Accounts`, select the Tax Payable
+  account for the company. Take note of the account's ``id`` in the URL string. 
+
+.. image:: taxcloud/user-default-find-account-id.png
+   :alt: The account's ID can be found in the URL string as 'id=...'. 
+   :align: center
+
+* Activate the :ref:`developer mode <developer-mode>`, then go to 
+  :menuselection:`Settings --> Technical --> Actions --> User-Defined Defaults`, and 
+  click on *Create*.
+
+* Click on *Field*, then, in the drop-down menu, on *Search More*. 
+
+.. image:: taxcloud/user-default-search-field.png
+   :alt: Click on 'Search More' in the 'Field' drop-down menu. 
+   :align: center
+
+* In the pop-up's search box, filter on the model ``tax.repartition.line`` and the field ``account``. 
+  Select the ``account`` field of the ``tax.repartition.line`` model. 
+
+.. image:: taxcloud/user-default-select-field.png
+   :alt: Select the 'account' field of the 'tax.repartition.line' model. 
+   :align: center
+
+* In the **Default Value** field, enter the ID of the company's Tax Payable account. 
+  Select the company for which this configuration should apply in the *Company* field. 
+  Click *Save*. 
+
+.. image:: taxcloud/user-default-enter-default-account-id.png
+   :alt: Enter the ID of the company's Tax Payable account. 
+   :align: center
+
+
 How it works
 ============
 

content/applications/inventory_and_mrp/inventory/management/warehouses/difference_warehouse_location.rst

@@ -10,7 +10,7 @@ A **Location**, is a specific space within your warehouse. It can be
 considered as a sublocation of your warehouse, as a shelf, a floor, an
 aisle, etc. Therefore, a location is part of one warehouse only and it
 is not possible to link one location to multiple warehouses. You can
-configure as much locations as you need under one warehouse.
+configure as many locations as you need under one warehouse.
 
 There are 3 types of locations:
 

content/applications/inventory_and_mrp/inventory/routes/concepts/use-routes.rst

@@ -257,19 +257,19 @@ The available rules trigger various actions. If Odoo offers *Push* and
 all of them:
 
 -  **Pull From**: this rule is triggered by a need for the product
-   in a specific stock location. The need can come from a sale order
-   which has been validated or for a manufacturing order which
+   in a specific location. The need can come from a sale order
+   which has been validated or from a manufacturing order which
    requires a specific component. When the need appears in the
-   source location, Odoo generates a picking to fulfill this need.
+   destination location, Odoo generates a picking to fulfill this need.
 -  **Push To**: this rule is triggered by the arrival of some
-   products in the defined source location. In case you move
+   products in the defined source location. In the case you move
    products to the source location, Odoo generates a picking to move
    those products to the destination location.
--  **Push & Pull**: it allows to generate pickings in the two
-   different situations explained above. It means that when products are
+-  **Pull & Push**: this rule allows generating pickings in the two
+   situations explained above. This means that when products are
    required at a specific location, a transfer is created from the previous location to fulfill 
-   that need. Then, a need is created in the previous location and a rule is triggered to fulfill 
-   it. Once the second need fulfilled, the products are pushed to the first location and all the
+   that need. This creates a need in the previous location and a rule is triggered to fulfill 
+   it. Once the second need is fulfilled, the products are pushed to the destination location and all the
    needs are fulfilled.
 -  **Buy**: when products are needed at the destination location, a
    request for quotation is created to fulfill the need.

content/applications/inventory_and_mrp/manufacturing/management/flexible_components_consumption.rst

@@ -0,0 +1,53 @@
+===================================
+Use flexible components consumption
+===================================
+
+Sometimes, you might need more components than usual to manufacture a
+product. Let’s say that you produce a desk combination of 4 desks and
+two chairs but your customer asks you for one more desk. Alright, you can do
+that. But you will need to register it!
+
+In case this happens, Odoo has the *flexible components consumption*
+feature available. If you enable it, you will be able to consume as many
+components as needed and it will make you save time in the registration
+of your items consumption.
+
+Configuration
+=============
+
+Using flexible component consumption is easy and can be done in a few
+steps. All you need is a *BoM* and a *Quality Control Point*.
+Therefore, you will need to activate the feature *Quality* in the
+*MRP* app settings.
+
+First, open the *BoM* you want to use for flexible component
+consumption and edit it. In the *Miscellaneous* tab, choose
+*Flexible* as the consumption type. Then, save.
+
+.. image:: media/flexible_components_consumption_01.png
+    :align: center
+
+Now, in the *Quality* app, open the *Control Point* menu, under
+*Quality Control* and create a new *Quality Control Point*. Choose
+your product, your operation and work order operation. Then, choose
+*Register Consumed Materials* as type.
+
+.. image:: media/flexible_components_consumption_02.png
+    :align: center
+
+Next, go back to your *Manufacturing* app and create a *Manufacturing
+order*. Choose the product for which you have created the flexible
+*BoM*.
+
+Then, confirm it and launch the process step. While processing, you will
+have the possibility to consume more components than expected in the
+*BoM*. To do so, click on *Continue Consumption*.
+
+.. image:: media/flexible_components_consumption_03.png
+    :align: center
+
+When the job is over, you will find a summary of your component
+consumption in the *Finished Steps* tab of your work order.
+
+.. image:: media/flexible_components_consumption_04.png
+    :align: center

content/applications/productivity/studio/concepts/understanding_general.rst

@@ -84,7 +84,7 @@ and each of them represents a mode of visualization. Some examples are: *form*,
 What is a Menu?
 ---------------
 
-A **Menu** is a button that executes and action. In Odoo Studio, to create menus (models) and
+A **Menu** is a button that executes an action. In Odoo Studio, to create menus (models) and
 rearrange their hierarchy, click on *Edit Menu*.
 
 .. image:: media/edit_menu.png

content/applications/sales/point_of_sale/overview.rst

@@ -9,3 +9,5 @@ Overview
 
    overview/getting_started
    overview/register
+   overview/https
+   overview/epos_ssc

content/applications/sales/point_of_sale/overview/epos_ssc.rst

@@ -0,0 +1,87 @@
+=========================================
+Self-signed certificate for ePOS printers
+=========================================
+
+ePos printers are designed specifically to work with your Point of Sale system, which sends the
+tickets directly to the printer.
+
+Some models don't require an IoT box, but the connection between your web browser and the printer
+may require a :doc:`secure connection with the HTTPS protocol <https>`. If so, a self-signed
+certificate is necessary to use your printer.
+
+.. note::
+   Please check the following list of compatible `Epson ePOS printers
+   <https://c4b.epson-biz.com/modules/community/index.php?content_id=91>`_. This list includes the
+   following models:
+
+   - TM-H6000IV-DT (Receipt printer only)
+   - TM-T70II-DT
+   - TM-T88V-DT
+   - TM-L90-i
+   - TM-T20II-i
+   - TM-T70-i
+   - TM-T82II-i
+   - TM-T83II-i
+   - TM-T88V-i
+   - TM-U220-i
+   - TM-m10
+   - TM-m30
+   - TM-P20 (Wi-Fi® model)
+   - TM-P60II (Receipt: Wi-Fi® model)
+   - TM-P60II (Peeler: Wi-Fi® model)
+   - TM-P80 (Wi-Fi® model)
+
+Generate a Self-signed certificate
+==================================
+
+Access your ePOS printer's settings with your web browser by navigating to its IP address, for
+example, `http://192.168.1.25`.
+
+.. note::
+   - The printer automatically prints the IP address during startup.
+   - We recommend assigning a **fixed IP address** to the printer from the network router.
+
+Go to :menuselection:`Authentication --> Certificate List` and create a new **Self-Signed
+Certificate**.
+
+- **Common Name**: the IP address of the ePos Printer, for example, `192.168.1.25`
+- **Validity Period**: `10`
+
+Create and reboot the printer, go to :menuselection:`Security --> SSL/TLS`, and check if
+**Selfsigned Certificate** is selected.
+
+Export the Self-signed certificate
+==================================
+
+To avoid having to accept the self-signed certificate several times, you can export it and then
+import it to your web browser or mobile device.
+
+To do so, access your ePOS printer's settings with your web browser by navigating to its IP address,
+for example, `https://192.168.1.25`. Then, accept the self-signed certificate.
+
+.. note::
+   Note that the protocol is now **HTTPS**.
+
+Click on :menuselection:`Connection is not secure --> Certificate is not valid`.
+
+.. image:: epos_ssc/browser-warning.png
+   :align: center
+   :alt: The web browser indicates that the connection to the printer is not secure.
+
+Go to the *Details* tab and click on **Copy to file**.
+Select X.509 in base 64 and save it.
+
+Import the Self-signed certificate to Windows (Using Chrome)
+============================================================
+
+In your Chrome browser, go to :menuselection:`Settings --> Privacy and security --> Security -->
+Manage certificates`
+
+Go to the *Trusted Root Certification Authorities* tab and click on **Import** and select
+your previous file. Accept all warnings and restart your browser.
+
+Import the Self-signed certificate to your Android device
+=========================================================
+
+On your Android device, open the settings and search for *certificate*. Then, click on **Certificate
+AC** (Install from device storage), and select the certificate.

content/applications/sales/point_of_sale/overview/https.rst

@@ -0,0 +1,22 @@
+=========================
+Secure connection (HTTPS)
+=========================
+
+If **Direct Devices** is enabled in a Point of Sale settings (for example, if you use an ePos
+printer), HTTP becomes the default protocol.
+
+Force your Point of Sale to use a secure connection (HTTPS)
+===========================================================
+
+Add a new **key** in the **System Parameters** to force your Point of Sale to use a secure
+connection with the HTTPS protocol.
+
+To do so, activate the :ref:`developer mode <developer-mode>`, go to :menuselection:`Settings -->
+Technical --> Parameters --> System Parameters`, then create a new parameter, add the following
+values and click on *Save*.
+
+- **Key**: `point_of_sale.enforce_https`
+- **Value**: `True`
+
+.. seealso::
+   - :doc:`epos_ssc`

content/applications/sales/sales/ebay_connector/setup.rst

@@ -36,6 +36,117 @@ on **Sync countries and currencies**, then you can fill in all the other fields.
 When all the fields are filled in, you can synchronize the categories and the
 policies by clicking on the adequate buttons.
 
+Accept account deletion notifications
+=====================================
+
+Since September 2021, **eBay requires supporting customer account deletion/closure notifications**.
+As such, when eBay receives an account request for deletion, all eBay partners must confirm the
+reception of the request and take further action if necessary.
+
+Odoo has a notification endpoint to receive those notifications, confirm the reception of the
+request, and handle the first set of actions to anonymize the account details in **Contacts** and
+remove the customer's access to the portal.
+
+.. important::
+   Make sure to correctly :ref:`set up your subscription to the marketplace account deletion
+   notifications <ebay/subscribe-account-deletion-notifications>` as eBay may temporarily disable
+   the related eBay account until the subscription is completed.
+
+Verify your installation of Odoo is up to date
+----------------------------------------------
+
+In order to activate the endpoint, the module **eBay Connector - Account Deletion** must be
+installed. If your Odoo database was first created after September 2021, the module is installed
+automatically and you can proceed to the :ref:`next step <ebay/retrieve-endpoint-details>`.
+
+Update Odoo to the latest release
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+The notification endpoint is made available through a new Odoo module; to be able to install it,
+you must make sure that your Odoo source code is up-to-date.
+
+- If you use Odoo on Odoo.com or Odoo.sh platform, your code is already up-to-date and 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 :doc:`this documentation page </administration/maintain/update>` or by
+  contacting your integrating partner.
+
+Update the list of available modules
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+New modules must be *discovered* by your Odoo instance to be available in the :menuselection:`Apps`
+menu.
+
+To do so, activate the :ref:`developer mode <developer-mode>`, and go to :menuselection:`Apps ->
+Update Apps List`. A wizard will ask for confirmation.
+
+Install the eBay Connector - Account Deletion update
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+.. warning::
+   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. 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.
+
+To install the module, go to the :menuselection:`Apps` menu, remove the `Apps` search facet and
+search for `ebay`. If the module **eBay Connector - Account Deletion** is present and marked as
+installed, your Odoo database is already up-to-date and you can proceed with the next step. If it is
+not yet installed, install it now.
+
+.. _ebay/retrieve-endpoint-details:
+
+Retrieve endpoint details from Odoo
+-----------------------------------
+
+The endpoint details can be found in :menuselection:`Sales --> Configuration --> Settings --> eBay`.
+Click on *Generate Token* to retrieve your **Verification Token**.
+
+.. image:: media/verification-token.png
+   :align: center
+   :alt: Button to generate an eBay verification token in Odoo
+
+.. _ebay/subscribe-account-deletion-notifications:
+
+Subscribe to account deletion notifications
+-------------------------------------------
+
+Log in on the `developer portal of eBay <https://go.developer.ebay.com/>`_ and go to **Alerts &
+Notifications**.
+
+.. image:: media/ebay-your-account.png
+   :align: center
+   :alt: Overview of the Alerts & Notifications dashboard of eBay
+
+To subscribe to deletion/closure notifications, eBay needs a few details:
+
+- An **email address** to send notifications to if the endpoint is unreachable.
+- The **endpoint details**:
+
+  - The URL to Odoo's account deletion notification endpoint
+  - A verification token
+
+.. image:: media/ebay-notification-endpoint.png
+   :align: center
+   :alt: Dedicated fields to enter the endpoint details
+
+.. tip::
+   You can edit the last two fields once the email address field is filled out.
+
+Verify the connectivity with the endpoint
+-----------------------------------------
+
+After setting the retrieved endpoint details in eBay's dashboard, consider testing the connectivity
+with the **Send Test Notification** button.
+
+You should get the following confirmation message: "A test notification was sent successfully!"
+
+.. image:: media/test-notification.png
+   :align: center
+   :alt: Button to send test notification
+
 Using the updated synchronisation method
 ========================================
 
@@ -51,7 +162,9 @@ To switch to the new synchronization mechanism:
 #. Activate the :ref:`developer mode <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)
+#. 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)
 #. Ensure that the **Next Execution Date** for both these actions are in the near future
 
 Starting with the next execution date, the new method will be used instead of the old one.

content/applications/sales/sales/products_prices/products/import.rst

@@ -23,7 +23,7 @@ How to customize the file
 Why an “ID” column?
 ===================
 
-The ID is a truly unique identifier for the line item. Feel free to use  one of your
+The ID is a truly unique identifier for the line item. Feel free to use one from your
 previous software to ease the transition into Odoo.
 
 Setting an ID is not mandatory when importing, but it helps in many cases:

content/applications/sales/subscriptions.rst

@@ -12,7 +12,7 @@ keep the churn under control and have reporting on the main KPIs: MRR, ARR, rete
 upselling, etc.
 
 .. seealso::
-   - `Odoo Tutorials: Subscriptions <https://www.odoo.com/slides/subscription-28>`_
+   - `Odoo Tutorials: Subscriptions <https://www.odoo.com/slides/subscription-20>`_
 
 .. toctree::
    :titlesonly:

content/applications/websites/website/publish/domain_name.rst

@@ -77,7 +77,7 @@ We can now apply the redirection from your domain name's manager account:
 
 .. note:: Here are some specific guidelines to create a CNAME record:
 
-   - `GoDaddy <https://be.godaddy.com/fr/help/add-a-cname-record-19236>`__
+   - `GoDaddy <https://www.godaddy.com/help/add-a-cname-record-19236>`__
    - `Namecheap <https://www.namecheap.com/support/knowledgebase/article.aspx/9646/10/how-can-i-set-up-a-cname-record-for-my-domain>`__
    - `OVH <https://www.ovh.co.uk/g1519.exchange_20132016_how_to_add_a_cname_record>`__
 

content/contributing/documentation.rst

@@ -70,12 +70,8 @@ Use the GitHub interface
 #. Verify that you are browsing the documentation in the version that you intend to change. The
    version can be selected from the dropdown in the top menu.
 
-   .. image:: documentation/version-selector.png
-
 #. Head over to the page that you want to change and click on the **Edit on GitHub** button in the
-   bottom of the left menu.
-
-   .. image:: documentation/edit-on-github.png
+   top right corner of the page.
 
 #. If you do not have edit rights on the repository (`odoo/documentation
    <https://github.com/odoo/documentation>`_), you need to fork it by clicking on the appropriate

content/contributing/documentation/rst_cheat_sheet.rst

@@ -520,7 +520,7 @@ Document metadata
 +-----------------+--------------------------------------------------------------------------------+
 | `code-column`   |  | Show a dynamic side column that can be used to display interactive          |
 |                 |    tutorials or code excerpts.                                                 |
-|                 |  | For example, see :doc:`/developer/misc/api/upgrade` or                      |
+|                 |  | For example, see                                                            |
 |                 |    :doc:`/applications/finance/accounting/getting_started/memento`.            |
 +-----------------+--------------------------------------------------------------------------------+
 | `hide-page-toc` | Hide the "On this page" sidebar and use full page width for the content.       |

content/developer/howtos/rdtraining/B_acl_irrules.rst

@@ -198,7 +198,7 @@ Since the "demo" user was not made a real-estate agent or manager, they should
 not even be able to see the real-estate application. Use a private tab or window
 to check for this (the "demo" user has the password "demo").
 
-Access Rules
+Record Rules
 ============
 
 .. seealso:: The documentation related to this topic can be found at
@@ -214,7 +214,7 @@ Access rights can grant access to an entire model but often we need to be
 more specific: while an agent can interact with properties in general we may not
 want them to update or even see properties managed by one of their colleagues.
 
-Access *rules* provide that precision: they can grant or reject access to
+Record *rules* provide that precision: they can grant or reject access to
 individual records:
 
 .. code-block:: xml
@@ -294,10 +294,10 @@ do so.
 There are two main ways to bypass existing security checks in Odoo, either
 wilfully or as a side-effect:
 
-* The ``sudo()`` method will create a new recorset in "sudo mode", this ignores
-  all access rules and access rights (although hard-coded group and user checks
+* The ``sudo()`` method will create a new recordset in "sudo mode", this ignores
+  all access rights and record rules (although hard-coded group and user checks
   may still apply).
-* Performing raw SQL queries will bypass access rules and access rights as a
+* Performing raw SQL queries will bypass access rights and record rules as a
   side-effect of bypassing the ORM itself.
 
 .. exercise::
@@ -322,12 +322,12 @@ Programmatically checking security
     At the end of this section, the creation of the invoice should be resilient
     to security issues regardless to changes to ``estate``.
 
-In Odoo, access rights and access rules are only checked *when performing data
+In Odoo, access rights and record rules are only checked *when performing data
 access via the ORM* e.g. creating, reading, searching, writing, or unlinking a
 record via ORM methods. Other methods do *not* necessarily check against any
 sort of access rights.
 
-In the previous section, we bypassed the access rules when creating the invoice
+In the previous section, we bypassed the record rules when creating the invoice
 in ``action_sold``. This bypass can be reached by any user without any access
 right being checked:
 
@@ -372,8 +372,8 @@ Explicit security checks can be performed by:
   verifies that the current user is allowed to perform the operation on *every*
   record of the set.
 
-.. warning:: Checking access rights and checking access rules are separate
-             operations, if you're checking access rules you usually want to
+.. warning:: Checking access rights and checking record rules are separate
+             operations, if you're checking record rules you usually want to
              also check access rights beforehand.
 
 .. exercise::
@@ -422,7 +422,7 @@ As before, because this is based on non-trivial records it's easier for a user
 to relax rules than to tighten them so it makes sense to default to a
 relatively stronger security model.
 
-Multi-company rules are simply access rules based on the ``company_ids`` or
+Multi-company rules are simply record rules based on the ``company_ids`` or
 ``company_id`` fields:
 
 * ``company_ids`` is all the companies to which the current user has access

content/developer/misc/api.rst

@@ -9,4 +9,4 @@ API
 
     api/odoo
     api/iap
-    api/upgrade
+    api/extract_api

content/developer/misc/api/extract_api.rst

@@ -0,0 +1,555 @@
+:code-column:
+
+===============
+Extract API
+===============
+
+Odoo provides a service allowing you to automate the processing of your invoices. The service scans your document using an Optical
+Character Recognition (OCR) engine and then uses AI-based algorithms to extract the fields of interest such as the total, the due date, or
+the invoice lines. More functional information can be found on the `demo page <https://www.odoo.com/page/invoice-automation>`_.
+
+This service is a paid service. Each invoice processing will cost you one credit. Three different sized packs can be bought on `iap.odoo.com <https://iap.odoo.com/iap/in-app-services/259?sortby=date>`_.
+
+You can either use this service directly in the Odoo Accounting App or through the API. The Extract API which is detailed in the next section
+allows you to integrate our service directly into your own projects.
+
+Invoices
+========
+The extract API use the JSON-RPC2_ protocol. The diffent routes are located at the following address: **https://iap-extract.odoo.com**.
+
+Expected successful flow
+------------------------
+
+1. Call :ref:`webservices/extract_api/invoice_parse` to submit your invoices (one call for each invoice). On success, you receive a `document_id` in the response.
+2. You then have to regularly poll :ref:`webservices/extract_api/invoice_get_results` to get the document's parsing status.
+3. Once the result received, you can validate it by calling :ref:`webservices/extract_api/invoice_validate` and sending the expected values.
+   This step is optional but greatly helps the system to improve.
+
+These 3 routes are detailed in this :ref:`section <webservices/extract_api/routes>`. The HTTP POST method should be used for all of them. A python implementation of the full flow
+can be found :download:`here <extract_api/implementation.py>` and a token for integration testing is provided in the :ref:`integration testing section <webservices/extract_api/integration_testing>`.
+
+.. _webservices/extract_api/routes:
+
+Routes
+------
+
+.. _webservices/extract_api/invoice_parse:
+
+``/iap/invoice_extract/parse``
+''''''''''''''''''''''''''''''
+
+Description
+^^^^^^^^^^^
+Request a processing of the document from the OCR. The route will return a `document_id` you can use to obtain the result of your request.
+
+Request Body
+^^^^^^^^^^^^
+
+``jsonrpc`` (required)
+    Must be exactly “2.0”.
+``method`` (required)
+    Must be “call”.
+``id`` (required)
+    An identifier established by the client. It allows the client to keep track of which response goes with which request. This makes asynchronous calls easier.
+``params``
+    ``account_token`` (required)
+        The token of the account from which credits will be taken. Each successful call costs one token.
+    ``version`` (optional)
+        The version will determine the format of your requests and the format of the server response. Some results can be unavailable in older versions. For the current
+        version 1.2.0, send ‘120’. If not specified, the latest version will be used.
+    ``documents`` (required)
+        The invoice must be provided as a string in the ASCII encoding. The list should contain only one string. If multiple strings are provided only the first string
+        corresponding to a pdf will be processed. If no pdf is found, the first string will be processed. This field is a list only for legacy reasons. The supported extensions
+        are *pdf*, *png*, *jpg* and *bmp*.
+    ``user_infos`` (required)
+        Information concerning the person to whom the invoice is intended. This information is not required in order for the service to work but it greatly improves the quality of the result.
+
+        ``user_company_vat`` (optional)
+            VAT number of the client.
+        ``user_company_name`` (optional)
+            Name of the client’s company.
+        ``user_company_country_code`` (optional)
+            Country code of the client. Format: `ISO3166 alpha-2 <https://www.iban.com/country-codes>`_.
+        ``user_lang`` (optional)
+            The client language. Format: *language_code + _ + locale* (ex: fr_FR, en_US).
+        ``user_email`` (optional)
+            The client email.
+
+.. rst-class:: setup doc-aside
+
+.. switcher::
+
+    .. code-block:: text
+
+            {
+                "jsonrpc": string,
+                "method": string,
+                "params": {
+                        "account_token": string (hex),
+                        "version": int,
+                        "documents": [string],
+                        "user_infos": {
+                                "user_company_vat": string,
+                                "user_company_name": string,
+                                "user_company_country_code": string,
+                                "user_lang": string,
+                                "user_email": string,
+                        },
+                },
+                "id": string (hex),
+            }
+
+Response
+^^^^^^^^
+
+``jsonrpc``
+    A string specifying the version of the JSON-RPC protocol. It will be “2.0”.
+``id``
+    The identifier you set in the request body.
+``result``
+    ``status_code``
+        |STATUS_CODE|
+    ``status_msg``
+        |STATUS_MSG|
+    ``document_id``
+        Only present if the request is successful.
+
+.. note::  The API does not actually use the JSON-RPC error scheme. Instead the API has its own error scheme bundled inside a successful JSON-RPC result.
+
+=============  ==============================================================
+ status_code       status_msg
+=============  ==============================================================
+0              Success
+2              An error occurred
+3              You don't have enough credit
+6              Unsupported file format
+9              Server is currently under maintenance. Please try again later.
+=============  ==============================================================
+
+.. rst-class:: setup doc-aside
+
+.. switcher::
+
+    .. code-block:: text
+
+        {
+            "jsonrpc": string,
+            "id": string,
+            "result": {
+                "status_code": int,
+                "status_msg": string,
+                "document_id": int,
+            }
+        }
+
+
+.. _webservices/extract_api/invoice_get_results:
+
+``/iap/invoice_extract/get_results``
+''''''''''''''''''''''''''''''''''''
+
+Description
+^^^^^^^^^^^
+Request the results of the documents ids obtained with the :ref:`/parse <webservices/extract_api/invoice_parse>` route. Can either return the results or a "request pending" message.
+
+Request Body
+^^^^^^^^^^^^
+
+``jsonrpc`` (required)
+    |SAME_AS_PARSE|
+``method`` (required)
+    |SAME_AS_PARSE|
+``id`` (required)
+    |SAME_AS_PARSE|
+``params``:
+    ``version`` (required)
+        |SAME_AS_PARSE|
+    ``documents_ids`` (required)
+        The list of ``document_id`` for which you want to get the current parsing status.
+
+.. rst-class:: setup doc-aside
+
+.. switcher::
+
+    .. code-block:: text
+
+        {
+            "jsonrpc": string,
+            "method": string,
+            "params": {
+                "version": int,
+                "documents_ids": [int]
+            },
+            "id": string (hex),
+        }
+
+
+Response
+^^^^^^^^
+
+``jsonrpc``
+    |SAME_AS_PARSE|
+``id``
+    |SAME_AS_PARSE|
+``result``
+    Dictionary where each key is a document_id. For each ``document_id``:
+
+    ``status_code``
+        |STATUS_CODE|
+    ``status_msg``
+        |STATUS_MSG|
+    ``results``
+        Only present if the request is successful.
+
+.. warning:: result keys are strings despite the fact that the document_ids given in the request body are integers.
+
+=============  ==============================================================
+ status_code       status_msg
+=============  ==============================================================
+0              Success
+1              Not ready
+2              An error occurred
+9              Server is currently under maintenance. Please try again later.
+=============  ==============================================================
+
+.. rst-class:: setup doc-aside
+
+.. switcher::
+
+    .. code-block:: text
+
+        {
+            "jsonrpc": string,
+            "id": string,
+            "result": {
+                "document_id_1": {
+                    "status_code": int,
+                    "status_msg": str,
+                    "results": [{"feature_1_name": feature_1_result,
+                                 "feature_2_name": feature_2_result,
+                                 …
+                                }]
+                    },
+                "document_id_2": {
+                    "status_code": int,
+                    "status_msg": str,
+                    "results": [{"feature_1_name": feature_1_result,
+                                 "feature_2_name": feature_2_result,
+                                 …
+                                }]
+                    },
+                    ...
+            }
+        }
+
+.. _webservices/extract_api/invoice_get_results/feature_result:
+
+``feature_result``
+''''''''''''''''''
+
+Each field of interest we want to extract from the invoice such as the total or the due date are also called features. An exhaustive list of all the extracted features can be found in the table below.
+
+For each feature, we return a list of candidates and we spotlight the candidate our model predicts to be the best fit for the feature.
+
+``selected_value``
+    The best candidate for this feature.
+``words``
+    List of all the candidates for this feature ordered by decreasing score.
+
+.. container:: doc-aside
+
+    .. switcher::
+
+        .. code-block:: text
+
+            {
+                "selected_value": candidate_12,
+                "words": [candidate_12, candidate_3, candidate_4,...]
+            }
+
+
+``candidate``
+'''''''''''''
+
+For each candidate we give its representation and position in the document. Candidates are sorted by decreasing order of suitability.
+
+``content``
+    Representation of the candidate.
+``coords``
+    ``[center_x, center_y, width, height, rotation_angle]``. The position and dimensions are relative to the size of the page and are therefore between 0 and 1.
+    The angle is a clockwise rotation measured in degrees.
+``page``
+    Page of the original document on which the candidate is located (starts at 0).
+
+.. container:: doc-aside
+
+    .. switcher::
+
+        .. code-block:: text
+
+            {
+                "content": string|float,
+                "coords": [float, float, float, float, float],
+                "page": int
+            }
+
++-------------------------+------------------------------------------------------------------------------------+
+| Feature name            | Specifities                                                                        |
++=========================+====================================================================================+
+| ``SWIFT_code``          | **content** is a dictionary encoded as a string.                                   |
+|                         |                                                                                    |
+|                         | It contains information about the detected SWIFT code                              |
+|                         | (or `BIC <https://www.iso9362.org/isobic/overview.html>`_).                        |
+|                         |                                                                                    |
+|                         | Keys:                                                                              |
+|                         |                                                                                    |
+|                         | ``bic``                                                                            |
+|                         |     detected BIC (string).                                                         |
+|                         | ``name`` (optional)                                                                |
+|                         |     bank name (string).                                                            |
+|                         | ``country_code``                                                                   |
+|                         |     ISO3166 alpha-2 country code of the bank (string).                             |
+|                         | ``city`` (optional)                                                                |
+|                         |     city of the bank (string).                                                     |
+|                         | ``verified_bic``                                                                   |
+|                         |     True if the BIC has been found in our DB (bool).                               |
+|                         |                                                                                    |
+|                         | Name and city are present only if verified_bic is true.                            |
++-------------------------+------------------------------------------------------------------------------------+
+| ``VAT_Number``          | **content** is a string                                                            |
++-------------------------+------------------------------------------------------------------------------------+
+| ``country``             | **content** is a string                                                            |
++-------------------------+------------------------------------------------------------------------------------+
+| ``currency``            | **content** is a string                                                            |
++-------------------------+------------------------------------------------------------------------------------+
+| ``date``                | **content** is a string                                                            |
+|                         |                                                                                    |
+|                         | Format : *YYYY-MM-DD HH:MM:SS*                                                     |
++-------------------------+------------------------------------------------------------------------------------+
+| ``due_date``            | Same as for ``date``                                                               |
++-------------------------+------------------------------------------------------------------------------------+
+| ``global_taxes``        | **content** is a float                                                             |
+|                         |                                                                                    |
+|                         | **candidate** has an additional field ``amount_type``. Its value is always percent.|
+|                         |                                                                                    |
+|                         | **selected_values** is a list of candidates.                                       |
++-------------------------+------------------------------------------------------------------------------------+
+| ``global_taxes_amount`` | **content** is a float                                                             |
++-------------------------+------------------------------------------------------------------------------------+
+| ``invoice_id``          | **content** is a string                                                            |
++-------------------------+------------------------------------------------------------------------------------+
+| ``subtotal``            | **content** is a float                                                             |
++-------------------------+------------------------------------------------------------------------------------+
+| ``total``               | **content** is a float                                                             |
++-------------------------+------------------------------------------------------------------------------------+
+| ``supplier``            | **content** is a string                                                            |
++-------------------------+------------------------------------------------------------------------------------+
+
+``feature_result`` for the ``invoice_lines`` feature
+''''''''''''''''''''''''''''''''''''''''''''''''''''
+
+It follows a more specific structure. It is basically a list of dictionaries where each dictionary represents an invoice line. Each value follows
+a :ref:`webservices/extract_api/invoice_get_results/feature_result` structure.
+
+.. container:: doc-aside
+
+    .. switcher::
+
+        .. code-block:: text
+
+            [
+                {
+                    "description": feature_result,
+                    "discount": feature_result,
+                    "product": feature_result,
+                    "quantity": feature_result,
+                    "subtotal": feature_result,
+                    "total": feature_result,
+                    "taxes": feature_result,
+                    "total": feature_result,
+                    "unit": feature_result,
+                    "unit_price": feature_result
+                },
+                ...
+            ]
+
+.. _webservices/extract_api/invoice_validate:
+
+``/iap/invoice_extract/validate``
+'''''''''''''''''''''''''''''''''
+
+Description
+^^^^^^^^^^^
+Route that validates the different features of an invoice. The validation step is an optional step but is strongly recommended. By telling the system if it were right or wrong for each
+feature you give an important feedback. It has no direct impact but it helps the system to greatly improve its prediction accuracy for the invoices you will send in the future.
+
+Request Body
+^^^^^^^^^^^^
+
+``jsonrpc`` (required)
+    |SAME_AS_PARSE|
+``method`` (required)
+    |SAME_AS_PARSE|
+``params``
+    ``documents_id`` (required)
+        Id of the document for which you want to validate the result.
+    ``values``
+        Contains the validation for each feature. The field ``merged_line`` indicates if the ``invoice_lines`` have been merged or not.
+
+.. note:: You don't have to validate all the features in order for the validation to succeed. However :ref:`/validate <webservices/extract_api/invoice_validate>` can't be called multiple times for a same invoice.
+          Therefore you should validate all the features you want to validate at once.
+
+.. rst-class:: setup doc-aside
+
+.. switcher::
+
+    .. code-block:: text
+
+        {
+            "jsonrpc": string,
+            "method": string,
+            "params": {
+                "document_id": int,
+                "values": {
+                    "merged_lines": bool
+                    "feature_name_1": validation_1,
+                    "feature_name_2": validation_2,
+                    ...
+                }
+            },
+            "id": string (hex),
+        }
+
+``validation``
+''''''''''''''
+
+A **validation** for a given feature is a dictionary containing the textual representation of the expected value for this given feature.
+This format apply for all the features except for ``global_taxes`` and ``invoice_lines`` which have more complex validation format.
+
+.. rst-class:: setup doc-aside
+
+.. switcher::
+
+    .. code-block:: text
+
+        { "content": string|float }
+
+validation for ``global_taxes``
+'''''''''''''''''''''''''''''''
+
+**content** is a list of dictionaries. Each dictionary represents a tax:
+
+``amount``
+    Amount on which the tax is applied.
+``tax_amount``
+    Amount of the tax.
+``tax_amount_type``
+    Indicates if the ``tax_amount`` is a percentage or a fixed value. The type must be specified using the literal string "fixed" or "percent".
+``tax_price_include``
+    Indicates if ``amount`` already contains the tax or not.
+
+.. rst-class:: setup doc-aside
+
+.. switcher::
+
+    .. code-block:: text
+
+        {"content": [
+            {
+                "amount": float,
+                "tax_amount": float,
+                "tax_amount_type": "fixed"|"percent",
+                "tax_price_include": bool
+            },
+            ...
+        ]}
+
+validation for ``invoice_lines``
+''''''''''''''''''''''''''''''''
+
+**lines** is a list of dictionaries. Each dictionary represents an invoice line. The dictionary keys speak for themselves.
+
+.. rst-class:: setup doc-aside
+
+.. switcher::
+
+    .. code-block:: text
+
+        {"lines": [
+            {
+                "description": string,
+                "quantity": float,
+                "unit_price": float,
+                "product": string,
+                "taxes_amount": float,
+                "taxes": [
+                            {
+                                "amount": float,
+                                "type": "fixed"|"percent",
+                                "price_include": bool
+                            },
+                            ...
+                        ],
+                "subtotal": float,
+                "total": float
+            },
+            ...
+        ]}
+
+Response
+--------
+
+``jsonrpc``
+    |SAME_AS_PARSE|
+``id``
+    |SAME_AS_PARSE|
+``result``
+    ``status_code``
+        |STATUS_CODE|
+    ``status_msg``
+        |STATUS_MSG|
+
+=============  ==========================================================
+ status_code       status_msg
+=============  ==========================================================
+0              Success
+12             Validation format is incorrect
+=============  ==========================================================
+
+.. rst-class:: setup doc-aside
+
+.. switcher::
+
+    .. code-block:: text
+
+        {
+            "jsonrpc": string,
+            "id": string,
+            "result": {
+                "status_code": int,
+                "status_msg": string,
+            }
+        }
+
+
+.. _webservices/extract_api/integration_testing:
+
+Integration Testing
+===================
+
+You can test your integration by using *integration_token* as ``account_token`` in the :ref:`/parse <webservices/extract_api/invoice_parse>` request.
+
+Using this token put you in test mode and allows you to simulate the entire flow without really parsing a document and without being billed one credit for each successful invoice parsing.
+
+The only technical differences in test mode is that the document you send is not parsed by the system and that the response you get from :ref:`/get_results <webservices/extract_api/invoice_get_results>`
+is a hard-coded one.
+
+A python implementation of the full flow can be found :download:`here <extract_api/implementation.py>`.
+
+.. _JSON-RPC2: https://www.jsonrpc.org/specification
+
+.. |SAME_AS_PARSE| replace:: Same as for :ref:`/parse <webservices/extract_api/invoice_parse>`.
+
+.. |STATUS_CODE| replace:: The code indicating the status of the request. ``status_code`` is 0 in case of success. Other ``status_code`` are detailed in the table below.
+
+.. |STATUS_MSG| replace:: A string giving verbose details about the request status.

content/developer/misc/api/extract_api/implementation.py

@@ -0,0 +1,100 @@
+import base64
+import time
+import sys
+import json
+import requests
+
+account_token = "integration_token"  # Use your token
+domain_name = "https://iap-extract.odoo.com"
+path_to_pdf = "/path/to/invoice_file"
+
+API_VERSION = 120  # Do not change
+SUCCESS = 0
+NOT_READY = 1
+
+def jsonrpc(path, params):
+    payload = {
+        'jsonrpc': '2.0',
+        'method': 'call',
+        'params': params,
+        'id': 0,
+    }
+    req = requests.post(domain_name+path, json=payload, timeout=10)
+    req.raise_for_status()
+    resp = req.json()
+    return resp
+
+
+with open(path_to_pdf, "rb") as file:
+    params = {
+        'account_token': account_token,
+        'version': API_VERSION,
+        'documents': [base64.b64encode(file.read()).decode('ascii')],
+    }
+
+response = jsonrpc("/iap/invoice_extract/parse", params)
+print("/parse call status: ", response['result']['status_msg'])
+
+if response['result']['status_code'] != SUCCESS:
+    sys.exit(1)
+
+# You received an id that you can use to poll the server to get the result of the ocr when it will be ready
+document_id = response['result']['document_id']
+params = {
+    'version': API_VERSION,
+    'document_ids': [document_id],  # you can request the results of multiple documents at once if wanted
+}
+
+response = jsonrpc("/iap/invoice_extract/get_results", params)
+document_id = str(document_id) # /get_results expects a string despite the fact that the returned document_id is a int
+
+while response['result'][document_id]['status_code'] == NOT_READY:  # 1 is the status code indicating that the server is still processing the document
+    print("Still processing... Retrying in 5 seconds")
+    time.sleep(5)
+    response = jsonrpc("/iap/invoice_extract/get_results", params)
+
+with open('results.txt', 'w') as outfile:
+    json.dump(response, outfile, indent=2)
+print("\nResult saved in results.txt")
+
+if response['result'][document_id]['status_code'] != SUCCESS:
+    print(response['result'][document_id]['status_msg'])  # if it isn't a success, print the error message
+    sys.exit(1)
+
+document_results = response['result'][document_id]['results'][0]
+print("\nTotal:", document_results['total']['selected_value']['content'])
+print("Subtotal:", document_results['subtotal']['selected_value']['content'])
+print("Invoice id:", document_results['invoice_id']['selected_value']['content'])
+print("Date:", document_results['date']['selected_value']['content'])
+print("...\n")
+
+params = {
+    'document_id': document_id,
+    'values': {
+        'total': {'content': 100.0},
+        'subtotal': {'content': 100.0},
+        'global_taxes': {'content': []},
+        'global_taxes_amount': {'content': 0.0},
+        'date': {'content': '2020-09-25'},
+        'due_date': {'content': '2020-09-25'},
+        'invoice_id': {'content': document_results['invoice_id']['selected_value']['content']},
+        'partner': {'content': 'twinnta'},
+        'VAT_Number': {'content': 'BE23252248420'},
+        'currency': {'content': 'USD'},
+        'merged_lines': False,
+        'invoice_lines': {'lines': [{'description': 'Total TVA ',
+                                     'quantity': 1.0,
+                                     'unit_price': 100.0,
+                                     'product': False,
+                                     'taxes_amount': 0.0,
+                                     'taxes': [],
+                                     'subtotal': 100.0,
+                                     'total': 100.0}]
+        }
+    }
+}
+response = jsonrpc("/iap/invoice_extract/validate", params)
+if response['result']['status_code'] == SUCCESS:
+    print("/validate call status: Success")
+else:
+    print("/validate call status: wrong format")

content/developer/misc/api/odoo.rst

@@ -99,9 +99,9 @@ parameters
     want to use:
 
     * Log in your instance with an administrator account
-    * Go to :menuselection:`Settings --> Users --> Users`
+    * Go to :menuselection:`Settings --> Users & Companies --> Users`
     * Click on the user you want to use for XML-RPC access
-    * Click the :guilabel:`Change Password` button
+    * Click on :guilabel:`Action` and select :guilabel:`Change Password`
     * Set a :guilabel:`New Password` value then click
       :guilabel:`Change Password`.
 

content/developer/misc/api/upgrade.rst

@@ -1,655 +0,0 @@
-:code-column:
-
-.. _reference/upgrade-api:
-
-================
-Database Upgrade
-================
-
-Introduction
-~~~~~~~~~~~~
-
-This document describes the API used to upgrade an Odoo database to a
-higher version.
-
-It allows a database to be upgraded without ressorting to the html form at
-https://upgrade.odoo.com
-Although the database will follow the same process described on that form.
-
-
-The required steps are:
-
-* :ref:`creating a request <upgrade-api-create-method>`
-* :ref:`uploading a database dump <upgrade-api-upload-method>`
-* :ref:`running the upgrade process <upgrade-api-process-method>`
-* :ref:`obtaining the status of the database request <upgrade-api-status-method>`
-* :ref:`downloading the upgraded database dump <upgrade-api-download-method>`
-
-The methods
-~~~~~~~~~~~
-
-.. _upgrade-api-create-method:
-
-Creating a database upgrade request
-===================================
-
-This action creates a database request with the following information:
-
-* your contract reference
-* your email address
-* the target version (the Odoo version you want to upgrade to)
-* the purpose of your request (test or production)
-* the database dump name (required but purely informative)
-* optionally the server timezone (for Odoo source version < 6.1)
-
-The ``create`` method
----------------------
-
-.. py:function:: https://upgrade.odoo.com/database/v1/create
-
-    Creates a database upgrade request
-
-    :param str contract: (required) your enterprise contract reference
-    :param str email: (required) your email address
-    :param str target: (required) the Odoo version you want to upgrade to. Valid choices: 11.0, 12.0, 13.0
-    :param str aim: (required) the purpose of your upgrade database request. Valid choices: test, production.
-    :param str filename: (required) a purely informative name for you database dump file
-    :param str timezone: (optional) the timezone used by your server. Only for Odoo source version < 6.1
-    :return: request result
-    :rtype: JSON dictionary
-
-The *create* method returns a JSON dictionary containing the following keys:
-
-.. _upgrade-api-json-failure:
-
-``failures``
-''''''''''''
-
-The list of errors.
-
-A list of dictionaries, each dictionary giving information about one particular
-error. Each dictionary can contain various keys depending of the type of error
-but you will always get the ``reason`` and the ``message`` keys:
-
-* ``reason``: the error type
-* ``message``: a human friendly message
-
-Some possible keys:
-
-* ``code``: a faulty value
-* ``value``: a faulty value
-* ``expected``: a list of valid values
-
-See a sample output aside.
-
-.. rst-class:: setup doc-aside
-
-.. switcher::
-
-    .. code-block:: json
-
-            {
-              "failures": [
-                {
-                  "expected": [
-                    "11.0",
-                    "12.0",
-                    "13.0",
-                  ],
-                  "message": "Invalid value \"5.0\"",
-                  "reason": "TARGET:INVALID",
-                  "value": "5.0"
-                },
-                {
-                  "code": "M123456-abcxyz",
-                  "message": "Can not find contract M123456-abcxyz",
-                  "reason": "CONTRACT:NOT_FOUND"
-                }
-              ]
-            }
-
-
-``request``
-'''''''''''
-
-If the *create* method is successful, the value associated to the *request* key
-will be a dictionary containing various information about the created request:
-
-The most important keys are:
-
-* ``id``: the request id
-* ``key``: your private key for this request
-
-These 2 values will be requested by the other methods (upload, process and status)
-
-The other keys will be explained in the section describing the :ref:`status method <upgrade-api-status-method>`.
-
-
-Sample script
-'''''''''''''
-
-Here are 2 examples of database upgrade request creation using:
-
-* one in the python programming language using the requests library
-* one in the bash programming language using `curl <https://curl.haxx.se>`_ (tool
-  for transferring data using http) and `jq <https://stedolan.github.io/jq>`_ (JSON processor):
-
-.. rst-class:: setup doc-aside
-
-.. switcher::
-
-    .. code-block:: python
-
-        import requests
-
-        CREATE_URL = "https://upgrade.odoo.com/database/v1/create"
-        CONTRACT = "M123456-abcdef"
-        AIM = "test"
-        TARGET = "12.0"
-        EMAIL = "john.doe@example.com"
-        FILENAME = "db_name.dump"
-
-        fields = dict([
-            ('aim', AIM),
-            ('email', EMAIL),
-            ('filename', DB_SOURCE),
-            ('contract', CONTRACT),
-            ('target', TARGET),
-        ])
-
-        r = requests.get(CREATE_URL, data=fields)
-        print(r.text)
-
-    .. code-block:: bash
-
-        CONTRACT=M123456-abcdef
-        AIM=test
-        TARGET=12.0
-        EMAIL=john.doe@example.com
-        FILENAME=db_name.dump
-        CREATE_URL="https://upgrade.odoo.com/database/v1/create"
-        URL_PARAMS="contract=${CONTRACT}&aim=${AIM}&target=${TARGET}&email=${EMAIL}&filename=${FILENAME}"
-        curl -sS "${CREATE_URL}?${URL_PARAMS}" > create_result.json
-
-        # check for failures
-        failures=$(cat create_result.json | jq -r '.failures[]')
-        if [ "$failures" != "" ]; then
-          echo $failures | jq -r '.'
-          exit 1
-        fi
-
-.. _upgrade-api-upload-method:
-
-Uploading your database dump
-============================
-
-There are 2 methods to upload your database dump:
-
-* the ``upload`` method using the HTTPS protocol
-* the ``request_sftp_access`` method using the SFTP protocol
-
-The ``upload`` method
----------------------
-
-It's the most simple and most straightforward way of uploading your database dump.
-It uses the HTTPS protocol.
-
-.. py:function:: https://upgrade.odoo.com/database/v1/upload
-
-    Uploads a database dump
-
-    :param str key: (required) your private key
-    :param str request: (required) your request id
-    :return: request result
-    :rtype: JSON dictionary
-
-The request id and the private key are obtained using the :ref:`create method
-<upgrade-api-create-method>`
-
-The result is a JSON dictionary containing the list of ``failures``, which
-should be empty if everything went fine.
-
-.. rst-class:: setup doc-aside
-
-.. switcher::
-
-    .. code-block:: python
-
-        import requests
-
-        UPLOAD_URL = "https://upgrade.odoo.com/database/v1/upload"
-        DUMPFILE = "/tmp/dump.sql"
-
-        fields = dict([
-            ('request', '10534'),
-            ('key', 'Aw7pItGVKFuZ_FOR3U8VFQ=='),
-        ])
-        headers = {"Content-Type": "application/octet-stream"}
-
-        with open(DUMPFILE, 'rb') as f:
-            requests.post(UPLOAD_URL, data=f, params=fields, headers=headers)
-
-    .. code-block:: bash
-
-        UPLOAD_URL="https://upgrade.odoo.com/database/v1/upload"
-        DUMPFILE="openchs.70.cdump"
-        KEY="Aw7pItGVKFuZ_FOR3U8VFQ=="
-        REQUEST_ID="10534"
-        URL_PARAMS="key=${KEY}&request=${REQUEST_ID}"
-        HEADER="Content-Type: application/octet-stream"
-        curl -H $HEADER --data-binary "@${DUMPFILE}" "${UPLOAD_URL}?${URL_PARAMS}"
-
-.. _upgrade-api-request-sftp-access-method:
-
-The ``request_sftp_access`` method
-----------------------------------
-
-This method is recommended for big database dumps.
-It uses the SFTP protocol and supports resuming.
-
-It will create a temporary SFTP server where you can connect to and allow you
-to upload your database dump using an SFTP client.
-
-.. py:function:: https://upgrade.odoo.com/database/v1/request_sftp_access
-
-    Creates an SFTP server
-
-    :param str key: (required) your private key
-    :param str request: (required) your request id
-    :param str ssh_keys: (required) the path to a file listing the ssh public keys you'd like to use
-    :return: request result
-    :rtype: JSON dictionary
-
-The request id and the private key are obtained using the :ref:`create method
-<upgrade-api-create-method>`
-
-The file listing your ssh public keys should be roughly similar to a standard ``authorized_keys`` file.
-This file should only contains public keys, blank lines or comments (lines starting with the ``#`` character)
-
-Your database upgrade request should be in the ``draft`` state.
-
-The ``request_sftp_access`` method returns a JSON dictionary containing the following keys:
-
-
-.. rst-class:: setup doc-aside
-
-.. switcher::
-
-    .. code-block:: python
-
-        import requests
-
-        UPLOAD_URL = "https://upgrade.odoo.com/database/v1/request_sftp_access"
-        SSH_KEY = "$HOME/.ssh/id_rsa.pub"
-        SSH_KEY_CONTENT = open(SSH_KEY,'r').read()
-
-        fields = dict([
-            ('request', '10534'),
-            ('key', 'Aw7pItGVKFuZ_FOR3U8VFQ=='),
-            ('ssh_keys', SSH_KEY_CONTENT)
-        ])
-
-        r = requests.post(UPLOAD_URL, params=fields)
-        print(r.text)
-
-    .. code-block:: bash
-
-        REQUEST_SFTP_ACCESS_URL="https://upgrade.odoo.com/database/v1/request_sftp_access"
-        SSH_KEYS=/path/to/your/authorized_keys
-        KEY="Aw7pItGVKFuZ_FOR3U8VFQ=="
-        REQUEST_ID="10534"
-        URL_PARAMS="key=${KEY}&request=${REQUEST_ID}"
-
-        curl -sS "${REQUEST_SFTP_ACCESS_URL}?${URL_PARAMS}" -F ssh_keys=@${SSH_KEYS} > request_sftp_result.json
-
-        # check for failures
-        failures=$(cat request_sftp_result.json | jq -r '.failures[]')
-        if [ "$failures" != "" ]; then
-          echo $failures | jq -r '.'
-          exit 1
-        fi
-
-
-``failures``
-''''''''''''
-
-The list of errors. See :ref:`failures <upgrade-api-json-failure>` for an
-explanation about the JSON dictionary returned in case of failure.
-
-``request``
-'''''''''''
-
-If the call is successful, the value associated to the *request* key
-will be a dictionary containing your SFTP connection parameters:
-
-* ``hostname``: the host address to connect to
-* ``sftp_port``: the port to connect to
-* ``sftp_user``: the SFTP user to use for connecting
-* ``shared_file``: the filename you need to use (identical to the ``filename`` value you have used when creating the request in the :ref:`create method <upgrade-api-create-method>`.)
-* ``request_id``: the related upgrade request id (only informative, ,not required for the connection)
-* ``sample_command``: a sample command using the 'sftp' client
-
-You should normally be able to connect using the sample command as is.
-
-You will only have access to the ``shared_file``. No other files will be
-accessible and you will not be able to create new files in your shared
-environment on the SFTP server.
-
-Using the 'sftp' client
-+++++++++++++++++++++++
-
-Once you have successfully connected using your SFTP client, you can upload
-your database dump. Here is a sample session using the 'sftp' client:
-
-::
-
-    $ sftp -P 2200 user_10534@upgrade.odoo.com
-    Connected to upgrade.odoo.com.
-    sftp> put /path/to/openchs.70.cdump openchs.70.cdump
-    Uploading /path/to/openchs.70.cdump to /openchs.70.cdump
-    sftp> ls -l openchs.70.cdump
-    -rw-rw-rw-    0 0        0          849920 Aug 30 15:58 openchs.70.cdump
-
-If your connection is interrupted, you can continue your file transfer using
-the ``-a`` command line switch:
-
-.. code-block:: text
-
-    sftp> put -a /path/to/openchs.70.cdump openchs.70.cdump
-    Resuming upload of /path/to/openchs.70.cdump to /openchs.70.cdump
-
-If you don't want to manually type the command and need to automate your
-database upgrade using a script, you can use a batch file or pipe your commands to 'sftp':
-
-::
-
-  echo "put /path/to/openchs.70.cdump openchs.70.cdump" | sftp -b - -P 2200 user_10534@upgrade.odoo.com
-
-The ``-b`` parameter takes a filename. If the filename is ``-``, it reads the commands from standard input.
-
-
-.. _upgrade-api-process-method:
-
-Asking to process your request
-==============================
-
-This action ask the Upgrade Platform to process your database dump.
-
-The ``process`` method
-----------------------
-
-.. py:function:: https://upgrade.odoo.com/database/v1/process
-
-    Process a database dump
-
-    :param str key: (required) your private key
-    :param str request: (required) your request id
-    :return: request result
-    :rtype: JSON dictionary
-
-The request id and the private key are obtained using the :ref:`create method
-<upgrade-api-create-method>`
-
-The result is a JSON dictionary containing the list of ``failures``, which
-should be empty if everything went fine.
-
-.. rst-class:: setup doc-aside
-
-.. switcher::
-
-    .. code-block:: python
-
-        import requests
-
-        PROCESS_URL = "https://upgrade.odoo.com/database/v1/process"
-
-        fields = dict([
-            ('request', '10534'),
-            ('key', 'Aw7pItGVKFuZ_FOR3U8VFQ=='),
-        ])
-
-        r = requests.get(PROCESS_URL, data=fields)
-        print(r.text)
-
-    .. code-block:: bash
-
-        PROCESS_URL="https://upgrade.odoo.com/database/v1/process"
-        KEY="Aw7pItGVKFuZ_FOR3U8VFQ=="
-        REQUEST_ID="10534"
-        URL_PARAMS="key=${KEY}&request=${REQUEST_ID}"
-        curl -sS "${PROCESS_URL}?${URL_PARAMS}"
-
-.. _upgrade-api-skip-tests:
-
-
-Asking to skip the tests 
-=========================
-
-This action asks the Upgrade Platform to skip the tests for your request.
-If you don't want Odoo to test and validate the migration, you can bypass the testing stage and directly get the migrated dump.
-
-The ``skip_test`` method
-------------------------
-
-.. py:function:: https://upgrade.odoo.com/database/v1/skip_test
-
-    Skip the tests, deliver the upgraded dump, and set the state to 'delivered'
-
-    :param str key: (required) your private key
-    :param str request: (required) your request id
-    :return: request result
-    :rtype: JSON dictionary
-
-The request id and the private key are obtained using the :ref:`create method
-<upgrade-api-create-method>`
-
-The result is a JSON dictionary containing the list of ``failures``, which
-should be empty if everything went fine.
-
-.. rst-class:: setup doc-aside
-
-.. switcher::
-
-    .. code-block:: python
-
-        import requests
-
-        PROCESS_URL = "https://upgrade.odoo.com/database/v1/skip_test"
-
-        fields = dict([
-            ('request', '10534'),
-            ('key', 'Aw7pItGVKFuZ_FOR3U8VFQ=='),
-        ])
-
-        r = requests.get(PROCESS_URL, data=fields)
-        print(r.text)
-
-    .. code-block:: bash
-
-        PROCESS_URL="https://upgrade.odoo.com/database/v1/skip_test"
-        KEY="Aw7pItGVKFuZ_FOR3U8VFQ=="
-        REQUEST_ID="10534"
-        URL_PARAMS="key=${KEY}&request=${REQUEST_ID}"
-        curl -sS "${PROCESS_URL}?${URL_PARAMS}"
-
-.. _upgrade-api-status-method:
-
-Obtaining your request status
-=============================
-
-This action ask the status of your database upgrade request.
-
-The ``status`` method
----------------------
-
-.. py:function:: https://upgrade.odoo.com/database/v1/status
-
-    Ask the status of a database upgrade request
-
-    :param str key: (required) your private key
-    :param str request: (required) your request id
-    :return: request result
-    :rtype: JSON dictionary
-
-The request id and the private key are obtained using the :ref:`create method
-<upgrade-api-create-method>`
-
-The result is a JSON dictionary containing various information about your
-database upgrade request.
-
-.. rst-class:: setup doc-aside
-
-.. switcher::
-
-    .. code-block:: python
-
-        import requests
-
-        PROCESS_URL = "https://upgrade.odoo.com/database/v1/status"
-
-        fields = dict([
-            ('request', '10534'),
-            ('key', 'Aw7pItGVKFuZ_FOR3U8VFQ=='),
-        ])
-
-        r = requests.get(PROCESS_URL, data=fields)
-        print(r.text)
-
-    .. code-block:: bash
-
-        STATUS_URL="https://upgrade.odoo.com/database/v1/status"
-        KEY="Aw7pItGVKFuZ_FOR3U8VFQ=="
-        REQUEST_ID="10534"
-        URL_PARAMS="key=${KEY}&request=${REQUEST_ID}"
-        curl -sS "${STATUS_URL}?${URL_PARAMS}"
-
-Sample output
--------------
-
-The ``request`` key contains various useful information about your request:
-
-``id``
-    the request id
-``key``
-    your private key
-``email``
-    the email address you supplied when creating the request
-``target``
-    the target Odoo version you supplied when creating the request
-``aim``
-    the purpose (test, production) of your database upgrade request you supplied when creating the request
-``filename``
-    the filename you supplied when creating the request
-``timezone``
-    the timezone you supplied when creating the request
-``state``
-    the state of your request
-``issue_stage``
-    the stage of the issue we have create on Odoo main server
-``issue``
-    the id of the issue we have create on Odoo main server
-``status_url``
-    the URL to access your database upgrade request html page
-``notes_url``
-    the URL to get the notes about your database upgrade
-``original_sql_url``
-    the URL used to get your uploaded (not upgraded) database as an SQL stream
-``original_dump_url``
-    the URL used to get your uploaded (not upgraded) database as an archive file
-``upgraded_sql_url``
-    the URL used to get your upgraded database as an SQL stream
-``upgraded_dump_url``
-    the URL used to get your upgraded database as an archive file
-``modules_url``
-    the URL used to get your custom modules
-``filesize``
-    the size of your uploaded database file
-``database_uuid``
-    the Unique ID of your database
-``created_at``
-    the date when you created the request
-``estimated_time``
-    an estimation of the time it takes to upgrade your database
-``processed_at``
-    time when your database upgrade was started
-``elapsed``
-    the time it takes to upgrade your database
-``filestore``
-    your attachments were converted to the filestore
-``customer_message``
-    an important message related to your request
-``database_version``
-    the guessed Odoo version of your uploaded (not upgraded) database
-``postgresql``
-    the guessed Postgresql version of your uploaded (not upgraded) database
-``compressions``
-    the compression methods used by your uploaded database
-
-.. rst-class:: setup doc-aside
-
-.. switcher::
-
-    .. code-block:: json
-
-        {
-          "failures": [],
-          "request": {
-            "id": 10534,
-            "key": "Aw7pItGVKFuZ_FOR3U8VFQ==",
-            "email": "john.doe@example.com",
-            "target": "12.0",
-            "aim": "test",
-            "filename": "db_name.dump",
-            "timezone": null,
-            "state": "draft",
-            "issue_stage": "new",
-            "issue": 648398,
-            "status_url": "https://upgrade.odoo.com/database/eu1/10534/Aw7pItGVKFuZ_FOR3U8VFQ==/status",
-            "notes_url": "https://upgrade.odoo.com/database/eu1/10534/Aw7pItGVKFuZ_FOR3U8VFQ==/upgraded/notes",
-            "original_sql_url": "https://upgrade.odoo.com/database/eu1/10534/Aw7pItGVKFuZ_FOR3U8VFQ==/original/sql",
-            "original_dump_url": "https://upgrade.odoo.com/database/eu1/10534/Aw7pItGVKFuZ_FOR3U8VFQ==/original/archive",
-            "upgraded_sql_url": "https://upgrade.odoo.com/database/eu1/10534/Aw7pItGVKFuZ_FOR3U8VFQ==/upgraded/sql",
-            "upgraded_dump_url": "https://upgrade.odoo.com/database/eu1/10534/Aw7pItGVKFuZ_FOR3U8VFQ==/upgraded/archive",
-            "modules_url": "https://upgrade.odoo.com/database/eu1/10534/Aw7pItGVKFuZ_FOR3U8VFQ==/modules/archive",
-            "filesize": "912.99 Kb",
-            "database_uuid": null,
-            "created_at": "2018-09-09 07:13:49",
-            "estimated_time": null,
-            "processed_at": null,
-            "elapsed": "00:00",
-            "filestore": false,
-            "customer_message": null,
-            "database_version": null,
-            "postgresql": "9.4",
-            "compressions": [
-              "pgdmp_custom",
-              "sql"
-            ]
-          }
-        }
-
-.. _upgrade-api-download-method:
-
-Downloading your database dump
-==============================
-
-Beside downloading your migrated database using the URL provided by the
-:ref:`status method <upgrade-api-status-method>`, you can also use the SFTP
-protocol as described in the :ref:`request_sftp_access method
-<upgrade-api-request-sftp-access-method>`
-
-The difference is that you'll only be able to download the migrated database. No
-uploading will be possible.
-
-Your database upgrade request should be in the ``done`` state.
-
-Once you have successfully connected using your SFTP client, you can download
-your database dump. Here is a sample session using the 'sftp' client:
-
-::
-
-    $ sftp -P 2200 user_10534@upgrade.odoo.com
-    Connected to upgrade.odoo.com.
-    sftp> get upgraded_openchs.70.cdump /path/to/upgraded_openchs.70.cdump
-    Downloading /upgraded_openchs.70.cdump to /path/to/upgraded_openchs.70.cdump
-

content/developer/misc/other/guidelines.rst

@@ -71,10 +71,11 @@ models.
     |   |-- plant_order.py (another main model)
     |   |-- res_partner.py (inherited Odoo model)
 
-Concerning *security* and access rights and rules two main files should be used.
-First one is the definition of access rights done in a ``ir.model.access.csv``
-file. User groups are defined in ``<module>_groups.xml``. Access rules are
-defined in ``<model>_security.xml``.
+Concerning *security*, three main files should be used:
+
+- First one is the definition of access rights done in a :file:`ir.model.access.csv` file.
+- User groups are defined in :file:`<module>_groups.xml`.
+- Record rules are defined in :file:`<model>_security.xml`.
 
 .. code-block:: text
 

content/developer/reference/addons/data.rst

@@ -7,7 +7,7 @@ Data Files
 
 Odoo is greatly data-driven, and a big part of modules definition is thus
 the definition of the various records it manages: UI (menus and views),
-security (access rights and access rules), reports and plain data are all
+security (access rights and record rules), reports and plain data are all
 defined via records.
 
 Structure

content/developer/reference/addons/module.rst

@@ -90,17 +90,24 @@ Available manifest fields are:
 ``demo`` (``list(str)``)
     List of data files which are only installed or updated in *demonstration
     mode*
-``auto_install`` (``bool``, default: ``False``)
+``auto_install`` (``bool`` or ``list(str)``, default: ``False``)
     If ``True``, this module will automatically be installed if all of its
     dependencies are installed.
 
-    It is generally used for "link modules" implementing synergic integration
+    It is generally used for "link modules" implementing synergetic integration
     between two otherwise independent modules.
 
     For instance ``sale_crm`` depends on both ``sale`` and ``crm`` and is set
     to ``auto_install``. When both ``sale`` and ``crm`` are installed, it
     automatically adds CRM campaigns tracking to sale orders without either
-    ``sale`` or ``crm`` being aware of one another
+    ``sale`` or ``crm`` being aware of one another.
+
+    If it is a list, it must contain a subset of the dependencies. This module will automatically be
+    installed as soon as all the dependencies in the subset are installed. The remaining
+    dependencies will be automatically installed as well. If the list is empty, this module will
+    always be automatically installed regardless of its dependencies and these will be installed as
+    well.
+
 ``external_dependencies`` (``dict(key=list(str))``)
     A dictionary containing python and/or binary dependencies.
 
@@ -145,7 +152,7 @@ Available manifest fields are:
     These hooks should only be used when setup/cleanup required for this module
     is either extremely difficult or impossible through the api.
 ``active`` (``bool``)
-    This indicates whether this module must install automatically or not.
+    Deprecated. Replaced by ``auto_install``.
 
 .. _semantic versioning: https://semver.org
 .. _existing categories:

content/developer/reference/addons/security.rst

@@ -79,14 +79,14 @@ will have all three of create, read, and update.
 
 .. _reference/security/rules:
 
-Access Rules
+Record Rules
 ============
 
 Record rules are *conditions* which must be satisfied in order for an operation
 to be allowed. Record rules are evaluated record-by-record, following access
 rights.
 
-Access rules are default-allow: if access rights grant access and no rule
+Record rules are default-allow: if access rights grant access and no rule
 applies to the operation and model for the user, the access is granted.
 
 .. class:: ir.rule

content/developer/reference/addons/testing.rst

@@ -120,13 +120,15 @@ Subclasses of :class:`odoo.tests.common.BaseCase` (usually through
 :class:`~odoo.tests.common.TransactionCase`,
 :class:`~odoo.tests.common.SavepointCase` or
 :class:`~odoo.tests.common.HttpCase`) are automatically tagged with
-``standard``, ``at_install`` and their source module's name by default.
+``standard`` and ``at_install`` by default.
 
 Invocation
 ^^^^^^^^^^
 
 :option:`--test-tags <odoo-bin --test-tags>` can be used to select/filter tests
-to run on the command-line.
+to run on the command-line. It implies :option:`--test-enable <odoo-bin --test-enable>`,
+so it's not necessary to specify :option:`--test-enable <odoo-bin --test-enable>`
+when using :option:`--test-tags <odoo-bin --test-tags>`.
 
 This option defaults to ``+standard`` meaning tests tagged ``standard``
 (explicitly or implicitly) will be run by default when starting Odoo
@@ -157,7 +159,7 @@ have to be selected explicitly:
 
 .. code-block:: console
 
-    $ odoo-bin --test-enable --test-tags nice
+    $ odoo-bin --test-tags nice
 
 Note that only the tests tagged ``nice`` are going to be executed. To run
 *both* ``nice`` and ``standard`` tests, provide multiple values to
@@ -166,10 +168,10 @@ are *additive* (you're selecting all tests with *any* of the specified tags)
 
 .. code-block:: console
 
-    $ odoo-bin --test-enable --test-tags nice,standard
+    $ odoo-bin --test-tags nice,standard
 
 The config switch parameter also accepts the ``+`` and ``-`` prefixes. The
-``+`` prefix is implied and therefore, totaly optional. The ``-`` (minus)
+``+`` prefix is implied and therefore, totally optional. The ``-`` (minus)
 prefix is made to deselect tests tagged with the prefixed tags, even if they
 are selected by other specified tags e.g. if there are ``standard`` tests which
 are also tagged as ``slow`` you can run all standard tests *except* the slow
@@ -177,7 +179,7 @@ ones:
 
 .. code-block:: console
 
-    $ odoo-bin --test-enable --test-tags 'standard,-slow'
+    $ odoo-bin --test-tags 'standard,-slow'
 
 When you write a test that does not inherit from the
 :class:`~odoo.tests.common.BaseCase`, this test will not have the default tags,
@@ -194,6 +196,36 @@ they're not going to get run:
     class SmallTest(unittest.TestCase):
         ...
 
+Besides tags you can also specify specific modules, classes or functions to
+test. The full syntax of the format accepted by :option:`--test-tags <odoo-bin --test-tags>`
+is:
+
+.. code-block::
+
+    [-][tag][/module][:class][.method]
+
+So if you want to test the `stock_account` module, you can use:
+
+    .. code-block:: console
+
+        $ odoo-bin --test-tags /stock_account
+
+If you want to test a specific function with a unique name, it can be specified
+directly:
+
+    .. code-block:: console
+
+        $ odoo-bin --test-tags .test_supplier_invoice_forwarded_by_internal_user_without_supplier
+
+This is equivalent to
+
+    .. code-block:: console
+
+        $ odoo-bin --test-tags /account:TestAccountIncomingSupplierInvoice.test_supplier_invoice_forwarded_by_internal_user_without_supplier
+
+if the name of the test is unambiguous. Multiple modules, classes and functions
+can be specified at once separated by a `,` like with regular tags.
+
 .. _reference/testing/tags:
 
 Special tags
@@ -213,43 +245,36 @@ Special tags
   Note that this is *not exclusive* with ``at_install``, however since you
   will generally not want both ``post_install`` is usually paired with
   ``-at_install`` when tagging a test class.
-- *module_name*: Odoo tests classes extending
-  :class:`~odoo.tests.common.BaseCase` are implicitly tagged with the
-  technical name of their module. This allows easily selecting or excluding
-  specific modules when testing e.g. if you want to only run tests from
-  ``stock_account``:
-
-  .. code-block:: console
-
-      $ odoo-bin --test-enable --test-tags stock_account
 
 Examples
 ^^^^^^^^
 
 .. important::
 
-    Tests will be executed only in the installed or updated modules.  So
-    modules have to be selected with the :option:`-u <odoo-bin -u>` or
-    :option:`-i <odoo-bin -i>` switches.  For simplicity, those switches are
+    Tests will be executed only in installed modules. If you're starting from
+    a clean database, you'll need to install the modules with the
+    :option:`-i <odoo-bin -i>` switch at least once. After that it's no longer
+    needed, unless you need to upgrade the module, in which case
+    :option:`-u <odoo-bin -u>` can be used. For simplicity, those switches are
     not specified in the examples below.
 
 Run only the tests from the sale module:
 
 .. code-block:: console
 
-    $ odoo-bin --test-enable --test-tags sale
+    $ odoo-bin --test-tags /sale
 
 Run the tests from the sale module but not the ones tagged as slow:
 
 .. code-block:: console
 
-    $ odoo-bin --test-enable --test-tags 'sale,-slow'
+    $ odoo-bin --test-tags '/sale,-slow'
 
 Run only the tests from stock or tagged as slow:
 
 .. code-block:: console
 
-    $ odoo-bin --test-enable --test-tags '-standard, slow, stock'
+    $ odoo-bin --test-tags '-standard, slow, /stock'
 
 .. note:: ``-standard`` is implicit (not required), and present for clarity
 

content/developer/reference/javascript/qweb.rst

@@ -559,7 +559,7 @@ The javascript QWeb implementation provides a few debugging hooks:
     triggers a debugger breakpoint during template rendering::
 
         <t t-if="a_test">
-            <t t-debug="">
+            <t t-debug=""/>
         </t>
 
     will stop execution if debugging is active (exact condition depend on the

content/legal/terms/i18n/enterprise_fr.rst

@@ -23,6 +23,7 @@ Odoo Enterprise Subscription Agreement (FR)
 .. v9b: clarification that maintenance is opt-out + name of `cloc` command (+ paragraph 5.1 was partially outdated in FR)
 .. v9c: minor wording changes, tuned User definition, + copyright guarantee (re-application of v8a changes
         on all branches)
+.. v9c2: minor simplification in FR wording
 
 En vous abonnant aux services de Odoo Enterprise (les "Services") fournis par Odoo SA et ses filiales
 (collectivement, "Odoo SA") en relation avec Odoo Enterprise Edition ou Odoo Community Edition
@@ -573,7 +574,7 @@ y compris, mais sans s'y limiter, la perte de revenus, perte de profits, perte d
 perte commerciale ou toute autre perte financière, les coûts relatifs à l'arrêt ou au retard,
 la perte ou altération des données, découlant ou en relation avec le présent Contrat, quelle que
 soit la forme de l'action, qu'elle soit fondée sur une obligation contractuelle, délictuelle
-(y compris la stricte négligence) ou fondée sur toute autre règle de droit ou d'équité,
+ou fondée sur toute autre règle de droit ou d'équité,
 même si la partie ou ses filiales ont été informées du risque de tels dommages, ou si le
 recours proposé par la partie ou ses filiales n'atteint pas son but essentiel.
 

content/legal/terms/i18n/terms_of_sale_fr.rst

@@ -4,7 +4,7 @@
 Conditions Générales de Vente
 =============================
 
-.. note:: Dernière modification: 5 mai 2017.
+.. note:: Dernière modification: 20 octobre 2021.
 
 Ces conditions régissent la vente de produits et services entre
 Odoo S.A. et ses filiales (collectivement, "Odoo S.A.") et le client.
@@ -49,7 +49,10 @@ conformément à leur législation interne. La retenue à la source sera réglé
 le client, auprès de l'administration fiscale. En aucun cas, Odoo S.A. ne sera
 impliquée dans les coûts liés à la législation du pays. Le montant de la facture
 est donc dû à Odoo S.A. dans son intégralité et n’inclus pas les coûts relatifs
-à la législation du pays où se trouve le client.
+à la législation du pays où se trouve le client. Pour les clients implantés dans
+plusieurs pays, les prix applicables seront toujours basés sur l'implantation
+géographique ayant la liste de prix la plus élevée, sauf stipulation contraire
+par écrit au moment de la commande.
 
 Odoo S.A. s'engage à faire ses meilleurs efforts en vue de fournir en temps
 utile des services performants. Toutefois, aucune de ses obligations ne peut

content/legal/terms/terms_of_sale.rst

@@ -4,7 +4,7 @@
 General Terms of Sale
 =====================
 
-.. note:: Last revision: May 5, 2017.
+.. note:: Last revision: October 20, 2021.
 
 These General Terms of Sale govern the sale of products and services by
 Odoo S.A. and its affiliates (collectively, "Odoo S.A.") to the client.
@@ -39,7 +39,9 @@ paid by the client to the tax authorities. Under no circumstances can Odoo S.A.
 become involved in costs related to a country's legislation. The amount of the
 invoice will therefore be due to Odoo S.A. in its entirety and does not include
 any costs relating to the legislation of the country in which the client is
-located.
+located. For clients with a global presence, the applicable pricing is always
+based on the client location with the highest price list, unless otherwise
+specified in writing at the time of purchase.
 
 Odoo S.A. undertakes to do its best to supply services in due time in accordance
 with the agreed timeframes. However, none of its obligations can be considered

locale/da/LC_MESSAGES/applications.po

@@ -1,19 +1,15 @@
 # SOME DESCRIPTIVE TITLE.
-# Copyright (C) 2015-TODAY, Odoo S.A.
+# Copyright (C) Odoo S.A.
 # This file is distributed under the same license as the Odoo package.
 # FIRST AUTHOR <EMAIL@ADDRESS>, YEAR.
 # 
-# Translators:
-# Sanne Kristensen <sanne@vkdata.dk>, 2020
-# 
 #, fuzzy
 msgid ""
 msgstr ""
 "Project-Id-Version: Odoo 14.0\n"
 "Report-Msgid-Bugs-To: \n"
-"POT-Creation-Date: 2021-02-04 11:02+0100\n"
+"POT-Creation-Date: 2021-08-10 09:10+0000\n"
 "PO-Revision-Date: 2020-09-22 14:40+0000\n"
-"Last-Translator: Sanne Kristensen <sanne@vkdata.dk>, 2020\n"
 "Language-Team: Danish (https://www.transifex.com/odoo/teams/41243/da/)\n"
 "MIME-Version: 1.0\n"
 "Content-Type: text/plain; charset=UTF-8\n"
@@ -21,6 +17,10 @@ msgstr ""
 "Language: da\n"
 "Plural-Forms: nplurals=2; plural=(n != 1);\n"
 
-#: ../../applications.rst:3
-msgid "Applications"
-msgstr "Applikation"
+#: ../../content/applications.rst:9
+msgid "User Docs"
+msgstr ""
+
+#: ../../content/applications.rst:11
+msgid "Discover our user guides and configuration tutorials per application."
+msgstr ""

locale/da/LC_MESSAGES/index.po

@@ -8,7 +8,7 @@ msgid ""
 msgstr ""
 "Project-Id-Version: Odoo 14.0\n"
 "Report-Msgid-Bugs-To: \n"
-"POT-Creation-Date: 2021-05-18 07:12+0200\n"
+"POT-Creation-Date: 2021-06-14 13:29+0200\n"
 "PO-Revision-Date: 2020-09-22 14:40+0000\n"
 "Language-Team: Danish (https://www.transifex.com/odoo/teams/41243/da/)\n"
 "MIME-Version: 1.0\n"
@@ -17,6 +17,6 @@ msgstr ""
 "Language: da\n"
 "Plural-Forms: nplurals=2; plural=(n != 1);\n"
 
-#: ../../content/index.rst:3
+#: ../../content/index.rst:5
 msgid "Odoo Documentation"
 msgstr ""

locale/da/LC_MESSAGES/marketing.po

@@ -5,18 +5,18 @@
 # 
 # Translators:
 # Martin Trigaux, 2021
-# Pernille Kristensen <pernillekristensen1994@gmail.com>, 2021
 # Sanne Kristensen <sanne@vkdata.dk>, 2021
 # Mads Søndergaard, 2021
+# Pernille Kristensen <pernillekristensen1994@gmail.com>, 2021
 # 
 #, fuzzy
 msgid ""
 msgstr ""
 "Project-Id-Version: Odoo 14.0\n"
 "Report-Msgid-Bugs-To: \n"
-"POT-Creation-Date: 2021-06-14 13:29+0200\n"
+"POT-Creation-Date: 2021-08-10 09:10+0000\n"
 "PO-Revision-Date: 2021-05-18 05:18+0000\n"
-"Last-Translator: Mads Søndergaard, 2021\n"
+"Last-Translator: Pernille Kristensen <pernillekristensen1994@gmail.com>, 2021\n"
 "Language-Team: Danish (https://www.transifex.com/odoo/teams/41243/da/)\n"
 "MIME-Version: 1.0\n"
 "Content-Type: text/plain; charset=UTF-8\n"
@@ -28,10 +28,16 @@ msgstr ""
 msgid "Marketing"
 msgstr "Markedsføring"
 
-#: ../../content/applications/marketing/marketing_automation.rst:5
+#: ../../content/applications/marketing/marketing_automation.rst:8
 msgid "Marketing Automation"
 msgstr "Marketing automatisering"
 
+#: ../../content/applications/marketing/marketing_automation.rst:11
+#: ../../content/applications/marketing/sms_marketing.rst:11
+msgid ""
+"`Odoo Tutorials: Marketing <https://www.odoo.com/slides/marketing-27>`_"
+msgstr ""
+
 #: ../../content/applications/marketing/marketing_automation/advanced.rst:5
 msgid "Advanced"
 msgstr "Avanceret"
@@ -56,14 +62,6 @@ msgstr ""
 msgid "Let’s consider the example below:"
 msgstr ""
 
-#: ../../content/applications/marketing/marketing_automation/advanced/understanding_metrics.rstNone
-#: ../../content/applications/marketing/marketing_automation/advanced/understanding_metrics.rstNone
-#: ../../content/applications/marketing/marketing_automation/advanced/understanding_metrics.rstNone
-#: ../../content/applications/marketing/marketing_automation/advanced/understanding_metrics.rst:0
-#: ../../content/applications/marketing/marketing_automation/advanced/understanding_metrics.rstNone
-msgid "Metrics in Odoo Marketing Automation"
-msgstr ""
-
 #: ../../content/applications/marketing/marketing_automation/advanced/understanding_metrics.rst:19
 msgid ""
 "The *Target* - business object - is *Lead/Opportunity* and was narrowed down"
@@ -144,7 +142,7 @@ msgid ""
 "the beginning (parent action)."
 msgstr ""
 
-#: ../../content/applications/marketing/sms_marketing.rst:5
+#: ../../content/applications/marketing/sms_marketing.rst:8
 msgid "SMS Marketing"
 msgstr "SMS Marketing"
 
@@ -180,10 +178,6 @@ msgid ""
 " that includes the following characters:"
 msgstr ""
 
-#: ../../content/applications/marketing/sms_marketing/pricing/pricing_and_faq.rstNone
-msgid "GSM7 in Odoo SMS Marketing"
-msgstr ""
-
 #: ../../content/applications/marketing/sms_marketing/pricing/pricing_and_faq.rst:23
 msgid ""
 "**UNICODE** is the format applied if a special character, that *is not* in "
@@ -211,8 +205,8 @@ msgstr ""
 
 #: ../../content/applications/marketing/sms_marketing/pricing/pricing_and_faq.rst:37
 msgid ""
-"To see the **price per country, please consult**: `Odoo SMS - FAQ <https"
-"://iap-services.odoo.com/iap/sms/pricing#sms_faq_01>`_."
+"To see the **price per country, please consult**: `Odoo SMS - FAQ "
+"<https://iap-services.odoo.com/iap/sms/pricing#sms_faq_01>`_."
 msgstr ""
 
 #: ../../content/applications/marketing/sms_marketing/pricing/pricing_and_faq.rst:39
@@ -221,12 +215,6 @@ msgid ""
 "your database."
 msgstr ""
 
-#: ../../content/applications/marketing/sms_marketing/pricing/pricing_and_faq.rstNone
-#: ../../content/applications/marketing/sms_marketing/pricing/pricing_and_faq.rstNone
-#: ../../content/applications/marketing/sms_marketing/pricing/pricing_and_faq.rstNone
-msgid "SMS pricing and FAQ Odoo SMS Marketing"
-msgstr ""
-
 #: ../../content/applications/marketing/sms_marketing/pricing/pricing_and_faq.rst:49
 msgid "How do I buy credits?"
 msgstr ""
@@ -369,19 +357,23 @@ msgid ""
 "`here <https://www.odoo.com/pricing-packs>`_."
 msgstr ""
 
-#: ../../content/applications/marketing/survey.rst:5
-msgid "Survey"
-msgstr "Undersøgelse"
+#: ../../content/applications/marketing/surveys.rst:8
+msgid "Surveys"
+msgstr "Undersøgelser"
 
-#: ../../content/applications/marketing/survey/overview.rst:5
+#: ../../content/applications/marketing/surveys.rst:11
+msgid "`Odoo Tutorials: Surveys <https://www.odoo.com/slides/surveys-62>`_"
+msgstr ""
+
+#: ../../content/applications/marketing/surveys/overview.rst:5
 msgid "Overview"
 msgstr "Oversigt"
 
-#: ../../content/applications/marketing/survey/overview/create.rst:3
+#: ../../content/applications/marketing/surveys/overview/create.rst:3
 msgid "Get Started with Surveys"
 msgstr ""
 
-#: ../../content/applications/marketing/survey/overview/create.rst:5
+#: ../../content/applications/marketing/surveys/overview/create.rst:5
 msgid ""
 "Surveys can be used for a range of purposes that can go from collecting "
 "customer feedback, evaluate the success of an event, measure how pleased "
@@ -390,11 +382,11 @@ msgid ""
 "market is thinking."
 msgstr ""
 
-#: ../../content/applications/marketing/survey/overview/create.rst:11
+#: ../../content/applications/marketing/surveys/overview/create.rst:11
 msgid "Get started"
 msgstr "Kom igang"
 
-#: ../../content/applications/marketing/survey/overview/create.rst:13
+#: ../../content/applications/marketing/surveys/overview/create.rst:13
 msgid ""
 "When creating your survey, choose a *Title* and *Category*. The *Category* "
 "field is used to know in which context the survey is being conducted, as "
@@ -402,20 +394,15 @@ msgid ""
 "recruitment, certification, or employee appraisal."
 msgstr ""
 
-#: ../../content/applications/marketing/survey/overview/create.rstNone
-msgid ""
-"Form view of a survey with a title and category being chosen in Odoo Surveys"
-msgstr ""
-
-#: ../../content/applications/marketing/survey/overview/create.rst:22
+#: ../../content/applications/marketing/surveys/overview/create.rst:22
 msgid "Tab: Questions"
 msgstr ""
 
-#: ../../content/applications/marketing/survey/overview/create.rst:24
+#: ../../content/applications/marketing/surveys/overview/create.rst:24
 msgid "Add sections and questions by clicking on the respective links."
 msgstr ""
 
-#: ../../content/applications/marketing/survey/overview/create.rst:27
+#: ../../content/applications/marketing/surveys/overview/create.rst:27
 msgid ""
 "On the *Sections and Questions* form, once the question type is chosen and "
 "the answer added, under the tab *Options*, enable *Mandatory Answer*, and "
@@ -423,19 +410,19 @@ msgid ""
 "without answering the respective question."
 msgstr ""
 
-#: ../../content/applications/marketing/survey/overview/create.rst:29
+#: ../../content/applications/marketing/surveys/overview/create.rst:29
 msgid ""
 "Depending on the *Question Type*, the tab *Options* aggregates extra and "
 "different possibilities. Examples:"
 msgstr ""
 
-#: ../../content/applications/marketing/survey/overview/create.rst:31
+#: ../../content/applications/marketing/surveys/overview/create.rst:31
 msgid ""
 "*Single Line Text Box* - can choose a minimum and maximum text length "
 "(number of characters - spaces do not count), and its error message."
 msgstr ""
 
-#: ../../content/applications/marketing/survey/overview/create.rst:33
+#: ../../content/applications/marketing/surveys/overview/create.rst:33
 msgid ""
 "*Multiple choice: multiple answers allowed*: choose between radio buttons or"
 " a dropdown menu list, and if you would like to have a comment field. If the"
@@ -444,110 +431,86 @@ msgid ""
 "with which a text type field is displayed."
 msgstr ""
 
-#: ../../content/applications/marketing/survey/overview/create.rst:37
+#: ../../content/applications/marketing/surveys/overview/create.rst:37
 msgid ""
 "*Matrix Type*: choose if you would like to have one or multiple choices per "
 "row."
 msgstr ""
 
-#: ../../content/applications/marketing/survey/overview/create.rstNone
-msgid "Sections and questions view of a survey in Odoo Surveys"
-msgstr ""
-
-#: ../../content/applications/marketing/survey/overview/create.rst:44
+#: ../../content/applications/marketing/surveys/overview/create.rst:44
 msgid "Tab: Description"
 msgstr ""
 
-#: ../../content/applications/marketing/survey/overview/create.rst:46
+#: ../../content/applications/marketing/surveys/overview/create.rst:46
 msgid ""
 "Write a *Description* to be displayed under the title of the survey's "
 "homepage."
 msgstr ""
 
-#: ../../content/applications/marketing/survey/overview/create.rstNone
-msgid ""
-"Frontend of a survey showing the title and description of a survey for Odoo "
-"Surveys"
-msgstr ""
-
-#: ../../content/applications/marketing/survey/overview/create.rst:53
+#: ../../content/applications/marketing/surveys/overview/create.rst:53
 msgid "Click on *Edit* to personalize your pages with the website builder."
 msgstr ""
 
-#: ../../content/applications/marketing/survey/overview/create.rst:56
+#: ../../content/applications/marketing/surveys/overview/create.rst:56
 msgid "Tab: Options"
 msgstr ""
 
-#: ../../content/applications/marketing/survey/overview/create.rst:58
+#: ../../content/applications/marketing/surveys/overview/create.rst:58
 msgid ""
 "Under the tab *Options*, choose the *Layout* of your questions. If choosing "
 "*One page per section* or *One page per question*, an option *Back Button* "
 "becomes available, which allows the user to go back pages."
 msgstr ""
 
-#: ../../content/applications/marketing/survey/overview/create.rstNone
-msgid ""
-"Form view of a survey emphasizing the layout feature under options in Odoo "
-"Surveys"
-msgstr ""
-
-#: ../../content/applications/marketing/survey/overview/create.rst:67
+#: ../../content/applications/marketing/surveys/overview/create.rst:67
 msgid "Test and share the survey"
 msgstr ""
 
-#: ../../content/applications/marketing/survey/overview/create.rst:70
+#: ../../content/applications/marketing/surveys/overview/create.rst:70
 msgid ""
 "Once your Survey is ready, *Test* it to avoid *Sharing* it with potential "
 "errors. As answers get collected, click on *Answers* to access all the "
 "details of the respondent and his answers."
 msgstr ""
 
-#: ../../content/applications/marketing/survey/overview/create.rst:72
+#: ../../content/applications/marketing/surveys/overview/create.rst:72
 msgid ""
 "By default, a filter *Except Test Entries* is applied to keep the list of "
 "entries clean with only real participants."
 msgstr ""
 
-#: ../../content/applications/marketing/survey/overview/create.rstNone
-msgid "View list of the participations of a survey in Odoo Surveys"
-msgstr ""
-
-#: ../../content/applications/marketing/survey/overview/create.rst:79
+#: ../../content/applications/marketing/surveys/overview/create.rst:79
 msgid ""
 "Another way to access detailed answers is by going to "
 ":menuselection:`Participations --> Participations`."
 msgstr ""
 
-#: ../../content/applications/marketing/survey/overview/create.rst:80
+#: ../../content/applications/marketing/surveys/overview/create.rst:80
 msgid "Click on *See results* to be redirected to an analytical page."
 msgstr ""
 
-#: ../../content/applications/marketing/survey/overview/create.rstNone
-msgid "View of an analytical page for Odoo Surveys"
-msgstr ""
-
-#: ../../content/applications/marketing/survey/overview/create.rst:87
-#: ../../content/applications/marketing/survey/overview/time_random.rst:34
+#: ../../content/applications/marketing/surveys/overview/create.rst:87
+#: ../../content/applications/marketing/surveys/overview/time_random.rst:34
 msgid ":doc:`scoring`"
 msgstr ""
 
-#: ../../content/applications/marketing/survey/overview/create.rst:88
-#: ../../content/applications/marketing/survey/overview/scoring.rst:35
+#: ../../content/applications/marketing/surveys/overview/create.rst:88
+#: ../../content/applications/marketing/surveys/overview/scoring.rst:35
 msgid ":doc:`time_random`"
 msgstr ""
 
-#: ../../content/applications/marketing/survey/overview/scoring.rst:3
+#: ../../content/applications/marketing/surveys/overview/scoring.rst:3
 msgid "Scoring Surveys"
 msgstr ""
 
-#: ../../content/applications/marketing/survey/overview/scoring.rst:5
+#: ../../content/applications/marketing/surveys/overview/scoring.rst:5
 msgid ""
 "To measure your respondent’s performance, knowledge of a subject, or overall"
 " satisfaction, attach points to the answers of specific questions. The "
 "points are summed up to give your respondent a final score."
 msgstr ""
 
-#: ../../content/applications/marketing/survey/overview/scoring.rst:9
+#: ../../content/applications/marketing/surveys/overview/scoring.rst:9
 msgid ""
 "On your survey’s form, click on *Add a question* and, under the tab "
 "*Options*, choose between *Scoring with answers at the end* or *Scoring "
@@ -555,11 +518,7 @@ msgid ""
 "answer and score."
 msgstr ""
 
-#: ../../content/applications/marketing/survey/overview/scoring.rstNone
-msgid "Form view of a survey showing a list of answers in Odoo Surveys"
-msgstr ""
-
-#: ../../content/applications/marketing/survey/overview/scoring.rst:17
+#: ../../content/applications/marketing/surveys/overview/scoring.rst:17
 msgid ""
 "Set the percentage score the user needs to achieve to have successfully "
 "taken the survey. If enabling *Certificate*, choose its template. The "
@@ -567,13 +526,7 @@ msgid ""
 "finish it."
 msgstr ""
 
-#: ../../content/applications/marketing/survey/overview/scoring.rstNone
-msgid ""
-"Form view of a survey emphasizing the scoring and candidates section in Odoo"
-" Surveys"
-msgstr ""
-
-#: ../../content/applications/marketing/survey/overview/scoring.rst:25
+#: ../../content/applications/marketing/surveys/overview/scoring.rst:25
 msgid ""
 "Enable *Login required* to be able to *Give Badges*. Badges are related to "
 "the eLearning section of your website. Besides the logged-in user, visitors "
@@ -581,21 +534,15 @@ msgid ""
 "badges."
 msgstr ""
 
-#: ../../content/applications/marketing/survey/overview/scoring.rstNone
-msgid ""
-"View of the courses tab emphasizing the latest achievements section on the website for\n"
-"Odoo Surveys"
-msgstr ""
-
-#: ../../content/applications/marketing/survey/overview/time_random.rst:3
+#: ../../content/applications/marketing/surveys/overview/time_random.rst:3
 msgid "Time and Randomize Questions"
 msgstr ""
 
-#: ../../content/applications/marketing/survey/overview/time_random.rst:6
+#: ../../content/applications/marketing/surveys/overview/time_random.rst:6
 msgid "Time Limit"
 msgstr "Tidsbegrænsning"
 
-#: ../../content/applications/marketing/survey/overview/time_random.rst:10
+#: ../../content/applications/marketing/surveys/overview/time_random.rst:10
 msgid ""
 "On timed surveys, respondents need to complete the survey within a certain "
 "period of time. It can be used to ensure that all respondents get the same "
@@ -603,42 +550,31 @@ msgid ""
 " looking at external resources."
 msgstr ""
 
-#: ../../content/applications/marketing/survey/overview/time_random.rst:11
+#: ../../content/applications/marketing/surveys/overview/time_random.rst:11
 msgid "Set the *Time limit* under the tab *Options*."
 msgstr ""
 
-#: ../../content/applications/marketing/survey/overview/time_random.rstNone
-msgid ""
-"View of a survey form emphasizing the time limit feature in Odoo Surveys"
-msgstr ""
-
-#: ../../content/applications/marketing/survey/overview/time_random.rst:17
+#: ../../content/applications/marketing/surveys/overview/time_random.rst:17
 msgid ""
 "A timer is shown on the pages so the user can keep track of the remaining "
 "time. Surveys not \\ submitted by the *Time limit* do not have their answers"
 " saved."
 msgstr ""
 
-#: ../../content/applications/marketing/survey/overview/time_random.rst:21
+#: ../../content/applications/marketing/surveys/overview/time_random.rst:21
 msgid "Selection"
 msgstr "Udvælgelse"
 
-#: ../../content/applications/marketing/survey/overview/time_random.rst:25
+#: ../../content/applications/marketing/surveys/overview/time_random.rst:25
 msgid ""
 "When you randomize a survey, you allow for the questions to be shuffled in a"
 " random order every time someone opens the questionnaire. This can be useful"
 " to avoid having respondents looking at each others' answers."
 msgstr ""
 
-#: ../../content/applications/marketing/survey/overview/time_random.rst:27
+#: ../../content/applications/marketing/surveys/overview/time_random.rst:27
 msgid ""
 "To do so, under the tab *Options*, enable *Randomized per section*. Now, "
 "under the tab *Questions*, set how many of the questions in that section "
 "should be taken into account during the shuffling."
 msgstr ""
-
-#: ../../content/applications/marketing/survey/overview/time_random.rstNone
-msgid ""
-"View of a survey form emphasizing the random questions count column in Odoo "
-"Surveys"
-msgstr ""

locale/da/LC_MESSAGES/productivity.po

@@ -9,16 +9,16 @@
 # Sanne Kristensen <sanne@vkdata.dk>, 2021
 # lhmflexerp <lhm@flexerp.dk>, 2021
 # Mads Søndergaard, 2021
-# Mads Søndergaard <mads@vkdata.dk>, 2021
+# Mads Søndergaard, 2021
 # 
 #, fuzzy
 msgid ""
 msgstr ""
 "Project-Id-Version: Odoo 14.0\n"
 "Report-Msgid-Bugs-To: \n"
-"POT-Creation-Date: 2021-06-14 13:29+0200\n"
+"POT-Creation-Date: 2021-08-10 09:10+0000\n"
 "PO-Revision-Date: 2021-05-18 05:18+0000\n"
-"Last-Translator: Mads Søndergaard <mads@vkdata.dk>, 2021\n"
+"Last-Translator: Mads Søndergaard, 2021\n"
 "Language-Team: Danish (https://www.transifex.com/odoo/teams/41243/da/)\n"
 "MIME-Version: 1.0\n"
 "Content-Type: text/plain; charset=UTF-8\n"
@@ -30,7 +30,7 @@ msgstr ""
 msgid "Productivity"
 msgstr "Produktivitet"
 
-#: ../../content/applications/productivity/discuss.rst:5
+#: ../../content/applications/productivity/discuss.rst:8
 msgid "Discuss"
 msgstr "Beskeder"
 
@@ -335,8 +335,8 @@ msgstr ""
 
 #: ../../content/applications/productivity/discuss/advanced/email_servers.rst:176
 msgid ""
-"Projects (to create new Tasks in `Odoo Project <https://www.odoo.com/page"
-"/project-management>`__),"
+"Projects (to create new Tasks in `Odoo Project "
+"<https://www.odoo.com/page/project-management>`__),"
 msgstr ""
 
 #: ../../content/applications/productivity/discuss/advanced/email_servers.rst:178
@@ -490,10 +490,6 @@ msgid ""
 "job applicants."
 msgstr ""
 
-#: ../../content/applications/productivity/discuss/advanced/email_template.rstNone
-msgid "New email template form in Odoo"
-msgstr ""
-
 #: ../../content/applications/productivity/discuss/advanced/email_template.rst:30
 msgid ""
 "Under *Email Configuration*, fields such as *From*, *To (Emails)*, *To "
@@ -523,21 +519,12 @@ msgid ""
 "would like to use."
 msgstr ""
 
-#: ../../content/applications/productivity/discuss/advanced/email_template.rstNone
-msgid ""
-"View of the dynamic placeholder generator tab under a new template in Odoo"
-msgstr ""
-
 #: ../../content/applications/productivity/discuss/advanced/email_template.rst:45
 msgid ""
 "Next, copy the *Placeholder Expression* and paste it in the *Body* of the "
 "email, under the *Content* tab, using - essentially - the *Code View*."
 msgstr ""
 
-#: ../../content/applications/productivity/discuss/advanced/email_template.rstNone
-msgid "View of the body code view under the content tab in Odoo"
-msgstr ""
-
 #: ../../content/applications/productivity/discuss/advanced/email_template.rst:52
 msgid ""
 "Deactivate the *Code View* option by simply clicking on it again, and easily"
@@ -545,10 +532,6 @@ msgid ""
 "sending it."
 msgstr ""
 
-#: ../../content/applications/productivity/discuss/advanced/email_template.rstNone
-msgid "View of the content with the standard body view in Odoo"
-msgstr ""
-
 #: ../../content/applications/productivity/discuss/overview.rst:5
 msgid "Overview"
 msgstr "Oversigt"
@@ -576,10 +559,6 @@ msgid ""
 "to be handled."
 msgstr ""
 
-#: ../../content/applications/productivity/discuss/overview/get_started.rstNone
-msgid "View of the preferences page for Odoo Discuss"
-msgstr ""
-
 #: ../../content/applications/productivity/discuss/overview/get_started.rst:21
 msgid ""
 "By default, the field is set as *Handle by Emails* making messages, notes, "
@@ -591,20 +570,12 @@ msgstr ""
 msgid "Messages can then be *Marked as Todo*, *Replied*, or *Marked as Read*."
 msgstr ""
 
-#: ../../content/applications/productivity/discuss/overview/get_started.rstNone
-msgid "View of an inbox message and its action options in Odoo Discuss"
-msgstr ""
-
 #: ../../content/applications/productivity/discuss/overview/get_started.rst:28
 msgid ""
 "The messages tagged as *Mark as Todo* are also shown in *Starred*, while the"
 " ones *Marked as Read* are moved to *History*."
 msgstr ""
 
-#: ../../content/applications/productivity/discuss/overview/get_started.rstNone
-msgid "View of messages marked as todo in Odoo Discuss"
-msgstr ""
-
 #: ../../content/applications/productivity/discuss/overview/get_started.rst:36
 msgid "Start Chatting"
 msgstr ""
@@ -617,12 +588,6 @@ msgid ""
 " of where you are in Odoo."
 msgstr ""
 
-#: ../../content/applications/productivity/discuss/overview/get_started.rstNone
-msgid ""
-"View of the messages under the messaging menu emphasizing the request for push\n"
-"notifications for Odoo Discuss"
-msgstr ""
-
 #: ../../content/applications/productivity/discuss/overview/get_started.rst:48
 msgid ""
 "To stop receiving desktop notifications, reset the notifications settings of"
@@ -635,12 +600,6 @@ msgid ""
 "*Discuss* and send a *Direct Message*."
 msgstr ""
 
-#: ../../content/applications/productivity/discuss/overview/get_started.rstNone
-msgid ""
-"View of discuss’s panel emphasizing the titles channels and direct messages "
-"in Odoo Discuss"
-msgstr ""
-
 #: ../../content/applications/productivity/discuss/overview/get_started.rst:58
 msgid ""
 "You can also create :doc:`public and private channels <team_communication>`."
@@ -662,10 +621,6 @@ msgid ""
 "through email, depending on his settings."
 msgstr ""
 
-#: ../../content/applications/productivity/discuss/overview/get_started.rstNone
-msgid "View of a couple of chat window messages for Odoo Discuss"
-msgstr ""
-
 #: ../../content/applications/productivity/discuss/overview/get_started.rst:73
 msgid ""
 "When a user is mentioned, the search list (list of names) suggests values "
@@ -702,10 +657,6 @@ msgstr ""
 msgid "Airplane = out of the office"
 msgstr ""
 
-#: ../../content/applications/productivity/discuss/overview/get_started.rstNone
-msgid "View of the contacts’ status for Odoo Discuss"
-msgstr ""
-
 #: ../../content/applications/productivity/discuss/overview/get_started.rst:95
 #: ../../content/applications/productivity/discuss/overview/plan_activities.rst:65
 msgid ":doc:`team_communication`"
@@ -737,11 +688,6 @@ msgid ""
 "*Activities* menu."
 msgstr ""
 
-#: ../../content/applications/productivity/discuss/overview/plan_activities.rstNone
-msgid ""
-"View of crm leads page emphasizing the activities menu for Odoo Discuss"
-msgstr ""
-
 #: ../../content/applications/productivity/discuss/overview/plan_activities.rst:20
 msgid "Plan activities"
 msgstr ""
@@ -752,11 +698,6 @@ msgid ""
 "*Schedule activity*, or through Kanban views."
 msgstr ""
 
-#: ../../content/applications/productivity/discuss/overview/plan_activities.rstNone
-msgid ""
-"View of crm leads and the option to schedule an activity for Odoo Discuss"
-msgstr ""
-
 #: ../../content/applications/productivity/discuss/overview/plan_activities.rst:31
 msgid "Set your activity types"
 msgstr ""
@@ -768,12 +709,6 @@ msgid ""
 ":menuselection:`Settings --> Activity types`."
 msgstr ""
 
-#: ../../content/applications/productivity/discuss/overview/plan_activities.rstNone
-msgid ""
-"View of the settings page emphasizing the menu activity types for Odoo "
-"Discuss"
-msgstr ""
-
 #: ../../content/applications/productivity/discuss/overview/plan_activities.rst:42
 msgid ""
 "If you need to create an activity type with an available calendar, make sure"
@@ -790,24 +725,12 @@ msgid ""
 "*Recommended Next Activities*."
 msgstr ""
 
-#: ../../content/applications/productivity/discuss/overview/plan_activities.rstNone
-msgid ""
-"View of an activity type form emphasizing the field recommended next activities for Odoo\n"
-"Discuss"
-msgstr ""
-
 #: ../../content/applications/productivity/discuss/overview/plan_activities.rst:55
 msgid ""
 "Once the respective activity is completed, select *Done & Schedule Next* and"
 " next steps are suggested to you."
 msgstr ""
 
-#: ../../content/applications/productivity/discuss/overview/plan_activities.rstNone
-msgid ""
-"View of an activity being schedule emphasizing the recommended activities field being\n"
-"shown for Odoo Discuss"
-msgstr ""
-
 #: ../../content/applications/productivity/discuss/overview/plan_activities.rst:64
 #: ../../content/applications/productivity/discuss/overview/team_communication.rst:115
 msgid ":doc:`get_started`"
@@ -835,10 +758,6 @@ msgid ""
 "visible to users invited to it."
 msgstr ""
 
-#: ../../content/applications/productivity/discuss/overview/team_communication.rstNone
-msgid "View of discuss’s sidebar and a channel being created in Odo Discuss"
-msgstr ""
-
 #: ../../content/applications/productivity/discuss/overview/team_communication.rst:21
 msgid ""
 "A public channel is best used when many employees need to access information"
@@ -857,10 +776,6 @@ msgid ""
 " clicking on the *Channel Settings* icon on the sidebar."
 msgstr ""
 
-#: ../../content/applications/productivity/discuss/overview/team_communication.rstNone
-msgid "View of a channel’s settings form in Odoo Discuss"
-msgstr ""
-
 #: ../../content/applications/productivity/discuss/overview/team_communication.rst:36
 msgid "Privacy and Members"
 msgstr ""
@@ -880,12 +795,6 @@ msgid ""
 "*Invite*."
 msgstr ""
 
-#: ../../content/applications/productivity/discuss/overview/team_communication.rstNone
-msgid ""
-"View of Discuss’ sidebar emphasizing the option to invite members in Odoo "
-"Discuss"
-msgstr ""
-
 #: ../../content/applications/productivity/discuss/overview/team_communication.rst:49
 msgid ""
 "For *Selected group of users*, the option *Auto Subscribe Groups* "
@@ -911,10 +820,6 @@ msgid ""
 "messages will need to be approved before being sent."
 msgstr ""
 
-#: ../../content/applications/productivity/discuss/overview/team_communication.rstNone
-msgid "View of a message with a pending moderation status in Odoo Discuss"
-msgstr ""
-
 #: ../../content/applications/productivity/discuss/overview/team_communication.rst:66
 msgid ""
 "Under the *Moderation* tab choose as many moderators as you need, and if you"
@@ -927,22 +832,12 @@ msgid ""
 " to newcomers."
 msgstr ""
 
-#: ../../content/applications/productivity/discuss/overview/team_communication.rstNone
-msgid ""
-"View of a channel’s settings form emphasizing the tab moderation in Odoo "
-"Discuss"
-msgstr ""
-
 #: ../../content/applications/productivity/discuss/overview/team_communication.rst:73
 msgid ""
 "Moderators can: *Accept*, *Reject*, *Discard*, *Always Allow* or *Ban* "
 "messages."
 msgstr ""
 
-#: ../../content/applications/productivity/discuss/overview/team_communication.rstNone
-msgid "View of a message to be moderated in Odoo Discuss"
-msgstr ""
-
 #: ../../content/applications/productivity/discuss/overview/team_communication.rst:80
 msgid ""
 "Members of a mailing channel receive messages through email regardless of "
@@ -955,12 +850,6 @@ msgid ""
 "addresses per moderated channel to auto-ban them from sending messages."
 msgstr ""
 
-#: ../../content/applications/productivity/discuss/overview/team_communication.rstNone
-msgid ""
-"View of a channel’s setting form emphasizing the ban Lists menu in Odoo "
-"Discuss"
-msgstr ""
-
 #: ../../content/applications/productivity/discuss/overview/team_communication.rst:91
 msgid "Quick search bar"
 msgstr ""
@@ -973,12 +862,6 @@ msgid ""
 " and quickly find the one you need."
 msgstr ""
 
-#: ../../content/applications/productivity/discuss/overview/team_communication.rstNone
-msgid ""
-"View of the Discuss’ sidebar emphasizing the quick search bar in Odoo "
-"Discuss"
-msgstr ""
-
 #: ../../content/applications/productivity/discuss/overview/team_communication.rst:103
 msgid "Finding channels"
 msgstr ""
@@ -996,15 +879,11 @@ msgid ""
 "single character."
 msgstr ""
 
-#: ../../content/applications/productivity/discuss/overview/team_communication.rstNone
-msgid "View of a channel being searched through filters in Odoo Discuss"
-msgstr ""
-
 #: ../../content/applications/productivity/discuss/overview/team_communication.rst:116
 msgid ":doc:`plan_activities`"
 msgstr ""
 
-#: ../../content/applications/productivity/iot.rst:5
+#: ../../content/applications/productivity/iot.rst:8
 msgid "Internet of Things (IoT)"
 msgstr "Internet of Things (IoT)"
 
@@ -1087,8 +966,9 @@ msgstr ""
 #: ../../content/applications/productivity/iot/config/connect.rst:60
 msgid ""
 "If you are on Runbot, do not forget to add the -all or -base in the token "
-"(e.g. this token **http://375228-saas-11-5-iot-"
-"f3f920.runbot16.odoo.com\\|4957098401** should become "
+"(e.g. this token "
+"**http://375228-saas-11-5-iot-f3f920.runbot16.odoo.com\\|4957098401** should"
+" become "
 "**http://375228-saas-11-5-iot-f3f920-all.runbot16.odoo.com\\|4957098401**)."
 msgstr ""
 
@@ -1805,13 +1685,10 @@ msgstr ""
 
 #: ../../content/applications/productivity/iot/devices/scale.rst:17
 msgid ""
-"If your scale is `compatibale with Odoo IoT Box <https://www.odoo.com/page"
-"/iot-hardware>`_, there is no need to set up anything because it will be "
-"automatically detected as soon as it is connected."
-msgstr ""
-
-#: ../../content/applications/productivity/iot/devices/scale.rstNone
-msgid "IOT box auto detection."
+"If your scale is `compatibale with Odoo IoT Box "
+"<https://www.odoo.com/page/iot-hardware>`_, there is no need to set up "
+"anything because it will be automatically detected as soon as it is "
+"connected."
 msgstr ""
 
 #: ../../content/applications/productivity/iot/devices/scale.rst:24
@@ -1821,10 +1698,6 @@ msgid ""
 "*drivers list*. Then, click on load drivers."
 msgstr ""
 
-#: ../../content/applications/productivity/iot/devices/scale.rstNone
-msgid "View of the IoT box settings and driver list."
-msgstr ""
-
 #: ../../content/applications/productivity/iot/devices/scale.rst:32
 msgid "Use a Scale in Point of Sale"
 msgstr ""
@@ -1836,20 +1709,12 @@ msgid ""
 "configure, then click on *Edit* and enable the *IoT Box* feature."
 msgstr ""
 
-#: ../../content/applications/productivity/iot/devices/scale.rstNone
-msgid "View of the IoT box feature inside of the PoS settings."
-msgstr ""
-
 #: ../../content/applications/productivity/iot/devices/scale.rst:42
 msgid ""
 "Now, choose the *IoT Box* in the dropdown menu and check the *Electronic "
 "Scale* option. Then, you hit save."
 msgstr ""
 
-#: ../../content/applications/productivity/iot/devices/scale.rstNone
-msgid "List of the external tools that can be used with PoS and the IoT box."
-msgstr ""
-
 #: ../../content/applications/productivity/iot/devices/scale.rst:49
 msgid ""
 "The scale is now available in all your *PoS* sessions. Then, if a product "
@@ -1858,14 +1723,20 @@ msgid ""
 "price to the cart."
 msgstr ""
 
-#: ../../content/applications/productivity/iot/devices/scale.rstNone
-msgid "Electronic Scale dashboard view when no items are being weighed."
-msgstr ""
-
-#: ../../content/applications/productivity/studio.rst:5
+#: ../../content/applications/productivity/studio.rst:8
 msgid "Studio"
 msgstr "Studio"
 
+#: ../../content/applications/productivity/studio.rst:10
+msgid ""
+"Learn all you need in order to build custom applications: customize views, "
+"create specific reports, automate actions, define approval workflows, etc."
+msgstr ""
+
+#: ../../content/applications/productivity/studio.rst:14
+msgid "`Odoo Tutorials: Studio <https://www.odoo.com/slides/studio-31>`_"
+msgstr ""
+
 #: ../../content/applications/productivity/studio/concepts.rst:5
 msgid "Concepts"
 msgstr ""
@@ -1888,10 +1759,6 @@ msgid ""
 "changing stage if a field is not filled in."
 msgstr ""
 
-#: ../../content/applications/productivity/studio/concepts/understanding_automated_actions.rstNone
-msgid "Flowchart to exemplify an automated action rule for Odoo Studio"
-msgstr ""
-
 #: ../../content/applications/productivity/studio/concepts/understanding_automated_actions.rst:16
 msgid ""
 "Let's understand how to properly define *when* an automated action runs and "
@@ -2030,10 +1897,6 @@ msgid ""
 "goes through:"
 msgstr ""
 
-#: ../../content/applications/productivity/studio/concepts/understanding_automated_actions.rstNone
-msgid "View of an automated action being created in Odoo Studio"
-msgstr ""
-
 #: ../../content/applications/productivity/studio/concepts/understanding_automated_actions.rst:65
 msgid "The user creates the record without an email address set."
 msgstr ""
@@ -2125,12 +1988,6 @@ msgid ""
 "step."
 msgstr ""
 
-#: ../../content/applications/productivity/studio/concepts/understanding_general.rstNone
-msgid ""
-"Overview of the main dashboard emphasizing the option to create a new app in"
-" Odoo Studio"
-msgstr ""
-
 #: ../../content/applications/productivity/studio/concepts/understanding_general.rst:38
 msgid "What is a Model (also called Object)?"
 msgstr ""
@@ -2189,10 +2046,6 @@ msgid ""
 "In Odoo, relational field types are: *One2many*, *Many2one*, *Many2many*."
 msgstr ""
 
-#: ../../content/applications/productivity/studio/concepts/understanding_general.rstNone
-msgid "Tables with a visual explanation of related fields for Odoo Studio"
-msgstr ""
-
 #: ../../content/applications/productivity/studio/concepts/understanding_general.rst:66
 msgid ""
 "An **One2many** field is a *one-way* direction of selecting *multiple* "
@@ -2254,10 +2107,6 @@ msgid ""
 "menus (models) and rearrange their hierarchy, click on *Edit Menu*."
 msgstr ""
 
-#: ../../content/applications/productivity/studio/concepts/understanding_general.rstNone
-msgid "Overview of a menu being edit in Odoo Studio"
-msgstr ""
-
 #: ../../content/applications/productivity/studio/concepts/understanding_general.rst:95
 msgid "`Studio Basics <https://www.odoo.com/fr_FR/slides/studio-31>`_"
 msgstr ""
@@ -2283,10 +2132,6 @@ msgid ""
 "*customizations.zip*."
 msgstr ""
 
-#: ../../content/applications/productivity/studio/how_to/export_import.rstNone
-msgid "View of the menu customizations in Odoo Studio"
-msgstr ""
-
 #: ../../content/applications/productivity/studio/how_to/export_import.rst:16
 msgid ""
 "The module created contains the definition of custom models and fields, as "
@@ -2300,10 +2145,6 @@ msgid ""
 " *Import*."
 msgstr ""
 
-#: ../../content/applications/productivity/studio/how_to/export_import.rstNone
-msgid "View of the import modules window for Odoo Studio"
-msgstr ""
-
 #: ../../content/applications/productivity/studio/how_to/export_import.rst:25
 msgid ""
 "Studio does not know which apps are customized (because the same view can be"
@@ -2324,13 +2165,6 @@ msgid ""
 "software fun to use, and rewarding, for employees."
 msgstr ""
 
-#: ../../content/applications/productivity/studio/how_to/rainbow_man.rstNone
-#: ../../content/applications/productivity/studio/how_to/rainbow_man.rstNone
-msgid ""
-"View of a sales form and the tab properties and its rainbow man field in "
-"Odoo Studio"
-msgstr ""
-
 #: ../../content/applications/productivity/studio/how_to/rainbow_man.rst:13
 msgid ""
 "On most buttons in Odoo, such as *Send by Email*, *Confirm* or *Cancel*, "
@@ -2379,10 +2213,6 @@ msgid ""
 " email address, etc.)."
 msgstr ""
 
-#: ../../content/applications/productivity/studio/how_to/reports.rstNone
-msgid "View of the types of new reports in Odoo Studio"
-msgstr ""
-
 #: ../../content/applications/productivity/studio/how_to/reports.rst:17
 msgid ""
 "Under the tab **Add**, you find the fields to be dragged and dropped to the "
@@ -2392,10 +2222,6 @@ msgid ""
 " *Image*, and *Text in Cell* are static elements."
 msgstr ""
 
-#: ../../content/applications/productivity/studio/how_to/reports.rstNone
-msgid "View of a report and the tab add in Odoo Studio"
-msgstr ""
-
 #: ../../content/applications/productivity/studio/how_to/reports.rst:26
 msgid ""
 "Once the element is added to the view, select it to see its **Options**. The"
@@ -2404,10 +2230,6 @@ msgid ""
 "objects have their directives shown on *Field Expression*."
 msgstr ""
 
-#: ../../content/applications/productivity/studio/how_to/reports.rstNone
-msgid "View of a report and the tab options in Odoo Studio"
-msgstr ""
-
 #: ../../content/applications/productivity/studio/how_to/reports.rst:34
 msgid ""
 "Under **Visible if**, define the rule(s) to set visibility conditions to "
@@ -2430,12 +2252,6 @@ msgid ""
 "groups do not see the same final document."
 msgstr ""
 
-#: ../../content/applications/productivity/studio/how_to/reports.rstNone
-msgid ""
-"View of a report’s settings emphasizing the field limit visibility to groups"
-" in Odoo Studio"
-msgstr ""
-
 #: ../../content/applications/productivity/studio/how_to/reports.rst:46
 msgid ""
 "Under the **Report** tab, name your report, choose the paper format, and if "
@@ -2443,10 +2259,6 @@ msgid ""
 "document form."
 msgstr ""
 
-#: ../../content/applications/productivity/studio/how_to/reports.rstNone
-msgid "View of an invoice form emphasizing the menu print for Odoo Studio"
-msgstr ""
-
 #: ../../content/applications/productivity/studio/how_to/reports.rst:53
 msgid ""
 "If activating the :ref:`developer mode <developer-mode>`, additional fields "
@@ -2477,12 +2289,6 @@ msgid ""
 " have closed Studio, changes can not be undone anymore."
 msgstr ""
 
-#: ../../content/applications/productivity/studio/how_to/reports.rst:0
-msgid ""
-"View of a report being built and emphasizing the undo and redo buttons in "
-"Odoo Studio"
-msgstr ""
-
 #: ../../content/applications/productivity/studio/use_cases.rst:5
 msgid "Use Cases"
 msgstr ""
@@ -2526,12 +2332,6 @@ msgstr ""
 msgid "*Data to Write*: Lead/Opportunity > Value > 3"
 msgstr ""
 
-#: ../../content/applications/productivity/studio/use_cases/automated_actions.rstNone
-msgid ""
-"View of an automated action that sets a high priority to Belgian leads in "
-"Odoo Studio"
-msgstr ""
-
 #: ../../content/applications/productivity/studio/use_cases/automated_actions.rst:22
 msgid ""
 "Check :doc:`this doc <filters_status_bar>` in order to have another "
@@ -2566,22 +2366,12 @@ msgid ""
 " *Use by default* and *Save*."
 msgstr ""
 
-#: ../../content/applications/productivity/studio/use_cases/filters_status_bar.rstNone
-msgid "View of a custom filter being set to be used by default in Odoo"
-msgstr ""
-
 #: ../../content/applications/productivity/studio/use_cases/filters_status_bar.rst:15
 msgid ""
 "On *Filter Rules* in Studio mode, select the respective filter and enable "
 "*Default Filter*."
 msgstr ""
 
-#: ../../content/applications/productivity/studio/use_cases/filters_status_bar.rstNone
-msgid ""
-"View of a filter’s rule form emphasizing the field default filter in Odoo "
-"Studio"
-msgstr ""
-
 #: ../../content/applications/productivity/studio/use_cases/filters_status_bar.rst:21
 msgid ""
 "**Case scenario 2: add a status bar on the product form to manage its life "
@@ -2602,10 +2392,6 @@ msgid ""
 "*Default Group by* as *Pipeline status bar*."
 msgstr ""
 
-#: ../../content/applications/productivity/studio/use_cases/filters_status_bar.rstNone
-msgid "Form view emphasizing the button add a pipeline bar in Odoo Studio"
-msgstr ""
-
 #: ../../content/applications/productivity/studio/use_cases/filters_status_bar.rst:34
 msgid ""
 "Now, open your product form and set the right status for that product. As "
@@ -2619,10 +2405,6 @@ msgid ""
 "go back to *Form View*."
 msgstr ""
 
-#: ../../content/applications/productivity/studio/use_cases/filters_status_bar.rst:0
-msgid "View of Studio emphasizing the form view button in Odoo Studio"
-msgstr ""
-
 #: ../../content/applications/productivity/studio/use_cases/filters_status_bar.rst:44
 msgid ""
 "**Case scenario 2.a: when a product goes from ‘In use’ to ‘Deprecate’, set "
@@ -2655,12 +2437,6 @@ msgstr ""
 msgid "*Data to Write*: Cost (Product Template) > Value > 0"
 msgstr ""
 
-#: ../../content/applications/productivity/studio/use_cases/filters_status_bar.rstNone
-msgid ""
-"View of the automated action created to set the price of a product to zero "
-"in Odoo Studio"
-msgstr ""
-
 #: ../../content/applications/productivity/studio/use_cases/models_fields.rst:3
 msgid "Advanced Use Cases: Creating Models and Adding Fields"
 msgstr ""
@@ -2686,10 +2462,6 @@ msgstr ""
 msgid "You can now hide the related field created (*Country*) if you wish."
 msgstr ""
 
-#: ../../content/applications/productivity/studio/use_cases/models_fields.rstNone
-msgid "View of the invisibility domain of a field being set in Odoo Studio"
-msgstr ""
-
 #: ../../content/applications/productivity/studio/use_cases/models_fields.rst:19
 msgid ""
 "Another approach is to use the country’s ID. To do so, go to "
@@ -2707,11 +2479,6 @@ msgstr ""
 msgid "Again, hide the related field with the country’s ID if you prefer."
 msgstr ""
 
-#: ../../content/applications/productivity/studio/use_cases/models_fields.rstNone
-msgid ""
-"View of an URL emphasizing where a country’s ID can be found for Odoo Studio"
-msgstr ""
-
 #: ../../content/applications/productivity/studio/use_cases/models_fields.rst:28
 msgid ""
 "**Case scenario 2: create a model called 'Properties' and add fields called:"
@@ -2725,10 +2492,6 @@ msgid ""
 " on its form, drag & drop the necessary fields."
 msgstr ""
 
-#: ../../content/applications/productivity/studio/use_cases/models_fields.rstNone
-msgid "View of the recommended fields for an object in Odoo Studio"
-msgstr ""
-
 #: ../../content/applications/productivity/studio/use_cases/models_fields.rst:39
 msgid ""
 "**Case scenario 2.a: now, you would like to have a model called 'Regions' to"
@@ -2754,11 +2517,6 @@ msgid ""
 " in the view."
 msgstr ""
 
-#: ../../content/applications/productivity/studio/use_cases/models_fields.rst:0
-#: ../../content/applications/productivity/studio/use_cases/models_fields.rstNone
-msgid "Form view and a Many2one field being dropped in Odoo Studio"
-msgstr ""
-
 #: ../../content/applications/productivity/studio/use_cases/models_fields.rst:60
 msgid ""
 "Now, go to the model *Regions*, select the form view, and add a status "
@@ -2771,20 +2529,12 @@ msgid ""
 " records on the related model, and allow you to access them."
 msgstr ""
 
-#: ../../content/applications/productivity/studio/use_cases/models_fields.rstNone
-msgid "Form view and the status button window being shown in Odoo Studio"
-msgstr ""
-
 #: ../../content/applications/productivity/studio/use_cases/models_fields.rst:69
 msgid ""
 "When searching for relations, click on *Search more* and filter it by "
 "*Custom*. This way you avoid creating duplicates."
 msgstr ""
 
-#: ../../content/applications/productivity/studio/use_cases/models_fields.rst:0
-msgid "View of the search model window in Odoo Studio"
-msgstr ""
-
 #: ../../content/applications/productivity/studio/use_cases/models_fields.rst:76
 msgid ""
 "**Case scenario 2.b: in the model 'Properties', show all the tags as "
@@ -2797,10 +2547,6 @@ msgid ""
 "*Properties > Widgets*, choose *Checkboxes*."
 msgstr ""
 
-#: ../../content/applications/productivity/studio/use_cases/models_fields.rstNone
-msgid "Form view showing the widgets available in Odoo Studio"
-msgstr ""
-
 #: ../../content/applications/productivity/studio/use_cases/models_fields.rst:85
 msgid ""
 "**Case scenario 3: on the leads’ form, add a selection field with the "
@@ -2815,10 +2561,6 @@ msgid ""
 "another 2 times for *Checkboxes* and *Tags*."
 msgstr ""
 
-#: ../../content/applications/productivity/studio/use_cases/models_fields.rstNone
-msgid "Form view emphasizing the widget property in Odoo Studio"
-msgstr ""
-
 #: ../../content/applications/productivity/studio/use_cases/models_fields.rst:96
 msgid "Now, add a *Selection* field and the necessary values."
 msgstr ""
@@ -2831,12 +2573,6 @@ msgid ""
 "not = > Tags.*"
 msgstr ""
 
-#: ../../content/applications/productivity/studio/use_cases/models_fields.rstNone
-msgid ""
-"Form view emphasizing a field added and its invisibility properties in Odoo "
-"Studio"
-msgstr ""
-
 #: ../../content/applications/productivity/studio/use_cases/models_fields.rst:105
 msgid ""
 "**Case scenario 4: on a quotation’s form, add a selection field called "
@@ -2852,10 +2588,6 @@ msgid ""
 "the *Limit visibility to groups* as *Sales / Administrator* or managers."
 msgstr ""
 
-#: ../../content/applications/productivity/studio/use_cases/models_fields.rstNone
-msgid "Form view of a required domain being set in Odoo Studio"
-msgstr ""
-
 #: ../../content/applications/productivity/studio/use_cases/models_fields.rst:117
 msgid "**Case scenario 5: change the tooltip of a field for all views.**"
 msgstr ""
@@ -2872,12 +2604,6 @@ msgid ""
 "written is displayed on all views forms where the field is added."
 msgstr ""
 
-#: ../../content/applications/productivity/studio/use_cases/models_fields.rstNone
-msgid ""
-"Form view showing more property options and emphasizing the help feature in "
-"Odoo Studio"
-msgstr ""
-
 #: ../../content/applications/productivity/studio/use_cases/models_fields.rst:129
 msgid ""
 "The *Field Help* message can only be applied to *new* fields. If you would "
@@ -2885,11 +2611,6 @@ msgid ""
 "option under *Properties*."
 msgstr ""
 
-#: ../../content/applications/productivity/studio/use_cases/models_fields.rst:0
-msgid ""
-"View of the properties emphasizing the help tooltip option in Odoo Studio"
-msgstr ""
-
 #: ../../content/applications/productivity/studio/use_cases/views.rst:3
 msgid "Advanced Use Cases: Views"
 msgstr ""
@@ -2906,10 +2627,6 @@ msgid ""
 "option as the default one."
 msgstr ""
 
-#: ../../content/applications/productivity/studio/use_cases/views.rstNone
-msgid "View of the Kanban option being set as the default one in Odoo Studio"
-msgstr ""
-
 #: ../../content/applications/productivity/studio/use_cases/views.rst:14
 msgid ""
 "**Case scenario 2: allow for the list of leads to be edited inline without "
@@ -2928,8 +2645,3 @@ msgid ""
 "If the field is left blank, no editing is possible and records are shown "
 "based on your column preferences on the lead's page (front-end)."
 msgstr ""
-
-#: ../../content/applications/productivity/studio/use_cases/views.rstNone
-msgid ""
-"View options emphasizing the editable options of a leads page in Odoo Studio"
-msgstr ""

locale/da/LC_MESSAGES/sphinx.po

@@ -6,16 +6,15 @@
 # Translators:
 # Martin Trigaux, 2021
 # Sanne Kristensen <sanne@vkdata.dk>, 2021
-# Mads Søndergaard, 2021
 # 
 #, fuzzy
 msgid ""
 msgstr ""
 "Project-Id-Version: Odoo 14.0\n"
 "Report-Msgid-Bugs-To: \n"
-"POT-Creation-Date: 2021-06-14 16:09+0200\n"
+"POT-Creation-Date: 2021-08-10 09:10+0000\n"
 "PO-Revision-Date: 2021-07-02 09:18+0000\n"
-"Last-Translator: Mads Søndergaard, 2021\n"
+"Last-Translator: Sanne Kristensen <sanne@vkdata.dk>, 2021\n"
 "Language-Team: Danish (https://www.transifex.com/odoo/teams/41243/da/)\n"
 "MIME-Version: 1.0\n"
 "Content-Type: text/plain; charset=UTF-8\n"
@@ -36,143 +35,119 @@ msgid "Ask the Odoo Community"
 msgstr ""
 
 #: ../../extensions/odoo_theme/layout_templates/header.html:11
-#: ../../extensions/odoo_theme/layout_templates/homepage.html:7
 msgid "Try Odoo for FREE"
 msgstr ""
 
-#: ../../extensions/odoo_theme/layout_templates/homepage.html:4
+#: ../../extensions/odoo_theme/layout_templates/homepage.html:3
 msgid "Odoo Documentation"
 msgstr ""
 
-#: ../../extensions/odoo_theme/layout_templates/homepage.html:5
+#: ../../extensions/odoo_theme/layout_templates/homepage.html:8
+msgid "User Docs"
+msgstr ""
+
+#: ../../extensions/odoo_theme/layout_templates/homepage.html:9
 msgid ""
-"The comprehensive guide for Odoo users. Easily find the tutorial and helpful"
-" tips that suit your needs."
+"Discover our guide to help you use and configure the platform, by "
+"applications."
+msgstr ""
+
+#: ../../extensions/odoo_theme/layout_templates/homepage.html:10
+msgid "Top Apps"
 msgstr ""
 
 #: ../../extensions/odoo_theme/layout_templates/homepage.html:14
-msgid "Applications"
-msgstr "Applikation"
+msgid "Accounting"
+msgstr "Regnskab"
 
-#: ../../extensions/odoo_theme/layout_templates/homepage.html:15
-msgid ""
-"Master any app thanks to their end-user guides. Our wide array of functional"
-" workflows and processes are designed to help you unleash Odoo's potential."
+#: ../../extensions/odoo_theme/layout_templates/homepage.html:19
+msgid "Inventory"
+msgstr "Lager"
+
+#: ../../extensions/odoo_theme/layout_templates/homepage.html:24
+msgid "Manufacturing"
+msgstr "Produktion"
+
+#: ../../extensions/odoo_theme/layout_templates/homepage.html:29
+msgid "Point of Sale"
+msgstr "POS"
+
+#: ../../extensions/odoo_theme/layout_templates/homepage.html:35
+msgid "Install and Maintain"
 msgstr ""
 
-#: ../../extensions/odoo_theme/layout_templates/homepage.html:16
-#: ../../extensions/odoo_theme/layout_templates/homepage.html:43
-#: ../../extensions/odoo_theme/layout_templates/homepage.html:72
-#: ../../extensions/odoo_theme/layout_templates/homepage.html:99
-#: ../../extensions/odoo_theme/layout_templates/homepage.html:123
+#: ../../extensions/odoo_theme/layout_templates/homepage.html:36
+msgid ""
+"Learn how to install, deploy and upgrade Odoo on premise or on Odoo.sh."
+msgstr ""
+
+#: ../../extensions/odoo_theme/layout_templates/homepage.html:37
+#: ../../extensions/odoo_theme/layout_templates/homepage.html:66
+#: ../../extensions/odoo_theme/layout_templates/homepage.html:98
 msgid "Top Links"
 msgstr ""
 
-#: ../../extensions/odoo_theme/layout_templates/homepage.html:20
-msgid "The Accounting behind Odoo"
-msgstr ""
-
-#: ../../extensions/odoo_theme/layout_templates/homepage.html:25
-msgid "Resupply from another Warehouse"
-msgstr ""
-
-#: ../../extensions/odoo_theme/layout_templates/homepage.html:30
-msgid "Import data into Odoo"
-msgstr ""
-
-#: ../../extensions/odoo_theme/layout_templates/homepage.html:35
-msgid "Get Started with Discuss"
-msgstr ""
-
 #: ../../extensions/odoo_theme/layout_templates/homepage.html:41
-msgid "Administration"
-msgstr "Administration"
-
-#: ../../extensions/odoo_theme/layout_templates/homepage.html:42
-msgid ""
-"Easily setup your first Odoo installation. From downloads to day-to-day "
-"database administration, the dedicated tutorials have got you covered."
-msgstr ""
-
-#: ../../extensions/odoo_theme/layout_templates/homepage.html:47
 msgid "Installing Odoo"
 msgstr ""
 
-#: ../../extensions/odoo_theme/layout_templates/homepage.html:52
-msgid "Deploying Odoo"
+#: ../../extensions/odoo_theme/layout_templates/homepage.html:46
+msgid "System configuration"
 msgstr ""
 
-#: ../../extensions/odoo_theme/layout_templates/homepage.html:57
-msgid "Updating Odoo"
+#: ../../extensions/odoo_theme/layout_templates/homepage.html:51
+msgid "Bugfix updates"
 msgstr ""
 
-#: ../../extensions/odoo_theme/layout_templates/homepage.html:62
-msgid "Introduction to Odoo.sh"
+#: ../../extensions/odoo_theme/layout_templates/homepage.html:56
+msgid "Odoo.sh: The Odoo Cloud Platform"
 msgstr ""
 
-#: ../../extensions/odoo_theme/layout_templates/homepage.html:70
+#: ../../extensions/odoo_theme/layout_templates/homepage.html:64
 msgid "Developer"
 msgstr ""
 
-#: ../../extensions/odoo_theme/layout_templates/homepage.html:71
+#: ../../extensions/odoo_theme/layout_templates/homepage.html:65
 msgid ""
 "Learn to develop in Odoo by reading the framework references and programmer "
 "tutorials."
 msgstr ""
 
-#: ../../extensions/odoo_theme/layout_templates/homepage.html:76
-msgid "ORM API"
+#: ../../extensions/odoo_theme/layout_templates/homepage.html:70
+msgid "Tutorial: Getting started"
 msgstr ""
 
-#: ../../extensions/odoo_theme/layout_templates/homepage.html:81
-msgid "Building a Module"
+#: ../../extensions/odoo_theme/layout_templates/homepage.html:75
+msgid "ORM"
 msgstr ""
 
-#: ../../extensions/odoo_theme/layout_templates/homepage.html:86
+#: ../../extensions/odoo_theme/layout_templates/homepage.html:80
+msgid "Regular Views"
+msgstr ""
+
+#: ../../extensions/odoo_theme/layout_templates/homepage.html:85
+msgid "QWeb Views"
+msgstr ""
+
+#: ../../extensions/odoo_theme/layout_templates/homepage.html:90
 msgid "External API"
 msgstr ""
 
-#: ../../extensions/odoo_theme/layout_templates/homepage.html:91
-msgid "Command-line interface"
-msgstr ""
-
-#: ../../extensions/odoo_theme/layout_templates/homepage.html:97
-msgid "Services"
-msgstr "Serviceydelser"
-
-#: ../../extensions/odoo_theme/layout_templates/homepage.html:98
-msgid ""
-"Find out how to open a support ticket should you need to contact a Customer "
-"Service Representative."
-msgstr ""
-
-#: ../../extensions/odoo_theme/layout_templates/homepage.html:103
-msgid "Where to find help?"
-msgstr ""
-
-#: ../../extensions/odoo_theme/layout_templates/homepage.html:108
-msgid "Supported versions"
-msgstr ""
-
-#: ../../extensions/odoo_theme/layout_templates/homepage.html:113
-msgid "Legal"
-msgstr "Juridisk"
-
-#: ../../extensions/odoo_theme/layout_templates/homepage.html:121
+#: ../../extensions/odoo_theme/layout_templates/homepage.html:96
 msgid "Contributing"
 msgstr ""
 
-#: ../../extensions/odoo_theme/layout_templates/homepage.html:122
+#: ../../extensions/odoo_theme/layout_templates/homepage.html:97
 msgid ""
 "You want to contribute to Odoo but don't know where to start? The tutorials "
 "and guidelines are there to help you make Odoo even better."
 msgstr ""
 
-#: ../../extensions/odoo_theme/layout_templates/homepage.html:127
+#: ../../extensions/odoo_theme/layout_templates/homepage.html:102
 msgid "Write documentation"
 msgstr ""
 
-#: ../../extensions/odoo_theme/layout_templates/homepage.html:132
+#: ../../extensions/odoo_theme/layout_templates/homepage.html:107
 msgid "Content guidelines"
 msgstr ""
 

locale/da/LC_MESSAGES/websites.po

@@ -6,22 +6,23 @@
 # Translators:
 # JonathanStein <jstein@image.dk>, 2021
 # Sanne Kristensen <sanne@vkdata.dk>, 2021
-# Martin Trigaux, 2021
 # Per Rasmussen <perhgrasmussen@gmail.com>, 2021
 # Pernille Kristensen <pernillekristensen1994@gmail.com>, 2021
 # Ejner Sønniksen <ejner@vkdata.dk>, 2021
 # lhmflexerp <lhm@flexerp.dk>, 2021
 # Mads Søndergaard, 2021
-# Mads Søndergaard <mads@vkdata.dk>, 2021
+# Martin Trigaux, 2021
+# Morten Schou <ms@msteknik.dk>, 2021
+# Mads Søndergaard, 2021
 # 
 #, fuzzy
 msgid ""
 msgstr ""
 "Project-Id-Version: Odoo 14.0\n"
 "Report-Msgid-Bugs-To: \n"
-"POT-Creation-Date: 2021-06-14 13:29+0200\n"
+"POT-Creation-Date: 2021-08-10 09:10+0000\n"
 "PO-Revision-Date: 2021-05-18 05:18+0000\n"
-"Last-Translator: Mads Søndergaard <mads@vkdata.dk>, 2021\n"
+"Last-Translator: Mads Søndergaard, 2021\n"
 "Language-Team: Danish (https://www.transifex.com/odoo/teams/41243/da/)\n"
 "MIME-Version: 1.0\n"
 "Content-Type: text/plain; charset=UTF-8\n"
@@ -33,10 +34,27 @@ msgstr ""
 msgid "Websites"
 msgstr "Websites"
 
-#: ../../content/applications/websites/ecommerce.rst:5
+#: ../../content/applications/websites/ecommerce.rst:8
 msgid "eCommerce"
 msgstr "Webshop"
 
+#: ../../content/applications/websites/ecommerce.rst:10
+msgid ""
+"Run a modern open-source online store with Odoo eCommerce. Learn how to sell"
+" online, promote products and increase your average cart sizes."
+msgstr ""
+
+#: ../../content/applications/websites/ecommerce.rst:14
+#: ../../content/applications/websites/website.rst:14
+msgid "`Odoo Tutorials: Website <https://www.odoo.com/slides/website-25>`_"
+msgstr ""
+
+#: ../../content/applications/websites/ecommerce.rst:15
+#: ../../content/applications/websites/website.rst:15
+msgid ""
+"`Odoo Tutorials: eCommerce <https://www.odoo.com/slides/ecommerce-26>`_"
+msgstr ""
+
 #: ../../content/applications/websites/ecommerce/getting_started.rst:5
 msgid "Get started"
 msgstr "Kom igang"
@@ -170,125 +188,175 @@ msgid "Such extra image are common to all the product variants (if any)."
 msgstr ""
 
 #: ../../content/applications/websites/ecommerce/managing_products/variants.rst:3
-msgid "How to manage product variants"
+msgid "Manage product variants"
 msgstr ""
 
 #: ../../content/applications/websites/ecommerce/managing_products/variants.rst:5
 msgid ""
 "Product variants are used to offer variations of the same product to your "
-"customers on the products page. For example, the customer chooses a T-shirt "
-"and then selects its size and color.  In the example below, the customer "
-"chooses a phone, and then selects the memory; color and Wi-Fi band from the "
-"available options."
+"customers on the product's page."
 msgstr ""
 
-#: ../../content/applications/websites/ecommerce/managing_products/variants.rst:15
-msgid "How to create attributes & variants"
-msgstr ""
-
-#: ../../content/applications/websites/ecommerce/managing_products/variants.rst:17
+#: ../../content/applications/websites/ecommerce/managing_products/variants.rst:8
 msgid ""
-"Turn on *Products can have several attributes, defining variants (Example: "
-"size, color,...)* in :menuselection:`Sales --> Settings`."
+"Let's say one of your customers selects a T-shirt from your product catalog."
 msgstr ""
 
-#: ../../content/applications/websites/ecommerce/managing_products/variants.rst:20
-msgid "Select a product from the Products list, go to the *Variants* tab."
+#: ../../content/applications/websites/ecommerce/managing_products/variants.rst:10
+msgid ""
+"Then, they choose the size and color they want. The various size and color "
+"combinations are known as product variants."
+msgstr ""
+
+#: ../../content/applications/websites/ecommerce/managing_products/variants.rst:14
+msgid "Create attributes & variants"
+msgstr ""
+
+#: ../../content/applications/websites/ecommerce/managing_products/variants.rst:16
+msgid ""
+"In order to create various attributes and variants for your products, you "
+"first need to turn on *Variants* in :menuselection:`Sales --> Configuration "
+"--> Settings`."
+msgstr ""
+
+#: ../../content/applications/websites/ecommerce/managing_products/variants.rst:19
+msgid ""
+"Then, select a product from the Products list (:menuselection:`Sales / "
+"Website --> Products --> Products`). When the product detail form opens, "
+"click on *Edit*, and go to the *Variants* tab."
 msgstr ""
 
 #: ../../content/applications/websites/ecommerce/managing_products/variants.rst:22
 msgid ""
-"Add as many attributes as you need from 3 different types: radio buttons, "
-"drop-down menu or color buttons. You get several variants as soon as there "
-"are 2 values for 1 attribute."
+"Here, you can add as many different attributes as you'd like by clicking on "
+"*Add a line*."
+msgstr ""
+
+#: ../../content/applications/websites/ecommerce/managing_products/variants.rst:24
+msgid "These attributes appear as three different types:"
+msgstr ""
+
+#: ../../content/applications/websites/ecommerce/managing_products/variants.rst:26
+msgid "Radio buttons"
+msgstr ""
+
+#: ../../content/applications/websites/ecommerce/managing_products/variants.rst:27
+msgid "Color buttons"
+msgstr ""
+
+#: ../../content/applications/websites/ecommerce/managing_products/variants.rst:28
+msgid "Drop-down menu"
 msgstr ""
 
 #: ../../content/applications/websites/ecommerce/managing_products/variants.rst:30
-msgid "How to edit variants"
+msgid ""
+"Several variants appear as soon as there are two values for one attribute."
 msgstr ""
 
 #: ../../content/applications/websites/ecommerce/managing_products/variants.rst:32
-msgid "See all the variants from the product template detail form."
+msgid "Don't forget to hit *Save* once all variants have been entered."
 msgstr ""
 
-#: ../../content/applications/websites/ecommerce/managing_products/variants.rst:40
-msgid "You can edit following data:"
+#: ../../content/applications/websites/ecommerce/managing_products/variants.rst:39
+msgid "Edit variants"
 msgstr ""
 
-#: ../../content/applications/websites/ecommerce/managing_products/variants.rst:42
-msgid "Picture (will update in real time on the website),"
-msgstr ""
-
-#: ../../content/applications/websites/ecommerce/managing_products/variants.rst:43
-msgid "Barcode,"
-msgstr ""
-
-#: ../../content/applications/websites/ecommerce/managing_products/variants.rst:44
-msgid "Internal Reference (SKU #),"
-msgstr ""
-
-#: ../../content/applications/websites/ecommerce/managing_products/variants.rst:45
-msgid "Volume,"
-msgstr ""
-
-#: ../../content/applications/websites/ecommerce/managing_products/variants.rst:46
-msgid "Weight,"
-msgstr ""
-
-#: ../../content/applications/websites/ecommerce/managing_products/variants.rst:47
-msgid "Active (available in quotes & website)."
-msgstr ""
-
-#: ../../content/applications/websites/ecommerce/managing_products/variants.rst:50
+#: ../../content/applications/websites/ecommerce/managing_products/variants.rst:41
 msgid ""
-"Both the Barcode and the Internal Reference are variant-specific. You need "
-"to populate them once the variants generated."
+"After you hit *Save*, you are able to see all the variants from the product "
+"template detail form via the *Variants* smart button."
 msgstr ""
 
+#: ../../content/applications/websites/ecommerce/managing_products/variants.rst:48
+msgid ""
+"Clicking the *Variants* smart button takes you to the Product Variants page,"
+" where you can edit the following data for each specific variant:"
+msgstr ""
+
+#: ../../content/applications/websites/ecommerce/managing_products/variants.rst:51
+msgid "Picture(s)"
+msgstr ""
+
+#: ../../content/applications/websites/ecommerce/managing_products/variants.rst:52
+msgid "Internal Reference (SKU #)"
+msgstr ""
+
+#: ../../content/applications/websites/ecommerce/managing_products/variants.rst:53
+msgid "Barcode"
+msgstr "Stregkode"
+
 #: ../../content/applications/websites/ecommerce/managing_products/variants.rst:54
+msgid "Volume"
+msgstr "Volumen"
+
+#: ../../content/applications/websites/ecommerce/managing_products/variants.rst:55
+msgid "Weight"
+msgstr "Vægt"
+
+#: ../../content/applications/websites/ecommerce/managing_products/variants.rst:56
+msgid "Cost"
+msgstr "Kostpris"
+
+#: ../../content/applications/websites/ecommerce/managing_products/variants.rst:59
 msgid ""
-"See and edit all the variants from :menuselection:`Sales --> Sales --> "
-"Product Variants` as well. This might be quicker if you manage lots of "
-"variants."
+"Both the Barcode and the Internal Reference are variant-specific. You need "
+"to populate them once the variants are generated."
 msgstr ""
 
-#: ../../content/applications/websites/ecommerce/managing_products/variants.rst:58
-msgid "How to set specific prices per variant"
+#: ../../content/applications/websites/ecommerce/managing_products/variants.rst:63
+msgid "Set specific prices per variant"
 msgstr ""
 
-#: ../../content/applications/websites/ecommerce/managing_products/variants.rst:60
+#: ../../content/applications/websites/ecommerce/managing_products/variants.rst:65
 msgid ""
-"You can also set a specific public price per variant by clicking *Variant "
-"Prices* in the product detail form (action in top-left corner)."
+"You can set a specific public price per variant by clicking on *Configure "
+"Variants* in the product detail form (top-left corner). That takes you to "
+"the *Product Variant Values* page for that product."
 msgstr ""
 
-#: ../../content/applications/websites/ecommerce/managing_products/variants.rst:66
+#: ../../content/applications/websites/ecommerce/managing_products/variants.rst:72
 msgid ""
-"The Price Extra is added to the product price whenever the corresponding "
-"attribute value is selected."
+"To set a specific public price for a particular variant, simply click on the"
+" variant you want to modify, then click on *Edit*."
 msgstr ""
 
-#: ../../content/applications/websites/ecommerce/managing_products/variants.rst:76
+#: ../../content/applications/websites/ecommerce/managing_products/variants.rst:75
+msgid ""
+"The *Value Price Extra* field represents the monetary value that is added to"
+" the original product price whenever the corresponding attribute value is "
+"selected."
+msgstr ""
+
+#: ../../content/applications/websites/ecommerce/managing_products/variants.rst:82
+msgid "This is how the *Value Price Extra* looks on your website:"
+msgstr ""
+
+#: ../../content/applications/websites/ecommerce/managing_products/variants.rst:89
 msgid ""
 "Pricelist formulas let you set advanced price computation methods for "
 "product variants. See :doc:`../maximizing_revenue/pricing`."
 msgstr ""
 
-#: ../../content/applications/websites/ecommerce/managing_products/variants.rst:80
-msgid "How to disable/archive variants"
+#: ../../content/applications/websites/ecommerce/managing_products/variants.rst:93
+msgid "Disable/archive variants"
 msgstr ""
 
-#: ../../content/applications/websites/ecommerce/managing_products/variants.rst:82
+#: ../../content/applications/websites/ecommerce/managing_products/variants.rst:95
 msgid ""
-"You can disable/archive specific variants so that they are no longer "
-"available in quotes & website (not existing in your stock, deprecated, "
-"etc.). Simply uncheck *Active* in their detail form."
+"You can disable/archive specific variants so they are no longer available in"
+" quotes or on your website (not existing in your stock, deprecated, etc.). "
+"Simply select *Archive* in their detail form. You can reactivate them the "
+"same way."
 msgstr ""
 
-#: ../../content/applications/websites/ecommerce/managing_products/variants.rst:88
+#: ../../content/applications/websites/ecommerce/managing_products/variants.rst:103
 msgid ""
-"To retrieve such archived items, hit *Archived* on searching the variants "
-"list. You can reactivate them the same way."
+"To retrieve such items, hit *Archived* in the *Filters* category while "
+"searching the variants list."
+msgstr ""
+
+#: ../../content/applications/websites/ecommerce/managing_products/variants.rst:110
+msgid ":doc:`../../../sales/sales/products_prices/products/variants`"
 msgstr ""
 
 #: ../../content/applications/websites/ecommerce/maximizing_revenue.rst:5
@@ -482,7 +550,7 @@ msgstr ""
 
 #: ../../content/applications/websites/ecommerce/maximizing_revenue/promo_code.rst:43
 msgid ":doc:`pricing`"
-msgstr ""
+msgstr ":doc:`prissætning`"
 
 #: ../../content/applications/websites/ecommerce/maximizing_revenue/reviews.rst:3
 msgid "How to enable comments & rating"
@@ -625,10 +693,6 @@ msgid ""
 " with an automatic note in the *Chatter*."
 msgstr ""
 
-#: ../../content/applications/websites/ecommerce/shopper_experience/payment_acquirer.rstNone
-msgid "payment is confirmed in the chatter of sales order"
-msgstr ""
-
 #: ../../content/applications/websites/ecommerce/shopper_experience/payment_acquirer.rst:24
 msgid ""
 "If the user decides to create an invoice, the payment is directly "
@@ -637,10 +701,6 @@ msgid ""
 "the related Journal Entry."
 msgstr ""
 
-#: ../../content/applications/websites/ecommerce/shopper_experience/payment_acquirer.rstNone
-msgid "page with details surrounding the specific transaction"
-msgstr ""
-
 #: ../../content/applications/websites/ecommerce/shopper_experience/payment_acquirer.rst:32
 msgid ""
 "Specific messages are provided to your customers for every payment status "
@@ -678,10 +738,6 @@ msgstr ""
 msgid "Then activate *Automatic Invoices* and *Save*."
 msgstr ""
 
-#: ../../content/applications/websites/ecommerce/shopper_experience/payment_acquirer.rstNone
-msgid "example of automatic invoice"
-msgstr ""
-
 #: ../../content/applications/websites/ecommerce/shopper_experience/payment_acquirer.rst:54
 msgid "Capture payment after the delivery"
 msgstr ""
@@ -753,10 +809,14 @@ msgstr ""
 msgid "Collect taxes"
 msgstr ""
 
-#: ../../content/applications/websites/livechat.rst:5
+#: ../../content/applications/websites/livechat.rst:8
 msgid "Live Chat"
 msgstr "Live Chat"
 
+#: ../../content/applications/websites/livechat.rst:11
+msgid "`Live Chat: product page <https://www.odoo.com/app/live-chat>`_"
+msgstr ""
+
 #: ../../content/applications/websites/livechat/overview.rst:5
 #: ../../content/applications/websites/website/publish/translate.rst:6
 msgid "Overview"
@@ -786,19 +846,11 @@ msgid ""
 "Live Chat`."
 msgstr ""
 
-#: ../../content/applications/websites/livechat/overview/get_started.rstNone
-msgid "View of the settings page and the live chat feature for Odoo Live Chat"
-msgstr ""
-
 #: ../../content/applications/websites/livechat/overview/get_started.rst:21
 msgid ""
 "Select the channel to be linked to your website or create one on the fly."
 msgstr ""
 
-#: ../../content/applications/websites/livechat/overview/get_started.rstNone
-msgid "View of a live chat channel form for Odoo Live Chat"
-msgstr ""
-
 #: ../../content/applications/websites/livechat/overview/get_started.rst:27
 msgid "For both scenarios, under:"
 msgstr ""
@@ -824,10 +876,6 @@ msgid ""
 "users (from any country) land on the contact us page."
 msgstr ""
 
-#: ../../content/applications/websites/livechat/overview/get_started.rstNone
-msgid "View of a channel’s rules form for Odoo Live Chat"
-msgstr ""
-
 #: ../../content/applications/websites/livechat/overview/get_started.rst:43
 msgid ""
 "GeoIP, which refers to the process of finding a computer terminal’s "
@@ -851,10 +899,6 @@ msgid ""
 "single live chat page."
 msgstr ""
 
-#: ../../content/applications/websites/livechat/overview/get_started.rstNone
-msgid "View of the widget tab for Odoo Live Chat"
-msgstr ""
-
 #: ../../content/applications/websites/livechat/overview/get_started.rst:59
 msgid "Managing chat requests"
 msgstr ""
@@ -866,12 +910,6 @@ msgid ""
 " Odoo."
 msgstr ""
 
-#: ../../content/applications/websites/livechat/overview/get_started.rstNone
-msgid ""
-"View of the discuss application with a message sent through live chat in "
-"Odoo"
-msgstr ""
-
 #: ../../content/applications/websites/livechat/overview/get_started.rst:69
 msgid ""
 "Conversations are dispatched based on the current workload of the online "
@@ -888,11 +926,6 @@ msgid ""
 "channel under *Live Chat*, and *Join Channel* or *Leave Channel*."
 msgstr ""
 
-#: ../../content/applications/websites/livechat/overview/get_started.rstNone
-msgid ""
-"View of a channel form and the option to join a channel for Odoo Live Chat"
-msgstr ""
-
 #: ../../content/applications/websites/livechat/overview/get_started.rst:82
 #: ../../content/applications/websites/livechat/overview/responses.rst:48
 msgid ":doc:`ratings`"
@@ -933,28 +966,14 @@ msgstr ""
 msgid "A copy of the conversation can also be sent by email."
 msgstr ""
 
-#: ../../content/applications/websites/livechat/overview/ratings.rstNone
-msgid "View of the chat window from a user’s side for Odoo Live Chat"
-msgstr ""
-
 #: ../../content/applications/websites/livechat/overview/ratings.rst:22
 msgid "The rating is shown on the chat window itself for the operator."
 msgstr ""
 
-#: ../../content/applications/websites/livechat/overview/ratings.rstNone
-msgid ""
-"View of a chat window from an operator’s side highlighting a rating for Odoo"
-" Live Chat"
-msgstr ""
-
 #: ../../content/applications/websites/livechat/overview/ratings.rst:28
 msgid "And under :menuselection:`Report --> Customer Ratings`."
 msgstr ""
 
-#: ../../content/applications/websites/livechat/overview/ratings.rstNone
-msgid "View of the customer ratings page in Odoo Live Chat"
-msgstr ""
-
 #: ../../content/applications/websites/livechat/overview/ratings.rst:35
 msgid "Make the rating public"
 msgstr ""
@@ -966,10 +985,6 @@ msgid ""
 "rating of that channel on your website."
 msgstr ""
 
-#: ../../content/applications/websites/livechat/overview/ratings.rstNone
-msgid "View of the public ratings in the website for Odoo Live Chat"
-msgstr ""
-
 #: ../../content/applications/websites/livechat/overview/responses.rst:3
 msgid "Commands and Canned Responses"
 msgstr ""
@@ -1031,11 +1046,6 @@ msgid ""
 "link."
 msgstr ""
 
-#: ../../content/applications/websites/livechat/overview/responses.rstNone
-msgid ""
-"View of the chat window with a helpdesk ticket created in Odoo Live Chat"
-msgstr ""
-
 #: ../../content/applications/websites/livechat/overview/responses.rst:33
 msgid ""
 "Helpdesk tickets created from the chat automatically add the conversation as"
@@ -1059,15 +1069,16 @@ msgid ""
 "shortcut word you created."
 msgstr ""
 
-#: ../../content/applications/websites/livechat/overview/responses.rstNone
-msgid ""
-"View of a chat window and the use of a canned response in Odoo Live Chat"
-msgstr ""
-
-#: ../../content/applications/websites/website.rst:5
+#: ../../content/applications/websites/website.rst:8
 msgid "Website"
 msgstr "Hjemmeside"
 
+#: ../../content/applications/websites/website.rst:10
+msgid ""
+"Discover the best **Open-Source Website Builder** and learn how to build "
+"beautiful websites that convert visitors into leads or revenues."
+msgstr ""
+
 #: ../../content/applications/websites/website/optimize.rst:5
 msgid "Optimize"
 msgstr "Optimér"
@@ -1250,12 +1261,6 @@ msgstr ""
 "Gå til :menuselection:`Hjemmeside --> Konfiguration --> Indstillinger`og "
 "aktiver *Link sporere*."
 
-#: ../../content/applications/websites/website/optimize/link_tracker.rstNone
-msgid ""
-"View of Website settings page emphasizing the link trackers field in Odoo "
-"Website"
-msgstr ""
-
 #: ../../content/applications/websites/website/optimize/link_tracker.rst:19
 msgid "Set up traceable URLs"
 msgstr "Opsæt sporbare URL'er"
@@ -1270,10 +1275,6 @@ msgstr ""
 "Spor denne side`. Her kan du hente en specifik sporet URL, baseret på "
 "kampagne, medie, og kilde der anvendes."
 
-#: ../../content/applications/websites/website/optimize/link_tracker.rstNone
-msgid "View of the link tracker fields for Odoo Website"
-msgstr ""
-
 #: ../../content/applications/websites/website/optimize/link_tracker.rst:28
 msgid ""
 "**URL**: url of the page you want to track (e.g. the home page or a "
@@ -1326,11 +1327,6 @@ msgstr ""
 "nyligt*, kan du også klikke på *Statistikker* og se komplette statistikker "
 "over antallet af klik samt oprindelseslandene for de klik."
 
-#: ../../content/applications/websites/website/optimize/link_tracker.rstNone
-msgid ""
-"View of the tracked list emphasizing the statistics buttons in Odoo Website"
-msgstr ""
-
 #: ../../content/applications/websites/website/optimize/link_tracker.rst:50
 msgid "You can also access the link tracker on *odoo.com/r* via your browser."
 msgstr ""
@@ -1476,12 +1472,14 @@ msgstr "**Odoo Blogs**: skriv fantastisk indhold."
 #: ../../content/applications/websites/website/optimize/seo.rst:62
 msgid ""
 "**Odoo Slides**: publish all your Powerpoint or PDF presentations. Their "
-"content is automatically indexed on the web page. Example: `odoo.com/slides"
-"/public-channel-1 <https://www.odoo.com/slides/public-channel-1>`_"
+"content is automatically indexed on the web page. Example: "
+"`odoo.com/slides/public-channel-1 <https://www.odoo.com/slides/public-"
+"channel-1>`_"
 msgstr ""
 "**Odoo Dias**: udgiv alle dine Powerpoint eller PDF præsentationer. Deres "
-"indhold indekseres automatisk på hjemmesiden. Eksempel: `odoo.com/slides"
-"/public-channel-1 <https://www.odoo.com/slides/public-channel-1>`_"
+"indhold indekseres automatisk på hjemmesiden. Eksempel: "
+"`odoo.com/slides/public-channel-1 <https://www.odoo.com/slides/public-"
+"channel-1>`_"
 
 #: ../../content/applications/websites/website/optimize/seo.rst:66
 msgid ""
@@ -2002,8 +2000,8 @@ msgid ""
 " load your pages by two (e.g. 2 seconds instead of 4 seconds), the visitor "
 "abandonment rate is also divided by two. (25% to 12.5%). One extra second to"
 " load a page could `cost $1.6b to Amazon in sales "
-"<http://www.fastcompany.com/1825005/how-one-second-could-cost-amazon-16"
-"-billion-sales>`__."
+"<http://www.fastcompany.com/1825005/how-one-second-could-cost-"
+"amazon-16-billion-sales>`__."
 msgstr ""
 "Tiden det tager at indlæse en side er et vigtigt kriterie for søgemaskiner. "
 "En hurtigere hjemmeside forbedre ikke kun dine besøgendes oplevelse, men "
@@ -2519,8 +2517,9 @@ msgid ""
 "and eCommerce (Drupal, Wordpress, Magento, Prestashop). The following link "
 "provides an analysis of the major open source CMS and eCommerce compared to "
 "Odoo when it comes to high query volumes: "
-"`https://www.odoo.com/slides/slide/197 <https://www.odoo.com/slides/slide"
-"/odoo-cms-performance-comparison-and-optimisation-197>`_"
+"`https://www.odoo.com/slides/slide/197 "
+"<https://www.odoo.com/slides/slide/odoo-cms-performance-comparison-and-"
+"optimisation-197>`_"
 msgstr ""
 "Udover at være hurtig, er Odoo også mere skalérbar end traditionelle CMS og eHandel (Drupal, Wordpress, Magento, Prestashop). Det følgende link indeholder en analyse af de større Open Source CMS og eHandel, sammenlignet med Odoo, når det kommer til høj volumen på forespørgsler:\n"
 "`https://www.odoo.com/slides/slide/197 <https://www.odoo.com/slides/slide/odoo-cms-performance-comparison-and-optimisation-197>`_"
@@ -2679,6 +2678,110 @@ msgid ""
 "upgrades."
 msgstr ""
 
+#: ../../content/applications/websites/website/optimize/unsplash.rst:3
+msgid "Unsplash (free images)"
+msgstr ""
+
+#: ../../content/applications/websites/website/optimize/unsplash.rst:6
+msgid "Generate an Unsplash access key"
+msgstr ""
+
+#: ../../content/applications/websites/website/optimize/unsplash.rst:9
+msgid ""
+"**As a SaaS user**, you are ready to use Unsplash. You won't need to follow "
+"this guide to set up Unsplash information since you will use our own Odoo "
+"Unsplash key in a transparent way."
+msgstr ""
+
+#: ../../content/applications/websites/website/optimize/unsplash.rst:13
+msgid "Generate an Unsplash access key for non-Saas users"
+msgstr ""
+
+#: ../../content/applications/websites/website/optimize/unsplash.rst:15
+msgid "Create an account on `Unsplash.com <https://unsplash.com/join>`_."
+msgstr "Opret en konto på `Unsplash.com <https://unsplash.com/join>`_."
+
+#: ../../content/applications/websites/website/optimize/unsplash.rst:17
+msgid ""
+"Go to your `applications dashboard "
+"<https://unsplash.com/oauth/applications>`_ and click on **New "
+"Application**."
+msgstr ""
+"Go til dine `applikationers instrumentbræt "
+"<https://unsplash.com/oauth/applications>`_ og klik på **Ny Applikation**."
+
+#: ../../content/applications/websites/website/optimize/unsplash.rst:23
+msgid "Accept the conditions and click on **Accept terms**."
+msgstr "Accepter betingelserne og klik på **Acceptér Vilkår**."
+
+#: ../../content/applications/websites/website/optimize/unsplash.rst:28
+msgid ""
+"You will be prompted to insert an **Application name** and a "
+"**Description**. Please prefix your application name by \"**Odoo:** \" so "
+"that Unsplash can recognize it as an Odoo instance. Once done, click on "
+"**Create application**."
+msgstr ""
+"Du vil blive bedt om at indsætte et **Applikations navn** og en "
+"**Beskrivelse**. Venligst sæt \"**Odoo:** \" før dit applikationsnavn, så "
+"Unsplash kan genkende det som en Odoo instans. Når det er gjort, skal du "
+"klikke på **Opret applikation**."
+
+#: ../../content/applications/websites/website/optimize/unsplash.rst:35
+msgid ""
+"You should be redirected to your application details page. Scroll down a bit"
+" to find your **access key**."
+msgstr ""
+"Du bør blive omdirigeret til din applikationsdetalje side. Scroll en smule "
+"ned for at finde din **adgangsnøgle**."
+
+#: ../../content/applications/websites/website/optimize/unsplash.rst:42
+msgid ""
+"**As a non-SaaS user**, you won't be able to register for a production "
+"Unsplash key and will be limited to your test key that has a restriction of "
+"50 Unsplash requests per hour."
+msgstr ""
+"**Som en ikke-SaaS bruger** vil du ikke være i stand til at registrere dig "
+"til en Unsplash produktionsnøgle, og vil være begrænset til din testnøgle, "
+"der har en begrænsing på 50 Unsplash anmodninger per time."
+
+#: ../../content/applications/websites/website/optimize/unsplash.rst:46
+msgid "Generate an Unsplash application ID"
+msgstr ""
+
+#: ../../content/applications/websites/website/optimize/unsplash.rst:49
+msgid "You should first create and set up your Unsplash application."
+msgstr ""
+
+#: ../../content/applications/websites/website/optimize/unsplash.rst:51
+msgid ""
+"Go to your `applications dashboard "
+"<https://unsplash.com/oauth/applications>`_ and click on your newly created "
+"Unsplash application under **Your applications**."
+msgstr ""
+"Gå til din `applikations instrumentbræt "
+"<https://unsplash.com/oauth/applications>`_ og klik på din nyligt oprettede "
+"Unsplash applikation under **Dine applikationer**."
+
+#: ../../content/applications/websites/website/optimize/unsplash.rst:57
+msgid ""
+"You will be redirected to your application details page. The **application "
+"ID** will be visible in your browser's URL. The URL should be something like"
+" ``https://unsplash.com/oauth/applications/<application_id>``"
+msgstr ""
+"Du vil blive omdirigeret til din applikationsdetaljer side. **Applikations "
+"ID** vil være synligt i din browsers URL. URL bør være noget lig "
+"``https://unsplash.com/oauth/applications/<application_id>``"
+
+#: ../../content/applications/websites/website/optimize/unsplash.rst:65
+msgid ""
+"**As a non-SaaS user**, you won't be able to register for a production "
+"Unsplash key and will be limited to your test key that has a 50 Unsplash "
+"requests per hour restriction."
+msgstr ""
+"**Som en ikke-SaaS bruger**, vil du ikke være i stand til at registrer en "
+"produktions Unsplash nøgle, og vil blive begrænset til din testnøgle, som er"
+" begrænset til 50 Unsplash anmodninger per time."
+
 #: ../../content/applications/websites/website/publish.rst:5
 msgid "Publish"
 msgstr "Publicer"
@@ -3553,7 +3656,7 @@ msgid ""
 msgstr ""
 
 #: ../../content/applications/websites/website/publish/on-premise_geo-ip-installation.rst:36
-msgid ":doc:`CLI documentation </developer/reference/cmdline>`."
+msgid ":doc:`CLI documentation </developer/misc/other/cmdline>`."
 msgstr ""
 
 #: ../../content/applications/websites/website/publish/on-premise_geo-ip-installation.rst:39

locale/de/LC_MESSAGES/applications.po

@@ -1,5 +1,5 @@
 # SOME DESCRIPTIVE TITLE.
-# Copyright (C) 2015-TODAY, Odoo S.A.
+# Copyright (C) Odoo S.A.
 # This file is distributed under the same license as the Odoo package.
 # FIRST AUTHOR <EMAIL@ADDRESS>, YEAR.
 # 
@@ -8,7 +8,7 @@ msgid ""
 msgstr ""
 "Project-Id-Version: Odoo 14.0\n"
 "Report-Msgid-Bugs-To: \n"
-"POT-Creation-Date: 2021-02-04 11:02+0100\n"
+"POT-Creation-Date: 2021-08-10 09:10+0000\n"
 "PO-Revision-Date: 2020-09-22 14:40+0000\n"
 "Language-Team: German (https://www.transifex.com/odoo/teams/41243/de/)\n"
 "MIME-Version: 1.0\n"
@@ -17,6 +17,10 @@ msgstr ""
 "Language: de\n"
 "Plural-Forms: nplurals=2; plural=(n != 1);\n"
 
-#: ../../applications.rst:3
-msgid "Applications"
+#: ../../content/applications.rst:9
+msgid "User Docs"
+msgstr ""
+
+#: ../../content/applications.rst:11
+msgid "Discover our user guides and configuration tutorials per application."
 msgstr ""

locale/de/LC_MESSAGES/index.po

@@ -8,7 +8,7 @@ msgid ""
 msgstr ""
 "Project-Id-Version: Odoo 14.0\n"
 "Report-Msgid-Bugs-To: \n"
-"POT-Creation-Date: 2021-05-18 07:12+0200\n"
+"POT-Creation-Date: 2021-06-14 13:29+0200\n"
 "PO-Revision-Date: 2020-09-22 14:40+0000\n"
 "Language-Team: German (https://www.transifex.com/odoo/teams/41243/de/)\n"
 "MIME-Version: 1.0\n"
@@ -17,6 +17,6 @@ msgstr ""
 "Language: de\n"
 "Plural-Forms: nplurals=2; plural=(n != 1);\n"
 
-#: ../../content/index.rst:3
+#: ../../content/index.rst:5
 msgid "Odoo Documentation"
 msgstr ""

locale/de/LC_MESSAGES/marketing.po

@@ -4,20 +4,20 @@
 # FIRST AUTHOR <EMAIL@ADDRESS>, YEAR.
 # 
 # Translators:
-# Martin Trigaux, 2021
 # JackTheHunter <Maximilian.N98@gmail.com>, 2021
 # Chris Egal <sodaswed@web.de>, 2021
 # Oliver Roch <oliver.roch@d9t.de>, 2021
 # philku79 <philip.kuss@gmx.de>, 2021
+# Martin Trigaux, 2021
 # 
 #, fuzzy
 msgid ""
 msgstr ""
 "Project-Id-Version: Odoo 14.0\n"
 "Report-Msgid-Bugs-To: \n"
-"POT-Creation-Date: 2021-06-14 13:29+0200\n"
+"POT-Creation-Date: 2021-08-10 09:10+0000\n"
 "PO-Revision-Date: 2021-05-18 05:18+0000\n"
-"Last-Translator: philku79 <philip.kuss@gmx.de>, 2021\n"
+"Last-Translator: Martin Trigaux, 2021\n"
 "Language-Team: German (https://www.transifex.com/odoo/teams/41243/de/)\n"
 "MIME-Version: 1.0\n"
 "Content-Type: text/plain; charset=UTF-8\n"
@@ -29,10 +29,16 @@ msgstr ""
 msgid "Marketing"
 msgstr "Marketing"
 
-#: ../../content/applications/marketing/marketing_automation.rst:5
+#: ../../content/applications/marketing/marketing_automation.rst:8
 msgid "Marketing Automation"
 msgstr "Marketing-Automatisierung"
 
+#: ../../content/applications/marketing/marketing_automation.rst:11
+#: ../../content/applications/marketing/sms_marketing.rst:11
+msgid ""
+"`Odoo Tutorials: Marketing <https://www.odoo.com/slides/marketing-27>`_"
+msgstr ""
+
 #: ../../content/applications/marketing/marketing_automation/advanced.rst:5
 msgid "Advanced"
 msgstr "Fortgeschritten"
@@ -60,14 +66,6 @@ msgstr ""
 msgid "Let’s consider the example below:"
 msgstr ""
 
-#: ../../content/applications/marketing/marketing_automation/advanced/understanding_metrics.rstNone
-#: ../../content/applications/marketing/marketing_automation/advanced/understanding_metrics.rstNone
-#: ../../content/applications/marketing/marketing_automation/advanced/understanding_metrics.rstNone
-#: ../../content/applications/marketing/marketing_automation/advanced/understanding_metrics.rst:0
-#: ../../content/applications/marketing/marketing_automation/advanced/understanding_metrics.rstNone
-msgid "Metrics in Odoo Marketing Automation"
-msgstr ""
-
 #: ../../content/applications/marketing/marketing_automation/advanced/understanding_metrics.rst:19
 msgid ""
 "The *Target* - business object - is *Lead/Opportunity* and was narrowed down"
@@ -148,7 +146,7 @@ msgid ""
 "the beginning (parent action)."
 msgstr ""
 
-#: ../../content/applications/marketing/sms_marketing.rst:5
+#: ../../content/applications/marketing/sms_marketing.rst:8
 msgid "SMS Marketing"
 msgstr "SMS Marketing"
 
@@ -184,10 +182,6 @@ msgid ""
 " that includes the following characters:"
 msgstr ""
 
-#: ../../content/applications/marketing/sms_marketing/pricing/pricing_and_faq.rstNone
-msgid "GSM7 in Odoo SMS Marketing"
-msgstr ""
-
 #: ../../content/applications/marketing/sms_marketing/pricing/pricing_and_faq.rst:23
 msgid ""
 "**UNICODE** is the format applied if a special character, that *is not* in "
@@ -215,8 +209,8 @@ msgstr ""
 
 #: ../../content/applications/marketing/sms_marketing/pricing/pricing_and_faq.rst:37
 msgid ""
-"To see the **price per country, please consult**: `Odoo SMS - FAQ <https"
-"://iap-services.odoo.com/iap/sms/pricing#sms_faq_01>`_."
+"To see the **price per country, please consult**: `Odoo SMS - FAQ "
+"<https://iap-services.odoo.com/iap/sms/pricing#sms_faq_01>`_."
 msgstr ""
 
 #: ../../content/applications/marketing/sms_marketing/pricing/pricing_and_faq.rst:39
@@ -225,12 +219,6 @@ msgid ""
 "your database."
 msgstr ""
 
-#: ../../content/applications/marketing/sms_marketing/pricing/pricing_and_faq.rstNone
-#: ../../content/applications/marketing/sms_marketing/pricing/pricing_and_faq.rstNone
-#: ../../content/applications/marketing/sms_marketing/pricing/pricing_and_faq.rstNone
-msgid "SMS pricing and FAQ Odoo SMS Marketing"
-msgstr ""
-
 #: ../../content/applications/marketing/sms_marketing/pricing/pricing_and_faq.rst:49
 msgid "How do I buy credits?"
 msgstr ""
@@ -373,19 +361,23 @@ msgid ""
 "`here <https://www.odoo.com/pricing-packs>`_."
 msgstr ""
 
-#: ../../content/applications/marketing/survey.rst:5
-msgid "Survey"
-msgstr "Umfrage"
+#: ../../content/applications/marketing/surveys.rst:8
+msgid "Surveys"
+msgstr "Umfragen"
 
-#: ../../content/applications/marketing/survey/overview.rst:5
+#: ../../content/applications/marketing/surveys.rst:11
+msgid "`Odoo Tutorials: Surveys <https://www.odoo.com/slides/surveys-62>`_"
+msgstr ""
+
+#: ../../content/applications/marketing/surveys/overview.rst:5
 msgid "Overview"
 msgstr "Übersicht"
 
-#: ../../content/applications/marketing/survey/overview/create.rst:3
+#: ../../content/applications/marketing/surveys/overview/create.rst:3
 msgid "Get Started with Surveys"
 msgstr ""
 
-#: ../../content/applications/marketing/survey/overview/create.rst:5
+#: ../../content/applications/marketing/surveys/overview/create.rst:5
 msgid ""
 "Surveys can be used for a range of purposes that can go from collecting "
 "customer feedback, evaluate the success of an event, measure how pleased "
@@ -394,11 +386,11 @@ msgid ""
 "market is thinking."
 msgstr ""
 
-#: ../../content/applications/marketing/survey/overview/create.rst:11
+#: ../../content/applications/marketing/surveys/overview/create.rst:11
 msgid "Get started"
 msgstr "Beginnen"
 
-#: ../../content/applications/marketing/survey/overview/create.rst:13
+#: ../../content/applications/marketing/surveys/overview/create.rst:13
 msgid ""
 "When creating your survey, choose a *Title* and *Category*. The *Category* "
 "field is used to know in which context the survey is being conducted, as "
@@ -406,20 +398,15 @@ msgid ""
 "recruitment, certification, or employee appraisal."
 msgstr ""
 
-#: ../../content/applications/marketing/survey/overview/create.rstNone
-msgid ""
-"Form view of a survey with a title and category being chosen in Odoo Surveys"
-msgstr ""
-
-#: ../../content/applications/marketing/survey/overview/create.rst:22
+#: ../../content/applications/marketing/surveys/overview/create.rst:22
 msgid "Tab: Questions"
 msgstr ""
 
-#: ../../content/applications/marketing/survey/overview/create.rst:24
+#: ../../content/applications/marketing/surveys/overview/create.rst:24
 msgid "Add sections and questions by clicking on the respective links."
 msgstr ""
 
-#: ../../content/applications/marketing/survey/overview/create.rst:27
+#: ../../content/applications/marketing/surveys/overview/create.rst:27
 msgid ""
 "On the *Sections and Questions* form, once the question type is chosen and "
 "the answer added, under the tab *Options*, enable *Mandatory Answer*, and "
@@ -427,19 +414,19 @@ msgid ""
 "without answering the respective question."
 msgstr ""
 
-#: ../../content/applications/marketing/survey/overview/create.rst:29
+#: ../../content/applications/marketing/surveys/overview/create.rst:29
 msgid ""
 "Depending on the *Question Type*, the tab *Options* aggregates extra and "
 "different possibilities. Examples:"
 msgstr ""
 
-#: ../../content/applications/marketing/survey/overview/create.rst:31
+#: ../../content/applications/marketing/surveys/overview/create.rst:31
 msgid ""
 "*Single Line Text Box* - can choose a minimum and maximum text length "
 "(number of characters - spaces do not count), and its error message."
 msgstr ""
 
-#: ../../content/applications/marketing/survey/overview/create.rst:33
+#: ../../content/applications/marketing/surveys/overview/create.rst:33
 msgid ""
 "*Multiple choice: multiple answers allowed*: choose between radio buttons or"
 " a dropdown menu list, and if you would like to have a comment field. If the"
@@ -448,110 +435,86 @@ msgid ""
 "with which a text type field is displayed."
 msgstr ""
 
-#: ../../content/applications/marketing/survey/overview/create.rst:37
+#: ../../content/applications/marketing/surveys/overview/create.rst:37
 msgid ""
 "*Matrix Type*: choose if you would like to have one or multiple choices per "
 "row."
 msgstr ""
 
-#: ../../content/applications/marketing/survey/overview/create.rstNone
-msgid "Sections and questions view of a survey in Odoo Surveys"
-msgstr ""
-
-#: ../../content/applications/marketing/survey/overview/create.rst:44
+#: ../../content/applications/marketing/surveys/overview/create.rst:44
 msgid "Tab: Description"
 msgstr ""
 
-#: ../../content/applications/marketing/survey/overview/create.rst:46
+#: ../../content/applications/marketing/surveys/overview/create.rst:46
 msgid ""
 "Write a *Description* to be displayed under the title of the survey's "
 "homepage."
 msgstr ""
 
-#: ../../content/applications/marketing/survey/overview/create.rstNone
-msgid ""
-"Frontend of a survey showing the title and description of a survey for Odoo "
-"Surveys"
-msgstr ""
-
-#: ../../content/applications/marketing/survey/overview/create.rst:53
+#: ../../content/applications/marketing/surveys/overview/create.rst:53
 msgid "Click on *Edit* to personalize your pages with the website builder."
 msgstr ""
 
-#: ../../content/applications/marketing/survey/overview/create.rst:56
+#: ../../content/applications/marketing/surveys/overview/create.rst:56
 msgid "Tab: Options"
 msgstr ""
 
-#: ../../content/applications/marketing/survey/overview/create.rst:58
+#: ../../content/applications/marketing/surveys/overview/create.rst:58
 msgid ""
 "Under the tab *Options*, choose the *Layout* of your questions. If choosing "
 "*One page per section* or *One page per question*, an option *Back Button* "
 "becomes available, which allows the user to go back pages."
 msgstr ""
 
-#: ../../content/applications/marketing/survey/overview/create.rstNone
-msgid ""
-"Form view of a survey emphasizing the layout feature under options in Odoo "
-"Surveys"
-msgstr ""
-
-#: ../../content/applications/marketing/survey/overview/create.rst:67
+#: ../../content/applications/marketing/surveys/overview/create.rst:67
 msgid "Test and share the survey"
 msgstr ""
 
-#: ../../content/applications/marketing/survey/overview/create.rst:70
+#: ../../content/applications/marketing/surveys/overview/create.rst:70
 msgid ""
 "Once your Survey is ready, *Test* it to avoid *Sharing* it with potential "
 "errors. As answers get collected, click on *Answers* to access all the "
 "details of the respondent and his answers."
 msgstr ""
 
-#: ../../content/applications/marketing/survey/overview/create.rst:72
+#: ../../content/applications/marketing/surveys/overview/create.rst:72
 msgid ""
 "By default, a filter *Except Test Entries* is applied to keep the list of "
 "entries clean with only real participants."
 msgstr ""
 
-#: ../../content/applications/marketing/survey/overview/create.rstNone
-msgid "View list of the participations of a survey in Odoo Surveys"
-msgstr ""
-
-#: ../../content/applications/marketing/survey/overview/create.rst:79
+#: ../../content/applications/marketing/surveys/overview/create.rst:79
 msgid ""
 "Another way to access detailed answers is by going to "
 ":menuselection:`Participations --> Participations`."
 msgstr ""
 
-#: ../../content/applications/marketing/survey/overview/create.rst:80
+#: ../../content/applications/marketing/surveys/overview/create.rst:80
 msgid "Click on *See results* to be redirected to an analytical page."
 msgstr ""
 
-#: ../../content/applications/marketing/survey/overview/create.rstNone
-msgid "View of an analytical page for Odoo Surveys"
-msgstr ""
-
-#: ../../content/applications/marketing/survey/overview/create.rst:87
-#: ../../content/applications/marketing/survey/overview/time_random.rst:34
+#: ../../content/applications/marketing/surveys/overview/create.rst:87
+#: ../../content/applications/marketing/surveys/overview/time_random.rst:34
 msgid ":doc:`scoring`"
 msgstr ""
 
-#: ../../content/applications/marketing/survey/overview/create.rst:88
-#: ../../content/applications/marketing/survey/overview/scoring.rst:35
+#: ../../content/applications/marketing/surveys/overview/create.rst:88
+#: ../../content/applications/marketing/surveys/overview/scoring.rst:35
 msgid ":doc:`time_random`"
 msgstr ""
 
-#: ../../content/applications/marketing/survey/overview/scoring.rst:3
+#: ../../content/applications/marketing/surveys/overview/scoring.rst:3
 msgid "Scoring Surveys"
 msgstr ""
 
-#: ../../content/applications/marketing/survey/overview/scoring.rst:5
+#: ../../content/applications/marketing/surveys/overview/scoring.rst:5
 msgid ""
 "To measure your respondent’s performance, knowledge of a subject, or overall"
 " satisfaction, attach points to the answers of specific questions. The "
 "points are summed up to give your respondent a final score."
 msgstr ""
 
-#: ../../content/applications/marketing/survey/overview/scoring.rst:9
+#: ../../content/applications/marketing/surveys/overview/scoring.rst:9
 msgid ""
 "On your survey’s form, click on *Add a question* and, under the tab "
 "*Options*, choose between *Scoring with answers at the end* or *Scoring "
@@ -559,11 +522,7 @@ msgid ""
 "answer and score."
 msgstr ""
 
-#: ../../content/applications/marketing/survey/overview/scoring.rstNone
-msgid "Form view of a survey showing a list of answers in Odoo Surveys"
-msgstr ""
-
-#: ../../content/applications/marketing/survey/overview/scoring.rst:17
+#: ../../content/applications/marketing/surveys/overview/scoring.rst:17
 msgid ""
 "Set the percentage score the user needs to achieve to have successfully "
 "taken the survey. If enabling *Certificate*, choose its template. The "
@@ -571,13 +530,7 @@ msgid ""
 "finish it."
 msgstr ""
 
-#: ../../content/applications/marketing/survey/overview/scoring.rstNone
-msgid ""
-"Form view of a survey emphasizing the scoring and candidates section in Odoo"
-" Surveys"
-msgstr ""
-
-#: ../../content/applications/marketing/survey/overview/scoring.rst:25
+#: ../../content/applications/marketing/surveys/overview/scoring.rst:25
 msgid ""
 "Enable *Login required* to be able to *Give Badges*. Badges are related to "
 "the eLearning section of your website. Besides the logged-in user, visitors "
@@ -585,21 +538,15 @@ msgid ""
 "badges."
 msgstr ""
 
-#: ../../content/applications/marketing/survey/overview/scoring.rstNone
-msgid ""
-"View of the courses tab emphasizing the latest achievements section on the website for\n"
-"Odoo Surveys"
-msgstr ""
-
-#: ../../content/applications/marketing/survey/overview/time_random.rst:3
+#: ../../content/applications/marketing/surveys/overview/time_random.rst:3
 msgid "Time and Randomize Questions"
 msgstr ""
 
-#: ../../content/applications/marketing/survey/overview/time_random.rst:6
+#: ../../content/applications/marketing/surveys/overview/time_random.rst:6
 msgid "Time Limit"
 msgstr "Zeitlimit"
 
-#: ../../content/applications/marketing/survey/overview/time_random.rst:10
+#: ../../content/applications/marketing/surveys/overview/time_random.rst:10
 msgid ""
 "On timed surveys, respondents need to complete the survey within a certain "
 "period of time. It can be used to ensure that all respondents get the same "
@@ -607,42 +554,31 @@ msgid ""
 " looking at external resources."
 msgstr ""
 
-#: ../../content/applications/marketing/survey/overview/time_random.rst:11
+#: ../../content/applications/marketing/surveys/overview/time_random.rst:11
 msgid "Set the *Time limit* under the tab *Options*."
 msgstr ""
 
-#: ../../content/applications/marketing/survey/overview/time_random.rstNone
-msgid ""
-"View of a survey form emphasizing the time limit feature in Odoo Surveys"
-msgstr ""
-
-#: ../../content/applications/marketing/survey/overview/time_random.rst:17
+#: ../../content/applications/marketing/surveys/overview/time_random.rst:17
 msgid ""
 "A timer is shown on the pages so the user can keep track of the remaining "
 "time. Surveys not \\ submitted by the *Time limit* do not have their answers"
 " saved."
 msgstr ""
 
-#: ../../content/applications/marketing/survey/overview/time_random.rst:21
+#: ../../content/applications/marketing/surveys/overview/time_random.rst:21
 msgid "Selection"
 msgstr "Auswahl"
 
-#: ../../content/applications/marketing/survey/overview/time_random.rst:25
+#: ../../content/applications/marketing/surveys/overview/time_random.rst:25
 msgid ""
 "When you randomize a survey, you allow for the questions to be shuffled in a"
 " random order every time someone opens the questionnaire. This can be useful"
 " to avoid having respondents looking at each others' answers."
 msgstr ""
 
-#: ../../content/applications/marketing/survey/overview/time_random.rst:27
+#: ../../content/applications/marketing/surveys/overview/time_random.rst:27
 msgid ""
 "To do so, under the tab *Options*, enable *Randomized per section*. Now, "
 "under the tab *Questions*, set how many of the questions in that section "
 "should be taken into account during the shuffling."
 msgstr ""
-
-#: ../../content/applications/marketing/survey/overview/time_random.rstNone
-msgid ""
-"View of a survey form emphasizing the random questions count column in Odoo "
-"Surveys"
-msgstr ""

locale/de/LC_MESSAGES/productivity.po

@@ -15,7 +15,7 @@ msgid ""
 msgstr ""
 "Project-Id-Version: Odoo 14.0\n"
 "Report-Msgid-Bugs-To: \n"
-"POT-Creation-Date: 2021-06-14 13:29+0200\n"
+"POT-Creation-Date: 2021-08-10 09:10+0000\n"
 "PO-Revision-Date: 2021-05-18 05:18+0000\n"
 "Last-Translator: e2f <projects@e2f.com>, 2021\n"
 "Language-Team: German (https://www.transifex.com/odoo/teams/41243/de/)\n"
@@ -29,7 +29,7 @@ msgstr ""
 msgid "Productivity"
 msgstr "Produktivität"
 
-#: ../../content/applications/productivity/discuss.rst:5
+#: ../../content/applications/productivity/discuss.rst:8
 msgid "Discuss"
 msgstr "Diskussion"
 
@@ -334,8 +334,8 @@ msgstr ""
 
 #: ../../content/applications/productivity/discuss/advanced/email_servers.rst:176
 msgid ""
-"Projects (to create new Tasks in `Odoo Project <https://www.odoo.com/page"
-"/project-management>`__),"
+"Projects (to create new Tasks in `Odoo Project "
+"<https://www.odoo.com/page/project-management>`__),"
 msgstr ""
 
 #: ../../content/applications/productivity/discuss/advanced/email_servers.rst:178
@@ -489,10 +489,6 @@ msgid ""
 "job applicants."
 msgstr ""
 
-#: ../../content/applications/productivity/discuss/advanced/email_template.rstNone
-msgid "New email template form in Odoo"
-msgstr ""
-
 #: ../../content/applications/productivity/discuss/advanced/email_template.rst:30
 msgid ""
 "Under *Email Configuration*, fields such as *From*, *To (Emails)*, *To "
@@ -522,21 +518,12 @@ msgid ""
 "would like to use."
 msgstr ""
 
-#: ../../content/applications/productivity/discuss/advanced/email_template.rstNone
-msgid ""
-"View of the dynamic placeholder generator tab under a new template in Odoo"
-msgstr ""
-
 #: ../../content/applications/productivity/discuss/advanced/email_template.rst:45
 msgid ""
 "Next, copy the *Placeholder Expression* and paste it in the *Body* of the "
 "email, under the *Content* tab, using - essentially - the *Code View*."
 msgstr ""
 
-#: ../../content/applications/productivity/discuss/advanced/email_template.rstNone
-msgid "View of the body code view under the content tab in Odoo"
-msgstr ""
-
 #: ../../content/applications/productivity/discuss/advanced/email_template.rst:52
 msgid ""
 "Deactivate the *Code View* option by simply clicking on it again, and easily"
@@ -544,10 +531,6 @@ msgid ""
 "sending it."
 msgstr ""
 
-#: ../../content/applications/productivity/discuss/advanced/email_template.rstNone
-msgid "View of the content with the standard body view in Odoo"
-msgstr ""
-
 #: ../../content/applications/productivity/discuss/overview.rst:5
 msgid "Overview"
 msgstr "Übersicht"
@@ -575,10 +558,6 @@ msgid ""
 "to be handled."
 msgstr ""
 
-#: ../../content/applications/productivity/discuss/overview/get_started.rstNone
-msgid "View of the preferences page for Odoo Discuss"
-msgstr ""
-
 #: ../../content/applications/productivity/discuss/overview/get_started.rst:21
 msgid ""
 "By default, the field is set as *Handle by Emails* making messages, notes, "
@@ -590,20 +569,12 @@ msgstr ""
 msgid "Messages can then be *Marked as Todo*, *Replied*, or *Marked as Read*."
 msgstr ""
 
-#: ../../content/applications/productivity/discuss/overview/get_started.rstNone
-msgid "View of an inbox message and its action options in Odoo Discuss"
-msgstr ""
-
 #: ../../content/applications/productivity/discuss/overview/get_started.rst:28
 msgid ""
 "The messages tagged as *Mark as Todo* are also shown in *Starred*, while the"
 " ones *Marked as Read* are moved to *History*."
 msgstr ""
 
-#: ../../content/applications/productivity/discuss/overview/get_started.rstNone
-msgid "View of messages marked as todo in Odoo Discuss"
-msgstr ""
-
 #: ../../content/applications/productivity/discuss/overview/get_started.rst:36
 msgid "Start Chatting"
 msgstr ""
@@ -616,12 +587,6 @@ msgid ""
 " of where you are in Odoo."
 msgstr ""
 
-#: ../../content/applications/productivity/discuss/overview/get_started.rstNone
-msgid ""
-"View of the messages under the messaging menu emphasizing the request for push\n"
-"notifications for Odoo Discuss"
-msgstr ""
-
 #: ../../content/applications/productivity/discuss/overview/get_started.rst:48
 msgid ""
 "To stop receiving desktop notifications, reset the notifications settings of"
@@ -634,12 +599,6 @@ msgid ""
 "*Discuss* and send a *Direct Message*."
 msgstr ""
 
-#: ../../content/applications/productivity/discuss/overview/get_started.rstNone
-msgid ""
-"View of discuss’s panel emphasizing the titles channels and direct messages "
-"in Odoo Discuss"
-msgstr ""
-
 #: ../../content/applications/productivity/discuss/overview/get_started.rst:58
 msgid ""
 "You can also create :doc:`public and private channels <team_communication>`."
@@ -661,10 +620,6 @@ msgid ""
 "through email, depending on his settings."
 msgstr ""
 
-#: ../../content/applications/productivity/discuss/overview/get_started.rstNone
-msgid "View of a couple of chat window messages for Odoo Discuss"
-msgstr ""
-
 #: ../../content/applications/productivity/discuss/overview/get_started.rst:73
 msgid ""
 "When a user is mentioned, the search list (list of names) suggests values "
@@ -701,10 +656,6 @@ msgstr ""
 msgid "Airplane = out of the office"
 msgstr ""
 
-#: ../../content/applications/productivity/discuss/overview/get_started.rstNone
-msgid "View of the contacts’ status for Odoo Discuss"
-msgstr ""
-
 #: ../../content/applications/productivity/discuss/overview/get_started.rst:95
 #: ../../content/applications/productivity/discuss/overview/plan_activities.rst:65
 msgid ":doc:`team_communication`"
@@ -736,11 +687,6 @@ msgid ""
 "*Activities* menu."
 msgstr ""
 
-#: ../../content/applications/productivity/discuss/overview/plan_activities.rstNone
-msgid ""
-"View of crm leads page emphasizing the activities menu for Odoo Discuss"
-msgstr ""
-
 #: ../../content/applications/productivity/discuss/overview/plan_activities.rst:20
 msgid "Plan activities"
 msgstr ""
@@ -751,11 +697,6 @@ msgid ""
 "*Schedule activity*, or through Kanban views."
 msgstr ""
 
-#: ../../content/applications/productivity/discuss/overview/plan_activities.rstNone
-msgid ""
-"View of crm leads and the option to schedule an activity for Odoo Discuss"
-msgstr ""
-
 #: ../../content/applications/productivity/discuss/overview/plan_activities.rst:31
 msgid "Set your activity types"
 msgstr ""
@@ -767,12 +708,6 @@ msgid ""
 ":menuselection:`Settings --> Activity types`."
 msgstr ""
 
-#: ../../content/applications/productivity/discuss/overview/plan_activities.rstNone
-msgid ""
-"View of the settings page emphasizing the menu activity types for Odoo "
-"Discuss"
-msgstr ""
-
 #: ../../content/applications/productivity/discuss/overview/plan_activities.rst:42
 msgid ""
 "If you need to create an activity type with an available calendar, make sure"
@@ -789,24 +724,12 @@ msgid ""
 "*Recommended Next Activities*."
 msgstr ""
 
-#: ../../content/applications/productivity/discuss/overview/plan_activities.rstNone
-msgid ""
-"View of an activity type form emphasizing the field recommended next activities for Odoo\n"
-"Discuss"
-msgstr ""
-
 #: ../../content/applications/productivity/discuss/overview/plan_activities.rst:55
 msgid ""
 "Once the respective activity is completed, select *Done & Schedule Next* and"
 " next steps are suggested to you."
 msgstr ""
 
-#: ../../content/applications/productivity/discuss/overview/plan_activities.rstNone
-msgid ""
-"View of an activity being schedule emphasizing the recommended activities field being\n"
-"shown for Odoo Discuss"
-msgstr ""
-
 #: ../../content/applications/productivity/discuss/overview/plan_activities.rst:64
 #: ../../content/applications/productivity/discuss/overview/team_communication.rst:115
 msgid ":doc:`get_started`"
@@ -834,10 +757,6 @@ msgid ""
 "visible to users invited to it."
 msgstr ""
 
-#: ../../content/applications/productivity/discuss/overview/team_communication.rstNone
-msgid "View of discuss’s sidebar and a channel being created in Odo Discuss"
-msgstr ""
-
 #: ../../content/applications/productivity/discuss/overview/team_communication.rst:21
 msgid ""
 "A public channel is best used when many employees need to access information"
@@ -856,10 +775,6 @@ msgid ""
 " clicking on the *Channel Settings* icon on the sidebar."
 msgstr ""
 
-#: ../../content/applications/productivity/discuss/overview/team_communication.rstNone
-msgid "View of a channel’s settings form in Odoo Discuss"
-msgstr ""
-
 #: ../../content/applications/productivity/discuss/overview/team_communication.rst:36
 msgid "Privacy and Members"
 msgstr ""
@@ -879,12 +794,6 @@ msgid ""
 "*Invite*."
 msgstr ""
 
-#: ../../content/applications/productivity/discuss/overview/team_communication.rstNone
-msgid ""
-"View of Discuss’ sidebar emphasizing the option to invite members in Odoo "
-"Discuss"
-msgstr ""
-
 #: ../../content/applications/productivity/discuss/overview/team_communication.rst:49
 msgid ""
 "For *Selected group of users*, the option *Auto Subscribe Groups* "
@@ -910,10 +819,6 @@ msgid ""
 "messages will need to be approved before being sent."
 msgstr ""
 
-#: ../../content/applications/productivity/discuss/overview/team_communication.rstNone
-msgid "View of a message with a pending moderation status in Odoo Discuss"
-msgstr ""
-
 #: ../../content/applications/productivity/discuss/overview/team_communication.rst:66
 msgid ""
 "Under the *Moderation* tab choose as many moderators as you need, and if you"
@@ -926,22 +831,12 @@ msgid ""
 " to newcomers."
 msgstr ""
 
-#: ../../content/applications/productivity/discuss/overview/team_communication.rstNone
-msgid ""
-"View of a channel’s settings form emphasizing the tab moderation in Odoo "
-"Discuss"
-msgstr ""
-
 #: ../../content/applications/productivity/discuss/overview/team_communication.rst:73
 msgid ""
 "Moderators can: *Accept*, *Reject*, *Discard*, *Always Allow* or *Ban* "
 "messages."
 msgstr ""
 
-#: ../../content/applications/productivity/discuss/overview/team_communication.rstNone
-msgid "View of a message to be moderated in Odoo Discuss"
-msgstr ""
-
 #: ../../content/applications/productivity/discuss/overview/team_communication.rst:80
 msgid ""
 "Members of a mailing channel receive messages through email regardless of "
@@ -954,12 +849,6 @@ msgid ""
 "addresses per moderated channel to auto-ban them from sending messages."
 msgstr ""
 
-#: ../../content/applications/productivity/discuss/overview/team_communication.rstNone
-msgid ""
-"View of a channel’s setting form emphasizing the ban Lists menu in Odoo "
-"Discuss"
-msgstr ""
-
 #: ../../content/applications/productivity/discuss/overview/team_communication.rst:91
 msgid "Quick search bar"
 msgstr ""
@@ -972,12 +861,6 @@ msgid ""
 " and quickly find the one you need."
 msgstr ""
 
-#: ../../content/applications/productivity/discuss/overview/team_communication.rstNone
-msgid ""
-"View of the Discuss’ sidebar emphasizing the quick search bar in Odoo "
-"Discuss"
-msgstr ""
-
 #: ../../content/applications/productivity/discuss/overview/team_communication.rst:103
 msgid "Finding channels"
 msgstr ""
@@ -995,15 +878,11 @@ msgid ""
 "single character."
 msgstr ""
 
-#: ../../content/applications/productivity/discuss/overview/team_communication.rstNone
-msgid "View of a channel being searched through filters in Odoo Discuss"
-msgstr ""
-
 #: ../../content/applications/productivity/discuss/overview/team_communication.rst:116
 msgid ":doc:`plan_activities`"
 msgstr ""
 
-#: ../../content/applications/productivity/iot.rst:5
+#: ../../content/applications/productivity/iot.rst:8
 msgid "Internet of Things (IoT)"
 msgstr ""
 
@@ -1086,8 +965,9 @@ msgstr ""
 #: ../../content/applications/productivity/iot/config/connect.rst:60
 msgid ""
 "If you are on Runbot, do not forget to add the -all or -base in the token "
-"(e.g. this token **http://375228-saas-11-5-iot-"
-"f3f920.runbot16.odoo.com\\|4957098401** should become "
+"(e.g. this token "
+"**http://375228-saas-11-5-iot-f3f920.runbot16.odoo.com\\|4957098401** should"
+" become "
 "**http://375228-saas-11-5-iot-f3f920-all.runbot16.odoo.com\\|4957098401**)."
 msgstr ""
 
@@ -1804,13 +1684,10 @@ msgstr ""
 
 #: ../../content/applications/productivity/iot/devices/scale.rst:17
 msgid ""
-"If your scale is `compatibale with Odoo IoT Box <https://www.odoo.com/page"
-"/iot-hardware>`_, there is no need to set up anything because it will be "
-"automatically detected as soon as it is connected."
-msgstr ""
-
-#: ../../content/applications/productivity/iot/devices/scale.rstNone
-msgid "IOT box auto detection."
+"If your scale is `compatibale with Odoo IoT Box "
+"<https://www.odoo.com/page/iot-hardware>`_, there is no need to set up "
+"anything because it will be automatically detected as soon as it is "
+"connected."
 msgstr ""
 
 #: ../../content/applications/productivity/iot/devices/scale.rst:24
@@ -1820,10 +1697,6 @@ msgid ""
 "*drivers list*. Then, click on load drivers."
 msgstr ""
 
-#: ../../content/applications/productivity/iot/devices/scale.rstNone
-msgid "View of the IoT box settings and driver list."
-msgstr ""
-
 #: ../../content/applications/productivity/iot/devices/scale.rst:32
 msgid "Use a Scale in Point of Sale"
 msgstr ""
@@ -1835,20 +1708,12 @@ msgid ""
 "configure, then click on *Edit* and enable the *IoT Box* feature."
 msgstr ""
 
-#: ../../content/applications/productivity/iot/devices/scale.rstNone
-msgid "View of the IoT box feature inside of the PoS settings."
-msgstr ""
-
 #: ../../content/applications/productivity/iot/devices/scale.rst:42
 msgid ""
 "Now, choose the *IoT Box* in the dropdown menu and check the *Electronic "
 "Scale* option. Then, you hit save."
 msgstr ""
 
-#: ../../content/applications/productivity/iot/devices/scale.rstNone
-msgid "List of the external tools that can be used with PoS and the IoT box."
-msgstr ""
-
 #: ../../content/applications/productivity/iot/devices/scale.rst:49
 msgid ""
 "The scale is now available in all your *PoS* sessions. Then, if a product "
@@ -1857,14 +1722,20 @@ msgid ""
 "price to the cart."
 msgstr ""
 
-#: ../../content/applications/productivity/iot/devices/scale.rstNone
-msgid "Electronic Scale dashboard view when no items are being weighed."
-msgstr ""
-
-#: ../../content/applications/productivity/studio.rst:5
+#: ../../content/applications/productivity/studio.rst:8
 msgid "Studio"
 msgstr "Studio"
 
+#: ../../content/applications/productivity/studio.rst:10
+msgid ""
+"Learn all you need in order to build custom applications: customize views, "
+"create specific reports, automate actions, define approval workflows, etc."
+msgstr ""
+
+#: ../../content/applications/productivity/studio.rst:14
+msgid "`Odoo Tutorials: Studio <https://www.odoo.com/slides/studio-31>`_"
+msgstr ""
+
 #: ../../content/applications/productivity/studio/concepts.rst:5
 msgid "Concepts"
 msgstr ""
@@ -1887,10 +1758,6 @@ msgid ""
 "changing stage if a field is not filled in."
 msgstr ""
 
-#: ../../content/applications/productivity/studio/concepts/understanding_automated_actions.rstNone
-msgid "Flowchart to exemplify an automated action rule for Odoo Studio"
-msgstr ""
-
 #: ../../content/applications/productivity/studio/concepts/understanding_automated_actions.rst:16
 msgid ""
 "Let's understand how to properly define *when* an automated action runs and "
@@ -2029,10 +1896,6 @@ msgid ""
 "goes through:"
 msgstr ""
 
-#: ../../content/applications/productivity/studio/concepts/understanding_automated_actions.rstNone
-msgid "View of an automated action being created in Odoo Studio"
-msgstr ""
-
 #: ../../content/applications/productivity/studio/concepts/understanding_automated_actions.rst:65
 msgid "The user creates the record without an email address set."
 msgstr ""
@@ -2124,12 +1987,6 @@ msgid ""
 "step."
 msgstr ""
 
-#: ../../content/applications/productivity/studio/concepts/understanding_general.rstNone
-msgid ""
-"Overview of the main dashboard emphasizing the option to create a new app in"
-" Odoo Studio"
-msgstr ""
-
 #: ../../content/applications/productivity/studio/concepts/understanding_general.rst:38
 msgid "What is a Model (also called Object)?"
 msgstr ""
@@ -2188,10 +2045,6 @@ msgid ""
 "In Odoo, relational field types are: *One2many*, *Many2one*, *Many2many*."
 msgstr ""
 
-#: ../../content/applications/productivity/studio/concepts/understanding_general.rstNone
-msgid "Tables with a visual explanation of related fields for Odoo Studio"
-msgstr ""
-
 #: ../../content/applications/productivity/studio/concepts/understanding_general.rst:66
 msgid ""
 "An **One2many** field is a *one-way* direction of selecting *multiple* "
@@ -2253,10 +2106,6 @@ msgid ""
 "menus (models) and rearrange their hierarchy, click on *Edit Menu*."
 msgstr ""
 
-#: ../../content/applications/productivity/studio/concepts/understanding_general.rstNone
-msgid "Overview of a menu being edit in Odoo Studio"
-msgstr ""
-
 #: ../../content/applications/productivity/studio/concepts/understanding_general.rst:95
 msgid "`Studio Basics <https://www.odoo.com/fr_FR/slides/studio-31>`_"
 msgstr ""
@@ -2282,10 +2131,6 @@ msgid ""
 "*customizations.zip*."
 msgstr ""
 
-#: ../../content/applications/productivity/studio/how_to/export_import.rstNone
-msgid "View of the menu customizations in Odoo Studio"
-msgstr ""
-
 #: ../../content/applications/productivity/studio/how_to/export_import.rst:16
 msgid ""
 "The module created contains the definition of custom models and fields, as "
@@ -2299,10 +2144,6 @@ msgid ""
 " *Import*."
 msgstr ""
 
-#: ../../content/applications/productivity/studio/how_to/export_import.rstNone
-msgid "View of the import modules window for Odoo Studio"
-msgstr ""
-
 #: ../../content/applications/productivity/studio/how_to/export_import.rst:25
 msgid ""
 "Studio does not know which apps are customized (because the same view can be"
@@ -2323,13 +2164,6 @@ msgid ""
 "software fun to use, and rewarding, for employees."
 msgstr ""
 
-#: ../../content/applications/productivity/studio/how_to/rainbow_man.rstNone
-#: ../../content/applications/productivity/studio/how_to/rainbow_man.rstNone
-msgid ""
-"View of a sales form and the tab properties and its rainbow man field in "
-"Odoo Studio"
-msgstr ""
-
 #: ../../content/applications/productivity/studio/how_to/rainbow_man.rst:13
 msgid ""
 "On most buttons in Odoo, such as *Send by Email*, *Confirm* or *Cancel*, "
@@ -2378,10 +2212,6 @@ msgid ""
 " email address, etc.)."
 msgstr ""
 
-#: ../../content/applications/productivity/studio/how_to/reports.rstNone
-msgid "View of the types of new reports in Odoo Studio"
-msgstr ""
-
 #: ../../content/applications/productivity/studio/how_to/reports.rst:17
 msgid ""
 "Under the tab **Add**, you find the fields to be dragged and dropped to the "
@@ -2391,10 +2221,6 @@ msgid ""
 " *Image*, and *Text in Cell* are static elements."
 msgstr ""
 
-#: ../../content/applications/productivity/studio/how_to/reports.rstNone
-msgid "View of a report and the tab add in Odoo Studio"
-msgstr ""
-
 #: ../../content/applications/productivity/studio/how_to/reports.rst:26
 msgid ""
 "Once the element is added to the view, select it to see its **Options**. The"
@@ -2403,10 +2229,6 @@ msgid ""
 "objects have their directives shown on *Field Expression*."
 msgstr ""
 
-#: ../../content/applications/productivity/studio/how_to/reports.rstNone
-msgid "View of a report and the tab options in Odoo Studio"
-msgstr ""
-
 #: ../../content/applications/productivity/studio/how_to/reports.rst:34
 msgid ""
 "Under **Visible if**, define the rule(s) to set visibility conditions to "
@@ -2429,12 +2251,6 @@ msgid ""
 "groups do not see the same final document."
 msgstr ""
 
-#: ../../content/applications/productivity/studio/how_to/reports.rstNone
-msgid ""
-"View of a report’s settings emphasizing the field limit visibility to groups"
-" in Odoo Studio"
-msgstr ""
-
 #: ../../content/applications/productivity/studio/how_to/reports.rst:46
 msgid ""
 "Under the **Report** tab, name your report, choose the paper format, and if "
@@ -2442,10 +2258,6 @@ msgid ""
 "document form."
 msgstr ""
 
-#: ../../content/applications/productivity/studio/how_to/reports.rstNone
-msgid "View of an invoice form emphasizing the menu print for Odoo Studio"
-msgstr ""
-
 #: ../../content/applications/productivity/studio/how_to/reports.rst:53
 msgid ""
 "If activating the :ref:`developer mode <developer-mode>`, additional fields "
@@ -2476,12 +2288,6 @@ msgid ""
 " have closed Studio, changes can not be undone anymore."
 msgstr ""
 
-#: ../../content/applications/productivity/studio/how_to/reports.rst:0
-msgid ""
-"View of a report being built and emphasizing the undo and redo buttons in "
-"Odoo Studio"
-msgstr ""
-
 #: ../../content/applications/productivity/studio/use_cases.rst:5
 msgid "Use Cases"
 msgstr "Anwendungsfälle"
@@ -2525,12 +2331,6 @@ msgstr ""
 msgid "*Data to Write*: Lead/Opportunity > Value > 3"
 msgstr ""
 
-#: ../../content/applications/productivity/studio/use_cases/automated_actions.rstNone
-msgid ""
-"View of an automated action that sets a high priority to Belgian leads in "
-"Odoo Studio"
-msgstr ""
-
 #: ../../content/applications/productivity/studio/use_cases/automated_actions.rst:22
 msgid ""
 "Check :doc:`this doc <filters_status_bar>` in order to have another "
@@ -2565,22 +2365,12 @@ msgid ""
 " *Use by default* and *Save*."
 msgstr ""
 
-#: ../../content/applications/productivity/studio/use_cases/filters_status_bar.rstNone
-msgid "View of a custom filter being set to be used by default in Odoo"
-msgstr ""
-
 #: ../../content/applications/productivity/studio/use_cases/filters_status_bar.rst:15
 msgid ""
 "On *Filter Rules* in Studio mode, select the respective filter and enable "
 "*Default Filter*."
 msgstr ""
 
-#: ../../content/applications/productivity/studio/use_cases/filters_status_bar.rstNone
-msgid ""
-"View of a filter’s rule form emphasizing the field default filter in Odoo "
-"Studio"
-msgstr ""
-
 #: ../../content/applications/productivity/studio/use_cases/filters_status_bar.rst:21
 msgid ""
 "**Case scenario 2: add a status bar on the product form to manage its life "
@@ -2601,10 +2391,6 @@ msgid ""
 "*Default Group by* as *Pipeline status bar*."
 msgstr ""
 
-#: ../../content/applications/productivity/studio/use_cases/filters_status_bar.rstNone
-msgid "Form view emphasizing the button add a pipeline bar in Odoo Studio"
-msgstr ""
-
 #: ../../content/applications/productivity/studio/use_cases/filters_status_bar.rst:34
 msgid ""
 "Now, open your product form and set the right status for that product. As "
@@ -2618,10 +2404,6 @@ msgid ""
 "go back to *Form View*."
 msgstr ""
 
-#: ../../content/applications/productivity/studio/use_cases/filters_status_bar.rst:0
-msgid "View of Studio emphasizing the form view button in Odoo Studio"
-msgstr ""
-
 #: ../../content/applications/productivity/studio/use_cases/filters_status_bar.rst:44
 msgid ""
 "**Case scenario 2.a: when a product goes from ‘In use’ to ‘Deprecate’, set "
@@ -2654,12 +2436,6 @@ msgstr ""
 msgid "*Data to Write*: Cost (Product Template) > Value > 0"
 msgstr ""
 
-#: ../../content/applications/productivity/studio/use_cases/filters_status_bar.rstNone
-msgid ""
-"View of the automated action created to set the price of a product to zero "
-"in Odoo Studio"
-msgstr ""
-
 #: ../../content/applications/productivity/studio/use_cases/models_fields.rst:3
 msgid "Advanced Use Cases: Creating Models and Adding Fields"
 msgstr ""
@@ -2685,10 +2461,6 @@ msgstr ""
 msgid "You can now hide the related field created (*Country*) if you wish."
 msgstr ""
 
-#: ../../content/applications/productivity/studio/use_cases/models_fields.rstNone
-msgid "View of the invisibility domain of a field being set in Odoo Studio"
-msgstr ""
-
 #: ../../content/applications/productivity/studio/use_cases/models_fields.rst:19
 msgid ""
 "Another approach is to use the country’s ID. To do so, go to "
@@ -2706,11 +2478,6 @@ msgstr ""
 msgid "Again, hide the related field with the country’s ID if you prefer."
 msgstr ""
 
-#: ../../content/applications/productivity/studio/use_cases/models_fields.rstNone
-msgid ""
-"View of an URL emphasizing where a country’s ID can be found for Odoo Studio"
-msgstr ""
-
 #: ../../content/applications/productivity/studio/use_cases/models_fields.rst:28
 msgid ""
 "**Case scenario 2: create a model called 'Properties' and add fields called:"
@@ -2724,10 +2491,6 @@ msgid ""
 " on its form, drag & drop the necessary fields."
 msgstr ""
 
-#: ../../content/applications/productivity/studio/use_cases/models_fields.rstNone
-msgid "View of the recommended fields for an object in Odoo Studio"
-msgstr ""
-
 #: ../../content/applications/productivity/studio/use_cases/models_fields.rst:39
 msgid ""
 "**Case scenario 2.a: now, you would like to have a model called 'Regions' to"
@@ -2753,11 +2516,6 @@ msgid ""
 " in the view."
 msgstr ""
 
-#: ../../content/applications/productivity/studio/use_cases/models_fields.rst:0
-#: ../../content/applications/productivity/studio/use_cases/models_fields.rstNone
-msgid "Form view and a Many2one field being dropped in Odoo Studio"
-msgstr ""
-
 #: ../../content/applications/productivity/studio/use_cases/models_fields.rst:60
 msgid ""
 "Now, go to the model *Regions*, select the form view, and add a status "
@@ -2770,20 +2528,12 @@ msgid ""
 " records on the related model, and allow you to access them."
 msgstr ""
 
-#: ../../content/applications/productivity/studio/use_cases/models_fields.rstNone
-msgid "Form view and the status button window being shown in Odoo Studio"
-msgstr ""
-
 #: ../../content/applications/productivity/studio/use_cases/models_fields.rst:69
 msgid ""
 "When searching for relations, click on *Search more* and filter it by "
 "*Custom*. This way you avoid creating duplicates."
 msgstr ""
 
-#: ../../content/applications/productivity/studio/use_cases/models_fields.rst:0
-msgid "View of the search model window in Odoo Studio"
-msgstr ""
-
 #: ../../content/applications/productivity/studio/use_cases/models_fields.rst:76
 msgid ""
 "**Case scenario 2.b: in the model 'Properties', show all the tags as "
@@ -2796,10 +2546,6 @@ msgid ""
 "*Properties > Widgets*, choose *Checkboxes*."
 msgstr ""
 
-#: ../../content/applications/productivity/studio/use_cases/models_fields.rstNone
-msgid "Form view showing the widgets available in Odoo Studio"
-msgstr ""
-
 #: ../../content/applications/productivity/studio/use_cases/models_fields.rst:85
 msgid ""
 "**Case scenario 3: on the leads’ form, add a selection field with the "
@@ -2814,10 +2560,6 @@ msgid ""
 "another 2 times for *Checkboxes* and *Tags*."
 msgstr ""
 
-#: ../../content/applications/productivity/studio/use_cases/models_fields.rstNone
-msgid "Form view emphasizing the widget property in Odoo Studio"
-msgstr ""
-
 #: ../../content/applications/productivity/studio/use_cases/models_fields.rst:96
 msgid "Now, add a *Selection* field and the necessary values."
 msgstr ""
@@ -2830,12 +2572,6 @@ msgid ""
 "not = > Tags.*"
 msgstr ""
 
-#: ../../content/applications/productivity/studio/use_cases/models_fields.rstNone
-msgid ""
-"Form view emphasizing a field added and its invisibility properties in Odoo "
-"Studio"
-msgstr ""
-
 #: ../../content/applications/productivity/studio/use_cases/models_fields.rst:105
 msgid ""
 "**Case scenario 4: on a quotation’s form, add a selection field called "
@@ -2851,10 +2587,6 @@ msgid ""
 "the *Limit visibility to groups* as *Sales / Administrator* or managers."
 msgstr ""
 
-#: ../../content/applications/productivity/studio/use_cases/models_fields.rstNone
-msgid "Form view of a required domain being set in Odoo Studio"
-msgstr ""
-
 #: ../../content/applications/productivity/studio/use_cases/models_fields.rst:117
 msgid "**Case scenario 5: change the tooltip of a field for all views.**"
 msgstr ""
@@ -2871,12 +2603,6 @@ msgid ""
 "written is displayed on all views forms where the field is added."
 msgstr ""
 
-#: ../../content/applications/productivity/studio/use_cases/models_fields.rstNone
-msgid ""
-"Form view showing more property options and emphasizing the help feature in "
-"Odoo Studio"
-msgstr ""
-
 #: ../../content/applications/productivity/studio/use_cases/models_fields.rst:129
 msgid ""
 "The *Field Help* message can only be applied to *new* fields. If you would "
@@ -2884,11 +2610,6 @@ msgid ""
 "option under *Properties*."
 msgstr ""
 
-#: ../../content/applications/productivity/studio/use_cases/models_fields.rst:0
-msgid ""
-"View of the properties emphasizing the help tooltip option in Odoo Studio"
-msgstr ""
-
 #: ../../content/applications/productivity/studio/use_cases/views.rst:3
 msgid "Advanced Use Cases: Views"
 msgstr ""
@@ -2905,10 +2626,6 @@ msgid ""
 "option as the default one."
 msgstr ""
 
-#: ../../content/applications/productivity/studio/use_cases/views.rstNone
-msgid "View of the Kanban option being set as the default one in Odoo Studio"
-msgstr ""
-
 #: ../../content/applications/productivity/studio/use_cases/views.rst:14
 msgid ""
 "**Case scenario 2: allow for the list of leads to be edited inline without "
@@ -2927,8 +2644,3 @@ msgid ""
 "If the field is left blank, no editing is possible and records are shown "
 "based on your column preferences on the lead's page (front-end)."
 msgstr ""
-
-#: ../../content/applications/productivity/studio/use_cases/views.rstNone
-msgid ""
-"View options emphasizing the editable options of a leads page in Odoo Studio"
-msgstr ""