From b65460db47803aa310270ea73db03a42d8e09a2e Mon Sep 17 00:00:00 2001 From: "Tiffany Chang (tic)" Date: Wed, 20 Mar 2024 10:37:39 +0000 Subject: [PATCH] [I18N] *: export latest terms + add missing resources This commit does 2 things: - exports the latest terms to be translated - adds missing pot files + adds them to be translated on transifex (essentials, hr, and studio) Notes: - hr (source) was already in v16, but was missing from v15 and v17, hence the commits being slightly different - latest pot files of `contributing`, `developer`, and `legal` were purposely left off this PR because they are either not translated or not translated via Transifex, so these pot files serve no purpose closes odoo/documentation#8363 X-original-commit: 977a649fae0271e1bec1d65bd3492bc8da590090 Signed-off-by: Martin Trigaux (mat) Signed-off-by: Tiffany Chang (tic) --- .tx/config | 30 + locale/sources/administration.pot | 5946 +++++++---------- locale/sources/essentials.pot | 1442 ++++ locale/sources/finance.pot | 2721 +++----- locale/sources/general.pot | 9025 ++++++++++++-------------- locale/sources/hr.pot | 2938 +++++---- locale/sources/inventory_and_mrp.pot | 2167 +++++-- locale/sources/marketing.pot | 395 +- locale/sources/productivity.pot | 8090 +++++++++++------------ locale/sources/sales.pot | 1082 ++- locale/sources/services.pot | 210 +- locale/sources/studio.pot | 1894 ++++++ locale/sources/websites.pot | 730 ++- 13 files changed, 20053 insertions(+), 16617 deletions(-) create mode 100644 locale/sources/essentials.pot create mode 100644 locale/sources/studio.pot diff --git a/.tx/config b/.tx/config index b24d7277b..db7884502 100644 --- a/.tx/config +++ b/.tx/config @@ -21,6 +21,16 @@ replace_edited_strings = false keep_translations = false source_lang = en +[o:odoo:p:odoo-17-doc:r:essentials] +file_filter = locale//LC_MESSAGES/essentials.po +source_file = locale/sources/essentials.pot +type = POT +minimum_perc = 0 +resource_name = essentials +replace_edited_strings = false +keep_translations = false +source_lang = en + [o:odoo:p:odoo-17-doc:r:finance] file_filter = locale//LC_MESSAGES/finance.po source_file = locale/sources/finance.pot @@ -41,6 +51,16 @@ replace_edited_strings = false keep_translations = false source_lang = en +[o:odoo:p:odoo-17-doc:r:hr] +file_filter = locale//LC_MESSAGES/hr.po +source_file = locale/sources/hr.pot +type = POT +minimum_perc = 0 +resource_name = hr +replace_edited_strings = false +keep_translations = false +source_lang = en + [o:odoo:p:odoo-17-doc:r:index] file_filter = locale//LC_MESSAGES/index.po source_file = locale/sources/index.pot @@ -111,6 +131,16 @@ replace_edited_strings = false keep_translations = false source_lang = en +[o:odoo:p:odoo-17-doc:r:studio] +file_filter = locale//LC_MESSAGES/studio.po +source_file = locale/sources/studio.pot +type = POT +minimum_perc = 0 +resource_name = studio +replace_edited_strings = false +keep_translations = false +source_lang = en + [o:odoo:p:odoo-17-doc:r:websites] file_filter = locale//LC_MESSAGES/websites.po source_file = locale/sources/websites.pot diff --git a/locale/sources/administration.pot b/locale/sources/administration.pot index 254224f37..1adc4bac5 100644 --- a/locale/sources/administration.pot +++ b/locale/sources/administration.pot @@ -8,7 +8,7 @@ msgid "" msgstr "" "Project-Id-Version: Odoo 17.0\n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2024-03-08 12:48+0000\n" +"POT-Creation-Date: 2024-03-25 16:01+0000\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME \n" "Language-Team: LANGUAGE \n" @@ -17,7 +17,8 @@ msgstr "" "Content-Transfer-Encoding: 8bit\n" #: ../../content/administration.rst:8 -msgid "Install and Maintain" +#: ../../content/administration/odoo_online.rst:18 +msgid "Database management" msgstr "" #: ../../content/administration.rst:10 @@ -25,3051 +26,448 @@ msgid "These guides provide instructions on how to install, maintain and upgrade msgstr "" #: ../../content/administration.rst:13 -msgid ":doc:`History of Versions `" +msgid ":doc:`History of Versions `" msgstr "" -#: ../../content/administration/install.rst:5 -msgid "Install" -msgstr "" - -#: ../../content/administration/install.rst:7 -msgid "Depending on the intended use case, there are multiple ways to install Odoo - or not install it at all." -msgstr "" - -#: ../../content/administration/install.rst:10 -msgid ":doc:`Online ` is the easiest way to use Odoo in production or to try it." -msgstr "" - -#: ../../content/administration/install.rst:12 -msgid ":doc:`Packaged installers ` are suitable for testing Odoo and developing modules. They can be used for long-term production with additional deployment and maintenance work." -msgstr "" - -#: ../../content/administration/install.rst:16 -msgid ":doc:`Source install ` provides greater flexibility, as it allows, for example, running multiple Odoo versions on the same system. It is adequate to develop modules and can be used as a base for production deployment." -msgstr "" - -#: ../../content/administration/install.rst:20 -msgid "A `Docker `_ base image is available for development or deployment." -msgstr "" - -#: ../../content/administration/install.rst:26 -msgid "Editions" -msgstr "" - -#: ../../content/administration/install.rst:28 -msgid "There are two different editions." -msgstr "" - -#: ../../content/administration/install.rst:30 -msgid "**Odoo Community** is the free and open-source version of the software, licensed under the `GNU LGPLv3 `_. It is the core upon which Odoo Enterprise is built." -msgstr "" - -#: ../../content/administration/install.rst:34 -msgid "**Odoo Enterprise** is the shared source version of the software, giving access to more functionalities, including functional support, upgrades, and hosting. `Pricing `_ starts from one app free." -msgstr "" - -#: ../../content/administration/install.rst:39 -msgid ":doc:`Switch from Community to Enterprise ` at any time (except for the source install)." -msgstr "" - -#: ../../content/administration/install/cdn.rst:3 -msgid "Set up a content delivery network (CDN)" -msgstr "" - -#: ../../content/administration/install/cdn.rst:8 -msgid "Deploying with KeyCDN" -msgstr "" - -#: ../../content/administration/install/cdn.rst:10 -msgid "A :abbr:`CDN (Content Delivery Network)` or *content distribution network*, is a geographically distributed network of servers that provides high speed internet content. The :abbr:`CDN (Content Delivery Network)` provides quick, high-quality content delivery for content-heavy websites." -msgstr "" - -#: ../../content/administration/install/cdn.rst:14 -msgid "This document will guide you through the setup of a KeyCDN_ account with an Odoo powered website." -msgstr "" - -#: ../../content/administration/install/cdn.rst:17 -msgid "Create a pull zone in the KeyCDN dashboard" -msgstr "" - -#: ../../content/administration/install/cdn.rst:19 -msgid "On the KeyCDN dashboard, start by navigating to the :menuselection:`Zones` menu item on the left. On the form, give a value to the :guilabel:`Zone Name`, which will appear as part of the :abbr:`CDN (Content Delivery Network)`'s :abbr:`URL (Uniform Resource Locator)`. Then, set the :guilabel:`Zone Status` to :guilabel:`active` to engage the zone. For the :guilabel:`Zone Type` set the value to :guilabel:`Pull`, and then, finally, under the :guilabel:`Pull Settings`, enter the :guilabel:`Origin URL`— this address should be the full Odoo database :abbr:`URL (Uniform Resource Locator)`." -msgstr "" - -#: ../../content/administration/install/cdn.rst:28 -msgid "Use ``https://yourdatabase.odoo.com`` and replace the *yourdatabase* subdomain prefix with the actual name of the database. A custom :abbr:`URL (Uniform Resource Locator)` can be used, as well, in place of the Odoo subdomain that was provided to the database." -msgstr "" - -#: ../../content/administration/install/cdn.rst:-1 -msgid "KeyCDN's Zone configuration page." -msgstr "" - -#: ../../content/administration/install/cdn.rst:36 -msgid "Under the :guilabel:`General Settings` heading below the zone form, click the :guilabel:`Show all settings` button to expand the zone options. This should be the last option on the page. After expanding the :guilabel:`General Settings` ensure that the :guilabel:`CORS` option is :guilabel:`enabled`." -msgstr "" - -#: ../../content/administration/install/cdn.rst:41 -msgid "Next, scroll to the bottom of the zone configuration page and :guilabel:`Save` the changes. KeyCDN will indicate that the new zone will be deployed. This can take about 10 minutes." -msgstr "" - -#: ../../content/administration/install/cdn.rst:-1 -msgid "KeyCDN deploying the new Zone." -msgstr "" - -#: ../../content/administration/install/cdn.rst:49 -msgid "A new :guilabel:`Zone URL` has been generated for your Zone, in this example it is ``pulltest-xxxxx.kxcdn.com``. This value will differ for each database." -msgstr "" - -#: ../../content/administration/install/cdn.rst:52 -msgid "Copy this :guilabel:`Zone URL` to a text editor for later, as it will be used in the next steps." -msgstr "" - -#: ../../content/administration/install/cdn.rst:55 -msgid "Configure the Odoo instance with the new zone" -msgstr "" - -#: ../../content/administration/install/cdn.rst:57 -msgid "In the Odoo :guilabel:`Website` app, go to the :menuselection:`Settings` and then activate the :guilabel:`Content Delivery Network (CDN)` setting and copy/paste the :guilabel:`Zone URL` value from the earlier step into the :guilabel:`CDN Base URL` field. This field is only visible and configurable when :doc:`Developer Mode <../../applications/general/developer_mode>` is activated." -msgstr "" - -#: ../../content/administration/install/cdn.rst:63 -msgid "Ensure that there are two *forward slashes* (`//`) before the :guilabel:`CDN Base URL` and one forward slash (`/`) after the :guilabel:`CDN Base URL`." -msgstr "" - -#: ../../content/administration/install/cdn.rst:66 -msgid ":guilabel:`Save` the settings when complete." -msgstr "" - -#: ../../content/administration/install/cdn.rst:-1 -msgid "Activate the CDN setting in Odoo." -msgstr "" - -#: ../../content/administration/install/cdn.rst:72 -msgid "Now the website is using the CDN for the resources matching the :guilabel:`CDN filters` regular expressions." -msgstr "" - -#: ../../content/administration/install/cdn.rst:75 -msgid "In the HTML of the Odoo website, the :abbr:`CDN (content delivery network)` integration is evidenced as working properly by checking the :abbr:`URL (Uniform Resource Locators)` of images. The *CDN Base URL* value can be seen by using your web browser's :guilabel:`Inspect` feature on the Odoo website. Look for it's record by searching within the :guilabel:`Network` tab inside of devtools." -msgstr "" - -#: ../../content/administration/install/cdn.rst:-1 -msgid "The CDN Base URL can be seen using the inspect function on the Odoo website." -msgstr "" - -#: ../../content/administration/install/cdn.rst:85 -msgid "Prevent security issues by activating cross-origin resource sharing (CORS)" -msgstr "" - -#: ../../content/administration/install/cdn.rst:87 -msgid "A security restriction in some browsers (such as Mozilla Firefox and Google Chrome) prevents a remotely linked CSS file to fetch relative resources on this same external server." -msgstr "" - -#: ../../content/administration/install/cdn.rst:90 -msgid "If the :abbr:`CORS (Cross-Origin Resource Sharing)` option isn't enabled in the :guilabel:`CDN Zone`, the more obvious resulting problem on a standard Odoo website will be the lack of *Font Awesome* icons because the font file declared in the *Font Awesome* CSS won't be loaded from the remote server." -msgstr "" - -#: ../../content/administration/install/cdn.rst:95 -msgid "When these cross-origin resource issues occur, a security error message similar to the output below will appear in the web browser's developer console:" -msgstr "" - -#: ../../content/administration/install/cdn.rst:98 -msgid "``Font from origin 'http://pulltest-xxxxx.kxcdn.com' has been blocked from loading /shop:1 by Cross-Origin Resource Sharing policy: No 'Access-Control-Allow-Origin' header is present on the requested resource. Origin 'http://yourdatabase.odoo.com' is therefore not allowed access.``" -msgstr "" - -#: ../../content/administration/install/cdn.rst:-1 -msgid "Error message populated in the browser console." -msgstr "" - -#: ../../content/administration/install/cdn.rst:106 -msgid "Enabling the :abbr:`CORS (Cross-Origin Resource Sharing)` option in the :abbr:`CDN (Content Delivery Network)` settings fixes this issue." -msgstr "" - -#: ../../content/administration/install/deploy.rst:3 -msgid "System configuration" -msgstr "" - -#: ../../content/administration/install/deploy.rst:5 -msgid "This document describes basic steps to set up Odoo in production or on an internet-facing server. It follows :doc:`installation <../install>`, and is not generally necessary for a development systems that is not exposed on the internet." -msgstr "" - -#: ../../content/administration/install/deploy.rst:10 -msgid "If you are setting up a public server, be sure to check our :ref:`security` recommendations!" -msgstr "" - -#: ../../content/administration/install/deploy.rst:15 -msgid "dbfilter" -msgstr "" - -#: ../../content/administration/install/deploy.rst:17 -msgid "Odoo is a multi-tenant system: a single Odoo system may run and serve a number of database instances. It is also highly customizable, with customizations (starting from the modules being loaded) depending on the \"current database\"." -msgstr "" - -#: ../../content/administration/install/deploy.rst:21 -msgid "This is not an issue when working with the backend (web client) as a logged-in company user: the database can be selected when logging in, and customizations loaded afterwards." -msgstr "" - -#: ../../content/administration/install/deploy.rst:25 -msgid "However it is an issue for non-logged users (portal, website) which aren't bound to a database: Odoo needs to know which database should be used to load the website page or perform the operation. If multi-tenancy is not used that is not an issue, there's only one database to use, but if there are multiple databases accessible Odoo needs a rule to know which one it should use." -msgstr "" - -#: ../../content/administration/install/deploy.rst:31 -msgid "That is one of the purposes of :option:`--db-filter `: it specifies how the database should be selected based on the hostname (domain) that is being requested. The value is a `regular expression`_, possibly including the dynamically injected hostname (``%h``) or the first subdomain (``%d``) through which the system is being accessed." -msgstr "" - -#: ../../content/administration/install/deploy.rst:37 -msgid "For servers hosting multiple databases in production, especially if ``website`` is used, dbfilter **must** be set, otherwise a number of features will not work correctly." -msgstr "" - -#: ../../content/administration/install/deploy.rst:42 -msgid "Configuration samples" -msgstr "" - -#: ../../content/administration/install/deploy.rst:44 -msgid "Show only databases with names beginning with 'mycompany'" -msgstr "" - -#: ../../content/administration/install/deploy.rst:46 -#: ../../content/administration/install/deploy.rst:58 -#: ../../content/administration/install/deploy.rst:153 -#: ../../content/administration/install/deploy.rst:280 -msgid "in :ref:`the configuration file ` set:" -msgstr "" - -#: ../../content/administration/install/deploy.rst:53 -msgid "Show only databases matching the first subdomain after ``www``: for example the database \"mycompany\" will be shown if the incoming request was sent to ``www.mycompany.com`` or ``mycompany.co.uk``, but not for ``www2.mycompany.com`` or ``helpdesk.mycompany.com``." -msgstr "" - -#: ../../content/administration/install/deploy.rst:67 -msgid "Setting a proper :option:`--db-filter ` is an important part of securing your deployment. Once it is correctly working and only matching a single database per hostname, it is strongly recommended to block access to the database manager screens, and to use the ``--no-database-list`` startup parameter to prevent listing your databases, and to block access to the database management screens. See also security_." -msgstr "" - -#: ../../content/administration/install/deploy.rst:76 -#: ../../content/administration/install/source.rst:193 -msgid "PostgreSQL" -msgstr "" - -#: ../../content/administration/install/deploy.rst:78 -msgid "By default, PostgreSQL only allows connection over UNIX sockets and loopback connections (from \"localhost\", the same machine the PostgreSQL server is installed on)." -msgstr "" - -#: ../../content/administration/install/deploy.rst:82 -msgid "UNIX socket is fine if you want Odoo and PostgreSQL to execute on the same machine, and is the default when no host is provided, but if you want Odoo and PostgreSQL to execute on different machines [#different-machines]_ it will need to `listen to network interfaces`_ [#remote-socket]_, either:" -msgstr "" - -#: ../../content/administration/install/deploy.rst:87 -msgid "Only accept loopback connections and `use an SSH tunnel`_ between the machine on which Odoo runs and the one on which PostgreSQL runs, then configure Odoo to connect to its end of the tunnel" -msgstr "" - -#: ../../content/administration/install/deploy.rst:90 -msgid "Accept connections to the machine on which Odoo is installed, possibly over ssl (see `PostgreSQL connection settings`_ for details), then configure Odoo to connect over the network" -msgstr "" - -#: ../../content/administration/install/deploy.rst:95 -#: ../../content/administration/install/deploy.rst:145 -#: ../../content/administration/install/deploy.rst:235 -#: ../../content/administration/install/deploy.rst:275 -msgid "Configuration sample" -msgstr "" - -#: ../../content/administration/install/deploy.rst:97 -msgid "Allow tcp connection on localhost" -msgstr "" - -#: ../../content/administration/install/deploy.rst:98 -msgid "Allow tcp connection from 192.168.1.x network" -msgstr "" - -#: ../../content/administration/install/deploy.rst:100 -msgid "in ``/etc/postgresql//main/pg_hba.conf`` set:" -msgstr "" - -#: ../../content/administration/install/deploy.rst:108 -msgid "in ``/etc/postgresql//main/postgresql.conf`` set:" -msgstr "" - -#: ../../content/administration/install/deploy.rst:119 -msgid "Configuring Odoo" -msgstr "" - -#: ../../content/administration/install/deploy.rst:121 -msgid "Out of the box, Odoo connects to a local postgres over UNIX socket via port 5432. This can be overridden using :ref:`the database options ` when your Postgres deployment is not local and/or does not use the installation defaults." -msgstr "" - -#: ../../content/administration/install/deploy.rst:126 -msgid "The :doc:`packaged installers ` will automatically create a new user (``odoo``) and set it as the database user." -msgstr "" - -#: ../../content/administration/install/deploy.rst:129 -msgid "The database management screens are protected by the ``admin_passwd`` setting. This setting can only be set using configuration files, and is simply checked before performing database alterations. It should be set to a randomly generated value to ensure third parties can not use this interface." -msgstr "" - -#: ../../content/administration/install/deploy.rst:134 -msgid "All database operations use the :ref:`database options `, including the database management screen. For the database management screen to work requires that the PostgreSQL user have ``createdb`` right." -msgstr "" - -#: ../../content/administration/install/deploy.rst:138 -msgid "Users can always drop databases they own. For the database management screen to be completely non-functional, the PostgreSQL user needs to be created with ``no-createdb`` and the database must be owned by a different PostgreSQL user." -msgstr "" - -#: ../../content/administration/install/deploy.rst:142 -msgid "the PostgreSQL user *must not* be a superuser" -msgstr "" - -#: ../../content/administration/install/deploy.rst:147 -msgid "connect to a PostgreSQL server on 192.168.1.2" -msgstr "" - -#: ../../content/administration/install/deploy.rst:148 -msgid "port 5432" -msgstr "" - -#: ../../content/administration/install/deploy.rst:149 -msgid "using an 'odoo' user account," -msgstr "" - -#: ../../content/administration/install/deploy.rst:150 -msgid "with 'pwd' as a password" -msgstr "" - -#: ../../content/administration/install/deploy.rst:151 -msgid "filtering only db with a name beginning with 'mycompany'" -msgstr "" - -#: ../../content/administration/install/deploy.rst:168 -msgid "SSL Between Odoo and PostgreSQL" -msgstr "" - -#: ../../content/administration/install/deploy.rst:170 -msgid "Since Odoo 11.0, you can enforce ssl connection between Odoo and PostgreSQL. in Odoo the db_sslmode control the ssl security of the connection with value chosen out of 'disable', 'allow', 'prefer', 'require', 'verify-ca' or 'verify-full'" -msgstr "" - -#: ../../content/administration/install/deploy.rst:175 -msgid "`PostgreSQL Doc `_" -msgstr "" - -#: ../../content/administration/install/deploy.rst:180 -msgid "Builtin server" -msgstr "" - -#: ../../content/administration/install/deploy.rst:182 -msgid "Odoo includes built-in HTTP, cron, and live-chat servers, using either multi-threading or multi-processing." -msgstr "" - -#: ../../content/administration/install/deploy.rst:185 -msgid "The **multi-threaded** server is a simpler server primarily used for development, demonstrations, and its compatibility with various operating systems (including Windows). A new thread is spawned for every new HTTP request, even for long-lived connections such as websocket. Extra daemonic cron threads are spawned too. Due to a Python limitation (GIL), it doesn't make the best use of the hardware." -msgstr "" - -#: ../../content/administration/install/deploy.rst:191 -msgid "The multi-threaded server is the default server, also for docker containers. It is selected by leaving the :option:`--workers ` option out or setting it to ``0``." -msgstr "" - -#: ../../content/administration/install/deploy.rst:194 -msgid "The **multi-processing** server is a full-blown server primarily used for production. It is not liable to the same Python limitation (GIL) on resource usage and hence makes the best use of the hardware. A pool of workers is created upon server startup. New HTTP requests are queued by the OS until there are workers ready to process them. An extra event-driven HTTP worker for the live chat is spawned on an alternative port. Extra cron workers are spawned too. A configurable process reaper monitors resource usage and can kill/restart failed workers." -msgstr "" - -#: ../../content/administration/install/deploy.rst:201 -msgid "The multi-processing server is opt-in. It is selected by setting the :option:`--workers ` option to a non-null integer." -msgstr "" - -#: ../../content/administration/install/deploy.rst:205 -msgid "Because it is highly customized for Linux servers, the multi-processing server is not available on Windows." -msgstr "" - -#: ../../content/administration/install/deploy.rst:209 -msgid "Worker number calculation" -msgstr "" - -#: ../../content/administration/install/deploy.rst:211 -msgid "Rule of thumb : (#CPU * 2) + 1" -msgstr "" - -#: ../../content/administration/install/deploy.rst:212 -msgid "Cron workers need CPU" -msgstr "" - -#: ../../content/administration/install/deploy.rst:213 -msgid "1 worker ~= 6 concurrent users" -msgstr "" - -#: ../../content/administration/install/deploy.rst:216 -msgid "memory size calculation" -msgstr "" - -#: ../../content/administration/install/deploy.rst:218 -msgid "We consider 20% of the requests are heavy requests, while 80% are simpler ones" -msgstr "" - -#: ../../content/administration/install/deploy.rst:219 -msgid "A heavy worker, when all computed field are well designed, SQL requests are well designed, ... is estimated to consume around 1GB of RAM" -msgstr "" - -#: ../../content/administration/install/deploy.rst:220 -msgid "A lighter worker, in the same scenario, is estimated to consume around 150MB of RAM" -msgstr "" - -#: ../../content/administration/install/deploy.rst:222 -msgid "Needed RAM = #worker * ( (light_worker_ratio * light_worker_ram_estimation) + (heavy_worker_ratio * heavy_worker_ram_estimation) )" -msgstr "" - -#: ../../content/administration/install/deploy.rst:225 -#: ../../content/administration/install/deploy.rst:413 -msgid "LiveChat" -msgstr "" - -#: ../../content/administration/install/deploy.rst:227 -msgid "In multi-processing, a dedicated LiveChat worker is automatically started and listens on the :option:`--gevent-port `. By default, the HTTP requests will keep accessing the normal HTTP workers instead of the LiveChat one. You must deploy a proxy in front of Odoo and redirect incoming requests whose path starts with ``/websocket/`` to the LiveChat worker. You must also start Odoo in :option:`--proxy-mode ` so it uses the real client headers (such as hostname, scheme, and IP) instead of the proxy ones." -msgstr "" - -#: ../../content/administration/install/deploy.rst:237 -msgid "Server with 4 CPU, 8 Thread" -msgstr "" - -#: ../../content/administration/install/deploy.rst:238 -msgid "60 concurrent users" -msgstr "" - -#: ../../content/administration/install/deploy.rst:240 -msgid "60 users / 6 = 10 <- theoretical number of worker needed" -msgstr "" - -#: ../../content/administration/install/deploy.rst:241 -msgid "(4 * 2) + 1 = 9 <- theoretical maximal number of worker" -msgstr "" - -#: ../../content/administration/install/deploy.rst:242 -msgid "We'll use 8 workers + 1 for cron. We'll also use a monitoring system to measure cpu load, and check if it's between 7 and 7.5 ." -msgstr "" - -#: ../../content/administration/install/deploy.rst:243 -msgid "RAM = 9 * ((0.8*150) + (0.2*1024)) ~= 3Go RAM for Odoo" -msgstr "" - -#: ../../content/administration/install/deploy.rst:245 -msgid "in :ref:`the configuration file `:" -msgstr "" - -#: ../../content/administration/install/deploy.rst:261 -msgid "HTTPS" -msgstr "" - -#: ../../content/administration/install/deploy.rst:263 -msgid "Whether it's accessed via website/web client or web service, Odoo transmits authentication information in cleartext. This means a secure deployment of Odoo must use HTTPS\\ [#switching]_. SSL termination can be implemented via just about any SSL termination proxy, but requires the following setup:" -msgstr "" - -#: ../../content/administration/install/deploy.rst:268 -msgid "Enable Odoo's :option:`proxy mode `. This should only be enabled when Odoo is behind a reverse proxy" -msgstr "" - -#: ../../content/administration/install/deploy.rst:269 -msgid "Set up the SSL termination proxy (`Nginx termination example`_)" -msgstr "" - -#: ../../content/administration/install/deploy.rst:270 -msgid "Set up the proxying itself (`Nginx proxying example`_)" -msgstr "" - -#: ../../content/administration/install/deploy.rst:271 -msgid "Your SSL termination proxy should also automatically redirect non-secure connections to the secure port" -msgstr "" - -#: ../../content/administration/install/deploy.rst:277 -msgid "Redirect http requests to https" -msgstr "" - -#: ../../content/administration/install/deploy.rst:278 -msgid "Proxy requests to odoo" -msgstr "" - -#: ../../content/administration/install/deploy.rst:286 -msgid "in ``/etc/nginx/sites-enabled/odoo.conf`` set:" -msgstr "" - -#: ../../content/administration/install/deploy.rst:362 -msgid "HTTPS Hardening" -msgstr "" - -#: ../../content/administration/install/deploy.rst:364 -msgid "Add the `Strict-Transport-Security` header to all requests, in order to prevent browsers from ever sending a plain HTTP request to this domain. You will need to maintain a working HTTPS service with a valid certificate on this domain at all times, otherwise your users will see security alerts or be entirely unable to access it." -msgstr "" - -#: ../../content/administration/install/deploy.rst:370 -msgid "Force HTTPS connections during a year for every visitor in NGINX with the line:" -msgstr "" - -#: ../../content/administration/install/deploy.rst:376 -msgid "Additional configuration can be defined for the `session_id` cookie. The `Secure` flag can be added to ensure it is never transmitted over HTTP and `SameSite=Lax` to prevent authenticated `CSRF`_." -msgstr "" - -#: ../../content/administration/install/deploy.rst:387 -msgid "Odoo as a WSGI Application" -msgstr "" - -#: ../../content/administration/install/deploy.rst:389 -msgid "It is also possible to mount Odoo as a standard WSGI_ application. Odoo provides the base for a WSGI launcher script as ``odoo-wsgi.example.py``. That script should be customized (possibly after copying it from the setup directory) to correctly set the configuration directly in :mod:`odoo.tools.config` rather than through the command-line or a configuration file." -msgstr "" - -#: ../../content/administration/install/deploy.rst:395 -msgid "However the WSGI server will only expose the main HTTP endpoint for the web client, website and webservice API. Because Odoo does not control the creation of workers anymore it can not setup cron or livechat workers" -msgstr "" - -#: ../../content/administration/install/deploy.rst:400 -msgid "Cron Workers" -msgstr "" - -#: ../../content/administration/install/deploy.rst:402 -msgid "Starting one of the built-in Odoo servers next to the WSGI server is required to process cron jobs. That server must be configured to only process crons and not HTTP requests using the :option:`--no-http ` cli option or the ``http_enable = False`` configuration file setting." -msgstr "" - -#: ../../content/administration/install/deploy.rst:407 -msgid "On Linux-like systems, using the multi-processing server over the multi-threading one is recommended to benefit from better hardware usage and increased stability, i.e., using the :option:`--workers=-1 ` and :option:`--max-cron-threads=n ` cli options." -msgstr "" - -#: ../../content/administration/install/deploy.rst:415 -msgid "Using a gevent-compatible WSGI server is required for the correct operation of the live chat feature. That server should be able to handle many simultaneous long-lived connections but doesn't need a lot of processing power. All requests whose path starts with ``/websocket/`` should be directed to that server. A regular (thread/process-based) WSGI server should be used for all other requests." -msgstr "" - -#: ../../content/administration/install/deploy.rst:421 -msgid "The Odoo cron server can also be used to serve the live chat requests. Just drop the :option:`--no-http ` cli option from the cron server and make sure requests whose path starts with ``/websocket/`` are directed to this server, either on the :option:`--http-port ` (multi-threading server) or on the :option:`--gevent-port ` (multi-processing server)." -msgstr "" - -#: ../../content/administration/install/deploy.rst:430 -msgid "Serving static files and attachments" -msgstr "" - -#: ../../content/administration/install/deploy.rst:432 -msgid "For development convenience, Odoo directly serves all static files and attachments in its modules. This may not be ideal when it comes to performances, and static files should generally be served by a static HTTP server." -msgstr "" - -#: ../../content/administration/install/deploy.rst:437 -msgid "Serving static files" -msgstr "" - -#: ../../content/administration/install/deploy.rst:439 -msgid "Odoo static files are located in each module's :file:`static/` folder, so static files can be served by intercepting all requests to :samp:`/{MODULE}/static/{FILE}`, and looking up the right module (and file) in the various addons paths." -msgstr "" - -#: ../../content/administration/install/deploy.rst:443 -msgid "It is recommended to set the ``Content-Security-Policy: default-src 'none'`` header on all images delivered by the web server. It is not strictly necessary as users cannot modify/inject content inside of modules' :file:`static/` folder and existing images are final (they do not fetch new resources by themselves). However, it is good practice." -msgstr "" - -#: ../../content/administration/install/deploy.rst:448 -msgid "Using the above NGINX (https) configuration, the following ``map`` and ``location`` blocks should be added to serve static files via NGINX." -msgstr "" - -#: ../../content/administration/install/deploy.rst:475 -msgid "The actual ``root`` and ``try_files`` directives are dependant on your installation, specifically on your :option:`--addons-path `." -msgstr "" - -#: ../../content/administration/install/deploy.rst:482 -msgid "Debian package" -msgstr "" - -#: ../../content/administration/install/deploy.rst:484 -msgid "Say Odoo has been installed via the **debian packages** for Community and Enterprise, and that the :option:`--addons-path ` is ``'/usr/lib/python3/dist-packages/odoo/addons'``." -msgstr "" - -#: ../../content/administration/install/deploy.rst:488 -#: ../../content/administration/install/deploy.rst:502 -msgid "The ``root`` and ``try_files`` should be:" -msgstr "" - -#: ../../content/administration/install/deploy.rst:495 -msgid "Git sources" -msgstr "" - -#: ../../content/administration/install/deploy.rst:497 -msgid "Say Odoo has been installed via the **sources**, that both the Community and Enterprise git repositories were cloned in :file:`/opt/odoo/community` and :file:`/opt/odoo/enterprise` respectively, and that the :option:`--addons-path ` is ``'/opt/odoo/community/odoo/addons,/opt/odoo/community/addons,/opt/odoo/enterprise'``." -msgstr "" - -#: ../../content/administration/install/deploy.rst:510 -msgid "Serving attachments" -msgstr "" - -#: ../../content/administration/install/deploy.rst:512 -msgid "Attachments are files stored in the filestore which access is regulated by Odoo. They cannot be directly accessed via a static web server as accessing them requires multiple lookups in the database to determine where the files are stored and whether the current user can access them or not." -msgstr "" - -#: ../../content/administration/install/deploy.rst:517 -msgid "Nevertheless, once the file has been located and the access rights verified by Odoo, it is a good idea to serve the file using the static web server instead of Odoo. For Odoo to delegate serving files to the static web server, the `X-Sendfile `_ (apache) or `X-Accel `_ (nginx) extensions must be enabled and configured on the static web server. Once it is set up, start Odoo with the :option:`--x-sendfile ` CLI flag (this unique flag is used for both X-Sendfile and X-Accel)." -msgstr "" - -#: ../../content/administration/install/deploy.rst:527 -msgid "The X-Sendfile extension for apache (and compatible web servers) does not require any supplementary configuration." -msgstr "" - -#: ../../content/administration/install/deploy.rst:529 -msgid "The X-Accel extension for NGINX **does** require the following additionnal configuration:" -msgstr "" - -#: ../../content/administration/install/deploy.rst:538 -msgid "In case you don't know what is the path to your filestore, start Odoo with the :option:`--x-sendfile ` option and navigate to the ``/web/filestore`` URL directly via Odoo (don't navigate to the URL via NGINX). This logs a warnings, the message contains the configuration you need." -msgstr "" - -#: ../../content/administration/install/deploy.rst:547 -msgid "Security" -msgstr "" - -#: ../../content/administration/install/deploy.rst:549 -msgid "For starters, keep in mind that securing an information system is a continuous process, not a one-shot operation. At any moment, you will only be as secure as the weakest link in your environment." -msgstr "" - -#: ../../content/administration/install/deploy.rst:553 -msgid "So please do not take this section as the ultimate list of measures that will prevent all security problems. It's only intended as a summary of the first important things you should be sure to include in your security action plan. The rest will come from best security practices for your operating system and distribution, best practices in terms of users, passwords, and access control management, etc." -msgstr "" - -#: ../../content/administration/install/deploy.rst:559 -msgid "When deploying an internet-facing server, please be sure to consider the following security-related topics:" -msgstr "" - -#: ../../content/administration/install/deploy.rst:562 -msgid "Always set a strong super-admin admin password, and restrict access to the database management pages as soon as the system is set up. See :ref:`db_manager_security`." -msgstr "" - -#: ../../content/administration/install/deploy.rst:565 -msgid "Choose unique logins and strong passwords for all administrator accounts on all databases. Do not use 'admin' as the login. Do not use those logins for day-to-day operations, only for controlling/managing the installation. *Never* use any default passwords like admin/admin, even for test/staging databases." -msgstr "" - -#: ../../content/administration/install/deploy.rst:570 -msgid "Do **not** install demo data on internet-facing servers. Databases with demo data contain default logins and passwords that can be used to get into your systems and cause significant trouble, even on staging/dev systems." -msgstr "" - -#: ../../content/administration/install/deploy.rst:574 -msgid "Use appropriate database filters ( :option:`--db-filter `) to restrict the visibility of your databases according to the hostname. See :ref:`db_filter`. You may also use :option:`-d ` to provide your own (comma-separated) list of available databases to filter from, instead of letting the system fetch them all from the database backend." -msgstr "" - -#: ../../content/administration/install/deploy.rst:581 -msgid "Once your ``db_name`` and ``db_filter`` are configured and only match a single database per hostname, you should set ``list_db`` configuration option to ``False``, to prevent listing databases entirely, and to block access to the database management screens (this is also exposed as the :option:`--no-database-list ` command-line option)" -msgstr "" - -#: ../../content/administration/install/deploy.rst:587 -msgid "Make sure the PostgreSQL user (:option:`--db_user `) is *not* a super-user, and that your databases are owned by a different user. For example they could be owned by the ``postgres`` super-user if you are using a dedicated non-privileged ``db_user``. See also :ref:`setup/deploy/odoo`." -msgstr "" - -#: ../../content/administration/install/deploy.rst:592 -msgid "Keep installations updated by regularly installing the latest builds, either via GitHub or by downloading the latest version from https://www.odoo.com/page/download or http://nightly.odoo.com" -msgstr "" - -#: ../../content/administration/install/deploy.rst:596 -msgid "Configure your server in multi-process mode with proper limits matching your typical usage (memory/CPU/timeouts). See also :ref:`builtin_server`." -msgstr "" - -#: ../../content/administration/install/deploy.rst:599 -msgid "Run Odoo behind a web server providing HTTPS termination with a valid SSL certificate, in order to prevent eavesdropping on cleartext communications. SSL certificates are cheap, and many free options exist. Configure the web proxy to limit the size of requests, set appropriate timeouts, and then enable the :option:`proxy mode ` option. See also :ref:`https_proxy`." -msgstr "" - -#: ../../content/administration/install/deploy.rst:606 -msgid "If you need to allow remote SSH access to your servers, make sure to set a strong password for **all** accounts, not just `root`. It is strongly recommended to entirely disable password-based authentication, and only allow public key authentication. Also consider restricting access via a VPN, allowing only trusted IPs in the firewall, and/or running a brute-force detection system such as `fail2ban` or equivalent." -msgstr "" - -#: ../../content/administration/install/deploy.rst:612 -msgid "Consider installing appropriate rate-limiting on your proxy or firewall, to prevent brute-force attacks and denial of service attacks. See also :ref:`login_brute_force` for specific measures." -msgstr "" - -#: ../../content/administration/install/deploy.rst:616 -msgid "Many network providers provide automatic mitigation for Distributed Denial of Service attacks (DDOS), but this is often an optional service, so you should consult with them." -msgstr "" - -#: ../../content/administration/install/deploy.rst:620 -msgid "Whenever possible, host your public-facing demo/test/staging instances on different machines than the production ones. And apply the same security precautions as for production." -msgstr "" - -#: ../../content/administration/install/deploy.rst:624 -msgid "If your public-facing Odoo server has access to sensitive internal network resources or services (e.g. via a private VLAN), implement appropriate firewall rules to protect those internal resources. This will ensure that the Odoo server cannot be used accidentally (or as a result of malicious user actions) to access or disrupt those internal resources. Typically this can be done by applying an outbound default DENY rule on the firewall, then only explicitly authorizing access to internal resources that the Odoo server needs to access. `Systemd IP traffic access control `_ may also be useful to implement per-process network access control." -msgstr "" - -#: ../../content/administration/install/deploy.rst:635 -msgid "If your public-facing Odoo server is behind a Web Application Firewall, a load-balancer, a transparent DDoS protection service (like CloudFlare) or a similar network-level device, you may wish to avoid direct access to the Odoo system. It is generally difficult to keep the endpoint IP addresses of your Odoo servers secret. For example they can appear in web server logs when querying public systems, or in the headers of emails posted from Odoo. In such a situation you may want to configure your firewall so that the endpoints are not accessible publicly except from the specific IP addresses of your WAF, load-balancer or proxy service. Service providers like CloudFlare usually maintain a public list of their IP address ranges for this purpose." -msgstr "" - -#: ../../content/administration/install/deploy.rst:646 -msgid "If you are hosting multiple customers, isolate customer data and files from each other using containers or appropriate \"jail\" techniques." -msgstr "" - -#: ../../content/administration/install/deploy.rst:649 -msgid "Setup daily backups of your databases and filestore data, and copy them to a remote archiving server that is not accessible from the server itself." -msgstr "" - -#: ../../content/administration/install/deploy.rst:652 -msgid "Deploying Odoo on Linux is strongly recommended over Windows. Should you choose nevertheless to deploy on a Windows platform, a thorough security hardening review of the server should be conducted and is outside of the scope of this guide." -msgstr "" - -#: ../../content/administration/install/deploy.rst:660 -msgid "Blocking Brute Force Attacks" -msgstr "" - -#: ../../content/administration/install/deploy.rst:662 -msgid "For internet-facing deployments, brute force attacks on user passwords are very common, and this threat should not be neglected for Odoo servers. Odoo emits a log entry whenever a login attempt is performed, and reports the result: success or failure, along with the target login and source IP." -msgstr "" - -#: ../../content/administration/install/deploy.rst:666 -msgid "The log entries will have the following form." -msgstr "" - -#: ../../content/administration/install/deploy.rst:668 -msgid "Failed login::" -msgstr "" - -#: ../../content/administration/install/deploy.rst:672 -msgid "Successful login::" -msgstr "" - -#: ../../content/administration/install/deploy.rst:677 -msgid "These logs can be easily analyzed by an intrusion prevention system such as `fail2ban`." -msgstr "" - -#: ../../content/administration/install/deploy.rst:679 -msgid "For example, the following fail2ban filter definition should match a failed login::" -msgstr "" - -#: ../../content/administration/install/deploy.rst:686 -msgid "This could be used with a jail definition to block the attacking IP on HTTP(S)." -msgstr "" - -#: ../../content/administration/install/deploy.rst:688 -msgid "Here is what it could look like for blocking the IP for 15 minutes when 10 failed login attempts are detected from the same IP within 1 minute::" -msgstr "" - -#: ../../content/administration/install/deploy.rst:702 -msgid "Database Manager Security" -msgstr "" - -#: ../../content/administration/install/deploy.rst:704 -msgid ":ref:`setup/deploy/odoo` mentioned ``admin_passwd`` in passing." -msgstr "" - -#: ../../content/administration/install/deploy.rst:706 -msgid "This setting is used on all database management screens (to create, delete, dump or restore databases)." -msgstr "" - -#: ../../content/administration/install/deploy.rst:709 -msgid "If the management screens must not be accessible at all, you should set ``list_db`` configuration option to ``False``, to block access to all the database selection and management screens." -msgstr "" - -#: ../../content/administration/install/deploy.rst:715 -msgid "It is strongly recommended to disable the Database Manager for any internet-facing system! It is meant as a development/demo tool, to make it easy to quickly create and manage databases. It is not designed for use in production, and may even expose dangerous features to attackers. It is also not designed to handle large databases, and may trigger memory limits." -msgstr "" - -#: ../../content/administration/install/deploy.rst:721 -msgid "On production systems, database management operations should always be performed by the system administrator, including provisioning of new databases and automated backups." -msgstr "" - -#: ../../content/administration/install/deploy.rst:724 -msgid "Be sure to setup an appropriate ``db_name`` parameter (and optionally, ``db_filter`` too) so that the system can determine the target database for each request, otherwise users will be blocked as they won't be allowed to choose the database themselves." -msgstr "" - -#: ../../content/administration/install/deploy.rst:729 -msgid "If the management screens must only be accessible from a selected set of machines, use the proxy server's features to block access to all routes starting with ``/web/database`` except (maybe) ``/web/database/selector`` which displays the database-selection screen." -msgstr "" - -#: ../../content/administration/install/deploy.rst:733 -msgid "If the database-management screen should be left accessible, the ``admin_passwd`` setting must be changed from its ``admin`` default: this password is checked before allowing database-alteration operations." -msgstr "" - -#: ../../content/administration/install/deploy.rst:737 -msgid "It should be stored securely, and should be generated randomly e.g." -msgstr "" - -#: ../../content/administration/install/deploy.rst:743 -msgid "which will generate a 32 characters pseudorandom printable string." -msgstr "" - -#: ../../content/administration/install/deploy.rst:746 -msgid "Supported Browsers" -msgstr "" - -#: ../../content/administration/install/deploy.rst:748 -msgid "Odoo supports all the major desktop and mobile browsers available on the market, as long as they are supported by their publishers." -msgstr "" - -#: ../../content/administration/install/deploy.rst:751 -msgid "Here are the supported browsers:" -msgstr "" - -#: ../../content/administration/install/deploy.rst:753 -msgid "Google Chrome" -msgstr "" - -#: ../../content/administration/install/deploy.rst:754 -msgid "Mozilla Firefox" -msgstr "" - -#: ../../content/administration/install/deploy.rst:755 -msgid "Microsoft Edge" -msgstr "" - -#: ../../content/administration/install/deploy.rst:756 -msgid "Apple Safari" -msgstr "" - -#: ../../content/administration/install/deploy.rst:758 -msgid "Please make sure your browser is up-to-date and still supported by its publisher before filing a bug report." -msgstr "" - -#: ../../content/administration/install/deploy.rst:763 -msgid "Since Odoo 13.0, ES6 is supported. Therefore, IE support is dropped." -msgstr "" - -#: ../../content/administration/install/deploy.rst:766 -msgid "to have multiple Odoo installations use the same PostgreSQL database, or to provide more computing resources to both software." -msgstr "" - -#: ../../content/administration/install/deploy.rst:769 -msgid "technically a tool like socat_ can be used to proxy UNIX sockets across networks, but that is mostly for software which can only be used over UNIX sockets" -msgstr "" - -#: ../../content/administration/install/deploy.rst:773 -msgid "or be accessible only over an internal packet-switched network, but that requires secured switches, protections against `ARP spoofing`_ and precludes usage of WiFi. Even over secure packet-switched networks, deployment over HTTPS is recommended, and possible costs are lowered as \"self-signed\" certificates are easier to deploy on a controlled environment than over the internet." -msgstr "" - -#: ../../content/administration/install/email_gateway.rst:3 -msgid "Email gateway" -msgstr "" - -#: ../../content/administration/install/email_gateway.rst:5 -msgid "The Odoo mail gateway allows you to inject directly all the received emails in Odoo." -msgstr "" - -#: ../../content/administration/install/email_gateway.rst:7 -msgid "Its principle is straightforward: your SMTP server executes the \"mailgate\" script for every new incoming email." -msgstr "" - -#: ../../content/administration/install/email_gateway.rst:10 -msgid "The script takes care of connecting to your Odoo database through XML-RPC, and send the emails via the `MailThread.message_process()` feature." -msgstr "" - -#: ../../content/administration/install/email_gateway.rst:14 -msgid "Prerequisites" -msgstr "" - -#: ../../content/administration/install/email_gateway.rst:16 -msgid "Administrator access to the Odoo database." -msgstr "" - -#: ../../content/administration/install/email_gateway.rst:17 -msgid "Your own mail server such as Postfix or Exim." -msgstr "" - -#: ../../content/administration/install/email_gateway.rst:18 -msgid "Technical knowledge on how to configure an email server." -msgstr "" - -#: ../../content/administration/install/email_gateway.rst:21 -msgid "For Postfix" -msgstr "" - -#: ../../content/administration/install/email_gateway.rst:23 -msgid "In you alias config (:file:`/etc/aliases`):" -msgstr "" - -#: ../../content/administration/install/email_gateway.rst:30 -#: ../../content/administration/install/email_gateway.rst:45 -msgid "Resources" -msgstr "" - -#: ../../content/administration/install/email_gateway.rst:32 -msgid "`Postfix `_" -msgstr "" - -#: ../../content/administration/install/email_gateway.rst:33 -msgid "`Postfix aliases `_" -msgstr "" - -#: ../../content/administration/install/email_gateway.rst:34 -msgid "`Postfix virtual `_" -msgstr "" - -#: ../../content/administration/install/email_gateway.rst:38 -msgid "For Exim" -msgstr "" - -#: ../../content/administration/install/email_gateway.rst:47 -msgid "`Exim `_" -msgstr "" - -#: ../../content/administration/install/email_gateway.rst:50 -msgid "If you don't have access/manage your email server, use :ref:`inbound messages `." -msgstr "" - -#: ../../content/administration/install/geo_ip.rst:3 -msgid "Geo IP" -msgstr "" - -#: ../../content/administration/install/geo_ip.rst:6 -msgid "This documentation only applies to On-premise databases." -msgstr "" - -#: ../../content/administration/install/geo_ip.rst:9 +#: ../../content/administration.rst:16 +#: ../../content/administration/on_premise/geo_ip.rst:9 msgid "Installation" msgstr "" -#: ../../content/administration/install/geo_ip.rst:11 -msgid "Download both the GeoLite2 City and Country `databases `_. You should end up with two files called :file:`GeoLite2-City.mmdb` and :file:`GeoLite2-Country.mmdb`." +#: ../../content/administration.rst:18 +msgid "Depending on the intended use case, there are multiple ways to install Odoo - or not install it at all." msgstr "" -#: ../../content/administration/install/geo_ip.rst:15 -msgid "Move the files to the folder :file:`/usr/share/GeoIP/`." +#: ../../content/administration.rst:21 +msgid ":doc:`Online ` is the easiest way to use Odoo in production or to try it." msgstr "" -#: ../../content/administration/install/geo_ip.rst:22 -msgid "Restart the server" +#: ../../content/administration.rst:23 +msgid ":doc:`Packaged installers ` are suitable for testing Odoo and developing modules. They can be used for long-term production with additional deployment and maintenance work." msgstr "" -#: ../../content/administration/install/geo_ip.rst:25 -msgid "If you don't want to locate the geoip database in :file:`/usr/share/GeoIP/`, use the :option:`--geoip-city-db ` and :option:`--geoip-country-db ` options of the Odoo command line interface. These options take the absolute path to the GeoIP database file and use it as the GeoIP database. For example:" +#: ../../content/administration.rst:27 +msgid ":doc:`Source install ` provides greater flexibility, as it allows, for example, running multiple Odoo versions on the same system. It is adequate to develop modules and can be used as a base for production deployment." msgstr "" -#: ../../content/administration/install/geo_ip.rst:36 -msgid ":doc:`CLI documentation `." +#: ../../content/administration.rst:31 +msgid "A `Docker `_ base image is available for development or deployment." msgstr "" -#: ../../content/administration/install/geo_ip.rst:39 -msgid "Test GeoIP geolocation in your Odoo website" +#: ../../content/administration.rst:37 +msgid "Editions" msgstr "" -#: ../../content/administration/install/geo_ip.rst:41 -msgid "Edit a web page to include some geo-ip information such as the country name of the current request IP address. To do so:" +#: ../../content/administration.rst:39 +msgid "There are two different editions." msgstr "" -#: ../../content/administration/install/geo_ip.rst:44 -msgid "Go to your website. Open the web page that you want to test ``GeoIP``." +#: ../../content/administration.rst:41 +msgid "**Odoo Community** is the free and open-source version of the software, licensed under the `GNU LGPLv3 `_. It is the core upon which Odoo Enterprise is built." msgstr "" -#: ../../content/administration/install/geo_ip.rst:45 -msgid "Choose :menuselection:`Customize --> HTML/CSS/JS Editor`." +#: ../../content/administration.rst:45 +msgid "**Odoo Enterprise** is the shared source version of the software, giving access to more functionalities, including functional support, upgrades, and hosting. `Pricing `_ starts from one app free." msgstr "" -#: ../../content/administration/install/geo_ip.rst:46 -msgid "Add the following piece of XML in the page :" +#: ../../content/administration.rst:50 +msgid ":doc:`Switch from Community to Enterprise ` at any time (except for the source install)." msgstr "" -#: ../../content/administration/install/geo_ip.rst:52 -msgid "Save and refresh the page." +#: ../../content/administration/hosting.rst:3 +msgid "Hosting" msgstr "" -#: ../../content/administration/install/geo_ip.rst:54 -msgid "Geo-ip is working if you read your country name displayed in bold in the middle of the page." +#: ../../content/administration/hosting.rst:8 +msgid "Change hosting solution" msgstr "" -#: ../../content/administration/install/geo_ip.rst:56 -msgid "In case you read \"**geoip failure**\" instead then the geolocalization failed. The common causes are:" +#: ../../content/administration/hosting.rst:10 +msgid "The instructions to change the hosting type of a database depend on the current solution used and to which solution the database should be moved." msgstr "" -#: ../../content/administration/install/geo_ip.rst:58 -msgid "The browsing IP address is the localhost (``127.0.0.1``) or a local area network one. If you don't know, you can access your website using mobile data." +#: ../../content/administration/hosting.rst:14 +msgid "Transferring an on-premise database" msgstr "" -#: ../../content/administration/install/geo_ip.rst:60 -msgid "You are using a reverse-proxy (apache, nginx) in front of Odoo but didn't start Odoo with the proxy-mode enabled. See :option:`proxy mode `." +#: ../../content/administration/hosting.rst:17 +#: ../../content/administration/hosting.rst:90 +msgid "To Odoo Online" msgstr "" -#: ../../content/administration/install/geo_ip.rst:62 -msgid "The GeoIP database is corrupt, missing or unaccessible. In such case a warning was logged in the server logs." +#: ../../content/administration/hosting.rst:20 +#: ../../content/administration/hosting.rst:93 +msgid "Odoo Online is *not* compatible with **non-standard apps**." msgstr "" -#: ../../content/administration/install/online.rst:3 -msgid "Online" +#: ../../content/administration/hosting.rst:21 +msgid "The database's current version must be :doc:`supported `." msgstr "" -#: ../../content/administration/install/online.rst:5 -msgid "Online instances are accessed using any web browser and do not require a local installation." +#: ../../content/administration/hosting.rst:23 +msgid "Create a :ref:`duplicate of the database `." msgstr "" -#: ../../content/administration/install/online.rst:8 -msgid "Demo" +#: ../../content/administration/hosting.rst:24 +msgid "In this duplicate, uninstall all **non-standard apps**." msgstr "" -#: ../../content/administration/install/online.rst:10 -msgid "To quickly try out Odoo, shared `demo `_ instances are available. No registration is required, but each instance only lives for a few hours." +#: ../../content/administration/hosting.rst:25 +msgid "Use the database manager to grab a *dump with filestore*." msgstr "" -#: ../../content/administration/install/online.rst:14 -#: ../../content/administration/maintain/domain_names.rst:157 -#: ../../content/administration/maintain/domain_names.rst:211 -#: ../../content/administration/maintain/supported_versions.rst:29 +#: ../../content/administration/hosting.rst:26 +msgid "`Submit a support ticket `_ including the following:" +msgstr "" + +#: ../../content/administration/hosting.rst:28 +#: ../../content/administration/hosting.rst:98 +msgid "your **subscription number**," +msgstr "" + +#: ../../content/administration/hosting.rst:29 +msgid "the **URL** you want to use for the database (e.g., `company.odoo.com`), and" +msgstr "" + +#: ../../content/administration/hosting.rst:30 +msgid "the **dump** as an attachment or as a link to the file (required for 60 MB+ files)." +msgstr "" + +#: ../../content/administration/hosting.rst:32 +#: ../../content/administration/hosting.rst:105 +msgid "Odoo then makes sure the database is compatible before putting it online. In case of technical issues during the process, Odoo might contact you." +msgstr "" + +#: ../../content/administration/hosting.rst:36 +#: ../../content/administration/hosting.rst:109 +msgid "If you have time constraints, `submit a support ticket `_ as soon as possible to schedule the transfer." +msgstr "" + +#: ../../content/administration/hosting.rst:40 +#: ../../content/administration/hosting.rst:77 +msgid "To Odoo.sh" +msgstr "" + +#: ../../content/administration/hosting.rst:42 +#: ../../content/administration/hosting.rst:83 +msgid "Follow the instructions found in :ref:`the Import your database section ` of the Odoo.sh *Create your project* documentation." +msgstr "" + +#: ../../content/administration/hosting.rst:46 +msgid "Transferring an Odoo Online database" +msgstr "" + +#: ../../content/administration/hosting.rst:49 +msgid "Odoo Online's :ref:`intermediary versions ` cannot be hosted on-premise as that type of hosting does not support those versions. Therefore, if the database to transfer is running an intermediary version, it must be upgraded first to the next :ref:`major version `, waiting for its release if necessary." +msgstr "" + +#: ../../content/administration/hosting.rst:55 +msgid "Transferring an online database running on Odoo 16.3 would require first upgrading it to Odoo 17.0." +msgstr "" + +#: ../../content/administration/hosting.rst:59 +msgid "Click the gear icon (:guilabel:`⚙`) next to the database name on the `Odoo Online database manager `_ to display its version number." +msgstr "" + +#: ../../content/administration/hosting.rst:63 +msgid "If there is an active Odoo subscription linked to the database being migrated, reach out to the Customer Service Manager or `submit a support ticket `_ to complete the subscription transfer." +msgstr "" + +#: ../../content/administration/hosting.rst:68 +#: ../../content/administration/hosting.rst:118 +msgid "To on-premise" +msgstr "" + +#: ../../content/administration/hosting.rst:70 +#: ../../content/administration/hosting.rst:79 +msgid "Sign in to `the Odoo Online database manager `_ and click the gear icon (:guilabel:`⚙`) next to the database name to :guilabel:`Download` a backup. If the download fails due to the file being too large, `contact Odoo support `_." +msgstr "" + +#: ../../content/administration/hosting.rst:74 +#: ../../content/administration/hosting.rst:121 +msgid "Restore the database from the database manager on your local server using the backup." +msgstr "" + +#: ../../content/administration/hosting.rst:87 +msgid "Transferring an Odoo.sh database" +msgstr "" + +#: ../../content/administration/hosting.rst:95 +msgid "Uninstall all **non-standard apps** in a staging build before doing it in the production build." +msgstr "" + +#: ../../content/administration/hosting.rst:96 +msgid "`Create a support ticket `_ including the following:" +msgstr "" + +#: ../../content/administration/hosting.rst:99 +msgid "the **URL** you want to use for the database (e.g., `company.odoo.com`)," +msgstr "" + +#: ../../content/administration/hosting.rst:100 +msgid "which **branch** should be migrated," +msgstr "" + +#: ../../content/administration/hosting.rst:101 +msgid "in which **region** you want the database to be hosted (Americas, Europe, or Asia)," +msgstr "" + +#: ../../content/administration/hosting.rst:102 +msgid "which user(s) will be the **administrator(s)**, and" +msgstr "" + +#: ../../content/administration/hosting.rst:103 +msgid "**when** (and in which timezone) you want the database to be up and running." +msgstr "" + +#: ../../content/administration/hosting.rst:111 +msgid "Select the **region** closest to most of your users to reduce latency." +msgstr "" + +#: ../../content/administration/hosting.rst:112 +msgid "Future **administrator(s)** must have an Odoo.com account." +msgstr "" + +#: ../../content/administration/hosting.rst:113 +msgid "The **date and time** you want the database to be up and running are helpful to organize the switch from the Odoo.sh server to the Odoo Online servers." +msgstr "" + +#: ../../content/administration/hosting.rst:115 +msgid "Databases are **not reachable** during their migration." +msgstr "" + +#: ../../content/administration/hosting.rst:120 +msgid "Download a :ref:`backup of your Odoo.sh production database `." +msgstr "" + +#: ../../content/administration/neutralized_database.rst:3 +msgid "Neutralized database" +msgstr "" + +#: ../../content/administration/neutralized_database.rst:5 +msgid "A neutralized database is a non-production database on which several parameters are deactivated. This enables one to carry out tests without the risk of launching specific automated processes that could impact production data (e.g., sending emails to customers). Live access is removed and turned into a testing environment." +msgstr "" + +#: ../../content/administration/neutralized_database.rst:11 +msgid "**Any testing database created is a neutralized database:**" +msgstr "" + +#: ../../content/administration/neutralized_database.rst:13 +msgid "testing backup databases" +msgstr "" + +#: ../../content/administration/neutralized_database.rst:14 +msgid "duplicate databases" +msgstr "" + +#: ../../content/administration/neutralized_database.rst:15 +msgid "for Odoo.sh: staging and development databases" +msgstr "" + +#: ../../content/administration/neutralized_database.rst:18 +msgid "A database can also be neutralized when upgrading, as it is vital to do some tests before switching to a new version." +msgstr "" + +#: ../../content/administration/neutralized_database.rst:22 +msgid "Deactivated features" +msgstr "" + +#: ../../content/administration/neutralized_database.rst:24 +msgid "Here is a non-exhaustive list of the deactivated parameters:" +msgstr "" + +#: ../../content/administration/neutralized_database.rst:26 +msgid "all planned actions (e.g., automatic invoicing of subscriptions, mass mailing, etc.)" +msgstr "" + +#: ../../content/administration/neutralized_database.rst:27 +msgid "outgoing emails" +msgstr "" + +#: ../../content/administration/neutralized_database.rst:28 +msgid "bank synchronization" +msgstr "" + +#: ../../content/administration/neutralized_database.rst:29 +msgid "payment providers" +msgstr "" + +#: ../../content/administration/neutralized_database.rst:30 +msgid "delivery methods" +msgstr "" + +#: ../../content/administration/neutralized_database.rst:31 +msgid ":abbr:`IAP (In-App Purchase)` tokens" +msgstr "" + +#: ../../content/administration/neutralized_database.rst:34 +msgid "**A red banner at the top of the screen is displayed on the neutralized database so that it can be seen immediately.**" +msgstr "" + +#: ../../content/administration/odoo_accounts.rst:3 +msgid "Odoo.com accounts" +msgstr "" + +#: ../../content/administration/odoo_accounts.rst:5 +msgid "This documentation is dedicated to edits made to an Odoo.com account. The following processes describe how to delete an Odoo.com account, and how to change the password on an Odoo.com account." +msgstr "" + +#: ../../content/administration/odoo_accounts.rst:9 +msgid "Delete Odoo.com account" +msgstr "" + +#: ../../content/administration/odoo_accounts.rst:11 +msgid "To delete an Odoo.com account, start by clicking the profile icon in the upper-right corner (represented by the username and icon) to reveal a drop-down menu. From the drop-down menu, select :guilabel:`My Odoo.com account`, which reveals the user portal." +msgstr "" + +#: ../../content/administration/odoo_accounts.rst:15 +msgid "From the user portal, the delete option can be accessed by going to :menuselection:`My Account --> Edit Security Settings --> Delete Account`. It can also be accessed by going to `https://www.odoo.com/my/home `_." +msgstr "" + +#: ../../content/administration/odoo_accounts.rst:20 +msgid "Deleting an Odoo account is irreversible. Be careful performing this action, as the Odoo.com account is **not** retrievable once deleted." +msgstr "" + +#: ../../content/administration/odoo_accounts.rst:23 +msgid "Upon clicking the :guilabel:`Delete Account` button, a pop-up window appears, requesting confirmation for the account deletion." +msgstr "" + +#: ../../content/administration/odoo_accounts.rst:-1 +msgid "Clicking on the Delete Account button will populate a window verifying the change." +msgstr "" + +#: ../../content/administration/odoo_accounts.rst:30 +msgid "To confirm the deletion, enter the :guilabel:`Password` and the :guilabel:`Login` for the account being deleted. Then, click the :guilabel:`Delete Account` button to confirm the deletion." +msgstr "" + +#: ../../content/administration/odoo_accounts.rst:34 +msgid "Odoo.com account password change" +msgstr "" + +#: ../../content/administration/odoo_accounts.rst:36 +msgid "To change an Odoo.com account password, first login into the Odoo.com user account from the Odoo.com login page. After logging-in, go to the upper-right corner of the screen, and click the :guilabel:`▼ (down arrow)` icon next to the profile icon. Then, select :guilabel:`My Account`, and a portal dashboard appears." +msgstr "" + +#: ../../content/administration/odoo_accounts.rst:41 +msgid "To change the Odoo.com password, click on the :guilabel:`Edit Security Settings` link, below the :menuselection:`Account Security` section. Next, make the necessary changes by typing in the current :guilabel:`Password`, :guilabel:`New Password`, and verify the new password. Lastly, click on :guilabel:`Change Password` to complete the password change." +msgstr "" + +#: ../../content/administration/odoo_accounts.rst:47 +msgid "If a customer would like to change the login, contact Odoo support `here `_." +msgstr "" + +#: ../../content/administration/odoo_accounts.rst:51 +msgid "Passwords for Odoo.com users and portal users remain separate, even if the same email address is used." +msgstr "" + +#: ../../content/administration/odoo_accounts.rst:55 +msgid "Add two-factor authentication" +msgstr "" + +#: ../../content/administration/odoo_accounts.rst:57 +msgid "To add two-factor authentication, login into the Odoo.com user account from the Odoo.com login page. After logging-in, go to the upper-right corner of the screen, and click the :guilabel:`▼ (down arrow)` icon next to the :guilabel:`profile icon`. Then, select :guilabel:`My Account`, and a portal dashboard appears." +msgstr "" + +#: ../../content/administration/odoo_accounts.rst:62 +msgid "If the user would like to turn on two-factor authentication (2FA) for Odoo.com access, click on the :guilabel:`Edit Security Settings` link below the :menuselection:`Account Security` section." +msgstr "" + +#: ../../content/administration/odoo_accounts.rst:65 +msgid "Click on :guilabel:`Enable two-factor authentication` to turn on :abbr:`2FA (two-factor authentication)`. Then, confirm the current password in the :guilabel:`Password` field. Next, click on :guilabel:`Confirm Password`. Following that, activate :abbr:`2FA (two-factor authentication)` in a :abbr:`2FA (two-factor authentication)` app (Google Authenticator, Authy, etc.), by scanning the :guilabel:`QR code` or entering a :guilabel:`Verification Code`." +msgstr "" + +#: ../../content/administration/odoo_accounts.rst:71 +msgid "Finally, click on :guilabel:`Enable two-factor authentication` to complete the setup." +msgstr "" + +#: ../../content/administration/odoo_accounts.rst:74 +msgid "Under :guilabel:`My Account` Odoo.com users can also access the following:" +msgstr "" + +#: ../../content/administration/odoo_accounts.rst:76 +msgid ":guilabel:`My Partner dashboard`" +msgstr "" + +#: ../../content/administration/odoo_accounts.rst:77 +msgid ":guilabel:`My In-App Services`" +msgstr "" + +#: ../../content/administration/odoo_accounts.rst:78 +msgid ":guilabel:`My Apps Dashboard`" +msgstr "" + +#: ../../content/administration/odoo_online.rst:3 +#: ../../content/administration/supported_versions.rst:29 #: ../../content/administration/upgrade.rst:90 #: ../../content/administration/upgrade.rst:307 msgid "Odoo Online" msgstr "" -#: ../../content/administration/install/online.rst:16 -msgid "`Odoo Online `_ provides private instances which are fully managed and hosted by Odoo. It can be used for long-term production or to test Odoo thoroughly, including customizations that don't require code." +#: ../../content/administration/odoo_online.rst:5 +msgid "`Odoo Online `_ provides private databases which are fully managed and hosted by Odoo. It can be used for long-term production or to test Odoo thoroughly, including customizations that don't require code." msgstr "" -#: ../../content/administration/install/online.rst:21 +#: ../../content/administration/odoo_online.rst:10 msgid "Odoo Online is incompatible with custom modules or the Odoo App Store." msgstr "" -#: ../../content/administration/install/packages.rst:3 -msgid "Packaged installers" +#: ../../content/administration/odoo_online.rst:12 +msgid "Odoo Online databases are accessed using any web browser and do not require a local installation." msgstr "" -#: ../../content/administration/install/packages.rst:5 -msgid "Odoo provides packaged installers for Debian-based Linux distributions (Debian, Ubuntu, etc.), RPM-based Linux distributions (Fedora, CentOS, RHEL, etc.), and Windows for the Community and Enterprise editions." +#: ../../content/administration/odoo_online.rst:14 +msgid "To quickly try out Odoo, shared `demo `_ instances are available. No registration is required, but each instance only lives for a few hours." msgstr "" -#: ../../content/administration/install/packages.rst:9 -msgid "Official **Community** nightly packages with all relevant dependency requirements are available on the `nightly server `_." -msgstr "" - -#: ../../content/administration/install/packages.rst:13 -msgid "Nightly packages may be difficult to keep up to date." -msgstr "" - -#: ../../content/administration/install/packages.rst:15 -msgid "Official **Community** and **Enterprise** packages can be downloaded from the `Odoo download page `_." -msgstr "" - -#: ../../content/administration/install/packages.rst:19 -msgid "It is required to be logged in as a paying on-premise customer or partner to download the Enterprise packages." -msgstr "" - -#: ../../content/administration/install/packages.rst:25 -#: ../../content/administration/install/source.rst:52 -#: ../../content/administration/install/source.rst:129 -#: ../../content/administration/install/source.rst:152 -#: ../../content/administration/install/source.rst:174 -#: ../../content/administration/install/source.rst:199 -#: ../../content/administration/install/source.rst:228 -#: ../../content/administration/install/source.rst:271 -#: ../../content/administration/install/source.rst:384 -#: ../../content/administration/install/source.rst:446 -msgid "Linux" -msgstr "" - -#: ../../content/administration/install/packages.rst:28 -#: ../../content/administration/install/source.rst:116 -msgid "Prepare" -msgstr "" - -#: ../../content/administration/install/packages.rst:30 -msgid "Odoo needs a `PostgreSQL `_ server to run properly." -msgstr "" - -#: ../../content/administration/install/packages.rst:34 -#: ../../content/administration/install/packages.rst:70 -#: ../../content/administration/install/packages.rst:100 -#: ../../content/administration/install/source.rst:278 -msgid "Debian/Ubuntu" -msgstr "" - -#: ../../content/administration/install/packages.rst:36 -msgid "The default configuration for the Odoo 'deb' package is to use the PostgreSQL server on the same host as the Odoo instance. Execute the following command to install the PostgreSQL server:" -msgstr "" - -#: ../../content/administration/install/packages.rst:44 -#: ../../content/administration/install/packages.rst:80 -#: ../../content/administration/install/packages.rst:132 -msgid "Fedora" -msgstr "" - -#: ../../content/administration/install/packages.rst:46 -msgid "Make sure that the `sudo` command is available and well configured and, only then, execute the following command to install the PostgreSQL server:" -msgstr "" - -#: ../../content/administration/install/packages.rst:57 -#: ../../content/administration/install/source.rst:416 -msgid "`wkhtmltopdf` is not installed through **pip** and must be installed manually in `version 0.12.6 `_ for it to support headers and footers. Check out the `wkhtmltopdf wiki `_ for more details on the various versions." -msgstr "" - -#: ../../content/administration/install/packages.rst:63 -msgid "Repository" -msgstr "" - -#: ../../content/administration/install/packages.rst:65 -msgid "Odoo S.A. provides a repository that can be used to install the **Community** edition by executing the following commands:" -msgstr "" - -#: ../../content/administration/install/packages.rst:78 -msgid "Use the usual `apt-get upgrade` command to keep the installation up-to-date." -msgstr "" - -#: ../../content/administration/install/packages.rst:90 -msgid "Currently, there is no nightly repository for the Enterprise edition." -msgstr "" - -#: ../../content/administration/install/packages.rst:93 -msgid "Distribution package" -msgstr "" - -#: ../../content/administration/install/packages.rst:95 -msgid "Instead of using the repository, packages for both the **Community** and **Enterprise** editions can be downloaded from the `Odoo download page `_." -msgstr "" - -#: ../../content/administration/install/packages.rst:103 -msgid "Odoo 17 'deb' package currently supports `Debian Buster `_ and `Ubuntu 18.04 `_ or above." -msgstr "" - -#: ../../content/administration/install/packages.rst:107 -msgid "Once downloaded, execute the following commands **as root** to install Odoo as a service, create the necessary PostgreSQL user, and automatically start the server:" -msgstr "" - -#: ../../content/administration/install/packages.rst:117 -msgid "The `python3-xlwt` Debian package, needed to export into the XLS format, does not exist in Debian Buster nor Ubuntu 18.04. If needed, install it manually with the following:" -msgstr "" - -#: ../../content/administration/install/packages.rst:124 -msgid "The `num2words` Python package - needed to render textual amounts - does not exist in Debian Buster nor Ubuntu 18.04, which could cause problems with the `l10n_mx_edi` module. If needed, install it manually with the following:" -msgstr "" - -#: ../../content/administration/install/packages.rst:135 -msgid "Odoo 17 'rpm' package supports Fedora 36." -msgstr "" - -#: ../../content/administration/install/packages.rst:137 -msgid "Once downloaded, the package can be installed using the 'dnf' package manager:" -msgstr "" - -#: ../../content/administration/install/packages.rst:148 -#: ../../content/administration/install/source.rst:70 -#: ../../content/administration/install/source.rst:133 -#: ../../content/administration/install/source.rst:158 -#: ../../content/administration/install/source.rst:180 -#: ../../content/administration/install/source.rst:208 -#: ../../content/administration/install/source.rst:239 -#: ../../content/administration/install/source.rst:324 -#: ../../content/administration/install/source.rst:393 -#: ../../content/administration/install/source.rst:456 -msgid "Windows" -msgstr "" - -#: ../../content/administration/install/packages.rst:151 -msgid "Windows packaging is offered for the convenience of testing or running single-user local instances but production deployment is discouraged due to a number of limitations and risks associated with deploying Odoo on a Windows platform." -msgstr "" - -#: ../../content/administration/install/packages.rst:155 -msgid "Download the installer from the `nightly server `_ (Community only) or the Windows installer from the `Odoo download page `_ (any edition." -msgstr "" - -#: ../../content/administration/install/packages.rst:158 -msgid "Execute the downloaded file." -msgstr "" - -#: ../../content/administration/install/packages.rst:161 -msgid "On Windows 8 and later, a warning titled *Windows protected your PC* may be displayed. Click **More Info** and then **Run anyway** to proceed." -msgstr "" - -#: ../../content/administration/install/packages.rst:164 -msgid "Accept the `UAC `_ prompt." -msgstr "" - -#: ../../content/administration/install/packages.rst:165 -msgid "Go through the installation steps." -msgstr "" - -#: ../../content/administration/install/packages.rst:167 -msgid "Odoo launches automatically at the end of the installation." -msgstr "" - -#: ../../content/administration/install/source.rst:3 -msgid "Source" -msgstr "" - -#: ../../content/administration/install/source.rst:5 -msgid "The source 'installation' is not about installing Odoo but running it directly from the source instead." -msgstr "" - -#: ../../content/administration/install/source.rst:8 -msgid "Using the Odoo source can be more convenient for module developers as it is more easily accessible than using packaged installers." -msgstr "" - -#: ../../content/administration/install/source.rst:11 -msgid "It makes starting and stopping Odoo more flexible and explicit than the services set up by the packaged installers. Also, it allows overriding settings using :ref:`command-line parameters ` without needing to edit a configuration file." -msgstr "" - -#: ../../content/administration/install/source.rst:15 -msgid "Finally, it provides greater control over the system's setup and allows to more easily keep (and run) multiple versions of Odoo side-by-side." -msgstr "" - -#: ../../content/administration/install/source.rst:19 -msgid "Fetch the sources" -msgstr "" - -#: ../../content/administration/install/source.rst:21 -msgid "There are two ways to obtain the source code of Odoo: as a ZIP **archive** or through **Git**." -msgstr "" - -#: ../../content/administration/install/source.rst:24 -msgid "Archive" -msgstr "" - -#: ../../content/administration/install/source.rst:26 -msgid "Community edition:" -msgstr "" - -#: ../../content/administration/install/source.rst:28 -#: ../../content/administration/install/source.rst:34 -msgid "`Odoo download page `_" -msgstr "" - -#: ../../content/administration/install/source.rst:29 -msgid "`GitHub Community repository `_" -msgstr "" - -#: ../../content/administration/install/source.rst:30 -msgid "`Nightly server `_" -msgstr "" - -#: ../../content/administration/install/source.rst:32 -msgid "Enterprise edition:" -msgstr "" - -#: ../../content/administration/install/source.rst:35 -msgid "`GitHub Enterprise repository `_" -msgstr "" - -#: ../../content/administration/install/source.rst:40 -msgid "Git" -msgstr "" - -#: ../../content/administration/install/source.rst:43 -msgid "It is required to have `Git `_ installed, and it is recommended to have a basic knowledge of Git commands to proceed." -msgstr "" - -#: ../../content/administration/install/source.rst:46 -msgid "To clone a Git repository, choose between cloning with HTTPS or SSH. In most cases, the best option is HTTPS. However, choose SSH to contribute to Odoo source code or when following the :doc:`Getting Started developer tutorial `." -msgstr "" - -#: ../../content/administration/install/source.rst:56 -#: ../../content/administration/install/source.rst:74 -#: ../../content/administration/install/source.rst:92 -msgid "Clone with HTTPS" -msgstr "" - -#: ../../content/administration/install/source.rst:63 -#: ../../content/administration/install/source.rst:81 -#: ../../content/administration/install/source.rst:99 -msgid "Clone with SSH" -msgstr "" - -#: ../../content/administration/install/source.rst:88 -#: ../../content/administration/install/source.rst:141 -#: ../../content/administration/install/source.rst:164 -#: ../../content/administration/install/source.rst:186 -#: ../../content/administration/install/source.rst:213 -#: ../../content/administration/install/source.rst:253 -#: ../../content/administration/install/source.rst:347 -#: ../../content/administration/install/source.rst:405 -#: ../../content/administration/install/source.rst:467 -msgid "Mac OS" -msgstr "" - -#: ../../content/administration/install/source.rst:107 -msgid "**The Enterprise git repository does not contain the full Odoo source code**. It is only a collection of extra add-ons. The main server code is in the Community edition. Running the Enterprise version means running the server from the Community version with the `addons-path` option set to the folder with the Enterprise edition. It is required to clone both the Community and Enterprise repositories to have a working Odoo Enterprise installation." -msgstr "" - -#: ../../content/administration/install/source.rst:119 -msgid "Python" -msgstr "" - -#: ../../content/administration/install/source.rst:121 -msgid "Odoo requires **Python 3.10** or later to run." -msgstr "" - -#: ../../content/administration/install/source.rst:123 -msgid "Minimum requirement updated from Python 3.7 to Python 3.10." -msgstr "" - -#: ../../content/administration/install/source.rst:131 -msgid "Use a package manager to download and install Python 3 if needed." -msgstr "" - -#: ../../content/administration/install/source.rst:135 -msgid "`Download the latest version of Python 3 `_ and install it." -msgstr "" - -#: ../../content/administration/install/source.rst:138 -msgid "During installation, check **Add Python 3 to PATH**, then click **Customize Installation** and make sure that **pip** is checked." -msgstr "" - -#: ../../content/administration/install/source.rst:143 -msgid "Use a package manager (`Homebrew `_, `MacPorts `_) to download and install Python 3 if needed." -msgstr "" - -#: ../../content/administration/install/source.rst:147 -msgid "If Python 3 is already installed, make sure that the version is 3.7 or above, as previous versions are not compatible with Odoo." -msgstr "" - -#: ../../content/administration/install/source.rst:170 -msgid "Verify that `pip `_ is also installed for this version." -msgstr "" - -#: ../../content/administration/install/source.rst:195 -msgid "Odoo uses PostgreSQL as its database management system." -msgstr "" - -#: ../../content/administration/install/source.rst:201 -msgid "Use a package manager to download and install PostgreSQL (supported versions: 12.0 or above). It can be achieved by executing the following:" -msgstr "" - -#: ../../content/administration/install/source.rst:210 -msgid "`Download PostgreSQL `_ (supported versions: 12.0 or above) and install it." -msgstr "" - -#: ../../content/administration/install/source.rst:215 -msgid "Use `Postgres.app `_ to download and install PostgreSQL (supported version: 12.0 or above)." -msgstr "" - -#: ../../content/administration/install/source.rst:219 -msgid "To make the command line tools bundled with Postgres.app available, make sure to set up the `$PATH` variable by following the `Postgres.app CLI tools instructions `_." -msgstr "" - -#: ../../content/administration/install/source.rst:223 -msgid "By default, the only user is `postgres`. As Odoo forbids connecting as `postgres`, create a new PostgreSQL user." -msgstr "" - -#: ../../content/administration/install/source.rst:236 -#: ../../content/administration/install/source.rst:261 -msgid "Because the PostgreSQL user has the same name as the Unix login, it is possible to connect to the database without a password." -msgstr "" - -#: ../../content/administration/install/source.rst:241 -msgid "Add PostgreSQL's `bin` directory (by default: :file:`C:\\\\Program Files\\\\PostgreSQL\\\\\\\\bin`) to the `PATH`." -msgstr "" - -#: ../../content/administration/install/source.rst:243 -msgid "Create a postgres user with a password using the pg admin gui:" -msgstr "" - -#: ../../content/administration/install/source.rst:245 -msgid "Open **pgAdmin**." -msgstr "" - -#: ../../content/administration/install/source.rst:246 -msgid "Double-click the server to create a connection." -msgstr "" - -#: ../../content/administration/install/source.rst:247 -msgid "Select :menuselection:`Object --> Create --> Login/Group Role`." -msgstr "" - -#: ../../content/administration/install/source.rst:248 -msgid "Enter the username in the **Role Name** field (e.g., `odoo`)." -msgstr "" - -#: ../../content/administration/install/source.rst:249 -msgid "Open the **Definition** tab, enter a password (e.g., `odoo`), and click **Save**." -msgstr "" - -#: ../../content/administration/install/source.rst:250 -msgid "Open the **Privileges** tab and switch **Can login?** to `Yes` and **Create database?** to `Yes`." -msgstr "" - -#: ../../content/administration/install/source.rst:267 -msgid "Dependencies" -msgstr "" - -#: ../../content/administration/install/source.rst:273 -msgid "Using **distribution packages** is the preferred way of installing dependencies. Alternatively, install the Python dependencies with **pip**." -msgstr "" - -#: ../../content/administration/install/source.rst:280 -msgid "For Debian-based systems, the packages are listed in the `debian/control `_ file of the Odoo sources." -msgstr "" - -#: ../../content/administration/install/source.rst:283 -msgid "On Debian/Ubuntu, the following commands should install the required packages:" -msgstr "" - -#: ../../content/administration/install/source.rst:290 -msgid "Install with pip" -msgstr "" - -#: ../../content/administration/install/source.rst:292 -msgid "As some of the Python packages need a compilation step, they require system libraries to be installed." -msgstr "" - -#: ../../content/administration/install/source.rst:295 -msgid "On Debian/Ubuntu, the following command should install these required libraries:" -msgstr "" - -#: ../../content/administration/install/source.rst:301 -msgid "Odoo dependencies are listed in the :file:`requirements.txt` file located at the root of the Odoo Community directory." -msgstr "" - -#: ../../content/administration/install/source.rst:305 -msgid "The Python packages in :file:`requirements.txt` are based on their stable/LTS Debian/Ubuntu corresponding version at the moment of the Odoo release. For example, for Odoo 15.0, the `python3-babel` package version is 2.8.0 in Debian Bullseye and 2.6.0 in Ubuntu Focal. The lowest version is then chosen in the :file:`requirements.txt`." -msgstr "" - -#: ../../content/administration/install/source.rst:312 -#: ../../content/administration/install/source.rst:334 -#: ../../content/administration/install/source.rst:353 -msgid "It can be preferable not to mix Python module packages between different instances of Odoo or with the system. However, it is possible to use `virtualenv `_ to create isolated Python environments." -msgstr "" - -#: ../../content/administration/install/source.rst:316 -msgid "Navigate to the path of the Odoo Community installation (:file:`CommunityPath`) and run **pip** on the requirements file to install the requirements for the current user." -msgstr "" - -#: ../../content/administration/install/source.rst:326 -msgid "Before installing the dependencies, download and install the `Build Tools for Visual Studio `_. Select **C++ build tools** in the **Workloads** tab and install them when prompted." -msgstr "" - -#: ../../content/administration/install/source.rst:330 -#: ../../content/administration/install/source.rst:349 -msgid "Odoo dependencies are listed in the `requirements.txt` file located at the root of the Odoo Community directory." -msgstr "" - -#: ../../content/administration/install/source.rst:338 -msgid "Navigate to the path of the Odoo Community installation (`CommunityPath`) and run **pip** on the requirements file in a terminal **with Administrator privileges**:" -msgstr "" - -#: ../../content/administration/install/source.rst:357 -msgid "Navigate to the path of the Odoo Community installation (`CommunityPath`) and run **pip** on the requirements file:" -msgstr "" - -#: ../../content/administration/install/source.rst:367 -msgid "Non-Python dependencies must be installed with a package manager (`Homebrew `_, `MacPorts `_)." -msgstr "" - -#: ../../content/administration/install/source.rst:370 -msgid "Download and install the **Command Line Tools**:" -msgstr "" - -#: ../../content/administration/install/source.rst:376 -msgid "Use the package manager to install non-Python dependencies." -msgstr "" - -#: ../../content/administration/install/source.rst:379 -msgid "For languages using a **right-to-left interface** (such as Arabic or Hebrew), the `rtlcss` package is required." -msgstr "" - -#: ../../content/administration/install/source.rst:386 -msgid "Download and install **nodejs** and **npm** with a package manager." -msgstr "" - -#: ../../content/administration/install/source.rst:387 -#: ../../content/administration/install/source.rst:396 -#: ../../content/administration/install/source.rst:409 -msgid "Install `rtlcss`:" -msgstr "" - -#: ../../content/administration/install/source.rst:395 -msgid "Download and install `nodejs `_." -msgstr "" - -#: ../../content/administration/install/source.rst:402 -msgid "Edit the system environment's variable `PATH` to add the folder where `rtlcss.cmd` is located (typically: :file:`C:\\\\Users\\\\\\\\AppData\\\\Roaming\\\\npm\\\\`)." -msgstr "" - -#: ../../content/administration/install/source.rst:407 -msgid "Download and install **nodejs** with a package manager (`Homebrew `_, `MacPorts `_)." -msgstr "" - -#: ../../content/administration/install/source.rst:424 -msgid "Running Odoo" -msgstr "" - -#: ../../content/administration/install/source.rst:426 -msgid "Once all dependencies are set up, Odoo can be launched by running `odoo-bin`, the command-line interface of the server. It is located at the root of the Odoo Community directory." -msgstr "" - -#: ../../content/administration/install/source.rst:429 -msgid "To configure the server, either specify :ref:`command-line arguments ` or a :ref:`configuration file `." -msgstr "" - -#: ../../content/administration/install/source.rst:433 -msgid "For the Enterprise edition, add the path to the `enterprise` add-ons to the `addons-path` argument. Note that it must come before the other paths in `addons-path` for add-ons to be loaded correctly." -msgstr "" - -#: ../../content/administration/install/source.rst:437 -msgid "Common necessary configurations are:" -msgstr "" - -#: ../../content/administration/install/source.rst:439 -msgid "PostgreSQL user and password." -msgstr "" - -#: ../../content/administration/install/source.rst:440 -msgid "Custom addon paths beyond the defaults to load custom modules." -msgstr "" - -#: ../../content/administration/install/source.rst:442 -msgid "A typical way to run the server would be:" -msgstr "" - -#: ../../content/administration/install/source.rst:453 -#: ../../content/administration/install/source.rst:474 -msgid "Where `CommunityPath` is the path of the Odoo Community installation, and `mydb` is the name of the PostgreSQL database." -msgstr "" - -#: ../../content/administration/install/source.rst:463 -msgid "Where `CommunityPath` is the path of the Odoo Community installation, `dbuser` is the PostgreSQL login, `dbpassword` is the PostgreSQL password, and `mydb` is the name of the PostgreSQL database." -msgstr "" - -#: ../../content/administration/install/source.rst:477 -msgid "After the server has started (the INFO log `odoo.modules.loading: Modules loaded.` is printed), open http://localhost:8069 in a web browser and log into the Odoo database with the base administrator account: use `admin` as the email and, again, `admin` as the password." -msgstr "" - -#: ../../content/administration/install/source.rst:482 -msgid "From there, create and manage new :doc:`users <../../applications/general/users/manage_users>`." -msgstr "" - -#: ../../content/administration/install/source.rst:483 -msgid "The user account used to log into Odoo's web interface differs from the :option:`--db_user ` CLI argument." -msgstr "" - -#: ../../content/administration/install/source.rst:487 -msgid ":doc:`The list of CLI arguments for odoo-bin `" -msgstr "" - -#: ../../content/administration/maintain.rst:5 -msgid "Maintain" -msgstr "" - -#: ../../content/administration/maintain/azure_oauth.rst:3 -msgid "Connect Microsoft Outlook 365 to Odoo using Azure OAuth" -msgstr "" - -#: ../../content/administration/maintain/azure_oauth.rst:5 -msgid "Odoo is compatible with Microsoft's Azure OAuth for Microsoft 365. In order to send and receive secure emails from a custom domain, all that is required is to configure a few settings on the Azure platform and on the back end of the Odoo database. This configuration works with either a personal email address or an address created by a custom domain." -msgstr "" - -#: ../../content/administration/maintain/azure_oauth.rst:11 -msgid "`Microsoft Learn: Register an application with the Microsoft identity platform `_" -msgstr "" - -#: ../../content/administration/maintain/azure_oauth.rst:15 -msgid ":doc:`/applications/general/auth/azure`" -msgstr "" - -#: ../../content/administration/maintain/azure_oauth.rst:16 -msgid ":doc:`/applications/productivity/calendar/outlook`" -msgstr "" - -#: ../../content/administration/maintain/azure_oauth.rst:19 -msgid "Setup in Microsoft Azure Portal" -msgstr "" - -#: ../../content/administration/maintain/azure_oauth.rst:22 -msgid "Create a new application" -msgstr "" - -#: ../../content/administration/maintain/azure_oauth.rst:24 -msgid "To get started, go to `Microsoft's Azure Portal `_. Log in with the :guilabel:`Microsoft Outlook Office 365` account if there is one, otherwise log in with the personal :guilabel:`Microsoft account`. A user with administrative access to the Azure Settings will need to connect and perform the following configuration. Next, navigate to the section labeled :guilabel:`Manage Microsoft Entra ID` (formally *Azure Active Directory*)." -msgstr "" - -#: ../../content/administration/maintain/azure_oauth.rst:30 -msgid "Now, click on :guilabel:`Add (+)`, located in the top menu, and then select :guilabel:`App registration`. On the :guilabel:`Register an application` screen, rename the :guilabel:`Name` to `Odoo` or something recognizable. Under the :guilabel:`Supported account types` section select :guilabel:`Accounts in any organizational directory (Any Microsoft Entra ID directory - Multitenant) and personal Microsoft accounts (e.g. Skype, Xbox)`." -msgstr "" - -#: ../../content/administration/maintain/azure_oauth.rst:36 -msgid "Under the :guilabel:`Redirect URL` section, select :guilabel:`Web` as the platform, and then input `https:///microsoft_outlook/confirm` in the :guilabel:`URL` field. The Odoo base URL is the canonical domain at which your Odoo instance can be reached in the URL field." -msgstr "" - -#: ../../content/administration/maintain/azure_oauth.rst:41 -msgid "*mydatabase.odoo.com*, where *mydatabase* is the actual prefix of the database's subdomain, assuming it's hosted on Odoo.com" -msgstr "" - -#: ../../content/administration/maintain/azure_oauth.rst:44 -msgid "After the URL has been added to the field, :guilabel:`Register` the application so it is created." -msgstr "" - -#: ../../content/administration/maintain/azure_oauth.rst:47 -msgid "API permissions" -msgstr "" - -#: ../../content/administration/maintain/azure_oauth.rst:49 -msgid "The :guilabel:`API permissions` should be set next. Odoo will need specific API permissions to be able to read (IMAP) and send (SMTP) emails in the Microsoft 365 setup. First, click the :guilabel:`API permissions` link, located in the left menu bar. Next, click on the :guilabel:`(+) Add a Permission` button and select :guilabel:`Microsoft Graph` under :guilabel:`Commonly Used Microsoft APIs`. After, select the :guilabel:`Delegated Permissions` option." -msgstr "" - -#: ../../content/administration/maintain/azure_oauth.rst:55 -msgid "In the search bar, search for the following :guilabel:`Delegated permissions` and click :guilabel:`Add permissions` for each one:" -msgstr "" - -#: ../../content/administration/maintain/azure_oauth.rst:58 -msgid ":guilabel:`SMTP.Send`" -msgstr "" - -#: ../../content/administration/maintain/azure_oauth.rst:59 -msgid ":guilabel:`IMAP.AccessAsUser.All`" -msgstr "" - -#: ../../content/administration/maintain/azure_oauth.rst:62 -msgid "The :guilabel:`User.Read` permission will be added by default." -msgstr "" - -#: ../../content/administration/maintain/azure_oauth.rst:-1 -msgid "API permissions needed for Odoo integration are listed under the Microsoft Graph." -msgstr "" - -#: ../../content/administration/maintain/azure_oauth.rst:69 -msgid "Assign users and groups" -msgstr "" - -#: ../../content/administration/maintain/azure_oauth.rst:71 -msgid "After adding the API permissions, navigate back to the :guilabel:`Overview` of the :guilabel:`Application` in the top of the left sidebar menu." -msgstr "" - -#: ../../content/administration/maintain/azure_oauth.rst:74 -msgid "Now, add users to this application. Under the :guilabel:`Essentials` overview table, click on the link labeled :guilabel:`Managed Application in Local Directory`, or the last option on the bottom right-hand side of the table." -msgstr "" - -#: ../../content/administration/maintain/azure_oauth.rst:-1 -msgid "Add users/groups by clicking the Managed application in local directory link for the\n" -"created application." -msgstr "" - -#: ../../content/administration/maintain/azure_oauth.rst:83 -msgid "In the left sidebar menu, select :guilabel:`Users and Groups`. Next, click on :guilabel:`(+) Add User/Group`. Depending on the account, either a :guilabel:`Group` and a :guilabel:`User` can be added, or only :guilabel:`Users`. Personal accounts will only allow for :guilabel:`Users` to be added." -msgstr "" - -#: ../../content/administration/maintain/azure_oauth.rst:88 -msgid "Under :guilabel:`Users` or :guilabel:`Groups`, click on :guilabel:`None Selected` and add the users or group of users that will be sending emails from the :guilabel:`Microsoft account` in Odoo. :guilabel:`Add` the users/groups, click :guilabel:`Select`, and then :guilabel:`Assign` them to the application." -msgstr "" - -#: ../../content/administration/maintain/azure_oauth.rst:94 -msgid "Create credentials" -msgstr "" - -#: ../../content/administration/maintain/azure_oauth.rst:96 -msgid "Now that the Microsoft Azure app is set up, credentials need to be created for the Odoo setup. These include the :guilabel:`Client ID` and :guilabel:`Client Secret`. To start, the :guilabel:`Client ID` can be copied from the :guilabel:`Overview` page of the app. The :guilabel:`Client ID` or :guilabel:`Application ID` is located under the :guilabel:`Display Name` in the :guilabel:`Essentials` overview of the app." -msgstr "" - -#: ../../content/administration/maintain/azure_oauth.rst:-1 -msgid "Application/Client ID located in the Overview of the app." -msgstr "" - -#: ../../content/administration/maintain/azure_oauth.rst:106 -msgid "Next, the :guilabel:`Client Secret Value` needs to be retrieved. To get this value, click on :guilabel:`Certificates & Secrets` in the left sidebar menu. Then, a :guilabel:`Client Secret` needs to be produced. In order to do this, click on the :guilabel:`(+) New Client Secret` button." -msgstr "" - -#: ../../content/administration/maintain/azure_oauth.rst:110 -msgid "A window on the right will populate with a button labeled :guilabel:`Add a client secret`. Under :guilabel:`Description`, type in `Odoo Fetchmail` or something recognizable, and then set the :guilabel:`expiration date`." -msgstr "" - -#: ../../content/administration/maintain/azure_oauth.rst:115 -msgid "A new :guilabel:`Client Secret` will need to be produced and configured if the first one expires. In this event, there could be an interruption of service, so the expiration date should be noted and set to the furthest possible date." -msgstr "" - -#: ../../content/administration/maintain/azure_oauth.rst:119 -msgid "Next, click on :guilabel:`Add` when these two values are entered. A :guilabel:`Client Secret Value` and :guilabel:`Secret ID` will be created. It is important to copy the :guilabel:`Value` or :guilabel:`Client Secret Value` into a notepad as it will become encrypted after leaving this page. The :guilabel:`Secret ID` is not needed." -msgstr "" - -#: ../../content/administration/maintain/azure_oauth.rst:-1 -msgid "Client Secret Value or Value in the app's credentials." -msgstr "" - -#: ../../content/administration/maintain/azure_oauth.rst:128 -msgid "After these steps, the following items should be ready to be set up in Odoo:" -msgstr "" - -#: ../../content/administration/maintain/azure_oauth.rst:130 -msgid "A client ID (:guilabel:`Client ID` or :guilabel:`Application ID`)" -msgstr "" - -#: ../../content/administration/maintain/azure_oauth.rst:131 -msgid "A client secret (:guilabel:`Value` or :guilabel:`Client Secret Value`)" -msgstr "" - -#: ../../content/administration/maintain/azure_oauth.rst:133 -msgid "This completes the setup on the :guilabel:`Microsoft Azure Portal` side." -msgstr "" - -#: ../../content/administration/maintain/azure_oauth.rst:136 -#: ../../content/administration/maintain/google_oauth.rst:111 -msgid "Setup in Odoo" -msgstr "" - -#: ../../content/administration/maintain/azure_oauth.rst:139 -msgid "Enter Microsoft Outlook credentials" -msgstr "" - -#: ../../content/administration/maintain/azure_oauth.rst:141 -msgid "First, open the Odoo database and navigate to the :guilabel:`Apps` module. Then, remove the :guilabel:`Apps` filter from the search bar and type in `Outlook`. After that, install the module called :guilabel:`Microsoft Outlook`." -msgstr "" - -#: ../../content/administration/maintain/azure_oauth.rst:145 -msgid "Next, navigate to :menuselection:`Settings --> General Settings`, and under the :guilabel:`Discuss` section, ensure that the checkbox for :guilabel:`Custom Email Servers` is checked. This populates a new option for :guilabel:`Outlook Credentials`." -msgstr "" - -#: ../../content/administration/maintain/azure_oauth.rst:149 -msgid ":guilabel:`Save` the progress." -msgstr "" - -#: ../../content/administration/maintain/azure_oauth.rst:151 -msgid "Then, copy and paste the :guilabel:`Client ID` (Application ID) and :guilabel:`Client Secret (Client Secret Value)` into the respective fields and :guilabel:`Save` the settings." -msgstr "" - -#: ../../content/administration/maintain/azure_oauth.rst:-1 -msgid "Outlook Credentials in Odoo General Settings." -msgstr "" - -#: ../../content/administration/maintain/azure_oauth.rst:159 -#: ../../content/administration/maintain/google_oauth.rst:127 -msgid "Configure outgoing email server" -msgstr "" - -#: ../../content/administration/maintain/azure_oauth.rst:161 -msgid "On the :guilabel:`General Settings` page, under the :guilabel:`Custom Email Servers` setting, click the :guilabel:`Outgoing Email Servers` link to configure the Microsoft account." -msgstr "" - -#: ../../content/administration/maintain/azure_oauth.rst:164 -msgid "Then, create a new email server and check the box for :guilabel:`Outlook`. Next, fill in the :guilabel:`Name` (it can be anything) and the Microsoft Outlook email :guilabel:`Username`." -msgstr "" - -#: ../../content/administration/maintain/azure_oauth.rst:167 -msgid "If the :guilabel:`From Filter` field is empty, enter either a :ref:`domain or email address `." -msgstr "" - -#: ../../content/administration/maintain/azure_oauth.rst:170 -msgid "Then, click on :guilabel:`Connect your Outlook account`." -msgstr "" - -#: ../../content/administration/maintain/azure_oauth.rst:172 -msgid "A new window from Microsoft opens to complete the :guilabel:`authorization process`. Select the appropriate email address that is being configured in Odoo." -msgstr "" - -#: ../../content/administration/maintain/azure_oauth.rst:-1 -msgid "Permission page to grant access between newly created app and Odoo." -msgstr "" - -#: ../../content/administration/maintain/azure_oauth.rst:179 -msgid "Then, allow Odoo to access the Microsoft account by clicking on :guilabel:`Yes`. After this, the page will navigate back to the newly configured :guilabel:`Outgoing Mail Server` in Odoo. The configuration automatically loads the :guilabel:`token` in Odoo, and a tag stating :guilabel:`Outlook Token Valid` appears in green." -msgstr "" - -#: ../../content/administration/maintain/azure_oauth.rst:-1 -msgid "Valid Outlook Token indicator." -msgstr "" - -#: ../../content/administration/maintain/azure_oauth.rst:188 -msgid "Finally, click :guilabel:`Test Connection`. A confirmation message should appear. The Odoo database can now send safe, secure emails through Microsoft Outlook using OAuth authentication." -msgstr "" - -#: ../../content/administration/maintain/azure_oauth.rst:194 -msgid "Configuration with a single outgoing mail server" -msgstr "" - -#: ../../content/administration/maintain/azure_oauth.rst:196 -msgid "Configuring a single outgoing server is the simplest configuration available for Microsoft Azure and it doesn't require extensive access rights for the users in the database." -msgstr "" - -#: ../../content/administration/maintain/azure_oauth.rst:199 -msgid "A generic email address would be used to send emails for all users within the database. For example it could be structured with a `notifications` alias (`notifications@example.com`) or `contact` alias (`contact@example.com`). This address must be set as the :guilabel:`FROM Filtering` on the server. This address must also match the `{mail.default.from}@{mail.catchall.domain}` key combination in the system parameters." -msgstr "" - -#: ../../content/administration/maintain/azure_oauth.rst:206 -#: ../../content/administration/maintain/azure_oauth.rst:247 -msgid "For more information on the from filter visit: :ref:`email_communication/default`." -msgstr "" - -#: ../../content/administration/maintain/azure_oauth.rst:209 -#: ../../content/administration/maintain/azure_oauth.rst:254 -msgid "The :guilabel:`System Parameters` can be accessed by activating :ref:`developer-mode` in the :menuselection:`Settings --> Technical --> Parameters --> System Parameters` menu." -msgstr "" - -#: ../../content/administration/maintain/azure_oauth.rst:212 -msgid "When using this configuration, every email that is sent from the database will use the address of the configured `notification` mailbox. However it should be noted that the name of the sender will appear but their email address will change:" -msgstr "" - -#: ../../content/administration/maintain/azure_oauth.rst:-1 -msgid "Name from real sender with static email." -msgstr "" - -#: ../../content/administration/maintain/azure_oauth.rst:221 -msgid "Single outgoing mail server configuration:" -msgstr "" - -#: ../../content/administration/maintain/azure_oauth.rst:223 -msgid "Outgoing mail server **username** (login) = `notifications@example.com`" -msgstr "" - -#: ../../content/administration/maintain/azure_oauth.rst:224 -msgid "Outgoing mail server :guilabel:`FROM Filtering` = `notifications@example.com`" -msgstr "" - -#: ../../content/administration/maintain/azure_oauth.rst:225 -#: ../../content/administration/maintain/azure_oauth.rst:279 -msgid "`mail.catchall.domain` in system parameters = `example.com`" -msgstr "" - -#: ../../content/administration/maintain/azure_oauth.rst:226 -#: ../../content/administration/maintain/azure_oauth.rst:280 -msgid "`mail.default.from` in system parameters = `notifications`" -msgstr "" - -#: ../../content/administration/maintain/azure_oauth.rst:229 -msgid "User-specific (multiple user) configuration" -msgstr "" - -#: ../../content/administration/maintain/azure_oauth.rst:231 -msgid "In addition to a generic email server, individual email servers can be set up for users in a database. These email addresses must be set as the :guilabel:`FROM Filtering` on each individual server for this configuration to work." -msgstr "" - -#: ../../content/administration/maintain/azure_oauth.rst:235 -msgid "This configuration is the more difficult of the two Microsoft Azure configurations, in that it requires all users configured with email servers to have access rights to settings in order to establish a connection to the email server." -msgstr "" - -#: ../../content/administration/maintain/azure_oauth.rst:240 -#: ../../content/administration/odoo_sh/getting_started/branches.rst:480 -msgid "Setup" -msgstr "" - -#: ../../content/administration/maintain/azure_oauth.rst:242 -msgid "Each user should have a separate email server set up. The :guilabel:`FROM Filtering` should be set so that only the user's email is sent from that server. In other words, only a user with an email address that matches the set :guilabel:`FROM Filtering` is able to use this server." -msgstr "" - -#: ../../content/administration/maintain/azure_oauth.rst:249 -msgid "A :ref:`fallback server ` must be setup to allow for the sending of :guilabel:`notifications`. The :guilabel:`FROM Filtering` for this server should have the value of the `{mail.default.from}@{mail.catchall.domain}`." -msgstr "" - -#: ../../content/administration/maintain/azure_oauth.rst:258 -msgid "The configuration for this transactional email server can work alongside an outgoing mass-mailing email server. The :guilabel:`FROM Filtering` for the mass-mailing email server can remain empty, but it's require to be added in the settings of the *Email Marketing* application." -msgstr "" - -#: ../../content/administration/maintain/azure_oauth.rst:263 -msgid "For more information on setting the mass-mailing email server visit :ref:`email_communication/mass_mails`." -msgstr "" - -#: ../../content/administration/maintain/azure_oauth.rst:267 -msgid "Multiple user outgoing mail server configuration:" -msgstr "" - -#: ../../content/administration/maintain/azure_oauth.rst:270 -msgid "User #1 mailbox" -msgstr "" - -#: ../../content/administration/maintain/azure_oauth.rst:270 -msgid "Outgoing mail server #1 **username** (login) = `john@example.com`" -msgstr "" - -#: ../../content/administration/maintain/azure_oauth.rst:271 -msgid "Outgoing mail server #1 :guilabel:`FROM Filtering` = `john@example.com`" -msgstr "" - -#: ../../content/administration/maintain/azure_oauth.rst:273 -msgid "User #2 mailbox" -msgstr "" - -#: ../../content/administration/maintain/azure_oauth.rst:273 -msgid "Outgoing mail server #2 **username** (login) = `jane@example.com`" -msgstr "" - -#: ../../content/administration/maintain/azure_oauth.rst:274 -msgid "Outgoing mail server #2 :guilabel:`FROM Filtering` = `jane@example.com`" -msgstr "" - -#: ../../content/administration/maintain/azure_oauth.rst:276 -msgid "Notifications mailbox" -msgstr "" - -#: ../../content/administration/maintain/azure_oauth.rst:276 -msgid "Outgoing mail server #3 **username** (login) = `notifications@example.com`" -msgstr "" - -#: ../../content/administration/maintain/azure_oauth.rst:277 -msgid "Outgoing mail server #3 :guilabel:`FROM Filtering` = `notifications@example.com`" -msgstr "" - -#: ../../content/administration/maintain/azure_oauth.rst:279 -msgid "System Parameters" -msgstr "" - -#: ../../content/administration/maintain/azure_oauth.rst:283 -msgid "Configure incoming email server" -msgstr "" - -#: ../../content/administration/maintain/azure_oauth.rst:285 -msgid "The incoming account should be configured in a similar way to the outgoing email account. Navigate to the :guilabel:`Incoming Mail Servers` in the :guilabel:`Technical Menu` and :guilabel:`Create` a new configuration. Check or Select the button next to :guilabel:`Outlook Oauth Authentication` and enter the :guilabel:`Microsoft Outlook username`. Click on :guilabel:`Connect your Outlook account`. Odoo will state: :guilabel:`Outlook Token Valid` Now :guilabel:`Test and Confirm` the account. The account should be ready to receive email to the Odoo database." -msgstr "" - -#: ../../content/administration/maintain/azure_oauth.rst:293 -msgid ":doc:`../../applications/general/email_communication/email_servers`" -msgstr "" - -#: ../../content/administration/maintain/domain_names.rst:3 -#: ../../content/administration/maintain/odoo_online.rst:70 -msgid "Domain names" -msgstr "" - -#: ../../content/administration/maintain/domain_names.rst:5 -msgid "Domain names are text-based addresses identifying online locations, such as websites. They provide a more memorable and recognizable way for people to navigate the internet than numerical IP addresses." -msgstr "" - -#: ../../content/administration/maintain/domain_names.rst:8 -msgid "**Odoo Online** and **Odoo.sh** databases use a **subdomain** of the `odoo.com` **domain** by default (e.g., `mycompany.odoo.com`)." -msgstr "" - -#: ../../content/administration/maintain/domain_names.rst:11 -msgid "However, you can use a custom domain name instead by :ref:`registering a free domain name ` (only available for Odoo Online databases) or by :ref:`configuring a domain name you already own `." -msgstr "" - -#: ../../content/administration/maintain/domain_names.rst:16 -msgid "`Odoo Tutorials: Register a free domain name [video] `_" -msgstr "" - -#: ../../content/administration/maintain/domain_names.rst:22 -msgid "Register a free domain name with Odoo" -msgstr "" - -#: ../../content/administration/maintain/domain_names.rst:24 -msgid "To register a one-year free domain name for your Odoo Online database, sign in to your account and go to the `database manager `_. Click the gear icon (:guilabel:`⚙️`) next to the database name and select :guilabel:`Domain Names`." -msgstr "" - -#: ../../content/administration/maintain/domain_names.rst:-1 -msgid "Accessing a database's domain names configuration" -msgstr "" - -#: ../../content/administration/maintain/domain_names.rst:31 -msgid "Search for the desired domain name and check its availability." -msgstr "" - -#: ../../content/administration/maintain/domain_names.rst:-1 -msgid "Searching for an available domain name" -msgstr "" - -#: ../../content/administration/maintain/domain_names.rst:37 -msgid "Ensure the Website app is installed if the domain name registration option does not appear." -msgstr "" - -#: ../../content/administration/maintain/domain_names.rst:39 -msgid "Select the desired domain name, fill in the :guilabel:`Domain Owner` form, and click :guilabel:`Register`. The chosen domain name is directly linked to the database, but you still need to :ref:`map your domain name to your Odoo website `." -msgstr "" - -#: ../../content/administration/maintain/domain_names.rst:-1 -msgid "Filling in the domain owner information" -msgstr "" - -#: ../../content/administration/maintain/domain_names.rst:47 -msgid "A verification email from `noreply@domainnameverification.net` will be sent to the email address provided in the :guilabel:`Domain Owner` form. It is essential to verify your email address to keep the domain active and receive the renewal quote before expiration." -msgstr "" - -#: ../../content/administration/maintain/domain_names.rst:51 -msgid "The domain name registration is free for the first year. After this period, Odoo will continue to manage the domain in partnership with **Gandi.net**, the domain name registrar, and you will be charged `Gandi.net's renewal rate `_. Odoo sends a renewal quotation every year to the email address mentioned in the :guilabel:`Domain Owner` form several weeks before the expiration date of the domain. The domain is renewed automatically when the quotation is confirmed." -msgstr "" - -#: ../../content/administration/maintain/domain_names.rst:59 -msgid "The offer is only available for **Odoo Online** databases." -msgstr "" - -#: ../../content/administration/maintain/domain_names.rst:60 -msgid "The offer is limited to **one** domain name per client." -msgstr "" - -#: ../../content/administration/maintain/domain_names.rst:61 -msgid "The offer is limited to the registration of a **new** domain name." -msgstr "" - -#: ../../content/administration/maintain/domain_names.rst:62 -msgid "The offer is available to *One App Free* plans. Ensure that your website contains enough original content for Odoo to verify that your request is legitimate and respects `Odoo's Acceptable Use Policy `_. Given the high number of requests, it can take Odoo several days to review them." -msgstr "" - -#: ../../content/administration/maintain/domain_names.rst:70 -msgid "DNS records" -msgstr "" - -#: ../../content/administration/maintain/domain_names.rst:72 -msgid "To manage your free domain name :abbr:`DNS (domain name system)` records, open the `database manager `_, click the gear icon (:guilabel:`⚙️`) next to the database name, select :guilabel:`Domain Names`, and click :guilabel:`DNS`." -msgstr "" - -#: ../../content/administration/maintain/domain_names.rst:76 -msgid ":guilabel:`A`: the A record holds the IP address of the domain. It is automatically created and **cannot** be edited or deleted." -msgstr "" - -#: ../../content/administration/maintain/domain_names.rst:78 -msgid ":guilabel:`CNAME`: CNAME records forward one domain or subdomain to another domain. One is automatically created to map the `www.` subdomain to the database. If the database is renamed, the CNAME record **must** also be renamed." -msgstr "" - -#: ../../content/administration/maintain/domain_names.rst:81 -msgid ":guilabel:`MX`: MX records instruct servers on where to deliver emails." -msgstr "" - -#: ../../content/administration/maintain/domain_names.rst:82 -msgid ":guilabel:`TXT`: TXT records can be used for different purposes (e.g., to verify domain name ownership)." -msgstr "" - -#: ../../content/administration/maintain/domain_names.rst:85 -msgid "Any modification to the DNS records can take up to **72 hours** to propagate worldwide on all servers." -msgstr "" - -#: ../../content/administration/maintain/domain_names.rst:89 -msgid "`Submit a support ticket `_ if you need assistance to manage your domain name." -msgstr "" - -#: ../../content/administration/maintain/domain_names.rst:93 -msgid "Mailbox" -msgstr "" - -#: ../../content/administration/maintain/domain_names.rst:95 -msgid "The one-year free domain name offer does **not** include a mailbox. There are two options to link your domain name with a mailbox." -msgstr "" - -#: ../../content/administration/maintain/domain_names.rst:99 -msgid "Use a subdomain" -msgstr "" - -#: ../../content/administration/maintain/domain_names.rst:101 -msgid "You can create a subdomain (e.g., `subdomain.yourdomain.com`) to use as an alias domain for the database. It allows users to create records in the database from emails received on their `email@subdomain.yourdomain.com` alias." -msgstr "" - -#: ../../content/administration/maintain/domain_names.rst:105 -msgid "To do so, open the `database manager `_, click the gear icon (:guilabel:`⚙️`) next to the database name, and go to :menuselection:`Domain Names --> DNS --> Add DNS record --> CNAME`. Next, enter the desired subdomain in the :guilabel:`Name` field (e.g., `subdomain`), the original database domain with a period at the end (e.g., `mycompany.odoo.com.`) in the :guilabel:`Content` field, and click :guilabel:`Add record`." -msgstr "" - -#: ../../content/administration/maintain/domain_names.rst:111 -msgid "Then, add the alias domain as your *own domain* by clicking :guilabel:`Use my own domain`, entering the alias domain (e.g., `subdomain.yourdomain.com`), clicking :guilabel:`Verify`, and then :guilabel:`I confirm, it's done`." -msgstr "" - -#: ../../content/administration/maintain/domain_names.rst:115 -msgid "Finally, go to your database and open the :guilabel:`Settings`. Under the :guilabel:`Alias Domain` field, enter the alias domain (e.g., `subdomain.yourdomain.com`), click :guilabel:`Create`, and then :guilabel:`Save`." -msgstr "" - -#: ../../content/administration/maintain/domain_names.rst:120 -msgid "Use an external email provider" -msgstr "" - -#: ../../content/administration/maintain/domain_names.rst:122 -msgid "To use an external email provider, you should configure an MX record. To do so, open the `database manager `_, click the gear icon (:guilabel:`⚙️`) next to the database name, click :menuselection:`Domain Names --> DNS --> Add DNS record --> MX`. The values you should enter for the :guilabel:`Name`, :guilabel:`Content`, and :guilabel:`Priority` fields depend on the external email provider." -msgstr "" - -#: ../../content/administration/maintain/domain_names.rst:129 -msgid "`Google Workspace: MX record values `_" -msgstr "" - -#: ../../content/administration/maintain/domain_names.rst:130 -msgid "`Outlook and Exchange Online: Add an MX record for email `_" -msgstr "" - -#: ../../content/administration/maintain/domain_names.rst:135 -msgid "Configure an existing domain name" -msgstr "" - -#: ../../content/administration/maintain/domain_names.rst:137 -msgid "If you already have a domain name, you can use it for your Odoo website." -msgstr "" - -#: ../../content/administration/maintain/domain_names.rst:140 -msgid "It is strongly recommended to follow **in order** these three steps to avoid any :ref:`SSL certificate validation ` issues:" -msgstr "" - -#: ../../content/administration/maintain/domain_names.rst:143 -msgid ":ref:`Add a CNAME record `" -msgstr "" - -#: ../../content/administration/maintain/domain_names.rst:144 -msgid ":ref:`Map your domain name to your Odoo database `" -msgstr "" - -#: ../../content/administration/maintain/domain_names.rst:145 -msgid ":ref:`Map your domain name to your Odoo website `" -msgstr "" - -#: ../../content/administration/maintain/domain_names.rst:150 -msgid "Add a CNAME record" -msgstr "" - -#: ../../content/administration/maintain/domain_names.rst:152 -msgid "Creating a CNAME record to forward your domain name to the address of your Odoo database is required." -msgstr "" - -#: ../../content/administration/maintain/domain_names.rst:159 -msgid "The CNAME record's target address should be your database's address as defined at its creation (e.g., `mycompany.odoo.com`)." -msgstr "" - -#: ../../content/administration/maintain/domain_names.rst:162 -#: ../../content/administration/maintain/domain_names.rst:221 -#: ../../content/administration/maintain/supported_versions.rst:30 -#: ../../content/administration/odoo_sh.rst:5 -#: ../../content/administration/upgrade.rst:120 -#: ../../content/administration/upgrade.rst:318 -msgid "Odoo.sh" -msgstr "" - -#: ../../content/administration/maintain/domain_names.rst:164 -msgid "The CNAME record's target address can be the project's main address, which can be found on Odoo.sh by going to :menuselection:`Settings --> Project Name`, or a specific branch (production, staging or development) by going to :menuselection:`Branches --> select the branch --> Settings --> Custom domains`, and clicking :guilabel:`How to set up my domain?`. A message indicates which address your CNAME record should target." -msgstr "" - -#: ../../content/administration/maintain/domain_names.rst:170 -msgid "The specific instructions depend on your DNS hosting service." -msgstr "" - -#: ../../content/administration/maintain/domain_names.rst:173 -msgid "`GoDaddy: Add a CNAME record `_" -msgstr "" - -#: ../../content/administration/maintain/domain_names.rst:174 -msgid "`Namecheap: How to create a CNAME record for your domain `_" -msgstr "" - -#: ../../content/administration/maintain/domain_names.rst:175 -msgid "`OVHcloud: Add a new DNS record `_" -msgstr "" - -#: ../../content/administration/maintain/domain_names.rst:176 -msgid "`Cloudflare: Manage DNS records `_" -msgstr "" - -#: ../../content/administration/maintain/domain_names.rst:179 -msgid "Creating a CNAME record to map the `www` subdomain (`www.yourdomain.com`) as some visitors are used to typing `www.` before entering a domain name." -msgstr "" - -#: ../../content/administration/maintain/domain_names.rst:183 -msgid "You own the domain name `yourdomain.com`, and your Odoo Online database's address is `mycompany.odoo.com`. You want to access your Odoo database primarily with the domain `www.yourdomain.com` but also with the naked domain :dfn:`(a domain name without any subdomains or prefixes)` `yourdomain.com`." -msgstr "" - -#: ../../content/administration/maintain/domain_names.rst:188 -msgid "To do so, create a CNAME record for the `www` subdomain, with `mycompany.odoo.com` as the target. Next, create a redirect (301 permanent or visible redirect) to redirect visitors from `yourdomain.com` to `wwww.yourdomain.com`." -msgstr "" - -#: ../../content/administration/maintain/domain_names.rst:195 -msgid "Map a domain name to an Odoo database" -msgstr "" - -#: ../../content/administration/maintain/domain_names.rst:198 -msgid "Ensure you have :ref:`added a CNAME record ` to your domain name's DNS **before** mapping your domain name to your Odoo database." -msgstr "" - -#: ../../content/administration/maintain/domain_names.rst:201 -msgid "Failing to do so may prevent the validation of the :ref:`SSL certificate ` and could result in a *certificate name mismatch* error. Web browsers often display this as a warning, such as *\"Your connection is not private\"*." -msgstr "" - -#: ../../content/administration/maintain/domain_names.rst:205 -msgid "If you encounter this error after mapping the domain name to your database, wait up to five days, as the validation may still happen. If not, you can `submit a support ticket `_, including screenshots of your CNAME records." -msgstr "" - -#: ../../content/administration/maintain/domain_names.rst:213 -msgid "Open the `database manager `_, click the gear icon (:guilabel:`⚙️`) next to the database name, and go to :menuselection:`Domain Names --> Use my own domain`. Then, enter the domain name (e.g., `yourdomain.com`), click :guilabel:`Verify` and :guilabel:`I confirm, it's done`." -msgstr "" - -#: ../../content/administration/maintain/domain_names.rst:0 -msgid "Mapping a domain name to an Odoo Online database" -msgstr "" - -#: ../../content/administration/maintain/domain_names.rst:223 -msgid "On Odoo.sh, go to :menuselection:`Branches --> select your branch --> Settings --> Custom domains`, type the domain name to add, then click :guilabel:`Add domain`." -msgstr "" - -#: ../../content/administration/maintain/domain_names.rst:0 -msgid "Mapping a domain name to an Odoo.sh branch" -msgstr "" - -#: ../../content/administration/maintain/domain_names.rst:230 -msgid ":ref:`Odoo.sh branches: settings tab `" -msgstr "" - -#: ../../content/administration/maintain/domain_names.rst:235 -msgid "SSL encryption (HTTPS protocol)" -msgstr "" - -#: ../../content/administration/maintain/domain_names.rst:237 -msgid "**SSL encryption** allows visitors to navigate a website through a secure connection, which appears as the *https://* protocol at the beginning of a web address rather than the non-secure *http://* protocol." -msgstr "" - -#: ../../content/administration/maintain/domain_names.rst:241 -msgid "Odoo generates a separate SSL certificate for each domain :ref:`mapped to a database ` using `Let's Encrypt's certificate authority and ACME protocol `_." -msgstr "" - -#: ../../content/administration/maintain/domain_names.rst:246 -msgid "Certificate generation may take up to 24 hours." -msgstr "" - -#: ../../content/administration/maintain/domain_names.rst:247 -msgid "Several attempts to validate your certificate are made for five days after you map your domain name to your database." -msgstr "" - -#: ../../content/administration/maintain/domain_names.rst:249 -msgid "If you use another service, you can keep using it or change to Odoo's." -msgstr "" - -#: ../../content/administration/maintain/domain_names.rst:252 -msgid "No SSL certificate is generated for naked domains :dfn:`(domain names without any subdomains or prefixes)`." -msgstr "" - -#: ../../content/administration/maintain/domain_names.rst:258 -msgid "Web base URL of a database" -msgstr "" - -#: ../../content/administration/maintain/domain_names.rst:261 -msgid "If the Website app is installed on your database, skip this section and continue from the :ref:`Map a domain name to a website ` section." -msgstr "" - -#: ../../content/administration/maintain/domain_names.rst:264 -msgid "The *web base URL* or root URL of a database affects your main website address and all the links sent to your customers (e.g., quotations, portal links, etc.)." -msgstr "" - -#: ../../content/administration/maintain/domain_names.rst:267 -msgid "To make your custom domain name the *web base URL* of your database, access your database using your custom domain name and log in as an administrator :dfn:`(a user part of the Settings access right group under Administration)`." -msgstr "" - -#: ../../content/administration/maintain/domain_names.rst:272 -msgid "If you access your database with the original Odoo address (e.g., `mycompany.odoo.com`), the *web base URL* of your database will be updated accordingly. To prevent the automatic update of the *web base URL* when an administrator logs in to the database, activate the :ref:`developer mode `, go to :menuselection:`Settings --> Technical --> System Parameters --> New`, and enter `web.base.url.freeze` as the :guilabel:`Key` and `True` as the :guilabel:`Value`." -msgstr "" - -#: ../../content/administration/maintain/domain_names.rst:279 -msgid "You can also set the web base URL manually. To do so, activate the :ref:`developer mode `, go to :menuselection:`Settings --> Technical --> System Parameters`, and search for the `web.base.url` key (create it if necessary) and enter the full address of your website as the value (e.g., `https://www.yourdomain.com`). The URL must include the protocol `https://` (or `http://`) and *not* end with a slash (`/`)." -msgstr "" - -#: ../../content/administration/maintain/domain_names.rst:288 -msgid "Map a domain name to an Odoo website" -msgstr "" - -#: ../../content/administration/maintain/domain_names.rst:290 -msgid "Mapping your domain name to your website is different than mapping it to your database:" -msgstr "" - -#: ../../content/administration/maintain/domain_names.rst:292 -msgid "It defines your domain name as the main one for your website, helping search engines to index your website correctly." -msgstr "" - -#: ../../content/administration/maintain/domain_names.rst:294 -msgid "It defines your domain name as the base URL for your database, including portal links sent by email to your customers." -msgstr "" - -#: ../../content/administration/maintain/domain_names.rst:296 -msgid "If you have multiple websites, it maps your domain name to the appropriate website." -msgstr "" - -#: ../../content/administration/maintain/domain_names.rst:298 -msgid "Go to :menuselection:`Website --> Configuration --> Settings`. If you have multiple websites, select the one you want to configure. In the :guilabel:`Domain` field, enter the address of your website (e.g., `https://www.yourdomain.com`) and :guilabel:`Save`." -msgstr "" - -#: ../../content/administration/maintain/domain_names.rst:303 -msgid "Mapping your domain name to your Odoo website prevents Google Search from indexing your original database address (e.g., `mycompany.odoo.com`)." -msgstr "" - -#: ../../content/administration/maintain/domain_names.rst:306 -msgid "If both addresses are already indexed, it may take some time before the indexation of the second address is removed from Google Search. You can use the `Google Search Console `_ to fix the issue." -msgstr "" - -#: ../../content/administration/maintain/domain_names.rst:311 -msgid "If you have multiple websites and companies on your database, make sure to select the right :guilabel:`Company` under :menuselection:`Website --> Configuration --> Settings`. Doing so indicates Odoo which URL to use as the :ref:`base URL ` according to the company in use." -msgstr "" - -#: ../../content/administration/maintain/enterprise.rst:6 -msgid "Switch from Community to Enterprise" -msgstr "" - -#: ../../content/administration/maintain/enterprise.rst:8 -msgid "Depending on your current installation, there are multiple ways to upgrade your community version. In any case the basic guidelines are:" -msgstr "" - -#: ../../content/administration/maintain/enterprise.rst:12 -#: ../../content/administration/maintain/enterprise.rst:31 -#: ../../content/administration/maintain/enterprise.rst:63 -#: ../../content/administration/maintain/enterprise.rst:80 -msgid "Backup your community database" -msgstr "" - -#: ../../content/administration/maintain/enterprise.rst:17 -#: ../../content/administration/maintain/enterprise.rst:62 -msgid "Shutdown your server" -msgstr "" - -#: ../../content/administration/maintain/enterprise.rst:19 -msgid "Install the web_enterprise module" -msgstr "" - -#: ../../content/administration/maintain/enterprise.rst:21 -msgid "Restart your server" -msgstr "" - -#: ../../content/administration/maintain/enterprise.rst:23 -msgid "Enter your Odoo Enterprise Subscription code" -msgstr "" - -#: ../../content/administration/maintain/enterprise.rst:29 -msgid "On Linux, using an installer" -msgstr "" - -#: ../../content/administration/maintain/enterprise.rst:33 -msgid "Stop the odoo service" -msgstr "" - -#: ../../content/administration/maintain/enterprise.rst:39 -msgid "Install the enterprise .deb (it should install over the community package)" -msgstr "" - -#: ../../content/administration/maintain/enterprise.rst:45 -msgid "Update your database to the enterprise packages using" -msgstr "" - -#: ../../content/administration/maintain/enterprise.rst:51 -msgid "You should be able to connect to your Odoo Enterprise instance using your usual mean of identification. You can then link your database with your Odoo Enterprise Subscription by entering the code you received by e-mail in the form input" -msgstr "" - -#: ../../content/administration/maintain/enterprise.rst:57 -msgid "On Linux, using the source code" -msgstr "" - -#: ../../content/administration/maintain/enterprise.rst:59 -msgid "There are many ways to launch your server when using sources, and you probably have your own favourite. You may need to adapt sections to your usual workflow." -msgstr "" - -#: ../../content/administration/maintain/enterprise.rst:64 -msgid "Update the ``--addons-path`` parameter of your launch command (see :doc:`../install/source`)" -msgstr "" - -#: ../../content/administration/maintain/enterprise.rst:65 -msgid "Install the web_enterprise module by using" -msgstr "" - -#: ../../content/administration/maintain/enterprise.rst:71 -msgid "Depending on the size of your database, this may take some time." -msgstr "" - -#: ../../content/administration/maintain/enterprise.rst:73 -msgid "Restart your server with the updated addons path of point 3. You should be able to connect to your instance. You can then link your database with your Odoo Enterprise Subscription by entering the code you received by e-mail in the form input" -msgstr "" - -#: ../../content/administration/maintain/enterprise.rst:78 -msgid "On Windows" -msgstr "" - -#: ../../content/administration/maintain/enterprise.rst:82 -msgid "Uninstall Odoo Community (using the Uninstall executable in the installation folder) - PostgreSQL will remain installed" -msgstr "" - -#: ../../content/administration/maintain/enterprise.rst:88 -msgid "Launch the Odoo Enterprise Installer and follow the steps normally. When choosing the installation path, you can set the folder of the Community installation (this folder still contains the PostgreSQL installation). Uncheck ``Start Odoo`` at the end of the installation" -msgstr "" - -#: ../../content/administration/maintain/enterprise.rst:96 -msgid "Using a command window, update your Odoo Database using this command (from the Odoo installation path, in the server subfolder)" -msgstr "" - -#: ../../content/administration/maintain/enterprise.rst:103 -msgid "No need to manually launch the server, the service is running. You should be able to connect to your Odoo Enterprise instance using your usual mean of identification. You can then link your database with your Odoo Enterprise Subscription by entering the code you received by e-mail in the form input" -msgstr "" - -#: ../../content/administration/maintain/google_oauth.rst:3 -msgid "Connect Gmail to Odoo using Google OAuth" -msgstr "" - -#: ../../content/administration/maintain/google_oauth.rst:5 -msgid "Odoo is compatible with Google's OAuth for Gmail. In order to send secure emails from a custom domain, all that is required is to configure a few settings on Google's *Workspace* platform, as well as on the back end of the Odoo database. This configuration works by using either a personal email address or an address created by a custom domain." -msgstr "" - -#: ../../content/administration/maintain/google_oauth.rst:11 -msgid "For more information, visit `Google's documentation `_ on setting up OAuth." -msgstr "" - -#: ../../content/administration/maintain/google_oauth.rst:15 -msgid ":doc:`/applications/general/auth/google`" -msgstr "" - -#: ../../content/administration/maintain/google_oauth.rst:16 -msgid ":doc:`/applications/productivity/calendar/google`" -msgstr "" - -#: ../../content/administration/maintain/google_oauth.rst:19 -msgid "Setup in Google" -msgstr "" - -#: ../../content/administration/maintain/google_oauth.rst:22 -msgid "Create a new project" -msgstr "" - -#: ../../content/administration/maintain/google_oauth.rst:24 -msgid "To get started, go to the `Google API Console `_. Log in with your *Google Workspace* account if you have one, otherwise log in with your personal Gmail account (this should match the email address you want to configure in Odoo)." -msgstr "" - -#: ../../content/administration/maintain/google_oauth.rst:28 -msgid "After that, click on :guilabel:`Create Project`, located on the far right of the :guilabel:`OAuth consent screen`. If a project has already been created in this account, then the :guilabel:`New Project` option will be located on the top right under the :guilabel:`Select a project` drop-down menu." -msgstr "" - -#: ../../content/administration/maintain/google_oauth.rst:33 -msgid "On the :menuselection:`New Project` screen, rename the :guilabel:`Project name` to `Odoo` and browse for the :guilabel:`Location`. Set the :guilabel:`Location` as the *Google Workspace organization*. If you are using a personal Gmail account, then leave the :guilabel:`Location` as :guilabel:`No Organization`." -msgstr "" - -#: ../../content/administration/maintain/google_oauth.rst:-1 -msgid "Project Name and Location for Google OAuth." -msgstr "" - -#: ../../content/administration/maintain/google_oauth.rst:42 -msgid "Click on :guilabel:`Create` to finish this step." -msgstr "" - -#: ../../content/administration/maintain/google_oauth.rst:45 -msgid "OAuth consent screen" -msgstr "" - -#: ../../content/administration/maintain/google_oauth.rst:47 -msgid "If the page doesn't redirect to the :menuselection:`User Type` options, click on :guilabel:`OAuth consent screen` in the left menu." -msgstr "" - -#: ../../content/administration/maintain/google_oauth.rst:50 -msgid "Under :guilabel:`User Type` options, select the appropriate :guilabel:`User Type`, and then click on :guilabel:`Create` again, which will finally navigate to the :menuselection:`Edit app registration` page." -msgstr "" - -#: ../../content/administration/maintain/google_oauth.rst:55 -msgid "*Personal* Gmail Accounts are only allowed to be **External** User Type, which means Google may require an approval, or for *Scopes* to be added on. However, using a *Google WorkSpace* account allows for **Internal** User Type to be used." -msgstr "" - -#: ../../content/administration/maintain/google_oauth.rst:59 -msgid "Note, as well, that while the API connection is in the *External* testing mode, then no approval is necessary from Google. User limits in this testing mode is set to 100 users." -msgstr "" - -#: ../../content/administration/maintain/google_oauth.rst:63 -msgid "Edit app registration" -msgstr "" - -#: ../../content/administration/maintain/google_oauth.rst:65 -msgid "Next we will configure the app registration of the project." -msgstr "" - -#: ../../content/administration/maintain/google_oauth.rst:67 -msgid "On the :guilabel:`OAuth consent screen` step, under the :guilabel:`App information` section, enter `Odoo` in the :guilabel:`App name` field. Select the organization's email address under the :guilabel:`User support` email field." -msgstr "" - -#: ../../content/administration/maintain/google_oauth.rst:71 -msgid "Next, under :menuselection:`App Domain --> Authorized domains`, click on :guilabel:`Add Domain` and enter `odoo.com`." -msgstr "" - -#: ../../content/administration/maintain/google_oauth.rst:74 -msgid "After that, under the :guilabel:`Developer contact information` section, enter the organization's email address. Google uses this email address to notify the organization about any changes to your project." -msgstr "" - -#: ../../content/administration/maintain/google_oauth.rst:78 -msgid "Next, click on the :guilabel:`Save and Continue` button. Then, skip the :menuselection:`Scopes` page by scrolling to the bottom and clicking on :guilabel:`Save and Continue`." -msgstr "" - -#: ../../content/administration/maintain/google_oauth.rst:81 -msgid "If continuing in testing mode (External), add the email addresses being configured under the :guilabel:`Test users` step, by clicking on :guilabel:`Add Users`, and then the :guilabel:`Save and Continue` button. A summary of the app registration appears." -msgstr "" - -#: ../../content/administration/maintain/google_oauth.rst:85 -msgid "Finally, scroll to the bottom and click on :guilabel:`Back to Dashboard` to finish setting up the project." -msgstr "" - -#: ../../content/administration/maintain/google_oauth.rst:89 -msgid "Create Credentials" -msgstr "" - -#: ../../content/administration/maintain/google_oauth.rst:91 -msgid "Now that the project is set up, credentials should be created, which includes the *Client ID* and *Client Secret*. First, click on :guilabel:`Credentials` in the left sidebar menu." -msgstr "" - -#: ../../content/administration/maintain/google_oauth.rst:94 -msgid "Then, click on :guilabel:`Create Credentials` in the top menu and select :guilabel:`OAuth client ID` from the dropdown menu." -msgstr "" - -#: ../../content/administration/maintain/google_oauth.rst:97 -msgid "Under :guilabel:`Application Type`, select :guilabel:`Web Application` from the dropdown menu." -msgstr "" - -#: ../../content/administration/maintain/google_oauth.rst:98 -msgid "In the :guilabel:`Name` field, enter `Odoo`." -msgstr "" - -#: ../../content/administration/maintain/google_oauth.rst:99 -msgid "Under the :guilabel:`Authorized redirect URIs` label, click the button :guilabel:`ADD URI`, and then input `https://yourdbname.odoo.com/google_gmail/confirm` in the :guilabel:`URIs 1` field. Be sure to replace the *yourdbname* part of the URL with the actual Odoo database name." -msgstr "" - -#: ../../content/administration/maintain/google_oauth.rst:102 -msgid "Next, click on :guilabel:`Create` to generate an OAuth :guilabel:`Client ID` and :guilabel:`Client Secret`. Finally, copy each generated value for later use when configuring in Odoo, and then navigate to the Odoo database." -msgstr "" - -#: ../../content/administration/maintain/google_oauth.rst:-1 -msgid "Client ID and Client Secret for Google OAuth." -msgstr "" - -#: ../../content/administration/maintain/google_oauth.rst:114 -msgid "Enter Google Credentials" -msgstr "" - -#: ../../content/administration/maintain/google_oauth.rst:116 -msgid "First, open Odoo and navigate to the :guilabel:`Apps` module. Then, remove the :guilabel:`Apps` filter from the search bar and type in `Google`. Install the module called :guilabel:`Google Gmail`." -msgstr "" - -#: ../../content/administration/maintain/google_oauth.rst:120 -msgid "Next, navigate to :menuselection:`Settings --> General Settings`, and under the :guilabel:`Discuss` section, ensure that the checkbox for :guilabel:`Custom Email Servers` or :guilabel:`External Email Servers` is checked. This populates a new option for :guilabel:`Gmail Credentials` or :guilabel:`Use a Gmail Sever`. Then, copy and paste the respective values into the :guilabel:`Client ID` and :guilabel:`Client Secret` fields and :guilabel:`Save` the settings." -msgstr "" - -#: ../../content/administration/maintain/google_oauth.rst:129 -msgid "To configure the external Gmail account, return to the top of the :guilabel:`Custom Email Servers` setting and then click the :guilabel:`Outgoing Email Servers` link." -msgstr "" - -#: ../../content/administration/maintain/google_oauth.rst:-1 -msgid "Configure Outgoing Email Servers in Odoo." -msgstr "" - -#: ../../content/administration/maintain/google_oauth.rst:136 -msgid "Then, click on :guilabel:`New` or :guilabel:`Create` to create a new email server, and fill in the :guilabel:`Name`, :guilabel:`Description`, and the email :guilabel:`Username` (if required)." -msgstr "" - -#: ../../content/administration/maintain/google_oauth.rst:139 -msgid "Next, click on :guilabel:`Gmail OAuth Authentication` or :guilabel:`Gmail` (under the :guilabel:`Authenticate with` or :guilabel:`Connection` section). Finally, click on :guilabel:`Connect your Gmail Account`." -msgstr "" - -#: ../../content/administration/maintain/google_oauth.rst:143 -msgid "A new window labeled :guilabel:`Google` opens to complete the authorization process. Select the appropriate email address that is being configured in Odoo." -msgstr "" - -#: ../../content/administration/maintain/google_oauth.rst:146 -msgid "If the email address is a personal account, then an extra step pops up, so click :guilabel:`Continue` to allow the verification and connect the Gmail account to Odoo." -msgstr "" - -#: ../../content/administration/maintain/google_oauth.rst:149 -msgid "Then, allow Odoo to access the Google account by clicking on :guilabel:`Continue` or :guilabel:`Allow`. After that, the page navigates back to the newly configured outgoing email server in Odoo. The configuration automatically loads the token in Odoo, and a tag stating :guilabel:`Gmail Token Valid` appears in green." -msgstr "" - -#: ../../content/administration/maintain/google_oauth.rst:158 -msgid "Finally, :guilabel:`Test the Connection`. A confirmation message should appear. The Odoo database can now send safe, secure emails through Google using OAuth authentication." -msgstr "" - -#: ../../content/administration/maintain/google_oauth.rst:162 -msgid "Google OAuth FAQ" -msgstr "" - -#: ../../content/administration/maintain/google_oauth.rst:165 -msgid "Production VS Testing Publishing Status" -msgstr "" - -#: ../../content/administration/maintain/google_oauth.rst:167 -msgid "Choosing :guilabel:`Production` as the :guilabel:`Publishing Status` (instead of :guilabel:`Testing`) will display the following warning message:" -msgstr "" - -#: ../../content/administration/maintain/google_oauth.rst:-1 -msgid "OAuth is Limited to 100 Sensitive Scope Logins." -msgstr "" - -#: ../../content/administration/maintain/google_oauth.rst:174 -msgid "To correct this warning, navigate to the `Google API Platform `_. If the :guilabel:`Publishing status` is :guilabel:`In Production`, click :guilabel:`Back to Testing` to correct the issue." -msgstr "" - -#: ../../content/administration/maintain/google_oauth.rst:179 -msgid "No Test Users Added" -msgstr "" - -#: ../../content/administration/maintain/google_oauth.rst:181 -msgid "If no test users are added to the OAuth consent screen, then a 403 access denied error will populate." -msgstr "" - -#: ../../content/administration/maintain/google_oauth.rst:-1 -msgid "403 Access Denied Error." -msgstr "" - -#: ../../content/administration/maintain/google_oauth.rst:188 -msgid "To correct this error, return to the :guilabel:`OAuth consent screen` under :guilabel:`APIs & Services` and add test user(s) to the app. Add the email that you are configuring in Odoo." -msgstr "" - -#: ../../content/administration/maintain/google_oauth.rst:192 -msgid "Gmail Module not updated" -msgstr "" - -#: ../../content/administration/maintain/google_oauth.rst:194 -msgid "If the *Google Gmail* module in Odoo has not been updated to the latest version, then a :guilabel:`Forbidden` error message populates." -msgstr "" - -#: ../../content/administration/maintain/google_oauth.rst:-1 -msgid "Forbidden you don't have the permission to access the requested resource." -msgstr "" - -#: ../../content/administration/maintain/google_oauth.rst:201 -msgid "To correct this error, go to the :menuselection:`Apps` module and clear out the search terms. Then, search for `Gmail` or `Google` and upgrade the :guilabel:`Google Gmail` module. Finally, click on the three dots on the upper right of the module and select :guilabel:`Upgrade`." -msgstr "" - -#: ../../content/administration/maintain/google_oauth.rst:206 -msgid "Application Type" -msgstr "" - -#: ../../content/administration/maintain/google_oauth.rst:208 -msgid "When creating the credentials (OAuth *Client ID* and *Client Secret*), if :guilabel:`Desktop App` is selected for the :guilabel:`Application Type`, an :guilabel:`Authorization Error` appears." -msgstr "" - -#: ../../content/administration/maintain/google_oauth.rst:-1 -msgid "Error 400 Redirect URI Mismatch." -msgstr "" - -#: ../../content/administration/maintain/google_oauth.rst:215 -msgid "To correct this error, delete the credentials already created and create new credentials, selecting :guilabel:`Web Application` for the :guilabel:`Application Type`. Then, under :guilabel:`Authorized redirect URIs`, click :guilabel:`ADD URI` and type: `https://yourdbname.odoo.com/google_gmail/confirm` in the field, being sure to replace *yourdbname* in the URL with the Odoo database name." -msgstr "" - -#: ../../content/administration/maintain/hosting_changes.rst:3 -msgid "Change hosting solution" -msgstr "" - -#: ../../content/administration/maintain/hosting_changes.rst:5 -msgid "The instructions to change the hosting type of a database depend on the current solution used and to which solution the database should be moved." -msgstr "" - -#: ../../content/administration/maintain/hosting_changes.rst:9 -msgid "Transferring an on-premise database" -msgstr "" - -#: ../../content/administration/maintain/hosting_changes.rst:12 -#: ../../content/administration/maintain/hosting_changes.rst:80 -msgid "To Odoo Online" -msgstr "" - -#: ../../content/administration/maintain/hosting_changes.rst:15 -#: ../../content/administration/maintain/hosting_changes.rst:83 -msgid "Odoo Online is *not* compatible with **non-standard apps**." -msgstr "" - -#: ../../content/administration/maintain/hosting_changes.rst:16 -msgid "The database's current version must be :doc:`supported `." -msgstr "" - -#: ../../content/administration/maintain/hosting_changes.rst:18 -msgid "Create a :ref:`duplicate ` of the database." -msgstr "" - -#: ../../content/administration/maintain/hosting_changes.rst:19 -msgid "In this duplicate, uninstall all **non-standard apps**." -msgstr "" - -#: ../../content/administration/maintain/hosting_changes.rst:20 -msgid "Use the database manager to grab a *dump with filestore*." -msgstr "" - -#: ../../content/administration/maintain/hosting_changes.rst:21 -msgid "`Submit a support ticket `_ including the following:" -msgstr "" - -#: ../../content/administration/maintain/hosting_changes.rst:23 -#: ../../content/administration/maintain/hosting_changes.rst:88 -msgid "your **subscription number**," -msgstr "" - -#: ../../content/administration/maintain/hosting_changes.rst:24 -msgid "the **URL** you want to use for the database (e.g., `company.odoo.com`), and" -msgstr "" - -#: ../../content/administration/maintain/hosting_changes.rst:25 -msgid "the **dump** as an attachment or as a link to the file (required for 60 MB+ files)." -msgstr "" - -#: ../../content/administration/maintain/hosting_changes.rst:27 -#: ../../content/administration/maintain/hosting_changes.rst:95 -msgid "Odoo then makes sure the database is compatible before putting it online. In case of technical issues during the process, Odoo might contact you." -msgstr "" - -#: ../../content/administration/maintain/hosting_changes.rst:31 -#: ../../content/administration/maintain/hosting_changes.rst:99 -msgid "If you have time constraints, `submit a support ticket `_ as soon as possible to schedule the transfer." -msgstr "" - -#: ../../content/administration/maintain/hosting_changes.rst:35 -#: ../../content/administration/maintain/hosting_changes.rst:67 -msgid "To Odoo.sh" -msgstr "" - -#: ../../content/administration/maintain/hosting_changes.rst:37 -#: ../../content/administration/maintain/hosting_changes.rst:73 -msgid "Follow the instructions found in :ref:`the Import your database section ` of the Odoo.sh *Create your project* documentation." -msgstr "" - -#: ../../content/administration/maintain/hosting_changes.rst:41 -msgid "Transferring an Odoo Online database" -msgstr "" - -#: ../../content/administration/maintain/hosting_changes.rst:44 -msgid "Odoo Online's :ref:`intermediary versions ` cannot be hosted on-premise as that type of hosting does not support those versions. Therefore, if the database to transfer is running an intermediary version, it must be upgraded first to the next :ref:`major version `, waiting for its release if necessary." -msgstr "" - -#: ../../content/administration/maintain/hosting_changes.rst:50 -msgid "Transferring an online database running on Odoo 16.3 would require first upgrading it to Odoo 17.0." -msgstr "" - -#: ../../content/administration/maintain/hosting_changes.rst:54 -msgid "Click the gear icon (:guilabel:`⚙`) next to the database name on the `Odoo Online database manager `_ to display its version number." -msgstr "" - -#: ../../content/administration/maintain/hosting_changes.rst:58 -#: ../../content/administration/maintain/hosting_changes.rst:108 -msgid "To on-premise" -msgstr "" - -#: ../../content/administration/maintain/hosting_changes.rst:60 -#: ../../content/administration/maintain/hosting_changes.rst:69 -msgid "Sign in to `the Odoo Online database manager `_ and click the gear icon (:guilabel:`⚙`) next to the database name to :guilabel:`Download` a backup. If the download fails due to the file being too large, `contact Odoo support `_." -msgstr "" - -#: ../../content/administration/maintain/hosting_changes.rst:64 -#: ../../content/administration/maintain/hosting_changes.rst:111 -msgid "Restore the database from the database manager on your local server using the backup." -msgstr "" - -#: ../../content/administration/maintain/hosting_changes.rst:77 -msgid "Transferring an Odoo.sh database" -msgstr "" - -#: ../../content/administration/maintain/hosting_changes.rst:85 -msgid "Uninstall all **non-standard apps** in a staging build before doing it in the production build." -msgstr "" - -#: ../../content/administration/maintain/hosting_changes.rst:86 -msgid "`Create a support ticket `_ including the following:" -msgstr "" - -#: ../../content/administration/maintain/hosting_changes.rst:89 -msgid "the **URL** you want to use for the database (e.g., `company.odoo.com`)," -msgstr "" - -#: ../../content/administration/maintain/hosting_changes.rst:90 -msgid "which **branch** should be migrated," -msgstr "" - -#: ../../content/administration/maintain/hosting_changes.rst:91 -msgid "in which **region** you want the database to be hosted (Americas, Europe, or Asia)," -msgstr "" - -#: ../../content/administration/maintain/hosting_changes.rst:92 -msgid "which user(s) will be the **administrator(s)**, and" -msgstr "" - -#: ../../content/administration/maintain/hosting_changes.rst:93 -msgid "**when** (and in which timezone) you want the database to be up and running." -msgstr "" - -#: ../../content/administration/maintain/hosting_changes.rst:101 -msgid "Select the **region** closest to most of your users to reduce latency." -msgstr "" - -#: ../../content/administration/maintain/hosting_changes.rst:102 -msgid "Future **administrator(s)** must have an Odoo.com account." -msgstr "" - -#: ../../content/administration/maintain/hosting_changes.rst:103 -msgid "The **date and time** you want the database to be up and running are helpful to organize the switch from the Odoo.sh server to the Odoo Online servers." -msgstr "" - -#: ../../content/administration/maintain/hosting_changes.rst:105 -msgid "Databases are **not reachable** during their migration." -msgstr "" - -#: ../../content/administration/maintain/hosting_changes.rst:110 -msgid "Download a :ref:`backup of your Odoo.sh production database `." -msgstr "" - -#: ../../content/administration/maintain/mailjet_api.rst:3 -msgid "Mailjet API" -msgstr "" - -#: ../../content/administration/maintain/mailjet_api.rst:5 -msgid "Odoo is compatible with Mailjet's :abbr:`API (Application Programming Interface)` for mass mailing. Set up a dedicated mass mailing server through Mailjet by configuring settings in the Mailjet account and the Odoo database. In some circumstances, settings need to be configured on the custom domain's :abbr:`DNS (Domain Name System)` settings as well." -msgstr "" - -#: ../../content/administration/maintain/mailjet_api.rst:11 -msgid "Set up in Mailjet" -msgstr "" - -#: ../../content/administration/maintain/mailjet_api.rst:14 -msgid "Create API credentials" -msgstr "" - -#: ../../content/administration/maintain/mailjet_api.rst:16 -msgid "To get started, sign in to the `Mailjet Account Information `_ page. Next, navigate to the :guilabel:`Senders & Domains` section and click on :guilabel:`SMTP and SEND API Settings`." -msgstr "" - -#: ../../content/administration/maintain/mailjet_api.rst:-1 -msgid "SMTP and Send API Settings link in the Senders & Domains section of Mailjet." -msgstr "" - -#: ../../content/administration/maintain/mailjet_api.rst:24 -msgid "Then, copy the :abbr:`SMTP (Simple Mail Transfer Protocol)` configuration settings onto a notepad. They can be found under the :guilabel:`Configuration (SMTP only)` section. The :abbr:`SMTP (Simple Mail Transfer Protocol)` configuration settings include the server address, the security option needed (Use :abbr:`SSL (Secure Sockets Layer)`/:abbr:`TLS (Transport Layer Security)`), and the port number. The settings are needed to configure Mailjet in Odoo, which is covered in the :ref:`last section `." -msgstr "" - -#: ../../content/administration/maintain/mailjet_api.rst:32 -msgid "`Mailjet: How can I configure my SMTP parameters? `_" -msgstr "" - -#: ../../content/administration/maintain/mailjet_api.rst:36 -msgid "Odoo blocks `port 25` on Odoo Online and Odoo.sh databases. :ref:`See reference here `." -msgstr "" - -#: ../../content/administration/maintain/mailjet_api.rst:-1 -msgid "SMTP configuration from Mailjet." -msgstr "" - -#: ../../content/administration/maintain/mailjet_api.rst:43 -msgid "Next, click on the button labeled :guilabel:`Retrieve your API credentials` to retrieve the Mailjet API credentials." -msgstr "" - -#: ../../content/administration/maintain/mailjet_api.rst:46 -msgid "Then, click on the eye icon to reveal the :guilabel:`API key`. Copy this key to a notepad, as this serves as the :guilabel:`Username` in the Odoo configuration. Next, click on the :guilabel:`Generate Secret Key` button to generate the :guilabel:`Secret Key`. Copy this key to a notepad, as this serves as the :guilabel:`Password` in the Odoo configuration." -msgstr "" - -#: ../../content/administration/maintain/mailjet_api.rst:52 -msgid "Add verified sender address(es)" -msgstr "" - -#: ../../content/administration/maintain/mailjet_api.rst:54 -msgid "The next step is to add a sender address or a domain to the Mailjet account settings so that the email address or domain is approved to send emails using Mailjet's servers. First, navigate to the `Mailjet Account Information `_ page. Next, click on the :guilabel:`Add a Sender Domain or Address` link under the :guilabel:`Senders & Domains` section." -msgstr "" - -#: ../../content/administration/maintain/mailjet_api.rst:-1 -msgid "Add a sender domain or address in the Mailjet interface." -msgstr "" - -#: ../../content/administration/maintain/mailjet_api.rst:63 -msgid "Determine if a sender's email address or the entire domain needs to be added to the Mailjet settings. It may be easier to configure the domain as a whole if :abbr:`DNS (Domain Name System)` access is available. Jump to the :ref:`Add a domain ` section for steps on adding the domain." -msgstr "" - -#: ../../content/administration/maintain/mailjet_api.rst:69 -msgid "Either all email addresses of the Odoo database users who are sending emails using Mailjet's servers need to be configured or the domain(s) of the users' email addresses can be configured." -msgstr "" - -#: ../../content/administration/maintain/mailjet_api.rst:72 -msgid "By default, the email address originally set up in the Mailjet account is added as a trusted sender. To add another email address, click on the button labeled :guilabel:`Add a sender address`. Then, add the email address that is configured to send from the custom domain." -msgstr "" - -#: ../../content/administration/maintain/mailjet_api.rst:76 -msgid "At minimum the following email addresses should be set up in the provider and verified in Mailjet:" -msgstr "" - -#: ../../content/administration/maintain/mailjet_api.rst:78 -msgid "notifications\\@yourdomain.com" -msgstr "" - -#: ../../content/administration/maintain/mailjet_api.rst:79 -msgid "bounce\\@yourdomain.com" -msgstr "" - -#: ../../content/administration/maintain/mailjet_api.rst:80 -msgid "catchall\\@yourdomain.com" -msgstr "" - -#: ../../content/administration/maintain/mailjet_api.rst:83 -msgid "Replace `yourdomain` with the custom domain for the Odoo database. If there isn't one, then use the :guilabel:`mail.catchall.domain` system parameter." -msgstr "" - -#: ../../content/administration/maintain/mailjet_api.rst:86 -msgid "After that, fill out the :guilabel:`Email Information` form, making sure to select the appropriate email type: transactional email or mass emails. After completing the form, an activation email is sent to the email address and the trusted sender can be activated." -msgstr "" - -#: ../../content/administration/maintain/mailjet_api.rst:90 -msgid "It is recommended to set up the :abbr:`SPF (Sender Policy Framework)`/:abbr:`DKIM (DomainKeys Identified Mail)`/:abbr:`DMARC (Domain-based Message Authentication, Reporting, and Conformance)` settings on the domain of the sender." -msgstr "" - -#: ../../content/administration/maintain/mailjet_api.rst:95 -#: ../../content/administration/maintain/mailjet_api.rst:162 -msgid "`Mailjet's SPF/DKIM/DMARC documentation `_" -msgstr "" - -#: ../../content/administration/maintain/mailjet_api.rst:99 -msgid "If the database is not using a custom domain, then in order to verify the sender's address, a temporary alias (of the three email addresses mentioned above) should be set up in Odoo CRM to create a lead. Then, the database is able to receive the verification email and verify the accounts." -msgstr "" - -#: ../../content/administration/maintain/mailjet_api.rst:107 -msgid "Add a domain" -msgstr "" - -#: ../../content/administration/maintain/mailjet_api.rst:109 -msgid "By adding an entire domain to the Mailjet account, all the sender addresses related to that domain are automatically validated for sending emails using Mailjet servers. First, navigate to the `Mailjet Account Information `_ page. Next, click on :guilabel:`Add a Sender Domain or Address` link under the :guilabel:`Senders & Domains` section. Then, click on :guilabel:`Add domain` to add the custom domain." -msgstr "" - -#: ../../content/administration/maintain/mailjet_api.rst:116 -msgid "The domain needs to be added to the Mailjet account and then validated through the :abbr:`DNS (Domain Name System)`." -msgstr "" - -#: ../../content/administration/maintain/mailjet_api.rst:119 -msgid "After that, fill out the :guilabel:`Add a new Domain` page on Mailjet and click :guilabel:`Continue`." -msgstr "" - -#: ../../content/administration/maintain/mailjet_api.rst:122 -msgid "After adding the domain, a validation page will populate. Unless the Odoo database is on-premise (in which case, choose :guilabel:`Option 1`), choose :guilabel:`Option 2: Create a DNS Record`. Copy the TXT record information to a notepad and then navigate to the domain's :abbr:`DNS (Domain Name System)` provider to complete validation." -msgstr "" - -#: ../../content/administration/maintain/mailjet_api.rst:-1 -msgid "The TXT record information to input on the domain's DNS." -msgstr "" - -#: ../../content/administration/maintain/mailjet_api.rst:132 -msgid "Setup in the domain's DNS" -msgstr "" - -#: ../../content/administration/maintain/mailjet_api.rst:134 -msgid "After getting the TXT record information from the Mailjet account, add a TXT record to the domain's :abbr:`DNS (Domain Name System)`. This process varies depending on the :abbr:`DNS (Domain Name System)` provider. Consult the provider for specific configuration processes. The TXT record information consists of the :guilabel:`Host` and :guilabel:`Value`. Paste these into the corresponding fields in the TXT record." -msgstr "" - -#: ../../content/administration/maintain/mailjet_api.rst:141 -msgid "Return to Mailjet account information" -msgstr "" - -#: ../../content/administration/maintain/mailjet_api.rst:143 -msgid "After adding the TXT record to the domain's :abbr:`DNS (Domain Name System)`, navigate back to the Mailjet account. Then, navigate to :menuselection:`Account Information --> Add a Sender Domain or Address`, click the gear icon next to :guilabel:`Domain`, and select :guilabel:`Validate`." -msgstr "" - -#: ../../content/administration/maintain/mailjet_api.rst:147 -msgid "This action can also be done by going to the `Sender domains & addresses `_ page on the Mailjet account information and clicking on :guilabel:`Manage`." -msgstr "" - -#: ../../content/administration/maintain/mailjet_api.rst:150 -msgid "Next, click :guilabel:`Check Now` to validate the TXT record that was added on the domain. A success screen will appear if the domain is configured correctly." -msgstr "" - -#: ../../content/administration/maintain/mailjet_api.rst:-1 -msgid "Check DNS record in Mailjet." -msgstr "" - -#: ../../content/administration/maintain/mailjet_api.rst:157 -msgid "After successfully setting up the domain, there is an option to :guilabel:`Authenticate this domain (SPF/DKIM)`. This button populates :abbr:`SPF (Sender Policy Framework)` & :abbr:`DKIM (DomainKeys Identified Mail) records to input into the :abbr:`DNS (Domain Name System)` provider." -msgstr "" - -#: ../../content/administration/maintain/mailjet_api.rst:-1 -msgid "Authenticate the domain with SPF/DKIM records in Mailjet." -msgstr "" - -#: ../../content/administration/maintain/mailjet_api.rst:172 -msgid "Set up in Odoo" -msgstr "" - -#: ../../content/administration/maintain/mailjet_api.rst:174 -msgid "To complete the setup, navigate to the Odoo database and go to the :guilabel:`Settings`. With :ref:`developer-mode` turned on, go to the :menuselection:`Technical Menu --> Email --> Outgoing Mail Servers`. Then, create a new outgoing server configuration by clicking on the :guilabel:`Create` button." -msgstr "" - -#: ../../content/administration/maintain/mailjet_api.rst:179 -msgid "Next, input the `SMTP server` (in-v3.mailjet.com), `port number` (587 or 465), and `Security (SSL/TLS)` that was copied earlier from the Mailjet account. They can also be found `here `_. It is recommended to use :abbr:`SSL (Secure Sockets Layer)`/:abbr:`TLS (Transport Layer Security)` even though Mailjet may not require it." -msgstr "" - -#: ../../content/administration/maintain/mailjet_api.rst:184 -msgid "For the :guilabel:`Username`, input the :guilabel:`API KEY`. For the :guilabel:`Password`, input the :guilabel:`SECRET KEY` that was copied from the Mailjet account to the notepad earlier. These settings can be found on :menuselection:`Mailjet --> Account Settings --> SMTP and SEND API Settings`." -msgstr "" - -#: ../../content/administration/maintain/mailjet_api.rst:189 -msgid "Then, if the Mailjet server is used for mass emailing, set the :guilabel:`Priority` value higher than that of any transactional email server(s). Finally, save the settings and :guilabel:`Test the Connection`." -msgstr "" - -#: ../../content/administration/maintain/mailjet_api.rst:-1 -msgid "Odoo outgoing email server settings." -msgstr "" - -#: ../../content/administration/maintain/mailjet_api.rst:198 -msgid "In order for the notifications feature to work using Mailjet, there are three settings that need to be set in Odoo." -msgstr "" - -#: ../../content/administration/maintain/mailjet_api.rst:201 -msgid "The :guilabel:`From Filter` needs to be set on the server configuration. It is recommended to set it as a domain and not a full email address. It should match the domain in the two proceeding steps. More information can be referenced :ref:`here `." -msgstr "" - -#: ../../content/administration/maintain/mailjet_api.rst:205 -msgid "The :guilabel:`mail.default.from` system parameter must have the value `notifications\\@yourdomain.com`." -msgstr "" - -#: ../../content/administration/maintain/mailjet_api.rst:207 -msgid "The :guilabel:`mail.default.from_filter` system parameter must have the value `yourdomain.com`. Replace `yourdomain` with the custom domain for the Odoo database. If there isn't one, then use the :guilabel:`mail.catchall.domain` system parameter." -msgstr "" - -#: ../../content/administration/maintain/mailjet_api.rst:211 -msgid "For more information see :ref:`Using a default email address `." -msgstr "" - -#: ../../content/administration/maintain/mailjet_api.rst:213 -msgid "The :guilabel:`System Parameters` can be accessed by activating :doc:`../../applications/general/developer_mode` in the :menuselection:`Settings --> Technical --> Parameters --> System Parameters` menu." -msgstr "" - -#: ../../content/administration/maintain/mailjet_api.rst:217 -msgid "Once the setup is complete, the Odoo database is ready to use the Mailjet email server for mass mailing or transactional emails!" -msgstr "" - -#: ../../content/administration/maintain/neutralized_database.rst:3 -msgid "Neutralized database" -msgstr "" - -#: ../../content/administration/maintain/neutralized_database.rst:5 -msgid "A neutralized database is a non-production database on which several parameters are deactivated. This enables one to carry out tests without the risk of launching specific automated processes that could impact production data (e.g., sending emails to customers). Live access is removed and turned into a testing environment." -msgstr "" - -#: ../../content/administration/maintain/neutralized_database.rst:11 -msgid "**Any testing database created is a neutralized database:**" -msgstr "" - -#: ../../content/administration/maintain/neutralized_database.rst:13 -msgid "testing backup databases" -msgstr "" - -#: ../../content/administration/maintain/neutralized_database.rst:14 -msgid "duplicate databases" -msgstr "" - -#: ../../content/administration/maintain/neutralized_database.rst:15 -msgid "for Odoo.sh: staging and development databases" -msgstr "" - -#: ../../content/administration/maintain/neutralized_database.rst:18 -msgid "A database can also be neutralized when upgrading, as it is vital to do some tests before switching to a new version." -msgstr "" - -#: ../../content/administration/maintain/neutralized_database.rst:22 -msgid "Deactivated features" -msgstr "" - -#: ../../content/administration/maintain/neutralized_database.rst:24 -msgid "Here is a non-exhaustive list of the deactivated parameters:" -msgstr "" - -#: ../../content/administration/maintain/neutralized_database.rst:26 -msgid "all planned actions (e.g., automatic invoicing of subscriptions, mass mailing, etc.)" -msgstr "" - -#: ../../content/administration/maintain/neutralized_database.rst:27 -msgid "outgoing emails" -msgstr "" - -#: ../../content/administration/maintain/neutralized_database.rst:28 -msgid "bank synchronization" -msgstr "" - -#: ../../content/administration/maintain/neutralized_database.rst:29 -msgid "payment providers" -msgstr "" - -#: ../../content/administration/maintain/neutralized_database.rst:30 -msgid "delivery methods" -msgstr "" - -#: ../../content/administration/maintain/neutralized_database.rst:31 -msgid ":abbr:`IAP (In-App Purchase)` tokens" -msgstr "" - -#: ../../content/administration/maintain/neutralized_database.rst:34 -msgid "**A red banner at the top of the screen is displayed on the neutralized database so that it can be seen immediately.**" -msgstr "" - -#: ../../content/administration/maintain/odoo_online.rst:3 -msgid "Odoo Online database management" -msgstr "" - -#: ../../content/administration/maintain/odoo_online.rst:5 +#: ../../content/administration/odoo_online.rst:20 msgid "To manage a database, go to the `database manager `_ and sign in as the database administrator." msgstr "" -#: ../../content/administration/maintain/odoo_online.rst:8 +#: ../../content/administration/odoo_online.rst:23 msgid "All the main database management options are available by clicking the database name, except the upgrade option, which can be accessed by clicking the **arrow in a circle** icon next to the database name. It is only displayed if an upgrade is available." msgstr "" -#: ../../content/administration/maintain/odoo_online.rst:-1 +#: ../../content/administration/odoo_online.rst:-1 msgid "Accessing the database management options" msgstr "" -#: ../../content/administration/maintain/odoo_online.rst:15 +#: ../../content/administration/odoo_online.rst:30 msgid ":ref:`odoo_online/upgrade`" msgstr "" -#: ../../content/administration/maintain/odoo_online.rst:16 +#: ../../content/administration/odoo_online.rst:31 msgid ":ref:`odoo_online/duplicate`" msgstr "" -#: ../../content/administration/maintain/odoo_online.rst:17 +#: ../../content/administration/odoo_online.rst:32 msgid ":ref:`odoo_online/rename`" msgstr "" -#: ../../content/administration/maintain/odoo_online.rst:18 +#: ../../content/administration/odoo_online.rst:33 msgid ":ref:`odoo_online/download`" msgstr "" -#: ../../content/administration/maintain/odoo_online.rst:19 +#: ../../content/administration/odoo_online.rst:34 msgid ":ref:`odoo_online/domains`" msgstr "" -#: ../../content/administration/maintain/odoo_online.rst:20 +#: ../../content/administration/odoo_online.rst:35 msgid ":ref:`odoo_online/tags`" msgstr "" -#: ../../content/administration/maintain/odoo_online.rst:21 +#: ../../content/administration/odoo_online.rst:36 msgid ":ref:`odoo_online/delete`" msgstr "" -#: ../../content/administration/maintain/odoo_online.rst:22 +#: ../../content/administration/odoo_online.rst:37 msgid ":ref:`odoo_online/contact-support`" msgstr "" -#: ../../content/administration/maintain/odoo_online.rst:23 +#: ../../content/administration/odoo_online.rst:38 msgid ":ref:`odoo_online/users`" msgstr "" -#: ../../content/administration/maintain/odoo_online.rst:28 +#: ../../content/administration/odoo_online.rst:43 #: ../../content/administration/odoo_sh/getting_started/branches.rst:293 #: ../../content/administration/odoo_sh/getting_started/settings.rst:77 #: ../../content/administration/odoo_sh/getting_started/settings.rst:113 @@ -3077,722 +475,144 @@ msgstr "" msgid "Upgrade" msgstr "" -#: ../../content/administration/maintain/odoo_online.rst:30 +#: ../../content/administration/odoo_online.rst:45 msgid "Trigger a database upgrade." msgstr "" -#: ../../content/administration/maintain/odoo_online.rst:33 +#: ../../content/administration/odoo_online.rst:48 msgid "For more information about the upgrade process, check out the :ref:`Odoo Online upgrade documentation `." msgstr "" -#: ../../content/administration/maintain/odoo_online.rst:39 +#: ../../content/administration/odoo_online.rst:54 msgid "Duplicate" msgstr "" -#: ../../content/administration/maintain/odoo_online.rst:41 +#: ../../content/administration/odoo_online.rst:56 msgid "Create an exact copy of the database, which can be used to perform testing without compromising daily operations." msgstr "" -#: ../../content/administration/maintain/odoo_online.rst:45 +#: ../../content/administration/odoo_online.rst:60 msgid "By checking :guilabel:`For testing purposes`, all external actions (emails, payments, delivery orders, etc.) are disabled by default on the duplicated database." msgstr "" -#: ../../content/administration/maintain/odoo_online.rst:47 +#: ../../content/administration/odoo_online.rst:62 msgid "Duplicated databases expire automatically after 15 days." msgstr "" -#: ../../content/administration/maintain/odoo_online.rst:52 +#: ../../content/administration/odoo_online.rst:67 msgid "Rename" msgstr "" -#: ../../content/administration/maintain/odoo_online.rst:54 +#: ../../content/administration/odoo_online.rst:69 msgid "Rename the database and its URL." msgstr "" -#: ../../content/administration/maintain/odoo_online.rst:59 +#: ../../content/administration/odoo_online.rst:74 msgid "Download" msgstr "" -#: ../../content/administration/maintain/odoo_online.rst:61 +#: ../../content/administration/odoo_online.rst:76 msgid "Download a ZIP file containing a backup of the database." msgstr "" -#: ../../content/administration/maintain/odoo_online.rst:64 +#: ../../content/administration/odoo_online.rst:79 msgid "Databases are backed up daily as per the `Odoo Cloud Hosting SLA `_." msgstr "" -#: ../../content/administration/maintain/odoo_online.rst:72 -msgid "Use a custom :doc:`domain name ` to access the database via another URL." +#: ../../content/administration/odoo_online.rst:85 +msgid "Domain names" msgstr "" -#: ../../content/administration/maintain/odoo_online.rst:75 +#: ../../content/administration/odoo_online.rst:87 +msgid "Use a custom :doc:`domain name ` to access the database via another URL." +msgstr "" + +#: ../../content/administration/odoo_online.rst:91 msgid "You can :ref:`register a domain name for free `." msgstr "" -#: ../../content/administration/maintain/odoo_online.rst:80 +#: ../../content/administration/odoo_online.rst:96 msgid "Tags" msgstr "" -#: ../../content/administration/maintain/odoo_online.rst:82 +#: ../../content/administration/odoo_online.rst:98 msgid "Add tags to easily identify and sort your databases." msgstr "" -#: ../../content/administration/maintain/odoo_online.rst:85 +#: ../../content/administration/odoo_online.rst:101 msgid "You can search for tags in the search bar." msgstr "" -#: ../../content/administration/maintain/odoo_online.rst:90 +#: ../../content/administration/odoo_online.rst:106 #: ../../content/administration/odoo_sh/getting_started/branches.rst:550 msgid "Delete" msgstr "" -#: ../../content/administration/maintain/odoo_online.rst:92 +#: ../../content/administration/odoo_online.rst:108 msgid "Delete a database instantly." msgstr "" -#: ../../content/administration/maintain/odoo_online.rst:95 +#: ../../content/administration/odoo_online.rst:111 msgid "Deleting a database means that all data is permanently lost. The deletion is instant and applies to all users. It is recommended to create a backup of the database before deleting it." msgstr "" -#: ../../content/administration/maintain/odoo_online.rst:98 +#: ../../content/administration/odoo_online.rst:114 msgid "Carefully read the warning message and only proceed if the implications of deleting a database are fully understood." msgstr "" -#: ../../content/administration/maintain/odoo_online.rst:-1 +#: ../../content/administration/odoo_online.rst:-1 msgid "The warning message displayed before deleting a database" msgstr "" -#: ../../content/administration/maintain/odoo_online.rst:105 +#: ../../content/administration/odoo_online.rst:121 msgid "Only an administrator can delete a database." msgstr "" -#: ../../content/administration/maintain/odoo_online.rst:106 +#: ../../content/administration/odoo_online.rst:122 msgid "The database name is immediately made available to anyone." msgstr "" -#: ../../content/administration/maintain/odoo_online.rst:107 +#: ../../content/administration/odoo_online.rst:123 msgid "Deleting a database if it has expired or is linked to a subscription is impossible. In that case, contact `Odoo Support `_." msgstr "" -#: ../../content/administration/maintain/odoo_online.rst:113 +#: ../../content/administration/odoo_online.rst:129 msgid "Contact us" msgstr "" -#: ../../content/administration/maintain/odoo_online.rst:115 +#: ../../content/administration/odoo_online.rst:131 msgid "Access the `Odoo.com support page `_ with the database's details already pre-filled." msgstr "" -#: ../../content/administration/maintain/odoo_online.rst:121 +#: ../../content/administration/odoo_online.rst:137 msgid "Invite / remove users" msgstr "" -#: ../../content/administration/maintain/odoo_online.rst:123 +#: ../../content/administration/odoo_online.rst:139 msgid "To invite users, fill out the new user's email address and click :guilabel:`Invite`. To add multiple users, click :guilabel:`Add more users`." msgstr "" -#: ../../content/administration/maintain/odoo_online.rst:-1 +#: ../../content/administration/odoo_online.rst:-1 msgid "Inviting a user on a database" msgstr "" -#: ../../content/administration/maintain/odoo_online.rst:129 +#: ../../content/administration/odoo_online.rst:145 msgid "To remove users, select them and click :guilabel:`Remove`." msgstr "" -#: ../../content/administration/maintain/odoo_online.rst:132 -msgid ":doc:`/applications/general/users/manage_users`" +#: ../../content/administration/odoo_online.rst:148 +msgid ":doc:`/applications/general/users`" msgstr "" -#: ../../content/administration/maintain/odoo_online.rst:133 -msgid ":doc:`/applications/general/users/odoo_account`" +#: ../../content/administration/odoo_online.rst:149 +msgid ":doc:`odoo_accounts`" msgstr "" -#: ../../content/administration/maintain/on_premise.rst:3 -msgid "On-premise database management" -msgstr "" - -#: ../../content/administration/maintain/on_premise.rst:6 -msgid "Register a database" -msgstr "" - -#: ../../content/administration/maintain/on_premise.rst:8 -msgid "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 Expiration Date in the About menu (Odoo 9) or in the Settings Dashboard (Odoo 10)." -msgstr "" - -#: ../../content/administration/maintain/on_premise.rst:16 -msgid "Registration Error Message" -msgstr "" - -#: ../../content/administration/maintain/on_premise.rst:18 -msgid "If you are unable to register your database, you will likely encounter this message:" -msgstr "" - -#: ../../content/administration/maintain/on_premise.rst:-1 -msgid "Something went wrong while registering your database, you can try again or contact Odoo\n" -"Help" -msgstr "" - -#: ../../content/administration/maintain/on_premise.rst:27 -#: ../../content/administration/maintain/on_premise.rst:100 -#: ../../content/administration/maintain/on_premise.rst:127 -msgid "Solutions" -msgstr "" - -#: ../../content/administration/maintain/on_premise.rst:29 -msgid "Do you have a valid Enterprise subscription?" -msgstr "" - -#: ../../content/administration/maintain/on_premise.rst:31 -msgid "Check if your subscription details get the tag \"In Progress\" on your `Odoo Account `__ or with your Account Manager" -msgstr "" - -#: ../../content/administration/maintain/on_premise.rst:35 -msgid "Have you already linked a database with your subscription reference?" -msgstr "" - -#: ../../content/administration/maintain/on_premise.rst:37 -msgid "You can link only one database per subscription. (Need a test or a development database? `Find a partner `__)" -msgstr "" - -#: ../../content/administration/maintain/on_premise.rst:41 -msgid "You can unlink the old database yourself on your `Odoo Contract `__ with the button \"Unlink database\"" -msgstr "" - -#: ../../content/administration/maintain/on_premise.rst:47 -msgid "A confirmation message will appear; make sure this is the correct database as it will be deactivated shortly:" -msgstr "" - -#: ../../content/administration/maintain/on_premise.rst:53 -msgid "Do you have the updated version of Odoo 9?" -msgstr "" - -#: ../../content/administration/maintain/on_premise.rst:55 -#: ../../content/administration/maintain/on_premise.rst:159 -msgid "From July 2016 onward, Odoo 9 now automatically change the uuid of a duplicated database; a manual operation is no longer required." -msgstr "" - -#: ../../content/administration/maintain/on_premise.rst:58 -msgid "If it's not the case, you may have multiple databases sharing the same UUID. Please check on your `Odoo Contract `__, a short message will appear specifying which database is problematic:" -msgstr "" - -#: ../../content/administration/maintain/on_premise.rst:66 -msgid "In this case, you need to change the UUID on your test databases to solve this issue. You will find more information about this in :ref:`this section `." -msgstr "" - -#: ../../content/administration/maintain/on_premise.rst:69 -msgid "For your information, we identify database with UUID. Therefore, each database should have a distinct UUID to ensure that registration and invoicing proceed effortlessly for your and for us." -msgstr "" - -#: ../../content/administration/maintain/on_premise.rst:73 -msgid "Check your network and firewall settings" -msgstr "" - -#: ../../content/administration/maintain/on_premise.rst:75 -msgid "The Update notification must be able to reach Odoo's subscription validation servers. In other words, make sure that the Odoo server is able to open outgoing connections towards:" -msgstr "" - -#: ../../content/administration/maintain/on_premise.rst:79 -msgid "services.odoo.com on port 443 (or 80)" -msgstr "" - -#: ../../content/administration/maintain/on_premise.rst:80 -msgid "services.openerp.com on port 443 (or 80) for older deployments" -msgstr "" - -#: ../../content/administration/maintain/on_premise.rst:82 -msgid "Once you activated your database, you must keep these ports open, as the Update notification runs once a week." -msgstr "" - -#: ../../content/administration/maintain/on_premise.rst:86 -msgid "Error message due to too many users" -msgstr "" - -#: ../../content/administration/maintain/on_premise.rst:88 -msgid "If you have more users in your local database than provisionned in your Odoo Enterprise subscription, you may encounter this message:" -msgstr "" - -#: ../../content/administration/maintain/on_premise.rst:-1 -msgid "This database will expire in X days, you have more users than your subscription allows" -msgstr "" - -#: ../../content/administration/maintain/on_premise.rst:96 -msgid "When the message appears you have 30 days before the expiration. The countdown is updated everyday." -msgstr "" - -#: ../../content/administration/maintain/on_premise.rst:102 -msgid "**Add more users** on your subscription: follow the link and Validate the upsell quotation and pay for the extra users." -msgstr "" - -#: ../../content/administration/maintain/on_premise.rst:104 -msgid "**Deactivate users** as explained in this `documentation `_ and **Reject** the upsell quotation." -msgstr "" - -#: ../../content/administration/maintain/on_premise.rst:107 -msgid "Once your database has the correct number of users, the expiration message will disappear automatically after a few days, when the next verification occurs. We understand that it can be a bit frightening to see the countdown, so you can :ref:`force an Update Notification ` to make the message disappear right away." -msgstr "" - -#: ../../content/administration/maintain/on_premise.rst:114 -msgid "Database expired error message" -msgstr "" - -#: ../../content/administration/maintain/on_premise.rst:116 -msgid "If your database reaches its expiration date before your renew your subscription, you will encounter this message:" -msgstr "" - -#: ../../content/administration/maintain/on_premise.rst:-1 -msgid "This database has expired." -msgstr "" - -#: ../../content/administration/maintain/on_premise.rst:123 -msgid "This **blocking** message appears after a non-blocking message that lasts 30 days. If you fail to take action before the end of the countdown, the database is expired." -msgstr "" - -#: ../../content/administration/maintain/on_premise.rst:131 -msgid "Renew your subscription: follow the link and renew your subscription - note that" -msgstr "" - -#: ../../content/administration/maintain/on_premise.rst:130 -msgid "if you wish to pay by Wire Transfer, your subscription will effectively be renewed only when the payment arrives, which can take a few days. Credit card payments are processed immediately." -msgstr "" - -#: ../../content/administration/maintain/on_premise.rst:133 -msgid "Contact our `Support `__" -msgstr "" - -#: ../../content/administration/maintain/on_premise.rst:135 -msgid "None of those solutions worked for you? Please contact our `Support `__" -msgstr "" - -#: ../../content/administration/maintain/on_premise.rst:143 -msgid "Duplicate a database" -msgstr "" - -#: ../../content/administration/maintain/on_premise.rst:145 -msgid "You can duplicate your database by accessing the database manager on your server (/web/database/manager). In this page, you can easily duplicate your database (among other things)." -msgstr "" - -#: ../../content/administration/maintain/on_premise.rst:152 -msgid "When you duplicate a local database, it is **strongly** advised to change the duplicated database's uuid (Unniversally Unique Identifier), since this uuid is how your database identifies itself with our servers. Having two databases with the same uuid could result in invoicing problems or registration problems down the line." -msgstr "" - -#: ../../content/administration/maintain/on_premise.rst:162 -msgid "The database uuid is currently accessible from the menu :menuselection:`Settings --> Technical --> System Parameters`, we advise you to use a `uuid generator `_ or to 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." -msgstr "" - -#: ../../content/administration/maintain/supported_versions.rst:7 -msgid "Supported versions" -msgstr "" - -#: ../../content/administration/maintain/supported_versions.rst:9 -msgid "Odoo provides support and bug fixing **for the 3 last major versions** of Odoo." -msgstr "" - -#: ../../content/administration/maintain/supported_versions.rst:12 -msgid "Odoo releases intermediary versions called **Online versions** on the :doc:`Odoo Online ` hosting every two months. Odoo Online users can then benefit from the latest features of Odoo." -msgstr "" - -#: ../../content/administration/maintain/supported_versions.rst:16 -msgid "Admins of Odoo Online databases are invited to :doc:`upgrade <../upgrade>` them regularly." -msgstr "" - -#: ../../content/administration/maintain/supported_versions.rst:17 -msgid "Online versions are *not* released for Odoo.sh and On-Premise installations." -msgstr "" - -#: ../../content/administration/maintain/supported_versions.rst:18 -msgid "Online versions are listed below as *SaaS*." -msgstr "" - -#: ../../content/administration/maintain/supported_versions.rst:20 -msgid "This matrix shows the support status of every version." -msgstr "" - -#: ../../content/administration/maintain/supported_versions.rst:22 -msgid "**Major releases are in bold type.**" -msgstr "" - -#: ../../content/administration/maintain/supported_versions.rst:31 -msgid "On-Premise" -msgstr "" - -#: ../../content/administration/maintain/supported_versions.rst:32 -msgid "Release date" -msgstr "" - -#: ../../content/administration/maintain/supported_versions.rst:33 -msgid "End of support" -msgstr "" - -#: ../../content/administration/maintain/supported_versions.rst:34 -msgid "Odoo saas~17.1" -msgstr "" - -#: ../../content/administration/maintain/supported_versions.rst:35 -#: ../../content/administration/maintain/supported_versions.rst:41 -#: ../../content/administration/maintain/supported_versions.rst:42 -#: ../../content/administration/maintain/supported_versions.rst:43 -#: ../../content/administration/maintain/supported_versions.rst:47 -#: ../../content/administration/maintain/supported_versions.rst:71 -#: ../../content/administration/maintain/supported_versions.rst:72 -#: ../../content/administration/maintain/supported_versions.rst:73 -#: ../../content/administration/maintain/supported_versions.rst:89 -#: ../../content/administration/maintain/supported_versions.rst:90 -#: ../../content/administration/maintain/supported_versions.rst:91 -#: ../../content/administration/odoo_sh/getting_started/settings.rst:58 -#: ../../content/administration/odoo_sh/getting_started/settings.rst:59 -#: ../../content/administration/odoo_sh/getting_started/settings.rst:62 -#: ../../content/administration/odoo_sh/getting_started/settings.rst:63 -#: ../../content/administration/odoo_sh/getting_started/settings.rst:66 -#: ../../content/administration/odoo_sh/getting_started/settings.rst:67 -#: ../../content/administration/odoo_sh/getting_started/settings.rst:70 -#: ../../content/administration/odoo_sh/getting_started/settings.rst:71 -#: ../../content/administration/odoo_sh/getting_started/settings.rst:74 -#: ../../content/administration/odoo_sh/getting_started/settings.rst:75 -#: ../../content/administration/odoo_sh/getting_started/settings.rst:78 -#: ../../content/administration/odoo_sh/getting_started/settings.rst:79 -#: ../../content/administration/odoo_sh/getting_started/settings.rst:82 -#: ../../content/administration/odoo_sh/getting_started/settings.rst:83 -#: ../../content/administration/odoo_sh/getting_started/settings.rst:86 -#: ../../content/administration/odoo_sh/getting_started/settings.rst:87 -#: ../../content/administration/odoo_sh/getting_started/settings.rst:91 -#: ../../content/administration/odoo_sh/getting_started/settings.rst:95 -#: ../../content/administration/odoo_sh/getting_started/settings.rst:99 -#: ../../content/administration/odoo_sh/getting_started/settings.rst:103 -#: ../../content/administration/odoo_sh/getting_started/settings.rst:107 -#: ../../content/administration/odoo_sh/getting_started/settings.rst:111 -#: ../../content/administration/odoo_sh/getting_started/settings.rst:115 -#: ../../content/administration/odoo_sh/getting_started/settings.rst:119 -#: ../../content/administration/odoo_sh/getting_started/settings.rst:122 -#: ../../content/administration/odoo_sh/getting_started/settings.rst:123 -#: ../../content/administration/odoo_sh/getting_started/settings.rst:127 -msgid "|green|" -msgstr "" - -#: ../../content/administration/maintain/supported_versions.rst:36 -#: ../../content/administration/maintain/supported_versions.rst:37 -#: ../../content/administration/maintain/supported_versions.rst:48 -#: ../../content/administration/maintain/supported_versions.rst:49 -#: ../../content/administration/maintain/supported_versions.rst:54 -#: ../../content/administration/maintain/supported_versions.rst:55 -#: ../../content/administration/maintain/supported_versions.rst:60 -#: ../../content/administration/maintain/supported_versions.rst:61 -#: ../../content/administration/maintain/supported_versions.rst:66 -#: ../../content/administration/maintain/supported_versions.rst:67 -#: ../../content/administration/maintain/supported_versions.rst:78 -#: ../../content/administration/maintain/supported_versions.rst:79 -#: ../../content/administration/maintain/supported_versions.rst:84 -#: ../../content/administration/maintain/supported_versions.rst:85 -msgid "N/A" -msgstr "" - -#: ../../content/administration/maintain/supported_versions.rst:38 -msgid "January 2024" -msgstr "" - -#: ../../content/administration/maintain/supported_versions.rst:40 -msgid "**Odoo 17.0**" -msgstr "" - -#: ../../content/administration/maintain/supported_versions.rst:44 -#: ../../content/administration/maintain/supported_versions.rst:99 -msgid "November 2023" -msgstr "" - -#: ../../content/administration/maintain/supported_versions.rst:45 -msgid "October 2026 (planned)" -msgstr "" - -#: ../../content/administration/maintain/supported_versions.rst:46 -msgid "Odoo saas~16.4" -msgstr "" - -#: ../../content/administration/maintain/supported_versions.rst:50 -msgid "August 2023" -msgstr "" - -#: ../../content/administration/maintain/supported_versions.rst:52 -msgid "Odoo saas~16.3" -msgstr "" - -#: ../../content/administration/maintain/supported_versions.rst:53 -#: ../../content/administration/maintain/supported_versions.rst:59 -#: ../../content/administration/maintain/supported_versions.rst:65 -#: ../../content/administration/maintain/supported_versions.rst:77 -#: ../../content/administration/maintain/supported_versions.rst:83 -#: ../../content/administration/maintain/supported_versions.rst:95 -#: ../../content/administration/maintain/supported_versions.rst:96 -#: ../../content/administration/maintain/supported_versions.rst:97 -#: ../../content/administration/maintain/supported_versions.rst:101 -#: ../../content/administration/maintain/supported_versions.rst:102 -#: ../../content/administration/maintain/supported_versions.rst:103 -#: ../../content/administration/maintain/supported_versions.rst:107 -#: ../../content/administration/maintain/supported_versions.rst:108 -#: ../../content/administration/maintain/supported_versions.rst:109 -msgid "|red|" -msgstr "" - -#: ../../content/administration/maintain/supported_versions.rst:56 -msgid "June 2023" -msgstr "" - -#: ../../content/administration/maintain/supported_versions.rst:58 -msgid "Odoo saas~16.2" -msgstr "" - -#: ../../content/administration/maintain/supported_versions.rst:62 -msgid "March 2023" -msgstr "" - -#: ../../content/administration/maintain/supported_versions.rst:64 -msgid "Odoo saas~16.1" -msgstr "" - -#: ../../content/administration/maintain/supported_versions.rst:68 -msgid "February 2023" -msgstr "" - -#: ../../content/administration/maintain/supported_versions.rst:70 -msgid "**Odoo 16.0**" -msgstr "" - -#: ../../content/administration/maintain/supported_versions.rst:74 -#: ../../content/administration/maintain/supported_versions.rst:105 -msgid "October 2022" -msgstr "" - -#: ../../content/administration/maintain/supported_versions.rst:75 -msgid "November 2025 (planned)" -msgstr "" - -#: ../../content/administration/maintain/supported_versions.rst:76 -msgid "Odoo saas~15.2" -msgstr "" - -#: ../../content/administration/maintain/supported_versions.rst:80 -msgid "March 2022" -msgstr "" - -#: ../../content/administration/maintain/supported_versions.rst:81 -msgid "January 2023" -msgstr "" - -#: ../../content/administration/maintain/supported_versions.rst:82 -msgid "Odoo saas~15.1" -msgstr "" - -#: ../../content/administration/maintain/supported_versions.rst:86 -msgid "February 2022" -msgstr "" - -#: ../../content/administration/maintain/supported_versions.rst:87 -msgid "July 2022" -msgstr "" - -#: ../../content/administration/maintain/supported_versions.rst:88 -msgid "**Odoo 15.0**" -msgstr "" - -#: ../../content/administration/maintain/supported_versions.rst:92 -msgid "October 2021" -msgstr "" - -#: ../../content/administration/maintain/supported_versions.rst:93 -msgid "November 2024 (planned)" -msgstr "" - -#: ../../content/administration/maintain/supported_versions.rst:94 -msgid "**Odoo 14.0**" -msgstr "" - -#: ../../content/administration/maintain/supported_versions.rst:98 -msgid "October 2020" -msgstr "" - -#: ../../content/administration/maintain/supported_versions.rst:100 -msgid "**Odoo 13.0**" -msgstr "" - -#: ../../content/administration/maintain/supported_versions.rst:104 -msgid "October 2019" -msgstr "" - -#: ../../content/administration/maintain/supported_versions.rst:106 -msgid "Older versions" -msgstr "" - -#: ../../content/administration/maintain/supported_versions.rst:110 -msgid "Before 2019" -msgstr "" - -#: ../../content/administration/maintain/supported_versions.rst:111 -msgid "Before 2022" -msgstr "" - -#: ../../content/administration/maintain/supported_versions.rst:113 -msgid "Legend" -msgstr "" - -#: ../../content/administration/maintain/supported_versions.rst:115 -msgid "|green| Supported version" -msgstr "" - -#: ../../content/administration/maintain/supported_versions.rst:117 -msgid "|red| End-of-support" -msgstr "" - -#: ../../content/administration/maintain/supported_versions.rst:119 -msgid "N/A Never released for this platform" -msgstr "" - -#: ../../content/administration/maintain/supported_versions.rst:122 -msgid "Even though we don't support older versions, you can always `upgrade from any version `_." -msgstr "" - -#: ../../content/administration/maintain/update.rst:6 -msgid "Bugfix updates" -msgstr "" - -#: ../../content/administration/maintain/update.rst:9 -msgid "Introduction" -msgstr "" - -#: ../../content/administration/maintain/update.rst:11 -msgid "In order to benefit from the latest improvements, security fixes, bug corrections and performance boosts, you may need to update your Odoo installation from time to time." -msgstr "" - -#: ../../content/administration/maintain/update.rst:14 -msgid "This guide only applies when are using Odoo on your own hosting infrastructure. If you are using one of the Odoo Cloud solutions, updates are automatically performed for you." -msgstr "" - -#: ../../content/administration/maintain/update.rst:17 -msgid "The terminology surrounding software updates is often confusing, so here are some preliminary definitions:" -msgstr "" - -#: ../../content/administration/maintain/update.rst:25 -msgid "Updating (an Odoo installation)" -msgstr "" - -#: ../../content/administration/maintain/update.rst:21 -msgid "Refers to the process of obtaining the latest revision of the source code for your current Odoo Edition. For example, updating your Odoo Enterprise 13.0 to the latest revision. This does not directly cause any change to the contents of your Odoo database, and can be undone by reinstalling the previous revision of the source code." -msgstr "" - -#: ../../content/administration/maintain/update.rst:35 -msgid "Upgrading (an Odoo database)" -msgstr "" - -#: ../../content/administration/maintain/update.rst:28 -msgid "Refers to a complex data processing operation where the structure and contents of your database is permanently altered to make it compatible with a new release of Odoo. This operation is irreversible and typically accomplished via Odoo's `database upgrade service `_, when you decide to switch to a newer release of Odoo. Historically, this process has also been known as a \"migration\" because it involves moving data around inside the database, even though the database may end up at the same physical location after the upgrade." -msgstr "" - -#: ../../content/administration/maintain/update.rst:37 -msgid "This page describes the typical steps needed to *update* an Odoo installation to the latest version. If you'd like more information about upgrading a database, please visit the `Odoo Upgrade page `_ instead." -msgstr "" - -#: ../../content/administration/maintain/update.rst:43 -msgid "In a nutshell" -msgstr "" - -#: ../../content/administration/maintain/update.rst:45 -msgid "Updating Odoo is accomplished by simply reinstalling the latest version of your Odoo Edition on top of your current installation. This will preserve your data without any alteration, as long as you do not uninstall PostgreSQL (the database engine that comes with Odoo)." -msgstr "" - -#: ../../content/administration/maintain/update.rst:49 -msgid "The main reference for updating is logically our :doc:`installation guide <../install>`, which explains the common installation methods." -msgstr "" - -#: ../../content/administration/maintain/update.rst:52 -msgid "Updating is also most appropriately accomplished by the person who deployed Odoo initially, because the procedure is very similar." -msgstr "" - -#: ../../content/administration/maintain/update.rst:55 -msgid "We always recommend to download a complete new up-to-date Odoo version, rather than manually applying patches, such as the security patches that come with Security Advisories. The patches are mainly provided for installations that are heavily customized, or for technical personnel who prefer to apply minimal changes temporarily while testing a complete update." -msgstr "" - -#: ../../content/administration/maintain/update.rst:64 -msgid "Step 1: Download an updated Odoo version" -msgstr "" - -#: ../../content/administration/maintain/update.rst:66 -msgid "The central download page is https://www.odoo.com/page/download. If you see a \"Buy\" link for the Odoo Enterprise download, make sure you are logged into Odoo.com with the same login that is linked to your Odoo Enterprise subscription." -msgstr "" - -#: ../../content/administration/maintain/update.rst:70 -msgid "Alternatively, you can use the unique download link that was included with your Odoo Enterprise purchase confirmation email." -msgstr "" - -#: ../../content/administration/maintain/update.rst:73 -msgid "Downloading an updated version is not necessary if you installed via Github (see below)" -msgstr "" - -#: ../../content/administration/maintain/update.rst:77 -msgid "Step 2: Make a backup of your database" -msgstr "" - -#: ../../content/administration/maintain/update.rst:79 -msgid "The update procedure is quite safe and should not alter you data. However it's always best to take a full database backup before performing any change on your installation, and to store it somewhere safe, on a different computer." -msgstr "" - -#: ../../content/administration/maintain/update.rst:83 -msgid "If you have not disabled the database manager screen (see :ref:`here ` why you should), you can use it (link at bottom of your database selection screen) to download a backup of your database(s). If you disabled it, use the same procedure than for your usual backups." -msgstr "" - -#: ../../content/administration/maintain/update.rst:89 -msgid "Step 3: Install the updated version" -msgstr "" - -#: ../../content/administration/maintain/update.rst:91 -msgid "Choose the method that matches your current installation:" -msgstr "" - -#: ../../content/administration/maintain/update.rst:95 -msgid "Packaged Installers" -msgstr "" - -#: ../../content/administration/maintain/update.rst:97 -msgid "If you installed Odoo with an installation package downloaded on our website (the recommended method), updating is very simple. All you have to do is download the installation package corresponding to your system (see step #1) and install it on your server. They are updated daily and include the latest security fixes. Usually, you can simply double-click the package to install it on top of the current installation. After installing the package, be sure to restart the Odoo service or reboot your server, and you're all set." -msgstr "" - -#: ../../content/administration/maintain/update.rst:106 -msgid "Source Install (Tarball)" -msgstr "" - -#: ../../content/administration/maintain/update.rst:108 -msgid "If you have originally installed Odoo with the \"tarball\" version (source code archive), you have to replace the installation directory with a newer version. First download the latest tarball from Odoo.com. They are updated daily and include the latest security fixes (see step #1) After downloading the package, extract it to a temporary location on your server." -msgstr "" - -#: ../../content/administration/maintain/update.rst:113 -msgid "You will get a folder labeled with the version of the source code, for example \"odoo-13.0+e.20190719\", that contains a folder \"odoo.egg-info\" and the actual source code folder named \"odoo\" (for Odoo 10 and later) or \"openerp\" for older versions. You can ignore the odoo.egg-info folder. Locate the folder where your current installation is deployed, and replace it with the newer \"odoo\" or \"openerp\" folder that was in the archive you just extracted." -msgstr "" - -#: ../../content/administration/maintain/update.rst:119 -msgid "Be sure to match the folder layout, for example the new \"addons\" folder included in the source code should end up exactly at the same path it was before. Next, watch out for any specific configuration files that you may have manually copied or modified in the old folder, and copy them over to the new folder. Finally, restart the Odoo service or reboot the machine, and you are all set." -msgstr "" - -#: ../../content/administration/maintain/update.rst:126 -msgid "Source Install (Github)" -msgstr "" - -#: ../../content/administration/maintain/update.rst:128 -msgid "If you have originally installed Odoo with a full Github clone of the official repositories, the update procedure requires you to pull the latest source code via git. Change into the directory for each repository (the main Odoo repository, and the Enterprise repository), and run the following commands::" -msgstr "" - -#: ../../content/administration/maintain/update.rst:136 -msgid "The last command may encounter source code conflicts if you had edited the Odoo source code locally. The error message will give you the list of files with conflicts, and you will need to resolve the conflicts manually, by editing them and deciding which part of the code to keep." -msgstr "" - -#: ../../content/administration/maintain/update.rst:140 -msgid "Alternatively, if you prefer to simply discard the conflicting changes and restore the official version, you can use the following command::" -msgstr "" - -#: ../../content/administration/maintain/update.rst:145 -msgid "Finally, restart the Odoo service or reboot the machine, and you should be done." -msgstr "" - -#: ../../content/administration/maintain/update.rst:149 -msgid "Docker" -msgstr "" - -#: ../../content/administration/maintain/update.rst:151 -msgid "Please refer to our `Docker image documentation `_ for specific update instructions." +#: ../../content/administration/odoo_sh.rst:5 +#: ../../content/administration/supported_versions.rst:30 +#: ../../content/administration/upgrade.rst:120 +#: ../../content/administration/upgrade.rst:318 +msgid "Odoo.sh" msgstr "" #: ../../content/administration/odoo_sh/advanced.rst:5 @@ -4730,6 +1550,10 @@ msgstr "" msgid "SSH" msgstr "" +#: ../../content/administration/odoo_sh/getting_started/branches.rst:480 +msgid "Setup" +msgstr "" + #: ../../content/administration/odoo_sh/getting_started/branches.rst:482 msgid "In order to use SSH, you have to set up your profile SSH public key (if it is not already done). To do so, follow these steps:" msgstr "" @@ -5031,7 +1855,7 @@ msgid "Import your database" msgstr "" #: ../../content/administration/odoo_sh/getting_started/create.rst:93 -msgid "You can import your database in your Odoo.sh project as long as it is in a :doc:`supported version ` of Odoo." +msgid "You can import your database in your Odoo.sh project as long as it is in a :doc:`supported version ` of Odoo." msgstr "" #: ../../content/administration/odoo_sh/getting_started/create.rst:97 @@ -5147,7 +1971,7 @@ msgid "The imported database is considered a duplicate by default and the enterp msgstr "" #: ../../content/administration/odoo_sh/getting_started/create.rst:203 -msgid "If you plan to make it your production, unlink your former database from the subscription, and register the newly imported database. Read the :doc:`database registration documentation <../../maintain/on_premise>` for instructions." +msgid "If you plan to make it your production, unlink your former database from the subscription, and register the newly imported database. Read the :doc:`database registration documentation <../../on_premise>` for instructions." msgstr "" #: ../../content/administration/odoo_sh/getting_started/first_module.rst:3 @@ -5226,10 +2050,12 @@ msgstr "" msgid "|pic1| |pic2|" msgstr "" +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:40 #: ../../content/administration/odoo_sh/getting_started/first_module.rst:40 msgid "pic1" msgstr "" +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:43 #: ../../content/administration/odoo_sh/getting_started/first_module.rst:43 msgid "pic2" msgstr "" @@ -5267,7 +2093,7 @@ msgid "From the Odoo.sh editor, in a terminal:" msgstr "" #: ../../content/administration/odoo_sh/getting_started/first_module.rst:88 -msgid "Or, from your computer, if you have an :doc:`installation of Odoo <../../install/source>`:" +msgid "Or, from your computer, if you have an :doc:`installation of Odoo <../../on_premise/source>`:" msgstr "" #: ../../content/administration/odoo_sh/getting_started/first_module.rst:94 @@ -5865,6 +2691,47 @@ msgstr "" msgid "Admin" msgstr "" +#: ../../content/administration/odoo_sh/getting_started/settings.rst:58 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:59 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:62 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:63 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:66 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:67 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:70 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:71 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:74 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:75 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:78 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:79 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:82 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:83 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:86 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:87 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:91 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:95 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:99 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:103 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:107 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:111 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:115 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:119 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:122 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:123 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:127 +#: ../../content/administration/supported_versions.rst:35 +#: ../../content/administration/supported_versions.rst:41 +#: ../../content/administration/supported_versions.rst:42 +#: ../../content/administration/supported_versions.rst:43 +#: ../../content/administration/supported_versions.rst:47 +#: ../../content/administration/supported_versions.rst:71 +#: ../../content/administration/supported_versions.rst:72 +#: ../../content/administration/supported_versions.rst:73 +#: ../../content/administration/supported_versions.rst:89 +#: ../../content/administration/supported_versions.rst:90 +#: ../../content/administration/supported_versions.rst:91 +msgid "|green|" +msgstr "" + #: ../../content/administration/odoo_sh/getting_started/settings.rst:61 #: ../../content/administration/odoo_sh/getting_started/settings.rst:89 msgid "1-click connect" @@ -6044,8 +2911,1918 @@ msgstr "" msgid "The documentation will help you go live with your Odoo.sh project in no time." msgstr "" +#: ../../content/administration/on_premise.rst:5 +#: ../../content/administration/upgrade.rst:145 +#: ../../content/administration/upgrade.rst:341 +msgid "On-premise" +msgstr "" + +#: ../../content/administration/on_premise.rst:8 +msgid "Register a database" +msgstr "" + +#: ../../content/administration/on_premise.rst:10 +msgid "To register your database, enter your subscription code in the banner in the app dashboard. If the registration is successful, the banner will turn green and display the database expiration date." +msgstr "" + +#: ../../content/administration/on_premise.rst:14 +msgid "The expiration date is also displayed at the bottom of the Settings page." +msgstr "" + +#: ../../content/administration/on_premise.rst:19 +msgid "Duplicate a database" +msgstr "" + +#: ../../content/administration/on_premise.rst:21 +msgid "Duplicate a database by accessing the database manager on your server (`/web/database/manager`). Typically, you want to duplicate your production database into a neutralized testing database. It can be done by checking the neutralize box when prompted, which executes all :file:`neutralize.sql` scripts for every installed module." +msgstr "" + +#: ../../content/administration/on_premise.rst:27 +msgid "Common error messages and solutions" +msgstr "" + +#: ../../content/administration/on_premise.rst:30 +msgid "Registration error" +msgstr "" + +#: ../../content/administration/on_premise.rst:32 +msgid "In case of a registration error, the following message should be displayed." +msgstr "" + +#: ../../content/administration/on_premise.rst:-1 +msgid "Database registration error message" +msgstr "" + +#: ../../content/administration/on_premise.rst:37 +msgid "To resolve the issue:" +msgstr "" + +#: ../../content/administration/on_premise.rst:39 +msgid "Check the **validity of your Odoo Enterprise subscription** by verifying if your subscription details have the tag :guilabel:`In Progress` on your `Odoo Account `_ or contact your Account Manager." +msgstr "" + +#: ../../content/administration/on_premise.rst:43 +msgid "Ensure that **no other database is linked** to the subscription code, as only one database can be linked per subscription." +msgstr "" + +#: ../../content/administration/on_premise.rst:47 +msgid "If a test or a development database is needed, you can :ref:`duplicate a database `." +msgstr "" + +#: ../../content/administration/on_premise.rst:50 +msgid "Verify that **no databases share the same UUID** (Universally Unique Identifier) by opening your `Odoo Contract `_. If two or more databases share the same UUID, their name will be displayed." +msgstr "" + +#: ../../content/administration/on_premise.rst:-1 +msgid "Database UUID error message" +msgstr "" + +#: ../../content/administration/on_premise.rst:57 +msgid "If that is the case, manually change the database(s) UUID or `send a support ticket `_." +msgstr "" + +#: ../../content/administration/on_premise.rst:60 +msgid "As the update notification must be able to reach Odoo's subscription validation servers, ensure your **network and firewall settings** allow the Odoo server to open outgoing connections towards:" +msgstr "" + +#: ../../content/administration/on_premise.rst:64 +msgid "`services.odoo.com` on port `443` (or `80`)" +msgstr "" + +#: ../../content/administration/on_premise.rst:65 +msgid "for older deployments, `services.openerp.com` on port `443` (or `80`)" +msgstr "" + +#: ../../content/administration/on_premise.rst:67 +msgid "These ports must be kept open even after registering a database, as the update notification runs once a week." +msgstr "" + +#: ../../content/administration/on_premise.rst:71 +msgid "Too many users error" +msgstr "" + +#: ../../content/administration/on_premise.rst:73 +msgid "If you have more users in a local database than provisioned in your Odoo Enterprise subscription, the following message should be displayed." +msgstr "" + +#: ../../content/administration/on_premise.rst:-1 +msgid "Too many users on a database error message" +msgstr "" + +#: ../../content/administration/on_premise.rst:79 +msgid "When the message appears, you have 30 days to act before the database expires. The countdown is updated every day." +msgstr "" + +#: ../../content/administration/on_premise.rst:82 +#: ../../content/administration/on_premise.rst:108 +msgid "To resolve the issue, either:" +msgstr "" + +#: ../../content/administration/on_premise.rst:84 +msgid "**Add more users** to your subscription by clicking the :guilabel:`Upgrade your subscription` link displayed in the message to validate the upsell quotation and pay for the extra users." +msgstr "" + +#: ../../content/administration/on_premise.rst:86 +msgid ":ref:`Deactivate users ` and **reject** the upsell quotation." +msgstr "" + +#: ../../content/administration/on_premise.rst:89 +msgid "If you are on a monthly subscription plan, the database will automatically update to reflect the added user(s). If you are on a yearly or multi-year plan, an expiration banner will appear in the database. You can create the upsell quotation by clicking the banner to update the subscription or `send a support ticket `_ to resolve the issue." +msgstr "" + +#: ../../content/administration/on_premise.rst:94 +msgid "Once your database has the correct number of users, the expiration message disappears automatically after a few days, when the next verification occurs." +msgstr "" + +#: ../../content/administration/on_premise.rst:98 +msgid "Database expired error" +msgstr "" + +#: ../../content/administration/on_premise.rst:100 +msgid "If your database expires before you renew your subscription, the following message should be displayed." +msgstr "" + +#: ../../content/administration/on_premise.rst:-1 +msgid "Database expired error message" +msgstr "" + +#: ../../content/administration/on_premise.rst:106 +msgid "This message appears if you fail to act before the end of the 30-day countdown." +msgstr "" + +#: ../../content/administration/on_premise.rst:110 +msgid "Click the :guilabel:`Renew your subscription` link displayed in the message and complete the process. If you pay by wire transfer, your subscription will be renewed when the payment arrives which can take a few days. Credit card payments are processed immediately." +msgstr "" + +#: ../../content/administration/on_premise.rst:113 +msgid "`Send a support ticket `_." +msgstr "" + +#: ../../content/administration/on_premise/community_to_enterprise.rst:6 +msgid "Switch from Community to Enterprise" +msgstr "" + +#: ../../content/administration/on_premise/community_to_enterprise.rst:8 +msgid "Depending on your current installation, there are multiple ways to upgrade your community version. In any case the basic guidelines are:" +msgstr "" + +#: ../../content/administration/on_premise/community_to_enterprise.rst:12 +#: ../../content/administration/on_premise/community_to_enterprise.rst:31 +#: ../../content/administration/on_premise/community_to_enterprise.rst:63 +#: ../../content/administration/on_premise/community_to_enterprise.rst:80 +msgid "Backup your community database" +msgstr "" + +#: ../../content/administration/on_premise/community_to_enterprise.rst:17 +#: ../../content/administration/on_premise/community_to_enterprise.rst:62 +msgid "Shutdown your server" +msgstr "" + +#: ../../content/administration/on_premise/community_to_enterprise.rst:19 +msgid "Install the web_enterprise module" +msgstr "" + +#: ../../content/administration/on_premise/community_to_enterprise.rst:21 +msgid "Restart your server" +msgstr "" + +#: ../../content/administration/on_premise/community_to_enterprise.rst:23 +msgid "Enter your Odoo Enterprise Subscription code" +msgstr "" + +#: ../../content/administration/on_premise/community_to_enterprise.rst:29 +msgid "On Linux, using an installer" +msgstr "" + +#: ../../content/administration/on_premise/community_to_enterprise.rst:33 +msgid "Stop the odoo service" +msgstr "" + +#: ../../content/administration/on_premise/community_to_enterprise.rst:39 +msgid "Install the enterprise .deb (it should install over the community package)" +msgstr "" + +#: ../../content/administration/on_premise/community_to_enterprise.rst:45 +msgid "Update your database to the enterprise packages using" +msgstr "" + +#: ../../content/administration/on_premise/community_to_enterprise.rst:51 +msgid "You should be able to connect to your Odoo Enterprise instance using your usual mean of identification. You can then link your database with your Odoo Enterprise Subscription by entering the code you received by e-mail in the form input" +msgstr "" + +#: ../../content/administration/on_premise/community_to_enterprise.rst:57 +msgid "On Linux, using the source code" +msgstr "" + +#: ../../content/administration/on_premise/community_to_enterprise.rst:59 +msgid "There are many ways to launch your server when using sources, and you probably have your own favourite. You may need to adapt sections to your usual workflow." +msgstr "" + +#: ../../content/administration/on_premise/community_to_enterprise.rst:64 +msgid "Update the ``--addons-path`` parameter of your launch command (see :doc:`../on_premise/source`)" +msgstr "" + +#: ../../content/administration/on_premise/community_to_enterprise.rst:65 +msgid "Install the web_enterprise module by using" +msgstr "" + +#: ../../content/administration/on_premise/community_to_enterprise.rst:71 +msgid "Depending on the size of your database, this may take some time." +msgstr "" + +#: ../../content/administration/on_premise/community_to_enterprise.rst:73 +msgid "Restart your server with the updated addons path of point 3. You should be able to connect to your instance. You can then link your database with your Odoo Enterprise Subscription by entering the code you received by e-mail in the form input" +msgstr "" + +#: ../../content/administration/on_premise/community_to_enterprise.rst:78 +msgid "On Windows" +msgstr "" + +#: ../../content/administration/on_premise/community_to_enterprise.rst:82 +msgid "Uninstall Odoo Community (using the Uninstall executable in the installation folder) - PostgreSQL will remain installed" +msgstr "" + +#: ../../content/administration/on_premise/community_to_enterprise.rst:88 +msgid "Launch the Odoo Enterprise Installer and follow the steps normally. When choosing the installation path, you can set the folder of the Community installation (this folder still contains the PostgreSQL installation). Uncheck ``Start Odoo`` at the end of the installation" +msgstr "" + +#: ../../content/administration/on_premise/community_to_enterprise.rst:96 +msgid "Using a command window, update your Odoo Database using this command (from the Odoo installation path, in the server subfolder)" +msgstr "" + +#: ../../content/administration/on_premise/community_to_enterprise.rst:103 +msgid "No need to manually launch the server, the service is running. You should be able to connect to your Odoo Enterprise instance using your usual mean of identification. You can then link your database with your Odoo Enterprise Subscription by entering the code you received by e-mail in the form input" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:3 +msgid "System configuration" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:5 +msgid "This document describes basic steps to set up Odoo in production or on an internet-facing server. It follows :doc:`installation <../on_premise>`, and is not generally necessary for a development systems that is not exposed on the internet." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:10 +msgid "If you are setting up a public server, be sure to check our :ref:`security` recommendations!" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:15 +msgid "dbfilter" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:17 +msgid "Odoo is a multi-tenant system: a single Odoo system may run and serve a number of database instances. It is also highly customizable, with customizations (starting from the modules being loaded) depending on the \"current database\"." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:21 +msgid "This is not an issue when working with the backend (web client) as a logged-in company user: the database can be selected when logging in, and customizations loaded afterwards." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:25 +msgid "However it is an issue for non-logged users (portal, website) which aren't bound to a database: Odoo needs to know which database should be used to load the website page or perform the operation. If multi-tenancy is not used that is not an issue, there's only one database to use, but if there are multiple databases accessible Odoo needs a rule to know which one it should use." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:31 +msgid "That is one of the purposes of :option:`--db-filter `: it specifies how the database should be selected based on the hostname (domain) that is being requested. The value is a `regular expression`_, possibly including the dynamically injected hostname (``%h``) or the first subdomain (``%d``) through which the system is being accessed." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:37 +msgid "For servers hosting multiple databases in production, especially if ``website`` is used, dbfilter **must** be set, otherwise a number of features will not work correctly." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:42 +msgid "Configuration samples" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:44 +msgid "Show only databases with names beginning with 'mycompany'" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:46 +#: ../../content/administration/on_premise/deploy.rst:58 +#: ../../content/administration/on_premise/deploy.rst:153 +#: ../../content/administration/on_premise/deploy.rst:280 +msgid "in :ref:`the configuration file ` set:" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:53 +msgid "Show only databases matching the first subdomain after ``www``: for example the database \"mycompany\" will be shown if the incoming request was sent to ``www.mycompany.com`` or ``mycompany.co.uk``, but not for ``www2.mycompany.com`` or ``helpdesk.mycompany.com``." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:67 +msgid "Setting a proper :option:`--db-filter ` is an important part of securing your deployment. Once it is correctly working and only matching a single database per hostname, it is strongly recommended to block access to the database manager screens, and to use the ``--no-database-list`` startup parameter to prevent listing your databases, and to block access to the database management screens. See also security_." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:76 +#: ../../content/administration/on_premise/source.rst:193 +msgid "PostgreSQL" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:78 +msgid "By default, PostgreSQL only allows connection over UNIX sockets and loopback connections (from \"localhost\", the same machine the PostgreSQL server is installed on)." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:82 +msgid "UNIX socket is fine if you want Odoo and PostgreSQL to execute on the same machine, and is the default when no host is provided, but if you want Odoo and PostgreSQL to execute on different machines [#different-machines]_ it will need to `listen to network interfaces`_ [#remote-socket]_, either:" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:87 +msgid "Only accept loopback connections and `use an SSH tunnel`_ between the machine on which Odoo runs and the one on which PostgreSQL runs, then configure Odoo to connect to its end of the tunnel" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:90 +msgid "Accept connections to the machine on which Odoo is installed, possibly over ssl (see `PostgreSQL connection settings`_ for details), then configure Odoo to connect over the network" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:95 +#: ../../content/administration/on_premise/deploy.rst:145 +#: ../../content/administration/on_premise/deploy.rst:235 +#: ../../content/administration/on_premise/deploy.rst:275 +msgid "Configuration sample" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:97 +msgid "Allow tcp connection on localhost" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:98 +msgid "Allow tcp connection from 192.168.1.x network" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:100 +msgid "in ``/etc/postgresql//main/pg_hba.conf`` set:" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:108 +msgid "in ``/etc/postgresql//main/postgresql.conf`` set:" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:119 +msgid "Configuring Odoo" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:121 +msgid "Out of the box, Odoo connects to a local postgres over UNIX socket via port 5432. This can be overridden using :ref:`the database options ` when your Postgres deployment is not local and/or does not use the installation defaults." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:126 +msgid "The :doc:`packaged installers ` will automatically create a new user (``odoo``) and set it as the database user." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:129 +msgid "The database management screens are protected by the ``admin_passwd`` setting. This setting can only be set using configuration files, and is simply checked before performing database alterations. It should be set to a randomly generated value to ensure third parties can not use this interface." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:134 +msgid "All database operations use the :ref:`database options `, including the database management screen. For the database management screen to work requires that the PostgreSQL user have ``createdb`` right." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:138 +msgid "Users can always drop databases they own. For the database management screen to be completely non-functional, the PostgreSQL user needs to be created with ``no-createdb`` and the database must be owned by a different PostgreSQL user." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:142 +msgid "the PostgreSQL user *must not* be a superuser" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:147 +msgid "connect to a PostgreSQL server on 192.168.1.2" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:148 +msgid "port 5432" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:149 +msgid "using an 'odoo' user account," +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:150 +msgid "with 'pwd' as a password" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:151 +msgid "filtering only db with a name beginning with 'mycompany'" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:168 +msgid "SSL Between Odoo and PostgreSQL" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:170 +msgid "Since Odoo 11.0, you can enforce ssl connection between Odoo and PostgreSQL. in Odoo the db_sslmode control the ssl security of the connection with value chosen out of 'disable', 'allow', 'prefer', 'require', 'verify-ca' or 'verify-full'" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:175 +msgid "`PostgreSQL Doc `_" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:180 +msgid "Builtin server" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:182 +msgid "Odoo includes built-in HTTP, cron, and live-chat servers, using either multi-threading or multi-processing." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:185 +msgid "The **multi-threaded** server is a simpler server primarily used for development, demonstrations, and its compatibility with various operating systems (including Windows). A new thread is spawned for every new HTTP request, even for long-lived connections such as websocket. Extra daemonic cron threads are spawned too. Due to a Python limitation (GIL), it doesn't make the best use of the hardware." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:191 +msgid "The multi-threaded server is the default server, also for docker containers. It is selected by leaving the :option:`--workers ` option out or setting it to ``0``." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:194 +msgid "The **multi-processing** server is a full-blown server primarily used for production. It is not liable to the same Python limitation (GIL) on resource usage and hence makes the best use of the hardware. A pool of workers is created upon server startup. New HTTP requests are queued by the OS until there are workers ready to process them. An extra event-driven HTTP worker for the live chat is spawned on an alternative port. Extra cron workers are spawned too. A configurable process reaper monitors resource usage and can kill/restart failed workers." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:201 +msgid "The multi-processing server is opt-in. It is selected by setting the :option:`--workers ` option to a non-null integer." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:205 +msgid "Because it is highly customized for Linux servers, the multi-processing server is not available on Windows." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:209 +msgid "Worker number calculation" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:211 +msgid "Rule of thumb : (#CPU * 2) + 1" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:212 +msgid "Cron workers need CPU" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:213 +msgid "1 worker ~= 6 concurrent users" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:216 +msgid "memory size calculation" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:218 +msgid "We consider 20% of the requests are heavy requests, while 80% are simpler ones" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:219 +msgid "A heavy worker, when all computed field are well designed, SQL requests are well designed, ... is estimated to consume around 1GB of RAM" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:220 +msgid "A lighter worker, in the same scenario, is estimated to consume around 150MB of RAM" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:222 +msgid "Needed RAM = #worker * ( (light_worker_ratio * light_worker_ram_estimation) + (heavy_worker_ratio * heavy_worker_ram_estimation) )" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:225 +#: ../../content/administration/on_premise/deploy.rst:413 +msgid "LiveChat" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:227 +msgid "In multi-processing, a dedicated LiveChat worker is automatically started and listens on the :option:`--gevent-port `. By default, the HTTP requests will keep accessing the normal HTTP workers instead of the LiveChat one. You must deploy a proxy in front of Odoo and redirect incoming requests whose path starts with ``/websocket/`` to the LiveChat worker. You must also start Odoo in :option:`--proxy-mode ` so it uses the real client headers (such as hostname, scheme, and IP) instead of the proxy ones." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:237 +msgid "Server with 4 CPU, 8 Thread" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:238 +msgid "60 concurrent users" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:240 +msgid "60 users / 6 = 10 <- theoretical number of worker needed" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:241 +msgid "(4 * 2) + 1 = 9 <- theoretical maximal number of worker" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:242 +msgid "We'll use 8 workers + 1 for cron. We'll also use a monitoring system to measure cpu load, and check if it's between 7 and 7.5 ." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:243 +msgid "RAM = 9 * ((0.8*150) + (0.2*1024)) ~= 3Go RAM for Odoo" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:245 +msgid "in :ref:`the configuration file `:" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:261 +msgid "HTTPS" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:263 +msgid "Whether it's accessed via website/web client or web service, Odoo transmits authentication information in cleartext. This means a secure deployment of Odoo must use HTTPS\\ [#switching]_. SSL termination can be implemented via just about any SSL termination proxy, but requires the following setup:" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:268 +msgid "Enable Odoo's :option:`proxy mode `. This should only be enabled when Odoo is behind a reverse proxy" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:269 +msgid "Set up the SSL termination proxy (`Nginx termination example`_)" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:270 +msgid "Set up the proxying itself (`Nginx proxying example`_)" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:271 +msgid "Your SSL termination proxy should also automatically redirect non-secure connections to the secure port" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:277 +msgid "Redirect http requests to https" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:278 +msgid "Proxy requests to odoo" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:286 +msgid "in ``/etc/nginx/sites-enabled/odoo.conf`` set:" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:362 +msgid "HTTPS Hardening" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:364 +msgid "Add the `Strict-Transport-Security` header to all requests, in order to prevent browsers from ever sending a plain HTTP request to this domain. You will need to maintain a working HTTPS service with a valid certificate on this domain at all times, otherwise your users will see security alerts or be entirely unable to access it." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:370 +msgid "Force HTTPS connections during a year for every visitor in NGINX with the line:" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:376 +msgid "Additional configuration can be defined for the `session_id` cookie. The `Secure` flag can be added to ensure it is never transmitted over HTTP and `SameSite=Lax` to prevent authenticated `CSRF`_." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:387 +msgid "Odoo as a WSGI Application" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:389 +msgid "It is also possible to mount Odoo as a standard WSGI_ application. Odoo provides the base for a WSGI launcher script as ``odoo-wsgi.example.py``. That script should be customized (possibly after copying it from the setup directory) to correctly set the configuration directly in :mod:`odoo.tools.config` rather than through the command-line or a configuration file." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:395 +msgid "However the WSGI server will only expose the main HTTP endpoint for the web client, website and webservice API. Because Odoo does not control the creation of workers anymore it can not setup cron or livechat workers" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:400 +msgid "Cron Workers" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:402 +msgid "Starting one of the built-in Odoo servers next to the WSGI server is required to process cron jobs. That server must be configured to only process crons and not HTTP requests using the :option:`--no-http ` cli option or the ``http_enable = False`` configuration file setting." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:407 +msgid "On Linux-like systems, using the multi-processing server over the multi-threading one is recommended to benefit from better hardware usage and increased stability, i.e., using the :option:`--workers=-1 ` and :option:`--max-cron-threads=n ` cli options." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:415 +msgid "Using a gevent-compatible WSGI server is required for the correct operation of the live chat feature. That server should be able to handle many simultaneous long-lived connections but doesn't need a lot of processing power. All requests whose path starts with ``/websocket/`` should be directed to that server. A regular (thread/process-based) WSGI server should be used for all other requests." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:421 +msgid "The Odoo cron server can also be used to serve the live chat requests. Just drop the :option:`--no-http ` cli option from the cron server and make sure requests whose path starts with ``/websocket/`` are directed to this server, either on the :option:`--http-port ` (multi-threading server) or on the :option:`--gevent-port ` (multi-processing server)." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:430 +msgid "Serving static files and attachments" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:432 +msgid "For development convenience, Odoo directly serves all static files and attachments in its modules. This may not be ideal when it comes to performances, and static files should generally be served by a static HTTP server." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:437 +msgid "Serving static files" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:439 +msgid "Odoo static files are located in each module's :file:`static/` folder, so static files can be served by intercepting all requests to :samp:`/{MODULE}/static/{FILE}`, and looking up the right module (and file) in the various addons paths." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:443 +msgid "It is recommended to set the ``Content-Security-Policy: default-src 'none'`` header on all images delivered by the web server. It is not strictly necessary as users cannot modify/inject content inside of modules' :file:`static/` folder and existing images are final (they do not fetch new resources by themselves). However, it is good practice." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:448 +msgid "Using the above NGINX (https) configuration, the following ``map`` and ``location`` blocks should be added to serve static files via NGINX." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:475 +msgid "The actual ``root`` and ``try_files`` directives are dependant on your installation, specifically on your :option:`--addons-path `." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:482 +msgid "Debian package" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:484 +msgid "Say Odoo has been installed via the **debian packages** for Community and Enterprise, and that the :option:`--addons-path ` is ``'/usr/lib/python3/dist-packages/odoo/addons'``." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:488 +#: ../../content/administration/on_premise/deploy.rst:502 +msgid "The ``root`` and ``try_files`` should be:" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:495 +msgid "Git sources" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:497 +msgid "Say Odoo has been installed via the **sources**, that both the Community and Enterprise git repositories were cloned in :file:`/opt/odoo/community` and :file:`/opt/odoo/enterprise` respectively, and that the :option:`--addons-path ` is ``'/opt/odoo/community/odoo/addons,/opt/odoo/community/addons,/opt/odoo/enterprise'``." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:510 +msgid "Serving attachments" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:512 +msgid "Attachments are files stored in the filestore which access is regulated by Odoo. They cannot be directly accessed via a static web server as accessing them requires multiple lookups in the database to determine where the files are stored and whether the current user can access them or not." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:517 +msgid "Nevertheless, once the file has been located and the access rights verified by Odoo, it is a good idea to serve the file using the static web server instead of Odoo. For Odoo to delegate serving files to the static web server, the `X-Sendfile `_ (apache) or `X-Accel `_ (nginx) extensions must be enabled and configured on the static web server. Once it is set up, start Odoo with the :option:`--x-sendfile ` CLI flag (this unique flag is used for both X-Sendfile and X-Accel)." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:527 +msgid "The X-Sendfile extension for apache (and compatible web servers) does not require any supplementary configuration." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:529 +msgid "The X-Accel extension for NGINX **does** require the following additionnal configuration:" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:538 +msgid "In case you don't know what is the path to your filestore, start Odoo with the :option:`--x-sendfile ` option and navigate to the ``/web/filestore`` URL directly via Odoo (don't navigate to the URL via NGINX). This logs a warnings, the message contains the configuration you need." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:547 +msgid "Security" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:549 +msgid "For starters, keep in mind that securing an information system is a continuous process, not a one-shot operation. At any moment, you will only be as secure as the weakest link in your environment." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:553 +msgid "So please do not take this section as the ultimate list of measures that will prevent all security problems. It's only intended as a summary of the first important things you should be sure to include in your security action plan. The rest will come from best security practices for your operating system and distribution, best practices in terms of users, passwords, and access control management, etc." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:559 +msgid "When deploying an internet-facing server, please be sure to consider the following security-related topics:" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:562 +msgid "Always set a strong super-admin admin password, and restrict access to the database management pages as soon as the system is set up. See :ref:`db_manager_security`." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:565 +msgid "Choose unique logins and strong passwords for all administrator accounts on all databases. Do not use 'admin' as the login. Do not use those logins for day-to-day operations, only for controlling/managing the installation. *Never* use any default passwords like admin/admin, even for test/staging databases." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:570 +msgid "Do **not** install demo data on internet-facing servers. Databases with demo data contain default logins and passwords that can be used to get into your systems and cause significant trouble, even on staging/dev systems." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:574 +msgid "Use appropriate database filters ( :option:`--db-filter `) to restrict the visibility of your databases according to the hostname. See :ref:`db_filter`. You may also use :option:`-d ` to provide your own (comma-separated) list of available databases to filter from, instead of letting the system fetch them all from the database backend." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:581 +msgid "Once your ``db_name`` and ``db_filter`` are configured and only match a single database per hostname, you should set ``list_db`` configuration option to ``False``, to prevent listing databases entirely, and to block access to the database management screens (this is also exposed as the :option:`--no-database-list ` command-line option)" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:587 +msgid "Make sure the PostgreSQL user (:option:`--db_user `) is *not* a super-user, and that your databases are owned by a different user. For example they could be owned by the ``postgres`` super-user if you are using a dedicated non-privileged ``db_user``. See also :ref:`setup/deploy/odoo`." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:592 +msgid "Keep installations updated by regularly installing the latest builds, either via GitHub or by downloading the latest version from https://www.odoo.com/page/download or http://nightly.odoo.com" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:596 +msgid "Configure your server in multi-process mode with proper limits matching your typical usage (memory/CPU/timeouts). See also :ref:`builtin_server`." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:599 +msgid "Run Odoo behind a web server providing HTTPS termination with a valid SSL certificate, in order to prevent eavesdropping on cleartext communications. SSL certificates are cheap, and many free options exist. Configure the web proxy to limit the size of requests, set appropriate timeouts, and then enable the :option:`proxy mode ` option. See also :ref:`https_proxy`." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:606 +msgid "If you need to allow remote SSH access to your servers, make sure to set a strong password for **all** accounts, not just `root`. It is strongly recommended to entirely disable password-based authentication, and only allow public key authentication. Also consider restricting access via a VPN, allowing only trusted IPs in the firewall, and/or running a brute-force detection system such as `fail2ban` or equivalent." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:612 +msgid "Consider installing appropriate rate-limiting on your proxy or firewall, to prevent brute-force attacks and denial of service attacks. See also :ref:`login_brute_force` for specific measures." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:616 +msgid "Many network providers provide automatic mitigation for Distributed Denial of Service attacks (DDOS), but this is often an optional service, so you should consult with them." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:620 +msgid "Whenever possible, host your public-facing demo/test/staging instances on different machines than the production ones. And apply the same security precautions as for production." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:624 +msgid "If your public-facing Odoo server has access to sensitive internal network resources or services (e.g. via a private VLAN), implement appropriate firewall rules to protect those internal resources. This will ensure that the Odoo server cannot be used accidentally (or as a result of malicious user actions) to access or disrupt those internal resources. Typically this can be done by applying an outbound default DENY rule on the firewall, then only explicitly authorizing access to internal resources that the Odoo server needs to access. `Systemd IP traffic access control `_ may also be useful to implement per-process network access control." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:635 +msgid "If your public-facing Odoo server is behind a Web Application Firewall, a load-balancer, a transparent DDoS protection service (like CloudFlare) or a similar network-level device, you may wish to avoid direct access to the Odoo system. It is generally difficult to keep the endpoint IP addresses of your Odoo servers secret. For example they can appear in web server logs when querying public systems, or in the headers of emails posted from Odoo. In such a situation you may want to configure your firewall so that the endpoints are not accessible publicly except from the specific IP addresses of your WAF, load-balancer or proxy service. Service providers like CloudFlare usually maintain a public list of their IP address ranges for this purpose." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:646 +msgid "If you are hosting multiple customers, isolate customer data and files from each other using containers or appropriate \"jail\" techniques." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:649 +msgid "Setup daily backups of your databases and filestore data, and copy them to a remote archiving server that is not accessible from the server itself." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:652 +msgid "Deploying Odoo on Linux is strongly recommended over Windows. Should you choose nevertheless to deploy on a Windows platform, a thorough security hardening review of the server should be conducted and is outside of the scope of this guide." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:660 +msgid "Blocking Brute Force Attacks" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:662 +msgid "For internet-facing deployments, brute force attacks on user passwords are very common, and this threat should not be neglected for Odoo servers. Odoo emits a log entry whenever a login attempt is performed, and reports the result: success or failure, along with the target login and source IP." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:666 +msgid "The log entries will have the following form." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:668 +msgid "Failed login::" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:672 +msgid "Successful login::" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:677 +msgid "These logs can be easily analyzed by an intrusion prevention system such as `fail2ban`." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:679 +msgid "For example, the following fail2ban filter definition should match a failed login::" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:686 +msgid "This could be used with a jail definition to block the attacking IP on HTTP(S)." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:688 +msgid "Here is what it could look like for blocking the IP for 15 minutes when 10 failed login attempts are detected from the same IP within 1 minute::" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:702 +msgid "Database Manager Security" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:704 +msgid ":ref:`setup/deploy/odoo` mentioned ``admin_passwd`` in passing." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:706 +msgid "This setting is used on all database management screens (to create, delete, dump or restore databases)." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:709 +msgid "If the management screens must not be accessible at all, you should set ``list_db`` configuration option to ``False``, to block access to all the database selection and management screens." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:715 +msgid "It is strongly recommended to disable the Database Manager for any internet-facing system! It is meant as a development/demo tool, to make it easy to quickly create and manage databases. It is not designed for use in production, and may even expose dangerous features to attackers. It is also not designed to handle large databases, and may trigger memory limits." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:721 +msgid "On production systems, database management operations should always be performed by the system administrator, including provisioning of new databases and automated backups." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:724 +msgid "Be sure to setup an appropriate ``db_name`` parameter (and optionally, ``db_filter`` too) so that the system can determine the target database for each request, otherwise users will be blocked as they won't be allowed to choose the database themselves." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:729 +msgid "If the management screens must only be accessible from a selected set of machines, use the proxy server's features to block access to all routes starting with ``/web/database`` except (maybe) ``/web/database/selector`` which displays the database-selection screen." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:733 +msgid "If the database-management screen should be left accessible, the ``admin_passwd`` setting must be changed from its ``admin`` default: this password is checked before allowing database-alteration operations." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:737 +msgid "It should be stored securely, and should be generated randomly e.g." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:743 +msgid "which will generate a 32 characters pseudorandom printable string." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:746 +msgid "Supported Browsers" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:748 +msgid "Odoo supports all the major desktop and mobile browsers available on the market, as long as they are supported by their publishers." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:751 +msgid "Here are the supported browsers:" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:753 +msgid "Google Chrome" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:754 +msgid "Mozilla Firefox" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:755 +msgid "Microsoft Edge" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:756 +msgid "Apple Safari" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:758 +msgid "Please make sure your browser is up-to-date and still supported by its publisher before filing a bug report." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:763 +msgid "Since Odoo 13.0, ES6 is supported. Therefore, IE support is dropped." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:766 +msgid "to have multiple Odoo installations use the same PostgreSQL database, or to provide more computing resources to both software." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:769 +msgid "technically a tool like socat_ can be used to proxy UNIX sockets across networks, but that is mostly for software which can only be used over UNIX sockets" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:773 +msgid "or be accessible only over an internal packet-switched network, but that requires secured switches, protections against `ARP spoofing`_ and precludes usage of WiFi. Even over secure packet-switched networks, deployment over HTTPS is recommended, and possible costs are lowered as \"self-signed\" certificates are easier to deploy on a controlled environment than over the internet." +msgstr "" + +#: ../../content/administration/on_premise/email_gateway.rst:3 +msgid "Email gateway" +msgstr "" + +#: ../../content/administration/on_premise/email_gateway.rst:5 +msgid "The Odoo mail gateway allows you to inject directly all the received emails in Odoo." +msgstr "" + +#: ../../content/administration/on_premise/email_gateway.rst:7 +msgid "Its principle is straightforward: your SMTP server executes the \"mailgate\" script for every new incoming email." +msgstr "" + +#: ../../content/administration/on_premise/email_gateway.rst:10 +msgid "The script takes care of connecting to your Odoo database through XML-RPC, and send the emails via the `MailThread.message_process()` feature." +msgstr "" + +#: ../../content/administration/on_premise/email_gateway.rst:14 +msgid "Prerequisites" +msgstr "" + +#: ../../content/administration/on_premise/email_gateway.rst:16 +msgid "Administrator access to the Odoo database." +msgstr "" + +#: ../../content/administration/on_premise/email_gateway.rst:17 +msgid "Your own mail server such as Postfix or Exim." +msgstr "" + +#: ../../content/administration/on_premise/email_gateway.rst:18 +msgid "Technical knowledge on how to configure an email server." +msgstr "" + +#: ../../content/administration/on_premise/email_gateway.rst:21 +msgid "For Postfix" +msgstr "" + +#: ../../content/administration/on_premise/email_gateway.rst:23 +msgid "In you alias config (:file:`/etc/aliases`):" +msgstr "" + +#: ../../content/administration/on_premise/email_gateway.rst:30 +#: ../../content/administration/on_premise/email_gateway.rst:45 +msgid "Resources" +msgstr "" + +#: ../../content/administration/on_premise/email_gateway.rst:32 +msgid "`Postfix `_" +msgstr "" + +#: ../../content/administration/on_premise/email_gateway.rst:33 +msgid "`Postfix aliases `_" +msgstr "" + +#: ../../content/administration/on_premise/email_gateway.rst:34 +msgid "`Postfix virtual `_" +msgstr "" + +#: ../../content/administration/on_premise/email_gateway.rst:38 +msgid "For Exim" +msgstr "" + +#: ../../content/administration/on_premise/email_gateway.rst:47 +msgid "`Exim `_" +msgstr "" + +#: ../../content/administration/on_premise/email_gateway.rst:50 +msgid "If you don't have access/manage your email server, use :ref:`inbound messages `." +msgstr "" + +#: ../../content/administration/on_premise/geo_ip.rst:3 +msgid "Geo IP" +msgstr "" + +#: ../../content/administration/on_premise/geo_ip.rst:6 +msgid "This documentation only applies to On-premise databases." +msgstr "" + +#: ../../content/administration/on_premise/geo_ip.rst:11 +msgid "Download both the GeoLite2 City and Country `databases `_. You should end up with two files called :file:`GeoLite2-City.mmdb` and :file:`GeoLite2-Country.mmdb`." +msgstr "" + +#: ../../content/administration/on_premise/geo_ip.rst:15 +msgid "Move the files to the folder :file:`/usr/share/GeoIP/`." +msgstr "" + +#: ../../content/administration/on_premise/geo_ip.rst:22 +msgid "Restart the server" +msgstr "" + +#: ../../content/administration/on_premise/geo_ip.rst:25 +msgid "If you don't want to locate the geoip database in :file:`/usr/share/GeoIP/`, use the :option:`--geoip-city-db ` and :option:`--geoip-country-db ` options of the Odoo command line interface. These options take the absolute path to the GeoIP database file and use it as the GeoIP database. For example:" +msgstr "" + +#: ../../content/administration/on_premise/geo_ip.rst:36 +msgid ":doc:`CLI documentation `." +msgstr "" + +#: ../../content/administration/on_premise/geo_ip.rst:39 +msgid "Test GeoIP geolocation in your Odoo website" +msgstr "" + +#: ../../content/administration/on_premise/geo_ip.rst:41 +msgid "Edit a web page to include some geo-ip information such as the country name of the current request IP address. To do so:" +msgstr "" + +#: ../../content/administration/on_premise/geo_ip.rst:44 +msgid "Go to your website. Open the web page that you want to test ``GeoIP``." +msgstr "" + +#: ../../content/administration/on_premise/geo_ip.rst:45 +msgid "Choose :menuselection:`Customize --> HTML/CSS/JS Editor`." +msgstr "" + +#: ../../content/administration/on_premise/geo_ip.rst:46 +msgid "Add the following piece of XML in the page :" +msgstr "" + +#: ../../content/administration/on_premise/geo_ip.rst:52 +msgid "Save and refresh the page." +msgstr "" + +#: ../../content/administration/on_premise/geo_ip.rst:54 +msgid "Geo-ip is working if you read your country name displayed in bold in the middle of the page." +msgstr "" + +#: ../../content/administration/on_premise/geo_ip.rst:56 +msgid "In case you read \"**geoip failure**\" instead then the geolocalization failed. The common causes are:" +msgstr "" + +#: ../../content/administration/on_premise/geo_ip.rst:58 +msgid "The browsing IP address is the localhost (``127.0.0.1``) or a local area network one. If you don't know, you can access your website using mobile data." +msgstr "" + +#: ../../content/administration/on_premise/geo_ip.rst:60 +msgid "You are using a reverse-proxy (apache, nginx) in front of Odoo but didn't start Odoo with the proxy-mode enabled. See :option:`proxy mode `." +msgstr "" + +#: ../../content/administration/on_premise/geo_ip.rst:62 +msgid "The GeoIP database is corrupt, missing or unaccessible. In such case a warning was logged in the server logs." +msgstr "" + +#: ../../content/administration/on_premise/packages.rst:3 +msgid "Packaged installers" +msgstr "" + +#: ../../content/administration/on_premise/packages.rst:5 +msgid "Odoo provides packaged installers for Debian-based Linux distributions (Debian, Ubuntu, etc.), RPM-based Linux distributions (Fedora, CentOS, RHEL, etc.), and Windows for the Community and Enterprise editions." +msgstr "" + +#: ../../content/administration/on_premise/packages.rst:9 +msgid "Official **Community** nightly packages with all relevant dependency requirements are available on the `nightly server `_." +msgstr "" + +#: ../../content/administration/on_premise/packages.rst:13 +msgid "Nightly packages may be difficult to keep up to date." +msgstr "" + +#: ../../content/administration/on_premise/packages.rst:15 +msgid "Official **Community** and **Enterprise** packages can be downloaded from the `Odoo download page `_." +msgstr "" + +#: ../../content/administration/on_premise/packages.rst:19 +msgid "It is required to be logged in as a paying on-premise customer or partner to download the Enterprise packages." +msgstr "" + +#: ../../content/administration/on_premise/packages.rst:25 +#: ../../content/administration/on_premise/source.rst:52 +#: ../../content/administration/on_premise/source.rst:129 +#: ../../content/administration/on_premise/source.rst:152 +#: ../../content/administration/on_premise/source.rst:174 +#: ../../content/administration/on_premise/source.rst:199 +#: ../../content/administration/on_premise/source.rst:228 +#: ../../content/administration/on_premise/source.rst:271 +#: ../../content/administration/on_premise/source.rst:384 +#: ../../content/administration/on_premise/source.rst:446 +msgid "Linux" +msgstr "" + +#: ../../content/administration/on_premise/packages.rst:28 +#: ../../content/administration/on_premise/source.rst:116 +msgid "Prepare" +msgstr "" + +#: ../../content/administration/on_premise/packages.rst:30 +msgid "Odoo needs a `PostgreSQL `_ server to run properly." +msgstr "" + +#: ../../content/administration/on_premise/packages.rst:34 +#: ../../content/administration/on_premise/packages.rst:70 +#: ../../content/administration/on_premise/packages.rst:100 +#: ../../content/administration/on_premise/source.rst:278 +msgid "Debian/Ubuntu" +msgstr "" + +#: ../../content/administration/on_premise/packages.rst:36 +msgid "The default configuration for the Odoo 'deb' package is to use the PostgreSQL server on the same host as the Odoo instance. Execute the following command to install the PostgreSQL server:" +msgstr "" + +#: ../../content/administration/on_premise/packages.rst:44 +#: ../../content/administration/on_premise/packages.rst:80 +#: ../../content/administration/on_premise/packages.rst:132 +msgid "Fedora" +msgstr "" + +#: ../../content/administration/on_premise/packages.rst:46 +msgid "Make sure that the `sudo` command is available and well configured and, only then, execute the following command to install the PostgreSQL server:" +msgstr "" + +#: ../../content/administration/on_premise/packages.rst:57 +#: ../../content/administration/on_premise/source.rst:416 +msgid "`wkhtmltopdf` is not installed through **pip** and must be installed manually in `version 0.12.6 `_ for it to support headers and footers. Check out the `wkhtmltopdf wiki `_ for more details on the various versions." +msgstr "" + +#: ../../content/administration/on_premise/packages.rst:63 +msgid "Repository" +msgstr "" + +#: ../../content/administration/on_premise/packages.rst:65 +msgid "Odoo S.A. provides a repository that can be used to install the **Community** edition by executing the following commands:" +msgstr "" + +#: ../../content/administration/on_premise/packages.rst:78 +msgid "Use the usual `apt-get upgrade` command to keep the installation up-to-date." +msgstr "" + +#: ../../content/administration/on_premise/packages.rst:90 +msgid "Currently, there is no nightly repository for the Enterprise edition." +msgstr "" + +#: ../../content/administration/on_premise/packages.rst:93 +msgid "Distribution package" +msgstr "" + +#: ../../content/administration/on_premise/packages.rst:95 +msgid "Instead of using the repository, packages for both the **Community** and **Enterprise** editions can be downloaded from the `Odoo download page `_." +msgstr "" + +#: ../../content/administration/on_premise/packages.rst:103 +msgid "Odoo 17 'deb' package currently supports `Debian Buster `_ and `Ubuntu 18.04 `_ or above." +msgstr "" + +#: ../../content/administration/on_premise/packages.rst:107 +msgid "Once downloaded, execute the following commands **as root** to install Odoo as a service, create the necessary PostgreSQL user, and automatically start the server:" +msgstr "" + +#: ../../content/administration/on_premise/packages.rst:117 +msgid "The `python3-xlwt` Debian package, needed to export into the XLS format, does not exist in Debian Buster nor Ubuntu 18.04. If needed, install it manually with the following:" +msgstr "" + +#: ../../content/administration/on_premise/packages.rst:124 +msgid "The `num2words` Python package - needed to render textual amounts - does not exist in Debian Buster nor Ubuntu 18.04, which could cause problems with the `l10n_mx_edi` module. If needed, install it manually with the following:" +msgstr "" + +#: ../../content/administration/on_premise/packages.rst:135 +msgid "Odoo 17 'rpm' package supports Fedora 36." +msgstr "" + +#: ../../content/administration/on_premise/packages.rst:137 +msgid "Once downloaded, the package can be installed using the 'dnf' package manager:" +msgstr "" + +#: ../../content/administration/on_premise/packages.rst:148 +#: ../../content/administration/on_premise/source.rst:70 +#: ../../content/administration/on_premise/source.rst:133 +#: ../../content/administration/on_premise/source.rst:158 +#: ../../content/administration/on_premise/source.rst:180 +#: ../../content/administration/on_premise/source.rst:208 +#: ../../content/administration/on_premise/source.rst:239 +#: ../../content/administration/on_premise/source.rst:324 +#: ../../content/administration/on_premise/source.rst:393 +#: ../../content/administration/on_premise/source.rst:456 +msgid "Windows" +msgstr "" + +#: ../../content/administration/on_premise/packages.rst:151 +msgid "Windows packaging is offered for the convenience of testing or running single-user local instances but production deployment is discouraged due to a number of limitations and risks associated with deploying Odoo on a Windows platform." +msgstr "" + +#: ../../content/administration/on_premise/packages.rst:155 +msgid "Download the installer from the `nightly server `_ (Community only) or the Windows installer from the `Odoo download page `_ (any edition." +msgstr "" + +#: ../../content/administration/on_premise/packages.rst:158 +msgid "Execute the downloaded file." +msgstr "" + +#: ../../content/administration/on_premise/packages.rst:161 +msgid "On Windows 8 and later, a warning titled *Windows protected your PC* may be displayed. Click **More Info** and then **Run anyway** to proceed." +msgstr "" + +#: ../../content/administration/on_premise/packages.rst:164 +msgid "Accept the `UAC `_ prompt." +msgstr "" + +#: ../../content/administration/on_premise/packages.rst:165 +msgid "Go through the installation steps." +msgstr "" + +#: ../../content/administration/on_premise/packages.rst:167 +msgid "Odoo launches automatically at the end of the installation." +msgstr "" + +#: ../../content/administration/on_premise/source.rst:3 +msgid "Source install" +msgstr "" + +#: ../../content/administration/on_premise/source.rst:5 +msgid "The source 'installation' is not about installing Odoo but running it directly from the source instead." +msgstr "" + +#: ../../content/administration/on_premise/source.rst:8 +msgid "Using the Odoo source can be more convenient for module developers as it is more easily accessible than using packaged installers." +msgstr "" + +#: ../../content/administration/on_premise/source.rst:11 +msgid "It makes starting and stopping Odoo more flexible and explicit than the services set up by the packaged installers. Also, it allows overriding settings using :ref:`command-line parameters ` without needing to edit a configuration file." +msgstr "" + +#: ../../content/administration/on_premise/source.rst:15 +msgid "Finally, it provides greater control over the system's setup and allows to more easily keep (and run) multiple versions of Odoo side-by-side." +msgstr "" + +#: ../../content/administration/on_premise/source.rst:19 +msgid "Fetch the sources" +msgstr "" + +#: ../../content/administration/on_premise/source.rst:21 +msgid "There are two ways to obtain the source code of Odoo: as a ZIP **archive** or through **Git**." +msgstr "" + +#: ../../content/administration/on_premise/source.rst:24 +msgid "Archive" +msgstr "" + +#: ../../content/administration/on_premise/source.rst:26 +msgid "Community edition:" +msgstr "" + +#: ../../content/administration/on_premise/source.rst:28 +#: ../../content/administration/on_premise/source.rst:34 +msgid "`Odoo download page `_" +msgstr "" + +#: ../../content/administration/on_premise/source.rst:29 +msgid "`GitHub Community repository `_" +msgstr "" + +#: ../../content/administration/on_premise/source.rst:30 +msgid "`Nightly server `_" +msgstr "" + +#: ../../content/administration/on_premise/source.rst:32 +msgid "Enterprise edition:" +msgstr "" + +#: ../../content/administration/on_premise/source.rst:35 +msgid "`GitHub Enterprise repository `_" +msgstr "" + +#: ../../content/administration/on_premise/source.rst:40 +msgid "Git" +msgstr "" + +#: ../../content/administration/on_premise/source.rst:43 +msgid "It is required to have `Git `_ installed, and it is recommended to have a basic knowledge of Git commands to proceed." +msgstr "" + +#: ../../content/administration/on_premise/source.rst:46 +msgid "To clone a Git repository, choose between cloning with HTTPS or SSH. In most cases, the best option is HTTPS. However, choose SSH to contribute to Odoo source code or when following the :doc:`Getting Started developer tutorial `." +msgstr "" + +#: ../../content/administration/on_premise/source.rst:56 +#: ../../content/administration/on_premise/source.rst:74 +#: ../../content/administration/on_premise/source.rst:92 +msgid "Clone with HTTPS" +msgstr "" + +#: ../../content/administration/on_premise/source.rst:63 +#: ../../content/administration/on_premise/source.rst:81 +#: ../../content/administration/on_premise/source.rst:99 +msgid "Clone with SSH" +msgstr "" + +#: ../../content/administration/on_premise/source.rst:88 +#: ../../content/administration/on_premise/source.rst:141 +#: ../../content/administration/on_premise/source.rst:164 +#: ../../content/administration/on_premise/source.rst:186 +#: ../../content/administration/on_premise/source.rst:213 +#: ../../content/administration/on_premise/source.rst:253 +#: ../../content/administration/on_premise/source.rst:347 +#: ../../content/administration/on_premise/source.rst:405 +#: ../../content/administration/on_premise/source.rst:467 +msgid "Mac OS" +msgstr "" + +#: ../../content/administration/on_premise/source.rst:107 +msgid "**The Enterprise git repository does not contain the full Odoo source code**. It is only a collection of extra add-ons. The main server code is in the Community edition. Running the Enterprise version means running the server from the Community version with the `addons-path` option set to the folder with the Enterprise edition. It is required to clone both the Community and Enterprise repositories to have a working Odoo Enterprise installation." +msgstr "" + +#: ../../content/administration/on_premise/source.rst:119 +msgid "Python" +msgstr "" + +#: ../../content/administration/on_premise/source.rst:121 +msgid "Odoo requires **Python 3.10** or later to run." +msgstr "" + +#: ../../content/administration/on_premise/source.rst:123 +msgid "Minimum requirement updated from Python 3.7 to Python 3.10." +msgstr "" + +#: ../../content/administration/on_premise/source.rst:131 +msgid "Use a package manager to download and install Python 3 if needed." +msgstr "" + +#: ../../content/administration/on_premise/source.rst:135 +msgid "`Download the latest version of Python 3 `_ and install it." +msgstr "" + +#: ../../content/administration/on_premise/source.rst:138 +msgid "During installation, check **Add Python 3 to PATH**, then click **Customize Installation** and make sure that **pip** is checked." +msgstr "" + +#: ../../content/administration/on_premise/source.rst:143 +msgid "Use a package manager (`Homebrew `_, `MacPorts `_) to download and install Python 3 if needed." +msgstr "" + +#: ../../content/administration/on_premise/source.rst:147 +msgid "If Python 3 is already installed, make sure that the version is 3.7 or above, as previous versions are not compatible with Odoo." +msgstr "" + +#: ../../content/administration/on_premise/source.rst:170 +msgid "Verify that `pip `_ is also installed for this version." +msgstr "" + +#: ../../content/administration/on_premise/source.rst:195 +msgid "Odoo uses PostgreSQL as its database management system." +msgstr "" + +#: ../../content/administration/on_premise/source.rst:201 +msgid "Use a package manager to download and install PostgreSQL (supported versions: 12.0 or above). It can be achieved by executing the following:" +msgstr "" + +#: ../../content/administration/on_premise/source.rst:210 +msgid "`Download PostgreSQL `_ (supported versions: 12.0 or above) and install it." +msgstr "" + +#: ../../content/administration/on_premise/source.rst:215 +msgid "Use `Postgres.app `_ to download and install PostgreSQL (supported version: 12.0 or above)." +msgstr "" + +#: ../../content/administration/on_premise/source.rst:219 +msgid "To make the command line tools bundled with Postgres.app available, make sure to set up the `$PATH` variable by following the `Postgres.app CLI tools instructions `_." +msgstr "" + +#: ../../content/administration/on_premise/source.rst:223 +msgid "By default, the only user is `postgres`. As Odoo forbids connecting as `postgres`, create a new PostgreSQL user." +msgstr "" + +#: ../../content/administration/on_premise/source.rst:236 +#: ../../content/administration/on_premise/source.rst:261 +msgid "Because the PostgreSQL user has the same name as the Unix login, it is possible to connect to the database without a password." +msgstr "" + +#: ../../content/administration/on_premise/source.rst:241 +msgid "Add PostgreSQL's `bin` directory (by default: :file:`C:\\\\Program Files\\\\PostgreSQL\\\\\\\\bin`) to the `PATH`." +msgstr "" + +#: ../../content/administration/on_premise/source.rst:243 +msgid "Create a postgres user with a password using the pg admin gui:" +msgstr "" + +#: ../../content/administration/on_premise/source.rst:245 +msgid "Open **pgAdmin**." +msgstr "" + +#: ../../content/administration/on_premise/source.rst:246 +msgid "Double-click the server to create a connection." +msgstr "" + +#: ../../content/administration/on_premise/source.rst:247 +msgid "Select :menuselection:`Object --> Create --> Login/Group Role`." +msgstr "" + +#: ../../content/administration/on_premise/source.rst:248 +msgid "Enter the username in the **Role Name** field (e.g., `odoo`)." +msgstr "" + +#: ../../content/administration/on_premise/source.rst:249 +msgid "Open the **Definition** tab, enter a password (e.g., `odoo`), and click **Save**." +msgstr "" + +#: ../../content/administration/on_premise/source.rst:250 +msgid "Open the **Privileges** tab and switch **Can login?** to `Yes` and **Create database?** to `Yes`." +msgstr "" + +#: ../../content/administration/on_premise/source.rst:267 +msgid "Dependencies" +msgstr "" + +#: ../../content/administration/on_premise/source.rst:273 +msgid "Using **distribution packages** is the preferred way of installing dependencies. Alternatively, install the Python dependencies with **pip**." +msgstr "" + +#: ../../content/administration/on_premise/source.rst:280 +msgid "For Debian-based systems, the packages are listed in the `debian/control `_ file of the Odoo sources." +msgstr "" + +#: ../../content/administration/on_premise/source.rst:283 +msgid "On Debian/Ubuntu, the following commands should install the required packages:" +msgstr "" + +#: ../../content/administration/on_premise/source.rst:290 +msgid "Install with pip" +msgstr "" + +#: ../../content/administration/on_premise/source.rst:292 +msgid "As some of the Python packages need a compilation step, they require system libraries to be installed." +msgstr "" + +#: ../../content/administration/on_premise/source.rst:295 +msgid "On Debian/Ubuntu, the following command should install these required libraries:" +msgstr "" + +#: ../../content/administration/on_premise/source.rst:301 +msgid "Odoo dependencies are listed in the :file:`requirements.txt` file located at the root of the Odoo Community directory." +msgstr "" + +#: ../../content/administration/on_premise/source.rst:305 +msgid "The Python packages in :file:`requirements.txt` are based on their stable/LTS Debian/Ubuntu corresponding version at the moment of the Odoo release. For example, for Odoo 15.0, the `python3-babel` package version is 2.8.0 in Debian Bullseye and 2.6.0 in Ubuntu Focal. The lowest version is then chosen in the :file:`requirements.txt`." +msgstr "" + +#: ../../content/administration/on_premise/source.rst:312 +#: ../../content/administration/on_premise/source.rst:334 +#: ../../content/administration/on_premise/source.rst:353 +msgid "It can be preferable not to mix Python module packages between different instances of Odoo or with the system. However, it is possible to use `virtualenv `_ to create isolated Python environments." +msgstr "" + +#: ../../content/administration/on_premise/source.rst:316 +msgid "Navigate to the path of the Odoo Community installation (:file:`CommunityPath`) and run **pip** on the requirements file to install the requirements for the current user." +msgstr "" + +#: ../../content/administration/on_premise/source.rst:326 +msgid "Before installing the dependencies, download and install the `Build Tools for Visual Studio `_. Select **C++ build tools** in the **Workloads** tab and install them when prompted." +msgstr "" + +#: ../../content/administration/on_premise/source.rst:330 +#: ../../content/administration/on_premise/source.rst:349 +msgid "Odoo dependencies are listed in the `requirements.txt` file located at the root of the Odoo Community directory." +msgstr "" + +#: ../../content/administration/on_premise/source.rst:338 +msgid "Navigate to the path of the Odoo Community installation (`CommunityPath`) and run **pip** on the requirements file in a terminal **with Administrator privileges**:" +msgstr "" + +#: ../../content/administration/on_premise/source.rst:357 +msgid "Navigate to the path of the Odoo Community installation (`CommunityPath`) and run **pip** on the requirements file:" +msgstr "" + +#: ../../content/administration/on_premise/source.rst:367 +msgid "Non-Python dependencies must be installed with a package manager (`Homebrew `_, `MacPorts `_)." +msgstr "" + +#: ../../content/administration/on_premise/source.rst:370 +msgid "Download and install the **Command Line Tools**:" +msgstr "" + +#: ../../content/administration/on_premise/source.rst:376 +msgid "Use the package manager to install non-Python dependencies." +msgstr "" + +#: ../../content/administration/on_premise/source.rst:379 +msgid "For languages using a **right-to-left interface** (such as Arabic or Hebrew), the `rtlcss` package is required." +msgstr "" + +#: ../../content/administration/on_premise/source.rst:386 +msgid "Download and install **nodejs** and **npm** with a package manager." +msgstr "" + +#: ../../content/administration/on_premise/source.rst:387 +#: ../../content/administration/on_premise/source.rst:396 +#: ../../content/administration/on_premise/source.rst:409 +msgid "Install `rtlcss`:" +msgstr "" + +#: ../../content/administration/on_premise/source.rst:395 +msgid "Download and install `nodejs `_." +msgstr "" + +#: ../../content/administration/on_premise/source.rst:402 +msgid "Edit the system environment's variable `PATH` to add the folder where `rtlcss.cmd` is located (typically: :file:`C:\\\\Users\\\\\\\\AppData\\\\Roaming\\\\npm\\\\`)." +msgstr "" + +#: ../../content/administration/on_premise/source.rst:407 +msgid "Download and install **nodejs** with a package manager (`Homebrew `_, `MacPorts `_)." +msgstr "" + +#: ../../content/administration/on_premise/source.rst:424 +msgid "Running Odoo" +msgstr "" + +#: ../../content/administration/on_premise/source.rst:426 +msgid "Once all dependencies are set up, Odoo can be launched by running `odoo-bin`, the command-line interface of the server. It is located at the root of the Odoo Community directory." +msgstr "" + +#: ../../content/administration/on_premise/source.rst:429 +msgid "To configure the server, either specify :ref:`command-line arguments ` or a :ref:`configuration file `." +msgstr "" + +#: ../../content/administration/on_premise/source.rst:433 +msgid "For the Enterprise edition, add the path to the `enterprise` add-ons to the `addons-path` argument. Note that it must come before the other paths in `addons-path` for add-ons to be loaded correctly." +msgstr "" + +#: ../../content/administration/on_premise/source.rst:437 +msgid "Common necessary configurations are:" +msgstr "" + +#: ../../content/administration/on_premise/source.rst:439 +msgid "PostgreSQL user and password." +msgstr "" + +#: ../../content/administration/on_premise/source.rst:440 +msgid "Custom addon paths beyond the defaults to load custom modules." +msgstr "" + +#: ../../content/administration/on_premise/source.rst:442 +msgid "A typical way to run the server would be:" +msgstr "" + +#: ../../content/administration/on_premise/source.rst:453 +#: ../../content/administration/on_premise/source.rst:474 +msgid "Where `CommunityPath` is the path of the Odoo Community installation, and `mydb` is the name of the PostgreSQL database." +msgstr "" + +#: ../../content/administration/on_premise/source.rst:463 +msgid "Where `CommunityPath` is the path of the Odoo Community installation, `dbuser` is the PostgreSQL login, `dbpassword` is the PostgreSQL password, and `mydb` is the name of the PostgreSQL database." +msgstr "" + +#: ../../content/administration/on_premise/source.rst:477 +msgid "After the server has started (the INFO log `odoo.modules.loading: Modules loaded.` is printed), open http://localhost:8069 in a web browser and log into the Odoo database with the base administrator account: use `admin` as the email and, again, `admin` as the password." +msgstr "" + +#: ../../content/administration/on_premise/source.rst:482 +msgid "From there, create and manage new :doc:`users <../../applications/general/users>`." +msgstr "" + +#: ../../content/administration/on_premise/source.rst:483 +msgid "The user account used to log into Odoo's web interface differs from the :option:`--db_user ` CLI argument." +msgstr "" + +#: ../../content/administration/on_premise/source.rst:487 +msgid ":doc:`The list of CLI arguments for odoo-bin `" +msgstr "" + +#: ../../content/administration/on_premise/update.rst:6 +msgid "Bugfix updates" +msgstr "" + +#: ../../content/administration/on_premise/update.rst:9 +msgid "Introduction" +msgstr "" + +#: ../../content/administration/on_premise/update.rst:11 +msgid "In order to benefit from the latest improvements, security fixes, bug corrections and performance boosts, you may need to update your Odoo installation from time to time." +msgstr "" + +#: ../../content/administration/on_premise/update.rst:14 +msgid "This guide only applies when are using Odoo on your own hosting infrastructure. If you are using one of the Odoo Cloud solutions, updates are automatically performed for you." +msgstr "" + +#: ../../content/administration/on_premise/update.rst:17 +msgid "The terminology surrounding software updates is often confusing, so here are some preliminary definitions:" +msgstr "" + +#: ../../content/administration/on_premise/update.rst:25 +msgid "Updating (an Odoo installation)" +msgstr "" + +#: ../../content/administration/on_premise/update.rst:21 +msgid "Refers to the process of obtaining the latest revision of the source code for your current Odoo Edition. For example, updating your Odoo Enterprise 13.0 to the latest revision. This does not directly cause any change to the contents of your Odoo database, and can be undone by reinstalling the previous revision of the source code." +msgstr "" + +#: ../../content/administration/on_premise/update.rst:35 +msgid "Upgrading (an Odoo database)" +msgstr "" + +#: ../../content/administration/on_premise/update.rst:28 +msgid "Refers to a complex data processing operation where the structure and contents of your database is permanently altered to make it compatible with a new release of Odoo. This operation is irreversible and typically accomplished via Odoo's `database upgrade service `_, when you decide to switch to a newer release of Odoo. Historically, this process has also been known as a \"migration\" because it involves moving data around inside the database, even though the database may end up at the same physical location after the upgrade." +msgstr "" + +#: ../../content/administration/on_premise/update.rst:37 +msgid "This page describes the typical steps needed to *update* an Odoo installation to the latest version. If you'd like more information about upgrading a database, please visit the `Odoo Upgrade page `_ instead." +msgstr "" + +#: ../../content/administration/on_premise/update.rst:43 +msgid "In a nutshell" +msgstr "" + +#: ../../content/administration/on_premise/update.rst:45 +msgid "Updating Odoo is accomplished by simply reinstalling the latest version of your Odoo Edition on top of your current installation. This will preserve your data without any alteration, as long as you do not uninstall PostgreSQL (the database engine that comes with Odoo)." +msgstr "" + +#: ../../content/administration/on_premise/update.rst:49 +msgid "The main reference for updating is logically our :doc:`installation guide <../on_premise>`, which explains the common installation methods." +msgstr "" + +#: ../../content/administration/on_premise/update.rst:52 +msgid "Updating is also most appropriately accomplished by the person who deployed Odoo initially, because the procedure is very similar." +msgstr "" + +#: ../../content/administration/on_premise/update.rst:55 +msgid "We always recommend to download a complete new up-to-date Odoo version, rather than manually applying patches, such as the security patches that come with Security Advisories. The patches are mainly provided for installations that are heavily customized, or for technical personnel who prefer to apply minimal changes temporarily while testing a complete update." +msgstr "" + +#: ../../content/administration/on_premise/update.rst:64 +msgid "Step 1: Download an updated Odoo version" +msgstr "" + +#: ../../content/administration/on_premise/update.rst:66 +msgid "The central download page is https://www.odoo.com/page/download. If you see a \"Buy\" link for the Odoo Enterprise download, make sure you are logged into Odoo.com with the same login that is linked to your Odoo Enterprise subscription." +msgstr "" + +#: ../../content/administration/on_premise/update.rst:70 +msgid "Alternatively, you can use the unique download link that was included with your Odoo Enterprise purchase confirmation email." +msgstr "" + +#: ../../content/administration/on_premise/update.rst:73 +msgid "Downloading an updated version is not necessary if you installed via Github (see below)" +msgstr "" + +#: ../../content/administration/on_premise/update.rst:77 +msgid "Step 2: Make a backup of your database" +msgstr "" + +#: ../../content/administration/on_premise/update.rst:79 +msgid "The update procedure is quite safe and should not alter you data. However it's always best to take a full database backup before performing any change on your installation, and to store it somewhere safe, on a different computer." +msgstr "" + +#: ../../content/administration/on_premise/update.rst:83 +msgid "If you have not disabled the database manager screen (see :ref:`here ` why you should), you can use it (link at bottom of your database selection screen) to download a backup of your database(s). If you disabled it, use the same procedure than for your usual backups." +msgstr "" + +#: ../../content/administration/on_premise/update.rst:89 +msgid "Step 3: Install the updated version" +msgstr "" + +#: ../../content/administration/on_premise/update.rst:91 +msgid "Choose the method that matches your current installation:" +msgstr "" + +#: ../../content/administration/on_premise/update.rst:95 +msgid "Packaged Installers" +msgstr "" + +#: ../../content/administration/on_premise/update.rst:97 +msgid "If you installed Odoo with an installation package downloaded on our website (the recommended method), updating is very simple. All you have to do is download the installation package corresponding to your system (see step #1) and install it on your server. They are updated daily and include the latest security fixes. Usually, you can simply double-click the package to install it on top of the current installation. After installing the package, be sure to restart the Odoo service or reboot your server, and you're all set." +msgstr "" + +#: ../../content/administration/on_premise/update.rst:106 +msgid "Source Install (Tarball)" +msgstr "" + +#: ../../content/administration/on_premise/update.rst:108 +msgid "If you have originally installed Odoo with the \"tarball\" version (source code archive), you have to replace the installation directory with a newer version. First download the latest tarball from Odoo.com. They are updated daily and include the latest security fixes (see step #1) After downloading the package, extract it to a temporary location on your server." +msgstr "" + +#: ../../content/administration/on_premise/update.rst:113 +msgid "You will get a folder labeled with the version of the source code, for example \"odoo-13.0+e.20190719\", that contains a folder \"odoo.egg-info\" and the actual source code folder named \"odoo\" (for Odoo 10 and later) or \"openerp\" for older versions. You can ignore the odoo.egg-info folder. Locate the folder where your current installation is deployed, and replace it with the newer \"odoo\" or \"openerp\" folder that was in the archive you just extracted." +msgstr "" + +#: ../../content/administration/on_premise/update.rst:119 +msgid "Be sure to match the folder layout, for example the new \"addons\" folder included in the source code should end up exactly at the same path it was before. Next, watch out for any specific configuration files that you may have manually copied or modified in the old folder, and copy them over to the new folder. Finally, restart the Odoo service or reboot the machine, and you are all set." +msgstr "" + +#: ../../content/administration/on_premise/update.rst:126 +msgid "Source Install (Github)" +msgstr "" + +#: ../../content/administration/on_premise/update.rst:128 +msgid "If you have originally installed Odoo with a full Github clone of the official repositories, the update procedure requires you to pull the latest source code via git. Change into the directory for each repository (the main Odoo repository, and the Enterprise repository), and run the following commands::" +msgstr "" + +#: ../../content/administration/on_premise/update.rst:136 +msgid "The last command may encounter source code conflicts if you had edited the Odoo source code locally. The error message will give you the list of files with conflicts, and you will need to resolve the conflicts manually, by editing them and deciding which part of the code to keep." +msgstr "" + +#: ../../content/administration/on_premise/update.rst:140 +msgid "Alternatively, if you prefer to simply discard the conflicting changes and restore the official version, you can use the following command::" +msgstr "" + +#: ../../content/administration/on_premise/update.rst:145 +msgid "Finally, restart the Odoo service or reboot the machine, and you should be done." +msgstr "" + +#: ../../content/administration/on_premise/update.rst:149 +msgid "Docker" +msgstr "" + +#: ../../content/administration/on_premise/update.rst:151 +msgid "Please refer to our `Docker image documentation `_ for specific update instructions." +msgstr "" + +#: ../../content/administration/supported_versions.rst:7 +msgid "Supported versions" +msgstr "" + +#: ../../content/administration/supported_versions.rst:9 +msgid "Odoo provides support and bug fixing **for the 3 last major versions** of Odoo." +msgstr "" + +#: ../../content/administration/supported_versions.rst:12 +msgid "Odoo releases intermediary versions called **Online versions** on the :doc:`Odoo Online ` hosting every two months. Odoo Online users can then benefit from the latest features of Odoo." +msgstr "" + +#: ../../content/administration/supported_versions.rst:16 +msgid "Admins of Odoo Online databases are invited to :doc:`upgrade ` them regularly." +msgstr "" + +#: ../../content/administration/supported_versions.rst:17 +msgid "Online versions are *not* released for Odoo.sh and On-Premise installations." +msgstr "" + +#: ../../content/administration/supported_versions.rst:18 +msgid "Online versions are listed below as *SaaS*." +msgstr "" + +#: ../../content/administration/supported_versions.rst:20 +msgid "This matrix shows the support status of every version." +msgstr "" + +#: ../../content/administration/supported_versions.rst:22 +msgid "**Major releases are in bold type.**" +msgstr "" + +#: ../../content/administration/supported_versions.rst:31 +msgid "On-Premise" +msgstr "" + +#: ../../content/administration/supported_versions.rst:32 +msgid "Release date" +msgstr "" + +#: ../../content/administration/supported_versions.rst:33 +msgid "End of support" +msgstr "" + +#: ../../content/administration/supported_versions.rst:34 +msgid "Odoo saas~17.1" +msgstr "" + +#: ../../content/administration/supported_versions.rst:36 +#: ../../content/administration/supported_versions.rst:37 +#: ../../content/administration/supported_versions.rst:48 +#: ../../content/administration/supported_versions.rst:49 +#: ../../content/administration/supported_versions.rst:54 +#: ../../content/administration/supported_versions.rst:55 +#: ../../content/administration/supported_versions.rst:60 +#: ../../content/administration/supported_versions.rst:61 +#: ../../content/administration/supported_versions.rst:66 +#: ../../content/administration/supported_versions.rst:67 +#: ../../content/administration/supported_versions.rst:78 +#: ../../content/administration/supported_versions.rst:79 +#: ../../content/administration/supported_versions.rst:84 +#: ../../content/administration/supported_versions.rst:85 +msgid "N/A" +msgstr "" + +#: ../../content/administration/supported_versions.rst:38 +msgid "January 2024" +msgstr "" + +#: ../../content/administration/supported_versions.rst:40 +msgid "**Odoo 17.0**" +msgstr "" + +#: ../../content/administration/supported_versions.rst:44 +#: ../../content/administration/supported_versions.rst:99 +msgid "November 2023" +msgstr "" + +#: ../../content/administration/supported_versions.rst:45 +msgid "October 2026 (planned)" +msgstr "" + +#: ../../content/administration/supported_versions.rst:46 +msgid "Odoo saas~16.4" +msgstr "" + +#: ../../content/administration/supported_versions.rst:50 +msgid "August 2023" +msgstr "" + +#: ../../content/administration/supported_versions.rst:52 +msgid "Odoo saas~16.3" +msgstr "" + +#: ../../content/administration/supported_versions.rst:53 +#: ../../content/administration/supported_versions.rst:59 +#: ../../content/administration/supported_versions.rst:65 +#: ../../content/administration/supported_versions.rst:77 +#: ../../content/administration/supported_versions.rst:83 +#: ../../content/administration/supported_versions.rst:95 +#: ../../content/administration/supported_versions.rst:96 +#: ../../content/administration/supported_versions.rst:97 +#: ../../content/administration/supported_versions.rst:101 +#: ../../content/administration/supported_versions.rst:102 +#: ../../content/administration/supported_versions.rst:103 +#: ../../content/administration/supported_versions.rst:107 +#: ../../content/administration/supported_versions.rst:108 +#: ../../content/administration/supported_versions.rst:109 +msgid "|red|" +msgstr "" + +#: ../../content/administration/supported_versions.rst:56 +msgid "June 2023" +msgstr "" + +#: ../../content/administration/supported_versions.rst:58 +msgid "Odoo saas~16.2" +msgstr "" + +#: ../../content/administration/supported_versions.rst:62 +msgid "March 2023" +msgstr "" + +#: ../../content/administration/supported_versions.rst:64 +msgid "Odoo saas~16.1" +msgstr "" + +#: ../../content/administration/supported_versions.rst:68 +msgid "February 2023" +msgstr "" + +#: ../../content/administration/supported_versions.rst:70 +msgid "**Odoo 16.0**" +msgstr "" + +#: ../../content/administration/supported_versions.rst:74 +#: ../../content/administration/supported_versions.rst:105 +msgid "October 2022" +msgstr "" + +#: ../../content/administration/supported_versions.rst:75 +msgid "November 2025 (planned)" +msgstr "" + +#: ../../content/administration/supported_versions.rst:76 +msgid "Odoo saas~15.2" +msgstr "" + +#: ../../content/administration/supported_versions.rst:80 +msgid "March 2022" +msgstr "" + +#: ../../content/administration/supported_versions.rst:81 +msgid "January 2023" +msgstr "" + +#: ../../content/administration/supported_versions.rst:82 +msgid "Odoo saas~15.1" +msgstr "" + +#: ../../content/administration/supported_versions.rst:86 +msgid "February 2022" +msgstr "" + +#: ../../content/administration/supported_versions.rst:87 +msgid "July 2022" +msgstr "" + +#: ../../content/administration/supported_versions.rst:88 +msgid "**Odoo 15.0**" +msgstr "" + +#: ../../content/administration/supported_versions.rst:92 +msgid "October 2021" +msgstr "" + +#: ../../content/administration/supported_versions.rst:93 +msgid "November 2024 (planned)" +msgstr "" + +#: ../../content/administration/supported_versions.rst:94 +msgid "**Odoo 14.0**" +msgstr "" + +#: ../../content/administration/supported_versions.rst:98 +msgid "October 2020" +msgstr "" + +#: ../../content/administration/supported_versions.rst:100 +msgid "**Odoo 13.0**" +msgstr "" + +#: ../../content/administration/supported_versions.rst:104 +msgid "October 2019" +msgstr "" + +#: ../../content/administration/supported_versions.rst:106 +msgid "Older versions" +msgstr "" + +#: ../../content/administration/supported_versions.rst:110 +msgid "Before 2019" +msgstr "" + +#: ../../content/administration/supported_versions.rst:111 +msgid "Before 2022" +msgstr "" + +#: ../../content/administration/supported_versions.rst:113 +msgid "Legend" +msgstr "" + +#: ../../content/administration/supported_versions.rst:115 +msgid "|green| Supported version" +msgstr "" + +#: ../../content/administration/supported_versions.rst:117 +msgid "|red| End-of-support" +msgstr "" + +#: ../../content/administration/supported_versions.rst:119 +msgid "N/A Never released for this platform" +msgstr "" + +#: ../../content/administration/supported_versions.rst:122 +msgid "Even though we don't support older versions, you can always `upgrade from any version `_." +msgstr "" + #: ../../content/administration/upgrade.rst:7 -msgid "An upgrade is the process of moving your database from an older version to a newer :doc:`supported version ` (e.g., Odoo 14.0 to Odoo 16.0). Frequently upgrading is essential as each version comes with new and improved features, bug fixes, and security patches." +msgid "An upgrade is the process of moving your database from an older version to a newer :doc:`supported version ` (e.g., Odoo 14.0 to Odoo 16.0). Frequently upgrading is essential as each version comes with new and improved features, bug fixes, and security patches." msgstr "" #: ../../content/administration/upgrade.rst:15 @@ -6077,11 +4854,11 @@ msgid "Downgrading to a previous version of Odoo" msgstr "" #: ../../content/administration/upgrade.rst:36 -msgid ":doc:`Switching editions ` (e.g., from Community to Enterprise)" +msgid ":doc:`Switching editions ` (e.g., from Community to Enterprise)" msgstr "" -#: ../../content/administration/upgrade.rst:37 -msgid ":doc:`Changing hosting type ` (e.g., from on-premise to Odoo Online)" +#: ../../content/administration/upgrade.rst:38 +msgid ":ref:`Changing hosting type ` (e.g., from on-premise to Odoo Online)" msgstr "" #: ../../content/administration/upgrade.rst:39 @@ -6200,11 +4977,6 @@ msgstr "" msgid "Check out the :doc:`/developer/howtos/upgrade_custom_db` page for more information." msgstr "" -#: ../../content/administration/upgrade.rst:145 -#: ../../content/administration/upgrade.rst:341 -msgid "On-premise" -msgstr "" - #: ../../content/administration/upgrade.rst:147 msgid "The standard upgrade process can be initiated by entering the following command line on the machine where the database is hosted:" msgstr "" @@ -6558,5 +5330,5 @@ msgid ":doc:`Odoo.sh documentation `" msgstr "" #: ../../content/administration/upgrade.rst:407 -msgid ":doc:`Supported Odoo versions `" +msgid ":doc:`Supported Odoo versions `" msgstr "" diff --git a/locale/sources/essentials.pot b/locale/sources/essentials.pot new file mode 100644 index 000000000..e2bac2bb7 --- /dev/null +++ b/locale/sources/essentials.pot @@ -0,0 +1,1442 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) Odoo S.A. +# This file is distributed under the same license as the Odoo package. +# FIRST AUTHOR , YEAR. +# +#, fuzzy +msgid "" +msgstr "" +"Project-Id-Version: Odoo 17.0\n" +"Report-Msgid-Bugs-To: \n" +"POT-Creation-Date: 2024-03-25 16:01+0000\n" +"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" +"Last-Translator: FULL NAME \n" +"Language-Team: LANGUAGE \n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" + +#: ../../content/applications/essentials.rst:3 +msgid "Odoo essentials" +msgstr "" + +#: ../../content/applications/essentials/activities.rst:3 +msgid "Activities" +msgstr "" + +#: ../../content/applications/essentials/activities.rst:5 +msgid "*Activities* are follow-up tasks tied to a record in an Odoo database. Activities can be scheduled on any page of the database that contains a chatter thread, kanban view, list view, or activities view of an application." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:10 +msgid "Schedule activities" +msgstr "" + +#: ../../content/applications/essentials/activities.rst:12 +msgid "One way that activities are created is by clicking the :guilabel:`Schedule Activity` button, located at the top of the *chatter* on any record. On the pop-up window that appears, select an :guilabel:`Activity Type` from the drop-down menu." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:17 +msgid "Individual applications have a list of *Activity Types* dedicated to that application. For example, to view and edit the activities available for the *CRM* application, go to :menuselection:`CRM app --> Configuration --> Activity Types`." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:21 +msgid "Enter a title for the activity in the :guilabel:`Summary` field, located in the :guilabel:`Schedule Activity` pop-up window." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:24 +msgid "To assign the activity to a different user, select a name from the :guilabel:`Assigned to` drop-down menu. Otherwise, the user creating the activity is automatically assigned." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:27 +msgid "Lastly, feel free to add any additional information in the optional :guilabel:`Log a note...` field." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:30 +msgid "The :guilabel:`Due Date` field on the :guilabel:`Schedule Activity` pop-up window auto-populates based on the configuration settings for the selected :guilabel:`Activity Type`. However, this date can be changed by selecting a day on the calendar in the :guilabel:`Due Date` field." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:34 +msgid "Lastly, click one of the following buttons:" +msgstr "" + +#: ../../content/applications/essentials/activities.rst:36 +msgid ":guilabel:`Schedule`: adds the activity to the chatter under :guilabel:`Planned activities`." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:37 +msgid ":guilabel:`Mark as Done`: adds the details of the activity to the chatter under :guilabel:`Today`. The activity is not scheduled, it is automatically marked as completed." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:39 +msgid ":guilabel:`Done \\& Schedule Next`: adds the task under :guilabel:`Today` marked as done, and opens a new activity window." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:41 +msgid ":guilabel:`Discard`: discards any changes made on the pop-up window." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:-1 +#: ../../content/applications/essentials/activities.rst:-1 +msgid "View of CRM leads and the option to schedule an activity." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:47 +msgid "Depending on the activity type, the :guilabel:`Schedule` button may be replaced by a :guilabel:`Save` button, or an :guilabel:`Open Calendar` button." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:50 +msgid "Scheduled activities are added to the chatter for the record under :guilabel:`Planned activities`." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:55 +msgid "Activities can also be scheduled from the kanban, list, or activities view of an application." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:59 +msgid "Kanban view" +msgstr "" + +#: ../../content/applications/essentials/activities.rst:61 +msgid "Select a record on which to schedule an activity. Click on the :guilabel:`🕘 (clock)` icon, then :guilabel:`Schedule An Activity`, and proceed to fill out the pop-up form." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:0 +msgid "Kanban view of the CRM pipeline and the option to schedule an activity." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:67 +msgid "List view" +msgstr "" + +#: ../../content/applications/essentials/activities.rst:69 +msgid "Select a record on which to schedule an activity. Click on the :guilabel:`🕘 (clock)` icon, then :guilabel:`Schedule An Activity`. If the record already has an activity scheduled, the clock icon may be replaced by a :guilabel:`📞 (phone)` or an :guilabel:`✉️ (envelope)` icon." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:0 +msgid "List view of the CRM pipeline and the option to schedule an activity." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:76 +msgid "Activity view" +msgstr "" + +#: ../../content/applications/essentials/activities.rst:78 +msgid "To open the activity view for an application, select the :guilabel:`🕘 (clock)` icon from the menu bar anywhere in the database. Select any application from the drop-down menu, and click the :guilabel:`🕘 (clock)` icon for the desired app." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:0 +msgid "Activity menu drop down with focus on where to open activity view for CRM." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:85 +msgid "Select a record on which to schedule an activity. Move across the row to find the desired activity type, then click the :guilabel:`＋ (plus sign)`." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:0 +msgid "Activity view of the CRM pipeline and the option to schedule an activity." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:92 +msgid "Activity colors, and their relation to an activity's due date, is consistent throughout Odoo, regardless of the activity type, or the view." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:95 +msgid "Activities that appear in **green** indicate a due date sometime in the future." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:96 +msgid "**Yellow** indicates that the activity's due date is today." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:97 +msgid "**Red** indicates that the activity is overdue and the due date has passed." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:99 +msgid "For example, if an activity is created for a phone call, and the due date passes, the activity appears with a red phone in list view, and a red clock on the kanban view." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:103 +msgid "View scheduled activities" +msgstr "" + +#: ../../content/applications/essentials/activities.rst:105 +msgid "To view scheduled activities, open either the :menuselection:`Sales app` or :menuselection:`CRM app` and click the :guilabel:`🕘 (clock)` icon, located to the far-right side of the other view options." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:108 +msgid "Doing so opens the activities menu, showcasing all the scheduled activities for the user, by default. To show all activities for every user, remove the :guilabel:`My Pipeline` filter from the :guilabel:`Search...` bar." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:112 +msgid "To view a consolidated list of activities separated by the application where they were created, and by deadline, click the :guilabel:`🕘 (clock)` icon on the header menu to see the activities for that specific application in a drop-down menu." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:116 +msgid "The possibility to :guilabel:`Add new note` and :guilabel:`Request a Document` appear at the bottom of this drop-down menu, when the :guilabel:`🕘 (clock)` icon on the header menu is clicked." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:-1 +msgid "View of CRM leads page emphasizing the activities menu." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:123 +msgid "Configure activity types" +msgstr "" + +#: ../../content/applications/essentials/activities.rst:125 +msgid "To configure the types of activities in the database, go to :menuselection:`Settings app --> Discuss --> Activities --> Activity Types`." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:-1 +msgid "View of the settings page emphasizing the menu activity types." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:131 +msgid "Doing so reveals the :guilabel:`Activity Types` page, where the existing activity types are found." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:133 +msgid "To edit an existing activity type, select it from the list, then click :guilabel:`Edit`. To create a new activity type, click :guilabel:`Create`." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:136 +msgid "At the top of a blank activity type form, start by choosing a :guilabel:`Name` for the new activity type." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:-1 +msgid "New activity type form." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:143 +msgid "Activity settings" +msgstr "" + +#: ../../content/applications/essentials/activities.rst:146 +msgid "Action" +msgstr "" + +#: ../../content/applications/essentials/activities.rst:148 +msgid "The *Action* field specifies the intent of the activity. Some actions trigger specific behaviors after an activity is scheduled." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:151 +msgid "If :guilabel:`Upload Document` is selected, a link to upload a document is added directly to the planned activity in the chatter." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:153 +msgid "If either :guilabel:`Phonecall` or :guilabel:`Meeting` are selected, users have the option to open their calendar to schedule a time for this activity." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:155 +msgid "If :guilabel:`Request Signature` is selected, a link is added to the planned activity in the chatter that opens a signature request pop-up window." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:159 +msgid "The actions available to select on an activity type vary, depending on the applications currently installed in the database." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:163 +msgid "Default user" +msgstr "" + +#: ../../content/applications/essentials/activities.rst:165 +msgid "To automatically assign this activity to a specific user when this activity type is scheduled, choose a name from the :guilabel:`Default User` drop-down menu. If this field is left blank, the activity is assigned to the user who creates the activity." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:170 +msgid "Default summary" +msgstr "" + +#: ../../content/applications/essentials/activities.rst:172 +msgid "To include notes whenever this activity type is created, enter them into the :guilabel:`Default Summary` field." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:176 +msgid "The information in the :guilabel:`Default User` and :guilabel:`Default Summary` fields are included when an activity is created. However, they can be altered before the activity is scheduled or saved." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:181 +msgid "Next activity" +msgstr "" + +#: ../../content/applications/essentials/activities.rst:183 +msgid "To automatically suggest, or trigger, a new activity after an activity has been marked complete, the :guilabel:`Chaining Type` must be set." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:187 +msgid "Suggest next activity" +msgstr "" + +#: ../../content/applications/essentials/activities.rst:189 +msgid "In the :guilabel:`Chaining Type` field, select :guilabel:`Suggest Next Activity`. Upon doing so, the field underneath changes to: :guilabel:`Suggest`. Click the :guilabel:`Suggest` field drop-down menu to select any activities to recommend as follow-up tasks to this activity type." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:193 +#: ../../content/applications/essentials/activities.rst:220 +msgid "In the :guilabel:`Schedule` field, choose a default deadline for these activities. To do so, configure a desired number of :guilabel:`Days`, :guilabel:`Weeks`, or :guilabel:`Months`. Then, decide if it should occur :guilabel:`after completion date` or :guilabel:`after previous activity deadline`." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:198 +#: ../../content/applications/essentials/activities.rst:225 +msgid "This :guilabel:`Schedule` field information can be altered before the activity is scheduled." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:200 +#: ../../content/applications/essentials/activities.rst:227 +msgid "When all configurations are complete, click :guilabel:`Save`." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:-1 +msgid "Schedule activity popup with emphasis on recommended activities." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:206 +msgid "If an activity has the :guilabel:`Chaining Type` set to :guilabel:`Suggest Next Activity`, and has activities listed in the :guilabel:`Suggest` field, users are presented with recommendations for activities as next steps." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:211 +msgid "Trigger next activity" +msgstr "" + +#: ../../content/applications/essentials/activities.rst:213 +msgid "Setting the :guilabel:`Chaining Type` to :guilabel:`Trigger Next Activity` immediately launches the next activity once the previous one is completed." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:216 +msgid "If :guilabel:`Trigger Next Activity` is selected in the :guilabel:`Chaining Type` field, the field beneath changes to: :guilabel:`Trigger`. From the :guilabel:`Trigger` field drop-down menu, select the activity that should be launched once this activity is completed." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:-1 +msgid "Schedule new activity popup with emphasis on Done and launch next button." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:233 +msgid "When an activity has the :guilabel:`Chaining Type` set to :guilabel:`Trigger Next Activity`, marking the activity as `Done` immediately launches the next activity listed in the :guilabel:`Trigger` field." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:238 +msgid ":doc:`/applications/productivity/discuss`" +msgstr "" + +#: ../../content/applications/essentials/activities.rst:239 +msgid ":doc:`/applications/productivity/discuss/team_communication`" +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:3 +msgid "Export and import data" +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:5 +msgid "In Odoo, it is sometimes necessary to export or import data for running reports, or for data modification. This document covers the export and import of data into and out of Odoo." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:9 +msgid "Sometimes, users run into a 'time out' error, or a record does not process, due to its size. This can occur with large exports, or in cases where the import file is too large. To circumvent this limitation surrounding the size of the records, process exports or imports in smaller batches." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:16 +msgid "Export data from Odoo" +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:18 +msgid "When working with a database, it is sometimes necessary to export data in a distinct file. Doing so can aid in reporting on activities, although, Odoo provides a precise and easy reporting tool with each available application." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:22 +msgid "With Odoo, the values can be exported from any field in any record. To do so, activate the list view (:guilabel:`☰ (three horizontal lines)` icon), on the items that need to be exported, and then select the records that should be exported. To select a record, tick the checkbox next to the corresponding record. Finally, click on :guilabel:`⚙️ Action`, and then :guilabel:`Export`." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:-1 +msgid "View of the different things to enable/click to export data." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:31 +msgid "When clicking on :guilabel:`Export`, an :guilabel:`Export Data` pop-over window appears, with several options for the data to export:" +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:-1 +msgid "Overview of options to consider when exporting data in Odoo.." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:38 +msgid "With the :guilabel:`I want to update data (import-compatable export)` option ticked, the system only shows the fields that can be imported. This is helpful in the case where the existing records need to be updated. This works like a filter. Leaving the box unticked, gives many more field options because it shows all the fields, not just the ones that can be imported." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:42 +msgid "When exporting, there is the option to export in two formats: `.csv` and `.xls`. With `.csv`, items are separated by a comma, while `.xls` holds information about all the worksheets in a file, including both content and formatting." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:45 +msgid "These are the items that can be exported. Use the :guilabel:`> (right arrow)` icon to display more sub-field options. Use the :guilabel:`Search` bar to find specific fields. To use the :guilabel:`Search` option more efficiently, click on all the :guilabel:`> (right arrows)` to display all fields." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:49 +msgid "The :guilabel:`+ (plus sign)` icon button is present to add fields to the :guilabel:`Fields to export` list." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:51 +msgid "The :guilabel:`↕️ (up-down arrow)` to the left of the selected fields can be used to move the fields up and down, to change the order in which they are displayed in the exported file. Drag-and-drop using the :guilabel:`↕️ (up-down arrow)` icon." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:54 +msgid "The :guilabel:`🗑️ (trash can)` icon is used to remove fields. Click on the :guilabel:`🗑️ (trash can)` icon to remove the field." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:56 +msgid "For recurring reports, it is helpful to save export presets. Select all the needed fields, and click on the template drop-down menu. Once there, click on :guilabel:`New template`, and give a unique name to the export just created. The next time the same list needs to be exported, select the related template that was previously saved from the drop-down menu." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:62 +msgid "It is helpful to know the field's external identifier. For example, :guilabel:`Related Company` in the export user interface is equal to *parent_id* (external identifier). This is helpful because then, the only data exported is what should be modified and re-imported." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:69 +msgid "Import data into Odoo" +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:71 +msgid "Importing data into Odoo is extremely helpful during implementation, or in times where data needs to be updated in bulk. The following documentation covers how to import data into an Odoo database." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:75 +msgid "Imports are permanent and **cannot** be undone. However, it is possible to use filters (`created on` or `last modified`) to identify records changed or created by the import." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:79 +msgid "Activating :ref:`developer mode ` changes the visible import settings in the left menu. Doing so reveals an :menuselection:`Advanced` menu. Included in this advanced menu are two options: :guilabel:`Track history during import` and :guilabel:`Allow matching with subfields`." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:-1 +msgid "Advanced import options when developer mode is activated." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:87 +msgid "If the model uses openchatter, the :guilabel:`Track history during import` option sets up subscriptions and sends notifications during the import, but leads to a slower import." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:90 +msgid "Should the :guilabel:`Allow matching with subfields` option be selected, then all subfields within a field are used to match under the :guilabel:`Odoo Field` while importing." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:94 +msgid "Get started" +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:96 +msgid "Data can be imported on any Odoo business object using either Excel (`.xlsx`) or :abbr:`CSV (Comma-separated Values)` (`.csv`) formats. This includes: contacts, products, bank statements, journal entries, and orders." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:100 +msgid "Open the view of the object to which the data should be imported/populated, and click on :menuselection:`⭐ Favorites --> Import records`." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:-1 +msgid "Favorites menu revealed with the import records option highlighted." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:107 +msgid "After clicking :guilabel:`Import records`, Odoo reveals a separate page with templates that can be downloaded and populated with the company's own data. Such templates can be imported in one click, since the data mapping is already done. To download a template click :guilabel:`Import Template for Customers` at the center of the page." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:113 +msgid "When importing a :abbr:`CSV (Comma-separated Values)` file, Odoo provides :guilabel:`Formatting` options. These options do **not** appear when importing the proprietary Excel file type (`.xls`, `.xlsx`)." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:0 +msgid "Formatting options presented when a CVS file is imported in Odoo." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:121 +msgid "Make necessary adjustments to the *Formatting* options, and ensure all columns in the :guilabel:`Odoo field` and :guilabel:`File Column` are free of errors. Finally, click :guilabel:`Import` to import the data." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:126 +msgid "Adapt a template" +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:128 +msgid "Import templates are provided in the import tool of the most common data to import (contacts, products, bank statements, etc.). Open them with any spreadsheet software (*Microsoft Office*, *OpenOffice*, *Google Drive*, etc.)." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:132 +msgid "Once the template is downloaded, proceed to follow these steps:" +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:134 +msgid "Add, remove, and sort columns to best fit the data structure." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:135 +msgid "It is strongly advised to **not** remove the :guilabel:`External ID` (ID) column (see why in the next section)." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:137 +msgid "Set a unique ID to every record by dragging down the ID sequencing in the :guilabel:`External ID` (ID) column." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:-1 +msgid "An animation of the mouse dragging down the ID column, so each record has a unique ID." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:145 +msgid "When a new column is added, Odoo may not be able to map it automatically, if its label does not fit any field within Odoo. However, new columns can be mapped manually when the import is tested. Search the drop-down menu for the corresponding field." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:-1 +msgid "Drop-down menu expanded in the initial import screen on Odoo." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:153 +msgid "Then, use this field's label in the import file to ensure future imports are successful." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:156 +msgid "Another useful way to find out the proper column names to import is to export a sample file using the fields that should be imported. This way, if there is not a sample import template, the names are accurate." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:161 +msgid "Import from another application" +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:163 +msgid "The :guilabel:`External ID` (ID) is a unique identifier for the line item. Feel free to use one from previous software to facilitate the transition to Odoo." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:166 +msgid "Setting an ID is not mandatory when importing, but it helps in many cases:" +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:168 +msgid "Update imports: import the same file several times without creating duplicates." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:169 +msgid ":ref:`Import relation fields `." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:171 +msgid "To recreate relationships between different records, the unique identifier from the original application should be used to map it to the :guilabel:`External ID` (ID) column in Odoo." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:174 +msgid "When another record is imported that links to the first one, use **XXX/ID** (XXX/External ID) for the original unique identifier. This record can also be found using its name." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:178 +msgid "It should be noted that there will be a conflict if two or more records have the same name." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:180 +msgid "The :guilabel:`External ID` (ID) can also be used to update the original import, if modified data needs to be re-imported later, therefore, it is a good practice to specify it whenever possible." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:184 +msgid "Field missing to map column" +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:186 +msgid "Odoo heuristically tries to find the type of field for each column inside the imported file, based on the first ten lines of the files." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:189 +msgid "For example, if there is a column only containing numbers, only the fields with the *integer* type are presented as options." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:192 +msgid "While this behavior might be beneficial in most cases, it is also possible that it could fail, or the column may be mapped to a field that is not proposed by default." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:195 +msgid "If this happens, check the :guilabel:`Show fields of relation fields (advanced) option`, then a complete list of fields becomes available for each column." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:-1 +msgid "Searching for the field to match the tax column." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:203 +msgid "Change data import format" +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:206 +msgid "Odoo can automatically detect if a column is a date, and tries to guess the date format from a set of most commonly used date formats. While this process can work for many date formats, some date formats are not recognizable. This can cause confusion, due to day-month inversions; it is difficult to guess which part of a date format is the day, and which part is the month, in a date, such as `01-03-2016`." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:212 +msgid "When importing a :abbr:`CSV (Comma-separated Values)` file, Odoo provides :guilabel:`Formatting` options." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:215 +msgid "To view which date format Odoo has found from the file, check the :guilabel:`Date Format` that is shown when clicking on options under the file selector. If this format is incorrect, change it to the preferred format using *ISO 8601* to define the format." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:220 +msgid "*ISO 8601* is an international standard, covering the worldwide exchange, along with the communication of date and time-related data. For example, the date format should be `YYYY-MM-DD`. So, in the case of July 24th 1981, it should be written as `1981-07-24`." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:225 +msgid "When importing Excel files (`.xls`, `.xlsx`), consider using *date cells* to store dates. This maintains locale date formats for display, regardless of how the date is formatted in Odoo. When importing a :abbr:`CSV (Comma-separated Values)` file, use Odoo's :guilabel:`Formatting` section to select the date format columns to import." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:231 +msgid "Import numbers with currency signs" +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:233 +msgid "Odoo fully supports numbers with parenthesis to represent negative signs, as well as numbers with currency signs attached to them. Odoo also automatically detects which thousand/decimal separator is used. If a currency symbol unknown to Odoo is used, it might not be recognized as a number, and the import crashes." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:239 +msgid "When importing a :abbr:`CSV (Comma-separated Values)` file, the :guilabel:`Formatting` menu appears on the left-hand column. Under these options, the :guilabel:`Thousands Separator` can be changed." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:243 +msgid "Examples of supported numbers (using 'thirty-two thousand' as the figure):" +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:245 +msgid "32.000,00" +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:246 +msgid "32000,00" +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:247 +msgid "32,000.00" +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:248 +msgid "-32000.00" +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:249 +msgid "(32000.00)" +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:250 +msgid "$ 32.000,00" +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:251 +msgid "(32000.00 €)" +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:253 +msgid "Example that will not work:" +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:255 +msgid "ABC 32.000,00" +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:256 +msgid "$ (32.000,00)" +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:259 +msgid "A :guilabel:`() (parenthesis)` around the number indicates that the number is a negative value. The currency symbol **must** be placed within the parenthesis for Odoo to recognize it as a negative currency value." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:264 +msgid "Import preview table not displayed correctly" +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:266 +msgid "By default, the import preview is set on commas as field separators, and quotation marks as text delimiters. If the :abbr:`CSV (Comma-separated Values)` file does not have these settings, modify the :guilabel:`Formatting` options (displayed under the :guilabel:`Import` :abbr:`CSV (Comma-separated Values)` file bar after selecting the :abbr:`CSV (Comma-separated Values)` file)." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:272 +msgid "If the :abbr:`CSV (Comma-separated Values)` file has a tabulation as a separator, Odoo does **not** detect the separations. The file format options need to be modified in the spreadsheet application. See the following :ref:`Change CSV file format ` section." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:280 +msgid "Change CSV file format in spreadsheet application" +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:282 +msgid "When editing and saving :abbr:`CSV (Comma-separated Values)` files in spreadsheet applications, the computer's regional settings are applied for the separator and delimiter. Odoo suggests using *OpenOffice* or *LibreOffice*, as both applications allow modifications of all three options (from *LibreOffice* application, go to :menuselection:`'Save As' dialog box --> Check the box 'Edit filter settings' --> Save`)." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:288 +msgid "Microsoft Excel can modify the encoding when saving (:menuselection:`'Save As' dialog box --> 'Tools' drop-down menu --> Encoding tab`)." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:292 +msgid "Difference between Database ID and External ID" +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:294 +msgid "Some fields define a relationship with another object. For example, the country of a contact is a link to a record of the 'Country' object. When such fields are imported, Odoo has to recreate links between the different records. To help import such fields, Odoo provides three mechanisms." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:299 +msgid "**Only one** mechanism should be used per field that is imported." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:301 +msgid "For example, to reference the country of a contact, Odoo proposes three different fields to import:" +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:303 +msgid ":guilabel:`Country`: the name or code of the country" +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:304 +msgid ":guilabel:`Country/Database ID`: the unique Odoo ID for a record, defined by the ID PostgreSQL column" +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:306 +msgid ":guilabel:`Country/External ID`: the ID of this record referenced in another application (or the `.XML` file that imported it)" +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:309 +msgid "For the country of Belgium, for example, use one of these three ways to import:" +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:311 +msgid ":guilabel:`Country`: `Belgium`" +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:312 +msgid ":guilabel:`Country/Database ID`: `21`" +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:313 +msgid ":guilabel:`Country/External ID`: `base.be`" +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:315 +msgid "According to the company's need, use one of these three ways to reference records in relations. Here is an example when one or the other should be used, according to the need:" +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:318 +msgid "Use :guilabel:`Country`: this is the easiest way when data comes from :abbr:`CSV (Comma-separated Values)` files that have been created manually." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:320 +msgid "Use :guilabel:`Country/Database ID`: this should rarely be used. It is mostly used by developers as the main advantage is to never have conflicts (there may be several records with the same name, but they always have a unique Database ID)" +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:323 +msgid "Use :guilabel:`Country/External ID`: use *External ID* when importing data from a third-party application." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:326 +msgid "When *External IDs* are used, import :abbr:`CSV (Comma-separated Values)` files with the :guilabel:`External ID` (ID) column defining the *External ID* of each record that is imported. Then, a reference can be made to that record with columns, like `Field/External ID`. The following two :abbr:`CSV (Comma-separated Values)` files provide an example for products and their categories." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:331 +msgid ":download:`CSV file for categories `" +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:333 +msgid ":download:`CSV file for Products `" +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:339 +msgid "Import relation fields" +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:341 +msgid "An Odoo object is always related to many other objects (e.g. a product is linked to product categories, attributes, vendors, etc.). To import those relations, the records of the related object need to be imported first, from their own list menu." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:345 +msgid "This can be achieved by using either the name of the related record, or its ID, depending on the circumstances. The ID is expected when two records have the same name. In such a case add `/ ID` at the end of the column title (e.g. for product attributes: `Product Attributes / Attribute / ID`)." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:350 +msgid "Options for multiple matches on fields" +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:352 +msgid "If, for example, there are two product categories with the child name `Sellable` (e.g. `Misc. Products/Sellable` & `Other Products/Sellable`), the validation is halted, but the data may still be imported. However, Odoo recommends that the data is not imported because it will all be linked to the first `Sellable` category found in the *Product Category* list (`Misc. Products/Sellable`). Odoo, instead, recommends modifying one of the duplicate's values, or the product category hierarchy." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:359 +msgid "However, if the company does not wish to change the configuration of product categories, Odoo recommends making use of the *External ID* for this field, 'Category'." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:363 +msgid "Import many2many relationship fields" +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:365 +msgid "The tags should be separated by a comma, without any spacing. For example, if a customer needs to be linked to both tags: `Manufacturer` and `Retailer` then 'Manufacturer,Retailer' needs to be encoded in the same column of the :abbr:`CSV (Comma-separated Values)` file." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:369 +msgid ":download:`CSV file for Manufacturer, Retailer `" +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:372 +msgid "Import one2many relationships" +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:374 +msgid "If a company wants to import a sales order with several order lines, a specific row **must** be reserved in the :abbr:`CSV (Comma-separated Values)` file for each order line. The first order line is imported on the same row as the information relative to order. Any additional lines need an additional row that does not have any information in the fields relative to the order." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:379 +msgid "As an example, here is a :abbr:`CSV (Comma-separated Values)` file of some quotations that can be imported, based on demo data:" +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:382 +msgid ":download:`File for some Quotations `" +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:385 +msgid "The following :abbr:`CSV (Comma-separated Values)` file shows how to import purchase orders with their respective purchase order lines:" +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:388 +msgid ":download:`Purchase orders with their respective purchase order lines `" +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:391 +msgid "The following :abbr:`CSV (Comma-separated Values)` file shows how to import customers and their respective contacts:" +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:394 +msgid ":download:`Customers and their respective contacts `" +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:398 +msgid "Import records several times" +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:400 +msgid "If an imported file contains one of the columns: :guilabel:`External ID` or :guilabel:`Database ID`, records that have already been imported are modified, instead of being created. This is extremely useful as it allows users to import the same :abbr:`CSV (Comma-separated Values)` file several times, while having made some changes in between two imports." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:405 +msgid "Odoo takes care of creating or modifying each record, depending if it is new or not." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:407 +msgid "This feature allows a company to use the *Import/Export tool* in Odoo to modify a batch of records in a spreadsheet application." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:411 +msgid "Value not provided for a specific field" +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:413 +msgid "If all fields are not set in the CSV file, Odoo assigns the default value for every non-defined field. But, if fields are set with empty values in the :abbr:`CSV (Comma-separated Values)` file, Odoo sets the empty value in the field, instead of assigning the default value." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:418 +msgid "Export/import different tables from an SQL application to Odoo" +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:420 +msgid "If data needs to be imported from different tables, relations need to be recreated between records belonging to different tables. For instance, if companies and people are imported, the link between each person and the company they work for needs to be recreated." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:424 +msgid "To manage relations between tables, use the `External ID` facilities of Odoo. The `External ID` of a record is the unique identifier of this record in another application. The `External ID` must be unique across all records of all objects. It is a good practice to prefix this `External ID` with the name of the application or table. (like, 'company_1', 'person_1' - instead of '1')" +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:429 +msgid "As an example, suppose there is an SQL database with two tables that are to be imported: companies and people. Each person belongs to one company, so the link between a person and the company they work for must be recreated." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:433 +msgid "Test this example, with a :download:`sample of a PostgreSQL database `." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:436 +msgid "First, export all companies and their *External ID*. In PSQL, write the following command:" +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:442 +msgid "This SQL command creates the following :abbr:`CSV (Comma-separated Values)` file:" +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:451 +msgid "To create the :abbr:`CSV (Comma-separated Values)` file for people linked to companies, use the following SQL command in PSQL:" +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:458 +msgid "It produces the following :abbr:`CSV (Comma-separated Values)` file:" +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:468 +msgid "In this file, Fabien and Laurence are working for the Bigees company (`company_1`), and Eric is working for the Organi company. The relation between people and companies is done using the *External ID* of the companies. The *External ID* is prefixed by the name of the table to avoid a conflict of ID between people and companies (`person_1` and `company_1`, who shared the same ID 1 in the original database)." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:474 +msgid "The two files produced are ready to be imported in Odoo without any modifications. After having imported these two :abbr:`CSV (Comma-separated Values)` files, there are four contacts and three companies (the first two contacts are linked to the first company). Keep in mind to first import the companies, and then the people." +msgstr "" + +#: ../../content/applications/essentials/in_app_purchase.rst:3 +msgid "In-app purchase (IAP)" +msgstr "" + +#: ../../content/applications/essentials/in_app_purchase.rst:7 +msgid "In-app purchases (IAP) are optional services that enhance Odoo databases. Each service provides its own specific features and functionality. A full list of services is available on the `Odoo IAP Catalog `_." +msgstr "" + +#: ../../content/applications/essentials/in_app_purchase.rst:-1 +msgid "The IAP catalog with various services available on IAP.Odoo.com." +msgstr "" + +#: ../../content/applications/essentials/in_app_purchase.rst:16 +msgid "The :guilabel:`SMS` service sends text messages to contacts directly from the database, and the :guilabel:`Documents Digitization` service digitizes scanned or PDF vendor bills, expenses, and resumes with optical character recognition (OCR) and artificial intelligence (AI)." +msgstr "" + +#: ../../content/applications/essentials/in_app_purchase.rst:20 +msgid "|IAP| services do **not** need to be configured or set up before use. Odoo users can simply click on the service in the app to activate it. However, each service requires its own prepaid credits, and when they run out, users **must** :ref:`buy more ` in order to keep using it." +msgstr "" + +#: ../../content/applications/essentials/in_app_purchase.rst:25 +msgid "Users with an Enterprise version of Odoo Online get free credits to test IAP features." +msgstr "" + +#: ../../content/applications/essentials/in_app_purchase.rst:30 +msgid "IAP services" +msgstr "" + +#: ../../content/applications/essentials/in_app_purchase.rst:32 +msgid "|IAP| services are provided by Odoo, as well as third-parties, and have a wide range of uses." +msgstr "" + +#: ../../content/applications/essentials/in_app_purchase.rst:34 +msgid "The following |IAP| services are provided by Odoo:" +msgstr "" + +#: ../../content/applications/essentials/in_app_purchase.rst:36 +msgid ":guilabel:`Documents Digitization`: digitizes scanned or PDF vendor bills, expenses, and resumes with OCR and AI." +msgstr "" + +#: ../../content/applications/essentials/in_app_purchase.rst:38 +msgid ":guilabel:`Partner Autocomplete`: automatically populates contact records with corporate data." +msgstr "" + +#: ../../content/applications/essentials/in_app_purchase.rst:39 +msgid ":guilabel:`SMS`: sends SMS text messages to contacts directly from the database." +msgstr "" + +#: ../../content/applications/essentials/in_app_purchase.rst:40 +msgid ":guilabel:`Lead Generation`: generates leads based on a set of criteria, and converts web visitors into quality leads and opportunities." +msgstr "" + +#: ../../content/applications/essentials/in_app_purchase.rst:42 +msgid ":guilabel:`Snailmail`: sends customer invoices and follow-up reports by post, worldwide." +msgstr "" + +#: ../../content/applications/essentials/in_app_purchase.rst:44 +msgid "For more information on every service currently available, visit the `Odoo IAP Catalog `_." +msgstr "" + +#: ../../content/applications/essentials/in_app_purchase.rst:48 +msgid "Use IAP services" +msgstr "" + +#: ../../content/applications/essentials/in_app_purchase.rst:50 +msgid "|IAP| services are automatically integrated with Odoo, and do **not** require users to configure any settings. To use a service, simply interact with it wherever it appears in the database." +msgstr "" + +#: ../../content/applications/essentials/in_app_purchase.rst:54 +msgid "The following flow focuses on the *SMS* |IAP| service being used from a contact's record." +msgstr "" + +#: ../../content/applications/essentials/in_app_purchase.rst:56 +msgid "This can be done by clicking the :guilabel:`📱 (phone) SMS` icon within the database." +msgstr "" + +#: ../../content/applications/essentials/in_app_purchase.rst:-1 +msgid "The SMS icon on a typical contact information form located within an Odoo database." +msgstr "" + +#: ../../content/applications/essentials/in_app_purchase.rst:62 +msgid "One way to utilize the *SMS* |IAP| service with Odoo is showcased in the following steps:" +msgstr "" + +#: ../../content/applications/essentials/in_app_purchase.rst:64 +msgid "Navigate to the :menuselection:`Contacts application`, and click on a contact with a mobile phone number entered in either the :guilabel:`Phone` or :guilabel:`Mobile` field of the contact form." +msgstr "" + +#: ../../content/applications/essentials/in_app_purchase.rst:67 +msgid "Hover the mouse over the :guilabel:`Phone` or :guilabel:`Mobile` field, and a :guilabel:`📱 (phone) SMS` icon appears to the right." +msgstr "" + +#: ../../content/applications/essentials/in_app_purchase.rst:69 +msgid "Click the :guilabel:`📱 (phone) SMS` icon, and a :guilabel:`Send SMS Text Message` pop-up window appears." +msgstr "" + +#: ../../content/applications/essentials/in_app_purchase.rst:71 +msgid "Type a message in the :guilabel:`Message` field of the :guilabel:`Send SMS Text Message` pop-up window. Then, click the :guilabel:`Send SMS` button. Odoo then sends the message, via SMS, to the contact, and logs what was sent in the *chatter* of the contact's form." +msgstr "" + +#: ../../content/applications/essentials/in_app_purchase.rst:75 +msgid "Upon sending the SMS message, the prepaid credits for the *SMS* |IAP| service are automatically deducted from the existing credits. If there are not enough credits to send the message, Odoo prompts the user to purchase more." +msgstr "" + +#: ../../content/applications/essentials/in_app_purchase.rst:80 +msgid "For more information on how to use various |IAP| services, and for more in-depth instructions related to SMS functionality in Odoo, review the documentation below:" +msgstr "" + +#: ../../content/applications/essentials/in_app_purchase.rst:83 +msgid ":doc:`Lead mining `" +msgstr "" + +#: ../../content/applications/essentials/in_app_purchase.rst:84 +msgid ":doc:`Enrich your contacts base with Partner Autocomplete `" +msgstr "" + +#: ../../content/applications/essentials/in_app_purchase.rst:86 +msgid ":doc:`SMS essentials `" +msgstr "" + +#: ../../content/applications/essentials/in_app_purchase.rst:91 +msgid "IAP credits" +msgstr "" + +#: ../../content/applications/essentials/in_app_purchase.rst:93 +msgid "Every time an |IAP| service is used, the prepaid credits for that service are spent. Odoo prompts the purchase of more credits when there are not enough credits left to continue using a service. Email alerts can also be set up for when :ref:`credits are low `." +msgstr "" + +#: ../../content/applications/essentials/in_app_purchase.rst:97 +msgid "Credits are purchased in *Packs* from the `Odoo IAP Catalog `_, and pricing is specific to each service." +msgstr "" + +#: ../../content/applications/essentials/in_app_purchase.rst:101 +msgid "The `SMS service `_ has four packs available, in denominations of:" +msgstr "" + +#: ../../content/applications/essentials/in_app_purchase.rst:104 +msgid ":guilabel:`Starter Pack`: 10 credits" +msgstr "" + +#: ../../content/applications/essentials/in_app_purchase.rst:105 +msgid ":guilabel:`Standard Pack`: 100 credits" +msgstr "" + +#: ../../content/applications/essentials/in_app_purchase.rst:106 +msgid ":guilabel:`Advanced Pack`: 500 credits" +msgstr "" + +#: ../../content/applications/essentials/in_app_purchase.rst:107 +msgid ":guilabel:`Expert Pack`: 1,000 credits" +msgstr "" + +#: ../../content/applications/essentials/in_app_purchase.rst:-1 +msgid "Four different packs of credits for the SMS IAP service." +msgstr "" + +#: ../../content/applications/essentials/in_app_purchase.rst:113 +msgid "The number of credits consumed depends on the length of the SMS and the country of destination." +msgstr "" + +#: ../../content/applications/essentials/in_app_purchase.rst:115 +msgid "For more information, refer to the :doc:`SMS Pricing and FAQ ` documentation." +msgstr "" + +#: ../../content/applications/essentials/in_app_purchase.rst:121 +msgid "Buy credits" +msgstr "" + +#: ../../content/applications/essentials/in_app_purchase.rst:123 +msgid "If there are not enough credits to perform a task, the database automatically prompts the purchase of more credits." +msgstr "" + +#: ../../content/applications/essentials/in_app_purchase.rst:126 +msgid "Users can check the current balance of credits for each service, and manually purchase more credits, by navigating to the :menuselection:`Settings app --> Search IAP --> View My Services`." +msgstr "" + +#: ../../content/applications/essentials/in_app_purchase.rst:129 +#: ../../content/applications/essentials/in_app_purchase.rst:146 +msgid "Doing so reveals an :guilabel:`IAP Account` page, listing the various |IAP| services in the database. From here, click an |IAP| service to open its :guilabel:`Account Information` page, where additional credits can be purchased." +msgstr "" + +#: ../../content/applications/essentials/in_app_purchase.rst:134 +msgid "Manually buy credits" +msgstr "" + +#: ../../content/applications/essentials/in_app_purchase.rst:136 +msgid "To manually buy credits in Odoo, follow these steps:" +msgstr "" + +#: ../../content/applications/essentials/in_app_purchase.rst:138 +#: ../../content/applications/essentials/in_app_purchase.rst:173 +msgid "Go to the :menuselection:`Settings application`." +msgstr "" + +#: ../../content/applications/essentials/in_app_purchase.rst:139 +#: ../../content/applications/essentials/in_app_purchase.rst:174 +msgid "Type `IAP` in the search bar." +msgstr "" + +#: ../../content/applications/essentials/in_app_purchase.rst:140 +#: ../../content/applications/essentials/in_app_purchase.rst:175 +msgid "Click :guilabel:`View My Services`." +msgstr "" + +#: ../../content/applications/essentials/in_app_purchase.rst:0 +msgid "The Settings app showing the Odoo IAP heading and View My Services button." +msgstr "" + +#: ../../content/applications/essentials/in_app_purchase.rst:149 +msgid "On the :guilabel:`Account Information` page, click the :guilabel:`Buy Credit` button." +msgstr "" + +#: ../../content/applications/essentials/in_app_purchase.rst:0 +msgid "The Account Information page for an IAP service showing the Buy Credit button." +msgstr "" + +#: ../../content/applications/essentials/in_app_purchase.rst:155 +msgid "Doing so loads a :guilabel:`Buy Credits for (IAP Account)` page in a new tab. From here, click :guilabel:`Buy` on the desired pack of credits. Then, follow the prompts to enter payment details, and confirm the order." +msgstr "" + +#: ../../content/applications/essentials/in_app_purchase.rst:0 +msgid "The SMS service page on IAP.Odoo.com with four packs of credits available for purchase." +msgstr "" + +#: ../../content/applications/essentials/in_app_purchase.rst:163 +msgid "Once the transaction is complete, the credits are available for use in the database." +msgstr "" + +#: ../../content/applications/essentials/in_app_purchase.rst:168 +msgid "Low-credit notification" +msgstr "" + +#: ../../content/applications/essentials/in_app_purchase.rst:170 +msgid "It is possible to be notified when credits are low, in order to avoid running out of credits, while using an |IAP| service. To do that, follow this process:" +msgstr "" + +#: ../../content/applications/essentials/in_app_purchase.rst:176 +msgid "The available |IAP| accounts appear in a list view on the :guilabel:`IAP Account` page. From here, click on the desired |IAP| account to view that service's :guilabel:`Account Information` page." +msgstr "" + +#: ../../content/applications/essentials/in_app_purchase.rst:179 +msgid "On the :guilabel:`Account Information` page, tick the :guilabel:`Warn Me` box. Doing so reveals two fields on the form: :guilabel:`Threshold` and :guilabel:`Warning Email`." +msgstr "" + +#: ../../content/applications/essentials/in_app_purchase.rst:0 +msgid "Odoo will send an email alert when credits for this service fall below the threshold." +msgstr "" + +#: ../../content/applications/essentials/in_app_purchase.rst:186 +msgid "In the :guilabel:`Threshold` field, enter an amount of credits Odoo should use as the minimum threshold for this service." +msgstr "" + +#: ../../content/applications/essentials/in_app_purchase.rst:188 +msgid "In the :guilabel:`Warning Email` field, enter the email address that should receive the notification." +msgstr "" + +#: ../../content/applications/essentials/in_app_purchase.rst:191 +msgid "Odoo sends a low-credit alert to the :guilabel:`Warning Email` when the balance of credits falls below the amount listed as the :guilabel:`Threshold`." +msgstr "" + +#: ../../content/applications/essentials/reporting.rst:3 +msgid "Reporting" +msgstr "" + +#: ../../content/applications/essentials/reporting.rst:5 +msgid "You can find several reports under the :guilabel:`Reporting` menu of most apps that let you analyze and visualize the data of your records." +msgstr "" + +#: ../../content/applications/essentials/reporting.rst:11 +msgid "Selecting a view" +msgstr "" + +#: ../../content/applications/essentials/reporting.rst:13 +msgid "Depending on the report, Odoo can display the data in various ways. Sometimes, a unique view fully tailored to the report is available, while several views are available for others. However, two generic views are dedicated to reporting: the graph and pivot views." +msgstr "" + +#: ../../content/applications/essentials/reporting.rst:20 +msgid "Graph view" +msgstr "" + +#: ../../content/applications/essentials/reporting.rst:22 +msgid "The :ref:`graph view ` is used to visualize your records' data, helping you identify patterns and trends. The view is often found under the :guilabel:`Reporting` menu of apps but can be found elsewhere. Click the **graph view button** located at the top right to access it." +msgstr "" + +#: ../../content/applications/essentials/reporting.rst:-1 +msgid "Selecting the graph view" +msgstr "" + +#: ../../content/applications/essentials/reporting.rst:33 +msgid "Pivot view" +msgstr "" + +#: ../../content/applications/essentials/reporting.rst:35 +msgid "The :ref:`pivot view ` is used to aggregate your records' data and break it down for analysis. The view is often found under the :guilabel:`Reporting` menu of apps but can be found elsewhere. Click the **pivot view button** located at the top right to access it." +msgstr "" + +#: ../../content/applications/essentials/reporting.rst:-1 +msgid "Selecting the pivot view" +msgstr "" + +#: ../../content/applications/essentials/reporting.rst:45 +msgid "Choosing measures" +msgstr "" + +#: ../../content/applications/essentials/reporting.rst:47 +msgid "After selecting a view, you should ensure only the relevant records are :doc:`filtered `. Next, you should choose what is measured. By default, a measure is always selected. If you wish to edit it, click :guilabel:`Measures` and choose one or, only for pivots, multiple measures." +msgstr "" + +#: ../../content/applications/essentials/reporting.rst:52 +msgid "When you select a measure, Odoo aggregates the values recorded on that field for the filtered records. Only numerical fields (:ref:`integer `, :ref:`decimal `, :ref:`monetary `) can be measured. In addition, the :guilabel:`Count` option is used to count the total number of filtered records." +msgstr "" + +#: ../../content/applications/essentials/reporting.rst:58 +msgid "After choosing what you want to measure, you can define how the data should be :ref:`grouped ` depending on the dimension you want to analyze. By default, the data is often grouped by *Date > Month*, which is used to analyze the evolution of a measure over the months." +msgstr "" + +#: ../../content/applications/essentials/reporting.rst:63 +msgid "When you filter a single time period, the option to compare it against another one appears." +msgstr "" + +#: ../../content/applications/essentials/reporting.rst:0 +msgid "Using the comparison option" +msgstr "" + +#: ../../content/applications/essentials/reporting.rst:72 +msgid "Select measures" +msgstr "" + +#: ../../content/applications/essentials/reporting.rst:74 +msgid "Among other measures, you could add the :guilabel:`Margin` and :guilabel:`Count` measures to the Sales Analysis report. By default, the :guilabel:`Untaxed Amount` measure is selected." +msgstr "" + +#: ../../content/applications/essentials/reporting.rst:0 +msgid "Selecting different measures on the Sales Analysis report" +msgstr "" + +#: ../../content/applications/essentials/reporting.rst:81 +msgid "Group measures" +msgstr "" + +#: ../../content/applications/essentials/reporting.rst:83 +msgid "You could group the measures by :guilabel:`Product Category` at the level of rows on the previous Sales Analysis report example." +msgstr "" + +#: ../../content/applications/essentials/reporting.rst:0 +msgid "Adding a group on the Sales Analysis report" +msgstr "" + +#: ../../content/applications/essentials/reporting.rst:92 +msgid "Using the pivot view" +msgstr "" + +#: ../../content/applications/essentials/reporting.rst:94 +msgid "Grouping data is quintessential to the pivot view. It enables drilling down the data to gain deeper insights. While you can use the :guilabel:`Group By` option to quickly add a group at the level of rows, as shown in the example above, you can also click the plus button (:guilabel:`➕`) next to the :guilabel:`Total` header at the level of rows *and* columns, and then select one of the **preconfigured groups**. To remove one, click the minus button (:guilabel:`➖`)." +msgstr "" + +#: ../../content/applications/essentials/reporting.rst:100 +msgid "Once you have added a group, you can add new ones on the opposite axis or the newly created subgroups." +msgstr "" + +#: ../../content/applications/essentials/reporting.rst:104 +msgid "You could further divide the measures on the previous Sales Analysis report example by the :guilabel:`Salesperson` group at the level of columns and by the :guilabel:`Order Date > Month` group on the :guilabel:`All / Saleable / Office Furniture` product category." +msgstr "" + +#: ../../content/applications/essentials/reporting.rst:0 +msgid "Adding multiple groups on the Sales Analysis report" +msgstr "" + +#: ../../content/applications/essentials/reporting.rst:112 +msgid "Switch the rows and columns' groups by clicking the flip axis button (:guilabel:`⇄`)." +msgstr "" + +#: ../../content/applications/essentials/reporting.rst:113 +msgid "Click on a measure's label to sort the values by ascending (⏶) or descending (⏷) order." +msgstr "" + +#: ../../content/applications/essentials/reporting.rst:114 +msgid "Download a `.xlsx` version of the pivot by clicking the download button (:guilabel:`⭳`)." +msgstr "" + +#: ../../content/applications/essentials/reporting.rst:119 +msgid "Using the graph view" +msgstr "" + +#: ../../content/applications/essentials/reporting.rst:121 +msgid "Three graphs are available: the bar, line, and pie charts." +msgstr "" + +#: ../../content/applications/essentials/reporting.rst:123 +msgid "**Bar charts** are used to show the distribution or a comparison of several categories. They are especially useful as they can deal with larger data sets." +msgstr "" + +#: ../../content/applications/essentials/reporting.rst:126 +msgid "**Line charts** are useful to show changing time series and trends over time." +msgstr "" + +#: ../../content/applications/essentials/reporting.rst:128 +msgid "**Pie charts** are used to show the distribution or a comparison of a small number of categories when they form a meaningful whole." +msgstr "" + +#: ../../content/applications/essentials/reporting.rst:133 +msgid "Bar chart" +msgstr "" + +#: ../../content/applications/essentials/reporting.rst:0 +msgid "Viewing the Sales Analysis report as a bar chart" +msgstr "" + +#: ../../content/applications/essentials/reporting.rst:138 +msgid "Line chart" +msgstr "" + +#: ../../content/applications/essentials/reporting.rst:0 +msgid "Viewing the Sales Analysis report as a line chart" +msgstr "" + +#: ../../content/applications/essentials/reporting.rst:143 +msgid "Pie chart" +msgstr "" + +#: ../../content/applications/essentials/reporting.rst:0 +msgid "Viewing the Sales Analysis report as a pie chart" +msgstr "" + +#: ../../content/applications/essentials/reporting.rst:149 +msgid "For **bar** and **line** charts, you can use the stacked option when you have at least two groups, which then appear on top of each other instead of next to each other." +msgstr "" + +#: ../../content/applications/essentials/reporting.rst:154 +msgid "Stacked bar chart" +msgstr "" + +#: ../../content/applications/essentials/reporting.rst:0 +msgid "Stacked bar chart example" +msgstr "" + +#: ../../content/applications/essentials/reporting.rst:159 +msgid "Regular bar chart" +msgstr "" + +#: ../../content/applications/essentials/reporting.rst:0 +msgid "Non-stacked bar chart example" +msgstr "" + +#: ../../content/applications/essentials/reporting.rst:164 +msgid "Stacked line chart" +msgstr "" + +#: ../../content/applications/essentials/reporting.rst:0 +msgid "Stacked line chart example" +msgstr "" + +#: ../../content/applications/essentials/reporting.rst:169 +#: ../../content/applications/essentials/reporting.rst:184 +msgid "Regular line chart" +msgstr "" + +#: ../../content/applications/essentials/reporting.rst:0 +msgid "Non-stacked line chart example" +msgstr "" + +#: ../../content/applications/essentials/reporting.rst:174 +msgid "For **line** charts, you can use the cumulative option to sum values, which is especially useful to show the change in growth over a time period." +msgstr "" + +#: ../../content/applications/essentials/reporting.rst:179 +msgid "Cumulative line chart" +msgstr "" + +#: ../../content/applications/essentials/reporting.rst:0 +msgid "Cumulative line chart example" +msgstr "" + +#: ../../content/applications/essentials/reporting.rst:0 +msgid "Regular line chart example" +msgstr "" + +#: ../../content/applications/essentials/search.rst:3 +msgid "Search and filter records" +msgstr "" + +#: ../../content/applications/essentials/search.rst:5 +msgid "Odoo uses filters to include only the most relevant records depending on the purpose of the view you are on. However, you can edit the default filter or search for specific values." +msgstr "" + +#: ../../content/applications/essentials/search.rst:11 +msgid "Preconfigured filters" +msgstr "" + +#: ../../content/applications/essentials/search.rst:13 +msgid "You can modify the default selection of records by clicking :guilabel:`Filters` and selecting one or several **preconfigured filters**." +msgstr "" + +#: ../../content/applications/essentials/search.rst:17 +msgid "On the Sales Analysis report, only records at the sales order stage are selected by default. However, you could *also* include records at the quotation stage by selecting :guilabel:`Quotations`. Furthermore, you could *only* include records from a specific year, for example *2022*, by selecting :menuselection:`Order Date --> 2022`." +msgstr "" + +#: ../../content/applications/essentials/search.rst:0 +msgid "Using preconfigured filters on the Sales Analysis report" +msgstr "" + +#: ../../content/applications/essentials/search.rst:27 +msgid "If you select preconfigured filters from the same group (i.e., that are *not* separated by an horizontal line), the records can match *any* condition to be included. However, if you select filters from different groups, the records have to match *all* condition to be included." +msgstr "" + +#: ../../content/applications/essentials/search.rst:34 +msgid "Custom filters" +msgstr "" + +#: ../../content/applications/essentials/search.rst:36 +msgid "You can create custom filters using most fields present on the model by clicking :menuselection:`Filters --> Add Custom Filter`, selecting a field, an operator, a value, and clicking :guilabel:`Apply`." +msgstr "" + +#: ../../content/applications/essentials/search.rst:41 +msgid "You could *only* include records from a single salesperson on the Sales Analysis report, for example *Mitchell Admin*, by selecting :guilabel:`Salesperson` as the field, :guilabel:`is equal to` as the operator, and typing `Mitchell Admin` as the value." +msgstr "" + +#: ../../content/applications/essentials/search.rst:0 +msgid "Using a custom filter on the Sales Analysis report" +msgstr "" + +#: ../../content/applications/essentials/search.rst:50 +msgid "If the records should *only* match one of several conditions, click :guilabel:`Add a condition` before applying a custom filter. If the records should match *all* conditions, add new custom filters instead." +msgstr "" + +#: ../../content/applications/essentials/search.rst:57 +msgid "Search for values" +msgstr "" + +#: ../../content/applications/essentials/search.rst:59 +msgid "You can use the search field to quickly look for specific values and add them as a filter. Either type the full value you are searching for and select the desired field, or type a part of the value, click the dropdown button (:guilabel:`⏵`) before the chosen field, and select the exact value you are looking for." +msgstr "" + +#: ../../content/applications/essentials/search.rst:65 +msgid "Instead of adding a custom filter to select records where *Mitchell Admin* is the salesperson on the Sales Analysis report, you could search for `Mitch`, click the dropdown button (:guilabel:`⏵`) next to :guilabel:`Search Salesperson for: Mitch`, and select :guilabel:`Mitchell Admin`." +msgstr "" + +#: ../../content/applications/essentials/search.rst:0 +msgid "Searching for a specific value on the Sales Analysis report" +msgstr "" + +#: ../../content/applications/essentials/search.rst:75 +msgid "Using the search field is equivalent to using the *contains* operator when adding a custom filter. If you enter a partial value and directly select the desired field, *all* records containing the characters you typed for the selected field will be included." +msgstr "" + +#: ../../content/applications/essentials/search.rst:82 +msgid "Group records" +msgstr "" + +#: ../../content/applications/essentials/search.rst:84 +msgid "You can click :guilabel:`Group By` below the search field to cluster records together according to one of the **preconfigured groups**." +msgstr "" + +#: ../../content/applications/essentials/search.rst:88 +msgid "You could group the records by salesperson on the Sales Analysis report by clicking :guilabel:`Group By` and selecting :guilabel:`Salesperson`. No records are filtered out." +msgstr "" + +#: ../../content/applications/essentials/search.rst:0 +msgid "Grouping records on the Sales Analysis report" +msgstr "" + +#: ../../content/applications/essentials/search.rst:95 +msgid "You can **customize groups** by using a wide selection of fields present on the model. To do so, click :menuselection:`Group By --> Add Custom Group`, select a field, and click :guilabel:`Apply`." +msgstr "" + +#: ../../content/applications/essentials/search.rst:99 +msgid "You can use several groups at the same time. The first group you select is the main cluster, the next one you add further divides the main group's categories, and so on." +msgstr "" diff --git a/locale/sources/finance.pot b/locale/sources/finance.pot index 1d0367d94..97f262d1c 100644 --- a/locale/sources/finance.pot +++ b/locale/sources/finance.pot @@ -8,7 +8,7 @@ msgid "" msgstr "" "Project-Id-Version: Odoo 17.0\n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2024-03-08 12:48+0000\n" +"POT-Creation-Date: 2024-03-25 16:01+0000\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME \n" "Language-Team: LANGUAGE \n" @@ -140,12 +140,12 @@ msgid "Statement" msgstr "" #: ../../content/applications/finance/accounting.rst:135 -#: ../../content/applications/finance/accounting/customer_invoices.rst:216 +#: ../../content/applications/finance/accounting/customer_invoices.rst:214 msgid "Balance sheet" msgstr "" #: ../../content/applications/finance/accounting.rst:137 -#: ../../content/applications/finance/accounting/customer_invoices.rst:206 +#: ../../content/applications/finance/accounting/customer_invoices.rst:204 msgid "Profit and loss" msgstr "" @@ -437,7 +437,6 @@ msgstr "" #: ../../content/applications/finance/accounting/taxes/retention.rst:11 #: ../../content/applications/finance/accounting/vendor_bills/deferred_expenses.rst:29 #: ../../content/applications/finance/accounting/vendor_bills/invoice_digitization.rst:18 -#: ../../content/applications/finance/documents.rst:16 #: ../../content/applications/finance/fiscal_localizations.rst:21 #: ../../content/applications/finance/fiscal_localizations/argentina.rst:17 #: ../../content/applications/finance/fiscal_localizations/argentina.rst:894 @@ -448,8 +447,8 @@ msgstr "" #: ../../content/applications/finance/fiscal_localizations/austria.rst:6 #: ../../content/applications/finance/fiscal_localizations/austria.rst:45 #: ../../content/applications/finance/fiscal_localizations/belgium.rst:8 -#: ../../content/applications/finance/fiscal_localizations/belgium.rst:255 -#: ../../content/applications/finance/fiscal_localizations/belgium.rst:528 +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:256 +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:532 #: ../../content/applications/finance/fiscal_localizations/brazil.rst:28 #: ../../content/applications/finance/fiscal_localizations/colombia.rst:21 #: ../../content/applications/finance/fiscal_localizations/ecuador.rst:34 @@ -1558,6 +1557,8 @@ msgstr "" msgid "This model should be at the top of the *sequence* of models, as it enables Odoo to suggest matching existing invoices or bills with a bank transaction based on set conditions." msgstr "" +#: ../../content/applications/finance/accounting/bank/reconciliation_models.rst:-1 +#: ../../content/applications/finance/accounting/bank/reconciliation_models.rst:-1 #: ../../content/applications/finance/accounting/bank/reconciliation_models.rst:-1 msgid "Set rules to trigger the reconciliation." msgstr "" @@ -1687,7 +1688,7 @@ msgid "After setting the necessary formatting options and mapping the file colum msgstr "" #: ../../content/applications/finance/accounting/bank/transactions.rst:42 -msgid ":doc:`/applications/general/export_import_data`" +msgid ":doc:`/applications/essentials/export_import_data`" msgstr "" #: ../../content/applications/finance/accounting/bank/transactions.rst:47 @@ -1788,104 +1789,100 @@ msgid "Draft invoices" msgstr "" #: ../../content/applications/finance/accounting/customer_invoices.rst:49 -msgid "The system generates invoice which are initially set to the Draft state. While these invoices" +msgid "The system generates invoice which are initially set to the Draft state. While these invoices remain unvalidated, they have no accounting impact within the system. There is nothing to stop users from creating their own draft invoices." msgstr "" -#: ../../content/applications/finance/accounting/customer_invoices.rst:52 -msgid "remain unvalidated, they have no accounting impact within the system. There is nothing to stop users from creating their own draft invoices." -msgstr "" - -#: ../../content/applications/finance/accounting/customer_invoices.rst:55 +#: ../../content/applications/finance/accounting/customer_invoices.rst:53 msgid "Let's create a customer invoice with following information:" msgstr "" -#: ../../content/applications/finance/accounting/customer_invoices.rst:57 +#: ../../content/applications/finance/accounting/customer_invoices.rst:55 msgid "Customer: Agrolait" msgstr "" -#: ../../content/applications/finance/accounting/customer_invoices.rst:58 +#: ../../content/applications/finance/accounting/customer_invoices.rst:56 msgid "Product: iMac" msgstr "" -#: ../../content/applications/finance/accounting/customer_invoices.rst:59 +#: ../../content/applications/finance/accounting/customer_invoices.rst:57 msgid "Quantity: 1" msgstr "" -#: ../../content/applications/finance/accounting/customer_invoices.rst:60 +#: ../../content/applications/finance/accounting/customer_invoices.rst:58 msgid "Unit Price: 100" msgstr "" -#: ../../content/applications/finance/accounting/customer_invoices.rst:61 +#: ../../content/applications/finance/accounting/customer_invoices.rst:59 msgid "Taxes: Tax 15%" msgstr "" -#: ../../content/applications/finance/accounting/customer_invoices.rst:67 +#: ../../content/applications/finance/accounting/customer_invoices.rst:65 msgid "The document is composed of three parts:" msgstr "" -#: ../../content/applications/finance/accounting/customer_invoices.rst:69 +#: ../../content/applications/finance/accounting/customer_invoices.rst:67 msgid "the top of the invoice, with customer information," msgstr "" -#: ../../content/applications/finance/accounting/customer_invoices.rst:70 +#: ../../content/applications/finance/accounting/customer_invoices.rst:68 msgid "the main body of the invoice, with detailed invoice lines," msgstr "" -#: ../../content/applications/finance/accounting/customer_invoices.rst:71 +#: ../../content/applications/finance/accounting/customer_invoices.rst:69 msgid "the bottom of the page, with detail about the taxes, and the totals." msgstr "" -#: ../../content/applications/finance/accounting/customer_invoices.rst:74 +#: ../../content/applications/finance/accounting/customer_invoices.rst:72 msgid "Open or Pro-forma invoices" msgstr "" -#: ../../content/applications/finance/accounting/customer_invoices.rst:76 +#: ../../content/applications/finance/accounting/customer_invoices.rst:74 msgid "An invoice will usually include the quantity and the price of goods and/or services, the date, any parties involved, the unique invoice number, and any tax information." msgstr "" -#: ../../content/applications/finance/accounting/customer_invoices.rst:80 +#: ../../content/applications/finance/accounting/customer_invoices.rst:78 msgid "\"Validate\" the invoice when you are ready to approve it. The invoice then moves from the Draft state to the Open state." msgstr "" -#: ../../content/applications/finance/accounting/customer_invoices.rst:83 +#: ../../content/applications/finance/accounting/customer_invoices.rst:81 msgid "When you have validated an invoice, Odoo gives it a unique number from a defined, and modifiable, sequence." msgstr "" -#: ../../content/applications/finance/accounting/customer_invoices.rst:88 +#: ../../content/applications/finance/accounting/customer_invoices.rst:86 msgid "Accounting entries corresponding to this invoice are automatically generated when you validate the invoice. You can see the details by clicking on the entry in the Journal Entry field in the \"Other Info\" tab." msgstr "" -#: ../../content/applications/finance/accounting/customer_invoices.rst:96 +#: ../../content/applications/finance/accounting/customer_invoices.rst:94 msgid "Send the invoice to customer" msgstr "" -#: ../../content/applications/finance/accounting/customer_invoices.rst:98 +#: ../../content/applications/finance/accounting/customer_invoices.rst:96 msgid "After validating the customer invoice, you can directly send it to the customer via the 'Send by email' functionality." msgstr "" -#: ../../content/applications/finance/accounting/customer_invoices.rst:103 +#: ../../content/applications/finance/accounting/customer_invoices.rst:101 msgid "A typical journal entry generated from a validated invoice will look like as follows:" msgstr "" -#: ../../content/applications/finance/accounting/customer_invoices.rst:107 -#: ../../content/applications/finance/accounting/customer_invoices.rst:128 +#: ../../content/applications/finance/accounting/customer_invoices.rst:105 +#: ../../content/applications/finance/accounting/customer_invoices.rst:126 #: ../../content/applications/finance/accounting/payments/internal_transfers.rst:39 #: ../../content/applications/finance/accounting/payments/internal_transfers.rst:56 msgid "**Account**" msgstr "" -#: ../../content/applications/finance/accounting/customer_invoices.rst:107 -#: ../../content/applications/finance/accounting/customer_invoices.rst:128 +#: ../../content/applications/finance/accounting/customer_invoices.rst:105 +#: ../../content/applications/finance/accounting/customer_invoices.rst:126 msgid "**Partner**" msgstr "" -#: ../../content/applications/finance/accounting/customer_invoices.rst:107 -#: ../../content/applications/finance/accounting/customer_invoices.rst:128 +#: ../../content/applications/finance/accounting/customer_invoices.rst:105 +#: ../../content/applications/finance/accounting/customer_invoices.rst:126 msgid "**Due date**" msgstr "" -#: ../../content/applications/finance/accounting/customer_invoices.rst:107 -#: ../../content/applications/finance/accounting/customer_invoices.rst:128 +#: ../../content/applications/finance/accounting/customer_invoices.rst:105 +#: ../../content/applications/finance/accounting/customer_invoices.rst:126 #: ../../content/applications/finance/accounting/payments/internal_transfers.rst:40 #: ../../content/applications/finance/accounting/payments/internal_transfers.rst:57 #: ../../content/applications/finance/accounting/taxes/cash_basis.rst:68 @@ -1894,8 +1891,8 @@ msgstr "" msgid "**Debit**" msgstr "" -#: ../../content/applications/finance/accounting/customer_invoices.rst:107 -#: ../../content/applications/finance/accounting/customer_invoices.rst:128 +#: ../../content/applications/finance/accounting/customer_invoices.rst:105 +#: ../../content/applications/finance/accounting/customer_invoices.rst:126 #: ../../content/applications/finance/accounting/payments/internal_transfers.rst:41 #: ../../content/applications/finance/accounting/payments/internal_transfers.rst:58 #: ../../content/applications/finance/accounting/taxes/cash_basis.rst:68 @@ -1904,31 +1901,31 @@ msgstr "" msgid "**Credit**" msgstr "" -#: ../../content/applications/finance/accounting/customer_invoices.rst:109 -#: ../../content/applications/finance/accounting/customer_invoices.rst:132 +#: ../../content/applications/finance/accounting/customer_invoices.rst:107 +#: ../../content/applications/finance/accounting/customer_invoices.rst:130 #: ../../content/applications/finance/accounting/get_started/cheat_sheet.rst:170 #: ../../content/applications/finance/fiscal_localizations/united_arab_emirates.rst:58 msgid "Accounts Receivable" msgstr "" +#: ../../content/applications/finance/accounting/customer_invoices.rst:107 #: ../../content/applications/finance/accounting/customer_invoices.rst:109 -#: ../../content/applications/finance/accounting/customer_invoices.rst:111 +#: ../../content/applications/finance/accounting/customer_invoices.rst:128 #: ../../content/applications/finance/accounting/customer_invoices.rst:130 -#: ../../content/applications/finance/accounting/customer_invoices.rst:132 msgid "Agrolait" msgstr "" -#: ../../content/applications/finance/accounting/customer_invoices.rst:109 +#: ../../content/applications/finance/accounting/customer_invoices.rst:107 msgid "01/07/2015" msgstr "" -#: ../../content/applications/finance/accounting/customer_invoices.rst:109 +#: ../../content/applications/finance/accounting/customer_invoices.rst:107 +#: ../../content/applications/finance/accounting/customer_invoices.rst:128 #: ../../content/applications/finance/accounting/customer_invoices.rst:130 -#: ../../content/applications/finance/accounting/customer_invoices.rst:132 msgid "115" msgstr "" -#: ../../content/applications/finance/accounting/customer_invoices.rst:111 +#: ../../content/applications/finance/accounting/customer_invoices.rst:109 #: ../../content/applications/finance/accounting/taxes.rst:5 #: ../../content/applications/finance/fiscal_localizations/argentina.rst:169 #: ../../content/applications/finance/fiscal_localizations/belgium.rst:32 @@ -1946,12 +1943,12 @@ msgstr "" msgid "Taxes" msgstr "" -#: ../../content/applications/finance/accounting/customer_invoices.rst:111 +#: ../../content/applications/finance/accounting/customer_invoices.rst:109 #: ../../content/applications/finance/fiscal_localizations/france.rst:96 msgid "15" msgstr "" -#: ../../content/applications/finance/accounting/customer_invoices.rst:113 +#: ../../content/applications/finance/accounting/customer_invoices.rst:111 #: ../../content/applications/finance/accounting/customer_invoices/overview.rst:16 #: ../../content/applications/finance/fiscal_localizations/australia.rst:142 #: ../../content/applications/finance/fiscal_localizations/australia.rst:146 @@ -1966,7 +1963,7 @@ msgstr "" msgid "Sales" msgstr "" -#: ../../content/applications/finance/accounting/customer_invoices.rst:113 +#: ../../content/applications/finance/accounting/customer_invoices.rst:111 #: ../../content/applications/finance/accounting/get_started/cheat_sheet.rst:172 #: ../../content/applications/finance/accounting/get_started/cheat_sheet.rst:226 #: ../../content/applications/finance/accounting/get_started/cheat_sheet.rst:228 @@ -1978,19 +1975,19 @@ msgstr "" msgid "100" msgstr "" -#: ../../content/applications/finance/accounting/customer_invoices.rst:117 +#: ../../content/applications/finance/accounting/customer_invoices.rst:115 msgid "Payment" msgstr "" -#: ../../content/applications/finance/accounting/customer_invoices.rst:119 +#: ../../content/applications/finance/accounting/customer_invoices.rst:117 msgid "In Odoo, an invoice is considered to be paid when the associated accounting entry has been reconciled with the payment entries. If there has not been a reconciliation, the invoice will remain in the Open state until you have entered the payment." msgstr "" -#: ../../content/applications/finance/accounting/customer_invoices.rst:124 +#: ../../content/applications/finance/accounting/customer_invoices.rst:122 msgid "A typical journal entry generated from a payment will look like as follows:" msgstr "" -#: ../../content/applications/finance/accounting/customer_invoices.rst:130 +#: ../../content/applications/finance/accounting/customer_invoices.rst:128 #: ../../content/applications/finance/accounting/get_started/cheat_sheet.rst:238 #: ../../content/applications/finance/accounting/get_started/cheat_sheet.rst:254 #: ../../content/applications/finance/accounting/payments/checks.rst:108 @@ -1999,75 +1996,75 @@ msgstr "" msgid "Bank" msgstr "" -#: ../../content/applications/finance/accounting/customer_invoices.rst:136 +#: ../../content/applications/finance/accounting/customer_invoices.rst:134 msgid "Receive a partial payment through the bank statement" msgstr "" -#: ../../content/applications/finance/accounting/customer_invoices.rst:138 +#: ../../content/applications/finance/accounting/customer_invoices.rst:136 msgid "You can manually enter your bank statements in Odoo, or you can import them in from a csv file or from several other predefined formats according to your accounting localisation." msgstr "" -#: ../../content/applications/finance/accounting/customer_invoices.rst:142 +#: ../../content/applications/finance/accounting/customer_invoices.rst:140 msgid "Create a bank statement from the accounting dashboard with the related journal and enter an amount of $100 ." msgstr "" -#: ../../content/applications/finance/accounting/customer_invoices.rst:148 +#: ../../content/applications/finance/accounting/customer_invoices.rst:146 msgid "Reconcile" msgstr "" -#: ../../content/applications/finance/accounting/customer_invoices.rst:150 +#: ../../content/applications/finance/accounting/customer_invoices.rst:148 msgid "Now let's reconcile!" msgstr "" -#: ../../content/applications/finance/accounting/customer_invoices.rst:154 +#: ../../content/applications/finance/accounting/customer_invoices.rst:152 msgid "You can now go through every transaction and reconcile them or you can mass reconcile with instructions at the bottom." msgstr "" -#: ../../content/applications/finance/accounting/customer_invoices.rst:156 +#: ../../content/applications/finance/accounting/customer_invoices.rst:154 msgid "After reconciling the items in the sheet, the related invoice will now display \"You have outstanding payments for this customer. You can reconcile them to pay this invoice. \"" msgstr "" -#: ../../content/applications/finance/accounting/customer_invoices.rst:164 +#: ../../content/applications/finance/accounting/customer_invoices.rst:162 msgid "Apply the payment. Below, you can see that the payment has been added to the invoice." msgstr "" -#: ../../content/applications/finance/accounting/customer_invoices.rst:170 +#: ../../content/applications/finance/accounting/customer_invoices.rst:168 msgid "Payment Followup" msgstr "" -#: ../../content/applications/finance/accounting/customer_invoices.rst:172 +#: ../../content/applications/finance/accounting/customer_invoices.rst:170 msgid "There's a growing trend of customers paying bills later and later. Therefore, collectors must make every effort to collect money and collect it faster." msgstr "" -#: ../../content/applications/finance/accounting/customer_invoices.rst:176 +#: ../../content/applications/finance/accounting/customer_invoices.rst:174 msgid "Odoo will help you define your follow-up strategy. To remind customers to pay their outstanding invoices, you can define different actions depending on how severely overdue the customer is. These actions are bundled into follow-up levels that are triggered when the due date of an invoice has passed a certain number of days. If there are other overdue invoices for the same customer, the actions of the most overdue invoice will be executed." msgstr "" -#: ../../content/applications/finance/accounting/customer_invoices.rst:184 +#: ../../content/applications/finance/accounting/customer_invoices.rst:182 msgid "By going to the customer record and diving into the \"Overdue Payments\" you will see the follow-up message and all overdue invoices." msgstr "" -#: ../../content/applications/finance/accounting/customer_invoices.rst:194 +#: ../../content/applications/finance/accounting/customer_invoices.rst:192 msgid "Customer aging report:" msgstr "" -#: ../../content/applications/finance/accounting/customer_invoices.rst:196 +#: ../../content/applications/finance/accounting/customer_invoices.rst:194 msgid "The customer aging report will be an additional key tool for the collector to understand the customer credit issues, and to prioritize their work." msgstr "" -#: ../../content/applications/finance/accounting/customer_invoices.rst:200 +#: ../../content/applications/finance/accounting/customer_invoices.rst:198 msgid "Use the aging report to determine which customers are overdue and begin your collection efforts." msgstr "" -#: ../../content/applications/finance/accounting/customer_invoices.rst:208 +#: ../../content/applications/finance/accounting/customer_invoices.rst:206 msgid "The Profit and Loss statement displays your revenue and expense details. Ultimately, this gives you a clear image of your Net Profit and Loss. It is sometimes referred to as the \"Income Statement\" or \"Statement of Revenues and Expenses.\"" msgstr "" -#: ../../content/applications/finance/accounting/customer_invoices.rst:218 +#: ../../content/applications/finance/accounting/customer_invoices.rst:216 msgid "The balance sheet summarizes your company's liabilities, assets and equity at a specific moment in time." msgstr "" -#: ../../content/applications/finance/accounting/customer_invoices.rst:225 +#: ../../content/applications/finance/accounting/customer_invoices.rst:223 msgid "For example, if you manage your inventory using the perpetual accounting method, you should expect a decrease in account \"Current Assets\" once the material has been shipped to the customer." msgstr "" @@ -2525,7 +2522,7 @@ msgid "Emails also go to different addresses. The quotation and sales order are msgstr "" #: ../../content/applications/finance/accounting/customer_invoices/customer_addresses.rst:36 -msgid "Reports, such as the delivery slip and invoice report, can be :doc:`customized using Studio `." +msgid "Reports, such as the delivery slip and invoice report, can be :doc:`customized using Studio `." msgstr "" #: ../../content/applications/finance/accounting/customer_invoices/customer_addresses.rst:38 @@ -3959,12 +3956,12 @@ msgid "Pingen (Odoo Snailmail service provider) scans the area to process the ad msgstr "" #: ../../content/applications/finance/accounting/customer_invoices/snailmail.rst:45 -#: ../../content/applications/finance/accounting/vendor_bills/invoice_digitization.rst:84 +#: ../../content/applications/finance/accounting/vendor_bills/invoice_digitization.rst:85 msgid "Pricing" msgstr "" #: ../../content/applications/finance/accounting/customer_invoices/snailmail.rst:47 -msgid "Snailmail is an :doc:`/applications/general/in_app_purchase` service that requires prepaid stamps (=credits) to work. Sending one document consumes one stamp." +msgid "Snailmail is an :doc:`/applications/essentials/in_app_purchase` service that requires prepaid stamps (=credits) to work. Sending one document consumes one stamp." msgstr "" #: ../../content/applications/finance/accounting/customer_invoices/snailmail.rst:50 @@ -3972,7 +3969,7 @@ msgid "To buy stamps, go to :menuselection:`Accounting --> Configuration --> Set msgstr "" #: ../../content/applications/finance/accounting/customer_invoices/snailmail.rst:55 -#: ../../content/applications/finance/accounting/vendor_bills/invoice_digitization.rst:94 +#: ../../content/applications/finance/accounting/vendor_bills/invoice_digitization.rst:95 msgid "If you are on Odoo Online and have the Enterprise version, you benefit from free trial credits to test the feature." msgstr "" @@ -4401,6 +4398,8 @@ msgid "Avg Cost" msgstr "" #: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:91 +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:91 +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:275 #: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:275 #: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:279 #: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:283 @@ -4412,6 +4411,7 @@ msgstr "" #: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:91 #: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:275 #: ../../content/applications/finance/fiscal_localizations/france.rst:240 +#: ../../content/applications/finance/fiscal_localizations/france.rst:240 msgid "0" msgstr "" @@ -4467,14 +4467,17 @@ msgstr "" #: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:97 #: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:197 #: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:199 +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:199 #: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:238 #: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:240 +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:240 #: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:242 #: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:281 #: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:283 #: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:285 #: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:287 #: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:289 +#: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:289 msgid "$12" msgstr "" @@ -5140,6 +5143,7 @@ msgstr "" msgid "Non-current Liabilities" msgstr "" +#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:78 #: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:78 msgid "Equity" msgstr "" @@ -5155,6 +5159,7 @@ msgstr "" msgid "Profit & Loss" msgstr "" +#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:82 #: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:82 msgid "Income" msgstr "" @@ -5163,6 +5168,7 @@ msgstr "" msgid "Other Income" msgstr "" +#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:86 #: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:86 msgid "Expense" msgstr "" @@ -5175,6 +5181,7 @@ msgstr "" msgid "Cost of Revenue" msgstr "" +#: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:92 #: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:92 msgid "Other" msgstr "" @@ -5213,8 +5220,6 @@ msgid "In the :guilabel:`View` menu of an account, select a **default tax** to b msgstr "" #: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:117 -#: ../../content/applications/finance/documents.rst:52 -#: ../../content/applications/finance/sign.rst:236 msgid "Tags" msgstr "" @@ -6473,11 +6478,12 @@ msgid "You can send reminder emails in batches from the :guilabel:`Follow-up Rep msgstr "" #: ../../content/applications/finance/accounting/payments/follow_up.rst:93 -msgid ":doc:`../../../general/in_app_purchase`" +#: ../../content/applications/finance/accounting/vendor_bills/invoice_digitization.rst:100 +msgid ":doc:`/applications/essentials/in_app_purchase`" msgstr "" #: ../../content/applications/finance/accounting/payments/follow_up.rst:94 -msgid ":doc:`../../../marketing/sms_marketing/pricing/pricing_and_faq`" +msgid ":doc:`/applications/marketing/sms_marketing/pricing/pricing_and_faq`" msgstr "" #: ../../content/applications/finance/accounting/payments/follow_up.rst:95 @@ -6693,7 +6699,7 @@ msgid "If you use Odoo on Odoo.com or Odoo.sh platform, your code is already up- msgstr "" #: ../../content/applications/finance/accounting/payments/online/install_portal_patch.rst:28 -msgid "If you use Odoo with an on-premise setup or through a partner, you must update your installation as detailed in :doc:`this documentation page `, or by contacting your integrating partner." +msgid "If you use Odoo with an on-premise setup or through a partner, you must update your installation as detailed in :doc:`this documentation page `, or by contacting your integrating partner." msgstr "" #: ../../content/applications/finance/accounting/payments/online/install_portal_patch.rst:33 @@ -8782,8 +8788,11 @@ msgstr "" msgid "Total" msgstr "" +#: ../../content/applications/finance/accounting/taxes.rst:97 #: ../../content/applications/finance/accounting/taxes.rst:97 #: ../../content/applications/finance/accounting/taxes.rst:112 +#: ../../content/applications/finance/accounting/taxes.rst:112 +#: ../../content/applications/finance/accounting/taxes.rst:127 #: ../../content/applications/finance/accounting/taxes.rst:127 #: ../../content/applications/finance/accounting/taxes.rst:271 msgid "1,000" @@ -9063,18 +9072,46 @@ msgid "The taxes' sequence in Odoo determines which tax is applied first" msgstr "" #: ../../content/applications/finance/accounting/taxes.rst:311 -msgid ":doc:`taxes/fiscal_positions`" -msgstr "" - -#: ../../content/applications/finance/accounting/taxes.rst:312 -msgid ":doc:`taxes/B2B_B2C`" +msgid "Extra taxes" msgstr "" #: ../../content/applications/finance/accounting/taxes.rst:313 +msgid "\"Extra taxes\" is a broad term referring to additional taxes beyond the standard or basic taxes imposed by governments. These extra taxes can be **luxury** taxes, **environmental** taxes, **import** or **export duties** taxes, etc." +msgstr "" + +#: ../../content/applications/finance/accounting/taxes.rst:318 +msgid "The method to compute these taxes varies across different countries. We recommend consulting your country's regulations to understand how to calculate them for your business." +msgstr "" + +#: ../../content/applications/finance/accounting/taxes.rst:321 +msgid "To compute an extra tax in Odoo, :ref:`create a tax `, enter a tax name, select a :ref:`Tax Computation `, set an :guilabel:`Amount`, and in the :guilabel:`Advanced Options` tab, check :guilabel:`Affect Base of Subsequent Taxes`. Then, drag and drop the taxes in the :ref:`order they should be computed `." +msgstr "" + +#: ../../content/applications/finance/accounting/taxes.rst:327 +msgid "In Belgium, the formula to compute an environmental tax is: `(product price + environmental tax) x sales tax`. Therefore, our environmental tax has to come *before* the sales tax in the computation sequence." +msgstr "" + +#: ../../content/applications/finance/accounting/taxes.rst:330 +msgid "In our case, we created a 5% environmental tax (Ecotax) and put it *before* the Belgian base tax of 21%." +msgstr "" + +#: ../../content/applications/finance/accounting/taxes.rst:0 +msgid "Environmental tax sequence in Belgium." +msgstr "" + +#: ../../content/applications/finance/accounting/taxes.rst:337 +msgid ":doc:`taxes/fiscal_positions`" +msgstr "" + +#: ../../content/applications/finance/accounting/taxes.rst:338 +msgid ":doc:`taxes/B2B_B2C`" +msgstr "" + +#: ../../content/applications/finance/accounting/taxes.rst:339 msgid ":doc:`taxes/taxcloud`" msgstr "" -#: ../../content/applications/finance/accounting/taxes.rst:314 +#: ../../content/applications/finance/accounting/taxes.rst:340 msgid ":doc:`reporting/tax_returns`" msgstr "" @@ -9758,7 +9795,7 @@ msgstr "" #: ../../content/applications/finance/fiscal_localizations/argentina.rst:592 #: ../../content/applications/finance/fiscal_localizations/brazil.rst:463 #: ../../content/applications/finance/fiscal_localizations/chile.rst:700 -#: ../../content/applications/finance/fiscal_localizations/italy.rst:279 +#: ../../content/applications/finance/fiscal_localizations/italy.rst:119 msgid "Vendor bills" msgstr "" @@ -10373,484 +10410,47 @@ msgid "The email alias is now available in the :guilabel:`Advanced Settings` tab msgstr "" #: ../../content/applications/finance/accounting/vendor_bills/invoice_digitization.rst:55 -msgid "If you use the :doc:`Documents <../../documents>` app, you can automatically send your scanned invoices to the :guilabel:`Finance` workspace (e.g., `inbox-financial@example.odoo.com`)." +msgid "If you use the :doc:`Documents ` app, you can automatically send your scanned invoices to the :guilabel:`Finance` workspace (e.g., `inbox-financial@example.odoo.com`)." msgstr "" -#: ../../content/applications/finance/accounting/vendor_bills/invoice_digitization.rst:58 +#: ../../content/applications/finance/accounting/vendor_bills/invoice_digitization.rst:59 msgid "The default email aliases `vendor-bills@` and `customer-invoices@` followed by the :guilabel:`Alias Domain` you set are automatically created for the :guilabel:`Vendor Bills` and :guilabel:`Customer Invoices` journals, respectively. Emails sent to these addresses are converted automatically into new invoices or bills." msgstr "" -#: ../../content/applications/finance/accounting/vendor_bills/invoice_digitization.rst:63 +#: ../../content/applications/finance/accounting/vendor_bills/invoice_digitization.rst:64 msgid "To change a default email alias, go to :menuselection:`Accounting --> Configuration --> Accounting: Journals`. Select the journal you want to edit, click on the :guilabel:`Advanced Settings` tab, and edit the `Email Alias`." msgstr "" -#: ../../content/applications/finance/accounting/vendor_bills/invoice_digitization.rst:68 +#: ../../content/applications/finance/accounting/vendor_bills/invoice_digitization.rst:69 msgid "Invoice digitization" msgstr "" -#: ../../content/applications/finance/accounting/vendor_bills/invoice_digitization.rst:70 +#: ../../content/applications/finance/accounting/vendor_bills/invoice_digitization.rst:71 msgid "According to your settings, the document is either processed automatically, or you need to click on :guilabel:`Send for digitization` to do it manually." msgstr "" -#: ../../content/applications/finance/accounting/vendor_bills/invoice_digitization.rst:73 +#: ../../content/applications/finance/accounting/vendor_bills/invoice_digitization.rst:74 msgid "Once the data is extracted from the PDF, you can correct it if necessary by clicking on the respective tags (available in :guilabel:`Edit` mode) and selecting the proper information instead." msgstr "" -#: ../../content/applications/finance/accounting/vendor_bills/invoice_digitization.rst:77 +#: ../../content/applications/finance/accounting/vendor_bills/invoice_digitization.rst:78 msgid "Data recognition with AI" msgstr "" -#: ../../content/applications/finance/accounting/vendor_bills/invoice_digitization.rst:79 +#: ../../content/applications/finance/accounting/vendor_bills/invoice_digitization.rst:80 msgid "It is essential to review and correct (if needed) the information uploaded during digitization. Then, you have to post the document by clicking on :guilabel:`Confirm`. In this manner, the AI learns, and the system identifies the correct data for future digitizations." msgstr "" -#: ../../content/applications/finance/accounting/vendor_bills/invoice_digitization.rst:86 +#: ../../content/applications/finance/accounting/vendor_bills/invoice_digitization.rst:87 msgid "The **invoice digitization** is an In-App Purchase (IAP) service that requires prepaid credits to work. Digitizing one document consumes one credit." msgstr "" -#: ../../content/applications/finance/accounting/vendor_bills/invoice_digitization.rst:89 +#: ../../content/applications/finance/accounting/vendor_bills/invoice_digitization.rst:90 msgid "To buy credits, go to :menuselection:`Accounting --> Configuration --> Settings --> Digitization` and click on :guilabel:`Buy credits`, or go to :menuselection:`Settings --> Odoo IAP` and click on :guilabel:`View My Services`." msgstr "" -#: ../../content/applications/finance/accounting/vendor_bills/invoice_digitization.rst:98 -msgid "`Our Privacy Policy `_" -msgstr "" - #: ../../content/applications/finance/accounting/vendor_bills/invoice_digitization.rst:99 -msgid ":doc:`/applications/general/in_app_purchase`" -msgstr "" - -#: ../../content/applications/finance/documents.rst:3 -msgid "Documents" -msgstr "" - -#: ../../content/applications/finance/documents.rst:5 -msgid "**Odoo Documents** allows you to store, view, and manage files within Odoo." -msgstr "" - -#: ../../content/applications/finance/documents.rst:7 -msgid "You can upload any file (max 64MB per file on Odoo Online) and organize them in various workspaces." -msgstr "" - -#: ../../content/applications/finance/documents.rst:10 -msgid "`Odoo Documents: product page `_" -msgstr "" - -#: ../../content/applications/finance/documents.rst:11 -msgid "`Odoo Tutorials: Documents basics [video] `_" -msgstr "" - -#: ../../content/applications/finance/documents.rst:13 -msgid "`Odoo Tutorials: Using Documents with your Accounting App [video] `_" -msgstr "" - -#: ../../content/applications/finance/documents.rst:18 -msgid "By going to :menuselection:`Documents --> Configuration --> Settings`, you can enable the centralization of files attached to a specific area of your activity. For example, by ticking :guilabel:`Human Resources`, your HR documents are automatically available in the HR workspace, while documents related to Payroll are automatically available in the Payroll sub-workspace . You can change the default workspace using the dropdown menu and edit its properties by clicking the internal link button (:guilabel:`➔`)." -msgstr "" - -#: ../../content/applications/finance/documents.rst:-1 -msgid "Enable the centralization of files attached to a specific area of your activity." -msgstr "" - -#: ../../content/applications/finance/documents.rst:29 -msgid "If you enable the centralization of your accounting files and documents, it is necessary to click on :guilabel:`Journals` and define each journal independently to allow automatic synchronization." -msgstr "" - -#: ../../content/applications/finance/documents.rst:0 -msgid "Enable the centralization of files attached to your accounting." -msgstr "" - -#: ../../content/applications/finance/documents.rst:36 -msgid "If you select a new workspace, existing documents aren't moved. Only newly created documents will be found under the new workspace." -msgstr "" - -#: ../../content/applications/finance/documents.rst:40 -msgid "Workspaces" -msgstr "" - -#: ../../content/applications/finance/documents.rst:42 -msgid "Workspaces are hierarchical folders having their own set of tags and :ref:`actions `. Default workspaces exist, but you can create your own by going to :menuselection:`Documents --> Configuration --> Workspaces` and clicking :guilabel:`New`. On the new page, fill in the following information:" -msgstr "" - -#: ../../content/applications/finance/documents.rst:47 -#: ../../content/applications/finance/fiscal_localizations/chile.rst:232 -#: ../../content/applications/finance/fiscal_localizations/chile.rst:1047 -#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:78 -#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:271 -msgid ":guilabel:`Name`" -msgstr "" - -#: ../../content/applications/finance/documents.rst:48 -msgid ":guilabel:`Parent Workspace`: if you want to create a sub-workspace, select its :guilabel:`Parent Workspace`" -msgstr "" - -#: ../../content/applications/finance/documents.rst:54 -msgid "Tags are used within workspaces to add a level of differentiation between documents. They are organized per category, and filters can be used to sort them." -msgstr "" - -#: ../../content/applications/finance/documents.rst:57 -msgid "Tags can be created from the :guilabel:`Tags` tab. Click :guilabel:`Add a line`, create the :guilabel:`Tag Category`, and :guilabel:`Name` your tags." -msgstr "" - -#: ../../content/applications/finance/documents.rst:61 -msgid "The tags of a parent workspace apply to the child workspaces automatically;" -msgstr "" - -#: ../../content/applications/finance/documents.rst:62 -msgid "Tags can be created and modified by going to :menuselection:`Configuration --> Tags`;" -msgstr "" - -#: ../../content/applications/finance/documents.rst:63 -msgid "Tags can also be created or edited by clicking the gear icon :guilabel:`⚙` on the left menu." -msgstr "" - -#: ../../content/applications/finance/documents.rst:66 -msgid "Access rights" -msgstr "" - -#: ../../content/applications/finance/documents.rst:68 -msgid "To manage your workspace access rights, go to :menuselection:`Documents --> Configuration --> Workspaces`, open the workspace you want to edit, and go to the :guilabel:`Access Rights` tab. You can add :guilabel:`Write Groups` that can view, create, and edit the workspace's documents. You can also add :guilabel:`Read Groups` that can only view the workspace's documents." -msgstr "" - -#: ../../content/applications/finance/documents.rst:74 -#: ../../content/applications/finance/fiscal_localizations/argentina.rst:31 -#: ../../content/applications/finance/fiscal_localizations/australia.rst:16 -#: ../../content/applications/finance/fiscal_localizations/australia.rst:100 -#: ../../content/applications/finance/fiscal_localizations/austria.rst:16 -#: ../../content/applications/finance/fiscal_localizations/chile.rst:32 -#: ../../content/applications/finance/fiscal_localizations/colombia.rst:35 -#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:48 -#: ../../content/applications/finance/fiscal_localizations/egypt.rst:18 -#: ../../content/applications/finance/fiscal_localizations/france.rst:59 -#: ../../content/applications/finance/fiscal_localizations/india.rst:18 -#: ../../content/applications/finance/fiscal_localizations/italy.rst:19 -#: ../../content/applications/finance/fiscal_localizations/kenya.rst:18 -#: ../../content/applications/finance/fiscal_localizations/kenya.rst:36 -#: ../../content/applications/finance/fiscal_localizations/luxembourg.rst:16 -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:73 -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:117 -#: ../../content/applications/finance/fiscal_localizations/romania.rst:16 -#: ../../content/applications/finance/fiscal_localizations/saudi_arabia.rst:17 -#: ../../content/applications/finance/fiscal_localizations/thailand.rst:16 -#: ../../content/applications/finance/fiscal_localizations/united_arab_emirates.rst:18 -#: ../../content/applications/finance/fiscal_localizations/united_kingdom.rst:16 -msgid "Description" -msgstr "" - -#: ../../content/applications/finance/documents.rst:76 -msgid "You can add descriptive information to your workspace by going to :menuselection:`Documents --> Configuration --> Workspaces`, opening the workspace you want to describe and going to the :guilabel:`Description` tab." -msgstr "" - -#: ../../content/applications/finance/documents.rst:81 -msgid "Workspaces can also be created and edited by clicking the gear icon :guilabel:`⚙` on the left menu." -msgstr "" - -#: ../../content/applications/finance/documents.rst:0 -msgid "Create sub-workspaces from the left menu" -msgstr "" - -#: ../../content/applications/finance/documents.rst:88 -msgid "Documents management" -msgstr "" - -#: ../../content/applications/finance/documents.rst:90 -msgid "When selecting or opening a document, the right panel displays different options. On the top, additional options might be available: :guilabel:`Download`, :guilabel:`Share`, :guilabel:`Replace`, :guilabel:`Lock` or :guilabel:`Split`. It is also possible to :guilabel:`Open chatter` or :guilabel:`Archive` the document." -msgstr "" - -#: ../../content/applications/finance/documents.rst:-1 -msgid "right panel options" -msgstr "" - -#: ../../content/applications/finance/documents.rst:99 -msgid "Then, you can modify the name of your file by clicking on :guilabel:`Document`. A :guilabel:`Contact` or an :guilabel:`Owner` can be assigned. The related :guilabel:`Workspace` can be modified and it is possible to access the related :guilabel:`Journal Entry` or add :guilabel:`Tags`." -msgstr "" - -#: ../../content/applications/finance/documents.rst:105 -msgid "The :guilabel:`Contact` is the person related to the document and assigned to it. He can only view the document and not modify it. I.e.: an existing supplier in your database is the contact for their bill." -msgstr "" - -#: ../../content/applications/finance/documents.rst:108 -msgid "The person who creates a document is, by default :guilabel:`Owner` of it and has complete rights to it. It is possible to replace the owner of a document. I.e., an employee must be owner of a document to be able to see it in \"My Profile\"." -msgstr "" - -#: ../../content/applications/finance/documents.rst:112 -msgid "Different :ref:`Actions ` are available at the bottom of the right panel, depending on the workspace where your document is stored." -msgstr "" - -#: ../../content/applications/finance/documents.rst:116 -msgid "Split PDF documents" -msgstr "" - -#: ../../content/applications/finance/documents.rst:118 -msgid "Select the PDF you want to split, and click the scissors icon. A new view displays all the pages of the document." -msgstr "" - -#: ../../content/applications/finance/documents.rst:121 -msgid "By default, each page of the document will be split when clicking :guilabel:`Split`. To remove a split between two pages, click on the scissors icon." -msgstr "" - -#: ../../content/applications/finance/documents.rst:-1 -msgid "split your documents" -msgstr "" - -#: ../../content/applications/finance/documents.rst:128 -msgid "To merge documents from your dashboard, select them and click the scissors icon. Click on the scissors between the two documents and click :guilabel:`Split` to merge the documents." -msgstr "" - -#: ../../content/applications/finance/documents.rst:132 -msgid "Additional features" -msgstr "" - -#: ../../content/applications/finance/documents.rst:134 -msgid "Select a workspace and click the arrow next to the :guilabel:`Upload` button to access additional features:" -msgstr "" - -#: ../../content/applications/finance/documents.rst:138 -msgid "Request" -msgstr "" - -#: ../../content/applications/finance/documents.rst:140 -msgid "You can create \"missing documents\" and organize them as documents, to remind users to download them." -msgstr "" - -#: ../../content/applications/finance/documents.rst:142 -msgid "Select the workspace where the file should be stored, click :guilabel:`Upload`, then :guilabel:`Request`. Add the :guilabel:`Document Name`, select the person you need it from in the :guilabel:`Request To` field, fill in the :guilabel:`Due Date In`, confirm the :guilabel:`Workspace`, the document should belong to, and add :guilabel:`Tags` and a :guilabel:`Note`, if needed. Then, click :guilabel:`Request`. A placeholder for the missing document is created in the workspace." -msgstr "" - -#: ../../content/applications/finance/documents.rst:149 -msgid "When your document is available, click the placeholder to upload it." -msgstr "" - -#: ../../content/applications/finance/documents.rst:151 -msgid "You can see all missing documents by going to the **Activity** view and to the :guilabel:`Requested Document` column." -msgstr "" - -#: ../../content/applications/finance/documents.rst:155 -msgid "From the :guilabel:`Activity` view, you can send a **reminder email** to users from whom you are expecting a document. Go to the :guilabel:`Requested Document` column, click on ⋮ and :guilabel:`Document Request: Reminder`." -msgstr "" - -#: ../../content/applications/finance/documents.rst:159 -msgid "Click on a date to see the details of a specific request. You can update it by clicking on the pen icon, :guilabel:`Preview` the content of the reminder email, or :guilabel:`Send Now` to send a reminder email." -msgstr "" - -#: ../../content/applications/finance/documents.rst:0 -msgid "send a reminder email from the Activity view" -msgstr "" - -#: ../../content/applications/finance/documents.rst:167 -msgid "Add a link" -msgstr "" - -#: ../../content/applications/finance/documents.rst:169 -msgid "To add a link to your documents dashboard, click on :guilabel:`Add a Link`, enter the :guilabel:`URL`, and :guilabel:`Name` it." -msgstr "" - -#: ../../content/applications/finance/documents.rst:173 -msgid "Share" -msgstr "" - -#: ../../content/applications/finance/documents.rst:175 -msgid "You can create a share link to a document or all documents of a workspace. It allows anyone to download the file(s) or upload files to a workspace." -msgstr "" - -#: ../../content/applications/finance/documents.rst:178 -msgid "To do so, select the workspace or the document and click the arrow next to the :guilabel:`Upload` button then :guilabel:`Share`. On the pop-up, the share :guilabel:`URL` is displayed. :guilabel:`Copy` it to share it with anyone. :guilabel:`Name` the share link and set a validity date for the URL by filling in the :guilabel:`Valid Until` field. Tick the :guilabel:`Include Sub Folders` box if you also want to share a workspace's sub-folders. To let users upload their own documents, select :guilabel:`Download and Upload`." -msgstr "" - -#: ../../content/applications/finance/documents.rst:186 -msgid "It is possible to only share one or more documents (without their workspace) by selecting them and clicking :guilabel:`Share`." -msgstr "" - -#: ../../content/applications/finance/documents.rst:190 -msgid "New spreadsheet" -msgstr "" - -#: ../../content/applications/finance/documents.rst:192 -msgid "To create a new :doc:`spreadsheet `, click :guilabel:`New Spreadsheet`. You can select a :guilabel:`Blank spreadsheet` or an :doc:`existing template `." -msgstr "" - -#: ../../content/applications/finance/documents.rst:198 -msgid "Workflow actions" -msgstr "" - -#: ../../content/applications/finance/documents.rst:200 -msgid "Workflow actions help manage documents and overall business operations. These are automated actions that can be created and customized for each workspace. With a single click you can, for example, create, move, sign, and add tags to a document, and process bills." -msgstr "" - -#: ../../content/applications/finance/documents.rst:204 -msgid "These workflow actions appear on the right panel when a document meets the set criteria." -msgstr "" - -#: ../../content/applications/finance/documents.rst:207 -msgid "Create workflow actions" -msgstr "" - -#: ../../content/applications/finance/documents.rst:209 -msgid "To create workflow actions, go to :menuselection:`Documents --> Configuration --> Actions` and click :guilabel:`New`." -msgstr "" - -#: ../../content/applications/finance/documents.rst:213 -msgid "An action applies to all **sub-workspaces** under the :guilabel:`Related Workspace` you selected." -msgstr "" - -#: ../../content/applications/finance/documents.rst:216 -msgid "Set the conditions" -msgstr "" - -#: ../../content/applications/finance/documents.rst:218 -msgid "You can :guilabel:`Create` a new :guilabel:`Action` or edit an existing one. You can define the :guilabel:`Action Name` and then set the conditions that trigger the appearance of the action button (:guilabel:`▶`) on the right-side panel when selecting a file." -msgstr "" - -#: ../../content/applications/finance/documents.rst:222 -msgid "There are three basic types of conditions you can set:" -msgstr "" - -#: ../../content/applications/finance/documents.rst:224 -msgid ":guilabel:`Tags`: you can use the :guilabel:`Contains` and :guilabel:`Does not contain` conditions, meaning the files *must have* or *mustn't have* the tags set here." -msgstr "" - -#: ../../content/applications/finance/documents.rst:227 -msgid ":guilabel:`Contact`: the files must be associated with the contact set here." -msgstr "" - -#: ../../content/applications/finance/documents.rst:229 -msgid ":guilabel:`Owner`: the files must be associated with the owner set here." -msgstr "" - -#: ../../content/applications/finance/documents.rst:-1 -msgid "Example of a workflow action's basic condition in Odoo Documents" -msgstr "" - -#: ../../content/applications/finance/documents.rst:235 -msgid "If you don't set any conditions, the action button appears for all files inside the selected workspace." -msgstr "" - -#: ../../content/applications/finance/documents.rst:239 -msgid "Advanced condition type: domain" -msgstr "" - -#: ../../content/applications/finance/documents.rst:242 -msgid "It is recommended to have some knowledge of Odoo development to configure *Domain* filters properly." -msgstr "" - -#: ../../content/applications/finance/documents.rst:245 -msgid "The :ref:`developer mode ` needs to be activated to access the :guilabel:`Domain` condition from the :guilabel:`Actions` tab. Once done, select the :guilabel:`Domain` condition type and click :guilabel:`Add condition`." -msgstr "" - -#: ../../content/applications/finance/documents.rst:249 -msgid "To create a rule, you typically select a :guilabel:`field`, an :guilabel:`operator`, and a :guilabel:`value`. For example, if you want to add a workflow action to all the PDF files inside a workspace, set the :guilabel:`field` to *Mime Type*, the :guilabel:`operator` to *contains*, and the pdf :guilabel:`value`." -msgstr "" - -#: ../../content/applications/finance/documents.rst:-1 -msgid "Example of a workflow action's domain condition in Odoo Documents" -msgstr "" - -#: ../../content/applications/finance/documents.rst:257 -msgid "Click :guilabel:`Add New Rule` (plus icon) and :guilabel:`Add branch` to add conditions and sub-conditions. You can then specify if your rule should match :guilabel:`all` or :guilabel:`any` conditions. You can also edit the rule directly using the :guilabel:`Code editor`." -msgstr "" - -#: ../../content/applications/finance/documents.rst:262 -msgid "Configure the actions" -msgstr "" - -#: ../../content/applications/finance/documents.rst:264 -msgid "Select the :guilabel:`Actions` tab to set up your action. You can simultaneously:" -msgstr "" - -#: ../../content/applications/finance/documents.rst:266 -msgid "**Set Contact**: add a contact to the file, or replace an existing contact with a new one." -msgstr "" - -#: ../../content/applications/finance/documents.rst:267 -msgid "**Set Owner**: add an owner to the file, or replace an existing owner with a new one." -msgstr "" - -#: ../../content/applications/finance/documents.rst:268 -msgid "**Move to Workspace**: move the file to any workspace." -msgstr "" - -#: ../../content/applications/finance/documents.rst:269 -msgid "**Create**: create one of the following items attached to the file in your database:" -msgstr "" - -#: ../../content/applications/finance/documents.rst:271 -msgid "**Link to record**: link the document to a record (i.e. link to a vehicle in Fleet);" -msgstr "" - -#: ../../content/applications/finance/documents.rst:272 -msgid "**Product template**: create a product you can edit directly;" -msgstr "" - -#: ../../content/applications/finance/documents.rst:273 -msgid "**Task**: create a Project task you can edit directly;" -msgstr "" - -#: ../../content/applications/finance/documents.rst:274 -msgid "**Signature PDF template**: create a new Sign template to send out;" -msgstr "" - -#: ../../content/applications/finance/documents.rst:275 -msgid "**PDF to sign**: create a PDF to sign;" -msgstr "" - -#: ../../content/applications/finance/documents.rst:276 -msgid "**Applicant**: create a new HR application you can edit directly;" -msgstr "" - -#: ../../content/applications/finance/documents.rst:277 -msgid "**Vendor bill**: create a vendor bill using OCR and AI to scrape information from the file content;" -msgstr "" - -#: ../../content/applications/finance/documents.rst:279 -msgid "**Customer invoice**: create a customer invoice using OCR and AI to scrape information from the file;" -msgstr "" - -#: ../../content/applications/finance/documents.rst:281 -msgid "**Vendor credit note**: create a vendor credit note using OCR and AI to scrape information from the file;" -msgstr "" - -#: ../../content/applications/finance/documents.rst:283 -msgid "**Credit note**: create a customer credit note using OCR and AI to scrape information from the file;" -msgstr "" - -#: ../../content/applications/finance/documents.rst:285 -msgid "**Miscellaneous Operations**: create a record in :guilabel:`Miscellaneous Operations` in Accounting;" -msgstr "" - -#: ../../content/applications/finance/documents.rst:287 -msgid "**Bank Statement**: create a Bank Statement in Finance;" -msgstr "" - -#: ../../content/applications/finance/documents.rst:288 -msgid "**Expense**: create an expense automatically based on a file's content." -msgstr "" - -#: ../../content/applications/finance/documents.rst:290 -msgid "**Set Tags**: add, remove, and replace any number of tags." -msgstr "" - -#: ../../content/applications/finance/documents.rst:291 -msgid "**Activities - Mark all as Done**: mark all activities linked to the file as done." -msgstr "" - -#: ../../content/applications/finance/documents.rst:292 -msgid "**Activities - Schedule Activity**: create a new activity linked to the file as configured in the action. You can choose to set the activity on the document owner." -msgstr "" - -#: ../../content/applications/finance/documents.rst:-1 -msgid "Example of a workflow action Odoo Documents" -msgstr "" - -#: ../../content/applications/finance/documents.rst:299 -msgid "Digitize documents with AI and optical character recognition (OCR)" -msgstr "" - -#: ../../content/applications/finance/documents.rst:301 -msgid "Documents available in the Finance workspace can be digitized. Select the document to digitize, click :guilabel:`Create Bill`, :guilabel:`Create Customer Invoice`, or :guilabel:`Create credit note`, and then click :guilabel:`Send for Digitization`." -msgstr "" - -#: ../../content/applications/finance/documents.rst:306 -msgid ":doc:`AI-powered document digitization <../finance/accounting/vendor_bills/invoice_digitization>`" +msgid "`Our Privacy Policy `_" msgstr "" #: ../../content/applications/finance/expenses.rst:5 @@ -10877,6 +10477,7 @@ msgstr "" msgid "The first step to track expenses is to configure the different types of expenses for the company (managed as *expense categories* in Odoo). Each category can be as specific or generalized as needed. Go to :menuselection:`Expenses app --> Configuration --> Expense Categories` to view the current expensable categories in a default list view." msgstr "" +#: ../../content/applications/finance/expenses.rst:-1 #: ../../content/applications/finance/expenses.rst:-1 msgid "Set expense costs on products." msgstr "" @@ -11076,7 +10677,7 @@ msgid "Create the domain alias by clicking the link." msgstr "" #: ../../content/applications/finance/expenses.rst:217 -msgid "If the domain alias needs to be set up, :guilabel:`Setup your domain alias` will appear beneath the incoming emails check box instead of the email address field. Refer to this documentation for setup instructions and more information: :doc:`/administration/maintain/domain_names`. Once the domain alias is configured, the email address field will be visible beneath the incoming emails section." +msgid "If the domain alias needs to be set up, :guilabel:`Setup your domain alias` will appear beneath the incoming emails check box instead of the email address field. Refer to this documentation for setup instructions and more information: :doc:`/applications/websites/website/configuration/domain_names`. Once the domain alias is configured, the email address field will be visible beneath the incoming emails section." msgstr "" #: ../../content/applications/finance/expenses.rst:223 @@ -11252,7 +10853,7 @@ msgid ":guilabel:`Settings`: The user has access to the entire *Settings* app wi msgstr "" #: ../../content/applications/finance/expenses.rst:394 -msgid "Please refer to :doc:`this document ` to learn more about managing users and their access rights." +msgid "Please refer to :doc:`this document ` to learn more about managing users and their access rights." msgstr "" #: ../../content/applications/finance/expenses.rst:397 @@ -11928,6 +11529,30 @@ msgstr "" msgid "Technical name" msgstr "" +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:31 +#: ../../content/applications/finance/fiscal_localizations/australia.rst:16 +#: ../../content/applications/finance/fiscal_localizations/australia.rst:100 +#: ../../content/applications/finance/fiscal_localizations/austria.rst:16 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:32 +#: ../../content/applications/finance/fiscal_localizations/colombia.rst:35 +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:48 +#: ../../content/applications/finance/fiscal_localizations/egypt.rst:18 +#: ../../content/applications/finance/fiscal_localizations/france.rst:59 +#: ../../content/applications/finance/fiscal_localizations/india.rst:18 +#: ../../content/applications/finance/fiscal_localizations/italy.rst:19 +#: ../../content/applications/finance/fiscal_localizations/kenya.rst:18 +#: ../../content/applications/finance/fiscal_localizations/kenya.rst:36 +#: ../../content/applications/finance/fiscal_localizations/luxembourg.rst:16 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:73 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:117 +#: ../../content/applications/finance/fiscal_localizations/romania.rst:16 +#: ../../content/applications/finance/fiscal_localizations/saudi_arabia.rst:17 +#: ../../content/applications/finance/fiscal_localizations/thailand.rst:16 +#: ../../content/applications/finance/fiscal_localizations/united_arab_emirates.rst:18 +#: ../../content/applications/finance/fiscal_localizations/united_kingdom.rst:16 +msgid "Description" +msgstr "" + #: ../../content/applications/finance/fiscal_localizations/argentina.rst:32 msgid ":guilabel:`Argentina - Accounting`" msgstr "" @@ -11988,6 +11613,7 @@ msgstr "" msgid "Once the localization modules are installed, the first step is to set up the company's data. In addition to the basic information, a key field to fill in is the :guilabel:`AFIP Responsibility Type`, which represents the fiscal obligation and structure of the company." msgstr "" +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:-1 #: ../../content/applications/finance/fiscal_localizations/argentina.rst:-1 msgid "Select AFIP Responsibility Type." msgstr "" @@ -14591,7 +14217,7 @@ msgstr "" #: ../../content/applications/finance/fiscal_localizations/austria.rst:52 #: ../../content/applications/finance/fiscal_localizations/chile.rst:68 -#: ../../content/applications/finance/fiscal_localizations/italy.rst:41 +#: ../../content/applications/finance/fiscal_localizations/italy.rst:37 #: ../../content/applications/finance/fiscal_localizations/saudi_arabia.rst:38 msgid "Company information" msgstr "" @@ -14885,6 +14511,8 @@ msgstr "" msgid "In Belgium, 31% of **restaurant** expenses are non-deductible. Create a new **disallowed expenses category** and set both :guilabel:`Related Account(s)` and :guilabel:`Current Rate`." msgstr "" +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:-1 +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:-1 #: ../../content/applications/finance/fiscal_localizations/belgium.rst:-1 msgid "Disallowed expenses categories" msgstr "" @@ -14950,7 +14578,7 @@ msgid "CODA" msgstr "" #: ../../content/applications/finance/fiscal_localizations/belgium.rst:218 -msgid "**CODA** is an electronic XML format used to import Belgian bank statements. You can download CODA files from your bank and import them directly into Odoo by clicking :guilabel:`Import Statement` from your :guilabel:`Bank` journal on your dashboard." +msgid "**CODA** is an electronic XML format used to import Belgian bank statements. You can download CODA files from your bank and import them directly into Odoo by clicking :guilabel:`Import file` from your :guilabel:`Bank` journal on your dashboard." msgstr "" #: ../../content/applications/finance/fiscal_localizations/belgium.rst:-1 @@ -14958,7 +14586,7 @@ msgid "Import CODA files" msgstr "" #: ../../content/applications/finance/fiscal_localizations/belgium.rst:226 -msgid ":ref:`Import bank statements files `" +msgid ":ref:`Import bank files `" msgstr "" #: ../../content/applications/finance/fiscal_localizations/belgium.rst:231 @@ -14986,19 +14614,19 @@ msgid "**CodaBox** is a service that allows Belgian accounting firms to access t msgstr "" #: ../../content/applications/finance/fiscal_localizations/belgium.rst:251 -msgid "As an accounting firm, you must manage your clients on separate databases and configure them individually to avoid mixing up their data." +msgid "As an accounting firm, you must manage your clients on separate databases and configure them individually to avoid mixing up their data. The connection must be made by the accounting firm with valid CodaBox Connect credentials." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/belgium.rst:257 +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:258 msgid "The configuration must be done on each client database. In the following instructions, we will refer to your client's company as *Company* and to your accounting firm as *Accounting Firm*." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/belgium.rst:261 +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:262 msgid "You must first :ref:`install ` :guilabel:`CodaBox` and :guilabel:`CodaBox Bridge Wizard` (if available) to start." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/belgium.rst:265 -msgid "Make sure the company settings are correctly configured, i.e., the country is set to :guilabel:`Belgium`, the :guilabel:`Tax ID` and :guilabel:`Accounting Firm` fields are filled, as well as the :guilabel:`Tax ID` of the accounting firm (if not filled, the :guilabel:`Tax ID` of the company is used)." +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:266 +msgid "Make sure the company settings are correctly configured, i.e., the country is set to :guilabel:`Belgium`, the :guilabel:`Tax ID` and :guilabel:`Accounting Firm` fields are filled, as well as the :guilabel:`Tax ID` of the :guilabel:`Accounting Firm`." msgstr "" #: ../../content/applications/finance/fiscal_localizations/belgium.rst:271 @@ -15006,7 +14634,7 @@ msgid "Configure the journals" msgstr "" #: ../../content/applications/finance/fiscal_localizations/belgium.rst:275 -#: ../../content/applications/finance/fiscal_localizations/belgium.rst:326 +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:330 msgid "For CODA files" msgstr "" @@ -15026,21 +14654,25 @@ msgstr "" msgid "Configuration of a CODA journal." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/belgium.rst:285 -#: ../../content/applications/finance/fiscal_localizations/belgium.rst:332 +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:286 +msgid "When working with bank transactions that use different currencies, it is recommended to create multiple journals with the same bank account but different currencies." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:289 +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:336 msgid "For SODA files" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/belgium.rst:287 +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:291 msgid "Create a new miscellaneous journal." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/belgium.rst:288 -#: ../../content/applications/finance/fiscal_localizations/belgium.rst:301 +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:292 +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:305 msgid "Go to :menuselection:`Accounting --> Configuration --> Settings`, then go to the :guilabel:`CodaBox` section." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/belgium.rst:290 +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:294 msgid "Select the journal you just created in the SODA journal field." msgstr "" @@ -15048,318 +14680,317 @@ msgstr "" msgid "Configuration of a SODA journal." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/belgium.rst:299 +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:303 msgid "Configure the connection" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/belgium.rst:303 +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:307 msgid "Click on :guilabel:`Manage Connection` to open the connection wizard, which shows the :guilabel:`Accounting Firm VAT` number and the :guilabel:`Company VAT` number that will be used for the connection." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/belgium.rst:306 +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:310 msgid "If this is your **first connection**, click on :guilabel:`Create connection`. The wizard confirms that the connection has been created on **Odoo's side**. Follow the steps to validate the connection on **CodaBox's side**, too." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/belgium.rst:310 +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:314 msgid "If this is **not your first connection**, the :guilabel:`Accounting Firm Password` provided by Odoo during the first connection will be requested to create a new connection." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/belgium.rst:314 +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:318 msgid "This :guilabel:`Accounting Firm Password` is unique to Odoo and must be stored securely on your side." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/belgium.rst:317 +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:321 msgid "The :guilabel:`Status` should have now switched to :guilabel:`Connected`." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/belgium.rst:320 +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:324 msgid "Synchronization" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/belgium.rst:322 +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:326 msgid "Once the connection is established, Odoo can be synchronized with CodaBox." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/belgium.rst:328 +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:332 msgid "CODA files are automatically imported from CodaBox every 12 hours. You do not have to do anything. However, if you wish, it can also be done manually, by clicking on :guilabel:`Fetch from CodaBox` in the Accounting Dashboard." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/belgium.rst:334 +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:338 msgid "SODA files are automatically imported from CodaBox once a day as a draft. You do not have to do anything. However, if you wish, it can also be done manually by clicking on :guilabel:`Fetch from CodaBox` in the Accounting Dashboard." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/belgium.rst:338 +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:342 msgid "By default, if an account in the SODA file is not mapped to an account in Odoo, the Suspense Account (499000) is used, and a note is added to the created journal entry." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/belgium.rst:342 +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:346 msgid "You can access the mapping between the SODA and Odoo accounts by going to :menuselection:`Accounting --> Configuration --> Settings` and clicking on the :guilabel:`Open SODA Mapping` button in the :guilabel:`CodaBox` section." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/belgium.rst:348 +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:352 msgid "Potential issues" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/belgium.rst:350 +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:354 msgid "**CodaBox is not configured. Please check your configuration.**" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/belgium.rst:352 +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:356 msgid "Either the :guilabel:`Company VAT` or the :guilabel:`Accounting Firm VAT` is not set." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/belgium.rst:354 +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:358 msgid "**No connection exists with these accounting firms and company VAT numbers.** **Please check your configuration.**" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/belgium.rst:357 +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:361 msgid "This can happen when checking the connection status, and the :guilabel:`Accounting Firm VAT` and :guilabel:`Company VAT` combination still needs to be registered. This may happen if you have changed the :guilabel:`Company VAT` after the connection was established. For security reasons, you have to :ref:`recreate a connection ` for this :guilabel:`Company VAT`." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/belgium.rst:363 +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:367 msgid "**It seems that your CodaBox connection is not valid anymore. Please connect again.**" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/belgium.rst:365 +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:369 msgid "This can happen if you revoke Odoo's access to your CodaBox account or still need to complete the configuration process. In this case, you must revoke the connection and create a new one." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/belgium.rst:368 +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:372 msgid "**The provided password is not valid for this accounting firm.** **You must reuse the password you received from Odoo during your first connection.**" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/belgium.rst:371 +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:375 msgid "The password you provided is different from the one you received from Odoo during your first connection. You must use the password you received from Odoo during your first connection to create a new connection for this accounting firm. If you have lost your password, you must first revoke the Odoo connection on CodaBox's side (i.e., on your myCodaBox portal). Then, you can revoke the connection on Odoo's side and :ref:`create a new one `." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/belgium.rst:378 +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:382 msgid "**It seems that the company or accounting firm VAT number you provided is not valid.** **Please check your configuration.**" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/belgium.rst:381 +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:385 msgid "Either the :guilabel:`Company VAT` or the :guilabel:`Accounting Firm VAT` is not in a valid Belgian format." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/belgium.rst:384 +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:388 msgid "**It seems that the accounting firm VAT number you provided does not exist in CodaBox.** **Please check your configuration.**" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/belgium.rst:387 +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:391 msgid "The :guilabel:`Accounting Firm VAT` number you provided is not registered in CodaBox. You may not have a valid CodaBox license linked to this VAT number." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/belgium.rst:390 +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:394 msgid "**It seems you have already created a connection to CodaBox with this accounting firm.** **To create a new connection, you must first revoke the old one on myCodaBox portal.**" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/belgium.rst:393 +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:397 msgid "You must go to your myCodaBox portal and revoke Odoo's access to your CodaBox account. Then, you can :ref:`create a new connection ` on Odoo's side." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/belgium.rst:398 +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:402 msgid "To revoke the connection between Odoo and CodaBox, go to :menuselection:`Accounting --> Configuration --> Settings`, scroll down to the :guilabel:`CodaBox` section, click on :guilabel:`Manage Connection`, then click on :guilabel:`Revoke`." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/belgium.rst:404 +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:408 #: ../../content/applications/finance/fiscal_localizations/mexico.rst:263 #: ../../content/applications/finance/fiscal_localizations/mexico.rst:314 msgid "Electronic invoicing" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/belgium.rst:406 +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:410 msgid "Odoo supports the **Peppol BIS Billing 3.0 (UBL)** electronic invoicing format. To enable it for a customer, go to :menuselection:`Accounting --> Customers --> Customers`, open their contact form, and under the :guilabel:`Accounting` tab, select the :guilabel:`Peppol BIS Billing 3.0` format." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/belgium.rst:411 +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:415 #: ../../content/applications/finance/fiscal_localizations/ecuador.rst:183 -#: ../../content/applications/finance/fiscal_localizations/italy.rst:94 msgid ":doc:`../accounting/customer_invoices/electronic_invoicing`" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/belgium.rst:416 +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:420 msgid "Cash discount" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/belgium.rst:418 +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:422 msgid "In Belgium, if an early payment discount is offered on an invoice, the tax is calculated based on the discounted total amount, whether the customer benefits from the discount or not." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/belgium.rst:421 +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:425 msgid "To apply the right tax amount and report it correctly in your VAT return, set the tax reduction as :guilabel:`Always (upon invoice)`." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/belgium.rst:425 +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:429 msgid ":doc:`../accounting/customer_invoices/cash_discounts`" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/belgium.rst:430 +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:434 msgid "Fiscal certification: POS restaurant" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/belgium.rst:432 +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:436 msgid "In Belgium, the owner of a cooking business such as a restaurant or food truck is required by law to use a government-certified **Cash Register System** for their receipts. This applies if their yearly earnings (excluding VAT, drinks, and take-away food) exceed 25,000 euros." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/belgium.rst:436 +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:440 msgid "This government-certified system entails the use of a :ref:`certified POS system `, along with a device called a :ref:`Fiscal Data Module ` (or **black box**) and a :ref:`VAT Signing Card `." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/belgium.rst:441 +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:445 msgid "Do not forget to register as *foodservice industry manager* on the `Federal Public Service Finance registration form `_." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/belgium.rst:447 +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:451 msgid "Certified POS system" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/belgium.rst:449 +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:453 msgid "The Odoo POS system is certified for the major versions of databases hosted on **Odoo Online** and **Odoo.sh**. Please refer to the following table to ensure that your POS system is certified." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/belgium.rst:457 +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:461 #: ../../content/applications/finance/payment_providers/stripe.rst:14 msgid "Odoo Online" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/belgium.rst:458 +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:462 msgid "Odoo.sh" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/belgium.rst:459 +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:463 msgid "On-Premise" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/belgium.rst:460 +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:464 msgid "Odoo 16.0" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/belgium.rst:461 -#: ../../content/applications/finance/fiscal_localizations/belgium.rst:462 -#: ../../content/applications/finance/fiscal_localizations/belgium.rst:469 -#: ../../content/applications/finance/fiscal_localizations/belgium.rst:470 +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:465 +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:466 #: ../../content/applications/finance/fiscal_localizations/belgium.rst:473 #: ../../content/applications/finance/fiscal_localizations/belgium.rst:474 +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:477 +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:478 msgid "Certified" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/belgium.rst:463 -#: ../../content/applications/finance/fiscal_localizations/belgium.rst:465 -#: ../../content/applications/finance/fiscal_localizations/belgium.rst:466 #: ../../content/applications/finance/fiscal_localizations/belgium.rst:467 +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:469 +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:470 #: ../../content/applications/finance/fiscal_localizations/belgium.rst:471 #: ../../content/applications/finance/fiscal_localizations/belgium.rst:475 +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:479 msgid "Not certified" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/belgium.rst:464 +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:468 msgid "Odoo 15.2" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/belgium.rst:468 +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:472 msgid "Odoo 15.0" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/belgium.rst:472 +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:476 msgid "Odoo 14.0" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/belgium.rst:478 -msgid ":doc:`/administration/maintain/supported_versions`" -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/belgium.rst:480 -msgid "A `certified POS system `_ must adhere to rigorous government regulations, which means it operates differently from a non-certified POS." +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:482 +msgid ":doc:`/administration/supported_versions`" msgstr "" #: ../../content/applications/finance/fiscal_localizations/belgium.rst:484 -msgid "On a certified POS, you cannot:" -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/belgium.rst:486 -msgid "Set up and use the **global discounts** feature (the `pos_discount` module is blacklisted and cannot be activated)." +msgid "A `certified POS system `_ must adhere to rigorous government regulations, which means it operates differently from a non-certified POS." msgstr "" #: ../../content/applications/finance/fiscal_localizations/belgium.rst:488 -msgid "Set up and use the **loyalty programs** feature (the `pos_loyalty` module is blacklisted and cannot be activated)." +msgid "On a certified POS, you cannot:" msgstr "" #: ../../content/applications/finance/fiscal_localizations/belgium.rst:490 -msgid "Reprint receipts (the `pos_reprint` module is blacklisted and cannot be activated)." -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/belgium.rst:491 -msgid "Modify prices in order lines." +msgid "Set up and use the **global discounts** feature (the `pos_discount` module is blacklisted and cannot be activated)." msgstr "" #: ../../content/applications/finance/fiscal_localizations/belgium.rst:492 -msgid "Modify or delete order lines in POS orders." -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/belgium.rst:493 -msgid "Sell products without a valid VAT number." +msgid "Set up and use the **loyalty programs** feature (the `pos_loyalty` module is blacklisted and cannot be activated)." msgstr "" #: ../../content/applications/finance/fiscal_localizations/belgium.rst:494 -msgid "Use a POS that is not connected to an IoT box." +msgid "Reprint receipts (the `pos_reprint` module is blacklisted and cannot be activated)." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:495 +msgid "Modify prices in order lines." msgstr "" #: ../../content/applications/finance/fiscal_localizations/belgium.rst:496 +msgid "Modify or delete order lines in POS orders." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:497 +msgid "Sell products without a valid VAT number." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:498 +msgid "Use a POS that is not connected to an IoT box." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:500 msgid "The :doc:`cash rounding <../../sales/point_of_sale/pricing/cash_rounding>` feature must be activated and set to a :guilabel:`Rounding Precision` of `0,05` and a :guilabel:`Rounding Method` set as :guilabel:`Half-Up`." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/belgium.rst:499 +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:503 msgid "Taxes must be set as included in the price. To set it up, go to :menuselection:`Point of Sale --> Configuration --> Settings`, and from the :guilabel:`Accounting` section, open the :guilabel:`Default Sales Tax` form by clicking the arrow next to the default sales tax field. There, click :guilabel:`Advanced Options` and enable :guilabel:`Included in Price`." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/belgium.rst:503 +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:507 msgid "At the start of a POS session, users must click :guilabel:`Work in` to clock in. Doing so allows the registration of POS orders. If users are not clocked in, they cannot make POS orders. Likewise, they must click :guilabel:`Work Out` to clock out at the end of the session." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/belgium.rst:508 +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:512 msgid "If you configure a POS to work with a :abbr:`FDM (Fiscal Data Module)`, you cannot use it again without it." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/belgium.rst:514 +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:518 msgid "Fiscal Data Module (FDM)" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/belgium.rst:516 +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:520 msgid "An FDM, or **black box**, is a government-certified device that works together with the Point of Sale application and saves your POS orders information. Concretely, a **hash** (:dfn:`unique code`) is generated for each POS order and added to its receipt. This allows the government to verify that all revenue is declared." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/belgium.rst:522 +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:526 msgid "Only the FDM from **Boîtenoire.be** with the `FDM certificate number BMC01 `_ is supported by Odoo. `Contact the manufacturer (GCV BMC) `_ to order one." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/belgium.rst:530 +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:534 msgid "Before setting up your database to work with an FDM, ensure you have the following hardware:" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/belgium.rst:532 +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:536 msgid "a **Boîtenoire.be** (certificate number BMC01) FDM;" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/belgium.rst:533 +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:537 msgid "an RS-232 serial null modem cable per FDM;" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/belgium.rst:534 +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:538 msgid "an RS-232 serial-to-USB adapter per FDM;" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/belgium.rst:535 +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:539 msgid "an :ref:`IoT Box ` (one IoT box per FDM); and" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/belgium.rst:536 +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:540 msgid "a receipt printer." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/belgium.rst:541 +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:545 msgid "Black box module" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/belgium.rst:543 +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:547 msgid "As a pre-requisite, :ref:`activate ` the `Belgian Registered Cash Register` module (technical name: `pos_blackbox_be`)." msgstr "" @@ -15367,7 +14998,7 @@ msgstr "" msgid "black box modules for belgian fiscal certification" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/belgium.rst:549 +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:553 msgid "Once the module is activated, add your VAT number to your company information. To set it up, go to :menuselection:`Settings --> Companies --> Update Info`, and fill in the :guilabel:`VAT` field. Then, enter a national registration number for every staff member who operates the POS system. To do so, go to the :guilabel:`Employees` app and open an employee form. There, go to :menuselection:`HR settings tab --> Attendance/Point of Sale`, and fill in the :guilabel:`INSZ or BIS number` field." msgstr "" @@ -15375,55 +15006,55 @@ msgstr "" msgid "ISNZ or BIS number field on employee form" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/belgium.rst:559 +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:563 msgid "To input your information, click on your avatar, go to :menuselection:`My Profile --> Preference tab`, and enter your INSZ or BIS number in the designated field." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/belgium.rst:563 +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:567 msgid "You must configure the :abbr:`FDM (Fiscal Data Module)` directly in the production database. Utilizing it in a testing environment may result in incorrect data being stored within the FDM." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/belgium.rst:569 +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:573 msgid "IoT Box" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/belgium.rst:571 +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:575 msgid "In order to use an :abbr:`FDM (Fiscal Data Module)`, you need a registered IoT Box. To register your IoT box, you must contact us through our `support contact form `_ and provide the following information:" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/belgium.rst:575 +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:579 msgid "your VAT number;" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/belgium.rst:576 +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:580 msgid "your company's name, address, and legal structure; and" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/belgium.rst:577 +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:581 msgid "the Mac address of your IoT Box." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/belgium.rst:579 -msgid "Once your IoT box is certified, :doc:`connect <../../productivity/iot/config/connect>` it to your database. To verify that the IoT Box recognizes the FDM, go to the IoT homepage and scroll down the :guilabel:`IOT Device` section, which should display the FDM." +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:583 +msgid "Once your IoT box is certified, :doc:`connect <../../general/iot/config/connect>` it to your database. To verify that the IoT Box recognizes the FDM, go to the IoT homepage and scroll down the :guilabel:`IOT Device` section, which should display the FDM." msgstr "" #: ../../content/applications/finance/fiscal_localizations/belgium.rst:-1 msgid "Hardware status page on a registered IoT Box" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/belgium.rst:586 +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:590 msgid "Then, add the IoT to your POS. To do so, go to :menuselection:`Point of Sale --> Configuration --> Point of Sale`, select your POS, scroll down to the :guilabel:`Connected Device` section, and enable :guilabel:`IoT Box`. Lastly, add the FMD in the :guilabel:`Fiscal Data Module` field." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/belgium.rst:591 +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:595 msgid "To be able to use an FDM, you must at least connect one :guilabel:`Receipt Printer`." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/belgium.rst:596 +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:600 msgid "VAT signing card" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/belgium.rst:598 +#: ../../content/applications/finance/fiscal_localizations/belgium.rst:602 msgid "When you open a POS session and make your initial transaction, you are prompted to enter the PIN provided with your :abbr:`VSC (VAT signing card)`. The card is delivered by the :abbr:`FPS (Service Public Federal Finances)` upon `registration `_." msgstr "" @@ -15555,7 +15186,7 @@ msgid "Avalara AvaTax is a tax calculation and electronic invoicing provider tha msgstr "" #: ../../content/applications/finance/fiscal_localizations/brazil.rst:90 -msgid "Using this integration requires :doc:`In-App-Purchases (IAPs) <../../general/in_app_purchase>` to compute the taxes and to send the electronic invoices. Whenever you compute taxes, an |API| call is made using credits from your |IAP| credits balance." +msgid "Using this integration requires :doc:`In-App-Purchases (IAPs) <../../essentials/in_app_purchase>` to compute the taxes and to send the electronic invoices. Whenever you compute taxes, an |API| call is made using credits from your |IAP| credits balance." msgstr "" #: ../../content/applications/finance/fiscal_localizations/brazil.rst:95 @@ -16414,6 +16045,13 @@ msgstr "" msgid "Configuring partner contacts is also required to send :abbr:`SII (Servicio de Impuestos Internos)` electronic invoices. Open the :menuselection:`Contacts` app to do so and fill in the following fields on a new or existing contact form." msgstr "" +#: ../../content/applications/finance/fiscal_localizations/chile.rst:232 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:1047 +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:78 +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:271 +msgid ":guilabel:`Name`" +msgstr "" + #: ../../content/applications/finance/fiscal_localizations/chile.rst:233 #: ../../content/applications/finance/fiscal_localizations/chile.rst:1048 #: ../../content/applications/finance/fiscal_localizations/ecuador.rst:83 @@ -18206,7 +17844,6 @@ msgid "`Smart Tutorial - Localización de Ecuador `_" msgstr "" #: ../../content/applications/finance/fiscal_localizations/egypt.rst:223 -msgid ":doc:`../../../administration/install`" +msgid ":doc:`../../../administration/on_premise`" msgstr "" #: ../../content/applications/finance/fiscal_localizations/egypt.rst:228 @@ -19834,6 +19471,7 @@ msgstr "" msgid "Template" msgstr "" +#: ../../content/applications/finance/fiscal_localizations/france.rst:184 #: ../../content/applications/finance/fiscal_localizations/france.rst:184 msgid "`400000`" msgstr "" @@ -19847,6 +19485,7 @@ msgstr "" msgid "`40`" msgstr "" +#: ../../content/applications/finance/fiscal_localizations/france.rst:186 #: ../../content/applications/finance/fiscal_localizations/france.rst:186 msgid "`40100000`" msgstr "" @@ -20133,7 +19772,7 @@ msgid "Getting compliant with Odoo is very easy." msgstr "" #: ../../content/applications/finance/fiscal_localizations/france.rst:366 -msgid "Your company is requested by the tax administration to deliver a certificate of conformity testifying that your software complies with the anti-fraud legislation. This certificate is granted by Odoo SA to Odoo Enterprise users `here `_. If you use Odoo Community, you should :doc:`upgrade to Odoo Enterprise ` or contact your Odoo service provider." +msgid "Your company is requested by the tax administration to deliver a certificate of conformity testifying that your software complies with the anti-fraud legislation. This certificate is granted by Odoo SA to Odoo Enterprise users `here `_. If you use Odoo Community, you should :doc:`upgrade to Odoo Enterprise ` or contact your Odoo service provider." msgstr "" #: ../../content/applications/finance/fiscal_localizations/france.rst:373 @@ -20734,8 +20373,8 @@ msgstr "" msgid "Go to :menuselection:`Accounting --> Configuration --> Settings`. Under the :guilabel:`Customer Payments` section, activate the :guilabel:`QR Codes` feature." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/hong_kong.rst:-1 #: ../../content/applications/finance/fiscal_localizations/hong_kong.rst:19 +#: ../../content/applications/finance/fiscal_localizations/hong_kong.rst:-1 msgid "FPS bank account configuration" msgstr "" @@ -21288,6 +20927,7 @@ msgstr "" msgid "Click :guilabel:`Fetch GSTR-2B Summary` to retrieve the **GSTR-2B** summary. After a few seconds, the status of the report changes to :guilabel:`Waiting for Reception`. This means Odoo is trying to receive the **GSTR-2B** report from the **GST portal**;" msgstr "" +#: ../../content/applications/finance/fiscal_localizations/india.rst:0 #: ../../content/applications/finance/fiscal_localizations/india.rst:0 msgid "GSTR-2B in Waiting for Reception" msgstr "" @@ -21526,7 +21166,6 @@ msgid "`l10n_it`" msgstr "" #: ../../content/applications/finance/fiscal_localizations/italy.rst:23 -#: ../../content/applications/finance/fiscal_localizations/italy.rst:26 msgid "Italy - E-invoicing" msgstr "" @@ -21535,7 +21174,11 @@ msgid "`l10n_it_edi`" msgstr "" #: ../../content/applications/finance/fiscal_localizations/italy.rst:25 -msgid "e-invoice implementation" +msgid "E-invoice implementation" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/italy.rst:26 +msgid "Italy - E-invoicing (Withholding)" msgstr "" #: ../../content/applications/finance/fiscal_localizations/italy.rst:27 @@ -21543,7 +21186,7 @@ msgid "`l10n_it_edi_withholding`" msgstr "" #: ../../content/applications/finance/fiscal_localizations/italy.rst:28 -msgid "e-invoice withholding" +msgid "E-invoice withholding" msgstr "" #: ../../content/applications/finance/fiscal_localizations/italy.rst:29 @@ -21572,576 +21215,753 @@ msgstr "" msgid "Transport documents - Documento di Trasporto (DDT)" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/italy.rst:-1 -msgid "Italian localization modules" -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/italy.rst:43 +#: ../../content/applications/finance/fiscal_localizations/italy.rst:39 msgid "Configuring the company's information ensures your Accounting database is properly set up. To add information, go to :menuselection:`Settings --> General Settings`, and in the :guilabel:`Companies` section, click :guilabel:`Update info`. From here, fill out the fields:" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/italy.rst:47 +#: ../../content/applications/finance/fiscal_localizations/italy.rst:43 msgid ":guilabel:`Address`: the address of the company;" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/italy.rst:48 +#: ../../content/applications/finance/fiscal_localizations/italy.rst:44 msgid ":guilabel:`VAT`: VAT of the company;" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/italy.rst:49 +#: ../../content/applications/finance/fiscal_localizations/italy.rst:45 msgid ":guilabel:`Codice Fiscale`: the fiscal code of the company;" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/italy.rst:50 +#: ../../content/applications/finance/fiscal_localizations/italy.rst:46 msgid ":guilabel:`Tax System`: the tax system under which the company falls;" msgstr "" #: ../../content/applications/finance/fiscal_localizations/italy.rst:-1 -msgid "Company information to provide" +msgid "Company information to be provided" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/italy.rst:57 -msgid "E-invoicing" -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/italy.rst:59 -msgid "The :abbr:`SdI (Sistema di Interscambio)` is the electronic invoicing system used in Italy. It enables to send and receive electronic invoices to and from customers. The documents must be in XML format and formally validated by the system before being delivered." -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/italy.rst:63 -msgid "To be able to receive invoices and notifications, the :abbr:`SdI (Sistema di Interscambio)` service must be notified that the user's files are to be sent to **Odoo** and processed on their behalf. To so, you must set up Odoo's :guilabel:`Codice Destinatario` on the **Agenzia Delle Entrate** portal." -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/italy.rst:68 -msgid "Go to https://ivaservizi.agenziaentrate.gov.it/portale/ and authenticate;" -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/italy.rst:69 -msgid "Go to section :menuselection:`Fatture e Corrispettivi`;" -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/italy.rst:70 -msgid "Set the user as Legal Party for the VAT number you wish to configure the electronic address;" -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/italy.rst:71 -msgid "In :menuselection:`Servizi Disponibili --> Fatturazione Elettronica --> Registrazione dell’indirizzo telematico dove ricevere tutte le fatture elettroniche`, insert Odoo's :guilabel:`Codice Destinatario` `K95IV18`, and confirm." -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/italy.rst:76 -msgid "Electronic Data Interchange (EDI)" -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/italy.rst:78 -msgid "Odoo uses the **FatturaPA** :abbr:`EDI (Electronic Data Interchange)` format for the Italian localization and is enabled on the default journals when installed. When the **file processing authorization** has been set, all **invoices** and **bills** are automatically sent." -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/italy.rst:83 -msgid "You can :ref:`enable electronic invoicing for other sales and purchase journals ` than the default ones." -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/italy.rst:86 -msgid "You can check the current status of an invoice by the :guilabel:`Electronic invoicing` field. The XML file can be found in the **chatter** of the invoice." -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/italy.rst:-1 -msgid "Electronic invoicing status (waiting for confirmation)" -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/italy.rst:97 -msgid "File processing authorization (Odoo)" -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/italy.rst:99 -msgid "Since the files are transmitted through Odoo's server before being sent to the :abbr:`SdI (Sistema di Interscambio)` or received by your database, you need to authorize Odoo to process your files from your database. To do so, go to :menuselection:`Accounting --> Configuration --> Settings --> Electronic Document Invoicing`." -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/italy.rst:104 -msgid "There are **three** modes available:" -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/italy.rst:108 -msgid ":guilabel:`Demo`" -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/italy.rst:107 -msgid "This mode simulates an environment in which invoices are sent to the government. In this mode, invoices need to be *manually* downloaded as XML files and uploaded to the **Agenzia delle Entrate**'s website." -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/italy.rst:112 -msgid ":guilabel:`Test (experimental)`" -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/italy.rst:111 -msgid "This mode sends invoices to a non-production (i.e., test) service made available by the **Agenzia delle Entrate**. Saving this change directs all companies on the database to use this configuration." -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/italy.rst:115 -msgid ":guilabel:`Official`" -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/italy.rst:115 -msgid "This is a production mode that sends your invoices directly to the **Agenzia delle Entrate**." -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/italy.rst:117 -msgid "Once a mode is selected, you need to accept the **terms and conditions** by ticking :guilabel:`Allow Odoo to process invoices`, and then :guilabel:`Save`. You can now record your transactions in Odoo Accounting." -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/italy.rst:122 -msgid "Selecting either :guilabel:`Test (experimental)` or :guilabel:`Official` is **irreversible**. Once in :guilabel:`Official` mode, it is not possible to select :guilabel:`Test (experimental)` or :guilabel:`Demo`, and same for :guilabel:`Test (experimental)`. We recommend creating a separate database for testing purposes only." -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/italy.rst:128 -msgid "When in :guilabel:`Test (Experimental)` mode, all invoices sent *must* have a partner using one of the following fake :guilabel:`Codice Destinatario` given by the **Agenzia Delle Entrate**: `0803HR0` - `N8MIMM9` - `X9XX79Z`. Any real production :guilabel:`Codice Destinario` of your customers will not be recognized as valid by the test service." -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/italy.rst:-1 -msgid "Italy's electronic document invoicing options" -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/italy.rst:138 +#: ../../content/applications/finance/fiscal_localizations/italy.rst:52 msgid "Taxes configuration" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/italy.rst:140 -msgid "Many of the e-invoicing features are implemented using Odoo's tax system. As such, it is very important that taxes are properly configured in order to generate invoices correctly and handle other billing use cases. For example, specific configurations are required for the **reverse charge** type of taxes. In case of a **reverse charge** tax, the seller does *not* charge the customer for the VAT but, instead, the customer pays the VAT *themselves* to their government. There are **two** main types:" +#: ../../content/applications/finance/fiscal_localizations/italy.rst:54 +msgid "Many of the e-invoicing features are implemented using Odoo's tax system. As such, taxes must be properly configured to generate invoices correctly and handle other billing use cases." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/italy.rst:147 -msgid ":ref:`external reverse charge `;" +#: ../../content/applications/finance/fiscal_localizations/italy.rst:57 +msgid "The **Italian** localization contains predefined **examples** of taxes for various purposes." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/italy.rst:148 -msgid ":ref:`internal reverse charge `." +#: ../../content/applications/finance/fiscal_localizations/italy.rst:62 +msgid "Tax exemption" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/italy.rst:153 -msgid "External reverse charge" +#: ../../content/applications/finance/fiscal_localizations/italy.rst:64 +msgid "The use of sale taxes that amount to **zero percent** (0%) is required by Italian authorities to keep track of the exact :guilabel:`Tax Exemption Kind (Natura)` and :guilabel:`Law Reference` that justify the exemption operated on an invoice line." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/italy.rst:156 -#: ../../content/applications/finance/fiscal_localizations/italy.rst:387 +#: ../../content/applications/finance/fiscal_localizations/italy.rst:69 +msgid "The export tax in the EU can be used as reference (`0% EU`, invoice label `00eu`). It can be found under :menuselection:`Accounting --> Configuration --> Taxes`. Exports are exempt from VAT, and therefore, they require :guilabel:`Exoneration` kind and :guilabel:`Law Reference` filled in." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/italy.rst:-1 +msgid "Tax Exemption Settings" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/italy.rst:77 +msgid "There are many :guilabel:`Tax Exemption Kind (Natura)` and :guilabel:`Law Reference` codes. Make sure you check the latest version available to get the latest information on:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/italy.rst:80 +msgid "`Italian authorities documentation `_" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/italy.rst:81 +msgid "`Official guide on Tax exemption `_" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/italy.rst:84 +msgid "If you need to use a different kind of exoneration, go to :menuselection:`Accounting --> Configuration --> Taxes`, select a similar tax, then click on the cog icon and select :guilabel:`Duplicate`. In the :guilabel:`Advanced Options` tab, add the :guilabel:`Exoneration` and :guilabel:`Law Reference`. To confirm click on :guilabel:`Save`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/italy.rst:90 +msgid "**Rename** your taxes in the :guilabel:`Name` field according to their :guilabel:`Exoneration` to differentiate them easily." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/italy.rst:96 +msgid "Reverse charge" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/italy.rst:98 +msgid "The **reverse charge** mechanism is a VAT rule that shifts the liability to pay VAT from the supplier to the customer. The customers pay the VAT *themselves* to the :abbr:`AdE (Agenzia delle Entrate)` instead. There are different types:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/italy.rst:0 +msgid ":guilabel:`Internal Reverse Charge` (for domestic sales)" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/italy.rst:0 +msgid "The VAT responsibility is shifted to the buyer for certain categories of products and services." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/italy.rst:0 +msgid ":guilabel:`External Reverse Charge` (for intra-EU sales)" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/italy.rst:0 +msgid "VAT is due in the country of the delivery or in the country where the service is performed. When the buyer is itself an Italian business, then the EU offers a mechanism that allows the seller to transfer his responsibility to the buyer." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/italy.rst:110 +#: ../../content/applications/finance/fiscal_localizations/italy.rst:505 #: ../../content/applications/finance/fiscal_localizations/united_arab_emirates.rst:212 msgid "Invoices" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/italy.rst:158 -msgid "To make an export invoice, make sure that the invoice lines all use a tax configured for **reverse charge**. The **Italian** localization contains an **example** of a reverse charge tax for export in the EU to be used as reference (`0% EU`, invoice label `00eu`), which can be found under :menuselection:`Accounting --> Configuration --> Taxes`. Exports are exempt from VAT, and therefore **reverse charge** taxes require the :guilabel:`Has exoneration of tax (Italy)` option ticked, with both the :guilabel:`Exoneration` kind and :guilabel:`Law Reference` filled in." +#: ../../content/applications/finance/fiscal_localizations/italy.rst:112 +msgid "**Reverse-charged** customer invoices show no VAT amount, but the :abbr:`AdE (Agenzia delle Entrate)` requires the seller to specify the :guilabel:`Tax Exemption` reason and the :guilabel:`Law Reference` that enable the reverse-charge mechanism. Odoo provides a set of special 0% taxes that can be assigned to each reverse-charged invoice lines, representing the most commonly used configurations." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/italy.rst:121 +msgid "Italian companies subjected to Reverse Charge must send the information in the bill received to the :abbr:`AdE (Agenzia delle Entrate)`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/italy.rst:125 +msgid "Self-reported VAT XML files must be issued and sent to the :abbr:`AdE (Agenzia Delle Entrate)` for reverse charged bills." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/italy.rst:128 +msgid "When creating a vendor bill, **reverse charge** taxes are available to be added in the :guilabel:`Taxes` field. You can check which taxes are available by going to :menuselection:`Accounting --> Configuration --> Taxes`, you can see that the 10% Goods and 22% Services taxes are activated, among others. Due to the automated configuration of the Italian fiscal position, these are automatically activated in the tax list." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/italy.rst:137 +msgid "Tax grids" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/italy.rst:139 +msgid "The Italian localization has a specific :ref:`tax grid ` section for **reverse charge** taxes. These tax grids are identifiable by the :ref:`VJ ` tag, and can be found by going to :menuselection:`Accounting --> Reporting --> Audit Reports: Tax Report`." msgstr "" #: ../../content/applications/finance/fiscal_localizations/italy.rst:-1 -msgid "External reverse charge settings" +msgid "Reverse charge tax grid from the VJ section of the Tax Declaration" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/italy.rst:170 -msgid "If you need to use a different kind of :guilabel:`Exoneration`, click :menuselection:`Action --> Duplicate` within the tax menu to create a copy of an existing similar tax. Then, select another :guilabel:`Exoneration`, and :guilabel:`Save`. Repeat this process as many times as you need different kind of :guilabel:`Exoneration` taxes." +#: ../../content/applications/finance/fiscal_localizations/italy.rst:149 +msgid "E-invoicing" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/italy.rst:176 -msgid "**Rename** your taxes in the :guilabel:`Name` field according to their :guilabel:`Exoneration` to differentiate them easily." +#: ../../content/applications/finance/fiscal_localizations/italy.rst:151 +msgid "The :abbr:`SdI (Sistema di Interscambio)` is the :doc:`electronic invoicing <../accounting/customer_invoices/electronic_invoicing>` system used in Italy. It enables the sending and receiving of electronic invoices to and from customers. The documents must be in an XML :abbr:`EDI (Electronic Data Interchange)` format called **FatturaPA** and formally validated by the system before being delivered." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/italy.rst:179 -msgid "On your invoice, select the corresponding tax you need in the :guilabel:`Taxes` field. You can find the following **additional info** by opening the **XML** file of the issued invoice:" +#: ../../content/applications/finance/fiscal_localizations/italy.rst:157 +msgid "To be able to receive invoices and notifications, the :abbr:`SdI (Sistema di Interscambio)` service must be notified that the user's files need to be sent to Odoo and processed on their behalf. To do so, you must set up Odoo's :guilabel:`Destination Code` on the :abbr:`AdE (Agenzia Delle Entrate)` portal." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/italy.rst:182 -msgid ":guilabel:`SdI address (Codice Destinatario)`: must be filled for both **EU** or **non-EU**;" +#: ../../content/applications/finance/fiscal_localizations/italy.rst:162 +msgid "Go to `Italian authorities portal `_ and authenticate;" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/italy.rst:183 -msgid ":guilabel:`Country Id`: must contain the country of the foreign seller in the two-letter ISO (Alpha-2) code (ex., `IT` for 'Italy');" +#: ../../content/applications/finance/fiscal_localizations/italy.rst:164 +msgid "Go to section :menuselection:`Fatture e Corrispettivi`;" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/italy.rst:185 -msgid ":guilabel:`CAP`: must be filled with `00000`;" +#: ../../content/applications/finance/fiscal_localizations/italy.rst:165 +msgid "Set the user as Legal Party for the VAT number you wish to configure the electronic address;" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/italy.rst:186 -msgid ":guilabel:`Partita Iva` (**VAT number**): must contain the **VAT** number for **EU businesses** and `OO99999999999` (double 'O' **letter**, not 'zero') for **non-EU businesses**. In case of private customers without **VAT** number, use `0000000`;" +#: ../../content/applications/finance/fiscal_localizations/italy.rst:166 +msgid "In :menuselection:`Servizi Disponibili --> Fatturazione Elettronica --> Registrazione dell’indirizzo telematico dove ricevere tutte le fatture elettroniche`, insert Odoo's :guilabel:`Destination Code` `K95IV18`, and confirm." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/italy.rst:189 -msgid ":guilabel:`Fiscal Code`: for foreign entities without an actual **Codice Fiscale**, any recognizable identifier is valid." +#: ../../content/applications/finance/fiscal_localizations/italy.rst:171 +msgid "EDI Mode and authorization" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/italy.rst:193 -msgid "Odoo does not support sending user-modified XML files." +#: ../../content/applications/finance/fiscal_localizations/italy.rst:173 +msgid "Since the files are transmitted through Odoo's server before being sent to the :abbr:`SdI (Sistema di Interscambio)` or received by your database, you need to authorize Odoo to process your files from your database. To do so, go to :menuselection:`Accounting --> Configuration --> Settings --> Electronic Document Invoicing`." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/italy.rst:195 -msgid "For **invoices**, multiple configurations are technically identified by a :guilabel:`Tipo Documento` code:" +#: ../../content/applications/finance/fiscal_localizations/italy.rst:178 +msgid "There are three modes available:" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/italy.rst:198 -msgid "`TD02` - Down payments;" +#: ../../content/applications/finance/fiscal_localizations/italy.rst:0 +msgid ":guilabel:`Demo`" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/italy.rst:199 -msgid "`TDO7` - Simplified invoice;" +#: ../../content/applications/finance/fiscal_localizations/italy.rst:0 +msgid "This mode simulates an environment in which invoices are sent to the government. In this mode, invoices need to be *manually* downloaded as XML files and uploaded to the :abbr:`AdE (Agenzia delle Entrate)`'s website." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/italy.rst:200 -msgid "`TD08` - Simplified credit note;" +#: ../../content/applications/finance/fiscal_localizations/italy.rst:0 +msgid ":guilabel:`Test (experimental)`" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/italy.rst:201 -msgid "`TD09` - Simplified debit note;" +#: ../../content/applications/finance/fiscal_localizations/italy.rst:0 +msgid "This mode sends invoices to a non-production (i.e., test) service made available by the :abbr:`AdE (Agenzia delle Entrate)`. Saving this change directs all companies on the database to use this configuration." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/italy.rst:202 -msgid "`TD24` - Deferred invoice." +#: ../../content/applications/finance/fiscal_localizations/italy.rst:0 +msgid ":guilabel:`Official`" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/italy.rst:206 -msgid "`TD02`" +#: ../../content/applications/finance/fiscal_localizations/italy.rst:0 +msgid "This is a production mode that sends your invoices directly to the :abbr:`AdE (Agenzia delle Entrate)`." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/italy.rst:208 -msgid "Down payments." +#: ../../content/applications/finance/fiscal_localizations/italy.rst:192 +msgid "Once a mode is selected, you need to accept the **terms and conditions** by ticking :guilabel:`Allow Odoo to process invoices`, and then :guilabel:`Save`. You can now record your transactions in Odoo Accounting." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/italy.rst:210 -msgid "**Down payment** invoices are imported/exported with a different :guilabel:`Tipo Documento` code `TDO2` than regular invoices. Upon import of the invoice, it creates a regular vendor bill." +#: ../../content/applications/finance/fiscal_localizations/italy.rst:197 +msgid "Selecting either :guilabel:`Test (experimental)` or :guilabel:`Official` is **irreversible**. For example, once in :guilabel:`Official` mode, it is not possible to select :guilabel:`Test (experimental)` or :guilabel:`Demo`. We recommend creating a **separate database** for testing purposes only." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/italy.rst:203 +msgid "When in :guilabel:`Test (Experimental)` mode, all invoices sent *must* have a partner using one of the following fake :guilabel:`Destination Code` given by the :abbr:`AdE (Agenzia Delle Entrate)`: `0803HR0` - `N8MIMM9` - `X9XX79Z`. Any real production :guilabel:`Codice Destinario` of your customers will not be recognized as valid by the test service." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/italy.rst:-1 +msgid "Electronic document invoicing settings" msgstr "" #: ../../content/applications/finance/fiscal_localizations/italy.rst:214 -msgid "Odoo exports moves as `TD02` if the following conditions are met:" +#: ../../content/applications/finance/fiscal_localizations/italy.rst:587 +msgid "Process" msgstr "" #: ../../content/applications/finance/fiscal_localizations/italy.rst:216 -#: ../../content/applications/finance/fiscal_localizations/italy.rst:274 -msgid "Is an invoice;" +msgid "The submission of invoices to the :abbr:`SdI (Sistema di Interscambio)` for Italy is an electronic process used for the mandatory transmission of tax documents in XML format between companies and the :abbr:`AdE (Agenzia delle Entrate)` to reduce errors and verify the correctness of operations." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/italy.rst:217 -msgid "All invoice lines are related to **sales order lines** that have the flag `is_downpayment` set as `True`." -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/italy.rst:220 -msgid "`TD07`, `TD08`, and `TD09`" -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/italy.rst:222 -msgid "Simplified invoices, and credit/debit notes." -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/italy.rst:224 -msgid "Simplified invoices and credit notes can be used to certify **domestic transactions** under **400 EUR** (VAT included). Its status is the same as a regular invoice, but with fewer information requirements." -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/italy.rst:228 -msgid "For a **simplified** invoice to be established, it must include:" -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/italy.rst:230 -msgid ":guilabel:`Customer Invoice` reference: **unique** numbering sequence with **no gaps**;" -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/italy.rst:231 -msgid ":guilabel:`Invoice Date`: issue **date** of the invoice;" -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/italy.rst:232 -msgid ":guilabel:`Company Info`: the **seller**'s full credentials (VAT/TIN number, name, full address) under :menuselection:`General Settings --> Companies (section)`;" -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/italy.rst:234 -msgid ":guilabel:`VAT`: the **buyer**'s VAT/TIN number (on their profile card);" -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/italy.rst:235 -msgid ":guilabel:`Total`: the total **amount** (VAT included) of the invoice." -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/italy.rst:237 -msgid "In the :abbr:`EDI (Electronic Data Interchange)`, Odoo exports invoices as simplified if:" -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/italy.rst:239 -msgid "It is a **domestic** transaction (i.e., the partner is from Italy);" -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/italy.rst:240 -msgid "The buyer's data is **insufficient** for a regular invoice;" -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/italy.rst:241 -msgid "The **required fields** for a regular invoice (address, ZIP code, city, country) are provided;" -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/italy.rst:243 -msgid "The total amount VAT included is **less** than **400 EUR**." -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/italy.rst:246 -msgid "The 400 EUR threshold was defined in `the decree of the 10th of May 2019 in the Gazzetta Ufficiale `_. We advise you to check the current official value." -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/italy.rst:250 -msgid "`TD24`" -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/italy.rst:252 -msgid "Deferred invoices." -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/italy.rst:254 -msgid "The **deferred invoice** is an invoice that is **issued at a later time** than the sale of goods or the provision of services. A **deferred invoice** has to be issued at the latest within the **15th day** of the month following the delivery covered by the document." -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/italy.rst:258 -msgid "It usually is a **summary invoice** containing a list of multiple sales of goods or services, carried out in the month. The business is allowed to **group** the sales into **one invoice**, generally issued at the **end of the month** for accounting purposes. Deferred invoices are default for **wholesaler** having recurrent clients." -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/italy.rst:263 -msgid "If the goods are transported by a **carrier**, every delivery has an associated **Documento di Transporto (DDT)**, or **Transport Document**. The deferred invoice **must** indicate the details of all the **DDTs** information for better tracing." -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/italy.rst:268 -msgid "E-invoicing of deferred invoices requires the `l10n_it_stock_ddt` :ref:`module `. In this case, a dedicated :guilabel:`Tipo Documento` `TD24` is used in the e-invoice." -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/italy.rst:272 -msgid "Odoo exports moves as `TD24` if the following conditions are met:" -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/italy.rst:275 -msgid "Is associated to deliveries whose **DDTs** have a **different** date than the issuance date of the invoice." -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/italy.rst:281 -msgid "Italian companies buying goods or services from EU countries (or services from non-EU countries) must send the information contained within the bill received to the **Agenzia delle Entrate**. This allows you to complete tax-related information on your bill, and to send it. The seller must be set as :guilabel:`Cedente/Prestatore`, and the buyer as :guilabel:`Cessionario/Committente`. Contained within the **XML** document for the vendor bill, the vendor's credentials show as :guilabel:`Cedente/Prestatore`, and your company's credentials as :guilabel:`Cessionario/Committente`." -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/italy.rst:290 -msgid "Self-billing invoices or VAT invoice integrations must be issued and sent to the tax agency." -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/italy.rst:292 -msgid "When inputting taxes in a vendor bill, it is possible to select **reverse charge** taxes. These are automatically activated in the Italian fiscal position. By going to :menuselection:`Accounting --> Configuration --> Taxes`, the `10%` and `22%` :guilabel:`Goods` and :guilabel:`Services` tax scopes are activated and preconfigured with the correct tax grids. These are set up automatically to ensure the correct booking of accounting entries and display of the tax report." -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/italy.rst:298 -msgid "For **vendor bills**, **three** types of configurations are technically identified by a code called :guilabel:`Tipo Documento`:" -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/italy.rst:301 -msgid "`TD17` - Buying services from **EU** and **non-EU** countries;" -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/italy.rst:302 -msgid "`TD18` - Buying **goods** from **EU**;" -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/italy.rst:303 -msgid "`TD19` - Buying **goods** from a **foreign** vendor, but the **goods** are already in **Italy** in a **VAT deposit**." -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/italy.rst:308 -msgid "`TD17`" -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/italy.rst:310 -msgid "Buying **services** from **EU** and **non-EU** countries:" -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/italy.rst:312 -msgid "The foreign *seller* invoices a service with a **VAT-excluded** price, as it is not taxable in Italy. The VAT is paid by the *buyer* in Italy;" -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/italy.rst:315 -msgid "Within EU: the *buyer* integrates the invoice received with the **VAT information** due in Italy (i.e., **vendor bill tax integration**);" -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/italy.rst:317 -msgid "Non-EU: the *buyer* sends themselves an invoice (i.e., **self-billing**)." -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/italy.rst:319 -msgid "Odoo exports a transaction as `TD17` if the following conditions are met:" -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/italy.rst:321 -#: ../../content/applications/finance/fiscal_localizations/italy.rst:335 -#: ../../content/applications/finance/fiscal_localizations/italy.rst:351 -#: ../../content/applications/finance/fiscal_localizations/italy.rst:411 -msgid "Is a vendor bill;" -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/italy.rst:322 -#: ../../content/applications/finance/fiscal_localizations/italy.rst:336 -#: ../../content/applications/finance/fiscal_localizations/italy.rst:412 -msgid "At least one tax on the invoice lines targets the tax grids :ref:`VJ `;" -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/italy.rst:323 -msgid "All invoice lines either have :guilabel:`Services` as **products**, or a tax with the :guilabel:`Services` as **tax scope**." -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/italy.rst:326 -msgid "`TD18`" -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/italy.rst:328 -msgid "Buying **goods** from **EU**:" -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/italy.rst:330 -msgid "Invoices issued within the EU follow a **standard format**, therefore only an integration of the existing invoice is required." -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/italy.rst:333 -msgid "Odoo exports a transaction as `TD18` if the following conditions are met:" -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/italy.rst:337 -msgid "All invoice lines either have :guilabel:`Consumable` as **products**, or a tax with the :guilabel:`Goods` as **tax scope**." -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/italy.rst:340 -msgid "`TD19`" -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/italy.rst:342 -msgid "Buying **goods** from a **foreign** vendor, but the **goods** are already in **Italy** in a **VAT deposit**:" -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/italy.rst:345 -msgid "From EU: the *buyer* integrates the invoice received with the **VAT information** due in Italy (i.e., **vendor bill tax integration**);" -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/italy.rst:347 -msgid "Non-EU: the *buyer* sends an invoice to *themselves* (i.e., **self-billing**)." -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/italy.rst:349 -msgid "Odoo exports a move as a `TD19` if the following conditions are met:" -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/italy.rst:352 -msgid "At least one tax on the invoice lines targets the tax grid :ref:`VJ3 `;" -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/italy.rst:353 -msgid "All invoice lines either have :guilabel:`Consumable` products, or a tax with :guilabel:`Goods` as tax scope." -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/italy.rst:357 -msgid "Odoo does not offer the `Conservazione Sostitutiva `_ requirements. Other providers and **Agenzia delle Entrate** supply free and certified storage to meet the requested conditions." -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/italy.rst:365 -msgid "Internal reverse charge" -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/italy.rst:368 -msgid "Odoo currently does not support domestic **internal reverse charge** processes." -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/italy.rst:373 -msgid "'Reverse Charge' tax grids" -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/italy.rst:375 -msgid "The Italian localization has a specific **tax grid** section for **reverse charge** taxes. These tax grids are identifiable by the :ref:`VJ ` tag, and can be found under :menuselection:`Accounting --> Reporting --> Audit Reports: Tax Report`." +#: ../../content/applications/finance/fiscal_localizations/italy.rst:221 +msgid "You can check the current status of an invoice by the :guilabel:`SdI State` field. The XML file is attached to the invoice." msgstr "" #: ../../content/applications/finance/fiscal_localizations/italy.rst:-1 -msgid "Italian reverse charge tax grids" +msgid "EDI system architecture" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/italy.rst:384 -msgid "San Marino" +#: ../../content/applications/finance/fiscal_localizations/italy.rst:228 +msgid "XML Documents creation" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/italy.rst:230 +msgid "Odoo generates the required XML files as attachments to invoices in the `FatturaPA` format required by the :abbr:`AdE (Agenzia delle Entrate)`. Once the invoices needed are selected, go to :guilabel:`Action` and click on :guilabel:`Send and Print`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/italy.rst:-1 +msgid "Send and Print menu" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/italy.rst:237 +msgid "When the pop-up window opens there is a selection of actions that can be taken. :guilabel:`Generate XML File` generates the attachments." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/italy.rst:-1 +msgid "Send and Print dialog" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/italy.rst:243 +msgid "The XML file as well as the PDF once can be found attached to the invoice." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/italy.rst:-1 +msgid "EDI Attachments" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/italy.rst:249 +msgid "Submission to SDI" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/italy.rst:251 +msgid "The :guilabel:`Send to Tax Agency` option in the :guilabel:`Send and Print` dialog sends the attachment to the :guilabel:`Proxy Server`, which gathers all requests and then forwards them via a WebServices channel to the :abbr:`SdI (Sistema di Interscambio)`. Check the sending status of the invoice through the :guilabel:`Check Sending` button at the top of the invoice's view." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/italy.rst:257 +msgid "Processing by SDI" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/italy.rst:259 +msgid "The :abbr:`SdI (Sistema di Interscambio)` receives the document and verifies for any errors. At this stage, the invoice is in the :guilabel:`SdI Processing` state, as shown on the invoice. The invoice also gets assigned a :guilabel:`FatturaPA Transaction` number that is shown in the :guilabel:`Electronic Invoicing` tab. The checks may take variable time, ranging from a few seconds up to a day, depending on the queue of invoices sent throughout Italy." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/italy.rst:-1 +msgid "Check Sending button and Sdi Processing state" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/italy.rst:269 +msgid "Acceptance" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/italy.rst:271 +msgid "If the document is valid, it is recorded and considered fiscally valid by the :abbr:`AdE (Agenzia delle Entrate)`, which will proceed with archiving in :guilabel:`Substitute Storage (Conservazione Sostitutiva)` if explicitly requested on the Agency's portal." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/italy.rst:276 +msgid "Odoo does not offer the `Conservazione Sostitutiva `_ requirements. Other providers and :abbr:`AdE (Agenzia delle Entrate)` supply free and certified storage to meet the specifications requested by law." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/italy.rst:281 +msgid "The :abbr:`SdI (Sistema di Interscambio)` :guilabel:`Destination Code` attempts to forward the invoice to the customer at the provided address, whether it is a `PEC` email address or a :abbr:`SdI (Sistema di Interscambio)` :guilabel:`Destination Code` for their ERP's WebServices channels. A maximum of 6 attempts are made every 12 hours, so even if unsuccessful, this process can take up to three days. The invoice status is :guilabel:`Accepted by SDI, Forwarding to Partner`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/italy.rst:288 +msgid "Possible Rejection" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/italy.rst:290 +msgid "The :abbr:`SdI (Sistema di Interscambio)` may find inaccuracies in the compilation, possibly even formal ones. In this case, the invoice is in the :guilabel:`SDI Rejected` state. The :abbr:`SdI (Sistema di Interscambio)`'s observations are inserted at the top of the Invoice tab. To resolve the issue, it is sufficient to delete the attachments of the invoice, return the invoice to :guilabel:`Draft`, and fix the errors. Once the invoice is ready, it can be resent." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/italy.rst:297 +msgid "To regenerate the XML, both the XML attachment and the PDF report must be deleted, so that they are then regenerated together. This ensures that both always contain the same data." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/italy.rst:-1 +msgid "EDI Rejected State" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/italy.rst:304 +msgid "Forwarding Completed" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/italy.rst:306 +msgid "The invoice has been delivered to the customer; however, you can still send a copy to the customer in PDF via email or post. Its status is :guilabel:`Accepted by SDI, Delivered to Partner`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/italy.rst:309 +msgid "If the :abbr:`SdI (Sistema di Interscambio)` cannot contact your customer, they may not be registered on the :abbr:`AdE (Agenzia delle Entrate)` portal. In this case, just make sure to send the invoice in PDF via email or by mail. The invoice is then in the :guilabel:`Accepted by SDI, Partner Delivery Failed` state." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/italy.rst:315 +msgid "Tax Integration" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/italy.rst:317 +msgid "When you receive a vendor bill, either from :abbr:`SdI (Sistema di Interscambio)`, from paper or from an imported XML file, the Tax Agency might request that you send some tax information integration back to the :abbr:`SdI (Sistema di Interscambio)`. It happens when a transaction that was tax exempt becomes taxable for any reason." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/italy.rst:323 +msgid "Here is a non-exhaustive list:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/italy.rst:0 +msgid ":ref:`italy/reverse-charge`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/italy.rst:0 +msgid "As a buyer, you have to pay taxes on what you buy and integrate tax information. :guilabel:`Reverse Charge` taxes." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/italy.rst:0 +msgid ":ref:`italy/split-payment`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/italy.rst:0 +msgid "As a :abbr:`PA (Public Administration)` business buyer, you have to pay taxes and integrate tax information. Be sure that you replace the :guilabel:`0% Sale Taxes` on the vendor bill you received with the correct :guilabel:`Split Payment` taxes." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/italy.rst:0 +msgid ":guilabel:`Self Consumption`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/italy.rst:0 +msgid "When, as a business owner, you use an asset that you bought for business for personal reasons instead, you have to pay those taxes you originally deducted as a business cost for it." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/italy.rst:336 +msgid "Odoo may detect that your vendor bill can be interpreted as a document of a type that needs tax integration, as detailed in the :ref:`italy/document-types` section." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/italy.rst:340 +msgid "Be sure that you replace the :guilabel:`0% Sale Taxes` on the vendor bill you received with the ones you're supposed to pay to the :abbr:`AdE (Agenzia delle Entrate)`. A button then appears on the top of the single vendor bill form to send them." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/italy.rst:344 +msgid "When clicking on the :guilabel:`Send Tax Integration` button, an XML file of the appropriate :guilabel:`Document Type` is generated, attached to the bill, and sent as for invoices." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/italy.rst:0 +msgid "EDI Send Tax Integration button" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/italy.rst:353 +#: ../../content/applications/finance/fiscal_localizations/peru.rst:286 +msgid "Document Types" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/italy.rst:355 +msgid "The :abbr:`SdI (Sistema di Interscambio)` requires businesses to send customer invoices and other documents through the :abbr:`EDI (Electronic Data Interchange)`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/italy.rst:358 +msgid "The following :guilabel:`Document Type` codes all technically identify different business use cases." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/italy.rst:361 +msgid "TD01 - Invoices" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/italy.rst:363 +msgid "This represents the standard **domestic** scenario for all invoices exchanged through the :abbr:`SdI (Sistema di Interscambio)`. Any invoice that doesn't fall into one of the specific special cases is categorized as a regular invoice, identified by the :guilabel:`Document Type` `TD01`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/italy.rst:368 +msgid "TD02 - Down payments" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/italy.rst:370 +msgid "**Down payment** invoices are imported/exported with a different :guilabel:`Document Type` code `TDO2` than regular invoices. Upon import of the invoice, a regular vendor bill is created." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/italy.rst:373 +msgid "Odoo exports transactions as `TD02` if the following conditions are met:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/italy.rst:375 +#: ../../content/applications/finance/fiscal_localizations/italy.rst:497 +msgid "It is an invoice;" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/italy.rst:376 +msgid "All invoice lines are related to down payment sales order lines." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/italy.rst:379 +msgid "TD04 - Credit notes" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/italy.rst:381 +msgid "It is the standard scenario for all **credit notes** issued to **domestic** clients, when we need to formally acknowledge that the seller is reducing or canceling a previously issued invoice, for example, in case of overbilling, incorrect items, or overpayment. Just like invoices, they must be sent to the :abbr:`SdI (Sistema di Interscambio)`, their :guilabel:`Document Type` `TD04`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/italy.rst:387 +msgid "TD07, TD08, TD09 - Simplified Invoicing" msgstr "" #: ../../content/applications/finance/fiscal_localizations/italy.rst:389 -msgid "San Marino and Italy have special agreements on e-invoicing operations. As such, **invoices** follow the regular **reverse charge** rules. Additional requirements are not enforced by Odoo, however, the user is requested by the **State** to:" +msgid "Simplified invoices (`TD07`), credit notes (`TD08`), and debit notes (`TD09`) can be used to certify domestic transactions under 400 EUR (VAT included). Its status is the same as that of a regular invoice, but with fewer information requirements." msgstr "" #: ../../content/applications/finance/fiscal_localizations/italy.rst:393 -msgid "Select a tax with the option :guilabel:`Has exoneration of tax (Italy)` ticked, and the :guilabel:`Exoneration` set to `N3.3`;" +msgid "For a simplified invoice to be established, it must include:" msgstr "" #: ../../content/applications/finance/fiscal_localizations/italy.rst:395 -msgid "Use the generic :abbr:`SdI (Sistema di Interscambio)` :guilabel:`Codice Destinatario` `2R4GT08`. The invoice is then routed by a dedicated office in San Marino to the correct business." +msgid ":guilabel:`Customer Invoice` reference: **unique** numbering sequence with **no gaps**;" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/italy.rst:396 +msgid ":guilabel:`Invoice Date`: issue **date** of the invoice;" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/italy.rst:397 +msgid ":guilabel:`Company Info`: the **seller**'s full credentials (VAT/TIN number, name, full address) under :menuselection:`General Settings --> Companies (section)`;" msgstr "" #: ../../content/applications/finance/fiscal_localizations/italy.rst:399 -msgid "Bills" +msgid ":guilabel:`VAT`: the **buyer**'s VAT/TIN number (on the partner form);" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/italy.rst:401 -msgid "When a **paper bill** is received from San Marino, any Italian company **must** submit that invoice to the **Agenzia delle Entrate** by indicating the e-invoice's :guilabel:`Tipo Documento` field with the special value `TD28`." +#: ../../content/applications/finance/fiscal_localizations/italy.rst:400 +msgid ":guilabel:`Total`: the total **amount** (VAT included) of the invoice." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/italy.rst:402 +msgid "In the :abbr:`EDI (Electronic Data Interchange)`, Odoo exports invoices as simplified if:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/italy.rst:404 +msgid "It is a domestic transaction (i.e., the partner is from Italy);" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/italy.rst:405 +msgid "Your company's **required fields** (:guilabel:`VAT Number` or :guilabel:`Codice Fiscale`, :guilabel:`Fiscal Regime`, and full **address**) are provided;" msgstr "" #: ../../content/applications/finance/fiscal_localizations/italy.rst:407 -msgid "`TD28`" +msgid "The partner's address is not fully specified (i.e., it misses the City or the ZipCode);" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/italy.rst:409 -msgid "Odoo exports a move as `TD28` if the following conditions are met:" +#: ../../content/applications/finance/fiscal_localizations/italy.rst:408 +msgid "The total amount of VAT included is **less** than **400 EUR**." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/italy.rst:413 -msgid "The **country** of the partner is **San Marino**." +#: ../../content/applications/finance/fiscal_localizations/italy.rst:411 +msgid "The 400 EUR threshold was defined in `the decree of the 10th of May 2019 in the Gazzetta Ufficiale `_. We advise you to check the current official value." msgstr "" #: ../../content/applications/finance/fiscal_localizations/italy.rst:416 -msgid "Pubblica amministrazione (B2G)" +msgid "TD16 - Internal Reverse Charge" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/italy.rst:419 -msgid "Odoo does **not** send invoices directly to the government as they need to be signed. If we see that the codice destinatario is 6 digits, then it is not sent to the PA automatically, but you can download the XML, sign it with an external program and send it through the portal." +#: ../../content/applications/finance/fiscal_localizations/italy.rst:418 +msgid "Internal reverse charge transactions (see :ref:`italy/tax-exemption` and :ref:`italy/reverse-charge`) are exported as `TD16` if the following conditions are met:" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/italy.rst:424 -msgid "Digital qualified signature" +#: ../../content/applications/finance/fiscal_localizations/italy.rst:421 +#: ../../content/applications/finance/fiscal_localizations/italy.rst:438 +#: ../../content/applications/finance/fiscal_localizations/italy.rst:452 +#: ../../content/applications/finance/fiscal_localizations/italy.rst:470 +#: ../../content/applications/finance/fiscal_localizations/italy.rst:526 +msgid "It is a vendor bill;" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/italy.rst:422 +msgid "It has at least **one tax** on the invoice lines that targets one of these :ref:`tax grids `: `VJ6`, `VJ7`, `VJ8`, `VJ12`, `VJ13`, `VJ14`, `VJ15`, `VJ16`, `VJ17`" msgstr "" #: ../../content/applications/finance/fiscal_localizations/italy.rst:426 -msgid "For invoices and bills intended to the **Pubblica Amministrazione (B2G)**, a **Digital Qualified Signature** is required for all files sent through the :abbr:`SdI (Sistema di Interscambio)`. The **XML** file must be certified using a certificate that is either:" +msgid "TD17 - Buying services from abroad" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/italy.rst:430 -msgid "a **smart card**;" -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/italy.rst:431 -msgid "a **USB token**;" +#: ../../content/applications/finance/fiscal_localizations/italy.rst:428 +msgid "When buying **services** from **EU** and **non-EU** countries, the foreign *seller* invoices a service with a **VAT-excluded** price, as it is not taxable in Italy. The VAT is paid by the *buyer* in Italy." msgstr "" #: ../../content/applications/finance/fiscal_localizations/italy.rst:432 -msgid "a **Hardware Security Module (HSM)**." +msgid "Within the EU: the *buyer* integrates the invoice received with the **VAT information** due in Italy (i.e., **vendor bill tax integration**);" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/italy.rst:435 +#: ../../content/applications/finance/fiscal_localizations/italy.rst:434 +msgid "Non-EU: the *buyer* sends themselves an invoice (i.e., **self-billing**)." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/italy.rst:436 +msgid "Odoo exports a transaction as `TD17` if the following conditions are met:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/italy.rst:439 +msgid "It has at least **one tax** on the invoice lines that targets the tax grid :ref:`VJ3 `;" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/italy.rst:441 +msgid "All invoice lines either have :guilabel:`Services` as **products**, or a tax with the :guilabel:`Services` as **tax scope**." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/italy.rst:445 +msgid "TD18 - Buying goods from EU" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/italy.rst:447 +msgid "Invoices issued within the EU follow a **standard format**, therefore only an integration of the existing invoice is required." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/italy.rst:450 +msgid "Odoo exports a transaction as `TD18` if the following conditions are met:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/italy.rst:453 +msgid "The **partner** is from an **EU** country;" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/italy.rst:454 +msgid "It has at least one tax on the invoice lines that targets the tax grid :ref:`VJ9 `;" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/italy.rst:455 +msgid "All invoice lines either have :guilabel:`Consumable` as **products**, or a tax with :guilabel:`Goods` as **tax scope**." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/italy.rst:459 +msgid "TD19 - Buying goods from VAT deposit" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/italy.rst:461 +msgid "Buying **goods** from a **foreign** vendor, but the **goods** are already in **Italy** in a **VAT deposit**." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/italy.rst:464 +msgid "From the EU: the *buyer* integrates the invoice received with the **VAT information** due in Italy (i.e., **vendor bill tax integration**);" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/italy.rst:466 +msgid "Non-EU: the *buyer* sends an invoice to *themselves* (i.e., **self-billing**)." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/italy.rst:468 +msgid "Odoo exports a transaction as a `TD19` if the following conditions are met:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/italy.rst:471 +msgid "It has at least one tax on the invoice lines that targets the tax grid :ref:`VJ3 `;" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/italy.rst:472 +msgid "All invoice lines either have :guilabel:`Consumables` as products, or a tax with :guilabel:`Goods` as **tax scope**." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/italy.rst:476 +msgid "TD24 - Deferred invoices" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/italy.rst:478 +msgid "The **deferred invoice** is an invoice that is **issued at a later time** than the sale of goods or the provision of services. A **deferred invoice** has to be issued at the latest within the **15th day** of the month following the delivery covered by the document." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/italy.rst:482 +msgid "It usually is a **summary invoice** containing a list of multiple sales of goods or services carried out in the month. The business is allowed to **group** the sales into **one invoice**, generally issued at the **end of the month** for accounting purposes. Deferred invoices are default for **wholesalers** having recurrent clients." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/italy.rst:487 +msgid "If the goods are transported by a **carrier**, every delivery has an associated **Documento di Transporto (DDT)**, or **Transport Document**. The deferred invoice **must** indicate the details of all the **DDTs** information for better tracing." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/italy.rst:492 +msgid "E-invoicing of deferred invoices requires the `l10n_it_stock_ddt` :ref:`module `. In this case, a dedicated :guilabel:`Document Type` `TD24` is used in the e-invoice." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/italy.rst:495 +msgid "Odoo exports transactions as `TD24` if the following conditions are met:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/italy.rst:498 +msgid "It is associated with deliveries whose **DDTs** have a **different** date than the issue date of the invoice." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/italy.rst:502 +msgid "TD28 - San Marino" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/italy.rst:507 +msgid "San Marino and Italy have special agreements on e-invoicing operations. As such, **invoices** follow the regular **reverse charge** rules. You can use the proper :guilabel:`Document Type` depending on the invoice type: `TD01`, `TD04`, `TD05`, `TD24`, `TD25`. Additional requirements are not enforced by Odoo. However, the user is requested by the **State** to:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/italy.rst:512 +msgid "Select a tax with the :guilabel:`Tax Exemption Kind` set to `N3.3`;" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/italy.rst:513 +msgid "Use the generic :abbr:`SdI (Sistema di Interscambio)` :guilabel:`Destination Code` `2R4GT08`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/italy.rst:515 +msgid "The invoice is then routed by a dedicated office in San Marino to the correct business." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/italy.rst:518 +msgid "Vendor Bills" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/italy.rst:520 +msgid "When a **paper bill** is received from San Marino, any Italian company **must** submit that invoice to the :abbr:`AdE (Agenzia delle Entrate)` by indicating the e-invoice's :guilabel:`Document Type` field with the special value `TD28`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/italy.rst:524 +msgid "Odoo exports a transaction as `TD28` if the following conditions are met:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/italy.rst:527 +msgid "It has at least one tax on the invoice lines that targets the tax grids :ref:`VJ `;" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/italy.rst:528 +msgid "The **country** of the partner is **San Marino**." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/italy.rst:531 +msgid "Public Administration Businesses (B2G)" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/italy.rst:533 +msgid ":abbr:`PA (Public Administration)` businesses are subjected to more control than private businesses as they handle public money coming from taxpayers. The :abbr:`EDI (Electronic Data Interchange)` process adds some steps to the :ref:`regular one `, as :abbr:`PA (Public Administration)` businesses can **accept** or **refuse** invoices." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/italy.rst:539 +msgid ":abbr:`PA (Public Administration)` businesses have a 6-digit long :guilabel:`Destination Code`, also called :abbr:`CUU (Codice Univoco Ufficio)`, that is **mandatory**, **PEC** address cannot be used in this case." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/italy.rst:544 +msgid "`Complete list of businesses that belong to the Public Administration along with their Destination Code `_" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/italy.rst:548 msgid "CIG, CUP, DatiOrdineAcquisto" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/italy.rst:437 -msgid "To ensure the effective traceability of payments by public administrations, electronic invoices issued to the public administrations must contain:" +#: ../../content/applications/finance/fiscal_localizations/italy.rst:550 +msgid "To ensure the effective traceability of payments by public administrations, electronic invoices issued to public administrations must contain:" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/italy.rst:440 +#: ../../content/applications/finance/fiscal_localizations/italy.rst:553 msgid "The :abbr:`CIG (Codice Identificativo Gara)`, except in cases of exclusion from traceability obligations provided by law n. 136 of August 13, 2010;" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/italy.rst:442 +#: ../../content/applications/finance/fiscal_localizations/italy.rst:555 msgid "The :abbr:`CUP (Codice Unico di Progetto)`, in case of invoices related to public works." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/italy.rst:444 -msgid "If the **XML** file requires it, the **Agenzia Delle Entrate** can *only* proceed payments of electronic invoices when the **XML** file contains a :abbr:`CIG (Codice Identificativo Gara)` and :abbr:`CUP (Codice Unico di Progetto)`. For each electronic invoice, it is **necessary** to indicate the :abbr:`CUU (Codice Univoco Ufficio)`, which represents the unique identifier code that allows the :abbr:`SdI (Sistema di Interscambio)` to correctly deliver the electronic invoice to the recipient office." +#: ../../content/applications/finance/fiscal_localizations/italy.rst:557 +msgid "If the XML file requires it, the :abbr:`AdE (Agenzia Delle Entrate)` can *only* proceed payments of electronic invoices when the XML file contains a :abbr:`CIG (Codice Identificativo Gara)` and :abbr:`CUP (Codice Unico di Progetto)`." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/italy.rst:452 -msgid "The :abbr:`Codice Unico di Progetto)` and the :abbr:`CIG (Codice Identificativo Gara)` must be included in one of the **2.1.2** (DatiOrdineAcquisto), **2.1.3** (Dati Contratto), **2.1.4** (DatiConvenzione), **2.1.5** (Date Ricezione), or **2.1.6** (Dati Fatture Collegate) information blocks. These correspond to the elements named :guilabel:`CodiceCUP` and :guilabel:`CodiceCIG` of the electronic invoice **XML** file, whose table can be found on the government `website `_." +#: ../../content/applications/finance/fiscal_localizations/italy.rst:562 +msgid "The :abbr:`CUP (Codice Unico di Progetto)` and the :abbr:`CIG (Codice Identificativo Gara)` must be included in one of the `DatiOrdineAcquisto`, `DatiContratto`, `DatiConvenzione`, `DateRicezione`, or `DatiFattureCollegate` XML tags." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/italy.rst:458 -msgid "The :abbr:`CUU (Codice Univoco Ufficio)` must be included in the electronic invoice corresponding to the element **1.1.4** (:guilabel:`CodiceDestinario`)." +#: ../../content/applications/finance/fiscal_localizations/italy.rst:566 +msgid "These correspond to the elements named :guilabel:`CodiceCUP` and :guilabel:`CodiceCIG` of the electronic invoice XML file, whose table can be found on the government `website `_." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/italy.rst:573 +msgid "Split Payment" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/italy.rst:575 +msgid "The :guilabel:`Split Payment` mechanism behaves much like :ref:`italy/reverse-charge`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/italy.rst:578 +msgid "When an Italian company bills a :abbr:`PA (Public Administration)` business - for example, cleaning services for a public building - the :abbr:`PA (Public Administration)` business self-reports the VAT to the Tax Agency themselves, and the vendor just has to select the appropriate tax with the right :guilabel:`Tax Exemption` for their invoice lines." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/italy.rst:583 +msgid "The specific :guilabel:`Scissione dei Pagamenti` fiscal position is available to deal with partners belonging to the :abbr:`PA (Public Administration)`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/italy.rst:592 +msgid "Digital qualified signature" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/italy.rst:594 +msgid "For invoices and bills intended for the :abbr:`PA (Public Administration)`, a **Digital Qualified Signature** is required for all files sent through the :abbr:`SdI (Sistema di Interscambio)`. The XML file must be certified using a certificate that is either:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/italy.rst:598 +msgid "a **smart card**;" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/italy.rst:599 +msgid "a **USB token**;" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/italy.rst:600 +msgid "an :abbr:`HSM (Hardware Security Module)`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/italy.rst:603 +msgid "Odoo **cannot** digitally sign documents for you. When a 6-digit long :guilabel:`Codice Destinatario` is detected, then the :abbr:`EDI (Electronic Data Interchange)` process stops, and the invoice is set on the :guilabel:`Requires user signature` state. You can download the document in XML, sign it with any :guilabel:`Digital Qualified Signature` provider's external program and send it through the :abbr:`AdE (Agenzia Delle Entrate)` portal." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/italy.rst:610 +msgid "Acceptance or Refusal" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/italy.rst:613 +msgid "As Odoo does not handle sending signed invoices to :abbr:`PA (Public Administration)` businesses, these states cannot be directly triggered by Odoo. When you upload the invoice on the :abbr:`AdE (Agenzia Delle Entrate)` portal, Odoo receives notifications about it, putting the correct :guilabel:`SdI State` on the invoice." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/italy.rst:618 +msgid "After receiving the invoice through the :abbr:`SdI (Sistema di Interscambio)`, the :abbr:`PA (Public Administration)` business has 15 days to accept the invoice. If it does, then the process ends here. If the :abbr:`PA (Public Administration)` business refuses the invoice, it is still considered valid once it is accepted by the :abbr:`SdI (Sistema di Interscambio)`. You then have to issue a credit note to compensate and send it to the :abbr:`SdI (Sistema di Interscambio)`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/italy.rst:625 +msgid "Expired Terms" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/italy.rst:627 +msgid "If the :abbr:`PA (Public Administration)` business doesn't reply within 15 days, you need to contact the :abbr:`PA (Public Administration)` business directly, sending them both the invoice and the received deadline notification by email. You can make an arrangement with them and manually set the correct :guilabel:`SdI State` on your invoice." msgstr "" #: ../../content/applications/finance/fiscal_localizations/kenya.rst:3 @@ -22225,7 +22045,7 @@ msgid "Once it is loaded on your computer, a wizard opens. You have to read and msgstr "" #: ../../content/applications/finance/fiscal_localizations/kenya.rst:76 -msgid "A new page opens, confirming your :doc:`IoT Box <../../productivity/iot/config/connect>` is up and running. Connect your physical device **Tremol G03 Control Unit (type C)** to your laptop via USB. In the :guilabel:`IoT Device` section, check that your Tremol G03 Control Unit (type C) appears, confirming the connection between the device and your computer." +msgid "A new page opens, confirming your :doc:`IoT Box <../../general/iot/config/connect>` is up and running. Connect your physical device **Tremol G03 Control Unit (type C)** to your laptop via USB. In the :guilabel:`IoT Device` section, check that your Tremol G03 Control Unit (type C) appears, confirming the connection between the device and your computer." msgstr "" #: ../../content/applications/finance/fiscal_localizations/kenya.rst:-1 @@ -22237,7 +22057,7 @@ msgid "If the device is not detected, try to plug it in again or click on the :g msgstr "" #: ../../content/applications/finance/fiscal_localizations/kenya.rst:90 -msgid ":doc:`Connect an IoT box to your database <../../productivity/iot/config/connect>`" +msgid ":doc:`Connect an IoT box to your database <../../general/iot/config/connect>`" msgstr "" #: ../../content/applications/finance/fiscal_localizations/kenya.rst:93 @@ -22721,7 +22541,7 @@ msgid "Tax accounts available for Odoo." msgstr "" #: ../../content/applications/finance/fiscal_localizations/mexico.rst:253 -msgid "To configure products, go to :menuselection:`Accounting --> Customers --> Products`, then select a product to configure, or :guilabel:`Create` a new one. In the :guilabel:`Accounting` tab, and in the :guilabel:`UNSPSC Product Category` field, select the category that represents the product. The process can be done manually, or through :doc:`a bulk import <../../general/export_import_data>`." +msgid "To configure products, go to :menuselection:`Accounting --> Customers --> Products`, then select a product to configure, or :guilabel:`Create` a new one. In the :guilabel:`Accounting` tab, and in the :guilabel:`UNSPSC Product Category` field, select the category that represents the product. The process can be done manually, or through :doc:`a bulk import <../../essentials/export_import_data>`." msgstr "" #: ../../content/applications/finance/fiscal_localizations/mexico.rst:259 @@ -23829,9 +23649,9 @@ msgstr "" msgid "IAP (Odoo In-App Purchase)" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/peru.rst:-1 #: ../../content/applications/finance/fiscal_localizations/peru.rst:117 #: ../../content/applications/finance/fiscal_localizations/peru.rst:181 +#: ../../content/applications/finance/fiscal_localizations/peru.rst:-1 msgid "Digiflow" msgstr "" @@ -24045,10 +23865,6 @@ msgstr "" msgid "**Local Peru**: Set this fiscal position on local customers." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/peru.rst:286 -msgid "Document Types" -msgstr "" - #: ../../content/applications/finance/fiscal_localizations/peru.rst:288 msgid "In some Latin American countries, including Peru, some accounting transactions like invoices and vendor bills are classified by document types, defined by the government fiscal authorities, in this case by the SUNAT." msgstr "" @@ -25274,8 +25090,8 @@ msgstr "" msgid "PayNow is a payment service platform that allows customers to make instant domestic payments to individuals and merchants in Singapore dollars via online and mobile banking." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/singapore.rst:-1 #: ../../content/applications/finance/fiscal_localizations/singapore.rst:18 +#: ../../content/applications/finance/fiscal_localizations/singapore.rst:-1 msgid "PayNow bank account configuration" msgstr "" @@ -25636,6 +25452,7 @@ msgstr "" #: ../../content/applications/finance/fiscal_localizations/switzerland.rst:118 #: ../../content/applications/finance/fiscal_localizations/switzerland.rst:120 #: ../../content/applications/finance/fiscal_localizations/switzerland.rst:130 +#: ../../content/applications/finance/fiscal_localizations/switzerland.rst:130 #: ../../content/applications/finance/fiscal_localizations/switzerland.rst:132 msgid "7.7%" msgstr "" @@ -25700,6 +25517,7 @@ msgstr "" #: ../../content/applications/finance/fiscal_localizations/switzerland.rst:126 #: ../../content/applications/finance/fiscal_localizations/switzerland.rst:128 #: ../../content/applications/finance/fiscal_localizations/switzerland.rst:134 +#: ../../content/applications/finance/fiscal_localizations/switzerland.rst:134 #: ../../content/applications/finance/fiscal_localizations/switzerland.rst:136 msgid "3.7%" msgstr "" @@ -26471,8 +26289,8 @@ msgstr "" msgid "Vietnamese QR banking is a payment service platform that allows customers to make instant domestic payments to individuals and merchants in Vietnamese dong via online and mobile banking." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/vietnam.rst:-1 #: ../../content/applications/finance/fiscal_localizations/vietnam.rst:18 +#: ../../content/applications/finance/fiscal_localizations/vietnam.rst:-1 msgid "Vietnamese QR banking bank account configuration" msgstr "" @@ -28445,684 +28263,3 @@ msgstr "" #: ../../content/applications/finance/payment_providers/xendit.rst:42 msgid "Fill in the :guilabel:`Secret Key` and :guilabel:`Webhook Token` fields with the information saved at the step :ref:`payment_providers/xendit/configure_dashboard`." msgstr "" - -#: ../../content/applications/finance/sign.rst:3 -msgid "Sign" -msgstr "" - -#: ../../content/applications/finance/sign.rst:5 -msgid "**Odoo Sign** allows you to send, sign, and approve documents online, using electronic signatures." -msgstr "" - -#: ../../content/applications/finance/sign.rst:7 -msgid "An **electronic signature** shows a person's agreement to the content of a document. Just like a handwritten signature, the electronic one represents a legal bounding by the terms of the signed document." -msgstr "" - -#: ../../content/applications/finance/sign.rst:11 -msgid "With Sign, you can upload any PDF file and add fields to it. These fields can be automatically filled in with the user's details present in your database." -msgstr "" - -#: ../../content/applications/finance/sign.rst:15 -msgid "`Odoo Sign: product page `_" -msgstr "" - -#: ../../content/applications/finance/sign.rst:16 -msgid "`Odoo Tutorials: Sign [video] `_" -msgstr "" - -#: ../../content/applications/finance/sign.rst:19 -msgid "Validity of electronic signatures" -msgstr "" - -#: ../../content/applications/finance/sign.rst:21 -msgid "Documents signed via the Sign app are valid electronic signatures in the European Union and the United States of America. They also meet the requirements for electronic signatures in most countries. The legal validity of electronic signatures generated by Odoo depends on your country's legislation. Companies doing business abroad should also consider other countries' electronic signature laws." -msgstr "" - -#: ../../content/applications/finance/sign.rst:28 -msgid "European Union" -msgstr "" - -#: ../../content/applications/finance/sign.rst:30 -msgid "The `eIDAS regulation `_ establishes the framework for electronic signatures in the `27 member states of the European Union `_. It distinguishes three types of electronic signatures:" -msgstr "" - -#: ../../content/applications/finance/sign.rst:35 -msgid "Simple electronic signatures" -msgstr "" - -#: ../../content/applications/finance/sign.rst:36 -msgid "Advanced electronic signatures" -msgstr "" - -#: ../../content/applications/finance/sign.rst:37 -msgid "Qualified electronic signatures" -msgstr "" - -#: ../../content/applications/finance/sign.rst:39 -msgid "Odoo generates the first type, **simple electronic signatures**; these signatures are legally valid in the EU, as stated in the eIDAS regulation." -msgstr "" - -#: ../../content/applications/finance/sign.rst:42 -msgid "Electronic signatures may not be automatically recognized as valid. You may need to bring supporting evidence of a signature's validity. While the Sign app provides a simple electronic signature, some supporting evidence is automatically collected during the signature process, such as:" -msgstr "" - -#: ../../content/applications/finance/sign.rst:47 -msgid "Email and SMS validation (if enabled)" -msgstr "" - -#: ../../content/applications/finance/sign.rst:48 -msgid "Strong identity proof through itsme® (available in Belgium and the Netherlands)" -msgstr "" - -#: ../../content/applications/finance/sign.rst:49 -msgid "Timestamped, IP and geographically traceable access logs to the documents and their associated signatures" -msgstr "" - -#: ../../content/applications/finance/sign.rst:51 -msgid "Document traceability and inalterability (any alteration made to a signed document is detected by Odoo with the use of cryptographic proofs)" -msgstr "" - -#: ../../content/applications/finance/sign.rst:55 -msgid "United States of America" -msgstr "" - -#: ../../content/applications/finance/sign.rst:57 -msgid "The `ESIGN Act (Electronic Signatures in Global and National Commerce Act) `_, at the interstate and international levels, and the `UETA (Uniform Electronic Transactions Act) `_, at the state level, provide the legal framework for electronic signatures. Note that `Illinois `_ and `New York `_ have not adopted the UETA, but similar acts instead." -msgstr "" - -#: ../../content/applications/finance/sign.rst:66 -msgid "Overall, to be recognized as valid, electronic signatures have to meet five criteria:" -msgstr "" - -#: ../../content/applications/finance/sign.rst:68 -msgid "The signer must show a clear **intent to sign**. For example, using a mouse to draw a signature can show intent. The signer must also have the option to opt out of the electronic document." -msgstr "" - -#: ../../content/applications/finance/sign.rst:70 -msgid "The signer must first express or imply their **consent to conduct business electronically**." -msgstr "" - -#: ../../content/applications/finance/sign.rst:71 -msgid "**The signature must be clearly attributed**. In Odoo, metadata, such as the signer's IP address, is added to the signature, which can be used as supporting evidence." -msgstr "" - -#: ../../content/applications/finance/sign.rst:73 -msgid "**The signature must be associated with the signed document**, for example, by keeping a record detailing how the signature was captured." -msgstr "" - -#: ../../content/applications/finance/sign.rst:75 -msgid "Electronically signed documents need to be **retained and stored** by all parties involved; for example, by providing the signer either a fully-executed copy or the possibility to download a copy." -msgstr "" - -#: ../../content/applications/finance/sign.rst:80 -msgid "The above information has no legal value; it is only provided for general informational purposes. As laws governing electronic signatures rapidly evolve, we cannot guarantee that all information is up-to-date. We advise contacting a local attorney for legal advice regarding electronic signature compliance and validity." -msgstr "" - -#: ../../content/applications/finance/sign.rst:86 -msgid "Send a document to sign" -msgstr "" - -#: ../../content/applications/finance/sign.rst:89 -msgid "One-time signature" -msgstr "" - -#: ../../content/applications/finance/sign.rst:91 -msgid "You can click :guilabel:`Upload a PDF to sign` from your dashboard for a one-time signature. Select your document, open it, and drag and drop the required :ref:`fields ` in your document. You can modify the :ref:`role ` assigned to a field by clicking on it and selecting the one you want." -msgstr "" - -#: ../../content/applications/finance/sign.rst:96 -msgid "When ready, click :guilabel:`Send`, and fill in the required fields. Once sent, your document remains available. Go to :menuselection:`Documents --> All Documents` to see your document and the status of the signatures." -msgstr "" - -#: ../../content/applications/finance/sign.rst:-1 -msgid "Signature status" -msgstr "" - -#: ../../content/applications/finance/sign.rst:104 -msgid "Validity dates and reminders" -msgstr "" - -#: ../../content/applications/finance/sign.rst:106 -msgid "You can set **validity dates** on limited-duration agreement documents or send **automatic email reminders** to obtain signatures on time. From your dashboard, click :guilabel:`Send` on your document. On the new page, go to the :guilabel:`Options` section and fill in the :guilabel:`Valid Until` and :guilabel:`Reminder` fields." -msgstr "" - -#: ../../content/applications/finance/sign.rst:112 -#: ../../content/applications/finance/spreadsheet/templates.rst:3 -msgid "Templates" -msgstr "" - -#: ../../content/applications/finance/sign.rst:114 -msgid "You can create document templates when you have to send the same document several times. From your dashboard, click :guilabel:`Upload a PDF template`. Select the document and add the required :ref:`fields `. You can modify the :ref:`role ` of a field by clicking on it and selecting the one you want." -msgstr "" - -#: ../../content/applications/finance/sign.rst:119 -msgid "Click :guilabel:`Template Properties` to add :guilabel:`Tags` to your template, define a :guilabel:`Signed Document Workspace`, add :guilabel:`Signed Document Tags`, set a :guilabel:`Redirect Link` that will be available in the signature confirmation message received after the signature, or define :guilabel:`Authorized Users` if you want to restrict the use of your template to specific authorized users or groups." -msgstr "" - -#: ../../content/applications/finance/sign.rst:125 -msgid "Your templates are visible by default on your dashboard. You can click :guilabel:`Send` to quickly send a document template to a signer or :guilabel:`Sign Now` if you are ready to sign your document immediately." -msgstr "" - -#: ../../content/applications/finance/sign.rst:130 -msgid "You can **create a template from a document that was previously sent**. To do so, go to :menuselection:`Documents --> All Documents`. On the document you want to retrieve, click on the the vertical ellipsis (:guilabel:`⋮`), then :guilabel:`Template`. Click on the vertical ellipsis (:guilabel:`⋮`) again, then :guilabel:`Restore`. Your document now appears on your dashboard next to your other templates." -msgstr "" - -#: ../../content/applications/finance/sign.rst:139 -msgid "Roles" -msgstr "" - -#: ../../content/applications/finance/sign.rst:141 -msgid "Each field in a Sign document is related to a role corresponding to a specific person. When a document is being signed, the person assigned to the role must fill in their assigned fields and sign it." -msgstr "" - -#: ../../content/applications/finance/sign.rst:145 -msgid "Roles are available by going to :menuselection:`Sign --> Configuration --> Roles`." -msgstr "" - -#: ../../content/applications/finance/sign.rst:147 -msgid "It is possible to update existing roles or to create new roles by clicking on :guilabel:`New`. Choose a :guilabel:`Role Name`, add an :guilabel:`Extra Authentication Step` to confirm the identity of the signing person, and if the document can be reassigned to another contact, select :guilabel:`Change Authorized` for the role. A :guilabel:`Color` can also be chosen for the role. This color can help understand which roles are responsible for which field when configuring a template." -msgstr "" - -#: ../../content/applications/finance/sign.rst:155 -msgid "Secured identification" -msgstr "" - -#: ../../content/applications/finance/sign.rst:157 -msgid "As the owner of a document, you may request an :guilabel:`Extra Authentication Step` through :ref:`SMS verification ` or via :ref:`Itsme® ` (available in Belgium and the Netherlands). Both authentication options require :ref:`credits `. If you do not have any credits left, the authentication steps will be skipped." -msgstr "" - -#: ../../content/applications/finance/sign.rst:163 -msgid ":doc:`In-App Purchase (IAP) <../general/in_app_purchase>`" -msgstr "" - -#: ../../content/applications/finance/sign.rst:164 -msgid ":doc:`SMS pricing and FAQ <../marketing/sms_marketing/pricing/pricing_and_faq>`" -msgstr "" - -#: ../../content/applications/finance/sign.rst:169 -msgid "SMS verification" -msgstr "" - -#: ../../content/applications/finance/sign.rst:171 -msgid "Go to :menuselection:`Sign --> Configuration --> Roles`. Click in the :guilabel:`Extra Authentication Step` column for the role, and select :guilabel:`Unique Code Via SMS`." -msgstr "" - -#: ../../content/applications/finance/sign.rst:175 -msgid "Before being able to send SMS Text Messages, you need to register your phone number. To do so, go to :menuselection:`Sign --> Configuration --> Settings` and click :guilabel:`Buy credits` under :guilabel:`Authenticate by SMS`." -msgstr "" - -#: ../../content/applications/finance/sign.rst:179 -msgid "Go to the document to sign, add the field for which the SMS verification is required, for example, the :guilabel:`Signature` field, and click :guilabel:`Send`. On the new page, select the :guilabel:`customer` and click :guilabel:`Send`." -msgstr "" - -#: ../../content/applications/finance/sign.rst:183 -msgid "The person signing the document fills in the :guilabel:`Signature` field, then :guilabel:`Sign`, and clicks :guilabel:`Validate & Send Completed Document`. A :guilabel:`Final Validation` page pops up where to add their phone number. One-time codes are sent by SMS." -msgstr "" - -#: ../../content/applications/finance/sign.rst:-1 -msgid "Add a hash to your document" -msgstr "" - -#: ../../content/applications/finance/sign.rst:191 -msgid "This feature is enabled by default." -msgstr "" - -#: ../../content/applications/finance/sign.rst:192 -msgid "As soon as the :guilabel:`Extra Authentication Step` applies to a role, this validation step is requested for any field assigned to this role." -msgstr "" - -#: ../../content/applications/finance/sign.rst:198 -msgid "Itsme®" -msgstr "" - -#: ../../content/applications/finance/sign.rst:200 -msgid "Itsme® authentication can be used to allow signatories to provide their identity using itsme®. This feature is only available in **Belgium** and the **Netherlands**." -msgstr "" - -#: ../../content/applications/finance/sign.rst:203 -msgid "The feature can be enabled in :guilabel:`Sign Settings` and applies automatically to the :guilabel:`Customer (identified with itsme®)` role. To enable it for other roles, go to :menuselection:`Sign --> Configuration --> Roles`. Click in the :guilabel:`Extra Authentication Step` column for the role, and select :guilabel:`Via itsme®`." -msgstr "" - -#: ../../content/applications/finance/sign.rst:208 -msgid "Go to the document that needs to be signed and add the :guilabel:`Signature` field. Switch to any role configured to use the feature, and click :guilabel:`Validate` and :guilabel:`Send`." -msgstr "" - -#: ../../content/applications/finance/sign.rst:-1 -msgid "select customer identified with itsme®" -msgstr "" - -#: ../../content/applications/finance/sign.rst:214 -msgid "Upon signing the document, the signer completes the :guilabel:`Signature` field and proceeds by clicking on :guilabel:`Validate & Send Completed Document`, triggering a :guilabel:`Final verification` page where authentication via itsme® is required." -msgstr "" - -#: ../../content/applications/finance/sign.rst:219 -msgid "Signatory hash" -msgstr "" - -#: ../../content/applications/finance/sign.rst:221 -msgid "Each time someone signs a document, a **hash** - a unique digital signature of the operation - is generated to ensure traceability, integrity, and inalterability. This process guarantees that any changes made after a signature is affixed can be easily detected, maintaining the document's authenticity and security throughout its lifecycle." -msgstr "" - -#: ../../content/applications/finance/sign.rst:226 -msgid "A visual security frame displaying the beginning of the hash is added to the signatures. Internal users can hide or show it by turning the :guilabel:`Frame` option on or off when signing the document." -msgstr "" - -#: ../../content/applications/finance/sign.rst:-1 -msgid "Adding the visual security frame to a signature." -msgstr "" - -#: ../../content/applications/finance/sign.rst:238 -msgid "Tags can be used to categorize and organize documents, allowing users to quickly search for and filter documents based on specific criteria." -msgstr "" - -#: ../../content/applications/finance/sign.rst:241 -msgid "You can manage tags by going to :menuselection:`Configuration --> Tags`. To create a tag, click :guilabel:`New`. On the new line, add the :guilabel:`Tag Name` and select a :guilabel:`Color Index` for your tag." -msgstr "" - -#: ../../content/applications/finance/sign.rst:245 -msgid "To apply a tag to a document, use the dropdown list available in your document." -msgstr "" - -#: ../../content/applications/finance/sign.rst:248 -msgid "You can modify the tags of a signed document by going to :menuselection:`Documents --> All Documents`, clicking the vertical ellipsis (:guilabel:`⋮`) on your document, then :guilabel:`Details`, and modifying your :guilabel:`Tags`." -msgstr "" - -#: ../../content/applications/finance/sign.rst:253 -msgid "Sign order" -msgstr "" - -#: ../../content/applications/finance/sign.rst:255 -msgid "When a document needs to be signed by different parties, the signing order lets you control the order in which your recipients receive it for signature." -msgstr "" - -#: ../../content/applications/finance/sign.rst:258 -msgid "After uploading a PDF with at least two signature fields with two different roles and clicking :guilabel:`Send`, toggle the :guilabel:`Specify Signing Order` button and search for the signer's name or email information to add them. You can decide on the signing order by typing **1** or **2** in the first column." -msgstr "" - -#: ../../content/applications/finance/sign.rst:263 -msgid "Each recipient receives the signature request notification only once the previous recipient has completed their action." -msgstr "" - -#: ../../content/applications/finance/sign.rst:267 -msgid "`Odoo Quick Tips: Sign order [video] `_" -msgstr "" - -#: ../../content/applications/finance/sign.rst:272 -msgid "Field types" -msgstr "" - -#: ../../content/applications/finance/sign.rst:274 -msgid "Fields are used in a document to indicate what information must be completed by the signers. You can add fields to your document simply by dragging and dropping them for the left column into your document." -msgstr "" - -#: ../../content/applications/finance/sign.rst:278 -msgid "Various field types can be used to sign documents (placeholder, autocompletion, etc.). By configuring your own field types, also known as signature item types, the signing process can be even faster for your customers, partners, and employees." -msgstr "" - -#: ../../content/applications/finance/sign.rst:282 -msgid "To create and edit field types, go to :menuselection:`Sign --> Configuration --> Settings --> Edit field types`." -msgstr "" - -#: ../../content/applications/finance/sign.rst:285 -msgid "You can select an existing field by clicking on it, or you can :guilabel:`Create` a new one. First, edit the :guilabel:`Field Name`. Then, select a :guilabel:`Field Type`:" -msgstr "" - -#: ../../content/applications/finance/sign.rst:288 -msgid ":guilabel:`Signature`: users are asked to enter their signature either by drawing it, generating an automatic one based on their name, or uploading a local file (usually an image). Each subsequent :guilabel:`Signature` field type then reuses the data entered in the first field." -msgstr "" - -#: ../../content/applications/finance/sign.rst:291 -msgid ":guilabel:`Initial`: users are asked to enter their initials, in a similar way to the :guilabel:`Signature` field." -msgstr "" - -#: ../../content/applications/finance/sign.rst:293 -msgid ":guilabel:`Text`: users enter text on a single line." -msgstr "" - -#: ../../content/applications/finance/sign.rst:294 -msgid ":guilabel:`Multiline Text`: users enter text on multiple lines." -msgstr "" - -#: ../../content/applications/finance/sign.rst:295 -msgid ":guilabel:`Checkbox`: users can tick a box (e.g., to mark their approval or consent)." -msgstr "" - -#: ../../content/applications/finance/sign.rst:296 -msgid ":guilabel:`Selection`: users choose a single option from a variety of options." -msgstr "" - -#: ../../content/applications/finance/sign.rst:298 -msgid "The :guilabel:`Auto-fill Partner Field` setting is used to automatically fill in a field during the signature process. It uses the value of one of the fields on the contact (`res.partner`) model of the person signing the document. To do so, enter the contact model field's technical name." -msgstr "" - -#: ../../content/applications/finance/sign.rst:303 -msgid "To know the technical name of a field, enable developer mode and hover your mouse on the question mark next to the field." -msgstr "" - -#: ../../content/applications/finance/sign.rst:307 -msgid "Auto-completed values are suggestions and can be modified as required by the person signing the document." -msgstr "" - -#: ../../content/applications/finance/sign.rst:310 -msgid "The size of the fields can also be changed by editing the :guilabel:`Default Width` and :guilabel:`Default Height`. Both sizes are defined as a percentage of the full page expressed as a decimal, with 1 equalling the full page's width or height. By default, the width of new fields you create is set to 15% (0.150) of a full page's width, while their height is set to 1.5% (0.015) of a full page's height." -msgstr "" - -#: ../../content/applications/finance/sign.rst:316 -msgid "Next, write a :guilabel:`Tip`. Tips are displayed inside arrows on the left-hand side of the user's screen during the signing process to help them understand what the step entails (e.g., \"Sign here\" or “Fill in your birthdate”). You can also use a :guilabel:`Placeholder` text to be displayed inside the field before it is completed." -msgstr "" - -#: ../../content/applications/finance/sign.rst:-1 -msgid "Tip and placeholder example in Odoo Sign" -msgstr "" - -#: ../../content/applications/finance/spreadsheet.rst:6 -msgid "Spreadsheet" -msgstr "" - -#: ../../content/applications/finance/spreadsheet.rst:14 -msgid "Spreadsheet lets you organize, analyze, and visualize your data in tabular form. Among others, you can:" -msgstr "" - -#: ../../content/applications/finance/spreadsheet.rst:17 -msgid ":doc:`Insert and link your Odoo data (pivots, graphs, lists, and menus) `." -msgstr "" - -#: ../../content/applications/finance/spreadsheet.rst:18 -msgid ":doc:`Use default templates or create new ones `." -msgstr "" - -#: ../../content/applications/finance/spreadsheet.rst:19 -msgid "Format data." -msgstr "" - -#: ../../content/applications/finance/spreadsheet.rst:20 -msgid "Use formulas and functions." -msgstr "" - -#: ../../content/applications/finance/spreadsheet.rst:21 -msgid "Sort and filter data." -msgstr "" - -#: ../../content/applications/finance/spreadsheet.rst:28 -msgid "Some of Spreadsheet's main :abbr:`UI (user interface)` elements are highlighted and defined below." -msgstr "" - -#: ../../content/applications/finance/spreadsheet.rst:-1 -msgid "Spreadsheet main UI elements" -msgstr "" - -#: ../../content/applications/finance/spreadsheet.rst:34 -msgid "Menu bar" -msgstr "" - -#: ../../content/applications/finance/spreadsheet.rst:35 -msgid "Top bar" -msgstr "" - -#: ../../content/applications/finance/spreadsheet.rst:36 -msgid "Formula bar" -msgstr "" - -#: ../../content/applications/finance/spreadsheet.rst:37 -msgid "Filters button" -msgstr "" - -#: ../../content/applications/finance/spreadsheet.rst:38 -msgid "Row header" -msgstr "" - -#: ../../content/applications/finance/spreadsheet.rst:39 -msgid "Column header" -msgstr "" - -#: ../../content/applications/finance/spreadsheet.rst:40 -msgid "Cell menu" -msgstr "" - -#: ../../content/applications/finance/spreadsheet.rst:41 -msgid "Bottom bar" -msgstr "" - -#: ../../content/applications/finance/spreadsheet/insert.rst:3 -msgid "Link Odoo data" -msgstr "" - -#: ../../content/applications/finance/spreadsheet/insert.rst:5 -msgid "You can insert and link several elements from your database in your spreadsheets, namely:" -msgstr "" - -#: ../../content/applications/finance/spreadsheet/insert.rst:7 -msgid "pivots," -msgstr "" - -#: ../../content/applications/finance/spreadsheet/insert.rst:8 -msgid "graphs," -msgstr "" - -#: ../../content/applications/finance/spreadsheet/insert.rst:9 -msgid "lists, and" -msgstr "" - -#: ../../content/applications/finance/spreadsheet/insert.rst:10 -msgid "links to menus (i.e., a clickable link to a view of a specific model)." -msgstr "" - -#: ../../content/applications/finance/spreadsheet/insert.rst:12 -msgid "Before inserting :ref:`pivots `, :ref:`graphs `, or lists, ensure they are tailored to your needs, as some elements are more quickly - or only - configurable in their respective view." -msgstr "" - -#: ../../content/applications/finance/spreadsheet/insert.rst:16 -msgid "To insert pivots and graphs, click :guilabel:`Insert in spreadsheet` from any pivot or graph view." -msgstr "" - -#: ../../content/applications/finance/spreadsheet/insert.rst:17 -msgid "To insert lists, click :menuselection:`Favorites --> Insert list in spreadsheet` from any list view." -msgstr "" - -#: ../../content/applications/finance/spreadsheet/insert.rst:19 -msgid "To insert links to menus, click :menuselection:`Favorites --> Link menu in spreadsheet` from any view." -msgstr "" - -#: ../../content/applications/finance/spreadsheet/insert.rst:22 -msgid "In the pop-up box, either create a new spreadsheet by selecting :guilabel:`Blank spreadsheet` or insert it in an existing one by selecting it and clicking :guilabel:`Confirm`." -msgstr "" - -#: ../../content/applications/finance/spreadsheet/insert.rst:-1 -msgid "Inserting a pivot in a spreadsheet" -msgstr "" - -#: ../../content/applications/finance/spreadsheet/insert.rst:30 -msgid "By default, new spreadsheets are saved under the :guilabel:`Spreadsheet` workspace of the Documents app." -msgstr "" - -#: ../../content/applications/finance/spreadsheet/insert.rst:36 -msgid "Updating data" -msgstr "" - -#: ../../content/applications/finance/spreadsheet/insert.rst:38 -msgid "Once inserted in a spreadsheet, your data is kept up-to-date, reflecting any changes made to your database. Reopening the spreadsheet reloads the linked data." -msgstr "" - -#: ../../content/applications/finance/spreadsheet/insert.rst:42 -msgid "To update pivots and lists data without reopening a spreadsheet, go to the menu bar and click :menuselection:`Data --> Refresh all data`." -msgstr "" - -#: ../../content/applications/finance/spreadsheet/insert.rst:46 -msgid "Pivot data" -msgstr "" - -#: ../../content/applications/finance/spreadsheet/insert.rst:48 -msgid "Using :guilabel:`Refresh all data` only updates existing pivot cells. If new cells need to be added, go to the menu bar and click :menuselection:`Data --> Re-insert pivot` to fully update the pivot. Alternatively, click :guilabel:`Insert pivot`, select the pivot, and tick :guilabel:`Display missing cells only` to preview first the missing data." -msgstr "" - -#: ../../content/applications/finance/spreadsheet/insert.rst:0 -msgid "Displaying missing cells in a pivot" -msgstr "" - -#: ../../content/applications/finance/spreadsheet/insert.rst:57 -msgid "To change which records are :ref:`used by the pivot `, right-click on a pivot cell, select :guilabel:`See pivot properties`, and click :guilabel:`Edit domain`." -msgstr "" - -#: ../../content/applications/finance/spreadsheet/templates.rst:5 -msgid "Spreadsheet templates allow you to quickly create spreadsheets without starting from scratch." -msgstr "" - -#: ../../content/applications/finance/spreadsheet/templates.rst:7 -msgid "Several pre-built templates are available when creating a new spreadsheet from the **Documents** app, such as:" -msgstr "" - -#: ../../content/applications/finance/spreadsheet/templates.rst:10 -msgid ":ref:`budget reports `," -msgstr "" - -#: ../../content/applications/finance/spreadsheet/templates.rst:11 -msgid ":ref:`pipeline revenue reports `, or" -msgstr "" - -#: ../../content/applications/finance/spreadsheet/templates.rst:12 -msgid ":ref:`sales commission report `." -msgstr "" - -#: ../../content/applications/finance/spreadsheet/templates.rst:-1 -msgid "View of all the default templates" -msgstr "" - -#: ../../content/applications/finance/spreadsheet/templates.rst:17 -msgid "You can also :ref:`save any spreadsheet as a template ` and :ref:`manage and edit existing templates `." -msgstr "" - -#: ../../content/applications/finance/spreadsheet/templates.rst:21 -msgid "Default templates" -msgstr "" - -#: ../../content/applications/finance/spreadsheet/templates.rst:26 -msgid "Accounting: budget reports" -msgstr "" - -#: ../../content/applications/finance/spreadsheet/templates.rst:28 -msgid "Budget reports compare a company's actual spending with its budget over a defined period. Two templates are available: one uses quarterly intervals (:guilabel:`Budget Report (Quarterly)`), while the other uses monthly intervals (:guilabel:`Budget Report (Monthly)`)." -msgstr "" - -#: ../../content/applications/finance/spreadsheet/templates.rst:-1 -msgid "Extract of a budget report" -msgstr "" - -#: ../../content/applications/finance/spreadsheet/templates.rst:35 -msgid "The cells under the :guilabel:`Actuals` column are automatically filled in with the amount of money made and spent over the corresponding period (month or quarter). The data is taken from posted journal items under :ref:`income and expense accounts `." -msgstr "" - -#: ../../content/applications/finance/spreadsheet/templates.rst:40 -msgid "Journal items under the :guilabel:`Other Income` account type are not considered when collecting data." -msgstr "" - -#: ../../content/applications/finance/spreadsheet/templates.rst:43 -msgid "To analyze your budget's performance, fill the cells under the :guilabel:`Budget` column with how much money you expect to make (:guilabel:`Income` rows) and spend (:guilabel:`Expenses` rows) over the related period and per account. Then, the performance (:guilabel:`Perf.`) column compares :guilabel:`Actuals` data to their corresponding budget, expressed as a percentage." -msgstr "" - -#: ../../content/applications/finance/spreadsheet/templates.rst:48 -msgid "Lastly, the :guilabel:`Net Profit` row represents the total :guilabel:`Income` minus the total :guilabel:`Expenses` for the :guilabel:`Actuals` and :guilabel:`Budget` columns." -msgstr "" - -#: ../../content/applications/finance/spreadsheet/templates.rst:54 -msgid "CRM: pipeline revenue reports" -msgstr "" - -#: ../../content/applications/finance/spreadsheet/templates.rst:56 -msgid "Two pipeline revenue reports are available. The :guilabel:`Pipeline Revenue Report (Monthly)` is dedicated to one-time revenue (:abbr:`NRR (non-recurring revenue)`), while the :guilabel:`MRR/NRR Pipeline Revenue Report (Monthly)` covers recurring and non-recurring revenue (:abbr:`MRR (monthly recurring revenue)`)." -msgstr "" - -#: ../../content/applications/finance/spreadsheet/templates.rst:62 -msgid "Enable :guilabel:`Recurring Revenues` by going to :menuselection:`CRM --> Configuration --> Settings`." -msgstr "" - -#: ../../content/applications/finance/spreadsheet/templates.rst:-1 -msgid "Extract of a pipeline revenue report" -msgstr "" - -#: ../../content/applications/finance/spreadsheet/templates.rst:68 -msgid "The cells under the :guilabel:`Actuals` column are automatically filled in with the amount of monthly revenue from **won** opportunities." -msgstr "" - -#: ../../content/applications/finance/spreadsheet/templates.rst:71 -msgid "To compute the revenue performance, fill in the monthly revenue targets." -msgstr "" - -#: ../../content/applications/finance/spreadsheet/templates.rst:73 -msgid "For the :guilabel:`Revenue by Team` sheet, fill in the cells under the :guilabel:`Target` columns for each sales team." -msgstr "" - -#: ../../content/applications/finance/spreadsheet/templates.rst:75 -msgid "For the :guilabel:`Revenue by Salesperson` sheet, open the :guilabel:`Targets` sheet and fill in the cells next to each salesperson. Use the :guilabel:`Monthly Factor` table below to adapt the main targets depending on the month of the year." -msgstr "" - -#: ../../content/applications/finance/spreadsheet/templates.rst:79 -msgid "Then, the performance (:guilabel:`Perf.`) column compares :guilabel:`Actuals` data to their related budget, expressed as a percentage." -msgstr "" - -#: ../../content/applications/finance/spreadsheet/templates.rst:82 -msgid "Lastly, the :guilabel:`Forecasted` column gathers the monthly revenue of leads multiplied by their :guilabel:`Probability` percentage." -msgstr "" - -#: ../../content/applications/finance/spreadsheet/templates.rst:86 -msgid "For actuals and forecasts:" -msgstr "" - -#: ../../content/applications/finance/spreadsheet/templates.rst:88 -msgid "The :guilabel:`Expected Closing` date found on leads is used to assign them to a month." -msgstr "" - -#: ../../content/applications/finance/spreadsheet/templates.rst:89 -msgid "The recurring monthly revenue is used even if the recurring plan's number of months is set to a different value than 1 month. For example, a yearly plan's revenue is divided by 12 months." -msgstr "" - -#: ../../content/applications/finance/spreadsheet/templates.rst:95 -msgid "Sales: sales commission" -msgstr "" - -#: ../../content/applications/finance/spreadsheet/templates.rst:97 -msgid "This report presents the monthly commission earned or due to each salesperson." -msgstr "" - -#: ../../content/applications/finance/spreadsheet/templates.rst:-1 -msgid "Extract of a sales commission report" -msgstr "" - -#: ../../content/applications/finance/spreadsheet/templates.rst:102 -msgid "The :guilabel:`Rate` column is pre-filled with the percentage rate from the :guilabel:`Rates` tab, which can be customized for each product category according to the company's policy. Adjusting the rate for a specific product category automatically updates the commission amount for that category." -msgstr "" - -#: ../../content/applications/finance/spreadsheet/templates.rst:106 -msgid "The :guilabel:`Invoiced` column shows the total amount of untaxed invoices grouped by salesperson and month." -msgstr "" - -#: ../../content/applications/finance/spreadsheet/templates.rst:109 -msgid "Lastly, the :guilabel:`Comm.` column is computed by multiplying the invoiced amount with the rate percentage." -msgstr "" - -#: ../../content/applications/finance/spreadsheet/templates.rst:115 -msgid "Save a spreadsheet as a template" -msgstr "" - -#: ../../content/applications/finance/spreadsheet/templates.rst:117 -msgid "Any spreadsheet can be saved as a template. From the menu bar, click :menuselection:`File --> Save as template`. Modify the default :guilabel:`Template Name` if necessary and click :guilabel:`Confirm`." -msgstr "" - -#: ../../content/applications/finance/spreadsheet/templates.rst:122 -msgid "Templates are available to all users on the database." -msgstr "" - -#: ../../content/applications/finance/spreadsheet/templates.rst:127 -msgid "Manage and edit templates" -msgstr "" - -#: ../../content/applications/finance/spreadsheet/templates.rst:129 -msgid "Manage templates by going to :menuselection:`Documents --> Configuration --> Spreadsheet Templates`. Remove the :guilabel:`My Templates` :ref:`filter ` to view all templates in the database." -msgstr "" - -#: ../../content/applications/finance/spreadsheet/templates.rst:133 -msgid "To edit an existing template, click `✎ Edit` next to the desired template. Modifications are automatically saved." -msgstr "" - -#: ../../content/applications/finance/spreadsheet/templates.rst:137 -msgid "Use the download button under the :guilabel:`Data` column to export a template in JSON format. The file can be imported into another database." -msgstr "" diff --git a/locale/sources/general.pot b/locale/sources/general.pot index d2204a329..d5fe7ea05 100644 --- a/locale/sources/general.pot +++ b/locale/sources/general.pot @@ -8,7 +8,7 @@ msgid "" msgstr "" "Project-Id-Version: Odoo 17.0\n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2024-03-08 12:48+0000\n" +"POT-Creation-Date: 2024-03-25 16:01+0000\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME \n" "Language-Team: LANGUAGE \n" @@ -17,7 +17,7 @@ msgstr "" "Content-Transfer-Encoding: 8bit\n" #: ../../content/applications/general.rst:3 -msgid "Miscellaneous" +msgid "General settings" msgstr "" #: ../../content/applications/general/apps_modules.rst:3 @@ -85,581 +85,836 @@ msgid "Upgrade apps and modules" msgstr "" #: ../../content/applications/general/apps_modules.rst:47 -msgid "On some occasions, new improvements or app features are added to :doc:`supported versions of Odoo `. To be able to use them, you must **upgrade** your app." +msgid "On some occasions, new improvements or app features are added to :doc:`supported versions of Odoo `. To be able to use them, you must **upgrade** your app." msgstr "" -#: ../../content/applications/general/apps_modules.rst:51 +#: ../../content/applications/general/apps_modules.rst:50 msgid "Go to :menuselection:`Apps`, click on the *dropdown menu* of the app you want to upgrade, then on *Upgrade*." msgstr "" -#: ../../content/applications/general/apps_modules.rst:57 +#: ../../content/applications/general/apps_modules.rst:56 msgid "Uninstall apps and modules" msgstr "" -#: ../../content/applications/general/apps_modules.rst:59 +#: ../../content/applications/general/apps_modules.rst:58 msgid "Go to :menuselection:`Apps`, click on the *dropdown menu* of the app you want to uninstall, then on *Uninstall*." msgstr "" -#: ../../content/applications/general/apps_modules.rst:65 +#: ../../content/applications/general/apps_modules.rst:64 msgid "Some apps have dependencies, meaning that one app requires another. Therefore, uninstalling one app may uninstall multiple apps and modules. Odoo warns you which dependent apps and modules are affected by it." msgstr "" -#: ../../content/applications/general/apps_modules.rst:72 +#: ../../content/applications/general/apps_modules.rst:71 msgid "To complete the uninstallation, click on *Confirm*." msgstr "" -#: ../../content/applications/general/apps_modules.rst:75 +#: ../../content/applications/general/apps_modules.rst:74 msgid "Uninstalling an app also uninstalls all its dependencies and permanently erases their data." msgstr "" -#: ../../content/applications/general/auth.rst:5 -#: ../../content/applications/general/auth/azure.rst:79 -msgid "Authentication" +#: ../../content/applications/general/companies.rst:5 +msgid "Companies" msgstr "" -#: ../../content/applications/general/auth/2fa.rst:3 -msgid "Two-factor Authentication" +#: ../../content/applications/general/companies.rst:7 +msgid "A centralized management environment allows you to select multiple companies simultaneously and set their specific warehouses, customers, equipment, and contacts. It provides you the ability to generate reports of aggregated figures without switching interfaces, which facilitates daily tasks and the overall management process." msgstr "" -#: ../../content/applications/general/auth/2fa.rst:5 -msgid "Two-factor authentication (\"2FA\") is a good way to improve the security of an account, to make it less likely that an other person will manage to log in instead of you." +#: ../../content/applications/general/companies.rst:15 +msgid "Manage companies and records" msgstr "" -#: ../../content/applications/general/auth/2fa.rst:9 -msgid "Practically, it means storing a secret inside an *authenticator* (usually your cell phone) and exchanging a code from the authenticator when you try to log in." +#: ../../content/applications/general/companies.rst:17 +msgid "Go to :menuselection:`Settings --> Manage Companies` and fill in the form with your company’s information. If a *Parent Company* is selected, records are shared between the two companies (as long as both environments are active)." msgstr "" -#: ../../content/applications/general/auth/2fa.rst:13 -msgid "This means an attacker needs *both* to have guessed (or found) your password and to access (or steal) your authenticator, a more difficult proposition than either one or the other." +#: ../../content/applications/general/companies.rst:-1 +msgid "Overview of a new company's form in Odoo" msgstr "" -#: ../../content/applications/general/auth/2fa.rst:18 -msgid "Requirements" +#: ../../content/applications/general/companies.rst:26 +msgid "Activate the :ref:`developer mode ` to choose a *Favicon* for each of your companies, and easily identify them by the browser tabs. Set your favicons’ files size to 16x16 or 32x32 pixels. JPG, PNG, GIF, and ICO are extensions accepted." msgstr "" -#: ../../content/applications/general/auth/2fa.rst:20 -msgid "These lists are just examples, they are not endorsements of any specific software." +#: ../../content/applications/general/companies.rst:0 +msgid "View of a web browser and the favicon for a specific company chosen in Odoo" msgstr "" -#: ../../content/applications/general/auth/2fa.rst:23 -msgid "If you don't already have one, you will need to choose an authenticator." +#: ../../content/applications/general/companies.rst:35 +msgid "Switch between or select multiple companies by enabling their selection boxes to activate them. The grayed company is the one which environment is in use. To switch environments, click on the company’s name. In the example below, the user has access to three companies, two are activated, and the environment in use is of *JS Store US*." msgstr "" -#: ../../content/applications/general/auth/2fa.rst:26 -msgid "Phone-based authenticators are the easiest and most common so we will assume you'll pick and install one on your phone, examples include `Authy `_, `FreeOTP `_, `Google Authenticator `_, `LastPass Authenticator `_, `Microsoft Authenticator `_, ...; password managers also commonly include :abbr:`2FA (two-factor authentication)` support e.g. `1Password `_, `Bitwarden `_, ..." +#: ../../content/applications/general/companies.rst:-1 +msgid "View of the companies menu through the main dashboard in Odoo" msgstr "" -#: ../../content/applications/general/auth/2fa.rst:39 -msgid "For the sake of demonstration we will be using Google Authenticator (not because it is any good but because it is quite common)." +#: ../../content/applications/general/companies.rst:44 +msgid "Data such as Products, Contacts, and Equipment can be shared or set to be shown for a specific company only. To do so, on their forms, choose between:" msgstr "" -#: ../../content/applications/general/auth/2fa.rst:43 -msgid "Setting up two-factor authentication" +#: ../../content/applications/general/companies.rst:47 +msgid "*A blank field*: the record is shared within all companies." msgstr "" -#: ../../content/applications/general/auth/2fa.rst:45 -msgid "Once you have your authenticator of choice, go to the Odoo instance you want to setup :abbr:`2FA (two-factor authentication)`, then open :guilabel:`Preferences` (or :guilabel:`My Profile`):" +#: ../../content/applications/general/companies.rst:48 +msgid "*Adding a company*: the record is visible to users logged in to that specific company." msgstr "" -#: ../../content/applications/general/auth/2fa.rst:52 -msgid "Open the :guilabel:`Account Security` tab, then click the :guilabel:`Enable two-factor authentication` button:" +#: ../../content/applications/general/companies.rst:-1 +msgid "View of a product's form emphasizing the company field in Odoo Sales" msgstr "" -#: ../../content/applications/general/auth/2fa.rst:58 -msgid "Because this is a security-sensitive action, you will need to input your password:" +#: ../../content/applications/general/companies.rst:55 +msgid "Employees' access" msgstr "" -#: ../../content/applications/general/auth/2fa.rst:64 -msgid "After which you will see this screen with a barcode:" +#: ../../content/applications/general/companies.rst:57 +msgid "Once companies are created, manage your employees' :doc:`Access Rights ` for *Multi Companies*." msgstr "" -#: ../../content/applications/general/auth/2fa.rst:69 -msgid "In most applications, you can simply *scan the barcode* via the authenticator of your choice, the authenticator will then take care of all the setup:" +#: ../../content/applications/general/companies.rst:-1 +msgid "View of an user form emphasizing the multi companies field under the access rights tabs\n" +"in Odoo" msgstr "" -#: ../../content/applications/general/auth/2fa.rst:78 -msgid "If you can not scan the screen (e.g. because you are doing this set-up on the same phone as the authenticator application), you can click the provided link, or copy the secret to manually set-up your authenticator:" +#: ../../content/applications/general/companies.rst:66 +msgid "If a user has multiple companies *activated* on his database, and he is **editing** a record, the editing happens on the record's related company." msgstr "" -#: ../../content/applications/general/auth/2fa.rst:89 -msgid "Once this is done, the authenticator should display a *verification code* with some useful identifying information (e.g. the domain and login for which the code is):" +#: ../../content/applications/general/companies.rst:69 +msgid "Example: if editing a sale order issued under JS Store US while working on the JS Store Belgium environment, the changes are applied under JS Store US (the company from which the sale order was issued)." msgstr "" -#: ../../content/applications/general/auth/2fa.rst:96 -msgid "You can now input the code into the :guilabel:`Verification Code` field, then click the :guilabel:`Enable two-factor authentication` button." +#: ../../content/applications/general/companies.rst:70 +msgid "When **creating** a record, the company taken into account is:" msgstr "" -#: ../../content/applications/general/auth/2fa.rst:100 -msgid "Congratulation, your account is now protected by two-factor authentication!" +#: ../../content/applications/general/companies.rst:72 +msgid "The current company (the one active) or," msgstr "" -#: ../../content/applications/general/auth/2fa.rst:107 -msgid "Logging in" +#: ../../content/applications/general/companies.rst:73 +msgid "No company is set (on products and contacts’ forms for example) or," msgstr "" -#: ../../content/applications/general/auth/2fa.rst:109 -msgid "You should now :guilabel:`Log out` to follow along." +#: ../../content/applications/general/companies.rst:74 +msgid "The company set is the one linked to the document (the same as if a record is being edited)." msgstr "" -#: ../../content/applications/general/auth/2fa.rst:111 -msgid "On the login page, input the username and password of the account for which you set up :abbr:`2FA (two-factor authentication)`, rather than immediately enter Odoo you will now get a second log-in screen:" +#: ../../content/applications/general/companies.rst:77 +msgid "Documents’ format" msgstr "" -#: ../../content/applications/general/auth/2fa.rst:118 -msgid "Get your authenticator, input the code it provides for the domain and account, validate, and you're now in." +#: ../../content/applications/general/companies.rst:79 +msgid "To set documents' formats according to each company, *activate* and *select* the respective one and, under *Settings*, click on *Configure Document Layout*." msgstr "" -#: ../../content/applications/general/auth/2fa.rst:121 -msgid "And that's it. From now on, unless you disable :abbr:`2FA (two-factor authentication)` you will have a two-step log-in process rather than the old one-step process." +#: ../../content/applications/general/companies.rst:-1 +msgid "View of the settings page emphasizing the document layout field in Odoo" msgstr "" -#: ../../content/applications/general/auth/2fa.rst:125 -msgid "Don't lose your authenticator, if you do, you will need an *Odoo Administrator* to disable :abbr:`2FA (two-factor authentication)` on the account." +#: ../../content/applications/general/companies.rst:87 +msgid "Inter-Company Transactions" msgstr "" -#: ../../content/applications/general/auth/azure.rst:3 -msgid "Microsoft Azure sign-in authentication" +#: ../../content/applications/general/companies.rst:89 +msgid "First, make sure each one of your companies is properly set in relation to:" msgstr "" -#: ../../content/applications/general/auth/azure.rst:5 -msgid "The Microsoft Azure OAuth sign-in authentication is a useful function that allows Odoo users to sign in to their database with their Microsoft Azure account." +#: ../../content/applications/general/companies.rst:91 +msgid ":doc:`Chart of Accounts <../finance/accounting/get_started/chart_of_accounts>`" msgstr "" -#: ../../content/applications/general/auth/azure.rst:8 -msgid "This is particularly helpful if the organization uses Azure Workspace, and wants employees within the organization to connect to Odoo using their Microsoft Accounts." +#: ../../content/applications/general/companies.rst:92 +msgid ":doc:`Taxes <../finance/accounting/taxes>`" msgstr "" -#: ../../content/applications/general/auth/azure.rst:12 -msgid "Databases hosted on Odoo.com should not use OAuth login for the owner or administrator of the database as it would unlink the database from their Odoo.com account. If OAuth is set up for that user, the database will no longer be able to be duplicated, renamed, or otherwise managed from the Odoo.com portal." +#: ../../content/applications/general/companies.rst:93 +msgid ":doc:`Fiscal Positions <../finance/accounting/taxes/fiscal_positions>`" msgstr "" -#: ../../content/applications/general/auth/azure.rst:19 -msgid ":doc:`../../productivity/calendar/outlook`" +#: ../../content/applications/general/companies.rst:94 +msgid ":doc:`Journals <../finance/accounting/bank>`" msgstr "" -#: ../../content/applications/general/auth/azure.rst:20 -#: ../../content/applications/general/email_communication/email_servers.rst:69 -msgid ":doc:`/administration/maintain/azure_oauth`" +#: ../../content/applications/general/companies.rst:95 +msgid ":doc:`Fiscal Localizations <../finance/fiscal_localizations>`" msgstr "" -#: ../../content/applications/general/auth/azure.rst:23 -#: ../../content/applications/general/auth/google.rst:24 -#: ../../content/applications/general/voip/axivox/axivox_config.rst:17 -#: ../../content/applications/general/voip/onsip.rst:18 -msgid "Configuration" +#: ../../content/applications/general/companies.rst:96 +msgid ":doc:`Pricelists <../sales/sales/products_prices/prices/pricing>`" msgstr "" -#: ../../content/applications/general/auth/azure.rst:25 -msgid "Integrating the Microsoft sign-in function requires configuration on Microsoft and Odoo." +#: ../../content/applications/general/companies.rst:98 +msgid "Now, activate the *Inter-Company Transactions* option under *Settings*. With the respective company *activated* and *selected*, choose if you would like operations between companies to be synchronized at an invoice/bills level or at a sales/purchase orders level." msgstr "" -#: ../../content/applications/general/auth/azure.rst:28 -msgid "Odoo System Parameter" +#: ../../content/applications/general/companies.rst:-1 +msgid "View of the settings page emphasizing the inter company transaction field in Odoo" msgstr "" -#: ../../content/applications/general/auth/azure.rst:30 -msgid "First activate the :ref:`developer mode `, and then go to :menuselection:`Settings --> Technical --> System Parameters`." +#: ../../content/applications/general/companies.rst:106 +msgid "**Synchronize invoice/bills**: generates a bill/invoice when a company confirms a bill/invoice for the selected company." msgstr "" -#: ../../content/applications/general/auth/azure.rst:33 -msgid "Click :guilabel:`Create` and on the new/blank form that appears, add the following system parameter `auth_oauth.authorization_header` to the :guilabel:`Key` field, and set the :guilabel:`Value` to `1`. Then click :guilabel:`Save` to finish." +#: ../../content/applications/general/companies.rst:109 +msgid "*Example:* an invoice posted on JS Store Belgium, for JS Store US, automatically creates a vendor bill on the JS Store US, from the JS Store Belgium." msgstr "" -#: ../../content/applications/general/auth/azure.rst:38 -msgid "Microsoft Azure dashboard" +#: ../../content/applications/general/companies.rst:-1 +msgid "View of an invoice for JS Store US created on JS Store Belgium in Odoo" msgstr "" -#: ../../content/applications/general/auth/azure.rst:41 -msgid "Create a new application" +#: ../../content/applications/general/companies.rst:116 +msgid "**Synchronize sales/purchase order**: generates a drafted purchase/sales order using the selected company warehouse when a sales/purchase order is confirmed for the selected company. If instead of a drafted purchase/sales order you rather have it validated, enable *Automatic Validation*." msgstr "" -#: ../../content/applications/general/auth/azure.rst:43 -msgid "Now that the system parameters in Odoo have been set up, it's time to create a corresponding application inside of Microsoft Azure. To get started creating the new application, go to `Microsoft's Azure Portal `_. Log in with the :guilabel:`Microsoft Outlook Office 365` account if there is one, otherwise, log in with a personal :guilabel:`Microsoft account`." +#: ../../content/applications/general/companies.rst:120 +msgid "*Example:* when a sale order for JS Store US is confirmed on JS Store Belgium, a purchase order on JS Store Belgium is automatically created (and confirmed if the *Automatic Validation* feature was enabled)." msgstr "" -#: ../../content/applications/general/auth/azure.rst:50 -msgid "A user with administrative access to the *Azure Settings* must connect and perform the following configuration steps below." +#: ../../content/applications/general/companies.rst:-1 +msgid "View of the purchase created on JS Store US from JS Store Belgium in Odoo" msgstr "" -#: ../../content/applications/general/auth/azure.rst:53 -msgid "Next, navigate to the section labeled :guilabel:`Manage Microsoft Entra ID` (formally *Azure Active Directory*). The location of this link is usually in the center of the page." +#: ../../content/applications/general/companies.rst:129 +msgid "Products have to be configured as *Can be sold* and must be shared between the companies." msgstr "" -#: ../../content/applications/general/auth/azure.rst:56 -msgid "Now, click on the :guilabel:`Add (+)` icon, located in the top menu, and then select :guilabel:`App registration` from the drop-down menu. On the :guilabel:`Register an application` screen, rename the :guilabel:`Name` field to `Odoo Login OAuth` or a similarly recognizable title. Under the :guilabel:`Supported account types` section select the option for :guilabel:`Accounts in this organizational directory only (Default Directory only - Single tenant)`." +#: ../../content/applications/general/companies.rst:132 +msgid "Remember to test all workflows as an user other than the administrator." msgstr "" -#: ../../content/applications/general/auth/azure.rst:63 -msgid "The :guilabel:`Supported account types` can vary by Microsoft account type and end use of the OAuth. For example: Is the login meant for internal users within one organization or is it meant for customer portal access? The above configuration is used for internal users in an organization." +#: ../../content/applications/general/companies.rst:135 +msgid ":doc:`Multi-company Guidelines `" msgstr "" -#: ../../content/applications/general/auth/azure.rst:68 -msgid "Choose :guilabel:`Personal Microsoft accounts only` if the target audience is meant for portal users. Choose :guilabel:`Accounts in this organizational directory only (Default Directory only - Single tenant)` if the target audience is company users." +#: ../../content/applications/general/companies.rst:136 +msgid ":doc:`../finance/accounting/get_started/multi_currency`" msgstr "" -#: ../../content/applications/general/auth/azure.rst:72 -msgid "Under the :guilabel:`Redirect URL` section, select :guilabel:`Web` as the platform, and then input `https:///auth_oauth/signin` in the :guilabel:`URL` field. The Odoo base :abbr:`URL (Uniform Resource Locator)` is the canonical domain at which your Odoo instance can be reached (e.g. *mydatabase.odoo.com* if you are hosted on Odoo.com) in the :guilabel:`URL` field. Then, click :guilabel:`Register`, and the application is created." +#: ../../content/applications/general/companies/digest_emails.rst:3 +msgid "Digest Emails" msgstr "" -#: ../../content/applications/general/auth/azure.rst:81 -msgid "Edit the new app's authentication by clicking on the :guilabel:`Authentication` menu item in the left menu after being redirected to the application's settings from the previous step." +#: ../../content/applications/general/companies/digest_emails.rst:5 +msgid "**Digest Emails** are periodic snapshots sent to your organization via email that include high-level information about how your business is performing." msgstr "" -#: ../../content/applications/general/auth/azure.rst:84 -msgid "Next, the type of *tokens* needed for the OAuth authentication will be chosen. These are not currency tokens but rather authentication tokens that are passed between Microsoft and Odoo. Therefore, there is no cost for these tokens; they are used merely for authentication purposes between two :abbr:`APIs (application programming interfaces)`. Select the tokens that should be issued by the authorization endpoint by scrolling down the screen and check the boxes labeled: :guilabel:`Access tokens (used for implicit flows)` and :guilabel:`ID tokens (used for implicit and hybrid flows)`." +#: ../../content/applications/general/companies/digest_emails.rst:8 +msgid "Navigate to Digest Emails by going to :menuselection:`Settings --> General Settings --> Statistics`, then activate the **Digest Emails** feature and click on save." msgstr "" -#: ../../content/applications/general/auth/azure.rst:-1 -msgid "Authentication settings and endpoint tokens." +#: ../../content/applications/general/companies/digest_emails.rst:-1 +msgid "Digest Emails section inside General Settings." msgstr "" -#: ../../content/applications/general/auth/azure.rst:96 -msgid "Click :guilabel:`Save` to ensure these settings are saved." +#: ../../content/applications/general/companies/digest_emails.rst:15 +msgid "You can control a variety of settings for your Digest Emails, such as:" msgstr "" -#: ../../content/applications/general/auth/azure.rst:99 -msgid "Gather credentials" +#: ../../content/applications/general/companies/digest_emails.rst:17 +msgid "which KPIs are shared in the Digest" msgstr "" -#: ../../content/applications/general/auth/azure.rst:101 -msgid "With the application created and authenticated in the Microsoft Azure console, credentials will be gathered next. To do so, click on the :guilabel:`Overview` menu item in the left-hand column. Select and copy the :guilabel:`Application (client) ID` in the window that appears. Paste this credential to a clipboard / notepad, as this credential will be used in the Odoo configuration later." +#: ../../content/applications/general/companies/digest_emails.rst:18 +msgid "how often Digest Emails are sent" msgstr "" -#: ../../content/applications/general/auth/azure.rst:106 -msgid "After finishing this step, click on :guilabel:`Endpoints` on the top menu and click the *copy icon* next to :guilabel:`OAuth 2.0 authorization endpoint (v2)` field. Paste this value in the clipboard / notepad." +#: ../../content/applications/general/companies/digest_emails.rst:19 +msgid "who in your organization receives Digest Emails" msgstr "" -#: ../../content/applications/general/auth/azure.rst:-1 -msgid "Application ID and OAuth 2.0 authorization endpoint (v2) credentials." +#: ../../content/applications/general/companies/digest_emails.rst:20 +msgid "creating custom Digest Email templates" msgstr "" -#: ../../content/applications/general/auth/azure.rst:115 -msgid "Odoo setup" +#: ../../content/applications/general/companies/digest_emails.rst:21 +msgid "adding additional KPIs (Studio required)" msgstr "" -#: ../../content/applications/general/auth/azure.rst:117 -msgid "Finally, the last step in the Microsoft Azure OAuth configuration is to configure some settings in Odoo. Navigate to :menuselection:`Settings --> Integrations --> OAuth Authentication` and check the box to activate the OAuth login feature. Click :guilabel:`Save` to ensure the progress is saved. Then, sign in to the database once the login screen loads." +#: ../../content/applications/general/companies/digest_emails.rst:24 +msgid "By default, Digest Email is *enabled*, and *Your Odoo Periodic Digest* serves as the primary template, which includes all KPI measurements across your Odoo database and is sent daily to administrators." msgstr "" -#: ../../content/applications/general/auth/azure.rst:122 -msgid "Once again, navigate to :menuselection:`Settings --> Integrations --> OAuth Authentication` and click on :guilabel:`OAuth Providers`. Now, select :guilabel:`New` in the upper-left corner and name the provider `Azure`." +#: ../../content/applications/general/companies/digest_emails.rst:31 +msgid "Customize *Your Odoo Periodic Digest*" msgstr "" -#: ../../content/applications/general/auth/azure.rst:126 -msgid "Paste the :guilabel:`Application (client) ID` from the previous section into the :guilabel:`Client ID` field. After completing this, paste the new :guilabel:`OAuth 2.0 authorization endpoint (v2)` value into the :guilabel:`Authorization URL` field." +#: ../../content/applications/general/companies/digest_emails.rst:33 +msgid "To customize the default Digest Email (*Your Odoo Periodic Digest*), go to :menuselection:`Settings --> General Settings --> Statistics --> Digest Email`, select *Your Odoo Periodic Digest* and click on the *external link* next to the dropdown selection." msgstr "" -#: ../../content/applications/general/auth/azure.rst:130 -msgid "For the :guilabel:`UserInfo URL` field, paste the following :abbr:`URL (Uniform Resource Locator)`: `https://graph.microsoft.com/oidc/userinfo`" +#: ../../content/applications/general/companies/digest_emails.rst:37 +msgid "A popup window appears and presents a variety of editable settings, which include:" msgstr "" -#: ../../content/applications/general/auth/azure.rst:133 -msgid "In the :guilabel:`Scope` field, paste the following value: `openid profile email`. Next, the Windows logo can be used as the CSS class on the login screen by entering the following value: `fa fa-fw fa-windows`, in the :guilabel:`CSS class` field." +#: ../../content/applications/general/companies/digest_emails.rst:39 +msgid "**Digest Title** - what you want your Digest Email to be called" msgstr "" -#: ../../content/applications/general/auth/azure.rst:137 -msgid "Check the box next to the :guilabel:`Allowed` field to enable the OAuth provider. Finally, add `Microsoft Azure` to the :guilabel:`Login button label` field. This text will appear next to the Windows logo on the login page." +#: ../../content/applications/general/companies/digest_emails.rst:40 +msgid "**Periodicity** - control the regimen in how often Digest Emails are sent" msgstr "" -#: ../../content/applications/general/auth/azure.rst:-1 -msgid "Odoo provider setup in the Settings application." +#: ../../content/applications/general/companies/digest_emails.rst:41 +msgid "**KPIs** - check/uncheck each calculated KPI that appears in Digest Emails" msgstr "" -#: ../../content/applications/general/auth/azure.rst:145 -msgid ":guilabel:`Save` the changes to complete the OAuth authentication setup in Odoo." +#: ../../content/applications/general/companies/digest_emails.rst:42 +msgid "**Recipients** - add/remove users who receive your Digest Emails" msgstr "" -#: ../../content/applications/general/auth/azure.rst:148 -msgid "User experience flows" +#: ../../content/applications/general/companies/digest_emails.rst:43 +msgid "**Custom** - add your own KPIs (Studio required)" msgstr "" -#: ../../content/applications/general/auth/azure.rst:150 -msgid "For a user to log in to Odoo using Microsoft Azure, the user must be on the :menuselection:`Odoo password reset page`. This is the only way that Odoo is able to link the Microsoft Azure account and allow the user to log in." +#: ../../content/applications/general/companies/digest_emails.rst:-1 +msgid "Customize default Digest Email settings and custom KPIs." msgstr "" -#: ../../content/applications/general/auth/azure.rst:155 -msgid "Existing users must :ref:`reset their password ` to access the :menuselection:`Odoo password reset page`. New Odoo users must click the new user invitation link that was sent via email, then click on :guilabel:`Microsoft Azure`. Users should not set a new password." +#: ../../content/applications/general/companies/digest_emails.rst:52 +msgid "Custom digest emails" msgstr "" -#: ../../content/applications/general/auth/azure.rst:160 -msgid "To sign in to Odoo for the first time using the Microsoft Azure OAuth provider, navigate to the :menuselection:`Odoo password reset page` (using the new user invitation link). A password reset page should appear. Then, click on the option labeled :guilabel:`Microsoft Azure`. The page will redirect to the Microsoft login page." +#: ../../content/applications/general/companies/digest_emails.rst:54 +msgid "To do so, click on **Configure Digest Emails** and then **Create**." msgstr "" -#: ../../content/applications/general/auth/azure.rst:-1 -msgid "Microsoft Outlook login page." +#: ../../content/applications/general/companies/digest_emails.rst:56 +msgid "From there, give your Digest Email a title, specify periodicity, and choose your desired KPIs and recipients fields as needed." msgstr "" -#: ../../content/applications/general/auth/azure.rst:169 -msgid "Enter the :guilabel:`Microsoft Email Address` and click :guilabel:`Next`. Follow the process to sign in to the account. Should :abbr:`2FA (Two Factor Authentication)` be turned on, then an extra step may be required." +#: ../../content/applications/general/companies/digest_emails.rst:59 +msgid "After you click **Save**, your new custom Digest Email is available as a selection in the **General Settings** dropdown menu." msgstr "" -#: ../../content/applications/general/auth/azure.rst:-1 -msgid "Enter Microsoft login credentials." +#: ../../content/applications/general/companies/digest_emails.rst:65 +msgid "Custom KPIs with Studio" msgstr "" -#: ../../content/applications/general/auth/azure.rst:177 -msgid "Finally, after logging in to the account, the page will redirect to a permissions page where the user will be prompted to :guilabel:`Accept` the conditions that the Odoo application will access their Microsoft information." +#: ../../content/applications/general/companies/digest_emails.rst:67 +msgid "For either *Your Odoo Periodic Digest* or your own custom Digest Email, you can add your own KPIs by using Odoo Studio." msgstr "" -#: ../../content/applications/general/auth/azure.rst:-1 -msgid "Accept Microsoft conditions for permission access to your account information." +#: ../../content/applications/general/companies/digest_emails.rst:70 +msgid "To begin, click the **Toggle Studio** icon or click the **Recipients** tab and then the ellipses :menuselection:`… icon --> Add Custom Field` to edit the template or add additional fields." msgstr "" -#: ../../content/applications/general/auth/google.rst:3 -msgid "Google Sign-In Authentication" +#: ../../content/applications/general/companies/digest_emails.rst:73 +msgid "In order to create additional fields, you must create two fields on the digest object:" msgstr "" -#: ../../content/applications/general/auth/google.rst:5 -msgid "The *Google Sign-In Authentication* is a useful function that allows Odoo users to sign in to their database with their Google account." +#: ../../content/applications/general/companies/digest_emails.rst:75 +msgid "create a boolean field called `kpi_myfield` and display it in the KPIs tab" msgstr "" -#: ../../content/applications/general/auth/google.rst:8 -msgid "This is particularly helpful if the organization uses Google Workspace, and wants employees within the organization to connect to Odoo using their Google Accounts." +#: ../../content/applications/general/companies/digest_emails.rst:76 +msgid "create a computed field called `kpi_myfield_value` that computes your customized KPI" msgstr "" -#: ../../content/applications/general/auth/google.rst:12 -msgid "Databases hosted on Odoo.com should not use Oauth login for the owner or administrator of the database as it would unlink the database from their Odoo.com account. If Oauth is set up for that user, the database will no longer be able to be duplicated, renamed or otherwise managed from the Odoo.com portal." +#: ../../content/applications/general/companies/digest_emails.rst:77 +msgid "select your KPI(s) in the KPIs tab." msgstr "" -#: ../../content/applications/general/auth/google.rst:18 -msgid ":doc:`/applications/productivity/calendar/google`" +#: ../../content/applications/general/companies/digest_emails.rst:80 +msgid "Computed values reference table" msgstr "" -#: ../../content/applications/general/auth/google.rst:19 -#: ../../content/applications/general/email_communication/email_servers.rst:68 -msgid ":doc:`/administration/maintain/google_oauth`" +#: ../../content/applications/general/companies/digest_emails.rst:83 +msgid "LABEL" msgstr "" -#: ../../content/applications/general/auth/google.rst:26 -msgid "The integration of the Google sign-in function requires configuration both on Google *and* Odoo." +#: ../../content/applications/general/companies/digest_emails.rst:83 +msgid "VALUE" msgstr "" -#: ../../content/applications/general/auth/google.rst:31 -msgid "Google API Dashboard" +#: ../../content/applications/general/companies/digest_emails.rst:85 +msgid "Connected Users" msgstr "" -#: ../../content/applications/general/auth/google.rst:33 -msgid "Go to the `Google API Dashboard `_." +#: ../../content/applications/general/companies/digest_emails.rst:85 +msgid "`kpi_res_users_connected_value`" msgstr "" -#: ../../content/applications/general/auth/google.rst:34 -msgid "Make sure the right project is opened. If there isn't a project yet, click on :guilabel:`Create Project`, fill out the project name and other details of the company, and click on :guilabel:`Create`." +#: ../../content/applications/general/companies/digest_emails.rst:87 +msgid "Messages Sent" msgstr "" -#: ../../content/applications/general/auth/google.rst:0 -msgid "Filling out the details of a new project." +#: ../../content/applications/general/companies/digest_emails.rst:87 +msgid "`kpi_mail_message_total_value`" msgstr "" -#: ../../content/applications/general/auth/google.rst:43 -msgid "Choose the name of the company from the drop-down menu." +#: ../../content/applications/general/companies/digest_emails.rst:89 +msgid "New Leads" msgstr "" -#: ../../content/applications/general/auth/google.rst:48 -msgid "OAuth consent screen" +#: ../../content/applications/general/companies/digest_emails.rst:89 +msgid "`kpi_crm_lead_created_value`" msgstr "" -#: ../../content/applications/general/auth/google.rst:50 -msgid "On the left side menu, click on :menuselection:`OAuth consent screen`." +#: ../../content/applications/general/companies/digest_emails.rst:91 +msgid "Opportunities Won" msgstr "" -#: ../../content/applications/general/auth/google.rst:0 -msgid "Google OAuth consent selection menu." +#: ../../content/applications/general/companies/digest_emails.rst:91 +msgid "`kpi_crm_opportunities_won_value`" msgstr "" -#: ../../content/applications/general/auth/google.rst:56 -msgid "Choose one of the options (:guilabel:`Internal` / :guilabel:`External`), and click on :guilabel:`Create`." +#: ../../content/applications/general/companies/digest_emails.rst:93 +msgid "Open Tasks" msgstr "" -#: ../../content/applications/general/auth/google.rst:0 -msgid "Choice of a user type in OAuth consent." +#: ../../content/applications/general/companies/digest_emails.rst:93 +msgid "`kpi_project_task_opened_value`" msgstr "" -#: ../../content/applications/general/auth/google.rst:64 -msgid "*Personal* Gmail Accounts are only allowed to be **External** User Type, which means Google may require an approval, or for *Scopes* to be added on. However, using a *Google WorkSpace* account allows for **Internal** User Type to be used." +#: ../../content/applications/general/companies/digest_emails.rst:95 +msgid "Tickets Closed" msgstr "" -#: ../../content/applications/general/auth/google.rst:68 -msgid "Note, as well, that while the API connection is in the *External* testing mode, then no approval is necessary from Google. User limits in this testing mode is set to 100 users." +#: ../../content/applications/general/companies/digest_emails.rst:95 +msgid "`kpi_helpdesk_tickets_closed_value`" msgstr "" -#: ../../content/applications/general/auth/google.rst:71 -msgid "Fill out the required details and domain info, then click on :guilabel:`Save and Continue`." +#: ../../content/applications/general/companies/digest_emails.rst:97 +msgid "% of Happiness" msgstr "" -#: ../../content/applications/general/auth/google.rst:72 -msgid "On the :menuselection:`Scopes` page, leave all fields as is, and click on :guilabel:`Save and Continue`." +#: ../../content/applications/general/companies/digest_emails.rst:97 +msgid "`kpi_livechat_rating_value`" msgstr "" -#: ../../content/applications/general/auth/google.rst:74 -msgid "Next, if continuing in testing mode (*External*), add the email addresses being configured under the :guilabel:`Test users` step by clicking on :guilabel:`Add Users`, and then the :guilabel:`Save and Continue` button. A summary of the app registration appears." +#: ../../content/applications/general/companies/digest_emails.rst:99 +msgid "Conversations handled" msgstr "" -#: ../../content/applications/general/auth/google.rst:77 -msgid "Finally, scroll to the bottom, and click on :guilabel:`Back to Dashboard`." +#: ../../content/applications/general/companies/digest_emails.rst:99 +msgid "`kpi_livechat_conversations_value`" msgstr "" -#: ../../content/applications/general/auth/google.rst:82 -msgid "Credentials" +#: ../../content/applications/general/companies/digest_emails.rst:101 +msgid "Time to answer (sec)" msgstr "" -#: ../../content/applications/general/auth/google.rst:84 -msgid "On the left side menu, click on :menuselection:`Credentials`." +#: ../../content/applications/general/companies/digest_emails.rst:101 +msgid "`kpi_livechat_response_value`" msgstr "" -#: ../../content/applications/general/auth/google.rst:0 -msgid "Credentials button menu." +#: ../../content/applications/general/companies/digest_emails.rst:103 +msgid "All Sales" msgstr "" -#: ../../content/applications/general/auth/google.rst:90 -msgid "Click on :guilabel:`Create Credentials`, and select :guilabel:`OAuth client ID`." +#: ../../content/applications/general/companies/digest_emails.rst:103 +msgid "`kpi_all_sale_total_value`" msgstr "" -#: ../../content/applications/general/auth/google.rst:0 -msgid "OAuth client id selection." +#: ../../content/applications/general/companies/digest_emails.rst:105 +msgid "eCommerce Sales" msgstr "" -#: ../../content/applications/general/auth/google.rst:96 -msgid "Select :guilabel:`Web Application` as the :guilabel:`Application Type`. Now, configure the allowed pages on which Odoo will be redirected." +#: ../../content/applications/general/companies/digest_emails.rst:105 +msgid "`kpi_website_sale_total_value`" msgstr "" -#: ../../content/applications/general/auth/google.rst:99 -msgid "In order to achieve this, in the :guilabel:`Authorized redirect URIs` field, enter the database's domain immediately followed by `/auth_oauth/signin`. For example: `https://mydomain.odoo.com/auth_oauth/signin`, then click on :guilabel:`Create`." +#: ../../content/applications/general/companies/digest_emails.rst:107 +msgid "Revenue" msgstr "" -#: ../../content/applications/general/auth/google.rst:103 -msgid "Now that the *OAuth client* has been created, a screen will appear with the :guilabel:`Client ID` and :guilabel:`Client Secret`. Copy the :guilabel:`Client ID` for later, as it will be necessary for the configuration in Odoo, which will be covered in the following steps." +#: ../../content/applications/general/companies/digest_emails.rst:107 +msgid "`kpi_account_total_revenue_value`" msgstr "" -#: ../../content/applications/general/auth/google.rst:110 -msgid "Google Authentication on Odoo" +#: ../../content/applications/general/companies/digest_emails.rst:109 +msgid "Bank & Cash Moves" msgstr "" -#: ../../content/applications/general/auth/google.rst:115 -msgid "Retrieve the Client ID" +#: ../../content/applications/general/companies/digest_emails.rst:109 +msgid "`kpi_account_bank_cash_value`" msgstr "" -#: ../../content/applications/general/auth/google.rst:117 -msgid "Once the previous steps are complete, two keys are generated on the Google API Dashboard: :guilabel:`Client ID` and :guilabel:`Client Secret`. Copy the :guilabel:`Client ID`." +#: ../../content/applications/general/companies/digest_emails.rst:111 +msgid "POS Sales" msgstr "" -#: ../../content/applications/general/auth/google.rst:-1 -msgid "Google OAuth Client ID generated." +#: ../../content/applications/general/companies/digest_emails.rst:111 +msgid "`kpi_pos_total_value`" msgstr "" -#: ../../content/applications/general/auth/google.rst:127 -msgid "Odoo activation" +#: ../../content/applications/general/companies/digest_emails.rst:113 +msgid "New Employees" msgstr "" -#: ../../content/applications/general/auth/google.rst:129 -msgid "Go to :menuselection:`Odoo General Settings --> Integrations` and activate :guilabel:`OAuth Authentication`." +#: ../../content/applications/general/companies/digest_emails.rst:113 +msgid "`kpi_hr_recruitment_new_colleagues_value`" msgstr "" -#: ../../content/applications/general/auth/google.rst:133 -msgid "Odoo may prompt the user to log-in again after this step." +#: ../../content/applications/general/companies/email_template.rst:3 +msgid "Email templates" msgstr "" -#: ../../content/applications/general/auth/google.rst:135 -msgid "Go back to :menuselection:`General Settings --> Integrations --> OAuth Authentication`, activate the selection and :guilabel:`Save`. Next, return to :menuselection:`General Settings --> Integrations --> Google Authentication` and activate the selection. Then fill out the :guilabel:`Client ID` with the key from the Google API Dashboard, and :guilabel:`Save`." +#: ../../content/applications/general/companies/email_template.rst:5 +msgid "Email templates are saved emails that are used repeatedly to send emails from the database. They allow users to send quality communications, without having to compose the same text repeatedly." msgstr "" -#: ../../content/applications/general/auth/google.rst:0 -msgid "Filling out the client id in Odoo settings." +#: ../../content/applications/general/companies/email_template.rst:8 +msgid "Creating different templates that are tailored to specific situations lets users choose the right message for the right audience. This increases the quality of the message and the overall engagement rate with the customer." msgstr "" -#: ../../content/applications/general/auth/google.rst:145 -msgid "Google OAuth2 configuration can also be accessed by clicking on :guilabel:`OAuth Providers` under the :guilabel:`OAuth Authentication` heading in :menuselection:`Integrations`." +#: ../../content/applications/general/companies/email_template.rst:13 +msgid "Email templates in Odoo use QWeb or XML, which allows for editing emails in their final rendering, making customizations more robust, without having to edit any code whatsoever. This means that Odoo can use a Graphical User Interface (GUI) to edit emails, which edits the backend code. When the received email is read by the end user's program, different formatting and graphics will appear in the final form of it." msgstr "" -#: ../../content/applications/general/auth/google.rst:151 -msgid "Log in to Odoo with Google" +#: ../../content/applications/general/companies/email_template.rst:19 +msgid "Access email templates in :ref:`developer mode ` by navigating to :menuselection:`Settings app --> Technical menu --> Email --> Email Templates`." msgstr "" -#: ../../content/applications/general/auth/google.rst:153 -msgid "To link the Google account to the Odoo profile, click on :guilabel:`Log in with Google` when first logging into Odoo." +#: ../../content/applications/general/companies/email_template.rst:23 +msgid "Editing email templates" msgstr "" -#: ../../content/applications/general/auth/google.rst:0 -msgid "Reset password screen with \"Log in with Google\" button." +#: ../../content/applications/general/companies/email_template.rst:25 +msgid "The *powerbox* feature can be used when working with email templates. This feature provides the ability to directly edit the formatting and text in an email template, as well as the ability to add links, buttons, appointment options, or images." msgstr "" -#: ../../content/applications/general/auth/google.rst:161 -msgid "Existing users must :ref:`reset their password ` to access the :menuselection:`Reset Password` page, while new users can directly click on :guilabel:`Log in with Google`, instead of choosing a new password." +#: ../../content/applications/general/companies/email_template.rst:29 +msgid "Additionally, the XML/HTML code of the email template can be edited directly, via the :guilabel:`` icon. Dynamic placeholders (referencing fields within Odoo) are also available for use in the email template." msgstr "" -#: ../../content/applications/general/auth/google.rst:166 -msgid "`Google Cloud Platform Console Help - Setting up OAuth 2.0 `_" +#: ../../content/applications/general/companies/email_template.rst:34 +msgid "Powerbox" msgstr "" -#: ../../content/applications/general/auth/ldap.rst:3 -msgid "Sign in with LDAP" +#: ../../content/applications/general/companies/email_template.rst:36 +msgid "The *powerbox* feature is an enriched text editor with various formatting, layout, and text options. It can also be used to add XML/HTML features in an email template. The powerbox feature is activated by typing a forward slash `/` in the body of the email template." msgstr "" -#: ../../content/applications/general/auth/ldap.rst:5 -msgid "Install the Lightweight Directory Access Protocol (LDAP) module in General Settings." +#: ../../content/applications/general/companies/email_template.rst:40 +msgid "When a forward slash `/` is typed in the body of an email template, a drop-down menu appears with the following options:" msgstr "" -#: ../../content/applications/general/auth/ldap.rst:7 -msgid "Click on **Create** in Setup the :abbr:`LDAP (Lightweight Directory Access Protocol)` Server." +#: ../../content/applications/general/companies/email_template.rst:43 +msgid ":guilabel:`Structure`" msgstr "" -#: ../../content/applications/general/auth/ldap.rst:-1 -msgid "LDAP Authentication checkbox highlighted in the integrations settings on Odoo." +#: ../../content/applications/general/companies/email_template.rst:45 +msgid ":guilabel:`Bulleted list`: Create a simple bulleted list." msgstr "" -#: ../../content/applications/general/auth/ldap.rst:-1 -msgid "Create highlighted in the LDAP server settings." +#: ../../content/applications/general/companies/email_template.rst:46 +msgid ":guilabel:`Numbered list`: Create a list with numbering." msgstr "" -#: ../../content/applications/general/auth/ldap.rst:17 -msgid "Choose the company using the LDAP." +#: ../../content/applications/general/companies/email_template.rst:47 +msgid ":guilabel:`Checklist`: Track tasks with a checklist." msgstr "" -#: ../../content/applications/general/auth/ldap.rst:-1 -msgid "Select the company drop-down menu highlighted in LDAP setup." +#: ../../content/applications/general/companies/email_template.rst:48 +msgid ":guilabel:`Table`: Insert a table." msgstr "" -#: ../../content/applications/general/auth/ldap.rst:23 -msgid "In **Server Information**, enter the IP address of the server and the port it listens to." +#: ../../content/applications/general/companies/email_template.rst:49 +msgid ":guilabel:`Separator`: Insert a horizontal rule separator." msgstr "" -#: ../../content/applications/general/auth/ldap.rst:25 -msgid "Tick **Use TLS** if the server is compatible." +#: ../../content/applications/general/companies/email_template.rst:50 +msgid ":guilabel:`Quote`: Add a blockquote section." msgstr "" -#: ../../content/applications/general/auth/ldap.rst:-1 -msgid "LDAP server settings highlighted in LDAP server setup on Odoo." +#: ../../content/applications/general/companies/email_template.rst:51 +msgid ":guilabel:`Code`: Add a code section." msgstr "" -#: ../../content/applications/general/auth/ldap.rst:31 -msgid "In **Login Information**, enter ID and password of the account used to query the server. If left empty, the server queries anonymously." +#: ../../content/applications/general/companies/email_template.rst:52 +msgid ":guilabel:`2 columns`: Convert into two columns." msgstr "" -#: ../../content/applications/general/auth/ldap.rst:-1 -msgid "Login information highlighted in LDAP server setup on Odoo." +#: ../../content/applications/general/companies/email_template.rst:53 +msgid ":guilabel:`3 columns`: Convert into three columns." msgstr "" -#: ../../content/applications/general/auth/ldap.rst:38 -msgid "In **Process Parameter**, enter the domain name of the LDAP server in :abbr:`LDAP (Lightweight Directory Access Protocol)` nomenclature (e.g. ``dc=example,dc=com``)." +#: ../../content/applications/general/companies/email_template.rst:54 +msgid ":guilabel:`4 columns`: Convert into four columns." msgstr "" -#: ../../content/applications/general/auth/ldap.rst:41 -msgid "In **LDAP filter**, enter ``uid=%s``" +#: ../../content/applications/general/companies/email_template.rst:56 +msgid ":guilabel:`Format`" msgstr "" -#: ../../content/applications/general/auth/ldap.rst:-1 -msgid "Process parameter highlighted in LDAP server setup on Odoo." +#: ../../content/applications/general/companies/email_template.rst:58 +msgid ":guilabel:`Heading 1`: Big section heading." msgstr "" -#: ../../content/applications/general/auth/ldap.rst:47 -msgid "In **User Information**, tick *Create User* if Odoo should create a User profile the first time someone logs in with :abbr:`LDAP (Lightweight Directory Access Protocol)`." +#: ../../content/applications/general/companies/email_template.rst:59 +msgid ":guilabel:`Heading 2`: Medium section heading." msgstr "" -#: ../../content/applications/general/auth/ldap.rst:50 -msgid "In **Template User**, indicate a template for the new profiles created. If left blanked, the admin profile will be used as template." +#: ../../content/applications/general/companies/email_template.rst:60 +msgid ":guilabel:`Heading 3`: Small section heading." msgstr "" -#: ../../content/applications/general/auth/ldap.rst:-1 -msgid "User information highlighted on LDAP server setup on Odoo." +#: ../../content/applications/general/companies/email_template.rst:61 +msgid ":guilabel:`Switch direction`: Switch the text's direction." +msgstr "" + +#: ../../content/applications/general/companies/email_template.rst:62 +msgid ":guilabel:`Text`: Paragraph block." +msgstr "" + +#: ../../content/applications/general/companies/email_template.rst:64 +msgid ":guilabel:`Media`" +msgstr "" + +#: ../../content/applications/general/companies/email_template.rst:66 +msgid ":guilabel:`Image`: Insert an image." +msgstr "" + +#: ../../content/applications/general/companies/email_template.rst:67 +msgid ":guilabel:`Article`: Link an article." +msgstr "" + +#: ../../content/applications/general/companies/email_template.rst:69 +msgid ":guilabel:`Navigation`" +msgstr "" + +#: ../../content/applications/general/companies/email_template.rst:71 +msgid ":guilabel:`Link`: Add a link." +msgstr "" + +#: ../../content/applications/general/companies/email_template.rst:72 +msgid ":guilabel:`Button`: Add a button." +msgstr "" + +#: ../../content/applications/general/companies/email_template.rst:73 +msgid ":guilabel:`Appointment`: Add a specific appointment." +msgstr "" + +#: ../../content/applications/general/companies/email_template.rst:74 +msgid ":guilabel:`Calendar`: Schedule an appointment." +msgstr "" + +#: ../../content/applications/general/companies/email_template.rst:76 +msgid ":guilabel:`Widgets`" +msgstr "" + +#: ../../content/applications/general/companies/email_template.rst:78 +msgid ":guilabel:`3 Stars`: Insert a rating over three stars." +msgstr "" + +#: ../../content/applications/general/companies/email_template.rst:79 +msgid ":guilabel:`5 Stars`: Insert a rating over five stars." +msgstr "" + +#: ../../content/applications/general/companies/email_template.rst:81 +msgid ":guilabel:`Basic Blocks`" +msgstr "" + +#: ../../content/applications/general/companies/email_template.rst:83 +msgid ":guilabel:`Signature`: Insert your signature." +msgstr "" + +#: ../../content/applications/general/companies/email_template.rst:85 +msgid ":guilabel:`Marketing Tools`" +msgstr "" + +#: ../../content/applications/general/companies/email_template.rst:87 +msgid ":guilabel:`Dynamic Placeholders`: Insert personalized content." +msgstr "" + +#: ../../content/applications/general/companies/email_template.rst:90 +msgid "To use any of these options, click on the desired feature from the powerbox drop-down menu. To format existing text with a text-related option (e.g. :guilabel:`Heading 1`, :guilabel:`Switch direction`, etc.), highlight the text, then type in the activator key (forward slash) `/`, and select the desired option from the drop-down menu." +msgstr "" + +#: ../../content/applications/general/companies/email_template.rst:0 +msgid "Powerbox feature in the email template." +msgstr "" + +#: ../../content/applications/general/companies/email_template.rst:100 +msgid ":ref:`Using dynamic placeholders `" +msgstr "" + +#: ../../content/applications/general/companies/email_template.rst:103 +msgid "XML/HTML code editor" +msgstr "" + +#: ../../content/applications/general/companies/email_template.rst:105 +msgid "To access the XML/HTML editor for an email template, first enter :ref:`developer mode `. Then, click the :guilabel:`` icon in the upper-right corner of the template, and proceed to edit the XML/HTML. To return to the standard text editor, click the :guilabel:`` icon again." +msgstr "" + +#: ../../content/applications/general/companies/email_template.rst:-1 +msgid "HTML editor in the email template." +msgstr "" + +#: ../../content/applications/general/companies/email_template.rst:115 +msgid "The XML/HTML editor should be accessed with caution as this is the backend code of the template. Editing the code can cause the email template to break immediately or when upgrading the database." +msgstr "" + +#: ../../content/applications/general/companies/email_template.rst:122 +msgid "Dynamic placeholders" +msgstr "" + +#: ../../content/applications/general/companies/email_template.rst:124 +msgid "*Dynamic placeholders* reference certain fields within the Odoo database to produce unique data in the email template." +msgstr "" + +#: ../../content/applications/general/companies/email_template.rst:128 +msgid "Many companies like to customize their emails with a personalized piece of customer information to grab attention. This can be accomplished in Odoo by referencing a field within a model by inserting a dynamic placeholder. For example, a customer's name can be referenced in the email from the :guilabel:`Customer` field on the :guilabel:`Sales Order` model. The dynamic placeholder for this field is: `{{ object.partner_id }}`." +msgstr "" + +#: ../../content/applications/general/companies/email_template.rst:134 +msgid "Dynamic placeholders are encoded to display fields from within the database. Dynamic placeholders can be used in the :guilabel:`Body` (:guilabel:`Content` Tab) of the email template. They can also be used in the fields present in the :guilabel:`Email Configuration` tab, the :guilabel:`Subject` of the email, and the :guilabel:`Language`." +msgstr "" + +#: ../../content/applications/general/companies/email_template.rst:139 +msgid "To use the dynamic placeholders in the :guilabel:`Body` of an email open the **powerbox** feature by typing in `/` into the body of the email template under the :guilabel:`Content` tab. Scroll to the bottom of the options list, to :guilabel:`Marketing Tools`. Next, select :guilabel:`Dynamic Placeholder`. Then select the dynamic placeholder from a list of available options and follow the prompts to configure it with the desired corresponding Odoo field. Each dynamic placeholder will vary in configuration." +msgstr "" + +#: ../../content/applications/general/companies/email_template.rst:-1 +msgid "Using dynamic placeholders in an email template." +msgstr "" + +#: ../../content/applications/general/companies/email_template.rst:151 +msgid "Each unique combination of :guilabel:`Fields`, :guilabel:`Sub-models` and :guilabel:`Sub-fields` creates a different dynamic placeholder. Imagine it as a combination to the field that is being created." +msgstr "" + +#: ../../content/applications/general/companies/email_template.rst:155 +msgid "To search the available fields, simply type in the front-end name (on user-interface) of the field in the search. This will find a result from all of the available fields for the model that the email template is created for." +msgstr "" + +#: ../../content/applications/general/companies/email_template.rst:160 +msgid "Customizing email templates are out of the scope of Odoo Support." +msgstr "" + +#: ../../content/applications/general/companies/email_template.rst:163 +msgid "Rich text editor" +msgstr "" + +#: ../../content/applications/general/companies/email_template.rst:165 +msgid "A rich text editor toolbar can be accessed by highlighting text in the email template. This can be used to change the heading, font size/style, color, add a list type, or a link." +msgstr "" + +#: ../../content/applications/general/companies/email_template.rst:-1 +msgid "Rich text editor in the email template." +msgstr "" + +#: ../../content/applications/general/companies/email_template.rst:173 +msgid "Resetting email templates" +msgstr "" + +#: ../../content/applications/general/companies/email_template.rst:175 +msgid "Should the email template not work because the code has been altered it can be reset to restore it back to the out-of-box default template. Simply click on the :guilabel:`Reset Template` button in the upper left-hand of the screen and the template will be reset." +msgstr "" + +#: ../../content/applications/general/companies/email_template.rst:-1 +msgid "Resetting the email template." +msgstr "" + +#: ../../content/applications/general/companies/email_template.rst:184 +msgid "Default reply on email templates" +msgstr "" + +#: ../../content/applications/general/companies/email_template.rst:186 +msgid "Under the :guilabel:`Email Configuration` tab on an email template, there is a :guilabel:`Reply To` field. In this field, add email addresses to which replies are redirected when sending emails en masse using this template." +msgstr "" + +#: ../../content/applications/general/companies/email_template.rst:191 +msgid "Add multiple email addresses by adding a comma `,` between the addresses or dynamic placeholders." +msgstr "" + +#: ../../content/applications/general/companies/email_template.rst:-1 +msgid "Reply-to field on template." +msgstr "" + +#: ../../content/applications/general/companies/email_template.rst:198 +msgid "The :guilabel:`Reply To` field is **only** used for mass mailing (sending emails in bulk). Bulk emails can be sent in almost every Odoo application that has a list view option." +msgstr "" + +#: ../../content/applications/general/companies/email_template.rst:201 +msgid "To send mass mails, while in :guilabel:`list` view, check the boxes next to the desired records where the emails are to be sent, click the :guilabel:`Action` button (represented by a :guilabel:`⚙️ (gear)` icon), and select the desired email option from the :guilabel:`Action` drop-down menu. Email options can vary by the particular list view and application." +msgstr "" + +#: ../../content/applications/general/companies/email_template.rst:206 +msgid "If it is possible to send an email, a mail composer pop-up window appears, with values that can be defined and customized. This option will be available on the :guilabel:`Action` button on pages where emails can be sent in bulk---for example, on the :guilabel:`Customers` page of the CRM app. This action occurs throughout the Odoo database." +msgstr "" + +#: ../../content/applications/general/companies/email_template.rst:-1 +msgid "Email composer in mass mailing mode with reply-to highlighted." +msgstr "" + +#: ../../content/applications/general/companies/email_template.rst:216 +msgid "Transactional emails and corresponding URLs" +msgstr "" + +#: ../../content/applications/general/companies/email_template.rst:218 +msgid "In Odoo, multiple events can trigger the sending of automated emails. These emails are known as *transactional emails*, and sometimes contain links redirecting to the Odoo database." +msgstr "" + +#: ../../content/applications/general/companies/email_template.rst:221 +msgid "By default, links generated by the database use the dynamic `web.base.url` key defined in the system parameters. For more information about this, see :ref:`system parameters `." +msgstr "" + +#: ../../content/applications/general/companies/email_template.rst:225 +msgid "If the *Website* application is not installed, the `web.base.url` key will always be the default parameter used to generate all the links." +msgstr "" + +#: ../../content/applications/general/companies/email_template.rst:229 +msgid "The `web.base.url` key can only have a single value, meaning that, in a multi-website or multi-company database environment, even if there is a specific domain name for each website, the links generated to share a document (or the links within a transactional email) may remain the same, regardless of which website/company is related to the sending of the email/document." +msgstr "" + +#: ../../content/applications/general/companies/email_template.rst:235 +msgid "If the :guilabel:`Value` of the :guilabel:`web.base.url` system parameter is equal to `https://www.mycompany.com` and there are two separate companies in Odoo with different website URLs: `https://www.mycompany2.com` and `https://www.mycompany1.com`, the links created by Odoo to share a document, or send a transactional email, come from the domain: `https://www.mycompany.com`, regardless of which company sends the document or email." +msgstr "" + +#: ../../content/applications/general/companies/email_template.rst:241 +msgid "This is not always the case, as some Odoo applications (*eCommerce*, for example) have a link established in the database with the *Website* application. In that case, if a specific domain is defined for the website, the URL generated in the email template uses the domain defined on the corresponding website of the company." +msgstr "" + +#: ../../content/applications/general/companies/email_template.rst:247 +msgid "When a customer makes a purchase on an Odoo *eCommerce* website, the order has an established link with that website. As a result, the links in the confirmation email sent to the customer use the domain name for that specific website." +msgstr "" + +#: ../../content/applications/general/companies/email_template.rst:252 +msgid "A document shared using the *Documents* application will **always** use the `web.base.url` key, as the document shared is not associated with any particular website. This means that the URL will always be the same (the `web.base.url` key value), no matter what company it's shared from. This is a known limitation." +msgstr "" + +#: ../../content/applications/general/companies/email_template.rst:257 +msgid "For more information about how to configure domains, check out the :doc:`domain name documentation `." +msgstr "" + +#: ../../content/applications/general/companies/email_template.rst:261 +msgid "Updating translations within email templates" +msgstr "" + +#: ../../content/applications/general/companies/email_template.rst:263 +msgid "In Odoo, email templates are automatically translated for all users in the database for all of the languages installed. Changing the translations shouldn't be necessary. However, if for a specific reason, some of the translations need to be changed, it can be done." +msgstr "" + +#: ../../content/applications/general/companies/email_template.rst:268 +msgid "Like any modification in the code, if translation changes are not done correctly (for example, modifications leading to bad syntax), it can break the template, and as a result, the template will appear blank." +msgstr "" + +#: ../../content/applications/general/companies/email_template.rst:272 +msgid "In order to edit translations, first enter :ref:`developer mode `. Then, on the email template, click on the :guilabel:`Edit` button, and then click on the language button, represented by the initials of the language currently being used (e.g. :guilabel:`EN` for English)." +msgstr "" + +#: ../../content/applications/general/companies/email_template.rst:-1 +msgid "Edit the language of a template." +msgstr "" + +#: ../../content/applications/general/companies/email_template.rst:281 +msgid "If there aren't multiple languages installed and activated in the database, or if the user does not have administration access rights, the language button will not appear." +msgstr "" + +#: ../../content/applications/general/companies/email_template.rst:284 +msgid "A pop-up window with the different languages installed on the database appears. From this pop-up, editing of translations is possible. When the desired changes have been made, click the :guilabel:`Save` button to save the changes." +msgstr "" + +#: ../../content/applications/general/companies/email_template.rst:-1 +msgid "Translation of the body of the Appointment Booked template." +msgstr "" + +#: ../../content/applications/general/companies/email_template.rst:293 +msgid "When editing the translations, the default language set in the database appears in **bold**." msgstr "" #: ../../content/applications/general/developer_mode.rst:5 @@ -766,264 +1021,370 @@ msgstr "" msgid "See the :guilabel:`Fields View Get`" msgstr "" -#: ../../content/applications/general/digest_emails.rst:3 -msgid "Digest Emails" -msgstr "" - -#: ../../content/applications/general/digest_emails.rst:5 -msgid "**Digest Emails** are periodic snapshots sent to your organization via email that include high-level information about how your business is performing." -msgstr "" - -#: ../../content/applications/general/digest_emails.rst:8 -msgid "Navigate to Digest Emails by going to :menuselection:`Settings --> General Settings --> Statistics`, then activate the **Digest Emails** feature and click on save." -msgstr "" - -#: ../../content/applications/general/digest_emails.rst:-1 -msgid "Digest Emails section inside General Settings." -msgstr "" - -#: ../../content/applications/general/digest_emails.rst:15 -msgid "You can control a variety of settings for your Digest Emails, such as:" -msgstr "" - -#: ../../content/applications/general/digest_emails.rst:17 -msgid "which KPIs are shared in the Digest" -msgstr "" - -#: ../../content/applications/general/digest_emails.rst:18 -msgid "how often Digest Emails are sent" -msgstr "" - -#: ../../content/applications/general/digest_emails.rst:19 -msgid "who in your organization receives Digest Emails" -msgstr "" - -#: ../../content/applications/general/digest_emails.rst:20 -msgid "creating custom Digest Email templates" -msgstr "" - -#: ../../content/applications/general/digest_emails.rst:21 -msgid "adding additional KPIs (Studio required)" -msgstr "" - -#: ../../content/applications/general/digest_emails.rst:24 -msgid "By default, Digest Email is *enabled*, and *Your Odoo Periodic Digest* serves as the primary template, which includes all KPI measurements across your Odoo database and is sent daily to administrators." -msgstr "" - -#: ../../content/applications/general/digest_emails.rst:31 -msgid "Customize *Your Odoo Periodic Digest*" -msgstr "" - -#: ../../content/applications/general/digest_emails.rst:33 -msgid "To customize the default Digest Email (*Your Odoo Periodic Digest*), go to :menuselection:`Settings --> General Settings --> Statistics --> Digest Email`, select *Your Odoo Periodic Digest* and click on the *external link* next to the dropdown selection." -msgstr "" - -#: ../../content/applications/general/digest_emails.rst:37 -msgid "A popup window appears and presents a variety of editable settings, which include:" -msgstr "" - -#: ../../content/applications/general/digest_emails.rst:39 -msgid "**Digest Title** - what you want your Digest Email to be called" -msgstr "" - -#: ../../content/applications/general/digest_emails.rst:40 -msgid "**Periodicity** - control the regimen in how often Digest Emails are sent" -msgstr "" - -#: ../../content/applications/general/digest_emails.rst:41 -msgid "**KPIs** - check/uncheck each calculated KPI that appears in Digest Emails" -msgstr "" - -#: ../../content/applications/general/digest_emails.rst:42 -msgid "**Recipients** - add/remove users who receive your Digest Emails" -msgstr "" - -#: ../../content/applications/general/digest_emails.rst:43 -msgid "**Custom** - add your own KPIs (Studio required)" -msgstr "" - -#: ../../content/applications/general/digest_emails.rst:-1 -msgid "Customize default Digest Email settings and custom KPIs." -msgstr "" - -#: ../../content/applications/general/digest_emails.rst:52 -msgid "Custom digest emails" -msgstr "" - -#: ../../content/applications/general/digest_emails.rst:54 -msgid "To do so, click on **Configure Digest Emails** and then **Create**." -msgstr "" - -#: ../../content/applications/general/digest_emails.rst:56 -msgid "From there, give your Digest Email a title, specify periodicity, and choose your desired KPIs and recipients fields as needed." -msgstr "" - -#: ../../content/applications/general/digest_emails.rst:59 -msgid "After you click **Save**, your new custom Digest Email is available as a selection in the **General Settings** dropdown menu." -msgstr "" - -#: ../../content/applications/general/digest_emails.rst:65 -msgid "Custom KPIs with Studio" -msgstr "" - -#: ../../content/applications/general/digest_emails.rst:67 -msgid "For either *Your Odoo Periodic Digest* or your own custom Digest Email, you can add your own KPIs by using Odoo Studio." -msgstr "" - -#: ../../content/applications/general/digest_emails.rst:70 -msgid "To begin, click the **Toggle Studio** icon or click the **Recipients** tab and then the ellipses :menuselection:`… icon --> Add Custom Field` to edit the template or add additional fields." -msgstr "" - -#: ../../content/applications/general/digest_emails.rst:73 -msgid "In order to create additional fields, you must create two fields on the digest object:" -msgstr "" - -#: ../../content/applications/general/digest_emails.rst:75 -msgid "create a boolean field called `kpi_myfield` and display it in the KPIs tab" -msgstr "" - -#: ../../content/applications/general/digest_emails.rst:76 -msgid "create a computed field called `kpi_myfield_value` that computes your customized KPI" -msgstr "" - -#: ../../content/applications/general/digest_emails.rst:77 -msgid "select your KPI(s) in the KPIs tab." -msgstr "" - -#: ../../content/applications/general/digest_emails.rst:80 -msgid "Computed values reference table" -msgstr "" - -#: ../../content/applications/general/digest_emails.rst:83 -msgid "LABEL" -msgstr "" - -#: ../../content/applications/general/digest_emails.rst:83 -msgid "VALUE" -msgstr "" - -#: ../../content/applications/general/digest_emails.rst:85 -msgid "Connected Users" -msgstr "" - -#: ../../content/applications/general/digest_emails.rst:85 -msgid "`kpi_res_users_connected_value`" -msgstr "" - -#: ../../content/applications/general/digest_emails.rst:87 -msgid "Messages Sent" -msgstr "" - -#: ../../content/applications/general/digest_emails.rst:87 -msgid "`kpi_mail_message_total_value`" -msgstr "" - -#: ../../content/applications/general/digest_emails.rst:89 -msgid "New Leads" -msgstr "" - -#: ../../content/applications/general/digest_emails.rst:89 -msgid "`kpi_crm_lead_created_value`" -msgstr "" - -#: ../../content/applications/general/digest_emails.rst:91 -msgid "Opportunities Won" -msgstr "" - -#: ../../content/applications/general/digest_emails.rst:91 -msgid "`kpi_crm_opportunities_won_value`" -msgstr "" - -#: ../../content/applications/general/digest_emails.rst:93 -msgid "Open Tasks" -msgstr "" - -#: ../../content/applications/general/digest_emails.rst:93 -msgid "`kpi_project_task_opened_value`" -msgstr "" - -#: ../../content/applications/general/digest_emails.rst:95 -msgid "Tickets Closed" -msgstr "" - -#: ../../content/applications/general/digest_emails.rst:95 -msgid "`kpi_helpdesk_tickets_closed_value`" -msgstr "" - -#: ../../content/applications/general/digest_emails.rst:97 -msgid "% of Happiness" -msgstr "" - -#: ../../content/applications/general/digest_emails.rst:97 -msgid "`kpi_livechat_rating_value`" -msgstr "" - -#: ../../content/applications/general/digest_emails.rst:99 -msgid "Conversations handled" -msgstr "" - -#: ../../content/applications/general/digest_emails.rst:99 -msgid "`kpi_livechat_conversations_value`" -msgstr "" - -#: ../../content/applications/general/digest_emails.rst:101 -msgid "Time to answer (sec)" -msgstr "" - -#: ../../content/applications/general/digest_emails.rst:101 -msgid "`kpi_livechat_response_value`" -msgstr "" - -#: ../../content/applications/general/digest_emails.rst:103 -msgid "All Sales" -msgstr "" - -#: ../../content/applications/general/digest_emails.rst:103 -msgid "`kpi_all_sale_total_value`" -msgstr "" - -#: ../../content/applications/general/digest_emails.rst:105 -msgid "eCommerce Sales" -msgstr "" - -#: ../../content/applications/general/digest_emails.rst:105 -msgid "`kpi_website_sale_total_value`" -msgstr "" - -#: ../../content/applications/general/digest_emails.rst:107 -msgid "Revenue" -msgstr "" - -#: ../../content/applications/general/digest_emails.rst:107 -msgid "`kpi_account_total_revenue_value`" -msgstr "" - -#: ../../content/applications/general/digest_emails.rst:109 -msgid "Bank & Cash Moves" -msgstr "" - -#: ../../content/applications/general/digest_emails.rst:109 -msgid "`kpi_account_bank_cash_value`" -msgstr "" - -#: ../../content/applications/general/digest_emails.rst:111 -msgid "POS Sales" -msgstr "" - -#: ../../content/applications/general/digest_emails.rst:111 -msgid "`kpi_pos_total_value`" -msgstr "" - -#: ../../content/applications/general/digest_emails.rst:113 -msgid "New Employees" -msgstr "" - -#: ../../content/applications/general/digest_emails.rst:113 -msgid "`kpi_hr_recruitment_new_colleagues_value`" -msgstr "" - #: ../../content/applications/general/email_communication.rst:5 -msgid "Email Communication" +msgid "Email communication" +msgstr "" + +#: ../../content/applications/general/email_communication/azure_oauth.rst:3 +msgid "Connect Microsoft Outlook 365 to Odoo using Azure OAuth" +msgstr "" + +#: ../../content/applications/general/email_communication/azure_oauth.rst:5 +msgid "Odoo is compatible with Microsoft's Azure OAuth for Microsoft 365. In order to send and receive secure emails from a custom domain, all that is required is to configure a few settings on the Azure platform and on the back end of the Odoo database. This configuration works with either a personal email address or an address created by a custom domain." +msgstr "" + +#: ../../content/applications/general/email_communication/azure_oauth.rst:11 +msgid "`Microsoft Learn: Register an application with the Microsoft identity platform `_" +msgstr "" + +#: ../../content/applications/general/email_communication/azure_oauth.rst:15 +msgid ":doc:`/applications/general/users/azure`" +msgstr "" + +#: ../../content/applications/general/email_communication/azure_oauth.rst:16 +msgid ":doc:`/applications/productivity/calendar/outlook`" +msgstr "" + +#: ../../content/applications/general/email_communication/azure_oauth.rst:19 +msgid "Setup in Microsoft Azure Portal" +msgstr "" + +#: ../../content/applications/general/email_communication/azure_oauth.rst:22 +#: ../../content/applications/general/users/azure.rst:40 +msgid "Create a new application" +msgstr "" + +#: ../../content/applications/general/email_communication/azure_oauth.rst:24 +msgid "To get started, go to `Microsoft's Azure Portal `_. Log in with the :guilabel:`Microsoft Outlook Office 365` account if there is one, otherwise log in with the personal :guilabel:`Microsoft account`. A user with administrative access to the Azure Settings will need to connect and perform the following configuration. Next, navigate to the section labeled :guilabel:`Manage Microsoft Entra ID` (formally *Azure Active Directory*)." +msgstr "" + +#: ../../content/applications/general/email_communication/azure_oauth.rst:30 +msgid "Now, click on :guilabel:`Add (+)`, located in the top menu, and then select :guilabel:`App registration`. On the :guilabel:`Register an application` screen, rename the :guilabel:`Name` to `Odoo` or something recognizable. Under the :guilabel:`Supported account types` section select :guilabel:`Accounts in any organizational directory (Any Microsoft Entra ID directory - Multitenant) and personal Microsoft accounts (e.g. Skype, Xbox)`." +msgstr "" + +#: ../../content/applications/general/email_communication/azure_oauth.rst:36 +msgid "Under the :guilabel:`Redirect URL` section, select :guilabel:`Web` as the platform, and then input `https:///microsoft_outlook/confirm` in the :guilabel:`URL` field. The Odoo base URL is the canonical domain at which your Odoo instance can be reached in the URL field." +msgstr "" + +#: ../../content/applications/general/email_communication/azure_oauth.rst:41 +msgid "*mydatabase.odoo.com*, where *mydatabase* is the actual prefix of the database's subdomain, assuming it's hosted on Odoo.com" +msgstr "" + +#: ../../content/applications/general/email_communication/azure_oauth.rst:44 +msgid "After the URL has been added to the field, :guilabel:`Register` the application so it is created." +msgstr "" + +#: ../../content/applications/general/email_communication/azure_oauth.rst:47 +msgid "API permissions" +msgstr "" + +#: ../../content/applications/general/email_communication/azure_oauth.rst:49 +msgid "The :guilabel:`API permissions` should be set next. Odoo will need specific API permissions to be able to read (IMAP) and send (SMTP) emails in the Microsoft 365 setup. First, click the :guilabel:`API permissions` link, located in the left menu bar. Next, click on the :guilabel:`(+) Add a Permission` button and select :guilabel:`Microsoft Graph` under :guilabel:`Commonly Used Microsoft APIs`. After, select the :guilabel:`Delegated Permissions` option." +msgstr "" + +#: ../../content/applications/general/email_communication/azure_oauth.rst:55 +msgid "In the search bar, search for the following :guilabel:`Delegated permissions` and click :guilabel:`Add permissions` for each one:" +msgstr "" + +#: ../../content/applications/general/email_communication/azure_oauth.rst:58 +msgid ":guilabel:`SMTP.Send`" +msgstr "" + +#: ../../content/applications/general/email_communication/azure_oauth.rst:59 +msgid ":guilabel:`IMAP.AccessAsUser.All`" +msgstr "" + +#: ../../content/applications/general/email_communication/azure_oauth.rst:62 +msgid "The :guilabel:`User.Read` permission will be added by default." +msgstr "" + +#: ../../content/applications/general/email_communication/azure_oauth.rst:-1 +msgid "API permissions needed for Odoo integration are listed under the Microsoft Graph." +msgstr "" + +#: ../../content/applications/general/email_communication/azure_oauth.rst:69 +msgid "Assign users and groups" +msgstr "" + +#: ../../content/applications/general/email_communication/azure_oauth.rst:71 +msgid "After adding the API permissions, navigate back to the :guilabel:`Overview` of the :guilabel:`Application` in the top of the left sidebar menu." +msgstr "" + +#: ../../content/applications/general/email_communication/azure_oauth.rst:74 +msgid "Now, add users to this application. Under the :guilabel:`Essentials` overview table, click on the link labeled :guilabel:`Managed Application in Local Directory`, or the last option on the bottom right-hand side of the table." +msgstr "" + +#: ../../content/applications/general/email_communication/azure_oauth.rst:-1 +msgid "Add users/groups by clicking the Managed application in local directory link for the\n" +"created application." +msgstr "" + +#: ../../content/applications/general/email_communication/azure_oauth.rst:83 +msgid "In the left sidebar menu, select :guilabel:`Users and Groups`. Next, click on :guilabel:`(+) Add User/Group`. Depending on the account, either a :guilabel:`Group` and a :guilabel:`User` can be added, or only :guilabel:`Users`. Personal accounts will only allow for :guilabel:`Users` to be added." +msgstr "" + +#: ../../content/applications/general/email_communication/azure_oauth.rst:88 +msgid "Under :guilabel:`Users` or :guilabel:`Groups`, click on :guilabel:`None Selected` and add the users or group of users that will be sending emails from the :guilabel:`Microsoft account` in Odoo. :guilabel:`Add` the users/groups, click :guilabel:`Select`, and then :guilabel:`Assign` them to the application." +msgstr "" + +#: ../../content/applications/general/email_communication/azure_oauth.rst:94 +msgid "Create credentials" +msgstr "" + +#: ../../content/applications/general/email_communication/azure_oauth.rst:96 +msgid "Now that the Microsoft Azure app is set up, credentials need to be created for the Odoo setup. These include the :guilabel:`Client ID` and :guilabel:`Client Secret`. To start, the :guilabel:`Client ID` can be copied from the :guilabel:`Overview` page of the app. The :guilabel:`Client ID` or :guilabel:`Application ID` is located under the :guilabel:`Display Name` in the :guilabel:`Essentials` overview of the app." +msgstr "" + +#: ../../content/applications/general/email_communication/azure_oauth.rst:-1 +msgid "Application/Client ID located in the Overview of the app." +msgstr "" + +#: ../../content/applications/general/email_communication/azure_oauth.rst:106 +msgid "Next, the :guilabel:`Client Secret Value` needs to be retrieved. To get this value, click on :guilabel:`Certificates & Secrets` in the left sidebar menu. Then, a :guilabel:`Client Secret` needs to be produced. In order to do this, click on the :guilabel:`(+) New Client Secret` button." +msgstr "" + +#: ../../content/applications/general/email_communication/azure_oauth.rst:110 +msgid "A window on the right will populate with a button labeled :guilabel:`Add a client secret`. Under :guilabel:`Description`, type in `Odoo Fetchmail` or something recognizable, and then set the :guilabel:`expiration date`." +msgstr "" + +#: ../../content/applications/general/email_communication/azure_oauth.rst:115 +msgid "A new :guilabel:`Client Secret` will need to be produced and configured if the first one expires. In this event, there could be an interruption of service, so the expiration date should be noted and set to the furthest possible date." +msgstr "" + +#: ../../content/applications/general/email_communication/azure_oauth.rst:119 +msgid "Next, click on :guilabel:`Add` when these two values are entered. A :guilabel:`Client Secret Value` and :guilabel:`Secret ID` will be created. It is important to copy the :guilabel:`Value` or :guilabel:`Client Secret Value` into a notepad as it will become encrypted after leaving this page. The :guilabel:`Secret ID` is not needed." +msgstr "" + +#: ../../content/applications/general/email_communication/azure_oauth.rst:-1 +msgid "Client Secret Value or Value in the app's credentials." +msgstr "" + +#: ../../content/applications/general/email_communication/azure_oauth.rst:128 +msgid "After these steps, the following items should be ready to be set up in Odoo:" +msgstr "" + +#: ../../content/applications/general/email_communication/azure_oauth.rst:130 +msgid "A client ID (:guilabel:`Client ID` or :guilabel:`Application ID`)" +msgstr "" + +#: ../../content/applications/general/email_communication/azure_oauth.rst:131 +msgid "A client secret (:guilabel:`Value` or :guilabel:`Client Secret Value`)" +msgstr "" + +#: ../../content/applications/general/email_communication/azure_oauth.rst:133 +msgid "This completes the setup on the :guilabel:`Microsoft Azure Portal` side." +msgstr "" + +#: ../../content/applications/general/email_communication/azure_oauth.rst:136 +#: ../../content/applications/general/email_communication/google_oauth.rst:111 +msgid "Setup in Odoo" +msgstr "" + +#: ../../content/applications/general/email_communication/azure_oauth.rst:139 +msgid "Enter Microsoft Outlook credentials" +msgstr "" + +#: ../../content/applications/general/email_communication/azure_oauth.rst:141 +msgid "First, open the Odoo database and navigate to the :guilabel:`Apps` module. Then, remove the :guilabel:`Apps` filter from the search bar and type in `Outlook`. After that, install the module called :guilabel:`Microsoft Outlook`." +msgstr "" + +#: ../../content/applications/general/email_communication/azure_oauth.rst:145 +msgid "Next, navigate to :menuselection:`Settings --> General Settings`, and under the :guilabel:`Discuss` section, ensure that the checkbox for :guilabel:`Custom Email Servers` is checked. This populates a new option for :guilabel:`Outlook Credentials`." +msgstr "" + +#: ../../content/applications/general/email_communication/azure_oauth.rst:149 +msgid ":guilabel:`Save` the progress." +msgstr "" + +#: ../../content/applications/general/email_communication/azure_oauth.rst:151 +msgid "Then, copy and paste the :guilabel:`Client ID` (Application ID) and :guilabel:`Client Secret (Client Secret Value)` into the respective fields and :guilabel:`Save` the settings." +msgstr "" + +#: ../../content/applications/general/email_communication/azure_oauth.rst:-1 +msgid "Outlook Credentials in Odoo General Settings." +msgstr "" + +#: ../../content/applications/general/email_communication/azure_oauth.rst:159 +#: ../../content/applications/general/email_communication/google_oauth.rst:127 +msgid "Configure outgoing email server" +msgstr "" + +#: ../../content/applications/general/email_communication/azure_oauth.rst:161 +msgid "On the :guilabel:`General Settings` page, under the :guilabel:`Custom Email Servers` setting, click the :guilabel:`Outgoing Email Servers` link to configure the Microsoft account." +msgstr "" + +#: ../../content/applications/general/email_communication/azure_oauth.rst:164 +msgid "Then, create a new email server and check the box for :guilabel:`Outlook`. Next, fill in the :guilabel:`Name` (it can be anything) and the Microsoft Outlook email :guilabel:`Username`." +msgstr "" + +#: ../../content/applications/general/email_communication/azure_oauth.rst:167 +msgid "If the :guilabel:`From Filter` field is empty, enter either a :ref:`domain or email address `." +msgstr "" + +#: ../../content/applications/general/email_communication/azure_oauth.rst:170 +msgid "Then, click on :guilabel:`Connect your Outlook account`." +msgstr "" + +#: ../../content/applications/general/email_communication/azure_oauth.rst:172 +msgid "A new window from Microsoft opens to complete the :guilabel:`authorization process`. Select the appropriate email address that is being configured in Odoo." +msgstr "" + +#: ../../content/applications/general/email_communication/azure_oauth.rst:-1 +msgid "Permission page to grant access between newly created app and Odoo." +msgstr "" + +#: ../../content/applications/general/email_communication/azure_oauth.rst:179 +msgid "Then, allow Odoo to access the Microsoft account by clicking on :guilabel:`Yes`. After this, the page will navigate back to the newly configured :guilabel:`Outgoing Mail Server` in Odoo. The configuration automatically loads the :guilabel:`token` in Odoo, and a tag stating :guilabel:`Outlook Token Valid` appears in green." +msgstr "" + +#: ../../content/applications/general/email_communication/azure_oauth.rst:-1 +msgid "Valid Outlook Token indicator." +msgstr "" + +#: ../../content/applications/general/email_communication/azure_oauth.rst:188 +msgid "Finally, click :guilabel:`Test Connection`. A confirmation message should appear. The Odoo database can now send safe, secure emails through Microsoft Outlook using OAuth authentication." +msgstr "" + +#: ../../content/applications/general/email_communication/azure_oauth.rst:194 +msgid "Configuration with a single outgoing mail server" +msgstr "" + +#: ../../content/applications/general/email_communication/azure_oauth.rst:196 +msgid "Configuring a single outgoing server is the simplest configuration available for Microsoft Azure and it doesn't require extensive access rights for the users in the database." +msgstr "" + +#: ../../content/applications/general/email_communication/azure_oauth.rst:199 +msgid "A generic email address would be used to send emails for all users within the database. For example it could be structured with a `notifications` alias (`notifications@example.com`) or `contact` alias (`contact@example.com`). This address must be set as the :guilabel:`FROM Filtering` on the server. This address must also match the `{mail.default.from}@{mail.catchall.domain}` key combination in the system parameters." +msgstr "" + +#: ../../content/applications/general/email_communication/azure_oauth.rst:206 +#: ../../content/applications/general/email_communication/azure_oauth.rst:247 +msgid "For more information on the from filter visit: :ref:`email_communication/default`." +msgstr "" + +#: ../../content/applications/general/email_communication/azure_oauth.rst:209 +#: ../../content/applications/general/email_communication/azure_oauth.rst:254 +msgid "The :guilabel:`System Parameters` can be accessed by activating :ref:`developer-mode` in the :menuselection:`Settings --> Technical --> Parameters --> System Parameters` menu." +msgstr "" + +#: ../../content/applications/general/email_communication/azure_oauth.rst:212 +msgid "When using this configuration, every email that is sent from the database will use the address of the configured `notification` mailbox. However it should be noted that the name of the sender will appear but their email address will change:" +msgstr "" + +#: ../../content/applications/general/email_communication/azure_oauth.rst:-1 +msgid "Name from real sender with static email." +msgstr "" + +#: ../../content/applications/general/email_communication/azure_oauth.rst:221 +msgid "Single outgoing mail server configuration:" +msgstr "" + +#: ../../content/applications/general/email_communication/azure_oauth.rst:223 +msgid "Outgoing mail server **username** (login) = `notifications@example.com`" +msgstr "" + +#: ../../content/applications/general/email_communication/azure_oauth.rst:224 +msgid "Outgoing mail server :guilabel:`FROM Filtering` = `notifications@example.com`" +msgstr "" + +#: ../../content/applications/general/email_communication/azure_oauth.rst:225 +#: ../../content/applications/general/email_communication/azure_oauth.rst:279 +msgid "`mail.catchall.domain` in system parameters = `example.com`" +msgstr "" + +#: ../../content/applications/general/email_communication/azure_oauth.rst:226 +#: ../../content/applications/general/email_communication/azure_oauth.rst:280 +msgid "`mail.default.from` in system parameters = `notifications`" +msgstr "" + +#: ../../content/applications/general/email_communication/azure_oauth.rst:229 +msgid "User-specific (multiple user) configuration" +msgstr "" + +#: ../../content/applications/general/email_communication/azure_oauth.rst:231 +msgid "In addition to a generic email server, individual email servers can be set up for users in a database. These email addresses must be set as the :guilabel:`FROM Filtering` on each individual server for this configuration to work." +msgstr "" + +#: ../../content/applications/general/email_communication/azure_oauth.rst:235 +msgid "This configuration is the more difficult of the two Microsoft Azure configurations, in that it requires all users configured with email servers to have access rights to settings in order to establish a connection to the email server." +msgstr "" + +#: ../../content/applications/general/email_communication/azure_oauth.rst:240 +#: ../../content/applications/general/iot/config/pos.rst:21 +#: ../../content/applications/general/iot/config/troubleshooting.rst:456 +msgid "Setup" +msgstr "" + +#: ../../content/applications/general/email_communication/azure_oauth.rst:242 +msgid "Each user should have a separate email server set up. The :guilabel:`FROM Filtering` should be set so that only the user's email is sent from that server. In other words, only a user with an email address that matches the set :guilabel:`FROM Filtering` is able to use this server." +msgstr "" + +#: ../../content/applications/general/email_communication/azure_oauth.rst:249 +msgid "A :ref:`fallback server ` must be setup to allow for the sending of :guilabel:`notifications`. The :guilabel:`FROM Filtering` for this server should have the value of the `{mail.default.from}@{mail.catchall.domain}`." +msgstr "" + +#: ../../content/applications/general/email_communication/azure_oauth.rst:258 +msgid "The configuration for this transactional email server can work alongside an outgoing mass-mailing email server. The :guilabel:`FROM Filtering` for the mass-mailing email server can remain empty, but it's require to be added in the settings of the *Email Marketing* application." +msgstr "" + +#: ../../content/applications/general/email_communication/azure_oauth.rst:263 +msgid "For more information on setting the mass-mailing email server visit :ref:`email_communication/mass_mails`." +msgstr "" + +#: ../../content/applications/general/email_communication/azure_oauth.rst:267 +msgid "Multiple user outgoing mail server configuration:" +msgstr "" + +#: ../../content/applications/general/email_communication/azure_oauth.rst:270 +msgid "User #1 mailbox" +msgstr "" + +#: ../../content/applications/general/email_communication/azure_oauth.rst:270 +msgid "Outgoing mail server #1 **username** (login) = `john@example.com`" +msgstr "" + +#: ../../content/applications/general/email_communication/azure_oauth.rst:271 +msgid "Outgoing mail server #1 :guilabel:`FROM Filtering` = `john@example.com`" +msgstr "" + +#: ../../content/applications/general/email_communication/azure_oauth.rst:273 +msgid "User #2 mailbox" +msgstr "" + +#: ../../content/applications/general/email_communication/azure_oauth.rst:273 +msgid "Outgoing mail server #2 **username** (login) = `jane@example.com`" +msgstr "" + +#: ../../content/applications/general/email_communication/azure_oauth.rst:274 +msgid "Outgoing mail server #2 :guilabel:`FROM Filtering` = `jane@example.com`" +msgstr "" + +#: ../../content/applications/general/email_communication/azure_oauth.rst:276 +msgid "Notifications mailbox" +msgstr "" + +#: ../../content/applications/general/email_communication/azure_oauth.rst:276 +msgid "Outgoing mail server #3 **username** (login) = `notifications@example.com`" +msgstr "" + +#: ../../content/applications/general/email_communication/azure_oauth.rst:277 +msgid "Outgoing mail server #3 :guilabel:`FROM Filtering` = `notifications@example.com`" +msgstr "" + +#: ../../content/applications/general/email_communication/azure_oauth.rst:279 +msgid "System Parameters" +msgstr "" + +#: ../../content/applications/general/email_communication/azure_oauth.rst:283 +msgid "Configure incoming email server" +msgstr "" + +#: ../../content/applications/general/email_communication/azure_oauth.rst:285 +msgid "The incoming account should be configured in a similar way to the outgoing email account. Navigate to the :guilabel:`Incoming Mail Servers` in the :guilabel:`Technical Menu` and :guilabel:`Create` a new configuration. Check or Select the button next to :guilabel:`Outlook Oauth Authentication` and enter the :guilabel:`Microsoft Outlook username`. Click on :guilabel:`Connect your Outlook account`. Odoo will state: :guilabel:`Outlook Token Valid` Now :guilabel:`Test and Confirm` the account. The account should be ready to receive email to the Odoo database." +msgstr "" + +#: ../../content/applications/general/email_communication/azure_oauth.rst:293 +msgid ":doc:`email_servers`" msgstr "" #: ../../content/applications/general/email_communication/email_domain.rst:3 @@ -1360,7 +1721,7 @@ msgid "Scope of this documentation" msgstr "" #: ../../content/applications/general/email_communication/email_servers.rst:26 -msgid "This document is **mainly dedicated to Odoo on-premise databases** who don't benefit from an out-of-the-box solution to send and receive emails in Odoo, unlike `Odoo Online `_ and `Odoo.sh `_. Incoming and outgoing servers must be configured for on-premise databases." +msgid "This document is **mainly dedicated to Odoo on-premise databases** that do not benefit from an out-of-the-box solution to send and receive emails in Odoo, unlike `Odoo Online `_ and `Odoo.sh `_. Incoming and outgoing servers must be configured for on-premise databases." msgstr "" #: ../../content/applications/general/email_communication/email_servers.rst:31 @@ -1392,7 +1753,15 @@ msgid "Manage outbound messages" msgstr "" #: ../../content/applications/general/email_communication/email_servers.rst:61 -msgid "As a system admin, go to :menuselection:`Settings --> General Settings --> Discuss` in Odoo, and enable the :guilabel:`Custom Email Servers` option. Then, click :guilabel:`Save`. Next, click :guilabel:`Outgoing Email Servers` and click :guilabel:`Create` to create a new outgoing mail server record in Odoo. Reference the SMTP data of the external email server. Once all the information has been filled out, click :guilabel:`Test Connection`." +msgid "As a system administrator, go to :menuselection:`Settings --> General Settings --> Discuss` in Odoo, and enable the :guilabel:`Custom Email Servers` option. Then, click :guilabel:`Save`. Next, click :guilabel:`Outgoing Email Servers` and click :guilabel:`Create` to create a new outgoing mail server record in Odoo. Reference the SMTP data of the external email server. Once all the information has been filled out, click :guilabel:`Test Connection`." +msgstr "" + +#: ../../content/applications/general/email_communication/email_servers.rst:68 +msgid ":doc:`google_oauth`" +msgstr "" + +#: ../../content/applications/general/email_communication/email_servers.rst:69 +msgid ":doc:`azure_oauth`" msgstr "" #: ../../content/applications/general/email_communication/email_servers.rst:72 @@ -1500,7 +1869,7 @@ msgid "Set up different dedicated servers for transactional and mass emails" msgstr "" #: ../../content/applications/general/email_communication/email_servers.rst:179 -msgid "In Odoo a separate email server can be used for transactional emails and mass mailings. Example: Use Postmark or SendinBlue for transactional emails, and Amazon SES, Mailgun, Sendgrid or :doc:`Mailjet ` for mass mailings." +msgid "In Odoo a separate email server can be used for transactional emails and mass mailings. Example: Use Postmark or SendinBlue for transactional emails, and Amazon SES, Mailgun, Sendgrid or :doc:`Mailjet ` for mass mailings." msgstr "" #: ../../content/applications/general/email_communication/email_servers.rst:184 @@ -1528,7 +1897,7 @@ msgid "Odoo relies on generic email aliases to fetch incoming messages." msgstr "" #: ../../content/applications/general/email_communication/email_servers.rst:209 -msgid "**Reply messages** of messages sent from Odoo are routed to their original discussion thread (and to the inbox of all its followers) by the alias of the model if there is any or by the catchall alias (**catchall@**). Replies to messages of models that don't have a custom alias will use the catchall alias (`catchall@mycompany.odoo.com`). The catchall address, however, does not have another action attached to it like other aliases might, it is only used to collect replies." +msgid "**Reply messages** of messages sent from Odoo are routed to their original discussion thread (and to the inbox of all its followers) by the alias of the model if there is any or by the catchall alias (**catchall@**). Replies to messages of models that do not have a custom alias will use the catchall alias (`catchall@mycompany.odoo.com`). The catchall address, however, does not have another action attached to it like other aliases might, it is only used to collect replies." msgstr "" #: ../../content/applications/general/email_communication/email_servers.rst:214 @@ -1588,7 +1957,7 @@ msgid "All the aliases are customizable in Odoo. Object aliases can be edited fr msgstr "" #: ../../content/applications/general/email_communication/email_servers.rst:264 -msgid "To edit catchall and bounce aliases, first activate the :ref:`developer mode `. Then, go to :menuselection:`Settings --> Technical --> Parameters --> System Parameters` to customize the aliases (`mail.catchall.alias` & `mail.bounce.alias`). These types of changes should be completed prior to the database going live. If a customer replies after a change is made then the system will not recognize the old alias and the reply won't be received." +msgid "To edit catchall and bounce aliases, first activate the :ref:`developer mode `. Then, go to :menuselection:`Settings --> Technical --> Parameters --> System Parameters` to customize the aliases (`mail.catchall.alias` & `mail.bounce.alias`). These types of changes should be completed prior to the database going live. If a customer replies after a change is made then the system will not recognize the old alias, and the reply will not be received." msgstr "" #: ../../content/applications/general/email_communication/email_servers.rst:270 @@ -1612,11 +1981,11 @@ msgid "The two system parameters are as follows:" msgstr "" #: ../../content/applications/general/email_communication/email_servers.rst:287 -msgid "`mail.incoming.limit.period` (60 minutes by default)" +msgid "`mail.gateway.loop.minutes` (120 minutes by default)" msgstr "" #: ../../content/applications/general/email_communication/email_servers.rst:288 -msgid "`mail.incoming.limit.alias` (5 by default)" +msgid "`mail.gateway.loop.threshold` (20 by default)" msgstr "" #: ../../content/applications/general/email_communication/email_servers.rst:290 @@ -1624,379 +1993,47 @@ msgid "Add these fields in Odoo by first enabling :ref:`developer mode `. Then, go to :menuselection:`Settings app --> Technical --> Email section --> Aliases`." msgstr "" -#: ../../content/applications/general/email_communication/email_template.rst:8 -msgid "Creating different templates that are tailored to specific situations lets users choose the right message for the right audience. This increases the quality of the message and the overall engagement rate with the customer." +#: ../../content/applications/general/email_communication/email_servers.rst:313 +msgid "The following system parameter, `mail.catchall.domain.allowed`, set with allowed alias domain values, separated by commas, filters out correctly addressed emails to aliases. Setting the domain(s) for which the alias can create a ticket, lead, opportunity, etc., eliminates false positives where email addresses with only the prefix alias (not the domain) are present." msgstr "" -#: ../../content/applications/general/email_communication/email_template.rst:13 -msgid "Email templates in Odoo use QWeb or XML, which allows for editing emails in their final rendering, making customizations more robust, without having to edit any code whatsoever. This means that Odoo can use a Graphical User Interface (GUI) to edit emails, which edits the backend code. When the received email is read by the end user's program, different formatting and graphics will appear in the final form of it." +#: ../../content/applications/general/email_communication/email_servers.rst:318 +msgid "In some instances, matches have been made in the Odoo database when an email is received with the same alias prefix and a different domain on the incoming email address. This is true in the sender, recipient, and :abbr:`CC (Carbon Copy)` email addresses of an incoming email." msgstr "" -#: ../../content/applications/general/email_communication/email_template.rst:19 -msgid "Access email templates in :ref:`developer mode ` by navigating to :menuselection:`Settings app --> Technical menu --> Email --> Email Templates`." +#: ../../content/applications/general/email_communication/email_servers.rst:323 +msgid "When Odoo receives emails that have the name `commercial` prefix alias in the sender, recipient, or :abbr:`CC (Carbon Copy)` email address(es) (e.g. commercial@gmail.com, commercial@odoo.net), the database falsely treats the email as the full `commercial` alias (with a different domain), and therefore, creates a ticket/lead/opportunity/etc." msgstr "" -#: ../../content/applications/general/email_communication/email_template.rst:23 -msgid "Editing email templates" +#: ../../content/applications/general/email_communication/email_servers.rst:329 +msgid "This alias mismatch issue has been resolved in Odoo 17, however, the `mail.catchall.domain.allowed` system parameter is still used in Odoo 17 for backward compatibility." msgstr "" -#: ../../content/applications/general/email_communication/email_template.rst:25 -msgid "The *powerbox* feature can be used when working with email templates. This feature provides the ability to directly edit the formatting and text in an email template, as well as the ability to add links, buttons, appointment options, or images." +#: ../../content/applications/general/email_communication/email_servers.rst:333 +msgid "To add the `mail.catchall.domain.allowed` system parameter, first, activate the :ref:`developer mode `. Then, go to :menuselection:`Settings app --> Technical --> Parameters section --> System Parameters`. Click :guilabel:`Create`. Then, type in `mail.catchall.domain.allowed` for the :guilabel:`Key` field." msgstr "" -#: ../../content/applications/general/email_communication/email_template.rst:29 -msgid "Additionally, the XML/HTML code of the email template can be edited directly, via the :guilabel:`` icon. Dynamic placeholders (referencing fields within Odoo) are also available for use in the email template." +#: ../../content/applications/general/email_communication/email_servers.rst:338 +msgid "Next, for the :guilabel:`Value` field, add the domain(s) separated by comma(s) (if plural domains). Manually :guilabel:`Save`, and the system parameter takes immediate effect." msgstr "" -#: ../../content/applications/general/email_communication/email_template.rst:34 -msgid "Powerbox" -msgstr "" - -#: ../../content/applications/general/email_communication/email_template.rst:36 -msgid "The *powerbox* feature is an enriched text editor with various formatting, layout, and text options. It can also be used to add XML/HTML features in an email template. The powerbox feature is activated by typing a forward slash `/` in the body of the email template." -msgstr "" - -#: ../../content/applications/general/email_communication/email_template.rst:40 -msgid "When a forward slash `/` is typed in the body of an email template, a drop-down menu appears with the following options:" -msgstr "" - -#: ../../content/applications/general/email_communication/email_template.rst:43 -msgid ":guilabel:`Structure`" -msgstr "" - -#: ../../content/applications/general/email_communication/email_template.rst:45 -msgid ":guilabel:`Bulleted list`: Create a simple bulleted list." -msgstr "" - -#: ../../content/applications/general/email_communication/email_template.rst:46 -msgid ":guilabel:`Numbered list`: Create a list with numbering." -msgstr "" - -#: ../../content/applications/general/email_communication/email_template.rst:47 -msgid ":guilabel:`Checklist`: Track tasks with a checklist." -msgstr "" - -#: ../../content/applications/general/email_communication/email_template.rst:48 -msgid ":guilabel:`Table`: Insert a table." -msgstr "" - -#: ../../content/applications/general/email_communication/email_template.rst:49 -msgid ":guilabel:`Separator`: Insert a horizontal rule separator." -msgstr "" - -#: ../../content/applications/general/email_communication/email_template.rst:50 -msgid ":guilabel:`Quote`: Add a blockquote section." -msgstr "" - -#: ../../content/applications/general/email_communication/email_template.rst:51 -msgid ":guilabel:`Code`: Add a code section." -msgstr "" - -#: ../../content/applications/general/email_communication/email_template.rst:52 -msgid ":guilabel:`2 columns`: Convert into two columns." -msgstr "" - -#: ../../content/applications/general/email_communication/email_template.rst:53 -msgid ":guilabel:`3 columns`: Convert into three columns." -msgstr "" - -#: ../../content/applications/general/email_communication/email_template.rst:54 -msgid ":guilabel:`4 columns`: Convert into four columns." -msgstr "" - -#: ../../content/applications/general/email_communication/email_template.rst:56 -msgid ":guilabel:`Format`" -msgstr "" - -#: ../../content/applications/general/email_communication/email_template.rst:58 -msgid ":guilabel:`Heading 1`: Big section heading." -msgstr "" - -#: ../../content/applications/general/email_communication/email_template.rst:59 -msgid ":guilabel:`Heading 2`: Medium section heading." -msgstr "" - -#: ../../content/applications/general/email_communication/email_template.rst:60 -msgid ":guilabel:`Heading 3`: Small section heading." -msgstr "" - -#: ../../content/applications/general/email_communication/email_template.rst:61 -msgid ":guilabel:`Switch direction`: Switch the text's direction." -msgstr "" - -#: ../../content/applications/general/email_communication/email_template.rst:62 -msgid ":guilabel:`Text`: Paragraph block." -msgstr "" - -#: ../../content/applications/general/email_communication/email_template.rst:64 -msgid ":guilabel:`Media`" -msgstr "" - -#: ../../content/applications/general/email_communication/email_template.rst:66 -msgid ":guilabel:`Image`: Insert an image." -msgstr "" - -#: ../../content/applications/general/email_communication/email_template.rst:67 -msgid ":guilabel:`Article`: Link an article." -msgstr "" - -#: ../../content/applications/general/email_communication/email_template.rst:69 -msgid ":guilabel:`Navigation`" -msgstr "" - -#: ../../content/applications/general/email_communication/email_template.rst:71 -msgid ":guilabel:`Link`: Add a link." -msgstr "" - -#: ../../content/applications/general/email_communication/email_template.rst:72 -msgid ":guilabel:`Button`: Add a button." -msgstr "" - -#: ../../content/applications/general/email_communication/email_template.rst:73 -msgid ":guilabel:`Appointment`: Add a specific appointment." -msgstr "" - -#: ../../content/applications/general/email_communication/email_template.rst:74 -msgid ":guilabel:`Calendar`: Schedule an appointment." -msgstr "" - -#: ../../content/applications/general/email_communication/email_template.rst:76 -msgid ":guilabel:`Widgets`" -msgstr "" - -#: ../../content/applications/general/email_communication/email_template.rst:78 -msgid ":guilabel:`3 Stars`: Insert a rating over three stars." -msgstr "" - -#: ../../content/applications/general/email_communication/email_template.rst:79 -msgid ":guilabel:`5 Stars`: Insert a rating over five stars." -msgstr "" - -#: ../../content/applications/general/email_communication/email_template.rst:81 -msgid ":guilabel:`Basic Blocks`" -msgstr "" - -#: ../../content/applications/general/email_communication/email_template.rst:83 -msgid ":guilabel:`Signature`: Insert your signature." -msgstr "" - -#: ../../content/applications/general/email_communication/email_template.rst:85 -msgid ":guilabel:`Marketing Tools`" -msgstr "" - -#: ../../content/applications/general/email_communication/email_template.rst:87 -msgid ":guilabel:`Dynamic Placeholders`: Insert personalized content." -msgstr "" - -#: ../../content/applications/general/email_communication/email_template.rst:90 -msgid "To use any of these options, click on the desired feature from the powerbox drop-down menu. To format existing text with a text-related option (e.g. :guilabel:`Heading 1`, :guilabel:`Switch direction`, etc.), highlight the text, then type in the activator key (forward slash) `/`, and select the desired option from the drop-down menu." -msgstr "" - -#: ../../content/applications/general/email_communication/email_template.rst:0 -msgid "Powerbox feature in the email template." -msgstr "" - -#: ../../content/applications/general/email_communication/email_template.rst:100 -msgid ":ref:`Using dynamic placeholders `" -msgstr "" - -#: ../../content/applications/general/email_communication/email_template.rst:103 -msgid "XML/HTML code editor" -msgstr "" - -#: ../../content/applications/general/email_communication/email_template.rst:105 -msgid "To access the XML/HTML editor for an email template, first enter :ref:`developer mode `. Then, click the :guilabel:`` icon in the upper-right corner of the template, and proceed to edit the XML/HTML. To return to the standard text editor, click the :guilabel:`` icon again." -msgstr "" - -#: ../../content/applications/general/email_communication/email_template.rst:-1 -msgid "HTML editor in the email template." -msgstr "" - -#: ../../content/applications/general/email_communication/email_template.rst:115 -msgid "The XML/HTML editor should be accessed with caution as this is the backend code of the template. Editing the code can cause the email template to break immediately or when upgrading the database." -msgstr "" - -#: ../../content/applications/general/email_communication/email_template.rst:122 -msgid "Dynamic placeholders" -msgstr "" - -#: ../../content/applications/general/email_communication/email_template.rst:124 -msgid "*Dynamic placeholders* reference certain fields within the Odoo database to produce unique data in the email template." -msgstr "" - -#: ../../content/applications/general/email_communication/email_template.rst:128 -msgid "Many companies like to customize their emails with a personalized piece of customer information to grab attention. This can be accomplished in Odoo by referencing a field within a model by inserting a dynamic placeholder. For example, a customer's name can be referenced in the email from the :guilabel:`Customer` field on the :guilabel:`Sales Order` model. The dynamic placeholder for this field is: `{{ object.partner_id }}`." -msgstr "" - -#: ../../content/applications/general/email_communication/email_template.rst:134 -msgid "Dynamic placeholders are encoded to display fields from within the database. Dynamic placeholders can be used in the :guilabel:`Body` (:guilabel:`Content` Tab) of the email template. They can also be used in the fields present in the :guilabel:`Email Configuration` tab, the :guilabel:`Subject` of the email, and the :guilabel:`Language`." -msgstr "" - -#: ../../content/applications/general/email_communication/email_template.rst:139 -msgid "To use the dynamic placeholders in the :guilabel:`Body` of an email open the **powerbox** feature by typing in `/` into the body of the email template under the :guilabel:`Content` tab. Scroll to the bottom of the options list, to :guilabel:`Marketing Tools`. Next, select :guilabel:`Dynamic Placeholder`. Then select the dynamic placeholder from a list of available options and follow the prompts to configure it with the desired corresponding Odoo field. Each dynamic placeholder will vary in configuration." -msgstr "" - -#: ../../content/applications/general/email_communication/email_template.rst:-1 -msgid "Using dynamic placeholders in an email template." -msgstr "" - -#: ../../content/applications/general/email_communication/email_template.rst:151 -msgid "Each unique combination of :guilabel:`Fields`, :guilabel:`Sub-models` and :guilabel:`Sub-fields` creates a different dynamic placeholder. Imagine it as a combination to the field that is being created." -msgstr "" - -#: ../../content/applications/general/email_communication/email_template.rst:155 -msgid "To search the available fields, simply type in the front-end name (on user-interface) of the field in the search. This will find a result from all of the available fields for the model that the email template is created for." -msgstr "" - -#: ../../content/applications/general/email_communication/email_template.rst:160 -msgid "Customizing email templates are out of the scope of Odoo Support." -msgstr "" - -#: ../../content/applications/general/email_communication/email_template.rst:163 -msgid "Rich text editor" -msgstr "" - -#: ../../content/applications/general/email_communication/email_template.rst:165 -msgid "A rich text editor toolbar can be accessed by highlighting text in the email template. This can be used to change the heading, font size/style, color, add a list type, or a link." -msgstr "" - -#: ../../content/applications/general/email_communication/email_template.rst:-1 -msgid "Rich text editor in the email template." -msgstr "" - -#: ../../content/applications/general/email_communication/email_template.rst:173 -msgid "Resetting email templates" -msgstr "" - -#: ../../content/applications/general/email_communication/email_template.rst:175 -msgid "Should the email template not work because the code has been altered it can be reset to restore it back to the out-of-box default template. Simply click on the :guilabel:`Reset Template` button in the upper left-hand of the screen and the template will be reset." -msgstr "" - -#: ../../content/applications/general/email_communication/email_template.rst:-1 -msgid "Resetting the email template." -msgstr "" - -#: ../../content/applications/general/email_communication/email_template.rst:184 -msgid "Default reply on email templates" -msgstr "" - -#: ../../content/applications/general/email_communication/email_template.rst:186 -msgid "Under the :guilabel:`Email Configuration` tab on an email template, there is a :guilabel:`Reply To` field. In this field, add email addresses to which replies are redirected when sending emails en masse using this template." -msgstr "" - -#: ../../content/applications/general/email_communication/email_template.rst:191 -msgid "Add multiple email addresses by adding a comma `,` between the addresses or dynamic placeholders." -msgstr "" - -#: ../../content/applications/general/email_communication/email_template.rst:-1 -msgid "Reply-to field on template." -msgstr "" - -#: ../../content/applications/general/email_communication/email_template.rst:198 -msgid "The :guilabel:`Reply To` field is **only** used for mass mailing (sending emails in bulk). Bulk emails can be sent in almost every Odoo application that has a list view option." -msgstr "" - -#: ../../content/applications/general/email_communication/email_template.rst:201 -msgid "To send mass mails, while in :guilabel:`list` view, check the boxes next to the desired records where the emails are to be sent, click the :guilabel:`Action` button (represented by a :guilabel:`⚙️ (gear)` icon), and select the desired email option from the :guilabel:`Action` drop-down menu. Email options can vary by the particular list view and application." -msgstr "" - -#: ../../content/applications/general/email_communication/email_template.rst:206 -msgid "If it is possible to send an email, a mail composer pop-up window appears, with values that can be defined and customized. This option will be available on the :guilabel:`Action` button on pages where emails can be sent in bulk---for example, on the :guilabel:`Customers` page of the CRM app. This action occurs throughout the Odoo database." -msgstr "" - -#: ../../content/applications/general/email_communication/email_template.rst:-1 -msgid "Email composer in mass mailing mode with reply-to highlighted." -msgstr "" - -#: ../../content/applications/general/email_communication/email_template.rst:216 -msgid "Transactional emails and corresponding URLs" -msgstr "" - -#: ../../content/applications/general/email_communication/email_template.rst:218 -msgid "In Odoo, multiple events can trigger the sending of automated emails. These emails are known as *transactional emails*, and sometimes contain links redirecting to the Odoo database." -msgstr "" - -#: ../../content/applications/general/email_communication/email_template.rst:221 -msgid "By default, links generated by the database use the dynamic `web.base.url` key defined in the system parameters. For more information about this, see :ref:`system parameters `." -msgstr "" - -#: ../../content/applications/general/email_communication/email_template.rst:225 -msgid "If the *Website* application is not installed, the `web.base.url` key will always be the default parameter used to generate all the links." -msgstr "" - -#: ../../content/applications/general/email_communication/email_template.rst:229 -msgid "The `web.base.url` key can only have a single value, meaning that, in a multi-website or multi-company database environment, even if there is a specific domain name for each website, the links generated to share a document (or the links within a transactional email) may remain the same, regardless of which website/company is related to the sending of the email/document." -msgstr "" - -#: ../../content/applications/general/email_communication/email_template.rst:235 -msgid "If the :guilabel:`Value` of the :guilabel:`web.base.url` system parameter is equal to `https://www.mycompany.com` and there are two separate companies in Odoo with different website URLs: `https://www.mycompany2.com` and `https://www.mycompany1.com`, the links created by Odoo to share a document, or send a transactional email, come from the domain: `https://www.mycompany.com`, regardless of which company sends the document or email." -msgstr "" - -#: ../../content/applications/general/email_communication/email_template.rst:241 -msgid "This is not always the case, as some Odoo applications (*eCommerce*, for example) have a link established in the database with the *Website* application. In that case, if a specific domain is defined for the website, the URL generated in the email template uses the domain defined on the corresponding website of the company." -msgstr "" - -#: ../../content/applications/general/email_communication/email_template.rst:247 -msgid "When a customer makes a purchase on an Odoo *eCommerce* website, the order has an established link with that website. As a result, the links in the confirmation email sent to the customer use the domain name for that specific website." -msgstr "" - -#: ../../content/applications/general/email_communication/email_template.rst:252 -msgid "A document shared using the *Documents* application will **always** use the `web.base.url` key, as the document shared is not associated with any particular website. This means that the URL will always be the same (the `web.base.url` key value), no matter what company it's shared from. This is a known limitation." -msgstr "" - -#: ../../content/applications/general/email_communication/email_template.rst:257 -msgid "For more information about how to configure domains, check out the :doc:`domain name documentation `." -msgstr "" - -#: ../../content/applications/general/email_communication/email_template.rst:261 -msgid "Updating translations within email templates" -msgstr "" - -#: ../../content/applications/general/email_communication/email_template.rst:263 -msgid "In Odoo, email templates are automatically translated for all users in the database for all of the languages installed. Changing the translations shouldn't be necessary. However, if for a specific reason, some of the translations need to be changed, it can be done." -msgstr "" - -#: ../../content/applications/general/email_communication/email_template.rst:268 -msgid "Like any modification in the code, if translation changes are not done correctly (for example, modifications leading to bad syntax), it can break the template, and as a result, the template will appear blank." -msgstr "" - -#: ../../content/applications/general/email_communication/email_template.rst:272 -msgid "In order to edit translations, first enter :ref:`developer mode `. Then, on the email template, click on the :guilabel:`Edit` button, and then click on the language button, represented by the initials of the language currently being used (e.g. :guilabel:`EN` for English)." -msgstr "" - -#: ../../content/applications/general/email_communication/email_template.rst:-1 -msgid "Edit the language of a template." -msgstr "" - -#: ../../content/applications/general/email_communication/email_template.rst:281 -msgid "If there aren't multiple languages installed and activated in the database, or if the user does not have administration access rights, the language button will not appear." -msgstr "" - -#: ../../content/applications/general/email_communication/email_template.rst:284 -msgid "A pop-up window with the different languages installed on the database appears. From this pop-up, editing of translations is possible. When the desired changes have been made, click the :guilabel:`Save` button to save the changes." -msgstr "" - -#: ../../content/applications/general/email_communication/email_template.rst:-1 -msgid "Translation of the body of the Appointment Booked template." -msgstr "" - -#: ../../content/applications/general/email_communication/email_template.rst:293 -msgid "When editing the translations, the default language set in the database appears in **bold**." +#: ../../content/applications/general/email_communication/email_servers.rst:-1 +msgid "mail.catchall.domain.allowed system parameter set with key and value highlighted." msgstr "" #: ../../content/applications/general/email_communication/faq.rst:3 @@ -2271,1090 +2308,3531 @@ msgstr "" msgid "The bounce system parameter needs to be set in the technical settings in order for the database to correctly receive bounce messages. To access this setting, go to :menuselection:`Settings app --> Technical menu --> Parameters --> System Parameters`. Then select the parameter name :guilabel:`mail.bounce.alias` and set the value to `bounce` if it isn't already set." msgstr "" -#: ../../content/applications/general/export_import_data.rst:3 -msgid "Export and import data" +#: ../../content/applications/general/email_communication/google_oauth.rst:3 +msgid "Connect Gmail to Odoo using Google OAuth" msgstr "" -#: ../../content/applications/general/export_import_data.rst:8 -msgid "Export data from Odoo" +#: ../../content/applications/general/email_communication/google_oauth.rst:5 +msgid "Odoo is compatible with Google's OAuth for Gmail. In order to send secure emails from a custom domain, all that is required is to configure a few settings on Google's *Workspace* platform, as well as on the back end of the Odoo database. This configuration works by using either a personal email address or an address created by a custom domain." msgstr "" -#: ../../content/applications/general/export_import_data.rst:10 -msgid "When working with a database, it sometimes is necessary to export your data in a distinct file. Doing so can help to do reporting over your activities (even if Odoo offers a precise and easy reporting tool with each available application)." +#: ../../content/applications/general/email_communication/google_oauth.rst:11 +msgid "For more information, visit `Google's documentation `_ on setting up OAuth." msgstr "" -#: ../../content/applications/general/export_import_data.rst:14 -msgid "With Odoo, you can export the values from any field in any record. To do so, activate the list view on the items that need to be exported, click on *Action*, and, then, on *Export*." +#: ../../content/applications/general/email_communication/google_oauth.rst:15 +msgid ":doc:`/applications/general/users/google`" msgstr "" -#: ../../content/applications/general/export_import_data.rst:-1 -msgid "view of the different things to enable/click to export data" +#: ../../content/applications/general/email_communication/google_oauth.rst:16 +#: ../../content/applications/general/users/google.rst:18 +msgid ":doc:`/applications/productivity/calendar/google`" msgstr "" -#: ../../content/applications/general/export_import_data.rst:22 -msgid "Pretty simple, this action still comes with some specificities. In fact, when clicking on *Export*, a pop-up window appears with several options for the data to export:" +#: ../../content/applications/general/email_communication/google_oauth.rst:19 +msgid "Setup in Google" msgstr "" -#: ../../content/applications/general/export_import_data.rst:-1 -msgid "overview of all the options to take into account when exporting data in Odoo" +#: ../../content/applications/general/email_communication/google_oauth.rst:22 +msgid "Create a new project" msgstr "" -#: ../../content/applications/general/export_import_data.rst:30 -msgid "With the *I want to update data* option ticked, the system only shows the fields which can be imported. This is very helpful in case you want to update existing records. Basically, this works like a filter. Leaving the box unticked gives way more field options because it shows all the fields, not just the ones which can be imported." +#: ../../content/applications/general/email_communication/google_oauth.rst:24 +msgid "To get started, go to the `Google API Console `_. Log in with your *Google Workspace* account if you have one, otherwise log in with your personal Gmail account (this should match the email address you want to configure in Odoo)." msgstr "" -#: ../../content/applications/general/export_import_data.rst:36 -msgid "When exporting, you can choose between two formats: .csv and .xls. With .csv, items are separated with a comma, while .xls holds information about all the worksheets in a file, including both content and formatting." +#: ../../content/applications/general/email_communication/google_oauth.rst:28 +msgid "After that, click on :guilabel:`Create Project`, located on the far right of the :guilabel:`OAuth consent screen`. If a project has already been created in this account, then the :guilabel:`New Project` option will be located on the top right under the :guilabel:`Select a project` drop-down menu." msgstr "" -#: ../../content/applications/general/export_import_data.rst:39 -msgid "Those are the items you may want to export. Use the arrows to display more sub-field options. Of course, you can use the search bar to find specific fields more easily. To use the search option more efficiently, display all the fields by clicking on all the arrows!" +#: ../../content/applications/general/email_communication/google_oauth.rst:33 +msgid "On the :menuselection:`New Project` screen, rename the :guilabel:`Project name` to `Odoo` and browse for the :guilabel:`Location`. Set the :guilabel:`Location` as the *Google Workspace organization*. If you are using a personal Gmail account, then leave the :guilabel:`Location` as :guilabel:`No Organization`." msgstr "" -#: ../../content/applications/general/export_import_data.rst:44 -msgid "The + button is there to add fields to the \"to export\" list." +#: ../../content/applications/general/email_communication/google_oauth.rst:-1 +msgid "Project Name and Location for Google OAuth." msgstr "" -#: ../../content/applications/general/export_import_data.rst:45 -msgid "The \"handles\" next to the selected fields allow you to move the fields up and down to change the order in which they must be displayed in the exported file." +#: ../../content/applications/general/email_communication/google_oauth.rst:42 +msgid "Click on :guilabel:`Create` to finish this step." msgstr "" -#: ../../content/applications/general/export_import_data.rst:48 -msgid "The trashcan is there if you need to remove fields." +#: ../../content/applications/general/email_communication/google_oauth.rst:45 +#: ../../content/applications/general/users/google.rst:48 +msgid "OAuth consent screen" msgstr "" -#: ../../content/applications/general/export_import_data.rst:49 -msgid "For recurring reports, it might be interesting to save export presets. Select all the needed ones and click on the template bar. There, click on *New template* and give a name to yours. The next time you need to export the same list, simply select the related template." +#: ../../content/applications/general/email_communication/google_oauth.rst:47 +msgid "If the page doesn't redirect to the :menuselection:`User Type` options, click on :guilabel:`OAuth consent screen` in the left menu." msgstr "" -#: ../../content/applications/general/export_import_data.rst:56 -msgid "It’s good to keep the field’s external identifier in mind. For example, *Related Company* is equal to *parent_id*. Doing so helps export only what you would like to import next." +#: ../../content/applications/general/email_communication/google_oauth.rst:50 +msgid "Under :guilabel:`User Type` options, select the appropriate :guilabel:`User Type`, and then click on :guilabel:`Create` again, which will finally navigate to the :menuselection:`Edit app registration` page." msgstr "" -#: ../../content/applications/general/export_import_data.rst:63 -msgid "Import data into Odoo" +#: ../../content/applications/general/email_communication/google_oauth.rst:55 +#: ../../content/applications/general/users/google.rst:64 +msgid "*Personal* Gmail Accounts are only allowed to be **External** User Type, which means Google may require an approval, or for *Scopes* to be added on. However, using a *Google WorkSpace* account allows for **Internal** User Type to be used." msgstr "" -#: ../../content/applications/general/export_import_data.rst:66 -msgid "How to start" +#: ../../content/applications/general/email_communication/google_oauth.rst:59 +#: ../../content/applications/general/users/google.rst:68 +msgid "Note, as well, that while the API connection is in the *External* testing mode, then no approval is necessary from Google. User limits in this testing mode is set to 100 users." msgstr "" -#: ../../content/applications/general/export_import_data.rst:68 -msgid "You can import data on any Odoo's business object using either Excel (.xlsx) or CSV (.csv) formats: contacts, products, bank statements, journal entries and even orders!" +#: ../../content/applications/general/email_communication/google_oauth.rst:63 +msgid "Edit app registration" msgstr "" -#: ../../content/applications/general/export_import_data.rst:72 -msgid "Open the view of the object you want to populate and click on :menuselection:`Favorites --> Import records`." +#: ../../content/applications/general/email_communication/google_oauth.rst:65 +msgid "Next we will configure the app registration of the project." msgstr "" -#: ../../content/applications/general/export_import_data.rst:78 -msgid "There you are provided with templates you can easily populate with your own data. Such templates can be imported in one click; The data mapping is already done." +#: ../../content/applications/general/email_communication/google_oauth.rst:67 +msgid "On the :guilabel:`OAuth consent screen` step, under the :guilabel:`App information` section, enter `Odoo` in the :guilabel:`App name` field. Select the organization's email address under the :guilabel:`User support` email field." msgstr "" -#: ../../content/applications/general/export_import_data.rst:83 -msgid "How to adapt the template" +#: ../../content/applications/general/email_communication/google_oauth.rst:71 +msgid "Next, under :menuselection:`App Domain --> Authorized domains`, click on :guilabel:`Add Domain` and enter `odoo.com`." msgstr "" -#: ../../content/applications/general/export_import_data.rst:85 -msgid "Add, remove and sort columns to fit at best your data structure." +#: ../../content/applications/general/email_communication/google_oauth.rst:74 +msgid "After that, under the :guilabel:`Developer contact information` section, enter the organization's email address. Google uses this email address to notify the organization about any changes to your project." msgstr "" -#: ../../content/applications/general/export_import_data.rst:86 -msgid "We advise to not remove the **ID** one (see why in the next section)." +#: ../../content/applications/general/email_communication/google_oauth.rst:78 +msgid "Next, click on the :guilabel:`Save and Continue` button. Then, skip the :menuselection:`Scopes` page by scrolling to the bottom and clicking on :guilabel:`Save and Continue`." msgstr "" -#: ../../content/applications/general/export_import_data.rst:87 -#: ../../content/applications/general/export_import_data.rst:376 -msgid "Set a unique ID to every single record by dragging down the ID sequencing." +#: ../../content/applications/general/email_communication/google_oauth.rst:81 +msgid "If continuing in testing mode (External), add the email addresses being configured under the :guilabel:`Test users` step, by clicking on :guilabel:`Add Users`, and then the :guilabel:`Save and Continue` button. A summary of the app registration appears." msgstr "" -#: ../../content/applications/general/export_import_data.rst:92 -msgid "When you add a new column, Odoo might not be able to map it automatically if its label doesn't fit any field in Odoo. Don't worry! You can map new columns manually when you test the import. Search the list for the corresponding field." +#: ../../content/applications/general/email_communication/google_oauth.rst:85 +msgid "Finally, scroll to the bottom and click on :guilabel:`Back to Dashboard` to finish setting up the project." msgstr "" -#: ../../content/applications/general/export_import_data.rst:100 -msgid "Then, use this field's label in your file in order to make it work straight on the very next time." +#: ../../content/applications/general/email_communication/google_oauth.rst:89 +msgid "Create Credentials" msgstr "" -#: ../../content/applications/general/export_import_data.rst:104 -msgid "How to import from another application" +#: ../../content/applications/general/email_communication/google_oauth.rst:91 +msgid "Now that the project is set up, credentials should be created, which includes the *Client ID* and *Client Secret*. First, click on :guilabel:`Credentials` in the left sidebar menu." msgstr "" -#: ../../content/applications/general/export_import_data.rst:106 -msgid "In order to re-create relationships between different records, you should use the unique identifier from the original application and map it to the **ID** (External ID) column in Odoo. When you import another record that links to the first one, use **XXX/ID** (XXX/External ID) to the original unique identifier. You can also find this record using its name but you will be stuck if at least 2 records have the same name." +#: ../../content/applications/general/email_communication/google_oauth.rst:94 +msgid "Then, click on :guilabel:`Create Credentials` in the top menu and select :guilabel:`OAuth client ID` from the dropdown menu." msgstr "" -#: ../../content/applications/general/export_import_data.rst:114 -msgid "The **ID** will also be used to update the original import if you need to re-import modified data later, it's thus good practice to specify it whenever possible." +#: ../../content/applications/general/email_communication/google_oauth.rst:97 +msgid "Under :guilabel:`Application Type`, select :guilabel:`Web Application` from the dropdown menu." msgstr "" -#: ../../content/applications/general/export_import_data.rst:120 -msgid "I cannot find the field I want to map my column to" +#: ../../content/applications/general/email_communication/google_oauth.rst:98 +msgid "In the :guilabel:`Name` field, enter `Odoo`." msgstr "" -#: ../../content/applications/general/export_import_data.rst:122 -msgid "Odoo tries to find with some heuristic, based on the first ten lines of the files, the type of field for each column inside your file. For example if you have a column only containing numbers, only the fields that are of type *Integer* will be displayed for you to choose from. While this behavior might be good and easy for most cases, it is also possible that it goes wrong or that you want to map your column to a field that is not proposed by default." +#: ../../content/applications/general/email_communication/google_oauth.rst:99 +msgid "Under the :guilabel:`Authorized redirect URIs` label, click the button :guilabel:`ADD URI`, and then input `https://yourdbname.odoo.com/google_gmail/confirm` in the :guilabel:`URIs 1` field. Be sure to replace the *yourdbname* part of the URL with the actual Odoo database name." msgstr "" -#: ../../content/applications/general/export_import_data.rst:131 -msgid "If that happens, you just have to check the ** Show fields of relation fields (advanced)** option, you will then be able to choose from the complete list of fields for each column." +#: ../../content/applications/general/email_communication/google_oauth.rst:102 +msgid "Next, click on :guilabel:`Create` to generate an OAuth :guilabel:`Client ID` and :guilabel:`Client Secret`. Finally, copy each generated value for later use when configuring in Odoo, and then navigate to the Odoo database." msgstr "" -#: ../../content/applications/general/export_import_data.rst:139 -msgid "Where can I change the date import format?" +#: ../../content/applications/general/email_communication/google_oauth.rst:-1 +msgid "Client ID and Client Secret for Google OAuth." msgstr "" -#: ../../content/applications/general/export_import_data.rst:141 -msgid "Odoo can automatically detect if a column is a date, and it will try to guess the date format from a set of most commonly used date formats. While this process can work for many date formats, some date formats will not be recognized. This can cause confusion due to day-month inversions; it is difficult to guess which part of a date format is the day and which part is the month in a date such as '01-03-2016'." +#: ../../content/applications/general/email_communication/google_oauth.rst:114 +msgid "Enter Google Credentials" msgstr "" -#: ../../content/applications/general/export_import_data.rst:147 -msgid "To view which date format Odoo has found from your file you can check the **Date Format** that is shown when clicking on **Options** under the file selector. If this format is incorrect you can change it to your liking using the *ISO 8601* to define the format." +#: ../../content/applications/general/email_communication/google_oauth.rst:116 +msgid "First, open Odoo and navigate to the :guilabel:`Apps` module. Then, remove the :guilabel:`Apps` filter from the search bar and type in `Google`. Install the module called :guilabel:`Google Gmail`." msgstr "" -#: ../../content/applications/general/export_import_data.rst:152 -msgid "If you are importing an excel (.xls, .xlsx) file, you can use date cells to store dates as the display of dates in excel is different from the way it is stored. That way you will be sure that the date format is correct in Odoo whatever your locale date format is." +#: ../../content/applications/general/email_communication/google_oauth.rst:120 +msgid "Next, navigate to :menuselection:`Settings --> General Settings`, and under the :guilabel:`Discuss` section, ensure that the checkbox for :guilabel:`Custom Email Servers` or :guilabel:`External Email Servers` is checked. This populates a new option for :guilabel:`Gmail Credentials` or :guilabel:`Use a Gmail Sever`. Then, copy and paste the respective values into the :guilabel:`Client ID` and :guilabel:`Client Secret` fields and :guilabel:`Save` the settings." msgstr "" -#: ../../content/applications/general/export_import_data.rst:157 -msgid "Can I import numbers with currency sign (e.g.: $32.00)?" +#: ../../content/applications/general/email_communication/google_oauth.rst:129 +msgid "To configure the external Gmail account, return to the top of the :guilabel:`Custom Email Servers` setting and then click the :guilabel:`Outgoing Email Servers` link." msgstr "" -#: ../../content/applications/general/export_import_data.rst:159 -msgid "Yes, we fully support numbers with parenthesis to represent negative sign as well as numbers with currency sign attached to them. Odoo also automatically detect which thousand/decimal separator you use (you can change those under **options**). If you use a currency symbol that is not known to Odoo, it might not be recognized as a number though and it will crash." +#: ../../content/applications/general/email_communication/google_oauth.rst:-1 +#: ../../content/applications/general/email_communication/google_oauth.rst:-1 +msgid "Configure Outgoing Email Servers in Odoo." msgstr "" -#: ../../content/applications/general/export_import_data.rst:164 -msgid "Examples of supported numbers (using thirty-two thousands as an example):" +#: ../../content/applications/general/email_communication/google_oauth.rst:136 +msgid "Then, click on :guilabel:`New` or :guilabel:`Create` to create a new email server, and fill in the :guilabel:`Name`, :guilabel:`Description`, and the email :guilabel:`Username` (if required)." msgstr "" -#: ../../content/applications/general/export_import_data.rst:166 -msgid "32.000,00" +#: ../../content/applications/general/email_communication/google_oauth.rst:139 +msgid "Next, click on :guilabel:`Gmail OAuth Authentication` or :guilabel:`Gmail` (under the :guilabel:`Authenticate with` or :guilabel:`Connection` section). Finally, click on :guilabel:`Connect your Gmail Account`." msgstr "" -#: ../../content/applications/general/export_import_data.rst:167 -msgid "32000,00" +#: ../../content/applications/general/email_communication/google_oauth.rst:143 +msgid "A new window labeled :guilabel:`Google` opens to complete the authorization process. Select the appropriate email address that is being configured in Odoo." msgstr "" -#: ../../content/applications/general/export_import_data.rst:168 -msgid "32,000.00" +#: ../../content/applications/general/email_communication/google_oauth.rst:146 +msgid "If the email address is a personal account, then an extra step pops up, so click :guilabel:`Continue` to allow the verification and connect the Gmail account to Odoo." msgstr "" -#: ../../content/applications/general/export_import_data.rst:169 -msgid "-32000.00" +#: ../../content/applications/general/email_communication/google_oauth.rst:149 +msgid "Then, allow Odoo to access the Google account by clicking on :guilabel:`Continue` or :guilabel:`Allow`. After that, the page navigates back to the newly configured outgoing email server in Odoo. The configuration automatically loads the token in Odoo, and a tag stating :guilabel:`Gmail Token Valid` appears in green." msgstr "" -#: ../../content/applications/general/export_import_data.rst:170 -msgid "(32000.00)" +#: ../../content/applications/general/email_communication/google_oauth.rst:158 +msgid "Finally, :guilabel:`Test the Connection`. A confirmation message should appear. The Odoo database can now send safe, secure emails through Google using OAuth authentication." msgstr "" -#: ../../content/applications/general/export_import_data.rst:171 -msgid "$ 32.000,00" +#: ../../content/applications/general/email_communication/google_oauth.rst:162 +msgid "Google OAuth FAQ" msgstr "" -#: ../../content/applications/general/export_import_data.rst:172 -msgid "(32000.00 €)" +#: ../../content/applications/general/email_communication/google_oauth.rst:165 +msgid "Production VS Testing Publishing Status" msgstr "" -#: ../../content/applications/general/export_import_data.rst:174 -msgid "Example that will not work:" +#: ../../content/applications/general/email_communication/google_oauth.rst:167 +msgid "Choosing :guilabel:`Production` as the :guilabel:`Publishing Status` (instead of :guilabel:`Testing`) will display the following warning message:" msgstr "" -#: ../../content/applications/general/export_import_data.rst:176 -msgid "ABC 32.000,00" +#: ../../content/applications/general/email_communication/google_oauth.rst:-1 +msgid "OAuth is Limited to 100 Sensitive Scope Logins." msgstr "" -#: ../../content/applications/general/export_import_data.rst:177 -msgid "$ (32.000,00)" +#: ../../content/applications/general/email_communication/google_oauth.rst:174 +msgid "To correct this warning, navigate to the `Google API Platform `_. If the :guilabel:`Publishing status` is :guilabel:`In Production`, click :guilabel:`Back to Testing` to correct the issue." msgstr "" -#: ../../content/applications/general/export_import_data.rst:180 -msgid "What can I do when the Import preview table isn't displayed correctly?" +#: ../../content/applications/general/email_communication/google_oauth.rst:179 +msgid "No Test Users Added" msgstr "" -#: ../../content/applications/general/export_import_data.rst:182 -msgid "By default the Import preview is set on commas as field separators and quotation marks as text delimiters. If your csv file does not have these settings, you can modify the File Format Options (displayed under the Browse CSV file bar after you select your file)." +#: ../../content/applications/general/email_communication/google_oauth.rst:181 +msgid "If no test users are added to the OAuth consent screen, then a 403 access denied error will populate." msgstr "" -#: ../../content/applications/general/export_import_data.rst:186 -msgid "Note that if your CSV file has a tabulation as separator, Odoo will not detect the separations. You will need to change the file format options in your spreadsheet application. See the following question." +#: ../../content/applications/general/email_communication/google_oauth.rst:-1 +msgid "403 Access Denied Error." msgstr "" -#: ../../content/applications/general/export_import_data.rst:191 -msgid "How can I change the CSV file format options when saving in my spreadsheet application?" +#: ../../content/applications/general/email_communication/google_oauth.rst:188 +msgid "To correct this error, return to the :guilabel:`OAuth consent screen` under :guilabel:`APIs & Services` and add test user(s) to the app. Add the email that you are configuring in Odoo." msgstr "" -#: ../../content/applications/general/export_import_data.rst:193 -msgid "If you edit and save CSV files in spreadsheet applications, your computer's regional settings will be applied for the separator and delimiter. We suggest you use OpenOffice or LibreOffice Calc as they will allow you to modify all three options (in :menuselection:`'Save As' dialog box --> Check the box 'Edit filter settings' --> Save`)." +#: ../../content/applications/general/email_communication/google_oauth.rst:192 +msgid "Gmail Module not updated" msgstr "" -#: ../../content/applications/general/export_import_data.rst:198 -msgid "Microsoft Excel will allow you to modify only the encoding when saving (in :menuselection:`'Save As' dialog box --> click 'Tools' dropdown list --> Encoding tab`)." +#: ../../content/applications/general/email_communication/google_oauth.rst:194 +msgid "If the *Google Gmail* module in Odoo has not been updated to the latest version, then a :guilabel:`Forbidden` error message populates." msgstr "" -#: ../../content/applications/general/export_import_data.rst:202 -msgid "What's the difference between Database ID and External ID?" +#: ../../content/applications/general/email_communication/google_oauth.rst:-1 +msgid "Forbidden you don't have the permission to access the requested resource." msgstr "" -#: ../../content/applications/general/export_import_data.rst:204 -msgid "Some fields define a relationship with another object. For example, the country of a contact is a link to a record of the 'Country' object. When you want to import such fields, Odoo will have to recreate links between the different records. To help you import such fields, Odoo provides three mechanisms. You must use one and only one mechanism per field you want to import." +#: ../../content/applications/general/email_communication/google_oauth.rst:201 +msgid "To correct this error, go to the :menuselection:`Apps` module and clear out the search terms. Then, search for `Gmail` or `Google` and upgrade the :guilabel:`Google Gmail` module. Finally, click on the three dots on the upper right of the module and select :guilabel:`Upgrade`." msgstr "" -#: ../../content/applications/general/export_import_data.rst:209 -msgid "For example, to reference the country of a contact, Odoo proposes you 3 different fields to import:" +#: ../../content/applications/general/email_communication/google_oauth.rst:206 +msgid "Application Type" msgstr "" -#: ../../content/applications/general/export_import_data.rst:211 -msgid "Country: the name or code of the country" +#: ../../content/applications/general/email_communication/google_oauth.rst:208 +msgid "When creating the credentials (OAuth *Client ID* and *Client Secret*), if :guilabel:`Desktop App` is selected for the :guilabel:`Application Type`, an :guilabel:`Authorization Error` appears." msgstr "" -#: ../../content/applications/general/export_import_data.rst:212 -msgid "Country/Database ID: the unique Odoo ID for a record, defined by the ID postgresql column" +#: ../../content/applications/general/email_communication/google_oauth.rst:-1 +msgid "Error 400 Redirect URI Mismatch." msgstr "" -#: ../../content/applications/general/export_import_data.rst:213 -msgid "Country/External ID: the ID of this record referenced in another application (or the .XML file that imported it)" +#: ../../content/applications/general/email_communication/google_oauth.rst:215 +msgid "To correct this error, delete the credentials already created and create new credentials, selecting :guilabel:`Web Application` for the :guilabel:`Application Type`. Then, under :guilabel:`Authorized redirect URIs`, click :guilabel:`ADD URI` and type: `https://yourdbname.odoo.com/google_gmail/confirm` in the field, being sure to replace *yourdbname* in the URL with the Odoo database name." msgstr "" -#: ../../content/applications/general/export_import_data.rst:216 -msgid "For the country Belgium, you can use one of these 3 ways to import:" +#: ../../content/applications/general/email_communication/mailjet_api.rst:3 +msgid "Mailjet API" msgstr "" -#: ../../content/applications/general/export_import_data.rst:218 -msgid "Country: Belgium" +#: ../../content/applications/general/email_communication/mailjet_api.rst:5 +msgid "Odoo is compatible with Mailjet's :abbr:`API (Application Programming Interface)` for mass mailing. Set up a dedicated mass mailing server through Mailjet by configuring settings in the Mailjet account and the Odoo database. In some circumstances, settings need to be configured on the custom domain's :abbr:`DNS (Domain Name System)` settings as well." msgstr "" -#: ../../content/applications/general/export_import_data.rst:219 -msgid "Country/Database ID: 21" +#: ../../content/applications/general/email_communication/mailjet_api.rst:11 +msgid "Set up in Mailjet" msgstr "" -#: ../../content/applications/general/export_import_data.rst:220 -msgid "Country/External ID: base.be" +#: ../../content/applications/general/email_communication/mailjet_api.rst:14 +msgid "Create API credentials" msgstr "" -#: ../../content/applications/general/export_import_data.rst:222 -msgid "According to your need, you should use one of these 3 ways to reference records in relations. Here is when you should use one or the other, according to your need:" +#: ../../content/applications/general/email_communication/mailjet_api.rst:16 +msgid "To get started, sign in to the `Mailjet Account Information `_ page. Next, navigate to the :guilabel:`Senders & Domains` section and click on :guilabel:`SMTP and SEND API Settings`." msgstr "" -#: ../../content/applications/general/export_import_data.rst:225 -msgid "Use Country: This is the easiest way when your data come from CSV files that have been created manually." +#: ../../content/applications/general/email_communication/mailjet_api.rst:-1 +msgid "SMTP and Send API Settings link in the Senders & Domains section of Mailjet." msgstr "" -#: ../../content/applications/general/export_import_data.rst:227 -msgid "Use Country/Database ID: You should rarely use this notation. It's mostly used by developers as it's main advantage is to never have conflicts (you may have several records with the same name, but they always have a unique Database ID)" +#: ../../content/applications/general/email_communication/mailjet_api.rst:24 +msgid "Then, copy the :abbr:`SMTP (Simple Mail Transfer Protocol)` configuration settings onto a notepad. They can be found under the :guilabel:`Configuration (SMTP only)` section. The :abbr:`SMTP (Simple Mail Transfer Protocol)` configuration settings include the server address, the security option needed (Use :abbr:`SSL (Secure Sockets Layer)`/:abbr:`TLS (Transport Layer Security)`), and the port number. The settings are needed to configure Mailjet in Odoo, which is covered in the :ref:`last section `." msgstr "" -#: ../../content/applications/general/export_import_data.rst:230 -msgid "Use Country/External ID: Use External ID when you import data from a third party application." +#: ../../content/applications/general/email_communication/mailjet_api.rst:32 +msgid "`Mailjet: How can I configure my SMTP parameters? `_" msgstr "" -#: ../../content/applications/general/export_import_data.rst:232 -msgid "When you use External IDs, you can import CSV files with the \"External ID\" column to define the External ID of each record you import. Then, you will be able to make a reference to that record with columns like \"Field/External ID\". The following two CSV files give you an example for Products and their Categories." +#: ../../content/applications/general/email_communication/mailjet_api.rst:36 +msgid "Odoo blocks `port 25` on Odoo Online and Odoo.sh databases. :ref:`See reference here `." msgstr "" -#: ../../content/applications/general/export_import_data.rst:237 -msgid ":download:`CSV file for categories `." +#: ../../content/applications/general/email_communication/mailjet_api.rst:-1 +msgid "SMTP configuration from Mailjet." msgstr "" -#: ../../content/applications/general/export_import_data.rst:240 -msgid ":download:`CSV file for Products `." +#: ../../content/applications/general/email_communication/mailjet_api.rst:43 +msgid "Next, click on the button labeled :guilabel:`Retrieve your API credentials` to retrieve the Mailjet API credentials." msgstr "" -#: ../../content/applications/general/export_import_data.rst:244 -msgid "What can I do if I have multiple matches for a field?" +#: ../../content/applications/general/email_communication/mailjet_api.rst:46 +msgid "Then, click on the eye icon to reveal the :guilabel:`API key`. Copy this key to a notepad, as this serves as the :guilabel:`Username` in the Odoo configuration. Next, click on the :guilabel:`Generate Secret Key` button to generate the :guilabel:`Secret Key`. Copy this key to a notepad, as this serves as the :guilabel:`Password` in the Odoo configuration." msgstr "" -#: ../../content/applications/general/export_import_data.rst:246 -msgid "If for example you have two product categories with the child name \"Sellable\" (ie. \"Misc. Products/Sellable\" & \"Other Products/Sellable\"), your validation is halted but you may still import your data. However, we recommend you do not import the data because they will all be linked to the first 'Sellable' category found in the Product Category list (\"Misc. Products/Sellable\"). We recommend you modify one of the duplicates' values or your product category hierarchy." +#: ../../content/applications/general/email_communication/mailjet_api.rst:52 +msgid "Add verified sender address(es)" msgstr "" -#: ../../content/applications/general/export_import_data.rst:252 -msgid "However if you do not wish to change your configuration of product categories, we recommend you use make use of the external ID for this field 'Category'." +#: ../../content/applications/general/email_communication/mailjet_api.rst:54 +msgid "The next step is to add a sender address or a domain to the Mailjet account settings so that the email address or domain is approved to send emails using Mailjet's servers. First, navigate to the `Mailjet Account Information `_ page. Next, click on the :guilabel:`Add a Sender Domain or Address` link under the :guilabel:`Senders & Domains` section." msgstr "" -#: ../../content/applications/general/export_import_data.rst:256 -msgid "How can I import a many2many relationship field (e.g. a customer that has multiple tags)?" +#: ../../content/applications/general/email_communication/mailjet_api.rst:-1 +msgid "Add a sender domain or address in the Mailjet interface." msgstr "" -#: ../../content/applications/general/export_import_data.rst:258 -msgid "The tags should be separated by a comma without any spacing. For example, if you want your customer to be linked to both tags 'Manufacturer' and 'Retailer' then you will encode \"Manufacturer,Retailer\" in the same column of your CSV file." +#: ../../content/applications/general/email_communication/mailjet_api.rst:63 +msgid "Determine if a sender's email address or the entire domain needs to be added to the Mailjet settings. It may be easier to configure the domain as a whole if :abbr:`DNS (Domain Name System)` access is available. Jump to the :ref:`Add a domain ` section for steps on adding the domain." msgstr "" -#: ../../content/applications/general/export_import_data.rst:262 -msgid ":download:`CSV file for Manufacturer, Retailer `" +#: ../../content/applications/general/email_communication/mailjet_api.rst:69 +msgid "Either all email addresses of the Odoo database users who are sending emails using Mailjet's servers need to be configured or the domain(s) of the users' email addresses can be configured." msgstr "" -#: ../../content/applications/general/export_import_data.rst:266 -msgid "How can I import a one2many relationship (e.g. several Order Lines of a Sales Order)?" +#: ../../content/applications/general/email_communication/mailjet_api.rst:72 +msgid "By default, the email address originally set up in the Mailjet account is added as a trusted sender. To add another email address, click on the button labeled :guilabel:`Add a sender address`. Then, add the email address that is configured to send from the custom domain." msgstr "" -#: ../../content/applications/general/export_import_data.rst:268 -msgid "If you want to import sales order having several order lines; for each order line, you need to reserve a specific row in the CSV file. The first order line will be imported on the same row as the information relative to order. Any additional lines will need an additional row that does not have any information in the fields relative to the order. As an example, here is ``purchase.order_functional_error_line_cant_adpat.CSV`` file of some quotations you can import, based on demo data." +#: ../../content/applications/general/email_communication/mailjet_api.rst:76 +msgid "At minimum the following email addresses should be set up in the provider and verified in Mailjet:" msgstr "" -#: ../../content/applications/general/export_import_data.rst:275 -msgid ":download:`File for some Quotations `." +#: ../../content/applications/general/email_communication/mailjet_api.rst:78 +msgid "notifications\\@yourdomain.com" msgstr "" -#: ../../content/applications/general/export_import_data.rst:277 -msgid "The following CSV file shows how to import purchase orders with their respective purchase order lines:" +#: ../../content/applications/general/email_communication/mailjet_api.rst:79 +msgid "bounce\\@yourdomain.com" msgstr "" -#: ../../content/applications/general/export_import_data.rst:280 -msgid ":download:`Purchase orders with their respective purchase order lines `." +#: ../../content/applications/general/email_communication/mailjet_api.rst:80 +msgid "catchall\\@yourdomain.com" msgstr "" -#: ../../content/applications/general/export_import_data.rst:282 -msgid "The following CSV file shows how to import customers and their respective contacts:" +#: ../../content/applications/general/email_communication/mailjet_api.rst:83 +msgid "Replace `yourdomain` with the custom domain for the Odoo database. If there isn't one, then use the :guilabel:`mail.catchall.domain` system parameter." msgstr "" -#: ../../content/applications/general/export_import_data.rst:284 -msgid ":download:`Customers and their respective contacts `." +#: ../../content/applications/general/email_communication/mailjet_api.rst:86 +msgid "After that, fill out the :guilabel:`Email Information` form, making sure to select the appropriate email type: transactional email or mass emails. After completing the form, an activation email is sent to the email address and the trusted sender can be activated." msgstr "" -#: ../../content/applications/general/export_import_data.rst:287 -msgid "Can I import several times the same record?" +#: ../../content/applications/general/email_communication/mailjet_api.rst:90 +msgid "It is recommended to set up the :abbr:`SPF (Sender Policy Framework)`/:abbr:`DKIM (DomainKeys Identified Mail)`/:abbr:`DMARC (Domain-based Message Authentication, Reporting, and Conformance)` settings on the domain of the sender." msgstr "" -#: ../../content/applications/general/export_import_data.rst:289 -msgid "If you import a file that contains one of the column \"External ID\" or \"Database ID\", records that have already been imported will be modified instead of being created. This is very useful as it allows you to import several times the same CSV file while having made some changes in between two imports. Odoo will take care of creating or modifying each record depending if it's new or not." +#: ../../content/applications/general/email_communication/mailjet_api.rst:95 +#: ../../content/applications/general/email_communication/mailjet_api.rst:162 +msgid "`Mailjet's SPF/DKIM/DMARC documentation `_" msgstr "" -#: ../../content/applications/general/export_import_data.rst:294 -msgid "This feature allows you to use the Import/Export tool of Odoo to modify a batch of records in your favorite spreadsheet application." +#: ../../content/applications/general/email_communication/mailjet_api.rst:99 +msgid "If the database is not using a custom domain, then in order to verify the sender's address, a temporary alias (of the three email addresses mentioned above) should be set up in Odoo CRM to create a lead. Then, the database is able to receive the verification email and verify the accounts." msgstr "" -#: ../../content/applications/general/export_import_data.rst:298 -msgid "What happens if I do not provide a value for a specific field?" +#: ../../content/applications/general/email_communication/mailjet_api.rst:107 +msgid "Add a domain" msgstr "" -#: ../../content/applications/general/export_import_data.rst:300 -msgid "If you do not set all fields in your CSV file, Odoo will assign the default value for every non defined fields. But if you set fields with empty values in your CSV file, Odoo will set the EMPTY value in the field, instead of assigning the default value." +#: ../../content/applications/general/email_communication/mailjet_api.rst:109 +msgid "By adding an entire domain to the Mailjet account, all the sender addresses related to that domain are automatically validated for sending emails using Mailjet servers. First, navigate to the `Mailjet Account Information `_ page. Next, click on :guilabel:`Add a Sender Domain or Address` link under the :guilabel:`Senders & Domains` section. Then, click on :guilabel:`Add domain` to add the custom domain." msgstr "" -#: ../../content/applications/general/export_import_data.rst:305 -msgid "How to export/import different tables from an SQL application to Odoo?" +#: ../../content/applications/general/email_communication/mailjet_api.rst:116 +msgid "The domain needs to be added to the Mailjet account and then validated through the :abbr:`DNS (Domain Name System)`." msgstr "" -#: ../../content/applications/general/export_import_data.rst:307 -msgid "If you need to import data from different tables, you will have to recreate relations between records belonging to different tables. (e.g. if you import companies and persons, you will have to recreate the link between each person and the company they work for)." +#: ../../content/applications/general/email_communication/mailjet_api.rst:119 +msgid "After that, fill out the :guilabel:`Add a new Domain` page on Mailjet and click :guilabel:`Continue`." msgstr "" -#: ../../content/applications/general/export_import_data.rst:311 -msgid "To manage relations between tables, you can use the \"External ID\" facilities of Odoo. The \"External ID\" of a record is the unique identifier of this record in another application. This \"External ID\" must be unique across all the records of all objects, so it's a good practice to prefix this \"External ID\" with the name of the application or table. (like 'company_1', 'person_1' instead of '1')" +#: ../../content/applications/general/email_communication/mailjet_api.rst:122 +msgid "After adding the domain, a validation page will populate. Unless the Odoo database is on-premise (in which case, choose :guilabel:`Option 1`), choose :guilabel:`Option 2: Create a DNS Record`. Copy the TXT record information to a notepad and then navigate to the domain's :abbr:`DNS (Domain Name System)` provider to complete validation." msgstr "" -#: ../../content/applications/general/export_import_data.rst:317 -msgid "As an example, suppose you have a SQL database with two tables you want to import: companies and persons. Each person belong to one company, so you will have to recreate the link between a person and the company he work for. (If you want to test this example, here is a :download:`dump of such a PostgreSQL database `)" +#: ../../content/applications/general/email_communication/mailjet_api.rst:-1 +msgid "The TXT record information to input on the domain's DNS." msgstr "" -#: ../../content/applications/general/export_import_data.rst:322 -msgid "We will first export all companies and their \"External ID\". In PSQL, write the following command:" +#: ../../content/applications/general/email_communication/mailjet_api.rst:132 +msgid "Setup in the domain's DNS" msgstr "" -#: ../../content/applications/general/export_import_data.rst:328 -msgid "This SQL command will create the following CSV file:" +#: ../../content/applications/general/email_communication/mailjet_api.rst:134 +msgid "After getting the TXT record information from the Mailjet account, add a TXT record to the domain's :abbr:`DNS (Domain Name System)`. This process varies depending on the :abbr:`DNS (Domain Name System)` provider. Consult the provider for specific configuration processes. The TXT record information consists of the :guilabel:`Host` and :guilabel:`Value`. Paste these into the corresponding fields in the TXT record." msgstr "" -#: ../../content/applications/general/export_import_data.rst:337 -msgid "To create the CSV file for persons, linked to companies, we will use the following SQL command in PSQL:" +#: ../../content/applications/general/email_communication/mailjet_api.rst:141 +msgid "Return to Mailjet account information" msgstr "" -#: ../../content/applications/general/export_import_data.rst:343 -msgid "It will produce the following CSV file:" +#: ../../content/applications/general/email_communication/mailjet_api.rst:143 +msgid "After adding the TXT record to the domain's :abbr:`DNS (Domain Name System)`, navigate back to the Mailjet account. Then, navigate to :menuselection:`Account Information --> Add a Sender Domain or Address`, click the gear icon next to :guilabel:`Domain`, and select :guilabel:`Validate`." msgstr "" -#: ../../content/applications/general/export_import_data.rst:353 -msgid "As you can see in this file, Fabien and Laurence are working for the Bigees company (company_1) and Eric is working for the Organi company. The relation between persons and companies is done using the External ID of the companies. We had to prefix the \"External ID\" by the name of the table to avoid a conflict of ID between persons and companies (person_1 and company_1 who shared the same ID 1 in the original database)." +#: ../../content/applications/general/email_communication/mailjet_api.rst:147 +msgid "This action can also be done by going to the `Sender domains & addresses `_ page on the Mailjet account information and clicking on :guilabel:`Manage`." msgstr "" -#: ../../content/applications/general/export_import_data.rst:359 -msgid "The two files produced are ready to be imported in Odoo without any modifications. After having imported these two CSV files, you will have 4 contacts and 3 companies. (the firsts two contacts are linked to the first company). You must first import the companies and then the persons." +#: ../../content/applications/general/email_communication/mailjet_api.rst:150 +msgid "Next, click :guilabel:`Check Now` to validate the TXT record that was added on the domain. A success screen will appear if the domain is configured correctly." msgstr "" -#: ../../content/applications/general/export_import_data.rst:364 -msgid "How to adapt an import template" +#: ../../content/applications/general/email_communication/mailjet_api.rst:-1 +msgid "Check DNS record in Mailjet." msgstr "" -#: ../../content/applications/general/export_import_data.rst:366 -msgid "Import templates are provided in the import tool of the most common data to import (contacts, products, bank statements, etc.). You can open them with any spreadsheets software (Microsoft Office, OpenOffice, Google Drive, etc.)." +#: ../../content/applications/general/email_communication/mailjet_api.rst:157 +msgid "After successfully setting up the domain, there is an option to :guilabel:`Authenticate this domain (SPF/DKIM)`. This button populates :abbr:`SPF (Sender Policy Framework)` & :abbr:`DKIM (DomainKeys Identified Mail) records to input into the :abbr:`DNS (Domain Name System)` provider." msgstr "" -#: ../../content/applications/general/export_import_data.rst:372 -msgid "How to customize the file" +#: ../../content/applications/general/email_communication/mailjet_api.rst:-1 +msgid "Authenticate the domain with SPF/DKIM records in Mailjet." msgstr "" -#: ../../content/applications/general/export_import_data.rst:374 -msgid "Remove columns you don't need. We advise to not remove the *ID* one (see why here below)." +#: ../../content/applications/general/email_communication/mailjet_api.rst:172 +msgid "Set up in Odoo" msgstr "" -#: ../../content/applications/general/export_import_data.rst:381 -msgid "When you add a new column, Odoo might not be able to map it automatically if its label doesn't fit any field of the system. If so, find the corresponding field using the search." +#: ../../content/applications/general/email_communication/mailjet_api.rst:174 +msgid "To complete the setup, navigate to the Odoo database and go to the :guilabel:`Settings`. With :ref:`developer-mode` turned on, go to the :menuselection:`Technical Menu --> Email --> Outgoing Mail Servers`. Then, create a new outgoing server configuration by clicking on the :guilabel:`Create` button." msgstr "" -#: ../../content/applications/general/export_import_data.rst:388 -msgid "Then, use the label you found in your import template in order to make it work straight away the very next time you try to import." +#: ../../content/applications/general/email_communication/mailjet_api.rst:179 +msgid "Next, input the `SMTP server` (in-v3.mailjet.com), `port number` (587 or 465), and `Security (SSL/TLS)` that was copied earlier from the Mailjet account. They can also be found `here `_. It is recommended to use :abbr:`SSL (Secure Sockets Layer)`/:abbr:`TLS (Transport Layer Security)` even though Mailjet may not require it." msgstr "" -#: ../../content/applications/general/export_import_data.rst:392 -msgid "Why an “ID” column" +#: ../../content/applications/general/email_communication/mailjet_api.rst:184 +msgid "For the :guilabel:`Username`, input the :guilabel:`API KEY`. For the :guilabel:`Password`, input the :guilabel:`SECRET KEY` that was copied from the Mailjet account to the notepad earlier. These settings can be found on :menuselection:`Mailjet --> Account Settings --> SMTP and SEND API Settings`." msgstr "" -#: ../../content/applications/general/export_import_data.rst:394 -msgid "The **ID** (External ID) is an unique identifier for the line item. Feel free to use the one of your previous software to ease the transition to Odoo." +#: ../../content/applications/general/email_communication/mailjet_api.rst:189 +msgid "Then, if the Mailjet server is used for mass emailing, set the :guilabel:`Priority` value higher than that of any transactional email server(s). Finally, save the settings and :guilabel:`Test the Connection`." msgstr "" -#: ../../content/applications/general/export_import_data.rst:397 -msgid "Setting an ID is not mandatory when importing but it helps in many cases:" +#: ../../content/applications/general/email_communication/mailjet_api.rst:-1 +msgid "Odoo outgoing email server settings." msgstr "" -#: ../../content/applications/general/export_import_data.rst:399 -msgid "Update imports: you can import the same file several times without creating duplicates;" +#: ../../content/applications/general/email_communication/mailjet_api.rst:198 +msgid "In order for the notifications feature to work using Mailjet, there are three settings that need to be set in Odoo." msgstr "" -#: ../../content/applications/general/export_import_data.rst:400 -msgid "Import relation fields (see here below)." +#: ../../content/applications/general/email_communication/mailjet_api.rst:201 +msgid "The :guilabel:`From Filter` needs to be set on the server configuration. It is recommended to set it as a domain and not a full email address. It should match the domain in the two proceeding steps. More information can be referenced :ref:`here `." msgstr "" -#: ../../content/applications/general/export_import_data.rst:403 -msgid "How to import relation fields" +#: ../../content/applications/general/email_communication/mailjet_api.rst:205 +msgid "The :guilabel:`mail.default.from` system parameter must have the value `notifications\\@yourdomain.com`." msgstr "" -#: ../../content/applications/general/export_import_data.rst:405 -msgid "An Odoo object is always related to many other objects (e.g. a product is linked to product categories, attributes, vendors, etc.). To import those relations you need to import the records of the related object first from their own list menu." +#: ../../content/applications/general/email_communication/mailjet_api.rst:207 +msgid "The :guilabel:`mail.default.from_filter` system parameter must have the value `yourdomain.com`. Replace `yourdomain` with the custom domain for the Odoo database. If there isn't one, then use the :guilabel:`mail.catchall.domain` system parameter." msgstr "" -#: ../../content/applications/general/export_import_data.rst:409 -msgid "You can do it using either the name of the related record or its ID. The ID is expected when two records have the same name. In such a case add \" / ID\" at the end of the column title (e.g. for product attributes: Product Attributes / Attribute / ID)." +#: ../../content/applications/general/email_communication/mailjet_api.rst:211 +msgid "For more information see :ref:`Using a default email address `." msgstr "" -#: ../../content/applications/general/geolocation.rst:3 +#: ../../content/applications/general/email_communication/mailjet_api.rst:213 +msgid "The :guilabel:`System Parameters` can be accessed by activating the :ref:`developer mode `." +msgstr "" + +#: ../../content/applications/general/email_communication/mailjet_api.rst:216 +msgid "Once the setup is complete, the Odoo database is ready to use the Mailjet email server for mass mailing or transactional emails!" +msgstr "" + +#: ../../content/applications/general/integrations.rst:3 +msgid "Integrations" +msgstr "" + +#: ../../content/applications/general/integrations/geolocation.rst:3 msgid "Geolocation" msgstr "" -#: ../../content/applications/general/geolocation.rst:5 +#: ../../content/applications/general/integrations/geolocation.rst:5 msgid "You can locate contacts or places and generate routes on a map in Odoo." msgstr "" -#: ../../content/applications/general/geolocation.rst:-1 +#: ../../content/applications/general/integrations/geolocation.rst:-1 msgid "Map displaying a contact's location." msgstr "" -#: ../../content/applications/general/geolocation.rst:10 +#: ../../content/applications/general/integrations/geolocation.rst:10 msgid "To use the feature, open the :guilabel:`Settings` app, and, under the :guilabel:`Integrations`, section, activate :guilabel:`Geo Localization`. Then, choose between using the OpenStreetMap or Google Places API." msgstr "" -#: ../../content/applications/general/geolocation.rst:14 +#: ../../content/applications/general/integrations/geolocation.rst:14 msgid "**OpenStreetMap**" msgstr "" -#: ../../content/applications/general/geolocation.rst:16 +#: ../../content/applications/general/integrations/geolocation.rst:16 msgid "OpenStreetMap is a free, open geographic database updated and maintained by volunteers. To use it, select :guilabel:`Open Street Map`." msgstr "" -#: ../../content/applications/general/geolocation.rst:20 +#: ../../content/applications/general/integrations/geolocation.rst:20 msgid "OpenStreetMap might not always be accurate. You can `join the OpenStreetMap community `_ to fix any issues encountered." msgstr "" -#: ../../content/applications/general/geolocation.rst:23 +#: ../../content/applications/general/integrations/geolocation.rst:23 msgid "**Google Places API map**" msgstr "" -#: ../../content/applications/general/geolocation.rst:25 +#: ../../content/applications/general/integrations/geolocation.rst:25 msgid "The Google Places API map provides detailed info on places, businesses, and points of interest. It supports location-based features like search, navigation, and recommendations." msgstr "" -#: ../../content/applications/general/geolocation.rst:29 +#: ../../content/applications/general/integrations/geolocation.rst:29 msgid "Using the Google Places API could require `payment to Google `_." msgstr "" -#: ../../content/applications/general/geolocation.rst:32 +#: ../../content/applications/general/integrations/geolocation.rst:32 msgid "To use it, select :guilabel:`Google Place Map` and enter your :ref:`API Key `." msgstr "" -#: ../../content/applications/general/geolocation.rst:-1 +#: ../../content/applications/general/integrations/geolocation.rst:-1 msgid "Google Places API key" msgstr "" -#: ../../content/applications/general/geolocation.rst:39 -msgid ":doc:`../../applications/websites/website/configuration/address_autocomplete`" +#: ../../content/applications/general/integrations/geolocation.rst:39 +msgid ":doc:`/applications/websites/website/configuration/address_autocomplete`" msgstr "" -#: ../../content/applications/general/in_app_purchase.rst:3 -msgid "In-app purchase (IAP)" +#: ../../content/applications/general/integrations/mail_plugins.rst:5 +msgid "Mail Plugins" msgstr "" -#: ../../content/applications/general/in_app_purchase.rst:7 -msgid "In-app purchases (IAP) are optional services that enhance Odoo databases. Each service provides its own specific features and functionality. A full list of services is available on the `Odoo IAP Catalog `_." +#: ../../content/applications/general/integrations/mail_plugins.rst:13 +msgid "Mail Plugins are connectors that bridge your mailbox with your Odoo database. With them, you can interact with your Odoo database directly from your mailbox by:" msgstr "" -#: ../../content/applications/general/in_app_purchase.rst:-1 -msgid "The IAP catalog with various services available on IAP.Odoo.com." +#: ../../content/applications/general/integrations/mail_plugins.rst:16 +msgid "Creating leads and centralizing prospects' emails into the CRM app." msgstr "" -#: ../../content/applications/general/in_app_purchase.rst:16 -msgid "The :guilabel:`SMS` service sends text messages to contacts directly from the database, and the :guilabel:`Documents Digitization` service digitizes scanned or PDF vendor bills, expenses, and resumes with optical character recognition (OCR) and artificial intelligence (AI)." +#: ../../content/applications/general/integrations/mail_plugins.rst:17 +msgid "Generating tasks in any Odoo project." msgstr "" -#: ../../content/applications/general/in_app_purchase.rst:20 -msgid "|IAP| services do **not** need to be configured or set up before use. Odoo users can simply click on the service in the app to activate it. However, each service requires its own prepaid credits, and when they run out, users **must** :ref:`buy more ` in order to keep using it." +#: ../../content/applications/general/integrations/mail_plugins.rst:18 +msgid "Creating tickets in the Helpdesk app." msgstr "" -#: ../../content/applications/general/in_app_purchase.rst:25 -msgid "Users with an Enterprise version of Odoo Online get free credits to test IAP features." +#: ../../content/applications/general/integrations/mail_plugins.rst:19 +msgid "Searching and storing insights on your contacts." msgstr "" -#: ../../content/applications/general/in_app_purchase.rst:30 -msgid "IAP services" +#: ../../content/applications/general/integrations/mail_plugins.rst:21 +msgid "Mail Plugins are available for :doc:`Outlook ` and :doc:`Gmail `." msgstr "" -#: ../../content/applications/general/in_app_purchase.rst:32 -msgid "|IAP| services are provided by Odoo, as well as third-parties, and have a wide range of uses." +#: ../../content/applications/general/integrations/mail_plugins.rst:27 +msgid "Pricing" msgstr "" -#: ../../content/applications/general/in_app_purchase.rst:34 -msgid "The following |IAP| services are provided by Odoo:" +#: ../../content/applications/general/integrations/mail_plugins.rst:29 +msgid "Mail Plugins are **free** to install and use." msgstr "" -#: ../../content/applications/general/in_app_purchase.rst:36 -msgid ":guilabel:`Documents Digitization`: digitizes scanned or PDF vendor bills, expenses, and resumes with OCR and AI." +#: ../../content/applications/general/integrations/mail_plugins.rst:31 +msgid "However, they can provide **Lead Enrichment**, which is part of a paid service known as **Lead Generation**." msgstr "" -#: ../../content/applications/general/in_app_purchase.rst:38 -msgid ":guilabel:`Partner Autocomplete`: automatically populates contact records with corporate data." +#: ../../content/applications/general/integrations/mail_plugins.rst:34 +msgid "Mail plugins allow you to test Lead Enrichment for free, whether you connect the plugins to a database or not. After a while, the plugins ask you to buy :doc:`../../essentials/in_app_purchase` credits if you would like to keep using this service." msgstr "" -#: ../../content/applications/general/in_app_purchase.rst:39 -msgid ":guilabel:`SMS`: sends SMS text messages to contacts directly from the database." +#: ../../content/applications/general/integrations/mail_plugins.rst:41 +msgid "Lead Generation IAP service" msgstr "" -#: ../../content/applications/general/in_app_purchase.rst:40 -msgid ":guilabel:`Lead Generation`: generates leads based on a set of criteria, and converts web visitors into quality leads and opportunities." +#: ../../content/applications/general/integrations/mail_plugins.rst:43 +msgid "Lead Enrichment uses the *Lead Generation IAP service*. Each request consumes one *Lead Generation credit*." msgstr "" -#: ../../content/applications/general/in_app_purchase.rst:42 -msgid ":guilabel:`Snailmail`: sends customer invoices and follow-up reports by post, worldwide." +#: ../../content/applications/general/integrations/mail_plugins.rst:46 +msgid "To buy credits, go to :menuselection:`Settings --> CRM --> Lead Enrichment --> Buy credits` and select a package." msgstr "" -#: ../../content/applications/general/in_app_purchase.rst:44 -msgid "For more information on every service currently available, visit the `Odoo IAP Catalog `_." +#: ../../content/applications/general/integrations/mail_plugins.rst:50 +msgid "If you are out of credits, the only information populated when clicking on the suggested company is its website link and logo." msgstr "" -#: ../../content/applications/general/in_app_purchase.rst:48 -msgid "Use IAP services" +#: ../../content/applications/general/integrations/mail_plugins.rst:52 +msgid "Check out the `Lead Generation IAP service Privacy Policy `_." msgstr "" -#: ../../content/applications/general/in_app_purchase.rst:50 -msgid "|IAP| services are automatically integrated with Odoo, and do **not** require users to configure any settings. To use a service, simply interact with it wherever it appears in the database." +#: ../../content/applications/general/integrations/mail_plugins.rst:56 +msgid ":doc:`../../essentials/in_app_purchase`" msgstr "" -#: ../../content/applications/general/in_app_purchase.rst:54 -msgid "The following flow focuses on the *SMS* |IAP| service being used from a contact's record." +#: ../../content/applications/general/integrations/mail_plugins.rst:57 +msgid "`Odoo Tutorials: Lead Enrichment `_" msgstr "" -#: ../../content/applications/general/in_app_purchase.rst:56 -msgid "This can be done by clicking the :guilabel:`📱 (phone) SMS` icon within the database." +#: ../../content/applications/general/integrations/mail_plugins/gmail.rst:3 +msgid "Gmail Plugin" msgstr "" -#: ../../content/applications/general/in_app_purchase.rst:-1 -msgid "The SMS icon on a typical contact information form located within an Odoo database." +#: ../../content/applications/general/integrations/mail_plugins/gmail.rst:5 +msgid "The *Gmail Plugin* integrates an Odoo database with a Gmail inbox, so users can keep track of all their work between Gmail and Odoo, without losing any information." msgstr "" -#: ../../content/applications/general/in_app_purchase.rst:62 -msgid "One way to utilize the *SMS* |IAP| service with Odoo is showcased in the following steps:" +#: ../../content/applications/general/integrations/mail_plugins/gmail.rst:9 +msgid "Odoo Online users" msgstr "" -#: ../../content/applications/general/in_app_purchase.rst:64 -msgid "Navigate to the :menuselection:`Contacts application`, and click on a contact with a mobile phone number entered in either the :guilabel:`Phone` or :guilabel:`Mobile` field of the contact form." +#: ../../content/applications/general/integrations/mail_plugins/gmail.rst:11 +msgid "For databases hosted on Odoo Online (or Odoo.sh), follow the steps below to configure the Gmail Plugin." msgstr "" -#: ../../content/applications/general/in_app_purchase.rst:67 -msgid "Hover the mouse over the :guilabel:`Phone` or :guilabel:`Mobile` field, and a :guilabel:`📱 (phone) SMS` icon appears to the right." +#: ../../content/applications/general/integrations/mail_plugins/gmail.rst:15 +#: ../../content/applications/general/integrations/mail_plugins/gmail.rst:94 +msgid "Install the Gmail Plugin" msgstr "" -#: ../../content/applications/general/in_app_purchase.rst:69 -msgid "Click the :guilabel:`📱 (phone) SMS` icon, and a :guilabel:`Send SMS Text Message` pop-up window appears." +#: ../../content/applications/general/integrations/mail_plugins/gmail.rst:17 +msgid "First, log in to the Gmail account that the user wishes to connect to Odoo." msgstr "" -#: ../../content/applications/general/in_app_purchase.rst:71 -msgid "Type a message in the :guilabel:`Message` field of the :guilabel:`Send SMS Text Message` pop-up window. Then, click the :guilabel:`Send SMS` button. Odoo then sends the message, via SMS, to the contact, and logs what was sent in the *chatter* of the contact's form." +#: ../../content/applications/general/integrations/mail_plugins/gmail.rst:19 +msgid "From the Gmail inbox, click the plus sign icon on the right side panel to get add-ons. If the side panel is not visible, click on the arrow icon at the bottom right corner of the inbox to reveal it." msgstr "" -#: ../../content/applications/general/in_app_purchase.rst:75 -msgid "Upon sending the SMS message, the prepaid credits for the *SMS* |IAP| service are automatically deducted from the existing credits. If there are not enough credits to send the message, Odoo prompts the user to purchase more." +#: ../../content/applications/general/integrations/mail_plugins/gmail.rst:-1 +msgid "Plus sign icon on the Gmail inbox side panel." msgstr "" -#: ../../content/applications/general/in_app_purchase.rst:80 -msgid "For more information on how to use various |IAP| services, and for more in-depth instructions related to SMS functionality in Odoo, review the documentation below:" +#: ../../content/applications/general/integrations/mail_plugins/gmail.rst:26 +msgid "Then, use the search bar to search for `Odoo` and locate the :guilabel:`Odoo Inbox Addin`." msgstr "" -#: ../../content/applications/general/in_app_purchase.rst:83 -msgid ":doc:`Lead mining `" +#: ../../content/applications/general/integrations/mail_plugins/gmail.rst:-1 +msgid "Odoo Inbox Addin on Google Workspace Marketplace." msgstr "" -#: ../../content/applications/general/in_app_purchase.rst:84 -msgid ":doc:`Enrich your contacts base with Partner Autocomplete `" +#: ../../content/applications/general/integrations/mail_plugins/gmail.rst:32 +msgid "Or, go directly to the :guilabel:`Odoo Inbox Addin` page on the `Google Workspace Marketplace `_." msgstr "" -#: ../../content/applications/general/in_app_purchase.rst:86 -msgid ":doc:`SMS essentials `" +#: ../../content/applications/general/integrations/mail_plugins/gmail.rst:35 +msgid "Once the plugin is located, click :guilabel:`Install`. Then, click :guilabel:`Continue` to start the installation." msgstr "" -#: ../../content/applications/general/in_app_purchase.rst:91 -msgid "IAP credits" +#: ../../content/applications/general/integrations/mail_plugins/gmail.rst:38 +msgid "Next, select which Gmail account the user wishes to connect to Odoo. Then click :guilabel:`Allow` to let Odoo access the Google account. Google will then show a pop-up window confirming that the installation was successful." msgstr "" -#: ../../content/applications/general/in_app_purchase.rst:93 -msgid "Every time an |IAP| service is used, the prepaid credits for that service are spent. Odoo prompts the purchase of more credits when there are not enough credits left to continue using a service. Email alerts can also be set up for when :ref:`credits are low `." +#: ../../content/applications/general/integrations/mail_plugins/gmail.rst:43 +#: ../../content/applications/general/integrations/mail_plugins/gmail.rst:134 +msgid "Configure the Odoo database" msgstr "" -#: ../../content/applications/general/in_app_purchase.rst:97 -msgid "Credits are purchased in *Packs* from the `Odoo IAP Catalog `_, and pricing is specific to each service." +#: ../../content/applications/general/integrations/mail_plugins/gmail.rst:45 +#: ../../content/applications/general/integrations/mail_plugins/gmail.rst:136 +msgid "The :guilabel:`Mail Plugin` feature must be enabled in the Odoo database in order to use the Gmail Plugin. To enable the feature, go to :menuselection:`Settings --> General Settings`. Under the :guilabel:`Integrations` section, activate :guilabel:`Mail Plugin`, and then click :guilabel:`Save`." msgstr "" -#: ../../content/applications/general/in_app_purchase.rst:101 -msgid "The `SMS service `_ has four packs available, in denominations of:" +#: ../../content/applications/general/integrations/mail_plugins/gmail.rst:-1 +#: ../../content/applications/general/integrations/mail_plugins/gmail.rst:-1 +msgid "The Mail Plugin feature in the Settings." msgstr "" -#: ../../content/applications/general/in_app_purchase.rst:104 -msgid ":guilabel:`Starter Pack`: 10 credits" +#: ../../content/applications/general/integrations/mail_plugins/gmail.rst:55 +#: ../../content/applications/general/integrations/mail_plugins/gmail.rst:145 +msgid "Configure the Gmail inbox" msgstr "" -#: ../../content/applications/general/in_app_purchase.rst:105 -msgid ":guilabel:`Standard Pack`: 100 credits" +#: ../../content/applications/general/integrations/mail_plugins/gmail.rst:57 +#: ../../content/applications/general/integrations/mail_plugins/gmail.rst:147 +msgid "In the Gmail inbox, a purple Odoo icon is now visible on the right side panel. Click on the Odoo icon to open up the Odoo plugin window. Then, click on any email in the inbox. Click :guilabel:`Authorize Access` in the plugin window to grant Odoo access to the Gmail inbox." msgstr "" -#: ../../content/applications/general/in_app_purchase.rst:106 -msgid ":guilabel:`Advanced Pack`: 500 credits" +#: ../../content/applications/general/integrations/mail_plugins/gmail.rst:-1 +#: ../../content/applications/general/integrations/mail_plugins/gmail.rst:-1 +msgid "The Authorize Access button in the right sidebar of the Odoo plugin panel." msgstr "" -#: ../../content/applications/general/in_app_purchase.rst:107 -msgid ":guilabel:`Expert Pack`: 1,000 credits" +#: ../../content/applications/general/integrations/mail_plugins/gmail.rst:65 +#: ../../content/applications/general/integrations/mail_plugins/gmail.rst:155 +msgid "Next, click :guilabel:`Login`. Then, enter the URL of the Odoo database that the user wishes to connect to the Gmail inbox, and log in to the database." msgstr "" -#: ../../content/applications/general/in_app_purchase.rst:-1 -msgid "Four different packs of credits for the SMS IAP service." +#: ../../content/applications/general/integrations/mail_plugins/gmail.rst:69 +#: ../../content/applications/general/integrations/mail_plugins/gmail.rst:159 +msgid "Use the general URL for the database, not the URL of a specific page in the database. For example, use `https://mycompany.odoo.com`, not `https://mycompany.odoo.com/web#cids=1&action=menu`." msgstr "" -#: ../../content/applications/general/in_app_purchase.rst:113 -msgid "The number of credits consumed depends on the length of the SMS and the country of destination." +#: ../../content/applications/general/integrations/mail_plugins/gmail.rst:73 +#: ../../content/applications/general/integrations/mail_plugins/gmail.rst:163 +msgid "Finally, click :guilabel:`Allow` to let Gmail access the Odoo database. The browser will then show a :guilabel:`Success!` message. After that, close the window. The Gmail inbox and Odoo database are now connected." msgstr "" -#: ../../content/applications/general/in_app_purchase.rst:115 -msgid "For more information, refer to the :doc:`SMS Pricing and FAQ ` documentation." +#: ../../content/applications/general/integrations/mail_plugins/gmail.rst:78 +msgid "Odoo On-Premise users" msgstr "" -#: ../../content/applications/general/in_app_purchase.rst:121 -msgid "Buy credits" +#: ../../content/applications/general/integrations/mail_plugins/gmail.rst:80 +msgid "For databases hosted on servers other than Odoo Online (or Odoo.sh), follow the steps below to configure the Gmail Plugin." msgstr "" -#: ../../content/applications/general/in_app_purchase.rst:123 -msgid "If there are not enough credits to perform a task, the database automatically prompts the purchase of more credits." +#: ../../content/applications/general/integrations/mail_plugins/gmail.rst:84 +msgid "As part of their security guidelines, Google requires add-on creators to provide a list of URLs that can be used in actions and redirections launched by the add-on. This protects users by ensuring, for example, that no add-on redirects users toward a malicious website. (Read more on `Google Apps Script `_.)" msgstr "" -#: ../../content/applications/general/in_app_purchase.rst:126 -msgid "Users can check the current balance of credits for each service, and manually purchase more credits, by navigating to the :menuselection:`Settings app --> Search IAP --> View My Services`." +#: ../../content/applications/general/integrations/mail_plugins/gmail.rst:89 +msgid "Since Odoo can only list the `odoo.com` domain and not every on-premise customer's unique server domain, on-premise customers cannot install the Gmail Plugin from the Google Workspace Marketplace." msgstr "" -#: ../../content/applications/general/in_app_purchase.rst:129 -#: ../../content/applications/general/in_app_purchase.rst:146 -msgid "Doing so reveals an :guilabel:`IAP Account` page, listing the various |IAP| services in the database. From here, click an |IAP| service to open its :guilabel:`Account Information` page, where additional credits can be purchased." +#: ../../content/applications/general/integrations/mail_plugins/gmail.rst:96 +msgid "First, access the `GitHub repository `_ for the Odoo Mail Plugins. Next, click on the green :guilabel:`Code` button. Then, click :guilabel:`Download ZIP` to download the Mail Plugin files onto the user's computer." msgstr "" -#: ../../content/applications/general/in_app_purchase.rst:134 -msgid "Manually buy credits" +#: ../../content/applications/general/integrations/mail_plugins/gmail.rst:-1 +msgid "Download the ZIP file from the Odoo GitHub repository for Mail Plugins." msgstr "" -#: ../../content/applications/general/in_app_purchase.rst:136 -msgid "To manually buy credits in Odoo, follow these steps:" +#: ../../content/applications/general/integrations/mail_plugins/gmail.rst:104 +msgid "Open the ZIP file on the computer. Then, go to :menuselection:`mail-client-extensions-master --> gmail --> src --> views`, and open the :file:`login.ts` file using any text editor software, such as Notepad (Windows), TextEdit (Mac), or Visual Studio Code." msgstr "" -#: ../../content/applications/general/in_app_purchase.rst:138 -#: ../../content/applications/general/in_app_purchase.rst:173 -msgid "Go to the :menuselection:`Settings application`." +#: ../../content/applications/general/integrations/mail_plugins/gmail.rst:108 +msgid "Delete the following three lines of text from the :file:`login.ts` file:" msgstr "" -#: ../../content/applications/general/in_app_purchase.rst:139 -#: ../../content/applications/general/in_app_purchase.rst:174 -msgid "Type `IAP` in the search bar." +#: ../../content/applications/general/integrations/mail_plugins/gmail.rst:116 +msgid "This removes the `odoo.com` domain constraint from the Gmail Plugin program." msgstr "" -#: ../../content/applications/general/in_app_purchase.rst:140 -#: ../../content/applications/general/in_app_purchase.rst:175 -msgid "Click :guilabel:`View My Services`." +#: ../../content/applications/general/integrations/mail_plugins/gmail.rst:118 +msgid "Next, in the ZIP file, go to :menuselection:`mail-client-extensions-master --> gmail`, and open the file called :guilabel:`appsscript.json`. In the :guilabel:`urlFetchWhitelist` section, replace all the references to `odoo.com` with the Odoo customer's unique server domain." msgstr "" -#: ../../content/applications/general/in_app_purchase.rst:0 -msgid "The Settings app showing the Odoo IAP heading and View My Services button." +#: ../../content/applications/general/integrations/mail_plugins/gmail.rst:122 +msgid "Then, in the same :guilabel:`gmail` folder, open the file called :guilabel:`README.md`. Follow the instructions in the :guilabel:`README.md` file to push the Gmail Plugin files as a Google Project." msgstr "" -#: ../../content/applications/general/in_app_purchase.rst:149 -msgid "On the :guilabel:`Account Information` page, click the :guilabel:`Buy Credit` button." +#: ../../content/applications/general/integrations/mail_plugins/gmail.rst:126 +msgid "The computer must be able to run Linux commands in order to follow the instructions on the :guilabel:`README.md` file." msgstr "" -#: ../../content/applications/general/in_app_purchase.rst:0 -msgid "The Account Information page for an IAP service showing the Buy Credit button." +#: ../../content/applications/general/integrations/mail_plugins/gmail.rst:129 +msgid "After that, share the Google Project with the Gmail account that the user wishes to connect to Odoo. Then, click :guilabel:`Publish` and :guilabel:`Deploy from manifest`. Lastly, click :guilabel:`Install the add-on` to install the Gmail Plugin." msgstr "" -#: ../../content/applications/general/in_app_purchase.rst:155 -msgid "Doing so loads a :guilabel:`Buy Credits for (IAP Account)` page in a new tab. From here, click :guilabel:`Buy` on the desired pack of credits. Then, follow the prompts to enter payment details, and confirm the order." +#: ../../content/applications/general/integrations/mail_plugins/outlook.rst:3 +msgid "Outlook Plugin" msgstr "" -#: ../../content/applications/general/in_app_purchase.rst:0 -msgid "The SMS service page on IAP.Odoo.com with four packs of credits available for purchase." +#: ../../content/applications/general/integrations/mail_plugins/outlook.rst:5 +msgid "Outlook allows for third-party applications to connect in order to execute database actions from emails. Odoo has a plugin for Outlook that allows for the creation of an opportunity from the email panel." msgstr "" -#: ../../content/applications/general/in_app_purchase.rst:163 -msgid "Once the transaction is complete, the credits are available for use in the database." +#: ../../content/applications/general/integrations/mail_plugins/outlook.rst:10 +#: ../../content/applications/general/iot/config.rst:5 +#: ../../content/applications/general/users/azure.rst:22 +#: ../../content/applications/general/users/google.rst:24 +msgid "Configuration" msgstr "" -#: ../../content/applications/general/in_app_purchase.rst:168 -msgid "Low-credit notification" +#: ../../content/applications/general/integrations/mail_plugins/outlook.rst:12 +msgid "The Outlook :doc:`Mail Plugin <../mail_plugins>` needs to be configured both on Odoo and Outlook." msgstr "" -#: ../../content/applications/general/in_app_purchase.rst:170 -msgid "It is possible to be notified when credits are low, in order to avoid running out of credits, while using an |IAP| service. To do that, follow this process:" +#: ../../content/applications/general/integrations/mail_plugins/outlook.rst:17 +msgid "Enable Mail Plugin" msgstr "" -#: ../../content/applications/general/in_app_purchase.rst:176 -msgid "The available |IAP| accounts appear in a list view on the :guilabel:`IAP Account` page. From here, click on the desired |IAP| account to view that service's :guilabel:`Account Information` page." +#: ../../content/applications/general/integrations/mail_plugins/outlook.rst:19 +msgid "First, enable the *Mail Plugin* feature in the database. Go to :menuselection:`Settings --> General Settings --> Integrations`, enable :guilabel:`Mail Plugin`, and :guilabel:`Save` the configuration." msgstr "" -#: ../../content/applications/general/in_app_purchase.rst:179 -msgid "On the :guilabel:`Account Information` page, tick the :guilabel:`Warn Me` box. Doing so reveals two fields on the form: :guilabel:`Threshold` and :guilabel:`Warning Email`." +#: ../../content/applications/general/integrations/mail_plugins/outlook.rst:25 +msgid "Install the Outlook Plugin" msgstr "" -#: ../../content/applications/general/in_app_purchase.rst:0 -msgid "Odoo will send an email alert when credits for this service fall below the threshold." +#: ../../content/applications/general/integrations/mail_plugins/outlook.rst:27 +msgid "Download (:menuselection:`Save Page As --> Web Page XML only`) the following XML file to upload later: `https://download.odoocdn.com/plugins/outlook/manifest.xml `_." msgstr "" -#: ../../content/applications/general/in_app_purchase.rst:186 -msgid "In the :guilabel:`Threshold` field, enter an amount of credits Odoo should use as the minimum threshold for this service." +#: ../../content/applications/general/integrations/mail_plugins/outlook.rst:31 +msgid "Next, open the Outlook mailbox, and select any email. After completing this, click on the :guilabel:`More actions` button in the upper right-side and select :guilabel:`Get Add-ins`." msgstr "" -#: ../../content/applications/general/in_app_purchase.rst:188 -msgid "In the :guilabel:`Warning Email` field, enter the email address that should receive the notification." +#: ../../content/applications/general/integrations/mail_plugins/outlook.rst:-1 +msgid "More actions button in Outlook" msgstr "" -#: ../../content/applications/general/in_app_purchase.rst:191 -msgid "Odoo sends a low-credit alert to the :guilabel:`Warning Email` when the balance of credits falls below the amount listed as the :guilabel:`Threshold`." +#: ../../content/applications/general/integrations/mail_plugins/outlook.rst:38 +msgid "Following this step, select the :guilabel:`My add-ins` tab on the left-side." msgstr "" -#: ../../content/applications/general/reporting.rst:3 -msgid "Reporting" +#: ../../content/applications/general/integrations/mail_plugins/outlook.rst:-1 +msgid "My add-ins in Outlook" msgstr "" -#: ../../content/applications/general/reporting.rst:5 -msgid "You can find several reports under the :guilabel:`Reporting` menu of most apps that let you analyze and visualize the data of your records." +#: ../../content/applications/general/integrations/mail_plugins/outlook.rst:44 +msgid "Under :guilabel:`Custom add-ins` towards the bottom, click on :guilabel:`+ Add a custom add-in`, and then on :guilabel:`Add from file...`" msgstr "" -#: ../../content/applications/general/reporting.rst:11 -msgid "Selecting a view" +#: ../../content/applications/general/integrations/mail_plugins/outlook.rst:-1 +msgid "Custom add-ins in Outlook" msgstr "" -#: ../../content/applications/general/reporting.rst:13 -msgid "Depending on the report, Odoo can display the data in various ways. Sometimes, a unique view fully tailored to the report is available, while several views are available for others. However, two generic views are dedicated to reporting: the graph and pivot views." +#: ../../content/applications/general/integrations/mail_plugins/outlook.rst:51 +msgid "For the next step, attach the `manifest.xml` file downloaded above, and press :guilabel:`OK`. Next, read the warning and click on :guilabel:`Install`." msgstr "" -#: ../../content/applications/general/reporting.rst:20 -msgid "Graph view" +#: ../../content/applications/general/integrations/mail_plugins/outlook.rst:-1 +msgid "Custom add-in installation warning in Outlook" msgstr "" -#: ../../content/applications/general/reporting.rst:22 -msgid "The :ref:`graph view ` is used to visualize your records' data, helping you identify patterns and trends. The view is often found under the :guilabel:`Reporting` menu of apps but can be found elsewhere. Click the **graph view button** located at the top right to access it." +#: ../../content/applications/general/integrations/mail_plugins/outlook.rst:61 +msgid "Connect the database" msgstr "" -#: ../../content/applications/general/reporting.rst:-1 -msgid "Selecting the graph view" +#: ../../content/applications/general/integrations/mail_plugins/outlook.rst:63 +msgid "Now, Outlook will be connected to the Odoo database. First, open any email in the Outlook mailbox, click on the :guilabel:`More actions` button in the upper right-side, and select :guilabel:`Odoo for Outlook`." msgstr "" -#: ../../content/applications/general/reporting.rst:33 -msgid "Pivot view" +#: ../../content/applications/general/integrations/mail_plugins/outlook.rst:-1 +msgid "Odoo for Outlook add-in button" msgstr "" -#: ../../content/applications/general/reporting.rst:35 -msgid "The :ref:`pivot view ` is used to aggregate your records' data and break it down for analysis. The view is often found under the :guilabel:`Reporting` menu of apps but can be found elsewhere. Click the **pivot view button** located at the top right to access it." +#: ../../content/applications/general/integrations/mail_plugins/outlook.rst:71 +msgid "The right-side panel can now display **Company Insights**. At the bottom, click on :guilabel:`Login`." msgstr "" -#: ../../content/applications/general/reporting.rst:-1 -msgid "Selecting the pivot view" +#: ../../content/applications/general/integrations/mail_plugins/outlook.rst:-1 +msgid "Logging in the Odoo database" msgstr "" -#: ../../content/applications/general/reporting.rst:45 -msgid "Choosing measures" +#: ../../content/applications/general/integrations/mail_plugins/outlook.rst:79 +msgid "Only a limited amount of **Company Insights** (*Lead Enrichment*) requests are available as a trial database. This feature requires :ref:`prepaid credits `." msgstr "" -#: ../../content/applications/general/reporting.rst:47 -msgid "After selecting a view, you should ensure only the relevant records are :doc:`filtered `. Next, you should choose what is measured. By default, a measure is always selected. If you wish to edit it, click :guilabel:`Measures` and choose one or, only for pivots, multiple measures." +#: ../../content/applications/general/integrations/mail_plugins/outlook.rst:83 +msgid "If, after a short while, the panel is still empty, it is possible that the browser cookie settings prevented it from loading. Note that these settings also change if the browser is in \"Incognito\" mode." msgstr "" -#: ../../content/applications/general/reporting.rst:52 -msgid "When you select a measure, Odoo aggregates the values recorded on that field for the filtered records. Only numerical fields (:ref:`integer `, :ref:`decimal `, :ref:`monetary `) can be measured. In addition, the :guilabel:`Count` option is used to count the total number of filtered records." +#: ../../content/applications/general/integrations/mail_plugins/outlook.rst:87 +msgid "To fix this issue, configure the browser to always allow cookies on Odoo's plugin page." msgstr "" -#: ../../content/applications/general/reporting.rst:58 -msgid "After choosing what you want to measure, you can define how the data should be :ref:`grouped ` depending on the dimension you want to analyze. By default, the data is often grouped by *Date > Month*, which is used to analyze the evolution of a measure over the months." +#: ../../content/applications/general/integrations/mail_plugins/outlook.rst:89 +msgid "For Google Chrome, change the browser cookie settings by following the guide at: `https://support.google.com/chrome/answer/95647 `_ and adding `download.odoo.com` to the list of :guilabel:`Sites that can always use cookies`." msgstr "" -#: ../../content/applications/general/reporting.rst:63 -msgid "When you filter a single time period, the option to compare it against another one appears." +#: ../../content/applications/general/integrations/mail_plugins/outlook.rst:94 +msgid "Once this is complete, the Outlook panel needs to be opened again." msgstr "" -#: ../../content/applications/general/reporting.rst:0 -msgid "Using the comparison option" +#: ../../content/applications/general/integrations/mail_plugins/outlook.rst:96 +msgid "Now, enter the Odoo database URL and click on :guilabel:`Login`." msgstr "" -#: ../../content/applications/general/reporting.rst:72 -msgid "Select measures" +#: ../../content/applications/general/integrations/mail_plugins/outlook.rst:-1 +msgid "Entering the Odoo database URL" msgstr "" -#: ../../content/applications/general/reporting.rst:74 -msgid "Among other measures, you could add the :guilabel:`Margin` and :guilabel:`Count` measures to the Sales Analysis report. By default, the :guilabel:`Untaxed Amount` measure is selected." +#: ../../content/applications/general/integrations/mail_plugins/outlook.rst:102 +msgid "Next, click on :guilabel:`Allow` to open the pop-up window." msgstr "" -#: ../../content/applications/general/reporting.rst:0 -msgid "Selecting different measures on the Sales Analysis report" +#: ../../content/applications/general/integrations/mail_plugins/outlook.rst:-1 +msgid "New window pop-up warning" msgstr "" -#: ../../content/applications/general/reporting.rst:81 -msgid "Group measures" +#: ../../content/applications/general/integrations/mail_plugins/outlook.rst:108 +msgid "If the user isn't logged into the database, enter the credentials. Click on :guilabel:`Allow` to let the Outlook Plugin connect to the database." msgstr "" -#: ../../content/applications/general/reporting.rst:83 -msgid "You could group the measures by :guilabel:`Product Category` at the level of rows on the previous Sales Analysis report example." +#: ../../content/applications/general/integrations/mail_plugins/outlook.rst:-1 +msgid "Allowing the Outlook Plugin to connect to a database" msgstr "" -#: ../../content/applications/general/reporting.rst:0 -msgid "Adding a group on the Sales Analysis report" +#: ../../content/applications/general/integrations/mail_plugins/outlook.rst:118 +msgid "Add a shortcut to the plugin" msgstr "" -#: ../../content/applications/general/reporting.rst:92 -msgid "Using the pivot view" +#: ../../content/applications/general/integrations/mail_plugins/outlook.rst:120 +msgid "By default, the Outlook Plugin can be opened from the *More actions* menu. However, to save time, it's possible to add it next to the other default actions." msgstr "" -#: ../../content/applications/general/reporting.rst:94 -msgid "Grouping data is quintessential to the pivot view. It enables drilling down the data to gain deeper insights. While you can use the :guilabel:`Group By` option to quickly add a group at the level of rows, as shown in the example above, you can also click the plus button (:guilabel:`➕`) next to the :guilabel:`Total` header at the level of rows *and* columns, and then select one of the **preconfigured groups**. To remove one, click the minus button (:guilabel:`➖`)." +#: ../../content/applications/general/integrations/mail_plugins/outlook.rst:123 +msgid "In the Outlook mailbox, click on :guilabel:`Settings`, then on :guilabel:`View all Outlook settings`." msgstr "" -#: ../../content/applications/general/reporting.rst:100 -msgid "Once you have added a group, you can add new ones on the opposite axis or the newly created subgroups." +#: ../../content/applications/general/integrations/mail_plugins/outlook.rst:-1 +msgid "Viewing all Outlook settings" msgstr "" -#: ../../content/applications/general/reporting.rst:104 -msgid "You could further divide the measures on the previous Sales Analysis report example by the :guilabel:`Salesperson` group at the level of columns and by the :guilabel:`Order Date > Month` group on the :guilabel:`All / Saleable / Office Furniture` product category." +#: ../../content/applications/general/integrations/mail_plugins/outlook.rst:130 +msgid "Now, select :guilabel:`Customize actions` under :guilabel:`Mail`, click on :guilabel:`Odoo for Outlook`, and then :guilabel:`Save`." msgstr "" -#: ../../content/applications/general/reporting.rst:0 -msgid "Adding multiple groups on the Sales Analysis report" +#: ../../content/applications/general/integrations/mail_plugins/outlook.rst:-1 +#: ../../content/applications/general/integrations/mail_plugins/outlook.rst:-1 +msgid "Odoo for Outlook customized action" msgstr "" -#: ../../content/applications/general/reporting.rst:112 -msgid "Switch the rows and columns' groups by clicking the flip axis button (:guilabel:`⇄`)." +#: ../../content/applications/general/integrations/mail_plugins/outlook.rst:137 +msgid "Following this step, open any email; the shortcut should be displayed." msgstr "" -#: ../../content/applications/general/reporting.rst:113 -msgid "Click on a measure's label to sort the values by ascending (⏶) or descending (⏷) order." +#: ../../content/applications/general/integrations/mail_plugins/outlook.rst:144 +msgid "Using the plugin" msgstr "" -#: ../../content/applications/general/reporting.rst:114 -msgid "Download a `.xlsx` version of the pivot by clicking the download button (:guilabel:`⭳`)." +#: ../../content/applications/general/integrations/mail_plugins/outlook.rst:146 +msgid "Now that the plug-in is installed and operational, all that needs to be done to create a lead is to click on the `O` [Odoo icon] or navigate to :guilabel:`More actions` and click on :guilabel:`Odoo for Outlook`. The side panel will appear on the right-side, and under :guilabel:`Opportunities` click on :guilabel:`New`. A new window with the created opportunity in the Odoo database will populate." msgstr "" -#: ../../content/applications/general/reporting.rst:119 -msgid "Using the graph view" +#: ../../content/applications/general/integrations/unsplash.rst:3 +msgid "Unsplash" msgstr "" -#: ../../content/applications/general/reporting.rst:121 -msgid "Three graphs are available: the bar, line, and pie charts." +#: ../../content/applications/general/integrations/unsplash.rst:5 +msgid "**Unsplash** is a recognized stock photography library integrated with Odoo." msgstr "" -#: ../../content/applications/general/reporting.rst:123 -msgid "**Bar charts** are used to show the distribution or a comparison of several categories. They are especially useful as they can deal with larger data sets." +#: ../../content/applications/general/integrations/unsplash.rst:7 +msgid "If your database is hosted on **Odoo Online**, you can access Unsplash pictures without configuration." msgstr "" -#: ../../content/applications/general/reporting.rst:126 -msgid "**Line charts** are useful to show changing time series and trends over time." +#: ../../content/applications/general/integrations/unsplash.rst:10 +msgid "If your database is hosted on **Odoo.sh or on-premise**, proceed as follows:" msgstr "" -#: ../../content/applications/general/reporting.rst:128 -msgid "**Pie charts** are used to show the distribution or a comparison of a small number of categories when they form a meaningful whole." +#: ../../content/applications/general/integrations/unsplash.rst:12 +msgid "To **generate an Unsplash access key**, create or sign in to an `Unsplash account `_." msgstr "" -#: ../../content/applications/general/reporting.rst:133 -msgid "Bar chart" +#: ../../content/applications/general/integrations/unsplash.rst:15 +msgid "Access your `applications dashboard `_, click :guilabel:`New Application`, select all checkboxes, and click :guilabel:`Accept terms`." msgstr "" -#: ../../content/applications/general/reporting.rst:0 -msgid "Viewing the Sales Analysis report as a bar chart" +#: ../../content/applications/general/integrations/unsplash.rst:18 +msgid "In the pop-up window, enter your :guilabel:`Application Name`, starting with the prefix `Odoo:` (e.g., `Odoo: connection`), so Unsplash recognizes it as an Odoo instance. Then, add a :guilabel:`Description` and click :guilabel:`Create application`." msgstr "" -#: ../../content/applications/general/reporting.rst:138 -msgid "Line chart" +#: ../../content/applications/general/integrations/unsplash.rst:22 +msgid "On the application details page, scroll down to the :guilabel:`Keys` section and copy the :guilabel:`Access Key` and :guilabel:`Application ID`." msgstr "" -#: ../../content/applications/general/reporting.rst:0 -msgid "Viewing the Sales Analysis report as a line chart" +#: ../../content/applications/general/integrations/unsplash.rst:25 +msgid "In Odoo, go to :menuselection:`General Settings` and enable the :guilabel:`Unsplash Image Library` feature. Then, enter the Unsplash :guilabel:`Access Key` and :guilabel:`Application ID`." msgstr "" -#: ../../content/applications/general/reporting.rst:143 -msgid "Pie chart" +#: ../../content/applications/general/integrations/unsplash.rst:29 +msgid "As a non-Odoo Online user, you are limited to a test key with a maximum of 50 Unsplash requests per hour." msgstr "" -#: ../../content/applications/general/reporting.rst:0 -msgid "Viewing the Sales Analysis report as a pie chart" +#: ../../content/applications/general/iot.rst:8 +msgid "Internet of Things (IoT)" msgstr "" -#: ../../content/applications/general/reporting.rst:149 -msgid "For **bar** and **line** charts, you can use the stacked option when you have at least two groups, which then appear on top of each other instead of next to each other." +#: ../../content/applications/general/iot.rst:17 +msgid "The Open Platform Communications (OPC) Unified Architecture (UA) protocol is now supported by the :abbr:`IoT (Internet of Things)` box. :abbr:`OPC (Open Platform Communications)` :abbr:`UA (United Architecture)` is an open standard that specifies information exchange for industrial communication on devices, between machines and between systems. This includes communication between information technology and operational technology. :abbr:`OPC (Open Platform Communications)` :abbr:`UA (United Architecture)` can be used with any software platform, on a wide variety of devices, and deployed securely. The :abbr:`IoT (Internet of Things)` box has entered the world of the Industry 4.0 standard and can be utilized in a wide variety of industries, and for things like building automation, packaging, utilities, etc." msgstr "" -#: ../../content/applications/general/reporting.rst:154 -msgid "Stacked bar chart" +#: ../../content/applications/general/iot/config/connect.rst:3 +msgid "Connect an IoT box to Odoo" msgstr "" -#: ../../content/applications/general/reporting.rst:0 -msgid "Stacked bar chart example" +#: ../../content/applications/general/iot/config/connect.rst:5 +msgid "An Internet of Things (IoT) box is a micro-computer device that allows for the connection of input and output devices to an Odoo database. An :abbr:`IoT (Internet of Things)` box subscription is required in order to use the :abbr:`IoT (Internet of Things)` box with a secured connection. A computer is also required to set up the :abbr:`IoT (Internet of Things)` box." msgstr "" -#: ../../content/applications/general/reporting.rst:159 -msgid "Regular bar chart" +#: ../../content/applications/general/iot/config/connect.rst:11 +msgid "`IoT Box FAQ `_" msgstr "" -#: ../../content/applications/general/reporting.rst:0 -msgid "Non-stacked bar chart example" +#: ../../content/applications/general/iot/config/connect.rst:13 +msgid "Begin the :abbr:`IoT (Internet of Things)` configuration process by :ref:`installing the IoT app ` on the Odoo database through the :menuselection:`Apps` application." msgstr "" -#: ../../content/applications/general/reporting.rst:164 -msgid "Stacked line chart" +#: ../../content/applications/general/iot/config/connect.rst:-1 +msgid "The Internet of Things (IoT) app on the Odoo database." msgstr "" -#: ../../content/applications/general/reporting.rst:0 -msgid "Stacked line chart example" +#: ../../content/applications/general/iot/config/connect.rst:20 +msgid "Next, after the *IoT app* is installed, navigate to :menuselection:`IoT app --> IoT Boxes`, and then click on the :guilabel:`Connect` button located in the upper-left corner of the :menuselection:`IoT Boxes` dashboard." msgstr "" -#: ../../content/applications/general/reporting.rst:169 -#: ../../content/applications/general/reporting.rst:184 -msgid "Regular line chart" +#: ../../content/applications/general/iot/config/connect.rst:-1 +msgid "Connecting an IoT box to the Odoo database." msgstr "" -#: ../../content/applications/general/reporting.rst:0 -msgid "Non-stacked line chart example" +#: ../../content/applications/general/iot/config/connect.rst:28 +msgid "There are two recommended ways to connect the :abbr:`IoT (Internet of Things)` box to the database once the *IoT app* is installed. Follow the steps in either of the next two sections to connect the :abbr:`IoT (Internet of Things)` box via :ref:`wired ethernet connection ` or via :ref:`WiFi `." msgstr "" -#: ../../content/applications/general/reporting.rst:174 -msgid "For **line** charts, you can use the cumulative option to sum values, which is especially useful to show the change in growth over a time period." +#: ../../content/applications/general/iot/config/connect.rst:-1 +msgid "Connection steps for a wired connection or WiFi connection." msgstr "" -#: ../../content/applications/general/reporting.rst:179 -msgid "Cumulative line chart" +#: ../../content/applications/general/iot/config/connect.rst:38 +msgid "The disk image that the :abbr:`IoT (Internet of Things)` box SD card is formatted with is unique to the version of the Odoo database that the :abbr:`IoT (Internet of Things)` box is running on. Ensure that the :abbr:`IoT (Internet of Things)` box is :ref:`flashed ` with the most up-to-date disk image." msgstr "" -#: ../../content/applications/general/reporting.rst:0 -msgid "Cumulative line chart example" +#: ../../content/applications/general/iot/config/connect.rst:46 +msgid "Ethernet connection" msgstr "" -#: ../../content/applications/general/reporting.rst:0 -msgid "Regular line chart example" +#: ../../content/applications/general/iot/config/connect.rst:48 +msgid "The following is the process to connect the :abbr:`IoT (Internet of Things)` box via an ethernet cable to the Odoo database (by way of the ethernet port; RJ-45)." msgstr "" -#: ../../content/applications/general/search.rst:3 -msgid "Search and filter records" +#: ../../content/applications/general/iot/config/connect.rst:51 +msgid "First, connect all wired devices to the :abbr:`IoT (Internet of Things)` box (ethernet, :abbr:`USB (Universal Serial Bus)` devices, etc.). At minimum, an HDMI screen should be connected. Then, plug the :abbr:`IoT (Internet of Things)` box into a power source." msgstr "" -#: ../../content/applications/general/search.rst:5 -msgid "Odoo uses filters to include only the most relevant records depending on the purpose of the view you are on. However, you can edit the default filter or search for specific values." +#: ../../content/applications/general/iot/config/connect.rst:55 +msgid "Immediately after the unit powers on and boots up, read the *pairing code* from the screen or from the printout of a receipt printer connected to the :abbr:`IoT (Internet of Things)` box." msgstr "" -#: ../../content/applications/general/search.rst:11 -msgid "Preconfigured filters" +#: ../../content/applications/general/iot/config/connect.rst:59 +msgid "By default, the :abbr:`IoT (Internet of Things)` box will display the *pairing code* for a maximum of 5 minutes after the unit boots up. After 5 minutes, the *pairing code* will disappear for security purposes and the :abbr:`IoT (Internet of Things)` box will need to be rebooted manually by unplugging the unit from the power source for ten seconds and re-plugging it back in." msgstr "" -#: ../../content/applications/general/search.rst:13 -msgid "You can modify the default selection of records by clicking :guilabel:`Filters` and selecting one or several **preconfigured filters**." +#: ../../content/applications/general/iot/config/connect.rst:65 +msgid "If no screen is attached to the :abbr:`IoT (Internet of Things)` box, then the *pairing code* can be accessed from the :abbr:`IoT (Internet of Things)` box homepage by clicking on the :guilabel:`POS Display` button. For instructions on how to access the :abbr:`IoT (Internet of Things)` box homepage visit :ref:`iot_connect/token`." msgstr "" -#: ../../content/applications/general/search.rst:17 -msgid "On the Sales Analysis report, only records at the sales order stage are selected by default. However, you could *also* include records at the quotation stage by selecting :guilabel:`Quotations`. Furthermore, you could *only* include records from a specific year, for example *2022*, by selecting :menuselection:`Order Date --> 2022`." +#: ../../content/applications/general/iot/config/connect.rst:70 +msgid "On the computer, navigate to :menuselection:`IoT app --> IoT Boxes`, and then click on the :guilabel:`Connect` button located in the upper-left corner of the the :menuselection:`IoT Boxes` dashboard. Input the *pairing code* in the :guilabel:`Pairing Code` field and click on the :guilabel:`Pair` button. The database will now link to the :abbr:`IoT (Internet of Things)` box and it will appear on the :menuselection:`IoT Boxes` page." msgstr "" -#: ../../content/applications/general/search.rst:0 -msgid "Using preconfigured filters on the Sales Analysis report" +#: ../../content/applications/general/iot/config/connect.rst:79 +msgid "WiFi connection" msgstr "" -#: ../../content/applications/general/search.rst:27 -msgid "If you select preconfigured filters from the same group (i.e., that are *not* separated by an horizontal line), the records can match *any* condition to be included. However, if you select filters from different groups, the records have to match *all* condition to be included." +#: ../../content/applications/general/iot/config/connect.rst:81 +msgid "The following is the process to connect the :abbr:`IoT (Internet of Things)` box via a WiFi connection to the Odoo database." msgstr "" -#: ../../content/applications/general/search.rst:34 -msgid "Custom filters" +#: ../../content/applications/general/iot/config/connect.rst:84 +msgid "First, ensure there is no ethernet cable plugged into the :abbr:`IoT (Internet of Things)` box. Then, connect all wired devices to the :abbr:`IoT (Internet of Things)` box (:abbr:`USB (Universal Serial Bus)` devices, etc.)." msgstr "" -#: ../../content/applications/general/search.rst:36 -msgid "You can create custom filters using most fields present on the model by clicking :menuselection:`Filters --> Add Custom Filter`, selecting a field, an operator, a value, and clicking :guilabel:`Apply`." +#: ../../content/applications/general/iot/config/connect.rst:88 +msgid "After connecting the devices, plug the :abbr:`IoT (Internet of Things)` box into to a power source. On the computer, navigate to :menuselection:`IoT app --> IoT Boxes`, and then click on the :guilabel:`Connect` button located in the upper-left corner of the the :menuselection:`IoT Boxes` dashboard. Then copy the :guilabel:`Token` from the :guilabel:`WiFi connection` section as this will later be used to link the Odoo database to the :abbr:`IoT (Internet of Things)` box." msgstr "" -#: ../../content/applications/general/search.rst:41 -msgid "You could *only* include records from a single salesperson on the Sales Analysis report, for example *Mitchell Admin*, by selecting :guilabel:`Salesperson` as the field, :guilabel:`is equal to` as the operator, and typing `Mitchell Admin` as the value." +#: ../../content/applications/general/iot/config/connect.rst:94 +msgid "Back on the computer, navigate to the available WiFi networks and connect to the :abbr:`IoT (Internet of Things)` box WiFi network. The WiFi network dispersed by the :abbr:`IoT (Internet of Things)` box will start with `IoTBox-xxxxxxxxxx`." msgstr "" -#: ../../content/applications/general/search.rst:0 -msgid "Using a custom filter on the Sales Analysis report" +#: ../../content/applications/general/iot/config/connect.rst:-1 +msgid "WiFi networks available on the computer." msgstr "" -#: ../../content/applications/general/search.rst:50 -msgid "If the records should *only* match one of several conditions, click :guilabel:`Add a condition` before applying a custom filter. If the records should match *all* conditions, add new custom filters instead." +#: ../../content/applications/general/iot/config/connect.rst:102 +msgid "Upon connecting to the :abbr:`IoT (Internet of Things)` box WiFi, a browser will automatically redirect to the :menuselection:`Configure Iot Box` wizard. Name the :abbr:`IoT (Internet of Things)` box, then paste the previously copied *token* into the :guilabel:`Server Token` field, and then click on :guilabel:`Next`." msgstr "" -#: ../../content/applications/general/search.rst:57 -msgid "Search for values" +#: ../../content/applications/general/iot/config/connect.rst:-1 +msgid "Enter the server token into the IoT box." msgstr "" -#: ../../content/applications/general/search.rst:59 -msgid "You can use the search field to quickly look for specific values and add them as a filter. Either type the full value you are searching for and select the desired field, or type a part of the value, click the dropdown button (:guilabel:`⏵`) before the chosen field, and select the exact value you are looking for." +#: ../../content/applications/general/iot/config/connect.rst:112 +msgid "If the :abbr:`IoT (Internet of Things)` box WiFi connection wizard doesn't start, then see the documentation on :ref:`connecting with a token `." msgstr "" -#: ../../content/applications/general/search.rst:65 -msgid "Instead of adding a custom filter to select records where *Mitchell Admin* is the salesperson on the Sales Analysis report, you could search for `Mitch`, click the dropdown button (:guilabel:`⏵`) next to :guilabel:`Search Salesperson for: Mitch`, and select :guilabel:`Mitchell Admin`." +#: ../../content/applications/general/iot/config/connect.rst:115 +msgid "Now, choose the WiFi network that the :abbr:`IoT (Internet of Things)` box will connect with (enter the password if there is one) and click on :guilabel:`Connect`. Wait a few seconds and the browser will redirect to the :abbr:`IoT (Internet of Things)` box homepage. The computer may need to be manually re-connected back to the original WiFi connection, if this does not happen automatically." msgstr "" -#: ../../content/applications/general/search.rst:0 -msgid "Searching for a specific value on the Sales Analysis report" +#: ../../content/applications/general/iot/config/connect.rst:-1 +msgid "Configuring the WiFi for the IoT box." msgstr "" -#: ../../content/applications/general/search.rst:75 -msgid "Using the search field is equivalent to using the *contains* operator when adding a custom filter. If you enter a partial value and directly select the desired field, *all* records containing the characters you typed for the selected field will be included." +#: ../../content/applications/general/iot/config/connect.rst:124 +msgid "After completing each step, the :abbr:`IoT (Internet of Things)` box should appear when navigating to :menuselection:`IoT app --> IoT Boxes` on the Odoo database." msgstr "" -#: ../../content/applications/general/search.rst:82 -msgid "Group records" +#: ../../content/applications/general/iot/config/connect.rst:-1 +msgid "The IoT box has been successfully configured on the Odoo database." msgstr "" -#: ../../content/applications/general/search.rst:84 -msgid "You can click :guilabel:`Group By` below the search field to cluster records together according to one of the **preconfigured groups**." +#: ../../content/applications/general/iot/config/connect.rst:132 +msgid "The :abbr:`IoT (Internet of Things)` box may need to be manually rebooted upon successfully connecting via WiFi for the box to appear in the *IoT app* on the Odoo database. To do so, simply unplug the device and plug it back into the power source after ten seconds." msgstr "" -#: ../../content/applications/general/search.rst:88 -msgid "You could group the records by salesperson on the Sales Analysis report by clicking :guilabel:`Group By` and selecting :guilabel:`Salesperson`. No records are filtered out." +#: ../../content/applications/general/iot/config/connect.rst:139 +msgid "Manually connecting the IoT box using the token" msgstr "" -#: ../../content/applications/general/search.rst:0 -msgid "Grouping records on the Sales Analysis report" +#: ../../content/applications/general/iot/config/connect.rst:141 +msgid "A manual connection of the :abbr:`IoT (Internet of Things)` box to the :abbr:`IoT (Internet of Things)` app can be made using the *token*, from a computer. The *token* can be found by navigating to :menuselection:`IoT app --> IoT Boxes` and clicking on :guilabel:`Connect`." msgstr "" -#: ../../content/applications/general/search.rst:95 -msgid "You can **customize groups** by using a wide selection of fields present on the model. To do so, click :menuselection:`Group By --> Add Custom Group`, select a field, and click :guilabel:`Apply`." +#: ../../content/applications/general/iot/config/connect.rst:145 +msgid "Under the :guilabel:`WiFi Connection` section of the :guilabel:`Connect an IoT Box` page that appears, click :guilabel:`Copy` to the right of the :guilabel:`Token`. This token will be entered into the :abbr:`IoT (Internet of Things)` box homepage." msgstr "" -#: ../../content/applications/general/search.rst:99 -msgid "You can use several groups at the same time. The first group you select is the main cluster, the next one you add further divides the main group's categories, and so on." +#: ../../content/applications/general/iot/config/connect.rst:149 +msgid "Access the :abbr:`IoT (Internet of Things)` box homepage by entering the :abbr:`IP (Internet Protocol)` address of the :abbr:`IoT (Internet of Things)` box into a browser window from a computer on the same network as the :abbr:`IoT (Internet of Things)` box (preferably by ethernet connection)." +msgstr "" + +#: ../../content/applications/general/iot/config/connect.rst:154 +msgid "The :abbr:`IP (Internet Protocol)` address can be accessed by the router admin console that the :abbr:`IoT (Internet of Things)` box is connected to, or by connecting a receipt printer to the :abbr:`IoT (Internet of Things)` box. A receipt will print out with the :abbr:`IoT (Internet of Things)` box's :abbr:`IP (Internet Protocol)` address on it." +msgstr "" + +#: ../../content/applications/general/iot/config/connect.rst:159 +msgid "On the :abbr:`IoT (Internet of Things)` box homepage, enter the *token* under the :guilabel:`Server` section by clicking on :guilabel:`Configure`. Then, paste the *token* into the :guilabel:`Server Token` field and click :guilabel:`Connect`. The :abbr:`IoT (Internet of Things)` box will then link to the Odoo database." +msgstr "" + +#: ../../content/applications/general/iot/config/connect.rst:167 +msgid "IoT box schema" +msgstr "" + +#: ../../content/applications/general/iot/config/connect.rst:170 +msgid "Raspberry Pi 4" +msgstr "" + +#: ../../content/applications/general/iot/config/connect.rst:174 +msgid "The Odoo IoT box (Raspberry Pi 4) schema with labels." +msgstr "" + +#: ../../content/applications/general/iot/config/connect.rst:177 +msgid "Raspberry Pi 3" +msgstr "" + +#: ../../content/applications/general/iot/config/connect.rst:181 +msgid "The Odoo IoT box (Raspberry Pi 3) schema with labels." +msgstr "" + +#: ../../content/applications/general/iot/config/https_certificate_iot.rst:5 +msgid "HTTPS certificate (IoT)" +msgstr "" + +#: ../../content/applications/general/iot/config/https_certificate_iot.rst:8 +msgid "What is HTTPS?" +msgstr "" + +#: ../../content/applications/general/iot/config/https_certificate_iot.rst:10 +msgid "*Hypertext Transfer Protocol Secure* (HTTPS) is the secure version of *Hypertext Transfer Protocol* (HTTP), which is the primary protocol used to send data back and forth between a web browser and a website. :abbr:`HTTPS (Hypertext Transfer Protocol Secure)` is encrypted in order to increase the security of data transfer." +msgstr "" + +#: ../../content/applications/general/iot/config/https_certificate_iot.rst:15 +msgid ":abbr:`HTTPS (Hypertext Transfer Protocol Secure)` uses an encryption protocol to encrypt communications. The protocol is called *Transport Layer Security* (TLS), although formerly it was known as *Secure Sockets Layer* (SSL)." +msgstr "" + +#: ../../content/applications/general/iot/config/https_certificate_iot.rst:19 +msgid ":abbr:`HTTPS (Hypertext Transfer Protocol Secure)` occurs based upon the transmission of :abbr:`TLS (Transport Layer Security)`/:abbr:`SSL (Secure Sockets Layer)` certificates, which verify that a particular provider is who they say they are." +msgstr "" + +#: ../../content/applications/general/iot/config/https_certificate_iot.rst:24 +msgid "In this documentation and throughout Odoo the term \"HTTPS certificate\" will be used to define the fact that the :abbr:`SSL (Secure Sockets Layer)` certificate is valid and allows a :abbr:`HTTPS (Hypertext Transfer Protocol Secure)` connection." +msgstr "" + +#: ../../content/applications/general/iot/config/https_certificate_iot.rst:29 +msgid "Why is it needed?" +msgstr "" + +#: ../../content/applications/general/iot/config/https_certificate_iot.rst:31 +msgid "In order to communicate with certain network devices (in particular for payment terminals), the usage of :abbr:`HTTPS (Hypertext Transfer Protocol Secure)` is mandatory. If the :abbr:`HTTPS (Hypertext Transfer Protocol Secure)` certificate isn't valid, some devices won't be able to interact with the :abbr:`IoT (Internet of Things)` Box." +msgstr "" + +#: ../../content/applications/general/iot/config/https_certificate_iot.rst:37 +msgid "How to obtain a Hypertext Transfer Protocol Secure (HTTPS) certificate" +msgstr "" + +#: ../../content/applications/general/iot/config/https_certificate_iot.rst:39 +msgid "The generation of the :abbr:`HTTPS (Hypertext Transfer Protocol Secure)` certificate is automatic." +msgstr "" + +#: ../../content/applications/general/iot/config/https_certificate_iot.rst:41 +msgid "The :abbr:`IoT (Internet of Things)` Box will send a specific request to ``_ which will send back the :abbr:`HTTPS (Hypertext Transfer Protocol Secure)` certificate if the :abbr:`IoT (Internet of Things)` box and database are eligible." +msgstr "" + +#: ../../content/applications/general/iot/config/https_certificate_iot.rst:48 +msgid "Internet of Things (IoT) eligibility" +msgstr "" + +#: ../../content/applications/general/iot/config/https_certificate_iot.rst:50 +msgid "The database should be a **production** instance. The database instance should not be a copy, a duplicate, a staging, or a development environment." +msgstr "" + +#: ../../content/applications/general/iot/config/https_certificate_iot.rst:52 +msgid "The Odoo subscription must:" +msgstr "" + +#: ../../content/applications/general/iot/config/https_certificate_iot.rst:54 +msgid "Have an :guilabel:`IoT Box Subscription` line." +msgstr "" + +#: ../../content/applications/general/iot/config/https_certificate_iot.rst:55 +msgid ":guilabel:`Status` must be :guilabel:`In Progress`." +msgstr "" + +#: ../../content/applications/general/iot/config/https_certificate_iot.rst:57 +msgid "If the subscription is linked to a ``_ portal user check the information on the portal subscription page." +msgstr "" + +#: ../../content/applications/general/iot/config/https_certificate_iot.rst:0 +msgid "Odoo.com portal subscriptions filtered by \"in progress\"." +msgstr "" + +#: ../../content/applications/general/iot/config/https_certificate_iot.rst:64 +msgid "In this case, both subscriptions are considered \"in progress\" as the :guilabel:`Filter By\\: In Progress` was used." +msgstr "" + +#: ../../content/applications/general/iot/config/https_certificate_iot.rst:68 +msgid "If the subscription is in question, contact the database's Account Manager or Partner regarding the matter." +msgstr "" + +#: ../../content/applications/general/iot/config/https_certificate_iot.rst:72 +msgid "Troubleshooting Hypertext Transfer Protocol Secure (HTTPS) certificate errors" +msgstr "" + +#: ../../content/applications/general/iot/config/https_certificate_iot.rst:74 +msgid "If anything goes wrong during the process of the \"HTTPS certificate\" generation or reception, a specific error will code be given on the :abbr:`IoT (Internet of Things)` box home page." +msgstr "" + +#: ../../content/applications/general/iot/config/https_certificate_iot.rst:78 +msgid "Accessing the :abbr:`IoT (Internet of Things)` box homepage will check for the presence of the \"HTTPS certificate\" and will attempt its generation if it is missing. As such, if there is an error on the :abbr:`IoT (Internet of Things)` box home page, refresh the :abbr:`IoT (Internet of Things)` home page to see if the error disappears." +msgstr "" + +#: ../../content/applications/general/iot/config/https_certificate_iot.rst:84 +msgid "`ERR_IOT_HTTPS_CHECK_NO_SERVER`" +msgstr "" + +#: ../../content/applications/general/iot/config/https_certificate_iot.rst:88 +#: ../../content/applications/general/iot/config/https_certificate_iot.rst:101 +#: ../../content/applications/general/iot/config/https_certificate_iot.rst:110 +#: ../../content/applications/general/iot/config/https_certificate_iot.rst:132 +#: ../../content/applications/general/iot/config/https_certificate_iot.rst:149 +#: ../../content/applications/general/iot/config/https_certificate_iot.rst:166 +msgid "Reason:" +msgstr "" + +#: ../../content/applications/general/iot/config/https_certificate_iot.rst:87 +msgid "The configuration regarding the server is missing. In other words, the Odoo instance is not connected with the IoT box." +msgstr "" + +#: ../../content/applications/general/iot/config/https_certificate_iot.rst:91 +#: ../../content/applications/general/iot/config/https_certificate_iot.rst:104 +#: ../../content/applications/general/iot/config/https_certificate_iot.rst:114 +#: ../../content/applications/general/iot/config/https_certificate_iot.rst:137 +#: ../../content/applications/general/iot/config/https_certificate_iot.rst:159 +#: ../../content/applications/general/iot/config/https_certificate_iot.rst:170 +msgid "Solution:" +msgstr "" + +#: ../../content/applications/general/iot/config/https_certificate_iot.rst:91 +msgid "Ensure that the server is configured." +msgstr "" + +#: ../../content/applications/general/iot/config/https_certificate_iot.rst:94 +#: ../../content/applications/general/iot/config/windows_iot.rst:121 +msgid ":doc:`/applications/general/iot/config/connect`" +msgstr "" + +#: ../../content/applications/general/iot/config/https_certificate_iot.rst:97 +msgid "`ERR_IOT_HTTPS_CHECK_CERT_READ_EXCEPTION`" +msgstr "" + +#: ../../content/applications/general/iot/config/https_certificate_iot.rst:100 +msgid "An unhandled error happened when trying to read the existing :abbr:`HTTPS (Hypertext Transfer Protocol Secure)` certificate." +msgstr "" + +#: ../../content/applications/general/iot/config/https_certificate_iot.rst:104 +msgid "Ensure that the :abbr:`HTTPS (Hypertext Transfer Protocol Secure)` certificate file is readable." +msgstr "" + +#: ../../content/applications/general/iot/config/https_certificate_iot.rst:107 +msgid "`ERR_IOT_HTTPS_LOAD_NO_CREDENTIAL`" +msgstr "" + +#: ../../content/applications/general/iot/config/https_certificate_iot.rst:110 +msgid "The contract and/or database :abbr:`UUID (Universal Unique Identifier)` is missing." +msgstr "" + +#: ../../content/applications/general/iot/config/https_certificate_iot.rst:113 +msgid "Ensure that both values are configured as intended. To modify them, go to the :abbr:`IoT (Internet of Things)` box home page, and navigate to :guilabel:`Credential`." +msgstr "" + +#: ../../content/applications/general/iot/config/https_certificate_iot.rst:117 +msgid "`ERR_IOT_HTTPS_LOAD_REQUEST_EXCEPTION`" +msgstr "" + +#: ../../content/applications/general/iot/config/https_certificate_iot.rst:120 +msgid "An unexpected error happened when the :abbr:`IoT (Internet of Things)` box tried to reach ``_. The causes are likely due to the network infrastructure/configuration:" +msgstr "" + +#: ../../content/applications/general/iot/config/https_certificate_iot.rst:124 +msgid "The :abbr:`IoT (Internet of Things)` box does not have access to internet." +msgstr "" + +#: ../../content/applications/general/iot/config/https_certificate_iot.rst:125 +msgid "The network does not allow the :abbr:`IoT (Internet of Things)` box to communicate with ``_. This may be due to network devices preventing the communication (firewalls, etc.) or the network configuration (:abbr:`VPN (Virtual Private Network)`, etc.)." +msgstr "" + +#: ../../content/applications/general/iot/config/https_certificate_iot.rst:131 +msgid "More information regarding the error that occurred can be found in the full request exception details, which are in the :abbr:`IoT (Internet of Things)` box logs." +msgstr "" + +#: ../../content/applications/general/iot/config/https_certificate_iot.rst:136 +msgid "Consult with your system or network administrator should this issue arise. This error code depends on the network infrastructure and goes beyond Odoo support's service scope." +msgstr "" + +#: ../../content/applications/general/iot/config/https_certificate_iot.rst:140 +msgid "`ERR_IOT_HTTPS_LOAD_REQUEST_STATUS`" +msgstr "" + +#: ../../content/applications/general/iot/config/https_certificate_iot.rst:143 +msgid "The IoT-box was able to reach ``_ but received an unusual `HTTP response (status codes) `_." +msgstr "" + +#: ../../content/applications/general/iot/config/https_certificate_iot.rst:147 +msgid "This error code will also give the HTTP response status codes. For example, if the error reads `ERR_IOT_HTTPS_LOAD_REQUEST_STATUS 404` it means that the page returned a 404 error, which is the \"Page Not Found\" code." +msgstr "" + +#: ../../content/applications/general/iot/config/https_certificate_iot.rst:152 +msgid "Check if ``_ is down using a web browser, as it's possible that it is down due to maintenance." +msgstr "" + +#: ../../content/applications/general/iot/config/https_certificate_iot.rst:155 +msgid "If ``_ is down due to maintenance, unfortunately there is nothing that can be done but instead wait for it to recover." +msgstr "" + +#: ../../content/applications/general/iot/config/https_certificate_iot.rst:157 +msgid "If ``_ is not down due to maintenance, open a `support ticket `_ on the matter. Ensure that the 3 digits status code next to the code error is included in the support ticket." +msgstr "" + +#: ../../content/applications/general/iot/config/https_certificate_iot.rst:162 +msgid "`ERR_IOT_HTTPS_LOAD_REQUEST_NO_RESULT`" +msgstr "" + +#: ../../content/applications/general/iot/config/https_certificate_iot.rst:165 +msgid "The :abbr:`IoT (Internet of Things)` box was able to reach ``_ but it refused to deliver the :abbr:`HTTPS (Hypertext Transfer Protocol Secure)` certificate." +msgstr "" + +#: ../../content/applications/general/iot/config/https_certificate_iot.rst:169 +msgid "Ensure that the :abbr:`IoT (Internet of Things)` box and database are eligible for a certificate: :ref:`Internet of Things (IoT) eligibility `." +msgstr "" + +#: ../../content/applications/general/iot/config/https_certificate_iot.rst:173 +msgid "How to ensure that the HTTPS certificate is correct" +msgstr "" + +#: ../../content/applications/general/iot/config/https_certificate_iot.rst:175 +msgid "If the certificate has been applied successfully, a new :abbr:`HTTPS (Hypertext Transfer Protocol Secure)` :abbr:`URL (Uniform Resource Locator)` for the :abbr:`IoT (Internet of Things)` box ending with `.odoo-iot.com` will appear on the Odoo database, inside of the :menuselection:`IoT` application on that specific device's form." +msgstr "" + +#: ../../content/applications/general/iot/config/https_certificate_iot.rst:-1 +msgid "Odoo IoT app IoT box with .odoo-iot.com domain." +msgstr "" + +#: ../../content/applications/general/iot/config/https_certificate_iot.rst:184 +msgid "When navigating to the :abbr:`URL (Uniform Resource Locator)` in a browser a secured :abbr:`HTTPS (Hypertext Transfer Protocol Secure)` connection will be established." +msgstr "" + +#: ../../content/applications/general/iot/config/https_certificate_iot.rst:191 +msgid "Example of valid SSL certificate details on the browser." +msgstr "" + +#: ../../content/applications/general/iot/config/https_certificate_iot.rst:191 +msgid "Padlock in Chrome on Windows 10 attesting the fact that the connection is secured in :abbr:`HTTPS (Hypertext Transfer Protocol Secure)`." +msgstr "" + +#: ../../content/applications/general/iot/config/https_certificate_iot.rst:194 +msgid "The IoT-box homepage will now display an `OK` status next to `HTTPS certificate`. The drop-down menu icon, when clicked, will reveal information regarding the certificate." +msgstr "" + +#: ../../content/applications/general/iot/config/https_certificate_iot.rst:-1 +msgid "IoT box homepage with HTTPS certificate OK status." +msgstr "" + +#: ../../content/applications/general/iot/config/https_certificate_iot.rst:202 +msgid "Domain Name System (DNS) issue" +msgstr "" + +#: ../../content/applications/general/iot/config/https_certificate_iot.rst:204 +msgid "If the :abbr:`IoT (Internet of Things)` box can be accessed from its :abbr:`IP (Intrernet Protocol)` address but not the Odoo assigned domain: `.odoo-iot.com`; then the :abbr:`IoT (Internet of Things)` box is likely running into a :abbr:`DNS (Domain Name System)` issue. On some browsers, it will give an error code mentioning :abbr:`DNS (Domain Name System)` (like `DNS_PROBE_FINISHED_NXDOMAIN`)." +msgstr "" + +#: ../../content/applications/general/iot/config/https_certificate_iot.rst:209 +msgid "These :abbr:`DNS (Domain Name System)` issues may appear as the following in different browsers:" +msgstr "" + +#: ../../content/applications/general/iot/config/https_certificate_iot.rst:213 +msgid "Chrome" +msgstr "" + +#: ../../content/applications/general/iot/config/https_certificate_iot.rst:0 +#: ../../content/applications/general/iot/config/https_certificate_iot.rst:219 +msgid "DNS issue on Chrome browser on Windows 10." +msgstr "" + +#: ../../content/applications/general/iot/config/https_certificate_iot.rst:222 +msgid "Firefox" +msgstr "" + +#: ../../content/applications/general/iot/config/https_certificate_iot.rst:0 +#: ../../content/applications/general/iot/config/https_certificate_iot.rst:228 +msgid "DNS issue on Firefox browser on Windows 10." +msgstr "" + +#: ../../content/applications/general/iot/config/https_certificate_iot.rst:230 +msgid "Edge" +msgstr "" + +#: ../../content/applications/general/iot/config/https_certificate_iot.rst:0 +#: ../../content/applications/general/iot/config/https_certificate_iot.rst:236 +msgid "DNS issue on Edge browser on Windows 10." +msgstr "" + +#: ../../content/applications/general/iot/config/https_certificate_iot.rst:240 +msgid "Domain Name System (DNS) issue solution" +msgstr "" + +#: ../../content/applications/general/iot/config/https_certificate_iot.rst:242 +msgid "Should the router allow the :abbr:`DNS (Domain Name System)` to be manually changed, change the DNS to use `Google DNS `_." +msgstr "" + +#: ../../content/applications/general/iot/config/https_certificate_iot.rst:244 +msgid "If your router doesn't allow for this, then a change will need to be made on the :abbr:`DNS (Domain Name System)` settings of each of the devices using `Google DNS `_. This will need to occur on **every** device that plans to interact with the :abbr:`IoT (Internet of Things)` box (e.g. computer, tablet or phone). The individual device configuration processes can be found on the website of the device's manufacturer." +msgstr "" + +#: ../../content/applications/general/iot/config/https_certificate_iot.rst:252 +msgid "Other :abbr:`IoT (Internet of Things)` devices such as payment terminals likely won't need their :abbr:`DNS (Domain Name System)` settings changed as they are already configured with custom :abbr:`DNS (Domain Name System)`." +msgstr "" + +#: ../../content/applications/general/iot/config/https_certificate_iot.rst:257 +msgid "Consult with your system or network administrator should this issue arise. This error code depends on the network infrastructure, and it goes beyond Odoo support's service scope." +msgstr "" + +#: ../../content/applications/general/iot/config/pos.rst:3 +msgid "Use an IoT box with a PoS" +msgstr "" + +#: ../../content/applications/general/iot/config/pos.rst:6 +msgid "Prerequisites" +msgstr "" + +#: ../../content/applications/general/iot/config/pos.rst:8 +msgid "Before starting, make sure the following equipment is available:" +msgstr "" + +#: ../../content/applications/general/iot/config/pos.rst:10 +msgid "An :abbr:`IoT (Internet of Things)` box, with its power adapter." +msgstr "" + +#: ../../content/applications/general/iot/config/pos.rst:11 +msgid "A computer or tablet with an up-to-date web browser." +msgstr "" + +#: ../../content/applications/general/iot/config/pos.rst:12 +msgid "Odoo Online or an Odoo instance with the *Point of Sale* and *IoT* applications installed." +msgstr "" + +#: ../../content/applications/general/iot/config/pos.rst:13 +msgid "A local network set up with :abbr:`DHCP (Dynamic Host Configuration Protocol)` (this is the default setting)." +msgstr "" + +#: ../../content/applications/general/iot/config/pos.rst:15 +msgid "An RJ45 Ethernet Cable (optional, but preferred over WiFi, which is already built in)." +msgstr "" + +#: ../../content/applications/general/iot/config/pos.rst:16 +msgid "Any of the supported hardware (receipt printer, barcode scanner, cash drawer, payment terminal, scale, customer display, etc.). The list of supported hardware can be found on the `POS Hardware page `_." +msgstr "" + +#: ../../content/applications/general/iot/config/pos.rst:25 +msgid "A suggested configuration for a point of sale system." +msgstr "" + +#: ../../content/applications/general/iot/config/pos.rst:27 +msgid "To connect hardware to the :abbr:`PoS (Point of Sale)`, the first step is to connect an :abbr:`IoT (Internet of Things)` box to the database. To do this, follow these instructions: :doc:`Connect an Internet of Things (IoT) box to the Odoo database `." +msgstr "" + +#: ../../content/applications/general/iot/config/pos.rst:31 +msgid "Then, connect the peripheral devices to the :abbr:`IoT (Internet of Things)` box." +msgstr "" + +#: ../../content/applications/general/iot/config/pos.rst:37 +msgid "Device Name" +msgstr "" + +#: ../../content/applications/general/iot/config/pos.rst:38 +msgid "Instructions" +msgstr "" + +#: ../../content/applications/general/iot/config/pos.rst:39 +#: ../../content/applications/general/iot/config/troubleshooting.rst:66 +msgid "Printer" +msgstr "" + +#: ../../content/applications/general/iot/config/pos.rst:40 +msgid "Connect a supported receipt printer to a :abbr:`USB (Universal Serial Bus)` port or to the network, and power it on. Refer to :doc:`/applications/sales/point_of_sale/restaurant/kitchen_printing`." +msgstr "" + +#: ../../content/applications/general/iot/config/pos.rst:43 +#: ../../content/applications/general/iot/config/troubleshooting.rst:412 +msgid "Cash drawer" +msgstr "" + +#: ../../content/applications/general/iot/config/pos.rst:44 +msgid "The cash drawer should be connected to the printer with an RJ25 cable." +msgstr "" + +#: ../../content/applications/general/iot/config/pos.rst:45 +#: ../../content/applications/general/iot/config/troubleshooting.rst:360 +msgid "Barcode scanner" +msgstr "" + +#: ../../content/applications/general/iot/config/pos.rst:46 +msgid "In order for the barcode scanner to be compatible it must end barcodes with an `ENTER` character (keycode 28). This is most likely the default configuration of the barcode scanner." +msgstr "" + +#: ../../content/applications/general/iot/config/pos.rst:48 +#: ../../content/applications/general/iot/config/troubleshooting.rst:423 +msgid "Scale" +msgstr "" + +#: ../../content/applications/general/iot/config/pos.rst:49 +msgid "Connect the scale and power it on. Refer to :doc:`../devices/scale`." +msgstr "" + +#: ../../content/applications/general/iot/config/pos.rst:51 +msgid "Customer display" +msgstr "" + +#: ../../content/applications/general/iot/config/pos.rst:52 +msgid "Connect a screen to the :abbr:`IoT (Internet of Things)` box to display the :abbr:`PoS (Point of Sale)` order. Refer to :doc:`../devices/screen`." +msgstr "" + +#: ../../content/applications/general/iot/config/pos.rst:54 +msgid "Payment terminal" +msgstr "" + +#: ../../content/applications/general/iot/config/pos.rst:55 +msgid "The connection process depends on the terminal. Refer to the :doc:`payment terminals documentation `." +msgstr "" + +#: ../../content/applications/general/iot/config/pos.rst:58 +msgid "Once this is completed, connect the :abbr:`IoT (Internet of Things)` box to the :menuselection:`PoS` application. To do this, go to :menuselection:`Point of Sale --> Configuration --> PoS`, tick the :guilabel:`IoT Box` option, and select the devices to be used in this :abbr:`PoS (Point of Sale)`. :guilabel:`Save` the the changes." +msgstr "" + +#: ../../content/applications/general/iot/config/pos.rst:-1 +msgid "Configuring the connected devices in the POS application." +msgstr "" + +#: ../../content/applications/general/iot/config/pos.rst:67 +msgid "Once set up is done, a new :abbr:`PoS (Point of Sale)` session can be launched." +msgstr "" + +#: ../../content/applications/general/iot/config/troubleshooting.rst:3 +#: ../../content/applications/general/iot/config/windows_iot.rst:127 +msgid "Troubleshooting" +msgstr "" + +#: ../../content/applications/general/iot/config/troubleshooting.rst:6 +msgid "IoT box connection" +msgstr "" + +#: ../../content/applications/general/iot/config/troubleshooting.rst:9 +msgid "Unable to locate the pairing code to connect the IoT box" +msgstr "" + +#: ../../content/applications/general/iot/config/troubleshooting.rst:11 +msgid "The pairing code should be printed on receipt printers connected to the :abbr:`IoT (Internet of Things)` box and should also be displayed on connected monitors." +msgstr "" + +#: ../../content/applications/general/iot/config/troubleshooting.rst:14 +msgid "The pairing code does not show under the following circumstances:" +msgstr "" + +#: ../../content/applications/general/iot/config/troubleshooting.rst:16 +msgid "The :abbr:`IoT (Internet of Things)` box is already connected to an Odoo database." +msgstr "" + +#: ../../content/applications/general/iot/config/troubleshooting.rst:17 +msgid "The :abbr:`IoT (Internet of Things)` box is not connected to the Internet." +msgstr "" + +#: ../../content/applications/general/iot/config/troubleshooting.rst:18 +msgid "The code is only valid for 5 minutes after the :abbr:`IoT (Internet of Things)` box has started. It is automatically removed from connected displays when this time has expired." +msgstr "" + +#: ../../content/applications/general/iot/config/troubleshooting.rst:20 +msgid "The version of the :abbr:`IoT (Internet of Things)` box image is too old. If the :abbr:`IoT (Internet of Things)` box image is from an earlier version, then the SD card of the :abbr:`IoT (Internet of Things)` box needs to be re-flashed to update the image (see :ref:`Flashing the SD Card `)." +msgstr "" + +#: ../../content/applications/general/iot/config/troubleshooting.rst:25 +msgid "If none of the cases listed above correct the issue, then make sure the :abbr:`IoT (Internet of Things)` box has correctly started, by checking that a fixed green LED is showing next to the power port." +msgstr "" + +#: ../../content/applications/general/iot/config/troubleshooting.rst:30 +msgid "IoT box is connected but it is not showing in the database" +msgstr "" + +#: ../../content/applications/general/iot/config/troubleshooting.rst:32 +msgid "When an :abbr:`IoT (Internet of Things)` box connects to a database, it may restart. If so, it can take up to five minutes before appearing in the database. If the :abbr:`IoT (Internet of Things)` box is still not showing after five minutes, make sure that the :abbr:`IoT (Internet of Things)` box can reach the database and that the server does not use a multi-database environment." +msgstr "" + +#: ../../content/applications/general/iot/config/troubleshooting.rst:37 +msgid "To access the database from the :abbr:`IoT (Internet of Things)` box, open a browser and type in the database address." +msgstr "" + +#: ../../content/applications/general/iot/config/troubleshooting.rst:41 +msgid "The IoT box is connected to the Odoo database, but cannot be reached" +msgstr "" + +#: ../../content/applications/general/iot/config/troubleshooting.rst:43 +msgid "Make sure that the :abbr:`IoT (Internet of Things)` box and the computer running the browser are located on the same network, as the :abbr:`IoT (Internet of Things)` box cannot be reached from outside the local network." +msgstr "" + +#: ../../content/applications/general/iot/config/troubleshooting.rst:48 +msgid "The HTTPS certificate does not generate" +msgstr "" + +#: ../../content/applications/general/iot/config/troubleshooting.rst:50 +msgid "In order to generate a :abbr:`HTTPS (Hypertext Transfer Protocol Secure)` certificate, an IoT box subscription is required for the :abbr:`IoT (Internet of Things)` box. Connecting the :abbr:`IoT (Internet of Things)` box prior to configuring an :abbr:`IoT (Internet of Things)` subscription for the database and :abbr:`IoT (Internet of Things)` box with the Account Manager will result in an unsecured connection." +msgstr "" + +#: ../../content/applications/general/iot/config/troubleshooting.rst:56 +msgid "In addition, a firewall can also prevent the :abbr:`HTTPS (Hypertext Transfer Protocol Secure)` certificate from generating correctly. In this case, deactivate the firewall until the certificate is successfully generated. It should also be noted that certain devices, such as a router that has a built-in firewall, can prevent the :abbr:`HTTPS (Hypertext Transfer Protocol Secure)` certificate from generating." +msgstr "" + +#: ../../content/applications/general/iot/config/troubleshooting.rst:63 +msgid ":doc:`HTTPS certificate (IoT) `" +msgstr "" + +#: ../../content/applications/general/iot/config/troubleshooting.rst:69 +msgid "The printer is not detected" +msgstr "" + +#: ../../content/applications/general/iot/config/troubleshooting.rst:71 +msgid "If a printer does not appear in the devices list, go to the :abbr:`IoT (Internet of Things)` box homepage and make sure that it is listed under :guilabel:`Printers`." +msgstr "" + +#: ../../content/applications/general/iot/config/troubleshooting.rst:-1 +msgid "The IoT box Home Page landing page." +msgstr "" + +#: ../../content/applications/general/iot/config/troubleshooting.rst:78 +msgid "If the printer is not present on the :abbr:`IoT (Internet of Things)` box homepage, click :guilabel:`Printers Server`, go to the :guilabel:`Administration` tab and click on :guilabel:`Add Printer`. If the printer is not present in the list, it is likely not connected properly." +msgstr "" + +#: ../../content/applications/general/iot/config/troubleshooting.rst:83 +msgid "The printer outputs random text" +msgstr "" + +#: ../../content/applications/general/iot/config/troubleshooting.rst:85 +msgid "For most printers, the correct driver should be automatically detected and selected. However, in some cases, the automatic detection mechanism might not be enough, and if no driver is found, the printer might print random characters." +msgstr "" + +#: ../../content/applications/general/iot/config/troubleshooting.rst:89 +msgid "The solution is to manually select the corresponding driver. On the :abbr:`IoT (Internet of Things)` box homepage, click on :guilabel:`Printers Server`, go to the :guilabel:`Printers` tab and select the printer in the list. In the :guilabel:`Administration` drop-down menu, click on :guilabel:`Modify Printer`. Follow the steps and select the *make* and *model* corresponding to the printer." +msgstr "" + +#: ../../content/applications/general/iot/config/troubleshooting.rst:-1 +msgid "Edit the printer connected to the IoT box." +msgstr "" + +#: ../../content/applications/general/iot/config/troubleshooting.rst:100 +msgid "Epson and Star receipt printers and Zebra label printers do not need a driver to work. Make sure that no driver is selected for those printers." +msgstr "" + +#: ../../content/applications/general/iot/config/troubleshooting.rst:104 +msgid "Epson configuration special case" +msgstr "" + +#: ../../content/applications/general/iot/config/troubleshooting.rst:106 +msgid "Most Epson printers support printing receipts in Odoo :abbr:`POS (Point of Sale)` using the `GS v 0` command. However, the following Epson printer models do not support this command:" +msgstr "" + +#: ../../content/applications/general/iot/config/troubleshooting.rst:109 +msgid "TM-U220" +msgstr "" + +#: ../../content/applications/general/iot/config/troubleshooting.rst:110 +msgid "TM-U230" +msgstr "" + +#: ../../content/applications/general/iot/config/troubleshooting.rst:111 +msgid "TM-P60" +msgstr "" + +#: ../../content/applications/general/iot/config/troubleshooting.rst:112 +msgid "TMP-P60II" +msgstr "" + +#: ../../content/applications/general/iot/config/troubleshooting.rst:114 +msgid "Bypass this issue by configuring the printer to use the `ESC *` command instead." +msgstr "" + +#: ../../content/applications/general/iot/config/troubleshooting.rst:117 +msgid "Process to force ESC * command" +msgstr "" + +#: ../../content/applications/general/iot/config/troubleshooting.rst:120 +msgid "Epson printer compatibility" +msgstr "" + +#: ../../content/applications/general/iot/config/troubleshooting.rst:122 +msgid "The first step is to check whether the printer is incompatible with `GS v 0` command." +msgstr "" + +#: ../../content/applications/general/iot/config/troubleshooting.rst:126 +msgid "`Epson GS v 0 documentation `_ for `GS v 0` compatible printers." +msgstr "" + +#: ../../content/applications/general/iot/config/troubleshooting.rst:128 +msgid "`Epson ESC * documentation `_ for `ESC *` compatible printers." +msgstr "" + +#: ../../content/applications/general/iot/config/troubleshooting.rst:131 +msgid "If the printer is not compatible with the `ESC *` command then the following process is not possible. Should the printer be compatible to use the `ESC *` command to print, follow this process to configure the printer with the :abbr:`IoT (Internet of Things)` box." +msgstr "" + +#: ../../content/applications/general/iot/config/troubleshooting.rst:136 +msgid "IoT box configuration for ESC *" +msgstr "" + +#: ../../content/applications/general/iot/config/troubleshooting.rst:138 +msgid "To configure the :abbr:`IoT (Internet of Things)` box to use the `ESC *` command to print, go to the :abbr:`IoT (Internet of Things)` box homepage by navigating to :menuselection:`IoT app --> IoT Boxes`. Then click on the :guilabel:`IP address` and this will direct to the :abbr:`IoT (Internet of Things)` box homepage." +msgstr "" + +#: ../../content/applications/general/iot/config/troubleshooting.rst:143 +msgid "**Choosing the printer**" +msgstr "" + +#: ../../content/applications/general/iot/config/troubleshooting.rst:145 +msgid "Now click on the :guilabel:`Printers server` button. This will redirect the browser to the *CUPS* page. Next, go to :menuselection:`Administration --> Printers --> Add Printer`, choose the printer that should be modified, and then click :guilabel:`Continue`." +msgstr "" + +#: ../../content/applications/general/iot/config/troubleshooting.rst:150 +msgid "If the name of the printer is still uncertain, take the following steps:" +msgstr "" + +#: ../../content/applications/general/iot/config/troubleshooting.rst:152 +msgid "Take note of the listed printers on the *CUPS* page." +msgstr "" + +#: ../../content/applications/general/iot/config/troubleshooting.rst:153 +msgid "Turn the printer off and refresh the page." +msgstr "" + +#: ../../content/applications/general/iot/config/troubleshooting.rst:154 +msgid "Now compare the difference with the first list to see which printer disappeared." +msgstr "" + +#: ../../content/applications/general/iot/config/troubleshooting.rst:155 +msgid "Turn the printer back on and refresh the page again." +msgstr "" + +#: ../../content/applications/general/iot/config/troubleshooting.rst:156 +msgid "Double-check the list again to see if the printer re-appears." +msgstr "" + +#: ../../content/applications/general/iot/config/troubleshooting.rst:157 +msgid "The printer that disappeared and reappears again on the listed printers is the name of the printer in question." +msgstr "" + +#: ../../content/applications/general/iot/config/troubleshooting.rst:161 +msgid "This can be :guilabel:`Unknown` under :guilabel:`Local printers`." +msgstr "" + +#: ../../content/applications/general/iot/config/troubleshooting.rst:163 +msgid "**CUPS naming convention**" +msgstr "" + +#: ../../content/applications/general/iot/config/troubleshooting.rst:165 +msgid "`CUPS` will prompt the administrator for three pieces of information: the :guilabel:`Name`, :guilabel:`Description` and the :guilabel:`Location`. The last two pieces of information do not need to be specific, however, the :guilabel:`Name` should follow a particular convention to work with the `ESC *` command." +msgstr "" + +#: ../../content/applications/general/iot/config/troubleshooting.rst:170 +msgid "The :guilabel:`Name` should match this convention: `__IMC___...___`" +msgstr "" + +#: ../../content/applications/general/iot/config/troubleshooting.rst:173 +msgid "A breakdown of the naming convention:" +msgstr "" + +#: ../../content/applications/general/iot/config/troubleshooting.rst:175 +msgid "`printer_name`: This is the printer name. It can be any character as long as it does not contain `_`, `/`, `#`, or ` ` (space character)." +msgstr "" + +#: ../../content/applications/general/iot/config/troubleshooting.rst:177 +msgid "`IMC`: This stands for *Image Mode Column* (the simplified name for `ESC *`)." +msgstr "" + +#: ../../content/applications/general/iot/config/troubleshooting.rst:178 +msgid "`param_1`: This stands for the specific parameter:" +msgstr "" + +#: ../../content/applications/general/iot/config/troubleshooting.rst:180 +msgid "`SCALE`: Scale of the picture (with the same aspect ratio). `X` should be an integer describing the scale percentage that should be used." +msgstr "" + +#: ../../content/applications/general/iot/config/troubleshooting.rst:184 +msgid "`100` is the original size, `50` is half the size, `200` is twice the size." +msgstr "" + +#: ../../content/applications/general/iot/config/troubleshooting.rst:186 +msgid "`LDV`: *Low Density Vertical* (will be set to *High Density Vertical* if not specified)." +msgstr "" + +#: ../../content/applications/general/iot/config/troubleshooting.rst:187 +msgid "`LDH`: *Low Density Horizontal* (will be set to *High Density Horizontal* if not specified)." +msgstr "" + +#: ../../content/applications/general/iot/config/troubleshooting.rst:190 +msgid "*Density* parameters might need to be configured in a particular way depending on the printer model." +msgstr "" + +#: ../../content/applications/general/iot/config/troubleshooting.rst:194 +msgid "Visit `Epson's ESC * documentation `_ and click on the printer model printer in the table above to see if the printer should set these parameters." +msgstr "" + +#: ../../content/applications/general/iot/config/troubleshooting.rst:199 +msgid "The following are examples of proper and improper name formatting:" +msgstr "" + +#: ../../content/applications/general/iot/config/troubleshooting.rst:201 +msgid "Proper name formatting:" +msgstr "" + +#: ../../content/applications/general/iot/config/troubleshooting.rst:203 +msgid "`EPSONTMm30II__IMC__`" +msgstr "" + +#: ../../content/applications/general/iot/config/troubleshooting.rst:204 +msgid "`EPSON_TM_U220__IMC_LDV_LDH_SCALE80__`" +msgstr "" + +#: ../../content/applications/general/iot/config/troubleshooting.rst:206 +msgid "Improper name formatting (this will not prevent printing, but the result might not have the expected printed output):" +msgstr "" + +#: ../../content/applications/general/iot/config/troubleshooting.rst:209 +msgid "`EPSON TMm 30II` -> The name cannot have spaces." +msgstr "" + +#: ../../content/applications/general/iot/config/troubleshooting.rst:210 +msgid "`EPSONTMm30II` -> The name itself is correct, but it will not use `ESC *`." +msgstr "" + +#: ../../content/applications/general/iot/config/troubleshooting.rst:211 +msgid "`EPSONTMm30II__IMC` -> This name is missing the end `__`." +msgstr "" + +#: ../../content/applications/general/iot/config/troubleshooting.rst:212 +msgid "`EPSONTMm30II__IMC_XDV__` -> The parameter `XDV` does not match any existing parameters." +msgstr "" + +#: ../../content/applications/general/iot/config/troubleshooting.rst:213 +msgid "`EPSONTMm30II__IMC_SCALE__` -> The parameter `SCALE` is missing the scale value." +msgstr "" + +#: ../../content/applications/general/iot/config/troubleshooting.rst:215 +msgid "**Finish adding a printer**" +msgstr "" + +#: ../../content/applications/general/iot/config/troubleshooting.rst:217 +msgid "After setting the name of the printer with the appropriate naming convention, click :guilabel:`Continue`. Next, set the :guilabel:`Make` value to :guilabel:`Raw` and for the :guilabel:`Model` value, set this to :guilabel:`Raw Queue (en)`." +msgstr "" + +#: ../../content/applications/general/iot/config/troubleshooting.rst:221 +msgid "After completing these steps, click :guilabel:`Add Printer`. If everything was done correctly, the page should redirect to the *Banners* page." +msgstr "" + +#: ../../content/applications/general/iot/config/troubleshooting.rst:224 +msgid "At this point the printer should have been created, now the :abbr:`IoT (Internet of Things)` box just needs to detect it and then sync to Odoo's server (this could take a few minutes)." +msgstr "" + +#: ../../content/applications/general/iot/config/troubleshooting.rst:227 +msgid "**Adding the printer to Odoo PoS**" +msgstr "" + +#: ../../content/applications/general/iot/config/troubleshooting.rst:229 +msgid "Once the printer is visible on the Odoo database, do not forget to choose it in the :abbr:`PoS (Point of Sale)`configuration as the :abbr:`IoT (Internet of Things)` printer. Navigate to :menuselection:`Pos App --> Settings --> Connected Devices --> IoT Box --> Receipt Printer --> Save`." +msgstr "" + +#: ../../content/applications/general/iot/config/troubleshooting.rst:235 +msgid "If the printer was set up incorrectly (it is still printing random text or the printed receipt is too big or small), then it cannot be modified via the printer name with *CUPS*. Instead, the above process can be repeated to set up another printer from scratch to create one with modified parameters." +msgstr "" + +#: ../../content/applications/general/iot/config/troubleshooting.rst:240 +msgid "**Example setup of the Epson TM-U220B printer using ESC**" +msgstr "" + +#: ../../content/applications/general/iot/config/troubleshooting.rst:245 +msgid "The following is an example of the troubleshooting process for a TM-U220B printer model using the `ESC *` command. The receipt pictured below is an example of a receipt that is printing correctly due to proper formatting (in theory):" +msgstr "" + +#: ../../content/applications/general/iot/config/troubleshooting.rst:0 +msgid "Properly formatted receipt picture from a demo database." +msgstr "" + +#: ../../content/applications/general/iot/config/troubleshooting.rst:253 +msgid "Trying to print this receipt right-away prior to the proper formatting will not work as the TM-U220B printer model does not support `GS v 0`. Instead random characters will print:" +msgstr "" + +#: ../../content/applications/general/iot/config/troubleshooting.rst:0 +msgid "Printer paper with seemingly random characters." +msgstr "" + +#: ../../content/applications/general/iot/config/troubleshooting.rst:260 +msgid "To properly configure formatting for the Epson TM-U220B printer model take the following steps." +msgstr "" + +#: ../../content/applications/general/iot/config/troubleshooting.rst:262 +msgid "After consulting Epson's website for compatibility for both of the commands: `GS v 0 `_ and `ESC * `_, it can be seen that indeed the TM-U220B is not compatible with `GS v 0`, but is compatible with `ESC *`." +msgstr "" + +#: ../../content/applications/general/iot/config/troubleshooting.rst:0 +msgid "Epson compatibility evaluation from Epson website." +msgstr "" + +#: ../../content/applications/general/iot/config/troubleshooting.rst:271 +msgid "When adding the printer, *CUPS* will ask which printer should be added:" +msgstr "" + +#: ../../content/applications/general/iot/config/troubleshooting.rst:0 +msgid "Administration menu, add printer selection." +msgstr "" + +#: ../../content/applications/general/iot/config/troubleshooting.rst:277 +msgid "In this case, the printer is connected via :abbr:`USB (Universal Serial Bus)` so it won' be part of the :guilabel:`Discovered Network Printers`. Instead it is likely part of the :guilabel:`Unknown` selection under :guilabel:`Local Printers`. By unplugging the printer's :abbr:`USB (Universal Serial Bus)` cable from the :abbr:`IoT (Internet of Things)` box and refreshing the page, the :guilabel:`Unknown` printer disappears. By plugging it back in, the printer reappears, so it can be said that this is the printer in question." +msgstr "" + +#: ../../content/applications/general/iot/config/troubleshooting.rst:284 +msgid "For the naming convention, since it needs to print using the `ESC *` command, it is imperative to add `__IMC`. Reference the printer model on `Epson's ESC * site `_ to find out more about the *density* parameters." +msgstr "" + +#: ../../content/applications/general/iot/config/troubleshooting.rst:0 +msgid "Epson TM-U220 specifications on manufacturer's website." +msgstr "" + +#: ../../content/applications/general/iot/config/troubleshooting.rst:293 +msgid "For this particular model, TM-U220, `m` should be equal to 0 or 1. While referencing the :guilabel:`Description` below the pink box in the above picture, the `m` values could be 0, 1, 32 or 33. So in this printers case, the `m` value can NOT be 32 or 33 (otherwise there will be random characters printed)." +msgstr "" + +#: ../../content/applications/general/iot/config/troubleshooting.rst:298 +msgid "The table includes the numeric values: 32 and 33, they both occur if the :guilabel:`Number of bits for vertical data` is set to 24. This means that is a *High Vertical Density*. In the case of configuring the Epson TM-U220, the *Low Vertical Density* will need to be forced, as this printer model does not support *High Vertical Density* for this command `ESC *`." +msgstr "" + +#: ../../content/applications/general/iot/config/troubleshooting.rst:303 +msgid "To add a *Low Vertical Density*, add the `LDV` parameter to the naming convention." +msgstr "" + +#: ../../content/applications/general/iot/config/troubleshooting.rst:0 +msgid "Add a *Low Vertical Density* (the `LDV` parameter) to the naming convention." +msgstr "" + +#: ../../content/applications/general/iot/config/troubleshooting.rst:309 +msgid "Click :guilabel:`Continue` to proceed. Next, set the :guilabel:`Make` value to :guilabel:`Raw` and for the :guilabel:`Model` value, set this to :guilabel:`Raw Queue (en)`." +msgstr "" + +#: ../../content/applications/general/iot/config/troubleshooting.rst:0 +msgid "Epson TM-U220 specifications on manufacturers website." +msgstr "" + +#: ../../content/applications/general/iot/config/troubleshooting.rst:316 +msgid "However, when trying to print with the naming convention: `EpsonTMU220B__IMC_LDV__`, it prints the receipt, but it is too big and outside the margin. To resolve this, add a new printer (and naming convention) with the `SCALE` parameter to adapt to our receipt size." +msgstr "" + +#: ../../content/applications/general/iot/config/troubleshooting.rst:320 +msgid "Here are some examples:" +msgstr "" + +#: ../../content/applications/general/iot/config/troubleshooting.rst:325 +msgid "Printer Naming Convention" +msgstr "" + +#: ../../content/applications/general/iot/config/troubleshooting.rst:326 +msgid "`EpsonTMU220B__IMC_LDV__`" +msgstr "" + +#: ../../content/applications/general/iot/config/troubleshooting.rst:327 +msgid "`EpsonTMU220B__IMC_LDV_SCALE75__`" +msgstr "" + +#: ../../content/applications/general/iot/config/troubleshooting.rst:328 +msgid "`EpsonTMU220B__IMC_LDV_LDH__`" +msgstr "" + +#: ../../content/applications/general/iot/config/troubleshooting.rst:329 +msgid "`EpsonTMU220B__IMC_LDV_LDH_SCALE35__`" +msgstr "" + +#: ../../content/applications/general/iot/config/troubleshooting.rst:0 +msgid "Receipt example format." +msgstr "" + +#: ../../content/applications/general/iot/config/troubleshooting.rst:0 +msgid "Receipt format using naming convention: EpsonTMU220B__IMC_LDV__." +msgstr "" + +#: ../../content/applications/general/iot/config/troubleshooting.rst:0 +msgid "Receipt format using naming convention: EpsonTMU220B__IMC_LDV_SCALE75__." +msgstr "" + +#: ../../content/applications/general/iot/config/troubleshooting.rst:0 +msgid "Receipt format using naming convention: EpsonTMU220B__IMC_LDV_LDH__." +msgstr "" + +#: ../../content/applications/general/iot/config/troubleshooting.rst:0 +msgid "Receipt format using naming convention: EpsonTMU220B__IMC_LDV_LDH_SCALE35__." +msgstr "" + +#: ../../content/applications/general/iot/config/troubleshooting.rst:347 +msgid "The Zebra printer does not print anything" +msgstr "" + +#: ../../content/applications/general/iot/config/troubleshooting.rst:349 +msgid "Zebra printers are quite sensitive to the format of the Zebra Programming Language (ZPL) code that is printed. If nothing comes out of the printer or blank labels are printed, try changing the format of the report that is sent to the printer by accessing :menuselection:`Settings --> Technical --> User Interface --> Views` in :ref:`developer mode ` and look for the corresponding template." +msgstr "" + +#: ../../content/applications/general/iot/config/troubleshooting.rst:356 +msgid "Check out Zebra's instructions on printing :abbr:`ZPL (Zebra Programming Language)` files `here `_." +msgstr "" + +#: ../../content/applications/general/iot/config/troubleshooting.rst:363 +msgid "The characters read by the barcode scanner do not match the barcode" +msgstr "" + +#: ../../content/applications/general/iot/config/troubleshooting.rst:365 +msgid "By default, most barcode scanners are configured in the US QWERTY format. If the barcode scanner uses a different layout, go to the form view of the device (:menuselection:`IoT App --> Devices --> Barcode Device`) and select the correct format." +msgstr "" + +#: ../../content/applications/general/iot/config/troubleshooting.rst:370 +msgid "Nothing happens when a barcode is scanned" +msgstr "" + +#: ../../content/applications/general/iot/config/troubleshooting.rst:372 +msgid "Make sure that the correct device is selected in the :menuselection:`Point of Sale` configuration and that the barcode is configured to send an `ENTER` character (keycode 28) at the end of every barcode. To do so, navigate to :menuselection:`PoS app --> 3-Dot Menu on the PoS --> IoT Box section --> Edit`." +msgstr "" + +#: ../../content/applications/general/iot/config/troubleshooting.rst:378 +msgid "The barcode scanner is detected as a keyboard" +msgstr "" + +#: ../../content/applications/general/iot/config/troubleshooting.rst:381 +msgid "Some barcode scanners do not advertise themselves as barcode scanners but as a USB keyboard instead, and will not be recognized by the :abbr:`IoT (Internet of Things)` box." +msgstr "" + +#: ../../content/applications/general/iot/config/troubleshooting.rst:384 +msgid "The device type can be manually changed by going to its form view (:menuselection:`IoT App --> Devices --> Barcode Device`) and activating the :guilabel:`Is scanner` option." +msgstr "" + +#: ../../content/applications/general/iot/config/troubleshooting.rst:-1 +msgid "Modifying the form view of the barcode scanner." +msgstr "" + +#: ../../content/applications/general/iot/config/troubleshooting.rst:392 +msgid "Barcode scanner processes barcode characters individually" +msgstr "" + +#: ../../content/applications/general/iot/config/troubleshooting.rst:394 +msgid "When accessing the mobile version of Odoo from a mobile device, or tablet, paired with a barcode scanner, via the :abbr:`IoT (Internet of Things)` box, the scanner may process each barcode character as an individual scan. In this case, the *Keyboard Layout* option **must** be filled out with the appropriate language of the barcode scanner on the *Barcode Scanner* form page." +msgstr "" + +#: ../../content/applications/general/iot/config/troubleshooting.rst:400 +msgid "Access the barcode scanner form page by navigating to :menuselection:`IoT App --> Devices --> Barcode Scanner`." +msgstr "" + +#: ../../content/applications/general/iot/config/troubleshooting.rst:-1 +msgid "Barcode scanner form page, with keyboard layout option highlighted." +msgstr "" + +#: ../../content/applications/general/iot/config/troubleshooting.rst:407 +msgid "The :guilabel:`Keyboard Layout` is language based, and the options available vary, depending on the device and the language of the database. For example: :guilabel:`English (UK)`, :guilabel:`English (US)`, etc." +msgstr "" + +#: ../../content/applications/general/iot/config/troubleshooting.rst:415 +msgid "The cash drawer does not open" +msgstr "" + +#: ../../content/applications/general/iot/config/troubleshooting.rst:417 +msgid "The cash drawer should be connected to the printer and the :guilabel:`Cash drawer` checkbox should be ticked in the :abbr:`PoS (Point of Sale)` configuration. To do so, navigate to :menuselection:`POS app --> 3-Dot Menu on the POS --> IoT Box section --> Edit --> Receipt Printer --> Cashdrawer checkbox`." +msgstr "" + +#: ../../content/applications/general/iot/config/troubleshooting.rst:425 +msgid "Scales play a crucial role in the checkout process, especially for products sold by weight, rather than fixed pricing." +msgstr "" + +#: ../../content/applications/general/iot/config/troubleshooting.rst:429 +msgid "Set up Ariva S scales" +msgstr "" + +#: ../../content/applications/general/iot/config/troubleshooting.rst:431 +msgid "Odoo has determined that a specific setting in Ariva S series scales (manufactured by Mettler-Toledo, LLC.) needs modification, and a dedicated Mettler :abbr:`USB (Universal Serial Bus)`-to-proprietary RJ45 cable is required for the scale to function with Odoo's :abbr:`IoT (Internet of Things)` box." +msgstr "" + +#: ../../content/applications/general/iot/config/troubleshooting.rst:436 +msgid "To correctly configure the scale for recognition by the :abbr:`IoT (Internet of Things)` box, follow this setup process for the Ariva S series scales." +msgstr "" + +#: ../../content/applications/general/iot/config/troubleshooting.rst:440 +msgid "It is crucial to use the official Mettler :abbr:`USB (Universal Serial Bus)`-to-RJ45 cable during this process." +msgstr "" + +#: ../../content/applications/general/iot/config/troubleshooting.rst:444 +msgid "Cable" +msgstr "" + +#: ../../content/applications/general/iot/config/troubleshooting.rst:446 +msgid "The Mettler part number is 72256236 - :abbr:`USB (Universal Serial Bus)`-to-:abbr:`POS (Point of Sale)` cable. Contact Mettler, or a partner, to purchase an authentic cable. Note that **no other** cable outside of this Mettler cable works for this configuration. Using a serial-only cable attached to a serial-to-:abbr:`USB (Universal Serial Bus)` adapter is **not** effective." +msgstr "" + +#: ../../content/applications/general/iot/config/troubleshooting.rst:-1 +msgid "Authentic Mettler USB to POS cable, part number 72256236." +msgstr "" + +#: ../../content/applications/general/iot/config/troubleshooting.rst:458 +msgid "Refer to Mettler's Setup Guide for Ariva S series scales during the following configuration: `Ariva Checkout Scale User's Guide `_." +msgstr "" + +#: ../../content/applications/general/iot/config/troubleshooting.rst:461 +msgid "To begin, go to page 17 in the above manual for *Setup*. This guide lists potential settings for the Ariva S series scales." +msgstr "" + +#: ../../content/applications/general/iot/config/troubleshooting.rst:464 +msgid "Follow the instructions, along with the following process, to set the scale to setup mode. First, hold the **>T<** button for eight seconds, or until :guilabel:`CONF` appears." +msgstr "" + +#: ../../content/applications/general/iot/config/troubleshooting.rst:467 +msgid "Next, press **>T<** until :guilabel:`GRP 3` appears, then press **>0<** to confirm." +msgstr "" + +#: ../../content/applications/general/iot/config/troubleshooting.rst:469 +msgid "Under :guilabel:`3.1`, ensure the setting is set to :guilabel:`1` (USB Virtual COM ports). Press **>T<** to cycle through the options under group 3.1." +msgstr "" + +#: ../../content/applications/general/iot/config/troubleshooting.rst:472 +msgid "Once :guilabel:`3.1` is set to :guilabel:`1`, press **>0<** to confirm the selection. Continue to press **>0<** until :guilabel:`GRP 4` appears." +msgstr "" + +#: ../../content/applications/general/iot/config/troubleshooting.rst:475 +msgid "Now, press **>T<** until :guilabel:`EXIT` appears." +msgstr "" + +#: ../../content/applications/general/iot/config/troubleshooting.rst:478 +msgid "Do **not** make any other changes unless otherwise needed." +msgstr "" + +#: ../../content/applications/general/iot/config/troubleshooting.rst:480 +msgid "Once :guilabel:`EXIT` appears, press **>0<**. Following this, press **>0<** again to :guilabel:`SAVE`. Now the scale restarts." +msgstr "" + +#: ../../content/applications/general/iot/config/troubleshooting.rst:483 +msgid "Finally, restart the :abbr:`IoT (Internet of Things)` box to recognize the changes made on the scale's configuration. After restarting, the scale appears as `Toledo 8217`, as opposed to the previous display, where it appeared as `Adam Equipment Serial`." +msgstr "" + +#: ../../content/applications/general/iot/config/updating_iot.rst:3 +msgid "Updating (IoT)" +msgstr "" + +#: ../../content/applications/general/iot/config/updating_iot.rst:5 +msgid "Due to the complexity of the :abbr:`IoT (Internet of Things)` box, and virtual Windows :abbr:`IoT (Internet of Things)` box, the term 'updating' can mean several different things." +msgstr "" + +#: ../../content/applications/general/iot/config/updating_iot.rst:8 +msgid "The actual drivers can be updated, the core code on the :abbr:`IoT (Internet of Things)` box can be updated, or a new image can be flashed (using a physical :abbr:`IoT (Internet of Things)` box)." +msgstr "" + +#: ../../content/applications/general/iot/config/updating_iot.rst:11 +msgid "This document explores the various ways to update :abbr:`IoT (Internet of Things)` boxes to ensure smooth operation of :abbr:`IoT (Internet of Things)` box processes and devices." +msgstr "" + +#: ../../content/applications/general/iot/config/updating_iot.rst:17 +msgid "Flashing the SD card on IoT box" +msgstr "" + +#: ../../content/applications/general/iot/config/updating_iot.rst:20 +msgid "This update does **not** apply to the Windows :abbr:`IoT (Internet of Things)` box (Odoo 16 and higher)." +msgstr "" + +#: ../../content/applications/general/iot/config/updating_iot.rst:23 +msgid "To update the Windows :abbr:`IoT (Internet of Things)`, first, uninstall the previous version of the Odoo Windows program, and then reinstall it using the most up-to-date installation package." +msgstr "" + +#: ../../content/applications/general/iot/config/updating_iot.rst:26 +msgid "To begin the installation, navigate to the Odoo 16 (or higher) installation package for Enterprise or Community - Windows edition, at `Odoo's download page `_." +msgstr "" + +#: ../../content/applications/general/iot/config/updating_iot.rst:30 +msgid "In some circumstances, the :abbr:`IoT (Internet of Things)` box's micro SD Card may need to be re-flashed with *Etcher* software to benefit from Odoo's latest :abbr:`IoT (Internet of Things)` image update. This means the Odoo :abbr:`IoT (Internet of Things)` box software may need to be updated in instances of a new :abbr:`IoT (Internet of Things)` box, or when a handler's update, or an update from the :abbr:`IoT (Internet of Things)` box home page, does not resolve issues." +msgstr "" + +#: ../../content/applications/general/iot/config/updating_iot.rst:38 +msgid "It is often necessary to re-flash the :abbr:`IoT (Internet of Things)` box's image after upgrading the Odoo database to a new version." +msgstr "" + +#: ../../content/applications/general/iot/config/updating_iot.rst:40 +msgid "A computer with a micro SD card reader/adapter is **required** to re-flash the micro SD card." +msgstr "" + +#: ../../content/applications/general/iot/config/updating_iot.rst:42 +msgid "First, begin by downloading `Etcher `_. It is a free, open-source utility, used for burning image files onto drives. After the download completes, install and launch the program on the computer." +msgstr "" + +#: ../../content/applications/general/iot/config/updating_iot.rst:46 +msgid "Then, download the latest :abbr:`IoT (Internet of Things)` image from `nightly `_, which will be labeled as `iotbox-latest.zip`. This particular image is compatible with *all* supported versions of Odoo." +msgstr "" + +#: ../../content/applications/general/iot/config/updating_iot.rst:50 +msgid "After this step is complete, insert the :abbr:`IoT (Internet of Things)` box's micro SD card into the computer or reader. Open *Etcher*, and select :guilabel:`Flash from file`, then find and select the `iotbox-latest.zip` image and extract it. Next, select the drive the image should be burned to." +msgstr "" + +#: ../../content/applications/general/iot/config/updating_iot.rst:54 +msgid "Lastly, click :guilabel:`Flash`, and wait for the process to finish." +msgstr "" + +#: ../../content/applications/general/iot/config/updating_iot.rst:-1 +msgid "Balena's Etcher software dashboard." +msgstr "" + +#: ../../content/applications/general/iot/config/updating_iot.rst:61 +msgid "Balena's *Etcher* software also allows for the administrator to flash the :abbr:`SD (Secure Digital)` card from a :abbr:`URL (Uniform Resource Locator)`. To flash from a :abbr:`URL (Uniform Resource Locator)`, simply click :guilabel:`Flash from URL`, instead of :guilabel:`Flash from file`." +msgstr "" + +#: ../../content/applications/general/iot/config/updating_iot.rst:66 +msgid "Then, enter the following: `http://nightly.odoo.com/master/iotbox/iotbox-latest.zip`." +msgstr "" + +#: ../../content/applications/general/iot/config/updating_iot.rst:0 +msgid "A view of Balena's Etcher software, with the flash from URL option highlighted." +msgstr "" + +#: ../../content/applications/general/iot/config/updating_iot.rst:73 +msgid "An alternative software for flashing the micro SD card is `Raspberry Pi Imager `_." +msgstr "" + +#: ../../content/applications/general/iot/config/updating_iot.rst:79 +msgid "Update from the IoT box home page" +msgstr "" + +#: ../../content/applications/general/iot/config/updating_iot.rst:81 +msgid "In the background, the :abbr:`IoT (Internet of Things)` box uses a version of Odoo code to run and connect to the Odoo database. This code may need to be updated in order for the :abbr:`IoT (Internet of Things)` box to operate effectively. This operation should be completed on a routine basis, to ensure the :abbr:`IoT (Internet of Things)` system, and its processes, stay up-to-date." +msgstr "" + +#: ../../content/applications/general/iot/config/updating_iot.rst:86 +msgid "Go to the :abbr:`IoT (Internet of Things)` box home page by navigating to :menuselection:`IoT app --> IoT Boxes`, and clicking on the :guilabel:`IP address` of the :abbr:`IoT (Internet of Things)` box. Then, click on :guilabel:`Update` (next to the version number)." +msgstr "" + +#: ../../content/applications/general/iot/config/updating_iot.rst:90 +msgid "If a new version of the :abbr:`IoT (Internet of Things)` box image is available, an :guilabel:`Upgrade to _xx.xx_` button appears at the bottom of the page. Click this button to upgrade the unit, at which point the :abbr:`IoT (Internet of Things)` box flashes itself to the newer version. All of the previous configurations are then saved." +msgstr "" + +#: ../../content/applications/general/iot/config/updating_iot.rst:96 +msgid "This process can take more than 30 minutes. Do **not** turn off, or unplug, the :abbr:`IoT (Internet of Things)` box, as it would leave it in an inconsistent state. This means the :abbr:`IoT (Internet of Things)` box needs to be :ref:`re-flashed ` with a new image." +msgstr "" + +#: ../../content/applications/general/iot/config/updating_iot.rst:-1 +msgid "IoT box software upgrade in the IoT Box Home Page." +msgstr "" + +#: ../../content/applications/general/iot/config/updating_iot.rst:106 +msgid "Handler (driver) update" +msgstr "" + +#: ../../content/applications/general/iot/config/updating_iot.rst:108 +msgid "There may be some instances where drivers or interfaces need to be updated for individual devices (e.g. scales, measurement tools, etc.). The IoT handler's (drivers and interfaces) code can be modified by syncing them with the configured server handler's code." +msgstr "" + +#: ../../content/applications/general/iot/config/updating_iot.rst:112 +msgid "This can be helpful in instances where :abbr:`IoT (Internet of Things)` devices (e.g. scales, measurement tools, etc.) are not working properly with the :abbr:`IoT (Internet of Things)` box." +msgstr "" + +#: ../../content/applications/general/iot/config/updating_iot.rst:115 +msgid "For both the Windows :abbr:`IoT (Internet of Things)` (Odoo 16 and higher) and physical :abbr:`IoT (Internet of Things)` box, this process can be performed manually from the :abbr:`IoT (Internet of Things)` box home page. Go to the :abbr:`IoT (Internet of Things)` box home page by navigating to :menuselection:`IoT app --> IoT Boxes`, and clicking on the :guilabel:`IP address` of the :abbr:`IoT (Internet of Things)` box." +msgstr "" + +#: ../../content/applications/general/iot/config/updating_iot.rst:121 +msgid "Next, click :guilabel:`Handlers list`, and then select :guilabel:`Load Handlers` at the bottom of the page." +msgstr "" + +#: ../../content/applications/general/iot/config/updating_iot.rst:-1 +msgid "Handlers list on an IoT box with the load handlers button highlighted." +msgstr "" + +#: ../../content/applications/general/iot/config/updating_iot.rst:129 +msgid "Handler's code is fetched from the configured server, and it needs to be up-to-date to have the latest fixes and patches." +msgstr "" + +#: ../../content/applications/general/iot/config/updating_iot.rst:133 +msgid "A handler update is also performed automatically each time the :abbr:`IoT (Internet of Things)` box is restarted. The only exception to this process is if the *Automatic drivers update* is unchecked in the form view of the :abbr:`IoT (Internet of Things)` box on the Odoo server. This setting can be reached by going to :menuselection:`IoT App --> Select the IoT box --> Automatic drivers update`." +msgstr "" + +#: ../../content/applications/general/iot/config/windows_iot.rst:3 +msgid "Connect Windows IoT Odoo" +msgstr "" + +#: ../../content/applications/general/iot/config/windows_iot.rst:5 +msgid "A Virtual IoT box is a computer program that needs to be downloaded and installed on a Windows computer. This requires a Windows operating system with an Odoo 16 or later database." +msgstr "" + +#: ../../content/applications/general/iot/config/windows_iot.rst:8 +msgid "The Windows virtual :abbr:`IoT (Internet of Things)` box works the same way as a physical :abbr:`IoT (Internet of Things)` box, with the ability to run most of the same devices. All :abbr:`POS (Point of Sale)` devices work with it, such as a scale or printer. Payment terminals will also work, but it should be noted that :abbr:`MRP (Material Requirement Planning)` devices are not compatible. *These include cameras or measurement tools.*" +msgstr "" + +#: ../../content/applications/general/iot/config/windows_iot.rst:15 +msgid "Pre-requisites" +msgstr "" + +#: ../../content/applications/general/iot/config/windows_iot.rst:17 +msgid "The following items will be needed to complete the Windows :abbr:`IoT (Internet of Things)` installation." +msgstr "" + +#: ../../content/applications/general/iot/config/windows_iot.rst:20 +msgid "Odoo 16 database or any version above." +msgstr "" + +#: ../../content/applications/general/iot/config/windows_iot.rst:21 +msgid ":abbr:`IoT (Internet of Things)` compatible devices (except those mentioned above). Refer to: `Odoo's compatible IoT devices `_." +msgstr "" + +#: ../../content/applications/general/iot/config/windows_iot.rst:23 +msgid "Device drivers for Windows." +msgstr "" + +#: ../../content/applications/general/iot/config/windows_iot.rst:26 +msgid "Odoo recommends using an updated, recent version of Windows (Windows 10/11) as some older operating systems can cause the Windows virtual :abbr:`IoT (Internet of Things)` to not work." +msgstr "" + +#: ../../content/applications/general/iot/config/windows_iot.rst:29 +msgid "Windows computer (laptop, desktop, or server)." +msgstr "" + +#: ../../content/applications/general/iot/config/windows_iot.rst:30 +msgid "Odoo :abbr:`IoT (Internet of Things)` subscription. Refer to: :ref:`iot/iot-eligibility`." +msgstr "" + +#: ../../content/applications/general/iot/config/windows_iot.rst:33 +msgid "Connect the Windows virtual IoT box to an Odoo database" +msgstr "" + +#: ../../content/applications/general/iot/config/windows_iot.rst:35 +msgid "The Windows virtual IoT box is simple to setup in just a few easy steps. Follow this process when installing the Windows virtual IoT software for the first time." +msgstr "" + +#: ../../content/applications/general/iot/config/windows_iot.rst:39 +msgid "Download and initial installation" +msgstr "" + +#: ../../content/applications/general/iot/config/windows_iot.rst:41 +msgid "To begin the installation, navigate to the Odoo 16 or higher installation package for Enterprise or Community - Windows edition at `Odoo's download page `_. Next, install and setup the Odoo :file:`.exe` file. After the instructions screen, click :guilabel:`Next` to start the installation and agree to the :abbr:`TOS (Terms of Service)`." +msgstr "" + +#: ../../content/applications/general/iot/config/windows_iot.rst:46 +msgid "During the next step of the installation, select :guilabel:`Odoo IoT` from the :guilabel:`Select the type of install` drop-down menu." +msgstr "" + +#: ../../content/applications/general/iot/config/windows_iot.rst:50 +msgid "For reference, the following should be installed:" +msgstr "" + +#: ../../content/applications/general/iot/config/windows_iot.rst:52 +msgid "**Odoo server**" +msgstr "" + +#: ../../content/applications/general/iot/config/windows_iot.rst:53 +msgid "**Odoo IoT**" +msgstr "" + +#: ../../content/applications/general/iot/config/windows_iot.rst:54 +msgid "**Nginx WebServer**" +msgstr "" + +#: ../../content/applications/general/iot/config/windows_iot.rst:55 +msgid "**Ghostscript interpreter**" +msgstr "" + +#: ../../content/applications/general/iot/config/windows_iot.rst:57 +msgid "Ensure there is enough space on the computer for the installation and click :guilabel:`Next`." +msgstr "" + +#: ../../content/applications/general/iot/config/windows_iot.rst:60 +msgid "Setting the destination and completing the installation" +msgstr "" + +#: ../../content/applications/general/iot/config/windows_iot.rst:62 +msgid "To complete the installation, select the :guilabel:`Destination Folder` and click :guilabel:`Install`." +msgstr "" + +#: ../../content/applications/general/iot/config/windows_iot.rst:66 +msgid "Choosing ``C:\\odoo`` as the install location will allow for the Nginx server to start. If the folder doesn't exist, then create it. Otherwise the installation files will be spread throughout the hard drive." +msgstr "" + +#: ../../content/applications/general/iot/config/windows_iot.rst:71 +msgid "Odoo's Windows virtual IoT software should not be installed inside any of the Window's User's directories. Doing so will not allow for Nginx to initialize." +msgstr "" + +#: ../../content/applications/general/iot/config/windows_iot.rst:74 +msgid "The installation may take a few minutes. When complete, click :guilabel:`Next` to continue." +msgstr "" + +#: ../../content/applications/general/iot/config/windows_iot.rst:76 +msgid "Ensure that the :guilabel:`Start Odoo` box is checked and click :guilabel:`Finish`. After installation, the Odoo server will run and automatically open `http://localhost:8069` on a web browser. The webpage should display the :abbr:`IoT (Internet of Things)` box homepage." +msgstr "" + +#: ../../content/applications/general/iot/config/windows_iot.rst:81 +msgid "A restart of the Windows IoT program may be necessary should the web browser not display anything. :ref:`iot/restart_windows_iot`" +msgstr "" + +#: ../../content/applications/general/iot/config/windows_iot.rst:85 +msgid "Connecting devices" +msgstr "" + +#: ../../content/applications/general/iot/config/windows_iot.rst:87 +msgid "Next, connect the :abbr:`IoT (Internet of Things)` devices to the Windows computer. Windows should automatically detect the device because the driver is pre-installed on the computer. If not, search for and install the Windows driver for the device." +msgstr "" + +#: ../../content/applications/general/iot/config/windows_iot.rst:92 +msgid "Most devices connect to the Windows Machine for Windows IoT automatically through Windows Plug-N-Play (PnP). However, if Windows does not automatically recognize the device after connecting, then the administrator may need to install the corresponding drivers manually." +msgstr "" + +#: ../../content/applications/general/iot/config/windows_iot.rst:96 +msgid "Devices automatically recognized:" +msgstr "" + +#: ../../content/applications/general/iot/config/windows_iot.rst:98 +msgid "Regular ink/toner based printers" +msgstr "" + +#: ../../content/applications/general/iot/config/windows_iot.rst:99 +msgid "Receipt printers (Epson/Star)" +msgstr "" + +#: ../../content/applications/general/iot/config/windows_iot.rst:100 +msgid "Barcode scanners" +msgstr "" + +#: ../../content/applications/general/iot/config/windows_iot.rst:101 +msgid "Measurement devices (although some configuration of the measurement device settings is required) See this documentation: :doc:`../devices/measurement_tool`" +msgstr "" + +#: ../../content/applications/general/iot/config/windows_iot.rst:104 +msgid "Devices not automatically recognized (requires manual driver download):" +msgstr "" + +#: ../../content/applications/general/iot/config/windows_iot.rst:106 +msgid "Label printers (Zebra)" +msgstr "" + +#: ../../content/applications/general/iot/config/windows_iot.rst:107 +msgid "Scales" +msgstr "" + +#: ../../content/applications/general/iot/config/windows_iot.rst:109 +msgid "Reference the manufacturer's website for the equipment in question. Then, download the drivers and install them on the Windows machine. Reconnect the device in question and Windows will find the device." +msgstr "" + +#: ../../content/applications/general/iot/config/windows_iot.rst:113 +msgid "Following connecting devices to the computer, refresh the :abbr:`IoT (Internet of Things)` box homepage and verify the device is seen. If not, reload the handlers through the :abbr:`IoT (Internet of Things)` box homepage." +msgstr "" + +#: ../../content/applications/general/iot/config/windows_iot.rst:117 +msgid "Finally, connect Windows :abbr:`IoT (Internet of Things)` to a database using existing instructions (manually using the Token)." +msgstr "" + +#: ../../content/applications/general/iot/config/windows_iot.rst:123 +msgid "Now the installation is complete, the devices connected to :abbr:`IoT (Internet of Things)` can be used to complete processes/actions." +msgstr "" + +#: ../../content/applications/general/iot/config/windows_iot.rst:132 +msgid "Restart Windows IoT box" +msgstr "" + +#: ../../content/applications/general/iot/config/windows_iot.rst:134 +msgid "In some instances a manual restart of the physical :abbr:`IoT (Internet of Things)` box can resolve the issue of an :abbr:`IoT (Internet of Things)` box not showing up on the database. For the Windows virtual :abbr:`IoT (Internet of Things)` box a manual restart of the Odoo server can resolve database connection issues." +msgstr "" + +#: ../../content/applications/general/iot/config/windows_iot.rst:139 +msgid "To restart the virtual Windows IoT server:" +msgstr "" + +#: ../../content/applications/general/iot/config/windows_iot.rst:141 +msgid "Type `Services` into the Windows :guilabel:`Search Bar`." +msgstr "" + +#: ../../content/applications/general/iot/config/windows_iot.rst:142 +msgid "Select the :menuselection:`Services` App and scroll down to the :guilabel:`Odoo` service." +msgstr "" + +#: ../../content/applications/general/iot/config/windows_iot.rst:143 +msgid "Right click on :guilabel:`Odoo` and select :guilabel:`Start` or :guilabel:`Restart`. This action will manually restart the Odoo IoT server." +msgstr "" + +#: ../../content/applications/general/iot/config/windows_iot.rst:147 +msgid "Firewalls" +msgstr "" + +#: ../../content/applications/general/iot/config/windows_iot.rst:149 +msgid "Firewalls keep devices safe and secure. Sometimes they can block connections that should be made though. The Windows virtual :abbr:`IoT (Internet of Things)` box software may not be reachable to the :abbr:`LAN (Local Area Network)` due to a firewall preventing the connection. Consult your local IT support team to make exceptions (network discovery) in the :abbr:`OS (Operating System)` or firewall program. Windows has their own firewall as do other virus protection programs." +msgstr "" + +#: ../../content/applications/general/iot/config/windows_iot.rst:156 +msgid "A client might encounter a time when they are able to reach the homepage of the :abbr:`IoT (Internet of Things)` box, yet they cannot access it from another computer/mobile device/tablet on the same network." +msgstr "" + +#: ../../content/applications/general/iot/config/windows_iot.rst:161 +msgid "Making an exception on Windows Defender" +msgstr "" + +#: ../../content/applications/general/iot/config/windows_iot.rst:163 +msgid "It is possible to allow other devices to access the Windows virtual :abbr:`IoT (Internet of Things)` box while keeping the firewall on. This is done by creating a rule on *Windows Defender* and allowing communication through port `8069`. The following process describes the steps to take in order to make this exception." +msgstr "" + +#: ../../content/applications/general/iot/config/windows_iot.rst:169 +msgid "Create a rule in Windows Defender" +msgstr "" + +#: ../../content/applications/general/iot/config/windows_iot.rst:171 +msgid "First, open the *Windows Firewall* by navigating to the :menuselection:`Start Menu` and typing in `Firewall`. Then, open the :menuselection:`Windows Defender Firewall` program. In the left-hand menu, navigate to :guilabel:`Advanced Settings`." +msgstr "" + +#: ../../content/applications/general/iot/config/windows_iot.rst:175 +msgid "Once :guilabel:`Advanced Settings` have been selected, click :guilabel:`Inbound Rules` in the left-hand menu. Then, in the right-hand menu column (under :guilabel:`Inbound Rules`), click on :guilabel:`New Rule` to create a new rule." +msgstr "" + +#: ../../content/applications/general/iot/config/windows_iot.rst:180 +msgid "Configure new rule" +msgstr "" + +#: ../../content/applications/general/iot/config/windows_iot.rst:182 +msgid "On the :menuselection:`Rule Type` screen, select :guilabel:`Port`. Then click :guilabel:`Next`. From the :menuselection:`Protocol and Ports` page leave the rule application to :guilabel:`TCP`. Then, select :guilabel:`Specific Local Ports` for the :guilabel:`ports` option. In the text box, type in `8069`. Finally click :guilabel:`Next` to continue to the next step." +msgstr "" + +#: ../../content/applications/general/iot/config/windows_iot.rst:187 +msgid "On the :menuselection:`Actions` page, select :guilabel:`Allow the connection` and click :guilabel:`Next`. The following page on the :menuselection:`Rule Configuration` wizard is the :guilabel:`Profile` page. On this page, select whichever connection type applies to the network the Windows machine is operating on. Ideally, select :guilabel:`Private` only connections. The *Private* connection type is the most secure connection while allowing the selected port to communicate. Click :guilabel:`Next` to continue." +msgstr "" + +#: ../../content/applications/general/iot/config/windows_iot.rst:194 +msgid "Finally, assign a new, unique name to the rule. For example, this name can be `Odoo`. Optionally, add a brief description in the :guilabel:`Description` field. Click :guilabel:`Finish` to complete the :guilabel:`Rule Configuration` wizard. Now, the new rule is active and devices can connect to the Windows virtual :abbr:`IoT (Internet of Things)` box." +msgstr "" + +#: ../../content/applications/general/iot/config/windows_iot.rst:200 +msgid "Worldline exception" +msgstr "" + +#: ../../content/applications/general/iot/config/windows_iot.rst:202 +msgid "*Worldline* is a payment terminal that can be connected to Odoo's *PoS* (point of sale) system. It allows for a comprehensive and fluid payment experience for customers. Worldline is available in Benelux (coalition of Belgium, the Netherlands, and Luxembourg)." +msgstr "" + +#: ../../content/applications/general/iot/config/windows_iot.rst:206 +msgid "When using the Windows IoT server to connect the Worldline payment terminal, it is necessary to create an exception in the Windows firewall so that a connection can be made between the Odoo database/:abbr:`IoT (Internet of Things)` box and Worldline." +msgstr "" + +#: ../../content/applications/general/iot/config/windows_iot.rst:211 +msgid ":doc:`../../../sales/point_of_sale/payment_methods/terminals/worldline`" +msgstr "" + +#: ../../content/applications/general/iot/config/windows_iot.rst:213 +msgid "To create the exception, first, open the *Windows Defender Firewall* app on the Windows machine. This can be accomplished by typing `windows defender` in the :guilabel:`Search` bar." +msgstr "" + +#: ../../content/applications/general/iot/config/windows_iot.rst:216 +msgid "Next, click :guilabel:`Advanced settings` in the left menu." +msgstr "" + +#: ../../content/applications/general/iot/config/windows_iot.rst:-1 +msgid "Advanced settings option highlighted in the left pane of the Windows Defender Firewall app." +msgstr "" + +#: ../../content/applications/general/iot/config/windows_iot.rst:222 +msgid "In the left menu, choose :guilabel:`Inbound Rules`." +msgstr "" + +#: ../../content/applications/general/iot/config/windows_iot.rst:-1 +msgid "Windows Defender left window pane with inbound rules menu item highlighted." +msgstr "" + +#: ../../content/applications/general/iot/config/windows_iot.rst:228 +msgid "After selecting :guilabel:`Inbound Rules`, select :guilabel:`New Rule` in the far right menu." +msgstr "" + +#: ../../content/applications/general/iot/config/windows_iot.rst:-1 +msgid "New rule dropdown shown with new rule option highlighted." +msgstr "" + +#: ../../content/applications/general/iot/config/windows_iot.rst:234 +msgid "Then, for the :guilabel:`Rule Type`, select the radio button for :guilabel:`Port`. Click :guilabel:`Next` to continue to the rest of the configuration." +msgstr "" + +#: ../../content/applications/general/iot/config/windows_iot.rst:-1 +msgid "Rule Type window open, with the radio button next to port highlighted." +msgstr "" + +#: ../../content/applications/general/iot/config/windows_iot.rst:241 +msgid "On the :guilabel:`Protocols and Ports` page, choose the radio button for :guilabel:`TCP`, under :guilabel:`Does this rule apply to TCP or UDP?`." +msgstr "" + +#: ../../content/applications/general/iot/config/windows_iot.rst:244 +msgid "Next, under :guilabel:`Does this rule apply to all local ports or specific ports?`, select the radio button for :guilabel:`Specific local ports`. Then, enter `9050`, and click :guilabel:`Next` to continue." +msgstr "" + +#: ../../content/applications/general/iot/config/windows_iot.rst:-1 +msgid "Protocol/port configuration window with TCP, specific port (9050) and Next highlighted." +msgstr "" + +#: ../../content/applications/general/iot/config/windows_iot.rst:252 +msgid "The next screen is the :guilabel:`Action` page. Under :guilabel:`What action should be taken when a connection matches the specified conditions?`, choose the radio button for :guilabel:`Allow the connection`. Then, click :guilabel:`Next` to continue." +msgstr "" + +#: ../../content/applications/general/iot/config/windows_iot.rst:256 +msgid "A :guilabel:`Profile` page appears. Under :guilabel:`When does this rule apply?`, leave the three boxes checked for: :guilabel:`Domain`, :guilabel:`Private`, and :guilabel:`Public`. Click :guilabel:`Next` to continue to the naming convention page." +msgstr "" + +#: ../../content/applications/general/iot/config/windows_iot.rst:260 +msgid "On the :guilabel:`Name` page, enter `Odoo Worldline`, under the :guilabel:`Name` field. Enter a :guilabel:`Description (optional)`. Finally, once ready, click :guilabel:`Finish`." +msgstr "" + +#: ../../content/applications/general/iot/config/windows_iot.rst:263 +msgid "The final :guilabel:`Inbound rule` should appear as follows:" +msgstr "" + +#: ../../content/applications/general/iot/config/windows_iot.rst:270 +msgid "Odoo Worldline" +msgstr "" + +#: ../../content/applications/general/iot/config/windows_iot.rst:271 +msgid "Profile" +msgstr "" + +#: ../../content/applications/general/iot/config/windows_iot.rst:272 +msgid "All" +msgstr "" + +#: ../../content/applications/general/iot/config/windows_iot.rst:273 +msgid "Enabled" +msgstr "" + +#: ../../content/applications/general/iot/config/windows_iot.rst:274 +msgid "Yes" +msgstr "" + +#: ../../content/applications/general/iot/config/windows_iot.rst:275 +msgid "Action" +msgstr "" + +#: ../../content/applications/general/iot/config/windows_iot.rst:276 +msgid "Allow" +msgstr "" + +#: ../../content/applications/general/iot/config/windows_iot.rst:277 +msgid "Override" +msgstr "" + +#: ../../content/applications/general/iot/config/windows_iot.rst:278 +msgid "No" +msgstr "" + +#: ../../content/applications/general/iot/config/windows_iot.rst:279 +msgid "Program" +msgstr "" + +#: ../../content/applications/general/iot/config/windows_iot.rst:280 +#: ../../content/applications/general/iot/config/windows_iot.rst:282 +#: ../../content/applications/general/iot/config/windows_iot.rst:284 +#: ../../content/applications/general/iot/config/windows_iot.rst:290 +#: ../../content/applications/general/iot/config/windows_iot.rst:292 +#: ../../content/applications/general/iot/config/windows_iot.rst:294 +#: ../../content/applications/general/iot/config/windows_iot.rst:296 +#: ../../content/applications/general/iot/config/windows_iot.rst:298 +#: ../../content/applications/general/iot/config/windows_iot.rst:302 +msgid "Any" +msgstr "" + +#: ../../content/applications/general/iot/config/windows_iot.rst:281 +msgid "Local Address" +msgstr "" + +#: ../../content/applications/general/iot/config/windows_iot.rst:283 +msgid "Remote Address" +msgstr "" + +#: ../../content/applications/general/iot/config/windows_iot.rst:285 +msgid "Protocol" +msgstr "" + +#: ../../content/applications/general/iot/config/windows_iot.rst:286 +msgid "TCP" +msgstr "" + +#: ../../content/applications/general/iot/config/windows_iot.rst:287 +msgid "Local Port" +msgstr "" + +#: ../../content/applications/general/iot/config/windows_iot.rst:288 +msgid "9050" +msgstr "" + +#: ../../content/applications/general/iot/config/windows_iot.rst:289 +msgid "Remote Port" +msgstr "" + +#: ../../content/applications/general/iot/config/windows_iot.rst:291 +msgid "Authorized Users" +msgstr "" + +#: ../../content/applications/general/iot/config/windows_iot.rst:293 +msgid "Authorized Computers" +msgstr "" + +#: ../../content/applications/general/iot/config/windows_iot.rst:295 +msgid "Authorized Local Principals" +msgstr "" + +#: ../../content/applications/general/iot/config/windows_iot.rst:297 +msgid "Local User Owner" +msgstr "" + +#: ../../content/applications/general/iot/config/windows_iot.rst:299 +msgid "PolicyAppld" +msgstr "" + +#: ../../content/applications/general/iot/config/windows_iot.rst:300 +msgid "None" +msgstr "" + +#: ../../content/applications/general/iot/config/windows_iot.rst:301 +msgid "Application Package" +msgstr "" + +#: ../../content/applications/general/iot/config/windows_iot.rst:305 +msgid "Uninstalling Windows IoT" +msgstr "" + +#: ../../content/applications/general/iot/config/windows_iot.rst:307 +msgid "Uninstalling the Windows virtual :abbr:`IoT (Internet of Things)` box is done through the Windows program manager. Using any Windows version, search for `program`. Then, select :guilabel:`Add or Remove Programs` located in the control panel. Search for `Odoo` and click the :guilabel:`three dot menu` to uninstall." +msgstr "" + +#: ../../content/applications/general/iot/config/windows_iot.rst:312 +msgid "Confirm the un-installation and follow the steps to uninstall through the Odoo uninstall guide." +msgstr "" + +#: ../../content/applications/general/iot/devices.rst:5 +msgid "Devices" +msgstr "" + +#: ../../content/applications/general/iot/devices/camera.rst:3 +msgid "Connect a camera" +msgstr "" + +#: ../../content/applications/general/iot/devices/camera.rst:5 +msgid "A camera can be connected to an :abbr:`IoT (Internet of Things)` box with an Odoo database in just a few steps. Once a camera is connected to an :abbr:`IoT (Internet of Things)` box, it can be used in a manufacturing process, or it can be linked to a quality control point/quality check. Doing so allows for the taking of pictures when a chosen quality control point/check has been reached, or when a specific key is pressed during manufacturing." +msgstr "" + +#: ../../content/applications/general/iot/devices/camera.rst:12 +#: ../../content/applications/general/iot/devices/footswitch.rst:14 +#: ../../content/applications/general/iot/devices/printer.rst:11 +#: ../../content/applications/general/iot/devices/scale.rst:10 +#: ../../content/applications/general/iot/devices/screen.rst:18 +msgid "Connection" +msgstr "" + +#: ../../content/applications/general/iot/devices/camera.rst:14 +msgid "To connect a camera to an :abbr:`IoT (Internet of Things)` box, simply connect the two via cable. This is usually done with a :abbr:`USB (Universal Serial Bus)` cable of some sort." +msgstr "" + +#: ../../content/applications/general/iot/devices/camera.rst:17 +msgid "If the camera is `supported `_, there is no need to set up anything, as it'll be detected as soon as it's connected." +msgstr "" + +#: ../../content/applications/general/iot/devices/camera.rst:-1 +msgid "Camera recognized on the IoT box." +msgstr "" + +#: ../../content/applications/general/iot/devices/camera.rst:25 +msgid "Link camera to quality control point in manufacturing process" +msgstr "" + +#: ../../content/applications/general/iot/devices/camera.rst:27 +msgid "In the :menuselection:`Quality app`, a device can be set up on a :guilabel:`Quality Control Point`. To do that, navigate to the :menuselection:`Quality app --> Quality Control --> Control Points` and open the desired :guilabel:`Control Point` that'll be linked to the camera." +msgstr "" + +#: ../../content/applications/general/iot/devices/camera.rst:31 +msgid "On the control point form, edit the control point by selecting the :guilabel:`Type` field, and clicking on :guilabel:`Take a Picture` from the drop-down menu. Doing so reveals a field called :guilabel:`Device`, wherein the attached *device* can be selected. :guilabel:`Save` the changes, if required." +msgstr "" + +#: ../../content/applications/general/iot/devices/camera.rst:-1 +msgid "Setting up the device on the quality control point." +msgstr "" + +#: ../../content/applications/general/iot/devices/camera.rst:40 +msgid "The camera is now useable with the selected quality control point. When the quality control point is reached during the manufacturing process, the database prompts the operator to take a picture." +msgstr "" + +#: ../../content/applications/general/iot/devices/camera.rst:-1 +msgid "Graphic user interface of the device on the quality control point." +msgstr "" + +#: ../../content/applications/general/iot/devices/camera.rst:48 +msgid "Quality control points can also be accessed by navigating to :menuselection:`IoT App --> Devices`. From here, select the device. There is a :guilabel:`Quality Control Points` tab, where they can be added with the device." +msgstr "" + +#: ../../content/applications/general/iot/devices/camera.rst:53 +msgid "On a quality check form, the :guilabel:`Type` of check can also be specified to :guilabel:`Take a Picture`. Navigate to :menuselection:`Quality app --> Quality Control --> Quality Checks --> New` to create a new quality check from the :guilabel:`Quality Checks` page." +msgstr "" + +#: ../../content/applications/general/iot/devices/camera.rst:58 +#: ../../content/applications/general/iot/devices/printer.rst:70 +msgid ":doc:`/applications/inventory_and_mrp/quality/quality_management/quality_control_points`" +msgstr "" + +#: ../../content/applications/general/iot/devices/camera.rst:59 +#: ../../content/applications/general/iot/devices/printer.rst:71 +msgid ":doc:`/applications/inventory_and_mrp/quality/quality_management/quality_alerts`" +msgstr "" + +#: ../../content/applications/general/iot/devices/camera.rst:62 +msgid "Link camera to a work center in the Manufacturing app" +msgstr "" + +#: ../../content/applications/general/iot/devices/camera.rst:64 +msgid "To link a camera to an action, it first needs to be configured on a work center. Navigate to :menuselection:`Manufacturing app --> Configuration --> Work Centers`. Next, go to the desired :guilabel:`Work Center` in which a camera will be used to reveal that specific work center's detail form. From here, add the device in the :guilabel:`IoT Triggers` tab, in the :guilabel:`Device` column, by clicking :guilabel:`Add a Line`." +msgstr "" + +#: ../../content/applications/general/iot/devices/camera.rst:70 +msgid "Now, the camera device can be linked to the :guilabel:`Action` column drop-down option labeled :guilabel:`Take a Picture`. A key can also be added to trigger the action." +msgstr "" + +#: ../../content/applications/general/iot/devices/camera.rst:74 +msgid "The first trigger listed is chosen first. The order of triggers matters, and they can be dragged into any desired order." +msgstr "" + +#: ../../content/applications/general/iot/devices/camera.rst:78 +msgid "On the :guilabel:`Work Order` screen, a status graphic indicates whether the database is correctly connected to the camera." +msgstr "" + +#: ../../content/applications/general/iot/devices/camera.rst:82 +#: ../../content/applications/general/iot/devices/footswitch.rst:52 +#: ../../content/applications/general/iot/devices/measurement_tool.rst:92 +#: ../../content/applications/general/iot/devices/printer.rst:95 +msgid ":ref:`workcenter_iot`" +msgstr "" + +#: ../../content/applications/general/iot/devices/footswitch.rst:3 +msgid "Connect a footswitch" +msgstr "" + +#: ../../content/applications/general/iot/devices/footswitch.rst:5 +msgid "When working in a manufacturing environment, it's always better for an operator to have both hands available at all times. Odoo's :abbr:`IoT (Internet of Things)` box makes this possible when using a footswitch." +msgstr "" + +#: ../../content/applications/general/iot/devices/footswitch.rst:9 +msgid "In fact, with a footswitch, the operator is able to go from one screen to another, and perform actions using their foot. This can be configured in just a few steps on the work center in the *Manufacturing* app." +msgstr "" + +#: ../../content/applications/general/iot/devices/footswitch.rst:16 +msgid "To connect a footswitch to the :abbr:`IoT (Internet of Things)` box, connect the two devices via cable. More often than not, this is done with a :abbr:`USB (Universal Serial Bus)` cable." +msgstr "" + +#: ../../content/applications/general/iot/devices/footswitch.rst:19 +msgid "If the footswitch is a `supported device `_, there is no need to take further action, since it'll be automatically detected when connected." +msgstr "" + +#: ../../content/applications/general/iot/devices/footswitch.rst:-1 +msgid "Footswitch recognized on the IoT box." +msgstr "" + +#: ../../content/applications/general/iot/devices/footswitch.rst:27 +msgid "Link a footswitch to a work center in the Odoo Manufacturing app" +msgstr "" + +#: ../../content/applications/general/iot/devices/footswitch.rst:29 +msgid "To link a footswitch to an action, it first needs to be configured on a work center. Navigate to :menuselection:`Manufacturing app --> Configuration --> Work Centers`. From here, go to the desired :guilabel:`Work Center` in which the footswitch will be used, and add the device in the :guilabel:`IoT Triggers` tab, under the :guilabel:`Device` column, by selecting :guilabel:`Add a Line`. Doing so means the footswitch can be linked to an option in the :guilabel:`Action` column drop-down, and optionally, a key can be added to trigger it. An example of an :guilabel:`Action` in the *Manufacturing app* could be the :guilabel:`Validate` or :guilabel:`Mark as Done` buttons on a manufacturing work order." +msgstr "" + +#: ../../content/applications/general/iot/devices/footswitch.rst:-1 +msgid "Footswitch trigger setup on the Odoo database." +msgstr "" + +#: ../../content/applications/general/iot/devices/footswitch.rst:43 +msgid "It should be noted that the first listed trigger is chosen first. So, the order matters, and these triggers can be dragged into any order. In the picture above, using the footswitch automatically skips the part of the process that's currently being worked on." +msgstr "" + +#: ../../content/applications/general/iot/devices/footswitch.rst:48 +msgid "On the :guilabel:`Work Order` screen, a status graphic indicates whether the database is correctly connected to the footswitch." +msgstr "" + +#: ../../content/applications/general/iot/devices/measurement_tool.rst:3 +msgid "Connect a measurement tool" +msgstr "" + +#: ../../content/applications/general/iot/devices/measurement_tool.rst:7 +msgid "With Odoo's :abbr:`IoT (Internet of Things)` box, it is possible to connect measurement tools to the Odoo database for use in the *Quality app* on a quality control point/quality check, or for use in a work center during the manufacturing process." +msgstr "" + +#: ../../content/applications/general/iot/devices/measurement_tool.rst:11 +msgid "Find the list of supported devices here: `Supported devices `_." +msgstr "" + +#: ../../content/applications/general/iot/devices/measurement_tool.rst:15 +msgid "Connect with universal serial bus (USB)" +msgstr "" + +#: ../../content/applications/general/iot/devices/measurement_tool.rst:17 +msgid "To add a device connected by :abbr:`USB (Universal Serial Bus)`, plug the :abbr:`USB (Universal Serial Bus)` cable into the :abbr:`IoT (Internet of Things)` box, and the device appears in the Odoo database." +msgstr "" + +#: ../../content/applications/general/iot/devices/measurement_tool.rst:-1 +msgid "Measurement tool recognized on the IoT box." +msgstr "" + +#: ../../content/applications/general/iot/devices/measurement_tool.rst:26 +msgid "Connect with bluetooth" +msgstr "" + +#: ../../content/applications/general/iot/devices/measurement_tool.rst:28 +msgid "Activate the Bluetooth functionality on the device (see the device manual for further explanation), and the :abbr:`IoT (Internet of Things)` box automatically connects to the device." +msgstr "" + +#: ../../content/applications/general/iot/devices/measurement_tool.rst:-1 +msgid "Bluetooth indicator on measurement tool." +msgstr "" + +#: ../../content/applications/general/iot/devices/measurement_tool.rst:37 +msgid "Link a measurement tool to a quality control point in the manufacturing process" +msgstr "" + +#: ../../content/applications/general/iot/devices/measurement_tool.rst:39 +msgid "In the *Quality app*, a device can be set up on a quality control point. To do that, navigate to :menuselection:`Quality app --> Quality Control --> Control Points`, and open the desired control point to which the measurement tool should be linked." +msgstr "" + +#: ../../content/applications/general/iot/devices/measurement_tool.rst:43 +msgid "From here, edit the control point, by selecting the :guilabel:`Type` field, and clicking :guilabel:`Measure` from the drop-down menu. Doing so reveals a field called :guilabel:`Device`, where the attached device can be selected." +msgstr "" + +#: ../../content/applications/general/iot/devices/measurement_tool.rst:47 +msgid "Additionally, :guilabel:`Norm` and :guilabel:`Tolerance` can be configured. :guilabel:`Save` the changes, if required." +msgstr "" + +#: ../../content/applications/general/iot/devices/measurement_tool.rst:50 +msgid "At this point, the measurement tool is linked to the chosen quality control point. The value, which usually needs to be changed manually, is automatically updated while the tool is being used." +msgstr "" + +#: ../../content/applications/general/iot/devices/measurement_tool.rst:-1 +msgid "Measurement tool input in the Odoo database." +msgstr "" + +#: ../../content/applications/general/iot/devices/measurement_tool.rst:58 +#: ../../content/applications/general/iot/devices/printer.rst:60 +msgid "Quality control points can also be accessed by navigating to :menuselection:`IoT App --> Devices`, then select the device. There is a :guilabel:`Quality Control Points` tab, where they can be added with the device." +msgstr "" + +#: ../../content/applications/general/iot/devices/measurement_tool.rst:63 +msgid "On a quality check detail form, the :guilabel:`Type` of check can also be specified to :guilabel:`Measure`. Access a new quality check detail page, by navigating to :menuselection:`Quality app --> Quality Control --> Quality Checks --> New`." +msgstr "" + +#: ../../content/applications/general/iot/devices/measurement_tool.rst:68 +msgid ":doc:`../../../inventory_and_mrp/quality/quality_management/quality_control_points`" +msgstr "" + +#: ../../content/applications/general/iot/devices/measurement_tool.rst:69 +msgid ":doc:`../../../inventory_and_mrp/quality/quality_management/quality_alerts`" +msgstr "" + +#: ../../content/applications/general/iot/devices/measurement_tool.rst:72 +msgid "Link a measurement tool to a work center in the Manufacturing app" +msgstr "" + +#: ../../content/applications/general/iot/devices/measurement_tool.rst:74 +msgid "To link a measurement tool to an action, it first needs to be configured on a work center. To do that, navigate to :menuselection:`Manufacturing app --> Configuration --> Work Centers`. Then, select the desired work center in which the measurement tool will be used." +msgstr "" + +#: ../../content/applications/general/iot/devices/measurement_tool.rst:78 +msgid "On the work center page, add the device in the :guilabel:`IoT Triggers` tab, under the :guilabel:`Device` column, by selecting :guilabel:`Add a Line`. Then, the measurement tool can be linked to the :guilabel:`Action` drop-down menu option labeled :guilabel:`Take Measure`. A key can be added to trigger the action." +msgstr "" + +#: ../../content/applications/general/iot/devices/measurement_tool.rst:84 +msgid "It should be noted that the first listed trigger is chosen first. The order matters, and these triggers can be dragged into any order." +msgstr "" + +#: ../../content/applications/general/iot/devices/measurement_tool.rst:88 +msgid "On the :guilabel:`Work Order` screen, a status graphic indicates whether the database is correctly connected to the measurement tool." +msgstr "" + +#: ../../content/applications/general/iot/devices/printer.rst:3 +msgid "Connect a printer" +msgstr "" + +#: ../../content/applications/general/iot/devices/printer.rst:5 +msgid "Printer installation can be done in a few easy steps. The printer can be used to print receipts, labels, orders, or even reports from the different Odoo apps. In addition, printer actions can be assigned as an *action on a trigger* during the manufacturing process, or added onto a quality control point or a quality check." +msgstr "" + +#: ../../content/applications/general/iot/devices/printer.rst:13 +msgid "The :abbr:`IoT (Internet of Things)` box supports printers connected through :abbr:`USB (Universal Serial Bus)`, network connection, or Bluetooth. `Supported printers `__ are detected automatically, and appear in the :guilabel:`Devices` list of the *IoT app*." +msgstr "" + +#: ../../content/applications/general/iot/devices/printer.rst:-1 +msgid "The printer as it would appear in the IoT app devices list." +msgstr "" + +#: ../../content/applications/general/iot/devices/printer.rst:23 +msgid "The printer can take up to two minutes to appear in the *IoT app* devices list." +msgstr "" + +#: ../../content/applications/general/iot/devices/printer.rst:26 +msgid "Link printer" +msgstr "" + +#: ../../content/applications/general/iot/devices/printer.rst:29 +msgid "Link printer to work orders" +msgstr "" + +#: ../../content/applications/general/iot/devices/printer.rst:31 +msgid "*Work Orders* can be linked to printers, via a quality control point, to print labels for manufactured products." +msgstr "" + +#: ../../content/applications/general/iot/devices/printer.rst:34 +msgid "In the *Quality app*, a device can be set up on a quality control point. To do that, go to the :menuselection:`Quality app --> Quality Control --> Control Points`, and open the desired control point to which the printer will be linked." +msgstr "" + +#: ../../content/applications/general/iot/devices/printer.rst:39 +msgid "A *Manufacturing Operation* and *Work Order Operation* need to be attached to a quality control point before the :guilabel:`Type` field allows for the :guilabel:`Print Label` option to be selected." +msgstr "" + +#: ../../content/applications/general/iot/devices/printer.rst:43 +msgid "From here, edit the control point, by selecting the :guilabel:`Type` field, and selecting :guilabel:`Print Label` from the drop-down menu of options. Doing so reveals a field called :guilabel:`Device`, where the attached *device* can be selected. :guilabel:`Save` the changes, if required." +msgstr "" + +#: ../../content/applications/general/iot/devices/printer.rst:-1 +msgid "This is the quality control point setup." +msgstr "" + +#: ../../content/applications/general/iot/devices/printer.rst:52 +msgid "The printer can now be used with the selected quality control point. When the quality control point is reached during the manufacturing process, the database presents the option to print labels for a specific product." +msgstr "" + +#: ../../content/applications/general/iot/devices/printer.rst:65 +msgid "On a quality check detail form, the :guilabel:`Type` of check can also be specified to :guilabel:`Print Label`. To create new quality checks, navigate to :menuselection:`Quality app --> Quality Control --> Quality Checks --> New`." +msgstr "" + +#: ../../content/applications/general/iot/devices/printer.rst:74 +msgid "Link a printer to a work center in the Manufacturing app" +msgstr "" + +#: ../../content/applications/general/iot/devices/printer.rst:76 +msgid "To link a printer to an action, it first needs to be configured on a work center. To do that, navigate to :menuselection:`Manufacturing app --> Configuration --> Work Centers`. From here, select the desired work center in which the printer will be used. Next, add the device in the :guilabel:`IoT Triggers` tab, under the :guilabel:`Device` column, by selecting :guilabel:`Add a Line`." +msgstr "" + +#: ../../content/applications/general/iot/devices/printer.rst:82 +msgid "Then, the printer can be linked to either of the following options in the :guilabel:`Actions` drop-down menu: :guilabel:`Print Labels`, :guilabel:`Print Operation`, or :guilabel:`Print Delivery Slip`. A key can also be added to trigger the action." +msgstr "" + +#: ../../content/applications/general/iot/devices/printer.rst:87 +msgid "The first listed trigger on the form will be chosen first. So, the order matters, and these triggers can be dragged into any order." +msgstr "" + +#: ../../content/applications/general/iot/devices/printer.rst:91 +msgid "On the :guilabel:`Work Order` screen, a status graphic indicates whether the database is correctly connected to the printer." +msgstr "" + +#: ../../content/applications/general/iot/devices/printer.rst:98 +msgid "Link printer to reports" +msgstr "" + +#: ../../content/applications/general/iot/devices/printer.rst:100 +msgid "It's also possible to link a type of report to a certain printer. In the *IoT app*, go to the :guilabel:`Devices` menu, and select the desired printer that needs to be configured." +msgstr "" + +#: ../../content/applications/general/iot/devices/printer.rst:103 +msgid "From here, click :guilabel:`Edit`, go to the :guilabel:`Printer Reports` tab, and select :guilabel:`Add a line`. In the window that appears, check all the types of :guilabel:`Reports` that should be linked to this printer." +msgstr "" + +#: ../../content/applications/general/iot/devices/printer.rst:-1 +msgid "The printer devices listed in the IoT Devices menu." +msgstr "" + +#: ../../content/applications/general/iot/devices/printer.rst:111 +msgid "Now, each time :guilabel:`Print` is selected in the control panel, instead of downloading a PDF, a pop-up appears which displays all the printer(s) linked to the report. Then Odoo sends the report to the selected printer(s), and automatically prints it." +msgstr "" + +#: ../../content/applications/general/iot/devices/printer.rst:116 +msgid ":doc:`POS Order Printing <../../../sales/point_of_sale/restaurant/kitchen_printing>`" +msgstr "" + +#: ../../content/applications/general/iot/devices/printer.rst:119 +msgid "Reports can also be configured in the :guilabel:`Technical Menu` while in :ref:`debug mode `. To do that, navigate to :menuselection:`Settings App --> Technical Menu --> Actions --> Reports`. From here, the individual report can be found in this list, where the :guilabel:`IoT Device` can be set on the report." +msgstr "" + +#: ../../content/applications/general/iot/devices/scale.rst:3 +msgid "Connect a scale" +msgstr "" + +#: ../../content/applications/general/iot/devices/scale.rst:5 +msgid "A scale can be connected to the :abbr:`IoT (Internet of Things)` box on an Odoo database in a few easy steps. After setup, the *Point of Sale* app can be used to weigh products, which is helpful if their prices are calculated based on weight." +msgstr "" + +#: ../../content/applications/general/iot/devices/scale.rst:12 +msgid "To link the scale to the :abbr:`IoT (Internet of Things)` box, connect it with a :abbr:`USB (Universal Serial Bus)` cable." +msgstr "" + +#: ../../content/applications/general/iot/devices/scale.rst:16 +msgid "In some cases, a serial port to :abbr:`USB (Universal Serial Bus)` adapter may be needed." +msgstr "" + +#: ../../content/applications/general/iot/devices/scale.rst:18 +msgid "If the scale is `compatible with Odoo IoT Box `_, there is no need to set up anything because it will be automatically detected as soon as it is connected." +msgstr "" + +#: ../../content/applications/general/iot/devices/scale.rst:-1 +msgid "IOT box auto detection." +msgstr "" + +#: ../../content/applications/general/iot/devices/scale.rst:25 +msgid "The :abbr:`IoT (Internet of Things)` box may need to be restarted and the scale's drivers may need to be downloaded to the box in some cases. To update the drivers, go to the :abbr:`IoT (Internet of Things)` box homepage and click on :guilabel:`Drivers List`. Then, click on :guilabel:`Load Drivers`." +msgstr "" + +#: ../../content/applications/general/iot/devices/scale.rst:-1 +msgid "View of the IoT box settings and driver list." +msgstr "" + +#: ../../content/applications/general/iot/devices/scale.rst:34 +msgid "If loading the drivers still doesn't allow for the scale to function, it may be that the scale is not compatible with the Odoo :abbr:`IoT (Internet of Things)` box. In this case, a different scale will need to be used." +msgstr "" + +#: ../../content/applications/general/iot/devices/scale.rst:39 +msgid "Use a scale in a point of sale (POS) system" +msgstr "" + +#: ../../content/applications/general/iot/devices/scale.rst:41 +msgid "To use the scale in the *Point of Sale app*, go to :menuselection:`PoS app --> 3-Dot Menu on the PoS --> Settings`, then enable the :abbr:`IoT (Internet of Things)` box feature. After this is complete, the scale device can be set." +msgstr "" + +#: ../../content/applications/general/iot/devices/scale.rst:45 +msgid "Select the scale from the :guilabel:`Electronic Scale` drop-down menu. Then click :guilabel:`Save` to save the changes, if required." +msgstr "" + +#: ../../content/applications/general/iot/devices/scale.rst:-1 +msgid "List of the external tools that can be used with PoS and the IoT box." +msgstr "" + +#: ../../content/applications/general/iot/devices/scale.rst:52 +msgid "The scale is now available in all the :abbr:`PoS (Point of Sale)` sessions. Now, if a product has a price per weight set, clicking on it on the :guilabel:`PoS` screen opens the scale screen, where the cashier can weigh the product and add the correct price to the cart." +msgstr "" + +#: ../../content/applications/general/iot/devices/scale.rst:-1 +msgid "Electronic Scale dashboard view when no items are being weighed." +msgstr "" + +#: ../../content/applications/general/iot/devices/screen.rst:3 +msgid "Connect a screen" +msgstr "" + +#: ../../content/applications/general/iot/devices/screen.rst:5 +msgid "In Odoo, an :abbr:`IoT (Internet of Things)` box can be connected to a screen display. After being configured, the screen can be used to display a Point of Sale (PoS) order to a client." +msgstr "" + +#: ../../content/applications/general/iot/devices/screen.rst:10 +msgid "An example of a PoS (point of sale) order on a screen display." +msgstr "" + +#: ../../content/applications/general/iot/devices/screen.rst:12 +msgid "Access the customer display by going to the :abbr:`IoT (Internet of Things)` box homepage and clicking on the :guilabel:`PoS Display` button. To get to the :abbr:`IoT (Internet of Things)` box homepage, navigate to :menuselection:`IoT app --> IoT Boxes` and click on the :abbr:`IoT (Internet of Things)` box homepage link." +msgstr "" + +#: ../../content/applications/general/iot/devices/screen.rst:20 +msgid "The way to connect the screen display to the :abbr:`IoT (Internet of Things)` box differs depending on the model." +msgstr "" + +#: ../../content/applications/general/iot/devices/screen.rst:25 +msgid "IoT Box model 4" +msgstr "" + +#: ../../content/applications/general/iot/devices/screen.rst:27 +msgid "Connect up to two screens with micro-HDMI cables on the side of the :abbr:`IoT (Internet of Things)` box. If two screens are connected, they can display distinct content (see :ref:`Screen Usage `)." +msgstr "" + +#: ../../content/applications/general/iot/devices/screen.rst:31 +msgid "IoT Box model 3" +msgstr "" + +#: ../../content/applications/general/iot/devices/screen.rst:33 +msgid "Connect the screen with an HDMI cable on the side of the :abbr:`IoT (Internet of Things)` box." +msgstr "" + +#: ../../content/applications/general/iot/devices/screen.rst:36 +msgid ":ref:`See the Raspberry Pi Schema `." +msgstr "" + +#: ../../content/applications/general/iot/devices/screen.rst:39 +msgid "Screen(s) should be connected before the :abbr:`IoT (Internet of Things)` box is switched on. If it is already on, connect the screen(s), and then restart the :abbr:`IoT (Internet of Things)` box by unplugging it for ten seconds and plugging it back into its power source." +msgstr "" + +#: ../../content/applications/general/iot/devices/screen.rst:44 +msgid "The usage of HDMI/micro-HDMI adapters may cause issues which will result in a blank, black screen on the screen display. Using the specific cable for the display connection is recommended." +msgstr "" + +#: ../../content/applications/general/iot/devices/screen.rst:47 +msgid "If the connection was successful, the screen should display the :guilabel:`POS Client display` screen." +msgstr "" + +#: ../../content/applications/general/iot/devices/screen.rst:-1 +msgid "The default \"POS Client Display\" screen that appears when a screen display is successfully\n" +"connected to an IoT box." +msgstr "" + +#: ../../content/applications/general/iot/devices/screen.rst:55 +msgid "The screen should also appear in the list of :guilabel:`Displays` on the :abbr:`IoT (Internet of Things)` box homepage. Alternatively, the display can be seen by accessing :menuselection:`IoT app --> Devices`." +msgstr "" + +#: ../../content/applications/general/iot/devices/screen.rst:-1 +msgid "An example of a screen display name shown on the IoT Box Home Page." +msgstr "" + +#: ../../content/applications/general/iot/devices/screen.rst:64 +msgid "If no screen is detected, a default display named :guilabel:`Distant Display` will be displayed instead. This indicates that there is no hardware screen connected." +msgstr "" + +#: ../../content/applications/general/iot/devices/screen.rst:0 +msgid "The \"Distant Display\" screen name will be used if no screen is detected." +msgstr "" + +#: ../../content/applications/general/iot/devices/screen.rst:74 +msgid "Usage" +msgstr "" + +#: ../../content/applications/general/iot/devices/screen.rst:77 +msgid "Show Point of Sale orders to customers" +msgstr "" + +#: ../../content/applications/general/iot/devices/screen.rst:79 +msgid "To use the screen in the *Point of Sale app*, go to :menuselection:`Point of Sale --> Configuration --> Point of Sale`, select a :abbr:`PoS (Point of Sale)`, click :guilabel:`Edit` if necessary, and enable the :guilabel:`IoT Box` feature." +msgstr "" + +#: ../../content/applications/general/iot/devices/screen.rst:83 +msgid "Next, select the screen from the :guilabel:`Customer Display` drop-down menu. Then click :guilabel:`Save`, if required." +msgstr "" + +#: ../../content/applications/general/iot/devices/screen.rst:-1 +msgid "Connect the screen display to the Point of Sale app." +msgstr "" + +#: ../../content/applications/general/iot/devices/screen.rst:90 +msgid "The screen is now available for :abbr:`PoS (Point of Sale)` sessions. A screen icon will appear in the menu at the top of the screen to indicate the screen's connection status." +msgstr "" + +#: ../../content/applications/general/iot/devices/screen.rst:-1 +msgid "The \"screen\" icon on the Point of Sale display shows the connection status with the\n" +"screen." +msgstr "" + +#: ../../content/applications/general/iot/devices/screen.rst:98 +msgid "The screen will automatically show the :abbr:`PoS (Point of Sale)` orders and update when changes are made to the order." +msgstr "" + +#: ../../content/applications/general/iot/devices/screen.rst:-1 +msgid "An example of a PoS order on a screen display." +msgstr "" + +#: ../../content/applications/general/iot/devices/screen.rst:106 +msgid "Display a website on the screen" +msgstr "" + +#: ../../content/applications/general/iot/devices/screen.rst:108 +msgid "Open the screen form view by accessing :menuselection:`IoT app --> Devices --> Customer Display`. This allows the user to choose a particular website URL to display on the screen using the :guilabel:`Display URL` field." msgstr "" #: ../../content/applications/general/users.rst:5 -msgid "Users and companies" +msgid "Users" msgstr "" #: ../../content/applications/general/users.rst:7 -msgid "Odoo defines a *user* as someone who has access to a database to perform daily tasks. You can add as many users as you need and, in order to restrict the type of information each user can access, rules can be applied. Users and access rights can be added and changed at any point." +msgid "Odoo defines a **user** as someone who has access to a database to perform daily tasks. You can add as many users as you need and, in order to restrict the type of information each user can access, rules can be applied. Users and access rights can be added and changed at any point." +msgstr "" + +#: ../../content/applications/general/users.rst:12 +msgid ":doc:`users/language`" +msgstr "" + +#: ../../content/applications/general/users.rst:13 +msgid ":doc:`users/access_rights`" +msgstr "" + +#: ../../content/applications/general/users.rst:18 +msgid "Add individual users" +msgstr "" + +#: ../../content/applications/general/users.rst:20 +msgid "Go to :menuselection:`Settings --> Manage Users` and click on *Create*." +msgstr "" + +#: ../../content/applications/general/users.rst:-1 +msgid "View of the settings page emphasizing the manage users field in Odoo" +msgstr "" + +#: ../../content/applications/general/users.rst:28 +msgid "Fill in the form with the needed information. Under the tab :doc:`Access Rights ` choose the group within each application the user can have access to." +msgstr "" + +#: ../../content/applications/general/users.rst:29 +msgid "The list of applications shown is based on the applications installed on the database." +msgstr "" + +#: ../../content/applications/general/users.rst:-1 +msgid "View of a user’s form emphasizing the access rights tab in Odoo" +msgstr "" + +#: ../../content/applications/general/users.rst:34 +msgid "When you are done editing the page and have *Saved* it, an invitation email is automatically sent to the user. The user must click on it to accept the invitation and create a login." +msgstr "" + +#: ../../content/applications/general/users.rst:-1 +msgid "View of a user’s form with a notification that the invitation email has been sent in Odoo" +msgstr "" + +#: ../../content/applications/general/users.rst:41 +msgid "Remember that subscription prices follow the number of users. Refer to our `pricing page `_ for more information." +msgstr "" + +#: ../../content/applications/general/users.rst:45 +msgid "With the :ref:`developer mode ` activated, *User Types* can be selected." +msgstr "" + +#: ../../content/applications/general/users.rst:-1 +msgid "View of a user’s form in developer mode emphasizing the user type field in Odoo" +msgstr "" + +#: ../../content/applications/general/users.rst:51 +msgid "The *Portal* and *Public* options do not allow you to choose access rights. Members have specific ones (such as record rules and restricted menus) and usually do not belong to the usual Odoo groups." +msgstr "" + +#: ../../content/applications/general/users.rst:58 +msgid "Deactivate users" +msgstr "" + +#: ../../content/applications/general/users.rst:60 +msgid "Go to :menuselection:`Settings --> Users & Companies --> Users`, open the user you want to deactivate, click on *Action*, and then on *Archive*." +msgstr "" + +#: ../../content/applications/general/users.rst:64 +msgid "**Never** deactivate the main user (*admin*)." +msgstr "" + +#: ../../content/applications/general/users.rst:69 +msgid "Passwords management" +msgstr "" + +#: ../../content/applications/general/users.rst:74 +msgid "Reset passwords" +msgstr "" + +#: ../../content/applications/general/users.rst:79 +msgid "Enable password resets from login page" +msgstr "" + +#: ../../content/applications/general/users.rst:81 +msgid "It is possible to enable password resets directly from the login page." +msgstr "" + +#: ../../content/applications/general/users.rst:83 +msgid "To do so, go to :menuselection:`Settings --> Permissions`, activate **Password Reset** and *Save*." +msgstr "" + +#: ../../content/applications/general/users.rst:-1 +msgid "Enabling Password Reset in Odoo Settings" +msgstr "" + +#: ../../content/applications/general/users.rst:91 +msgid "Send reset instructions to users" +msgstr "" + +#: ../../content/applications/general/users.rst:93 +msgid "Go to :menuselection:`Settings --> Users & Companies --> Users`, select the user out of the list and click on *Send Password Reset Instructions* on its user form. An email is automatically sent to them." +msgstr "" + +#: ../../content/applications/general/users.rst:98 +msgid "The *Send Password Reset Instructions* button only appears if the Odoo invitation email has already been confirmed by the user." +msgstr "" + +#: ../../content/applications/general/users.rst:101 +msgid "This email contains all the instructions needed to reset the password, along with a link redirecting the user to an Odoo login page." +msgstr "" + +#: ../../content/applications/general/users.rst:-1 +msgid "Example of an email with a password reset link for an Odoo account" +msgstr "" + +#: ../../content/applications/general/users.rst:110 +msgid "Change users’ passwords" +msgstr "" + +#: ../../content/applications/general/users.rst:112 +msgid "Go to :menuselection:`Settings --> Users & Companies --> Users` and select a user to access its form. Click on the *Action* button and select *Change Password*." +msgstr "" + +#: ../../content/applications/general/users.rst:-1 +msgid "Change another user's password on Odoo" +msgstr "" + +#: ../../content/applications/general/users.rst:118 +msgid "Enter a new password and confirm by clicking on *Change Password*." +msgstr "" + +#: ../../content/applications/general/users.rst:121 +msgid "This operation only modifies the password of the users locally and does not affect their odoo.com account. If you want to change the odoo.com password, you can :ref:`send the password reset instructions `." +msgstr "" + +#: ../../content/applications/general/users.rst:125 +msgid "Click on *Change Password* one more time. You are then redirected to an Odoo login page where you can reaccess your database using your new password." +msgstr "" + +#: ../../content/applications/general/users.rst:131 +msgid "Multi Companies" +msgstr "" + +#: ../../content/applications/general/users.rst:133 +msgid "The *Multi Companies* field allows you to set to which of the multiple companies database you hold the user can have access." +msgstr "" + +#: ../../content/applications/general/users.rst:137 +msgid "Note that if not handled correctly, it may be the source of a lot of inconsistent multi-company behaviors. Therefore, a good knowledge of Odoo is required. For technical explanations refer to :doc:`this ` documentation." +msgstr "" + +#: ../../content/applications/general/users.rst:-1 +msgid "View of a user’s form emphasizing the multi companies field in Odoo" +msgstr "" + +#: ../../content/applications/general/users.rst:146 +msgid ":doc:`companies`" +msgstr "" + +#: ../../content/applications/general/users/2fa.rst:3 +msgid "Two-factor Authentication" +msgstr "" + +#: ../../content/applications/general/users/2fa.rst:5 +msgid "Two-factor authentication (\"2FA\") is a good way to improve the security of an account, to make it less likely that an other person will manage to log in instead of you." +msgstr "" + +#: ../../content/applications/general/users/2fa.rst:9 +msgid "Practically, it means storing a secret inside an *authenticator* (usually your cell phone) and exchanging a code from the authenticator when you try to log in." +msgstr "" + +#: ../../content/applications/general/users/2fa.rst:13 +msgid "This means an attacker needs *both* to have guessed (or found) your password and to access (or steal) your authenticator, a more difficult proposition than either one or the other." +msgstr "" + +#: ../../content/applications/general/users/2fa.rst:18 +msgid "Requirements" +msgstr "" + +#: ../../content/applications/general/users/2fa.rst:20 +msgid "These lists are just examples, they are not endorsements of any specific software." +msgstr "" + +#: ../../content/applications/general/users/2fa.rst:23 +msgid "If you don't already have one, you will need to choose an authenticator." +msgstr "" + +#: ../../content/applications/general/users/2fa.rst:26 +msgid "Phone-based authenticators are the easiest and most common so we will assume you'll pick and install one on your phone, examples include `Authy `_, `FreeOTP `_, `Google Authenticator `_, `LastPass Authenticator `_, `Microsoft Authenticator `_, ...; password managers also commonly include :abbr:`2FA (two-factor authentication)` support e.g. `1Password `_, `Bitwarden `_, ..." +msgstr "" + +#: ../../content/applications/general/users/2fa.rst:39 +msgid "For the sake of demonstration we will be using Google Authenticator (not because it is any good but because it is quite common)." +msgstr "" + +#: ../../content/applications/general/users/2fa.rst:43 +msgid "Setting up two-factor authentication" +msgstr "" + +#: ../../content/applications/general/users/2fa.rst:45 +msgid "Once you have your authenticator of choice, go to the Odoo instance you want to setup :abbr:`2FA (two-factor authentication)`, then open :guilabel:`Preferences` (or :guilabel:`My Profile`):" +msgstr "" + +#: ../../content/applications/general/users/2fa.rst:52 +msgid "Open the :guilabel:`Account Security` tab, then click the :guilabel:`Enable two-factor authentication` button:" +msgstr "" + +#: ../../content/applications/general/users/2fa.rst:58 +msgid "Because this is a security-sensitive action, you will need to input your password:" +msgstr "" + +#: ../../content/applications/general/users/2fa.rst:64 +msgid "After which you will see this screen with a barcode:" +msgstr "" + +#: ../../content/applications/general/users/2fa.rst:69 +msgid "In most applications, you can simply *scan the barcode* via the authenticator of your choice, the authenticator will then take care of all the setup:" +msgstr "" + +#: ../../content/applications/general/users/2fa.rst:78 +msgid "If you can not scan the screen (e.g. because you are doing this set-up on the same phone as the authenticator application), you can click the provided link, or copy the secret to manually set-up your authenticator:" +msgstr "" + +#: ../../content/applications/general/users/2fa.rst:89 +msgid "Once this is done, the authenticator should display a *verification code* with some useful identifying information (e.g. the domain and login for which the code is):" +msgstr "" + +#: ../../content/applications/general/users/2fa.rst:96 +msgid "You can now input the code into the :guilabel:`Verification Code` field, then click the :guilabel:`Enable two-factor authentication` button." +msgstr "" + +#: ../../content/applications/general/users/2fa.rst:100 +msgid "Congratulation, your account is now protected by two-factor authentication!" +msgstr "" + +#: ../../content/applications/general/users/2fa.rst:107 +msgid "Logging in" +msgstr "" + +#: ../../content/applications/general/users/2fa.rst:109 +msgid "You should now :guilabel:`Log out` to follow along." +msgstr "" + +#: ../../content/applications/general/users/2fa.rst:111 +msgid "On the login page, input the username and password of the account for which you set up :abbr:`2FA (two-factor authentication)`, rather than immediately enter Odoo you will now get a second log-in screen:" +msgstr "" + +#: ../../content/applications/general/users/2fa.rst:118 +msgid "Get your authenticator, input the code it provides for the domain and account, validate, and you're now in." +msgstr "" + +#: ../../content/applications/general/users/2fa.rst:121 +msgid "And that's it. From now on, unless you disable :abbr:`2FA (two-factor authentication)` you will have a two-step log-in process rather than the old one-step process." +msgstr "" + +#: ../../content/applications/general/users/2fa.rst:125 +msgid "Don't lose your authenticator, if you do, you will need an *Odoo Administrator* to disable :abbr:`2FA (two-factor authentication)` on the account." msgstr "" #: ../../content/applications/general/users/access_rights.rst:3 @@ -3441,185 +5919,352 @@ msgstr "" msgid "Making changes in access rights can have a big impact on the database. For this reason, we recommend you to contact your Odoo Business Analyst or our Support Team, unless you have knowledge about Domains in Odoo." msgstr "" -#: ../../content/applications/general/users/companies.rst:3 -msgid "Companies" +#: ../../content/applications/general/users/azure.rst:3 +msgid "Microsoft Azure sign-in authentication" msgstr "" -#: ../../content/applications/general/users/companies.rst:5 -msgid "A centralized management environment allows you to select multiple companies simultaneously and set their specific warehouses, customers, equipment, and contacts. It provides you the ability to generate reports of aggregated figures without switching interfaces, which facilitates daily tasks and the overall management process." +#: ../../content/applications/general/users/azure.rst:5 +msgid "The Microsoft Azure OAuth sign-in authentication is a useful function that allows Odoo users to sign in to their database with their Microsoft Azure account." msgstr "" -#: ../../content/applications/general/users/companies.rst:13 -msgid "Manage companies and records" +#: ../../content/applications/general/users/azure.rst:8 +msgid "This is particularly helpful if the organization uses Azure Workspace, and wants employees within the organization to connect to Odoo using their Microsoft Accounts." msgstr "" -#: ../../content/applications/general/users/companies.rst:15 -msgid "Go to :menuselection:`Settings --> Manage Companies` and fill in the form with your company’s information. If a *Parent Company* is selected, records are shared between the two companies (as long as both environments are active)." +#: ../../content/applications/general/users/azure.rst:12 +msgid "Databases hosted on Odoo.com should not use OAuth login for the owner or administrator of the database as it would unlink the database from their Odoo.com account. If OAuth is set up for that user, the database will no longer be able to be duplicated, renamed, or otherwise managed from the Odoo.com portal." msgstr "" -#: ../../content/applications/general/users/companies.rst:-1 -msgid "Overview of a new company's form in Odoo" +#: ../../content/applications/general/users/azure.rst:18 +msgid ":doc:`../../productivity/calendar/outlook`" msgstr "" -#: ../../content/applications/general/users/companies.rst:24 -msgid "Activate the :ref:`developer mode ` to choose a *Favicon* for each of your companies, and easily identify them by the browser tabs. Set your favicons’ files size to 16x16 or 32x32 pixels. JPG, PNG, GIF, and ICO are extensions accepted." +#: ../../content/applications/general/users/azure.rst:19 +msgid ":doc:`../email_communication/azure_oauth`" msgstr "" -#: ../../content/applications/general/users/companies.rst:0 -msgid "View of a web browser and the favicon for a specific company chosen in Odoo" +#: ../../content/applications/general/users/azure.rst:24 +msgid "Integrating the Microsoft sign-in function requires configuration on Microsoft and Odoo." msgstr "" -#: ../../content/applications/general/users/companies.rst:33 -msgid "Switch between or select multiple companies by enabling their selection boxes to activate them. The grayed company is the one which environment is in use. To switch environments, click on the company’s name. In the example below, the user has access to three companies, two are activated, and the environment in use is of *JS Store US*." +#: ../../content/applications/general/users/azure.rst:27 +msgid "Odoo System Parameter" msgstr "" -#: ../../content/applications/general/users/companies.rst:-1 -msgid "View of the companies menu through the main dashboard in Odoo" +#: ../../content/applications/general/users/azure.rst:29 +msgid "First activate the :ref:`developer mode `, and then go to :menuselection:`Settings --> Technical --> System Parameters`." msgstr "" -#: ../../content/applications/general/users/companies.rst:42 -msgid "Data such as Products, Contacts, and Equipment can be shared or set to be shown for a specific company only. To do so, on their forms, choose between:" +#: ../../content/applications/general/users/azure.rst:32 +msgid "Click :guilabel:`Create` and on the new/blank form that appears, add the following system parameter `auth_oauth.authorization_header` to the :guilabel:`Key` field, and set the :guilabel:`Value` to `1`. Then click :guilabel:`Save` to finish." msgstr "" -#: ../../content/applications/general/users/companies.rst:45 -msgid "*A blank field*: the record is shared within all companies." +#: ../../content/applications/general/users/azure.rst:37 +msgid "Microsoft Azure dashboard" msgstr "" -#: ../../content/applications/general/users/companies.rst:46 -msgid "*Adding a company*: the record is visible to users logged in to that specific company." +#: ../../content/applications/general/users/azure.rst:42 +msgid "Now that the system parameters in Odoo have been set up, it's time to create a corresponding application inside of Microsoft Azure. To get started creating the new application, go to `Microsoft's Azure Portal `_. Log in with the :guilabel:`Microsoft Outlook Office 365` account if there is one, otherwise, log in with a personal :guilabel:`Microsoft account`." msgstr "" -#: ../../content/applications/general/users/companies.rst:-1 -msgid "View of a product's form emphasizing the company field in Odoo Sales" +#: ../../content/applications/general/users/azure.rst:49 +msgid "A user with administrative access to the *Azure Settings* must connect and perform the following configuration steps below." msgstr "" -#: ../../content/applications/general/users/companies.rst:53 -msgid "Employees' access" +#: ../../content/applications/general/users/azure.rst:52 +msgid "Next, navigate to the section labeled :guilabel:`Manage Microsoft Entra ID` (formally *Azure Active Directory*). The location of this link is usually in the center of the page." msgstr "" -#: ../../content/applications/general/users/companies.rst:55 -msgid "Once companies are created, manage your employees' :doc:`Access Rights ` for *Multi Companies*." +#: ../../content/applications/general/users/azure.rst:55 +msgid "Now, click on the :guilabel:`Add (+)` icon, located in the top menu, and then select :guilabel:`App registration` from the drop-down menu. On the :guilabel:`Register an application` screen, rename the :guilabel:`Name` field to `Odoo Login OAuth` or a similarly recognizable title. Under the :guilabel:`Supported account types` section select the option for :guilabel:`Accounts in this organizational directory only (Default Directory only - Single tenant)`." msgstr "" -#: ../../content/applications/general/users/companies.rst:-1 -msgid "View of an user form emphasizing the multi companies field under the access rights tabs\n" -"in Odoo" +#: ../../content/applications/general/users/azure.rst:62 +msgid "The :guilabel:`Supported account types` can vary by Microsoft account type and end use of the OAuth. For example: Is the login meant for internal users within one organization or is it meant for customer portal access? The above configuration is used for internal users in an organization." msgstr "" -#: ../../content/applications/general/users/companies.rst:64 -msgid "If a user has multiple companies *activated* on his database, and he is **editing** a record, the editing happens on the record's related company." +#: ../../content/applications/general/users/azure.rst:67 +msgid "Choose :guilabel:`Personal Microsoft accounts only` if the target audience is meant for portal users. Choose :guilabel:`Accounts in this organizational directory only (Default Directory only - Single tenant)` if the target audience is company users." msgstr "" -#: ../../content/applications/general/users/companies.rst:67 -msgid "Example: if editing a sale order issued under JS Store US while working on the JS Store Belgium environment, the changes are applied under JS Store US (the company from which the sale order was issued)." +#: ../../content/applications/general/users/azure.rst:71 +msgid "Under the :guilabel:`Redirect URL` section, select :guilabel:`Web` as the platform, and then input `https:///auth_oauth/signin` in the :guilabel:`URL` field. The Odoo base :abbr:`URL (Uniform Resource Locator)` is the canonical domain at which your Odoo instance can be reached (e.g. *mydatabase.odoo.com* if you are hosted on Odoo.com) in the :guilabel:`URL` field. Then, click :guilabel:`Register`, and the application is created." msgstr "" -#: ../../content/applications/general/users/companies.rst:68 -msgid "When **creating** a record, the company taken into account is:" +#: ../../content/applications/general/users/azure.rst:78 +msgid "Authentication" msgstr "" -#: ../../content/applications/general/users/companies.rst:70 -msgid "The current company (the one active) or," +#: ../../content/applications/general/users/azure.rst:80 +msgid "Edit the new app's authentication by clicking on the :guilabel:`Authentication` menu item in the left menu after being redirected to the application's settings from the previous step." msgstr "" -#: ../../content/applications/general/users/companies.rst:71 -msgid "No company is set (on products and contacts’ forms for example) or," +#: ../../content/applications/general/users/azure.rst:83 +msgid "Next, the type of *tokens* needed for the OAuth authentication will be chosen. These are not currency tokens but rather authentication tokens that are passed between Microsoft and Odoo. Therefore, there is no cost for these tokens; they are used merely for authentication purposes between two :abbr:`APIs (application programming interfaces)`. Select the tokens that should be issued by the authorization endpoint by scrolling down the screen and check the boxes labeled: :guilabel:`Access tokens (used for implicit flows)` and :guilabel:`ID tokens (used for implicit and hybrid flows)`." msgstr "" -#: ../../content/applications/general/users/companies.rst:72 -msgid "The company set is the one linked to the document (the same as if a record is being edited)." +#: ../../content/applications/general/users/azure.rst:-1 +msgid "Authentication settings and endpoint tokens." msgstr "" -#: ../../content/applications/general/users/companies.rst:75 -msgid "Documents’ format" +#: ../../content/applications/general/users/azure.rst:95 +msgid "Click :guilabel:`Save` to ensure these settings are saved." msgstr "" -#: ../../content/applications/general/users/companies.rst:77 -msgid "To set documents' formats according to each company, *activate* and *select* the respective one and, under *Settings*, click on *Configure Document Layout*." +#: ../../content/applications/general/users/azure.rst:98 +msgid "Gather credentials" msgstr "" -#: ../../content/applications/general/users/companies.rst:-1 -msgid "View of the settings page emphasizing the document layout field in Odoo" +#: ../../content/applications/general/users/azure.rst:100 +msgid "With the application created and authenticated in the Microsoft Azure console, credentials will be gathered next. To do so, click on the :guilabel:`Overview` menu item in the left-hand column. Select and copy the :guilabel:`Application (client) ID` in the window that appears. Paste this credential to a clipboard / notepad, as this credential will be used in the Odoo configuration later." msgstr "" -#: ../../content/applications/general/users/companies.rst:85 -msgid "Inter-Company Transactions" +#: ../../content/applications/general/users/azure.rst:105 +msgid "After finishing this step, click on :guilabel:`Endpoints` on the top menu and click the *copy icon* next to :guilabel:`OAuth 2.0 authorization endpoint (v2)` field. Paste this value in the clipboard / notepad." msgstr "" -#: ../../content/applications/general/users/companies.rst:87 -msgid "First, make sure each one of your companies is properly set in relation to:" +#: ../../content/applications/general/users/azure.rst:-1 +msgid "Application ID and OAuth 2.0 authorization endpoint (v2) credentials." msgstr "" -#: ../../content/applications/general/users/companies.rst:89 -msgid ":doc:`Chart of Accounts <../../finance/accounting/get_started/chart_of_accounts>`" +#: ../../content/applications/general/users/azure.rst:114 +msgid "Odoo setup" msgstr "" -#: ../../content/applications/general/users/companies.rst:90 -msgid ":doc:`Taxes <../../finance/accounting/taxes>`" +#: ../../content/applications/general/users/azure.rst:116 +msgid "Finally, the last step in the Microsoft Azure OAuth configuration is to configure some settings in Odoo. Navigate to :menuselection:`Settings --> Integrations --> OAuth Authentication` and check the box to activate the OAuth login feature. Click :guilabel:`Save` to ensure the progress is saved. Then, sign in to the database once the login screen loads." msgstr "" -#: ../../content/applications/general/users/companies.rst:91 -msgid ":doc:`Fiscal Positions <../../finance/accounting/taxes/fiscal_positions>`" +#: ../../content/applications/general/users/azure.rst:121 +msgid "Once again, navigate to :menuselection:`Settings --> Integrations --> OAuth Authentication` and click on :guilabel:`OAuth Providers`. Now, select :guilabel:`New` in the upper-left corner and name the provider `Azure`." msgstr "" -#: ../../content/applications/general/users/companies.rst:92 -msgid ":doc:`Journals <../../finance/accounting/bank>`" +#: ../../content/applications/general/users/azure.rst:125 +msgid "Paste the :guilabel:`Application (client) ID` from the previous section into the :guilabel:`Client ID` field. After completing this, paste the new :guilabel:`OAuth 2.0 authorization endpoint (v2)` value into the :guilabel:`Authorization URL` field." msgstr "" -#: ../../content/applications/general/users/companies.rst:93 -msgid ":doc:`Fiscal Localizations <../../finance/fiscal_localizations>`" +#: ../../content/applications/general/users/azure.rst:129 +msgid "For the :guilabel:`UserInfo URL` field, paste the following :abbr:`URL (Uniform Resource Locator)`: `https://graph.microsoft.com/oidc/userinfo`" msgstr "" -#: ../../content/applications/general/users/companies.rst:94 -msgid ":doc:`Pricelists <../../sales/sales/products_prices/prices/pricing>`" +#: ../../content/applications/general/users/azure.rst:132 +msgid "In the :guilabel:`Scope` field, paste the following value: `openid profile email`. Next, the Windows logo can be used as the CSS class on the login screen by entering the following value: `fa fa-fw fa-windows`, in the :guilabel:`CSS class` field." msgstr "" -#: ../../content/applications/general/users/companies.rst:96 -msgid "Now, activate the *Inter-Company Transactions* option under *Settings*. With the respective company *activated* and *selected*, choose if you would like operations between companies to be synchronized at an invoice/bills level or at a sales/purchase orders level." +#: ../../content/applications/general/users/azure.rst:136 +msgid "Check the box next to the :guilabel:`Allowed` field to enable the OAuth provider. Finally, add `Microsoft Azure` to the :guilabel:`Login button label` field. This text will appear next to the Windows logo on the login page." msgstr "" -#: ../../content/applications/general/users/companies.rst:-1 -msgid "View of the settings page emphasizing the inter company transaction field in Odoo" +#: ../../content/applications/general/users/azure.rst:-1 +msgid "Odoo provider setup in the Settings application." msgstr "" -#: ../../content/applications/general/users/companies.rst:104 -msgid "**Synchronize invoice/bills**: generates a bill/invoice when a company confirms a bill/invoice for the selected company." +#: ../../content/applications/general/users/azure.rst:144 +msgid ":guilabel:`Save` the changes to complete the OAuth authentication setup in Odoo." msgstr "" -#: ../../content/applications/general/users/companies.rst:107 -msgid "*Example:* an invoice posted on JS Store Belgium, for JS Store US, automatically creates a vendor bill on the JS Store US, from the JS Store Belgium." +#: ../../content/applications/general/users/azure.rst:147 +msgid "User experience flows" msgstr "" -#: ../../content/applications/general/users/companies.rst:-1 -msgid "View of an invoice for JS Store US created on JS Store Belgium in Odoo" +#: ../../content/applications/general/users/azure.rst:149 +msgid "For a user to log in to Odoo using Microsoft Azure, the user must be on the :menuselection:`Odoo password reset page`. This is the only way that Odoo is able to link the Microsoft Azure account and allow the user to log in." msgstr "" -#: ../../content/applications/general/users/companies.rst:114 -msgid "**Synchronize sales/purchase order**: generates a drafted purchase/sales order using the selected company warehouse when a sales/purchase order is confirmed for the selected company. If instead of a drafted purchase/sales order you rather have it validated, enable *Automatic Validation*." +#: ../../content/applications/general/users/azure.rst:154 +msgid "Existing users must :ref:`reset their password ` to access the :menuselection:`Odoo password reset page`. New Odoo users must click the new user invitation link that was sent via email, then click on :guilabel:`Microsoft Azure`. Users should not set a new password." msgstr "" -#: ../../content/applications/general/users/companies.rst:118 -msgid "*Example:* when a sale order for JS Store US is confirmed on JS Store Belgium, a purchase order on JS Store Belgium is automatically created (and confirmed if the *Automatic Validation* feature was enabled)." +#: ../../content/applications/general/users/azure.rst:159 +msgid "To sign in to Odoo for the first time using the Microsoft Azure OAuth provider, navigate to the :menuselection:`Odoo password reset page` (using the new user invitation link). A password reset page should appear. Then, click on the option labeled :guilabel:`Microsoft Azure`. The page will redirect to the Microsoft login page." msgstr "" -#: ../../content/applications/general/users/companies.rst:-1 -msgid "View of the purchase created on JS Store US from JS Store Belgium in Odoo" +#: ../../content/applications/general/users/azure.rst:-1 +msgid "Microsoft Outlook login page." msgstr "" -#: ../../content/applications/general/users/companies.rst:127 -msgid "Products have to be configured as *Can be sold* and must be shared between the companies." +#: ../../content/applications/general/users/azure.rst:168 +msgid "Enter the :guilabel:`Microsoft Email Address` and click :guilabel:`Next`. Follow the process to sign in to the account. Should :abbr:`2FA (Two Factor Authentication)` be turned on, then an extra step may be required." msgstr "" -#: ../../content/applications/general/users/companies.rst:130 -msgid "Remember to test all workflows as an user other than the administrator." +#: ../../content/applications/general/users/azure.rst:-1 +msgid "Enter Microsoft login credentials." msgstr "" -#: ../../content/applications/general/users/companies.rst:133 -msgid ":doc:`Multi-company Guidelines `" +#: ../../content/applications/general/users/azure.rst:176 +msgid "Finally, after logging in to the account, the page will redirect to a permissions page where the user will be prompted to :guilabel:`Accept` the conditions that the Odoo application will access their Microsoft information." msgstr "" -#: ../../content/applications/general/users/companies.rst:134 -msgid ":doc:`../../finance/accounting/get_started/multi_currency`" +#: ../../content/applications/general/users/azure.rst:-1 +msgid "Accept Microsoft conditions for permission access to your account information." +msgstr "" + +#: ../../content/applications/general/users/google.rst:3 +msgid "Google Sign-In Authentication" +msgstr "" + +#: ../../content/applications/general/users/google.rst:5 +msgid "The *Google Sign-In Authentication* is a useful function that allows Odoo users to sign in to their database with their Google account." +msgstr "" + +#: ../../content/applications/general/users/google.rst:8 +msgid "This is particularly helpful if the organization uses Google Workspace, and wants employees within the organization to connect to Odoo using their Google Accounts." +msgstr "" + +#: ../../content/applications/general/users/google.rst:12 +msgid "Databases hosted on Odoo.com should not use Oauth login for the owner or administrator of the database as it would unlink the database from their Odoo.com account. If Oauth is set up for that user, the database will no longer be able to be duplicated, renamed or otherwise managed from the Odoo.com portal." +msgstr "" + +#: ../../content/applications/general/users/google.rst:19 +msgid ":doc:`../email_communication/google_oauth`" +msgstr "" + +#: ../../content/applications/general/users/google.rst:26 +msgid "The integration of the Google sign-in function requires configuration both on Google *and* Odoo." +msgstr "" + +#: ../../content/applications/general/users/google.rst:31 +msgid "Google API Dashboard" +msgstr "" + +#: ../../content/applications/general/users/google.rst:33 +msgid "Go to the `Google API Dashboard `_." +msgstr "" + +#: ../../content/applications/general/users/google.rst:34 +msgid "Make sure the right project is opened. If there isn't a project yet, click on :guilabel:`Create Project`, fill out the project name and other details of the company, and click on :guilabel:`Create`." +msgstr "" + +#: ../../content/applications/general/users/google.rst:0 +msgid "Filling out the details of a new project." +msgstr "" + +#: ../../content/applications/general/users/google.rst:43 +msgid "Choose the name of the company from the drop-down menu." +msgstr "" + +#: ../../content/applications/general/users/google.rst:50 +msgid "On the left side menu, click on :menuselection:`OAuth consent screen`." +msgstr "" + +#: ../../content/applications/general/users/google.rst:0 +msgid "Google OAuth consent selection menu." +msgstr "" + +#: ../../content/applications/general/users/google.rst:56 +msgid "Choose one of the options (:guilabel:`Internal` / :guilabel:`External`), and click on :guilabel:`Create`." +msgstr "" + +#: ../../content/applications/general/users/google.rst:0 +msgid "Choice of a user type in OAuth consent." +msgstr "" + +#: ../../content/applications/general/users/google.rst:71 +msgid "Fill out the required details and domain info, then click on :guilabel:`Save and Continue`." +msgstr "" + +#: ../../content/applications/general/users/google.rst:72 +msgid "On the :menuselection:`Scopes` page, leave all fields as is, and click on :guilabel:`Save and Continue`." +msgstr "" + +#: ../../content/applications/general/users/google.rst:74 +msgid "Next, if continuing in testing mode (*External*), add the email addresses being configured under the :guilabel:`Test users` step by clicking on :guilabel:`Add Users`, and then the :guilabel:`Save and Continue` button. A summary of the app registration appears." +msgstr "" + +#: ../../content/applications/general/users/google.rst:77 +msgid "Finally, scroll to the bottom, and click on :guilabel:`Back to Dashboard`." +msgstr "" + +#: ../../content/applications/general/users/google.rst:82 +msgid "Credentials" +msgstr "" + +#: ../../content/applications/general/users/google.rst:84 +msgid "On the left side menu, click on :menuselection:`Credentials`." +msgstr "" + +#: ../../content/applications/general/users/google.rst:0 +msgid "Credentials button menu." +msgstr "" + +#: ../../content/applications/general/users/google.rst:90 +msgid "Click on :guilabel:`Create Credentials`, and select :guilabel:`OAuth client ID`." +msgstr "" + +#: ../../content/applications/general/users/google.rst:0 +msgid "OAuth client id selection." +msgstr "" + +#: ../../content/applications/general/users/google.rst:96 +msgid "Select :guilabel:`Web Application` as the :guilabel:`Application Type`. Now, configure the allowed pages on which Odoo will be redirected." +msgstr "" + +#: ../../content/applications/general/users/google.rst:99 +msgid "In order to achieve this, in the :guilabel:`Authorized redirect URIs` field, enter the database's domain immediately followed by `/auth_oauth/signin`. For example: `https://mydomain.odoo.com/auth_oauth/signin`, then click on :guilabel:`Create`." +msgstr "" + +#: ../../content/applications/general/users/google.rst:103 +msgid "Now that the *OAuth client* has been created, a screen will appear with the :guilabel:`Client ID` and :guilabel:`Client Secret`. Copy the :guilabel:`Client ID` for later, as it will be necessary for the configuration in Odoo, which will be covered in the following steps." +msgstr "" + +#: ../../content/applications/general/users/google.rst:110 +msgid "Google Authentication on Odoo" +msgstr "" + +#: ../../content/applications/general/users/google.rst:115 +msgid "Retrieve the Client ID" +msgstr "" + +#: ../../content/applications/general/users/google.rst:117 +msgid "Once the previous steps are complete, two keys are generated on the Google API Dashboard: :guilabel:`Client ID` and :guilabel:`Client Secret`. Copy the :guilabel:`Client ID`." +msgstr "" + +#: ../../content/applications/general/users/google.rst:-1 +msgid "Google OAuth Client ID generated." +msgstr "" + +#: ../../content/applications/general/users/google.rst:127 +msgid "Odoo activation" +msgstr "" + +#: ../../content/applications/general/users/google.rst:129 +msgid "Go to :menuselection:`Odoo General Settings --> Integrations` and activate :guilabel:`OAuth Authentication`." +msgstr "" + +#: ../../content/applications/general/users/google.rst:133 +msgid "Odoo may prompt the user to log-in again after this step." +msgstr "" + +#: ../../content/applications/general/users/google.rst:135 +msgid "Go back to :menuselection:`General Settings --> Integrations --> OAuth Authentication`, activate the selection and :guilabel:`Save`. Next, return to :menuselection:`General Settings --> Integrations --> Google Authentication` and activate the selection. Then fill out the :guilabel:`Client ID` with the key from the Google API Dashboard, and :guilabel:`Save`." +msgstr "" + +#: ../../content/applications/general/users/google.rst:0 +msgid "Filling out the client id in Odoo settings." +msgstr "" + +#: ../../content/applications/general/users/google.rst:145 +msgid "Google OAuth2 configuration can also be accessed by clicking on :guilabel:`OAuth Providers` under the :guilabel:`OAuth Authentication` heading in :menuselection:`Integrations`." +msgstr "" + +#: ../../content/applications/general/users/google.rst:151 +msgid "Log in to Odoo with Google" +msgstr "" + +#: ../../content/applications/general/users/google.rst:153 +msgid "To link the Google account to the Odoo profile, click on :guilabel:`Log in with Google` when first logging into Odoo." +msgstr "" + +#: ../../content/applications/general/users/google.rst:0 +msgid "Reset password screen with \"Log in with Google\" button." +msgstr "" + +#: ../../content/applications/general/users/google.rst:161 +msgid "Existing users must :ref:`reset their password ` to access the :menuselection:`Reset Password` page, while new users can directly click on :guilabel:`Log in with Google`, instead of choosing a new password." +msgstr "" + +#: ../../content/applications/general/users/google.rst:166 +msgid "`Google Cloud Platform Console Help - Setting up OAuth 2.0 `_" msgstr "" #: ../../content/applications/general/users/language.rst:3 @@ -3678,261 +6323,76 @@ msgstr "" msgid ":doc:`../../websites/website/configuration/translate`" msgstr "" -#: ../../content/applications/general/users/manage_users.rst:3 -msgid "Manage users" +#: ../../content/applications/general/users/ldap.rst:3 +msgid "Sign in with LDAP" msgstr "" -#: ../../content/applications/general/users/manage_users.rst:5 -msgid "Odoo defines a **user** as someone who has access to a database to perform daily tasks. You can add as many users as you need and, in order to restrict the type of information each user can access, rules can be applied. Users and access rights can be added and changed at any point." +#: ../../content/applications/general/users/ldap.rst:5 +msgid "Install the Lightweight Directory Access Protocol (LDAP) module in General Settings." msgstr "" -#: ../../content/applications/general/users/manage_users.rst:10 -msgid ":doc:`language`" +#: ../../content/applications/general/users/ldap.rst:7 +msgid "Click on **Create** in Setup the :abbr:`LDAP (Lightweight Directory Access Protocol)` Server." msgstr "" -#: ../../content/applications/general/users/manage_users.rst:11 -msgid ":doc:`access_rights`" +#: ../../content/applications/general/users/ldap.rst:-1 +msgid "LDAP Authentication checkbox highlighted in the integrations settings on Odoo." msgstr "" -#: ../../content/applications/general/users/manage_users.rst:16 -msgid "Add individual users" +#: ../../content/applications/general/users/ldap.rst:-1 +msgid "Create highlighted in the LDAP server settings." msgstr "" -#: ../../content/applications/general/users/manage_users.rst:18 -msgid "Go to :menuselection:`Settings --> Manage Users` and click on *Create*." +#: ../../content/applications/general/users/ldap.rst:17 +msgid "Choose the company using the LDAP." msgstr "" -#: ../../content/applications/general/users/manage_users.rst:-1 -msgid "View of the settings page emphasizing the manage users field in Odoo" +#: ../../content/applications/general/users/ldap.rst:-1 +msgid "Select the company drop-down menu highlighted in LDAP setup." msgstr "" -#: ../../content/applications/general/users/manage_users.rst:27 -msgid "Fill in the form with the needed information. Under the tab :doc:`Access Rights ` choose the group within each application the user can have access to." +#: ../../content/applications/general/users/ldap.rst:23 +msgid "In **Server Information**, enter the IP address of the server and the port it listens to." msgstr "" -#: ../../content/applications/general/users/manage_users.rst:28 -msgid "The list of applications shown is based on the applications installed on the database." +#: ../../content/applications/general/users/ldap.rst:25 +msgid "Tick **Use TLS** if the server is compatible." msgstr "" -#: ../../content/applications/general/users/manage_users.rst:-1 -msgid "View of a user’s form emphasizing the access rights tab in Odoo" +#: ../../content/applications/general/users/ldap.rst:-1 +msgid "LDAP server settings highlighted in LDAP server setup on Odoo." msgstr "" -#: ../../content/applications/general/users/manage_users.rst:34 -msgid "When you are done editing the page and have *Saved* it, an invitation email is automatically sent to the user. The user must click on it to accept the invitation and create a login." +#: ../../content/applications/general/users/ldap.rst:31 +msgid "In **Login Information**, enter ID and password of the account used to query the server. If left empty, the server queries anonymously." msgstr "" -#: ../../content/applications/general/users/manage_users.rst:-1 -msgid "View of a user’s form with a notification that the invitation email has been sent in Odoo" +#: ../../content/applications/general/users/ldap.rst:-1 +msgid "Login information highlighted in LDAP server setup on Odoo." msgstr "" -#: ../../content/applications/general/users/manage_users.rst:42 -msgid "Remember that subscription prices follow the number of users. Refer to our `pricing page `_ for more information." +#: ../../content/applications/general/users/ldap.rst:38 +msgid "In **Process Parameter**, enter the domain name of the LDAP server in :abbr:`LDAP (Lightweight Directory Access Protocol)` nomenclature (e.g. ``dc=example,dc=com``)." msgstr "" -#: ../../content/applications/general/users/manage_users.rst:46 -msgid "With the :ref:`developer mode ` activated, *User Types* can be selected." +#: ../../content/applications/general/users/ldap.rst:41 +msgid "In **LDAP filter**, enter ``uid=%s``" msgstr "" -#: ../../content/applications/general/users/manage_users.rst:-1 -msgid "View of a user’s form in developer mode emphasizing the user type field in Odoo" +#: ../../content/applications/general/users/ldap.rst:-1 +msgid "Process parameter highlighted in LDAP server setup on Odoo." msgstr "" -#: ../../content/applications/general/users/manage_users.rst:53 -msgid "The *Portal* and *Public* options do not allow you to choose access rights. Members have specific ones (such as record rules and restricted menus) and usually do not belong to the usual Odoo groups." +#: ../../content/applications/general/users/ldap.rst:47 +msgid "In **User Information**, tick *Create User* if Odoo should create a User profile the first time someone logs in with :abbr:`LDAP (Lightweight Directory Access Protocol)`." msgstr "" -#: ../../content/applications/general/users/manage_users.rst:60 -msgid "Deactivate users" +#: ../../content/applications/general/users/ldap.rst:50 +msgid "In **Template User**, indicate a template for the new profiles created. If left blanked, the admin profile will be used as template." msgstr "" -#: ../../content/applications/general/users/manage_users.rst:62 -msgid "Go to :menuselection:`Settings --> Users & Companies --> Users`, open the user you want to deactivate, click on *Action*, and then on *Archive*." -msgstr "" - -#: ../../content/applications/general/users/manage_users.rst:66 -msgid "**Never** deactivate the main user (*admin*)." -msgstr "" - -#: ../../content/applications/general/users/manage_users.rst:71 -msgid "Passwords management" -msgstr "" - -#: ../../content/applications/general/users/manage_users.rst:76 -msgid "Reset passwords" -msgstr "" - -#: ../../content/applications/general/users/manage_users.rst:81 -msgid "Enable password resets from login page" -msgstr "" - -#: ../../content/applications/general/users/manage_users.rst:83 -msgid "It is possible to enable password resets directly from the login page." -msgstr "" - -#: ../../content/applications/general/users/manage_users.rst:85 -msgid "To do so, go to :menuselection:`Settings --> Permissions`, activate **Password Reset** and *Save*." -msgstr "" - -#: ../../content/applications/general/users/manage_users.rst:-1 -msgid "Enabling Password Reset in Odoo Settings" -msgstr "" - -#: ../../content/applications/general/users/manage_users.rst:94 -msgid "Send reset instructions to users" -msgstr "" - -#: ../../content/applications/general/users/manage_users.rst:96 -msgid "Go to :menuselection:`Settings --> Users & Companies --> Users`, select the user out of the list and click on *Send Password Reset Instructions* on its user form. An email is automatically sent to them." -msgstr "" - -#: ../../content/applications/general/users/manage_users.rst:101 -msgid "The *Send Password Reset Instructions* button only appears if the Odoo invitation email has already been confirmed by the user." -msgstr "" - -#: ../../content/applications/general/users/manage_users.rst:104 -msgid "This email contains all the instructions needed to reset the password, along with a link redirecting the user to an Odoo login page." -msgstr "" - -#: ../../content/applications/general/users/manage_users.rst:-1 -msgid "Example of an email with a password reset link for an Odoo account" -msgstr "" - -#: ../../content/applications/general/users/manage_users.rst:114 -msgid "Change users’ passwords" -msgstr "" - -#: ../../content/applications/general/users/manage_users.rst:116 -msgid "Go to :menuselection:`Settings --> Users & Companies --> Users` and select a user to access its form. Click on the *Action* button and select *Change Password*." -msgstr "" - -#: ../../content/applications/general/users/manage_users.rst:-1 -msgid "Change another user's password on Odoo" -msgstr "" - -#: ../../content/applications/general/users/manage_users.rst:123 -msgid "Enter a new password and confirm by clicking on *Change Password*." -msgstr "" - -#: ../../content/applications/general/users/manage_users.rst:126 -msgid "This operation only modifies the password of the users locally and does not affect their odoo.com account. If you want to change the odoo.com password, you can :ref:`send the password reset instructions `." -msgstr "" - -#: ../../content/applications/general/users/manage_users.rst:130 -msgid "Click on *Change Password* one more time. You are then redirected to an Odoo login page where you can reaccess your database using your new password." -msgstr "" - -#: ../../content/applications/general/users/manage_users.rst:136 -msgid "Multi Companies" -msgstr "" - -#: ../../content/applications/general/users/manage_users.rst:138 -msgid "The *Multi Companies* field allows you to set to which of the multiple companies database you hold the user can have access." -msgstr "" - -#: ../../content/applications/general/users/manage_users.rst:142 -msgid "Note that if not handled correctly, it may be the source of a lot of inconsistent multi-company behaviors. Therefore, a good knowledge of Odoo is required. For technical explanations refer to :doc:`this ` documentation." -msgstr "" - -#: ../../content/applications/general/users/manage_users.rst:-1 -msgid "View of a user’s form emphasizing the multi companies field in Odoo" -msgstr "" - -#: ../../content/applications/general/users/manage_users.rst:152 -msgid ":doc:`companies`" -msgstr "" - -#: ../../content/applications/general/users/odoo_account.rst:3 -msgid "Odoo.com account changes" -msgstr "" - -#: ../../content/applications/general/users/odoo_account.rst:5 -msgid "This documentation is dedicated to edits made to an Odoo.com account. The following processes describe how to delete an Odoo.com account, and how to change the password on an Odoo.com account." -msgstr "" - -#: ../../content/applications/general/users/odoo_account.rst:9 -msgid "Delete Odoo.com account" -msgstr "" - -#: ../../content/applications/general/users/odoo_account.rst:11 -msgid "To delete an Odoo.com account, start by clicking the profile icon in the upper-right corner (represented by the username and icon) to reveal a drop-down menu. From the drop-down menu, select :guilabel:`My Odoo.com account`, which reveals the user portal." -msgstr "" - -#: ../../content/applications/general/users/odoo_account.rst:15 -msgid "From the user portal, the delete option can be accessed by going to :menuselection:`My Account --> Edit Security Settings --> Delete Account`. It can also be accessed by going to `https://www.odoo.com/my/home `_." -msgstr "" - -#: ../../content/applications/general/users/odoo_account.rst:20 -msgid "Deleting an Odoo account is irreversible. Be careful performing this action, as the Odoo.com account is **not** retrievable once deleted." -msgstr "" - -#: ../../content/applications/general/users/odoo_account.rst:23 -msgid "Upon clicking the :guilabel:`Delete Account` button, a pop-up window appears, requesting confirmation for the account deletion." -msgstr "" - -#: ../../content/applications/general/users/odoo_account.rst:-1 -msgid "Clicking on the Delete Account button will populate a window verifying the change." -msgstr "" - -#: ../../content/applications/general/users/odoo_account.rst:30 -msgid "To confirm the deletion, enter the :guilabel:`Password` and the :guilabel:`Login` for the account being deleted. Then, click the :guilabel:`Delete Account` button to confirm the deletion." -msgstr "" - -#: ../../content/applications/general/users/odoo_account.rst:34 -msgid "Odoo.com account password change" -msgstr "" - -#: ../../content/applications/general/users/odoo_account.rst:36 -msgid "To change an Odoo.com account password, first login into the Odoo.com user account from the Odoo.com login page. After logging-in, go to the upper-right corner of the screen, and click the :guilabel:`▼ (down arrow)` icon next to the profile icon. Then, select :guilabel:`My Account`, and a portal dashboard appears." -msgstr "" - -#: ../../content/applications/general/users/odoo_account.rst:41 -msgid "To change the Odoo.com password, click on the :guilabel:`Edit Security Settings` link, below the :menuselection:`Account Security` section. Next, make the necessary changes by typing in the current :guilabel:`Password`, :guilabel:`New Password`, and verify the new password. Lastly, click on :guilabel:`Change Password` to complete the password change." -msgstr "" - -#: ../../content/applications/general/users/odoo_account.rst:47 -msgid "If a customer would like to change the login, contact Odoo support `here `_." -msgstr "" - -#: ../../content/applications/general/users/odoo_account.rst:51 -msgid "Passwords for Odoo.com users and portal users remain separate, even if the same email address is used." -msgstr "" - -#: ../../content/applications/general/users/odoo_account.rst:55 -#: ../../content/applications/general/users/portal.rst:143 -msgid "Add two-factor authentication" -msgstr "" - -#: ../../content/applications/general/users/odoo_account.rst:57 -msgid "To add two-factor authentication, login into the Odoo.com user account from the Odoo.com login page. After logging-in, go to the upper-right corner of the screen, and click the :guilabel:`▼ (down arrow)` icon next to the :guilabel:`profile icon`. Then, select :guilabel:`My Account`, and a portal dashboard appears." -msgstr "" - -#: ../../content/applications/general/users/odoo_account.rst:62 -msgid "If the user would like to turn on two-factor authentication (2FA) for Odoo.com access, click on the :guilabel:`Edit Security Settings` link below the :menuselection:`Account Security` section." -msgstr "" - -#: ../../content/applications/general/users/odoo_account.rst:65 -msgid "Click on :guilabel:`Enable two-factor authentication` to turn on :abbr:`2FA (two-factor authentication)`. Then, confirm the current password in the :guilabel:`Password` field. Next, click on :guilabel:`Confirm Password`. Following that, activate :abbr:`2FA (two-factor authentication)` in a :abbr:`2FA (two-factor authentication)` app (Google Authenticator, Authy, etc.), by scanning the :guilabel:`QR code` or entering a :guilabel:`Verification Code`." -msgstr "" - -#: ../../content/applications/general/users/odoo_account.rst:71 -msgid "Finally, click on :guilabel:`Enable two-factor authentication` to complete the setup." -msgstr "" - -#: ../../content/applications/general/users/odoo_account.rst:74 -msgid "Under :guilabel:`My Account` Odoo.com users can also access the following:" -msgstr "" - -#: ../../content/applications/general/users/odoo_account.rst:76 -msgid ":guilabel:`My Partner dashboard`" -msgstr "" - -#: ../../content/applications/general/users/odoo_account.rst:77 -msgid ":guilabel:`My In-App Services`" -msgstr "" - -#: ../../content/applications/general/users/odoo_account.rst:78 -msgid ":guilabel:`My Apps Dashboard`" +#: ../../content/applications/general/users/ldap.rst:-1 +msgid "User information highlighted on LDAP server setup on Odoo." msgstr "" #: ../../content/applications/general/users/portal.rst:3 @@ -4114,6 +6574,10 @@ msgstr "" msgid "Passwords for portal users and Odoo.com users remain separate, even if the same email address is used." msgstr "" +#: ../../content/applications/general/users/portal.rst:143 +msgid "Add two-factor authentication" +msgstr "" + #: ../../content/applications/general/users/portal.rst:148 msgid "If the customer would like to turn on two-factor authentication (2FA) for portal access, click on the :guilabel:`Edit Security Settings` link, below the :guilabel:`Account Security` section." msgstr "" @@ -4133,3070 +6597,3 @@ msgstr "" #: ../../content/applications/general/users/portal.rst:165 msgid "If the customer would like to manage payment options, navigate to the :guilabel:`Manage payment methods` in the menu on the right. Then, add the new payment information, and select :guilabel:`Add new card`." msgstr "" - -#: ../../content/applications/general/voip.rst:7 -msgid "VoIP (Voice over Internet Protocol)" -msgstr "" - -#: ../../content/applications/general/voip.rst:10 -msgid "For more information, reference the `Odoo eLearning (video tutorials) on VoIP `_" -msgstr "" - -#: ../../content/applications/general/voip/axivox.rst:5 -msgid "Axivox configuration" -msgstr "" - -#: ../../content/applications/general/voip/axivox/axivox_config.rst:3 -msgid "VoIP services in Odoo with Axivox" -msgstr "" - -#: ../../content/applications/general/voip/axivox/axivox_config.rst:6 -#: ../../content/applications/general/voip/onsip.rst:6 -msgid "Introduction" -msgstr "" - -#: ../../content/applications/general/voip/axivox/axivox_config.rst:8 -msgid "Odoo VoIP (Voice over Internet Protocol) can be set up to work together with `Axivox `_. In that case, an Asterisk server is **not** necessary, as the infrastructure is hosted and managed by Axivox." -msgstr "" - -#: ../../content/applications/general/voip/axivox/axivox_config.rst:12 -msgid "To use this service, `contact Axivox `_ to open an account. Before doing so, verify that Axivox covers the company's area, along with the areas the company's users wish to call." -msgstr "" - -#: ../../content/applications/general/voip/axivox/axivox_config.rst:19 -msgid "To configure Axivox in Odoo, go to the :menuselection:`Apps` application, and search for `VoIP`. Then, install the :guilabel:`VoIP` module." -msgstr "" - -#: ../../content/applications/general/voip/axivox/axivox_config.rst:22 -msgid "Next, go to :menuselection:`Settings app --> General Settings --> Integrations section`, and fill out the :guilabel:`Asterisk (VoIP)` field:" -msgstr "" - -#: ../../content/applications/general/voip/axivox/axivox_config.rst:25 -msgid ":guilabel:`OnSIP Domain`: set the domain created by Axivox for the account (e.g., `yourcompany.axivox.com`)" -msgstr "" - -#: ../../content/applications/general/voip/axivox/axivox_config.rst:27 -msgid ":guilabel:`WebSocket`: type in `wss://pabx.axivox.com:3443`" -msgstr "" - -#: ../../content/applications/general/voip/axivox/axivox_config.rst:28 -msgid ":guilabel:`VoIP Environment`: set as :guilabel:`Production`" -msgstr "" - -#: ../../content/applications/general/voip/axivox/axivox_config.rst:-1 -msgid "Integration of Axivox as VoIP provider in an Odoo database." -msgstr "" - -#: ../../content/applications/general/voip/axivox/axivox_config.rst:35 -msgid "Access the domain on the Axivox administrative panel by navigating to `https://manage.axivox.com/ `_. After logging into the portal, go to :menuselection:`Users --> Edit (next to any user) --> SIP Identifiers tab --> Domain`." -msgstr "" - -#: ../../content/applications/general/voip/axivox/axivox_config.rst:40 -msgid "Configure VoIP user in Odoo" -msgstr "" - -#: ../../content/applications/general/voip/axivox/axivox_config.rst:42 -msgid "Next, the user is configured in Odoo, which **must** take place for every Axivox/Odoo user using VoIP." -msgstr "" - -#: ../../content/applications/general/voip/axivox/axivox_config.rst:45 -msgid "In Odoo, go to :menuselection:`Settings app --> Users & Companies --> Users`, then open the desired user's form to configure :abbr:`VoIP (Voice over Internet Protocol)`. Under the :guilabel:`Preferences` tab, fill out the :guilabel:`VOIP Configuration` section:" -msgstr "" - -#: ../../content/applications/general/voip/axivox/axivox_config.rst:49 -msgid ":guilabel:`VoIP username` / :guilabel:`Extension number`: (Axivox) :guilabel:`SIP username`" -msgstr "" - -#: ../../content/applications/general/voip/axivox/axivox_config.rst:50 -msgid ":guilabel:`OnSip Auth Username`: (Axivox) :guilabel:`SIP username`" -msgstr "" - -#: ../../content/applications/general/voip/axivox/axivox_config.rst:51 -msgid ":guilabel:`VoIP Secret`: (Axivox) :guilabel:`SIP Password`" -msgstr "" - -#: ../../content/applications/general/voip/axivox/axivox_config.rst:52 -msgid ":guilabel:`Call from another device`: option to always transfer phone calls to handset" -msgstr "" - -#: ../../content/applications/general/voip/axivox/axivox_config.rst:53 -msgid ":guilabel:`External device number`: SIP external phone extension" -msgstr "" - -#: ../../content/applications/general/voip/axivox/axivox_config.rst:54 -msgid ":guilabel:`Reject incoming calls`: option to reject all incoming calls" -msgstr "" - -#: ../../content/applications/general/voip/axivox/axivox_config.rst:55 -msgid ":guilabel:`How to place calls on mobile`: method to make calls on a mobile device" -msgstr "" - -#: ../../content/applications/general/voip/axivox/axivox_config.rst:-1 -msgid "Integration of Axivox user in the Odoo user preference." -msgstr "" - -#: ../../content/applications/general/voip/axivox/axivox_config.rst:62 -msgid "Access the domain on the Axivox administrative panel by navigating to `https://manage.axivox.com/ `_. After logging into the portal, go to :menuselection:`Users --> Edit (next to the user) --> SIP Identifiers tab --> SIP username / SIP password`." -msgstr "" - -#: ../../content/applications/general/voip/axivox/axivox_config.rst:0 -msgid "SIP credentials in the Axivox manager." -msgstr "" - -#: ../../content/applications/general/voip/axivox/axivox_config.rst:71 -msgid "When entering the :guilabel:`SIP Password` into the user's :guilabel:`Preferences` tab, this value **must** be typed out manually and **not** pasted in. Pasting in causes a `401 server rejection error`." -msgstr "" - -#: ../../content/applications/general/voip/axivox/call_queues.rst:3 -msgid "Call queues" -msgstr "" - -#: ../../content/applications/general/voip/axivox/call_queues.rst:5 -msgid "A call queue is a system that organizes and routes incoming calls. When customers call a business, and all of the agents are busy, the call queue lines up the callers in sequential order, based on the time they called in." -msgstr "" - -#: ../../content/applications/general/voip/axivox/call_queues.rst:9 -msgid "The callers then wait on hold to be connected to the next available call center agent." -msgstr "" - -#: ../../content/applications/general/voip/axivox/call_queues.rst:11 -msgid "Implementing a call queue system reduces stress for employees, and helps build brand trust with customers. Many companies use call queues to set expectations with customers, and to distribute the workload equally amongst employees." -msgstr "" - -#: ../../content/applications/general/voip/axivox/call_queues.rst:15 -msgid "This document covers the process required to configure call queues (with advanced settings), as well as how to log into a call queue from the Odoo database." -msgstr "" - -#: ../../content/applications/general/voip/axivox/call_queues.rst:19 -msgid ":ref:`voip/axivox/music_on_hold`" -msgstr "" - -#: ../../content/applications/general/voip/axivox/call_queues.rst:22 -msgid "Add a queue" -msgstr "" - -#: ../../content/applications/general/voip/axivox/call_queues.rst:24 -msgid "To add a call queue in Axivox, navigate to the `Axivox management console `_. In the left menu, click :guilabel:`Queues`. Next, click :guilabel:`Add a queue`. Doing so reveals a blank :guilabel:`New queue` form with various fields to fill out." -msgstr "" - -#: ../../content/applications/general/voip/axivox/call_queues.rst:30 -msgid "Name" -msgstr "" - -#: ../../content/applications/general/voip/axivox/call_queues.rst:32 -msgid "Once the :guilabel:`New queue` page appears, enter the :guilabel:`Name` of the queue." -msgstr "" - -#: ../../content/applications/general/voip/axivox/call_queues.rst:35 -msgid "Internal extension" -msgstr "" - -#: ../../content/applications/general/voip/axivox/call_queues.rst:37 -msgid "Choose an :guilabel:`Internal extension` for the queue. This is a number to be dialed by users of the database to reach the login prompt for the queue." -msgstr "" - -#: ../../content/applications/general/voip/axivox/call_queues.rst:41 -msgid "Strategy" -msgstr "" - -#: ../../content/applications/general/voip/axivox/call_queues.rst:43 -msgid "Next, is the :guilabel:`Strategy` field. This field determines the call routing of received calls into this queue." -msgstr "" - -#: ../../content/applications/general/voip/axivox/call_queues.rst:46 -msgid "The following choices are available in the :guilabel:`Strategy` drop-down menu:" -msgstr "" - -#: ../../content/applications/general/voip/axivox/call_queues.rst:48 -msgid ":guilabel:`Call all available agents`" -msgstr "" - -#: ../../content/applications/general/voip/axivox/call_queues.rst:49 -msgid ":guilabel:`Calls the agent who has received the call for the longest time`" -msgstr "" - -#: ../../content/applications/general/voip/axivox/call_queues.rst:50 -msgid ":guilabel:`Calls the agent who has received the least call`" -msgstr "" - -#: ../../content/applications/general/voip/axivox/call_queues.rst:51 -msgid ":guilabel:`Call a random agent`" -msgstr "" - -#: ../../content/applications/general/voip/axivox/call_queues.rst:52 -msgid ":guilabel:`Call agents one after the other`" -msgstr "" - -#: ../../content/applications/general/voip/axivox/call_queues.rst:53 -msgid ":guilabel:`Call agents one after the other starting with the first in the list`" -msgstr "" - -#: ../../content/applications/general/voip/axivox/call_queues.rst:55 -msgid "Choose a strategy that best meets the company's needs for customers in the queue." -msgstr "" - -#: ../../content/applications/general/voip/axivox/call_queues.rst:58 -msgid "Maximum waiting time in seconds" -msgstr "" - -#: ../../content/applications/general/voip/axivox/call_queues.rst:60 -msgid "In the :guilabel:`Maximum waiting time in seconds` field, determine the longest time a customer waits in the queue before going to a voicemail, or wherever else they are directed to in a dial plan. Enter a time in seconds." -msgstr "" - -#: ../../content/applications/general/voip/axivox/call_queues.rst:65 -msgid "Maximum duration of ringing at an agent" -msgstr "" - -#: ../../content/applications/general/voip/axivox/call_queues.rst:67 -msgid "In the :guilabel:`Maximum duration of ringing at an agent` field, determine the longest time an individual agent's line rings before moving on to another agent, or moving to the next step in the dial plan. Enter a time in seconds." -msgstr "" - -#: ../../content/applications/general/voip/axivox/call_queues.rst:72 -msgid "For more information on dial plans, visit:" -msgstr "" - -#: ../../content/applications/general/voip/axivox/call_queues.rst:74 -#: ../../content/applications/general/voip/axivox/dynamic_caller_id.rst:36 -msgid ":doc:`dial_plan_basics`" -msgstr "" - -#: ../../content/applications/general/voip/axivox/call_queues.rst:75 -#: ../../content/applications/general/voip/axivox/dynamic_caller_id.rst:37 -msgid ":doc:`dial_plan_advanced`" -msgstr "" - -#: ../../content/applications/general/voip/axivox/call_queues.rst:78 -msgid "Adding agents" -msgstr "" - -#: ../../content/applications/general/voip/axivox/call_queues.rst:80 -msgid "The final two fields on the :guilabel:`New queue` form revolve around adding agents. Adding :guilabel:`Static agents` and :guilabel:`Dynamic agents` are two pre-configured methods for adding agents onto the call queue during the configuration." -msgstr "" - -#: ../../content/applications/general/voip/axivox/call_queues.rst:87 -msgid "Static agents" -msgstr "" - -#: ../../content/applications/general/voip/axivox/call_queues.rst:89 -msgid "When :guilabel:`Static agents` are added, these agents are automatically added to the queue without the need to log in to receive calls." -msgstr "" - -#: ../../content/applications/general/voip/axivox/call_queues.rst:95 -msgid "Dynamic agents" -msgstr "" - -#: ../../content/applications/general/voip/axivox/call_queues.rst:97 -msgid "When :guilabel:`Dynamic agents` are added, these agents have the ability to log into this queue. They are **not** logged-in automatically, and **must** log in to receive calls." -msgstr "" - -#: ../../content/applications/general/voip/axivox/call_queues.rst:100 -msgid "Be sure to :guilabel:`Save` the changes, and click :guilabel:`Apply changes` in the upper-right corner to implement the change in production." -msgstr "" - -#: ../../content/applications/general/voip/axivox/call_queues.rst:104 -msgid "Agent connection" -msgstr "" - -#: ../../content/applications/general/voip/axivox/call_queues.rst:106 -msgid "There are three ways call agents can connect to an Axivox call queue:" -msgstr "" - -#: ../../content/applications/general/voip/axivox/call_queues.rst:108 -msgid "Dynamic agents connect automatically." -msgstr "" - -#: ../../content/applications/general/voip/axivox/call_queues.rst:109 -msgid "Manager logs in specific agent(s), via the `Axivox management console `_." -msgstr "" - -#: ../../content/applications/general/voip/axivox/call_queues.rst:111 -msgid "Agent connects to the queue in Odoo, via the *VoIP* widget." -msgstr "" - -#: ../../content/applications/general/voip/axivox/call_queues.rst:114 -msgid "See the documentation on setting :ref:`voip/axivox/dynamic-agents` in the `Axivox management console `_." -msgstr "" - -#: ../../content/applications/general/voip/axivox/call_queues.rst:118 -msgid "Connect via Axivox queue" -msgstr "" - -#: ../../content/applications/general/voip/axivox/call_queues.rst:120 -msgid "After the initial configuration of the call queue is completed, with the changes saved and implemented, a manager can log into the `Axivox management console `_ and connect dynamic agents to the queue manually." -msgstr "" - -#: ../../content/applications/general/voip/axivox/call_queues.rst:124 -msgid "To connect an agent, click :guilabel:`Queues`, located in the left-hand column. Doing so reveals the :guilabel:`Queues` dashboard, with a few different columns listed:" -msgstr "" - -#: ../../content/applications/general/voip/axivox/call_queues.rst:127 -msgid ":guilabel:`Name`: name of the queue." -msgstr "" - -#: ../../content/applications/general/voip/axivox/call_queues.rst:128 -msgid ":guilabel:`Extension`: number of the extension to be dialed to reach the queue." -msgstr "" - -#: ../../content/applications/general/voip/axivox/call_queues.rst:129 -msgid ":guilabel:`Agent Connection`: number to dial to log into the queue." -msgstr "" - -#: ../../content/applications/general/voip/axivox/call_queues.rst:130 -msgid ":guilabel:`Agent disconnection`: number to dial to log out of the queue." -msgstr "" - -#: ../../content/applications/general/voip/axivox/call_queues.rst:131 -msgid ":guilabel:`Connected Agents`: name of agent connected to the queue." -msgstr "" - -#: ../../content/applications/general/voip/axivox/call_queues.rst:133 -msgid "The following buttons are also available on the :guilabel:`Queues` dashboard:" -msgstr "" - -#: ../../content/applications/general/voip/axivox/call_queues.rst:135 -msgid ":guilabel:`Connect an agent`: manually connect an agent to the queue." -msgstr "" - -#: ../../content/applications/general/voip/axivox/call_queues.rst:136 -msgid ":guilabel:`Report`: run a report on the queue." -msgstr "" - -#: ../../content/applications/general/voip/axivox/call_queues.rst:137 -msgid ":guilabel:`Delete`: delete the queue." -msgstr "" - -#: ../../content/applications/general/voip/axivox/call_queues.rst:138 -msgid ":guilabel:`Edit`: make changes to the settings of the queue." -msgstr "" - -#: ../../content/applications/general/voip/axivox/call_queues.rst:140 -msgid "When agents are connected to the queue, or are live with a customer, they are displayed under the :guilabel:`Connected Agents` column." -msgstr "" - -#: ../../content/applications/general/voip/axivox/call_queues.rst:143 -msgid "If they are static agents, they **always** show up as connected." -msgstr "" - -#: ../../content/applications/general/voip/axivox/call_queues.rst:145 -msgid "Connect an agent by clicking the orange button labeled, :guilabel:`Connect an agent`. Then, select the desired agent's name from the drop-down menu, and click :guilabel:`Connect`." -msgstr "" - -#: ../../content/applications/general/voip/axivox/call_queues.rst:-1 -msgid "Call queue with connected agents column highlighted and connect an agent and report buttons\n" -"highlighted." -msgstr "" - -#: ../../content/applications/general/voip/axivox/call_queues.rst:154 -msgid "For more information on static and dynamic agents, see this documentation:" -msgstr "" - -#: ../../content/applications/general/voip/axivox/call_queues.rst:156 -msgid ":ref:`voip/axivox/static-agents`" -msgstr "" - -#: ../../content/applications/general/voip/axivox/call_queues.rst:157 -msgid ":ref:`voip/axivox/dynamic-agents`" -msgstr "" - -#: ../../content/applications/general/voip/axivox/call_queues.rst:160 -msgid "Report" -msgstr "" - -#: ../../content/applications/general/voip/axivox/call_queues.rst:162 -msgid "Click :guilabel:`Report` to check on the reporting for a particular queue, in order to see who connected when, and what phone calls came in and out of the queue. This information is showcased on a separate :guilabel:`Queue report` page, when the green :guilabel:`Report` button is clicked." -msgstr "" - -#: ../../content/applications/general/voip/axivox/call_queues.rst:166 -msgid "Reports can be customized by date in the :guilabel:`Period` field, and specified in the :guilabel:`From` and :guilabel:`to` fields. The information can be organized by :guilabel:`Event type`, and :guilabel:`Call ID`." -msgstr "" - -#: ../../content/applications/general/voip/axivox/call_queues.rst:170 -msgid "When the custom configurations have been entered, click :guilabel:`Apply`." -msgstr "" - -#: ../../content/applications/general/voip/axivox/call_queues.rst:172 -msgid "Each report can be exported to a :abbr:`CSV (comma separated value)` file for further use and analysis, via the :guilabel:`Export to CSV` button." -msgstr "" - -#: ../../content/applications/general/voip/axivox/call_queues.rst:175 -msgid "When the :guilabel:`Event type` field is clicked, a drop-down menu appears with the following options:" -msgstr "" - -#: ../../content/applications/general/voip/axivox/call_queues.rst:178 -msgid ":guilabel:`The caller quit`" -msgstr "" - -#: ../../content/applications/general/voip/axivox/call_queues.rst:179 -msgid ":guilabel:`An agent is connecting`" -msgstr "" - -#: ../../content/applications/general/voip/axivox/call_queues.rst:180 -msgid ":guilabel:`An agent is disconnecting`" -msgstr "" - -#: ../../content/applications/general/voip/axivox/call_queues.rst:181 -msgid ":guilabel:`The call was terminated (agent hangs up)`" -msgstr "" - -#: ../../content/applications/general/voip/axivox/call_queues.rst:182 -msgid ":guilabel:`The call was terminated (caller hangs up)`" -msgstr "" - -#: ../../content/applications/general/voip/axivox/call_queues.rst:183 -msgid ":guilabel:`The caller is connected to an agent.`" -msgstr "" - -#: ../../content/applications/general/voip/axivox/call_queues.rst:184 -msgid ":guilabel:`Someone is entering the queue`" -msgstr "" - -#: ../../content/applications/general/voip/axivox/call_queues.rst:185 -msgid ":guilabel:`The caller exits the queue (no agent is connected)`" -msgstr "" - -#: ../../content/applications/general/voip/axivox/call_queues.rst:186 -msgid ":guilabel:`The caller exits the queue (timeout)`" -msgstr "" - -#: ../../content/applications/general/voip/axivox/call_queues.rst:187 -msgid ":guilabel:`No one is answering`" -msgstr "" - -#: ../../content/applications/general/voip/axivox/call_queues.rst:188 -msgid ":guilabel:`No one is answering, the caller hangs up`" -msgstr "" - -#: ../../content/applications/general/voip/axivox/call_queues.rst:189 -msgid ":guilabel:`Transfer`" -msgstr "" - -#: ../../content/applications/general/voip/axivox/call_queues.rst:190 -msgid ":guilabel:`Blind Transfer`" -msgstr "" - -#: ../../content/applications/general/voip/axivox/call_queues.rst:-1 -msgid "Event types in the Axivox queue reporting feature." -msgstr "" - -#: ../../content/applications/general/voip/axivox/call_queues.rst:196 -msgid "There is no limit to how many options can be selected from the :guilabel:`Event type` drop-down menu." -msgstr "" - -#: ../../content/applications/general/voip/axivox/call_queues.rst:199 -msgid "Clicking :guilabel:`Check all` selects all the available options from the drop-down menu, and clicking :guilabel:`Uncheck all` removes all selections from the drop-down menu." -msgstr "" - -#: ../../content/applications/general/voip/axivox/call_queues.rst:202 -msgid "To select an individual :guilabel:`Event type`, click on the desired option in the drop-down menu." -msgstr "" - -#: ../../content/applications/general/voip/axivox/call_queues.rst:-1 -msgid "Axivox queue report with result, event type, and period highlighted." -msgstr "" - -#: ../../content/applications/general/voip/axivox/call_queues.rst:209 -msgid "Connect to queue on Odoo" -msgstr "" - -#: ../../content/applications/general/voip/axivox/call_queues.rst:211 -msgid "Dynamic agents can connect manually to the Axivox call queue from the Odoo *VoIP* widget, once the *VoIP* app is configured for the individual user in Odoo." -msgstr "" - -#: ../../content/applications/general/voip/axivox/call_queues.rst:215 -msgid ":doc:`axivox_config`" -msgstr "" - -#: ../../content/applications/general/voip/axivox/call_queues.rst:217 -msgid "To access the Odoo *VoIP* widget, click the :guilabel:`☎️ (phone)` icon in the upper-right corner of the screen, from any window within Odoo." -msgstr "" - -#: ../../content/applications/general/voip/axivox/call_queues.rst:221 -msgid "For more information on the Odoo *VoIP* widget, see this documentation: :doc:`../voip_widget`" -msgstr "" - -#: ../../content/applications/general/voip/axivox/call_queues.rst:223 -msgid "For an agent to connect to the call queue, simply dial the :guilabel:`Agent connection` number, and press the green call button :guilabel:`📞 (phone)` icon in the *VoIP* widget. Then, the agent hears a short, two-second message indicating the agent is logged in. The call automatically ends (disconnects)." -msgstr "" - -#: ../../content/applications/general/voip/axivox/call_queues.rst:228 -msgid "To view the connected agents in a call queue, navigate to the `Axivox management console `_, and click :guilabel:`Queues`, located in the left-hand column." -msgstr "" - -#: ../../content/applications/general/voip/axivox/call_queues.rst:231 -msgid "Then, click the green :guilabel:`Refresh` button at the top of the :guilabel:`Connected agents` column. Any agent (static or dynamic) that is connected to the queue currently, appears in the column next to the queue they are logged into." -msgstr "" - -#: ../../content/applications/general/voip/axivox/call_queues.rst:235 -msgid "To log out of the queue, open the Odoo *VoIP* widget, dial the :guilabel:`Agent disconnection` number, and press the green call button :guilabel:`📞 (phone)` icon. The agent is disconnected from the queue after a short, two-second message." -msgstr "" - -#: ../../content/applications/general/voip/axivox/call_queues.rst:239 -msgid "To manually log a dynamic agent out of a call queue, navigate to the `Axivox management console `_, and click :guilabel:`Queues`, located in the left-hand column. Then, click the green :guilabel:`Refresh` button at the top of the :guilabel:`Connected agents` column." -msgstr "" - -#: ../../content/applications/general/voip/axivox/call_queues.rst:243 -msgid "To disconnect an agent manually, click the red :guilabel:`Disconnect` button, and they are immediately disconnected. This can be helpful in situations where agents forget to log out at the end of the day." -msgstr "" - -#: ../../content/applications/general/voip/axivox/conference_calls.rst:3 -msgid "Conference calls" -msgstr "" - -#: ../../content/applications/general/voip/axivox/conference_calls.rst:5 -msgid "Conference calls help employees connect quickly and efficiently, so matters can be discussed in an open forum of sorts. Attendees can be limited, via a sign-in code. That way, confidential matters stay private." -msgstr "" - -#: ../../content/applications/general/voip/axivox/conference_calls.rst:9 -msgid "This document covers the configuration of conference calls in Axivox for use in Odoo *VoIP*." -msgstr "" - -#: ../../content/applications/general/voip/axivox/conference_calls.rst:12 -msgid "Add a virtual conference" -msgstr "" - -#: ../../content/applications/general/voip/axivox/conference_calls.rst:14 -msgid "To add a virtual conference room, navigate to the `Axivox management console `_. After logging in, click on :guilabel:`Conferences` in the menu on the left." -msgstr "" - -#: ../../content/applications/general/voip/axivox/conference_calls.rst:18 -msgid "Next, click the green button labeled, :guilabel:`Add a conference`, and a :guilabel:`New conference` form appears." -msgstr "" - -#: ../../content/applications/general/voip/axivox/conference_calls.rst:-1 -msgid "New conference form on Axivox." -msgstr "" - -#: ../../content/applications/general/voip/axivox/conference_calls.rst:25 -msgid "From here, fill in the :guilabel:`Name` field, and set an :guilabel:`Internal extension`." -msgstr "" - -#: ../../content/applications/general/voip/axivox/conference_calls.rst:27 -msgid "The internal extension is what everyone in the network uses to quickly dial into the conference call, instead of typing in the whole phone number." -msgstr "" - -#: ../../content/applications/general/voip/axivox/conference_calls.rst:31 -msgid "Pick a number between three and five digits long, making it easy to remember and dial." -msgstr "" - -#: ../../content/applications/general/voip/axivox/conference_calls.rst:33 -msgid "Next, set the :guilabel:`Access code`, if the conference room requires security. This is a password to get into the conference, once the extension for the conference is dialed. Immediately after dialing the extension, a digital receptionist prompts for the :guilabel:`Access code`." -msgstr "" - -#: ../../content/applications/general/voip/axivox/conference_calls.rst:37 -msgid "In the :guilabel:`Administrator extension` field, click the drop-down menu, and select the user's extension that manages the call." -msgstr "" - -#: ../../content/applications/general/voip/axivox/conference_calls.rst:40 -msgid "Finally, in the :guilabel:`Wait for the administrator to start the conference` field, click the drop-down menu, and select :guilabel:`Yes` or :guilabel:`No`." -msgstr "" - -#: ../../content/applications/general/voip/axivox/conference_calls.rst:43 -msgid "Should the selection be :guilabel:`Yes`, then nobody is allowed to utilize the virtual conference room until the administrator is present, and logged into the conference call." -msgstr "" - -#: ../../content/applications/general/voip/axivox/conference_calls.rst:46 -msgid "When all fields are filled in, be sure to :guilabel:`Save` the configuration. Then, click :guilabel:`Apply changes` in the upper-right corner to implement the change in production." -msgstr "" - -#: ../../content/applications/general/voip/axivox/conference_calls.rst:49 -msgid "Upon doing so, the conference is added, and the Axivox administrator has the option to :guilabel:`Delete` or :guilabel:`Edit` the conference from the Axivox :guilabel:`Conference` main dashboard." -msgstr "" - -#: ../../content/applications/general/voip/axivox/conference_calls.rst:53 -msgid "To invite an Axivox user to a specific conference call, click :guilabel:`Invite` to the right of the desired conference, and proceed to enter the extension or phone number of the invitee in the pop-up window that appears." -msgstr "" - -#: ../../content/applications/general/voip/axivox/conference_calls.rst:57 -msgid "Once the extension or number is added into the :guilabel:`Please enter the phone number of the person you want to invite` field, click the green :guilabel:`Invite` button, and the recipient immediately receives a phone call, automatically linking them to the conference." -msgstr "" - -#: ../../content/applications/general/voip/axivox/conference_calls.rst:66 -#: ../../content/applications/general/voip/axivox/manage_users.rst:32 -msgid "Incoming numbers" -msgstr "" - -#: ../../content/applications/general/voip/axivox/conference_calls.rst:68 -msgid "To open a conference to a wider audience, an Axivox conference can be linked to *Incoming numbers*." -msgstr "" - -#: ../../content/applications/general/voip/axivox/conference_calls.rst:70 -msgid "To do that, log into the `Axivox management console `_, and click :guilabel:`Incoming numbers` in the menu on the left." -msgstr "" - -#: ../../content/applications/general/voip/axivox/conference_calls.rst:73 -msgid "On the :guilabel:`Incoming numbers` dashboard, click :guilabel:`Edit` to the far-right of the :guilabel:`Number` to which the conference should be attached." -msgstr "" - -#: ../../content/applications/general/voip/axivox/conference_calls.rst:76 -msgid "Then, under the first field, labeled, :guilabel:`Destination type for voice call`, click the drop-down menu, and select :guilabel:`Conference`." -msgstr "" - -#: ../../content/applications/general/voip/axivox/conference_calls.rst:79 -msgid "Next, in the :guilabel:`Conference` field, click the drop-down menu, and select the specific conference that should be attached to this incoming number." -msgstr "" - -#: ../../content/applications/general/voip/axivox/conference_calls.rst:82 -msgid "Now, whenever this incoming number is dialed, the caller is let into the conference, if there is not an :guilabel:`Access code` required. If there *is* an :guilabel:`Access code` required, the caller is then prompted to enter the :guilabel:`Access code` to enter the conference." -msgstr "" - -#: ../../content/applications/general/voip/axivox/conference_calls.rst:87 -msgid "Start call in Odoo" -msgstr "" - -#: ../../content/applications/general/voip/axivox/conference_calls.rst:89 -msgid "Anywhere in the Odoo database, open the *VoIP* widget, by clicking the :guilabel:`☎️ (phone)` icon, located in the upper-right corner. Then, dial the specific extension number for the conference, and click the :guilabel:`📞 (phone)` icon." -msgstr "" - -#: ../../content/applications/general/voip/axivox/conference_calls.rst:-1 -msgid "Connecting to a conference extension using the Odoo VoIP widget." -msgstr "" - -#: ../../content/applications/general/voip/axivox/conference_calls.rst:97 -msgid "Once the digital receptionist answers, enter the :guilabel:`Access code` (if needed), and press the :guilabel:`# (pound)` icon/key." -msgstr "" - -#: ../../content/applications/general/voip/axivox/dial_plan_advanced.rst:3 -msgid "Advanced dial plans" -msgstr "" - -#: ../../content/applications/general/voip/axivox/dial_plan_advanced.rst:5 -msgid "Typically, companies have a lot of incoming calls every day, but many do not want their teams to answer calls 24 hours a day, 7 days a week." -msgstr "" - -#: ../../content/applications/general/voip/axivox/dial_plan_advanced.rst:8 -msgid "By using Axivox advanced dial plan features, the process can be automated, and routing can be set up for all scenarios. This way, customers are never left waiting, or frustrated, because they cannot get in touch with anyone." -msgstr "" - -#: ../../content/applications/general/voip/axivox/dial_plan_advanced.rst:12 -msgid "By utilizing the advanced elements in dial plans, companies can automate call routing for certain days or times, like company holidays. Companies can also allow callers to enter extensions themselves, and get transferred automatically using a digital receptionist. This way, an administrative team does **not** have to be available around the clock." -msgstr "" - -#: ../../content/applications/general/voip/axivox/dial_plan_advanced.rst:17 -msgid "There is even the option to route callers, depending on where they are calling from in the world, thus maximizing efficiency." -msgstr "" - -#: ../../content/applications/general/voip/axivox/dial_plan_advanced.rst:21 -msgid "For more information on basic dial plans, and how to add elements, visit :doc:`dial_plan_basics`." -msgstr "" - -#: ../../content/applications/general/voip/axivox/dial_plan_advanced.rst:24 -msgid "Using a browser add-on for spelling may hinder the use of the visual editor in dial plans. Do **not** use a translator with the Axivox management console." -msgstr "" - -#: ../../content/applications/general/voip/axivox/dial_plan_advanced.rst:28 -#: ../../content/applications/general/voip/axivox/dial_plan_basics.rst:160 -msgid "Advanced elements" -msgstr "" - -#: ../../content/applications/general/voip/axivox/dial_plan_advanced.rst:30 -msgid "In Axivox dial plans (as described in :doc:`dial_plan_basics`), there are two advanced elements that can be used." -msgstr "" - -#: ../../content/applications/general/voip/axivox/dial_plan_advanced.rst:33 -#: ../../content/applications/general/voip/axivox/dial_plan_basics.rst:164 -msgid ":guilabel:`Record`: recording feature is enabled (requires plan change, enabled in Axivox settings)." -msgstr "" - -#: ../../content/applications/general/voip/axivox/dial_plan_advanced.rst:35 -#: ../../content/applications/general/voip/axivox/dial_plan_basics.rst:166 -msgid ":guilabel:`Caller ID`: replace the caller ID by the called number or free text." -msgstr "" - -#: ../../content/applications/general/voip/axivox/dial_plan_advanced.rst:37 -msgid "To add one of these elements, navigate to the :guilabel:`Dial plans` page, located in the menu on the left side of the `Axivox management console `_." -msgstr "" - -#: ../../content/applications/general/voip/axivox/dial_plan_advanced.rst:40 -msgid "Next, click on the :guilabel:`Visual Editor` button to the right of the desired dial plan to edit it. Finally, open the :guilabel:`New element` drop-down menu, select the element, and click :guilabel:`Add`." -msgstr "" - -#: ../../content/applications/general/voip/axivox/dial_plan_advanced.rst:-1 -msgid "Visual editor for a dial plan in Axivox, with Add and the dispatcher element highlighted." -msgstr "" - -#: ../../content/applications/general/voip/axivox/dial_plan_advanced.rst:48 -#: ../../content/applications/general/voip/axivox/dial_plan_advanced.rst:99 -msgid "For more information, visit :ref:`voip/axivox/dial_plans`." -msgstr "" - -#: ../../content/applications/general/voip/axivox/dial_plan_advanced.rst:51 -msgid "The :guilabel:`Record` element records calls that are routed through this element, and requires an additional plan change in Axivox." -msgstr "" - -#: ../../content/applications/general/voip/axivox/dial_plan_advanced.rst:54 -msgid "To enable recording on Axivox, navigate to :guilabel:`Settings` in the `Axivox management console `_. Then, go to the :guilabel:`Recording` drop-down menu, near the bottom of the page. From there, select :guilabel:`Enabled` from the drop-down menu to enable recording using the :guilabel:`Record` element in a dial plan." -msgstr "" - -#: ../../content/applications/general/voip/axivox/dial_plan_advanced.rst:60 -msgid "If the :guilabel:`Recording` drop-down menu is unavailable and unable to change, then consult Axivox to enable the feature." -msgstr "" - -#: ../../content/applications/general/voip/axivox/dial_plan_advanced.rst:63 -msgid "The :guilabel:`Caller ID` element allows for the replacement of the caller ID downstream, after routing." -msgstr "" - -#: ../../content/applications/general/voip/axivox/dial_plan_advanced.rst:66 -msgid "Upon adding the :guilabel:`Caller ID` element to the dial plan, and double-clicking it to configure it, two options appear." -msgstr "" - -#: ../../content/applications/general/voip/axivox/dial_plan_advanced.rst:69 -msgid "The first is a :guilabel:`Free text` field, where any text can be input to replace the caller ID. The second option is :guilabel:`Replace the caller ID by the called number`. This option replaces the caller's ID with the :guilabel:`Incoming number`." -msgstr "" - -#: ../../content/applications/general/voip/axivox/dial_plan_advanced.rst:74 -msgid "A company may want to use the :guilabel:`Caller ID` element to replace the :guilabel:`Incoming number`, so employees, or outside transfers, cannot see the number, and information is kept private." -msgstr "" - -#: ../../content/applications/general/voip/axivox/dial_plan_advanced.rst:79 -#: ../../content/applications/general/voip/axivox/dial_plan_basics.rst:135 -msgid "Basic routing elements" -msgstr "" - -#: ../../content/applications/general/voip/axivox/dial_plan_advanced.rst:81 -msgid "Basic routing elements in Axivox dial plans provide extension-based routing. This can be done by adding either a *Menu* to numerically link the dial-by-numbers to an action, or by using a *Digital Receptionist* to automatically route or listen for an extension, based on a key input from the caller." -msgstr "" - -#: ../../content/applications/general/voip/axivox/dial_plan_advanced.rst:86 -msgid "The main difference between the two elements is that the *Digital Receptionist* does **not** need to be pre-configured numerically with actions. Instead, it acts as a virtual receptionist." -msgstr "" - -#: ../../content/applications/general/voip/axivox/dial_plan_advanced.rst:89 -msgid ":guilabel:`Menu`: add a dial-by-number directory and configured downstream actions (not terminal). For example, a dial-by-numbers function could feature an element, wherein clicking '2' takes the caller to the element linked to '2' on the Menu element in the dial plan." -msgstr "" - -#: ../../content/applications/general/voip/axivox/dial_plan_advanced.rst:92 -msgid ":guilabel:`Digital Receptionist`: attach a virtual dispatcher to listen for extensions." -msgstr "" - -#: ../../content/applications/general/voip/axivox/dial_plan_advanced.rst:94 -msgid "To add one of these elements, navigate to the :guilabel:`Dial plans` page, located in the menu on the left side of the `Axivox management console `_. Next, click on the :guilabel:`Visual Editor` button to the right of the dial plan, to edit the dial plan. Then, open the :guilabel:`New element` drop-down menu, select the element, and click :guilabel:`Add`." -msgstr "" - -#: ../../content/applications/general/voip/axivox/dial_plan_advanced.rst:102 -msgid "Digital receptionist scenario" -msgstr "" - -#: ../../content/applications/general/voip/axivox/dial_plan_advanced.rst:104 -msgid "The *Digital Receptionist* element is a listen-feature that accurately routes callers through a dial plan, based on the extension they enter, via the key pad." -msgstr "" - -#: ../../content/applications/general/voip/axivox/dial_plan_advanced.rst:107 -msgid "Set a *Digital Receptionist* to eliminate the need of a team, or live receptionist, to be on-call all the time. With that element in place, calls now reach their destination, without a real person interjecting." -msgstr "" - -#: ../../content/applications/general/voip/axivox/dial_plan_advanced.rst:111 -msgid "After adding the :guilabel:`Digital Receptionist` element to a dial plan, connect the appropriate endpoints, and double-click on the element to set the :guilabel:`Timeout` on the :guilabel:`receptionist` pop-up window that appears." -msgstr "" - -#: ../../content/applications/general/voip/axivox/dial_plan_advanced.rst:115 -msgid "The :guilabel:`Timeout` can be set in `5` second increments, from `5` seconds to `60` seconds." -msgstr "" - -#: ../../content/applications/general/voip/axivox/dial_plan_advanced.rst:118 -msgid "The :guilabel:`Digital Receptionist` element **requires** a :guilabel:`Play a file` element on either side of it, to explain what action to take, and when a wrong extension is entered." -msgstr "" - -#: ../../content/applications/general/voip/axivox/dial_plan_advanced.rst:122 -msgid "While customizing a dial plan in a :guilabel:`Dialplan Editor` pop-up window, add a :guilabel:`Menu` element, with a :guilabel:`Greeting message` that might read, `Press star to dial an extension`." -msgstr "" - -#: ../../content/applications/general/voip/axivox/dial_plan_advanced.rst:126 -msgid "Then, on the :guilabel:`Menu` element, for the :guilabel:`* (star)` option, link a :guilabel:`Play a file` element, that plays an :guilabel:`Audio message` saying, 'Enter the extension of the person you are trying to reach'." -msgstr "" - -#: ../../content/applications/general/voip/axivox/dial_plan_advanced.rst:130 -msgid "Following the first :guilabel:`Play a file` element, add the :guilabel:`Digital Receptionist` element, followed by another :guilabel:`Play a file` element, which states, 'That is not a valid extension'." -msgstr "" - -#: ../../content/applications/general/voip/axivox/dial_plan_advanced.rst:134 -msgid "This last element is in place to close the loop, should the caller not enter a correct extension." -msgstr "" - -#: ../../content/applications/general/voip/axivox/dial_plan_advanced.rst:136 -msgid "Finally, this last :guilabel:`Play a file` element is looped back into the :guilabel:`Menu` element." -msgstr "" - -#: ../../content/applications/general/voip/axivox/dial_plan_advanced.rst:0 -msgid "A digital receptionist element highlighted in an example dial plan." -msgstr "" - -#: ../../content/applications/general/voip/axivox/dial_plan_advanced.rst:144 -msgid "Dial plan elements can be configured by double-clicking them, and selecting different features of the Axivox console to them." -msgstr "" - -#: ../../content/applications/general/voip/axivox/dial_plan_advanced.rst:147 -msgid "For example, an :guilabel:`Audio message` needs to be made, and then selected in a :guilabel:`Play a file` or :guilabel:`Menu` element." -msgstr "" - -#: ../../content/applications/general/voip/axivox/dial_plan_advanced.rst:150 -msgid "For more information, see this documentation :ref:`voip/axivox/audio_messages`." -msgstr "" - -#: ../../content/applications/general/voip/axivox/dial_plan_advanced.rst:153 -#: ../../content/applications/general/voip/axivox/dial_plan_basics.rst:147 -msgid "Advanced routing elements" -msgstr "" - -#: ../../content/applications/general/voip/axivox/dial_plan_advanced.rst:155 -msgid "Advanced routing elements route calls automatically as they are received into the incoming number(s). This can be configured using geo-location, whitelisting, or time-based variables. Calls pass through a filter prior to their final destination, and are routed, based on the set variable(s)." -msgstr "" - -#: ../../content/applications/general/voip/axivox/dial_plan_advanced.rst:160 -msgid "The following are advanced routing elements:" -msgstr "" - -#: ../../content/applications/general/voip/axivox/dial_plan_advanced.rst:162 -msgid ":guilabel:`Dispatcher`: create a call filter to route traffic, based on the geo-location of the caller ID." -msgstr "" - -#: ../../content/applications/general/voip/axivox/dial_plan_advanced.rst:164 -msgid ":guilabel:`Access List`: create a tailored access list, with VIP customer preference." -msgstr "" - -#: ../../content/applications/general/voip/axivox/dial_plan_advanced.rst:165 -#: ../../content/applications/general/voip/axivox/dial_plan_basics.rst:154 -msgid ":guilabel:`Time Condition`: create time conditions to route incoming traffic around holidays, or other sensitive time-frames." -msgstr "" - -#: ../../content/applications/general/voip/axivox/dial_plan_advanced.rst:169 -msgid "Whitelisting is a technical term used to create a list of allowed numbers. Conversely, blacklisting is used to create a list of denied numbers." -msgstr "" - -#: ../../content/applications/general/voip/axivox/dial_plan_advanced.rst:172 -msgid "To add one of these elements, navigate to the :guilabel:`Dial plans` page, located in the menu on the left side of the `Axivox management console `_. Next, click on the :guilabel:`Visual Editor` button to the right of the dial plan, to edit the dial plan. Then, open the :guilabel:`New element` drop-down menu, select the element, and click :guilabel:`Add`. For more information, visit :ref:`voip/axivox/dial_plans`." -msgstr "" - -#: ../../content/applications/general/voip/axivox/dial_plan_advanced.rst:179 -msgid "Dispatcher scenario" -msgstr "" - -#: ../../content/applications/general/voip/axivox/dial_plan_advanced.rst:181 -msgid "A *Dispatcher* element is a dial plan feature that directs calls, based on region or geo-location. In most cases, the :guilabel:`Dispatcher` element in a dial plan is linked to the :guilabel:`Start` element, in order to filter or screen calls as they come into an incoming number." -msgstr "" - -#: ../../content/applications/general/voip/axivox/dial_plan_advanced.rst:185 -msgid "Double-click the :guilabel:`Dispatcher` element in the :guilabel:`Dialplan Editor` pop-up window to configure it." -msgstr "" - -#: ../../content/applications/general/voip/axivox/dial_plan_advanced.rst:188 -msgid "This element checks numbers (routed through this element), according to regular expressions. To add a regular expression, click :guilabel:`Add a line` on the bottom of the :guilabel:`Dispatcher` pop-up window." -msgstr "" - -#: ../../content/applications/general/voip/axivox/dial_plan_advanced.rst:192 -msgid "Then, under :guilabel:`Name`, enter a recognizable name to identify this expression. This is the name that appears in the :guilabel:`Dispatcher` element on the dial plan showcased in the :guilabel:`Dialplan Editor` pop-up window." -msgstr "" - -#: ../../content/applications/general/voip/axivox/dial_plan_advanced.rst:196 -msgid "In the :guilabel:`Regular expression` field, enter the country code, or area code, which Axivox should route for incoming calls. This is especially helpful when a company would like to filter their customers to certain queues, or users based on the customer's geo-location." -msgstr "" - -#: ../../content/applications/general/voip/axivox/dial_plan_advanced.rst:200 -msgid "To specify all numbers behind a certain country code, or area code, include `\\d+` after the country code, or country code + area code." -msgstr "" - -#: ../../content/applications/general/voip/axivox/dial_plan_advanced.rst:-1 -msgid "Dispatcher configuration panel, with name, regular expression and add a line highlighted." -msgstr "" - -#: ../../content/applications/general/voip/axivox/dial_plan_advanced.rst:208 -msgid "`02\\\\d+`: validates the numbers starting with `02`" -msgstr "" - -#: ../../content/applications/general/voip/axivox/dial_plan_advanced.rst:209 -msgid "`00\\\\d+`: validates all numbers beginning with `00`" -msgstr "" - -#: ../../content/applications/general/voip/axivox/dial_plan_advanced.rst:210 -msgid "`0052\\\\d+` validates all numbers beginning with `0052` (Mexico country code)" -msgstr "" - -#: ../../content/applications/general/voip/axivox/dial_plan_advanced.rst:211 -msgid "`001716\\\\d+`: validates all numbers beginning with `001716` (USA country code + Western New York area code)" -msgstr "" - -#: ../../content/applications/general/voip/axivox/dial_plan_advanced.rst:215 -msgid "A regular expression (shortened to \"regex\" or \"regexp\"), sometimes referred to as a \"rational expression,\" is a sequence of characters that specifies a match pattern in text. In other words, a match is made within the given range of numbers." -msgstr "" - -#: ../../content/applications/general/voip/axivox/dial_plan_advanced.rst:219 -msgid "When the desired configurations are complete on the :guilabel:`Dispatcher` pop-up window, be sure to click :guilabel:`Save`." -msgstr "" - -#: ../../content/applications/general/voip/axivox/dial_plan_advanced.rst:222 -msgid "Upon doing so, the :guilabel:`Dispatcher` element appears with different routes available to configure, based on the :guilabel:`Regular Expressions` that were set." -msgstr "" - -#: ../../content/applications/general/voip/axivox/dial_plan_advanced.rst:225 -msgid "Attach these routes to any :guilabel:`New element` in the :guilabel:`Dialplan Editor` pop-up window." -msgstr "" - -#: ../../content/applications/general/voip/axivox/dial_plan_advanced.rst:227 -msgid "By default, there is an :guilabel:`Unknown` path that appears on the :guilabel:`Dispatcher` element after setting at least one :guilabel:`Regular Expression`." -msgstr "" - -#: ../../content/applications/general/voip/axivox/dial_plan_advanced.rst:230 -msgid "Calls follow this route/path when their number does not match any :guilabel:`Regular Expression` set on the :guilabel:`Dispatcher` element." -msgstr "" - -#: ../../content/applications/general/voip/axivox/dial_plan_advanced.rst:-1 -msgid "Dial plan with dispatcher element highlighted." -msgstr "" - -#: ../../content/applications/general/voip/axivox/dial_plan_advanced.rst:238 -msgid "Time condition scenario" -msgstr "" - -#: ../../content/applications/general/voip/axivox/dial_plan_advanced.rst:240 -msgid "When a :guilabel:`Time Condition` element is added to a dial plan, it has a simple :guilabel:`True` and :guilabel:`False` routing." -msgstr "" - -#: ../../content/applications/general/voip/axivox/dial_plan_advanced.rst:243 -msgid "After adding the :guilabel:`Time Condition` element to a dial plan, double-click it to configure the variables. :guilabel:`Hour/Minute`, :guilabel:`Days of the week`, :guilabel:`Day of the month`, and :guilabel:`Month` can all be configured." -msgstr "" - -#: ../../content/applications/general/voip/axivox/dial_plan_advanced.rst:247 -msgid "If the time which the caller contacts the incoming number matches the set time conditions, then the :guilabel:`True` path is followed, otherwise the :guilabel:`False` path is followed." -msgstr "" - -#: ../../content/applications/general/voip/axivox/dial_plan_advanced.rst:251 -msgid "For a company that is closed yearly for the American Independence Day holiday (July 4th) the following time conditions should be set:" -msgstr "" - -#: ../../content/applications/general/voip/axivox/dial_plan_advanced.rst:254 -msgid ":guilabel:`Hour/Minute` - `0:0 to 23:59`" -msgstr "" - -#: ../../content/applications/general/voip/axivox/dial_plan_advanced.rst:255 -msgid ":guilabel:`Day of the week` - `All to All`" -msgstr "" - -#: ../../content/applications/general/voip/axivox/dial_plan_advanced.rst:256 -msgid ":guilabel:`Day of the month` - `From 4 to 4`" -msgstr "" - -#: ../../content/applications/general/voip/axivox/dial_plan_advanced.rst:257 -msgid ":guilabel:`Month` - `July`" -msgstr "" - -#: ../../content/applications/general/voip/axivox/dial_plan_advanced.rst:259 -msgid "The :guilabel:`Time Condition` element is especially useful for holidays, weekends, and to set working hours. When a caller reaches a destination where they can be helped, either with a real person or voicemail, this reduces wasted time and hangups." -msgstr "" - -#: ../../content/applications/general/voip/axivox/dial_plan_advanced.rst:-1 -msgid "Time condition element set in a dial plan on Axivox. Time condition is highlighted." -msgstr "" - -#: ../../content/applications/general/voip/axivox/dial_plan_advanced.rst:268 -msgid "To set the :guilabel:`Timezone` that the :guilabel:`Time Condition` operates under, navigate to `Axivox management console `_, and click :guilabel:`Settings` in the menu on the left. Then, set the :guilabel:`Timezone` using the second field from the bottom, by clicking the drop-down menu." -msgstr "" - -#: ../../content/applications/general/voip/axivox/dial_plan_advanced.rst:274 -msgid "Access list scenario" -msgstr "" - -#: ../../content/applications/general/voip/axivox/dial_plan_advanced.rst:276 -msgid "An *Access List* element in a dial plan allows for the routing of certain numbers, and disallows (denies) other numbers." -msgstr "" - -#: ../../content/applications/general/voip/axivox/dial_plan_advanced.rst:279 -msgid "After adding an :guilabel:`Access List` element to a dial plan, it can be configured by double-clicking on the element directly in the :guilabel:`Dialplan Editor` pop-up window." -msgstr "" - -#: ../../content/applications/general/voip/axivox/dial_plan_advanced.rst:282 -msgid "Two fields appear where regular expressions can based in the :guilabel:`Allow` and :guilabel:`Deny` fields of the :guilabel:`Access List` pop-up window." -msgstr "" - -#: ../../content/applications/general/voip/axivox/dial_plan_advanced.rst:286 -msgid "For a very important customer, their number can be set in the :guilabel:`Allow` field, and these callers can be sent directly to management." -msgstr "" - -#: ../../content/applications/general/voip/axivox/dial_plan_advanced.rst:290 -msgid "A regular expression (shortened to \"regex\" or \"regexp\"), sometimes also referred to as a \"rational expression,\" is a sequence of characters that specifies a match pattern in text." -msgstr "" - -#: ../../content/applications/general/voip/axivox/dial_plan_advanced.rst:-1 -msgid "Access list element configuration with the allow/deny fields highlighted." -msgstr "" - -#: ../../content/applications/general/voip/axivox/dial_plan_advanced.rst:298 -msgid "`2\\\\d\\\\d`: validates numbers from `200 to 299`" -msgstr "" - -#: ../../content/applications/general/voip/axivox/dial_plan_advanced.rst:299 -msgid "`02\\\\d*`: validates all numbers beginning with `02`" -msgstr "" - -#: ../../content/applications/general/voip/axivox/dial_plan_advanced.rst:300 -msgid "`0017165551212`: validates the number (`0017165551212`)" -msgstr "" - -#: ../../content/applications/general/voip/axivox/dial_plan_advanced.rst:302 -msgid "After setting the :guilabel:`Allow` and :guilabel:`Deny` fields with regular expressions or numbers, click :guilabel:`Save` on the :guilabel:`Access List` pop-up window." -msgstr "" - -#: ../../content/applications/general/voip/axivox/dial_plan_advanced.rst:305 -msgid "Then, on the :guilabel:`Access list` element in the dial plan, three paths (or routes) are available to link to further actions." -msgstr "" - -#: ../../content/applications/general/voip/axivox/dial_plan_advanced.rst:308 -msgid "Unknown calls can be routed through the regular menu flow by adding a :guilabel:`Menu` element, and connecting it to the :guilabel:`Unknown` path. :guilabel:`Refused` calls can be routed to the :guilabel:`Hang up` element. Lastly, :guilabel:`Authorized` callers can be sent to a specific extension or queue." -msgstr "" - -#: ../../content/applications/general/voip/axivox/dial_plan_advanced.rst:-1 -msgid "Access list element highlighted in an example dial plan." -msgstr "" - -#: ../../content/applications/general/voip/axivox/dial_plan_advanced.rst:318 -msgid "Switches" -msgstr "" - -#: ../../content/applications/general/voip/axivox/dial_plan_advanced.rst:320 -msgid "A *Switch* element in Axivox is a simple activated/deactivated route action." -msgstr "" - -#: ../../content/applications/general/voip/axivox/dial_plan_advanced.rst:322 -msgid "These can be activated or chosen quickly, allowing for quick routing changes, without altering the dial plan." -msgstr "" - -#: ../../content/applications/general/voip/axivox/dial_plan_advanced.rst:325 -msgid "Alternate routes can be configured, so that in a moments notice, they can be switched to. This could be for new availability, or to adjust traffic flow for any number of reasons." -msgstr "" - -#: ../../content/applications/general/voip/axivox/dial_plan_advanced.rst:328 -msgid "Axivox allows for a simple on/off switch, and a multi-switch, which can have several paths to choose from." -msgstr "" - -#: ../../content/applications/general/voip/axivox/dial_plan_advanced.rst:331 -msgid ":guilabel:`Switch`: a manual on/off control that can divert traffic, based on whether it is opened (on) or closed (off)." -msgstr "" - -#: ../../content/applications/general/voip/axivox/dial_plan_advanced.rst:333 -#: ../../content/applications/general/voip/axivox/dial_plan_basics.rst:156 -msgid ":guilabel:`Multi-Switch`: a mechanism to create paths, and turn them on and off, to divert incoming calls." -msgstr "" - -#: ../../content/applications/general/voip/axivox/dial_plan_advanced.rst:337 -msgid "Basic switch" -msgstr "" - -#: ../../content/applications/general/voip/axivox/dial_plan_advanced.rst:339 -msgid "A :guilabel:`Switch` can be set in the `Axivox management console `_ by navigating to :guilabel:`Switches` in the left menu. To create a new switch click :guilabel:`Add a switch` from the :guilabel:`Switches` dashboard, configure a :guilabel:`Name` for it, and click :guilabel:`Save`." -msgstr "" - -#: ../../content/applications/general/voip/axivox/dial_plan_advanced.rst:344 -msgid "Then, toggle the desired switch to either :guilabel:`On` or :guilabel:`Off`, from the :guilabel:`State` column on the :guilabel:`Switches` dashboard." -msgstr "" - -#: ../../content/applications/general/voip/axivox/dial_plan_advanced.rst:347 -msgid "This :guilabel:`On` / :guilabel:`Off` state automatically routes traffic in a dial plan, in which this switch is set." -msgstr "" - -#: ../../content/applications/general/voip/axivox/dial_plan_advanced.rst:350 -msgid "The traffic travels to the :guilabel:`Active` route when :guilabel:`On` is toggled in the switch. The call traffic travels to the :guilabel:`Inactive` route when :guilabel:`Off` is toggled in the switch." -msgstr "" - -#: ../../content/applications/general/voip/axivox/dial_plan_advanced.rst:354 -msgid "Changes can be made on the fly, just be sure to click :guilabel:`Apply changes` to implement the them." -msgstr "" - -#: ../../content/applications/general/voip/axivox/dial_plan_advanced.rst:358 -msgid "Add a switch to dial plan" -msgstr "" - -#: ../../content/applications/general/voip/axivox/dial_plan_advanced.rst:360 -msgid "To add a :guilabel:`Switch` to a dial plan, navigate to `Axivox management console `_, and click on :guilabel:`Dial plans` in the left menu. Then, click :guilabel:`Visual Editor` next to the desired dial plan to open the :guilabel:`Dialplan Editor` pop-up window." -msgstr "" - -#: ../../content/applications/general/voip/axivox/dial_plan_advanced.rst:365 -msgid "Then, from the :guilabel:`New element` drop-down menu, select :guilabel:`Switch`, and then click :guilabel:`Add`. Double-click on the element to further configure the :guilabel:`Switch` element." -msgstr "" - -#: ../../content/applications/general/voip/axivox/dial_plan_advanced.rst:-1 -msgid "Switch configuration in a dial plan, with inactive and active routes highlighted." -msgstr "" - -#: ../../content/applications/general/voip/axivox/dial_plan_advanced.rst:373 -msgid "Multi-switch" -msgstr "" - -#: ../../content/applications/general/voip/axivox/dial_plan_advanced.rst:375 -msgid "A *Multi-Switch* element in Axivox is a switch where multiple paths can be configured, and switched between." -msgstr "" - -#: ../../content/applications/general/voip/axivox/dial_plan_advanced.rst:378 -msgid "To configure and set a :guilabel:`Multi-Switch` element, navigate to `Axivox management console `_. Then, click on the :guilabel:`Switches` menu item in the left menu." -msgstr "" - -#: ../../content/applications/general/voip/axivox/dial_plan_advanced.rst:381 -msgid "Toggle to the :guilabel:`Multi-switch` tab to create, or set, a pre-configured :guilabel:`Multi-Switch` element." -msgstr "" - -#: ../../content/applications/general/voip/axivox/dial_plan_advanced.rst:384 -msgid "To create a new :guilabel:`Multi-Switch`, click :guilabel:`Create new`. Then, enter a :guilabel:`Name` for the element, and then enter the :guilabel:`Available choice`. Enter one :guilabel:`Available choice` per line. Do **not** duplicate any entries." -msgstr "" - -#: ../../content/applications/general/voip/axivox/dial_plan_advanced.rst:388 -msgid "Remember to click :guilabel:`Save` when done." -msgstr "" - -#: ../../content/applications/general/voip/axivox/dial_plan_advanced.rst:390 -msgid "To select the :guilabel:`State` of the :guilabel:`Multi-Switch`, click the drop-down menu next to the :guilabel:`Multi-Switch` name, under the :guilabel:`Multi-switch` tab on the :guilabel:`Switches` dashboard." -msgstr "" - -#: ../../content/applications/general/voip/axivox/dial_plan_advanced.rst:394 -msgid "The :guilabel:`State` chosen is the route that is followed in the dial plan. The :guilabel:`State` can be edited on the fly, just be sure to click :guilabel:`Apply changes`." -msgstr "" - -#: ../../content/applications/general/voip/axivox/dial_plan_advanced.rst:398 -msgid "Add a multi-switch to dial plan" -msgstr "" - -#: ../../content/applications/general/voip/axivox/dial_plan_advanced.rst:400 -msgid "To add a :guilabel:`Multi-Switch` element to a dial plan, navigate to `Axivox management console `_, and click :guilabel:`Dial plans` in the left menu." -msgstr "" - -#: ../../content/applications/general/voip/axivox/dial_plan_advanced.rst:403 -msgid "Then, select or create a dial plan. Next, click :guilabel:`Visual Editor` on the desired dial plan." -msgstr "" - -#: ../../content/applications/general/voip/axivox/dial_plan_advanced.rst:405 -msgid "On the :guilabel:`Dialplan Editor` pop-up window that appears, click on the :guilabel:`New element` drop-down menu, and select :guilabel:`Multi-Switch`. Then, click :guilabel:`Add`. Double-click on the element to further configure the :guilabel:`Switch` element." -msgstr "" - -#: ../../content/applications/general/voip/axivox/dial_plan_advanced.rst:-1 -msgid "Multi-switch configuration in a dial plan, with chosen route highlighted." -msgstr "" - -#: ../../content/applications/general/voip/axivox/dial_plan_basics.rst:3 -msgid "Dial plan basics" -msgstr "" - -#: ../../content/applications/general/voip/axivox/dial_plan_basics.rst:5 -msgid "When someone calls a business, they might need to get in contact with customer support, a sales team, or even a person's direct line. The caller might also be in search of some information about the business, such as store hours. Or, they might want to leave a voicemail, so someone from the company can call them back. With dial plans in Axivox, a company can manage how incoming calls like this are handled." -msgstr "" - -#: ../../content/applications/general/voip/axivox/dial_plan_basics.rst:11 -msgid "Using proper call architecture through a dial plan, callers get directed to the right people, or to the right information, in a quick, efficient manner." -msgstr "" - -#: ../../content/applications/general/voip/axivox/dial_plan_basics.rst:14 -msgid "This document covers the basic configuration of dial plans in Axivox." -msgstr "" - -#: ../../content/applications/general/voip/axivox/dial_plan_basics.rst:17 -msgid "For more information on advanced dial plans, visit :doc:`dial_plan_advanced`." -msgstr "" - -#: ../../content/applications/general/voip/axivox/dial_plan_basics.rst:20 -msgid "Using a browser add-on for spelling may hinder the use of the visual editor in dial plans. Do not use a translator with the Axivox management console." -msgstr "" - -#: ../../content/applications/general/voip/axivox/dial_plan_basics.rst:26 -msgid "Dial plans" -msgstr "" - -#: ../../content/applications/general/voip/axivox/dial_plan_basics.rst:28 -msgid "Access dial plans by navigating to `Axivox management console `_, and clicking on :guilabel:`Dial plans` from the menu on the left." -msgstr "" - -#: ../../content/applications/general/voip/axivox/dial_plan_basics.rst:31 -msgid "To add a new dial plan from the :guilabel:`Dial plan` page, click the green button labeled, :guilabel:`Add a new dial plan`." -msgstr "" - -#: ../../content/applications/general/voip/axivox/dial_plan_basics.rst:35 -msgid "Axivox has no limit to the number of dial plans that can be created. These can be added, and improved upon, at any time. This allows for sandboxes to be created with many different configurations." -msgstr "" - -#: ../../content/applications/general/voip/axivox/dial_plan_basics.rst:-1 -msgid "Dial plan dashboard with the edit features and Add a dial plan button highlighted." -msgstr "" - -#: ../../content/applications/general/voip/axivox/dial_plan_basics.rst:43 -msgid "To edit an existing dial plan, choose one of the following options to the right of the saved dial plan:" -msgstr "" - -#: ../../content/applications/general/voip/axivox/dial_plan_basics.rst:46 -msgid ":guilabel:`Delete`: this action deletes the attached dial plan." -msgstr "" - -#: ../../content/applications/general/voip/axivox/dial_plan_basics.rst:47 -msgid ":guilabel:`Edit`: this action allows the user to edit the dial plan." -msgstr "" - -#: ../../content/applications/general/voip/axivox/dial_plan_basics.rst:48 -msgid ":guilabel:`Visual Editor`: this action opens a visual editor window, where the dial plan architecture can be viewed and edited." -msgstr "" - -#: ../../content/applications/general/voip/axivox/dial_plan_basics.rst:50 -msgid ":guilabel:`Duplicate`: this action duplicates the dial plan, and puts it at the bottom of the list, with an extension of one number (+1) larger than the original extension." -msgstr "" - -#: ../../content/applications/general/voip/axivox/dial_plan_basics.rst:54 -msgid "Dialplan editor (visual editor)" -msgstr "" - -#: ../../content/applications/general/voip/axivox/dial_plan_basics.rst:56 -msgid "When the :guilabel:`Visual Editor` button is clicked for a dial plan on the :guilabel:`Dial plan` page, a pop-up :guilabel:`Dialplan Editor` window appears." -msgstr "" - -#: ../../content/applications/general/voip/axivox/dial_plan_basics.rst:59 -msgid "This pop-up window is the primary place where the architecture, or structure, of the dial plan is configured. In this window, a :abbr:`GUI (graphical user interface)` appears, where various dial plan elements can be configured and linked together." -msgstr "" - -#: ../../content/applications/general/voip/axivox/dial_plan_basics.rst:-1 -msgid "Visual editor for an example dial plan, with the new element, Add, and Save buttons\n" -"highlighted." -msgstr "" - -#: ../../content/applications/general/voip/axivox/dial_plan_basics.rst:69 -msgid "New dial plans come blank with :guilabel:`New element` options for the user to :guilabel:`Add` and :guilabel:`Save`." -msgstr "" - -#: ../../content/applications/general/voip/axivox/dial_plan_basics.rst:72 -msgid "The method for saving in the :guilabel:`Dialplan Editor` is different from saving any other edits in the Axivox management console because the :guilabel:`Save` button **must** be pressed before closing the :menuselection:`Visual editor`." -msgstr "" - -#: ../../content/applications/general/voip/axivox/dial_plan_basics.rst:76 -msgid "Then, before these changes can take place on the Axivox platform, the user **must** click :guilabel:`Apply changes` in the upper-right corner of the :guilabel:`Dial plan` page." -msgstr "" - -#: ../../content/applications/general/voip/axivox/dial_plan_basics.rst:79 -msgid "From the :guilabel:`Dialplan Editor` pop-up window, users can add a new element to the dial plan. To do that, open the :guilabel:`New element` drop-down menu, and select the desired element. Then, click :guilabel:`Add`." -msgstr "" - -#: ../../content/applications/general/voip/axivox/dial_plan_basics.rst:83 -msgid "Doing so adds that element to the visual editor display of the dial plan being modified. This element can be moved where desired amongst the other elements present in the dial plan." -msgstr "" - -#: ../../content/applications/general/voip/axivox/dial_plan_basics.rst:86 -msgid "Connect elements in the dial plan by clicking and dragging outward from the :guilabel:`(open circle)` icon on the right side of the element. Doing so reveals an :guilabel:`(arrow)` icon. Proceed to drag this :guilabel:`(arrow)` icon to the desired element in the dial plan that it is meant to connect with." -msgstr "" - -#: ../../content/applications/general/voip/axivox/dial_plan_basics.rst:91 -msgid "Connect the :guilabel:`(arrow)` icon to the circle on the left side of the desired element." -msgstr "" - -#: ../../content/applications/general/voip/axivox/dial_plan_basics.rst:93 -msgid "Calls displayed in the dial plan flow from left-to-right in the element." -msgstr "" - -#: ../../content/applications/general/voip/axivox/dial_plan_basics.rst:95 -msgid "In order to further configure a :guilabel:`New element`, double-click on the element inside the dial plan, to reveal a subsequent pop-up window, wherein additional customizations can be entered." -msgstr "" - -#: ../../content/applications/general/voip/axivox/dial_plan_basics.rst:98 -msgid "Each element has a different configuration pop-up window that appears when double-clicked." -msgstr "" - -#: ../../content/applications/general/voip/axivox/dial_plan_basics.rst:101 -msgid "All elements **must** have a final destination in the dial plan in order to close a loop. This can be accomplished by implementing the :guilabel:`Hang up` element, or looping the element back to a :guilabel:`Menu` element or :guilabel:`Digital Receptionist` element elsewhere in the dial plan." -msgstr "" - -#: ../../content/applications/general/voip/axivox/dial_plan_basics.rst:0 -msgid "Dial plan, shown with highlight looping open end back to the beginning of the menu\n" -"element." -msgstr "" - -#: ../../content/applications/general/voip/axivox/dial_plan_basics.rst:111 -msgid "Once all desired dial plan elements and configurations are complete, remember to click :guilabel:`Save` before exiting the :guilabel:`Dialplan Editor` pop-up window. Then, click :guilabel:`Apply changes` on the :guilabel:`Dial plans` page to ensure they are implemented into Axivox production." -msgstr "" - -#: ../../content/applications/general/voip/axivox/dial_plan_basics.rst:117 -msgid "Dial plan elements" -msgstr "" - -#: ../../content/applications/general/voip/axivox/dial_plan_basics.rst:119 -msgid "The following elements are available in the :guilabel:`New element` drop-down menu, while designing a dial plan in the :guilabel:`Dialplan Editor` pop-up window." -msgstr "" - -#: ../../content/applications/general/voip/axivox/dial_plan_basics.rst:123 -msgid "Basic elements" -msgstr "" - -#: ../../content/applications/general/voip/axivox/dial_plan_basics.rst:125 -msgid "These are the basic elements that are used in simple dial plans in Axivox:" -msgstr "" - -#: ../../content/applications/general/voip/axivox/dial_plan_basics.rst:127 -msgid ":guilabel:`Call`: call an extension or queue." -msgstr "" - -#: ../../content/applications/general/voip/axivox/dial_plan_basics.rst:128 -msgid ":guilabel:`Play a file`: play an audio file or voice greeting." -msgstr "" - -#: ../../content/applications/general/voip/axivox/dial_plan_basics.rst:129 -msgid ":guilabel:`Voicemail`: forward to a voicemail (terminal)." -msgstr "" - -#: ../../content/applications/general/voip/axivox/dial_plan_basics.rst:130 -msgid ":guilabel:`Hang up`: hang up the call (terminal)." -msgstr "" - -#: ../../content/applications/general/voip/axivox/dial_plan_basics.rst:131 -msgid ":guilabel:`Queue`: attach a call queue with a group of users to answer a call." -msgstr "" - -#: ../../content/applications/general/voip/axivox/dial_plan_basics.rst:132 -msgid ":guilabel:`Conference`: add a conference room for a caller to connect to." -msgstr "" - -#: ../../content/applications/general/voip/axivox/dial_plan_basics.rst:137 -msgid "Routing elements change or route the path of a caller, these are some basic routing elements used in Axivox:" -msgstr "" - -#: ../../content/applications/general/voip/axivox/dial_plan_basics.rst:140 -msgid ":guilabel:`Menu`: add a dial-by-number directory and configure downstream actions (not terminal)." -msgstr "" - -#: ../../content/applications/general/voip/axivox/dial_plan_basics.rst:141 -msgid ":guilabel:`Switch`: attach a manual on/off control that can divert traffic based on whether it is opened (On) or closed (Off)." -msgstr "" - -#: ../../content/applications/general/voip/axivox/dial_plan_basics.rst:143 -msgid ":guilabel:`Digital Receptionist`: attach a virtual dispatcher to listen for extensions to connect to." -msgstr "" - -#: ../../content/applications/general/voip/axivox/dial_plan_basics.rst:149 -msgid "These are the more advanced elements that route calls in Axivox:" -msgstr "" - -#: ../../content/applications/general/voip/axivox/dial_plan_basics.rst:151 -msgid ":guilabel:`Dispatcher`: create a call filter to route traffic based on the geo-location of the caller ID." -msgstr "" - -#: ../../content/applications/general/voip/axivox/dial_plan_basics.rst:153 -msgid ":guilabel:`Access List`: create a tailored access list with VIP customer preference." -msgstr "" - -#: ../../content/applications/general/voip/axivox/dial_plan_basics.rst:162 -msgid "The following are more advanced elements (not routing) in Axivox:" -msgstr "" - -#: ../../content/applications/general/voip/axivox/dial_plan_basics.rst:169 -msgid "Dial plan elements can be configured by double-clicking them, and linking different aspects of the Axivox console to them." -msgstr "" - -#: ../../content/applications/general/voip/axivox/dial_plan_basics.rst:173 -msgid "Attach to incoming number" -msgstr "" - -#: ../../content/applications/general/voip/axivox/dial_plan_basics.rst:175 -msgid "To attach an existing dial plan to an incoming number, go to `Axivox management console `_ , and click on :guilabel:`Incoming numbers`." -msgstr "" - -#: ../../content/applications/general/voip/axivox/dial_plan_basics.rst:178 -msgid "Next, click :guilabel:`Edit` next to the number to which the dial plan should be attached." -msgstr "" - -#: ../../content/applications/general/voip/axivox/dial_plan_basics.rst:180 -msgid "Doing so reveals a separate page wherein that number's dial plan can be modified. To do that, select :guilabel:`Dial plan` from the :guilabel:`Destination type for voice call` field drop-down menu. Then, choose the desired dial plan from the :guilabel:`Dial plan` field that appears." -msgstr "" - -#: ../../content/applications/general/voip/axivox/dial_plan_basics.rst:184 -msgid "With that in place, that means when that specific number calls in, the configured dial plan is activated, and runs through the prompts to properly route the caller." -msgstr "" - -#: ../../content/applications/general/voip/axivox/dial_plan_basics.rst:187 -msgid "Finally, :guilabel:`Save` the changes, and click :guilabel:`Apply changes` in the upper-right corner." -msgstr "" - -#: ../../content/applications/general/voip/axivox/dial_plan_basics.rst:191 -msgid "Basic dial plan scenario" -msgstr "" - -#: ../../content/applications/general/voip/axivox/dial_plan_basics.rst:193 -msgid "The following showcases a basic dial plan scenario for call routing, where additional elements can be added to expand the setup. This basic dial plan scenario includes the following linked elements :menuselection:`Start --> Play a file --> Menu --> (Hang-up, Calls, Queues, Conferences) --> (Voicemail, Hang-up)`." -msgstr "" - -#: ../../content/applications/general/voip/axivox/dial_plan_basics.rst:-1 -msgid "Basic dial plan configuration." -msgstr "" - -#: ../../content/applications/general/voip/axivox/dial_plan_basics.rst:203 -msgid "This setup does **not** include any basic or advanced call routing. For more information on call routing, reference this documentation: :doc:`dial_plan_advanced`." -msgstr "" - -#: ../../content/applications/general/voip/axivox/dynamic_caller_id.rst:3 -msgid "Dynamic caller ID" -msgstr "" - -#: ../../content/applications/general/voip/axivox/dynamic_caller_id.rst:5 -msgid "*Caller ID* identifies the caller when they make a phone call. It allows the recipient of the call to see what number the caller is calling from. Caller ID shows users and clients who is calling, so they can choose to pick up or decline the call." -msgstr "" - -#: ../../content/applications/general/voip/axivox/dynamic_caller_id.rst:9 -msgid "Axivox offers a dynamic caller ID option to choose which number is displayed on outgoing calls." -msgstr "" - -#: ../../content/applications/general/voip/axivox/dynamic_caller_id.rst:11 -msgid "International numbers can be purchased to do business transactions internationally, via a phone call, from a number that has an area code or country code of the destination being called. By displaying a local number, this can increase customer engagement." -msgstr "" - -#: ../../content/applications/general/voip/axivox/dynamic_caller_id.rst:15 -msgid "Some companies have many employees making calls from a call center. These employees are not always available to receive a return phone call from a prospective customer. In this case, :abbr:`VoIP (Voice over Internet Protocol)` can be configured in such a way that dynamic caller ID shows the main company phone number, so any number of employees in the group can answer the call. This way, a call is never missed." -msgstr "" - -#: ../../content/applications/general/voip/axivox/dynamic_caller_id.rst:24 -msgid "Default outgoing number" -msgstr "" - -#: ../../content/applications/general/voip/axivox/dynamic_caller_id.rst:26 -msgid "In Axivox a *default number* can be set. This is a company's main number. This means, when anyone from the company (user/employee) calls a number outside the company, the default outgoing number shows up automatically on the caller ID." -msgstr "" - -#: ../../content/applications/general/voip/axivox/dynamic_caller_id.rst:30 -msgid "If someone from outside the company tries to call back a user/employee, they are then funneled back through the main line (default number). If there is a dial plan set up, they are prompted to make selections. This is especially helpful in cases where employees change positions frequently, or if they leave the company." -msgstr "" - -#: ../../content/applications/general/voip/axivox/dynamic_caller_id.rst:39 -msgid "To access the default number, go to the `Axivox management console `_, and log in. Then, click into :guilabel:`Settings` in the left menu, and navigate to :guilabel:`Default outgoing number`." -msgstr "" - -#: ../../content/applications/general/voip/axivox/dynamic_caller_id.rst:43 -msgid "From here, change the :guilabel:`Default outgoing number` by clicking the drop-down menu, and making a selection from the incoming phone numbers available on Axivox." -msgstr "" - -#: ../../content/applications/general/voip/axivox/dynamic_caller_id.rst:46 -msgid "Be sure to :guilabel:`Save` the changes, then click :guilabel:`Apply changes` in the upper-right corner of the :guilabel:`General Settings` page to implement the change." -msgstr "" - -#: ../../content/applications/general/voip/axivox/dynamic_caller_id.rst:49 -msgid "The :guilabel:`Default outgoing number` is what shows up by default in the Axivox management portal. However, the outgoing number can also be configured differently at the user level." -msgstr "" - -#: ../../content/applications/general/voip/axivox/dynamic_caller_id.rst:53 -msgid "Users" -msgstr "" - -#: ../../content/applications/general/voip/axivox/dynamic_caller_id.rst:55 -msgid "To configure the outgoing number at the user level, log in to the `Axivox management console `_. Next, click :guilabel:`Users` from the menu on the left, and then click :guilabel:`Edit` to the right of the user that is to be configured." -msgstr "" - -#: ../../content/applications/general/voip/axivox/dynamic_caller_id.rst:59 -msgid "Under :guilabel:`Outgoing number`, click the drop-down menu to select either the :guilabel:`Default outgoing number` (as specified here: :ref:`voip/axivox/dynamic-caller-id-default`), or any of the incoming numbers on the Axivox account." -msgstr "" - -#: ../../content/applications/general/voip/axivox/dynamic_caller_id.rst:63 -msgid "Choosing the :guilabel:`Default` selection in the :guilabel:`Outgoing number` drop-down menu ensures this user has the :guilabel:`Default outgoing number` shown on their caller ID when making calls." -msgstr "" - -#: ../../content/applications/general/voip/axivox/dynamic_caller_id.rst:66 -msgid "If a specific number is chosen, and that number is assigned to this user under :guilabel:`Incoming numbers` (in the Axivox console's menu on the left), that means this user has a direct line for customers to reach them." -msgstr "" - -#: ../../content/applications/general/voip/axivox/dynamic_caller_id.rst:70 -msgid "Once the desired changes are complete, be sure to click :guilabel:`Save`, then click :guilabel:`Apply changes` in the upper-right corner to implement the change." -msgstr "" - -#: ../../content/applications/general/voip/axivox/dynamic_caller_id.rst:74 -msgid "By default, when creating a new user in Axivox, the :guilabel:`Outgoing number` is automatically set to :guilabel:`Default`." -msgstr "" - -#: ../../content/applications/general/voip/axivox/dynamic_caller_id.rst:78 -msgid "Advanced options" -msgstr "" - -#: ../../content/applications/general/voip/axivox/dynamic_caller_id.rst:80 -msgid "To access the :guilabel:`Advanced options`, navigate to the :guilabel:`Settings` option in the menu on the left of the `Axivox management console `_. Then, click :guilabel:`Advanced options` to the right of :guilabel:`Default outgoing number`." -msgstr "" - -#: ../../content/applications/general/voip/axivox/dynamic_caller_id.rst:84 -msgid "By default, there are not any advanced rules set. To create one, click the green :guilabel:`+ (plus)` icon. Doing so reveals a line with two blank fields. From here, different caller IDs can be set up, depending on what location the user/employee is calling from." -msgstr "" - -#: ../../content/applications/general/voip/axivox/dynamic_caller_id.rst:88 -msgid "To create a rule, first set the :guilabel:`Destination prefix` in the first empty field. This is the country code, complete with zero(s) in front of it. Then, in the second empty field, select the phone number that should be used for calling out from that country code." -msgstr "" - -#: ../../content/applications/general/voip/axivox/dynamic_caller_id.rst:93 -msgid "Check the box for :guilabel:`Apply advanced rules even for users with a default outgoing number configured` to allow these rules to take precedent over all other outgoing configurations." -msgstr "" - -#: ../../content/applications/general/voip/axivox/dynamic_caller_id.rst:97 -msgid "The order of the rules can be modified by dragging-and-dropping them into another order. The first matching rule is applied." -msgstr "" - -#: ../../content/applications/general/voip/axivox/dynamic_caller_id.rst:101 -msgid "For example, a company wants all users/employees to utilize the configured number for Great Britain when calling from the `0044` country code (Great Britain)." -msgstr "" - -#: ../../content/applications/general/voip/axivox/dynamic_caller_id.rst:104 -msgid "To accomplish that, simply type in `0044` into the :guilabel:`Destination prefix` field, and select the number starting with the `+44` country code. Order the rules as necessary, and select the checkbox to supersede all other rules, if needed." -msgstr "" - -#: ../../content/applications/general/voip/axivox/dynamic_caller_id.rst:0 -msgid "Advanced options for the default outgoing number." -msgstr "" - -#: ../../content/applications/general/voip/axivox/dynamic_caller_id.rst:112 -msgid "Once the desired configurations are complete, be sure to click :guilabel:`Save`, then click :guilabel:`Apply changes` in the upper-right corner to implement the change." -msgstr "" - -#: ../../content/applications/general/voip/axivox/manage_users.rst:3 -msgid "Manage users in Axivox" -msgstr "" - -#: ../../content/applications/general/voip/axivox/manage_users.rst:5 -msgid "Managing Axivox :abbr:`VoIP (Voice over Internet Protocol)` users is an important part of setting up :abbr:`VoIP (Voice over Internet Protocol)` in an Odoo database. Each Axivox user has a unique name, phone number and/or extension, and a voicemail. This way, they can be reached in a variety of convenient ways." -msgstr "" - -#: ../../content/applications/general/voip/axivox/manage_users.rst:10 -msgid "Axivox users are organized in a simple, straightforward way in the Axivox console, so an administrator can manage users quickly and easily." -msgstr "" - -#: ../../content/applications/general/voip/axivox/manage_users.rst:14 -msgid "This documentation covers how to configure everything through a provider called, Axivox. Depending on the chosen VoIP provider, the processes to manage users may be different." -msgstr "" - -#: ../../content/applications/general/voip/axivox/manage_users.rst:18 -msgid "Overview" -msgstr "" - -#: ../../content/applications/general/voip/axivox/manage_users.rst:20 -msgid "Begin at the Axivox management console by navigating to `https://manage.axivox.com `_. Log in with the appropriate administrator credentials." -msgstr "" - -#: ../../content/applications/general/voip/axivox/manage_users.rst:24 -msgid "Actions in the Axivox management console **must** be double-saved, in order for the changes to take effect. To save any changes, click :guilabel:`Save` in the individualized changes screen. Then, to implement those changes, click the :guilabel:`Apply Changes` button in the upper-right corner of the console." -msgstr "" - -#: ../../content/applications/general/voip/axivox/manage_users.rst:34 -msgid "Incoming numbers are all the numbers a company is paying to use to receive calls." -msgstr "" - -#: ../../content/applications/general/voip/axivox/manage_users.rst:36 -msgid "Click on :menuselection:`Incoming numbers` from the menu on the left of the Axivox management console. Doing so reveals the :guilabel:`Incoming numbers` page, where all the incoming numbers are listed, along with their :guilabel:`Destination` and SMS information." -msgstr "" - -#: ../../content/applications/general/voip/axivox/manage_users.rst:40 -msgid "The :guilabel:`Destination` determines the action that is taken, or the path the caller follows when dialing said numbers." -msgstr "" - -#: ../../content/applications/general/voip/axivox/manage_users.rst:43 -msgid "To edit the :guilabel:`Destination`, click the :guilabel:`Edit` button to the far-right of the incoming number line to be modified. Then, on the :guilabel:`Edit number` page that appears, the :guilabel:`Destination type for voice call` can be changed." -msgstr "" - -#: ../../content/applications/general/voip/axivox/manage_users.rst:47 -msgid "The options available in the :guilabel:`Destination type for voice call` drop-down menu are as follows:" -msgstr "" - -#: ../../content/applications/general/voip/axivox/manage_users.rst:50 -msgid ":guilabel:`Not configured`" -msgstr "" - -#: ../../content/applications/general/voip/axivox/manage_users.rst:51 -msgid ":guilabel:`Extension`" -msgstr "" - -#: ../../content/applications/general/voip/axivox/manage_users.rst:52 -msgid ":guilabel:`Dial plan`" -msgstr "" - -#: ../../content/applications/general/voip/axivox/manage_users.rst:53 -msgid ":guilabel:`Voicemail`" -msgstr "" - -#: ../../content/applications/general/voip/axivox/manage_users.rst:54 -msgid ":guilabel:`Hang up`" -msgstr "" - -#: ../../content/applications/general/voip/axivox/manage_users.rst:55 -msgid ":guilabel:`Conference`" -msgstr "" - -#: ../../content/applications/general/voip/axivox/manage_users.rst:57 -msgid "Depending on the selection made in the :guilabel:`Destination type for voice call` drop-down menu, a second, selection-specific drop-down menu is populated with further configuration options. Additionally, more fields are revealed, based on the selection made in the :guilabel:`Destination type for voice call` drop-down menu." -msgstr "" - -#: ../../content/applications/general/voip/axivox/manage_users.rst:62 -msgid "Once the desired configurations are complete, click :guilabel:`Save`, then click :guilabel:`Apply changes` in the upper-right corner to implement them." -msgstr "" - -#: ../../content/applications/general/voip/axivox/manage_users.rst:66 -msgid "New users" -msgstr "" - -#: ../../content/applications/general/voip/axivox/manage_users.rst:68 -msgid "Every employee using :abbr:`VoIP (Voice over Internet Protocol)` at the company needs an Axivox user account associated with them." -msgstr "" - -#: ../../content/applications/general/voip/axivox/manage_users.rst:71 -msgid "To view existing users in the Axivox management console, click :guilabel:`Users` from the menu on the left of the console. Every user has a :guilabel:`Number`, :guilabel:`Name`, option for a :guilabel:`Voicemail`, and an :guilabel:`Outgoing number` specified." -msgstr "" - -#: ../../content/applications/general/voip/axivox/manage_users.rst:75 -msgid "To create a new user in the Axivox console, click :guilabel:`Add a user` to reveal a :guilabel:`New user` form. The following tabs are available for configuring the new user:" -msgstr "" - -#: ../../content/applications/general/voip/axivox/manage_users.rst:78 -msgid ":guilabel:`General`: basic information, including the extension of the user, can be set." -msgstr "" - -#: ../../content/applications/general/voip/axivox/manage_users.rst:79 -msgid ":guilabel:`Forwardings`: internal forwards on 'no answer' or busy signals." -msgstr "" - -#: ../../content/applications/general/voip/axivox/manage_users.rst:80 -msgid ":guilabel:`Follow Me`: external forward configuration." -msgstr "" - -#: ../../content/applications/general/voip/axivox/manage_users.rst:81 -msgid ":guilabel:`Keys`: set hot-keys within the :abbr:`VoIP (Voice over Internet Protocol)` system." -msgstr "" - -#: ../../content/applications/general/voip/axivox/manage_users.rst:82 -msgid ":guilabel:`SIP Identifiers`: :abbr:`SIP (Session Initiation Protocol)` username and password for external configuration." -msgstr "" - -#: ../../content/applications/general/voip/axivox/manage_users.rst:84 -msgid ":guilabel:`Permissions`: set access rights for users in the Axivox management console." -msgstr "" - -#: ../../content/applications/general/voip/axivox/manage_users.rst:87 -msgid "General tab" -msgstr "" - -#: ../../content/applications/general/voip/axivox/manage_users.rst:89 -msgid "Under the :guilabel:`General` tab of the :guilabel:`New user` form, in the :guilabel:`Extension` field, input an extension that is unique to the user. This is the number internal users dial to reach a specific employee." -msgstr "" - -#: ../../content/applications/general/voip/axivox/manage_users.rst:93 -msgid "In the :guilabel:`Name` field, input the employee name." -msgstr "" - -#: ../../content/applications/general/voip/axivox/manage_users.rst:95 -msgid "Next, fill out the :guilabel:`Email address of the user` field. A valid email address for the employee should be added here, where the user receives business emails." -msgstr "" - -#: ../../content/applications/general/voip/axivox/manage_users.rst:98 -msgid "In the :guilabel:`GSM number` field, enter an alternative number at which the user can be reached. Be sure to include the country code." -msgstr "" - -#: ../../content/applications/general/voip/axivox/manage_users.rst:102 -#: ../../content/applications/general/voip/onsip.rst:134 -msgid "A country code is a locator code that allows access to the desired country's phone system. The country code is dialed first, prior to the target number. Each country in the world has its own specific country code." -msgstr "" - -#: ../../content/applications/general/voip/axivox/manage_users.rst:106 -#: ../../content/applications/general/voip/onsip.rst:145 -msgid "For a list of comprehensive country codes, visit: `https://countrycode.org `_." -msgstr "" - -#: ../../content/applications/general/voip/axivox/manage_users.rst:-1 -msgid "General tab layout in the Axivox management console." -msgstr "" - -#: ../../content/applications/general/voip/axivox/manage_users.rst:113 -msgid "In the :guilabel:`Voicemail` field, select either :guilabel:`Yes` or :guilabel:`No` from the drop-down menu." -msgstr "" - -#: ../../content/applications/general/voip/axivox/manage_users.rst:116 -msgid "In the :guilabel:`Directory` field, the administrator has the option to leave it blank, by making no changes, or selecting :guilabel:`Default` from the drop-down menu. The :guilabel:`Directory` is used in the *Digital Receptionist* feature element of a dial-plan." -msgstr "" - -#: ../../content/applications/general/voip/axivox/manage_users.rst:120 -msgid "At the bottom of the :guilabel:`General` tab, there are two separate options with selection boxes." -msgstr "" - -#: ../../content/applications/general/voip/axivox/manage_users.rst:122 -msgid "The first option is :guilabel:`This user can receive multiple calls at the same time`. By selecting this option, users are able to receive calls when on another call." -msgstr "" - -#: ../../content/applications/general/voip/axivox/manage_users.rst:125 -msgid "The second option, :guilabel:`This user must log-in to call`, provides the option to make it mandatory for the user to log in." -msgstr "" - -#: ../../content/applications/general/voip/axivox/manage_users.rst:129 -msgid "If a company uses physical VoIP phones on desks, and wants their employees to be able to log in from *any* phone or desk in the office, they would make the selection for :guilabel:`This user must log-in to call`." -msgstr "" - -#: ../../content/applications/general/voip/axivox/manage_users.rst:133 -msgid "Once the desired configurations are complete, click :guilabel:`Save`, then click :guilabel:`Apply changes` in the upper-right corner." -msgstr "" - -#: ../../content/applications/general/voip/axivox/manage_users.rst:139 -msgid "Forwardings tab" -msgstr "" - -#: ../../content/applications/general/voip/axivox/manage_users.rst:141 -msgid "Under the :guilabel:`Forwardings` tab of the :guilabel:`New user` form, a company can decide what happens if someone calls a user, and the call is not answered." -msgstr "" - -#: ../../content/applications/general/voip/axivox/manage_users.rst:145 -msgid "Forwardings are disabled when the :guilabel:`Follow Me` option is enabled." -msgstr "" - -#: ../../content/applications/general/voip/axivox/manage_users.rst:147 -msgid "For example, under the :guilabel:`Forwarding on no answer` field, when the button for :guilabel:`Add a destination` is selected, the option to add a specific user or phone number is revealed. After entering the :guilabel:`Destination`, a specific time frame can be selected by sliding the :guilabel:`seconds bar` to the desired ring time." -msgstr "" - -#: ../../content/applications/general/voip/axivox/manage_users.rst:152 -msgid "Additional :guilabel:`Destinations` can be added on with different ring times." -msgstr "" - -#: ../../content/applications/general/voip/axivox/manage_users.rst:155 -msgid "Ring times can be staggered, so the call is forwarded to another user after the first user does not pick up the call. The option to :guilabel:`Send to voicemail as a last resort` is available to the administrator, should the :guilabel:`Destinations` not pick up." -msgstr "" - -#: ../../content/applications/general/voip/axivox/manage_users.rst:159 -msgid "Under the :guilabel:`Forwarding on busy` field, an administrator can :guilabel:`Add a destination`. When clicked, they can then set the :guilabel:`Destination` (user) and time frame. Should the original user's :abbr:`VoIP (Voice over Internet Protocol)` extension, or incoming number, be busy, the call is forwarded to the destination(s)." -msgstr "" - -#: ../../content/applications/general/voip/axivox/manage_users.rst:-1 -msgid "Manage forwarding calls to different users or phone numbers in the Forwardings tab." -msgstr "" - -#: ../../content/applications/general/voip/axivox/manage_users.rst:168 -msgid "When the desired configurations are complete, click :guilabel:`Save`, then click :guilabel:`Apply changes` in the upper-right corner of the page." -msgstr "" - -#: ../../content/applications/general/voip/axivox/manage_users.rst:172 -msgid "Follow Me tab" -msgstr "" - -#: ../../content/applications/general/voip/axivox/manage_users.rst:174 -msgid "When the :guilabel:`Follow Me` option is selected, under the :guilabel:`Follow Me` tab of the :guilabel:`New user` form, no :menuselection:`Forwardings` can be made." -msgstr "" - -#: ../../content/applications/general/voip/axivox/manage_users.rst:177 -msgid "Also, when the :guilabel:`Follow Me` option is selected, the :guilabel:`Add a destination` button can be selected to add users, or a destination phone number, to the original user's account. That way, these added numbers ring when a call is received." -msgstr "" - -#: ../../content/applications/general/voip/axivox/manage_users.rst:181 -msgid "After entering the :guilabel:`Destination`, a specific time frame can be made by sliding the :guilabel:`seconds bar` to the desired ring time. Additional :guilabel:`Destinations` can be added with different ring times." -msgstr "" - -#: ../../content/applications/general/voip/axivox/manage_users.rst:186 -msgid "The original user's :abbr:`VoIP (Voice over Internet Protocol)` number does **not** ring with this option selected. Ring times can also be staggered, so the call is forwarded to another user after the first user does not pick up the call." -msgstr "" - -#: ../../content/applications/general/voip/axivox/manage_users.rst:-1 -msgid "Ring destinations like different users or phone numbers from the Follow Me tab." -msgstr "" - -#: ../../content/applications/general/voip/axivox/manage_users.rst:195 -msgid "The Odoo mobile app, or another :abbr:`SIP (Session Initiation Protocol)` mobile client, allows for simultaneous ringing of the user's extension or incoming number. For more information, visit the :doc:`VoIP Mobile Integrations <../devices_integrations>` documentation." -msgstr "" - -#: ../../content/applications/general/voip/axivox/manage_users.rst:199 -#: ../../content/applications/general/voip/axivox/manage_users.rst:345 -msgid "Once all desired configurations are complete, click :guilabel:`Save`, then click :guilabel:`Apply changes` in the upper-right corner." -msgstr "" - -#: ../../content/applications/general/voip/axivox/manage_users.rst:203 -msgid "Keys tab" -msgstr "" - -#: ../../content/applications/general/voip/axivox/manage_users.rst:205 -msgid "Under the :guilabel:`Keys` tab of the :guilabel:`New user` form, speed dial actions for the user can be configured. Some more advanced options are available, as well." -msgstr "" - -#: ../../content/applications/general/voip/axivox/manage_users.rst:208 -msgid "The following options are available to set to numerical values `1-20`." -msgstr "" - -#: ../../content/applications/general/voip/axivox/manage_users.rst:210 -msgid "These actions can be set on each number:" -msgstr "" - -#: ../../content/applications/general/voip/axivox/manage_users.rst:212 -msgid ":guilabel:`Not configured`: the default action, which is nothing." -msgstr "" - -#: ../../content/applications/general/voip/axivox/manage_users.rst:213 -msgid ":guilabel:`BLF (Busy lamp fields)`: this action shows the status of other users' phones connected to the Axivox phone system. This is primarily used on a desk-phone." -msgstr "" - -#: ../../content/applications/general/voip/axivox/manage_users.rst:215 -msgid ":guilabel:`Quick Call`: this action allows for a speed-dial of an external number." -msgstr "" - -#: ../../content/applications/general/voip/axivox/manage_users.rst:216 -msgid ":guilabel:`Line`: this action allows the user to call another user." -msgstr "" - -#: ../../content/applications/general/voip/axivox/manage_users.rst:217 -msgid ":guilabel:`Switch`: this action allows the user to switch between calls from a desk-phone." -msgstr "" - -#: ../../content/applications/general/voip/axivox/manage_users.rst:218 -msgid ":guilabel:`Pickup`: this action allows the user to pick up an incoming call from a desk-phone." -msgstr "" - -#: ../../content/applications/general/voip/axivox/manage_users.rst:-1 -msgid "Manage user page with Keys tab highlighted and number 2 key drop-down menu selected (with\n" -"highlight)" -msgstr "" - -#: ../../content/applications/general/voip/axivox/manage_users.rst:225 -#: ../../content/applications/general/voip/axivox/manage_users.rst:313 -msgid "Once all the desired configurations are complete, click :guilabel:`Save`, then click :guilabel:`Apply changes` in the upper-right corner." -msgstr "" - -#: ../../content/applications/general/voip/axivox/manage_users.rst:229 -msgid "Many of the preceding options have secondary options available, as well, that can be used to link a user, or external phone number. These **must** be filled out in conjunction with the initial action." -msgstr "" - -#: ../../content/applications/general/voip/axivox/manage_users.rst:234 -msgid "The :guilabel:`Number of keys` field can be changed by entering in the desired numerical value in the :guilabel:`Number of keys` field, located at the top of the :guilabel:`Keys` tab of the :guilabel:`New user` form." -msgstr "" - -#: ../../content/applications/general/voip/axivox/manage_users.rst:239 -msgid "SIP Identifiers tab" -msgstr "" - -#: ../../content/applications/general/voip/axivox/manage_users.rst:241 -msgid "*SIP*, which stands for Session Initiation Protocol telephony, allows one to make and receive calls through an internet connection. The :guilabel:`SIP Identifiers` tab on the :guilabel:`New user` form, contains credentials needed to configure Axivox users in Odoo and/or a different :abbr:`SIP (Session Initiation Protocol)` mobile client." -msgstr "" - -#: ../../content/applications/general/voip/axivox/manage_users.rst:247 -msgid "See the documentation on configuring Axivox, using the SIP identifiers:" -msgstr "" - -#: ../../content/applications/general/voip/axivox/manage_users.rst:249 -msgid ":doc:`Use VoIP services in Odoo with Axivox `" -msgstr "" - -#: ../../content/applications/general/voip/axivox/manage_users.rst:250 -msgid ":doc:`Axivox Mobile Integrations <../devices_integrations>`" -msgstr "" - -#: ../../content/applications/general/voip/axivox/manage_users.rst:252 -msgid "Under the :guilabel:`SIP Identifiers` tab, the :guilabel:`SIP username` field represents the user's information that was entered in the :guilabel:`Extension` field, under the :guilabel:`General` tab." -msgstr "" - -#: ../../content/applications/general/voip/axivox/manage_users.rst:255 -msgid "The :guilabel:`Domain` field is assigned to the company by the Axivox representative." -msgstr "" - -#: ../../content/applications/general/voip/axivox/manage_users.rst:257 -msgid "The value in the :guilabel:`SIP Password` field is unique for every Axivox user. This value is used to sign into Axivox on Odoo, and for any mobile :abbr:`SIP (Session Initiation Protocol)` clients." -msgstr "" - -#: ../../content/applications/general/voip/axivox/manage_users.rst:-1 -msgid "Important credentials used for external configurations of Axivox VoIP." -msgstr "" - -#: ../../content/applications/general/voip/axivox/manage_users.rst:264 -msgid "The value listed in the :guilabel:`Address of the proxy server` field is typically: `pabx.axivox.com`, but is subject to change by Axivox, so be sure to check the :guilabel:`SIP Identifiers` tab for the most accurate value." -msgstr "" - -#: ../../content/applications/general/voip/axivox/manage_users.rst:268 -msgid "Once all desired configurations have been made, click :guilabel:`Save`, then click :guilabel:`Apply changes` in the upper-right corner." -msgstr "" - -#: ../../content/applications/general/voip/axivox/manage_users.rst:272 -msgid "Permissions tab" -msgstr "" - -#: ../../content/applications/general/voip/axivox/manage_users.rst:274 -msgid "Under the :guilabel:`Permissions` tab of a :guilabel:`New user` form, a :guilabel:`Username` and :guilabel:`Password` can be entered for the user." -msgstr "" - -#: ../../content/applications/general/voip/axivox/manage_users.rst:277 -msgid "Beneath those fields, the following permissions can be granted to Axivox users for portal access:" -msgstr "" - -#: ../../content/applications/general/voip/axivox/manage_users.rst:279 -msgid ":guilabel:`User portal access`" -msgstr "" - -#: ../../content/applications/general/voip/axivox/manage_users.rst:280 -msgid ":guilabel:`User management`" -msgstr "" - -#: ../../content/applications/general/voip/axivox/manage_users.rst:281 -msgid ":guilabel:`Administrator access`" -msgstr "" - -#: ../../content/applications/general/voip/axivox/manage_users.rst:282 -msgid ":guilabel:`Phone management`" -msgstr "" - -#: ../../content/applications/general/voip/axivox/manage_users.rst:283 -msgid ":guilabel:`User group management`" -msgstr "" - -#: ../../content/applications/general/voip/axivox/manage_users.rst:284 -msgid ":guilabel:`Phone number management`" -msgstr "" - -#: ../../content/applications/general/voip/axivox/manage_users.rst:285 -msgid ":guilabel:`Dial plan management`" -msgstr "" - -#: ../../content/applications/general/voip/axivox/manage_users.rst:286 -msgid ":guilabel:`Pickup group management`" -msgstr "" - -#: ../../content/applications/general/voip/axivox/manage_users.rst:287 -msgid ":guilabel:`Switch management`" -msgstr "" - -#: ../../content/applications/general/voip/axivox/manage_users.rst:288 -msgid ":guilabel:`Conference management`" -msgstr "" - -#: ../../content/applications/general/voip/axivox/manage_users.rst:289 -msgid ":guilabel:`Queue management`" -msgstr "" - -#: ../../content/applications/general/voip/axivox/manage_users.rst:290 -msgid ":guilabel:`Voicemail management`" -msgstr "" - -#: ../../content/applications/general/voip/axivox/manage_users.rst:291 -msgid ":guilabel:`Audio messages management`" -msgstr "" - -#: ../../content/applications/general/voip/axivox/manage_users.rst:292 -msgid ":guilabel:`Music on hold management`" -msgstr "" - -#: ../../content/applications/general/voip/axivox/manage_users.rst:293 -msgid ":guilabel:`Directory management`" -msgstr "" - -#: ../../content/applications/general/voip/axivox/manage_users.rst:294 -msgid ":guilabel:`Call list`" -msgstr "" - -#: ../../content/applications/general/voip/axivox/manage_users.rst:295 -msgid ":guilabel:`Connected user list`" -msgstr "" - -#: ../../content/applications/general/voip/axivox/manage_users.rst:296 -msgid ":guilabel:`Global settings`" -msgstr "" - -#: ../../content/applications/general/voip/axivox/manage_users.rst:297 -msgid ":guilabel:`Apply changes button`" -msgstr "" - -#: ../../content/applications/general/voip/axivox/manage_users.rst:298 -msgid ":guilabel:`Invoice download`" -msgstr "" - -#: ../../content/applications/general/voip/axivox/manage_users.rst:299 -msgid ":guilabel:`Invoice details`" -msgstr "" - -#: ../../content/applications/general/voip/axivox/manage_users.rst:300 -msgid ":guilabel:`Blacklist management`" -msgstr "" - -#: ../../content/applications/general/voip/axivox/manage_users.rst:301 -msgid ":guilabel:`Conference participant management`" -msgstr "" - -#: ../../content/applications/general/voip/axivox/manage_users.rst:303 -msgid "To access credentials for the Axivox user portal, navigate to the top of the :menuselection:`Permissions` tab. Then, copy the :guilabel:`Username`, and enter the correct :guilabel:`Password` for the individual user. There is a minimum of 8 characters for a user password." -msgstr "" - -#: ../../content/applications/general/voip/axivox/manage_users.rst:309 -msgid "These are the same permissions granted to the Axivox administrator that are listed in the menu on the left in the Axivox management console. Should a selection state :guilabel:`No`, or :guilabel:`No access`, then the menu option does **not** populate for the user." -msgstr "" - -#: ../../content/applications/general/voip/axivox/manage_users.rst:316 -msgid "Upon finishing the setup for a new user, an :ref:`voip/axivox/incoming_number` can be linked." -msgstr "" - -#: ../../content/applications/general/voip/axivox/manage_users.rst:-1 -msgid "Manage a user page, with the permissions tab highlighted, along with the first permission\n" -"highlighted indicating a no selection." -msgstr "" - -#: ../../content/applications/general/voip/axivox/manage_users.rst:326 -msgid "User groups" -msgstr "" - -#: ../../content/applications/general/voip/axivox/manage_users.rst:328 -msgid "A user group is a grouping of Axivox users that can be linked to a queue for call center capability." -msgstr "" - -#: ../../content/applications/general/voip/axivox/manage_users.rst:331 -msgid "To begin using user groups, navigate to `https://manage.axivox.com `_." -msgstr "" - -#: ../../content/applications/general/voip/axivox/manage_users.rst:333 -msgid "Then, log in with the appropriate administrator credentials. From the menu on the left of the Axivox administrative panel, click into :guilabel:`User Groups`." -msgstr "" - -#: ../../content/applications/general/voip/axivox/manage_users.rst:336 -msgid "To add a user group from the :guilabel:`User Groups` page, click :guilabel:`Add a group`." -msgstr "" - -#: ../../content/applications/general/voip/axivox/manage_users.rst:338 -msgid "Next, name the group, by entering text into the :guilabel:`Name` field. Then, add a member to the group by typing the first few letters of the user's name into the :guilabel:`Members` field. The user populates in a drop-down menu below the field. Then, click on the desired user, and they are added to the user group." -msgstr "" - -#: ../../content/applications/general/voip/axivox/manage_users.rst:343 -msgid "Repeat this process to add more users to the group." -msgstr "" - -#: ../../content/applications/general/voip/axivox/vm_audio_messages.rst:3 -msgid "Voicemails and audio messages" -msgstr "" - -#: ../../content/applications/general/voip/axivox/vm_audio_messages.rst:7 -msgid "Managing voicemail is an important part of any business. A company needs to access their messages with ease, and stay on top of any missed calls. Recording audio messages, like thanking a caller for reaching out, or directing them to the right extension, is also a great way to personalize the business interaction, and set the tone with the customer." -msgstr "" - -#: ../../content/applications/general/voip/axivox/vm_audio_messages.rst:12 -msgid "This document covers the configuration of both voicemail and audio messages in the Axivox administrative portal." -msgstr "" - -#: ../../content/applications/general/voip/axivox/vm_audio_messages.rst:18 -msgid "Set global language" -msgstr "" - -#: ../../content/applications/general/voip/axivox/vm_audio_messages.rst:20 -msgid "To start using voicemails and audio messages with Axivox, the global language should be set in the Axivox admin portal settings. To do that, navigate to `manage.axivox.com `_. After logging into the portal, go to :menuselection:`Settings --> Global language (e.g.: voicemail messages,...)`." -msgstr "" - -#: ../../content/applications/general/voip/axivox/vm_audio_messages.rst:25 -msgid "From here, set the language to either: :guilabel:`Francais`, :guilabel:`English`, :guilabel:`Espanol`, or :guilabel:`Deutsch`." -msgstr "" - -#: ../../content/applications/general/voip/axivox/vm_audio_messages.rst:28 -msgid "Then, click :guilabel:`Save`, followed by :guilabel:`Apply changes` in the upper-right corner of the :guilabel:`General Settings` page to implement the change into production." -msgstr "" - -#: ../../content/applications/general/voip/axivox/vm_audio_messages.rst:34 -msgid "Activate voicemail" -msgstr "" - -#: ../../content/applications/general/voip/axivox/vm_audio_messages.rst:36 -msgid "In order for a user to utilize voicemail in Axivox, the voicemail feature **must** be turned on in the Axivox administrative portal. To begin using voicemail with a user, navigate to `manage.axivox.com `_. Then, log in with the appropriate administrator credentials." -msgstr "" - -#: ../../content/applications/general/voip/axivox/vm_audio_messages.rst:40 -msgid "On the left menu of the Axivox administrative panel, click into :guilabel:`Users`." -msgstr "" - -#: ../../content/applications/general/voip/axivox/vm_audio_messages.rst:42 -msgid "Then, click into the specific user the voicemail should be activated for. Under the section marked, :guilabel:`Voicemail`, open the drop-down menu, and click on :guilabel:`Yes`." -msgstr "" - -#: ../../content/applications/general/voip/axivox/vm_audio_messages.rst:45 -msgid "Lastly, :guilabel:`Save` the change, then click :guilabel:`Apply changes` in the upper-right corner of the screen." -msgstr "" - -#: ../../content/applications/general/voip/axivox/vm_audio_messages.rst:49 -msgid "Voicemail" -msgstr "" - -#: ../../content/applications/general/voip/axivox/vm_audio_messages.rst:51 -msgid "The next step is to set up the individual voicemail boxes on the Axivox administrative portal. To access the portal, visit `manage.axivox.com `_ and log in. Then, navigate to :menuselection:`Voicemails`, located in the menu on the left." -msgstr "" - -#: ../../content/applications/general/voip/axivox/vm_audio_messages.rst:55 -msgid "If the voicemail option was activated in the user profile, using this process :ref:`voip/axivox/activate_voicemail`, then a voicemail is automatically created on the :guilabel:`Voicemails` page." -msgstr "" - -#: ../../content/applications/general/voip/axivox/vm_audio_messages.rst:60 -msgid "It should be noted that some of the administrative portal language is in French, as Axivox is a Belgian company. The global language is still set to one of the four options as seen here: :ref:`voip/axivox/global_language`." -msgstr "" - -#: ../../content/applications/general/voip/axivox/vm_audio_messages.rst:65 -msgid "Manually create voicemail" -msgstr "" - -#: ../../content/applications/general/voip/axivox/vm_audio_messages.rst:67 -msgid "To manually create a new voicemail box, click :guilabel:`Add a voicemail` on the :guilabel:`Voicemails` page. Or, edit an existing voicemail box, by clicking :guilabel:`Edit` to the far-right of an existing voicemail box on the :guilabel:`Voicemails` page." -msgstr "" - -#: ../../content/applications/general/voip/axivox/vm_audio_messages.rst:72 -msgid "Suppose a sales or support team needs a general voicemail box. The voicemail would need to be created manually, and attached to an incoming number." -msgstr "" - -#: ../../content/applications/general/voip/axivox/vm_audio_messages.rst:75 -msgid "The new, manually-created voicemail box should be attached to an incoming number, so it can receive messages. To do so, navigate to :menuselection:`Incoming numbers`, located in the menu on the left. Then, click :guilabel:`Edit` to the far-right of the specific number the voicemail should be linked to." -msgstr "" - -#: ../../content/applications/general/voip/axivox/vm_audio_messages.rst:80 -msgid "In the :guilabel:`Destination type for voice call` field, click the drop-down menu, and select :guilabel:`Voicemail`. Then, open the drop-down menu on the next line labeled, :guilabel:`Voicemail`, and select the manually-created voicemail box." -msgstr "" - -#: ../../content/applications/general/voip/axivox/vm_audio_messages.rst:85 -msgid "If an incoming number is capable of receiving SMS/text messages, an additional field, :guilabel:`Destination email address for Incoming SMS`, is present." -msgstr "" - -#: ../../content/applications/general/voip/axivox/vm_audio_messages.rst:88 -msgid "To determine whether an incoming number is capable of receiving SMS/text messages, click :guilabel:`Incoming numbers` from the menu on the left, then check the :guilabel:`SMS compatible` column for the incoming number." -msgstr "" - -#: ../../content/applications/general/voip/axivox/vm_audio_messages.rst:92 -msgid "Then, if applicable, in the field labeled, :guilabel:`Destination email address for Incoming SMS`, enter an email to which incoming text messages sent to the incoming number can be received. Some incoming numbers (US +1) in Axivox are capable of receiving text messages from individuals and automated numbers." -msgstr "" - -#: ../../content/applications/general/voip/axivox/vm_audio_messages.rst:97 -msgid "Should this field be left empty, the default destination address is used, instead (as previously set in the beginning of the process for manually creating a voicemail)." -msgstr "" - -#: ../../content/applications/general/voip/axivox/vm_audio_messages.rst:100 -msgid "Once all desired configurations are complete, click :guilabel:`Save`, then click :guilabel:`Apply changes` in the upper-right corner of the screen to implement the change into production." -msgstr "" - -#: ../../content/applications/general/voip/axivox/vm_audio_messages.rst:104 -msgid "Notifications" -msgstr "" - -#: ../../content/applications/general/voip/axivox/vm_audio_messages.rst:106 -msgid "Now, whenever a voicemail is received on any of the automatically pre-configured or manually-linked voicemail boxes, an email is sent to the user's email address, as listed in the :guilabel:`Voicemails` page, or in the user's Axivox profile." -msgstr "" - -#: ../../content/applications/general/voip/axivox/vm_audio_messages.rst:110 -msgid "This information can be accessed by navigating to :menuselection:`Users` in the left menu, and clicking :guilabel:`Edit` next to the specific user in question." -msgstr "" - -#: ../../content/applications/general/voip/axivox/vm_audio_messages.rst:116 -msgid "Forwarding to voicemail" -msgstr "" - -#: ../../content/applications/general/voip/axivox/vm_audio_messages.rst:118 -msgid "In Axivox, there are also numerous forwarding settings for a user. To access these forwarding settings, go to `manage.axivox.com `_ and log in." -msgstr "" - -#: ../../content/applications/general/voip/axivox/vm_audio_messages.rst:121 -msgid "Next, navigate to :menuselection:`Users`, located in the menu on the left." -msgstr "" - -#: ../../content/applications/general/voip/axivox/vm_audio_messages.rst:123 -msgid "From there, click into the specific user the forwarding should be added to. Then, open the :guilabel:`Forwardings` tab." -msgstr "" - -#: ../../content/applications/general/voip/axivox/vm_audio_messages.rst:126 -msgid "If the user is busy on another call, or away from the phone, there is an option present in this tab to :guilabel:`Send to voicemail as a last resort`, located in the :guilabel:`Forwarding on no answer` and :guilabel:`Forwarding on busy` fields." -msgstr "" - -#: ../../content/applications/general/voip/axivox/vm_audio_messages.rst:-1 -msgid "Send to voicemail as a last resort options highlighted on the Forwardings tab of the user." -msgstr "" - -#: ../../content/applications/general/voip/axivox/vm_audio_messages.rst:134 -msgid "If the :guilabel:`Send to voicemail as a last resort` box is ticked, when the forwarding actions stated in each section are not successful, the caller is routed to the voicemail set on the particular user." -msgstr "" - -#: ../../content/applications/general/voip/axivox/vm_audio_messages.rst:139 -msgid "For more information on forwarding and transfers, visit :ref:`voip/axivox/forwardings_tab`." -msgstr "" - -#: ../../content/applications/general/voip/axivox/vm_audio_messages.rst:141 -msgid "When all the desired configurations are complete, click :guilabel:`Save`, then click :guilabel:`Apply changes` in the upper-right corner of the screen to implement the change." -msgstr "" - -#: ../../content/applications/general/voip/axivox/vm_audio_messages.rst:147 -msgid "Audio messages" -msgstr "" - -#: ../../content/applications/general/voip/axivox/vm_audio_messages.rst:149 -msgid "It is possible to add audio messages *before* a customer's call is even taken, to inform them about the waiting time for deliveries, the availability of a product, or any other important promotional messages." -msgstr "" - -#: ../../content/applications/general/voip/axivox/vm_audio_messages.rst:153 -msgid "To record an audio message in Axivox, navigate to `manage.axivox.com `_ and log in." -msgstr "" - -#: ../../content/applications/general/voip/axivox/vm_audio_messages.rst:155 -msgid "Next, click on :guilabel:`Audio messages` in the menu on the left. From the :guilabel:`Audio messages` page, click :guilabel:`Add a message`." -msgstr "" - -#: ../../content/applications/general/voip/axivox/vm_audio_messages.rst:158 -msgid "Type in a :guilabel:`Name`, and click :guilabel:`Save`." -msgstr "" - -#: ../../content/applications/general/voip/axivox/vm_audio_messages.rst:160 -msgid "Upon clicking :guilabel:`Save`, the browser redirects back to the main :guilabel:`Audio messages` page, where the newly-created message can be found on the list." -msgstr "" - -#: ../../content/applications/general/voip/axivox/vm_audio_messages.rst:163 -msgid "There are two different ways to make the audio message. The user could either record the message over the phone, or type the message (in text), and select a computer-generated speaker to read the message." -msgstr "" - -#: ../../content/applications/general/voip/axivox/vm_audio_messages.rst:168 -msgid "Record audio message" -msgstr "" - -#: ../../content/applications/general/voip/axivox/vm_audio_messages.rst:170 -msgid "To record an audio message over the phone, click the orange button labeled, :guilabel:`Record/Listen`, located to the right of the desired message on the list to record, on the :guilabel:`Audio messages` page." -msgstr "" - -#: ../../content/applications/general/voip/axivox/vm_audio_messages.rst:174 -msgid "When clicked, a :guilabel:`Record / listen to a message` pop-up window appears. From here, the message is then recorded, via one of the extensions that is associated with the user. Under :guilabel:`Extension to use for message management` field, click the drop-down menu, and select the extension where Axivox should call to record the message." -msgstr "" - -#: ../../content/applications/general/voip/axivox/vm_audio_messages.rst:179 -msgid "Then, click :guilabel:`OK` to begin the call." -msgstr "" - -#: ../../content/applications/general/voip/axivox/vm_audio_messages.rst:182 -msgid "The user **must** be active in the production database with :abbr:`VoIP (Voice over Internet Protocol)` configured. To configure :abbr:`VoIP (Voice over Internet Protocol)` for a user, see this documentation: :doc:`axivox_config`." -msgstr "" - -#: ../../content/applications/general/voip/axivox/vm_audio_messages.rst:186 -msgid "Upon connecting to the Axivox audio recorder management line, a recorded French-speaking operator provides the following options:" -msgstr "" - -#: ../../content/applications/general/voip/axivox/vm_audio_messages.rst:189 -#: ../../content/applications/general/voip/axivox/vm_audio_messages.rst:199 -msgid "Press `1` to record a message." -msgstr "" - -#: ../../content/applications/general/voip/axivox/vm_audio_messages.rst:190 -#: ../../content/applications/general/voip/axivox/vm_audio_messages.rst:200 -msgid "Press `2` to listen to the current message." -msgstr "" - -#: ../../content/applications/general/voip/axivox/vm_audio_messages.rst:192 -msgid "Press either `1` or `2`, depending on whether or not there is already a message present in the system for this particular audio message that requires a review, before recording a new one." -msgstr "" - -#: ../../content/applications/general/voip/axivox/vm_audio_messages.rst:195 -msgid "Record the new audio message after pressing `1`, then press `#` to end the recording." -msgstr "" - -#: ../../content/applications/general/voip/axivox/vm_audio_messages.rst:197 -msgid "The French-speaking operator returns to the line presenting the first set of questions again:" -msgstr "" - -#: ../../content/applications/general/voip/axivox/vm_audio_messages.rst:202 -msgid "Press `#` to end the call." -msgstr "" - -#: ../../content/applications/general/voip/axivox/vm_audio_messages.rst:205 -msgid "Write audio message" -msgstr "" - -#: ../../content/applications/general/voip/axivox/vm_audio_messages.rst:207 -msgid "To type the message, and select a computerized speaker to say the text, navigate to the :menuselection:`Audio messages` in the menu on the left." -msgstr "" - -#: ../../content/applications/general/voip/axivox/vm_audio_messages.rst:210 -msgid "From the :guilabel:`Audio messages` page, select the blue button labeled, :guilabel:`Text message`, next to the corresponding audio message :guilabel:`Name` that the message should be attached to." -msgstr "" - -#: ../../content/applications/general/voip/axivox/vm_audio_messages.rst:213 -msgid "Doing so reveals a :guilabel:`Convert text to message` pop-up window." -msgstr "" - -#: ../../content/applications/general/voip/axivox/vm_audio_messages.rst:215 -msgid "From the :guilabel:`Convert to text message` pop-up window, click the drop-down menu next to the field labeled, :guilabel:`Voice`, and select an option for the :guilabel:`Text` to be read in." -msgstr "" - -#: ../../content/applications/general/voip/axivox/vm_audio_messages.rst:218 -msgid "After the :guilabel:`Voice` selection has been made, and the message has been written in the :guilabel:`Text` field, click :guilabel:`Generate` to process the audio file." -msgstr "" - -#: ../../content/applications/general/voip/axivox/vm_audio_messages.rst:221 -msgid "The text is read in the same language it is written in the :guilabel:`Text` field. Should the language differ in the :guilabel:`Voice` field, then an accent is used by the computerized speaker." -msgstr "" - -#: ../../content/applications/general/voip/axivox/vm_audio_messages.rst:224 -msgid "Finally, when these steps are complete, click :guilabel:`Save` to save the audio message." -msgstr "" - -#: ../../content/applications/general/voip/axivox/vm_audio_messages.rst:226 -msgid "To implement the changes, click :guilabel:`Apply changes` in the upper-right corner of the screen." -msgstr "" - -#: ../../content/applications/general/voip/axivox/vm_audio_messages.rst:-1 -msgid "Convert text to message window with voice, text, generate button and save highlighted." -msgstr "" - -#: ../../content/applications/general/voip/axivox/vm_audio_messages.rst:233 -msgid "To set a greeting or audio message in a dial plan element double-click on the element. This could be a :guilabel:`Play a file` element, or a :guilabel:`Menu` element, in which the caller should encounter an urgent message, or a dial-by-number directory." -msgstr "" - -#: ../../content/applications/general/voip/axivox/vm_audio_messages.rst:237 -msgid "For more information on dial plans see this documentation: :doc:`dial_plan_basics` or :doc:`dial_plan_advanced`." -msgstr "" - -#: ../../content/applications/general/voip/axivox/vm_audio_messages.rst:243 -msgid "Music on-hold" -msgstr "" - -#: ../../content/applications/general/voip/axivox/vm_audio_messages.rst:245 -msgid "Axivox has the option to add custom hold music to the call whenever a caller is waiting for their call to be answered. To add hold music to the Axivox administrative portal, navigate to the `manage.axivox.com `_, and log in." -msgstr "" - -#: ../../content/applications/general/voip/axivox/vm_audio_messages.rst:249 -msgid "Then, click on :guilabel:`Music on hold` from the menu on the left, and a :guilabel:`Change the music on hold` pop-up window appears." -msgstr "" - -#: ../../content/applications/general/voip/axivox/vm_audio_messages.rst:252 -msgid "On the :guilabel:`Change the music on hold` pop-up window, click the :guilabel:`Choose File` button to select an MP3 (MPEG Audio Layer 3) or WAV (Waveform Audio File Format ) file to be uploaded." -msgstr "" - -#: ../../content/applications/general/voip/axivox/vm_audio_messages.rst:256 -msgid "Only :abbr:`MP3 (MPEG Audio Layer 3)` or :abbr:`WAV (Waveform Audio File Format)` files can be uploaded to the Axivox administrative portal." -msgstr "" - -#: ../../content/applications/general/voip/axivox/vm_audio_messages.rst:259 -msgid "Once the file is selected, the :guilabel:`Progression` bar shows an upload status. When this activity completes, the window can be closed, by clicking :guilabel:`Close`." -msgstr "" - -#: ../../content/applications/general/voip/axivox/vm_audio_messages.rst:262 -msgid "When the desired changes are complete, click :guilabel:`Apply changes` in the upper-right corner of the screen." -msgstr "" - -#: ../../content/applications/general/voip/devices_integrations.rst:3 -msgid "Devices and integrations" -msgstr "" - -#: ../../content/applications/general/voip/devices_integrations.rst:5 -msgid ":abbr:`VoIP (Voice over Internet Protocol)` can be used on many different devices, such as a computer, tablet, mobile phone, and many more. This is helpful in that it reduces costs, and employees can work from anywhere in the world, so long as they have a broadband internet connection." -msgstr "" - -#: ../../content/applications/general/voip/devices_integrations.rst:9 -msgid "Odoo *VoIP* is SIP (Session Initiation Protocol) compatible, which means it can be used with *any* :abbr:`SIP (Session Initiation Protocol)` compatible application." -msgstr "" - -#: ../../content/applications/general/voip/devices_integrations.rst:12 -msgid "This document covers the process of setting up Odoo *VoIP* across different devices and integrations." -msgstr "" - -#: ../../content/applications/general/voip/devices_integrations.rst:15 -msgid "Odoo is fully-integrated with all Odoo apps, allowing users to click into any app, and schedule a call as an activity in the chatter." -msgstr "" - -#: ../../content/applications/general/voip/devices_integrations.rst:19 -msgid "For example, in the *CRM* app, a user can click into an opportunity, and click on :guilabel:`Activities` in the chatter." -msgstr "" - -#: ../../content/applications/general/voip/devices_integrations.rst:22 -msgid "Next, they can choose :guilabel:`Call`, and under :guilabel:`Due Date`, they can select a date." -msgstr "" - -#: ../../content/applications/general/voip/devices_integrations.rst:24 -msgid "Once they click :guilabel:`Save`, an activity shows up in the chatter." -msgstr "" - -#: ../../content/applications/general/voip/devices_integrations.rst:26 -msgid "Should the :guilabel:`Due Date` be for today's date, the activity shows up in the :abbr:`VoIP (Voice over Internet Protocol)` widget." -msgstr "" - -#: ../../content/applications/general/voip/devices_integrations.rst:0 -msgid "View of CRM leads and the option to schedule an activity for Odoo Discuss." -msgstr "" - -#: ../../content/applications/general/voip/devices_integrations.rst:34 -msgid "Odoo VoIP (laptop/desktop computer)" -msgstr "" - -#: ../../content/applications/general/voip/devices_integrations.rst:36 -msgid "The Odoo *VoIP* (Voice over Internet Protocol) module and widget can be used from any browser on a laptop or desktop device. Simply click on the :guilabel:`☎️ (phone)` icon in the upper-right corner, while in the Odoo database, and the widget appears." -msgstr "" - -#: ../../content/applications/general/voip/devices_integrations.rst:41 -msgid "To see how to use the :abbr:`VoIP (Voice over Internet Protocol)` widget on a desktop/laptop computer, check out this documentation: :doc:`voip_widget`." -msgstr "" - -#: ../../content/applications/general/voip/devices_integrations.rst:45 -msgid "Odoo VoIP (tablet/mobile device)" -msgstr "" - -#: ../../content/applications/general/voip/devices_integrations.rst:47 -msgid "The Odoo *VoIP* app can be used on tablets and mobile phones, through the Odoo Android or Apple IOS applications. Additionally, a mobile web browser can be used to access the database." -msgstr "" - -#: ../../content/applications/general/voip/devices_integrations.rst:51 -msgid "Odoo Android and Apple IOS applications are no longer being maintained by Odoo on the Android and Apple portals. This means Odoo support only handles limited scopes of Odoo Android or Apple IOS support tickets." -msgstr "" - -#: ../../content/applications/general/voip/devices_integrations.rst:56 -msgid "While outgoing calls can be placed using Odoo on a mobile device, be aware that Odoo is **not** a full :abbr:`VoIP (Voice over Internet Protocol)` application, and does **not** ring on incoming calls. If the user needs to be reachable on a mobile device at all times, an app, like Zoiper, should be used. Apps like that stay connected in the background at all times." -msgstr "" - -#: ../../content/applications/general/voip/devices_integrations.rst:61 -msgid "For more information, see this documentation: :ref:`voip/zoiper`." -msgstr "" - -#: ../../content/applications/general/voip/devices_integrations.rst:63 -msgid "While in the mobile application on a mobile device/tablet, access the Odoo *VoIP* widget, by tapping on the :guilabel:`☎️ (phone)` icon in the upper-right corner. The widget appears in the lower-left corner." -msgstr "" - -#: ../../content/applications/general/voip/devices_integrations.rst:67 -msgid "When first making a call from the tablet using the mobile application, the user is prompted to :guilabel:`Allow` the database to use the microphone. Click :guilabel:`Allow` when prompted to continue with the call using the microphone." -msgstr "" - -#: ../../content/applications/general/voip/devices_integrations.rst:71 -msgid "This step is **necessary**, whether using the mobile Odoo application or web browser." -msgstr "" - -#: ../../content/applications/general/voip/devices_integrations.rst:-1 -msgid "Allow the database to access the microphone." -msgstr "" - -#: ../../content/applications/general/voip/devices_integrations.rst:77 -msgid "Odoo then asks how to make the call. The two options are : :guilabel:`VOIP` or :guilabel:`Phone` (should the tablet be enabled for calling). Click the box next to :guilabel:`Remember ?` should this decision be the default moving forward." -msgstr "" - -#: ../../content/applications/general/voip/devices_integrations.rst:-1 -msgid "Window prompt to choose whether to use VOIP or the devices phone to make the call." -msgstr "" - -#: ../../content/applications/general/voip/devices_integrations.rst:85 -msgid "Here is the layout of what the Odoo *VoIP* app looks like on a mobile device:" -msgstr "" - -#: ../../content/applications/general/voip/devices_integrations.rst:-1 -msgid "Layout of what the VoIP app looks like on the a mobile device." -msgstr "" - -#: ../../content/applications/general/voip/devices_integrations.rst:94 -msgid "Zoiper Lite" -msgstr "" - -#: ../../content/applications/general/voip/devices_integrations.rst:96 -msgid "*Zoiper Lite* is a free :abbr:`VoIP (Voice over Internet Protocol)` :abbr:`SIP (Session Initiation Protocol)` dialer with voice and video." -msgstr "" - -#: ../../content/applications/general/voip/devices_integrations.rst:99 -msgid "To start using the *Zoiper* app, download it to the device, via the `Zoiper download page `_." -msgstr "" - -#: ../../content/applications/general/voip/devices_integrations.rst:102 -msgid "A mobile device is the most common installation, and this document covers how to set up on the *Zoiper* IOS application. Screenshots and steps may differ depending on the set up conditions." -msgstr "" - -#: ../../content/applications/general/voip/devices_integrations.rst:105 -msgid "After installing the *Zoiper* application on the mobile phone, open the application, and tap on :guilabel:`Settings`. Navigate to :menuselection:`Accounts`, and tap on the :guilabel:`+ (plus)` icon to add an account." -msgstr "" - -#: ../../content/applications/general/voip/devices_integrations.rst:109 -msgid "If the :abbr:`VoIP (Voice over Internet Protocol)` account is already set up, then click :guilabel:`Yes`. This means an account username and password has already been produced." -msgstr "" - -#: ../../content/applications/general/voip/devices_integrations.rst:-1 -msgid "Zoiper account setup, shown in the view from a mobile device." -msgstr "" - -#: ../../content/applications/general/voip/devices_integrations.rst:116 -msgid "Next, tap on :guilabel:`Select a provider`. On the screen that populates, tap :guilabel:`Country`, in the upper-right corner, to narrow the providers down to a specific country. Choose the country for the provider that is being configured, then find the :guilabel:`Provider`, and select it." -msgstr "" - -#: ../../content/applications/general/voip/devices_integrations.rst:121 -msgid "If the provider being configured is *Axivox*, then select :guilabel:`Belgium`. Then, choose :guilabel:`Axivox` as the provider." -msgstr "" - -#: ../../content/applications/general/voip/devices_integrations.rst:-1 -msgid "Zoiper account setup, choosing the provider." -msgstr "" - -#: ../../content/applications/general/voip/devices_integrations.rst:128 -msgid "Under :abbr:`SIP (Session Initiation Protocol)` options, enter the :guilabel:`Account name`, :guilabel:`Domain`, :guilabel:`Username`, and :guilabel:`Password`. All this information varies, based on the account." -msgstr "" - -#: ../../content/applications/general/voip/devices_integrations.rst:133 -msgid "To access this information, via the *Axivox* portal, navigate to :menuselection:`Users --> Choose user --> Edit --> SIP Identifiers tab`. The :guilabel:`SIP username`, :guilabel:`Domain`, :guilabel:`SIP password`, and :guilabel:`Address of the proxy server` are all present in this tab." -msgstr "" - -#: ../../content/applications/general/voip/devices_integrations.rst:141 -msgid "Zoiper Field" -msgstr "" - -#: ../../content/applications/general/voip/devices_integrations.rst:142 -msgid "Axivox Field" -msgstr "" - -#: ../../content/applications/general/voip/devices_integrations.rst:143 -msgid "Account name" -msgstr "" - -#: ../../content/applications/general/voip/devices_integrations.rst:144 -msgid "*Can be anything*" -msgstr "" - -#: ../../content/applications/general/voip/devices_integrations.rst:145 -#: ../../content/applications/general/voip/devices_integrations.rst:146 -msgid "Domain" -msgstr "" - -#: ../../content/applications/general/voip/devices_integrations.rst:147 -msgid "Username" -msgstr "" - -#: ../../content/applications/general/voip/devices_integrations.rst:148 -msgid "SIP username" -msgstr "" - -#: ../../content/applications/general/voip/devices_integrations.rst:149 -msgid "Password" -msgstr "" - -#: ../../content/applications/general/voip/devices_integrations.rst:150 -msgid "SIP password" -msgstr "" - -#: ../../content/applications/general/voip/devices_integrations.rst:152 -msgid "Once this account information is entered, click the green :guilabel:`Register` button at the top of the screen. Once the registration information is checked, *Zoiper* populates a message, stating :guilabel:`Registration Status: OK`." -msgstr "" - -#: ../../content/applications/general/voip/devices_integrations.rst:156 -msgid "At this point, *Zoiper* is now set up to make phone calls using the :abbr:`VoIP (Voice over Internet Protocol)` service." -msgstr "" - -#: ../../content/applications/general/voip/devices_integrations.rst:-1 -msgid "Zoiper account setup, registration successful." -msgstr "" - -#: ../../content/applications/general/voip/devices_integrations.rst:164 -msgid "Linphone" -msgstr "" - -#: ../../content/applications/general/voip/devices_integrations.rst:166 -msgid "*Linphone* is an open-source :abbr:`VoIP (Voice over Internet Protocol)` :abbr:`SIP (Session Initiation Protocol)` softphone, used for voice, video, messaging (group and individual), as well as conference calls." -msgstr "" - -#: ../../content/applications/general/voip/devices_integrations.rst:170 -msgid "To start using the *Linphone* app, download it to the device, via the `Linphone download page `_." -msgstr "" - -#: ../../content/applications/general/voip/devices_integrations.rst:173 -msgid "A mobile device is the most common installation, and this document covers how to set up the *Linphone* IOS application. Screenshots and steps may differ depending on the circumstances." -msgstr "" - -#: ../../content/applications/general/voip/devices_integrations.rst:176 -msgid "To begin configuring *Linphone* for use with a :abbr:`SIP (Session Initiation Protocol)` provider, first open *Linphone*, and an assistant screen appears." -msgstr "" - -#: ../../content/applications/general/voip/devices_integrations.rst:179 -msgid "From this screen, select :guilabel:`Use SIP Account`. Then, on the following screen, enter the :guilabel:`Username`, :guilabel:`Password`, :guilabel:`Domain`, and :guilabel:`Display Name`. Once complete, press :guilabel:`Login`." -msgstr "" - -#: ../../content/applications/general/voip/devices_integrations.rst:183 -msgid "At this point, *Linphone* is ready to start making calls, once there is a green button at the top of the application screen that reads, :guilabel:`Connected`." -msgstr "" - -#: ../../content/applications/general/voip/devices_integrations.rst:-1 -msgid "Linphone account setup, registration successful." -msgstr "" - -#: ../../content/applications/general/voip/devices_integrations.rst:191 -msgid "*Linphone* makes a variety of applications for mobile and desktop devices in operating systems, such as Windows, Linux, Apple, and Android. Because *Linphone* is an open-source project, many new updates are released on a regular basis." -msgstr "" - -#: ../../content/applications/general/voip/devices_integrations.rst:195 -msgid "See `Linphone's wiki-documentation page `_." -msgstr "" - -#: ../../content/applications/general/voip/onsip.rst:3 -msgid "Use VoIP services in Odoo with OnSIP" -msgstr "" - -#: ../../content/applications/general/voip/onsip.rst:8 -msgid "Odoo *VoIP* can be set up to work together with `OnSIP `_. OnSIP is a VoIP provider. An account is needed with OnSIP in order to use this service." -msgstr "" - -#: ../../content/applications/general/voip/onsip.rst:11 -msgid "Before setting up an account with OnSIP, make sure the company's home area, and the areas that will be called, are covered by OnSIP services." -msgstr "" - -#: ../../content/applications/general/voip/onsip.rst:14 -msgid "After opening an OnSIP account, follow the configuration procedure below to configure it on an Odoo database." -msgstr "" - -#: ../../content/applications/general/voip/onsip.rst:20 -msgid "To configure the Odoo database to connect to OnSIP services, first navigate to the :menuselection:`Apps application` from the main Odoo dashboard. Then, remove the default `Apps` filter from the :guilabel:`Search...` bar, and search for `OnSIP`." -msgstr "" - -#: ../../content/applications/general/voip/onsip.rst:24 -msgid "Next, activate the :guilabel:`VOIP OnSIP` module." -msgstr "" - -#: ../../content/applications/general/voip/onsip.rst:-1 -msgid "View of OnSIP app in the app search results." -msgstr "" - -#: ../../content/applications/general/voip/onsip.rst:31 -msgid "Odoo VoIP setting" -msgstr "" - -#: ../../content/applications/general/voip/onsip.rst:33 -msgid "After installing the *VOIP OnSIP* module, go to the :menuselection:`Settings app`, scroll down to the :guilabel:`Integrations` section, and locate the :guilabel:`Asterisk (VoIP)` fields. Then, proceed to fill in those three fields with the following information:" -msgstr "" - -#: ../../content/applications/general/voip/onsip.rst:37 -msgid ":guilabel:`OnSIP Domain`: the domain that was assigned when creating an account on `OnSIP `_." -msgstr "" - -#: ../../content/applications/general/voip/onsip.rst:39 -msgid ":guilabel:`WebSocket`: `wss://edge.sip.onsip.com`" -msgstr "" - -#: ../../content/applications/general/voip/onsip.rst:40 -msgid ":guilabel:`VoIP Environment`: :guilabel:`Production`" -msgstr "" - -#: ../../content/applications/general/voip/onsip.rst:-1 -msgid "VoIP configuration settings in Odoo Settings app." -msgstr "" - -#: ../../content/applications/general/voip/onsip.rst:47 -msgid "To access the OnSIP domain, navigate to `OnSIP `_ and log in. Then, click the :guilabel:`Administrators` link in the top-right of the page." -msgstr "" - -#: ../../content/applications/general/voip/onsip.rst:50 -msgid "Next, in the left menu, click :guilabel:`Users`, and then select any user. By default, the selected user opens on the :guilabel:`User Info` tab." -msgstr "" - -#: ../../content/applications/general/voip/onsip.rst:53 -msgid "Click on the :guilabel:`Phone Settings` tab to reveal OnSIP configuration credentials (first column)." -msgstr "" - -#: ../../content/applications/general/voip/onsip.rst:0 -msgid "Domain setting revealed (highlighted) on administrative panel of OnSIP management\n" -"console." -msgstr "" - -#: ../../content/applications/general/voip/onsip.rst:62 -msgid "Odoo user setting" -msgstr "" - -#: ../../content/applications/general/voip/onsip.rst:64 -msgid "Next, the user needs to be set up in Odoo. Every user associated with an OnSIP user **must** also be configured in the Odoo user's settings/preferences." -msgstr "" - -#: ../../content/applications/general/voip/onsip.rst:67 -msgid "To do that, navigate to :menuselection:`Settings app --> Manage Users --> Select the User`." -msgstr "" - -#: ../../content/applications/general/voip/onsip.rst:69 -msgid "On the user form, click :guilabel:`Edit` to configure the user's OnSIP account. Then, click the :guilabel:`Preferences` tab, and scroll to the :guilabel:`VoIP Configuration` section." -msgstr "" - -#: ../../content/applications/general/voip/onsip.rst:72 -msgid "In this section, fill in the fields with OnSIP credentials." -msgstr "" - -#: ../../content/applications/general/voip/onsip.rst:74 -msgid "Fill in the following fields with the associated credentials listed below:" -msgstr "" - -#: ../../content/applications/general/voip/onsip.rst:76 -msgid ":guilabel:`Voip Username` = OnSIP :guilabel:`Username`" -msgstr "" - -#: ../../content/applications/general/voip/onsip.rst:77 -msgid ":guilabel:`OnSIP Auth Username` = OnSIP :guilabel:`Auth Username`" -msgstr "" - -#: ../../content/applications/general/voip/onsip.rst:78 -msgid ":guilabel:`VoIP Secret` = OnSIP :guilabel:`SIP Password`" -msgstr "" - -#: ../../content/applications/general/voip/onsip.rst:79 -msgid ":guilabel:`External Device Number` = OnSIP :guilabel:`Ext.` (extension without the `x`)" -msgstr "" - -#: ../../content/applications/general/voip/onsip.rst:-1 -msgid "OnSIP user credentials with username, auth username, SIP password, and extension\n" -"highlighted." -msgstr "" - -#: ../../content/applications/general/voip/onsip.rst:87 -msgid "The OnSIP extension can be found in the *User* banner line above the tabs." -msgstr "" - -#: ../../content/applications/general/voip/onsip.rst:89 -msgid "When these steps are complete, navigate away from the user form in Odoo to save the configurations." -msgstr "" - -#: ../../content/applications/general/voip/onsip.rst:91 -msgid "Once saved, Odoo users can make phone calls by clicking the :guilabel:`☎️ (phone)` icon in the top-right corner of Odoo." -msgstr "" - -#: ../../content/applications/general/voip/onsip.rst:95 -msgid "Additional setup and troubleshooting steps can be found on `OnSIP's knowledge base `_." -msgstr "" - -#: ../../content/applications/general/voip/onsip.rst:99 -msgid "Incoming calls" -msgstr "" - -#: ../../content/applications/general/voip/onsip.rst:101 -msgid "The Odoo database also receives incoming calls that produce pop-up windows in Odoo. When those call pop-up windows appear, click the green :guilabel:`📞 (phone)` icon to answer the call." -msgstr "" - -#: ../../content/applications/general/voip/onsip.rst:104 -msgid "To ignore the call, click the red :guilabel:`📞 (phone)` icon." -msgstr "" - -#: ../../content/applications/general/voip/onsip.rst:-1 -msgid "Incoming call shown in the Odoo VoIP widget." -msgstr "" - -#: ../../content/applications/general/voip/onsip.rst:112 -msgid ":doc:`voip_widget`" -msgstr "" - -#: ../../content/applications/general/voip/onsip.rst:115 -#: ../../content/applications/general/voip/voip_widget.rst:32 -msgid "Troubleshooting" -msgstr "" - -#: ../../content/applications/general/voip/onsip.rst:118 -msgid "Missing parameters" -msgstr "" - -#: ../../content/applications/general/voip/onsip.rst:120 -msgid "If a *Missing Parameters* message appears in the Odoo widget, make sure to refresh the Odoo browser window (or tab), and try again." -msgstr "" - -#: ../../content/applications/general/voip/onsip.rst:-1 -msgid "Missing parameter message in the Odoo VoIP widget." -msgstr "" - -#: ../../content/applications/general/voip/onsip.rst:128 -msgid "Incorrect number" -msgstr "" - -#: ../../content/applications/general/voip/onsip.rst:130 -msgid "If an *Incorrect Number* message appears in the Odoo widget, make sure to use the international format for the number. This means leading with the :guilabel:`+ (plus)` sign, followed by the international country code." -msgstr "" - -#: ../../content/applications/general/voip/onsip.rst:138 -msgid "For example, `+16505555555` (where `+1` is the international prefix for the United States)." -msgstr "" - -#: ../../content/applications/general/voip/onsip.rst:-1 -msgid "Incorrect number message populated in the Odoo VoIP widget." -msgstr "" - -#: ../../content/applications/general/voip/onsip.rst:149 -msgid "OnSIP on mobile phone" -msgstr "" - -#: ../../content/applications/general/voip/onsip.rst:151 -msgid "In order to make and receive phone calls when the user is not in front of Odoo on their computer, a softphone app on a mobile phone can be used in parallel with Odoo *VoIP*." -msgstr "" - -#: ../../content/applications/general/voip/onsip.rst:154 -msgid "This is useful for convenient, on-the-go calls, and to make sure incoming calls are heard. Any SIP softphone will work." -msgstr "" - -#: ../../content/applications/general/voip/onsip.rst:158 -msgid ":doc:`devices_integrations`" -msgstr "" - -#: ../../content/applications/general/voip/onsip.rst:159 -msgid "`OnSIP App Download `_" -msgstr "" - -#: ../../content/applications/general/voip/transfer_forward.rst:3 -msgid "Make, receive, transfer, and forward calls" -msgstr "" - -#: ../../content/applications/general/voip/transfer_forward.rst:5 -msgid "Calling prospective clients, customers, or colleagues is an essential part of any business. A company also needs to be available when customers call, in order to build trust and make connections." -msgstr "" - -#: ../../content/applications/general/voip/transfer_forward.rst:9 -msgid "This document covers how to make, receive, transfer, and forward calls with Odoo *VoIP*." -msgstr "" - -#: ../../content/applications/general/voip/transfer_forward.rst:12 -msgid "Make calls" -msgstr "" - -#: ../../content/applications/general/voip/transfer_forward.rst:14 -msgid "Starting on the Odoo dashboard, a call can be made by opening the phone widget in the the upper-right corner, which is represented by a :guilabel:`☎️ (phone)` icon." -msgstr "" - -#: ../../content/applications/general/voip/transfer_forward.rst:17 -msgid "Then, a user can click on the :guilabel:`Contacts` tab, and click into any contact in the database to make a call." -msgstr "" - -#: ../../content/applications/general/voip/transfer_forward.rst:20 -msgid "Additionally, one can also use the :guilabel:`Search bar` in the :guilabel:`VOIP` pop-up window to find any desired contact." -msgstr "" - -#: ../../content/applications/general/voip/transfer_forward.rst:-1 -msgid "Using the VoIP phone widget to make calls." -msgstr "" - -#: ../../content/applications/general/voip/transfer_forward.rst:27 -msgid "To manually make a call, click the :guilabel:`⌨️ (keyboard)` icon, and proceed to manually key in the desired number. Do not forget to lead with the :guilabel:`+ (plus)` icon, followed by the international country code." -msgstr "" - -#: ../../content/applications/general/voip/transfer_forward.rst:32 -msgid "For the United States of America, the country code and :guilabel:`+ (plus)` icon, would look like this: `+1`. If one were to dial Belgium, the number would be prefixed by `+32`, and for Great Britain it would be `+44`." -msgstr "" - -#: ../../content/applications/general/voip/transfer_forward.rst:36 -msgid "After entering the full number, with the required :guilabel:`+ (plus)` icon prefix and country code, click the green :guilabel:`📞 (phone)` icon to start the call. When finished, click the red :guilabel:`📞 (phone)` icon to end the call." -msgstr "" - -#: ../../content/applications/general/voip/transfer_forward.rst:45 -msgid "Receive calls" -msgstr "" - -#: ../../content/applications/general/voip/transfer_forward.rst:47 -msgid "An incoming call automatically opens the *VoIP* widget, when a user is using the Odoo database. Should the database be open in another tab, a sound plays (the sound **must** be activated on the device)." -msgstr "" - -#: ../../content/applications/general/voip/transfer_forward.rst:51 -msgid "Once back to the tab, the calling screen of the *VoIP* phone widget appears." -msgstr "" - -#: ../../content/applications/general/voip/transfer_forward.rst:53 -msgid "Click the green :guilabel:`📞 (phone)` icon to pick up the call, or the red :guilabel:`📞 (phone)` icon to reject the call." -msgstr "" - -#: ../../content/applications/general/voip/transfer_forward.rst:-1 -msgid "Incoming call on the VoIP widget, with the call answer and call reject buttons highlighted." -msgstr "" - -#: ../../content/applications/general/voip/transfer_forward.rst:61 -msgid "Add to call queue" -msgstr "" - -#: ../../content/applications/general/voip/transfer_forward.rst:63 -msgid "All the contacts and customers that need to be called can be seen in one place with the Odoo *VoIP* phone widget, under the :guilabel:`Next activities` tab." -msgstr "" - -#: ../../content/applications/general/voip/transfer_forward.rst:-1 -msgid "VoIP widget with next activities highlighted, showing tasks below." -msgstr "" - -#: ../../content/applications/general/voip/transfer_forward.rst:70 -msgid "To add a call to the :guilabel:`Next activities` tab, click the green :guilabel:`📞 (phone)` icon, while in kanban view of the *CRM* application." -msgstr "" - -#: ../../content/applications/general/voip/transfer_forward.rst:73 -msgid "To remove them from the call queue, hover over the opportunity that has a call scheduled, and click the red :guilabel:`📞 (phone)` icon that appears with the :guilabel:`- (minus)` icon." -msgstr "" - -#: ../../content/applications/general/voip/transfer_forward.rst:76 -msgid "When navigating back to the *VoIP* phone widget, **only** the calls that are scheduled immediately for that day appear in the queue under the :guilabel:`Next Activities` tab of the *VoIP* pop-up widget." -msgstr "" - -#: ../../content/applications/general/voip/transfer_forward.rst:-1 -msgid "Adding a call to the next activities tab in the VoIP phone widget." -msgstr "" - -#: ../../content/applications/general/voip/transfer_forward.rst:84 -msgid "The :guilabel:`Next Activities` tab of the *VoIP* phone widget is integrated with the following Odoo apps: *CRM*, *Project*, and *Helpdesk*." -msgstr "" - -#: ../../content/applications/general/voip/transfer_forward.rst:87 -msgid "A call can be added in the chatter of records within those applications." -msgstr "" - -#: ../../content/applications/general/voip/transfer_forward.rst:89 -msgid "To manually add a call, via the chatter, click :guilabel:`Activities` (next to the :guilabel:`🕗 (clock)` icon). Under :guilabel:`Activity Type`, select :guilabel:`Call` from the drop-down menu that appears." -msgstr "" - -#: ../../content/applications/general/voip/transfer_forward.rst:93 -msgid "Next, set a :guilabel:`Due Date`, and add a :guilabel:`Summary`." -msgstr "" - -#: ../../content/applications/general/voip/transfer_forward.rst:95 -msgid "Lastly, change the :guilabel:`Assigned to` field to the person that should make the call. Whomever is set in this last field (:guilabel:`Assigned to`) has this call show up in their :guilabel:`Next Activities` call queue in the Odoo *VoIP* phone widget." -msgstr "" - -#: ../../content/applications/general/voip/transfer_forward.rst:100 -msgid "Only calls for the immediate day (today's date) appear in the :guilabel:`Next Activities` tab of the *VoIP* phone widget for that specific user." -msgstr "" - -#: ../../content/applications/general/voip/transfer_forward.rst:103 -msgid "If specified, click :guilabel:`Save` or :guilabel:`Open Calendar` to complete the scheduling of the call." -msgstr "" - -#: ../../content/applications/general/voip/transfer_forward.rst:107 -msgid "Transfer calls" -msgstr "" - -#: ../../content/applications/general/voip/transfer_forward.rst:109 -msgid "A call can be transferred from one user to another in the Odoo *VoIP* phone widget. However, this can **only** occur after speaking to the caller first. Without picking up the call in the Odoo *VoIP* phone widget, the only way to transfer a call is automatically though the provider console/portal." -msgstr "" - -#: ../../content/applications/general/voip/transfer_forward.rst:115 -msgid "For more information on transfers, visit :ref:`voip/axivox/forwardings_tab`." -msgstr "" - -#: ../../content/applications/general/voip/transfer_forward.rst:117 -msgid "To transfer a call within the Odoo *VoIP* phone widget, first, answer the call using the green :guilabel:`📞 (phone)` icon." -msgstr "" - -#: ../../content/applications/general/voip/transfer_forward.rst:120 -msgid "Once the incoming call is answered, click the :guilabel:`↔ (left-right arrow)` icon. Then, enter the extension of the user the call should be forwarded to. Finally, click :guilabel:`Transfer` to route the call to that phone number." -msgstr "" - -#: ../../content/applications/general/voip/transfer_forward.rst:125 -msgid "To find the extension for a user, consult the :abbr:`VoIP (Voice over Internet Protocol)` administrator, or, if the user has *Settings* access rights to *Administration*, navigate to :menuselection:`Settings App --> Manage Users --> Select the user --> Preferences --> VOIP --> VoIP username / Extension number`." -msgstr "" - -#: ../../content/applications/general/voip/transfer_forward.rst:130 -msgid "For more information on access rights, visit: :doc:`../users/access_rights`." -msgstr "" - -#: ../../content/applications/general/voip/transfer_forward.rst:-1 -msgid "Transferring a call within the phone widget, with the transfer buttons highlighted." -msgstr "" - -#: ../../content/applications/general/voip/transfer_forward.rst:137 -msgid "Forward calls" -msgstr "" - -#: ../../content/applications/general/voip/transfer_forward.rst:139 -msgid "To forward a call within the Odoo *VoIP* phone widget, first, answer the call using the green :guilabel:`📞 (phone)` icon. Once the incoming call is answered, click the :guilabel:`↔ (left-right arrow)` icon." -msgstr "" - -#: ../../content/applications/general/voip/transfer_forward.rst:143 -msgid "Then, enter the full phone number of the user the call should be forwarded to. Finally, click :guilabel:`Transfer` to route the call to that phone number." -msgstr "" - -#: ../../content/applications/general/voip/transfer_forward.rst:147 -msgid "For more information on forwarding, visit :ref:`voip/axivox/forwardings_tab`." -msgstr "" - -#: ../../content/applications/general/voip/voip_widget.rst:3 -msgid "VoIP widget" -msgstr "" - -#: ../../content/applications/general/voip/voip_widget.rst:5 -msgid "The *VoIP* widget is an add-on made available to Odoo users through the *VoIP* module. It is used to incorporate virtual telephony into the database. The widget is the control center for making and managing calls in Odoo." -msgstr "" - -#: ../../content/applications/general/voip/voip_widget.rst:10 -msgid "Phone calls" -msgstr "" - -#: ../../content/applications/general/voip/voip_widget.rst:12 -msgid "To make phone calls while in the Odoo database, click the :guilabel:`☎️ (phone)` icon, located in the top navigation bar." -msgstr "" - -#: ../../content/applications/general/voip/voip_widget.rst:15 -msgid "When clicked, a :guilabel:`VOIP` pop-up widget appears in the lower-left corner of the Odoo database. The widget allows users to freely navigate throughout the database, while making and receiving calls." -msgstr "" - -#: ../../content/applications/general/voip/voip_widget.rst:19 -msgid "When receiving calls in Odoo, the :guilabel:`VOIP` widget rings,and displays a notification. To close the widget, click the :guilabel:`X (close)` icon in the upper-right of the widget's screen." -msgstr "" - -#: ../../content/applications/general/voip/voip_widget.rst:23 -msgid "The :abbr:`VoIP (Voice over Internet Protocol)` number is the one provided by Axivox. It can be accessed by navigating to `https://manage.axivox.com/ `_. After logging into the portal, go to :menuselection:`Users --> Outgoing number` (column)." -msgstr "" - -#: ../../content/applications/general/voip/voip_widget.rst:-1 -msgid "VoIP call in Odoo." -msgstr "" - -#: ../../content/applications/general/voip/voip_widget.rst:35 -msgid "If a *Missing Parameter* error message appears in the Odoo *VoIP* widget, refresh the Odoo window, and try again." -msgstr "" - -#: ../../content/applications/general/voip/voip_widget.rst:0 -msgid "\"Missing Parameter\" error message in the Odoo softphone." -msgstr "" - -#: ../../content/applications/general/voip/voip_widget.rst:43 -msgid "If an *Incorrect Number* error message appears in the Odoo *VoIP* widget, make sure to use the international format, leading with the :guilabel:`+ (plus)` sign, followed by the international country code." -msgstr "" - -#: ../../content/applications/general/voip/voip_widget.rst:47 -msgid "(E.g., +16506913277, where `+1` is the international prefix for the United States.)" -msgstr "" - -#: ../../content/applications/general/voip/voip_widget.rst:0 -msgid "\"Incorrect Number\" error message in the Odoo softphone." -msgstr "" - -#: ../../content/applications/general/voip/voip_widget.rst:54 -msgid "Tabs" -msgstr "" - -#: ../../content/applications/general/voip/voip_widget.rst:56 -msgid "In all, there are three tabs (:guilabel:`Recent`, :guilabel:`Next Activities`, and :guilabel:`Contacts`) present in the *VoIP* widget, which are used for managing calls and day-to-day activities in Odoo." -msgstr "" - -#: ../../content/applications/general/voip/voip_widget.rst:61 -msgid "Recent" -msgstr "" - -#: ../../content/applications/general/voip/voip_widget.rst:63 -msgid "Under the :guilabel:`Recent` tab of the *VoIP* widget, the call history for the user is available. This includes incoming and outgoing calls. Any number can be clicked to begin a call." -msgstr "" - -#: ../../content/applications/general/voip/voip_widget.rst:67 -msgid "Next activities" -msgstr "" - -#: ../../content/applications/general/voip/voip_widget.rst:69 -msgid "Under the :guilabel:`Next Activities` tab of the *VoIP* widget, a user can see any activities assigned to them, and which ones are due to be completed for the day." -msgstr "" - -#: ../../content/applications/general/voip/voip_widget.rst:72 -msgid "Click an activity from this tab to perform any actions including: Sending an email, accessing their contact, scheduling another activity, or accessing a linked record (such as a Sales Order, Lead/Opportunity, or Project Task)." -msgstr "" - -#: ../../content/applications/general/voip/voip_widget.rst:76 -msgid "The user can also mark the activity as complete, edit the details of the activity, or cancel it." -msgstr "" - -#: ../../content/applications/general/voip/voip_widget.rst:78 -msgid "To call the customer related to a scheduled activity, click the :guilabel:`📞 (phone)` icon, or click the :guilabel:`⌨️ (keyboard)` icon to dial another number for the customer." -msgstr "" - -#: ../../content/applications/general/voip/voip_widget.rst:-1 -msgid "Activity control center on the VoIP widget." -msgstr "" - -#: ../../content/applications/general/voip/voip_widget.rst:85 -msgid "Some other icons appear in the *VoIP* widget, categorized by two sections: :guilabel:`Document` and :guilabel:`Activity`." -msgstr "" - -#: ../../content/applications/general/voip/voip_widget.rst:88 -msgid "Under the :guilabel:`Document` section, from right to left:" -msgstr "" - -#: ../../content/applications/general/voip/voip_widget.rst:90 -msgid ":guilabel:`✉️ (envelope)` icon: sends an email" -msgstr "" - -#: ../../content/applications/general/voip/voip_widget.rst:91 -msgid ":guilabel:`👤 (person icon)` icon: redirects to the contact card" -msgstr "" - -#: ../../content/applications/general/voip/voip_widget.rst:92 -msgid ":guilabel:`📄 (document)` icon: redirects to the attached record in Odoo" -msgstr "" - -#: ../../content/applications/general/voip/voip_widget.rst:93 -msgid ":guilabel:`🕓 (clock)` icon: schedule an activity" -msgstr "" - -#: ../../content/applications/general/voip/voip_widget.rst:95 -msgid "Under the :guilabel:`Activity` section, from left to right:" -msgstr "" - -#: ../../content/applications/general/voip/voip_widget.rst:97 -msgid ":guilabel:`✔️ (checkmark)` icon: mark activity as done" -msgstr "" - -#: ../../content/applications/general/voip/voip_widget.rst:98 -msgid ":guilabel:`✏️ (pencil)` icon: edit the activity" -msgstr "" - -#: ../../content/applications/general/voip/voip_widget.rst:99 -msgid ":guilabel:`✖️ (cancel)` icon: cancel the activity" -msgstr "" - -#: ../../content/applications/general/voip/voip_widget.rst:102 -msgid "Contacts" -msgstr "" - -#: ../../content/applications/general/voip/voip_widget.rst:104 -msgid "Under the :guilabel:`Contacts` tab of the *VoIP* widget, a user can access a contact in the *Contacts* app." -msgstr "" - -#: ../../content/applications/general/voip/voip_widget.rst:107 -msgid "Any contact can easily be called by clicking into the contact from the *VoIP* widget's :guilabel:`Contacts` tab." -msgstr "" - -#: ../../content/applications/general/voip/voip_widget.rst:110 -msgid "A search feature is also available in the upper-right side of the widget, represented by a :guilabel:`🔍 (magnifying glass)` icon." -msgstr "" diff --git a/locale/sources/hr.pot b/locale/sources/hr.pot index ef54877ab..e0605c234 100644 --- a/locale/sources/hr.pot +++ b/locale/sources/hr.pot @@ -8,7 +8,7 @@ msgid "" msgstr "" "Project-Id-Version: Odoo 17.0\n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2024-03-08 12:48+0000\n" +"POT-Creation-Date: 2024-03-25 16:01+0000\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME \n" "Language-Team: LANGUAGE \n" @@ -39,7 +39,7 @@ msgid "Regular appraisals are good for both the employees and the company, since msgstr "" #: ../../content/applications/hr/appraisals.rst:18 -#: ../../content/applications/hr/attendances.rst:67 +#: ../../content/applications/hr/attendances.rst:66 #: ../../content/applications/hr/frontdesk.rst:13 #: ../../content/applications/hr/time_off.rst:27 msgid "Configuration" @@ -501,7 +501,7 @@ msgid "If managers want to leave notes that are only visible to other managers, msgstr "" #: ../../content/applications/hr/appraisals.rst:386 -#: ../../content/applications/hr/recruitment.rst:521 +#: ../../content/applications/hr/recruitment.rst:520 msgid "Schedule a meeting" msgstr "" @@ -546,38 +546,38 @@ msgid "The color of the icon indicates the status; a green icon means an activit msgstr "" #: ../../content/applications/hr/appraisals.rst:421 -msgid "For more details on activities, refer to the :doc:`../productivity/discuss/overview/plan_activities` document." +msgid "For more details on activities, refer to the :doc:`../essentials/activities` document." msgstr "" #: ../../content/applications/hr/appraisals.rst:0 msgid "The appraisal cards with the various activity icons highlighted." msgstr "" -#: ../../content/applications/hr/appraisals.rst:428 +#: ../../content/applications/hr/appraisals.rst:427 msgid "Enter a brief description in the :guilabel:`Summary` field of the :guilabel:`Schedule Activity` pop-up window, such as `Annual Appraisal for (Employee)`." msgstr "" -#: ../../content/applications/hr/appraisals.rst:431 +#: ../../content/applications/hr/appraisals.rst:430 msgid "Next, click the :guilabel:`Open Calendar` button. From the calendar page that appears, navigate to, and double-click on, the desired date and time for the meeting." msgstr "" -#: ../../content/applications/hr/appraisals.rst:434 +#: ../../content/applications/hr/appraisals.rst:433 msgid "Doing so opens a :guilabel:`New Event` pop-up form. From this pop-up form, make any desired modifications, such as designating a :guilabel:`Start` time, or giving a :guilabel:`Name` to the meeting." msgstr "" -#: ../../content/applications/hr/appraisals.rst:438 +#: ../../content/applications/hr/appraisals.rst:437 msgid "Add the appraisee in the :guilabel:`Attendees` section, and include anyone else who should be in the meeting, if necessary." msgstr "" -#: ../../content/applications/hr/appraisals.rst:441 +#: ../../content/applications/hr/appraisals.rst:440 msgid "To make the meeting a video call, instead of an in-person meeting, click :guilabel:`+ Odoo meeting`, and a :guilabel:`Videocall URL` link appears in the field." msgstr "" -#: ../../content/applications/hr/appraisals.rst:444 +#: ../../content/applications/hr/appraisals.rst:443 msgid "Once all the desired changes are complete, click :guilabel:`Save & Close`." msgstr "" -#: ../../content/applications/hr/appraisals.rst:446 +#: ../../content/applications/hr/appraisals.rst:445 msgid "The meeting now appears on the calendar, and the invited parties are informed, via email." msgstr "" @@ -585,55 +585,55 @@ msgstr "" msgid "The meeting form with all information entered for Ronnie Hart's annual appraisal." msgstr "" -#: ../../content/applications/hr/appraisals.rst:452 +#: ../../content/applications/hr/appraisals.rst:451 msgid "The other way to schedule a meeting is from the individual appraisal form. To do this, navigate to the :menuselection:`Appraisal application` dashboard, then click on an appraisal card." msgstr "" -#: ../../content/applications/hr/appraisals.rst:455 +#: ../../content/applications/hr/appraisals.rst:454 msgid "Next, click on the :guilabel:`Meeting` smart button, and the calendar loads. Follow the same directions above to create the meeting." msgstr "" -#: ../../content/applications/hr/appraisals.rst:459 +#: ../../content/applications/hr/appraisals.rst:458 msgid "If no meetings are scheduled, the :guilabel:`Meeting` smart button says :guilabel:`No Meeting`." msgstr "" -#: ../../content/applications/hr/appraisals.rst:464 +#: ../../content/applications/hr/appraisals.rst:463 msgid "Goals" msgstr "" -#: ../../content/applications/hr/appraisals.rst:466 +#: ../../content/applications/hr/appraisals.rst:465 msgid "The ability to set goals for employees to work toward is an important feature of Odoo *Appraisals*. Goals are typically set during an appraisal, so the employee knows what they need to work toward before their next appraisal." msgstr "" -#: ../../content/applications/hr/appraisals.rst:470 +#: ../../content/applications/hr/appraisals.rst:469 msgid "To view all goals, navigate to :menuselection:`Appraisals application --> Goals`. This presents all the goals for every employee, in a default Kanban view." msgstr "" -#: ../../content/applications/hr/appraisals.rst:473 +#: ../../content/applications/hr/appraisals.rst:472 msgid "Each goal card contains the following information:" msgstr "" -#: ../../content/applications/hr/appraisals.rst:475 +#: ../../content/applications/hr/appraisals.rst:474 msgid ":guilabel:`Skill`: the name of the goal." msgstr "" -#: ../../content/applications/hr/appraisals.rst:476 +#: ../../content/applications/hr/appraisals.rst:475 msgid ":guilabel:`Name`: the employee the goal is assigned to." msgstr "" -#: ../../content/applications/hr/appraisals.rst:477 +#: ../../content/applications/hr/appraisals.rst:476 msgid ":guilabel:`Deadline`: the due date for the goal." msgstr "" -#: ../../content/applications/hr/appraisals.rst:478 +#: ../../content/applications/hr/appraisals.rst:477 msgid ":guilabel:`Progress`: the percentage of competency set for the goal." msgstr "" -#: ../../content/applications/hr/appraisals.rst:479 +#: ../../content/applications/hr/appraisals.rst:478 msgid ":guilabel:`Employee`: the profile icon of the employee the goal is assigned to." msgstr "" -#: ../../content/applications/hr/appraisals.rst:481 +#: ../../content/applications/hr/appraisals.rst:480 msgid "If a goal is completed, a :guilabel:`Done` banner appears in the top-right corner of the goal card." msgstr "" @@ -641,27 +641,27 @@ msgstr "" msgid "The goals Kanban view, with nine goal cards." msgstr "" -#: ../../content/applications/hr/appraisals.rst:488 +#: ../../content/applications/hr/appraisals.rst:487 msgid "Every individual goal requires its own entry for each employee. If employees have the same goal, a goal card for each employee appears on the list. For example, if both Bob and Sara have the same goal of `Typing`, two cards appear in the Kanban view: one `Typing` goal for Bob, and another `Typing` goal for Sara." msgstr "" -#: ../../content/applications/hr/appraisals.rst:494 +#: ../../content/applications/hr/appraisals.rst:493 msgid "New goal" msgstr "" -#: ../../content/applications/hr/appraisals.rst:496 +#: ../../content/applications/hr/appraisals.rst:495 msgid "To create a new goal, navigate to :menuselection:`Appraisals application --> Goals`, and click :guilabel:`New` to open a blank goal form." msgstr "" -#: ../../content/applications/hr/appraisals.rst:499 +#: ../../content/applications/hr/appraisals.rst:498 msgid "Enter the information on the card. The information requested is all the same information that appears on the :ref:`goal card ` in the Kanban view, with the addition of a :guilabel:`Tags` field and a :guilabel:`Description` tab." msgstr "" -#: ../../content/applications/hr/appraisals.rst:503 +#: ../../content/applications/hr/appraisals.rst:502 msgid "The current user populates the :guilabel:`Employee` field by default, and the :guilabel:`Manager` field populates with the manager set on the employee profile." msgstr "" -#: ../../content/applications/hr/appraisals.rst:506 +#: ../../content/applications/hr/appraisals.rst:505 msgid "Make any necessary changes to the form, and add any notes that might be useful to clarify the goal in the :guilabel:`Description` tab." msgstr "" @@ -669,68 +669,68 @@ msgstr "" msgid "A goal form filled out for a Python skill, set to 50% proficiency." msgstr "" -#: ../../content/applications/hr/appraisals.rst:514 +#: ../../content/applications/hr/appraisals.rst:513 msgid "Completed goals" msgstr "" -#: ../../content/applications/hr/appraisals.rst:516 +#: ../../content/applications/hr/appraisals.rst:515 msgid "When a goal has been met, it is important to update the record. A goal can be marked as `Done` in one of two ways: from the main :guilabel:`Goals` dashboard, or from the individual goal card." msgstr "" -#: ../../content/applications/hr/appraisals.rst:519 +#: ../../content/applications/hr/appraisals.rst:518 msgid "To mark a goal as `Done` from the main :guilabel:`Goals` dashboard, click on the :guilabel:`⋮ (three dots)` icon in the top-right of a goal card." msgstr "" -#: ../../content/applications/hr/appraisals.rst:523 +#: ../../content/applications/hr/appraisals.rst:522 msgid "The :guilabel:`⋮ (three dots)` icon **only** appears when the mouse hovers over the corner of a goal card." msgstr "" -#: ../../content/applications/hr/appraisals.rst:526 +#: ../../content/applications/hr/appraisals.rst:525 msgid "Then, click :guilabel:`Mark as Done` from the resulting drop-down menu. A green :guilabel:`Done` banner appears in the top-right corner of the goal card." msgstr "" -#: ../../content/applications/hr/appraisals.rst:529 +#: ../../content/applications/hr/appraisals.rst:528 msgid "To mark a goal as `Done` from the goal card itself, click on a goal card to open that goal's form. Then, click the :guilabel:`Mark as Done` button in the top-left of the form. When clicked, a green :guilabel:`Done` banner appears in the top-right corner of the goal form." msgstr "" -#: ../../content/applications/hr/appraisals.rst:534 -#: ../../content/applications/hr/attendances.rst:450 +#: ../../content/applications/hr/appraisals.rst:533 +#: ../../content/applications/hr/attendances.rst:526 #: ../../content/applications/hr/frontdesk.rst:351 #: ../../content/applications/hr/payroll/reporting.rst:3 -#: ../../content/applications/hr/referrals.rst:754 -#: ../../content/applications/hr/time_off.rst:700 +#: ../../content/applications/hr/referrals.rst:753 +#: ../../content/applications/hr/time_off.rst:702 msgid "Reporting" msgstr "" -#: ../../content/applications/hr/appraisals.rst:536 +#: ../../content/applications/hr/appraisals.rst:535 msgid "The *Appraisals* application tracks two metrics across two different reports: an :ref:`appraisal analysis `, and a :ref:`skills evolution `." msgstr "" -#: ../../content/applications/hr/appraisals.rst:542 +#: ../../content/applications/hr/appraisals.rst:541 msgid "Appraisal analysis" msgstr "" -#: ../../content/applications/hr/appraisals.rst:544 +#: ../../content/applications/hr/appraisals.rst:543 msgid "To access the *Appraisal Analysis* report, navigate to :menuselection:`Appraisals application --> Reporting --> Appraisal Analysis`. This displays a report of all the appraisals in the database, highlighted in different colors to represent their status." msgstr "" -#: ../../content/applications/hr/appraisals.rst:548 +#: ../../content/applications/hr/appraisals.rst:547 msgid "Appraisals in yellow are completed, appraisals in orange are in-progress (the appraisal is confirmed, but not completed), and appraisals in gray are scheduled (according to the :ref:`appraisals/appraisal-plan`), but have not been confirmed yet." msgstr "" -#: ../../content/applications/hr/appraisals.rst:552 +#: ../../content/applications/hr/appraisals.rst:551 msgid "The report displays the whole current year, by default, grouped by department." msgstr "" -#: ../../content/applications/hr/appraisals.rst:554 +#: ../../content/applications/hr/appraisals.rst:553 msgid "To change the calendar view presented, change the date settings in the top-left of the report. The options to display are :guilabel:`Day`, :guilabel:`Week`, :guilabel:`Month`, and :guilabel:`Year`. Use the arrows to move forward or backward in time." msgstr "" -#: ../../content/applications/hr/appraisals.rst:558 +#: ../../content/applications/hr/appraisals.rst:557 msgid "At any point, click the :guilabel:`Today` button to present the calendar to include today's date in the view." msgstr "" -#: ../../content/applications/hr/appraisals.rst:561 +#: ../../content/applications/hr/appraisals.rst:560 msgid "The report can have other filters and groupings set in the :guilabel:`Search...` bar at the top." msgstr "" @@ -738,51 +738,51 @@ msgstr "" msgid "A report showing all the appraisals for the Appraisal Analysis report." msgstr "" -#: ../../content/applications/hr/appraisals.rst:570 +#: ../../content/applications/hr/appraisals.rst:569 msgid "Skills evolution" msgstr "" -#: ../../content/applications/hr/appraisals.rst:572 +#: ../../content/applications/hr/appraisals.rst:571 msgid "To access the *Skills Evolution* report, navigate to :menuselection:`Appraisals application --> Reporting --> Skills Evolution`. This displays a report of all skills, grouped by employee." msgstr "" -#: ../../content/applications/hr/appraisals.rst:575 +#: ../../content/applications/hr/appraisals.rst:574 msgid "All the lines of the report are collapsed, by default. To view the details of a line, click on a line to expand the data." msgstr "" -#: ../../content/applications/hr/appraisals.rst:578 +#: ../../content/applications/hr/appraisals.rst:577 msgid "Each skill has the following information listed:" msgstr "" -#: ../../content/applications/hr/appraisals.rst:580 +#: ../../content/applications/hr/appraisals.rst:579 msgid ":guilabel:`Employee`: name of the employee." msgstr "" -#: ../../content/applications/hr/appraisals.rst:581 +#: ../../content/applications/hr/appraisals.rst:580 msgid ":guilabel:`Skill Type`: the category the skill falls under." msgstr "" -#: ../../content/applications/hr/appraisals.rst:582 +#: ../../content/applications/hr/appraisals.rst:581 msgid ":guilabel:`Skill`: the specific, individual skill." msgstr "" -#: ../../content/applications/hr/appraisals.rst:583 +#: ../../content/applications/hr/appraisals.rst:582 msgid ":guilabel:`Previous Skill Level`: the level the employee had previously achieved for the skill." msgstr "" -#: ../../content/applications/hr/appraisals.rst:584 +#: ../../content/applications/hr/appraisals.rst:583 msgid ":guilabel:`Previous Skill Progress`: the previous percentage of competency achieved for the skill (based on the :guilabel:`Skill Level`)." msgstr "" -#: ../../content/applications/hr/appraisals.rst:586 +#: ../../content/applications/hr/appraisals.rst:585 msgid ":guilabel:`Current Skill Level`: the current level the employee has achieved for the skill." msgstr "" -#: ../../content/applications/hr/appraisals.rst:587 +#: ../../content/applications/hr/appraisals.rst:586 msgid ":guilabel:`Current Skill Progress`: the current percentage of competency achieved for the skill." msgstr "" -#: ../../content/applications/hr/appraisals.rst:588 +#: ../../content/applications/hr/appraisals.rst:587 msgid ":guilabel:`Justification`: any notes entered on the skill explaining the progress." msgstr "" @@ -795,11 +795,11 @@ msgid "Attendances" msgstr "" #: ../../content/applications/hr/attendances.rst:12 -msgid "Odoo's *Attendances* application functions as a time clock. Employees are able to check in and out of work using a dedicated device in kiosk mode, while users are also able to check in and out of work directly from the database. Managers can quickly see who is available at any given time, and create reports to see everyone's hours, and gain insights on which employees are working overtime, or checking out of work earlier than expected." +msgid "Odoo's *Attendances* application functions as a time clock. Employees are able to check in and out of work using a dedicated device in kiosk mode, while users are also able to check in and out of work directly from the database. Managers can quickly see who is available at any given time, create reports to see everyone's hours, and gain insights on which employees are working overtime, or checking out of work earlier than expected." msgstr "" #: ../../content/applications/hr/attendances.rst:21 -msgid "Access Rights" +msgid "Access rights" msgstr "" #: ../../content/applications/hr/attendances.rst:23 @@ -807,11 +807,11 @@ msgid "It is important to understand how the different access rights affect what msgstr "" #: ../../content/applications/hr/attendances.rst:26 -msgid "Every user in the database is always able to access their own information on the dashboard, and can check in and out directly from the database. Access to all the other features is determined by access rights." +msgid "Every user in the database is always able to access their own information on the dashboard and can check in and out directly from the database. Access to all the other features is determined by access rights." msgstr "" #: ../../content/applications/hr/attendances.rst:30 -msgid "To see what access rights a user has, navigate to the :menuselection:`Settings application --> Users & Companies: Users`, and click on an individual user. The :guilabel:`Access Rights` tab is visible by default. Scroll down to the :guilabel:`Human Resources` section to see the setting. For the :guilabel:`Attendances` field, the options are either to leave the field blank, or select :guilabel:`Administrator`." +msgid "To see what access rights a user has, navigate to the :menuselection:`Settings application --> Users & Companies: Users`, and click on an individual user. The :guilabel:`Access Rights` tab is visible by default. Scroll down to the :guilabel:`Human Resources` section to see the setting. For the :guilabel:`Attendances` field, the options are either to leave the field blank or select :guilabel:`Administrator`." msgstr "" #: ../../content/applications/hr/attendances.rst:36 @@ -819,7 +819,7 @@ msgid "If the :guilabel:`Administrator` option is selected, the user has full ac msgstr "" #: ../../content/applications/hr/attendances.rst:41 -msgid "If left blank, the user can only view their own information on the *Attendances* application dashboard, and can view their own personal attendance records under the reporting feature. Everyone else's attendance records will be hidden from view on the report. There is no access to either the kiosk mode or the configuration menu." +msgid "If left blank, the user can only view their own information on the *Attendances* application dashboard and can view their own personal attendance records under the reporting feature. All other attendance records are hidden from view on the report. There is no access to either the kiosk mode or the configuration menu." msgstr "" #: ../../content/applications/hr/attendances.rst:49 @@ -827,182 +827,211 @@ msgid "Approvers" msgstr "" #: ../../content/applications/hr/attendances.rst:51 -msgid "The only other scenario where different information may be accessible in the *Attendances* application is for approvers. If a user does *not* have administrative rights for the *Attendances* application, but they are set as an employee's approver for the *Attendances* application, that user will be able to view the attendance records for that specific employee, as well as make modifications to that employee's attendance records (when necessary). This applies to all employee's the user is listed as the *Attendances* application approver. Approvers are typically managers, though this is not necessary." +msgid "The **only** other scenario where different information may be accessible in the *Attendances* application is for approvers. If a user does *not* have administrative rights for the *Attendances* application, but they are set as an employee's approver for the *Attendances* application, that user is able to view the attendance records for that specific employee, as well as make modifications to that employee's attendance records, if necessary. This applies to all employees for whom the user is listed as the *Attendances* application approver. Approvers are typically managers, though this is not required." msgstr "" #: ../../content/applications/hr/attendances.rst:59 -msgid "To see who the attendance approver is for an employee, navigate to the :menuselection:`Employees application` and click on the specific employee. Click on the :guilabel:`Work Information` tab, and scroll to the :guilabel:`Approvers` section, and check the :guilabel:`Attendance` field. The person selected will be able to view that employees' attendance records, both on the *Attendances* application dashboard as well as in the attendance reports, and make modifications to their records." +msgid "To see who the attendance approver is for an employee, navigate to the :menuselection:`Employees application` and click on the specific employee. Click on the :guilabel:`Work Information` tab, scroll to the :guilabel:`Approvers` section, and check the :guilabel:`Attendance` field. The person selected is able to view that employees' attendance records, both on the *Attendances* application dashboard as well as in the attendance reports, and make modifications to their records." msgstr "" -#: ../../content/applications/hr/attendances.rst:69 -msgid "There are very few configurations needed in the *Attendances* application. Determining how employees check in and out, defining how the kiosks function, and determining how extra hours are computed are all set in the Configuration menu. Navigate to the :menuselection:`Attendances application--> Configuration` to access the configuration menu." +#: ../../content/applications/hr/attendances.rst:68 +msgid "Few configurations are needed in the *Attendances* application. Determining how employees check in and out, defining how the kiosks function, and determining how extra hours are computed are all set in the Configuration menu. Navigate to the :menuselection:`Attendances application --> Configuration` to access the configuration menu." msgstr "" -#: ../../content/applications/hr/attendances.rst:75 +#: ../../content/applications/hr/attendances.rst:74 msgid "Modes" msgstr "" -#: ../../content/applications/hr/attendances.rst:79 +#: ../../content/applications/hr/attendances.rst:78 msgid ":guilabel:`Kiosk Mode`: using the drop-down menu, select how an employee checks in when using a kiosk. Options are :guilabel:`Barcode/RFID`, :guilabel:`Barcode/RFID and Manual Selection`, or :guilabel:`Manual Selection`." msgstr "" -#: ../../content/applications/hr/attendances.rst:84 -msgid "The *Barcode* application **does not** need to be installed in order to use one of the Barcode/RFID settings." +#: ../../content/applications/hr/attendances.rst:83 +msgid "The *Barcode* application **does not** need to be installed to use one of the Barcode/RFID settings." msgstr "" -#: ../../content/applications/hr/attendances.rst:87 +#: ../../content/applications/hr/attendances.rst:86 msgid ":guilabel:`Attendances from Backend`: activate this selection to allow users to check in and out directly from the Odoo database. If this is not activated, users must use a kiosk to check in and out of work." msgstr "" -#: ../../content/applications/hr/attendances.rst:94 -msgid "Kiosk Settings" +#: ../../content/applications/hr/attendances.rst:93 +msgid "Kiosk settings" msgstr "" -#: ../../content/applications/hr/attendances.rst:96 -msgid "This section only needs to be configured if employees use kiosks for checking in and out. If kiosks are *not* being used, modifying any of these fields will **not** adversely affect the functionality of the Attendances application." +#: ../../content/applications/hr/attendances.rst:95 +msgid "This section only needs to be configured if employees use kiosks for checking in and out. If kiosks are **not** being used, modifying any of these fields does **not** adversely affect the *Attendances* application." msgstr "" -#: ../../content/applications/hr/attendances.rst:100 -msgid ":guilabel:`Barcode Source`: this setting appears if either of the two Barcode/RFID selections were configured for the :ref:`Kiosk Mode ` setting. Select how barcodes are scanned at the kiosk, either with a dedicated barcode :guilabel:`Scanner`, or the device's :guilabel:`Front Camera`, or :guilabel:`Back Camera`." +#: ../../content/applications/hr/attendances.rst:99 +msgid ":guilabel:`Barcode Source`: this setting appears **only** if either of the two Barcode/RFID selections were configured for the :ref:`Kiosk Mode ` setting. Select how barcodes are scanned at the kiosk, either with a dedicated barcode :guilabel:`Scanner`, or the device's :guilabel:`Front Camera`, or :guilabel:`Back Camera`." msgstr "" -#: ../../content/applications/hr/attendances.rst:104 +#: ../../content/applications/hr/attendances.rst:103 msgid ":guilabel:`Employee PIN Identification`: activate this option if employees should use a unique PIN to check in. PINs are configured on each individual employee record. Refer to the :doc:`../hr/employees/new_employee` documentation for more information on setting up PINs." msgstr "" -#: ../../content/applications/hr/attendances.rst:107 +#: ../../content/applications/hr/attendances.rst:106 msgid ":guilabel:`Display Time`: set the duration (in seconds) the check in and check out confirmation screen remains on the kiosk before going back to the main check in screen." msgstr "" -#: ../../content/applications/hr/attendances.rst:109 -msgid ":guilabel:`Attendance Kiosk Url`: Odoo generates a unique web address (URL) in order to use a device as a kiosk without having to sign in to the Odoo database. When setting up a kiosk device, navigate to this unique web address in a web browser to present the Attendances application kiosk." +#: ../../content/applications/hr/attendances.rst:108 +msgid ":guilabel:`Attendance Kiosk Url`: Odoo generates a unique web address (URL) to use a device as a kiosk without having to sign in to the Odoo database. When setting up a kiosk device, navigate to this unique web address in a web browser to present the Attendances application kiosk." msgstr "" -#: ../../content/applications/hr/attendances.rst:114 -msgid "These kiosk URLs are **not** secured with any type of access code. Anyone who has the URL can access the Attendances application kiosk. If the URL is compromised for any reason, such as in the event of a security breach, click :guilabel:`Generate a new Kiosk Mode URL`, located beneath the link, to generate a new URL and update the kiosk(s) accordingly." +#: ../../content/applications/hr/attendances.rst:113 +msgid "These kiosk URLs are **not** secured with any type of access code. Anyone who has the URL can access the Attendances application kiosk. If the URL is compromised for any reason, such as in the event of a security breach, click :guilabel:`Generate a new Kiosk Mode URL`, located beneath the link, to generate a new URL and update the kiosk accordingly." msgstr "" -#: ../../content/applications/hr/attendances.rst:120 -msgid "Extra Hours" +#: ../../content/applications/hr/attendances.rst:119 +msgid "Extra hours" msgstr "" -#: ../../content/applications/hr/attendances.rst:122 +#: ../../content/applications/hr/attendances.rst:121 +msgid "This section specifies how extra time is calculated, including when extra time is counted and what time is not logged." +msgstr "" + +#: ../../content/applications/hr/attendances.rst:124 msgid ":guilabel:`Count of Extra Hours`: enable this box to allow employees to log extra hours beyond their set working hours (sometimes referred to as *overtime*). Activating this selection displays the following settings as well. If this is not activated, no other configurations appear." msgstr "" -#: ../../content/applications/hr/attendances.rst:126 -msgid ":guilabel:`Start From`: the current date is automatically entered in this field. If desired, click on this field and use the calendar selector to modify the start date that extra hours will be logged." +#: ../../content/applications/hr/attendances.rst:128 +msgid ":guilabel:`Start From`: the current date is automatically entered in this field. If desired, click on this field and use the calendar selector to modify the start date on which extra hours are logged." msgstr "" -#: ../../content/applications/hr/attendances.rst:129 -msgid ":guilabel:`Tolerance Time In Favor Of Company`: enter the amount of time, in minutes, that will *not* count towards an employee's overtime. When an employee checks out, and the extra time logged is below the specified minutes, the extra time will *not* be counted as overtime for the employee." +#: ../../content/applications/hr/attendances.rst:131 +msgid ":guilabel:`Tolerance Time In Favor Of Company`: enter the amount of time, in minutes, that is **not** counted towards an employee's overtime. When an employee checks out, and the extra time logged is below the specified minutes, the extra time is **not** counted as overtime for the employee." msgstr "" -#: ../../content/applications/hr/attendances.rst:133 -msgid ":guilabel:`Tolerance Time In Favor Of Employee`: enter the amount of time, in minutes, that an employee is given, that will not adversely affect their attendance if they log less time than their working hours. When an employee checks out, and the total time logged for the day is less than their specified working hours, and less than this specified grace period, they will not be penalized for their reduced hours." -msgstr "" - -#: ../../content/applications/hr/attendances.rst:138 -msgid ":guilabel:`Display Extra Hours`: activate this box to display the extra hours logged by an employee when they check out with a kiosk, or when a user checks out in the database." +#: ../../content/applications/hr/attendances.rst:135 +msgid ":guilabel:`Tolerance Time In Favor Of Employee`: enter the amount of time, in minutes, that an employee is given, that does **not** adversely affect their attendance if they log less time than their working hours. When an employee checks out, and the total time logged for the day is less than their specified working hours and less than this specified grace period, they are **not** penalized for their reduced hours." msgstr "" #: ../../content/applications/hr/attendances.rst:142 -msgid "A company sets both of the :guilabel:`Tolerance` fields to `15` minutes, and the working hours for the entire company is set from 9:00 AM to 5:00 PM. If an employee checks in at 9:00 AM, and checks out at 5:14 PM, the extra 14 minutes are *not* counted towards their overtime. If an employee checks in at 9:05 AM, and checks out at 4:55 PM, even though they logged a total of 10 minutes less than their full working hours, they will not be penalized for this discrepancy." +msgid "A company sets both of the :guilabel:`Tolerance` fields to `15` minutes, and the working hours for the entire company are set from 9:00 AM to 5:00 PM." +msgstr "" + +#: ../../content/applications/hr/attendances.rst:145 +msgid "If an employee checks in at 9:00 AM, and checks out at 5:14 PM, the extra 14 minutes are **not** counted towards their overtime." +msgstr "" + +#: ../../content/applications/hr/attendances.rst:148 +msgid "If an employee checks in at 9:05 AM, and checks out at 4:55 PM, even though they logged a total of 10 minutes less than their full working hours, they are **not** penalized for this discrepancy." msgstr "" #: ../../content/applications/hr/attendances.rst:152 +msgid ":guilabel:`Display Extra Hours`: activate this box to display the extra hours logged by an employee when they check out with a kiosk, or when a user checks out in the database." +msgstr "" + +#: ../../content/applications/hr/attendances.rst:156 +msgid "Employees are still able to log overtime hours even if the :guilabel:`Count of Extra Hours` option is not activated. The difference is that when :guilabel:`Count of Extra Hours` is activated, the extra hours can be :ref:`deducted from an approved time off request `." +msgstr "" + +#: ../../content/applications/hr/attendances.rst:164 msgid "Check in and out via the database" msgstr "" -#: ../../content/applications/hr/attendances.rst:154 +#: ../../content/applications/hr/attendances.rst:166 msgid "Odoo's *Attendances* application allows users who are logged into the database to check in and out, without needing to go into the *Attendances* application, or use a kiosk. For some smaller companies, where every employee is also a user, this feature may be useful." msgstr "" -#: ../../content/applications/hr/attendances.rst:158 +#: ../../content/applications/hr/attendances.rst:170 msgid "A user can check in and out on the main database dashboard, as well as in any application. In the upper right corner of the top main menu, which is always visible regardless of what application the user is in, a :guilabel:`🔴 (red circle)` or :guilabel:`🟢 (green circle)` is visible. Click on the colored circle to reveal the attendance widget, enabling the user to check in and/or out." msgstr "" +#: ../../content/applications/hr/attendances.rst:-1 #: ../../content/applications/hr/attendances.rst:-1 msgid "Top right main menu with check in button highlighted." msgstr "" -#: ../../content/applications/hr/attendances.rst:168 +#: ../../content/applications/hr/attendances.rst:180 msgid "Check in" msgstr "" -#: ../../content/applications/hr/attendances.rst:170 -msgid "If the attendance widget circle is red, this indicates the user is not currently checked in. Click the :guilabel:`🔴 (red circle)` and the attendance widget appears, displaying a green :guilabel:`Check in ->` button." +#: ../../content/applications/hr/attendances.rst:182 +msgid "If the attendance widget circle is red, this indicates the user is not currently checked in. Click the :guilabel:`🔴 (red circle)` and the attendance widget appears, displaying a green :guilabel:`Check in ➡️` button." msgstr "" -#: ../../content/applications/hr/attendances.rst:178 -msgid "If the user has not checked in and out already during the current work day, this button is the only visible item in the widget. If the user has previously checked in and out, a :guilabel:`Total today` field appears above the button, and the total amount of time that has been logged for the day appears beneath that field, in an :guilabel:`XX:XX` (hours:minutes) format." +#: ../../content/applications/hr/attendances.rst:190 +msgid "When the user checks in from the database, the *Attendances* app logs the location details for the user, including the IP Address and GPS coordinates." msgstr "" -#: ../../content/applications/hr/attendances.rst:183 -msgid "Click the :guilabel:`Check in ->` button to check in. The :guilabel:`🔴 (red circle)` in the top menu changes to green, and the widget changes appearance as well. The widget updates to reflect that the user has checked in, by changing the green :guilabel:`Check in ->` button to a yellow :guilabel:`Check out ->` button." +#: ../../content/applications/hr/attendances.rst:194 +msgid "For the *Attendances* app to log the location details, the user must allow their computer to access their location information." msgstr "" -#: ../../content/applications/hr/attendances.rst:188 +#: ../../content/applications/hr/attendances.rst:197 +msgid "If the user has not checked in and out already during the current work day, this button is the only visible item in the widget. If the user has previously checked in and out, a :guilabel:`Total today` field appears above the button, and the total amount of time that has been logged for the day appears beneath that field, in an :guilabel:`HH:MM` (hours:minutes) format." +msgstr "" + +#: ../../content/applications/hr/attendances.rst:202 +msgid "Click the :guilabel:`Check in ➡️` button to check in. The :guilabel:`🔴 (red circle)` in the top menu changes to green, and the widget changes appearance as well. The widget updates to reflect that the user has checked in, by changing the green :guilabel:`Check in ➡️` button to a yellow :guilabel:`Check out ➡️` button." +msgstr "" + +#: ../../content/applications/hr/attendances.rst:207 msgid "Click anywhere on the screen to close the attendance widget." msgstr "" -#: ../../content/applications/hr/attendances.rst:191 +#: ../../content/applications/hr/attendances.rst:210 msgid "Check out" msgstr "" -#: ../../content/applications/hr/attendances.rst:193 -msgid "If the user is checking out for the first time, :guilabel:`Since XX:XX (AM/PM)` appears at the top of the widget, with the time the user checked in populating the time field. Beneath that line, :guilabel:`XX:XX` is displayed, indicating the hours and minutes that have elapsed since checking in. As time passes, this value is updated to reflect the hours and minutes that have passed since the user checked in." +#: ../../content/applications/hr/attendances.rst:212 +msgid "If the user is checking out for the first time, :guilabel:`Since HH:MM (AM/PM)` appears at the top of the widget, with the time the user checked in populating the time field. Beneath that line, :guilabel:`HH:MM` is displayed, indicating the hours and minutes that have elapsed since checking in. As time passes, this value is updated to reflect the hours and minutes that have passed since the user checked in." msgstr "" -#: ../../content/applications/hr/attendances.rst:199 -msgid "If the user has previously checked in and out, additional fields are presented. A :guilabel:`Before XX:XX (AM/PM)` field appears in addition to the :guilabel:`Since XX:XX (AM/PM)` field. The time displayed in both of these fields are populated with the most recent check in time, and will match. Beneath the :guilabel:`Before XX:XX (AM/PM)` field, the previously logged hours are displayed, in an :guilabel:`XX:XX` (hours:minutes) format." +#: ../../content/applications/hr/attendances.rst:218 +msgid "If the user has previously checked in and out, additional fields are presented. A :guilabel:`Before HH:MM (AM/PM)` field appears in addition to the :guilabel:`Since HH:MM (AM/PM)` field. The time displayed in both of these fields are populated with the most recent check in time, and will match. Beneath the :guilabel:`Before HH:MM (AM/PM)` field, the previously logged hours are displayed, in an :guilabel:`HH:MM` (hours:minutes) format." msgstr "" -#: ../../content/applications/hr/attendances.rst:205 -msgid "In addition, beneath both of these fields, a :guilabel:`Total today` field appears. This field is the sum of both the :guilabel:`Before XX:XX (AM/PM)` and :guilabel:`Since XX:XX (AM/PM)` fields, and is the total time that will be logged for the user, if they were to log out at that moment." +#: ../../content/applications/hr/attendances.rst:224 +msgid "In addition, beneath both of these fields, a :guilabel:`Total today` field appears. This field is the sum of both the :guilabel:`Before HH:MM (AM/PM)` and :guilabel:`Since HH:MM (AM/PM)` fields, and is the total time that will be logged for the user, if they were to log out at that moment." msgstr "" -#: ../../content/applications/hr/attendances.rst:209 -msgid "As time passes, both the :guilabel:`Since XX:XX (AM/PM)` and :guilabel:`Total today` fields are updated live. To check out, click the yellow :guilabel:`Check out ->` button. The attendance widget updates again, displaying the :guilabel:`Total today` field with the logged time, and the yellow :guilabel:`Check out ->` button changes to a green :guilabel:`Check in ->` button." +#: ../../content/applications/hr/attendances.rst:228 +msgid "As time passes, both the :guilabel:`Since HH:MM (AM/PM)` and :guilabel:`Total today` fields are updated live. To check out, click the yellow :guilabel:`Check out ➡️` button. The attendance widget updates again, displaying the :guilabel:`Total today` field with the logged time, and the yellow :guilabel:`Check out ➡️` button changes to a green :guilabel:`Check in ➡️` button." +msgstr "" + +#: ../../content/applications/hr/attendances.rst:233 +msgid "When the user checks out from the database, the *Attendances* app logs the location details for the user. This information is **only** logged if the user allows their computer to access this information." msgstr "" #: ../../content/applications/hr/attendances.rst:-1 msgid "The pop-up that appears when an employee checks in inside the database." msgstr "" -#: ../../content/applications/hr/attendances.rst:219 +#: ../../content/applications/hr/attendances.rst:242 msgid "There is no limit to the amount of times a user can check in and check out. Users are able to check in and out without any time elapsing (a value of 00:00). Each time an employee logs in and out, the information is stored and appears on the dashboard, including check ins and check outs with no time value." msgstr "" -#: ../../content/applications/hr/attendances.rst:225 -msgid "Kiosk Mode" +#: ../../content/applications/hr/attendances.rst:250 +msgid "Kiosk mode" msgstr "" -#: ../../content/applications/hr/attendances.rst:227 +#: ../../content/applications/hr/attendances.rst:252 msgid "Some companies may opt to use a dedicated device (a laptop or desktop PC, a tablet, or a mobile phone) for employees to check in and check out from. Kiosk mode is used for these scenarios." msgstr "" -#: ../../content/applications/hr/attendances.rst:231 -msgid "If users check in and out using either a badge or an RFID, then an accessible device in kiosk mode **must** be available in order to check in and check out using these two methods." +#: ../../content/applications/hr/attendances.rst:256 +msgid "If users check in and out using either a badge or an RFID, then an accessible device in kiosk mode **must** be available to check in and check out using these two methods." msgstr "" -#: ../../content/applications/hr/attendances.rst:234 +#: ../../content/applications/hr/attendances.rst:259 msgid "Entering kiosk mode is only available for users with specific :ref:`access rights `." msgstr "" -#: ../../content/applications/hr/attendances.rst:237 -msgid "There are three ways that kiosk mode can be activated:" +#: ../../content/applications/hr/attendances.rst:262 +msgid "Kiosk mode can be activated in three different ways:" msgstr "" -#: ../../content/applications/hr/attendances.rst:239 +#: ../../content/applications/hr/attendances.rst:264 msgid "Navigate to the :guilabel:`Attendances` application, and click :guilabel:`Kiosk Mode` in the top menu. The device then enters kiosk mode." msgstr "" -#: ../../content/applications/hr/attendances.rst:241 +#: ../../content/applications/hr/attendances.rst:266 msgid "Navigate to the :menuselection:`Attendances application --> Configuration`. In the :guilabel:`Kiosk Settings` section, click on the link in the :guilabel:`Attendance Kiosk Url` field. A new tab opens in kiosk mode. It is recommended to close the database tab to keep the database secure." msgstr "" -#: ../../content/applications/hr/attendances.rst:245 +#: ../../content/applications/hr/attendances.rst:270 msgid "Navigate to the :menuselection:`Attendances application --> Configuration`. In the :guilabel:`Kiosk Settings` section, click :guilabel:`Copy` next to the link beneath the :guilabel:`Attendance Kiosk Url` field. Paste this URL into a web browser on the kiosk device and navigate to it." msgstr "" @@ -1010,15 +1039,15 @@ msgstr "" msgid "The Attendances Kiosk URL field in the settings section of the Attendances application." msgstr "" -#: ../../content/applications/hr/attendances.rst:254 -msgid "As a security measure, once a device is in kiosk mode, it is not possible to exit kiosk mode and go back into the database without singing back in. To exit kiosk mode, click the back button in the web browser. This logs the user out of the database, and returns to the main log in screen. This prevents anyone from accessing the database, adding another layer of security." +#: ../../content/applications/hr/attendances.rst:279 +msgid "As a security measure, once a device is in kiosk mode, it is not possible to exit kiosk mode and go back into the database without signing back in. To exit kiosk mode, click the back button in the web browser. This logs the user out of the database, and returns to the main log in screen. This adds an extra layer of security, preventing anyone from accessing the database." msgstr "" -#: ../../content/applications/hr/attendances.rst:260 +#: ../../content/applications/hr/attendances.rst:285 msgid "Badge" msgstr "" -#: ../../content/applications/hr/attendances.rst:262 +#: ../../content/applications/hr/attendances.rst:287 msgid "To check in or out using a badge, tap the :guilabel:`📷 (camera) Tap to scan` image in the center of the kiosk. Then, scan the barcode on the badge using the method configured in the :ref:`kiosk settings ` section of the configuration menu. Options are a dedicated barcode scanning device, or the kiosk's front or back camera. Once the barcode is scanned, the employee is checked in or out, and a :ref:`confirmation message ` appears with all the check in or check out information." msgstr "" @@ -1026,47 +1055,47 @@ msgstr "" msgid "The Attendances Kiosk view displaying the scan badge image." msgstr "" -#: ../../content/applications/hr/attendances.rst:274 +#: ../../content/applications/hr/attendances.rst:299 msgid "RFID" msgstr "" -#: ../../content/applications/hr/attendances.rst:276 +#: ../../content/applications/hr/attendances.rst:301 msgid "To check in or out using an RFID key fob, simply scan the fob with an RFID reader. Once scanned, the employee is then either checked in or checked out, and a :ref:`confirmation message ` appears with all the check in or check out information." msgstr "" -#: ../../content/applications/hr/attendances.rst:281 +#: ../../content/applications/hr/attendances.rst:306 msgid "Manually" msgstr "" -#: ../../content/applications/hr/attendances.rst:283 +#: ../../content/applications/hr/attendances.rst:308 msgid "Users who do not have a scannable badge or an RFID fob can manually check in and out at a kiosk. Tap the :guilabel:`Identify Manually` button on the kiosk, and a screen with all the employees that can be checked in or out appears. This is the same view as in the *Employees* application dashboard. Tap on the person, and they are either checked in or checked out, and a :ref:`confirmation message ` appears." msgstr "" -#: ../../content/applications/hr/attendances.rst:289 +#: ../../content/applications/hr/attendances.rst:314 msgid "When a large number of employees appear in the list, making scrolling inefficient, there are two ways to quickly find a specific person:" msgstr "" -#: ../../content/applications/hr/attendances.rst:292 +#: ../../content/applications/hr/attendances.rst:317 msgid ":guilabel:`Search...`: tap on the :guilabel:`Search...` field and enter the person's name. As the name is typed in, the matching results are displayed on the screen." msgstr "" -#: ../../content/applications/hr/attendances.rst:294 -msgid ":guilabel:`Department`: to quickly filter the presented employees, tap on a department to display only those employees that are part of that department. The :guilabel:`Departments` are listed on the left side of the screen, and the number at the end of each department indicates how many employees are part of the department, and will be displayed when selected." +#: ../../content/applications/hr/attendances.rst:319 +msgid ":guilabel:`Department`: to quickly filter the presented employees, tap on a department to display only those employees that are part of that department. The :guilabel:`Departments` are listed on the left side of the screen, and the number at the end of each department indicates how many employees are part of the department, and is displayed when selected." msgstr "" -#: ../../content/applications/hr/attendances.rst:300 +#: ../../content/applications/hr/attendances.rst:325 msgid "PIN" msgstr "" -#: ../../content/applications/hr/attendances.rst:302 +#: ../../content/applications/hr/attendances.rst:327 msgid "If the :guilabel:`Employee PIN Identification` option was activated in the :ref:`kiosk settings ` section of the configuration menu, the employee is prompted to enter a PIN when manually checking in or out." msgstr "" -#: ../../content/applications/hr/attendances.rst:306 +#: ../../content/applications/hr/attendances.rst:331 msgid "After the employee is selected, a number pad appears with a message. When checking in, :guilabel:`(Employee) Welcome! Please enter your PIN to check in` appears above the numbers. When checking out, :guilabel:`(Employee) Want to check out? Please enter your PIN to check out` appears above the numbers." msgstr "" -#: ../../content/applications/hr/attendances.rst:311 +#: ../../content/applications/hr/attendances.rst:336 msgid "Tap in the PIN using the number pad, then tap :guilabel:`OK` when done. The employee is then checked in or out, and a :ref:`confirmation message ` appears." msgstr "" @@ -1074,15 +1103,15 @@ msgstr "" msgid "The pop-up that appears when prompted to enter a pin." msgstr "" -#: ../../content/applications/hr/attendances.rst:321 +#: ../../content/applications/hr/attendances.rst:346 msgid "Confirmation message" msgstr "" -#: ../../content/applications/hr/attendances.rst:323 -msgid "When an employee checks in or out, a confirmation message appears with all the check in or check out information. When checking in, a welcome message appears, as well as the date and time of check in. An :guilabel:`Hours Previously Today: XX:XX` field also appears, displaying any time already logged for that employee for the day. If no time has already been logged, the value displayed is `00:00`. Beneath the message is an :guilabel:`OK` button. To exit the screen before the preset time in the kiosk, tap the :guilabel:`OK` button." +#: ../../content/applications/hr/attendances.rst:348 +msgid "When an employee checks in or out, a confirmation message appears with all the check in or check out information. When checking in, a welcome message appears, as well as the date and time of check in. An :guilabel:`Hours Previously Today: HH:MM` field also appears, displaying any time already logged for that employee for the day. If no time has already been logged, the value displayed is `00:00`. Beneath the message is an :guilabel:`OK` button. To exit the screen before the preset time in the kiosk, tap the :guilabel:`OK` button." msgstr "" -#: ../../content/applications/hr/attendances.rst:330 +#: ../../content/applications/hr/attendances.rst:355 msgid "When checking out, the screen displays a goodbye message, with the date and time of check out, and the total hours logged for the day. Beneath the message is a :guilabel:`Goodbye` button. To exit the screen before the preset time, tap the :guilabel:`Goodbye` button." msgstr "" @@ -1090,28 +1119,28 @@ msgstr "" msgid "The goodbye message with all the employee's check out information." msgstr "" -#: ../../content/applications/hr/attendances.rst:339 -#: ../../content/applications/hr/time_off.rst:307 +#: ../../content/applications/hr/attendances.rst:364 +#: ../../content/applications/hr/time_off.rst:309 msgid "Overview" msgstr "" -#: ../../content/applications/hr/attendances.rst:341 +#: ../../content/applications/hr/attendances.rst:366 msgid "When entering the *Attendances* application, the :guilabel:`Overview` dashboard is presented, containing all the check in and check out information for the signed in user. If the user has specific :ref:`access rights ` and/or are :ref:`approvers ` for specific employees, then those additional employee's check in and check out information is also visible on the :guilabel:`Overview` dashboard." msgstr "" -#: ../../content/applications/hr/attendances.rst:348 +#: ../../content/applications/hr/attendances.rst:373 msgid "Views" msgstr "" -#: ../../content/applications/hr/attendances.rst:350 +#: ../../content/applications/hr/attendances.rst:375 msgid "To change the view from the default Gantt chart to a list view, click the :guilabel:`List` icon in the top right of the dashboard, beneath the user's photo. To switch back to the Gantt chart, click the :guilabel:`Gantt` button, located next to the :guilabel:`List` button." msgstr "" -#: ../../content/applications/hr/attendances.rst:354 -msgid "The default view presents the current day's information. To present the information for the :guilabel:`Week`, :guilabel:`Month`, or :guilabel:`Year`, click on the :guilabel:`Day` button to reveal a drop-down, displaying those other options. Select the desired view, and the dashboard will update, presenting the selected information. To change the :guilabel:`Day`, :guilabel:`Week`, :guilabel:`Month`, or :guilabel:`Year` presented, click the left or right :guilabel:`arrow` buttons on either side of the drop-down button. To jump back to a view containing the current day, click the :guilabel:`Today` button. The refreshed the dashboard, presenting information containing the current day's information." +#: ../../content/applications/hr/attendances.rst:379 +msgid "The default view presents the current day's information. To present the information for the :guilabel:`Week`, :guilabel:`Month`, or :guilabel:`Year`, click on the :guilabel:`Day` button to reveal a drop-down, displaying those other options. Select the desired view, and the dashboard updates, presenting the selected information. To change the :guilabel:`Day`, :guilabel:`Week`, :guilabel:`Month`, or :guilabel:`Year` presented, click the :guilabel:`← (left arrow)` or :guilabel:`→ (right arrow)` buttons on either side of the drop-down menu. To jump back to a view containing the current day, click the :guilabel:`Today` button. This refreshes the dashboard, presenting information containing the current day's information." msgstr "" -#: ../../content/applications/hr/attendances.rst:363 +#: ../../content/applications/hr/attendances.rst:388 msgid "In the :guilabel:`Day` view, the column for the current hour is highlighted in yellow. If the :guilabel:`Week` or :guilabel:`Month` view is selected, the column for the current day is highlighted. If the :guilabel:`Year` view is selected, the current month is highlighted." msgstr "" @@ -1120,91 +1149,168 @@ msgid "The overview dashboard presenting the information for the week, with the "highlighted." msgstr "" -#: ../../content/applications/hr/attendances.rst:372 +#: ../../content/applications/hr/attendances.rst:397 msgid "Any entries that have errors appear in red, indicating they need to be resolved by a user with the proper :ref:`access rights ` and/or are :ref:`approvers ` for the employee(s) with the errors." msgstr "" -#: ../../content/applications/hr/attendances.rst:379 -msgid "Filters and Groups" +#: ../../content/applications/hr/attendances.rst:404 +msgid "Filters and groups" msgstr "" -#: ../../content/applications/hr/attendances.rst:381 -msgid "To filter the results in the dashboard or to present different groups of information, click the drop-down button in the :guilabel:`Search` bar above the dashboard, then select one of the available :guilabel:`Filters` or :guilabel:`Group By` options. There are several pre-configured filters and groups to choose from, as well as an option to create custom ones." +#: ../../content/applications/hr/attendances.rst:406 +msgid "To filter the results in the overview dashboard, or to present different groups of information, click the :guilabel:`🔻 (triangle drop down)` button in the right side of the :guilabel:`Search` bar above the dashboard, and select one of the available :guilabel:`Filters` or :guilabel:`Group By` options. There are several pre-configured filters and groups to choose from, as well as an option to create custom ones." msgstr "" -#: ../../content/applications/hr/attendances.rst:387 +#: ../../content/applications/hr/attendances.rst:413 +#: ../../content/applications/hr/payroll/reporting.rst:276 msgid "Filters" msgstr "" -#: ../../content/applications/hr/attendances.rst:389 +#: ../../content/applications/hr/attendances.rst:415 msgid "The default filters that can be selected are:" msgstr "" -#: ../../content/applications/hr/attendances.rst:391 +#: ../../content/applications/hr/attendances.rst:417 msgid ":guilabel:`My Attendances`: this filter only presents the user's attendance data." msgstr "" -#: ../../content/applications/hr/attendances.rst:392 +#: ../../content/applications/hr/attendances.rst:418 msgid ":guilabel:`My Team`: this filter presents the attendance data for the user's team." msgstr "" -#: ../../content/applications/hr/attendances.rst:393 +#: ../../content/applications/hr/attendances.rst:419 msgid ":guilabel:`At Work`: this filter displays the attendance data for everyone currently checked in." msgstr "" -#: ../../content/applications/hr/attendances.rst:394 +#: ../../content/applications/hr/attendances.rst:420 msgid ":guilabel:`Errors`: this filter displays any entries with :ref:`errors ` that need to be resolved." msgstr "" -#: ../../content/applications/hr/attendances.rst:396 +#: ../../content/applications/hr/attendances.rst:422 msgid ":guilabel:`Check In`: this filter has a drop-down to further select a specific time period. Select the desired time period from the options presented, a specific month, quarter, or year." msgstr "" -#: ../../content/applications/hr/attendances.rst:398 +#: ../../content/applications/hr/attendances.rst:424 msgid ":guilabel:`Last 7 days`: this filter presents the attendance data for the last seven days." msgstr "" -#: ../../content/applications/hr/attendances.rst:399 +#: ../../content/applications/hr/attendances.rst:425 msgid ":guilabel:`Add Custom Filter`: create a custom filter using the pop-up that appears when this is selected." msgstr "" -#: ../../content/applications/hr/attendances.rst:403 +#: ../../content/applications/hr/attendances.rst:429 msgid "Groups" msgstr "" -#: ../../content/applications/hr/attendances.rst:405 +#: ../../content/applications/hr/attendances.rst:431 msgid "The default groups that can be selected are:" msgstr "" -#: ../../content/applications/hr/attendances.rst:407 +#: ../../content/applications/hr/attendances.rst:433 msgid ":guilabel:`Check In`: this grouping presents a drop-down menu containing the following time period options: :guilabel:`Year`, :guilabel:`Quarter`, :guilabel:`Month`, :guilabel:`Week`, and :guilabel:`Day`. Selected the time period to display all the check-in information, grouped by the selected time period." msgstr "" -#: ../../content/applications/hr/attendances.rst:411 +#: ../../content/applications/hr/attendances.rst:437 msgid ":guilabel:`Employee`: this group presents the attendance data organized by employee." msgstr "" -#: ../../content/applications/hr/attendances.rst:412 +#: ../../content/applications/hr/attendances.rst:438 msgid ":guilabel:`Check Out`: this grouping presents a drop-down menu containing the following time period options: :guilabel:`Year`, :guilabel:`Quarter`, :guilabel:`Month`, :guilabel:`Week`, and :guilabel:`Day`. Selected the time period to display all the check-out information, grouped by the selected time period." msgstr "" -#: ../../content/applications/hr/attendances.rst:416 +#: ../../content/applications/hr/attendances.rst:442 msgid ":guilabel:`Add Custom Group`: this option displays a drop-down menu with a variety of options to group the attendance data by, including :guilabel:`City`, :guilabel:`Country`, :guilabel:`Mode`, and :guilabel:`IP Address`." msgstr "" -#: ../../content/applications/hr/attendances.rst:423 +#: ../../content/applications/hr/attendances.rst:449 +msgid "Attendance log details" +msgstr "" + +#: ../../content/applications/hr/attendances.rst:451 +msgid "Odoo captures various time and location details when a user checks in and out. The specific details provided are determined by the method the user checked in and out." +msgstr "" + +#: ../../content/applications/hr/attendances.rst:454 +msgid "To view the specific check in and/or check out details for an employee, click on an individual entry in the overview dashboard." +msgstr "" + +#: ../../content/applications/hr/attendances.rst:457 +msgid "A detailed attendance log for the user appears in a pop-up window. To close the detailed attendance log, click the :guilabel:`Save & Close` button in the bottom-left corner of the form." +msgstr "" + +#: ../../content/applications/hr/attendances.rst:460 +msgid "The detailed attendance log contains the following information:" +msgstr "" + +#: ../../content/applications/hr/attendances.rst:463 +msgid "Main details" +msgstr "" + +#: ../../content/applications/hr/attendances.rst:465 +msgid ":guilabel:`Employee`: the name of the employee." +msgstr "" + +#: ../../content/applications/hr/attendances.rst:466 +msgid ":guilabel:`Check In`: the date and time the employee checked in." +msgstr "" + +#: ../../content/applications/hr/attendances.rst:467 +msgid ":guilabel:`Check Out`: the date and time the employee checked out. This only appears if the employee has checked out." +msgstr "" + +#: ../../content/applications/hr/attendances.rst:469 +msgid ":guilabel:`Worked Hours`: the total amount of time the employee logged for the day, in an hour and minute format (HH:MM). This value calculates all the checks in and check outs for the day, if the employee checked in and out multiple times." +msgstr "" + +#: ../../content/applications/hr/attendances.rst:472 +msgid ":guilabel:`Extra Hours`: any extra hours the employee logged that is beyond their expected working hours." +msgstr "" + +#: ../../content/applications/hr/attendances.rst:476 +msgid "Check in/check out details" +msgstr "" + +#: ../../content/applications/hr/attendances.rst:478 +msgid "The following information appears for both the :guilabel:`Check In` and :guilabel:`Check Out` sections." +msgstr "" + +#: ../../content/applications/hr/attendances.rst:481 +msgid ":guilabel:`Mode`: the method with which the attendance information was gathered. :guilabel:`Systray` is displayed if the employee logged in and out :ref:`directly from the database `, :guilabel:`Manual` is displayed if the employee logged in and out :ref:`using an attendance kiosk `." +msgstr "" + +#: ../../content/applications/hr/attendances.rst:485 +msgid ":guilabel:`IP Address`: the IP address for the computer the employee used to log in or out." +msgstr "" + +#: ../../content/applications/hr/attendances.rst:486 +msgid ":guilabel:`Browser`: the web browser the employee used to log in or out." +msgstr "" + +#: ../../content/applications/hr/attendances.rst:487 +msgid ":guilabel:`Localization`: the city and country associated with the computer's IP address." +msgstr "" + +#: ../../content/applications/hr/attendances.rst:488 +msgid ":guilabel:`GPS Coordinates`: the specific coordinates when the user logged in or out. To view the specific coordinates on a map, click the :guilabel:`→ View on Maps` button beneath the :guilabel:`GPS Coordinates`. This opens a map in a new browser tab, with the specific location pointed out." +msgstr "" + +#: ../../content/applications/hr/attendances.rst:-1 +msgid "The detailed information for an attendance entry." +msgstr "" + +#: ../../content/applications/hr/attendances.rst:498 msgid "Errors" msgstr "" -#: ../../content/applications/hr/attendances.rst:425 -msgid "Entries that contain an error appear on the dashboard in red. In the :guilabel:`Gantt view`, the entry appears with a red background. If in the :guilabel:`List view`, the entry text appears in red." +#: ../../content/applications/hr/attendances.rst:500 +msgid "Entries that contain an error appear on the overview dashboard in red. In the :guilabel:`Gantt view`, the entry appears with a red background. If in the :guilabel:`List view`, the entry text appears in red." msgstr "" -#: ../../content/applications/hr/attendances.rst:428 +#: ../../content/applications/hr/attendances.rst:504 msgid "An error typically occurs when an employee has checked in but has not checked out within the last 24 hours, or when an employee has a check in and check out period spanning over 16 hours." msgstr "" -#: ../../content/applications/hr/attendances.rst:431 +#: ../../content/applications/hr/attendances.rst:507 msgid "To fix the error, the attendance entry must be modified or deleted. Click on the entry to reveal a pop-up containing the details for that particular entry. To modify the :guilabel:`Check In` and/or :guilabel:`Check Out` information, click on the :guilabel:`Check In` or :guilabel:`Check Out` field and a calendar selector appears. Click on the desired date, then use the time selector beneath the calendar to select the specific time for the entry. When the information is correct, click :guilabel:`Apply.`" msgstr "" @@ -1213,35 +1319,35 @@ msgid "The pop-up that allows for modifications to an attendance entry with an e "selector is shown, and the time selector is highlighted." msgstr "" -#: ../../content/applications/hr/attendances.rst:443 +#: ../../content/applications/hr/attendances.rst:519 msgid "When all the information on the pop-up is correct, click :guilabel:`Save & Close`. When the entry no longer has an error, the entry appears in gray instead of red." msgstr "" -#: ../../content/applications/hr/attendances.rst:446 +#: ../../content/applications/hr/attendances.rst:522 msgid "To delete an entry, click :guilabel:`Remove` on the pop-up instead of making modifications to the entry." msgstr "" -#: ../../content/applications/hr/attendances.rst:452 +#: ../../content/applications/hr/attendances.rst:528 msgid "To view attendance reports, click :guilabel:`Reporting` in the top menu. The default report displays each employee's attendance information for the past 3 months, in a :guilabel:`Line Chart`." msgstr "" -#: ../../content/applications/hr/attendances.rst:455 +#: ../../content/applications/hr/attendances.rst:531 msgid "The default view is a :guilabel:`Graph`. To view the data in a pivot table, click the :guilabel:`Pivot Table` button on the top right of the report. To switch back to the graph view, click the :guilabel:`Graph` button, located next to the :guilabel:`Pivot Table` button." msgstr "" -#: ../../content/applications/hr/attendances.rst:459 +#: ../../content/applications/hr/attendances.rst:535 msgid "To present different information, adjust the :ref:`filters and groups ` in the same way as in the :guilabel:`Overview` dashboard." msgstr "" -#: ../../content/applications/hr/attendances.rst:462 +#: ../../content/applications/hr/attendances.rst:538 msgid "The data can be presented in either a :guilabel:`Bar Chart`, :guilabel:`Line Chart`, :guilabel:`Pie Chart`, :guilabel:`Stacked` chart, or in :guilabel:`Descending` or :guilabel:`Ascending` order. To change the view to any of these charts, click the corresponding button above the displayed chart." msgstr "" -#: ../../content/applications/hr/attendances.rst:466 +#: ../../content/applications/hr/attendances.rst:542 msgid "To change the :guilabel:`Measures`, click the :guilabel:`Measures` button and select the desired measure from the drop-down menu." msgstr "" -#: ../../content/applications/hr/attendances.rst:469 +#: ../../content/applications/hr/attendances.rst:545 msgid "The report can also be inserted into a spreadsheet. Click the :guilabel:`Insert in Spreadsheet` button and a pop-up appears. Select the desired spreadsheet, and click :guilabel:`Confirm`." msgstr "" @@ -1327,7 +1433,7 @@ msgid "Odoo *Employees* organizes a company's employee records, contracts, and d msgstr "" #: ../../content/applications/hr/employees/new_employee.rst:3 -msgid "Create new employees" +msgid "New employees" msgstr "" #: ../../content/applications/hr/employees/new_employee.rst:5 @@ -1360,7 +1466,6 @@ msgstr "" #: ../../content/applications/hr/employees/new_employee.rst:35 #: ../../content/applications/hr/payroll/contracts.rst:39 -#: ../../content/applications/hr/payroll/payslips.rst:51 msgid "Required fields" msgstr "" @@ -1378,8 +1483,7 @@ msgstr "" #: ../../content/applications/hr/employees/new_employee.rst:47 #: ../../content/applications/hr/payroll/contracts.rst:66 -#: ../../content/applications/hr/payroll/payslips.rst:91 -#: ../../content/applications/hr/recruitment.rst:737 +#: ../../content/applications/hr/recruitment.rst:736 msgid "Optional fields" msgstr "" @@ -1626,6 +1730,7 @@ msgid "Click the :guilabel:`Internal Link` arrow to open a form with the approve msgstr "" #: ../../content/applications/hr/employees/new_employee.rst:276 +#: ../../content/applications/hr/employees/new_employee.rst:351 msgid "The users that appear in the drop-down menu for the :guilabel:`Approvers` section **must** have *Administrator* rights set for the corresponding human resources role." msgstr "" @@ -1634,6 +1739,7 @@ msgid "To check who has these rights, go to :menuselection:`Settings app --> Use msgstr "" #: ../../content/applications/hr/employees/new_employee.rst:283 +#: ../../content/applications/hr/employees/new_employee.rst:358 msgid "In order for the user to appear as an approver for :guilabel:`Expenses`, they **must** have either :guilabel:`Team Approver`, :guilabel:`All Approver`, or :guilabel:`Administrator` set for the :guilabel:`Expenses` role." msgstr "" @@ -1717,159 +1823,183 @@ msgstr "" msgid ":guilabel:`Planning`: select a role from the drop-down menu for both the :guilabel:`Roles` and the :guilabel:`Default Role` fields. If the :guilabel:`Default Role` is selected as a role, it is automatically added to the list of :guilabel:`Roles`." msgstr "" -#: ../../content/applications/hr/employees/new_employee.rst:351 -msgid "The :guilabel:`Planning` section affects the *Planning* application and **only** appears if the *Planning* application is installed." -msgstr "" - #: ../../content/applications/hr/employees/new_employee.rst:354 -msgid "If an employee has assigned :guilabel:`Roles`, they are **only** assigned to shifts for these roles." +msgid "To check who has these rights, go to :menuselection:`Settings app --> Users --> → Manage Users`. Click on an employee, and check the :guilabel:`Human Resources` section of the :guilabel:`Access Rights` tab." msgstr "" -#: ../../content/applications/hr/employees/new_employee.rst:357 -msgid "If this field is blank, they are assigned shifts, regardless of the role. The :guilabel:`Default Role` has precedence over the other roles when assigning shifts." +#: ../../content/applications/hr/employees/new_employee.rst:361 +msgid "In order for the user to appear as an approver for :guilabel:`Time Off`, they **must** have either :guilabel:`Officer` or :guilabel:`Administrator` set for the :guilabel:`Time Off` role." msgstr "" #: ../../content/applications/hr/employees/new_employee.rst:363 +msgid "In order for the user to appear as an approver for :guilabel:`Timesheets`, they **must** have either :guilabel:`Manager`, :guilabel:`Officer`, or :guilabel:`Administrator` set for the :guilabel:`Payroll` role." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:368 +msgid ":guilabel:`Working Hours` are related to a company's working times, and an employee **cannot** have working hours that are outside of a company's working times." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:371 +msgid "Each individual working time is company-specific. So, for multi-company databases, each company **must** have its own working hours set." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:374 +msgid "If an employee's working hours are not configured as a working time for the company, new working times can be added, or existing working times can be modified." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:377 +msgid "To add or modify a working time, go to the :menuselection:`Payroll app --> Configuration --> Working Schedules`. Then, either add a new working time by clicking :guilabel:`New`, or edit an existing one by selecting a :guilabel:`Working Time` from the list to modify it." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:381 +msgid "Refer to the :ref:`Working schedules ` section of the payroll documentation for specific details on creating and editing working schedules." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:384 +msgid "After the new working time is created, or an existing one is modified, the :guilabel:`Working Hours` can be set on the employee form. In the :guilabel:`Schedule` section of the :guilabel:`Work Information` tab, select the employee's working hours using the drop-down menu." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:391 msgid "Private information tab" msgstr "" -#: ../../content/applications/hr/employees/new_employee.rst:365 +#: ../../content/applications/hr/employees/new_employee.rst:393 msgid "No information in the :guilabel:`Private Information` tab is required to create an employee, however, some information in this section may be critical for the company's payroll department. In order to properly process payslips and ensure all deductions are accounted for, the employee's personal information should be entered." msgstr "" -#: ../../content/applications/hr/employees/new_employee.rst:370 +#: ../../content/applications/hr/employees/new_employee.rst:398 msgid "Here, the employee's :guilabel:`Private Contact`, :guilabel:`Family Status`, :guilabel:`Emergency` contact, :guilabel:`Education`, :guilabel:`Work Permit`, and :guilabel:`Citizenship` information is entered. Fields are entered either using a drop-down menu, ticking a checkbox, or typing in the information." msgstr "" -#: ../../content/applications/hr/employees/new_employee.rst:375 +#: ../../content/applications/hr/employees/new_employee.rst:403 msgid ":guilabel:`Private Contact`: enter the :guilabel:`Private Address`, :guilabel:`Email`, and :guilabel:`Phone` for the employee. Then, enter the employee's :guilabel:`Bank Account Number` using the drop-down menu." msgstr "" -#: ../../content/applications/hr/employees/new_employee.rst:379 +#: ../../content/applications/hr/employees/new_employee.rst:407 msgid "If the bank is not already configured (the typical situation when creating a new employee), enter the bank account number, and click :guilabel:`Create and edit..`. A :guilabel:`Create Bank Account Number` form loads. Fill in the necessary information, then click :guilabel:`Save & Close`." msgstr "" -#: ../../content/applications/hr/employees/new_employee.rst:383 +#: ../../content/applications/hr/employees/new_employee.rst:411 msgid "Next, select the employee's preferred :guilabel:`Language` from the drop-down menu. Then enter the :guilabel:`Home-Work Distance` in the field. This field is only necessary if the employee is receiving any type of commuter benefits." msgstr "" -#: ../../content/applications/hr/employees/new_employee.rst:387 +#: ../../content/applications/hr/employees/new_employee.rst:415 msgid "Lastly, enter the employee's license plate information in the :guilabel:`Private Car Plate` field." msgstr "" -#: ../../content/applications/hr/employees/new_employee.rst:388 +#: ../../content/applications/hr/employees/new_employee.rst:416 msgid ":guilabel:`Family Status`: select the current :guilabel:`Marital Status` using the drop-down menu, either :guilabel:`Single`, :guilabel:`Married`, :guilabel:`Legal Cohabitant`, :guilabel:`Widower`, or :guilabel:`Divorced`. If the employee has any dependent children, enter the :guilabel:`Number of Dependent Children` in the field." msgstr "" -#: ../../content/applications/hr/employees/new_employee.rst:392 +#: ../../content/applications/hr/employees/new_employee.rst:420 msgid ":guilabel:`Emergency`: type in the :guilabel:`Contact Name` and :guilabel:`Contact Phone` number of the employee's emergency contact in the respective fields." msgstr "" -#: ../../content/applications/hr/employees/new_employee.rst:394 +#: ../../content/applications/hr/employees/new_employee.rst:422 msgid ":guilabel:`Education`: select the highest level of education completed by the employee from the :guilabel:`Certificate Level` drop-down menu. Default options include :guilabel:`Graduate`, :guilabel:`Bachelor`, :guilabel:`Master`, :guilabel:`Doctor`, or :guilabel:`Other`." msgstr "" -#: ../../content/applications/hr/employees/new_employee.rst:398 +#: ../../content/applications/hr/employees/new_employee.rst:426 msgid "Type in the :guilabel:`Field of Study`, and the name of the :guilabel:`School` in the respective fields." msgstr "" -#: ../../content/applications/hr/employees/new_employee.rst:400 +#: ../../content/applications/hr/employees/new_employee.rst:428 msgid ":guilabel:`Work Permit`: if the employee has a work permit, enter the information in this section. Type in the :guilabel:`Visa No` (visa number), and/or :guilabel:`Work Permit No` (work permit number) in the corresponding fields." msgstr "" -#: ../../content/applications/hr/employees/new_employee.rst:404 +#: ../../content/applications/hr/employees/new_employee.rst:432 msgid "Using the calendar selector, select the :guilabel:`Visa Expiration Date`, and/or the :guilabel:`Work Permit Expiration Date`, to enter the expiration date(s)." msgstr "" -#: ../../content/applications/hr/employees/new_employee.rst:407 +#: ../../content/applications/hr/employees/new_employee.rst:435 msgid "If available, upload a digital copy of the :guilabel:`Work Permit` document. Click :guilabel:`Upload your file`, navigate to the work permit file in the file explorer, and click :guilabel:`Open`." msgstr "" -#: ../../content/applications/hr/employees/new_employee.rst:410 +#: ../../content/applications/hr/employees/new_employee.rst:438 msgid ":guilabel:`Citizenship`: this section contains all the information relevant to the citizenship of the employee. Some fields use a drop-down menu, as the :guilabel:`Nationality (Country)`, :guilabel:`Gender`, and :guilabel:`Country of Birth` fields do." msgstr "" -#: ../../content/applications/hr/employees/new_employee.rst:414 +#: ../../content/applications/hr/employees/new_employee.rst:442 msgid "The :guilabel:`Date of Birth` uses a calendar selector to select the date. First, click on the name of the month, then the year, to access the year ranges. Use the :guilabel:`< (left)` and :guilabel:`> (right)` arrow icons, navigate to the correct year range, and click on the year. Next, click on the month. Last, click on the day to select the date." msgstr "" -#: ../../content/applications/hr/employees/new_employee.rst:419 +#: ../../content/applications/hr/employees/new_employee.rst:447 msgid "Type in the information for the :guilabel:`Identification No` (identification number), :guilabel:`Passport No` (passport number), and :guilabel:`Place of Birth` fields." msgstr "" -#: ../../content/applications/hr/employees/new_employee.rst:422 +#: ../../content/applications/hr/employees/new_employee.rst:450 msgid "Lastly, if the employee is **not** a resident of the country they are working in, activate the checkbox next to the :guilabel:`Non-resident` field." msgstr "" -#: ../../content/applications/hr/employees/new_employee.rst:426 +#: ../../content/applications/hr/employees/new_employee.rst:454 msgid "Depending on the localization setting, other fields may be present. For example, for the United States, a :guilabel:`SSN No` (Social Security Number) field is present." msgstr "" -#: ../../content/applications/hr/employees/new_employee.rst:432 +#: ../../content/applications/hr/employees/new_employee.rst:460 msgid "HR settings tab" msgstr "" -#: ../../content/applications/hr/employees/new_employee.rst:434 +#: ../../content/applications/hr/employees/new_employee.rst:462 msgid "This tab provides various fields for different information, depending on the country the company is located. Different fields are configured for different locations, however some sections appear regardless." msgstr "" -#: ../../content/applications/hr/employees/new_employee.rst:438 +#: ../../content/applications/hr/employees/new_employee.rst:466 msgid ":guilabel:`Status`: select an :guilabel:`Employee Type` and, if applicable, a :guilabel:`Related User`, with the drop-down menus. The :guilabel:`Employee Type` options include :guilabel:`Employee`, :guilabel:`Student`, :guilabel:`Trainee`, :guilabel:`Contractor`, or :guilabel:`Freelancer`." msgstr "" -#: ../../content/applications/hr/employees/new_employee.rst:444 +#: ../../content/applications/hr/employees/new_employee.rst:472 msgid "Employees do **not** also need to be users. *Employees* do **not** count towards the Odoo subscription billing, while *Users* **do** count towards billing. If the new employee should also be a user, the user **must** be created." msgstr "" -#: ../../content/applications/hr/employees/new_employee.rst:448 +#: ../../content/applications/hr/employees/new_employee.rst:476 msgid "After the employee is created, click the :guilabel:`⚙️ (gear)` icon, then click :guilabel:`Create User`. A :guilabel:`Create User` form appears." msgstr "" -#: ../../content/applications/hr/employees/new_employee.rst:451 +#: ../../content/applications/hr/employees/new_employee.rst:479 msgid "Type in the :guilabel:`Name` and :guilabel:`Email Address`. Next, select the :guilabel:`Company` from the drop-down menu." msgstr "" -#: ../../content/applications/hr/employees/new_employee.rst:454 +#: ../../content/applications/hr/employees/new_employee.rst:482 msgid "Then, enter the :guilabel:`Phone` and :guilabel:`Mobile` numbers in the respective fields." msgstr "" -#: ../../content/applications/hr/employees/new_employee.rst:456 +#: ../../content/applications/hr/employees/new_employee.rst:484 msgid "If a photo is available, click the :guilabel:`Edit` icon (which appears as a :guilabel:`✏️ (pencil)` icon) in the lower-left corner of the image box, which is located in the top-right corner of the form." msgstr "" -#: ../../content/applications/hr/employees/new_employee.rst:460 +#: ../../content/applications/hr/employees/new_employee.rst:488 msgid "A file explorer pops up. Navigate to the file, then click :guilabel:`Open` to select it. Finally, click :guilabel:`Save` after all the information is entered, and the employee record is automatically updated with the newly-created user populating the :guilabel:`Related User field`." msgstr "" -#: ../../content/applications/hr/employees/new_employee.rst:465 -msgid "Users can also be created manually. For more information on how to manually add a user, refer to the :doc:`../../general/users/manage_users` document." +#: ../../content/applications/hr/employees/new_employee.rst:493 +msgid "Users can also be created manually. For more information on how to manually add a user, refer to the :doc:`../../general/users/` document." msgstr "" -#: ../../content/applications/hr/employees/new_employee.rst:468 +#: ../../content/applications/hr/employees/new_employee.rst:496 msgid ":guilabel:`Attendance/Point of Sale/Manufacturing`: the employee's :guilabel:`PIN Code` and :guilabel:`Badge ID` can be entered here, if the employee needs/has one. Click :guilabel:`Generate` next to the :guilabel:`Badge ID` to create a badge ID." msgstr "" -#: ../../content/applications/hr/employees/new_employee.rst:472 +#: ../../content/applications/hr/employees/new_employee.rst:500 msgid "The :guilabel:`PIN Code` is used to sign in and out of the *Attendance* app kiosk, and a :abbr:`POS (Point Of Sale)` system." msgstr "" -#: ../../content/applications/hr/employees/new_employee.rst:474 +#: ../../content/applications/hr/employees/new_employee.rst:502 msgid ":guilabel:`Payroll`: if applicable, enter the :guilabel:`Registration Number of the Employee` in this section." msgstr "" -#: ../../content/applications/hr/employees/new_employee.rst:477 +#: ../../content/applications/hr/employees/new_employee.rst:505 msgid "Depending on the localization setting, the other items that appear in this field vary based on location. In addition, other sections may appear in this tab based on location. It is recommended to check with the payroll and/or accounting departments to ensure this section, as well as any other sections relating to payroll that may appear, are filled in correctly." msgstr "" -#: ../../content/applications/hr/employees/new_employee.rst:481 +#: ../../content/applications/hr/employees/new_employee.rst:509 msgid ":guilabel:`Application Settings`: enter the employee's :guilabel:`Billing Time Target` for the billing rate leader board in the *Timesheets* application. Next, enter the :guilabel:`Hourly Cost` in a XX.XX format. This is factored in when the employee is working at a :doc:`work center <../../inventory_and_mrp/manufacturing/management/using_work_centers>`." msgstr "" -#: ../../content/applications/hr/employees/new_employee.rst:486 +#: ../../content/applications/hr/employees/new_employee.rst:514 msgid "If applicable, enter the :guilabel:`Fleet Mobility Card` number." msgstr "" -#: ../../content/applications/hr/employees/new_employee.rst:489 +#: ../../content/applications/hr/employees/new_employee.rst:517 msgid "Manufacturing costs are added to the costs for producing a product, if the value of the manufactured product is **not** a fixed amount. This cost does **not** affect the *Payroll* application." msgstr "" @@ -1877,16 +2007,16 @@ msgstr "" msgid "Enter any information prompted in the HR Settings tab for the employee." msgstr "" -#: ../../content/applications/hr/employees/new_employee.rst:500 +#: ../../content/applications/hr/employees/new_employee.rst:528 msgid "Documents" msgstr "" -#: ../../content/applications/hr/employees/new_employee.rst:502 +#: ../../content/applications/hr/employees/new_employee.rst:530 msgid "All employee-related documents are stored in the *Documents* app. The number of associated documents is displayed in the :guilabel:`Documents` smart button above the employee record. Click on the smart button to access all documents." msgstr "" -#: ../../content/applications/hr/employees/new_employee.rst:506 -msgid "Refer to :doc:`documentation <../../finance/documents>` on the *Documents* app for more information." +#: ../../content/applications/hr/employees/new_employee.rst:534 +msgid "Refer to :doc:`documentation <../../productivity/documents>` on the *Documents* app for more information." msgstr "" #: ../../content/applications/hr/employees/new_employee.rst:-1 @@ -1906,11 +2036,11 @@ msgid "Configuration menu" msgstr "" #: ../../content/applications/hr/fleet/configuration.rst:5 -msgid "This document outlines all of the configurations and settings for the *Fleet* application, including :ref:`settings `, :ref:`manufacturers `, :ref:`vehicle models `, and :ref:`model categories `." +msgid "This document outlines all of the configurations and settings for the *Fleet* application, including :ref:`settings `, :ref:`manufacturers `, vehicle :ref:`models `, and model :ref:`categories `." msgstr "" #: ../../content/applications/hr/fleet/configuration.rst:15 -msgid "To access the settings menu, go to :menuselection:`Fleet application --> Configuration --> Settings`. There are two settings that need configuration, the vehicle contract end date alert delay, and a new vehicle request limit." +msgid "To access the settings menu, go to :menuselection:`Fleet application --> Configuration --> Settings`. There are two settings that need configuration, the vehicle contract end date alert, and a new vehicle request limit." msgstr "" #: ../../content/applications/hr/fleet/configuration.rst:-1 @@ -1918,15 +2048,15 @@ msgid "Settings available for the Fleet application." msgstr "" #: ../../content/applications/hr/fleet/configuration.rst:24 -msgid "End Date Contract Alert" +msgid "End date contract alert" msgstr "" #: ../../content/applications/hr/fleet/configuration.rst:26 -msgid "The :guilabel:`End Date Contract Alert` field defines an alert delay for the persons responsible for vehicle contracts. The responsible person(s) will receive an email informing them a vehicle contract is about to expire in the number of days defined in this field." +msgid "The :guilabel:`End Date Contract Alert` field defines when an alert is sent to the persons responsible for the vehicle contracts. The responsible persons receive an email informing them when a vehicle contract is expiring. How far in advance the email is sent is defined in this field." msgstr "" #: ../../content/applications/hr/fleet/configuration.rst:31 -msgid "To determine who the responsible person is for a contract, open an individual contract. The person listed as :guilabel:`Responsible` under the :guilabel:`Contract Information` section of the contract is the person who will receive the alert." +msgid "To determine who the responsible person is for a contract, open an individual contract. The person listed as :guilabel:`Responsible` under the :guilabel:`Information` section of the contract is the one who receives the alert." msgstr "" #: ../../content/applications/hr/fleet/configuration.rst:35 @@ -1934,15 +2064,15 @@ msgid "To access all contracts, navigate to :menuselection:`Fleet app --> Fleet msgstr "" #: ../../content/applications/hr/fleet/configuration.rst:38 -msgid "An individual contract can also be found by navigating to :menuselection:`Fleet app --> Fleet --> Fleet` and clicking on an individual vehicle. On the vehicle form, click the :guilabel:`Contracts` smart button at the top of the page. The contract(s) associated with this vehicle only appears in the list. Click on an individual contract to open it. The :guilabel:`Responsible` person is listed on the contract." +msgid "An individual contract can also be found by navigating to :menuselection:`Fleet app --> Fleet --> Fleet` and clicking on an individual vehicle card. On the vehicle form, click the :guilabel:`Contracts` smart button at the top of the page. The contracts associated only with this vehicle appear in the list. Click on an individual contract to open it. The :guilabel:`Responsible` person is listed on the contract." msgstr "" #: ../../content/applications/hr/fleet/configuration.rst:45 -msgid "New Vehicle Request" +msgid "New vehicle request" msgstr "" #: ../../content/applications/hr/fleet/configuration.rst:47 -msgid "The :guilabel:`New Vehicle Request` field sets a limit on how many new vehicles are requested based on fleet availability. An employee filling out the salary configurator form (after being offered a position), will *not* be able to request a new car if the number of existing cars is greater than the number specified in the :guilabel:`New Vehicle Request` field. Enter the specific number limit for existing available cars in this field." +msgid "The :guilabel:`New Vehicle Request` field sets a limit on how many new vehicles are requested based on fleet availability. After being offered a position, an employee filling out the online salary configurator form is **not** able to request a new car if the number of existing cars is greater than the number specified in the :guilabel:`New Vehicle Request` field. Enter the specific number limit for existing available cars in this field." msgstr "" #: ../../content/applications/hr/fleet/configuration.rst:54 @@ -1950,420 +2080,465 @@ msgid "If the :guilabel:`New Vehicle Request` limit is set to 20 vehicles, and t msgstr "" #: ../../content/applications/hr/fleet/configuration.rst:61 +#: ../../content/applications/hr/fleet/configuration.rst:102 +msgid "Models" +msgstr "" + +#: ../../content/applications/hr/fleet/configuration.rst:64 msgid "Manufacturers" msgstr "" -#: ../../content/applications/hr/fleet/configuration.rst:63 -msgid "Odoo *Fleet* comes pre-configured with sixty-six commonly used car and bicycle manufacturers in the database, along with their logos. To view the pre-loaded manufacturers, go to :menuselection:`Fleet app --> Configuration --> Manufacturers`." +#: ../../content/applications/hr/fleet/configuration.rst:66 +msgid "Odoo *Fleet* comes pre-configured with sixty-six commonly used car manufacturers in the database, along with their logos. To view the pre-loaded manufacturers, go to :menuselection:`Fleet app --> Configuration --> Models: Manufacturers`." msgstr "" -#: ../../content/applications/hr/fleet/configuration.rst:67 -msgid "The manufacturers appear in a list view in alphabetical order. Each manufacturer's card lists how many specific models are configured for each particular manufacturer. Odoo comes with forty six pre-configured :ref:`models ` from four major auto manufacturers and one major bicycle manufacturer: Audi, BMW, Mercedes, Opel (cars), and Eddy Merckx (bicycle)." +#: ../../content/applications/hr/fleet/configuration.rst:70 +msgid "The manufacturers appear in a list view in alphabetical order. Each manufacturer's card lists how many specific models are configured for each particular manufacturer. Odoo comes with forty five pre-configured :ref:`models ` from four major auto manufacturers: Audi, BMW, Mercedes, and Opel." msgstr "" #: ../../content/applications/hr/fleet/configuration.rst:-1 msgid "Manufacturer card with the amount of models listed." msgstr "" -#: ../../content/applications/hr/fleet/configuration.rst:77 +#: ../../content/applications/hr/fleet/configuration.rst:82 msgid "Add a manufacturer" msgstr "" -#: ../../content/applications/hr/fleet/configuration.rst:79 -msgid "To add a new manufacturer to the database, click :guilabel:`Create`. A manufacturer form will load. Only two pieces of information are needed, the :guilabel:`Name` of the manufacturer, and the logo. Type the name of the manufacturer in the name field, and select an image to upload for the logo. When the information is entered, click :guilabel:`Save`." +#: ../../content/applications/hr/fleet/configuration.rst:84 +msgid "To add a new manufacturer to the database, click :guilabel:`New`, and a blank manufacturer form loads." msgstr "" #: ../../content/applications/hr/fleet/configuration.rst:87 -msgid "Vehicle Models" +msgid "First, type the name of the manufacturer in the :guilabel:`Name` field. This is the only required field." msgstr "" -#: ../../content/applications/hr/fleet/configuration.rst:89 -msgid "Many manufacturers have a variety of models that they produce. When adding a vehicle to the fleet, it is important to specify the vehicle model being added. Odoo comes with pre-configured car models from four major auto manufacturers, and one pre-configured bicycle model from one bicycle manufacturer: Audi, BMW, Mercedes, Opel (cars), and Eddy Merckx (bicycle). If a vehicle *other* than the pre-configured models from these manufacturers are part of a fleet, the model (and/or manufacturer) will need to be added to the database." +#: ../../content/applications/hr/fleet/configuration.rst:90 +msgid "Next, if a photo is available, hover over the image box and click the :guilabel:`✏️ (Pencil)` icon that appears in the lower-left corner." msgstr "" -#: ../../content/applications/hr/fleet/configuration.rst:97 -msgid "Preconfigured Models" +#: ../../content/applications/hr/fleet/configuration.rst:93 +msgid "A file explorer window pops up. Navigate to the file, then click :guilabel:`Open` to select it." msgstr "" -#: ../../content/applications/hr/fleet/configuration.rst:99 -msgid "The following models are pre-loaded in Odoo and do not need to be added to the database:" +#: ../../content/applications/hr/fleet/configuration.rst:95 +msgid "The manufacturer form automatically saves as data is entered. However, the form can be saved manually at any time by clicking the :guilabel:`Save manually` option, represented by a :guilabel:`(cloud with an upwards arrow)` icon." msgstr "" -#: ../../content/applications/hr/fleet/configuration.rst:102 +#: ../../content/applications/hr/fleet/configuration.rst:104 +msgid "Many manufacturers have a variety of models that they produce. Odoo comes with pre-configured car models from four major auto manufacturers: Audi, BMW, Mercedes, and Opel." +msgstr "" + +#: ../../content/applications/hr/fleet/configuration.rst:107 +msgid "If a vehicle *other* than the pre-configured models from these manufacturers is part of a fleet, the model (and/or manufacturer) **must** be added to the database." +msgstr "" + +#: ../../content/applications/hr/fleet/configuration.rst:111 +msgid "Pre-configured models" +msgstr "" + +#: ../../content/applications/hr/fleet/configuration.rst:113 +msgid "The following models are pre-configured in Odoo and do not need to be added to the database:" +msgstr "" + +#: ../../content/applications/hr/fleet/configuration.rst:116 msgid "AUDI" msgstr "" -#: ../../content/applications/hr/fleet/configuration.rst:102 +#: ../../content/applications/hr/fleet/configuration.rst:116 msgid "BMW" msgstr "" -#: ../../content/applications/hr/fleet/configuration.rst:102 -msgid "Eddy Merckx" -msgstr "" - -#: ../../content/applications/hr/fleet/configuration.rst:102 +#: ../../content/applications/hr/fleet/configuration.rst:116 msgid "Mercedes" msgstr "" -#: ../../content/applications/hr/fleet/configuration.rst:102 +#: ../../content/applications/hr/fleet/configuration.rst:116 msgid "Opel" msgstr "" -#: ../../content/applications/hr/fleet/configuration.rst:104 +#: ../../content/applications/hr/fleet/configuration.rst:118 msgid "A1" msgstr "" -#: ../../content/applications/hr/fleet/configuration.rst:104 +#: ../../content/applications/hr/fleet/configuration.rst:118 msgid "Serie 1" msgstr "" -#: ../../content/applications/hr/fleet/configuration.rst:104 -msgid "SanRemo76" -msgstr "" - -#: ../../content/applications/hr/fleet/configuration.rst:104 +#: ../../content/applications/hr/fleet/configuration.rst:118 msgid "Class A" msgstr "" -#: ../../content/applications/hr/fleet/configuration.rst:104 +#: ../../content/applications/hr/fleet/configuration.rst:118 msgid "Agilia" msgstr "" -#: ../../content/applications/hr/fleet/configuration.rst:106 +#: ../../content/applications/hr/fleet/configuration.rst:120 msgid "A3" msgstr "" -#: ../../content/applications/hr/fleet/configuration.rst:106 +#: ../../content/applications/hr/fleet/configuration.rst:120 msgid "Serie 3" msgstr "" -#: ../../content/applications/hr/fleet/configuration.rst:106 +#: ../../content/applications/hr/fleet/configuration.rst:120 msgid "Class B" msgstr "" -#: ../../content/applications/hr/fleet/configuration.rst:106 +#: ../../content/applications/hr/fleet/configuration.rst:120 msgid "Ampera" msgstr "" -#: ../../content/applications/hr/fleet/configuration.rst:108 +#: ../../content/applications/hr/fleet/configuration.rst:122 msgid "A4" msgstr "" -#: ../../content/applications/hr/fleet/configuration.rst:108 +#: ../../content/applications/hr/fleet/configuration.rst:122 msgid "Serie 5" msgstr "" -#: ../../content/applications/hr/fleet/configuration.rst:108 +#: ../../content/applications/hr/fleet/configuration.rst:122 msgid "Class C" msgstr "" -#: ../../content/applications/hr/fleet/configuration.rst:108 +#: ../../content/applications/hr/fleet/configuration.rst:122 msgid "Antara" msgstr "" -#: ../../content/applications/hr/fleet/configuration.rst:110 +#: ../../content/applications/hr/fleet/configuration.rst:124 msgid "A5" msgstr "" -#: ../../content/applications/hr/fleet/configuration.rst:110 +#: ../../content/applications/hr/fleet/configuration.rst:124 msgid "Serie 6" msgstr "" -#: ../../content/applications/hr/fleet/configuration.rst:110 +#: ../../content/applications/hr/fleet/configuration.rst:124 msgid "Class CL" msgstr "" -#: ../../content/applications/hr/fleet/configuration.rst:110 +#: ../../content/applications/hr/fleet/configuration.rst:124 msgid "Astra" msgstr "" -#: ../../content/applications/hr/fleet/configuration.rst:112 +#: ../../content/applications/hr/fleet/configuration.rst:126 msgid "A6" msgstr "" -#: ../../content/applications/hr/fleet/configuration.rst:112 +#: ../../content/applications/hr/fleet/configuration.rst:126 msgid "Serie 7" msgstr "" -#: ../../content/applications/hr/fleet/configuration.rst:112 +#: ../../content/applications/hr/fleet/configuration.rst:126 msgid "Class CLS" msgstr "" -#: ../../content/applications/hr/fleet/configuration.rst:112 +#: ../../content/applications/hr/fleet/configuration.rst:126 msgid "AstraGTC" msgstr "" -#: ../../content/applications/hr/fleet/configuration.rst:114 +#: ../../content/applications/hr/fleet/configuration.rst:128 msgid "A7" msgstr "" -#: ../../content/applications/hr/fleet/configuration.rst:114 +#: ../../content/applications/hr/fleet/configuration.rst:128 msgid "Serie Hybrid" msgstr "" -#: ../../content/applications/hr/fleet/configuration.rst:114 +#: ../../content/applications/hr/fleet/configuration.rst:128 msgid "Class E" msgstr "" -#: ../../content/applications/hr/fleet/configuration.rst:114 +#: ../../content/applications/hr/fleet/configuration.rst:128 msgid "Combo Tour" msgstr "" -#: ../../content/applications/hr/fleet/configuration.rst:116 +#: ../../content/applications/hr/fleet/configuration.rst:130 msgid "A8" msgstr "" -#: ../../content/applications/hr/fleet/configuration.rst:116 +#: ../../content/applications/hr/fleet/configuration.rst:130 msgid "Serie M" msgstr "" -#: ../../content/applications/hr/fleet/configuration.rst:116 +#: ../../content/applications/hr/fleet/configuration.rst:130 msgid "Class GL" msgstr "" -#: ../../content/applications/hr/fleet/configuration.rst:116 +#: ../../content/applications/hr/fleet/configuration.rst:130 msgid "Corsa" msgstr "" -#: ../../content/applications/hr/fleet/configuration.rst:118 +#: ../../content/applications/hr/fleet/configuration.rst:132 msgid "Q3" msgstr "" -#: ../../content/applications/hr/fleet/configuration.rst:118 +#: ../../content/applications/hr/fleet/configuration.rst:132 msgid "Serie X" msgstr "" -#: ../../content/applications/hr/fleet/configuration.rst:118 +#: ../../content/applications/hr/fleet/configuration.rst:132 msgid "Class GLK" msgstr "" -#: ../../content/applications/hr/fleet/configuration.rst:118 +#: ../../content/applications/hr/fleet/configuration.rst:132 msgid "Insignia" msgstr "" -#: ../../content/applications/hr/fleet/configuration.rst:120 +#: ../../content/applications/hr/fleet/configuration.rst:134 msgid "Q5" msgstr "" -#: ../../content/applications/hr/fleet/configuration.rst:120 +#: ../../content/applications/hr/fleet/configuration.rst:134 msgid "Serie Z4" msgstr "" -#: ../../content/applications/hr/fleet/configuration.rst:120 +#: ../../content/applications/hr/fleet/configuration.rst:134 msgid "Class M" msgstr "" -#: ../../content/applications/hr/fleet/configuration.rst:120 +#: ../../content/applications/hr/fleet/configuration.rst:134 msgid "Meriva" msgstr "" -#: ../../content/applications/hr/fleet/configuration.rst:122 +#: ../../content/applications/hr/fleet/configuration.rst:136 msgid "Q7" msgstr "" -#: ../../content/applications/hr/fleet/configuration.rst:122 +#: ../../content/applications/hr/fleet/configuration.rst:136 msgid "Class R" msgstr "" -#: ../../content/applications/hr/fleet/configuration.rst:122 +#: ../../content/applications/hr/fleet/configuration.rst:136 msgid "Mokka" msgstr "" -#: ../../content/applications/hr/fleet/configuration.rst:124 +#: ../../content/applications/hr/fleet/configuration.rst:138 msgid "TT" msgstr "" -#: ../../content/applications/hr/fleet/configuration.rst:124 +#: ../../content/applications/hr/fleet/configuration.rst:138 msgid "Class S" msgstr "" -#: ../../content/applications/hr/fleet/configuration.rst:124 +#: ../../content/applications/hr/fleet/configuration.rst:138 msgid "Zafira" msgstr "" -#: ../../content/applications/hr/fleet/configuration.rst:126 +#: ../../content/applications/hr/fleet/configuration.rst:140 msgid "Class SLK" msgstr "" -#: ../../content/applications/hr/fleet/configuration.rst:126 +#: ../../content/applications/hr/fleet/configuration.rst:140 msgid "Zafira Tourer" msgstr "" -#: ../../content/applications/hr/fleet/configuration.rst:128 +#: ../../content/applications/hr/fleet/configuration.rst:142 msgid "Class SLS" msgstr "" -#: ../../content/applications/hr/fleet/configuration.rst:134 +#: ../../content/applications/hr/fleet/configuration.rst:148 msgid "Add a new model" msgstr "" -#: ../../content/applications/hr/fleet/configuration.rst:136 -msgid "New vehicle models can easily be added to the database. To add a new model, navigate to :menuselection:`Fleet app --> Configuration --> Vehicle Models`. Click :guilabel:`Create` and a vehicle model form will load. Enter the following information on the form, then click :guilabel:`Save`. Be advised, some fields are specific to Belgian based companies, so not all fields or sections may be visible depending on the location of the company." +#: ../../content/applications/hr/fleet/configuration.rst:150 +msgid "New vehicle models can easily be added to the database. To add a new model, navigate to :menuselection:`Fleet app --> Configuration --> Models: Models`. Click the :guilabel:`New` button in the top-left corner and a blank vehicle model form loads." msgstr "" -#: ../../content/applications/hr/fleet/configuration.rst:142 +#: ../../content/applications/hr/fleet/configuration.rst:154 +#: ../../content/applications/hr/frontdesk.rst:31 +#: ../../content/applications/hr/payroll.rst:881 +#: ../../content/applications/hr/payroll/work_entries.rst:54 +#: ../../content/applications/hr/time_off.rst:416 +msgid "Enter the following information on the form:" +msgstr "" + +#: ../../content/applications/hr/fleet/configuration.rst:157 +msgid "Some fields or sections are based on the localization setting of the company, therefore not all fields or sections may be visible." +msgstr "" + +#: ../../content/applications/hr/fleet/configuration.rst:160 msgid ":guilabel:`Model name`: enter the model name in the field." msgstr "" -#: ../../content/applications/hr/fleet/configuration.rst:143 -msgid ":guilabel:`Manufacturer`: select the manufacturer from the drop-down menu. If the manufacturer is not configured, type in the manufacturer and then click :guilabel:`Create` or :guilabel:`Create & Edit`." -msgstr "" - -#: ../../content/applications/hr/fleet/configuration.rst:146 -msgid ":guilabel:`Vehicle Type`: select one of two preconfigured vehicle types, either :guilabel:`Car` or :guilabel:`Bike`, from the drop-down menu. The vehicle types are hardcoded in Odoo and are integrated with the *Payroll* application since vehicles can be part of an employee's benefits. Adding additional vehicle types is not possible as it will affect payroll." -msgstr "" - -#: ../../content/applications/hr/fleet/configuration.rst:150 -msgid ":guilabel:`Category`: select the category the vehicle is categorized under from the drop-down menu. To create a new category, type in the category and then click :guilabel:`Create (new category)`." -msgstr "" - -#: ../../content/applications/hr/fleet/configuration.rst:155 -msgid "When the manufacturer is selected, the logo for the manufacturer will automatically load in the image box in the top right corner." -msgstr "" - -#: ../../content/applications/hr/fleet/configuration.rst:159 -msgid "Information tab" -msgstr "" - -#: ../../content/applications/hr/fleet/configuration.rst:162 -msgid "Model" -msgstr "" - -#: ../../content/applications/hr/fleet/configuration.rst:164 -msgid ":guilabel:`Seats Number`: enter how many passengers the vehicle can accommodate." -msgstr "" - -#: ../../content/applications/hr/fleet/configuration.rst:165 -msgid ":guilabel:`Doors Number`: enter the number of doors the vehicle has." -msgstr "" - -#: ../../content/applications/hr/fleet/configuration.rst:166 -msgid ":guilabel:`Color`: enter the color of the vehicle." +#: ../../content/applications/hr/fleet/configuration.rst:161 +msgid ":guilabel:`Manufacturer`: select the manufacturer from the drop-down menu. If a logo is configured for the selected manufacturer, the logo automatically loads in the image box in the top-right corner. If the manufacturer is not already configured, type in the manufacturer name and then click :guilabel:`Create` to add the manufacturer, or :guilabel:`Create and edit...` to :ref:`add the manufacturer and the logo ` in a :guilabel:`Create Manufacturer` pop-up window." msgstr "" #: ../../content/applications/hr/fleet/configuration.rst:167 -msgid ":guilabel:`Model Year`: enter the year the vehicle was manufactured." -msgstr "" - -#: ../../content/applications/hr/fleet/configuration.rst:168 -msgid ":guilabel:`Trailer Hitch`: check this box if the vehicle has a trailer hitch installed." +msgid ":guilabel:`Vehicle Type`: select one of two pre-configured vehicle types, either :guilabel:`Car` or :guilabel:`Bike`, from the drop-down menu. The vehicle types are hardcoded in Odoo and are integrated with the *Payroll* application since vehicles can be part of an employee's benefits. Adding additional vehicle types is not possible as it affects payroll." msgstr "" #: ../../content/applications/hr/fleet/configuration.rst:171 +msgid ":guilabel:`Category`: select the category the vehicle is categorized under from the drop-down menu. To create a new category, type in the category name and then click :guilabel:`Create \"new category\"`." +msgstr "" + +#: ../../content/applications/hr/fleet/configuration.rst:176 +msgid "Information tab" +msgstr "" + +#: ../../content/applications/hr/fleet/configuration.rst:179 +msgid "Model" +msgstr "" + +#: ../../content/applications/hr/fleet/configuration.rst:181 +msgid ":guilabel:`Seats Number`: enter how many passengers the vehicle can accommodate." +msgstr "" + +#: ../../content/applications/hr/fleet/configuration.rst:182 +msgid ":guilabel:`Doors Number`: enter the number of doors the vehicle has." +msgstr "" + +#: ../../content/applications/hr/fleet/configuration.rst:183 +msgid ":guilabel:`Color`: enter the color of the vehicle." +msgstr "" + +#: ../../content/applications/hr/fleet/configuration.rst:184 +msgid ":guilabel:`Model Year`: enter the year the vehicle was manufactured." +msgstr "" + +#: ../../content/applications/hr/fleet/configuration.rst:185 +msgid ":guilabel:`Trailer Hitch`: check this box if the vehicle has a trailer hitch installed." +msgstr "" + +#: ../../content/applications/hr/fleet/configuration.rst:188 #: ../../content/applications/hr/payroll.rst:390 msgid "Salary" msgstr "" -#: ../../content/applications/hr/fleet/configuration.rst:174 +#: ../../content/applications/hr/fleet/configuration.rst:191 msgid "The :guilabel:`Salary` section only appears for Belgian-based companies, and only if the company has their localization setting set to Belgium. The cost values are all **monthly** with the exception of the :guilabel:`Catalog Value (VAT Incl.)`." msgstr "" -#: ../../content/applications/hr/fleet/configuration.rst:178 -msgid ":guilabel:`Can be requested`: check this box if employees can request this model vehicle." +#: ../../content/applications/hr/fleet/configuration.rst:195 +msgid ":guilabel:`Can be requested`: check this box if employees can request this model for a new vehicle." msgstr "" -#: ../../content/applications/hr/fleet/configuration.rst:179 +#: ../../content/applications/hr/fleet/configuration.rst:197 msgid ":guilabel:`Catalog Value (VAT Incl.)`: enter the :abbr:`MSRP (Manufacturer's Suggested Retail Price)` for the vehicle at the time of purchase or lease." msgstr "" -#: ../../content/applications/hr/fleet/configuration.rst:181 +#: ../../content/applications/hr/fleet/configuration.rst:199 msgid ":guilabel:`C02 fee`: this value is automatically calculated based on Belgian laws and regulations, and cannot be modified. The value is based on the value entered in the :guilabel:`CO2 Emissions` field in the :guilabel:`Engine` section of the vehicle form." msgstr "" -#: ../../content/applications/hr/fleet/configuration.rst:186 -msgid "Modifying the :guilabel:`CO2 Emissions` field will adjust the value in the :guilabel:`CO2 fee` field." -msgstr "" - -#: ../../content/applications/hr/fleet/configuration.rst:189 -msgid ":guilabel:`Cost (Depreciated)`: enter the monthly cost for the vehicle, which appears in the salary configurator that is available to a future employee when they are offered a job position. This value impacts the gross and net salary of the employee who is assigned to the vehicle. This figure is depreciated over time according to local tax laws. The :guilabel:`Cost (Depreciated)` does not depreciate automatically on the *vehicle model*, it only depreciates based on the *contract* linked to a specific vehicle and not on the general model." -msgstr "" - -#: ../../content/applications/hr/fleet/configuration.rst:195 -msgid ":guilabel:`Total Cost (Depreciated)`: this value is the :guilabel:`Cost (Depreciated)` and the :guilabel:`C02 fee` fields combined, and also is depreciated over time." -msgstr "" - -#: ../../content/applications/hr/fleet/configuration.rst:199 -msgid "Engine" -msgstr "" - -#: ../../content/applications/hr/fleet/configuration.rst:201 -msgid ":guilabel:`Fuel Type`: select the type of fuel the vehicle uses form the drop-down menu. The options are :guilabel:`Diesel`, :guilabel:`Gasoline`, :guilabel:`Hybrid Diesel`, :guilabel:`Hybrid Gasoline`, :guilabel:`Plug-in Hybrid Diesel`, :guilabel:`Plug-in Hybrid Gasoline`, :guilabel:`CNG`, :guilabel:`LPG`, :guilabel:`Hydrogen`, or :guilabel:`Electric`." -msgstr "" - -#: ../../content/applications/hr/fleet/configuration.rst:205 -msgid ":guilabel:`CO2 Emissions`: enter the average carbon dioxide emissions the vehicle produces in grams per kilometer (g/km). This information is provided by the car manufacturer." +#: ../../content/applications/hr/fleet/configuration.rst:204 +msgid "Modifying the :guilabel:`CO2 Emissions` field adjusts the value in the :guilabel:`CO2 fee` field." msgstr "" #: ../../content/applications/hr/fleet/configuration.rst:207 -msgid ":guilabel:`CO2 Standard`: enter the standard amount of carbon dioxide in grams per kilometer (g/km) for a similar sized vehicle." +msgid ":guilabel:`Cost (Depreciated)`: enter the monthly cost for the vehicle, which appears in the salary configurator that is available to a future employee when they are offered a job position." msgstr "" -#: ../../content/applications/hr/fleet/configuration.rst:209 -msgid ":guilabel:`Transmission`: select the transmission type from the drop-down menu, either :guilabel:`Manual` or :guilabel:`Automatic`." -msgstr "" - -#: ../../content/applications/hr/fleet/configuration.rst:211 -msgid ":guilabel:`Power`: if the vehicle is electric or hybrid, enter the power the vehicle uses in kilowatts (kW)." +#: ../../content/applications/hr/fleet/configuration.rst:210 +msgid "This value impacts the gross and net salary of the employee who is assigned to the vehicle. This figure is depreciated over time according to local tax laws." msgstr "" #: ../../content/applications/hr/fleet/configuration.rst:213 -msgid ":guilabel:`Horsepower`: enter the vehicle's horsepower in this field." +msgid "The :guilabel:`Cost (Depreciated)` does **not** depreciate automatically on the *vehicle model*, it **only** depreciates based on the *contract* linked to a specific vehicle and not on the general model." msgstr "" -#: ../../content/applications/hr/fleet/configuration.rst:214 -msgid ":guilabel:`Horsepower Taxation`: enter the amount that is taxed based on the size of the vehicle's engine. This is determined by local taxes and regulations, and varies depending on the location. It is recommended to check with the accounting department to ensure this value is correct." -msgstr "" - -#: ../../content/applications/hr/fleet/configuration.rst:217 -msgid ":guilabel:`Tax Deduction`: this field auto-populates according to the engine specifications, and cannot be modified. The percentage is based on the localization settings and local tax laws." +#: ../../content/applications/hr/fleet/configuration.rst:216 +msgid ":guilabel:`Total Cost (Depreciated)`: this value is the :guilabel:`Cost (Depreciated)` and the :guilabel:`C02 fee` fields combined, and is also depreciated over time. This field is automatically calculated and cannot be modified." msgstr "" #: ../../content/applications/hr/fleet/configuration.rst:221 -msgid "Vendors tab" +msgid "Engine" msgstr "" #: ../../content/applications/hr/fleet/configuration.rst:223 -msgid "Vehicle specific vendors, such as car dealerships, are not listed separately from other vendors. The vendors that a vehicle can be purchased from also appear in the list of vendors used by the *Purchase* app." +msgid ":guilabel:`Fuel Type`: select the type of fuel the vehicle uses from the drop-down menu. The options are :guilabel:`Diesel`, :guilabel:`Gasoline`, :guilabel:`Full Hybrid`, :guilabel:`Plug-in Hybrid Diesel`, :guilabel:`Plug-in Hybrid Gasoline`, :guilabel:`CNG`, :guilabel:`LPG`, :guilabel:`Hydrogen`, or :guilabel:`Electric`." msgstr "" #: ../../content/applications/hr/fleet/configuration.rst:227 -msgid "The vendor(s) the vehicle can be purchased from may be added in this tab. To add a vendor, click :guilabel:`Add`, and a pop-up loads with a list of all the vendors currently in the database. Select the vendor to add by clicking the checkbox next to the vendor name, then click :guilabel:`Select`. There is no limit to the number of vendors that can be added to this list." +msgid ":guilabel:`CO2 Emissions`: enter the average carbon dioxide emissions the vehicle produces in grams per kilometer (g/km). This information is provided by the car manufacturer." msgstr "" -#: ../../content/applications/hr/fleet/configuration.rst:232 -msgid "If a vendor is not in the database, add a vendor by clicking :guilabel:`Create`. A vendor form will load. Enter the information in the vendor tab, then click :guilabel:`Save & Close` to add the vendor and close the window, or :guilabel:`Save & New` to add the current vendor and create another new vendor." +#: ../../content/applications/hr/fleet/configuration.rst:229 +msgid ":guilabel:`CO2 Standard`: enter the standard amount of carbon dioxide in grams per kilometer (g/km) for a similar sized vehicle." +msgstr "" + +#: ../../content/applications/hr/fleet/configuration.rst:231 +msgid ":guilabel:`Transmission`: select the transmission type from the drop-down menu, either :guilabel:`Manual` or :guilabel:`Automatic`." +msgstr "" + +#: ../../content/applications/hr/fleet/configuration.rst:233 +msgid ":guilabel:`Power`: if the vehicle is electric or hybrid, enter the power the vehicle uses in kilowatts (kW)." +msgstr "" + +#: ../../content/applications/hr/fleet/configuration.rst:235 +msgid ":guilabel:`Horsepower`: enter the vehicle's horsepower in this field." +msgstr "" + +#: ../../content/applications/hr/fleet/configuration.rst:236 +msgid ":guilabel:`Horsepower Taxation`: enter the amount that is taxed based on the size of the vehicle's engine. This is determined by local taxes and regulations, and varies depending on the location. It is recommended to check with the accounting department to ensure this value is correct." +msgstr "" + +#: ../../content/applications/hr/fleet/configuration.rst:239 +msgid ":guilabel:`Tax Deduction`: this field auto-populates according to the engine specifications, and cannot be modified. The percentage is based on the localization settings and local tax laws." +msgstr "" + +#: ../../content/applications/hr/fleet/configuration.rst:243 +msgid "Vendors tab" +msgstr "" + +#: ../../content/applications/hr/fleet/configuration.rst:245 +msgid "Vehicle specific vendors, such as car dealerships, are not listed separately from other vendors. The vendors that a vehicle can be purchased from also appear in the list of vendors in the *Purchase* app." +msgstr "" + +#: ../../content/applications/hr/fleet/configuration.rst:249 +msgid "The vendors the specific vehicle model can be purchased from may be added in this tab. To add a vendor, click the :guilabel:`Add` button. An :guilabel:`Add: Vendors` pop-up window loads with a list of all the vendors currently in the database." +msgstr "" + +#: ../../content/applications/hr/fleet/configuration.rst:253 +msgid "Select the vendor to add by clicking the checkbox to the left of the vendor name, then click :guilabel:`Select`. There is no limit to the number of vendors that can be added to this list." +msgstr "" + +#: ../../content/applications/hr/fleet/configuration.rst:256 +msgid "If a vendor is not in the database, add a vendor by clicking the :guilabel:`New` button at the bottom of the :guilabel:`Add: Vendors` pop-up window. A blank :guilabel:`Create Vendors` pop-up form loads." +msgstr "" + +#: ../../content/applications/hr/fleet/configuration.rst:260 +msgid "Enter the information on the :guilabel:`Create Vendors` form, including the various tabs, then click :guilabel:`Save & Close` to add the vendor and close the window, or :guilabel:`Save & New` to add the current vendor and create another new vendor." msgstr "" #: ../../content/applications/hr/fleet/configuration.rst:-1 msgid "Vendor form to fill out when adding a new vendor." msgstr "" -#: ../../content/applications/hr/fleet/configuration.rst:244 -msgid "Model Category" +#: ../../content/applications/hr/fleet/configuration.rst:271 +msgid "Categories" msgstr "" -#: ../../content/applications/hr/fleet/configuration.rst:246 -msgid "To best organize a fleet, it is recommended to have vehicle models housed under a specific category, to more easily see what kinds of vehicles are in the fleet. Model categories are set on the :ref:`vehicle model form `." +#: ../../content/applications/hr/fleet/configuration.rst:273 +msgid "To best organize a fleet, it is recommended to have vehicle models housed under a specific category, to more easily see what kinds of vehicles are in the fleet." msgstr "" -#: ../../content/applications/hr/fleet/configuration.rst:250 -msgid "To view all the models currently set up, navigate to :menuselection:`Fleet application --> Configuration --> Model Category`. All models are displayed in a list view." +#: ../../content/applications/hr/fleet/configuration.rst:276 +msgid "Model categories are set on the :ref:`vehicle model form `." msgstr "" -#: ../../content/applications/hr/fleet/configuration.rst:254 -msgid "Add a new model category" +#: ../../content/applications/hr/fleet/configuration.rst:278 +msgid "Unlike manufacturers and models, Odoo does not come with any categories pre-configured; all categories must be added." msgstr "" -#: ../../content/applications/hr/fleet/configuration.rst:256 -msgid "To add a new category, click :guilabel:`Create`. A new entry line appears at the bottom of the list. Type in the new category, then click :guilabel:`Save` to save the entry." +#: ../../content/applications/hr/fleet/configuration.rst:281 +msgid "To view all the currently configured categories, navigate to :menuselection:`Fleet application --> Configuration --> Models: Categories`. All currently configured categories are displayed in a list view." msgstr "" -#: ../../content/applications/hr/fleet/configuration.rst:259 -msgid "To reorganize how the categories appear in the list, click on the up and down arrows to the left of the category to be moved, and drag the line to the desired position. The order of the list does not affect the database in any way. However, it may be preferable to view the vehicle categories in a specific order, for example, by size, or the numbers of passengers the vehicle can carry." +#: ../../content/applications/hr/fleet/configuration.rst:286 +msgid "Add a new category" +msgstr "" + +#: ../../content/applications/hr/fleet/configuration.rst:288 +msgid "To add a new category, click the :guilabel:`New` button in the top-left corner. A new entry line appears at the bottom of the list. Type in the new category, then either press the enter key on the keyboard, or click anywhere on the screen, to save the entry." +msgstr "" + +#: ../../content/applications/hr/fleet/configuration.rst:292 +msgid "To reorganize how the categories appear in the list, click the :guilabel:`(six small gray boxes)` to the left of the category to be moved, and drag the line to the desired position. The order of the list does not affect the database in any way. However, it may be preferable to view the vehicle categories in a specific order, for example, by size, or the numbers of passengers the vehicle can carry." msgstr "" #: ../../content/applications/hr/fleet/configuration.rst:-1 -msgid "List view of the models in the fleet." +msgid "List view of the categories in the fleet." msgstr "" #: ../../content/applications/hr/fleet/new_vehicle.rst:3 @@ -2474,6 +2649,8 @@ msgstr "" msgid "Creating a new company may cause a subscription price change depending on the current plan. Refer to `Odoo's pricing plan `_ for more details." msgstr "" +#: ../../content/applications/hr/fleet/new_vehicle.rst:-1 +#: ../../content/applications/hr/fleet/new_vehicle.rst:-1 #: ../../content/applications/hr/fleet/new_vehicle.rst:-1 msgid "The new vehicle form, showing the vehicle tax section." msgstr "" @@ -2761,13 +2938,6 @@ msgstr "" msgid "To create a station, navigate to :menuselection:`Frontdesk app --> Configuration --> Stations`, and click :guilabel:`New`. When clicked, a blank frontdesk form appears." msgstr "" -#: ../../content/applications/hr/frontdesk.rst:31 -#: ../../content/applications/hr/payroll.rst:881 -#: ../../content/applications/hr/payroll/work_entries.rst:54 -#: ../../content/applications/hr/time_off.rst:414 -msgid "Enter the following information on the form:" -msgstr "" - #: ../../content/applications/hr/frontdesk.rst:33 msgid ":guilabel:`Frontdesk Name`: enter a name for the specific frontdesk location. This should be short and easily identifiable, such as `Reception Desk` or `Main Lobby`. This field is required in order to create a station." msgstr "" @@ -2803,7 +2973,7 @@ msgid "The image selected for the station photo appears as the background image msgstr "" #: ../../content/applications/hr/frontdesk.rst:59 -#: ../../content/applications/hr/recruitment.rst:609 +#: ../../content/applications/hr/recruitment.rst:608 msgid "Options tab" msgstr "" @@ -3179,7 +3349,7 @@ msgstr "" #: ../../content/applications/hr/payroll.rst:5 #: ../../content/applications/hr/payroll.rst:81 -#: ../../content/applications/hr/payroll/reporting.rst:39 +#: ../../content/applications/hr/payroll/reporting.rst:31 msgid "Payroll" msgstr "" @@ -3244,7 +3414,7 @@ msgid "Each individual company can have a different localization setting configu msgstr "" #: ../../content/applications/hr/payroll.rst:59 -msgid "For more information on companies, refer to the :doc:`Companies <../general/users/companies>` documentation, which covers how to set up companies." +msgid "For more information on companies, refer to the :doc:`Companies <../general/companies>` documentation, which covers how to set up companies." msgstr "" #: ../../content/applications/hr/payroll.rst:63 @@ -3819,7 +3989,7 @@ msgid "Salary structure details for Regular Pay, listing all the specific Salary msgstr "" #: ../../content/applications/hr/payroll.rst:545 -#: ../../content/applications/hr/time_off.rst:191 +#: ../../content/applications/hr/time_off.rst:193 msgid "Rules" msgstr "" @@ -4327,27 +4497,27 @@ msgid "Refer to the :doc:`../hr/recruitment/new_job` documentation for more deta msgstr "" #: ../../content/applications/hr/payroll.rst:949 -msgid ":doc:`payroll/reporting`" -msgstr "" - -#: ../../content/applications/hr/payroll.rst:950 msgid ":doc:`payroll/contracts`" msgstr "" -#: ../../content/applications/hr/payroll.rst:951 +#: ../../content/applications/hr/payroll.rst:950 msgid ":doc:`payroll/payslips`" msgstr "" -#: ../../content/applications/hr/payroll.rst:952 +#: ../../content/applications/hr/payroll.rst:951 msgid ":doc:`payroll/work_entries`" msgstr "" +#: ../../content/applications/hr/payroll.rst:952 +msgid ":doc:`payroll/reporting`" +msgstr "" + #: ../../content/applications/hr/payroll/contracts.rst:5 msgid "Every employee in Odoo is required to have a contract in order to be paid. A contract outlines the terms of an employee's position, their compensation, their working hours, and any other details about their position." msgstr "" #: ../../content/applications/hr/payroll/contracts.rst:10 -msgid "Contract documents (PDFs) are uploaded and organized using the *Documents* application, and are signed using the *Sign* application. Ensure these applications are installed in order to send and sign contracts. Please refer to the :doc:`/applications/finance/documents` and :doc:`/applications/finance/sign` documentation." +msgid "Contract documents (PDFs) are uploaded and organized using the *Documents* application, and are signed using the *Sign* application. Ensure these applications are installed in order to send and sign contracts. Please refer to the :doc:`/applications/productivity/documents` and :doc:`/applications/productivity/sign` documentation." msgstr "" #: ../../content/applications/hr/payroll/contracts.rst:15 @@ -4446,6 +4616,7 @@ msgstr "" msgid "The contract details section allows for the addition and editing of a contract, and the ability to send the contract to the employee for approval and signatures." msgstr "" +#: ../../content/applications/hr/payroll/contracts.rst:-1 #: ../../content/applications/hr/payroll/contracts.rst:-1 msgid "Contract details in optional tabs for a new contract." msgstr "" @@ -4631,7 +4802,7 @@ msgid "Payslips" msgstr "" #: ../../content/applications/hr/payroll/payslips.rst:5 -msgid "Payslips are created either by the employees themselves or their managers, and are approved by authorized employees (typically managers). Then, once payslips are approved, employees are issued payslips and are paid either by check or direct deposit, depending on how their employee profile is configured." +msgid "*Payslips* are created either by the employees themselves or their managers, and are approved by authorized employees (typically managers). Then, once payslips are approved, employees are issued payslips and are paid either by check or direct deposit, depending on how their employee profile is configured." msgstr "" #: ../../content/applications/hr/payroll/payslips.rst:10 @@ -4646,11 +4817,11 @@ msgstr "" msgid "Payslips menu selection in Payroll." msgstr "" -#: ../../content/applications/hr/payroll/payslips.rst:21 +#: ../../content/applications/hr/payroll/payslips.rst:23 msgid "To pay" msgstr "" -#: ../../content/applications/hr/payroll/payslips.rst:23 +#: ../../content/applications/hr/payroll/payslips.rst:25 msgid "Click on :menuselection:`Payroll app --> Payslips --> To Pay` to see the payslips that need to be paid. On this page, Odoo displays the payslips that have not been generated yet, and can be created from this dashboard." msgstr "" @@ -4658,555 +4829,862 @@ msgstr "" msgid "View all payslips that need to be paid on the Payslips To Pay page." msgstr "" -#: ../../content/applications/hr/payroll/payslips.rst:31 -msgid "Each payslip will list the :guilabel:`Reference` number for the individual payslip, the :guilabel:`Employee` name, :guilabel:`Batch Name`, the :guilabel:`From` and :guilabel:`To` date range, the :guilabel:`Company`, the :guilabel:`Basic Wage`, :guilabel:`Net Wage`, and the :guilabel:`Status` of the payslip." +#: ../../content/applications/hr/payroll/payslips.rst:33 +msgid "Each payslip lists the :guilabel:`Reference` number for the individual payslip, the :guilabel:`Employee` name, the :guilabel:`Batch Name`, the :guilabel:`Company`, the :guilabel:`Basic Wage`, :guilabel:`Gross Wage`, :guilabel:`Net Wage`, and the :guilabel:`Status` of the payslip." msgstr "" -#: ../../content/applications/hr/payroll/payslips.rst:36 -msgid "Clicking on an individual payslip entry will show the details for the individual payslip." +#: ../../content/applications/hr/payroll/payslips.rst:37 +msgid "Click on an individual payslip entry to view the details for that individual payslip." msgstr "" -#: ../../content/applications/hr/payroll/payslips.rst:41 -msgid "Create new payslip" +#: ../../content/applications/hr/payroll/payslips.rst:42 +msgid "Create a new payslip" msgstr "" -#: ../../content/applications/hr/payroll/payslips.rst:43 -msgid "A new payslip can be created from the :guilabel:`Payslips To Pay` page (:menuselection:`Payroll app --> Payslips --> To Pay`) or the :guilabel:`Employee Payslips` page (:menuselection:`Payroll app --> Payslips --> All Payslips`), by clicking the :guilabel:`Create` button in the top-left corner." +#: ../../content/applications/hr/payroll/payslips.rst:44 +msgid "A new payslip can be created from either the :ref:`Payslips To Pay ` page or the :ref:`Employee Payslips ` page." msgstr "" #: ../../content/applications/hr/payroll/payslips.rst:47 -msgid "Clicking :guilabel:`Create` reveals a blank payslip form, wherein the necessary payslip information can be entered." +msgid "Create a new payslip by clicking the :guilabel:`New` button in the top-left corner." msgstr "" -#: ../../content/applications/hr/payroll/payslips.rst:53 -msgid "On the blank payslip form, a number of fields are required to be filled in with the necessary information. These required fields are represented by **bold** lines." +#: ../../content/applications/hr/payroll/payslips.rst:49 +msgid "A blank payslip form is loaded, where the necessary payslip information can be entered." msgstr "" -#: ../../content/applications/hr/payroll/payslips.rst:-1 -msgid "The necessary fields for a new payslip." +#: ../../content/applications/hr/payroll/payslips.rst:52 +msgid "Payslip form" msgstr "" -#: ../../content/applications/hr/payroll/payslips.rst:60 -msgid ":guilabel:`Employee`: Type in the name of an employee, or select the desired employee from the drop-down list. Upon selecting an employee, several other fields on the payslip form may auto-populate. Typically, after making a selection in the :guilabel:`Employee` field, Odoo auto-populates the :guilabel:`Contract`, :guilabel:`Structure`, and :guilabel:`Payslip Name` fields, but **only** if that information is already on that employee's form in the *Employees* app." +#: ../../content/applications/hr/payroll/payslips.rst:54 +msgid "On the blank payslip form, several fields are required. Most of the required fields auto-populate after an employee is selected." msgstr "" -#: ../../content/applications/hr/payroll/payslips.rst:66 -msgid ":guilabel:`Period`: Click the default date to reveal a pop-up calendar. On this calendar, use the :guilabel:`< (less-than)` and :guilabel:`> (greater than)` icons to select the desired month, and click on the desired day to select that specific date as the start date for the payslip. Repeat this process to add an end date for the payslip in the field below." +#: ../../content/applications/hr/payroll/payslips.rst:57 +msgid "Fill out the following information on the payslip form:" msgstr "" -#: ../../content/applications/hr/payroll/payslips.rst:70 -msgid ":guilabel:`Contract`: Using the drop-down menu, select the desired contract for the employee. Only the available corresponding contracts for the selected employee appear as options." +#: ../../content/applications/hr/payroll/payslips.rst:59 +msgid ":guilabel:`Employee`: type in the name of an employee, or select the desired employee from the drop-down list in this field. This field is **required**." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:63 +msgid "It is recommended to **only** create payslips for employees that are already in the database. If there is no current employee record (and therefore no employee contract) it is recommended to create the new employee in the *Employees* application **before** creating payslips for that employee. Refer to the :doc:`new employee <../employees/new_employee>` documentation for instructions on how to add an employee." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:69 +msgid ":guilabel:`Period`: the first day to the last day of the *current* month auto-populates the :guilabel:`Period` fields by default. The dates can be changed, if desired." msgstr "" #: ../../content/applications/hr/payroll/payslips.rst:72 -msgid ":guilabel:`Structure`: Using the drop-down menu, select the salary structure type. Only the available corresponding structures for the selected contract for that specific employee appear as options." -msgstr "" - -#: ../../content/applications/hr/payroll/payslips.rst:75 -msgid ":guilabel:`Payslip Name`: In the blank field, type in the name for the payslip. The name should be short and descriptive, such as `April 2023`." +msgid "To change the start date, click on the first date in the :guilabel:`Period` field to reveal a pop-up calendar. On this calendar, use the :guilabel:`< (less-than)` and :guilabel:`> (greater-than)` icons to select the desired month. Then, click on the desired day to select that specific date." msgstr "" #: ../../content/applications/hr/payroll/payslips.rst:77 -msgid ":guilabel:`Company`: In the :guilabel:`Accounting Information` tab, select the company the payslip applies to from the :guilabel:`Company` drop-down menu." +msgid "Repeat this process to modify the end date for the payslip. These fields are **required**." msgstr "" -#: ../../content/applications/hr/payroll/payslips.rst:79 -msgid ":guilabel:`Salary Journal`: In the :guilabel:`Accounting Information` tab, enter the salary journal in which the payment will be reflected, and found in the *Accounting* application." +#: ../../content/applications/hr/payroll/payslips.rst:78 +msgid ":guilabel:`Contract`: using the drop-down menu, select the desired contract for the employee. Only the available corresponding contracts for the selected employee appear as options. This field is **required**." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:81 +msgid ":guilabel:`Batch`: using the drop-down menu in this field, select the batch of payslips this new payslip should be added to." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:83 +msgid ":guilabel:`Structure`: using the drop-down menu, select the salary structure type. Only the corresponding structures associated with the selected contract for the employee appear as options." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:86 +msgid "If no employee and/or no contract is selected yet, all available :guilabel:`Structures` appear in the list. Once an employee and/or contract is selected, any unavailable :guilabel:`Structures` set for that employee and/or contract do not appear. This field is **required**." msgstr "" #: ../../content/applications/hr/payroll/payslips.rst:-1 -msgid "The necessary fields for a new payslip in the Accounting Information tab." -msgstr "" - -#: ../../content/applications/hr/payroll/payslips.rst:87 -msgid "It is recommended to check with the accounting department to ensure every entry that affects the *Accounting* application is correct." -msgstr "" - -#: ../../content/applications/hr/payroll/payslips.rst:93 -msgid ":guilabel:`Reference`: Any note or reference message for the new entry can be entered here." -msgstr "" - -#: ../../content/applications/hr/payroll/payslips.rst:94 -msgid ":guilabel:`Company Car`: If applicable, select the company car from the drop-down." +msgid "The top fields for a new payslip all filled out for a February payslip." msgstr "" #: ../../content/applications/hr/payroll/payslips.rst:95 -msgid ":guilabel:`Worked Days`: In the :guilabel:`Worked Days \\& Inputs` tab, the entries under :guilabel:`Worked Days` (including the :guilabel:`Type`, :guilabel:`Description`, :guilabel:`Number of Days`, :guilabel:`Number of Hours`, and :guilabel:`Amount`) are automatically filled in, based on what was entered for the :guilabel:`Period`, :guilabel:`Contract`, and :guilabel:`Structure` fields of the payslip form." +msgid "Typically, after making a selection in the :guilabel:`Employee` field, Odoo auto-populates all other required fields (besides the :guilabel:`Period` field), but **only** if that information is already on that employee's form in the *Employees* app." msgstr "" #: ../../content/applications/hr/payroll/payslips.rst:100 -msgid ":guilabel:`Salary Computation`: The :guilabel:`Salary Computation` tab is automatically filled in after the :guilabel:`Compute Sheet` button is clicked. Doing so displays all the wages, deductions, taxes, etc. for the entry." +msgid "If modifications to auto-populated fields are made, it is recommended to check with the accounting department to ensure every entry that affects the *Accounting* application is correct." msgstr "" -#: ../../content/applications/hr/payroll/payslips.rst:103 -msgid ":guilabel:`Batch Name`: Located in the :guilabel:`Accounting Information` tab, select the payslip batch this new payslip should be added to from the drop-down menu." +#: ../../content/applications/hr/payroll/payslips.rst:104 +msgid "Worked days & inputs tab" msgstr "" -#: ../../content/applications/hr/payroll/payslips.rst:105 -msgid ":guilabel:`Date Account`: Located in the :guilabel:`Accounting Information` tab, enter the date on which the payslip should be posted, by clicking on the drop-down menu, and navigating to the correct month and year using the :guilabel:`< > (less-than/greater-than)` icons in the calendar pop-up window. Then, click on the desired date." +#: ../../content/applications/hr/payroll/payslips.rst:106 +msgid ":guilabel:`Worked Days`: the entries under :guilabel:`Worked Days` (including the :guilabel:`Type`, :guilabel:`Description`, :guilabel:`Number of Days`, :guilabel:`Number of Hours`, and :guilabel:`Amount`) are automatically filled in, based on what was entered for the :guilabel:`Period`, :guilabel:`Contract`, and :guilabel:`Structure` fields of the payslip form." msgstr "" -#: ../../content/applications/hr/payroll/payslips.rst:109 -msgid ":guilabel:`Salary Journal`: This field, located in the :guilabel:`Accounting Information` tab, represents the journal that the payslip will be logged in, and is automatically selected when the :guilabel:`Contract` and :guilabel:`Structure` are entered in the payslip form." +#: ../../content/applications/hr/payroll/payslips.rst:110 +msgid ":guilabel:`Other Inputs`: additional inputs affecting the payslip can be entered in this section, such as deductions, reimbursements, and expenses." msgstr "" -#: ../../content/applications/hr/payroll/payslips.rst:112 -msgid ":guilabel:`Accounting Entry`: This field, located in the :guilabel:`Accounting Information` tab, is automatically filled in once the payslip is confirmed." +#: ../../content/applications/hr/payroll/payslips.rst:113 +msgid "Click :guilabel:`Add a line` to create an entry in the :guilabel:`Other Inputs` section." msgstr "" -#: ../../content/applications/hr/payroll/payslips.rst:116 -msgid "Save and process new payslip" +#: ../../content/applications/hr/payroll/payslips.rst:115 +msgid "Using the drop-down menu in the :guilabel:`Type` column, select a :guilabel:`Type` for the input. Next, enter a :guilabel:`Description`, if desired. Lastly, enter the amount in the :guilabel:`Count` field." msgstr "" -#: ../../content/applications/hr/payroll/payslips.rst:118 -msgid "When all the necessary information on the payslip is entered, click :guilabel:`Save` to save the data, or click :guilabel:`Discard` to delete the entry." +#: ../../content/applications/hr/payroll/payslips.rst:-1 +msgid "The fields filled out in the worked days and inputs tab." msgstr "" -#: ../../content/applications/hr/payroll/payslips.rst:122 -msgid "Saving the entry is not required in order to compute the sheet, although it is considered best practice to do so. The :guilabel:`Compute Sheet` button can be clicked without first saving the payslip. Doing so will save the entry *and* compute the sheet." +#: ../../content/applications/hr/payroll/payslips.rst:124 +msgid "Salary computation tab" msgstr "" #: ../../content/applications/hr/payroll/payslips.rst:126 -msgid "Click the :guilabel:`Compute Sheet` button to register all the information, and have the :guilabel:`Salary Computation` tab populated. If any modifications need to be made, click the :guilabel:`Edit` button, make the desired changes, then click the :guilabel:`Recompute Worked Days` button to have the changes reflected in the :guilabel:`Worked Days` and :guilabel:`Salary Computation` tabs." +msgid ":guilabel:`Salary Computation`: the :guilabel:`Salary Computation` tab is automatically filled in after the :guilabel:`Compute Sheet` button is clicked. Doing so displays the wages, deductions, taxes, etc. for the entry." msgstr "" -#: ../../content/applications/hr/payroll/payslips.rst:132 -msgid "To print the payslip, click the :guilabel:`Print` button. To cancel the payslip, click the :guilabel:`Cancel Payslip` button." +#: ../../content/applications/hr/payroll/payslips.rst:129 +msgid ":guilabel:`Has Negative Net To Report`: click the checkbox if the employee has a negative net amount for this payslip. This **only** appears if the employee's payslip has a negative balance." msgstr "" -#: ../../content/applications/hr/payroll/payslips.rst:135 -msgid "Once everything on the payslip form is correct, click the :guilabel:`Create Draft Entry` button to create the payslip. The chatter is automatically updated to show the email sent to the employee, along with a PDF copy of the payslip." +#: ../../content/applications/hr/payroll/payslips.rst:-1 +msgid "The fields filled out in the salary computation tab." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:137 +msgid "Other info tab" +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:139 +msgid ":guilabel:`Payslip Name`: type in a name for the payslip in this field. The name should be short and descriptive, such as `(Employee Name) April 2023`. This field is **required**." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:141 +msgid ":guilabel:`Company`: select the company the payslip applies to using the drop-down menu in this field. This field is **required**." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:143 +msgid ":guilabel:`Close Date`: enter the date that the payment is made to the employee in this field." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:145 +msgid "Click in the field to reveal a calendar pop-up window. Using the :guilabel:`< > (less-than/greater-than)` icons, navigate to the desired month and year." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:148 +msgid "Then, click on the desired date to select it." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:149 +msgid ":guilabel:`Date Account`: enter the date on which the payslip should be posted in this field." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:150 +msgid ":guilabel:`Salary Journal`: this field auto-populates after selecting an existing :guilabel:`Employee`. This field **cannot** be edited, as it is linked to the *Accounting* application. This field is **required**." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:153 +msgid ":guilabel:`Accounting Entry`: if applicable, this field is automatically populated once the payslip is confirmed. This field **cannot** be modified." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:155 +msgid ":guilabel:`Add an Internal Note...`: any note or reference message for the new entry can be typed in this field." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:-1 +msgid "The fields filled out in the other info tab." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:163 +msgid "Process the new payslip" +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:165 +msgid "When all the necessary information on the payslip is entered, click the :guilabel:`Compute Sheet` button. Upon doing so, all the information on the payslip is saved, and the :guilabel:`Salary Computation` tab auto-populates, based on the information on the employee's contract or attendance records." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:170 +msgid "If any modifications need to be made, first click the :guilabel:`Cancel` button, then click the :guilabel:`Set to Draft` button. Make any desired changes, then click the :guilabel:`Compute Sheet` button once again, and the changes are reflected in the :guilabel:`Worked Days` and :guilabel:`Salary Computation` tabs." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:175 +msgid "Once everything on the payslip form is correct, click the :guilabel:`Create Draft Entry` button to create the payslip." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:178 +msgid "Then, a confirmation pop-up window appears, asking :guilabel:`Are you sure you want to proceed?`. Click :guilabel:`OK` to confirm." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:181 +msgid "The chatter is automatically updated to show the email sent to the employee, along with a PDF copy of the payslip." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:185 +msgid "The database may need to be refreshed for the payslip and email to appear." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:187 +msgid "To print the payslip, click the :guilabel:`Print` button. To cancel the payslip, click the :guilabel:`Cancel` button." msgstr "" #: ../../content/applications/hr/payroll/payslips.rst:-1 msgid "The new payslip is emailed to the employee and the email appears in the chatter." msgstr "" -#: ../../content/applications/hr/payroll/payslips.rst:143 -msgid "Next, the payment must be sent to the employee. To do this, click the :guilabel:`Make Payment` button. Doing so reveals a pop-up form, in which the desired :guilabel:`Bank Journal` that the payment should be made against must be selected from a drop-down menu. Then, click the :guilabel:`Confirm` button to confirm the journal, and return to the payslip." +#: ../../content/applications/hr/payroll/payslips.rst:194 +msgid "Next, the payment must be sent to the employee. To do this, click the :guilabel:`Register Payment` button. Doing so reveals a pop-up form, in which the desired :guilabel:`Bank Journal` that the payment should be made against must be selected from a drop-down menu. Then, click the :guilabel:`Confirm` button to confirm the journal, and return to the payslip." msgstr "" -#: ../../content/applications/hr/payroll/payslips.rst:-1 -msgid "Click Make Payment to send the payment to the employee." -msgstr "" - -#: ../../content/applications/hr/payroll/payslips.rst:152 -msgid "If a payment needs to be cancelled or refunded, click the corresponding :guilabel:`Refund` or :guilabel:`Cancel Payslip` button, located at the top of the payslip form." -msgstr "" - -#: ../../content/applications/hr/payroll/payslips.rst:156 -msgid "In order for a payslip to be paid, the employee *must* have a bank account entered in their contact information. If there is no bank information, a payslip cannot be paid, and an error will appear when the :guilabel:`Make Payment` button is clicked. Banking information can be found in the :guilabel:`Private Information` tab on the employee's card. Edit the employee card, and add banking information, if it is missing." +#: ../../content/applications/hr/payroll/payslips.rst:200 +msgid "In order for a payslip to be paid, the employee *must* have a bank account entered in their contact information. If there is no bank information, a payslip cannot be paid, and an error appears when the :guilabel:`Make Payment` button is clicked. Banking information can be found in the :ref:`Private Information ` tab on the employee's card in the *Employees* app. Edit the employee card, and add banking information, if it is missing." msgstr "" #: ../../content/applications/hr/payroll/payslips.rst:0 msgid "Banking information can be entered in an employee's card." msgstr "" -#: ../../content/applications/hr/payroll/payslips.rst:167 +#: ../../content/applications/hr/payroll/payslips.rst:210 +msgid "Odoo automatically checks bank account information. If there is an error with the employee's listed bank account, an error appears in a pop-up window, stating, *The employee bank account is untrusted.* If this error appears, update the employee's bank account information on their :ref:`Employee Form `." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:215 +msgid "If a payment needs to be canceled or refunded, click the corresponding :guilabel:`Cancel` or :guilabel:`Refund` button, located at the top-left of the screen." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:219 +msgid "Before processing payslips, it is best practice to check the *Warnings* section of the *Payroll* app dashboard. Here, all possible issues concerning payroll appear." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:222 +msgid "To view the warnings, navigate to :menuselection:`Payroll app --> Dashboard`. The warnings appear in the top-left corner of the dashboard." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:0 +msgid "The dashboard view of the Payroll app, with the warnings box highlighted." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:229 +msgid "Warnings are grouped by type, such as `Employees Without Running Contracts` or `Employees Without Bank account Number`. Click on a warning to view all entries associated with that specific issue." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:232 +msgid "If the warnings are not resolved, at any point in the payslip processing process, an error may occur. Errors appear in a pop-up window, and provide details for the error, and how to resolve them." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:236 +msgid "Payslips **cannot** be completed if there are any warnings or issues associated with the payslip." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:241 msgid "All payslips" msgstr "" -#: ../../content/applications/hr/payroll/payslips.rst:169 -msgid "To view all payslips regardless of status, go to :menuselection:`Payroll app --> Payslips --> All Payslips`. Here, all payslips are organized by batch (in a default list view)." +#: ../../content/applications/hr/payroll/payslips.rst:243 +msgid "To view all payslips, regardless of status, go to :menuselection:`Payroll app --> Payslips --> All Payslips`. The :guilabel:`Employee Payslips` page loads, displaying all payslips, organized by batch, in a default nested list view." msgstr "" -#: ../../content/applications/hr/payroll/payslips.rst:172 -msgid "Click on the :guilabel:`▶ (arrow)` next to the individual batch name to view all the payslips in that particular batch, along with all the payslip details. The number of payslips in the batch is written in parenthesis after the batch name. The :guilabel:`Status` for each individual payslip appears on the far-right side, indicating if it is in :guilabel:`Draft Mode`, :guilabel:`Waiting`, or if it is :guilabel:`Done`." +#: ../../content/applications/hr/payroll/payslips.rst:247 +msgid "Click on the :guilabel:`▶ (right arrow)` next to an individual batch name to view all the payslips in that particular batch, along with all the payslip details." msgstr "" -#: ../../content/applications/hr/payroll/payslips.rst:179 -msgid ":guilabel:`Draft` indicates the payslip is created, and there is still time to make edits, since the amounts are not calculated." +#: ../../content/applications/hr/payroll/payslips.rst:250 +msgid "The number of payslips in the batch is written in parenthesis after the batch name. The :guilabel:`Status` for each individual payslip appears on the far-right side, indicating one of the following status options:" msgstr "" -#: ../../content/applications/hr/payroll/payslips.rst:181 -msgid "`Waiting` indicates the payslip has been calculated and the salary details can be found in the *Salary Computation* tab." +#: ../../content/applications/hr/payroll/payslips.rst:254 +msgid ":guilabel:`Draft`: the payslip is created, and there is still time to make edits, since the amounts are not calculated." msgstr "" -#: ../../content/applications/hr/payroll/payslips.rst:183 -msgid "`Done` indicates the payslip is calculated and ready to be paid." +#: ../../content/applications/hr/payroll/payslips.rst:256 +msgid ":guilabel:`Waiting`: the payslip has been calculated, and the salary details can be found in the *Salary Computation* tab." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:258 +msgid ":guilabel:`Done`: the payslip is calculated and ready to be paid." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:259 +msgid ":guilabel:`Paid`: the employee has been paid." msgstr "" #: ../../content/applications/hr/payroll/payslips.rst:-1 msgid "View all payslips organized by batches. Click on the arrow to expand each batch." msgstr "" -#: ../../content/applications/hr/payroll/payslips.rst:189 +#: ../../content/applications/hr/payroll/payslips.rst:265 msgid "Click on an individual payslip to view the details for that payslip on a separate page. Using the breadcrumb menu, click :guilabel:`Employee Payslips` to go back to the list view of all payslips." msgstr "" -#: ../../content/applications/hr/payroll/payslips.rst:192 -msgid "A new payslip can be created from the :guilabel:`Employee Payslips` page, by clicking the :guilabel:`Create` button in the upper-left corner. Doing so reveals a separate blank payslip form page. On that blank payslip form page, enter all the necessary information, as described in the :ref:`Create a new payslip ` section." +#: ../../content/applications/hr/payroll/payslips.rst:268 +msgid "A new payslip can be created from the :guilabel:`Employee Payslips` page, by clicking the :guilabel:`New` button in the upper-left corner. Doing so reveals a separate blank payslip form page. On that blank payslip form page, enter all the necessary information, as described in the :ref:`Create new payslips ` section." msgstr "" -#: ../../content/applications/hr/payroll/payslips.rst:197 -msgid "To print PDF versions of payslips from the :guilabel:`Payslips to Pay` or :guilabel:`Employee Payslips` pages, first select the desired payslips by clicking on the individual checkbox next to each payslip to be printed. Or, click the box next to :guilabel:`Reference`, which selects all visible payslips on the page. Then, click the :guilabel:`Print` button to print the payslips." +#: ../../content/applications/hr/payroll/payslips.rst:273 +msgid "To print PDF versions of payslips from the *Payslips to Pay* or :guilabel:`Employee Payslips` pages, first select the desired payslips by clicking on the individual checkbox to the left of each payslip to be printed. Or, click the box to the left of the :guilabel:`Reference` column title, which selects all visible payslips on the page. Then, click the :guilabel:`Print` button to print the payslips." msgstr "" -#: ../../content/applications/hr/payroll/payslips.rst:-1 -msgid "Click on the Print smart button to print payslips to a PDF." -msgstr "" - -#: ../../content/applications/hr/payroll/payslips.rst:206 -msgid "Payslips can also be exported to an Excel spreadsheet. When exporting, all payslips are exported regardless of whether some are selected or not. Click on the :guilabel:`Export All` button (download icon) to export all payslips to an Excel spreadsheet." +#: ../../content/applications/hr/payroll/payslips.rst:279 +msgid "Payslips can also be exported to an Excel spreadsheet. To export **all** payslips, click on the :guilabel:`⚙️ (gear)` icon at the end of the words :guilabel:`Employee Payslips` in the top-left corner. This reveals a drop-down menu. Click :guilabel:`Export All` to export all payslips to a spreadsheet." msgstr "" #: ../../content/applications/hr/payroll/payslips.rst:-1 msgid "Click on the Export All smart button to export all payslips to an Excel payslip." msgstr "" -#: ../../content/applications/hr/payroll/payslips.rst:215 +#: ../../content/applications/hr/payroll/payslips.rst:288 +msgid "To export only select payslips, first select the payslips to be exported from the list. Then, click the checkbox to the left of each individual payslip to select it. As payslips are selected, a smart button appears in the top-center of the page, indicating the number of selected payslips. Then, click the :guilabel:`⚙️ (gear) Actions` icon in the top-center of the page, and click :guilabel:`Export`." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:-1 +msgid "The individual list of employee ayslips with three selected to be exported." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:299 msgid "Both *To Pay* and *All Payslips* display all the detailed information for each payslip." msgstr "" -#: ../../content/applications/hr/payroll/payslips.rst:218 +#: ../../content/applications/hr/payroll/payslips.rst:302 msgid "Batches" msgstr "" -#: ../../content/applications/hr/payroll/payslips.rst:220 +#: ../../content/applications/hr/payroll/payslips.rst:304 msgid "To view payslips in batches, navigate to :menuselection:`Payroll app --> Payslips --> Batches` to display all the payslip batches that have been created. These payslip batches are displayed in a list view, by default." msgstr "" -#: ../../content/applications/hr/payroll/payslips.rst:224 -msgid "Each batch displays the :guilabel:`Name`, :guilabel:`Date From` and :guilabel:`Date To` dates, whether it was a :guilabel:`Credit note`, its :guilabel:`Status`, and the :guilabel:`Company`." +#: ../../content/applications/hr/payroll/payslips.rst:308 +msgid "Each batch displays the :guilabel:`Name`, :guilabel:`Date From` and :guilabel:`Date To` dates, its :guilabel:`Status`, the number of payslips in the batch (:guilabel:`Payslips Count`), and the :guilabel:`Company`." msgstr "" #: ../../content/applications/hr/payroll/payslips.rst:-1 msgid "View displaying all batches created." msgstr "" -#: ../../content/applications/hr/payroll/payslips.rst:231 -msgid "Click on an individual batch to view the details for that batch on a separate page. On this batch detail page, modifications can be made. To make any modifications to a batch, click the :guilabel:`Edit` button. Then, proceed to make any necessary changes." -msgstr "" - -#: ../../content/applications/hr/payroll/payslips.rst:235 -msgid "When all desired changes have been made, click either :guilabel:`Save` to save the changes, or :guilabel:`Discard` to revert back to the original data." -msgstr "" - -#: ../../content/applications/hr/payroll/payslips.rst:238 -msgid "After modifications have been saved, click the :guilabel:`Generate Payslips` button to reveal a :guilabel:`Generate Payslips` pop-up form, in which payslips affected by the changes can be created or modified." -msgstr "" - -#: ../../content/applications/hr/payroll/payslips.rst:242 -msgid "All payslips associated with the batch are displayed in the employees section of the :guilabel:`Generate Payslips` pop-up. To filter the results by either the :guilabel:`Salary Structure` and/or the :guilabel:`Department`, select a salary structure and/or department from the respective drop-down menus." -msgstr "" - -#: ../../content/applications/hr/payroll/payslips.rst:247 -msgid "Only employees that match the selected :guilabel:`Salary Structure` and/or :guilabel:`Department` appear in the employees list. Click the :guilabel:`Generate` button at the bottom of the :guilabel:`Generate Payslips` pop-up window to generate the modified payslips, and close the pop-up window." -msgstr "" - -#: ../../content/applications/hr/payroll/payslips.rst:-1 -msgid "Generate payslips from the edited batch." -msgstr "" - -#: ../../content/applications/hr/payroll/payslips.rst:256 -msgid "Back on the batch details page, click the :guilabel:`Create Draft Entry` smart button to create a draft of the payslips." -msgstr "" - -#: ../../content/applications/hr/payroll/payslips.rst:263 -msgid "Once the draft payslips are created, the button changes to say :guilabel:`Make Payment`. Click the :guilabel:`Make Payment` button. A pop-up window appears, in which the bank journal information must be entered. Select the :guilabel:`Bank Journal` from the drop-down list, and click :guilabel:`Confirm` to process the payslips, and pay the employees." -msgstr "" - -#: ../../content/applications/hr/payroll/payslips.rst:268 -msgid "On the batch detail page, the number of payslips in the batch is accessible via the :guilabel:`Payslips` smart button, located in the top-right corner. Individual payslips for the batch can be viewed by clicking the :guilabel:`Payslips` smart button in the top-right corner." -msgstr "" - -#: ../../content/applications/hr/payroll/payslips.rst:272 -msgid "Use the breadcrumb menu to navigate back to the individual batch detail page, or back to the list of all batches." -msgstr "" - -#: ../../content/applications/hr/payroll/payslips.rst:-1 -msgid "Click the Payslips smart button to view the individual payslips in the batch." -msgstr "" - -#: ../../content/applications/hr/payroll/payslips.rst:280 +#: ../../content/applications/hr/payroll/payslips.rst:317 msgid "Create a new batch" msgstr "" -#: ../../content/applications/hr/payroll/payslips.rst:282 -msgid "To create a new batch of payslips from the :guilabel:`Payslips Batches` page (:menuselection:`Payroll app --> Payslips --> Batches`), click the :guilabel:`Create` button in the upper-left corner. Doing so reveals a blank payslip batch form on a separate page." +#: ../../content/applications/hr/payroll/payslips.rst:319 +msgid "To create a new batch of payslips from the :guilabel:`Payslips Batches` page (:menuselection:`Payroll app --> Payslips --> Batches`), click the :guilabel:`New` button in the top-left corner. Doing so reveals a blank payslip batch form on a separate page." msgstr "" -#: ../../content/applications/hr/payroll/payslips.rst:286 -msgid "On the new payslip batch form, enter the :guilabel:`Name` for the batch, and select the date range to which the batch applies, by clicking the :guilabel:`▼ (drop-down arrow)` icon in the :guilabel:`Period` fields, which reveals a calendar pop-up window. From this calendar pop-up window, navigate to the correct month, and click on the corresponding day for both the start and end dates." +#: ../../content/applications/hr/payroll/payslips.rst:323 +msgid "On the new payslip batch form, enter the :guilabel:`Batch Name`." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:325 +msgid "Next, select the date range to which the batch applies. Click into one of the :guilabel:`Period` fields, and a calendar pop-up window appears. From this calendar pop-up window, navigate to the correct month, and click on the corresponding day for both the start and end dates of the batch." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:329 +msgid "The current company populates the :guilabel:`Company` field. If operating in a multi-company environment, it is **not** possible to modify the :guilabel:`Company` from the form. The batch **must** be created while in the database for the desired company." msgstr "" #: ../../content/applications/hr/payroll/payslips.rst:-1 msgid "Enter the details for the new batch." msgstr "" -#: ../../content/applications/hr/payroll/payslips.rst:295 -msgid "If the batch is a credit note, check the box next to :guilabel:`Credit Note`. Then, in the :guilabel:`Generation Date` field, select the date the payslips should be generated from a calendar pop-up window. This generated date is reflected in the accounting journal entries." +#: ../../content/applications/hr/payroll/payslips.rst:340 +msgid "Process a batch" msgstr "" -#: ../../content/applications/hr/payroll/payslips.rst:299 -msgid "Lastly, in the :guilabel:`Company` field, select the company these payslips are written against." +#: ../../content/applications/hr/payroll/payslips.rst:342 +msgid "Click on an individual batch to view the details for that batch on a separate page. On this batch detail page, different options (buttons) appear at the top, depending on the status of the batch:" msgstr "" -#: ../../content/applications/hr/payroll/payslips.rst:301 -msgid "When all the information on the payslip batch form is correct, click the :guilabel:`Save` button to save the information. To delete the entry, click the :guilabel:`Discard` button." +#: ../../content/applications/hr/payroll/payslips.rst:345 +msgid ":guilabel:`New` status: batches without any payslips added to them have a status of :guilabel:`New`. The following button options appear for these batches:" msgstr "" -#: ../../content/applications/hr/payroll/payslips.rst:304 -msgid "To create the payslips for the newly-created batch, click the :guilabel:`Generate Payslips` button at the top of the form." +#: ../../content/applications/hr/payroll/payslips.rst:0 +msgid "A batch with a status of new, with the available buttons highlighted." msgstr "" -#: ../../content/applications/hr/payroll/payslips.rst:307 -msgid "When clicked, a pop-up window appears showing all the payslips that will be created. To remove any individual payslips, click the black :guilabel:`✖ (x mark)` icon at the far right of the payslip line." +#: ../../content/applications/hr/payroll/payslips.rst:352 +msgid ":guilabel:`Add Payslips`: click the :guilabel:`Add Payslips` button to add payslips to the batch, and an :guilabel:`Add Payslips` pop-up window appears. Only payslips that can be added to the batch (payslips not currently part of a batch) appear on the list." msgstr "" -#: ../../content/applications/hr/payroll/payslips.rst:311 -msgid "If a specific :guilabel:`Salary Structure` or :guilabel:`Department` needs to be specified for the batch, select them from the corresponding drop-down menus." +#: ../../content/applications/hr/payroll/payslips.rst:356 +msgid "Select the desired payslips by clicking the checkbox to the left of each payslip name, then click the :guilabel:`Select` button to add them to the batch. Once payslips are selected and added to the batch, the status changes to :guilabel:`Confirmed`." msgstr "" -#: ../../content/applications/hr/payroll/payslips.rst:314 -msgid "Click the :guilabel:`Generate` button at the bottom of the pop-up window to create the payslips for the batch." +#: ../../content/applications/hr/payroll/payslips.rst:360 +msgid ":guilabel:`Generate Payslips`: after payslips have been added to the batch, click the :guilabel:`Generate Payslips` button to process the payslips and create individual payslips in the database." msgstr "" -#: ../../content/applications/hr/payroll/payslips.rst:-1 -msgid "Generate payslips for the new batch." +#: ../../content/applications/hr/payroll/payslips.rst:364 +msgid "A :guilabel:`Generate Payslips` pop-up window appears. If only a specific :guilabel:`Salary Structure` and/or specific :guilabel:`Department` is desired to make payslips for, select them from the corresponding drop-down menus. If no selections are made, then all payslips listed in the pop-up window are processed as usual." msgstr "" -#: ../../content/applications/hr/payroll/payslips.rst:322 -msgid "On the :guilabel:`Generate Payslips` pop-up window, selecting a :guilabel:`Department` and/or :guilabel:`Salary Structure` only displays payslips that apply to those specifically-selected parameters." +#: ../../content/applications/hr/payroll/payslips.rst:369 +msgid "Click the :guilabel:`Generate` button to create the payslips. The :guilabel:`Generate Payslips` button changes to a :guilabel:`Create Draft Entry` button, and the status changes to :guilabel:`Confirmed`." msgstr "" -#: ../../content/applications/hr/payroll/payslips.rst:326 -msgid "If there are any errors or issues preventing the payslips from being generated, an error message appears in the top-right section. This error box disappears on its own after several seconds, or the :guilabel:`✖ (x mark)` icon can be clicked to close the alert." +#: ../../content/applications/hr/payroll/payslips.rst:373 +msgid ":guilabel:`Confirmed` status: batches that have been created and have payslips in them, but the payslips have *not* been processed, have a status of :guilabel:`Confirmed`. The following two button options appear for these batches:" msgstr "" -#: ../../content/applications/hr/payroll/payslips.rst:330 -msgid "To remedy the issue, make any necessary modifications (e.g. removing any payslip lines that cannot be processed), then click the :guilabel:`Generate` button again." +#: ../../content/applications/hr/payroll/payslips.rst:0 +msgid "A batch with a status of confirmed, with the available buttons highlighted." msgstr "" -#: ../../content/applications/hr/payroll/payslips.rst:333 -msgid "Once the payslips have been successfully generated, the screen returns to the payslip batch form." +#: ../../content/applications/hr/payroll/payslips.rst:381 +msgid ":guilabel:`Create Draft Entry`: click the :guilabel:`Create Draft Entry` button to confirm the individual payslips (and the batch), and create a draft of the payslips. The batch now has a status of :guilabel:`Done`." msgstr "" -#: ../../content/applications/hr/payroll/payslips.rst:335 -msgid "From here, click the :guilabel:`Generate Draft Entry` button to change the payslips' status from :guilabel:`Draft` to :guilabel:`Done`." +#: ../../content/applications/hr/payroll/payslips.rst:384 +#: ../../content/applications/hr/payroll/payslips.rst:406 +msgid ":guilabel:`Set to Draft`: if at any point the batch needs to be reverted back to a status of :guilabel:`New`, click the :guilabel:`Set to Draft` button. This action does **not** remove any payslips that have already been added to the batch." msgstr "" -#: ../../content/applications/hr/payroll/payslips.rst:338 -msgid "Once payslips have been generated, click the :guilabel:`Make Payment` button to process the payments. Doing so reveals a pop-up window, in which the proper banking information must be entered. In this pop-up window, select the appropriate :guilabel:`Bank Journal` from the drop-down menu, and enter the appropriate file name." +#: ../../content/applications/hr/payroll/payslips.rst:388 +msgid ":guilabel:`Done` status: batches with confirmed payslips in them have a status of :guilabel:`Done`. The following button options appear for these batches:" msgstr "" -#: ../../content/applications/hr/payroll/payslips.rst:343 -msgid "When done, click the :guilabel:`Confirm` button to confirm the information, or click :guilabel:`Cancel` to discard." +#: ../../content/applications/hr/payroll/payslips.rst:0 +msgid "A batch with a status of done, with the available buttons highlighted." msgstr "" -#: ../../content/applications/hr/payroll/payslips.rst:347 -msgid "Generate commission payslips" +#: ../../content/applications/hr/payroll/payslips.rst:395 +msgid ":guilabel:`Create Payment Report`: click the :guilabel:`Create Payment Report` button, and a :guilabel:`Select a bank journal` pop-up window appears. Select the correct bank journal from the drop-down menu." msgstr "" -#: ../../content/applications/hr/payroll/payslips.rst:349 -msgid "Commission payslips can be generated directly from the :guilabel:`Payslips Batches` page (:menuselection:`Payroll app --> Payslips --> Batches`). To generate commission payslips from this page, click on the desired batch (or batches) to create commissions payslips for, then click the :guilabel:`Generate Commission Payslips` button." +#: ../../content/applications/hr/payroll/payslips.rst:399 +msgid "The batch name appears in the :guilabel:`File name` field, but this can be modified, if desired. Finally, click :guilabel:`Confirm` to process the payslips, and pay the employees." msgstr "" -#: ../../content/applications/hr/payroll/payslips.rst:354 -msgid "Doing so reveals a :guilabel:`Generate Commission Payslip` pop-up window, in which the necessary information **must** be filled out." +#: ../../content/applications/hr/payroll/payslips.rst:401 +msgid ":guilabel:`Mark as paid`: after the payments have been created via the :guilabel:`Create Payment Report` button, the payslips need to be marked as paid in the database." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:404 +msgid "Click the :guilabel:`Mark as paid` button, and the status of the batch changes to :guilabel:`Paid`." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:410 +msgid ":guilabel:`Paid` status: batches that have been completed have a status of :guilabel:`Paid`. No other button options appear for this status." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:0 +msgid "A batch with a status of paid, with the available buttons highlighted." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:417 +msgid "On the batch detail page, the individual payslips in the batch are accessible, via the :guilabel:`Payslips` smart button, located above the batch information, in the center. Click the :guilabel:`Payslips` smart button to view a list of all the individual payslips." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:421 +msgid "Use the breadcrumb menu to navigate back to the individual batch detail page, or back to the list of all batches." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:425 +msgid "Generate warrant payslips" +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:427 +msgid "Commissions are paid to employees in Odoo using *warrant payslips*." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:429 +msgid "Warrant payslips can be generated directly from the :guilabel:`Payslips Batches` page (:menuselection:`Payroll app --> Payslips --> Batches`)." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:432 +msgid "First, select the desired batches by clicking the box to the left of each batch for which commission payslips should be created. Next, click the :guilabel:`Generate Warrant Payslips` button at the top of the page." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:436 +msgid "Doing so reveals a :guilabel:`Generate Warrant Payslips` pop-up window, in which the necessary information **must** be filled out." msgstr "" #: ../../content/applications/hr/payroll/payslips.rst:-1 msgid "Enter the commission details." msgstr "" -#: ../../content/applications/hr/payroll/payslips.rst:361 -msgid "On this pop-up window, click on the drop-down menus, located beside the :guilabel:`Period` field, to reveal calendar pop-up windows. On these calendar pop-up windows, select the desired period for which the payslips are being generated. Using the :guilabel:`< (left)` and :guilabel:`> (right)` arrows, navigate to the correct month, and click on the date to select it." +#: ../../content/applications/hr/payroll/payslips.rst:443 +msgid "In this pop-up window, click on the drop-down menus, located beside the :guilabel:`Period` field, to reveal calendar pop-up windows. On these calendar pop-up windows, select the desired period for which the payslips are being generated. Using the :guilabel:`< (left)` and :guilabel:`> (right)` arrow icons, navigate to the correct month, and click on the date to select it." msgstr "" -#: ../../content/applications/hr/payroll/payslips.rst:366 +#: ../../content/applications/hr/payroll/payslips.rst:448 msgid "In the :guilabel:`Department` field, select the desired department from the drop-down menu." msgstr "" -#: ../../content/applications/hr/payroll/payslips.rst:368 +#: ../../content/applications/hr/payroll/payslips.rst:450 msgid "When a department is selected, the employees listed for that department appear in the :guilabel:`Employee` section." msgstr "" -#: ../../content/applications/hr/payroll/payslips.rst:371 -msgid "Under the :guilabel:`Employee` section, enter the :guilabel:`Commission Amount` for each employee in the appropriate column. To remove an employee, click the :guilabel:`🗑️ (trash)` icon to remove the line." +#: ../../content/applications/hr/payroll/payslips.rst:453 +msgid "Under the :guilabel:`Employee` section, enter the :guilabel:`Commission Amount` for each employee in the far-right column. To remove an employee, click the :guilabel:`🗑️ (trash)` icon to remove the line." msgstr "" -#: ../../content/applications/hr/payroll/payslips.rst:375 +#: ../../content/applications/hr/payroll/payslips.rst:457 msgid "Add a new entry by clicking :guilabel:`Add a Line`, and entering the :guilabel:`Employee` and the appropriate :guilabel:`Commission Amount`." msgstr "" -#: ../../content/applications/hr/payroll/payslips.rst:378 -msgid "Click the :guilabel:`Upload Your File` button to add a file, if necessary. Any file type is accepted." +#: ../../content/applications/hr/payroll/payslips.rst:460 +msgid "Click the :guilabel:`Upload your file` button to add a file, if necessary. Any file type is accepted." msgstr "" -#: ../../content/applications/hr/payroll/payslips.rst:381 -msgid "Using the drop-down menu beside the :guilabel:`Commission Type` field, select either :guilabel:`Classic Commission` or :guilabel:`Warrant`. :guilabel:`Classic` is the most typical of commission, while :guilabel:`Warrant` is primarily used for Belgium companies." +#: ../../content/applications/hr/payroll/payslips.rst:463 +msgid "Once all the commissions are properly entered, click the :guilabel:`Generate Payslips` button to create the warrant payslips in a batch." msgstr "" -#: ../../content/applications/hr/payroll/payslips.rst:385 -msgid "Once all the commissions are properly entered, click the :guilabel:`Generate Payslips` button to create the commission payslips." +#: ../../content/applications/hr/payroll/payslips.rst:466 +msgid ":ref:`Process the batch ` in the same way as a typical batch to complete the payment process." msgstr "" #: ../../content/applications/hr/payroll/reporting.rst:5 -msgid "The :guilabel:`Reporting` section of the *Payroll* app offers a variety of reports to choose from. The :guilabel:`Payroll`, :guilabel:`Meal Vouchers`, :guilabel:`Attachment of Salary`, and :guilabel:`DMFA` reports are universal and available for all companies regardless of location. The :guilabel:`Paid Time Off Allocation`, :guilabel:`273S Sheet`, and :guilabel:`274.XX Sheets` reports are specific to Belgian companies only." +msgid "The *Reporting* section of the *Payroll* app offers a variety of reports to choose from, organized by location." +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:8 +msgid "The *Payroll* report, *Work Entry Analysis* report, and *Salary Attachment Report* are default reports in the *Payroll* app, and are available for all companies, regardless of location." msgstr "" #: ../../content/applications/hr/payroll/reporting.rst:11 -msgid "To view a report, go to :menuselection:`Payroll --> Reporting` and click on the specific report." +msgid "Beneath the three default reports are all localization-based reports, organized by country, in alphabetical order. These reports contain all the various information for the offered benefits and local tax laws." +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:15 +msgid "To view all the available reports for the database, including all the localization-specific ones, navigate to :menuselection:`Payroll app --> Reporting` to view the available reports in a drop-down menu. Click on a specific report to view it." msgstr "" #: ../../content/applications/hr/payroll/reporting.rst:-1 -msgid "Report dashboard view." +msgid "Report dashboard view showing extra reports for Belgium databases." msgstr "" -#: ../../content/applications/hr/payroll/reporting.rst:17 -msgid "If a report is unavailable to a company, a user error pops up, stating `You must be logged in to a Belgian company to use this feature.`" +#: ../../content/applications/hr/payroll/reporting.rst:23 +msgid "If a report is unavailable to a user, an :guilabel:`Invalid Operation` pop-up window appears, stating: :guilabel:`You must be logged in to a (country) company to use this feature`, where \"(country)\" is the specific country the company is configured for." msgstr "" -#: ../../content/applications/hr/payroll/reporting.rst:20 -msgid "At the top of each report, click on :guilabel:`Filters` to display the optional filters for the specific report. Filters show information that matches the specific filter parameters. For example, when selecting the :guilabel:`Last 365 Day Payslip` filter, only payslips for the last 365 days appear. All reports have the option to add a custom filter, and each have different default custom filter options. Select the parameters, then click the :guilabel:`Apply` button." +#: ../../content/applications/hr/payroll/reporting.rst:28 +msgid "Default reports" msgstr "" -#: ../../content/applications/hr/payroll/reporting.rst:30 -msgid "Clicking on :guilabel:`Favorites` displays three options: :guilabel:`Save the current search`, :guilabel:`Add the search to the dashboard`, or :guilabel:`Insert the search to a Google spreadsheet`." +#: ../../content/applications/hr/payroll/reporting.rst:33 +msgid "Click on :menuselection:`Payroll app --> Reporting --> Payroll` to display the :guilabel:`Payroll Analysis` report. This report shows all the payslips generated in the last 365 days, due to the default :ref:`filter `: `Last 365 Days Payslip`." msgstr "" #: ../../content/applications/hr/payroll/reporting.rst:-1 -msgid "Favorite options for reports." +msgid "Payroll overview report showing payroll for the last 365 days." msgstr "" #: ../../content/applications/hr/payroll/reporting.rst:41 -msgid "Click on :menuselection:`Payroll --> Reporting --> Payroll` to display the :guilabel:`Payroll Analysis` report." +msgid "The report can display metrics for a variety of parameters. Click the :guilabel:`Measures` box to view a drop-down menu with the various metric options to display. The default options available include:" +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:45 +msgid ":guilabel:`# Payslip`" +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:46 +msgid ":guilabel:`Basic Wage`" +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:47 +msgid ":guilabel:`Basic Wage for Time Off`" msgstr "" #: ../../content/applications/hr/payroll/reporting.rst:48 -msgid "This shows all the payslips generated in the last 365 days. The report can display metrics for a variety of parameters. Click the :guilabel:`Measures` box to view a drop-down menu with the various options to display. The options available include: :guilabel:`# Payslip`, :guilabel:`Basic Wage`, :guilabel:`Basic Wage for Time Off`, :guilabel:`Days of Paid Time Off`, :guilabel:`Days of Unforeseen Absence`, :guilabel:`Days of Unpaid Time Off`, :guilabel:`Gross Wage`, :guilabel:`Net Wage`, :guilabel:`Number of Days`, :guilabel:`Number of Hours`, :guilabel:`Work Days`, :guilabel:`Work Hours`, and :guilabel:`Count`." +msgid ":guilabel:`Days of Paid Time Off`" msgstr "" -#: ../../content/applications/hr/payroll/reporting.rst:61 +#: ../../content/applications/hr/payroll/reporting.rst:49 +msgid ":guilabel:`Days of Unforeseen Absence`" +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:50 +msgid ":guilabel:`Days of Unpaid Time Off`" +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:51 +msgid ":guilabel:`Gross Wage`" +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:52 +msgid ":guilabel:`Net Wage`" +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:53 +msgid ":guilabel:`Number of Days`" +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:54 +msgid ":guilabel:`Number of Hours`" +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:55 +msgid ":guilabel:`Work Days`" +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:56 +msgid ":guilabel:`Work Hours`" +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:57 +msgid ":guilabel:`Count`" +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:59 +msgid ":guilabel:`Net Wage` is the default metric for the :guilabel:`Payroll` report." +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:-1 +msgid "The various measures available to display for the Payroll Analysis report." +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:66 msgid "Line chart" msgstr "" -#: ../../content/applications/hr/payroll/reporting.rst:63 -msgid "A line chart is the default view for the *Payroll Analysis* report. If a different view was selected, click on the :guilabel:`Line Chart` icon (middle icon) in the menu bar to change the view back to a line chart. An option to display the line chart in ascending or descending order appears at the end of the options." +#: ../../content/applications/hr/payroll/reporting.rst:68 +msgid "A line chart is the default view for the *Payroll* report. If a different view is selected, click the :guilabel:`Line Chart` button (represented by a :guilabel:`📈 (chart increasing)` icon) in the menu bar to change the view back to a line chart." msgstr "" -#: ../../content/applications/hr/payroll/reporting.rst:73 +#: ../../content/applications/hr/payroll/reporting.rst:72 +msgid "Several options are available for the line chart. Click the corresponding button to activate the selection, and change the way the data is presented. These icons appear at the end of the chart options. The various options are:" +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:78 +msgid ":guilabel:`Stacked`: data is presented with each metric in its own line, \"stacked\" on top of each other. This helps visualize the distribution and variances between different categories." +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:83 +msgid ":guilabel:`Cumulative`: data is presented with each metric on an individual line, with the total amount calculated by combining all the lines. This provides a comprehensive view of the cumulative data." +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:89 +msgid ":guilabel:`Descending`: data is shown with the largest values on the left side of the chart, gradually decreasing towards the smallest values on the right side, along the x-axis. This arrangement helps emphasize trends or outliers at the extremes." +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:95 +msgid ":guilabel:`Ascending`: data is presented with the smallest values on the left side of the chart, increasing towards the largest values on the right side, along the x-axis. This arrangement can be useful for highlighting progressive growth or trends." +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:100 +msgid "These options can be combined to create a variety of views." +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:-1 +msgid "Menu buttons with the line chart called out, along with the other option buttons." +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:107 msgid "Bar chart" msgstr "" -#: ../../content/applications/hr/payroll/reporting.rst:75 -msgid "To display the data in a bar chart, click on the :guilabel:`Bar Chart` icon (first icon) in the menu bar." +#: ../../content/applications/hr/payroll/reporting.rst:109 +msgid "To display the data in a bar chart, click on the :guilabel:`Bar Chart` button (represented by a :guilabel:`📊 (bar chart)` icon) in the menu bar." msgstr "" -#: ../../content/applications/hr/payroll/reporting.rst:82 -msgid "Click the :guilabel:`Stacked` icon to view the bar chart in a stacked format (where multiple values appear in each column). An option to display the columns in ascending or descending order appears at the end of the options." +#: ../../content/applications/hr/payroll/reporting.rst:112 +msgid "Click the :ref:`Stacked ` icon to view the bar chart in a stacked format (where multiple values appear in each column). :ref:`Cumulative ` bar charts are useful for visualizing the progression over time or other categories." msgstr "" -#: ../../content/applications/hr/payroll/reporting.rst:87 -msgid "Clicking an option enables it. To disable the option, click it again. When the option is enabled it appears grey. When it is inactive, it appears white." +#: ../../content/applications/hr/payroll/reporting.rst:116 +msgid "An option to display the columns in :ref:`Descending ` or :ref:`Ascending ` order appears at the end of the options." msgstr "" -#: ../../content/applications/hr/payroll/reporting.rst:91 +#: ../../content/applications/hr/payroll/reporting.rst:-1 +msgid "Menu buttons with the bar chart called out, along with the other option buttons." +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:124 +msgid "Clicking an option enables it. To turn off the option, click it again. When the option is enabled the icon appears lighter, with a turquoise outline. When it is inactive, it appears gray, with no outline." +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:129 msgid "Pie chart" msgstr "" -#: ../../content/applications/hr/payroll/reporting.rst:93 -msgid "To display the data in a pie chart, click on the :guilabel:`Pie Chart` icon (last icon) in the menu bar. There are no additional options available in this view." +#: ../../content/applications/hr/payroll/reporting.rst:131 +msgid "To display the data in a pie chart, click on the :guilabel:`Pie Chart` button (represented by a :guilabel:`(pie chart)` icon) in the menu bar. There are no additional options available in this view." msgstr "" -#: ../../content/applications/hr/payroll/reporting.rst:101 +#: ../../content/applications/hr/payroll/reporting.rst:-1 +msgid "Menu buttons with the pie chart called out." +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:140 msgid "Pivot table" msgstr "" -#: ../../content/applications/hr/payroll/reporting.rst:103 -msgid "The bottom half of the :guilabel:`Payroll Analysis` dashboard presents a pivot table no matter which type of chart is selected for the top of the dashboard. The default information displayed is the number of payslips, net wage, gross wage, days of paid time off, and days of unpaid time off. The information is divided by department. To display more information on the report, select the :guilabel:`Measures` drop-down menu, then click on any other items to display." +#: ../../content/applications/hr/payroll/reporting.rst:142 +msgid "To display the data in a pivot table, click on the :guilabel:`Pivot` button (represented by a :guilabel:`(pivot)` icon) located in the far-right side of the top menu bar." msgstr "" -#: ../../content/applications/hr/payroll/reporting.rst:113 -msgid "To sort the entries by a specific column, such as :guilabel:`Net Wage`, click on the column name twice. The first click selects the column, and the second click sorts the information in descending order." +#: ../../content/applications/hr/payroll/reporting.rst:145 +msgid "The default information displayed includes the number of payslips (:guilabel:`# Payslip`), the :guilabel:`Net Wage`, the :guilabel:`Gross Wage`, the number of :guilabel:`Days of Paid Time Off`, and the number of :guilabel:`Days of Unpaid Time Off`. The information is organized by department." +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:149 +msgid "To display more information on the report, click the :guilabel:`Measures` button to reveal a drop-down menu. Then, click on any other metric to display it on the pivot table." msgstr "" #: ../../content/applications/hr/payroll/reporting.rst:-1 -msgid "To sort information by descending order, click the column head twice." -msgstr "" - -#: ../../content/applications/hr/payroll/reporting.rst:121 -#: ../../content/applications/hr/payroll/reporting.rst:172 -msgid "To export the data in an XLSX format, click the :guilabel:`Download xlsx` icon. The information will be downloaded into an Excel spreadsheet." -msgstr "" - -#: ../../content/applications/hr/payroll/reporting.rst:-1 -msgid "Download an Excel spreadsheet of the data by clicking the download button." -msgstr "" - -#: ../../content/applications/hr/payroll/reporting.rst:128 -#: ../../content/applications/hr/payroll/reporting.rst:179 -msgid "The data can be inserted into a spreadsheet by clicking the :guilabel:`Insert in Spreadsheet` button. A pop-up appears asking which spreadsheet to place the information in. Select an existing spreadsheet or enter the name for a new spreadsheet. Click the :guilabel:`Confirm` button to move to a spreadsheet view with all the information populated." -msgstr "" - -#: ../../content/applications/hr/payroll/reporting.rst:-1 -msgid "Send the data to a spreadsheet." -msgstr "" - -#: ../../content/applications/hr/payroll/reporting.rst:137 -msgid "Once in the spreadsheet view, click on :guilabel:`File`, then select :guilabel:`Save` to save the data, or :guilabel:`Save as Template` to save the setting as a template to use in the future." -msgstr "" - -#: ../../content/applications/hr/payroll/reporting.rst:141 -#: ../../content/applications/hr/payroll/reporting.rst:188 -msgid "The *Documents* application must be installed in order to use the :guilabel:`Insert in Spreadsheet` option." -msgstr "" - -#: ../../content/applications/hr/payroll/reporting.rst:146 -msgid "Meal Vouchers" -msgstr "" - -#: ../../content/applications/hr/payroll/reporting.rst:148 -msgid ":guilabel:`Meal Vouchers` provides an overview of the meal vouchers used by employees, and can be shown by :guilabel:`Day`, :guilabel:`Week`, :guilabel:`Month`, :guilabel:`Quarter`, or :guilabel:`Year`. The default view is by month." -msgstr "" - -#: ../../content/applications/hr/payroll/reporting.rst:-1 -msgid "Meal voucher" +msgid "Pivot table view with the various metrics called out." msgstr "" #: ../../content/applications/hr/payroll/reporting.rst:156 -msgid "To change the displayed view, click on :guilabel:`Total`. The data collapses, showing only the count column. Click on :guilabel:`Total` again, then hover over :guilabel:`Day`, then click on one of the other time-period options available." +msgid "To sort the entries by a specific column, such as :guilabel:`Net Wage`, click on the column name twice. The first click selects the column, and the second click sorts the information in descending order." msgstr "" -#: ../../content/applications/hr/payroll/reporting.rst:164 -msgid "It is possible to compare the current meal voucher report to the one for the previous time period or the previous year. To view these comparisons, click on the :guilabel:`Comparison` drop-down menu at the top, then select either :guilabel:`Date: Previous Period` or :guilabel:`Date: Previous Year`." +#: ../../content/applications/hr/payroll/reporting.rst:160 +#: ../../content/applications/hr/payroll/reporting.rst:225 +msgid "To export the data in an XLSX format, click the :guilabel:`Download xlsx` button, represented by a :guilabel:`⬇️ (down arrow above a horizontal bar)` icon, located at the far-right of the available icons. The information is then downloaded into a spreadsheet." +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:-1 +msgid "The menu options with the download button highlighted." +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:168 +msgid "Any report can be inserted into a spreadsheet by clicking the :guilabel:`Insert in Spreadsheet` button. A :guilabel:`Select a spreadsheet to insert your (type of report)` pop-up window appears, asking which spreadsheet to place the information in. Select an existing spreadsheet or dashboard, or select a new :guilabel:`Blank spreadsheet`. Click the :guilabel:`Confirm` button to move to a spreadsheet view with the report added to it." +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:-1 +msgid "The view of data sent to a spreadsheet." +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:181 +msgid "If the *Documents* app is **not** installed, the :guilabel:`Insert in Spreadsheet` option places the newly-created spreadsheet in the *Dashboards* app." msgstr "" #: ../../content/applications/hr/payroll/reporting.rst:184 -msgid "Once in the spreadsheet view, click on :guilabel:`File`, then select :guilabel:`Save` to save the data, or :guilabel:`Save as Template` to save the settings as a template to use in the future." +msgid "If the *Documents* application **is** installed, the spreadsheet has the option to be stored in either the *Dashboards* app or *Documents* app." msgstr "" -#: ../../content/applications/hr/payroll/reporting.rst:192 -msgid "Attachment of Salary" +#: ../../content/applications/hr/payroll/reporting.rst:188 +msgid "Work entry analysis" +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:190 +msgid "The default :guilabel:`Work entry analysis` report provides an overview of the validated work entries for the current month. To view this report, navigate to :menuselection:`Payroll app --> Reporting --> Work Entry Analysis`." msgstr "" #: ../../content/applications/hr/payroll/reporting.rst:194 -msgid "The :guilabel:`Attachment of Salary` report shows all deductions or allocations per employee, such as child support payments and wage garnishments." +msgid "The work entries appear in a pivot table, with the default filters of `Current month: (Month)(Year)` and `Validated`. The various types of :doc:`work_entries` are listed on the left-hand side (x-axis), while the :guilabel:`Total` values appear along the top (the y-axis)." +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:198 +msgid "To change the displayed view, click the :guilabel:`➕ (plus)` icon next to the word :guilabel:`Total`, then click on one of the grouping options. The available options are :guilabel:`Work Entry Type`, :guilabel:`Employee`, and :guilabel:`Department`. If in a multi-company database, a :guilabel:`Company` option also appears." +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:203 +msgid "To add a new group to sort the data, click :guilabel:`Add Custom Group`, then click one of the presented options." +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:207 +msgid "Wherever a :guilabel:`➕ (plus)` icon appears on a pivot table, the information can be further grouped. Click on a :guilabel:`➕ (plus)` icon to reveal the available grouping options." +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:210 +msgid "Click on a :guilabel:`➖ (minus)` icon anywhere on the pivot table to remove that respective grouping." +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:213 +msgid "It is possible to compare the current :guilabel:`Work entry analysis` report to the previous month or the previous year. To view these comparisons, click the :guilabel:`⬇️ (down arrow)` icon in the search bar to reveal the various :ref:`filter ` and grouping options." +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:217 +msgid "In the section titled :guilabel:`Comparison`, click on either :guilabel:`Current Month: Previous Period` or :guilabel:`Current Month: Previous Year`. The report updates and displays the previous time period values, as well as the :guilabel:`Variation` between the two." +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:-1 +msgid "A pivot table comparing the work entries of the current month and the previous month." +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:229 +msgid "The data can also be inserted into a spreadsheet. Click the :guilabel:`Insert in Spreadsheet` button and a :guilabel:`Select a spreadsheet to insert your (type of report)` pop-up window appears, asking which spreadsheet to place the information in. Select an existing spreadsheet or dashboard, or select a new :guilabel:`Blank spreadsheet`. Click the :guilabel:`Confirm` button to move to a spreadsheet view with the report added to it." +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:236 +msgid "The work entry analysis spreadsheet is :ref:`stored in the same locations ` as a pivot table." +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:240 +msgid "Salary attachment report" +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:242 +msgid "The :guilabel:`Salary Attachment Report` shows all deductions or allocations per employee, such as child support payments and wage garnishments. To view this report, navigate to :menuselection:`Payroll app --> Reporting --> Salary Attachment Report`." msgstr "" #: ../../content/applications/hr/payroll/reporting.rst:-1 msgid "View the Attachment of Salary report that shows all salary garnishments." msgstr "" -#: ../../content/applications/hr/payroll/reporting.rst:201 -msgid "The employees are listed in the left-side column, while the different deductions are listed in the top row, organized by month." +#: ../../content/applications/hr/payroll/reporting.rst:250 +msgid "The employees are listed in the left-side column, while the different deductions are listed in the top row, organized by deduction and monthly individual payslips." msgstr "" -#: ../../content/applications/hr/payroll/reporting.rst:204 -msgid "The report can be exported as a XLSX file, or inserted into a spreadsheet, using the corresponding buttons at the top." +#: ../../content/applications/hr/payroll/reporting.rst:253 +msgid "The report can be exported as an XLSX file, or inserted into a spreadsheet, using the corresponding buttons at the top." msgstr "" -#: ../../content/applications/hr/payroll/reporting.rst:207 -msgid "Clicking on the :guilabel:`Measures` button shows options for how the data is displayed. :guilabel:`Assignment of salary`, :guilabel:`Attachment of salary`, :guilabel:`Child support`, and :guilabel:`Count`, can all be selected or deselected by clicking on the item. If an item has a check mark, it is displayed." +#: ../../content/applications/hr/payroll/reporting.rst:256 +msgid "Click the :guilabel:`Measures` button to reveal the options of what data can be displayed. :guilabel:`Assignment of salary`, :guilabel:`Attachment of salary`, :guilabel:`Child support`, and :guilabel:`Count` can all be selected or deselected by clicking on the item. If an item has a checkmark next to it, that information is displayed." msgstr "" #: ../../content/applications/hr/payroll/reporting.rst:-1 -msgid "Select the options that be displayed in the report." +msgid "Select the options to be displayed in the Salary Attachment Report." msgstr "" -#: ../../content/applications/hr/payroll/reporting.rst:216 -msgid "The salary attachment report can be compared to the one for the previous time period or the previous year. To view these comparisons, click on the on the :guilabel:`Comparison` drop-down menu at the top, then select either :guilabel:`Payslip End Date: Previous Period` or :guilabel:`Payslip End Date: Previous Year`." +#: ../../content/applications/hr/payroll/reporting.rst:265 +msgid "The :guilabel:`Salary Attachment Report` can be compared to the report for the previous time period or the previous year. To view these comparisons, click the :guilabel:`⬇️ (down arrow)` icon in the search bar to reveal the various :ref:`filter ` and grouping options." +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:269 +msgid "In the section titled :guilabel:`Comparison`, click on either :guilabel:`Payslip End Date: Previous Period` or :guilabel:`Payslip End Date: Previous Year`. The report updates and displays the previous time period values, as well as the :guilabel:`Variation` between the two." +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:278 +msgid "At the top of each report, the default filters are shown inside the :guilabel:`Search...` box." +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:280 +msgid "Click the :guilabel:`⬇️ (down arrow)` icon in the search bar to display the available :guilabel:`Filters`. Filters show information that match the specific filter parameters." +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:284 +msgid "The :guilabel:`Work Entries Analysis` report has two default filters, the `Current month:(Month) (Year)` filter, and the `Validated` filter." +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:-1 +msgid "Filters enabled for the Work Entries Analysis report." +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:291 +msgid "The :guilabel:`Payroll` report has only one default filter, the `Last 365 Days Payslip` filter." +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:293 +msgid "The :guilabel:`Salary Attachment Report` has only one default filter, the `Payslip End Date: (Year)` filter." +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:296 +msgid "All reports can include custom filters, or group information, by different metrics (employee, department, company, etc.)." +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:299 +msgid "Some reports have the option to compare the current report to the previous time period or year (a :guilabel:`Comparison` option)." +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:302 +msgid "Click on a parameter to select it and activate it. The report is immediately updated with the new parameters." +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:305 +msgid "The updated report can be set as a *favorite* report, meaning the parameters are stored for quick access in the future. To do that, click :guilabel:`Save the current search`, under the :guilabel:`Favorites` section, located in the search bar drop-down mega menu of filter options. Doing so reveals two options and a :guilabel:`Save` button." +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:310 +msgid "To set the current report as the default configuration when the report is accessed, check the box next to :guilabel:`Default filter`. If the current report should be accessible to everyone in the database, check the box next to :guilabel:`Share`." +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:314 +msgid "Finally, click :guilabel:`Save`, which saves the currently configured report. Then, it appears beneath the :guilabel:`Favorites` in the search bar drop-down mega menu of filter options." msgstr "" #: ../../content/applications/hr/payroll/work_entries.rst:5 @@ -5792,10 +6270,10 @@ msgid ":guilabel:`Applicant: Your Salary Package`: this template is used when of msgstr "" #: ../../content/applications/hr/recruitment.rst:177 -msgid "Email templates can be created, modified, and deleted to suit the needs of a business. For more information on email templates, refer to the :doc:`../general/email_communication/email_template` document." +msgid "Email templates can be created, modified, and deleted to suit the needs of a business. For more information on email templates, refer to the :doc:`../general/companies/email_template` document." msgstr "" -#: ../../content/applications/hr/recruitment.rst:181 +#: ../../content/applications/hr/recruitment.rst:180 msgid "To manually send an email click :guilabel:`Send message` in the chatter. A text box appears, as well as the applicant's email address. Click the :guilabel:`⤢ (double arrow)` full composer icon in the bottom right corner of the :guilabel:`Send Message` tab in the chatter." msgstr "" @@ -5803,31 +6281,31 @@ msgstr "" msgid "Send an email from the chatter." msgstr "" -#: ../../content/applications/hr/recruitment.rst:189 +#: ../../content/applications/hr/recruitment.rst:188 msgid "An email composer pop-up loads, with the :guilabel:`Recipients` and :guilabel:`Subject` pre-populated. The applicant's email address is entered on the :guilabel:`Recipients` line, and the :guilabel:`Subject` is `Re: (Subject / Application Name)`. The email body is empty by default." msgstr "" -#: ../../content/applications/hr/recruitment.rst:193 +#: ../../content/applications/hr/recruitment.rst:192 msgid "To use a pre-configured email template, click the drop-down next to the :guilabel:`Load template` field in the lower right section of the window. Pre-configured email templates may contain dynamic placeholders so unique information can be populated in the email for a more personalized message to the applicant. There are several pre-configured email templates to choose from. Depending on the template selected, the email subject and/or body may change." msgstr "" -#: ../../content/applications/hr/recruitment.rst:200 +#: ../../content/applications/hr/recruitment.rst:199 msgid "Only the email templates that are configured for the model will load. There are other email templates pre-configured in Odoo, but if they are not configured for the recruitment application, they will not appear in the list of available templates." msgstr "" -#: ../../content/applications/hr/recruitment.rst:204 +#: ../../content/applications/hr/recruitment.rst:203 msgid "If any attachments are to be added, click the :guilabel:`Attach A File` button in the lower left corner. Navigate to the file to be attached, then click :guilabel:`Open` to attach it. To delete an attachment, click the :guilabel:`X (Delete)` icon to the right of the attachment. If any changes need to be made to the email, edit the body of the email. If the edits should be saved to be used in the future, the email can be saved as a new template. Click the :guilabel:`Save As New Template` button in the bottom right corner. To send the email, click :guilabel:`Send` and the email will be sent to the applicant. The email then appears in the chatter." msgstr "" -#: ../../content/applications/hr/recruitment.rst:213 +#: ../../content/applications/hr/recruitment.rst:212 msgid "Stage flow" msgstr "" -#: ../../content/applications/hr/recruitment.rst:215 +#: ../../content/applications/hr/recruitment.rst:214 msgid "In order to move an applicant's card from one stage to another, the applicant's card can either be dragged and dropped in the kanban view to the desired stage, or the stage can be modified on the applicant's card." msgstr "" -#: ../../content/applications/hr/recruitment.rst:219 +#: ../../content/applications/hr/recruitment.rst:218 msgid "To change the stage on the applicant's card, click on the applicant's card in the kanban view to go to a detailed view of the card. The current stage for the card is highlighted in purple at the top, above the card. Simply click the desired stage for the card, and the stage changes. A log note indicating the stage change appears in the chatter. Navigate back to the kanban view by clicking on :guilabel:`Applications` in the breadcrumb menu in the top left, and the applicant's card now appears in the new stage." msgstr "" @@ -5836,63 +6314,63 @@ msgid "Change the stage of an applicant by clicking on the desired stage at the "applicant's card." msgstr "" -#: ../../content/applications/hr/recruitment.rst:234 +#: ../../content/applications/hr/recruitment.rst:233 msgid "Initial qualification" msgstr "" -#: ../../content/applications/hr/recruitment.rst:237 +#: ../../content/applications/hr/recruitment.rst:236 msgid "The following information is based on Odoo's default recruitment pipeline flow. Be advised that if modifications are made to create a customized recruitment pipeline flow, it will vary from the following information." msgstr "" -#: ../../content/applications/hr/recruitment.rst:241 +#: ../../content/applications/hr/recruitment.rst:240 msgid "All applicants appear in the :guilabel:`Initial Qualification` stage, whether submitted online or if the applicant is manually entered by a recruiter. When the applicant's card is created, Odoo automatically populates the applicant's :guilabel:`Name`, :guilabel:`Email address`, and :guilabel:`Phone number` on the applicant's card. This information is required when applying for a job position." msgstr "" -#: ../../content/applications/hr/recruitment.rst:247 +#: ../../content/applications/hr/recruitment.rst:246 msgid "If the applicant entered any information in the :guilabel:`Short Introduction` section of the online application, it is populated in the :guilabel:`Application Summary` tab at the bottom of the applicant's card. If a resumé was attached to the online application, the resumé appears in the attachments section of the chatter, and is also stored in the *Documents* application. To find the recruitment documents stored in the Documents application, navigate to the main :menuselection:`Documents` dashboard, and click the folder labeled :guilabel:`Recruitment` on the right side. All recruitment documents will be stored within that folder." msgstr "" -#: ../../content/applications/hr/recruitment.rst:256 +#: ../../content/applications/hr/recruitment.rst:255 msgid "Send interview" msgstr "" -#: ../../content/applications/hr/recruitment.rst:258 +#: ../../content/applications/hr/recruitment.rst:257 msgid "At any point in the hiring process, an *interview* can be sent to the applicant to obtain more information. These interviews are custom-made, and can be formatted in a variety of ways." msgstr "" -#: ../../content/applications/hr/recruitment.rst:261 +#: ../../content/applications/hr/recruitment.rst:260 msgid "Odoo uses the term *interview*, but these can be thought of as questionnaires, surveys, tests, certifications, etc. Custom interviews can be formatted to suit each individual job position's needs. For example, a job position for a computer programmer could have an interview in the form of a programming quiz to determine the skill level of the applicant. A job position for a restaurant server could have a questionnaire inquiring about the applicant's availability, if the desired applicant needs to be available on weekend evenings. For more information on creating and editing interview forms, refer to the :doc:`../hr/recruitment/new_job` documentation." msgstr "" -#: ../../content/applications/hr/recruitment.rst:270 +#: ../../content/applications/hr/recruitment.rst:269 msgid "In order to send an email to an applicant, there must be an email address on the applicant's card. If an email address is not entered on the applicant's card, when :guilabel:`Send Interview` is clicked, the applicant's card appears instead of the :guilabel:`Survey` pop-up window. Enter the email address in the email field, then click :guilabel:`Save`. Once the applicant's card is saved, the applicant's card closes and the :guilabel:`Survey` pop-up window appears." msgstr "" -#: ../../content/applications/hr/recruitment.rst:276 +#: ../../content/applications/hr/recruitment.rst:275 msgid "To send an interview to an applicant, click on an applicant's card to navigate to a detailed view of the applicant's card. At the top of the applicant's card, click the button labeled :guilabel:`Send Interview`." msgstr "" -#: ../../content/applications/hr/recruitment.rst:280 +#: ../../content/applications/hr/recruitment.rst:279 msgid "If the applicant's card has an email address on file, a :guilabel:`Survey` pop-up window appears, with all the information populated. If an email is not on the applicant's card, then a contact form appears. Enter the applicants email address, then click :guilabel:`Save`. The card closes and the :guilabel:`Survey` pop-up window appears." msgstr "" -#: ../../content/applications/hr/recruitment.rst:285 +#: ../../content/applications/hr/recruitment.rst:284 msgid "Odoo refers to the interview forms as *surveys*. These email templates also use dynamic placeholders to personalize the email to the applicant and the job position. Add any additional recipients for the survey if more people should receive the email. If an email is in the database as a contact, add that contact on the :guilabel:`Recipients` line. If an email should be sent to someone who is not in the database as a contact, and they should **not** be added as a contact, add their email to the :guilabel:`Additional emails` line." msgstr "" -#: ../../content/applications/hr/recruitment.rst:292 +#: ../../content/applications/hr/recruitment.rst:291 msgid "If any attachments need to be added, click the :guilabel:`Attachments` button and a file explorer window appears. Navigate to the desired file, then click :guilabel:`Open` to attach it to the email. The attachment loads, and is listed above the :guilabel:`Attachments` button." msgstr "" -#: ../../content/applications/hr/recruitment.rst:296 +#: ../../content/applications/hr/recruitment.rst:295 msgid "If the emailed interview must be completed by a specific date, select a date for the :guilabel:`Answer deadline` in the lower-right area of the pop-up window. Click on the line next to :guilabel:`Answer deadline`, and a calendar selector appears. Use the :guilabel:`< (left)` and :guilabel:`> (right)` arrows on either side of the month to navigate to the desired month, then click on the :guilabel:`day` to select the date." msgstr "" -#: ../../content/applications/hr/recruitment.rst:302 +#: ../../content/applications/hr/recruitment.rst:301 msgid "The :guilabel:`Mail template` field is pre-populated based on the configuration for the interview. A different template can be chosen from the drop-down menu if desired. If a new template is selected, the new email template loads in the email body." msgstr "" -#: ../../content/applications/hr/recruitment.rst:306 +#: ../../content/applications/hr/recruitment.rst:305 msgid "To send the email with the interview link to the applicant, click :guilabel:`Send` at the bottom of the email pop-up." msgstr "" @@ -5901,27 +6379,27 @@ msgid "Send a custom survey, also referred to as an interview form, to an applic "pre-configured template." msgstr "" -#: ../../content/applications/hr/recruitment.rst:315 +#: ../../content/applications/hr/recruitment.rst:314 msgid "Refuse" msgstr "" -#: ../../content/applications/hr/recruitment.rst:317 +#: ../../content/applications/hr/recruitment.rst:316 msgid "At any point in the recruitment pipeline, an applicant can be refused from the job application process. To refuse an applicant, click on an applicant's card to navigate to a detailed view of the applicant's card. At the top of the applicant's card, there are several buttons. Click the one labeled :guilabel:`Refuse`." msgstr "" -#: ../../content/applications/hr/recruitment.rst:322 +#: ../../content/applications/hr/recruitment.rst:321 msgid "A :guilabel:`Refuse Reason` pop-up appears. Select the :guilabel:`Refuse Reason` from the drop-down menu. The default refuse reasons in Odoo are: :guilabel:`Doesn't fit the job requirements`, :guilabel:`The applicant is not interested anymore`, and :guilabel:`The applicant gets a better offer`. These three refusal reasons have pre-configured email templates associated with them. Additional refusal reasons can be created and existing ones can be modified or deleted. To add a new refusal reason, type in the name of the reason, then click :guilabel:`Create and Edit...`. A :guilabel:`Create: Refuse Reason` pop-up window appears. Type in the name of the new email template in the :guilabel:`Email Template` field, and click :guilabel:`Create and Edit...`. A :guilabel:`Create: Email Template` window loads. Configure the new email template, then click :guilabel:`Save`." msgstr "" -#: ../../content/applications/hr/recruitment.rst:334 -msgid "Pre-configured email templates in Odoo sometimes use dynamic placeholders, which are customized pieces of data that populate dynamic content. For example, if the applicant's name is a piece of dynamic content, the applicant's name will appear anytime that dynamic placeholder appears on the email template. For more detailed information on email templates, refer to the :doc:`../general/email_communication/email_template` documentation." +#: ../../content/applications/hr/recruitment.rst:333 +msgid "Pre-configured email templates in Odoo sometimes use dynamic placeholders, which are customized pieces of data that populate dynamic content. For example, if the applicant's name is a piece of dynamic content, the applicant's name will appear anytime that dynamic placeholder appears on the email template. For more detailed information on email templates, refer to the :doc:`../general/companies/email_template` documentation." msgstr "" -#: ../../content/applications/hr/recruitment.rst:340 +#: ../../content/applications/hr/recruitment.rst:339 msgid "An email template populates the :guilabel:`Email Template` field after a refusal reason is selected. If an email should not be sent to the applicant, uncheck the :guilabel:`Send Email` checkbox. To view the email template, click the :guilabel:`External Link` icon to the right of the email template selected. The email template loads in the pop-up window, and can be modified if needed. After making modifications, click :guilabel:`Save`. To close the email template, click :guilabel:`Discard`." msgstr "" -#: ../../content/applications/hr/recruitment.rst:346 +#: ../../content/applications/hr/recruitment.rst:345 msgid "To send the refusal email to the applicant, click :guilabel:`Send`. The refusal email is sent to the applicant, and a :guilabel:`Refused` banner appears on the applicant's card." msgstr "" @@ -5929,23 +6407,23 @@ msgstr "" msgid "An applicant's card with the refused banner appearing in the top right corner in red." msgstr "" -#: ../../content/applications/hr/recruitment.rst:353 +#: ../../content/applications/hr/recruitment.rst:352 msgid "After refusal, the applicant's card is no longer visible in the job position's kanban view. To view refused applicants, navigate to the :menuselection:`Recruitment app --> Applications --> All Applications`. All applications for all job positions are presented in a list view. To view the refused applicants only, click :guilabel:`Filters`, then click :guilabel:`Archived/Refused`. All applicants that have been archived and/or refused appear in the list. To further organize this list and view refusals by job position, click :guilabel:`≣ Group By`, then click :guilabel:`Job`." msgstr "" -#: ../../content/applications/hr/recruitment.rst:361 +#: ../../content/applications/hr/recruitment.rst:360 msgid "New applicant" msgstr "" -#: ../../content/applications/hr/recruitment.rst:363 +#: ../../content/applications/hr/recruitment.rst:362 msgid "An applicant card can be manually added if needed. If an applicant needs to be added to the list of prospective candidates and an applicant card has not been created yet (they have not applied for the job online yet) an applicant card can be easily added from the job position kanban view in one of two ways, using either the :ref:`Quick add ` icon or the :ref:`Create ` button." msgstr "" -#: ../../content/applications/hr/recruitment.rst:372 +#: ../../content/applications/hr/recruitment.rst:371 msgid "Quick add" msgstr "" -#: ../../content/applications/hr/recruitment.rst:374 +#: ../../content/applications/hr/recruitment.rst:373 msgid "Quickly add a new applicant using the :guilabel:`Quick add` icon. If not already in the job position kanban view, navigate to the main recruitment dashboard, and click the :guilabel:`New Applicants` button on the job position card that the applicant should be added to. Then, click on the small :guilabel:`+ (plus sign) Quick add` icon in the top right of the :guilabel:`Initial Qualification` stage to quickly add a new applicant." msgstr "" @@ -5953,141 +6431,141 @@ msgstr "" msgid "All the fields for a new applicant form entered when using the Quick Add option." msgstr "" -#: ../../content/applications/hr/recruitment.rst:384 +#: ../../content/applications/hr/recruitment.rst:383 msgid "Enter the following information on the card:" msgstr "" -#: ../../content/applications/hr/recruitment.rst:386 +#: ../../content/applications/hr/recruitment.rst:385 msgid ":guilabel:`Subject/Application Name`: this is the only required field. Enter the title for the card. Typically this is the applicant's name and job position being applied to, for example: `Laura Smith - Experienced Developer`. This field is not visible in the kanban view (unless in the Developer mode), but is visible on the individual card." msgstr "" +#: ../../content/applications/hr/recruitment.rst:389 +#: ../../content/applications/hr/recruitment.rst:434 +msgid ":guilabel:`Applicant's Name`: enter the applicant's name." +msgstr "" + #: ../../content/applications/hr/recruitment.rst:390 #: ../../content/applications/hr/recruitment.rst:435 -msgid ":guilabel:`Applicant's Name`: enter the applicant's name." -msgstr "" - -#: ../../content/applications/hr/recruitment.rst:391 -#: ../../content/applications/hr/recruitment.rst:436 msgid ":guilabel:`Email`: enter the applicant's email address." msgstr "" -#: ../../content/applications/hr/recruitment.rst:392 +#: ../../content/applications/hr/recruitment.rst:391 msgid ":guilabel:`Applied Job`: the current job position populates this field. If needed, the job position can be changed by selecting a different position from the drop-down menu. If a different job position is selected, after the card is created, the card will appear in the selected job position." msgstr "" -#: ../../content/applications/hr/recruitment.rst:397 +#: ../../content/applications/hr/recruitment.rst:396 msgid "After the information is entered, click :guilabel:`Add`. The applicant appears in the list, and a new blank applicant card appears. Click either the :guilabel:`🗑️ (delete)` icon or click anywhere on the screen to close the card." msgstr "" -#: ../../content/applications/hr/recruitment.rst:401 +#: ../../content/applications/hr/recruitment.rst:400 msgid "If preferred, after entering the applicant name, click :guilabel:`Edit` and a detailed :guilabel:`Applicant Form` loads. :ref:`Enter the information on the form `, then click :guilabel:`Save`" msgstr "" -#: ../../content/applications/hr/recruitment.rst:408 +#: ../../content/applications/hr/recruitment.rst:407 msgid "Create" msgstr "" -#: ../../content/applications/hr/recruitment.rst:410 +#: ../../content/applications/hr/recruitment.rst:409 msgid "Add a new applicant including all the relevant information using the :guilabel:`Create` button. If not already in the kanban view for the job position to add an applicant to, navigate to the main recruitment dashboard, and click the :guilabel:`New Applicants` button on the job position card that the applicant should be added to. Then, click the :guilabel:`Create` button in the top left of the kanban view and an applicant form loads." msgstr "" -#: ../../content/applications/hr/recruitment.rst:416 +#: ../../content/applications/hr/recruitment.rst:415 msgid "Certain fields on the applicant card may be pre-populated, depending on how the job position is configured. Typically, the :guilabel:`Job` section, as well as the :guilabel:`Recruiter` field, are all pre-populated." msgstr "" -#: ../../content/applications/hr/recruitment.rst:420 +#: ../../content/applications/hr/recruitment.rst:419 msgid "Enter the following information on the new applicant form. Note that not all fields listed below may be visible. Depending on installed applications and configurations, some fields may not be displayed." msgstr "" -#: ../../content/applications/hr/recruitment.rst:427 +#: ../../content/applications/hr/recruitment.rst:426 msgid "Applicant section" msgstr "" -#: ../../content/applications/hr/recruitment.rst:429 +#: ../../content/applications/hr/recruitment.rst:428 msgid ":guilabel:`Subject/Application Name`: this is the only required field. Enter the title for the card. Typically this is the applicant's name and job position being applied to, for example: `Laura Smith - Experienced Developer`. This field is not visible in the kanban view, unless the :guilabel:`Applicant's Name` is left blank. If there is no :guilabel:`Applicant's Name`, then the :guilabel:`Subject/Application Name` is what is displayed on the applicant card in the kanban view." msgstr "" -#: ../../content/applications/hr/recruitment.rst:437 +#: ../../content/applications/hr/recruitment.rst:436 msgid ":guilabel:`Phone`: enter the applicant's phone number." msgstr "" -#: ../../content/applications/hr/recruitment.rst:438 +#: ../../content/applications/hr/recruitment.rst:437 msgid ":guilabel:`Mobile`: enter the applicant's mobile number." msgstr "" -#: ../../content/applications/hr/recruitment.rst:439 +#: ../../content/applications/hr/recruitment.rst:438 msgid ":guilabel:`Degree`: select the applicant's highest level of education earned from the drop-down menu. Options are :guilabel:`Graduate`, :guilabel:`Bachelor Degree`, :guilabel:`Master Degree`, or :guilabel:`Doctoral Degree`. The :guilabel:`Graduate` option indicates graduating the highest level of school before a Bachelor's degree, such as a high school or secondary school diploma, depending on the country." msgstr "" -#: ../../content/applications/hr/recruitment.rst:444 +#: ../../content/applications/hr/recruitment.rst:443 msgid ":guilabel:`Tags`: select as many tags as desired from the drop-down menu. To add a tag that does not exist, type in the tag name, the click :guilabel:`Create \"new tag\"`." msgstr "" -#: ../../content/applications/hr/recruitment.rst:446 +#: ../../content/applications/hr/recruitment.rst:445 msgid ":guilabel:`Interviewer`: select the person who will be conducting the interview(s) from the drop-down menu. The person must have either *recruiter* or *officer* rights configured for the Recruitment application in order to appear on the drop-down." msgstr "" -#: ../../content/applications/hr/recruitment.rst:449 +#: ../../content/applications/hr/recruitment.rst:448 msgid ":guilabel:`Recruiter`: select the person responsible for the entire recruitment process for the job position. Only *users* can be selected, and all users are presented in the drop-down to select from." msgstr "" -#: ../../content/applications/hr/recruitment.rst:452 +#: ../../content/applications/hr/recruitment.rst:451 msgid ":guilabel:`Appreciation`: click on one of the stars to select a rating for the applicant. One star indicates :guilabel:`Good`, two stars indicates :guilabel:`Very Good`, and three stars indicates :guilabel:`Excellent.`" msgstr "" -#: ../../content/applications/hr/recruitment.rst:455 +#: ../../content/applications/hr/recruitment.rst:454 msgid ":guilabel:`Referred By User`: if referral points are to be earned for this job position in the *Referrals* application, select the user who referred the applicant from the drop-down menu. The *Referrals* application must be installed for this to appear." msgstr "" -#: ../../content/applications/hr/recruitment.rst:460 +#: ../../content/applications/hr/recruitment.rst:459 msgid "Job section" msgstr "" -#: ../../content/applications/hr/recruitment.rst:462 +#: ../../content/applications/hr/recruitment.rst:461 msgid "The following fields are pre-populated when creating a new applicant, as long as these field are specified on the Job Position. Editing the fields is possible, if desired." msgstr "" -#: ../../content/applications/hr/recruitment.rst:465 +#: ../../content/applications/hr/recruitment.rst:464 msgid ":guilabel:`Applied Job`: select the job position the applicant is applying to from the drop-down menu." msgstr "" -#: ../../content/applications/hr/recruitment.rst:467 +#: ../../content/applications/hr/recruitment.rst:466 msgid ":guilabel:`Department`: select the department the job position falls under from the drop-down menu." msgstr "" -#: ../../content/applications/hr/recruitment.rst:469 +#: ../../content/applications/hr/recruitment.rst:468 msgid ":guilabel:`Company`: select the company the job positions is for using the drop-down menu." msgstr "" -#: ../../content/applications/hr/recruitment.rst:472 +#: ../../content/applications/hr/recruitment.rst:471 msgid "Contract section" msgstr "" -#: ../../content/applications/hr/recruitment.rst:474 +#: ../../content/applications/hr/recruitment.rst:473 msgid ":guilabel:`Expected Salary`: enter the amount the applicant is requesting for the role in this field. The number should be in a `XX,XXX.XX` format. The currency is determined by the localization setting for the company." msgstr "" -#: ../../content/applications/hr/recruitment.rst:477 +#: ../../content/applications/hr/recruitment.rst:476 msgid ":guilabel:`Expected Salary - Extra advantages...`: if any extra advantages are requested by the applicant, enter it in this field. This should be short and descriptive, such as `1 week extra vacation` or `dental plan`." msgstr "" -#: ../../content/applications/hr/recruitment.rst:480 +#: ../../content/applications/hr/recruitment.rst:479 msgid ":guilabel:`Proposed Salary`: enter the amount to be offered to the applicant for the role in this field. The number should be in a `XX,XXX.XX` format." msgstr "" -#: ../../content/applications/hr/recruitment.rst:482 +#: ../../content/applications/hr/recruitment.rst:481 msgid ":guilabel:`Proposed Salary - Extra advantages...`: if any extra advantages are offered to the applicant, enter it in this field. This should be short and descriptive, such as `1 week extra vacation` or `dental plan`." msgstr "" -#: ../../content/applications/hr/recruitment.rst:485 +#: ../../content/applications/hr/recruitment.rst:484 msgid ":guilabel:`Availability`: using the calendar module in the drop-down menu, select the available start date for the applicant." msgstr "" -#: ../../content/applications/hr/recruitment.rst:489 +#: ../../content/applications/hr/recruitment.rst:488 msgid "Application summary tab" msgstr "" -#: ../../content/applications/hr/recruitment.rst:491 +#: ../../content/applications/hr/recruitment.rst:490 msgid "Any additional details or notes that should be added to the applicant's card can be typed into this field." msgstr "" @@ -6095,11 +6573,11 @@ msgstr "" msgid "All the fields for a new applicant form entered." msgstr "" -#: ../../content/applications/hr/recruitment.rst:501 +#: ../../content/applications/hr/recruitment.rst:500 msgid "First interview" msgstr "" -#: ../../content/applications/hr/recruitment.rst:503 +#: ../../content/applications/hr/recruitment.rst:502 msgid "After an applicant has passed the :guilabel:`Initial Qualification` stage, they can be moved to the :guilabel:`First Interview` stage in the job position kanban view. To move the applicant to the next stage, drag and drop the applicant's card to the :guilabel:`First Interview` stage, or click on the :guilabel:`First Interview` stage button at the top of the individual applicant's card." msgstr "" @@ -6107,27 +6585,27 @@ msgstr "" msgid "An applicant's card moves from one stage t another by using the click and drag method." msgstr "" -#: ../../content/applications/hr/recruitment.rst:512 +#: ../../content/applications/hr/recruitment.rst:511 msgid "When the applicant's card moves to the :guilabel:`First Interview` stage, an acknowledgement email is automatically sent to the applicant. The email is created using an email template titled :guilabel:`Applicant: Acknowledgement`. This email template is pre-configured in Odoo, and contains dynamic placeholders for the job position, the recruiter's name, and the company's information. Once the email is sent, the email appears in the chatter." msgstr "" -#: ../../content/applications/hr/recruitment.rst:523 +#: ../../content/applications/hr/recruitment.rst:522 msgid "When a date and time have been agreed upon for both the applicant and interviewer, the interview can be scheduled. To schedule an interview, whether a phone or in-person interview, click the :guilabel:`Meeting` smart button at the top of the applicant's record." msgstr "" -#: ../../content/applications/hr/recruitment.rst:527 +#: ../../content/applications/hr/recruitment.rst:526 msgid "The applicant's card can be found by navigating to the :menuselection:`Recruitment application` dashboard, click on a :guilabel:`New Applications` button in the job position card, then click on the applicant's card." msgstr "" -#: ../../content/applications/hr/recruitment.rst:532 +#: ../../content/applications/hr/recruitment.rst:531 msgid "The meeting smart button will display :guilabel:`No Meeting` if no meetings are currently scheduled. For new applicants who are new to the :guilabel:`First Interview` stage, this will be the default. If there are any meetings already scheduled, the smart button will display :guilabel:`Next Meeting` with the date of the upcoming meeting." msgstr "" -#: ../../content/applications/hr/recruitment.rst:537 +#: ../../content/applications/hr/recruitment.rst:536 msgid "Doing so loads the *Calendar* application, showing the currently scheduled meetings and events for the user. The meetings and events displayed are for the employees who are listed under the :guilabel:`Attendees` section on the right side of the calendar view. To change the currently loaded meetings and events being displayed, uncheck the person who's calendar events are to be hidden. Only the checked attendees will be visible on the calendar." msgstr "" -#: ../../content/applications/hr/recruitment.rst:543 +#: ../../content/applications/hr/recruitment.rst:542 msgid "The default view is the week view. To change the calendar view, click on a button to present the calendar in a different view, either :guilabel:`Day`, :guilabel:`Month`, or :guilabel:`Year`. To change the displayed date range for the calendar, either use the :guilabel:`⬅️ (Left)`, :guilabel:`➡️ (Right)`, or :guilabel:`Today` buttons above the calendar, or click on a date in the calendar on the right side of the displayed calendar." msgstr "" @@ -6135,83 +6613,83 @@ msgstr "" msgid "The calendar view, highlighting how to change the displayed meetings." msgstr "" -#: ../../content/applications/hr/recruitment.rst:553 +#: ../../content/applications/hr/recruitment.rst:552 msgid "To add a meeting to the calendar, click on the day the meeting is to take place, or click on the start time of the meeting and drag to the end time, to select the date, time, and the length of the meeting. If the calendar is displaying the day or week view, click on the day *and* the time slot the meeting is to take place. A :guilabel:`New Event` pop up appears, with the :guilabel:`Meeting Subject` populated with the applicant card's :guilabel:`Subject/Application Name`. The default time slot is 30 minutes. If the information is correct, click :guilabel:`Create` to add the meeting to the calendar, or click :guilabel:`Edit` to modify the meeting." msgstr "" -#: ../../content/applications/hr/recruitment.rst:561 +#: ../../content/applications/hr/recruitment.rst:560 msgid "If :guilabel:`Edit` is clicked, an expanded :guilabel:`New Event` card loads. Make any changes needed to the form." msgstr "" -#: ../../content/applications/hr/recruitment.rst:565 +#: ../../content/applications/hr/recruitment.rst:564 msgid "New event card" msgstr "" -#: ../../content/applications/hr/recruitment.rst:567 +#: ../../content/applications/hr/recruitment.rst:566 msgid "The fields available to populate or modify on the detailed :guilabel:`New Event` card are as follows. The only required fields to enter are the :guilabel:`Meeting Subject`, :guilabel:`Starting At`, and :guilabel:`Ending At` fields. Once the card details are entered, click :guilabel:`Save` to save the changes and create the meeting." msgstr "" -#: ../../content/applications/hr/recruitment.rst:572 +#: ../../content/applications/hr/recruitment.rst:571 msgid ":guilabel:`Meeting Subject`: enter the subject for the meeting. This should clearly indicate the purpose of the meeting. The default subject is the :guilabel:`Subject/Application Name` on the applicant's card." msgstr "" -#: ../../content/applications/hr/recruitment.rst:575 +#: ../../content/applications/hr/recruitment.rst:574 msgid ":guilabel:`Attendees`: select the people who should be in attendance. The default employee listed is the person who is creating the meeting. Add as many other people as desired." msgstr "" -#: ../../content/applications/hr/recruitment.rst:579 +#: ../../content/applications/hr/recruitment.rst:578 msgid "Meeting details tab" msgstr "" -#: ../../content/applications/hr/recruitment.rst:581 +#: ../../content/applications/hr/recruitment.rst:580 msgid ":guilabel:`Starting At`: using the drop-down calendar, select the date and time for the meeting start time." msgstr "" -#: ../../content/applications/hr/recruitment.rst:583 +#: ../../content/applications/hr/recruitment.rst:582 msgid ":guilabel:`Ending At`: using the drop-down calendar, select the date and time for the meeting end time." msgstr "" -#: ../../content/applications/hr/recruitment.rst:585 +#: ../../content/applications/hr/recruitment.rst:584 msgid ":guilabel:`Duration`: this field auto populates based on the :guilabel:`Starting At` and :guilabel:`Ending At` times entered. If the meeting time is adjusted, this field automatically adjusts to the correct duration length." msgstr "" -#: ../../content/applications/hr/recruitment.rst:588 +#: ../../content/applications/hr/recruitment.rst:587 msgid ":guilabel:`All Day`: if the meeting is an all day long event, check the box next to :guilabel:`All Day`. After this box is checked, the :guilabel:`Duration` field is hidden from view, a well as the meeting start and end times." msgstr "" -#: ../../content/applications/hr/recruitment.rst:591 +#: ../../content/applications/hr/recruitment.rst:590 msgid ":guilabel:`Organizer`: the employee who created the meeting is populated in this field. Use the drop-down menu to change the selected employee." msgstr "" -#: ../../content/applications/hr/recruitment.rst:593 +#: ../../content/applications/hr/recruitment.rst:592 msgid ":guilabel:`Description`: enter a brief description in this field. There is an option to enter formatted text, such as numbered lists, headings, tables, as well as links, photos, and more. Use the powerbox feature, by typing a `/`, and a list of options are presented. Scroll through the options and click on the desired item. The item appears in the field and can be modified. Each command presents a different pop-up window. Follow the instructions for each command to complete the entry." msgstr "" -#: ../../content/applications/hr/recruitment.rst:599 +#: ../../content/applications/hr/recruitment.rst:598 msgid ":guilabel:`Reminders`: select a reminder from the drop-down menu. Options include :guilabel:`Notification`, :guilabel:`Email`, and :guilabel:`SMS Text Message`, each with a specific time period before the event (hours, days, etc). The reminder chosen will alert the meeting participants of the meeting via the selected option." msgstr "" -#: ../../content/applications/hr/recruitment.rst:603 +#: ../../content/applications/hr/recruitment.rst:602 msgid ":guilabel:`Location`: enter the location for the meeting." msgstr "" -#: ../../content/applications/hr/recruitment.rst:604 +#: ../../content/applications/hr/recruitment.rst:603 msgid ":guilabel:`Meeting URL`: if the meeting is virtual, enter the meeting link in this field." msgstr "" -#: ../../content/applications/hr/recruitment.rst:605 +#: ../../content/applications/hr/recruitment.rst:604 msgid ":guilabel:`Tags`: select any tag(s) for the meeting using the drop-down menu. There is no limit to the number of tags that can be used." msgstr "" -#: ../../content/applications/hr/recruitment.rst:611 +#: ../../content/applications/hr/recruitment.rst:610 msgid ":guilabel:`Recurrent`: if the meeting should repeat at a selected interval (not typical for a first interview), check the box next to :guilabel:`Recurrent`. This reveals a recurrence section. Enter the details for how often the meeting should repeat, including an end time." msgstr "" -#: ../../content/applications/hr/recruitment.rst:614 +#: ../../content/applications/hr/recruitment.rst:613 msgid ":guilabel:`Privacy`: select the visibility of this meeting. Options are :guilabel:`Public`, :guilabel:`Private`, and :guilabel:`Only internal users`. :guilabel:`Public` allows for everyone to see the meeting, :guilabel:`Private` allows only the attendees listed on the meeting to see the meeting, and :guilabel:`Only internal users` allows anyone logged into the company database to see the meeting." msgstr "" -#: ../../content/applications/hr/recruitment.rst:619 +#: ../../content/applications/hr/recruitment.rst:618 msgid ":guilabel:`Show as`: select from the drop-down whether the meeting time should appear as :guilabel:`Busy` or :guilabel:`Available` in the attendees' schedules. Setting this field to :guilabel:`Available` allows other meetings to be scheduled for the same time. It is recommended to set this field to :guilabel:`Busy`, so no other meetings can be scheduled for the attendees at the same time." msgstr "" @@ -6219,15 +6697,15 @@ msgstr "" msgid "A new meeting card with all the details populated, and ready to save." msgstr "" -#: ../../content/applications/hr/recruitment.rst:630 +#: ../../content/applications/hr/recruitment.rst:629 msgid "Send meeting to attendees" msgstr "" -#: ../../content/applications/hr/recruitment.rst:632 +#: ../../content/applications/hr/recruitment.rst:631 msgid "Once changes have been entered and the meeting details are correct, the meeting can be sent to the attendees via email or text message." msgstr "" -#: ../../content/applications/hr/recruitment.rst:635 +#: ../../content/applications/hr/recruitment.rst:634 msgid "To send the meeting via email, click the :guilabel:`Email` button next to the list of attendees. A :guilabel:`Contact Attendees` email configurator pop-up appears. A pre-formatted email using the default :guilabel:`Calendar: Event Update` email template populates the email body field. The followers of the document (job application), as well as the user who created the meeting are added as :guilabel:`Recipients` by default. Add the applicant's email address to the list to send the email to the applicant as well. Make any other desired changes to the email. If an attachment is needed, click the :guilabel:`Attach A File` button, navigate to the file, then click :guilabel:`Open`. Once the email is ready to be sent, click :guilabel:`Send`." msgstr "" @@ -6235,15 +6713,15 @@ msgstr "" msgid "Enter the information to send the event via email." msgstr "" -#: ../../content/applications/hr/recruitment.rst:648 +#: ../../content/applications/hr/recruitment.rst:647 msgid "To send the meeting via text message, click the :guilabel:`SMS` button next to the list of attendees. A :guilabel:`Send SMS Text Message` pop-up appears. At the top, in a blue box, information appears regarding the message. The first line lists how many records (phone numbers) are selected. The second line lists the number of recipients and how many of them are invalid. If a contact does not have a valid phone number listed, click :guilabel:`Close`, and edit the attendee's record, then redo these steps." msgstr "" -#: ../../content/applications/hr/recruitment.rst:656 +#: ../../content/applications/hr/recruitment.rst:655 msgid "It is *not* recommended to check the box to send to all the records in the :guilabel:`Send SMS Text Message` pop-up. This would send a message to all contacts with a valid phone number." msgstr "" -#: ../../content/applications/hr/recruitment.rst:659 +#: ../../content/applications/hr/recruitment.rst:658 msgid "When the message reads :guilabel:`0 are invalid`, type in the message to be sent in the :guilabel:`Message` field. Beneath the message field, the number of characters, as well as the amount of text messages required to send the message (according to GSM7 criteria) appears. Click :guilabel:`Put In Queue` to have the text sent later, after any other messages are scheduled, or click :guilabel:`Send Now` to send the message immediately." msgstr "" @@ -6251,95 +6729,95 @@ msgstr "" msgid "Send a text message to the attendees of the meeting." msgstr "" -#: ../../content/applications/hr/recruitment.rst:670 -msgid "Sending text messages is not a default capability with Odoo. To send text messages, credits are required, which need to be purchased. For more information on IAP credits and plans, refer to the :doc:`../general/in_app_purchase` documentation." +#: ../../content/applications/hr/recruitment.rst:669 +msgid "Sending text messages is not a default capability with Odoo. To send text messages, credits are required, which need to be purchased. For more information on IAP credits and plans, refer to the :doc:`../essentials/in_app_purchase` documentation." msgstr "" -#: ../../content/applications/hr/recruitment.rst:677 +#: ../../content/applications/hr/recruitment.rst:676 msgid "Second interview" msgstr "" -#: ../../content/applications/hr/recruitment.rst:679 +#: ../../content/applications/hr/recruitment.rst:678 msgid "After an applicant has passed the :guilabel:`First Interview` stage, they can be moved to the :guilabel:`Second Interview` stage. To move the applicant to the next stage, drag and drop the applicant's card to the :guilabel:`Second Interview` stage, or click on the :guilabel:`Second Interview` stage button at the top of the individual applicant's card." msgstr "" -#: ../../content/applications/hr/recruitment.rst:684 +#: ../../content/applications/hr/recruitment.rst:683 msgid "When the applicant's card moves to the :guilabel:`Second Interview` stage, there are no automatic activities or emails configured for this stage, unlike for the :guilabel:`First Interview` stage. The recruiter can now :ref:`schedule a second interview ` with the applicant, following the same process as for the first interview." msgstr "" -#: ../../content/applications/hr/recruitment.rst:692 +#: ../../content/applications/hr/recruitment.rst:691 msgid "Contract proposal" msgstr "" -#: ../../content/applications/hr/recruitment.rst:694 +#: ../../content/applications/hr/recruitment.rst:693 msgid "When the applicant has passed the interview stages and an offer is ready to be sent, they can be moved to the :guilabel:`Contract Proposal` stage. Drag and drop the applicant's card to the :guilabel:`Contract Proposal` stage, or click on the :guilabel:`Contract Proposal` stage button at the top right of the individual applicant's card." msgstr "" -#: ../../content/applications/hr/recruitment.rst:699 +#: ../../content/applications/hr/recruitment.rst:698 msgid "The next step is to send an offer to the applicant. On the applicant's card, click the :guilabel:`Generate Offer` button. A :guilabel:`Generate a Simulation Link` pop-up appears. All fields are pre-populated with information from the job position, except for the :guilabel:`Force New Cars List`, :guilabel:`Default Vehicle`, and the :guilabel:`Canteen Cost` (this is set to `0.00`)." msgstr "" -#: ../../content/applications/hr/recruitment.rst:706 +#: ../../content/applications/hr/recruitment.rst:705 msgid "Not all fields may appear on the :guilabel:`Generate a Simulation Link` pop-up. Depending on the localization setting for the company and the applications installed, some fields may not appear. For example if the *Fleet* application is not installed, the fields related to vehicles will not appear on the pop-up." msgstr "" -#: ../../content/applications/hr/recruitment.rst:712 +#: ../../content/applications/hr/recruitment.rst:711 msgid "Universal fields" msgstr "" -#: ../../content/applications/hr/recruitment.rst:714 +#: ../../content/applications/hr/recruitment.rst:713 msgid "The following fields appear for all offers sent to applicants regardless of localization settings." msgstr "" -#: ../../content/applications/hr/recruitment.rst:716 +#: ../../content/applications/hr/recruitment.rst:715 msgid ":guilabel:`Offer Template`: the template currently being used to populate the :guilabel:`Generate a Simulation Link` pop-up. To modify the template, click the :guilabel:`External link` icon to the right of the drop-down arrow. Make any changes, then click :guilabel:`Save`." msgstr "" -#: ../../content/applications/hr/recruitment.rst:719 +#: ../../content/applications/hr/recruitment.rst:718 msgid ":guilabel:`Job Title`: the name of the position being offered to the applicant." msgstr "" -#: ../../content/applications/hr/recruitment.rst:720 +#: ../../content/applications/hr/recruitment.rst:719 msgid ":guilabel:`Contract Start Date`: the date the contract takes effect. The default date is the current date. To modify the date, click the drop-down to reveal a calendar. Use the :guilabel:`< (left)` and :guilabel:`> (right)` arrows on either side of the month to navigate to the desired month, then click on the :guilabel:`day` to select the date." msgstr "" -#: ../../content/applications/hr/recruitment.rst:724 +#: ../../content/applications/hr/recruitment.rst:723 msgid ":guilabel:`Yearly Cost`: the annual salary being offered." msgstr "" -#: ../../content/applications/hr/recruitment.rst:725 +#: ../../content/applications/hr/recruitment.rst:724 msgid ":guilabel:`Offer Link`: this link takes the applicant to a webpage where they can enter their personal information, which will be imported to their employee record when created. If applicable, the applicant can modify their salary package (this option is not available for all localizations). Lastly, this is where the applicant accepts the offer by clicking :guilabel:`Review Contract & Sign` to accept the contract and sign it using the *Sign* application." msgstr "" -#: ../../content/applications/hr/recruitment.rst:733 +#: ../../content/applications/hr/recruitment.rst:732 msgid "The *Sign* application must be installed in order for a document to be signed. Ensure the *Sign* application is installed to use this feature." msgstr "" -#: ../../content/applications/hr/recruitment.rst:739 +#: ../../content/applications/hr/recruitment.rst:738 msgid "The following fields will only appear if specific localization settings are selected, and/or certain applications are installed. For example if the *Fleet* application is not installed, none of the optional fields related to vehicles will appear, such as :guilabel:`Force New Cars List` or :guilabel:`Default Vehicle`." msgstr "" -#: ../../content/applications/hr/recruitment.rst:744 +#: ../../content/applications/hr/recruitment.rst:743 msgid ":guilabel:`Job Position`: the official title of the job being offered to the applicant, from the :guilabel:`Job Position` card. To modify the name, click the :guilabel:`External link` icon to the right of the drop-down arrow. Make any changes, then click :guilabel:`Save`." msgstr "" -#: ../../content/applications/hr/recruitment.rst:747 +#: ../../content/applications/hr/recruitment.rst:746 msgid ":guilabel:`Department`: the department the job position falls under. To modify the department, click the :guilabel:`External link` icon to the right of the drop-down arrow. Make any changes, then click :guilabel:`Save`." msgstr "" -#: ../../content/applications/hr/recruitment.rst:750 +#: ../../content/applications/hr/recruitment.rst:749 msgid ":guilabel:`Force New Cars List`: check this box to offer a new vehicle to the applicant." msgstr "" -#: ../../content/applications/hr/recruitment.rst:751 +#: ../../content/applications/hr/recruitment.rst:750 msgid ":guilabel:`Default Vehicle`: using the drop-down menu, select the vehicle that will be assigned to the applicant." msgstr "" -#: ../../content/applications/hr/recruitment.rst:753 +#: ../../content/applications/hr/recruitment.rst:752 msgid ":guilabel:`Canteen Cost`: enter the amount that is offered to the applicant for the cafeteria." msgstr "" -#: ../../content/applications/hr/recruitment.rst:754 +#: ../../content/applications/hr/recruitment.rst:753 msgid ":guilabel:`Contract Type`: using the drop-down menu, select the type of contract that is being offered." msgstr "" @@ -6347,19 +6825,19 @@ msgstr "" msgid "Format the offer to send to the applicant. Make any modifications before sending." msgstr "" -#: ../../content/applications/hr/recruitment.rst:762 +#: ../../content/applications/hr/recruitment.rst:761 msgid "Send offer" msgstr "" -#: ../../content/applications/hr/recruitment.rst:764 +#: ../../content/applications/hr/recruitment.rst:763 msgid "To send the offer to the applicant, click :guilabel:`Send`. If the applicant does not have an email address listed on their applicant card, the applicant form appears so their email can be configured. If there is already an email configured on the applicant's card, the email pop-up appears instead. If prompted with the applicant's card, enter the applicant's email address in the :guilabel:`Email` field, then click :guilabel:`Save`. The applicant form closes and the email pop-up appears." msgstr "" -#: ../../content/applications/hr/recruitment.rst:770 +#: ../../content/applications/hr/recruitment.rst:769 msgid "The :guilabel:`Applicant: Your Salary Package` email template is used, and the :guilabel:`Recipients`, :guilabel:`Subject`, and email body are pre-populated based on the email template. If any attachments need to be added, click the :guilabel:`Attachments` button and a file explorer window appears. Navigate to the desired file, then click :guilabel:`Open` to attach it to the email. The attachment loads, and is listed above the :guilabel:`Attachments` button. Once the email is ready to send, click :guilabel:`Send`." msgstr "" -#: ../../content/applications/hr/recruitment.rst:778 +#: ../../content/applications/hr/recruitment.rst:777 msgid "To send an offer, ensure the *Sign* application is installed. This is necessary so the offer can be sent to the applicant by the recruiter. The applicant does not need any software installed." msgstr "" @@ -6367,19 +6845,19 @@ msgstr "" msgid "Send an email to the applicant with a link to the offered salary." msgstr "" -#: ../../content/applications/hr/recruitment.rst:788 +#: ../../content/applications/hr/recruitment.rst:787 msgid "Contract signed" msgstr "" -#: ../../content/applications/hr/recruitment.rst:790 +#: ../../content/applications/hr/recruitment.rst:789 msgid "Once the applicant has accepted the offer and signed the contract, the next step is to move the applicant to the :guilabel:`Contract Signed` stage. To move the applicant to the next stage, drag and drop the applicant's card to the :guilabel:`Contract Signed` stage, or click the :guilabel:`More` button at the top of the applicant's card to reveal the :guilabel:`Contract Signed` stage button at the top of the individual applicant's card, and click :guilabel:`Contract Signed`." msgstr "" -#: ../../content/applications/hr/recruitment.rst:797 +#: ../../content/applications/hr/recruitment.rst:796 msgid "The :guilabel:`Contract Signed` stage is folded in the kanban view, but the card may still be dragged and dropped into that stage." msgstr "" -#: ../../content/applications/hr/recruitment.rst:800 +#: ../../content/applications/hr/recruitment.rst:799 msgid "Once the applicant's card moves to the :guilabel:`Contract Signed` stage, a green :guilabel:`Hired` banner appears in the top right of the applicant's card." msgstr "" @@ -6387,15 +6865,15 @@ msgstr "" msgid "Hired banner in the top right corner of applicant card." msgstr "" -#: ../../content/applications/hr/recruitment.rst:808 +#: ../../content/applications/hr/recruitment.rst:807 msgid "Create employee" msgstr "" -#: ../../content/applications/hr/recruitment.rst:810 +#: ../../content/applications/hr/recruitment.rst:809 msgid "Once the applicant has been hired, the next step is to create an employee record of them. On the applicant's card, click the :guilabel:`Create Employee` button in the top left. An employee form appears, and any information from the applicant's card that can be imported into the employee card appears in the form." msgstr "" -#: ../../content/applications/hr/recruitment.rst:815 +#: ../../content/applications/hr/recruitment.rst:814 msgid "Fill out the rest of the form. For detailed information on the fields, refer to the :doc:`employees/new_employee` documentation. When done, click :guilabel:`Save`. The employee record is now saved in the *Employees* app." msgstr "" @@ -6941,46 +7419,46 @@ msgid "The only configuration needed for the Referrals application after it is i msgstr "" #: ../../content/applications/hr/referrals.rst:16 -msgid "Any user with either :guilabel:`Referral User`, :guilabel:`Officer`, or :guilabel:`Administrator` rights for the Recruitment application has access to the Referrals application. Only user's with :guilabel:`Administrator` rights for the Recruitment application have access to the :ref:`reporting ` and configurations menus. For more information on users and access rights, refer to these documents: :doc:`../general/users/manage_users` and :doc:`../general/users/access_rights`." +msgid "Any user with either :guilabel:`Referral User`, :guilabel:`Officer`, or :guilabel:`Administrator` rights for the Recruitment application has access to the Referrals application. Only user's with :guilabel:`Administrator` rights for the Recruitment application have access to the :ref:`reporting ` and configurations menus. For more information on users and access rights, refer to these documents: :doc:`../general/users` and :doc:`../general/users/access_rights`." msgstr "" -#: ../../content/applications/hr/referrals.rst:24 +#: ../../content/applications/hr/referrals.rst:23 msgid "Onboarding" msgstr "" -#: ../../content/applications/hr/referrals.rst:26 +#: ../../content/applications/hr/referrals.rst:25 msgid "When opening the *Referrals* application for the first time, a pre-configured onboarding script appears. This is in the form of four slides, each explaining the different parts of the Referrals application. At the top of the dashboard, the following message is displayed throughout all the onboarding slides: :guilabel:`GATHER YOUR TEAM! Job Referral Program`. Behind this main message is an image, and beneath it some more explanatory text." msgstr "" -#: ../../content/applications/hr/referrals.rst:32 +#: ../../content/applications/hr/referrals.rst:31 msgid "Each of the onboarding slides has a corresponding image and message that is displayed. After reading each message, click the :guilabel:`Next` button to advance to the next slide." msgstr "" -#: ../../content/applications/hr/referrals.rst:35 +#: ../../content/applications/hr/referrals.rst:34 msgid "The text that appears on each slide is as follows:" msgstr "" -#: ../../content/applications/hr/referrals.rst:37 +#: ../../content/applications/hr/referrals.rst:36 msgid ":guilabel:`Oh no! Villains are lurking the city! Help us recruit a team of superheroes to save the day!`" msgstr "" -#: ../../content/applications/hr/referrals.rst:39 +#: ../../content/applications/hr/referrals.rst:38 msgid ":guilabel:`Browse through open job positions, promote them on social media, or refer friends.`" msgstr "" -#: ../../content/applications/hr/referrals.rst:40 +#: ../../content/applications/hr/referrals.rst:39 msgid ":guilabel:`Collect points and exchange them for awesome gifts in the shop.`" msgstr "" -#: ../../content/applications/hr/referrals.rst:41 +#: ../../content/applications/hr/referrals.rst:40 msgid ":guilabel:`Compete against your colleagues to build the best justice league!`" msgstr "" -#: ../../content/applications/hr/referrals.rst:44 +#: ../../content/applications/hr/referrals.rst:43 msgid "The onboarding slides will appear every time the Referrals application is opened, until all the slides have been viewed and the :guilabel:`Start Now` button has been clicked. If the onboarding is exited at any point, or if the :guilabel:`Start Now` button has *not* been clicked, the onboarding slides will begin again when the Referrals application is opened. Once the :guilabel:`Start Now` button has been clicked, the onboarding slides will not be seen again, and the main dashboard will load when the Referrals application is opened from that point on." msgstr "" -#: ../../content/applications/hr/referrals.rst:51 +#: ../../content/applications/hr/referrals.rst:50 msgid "At any point during onboarding, the :guilabel:`Skip` button may be clicked. This exits the onboarding, and the main Referrals dashboard loads. If :guilabel:`Skip` is clicked, onboarding slides will not load anymore when opening the Referrals application." msgstr "" @@ -6988,27 +7466,27 @@ msgstr "" msgid "An onboarding slide with the skip and next buttons visible at the bottom." msgstr "" -#: ../../content/applications/hr/referrals.rst:60 +#: ../../content/applications/hr/referrals.rst:59 msgid "If there are any candidates hired that the user had referred prior to opening the Referrals app (meaning the onboarding slides have not appeared before), when :guilabel:`Start Now` is clicked at the end of onboarding, instead of going to the main dashboard, a :ref:`hired ` screen appears instead." msgstr "" -#: ../../content/applications/hr/referrals.rst:66 +#: ../../content/applications/hr/referrals.rst:65 msgid "Modifying onboarding slides" msgstr "" -#: ../../content/applications/hr/referrals.rst:68 +#: ../../content/applications/hr/referrals.rst:67 msgid "Onboarding slides can be modified if desired. Only users with :guilabel:`Administrator` rights for the Recruitment application can modify onboarding slides. To edit a slide, navigate to :menuselection:`Referrals app --> Configuration --> Onboarding.` Each line displays the text for the individual onboarding slide. To edit an onboarding slide, click on an individual slide line to open the slide's onboarding form, then click :guilabel:`Edit`." msgstr "" -#: ../../content/applications/hr/referrals.rst:74 +#: ../../content/applications/hr/referrals.rst:73 msgid "Make any changes to the message in the :guilabel:`Text` box. To change the order the slide appear in the onboarding, the :guilabel:`Sequence` can be modified. Type in the corresponding number to indicate the order in which the slides should be displayed. A :guilabel:`Company` may be selected, however, if this field is populated, that slide will only be displayed for that particular company." msgstr "" -#: ../../content/applications/hr/referrals.rst:79 +#: ../../content/applications/hr/referrals.rst:78 msgid "The image can be modified as well. Hover over the image thumbnail in the top right corner of the form. A :guilabel:`✏️ (pencil)` icon and :guilabel:`🗑️ (garbage can)` icon appear. Click the :guilabel:`✏️ (pencil)` icon to change the image. A file navigator window loads. Navigate to the desired image, select it, then click :guilabel:`Open`. The new image appears in the thumbnail. To delete an image, click the :guilabel:`🗑️ (garbage can)` icon, then select a new image using the :guilabel:`✏️ (pencil)` icon." msgstr "" -#: ../../content/applications/hr/referrals.rst:86 +#: ../../content/applications/hr/referrals.rst:85 msgid "To save any changes, click :guilabel:`Save`, or click :guilabel:`Discard` to delete any changes and revert to the original content." msgstr "" @@ -7016,7 +7494,7 @@ msgstr "" msgid "An onboarding slide in edit mode, with the main fields highlighted." msgstr "" -#: ../../content/applications/hr/referrals.rst:93 +#: ../../content/applications/hr/referrals.rst:92 msgid "The order of the slides can also be changed directly in the Onboarding dashboard, without having to edit an individual onboarding slide. Click the up and down arrow symbol that appears after the checkbox and before the slide text, and drag the slide to the desired position. The :guilabel:`Sequence` automatically changes on all the slide's onboarding forms, reflecting the new sequence." msgstr "" @@ -7024,19 +7502,19 @@ msgstr "" msgid "The onboarding slides in a list, with the drag and drop arrows highlighted." msgstr "" -#: ../../content/applications/hr/referrals.rst:104 +#: ../../content/applications/hr/referrals.rst:103 msgid "Share job positions" msgstr "" -#: ../../content/applications/hr/referrals.rst:106 +#: ../../content/applications/hr/referrals.rst:105 msgid "In order to earn referral points, a user must first share a job position so the applicant can apply for the position. There are several ways to share job positions within the Referrals application, through the :ref:`View Jobs ` button and the :ref:`Email A Friend ` button." msgstr "" -#: ../../content/applications/hr/referrals.rst:114 +#: ../../content/applications/hr/referrals.rst:113 msgid "View Jobs" msgstr "" -#: ../../content/applications/hr/referrals.rst:116 +#: ../../content/applications/hr/referrals.rst:115 msgid "To see all job positions that are actively recruiting candidates, click the :guilabel:`View Jobs` button on the main Referrals dashboard. This presents all job positions, with each individual job presented in its own card." msgstr "" @@ -7045,51 +7523,51 @@ msgid "The 'View Jobs' screen, displaying all current open job positions. All in "displayed on the card." msgstr "" -#: ../../content/applications/hr/referrals.rst:125 +#: ../../content/applications/hr/referrals.rst:124 msgid "Each job position card contains the following information:" msgstr "" -#: ../../content/applications/hr/referrals.rst:127 +#: ../../content/applications/hr/referrals.rst:126 msgid "The title of the job position. This information is taken from the :guilabel:`Job Position` field of the job form." msgstr "" -#: ../../content/applications/hr/referrals.rst:129 +#: ../../content/applications/hr/referrals.rst:128 msgid "The number of positions being recruited. This information is taken from the :guilabel:`Expected New Employees` field of the :guilabel:`Recruitment` tab of the job form." msgstr "" -#: ../../content/applications/hr/referrals.rst:131 +#: ../../content/applications/hr/referrals.rst:130 msgid "The points a user will earn when an applicant applies for the position." msgstr "" -#: ../../content/applications/hr/referrals.rst:132 +#: ../../content/applications/hr/referrals.rst:131 msgid "The job description detailing the job position. This information is taken from the :guilabel:`Job Position` tab of the job form." msgstr "" -#: ../../content/applications/hr/referrals.rst:135 +#: ../../content/applications/hr/referrals.rst:134 msgid "To see all the details for a job position, click the :guilabel:`More Info` button on the specific card. This opens the job position webpage in a new browser tab. This is what an applicant sees before applying for a position." msgstr "" -#: ../../content/applications/hr/referrals.rst:140 +#: ../../content/applications/hr/referrals.rst:139 msgid "Only published job positions will be visible in the Referrals app. To check which job positions are published or not, refer to the :doc:`recruitment/new_job` documentation." msgstr "" -#: ../../content/applications/hr/referrals.rst:144 +#: ../../content/applications/hr/referrals.rst:143 msgid "Refer friends" msgstr "" -#: ../../content/applications/hr/referrals.rst:146 +#: ../../content/applications/hr/referrals.rst:145 msgid "To share a job position with someone, click the :guilabel:`Refer Friend` button on the specific job position card. A pre-configured :guilabel:`Send Job Offer by Mail` email pop-up window appears. Enter the recipient's email address in the :guilabel:`Email` field." msgstr "" -#: ../../content/applications/hr/referrals.rst:150 +#: ../../content/applications/hr/referrals.rst:149 msgid "The subject and body are populated using a default template. The subject `Job for you` appears, and can be modified if desired." msgstr "" -#: ../../content/applications/hr/referrals.rst:153 +#: ../../content/applications/hr/referrals.rst:152 msgid "The specific title of the job position will populate the :guilabel:`Job Position` placeholder in the email body. The `See Job Offer` text in the email body is an individualized tracking link to the specific job position listed on the website. When the prospective employee receives the email, the link will send them to the job position page, where they can apply for the position, and the person who referred them is tracked in the Referrals application." msgstr "" -#: ../../content/applications/hr/referrals.rst:159 +#: ../../content/applications/hr/referrals.rst:158 msgid "If desired, add any text or closing salutation to the email body. When all edits have been made, click :guilabel:`Send Email` to send the email, or click :guilabel:`Cancel` to close the email pop-up window." msgstr "" @@ -7097,11 +7575,11 @@ msgstr "" msgid "Referral email pop-up window with the email message inside it." msgstr "" -#: ../../content/applications/hr/referrals.rst:168 +#: ../../content/applications/hr/referrals.rst:167 msgid "Share a job" msgstr "" -#: ../../content/applications/hr/referrals.rst:170 +#: ../../content/applications/hr/referrals.rst:169 msgid "There are several other ways to share a job position aside from sending an email, via social media platforms and tracking links to the job position. At the bottom of each job position card are four icons and corresponding tracking links that can be used to share the job position, keeping track of applicants in the Referrals application." msgstr "" @@ -7109,27 +7587,27 @@ msgstr "" msgid "The various sharing icons that appear for each job." msgstr "" -#: ../../content/applications/hr/referrals.rst:180 +#: ../../content/applications/hr/referrals.rst:179 msgid "Link" msgstr "" -#: ../../content/applications/hr/referrals.rst:182 +#: ../../content/applications/hr/referrals.rst:181 msgid "To share the job position with a customized tracking link, click the :guilabel:`Share Now` button with the :guilabel:`🔗 (chain)` icon inside it. A :guilabel:`Link to Share` pop-up window appears with the tracking link. Click :guilabel:`Copy` to copy the link. After the link is copied, click the :guilabel:`Close` button to close the pop-up. Next, share the link with the prospective employee however desired." msgstr "" -#: ../../content/applications/hr/referrals.rst:189 +#: ../../content/applications/hr/referrals.rst:188 msgid "Facebook" msgstr "" -#: ../../content/applications/hr/referrals.rst:191 +#: ../../content/applications/hr/referrals.rst:190 msgid "To share the job position using Facebook, click the :guilabel:`Share Now` button with the :guilabel:`f (Facebook icon)` inside it. If the user is already logged into Facebook, when the :guilabel:`f (Facebook icon)` is clicked, a :guilabel:`Share on Facebook` page loads in a new tab, with the link populated in the main body of the new post. If the user is *not* already logged in, a log-in screen loads instead, prompting the user to log-in to Facebook first." msgstr "" -#: ../../content/applications/hr/referrals.rst:197 +#: ../../content/applications/hr/referrals.rst:196 msgid "Type in any additional information to add to the post, in the space directly below your name. If desired, :guilabel:`tag` users, :guilabel:`check-in` at a location, or add a :guilabel:`status` to the post. To tag a user, click the :guilabel:`Tag Friends` icon and select the people to tag to the post. To add a check-in location, click the :guilabel:`Check in` icon, and select the location from the pop-up of predetermined locations based on your current location. To add a :guilabel:`status`, click the :guilabel:`Feeling/Activity` icon, then select either the feeling or the activity type, and lastly, if an activity type was selected, select the specific activity." msgstr "" -#: ../../content/applications/hr/referrals.rst:205 +#: ../../content/applications/hr/referrals.rst:204 msgid "There are five methods to share the job position, :guilabel:`Your Story`, :guilabel:`Share on a Friend's Timeline`, :guilabel:`Share in a Group`, :guilabel:`Share in an Event`, and :guilabel:`Share in a Private Message`. To select the sharing method, click the drop-down menu located at the top of the page, directly beneath the :guilabel:`Share on Facebook` banner." msgstr "" @@ -7138,113 +7616,113 @@ msgid "The view on Facebook when sharing a job description. All the various ways "highlighted, as are all the required settings." msgstr "" -#: ../../content/applications/hr/referrals.rst:217 +#: ../../content/applications/hr/referrals.rst:216 msgid "Share to news feed or story" msgstr "" -#: ../../content/applications/hr/referrals.rst:219 +#: ../../content/applications/hr/referrals.rst:218 msgid "The default sharing method is through the :guilabel:`News Feed`, :guilabel:`Story`, or both. At the lower portion of the form are radio buttons next to the two options, :guilabel:`Feed` (for the News Feed) and :guilabel:`Your Story` for stories. When :guilabel:`Share to News Feed or Story` is selected, these buttons are active, if another option is selected, these radio buttons are greyed out. Activate the radio button(s) to indicate how the job position should be shared, either in the news feed, the story, or both." msgstr "" -#: ../../content/applications/hr/referrals.rst:226 +#: ../../content/applications/hr/referrals.rst:225 msgid "The :guilabel:`Share to news feed or story` option allows for specific privacy settings to be selected. In the lower right corner of the screen, there are two drop-down menu options, one for the :guilabel:`Feed` option, the other for the :guilabel:`Your story` option. Select the posting parameters from the drop-down menus. The :guilabel:`Feed` ad :guilabel:`Your story` options appear different from user to user, depending on what privacy settings have been created in Facebook. :guilabel:`Public` and :guilabel:`Friends` are default options, but other options that the user may have configured will appear as well, such as custom groups." msgstr "" -#: ../../content/applications/hr/referrals.rst:234 +#: ../../content/applications/hr/referrals.rst:233 msgid "When the post and/or story is ready to be shared, click the blue :guilabel:`Post to Facebook` button at the bottom of the screen." msgstr "" -#: ../../content/applications/hr/referrals.rst:237 +#: ../../content/applications/hr/referrals.rst:236 msgid "Share on a friend's timeline" msgstr "" -#: ../../content/applications/hr/referrals.rst:239 +#: ../../content/applications/hr/referrals.rst:238 msgid "Instead of making a public post on the user's on Facebook page, the job position can be shared directly on a friend's timeline. Click the :guilabel:`Share to News Feed or Story` drop-down menu near the top of the page, and select :guilabel:`Share on a Fried's Timeline`." msgstr "" -#: ../../content/applications/hr/referrals.rst:243 +#: ../../content/applications/hr/referrals.rst:242 msgid "When selected, a :guilabel:`Friend` field appears below the selection. Begin to type in the friend's name. As the name is typed, a list appears, populated with names that match what is entered. Select the friend from the list. **Only** one friend can be selected." msgstr "" -#: ../../content/applications/hr/referrals.rst:247 -#: ../../content/applications/hr/referrals.rst:262 -#: ../../content/applications/hr/referrals.rst:276 +#: ../../content/applications/hr/referrals.rst:246 +#: ../../content/applications/hr/referrals.rst:261 +#: ../../content/applications/hr/referrals.rst:275 msgid "When the post is ready to be shared, click the blue :guilabel:`Post to Facebook` button at the bottom of the screen." msgstr "" -#: ../../content/applications/hr/referrals.rst:250 +#: ../../content/applications/hr/referrals.rst:249 msgid "Share in a group" msgstr "" -#: ../../content/applications/hr/referrals.rst:252 +#: ../../content/applications/hr/referrals.rst:251 msgid "To reach a specific audience and not share the job position publicly with everyone, a job can be shared in a group. Click the :guilabel:`Share to News Feed or Story` drop-down menu near the top of the page, and select :guilabel:`Share in a Group`." msgstr "" -#: ../../content/applications/hr/referrals.rst:256 +#: ../../content/applications/hr/referrals.rst:255 msgid "When selected, a :guilabel:`Group` field appears below the selection. The available groups that can be posted to are groups the user is currently a member of. Job positions cannot be shared with groups the user has not joined. Begin to type in the name of the group. As the group name is typed, a list appears, populated with the group names that match what is entered. Select the group from the list. Only one group can be selected." msgstr "" -#: ../../content/applications/hr/referrals.rst:265 +#: ../../content/applications/hr/referrals.rst:264 msgid "Share in an event" msgstr "" -#: ../../content/applications/hr/referrals.rst:267 +#: ../../content/applications/hr/referrals.rst:266 msgid "A job position can also be shared on an event page. Click the :guilabel:`Share to News Feed or Story` drop-down menu near the top of the page, and select :guilabel:`Share in an Event`." msgstr "" -#: ../../content/applications/hr/referrals.rst:270 +#: ../../content/applications/hr/referrals.rst:269 msgid "When selected, an :guilabel:`Event` field appears below the selection. The available events that can be posted to are events the user is invited to. This includes events that the user has not responded to yet, and events that have occurred in the past. Begin to type in the name of the event. As the event name is typed, a list appears, populated with the events that match what is entered. Select the event from the list. Only one event can be selected." msgstr "" -#: ../../content/applications/hr/referrals.rst:279 +#: ../../content/applications/hr/referrals.rst:278 msgid "Share in a private message" msgstr "" -#: ../../content/applications/hr/referrals.rst:281 +#: ../../content/applications/hr/referrals.rst:280 msgid "The last option is to share a job position privately instead of publicly, in a Facebook message. Click the :guilabel:`Share to News Feed or Story` drop-down menu near the top of the page, and select :guilabel:`Share in an Private Message`." msgstr "" -#: ../../content/applications/hr/referrals.rst:285 +#: ../../content/applications/hr/referrals.rst:284 msgid "When selected, a :guilabel:`To` field appears below the selection. Begin to type in the friend's name. As the name is typed, a list appears, populated with names that match what is entered. Select the friend from the list. Multiple friends can be selected and added to a single message. Repeat this process for each friend to be added." msgstr "" -#: ../../content/applications/hr/referrals.rst:290 +#: ../../content/applications/hr/referrals.rst:289 msgid "When the message is ready to be sent, click the blue :guilabel:`Send message` button at the bottom of the screen." msgstr "" -#: ../../content/applications/hr/referrals.rst:294 +#: ../../content/applications/hr/referrals.rst:293 msgid "X/Twitter" msgstr "" -#: ../../content/applications/hr/referrals.rst:296 +#: ../../content/applications/hr/referrals.rst:295 msgid "A job position can also be shared on X/Twitter. Click the :guilabel:`Share Now` button with the bird icon inside it. If the user is already signed in to X/Twitter, when the :guilabel:`Share Now` icon is clicked, an X/Twitter page loads in a new tab with a pre-populated message ready to post, in a draft pop-up. If the user is *not* already signed in, a sign-in screen loads instead, prompting the user to sign in to X/Twitter." msgstr "" -#: ../../content/applications/hr/referrals.rst:302 +#: ../../content/applications/hr/referrals.rst:301 msgid "The default message is:" msgstr "" -#: ../../content/applications/hr/referrals.rst:304 +#: ../../content/applications/hr/referrals.rst:303 msgid ":guilabel:`Amazing job offer for (Job Position)! Check it live: (link to Job Position)`" msgstr "" -#: ../../content/applications/hr/referrals.rst:306 +#: ../../content/applications/hr/referrals.rst:305 msgid "Type in any additional information or make any edits to the message. If desired, click the :guilabel:`X` in the top left corner of the thumbnail preview of the webpage to remove it. To adjust the audience for the message, click the drop-down button labeled :guilabel:`Everyone`. Select the preferred audience from the drop-down menu. The default option is :guilabel:`Everyone`, and the other options is :guilabel:`Circle`. The :guilabel:`Circle` is a group of people that the user has selected in X/Twitter." msgstr "" -#: ../../content/applications/hr/referrals.rst:313 +#: ../../content/applications/hr/referrals.rst:312 msgid "The default setting is :guilabel:`🌎 (globe) Everyone can reply`, an allows everyone on X/Twitter to reply to the message. To change this, click the :guilabel:`🌎 (globe) Everyone can reply` button in the lower left section of the message. There are four options presented: :guilabel:`Everyone`, :guilabel:`Accounts you follow`, :guilabel:`Verified accounts`, and :guilabel:`Only accounts you mention`. Selecting one of the other options restricts who can reply to the message." msgstr "" -#: ../../content/applications/hr/referrals.rst:319 +#: ../../content/applications/hr/referrals.rst:318 msgid "There are various other items that can be added to the message. Media (photos, videos, etc), GIF's, polls, emojis, and a location may all be added. Click the corresponding icon in the bottom left of the message and follow the prompts to add the desired additional elements." msgstr "" -#: ../../content/applications/hr/referrals.rst:323 +#: ../../content/applications/hr/referrals.rst:322 msgid "To have the message posted at a future date and time, click the :guilabel:`Schedule` icon in the lower left of the message window. It is the fifth icon from the left. Enter the date and time that the message should be posted using the date and time selector presented. Click :guilabel:`Confirm` to add the scheduled time to the message." msgstr "" -#: ../../content/applications/hr/referrals.rst:328 +#: ../../content/applications/hr/referrals.rst:327 msgid "To post the message, click :guilabel:`Post`. The message will be immediately posted, or, if it was scheduled, will be posted at the scheduled date and time." msgstr "" @@ -7253,39 +7731,39 @@ msgid "The X/Twitter pop-up when sharing a job description. All the other items "to the message are highlighted, as is the visibility setting and the post button." msgstr "" -#: ../../content/applications/hr/referrals.rst:337 +#: ../../content/applications/hr/referrals.rst:336 msgid "LinkedIn" msgstr "" -#: ../../content/applications/hr/referrals.rst:339 +#: ../../content/applications/hr/referrals.rst:338 msgid "To share a job position on LinkedIn, click the :guilabel:`Share Now` button with the :guilabel:`in (LinkedIn logo)` inside it. If the user is already logged into LinkedIn, when the :guilabel:`Share Now` button is clicked, a new tab loads in LinkedIn, with a link to the job position at the top. If the user is *not* already logged in, a log-in screen loads instead, prompting the user to log-in to LinkedIn first." msgstr "" -#: ../../content/applications/hr/referrals.rst:345 +#: ../../content/applications/hr/referrals.rst:344 msgid "The job position can be shared either in a public post, or in a private message to an individual or group of individuals." msgstr "" -#: ../../content/applications/hr/referrals.rst:349 +#: ../../content/applications/hr/referrals.rst:348 msgid "Share in a post" msgstr "" -#: ../../content/applications/hr/referrals.rst:351 +#: ../../content/applications/hr/referrals.rst:350 msgid "To share the job position in a public post, click the :guilabel:`✏️ (pencil) Share in a post` button in the lower-left corner of the screen. A :guilabel:`Create a post` window loads, with the job position link populated. Enter any other information to the post in the field." msgstr "" -#: ../../content/applications/hr/referrals.rst:355 +#: ../../content/applications/hr/referrals.rst:354 msgid "To change the audience that will see the post, click the :guilabel:`🌎 (globe) Anyone` drop-down, located directly beneath the account name. Click on the desired selection, then click the :guilabel:`Save` button on the far right side of the screen, beneath the last listed option." msgstr "" -#: ../../content/applications/hr/referrals.rst:359 +#: ../../content/applications/hr/referrals.rst:358 msgid ":guilabel:`Anyone` allows anyone on LinkedIn to see the post. :guilabel:`Connections only` will only share the post with people who are connected with the user, and will be hidden from everyone else. :guilabel:`Group` shares the post with a specific group the user is a member of. The post can only be shared with one group; posting to multiple groups at once is not available. If :guilabel:`Group` is selected, a page loads with a list of all the groups the user is currently a member of. Click on a group to select it, then click the :guilabel:`Save` button in the lower right corner." msgstr "" -#: ../../content/applications/hr/referrals.rst:367 +#: ../../content/applications/hr/referrals.rst:366 msgid "Next, select who can comment on the post. To change this setting, click on the :guilabel:`💬 (speech bubble) Anyone` button located beneath the body of the post. A page loads with the various options. Click on one of the three options to select it. The three options are :guilabel:`Anyone`, :guilabel:`Connections only`, and :guilabel:`No one`. The default option is :guilabel:`Anyone`, which allows anyone with a LinkedIn account to comment on the post. :guilabel:`Connections only` will only allow people who are connected with the user to comment on the post. :guilabel:`No one` turns off commenting. After making a selection, click the :guilabel:`Save` button in the far lower right corner." msgstr "" -#: ../../content/applications/hr/referrals.rst:376 +#: ../../content/applications/hr/referrals.rst:375 msgid "Finally, once the post is edited and the settings have been selected, click :guilabel:`Post` to share the job position." msgstr "" @@ -7293,63 +7771,63 @@ msgstr "" msgid "A linkedIn post to share a job. The job position is highlighted as is the post button." msgstr "" -#: ../../content/applications/hr/referrals.rst:384 +#: ../../content/applications/hr/referrals.rst:383 msgid "Send as private message" msgstr "" -#: ../../content/applications/hr/referrals.rst:386 +#: ../../content/applications/hr/referrals.rst:385 msgid "Instead of making a public post, the post can be sent to a connection in a private message. To do so, click the :guilabel:`Send as private message` button in the lower left corner. A message window loads with the link to the job description in the bottom of the window. First, select the recipient(s) for the message. Type the name in the :guilabel:`Search for message recipients` field. As the name is typed in, any matching connections appear. Click on a connection to add them. Repeat this for all the recipients to send the message to. There is no limit on the number of connections that can be messaged. Next, enter any additional text in the message body. Click :guilabel:`Send` in the lower right corner to send the message. A :guilabel:`Message successfully sent!` screen loads. Two options are presented, :guilabel:`View Message` and :guilabel:`Continue to LinkedIn`. Click on the desired selection to navigate to that choice, or close the browser tab to exit." msgstr "" -#: ../../content/applications/hr/referrals.rst:400 +#: ../../content/applications/hr/referrals.rst:399 msgid "Email a friend" msgstr "" -#: ../../content/applications/hr/referrals.rst:402 +#: ../../content/applications/hr/referrals.rst:401 msgid "Another way to share job opportunities is to share the entire current list of open job positions instead of one job position at a time. To do this, navigate to the main *Referrals* app dashboard. Click the :guilabel:`Email a friend` button at the bottom of the screen. A :guilabel:`Send Job Offer by Mail` pop-up window appears." msgstr "" -#: ../../content/applications/hr/referrals.rst:407 +#: ../../content/applications/hr/referrals.rst:406 msgid "Enter the email address(es) in the :guilabel:`Email` line. The email can be sent to multiple recipients, simply enter a comma followed by a single space after each email address. The :guilabel:`Subject` is pre-configured with `Job for you`, but can be edited." msgstr "" -#: ../../content/applications/hr/referrals.rst:411 +#: ../../content/applications/hr/referrals.rst:410 msgid "The email body is also populated with pre-configured text. The text that appears is:" msgstr "" -#: ../../content/applications/hr/referrals.rst:413 +#: ../../content/applications/hr/referrals.rst:412 msgid "`Hello,`" msgstr "" -#: ../../content/applications/hr/referrals.rst:415 +#: ../../content/applications/hr/referrals.rst:414 msgid "`There are some amazing job offers in my company! Have a look, they can be interesting for you`" msgstr "" -#: ../../content/applications/hr/referrals.rst:417 +#: ../../content/applications/hr/referrals.rst:416 msgid "`See Job Offers`" msgstr "" -#: ../../content/applications/hr/referrals.rst:419 +#: ../../content/applications/hr/referrals.rst:418 msgid "The `See Job Offers` text is a tracking link to a complete list of all job positions currently being recruited for, that are live on the company's website (published). Add any additional text and/or make any edits to the message body, then click :guilabel:`Send Mail` to send the email. The message will be sent and the window will close." msgstr "" -#: ../../content/applications/hr/referrals.rst:427 +#: ../../content/applications/hr/referrals.rst:426 msgid "Hired referrals" msgstr "" -#: ../../content/applications/hr/referrals.rst:429 +#: ../../content/applications/hr/referrals.rst:428 msgid "When a candidate that has been referred by a user is hired, the user \"grows their superhero team\" and adds superhero avatars to their Referrals dashboard." msgstr "" -#: ../../content/applications/hr/referrals.rst:432 +#: ../../content/applications/hr/referrals.rst:431 msgid "After a referral has been hired, when the user next opens the Referrals app, instead of the main dashboard, a hired page loads. The text :guilabel:`(Referral Name) has been hired! Choose an avatar for your new friend!` appears." msgstr "" -#: ../../content/applications/hr/referrals.rst:436 +#: ../../content/applications/hr/referrals.rst:435 msgid "Below this message are five avatar thumbnails to choose from. If an avatar has already been assigned to a referral, the thumbnail is greyed out, and the name the avatar has been chosen for appears beneath the avatar. Click on an available avatar to select it." msgstr "" -#: ../../content/applications/hr/referrals.rst:440 +#: ../../content/applications/hr/referrals.rst:439 msgid "If more than one referral was hired since opening the Referrals application, after selecting the first avatar, the user is prompted to select another avatar for the subsequent hired referral. Once all avatars have been selected, the dashboard loads and all the avatars are now visible. Mouse over each avatar and their name is displayed above them." msgstr "" @@ -7358,28 +7836,28 @@ msgid "The hired screen. A selection of avatars are presented to chose from, wit "chosen are greyed out." msgstr "" -#: ../../content/applications/hr/referrals.rst:451 +#: ../../content/applications/hr/referrals.rst:450 msgid "Modify friends" msgstr "" -#: ../../content/applications/hr/referrals.rst:453 +#: ../../content/applications/hr/referrals.rst:452 msgid "Friend avatars are able to be modified in the same manner that :ref:`levels ` are modified. Only users with :guilabel:`Administrator` rights for the Recruitment application can make modifications to friends. The pre-configured friends can be seen and modified by navigating to :menuselection:`Referrals app --> Configuration --> Friends`. Each friend avatar appears in the :guilabel:`Dashboard Image` column, and the corresponding name appears in the :guilabel:`Friend Name` column. The default images are a motley group of hero characters, ranging from robots to dogs." msgstr "" -#: ../../content/applications/hr/referrals.rst:460 +#: ../../content/applications/hr/referrals.rst:459 msgid "To modify a friend's dashboard image, thumbnail, name, or position, click on an individual friend to open the referral friend form. Click :guilabel:`Edit` to make modifications. Type the name in the :guilabel:`Friend Name` field. The name is solely to differentiate the friends in the configuration menu; the friend's name is not visible anywhere else in the Referrals application." msgstr "" -#: ../../content/applications/hr/referrals.rst:465 +#: ../../content/applications/hr/referrals.rst:464 msgid "The :guilabel:`Position` can be set to either :guilabel:`Front` or :guilabel:`Back`. This determines the position of the friend in relation to the user's super hero avatar. Click the radio button next to the desired selection, and the friend will appear either in front of or behind the user's avatar when activated." msgstr "" -#: ../../content/applications/hr/referrals.rst:470 +#: ../../content/applications/hr/referrals.rst:469 msgid "If desired, both the thumbnail :guilabel:`Image` and the :guilabel:`Dashboard Image` can be modified. Hover over the image being replaced to reveal a :guilabel:`✏️ (pencil)` icon and :guilabel:`🗑️ (garbage can)` icon. Click the :guilabel:`✏️ (pencil)` icon and a file explorer window appears. Navigate to the desired image file then click :guilabel:`Open` to select it." msgstr "" -#: ../../content/applications/hr/referrals.rst:475 -#: ../../content/applications/hr/referrals.rst:660 +#: ../../content/applications/hr/referrals.rst:474 +#: ../../content/applications/hr/referrals.rst:659 msgid "Once all changes have been made, click the :guilabel:`Save` button to save the changes, or click the :guilabel:`Discard` button to revert to the original information." msgstr "" @@ -7387,132 +7865,132 @@ msgstr "" msgid "A friend form in edit mode." msgstr "" -#: ../../content/applications/hr/referrals.rst:483 -#: ../../content/applications/hr/referrals.rst:668 +#: ../../content/applications/hr/referrals.rst:482 +#: ../../content/applications/hr/referrals.rst:667 msgid "It is not advised to edit the images. An image file must have a transparent background in order for it to render properly. Only users with knowledge about transparent images should attempt adjusting any images in the Referrals application." msgstr "" -#: ../../content/applications/hr/referrals.rst:487 +#: ../../content/applications/hr/referrals.rst:486 msgid "Once an image is changed and the friend is saved, it is **not possible** to revert to the original image. To revert to the original image, the Referrals application must be *uninstalled then reinstalled.*" msgstr "" -#: ../../content/applications/hr/referrals.rst:492 +#: ../../content/applications/hr/referrals.rst:491 msgid "Referral points" msgstr "" -#: ../../content/applications/hr/referrals.rst:494 +#: ../../content/applications/hr/referrals.rst:493 msgid "The referral program is based on earning points that are then exchanged for rewards. On the main Referrals application dashboard, the top displays a summary of the user's current points. The left side of the summary displays the total points earned, and the right side displays the points that are available to spend." msgstr "" -#: ../../content/applications/hr/referrals.rst:499 +#: ../../content/applications/hr/referrals.rst:498 msgid "To see the various referrals and the points earned for each, click on one of the buttons directly beneath the avatars. The options are :guilabel:`Referrals`, :guilabel:`Ongoing`, and :guilabel:`Successful`." msgstr "" -#: ../../content/applications/hr/referrals.rst:503 +#: ../../content/applications/hr/referrals.rst:502 msgid "The current number of referrals who are still active in the recruitment pipeline, and have not yet been hired or refused, appear above the :guilabel:`Ongoing` button. The number of referrals who have been hired appear above the :guilabel:`Successful` button. The total number of referrals (both the ongoing and successful referrals combined) appear above the :guilabel:`Referrals` button." msgstr "" -#: ../../content/applications/hr/referrals.rst:509 +#: ../../content/applications/hr/referrals.rst:508 msgid "To view the referrals associated with each of the categories, :guilabel:`Referrals`, :guilabel:`Ongoing`, and :guilabel:`Successful`, click on the corresponding button. All the referrals for that specific category are displayed." msgstr "" -#: ../../content/applications/hr/referrals.rst:514 +#: ../../content/applications/hr/referrals.rst:513 msgid "My referrals" msgstr "" -#: ../../content/applications/hr/referrals.rst:516 +#: ../../content/applications/hr/referrals.rst:515 msgid "To see all the referrals (both ongoing and successful) click the :guilabel:`Referrals` button. A :guilabel:`My Referral` window loads. This screen displays all the referrals, with each referral in its own referral card." msgstr "" -#: ../../content/applications/hr/referrals.rst:520 +#: ../../content/applications/hr/referrals.rst:519 msgid "A successful referral has a green line down the left side of the card, and displays a :guilabel:`✓ Hired` image in the top right corner of the card. Referrals that are in process display an :guilabel:`In Progress` image in the top right corner." msgstr "" -#: ../../content/applications/hr/referrals.rst:524 +#: ../../content/applications/hr/referrals.rst:523 msgid "Each referral card lists the name of the applicant, the department the job position is in, the name of the job position, the person responsible for filling the role (recruiter), and the points earned." msgstr "" -#: ../../content/applications/hr/referrals.rst:528 +#: ../../content/applications/hr/referrals.rst:527 msgid "Points" msgstr "" -#: ../../content/applications/hr/referrals.rst:530 +#: ../../content/applications/hr/referrals.rst:529 msgid "The points that can be earned for a referral are the same across all job positions. Each stage of the recruitment process has corresponding points assigned to it. The stages listed correspond to the stages configured in the *Recruitment* application." msgstr "" -#: ../../content/applications/hr/referrals.rst:534 +#: ../../content/applications/hr/referrals.rst:533 msgid "On each individual referral card, beneath the points earned is a bar chart that displays how many points have been earned out of the total possible points that can be earned if the applicant is hired." msgstr "" -#: ../../content/applications/hr/referrals.rst:538 +#: ../../content/applications/hr/referrals.rst:537 msgid "Beneath the bar chart is a list of the various recruitment stages and the points earned when the referral moves to that stage. If a stage has been achieved and the points have been earned, a green check mark appears next to the stage." msgstr "" -#: ../../content/applications/hr/referrals.rst:543 +#: ../../content/applications/hr/referrals.rst:542 msgid "The pre-configured point structure for referrals is as follows:" msgstr "" -#: ../../content/applications/hr/referrals.rst:545 +#: ../../content/applications/hr/referrals.rst:544 msgid ":guilabel:`Initial Qualification`: 1 point" msgstr "" -#: ../../content/applications/hr/referrals.rst:546 +#: ../../content/applications/hr/referrals.rst:545 msgid ":guilabel:`First Interview`: 20 points" msgstr "" -#: ../../content/applications/hr/referrals.rst:547 +#: ../../content/applications/hr/referrals.rst:546 msgid ":guilabel:`Second Interview`: 9 points" msgstr "" -#: ../../content/applications/hr/referrals.rst:548 +#: ../../content/applications/hr/referrals.rst:547 msgid ":guilabel:`Contract Proposal`: 5 points" msgstr "" -#: ../../content/applications/hr/referrals.rst:549 +#: ../../content/applications/hr/referrals.rst:548 msgid ":guilabel:`Contract Signed`: 50 points" msgstr "" -#: ../../content/applications/hr/referrals.rst:551 +#: ../../content/applications/hr/referrals.rst:550 msgid "The total points earned for a referral that is hired is 85 points. Modifications of the points earned for each stage is done in the Recruitment application. Refer to the :ref:`Recruitment ` documentation to modify the points for each stage." msgstr "" -#: ../../content/applications/hr/referrals.rst:558 +#: ../../content/applications/hr/referrals.rst:557 msgid "Rewards" msgstr "" -#: ../../content/applications/hr/referrals.rst:561 +#: ../../content/applications/hr/referrals.rst:560 msgid "Create rewards" msgstr "" -#: ../../content/applications/hr/referrals.rst:563 +#: ../../content/applications/hr/referrals.rst:562 msgid "The rewards are the only configurations needed when setting up the Referrals application. Only users with :guilabel:`Administrator` rights for the Recruitment application can create or modify rewards. To add rewards, navigate to :menuselection:`Referrals app --> Configuration --> Rewards`. Click :guilabel:`Create` and a reward form loads. Enter the following information on the form:" msgstr "" -#: ../../content/applications/hr/referrals.rst:568 +#: ../../content/applications/hr/referrals.rst:567 msgid ":guilabel:`Product Name`: Enter the name as it should appear for the reward." msgstr "" -#: ../../content/applications/hr/referrals.rst:569 +#: ../../content/applications/hr/referrals.rst:568 msgid ":guilabel:`Cost`: Enter the amount of points required to redeem the reward." msgstr "" -#: ../../content/applications/hr/referrals.rst:570 +#: ../../content/applications/hr/referrals.rst:569 msgid ":guilabel:`Company`: Using the drop-down menu, select the company the reward will appear for. If a reward is to be used for several companies, each company needs to have a record of the reward, with the company listed on the form." msgstr "" -#: ../../content/applications/hr/referrals.rst:573 +#: ../../content/applications/hr/referrals.rst:572 msgid ":guilabel:`Gift Responsible`: Select the person who will be responsible for procuring and delivering the reward to the recipient, using the drop-down menu. This person is alerted when the reward is purchased, so they know when to deliver the reward to the recipient." msgstr "" -#: ../../content/applications/hr/referrals.rst:576 +#: ../../content/applications/hr/referrals.rst:575 msgid ":guilabel:`Description`: Type in the description for the reward. This will be visible on the reward card, beneath the title." msgstr "" -#: ../../content/applications/hr/referrals.rst:578 +#: ../../content/applications/hr/referrals.rst:577 msgid ":guilabel:`Photo`: Add a photo of the reward, which appears on the rewards page. Hover over the image square, and two icons appear, a :guilabel:`✏️ (pencil)` and a :guilabel:`🗑️ (garbage can)`. Click the :guilabel:`✏️ (pencil)` icon and a file explorer appears. Navigate to the photo file, then click :guilabel:`Open` to select it." msgstr "" -#: ../../content/applications/hr/referrals.rst:583 +#: ../../content/applications/hr/referrals.rst:582 msgid "The only required fields are the :guilabel:`Product Name`, :guilabel:`Company`, and :guilabel:`Description`." msgstr "" @@ -7520,23 +7998,23 @@ msgstr "" msgid "A filled out reward form with all details entered." msgstr "" -#: ../../content/applications/hr/referrals.rst:591 +#: ../../content/applications/hr/referrals.rst:590 msgid "It is advised to enter a :guilabel:`Cost` and add a :guilabel:`Photo`. If a cost is not entered, the default cost will be listed as zero, which would list the reward as free in the reward shop. If a photo is not selected, a placeholder icon will be displayed on the rewards page." msgstr "" -#: ../../content/applications/hr/referrals.rst:596 +#: ../../content/applications/hr/referrals.rst:595 msgid "Redeem rewards" msgstr "" -#: ../../content/applications/hr/referrals.rst:598 +#: ../../content/applications/hr/referrals.rst:597 msgid "To redeem points for a reward, click the :guilabel:`Rewards` button on the main Referrals dashboard. All the configured rewards are listed in individual reward cards. The points required to purchase the reward is listed in the top right corner of the card. If the user has enough points to purchase a reward, a :guilabel:`🧺 (basket) Buy` button appears at the bottom of the reward card. If they do not have enough points for a reward, the reward card displays :guilabel:`You need another (x) points to buy this` instead of a buy button." msgstr "" -#: ../../content/applications/hr/referrals.rst:605 +#: ../../content/applications/hr/referrals.rst:604 msgid "Click the :guilabel:`🧺 (basket) Buy` button on a reward to purchase it. A confirmation pop-up appears, asking if the user is sure they want to purchase the reward. Click :guilabel:`OK` to purchase the item, or :guilabel:`Cancel` to close the window and cancel the purchase." msgstr "" -#: ../../content/applications/hr/referrals.rst:609 +#: ../../content/applications/hr/referrals.rst:608 msgid "After :guilabel:`OK` is clicked, the pop-up window closes, and the points used to purchase the reward are subtracted from the user's available points. The rewards presented are now updated to reflect the user's current available points." msgstr "" @@ -7545,39 +8023,39 @@ msgid "Buy button appears below a mug and backpack reward, while the bicycle rew "many more reward points are needed to redeem." msgstr "" -#: ../../content/applications/hr/referrals.rst:621 +#: ../../content/applications/hr/referrals.rst:620 msgid "Levels" msgstr "" -#: ../../content/applications/hr/referrals.rst:623 +#: ../../content/applications/hr/referrals.rst:622 msgid "The referrals application has pre-configured levels that are reflected in the user's avatar on the Referrals dashboard. As a user refers potential employees and earns points, they can *level up*, much like in a video game." msgstr "" -#: ../../content/applications/hr/referrals.rst:627 +#: ../../content/applications/hr/referrals.rst:626 msgid "Levels have no functional impact on the performance of the application. They are solely used for the purpose of adding achievement tiers for participants to aim for, gamifying referrals for the user." msgstr "" -#: ../../content/applications/hr/referrals.rst:630 +#: ../../content/applications/hr/referrals.rst:629 msgid "The user's current level is displayed at the top of the main Referrals application dashboard, directly beneath their photo, in a :guilabel:`Level: X` format. In addition, a colored ring appears around the user's photo, indicating how many points the user currently has, and how many additional points they need to level up. The cyan colored portion of the ring represents points earned, while the white colored portion represents the points still needed before they can level up." msgstr "" -#: ../../content/applications/hr/referrals.rst:637 +#: ../../content/applications/hr/referrals.rst:636 msgid "Modify levels" msgstr "" -#: ../../content/applications/hr/referrals.rst:639 +#: ../../content/applications/hr/referrals.rst:638 msgid "Only users with :guilabel:`Administrator` rights for the Recruitment application can modify levels. The pre-configured levels can be seen and modified by navigating to :menuselection:`Referrals app --> Configuration --> Levels`. Each avatar appears in the :guilabel:`Image` column, and the corresponding level number appears in the :guilabel:`Level Name` column. The default images are of Odoo superheroes, and each level adds an additional element to their avatar, such as capes and shields." msgstr "" -#: ../../content/applications/hr/referrals.rst:646 +#: ../../content/applications/hr/referrals.rst:645 msgid "To modify a level's image, name, or points required to reach the level, click on an individual level in the list to open the level form. Click :guilabel:`Edit` to make modifications." msgstr "" -#: ../../content/applications/hr/referrals.rst:649 +#: ../../content/applications/hr/referrals.rst:648 msgid "Type in the name or number of the level in the :guilabel:`Level Name` field. What is entered is displayed beneath the user's photo on the main dashboard when they reach that level. Enter the number of referral points needed to reach that level in the :guilabel:`Requirements` field. The points needed to level up are the total accumulated points earned over the lifetime of the employee, not additional points from the previous level that must be earned." msgstr "" -#: ../../content/applications/hr/referrals.rst:655 +#: ../../content/applications/hr/referrals.rst:654 msgid "If desired, the :guilabel:`Image` can also be modified. Hover over the image to reveal a :guilabel:`✏️ (pencil)` icon and :guilabel:`🗑️ (garbage can)` icon. Click the :guilabel:`✏️ (pencil)` icon and a file explorer window appears. Navigate to the desired image file then click :guilabel:`Open` to select it." msgstr "" @@ -7585,23 +8063,23 @@ msgstr "" msgid "A level form in edit mode." msgstr "" -#: ../../content/applications/hr/referrals.rst:672 +#: ../../content/applications/hr/referrals.rst:671 msgid "Once an image is changed and the level is saved, it is **not possible** to revert to the original image. To revert to the original image, the Referrals application must be *uninstalled then reinstalled.*" msgstr "" -#: ../../content/applications/hr/referrals.rst:677 +#: ../../content/applications/hr/referrals.rst:676 msgid "Level up" msgstr "" -#: ../../content/applications/hr/referrals.rst:679 +#: ../../content/applications/hr/referrals.rst:678 msgid "Once enough points have been accumulated to level up, the circle around the user's photo is completely filled in with a cyan color, a large image stating :guilabel:`Level up!` appears above the photo, and the phrase :guilabel:`Click to level up!` appears beneath the user's photo and current level." msgstr "" -#: ../../content/applications/hr/referrals.rst:684 +#: ../../content/applications/hr/referrals.rst:683 msgid "Click on either the :guilabel:`LEVEL UP!` graphic, the user's photo, or the text :guilabel:`Click to level up!` beneath the user's photo to level up the user. The user's avatar changes to the current level, and the ring around the photo is updated to indicate the current amount of points." msgstr "" -#: ../../content/applications/hr/referrals.rst:688 +#: ../../content/applications/hr/referrals.rst:687 msgid "Leveling up does not cost the user any points, the user simply needs to earn the specified amount of points required." msgstr "" @@ -7610,19 +8088,19 @@ msgid "A 'Click to level up!' appears beneath the user's image, and a large 'Lev "above their image." msgstr "" -#: ../../content/applications/hr/referrals.rst:697 +#: ../../content/applications/hr/referrals.rst:696 msgid "Once a user has reached the highest configured level, they will continue to accrue points that can be redeemed for rewards, but they are no longer able to level up. The ring around their photo remains solid cyan." msgstr "" -#: ../../content/applications/hr/referrals.rst:702 +#: ../../content/applications/hr/referrals.rst:701 msgid "Alerts" msgstr "" -#: ../../content/applications/hr/referrals.rst:704 +#: ../../content/applications/hr/referrals.rst:703 msgid "In the Referrals application, it is possible to post a message, also referred to as an *alert*, at the top of the dashboard to share important information with users. These alerts appear as a thin semi-transparent banner, with the word :guilabel:`New!` appearing on the far left. The text for the alert is in the center of the banner, and on the far right side is an :guilabel:`X`." msgstr "" -#: ../../content/applications/hr/referrals.rst:709 +#: ../../content/applications/hr/referrals.rst:708 msgid "Alerts appear on the main dashboard for the specified time configured on the individual alert. If a user does not wish to see a specific alert again, click the :guilabel:`X` in the far right side of the alert. This removes the alert from the dashboard and will not appear again, even when opening the Referrals application for the first time in a new session." msgstr "" @@ -7630,47 +8108,47 @@ msgstr "" msgid "Two alert banners appear above the user's photo." msgstr "" -#: ../../content/applications/hr/referrals.rst:719 +#: ../../content/applications/hr/referrals.rst:718 msgid "Create an alert" msgstr "" -#: ../../content/applications/hr/referrals.rst:721 +#: ../../content/applications/hr/referrals.rst:720 msgid "Only users with :guilabel:`Administrator` rights for the Recruitment application can create alerts. To add a new alert, navigate to the :menuselection:`Referrals application --> Configuration --> Alerts`." msgstr "" -#: ../../content/applications/hr/referrals.rst:725 +#: ../../content/applications/hr/referrals.rst:724 msgid "Click :guilabel:`Create` and a blank alert form loads. Enter the following information on the form:" msgstr "" -#: ../../content/applications/hr/referrals.rst:727 +#: ../../content/applications/hr/referrals.rst:726 msgid ":guilabel:`Date From`: The date the alert starts. On this date, the alert will be visible on the dashboard." msgstr "" -#: ../../content/applications/hr/referrals.rst:729 +#: ../../content/applications/hr/referrals.rst:728 msgid ":guilabel:`Date To`: The date the alert ends. After this date, the alert will be hidden from view." msgstr "" -#: ../../content/applications/hr/referrals.rst:730 +#: ../../content/applications/hr/referrals.rst:729 msgid ":guilabel:`Company`: The current company populates this field by default. To modify the company the alert should be displayed for, select the company from the drop-down menu. If this field remains blank, the alert is visible to everyone with access to the Referrals application. If a company is specified, only user's within that company (who also have access to the Referrals application) will see the alert." msgstr "" -#: ../../content/applications/hr/referrals.rst:735 +#: ../../content/applications/hr/referrals.rst:734 msgid ":guilabel:`Alert`: Enter the text for the alert. This message appears inside the alert banner on the main dashboard." msgstr "" -#: ../../content/applications/hr/referrals.rst:737 +#: ../../content/applications/hr/referrals.rst:736 msgid ":guilabel:`On Click`: There are three options for the alert. Click the radio button next to the desired selection. The options are:" msgstr "" -#: ../../content/applications/hr/referrals.rst:740 +#: ../../content/applications/hr/referrals.rst:739 msgid ":guilabel:`Not Clickable`: The alert only displays text, there is no link to click." msgstr "" -#: ../../content/applications/hr/referrals.rst:741 +#: ../../content/applications/hr/referrals.rst:740 msgid ":guilabel:`Go to All Jobs`: The alert contains a link that when clicked, navigates to the website with all the currently posted job positions." msgstr "" -#: ../../content/applications/hr/referrals.rst:743 +#: ../../content/applications/hr/referrals.rst:742 msgid ":guilabel:`Specify URL`: The alert contains a link to a specific URL, that when clicked, navigates to that URL. When selected, a :guilabel:`URL` field appears below the :guilabel:`On Click` section. Enter the URL in the field." msgstr "" @@ -7678,23 +8156,23 @@ msgstr "" msgid "An alert form completely filled in with all selections entered." msgstr "" -#: ../../content/applications/hr/referrals.rst:756 +#: ../../content/applications/hr/referrals.rst:755 msgid "Only users with :guilabel:`Administrator` rights for the Recruitment application have access to the Reporting feature in Referrals. To access the reports, click :menuselection:`Referrals application --> Reporting`. The main view is the Reporting Dashboard view, which contains three sections." msgstr "" -#: ../../content/applications/hr/referrals.rst:760 +#: ../../content/applications/hr/referrals.rst:759 msgid "In the top portion of the window, the report displays a bar chart of how many referred candidates are hired, and how many are still in the hiring pipeline. The candidates are further divided by channel, showing specifically where the referral came from, such as a direct referral, Facebook, etc. If a channel does not appear on the report, that indicates there are no referrals from that particular channel." msgstr "" -#: ../../content/applications/hr/referrals.rst:766 +#: ../../content/applications/hr/referrals.rst:765 msgid "The middle third provides all the specific data that has been tracked. This includes how many total points have been earned across all referrals, how many applicants were referred, hired, or refused, how many applicants the current logged-in user referred, how many total points were earned, and how many points were given for refused applicants." msgstr "" -#: ../../content/applications/hr/referrals.rst:771 +#: ../../content/applications/hr/referrals.rst:770 msgid "The bottom third displays a pivot table. This table can be inserted into a new or existing spreadsheet. To do so, click the :guilabel:`Insert in Spreadsheet` button right above the chart. A pop-up appears, asking which spreadsheet to insert the pivot chart into. Select the desired spreadsheet from the drop-down menu, or select :guilabel:`New Spreadsheet`. Click :guilabel:`Confirm` and the selected spreadsheet loads, with the new table in it." msgstr "" -#: ../../content/applications/hr/referrals.rst:778 +#: ../../content/applications/hr/referrals.rst:777 msgid "The spreadsheet is stored in the *Documents* application. This application needs to be installed in order to use the :guilabel:`Insert in Spreadsheet` option." msgstr "" @@ -7790,103 +8268,103 @@ msgstr "" msgid ":guilabel:`Hours`: if the time off can be taken in hourly increments." msgstr "" -#: ../../content/applications/hr/time_off.rst:82 +#: ../../content/applications/hr/time_off.rst:84 msgid ":guilabel:`Deduct Extra Hours`: tick this box if the time off request should factor in any extra time accrued by the employee" msgstr "" -#: ../../content/applications/hr/time_off.rst:86 +#: ../../content/applications/hr/time_off.rst:88 msgid "For example, if an employee worked two (2) extra hours for the week, and requests five (5) hours of time off, the request would be for three (3) hours, since the two (2) additionally worked hours are used first, and deducted from the request." msgstr "" -#: ../../content/applications/hr/time_off.rst:90 +#: ../../content/applications/hr/time_off.rst:92 msgid ":guilabel:`Allow To Join Supporting Document`: tick this box to allow the employee to attach documents to the time off request. This is useful in situations where documentation is required, such as long-term medical leave." msgstr "" -#: ../../content/applications/hr/time_off.rst:93 +#: ../../content/applications/hr/time_off.rst:95 msgid ":guilabel:`Kind of Leave`: select from the drop-down menu the type of leave this time off type is, either :guilabel:`Time Off` or :guilabel:`Other`." msgstr "" -#: ../../content/applications/hr/time_off.rst:95 +#: ../../content/applications/hr/time_off.rst:97 msgid ":guilabel:`Company`: if multiple companies are created in the database, and this time off type only applies to one company, select the company from the drop-down menu. If this field is left blank, the time off type applies to all companies in the database." msgstr "" -#: ../../content/applications/hr/time_off.rst:100 +#: ../../content/applications/hr/time_off.rst:102 msgid "Allocation requests section" msgstr "" -#: ../../content/applications/hr/time_off.rst:102 +#: ../../content/applications/hr/time_off.rst:104 msgid ":guilabel:`Requires allocation`: if the time off must be allocated to employees, select :guilabel:`Yes`. If the time off can be requested without time off being previously allocated, select :guilabel:`No Limit`. If :guilabel:`No Limit` is selected, the following options do not appear on the form." msgstr "" -#: ../../content/applications/hr/time_off.rst:106 +#: ../../content/applications/hr/time_off.rst:108 msgid ":guilabel:`Employee Requests`: select :guilabel:`Extra Days Requests Allowed` if the employee is able to request more time off than was allocated." msgstr "" -#: ../../content/applications/hr/time_off.rst:110 +#: ../../content/applications/hr/time_off.rst:112 msgid "For example, if ten (10) days are allocated to the employee for this particular type of time off, and this option is enabled, the employee may submit a request for more than ten (10) days." msgstr "" -#: ../../content/applications/hr/time_off.rst:113 +#: ../../content/applications/hr/time_off.rst:115 msgid "If employees should **not** be able to make requests for more time off than what was allocated, select the :guilabel:`Not Allowed` option." msgstr "" -#: ../../content/applications/hr/time_off.rst:116 +#: ../../content/applications/hr/time_off.rst:118 msgid ":guilabel:`Approval`: select the type of approval(s) required for the allocation of this particular type of time off." msgstr "" -#: ../../content/applications/hr/time_off.rst:119 +#: ../../content/applications/hr/time_off.rst:121 msgid ":guilabel:`No validation needed` indicates that no approvals are required." msgstr "" -#: ../../content/applications/hr/time_off.rst:120 +#: ../../content/applications/hr/time_off.rst:122 msgid ":guilabel:`Approved by Time Off Officer` indicates the :ref:`Time Off Officer ` set on this form must approve the allocation." msgstr "" -#: ../../content/applications/hr/time_off.rst:122 +#: ../../content/applications/hr/time_off.rst:124 msgid ":guilabel:`Set by Time Off Officer` indicates that the :ref:`Time Off Officer ` set on this form must allocate the time off." msgstr "" -#: ../../content/applications/hr/time_off.rst:126 +#: ../../content/applications/hr/time_off.rst:128 msgid "Payroll section" msgstr "" -#: ../../content/applications/hr/time_off.rst:128 +#: ../../content/applications/hr/time_off.rst:130 msgid "If the time off type should create :doc:`../hr/payroll/work_entries` in the *Payroll* application, select the :guilabel:`Work Entry Type` from the drop-down list." msgstr "" -#: ../../content/applications/hr/time_off.rst:132 +#: ../../content/applications/hr/time_off.rst:134 msgid "Timesheets section" msgstr "" -#: ../../content/applications/hr/time_off.rst:135 +#: ../../content/applications/hr/time_off.rst:137 msgid "The :guilabel:`Timesheets` section only appears if the user is in developer mode. Refer to the :ref:`developer-mode` document for details on how to access the developer mode." msgstr "" -#: ../../content/applications/hr/time_off.rst:138 +#: ../../content/applications/hr/time_off.rst:140 msgid "When an employee takes time off and is also using timesheets, Odoo creates entries in the timesheet for the time off. This section defines how they are entered." msgstr "" -#: ../../content/applications/hr/time_off.rst:141 +#: ../../content/applications/hr/time_off.rst:143 msgid ":guilabel:`Project`: select the project that the time off type entries appear in." msgstr "" -#: ../../content/applications/hr/time_off.rst:142 +#: ../../content/applications/hr/time_off.rst:144 msgid ":guilabel:`Task`: select the task that appears in the timesheet for this time off type. The options are: :guilabel:`Time Off`, :guilabel:`Meeting`, or :guilabel:`Training`." msgstr "" -#: ../../content/applications/hr/time_off.rst:146 +#: ../../content/applications/hr/time_off.rst:148 msgid "Display option section" msgstr "" -#: ../../content/applications/hr/time_off.rst:148 +#: ../../content/applications/hr/time_off.rst:150 msgid ":guilabel:`Color`: select a color to be used in the *Time Off* application dashboard." msgstr "" -#: ../../content/applications/hr/time_off.rst:149 +#: ../../content/applications/hr/time_off.rst:151 msgid ":guilabel:`Cover Image`: select an icon to be used in the *Time Off* application dashboard." msgstr "" -#: ../../content/applications/hr/time_off.rst:152 +#: ../../content/applications/hr/time_off.rst:154 msgid "The only required fields on the time off type form are the name of the :guilabel:`Time Off Type`, the :guilabel:`Approval`, the :guilabel:`Responsible Time Off Officer`, :guilabel:`Take Time Off in`, :guilabel:`Kind of Leave`, and the :guilabel:`Allocation Requests` section." msgstr "" @@ -7894,91 +8372,91 @@ msgstr "" msgid "Time off type form with all the information filled out for sick time off." msgstr "" -#: ../../content/applications/hr/time_off.rst:163 +#: ../../content/applications/hr/time_off.rst:165 msgid "Accrual plans" msgstr "" -#: ../../content/applications/hr/time_off.rst:165 +#: ../../content/applications/hr/time_off.rst:167 msgid "Some time off is earned through an accrual plan, meaning that for every specified amount of time an employee works (hour, day, week, etc), they earn or *accrue* a specified amount of time off." msgstr "" -#: ../../content/applications/hr/time_off.rst:169 +#: ../../content/applications/hr/time_off.rst:171 msgid "If an employee accrues a vacation day for every week they work, they would earn 0.2 vacation days for each hour they work. At the end of a forty (40) hour work week, they earn a whole vacation day (8 hours)." msgstr "" -#: ../../content/applications/hr/time_off.rst:174 +#: ../../content/applications/hr/time_off.rst:176 msgid "Create accrual plan" msgstr "" -#: ../../content/applications/hr/time_off.rst:176 +#: ../../content/applications/hr/time_off.rst:178 msgid "To create a new accrual plan, navigate to :menuselection:`Time Off app --> Configuration --> Accrual Plans`. Then, click the :guilabel:`Create` button, which reveals a blank accrual plan form." msgstr "" -#: ../../content/applications/hr/time_off.rst:179 +#: ../../content/applications/hr/time_off.rst:181 msgid "Enter the accrual plan name in the :guilabel:`Name` field. If the accrual plan only applies to a specific time off type, select it from the drop-down menu. If this accrual plan is available for all time off types, leave this field blank." msgstr "" -#: ../../content/applications/hr/time_off.rst:183 +#: ../../content/applications/hr/time_off.rst:185 msgid "Next, select how the :guilabel:`Level Transition` occurs, either :guilabel:`Immediately` or :guilabel:`After this accrual's period`. By default, the first level begins once the time off is approved if the time off is based on an accrual plan. If :guilabel:`Immediately` is selected, then the next level begins according to the time frame set on the level. If :guilabel:`After this accrual's period` is selected, the next level does not begin until the first level is completed according to the rules set on it." msgstr "" -#: ../../content/applications/hr/time_off.rst:193 +#: ../../content/applications/hr/time_off.rst:195 msgid "Rules must be created in order for the accrual plan to accrue time off." msgstr "" -#: ../../content/applications/hr/time_off.rst:195 +#: ../../content/applications/hr/time_off.rst:197 msgid "To create a new rule, click the :guilabel:`Add A New Level` button right beneath the word `Rules`, and a :guilabel:`Create Level` pop-up form appears." msgstr "" -#: ../../content/applications/hr/time_off.rst:198 +#: ../../content/applications/hr/time_off.rst:200 msgid "Fill out the following fields on the form:" msgstr "" -#: ../../content/applications/hr/time_off.rst:200 +#: ../../content/applications/hr/time_off.rst:202 msgid ":guilabel:`Start after (#) (time period) after allocation date`: enter the number and value of the time period that must pass before the employee starts to accumulate time off. The first value is numerical; enter a number in the first field." msgstr "" -#: ../../content/applications/hr/time_off.rst:204 +#: ../../content/applications/hr/time_off.rst:206 msgid "Then, select the type of time period using the drop-down menu in the second field. The options are: :guilabel:`day(s)`, :guilabel:`month(s)`, or :guilabel:`year(s)`." msgstr "" -#: ../../content/applications/hr/time_off.rst:206 +#: ../../content/applications/hr/time_off.rst:208 msgid ":guilabel:`Based on worked time`: tick this box if the accrual of time off is based on the time the employee has worked. If an employee takes time off that is *not* considered a worked day, Odoo will not count that day towards their accrual plan." msgstr "" -#: ../../content/applications/hr/time_off.rst:209 +#: ../../content/applications/hr/time_off.rst:211 msgid ":guilabel:`Rate (#) (time)`: enter the rate of time off that is accumulated. The first value is numerical; enter a number in the first field. Whole numbers are not necessary, any decimal value may be entered." msgstr "" -#: ../../content/applications/hr/time_off.rst:213 +#: ../../content/applications/hr/time_off.rst:215 msgid "Next, in the second field, select the type of time accrued using the drop-down menu. The options are either :guilabel:`Days` or :guilabel:`Hours`." msgstr "" -#: ../../content/applications/hr/time_off.rst:215 +#: ../../content/applications/hr/time_off.rst:217 msgid ":guilabel:`Frequency (X)`: select how often the employee accrues the time off for this rule using the drop-down menu. The options are :guilabel:`Daily`, :guilabel:`Weekly`, :guilabel:`Twice a month`, :guilabel:`Monthly`, :guilabel:`Twice a year`, or :guilabel:`Yearly`." msgstr "" -#: ../../content/applications/hr/time_off.rst:219 +#: ../../content/applications/hr/time_off.rst:221 msgid "Depending on the selection, more fields appear to specify exactly when the accrual renews." msgstr "" -#: ../../content/applications/hr/time_off.rst:222 +#: ../../content/applications/hr/time_off.rst:224 msgid "If the employee should accrue one vacation day for every week worked, the :guilabel:`Rate` is set to `1`, and the :guilabel:`Frequency` entry is set to `Frequency (Weekly) on (Friday)`. Only the :guilabel:`Frequency` and :guilabel:`Weekday` fields appear." msgstr "" -#: ../../content/applications/hr/time_off.rst:226 +#: ../../content/applications/hr/time_off.rst:228 msgid "If the employee should accrue ten (10)vacation days each year, and they receive these days every year on the first of January, the :guilabel:`Rate` is set to `10`, and the :guilabel:`Frequency` entry is set to `Frequency (Yearly) on the (1) of (January)`. The :guilabel:`Frequency`, :guilabel:`Date`, and :guilabel:`Month` fields appear." msgstr "" -#: ../../content/applications/hr/time_off.rst:231 +#: ../../content/applications/hr/time_off.rst:233 msgid ":guilabel:`Limit to`: enter a maximum amount of days the employee can accrue with this plan." msgstr "" -#: ../../content/applications/hr/time_off.rst:232 +#: ../../content/applications/hr/time_off.rst:234 msgid ":guilabel:`At the end of the calendar year, unused accruals will be`: select from the drop-down menu how unused time off is handled." msgstr "" -#: ../../content/applications/hr/time_off.rst:235 +#: ../../content/applications/hr/time_off.rst:237 msgid "The options are either :guilabel:`Transferred to the next year`, which rolls over unused time to the next calendar year, or :guilabel:`Lost`, which means any unused time off is gone." msgstr "" @@ -7986,7 +8464,7 @@ msgstr "" msgid "A level form with all the data filled out." msgstr "" -#: ../../content/applications/hr/time_off.rst:242 +#: ../../content/applications/hr/time_off.rst:244 msgid "When the form is filled out, click :guilabel:`Save & Close` to save the form and close the pop-up, or :guilabel:`Save & New` to save the form and create a new rule. Add as many levels as desired." msgstr "" @@ -7994,63 +8472,63 @@ msgstr "" msgid "An accrual form with all the entries filled out." msgstr "" -#: ../../content/applications/hr/time_off.rst:252 +#: ../../content/applications/hr/time_off.rst:254 msgid "Public holidays" msgstr "" -#: ../../content/applications/hr/time_off.rst:254 +#: ../../content/applications/hr/time_off.rst:256 msgid "Most countries have public or national holidays, and some companies may have specific days they are closed and/or give extra days as holidays." msgstr "" -#: ../../content/applications/hr/time_off.rst:257 +#: ../../content/applications/hr/time_off.rst:259 msgid "It is important to configure these days in Odoo, so employees are aware of the days they have off, and do not request time off on days that are already set as a public holiday (non-working days)." msgstr "" -#: ../../content/applications/hr/time_off.rst:261 +#: ../../content/applications/hr/time_off.rst:263 msgid "Create public holiday" msgstr "" -#: ../../content/applications/hr/time_off.rst:263 +#: ../../content/applications/hr/time_off.rst:265 msgid "To create a public holiday, navigate to :menuselection:`Time Off app --> Configuration --> Public Holidays`." msgstr "" -#: ../../content/applications/hr/time_off.rst:266 +#: ../../content/applications/hr/time_off.rst:268 msgid "All currently configured public holidays appear in a list view." msgstr "" -#: ../../content/applications/hr/time_off.rst:268 +#: ../../content/applications/hr/time_off.rst:270 msgid "Click the :guilabel:`Create` button, and a new line appears at the bottom of the list." msgstr "" -#: ../../content/applications/hr/time_off.rst:270 +#: ../../content/applications/hr/time_off.rst:272 msgid "Enter the following information:" msgstr "" -#: ../../content/applications/hr/time_off.rst:272 +#: ../../content/applications/hr/time_off.rst:274 msgid ":guilabel:`Name`: enter the name of the holiday." msgstr "" -#: ../../content/applications/hr/time_off.rst:273 +#: ../../content/applications/hr/time_off.rst:275 msgid ":guilabel:`Company`: if in a multi-company database, the current company populates this field by default. It is not possible to edit this field." msgstr "" -#: ../../content/applications/hr/time_off.rst:275 +#: ../../content/applications/hr/time_off.rst:277 msgid ":guilabel:`Start Date`: using the date and time picker, select the date and time that the holiday starts. By default, this field is configured for the current date. The start time is set according to the start time for the company (according to the :ref:`working times `). If the user's computer is set to a different time zone, the start time is adjusted according to the difference in the time zone compared to the company's time zone." msgstr "" -#: ../../content/applications/hr/time_off.rst:280 +#: ../../content/applications/hr/time_off.rst:282 msgid ":guilabel:`End Date`: using the date and time picker, select the date and time that the holiday ends. By default, this field is configured for the current date, and the time is set to the end time for the company (according to the :ref:`working times `). If the user's computer is set to a different time zone, the start time is adjusted according to the difference in the time zone compared to the company's time zone." msgstr "" -#: ../../content/applications/hr/time_off.rst:287 +#: ../../content/applications/hr/time_off.rst:289 msgid "A company is located in San Francisco, and the working times are 9:00 AM - 6:00 PM (an eight (8) hour work day with a one (1) hour lunch break). A user is located in New York, and their computer time zone is set to Eastern. When they create a Public Holiday, the start time appears as 12:00 PM - 9:00 PM, since the time zone is accounted for. If a different user is located in Los Angeles, and their computer time zone is set to Pacific, when they create a Public Holiday, the time appears as 9:00 AM - 6:00 PM." msgstr "" -#: ../../content/applications/hr/time_off.rst:294 +#: ../../content/applications/hr/time_off.rst:296 msgid ":guilabel:`Working Hours`: if the holiday should only apply to employees who have a specific set of working hours, select the working hours from the drop-down menu. If left blank, the holiday applies to all employees." msgstr "" -#: ../../content/applications/hr/time_off.rst:297 +#: ../../content/applications/hr/time_off.rst:299 msgid ":guilabel:`Work Entry Type`: if using the *Payroll* application, this field defines how the work entry for the holiday appears. Select the work entry type from the drop-down menu." msgstr "" @@ -8058,35 +8536,35 @@ msgstr "" msgid "The list of public holidays in the configuration menu." msgstr "" -#: ../../content/applications/hr/time_off.rst:309 +#: ../../content/applications/hr/time_off.rst:311 msgid "To view a color-coded schedule of both the user's time off, and/or the team managed by them, navigate to :menuselection:`Time Off app --> Overview`. This presents a calendar with the default filter of :guilabel:`My Team`, in a month view." msgstr "" -#: ../../content/applications/hr/time_off.rst:313 +#: ../../content/applications/hr/time_off.rst:315 msgid "To change the time period displayed, click on either the :guilabel:`Day`, :guilabel:`Week`, :guilabel:`Month`, or :guilabel:`Year` buttons to present the calendar in that corresponding view." msgstr "" -#: ../../content/applications/hr/time_off.rst:316 +#: ../../content/applications/hr/time_off.rst:318 msgid "Each team member is displayed on a line, and any time off they requested, regardless of the status (:guilabel:`Validated` or :guilabel:`To Approve`), appears on the calendar." msgstr "" -#: ../../content/applications/hr/time_off.rst:319 +#: ../../content/applications/hr/time_off.rst:321 msgid "Each employee is color-coded. The employee's color is selected at random and does not correspond to the type of time off they requested." msgstr "" -#: ../../content/applications/hr/time_off.rst:322 +#: ../../content/applications/hr/time_off.rst:324 msgid "The status of the time of is represented by the color of the request either appearing solid (:guilabel:`Validated`) or striped (:guilabel:`To Approve`)." msgstr "" -#: ../../content/applications/hr/time_off.rst:325 +#: ../../content/applications/hr/time_off.rst:327 msgid "The number of days or hours requested is written on the request (if there is enough space)." msgstr "" -#: ../../content/applications/hr/time_off.rst:327 +#: ../../content/applications/hr/time_off.rst:329 msgid "At the bottom of the calendar, a bar graph shows how many people are projected to be out on any given day. The number on the bar represents the number of employees out for those highlighted days." msgstr "" -#: ../../content/applications/hr/time_off.rst:330 +#: ../../content/applications/hr/time_off.rst:332 msgid "Hover over a time off entry to view the details for the specific time off entry. The total number of hours or days are listed, along with the start and end time of the time off." msgstr "" @@ -8094,156 +8572,156 @@ msgstr "" msgid "Overview of the user's team, with time off requests shown." msgstr "" -#: ../../content/applications/hr/time_off.rst:340 +#: ../../content/applications/hr/time_off.rst:342 msgid "Allocate time off" msgstr "" -#: ../../content/applications/hr/time_off.rst:342 +#: ../../content/applications/hr/time_off.rst:344 msgid "Once time off types and accrual plans have been configured, the next step is to allocate, or give, time off to employees. This section is only visible to users who have either :guilabel:`Time Off Officer` or :guilabel:`Administrator` access rights for the *Time Off* application." msgstr "" -#: ../../content/applications/hr/time_off.rst:346 +#: ../../content/applications/hr/time_off.rst:348 msgid "To create a new allocation, navigate to :menuselection:`Time Off app --> Approvals --> Allocations`." msgstr "" -#: ../../content/applications/hr/time_off.rst:348 +#: ../../content/applications/hr/time_off.rst:350 msgid "This presents a list of all current allocations, including their respective status." msgstr "" -#: ../../content/applications/hr/time_off.rst:350 +#: ../../content/applications/hr/time_off.rst:352 msgid "Click :guilabel:`Create` to allocate time off, and a blank allocation form appears." msgstr "" -#: ../../content/applications/hr/time_off.rst:352 +#: ../../content/applications/hr/time_off.rst:354 msgid "After entering a name for the allocation on the first blank field of the form, enter the following information:" msgstr "" -#: ../../content/applications/hr/time_off.rst:355 +#: ../../content/applications/hr/time_off.rst:357 msgid ":guilabel:`Time Off Type`: using the drop-down menu, select the type of time off that is being allocated to the employees." msgstr "" -#: ../../content/applications/hr/time_off.rst:357 +#: ../../content/applications/hr/time_off.rst:359 msgid ":guilabel:`Allocation Type`: select either :guilabel:`Regular Allocation` or :guilabel:`Accrual Allocation`." msgstr "" -#: ../../content/applications/hr/time_off.rst:359 +#: ../../content/applications/hr/time_off.rst:361 msgid ":guilabel:`Accrual Plan`: if :guilabel:`Accrual Allocation` is selected for the :guilabel:`Allocation Type`, the :guilabel:`Accrual Plan` field appears. Using the drop-down menu, select the accrual plan with which the allocation is associated. An accrual plan **must** be selected for an :guilabel:`Accrual Allocation`." msgstr "" -#: ../../content/applications/hr/time_off.rst:363 +#: ../../content/applications/hr/time_off.rst:365 msgid ":guilabel:`Validity Period/Start Date`: if :guilabel:`Regular Allocation` is selected for the :guilabel:`Allocation Type`, this field is labeled :guilabel:`Validity Period`." msgstr "" -#: ../../content/applications/hr/time_off.rst:366 +#: ../../content/applications/hr/time_off.rst:368 msgid "Using the calendar, select the beginning date for the allocation. If the allocation expires, select the expiration date in the next date field. If the time off does *not* expire, leave the second date field blank." msgstr "" -#: ../../content/applications/hr/time_off.rst:370 +#: ../../content/applications/hr/time_off.rst:372 msgid "If :guilabel:`Accrual Allocation` is selected for the :guilabel:`Allocation Type`, this field is labeled :guilabel:`Start Date`." msgstr "" -#: ../../content/applications/hr/time_off.rst:373 +#: ../../content/applications/hr/time_off.rst:375 msgid "Using the calendar picker, select the start date for the allocation. If the allocation expires, select the expiration date in the :guilabel:`Run until` field. If the time off does *not* expire, leave the :guilabel:`Run until` field blank." msgstr "" -#: ../../content/applications/hr/time_off.rst:376 +#: ../../content/applications/hr/time_off.rst:378 msgid ":guilabel:`Duration`: enter the amount of time that is being allocated to the employees. This field displays the time in either :guilabel:`Hours` or :guilabel:`Days`, depending on how the selected :ref:`Time Off Type ` is configured (in days or hours)." msgstr "" -#: ../../content/applications/hr/time_off.rst:379 +#: ../../content/applications/hr/time_off.rst:381 msgid ":guilabel:`Mode`: using the drop-down menu, select how the allocation is assigned. This selection determines who receives the time off allocation. The options are :guilabel:`By Employee`, :guilabel:`By Company`, :guilabel:`By Department`, or :guilabel:`By Employee Tag`." msgstr "" -#: ../../content/applications/hr/time_off.rst:383 +#: ../../content/applications/hr/time_off.rst:385 msgid "Depending on what was selected for the :guilabel:`Mode`, this following field is labeled either: :guilabel:`Employees`, :guilabel:`Company`, :guilabel:`Department`, or :guilabel:`Employee Tag`." msgstr "" -#: ../../content/applications/hr/time_off.rst:386 +#: ../../content/applications/hr/time_off.rst:388 msgid "Using the drop-down menu, indicate the specific employees, company, department, or employee tags who are receiving this time off." msgstr "" -#: ../../content/applications/hr/time_off.rst:389 +#: ../../content/applications/hr/time_off.rst:391 msgid "Multiple selections can be made for either :guilabel:`Employees` or :guilabel:`Employee Tag`." msgstr "" -#: ../../content/applications/hr/time_off.rst:391 +#: ../../content/applications/hr/time_off.rst:393 msgid "Only one selection can be made for the :guilabel:`Company` or :guilabel:`Department`." msgstr "" -#: ../../content/applications/hr/time_off.rst:392 +#: ../../content/applications/hr/time_off.rst:394 msgid ":guilabel:`Add a reason...`: if any description or note is necessary to explain the time off allocation, enter it in this field at the bottom of the form." msgstr "" -#: ../../content/applications/hr/time_off.rst:398 +#: ../../content/applications/hr/time_off.rst:400 msgid "Request time off" msgstr "" -#: ../../content/applications/hr/time_off.rst:400 +#: ../../content/applications/hr/time_off.rst:402 msgid "Once an employee has been allocated time off, a request to use the time off can be submitted. Time off can be requested in one of two ways, either from the :ref:`dashboard ` or from the :guilabel:`My Time Off` view." msgstr "" -#: ../../content/applications/hr/time_off.rst:404 +#: ../../content/applications/hr/time_off.rst:406 msgid "To access the dashboard, navigate to :menuselection:`Time Off app --> My Time Off --> Dashboard`. This is also the default view for the *Time Off* application." msgstr "" -#: ../../content/applications/hr/time_off.rst:407 +#: ../../content/applications/hr/time_off.rst:409 msgid "To access :guilabel:`My Time Off`, navigate to :menuselection:`Time Off app --> My Time Off --> My Time Off`. This presents a list view of all the time off requests for the employee." msgstr "" -#: ../../content/applications/hr/time_off.rst:410 +#: ../../content/applications/hr/time_off.rst:412 msgid "To create a new request for time off, click either the :guilabel:`New Time Off` button on the main *Time Off* dashboard, or the :guilabel:`Create` button in the :guilabel:`My Time Off` list view. Both buttons open a new time off request form." msgstr "" -#: ../../content/applications/hr/time_off.rst:416 +#: ../../content/applications/hr/time_off.rst:418 msgid ":guilabel:`Time Off Type`: select the type of time off being requested from the drop-down menu." msgstr "" -#: ../../content/applications/hr/time_off.rst:417 +#: ../../content/applications/hr/time_off.rst:419 msgid ":guilabel:`Dates`: enter the dates that the time off will fall under. There are two fields to populate, the :guilabel:`From` and :guilabel:`To` fields. Click on either the :guilabel:`From` or :guilabel:`To` field, and a calendar pop-up appears." msgstr "" -#: ../../content/applications/hr/time_off.rst:421 +#: ../../content/applications/hr/time_off.rst:423 msgid "Click on the start date, then click on the end date. The selected start and end dates appear in deep purple, and the dates between them appear in pale purple (if applicable)." msgstr "" -#: ../../content/applications/hr/time_off.rst:424 +#: ../../content/applications/hr/time_off.rst:426 msgid "If the time off requested is for a single day, click on the start date, then click the same date again for the end date." msgstr "" -#: ../../content/applications/hr/time_off.rst:427 +#: ../../content/applications/hr/time_off.rst:429 msgid "When the correct dates are selected/highlighted, click the :guilabel:`Apply` button." msgstr "" -#: ../../content/applications/hr/time_off.rst:429 +#: ../../content/applications/hr/time_off.rst:431 msgid "The dates now populate the :guilabel:`From` and :guilabel:`To` fields." msgstr "" -#: ../../content/applications/hr/time_off.rst:431 +#: ../../content/applications/hr/time_off.rst:433 msgid ":guilabel:`Half Day`: if the time off request is for a half day, tick this box. When this is selected, the :guilabel:`From` date field disappears, and is replaced with a drop-down menu. Select either :guilabel:`Morning` or :guilabel:`Afternoon` to indicate which half of the day is being requested." msgstr "" -#: ../../content/applications/hr/time_off.rst:435 +#: ../../content/applications/hr/time_off.rst:437 msgid ":guilabel:`Custom Hours`: if the time off requested is not a whole or half day, tick this box. A :guilabel:`From` and :guilabel:`To` field appears beneath this option if selected. Using the drop-down menu, select the start and end time for the time off request." msgstr "" -#: ../../content/applications/hr/time_off.rst:439 +#: ../../content/applications/hr/time_off.rst:441 msgid ":guilabel:`Duration`: this field updates automatically once the :guilabel:`Date` section is completed. If the :guilabel:`Date` section is modified, this section automatically updates to reflect the total time off requested. This field is in either hours or days, depending on the :guilabel:`Date` selections." msgstr "" -#: ../../content/applications/hr/time_off.rst:443 +#: ../../content/applications/hr/time_off.rst:445 msgid ":guilabel:`Description`: enter a description for the time off request. This should include any details that managers and approvers may need in order to approve the request." msgstr "" -#: ../../content/applications/hr/time_off.rst:445 +#: ../../content/applications/hr/time_off.rst:447 msgid ":guilabel:`Supporting Document`: this field only appears if the :guilabel:`Time Off Type` selected allows for the attachments of documents. Click the :guilabel:`Attach File` button, and a file explorer window appears." msgstr "" -#: ../../content/applications/hr/time_off.rst:449 +#: ../../content/applications/hr/time_off.rst:451 msgid "Navigate to the file(s) to attach, then click the :guilabel:`Open` button. The files then appear on the time off request form. Multiple documents can be attached, if necessary." msgstr "" -#: ../../content/applications/hr/time_off.rst:452 -#: ../../content/applications/hr/time_off.rst:492 +#: ../../content/applications/hr/time_off.rst:454 +#: ../../content/applications/hr/time_off.rst:494 msgid "When the form is complete, click the :guilabel:`Save` button to save the information, and submit the request." msgstr "" @@ -8251,43 +8729,43 @@ msgstr "" msgid "A time off request form filled out for an employee home sick for two days with the flu." msgstr "" -#: ../../content/applications/hr/time_off.rst:462 +#: ../../content/applications/hr/time_off.rst:464 msgid "Request allocation" msgstr "" -#: ../../content/applications/hr/time_off.rst:464 +#: ../../content/applications/hr/time_off.rst:466 msgid "If an employee has used all their time off, or is going to run out of time off, they can request an allocation for additional time. Allocations can be requested in one of two ways, either from the :ref:`dashboard ` or the :guilabel:`My Allocations` view." msgstr "" -#: ../../content/applications/hr/time_off.rst:468 +#: ../../content/applications/hr/time_off.rst:470 msgid "To access the dashboard, navigate to the :menuselection:`Time Off app --> My Time Off --> Dashboard`. This is also the default view for the *Time Off* application." msgstr "" -#: ../../content/applications/hr/time_off.rst:471 +#: ../../content/applications/hr/time_off.rst:473 msgid "To access :guilabel:`My Allocations`, navigate to the :menuselection:`Time Off app --> My Time Off --> My Allocations`. This presents a list view of all the allocations for the employee." msgstr "" -#: ../../content/applications/hr/time_off.rst:474 +#: ../../content/applications/hr/time_off.rst:476 msgid "To create a new allocation request, click either the :guilabel:`Allocation Request` button on the main *Time Off* dashboard, or the :guilabel:`Create` button in the :guilabel:`My Allocations` list view. Both buttons open a new allocation request form." msgstr "" -#: ../../content/applications/hr/time_off.rst:478 +#: ../../content/applications/hr/time_off.rst:480 msgid "After entering a name for the allocation in the first blank line on the form, enter the following information:" msgstr "" -#: ../../content/applications/hr/time_off.rst:481 +#: ../../content/applications/hr/time_off.rst:483 msgid ":guilabel:`Time Off Type`: select the type of time off being requested for the allocation from the drop-down menu." msgstr "" -#: ../../content/applications/hr/time_off.rst:483 +#: ../../content/applications/hr/time_off.rst:485 msgid ":guilabel:`Validity Period`: the current date populates the start date by default. If there is no expiration on the time off type, there is no date populated as the end date. If the time off type has an expiration date, the date automatically populates the end date field once the form is saved." msgstr "" -#: ../../content/applications/hr/time_off.rst:487 +#: ../../content/applications/hr/time_off.rst:489 msgid ":guilabel:`Duration`: enter the amount of time being requested. The format (either days or hours) is in the same format as the time off type." msgstr "" -#: ../../content/applications/hr/time_off.rst:489 +#: ../../content/applications/hr/time_off.rst:491 msgid ":guilabel:`Add a reason...`: enter a description for the allocation request. This should include any details that managers and approvers may need in order to approve the request." msgstr "" @@ -8296,72 +8774,72 @@ msgid "An allocation request form filled out for an employee requesting an addit "sick time." msgstr "" -#: ../../content/applications/hr/time_off.rst:501 +#: ../../content/applications/hr/time_off.rst:503 msgid "Approvals" msgstr "" -#: ../../content/applications/hr/time_off.rst:503 +#: ../../content/applications/hr/time_off.rst:505 msgid "Most requests for time off and allocations need to go through the approval process, prior to the time off being allocated, and then granted to an employee. Requests either need one or two approvals, depending on how the specific type of time off is configured." msgstr "" -#: ../../content/applications/hr/time_off.rst:507 +#: ../../content/applications/hr/time_off.rst:509 msgid "Only users who can approve allocation and time off requests have the :guilabel:`Approvals` section visible in the *Time Off* application." msgstr "" -#: ../../content/applications/hr/time_off.rst:511 +#: ../../content/applications/hr/time_off.rst:513 msgid "Approve allocations" msgstr "" -#: ../../content/applications/hr/time_off.rst:513 +#: ../../content/applications/hr/time_off.rst:515 msgid "To view allocations that need approval, navigate to :menuselection:`Time Off app --> Approvals --> Allocations`. The only allocations visible on this list are for employees the user has either :guilabel:`Time Off Officer` or :guilabel:`Administrator` access rights for in the *Time Off* application." msgstr "" -#: ../../content/applications/hr/time_off.rst:518 +#: ../../content/applications/hr/time_off.rst:520 msgid "The default filters that are configured to be in place when navigating to the :guilabel:`Allocations` list are :guilabel:`My Team` and :guilabel:`Active Employee`. This *only* presents employees on the user's team (who they manage) and active employees. Inactive users are not shown." msgstr "" -#: ../../content/applications/hr/time_off.rst:523 +#: ../../content/applications/hr/time_off.rst:525 msgid "The left side of the screen has various grouping options to narrow down the presented allocation requests." msgstr "" -#: ../../content/applications/hr/time_off.rst:526 +#: ../../content/applications/hr/time_off.rst:528 msgid "The options are :guilabel:`To Approve`, :guilabel:`To Submit`, :guilabel:`Refused`, and :guilabel:`Approved`." msgstr "" -#: ../../content/applications/hr/time_off.rst:529 +#: ../../content/applications/hr/time_off.rst:531 msgid "To view all allocation requests, click :guilabel:`All`." msgstr "" -#: ../../content/applications/hr/time_off.rst:531 +#: ../../content/applications/hr/time_off.rst:533 msgid "It is also possible to display allocation requests by department. Click on the department to only present allocations for that specific department." msgstr "" -#: ../../content/applications/hr/time_off.rst:535 +#: ../../content/applications/hr/time_off.rst:537 msgid "The groupings on the left side only present allocation requests that fall under the default filters of :guilabel:`My Team` and :guilabel:`Active Employee`. Only the statuses for allocation requests that fall under those filters are presented on the left side." msgstr "" -#: ../../content/applications/hr/time_off.rst:539 +#: ../../content/applications/hr/time_off.rst:541 msgid "For example, if there are no requests with a status of :guilabel:`To Submit`, that status option does not appear in the left-hand side." msgstr "" -#: ../../content/applications/hr/time_off.rst:542 +#: ../../content/applications/hr/time_off.rst:544 msgid "All departments for the user's employees appear in the list. If there are no allocation requests that fall under that department matching the pre-configured filters, the list is blank." msgstr "" -#: ../../content/applications/hr/time_off.rst:545 +#: ../../content/applications/hr/time_off.rst:547 msgid "It is always possible to remove any of the pre-configured filters, by clicking the :guilabel:`✖️ (remove)` icon on the specific filter to remove it." msgstr "" -#: ../../content/applications/hr/time_off.rst:548 -#: ../../content/applications/hr/time_off.rst:597 +#: ../../content/applications/hr/time_off.rst:550 +#: ../../content/applications/hr/time_off.rst:599 msgid "The status column displays the status of each request, with the status highlighted in a specific color." msgstr "" -#: ../../content/applications/hr/time_off.rst:551 +#: ../../content/applications/hr/time_off.rst:553 msgid "The :guilabel:`To Approve` requests are highlighted in yellow, :guilabel:`Approved` requests are highlighted in green, :guilabel:`To Submit` (drafts) requests are highlighted in blue, and the :guilabel:`Refused` requests are highlighted in gray." msgstr "" -#: ../../content/applications/hr/time_off.rst:555 +#: ../../content/applications/hr/time_off.rst:557 msgid "To approve an allocation request, click :guilabel:`✔ Validate` at the end of the line, to refuse a request, click :guilabel:`✖️ Refuse`." msgstr "" @@ -8369,47 +8847,47 @@ msgstr "" msgid "Allocations with the filter, groupings, and status sections highlighted." msgstr "" -#: ../../content/applications/hr/time_off.rst:562 +#: ../../content/applications/hr/time_off.rst:564 msgid "If more details are needed, click anywhere on the allocation request line (except for :guilabel:`✔ Validate` and :guilabel:`✖️ Refuse`) to view the request in detail." msgstr "" -#: ../../content/applications/hr/time_off.rst:565 +#: ../../content/applications/hr/time_off.rst:567 msgid "Depending on the rights of the user, changes can be made on the allocation request form that appears. To modify the request, click the :guilabel:`Edit` button, make any desired changes, then click :guilabel:`Save`." msgstr "" -#: ../../content/applications/hr/time_off.rst:569 +#: ../../content/applications/hr/time_off.rst:571 msgid "It is also possible to approve or refuse the request from this form. Click the :guilabel:`Validate` button to approve, or the :guilabel:`Refuse` button to refuse the request." msgstr "" -#: ../../content/applications/hr/time_off.rst:575 +#: ../../content/applications/hr/time_off.rst:577 msgid "Approve time off" msgstr "" -#: ../../content/applications/hr/time_off.rst:577 +#: ../../content/applications/hr/time_off.rst:579 msgid "To view time off requests that need approval, navigate to :menuselection:`Time Off app --> Approvals --> Time Off`. The only time off requests visible on this list are for employees the user has either :guilabel:`Time Off Officer` or :guilabel:`Administrator` access rights for the *Time Off* application." msgstr "" -#: ../../content/applications/hr/time_off.rst:582 +#: ../../content/applications/hr/time_off.rst:584 msgid "The default filters in the :guilabel:`Time Off` list are :guilabel:`To Approve`, :guilabel:`My Team`, :guilabel:`Active Employee`, and :guilabel:`Active Time Off`. This only presents time off requests that need to be approved for current employees on the user's team, for requests that are active and *not* in a draft mode." msgstr "" -#: ../../content/applications/hr/time_off.rst:587 +#: ../../content/applications/hr/time_off.rst:589 msgid "The left side of the screen has various grouping options to narrow down the presented time off requests. Since only time off requests that need to be approved are shown, the only status options are :guilabel:`All` and :guilabel:`To Approve`." msgstr "" -#: ../../content/applications/hr/time_off.rst:591 +#: ../../content/applications/hr/time_off.rst:593 msgid "To view requests with other statuses, first remove the :guilabel:`To Approve` filter, by clicking the :guilabel:`✖️ (remove)` icon next to the :guilabel:`To Approve` filter to remove it." msgstr "" -#: ../../content/applications/hr/time_off.rst:594 +#: ../../content/applications/hr/time_off.rst:596 msgid "To display time off requests for specific departments, click on the department on the left-hand side. Only requests within the selected department are then presented." msgstr "" -#: ../../content/applications/hr/time_off.rst:600 +#: ../../content/applications/hr/time_off.rst:602 msgid "The :guilabel:`To Approve` requests are highlighted in yellow, and are the only ones that appear in the list by default. If the :guilabel:`To Approve` filter is removed, then all statuses appear. :guilabel:`Approved` requests are highlighted in green, :guilabel:`To Submit` (drafts) requests are highlighted in blue, and the :guilabel:`Refused` requests are highlighted in gray." msgstr "" -#: ../../content/applications/hr/time_off.rst:605 +#: ../../content/applications/hr/time_off.rst:607 msgid "To approve a time off request, click :guilabel:`👍 Approve` at the end of the line, to refuse a request, click :guilabel:`✖️ Refuse`." msgstr "" @@ -8417,72 +8895,72 @@ msgstr "" msgid "Time off requests with the filter, groupings, and status sections highlighted." msgstr "" -#: ../../content/applications/hr/time_off.rst:612 +#: ../../content/applications/hr/time_off.rst:614 msgid "If more details are needed, click anywhere on the time off request line (except for :guilabel:`👍 Approve` and :guilabel:`✖️ Refuse`) to load the time off request form. Depending on the rights of the user, changes can be made." msgstr "" -#: ../../content/applications/hr/time_off.rst:616 +#: ../../content/applications/hr/time_off.rst:618 msgid "To modify the request, click the :guilabel:`Edit` button, make any desired changes, then click :guilabel:`Save`." msgstr "" -#: ../../content/applications/hr/time_off.rst:619 +#: ../../content/applications/hr/time_off.rst:621 msgid "It is also possible to approve or refuse the request from this form. Click the :guilabel:`Approve` button to approve, or the :guilabel:`Refuse` button to refuse the request." msgstr "" -#: ../../content/applications/hr/time_off.rst:623 -#: ../../content/applications/hr/time_off.rst:674 +#: ../../content/applications/hr/time_off.rst:625 +#: ../../content/applications/hr/time_off.rst:676 msgid "My time off" msgstr "" -#: ../../content/applications/hr/time_off.rst:625 +#: ../../content/applications/hr/time_off.rst:627 msgid "The :guilabel:`My Time Off` section of the *Time Off* application contains the time off dashboard, as well as the user's time off requests and allocations." msgstr "" -#: ../../content/applications/hr/time_off.rst:631 +#: ../../content/applications/hr/time_off.rst:633 msgid "Dashboard" msgstr "" -#: ../../content/applications/hr/time_off.rst:633 +#: ../../content/applications/hr/time_off.rst:635 msgid "All users have access to the time off dashboard, which is the default view in the *Time Off* application. The dashboard can also be accessed at any point in the application by navigating to :menuselection:`Time Off app --> My Time Off --> Dashboard`." msgstr "" -#: ../../content/applications/hr/time_off.rst:637 +#: ../../content/applications/hr/time_off.rst:639 msgid "The current year is displayed, and the current day is highlighted in red." msgstr "" -#: ../../content/applications/hr/time_off.rst:639 +#: ../../content/applications/hr/time_off.rst:641 msgid "To change the view, click on the desired button at the top. The options are :guilabel:`Day`, :guilabel:`Week`, :guilabel:`Month`, or :guilabel:`Year` (the default)." msgstr "" -#: ../../content/applications/hr/time_off.rst:642 +#: ../../content/applications/hr/time_off.rst:644 msgid "To change the presented dates, click the left and right arrows on either side of the :guilabel:`Today` button. The calendar view adjusts in increments of the presented view." msgstr "" -#: ../../content/applications/hr/time_off.rst:645 +#: ../../content/applications/hr/time_off.rst:647 msgid "For example, if :guilabel:`Week` is selected, the arrows adjust the view by one week." msgstr "" -#: ../../content/applications/hr/time_off.rst:647 +#: ../../content/applications/hr/time_off.rst:649 msgid "To change the view at any point to a view that includes the current date, click the :guilabel:`Today` button." msgstr "" -#: ../../content/applications/hr/time_off.rst:650 +#: ../../content/applications/hr/time_off.rst:652 msgid "Above the calendar view is a summary of the users time off balances. Every time off type that has been allocated appears in its own summary box. Each summary lists the type of time off, the corresponding icon, the current available balance (in hours or days), and an expiration date (if applicable)." msgstr "" -#: ../../content/applications/hr/time_off.rst:655 +#: ../../content/applications/hr/time_off.rst:657 msgid "The legend on the right side of the calendar view displays the various time off types, with their corresponding colors. The status of the time off requests are shown as well." msgstr "" -#: ../../content/applications/hr/time_off.rst:658 +#: ../../content/applications/hr/time_off.rst:660 msgid "Time off that has been validated appears in a solid color (in the color specified in the Time Off Types part of the legend). Time off requests that still need to be approved appear with white stripes in the color. Refused time off requests have a colored line through the dates." msgstr "" -#: ../../content/applications/hr/time_off.rst:662 +#: ../../content/applications/hr/time_off.rst:664 msgid "New time off requests can be made from the dashboard. Click the :guilabel:`New Time Off` button at the top of the dashboard, and a new :ref:`time off form ` appears." msgstr "" -#: ../../content/applications/hr/time_off.rst:665 +#: ../../content/applications/hr/time_off.rst:667 msgid "New allocation requests can also be made from the dashboard. Click the :guilabel:`Allocation Request` button at the top of the dashboard to request more time off, and a new :ref:`allocation form ` appears." msgstr "" @@ -8490,59 +8968,59 @@ msgstr "" msgid "Time off dashboard view with the legend, time off summaries, and view buttons highlighted." msgstr "" -#: ../../content/applications/hr/time_off.rst:676 +#: ../../content/applications/hr/time_off.rst:678 msgid "To view a list of all the user's time off requests, navigate to :menuselection:`Time Off app --> My Time Off --> My Time Off`. Here, all time off requests appear in a list view, both past and present." msgstr "" -#: ../../content/applications/hr/time_off.rst:680 +#: ../../content/applications/hr/time_off.rst:682 msgid "Other than the employee's name, the list includes the following information for each request: the :guilabel:`Time Off Type`, :guilabel:`Description`, :guilabel:`Start Date`, :guilabel:`End Date`, :guilabel:`Duration`, and the :guilabel:`Status`." msgstr "" -#: ../../content/applications/hr/time_off.rst:684 +#: ../../content/applications/hr/time_off.rst:686 msgid "A new time off request can be made from this view. Click the :guilabel:`Create` button to :ref:`request time off `." msgstr "" -#: ../../content/applications/hr/time_off.rst:688 +#: ../../content/applications/hr/time_off.rst:690 msgid "My allocations" msgstr "" -#: ../../content/applications/hr/time_off.rst:690 +#: ../../content/applications/hr/time_off.rst:692 msgid "To view a list of all the users allocations, navigate to :menuselection:`Time Off app --> My Time Off --> My Allocations`. All allocations and requested allocations appear in a list view." msgstr "" -#: ../../content/applications/hr/time_off.rst:693 +#: ../../content/applications/hr/time_off.rst:695 msgid "The information presented includes: the :guilabel:`Time Off Type`, :guilabel:`Description`, :guilabel:`Duration`, :guilabel:`Allocation Type`, and the :guilabel:`Status`." msgstr "" -#: ../../content/applications/hr/time_off.rst:696 +#: ../../content/applications/hr/time_off.rst:698 msgid "A new allocation request can be made from this view, as well. Click the :guilabel:`Create` button to :ref:`request an allocation `." msgstr "" -#: ../../content/applications/hr/time_off.rst:702 +#: ../../content/applications/hr/time_off.rst:704 msgid "The reporting feature allows users to view time off for their team, either by employee or type of time off. This allows users to see which employees are taking time off, how much time off they are taking, and what time off types are being used." msgstr "" -#: ../../content/applications/hr/time_off.rst:707 +#: ../../content/applications/hr/time_off.rst:709 msgid "By employee" msgstr "" -#: ../../content/applications/hr/time_off.rst:709 +#: ../../content/applications/hr/time_off.rst:711 msgid "To view a report of employee time off requests, navigate to :menuselection:`Time Off app --> Reporting --> by Employee`." msgstr "" -#: ../../content/applications/hr/time_off.rst:712 +#: ../../content/applications/hr/time_off.rst:714 msgid "The default report is a stacked bar chart with the filters of :guilabel:`Active Employee` and :guilabel:`Type` in place." msgstr "" -#: ../../content/applications/hr/time_off.rst:715 +#: ../../content/applications/hr/time_off.rst:717 msgid "Each employee is displayed in their own column, with the bar displaying how many days of each type of time off type they requested." msgstr "" -#: ../../content/applications/hr/time_off.rst:718 +#: ../../content/applications/hr/time_off.rst:720 msgid "The report can be displayed in other ways. Click the various options at the top of the report to view the data differently." msgstr "" -#: ../../content/applications/hr/time_off.rst:721 +#: ../../content/applications/hr/time_off.rst:723 msgid "The graph options are :guilabel:`Bar Chart`, :guilabel:`Line Chart`, or :guilabel:`Pie Chart`. The :guilabel:`Bar Chart` includes an option to present the data :guilabel:`Stacked`. Both the :guilabel:`Bar Chart` and :guilabel:`Line Chart` have options to present the data in either :guilabel:`Descending` or :guilabel:`Ascending` order." msgstr "" @@ -8550,19 +9028,19 @@ msgstr "" msgid "Report of time off, shown by each employee in a stacked bar chart." msgstr "" -#: ../../content/applications/hr/time_off.rst:731 +#: ../../content/applications/hr/time_off.rst:733 msgid "By type" msgstr "" -#: ../../content/applications/hr/time_off.rst:733 +#: ../../content/applications/hr/time_off.rst:735 msgid "To view a list of approved time off, organized by time off type, navigate to :menuselection:`Time Off app --> Reporting --> by Type`. This shows each time off type in its own section." msgstr "" -#: ../../content/applications/hr/time_off.rst:736 +#: ../../content/applications/hr/time_off.rst:738 msgid "Click on a time off type to expand the list. Each request is listed, with the following information displayed: the :guilabel:`Employee`, :guilabel:`Number of Days`, :guilabel:`Request Type`, :guilabel:`Start Date`, :guilabel:`End Date`, :guilabel:`Status`, and the :guilabel:`Description`." msgstr "" -#: ../../content/applications/hr/time_off.rst:740 +#: ../../content/applications/hr/time_off.rst:742 msgid "The default filters in place for this report are :guilabel:`Approved Requests`, :guilabel:`Active Employee`, the :guilabel:`Current Year`, and the :guilabel:`Type`." msgstr "" diff --git a/locale/sources/inventory_and_mrp.pot b/locale/sources/inventory_and_mrp.pot index 8aec2f7c4..0e3eced03 100644 --- a/locale/sources/inventory_and_mrp.pot +++ b/locale/sources/inventory_and_mrp.pot @@ -8,7 +8,7 @@ msgid "" msgstr "" "Project-Id-Version: Odoo 17.0\n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2024-03-08 12:48+0000\n" +"POT-Creation-Date: 2024-03-25 16:01+0000\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME \n" "Language-Team: LANGUAGE \n" @@ -214,112 +214,363 @@ msgid "To apply the inventory adjustment, click the green :guilabel:`✅ Apply` msgstr "" #: ../../content/applications/inventory_and_mrp/barcode/operations/barcode_nomenclature.rst:3 -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/cancel.rst:6 -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/invoicing.rst:8 -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/label_type.rst:6 -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/labels.rst:6 -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/third_party_shipper.rst:8 -msgid "Overview" +msgid "Default barcode nomenclature" msgstr "" -#: ../../content/applications/inventory_and_mrp/barcode/operations/barcode_nomenclature.rst:5 -msgid "There are different situations in which barcode nomenclatures can be useful. A well-known use case is the one of a point of sale which sells products in bulk, in which the customers will scale their products themselves and get the printed barcode to stick on the product. This barcode will contain the weight of the product and help compute the price accordingly." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/barcode/operations/barcode_nomenclature.rst:13 -msgid "Create a Barcode Nomenclature" +#: ../../content/applications/inventory_and_mrp/barcode/operations/barcode_nomenclature.rst:10 +msgid "*Barcode nomenclatures* define how barcodes are recognized and categorized. When a barcode is scanned, it is associated to the **first** rule with a matching pattern. The pattern syntax is described in Odoo's nomenclature list using a regular expression, and a barcode is successfully read by Odoo if its prefix and/or length matches the one defined in the barcode's rule." msgstr "" #: ../../content/applications/inventory_and_mrp/barcode/operations/barcode_nomenclature.rst:15 -msgid "Odoo supports Barcode Nomenclatures, which determine the mapping and interpretation of the encoded information. You can configure your barcode nomenclature being in :ref:`developer mode `. To do so, go to :menuselection:`Inventory --> Configuration --> Barcode Nomenclature`." +msgid "Odoo *Barcode* supports UPC (Universal Product Code), EAN (European Article Number), and GS1 encoding. The pre-configured nomenclatures in Odoo are *Default Nomenclature* and *Default GS1 Nomenclature*. The default nomenclature uses |UPC| and |EAN| encoding, and supports |UPC|/|EAN| conversion." msgstr "" -#: ../../content/applications/inventory_and_mrp/barcode/operations/barcode_nomenclature.rst:20 -msgid "You can create a barcode nomenclature from there, and then add a line to create your first rule." +#: ../../content/applications/inventory_and_mrp/barcode/operations/barcode_nomenclature.rst:21 +msgid "|UPC| and |EAN| barcodes **must** be `purchased from GS1 `_ to use these barcodes. GS1 is the **only** official provider of |UPC|/|EAN| and GS1 |GTINs| in the world." msgstr "" -#: ../../content/applications/inventory_and_mrp/barcode/operations/barcode_nomenclature.rst:26 -msgid "The first step is to specify the **rule name**, for example Weight Barcode with 3 Decimals. You then have to specify the type for barcode nomenclature, in our case it will be Weighted Product." +#: ../../content/applications/inventory_and_mrp/barcode/operations/barcode_nomenclature.rst:28 +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:32 +msgid "Set up barcode nomenclature" msgstr "" -#: ../../content/applications/inventory_and_mrp/barcode/operations/barcode_nomenclature.rst:33 -msgid "The Barcode Pattern is a regular expression that defines the structure of the barcode. In this example 21 defines the products on which the rule will be applied, those are the numbers by which the product barcode should start. The 5 “dots” are the following numbers of the product barcode and are there simply to identify the product in question. The “N” define a number and the “D” define the decimals." +#: ../../content/applications/inventory_and_mrp/barcode/operations/barcode_nomenclature.rst:30 +msgid "To use default nomenclature, navigate to :menuselection:`Inventory app --> Configuration --> Settings`. Under the :guilabel:`Barcode` section, click the checkbox next to :guilabel:`Barcode Scanner` to enable barcodes. Doing so installs the *Barcode* app in the database." msgstr "" -#: ../../content/applications/inventory_and_mrp/barcode/operations/barcode_nomenclature.rst:40 -msgid "The encoding allows to specify the barcode encoding on which the rule should be applied." +#: ../../content/applications/inventory_and_mrp/barcode/operations/barcode_nomenclature.rst:34 +msgid "Next, ensure that the :guilabel:`Default Nomenclature` setting is selected in the :guilabel:`Barcode Nomenclature` field. Then, click :guilabel:`Save`." msgstr "" -#: ../../content/applications/inventory_and_mrp/barcode/operations/barcode_nomenclature.rst:44 -msgid "You can define different rules and order their priority thanks to the sequence. The first rule which matches the scanned barcode will be applied." +#: ../../content/applications/inventory_and_mrp/barcode/operations/barcode_nomenclature.rst:-1 +msgid "Enabled barcode setting with Default Nomenclature selected." msgstr "" -#: ../../content/applications/inventory_and_mrp/barcode/operations/barcode_nomenclature.rst:49 -msgid "Configure your Product" +#: ../../content/applications/inventory_and_mrp/barcode/operations/barcode_nomenclature.rst:41 +msgid "Once the nomenclature is saved and selected, the :menuselection:`Barcode Nomenclatures` settings can be accessed, via a hidden menu that is **only** discoverable after enabling :ref:`developer mode `." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/barcode_nomenclature.rst:45 +msgid "Once developer mode is enabled, navigate to :menuselection:`Inventory app --> Configuration --> Barcode Nomenclatures` menu, and select :guilabel:`Default Nomenclature`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/barcode_nomenclature.rst:48 +msgid "From this page, the :guilabel:`Barcode Nomenclature` is specified at the top as the `Default Nomenclature`." msgstr "" #: ../../content/applications/inventory_and_mrp/barcode/operations/barcode_nomenclature.rst:51 -msgid "The barcode of the product should start by “21”;" +msgid "Under that, the :guilabel:`UPC/EAN Conversion` field is set to :guilabel:`Always`, by default. This setting determines if a |UPC|/|EAN| barcode should be automatically converted one way or another when trying to match a rule with the other encoding." msgstr "" -#: ../../content/applications/inventory_and_mrp/barcode/operations/barcode_nomenclature.rst:52 -msgid "The 5 “dots” are the other numbers of your product barcode, allowing to identify the product;" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/barcode/operations/barcode_nomenclature.rst:53 -msgid "The barcode should contain 0’s where you did defined D’s or N’s. In our case we need to set 5 zeros because we configured “21…..{NNDDD}”;" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/barcode/operations/barcode_nomenclature.rst:54 -msgid "In EAN-13, the last number is a check number, use an EAN13 generator to know which digit it should be in your case." +#: ../../content/applications/inventory_and_mrp/barcode/operations/barcode_nomenclature.rst:55 +msgid "The other available options for this field are :guilabel:`Never`, :guilabel:`EAN-13 to UPC-A`, and :guilabel:`UPC-A to EAN-13`." msgstr "" #: ../../content/applications/inventory_and_mrp/barcode/operations/barcode_nomenclature.rst:59 -msgid "In case you weight 1,5 Kg of pasta, the balance will print you the following barcode 2112345015002. If you scan this barcode in your POS or when receiving products in your barcode application, Odoo will automatically create a new line for the Pasta product for a quantity of 1.5 Kg. For the point of sale, a price depending on the quantity will also be computed." +msgid "For |UPC|/|EAN| conversion to work for every barcode scanned, the setting in the :guilabel:`UPC/EAN Conversion` field **must** be set to :guilabel:`Always`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/barcode_nomenclature.rst:62 +msgid "The last field at the top of the page is the :guilabel:`Is GS1 Nomenclature` field. For the :guilabel:`Default Nomenclature`, this field should remain unchecked. This is because the :guilabel:`Default Nomenclature` uses |UPC| and |EAN| encoding, *not* GS1 encoding." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/barcode_nomenclature.rst:-1 +msgid "Default Nomenclature page setting fields." msgstr "" #: ../../content/applications/inventory_and_mrp/barcode/operations/barcode_nomenclature.rst:70 -msgid "Rule Types" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/barcode/operations/barcode_nomenclature.rst:72 -msgid "**Priced Product**: allows you to identify the product and specify its price, used in POS." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/barcode/operations/barcode_nomenclature.rst:73 -msgid "**Discounted Product**: allows you to create one barcode per applied discount. You can then scan your product in the POS and then scan the discount barcode, discount will be applied on the normal price of the product." +msgid "Further down the page, there is a list showcasing the :guilabel:`Rule Name`, :guilabel:`Type`, :guilabel:`Encoding`, and :guilabel:`Barcode Pattern` for the *rules* and *barcode patterns* that Odoo supports for the default nomenclature." msgstr "" #: ../../content/applications/inventory_and_mrp/barcode/operations/barcode_nomenclature.rst:74 -msgid "**Weighted Product**: allows you to identify the product and specify its weight, used in both POS (in which the price is computed based on the weight) and in inventory." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/barcode/operations/barcode_nomenclature.rst:75 -msgid "**Client**: allows you to identify the customer, for example used with loyalty program." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/barcode/operations/barcode_nomenclature.rst:76 -msgid "**Cashier**: allows you to identify the cashier when entering the POS." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/barcode/operations/barcode_nomenclature.rst:77 -msgid "**Location**: allows you to identify the location on a transfer when multi-location is activated." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/barcode/operations/barcode_nomenclature.rst:78 -msgid "**Package**: allows you to identify packages on a transfer when packages are activated." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/barcode/operations/barcode_nomenclature.rst:79 -msgid "**Credit Card**: doesn’t need manual modification, exists for data from the Mercury module." +msgid "The :ref:`default nomenclature list ` contains all the information that can be condensed with a |UPC|/|EAN| barcode." msgstr "" #: ../../content/applications/inventory_and_mrp/barcode/operations/barcode_nomenclature.rst:80 -msgid "**Unit Product**: allows you to identify a product for both POS and transfers." +msgid "Use UPC/EAN barcodes in Odoo" msgstr "" -#: ../../content/applications/inventory_and_mrp/barcode/operations/barcode_nomenclature.rst:83 -msgid "When the barcode pattern contains .*, it means that it can contain any number of characters, those characters being any number." +#: ../../content/applications/inventory_and_mrp/barcode/operations/barcode_nomenclature.rst:82 +msgid "For product identification using |UPC|/|EAN| barcodes in Odoo, businesses **must** obtain `barcodes `_ purchased directly from GS1." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/barcode_nomenclature.rst:86 +msgid "The |UPC| and |EAN| barcode formats are predominantly used in their own regions. |UPC| is used only in the United States and Canada, while |EAN| is used everywhere else globally." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/barcode_nomenclature.rst:89 +msgid "A |UPC| is usually a 12-digit barcode used to identify most products, while |EAN| barcodes use 13-digit barcodes to identify products." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/barcode_nomenclature.rst:92 +msgid "|UPC| codes can be converted to |EAN| by prefixing them with a zero. In Odoo, by default, |UPC|/|EAN| barcodes are automatically converted one way or another when trying to match a rule with the other encoding." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/barcode_nomenclature.rst:96 +msgid "Refer to the :ref:`default nomenclature list ` to see a comprehensive list of all barcode patterns and rules to follow." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/barcode_nomenclature.rst:100 +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:96 +msgid "Create rules" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/barcode_nomenclature.rst:102 +msgid "|UPC| and |EAN| barcodes contain specific information in the barcode. Scanning these codes from the :ref:`default nomenclature list ` automatically fills corresponding data in the Odoo database." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/barcode_nomenclature.rst:106 +msgid "Adding new barcode rules to this list ensures that non-standard (:dfn:`user-created`) formats are interpreted accurately." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/barcode_nomenclature.rst:109 +msgid "To create new rules, first activate :ref:`developer mode `. Then, navigate to :menuselection:`Inventory app --> Configuration --> Barcode Nomenclatures`. Select the :guilabel:`Default Nomenclature` list item." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/barcode_nomenclature.rst:113 +msgid "On the :guilabel:`Default Nomenclature` page, select :guilabel:`Add a line` at the bottom of the table, which opens a :guilabel:`Create Rules` pop-up window to create a new rule." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/barcode_nomenclature.rst:-1 +msgid "Create Rules pop-up window on Default Nomenclature page." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/barcode_nomenclature.rst:120 +msgid "The :guilabel:`Rule Name` field is used internally to identify what the barcode represents." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/barcode_nomenclature.rst:122 +msgid "The :guilabel:`Sequence` field represents the priority of the rule; meaning the smaller the value, the higher the rule appears on the table." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/barcode_nomenclature.rst:125 +msgid "The barcode :guilabel:`Type` field represents different classifications of information that can be understood by the system (e.g., :guilabel:`Package`, :guilabel:`Lot`, :guilabel:`Location`, :guilabel:`Coupon`, etc.)." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/barcode_nomenclature.rst:129 +msgid "The :guilabel:`Encoding` field specifies which encoding the barcode uses; this rule **only** applies if the barcode uses this specific encoding. The available :guilabel:`Encoding` options are: :guilabel:`EAN-13`, :guilabel:`EAN-8`, :guilabel:`UPC-A`, and :guilabel:`GS1-28`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/barcode_nomenclature.rst:133 +msgid "The :guilabel:`Barcode Pattern` field represents how the sequence of letters or numbers is recognized by the system to contain information about the product. Odoo follows the sequential order of this table, and uses the first rule it matches, based on the sequence." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/barcode_nomenclature.rst:138 +msgid "Barcode patterns can also define how numerical values, such as weight or price, are encoded in the barcode." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/barcode_nomenclature.rst:141 +msgid "They are indicated by **{NNN}**, where `N` defines where the number's digits are encoded. *Floats* are also supported with the decimals, indicated by `D`, such as **{NNNDD}**." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/barcode_nomenclature.rst:144 +msgid "In this case, the barcode field on the associated records **must** show these digits as zeros." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/barcode_nomenclature.rst:146 +msgid "After filling in the information, click the :guilabel:`Save & New` button to save the rule, and instantly start creating another rule. Or, click :guilabel:`Save & Close` to save the rule, and return to the table of rules." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/barcode_nomenclature.rst:151 +msgid "When the :guilabel:`Barcode Pattern` field contains `.*`, it means it can contain **any** number of characters - those characters being **any** number or type of character." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/barcode_nomenclature.rst:157 +msgid "Default nomenclature list" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/barcode_nomenclature.rst:159 +msgid "The table below contains Odoo's list of :guilabel:`Default Nomenclature` rules. Barcode patterns are written in regular expressions." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/barcode_nomenclature.rst:166 +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:173 +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_usage.rst:38 +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_usage.rst:166 +msgid "Rule Name" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/barcode_nomenclature.rst:167 +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:173 +msgid "Type" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/barcode_nomenclature.rst:168 +msgid "Encoding" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/barcode_nomenclature.rst:169 +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:173 +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_usage.rst:38 +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_usage.rst:166 +msgid "Barcode Pattern" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/barcode_nomenclature.rst:170 +msgid "Price Barcodes 2 Decimals" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/barcode_nomenclature.rst:171 +msgid "Priced Product" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/barcode_nomenclature.rst:172 +#: ../../content/applications/inventory_and_mrp/barcode/operations/barcode_nomenclature.rst:180 +msgid "EAN-13" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/barcode_nomenclature.rst:173 +msgid "23.....{NNNDD}" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/barcode_nomenclature.rst:174 +msgid "Discount Barcodes" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/barcode_nomenclature.rst:175 +msgid "Discounted Product" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/barcode_nomenclature.rst:176 +#: ../../content/applications/inventory_and_mrp/barcode/operations/barcode_nomenclature.rst:184 +#: ../../content/applications/inventory_and_mrp/barcode/operations/barcode_nomenclature.rst:188 +#: ../../content/applications/inventory_and_mrp/barcode/operations/barcode_nomenclature.rst:192 +#: ../../content/applications/inventory_and_mrp/barcode/operations/barcode_nomenclature.rst:196 +#: ../../content/applications/inventory_and_mrp/barcode/operations/barcode_nomenclature.rst:200 +#: ../../content/applications/inventory_and_mrp/barcode/operations/barcode_nomenclature.rst:204 +#: ../../content/applications/inventory_and_mrp/barcode/operations/barcode_nomenclature.rst:208 +#: ../../content/applications/inventory_and_mrp/barcode/operations/barcode_nomenclature.rst:212 +msgid "Any" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/barcode_nomenclature.rst:177 +msgid "22{NN}" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/barcode_nomenclature.rst:178 +msgid "Weight Barcodes 3 Decimals" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/barcode_nomenclature.rst:179 +msgid "Weighted Product" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/barcode_nomenclature.rst:181 +msgid "21.....{NNDDD}" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/barcode_nomenclature.rst:182 +msgid "Customer Barcodes" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/barcode_nomenclature.rst:183 +msgid "Client" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/barcode_nomenclature.rst:185 +msgid "042" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/barcode_nomenclature.rst:186 +msgid "Coupon & Gift Card Barcodes" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/barcode_nomenclature.rst:187 +msgid "Coupon" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/barcode_nomenclature.rst:189 +msgid "043|044" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/barcode_nomenclature.rst:190 +msgid "Cashier Barcodes" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/barcode_nomenclature.rst:191 +msgid "Cashier" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/barcode_nomenclature.rst:193 +msgid "041" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/barcode_nomenclature.rst:194 +msgid "Location barcodes" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/barcode_nomenclature.rst:195 +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:189 +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:189 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/warehouses_locations.rst:17 +msgid "Location" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/barcode_nomenclature.rst:197 +msgid "414" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/barcode_nomenclature.rst:198 +msgid "Package barcodes" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/barcode_nomenclature.rst:199 +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:175 +msgid "Package" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/barcode_nomenclature.rst:201 +msgid "PACK" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/barcode_nomenclature.rst:202 +msgid "Lot barcodes" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/barcode_nomenclature.rst:203 +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:191 +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:191 +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:194 +msgid "Lot" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/barcode_nomenclature.rst:205 +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_usage.rst:45 +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_usage.rst:143 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/removal_strategies/lifo.rst:39 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/removal_strategies/lifo.rst:40 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/removal_strategies/lifo.rst:41 +msgid "10" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/barcode_nomenclature.rst:206 +msgid "Magnetic Credit Card" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/barcode_nomenclature.rst:207 +msgid "Credit Card" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/barcode_nomenclature.rst:209 +msgid "%.*" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/barcode_nomenclature.rst:210 +msgid "Product Barcodes" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/barcode_nomenclature.rst:211 +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:177 +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:180 +msgid "Unit Product" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/barcode_nomenclature.rst:213 +msgid ".*" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/barcode_nomenclature.rst:216 +msgid ":doc:`gs1_nomenclature`" msgstr "" #: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:3 @@ -350,10 +601,6 @@ msgstr "" msgid ":ref:`Why's my barcode not working? `" msgstr "" -#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:32 -msgid "Set up barcode nomenclature" -msgstr "" - #: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:34 msgid "To use GS1 nomenclature, navigate to the :menuselection:`Inventory app --> Configuration --> Settings`. Then under the :guilabel:`Barcode` section, check the :guilabel:`Barcode Scanner` box. Next, select :menuselection:`Barcode Nomenclature --> Default GS1 Nomenclature` from the default barcode nomenclature options." msgstr "" @@ -406,10 +653,6 @@ msgstr "" msgid ":ref:`Non-unit quantities workflow `" msgstr "" -#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:96 -msgid "Create rules" -msgstr "" - #: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:98 msgid "GS1 rules are a specific format of information contained in the barcode, beginning with an |AI| and containing a defined length of characters. Scanning GS1 barcodes from the :ref:`default GS1 list ` auto-fills corresponding data in the Odoo database." msgstr "" @@ -478,22 +721,6 @@ msgstr "" msgid "The table below contains Odoo's default list of GS1 rules. Barcode patterns are written in regular expressions. Only the first three rules require a `check digit `_ as the final character." msgstr "" -#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:173 -#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_usage.rst:38 -#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_usage.rst:166 -msgid "Rule Name" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:173 -msgid "Type" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:173 -#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_usage.rst:38 -#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_usage.rst:166 -msgid "Barcode Pattern" -msgstr "" - #: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:173 msgid "GS1 Content Type" msgstr "" @@ -506,10 +733,6 @@ msgstr "" msgid "Serial Shipping Container Code" msgstr "" -#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:175 -msgid "Package" -msgstr "" - #: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:175 msgid "(00)(\\\\d{18})" msgstr "" @@ -533,11 +756,6 @@ msgstr "" msgid "Global Trade Item Number (GTIN)" msgstr "" -#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:177 -#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:180 -msgid "Unit Product" -msgstr "" - #: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:177 #: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_usage.rst:40 #: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_usage.rst:168 @@ -567,6 +785,7 @@ msgstr "" msgid "Ship to / Deliver to global location" msgstr "" +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:183 #: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:183 #: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:186 msgid "Destination location" @@ -592,11 +811,6 @@ msgstr "" msgid "I.D. of a physical location" msgstr "" -#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:189 -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/warehouses_locations.rst:17 -msgid "Location" -msgstr "" - #: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:189 msgid "(414)(\\\\d{13})" msgstr "" @@ -606,11 +820,6 @@ msgstr "" msgid "Batch or lot number" msgstr "" -#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:191 -#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:194 -msgid "Lot" -msgstr "" - #: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:191 msgid "(10) ([!\"%-/0-9:-?A-Z_a-z]{0,20})" msgstr "" @@ -621,6 +830,7 @@ msgstr "" msgid "Alpha-numeric name" msgstr "" +#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:194 #: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:194 msgid "Serial number" msgstr "" @@ -916,14 +1126,6 @@ msgstr "" msgid "Lot Number" msgstr "" -#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_usage.rst:45 -#: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_usage.rst:143 -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/removal_strategies/lifo.rst:39 -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/removal_strategies/lifo.rst:40 -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/removal_strategies/lifo.rst:41 -msgid "10" -msgstr "" - #: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_usage.rst:45 msgid "(10)([!\"%-/0-9:-?A-Z_a-z]{0,20})" msgstr "" @@ -945,6 +1147,10 @@ msgstr "" #: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/multipack.rst:11 #: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/delivery_three_steps.rst:18 #: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_three_steps.rst:16 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/reservation_methods.rst:36 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/reservation_methods/at_confirmation.rst:16 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/reservation_methods/before_scheduled_date.rst:17 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/reservation_methods/manually.rst:19 #: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/delivery_method.rst:17 #: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/starshipit_shipping.rst:104 #: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/third_party_shipper.rst:16 @@ -1575,6 +1781,278 @@ msgstr "" msgid "Setup" msgstr "" +#: ../../content/applications/inventory_and_mrp/barcode/setup/device_troubleshooting.rst:3 +msgid "Barcode device troubleshooting" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/setup/device_troubleshooting.rst:5 +msgid "Odoo *Barcode* supports three main types of barcode scanners: USB scanners, bluetooth scanners, and mobile computer scanners. While configuring each type of scanner, common issues may arise, in which the scanners do not work as intended, and Odoo returns errors to the device." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/setup/device_troubleshooting.rst:9 +msgid "Read the sections below to identify general and unique device issues, related to specific, popular types of scanners." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/setup/device_troubleshooting.rst:13 +msgid "General issues" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/setup/device_troubleshooting.rst:15 +msgid "Refer to the following sections below for common issues involving popular barcode scanner devices." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/setup/device_troubleshooting.rst:17 +msgid "For issues related to specific devices, refer to the :ref:`Android scanners ` section for mobile computer scanners, or to the :ref:`Screenless scanners ` section for USB and bluetooth scanners." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/setup/device_troubleshooting.rst:22 +msgid "Barcode cannot be read" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/setup/device_troubleshooting.rst:24 +msgid "One common issue encountered when using barcode scanners is an error resulting from barcodes that cannot be read." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/setup/device_troubleshooting.rst:27 +msgid "This can occur due to any of the following reasons:" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/setup/device_troubleshooting.rst:29 +msgid "The barcode is damaged." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/setup/device_troubleshooting.rst:30 +msgid "The device cannot read the required barcode type (some scanners can only read 2D barcodes)." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/setup/device_troubleshooting.rst:31 +msgid "The barcode being scanned is on a screen. Some scanners don't support this, and the barcodes **must** be printed out to be scanned. This is most common with 1D barcodes." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/setup/device_troubleshooting.rst:33 +msgid "The device has no battery, or is broken. To rule this out, follow the troubleshooting instructions in the following sections." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/setup/device_troubleshooting.rst:37 +msgid "Odoo returns barcode error" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/setup/device_troubleshooting.rst:39 +msgid "All types of barcode scanners have their own device \"language\", which affects how they output barcode data to Odoo's *Barcode* app. Sometimes, this can cause Odoo *Barcode* to return a barcode error after scanning. This could be due to any of the following reasons:" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/setup/device_troubleshooting.rst:43 +msgid "The computer is configured with a different keyboard layout than the barcode scanner. To rule this out, ensure that the device is configured with the same keyboard layout." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/setup/device_troubleshooting.rst:46 +msgid "For example, if the computer is configured to use an FR-BE keyboard, configure the scanner to send FR-BE keystrokes. The same logic applies if using a tablet instead of a computer." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/setup/device_troubleshooting.rst:49 +msgid "For more information on configuring keystrokes, refer to the :doc:`Barcode scanner setup ` documentation." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/setup/device_troubleshooting.rst:51 +msgid "For mobile computer scanners (such as Zebra devices, for example), the scanner might interpret the barcode differently than intended. To rule this out, scan a test barcode to see how the scanner interprets the barcode." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/setup/device_troubleshooting.rst:58 +msgid "Android scanners" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/setup/device_troubleshooting.rst:60 +msgid "The most recent barcode scanner models using Android and Google Chrome should work with Odoo. However, due to the variety of models and configurations, it is recommended to first test a scanner's compatibility with Odoo." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/setup/device_troubleshooting.rst:64 +msgid "The Zebra product line is recommended; specifically, the **Zebra TC21 (WiFi-only)**, and **Zebra TC26 (WiFi/cellular)**." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/setup/device_troubleshooting.rst:68 +msgid "`Odoo Inventory & Barcode compatible hardware `_" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/setup/device_troubleshooting.rst:71 +msgid "Barcode app does not give feedback" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/setup/device_troubleshooting.rst:73 +msgid "By default, Android barcode scanners pre-process the barcode, then send a full text. Since Odoo *Barcode* does not read this type of output, settings for each type of scanner **must** be configured correctly." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/setup/device_troubleshooting.rst:77 +msgid "Odoo *Barcode* expects that the scanner works like an analogue keyboard, and so, only detects *key events*. Refer to the following sections for configuration settings for the most popular devices." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/setup/device_troubleshooting.rst:81 +msgid "Zebra TC21/TC26" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/setup/device_troubleshooting.rst:83 +#: ../../content/applications/inventory_and_mrp/barcode/setup/hardware.rst:76 +msgid "When using Zebra scanners, ensure the following keystroke configurations are set to prevent errors." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/setup/device_troubleshooting.rst:85 +#: ../../content/applications/inventory_and_mrp/barcode/setup/hardware.rst:78 +msgid "Begin on the Zebra scanner's home screen, and select the :guilabel:`DataWedge` app (the app is represented by a :guilabel:`(light blue barcode)` icon)." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/setup/device_troubleshooting.rst:88 +#: ../../content/applications/inventory_and_mrp/barcode/setup/hardware.rst:81 +msgid "On the :guilabel:`DataWedge Profiles` page, select the profile option to access the Zebra scanner's settings." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/setup/device_troubleshooting.rst:91 +#: ../../content/applications/inventory_and_mrp/barcode/setup/hardware.rst:92 +msgid "Once the profile is selected, scroll down to the :guilabel:`Keyboard Output` option, and ensure the :guilabel:`Enable/disable keystroke output` option is :guilabel:`Enabled`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/setup/device_troubleshooting.rst:-1 +#: ../../content/applications/inventory_and_mrp/barcode/setup/hardware.rst:-1 +msgid "Show keystroke option in the Zebra scanner's DataWedge app." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/setup/device_troubleshooting.rst:98 +#: ../../content/applications/inventory_and_mrp/barcode/setup/hardware.rst:99 +msgid "Once that option is enabled, go back to the :guilabel:`Profile` options page, and go to the :guilabel:`Keystroke output` section. Then, open the :guilabel:`Key event options` submenu. Under :guilabel:`Characters`, ensure the :guilabel:`Send Characters as Events` option is checked." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/setup/device_troubleshooting.rst:103 +#: ../../content/applications/inventory_and_mrp/barcode/setup/hardware.rst:104 +msgid "The :guilabel:`Send Characters as Events` option **must** be checked on the Zebra scanner, or Odoo **cannot** recognize the barcodes that are scanned." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/setup/device_troubleshooting.rst:106 +msgid "Once the above steps have been taken, perform a test scan to ensure the Zebra scanner is working as intended." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/setup/device_troubleshooting.rst:110 +msgid "MUNBYN Android devices" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/setup/device_troubleshooting.rst:112 +msgid "When using MUNBYN Android scanners, ensure the following configurations are set to prevent errors." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/setup/device_troubleshooting.rst:114 +msgid "From the device's home screen, click :menuselection:`AppSettings`. On the resulting page, locate the :guilabel:`Process mode` section, and select :guilabel:`Keyboard input`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/setup/device_troubleshooting.rst:-1 +msgid "Process mode section on MUNBYN scanner's AppSettings page." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/setup/device_troubleshooting.rst:122 +msgid "The selected *Process mode* controls how data is processed after barcode data has been read out." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/setup/device_troubleshooting.rst:124 +msgid "*Keyboard input* enters read-out data at the position of the cursor, the same as input data on an analogue keyboard would." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/setup/device_troubleshooting.rst:127 +msgid "Once the above steps have been taken, perform a test scan to ensure the MUNBYN Android scanner is working as intended." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/setup/device_troubleshooting.rst:130 +msgid "Why is there no data output in the app after a successful scan?" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/setup/device_troubleshooting.rst:132 +msgid "When scanning a barcode, the scanner might beep, indicating a successful scan, but there is no data output in the app." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/setup/device_troubleshooting.rst:135 +msgid "To fix this issue, adjust the output method to *keyboard analogue* in the *Scanner* app on the device." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/setup/device_troubleshooting.rst:138 +msgid "From the device's home screen, click :menuselection:`Scanner App --> Settings`. From the :guilabel:`Settings` page, click :guilabel:`Output Mode`. The resulting pop-up window presents the different output options available to users. Select :guilabel:`Keyboard Mode`, then click :guilabel:`OK`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/setup/device_troubleshooting.rst:-1 +msgid "Output mode pop-up window on MUNBYN scanner." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/setup/device_troubleshooting.rst:147 +msgid "Go back to the app that needs to be scanned, and click on the input dialog box first before scanning. Finally, perform a test scan to ensure the MUNBYN Android scanner is working as intended." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/setup/device_troubleshooting.rst:152 +msgid "Datalogic Android devices" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/setup/device_troubleshooting.rst:154 +msgid "When using Datalogic Android scanners, ensure the following configurations are set to prevent errors." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/setup/device_troubleshooting.rst:157 +msgid "To view and configure all settings for the scanner, use the *Settings* app on the Datalogic Android device. From the applications menu, select :menuselection:`Settings --> System --> Scanner Settings`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/setup/device_troubleshooting.rst:161 +msgid "From the resulting list of settings, select :guilabel:`Wedge`. From this menu, under the :guilabel:`Keyboard wedge` section, ensure that the :guilabel:`Enable keyboard wedge` feature is activated." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/setup/device_troubleshooting.rst:165 +msgid "Then, also under the :guilabel:`Keyboard wedge` section, locate the :guilabel:`Keyboard wedge input mode` option. By default, the input mode is set to :guilabel:`Text injection`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/setup/device_troubleshooting.rst:-1 +msgid "Wedge configuration menu on Datalogic scanner." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/setup/device_troubleshooting.rst:172 +msgid "Click :guilabel:`Keyboard wedge input mode`, and change the setting to :guilabel:`Key pressure`. This ensures that scanned barcodes are translated into keyboard strokes, instead of being injected into the text area." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/setup/device_troubleshooting.rst:-1 +msgid "Keyboard wedge input mode selection on Datalogic scanner." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/setup/device_troubleshooting.rst:180 +msgid "Once all those steps have been taken, perform a test scan to ensure the Datalogic Android scanner is working as intended." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/setup/device_troubleshooting.rst:186 +msgid "Screenless scanners" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/setup/device_troubleshooting.rst:188 +msgid "Screenless scanners are barcode scanning devices that have no screens. These include USB scanners and bluetooth scanners." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/setup/device_troubleshooting.rst:192 +msgid "Odoo supports most USB and Bluetooth barcode scanners, as they all emulate a keyboard. However, to verify that a scanner is compatible with a specific keyboard layout (or can be configured to do so), refer to Odoo's `Inventory & Barcode compatible hardware `_ documentation." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/setup/device_troubleshooting.rst:198 +msgid "NETUM devices" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/setup/device_troubleshooting.rst:200 +msgid "By default, the NETUM barcode scanner's user manual only shows the French keyboard configuration. To use the Belgian keyboard, scan the code below:" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/setup/device_troubleshooting.rst:-1 +msgid "Belgian FR key barcode." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/setup/device_troubleshooting.rst:207 +msgid "Once that code has been scanned, ensure the NETUM scanner has the correct keyboard configuration, and is working as intended." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/setup/device_troubleshooting.rst:211 +msgid ":doc:`../setup/hardware`" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/setup/device_troubleshooting.rst:212 +#: ../../content/applications/inventory_and_mrp/barcode/setup/hardware.rst:165 +msgid ":doc:`../setup/software`" +msgstr "" + #: ../../content/applications/inventory_and_mrp/barcode/setup/hardware.rst:3 msgid "Barcode scanner setup" msgstr "" @@ -1659,18 +2137,6 @@ msgstr "" msgid "Zebra scanner" msgstr "" -#: ../../content/applications/inventory_and_mrp/barcode/setup/hardware.rst:76 -msgid "When using Zebra scanners, ensure the following keystroke configurations are set to prevent errors." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/barcode/setup/hardware.rst:78 -msgid "Begin on the Zebra scanner's home screen, and select the :guilabel:`DataWedge` app (the app is represented by a :guilabel:`(light blue barcode)` icon)." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/barcode/setup/hardware.rst:81 -msgid "On the :guilabel:`DataWedge Profiles` page, select the profile option to access the Zebra scanner's settings." -msgstr "" - #: ../../content/applications/inventory_and_mrp/barcode/setup/hardware.rst:85 msgid "It is **not** suggested to use the \"DWDemo\" profile, as it does not work properly in every circumstance." msgstr "" @@ -1679,22 +2145,6 @@ msgstr "" msgid "Instead, it is recommended to create a new, personal profile. Once a new profile is created, add the *Odoo Mobile* app and *Google Chrome* app in the :guilabel:`Associated Apps` on the scanner's home screen." msgstr "" -#: ../../content/applications/inventory_and_mrp/barcode/setup/hardware.rst:92 -msgid "Once the profile is selected, scroll down to the :guilabel:`Keyboard Output` option, and ensure the :guilabel:`Enable/disable keystroke output` option is :guilabel:`Enabled`." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/barcode/setup/hardware.rst:-1 -msgid "Show keystroke option in the Zebra scanner's DataWedge app." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/barcode/setup/hardware.rst:99 -msgid "Once that option is enabled, go back to the :guilabel:`Profile` options page, and go to the :guilabel:`Keystroke output` section. Then, open the :guilabel:`Key event options` submenu. Under :guilabel:`Characters`, ensure the :guilabel:`Send Characters as Events` option is checked." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/barcode/setup/hardware.rst:104 -msgid "The :guilabel:`Send Characters as Events` option **must** be checked on the Zebra scanner, or Odoo **cannot** recognize the barcodes that are scanned." -msgstr "" - #: ../../content/applications/inventory_and_mrp/barcode/setup/hardware.rst:107 msgid "Once all those steps have been taken, perform a test scan to ensure the Zebra scanner is working properly, as intended." msgstr "" @@ -1767,10 +2217,6 @@ msgstr "" msgid "After completing the steps, conduct a test scan to verify the Cipherlab scanner is working as intended." msgstr "" -#: ../../content/applications/inventory_and_mrp/barcode/setup/hardware.rst:165 -msgid ":doc:`../setup/software`" -msgstr "" - #: ../../content/applications/inventory_and_mrp/barcode/setup/software.rst:3 msgid "Activate the Barcodes in Odoo" msgstr "" @@ -2765,6 +3211,7 @@ msgid "Upon warehouse receipt, the recorded quantities are in the internal \"Uni msgstr "" #: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/uom.rst:133 +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/blanket_orders.rst:169 msgid "Replenishment" msgstr "" @@ -3511,7 +3958,7 @@ msgid ":doc:`differences`" msgstr "" #: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/package.rst:3 -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/usage.rst:12 +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/type.rst:189 #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/removal_strategies.rst:99 #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/removal_strategies.rst:159 msgid "Packages" @@ -3814,7 +4261,6 @@ msgid ":guilabel:`Barcode`: identifier for tracing packaging in stock moves or p msgstr "" #: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/packaging.rst:56 -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/usage.rst:137 msgid ":guilabel:`Company`: indicates the packaging is only available at the selected company. Leave blank to make the packaging available across all companies." msgstr "" @@ -3823,7 +4269,6 @@ msgid "To create a packaging type for six units of the product, `Grape Soda`, be msgstr "" #: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/packaging.rst:0 -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/usage.rst:0 msgid "Create 6-pack case for product." msgstr "" @@ -3840,12 +4285,10 @@ msgid "Two soda products, `Grape Soda` and `Diet Coke`, have three types of pack msgstr "" #: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/packaging.rst:0 -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/usage.rst:0 msgid "List of different packagings for products." msgstr "" #: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/packaging.rst:86 -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/usage.rst:179 msgid "Apply packagings" msgstr "" @@ -3854,17 +4297,14 @@ msgid "When creating a sales order in the :menuselection:`Sales` app, specify th msgstr "" #: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/packaging.rst:93 -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/usage.rst:186 msgid "18 cans of the product, `Grape Soda`, is packed using three 6-pack packagings." msgstr "" #: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/packaging.rst:0 -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/usage.rst:0 msgid "Assign packagings on the Sales Order Line." msgstr "" #: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/packaging.rst:100 -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/usage.rst:193 msgid "Packaging can be used in conjunction with Odoo :ref:`Barcode `. When receiving products from suppliers, scanning the packaging barcode automatically adds the number of units in the packaging to the internal count of the product." msgstr "" @@ -4180,6 +4620,313 @@ msgstr "" msgid ":doc:`/applications/inventory_and_mrp/inventory/product_management/product_tracking/differences`" msgstr "" +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/type.rst:3 +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/type.rst:69 +msgid "Product type" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/type.rst:7 +msgid "Define *product types* in Odoo to track products in varying levels of detail." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/type.rst:9 +msgid "Classify products as *storable* to track stock counts, allowing users to trigger :doc:`reordering rules <../product_replenishment/reordering_rules>` for generating purchase orders. *Consumable* products are assumed to always be in stock, and *service* products are performed and served by the business." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/type.rst:15 +msgid "`Odoo Tutorials: Product Type `_" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/type.rst:18 +msgid "Set product type" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/type.rst:20 +msgid "To set a product type, go to :menuselection:`Inventory app --> Products --> Products`, and select the desired product from the list." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/type.rst:23 +msgid "On the product form, in the :guilabel:`Product Type` field, select:" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/type.rst:25 +msgid ":guilabel:`Storable Product` for products tracked with stock counts. Only storable products can trigger reordering rules for generating purchase orders;" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/type.rst:29 +msgid "Choose :guilabel:`Storable Product` if it is necessary to track a product's stock at various locations, inventory valuations, or if the product has lots and/or serial numbers." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/type.rst:32 +msgid ":guilabel:`Consumable` for products that are always assumed to be in stock, whose quantities are not necessary to track or forecast (e.g. nails, toilet paper, coffee, etc.). Consumables are replaceable and essential, but exact counts are unnecessary; or" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/type.rst:35 +msgid ":guilabel:`Service` for sellable service products that are performed, and not tracked with stock counts (i.e. maintenance, installation, or repair services)." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/type.rst:0 +msgid "Set a product type on the product form." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/type.rst:43 +msgid "The product types listed above are part of the standard *Inventory* app. For access to the fields below, :ref:`install ` the corresponding apps **in addition** to *Inventory*." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/type.rst:46 +msgid ":guilabel:`Booking Fees`: charge a fee for booking appointments through the *Appointments* app. Requires the installation of the *Calendar* app and *Pay to Book* (`appointment_account_payment`) module" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/type.rst:49 +msgid ":guilabel:`Combo`: create discounted products sold in a bundle. Requires the installation of the *PoS* app." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/type.rst:51 +msgid ":guilabel:`Event Ticket`: sold to attendees wanting to go to an event. Requires the installation of the *Events* app" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/type.rst:53 +msgid ":guilabel:`Event Booth`: sold to partners or sponsors to set up a booth at an event. Requires the installation of the *Events* app" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/type.rst:55 +msgid ":guilabel:`Course`: sell access to an educational course. Requires the installation of the *eLearning* app" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/type.rst:59 +msgid "Compare types" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/type.rst:61 +msgid "Below is a summary of how each product type affects common *Inventory* operations, like transfers, reordering rules, and the forecasted report. Click the chart item with an asterisk (*) to navigate to detailed sections." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/type.rst:70 +msgid "Storable" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/type.rst:71 +msgid "Consumable" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/type.rst:72 +msgid "Service" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/type.rst:73 +msgid "Physical product" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/type.rst:74 +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/type.rst:75 +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/type.rst:83 +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/type.rst:91 +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/type.rst:95 +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/type.rst:103 +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/type.rst:104 +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/type.rst:107 +msgid "Yes" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/type.rst:76 +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/type.rst:80 +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/type.rst:84 +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/type.rst:85 +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/type.rst:92 +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/type.rst:93 +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/type.rst:97 +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/type.rst:101 +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/type.rst:105 +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/type.rst:109 +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/type.rst:112 +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/type.rst:113 +msgid "No" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/type.rst:77 +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/type.rst:118 +msgid "On-hand quantity" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/type.rst:78 +msgid ":ref:`Yes* `" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/type.rst:79 +msgid ":ref:`Yes* `" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/type.rst:81 +msgid ":doc:`Inventory valuation <../../warehouses_storage/inventory_valuation/using_inventory_valuation>`" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/type.rst:86 +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/type.rst:139 +msgid "Create transfer" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/type.rst:87 +msgid ":ref:`Yes* `" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/type.rst:88 +msgid ":ref:`Yes* `" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/type.rst:89 +msgid ":ref:`No* `" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/type.rst:90 +msgid ":doc:`Lot/serial number tracking `" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/type.rst:94 +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/type.rst:163 +msgid "Create purchase order" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/type.rst:96 +msgid ":ref:`Yes* `" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/type.rst:98 +msgid "Can be manufactured or subcontracted" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/type.rst:99 +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/type.rst:100 +msgid ":ref:`Yes* `" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/type.rst:102 +msgid "Can be in a kit" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/type.rst:106 +msgid "Placed in package" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/type.rst:108 +msgid ":ref:`Yes* `" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/type.rst:110 +msgid "Appears on Inventory report" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/type.rst:111 +msgid ":ref:`Yes `" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/type.rst:120 +msgid "A storable product's on-hand and forecasted quantities, based on incoming and outgoing orders, are reflected on the product form, accessed by going to :menuselection:`Inventory app --> Products --> Products`, and selecting the desired product." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/type.rst:128 +msgid "Show \"On Hand\" and \"Forecast\" smart buttons." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/type.rst:128 +msgid "Current and forecasted quantities are displayed in the **On Hand** and **Forecasted** smart buttons on the product form." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/type.rst:133 +msgid "On the other hand, consumable products are regarded as always available, and they **cannot** be managed using reordering rules or lot/serial numbers." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/type.rst:141 +msgid "*Transfers* are any warehouse operation, such as receipts, internal or batch transfers, or deliveries." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/type.rst:144 +msgid "When creating a transfer for storable products in the *Inventory* app, transfers modify the on-hand quantity at each location." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/type.rst:147 +msgid "For example, transferring five units from the internal location `WH/Stock` to `WH/Packing Zone` decreases the recorded quantity at `WH/Stock` and increases it at `WH/Packing Zone`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/type.rst:152 +msgid "For consumable products, transfers can be created, but exact quantities at each storage location are not tracked." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/type.rst:157 +msgid "Service products cannot be included in transfers, but these products can be `linked to projects and tasks for deadline tracking `_." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/type.rst:165 +msgid "Both storable and consumable products can be included in a request for quotation in the *Purchase* app." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/type.rst:168 +msgid "However, when receiving consumable products, their on-hand quantity does not change upon validating the receipt (e.g. `WH/IN`)." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/type.rst:174 +msgid "Manufacture or subcontract" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/type.rst:176 +msgid "Storable and consumable products can be manufactured, subcontracted, or included in a bill of materials (BoM)." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/type.rst:183 +msgid "Show \"Bill of Materials\" and \"Used In\" smart buttons." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/type.rst:183 +msgid "When the **Bill of Materials** and **Used In** smart buttons are visible on the product form, this indicates the product can be manufactured or used as a component of a |BOM|." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/type.rst:191 +msgid "Both storable and consumable products can be placed in :doc:`packages `." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/type.rst:193 +msgid "However, for consumable products, the quantity is not tracked, and the product is not listed in the package's :guilabel:`Contents`, accessed by going to :menuselection:`Inventory app --> Products --> Packages`, and selecting the desired package." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/type.rst:201 +msgid "Show Packages page, containing the package contents list." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/type.rst:201 +msgid "A consumable product was placed in the package, but the **Content** section does not list it." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/type.rst:203 +msgid "If the *Move Entire Package* feature is enabled, moving a package updates the location of the contained storable products. However, the location of consumable products are not updated." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/type.rst:209 +msgid "Inventory report" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/type.rst:211 +msgid "**Only** storable products appear on the following reports." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/type.rst:213 +msgid "The *stock report* is a comprehensive list of all on-hand, unreserved, incoming, and outgoing storable products. The report is only available to users with :doc:`administrator access <../../../../general/users/access_rights>`, and is found by navigating to :menuselection:`Inventory app --> Reporting --> Stock`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/type.rst:-1 +msgid "Show stock reporting list found in Inventory > Reporting > Stock." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/type.rst:222 +msgid "The *location report* is a breakdown of each location (internal, external, or virtual) and the on-hand and reserved quantity of each storable product. The report is only available with the *Storage Location* feature activated (:menuselection:`Inventory app --> Configuration --> Settings`), and to users with :doc:`administrator access <../../../../general/users/access_rights>`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/type.rst:227 +msgid "Navigate to the location report by going to :menuselection:`Inventory app --> Reporting --> Locations`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/type.rst:-1 +msgid "Show location reporting list found in Inventory > Reporting > Locations." +msgstr "" + #: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving.rst:5 msgid "Shipping and receiving" msgstr "" @@ -4193,6 +4940,14 @@ msgstr "" msgid "How to cancel a shipping request to a shipper?" msgstr "" +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/cancel.rst:6 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/invoicing.rst:8 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/label_type.rst:6 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/labels.rst:6 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/third_party_shipper.rst:8 +msgid "Overview" +msgstr "" + #: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/cancel.rst:8 msgid "Odoo can handle various delivery methods, including third party shippers. Odoo will be linked with the transportation company tracking system." msgstr "" @@ -5769,6 +6524,495 @@ msgstr "" msgid ":ref:`Process deliveries in three steps `" msgstr "" +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/reservation_methods.rst:6 +msgid "Reservation methods" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/reservation_methods.rst:8 +msgid "Companies that sell and deliver goods to customers need to make sure they always have stock on-hand, so when new sales orders are confirmed, they can deliver products on time." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/reservation_methods.rst:11 +msgid "In Odoo, this can be handled using *reservation methods*. Reservation methods control how products included in a delivery order (DO) should be reserved for delivery, ensuring they are reserved at the correct times, for the correct orders." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/reservation_methods.rst:15 +msgid "There are three different reservation methods in Odoo: *At Confirmation*, *Manually*, and *Before scheduled date*." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/reservation_methods.rst:20 +msgid "At Confirmation" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/reservation_methods.rst:22 +msgid "Reserves products **only** when a sales order is confirmed, **and** if stock is already available." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/reservation_methods.rst:25 +msgid "Manually" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/reservation_methods.rst:27 +msgid "Once a quote is confirmed, product availability **must** be checked manually, and the required quantity **must** be reserved manually." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/reservation_methods.rst:30 +msgid "Before scheduled date" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/reservation_methods.rst:32 +msgid "A specific number of days can be selected; this is the maximum number of days **before** a scheduled delivery date that products should be reserved." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/reservation_methods.rst:38 +msgid "Reservation methods are set on individual operations types. To configure reservation methods, go to :menuselection:`Inventory app --> Configuration --> Operations Types`. Then, select the desired operation type. Or, create a new one by clicking :guilabel:`New`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/reservation_methods.rst:42 +msgid "In the :guilabel:`General` tab of the operation type form, locate the :guilabel:`Reservation Method` option, and choose which method should be used for this type of operation." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/reservation_methods.rst:-1 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/reservation_methods/at_confirmation.rst:-1 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/reservation_methods/before_scheduled_date.rst:-1 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/reservation_methods/manually.rst:-1 +msgid "Reservation method field on delivery order operation type form." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/reservation_methods.rst:50 +msgid "If the :guilabel:`Before scheduled date` reservation method is selected, a new :guilabel:`Reserve before scheduled date` field appears below. From this field, the number of :guilabel:`days before` and :guilabel:`days before when starred` can be changed from the default `0`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/reservation_methods.rst:55 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/reservation_methods/before_scheduled_date.rst:38 +msgid "Changing the :guilabel:`days before` value changes the maximum number of days before a scheduled date that products should be reserved." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/reservation_methods.rst:58 +msgid "Changing the :guilabel:`days before when starred` value changes the maximum number of days before a scheduled date that starred (favorited) transfers for products should be reserved." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/reservation_methods.rst:0 +msgid "Reserve before scheduled date fields with before scheduled date method chosen." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/reservation_methods.rst:66 +msgid "Required applications" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/reservation_methods.rst:68 +msgid "The two required applications that **must** be :ref:`installed ` to use reservation methods are the *Sales* and *Inventory* apps." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/reservation_methods.rst:72 +msgid "In addition to delivery orders, reservation methods can also be used for *manufacturing orders*, *resupply subcontractor* orders, orders for *repairs*, and *internal transfers*, if desired. To enable this, configure the additional settings:" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/reservation_methods.rst:76 +msgid "**For manufacturing orders:** Install the *Manufacturing* application by going to the :menuselection:`Apps` application, locating the *Manufacturing* app, and clicking :guilabel:`Install`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/reservation_methods.rst:79 +msgid "**For resupply subcontractor:** Navigate to :menuselection:`Manufacturing app --> Configuration --> Settings`, and under the :guilabel:`Operations` section, enable :guilabel:`Subcontracting`. Then, click :guilabel:`Save`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/reservation_methods.rst:82 +msgid "**For repairs:** Install the *Repairs* application by going to the :menuselection:`Apps` application, locating the *Repairs* app, and clicking :guilabel:`Install`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/reservation_methods.rst:84 +msgid "**For internal transfers:** Navigate to :menuselection:`Inventory app --> Configuration --> Settings`, and under the :guilabel:`Warehouse` section, enable :guilabel:`Storage Locations`. Then, click :guilabel:`Save`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/reservation_methods.rst:88 +msgid "Once these apps are installed, no additional features need to be enabled from the settings for reservation methods to work. They will be available by default on certain operations types, and can be viewed and changed by navigating to :menuselection:`Inventory app --> Configuration --> Operations Types`, and then clicking on a specific operations type." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/reservation_methods.rst:94 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/reservation_methods/before_scheduled_date.rst:31 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/reservation_methods/manually.rst:33 +msgid "When the :guilabel:`Type of Operation` is changed to :guilabel:`Receipt` on an :guilabel:`Operations Type` form, reservation methods are **not** available." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/reservation_methods.rst:-1 +msgid "Operations Types highlighted from the Configurations submenu in the Inventory app." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/reservation_methods.rst:102 +msgid ":doc:`reservation_methods/at_confirmation`" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/reservation_methods.rst:103 +msgid ":doc:`reservation_methods/manually`" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/reservation_methods.rst:104 +msgid ":doc:`reservation_methods/before_scheduled_date`" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/reservation_methods/at_confirmation.rst:3 +msgid "At confirmation reservation" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/reservation_methods/at_confirmation.rst:9 +msgid "The *at confirmation* reservation method reserves products **only** when a sales order (SO) is confirmed, **and** if enough stock of the products included in the |SO| is already available." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/reservation_methods/at_confirmation.rst:13 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/reservation_methods/before_scheduled_date.rst:14 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/reservation_methods/manually.rst:16 +msgid ":doc:`About reservation methods <../reservation_methods>`" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/reservation_methods/at_confirmation.rst:18 +msgid "To set the reservation method to *at confirmation*, navigate to :menuselection:`Inventory app --> Configuration --> Operations Types`. Then, select the desired :guilabel:`Operation Type` to configure, or create a new one by clicking :guilabel:`New`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/reservation_methods/at_confirmation.rst:22 +msgid "In the :guilabel:`General` tab on the operation type form, locate the :guilabel:`Reservation Method` field, and select :guilabel:`At Confirmation`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/reservation_methods/at_confirmation.rst:30 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/reservation_methods/before_scheduled_date.rst:79 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/reservation_methods/manually.rst:37 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/removal_strategies/closest_location.rst:65 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/removal_strategies/fefo.rst:69 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/removal_strategies/fifo.rst:47 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/removal_strategies/least_packages.rst:30 +msgid "Workflow" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/reservation_methods/at_confirmation.rst:32 +msgid "To see the *at confirmation* reservation method in action, create a new |SO| by navigating to :menuselection:`Sales app --> New`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/reservation_methods/at_confirmation.rst:35 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/reservation_methods/manually.rst:42 +msgid "Add a customer in the :guilabel:`Customer` field. Then, in the :guilabel:`Order Lines` tab, click :guilabel:`Add a product`, and select a product to add to the quotation from the drop-down menu. Finally, in the :guilabel:`Quantity` column, adjust the desired quantity of the product to sell." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/reservation_methods/at_confirmation.rst:39 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/reservation_methods/before_scheduled_date.rst:92 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/reservation_methods/manually.rst:46 +msgid "Once ready, click :guilabel:`Confirm` to confirm the sales order." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/reservation_methods/at_confirmation.rst:41 +msgid "Click the :guilabel:`📈 (area graph)` icon on the product line to reveal the product's :guilabel:`Availability` tooltip, which reveals the :guilabel:`Reserved` number of units for this order." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/reservation_methods/at_confirmation.rst:46 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/reservation_methods/before_scheduled_date.rst:106 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/reservation_methods/manually.rst:57 +msgid "If there is **not** sufficient quantity of stock for the product included in the |SO|, the :guilabel:`📈 (area graph)` icon is red, instead of green." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/reservation_methods/at_confirmation.rst:49 +msgid "Instead of revealing the reserved number of units for the order, the :guilabel:`Availability` tooltip reads :guilabel:`Available`, and reveals the available number of units (e.g., `0 Units`)." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/reservation_methods/at_confirmation.rst:-1 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/reservation_methods/before_scheduled_date.rst:-1 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/reservation_methods/manually.rst:-1 +msgid "Confirmed sales order with product availability tooltip selected." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/reservation_methods/at_confirmation.rst:56 +msgid "Forecasted Report" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/reservation_methods/at_confirmation.rst:58 +msgid "To see all the factors that affect product reservation, click the :guilabel:`View Forecast` internal link arrow to view the :guilabel:`Forecasted Report` dashboard." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/reservation_methods/at_confirmation.rst:61 +msgid "The :guilabel:`Forecasted Report` displays forecast information about the product(s) included in the sales order; namely, any live receipts of the product, and any active sales orders, which are listed in the :guilabel:`Used By` column. See how each order is fulfilled in the :guilabel:`Replenishment` column." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/reservation_methods/at_confirmation.rst:66 +msgid "Additionally, the :guilabel:`Forecasted` quantity is calculated at the top of the page, by adding the :guilabel:`On Hand` and :guilabel:`Incoming` quantity, and subtracting the :guilabel:`Outgoing` quantity, as shown below:" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/reservation_methods/at_confirmation.rst:-1 +msgid "Forecasted quantity equation from the Forecasted Report page." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/reservation_methods/at_confirmation.rst:74 +msgid "If one order should be prioritized over another order, click the :guilabel:`Unreserve` button on the corresponding order line in the :guilabel:`Replenishment` column." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/reservation_methods/at_confirmation.rst:77 +msgid "To deliver the products, click the :guilabel:`Delivery` smart button at the top of the sales order form. To confirm that the reservation worked properly, ensure that the :guilabel:`Product Availability` field reads `Available` (in green text), and the numbers in the :guilabel:`Demand` and :guilabel:`Quantity` columns match (in this case, both should read `100.00`)." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/reservation_methods/at_confirmation.rst:-1 +msgid "Delivery order for product included in sales order with at confirmation reservation." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/reservation_methods/at_confirmation.rst:86 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/reservation_methods/before_scheduled_date.rst:149 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/reservation_methods/manually.rst:108 +msgid "Once ready, click :guilabel:`Validate`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/reservation_methods/at_confirmation.rst:89 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/reservation_methods/before_scheduled_date.rst:152 +msgid ":doc:`Manual reservation `" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/reservation_methods/at_confirmation.rst:90 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/reservation_methods/manually.rst:139 +msgid ":doc:`Before scheduled date reservation `" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/reservation_methods/before_scheduled_date.rst:3 +msgid "Before scheduled date reservation" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/reservation_methods/before_scheduled_date.rst:9 +msgid "The *Before scheduled date* reservation method allows users to select a specific number of days that act as the maximum number of days **before** a scheduled delivery date, when products included in a sales order (SO) should be reserved." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/reservation_methods/before_scheduled_date.rst:19 +msgid "To set the reservation method to *Before scheduled date*, navigate to :menuselection:`Inventory app --> Configuration --> Operations Types`. Then, select the desired :guilabel:`Operation Type` to configure, or create a new one by clicking :guilabel:`New`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/reservation_methods/before_scheduled_date.rst:23 +msgid "In the :guilabel:`General` tab, locate the :guilabel:`Reservation Method` field, and select :guilabel:`Before scheduled date`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/reservation_methods/before_scheduled_date.rst:34 +msgid "Once selected, a new :guilabel:`Reserve before scheduled date` field appears below. From this field, the number of :guilabel:`days before` and :guilabel:`days before when starred` can be changed from the default `0`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/reservation_methods/before_scheduled_date.rst:41 +msgid "Changing the :guilabel:`days before when starred` value changes the maximum number of days before a scheduled date that products should be reserved if the transfers are starred (favorited)." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/reservation_methods/before_scheduled_date.rst:45 +msgid "Here, the :guilabel:`days before` value is set to `2` days before, and the :guilabel:`days before when starred` value is set to `3`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/reservation_methods/before_scheduled_date.rst:48 +msgid "This means products are reserved two days before the scheduled delivery date for normal orders, and three days before the scheduled delivery date for starred (favorited) transfers." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/reservation_methods/before_scheduled_date.rst:-1 +msgid "Reserve before scheduled date field with set numerical values." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/reservation_methods/before_scheduled_date.rst:55 +msgid "This is the configuration applied for the following workflow found below." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/reservation_methods/before_scheduled_date.rst:58 +msgid "Edit product form" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/reservation_methods/before_scheduled_date.rst:60 +msgid "Before the *Before scheduled date* reservation method can be used, ensure that a *customer lead time* is added to products that plan to be sold with this method." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/reservation_methods/before_scheduled_date.rst:63 +msgid "To do that, navigate to :menuselection:`Inventory app --> Products --> Products`, and select the desired product to configure." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/reservation_methods/before_scheduled_date.rst:66 +msgid "On the product form, click the :guilabel:`Inventory` tab, and under the :guilabel:`Logistics` section, change the value in the :guilabel:`Customer Lead Time` field." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/reservation_methods/before_scheduled_date.rst:69 +msgid "For this example workflow, change it to `5` days." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/reservation_methods/before_scheduled_date.rst:71 +msgid "This sets the scheduled delivery date for this specific product to five days after the creation date of the sales order." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/reservation_methods/before_scheduled_date.rst:-1 +msgid "Product form with customer lead time set in Inventory tab." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/reservation_methods/before_scheduled_date.rst:81 +msgid "To see the *Before scheduled date* reservation method in action, create a new |SO| by navigating to :menuselection:`Sales app --> New`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/reservation_methods/before_scheduled_date.rst:84 +msgid "Add a customer in the :guilabel:`Customer` field, then, in the :guilabel:`Order Lines` tab, click :guilabel:`Add a product`, and select a product from the drop-down menu that has a configured *customer lead time*, to add to the quotation form." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/reservation_methods/before_scheduled_date.rst:88 +msgid "Finally, in the :guilabel:`Quantity` column, adjust the desired quantity of the product to sell." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/reservation_methods/before_scheduled_date.rst:90 +msgid "For this sample workflow, set the :guilabel:`Quantity` to `10`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/reservation_methods/before_scheduled_date.rst:94 +msgid "Click the green :guilabel:`📈 (area graph)` icon on the product line to reveal the product's :guilabel:`Availability` tooltip. This tooltip reveals the reserved number of units for this order. Because the reservation method is set to *Before scheduled date*, the :guilabel:`Reserved` quantity reads `0 Units`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/reservation_methods/before_scheduled_date.rst:99 +msgid "However, below that quantity reads `Available in stock`. This is because the quantity is available, but the scheduled date, for this example workflow, is five days from the order date." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/reservation_methods/before_scheduled_date.rst:102 +msgid "Since reservation is not until two days before the scheduled delivery, it will not reserve the products until then." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/reservation_methods/before_scheduled_date.rst:109 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/reservation_methods/manually.rst:60 +msgid "Instead of revealing the reserved number of units for the order, the :guilabel:`Availability` tooltip reads :guilabel:`Reserved`, and reveals the available number of units (e.g., `0 Units`)." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/reservation_methods/before_scheduled_date.rst:112 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/reservation_methods/manually.rst:63 +msgid "Additionally, unless there is a set replenishment or a live receipt, it also reads :guilabel:`No future availability`, in red text." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/reservation_methods/before_scheduled_date.rst:119 +msgid "Click the :guilabel:`Delivery` smart button to see the delivery order form." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/reservation_methods/before_scheduled_date.rst:121 +msgid "On the delivery order form, the status in the :guilabel:`Product Availability` field is listed as `Available`, in yellow text, instead of green. This is because there is sufficient stock on-hand for this order, but no quantity has been reserved yet." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/reservation_methods/before_scheduled_date.rst:125 +msgid "Note the :guilabel:`Scheduled Date` field, above the :guilabel:`Product Availability` field, displays the date five days from the order creation date. This indicates that the products are not reserved until three days from today's date (two days before the scheduled delivery date)." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/reservation_methods/before_scheduled_date.rst:-1 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/reservation_methods/manually.rst:-1 +msgid "Delivery order form with product availability and reserved quantity." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/reservation_methods/before_scheduled_date.rst:133 +msgid "In the :guilabel:`Operations` tab on the :guilabel:`Product` line, the numbers in the :guilabel:`Demand` column and the :guilabel:`Quantity` column do not match (in this case, the :guilabel:`Demand` column lists `10.00`, while the :guilabel:`Quantity` column lists `0`)." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/reservation_methods/before_scheduled_date.rst:137 +msgid "The :guilabel:`Quantity` column lists `0` because the products aren't reserved until two days *before* their delivery date. Odoo automatically reserves the products once the scheduled date arrives, at which point the :guilabel:`Demand` and :guilabel:`Quantity` columns will match." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/reservation_methods/before_scheduled_date.rst:142 +msgid "If the products in the |SO| should be reserved *sooner* than the scheduled reservation date, the reservation can be manually overridden. To manually reserve the products sooner than scheduled, click :guilabel:`Check Availability` at the top of the form." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/reservation_methods/before_scheduled_date.rst:146 +msgid "This turns the `Available` status in the :guilabel:`Product Availability` field green, and changes the number in the :guilabel:`Quantity` column to match the :guilabel:`Demand` column." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/reservation_methods/before_scheduled_date.rst:153 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/reservation_methods/manually.rst:138 +msgid ":doc:`At confirmation reservation `" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/reservation_methods/manually.rst:3 +msgid "Manual reservation" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/reservation_methods/manually.rst:9 +msgid "Unlike the *At Confirmation* reservation method, the *Manually* reservation method does **not** reserve products automatically." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/reservation_methods/manually.rst:12 +msgid "Instead, once a sales order (SO) is confirmed, product availability **must** be checked manually, and the required quantity **must** be reserved manually." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/reservation_methods/manually.rst:21 +msgid "To set the reservation method to *Manually*, navigate to :menuselection:`Inventory app --> Configuration --> Operations Types`. Then, select the desired :guilabel:`Operation Type` to be configured, or create a new one by clicking :guilabel:`New`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/reservation_methods/manually.rst:25 +msgid "In the :guilabel:`General` tab, locate the :guilabel:`Reservation Method` field, and select :guilabel:`Manually`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/reservation_methods/manually.rst:39 +msgid "To see the *Manually* reservation method in action, create a new |SO| by navigating to :menuselection:`Sales app --> New`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/reservation_methods/manually.rst:48 +msgid "Click the green :guilabel:`📈 (area graph)` icon on the product line to reveal the product's :guilabel:`Availability` tooltip. This tooltip reveals the reserved number of units for this order. Because the reservation method is set to *Manually*, the :guilabel:`Reserved` quantity reads `0 Units`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/reservation_methods/manually.rst:53 +msgid "However, below that quantity reads `Available in stock`. This is because the quantity is available, but must be manually reserved." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/reservation_methods/manually.rst:70 +msgid "Once the |SO| is confirmed, navigate to the :menuselection:`Inventory app`, and locate the :guilabel:`Delivery Orders` card on the :guilabel:`Inventory Overview` page." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/reservation_methods/manually.rst:73 +msgid "The :guilabel:`Delivery Orders` card displays the current status of live orders, including those with a :guilabel:`Waiting` status. Orders with this status indicate that the products in those orders have either not been reserved yet, or are not in stock at all." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/reservation_methods/manually.rst:-1 +msgid "Delivery orders task card with waiting status orders." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/reservation_methods/manually.rst:81 +msgid "To see the |SO| created previously, click the :guilabel:`(#) Waiting` button on the card (in this case, `8 Waiting`)." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/reservation_methods/manually.rst:84 +msgid "Locate the delivery order (DO) tied to the |SO| that was previously created, and click the line to view it." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/reservation_methods/manually.rst:87 +msgid "On the :guilabel:`Delivery Order` form, the status in the :guilabel:`Product Availability` field is listed as `Available`, in yellow text, instead of green. This is because there is sufficient stock on hand for this order, but no quantity has been reserved yet." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/reservation_methods/manually.rst:91 +msgid "In the :guilabel:`Operations` tab, on the :guilabel:`Product` line, the numbers in the :guilabel:`Demand` column and the :guilabel:`Quantity` column do *not* match." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/reservation_methods/manually.rst:94 +msgid "In this case, the :guilabel:`Demand` column lists `10.00`, while the :guilabel:`Quantity` column lists `0`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/reservation_methods/manually.rst:101 +msgid "To manually reserve the specified quantity of the product for this order, click the :guilabel:`Check Availability` button at the top of the form. Doing so turns the `Available` status in the :guilabel:`Product Availability` field green, and changes the number in the :guilabel:`Quantity` column to match the :guilabel:`Demand` column." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/reservation_methods/manually.rst:106 +msgid "This is because there is sufficient quantity in stock to reserve for the order." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/reservation_methods/manually.rst:111 +msgid "Multiple orders with a *Waiting* status can be manually reserved at the same time, and set to *Ready* status." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/reservation_methods/manually.rst:114 +msgid "To do that, open the :menuselection:`Inventory` app, which reveals the :guilabel:`Inventory Overview` page. The :guilabel:`Inventory Overview` page is also accessible by navigating to :menuselection:`Inventory app --> Overview`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/reservation_methods/manually.rst:118 +msgid "From the :guilabel:`Inventory Overview` page, click the :guilabel:`(#) Waiting` button on the :guilabel:`Delivery Orders` card." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/reservation_methods/manually.rst:121 +msgid "Then, tick the checkboxes to the left of each desired order, or tick the checkbox in the header row, to the far-left, to select all orders on the page at once." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/reservation_methods/manually.rst:124 +msgid "Then, click the :guilabel:`Check Availability` button at the top of the page." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/reservation_methods/manually.rst:126 +msgid "If the products included in every selected order have enough stock on-hand, this reserves the products, and moves the order into :guilabel:`Ready` status. Upon receiving a :guilabel:`Ready` status, the order disappears from the :guilabel:`Waiting` list." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/reservation_methods/manually.rst:130 +msgid "If there is *not* enough stock on-hand, the order retains its current status, and remains on the list." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/reservation_methods/manually.rst:0 +msgid "List of orders in waiting status and check availability button." +msgstr "" + #: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration.rst:5 msgid "Setup and configuration" msgstr "" @@ -6460,6 +7704,7 @@ msgstr "" msgid "Once logged into the Starshipit account, navigate to :menuselection:`Settings --> Pickup address`, and fill in the :guilabel:`Pickup address`. Ensure this field matches the warehouse address." msgstr "" +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/starshipit_shipping.rst:-1 #: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/starshipit_shipping.rst:-1 msgid "Adding addresses in the Starshipit settings." msgstr "" @@ -7313,8 +8558,7 @@ msgid "Set the :guilabel:`Package Use` field to :guilabel:`Reusable Box`." msgstr "" #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/cluster_picking.rst:86 -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/removal_strategies.rst:172 -msgid ":ref:`Packages `" +msgid ":doc:`Packages <../../product_management/product_tracking/package>`" msgstr "" #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/cluster_picking.rst:89 @@ -8298,179 +9542,6 @@ msgstr "" msgid "Default warehouse location on employee form." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/usage.rst:3 -msgid "Packages and packagings" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/usage.rst:5 -msgid "In Odoo, there are a variety of ways to specify the amount of products being bought, stocked, and sold. *Packages* and *packagings* are all available to streamline inventory flows, allowing for a variety of configurations for products as they enter and leave the warehouse." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/usage.rst:14 -msgid "Packages are a physical container that holds one or several products from a picking, typically used for outgoing deliveries or internal transfers. Packages can be a reusable or disposable (shipping) box, and are **not** specific to a product." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/usage.rst:18 -msgid "Reusable boxes temporarily hold products during a picking to be brought to either a packing or shipping area. Disposable boxes are the actual shipping containers (e.g. cardboard boxes, envelopes, shipping bags, etc). These are used to ship the products out to customers." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/usage.rst:22 -msgid "Multiple items in a sales order (SO) can be separated into different packages to accommodate the products. For example, an :abbr:`SO (Sales Order)` that has 20 boxes of pencils and 4 boxes of erasers can be separated into two separate packages, each containing 10 boxes of pencils and 2 boxes of erasers." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/usage.rst:28 -msgid "Products do *not* have to be divided equally. Products can be divided into as many packages that are needed to accommodate the :abbr:`SO (Sales Order)`." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/usage.rst:31 -msgid "In Odoo, the quantity of products in each package needs to be recorded, so there is a full history for each product, including which package each item is shipped out in." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/usage.rst:34 -msgid "To use this method, ensure the :guilabel:`Packages` option is enabled, by navigating to :menuselection:`Inventory app --> Configuration --> Settings --> Operations`. Click the :guilabel:`Packages` check box, and then :guilabel:`Save` to activate the feature." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/usage.rst:38 -msgid "On a delivery order, assign which package to use by clicking on the :guilabel:`≣ (Detailed Operations)` icon to the right of each product in the :guilabel:`Operations` tab." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/usage.rst:-1 -msgid "Find detailed operations icon to the right on the product line." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/usage.rst:45 -msgid "Clicking the :guilabel:`≣ (Detailed Operations)` icon of a product reveals a pop-up window. In this window, the :guilabel:`Product` name, :guilabel:`Demand`, and :guilabel:`Quantity Done` are clearly displayed above the customizable product line." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/usage.rst:49 -msgid "Here, the warehouse location the product is coming from can be modified, in addition to the :guilabel:`Source Package` and :guilabel:`Destination Package`, which represents what package(s) the product(s) will be packaged into." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/usage.rst:53 -msgid "Click :guilabel:`Add a line` to include each additional package used. Enter the desired amount in the :guilabel:`Done` field to specify the amount of products that will go into the :guilabel:`Destination Package`." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/usage.rst:58 -msgid "Multiple packages in a single delivery" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/usage.rst:60 -msgid "Although a :abbr:`DO (Delivery Order)` is typically associated with a single package, orders can be split by clicking the :guilabel:`≣ (Detailed Operations)` icon next to the products on an :abbr:`SO (Sales Order)` line. This opens the :guilabel:`Detailed Operations` window with an editable table to specify which products are intended for which package." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/usage.rst:66 -msgid "To package 10 boxes of pencils with 2 boxes of erasers from the same :abbr:`SO (Sales Order)`, begin by navigating to the :abbr:`DO (Delivery Order)`. Then, select the :guilabel:`≣ (four horizontal lines)` icon to the right of the product, `Box of Pencils`. Clicking the icon opens the :guilabel:`Detailed Operations` window that is used to detail how products, like the 20 `Box of Pencils`, are packaged." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/usage.rst:72 -msgid "Type in `10` under the :guilabel:`Done` field to package 10 products into the :guilabel:`Destination Package`. To specify the destination package, type the name of an existing package (such as `PACK0000006`) under the field, :guilabel:`Destination Package`. If the package does not exist, Odoo displays the :guilabel:`Create` button to create a new package. Click :guilabel:`Add a line` to assign the remaining products in another package, `PACK0000007`." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/usage.rst:0 -msgid "Detailed operations pop-up where the amount of product going in a pack can be specified." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/usage.rst:82 -msgid "Select :guilabel:`Detailed Operations` on the product line for `Box of Erasers` and similarly set 2 :guilabel:`Done` products to `PACK0000006` and `PACK0000007` each." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/usage.rst:0 -msgid "Put in pack button to match the done amount matches the demand." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/usage.rst:89 -msgid "Once all the products for each line have been entered, click :guilabel:`Confirm` to return to the :abbr:`DO (Delivery Order)`." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/usage.rst:92 -msgid "The :guilabel:`Done` quantity on the :abbr:`DO (Delivery Order)` updates as products are selected for each package. When the :guilabel:`Done` amount matches the :guilabel:`Demand` amount, click the :guilabel:`Validate` button to complete the delivery order." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/usage.rst:97 -msgid "The :guilabel:`Put In Pack` button is intended to quickly package all products in the :abbr:`DO (Delivery Order)` into one new package. The option to rename the package, or modify its contents, is available in the :guilabel:`Detailed Operations` pop-up." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/usage.rst:101 -msgid "Clicking on the :guilabel:`Packages` smart button in the upper-right corner of the delivery order reveals a separate page, showing all the packages used in that :abbr:`DO (Delivery Order)`." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/usage.rst:105 -msgid "Packagings" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/usage.rst:107 -msgid "*Packaging* is product specific, and refers to a disposable container that holds several units of a specific product. Unlike packages, packagings cannot be reusable, and each specific packaging must be defined on the individual product form." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/usage.rst:111 -msgid "For example, different packages for cans of soda can be configured as a 6-pack, a 12-pack, or a case of 36. Each flavor of soda would need a `6`, `12`, and `36` can packaging configured on the individual product since packagings are product specific, not generic." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/usage.rst:116 -msgid "Set up packagings" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/usage.rst:118 -msgid "To use packagings, ensure the :guilabel:`Product Packagings` feature is enabled. To do that, navigate to :menuselection:`Inventory app --> Configuration --> Settings`. Then, under the :guilabel:`Products` heading, check the box next to :guilabel:`Product Packagings`, and click :guilabel:`Save`." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/usage.rst:123 -msgid "In Odoo, product packagings are used on sales/purchase orders and inventory transfers." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/usage.rst:125 -msgid "Next, to create packagings, navigate to :menuselection:`Inventory app --> Products --> Products` and click on the desired product, then click :guilabel:`Edit` on the product page." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/usage.rst:128 -msgid "Under the :guilabel:`Inventory` tab, scroll down to the :guilabel:`Packaging` section, and click :guilabel:`Add a line`. Then, a pop-up window appears, in which the following information for each packaging should be entered:" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/usage.rst:132 -msgid ":guilabel:`Packaging`: name of packaging that appears on sales/purchase orders as a packaging option for the product" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/usage.rst:134 -msgid ":guilabel:`Contained quantity`: amount of product in the packaging" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/usage.rst:135 -msgid ":guilabel:`Barcode`: identifier used with the :ref:`Barcode app ` to trace the packaging of a product during stock moves or pickings. Leave blank if not in use" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/usage.rst:141 -msgid "Create a packaging type for 6 cans of the product, `Grape Soda`, by naming the :guilabel:`Packaging` to `6-pack` and setting the :guilabel:`Contained quantity` to `6` in the pop-up window that appears after clicking on :guilabel:`Add a line`." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/usage.rst:149 -msgid "When all the necessary information has been entered, either click :guilabel:`Save & Close` to save the packaging and return to the product detail form, or :guilabel:`Save & New` to save the packaging and create another one in a fresh pop-up window." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/usage.rst:154 -msgid "View all product packagings in the :guilabel:`Inventory` tab of the product form." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/usage.rst:0 -msgid "Show packaging and contained quantities, specified on the product page form in the\n" -"Inventory tab." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/usage.rst:162 -msgid "View all packagings" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/usage.rst:164 -msgid "To view all packagings that have been created, go to :menuselection:`Inventory app --> Configuration --> Product Packagings`. Doing so reveals the :guilabel:`Product Packagings` page with a complete list of all packagings that have been created for all products. Create new packagings by clicking :guilabel:`Create`." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/usage.rst:170 -msgid "Two soda products, `Grape Soda` and `Diet Coke`, have three types of packaging configured. On the :guilabel:`Product Packagings` page, each product can sold as a `6-Pack` that contains 6 products, `12-Pack` of 12 products, or a `Case` of 32 products." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/usage.rst:181 -msgid "When creating a sales order in the :menuselection:`Sales` app, specify the packagings that should be used for the product(s). The chosen packaging is displayed on the :abbr:`SO (Sales Order)` under the :guilabel:`Package` field." -msgstr "" - #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/wave_transfers.rst:3 msgid "Process wave transfers" msgstr "" @@ -9573,6 +10644,7 @@ msgstr "" msgid "The first stage of a replenishment order is processing the delivery from the warehouse that the product is being transferred from. On the :menuselection:`Inventory` dashboard, select the :guilabel:`X to Process` button on the :guilabel:`Delivery Orders` card for the outgoing warehouse, then the delivery order created for the replenishment. On the delivery order page, click the :guilabel:`Check Availability` button in the top left to reserve the quantity of the product to be transferred. Once the delivery has been dispatched, click the :guilabel:`Validate` button to register the quantities shipped." msgstr "" +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/warehouse_replenishment_transfer.rst:-1 #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/warehouse_replenishment_transfer.rst:-1 msgid "The delivery orders card for the outgoing warehouse." msgstr "" @@ -10329,6 +11401,10 @@ msgstr "" msgid "Enable the packages feature." msgstr "" +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/removal_strategies.rst:172 +msgid ":doc:`Packages <../product_management/product_tracking/package>`" +msgstr "" + #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/removal_strategies.rst:173 msgid ":doc:`2-step delivery <../shipping_receiving/daily_operations/receipts_delivery_two_steps>`" msgstr "" @@ -10409,13 +11485,6 @@ msgstr "" msgid "To use closest location, set the removal strategy on the parent location, 'WH/Stock'." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/removal_strategies/closest_location.rst:65 -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/removal_strategies/fefo.rst:69 -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/removal_strategies/fifo.rst:47 -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/removal_strategies/least_packages.rst:30 -msgid "Workflow" -msgstr "" - #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/removal_strategies/closest_location.rst:67 msgid "To see how the closest location removal strategy works, consider the following example, featuring the popular product, `iPhone charger`, which is stored in `WH/Stock/Shelf 1`, `WH/Stock/Shelf 2`, and `WH/Stock/Shelf 3`." msgstr "" @@ -10888,130 +11957,246 @@ msgstr "" msgid "`Odoo Tutorials: Managing Equipment Maintenance `_" msgstr "" -#: ../../content/applications/inventory_and_mrp/maintenance/equipment_management.rst:5 -msgid "Equipment management" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/maintenance/equipment_management/add_new_equipment.rst:3 +#: ../../content/applications/inventory_and_mrp/maintenance/add_new_equipment.rst:3 msgid "Add new equipment" msgstr "" -#: ../../content/applications/inventory_and_mrp/maintenance/equipment_management/add_new_equipment.rst:7 +#: ../../content/applications/inventory_and_mrp/maintenance/add_new_equipment.rst:7 msgid "In Odoo, *equipment* refers to any item that is used in everyday operations, including the manufacturing of products. This can mean a piece of machinery on a production line, a tool that is used in different locations, or a computer in an office space. Equipment registered in Odoo can be owned by the company that uses the Odoo database, or by a third party, such as a vendor in the case of equipment rentals." msgstr "" -#: ../../content/applications/inventory_and_mrp/maintenance/equipment_management/add_new_equipment.rst:13 +#: ../../content/applications/inventory_and_mrp/maintenance/add_new_equipment.rst:13 msgid "Using Odoo *Maintenance*, it is possible to track individual pieces of equipment, along with information about their maintenance requirements. To add a new piece of equipment, navigate to the :guilabel:`Maintenance` module, select :menuselection:`Equipments --> Machines & Tools --> Create`, and configure the equipment as follows:" msgstr "" -#: ../../content/applications/inventory_and_mrp/maintenance/equipment_management/add_new_equipment.rst:18 +#: ../../content/applications/inventory_and_mrp/maintenance/add_new_equipment.rst:18 msgid ":guilabel:`Equipment Name`: the product name of the piece of equipment" msgstr "" -#: ../../content/applications/inventory_and_mrp/maintenance/equipment_management/add_new_equipment.rst:19 +#: ../../content/applications/inventory_and_mrp/maintenance/add_new_equipment.rst:19 msgid ":guilabel:`Equipment Category`: the category that the equipment belongs to; for example, computers, machinery, tools, etc.; new categories can be created by navigating to :menuselection:`Configuration --> Equipment Categories` and clicking :guilabel:`Create`" msgstr "" -#: ../../content/applications/inventory_and_mrp/maintenance/equipment_management/add_new_equipment.rst:22 +#: ../../content/applications/inventory_and_mrp/maintenance/add_new_equipment.rst:22 msgid ":guilabel:`Company`: the company that owns the equipment; again, this can be the company that uses the Odoo database, or a third-party company" msgstr "" -#: ../../content/applications/inventory_and_mrp/maintenance/equipment_management/add_new_equipment.rst:24 +#: ../../content/applications/inventory_and_mrp/maintenance/add_new_equipment.rst:24 msgid ":guilabel:`Used By`: specify if the equipment is used by a specific employee, department, or both; select :guilabel:`Other` to specify both an employee and a department" msgstr "" -#: ../../content/applications/inventory_and_mrp/maintenance/equipment_management/add_new_equipment.rst:26 +#: ../../content/applications/inventory_and_mrp/maintenance/add_new_equipment.rst:26 msgid ":guilabel:`Maintenance Team`: the team responsible for servicing the equipment; new teams can be created by navigating to :menuselection:`Configuration --> Maintenance Teams` and selecting :guilabel:`Create`; the members of each team can also be assigned from this page" msgstr "" -#: ../../content/applications/inventory_and_mrp/maintenance/equipment_management/add_new_equipment.rst:29 +#: ../../content/applications/inventory_and_mrp/maintenance/add_new_equipment.rst:29 msgid ":guilabel:`Technician`: the person responsible for servicing the equipment; this can be used to assign a specific individual in the event that no maintenance team is assigned or when a specific member of the assigned team should always be responsible for the equipment; any person added to Odoo as a user can be assigned as a technician" msgstr "" -#: ../../content/applications/inventory_and_mrp/maintenance/equipment_management/add_new_equipment.rst:33 +#: ../../content/applications/inventory_and_mrp/maintenance/add_new_equipment.rst:33 msgid ":guilabel:`Used in location`: the location where the equipment is used; this is a simple text field that can be used to specify locations that are not work centers, like an office, for example" msgstr "" -#: ../../content/applications/inventory_and_mrp/maintenance/equipment_management/add_new_equipment.rst:36 +#: ../../content/applications/inventory_and_mrp/maintenance/add_new_equipment.rst:36 msgid ":guilabel:`Work Center`: if the equipment is used at a work center, specify it here; equipment can also be assigned to a work center by navigating to :menuselection:`Maintenance --> Equipments --> Work Centers`, selecting a work center or creating a new one using the :guilabel:`Create` button, and clicking the :guilabel:`Equipment` tab on the work center form" msgstr "" -#: ../../content/applications/inventory_and_mrp/maintenance/equipment_management/add_new_equipment.rst:-1 +#: ../../content/applications/inventory_and_mrp/maintenance/add_new_equipment.rst:-1 msgid "An example of a fully configured new equipment form." msgstr "" -#: ../../content/applications/inventory_and_mrp/maintenance/equipment_management/add_new_equipment.rst:46 +#: ../../content/applications/inventory_and_mrp/maintenance/add_new_equipment.rst:46 msgid "Include additional product information" msgstr "" -#: ../../content/applications/inventory_and_mrp/maintenance/equipment_management/add_new_equipment.rst:48 +#: ../../content/applications/inventory_and_mrp/maintenance/add_new_equipment.rst:48 msgid "The :guilabel:`Product Information` tab at the bottom of the form can be used to provide further details about the piece of equipment:" msgstr "" -#: ../../content/applications/inventory_and_mrp/maintenance/equipment_management/add_new_equipment.rst:51 +#: ../../content/applications/inventory_and_mrp/maintenance/add_new_equipment.rst:51 msgid ":guilabel:`Vendor`: the vendor that the equipment was purchased from" msgstr "" -#: ../../content/applications/inventory_and_mrp/maintenance/equipment_management/add_new_equipment.rst:52 +#: ../../content/applications/inventory_and_mrp/maintenance/add_new_equipment.rst:52 msgid ":guilabel:`Vendor Reference`: the reference code assigned to the vendor" msgstr "" -#: ../../content/applications/inventory_and_mrp/maintenance/equipment_management/add_new_equipment.rst:53 +#: ../../content/applications/inventory_and_mrp/maintenance/add_new_equipment.rst:53 msgid ":guilabel:`Model`: the specific model of the piece of equipment" msgstr "" -#: ../../content/applications/inventory_and_mrp/maintenance/equipment_management/add_new_equipment.rst:54 +#: ../../content/applications/inventory_and_mrp/maintenance/add_new_equipment.rst:54 msgid ":guilabel:`Serial Number`: the unique serial number of the equipment" msgstr "" -#: ../../content/applications/inventory_and_mrp/maintenance/equipment_management/add_new_equipment.rst:55 +#: ../../content/applications/inventory_and_mrp/maintenance/add_new_equipment.rst:55 msgid ":guilabel:`Effective Date`: the date that the equipment became available for use; this is used to calculate the :abbr:`MTBF (Mean Time Between Failures)`" msgstr "" -#: ../../content/applications/inventory_and_mrp/maintenance/equipment_management/add_new_equipment.rst:57 +#: ../../content/applications/inventory_and_mrp/maintenance/add_new_equipment.rst:57 msgid ":guilabel:`Cost`: the amount the equipment was purchased for" msgstr "" -#: ../../content/applications/inventory_and_mrp/maintenance/equipment_management/add_new_equipment.rst:58 +#: ../../content/applications/inventory_and_mrp/maintenance/add_new_equipment.rst:58 msgid ":guilabel:`Warranty Expiration Date`: the date on which the equipment's warranty will expire" msgstr "" -#: ../../content/applications/inventory_and_mrp/maintenance/equipment_management/add_new_equipment.rst:-1 +#: ../../content/applications/inventory_and_mrp/maintenance/add_new_equipment.rst:-1 msgid "The product information tab for the new piece of equipment." msgstr "" -#: ../../content/applications/inventory_and_mrp/maintenance/equipment_management/add_new_equipment.rst:65 +#: ../../content/applications/inventory_and_mrp/maintenance/add_new_equipment.rst:65 msgid "Add maintenance details" msgstr "" -#: ../../content/applications/inventory_and_mrp/maintenance/equipment_management/add_new_equipment.rst:67 +#: ../../content/applications/inventory_and_mrp/maintenance/add_new_equipment.rst:67 msgid "The :guilabel:`Maintenance` tab includes information that can be useful to maintenance teams:" msgstr "" -#: ../../content/applications/inventory_and_mrp/maintenance/equipment_management/add_new_equipment.rst:69 +#: ../../content/applications/inventory_and_mrp/maintenance/add_new_equipment.rst:69 msgid ":guilabel:`Preventive Maintenance Frequency`: specifies how often maintenance should be performed to prevent equipment failure" msgstr "" -#: ../../content/applications/inventory_and_mrp/maintenance/equipment_management/add_new_equipment.rst:71 +#: ../../content/applications/inventory_and_mrp/maintenance/add_new_equipment.rst:71 msgid ":guilabel:`Maintenance Duration`: the amount of time required to fix the equipment when it fails" msgstr "" -#: ../../content/applications/inventory_and_mrp/maintenance/equipment_management/add_new_equipment.rst:72 +#: ../../content/applications/inventory_and_mrp/maintenance/add_new_equipment.rst:72 msgid ":guilabel:`Expected Mean Time Between Failure`: the average amount of time that the equipment is expected to operate before failing" msgstr "" -#: ../../content/applications/inventory_and_mrp/maintenance/equipment_management/add_new_equipment.rst:-1 +#: ../../content/applications/inventory_and_mrp/maintenance/add_new_equipment.rst:-1 msgid "The maintenance tab for the new piece of equipment." msgstr "" -#: ../../content/applications/inventory_and_mrp/maintenance/equipment_management/add_new_equipment.rst:80 +#: ../../content/applications/inventory_and_mrp/maintenance/add_new_equipment.rst:80 msgid "The :guilabel:`Maintenance` tab also includes sections for :guilabel:`Mean Time Between Failure`, :guilabel:`Estimated Next Failure`, :guilabel:`Latest Failure`, and :guilabel:`Mean Time To Repair`. These values are calculated automatically based on maintenance requests if any exist." msgstr "" -#: ../../content/applications/inventory_and_mrp/maintenance/equipment_management/add_new_equipment.rst:86 +#: ../../content/applications/inventory_and_mrp/maintenance/add_new_equipment.rst:86 msgid "To see the maintenance requests for a piece of equipment, go to the page for the equipment and select :guilabel:`Maintenance` in the top right corner of the form." msgstr "" +#: ../../content/applications/inventory_and_mrp/maintenance/maintenance_requests.rst:3 +msgid "Maintenance requests" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/maintenance/maintenance_requests.rst:7 +msgid "In order to keep equipment and work centers functioning properly, it is often necessary to perform maintenance on them. This can include preventive maintenance, intended to prevent equipment from breaking down, or corrective maintenance, which is used to fix equipment that is broken or otherwise unusable." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/maintenance/maintenance_requests.rst:12 +msgid "In Odoo *Maintenance*, users can create *maintenance requests* to schedule and track the progress of equipment and work center maintenance." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/maintenance/maintenance_requests.rst:16 +msgid "Create maintenance request" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/maintenance/maintenance_requests.rst:18 +msgid "To create a new maintenance request, navigate to :menuselection:`Maintenance app --> Maintenance --> Maintenance Requests`, and click :guilabel:`New`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/maintenance/maintenance_requests.rst:21 +msgid "Begin filling out the form by entering a descriptive title in the :guilabel:`Request` field (e.g., `Drill not working`)." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/maintenance/maintenance_requests.rst:24 +msgid "The :guilabel:`Created By` field auto-populates with the user creating the request, but a different user can be selected by clicking on the drop-down menu." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/maintenance/maintenance_requests.rst:27 +msgid "In the :guilabel:`For` drop-down menu, select :guilabel:`Equipment` if the maintenance request is being created for a piece of equipment, or :guilabel:`Work Center` if it is being created for a work center." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/maintenance/maintenance_requests.rst:31 +msgid "Depending on the option selected in the :guilabel:`For` field, the next field is titled either :guilabel:`Equipment` or :guilabel:`Work Center`. Using the drop-down menu for either field, select a piece of equipment or a work center." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/maintenance/maintenance_requests.rst:35 +msgid "If the *Custom Maintenance Worksheets* setting is enabled in the *Maintenance* app's settings, a :guilabel:`Worksheet Template` field appears below the :guilabel:`Equipment` or :guilabel:`Work Center` field. If necessary, use this field to select a worksheet to be filled out by the employee performing the maintenance." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/maintenance/maintenance_requests.rst:40 +msgid "The next field is titled :guilabel:`Request Date`, and is set by default to the date on which the maintenance request is created. This date cannot be changed by the user." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/maintenance/maintenance_requests.rst:43 +msgid "In the :guilabel:`Maintenance Type` field, select the :guilabel:`Corrective` option if the request is intended to fix an existing issue, or the :guilabel:`Preventive` option if the request is intended to prevent issues from occurring in the future." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/maintenance/maintenance_requests.rst:47 +msgid "If the request is being created to address an issue that arose during a specific manufacturing order (MO), select it in the :guilabel:`Manufacturing Order` field." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/maintenance/maintenance_requests.rst:50 +msgid "If an |MO| was selected in the :guilabel:`Manufacturing Order` field, a :guilabel:`Work Order` field appears below it. If the issue arose during a specific work order, specify it in this field." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/maintenance/maintenance_requests.rst:53 +msgid "In the :guilabel:`Team` field, select the maintenance team that is responsible for managing the request. If a specific team member is responsible, select them in the :guilabel:`Responsible` field." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/maintenance/maintenance_requests.rst:56 +msgid "The :guilabel:`Scheduled Date` field is used to specify the date on which maintenance should take place, and the time it should begin. Choose a date by clicking on the field to open a calendar in a pop-up window, and then select a day on the calendar. Enter an hour and minute in the two fields below the calendar, and click :guilabel:`Apply` to save the date and time." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/maintenance/maintenance_requests.rst:61 +msgid "The :guilabel:`Duration` field is used to specify the time it takes to complete the maintenance request. Use the text-entry field to enter the time in a `00:00` format." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/maintenance/maintenance_requests.rst:64 +msgid "If :guilabel:`Work Center` was selected in the :guilabel:`For` field, a :guilabel:`Block Workcenter` checkbox appears below the :guilabel:`Duration` field. Enable the checkbox to prevent work orders or other maintenance from being scheduled at the specified work center while the maintenance request is being processed." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/maintenance/maintenance_requests.rst:69 +msgid "The :guilabel:`Priority` field is used to communicate the importance (or urgency) of the maintenance request. Assign the request a priority between zero and three :guilabel:`⭐⭐⭐ (stars)`, by clicking on the desired star number. Requests assigned a higher priority appear above those with a lower priority, on the Kanban board used to track the progression of maintenance requests." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/maintenance/maintenance_requests.rst:74 +msgid "In the :guilabel:`Notes` tab at the bottom of the form, enter any relevant details about the maintenance request (why the maintenance issue arose, when it occurred, etc.)." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/maintenance/maintenance_requests.rst:77 +msgid "The :guilabel:`Instructions` tab is used to include instructions for how maintenance should be performed. Select one of the three options, and then include the instructions as detailed below:" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/maintenance/maintenance_requests.rst:80 +msgid ":guilabel:`PDF`: click the :guilabel:`Upload your file` button to open the device's file manager, and then select a file to upload." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/maintenance/maintenance_requests.rst:82 +msgid ":guilabel:`Google Slide`: enter a :guilabel:`Google Slide link` in the text-entry field that appears after the option is selected." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/maintenance/maintenance_requests.rst:84 +msgid ":guilabel:`Text`: enter the instructions in the text-entry field that appears after the option is selected." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/maintenance/maintenance_requests.rst:-1 +msgid "A maintenance request form filled out for a piece of equipment." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/maintenance/maintenance_requests.rst:92 +msgid "Process maintenance request" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/maintenance/maintenance_requests.rst:94 +msgid "Once a maintenance request has been created, it appears in the *New Request* stage of the *Maintenance Requests* page, which can be accessed by navigating to :menuselection:`Maintenance app --> Maintenance --> Maintenance Requests`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/maintenance/maintenance_requests.rst:98 +msgid "Maintenance requests can be moved to different stages by dragging and dropping them. They can also be moved by clicking on a request to open it in a new page, and then selecting the desired stage from the stage indicator bar, located above the top-right corner of the request's form." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/maintenance/maintenance_requests.rst:102 +msgid "Successful maintenance requests should be moved to the :guilabel:`Repaired` stage, indicating that the specified piece of equipment or work center is repaired." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/maintenance/maintenance_requests.rst:105 +msgid "Failed maintenance requests should be moved to the :guilabel:`Scrap` stage, indicating the specified piece of equipment, or work center, could not be repaired, and must instead be scrapped." +msgstr "" + #: ../../content/applications/inventory_and_mrp/manufacturing.rst:8 msgid "Manufacturing" msgstr "" @@ -11029,7 +12214,7 @@ msgid "`Odoo Tutorials: Barcode Scanner msgstr "" #: ../../content/applications/inventory_and_mrp/manufacturing.rst:17 -msgid ":doc:`IoT Boxes (MES) `" +msgid ":doc:`IoT Boxes (MES) `" msgstr "" #: ../../content/applications/inventory_and_mrp/manufacturing/management.rst:5 @@ -14275,219 +15460,202 @@ msgid "Manage deals" msgstr "" #: ../../content/applications/inventory_and_mrp/purchase/manage_deals/blanket_orders.rst:3 -msgid "Use blanket orders to create purchase agreements with vendors" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/blanket_orders.rst:5 -msgid "Blanket orders are long-term purchase agreements between a company and a vendor to deliver products on a recurring basis with predetermined pricing. Using blanket orders are useful when products are always purchased from the same vendor, but in different quantities at different times." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/blanket_orders.rst:9 -msgid "By simplifying the ordering process, blanket orders not only save time, they also save money, since they can be advantageous when negotiating bulk pricing with vendors." +msgid "Blanket orders" msgstr "" #: ../../content/applications/inventory_and_mrp/purchase/manage_deals/blanket_orders.rst:13 -msgid ":doc:`calls_for_tenders`" +msgid "Blanket orders are long-term purchase agreements between a company and a vendor to deliver products on a recurring basis with predetermined pricing." msgstr "" #: ../../content/applications/inventory_and_mrp/purchase/manage_deals/blanket_orders.rst:16 +msgid "Blanket orders are helpful when products are consistently purchased from the same vendor, but in different quantities, and at different times." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/blanket_orders.rst:19 +msgid "By simplifying the ordering process, blanket orders not only save time, they also save money, since they can be advantageous when negotiating bulk pricing with vendors." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/blanket_orders.rst:23 msgid "Create a new blanket order" msgstr "" -#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/blanket_orders.rst:18 -msgid "To create blanket orders, the *Purchase Agreements* feature first needs to be enabled in the settings of the *Purchase* app. To do this, go to :menuselection:`Purchase --> Configuration --> Settings`, and under the :guilabel:`Orders` section, click the checkbox next to :guilabel:`Purchase Agreements`. Doing so will enable the ability to create blanket orders, as well as alternative requests for quotation (RFQs)." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/blanket_orders.rst:-1 -msgid "Purchase Agreements enabled in the Purshase app settings." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/blanket_orders.rst:28 -msgid "To create a blanket order, go to :menuselection:`Purchase --> Orders --> blanket orders`, and click :guilabel:`New`. This creates (and navigates to) a new blanket order form." +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/blanket_orders.rst:25 +msgid "To create blanket orders, enable the *Purchase Agreements* feature from the *Purchase* app settings. Navigate to :menuselection:`Purchase app --> Configuration --> Settings`, and under the :guilabel:`Orders` section, click the checkbox for :guilabel:`Purchase Agreements`. Then click :guilabel:`Save` to implement the changes." msgstr "" #: ../../content/applications/inventory_and_mrp/purchase/manage_deals/blanket_orders.rst:31 -msgid "From this new blanket order form, different fields and settings can be configured, so there are pre-determined rules that the recurring long-term agreement must follow:" +msgid "In addition to creating blanket orders, the *Purchase Agreements* setting also allows users to create alternative requests for quotation (RfQs)." msgstr "" -#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/blanket_orders.rst:34 -msgid ":guilabel:`Purchase Representative`: is the user assigned to this specific blanket order. By default, this is the user who created the agreement; the user can be changed directly from the drop-down menu next to this field." +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/blanket_orders.rst:-1 +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/calls_for_tenders.rst:-1 +msgid "Purchase Agreements enabled in the Purchase app settings." msgstr "" -#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/blanket_orders.rst:37 -msgid ":guilabel:`Agreement Type`: is the type of purchase agreement this blanket order is classified as. In Odoo, blanket orders are the only official purchase agreement." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/blanket_orders.rst:39 -msgid ":guilabel:`Vendor`: is the supplier to whom this agreement is tied, either once or on a recurring basis. The vendor can be selected directly from the drop-down menu next to this field." +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/blanket_orders.rst:38 +msgid "To create a blanket order, go to :menuselection:`Purchase app --> Orders --> Blanket Orders`, and click :guilabel:`New`. This opens a new blanket order form." msgstr "" #: ../../content/applications/inventory_and_mrp/purchase/manage_deals/blanket_orders.rst:41 -msgid ":guilabel:`Currency`: is the agreed-upon currency that will be used for this exchange. If multiple currencies have been activated in the database, the currency can be changed from the drop-down menu next to this field." +msgid "Configure the following fields in the new blanket order form to establish predetermined rules for the recurring long-term agreement:" msgstr "" #: ../../content/applications/inventory_and_mrp/purchase/manage_deals/blanket_orders.rst:44 -msgid ":guilabel:`Agreement Deadline`: is the date that this purchase agreement will be set to expire on (if desired). If this blanket order should not expire, leave this field blank." +msgid ":guilabel:`Purchase Representative`: the user assigned to this specific blanket order. By default, this is the user who created the agreement; the user can be changed directly from the drop-down menu next to this field." msgstr "" -#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/blanket_orders.rst:46 -msgid ":guilabel:`Ordering Date`: is the date that this blanket order should be placed on if a new quotation is created directly from the blanket order form. If a new quotation is created, this value will automatically populate the *Order Deadline* field on the :abbr:`RFQ (Request for Quotation)`." +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/blanket_orders.rst:47 +msgid ":guilabel:`Agreement Type`: the type of purchase agreement this blanket order is classified as. In Odoo, blanket orders are the only official purchase agreement." msgstr "" -#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/blanket_orders.rst:50 -msgid ":guilabel:`Delivery Date`: is the expected delivery date that the products included in an :abbr:`RFQ (Request for Quotation)` created directly from the blanket order form will be expected to arrive. If a new quotation is created, this value will automatically populate the *Expected Arrival* field on the :abbr:`RFQ (Request for Quotation)`." +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/blanket_orders.rst:49 +msgid ":guilabel:`Vendor`: the supplier to whom this agreement is tied, either once or on a recurring basis. The vendor can be selected directly from the drop-down menu next to this field." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/blanket_orders.rst:51 +msgid ":guilabel:`Currency`: the agreed-upon currency to be used for this exchange. If multiple currencies have been activated in the database, the currency can be changed from the drop-down menu next to this field." msgstr "" #: ../../content/applications/inventory_and_mrp/purchase/manage_deals/blanket_orders.rst:54 -msgid ":guilabel:`Source Document`: is the source purchase order (PO) that this blanket order will be tied to. If this blanket order should not be tied to any existing :abbr:`POs (Purchase Orders)`, leave this field blank." +msgid ":guilabel:`Agreement Deadline`: the date that this purchase agreement will be set to expire on. If this blanket order should not expire, leave this field blank." msgstr "" -#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/blanket_orders.rst:57 -msgid ":guilabel:`Company`: is the company assigned to this specific blanket order. By default, this is the company that the user creating the blanket order is listed under. If the database is not a multi-company database, this field can not be changed, and will default to the only company listed in the database." +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/blanket_orders.rst:56 +msgid ":guilabel:`Ordering Date`: the date that this blanket order should be placed on if a new quotation is created directly from the blanket order form. If a new quotation is created, this value automatically populates the *Order Deadline* field on the |RfQ|." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/blanket_orders.rst:59 +msgid ":guilabel:`Delivery Date`: the expected delivery date that the products included in an |RfQ| are expected, if created directly from a blanket order form. If a new quotation is created, this value automatically populates the *Expected Arrival* field on the |RfQ|." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/blanket_orders.rst:62 +msgid ":guilabel:`Source Document`: the source purchase order (PO) that this blanket order is tied to. If this blanket order should not be tied to any existing |PO|, leave this field blank." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/blanket_orders.rst:64 +msgid ":guilabel:`Company`: the company assigned to this specific blanket order. By default, this is the company that the user creating the blanket order is listed under. If the database is not a multi-company database, this field **cannot** be changed, and defaults to the only company listed in the database." msgstr "" #: ../../content/applications/inventory_and_mrp/purchase/manage_deals/blanket_orders.rst:-1 msgid "New blanket order purchase agreement with added products." msgstr "" -#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/blanket_orders.rst:66 -msgid "Once all relevant fields have been filled out, click :guilabel:`Add a line` to add products under the :guilabel:`Product` column. Then, change the quantity of each product in the :guilabel:`Quantity` column (if desired), and set a price in the :guilabel:`Unit Price` column." +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/blanket_orders.rst:73 +msgid "Once all relevant fields have been filled out, click :guilabel:`Add a line` to add products under the :guilabel:`Product` column. Then, in the :guilabel:`Quantity` column, change the quantity of each product, and set a price in the :guilabel:`Unit Price` column." msgstr "" -#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/blanket_orders.rst:71 -msgid "When adding products to a new blanket order, the pre-existing prices of products will not be added automatically to the product lines. The prices must be manually assigned by changing the value in the :guilabel:`Unit Price` column to an agreed-upon price with the listed vendor. Otherwise, the price will remain **0**." +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/blanket_orders.rst:78 +msgid "When adding products to a new blanket order, the pre-existing prices of products are not automatically added to the product lines. Instead, the prices **must** be manually assigned, by changing the value in the :guilabel:`Unit Price` column to an agreed-upon price with the listed vendor. Otherwise, the price will remain `0`." msgstr "" -#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/blanket_orders.rst:76 -msgid "To view and change the default purchase agreement settings for blanket orders directly from the blanket order form, click the :guilabel:`internal link (arrow icon)` next to the :guilabel:`Agreement Type` field where :guilabel:`Blanket Order` is listed. This navigates to the blanket order settings." +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/blanket_orders.rst:83 +msgid "To view and change the default purchase agreement settings for blanket orders directly from the blanket order form, click the :guilabel:`➡️ (right arrow)` icon that becomes visible when hovering over the :guilabel:`Agreement Type` field, where :guilabel:`Blanket Order` is listed. This navigates to the blanket order settings." msgstr "" -#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/blanket_orders.rst:81 -msgid "From here, the settings for blanket orders can be edited. Under the :guilabel:`Agreement Type` section, the name of the :guilabel:`Agreement Type` can be changed (if desired), and the :guilabel:`Agreement Selection Type` can be changed, as well. There are two options that can be activated for the type of selection:" +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/blanket_orders.rst:-1 +msgid "Internal link arrow next to Agreement Type field on blanket order form." msgstr "" -#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/blanket_orders.rst:86 -msgid ":guilabel:`Select only one RFQ (exclusive)`: when a purchase order is confirmed, the remaining purchase orders will be canceled." +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/blanket_orders.rst:92 +msgid "From here, the settings for blanket orders can be edited. Under the :guilabel:`Agreement Type` section, the name of the :guilabel:`Agreement Type` can be changed, and the :guilabel:`Agreement Selection Type` can be changed, as well. There are two options that can be activated for the type of selection:" msgstr "" -#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/blanket_orders.rst:88 -msgid ":guilabel:`Select multiple RFQ (non-exclusive)`: when a purchase order is confirmed, remaining purchase orders will ***not** be canceled. Instead, multiple purchase orders are allowed." +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/blanket_orders.rst:97 +msgid ":guilabel:`Select only one RfQ (exclusive)`: when a purchase order is confirmed, the remaining purchase orders are canceled." msgstr "" -#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/blanket_orders.rst:91 -msgid "Under the :guilabel:`Data For New Quotations` section, the settings for how product lines and quantities will be populated on new quotations using this purchase agreeement can be changed next to the :guilabel:`Lines` and :guilabel:`Quantities` fields." +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/blanket_orders.rst:99 +msgid ":guilabel:`Select multiple RfQ (non-exclusive)`: when a purchase order is confirmed, remaining purchase orders are **not** canceled. Instead, multiple purchase orders are allowed." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/blanket_orders.rst:102 +msgid "Under the :guilabel:`Data For New Quotations` section, the :guilabel:`Lines` and :guilabel:`Quantities` fields can be edited. Doing so sets how new quotations should be populated when using this purchase agreement." msgstr "" #: ../../content/applications/inventory_and_mrp/purchase/manage_deals/blanket_orders.rst:-1 msgid "Purchase Agreement type edit screen for blanket orders." msgstr "" -#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/blanket_orders.rst:99 +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/blanket_orders.rst:110 msgid "There are two options that can be activated for :guilabel:`Lines`:" msgstr "" -#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/blanket_orders.rst:101 -msgid ":guilabel:`Use lines of agreement`: when creating a new quotation, the product lines will pre-populate with the same products listed on the blanket order, if said blanket order is chosen on the new quotation." +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/blanket_orders.rst:112 +msgid ":guilabel:`Use lines of agreement`: when creating a new quotation, the product lines pre-populate with the same products listed on the blanket order, if said blanket order is chosen for the new quotation." msgstr "" -#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/blanket_orders.rst:104 -msgid ":guilabel:`Do not create RfQ lines automatically`: when creating a new quotation and selecting an existing blanket order, the settings will carry over to the new quotation, but the product lines will not populate." +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/blanket_orders.rst:115 +msgid ":guilabel:`Do not create RfQ lines automatically`: when creating a new quotation, **and** selecting an existing blanket order, the settings carry over to the new quotation, but the product lines do **not** populate." msgstr "" -#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/blanket_orders.rst:108 +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/blanket_orders.rst:119 msgid "And, there are two options that can be activated for :guilabel:`Quantities`:" msgstr "" -#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/blanket_orders.rst:110 -msgid ":guilabel:`Use quantities of agreement`: when creating a new quotation, the product quantities listed on the blanket order will pre-populate on the product lines, if said blanket order is chosen on the new quotation." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/blanket_orders.rst:113 -msgid ":guilabel:`Set quantities manually`: when creating a new quotation and selecting an existing blanket order, the product lines will pre-populate, but all quantities will be set to **0**. The quantities will need to be manually set by the user." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/blanket_orders.rst:117 -msgid "Once the desired changes have been made (if any), click :guilabel:`New` (via the breadcrumbs, at the top of the page) to navigate back to the blanket order form, and click :guilabel:`Confirm` to save this new purchase agreement. Once confirmed, the blanket order changes from *Draft* to *Ongoing*, meaning this agreement can be selected and used when creating new :abbr:`RFQs (Requests for Quotation)`." +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/blanket_orders.rst:121 +msgid ":guilabel:`Use quantities of agreement`: when creating a new quotation, the product quantities listed on the blanket order pre-populate on the product lines, if said blanket order is chosen for the new quotation." msgstr "" #: ../../content/applications/inventory_and_mrp/purchase/manage_deals/blanket_orders.rst:124 -msgid "After creating and confirming a blanket order, products, quantities, and prices can still be edited, added, and removed from the purchase agreement." +msgid ":guilabel:`Set quantities manually`: when creating a new quotation, **and** selecting an existing blanket order, the product lines pre-populate, but all quantities are set to `0`. The quantities **must** be manually set by the user." msgstr "" #: ../../content/applications/inventory_and_mrp/purchase/manage_deals/blanket_orders.rst:128 -msgid "Create a new :abbr:`RFQ (Request for Quotation)` from the blanket order" +msgid "Once any desired changes have been made, click :guilabel:`New` (via the breadcrumbs, at the top of the page) to navigate back to the blanket order form. Then, click :guilabel:`Confirm` to save this new purchase agreement." msgstr "" -#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/blanket_orders.rst:130 -msgid "After confirming a blanket order, new quotations can be created directly from the blanket order form that will use the rules set on the form and pre-populate the new quotation with the correct information. Additionally, this new quotation will be automatically linked to this blanket order form via the :guilabel:`RFQs/Orders` smart button at the top right of the form." +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/blanket_orders.rst:132 +msgid "Once confirmed, the blanket order's stage (in the upper-right corner) changes from :guilabel:`Draft` to :guilabel:`Ongoing`, meaning this agreement can be selected and used when creating new |RfQs|." msgstr "" -#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/blanket_orders.rst:135 -msgid "To create a new quotation from the blanket order form, click :guilabel:`New Quotation`. This creates (and navigates to) a new :abbr:`RFQ (Request for Quotation)`, that is pre-populated with the correct information, depending on the settings configured on the blanket order form." +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/blanket_orders.rst:136 +msgid "After creating and confirming a blanket order, products, quantities, and prices can still be edited, added, and removed from the purchase agreement." msgstr "" -#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/blanket_orders.rst:139 -msgid "From the new :abbr:`RFQ (Request for Quotation)` form, click :guilabel:`Send by Email` to compose and send an email to the listed vendor; click :guilabel:`Print RFQ` to generate a printable PDF of the quotation; or, once ready, click :guilabel:`Confirm Order` to confirm the purchase order (PO)." +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/blanket_orders.rst:140 +msgid "Create a new |RfQ| from the blanket order" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/blanket_orders.rst:142 +msgid "After confirming a blanket order, new quotations can be created directly from the blanket order form. |RfQs| using this form are pre-populated with information based on the rules set in the form. Additionally, new quotations are automatically linked to this blanket order form, via the :guilabel:`RFQs/Orders` smart button at the top-right of the form." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/blanket_orders.rst:147 +msgid "To create a new quotation from the blanket order form, click the :guilabel:`New Quotation` button. This opens a new |RfQ|, that is pre-populated with the correct information, depending on the settings configured on the blanket order form." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/blanket_orders.rst:151 +msgid "From the new |RfQ| form, click :guilabel:`Send by Email` to compose and send an email to the listed vendor. Click :guilabel:`Print RFQ` to generate a printable PDF of the quotation; or, once ready, click :guilabel:`Confirm Order` to confirm the |PO|." msgstr "" #: ../../content/applications/inventory_and_mrp/purchase/manage_deals/blanket_orders.rst:-1 msgid "New quotation with copied products and rules from blanket order." msgstr "" -#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/blanket_orders.rst:147 -msgid "Once the :abbr:`PO (Purchase Order)` has been confirmed, click back to the blanket order form (via the breadcrumbs, at the top of the page). From the blanket order form, there is now one :abbr:`RFQ (Request for Quotation)` listed in the :guilabel:`RFQs/Orders` smart button at the top right of the form. Click the :guilabel:`RFQs/Orders` smart button to see the purchase order that was just created." +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/blanket_orders.rst:159 +msgid "Once the |PO| has been confirmed, click back to the blanket order form (via the breadcrumbs, at the top of the page). From the blanket order form, there is now one |RfQ| listed in the :guilabel:`RFQs/Orders` smart button at the top-right of the form. Click the :guilabel:`RFQs/Orders` smart button to see the |PO| that was just created." msgstr "" #: ../../content/applications/inventory_and_mrp/purchase/manage_deals/blanket_orders.rst:-1 msgid "RFQs and Orders smart button from blanket order form." msgstr "" -#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/blanket_orders.rst:157 -msgid "Create a new blanket order from an :abbr:`RFQ (Request for Quotation)`" +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/blanket_orders.rst:171 +msgid "Once a blanket order is confirmed, a new vendor line is added under the :guilabel:`Purchase` tab of the products included in the order." msgstr "" -#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/blanket_orders.rst:159 -#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/calls_for_tenders.rst:49 -#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/calls_for_tenders.rst:148 -msgid "To create a new :abbr:`RFQ (Request for Quotation)`, navigate to the :menuselection:`Purchase` app, and click :guilabel:`New`." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/blanket_orders.rst:162 -msgid "Then, add information to the :abbr:`RFQ (Request for Quotation)` form: add a vendor from the drop-down menu next to the :guilabel:`Vendor` field, and click :guilabel:`Add a product` to select a product from the drop-down menu in the :guilabel:`Product` column. Then, set the desired purchase quantity in the :guilabel:`Quantity` column, and change the purchase price in the :guilabel:`Unit Price` column, if desired." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/blanket_orders.rst:168 -msgid "Clicking the :guilabel:`additional options (two-dots)` icon provides additional visibility options to add to the line item. Repeat these steps to add as many additional options as desired, including the :guilabel:`UoM` (Units of Measure) to purchase the products in, and the :guilabel:`Expected Arrival` date." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/blanket_orders.rst:173 -msgid "Before confirming the new quotation and creating a purchase order, click the drop-down menu next to the :guilabel:`Blanket Order` field, and type a new name for the new blanket order. This creates a brand new purchase agreement, and saves the information entered in the fields of the purchase order form, as well as the product information entered on the product lines." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/blanket_orders.rst:178 -msgid "From the new :abbr:`RFQ (Request for Quotation)` form, click :guilabel:`Send by Email` to compose and send an email to the listed vendor; click :guilabel:`Print RFQ` to generate a printable PDF of the quotation; or, once ready, click :guilabel:`Confirm Order` to confirm the :abbr:`PO (purchase order)`." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/blanket_orders.rst:-1 -msgid "New blanket order created directly from quotation." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/blanket_orders.rst:188 -msgid "To see the newly-created blanket order purchase agreement, go to :menuselection:`Orders --> Blanket Orders`, and click into the new blanket order. From here, settings and rules can be changed, if desired." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/blanket_orders.rst:193 -msgid "Blanket orders and replenishment" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/blanket_orders.rst:195 -msgid "Once a blanket order is confirmed, a new vendor line is added under the :guilabel:`Purchase` tab of of the products included in the :abbr:`BO (Blanket Order)`. This makes blanket orders useful with :doc:`automated replenishment <../../purchase/products/reordering>`, because information about the :guilabel:`Vendor`, :guilabel:`Price`, and the :guilabel:`Agreement` are referenced on the vendor line. This information is used to determine where, when, and for what price this product could be replenished." +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/blanket_orders.rst:174 +msgid "This makes blanket orders useful with :doc:`automated replenishment <../../purchase/products/reordering>`, because information about the :guilabel:`Vendor`, :guilabel:`Price`, and the :guilabel:`Agreement` are referenced on the vendor line. This information dictates when, where, and at what price the product should be replenished." msgstr "" #: ../../content/applications/inventory_and_mrp/purchase/manage_deals/blanket_orders.rst:-1 msgid "Product form with replenishment agreement linked to blanket order." msgstr "" +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/blanket_orders.rst:184 +msgid ":doc:`calls_for_tenders`" +msgstr "" + #: ../../content/applications/inventory_and_mrp/purchase/manage_deals/calls_for_tenders.rst:3 msgid "Create alternative requests for quotation for multiple vendors" msgstr "" @@ -14516,10 +15684,6 @@ msgstr "" msgid "To create alternative :abbr:`RFQs (Requests for Quotation)` directly from a quotation, the *Purchase Agreements* feature first needs to be enabled in the settings of the *Purchase* app. To do this, go to :menuselection:`Purchase --> Configuration --> Settings`, and under the :guilabel:`Orders` section, click the checkbox next to :guilabel:`Purchase Agreements`. Doing so will enable the ability to create alternative :abbr:`RFQs (Requests for Quotation)`, as well as the ability to create *blanket orders*." msgstr "" -#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/calls_for_tenders.rst:-1 -msgid "Purchase Agreements enabled in the Purchase app settings." -msgstr "" - #: ../../content/applications/inventory_and_mrp/purchase/manage_deals/calls_for_tenders.rst:37 msgid "To save time on a *call for tender*, custom vendors, prices, and delivery lead times can be set in the :guilabel:`Purchase` tab on a product form. To do so, navigate to :menuselection:`Purchase --> Products --> Products`, and select a product to edit. From the product form, click the :guilabel:`Purchase tab`, then click :guilabel:`Add a line`. From the drop-down menu, choose a vendor to set under the :guilabel:`Vendor` column, and set a :guilabel:`Price` and :guilabel:`Delivery Lead Time` if desired. Clicking the :guilabel:`additional options (two-dots)` icon provides additional visibility options to add to the line item." msgstr "" @@ -14528,6 +15692,11 @@ msgstr "" msgid "Create an :abbr:`RFQ (Request for Quotation)`" msgstr "" +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/calls_for_tenders.rst:49 +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/calls_for_tenders.rst:148 +msgid "To create a new :abbr:`RFQ (Request for Quotation)`, navigate to the :menuselection:`Purchase` app, and click :guilabel:`New`." +msgstr "" + #: ../../content/applications/inventory_and_mrp/purchase/manage_deals/calls_for_tenders.rst:52 #: ../../content/applications/inventory_and_mrp/purchase/manage_deals/calls_for_tenders.rst:151 msgid "Then, add information to the :abbr:`RFQ (Request for Quotation)` form: add a vendor from the drop-down next to the :guilabel:`Vendor` field, and click :guilabel:`Add a product` to select a product from the drop-down menu in the :guilabel:`Product` column. Then, set the desired purchase quantity in the :guilabel:`Quantity` column, and change the purchase price in the :guilabel:`Unit Price` column, if desired." diff --git a/locale/sources/marketing.pot b/locale/sources/marketing.pot index 340f9548b..51694c5fd 100644 --- a/locale/sources/marketing.pot +++ b/locale/sources/marketing.pot @@ -8,7 +8,7 @@ msgid "" msgstr "" "Project-Id-Version: Odoo 17.0\n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2024-03-08 12:48+0000\n" +"POT-Creation-Date: 2024-03-25 16:01+0000\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME \n" "Language-Team: LANGUAGE \n" @@ -34,12 +34,10 @@ msgstr "" #: ../../content/applications/marketing/email_marketing.rst:17 #: ../../content/applications/marketing/email_marketing.rst:219 -#: ../../content/applications/marketing/email_marketing/unsubscriptions.rst:74 msgid ":doc:`/applications/marketing/email_marketing/mailing_lists`" msgstr "" #: ../../content/applications/marketing/email_marketing.rst:18 -#: ../../content/applications/marketing/email_marketing/mailing_lists.rst:136 msgid ":doc:`/applications/marketing/email_marketing/unsubscriptions`" msgstr "" @@ -555,235 +553,420 @@ msgid "Mailing lists" msgstr "" #: ../../content/applications/marketing/email_marketing/mailing_lists.rst:5 -msgid "Mailing lists are important for a number of reasons. Mailing lists can provide valuable leads for sales teams, communicate with focus groups participants, contact consumers directly for useful feedback, and more." +msgid "Mailing lists in Odoo are used for both pre and post sales communications in the *Email Marketing* application. They provide sales teams with qualified lead lists, focus group participants, or current customers that fulfill specific criteria." msgstr "" -#: ../../content/applications/marketing/email_marketing/mailing_lists.rst:10 +#: ../../content/applications/marketing/email_marketing/mailing_lists.rst:9 +msgid "Mailing lists can be generated in Odoo, and exported as a downloadable file, or into the *Knowledge*, *Dashboards*, or *Spreadsheets* applications, or imported via copy/paste or file upload." +msgstr "" + +#: ../../content/applications/marketing/email_marketing/mailing_lists.rst:14 msgid "Create mailing lists" msgstr "" -#: ../../content/applications/marketing/email_marketing/mailing_lists.rst:12 -msgid "To create a mailing list in the *Email Marketing* application, navigate to :menuselection:`Mailing lists --> Mailing lists --> Create`. Clicking :guilabel:`Create` reveals a pop-up window." -msgstr "" - -#: ../../content/applications/marketing/email_marketing/mailing_lists.rst:-1 -msgid "View of the mailing list pop-up in the Odoo Email Marketing application." +#: ../../content/applications/marketing/email_marketing/mailing_lists.rst:16 +msgid "To create a mailing list in the *Email Marketing* application, navigate to :menuselection:`Email Marketing app --> Mailing Lists --> Mailing Lists --> New`." msgstr "" #: ../../content/applications/marketing/email_marketing/mailing_lists.rst:19 -msgid "In the pop-up, name the mailing list and designate if the mailing list should be public with the :guilabel:`Is Public` checkbox." +msgid "Clicking :guilabel:`New` reveals a blank mailing list form." msgstr "" -#: ../../content/applications/marketing/email_marketing/mailing_lists.rst:22 -msgid "The :guilabel:`Is Public` option allows the mailing list to be accessible by recipients in the unsubscription page, making it possible for them to update their subscription preferences." +#: ../../content/applications/marketing/email_marketing/mailing_lists.rst:-1 +msgid "View of the mailing list form in the Odoo Email Marketing application." msgstr "" #: ../../content/applications/marketing/email_marketing/mailing_lists.rst:25 -msgid "After those options have been configured, click :guilabel:`Create` to create the mailing list, which Odoo automatically adds to the :guilabel:`Mailing Lists` page." +msgid "On the form, type a name in the :guilabel:`Mailing List` field at the top." msgstr "" -#: ../../content/applications/marketing/email_marketing/mailing_lists.rst:29 -msgid "Add contacts to a mailing list" +#: ../../content/applications/marketing/email_marketing/mailing_lists.rst:27 +msgid "If the mailing list should be accessible by recipients from the subscription management page, allowing them to update their preferences, tick the box next to :guilabel:`Show In Preferences`." msgstr "" -#: ../../content/applications/marketing/email_marketing/mailing_lists.rst:31 -msgid "After a mailing list has been created (and added to the :guilabel:`Mailing Lists` dashboard), click on the desired mailing list to add contacts to the list." +#: ../../content/applications/marketing/email_marketing/mailing_lists.rst:30 +msgid "In the upper-left corner of the mailing list form, there are two buttons: :guilabel:`Send Mailing` and :guilabel:`Send SMS`." msgstr "" #: ../../content/applications/marketing/email_marketing/mailing_lists.rst:34 -msgid "Clicking the desired mailing list reveals a separate :guilabel:`Mailing List Contacts` page, in which contacts can be added to this specific list by clicking :guilabel:`Create`, and adding contact information directly on a separate contact detail form." +msgid "The :guilabel:`Send SMS` button **only** appears if the *SMS Marketing* application is installed." msgstr "" -#: ../../content/applications/marketing/email_marketing/mailing_lists.rst:38 -msgid "Or, while in the :menuselection:`Email Marketing` application, navigate to :menuselection:`Mailing Lists --> Mailing List Contacts`. Doing so reveals a separate page with all the mailing list contacts in the database." +#: ../../content/applications/marketing/email_marketing/mailing_lists.rst:36 +msgid "Clicking :guilabel:`Send Mailing` reveals a separate page with a blank email template form, which can be filled out by following steps explained in the :doc:`Email Marketing doc <../email_marketing>`." msgstr "" -#: ../../content/applications/marketing/email_marketing/mailing_lists.rst:42 -msgid "From here, click :guilabel:`Create`, and add a contact with the same previous steps. Or, click the :guilabel:`Import` icon (to the right of the :guilabel:`Create` button) to import contacts into the database." +#: ../../content/applications/marketing/email_marketing/mailing_lists.rst:40 +msgid "Clicking :guilabel:`Send SMS` reveals a separate page with a blank SMS template form, which can be filled out by following steps explained in the :doc:`SMS essentials doc <../sms_marketing/essentials/sms_essentials>`." msgstr "" -#: ../../content/applications/marketing/email_marketing/mailing_lists.rst:46 -msgid "Once contacts are in the database, click into the desired contact's detail form, and add the preferred mailing list in the :guilabel:`Mailing List` tab (at the bottom of the contact detail form), by clicking :guilabel:`Add a line`, and selecting the desired mailing list. Multiple mailing lists can be added to a single contact's detail form." +#: ../../content/applications/marketing/email_marketing/mailing_lists.rst:44 +msgid "At the top of the mailing list form is a series of smart buttons that display a variety of metrics related to the specific mailing list. When any of the smart buttons are clicked, a separate page is revealed, showcasing detailed analytics related to that particular statistic." msgstr "" -#: ../../content/applications/marketing/email_marketing/mailing_lists.rst:-1 -msgid "View of a contact detail form with mailing list tab in Odoo Email Marketing." +#: ../../content/applications/marketing/email_marketing/mailing_lists.rst:48 +msgid "The smart buttons available on a mailing list form are:" +msgstr "" + +#: ../../content/applications/marketing/email_marketing/mailing_lists.rst:50 +msgid ":guilabel:`Recipients`: how many people are subscribed to the mailing list" +msgstr "" + +#: ../../content/applications/marketing/email_marketing/mailing_lists.rst:51 +msgid ":guilabel:`Mailings`: how many mailings have been sent using this mailing list" +msgstr "" + +#: ../../content/applications/marketing/email_marketing/mailing_lists.rst:52 +msgid ":guilabel:`% Bounce`: percentage of mailings related to this mailing list that have been bounced back" +msgstr "" + +#: ../../content/applications/marketing/email_marketing/mailing_lists.rst:54 +msgid ":guilabel:`% Opt-out`: percentage of recipients that have opted-out of mailings from this mailing list" msgstr "" #: ../../content/applications/marketing/email_marketing/mailing_lists.rst:56 -msgid "Create new mailing list from contact detail form" +msgid ":guilabel:`% Blacklist`: percentage of recipients that have blacklisted themselves from the mailing list altogether" msgstr "" -#: ../../content/applications/marketing/email_marketing/mailing_lists.rst:58 -msgid "To create a mailing list from a contact detail form, click :guilabel:`Add a line`, and type in the name of a new mailing list in the empty field that appears. Then, select either :guilabel:`Create` or :guilabel:`Create and Edit...`." +#: ../../content/applications/marketing/email_marketing/mailing_lists.rst:59 +msgid "Once all the configurations on the mailing list form are complete, Odoo automatically adds the new mailing list to the :guilabel:`Mailing List` page in the *Email Marketing* app (:menuselection:`Email Marketing app --> Mailing Lists --> Mailing Lists`)." msgstr "" -#: ../../content/applications/marketing/email_marketing/mailing_lists.rst:-1 -msgid "View of the new mailing list drop-down on contact form in Odoo Email Marketing." +#: ../../content/applications/marketing/email_marketing/mailing_lists.rst:64 +msgid "Add contacts to mailing list" msgstr "" #: ../../content/applications/marketing/email_marketing/mailing_lists.rst:66 -msgid "The :guilabel:`Create` option quickly creates the mailing list to the contact detail form, and the list can be configured at a later date. The :guilabel:`Create and Edit...` option creates the mailing list, and reveals a pop-up window, in which the new mailing list can be configured right away." +msgid "In Odoo *Email Marketing*, there are a few different ways to add contacts to a mailing list." msgstr "" -#: ../../content/applications/marketing/email_marketing/mailing_lists.rst:-1 -msgid "View of the create and edit mailing list pop-up in Odoo Email Marketing." +#: ../../content/applications/marketing/email_marketing/mailing_lists.rst:68 +msgid "From the :guilabel:`Mailing Lists` page (:menuselection:`Email Marketing --> Mailing Lists --> Mailing Lists`), click the :guilabel:`Total Contacts` link on the line of the desired mailing list to which contacts should be added." msgstr "" -#: ../../content/applications/marketing/email_marketing/mailing_lists.rst:76 -msgid "Link a mailing list to website (Newsletter blocks)" +#: ../../content/applications/marketing/email_marketing/mailing_lists.rst:72 +msgid "Doing so reveals a separate :guilabel:`Mailing List Contacts` page for that specific mailing list, where contacts can be created or imported, and then added to the specific mailing list." +msgstr "" + +#: ../../content/applications/marketing/email_marketing/mailing_lists.rst:75 +msgid "This same page can also be accessed by clicking the desired mailing list from the :guilabel:`Mailing Lists` page, and then clicking the :guilabel:`Recipients` smart button on the mailing list form." msgstr "" #: ../../content/applications/marketing/email_marketing/mailing_lists.rst:78 -msgid "When a mailing list is created in the database, Odoo provides the option to directly link the mailing list on the Odoo-built website (created via Odoo's :guilabel:`Website` application)." +msgid "Doing so *also* reveals a separate :guilabel:`Mailing List Contacts` page for that specific mailing list, where contacts can be created or imported, and then added to the specific mailing list." msgstr "" #: ../../content/applications/marketing/email_marketing/mailing_lists.rst:81 -msgid "To link a mailing list to a website, navigate to the front-end of the website, and enter :guilabel:`Edit` mode by clicking :guilabel:`Edit` in the upper-right corner. When clicked, Odoo reveals a right-sidebar, filled with drag-and-drop *Building Blocks* that are packed with various features, options, and design elements." -msgstr "" - -#: ../../content/applications/marketing/email_marketing/mailing_lists.rst:86 -msgid "Then, to add a *subscription field* for a specific mailing list onto a website, drag-and-drop any of the :guilabel:`Newsletter` options (:guilabel:`Newsletter Block`, :guilabel:`Newsletter Popup`, or :guilabel:`Newsletter`)." -msgstr "" - -#: ../../content/applications/marketing/email_marketing/mailing_lists.rst:91 -msgid "To quickly locate the :guilabel:`Newsletter` building block options (while in :guilabel:`Edit` mode on the front-end of the website), type `Newsletter` into the search bar, located in the right sidebar, under the :guilabel:`Blocks` tab, and Odoo reveals the three different :guilabel:`Newsletter` block options." -msgstr "" - -#: ../../content/applications/marketing/email_marketing/mailing_lists.rst:0 -msgid "View of how to quickly search for Newsletter blocks in the Odoo Website application." -msgstr "" - -#: ../../content/applications/marketing/email_marketing/mailing_lists.rst:100 -msgid "When a :guilabel:`Newsletter` block is dragged onto the body of the website, Odoo reveals a pop-up window, in which the desired mailing list is selected from a drop-down menu (and linked) to this block on the website." +msgid "Contacts can also be directly imported to a specific mailing list from the :guilabel:`Mailing Lists` page, by clicking :guilabel:`Import Contacts` to the far-right of the desired mailing list." msgstr "" #: ../../content/applications/marketing/email_marketing/mailing_lists.rst:-1 -msgid "View of the add mailing list subscription pop-up on an Odoo Website." +msgid "The import contacts button of a mailing list line in Odoo Email Marketing." msgstr "" -#: ../../content/applications/marketing/email_marketing/mailing_lists.rst:108 -msgid ":guilabel:`Newsletter Block` - Adds a block onto the webpage, providing visitors with the option to add their email address to this mailing list, and subscribe to future communications." +#: ../../content/applications/marketing/email_marketing/mailing_lists.rst:88 +msgid "Doing so reveals an :guilabel:`Import Mailing Contacts` pop-up form." +msgstr "" + +#: ../../content/applications/marketing/email_marketing/mailing_lists.rst:-1 +msgid "The import mailing contacts pop-up form that appears in Odoo Email Marketing." +msgstr "" + +#: ../../content/applications/marketing/email_marketing/mailing_lists.rst:94 +msgid "Here, the desired mailing list is auto-populated in the :guilabel:`Import contacts in` field. Beneath that, write or paste email addresses in the :guilabel:`Contact List` field." +msgstr "" + +#: ../../content/applications/marketing/email_marketing/mailing_lists.rst:97 +msgid "The option to import a country, company name, and more is available, via the :guilabel:`Upload a file` link at the bottom of the pop-up form." +msgstr "" + +#: ../../content/applications/marketing/email_marketing/mailing_lists.rst:100 +msgid "When all contacts and configurations are complete, click :guilabel:`Import`." +msgstr "" + +#: ../../content/applications/marketing/email_marketing/mailing_lists.rst:102 +msgid "To add contacts to a specific mailing list from a master list of all mailing list contacts in the database, navigate to :menuselection:`Email Marketing app --> Mailing Lists --> Mailing List Contacts`. Doing so reveals the :guilabel:`Mailing List Contacts` page, featuring a list of all contacts associated with every mailing list." +msgstr "" + +#: ../../content/applications/marketing/email_marketing/mailing_lists.rst:-1 +msgid "The Mailing List page in the Odoo Email Marketing application." msgstr "" #: ../../content/applications/marketing/email_marketing/mailing_lists.rst:111 -msgid "Here's an example of a :guilabel:`Newsletter Block`." +msgid "The default :guilabel:`Exclude Blacklisted Emails` filter appears in the search bar." msgstr "" -#: ../../content/applications/marketing/email_marketing/mailing_lists.rst:0 -msgid "View of a sample newsletter block in the Odoo Website application." +#: ../../content/applications/marketing/email_marketing/mailing_lists.rst:113 +msgid "From the :guilabel:`Mailing List Contacts` page, contacts can be created and/or imported, and then added to a mailing list." msgstr "" #: ../../content/applications/marketing/email_marketing/mailing_lists.rst:116 -msgid ":guilabel:`Newsletter Popup` - Tells Odoo to reveal a subscription pop-up window to occur at a certain part of the webpage. When the visitor scrolls to this predetermined point, a pop-up subscription window appears, asking for their email address to subscribe to the mailing list. The pop-up window can be edited further to fit any business needs." +msgid "To add an existing contact to a mailing list, select the desired contact from the list on the :guilabel:`Mailing List Contacts` page to reveal their contact form." msgstr "" -#: ../../content/applications/marketing/email_marketing/mailing_lists.rst:121 -msgid "Here's an example of a :guilabel:`Newsletter Popup`." +#: ../../content/applications/marketing/email_marketing/mailing_lists.rst:119 +msgid "At the bottom of their contact form, click :guilabel:`Add a line` under the :guilabel:`Mailing List` column, locate the desired mailing list from the drop-down menu, and select it." msgstr "" -#: ../../content/applications/marketing/email_marketing/mailing_lists.rst:0 -msgid "View of a sample newsletter pop-up sample on an Odoo Website." +#: ../../content/applications/marketing/email_marketing/mailing_lists.rst:-1 +msgid "The Add a line for mailing lists on a standard contact form in Odoo Email Marketing." msgstr "" -#: ../../content/applications/marketing/email_marketing/mailing_lists.rst:126 -msgid ":guilabel:`Newsletter` - Provides visitors with a simple field to add their email address to the mailing list, and subscribe to future mailings in the footer (or anywhere else on the page)." +#: ../../content/applications/marketing/email_marketing/mailing_lists.rst:127 +msgid "A mailing list can be created directly from a contact form, by typing the name of the new mailing list in the :guilabel:`Mailing List` field. Then, after a new mailing list name has been entered, two options appear on the drop-down menu beneath the new mailing list name." msgstr "" -#: ../../content/applications/marketing/email_marketing/mailing_lists.rst:129 -msgid "Here's an example of a :guilabel:`Newsletter` dynamic block." +#: ../../content/applications/marketing/email_marketing/mailing_lists.rst:131 +msgid "From this drop-down menu, select :guilabel:`Create` to create the mailing list and edit it later, or select :guilabel:`Create and edit...` to create and edit the new mailing list right away." msgstr "" -#: ../../content/applications/marketing/email_marketing/mailing_lists.rst:0 -msgid "View of a Newsletter dynamic block on an Odoo Website." +#: ../../content/applications/marketing/email_marketing/mailing_lists.rst:134 +msgid "To remove a contact from a mailing list that the contact has been added to, enable the :guilabel:`Opt Out` checkbox. If the :guilabel:`Opt Out` checkbox is ticked, the ability to add a :guilabel:`Reason` why the contact opted-out is also available." msgstr "" -#: ../../content/applications/marketing/email_marketing/mailing_lists.rst:135 -#: ../../content/applications/marketing/email_marketing/unsubscriptions.rst:73 -msgid ":doc:`/applications/marketing/email_marketing`" +#: ../../content/applications/marketing/email_marketing/mailing_lists.rst:138 +msgid "When/if a contact *has* opted-out of a mailing list, the date they activated their opt-out appears in the :guilabel:`Unsubscription Date` column on their contact form." +msgstr "" + +#: ../../content/applications/marketing/email_marketing/mailing_lists.rst:141 +msgid "Lastly, the initial :guilabel:`Subscription Date` can be seen, as well. This field is auto-populated with the date and time their subscription to the mailing list has been saved." +msgstr "" + +#: ../../content/applications/marketing/email_marketing/mailing_lists.rst:144 +msgid "Multiple mailing lists can be added to a single contact form." +msgstr "" + +#: ../../content/applications/marketing/email_marketing/mailing_lists.rst:146 +msgid "To delete any mailing list from a contact form, simply click the :guilabel:`🗑️ (trash can)` icon." +msgstr "" + +#: ../../content/applications/marketing/email_marketing/mailing_lists.rst:149 +msgid "Link mailing list to website" +msgstr "" + +#: ../../content/applications/marketing/email_marketing/mailing_lists.rst:151 +msgid "When a mailing list is created in the database, Odoo provides the option to directly link the mailing list to the Odoo-built website (created via the Odoo *Website* application)." +msgstr "" + +#: ../../content/applications/marketing/email_marketing/mailing_lists.rst:154 +msgid "To link a mailing list to a website, navigate to the front-end of the website, which can be accomplished in a variety of ways throughout the database. The most direct way to get to the front-end of the website is to simply open the :menuselection:`Website` application from the main Odoo dashboard." +msgstr "" + +#: ../../content/applications/marketing/email_marketing/mailing_lists.rst:159 +msgid "Doing so reveals the designated homepage of the Odoo-built website for the database." +msgstr "" + +#: ../../content/applications/marketing/email_marketing/mailing_lists.rst:161 +msgid "From the front-end of the website, click the :guilabel:`Edit` button in the upper-right corner. When clicked, Odoo reveals a right-sidebar, filled with drag-and-drop *building blocks*, packed with various features, options, and design elements." +msgstr "" + +#: ../../content/applications/marketing/email_marketing/mailing_lists.rst:165 +msgid "Next, in the search bar of the right-sidebar, search for `Newsletter`. The :guilabel:`Newsletter` selection of building blocks is used to add subscription fields for any mailing list onto the website." +msgstr "" + +#: ../../content/applications/marketing/email_marketing/mailing_lists.rst:-1 +msgid "View of how to quickly search for Newsletter blocks in the Odoo Website application." +msgstr "" + +#: ../../content/applications/marketing/email_marketing/mailing_lists.rst:173 +msgid "Doing so reveals the following building block options: :guilabel:`Newsletter Block`, :guilabel:`Newsletter Popup`, and :guilabel:`Newsletter`. Any of these options can be used to add subscription fields for a mailing list onto the website." +msgstr "" + +#: ../../content/applications/marketing/email_marketing/mailing_lists.rst:177 +msgid "The :guilabel:`Newsletter Block` option places a customizable block onto the body of the website where a visitor to enter their email and click a button to subscribe to a designated mailing list." +msgstr "" + +#: ../../content/applications/marketing/email_marketing/mailing_lists.rst:-1 +#: ../../content/applications/marketing/email_marketing/mailing_lists.rst:-1 +msgid "Sample of how a newsletter block appears on an Odoo Website." +msgstr "" + +#: ../../content/applications/marketing/email_marketing/mailing_lists.rst:184 +msgid "The :guilabel:`Newsletter Popup` option reveals a customizable pop-up window that appears when a visitor scrolls to the specific section of the webpage on which the building block is placed. When the visitor reaches the designated section, a pop-up window appears, in which a visitor can enter their email address, click a button, and subscribe to that predetermined mailing list." +msgstr "" + +#: ../../content/applications/marketing/email_marketing/mailing_lists.rst:-1 +msgid "Sample of how a newsletter popup block appears on an Odoo Website." +msgstr "" + +#: ../../content/applications/marketing/email_marketing/mailing_lists.rst:193 +msgid "The :guilabel:`Newsletter` option provides the same functionality as the other options. However, it only consists of a field for the visitor to enter their email address, and a button to subscribe to the mailing list." +msgstr "" + +#: ../../content/applications/marketing/email_marketing/mailing_lists.rst:197 +msgid "It is covertly designed in this fashion to be cleanly implemented into the content of the webpage and/or footer." +msgstr "" + +#: ../../content/applications/marketing/email_marketing/mailing_lists.rst:204 +msgid "Once the desired newsletter building block is chosen, drag-and-drop it onto the body of the website. Then, select the newly-placed newsletter building block to reveal its configuration options on the right-sidebar." +msgstr "" + +#: ../../content/applications/marketing/email_marketing/mailing_lists.rst:208 +msgid "From there, open the :guilabel:`Newsletter` drop-down menu, and select the specific mailing list that should be applied to the block." +msgstr "" + +#: ../../content/applications/marketing/email_marketing/mailing_lists.rst:-1 +msgid "The newsletter drop-down menu in the customize sidebar that appears in Odoo Website." +msgstr "" + +#: ../../content/applications/marketing/email_marketing/mailing_lists.rst:215 +msgid "Once the desired configurations and customizations are complete, be sure to click the :guilabel:`Save` button in the upper-right corner." +msgstr "" + +#: ../../content/applications/marketing/email_marketing/mailing_lists.rst:218 +msgid "Now, when a visitor enters their email address, and clicks the button to subscribe, they are instantly subscribed to that pre-configured mailing list. They are also added as a contact for that mailing list in Odoo *Email Marketing*." +msgstr "" + +#: ../../content/applications/marketing/email_marketing/mailing_lists.rst:223 +#: ../../content/applications/marketing/email_marketing/unsubscriptions.rst:129 +msgid ":doc:`../email_marketing`" +msgstr "" + +#: ../../content/applications/marketing/email_marketing/mailing_lists.rst:224 +msgid ":doc:`unsubscriptions`" msgstr "" #: ../../content/applications/marketing/email_marketing/unsubscriptions.rst:3 -msgid "Manage unsubscriptions (Blacklist)" +msgid "Manage unsubscriptions (blacklist)" msgstr "" #: ../../content/applications/marketing/email_marketing/unsubscriptions.rst:5 -msgid "Providing recipients with the power to unsubscribe from mailing lists is not only a smart business practice, it's often a legal requirement. By allowing recipients to unsubscribe from a mailing list establishes a sense of trust with an audience, and helps companies appear genuine (and not spammy)." +msgid "Providing recipients with the power to unsubscribe from mailing lists is not only a smart business practice, it's often a legal requirement. Allowing recipients to unsubscribe from a mailing list establishes a sense of trust and control with an audience. It also helps companies appear more genuine, and less *spammy*." msgstr "" -#: ../../content/applications/marketing/email_marketing/unsubscriptions.rst:10 -msgid "Enable the Blacklist feature" +#: ../../content/applications/marketing/email_marketing/unsubscriptions.rst:11 +msgid "Unsubscribe and blacklist" msgstr "" -#: ../../content/applications/marketing/email_marketing/unsubscriptions.rst:12 -msgid "First, the *Blacklist* feature must be enabled. To do that, navigate to :menuselection:`Email Marketing app --> Configuration --> Settings`, enable to :guilabel:`Blacklist Options when Unsubscribing`, and click :guilabel:`Save`." +#: ../../content/applications/marketing/email_marketing/unsubscriptions.rst:13 +msgid "In addition to having the option to unsubscribe from specific mailing lists, the recipient can also *blacklist* themselves during the unsubscription process, meaning they will not receive *any* more marketing emails from the Odoo database." +msgstr "" + +#: ../../content/applications/marketing/email_marketing/unsubscriptions.rst:17 +msgid "In order to provide recipients with the ability to blacklist themselves, a specific feature **must** be enabled in the *Email Marketing* application." +msgstr "" + +#: ../../content/applications/marketing/email_marketing/unsubscriptions.rst:20 +msgid "Navigate to :menuselection:`Email Marketing app --> Configuration --> Settings`, and tick the checkbox next to the :guilabel:`Blacklist Option when Unsubscribing` feature. Then, click :guilabel:`Save` in the upper-left corner of the :guilabel:`Settings` page." msgstr "" #: ../../content/applications/marketing/email_marketing/unsubscriptions.rst:-1 msgid "View of the blacklist feature in the Settings page of the Odoo Email Marketing app." msgstr "" -#: ../../content/applications/marketing/email_marketing/unsubscriptions.rst:20 -msgid "With that feature activated, an *Unsubscribe* link appears in mailings. If a recipient clicks that link, Odoo reveals a :guilabel:`Unsubscriptions` page, where they can directly manage their subscriptions." +#: ../../content/applications/marketing/email_marketing/unsubscriptions.rst:29 +msgid "Unsubscribe" msgstr "" -#: ../../content/applications/marketing/email_marketing/unsubscriptions.rst:25 -msgid "With a test mailing, clicking the :guilabel:`Unsubscribe` link reveals an error page (*error 403 - Access Denied*). To make sure the link is working properly, create the mailing, and only send it to a personal email." +#: ../../content/applications/marketing/email_marketing/unsubscriptions.rst:31 +msgid "By default, an *Unsubscribe* link appears at the bottom of all mailing templates." msgstr "" -#: ../../content/applications/marketing/email_marketing/unsubscriptions.rst:30 +#: ../../content/applications/marketing/email_marketing/unsubscriptions.rst:34 +msgid "The *Unsubscribe* link does **not** appear by default if the *Start From Scratch* template is used to create a mailing. The user **must** manually add the specific unsubscribe link `/unsubscribe_from_list` in the body of the email, or use a block from the *Footers* section of the email builder, which includes the unsubscribe link." +msgstr "" + +#: ../../content/applications/marketing/email_marketing/unsubscriptions.rst:39 +msgid "If a recipient clicks the *Unsubscribe* link in a mailing, Odoo instantly unsubscribes them from the mailing list, presents them with a :guilabel:`Mailing Subscriptions` page where they can directly manage their subscriptions, and informs them that they've been :guilabel:`Successfully Unsubscribed`." +msgstr "" + +#: ../../content/applications/marketing/email_marketing/unsubscriptions.rst:-1 +msgid "The Mailng Subscriptions page that appears when 'Unsubscribe' link in mailing is clicked." +msgstr "" + +#: ../../content/applications/marketing/email_marketing/unsubscriptions.rst:48 +msgid "Beneath that, Odoo asks the former subscriber to :guilabel:`Please let us know why you updated your subscription`, and the user can proceed to choose the appropriate opt-out reason from a series of options presented to them." +msgstr "" + +#: ../../content/applications/marketing/email_marketing/unsubscriptions.rst:53 +msgid "The opt-out answer options can be created and modified by navigating to :menuselection:`Email Marketing app --> Configuration --> Optout Reasons`." +msgstr "" + +#: ../../content/applications/marketing/email_marketing/unsubscriptions.rst:56 +msgid "Once they've chosen the appropriate opt-out reason from the options presented to them, they can click the :guilabel:`Send` button. Odoo then logs their reasoning for unsubscribing in the *Email Marketing* app for future analysis." +msgstr "" + +#: ../../content/applications/marketing/email_marketing/unsubscriptions.rst:61 #: ../../content/applications/marketing/sms_marketing/essentials/mailing_lists_blacklists.rst:102 msgid "Blacklist" msgstr "" -#: ../../content/applications/marketing/email_marketing/unsubscriptions.rst:32 -msgid "In addition to having the option to *Unsubscribe* from specific mailing lists, the recipient can also *Blacklist* themselves, meaning they will not receive *any* more emails." +#: ../../content/applications/marketing/email_marketing/unsubscriptions.rst:63 +msgid "For a recipient to remove (i.e. blacklist) themselves from **all** marketing emails during the unsubscription process, on the :guilabel:`Mailing Subscriptions` page, they must click :guilabel:`Exclude Me`." msgstr "" -#: ../../content/applications/marketing/email_marketing/unsubscriptions.rst:36 -msgid "The mailing list has to be configured as *Public* in order to be visible for users." +#: ../../content/applications/marketing/email_marketing/unsubscriptions.rst:67 +msgid "Upon clicking :guilabel:`Exclude Me`, Odoo informs the recipient they have been successfully blacklisted, with a message reading: :guilabel:`✔️ Email added to our blocklist`." msgstr "" -#: ../../content/applications/marketing/email_marketing/unsubscriptions.rst:38 -msgid "To view a complete collection of blacklisted email addresses, navigate to :menuselection:`Email Marketing app --> Configuration --> Blacklisted Email Addresses`." +#: ../../content/applications/marketing/email_marketing/unsubscriptions.rst:-1 +msgid "The blocklist question on the Mailing Subscriptions page that recipients see." +msgstr "" + +#: ../../content/applications/marketing/email_marketing/unsubscriptions.rst:74 +msgid "Beneath that, Odoo asks the former subscriber to :guilabel:`Please let us know why you want to be added to our blocklist`, and the user can proceed to choose the appropriate reason from a series of options presented to them." +msgstr "" + +#: ../../content/applications/marketing/email_marketing/unsubscriptions.rst:78 +msgid "Once they've chosen the appropriate reason from the options presented to them, they can click the :guilabel:`Send` button. Odoo then logs their reasoning for blacklisting themselves in the *Email Marketing* app for future analysis." +msgstr "" + +#: ../../content/applications/marketing/email_marketing/unsubscriptions.rst:83 +msgid "Blacklisted email addresses" +msgstr "" + +#: ../../content/applications/marketing/email_marketing/unsubscriptions.rst:85 +msgid "To view a complete list of all blacklisted email addresses, navigate to :menuselection:`Email Marketing app --> Configuration --> Blacklisted Email Addresses`." msgstr "" #: ../../content/applications/marketing/email_marketing/unsubscriptions.rst:-1 msgid "View of the blacklisted email addresses page in Odoo Email Marketing." msgstr "" -#: ../../content/applications/marketing/email_marketing/unsubscriptions.rst:45 -msgid "When a blacklisted record is selected from this page, Odoo reveals a separate page with that blacklisted recipient's contact information." +#: ../../content/applications/marketing/email_marketing/unsubscriptions.rst:92 +msgid "When a blacklisted record is selected from this list, Odoo reveals a separate page with the recipient's contact information, along with the provided :guilabel:`Reason` why they chose to blacklist themselves." msgstr "" #: ../../content/applications/marketing/email_marketing/unsubscriptions.rst:-1 msgid "View of a blacklisted contact detail form in Odoo Email Marketing." msgstr "" -#: ../../content/applications/marketing/email_marketing/unsubscriptions.rst:52 -msgid "In the :guilabel:`Chatter` of this page, there's a time-stamped message, informing the user when that recipient blacklisted themselves (via a :guilabel:`Mail Blacklist created` log note)." +#: ../../content/applications/marketing/email_marketing/unsubscriptions.rst:100 +msgid "In the *chatter* of the blacklisted record page, there's a time-stamped message, informing the user when the recipient blacklisted themselves (via a :guilabel:`Mail Blacklist created` log note)." msgstr "" -#: ../../content/applications/marketing/email_marketing/unsubscriptions.rst:56 +#: ../../content/applications/marketing/email_marketing/unsubscriptions.rst:104 +msgid "Blacklisted emails are excluded from all marketing mailings, however, these emails can still receive transactional emails, such as order confirmations, shipping notifications, etc." +msgstr "" + +#: ../../content/applications/marketing/email_marketing/unsubscriptions.rst:108 msgid "Unblacklist contacts" msgstr "" -#: ../../content/applications/marketing/email_marketing/unsubscriptions.rst:58 -msgid "To *Unblacklist* contacts, click the :guilabel:`Unblacklist` button in the upper-left corner to remove the contact from the blacklist, allowing them to receive mailings once again." +#: ../../content/applications/marketing/email_marketing/unsubscriptions.rst:110 +msgid "To *Unblacklist* contacts, click the :guilabel:`Unblacklist` button in the upper-left corner of a blacklisted record's page to remove the contact from the blacklist, allowing them to receive mailings once again." msgstr "" -#: ../../content/applications/marketing/email_marketing/unsubscriptions.rst:61 -msgid "When :guilabel:`Unblacklist` is clicked, a pop-up appears. In this pop-up, the specific email address is listed, and there's a :guilabel:`Reason` field, in which a reason can be entered, explaining why this particular contact was removed from the blacklist." +#: ../../content/applications/marketing/email_marketing/unsubscriptions.rst:114 +msgid "When :guilabel:`Unblacklist` is clicked, an :guilabel:`Are you sure you want to unblacklist this Email Address?` pop-up window appears." +msgstr "" + +#: ../../content/applications/marketing/email_marketing/unsubscriptions.rst:117 +msgid "In this pop-up window, the email address of the selected blacklisted record is shown, and there's a :guilabel:`Reason` field, in which a reason can be entered, explaining why this particular contact was removed from the blacklist." msgstr "" #: ../../content/applications/marketing/email_marketing/unsubscriptions.rst:-1 msgid "View of the unblacklist pop-up window in the Odoo Email Marketing application." msgstr "" -#: ../../content/applications/marketing/email_marketing/unsubscriptions.rst:69 +#: ../../content/applications/marketing/email_marketing/unsubscriptions.rst:125 msgid "After filling in the fields, click :guilabel:`Confirm` to officially remove that particular contact from the blacklist." msgstr "" +#: ../../content/applications/marketing/email_marketing/unsubscriptions.rst:130 +msgid ":doc:`mailing_lists`" +msgstr "" + #: ../../content/applications/marketing/events.rst:5 msgid "Events" msgstr "" @@ -1644,6 +1827,7 @@ msgstr "" msgid "When configuring the target filters on a marketing campaign, there are some options that have an :guilabel:`> (arrow)` icon beside them. The :guilabel:`> (arrow)` icon signifies that the particular filter has more refined parameters within it that can be customized." msgstr "" +#: ../../content/applications/marketing/marketing_automation/target_audience.rst:-1 #: ../../content/applications/marketing/marketing_automation/target_audience.rst:-1 msgid "The drop-down filter menu in the Marketing Automation application." msgstr "" @@ -2026,6 +2210,7 @@ msgstr "" msgid "Next to the :guilabel:`Graph` tab on the activity block, there's the option to open a :guilabel:`Filter` tab (represented by a :guilabel:`filter/funnel` icon)." msgstr "" +#: ../../content/applications/marketing/marketing_automation/understanding_metrics.rst:-1 #: ../../content/applications/marketing/marketing_automation/understanding_metrics.rst:-1 msgid "What a campaign activity filter tab looks like in Odoo Marketing Automation." msgstr "" @@ -2168,6 +2353,7 @@ msgstr "" msgid "To create a new template directly from the :guilabel:`Mail Template` field, start typing the title of the new template into the blank field beside :guilabel:`Mail Template`, and select :guilabel:`Create and edit...` to reveal a :guilabel:`Create Marketing Template` pop-up window." msgstr "" +#: ../../content/applications/marketing/marketing_automation/workflow_activities.rst:-1 #: ../../content/applications/marketing/marketing_automation/workflow_activities.rst:-1 msgid "The create and edit email drop-down option on create activities pop-up window." msgstr "" @@ -2573,6 +2759,7 @@ msgstr "" msgid "To see a complete collection of blacklisted numbers, navigate to the :menuselection:`SMS Marketing app --> Configuration --> Blacklisted Phone Numbers` to reveal a dashboard containing every blacklisted phone number in the database." msgstr "" +#: ../../content/applications/marketing/sms_marketing/essentials/mailing_lists_blacklists.rst:-1 #: ../../content/applications/marketing/sms_marketing/essentials/mailing_lists_blacklists.rst:-1 msgid "SMS Blacklist menu in the application." msgstr "" @@ -3179,6 +3366,7 @@ msgstr "" msgid "To access a complete overview of all social marketing campaigns, open the :menuselection:`Social Marketing` application, and click :menuselection:`Campaigns` from the header menu. Doing so reveals a separate page with every campaign in a default kanban view." msgstr "" +#: ../../content/applications/marketing/social_marketing/essentials/social_campaigns.rst:-1 #: ../../content/applications/marketing/social_marketing/essentials/social_campaigns.rst:-1 msgid "View of the campaigns page in the Odoo Social Marketing application." msgstr "" @@ -3895,6 +4083,7 @@ msgstr "" msgid "To see a list of all social accounts and websites linked to the database, go to :menuselection:`Social Marketing app --> Configuration --> Social Accounts`. This :guilabel:`Social Accounts` display the :guilabel:`Name`, the :guilabel:`Handle/Short Name`, the :guilabel:`Social Media` platform, who it was :guilabel:`Created by`, and the :guilabel:`Company` to which it is associated." msgstr "" +#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:-1 #: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:-1 msgid "View of the social accounts page in the Odoo Social Marketing application." msgstr "" diff --git a/locale/sources/productivity.pot b/locale/sources/productivity.pot index 43dd7ea93..97239bab1 100644 --- a/locale/sources/productivity.pot +++ b/locale/sources/productivity.pot @@ -8,7 +8,7 @@ msgid "" msgstr "" "Project-Id-Version: Odoo 17.0\n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2024-03-08 12:48+0000\n" +"POT-Creation-Date: 2024-03-25 16:01+0000\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME \n" "Language-Team: LANGUAGE \n" @@ -21,7 +21,6 @@ msgid "Productivity" msgstr "" #: ../../content/applications/productivity/calendar.rst:5 -#: ../../content/applications/productivity/studio/views.rst:201 msgid "Calendar" msgstr "" @@ -34,11 +33,11 @@ msgid "Synchronize Google Calendar with Odoo to see and manage meetings from bot msgstr "" #: ../../content/applications/productivity/calendar/google.rst:9 -msgid ":doc:`/applications/general/auth/google`" +msgid ":doc:`/applications/general/users/google`" msgstr "" #: ../../content/applications/productivity/calendar/google.rst:10 -msgid ":doc:`/administration/maintain/google_oauth`" +msgid ":doc:`/applications/general/email_communication/google_oauth`" msgstr "" #: ../../content/applications/productivity/calendar/google.rst:13 @@ -230,11 +229,11 @@ msgid "Synchronizing a user's Outlook Calendar with Odoo is useful for keeping t msgstr "" #: ../../content/applications/productivity/calendar/outlook.rst:9 -msgid ":doc:`/applications/general/auth/azure`" +msgid ":doc:`/applications/general/users/azure`" msgstr "" #: ../../content/applications/productivity/calendar/outlook.rst:10 -msgid ":doc:`/administration/maintain/azure_oauth`" +msgid ":doc:`/applications/general/email_communication/azure_oauth`" msgstr "" #: ../../content/applications/productivity/calendar/outlook.rst:13 @@ -286,7 +285,7 @@ msgid "Configuration in Odoo" msgstr "" #: ../../content/applications/productivity/calendar/outlook.rst:59 -msgid "In the Odoo database, go to :menuselection:`Settings --> General Settings --> Integrations` and activate the :guilabel:`Outlook Calendar` setting." +msgid "In the Odoo database, go to :menuselection:`Settings app --> Calendar` in the left menu and activate the :guilabel:`Outlook Calendar` setting." msgstr "" #: ../../content/applications/productivity/calendar/outlook.rst:-1 @@ -382,2846 +381,765 @@ msgid "All users that want to use the synchronization simply need to :ref:`sync msgstr "" #: ../../content/applications/productivity/calendar/outlook.rst:137 -msgid ":doc:`../mail_plugins/outlook`" +msgid ":doc:`/applications/general/integrations/mail_plugins/outlook`" msgstr "" #: ../../content/applications/productivity/calendar/outlook.rst:138 msgid ":doc:`google`" msgstr "" -#: ../../content/applications/productivity/discuss.rst:8 +#: ../../content/applications/productivity/discuss.rst:6 msgid "Discuss" msgstr "" -#: ../../content/applications/productivity/discuss/advanced.rst:5 -msgid "Advanced" -msgstr "" - -#: ../../content/applications/productivity/discuss/advanced/ice_servers.rst:3 -msgid "Configure ICE servers with Twilio" -msgstr "" - -#: ../../content/applications/productivity/discuss/advanced/ice_servers.rst:5 -msgid "Odoo Discuss uses WebRTC API and peer-to-peer connections for voice and video calls. If one of the call attendees is behind a symmetric NAT, you need to configure an ICE server to establish a connection to the call attendee. To set up an ICE server, first, create a Twilio account for video calls, and then, connect that Twilio account to Odoo." -msgstr "" - -#: ../../content/applications/productivity/discuss/advanced/ice_servers.rst:11 -msgid "Create a Twilio account" -msgstr "" - -#: ../../content/applications/productivity/discuss/advanced/ice_servers.rst:13 -msgid "First, go to `Twilio `_ and click :guilabel:`Sign up` to create a new Twilio account. Next, enter your name and email address, create a password, and accept Twilio's terms of service. Then, click :guilabel:`Start your free trial`. Verify your email address with Twilio, as per their instructions." -msgstr "" - -#: ../../content/applications/productivity/discuss/advanced/ice_servers.rst:18 -msgid "Next, enter your phone number into Twilio. Then, Twilio will send you an SMS text message containing a verification code. Enter the verification code into Twilio to verify your phone number." -msgstr "" - -#: ../../content/applications/productivity/discuss/advanced/ice_servers.rst:22 -msgid "After that, Twilio redirects to a welcome page. Use the following list to answer Twilio's questions:" -msgstr "" - -#: ../../content/applications/productivity/discuss/advanced/ice_servers.rst:25 -msgid "For :guilabel:`Which Twilio product are you here to use?`, select :guilabel:`Video`." -msgstr "" - -#: ../../content/applications/productivity/discuss/advanced/ice_servers.rst:26 -msgid "For :guilabel:`What do you plan to build with Twilio?`, select :guilabel:`Other`." -msgstr "" - -#: ../../content/applications/productivity/discuss/advanced/ice_servers.rst:27 -msgid "For :guilabel:`How do you want to build with Twilio?`, select :guilabel:`With no code at all`." -msgstr "" - -#: ../../content/applications/productivity/discuss/advanced/ice_servers.rst:28 -msgid "For :guilabel:`What is your goal today?`, select :guilabel:`3rd party integrations`." -msgstr "" - -#: ../../content/applications/productivity/discuss/advanced/ice_servers.rst:-1 -msgid "The Twilio welcome page." -msgstr "" - -#: ../../content/applications/productivity/discuss/advanced/ice_servers.rst:34 -msgid "If necessary, change the billing country. Finally, click :guilabel:`Get Started with Twilio`." -msgstr "" - -#: ../../content/applications/productivity/discuss/advanced/ice_servers.rst:37 -msgid "Locate the Twilio Account SID and Auth Token" -msgstr "" - -#: ../../content/applications/productivity/discuss/advanced/ice_servers.rst:39 -msgid "To locate the Account SID and Auth Token, go to the Twilio account dashboard. Then, click :guilabel:`Develop` on the sidebar. In the :guilabel:`Account Info` section, locate the :guilabel:`Account SID` and the :guilabel:`Auth Token`. Both of these are needed to connect Twilio to Odoo." -msgstr "" - -#: ../../content/applications/productivity/discuss/advanced/ice_servers.rst:-1 -msgid "The Twilio Account SID and Auth Token can be found uner the Account Info section." -msgstr "" - -#: ../../content/applications/productivity/discuss/advanced/ice_servers.rst:49 -msgid "Connect Twilio to Odoo" -msgstr "" - -#: ../../content/applications/productivity/discuss/advanced/ice_servers.rst:51 -msgid "Open the Odoo database and go to :menuselection:`Settings --> General Settings --> Discuss`. Check the box next to :guilabel:`Use Twilio ICE servers` and enter the Twilio account's :guilabel:`Account SID` and :guilabel:`Auth Token`. Finally, click :guilabel:`Save` to apply these changes." -msgstr "" - -#: ../../content/applications/productivity/discuss/advanced/ice_servers.rst:-1 -msgid "Enable the \"Use Twilio ICE servers\" option in Odoo General Settings." -msgstr "" - -#: ../../content/applications/productivity/discuss/advanced/ice_servers.rst:61 -msgid "Define a list of custom ICE servers" -msgstr "" - -#: ../../content/applications/productivity/discuss/advanced/ice_servers.rst:63 -msgid "This step is not required for the Twilio configuration. However, if Twilio is not configured or is not working at any given moment, Odoo will fall back on the custom ICE servers list. The user must define the list of custom ICE servers." -msgstr "" - -#: ../../content/applications/productivity/discuss/advanced/ice_servers.rst:67 -msgid "In :menuselection:`Settings --> General Settings --> Discuss`, click the :guilabel:`ICE Servers` button under :guilabel:`Custom ICE server list`." -msgstr "" - -#: ../../content/applications/productivity/discuss/advanced/ice_servers.rst:-1 -msgid "The \"ICE Servers\" button in Odoo General Settings." -msgstr "" - -#: ../../content/applications/productivity/discuss/advanced/ice_servers.rst:74 -msgid "Odoo will redirect to the :guilabel:`ICE servers` page. Here you can define your own list of ICE servers." -msgstr "" - -#: ../../content/applications/productivity/discuss/advanced/ice_servers.rst:-1 -msgid "The \"ICE servers\" page in Odoo." -msgstr "" - -#: ../../content/applications/productivity/discuss/advanced/ice_servers.rst:82 -msgid "For on-premise instances of Odoo, the package `python3-gevent` is necessary for the Discuss module to run calls/video calls on Ubuntu (Linux) servers." -msgstr "" - -#: ../../content/applications/productivity/discuss/overview.rst:5 -msgid "Overview" -msgstr "" - -#: ../../content/applications/productivity/discuss/overview/get_started.rst:3 -msgid "Get started with Discuss" -msgstr "" - -#: ../../content/applications/productivity/discuss/overview/get_started.rst:5 +#: ../../content/applications/productivity/discuss.rst:8 msgid "Odoo *Discuss* is an internal communication app that allows users to connect through messages, notes, and file sharing, either through a persistent chat window that works across applications, or through the dedicated *Discuss* dashboard." msgstr "" -#: ../../content/applications/productivity/discuss/overview/get_started.rst:12 +#: ../../content/applications/productivity/discuss.rst:15 msgid "Choose notifications preference" msgstr "" -#: ../../content/applications/productivity/discuss/overview/get_started.rst:14 +#: ../../content/applications/productivity/discuss.rst:17 msgid "Access user-specific preferences for the *Discuss* app by navigating to :menuselection:`Settings app --> Users --> User --> Preferences tab`." msgstr "" -#: ../../content/applications/productivity/discuss/overview/get_started.rst:-1 +#: ../../content/applications/productivity/discuss.rst:-1 msgid "View of the Preferences tab for Odoo Discuss." msgstr "" -#: ../../content/applications/productivity/discuss/overview/get_started.rst:21 +#: ../../content/applications/productivity/discuss.rst:23 msgid "By default, the :guilabel:`Notification` field is set as :guilabel:`Handle by Emails`. With this setting enabled, a notification email will be sent by Odoo every time a message is sent from the chatter, a note is sent with an `@` mention (from chatter), or a notification is sent for a record that the user follows. Something that triggers a notification is changing of the stage (if an email\\ is configured to be sent, for example if the task is set to :guilabel:`Done`)." msgstr "" -#: ../../content/applications/productivity/discuss/overview/get_started.rst:27 +#: ../../content/applications/productivity/discuss.rst:29 msgid "By choosing :guilabel:`Handle in Odoo`, the above notifications are shown in the *Discuss* app's *inbox*. Messages can have the following actions taken on them: respond with an emoji by clicking :guilabel:`Add a Reaction`, or reply to the message by clicking on :guilabel:`Reply`. Additional actions may include starring the message by clicking :guilabel:`Marked as Todo`, or pinning the message by selecting :guilabel:`Pin` or even mark the message as unread by selecting :guilabel:`Marked as unread`." msgstr "" -#: ../../content/applications/productivity/discuss/overview/get_started.rst:-1 +#: ../../content/applications/productivity/discuss.rst:-1 msgid "View of an inbox message and its action options in Odoo Discuss." msgstr "" -#: ../../content/applications/productivity/discuss/overview/get_started.rst:38 +#: ../../content/applications/productivity/discuss.rst:39 msgid "Clicking :guilabel:`Mark as Todo` on a message causes it to appear on the :guilabel:`Starred` page, while clicking :guilabel:`Mark as Read` moves the message to :guilabel:`History`." msgstr "" -#: ../../content/applications/productivity/discuss/overview/get_started.rst:-1 +#: ../../content/applications/productivity/discuss.rst:-1 msgid "View of messages marked as todo in Odoo Discuss." msgstr "" -#: ../../content/applications/productivity/discuss/overview/get_started.rst:46 +#: ../../content/applications/productivity/discuss.rst:46 msgid "Start chatting" msgstr "" -#: ../../content/applications/productivity/discuss/overview/get_started.rst:48 +#: ../../content/applications/productivity/discuss.rst:48 msgid "The first time a user logs in to their account, OdooBot sends a message asking for permission to send desktop notifications for chats. If accepted, the user will receive push notifications on their desktop for the messages they receive, regardless of where the user is in Odoo." msgstr "" -#: ../../content/applications/productivity/discuss/overview/get_started.rst:-1 +#: ../../content/applications/productivity/discuss.rst:-1 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:58 +#: ../../content/applications/productivity/discuss.rst:57 msgid "To stop receiving desktop notifications, reset the notifications settings of the browser." msgstr "" -#: ../../content/applications/productivity/discuss/overview/get_started.rst:60 +#: ../../content/applications/productivity/discuss.rst:59 msgid "To start a chat, go to the :menuselection:`Discuss` app and click on the :guilabel:`+ (plus)` icon next to :guilabel:`Direct Messages` or :guilabel:`Channels` in the left menu of the dashboard." msgstr "" -#: ../../content/applications/productivity/discuss/overview/get_started.rst:-1 +#: ../../content/applications/productivity/discuss.rst:-1 msgid "View of Discuss's panel emphasizing the titles channels and direct messages in Odoo\n" "Discuss." msgstr "" -#: ../../content/applications/productivity/discuss/overview/get_started.rst:69 -msgid "A company can also easily create :doc:`public and private channels `." +#: ../../content/applications/productivity/discuss.rst:67 +msgid "A company can also easily create :doc:`public and private channels `." msgstr "" -#: ../../content/applications/productivity/discuss/overview/get_started.rst:73 +#: ../../content/applications/productivity/discuss.rst:70 msgid "Mentions in the chat and on the chatter" msgstr "" -#: ../../content/applications/productivity/discuss/overview/get_started.rst:75 +#: ../../content/applications/productivity/discuss.rst:72 msgid "To mention a user within a chat or the chatter, type `@user-name`; to refer to a channel, type `#channel-name`. The user mentioned will be notified in their *inbox* or through an email, depending on their communication settings." msgstr "" -#: ../../content/applications/productivity/discuss/overview/get_started.rst:-1 +#: ../../content/applications/productivity/discuss.rst:-1 msgid "View of a couple of chat window messages for Odoo Discuss." msgstr "" -#: ../../content/applications/productivity/discuss/overview/get_started.rst:84 +#: ../../content/applications/productivity/discuss.rst:80 msgid "When a user is mentioned, the search list (list of names) suggests values first based on the task's followers, and secondly on employees. If the record being searched does not match with either a follower or employee, the scope of the search becomes all partners." msgstr "" -#: ../../content/applications/productivity/discuss/overview/get_started.rst:89 +#: ../../content/applications/productivity/discuss.rst:85 msgid "User status" msgstr "" -#: ../../content/applications/productivity/discuss/overview/get_started.rst:91 +#: ../../content/applications/productivity/discuss.rst:87 msgid "It is helpful to see what colleagues are up to and how quickly they can respond to messages by checking their *status*. The status is shown on the left side of a contact's name on the :guilabel:`Discuss` sidebar, on the *messaging menu* and when listed in the *chatter*." msgstr "" -#: ../../content/applications/productivity/discuss/overview/get_started.rst:95 +#: ../../content/applications/productivity/discuss.rst:91 msgid "Green = online" msgstr "" -#: ../../content/applications/productivity/discuss/overview/get_started.rst:96 +#: ../../content/applications/productivity/discuss.rst:92 msgid "Orange = away" msgstr "" -#: ../../content/applications/productivity/discuss/overview/get_started.rst:97 +#: ../../content/applications/productivity/discuss.rst:93 msgid "White = offline" msgstr "" -#: ../../content/applications/productivity/discuss/overview/get_started.rst:98 +#: ../../content/applications/productivity/discuss.rst:94 msgid "Airplane = out of the office" msgstr "" -#: ../../content/applications/productivity/discuss/overview/get_started.rst:-1 +#: ../../content/applications/productivity/discuss.rst:-1 msgid "View of the contacts' status for Odoo Discuss." msgstr "" -#: ../../content/applications/productivity/discuss/overview/get_started.rst:106 -msgid ":doc:`/applications/productivity/discuss/overview/team_communication`" +#: ../../content/applications/productivity/discuss.rst:101 +msgid ":doc:`discuss/team_communication`" msgstr "" -#: ../../content/applications/productivity/discuss/overview/get_started.rst:107 -msgid ":doc:`/applications/productivity/discuss/overview/plan_activities`" +#: ../../content/applications/productivity/discuss.rst:102 +#: ../../content/applications/productivity/discuss/team_communication.rst:114 +msgid ":doc:`/applications/essentials/activities`" msgstr "" -#: ../../content/applications/productivity/discuss/overview/plan_activities.rst:3 -msgid "Activities" +#: ../../content/applications/productivity/discuss/ice_servers.rst:3 +msgid "Configure ICE servers with Twilio" msgstr "" -#: ../../content/applications/productivity/discuss/overview/plan_activities.rst:5 -msgid "*Activities* are follow-up tasks tied to a record in an Odoo database. Activities can be scheduled on any page of the database that contains a chatter thread, kanban view, list view, or activities view of an application." +#: ../../content/applications/productivity/discuss/ice_servers.rst:5 +msgid "Odoo Discuss uses WebRTC API and peer-to-peer connections for voice and video calls. If one of the call attendees is behind a symmetric NAT, you need to configure an ICE server to establish a connection to the call attendee. To set up an ICE server, first, create a Twilio account for video calls, and then, connect that Twilio account to Odoo." msgstr "" -#: ../../content/applications/productivity/discuss/overview/plan_activities.rst:10 -msgid "Schedule activities" +#: ../../content/applications/productivity/discuss/ice_servers.rst:11 +msgid "Create a Twilio account" msgstr "" -#: ../../content/applications/productivity/discuss/overview/plan_activities.rst:12 -msgid "One way that activities are created is by clicking the :guilabel:`Schedule Activity` button, located at the top of the *chatter* on any record. On the pop-up window that appears, select an :guilabel:`Activity Type` from the drop-down menu." +#: ../../content/applications/productivity/discuss/ice_servers.rst:13 +msgid "First, go to `Twilio `_ and click :guilabel:`Sign up` to create a new Twilio account. Next, enter your name and email address, create a password, and accept Twilio's terms of service. Then, click :guilabel:`Start your free trial`. Verify your email address with Twilio, as per their instructions." msgstr "" -#: ../../content/applications/productivity/discuss/overview/plan_activities.rst:17 -msgid "Individual applications have a list of *Activity Types* dedicated to that application. For example, to view and edit the activities available for the *CRM* application, go to :menuselection:`CRM app --> Configuration --> Activity Types`." +#: ../../content/applications/productivity/discuss/ice_servers.rst:18 +msgid "Next, enter your phone number into Twilio. Then, Twilio will send you an SMS text message containing a verification code. Enter the verification code into Twilio to verify your phone number." msgstr "" -#: ../../content/applications/productivity/discuss/overview/plan_activities.rst:21 -msgid "Enter a title for the activity in the :guilabel:`Summary` field, located in the :guilabel:`Schedule Activity` pop-up window." +#: ../../content/applications/productivity/discuss/ice_servers.rst:22 +msgid "After that, Twilio redirects to a welcome page. Use the following list to answer Twilio's questions:" msgstr "" -#: ../../content/applications/productivity/discuss/overview/plan_activities.rst:24 -msgid "To assign the activity to a different user, select a name from the :guilabel:`Assigned to` drop-down menu. Otherwise, the user creating the activity is automatically assigned." +#: ../../content/applications/productivity/discuss/ice_servers.rst:25 +msgid "For :guilabel:`Which Twilio product are you here to use?`, select :guilabel:`Video`." msgstr "" -#: ../../content/applications/productivity/discuss/overview/plan_activities.rst:27 -msgid "Lastly, feel free to add any additional information in the optional :guilabel:`Log a note...` field." +#: ../../content/applications/productivity/discuss/ice_servers.rst:26 +msgid "For :guilabel:`What do you plan to build with Twilio?`, select :guilabel:`Other`." msgstr "" -#: ../../content/applications/productivity/discuss/overview/plan_activities.rst:30 -msgid "The :guilabel:`Due Date` field on the :guilabel:`Schedule Activity` pop-up window auto-populates based on the configuration settings for the selected :guilabel:`Activity Type`. However, this date can be changed by selecting a day on the calendar in the :guilabel:`Due Date` field." +#: ../../content/applications/productivity/discuss/ice_servers.rst:27 +msgid "For :guilabel:`How do you want to build with Twilio?`, select :guilabel:`With no code at all`." msgstr "" -#: ../../content/applications/productivity/discuss/overview/plan_activities.rst:34 -msgid "Lastly, click one of the following buttons:" +#: ../../content/applications/productivity/discuss/ice_servers.rst:28 +msgid "For :guilabel:`What is your goal today?`, select :guilabel:`3rd party integrations`." msgstr "" -#: ../../content/applications/productivity/discuss/overview/plan_activities.rst:36 -msgid ":guilabel:`Schedule`: adds the activity to the chatter under :guilabel:`Planned activities`." +#: ../../content/applications/productivity/discuss/ice_servers.rst:-1 +msgid "The Twilio welcome page." msgstr "" -#: ../../content/applications/productivity/discuss/overview/plan_activities.rst:37 -msgid ":guilabel:`Mark as Done`: adds the details of the activity to the chatter under :guilabel:`Today`. The activity is not scheduled, it is automatically marked as completed." +#: ../../content/applications/productivity/discuss/ice_servers.rst:34 +msgid "If necessary, change the billing country. Finally, click :guilabel:`Get Started with Twilio`." msgstr "" -#: ../../content/applications/productivity/discuss/overview/plan_activities.rst:39 -msgid ":guilabel:`Done \\& Schedule Next`: adds the task under :guilabel:`Today` marked as done, and opens a new activity window." +#: ../../content/applications/productivity/discuss/ice_servers.rst:37 +msgid "Locate the Twilio Account SID and Auth Token" msgstr "" -#: ../../content/applications/productivity/discuss/overview/plan_activities.rst:41 -msgid ":guilabel:`Discard`: discards any changes made on the pop-up window." +#: ../../content/applications/productivity/discuss/ice_servers.rst:39 +msgid "To locate the Account SID and Auth Token, go to the Twilio account dashboard. Then, click :guilabel:`Develop` on the sidebar. In the :guilabel:`Account Info` section, locate the :guilabel:`Account SID` and the :guilabel:`Auth Token`. Both of these are needed to connect Twilio to Odoo." msgstr "" -#: ../../content/applications/productivity/discuss/overview/plan_activities.rst:-1 -msgid "View of CRM leads and the option to schedule an activity." +#: ../../content/applications/productivity/discuss/ice_servers.rst:-1 +msgid "The Twilio Account SID and Auth Token can be found uner the Account Info section." msgstr "" -#: ../../content/applications/productivity/discuss/overview/plan_activities.rst:48 -msgid "Depending on the activity type, the :guilabel:`Schedule` button may be replaced by a :guilabel:`Save` button, or an :guilabel:`Open Calendar` button." +#: ../../content/applications/productivity/discuss/ice_servers.rst:49 +msgid "Connect Twilio to Odoo" msgstr "" -#: ../../content/applications/productivity/discuss/overview/plan_activities.rst:51 -msgid "Scheduled activities are added to the chatter for the record under :guilabel:`Planned activities`." +#: ../../content/applications/productivity/discuss/ice_servers.rst:51 +msgid "Open the Odoo database and go to :menuselection:`Settings --> General Settings --> Discuss`. Check the box next to :guilabel:`Use Twilio ICE servers` and enter the Twilio account's :guilabel:`Account SID` and :guilabel:`Auth Token`. Finally, click :guilabel:`Save` to apply these changes." msgstr "" -#: ../../content/applications/productivity/discuss/overview/plan_activities.rst:57 -msgid "Activities can also be scheduled from the kanban, list, or activities view of an application." +#: ../../content/applications/productivity/discuss/ice_servers.rst:-1 +msgid "Enable the \"Use Twilio ICE servers\" option in Odoo General Settings." msgstr "" -#: ../../content/applications/productivity/discuss/overview/plan_activities.rst:61 -msgid "Kanban view" +#: ../../content/applications/productivity/discuss/ice_servers.rst:61 +msgid "Define a list of custom ICE servers" msgstr "" -#: ../../content/applications/productivity/discuss/overview/plan_activities.rst:63 -msgid "Select a record on which to schedule an activity. Click on the :guilabel:`🕘 (clock)` icon, then :guilabel:`Schedule An Activity`, and proceed to fill out the pop-up form." +#: ../../content/applications/productivity/discuss/ice_servers.rst:63 +msgid "This step is not required for the Twilio configuration. However, if Twilio is not configured or is not working at any given moment, Odoo will fall back on the custom ICE servers list. The user must define the list of custom ICE servers." msgstr "" -#: ../../content/applications/productivity/discuss/overview/plan_activities.rst:0 -msgid "Kanban view of the CRM pipeline and the option to schedule an activity." +#: ../../content/applications/productivity/discuss/ice_servers.rst:67 +msgid "In :menuselection:`Settings --> General Settings --> Discuss`, click the :guilabel:`ICE Servers` button under :guilabel:`Custom ICE server list`." msgstr "" -#: ../../content/applications/productivity/discuss/overview/plan_activities.rst:70 -msgid "List view" +#: ../../content/applications/productivity/discuss/ice_servers.rst:-1 +msgid "The \"ICE Servers\" button in Odoo General Settings." msgstr "" -#: ../../content/applications/productivity/discuss/overview/plan_activities.rst:72 -msgid "Select a record on which to schedule an activity. Click on the :guilabel:`🕘 (clock)` icon, then :guilabel:`Schedule An Activity`. If the record already has an activity scheduled, the clock icon may be replaced by a :guilabel:`📞 (phone)` or an :guilabel:`✉️ (envelope)` icon." +#: ../../content/applications/productivity/discuss/ice_servers.rst:74 +msgid "Odoo will redirect to the :guilabel:`ICE servers` page. Here you can define your own list of ICE servers." msgstr "" -#: ../../content/applications/productivity/discuss/overview/plan_activities.rst:0 -msgid "List view of the CRM pipeline and the option to schedule an activity." +#: ../../content/applications/productivity/discuss/ice_servers.rst:-1 +msgid "The \"ICE servers\" page in Odoo." msgstr "" -#: ../../content/applications/productivity/discuss/overview/plan_activities.rst:80 -msgid "Activity view" +#: ../../content/applications/productivity/discuss/ice_servers.rst:82 +msgid "For on-premise instances of Odoo, the package `python3-gevent` is necessary for the Discuss module to run calls/video calls on Ubuntu (Linux) servers." msgstr "" -#: ../../content/applications/productivity/discuss/overview/plan_activities.rst:82 -msgid "To open the activity view for an application, select the :guilabel:`🕘 (clock)` icon from the menu bar anywhere in the database. Select any application from the drop-down menu, and click the :guilabel:`🕘 (clock)` icon for the desired app." -msgstr "" - -#: ../../content/applications/productivity/discuss/overview/plan_activities.rst:0 -msgid "Activity menu drop down with focus on where to open activity view for CRM." -msgstr "" - -#: ../../content/applications/productivity/discuss/overview/plan_activities.rst:90 -msgid "Select a record on which to schedule an activity. Move across the row to find the desired activity type, then click the :guilabel:`＋ (plus sign)`." -msgstr "" - -#: ../../content/applications/productivity/discuss/overview/plan_activities.rst:0 -msgid "Activity view of the CRM pipeline and the option to schedule an activity." -msgstr "" - -#: ../../content/applications/productivity/discuss/overview/plan_activities.rst:98 -msgid "Activity colors, and their relation to an activity's due date, is consistent throughout Odoo, regardless of the activity type, or the view." -msgstr "" - -#: ../../content/applications/productivity/discuss/overview/plan_activities.rst:101 -msgid "Activities that appear in **green** indicate a due date sometime in the future." -msgstr "" - -#: ../../content/applications/productivity/discuss/overview/plan_activities.rst:102 -msgid "**Yellow** indicates that the activity's due date is today." -msgstr "" - -#: ../../content/applications/productivity/discuss/overview/plan_activities.rst:103 -msgid "**Red** indicates that the activity is overdue and the due date has passed." -msgstr "" - -#: ../../content/applications/productivity/discuss/overview/plan_activities.rst:105 -msgid "For example, if an activity is created for a phone call, and the due date passes, the activity appears with a red phone in list view, and a red clock on the kanban view." -msgstr "" - -#: ../../content/applications/productivity/discuss/overview/plan_activities.rst:109 -msgid "View scheduled activities" -msgstr "" - -#: ../../content/applications/productivity/discuss/overview/plan_activities.rst:111 -msgid "To view scheduled activities, open either the :menuselection:`Sales app` or :menuselection:`CRM app` and click the :guilabel:`🕘 (clock)` icon, located to the far-right side of the other view options." -msgstr "" - -#: ../../content/applications/productivity/discuss/overview/plan_activities.rst:114 -msgid "Doing so opens the activities menu, showcasing all the scheduled activities for the user, by default. To show all activities for every user, remove the :guilabel:`My Pipeline` filter from the :guilabel:`Search...` bar." -msgstr "" - -#: ../../content/applications/productivity/discuss/overview/plan_activities.rst:118 -msgid "To view a consolidated list of activities separated by the application where they were created, and by deadline, click the :guilabel:`🕘 (clock)` icon on the header menu to see the activities for that specific application in a drop-down menu." -msgstr "" - -#: ../../content/applications/productivity/discuss/overview/plan_activities.rst:122 -msgid "The possibility to :guilabel:`Add new note` and :guilabel:`Request a Document` appear at the bottom of this drop-down menu, when the :guilabel:`🕘 (clock)` icon on the header menu is clicked." -msgstr "" - -#: ../../content/applications/productivity/discuss/overview/plan_activities.rst:-1 -msgid "View of CRM leads page emphasizing the activities menu." -msgstr "" - -#: ../../content/applications/productivity/discuss/overview/plan_activities.rst:130 -msgid "Configure activity types" -msgstr "" - -#: ../../content/applications/productivity/discuss/overview/plan_activities.rst:132 -msgid "To configure the types of activities in the database, go to :menuselection:`Settings app --> Discuss --> Activities --> Activity Types`." -msgstr "" - -#: ../../content/applications/productivity/discuss/overview/plan_activities.rst:-1 -msgid "View of the settings page emphasizing the menu activity types." -msgstr "" - -#: ../../content/applications/productivity/discuss/overview/plan_activities.rst:139 -msgid "Doing so reveals the :guilabel:`Activity Types` page, where the existing activity types are found." -msgstr "" - -#: ../../content/applications/productivity/discuss/overview/plan_activities.rst:141 -msgid "To edit an existing activity type, select it from the list, then click :guilabel:`Edit`. To create a new activity type, click :guilabel:`Create`." -msgstr "" - -#: ../../content/applications/productivity/discuss/overview/plan_activities.rst:144 -msgid "At the top of a blank activity type form, start by choosing a :guilabel:`Name` for the new activity type." -msgstr "" - -#: ../../content/applications/productivity/discuss/overview/plan_activities.rst:-1 -msgid "New activity type form." -msgstr "" - -#: ../../content/applications/productivity/discuss/overview/plan_activities.rst:152 -msgid "Activity settings" -msgstr "" - -#: ../../content/applications/productivity/discuss/overview/plan_activities.rst:155 -#: ../../content/applications/productivity/iot/config/windows_iot.rst:275 -#: ../../content/applications/productivity/studio/automated_actions.rst:134 -msgid "Action" -msgstr "" - -#: ../../content/applications/productivity/discuss/overview/plan_activities.rst:157 -msgid "The *Action* field specifies the intent of the activity. Some actions trigger specific behaviors after an activity is scheduled." -msgstr "" - -#: ../../content/applications/productivity/discuss/overview/plan_activities.rst:160 -msgid "If :guilabel:`Upload Document` is selected, a link to upload a document is added directly to the planned activity in the chatter." -msgstr "" - -#: ../../content/applications/productivity/discuss/overview/plan_activities.rst:162 -msgid "If either :guilabel:`Phonecall` or :guilabel:`Meeting` are selected, users have the option to open their calendar to schedule a time for this activity." -msgstr "" - -#: ../../content/applications/productivity/discuss/overview/plan_activities.rst:164 -msgid "If :guilabel:`Request Signature` is selected, a link is added to the planned activity in the chatter that opens a signature request pop-up window." -msgstr "" - -#: ../../content/applications/productivity/discuss/overview/plan_activities.rst:168 -msgid "The actions available to select on an activity type vary, depending on the applications currently installed in the database." -msgstr "" - -#: ../../content/applications/productivity/discuss/overview/plan_activities.rst:172 -msgid "Default user" -msgstr "" - -#: ../../content/applications/productivity/discuss/overview/plan_activities.rst:174 -msgid "To automatically assign this activity to a specific user when this activity type is scheduled, choose a name from the :guilabel:`Default User` drop-down menu. If this field is left blank, the activity is assigned to the user who creates the activity." -msgstr "" - -#: ../../content/applications/productivity/discuss/overview/plan_activities.rst:179 -msgid "Default summary" -msgstr "" - -#: ../../content/applications/productivity/discuss/overview/plan_activities.rst:181 -msgid "To include notes whenever this activity type is created, enter them into the :guilabel:`Default Summary` field." -msgstr "" - -#: ../../content/applications/productivity/discuss/overview/plan_activities.rst:185 -msgid "The information in the :guilabel:`Default User` and :guilabel:`Default Summary` fields are included when an activity is created. However, they can be altered before the activity is scheduled or saved." -msgstr "" - -#: ../../content/applications/productivity/discuss/overview/plan_activities.rst:190 -msgid "Next activity" -msgstr "" - -#: ../../content/applications/productivity/discuss/overview/plan_activities.rst:192 -msgid "To automatically suggest, or trigger, a new activity after an activity has been marked complete, the :guilabel:`Chaining Type` must be set." -msgstr "" - -#: ../../content/applications/productivity/discuss/overview/plan_activities.rst:196 -msgid "Suggest next activity" -msgstr "" - -#: ../../content/applications/productivity/discuss/overview/plan_activities.rst:198 -msgid "In the :guilabel:`Chaining Type` field, select :guilabel:`Suggest Next Activity`. Upon doing so, the field underneath changes to: :guilabel:`Suggest`. Click the :guilabel:`Suggest` field drop-down menu to select any activities to recommend as follow-up tasks to this activity type." -msgstr "" - -#: ../../content/applications/productivity/discuss/overview/plan_activities.rst:202 -#: ../../content/applications/productivity/discuss/overview/plan_activities.rst:230 -msgid "In the :guilabel:`Schedule` field, choose a default deadline for these activities. To do so, configure a desired number of :guilabel:`Days`, :guilabel:`Weeks`, or :guilabel:`Months`. Then, decide if it should occur :guilabel:`after completion date` or :guilabel:`after previous activity deadline`." -msgstr "" - -#: ../../content/applications/productivity/discuss/overview/plan_activities.rst:207 -#: ../../content/applications/productivity/discuss/overview/plan_activities.rst:235 -msgid "This :guilabel:`Schedule` field information can be altered before the activity is scheduled." -msgstr "" - -#: ../../content/applications/productivity/discuss/overview/plan_activities.rst:209 -#: ../../content/applications/productivity/discuss/overview/plan_activities.rst:237 -msgid "When all configurations are complete, click :guilabel:`Save`." -msgstr "" - -#: ../../content/applications/productivity/discuss/overview/plan_activities.rst:-1 -msgid "Schedule activity popup with emphasis on recommended activities." -msgstr "" - -#: ../../content/applications/productivity/discuss/overview/plan_activities.rst:216 -msgid "If an activity has the :guilabel:`Chaining Type` set to :guilabel:`Suggest Next Activity`, and has activities listed in the :guilabel:`Suggest` field, users are presented with recommendations for activities as next steps." -msgstr "" - -#: ../../content/applications/productivity/discuss/overview/plan_activities.rst:221 -msgid "Trigger next activity" -msgstr "" - -#: ../../content/applications/productivity/discuss/overview/plan_activities.rst:223 -msgid "Setting the :guilabel:`Chaining Type` to :guilabel:`Trigger Next Activity` immediately launches the next activity once the previous one is completed." -msgstr "" - -#: ../../content/applications/productivity/discuss/overview/plan_activities.rst:226 -msgid "If :guilabel:`Trigger Next Activity` is selected in the :guilabel:`Chaining Type` field, the field beneath changes to: :guilabel:`Trigger`. From the :guilabel:`Trigger` field drop-down menu, select the activity that should be launched once this activity is completed." -msgstr "" - -#: ../../content/applications/productivity/discuss/overview/plan_activities.rst:-1 -msgid "Schedule new activity popup with emphasis on Done and launch next button." -msgstr "" - -#: ../../content/applications/productivity/discuss/overview/plan_activities.rst:244 -msgid "When an activity has the :guilabel:`Chaining Type` set to :guilabel:`Trigger Next Activity`, marking the activity as `Done` immediately launches the next activity listed in the :guilabel:`Trigger` field." -msgstr "" - -#: ../../content/applications/productivity/discuss/overview/plan_activities.rst:249 -#: ../../content/applications/productivity/discuss/overview/team_communication.rst:113 -msgid ":doc:`get_started`" -msgstr "" - -#: ../../content/applications/productivity/discuss/overview/plan_activities.rst:250 -msgid ":doc:`team_communication`" -msgstr "" - -#: ../../content/applications/productivity/discuss/overview/team_communication.rst:3 +#: ../../content/applications/productivity/discuss/team_communication.rst:3 msgid "Use channels for team communication" msgstr "" -#: ../../content/applications/productivity/discuss/overview/team_communication.rst:5 +#: ../../content/applications/productivity/discuss/team_communication.rst:5 msgid "Use channels in the Odoo *Discuss* app to organize discussions between individual teams, departments, projects, or any other group that requires regular communication. With channels, employees can communicate inside dedicated spaces within the Odoo database around specific topics, updates, and latest developments having to do with the organization." msgstr "" -#: ../../content/applications/productivity/discuss/overview/team_communication.rst:11 +#: ../../content/applications/productivity/discuss/team_communication.rst:11 msgid "Public and private channels" msgstr "" -#: ../../content/applications/productivity/discuss/overview/team_communication.rst:13 +#: ../../content/applications/productivity/discuss/team_communication.rst:13 msgid "A *Public* channel can be seen by everyone, while a *Private* one is only visible to users invited to it. To create a new channel, navigate to the :menuselection:`Discuss` app, and then click on the :guilabel:`➕ (plus)` icon next to the :guilabel:`Channels` heading in the left-side menu. After typing the name of the channel, two selectable options will appear: The first is a channel with a hashtag (`#`) to indicate that it is a public channel; the second option is a channel with a lock icon (`🔒`) next to it, to indicate that it is a private channel. Select the channel type that best fits the communication needs." msgstr "" -#: ../../content/applications/productivity/discuss/overview/team_communication.rst:-1 +#: ../../content/applications/productivity/discuss/team_communication.rst:-1 msgid "View of discuss's sidebar and a channel being created in Odoo Discuss." msgstr "" -#: ../../content/applications/productivity/discuss/overview/team_communication.rst:26 +#: ../../content/applications/productivity/discuss/team_communication.rst:26 msgid "A public channel is best used when many employees need to access information (such as company announcements), whereas a private channel could be used whenever information should be limited to specific groups (such as a specific department)." msgstr "" -#: ../../content/applications/productivity/discuss/overview/team_communication.rst:31 +#: ../../content/applications/productivity/discuss/team_communication.rst:31 msgid "Configuration options" msgstr "" -#: ../../content/applications/productivity/discuss/overview/team_communication.rst:33 +#: ../../content/applications/productivity/discuss/team_communication.rst:33 msgid "The channel's :guilabel:`Group Name`, :guilabel:`Description`, and :guilabel:`Privacy` settings can be modified by clicking on the channel's settings, represented by a :guilabel:`⚙️ (gear)` icon in the left sidebar menu, next to the channel's name." msgstr "" -#: ../../content/applications/productivity/discuss/overview/team_communication.rst:-1 +#: ../../content/applications/productivity/discuss/team_communication.rst:-1 msgid "View of a channel's settings form in Odoo Discuss." msgstr "" -#: ../../content/applications/productivity/discuss/overview/team_communication.rst:42 +#: ../../content/applications/productivity/discuss/team_communication.rst:42 msgid "Privacy and Members tabs" msgstr "" -#: ../../content/applications/productivity/discuss/overview/team_communication.rst:44 +#: ../../content/applications/productivity/discuss/team_communication.rst:44 msgid "Changing :guilabel:`Who can follow the group's activities?` controls which groups can have access to the channel." msgstr "" -#: ../../content/applications/productivity/discuss/overview/team_communication.rst:48 +#: ../../content/applications/productivity/discuss/team_communication.rst:48 msgid "Allowing :guilabel:`Everyone` to follow a private channel lets other users view and join it, as they would a public one." msgstr "" -#: ../../content/applications/productivity/discuss/overview/team_communication.rst:51 +#: ../../content/applications/productivity/discuss/team_communication.rst:51 msgid "When choosing :guilabel:`Invited people only`, specify in the :guilabel:`Members` tab which members should be invited. Inviting members can also be done from the *Discuss* app's main dashboard, by selecting the channel, clicking the *add user* icon in the top-right corner of the dashboard, and finally clicking :guilabel:`Invite to Channel` once all the users have been added." msgstr "" -#: ../../content/applications/productivity/discuss/overview/team_communication.rst:-1 +#: ../../content/applications/productivity/discuss/team_communication.rst:-1 msgid "View of Discuss' option to invite members in Odoo Discuss." msgstr "" -#: ../../content/applications/productivity/discuss/overview/team_communication.rst:60 +#: ../../content/applications/productivity/discuss/team_communication.rst:60 msgid "When the :guilabel:`Selected group of users` option is selected, it reveals the ability to add an :guilabel:`Authorized Group`, along with the options to :guilabel:`Auto Subscribe Groups` and :guilabel:`Auto Subscribe Departments`." msgstr "" -#: ../../content/applications/productivity/discuss/overview/team_communication.rst:64 +#: ../../content/applications/productivity/discuss/team_communication.rst:64 msgid "The option to :guilabel:`Auto Subscribe Groups` automatically adds users of that particular user group as followers. In other words, while :guilabel:`Authorized Groups` limits which users can access the channel, :guilabel:`Auto Subscribe Groups` automatically adds users as members as long as they are part of a specific user group. The same is true for :guilabel:`Auto Subscribe Departments`." msgstr "" -#: ../../content/applications/productivity/discuss/overview/team_communication.rst:70 +#: ../../content/applications/productivity/discuss/team_communication.rst:70 msgid "Quick search bar" msgstr "" -#: ../../content/applications/productivity/discuss/overview/team_communication.rst:72 +#: ../../content/applications/productivity/discuss/team_communication.rst:72 msgid "Once at least 20 channels, direct messages, or live chat conversations (if *Live Chat* module is installed on the database) are pinned in the sidebar, a :guilabel:`Quick search…` bar is displayed. This feature is a convenient way to filter conversations and quickly find relevant communications." msgstr "" -#: ../../content/applications/productivity/discuss/overview/team_communication.rst:-1 +#: ../../content/applications/productivity/discuss/team_communication.rst:-1 msgid "View of the Discuss' sidebar emphasizing the quick search bar in Odoo Discuss." msgstr "" -#: ../../content/applications/productivity/discuss/overview/team_communication.rst:81 +#: ../../content/applications/productivity/discuss/team_communication.rst:81 msgid "Finding channels" msgstr "" -#: ../../content/applications/productivity/discuss/overview/team_communication.rst:83 +#: ../../content/applications/productivity/discuss/team_communication.rst:83 msgid "Click on the settings :guilabel:`⚙️ (gear)` icon, located in the left sidebar, to the right of the :guilabel:`CHANNELS` collapsible menu item. Doing so will lead to a mosaic view containing all the public channels available. Users can join or leave channels on this screen by clicking the :guilabel:`JOIN` or :guilabel:`LEAVE` buttons that appear in the channel boxes." msgstr "" -#: ../../content/applications/productivity/discuss/overview/team_communication.rst:88 +#: ../../content/applications/productivity/discuss/team_communication.rst:88 msgid "There is also the ability to apply filtering criteria and save them for later use. The :guilabel:`Search...` function accepts wildcards by using the underscore character [ `_` ], and specific searches can be saved by using the :menuselection:`Favorites --> Save Current Search` drop-down menu." msgstr "" -#: ../../content/applications/productivity/discuss/overview/team_communication.rst:-1 +#: ../../content/applications/productivity/discuss/team_communication.rst:-1 msgid "View of a channel being searched through filters in Odoo Discuss" msgstr "" -#: ../../content/applications/productivity/discuss/overview/team_communication.rst:98 +#: ../../content/applications/productivity/discuss/team_communication.rst:98 msgid "Linking channel in chatter" msgstr "" -#: ../../content/applications/productivity/discuss/overview/team_communication.rst:100 +#: ../../content/applications/productivity/discuss/team_communication.rst:100 msgid "Channels can be linked in the chatter (log note) of a record in Odoo. To do so, simply type: `#` and the channel name. Click or press enter on the *channel* name. Upon logging the note a link to the channel will appear. After clicking on the link a chat window with the channel conversation will pop up in the lower right corner of the screen." msgstr "" -#: ../../content/applications/productivity/discuss/overview/team_communication.rst:105 +#: ../../content/applications/productivity/discuss/team_communication.rst:105 msgid "Users are able to contribute to this group channel (either public or member based) by typing messages in window and pressing *enter*." msgstr "" -#: ../../content/applications/productivity/discuss/overview/team_communication.rst:-1 +#: ../../content/applications/productivity/discuss/team_communication.rst:-1 msgid "Channel linked in chatter with the channel open on the lower right quadrant." msgstr "" -#: ../../content/applications/productivity/discuss/overview/team_communication.rst:114 -msgid ":doc:`plan_activities`" +#: ../../content/applications/productivity/discuss/team_communication.rst:113 +msgid ":doc:`../discuss`" msgstr "" -#: ../../content/applications/productivity/iot.rst:8 -msgid "Internet of Things (IoT)" +#: ../../content/applications/productivity/documents.rst:3 +msgid "Documents" msgstr "" -#: ../../content/applications/productivity/iot.rst:17 -msgid "The Open Platform Communications (OPC) Unified Architecture (UA) protocol is now supported by the :abbr:`IoT (Internet of Things)` box. :abbr:`OPC (Open Platform Communications)` :abbr:`UA (United Architecture)` is an open standard that specifies information exchange for industrial communication on devices, between machines and between systems. This includes communication between information technology and operational technology. :abbr:`OPC (Open Platform Communications)` :abbr:`UA (United Architecture)` can be used with any software platform, on a wide variety of devices, and deployed securely. The :abbr:`IoT (Internet of Things)` box has entered the world of the Industry 4.0 standard and can be utilized in a wide variety of industries, and for things like building automation, packaging, utilities, etc." +#: ../../content/applications/productivity/documents.rst:5 +msgid "**Odoo Documents** allows you to store, view, and manage files within Odoo." msgstr "" -#: ../../content/applications/productivity/iot/config.rst:5 -#: ../../content/applications/productivity/mail_plugins/outlook.rst:10 +#: ../../content/applications/productivity/documents.rst:7 +msgid "You can upload any file (max 64MB per file on Odoo Online) and organize them in various workspaces." +msgstr "" + +#: ../../content/applications/productivity/documents.rst:10 +msgid "`Odoo Documents: product page `_" +msgstr "" + +#: ../../content/applications/productivity/documents.rst:11 +msgid "`Odoo Tutorials: Documents basics [video] `_" +msgstr "" + +#: ../../content/applications/productivity/documents.rst:13 +msgid "`Odoo Tutorials: Using Documents with your Accounting App [video] `_" +msgstr "" + +#: ../../content/applications/productivity/documents.rst:16 +#: ../../content/applications/productivity/voip/axivox/axivox_config.rst:17 +#: ../../content/applications/productivity/voip/onsip.rst:19 msgid "Configuration" msgstr "" -#: ../../content/applications/productivity/iot/config/connect.rst:3 -msgid "Connect an IoT box to Odoo" +#: ../../content/applications/productivity/documents.rst:18 +msgid "By going to :menuselection:`Documents --> Configuration --> Settings`, you can enable the centralization of files attached to a specific area of your activity. For example, by ticking :guilabel:`Human Resources`, your HR documents are automatically available in the HR workspace, while documents related to Payroll are automatically available in the Payroll sub-workspace . You can change the default workspace using the dropdown menu and edit its properties by clicking the internal link button (:guilabel:`➔`)." msgstr "" -#: ../../content/applications/productivity/iot/config/connect.rst:5 -msgid "An Internet of Things (IoT) box is a micro-computer device that allows for the connection of input and output devices to an Odoo database. An :abbr:`IoT (Internet of Things)` box subscription is required in order to use the :abbr:`IoT (Internet of Things)` box with a secured connection. A computer is also required to set up the :abbr:`IoT (Internet of Things)` box." +#: ../../content/applications/productivity/documents.rst:-1 +msgid "Enable the centralization of files attached to a specific area of your activity." msgstr "" -#: ../../content/applications/productivity/iot/config/connect.rst:11 -msgid "`IoT Box FAQ `_" +#: ../../content/applications/productivity/documents.rst:29 +msgid "If you enable the centralization of your accounting files and documents, it is necessary to click on :guilabel:`Journals` and define each journal independently to allow automatic synchronization." msgstr "" -#: ../../content/applications/productivity/iot/config/connect.rst:13 -msgid "Begin the :abbr:`IoT (Internet of Things)` configuration process by :ref:`installing the IoT app ` on the Odoo database through the :menuselection:`Apps` application." +#: ../../content/applications/productivity/documents.rst:0 +msgid "Enable the centralization of files attached to your accounting." msgstr "" -#: ../../content/applications/productivity/iot/config/connect.rst:-1 -msgid "The Internet of Things (IoT) app on the Odoo database." +#: ../../content/applications/productivity/documents.rst:36 +msgid "If you select a new workspace, existing documents aren't moved. Only newly created documents will be found under the new workspace." msgstr "" -#: ../../content/applications/productivity/iot/config/connect.rst:20 -msgid "Next, after the *IoT app* is installed, navigate to :menuselection:`IoT app --> IoT Boxes`, and then click on the :guilabel:`Connect` button located in the upper-left corner of the :menuselection:`IoT Boxes` dashboard." +#: ../../content/applications/productivity/documents.rst:40 +msgid "Workspaces" msgstr "" -#: ../../content/applications/productivity/iot/config/connect.rst:-1 -msgid "Connecting an IoT box to the Odoo database." +#: ../../content/applications/productivity/documents.rst:42 +msgid "Workspaces are hierarchical folders having their own set of tags and :ref:`actions `. Default workspaces exist, but you can create your own by going to :menuselection:`Documents --> Configuration --> Workspaces` and clicking :guilabel:`New`. On the new page, fill in the following information:" msgstr "" -#: ../../content/applications/productivity/iot/config/connect.rst:28 -msgid "There are two recommended ways to connect the :abbr:`IoT (Internet of Things)` box to the database once the *IoT app* is installed. Follow the steps in either of the next two sections to connect the :abbr:`IoT (Internet of Things)` box via :ref:`wired ethernet connection ` or via :ref:`WiFi `." +#: ../../content/applications/productivity/documents.rst:47 +msgid ":guilabel:`Name`" msgstr "" -#: ../../content/applications/productivity/iot/config/connect.rst:-1 -msgid "Connection steps for a wired connection or WiFi connection." +#: ../../content/applications/productivity/documents.rst:48 +msgid ":guilabel:`Parent Workspace`: if you want to create a sub-workspace, select its :guilabel:`Parent Workspace`" msgstr "" -#: ../../content/applications/productivity/iot/config/connect.rst:38 -msgid "The disk image that the :abbr:`IoT (Internet of Things)` box SD card is formatted with is unique to the version of the Odoo database that the :abbr:`IoT (Internet of Things)` box is running on. Ensure that the :abbr:`IoT (Internet of Things)` box is :doc:`flashed ` with the most up-to-date disk image." +#: ../../content/applications/productivity/documents.rst:52 +#: ../../content/applications/productivity/sign.rst:236 +msgid "Tags" msgstr "" -#: ../../content/applications/productivity/iot/config/connect.rst:46 -msgid "Ethernet connection" +#: ../../content/applications/productivity/documents.rst:54 +msgid "Tags are used within workspaces to add a level of differentiation between documents. They are organized per category, and filters can be used to sort them." msgstr "" -#: ../../content/applications/productivity/iot/config/connect.rst:48 -msgid "The following is the process to connect the :abbr:`IoT (Internet of Things)` box via an ethernet cable to the Odoo database (by way of the ethernet port; RJ-45)." +#: ../../content/applications/productivity/documents.rst:57 +msgid "Tags can be created from the :guilabel:`Tags` tab. Click :guilabel:`Add a line`, create the :guilabel:`Tag Category`, and :guilabel:`Name` your tags." msgstr "" -#: ../../content/applications/productivity/iot/config/connect.rst:51 -msgid "First, connect all wired devices to the :abbr:`IoT (Internet of Things)` box (ethernet, :abbr:`USB (Universal Serial Bus)` devices, etc.). At minimum, an HDMI screen should be connected. Then, plug the :abbr:`IoT (Internet of Things)` box into a power source." +#: ../../content/applications/productivity/documents.rst:61 +msgid "The tags of a parent workspace apply to the child workspaces automatically;" msgstr "" -#: ../../content/applications/productivity/iot/config/connect.rst:55 -msgid "Immediately after the unit powers on and boots up, read the *pairing code* from the screen or from the printout of a receipt printer connected to the :abbr:`IoT (Internet of Things)` box." +#: ../../content/applications/productivity/documents.rst:62 +msgid "Tags can be created and modified by going to :menuselection:`Configuration --> Tags`;" msgstr "" -#: ../../content/applications/productivity/iot/config/connect.rst:59 -msgid "By default, the :abbr:`IoT (Internet of Things)` box will display the *pairing code* for a maximum of 5 minutes after the unit boots up. After 5 minutes, the *pairing code* will disappear for security purposes and the :abbr:`IoT (Internet of Things)` box will need to be rebooted manually by unplugging the unit from the power source for ten seconds and re-plugging it back in." +#: ../../content/applications/productivity/documents.rst:63 +msgid "Tags can also be created or edited by clicking the gear icon :guilabel:`⚙` on the left menu." msgstr "" -#: ../../content/applications/productivity/iot/config/connect.rst:65 -msgid "If no screen is attached to the :abbr:`IoT (Internet of Things)` box, then the *pairing code* can be accessed from the :abbr:`IoT (Internet of Things)` box homepage by clicking on the :guilabel:`POS Display` button. For instructions on how to access the :abbr:`IoT (Internet of Things)` box homepage visit :ref:`iot_connect/token`." +#: ../../content/applications/productivity/documents.rst:66 +msgid "Access rights" msgstr "" -#: ../../content/applications/productivity/iot/config/connect.rst:70 -msgid "On the computer, navigate to :menuselection:`IoT app --> IoT Boxes`, and then click on the :guilabel:`Connect` button located in the upper-left corner of the the :menuselection:`IoT Boxes` dashboard. Input the *pairing code* in the :guilabel:`Pairing Code` field and click on the :guilabel:`Pair` button. The database will now link to the :abbr:`IoT (Internet of Things)` box and it will appear on the :menuselection:`IoT Boxes` page." +#: ../../content/applications/productivity/documents.rst:68 +msgid "To manage your workspace access rights, go to :menuselection:`Documents --> Configuration --> Workspaces`, open the workspace you want to edit, and go to the :guilabel:`Access Rights` tab. You can add :guilabel:`Write Groups` that can view, create, and edit the workspace's documents. You can also add :guilabel:`Read Groups` that can only view the workspace's documents." msgstr "" -#: ../../content/applications/productivity/iot/config/connect.rst:79 -msgid "WiFi connection" +#: ../../content/applications/productivity/documents.rst:74 +msgid "Description" msgstr "" -#: ../../content/applications/productivity/iot/config/connect.rst:81 -msgid "The following is the process to connect the :abbr:`IoT (Internet of Things)` box via a WiFi connection to the Odoo database." +#: ../../content/applications/productivity/documents.rst:76 +msgid "You can add descriptive information to your workspace by going to :menuselection:`Documents --> Configuration --> Workspaces`, opening the workspace you want to describe and going to the :guilabel:`Description` tab." msgstr "" -#: ../../content/applications/productivity/iot/config/connect.rst:84 -msgid "First, ensure there is no ethernet cable plugged into the :abbr:`IoT (Internet of Things)` box. Then, connect all wired devices to the :abbr:`IoT (Internet of Things)` box (:abbr:`USB (Universal Serial Bus)` devices, etc.)." +#: ../../content/applications/productivity/documents.rst:81 +msgid "Workspaces can also be created and edited by clicking the gear icon :guilabel:`⚙` on the left menu." msgstr "" -#: ../../content/applications/productivity/iot/config/connect.rst:88 -msgid "After connecting the devices, plug the :abbr:`IoT (Internet of Things)` box into to a power source. On the computer, navigate to :menuselection:`IoT app --> IoT Boxes`, and then click on the :guilabel:`Connect` button located in the upper-left corner of the the :menuselection:`IoT Boxes` dashboard. Then copy the :guilabel:`Token` from the :guilabel:`WiFi connection` section as this will later be used to link the Odoo database to the :abbr:`IoT (Internet of Things)` box." +#: ../../content/applications/productivity/documents.rst:0 +msgid "Create sub-workspaces from the left menu" msgstr "" -#: ../../content/applications/productivity/iot/config/connect.rst:94 -msgid "Back on the computer, navigate to the available WiFi networks and connect to the :abbr:`IoT (Internet of Things)` box WiFi network. The WiFi network dispersed by the :abbr:`IoT (Internet of Things)` box will start with `IoTBox-xxxxxxxxxx`." +#: ../../content/applications/productivity/documents.rst:88 +msgid "Documents management" msgstr "" -#: ../../content/applications/productivity/iot/config/connect.rst:-1 -msgid "WiFi networks available on the computer." +#: ../../content/applications/productivity/documents.rst:90 +msgid "When selecting or opening a document, the right panel displays different options. On the top, additional options might be available: :guilabel:`Download`, :guilabel:`Share`, :guilabel:`Replace`, :guilabel:`Lock` or :guilabel:`Split`. It is also possible to :guilabel:`Open chatter` or :guilabel:`Archive` the document." msgstr "" -#: ../../content/applications/productivity/iot/config/connect.rst:102 -msgid "Upon connecting to the :abbr:`IoT (Internet of Things)` box WiFi, a browser will automatically redirect to the :menuselection:`Configure Iot Box` wizard. Name the :abbr:`IoT (Internet of Things)` box, then paste the previously copied *token* into the :guilabel:`Server Token` field, and then click on :guilabel:`Next`." +#: ../../content/applications/productivity/documents.rst:-1 +msgid "right panel options" msgstr "" -#: ../../content/applications/productivity/iot/config/connect.rst:-1 -msgid "Enter the server token into the IoT box." +#: ../../content/applications/productivity/documents.rst:99 +msgid "Then, you can modify the name of your file by clicking on :guilabel:`Document`. A :guilabel:`Contact` or an :guilabel:`Owner` can be assigned. The related :guilabel:`Workspace` can be modified and it is possible to access the related :guilabel:`Journal Entry` or add :guilabel:`Tags`." msgstr "" -#: ../../content/applications/productivity/iot/config/connect.rst:112 -msgid "If the :abbr:`IoT (Internet of Things)` box WiFi connection wizard doesn't start, then see the documentation on :ref:`connecting with a token `." +#: ../../content/applications/productivity/documents.rst:105 +msgid "The :guilabel:`Contact` is the person related to the document and assigned to it. He can only view the document and not modify it. I.e.: an existing supplier in your database is the contact for their bill." msgstr "" -#: ../../content/applications/productivity/iot/config/connect.rst:115 -msgid "Now, choose the WiFi network that the :abbr:`IoT (Internet of Things)` box will connect with (enter the password if there is one) and click on :guilabel:`Connect`. Wait a few seconds and the browser will redirect to the :abbr:`IoT (Internet of Things)` box homepage. The computer may need to be manually re-connected back to the original WiFi connection, if this does not happen automatically." +#: ../../content/applications/productivity/documents.rst:108 +msgid "The person who creates a document is, by default :guilabel:`Owner` of it and has complete rights to it. It is possible to replace the owner of a document. I.e., an employee must be owner of a document to be able to see it in \"My Profile\"." msgstr "" -#: ../../content/applications/productivity/iot/config/connect.rst:-1 -msgid "Configuring the WiFi for the IoT box." +#: ../../content/applications/productivity/documents.rst:112 +msgid "Different :ref:`Actions ` are available at the bottom of the right panel, depending on the workspace where your document is stored." msgstr "" -#: ../../content/applications/productivity/iot/config/connect.rst:124 -msgid "After completing each step, the :abbr:`IoT (Internet of Things)` box should appear when navigating to :menuselection:`IoT app --> IoT Boxes` on the Odoo database." +#: ../../content/applications/productivity/documents.rst:116 +msgid "Split PDF documents" msgstr "" -#: ../../content/applications/productivity/iot/config/connect.rst:-1 -msgid "The IoT box has been successfully configured on the Odoo database." +#: ../../content/applications/productivity/documents.rst:118 +msgid "Select the PDF you want to split, and click the scissors icon. A new view displays all the pages of the document." msgstr "" -#: ../../content/applications/productivity/iot/config/connect.rst:132 -msgid "The :abbr:`IoT (Internet of Things)` box may need to be manually rebooted upon successfully connecting via WiFi for the box to appear in the *IoT app* on the Odoo database. To do so, simply unplug the device and plug it back into the power source after ten seconds." +#: ../../content/applications/productivity/documents.rst:121 +msgid "By default, each page of the document will be split when clicking :guilabel:`Split`. To remove a split between two pages, click on the scissors icon." msgstr "" -#: ../../content/applications/productivity/iot/config/connect.rst:139 -msgid "Manually connecting the IoT box using the token" +#: ../../content/applications/productivity/documents.rst:-1 +msgid "split your documents" msgstr "" -#: ../../content/applications/productivity/iot/config/connect.rst:141 -msgid "A manual connection of the :abbr:`IoT (Internet of Things)` box to the :abbr:`IoT (Internet of Things)` app can be made using the *token*, from a computer. The *token* can be found by navigating to :menuselection:`IoT app --> IoT Boxes` and clicking on :guilabel:`Connect`." +#: ../../content/applications/productivity/documents.rst:128 +msgid "To merge documents from your dashboard, select them and click the scissors icon. Click on the scissors between the two documents and click :guilabel:`Split` to merge the documents." msgstr "" -#: ../../content/applications/productivity/iot/config/connect.rst:145 -msgid "Under the :guilabel:`WiFi Connection` section of the :guilabel:`Connect an IoT Box` page that appears, click :guilabel:`Copy` to the right of the :guilabel:`Token`. This token will be entered into the :abbr:`IoT (Internet of Things)` box homepage." +#: ../../content/applications/productivity/documents.rst:132 +msgid "Additional features" msgstr "" -#: ../../content/applications/productivity/iot/config/connect.rst:149 -msgid "Access the :abbr:`IoT (Internet of Things)` box homepage by entering the :abbr:`IP (Internet Protocol)` address of the :abbr:`IoT (Internet of Things)` box into a browser window from a computer on the same network as the :abbr:`IoT (Internet of Things)` box (preferably by ethernet connection)." +#: ../../content/applications/productivity/documents.rst:134 +msgid "Select a workspace and click the arrow next to the :guilabel:`Upload` button to access additional features:" msgstr "" -#: ../../content/applications/productivity/iot/config/connect.rst:154 -msgid "The :abbr:`IP (Internet Protocol)` address can be accessed by the router admin console that the :abbr:`IoT (Internet of Things)` box is connected to, or by connecting a receipt printer to the :abbr:`IoT (Internet of Things)` box. A receipt will print out with the :abbr:`IoT (Internet of Things)` box's :abbr:`IP (Internet Protocol)` address on it." +#: ../../content/applications/productivity/documents.rst:138 +msgid "Request" msgstr "" -#: ../../content/applications/productivity/iot/config/connect.rst:159 -msgid "On the :abbr:`IoT (Internet of Things)` box homepage, enter the *token* under the :guilabel:`Server` section by clicking on :guilabel:`Configure`. Then, paste the *token* into the :guilabel:`Server Token` field and click :guilabel:`Connect`. The :abbr:`IoT (Internet of Things)` box will then link to the Odoo database." +#: ../../content/applications/productivity/documents.rst:140 +msgid "You can create \"missing documents\" and organize them as documents, to remind users to download them." msgstr "" -#: ../../content/applications/productivity/iot/config/connect.rst:167 -msgid "IoT box schema" +#: ../../content/applications/productivity/documents.rst:142 +msgid "Select the workspace where the file should be stored, click :guilabel:`Upload`, then :guilabel:`Request`. Add the :guilabel:`Document Name`, select the person you need it from in the :guilabel:`Request To` field, fill in the :guilabel:`Due Date In`, confirm the :guilabel:`Workspace`, the document should belong to, and add :guilabel:`Tags` and a :guilabel:`Note`, if needed. Then, click :guilabel:`Request`. A placeholder for the missing document is created in the workspace." msgstr "" -#: ../../content/applications/productivity/iot/config/connect.rst:170 -msgid "Raspberry Pi 4" +#: ../../content/applications/productivity/documents.rst:149 +msgid "When your document is available, click the placeholder to upload it." msgstr "" -#: ../../content/applications/productivity/iot/config/connect.rst:174 -msgid "The Odoo IoT box (Raspberry Pi 4) schema with labels." +#: ../../content/applications/productivity/documents.rst:151 +msgid "You can see all missing documents by going to the **Activity** view and to the :guilabel:`Requested Document` column." msgstr "" -#: ../../content/applications/productivity/iot/config/connect.rst:177 -msgid "Raspberry Pi 3" +#: ../../content/applications/productivity/documents.rst:155 +msgid "From the :guilabel:`Activity` view, you can send a **reminder email** to users from whom you are expecting a document. Go to the :guilabel:`Requested Document` column, click on ⋮ and :guilabel:`Document Request: Reminder`." msgstr "" -#: ../../content/applications/productivity/iot/config/connect.rst:181 -msgid "The Odoo IoT box (Raspberry Pi 3) schema with labels." +#: ../../content/applications/productivity/documents.rst:159 +msgid "Click on a date to see the details of a specific request. You can update it by clicking on the pen icon, :guilabel:`Preview` the content of the reminder email, or :guilabel:`Send Now` to send a reminder email." msgstr "" -#: ../../content/applications/productivity/iot/config/flash_sdcard.rst:3 -msgid "Flashing the SD card" +#: ../../content/applications/productivity/documents.rst:0 +msgid "send a reminder email from the Activity view" msgstr "" -#: ../../content/applications/productivity/iot/config/flash_sdcard.rst:5 -msgid "In some circumstances, the :abbr:`IoT (Internet of Things)` box's micro SD Card may need to be re-flashed to benefit from Odoo's latest :abbr:`IoT (Internet of Things)` image update. This means that the Odoo :abbr:`IoT (Internet of Things)` box software may need to be updated." +#: ../../content/applications/productivity/documents.rst:167 +msgid "Add a link" msgstr "" -#: ../../content/applications/productivity/iot/config/flash_sdcard.rst:10 -msgid "Upgrade from the IoT box home page" +#: ../../content/applications/productivity/documents.rst:169 +msgid "To add a link to your documents dashboard, click on :guilabel:`Add a Link`, enter the :guilabel:`URL`, and :guilabel:`Name` it." msgstr "" -#: ../../content/applications/productivity/iot/config/flash_sdcard.rst:12 -msgid "Go to the :abbr:`IoT (Internet of Things)` box homepage by navigating to :menuselection:`IoT app --> IoT Boxes` and clicking on the :guilabel:`IP address` of the :abbr:`IoT (Internet of Things)` box. Then click on :guilabel:`Update` (next to the version number)." +#: ../../content/applications/productivity/documents.rst:173 +msgid "Share" msgstr "" -#: ../../content/applications/productivity/iot/config/flash_sdcard.rst:16 -msgid "If a new version of the :abbr:`IoT (Internet of Things)` Box image is available, an :guilabel:`Upgrade to _xx.xx_` button will appear at the bottom of the page. Click this button to upgrade the unit and the :abbr:`IoT (Internet of Things)` box will then flash itself to the new version. All of the previous configurations will be saved." +#: ../../content/applications/productivity/documents.rst:175 +msgid "You can create a share link to a document or all documents of a workspace. It allows anyone to download the file(s) or upload files to a workspace." msgstr "" -#: ../../content/applications/productivity/iot/config/flash_sdcard.rst:22 -msgid "This process can take more than 30 minutes. Do not turn off or unplug the :abbr:`IoT (Internet of Things)` box as it would leave it in an inconsistent state. This means that the :abbr:`IoT (Internet of Things)` box will need to be re-flashed with a new image. See :ref:`flash_sdcard/etcher`." +#: ../../content/applications/productivity/documents.rst:178 +msgid "To do so, select the workspace or the document and click the arrow next to the :guilabel:`Upload` button then :guilabel:`Share`. On the pop-up, the share :guilabel:`URL` is displayed. :guilabel:`Copy` it to share it with anyone. :guilabel:`Name` the share link and set a validity date for the URL by filling in the :guilabel:`Valid Until` field. Tick the :guilabel:`Include Sub Folders` box if you also want to share a workspace's sub-folders. To let users upload their own documents, select :guilabel:`Download and Upload`." msgstr "" -#: ../../content/applications/productivity/iot/config/flash_sdcard.rst:-1 -msgid "IoT box software upgrade in the IoT Box Home Page." +#: ../../content/applications/productivity/documents.rst:186 +msgid "It is possible to only share one or more documents (without their workspace) by selecting them and clicking :guilabel:`Share`." msgstr "" -#: ../../content/applications/productivity/iot/config/flash_sdcard.rst:34 -msgid "Upgrade with Etcher Software" +#: ../../content/applications/productivity/documents.rst:190 +msgid "New spreadsheet" msgstr "" -#: ../../content/applications/productivity/iot/config/flash_sdcard.rst:37 -msgid "A computer with a micro SD card reader/adapter is required in order to re-flash the micro SD card." +#: ../../content/applications/productivity/documents.rst:192 +msgid "To create a new :doc:`spreadsheet `, click :guilabel:`New Spreadsheet`. You can select a :guilabel:`Blank spreadsheet` or an :doc:`existing template `." msgstr "" -#: ../../content/applications/productivity/iot/config/flash_sdcard.rst:40 -msgid "Navigate to Balena's website and download `Etcher `_. It's a free and open-source utility used for burning image files onto drives. Click to `download `_. Install and launch the program on the computer." +#: ../../content/applications/productivity/documents.rst:198 +msgid "Workflow actions" msgstr "" -#: ../../content/applications/productivity/iot/config/flash_sdcard.rst:44 -msgid "Then download the version-specific :abbr:`IoT (Internet of Things)` image from `nightly `_." +#: ../../content/applications/productivity/documents.rst:200 +msgid "Workflow actions help manage documents and overall business operations. These are automated actions that can be created and customized for each workspace. With a single click you can, for example, create, move, sign, and add tags to a document, and process bills." msgstr "" -#: ../../content/applications/productivity/iot/config/flash_sdcard.rst:47 -msgid "The following are image versions on the `nightly `_ website with their corresponding Odoo database version:" +#: ../../content/applications/productivity/documents.rst:204 +msgid "These workflow actions appear on the right panel when a document meets the set criteria." msgstr "" -#: ../../content/applications/productivity/iot/config/flash_sdcard.rst:50 -msgid "Odoo V16 --> iotbox-latest.zip" +#: ../../content/applications/productivity/documents.rst:207 +msgid "Create workflow actions" msgstr "" -#: ../../content/applications/productivity/iot/config/flash_sdcard.rst:51 -msgid "Odoo V15 --> iotboxv21_10.zip" +#: ../../content/applications/productivity/documents.rst:209 +msgid "To create workflow actions, go to :menuselection:`Documents --> Configuration --> Actions` and click :guilabel:`New`." msgstr "" -#: ../../content/applications/productivity/iot/config/flash_sdcard.rst:52 -msgid "Odoo V14 --> iotboxv21_04.zip" +#: ../../content/applications/productivity/documents.rst:213 +msgid "An action applies to all **sub-workspaces** under the :guilabel:`Related Workspace` you selected." msgstr "" -#: ../../content/applications/productivity/iot/config/flash_sdcard.rst:53 -msgid "Odoo V13 --> iotboxv20_10.zip" +#: ../../content/applications/productivity/documents.rst:216 +msgid "Set the conditions" msgstr "" -#: ../../content/applications/productivity/iot/config/flash_sdcard.rst:55 -msgid "The images should be downloaded and extracted to a convenient file location." +#: ../../content/applications/productivity/documents.rst:218 +msgid "You can :guilabel:`Create` a new :guilabel:`Action` or edit an existing one. You can define the :guilabel:`Action Name` and then set the conditions that trigger the appearance of the action button (:guilabel:`▶`) on the right-side panel when selecting a file." msgstr "" -#: ../../content/applications/productivity/iot/config/flash_sdcard.rst:57 -msgid "After this step is complete, insert the :abbr:`IoT (Internet of Things)` box's micro SD card into the computer or reader. Open *Etcher* and select :guilabel:`Flash from file`, then find and select the image just downloaded and extracted. Next, select the drive the image should be burned to. Lastly, click on :guilabel:`Flash` and wait for the process to finish." +#: ../../content/applications/productivity/documents.rst:222 +msgid "There are three basic types of conditions you can set:" msgstr "" -#: ../../content/applications/productivity/iot/config/flash_sdcard.rst:-1 -msgid "Balena's Etcher software dashboard." +#: ../../content/applications/productivity/documents.rst:224 +msgid ":guilabel:`Tags`: you can use the :guilabel:`Contains` and :guilabel:`Does not contain` conditions, meaning the files *must have* or *mustn't have* the tags set here." msgstr "" -#: ../../content/applications/productivity/iot/config/flash_sdcard.rst:67 -msgid "An alternative software for flashing the micro SD card is *Raspberry Pi Imager*. Download the *Raspberry Pi* software `here `_." +#: ../../content/applications/productivity/documents.rst:227 +msgid ":guilabel:`Contact`: the files must be associated with the contact set here." msgstr "" -#: ../../content/applications/productivity/iot/config/https_certificate_iot.rst:5 -msgid "HTTPS certificate (IoT)" +#: ../../content/applications/productivity/documents.rst:229 +msgid ":guilabel:`Owner`: the files must be associated with the owner set here." msgstr "" -#: ../../content/applications/productivity/iot/config/https_certificate_iot.rst:8 -msgid "What is HTTPS?" +#: ../../content/applications/productivity/documents.rst:-1 +msgid "Example of a workflow action's basic condition in Odoo Documents" msgstr "" -#: ../../content/applications/productivity/iot/config/https_certificate_iot.rst:10 -msgid "*Hypertext Transfer Protocol Secure* (HTTPS) is the secure version of *Hypertext Transfer Protocol* (HTTP), which is the primary protocol used to send data back and forth between a web browser and a website. :abbr:`HTTPS (Hypertext Transfer Protocol Secure)` is encrypted in order to increase the security of data transfer." +#: ../../content/applications/productivity/documents.rst:235 +msgid "If you don't set any conditions, the action button appears for all files inside the selected workspace." msgstr "" -#: ../../content/applications/productivity/iot/config/https_certificate_iot.rst:15 -msgid ":abbr:`HTTPS (Hypertext Transfer Protocol Secure)` uses an encryption protocol to encrypt communications. The protocol is called *Transport Layer Security* (TLS), although formerly it was known as *Secure Sockets Layer* (SSL)." +#: ../../content/applications/productivity/documents.rst:239 +msgid "Advanced condition type: domain" msgstr "" -#: ../../content/applications/productivity/iot/config/https_certificate_iot.rst:19 -msgid ":abbr:`HTTPS (Hypertext Transfer Protocol Secure)` occurs based upon the transmission of :abbr:`TLS (Transport Layer Security)`/:abbr:`SSL (Secure Sockets Layer)` certificates, which verify that a particular provider is who they say they are." +#: ../../content/applications/productivity/documents.rst:242 +msgid "It is recommended to have some knowledge of Odoo development to configure *Domain* filters properly." msgstr "" -#: ../../content/applications/productivity/iot/config/https_certificate_iot.rst:24 -msgid "In this documentation and throughout Odoo the term \"HTTPS certificate\" will be used to define the fact that the :abbr:`SSL (Secure Sockets Layer)` certificate is valid and allows a :abbr:`HTTPS (Hypertext Transfer Protocol Secure)` connection." +#: ../../content/applications/productivity/documents.rst:245 +msgid "The :ref:`developer mode ` needs to be activated to access the :guilabel:`Domain` condition from the :guilabel:`Actions` tab. Once done, select the :guilabel:`Domain` condition type and click :guilabel:`Add condition`." msgstr "" -#: ../../content/applications/productivity/iot/config/https_certificate_iot.rst:29 -msgid "Why is it needed?" +#: ../../content/applications/productivity/documents.rst:249 +msgid "To create a rule, you typically select a :guilabel:`field`, an :guilabel:`operator`, and a :guilabel:`value`. For example, if you want to add a workflow action to all the PDF files inside a workspace, set the :guilabel:`field` to *Mime Type*, the :guilabel:`operator` to *contains*, and the pdf :guilabel:`value`." msgstr "" -#: ../../content/applications/productivity/iot/config/https_certificate_iot.rst:31 -msgid "In order to communicate with certain network devices (in particular for payment terminals), the usage of :abbr:`HTTPS (Hypertext Transfer Protocol Secure)` is mandatory. If the :abbr:`HTTPS (Hypertext Transfer Protocol Secure)` certificate isn't valid, some devices won't be able to interact with the :abbr:`IoT (Internet of Things)` Box." +#: ../../content/applications/productivity/documents.rst:-1 +msgid "Example of a workflow action's domain condition in Odoo Documents" msgstr "" -#: ../../content/applications/productivity/iot/config/https_certificate_iot.rst:37 -msgid "How to obtain a Hypertext Transfer Protocol Secure (HTTPS) certificate" +#: ../../content/applications/productivity/documents.rst:257 +msgid "Click :guilabel:`Add New Rule` (plus icon) and :guilabel:`Add branch` to add conditions and sub-conditions. You can then specify if your rule should match :guilabel:`all` or :guilabel:`any` conditions. You can also edit the rule directly using the :guilabel:`Code editor`." msgstr "" -#: ../../content/applications/productivity/iot/config/https_certificate_iot.rst:39 -msgid "The generation of the :abbr:`HTTPS (Hypertext Transfer Protocol Secure)` certificate is automatic." +#: ../../content/applications/productivity/documents.rst:262 +msgid "Configure the actions" msgstr "" -#: ../../content/applications/productivity/iot/config/https_certificate_iot.rst:41 -msgid "The :abbr:`IoT (Internet of Things)` Box will send a specific request to ``_ which will send back the :abbr:`HTTPS (Hypertext Transfer Protocol Secure)` certificate if the :abbr:`IoT (Internet of Things)` box and database are eligible." +#: ../../content/applications/productivity/documents.rst:264 +msgid "Select the :guilabel:`Actions` tab to set up your action. You can simultaneously:" msgstr "" -#: ../../content/applications/productivity/iot/config/https_certificate_iot.rst:48 -msgid "Internet of Things (IoT) eligibility" +#: ../../content/applications/productivity/documents.rst:266 +msgid "**Set Contact**: add a contact to the file, or replace an existing contact with a new one." msgstr "" -#: ../../content/applications/productivity/iot/config/https_certificate_iot.rst:50 -msgid "The database should be a **production** instance. The database instance should not be a copy, a duplicate, a staging, or a development environment." +#: ../../content/applications/productivity/documents.rst:267 +msgid "**Set Owner**: add an owner to the file, or replace an existing owner with a new one." msgstr "" -#: ../../content/applications/productivity/iot/config/https_certificate_iot.rst:52 -msgid "The Odoo subscription must:" +#: ../../content/applications/productivity/documents.rst:268 +msgid "**Move to Workspace**: move the file to any workspace." msgstr "" -#: ../../content/applications/productivity/iot/config/https_certificate_iot.rst:54 -msgid "Have an :guilabel:`IoT Box Subscription` line." +#: ../../content/applications/productivity/documents.rst:269 +msgid "**Create**: create one of the following items attached to the file in your database:" msgstr "" -#: ../../content/applications/productivity/iot/config/https_certificate_iot.rst:55 -msgid ":guilabel:`Status` must be :guilabel:`In Progress`." +#: ../../content/applications/productivity/documents.rst:271 +msgid "**Link to record**: link the document to a record (i.e. link to a vehicle in Fleet);" msgstr "" -#: ../../content/applications/productivity/iot/config/https_certificate_iot.rst:57 -msgid "If the subscription is linked to a ``_ portal user check the information on the portal subscription page." +#: ../../content/applications/productivity/documents.rst:272 +msgid "**Product template**: create a product you can edit directly;" msgstr "" -#: ../../content/applications/productivity/iot/config/https_certificate_iot.rst:0 -msgid "Odoo.com portal subscriptions filtered by \"in progress\"." +#: ../../content/applications/productivity/documents.rst:273 +msgid "**Task**: create a Project task you can edit directly;" msgstr "" -#: ../../content/applications/productivity/iot/config/https_certificate_iot.rst:64 -msgid "In this case, both subscriptions are considered \"in progress\" as the :guilabel:`Filter By\\: In Progress` was used." +#: ../../content/applications/productivity/documents.rst:274 +msgid "**Signature PDF template**: create a new Sign template to send out;" msgstr "" -#: ../../content/applications/productivity/iot/config/https_certificate_iot.rst:68 -msgid "If the subscription is in question, contact the database's Account Manager or Partner regarding the matter." +#: ../../content/applications/productivity/documents.rst:275 +msgid "**PDF to sign**: create a PDF to sign;" msgstr "" -#: ../../content/applications/productivity/iot/config/https_certificate_iot.rst:72 -msgid "Troubleshooting Hypertext Transfer Protocol Secure (HTTPS) certificate errors" +#: ../../content/applications/productivity/documents.rst:276 +msgid "**Applicant**: create a new HR application you can edit directly;" msgstr "" -#: ../../content/applications/productivity/iot/config/https_certificate_iot.rst:74 -msgid "If anything goes wrong during the process of the \"HTTPS certificate\" generation or reception, a specific error will code be given on the :abbr:`IoT (Internet of Things)` box home page." +#: ../../content/applications/productivity/documents.rst:277 +msgid "**Vendor bill**: create a vendor bill using OCR and AI to scrape information from the file content;" msgstr "" -#: ../../content/applications/productivity/iot/config/https_certificate_iot.rst:78 -msgid "Accessing the :abbr:`IoT (Internet of Things)` box homepage will check for the presence of the \"HTTPS certificate\" and will attempt its generation if it is missing. As such, if there is an error on the :abbr:`IoT (Internet of Things)` box home page, refresh the :abbr:`IoT (Internet of Things)` home page to see if the error disappears." +#: ../../content/applications/productivity/documents.rst:279 +msgid "**Customer invoice**: create a customer invoice using OCR and AI to scrape information from the file;" msgstr "" -#: ../../content/applications/productivity/iot/config/https_certificate_iot.rst:84 -msgid "`ERR_IOT_HTTPS_CHECK_NO_SERVER`" +#: ../../content/applications/productivity/documents.rst:281 +msgid "**Vendor credit note**: create a vendor credit note using OCR and AI to scrape information from the file;" msgstr "" -#: ../../content/applications/productivity/iot/config/https_certificate_iot.rst:88 -#: ../../content/applications/productivity/iot/config/https_certificate_iot.rst:101 -#: ../../content/applications/productivity/iot/config/https_certificate_iot.rst:110 -#: ../../content/applications/productivity/iot/config/https_certificate_iot.rst:132 -#: ../../content/applications/productivity/iot/config/https_certificate_iot.rst:149 -#: ../../content/applications/productivity/iot/config/https_certificate_iot.rst:166 -msgid "Reason:" +#: ../../content/applications/productivity/documents.rst:283 +msgid "**Credit note**: create a customer credit note using OCR and AI to scrape information from the file;" msgstr "" -#: ../../content/applications/productivity/iot/config/https_certificate_iot.rst:87 -msgid "The configuration regarding the server is missing. In other words, the Odoo instance is not connected with the IoT box." +#: ../../content/applications/productivity/documents.rst:285 +msgid "**Miscellaneous Operations**: create a record in :guilabel:`Miscellaneous Operations` in Accounting;" msgstr "" -#: ../../content/applications/productivity/iot/config/https_certificate_iot.rst:91 -#: ../../content/applications/productivity/iot/config/https_certificate_iot.rst:104 -#: ../../content/applications/productivity/iot/config/https_certificate_iot.rst:114 -#: ../../content/applications/productivity/iot/config/https_certificate_iot.rst:137 -#: ../../content/applications/productivity/iot/config/https_certificate_iot.rst:159 -#: ../../content/applications/productivity/iot/config/https_certificate_iot.rst:170 -msgid "Solution:" +#: ../../content/applications/productivity/documents.rst:287 +msgid "**Bank Statement**: create a Bank Statement in Finance;" msgstr "" -#: ../../content/applications/productivity/iot/config/https_certificate_iot.rst:91 -msgid "Ensure that the server is configured." +#: ../../content/applications/productivity/documents.rst:288 +msgid "**Expense**: create an expense automatically based on a file's content." msgstr "" -#: ../../content/applications/productivity/iot/config/https_certificate_iot.rst:94 -#: ../../content/applications/productivity/iot/config/windows_iot.rst:121 -msgid ":doc:`/applications/productivity/iot/config/connect`" +#: ../../content/applications/productivity/documents.rst:290 +msgid "**Set Tags**: add, remove, and replace any number of tags." msgstr "" -#: ../../content/applications/productivity/iot/config/https_certificate_iot.rst:97 -msgid "`ERR_IOT_HTTPS_CHECK_CERT_READ_EXCEPTION`" +#: ../../content/applications/productivity/documents.rst:291 +msgid "**Activities - Mark all as Done**: mark all activities linked to the file as done." msgstr "" -#: ../../content/applications/productivity/iot/config/https_certificate_iot.rst:100 -msgid "An unhandled error happened when trying to read the existing :abbr:`HTTPS (Hypertext Transfer Protocol Secure)` certificate." +#: ../../content/applications/productivity/documents.rst:292 +msgid "**Activities - Schedule Activity**: create a new activity linked to the file as configured in the action. You can choose to set the activity on the document owner." msgstr "" -#: ../../content/applications/productivity/iot/config/https_certificate_iot.rst:104 -msgid "Ensure that the :abbr:`HTTPS (Hypertext Transfer Protocol Secure)` certificate file is readable." +#: ../../content/applications/productivity/documents.rst:-1 +msgid "Example of a workflow action Odoo Documents" msgstr "" -#: ../../content/applications/productivity/iot/config/https_certificate_iot.rst:107 -msgid "`ERR_IOT_HTTPS_LOAD_NO_CREDENTIAL`" +#: ../../content/applications/productivity/documents.rst:299 +msgid "Digitize documents with AI and optical character recognition (OCR)" msgstr "" -#: ../../content/applications/productivity/iot/config/https_certificate_iot.rst:110 -msgid "The contract and/or database :abbr:`UUID (Universal Unique Identifier)` is missing." +#: ../../content/applications/productivity/documents.rst:301 +msgid "Documents available in the Finance workspace can be digitized. Select the document to digitize, click :guilabel:`Create Bill`, :guilabel:`Create Customer Invoice`, or :guilabel:`Create credit note`, and then click :guilabel:`Send for Digitization`." msgstr "" -#: ../../content/applications/productivity/iot/config/https_certificate_iot.rst:113 -msgid "Ensure that both values are configured as intended. To modify them, go to the :abbr:`IoT (Internet of Things)` box home page, and navigate to :guilabel:`Credential`." -msgstr "" - -#: ../../content/applications/productivity/iot/config/https_certificate_iot.rst:117 -msgid "`ERR_IOT_HTTPS_LOAD_REQUEST_EXCEPTION`" -msgstr "" - -#: ../../content/applications/productivity/iot/config/https_certificate_iot.rst:120 -msgid "An unexpected error happened when the :abbr:`IoT (Internet of Things)` box tried to reach ``_. The causes are likely due to the network infrastructure/configuration:" -msgstr "" - -#: ../../content/applications/productivity/iot/config/https_certificate_iot.rst:124 -msgid "The :abbr:`IoT (Internet of Things)` box does not have access to internet." -msgstr "" - -#: ../../content/applications/productivity/iot/config/https_certificate_iot.rst:125 -msgid "The network does not allow the :abbr:`IoT (Internet of Things)` box to communicate with ``_. This may be due to network devices preventing the communication (firewalls, etc.) or the network configuration (:abbr:`VPN (Virtual Private Network)`, etc.)." -msgstr "" - -#: ../../content/applications/productivity/iot/config/https_certificate_iot.rst:131 -msgid "More information regarding the error that occurred can be found in the full request exception details, which are in the :abbr:`IoT (Internet of Things)` box logs." -msgstr "" - -#: ../../content/applications/productivity/iot/config/https_certificate_iot.rst:136 -msgid "Consult with your system or network administrator should this issue arise. This error code depends on the network infrastructure and goes beyond Odoo support's service scope." -msgstr "" - -#: ../../content/applications/productivity/iot/config/https_certificate_iot.rst:140 -msgid "`ERR_IOT_HTTPS_LOAD_REQUEST_STATUS`" -msgstr "" - -#: ../../content/applications/productivity/iot/config/https_certificate_iot.rst:143 -msgid "The IoT-box was able to reach ``_ but received an unusual `HTTP response (status codes) `_." -msgstr "" - -#: ../../content/applications/productivity/iot/config/https_certificate_iot.rst:147 -msgid "This error code will also give the HTTP response status codes. For example, if the error reads `ERR_IOT_HTTPS_LOAD_REQUEST_STATUS 404` it means that the page returned a 404 error, which is the \"Page Not Found\" code." -msgstr "" - -#: ../../content/applications/productivity/iot/config/https_certificate_iot.rst:152 -msgid "Check if ``_ is down using a web browser, as it's possible that it is down due to maintenance." -msgstr "" - -#: ../../content/applications/productivity/iot/config/https_certificate_iot.rst:155 -msgid "If ``_ is down due to maintenance, unfortunately there is nothing that can be done but instead wait for it to recover." -msgstr "" - -#: ../../content/applications/productivity/iot/config/https_certificate_iot.rst:157 -msgid "If ``_ is not down due to maintenance, open a `support ticket `_ on the matter. Ensure that the 3 digits status code next to the code error is included in the support ticket." -msgstr "" - -#: ../../content/applications/productivity/iot/config/https_certificate_iot.rst:162 -msgid "`ERR_IOT_HTTPS_LOAD_REQUEST_NO_RESULT`" -msgstr "" - -#: ../../content/applications/productivity/iot/config/https_certificate_iot.rst:165 -msgid "The :abbr:`IoT (Internet of Things)` box was able to reach ``_ but it refused to deliver the :abbr:`HTTPS (Hypertext Transfer Protocol Secure)` certificate." -msgstr "" - -#: ../../content/applications/productivity/iot/config/https_certificate_iot.rst:169 -msgid "Ensure that the :abbr:`IoT (Internet of Things)` box and database are eligible for a certificate: :ref:`Internet of Things (IoT) eligibility `." -msgstr "" - -#: ../../content/applications/productivity/iot/config/https_certificate_iot.rst:173 -msgid "How to ensure that the HTTPS certificate is correct" -msgstr "" - -#: ../../content/applications/productivity/iot/config/https_certificate_iot.rst:175 -msgid "If the certificate has been applied successfully, a new :abbr:`HTTPS (Hypertext Transfer Protocol Secure)` :abbr:`URL (Uniform Resource Locator)` for the :abbr:`IoT (Internet of Things)` box ending with `.odoo-iot.com` will appear on the Odoo database, inside of the :menuselection:`IoT` application on that specific device's form." -msgstr "" - -#: ../../content/applications/productivity/iot/config/https_certificate_iot.rst:-1 -msgid "Odoo IoT app IoT box with .odoo-iot.com domain." -msgstr "" - -#: ../../content/applications/productivity/iot/config/https_certificate_iot.rst:184 -msgid "When navigating to the :abbr:`URL (Uniform Resource Locator)` in a browser a secured :abbr:`HTTPS (Hypertext Transfer Protocol Secure)` connection will be established." -msgstr "" - -#: ../../content/applications/productivity/iot/config/https_certificate_iot.rst:191 -msgid "Example of valid SSL certificate details on the browser." -msgstr "" - -#: ../../content/applications/productivity/iot/config/https_certificate_iot.rst:191 -msgid "Padlock in Chrome on Windows 10 attesting the fact that the connection is secured in :abbr:`HTTPS (Hypertext Transfer Protocol Secure)`." -msgstr "" - -#: ../../content/applications/productivity/iot/config/https_certificate_iot.rst:194 -msgid "The IoT-box homepage will now display an `OK` status next to `HTTPS certificate`. The drop-down menu icon, when clicked, will reveal information regarding the certificate." -msgstr "" - -#: ../../content/applications/productivity/iot/config/https_certificate_iot.rst:-1 -msgid "IoT box homepage with HTTPS certificate OK status." -msgstr "" - -#: ../../content/applications/productivity/iot/config/https_certificate_iot.rst:202 -msgid "Domain Name System (DNS) issue" -msgstr "" - -#: ../../content/applications/productivity/iot/config/https_certificate_iot.rst:204 -msgid "If the :abbr:`IoT (Internet of Things)` box can be accessed from its :abbr:`IP (Intrernet Protocol)` address but not the Odoo assigned domain: `.odoo-iot.com`; then the :abbr:`IoT (Internet of Things)` box is likely running into a :abbr:`DNS (Domain Name System)` issue. On some browsers, it will give an error code mentioning :abbr:`DNS (Domain Name System)` (like `DNS_PROBE_FINISHED_NXDOMAIN`)." -msgstr "" - -#: ../../content/applications/productivity/iot/config/https_certificate_iot.rst:209 -msgid "These :abbr:`DNS (Domain Name System)` issues may appear as the following in different browsers:" -msgstr "" - -#: ../../content/applications/productivity/iot/config/https_certificate_iot.rst:213 -msgid "Chrome" -msgstr "" - -#: ../../content/applications/productivity/iot/config/https_certificate_iot.rst:0 -#: ../../content/applications/productivity/iot/config/https_certificate_iot.rst:219 -msgid "DNS issue on Chrome browser on Windows 10." -msgstr "" - -#: ../../content/applications/productivity/iot/config/https_certificate_iot.rst:222 -msgid "Firefox" -msgstr "" - -#: ../../content/applications/productivity/iot/config/https_certificate_iot.rst:0 -#: ../../content/applications/productivity/iot/config/https_certificate_iot.rst:228 -msgid "DNS issue on Firefox browser on Windows 10." -msgstr "" - -#: ../../content/applications/productivity/iot/config/https_certificate_iot.rst:230 -msgid "Edge" -msgstr "" - -#: ../../content/applications/productivity/iot/config/https_certificate_iot.rst:0 -#: ../../content/applications/productivity/iot/config/https_certificate_iot.rst:236 -msgid "DNS issue on Edge browser on Windows 10." -msgstr "" - -#: ../../content/applications/productivity/iot/config/https_certificate_iot.rst:240 -msgid "Domain Name System (DNS) issue solution" -msgstr "" - -#: ../../content/applications/productivity/iot/config/https_certificate_iot.rst:242 -msgid "Should the router allow the :abbr:`DNS (Domain Name System)` to be manually changed, change the DNS to use `Google DNS `_." -msgstr "" - -#: ../../content/applications/productivity/iot/config/https_certificate_iot.rst:244 -msgid "If your router doesn't allow for this, then a change will need to be made on the :abbr:`DNS (Domain Name System)` settings of each of the devices using `Google DNS `_. This will need to occur on **every** device that plans to interact with the :abbr:`IoT (Internet of Things)` box (e.g. computer, tablet or phone). The individual device configuration processes can be found on the website of the device's manufacturer." -msgstr "" - -#: ../../content/applications/productivity/iot/config/https_certificate_iot.rst:252 -msgid "Other :abbr:`IoT (Internet of Things)` devices such as payment terminals likely won't need their :abbr:`DNS (Domain Name System)` settings changed as they are already configured with custom :abbr:`DNS (Domain Name System)`." -msgstr "" - -#: ../../content/applications/productivity/iot/config/https_certificate_iot.rst:257 -msgid "Consult with your system or network administrator should this issue arise. This error code depends on the network infrastructure, and it goes beyond Odoo support's service scope." -msgstr "" - -#: ../../content/applications/productivity/iot/config/pos.rst:3 -msgid "Use an IoT box with a PoS" -msgstr "" - -#: ../../content/applications/productivity/iot/config/pos.rst:6 -msgid "Prerequisites" -msgstr "" - -#: ../../content/applications/productivity/iot/config/pos.rst:8 -msgid "Before starting, make sure the following equipment is available:" -msgstr "" - -#: ../../content/applications/productivity/iot/config/pos.rst:10 -msgid "An :abbr:`IoT (Internet of Things)` box, with its power adapter." -msgstr "" - -#: ../../content/applications/productivity/iot/config/pos.rst:11 -msgid "A computer or tablet with an up-to-date web browser." -msgstr "" - -#: ../../content/applications/productivity/iot/config/pos.rst:12 -msgid "Odoo Online or an Odoo instance with the *Point of Sale* and *IoT* applications installed." -msgstr "" - -#: ../../content/applications/productivity/iot/config/pos.rst:13 -msgid "A local network set up with :abbr:`DHCP (Dynamic Host Configuration Protocol)` (this is the default setting)." -msgstr "" - -#: ../../content/applications/productivity/iot/config/pos.rst:15 -msgid "An RJ45 Ethernet Cable (optional, but preferred over WiFi, which is already built in)." -msgstr "" - -#: ../../content/applications/productivity/iot/config/pos.rst:16 -msgid "Any of the supported hardware (receipt printer, barcode scanner, cash drawer, payment terminal, scale, customer display, etc.). The list of supported hardware can be found on the `POS Hardware page `_." -msgstr "" - -#: ../../content/applications/productivity/iot/config/pos.rst:21 -msgid "Setup" -msgstr "" - -#: ../../content/applications/productivity/iot/config/pos.rst:25 -msgid "A suggested configuration for a point of sale system." -msgstr "" - -#: ../../content/applications/productivity/iot/config/pos.rst:27 -msgid "To connect hardware to the :abbr:`PoS (Point of Sale)`, the first step is to connect an :abbr:`IoT (Internet of Things)` box to the database. To do this, follow these instructions: :doc:`Connect an Internet of Things (IoT) box to the Odoo database `." -msgstr "" - -#: ../../content/applications/productivity/iot/config/pos.rst:31 -msgid "Then, connect the peripheral devices to the :abbr:`IoT (Internet of Things)` box." -msgstr "" - -#: ../../content/applications/productivity/iot/config/pos.rst:37 -msgid "Device Name" -msgstr "" - -#: ../../content/applications/productivity/iot/config/pos.rst:38 -msgid "Instructions" -msgstr "" - -#: ../../content/applications/productivity/iot/config/pos.rst:39 -#: ../../content/applications/productivity/iot/config/troubleshooting.rst:66 -msgid "Printer" -msgstr "" - -#: ../../content/applications/productivity/iot/config/pos.rst:40 -msgid "Connect a supported receipt printer to a :abbr:`USB (Universal Serial Bus)` port or to the network, and power it on. Refer to :doc:`/applications/sales/point_of_sale/restaurant/kitchen_printing`." -msgstr "" - -#: ../../content/applications/productivity/iot/config/pos.rst:43 -#: ../../content/applications/productivity/iot/config/troubleshooting.rst:412 -msgid "Cash drawer" -msgstr "" - -#: ../../content/applications/productivity/iot/config/pos.rst:44 -msgid "The cash drawer should be connected to the printer with an RJ25 cable." -msgstr "" - -#: ../../content/applications/productivity/iot/config/pos.rst:45 -#: ../../content/applications/productivity/iot/config/troubleshooting.rst:360 -msgid "Barcode scanner" -msgstr "" - -#: ../../content/applications/productivity/iot/config/pos.rst:46 -msgid "In order for the barcode scanner to be compatible it must end barcodes with an `ENTER` character (keycode 28). This is most likely the default configuration of the barcode scanner." -msgstr "" - -#: ../../content/applications/productivity/iot/config/pos.rst:48 -msgid "Scale" -msgstr "" - -#: ../../content/applications/productivity/iot/config/pos.rst:49 -msgid "Connect the scale and power it on. Refer to :doc:`/applications/productivity/iot/devices/scale`." -msgstr "" - -#: ../../content/applications/productivity/iot/config/pos.rst:51 -msgid "Customer display" -msgstr "" - -#: ../../content/applications/productivity/iot/config/pos.rst:52 -msgid "Connect a screen to the :abbr:`IoT (Internet of Things)` box to display the :abbr:`PoS (Point of Sale)` order. Refer to :doc:`/applications/productivity/iot/devices/screen`." -msgstr "" - -#: ../../content/applications/productivity/iot/config/pos.rst:54 -msgid "Payment terminal" -msgstr "" - -#: ../../content/applications/productivity/iot/config/pos.rst:55 -msgid "The connection process depends on the terminal. Refer to the :doc:`payment terminals documentation `." -msgstr "" - -#: ../../content/applications/productivity/iot/config/pos.rst:58 -msgid "Once this is completed, connect the :abbr:`IoT (Internet of Things)` box to the :menuselection:`PoS` application. To do this, go to :menuselection:`Point of Sale --> Configuration --> PoS`, tick the :guilabel:`IoT Box` option, and select the devices to be used in this :abbr:`PoS (Point of Sale)`. :guilabel:`Save` the the changes." -msgstr "" - -#: ../../content/applications/productivity/iot/config/pos.rst:-1 -msgid "Configuring the connected devices in the POS application." -msgstr "" - -#: ../../content/applications/productivity/iot/config/pos.rst:67 -msgid "Once set up is done, a new :abbr:`PoS (Point of Sale)` session can be launched." -msgstr "" - -#: ../../content/applications/productivity/iot/config/troubleshooting.rst:3 -#: ../../content/applications/productivity/iot/config/windows_iot.rst:127 -msgid "Troubleshooting" -msgstr "" - -#: ../../content/applications/productivity/iot/config/troubleshooting.rst:6 -msgid "IoT box connection" -msgstr "" - -#: ../../content/applications/productivity/iot/config/troubleshooting.rst:9 -msgid "Unable to locate the pairing code to connect the IoT box" -msgstr "" - -#: ../../content/applications/productivity/iot/config/troubleshooting.rst:11 -msgid "The pairing code should be printed on receipt printers connected to the :abbr:`IoT (Internet of Things)` box and should also be displayed on connected monitors." -msgstr "" - -#: ../../content/applications/productivity/iot/config/troubleshooting.rst:14 -msgid "The pairing code does not show under the following circumstances:" -msgstr "" - -#: ../../content/applications/productivity/iot/config/troubleshooting.rst:16 -msgid "The :abbr:`IoT (Internet of Things)` box is already connected to an Odoo database." -msgstr "" - -#: ../../content/applications/productivity/iot/config/troubleshooting.rst:17 -msgid "The :abbr:`IoT (Internet of Things)` box is not connected to the Internet." -msgstr "" - -#: ../../content/applications/productivity/iot/config/troubleshooting.rst:18 -msgid "The code is only valid for 5 minutes after the :abbr:`IoT (Internet of Things)` box has started. It is automatically removed from connected displays when this time has expired." -msgstr "" - -#: ../../content/applications/productivity/iot/config/troubleshooting.rst:20 -msgid "The version of the :abbr:`IoT (Internet of Things)` box image is too old. If the :abbr:`IoT (Internet of Things)` box image is from an earlier version, then the SD card of the :abbr:`IoT (Internet of Things)` box will need to be re-flashed to update the image (see :doc:`Flashing the SD Card `)." -msgstr "" - -#: ../../content/applications/productivity/iot/config/troubleshooting.rst:25 -msgid "If none of the cases listed above correct the issue, then make sure that the :abbr:`IoT (Internet of Things)` box has correctly started, by checking that a fixed green LED is showing next to the power port." -msgstr "" - -#: ../../content/applications/productivity/iot/config/troubleshooting.rst:30 -msgid "IoT box is connected but it is not showing in the database" -msgstr "" - -#: ../../content/applications/productivity/iot/config/troubleshooting.rst:32 -msgid "When an :abbr:`IoT (Internet of Things)` box connects to a database, it may restart. If so, it can take up to five minutes before appearing in the database. If the :abbr:`IoT (Internet of Things)` box is still not showing after five minutes, make sure that the :abbr:`IoT (Internet of Things)` box can reach the database and that the server does not use a multi-database environment." -msgstr "" - -#: ../../content/applications/productivity/iot/config/troubleshooting.rst:37 -msgid "To access the database from the :abbr:`IoT (Internet of Things)` box, open a browser and type in the database address." -msgstr "" - -#: ../../content/applications/productivity/iot/config/troubleshooting.rst:41 -msgid "The IoT box is connected to the Odoo database, but cannot be reached" -msgstr "" - -#: ../../content/applications/productivity/iot/config/troubleshooting.rst:43 -msgid "Make sure that the :abbr:`IoT (Internet of Things)` box and the computer running the browser are located on the same network, as the :abbr:`IoT (Internet of Things)` box cannot be reached from outside the local network." -msgstr "" - -#: ../../content/applications/productivity/iot/config/troubleshooting.rst:48 -msgid "The HTTPS certificate does not generate" -msgstr "" - -#: ../../content/applications/productivity/iot/config/troubleshooting.rst:50 -msgid "In order to generate a :abbr:`HTTPS (Hypertext Transfer Protocol Secure)` certificate, an IoT box subscription is required for the :abbr:`IoT (Internet of Things)` box. Connecting the :abbr:`IoT (Internet of Things)` box prior to configuring an :abbr:`IoT (Internet of Things)` subscription for the database and :abbr:`IoT (Internet of Things)` box with the Account Manager will result in an unsecured connection." -msgstr "" - -#: ../../content/applications/productivity/iot/config/troubleshooting.rst:56 -msgid "In addition, a firewall can also prevent the :abbr:`HTTPS (Hypertext Transfer Protocol Secure)` certificate from generating correctly. In this case, deactivate the firewall until the certificate is successfully generated. It should also be noted that certain devices, such as a router that has a built-in firewall, can prevent the :abbr:`HTTPS (Hypertext Transfer Protocol Secure)` certificate from generating." -msgstr "" - -#: ../../content/applications/productivity/iot/config/troubleshooting.rst:63 -msgid ":doc:`HTTPS certificate (IoT) `" -msgstr "" - -#: ../../content/applications/productivity/iot/config/troubleshooting.rst:69 -msgid "The printer is not detected" -msgstr "" - -#: ../../content/applications/productivity/iot/config/troubleshooting.rst:71 -msgid "If a printer does not appear in the devices list, go to the :abbr:`IoT (Internet of Things)` box homepage and make sure that it is listed under :guilabel:`Printers`." -msgstr "" - -#: ../../content/applications/productivity/iot/config/troubleshooting.rst:-1 -msgid "The IoT box Home Page landing page." -msgstr "" - -#: ../../content/applications/productivity/iot/config/troubleshooting.rst:78 -msgid "If the printer is not present on the :abbr:`IoT (Internet of Things)` box homepage, click :guilabel:`Printers Server`, go to the :guilabel:`Administration` tab and click on :guilabel:`Add Printer`. If the printer is not present in the list, it is likely not connected properly." -msgstr "" - -#: ../../content/applications/productivity/iot/config/troubleshooting.rst:83 -msgid "The printer outputs random text" -msgstr "" - -#: ../../content/applications/productivity/iot/config/troubleshooting.rst:85 -msgid "For most printers, the correct driver should be automatically detected and selected. However, in some cases, the automatic detection mechanism might not be enough, and if no driver is found, the printer might print random characters." -msgstr "" - -#: ../../content/applications/productivity/iot/config/troubleshooting.rst:89 -msgid "The solution is to manually select the corresponding driver. On the :abbr:`IoT (Internet of Things)` box homepage, click on :guilabel:`Printers Server`, go to the :guilabel:`Printers` tab and select the printer in the list. In the :guilabel:`Administration` drop-down menu, click on :guilabel:`Modify Printer`. Follow the steps and select the *make* and *model* corresponding to the printer." -msgstr "" - -#: ../../content/applications/productivity/iot/config/troubleshooting.rst:-1 -msgid "Edit the printer connected to the IoT box." -msgstr "" - -#: ../../content/applications/productivity/iot/config/troubleshooting.rst:100 -msgid "Epson and Star receipt printers and Zebra label printers do not need a driver to work. Make sure that no driver is selected for those printers." -msgstr "" - -#: ../../content/applications/productivity/iot/config/troubleshooting.rst:104 -msgid "Epson configuration special case" -msgstr "" - -#: ../../content/applications/productivity/iot/config/troubleshooting.rst:106 -msgid "Most Epson printers support printing receipts in Odoo :abbr:`POS (Point of Sale)` using the `GS v 0` command. However, the following Epson printer models do not support this command:" -msgstr "" - -#: ../../content/applications/productivity/iot/config/troubleshooting.rst:109 -msgid "TM-U220" -msgstr "" - -#: ../../content/applications/productivity/iot/config/troubleshooting.rst:110 -msgid "TM-U230" -msgstr "" - -#: ../../content/applications/productivity/iot/config/troubleshooting.rst:111 -msgid "TM-P60" -msgstr "" - -#: ../../content/applications/productivity/iot/config/troubleshooting.rst:112 -msgid "TMP-P60II" -msgstr "" - -#: ../../content/applications/productivity/iot/config/troubleshooting.rst:114 -msgid "Bypass this issue by configuring the printer to use the `ESC *` command instead." -msgstr "" - -#: ../../content/applications/productivity/iot/config/troubleshooting.rst:117 -msgid "Process to force ESC * command" -msgstr "" - -#: ../../content/applications/productivity/iot/config/troubleshooting.rst:120 -msgid "Epson printer compatibility" -msgstr "" - -#: ../../content/applications/productivity/iot/config/troubleshooting.rst:122 -msgid "The first step is to check whether the printer is incompatible with `GS v 0` command." -msgstr "" - -#: ../../content/applications/productivity/iot/config/troubleshooting.rst:126 -msgid "`Epson GS v 0 documentation `_ for `GS v 0` compatible printers." -msgstr "" - -#: ../../content/applications/productivity/iot/config/troubleshooting.rst:128 -msgid "`Epson ESC * documentation `_ for `ESC *` compatible printers." -msgstr "" - -#: ../../content/applications/productivity/iot/config/troubleshooting.rst:131 -msgid "If the printer is not compatible with the `ESC *` command then the following process is not possible. Should the printer be compatible to use the `ESC *` command to print, follow this process to configure the printer with the :abbr:`IoT (Internet of Things)` box." -msgstr "" - -#: ../../content/applications/productivity/iot/config/troubleshooting.rst:136 -msgid "IoT box configuration for ESC *" -msgstr "" - -#: ../../content/applications/productivity/iot/config/troubleshooting.rst:138 -msgid "To configure the :abbr:`IoT (Internet of Things)` box to use the `ESC *` command to print, go to the :abbr:`IoT (Internet of Things)` box homepage by navigating to :menuselection:`IoT app --> IoT Boxes`. Then click on the :guilabel:`IP address` and this will direct to the :abbr:`IoT (Internet of Things)` box homepage." -msgstr "" - -#: ../../content/applications/productivity/iot/config/troubleshooting.rst:143 -msgid "**Choosing the printer**" -msgstr "" - -#: ../../content/applications/productivity/iot/config/troubleshooting.rst:145 -msgid "Now click on the :guilabel:`Printers server` button. This will redirect the browser to the *CUPS* page. Next, go to :menuselection:`Administration --> Printers --> Add Printer`, choose the printer that should be modified, and then click :guilabel:`Continue`." -msgstr "" - -#: ../../content/applications/productivity/iot/config/troubleshooting.rst:150 -msgid "If the name of the printer is still uncertain, take the following steps:" -msgstr "" - -#: ../../content/applications/productivity/iot/config/troubleshooting.rst:152 -msgid "Take note of the listed printers on the *CUPS* page." -msgstr "" - -#: ../../content/applications/productivity/iot/config/troubleshooting.rst:153 -msgid "Turn the printer off and refresh the page." -msgstr "" - -#: ../../content/applications/productivity/iot/config/troubleshooting.rst:154 -msgid "Now compare the difference with the first list to see which printer disappeared." -msgstr "" - -#: ../../content/applications/productivity/iot/config/troubleshooting.rst:155 -msgid "Turn the printer back on and refresh the page again." -msgstr "" - -#: ../../content/applications/productivity/iot/config/troubleshooting.rst:156 -msgid "Double-check the list again to see if the printer re-appears." -msgstr "" - -#: ../../content/applications/productivity/iot/config/troubleshooting.rst:157 -msgid "The printer that disappeared and reappears again on the listed printers is the name of the printer in question." -msgstr "" - -#: ../../content/applications/productivity/iot/config/troubleshooting.rst:161 -msgid "This can be :guilabel:`Unknown` under :guilabel:`Local printers`." -msgstr "" - -#: ../../content/applications/productivity/iot/config/troubleshooting.rst:163 -msgid "**CUPS naming convention**" -msgstr "" - -#: ../../content/applications/productivity/iot/config/troubleshooting.rst:165 -msgid "`CUPS` will prompt the administrator for three pieces of information: the :guilabel:`Name`, :guilabel:`Description` and the :guilabel:`Location`. The last two pieces of information do not need to be specific, however, the :guilabel:`Name` should follow a particular convention to work with the `ESC *` command." -msgstr "" - -#: ../../content/applications/productivity/iot/config/troubleshooting.rst:170 -msgid "The :guilabel:`Name` should match this convention: `__IMC___...___`" -msgstr "" - -#: ../../content/applications/productivity/iot/config/troubleshooting.rst:173 -msgid "A breakdown of the naming convention:" -msgstr "" - -#: ../../content/applications/productivity/iot/config/troubleshooting.rst:175 -msgid "`printer_name`: This is the printer name. It can be any character as long as it does not contain `_`, `/`, `#`, or ` ` (space character)." -msgstr "" - -#: ../../content/applications/productivity/iot/config/troubleshooting.rst:177 -msgid "`IMC`: This stands for *Image Mode Column* (the simplified name for `ESC *`)." -msgstr "" - -#: ../../content/applications/productivity/iot/config/troubleshooting.rst:178 -msgid "`param_1`: This stands for the specific parameter:" -msgstr "" - -#: ../../content/applications/productivity/iot/config/troubleshooting.rst:180 -msgid "`SCALE`: Scale of the picture (with the same aspect ratio). `X` should be an integer describing the scale percentage that should be used." -msgstr "" - -#: ../../content/applications/productivity/iot/config/troubleshooting.rst:184 -msgid "`100` is the original size, `50` is half the size, `200` is twice the size." -msgstr "" - -#: ../../content/applications/productivity/iot/config/troubleshooting.rst:186 -msgid "`LDV`: *Low Density Vertical* (will be set to *High Density Vertical* if not specified)." -msgstr "" - -#: ../../content/applications/productivity/iot/config/troubleshooting.rst:187 -msgid "`LDH`: *Low Density Horizontal* (will be set to *High Density Horizontal* if not specified)." -msgstr "" - -#: ../../content/applications/productivity/iot/config/troubleshooting.rst:190 -msgid "*Density* parameters might need to be configured in a particular way depending on the printer model." -msgstr "" - -#: ../../content/applications/productivity/iot/config/troubleshooting.rst:194 -msgid "Visit `Epson's ESC * documentation `_ and click on the printer model printer in the table above to see if the printer should set these parameters." -msgstr "" - -#: ../../content/applications/productivity/iot/config/troubleshooting.rst:199 -msgid "The following are examples of proper and improper name formatting:" -msgstr "" - -#: ../../content/applications/productivity/iot/config/troubleshooting.rst:201 -msgid "Proper name formatting:" -msgstr "" - -#: ../../content/applications/productivity/iot/config/troubleshooting.rst:203 -msgid "`EPSONTMm30II__IMC__`" -msgstr "" - -#: ../../content/applications/productivity/iot/config/troubleshooting.rst:204 -msgid "`EPSON_TM_U220__IMC_LDV_LDH_SCALE80__`" -msgstr "" - -#: ../../content/applications/productivity/iot/config/troubleshooting.rst:206 -msgid "Improper name formatting (this will not prevent printing, but the result might not have the expected printed output):" -msgstr "" - -#: ../../content/applications/productivity/iot/config/troubleshooting.rst:209 -msgid "`EPSON TMm 30II` -> The name cannot have spaces." -msgstr "" - -#: ../../content/applications/productivity/iot/config/troubleshooting.rst:210 -msgid "`EPSONTMm30II` -> The name itself is correct, but it will not use `ESC *`." -msgstr "" - -#: ../../content/applications/productivity/iot/config/troubleshooting.rst:211 -msgid "`EPSONTMm30II__IMC` -> This name is missing the end `__`." -msgstr "" - -#: ../../content/applications/productivity/iot/config/troubleshooting.rst:212 -msgid "`EPSONTMm30II__IMC_XDV__` -> The parameter `XDV` does not match any existing parameters." -msgstr "" - -#: ../../content/applications/productivity/iot/config/troubleshooting.rst:213 -msgid "`EPSONTMm30II__IMC_SCALE__` -> The parameter `SCALE` is missing the scale value." -msgstr "" - -#: ../../content/applications/productivity/iot/config/troubleshooting.rst:215 -msgid "**Finish adding a printer**" -msgstr "" - -#: ../../content/applications/productivity/iot/config/troubleshooting.rst:217 -msgid "After setting the name of the printer with the appropriate naming convention, click :guilabel:`Continue`. Next, set the :guilabel:`Make` value to :guilabel:`Raw` and for the :guilabel:`Model` value, set this to :guilabel:`Raw Queue (en)`." -msgstr "" - -#: ../../content/applications/productivity/iot/config/troubleshooting.rst:221 -msgid "After completing these steps, click :guilabel:`Add Printer`. If everything was done correctly, the page should redirect to the *Banners* page." -msgstr "" - -#: ../../content/applications/productivity/iot/config/troubleshooting.rst:224 -msgid "At this point the printer should have been created, now the :abbr:`IoT (Internet of Things)` box just needs to detect it and then sync to Odoo's server (this could take a few minutes)." -msgstr "" - -#: ../../content/applications/productivity/iot/config/troubleshooting.rst:227 -msgid "**Adding the printer to Odoo PoS**" -msgstr "" - -#: ../../content/applications/productivity/iot/config/troubleshooting.rst:229 -msgid "Once the printer is visible on the Odoo database, do not forget to choose it in the :abbr:`PoS (Point of Sale)`configuration as the :abbr:`IoT (Internet of Things)` printer. Navigate to :menuselection:`Pos App --> Settings --> Connected Devices --> IoT Box --> Receipt Printer --> Save`." -msgstr "" - -#: ../../content/applications/productivity/iot/config/troubleshooting.rst:235 -msgid "If the printer was set up incorrectly (it is still printing random text or the printed receipt is too big or small), then it cannot be modified via the printer name with *CUPS*. Instead, the above process can be repeated to set up another printer from scratch to create one with modified parameters." -msgstr "" - -#: ../../content/applications/productivity/iot/config/troubleshooting.rst:240 -msgid "**Example setup of the Epson TM-U220B printer using ESC**" -msgstr "" - -#: ../../content/applications/productivity/iot/config/troubleshooting.rst:245 -msgid "The following is an example of the troubleshooting process for a TM-U220B printer model using the `ESC *` command. The receipt pictured below is an example of a receipt that is printing correctly due to proper formatting (in theory):" -msgstr "" - -#: ../../content/applications/productivity/iot/config/troubleshooting.rst:0 -msgid "Properly formatted receipt picture from a demo database." -msgstr "" - -#: ../../content/applications/productivity/iot/config/troubleshooting.rst:253 -msgid "Trying to print this receipt right-away prior to the proper formatting will not work as the TM-U220B printer model does not support `GS v 0`. Instead random characters will print:" -msgstr "" - -#: ../../content/applications/productivity/iot/config/troubleshooting.rst:0 -msgid "Printer paper with seemingly random characters." -msgstr "" - -#: ../../content/applications/productivity/iot/config/troubleshooting.rst:260 -msgid "To properly configure formatting for the Epson TM-U220B printer model take the following steps." -msgstr "" - -#: ../../content/applications/productivity/iot/config/troubleshooting.rst:262 -msgid "After consulting Epson's website for compatibility for both of the commands: `GS v 0 `_ and `ESC * `_, it can be seen that indeed the TM-U220B is not compatible with `GS v 0`, but is compatible with `ESC *`." -msgstr "" - -#: ../../content/applications/productivity/iot/config/troubleshooting.rst:0 -msgid "Epson compatibility evaluation from Epson website." -msgstr "" - -#: ../../content/applications/productivity/iot/config/troubleshooting.rst:271 -msgid "When adding the printer, *CUPS* will ask which printer should be added:" -msgstr "" - -#: ../../content/applications/productivity/iot/config/troubleshooting.rst:0 -msgid "Administration menu, add printer selection." -msgstr "" - -#: ../../content/applications/productivity/iot/config/troubleshooting.rst:277 -msgid "In this case, the printer is connected via :abbr:`USB (Universal Serial Bus)` so it won' be part of the :guilabel:`Discovered Network Printers`. Instead it is likely part of the :guilabel:`Unknown` selection under :guilabel:`Local Printers`. By unplugging the printer's :abbr:`USB (Universal Serial Bus)` cable from the :abbr:`IoT (Internet of Things)` box and refreshing the page, the :guilabel:`Unknown` printer disappears. By plugging it back in, the printer reappears, so it can be said that this is the printer in question." -msgstr "" - -#: ../../content/applications/productivity/iot/config/troubleshooting.rst:284 -msgid "For the naming convention, since it needs to print using the `ESC *` command, it is imperative to add `__IMC`. Reference the printer model on `Epson's ESC * site `_ to find out more about the *density* parameters." -msgstr "" - -#: ../../content/applications/productivity/iot/config/troubleshooting.rst:0 -msgid "Epson TM-U220 specifications on manufacturer's website." -msgstr "" - -#: ../../content/applications/productivity/iot/config/troubleshooting.rst:293 -msgid "For this particular model, TM-U220, `m` should be equal to 0 or 1. While referencing the :guilabel:`Description` below the pink box in the above picture, the `m` values could be 0, 1, 32 or 33. So in this printers case, the `m` value can NOT be 32 or 33 (otherwise there will be random characters printed)." -msgstr "" - -#: ../../content/applications/productivity/iot/config/troubleshooting.rst:298 -msgid "The table includes the numeric values: 32 and 33, they both occur if the :guilabel:`Number of bits for vertical data` is set to 24. This means that is a *High Vertical Density*. In the case of configuring the Epson TM-U220, the *Low Vertical Density* will need to be forced, as this printer model does not support *High Vertical Density* for this command `ESC *`." -msgstr "" - -#: ../../content/applications/productivity/iot/config/troubleshooting.rst:303 -msgid "To add a *Low Vertical Density*, add the `LDV` parameter to the naming convention." -msgstr "" - -#: ../../content/applications/productivity/iot/config/troubleshooting.rst:0 -msgid "Add a *Low Vertical Density* (the `LDV` parameter) to the naming convention." -msgstr "" - -#: ../../content/applications/productivity/iot/config/troubleshooting.rst:309 -msgid "Click :guilabel:`Continue` to proceed. Next, set the :guilabel:`Make` value to :guilabel:`Raw` and for the :guilabel:`Model` value, set this to :guilabel:`Raw Queue (en)`." -msgstr "" - -#: ../../content/applications/productivity/iot/config/troubleshooting.rst:0 -msgid "Epson TM-U220 specifications on manufacturers website." -msgstr "" - -#: ../../content/applications/productivity/iot/config/troubleshooting.rst:316 -msgid "However, when trying to print with the naming convention: `EpsonTMU220B__IMC_LDV__`, it prints the receipt, but it is too big and outside the margin. To resolve this, add a new printer (and naming convention) with the `SCALE` parameter to adapt to our receipt size." -msgstr "" - -#: ../../content/applications/productivity/iot/config/troubleshooting.rst:320 -msgid "Here are some examples:" -msgstr "" - -#: ../../content/applications/productivity/iot/config/troubleshooting.rst:325 -msgid "Printer Naming Convention" -msgstr "" - -#: ../../content/applications/productivity/iot/config/troubleshooting.rst:326 -msgid "`EpsonTMU220B__IMC_LDV__`" -msgstr "" - -#: ../../content/applications/productivity/iot/config/troubleshooting.rst:327 -msgid "`EpsonTMU220B__IMC_LDV_SCALE75__`" -msgstr "" - -#: ../../content/applications/productivity/iot/config/troubleshooting.rst:328 -msgid "`EpsonTMU220B__IMC_LDV_LDH__`" -msgstr "" - -#: ../../content/applications/productivity/iot/config/troubleshooting.rst:329 -msgid "`EpsonTMU220B__IMC_LDV_LDH_SCALE35__`" -msgstr "" - -#: ../../content/applications/productivity/iot/config/troubleshooting.rst:0 -msgid "Receipt example format." -msgstr "" - -#: ../../content/applications/productivity/iot/config/troubleshooting.rst:0 -msgid "Receipt format using naming convention: EpsonTMU220B__IMC_LDV__." -msgstr "" - -#: ../../content/applications/productivity/iot/config/troubleshooting.rst:0 -msgid "Receipt format using naming convention: EpsonTMU220B__IMC_LDV_SCALE75__." -msgstr "" - -#: ../../content/applications/productivity/iot/config/troubleshooting.rst:0 -msgid "Receipt format using naming convention: EpsonTMU220B__IMC_LDV_LDH__." -msgstr "" - -#: ../../content/applications/productivity/iot/config/troubleshooting.rst:0 -msgid "Receipt format using naming convention: EpsonTMU220B__IMC_LDV_LDH_SCALE35__." -msgstr "" - -#: ../../content/applications/productivity/iot/config/troubleshooting.rst:347 -msgid "The Zebra printer does not print anything" -msgstr "" - -#: ../../content/applications/productivity/iot/config/troubleshooting.rst:349 -msgid "Zebra printers are quite sensitive to the format of the Zebra Programming Language (ZPL) code that is printed. If nothing comes out of the printer or blank labels are printed, try changing the format of the report that is sent to the printer by accessing :menuselection:`Settings --> Technical --> User Interface --> Views` in :ref:`developer mode ` and look for the corresponding template." -msgstr "" - -#: ../../content/applications/productivity/iot/config/troubleshooting.rst:356 -msgid "Check out Zebra's instructions on printing :abbr:`ZPL (Zebra Programming Language)` files `here `_." -msgstr "" - -#: ../../content/applications/productivity/iot/config/troubleshooting.rst:363 -msgid "The characters read by the barcode scanner do not match the barcode" -msgstr "" - -#: ../../content/applications/productivity/iot/config/troubleshooting.rst:365 -msgid "By default, most barcode scanners are configured in the US QWERTY format. If the barcode scanner uses a different layout, go to the form view of the device (:menuselection:`IoT App --> Devices --> Barcode Device`) and select the correct format." -msgstr "" - -#: ../../content/applications/productivity/iot/config/troubleshooting.rst:370 -msgid "Nothing happens when a barcode is scanned" -msgstr "" - -#: ../../content/applications/productivity/iot/config/troubleshooting.rst:372 -msgid "Make sure that the correct device is selected in the :menuselection:`Point of Sale` configuration and that the barcode is configured to send an `ENTER` character (keycode 28) at the end of every barcode. To do so, navigate to :menuselection:`PoS app --> 3-Dot Menu on the PoS --> IoT Box section --> Edit`." -msgstr "" - -#: ../../content/applications/productivity/iot/config/troubleshooting.rst:378 -msgid "The barcode scanner is detected as a keyboard" -msgstr "" - -#: ../../content/applications/productivity/iot/config/troubleshooting.rst:381 -msgid "Some barcode scanners do not advertise themselves as barcode scanners but as a USB keyboard instead, and will not be recognized by the :abbr:`IoT (Internet of Things)` box." -msgstr "" - -#: ../../content/applications/productivity/iot/config/troubleshooting.rst:384 -msgid "The device type can be manually changed by going to its form view (:menuselection:`IoT App --> Devices --> Barcode Device`) and activating the :guilabel:`Is scanner` option." -msgstr "" - -#: ../../content/applications/productivity/iot/config/troubleshooting.rst:-1 -msgid "Modifying the form view of the barcode scanner." -msgstr "" - -#: ../../content/applications/productivity/iot/config/troubleshooting.rst:392 -msgid "Barcode scanner processes barcode characters individually" -msgstr "" - -#: ../../content/applications/productivity/iot/config/troubleshooting.rst:394 -msgid "When accessing the mobile version of Odoo from a mobile device, or tablet, paired with a barcode scanner, via the :abbr:`IoT (Internet of Things)` box, the scanner may process each barcode character as an individual scan. In this case, the *Keyboard Layout* option **must** be filled out with the appropriate language of the barcode scanner on the *Barcode Scanner* form page." -msgstr "" - -#: ../../content/applications/productivity/iot/config/troubleshooting.rst:400 -msgid "Access the barcode scanner form page by navigating to :menuselection:`IoT App --> Devices --> Barcode Scanner`." -msgstr "" - -#: ../../content/applications/productivity/iot/config/troubleshooting.rst:-1 -msgid "Barcode scanner form page, with keyboard layout option highlighted." -msgstr "" - -#: ../../content/applications/productivity/iot/config/troubleshooting.rst:407 -msgid "The :guilabel:`Keyboard Layout` is language based, and the options available vary, depending on the device and the language of the database. For example: :guilabel:`English (UK)`, :guilabel:`English (US)`, etc." -msgstr "" - -#: ../../content/applications/productivity/iot/config/troubleshooting.rst:415 -msgid "The cash drawer does not open" -msgstr "" - -#: ../../content/applications/productivity/iot/config/troubleshooting.rst:417 -msgid "The cash drawer should be connected to the printer and the :guilabel:`Cash drawer` checkbox should be ticked in the :abbr:`PoS (Point of Sale)` configuration. To do so, navigate to :menuselection:`POS app --> 3-Dot Menu on the POS --> IoT Box section --> Edit --> Receipt Printer --> Cashdrawer checkbox`." -msgstr "" - -#: ../../content/applications/productivity/iot/config/windows_iot.rst:3 -msgid "Connect Windows IoT Odoo" -msgstr "" - -#: ../../content/applications/productivity/iot/config/windows_iot.rst:5 -msgid "A Virtual IoT box is a computer program that needs to be downloaded and installed on a Windows computer. This requires a Windows operating system with an Odoo 16 or later database." -msgstr "" - -#: ../../content/applications/productivity/iot/config/windows_iot.rst:8 -msgid "The Windows virtual :abbr:`IoT (Internet of Things)` box works the same way as a physical :abbr:`IoT (Internet of Things)` box, with the ability to run most of the same devices. All :abbr:`POS (Point of Sale)` devices work with it, such as a scale or printer. Payment terminals will also work, but it should be noted that :abbr:`MRP (Material Requirement Planning)` devices are not compatible. *These include cameras or measurement tools.*" -msgstr "" - -#: ../../content/applications/productivity/iot/config/windows_iot.rst:15 -msgid "Pre-requisites" -msgstr "" - -#: ../../content/applications/productivity/iot/config/windows_iot.rst:17 -msgid "The following items will be needed to complete the Windows :abbr:`IoT (Internet of Things)` installation." -msgstr "" - -#: ../../content/applications/productivity/iot/config/windows_iot.rst:20 -msgid "Odoo 16 database or any version above." -msgstr "" - -#: ../../content/applications/productivity/iot/config/windows_iot.rst:21 -msgid ":abbr:`IoT (Internet of Things)` compatible devices (except those mentioned above). Refer to: `Odoo's compatible IoT devices `_." -msgstr "" - -#: ../../content/applications/productivity/iot/config/windows_iot.rst:23 -msgid "Device drivers for Windows." -msgstr "" - -#: ../../content/applications/productivity/iot/config/windows_iot.rst:26 -msgid "Odoo recommends using an updated, recent version of Windows (Windows 10/11) as some older operating systems can cause the Windows virtual :abbr:`IoT (Internet of Things)` to not work." -msgstr "" - -#: ../../content/applications/productivity/iot/config/windows_iot.rst:29 -msgid "Windows computer (laptop, desktop, or server)." -msgstr "" - -#: ../../content/applications/productivity/iot/config/windows_iot.rst:30 -msgid "Odoo :abbr:`IoT (Internet of Things)` subscription. Refer to: :ref:`iot/iot-eligibility`." -msgstr "" - -#: ../../content/applications/productivity/iot/config/windows_iot.rst:33 -msgid "Connect the Windows virtual IoT box to an Odoo database" -msgstr "" - -#: ../../content/applications/productivity/iot/config/windows_iot.rst:35 -msgid "The Windows virtual IoT box is simple to setup in just a few easy steps. Follow this process when installing the Windows virtual IoT software for the first time." -msgstr "" - -#: ../../content/applications/productivity/iot/config/windows_iot.rst:39 -msgid "Download and initial installation" -msgstr "" - -#: ../../content/applications/productivity/iot/config/windows_iot.rst:41 -msgid "To begin the installation, navigate to the Odoo 16 or higher installation package for Enterprise or Community - Windows edition at `Odoo's download page `_. Next, install and setup the Odoo :file:`.exe` file. After the instructions screen, click :guilabel:`Next` to start the installation and agree to the :abbr:`TOS (Terms of Service)`." -msgstr "" - -#: ../../content/applications/productivity/iot/config/windows_iot.rst:46 -msgid "During the next step of the installation, select :guilabel:`Odoo IoT` from the :guilabel:`Select the type of install` drop-down menu." -msgstr "" - -#: ../../content/applications/productivity/iot/config/windows_iot.rst:50 -msgid "For reference, the following should be installed:" -msgstr "" - -#: ../../content/applications/productivity/iot/config/windows_iot.rst:52 -msgid "**Odoo server**" -msgstr "" - -#: ../../content/applications/productivity/iot/config/windows_iot.rst:53 -msgid "**Odoo IoT**" -msgstr "" - -#: ../../content/applications/productivity/iot/config/windows_iot.rst:54 -msgid "**Nginx WebServer**" -msgstr "" - -#: ../../content/applications/productivity/iot/config/windows_iot.rst:55 -msgid "**Ghostscript interpreter**" -msgstr "" - -#: ../../content/applications/productivity/iot/config/windows_iot.rst:57 -msgid "Ensure there is enough space on the computer for the installation and click :guilabel:`Next`." -msgstr "" - -#: ../../content/applications/productivity/iot/config/windows_iot.rst:60 -msgid "Setting the destination and completing the installation" -msgstr "" - -#: ../../content/applications/productivity/iot/config/windows_iot.rst:62 -msgid "To complete the installation, select the :guilabel:`Destination Folder` and click :guilabel:`Install`." -msgstr "" - -#: ../../content/applications/productivity/iot/config/windows_iot.rst:66 -msgid "Choosing ``C:\\odoo`` as the install location will allow for the Nginx server to start. If the folder doesn't exist, then create it. Otherwise the installation files will be spread throughout the hard drive." -msgstr "" - -#: ../../content/applications/productivity/iot/config/windows_iot.rst:71 -msgid "Odoo's Windows virtual IoT software should not be installed inside any of the Window's User's directories. Doing so will not allow for Nginx to initialize." -msgstr "" - -#: ../../content/applications/productivity/iot/config/windows_iot.rst:74 -msgid "The installation may take a few minutes. When complete, click :guilabel:`Next` to continue." -msgstr "" - -#: ../../content/applications/productivity/iot/config/windows_iot.rst:76 -msgid "Ensure that the :guilabel:`Start Odoo` box is checked and click :guilabel:`Finish`. After installation, the Odoo server will run and automatically open `http://localhost:8069` on a web browser. The webpage should display the :abbr:`IoT (Internet of Things)` box homepage." -msgstr "" - -#: ../../content/applications/productivity/iot/config/windows_iot.rst:81 -msgid "A restart of the Windows IoT program may be necessary should the web browser not display anything. :ref:`iot/restart_windows_iot`" -msgstr "" - -#: ../../content/applications/productivity/iot/config/windows_iot.rst:85 -msgid "Connecting devices" -msgstr "" - -#: ../../content/applications/productivity/iot/config/windows_iot.rst:87 -msgid "Next, connect the :abbr:`IoT (Internet of Things)` devices to the Windows computer. Windows should automatically detect the device because the driver is pre-installed on the computer. If not, search for and install the Windows driver for the device." -msgstr "" - -#: ../../content/applications/productivity/iot/config/windows_iot.rst:92 -msgid "Most devices connect to the Windows Machine for Windows IoT automatically through Windows Plug-N-Play (PnP). However, if Windows does not automatically recognize the device after connecting, then the administrator may need to install the corresponding drivers manually." -msgstr "" - -#: ../../content/applications/productivity/iot/config/windows_iot.rst:96 -msgid "Devices automatically recognized:" -msgstr "" - -#: ../../content/applications/productivity/iot/config/windows_iot.rst:98 -msgid "Regular ink/toner based printers" -msgstr "" - -#: ../../content/applications/productivity/iot/config/windows_iot.rst:99 -msgid "Receipt printers (Epson/Star)" -msgstr "" - -#: ../../content/applications/productivity/iot/config/windows_iot.rst:100 -msgid "Barcode scanners" -msgstr "" - -#: ../../content/applications/productivity/iot/config/windows_iot.rst:101 -msgid "Measurement devices (although some configuration of the measurement device settings is required) See this documentation: :doc:`../devices/measurement_tool`" -msgstr "" - -#: ../../content/applications/productivity/iot/config/windows_iot.rst:104 -msgid "Devices not automatically recognized (requires manual driver download):" -msgstr "" - -#: ../../content/applications/productivity/iot/config/windows_iot.rst:106 -msgid "Label printers (Zebra)" -msgstr "" - -#: ../../content/applications/productivity/iot/config/windows_iot.rst:107 -msgid "Scales" -msgstr "" - -#: ../../content/applications/productivity/iot/config/windows_iot.rst:109 -msgid "Reference the manufacturer's website for the equipment in question. Then, download the drivers and install them on the Windows machine. Reconnect the device in question and Windows will find the device." -msgstr "" - -#: ../../content/applications/productivity/iot/config/windows_iot.rst:113 -msgid "Following connecting devices to the computer, refresh the :abbr:`IoT (Internet of Things)` box homepage and verify the device is seen. If not, reload the handlers through the :abbr:`IoT (Internet of Things)` box homepage." -msgstr "" - -#: ../../content/applications/productivity/iot/config/windows_iot.rst:117 -msgid "Finally, connect Windows :abbr:`IoT (Internet of Things)` to a database using existing instructions (manually using the Token)." -msgstr "" - -#: ../../content/applications/productivity/iot/config/windows_iot.rst:123 -msgid "Now the installation is complete, the devices connected to :abbr:`IoT (Internet of Things)` can be used to complete processes/actions." -msgstr "" - -#: ../../content/applications/productivity/iot/config/windows_iot.rst:132 -msgid "Restart Windows IoT box" -msgstr "" - -#: ../../content/applications/productivity/iot/config/windows_iot.rst:134 -msgid "In some instances a manual restart of the physical :abbr:`IoT (Internet of Things)` box can resolve the issue of an :abbr:`IoT (Internet of Things)` box not showing up on the database. For the Windows virtual :abbr:`IoT (Internet of Things)` box a manual restart of the Odoo server can resolve database connection issues." -msgstr "" - -#: ../../content/applications/productivity/iot/config/windows_iot.rst:139 -msgid "To restart the virtual Windows IoT server:" -msgstr "" - -#: ../../content/applications/productivity/iot/config/windows_iot.rst:141 -msgid "Type `Services` into the Windows :guilabel:`Search Bar`." -msgstr "" - -#: ../../content/applications/productivity/iot/config/windows_iot.rst:142 -msgid "Select the :menuselection:`Services` App and scroll down to the :guilabel:`Odoo` service." -msgstr "" - -#: ../../content/applications/productivity/iot/config/windows_iot.rst:143 -msgid "Right click on :guilabel:`Odoo` and select :guilabel:`Start` or :guilabel:`Restart`. This action will manually restart the Odoo IoT server." -msgstr "" - -#: ../../content/applications/productivity/iot/config/windows_iot.rst:147 -msgid "Firewalls" -msgstr "" - -#: ../../content/applications/productivity/iot/config/windows_iot.rst:149 -msgid "Firewalls keep devices safe and secure. Sometimes they can block connections that should be made though. The Windows virtual :abbr:`IoT (Internet of Things)` box software may not be reachable to the :abbr:`LAN (Local Area Network)` due to a firewall preventing the connection. Consult your local IT support team to make exceptions (network discovery) in the :abbr:`OS (Operating System)` or firewall program. Windows has their own firewall as do other virus protection programs." -msgstr "" - -#: ../../content/applications/productivity/iot/config/windows_iot.rst:156 -msgid "A client might encounter a time when they are able to reach the homepage of the :abbr:`IoT (Internet of Things)` box, yet they cannot access it from another computer/mobile device/tablet on the same network." -msgstr "" - -#: ../../content/applications/productivity/iot/config/windows_iot.rst:161 -msgid "Making an exception on Windows Defender" -msgstr "" - -#: ../../content/applications/productivity/iot/config/windows_iot.rst:163 -msgid "It is possible to allow other devices to access the Windows virtual :abbr:`IoT (Internet of Things)` box while keeping the firewall on. This is done by creating a rule on *Windows Defender* and allowing communication through port `8069`. The following process describes the steps to take in order to make this exception." -msgstr "" - -#: ../../content/applications/productivity/iot/config/windows_iot.rst:169 -msgid "Create a rule in Windows Defender" -msgstr "" - -#: ../../content/applications/productivity/iot/config/windows_iot.rst:171 -msgid "First, open the *Windows Firewall* by navigating to the :menuselection:`Start Menu` and typing in `Firewall`. Then, open the :menuselection:`Windows Defender Firewall` program. In the left-hand menu, navigate to :guilabel:`Advanced Settings`." -msgstr "" - -#: ../../content/applications/productivity/iot/config/windows_iot.rst:175 -msgid "Once :guilabel:`Advanced Settings` have been selected, click :guilabel:`Inbound Rules` in the left-hand menu. Then, in the right-hand menu column (under :guilabel:`Inbound Rules`), click on :guilabel:`New Rule` to create a new rule." -msgstr "" - -#: ../../content/applications/productivity/iot/config/windows_iot.rst:180 -msgid "Configure new rule" -msgstr "" - -#: ../../content/applications/productivity/iot/config/windows_iot.rst:182 -msgid "On the :menuselection:`Rule Type` screen, select :guilabel:`Port`. Then click :guilabel:`Next`. From the :menuselection:`Protocol and Ports` page leave the rule application to :guilabel:`TCP`. Then, select :guilabel:`Specific Local Ports` for the :guilabel:`ports` option. In the text box, type in `8069`. Finally click :guilabel:`Next` to continue to the next step." -msgstr "" - -#: ../../content/applications/productivity/iot/config/windows_iot.rst:187 -msgid "On the :menuselection:`Actions` page, select :guilabel:`Allow the connection` and click :guilabel:`Next`. The following page on the :menuselection:`Rule Configuration` wizard is the :guilabel:`Profile` page. On this page, select whichever connection type applies to the network the Windows machine is operating on. Ideally, select :guilabel:`Private` only connections. The *Private* connection type is the most secure connection while allowing the selected port to communicate. Click :guilabel:`Next` to continue." -msgstr "" - -#: ../../content/applications/productivity/iot/config/windows_iot.rst:194 -msgid "Finally, assign a new, unique name to the rule. For example, this name can be `Odoo`. Optionally, add a brief description in the :guilabel:`Description` field. Click :guilabel:`Finish` to complete the :guilabel:`Rule Configuration` wizard. Now, the new rule is active and devices can connect to the Windows virtual :abbr:`IoT (Internet of Things)` box." -msgstr "" - -#: ../../content/applications/productivity/iot/config/windows_iot.rst:200 -msgid "Worldline exception" -msgstr "" - -#: ../../content/applications/productivity/iot/config/windows_iot.rst:202 -msgid "*Worldline* is a payment terminal that can be connected to Odoo's *PoS* (point of sale) system. It allows for a comprehensive and fluid payment experience for customers. Worldline is available in Benelux (coalition of Belgium, the Netherlands, and Luxembourg)." -msgstr "" - -#: ../../content/applications/productivity/iot/config/windows_iot.rst:206 -msgid "When using the Windows IoT server to connect the Worldline payment terminal, it is necessary to create an exception in the Windows firewall so that a connection can be made between the Odoo database/:abbr:`IoT (Internet of Things)` box and Worldline." -msgstr "" - -#: ../../content/applications/productivity/iot/config/windows_iot.rst:211 -msgid ":doc:`../../../sales/point_of_sale/payment_methods/terminals/worldline`" -msgstr "" - -#: ../../content/applications/productivity/iot/config/windows_iot.rst:213 -msgid "To create the exception, first, open the *Windows Defender Firewall* app on the Windows machine. This can be accomplished by typing `windows defender` in the :guilabel:`Search` bar." -msgstr "" - -#: ../../content/applications/productivity/iot/config/windows_iot.rst:216 -msgid "Next, click :guilabel:`Advanced settings` in the left menu." -msgstr "" - -#: ../../content/applications/productivity/iot/config/windows_iot.rst:-1 -msgid "Advanced settings option highlighted in the left pane of the Windows Defender Firewall app." -msgstr "" - -#: ../../content/applications/productivity/iot/config/windows_iot.rst:222 -msgid "In the left menu, choose :guilabel:`Inbound Rules`." -msgstr "" - -#: ../../content/applications/productivity/iot/config/windows_iot.rst:-1 -msgid "Windows Defender left window pane with inbound rules menu item highlighted." -msgstr "" - -#: ../../content/applications/productivity/iot/config/windows_iot.rst:228 -msgid "After selecting :guilabel:`Inbound Rules`, select :guilabel:`New Rule` in the far right menu." -msgstr "" - -#: ../../content/applications/productivity/iot/config/windows_iot.rst:-1 -msgid "New rule dropdown shown with new rule option highlighted." -msgstr "" - -#: ../../content/applications/productivity/iot/config/windows_iot.rst:234 -msgid "Then, for the :guilabel:`Rule Type`, select the radio button for :guilabel:`Port`. Click :guilabel:`Next` to continue to the rest of the configuration." -msgstr "" - -#: ../../content/applications/productivity/iot/config/windows_iot.rst:-1 -msgid "Rule Type window open, with the radio button next to port highlighted." -msgstr "" - -#: ../../content/applications/productivity/iot/config/windows_iot.rst:241 -msgid "On the :guilabel:`Protocols and Ports` page, choose the radio button for :guilabel:`TCP`, under :guilabel:`Does this rule apply to TCP or UDP?`." -msgstr "" - -#: ../../content/applications/productivity/iot/config/windows_iot.rst:244 -msgid "Next, under :guilabel:`Does this rule apply to all local ports or specific ports?`, select the radio button for :guilabel:`Specific local ports`. Then, enter `9050`, and click :guilabel:`Next` to continue." -msgstr "" - -#: ../../content/applications/productivity/iot/config/windows_iot.rst:-1 -msgid "Protocol/port configuration window with TCP, specific port (9050) and Next highlighted." -msgstr "" - -#: ../../content/applications/productivity/iot/config/windows_iot.rst:252 -msgid "The next screen is the :guilabel:`Action` page. Under :guilabel:`What action should be taken when a connection matches the specified conditions?`, choose the radio button for :guilabel:`Allow the connection`. Then, click :guilabel:`Next` to continue." -msgstr "" - -#: ../../content/applications/productivity/iot/config/windows_iot.rst:256 -msgid "A :guilabel:`Profile` page appears. Under :guilabel:`When does this rule apply?`, leave the three boxes checked for: :guilabel:`Domain`, :guilabel:`Private`, and :guilabel:`Public`. Click :guilabel:`Next` to continue to the naming convention page." -msgstr "" - -#: ../../content/applications/productivity/iot/config/windows_iot.rst:260 -msgid "On the :guilabel:`Name` page, enter `Odoo Worldline`, under the :guilabel:`Name` field. Enter a :guilabel:`Description (optional)`. Finally, once ready, click :guilabel:`Finish`." -msgstr "" - -#: ../../content/applications/productivity/iot/config/windows_iot.rst:263 -msgid "The final :guilabel:`Inbound rule` should appear as follows:" -msgstr "" - -#: ../../content/applications/productivity/iot/config/windows_iot.rst:270 -msgid "Odoo Worldline" -msgstr "" - -#: ../../content/applications/productivity/iot/config/windows_iot.rst:271 -msgid "Profile" -msgstr "" - -#: ../../content/applications/productivity/iot/config/windows_iot.rst:272 -msgid "All" -msgstr "" - -#: ../../content/applications/productivity/iot/config/windows_iot.rst:273 -msgid "Enabled" -msgstr "" - -#: ../../content/applications/productivity/iot/config/windows_iot.rst:274 -msgid "Yes" -msgstr "" - -#: ../../content/applications/productivity/iot/config/windows_iot.rst:276 -msgid "Allow" -msgstr "" - -#: ../../content/applications/productivity/iot/config/windows_iot.rst:277 -msgid "Override" -msgstr "" - -#: ../../content/applications/productivity/iot/config/windows_iot.rst:278 -msgid "No" -msgstr "" - -#: ../../content/applications/productivity/iot/config/windows_iot.rst:279 -msgid "Program" -msgstr "" - -#: ../../content/applications/productivity/iot/config/windows_iot.rst:280 -#: ../../content/applications/productivity/iot/config/windows_iot.rst:282 -#: ../../content/applications/productivity/iot/config/windows_iot.rst:284 -#: ../../content/applications/productivity/iot/config/windows_iot.rst:290 -#: ../../content/applications/productivity/iot/config/windows_iot.rst:292 -#: ../../content/applications/productivity/iot/config/windows_iot.rst:294 -#: ../../content/applications/productivity/iot/config/windows_iot.rst:296 -#: ../../content/applications/productivity/iot/config/windows_iot.rst:298 -#: ../../content/applications/productivity/iot/config/windows_iot.rst:302 -msgid "Any" -msgstr "" - -#: ../../content/applications/productivity/iot/config/windows_iot.rst:281 -msgid "Local Address" -msgstr "" - -#: ../../content/applications/productivity/iot/config/windows_iot.rst:283 -msgid "Remote Address" -msgstr "" - -#: ../../content/applications/productivity/iot/config/windows_iot.rst:285 -msgid "Protocol" -msgstr "" - -#: ../../content/applications/productivity/iot/config/windows_iot.rst:286 -msgid "TCP" -msgstr "" - -#: ../../content/applications/productivity/iot/config/windows_iot.rst:287 -msgid "Local Port" -msgstr "" - -#: ../../content/applications/productivity/iot/config/windows_iot.rst:288 -msgid "9050" -msgstr "" - -#: ../../content/applications/productivity/iot/config/windows_iot.rst:289 -msgid "Remote Port" -msgstr "" - -#: ../../content/applications/productivity/iot/config/windows_iot.rst:291 -msgid "Authorized Users" -msgstr "" - -#: ../../content/applications/productivity/iot/config/windows_iot.rst:293 -msgid "Authorized Computers" -msgstr "" - -#: ../../content/applications/productivity/iot/config/windows_iot.rst:295 -msgid "Authorized Local Principals" -msgstr "" - -#: ../../content/applications/productivity/iot/config/windows_iot.rst:297 -msgid "Local User Owner" -msgstr "" - -#: ../../content/applications/productivity/iot/config/windows_iot.rst:299 -msgid "PolicyAppld" -msgstr "" - -#: ../../content/applications/productivity/iot/config/windows_iot.rst:300 -msgid "None" -msgstr "" - -#: ../../content/applications/productivity/iot/config/windows_iot.rst:301 -msgid "Application Package" -msgstr "" - -#: ../../content/applications/productivity/iot/config/windows_iot.rst:305 -msgid "Uninstalling Windows IoT" -msgstr "" - -#: ../../content/applications/productivity/iot/config/windows_iot.rst:307 -msgid "Uninstalling the Windows virtual :abbr:`IoT (Internet of Things)` box is done through the Windows program manager. Using any Windows version, search for `program`. Then, select :guilabel:`Add or Remove Programs` located in the control panel. Search for `Odoo` and click the :guilabel:`three dot menu` to uninstall." -msgstr "" - -#: ../../content/applications/productivity/iot/config/windows_iot.rst:312 -msgid "Confirm the un-installation and follow the steps to uninstall through the Odoo uninstall guide." -msgstr "" - -#: ../../content/applications/productivity/iot/devices.rst:5 -msgid "Devices" -msgstr "" - -#: ../../content/applications/productivity/iot/devices/camera.rst:3 -msgid "Connect a camera" -msgstr "" - -#: ../../content/applications/productivity/iot/devices/camera.rst:5 -msgid "A camera can be connected to an :abbr:`IoT (Internet of Things)` box with an Odoo database in just a few steps. Once a camera is connected to an :abbr:`IoT (Internet of Things)` box, it can be used in a manufacturing process, or it can be linked to a quality control point/quality check. Doing so allows for the taking of pictures when a chosen quality control point/check has been reached, or when a specific key is pressed during manufacturing." -msgstr "" - -#: ../../content/applications/productivity/iot/devices/camera.rst:12 -#: ../../content/applications/productivity/iot/devices/footswitch.rst:14 -#: ../../content/applications/productivity/iot/devices/printer.rst:11 -#: ../../content/applications/productivity/iot/devices/scale.rst:10 -#: ../../content/applications/productivity/iot/devices/screen.rst:18 -msgid "Connection" -msgstr "" - -#: ../../content/applications/productivity/iot/devices/camera.rst:14 -msgid "To connect a camera to an :abbr:`IoT (Internet of Things)` box, simply connect the two via cable. This is usually done with a :abbr:`USB (Universal Serial Bus)` cable of some sort." -msgstr "" - -#: ../../content/applications/productivity/iot/devices/camera.rst:17 -msgid "If the camera is `supported `_, there is no need to set up anything, as it'll be detected as soon as it's connected." -msgstr "" - -#: ../../content/applications/productivity/iot/devices/camera.rst:-1 -msgid "Camera recognized on the IoT box." -msgstr "" - -#: ../../content/applications/productivity/iot/devices/camera.rst:25 -msgid "Link camera to quality control point in manufacturing process" -msgstr "" - -#: ../../content/applications/productivity/iot/devices/camera.rst:27 -msgid "In the :menuselection:`Quality app`, a device can be set up on a :guilabel:`Quality Control Point`. To do that, navigate to the :menuselection:`Quality app --> Quality Control --> Control Points` and open the desired :guilabel:`Control Point` that'll be linked to the camera." -msgstr "" - -#: ../../content/applications/productivity/iot/devices/camera.rst:31 -msgid "On the control point form, edit the control point by selecting the :guilabel:`Type` field, and clicking on :guilabel:`Take a Picture` from the drop-down menu. Doing so reveals a field called :guilabel:`Device`, wherein the attached *device* can be selected. :guilabel:`Save` the changes, if required." -msgstr "" - -#: ../../content/applications/productivity/iot/devices/camera.rst:-1 -msgid "Setting up the device on the quality control point." -msgstr "" - -#: ../../content/applications/productivity/iot/devices/camera.rst:40 -msgid "The camera is now useable with the selected quality control point. When the quality control point is reached during the manufacturing process, the database prompts the operator to take a picture." -msgstr "" - -#: ../../content/applications/productivity/iot/devices/camera.rst:-1 -msgid "Graphic user interface of the device on the quality control point." -msgstr "" - -#: ../../content/applications/productivity/iot/devices/camera.rst:48 -msgid "Quality control points can also be accessed by navigating to :menuselection:`IoT App --> Devices`. From here, select the device. There is a :guilabel:`Quality Control Points` tab, where they can be added with the device." -msgstr "" - -#: ../../content/applications/productivity/iot/devices/camera.rst:53 -msgid "On a quality check form, the :guilabel:`Type` of check can also be specified to :guilabel:`Take a Picture`. Navigate to :menuselection:`Quality app --> Quality Control --> Quality Checks --> New` to create a new quality check from the :guilabel:`Quality Checks` page." -msgstr "" - -#: ../../content/applications/productivity/iot/devices/camera.rst:58 -#: ../../content/applications/productivity/iot/devices/printer.rst:70 -msgid ":doc:`/applications/inventory_and_mrp/quality/quality_management/quality_control_points`" -msgstr "" - -#: ../../content/applications/productivity/iot/devices/camera.rst:59 -#: ../../content/applications/productivity/iot/devices/printer.rst:71 -msgid ":doc:`/applications/inventory_and_mrp/quality/quality_management/quality_alerts`" -msgstr "" - -#: ../../content/applications/productivity/iot/devices/camera.rst:62 -msgid "Link camera to a work center in the Manufacturing app" -msgstr "" - -#: ../../content/applications/productivity/iot/devices/camera.rst:64 -msgid "To link a camera to an action, it first needs to be configured on a work center. Navigate to :menuselection:`Manufacturing app --> Configuration --> Work Centers`. Next, go to the desired :guilabel:`Work Center` in which a camera will be used to reveal that specific work center's detail form. From here, add the device in the :guilabel:`IoT Triggers` tab, in the :guilabel:`Device` column, by clicking :guilabel:`Add a Line`." -msgstr "" - -#: ../../content/applications/productivity/iot/devices/camera.rst:70 -msgid "Now, the camera device can be linked to the :guilabel:`Action` column drop-down option labeled :guilabel:`Take a Picture`. A key can also be added to trigger the action." -msgstr "" - -#: ../../content/applications/productivity/iot/devices/camera.rst:74 -msgid "The first trigger listed is chosen first. The order of triggers matters, and they can be dragged into any desired order." -msgstr "" - -#: ../../content/applications/productivity/iot/devices/camera.rst:78 -msgid "On the :guilabel:`Work Order` screen, a status graphic indicates whether the database is correctly connected to the camera." -msgstr "" - -#: ../../content/applications/productivity/iot/devices/camera.rst:82 -#: ../../content/applications/productivity/iot/devices/footswitch.rst:52 -#: ../../content/applications/productivity/iot/devices/measurement_tool.rst:92 -#: ../../content/applications/productivity/iot/devices/printer.rst:95 -msgid ":ref:`workcenter_iot`" -msgstr "" - -#: ../../content/applications/productivity/iot/devices/footswitch.rst:3 -msgid "Connect a footswitch" -msgstr "" - -#: ../../content/applications/productivity/iot/devices/footswitch.rst:5 -msgid "When working in a manufacturing environment, it's always better for an operator to have both hands available at all times. Odoo's :abbr:`IoT (Internet of Things)` box makes this possible when using a footswitch." -msgstr "" - -#: ../../content/applications/productivity/iot/devices/footswitch.rst:9 -msgid "In fact, with a footswitch, the operator is able to go from one screen to another, and perform actions using their foot. This can be configured in just a few steps on the work center in the *Manufacturing* app." -msgstr "" - -#: ../../content/applications/productivity/iot/devices/footswitch.rst:16 -msgid "To connect a footswitch to the :abbr:`IoT (Internet of Things)` box, connect the two devices via cable. More often than not, this is done with a :abbr:`USB (Universal Serial Bus)` cable." -msgstr "" - -#: ../../content/applications/productivity/iot/devices/footswitch.rst:19 -msgid "If the footswitch is a `supported device `_, there is no need to take further action, since it'll be automatically detected when connected." -msgstr "" - -#: ../../content/applications/productivity/iot/devices/footswitch.rst:-1 -msgid "Footswitch recognized on the IoT box." -msgstr "" - -#: ../../content/applications/productivity/iot/devices/footswitch.rst:27 -msgid "Link a footswitch to a work center in the Odoo Manufacturing app" -msgstr "" - -#: ../../content/applications/productivity/iot/devices/footswitch.rst:29 -msgid "To link a footswitch to an action, it first needs to be configured on a work center. Navigate to :menuselection:`Manufacturing app --> Configuration --> Work Centers`. From here, go to the desired :guilabel:`Work Center` in which the footswitch will be used, and add the device in the :guilabel:`IoT Triggers` tab, under the :guilabel:`Device` column, by selecting :guilabel:`Add a Line`. Doing so means the footswitch can be linked to an option in the :guilabel:`Action` column drop-down, and optionally, a key can be added to trigger it. An example of an :guilabel:`Action` in the *Manufacturing app* could be the :guilabel:`Validate` or :guilabel:`Mark as Done` buttons on a manufacturing work order." -msgstr "" - -#: ../../content/applications/productivity/iot/devices/footswitch.rst:-1 -msgid "Footswitch trigger setup on the Odoo database." -msgstr "" - -#: ../../content/applications/productivity/iot/devices/footswitch.rst:43 -msgid "It should be noted that the first listed trigger is chosen first. So, the order matters, and these triggers can be dragged into any order. In the picture above, using the footswitch automatically skips the part of the process that's currently being worked on." -msgstr "" - -#: ../../content/applications/productivity/iot/devices/footswitch.rst:48 -msgid "On the :guilabel:`Work Order` screen, a status graphic indicates whether the database is correctly connected to the footswitch." -msgstr "" - -#: ../../content/applications/productivity/iot/devices/measurement_tool.rst:3 -msgid "Connect a measurement tool" -msgstr "" - -#: ../../content/applications/productivity/iot/devices/measurement_tool.rst:7 -msgid "With Odoo's :abbr:`IoT (Internet of Things)` box, it is possible to connect measurement tools to the Odoo database for use in the *Quality app* on a quality control point/quality check, or for use in a work center during the manufacturing process." -msgstr "" - -#: ../../content/applications/productivity/iot/devices/measurement_tool.rst:11 -msgid "Find the list of supported devices here: `Supported devices `_." -msgstr "" - -#: ../../content/applications/productivity/iot/devices/measurement_tool.rst:15 -msgid "Connect with universal serial bus (USB)" -msgstr "" - -#: ../../content/applications/productivity/iot/devices/measurement_tool.rst:17 -msgid "To add a device connected by :abbr:`USB (Universal Serial Bus)`, plug the :abbr:`USB (Universal Serial Bus)` cable into the :abbr:`IoT (Internet of Things)` box, and the device appears in the Odoo database." -msgstr "" - -#: ../../content/applications/productivity/iot/devices/measurement_tool.rst:-1 -msgid "Measurement tool recognized on the IoT box." -msgstr "" - -#: ../../content/applications/productivity/iot/devices/measurement_tool.rst:26 -msgid "Connect with bluetooth" -msgstr "" - -#: ../../content/applications/productivity/iot/devices/measurement_tool.rst:28 -msgid "Activate the Bluetooth functionality on the device (see the device manual for further explanation), and the :abbr:`IoT (Internet of Things)` box automatically connects to the device." -msgstr "" - -#: ../../content/applications/productivity/iot/devices/measurement_tool.rst:-1 -msgid "Bluetooth indicator on measurement tool." -msgstr "" - -#: ../../content/applications/productivity/iot/devices/measurement_tool.rst:37 -msgid "Link a measurement tool to a quality control point in the manufacturing process" -msgstr "" - -#: ../../content/applications/productivity/iot/devices/measurement_tool.rst:39 -msgid "In the *Quality app*, a device can be set up on a quality control point. To do that, navigate to :menuselection:`Quality app --> Quality Control --> Control Points`, and open the desired control point to which the measurement tool should be linked." -msgstr "" - -#: ../../content/applications/productivity/iot/devices/measurement_tool.rst:43 -msgid "From here, edit the control point, by selecting the :guilabel:`Type` field, and clicking :guilabel:`Measure` from the drop-down menu. Doing so reveals a field called :guilabel:`Device`, where the attached device can be selected." -msgstr "" - -#: ../../content/applications/productivity/iot/devices/measurement_tool.rst:47 -msgid "Additionally, :guilabel:`Norm` and :guilabel:`Tolerance` can be configured. :guilabel:`Save` the changes, if required." -msgstr "" - -#: ../../content/applications/productivity/iot/devices/measurement_tool.rst:50 -msgid "At this point, the measurement tool is linked to the chosen quality control point. The value, which usually needs to be changed manually, is automatically updated while the tool is being used." -msgstr "" - -#: ../../content/applications/productivity/iot/devices/measurement_tool.rst:-1 -msgid "Measurement tool input in the Odoo database." -msgstr "" - -#: ../../content/applications/productivity/iot/devices/measurement_tool.rst:58 -#: ../../content/applications/productivity/iot/devices/printer.rst:60 -msgid "Quality control points can also be accessed by navigating to :menuselection:`IoT App --> Devices`, then select the device. There is a :guilabel:`Quality Control Points` tab, where they can be added with the device." -msgstr "" - -#: ../../content/applications/productivity/iot/devices/measurement_tool.rst:63 -msgid "On a quality check detail form, the :guilabel:`Type` of check can also be specified to :guilabel:`Measure`. Access a new quality check detail page, by navigating to :menuselection:`Quality app --> Quality Control --> Quality Checks --> New`." -msgstr "" - -#: ../../content/applications/productivity/iot/devices/measurement_tool.rst:68 -msgid ":doc:`../../../inventory_and_mrp/quality/quality_management/quality_control_points`" -msgstr "" - -#: ../../content/applications/productivity/iot/devices/measurement_tool.rst:69 -msgid ":doc:`../../../inventory_and_mrp/quality/quality_management/quality_alerts`" -msgstr "" - -#: ../../content/applications/productivity/iot/devices/measurement_tool.rst:72 -msgid "Link a measurement tool to a work center in the Manufacturing app" -msgstr "" - -#: ../../content/applications/productivity/iot/devices/measurement_tool.rst:74 -msgid "To link a measurement tool to an action, it first needs to be configured on a work center. To do that, navigate to :menuselection:`Manufacturing app --> Configuration --> Work Centers`. Then, select the desired work center in which the measurement tool will be used." -msgstr "" - -#: ../../content/applications/productivity/iot/devices/measurement_tool.rst:78 -msgid "On the work center page, add the device in the :guilabel:`IoT Triggers` tab, under the :guilabel:`Device` column, by selecting :guilabel:`Add a Line`. Then, the measurement tool can be linked to the :guilabel:`Action` drop-down menu option labeled :guilabel:`Take Measure`. A key can be added to trigger the action." -msgstr "" - -#: ../../content/applications/productivity/iot/devices/measurement_tool.rst:84 -msgid "It should be noted that the first listed trigger is chosen first. The order matters, and these triggers can be dragged into any order." -msgstr "" - -#: ../../content/applications/productivity/iot/devices/measurement_tool.rst:88 -msgid "On the :guilabel:`Work Order` screen, a status graphic indicates whether the database is correctly connected to the measurement tool." -msgstr "" - -#: ../../content/applications/productivity/iot/devices/printer.rst:3 -msgid "Connect a printer" -msgstr "" - -#: ../../content/applications/productivity/iot/devices/printer.rst:5 -msgid "Printer installation can be done in a few easy steps. The printer can be used to print receipts, labels, orders, or even reports from the different Odoo apps. In addition, printer actions can be assigned as an *action on a trigger* during the manufacturing process, or added onto a quality control point or a quality check." -msgstr "" - -#: ../../content/applications/productivity/iot/devices/printer.rst:13 -msgid "The :abbr:`IoT (Internet of Things)` box supports printers connected through :abbr:`USB (Universal Serial Bus)`, network connection, or Bluetooth. `Supported printers `__ are detected automatically, and appear in the :guilabel:`Devices` list of the *IoT app*." -msgstr "" - -#: ../../content/applications/productivity/iot/devices/printer.rst:-1 -msgid "The printer as it would appear in the IoT app devices list." -msgstr "" - -#: ../../content/applications/productivity/iot/devices/printer.rst:23 -msgid "The printer can take up to two minutes to appear in the *IoT app* devices list." -msgstr "" - -#: ../../content/applications/productivity/iot/devices/printer.rst:26 -msgid "Link printer" -msgstr "" - -#: ../../content/applications/productivity/iot/devices/printer.rst:29 -msgid "Link printer to work orders" -msgstr "" - -#: ../../content/applications/productivity/iot/devices/printer.rst:31 -msgid "*Work Orders* can be linked to printers, via a quality control point, to print labels for manufactured products." -msgstr "" - -#: ../../content/applications/productivity/iot/devices/printer.rst:34 -msgid "In the *Quality app*, a device can be set up on a quality control point. To do that, go to the :menuselection:`Quality app --> Quality Control --> Control Points`, and open the desired control point to which the printer will be linked." -msgstr "" - -#: ../../content/applications/productivity/iot/devices/printer.rst:39 -msgid "A *Manufacturing Operation* and *Work Order Operation* need to be attached to a quality control point before the :guilabel:`Type` field allows for the :guilabel:`Print Label` option to be selected." -msgstr "" - -#: ../../content/applications/productivity/iot/devices/printer.rst:43 -msgid "From here, edit the control point, by selecting the :guilabel:`Type` field, and selecting :guilabel:`Print Label` from the drop-down menu of options. Doing so reveals a field called :guilabel:`Device`, where the attached *device* can be selected. :guilabel:`Save` the changes, if required." -msgstr "" - -#: ../../content/applications/productivity/iot/devices/printer.rst:-1 -msgid "This is the quality control point setup." -msgstr "" - -#: ../../content/applications/productivity/iot/devices/printer.rst:52 -msgid "The printer can now be used with the selected quality control point. When the quality control point is reached during the manufacturing process, the database presents the option to print labels for a specific product." -msgstr "" - -#: ../../content/applications/productivity/iot/devices/printer.rst:65 -msgid "On a quality check detail form, the :guilabel:`Type` of check can also be specified to :guilabel:`Print Label`. To create new quality checks, navigate to :menuselection:`Quality app --> Quality Control --> Quality Checks --> New`." -msgstr "" - -#: ../../content/applications/productivity/iot/devices/printer.rst:74 -msgid "Link a printer to a work center in the Manufacturing app" -msgstr "" - -#: ../../content/applications/productivity/iot/devices/printer.rst:76 -msgid "To link a printer to an action, it first needs to be configured on a work center. To do that, navigate to :menuselection:`Manufacturing app --> Configuration --> Work Centers`. From here, select the desired work center in which the printer will be used. Next, add the device in the :guilabel:`IoT Triggers` tab, under the :guilabel:`Device` column, by selecting :guilabel:`Add a Line`." -msgstr "" - -#: ../../content/applications/productivity/iot/devices/printer.rst:82 -msgid "Then, the printer can be linked to either of the following options in the :guilabel:`Actions` drop-down menu: :guilabel:`Print Labels`, :guilabel:`Print Operation`, or :guilabel:`Print Delivery Slip`. A key can also be added to trigger the action." -msgstr "" - -#: ../../content/applications/productivity/iot/devices/printer.rst:87 -msgid "The first listed trigger on the form will be chosen first. So, the order matters, and these triggers can be dragged into any order." -msgstr "" - -#: ../../content/applications/productivity/iot/devices/printer.rst:91 -msgid "On the :guilabel:`Work Order` screen, a status graphic indicates whether the database is correctly connected to the printer." -msgstr "" - -#: ../../content/applications/productivity/iot/devices/printer.rst:98 -msgid "Link printer to reports" -msgstr "" - -#: ../../content/applications/productivity/iot/devices/printer.rst:100 -msgid "It's also possible to link a type of report to a certain printer. In the *IoT app*, go to the :guilabel:`Devices` menu, and select the desired printer that needs to be configured." -msgstr "" - -#: ../../content/applications/productivity/iot/devices/printer.rst:103 -msgid "From here, click :guilabel:`Edit`, go to the :guilabel:`Printer Reports` tab, and select :guilabel:`Add a line`. In the window that appears, check all the types of :guilabel:`Reports` that should be linked to this printer." -msgstr "" - -#: ../../content/applications/productivity/iot/devices/printer.rst:-1 -msgid "The printer devices listed in the IoT Devices menu." -msgstr "" - -#: ../../content/applications/productivity/iot/devices/printer.rst:111 -msgid "Now, each time :guilabel:`Print` is selected in the control panel, instead of downloading a PDF, a pop-up appears which displays all the printer(s) linked to the report. Then Odoo sends the report to the selected printer(s), and automatically prints it." -msgstr "" - -#: ../../content/applications/productivity/iot/devices/printer.rst:116 -msgid ":doc:`POS Order Printing <../../../sales/point_of_sale/restaurant/kitchen_printing>`" -msgstr "" - -#: ../../content/applications/productivity/iot/devices/printer.rst:119 -msgid "Reports can also be configured in the :guilabel:`Technical Menu` while in :ref:`debug mode `. To do that, navigate to :menuselection:`Settings App --> Technical Menu --> Actions --> Reports`. From here, the individual report can be found in this list, where the :guilabel:`IoT Device` can be set on the report." -msgstr "" - -#: ../../content/applications/productivity/iot/devices/scale.rst:3 -msgid "Connect a scale" -msgstr "" - -#: ../../content/applications/productivity/iot/devices/scale.rst:5 -msgid "A scale can be connected to the :abbr:`IoT (Internet of Things)` box on an Odoo database in a few easy steps. After setup, the *Point of Sale* app can be used to weigh products, which is helpful if their prices are calculated based on weight." -msgstr "" - -#: ../../content/applications/productivity/iot/devices/scale.rst:12 -msgid "To link the scale to the :abbr:`IoT (Internet of Things)` box, connect it with a :abbr:`USB (Universal Serial Bus)` cable." -msgstr "" - -#: ../../content/applications/productivity/iot/devices/scale.rst:16 -msgid "In some cases, a serial port to :abbr:`USB (Universal Serial Bus)` adapter may be needed." -msgstr "" - -#: ../../content/applications/productivity/iot/devices/scale.rst:18 -msgid "If the scale is `compatible with Odoo IoT Box `_, 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:-1 -msgid "IOT box auto detection." -msgstr "" - -#: ../../content/applications/productivity/iot/devices/scale.rst:25 -msgid "The :abbr:`IoT (Internet of Things)` box may need to be restarted and the scale's drivers may need to be downloaded to the box in some cases. To update the drivers, go to the :abbr:`IoT (Internet of Things)` box homepage and click on :guilabel:`Drivers List`. Then, click on :guilabel:`Load Drivers`." -msgstr "" - -#: ../../content/applications/productivity/iot/devices/scale.rst:-1 -msgid "View of the IoT box settings and driver list." -msgstr "" - -#: ../../content/applications/productivity/iot/devices/scale.rst:34 -msgid "If loading the drivers still doesn't allow for the scale to function, it may be that the scale is not compatible with the Odoo :abbr:`IoT (Internet of Things)` box. In this case, a different scale will need to be used." -msgstr "" - -#: ../../content/applications/productivity/iot/devices/scale.rst:39 -msgid "Use a scale in a point of sale (POS) system" -msgstr "" - -#: ../../content/applications/productivity/iot/devices/scale.rst:41 -msgid "To use the scale in the *Point of Sale app*, go to :menuselection:`PoS app --> 3-Dot Menu on the PoS --> Settings`, then enable the :abbr:`IoT (Internet of Things)` box feature. After this is complete, the scale device can be set." -msgstr "" - -#: ../../content/applications/productivity/iot/devices/scale.rst:45 -msgid "Select the scale from the :guilabel:`Electronic Scale` drop-down menu. Then click :guilabel:`Save` to save the changes, if required." -msgstr "" - -#: ../../content/applications/productivity/iot/devices/scale.rst:-1 -msgid "List of the external tools that can be used with PoS and the IoT box." -msgstr "" - -#: ../../content/applications/productivity/iot/devices/scale.rst:52 -msgid "The scale is now available in all the :abbr:`PoS (Point of Sale)` sessions. Now, if a product has a price per weight set, clicking on it on the :guilabel:`PoS` screen opens the scale screen, where the cashier can weigh the product and add the correct price to the cart." -msgstr "" - -#: ../../content/applications/productivity/iot/devices/scale.rst:-1 -msgid "Electronic Scale dashboard view when no items are being weighed." -msgstr "" - -#: ../../content/applications/productivity/iot/devices/screen.rst:3 -msgid "Connect a screen" -msgstr "" - -#: ../../content/applications/productivity/iot/devices/screen.rst:5 -msgid "In Odoo, an :abbr:`IoT (Internet of Things)` box can be connected to a screen display. After being configured, the screen can be used to display a Point of Sale (PoS) order to a client." -msgstr "" - -#: ../../content/applications/productivity/iot/devices/screen.rst:10 -msgid "An example of a PoS (point of sale) order on a screen display." -msgstr "" - -#: ../../content/applications/productivity/iot/devices/screen.rst:12 -msgid "Access the customer display by going to the :abbr:`IoT (Internet of Things)` box homepage and clicking on the :guilabel:`PoS Display` button. To get to the :abbr:`IoT (Internet of Things)` box homepage, navigate to :menuselection:`IoT app --> IoT Boxes` and click on the :abbr:`IoT (Internet of Things)` box homepage link." -msgstr "" - -#: ../../content/applications/productivity/iot/devices/screen.rst:20 -msgid "The way to connect the screen display to the :abbr:`IoT (Internet of Things)` box differs depending on the model." -msgstr "" - -#: ../../content/applications/productivity/iot/devices/screen.rst:25 -msgid "IoT Box model 4" -msgstr "" - -#: ../../content/applications/productivity/iot/devices/screen.rst:27 -msgid "Connect up to two screens with micro-HDMI cables on the side of the :abbr:`IoT (Internet of Things)` box. If two screens are connected, they can display distinct content (see :ref:`Screen Usage `)." -msgstr "" - -#: ../../content/applications/productivity/iot/devices/screen.rst:31 -msgid "IoT Box model 3" -msgstr "" - -#: ../../content/applications/productivity/iot/devices/screen.rst:33 -msgid "Connect the screen with an HDMI cable on the side of the :abbr:`IoT (Internet of Things)` box." -msgstr "" - -#: ../../content/applications/productivity/iot/devices/screen.rst:36 -msgid ":ref:`See the Raspberry Pi Schema `." -msgstr "" - -#: ../../content/applications/productivity/iot/devices/screen.rst:39 -msgid "Screen(s) should be connected before the :abbr:`IoT (Internet of Things)` box is switched on. If it is already on, connect the screen(s), and then restart the :abbr:`IoT (Internet of Things)` box by unplugging it for ten seconds and plugging it back into its power source." -msgstr "" - -#: ../../content/applications/productivity/iot/devices/screen.rst:44 -msgid "The usage of HDMI/micro-HDMI adapters may cause issues which will result in a blank, black screen on the screen display. Using the specific cable for the display connection is recommended." -msgstr "" - -#: ../../content/applications/productivity/iot/devices/screen.rst:47 -msgid "If the connection was successful, the screen should display the :guilabel:`POS Client display` screen." -msgstr "" - -#: ../../content/applications/productivity/iot/devices/screen.rst:-1 -msgid "The default \"POS Client Display\" screen that appears when a screen display is successfully\n" -"connected to an IoT box." -msgstr "" - -#: ../../content/applications/productivity/iot/devices/screen.rst:55 -msgid "The screen should also appear in the list of :guilabel:`Displays` on the :abbr:`IoT (Internet of Things)` box homepage. Alternatively, the display can be seen by accessing :menuselection:`IoT app --> Devices`." -msgstr "" - -#: ../../content/applications/productivity/iot/devices/screen.rst:-1 -msgid "An example of a screen display name shown on the IoT Box Home Page." -msgstr "" - -#: ../../content/applications/productivity/iot/devices/screen.rst:64 -msgid "If no screen is detected, a default display named :guilabel:`Distant Display` will be displayed instead. This indicates that there is no hardware screen connected." -msgstr "" - -#: ../../content/applications/productivity/iot/devices/screen.rst:0 -msgid "The \"Distant Display\" screen name will be used if no screen is detected." -msgstr "" - -#: ../../content/applications/productivity/iot/devices/screen.rst:74 -msgid "Usage" -msgstr "" - -#: ../../content/applications/productivity/iot/devices/screen.rst:77 -msgid "Show Point of Sale orders to customers" -msgstr "" - -#: ../../content/applications/productivity/iot/devices/screen.rst:79 -msgid "To use the screen in the *Point of Sale app*, go to :menuselection:`Point of Sale --> Configuration --> Point of Sale`, select a :abbr:`PoS (Point of Sale)`, click :guilabel:`Edit` if necessary, and enable the :guilabel:`IoT Box` feature." -msgstr "" - -#: ../../content/applications/productivity/iot/devices/screen.rst:83 -msgid "Next, select the screen from the :guilabel:`Customer Display` drop-down menu. Then click :guilabel:`Save`, if required." -msgstr "" - -#: ../../content/applications/productivity/iot/devices/screen.rst:-1 -msgid "Connect the screen display to the Point of Sale app." -msgstr "" - -#: ../../content/applications/productivity/iot/devices/screen.rst:90 -msgid "The screen is now available for :abbr:`PoS (Point of Sale)` sessions. A screen icon will appear in the menu at the top of the screen to indicate the screen's connection status." -msgstr "" - -#: ../../content/applications/productivity/iot/devices/screen.rst:-1 -msgid "The \"screen\" icon on the Point of Sale display shows the connection status with the\n" -"screen." -msgstr "" - -#: ../../content/applications/productivity/iot/devices/screen.rst:98 -msgid "The screen will automatically show the :abbr:`PoS (Point of Sale)` orders and update when changes are made to the order." -msgstr "" - -#: ../../content/applications/productivity/iot/devices/screen.rst:-1 -msgid "An example of a PoS order on a screen display." -msgstr "" - -#: ../../content/applications/productivity/iot/devices/screen.rst:106 -msgid "Display a website on the screen" -msgstr "" - -#: ../../content/applications/productivity/iot/devices/screen.rst:108 -msgid "Open the screen form view by accessing :menuselection:`IoT app --> Devices --> Customer Display`. This allows the user to choose a particular website URL to display on the screen using the :guilabel:`Display URL` field." +#: ../../content/applications/productivity/documents.rst:306 +msgid ":doc:`AI-powered document digitization <../finance/accounting/vendor_bills/invoice_digitization>`" msgstr "" #: ../../content/applications/productivity/knowledge.rst:7 @@ -3358,7 +1276,7 @@ msgid "To remove the cover, hover over it to make the buttons appear and click : msgstr "" #: ../../content/applications/productivity/knowledge/articles_editing.rst:78 -msgid "To associate Unsplash with your database, please refer to :doc:`../../websites/website/configuration/unsplash`." +msgid "To associate Unsplash with your database, please refer to :doc:`/applications/general/integrations/unsplash`." msgstr "" #: ../../content/applications/productivity/knowledge/articles_editing.rst:80 @@ -3839,7 +1757,6 @@ msgid "Categories displayed in the left sidebar of Odoo Knowledge" msgstr "" #: ../../content/applications/productivity/knowledge/properties.rst:3 -#: ../../content/applications/productivity/studio/fields.rst:453 msgid "Properties" msgstr "" @@ -3994,2249 +1911,689 @@ msgstr "" msgid "To hide the property sidebar panel, click the gear :guilabel:`(⚙)` button." msgstr "" -#: ../../content/applications/productivity/mail_plugins.rst:5 -msgid "Mail Plugins" +#: ../../content/applications/productivity/sign.rst:3 +msgid "Sign" msgstr "" -#: ../../content/applications/productivity/mail_plugins.rst:13 -msgid "Mail Plugins are connectors that bridge your mailbox with your Odoo database. With them, you can interact with your Odoo database directly from your mailbox by:" +#: ../../content/applications/productivity/sign.rst:5 +msgid "**Odoo Sign** allows you to send, sign, and approve documents online, using electronic signatures." msgstr "" -#: ../../content/applications/productivity/mail_plugins.rst:16 -msgid "Creating leads and centralizing prospects' emails into the CRM app." +#: ../../content/applications/productivity/sign.rst:7 +msgid "An **electronic signature** shows a person's agreement to the content of a document. Just like a handwritten signature, the electronic one represents a legal bounding by the terms of the signed document." msgstr "" -#: ../../content/applications/productivity/mail_plugins.rst:17 -msgid "Generating tasks in any Odoo project." +#: ../../content/applications/productivity/sign.rst:11 +msgid "With Sign, you can upload any PDF file and add fields to it. These fields can be automatically filled in with the user's details present in your database." msgstr "" -#: ../../content/applications/productivity/mail_plugins.rst:18 -msgid "Creating tickets in the Helpdesk app." +#: ../../content/applications/productivity/sign.rst:15 +msgid "`Odoo Sign: product page `_" msgstr "" -#: ../../content/applications/productivity/mail_plugins.rst:19 -msgid "Searching and storing insights on your contacts." +#: ../../content/applications/productivity/sign.rst:16 +msgid "`Odoo Tutorials: Sign [video] `_" msgstr "" -#: ../../content/applications/productivity/mail_plugins.rst:21 -msgid "Mail Plugins are available for :doc:`Outlook ` and :doc:`Gmail `." +#: ../../content/applications/productivity/sign.rst:19 +msgid "Validity of electronic signatures" msgstr "" -#: ../../content/applications/productivity/mail_plugins.rst:27 -msgid "Pricing" +#: ../../content/applications/productivity/sign.rst:21 +msgid "Documents signed via the Sign app are valid electronic signatures in the European Union and the United States of America. They also meet the requirements for electronic signatures in most countries. The legal validity of electronic signatures generated by Odoo depends on your country's legislation. Companies doing business abroad should also consider other countries' electronic signature laws." msgstr "" -#: ../../content/applications/productivity/mail_plugins.rst:29 -msgid "Mail Plugins are **free** to install and use." +#: ../../content/applications/productivity/sign.rst:28 +msgid "European Union" msgstr "" -#: ../../content/applications/productivity/mail_plugins.rst:31 -msgid "However, they can provide **Lead Enrichment**, which is part of a paid service known as **Lead Generation**." +#: ../../content/applications/productivity/sign.rst:30 +msgid "The `eIDAS regulation `_ establishes the framework for electronic signatures in the `27 member states of the European Union `_. It distinguishes three types of electronic signatures:" msgstr "" -#: ../../content/applications/productivity/mail_plugins.rst:34 -msgid "Mail plugins allow you to test Lead Enrichment for free, whether you connect the plugins to a database or not. After a while, the plugins ask you to buy :doc:`../general/in_app_purchase` credits if you would like to keep using this service." +#: ../../content/applications/productivity/sign.rst:35 +msgid "Simple electronic signatures" msgstr "" -#: ../../content/applications/productivity/mail_plugins.rst:41 -msgid "Lead Generation IAP service" +#: ../../content/applications/productivity/sign.rst:36 +msgid "Advanced electronic signatures" msgstr "" -#: ../../content/applications/productivity/mail_plugins.rst:43 -msgid "Lead Enrichment uses the *Lead Generation IAP service*. Each request consumes one *Lead Generation credit*." +#: ../../content/applications/productivity/sign.rst:37 +msgid "Qualified electronic signatures" msgstr "" -#: ../../content/applications/productivity/mail_plugins.rst:46 -msgid "To buy credits, go to :menuselection:`Settings --> CRM --> Lead Enrichment --> Buy credits` and select a package." +#: ../../content/applications/productivity/sign.rst:39 +msgid "Odoo generates the first type, **simple electronic signatures**; these signatures are legally valid in the EU, as stated in the eIDAS regulation." msgstr "" -#: ../../content/applications/productivity/mail_plugins.rst:50 -msgid "If you are out of credits, the only information populated when clicking on the suggested company is its website link and logo." +#: ../../content/applications/productivity/sign.rst:42 +msgid "Electronic signatures may not be automatically recognized as valid. You may need to bring supporting evidence of a signature's validity. While the Sign app provides a simple electronic signature, some supporting evidence is automatically collected during the signature process, such as:" msgstr "" -#: ../../content/applications/productivity/mail_plugins.rst:52 -msgid "Check out the `Lead Generation IAP service Privacy Policy `_." +#: ../../content/applications/productivity/sign.rst:47 +msgid "Email and SMS validation (if enabled)" msgstr "" -#: ../../content/applications/productivity/mail_plugins.rst:56 -msgid ":doc:`../general/in_app_purchase`" +#: ../../content/applications/productivity/sign.rst:48 +msgid "Strong identity proof through itsme® (available in Belgium and the Netherlands)" msgstr "" -#: ../../content/applications/productivity/mail_plugins.rst:57 -msgid "`Odoo Tutorials: Lead Enrichment `_" +#: ../../content/applications/productivity/sign.rst:49 +msgid "Timestamped, IP and geographically traceable access logs to the documents and their associated signatures" msgstr "" -#: ../../content/applications/productivity/mail_plugins/gmail.rst:3 -msgid "Gmail Plugin" +#: ../../content/applications/productivity/sign.rst:51 +msgid "Document traceability and inalterability (any alteration made to a signed document is detected by Odoo with the use of cryptographic proofs)" msgstr "" -#: ../../content/applications/productivity/mail_plugins/gmail.rst:5 -msgid "The *Gmail Plugin* integrates an Odoo database with a Gmail inbox, so users can keep track of all their work between Gmail and Odoo, without losing any information." +#: ../../content/applications/productivity/sign.rst:55 +msgid "United States of America" msgstr "" -#: ../../content/applications/productivity/mail_plugins/gmail.rst:9 -msgid "Odoo Online users" +#: ../../content/applications/productivity/sign.rst:57 +msgid "The `ESIGN Act (Electronic Signatures in Global and National Commerce Act) `_, at the interstate and international levels, and the `UETA (Uniform Electronic Transactions Act) `_, at the state level, provide the legal framework for electronic signatures. Note that `Illinois `_ and `New York `_ have not adopted the UETA, but similar acts instead." msgstr "" -#: ../../content/applications/productivity/mail_plugins/gmail.rst:11 -msgid "For databases hosted on Odoo Online (or Odoo.sh), follow the steps below to configure the Gmail Plugin." +#: ../../content/applications/productivity/sign.rst:66 +msgid "Overall, to be recognized as valid, electronic signatures have to meet five criteria:" msgstr "" -#: ../../content/applications/productivity/mail_plugins/gmail.rst:15 -#: ../../content/applications/productivity/mail_plugins/gmail.rst:94 -msgid "Install the Gmail Plugin" +#: ../../content/applications/productivity/sign.rst:68 +msgid "The signer must show a clear **intent to sign**. For example, using a mouse to draw a signature can show intent. The signer must also have the option to opt out of the electronic document." msgstr "" -#: ../../content/applications/productivity/mail_plugins/gmail.rst:17 -msgid "First, log in to the Gmail account that the user wishes to connect to Odoo." +#: ../../content/applications/productivity/sign.rst:70 +msgid "The signer must first express or imply their **consent to conduct business electronically**." msgstr "" -#: ../../content/applications/productivity/mail_plugins/gmail.rst:19 -msgid "From the Gmail inbox, click the plus sign icon on the right side panel to get add-ons. If the side panel is not visible, click on the arrow icon at the bottom right corner of the inbox to reveal it." +#: ../../content/applications/productivity/sign.rst:71 +msgid "**The signature must be clearly attributed**. In Odoo, metadata, such as the signer's IP address, is added to the signature, which can be used as supporting evidence." msgstr "" -#: ../../content/applications/productivity/mail_plugins/gmail.rst:-1 -msgid "Plus sign icon on the Gmail inbox side panel." +#: ../../content/applications/productivity/sign.rst:73 +msgid "**The signature must be associated with the signed document**, for example, by keeping a record detailing how the signature was captured." msgstr "" -#: ../../content/applications/productivity/mail_plugins/gmail.rst:26 -msgid "Then, use the search bar to search for `Odoo` and locate the :guilabel:`Odoo Inbox Addin`." +#: ../../content/applications/productivity/sign.rst:75 +msgid "Electronically signed documents need to be **retained and stored** by all parties involved; for example, by providing the signer either a fully-executed copy or the possibility to download a copy." msgstr "" -#: ../../content/applications/productivity/mail_plugins/gmail.rst:-1 -msgid "Odoo Inbox Addin on Google Workspace Marketplace." +#: ../../content/applications/productivity/sign.rst:80 +msgid "The above information has no legal value; it is only provided for general informational purposes. As laws governing electronic signatures rapidly evolve, we cannot guarantee that all information is up-to-date. We advise contacting a local attorney for legal advice regarding electronic signature compliance and validity." msgstr "" -#: ../../content/applications/productivity/mail_plugins/gmail.rst:32 -msgid "Or, go directly to the :guilabel:`Odoo Inbox Addin` page on the `Google Workspace Marketplace `_." +#: ../../content/applications/productivity/sign.rst:86 +msgid "Send a document to sign" msgstr "" -#: ../../content/applications/productivity/mail_plugins/gmail.rst:35 -msgid "Once the plugin is located, click :guilabel:`Install`. Then, click :guilabel:`Continue` to start the installation." +#: ../../content/applications/productivity/sign.rst:89 +msgid "One-time signature" msgstr "" -#: ../../content/applications/productivity/mail_plugins/gmail.rst:38 -msgid "Next, select which Gmail account the user wishes to connect to Odoo. Then click :guilabel:`Allow` to let Odoo access the Google account. Google will then show a pop-up window confirming that the installation was successful." +#: ../../content/applications/productivity/sign.rst:91 +msgid "You can click :guilabel:`Upload a PDF to sign` from your dashboard for a one-time signature. Select your document, open it, and drag and drop the required :ref:`fields ` in your document. You can modify the :ref:`role ` assigned to a field by clicking on it and selecting the one you want." msgstr "" -#: ../../content/applications/productivity/mail_plugins/gmail.rst:43 -#: ../../content/applications/productivity/mail_plugins/gmail.rst:134 -msgid "Configure the Odoo database" +#: ../../content/applications/productivity/sign.rst:96 +msgid "When ready, click :guilabel:`Send`, and fill in the required fields. Once sent, your document remains available. Go to :menuselection:`Documents --> All Documents` to see your document and the status of the signatures." msgstr "" -#: ../../content/applications/productivity/mail_plugins/gmail.rst:45 -#: ../../content/applications/productivity/mail_plugins/gmail.rst:136 -msgid "The :guilabel:`Mail Plugin` feature must be enabled in the Odoo database in order to use the Gmail Plugin. To enable the feature, go to :menuselection:`Settings --> General Settings`. Under the :guilabel:`Integrations` section, activate :guilabel:`Mail Plugin`, and then click :guilabel:`Save`." +#: ../../content/applications/productivity/sign.rst:-1 +msgid "Signature status" msgstr "" -#: ../../content/applications/productivity/mail_plugins/gmail.rst:-1 -msgid "The Mail Plugin feature in the Settings." +#: ../../content/applications/productivity/sign.rst:104 +msgid "Validity dates and reminders" msgstr "" -#: ../../content/applications/productivity/mail_plugins/gmail.rst:55 -#: ../../content/applications/productivity/mail_plugins/gmail.rst:145 -msgid "Configure the Gmail inbox" +#: ../../content/applications/productivity/sign.rst:106 +msgid "You can set **validity dates** on limited-duration agreement documents or send **automatic email reminders** to obtain signatures on time. From your dashboard, click :guilabel:`Send` on your document. On the new page, go to the :guilabel:`Options` section and fill in the :guilabel:`Valid Until` and :guilabel:`Reminder` fields." msgstr "" -#: ../../content/applications/productivity/mail_plugins/gmail.rst:57 -#: ../../content/applications/productivity/mail_plugins/gmail.rst:147 -msgid "In the Gmail inbox, a purple Odoo icon is now visible on the right side panel. Click on the Odoo icon to open up the Odoo plugin window. Then, click on any email in the inbox. Click :guilabel:`Authorize Access` in the plugin window to grant Odoo access to the Gmail inbox." +#: ../../content/applications/productivity/sign.rst:112 +#: ../../content/applications/productivity/spreadsheet/templates.rst:3 +msgid "Templates" msgstr "" -#: ../../content/applications/productivity/mail_plugins/gmail.rst:-1 -msgid "The Authorize Access button in the right sidebar of the Odoo plugin panel." +#: ../../content/applications/productivity/sign.rst:114 +msgid "You can create document templates when you have to send the same document several times. From your dashboard, click :guilabel:`Upload a PDF template`. Select the document and add the required :ref:`fields `. You can modify the :ref:`role ` of a field by clicking on it and selecting the one you want." msgstr "" -#: ../../content/applications/productivity/mail_plugins/gmail.rst:65 -#: ../../content/applications/productivity/mail_plugins/gmail.rst:155 -msgid "Next, click :guilabel:`Login`. Then, enter the URL of the Odoo database that the user wishes to connect to the Gmail inbox, and log in to the database." +#: ../../content/applications/productivity/sign.rst:119 +msgid "Click :guilabel:`Template Properties` to add :guilabel:`Tags` to your template, define a :guilabel:`Signed Document Workspace`, add :guilabel:`Signed Document Tags`, set a :guilabel:`Redirect Link` that will be available in the signature confirmation message received after the signature, or define :guilabel:`Authorized Users` if you want to restrict the use of your template to specific authorized users or groups." msgstr "" -#: ../../content/applications/productivity/mail_plugins/gmail.rst:69 -#: ../../content/applications/productivity/mail_plugins/gmail.rst:159 -msgid "Use the general URL for the database, not the URL of a specific page in the database. For example, use `https://mycompany.odoo.com`, not `https://mycompany.odoo.com/web#cids=1&action=menu`." +#: ../../content/applications/productivity/sign.rst:125 +msgid "Your templates are visible by default on your dashboard. You can click :guilabel:`Send` to quickly send a document template to a signer or :guilabel:`Sign Now` if you are ready to sign your document immediately." msgstr "" -#: ../../content/applications/productivity/mail_plugins/gmail.rst:73 -#: ../../content/applications/productivity/mail_plugins/gmail.rst:163 -msgid "Finally, click :guilabel:`Allow` to let Gmail access the Odoo database. The browser will then show a :guilabel:`Success!` message. After that, close the window. The Gmail inbox and Odoo database are now connected." +#: ../../content/applications/productivity/sign.rst:130 +msgid "You can **create a template from a document that was previously sent**. To do so, go to :menuselection:`Documents --> All Documents`. On the document you want to retrieve, click on the the vertical ellipsis (:guilabel:`⋮`), then :guilabel:`Template`. Click on the vertical ellipsis (:guilabel:`⋮`) again, then :guilabel:`Restore`. Your document now appears on your dashboard next to your other templates." msgstr "" -#: ../../content/applications/productivity/mail_plugins/gmail.rst:78 -msgid "Odoo On-Premise users" +#: ../../content/applications/productivity/sign.rst:139 +msgid "Roles" msgstr "" -#: ../../content/applications/productivity/mail_plugins/gmail.rst:80 -msgid "For databases hosted on servers other than Odoo Online (or Odoo.sh), follow the steps below to configure the Gmail Plugin." +#: ../../content/applications/productivity/sign.rst:141 +msgid "Each field in a Sign document is related to a role corresponding to a specific person. When a document is being signed, the person assigned to the role must fill in their assigned fields and sign it." msgstr "" -#: ../../content/applications/productivity/mail_plugins/gmail.rst:84 -msgid "As part of their security guidelines, Google requires add-on creators to provide a list of URLs that can be used in actions and redirections launched by the add-on. This protects users by ensuring, for example, that no add-on redirects users toward a malicious website. (Read more on `Google Apps Script `_.)" +#: ../../content/applications/productivity/sign.rst:145 +msgid "Roles are available by going to :menuselection:`Sign --> Configuration --> Roles`." msgstr "" -#: ../../content/applications/productivity/mail_plugins/gmail.rst:89 -msgid "Since Odoo can only list the `odoo.com` domain and not every on-premise customer's unique server domain, on-premise customers cannot install the Gmail Plugin from the Google Workspace Marketplace." +#: ../../content/applications/productivity/sign.rst:147 +msgid "It is possible to update existing roles or to create new roles by clicking on :guilabel:`New`. Choose a :guilabel:`Role Name`, add an :guilabel:`Extra Authentication Step` to confirm the identity of the signing person, and if the document can be reassigned to another contact, select :guilabel:`Change Authorized` for the role. A :guilabel:`Color` can also be chosen for the role. This color can help understand which roles are responsible for which field when configuring a template." msgstr "" -#: ../../content/applications/productivity/mail_plugins/gmail.rst:96 -msgid "First, access the `GitHub repository `_ for the Odoo Mail Plugins. Next, click on the green :guilabel:`Code` button. Then, click :guilabel:`Download ZIP` to download the Mail Plugin files onto the user's computer." +#: ../../content/applications/productivity/sign.rst:155 +msgid "Secured identification" msgstr "" -#: ../../content/applications/productivity/mail_plugins/gmail.rst:-1 -msgid "Download the ZIP file from the Odoo GitHub repository for Mail Plugins." +#: ../../content/applications/productivity/sign.rst:157 +msgid "As the owner of a document, you may request an :guilabel:`Extra Authentication Step` through :ref:`SMS verification ` or via :ref:`Itsme® ` (available in Belgium and the Netherlands). Both authentication options require :ref:`credits `. If you do not have any credits left, the authentication steps will be skipped." msgstr "" -#: ../../content/applications/productivity/mail_plugins/gmail.rst:104 -msgid "Open the ZIP file on the computer. Then, go to :menuselection:`mail-client-extensions-master --> gmail --> src --> views`, and open the :file:`login.ts` file using any text editor software, such as Notepad (Windows), TextEdit (Mac), or Visual Studio Code." +#: ../../content/applications/productivity/sign.rst:163 +msgid ":doc:`In-App Purchase (IAP) <../essentials/in_app_purchase>`" msgstr "" -#: ../../content/applications/productivity/mail_plugins/gmail.rst:108 -msgid "Delete the following three lines of text from the :file:`login.ts` file:" +#: ../../content/applications/productivity/sign.rst:164 +msgid ":doc:`SMS pricing and FAQ <../marketing/sms_marketing/pricing/pricing_and_faq>`" msgstr "" -#: ../../content/applications/productivity/mail_plugins/gmail.rst:116 -msgid "This removes the `odoo.com` domain constraint from the Gmail Plugin program." +#: ../../content/applications/productivity/sign.rst:169 +msgid "SMS verification" msgstr "" -#: ../../content/applications/productivity/mail_plugins/gmail.rst:118 -msgid "Next, in the ZIP file, go to :menuselection:`mail-client-extensions-master --> gmail`, and open the file called :guilabel:`appsscript.json`. In the :guilabel:`urlFetchWhitelist` section, replace all the references to `odoo.com` with the Odoo customer's unique server domain." +#: ../../content/applications/productivity/sign.rst:171 +msgid "Go to :menuselection:`Sign --> Configuration --> Roles`. Click in the :guilabel:`Extra Authentication Step` column for the role, and select :guilabel:`Unique Code Via SMS`." msgstr "" -#: ../../content/applications/productivity/mail_plugins/gmail.rst:122 -msgid "Then, in the same :guilabel:`gmail` folder, open the file called :guilabel:`README.md`. Follow the instructions in the :guilabel:`README.md` file to push the Gmail Plugin files as a Google Project." +#: ../../content/applications/productivity/sign.rst:175 +msgid "Before being able to send SMS Text Messages, you need to register your phone number. To do so, go to :menuselection:`Sign --> Configuration --> Settings` and click :guilabel:`Buy credits` under :guilabel:`Authenticate by SMS`." msgstr "" -#: ../../content/applications/productivity/mail_plugins/gmail.rst:126 -msgid "The computer must be able to run Linux commands in order to follow the instructions on the :guilabel:`README.md` file." +#: ../../content/applications/productivity/sign.rst:179 +msgid "Go to the document to sign, add the field for which the SMS verification is required, for example, the :guilabel:`Signature` field, and click :guilabel:`Send`. On the new page, select the :guilabel:`customer` and click :guilabel:`Send`." msgstr "" -#: ../../content/applications/productivity/mail_plugins/gmail.rst:129 -msgid "After that, share the Google Project with the Gmail account that the user wishes to connect to Odoo. Then, click :guilabel:`Publish` and :guilabel:`Deploy from manifest`. Lastly, click :guilabel:`Install the add-on` to install the Gmail Plugin." +#: ../../content/applications/productivity/sign.rst:183 +msgid "The person signing the document fills in the :guilabel:`Signature` field, then :guilabel:`Sign`, and clicks :guilabel:`Validate & Send Completed Document`. A :guilabel:`Final Validation` page pops up where to add their phone number. One-time codes are sent by SMS." msgstr "" -#: ../../content/applications/productivity/mail_plugins/outlook.rst:3 -msgid "Outlook Plugin" +#: ../../content/applications/productivity/sign.rst:-1 +msgid "Add a hash to your document" msgstr "" -#: ../../content/applications/productivity/mail_plugins/outlook.rst:5 -msgid "Outlook allows for third-party applications to connect in order to execute database actions from emails. Odoo has a plugin for Outlook that allows for the creation of an opportunity from the email panel." +#: ../../content/applications/productivity/sign.rst:191 +msgid "This feature is enabled by default." msgstr "" -#: ../../content/applications/productivity/mail_plugins/outlook.rst:12 -msgid "The Outlook :doc:`Mail Plugin <../mail_plugins>` needs to be configured both on Odoo and Outlook." +#: ../../content/applications/productivity/sign.rst:192 +msgid "As soon as the :guilabel:`Extra Authentication Step` applies to a role, this validation step is requested for any field assigned to this role." msgstr "" -#: ../../content/applications/productivity/mail_plugins/outlook.rst:17 -msgid "Enable Mail Plugin" +#: ../../content/applications/productivity/sign.rst:198 +msgid "Itsme®" msgstr "" -#: ../../content/applications/productivity/mail_plugins/outlook.rst:19 -msgid "First, enable the *Mail Plugin* feature in the database. Go to :menuselection:`Settings --> General Settings --> Integrations`, enable :guilabel:`Mail Plugin`, and :guilabel:`Save` the configuration." +#: ../../content/applications/productivity/sign.rst:200 +msgid "Itsme® authentication can be used to allow signatories to provide their identity using itsme®. This feature is only available in **Belgium** and the **Netherlands**." msgstr "" -#: ../../content/applications/productivity/mail_plugins/outlook.rst:25 -msgid "Install the Outlook Plugin" +#: ../../content/applications/productivity/sign.rst:203 +msgid "The feature can be enabled in :guilabel:`Sign Settings` and applies automatically to the :guilabel:`Customer (identified with itsme®)` role. To enable it for other roles, go to :menuselection:`Sign --> Configuration --> Roles`. Click in the :guilabel:`Extra Authentication Step` column for the role, and select :guilabel:`Via itsme®`." msgstr "" -#: ../../content/applications/productivity/mail_plugins/outlook.rst:27 -msgid "Download (:menuselection:`Save Page As --> Web Page XML only`) the following XML file to upload later: `https://download.odoocdn.com/plugins/outlook/manifest.xml `_." +#: ../../content/applications/productivity/sign.rst:208 +msgid "Go to the document that needs to be signed and add the :guilabel:`Signature` field. Switch to any role configured to use the feature, and click :guilabel:`Validate` and :guilabel:`Send`." msgstr "" -#: ../../content/applications/productivity/mail_plugins/outlook.rst:31 -msgid "Next, open the Outlook mailbox, and select any email. After completing this, click on the :guilabel:`More actions` button in the upper right-side and select :guilabel:`Get Add-ins`." +#: ../../content/applications/productivity/sign.rst:-1 +msgid "select customer identified with itsme®" msgstr "" -#: ../../content/applications/productivity/mail_plugins/outlook.rst:-1 -msgid "More actions button in Outlook" +#: ../../content/applications/productivity/sign.rst:214 +msgid "Upon signing the document, the signer completes the :guilabel:`Signature` field and proceeds by clicking on :guilabel:`Validate & Send Completed Document`, triggering a :guilabel:`Final verification` page where authentication via itsme® is required." msgstr "" -#: ../../content/applications/productivity/mail_plugins/outlook.rst:38 -msgid "Following this step, select the :guilabel:`My add-ins` tab on the left-side." +#: ../../content/applications/productivity/sign.rst:219 +msgid "Signatory hash" msgstr "" -#: ../../content/applications/productivity/mail_plugins/outlook.rst:-1 -msgid "My add-ins in Outlook" +#: ../../content/applications/productivity/sign.rst:221 +msgid "Each time someone signs a document, a **hash** - a unique digital signature of the operation - is generated to ensure traceability, integrity, and inalterability. This process guarantees that any changes made after a signature is affixed can be easily detected, maintaining the document's authenticity and security throughout its lifecycle." msgstr "" -#: ../../content/applications/productivity/mail_plugins/outlook.rst:44 -msgid "Under :guilabel:`Custom add-ins` towards the bottom, click on :guilabel:`+ Add a custom add-in`, and then on :guilabel:`Add from file...`" +#: ../../content/applications/productivity/sign.rst:226 +msgid "A visual security frame displaying the beginning of the hash is added to the signatures. Internal users can hide or show it by turning the :guilabel:`Frame` option on or off when signing the document." msgstr "" -#: ../../content/applications/productivity/mail_plugins/outlook.rst:-1 -msgid "Custom add-ins in Outlook" +#: ../../content/applications/productivity/sign.rst:-1 +msgid "Adding the visual security frame to a signature." msgstr "" -#: ../../content/applications/productivity/mail_plugins/outlook.rst:51 -msgid "For the next step, attach the `manifest.xml` file downloaded above, and press :guilabel:`OK`. Next, read the warning and click on :guilabel:`Install`." +#: ../../content/applications/productivity/sign.rst:238 +msgid "Tags can be used to categorize and organize documents, allowing users to quickly search for and filter documents based on specific criteria." msgstr "" -#: ../../content/applications/productivity/mail_plugins/outlook.rst:-1 -msgid "Custom add-in installation warning in Outlook" +#: ../../content/applications/productivity/sign.rst:241 +msgid "You can manage tags by going to :menuselection:`Configuration --> Tags`. To create a tag, click :guilabel:`New`. On the new line, add the :guilabel:`Tag Name` and select a :guilabel:`Color Index` for your tag." msgstr "" -#: ../../content/applications/productivity/mail_plugins/outlook.rst:61 -msgid "Connect the database" +#: ../../content/applications/productivity/sign.rst:245 +msgid "To apply a tag to a document, use the dropdown list available in your document." msgstr "" -#: ../../content/applications/productivity/mail_plugins/outlook.rst:63 -msgid "Now, Outlook will be connected to the Odoo database. First, open any email in the Outlook mailbox, click on the :guilabel:`More actions` button in the upper right-side, and select :guilabel:`Odoo for Outlook`." +#: ../../content/applications/productivity/sign.rst:248 +msgid "You can modify the tags of a signed document by going to :menuselection:`Documents --> All Documents`, clicking the vertical ellipsis (:guilabel:`⋮`) on your document, then :guilabel:`Details`, and modifying your :guilabel:`Tags`." msgstr "" -#: ../../content/applications/productivity/mail_plugins/outlook.rst:-1 -msgid "Odoo for Outlook add-in button" +#: ../../content/applications/productivity/sign.rst:253 +msgid "Sign order" msgstr "" -#: ../../content/applications/productivity/mail_plugins/outlook.rst:71 -msgid "The right-side panel can now display **Company Insights**. At the bottom, click on :guilabel:`Login`." +#: ../../content/applications/productivity/sign.rst:255 +msgid "When a document needs to be signed by different parties, the signing order lets you control the order in which your recipients receive it for signature." msgstr "" -#: ../../content/applications/productivity/mail_plugins/outlook.rst:-1 -msgid "Logging in the Odoo database" +#: ../../content/applications/productivity/sign.rst:258 +msgid "After uploading a PDF with at least two signature fields with two different roles and clicking :guilabel:`Send`, toggle the :guilabel:`Specify Signing Order` button and search for the signer's name or email information to add them. You can decide on the signing order by typing **1** or **2** in the first column." msgstr "" -#: ../../content/applications/productivity/mail_plugins/outlook.rst:79 -msgid "Only a limited amount of **Company Insights** (*Lead Enrichment*) requests are available as a trial database. This feature requires :ref:`prepaid credits `." +#: ../../content/applications/productivity/sign.rst:263 +msgid "Each recipient receives the signature request notification only once the previous recipient has completed their action." msgstr "" -#: ../../content/applications/productivity/mail_plugins/outlook.rst:83 -msgid "If, after a short while, the panel is still empty, it is possible that the browser cookie settings prevented it from loading. Note that these settings also change if the browser is in \"Incognito\" mode." +#: ../../content/applications/productivity/sign.rst:267 +msgid "`Odoo Quick Tips: Sign order [video] `_" msgstr "" -#: ../../content/applications/productivity/mail_plugins/outlook.rst:87 -msgid "To fix this issue, configure the browser to always allow cookies on Odoo's plugin page." +#: ../../content/applications/productivity/sign.rst:272 +msgid "Field types" msgstr "" -#: ../../content/applications/productivity/mail_plugins/outlook.rst:89 -msgid "For Google Chrome, change the browser cookie settings by following the guide at: `https://support.google.com/chrome/answer/95647 `_ and adding `download.odoo.com` to the list of :guilabel:`Sites that can always use cookies`." +#: ../../content/applications/productivity/sign.rst:274 +msgid "Fields are used in a document to indicate what information must be completed by the signers. You can add fields to your document simply by dragging and dropping them for the left column into your document." msgstr "" -#: ../../content/applications/productivity/mail_plugins/outlook.rst:94 -msgid "Once this is complete, the Outlook panel needs to be opened again." +#: ../../content/applications/productivity/sign.rst:278 +msgid "Various field types can be used to sign documents (placeholder, autocompletion, etc.). By configuring your own field types, also known as signature item types, the signing process can be even faster for your customers, partners, and employees." msgstr "" -#: ../../content/applications/productivity/mail_plugins/outlook.rst:96 -msgid "Now, enter the Odoo database URL and click on :guilabel:`Login`." +#: ../../content/applications/productivity/sign.rst:282 +msgid "To create and edit field types, go to :menuselection:`Sign --> Configuration --> Settings --> Edit field types`." msgstr "" -#: ../../content/applications/productivity/mail_plugins/outlook.rst:-1 -msgid "Entering the Odoo database URL" +#: ../../content/applications/productivity/sign.rst:285 +msgid "You can select an existing field by clicking on it, or you can :guilabel:`Create` a new one. First, edit the :guilabel:`Field Name`. Then, select a :guilabel:`Field Type`:" msgstr "" -#: ../../content/applications/productivity/mail_plugins/outlook.rst:102 -msgid "Next, click on :guilabel:`Allow` to open the pop-up window." +#: ../../content/applications/productivity/sign.rst:288 +msgid ":guilabel:`Signature`: users are asked to enter their signature either by drawing it, generating an automatic one based on their name, or uploading a local file (usually an image). Each subsequent :guilabel:`Signature` field type then reuses the data entered in the first field." msgstr "" -#: ../../content/applications/productivity/mail_plugins/outlook.rst:-1 -msgid "New window pop-up warning" +#: ../../content/applications/productivity/sign.rst:291 +msgid ":guilabel:`Initial`: users are asked to enter their initials, in a similar way to the :guilabel:`Signature` field." msgstr "" -#: ../../content/applications/productivity/mail_plugins/outlook.rst:108 -msgid "If the user isn't logged into the database, enter the credentials. Click on :guilabel:`Allow` to let the Outlook Plugin connect to the database." +#: ../../content/applications/productivity/sign.rst:293 +msgid ":guilabel:`Text`: users enter text on a single line." msgstr "" -#: ../../content/applications/productivity/mail_plugins/outlook.rst:-1 -msgid "Allowing the Outlook Plugin to connect to a database" +#: ../../content/applications/productivity/sign.rst:294 +msgid ":guilabel:`Multiline Text`: users enter text on multiple lines." msgstr "" -#: ../../content/applications/productivity/mail_plugins/outlook.rst:118 -msgid "Add a shortcut to the plugin" +#: ../../content/applications/productivity/sign.rst:295 +msgid ":guilabel:`Checkbox`: users can tick a box (e.g., to mark their approval or consent)." msgstr "" -#: ../../content/applications/productivity/mail_plugins/outlook.rst:120 -msgid "By default, the Outlook Plugin can be opened from the *More actions* menu. However, to save time, it's possible to add it next to the other default actions." +#: ../../content/applications/productivity/sign.rst:296 +msgid ":guilabel:`Selection`: users choose a single option from a variety of options." msgstr "" -#: ../../content/applications/productivity/mail_plugins/outlook.rst:123 -msgid "In the Outlook mailbox, click on :guilabel:`Settings`, then on :guilabel:`View all Outlook settings`." +#: ../../content/applications/productivity/sign.rst:298 +msgid "The :guilabel:`Auto-fill Partner Field` setting is used to automatically fill in a field during the signature process. It uses the value of one of the fields on the contact (`res.partner`) model of the person signing the document. To do so, enter the contact model field's technical name." msgstr "" -#: ../../content/applications/productivity/mail_plugins/outlook.rst:-1 -msgid "Viewing all Outlook settings" +#: ../../content/applications/productivity/sign.rst:303 +msgid "To know the technical name of a field, enable developer mode and hover your mouse on the question mark next to the field." msgstr "" -#: ../../content/applications/productivity/mail_plugins/outlook.rst:130 -msgid "Now, select :guilabel:`Customize actions` under :guilabel:`Mail`, click on :guilabel:`Odoo for Outlook`, and then :guilabel:`Save`." +#: ../../content/applications/productivity/sign.rst:307 +msgid "Auto-completed values are suggestions and can be modified as required by the person signing the document." msgstr "" -#: ../../content/applications/productivity/mail_plugins/outlook.rst:-1 -msgid "Odoo for Outlook customized action" +#: ../../content/applications/productivity/sign.rst:310 +msgid "The size of the fields can also be changed by editing the :guilabel:`Default Width` and :guilabel:`Default Height`. Both sizes are defined as a percentage of the full page expressed as a decimal, with 1 equalling the full page's width or height. By default, the width of new fields you create is set to 15% (0.150) of a full page's width, while their height is set to 1.5% (0.015) of a full page's height." msgstr "" -#: ../../content/applications/productivity/mail_plugins/outlook.rst:137 -msgid "Following this step, open any email; the shortcut should be displayed." +#: ../../content/applications/productivity/sign.rst:316 +msgid "Next, write a :guilabel:`Tip`. Tips are displayed inside arrows on the left-hand side of the user's screen during the signing process to help them understand what the step entails (e.g., \"Sign here\" or “Fill in your birthdate”). You can also use a :guilabel:`Placeholder` text to be displayed inside the field before it is completed." msgstr "" -#: ../../content/applications/productivity/mail_plugins/outlook.rst:144 -msgid "Using the plugin" +#: ../../content/applications/productivity/sign.rst:-1 +msgid "Tip and placeholder example in Odoo Sign" msgstr "" -#: ../../content/applications/productivity/mail_plugins/outlook.rst:146 -msgid "Now that the plug-in is installed and operational, all that needs to be done to create a lead is to click on the `O` [Odoo icon] or navigate to :guilabel:`More actions` and click on :guilabel:`Odoo for Outlook`. The side panel will appear on the right-side, and under :guilabel:`Opportunities` click on :guilabel:`New`. A new window with the created opportunity in the Odoo database will populate." +#: ../../content/applications/productivity/spreadsheet.rst:6 +msgid "Spreadsheet" msgstr "" -#: ../../content/applications/productivity/studio.rst:6 -msgid "Studio" +#: ../../content/applications/productivity/spreadsheet.rst:14 +msgid "Spreadsheet lets you organize, analyze, and visualize your data in tabular form. Among others, you can:" msgstr "" -#: ../../content/applications/productivity/studio.rst:17 -msgid "Studio is a toolbox that allows you to customize Odoo without coding knowledge. For example, you can, on any app, add or modify:" +#: ../../content/applications/productivity/spreadsheet.rst:17 +msgid ":doc:`Insert and link your Odoo data (pivots, graphs, lists, and menus) `." msgstr "" -#: ../../content/applications/productivity/studio.rst:20 -msgid ":doc:`Fields `" +#: ../../content/applications/productivity/spreadsheet.rst:18 +msgid ":doc:`Use default templates or create new ones `." msgstr "" -#: ../../content/applications/productivity/studio.rst:21 -msgid ":doc:`Views `" +#: ../../content/applications/productivity/spreadsheet.rst:19 +msgid "Format data." msgstr "" -#: ../../content/applications/productivity/studio.rst:22 -msgid ":doc:`Models `" +#: ../../content/applications/productivity/spreadsheet.rst:20 +msgid "Use formulas and functions." msgstr "" -#: ../../content/applications/productivity/studio.rst:23 -msgid ":doc:`Automated actions `" +#: ../../content/applications/productivity/spreadsheet.rst:21 +msgid "Sort and filter data." msgstr "" -#: ../../content/applications/productivity/studio.rst:24 -msgid ":doc:`PDF reports `" +#: ../../content/applications/productivity/spreadsheet.rst:26 +msgid "Glossary" msgstr "" -#: ../../content/applications/productivity/studio.rst:25 -msgid "Approval rules" +#: ../../content/applications/productivity/spreadsheet.rst:28 +msgid "Some of Spreadsheet's main :abbr:`UI (user interface)` elements are highlighted and defined below." msgstr "" -#: ../../content/applications/productivity/studio.rst:26 -msgid "Security rules" +#: ../../content/applications/productivity/spreadsheet.rst:-1 +msgid "Spreadsheet main UI elements" msgstr "" -#: ../../content/applications/productivity/studio.rst:28 -msgid "Or you can :doc:`build an app from scratch `." +#: ../../content/applications/productivity/spreadsheet.rst:34 +msgid "Menu bar" msgstr "" -#: ../../content/applications/productivity/studio.rst:31 -msgid "`Odoo Tutorials: Studio `_" +#: ../../content/applications/productivity/spreadsheet.rst:35 +msgid "Top bar" msgstr "" -#: ../../content/applications/productivity/studio/automated_actions.rst:3 -msgid "Automated actions (automations)" +#: ../../content/applications/productivity/spreadsheet.rst:36 +msgid "Formula bar" msgstr "" -#: ../../content/applications/productivity/studio/automated_actions.rst:5 -msgid "Automated actions are used to trigger automatic changes based on user actions (e.g., apply a modification when a field is set to a specific value) or on time conditions (e.g., archive a record 7 days after its last update)." +#: ../../content/applications/productivity/spreadsheet.rst:37 +msgid "Filters button" msgstr "" -#: ../../content/applications/productivity/studio/automated_actions.rst:9 -msgid "To create an automated action with Studio, go to :guilabel:`Automations` from anywhere within Studio." +#: ../../content/applications/productivity/spreadsheet.rst:38 +msgid "Row header" msgstr "" -#: ../../content/applications/productivity/studio/automated_actions.rst:12 -msgid "For every automated action you create, the following elements should be defined: the :ref:`studio/automated-actions/model`, the :ref:`studio/automated-actions/trigger`, the :ref:`studio/automated-actions/apply-on`, and the :ref:`studio/automated-actions/action`." +#: ../../content/applications/productivity/spreadsheet.rst:39 +msgid "Column header" msgstr "" -#: ../../content/applications/productivity/studio/automated_actions.rst:0 -msgid "Example of an automated action on the Subscription model" +#: ../../content/applications/productivity/spreadsheet.rst:40 +msgid "Cell menu" msgstr "" -#: ../../content/applications/productivity/studio/automated_actions.rst:25 -msgid "Model" +#: ../../content/applications/productivity/spreadsheet.rst:41 +msgid "Bottom bar" msgstr "" -#: ../../content/applications/productivity/studio/automated_actions.rst:27 -msgid "Select the model where the automated action should be applied." +#: ../../content/applications/productivity/spreadsheet/insert.rst:3 +msgid "Link Odoo data" msgstr "" -#: ../../content/applications/productivity/studio/automated_actions.rst:30 -msgid "The model you are on when you click on :guilabel:`Automations` is pre-selected by default." +#: ../../content/applications/productivity/spreadsheet/insert.rst:5 +msgid "You can insert and link several elements from your database in your spreadsheets, namely:" msgstr "" -#: ../../content/applications/productivity/studio/automated_actions.rst:35 -msgid "Trigger" +#: ../../content/applications/productivity/spreadsheet/insert.rst:7 +msgid "pivots," msgstr "" -#: ../../content/applications/productivity/studio/automated_actions.rst:37 -msgid "Define when the automated action should be applied. Six triggers are available." +#: ../../content/applications/productivity/spreadsheet/insert.rst:8 +msgid "graphs," msgstr "" -#: ../../content/applications/productivity/studio/automated_actions.rst:42 -msgid "On Creation" +#: ../../content/applications/productivity/spreadsheet/insert.rst:9 +msgid "lists, and" msgstr "" -#: ../../content/applications/productivity/studio/automated_actions.rst:44 -msgid "The action is triggered when a record is created and then saved." +#: ../../content/applications/productivity/spreadsheet/insert.rst:10 +msgid "links to menus (i.e., a clickable link to a view of a specific model)." msgstr "" -#: ../../content/applications/productivity/studio/automated_actions.rst:49 -msgid "On Update" +#: ../../content/applications/productivity/spreadsheet/insert.rst:12 +msgid "Before inserting :ref:`pivots `, :ref:`graphs `, or lists, ensure they are tailored to your needs, as some elements are more quickly - or only - configurable in their respective view." msgstr "" -#: ../../content/applications/productivity/studio/automated_actions.rst:51 -msgid "The action is triggered when a previously saved record is edited and then saved." +#: ../../content/applications/productivity/spreadsheet/insert.rst:16 +msgid "To insert pivots and graphs, click :guilabel:`Insert in spreadsheet` from any pivot or graph view." msgstr "" -#: ../../content/applications/productivity/studio/automated_actions.rst:53 -msgid "Use :guilabel:`Trigger Fields` to specify which fields - and only those - trigger the action on their update." +#: ../../content/applications/productivity/spreadsheet/insert.rst:17 +msgid "To insert lists, click :menuselection:`Favorites --> Insert list in spreadsheet` from any list view." msgstr "" -#: ../../content/applications/productivity/studio/automated_actions.rst:55 -msgid "To detect when a record changes from one state to another, define a :guilabel:`Before Update Domain` filter, which checks if the condition is satisfied before the record is updated. Then set an :ref:`studio/automated-actions/apply-on` filter, which checks if the condition is met after the record is updated." +#: ../../content/applications/productivity/spreadsheet/insert.rst:19 +msgid "To insert links to menus, click :menuselection:`Favorites --> Link menu in spreadsheet` from any view." msgstr "" -#: ../../content/applications/productivity/studio/automated_actions.rst:61 -msgid "If you want the automated action to happen when an email address is set on a contact, define the :guilabel:`Before Update Domain` to `Email is not set`, and the :guilabel:`Apply on` domain to `Email is set`." +#: ../../content/applications/productivity/spreadsheet/insert.rst:22 +msgid "In the pop-up box, either create a new spreadsheet by selecting :guilabel:`Blank spreadsheet` or insert it in an existing one by selecting it and clicking :guilabel:`Confirm`." msgstr "" -#: ../../content/applications/productivity/studio/automated_actions.rst:0 -msgid "Example of an On Update trigger" +#: ../../content/applications/productivity/spreadsheet/insert.rst:-1 +msgid "Inserting a pivot in a spreadsheet" msgstr "" -#: ../../content/applications/productivity/studio/automated_actions.rst:72 -msgid "On Creation & Update" +#: ../../content/applications/productivity/spreadsheet/insert.rst:30 +msgid "By default, new spreadsheets are saved under the :guilabel:`Spreadsheet` workspace of the Documents app." msgstr "" -#: ../../content/applications/productivity/studio/automated_actions.rst:74 -msgid "The action is triggered when a record is created and saved or edited afterward and saved." +#: ../../content/applications/productivity/spreadsheet/insert.rst:36 +msgid "Updating data" msgstr "" -#: ../../content/applications/productivity/studio/automated_actions.rst:79 -msgid "On Deletion" +#: ../../content/applications/productivity/spreadsheet/insert.rst:38 +msgid "Once inserted in a spreadsheet, your data is kept up-to-date, reflecting any changes made to your database. Reopening the spreadsheet reloads the linked data." msgstr "" -#: ../../content/applications/productivity/studio/automated_actions.rst:81 -msgid "The action is triggered when a record is deleted." +#: ../../content/applications/productivity/spreadsheet/insert.rst:42 +msgid "To update pivots and lists data without reopening a spreadsheet, go to the menu bar and click :menuselection:`Data --> Refresh all data`." msgstr "" -#: ../../content/applications/productivity/studio/automated_actions.rst:84 -msgid "This trigger is rarely used, as archiving records is usually preferred to deletion." +#: ../../content/applications/productivity/spreadsheet/insert.rst:46 +msgid "Pivot data" msgstr "" -#: ../../content/applications/productivity/studio/automated_actions.rst:89 -msgid "Based on Form Modification" +#: ../../content/applications/productivity/spreadsheet/insert.rst:48 +msgid "Using :guilabel:`Refresh all data` only updates existing pivot cells. If new cells need to be added, go to the menu bar and click :menuselection:`Data --> Re-insert pivot` to fully update the pivot. Alternatively, click :guilabel:`Insert pivot`, select the pivot, and tick :guilabel:`Display missing cells only` to preview first the missing data." msgstr "" -#: ../../content/applications/productivity/studio/automated_actions.rst:91 -msgid "The action is triggered when any change is done to a trigger field's value on the :ref:`Form view `, even before saving the record. This trigger only works on the user interface when a modification is made by a user. If the field is changed through another action and not by the user, the action will not run." +#: ../../content/applications/productivity/spreadsheet/insert.rst:0 +msgid "Displaying missing cells in a pivot" msgstr "" -#: ../../content/applications/productivity/studio/automated_actions.rst:97 -msgid "This trigger can only be used with the :ref:`Execute Python Code action `, so development is required." +#: ../../content/applications/productivity/spreadsheet/insert.rst:57 +msgid "To change which records are :ref:`used by the pivot `, right-click on a pivot cell, select :guilabel:`See pivot properties`, and click :guilabel:`Edit domain`." msgstr "" -#: ../../content/applications/productivity/studio/automated_actions.rst:103 -msgid "Based on Timed Condition" +#: ../../content/applications/productivity/spreadsheet/templates.rst:5 +msgid "Spreadsheet templates allow you to quickly create spreadsheets without starting from scratch." msgstr "" -#: ../../content/applications/productivity/studio/automated_actions.rst:105 -msgid "The action is triggered when a trigger field's date or date & time value is reached." +#: ../../content/applications/productivity/spreadsheet/templates.rst:7 +msgid "Several pre-built templates are available when creating a new spreadsheet from the **Documents** app, such as:" msgstr "" -#: ../../content/applications/productivity/studio/automated_actions.rst:107 -msgid "To trigger the action after the :guilabel:`Trigger Date`, add a number of minutes, hours, days, or months under :guilabel:`Delay after trigger date`. To trigger the action before, add a negative number instead." +#: ../../content/applications/productivity/spreadsheet/templates.rst:10 +msgid ":ref:`budget reports `," msgstr "" -#: ../../content/applications/productivity/studio/automated_actions.rst:112 -msgid "If you want to send a reminder email 30 minutes before the start of a calendar event, select the :guilabel:`Start (Calendar Event)` under :guilabel:`Trigger Date` and set the :guilabel:`Delay after trigger date` to **-30** :guilabel:`Minutes`." +#: ../../content/applications/productivity/spreadsheet/templates.rst:11 +msgid ":ref:`pipeline revenue reports `, or" msgstr "" -#: ../../content/applications/productivity/studio/automated_actions.rst:0 -msgid "Example of a Based on Timed Condition trigger" +#: ../../content/applications/productivity/spreadsheet/templates.rst:12 +msgid ":ref:`sales commission report `." msgstr "" -#: ../../content/applications/productivity/studio/automated_actions.rst:121 -msgid "By default, the scheduler checks for trigger dates every 4 hours." +#: ../../content/applications/productivity/spreadsheet/templates.rst:-1 +msgid "View of all the default templates" msgstr "" -#: ../../content/applications/productivity/studio/automated_actions.rst:126 -msgid "Apply on" +#: ../../content/applications/productivity/spreadsheet/templates.rst:17 +msgid "You can also :ref:`save any spreadsheet as a template ` and :ref:`manage and edit existing templates `." msgstr "" -#: ../../content/applications/productivity/studio/automated_actions.rst:128 -msgid "Define on which records of the model the automated action should be applied. It works the same way as when you apply filters on a model." +#: ../../content/applications/productivity/spreadsheet/templates.rst:21 +msgid "Default templates" msgstr "" -#: ../../content/applications/productivity/studio/automated_actions.rst:136 -msgid "Determine what the automated action should do (server action). There are eight types of action to choose from." +#: ../../content/applications/productivity/spreadsheet/templates.rst:26 +msgid "Accounting: budget reports" msgstr "" -#: ../../content/applications/productivity/studio/automated_actions.rst:142 -msgid "Execute Python Code" +#: ../../content/applications/productivity/spreadsheet/templates.rst:28 +msgid "Budget reports compare a company's actual spending with its budget over a defined period. Two templates are available: one uses quarterly intervals (:guilabel:`Budget Report (Quarterly)`), while the other uses monthly intervals (:guilabel:`Budget Report (Monthly)`)." msgstr "" -#: ../../content/applications/productivity/studio/automated_actions.rst:144 -msgid "The action is used to execute Python code. The available variables are described on the :guilabel:`Python Code` tab, which is also used to write your code, or on the :guilabel:`Help` tab." +#: ../../content/applications/productivity/spreadsheet/templates.rst:-1 +msgid "Extract of a budget report" msgstr "" -#: ../../content/applications/productivity/studio/automated_actions.rst:147 -msgid "To allow the action to be run through the website, tick :guilabel:`Available on the Website` and add a :guilabel:`Website Path`." +#: ../../content/applications/productivity/spreadsheet/templates.rst:35 +msgid "The cells under the :guilabel:`Actuals` column are automatically filled in with the amount of money made and spent over the corresponding period (month or quarter). The data is taken from posted journal items under :ref:`income and expense accounts `." msgstr "" -#: ../../content/applications/productivity/studio/automated_actions.rst:153 -msgid "Create a new Record" +#: ../../content/applications/productivity/spreadsheet/templates.rst:40 +msgid "Journal items under the :guilabel:`Other Income` account type are not considered when collecting data." msgstr "" -#: ../../content/applications/productivity/studio/automated_actions.rst:155 -msgid "The action is used to create a new record on any model." +#: ../../content/applications/productivity/spreadsheet/templates.rst:43 +msgid "To analyze your budget's performance, fill the cells under the :guilabel:`Budget` column with how much money you expect to make (:guilabel:`Income` rows) and spend (:guilabel:`Expenses` rows) over the related period and per account. Then, the performance (:guilabel:`Perf.`) column compares :guilabel:`Actuals` data to their corresponding budget, expressed as a percentage." msgstr "" -#: ../../content/applications/productivity/studio/automated_actions.rst:158 -msgid "Selecting a :guilabel:`Target Model` is only required if you want to target another model than the one you are on." +#: ../../content/applications/productivity/spreadsheet/templates.rst:48 +msgid "Lastly, the :guilabel:`Net Profit` row represents the total :guilabel:`Income` minus the total :guilabel:`Expenses` for the :guilabel:`Actuals` and :guilabel:`Budget` columns." msgstr "" -#: ../../content/applications/productivity/studio/automated_actions.rst:161 -msgid "To link the record that triggered the creation of the new record, select a field under :guilabel:`Link Field`. For example, you could create a contact automatically when a lead is turned into an opportunity." +#: ../../content/applications/productivity/spreadsheet/templates.rst:54 +msgid "CRM: pipeline revenue reports" msgstr "" -#: ../../content/applications/productivity/studio/automated_actions.rst:164 -msgid ":guilabel:`Data to Write` tab: the tab is used to specify the new record's values. After selecting a :guilabel:`Field`, select its :guilabel:`Evaluation Type`:" +#: ../../content/applications/productivity/spreadsheet/templates.rst:56 +msgid "Two pipeline revenue reports are available. The :guilabel:`Pipeline Revenue Report (Monthly)` is dedicated to one-time revenue (:abbr:`NRR (non-recurring revenue)`), while the :guilabel:`MRR/NRR Pipeline Revenue Report (Monthly)` covers recurring and non-recurring revenue (:abbr:`MRR (monthly recurring revenue)`)." msgstr "" -#: ../../content/applications/productivity/studio/automated_actions.rst:167 -msgid ":guilabel:`Value`: used to directly give the field's raw value in the :guilabel:`Value` column." +#: ../../content/applications/productivity/spreadsheet/templates.rst:62 +msgid "Enable :guilabel:`Recurring Revenues` by going to :menuselection:`CRM --> Configuration --> Settings`." msgstr "" -#: ../../content/applications/productivity/studio/automated_actions.rst:168 -msgid ":guilabel:`Reference`: used to select the record under the :guilabel:`Record` column and let Studio add the internal ID in the :guilabel:`Value` column." +#: ../../content/applications/productivity/spreadsheet/templates.rst:-1 +msgid "Extract of a pipeline revenue report" msgstr "" -#: ../../content/applications/productivity/studio/automated_actions.rst:172 -msgid "If an automated action creates a new task in a project, you can assign it to a specific user by setting the :guilabel:`Field` to :guilabel:`Responsible User (Project)`, the :guilabel:`Evaluation Type` to :guilabel:`Reference`, and the :guilabel:`Record` to a specific user." +#: ../../content/applications/productivity/spreadsheet/templates.rst:68 +msgid "The cells under the :guilabel:`Actuals` column are automatically filled in with the amount of monthly revenue from **won** opportunities." msgstr "" -#: ../../content/applications/productivity/studio/automated_actions.rst:0 -msgid "Example of a Create a new Record action" +#: ../../content/applications/productivity/spreadsheet/templates.rst:71 +msgid "To compute the revenue performance, fill in the monthly revenue targets." msgstr "" -#: ../../content/applications/productivity/studio/automated_actions.rst:181 -msgid ":guilabel:`Python expression`: used to dynamically define the newly created record’s value for a field using Python code in the :guilabel:`Value` column." +#: ../../content/applications/productivity/spreadsheet/templates.rst:73 +msgid "For the :guilabel:`Revenue by Team` sheet, fill in the cells under the :guilabel:`Target` columns for each sales team." msgstr "" -#: ../../content/applications/productivity/studio/automated_actions.rst:187 -msgid "Update the Record" +#: ../../content/applications/productivity/spreadsheet/templates.rst:75 +msgid "For the :guilabel:`Revenue by Salesperson` sheet, open the :guilabel:`Targets` sheet and fill in the cells next to each salesperson. Use the :guilabel:`Monthly Factor` table below to adapt the main targets depending on the month of the year." msgstr "" -#: ../../content/applications/productivity/studio/automated_actions.rst:189 -msgid "The action is used to set value(s) for field(s) of any record on the current model." +#: ../../content/applications/productivity/spreadsheet/templates.rst:79 +msgid "Then, the performance (:guilabel:`Perf.`) column compares :guilabel:`Actuals` data to their related budget, expressed as a percentage." msgstr "" -#: ../../content/applications/productivity/studio/automated_actions.rst:192 -msgid "The process to fill in the :guilabel:`Data to Write` tab is the same as described under :ref:`studio/automated-actions/action/new-record`." +#: ../../content/applications/productivity/spreadsheet/templates.rst:82 +msgid "Lastly, the :guilabel:`Forecasted` column gathers the monthly revenue of leads multiplied by their :guilabel:`Probability` percentage." msgstr "" -#: ../../content/applications/productivity/studio/automated_actions.rst:198 -msgid "Execute several actions" +#: ../../content/applications/productivity/spreadsheet/templates.rst:86 +msgid "For actuals and forecasts:" msgstr "" -#: ../../content/applications/productivity/studio/automated_actions.rst:200 -msgid "The action is used to trigger multiple actions at the same time. To do so, click on :guilabel:`Add a line` under the :guilabel:`Actions` tab. In the :guilabel:`Child Actions` pop-up, click on :guilabel:`Create` and configure the action." +#: ../../content/applications/productivity/spreadsheet/templates.rst:88 +msgid "The :guilabel:`Expected Closing` date found on leads is used to assign them to a month." msgstr "" -#: ../../content/applications/productivity/studio/automated_actions.rst:207 -msgid "Send Email" +#: ../../content/applications/productivity/spreadsheet/templates.rst:89 +msgid "The recurring monthly revenue is used even if the recurring plan's number of months is set to a different value than 1 month. For example, a yearly plan's revenue is divided by 12 months." msgstr "" -#: ../../content/applications/productivity/studio/automated_actions.rst:209 -msgid "The action is used to send an email to a contact linked to a specific record. To do so, select or create an :guilabel:`Email Template`." +#: ../../content/applications/productivity/spreadsheet/templates.rst:95 +msgid "Sales: sales commission" msgstr "" -#: ../../content/applications/productivity/studio/automated_actions.rst:215 -msgid "Add Followers" +#: ../../content/applications/productivity/spreadsheet/templates.rst:97 +msgid "This report presents the monthly commission earned or due to each salesperson." msgstr "" -#: ../../content/applications/productivity/studio/automated_actions.rst:217 -msgid "The action is used to subscribe existing contacts to the record." +#: ../../content/applications/productivity/spreadsheet/templates.rst:-1 +msgid "Extract of a sales commission report" msgstr "" -#: ../../content/applications/productivity/studio/automated_actions.rst:222 -msgid "Create Next Activity" +#: ../../content/applications/productivity/spreadsheet/templates.rst:102 +msgid "The :guilabel:`Rate` column is pre-filled with the percentage rate from the :guilabel:`Rates` tab, which can be customized for each product category according to the company's policy. Adjusting the rate for a specific product category automatically updates the commission amount for that category." msgstr "" -#: ../../content/applications/productivity/studio/automated_actions.rst:224 -msgid "The action is used to schedule a new activity linked to the record. Use the :guilabel:`Activity` tab to set it up as usual, but instead of the :guilabel:`Assigned to` field, select an :guilabel:`Activity User Type`. Select :guilabel:`Specific User` and add the user under :guilabel:`Responsible` if the activity should always be assigned to the same user. To dynamically target a user linked to the record, select :guilabel:`Generic User From Record` instead and change the :guilabel:`User field name` if necessary." +#: ../../content/applications/productivity/spreadsheet/templates.rst:106 +msgid "The :guilabel:`Invoiced` column shows the total amount of untaxed invoices grouped by salesperson and month." msgstr "" -#: ../../content/applications/productivity/studio/automated_actions.rst:232 -msgid "After a lead is turned into an opportunity, you want your automated action to set up a call for the user responsible for the lead. To do so, set the :guilabel:`Activity` to :guilabel:`Call` and set the :guilabel:`Activity User Type` to :guilabel:`Generic User From Record`." +#: ../../content/applications/productivity/spreadsheet/templates.rst:109 +msgid "Lastly, the :guilabel:`Comm.` column is computed by multiplying the invoiced amount with the rate percentage." msgstr "" -#: ../../content/applications/productivity/studio/automated_actions.rst:0 -msgid "Example of a Create Next Activity action" +#: ../../content/applications/productivity/spreadsheet/templates.rst:115 +msgid "Save a spreadsheet as a template" msgstr "" -#: ../../content/applications/productivity/studio/automated_actions.rst:243 -msgid "Send SMS Text Message" +#: ../../content/applications/productivity/spreadsheet/templates.rst:117 +msgid "Any spreadsheet can be saved as a template. From the menu bar, click :menuselection:`File --> Save as template`. Modify the default :guilabel:`Template Name` if necessary and click :guilabel:`Confirm`." msgstr "" -#: ../../content/applications/productivity/studio/automated_actions.rst:245 -msgid "The action is used to send an SMS to a contact linked to the record. To do so, select or create an :guilabel:`SMS Template`." +#: ../../content/applications/productivity/spreadsheet/templates.rst:122 +msgid "Templates are available to all users on the database." msgstr "" -#: ../../content/applications/productivity/studio/automated_actions.rst:249 -msgid "If you want sent messages to be logged in the Chatter, tick :guilabel:`Log as Note`." +#: ../../content/applications/productivity/spreadsheet/templates.rst:127 +msgid "Manage and edit templates" msgstr "" -#: ../../content/applications/productivity/studio/fields.rst:3 -msgid "Fields and widgets" +#: ../../content/applications/productivity/spreadsheet/templates.rst:129 +msgid "Manage templates by going to :menuselection:`Documents --> Configuration --> Spreadsheet Templates`. Remove the :guilabel:`My Templates` :ref:`filter ` to view all templates in the database." msgstr "" -#: ../../content/applications/productivity/studio/fields.rst:5 -msgid "Fields structure the models of a database. If you picture a model as a table or spreadsheet, fields are the columns where data is stored in the records (i.e., the rows). Fields also define the type of data that is stored within them. How the data is presented and formatted on the :abbr:`UI (User Interface)` is defined by their widget." +#: ../../content/applications/productivity/spreadsheet/templates.rst:133 +msgid "To edit an existing template, click `✎ Edit` next to the desired template. Modifications are automatically saved." msgstr "" -#: ../../content/applications/productivity/studio/fields.rst:10 -msgid "From a technical point of view, there are 15 field types in Odoo. However, you can choose from 20 fields in Studio, as some field types are available more than once with a different default widget." -msgstr "" - -#: ../../content/applications/productivity/studio/fields.rst:14 -msgid ":guilabel:`New Fields` can only be added to the :ref:`studio/views/general/form` and :ref:`studio/views/multiple-records/list` views. On other views, you can only add :guilabel:`Existing Fields` :dfn:`(fields already on the model)`." -msgstr "" - -#: ../../content/applications/productivity/studio/fields.rst:21 -msgid "Simple fields" -msgstr "" - -#: ../../content/applications/productivity/studio/fields.rst:23 -msgid "Simple fields contain basic values, such as text, numbers, files, etc." -msgstr "" - -#: ../../content/applications/productivity/studio/fields.rst:26 -#: ../../content/applications/productivity/studio/fields.rst:325 -msgid "Non-default widgets, when available, are presented as bullet points below." -msgstr "" - -#: ../../content/applications/productivity/studio/fields.rst:31 -msgid "Text (`char`)" -msgstr "" - -#: ../../content/applications/productivity/studio/fields.rst:33 -msgid "The :guilabel:`Text` field is used for short text containing any character. One text line is displayed when filling out the field." -msgstr "" - -#: ../../content/applications/productivity/studio/fields.rst:36 -#: ../../content/applications/productivity/studio/fields.rst:220 -msgid ":guilabel:`Badge`: displays the value inside a rounded shape, similar to a tag. The value cannot be edited on the UI, but a default value can be set." -msgstr "" - -#: ../../content/applications/productivity/studio/fields.rst:38 -#: ../../content/applications/productivity/studio/fields.rst:71 -msgid ":guilabel:`Copy to Clipboard`: users can copy the value by clicking a button." -msgstr "" - -#: ../../content/applications/productivity/studio/fields.rst:39 -msgid ":guilabel:`E-mail`: the value becomes a clickable *mailto* link." -msgstr "" - -#: ../../content/applications/productivity/studio/fields.rst:40 -msgid ":guilabel:`Image`: displays an image using a URL. The value cannot be edited manually, but a default value can be set." -msgstr "" - -#: ../../content/applications/productivity/studio/fields.rst:44 -msgid "This works differently than selecting the :ref:`Image field ` directly, as the image is not stored in Odoo when using a :guilabel:`Text` field with the :guilabel:`Image` widget. For example, it can be useful if you want to save disk space." -msgstr "" - -#: ../../content/applications/productivity/studio/fields.rst:49 -msgid ":guilabel:`Phone`: the value becomes a clickable *tel* link." -msgstr "" - -#: ../../content/applications/productivity/studio/fields.rst:52 -msgid "Tick :guilabel:`Enable SMS` to add an option to send an SMS directly from Odoo next to the field." -msgstr "" - -#: ../../content/applications/productivity/studio/fields.rst:55 -msgid ":guilabel:`URL`: the value becomes a clickable URL." -msgstr "" - -#: ../../content/applications/productivity/studio/fields.rst:0 -msgid "Examples of Text fields with different widgets" -msgstr "" - -#: ../../content/applications/productivity/studio/fields.rst:66 -msgid "Multiline Text (`text`)" -msgstr "" - -#: ../../content/applications/productivity/studio/fields.rst:68 -msgid "The :guilabel:`Multiline Text` field is used for longer text containing any type of character. Two text lines are displayed on the UI when filling out the field." -msgstr "" - -#: ../../content/applications/productivity/studio/fields.rst:0 -msgid "Examples of Multiline Text fields with different widgets" -msgstr "" - -#: ../../content/applications/productivity/studio/fields.rst:82 -msgid "Integer (`integer`)" -msgstr "" - -#: ../../content/applications/productivity/studio/fields.rst:84 -msgid "The :guilabel:`Integer` field is used for all integer numbers (:dfn:`positive, negative, or zero, without a decimal`)." -msgstr "" - -#: ../../content/applications/productivity/studio/fields.rst:87 -msgid ":guilabel:`Percentage Pie`: displays the value inside a percentage circle, usually for a computed value. The value cannot be edited on the UI, but a default value can be set." -msgstr "" - -#: ../../content/applications/productivity/studio/fields.rst:89 -#: ../../content/applications/productivity/studio/fields.rst:118 -msgid ":guilabel:`Progress Bar`: displays the value next to a percentage bar, usually for a computed value. The field cannot be edited manually, but a default value can be set." -msgstr "" - -#: ../../content/applications/productivity/studio/fields.rst:91 -msgid ":guilabel:`Handle`: displays a drag handle icon to order records manually in :ref:`List view `." -msgstr "" - -#: ../../content/applications/productivity/studio/fields.rst:0 -msgid "Examples of Integer fields with different widgets" -msgstr "" - -#: ../../content/applications/productivity/studio/fields.rst:103 -msgid "Decimal (`float`)" -msgstr "" - -#: ../../content/applications/productivity/studio/fields.rst:105 -msgid "The :guilabel:`Decimal` field is used for all decimal numbers (:dfn:`positive, negative, or zero, with a decimal`)." -msgstr "" - -#: ../../content/applications/productivity/studio/fields.rst:109 -msgid "Decimal numbers are displayed with two decimals after the decimal point on the UI, but they are stored in the database with more precision." -msgstr "" - -#: ../../content/applications/productivity/studio/fields.rst:112 -msgid ":guilabel:`Monetary`: it is similar to using the :ref:`Monetary field `. It is recommended to use the later as it offers more functionalities." -msgstr "" - -#: ../../content/applications/productivity/studio/fields.rst:115 -msgid ":guilabel:`Percentage`: displays a percent character `%` after the value." -msgstr "" - -#: ../../content/applications/productivity/studio/fields.rst:116 -msgid ":guilabel:`Percentage Pie`: displays the value inside a percentage circle, usually for a computed value. The field cannot be edited manually, but a default value can be set." -msgstr "" - -#: ../../content/applications/productivity/studio/fields.rst:120 -msgid ":guilabel:`Time`: the value must follow the *hh:mm* format, with a maximum of 59 minutes." -msgstr "" - -#: ../../content/applications/productivity/studio/fields.rst:0 -msgid "Examples of Decimal fields with different widgets" -msgstr "" - -#: ../../content/applications/productivity/studio/fields.rst:131 -msgid "Monetary (`monetary`)" -msgstr "" - -#: ../../content/applications/productivity/studio/fields.rst:133 -msgid "The :guilabel:`Monetary` field is used for all monetary values." -msgstr "" - -#: ../../content/applications/productivity/studio/fields.rst:136 -msgid "When you first add a :guilabel:`Monetary` field, you are prompted to add a :guilabel:`Currency` field if none exists already on the model. Odoo offers to add the :guilabel:`Currency` field for you. Once it is added, add the :guilabel:`Monetary` field again." -msgstr "" - -#: ../../content/applications/productivity/studio/fields.rst:0 -msgid "Example of a Monetary field along with its Currency field" -msgstr "" - -#: ../../content/applications/productivity/studio/fields.rst:149 -msgid "Html (`html`)" -msgstr "" - -#: ../../content/applications/productivity/studio/fields.rst:151 -msgid "The :guilabel:`Html` field is used to add text that can be edited using the Odoo HTML editor." -msgstr "" - -#: ../../content/applications/productivity/studio/fields.rst:153 -msgid ":guilabel:`Multiline Text`: disables the Odoo HTML editor to allow editing raw HTML." -msgstr "" - -#: ../../content/applications/productivity/studio/fields.rst:0 -msgid "Examples of Html fields with different widgets" -msgstr "" - -#: ../../content/applications/productivity/studio/fields.rst:164 -msgid "Date (`date`)" -msgstr "" - -#: ../../content/applications/productivity/studio/fields.rst:166 -msgid "The :guilabel:`Date` field is used to select a date on a calendar." -msgstr "" - -#: ../../content/applications/productivity/studio/fields.rst:168 -msgid ":guilabel:`Remaining Days`: the remaining number of days before the selected date is displayed (e.g., *In 5 days*), based on the current date." -msgstr "" - -#: ../../content/applications/productivity/studio/fields.rst:0 -msgid "Examples of Date fields with different widgets" -msgstr "" - -#: ../../content/applications/productivity/studio/fields.rst:180 -msgid "Date & Time (`datetime`)" -msgstr "" - -#: ../../content/applications/productivity/studio/fields.rst:182 -msgid "The :guilabel:`Date & Time` field is used to select a date on a calendar and a time on a clock. The user's current time is automatically used if no time is set." -msgstr "" - -#: ../../content/applications/productivity/studio/fields.rst:185 -msgid ":guilabel:`Date`: used to record the time without displaying it on the UI." -msgstr "" - -#: ../../content/applications/productivity/studio/fields.rst:186 -msgid ":guilabel:`Remaining days`: displays the remaining number of days before the selected date (e.g., *In 5 days*), based on the current date and time." -msgstr "" - -#: ../../content/applications/productivity/studio/fields.rst:0 -msgid "Examples of Date & Time fields with different widgets" -msgstr "" - -#: ../../content/applications/productivity/studio/fields.rst:198 -msgid "Checkbox (`boolean`)" -msgstr "" - -#: ../../content/applications/productivity/studio/fields.rst:200 -msgid "The :guilabel:`Checkbox` field is used when a value should only be true or false, indicated by checking or unchecking a checkbox." -msgstr "" - -#: ../../content/applications/productivity/studio/fields.rst:203 -msgid ":guilabel:`Button`: displays a radio button. The widget works without switching to the edit mode." -msgstr "" - -#: ../../content/applications/productivity/studio/fields.rst:204 -msgid ":guilabel:`Toggle`: displays a toggle button. The widget works without switching to the edit mode." -msgstr "" - -#: ../../content/applications/productivity/studio/fields.rst:0 -msgid "Examples of Checkbox fields with different widgets" -msgstr "" - -#: ../../content/applications/productivity/studio/fields.rst:215 -msgid "Selection (`selection`)" -msgstr "" - -#: ../../content/applications/productivity/studio/fields.rst:217 -msgid "The :guilabel:`Selection` field is used when users should select a single value from a group of predefined values." -msgstr "" - -#: ../../content/applications/productivity/studio/fields.rst:222 -msgid ":guilabel:`Badges`: displays all selectable values simultaneously inside rectangular shapes, organized horizontally." -msgstr "" - -#: ../../content/applications/productivity/studio/fields.rst:224 -msgid ":guilabel:`Priority`: displays star symbols instead of values, which can be used to indicate an importance or satisfaction level, for example. This has the same effect as selecting the :ref:`Priority field `, although, for the latter, four priority values are already predefined." -msgstr "" - -#: ../../content/applications/productivity/studio/fields.rst:228 -#: ../../content/applications/productivity/studio/fields.rst:352 -msgid ":guilabel:`Radio`: displays all selectable values at the same time as radio buttons." -msgstr "" - -#: ../../content/applications/productivity/studio/fields.rst:231 -msgid "By default, radio buttons are organized vertically. Tick :guilabel:`display horizontally` to switch the way they are displayed." -msgstr "" - -#: ../../content/applications/productivity/studio/fields.rst:0 -msgid "Examples of Selection fields with different widgets" -msgstr "" - -#: ../../content/applications/productivity/studio/fields.rst:243 -msgid "Priority (`selection`)" -msgstr "" - -#: ../../content/applications/productivity/studio/fields.rst:245 -msgid "The :guilabel:`Priority` field is used to display a three-star rating system, which can be used to indicate importance or satisfaction level. This field type is a :ref:`Selection field ` with the :guilabel:`Priority` widget selected by default and four priority values predefined. Consequently, the :guilabel:`Badge`, :guilabel:`Badges`, :guilabel:`Radio`, and :guilabel:`Selection` widgets have the same effects as described under :ref:`Selection `." -msgstr "" - -#: ../../content/applications/productivity/studio/fields.rst:253 -msgid "To change the number of available stars by adding or removing values, click :guilabel:`Edit Values`. Note that the first value is equal to 0 stars (i.e., when no selection is made), so having four values results in a three-star rating system, for example." -msgstr "" - -#: ../../content/applications/productivity/studio/fields.rst:0 -msgid "Example of a Priority field" -msgstr "" - -#: ../../content/applications/productivity/studio/fields.rst:266 -msgid "File (`binary`)" -msgstr "" - -#: ../../content/applications/productivity/studio/fields.rst:268 -msgid "The :guilabel:`File` field is used to upload any type of file, or sign a form (:guilabel:`Sign` widget)." -msgstr "" - -#: ../../content/applications/productivity/studio/fields.rst:271 -msgid ":guilabel:`Image`: users can upload an image file, which is then displayed in :ref:`Form view `. This has the same effect as using the :ref:`Image field `." -msgstr "" - -#: ../../content/applications/productivity/studio/fields.rst:274 -msgid ":guilabel:`PDF Viewer`: users can upload a PDF file, which can be then browsed from the :ref:`Form view `." -msgstr "" - -#: ../../content/applications/productivity/studio/fields.rst:276 -msgid ":guilabel:`Sign`: users can electronically sign the form. This has the same effect as selecting the :ref:`Sign field `." -msgstr "" - -#: ../../content/applications/productivity/studio/fields.rst:0 -msgid "Examples of File fields with different widgets" -msgstr "" - -#: ../../content/applications/productivity/studio/fields.rst:288 -msgid "Image (`binary`)" -msgstr "" - -#: ../../content/applications/productivity/studio/fields.rst:290 -msgid "The :guilabel:`Image` field is used to upload an image and display it in :ref:`Form view `. This field type is a :ref:`File field ` with the :guilabel:`Image` widget selected by default. Consequently, the :guilabel:`File`, :guilabel:`PDF Viewer`, and :guilabel:`Sign` widgets have the same effects as described under :ref:`File `." -msgstr "" - -#: ../../content/applications/productivity/studio/fields.rst:297 -msgid "To change the display size of uploaded images, select :guilabel:`Small`, :guilabel:`Medium`, or :guilabel:`Large` under the :guilabel:`Size` option." -msgstr "" - -#: ../../content/applications/productivity/studio/fields.rst:303 -msgid "Sign (`binary`)" -msgstr "" - -#: ../../content/applications/productivity/studio/fields.rst:305 -msgid "The :guilabel:`Sign` field is used to sign the form electronically. This field type is a :ref:`File field ` with the :guilabel:`Sign` widget selected by default. Consequently, the :guilabel:`File`, :guilabel:`Image`, and :guilabel:`PDF Viewer` widgets have the same effects as described under :ref:`File `." -msgstr "" - -#: ../../content/applications/productivity/studio/fields.rst:311 -msgid "To give users the :guilabel:`Auto` option when having to draw their signature, select one of the available :guilabel:`Auto-complete with` fields (:ref:`Text `, :ref:`Many2One `, and :ref:`Related Field ` on the model only). The signature is automatically generated using the data from the selected field." -msgstr "" - -#: ../../content/applications/productivity/studio/fields.rst:320 -msgid "Relational fields" -msgstr "" - -#: ../../content/applications/productivity/studio/fields.rst:322 -msgid "Relational fields are used to link and display the data from records on another model." -msgstr "" - -#: ../../content/applications/productivity/studio/fields.rst:330 -msgid "Many2One (`many2one`)" -msgstr "" - -#: ../../content/applications/productivity/studio/fields.rst:332 -msgid "The :guilabel:`Many2One` field is used to link another record (from another model) to the record being edited. The record's name from the other model is then displayed on the record being edited." -msgstr "" - -#: ../../content/applications/productivity/studio/fields.rst:336 -msgid "On the *Sales Order* model, the :guilabel:`Customer` field is a :guilabel:`Many2One` field pointing at the *Contact* model. This allows **many** sales orders to be linked to **one** contact (customer)." -msgstr "" - -#: ../../content/applications/productivity/studio/fields.rst:0 -msgid "Diagram showing a many2one relationship" -msgstr "" - -#: ../../content/applications/productivity/studio/fields.rst:345 -msgid "To prevent users from creating a new record in the linked model, tick :guilabel:`Disable creation`." -msgstr "" - -#: ../../content/applications/productivity/studio/fields.rst:347 -msgid "To prevent users from opening records in a pop-up window, tick :guilabel:`Disable opening`." -msgstr "" - -#: ../../content/applications/productivity/studio/fields.rst:348 -msgid "To help users only select the right record, click on :guilabel:`Domain` to create a filter." -msgstr "" - -#: ../../content/applications/productivity/studio/fields.rst:350 -msgid ":guilabel:`Badge`: displays the value inside a rounded shape, similar to a tag. The value cannot be edited on the UI." -msgstr "" - -#: ../../content/applications/productivity/studio/fields.rst:357 -msgid "One2Many (`one2many`)" -msgstr "" - -#: ../../content/applications/productivity/studio/fields.rst:359 -msgid "The :guilabel:`One2Many` field is used to display the existing relations between a record on the current model and multiple records from another model." -msgstr "" - -#: ../../content/applications/productivity/studio/fields.rst:363 -msgid "You could add a :guilabel:`One2Many` field on the *Contact* model to look at **one** customer's **many** sales orders." -msgstr "" - -#: ../../content/applications/productivity/studio/fields.rst:0 -msgid "Diagram showing a one2many relationship" -msgstr "" - -#: ../../content/applications/productivity/studio/fields.rst:371 -msgid "To use a :guilabel:`One2Many` field, the two models must have been linked already using a :ref:`Many2One field `. One2Many relations do not exist independently: a reverse-search of existing Many2One relations is performed." -msgstr "" - -#: ../../content/applications/productivity/studio/fields.rst:378 -msgid "Lines (`one2many`)" -msgstr "" - -#: ../../content/applications/productivity/studio/fields.rst:380 -msgid "The :guilabel:`Lines` field is used to create a table with rows and columns (e.g., the lines of products on a sales order)." -msgstr "" - -#: ../../content/applications/productivity/studio/fields.rst:384 -msgid "To modify the columns, click on the :guilabel:`Lines` field and then :guilabel:`Edit List View`. To edit the form that pops up when a user clicks on :guilabel:`Add a line`, click on :guilabel:`Edit Form View` instead." -msgstr "" - -#: ../../content/applications/productivity/studio/fields.rst:0 -msgid "Example of a Lines field" -msgstr "" - -#: ../../content/applications/productivity/studio/fields.rst:397 -msgid "Many2Many (`many2many`)" -msgstr "" - -#: ../../content/applications/productivity/studio/fields.rst:399 -msgid "The :guilabel:`Many2Many` field is used to link multiple records from another model to multiple records on the current model. Many2Many fields can use :guilabel:`Disable creation`, :guilabel:`Disable opening`, :guilabel:`Domain`, just like :ref:`Many2One fields `." -msgstr "" - -#: ../../content/applications/productivity/studio/fields.rst:405 -msgid "On the *Task* model, the :guilabel:`Assignees` field is a :guilabel:`Many2Many` field pointing at the *Contact* model. This allows a single user to be assigned to **many** tasks and **many** users to be assigned to a single task." -msgstr "" - -#: ../../content/applications/productivity/studio/fields.rst:0 -msgid "Diagram showing many2many relationships" -msgstr "" - -#: ../../content/applications/productivity/studio/fields.rst:413 -msgid ":guilabel:`Checkboxes`: users can select several values using checkboxes." -msgstr "" - -#: ../../content/applications/productivity/studio/fields.rst:414 -msgid ":guilabel:`Tags`: users can select several values appearing in rounded shapes, also known as *tags*. This has the same effect as selecting the :ref:`Tags field `." -msgstr "" - -#: ../../content/applications/productivity/studio/fields.rst:421 -msgid "Tags (`many2many`)" -msgstr "" - -#: ../../content/applications/productivity/studio/fields.rst:423 -msgid "The :guilabel:`Tags` field is used to display several values from another model appearing in rounded shapes, also known as *tags*. This field type is a :ref:`Many2Many field ` with the :guilabel:`Tags` widget selected by default. Consequently, the :guilabel:`Checkboxes` and :guilabel:`Many2Many` widgets have the same effects as described under :ref:`Many2Many `." -msgstr "" - -#: ../../content/applications/productivity/studio/fields.rst:430 -msgid "To display tags with different background colors, tick :guilabel:`Use colors`." -msgstr "" - -#: ../../content/applications/productivity/studio/fields.rst:0 -msgid "Example of a Tags field" -msgstr "" - -#: ../../content/applications/productivity/studio/fields.rst:441 -msgid "Related Field (`related`)" -msgstr "" - -#: ../../content/applications/productivity/studio/fields.rst:443 -msgid "A :guilabel:`Related Field` is not a relational field per se; no relationship is created between models. It uses an existing relationship to fetch and display information from another record." -msgstr "" - -#: ../../content/applications/productivity/studio/fields.rst:447 -msgid "To display the email address of a customer on the *Sales Order* model, use the :guilabel:`Related Field` `partner_id.email` by selecting :guilabel:`Customer` and then :guilabel:`Email`." -msgstr "" - -#: ../../content/applications/productivity/studio/fields.rst:455 -msgid ":guilabel:`Invisible`: When it is not necessary for users to view a field on the UI, tick :guilabel:`Invisible`. It helps clear the UI by only showing the essential fields depending on a specific situation." -msgstr "" - -#: ../../content/applications/productivity/studio/fields.rst:460 -msgid "On the *Form* view of the *Contact* model, the :guilabel:`Title` field only appears when :guilabel:`Individual` is selected, as that field would not be helpful for a :guilabel:`Company` contact." -msgstr "" - -#: ../../content/applications/productivity/studio/fields.rst:465 -msgid "The :guilabel:`Invisible` attribute also applies to Studio. To view hidden fields inside Studio, click on a view's :guilabel:`View` tab and tick :guilabel:`Show Invisible Elements`." -msgstr "" - -#: ../../content/applications/productivity/studio/fields.rst:469 -msgid ":guilabel:`Required`: If a field should always be completed by the user before being able to proceed, tick :guilabel:`Required`." -msgstr "" - -#: ../../content/applications/productivity/studio/fields.rst:471 -msgid ":guilabel:`Read only`: If users should not be able to modify a field, tick :guilabel:`Read only`." -msgstr "" - -#: ../../content/applications/productivity/studio/fields.rst:474 -msgid "You can choose to apply these three properties only for specific records by clicking on :guilabel:`Conditional` and creating a filter." -msgstr "" - -#: ../../content/applications/productivity/studio/fields.rst:477 -msgid ":guilabel:`Label`: The :guilabel:`Label` is the field's name on the UI." -msgstr "" - -#: ../../content/applications/productivity/studio/fields.rst:480 -msgid "This is not the same name as used in the PostgreSQL database. To view and change the latter, activate the :ref:`Developer mode `, and edit the :guilabel:`Technical Name`." -msgstr "" - -#: ../../content/applications/productivity/studio/fields.rst:483 -msgid ":guilabel:`Help Tooltip`: To explain the purpose of a field, write a description under :guilabel:`Help Tooltip`. It is displayed inside a tooltip box when hovering with your mouse over the field's label." -msgstr "" - -#: ../../content/applications/productivity/studio/fields.rst:486 -msgid ":guilabel:`Placeholder`: To provide an example of how a field should be completed, write it under :guilabel:`Placeholder`. It is displayed in light gray in lieu of the field's value." -msgstr "" - -#: ../../content/applications/productivity/studio/fields.rst:488 -msgid ":guilabel:`Widget`: To change the default appearance or functionality of a field, select one of the available widgets." -msgstr "" - -#: ../../content/applications/productivity/studio/fields.rst:490 -msgid ":guilabel:`Default value`: To add a default value to a field when a record is created, use :guilabel:`Default value`." -msgstr "" - -#: ../../content/applications/productivity/studio/fields.rst:492 -msgid ":guilabel:`Limit visibility to groups`: To limit which users can see the field, select a user access group." -msgstr "" - -#: ../../content/applications/productivity/studio/models_modules_apps.rst:3 -msgid "Models, modules, and apps" -msgstr "" - -#: ../../content/applications/productivity/studio/models_modules_apps.rst:5 -msgid "Models determine the logical structure of a database and how data is stored, organized, and manipulated. In other words, a model is a table of information that can be linked with other tables. A model usually represents a business concept, such as a *sales order*, *contact*, or *product*." -msgstr "" - -#: ../../content/applications/productivity/studio/models_modules_apps.rst:9 -msgid "Modules and apps contain various elements, such as models, views, data files, web controllers, and static web data." -msgstr "" - -#: ../../content/applications/productivity/studio/models_modules_apps.rst:13 -msgid "All apps are modules. Larger, standalone modules are typically referred to as apps, whereas other modules usually serve as add-ons to said apps." -msgstr "" - -#: ../../content/applications/productivity/studio/models_modules_apps.rst:19 -msgid "Suggested features" -msgstr "" - -#: ../../content/applications/productivity/studio/models_modules_apps.rst:21 -msgid "When you create a new model or app with Studio, you can choose to add up to 14 features to speed up the creation process. These features bundle fields, default settings, and views that are usually used together to provide some standard functionality. Most of these features can be added later on, but adding them from the start makes the model creation process much easier. Furthermore, these features interact together in some cases to increase their usefulness." -msgstr "" - -#: ../../content/applications/productivity/studio/models_modules_apps.rst:28 -msgid "Creating a model with the :ref:`studio/models-modules-apps/suggested-features/picture` and :ref:`studio/models-modules-apps/suggested-features/pipeline-stages` features enabled adds the image in the card layout of the :ref:`Kanban view `." -msgstr "" - -#: ../../content/applications/productivity/studio/models_modules_apps.rst:0 -msgid "Combination of the Picture and Pipeline stages features on the Kanban view" -msgstr "" - -#: ../../content/applications/productivity/studio/models_modules_apps.rst:39 -msgid "Contact details" -msgstr "" - -#: ../../content/applications/productivity/studio/models_modules_apps.rst:41 -msgid "Selecting :guilabel:`Contact details` adds to the :ref:`Form view ` a :ref:`Many2One field ` linked to the *Contact* model and two of its :ref:`Related Fields `: :guilabel:`Phone` and :guilabel:`Email`. The :guilabel:`Contact` field is also added to the :ref:`List view `, and the :ref:`Map view ` is activated." -msgstr "" - -#: ../../content/applications/productivity/studio/models_modules_apps.rst:0 -msgid "Contact details feature on the Form view" -msgstr "" - -#: ../../content/applications/productivity/studio/models_modules_apps.rst:57 -msgid "User assignment" -msgstr "" - -#: ../../content/applications/productivity/studio/models_modules_apps.rst:59 -msgid "Selecting :guilabel:`User assignment` adds to the :ref:`Form view ` a :ref:`Many2One field ` linked to the *Contact* model, with the following :guilabel:`Domain`: `Share User is not set` to only allow the selection of *Internal Users*. In addition, the :guilabel:`many2one_avatar_user` widget is used to display the user's avatar. The :guilabel:`Responsible` field is also added to the :ref:`List view `." -msgstr "" - -#: ../../content/applications/productivity/studio/models_modules_apps.rst:0 -msgid "User assignment feature on the Form view" -msgstr "" - -#: ../../content/applications/productivity/studio/models_modules_apps.rst:75 -msgid "Date & Calendar" -msgstr "" - -#: ../../content/applications/productivity/studio/models_modules_apps.rst:77 -msgid "Selecting :guilabel:`Date & Calendar` adds to the :ref:`Form view ` a :ref:`Date field ` and activates the :ref:`Calendar view `." -msgstr "" - -#: ../../content/applications/productivity/studio/models_modules_apps.rst:84 -msgid "Date range & Gantt" -msgstr "" - -#: ../../content/applications/productivity/studio/models_modules_apps.rst:86 -msgid "Selecting :guilabel:`Date range & Gantt` adds to the :ref:`Form view ` two :ref:`Date fields ` next to each other: one to set a start date, the other to set an end date, using the :guilabel:`daterange` widget, and activates the :ref:`Gantt view `." -msgstr "" - -#: ../../content/applications/productivity/studio/models_modules_apps.rst:94 -msgid "Pipeline stages" -msgstr "" - -#: ../../content/applications/productivity/studio/models_modules_apps.rst:96 -msgid "Selecting :guilabel:`Pipeline stages` activates the :ref:`Kanban view `, adds several fields such as :ref:`Priority ` and :guilabel:`Kanban State`, and three stages: :guilabel:`New`, :guilabel:`In Progress`, and :guilabel:`Done`. The :guilabel:`Pipeline status bar` and the :guilabel:`Kanban State` field are added to the :ref:`Form view `. The :guilabel:`Color` field is added to the :ref:`List view `." -msgstr "" - -#: ../../content/applications/productivity/studio/models_modules_apps.rst:105 -msgid "The :guilabel:`Pipeline stages` feature can be added at a later stage." -msgstr "" - -#: ../../content/applications/productivity/studio/models_modules_apps.rst:110 -msgid "Tags" -msgstr "" - -#: ../../content/applications/productivity/studio/models_modules_apps.rst:112 -msgid "Selecting :guilabel:`Tags` adds to the :ref:`studio/views/general/form` and :ref:`studio/views/multiple-records/list` views a :ref:`Tags field `, creating a *Tag* model with preconfigured access rights in the process." -msgstr "" - -#: ../../content/applications/productivity/studio/models_modules_apps.rst:120 -msgid "Picture" -msgstr "" - -#: ../../content/applications/productivity/studio/models_modules_apps.rst:122 -msgid "Selecting :guilabel:`Picture` adds to the top-right of the :ref:`Form view ` an :ref:`Image field `." -msgstr "" - -#: ../../content/applications/productivity/studio/models_modules_apps.rst:126 -msgid "The :guilabel:`Picture` feature can be added at a later stage." -msgstr "" - -#: ../../content/applications/productivity/studio/models_modules_apps.rst:131 -msgid "Lines" -msgstr "" - -#: ../../content/applications/productivity/studio/models_modules_apps.rst:133 -msgid "Selecting :guilabel:`Lines`: adds to the :ref:`Form view ` a :ref:`Lines field ` inside a :guilabel:`Tab` component." -msgstr "" - -#: ../../content/applications/productivity/studio/models_modules_apps.rst:139 -msgid "Notes" -msgstr "" - -#: ../../content/applications/productivity/studio/models_modules_apps.rst:141 -msgid "Selecting :guilabel:`Notes` adds to the :ref:`Form view ` an :ref:`Html field ` using the full width of the form." -msgstr "" - -#: ../../content/applications/productivity/studio/models_modules_apps.rst:147 -msgid "Monetary value" -msgstr "" - -#: ../../content/applications/productivity/studio/models_modules_apps.rst:149 -msgid "Selecting :guilabel:`Monetary value` adds to the :ref:`studio/views/general/form` and :ref:`studio/views/multiple-records/list` views a :ref:`Monetary field `. The :ref:`studio/views/reporting/graph` and :ref:`studio/views/reporting/pivot` views are also activated." -msgstr "" - -#: ../../content/applications/productivity/studio/models_modules_apps.rst:155 -msgid "A *Currency* field is added and hidden from the view." -msgstr "" - -#: ../../content/applications/productivity/studio/models_modules_apps.rst:160 -msgid "Company" -msgstr "" - -#: ../../content/applications/productivity/studio/models_modules_apps.rst:162 -msgid "Selecting :guilabel:`Company` adds to the :ref:`studio/views/general/form` and :ref:`studio/views/multiple-records/list` views a :ref:`Many2One field ` linked to the *Company* model." -msgstr "" - -#: ../../content/applications/productivity/studio/models_modules_apps.rst:167 -msgid "This is only useful if you work in a multi-company environment." -msgstr "" - -#: ../../content/applications/productivity/studio/models_modules_apps.rst:172 -msgid "Custom Sorting" -msgstr "" - -#: ../../content/applications/productivity/studio/models_modules_apps.rst:174 -msgid "Selecting :guilabel:`Custom Sorting` adds to the :ref:`List view ` a drag handle icon to manually reorder records." -msgstr "" - -#: ../../content/applications/productivity/studio/models_modules_apps.rst:0 -msgid "Custom Sorting feature on the List view" -msgstr "" - -#: ../../content/applications/productivity/studio/models_modules_apps.rst:186 -msgid "Chatter" -msgstr "" - -#: ../../content/applications/productivity/studio/models_modules_apps.rst:188 -msgid "Selecting :guilabel:`Chatter` adds to the :ref:`Form view ` Chatter functionalities (sending messages, logging notes, and scheduling activities)." -msgstr "" - -#: ../../content/applications/productivity/studio/models_modules_apps.rst:192 -msgid "The :guilabel:`Chatter` feature can be added at a later stage." -msgstr "" - -#: ../../content/applications/productivity/studio/models_modules_apps.rst:0 -msgid "Chatter feature on the Form view" -msgstr "" - -#: ../../content/applications/productivity/studio/models_modules_apps.rst:203 -msgid "Archiving" -msgstr "" - -#: ../../content/applications/productivity/studio/models_modules_apps.rst:205 -msgid "Selecting :guilabel:`Archiving` adds to the :ref:`studio/views/general/form` and :ref:`studio/views/multiple-records/list` views the :guilabel:`Archive` action and hides archived records from searches and views by default." -msgstr "" - -#: ../../content/applications/productivity/studio/models_modules_apps.rst:212 -msgid "Export and import customizations" -msgstr "" - -#: ../../content/applications/productivity/studio/models_modules_apps.rst:214 -msgid "When you do any customization with Studio, a new module named :guilabel:`Studio customizations` is added to your database." -msgstr "" - -#: ../../content/applications/productivity/studio/models_modules_apps.rst:217 -msgid "To export these customizations, go to :menuselection:`Main dashboard --> Studio --> Customizations --> Export` to download a ZIP file containing all customizations." -msgstr "" - -#: ../../content/applications/productivity/studio/models_modules_apps.rst:220 -msgid "To import and install these customizations in another database, connect to the destination database and go to :menuselection:`Main dashboard --> Studio --> Customizations --> Import`, then upload the exported ZIP file before clicking on the :guilabel:`Import` button." -msgstr "" - -#: ../../content/applications/productivity/studio/models_modules_apps.rst:225 -msgid "Before importing, make sure the destination database contains the same apps and modules as the source database. Studio does not add the underlying modules as dependencies of the exported module." -msgstr "" - -#: ../../content/applications/productivity/studio/pdf_reports.rst:3 -msgid "PDF reports" -msgstr "" - -#: ../../content/applications/productivity/studio/pdf_reports.rst:5 -msgid "With Studio, you can :ref:`edit existing PDF reports ` (e.g., invoices, quotations, etc.) or :ref:`create new ones `." -msgstr "" - -#: ../../content/applications/productivity/studio/pdf_reports.rst:11 -msgid "Default layout" -msgstr "" - -#: ../../content/applications/productivity/studio/pdf_reports.rst:13 -msgid "The default layout of reports is managed outside Studio. Go to :menuselection:`Settings`, then, in the :guilabel:`Companies` section, click :guilabel:`Configure Document Layout`. Layout settings are company-specific but apply to all reports." -msgstr "" - -#: ../../content/applications/productivity/studio/pdf_reports.rst:18 -msgid "You can see how the different settings affect the report layout in the report preview on the right, or download a sample invoice PDF by clicking :guilabel:`Download PDF Preview`." -msgstr "" - -#: ../../content/applications/productivity/studio/pdf_reports.rst:21 -msgid "Use the following settings:" -msgstr "" - -#: ../../content/applications/productivity/studio/pdf_reports.rst:25 -msgid ":guilabel:`Layout`: Four layouts are available:" -msgstr "" - -#: ../../content/applications/productivity/studio/pdf_reports.rst:29 -msgid "Light" -msgstr "" - -#: ../../content/applications/productivity/studio/pdf_reports.rst:0 -msgid "Light report layout sample" -msgstr "" - -#: ../../content/applications/productivity/studio/pdf_reports.rst:34 -msgid "Boxed" -msgstr "" - -#: ../../content/applications/productivity/studio/pdf_reports.rst:0 -msgid "Boxed report layout sample" -msgstr "" - -#: ../../content/applications/productivity/studio/pdf_reports.rst:39 -msgid "Bold" -msgstr "" - -#: ../../content/applications/productivity/studio/pdf_reports.rst:0 -msgid "Bold report layout sample" -msgstr "" - -#: ../../content/applications/productivity/studio/pdf_reports.rst:44 -msgid "Striped" -msgstr "" - -#: ../../content/applications/productivity/studio/pdf_reports.rst:0 -msgid "Striped report layout sample" -msgstr "" - -#: ../../content/applications/productivity/studio/pdf_reports.rst:51 -msgid ":guilabel:`Font`: Seven fonts are available: Lato, Roboto, Open Sans, Montserrat, Oswald, Raleway, and Tajawal (which supports Arabic and Latin scripts). Go to the `Google Fonts website `_ to preview them." -msgstr "" - -#: ../../content/applications/productivity/studio/pdf_reports.rst:57 -msgid ":guilabel:`Company logo`: Click the :guilabel:`Edit` button to upload or change the logo. This adds the logo to the company’s record on the *Company* model, which you can access by going to :menuselection:`Settings` and then clicking :guilabel:`Update Info` in the :guilabel:`Companies` section." -msgstr "" - -#: ../../content/applications/productivity/studio/pdf_reports.rst:64 -msgid ":guilabel:`Colors`: Change the primary and secondary colors used to structure reports. The default colors are automatically generated based on the colors of the logo." -msgstr "" - -#: ../../content/applications/productivity/studio/pdf_reports.rst:69 -msgid ":guilabel:`Layout background`: The following backgrounds are available:" -msgstr "" - -#: ../../content/applications/productivity/studio/pdf_reports.rst:71 -msgid ":guilabel:`Blank`: nothing is displayed." -msgstr "" - -#: ../../content/applications/productivity/studio/pdf_reports.rst:72 -msgid ":guilabel:`Geometric`: an image featuring geometric shapes is displayed in the background." -msgstr "" - -#: ../../content/applications/productivity/studio/pdf_reports.rst:73 -msgid ":guilabel:`Custom`: upload a custom background image." -msgstr "" - -#: ../../content/applications/productivity/studio/pdf_reports.rst:77 -msgid ":guilabel:`Company tagline`: This is displayed in the header of :ref:`external reports `. You can add multiple lines of text." -msgstr "" - -#: ../../content/applications/productivity/studio/pdf_reports.rst:82 -msgid ":guilabel:`Company details`: These are displayed in the header of :ref:`external reports `. You can add multiple lines of text." -msgstr "" - -#: ../../content/applications/productivity/studio/pdf_reports.rst:87 -msgid ":guilabel:`Footer`: This text is used in the footer of :ref:`external reports `. You can add multiple lines of text. You can also edit the footer using the :ref:`report editor `." -msgstr "" - -#: ../../content/applications/productivity/studio/pdf_reports.rst:93 -msgid ":guilabel:`Paper format`: to define the default paper size of reports. You can select :guilabel:`A4` (21 cm x 29.7 cm), :guilabel:`US Letter` (21.59 cm x 27.54 cm), or :guilabel:`QR codes page`. This can also be defined for individual reports in the :guilabel:`Paper format` field in :ref:`Studio `." -msgstr "" - -#: ../../content/applications/productivity/studio/pdf_reports.rst:101 -msgid "Creating new PDF reports" -msgstr "" - -#: ../../content/applications/productivity/studio/pdf_reports.rst:103 -msgid "To create a new report for a model, access the model, click the **Toggle Studio** button, then click :guilabel:`Reports`. Click :guilabel:`New` and, in the popup window that opens, select the type of report. This is solely used to determine what is displayed in the header and footer:" -msgstr "" - -#: ../../content/applications/productivity/studio/pdf_reports.rst:109 -msgid ":guilabel:`External`:" -msgstr "" - -#: ../../content/applications/productivity/studio/pdf_reports.rst:111 -msgid "The header displays the company's :ref:`logo `, :ref:`tagline `, and :ref:`details `." -msgstr "" - -#: ../../content/applications/productivity/studio/pdf_reports.rst:114 -msgid "The footer displays the values set in the :ref:`Footer ` field and the page number." -msgstr "" - -#: ../../content/applications/productivity/studio/pdf_reports.rst:117 -msgid ":guilabel:`Internal`: The header displays the user's current date and time, :guilabel:`Company Name`, and page number. There is no footer." -msgstr "" - -#: ../../content/applications/productivity/studio/pdf_reports.rst:120 -msgid ":guilabel:`Blank`: There is neither a header nor a footer. Click in the upper left corner of the page to edit the report." -msgstr "" - -#: ../../content/applications/productivity/studio/pdf_reports.rst:123 -msgid "Once you have created the report, you can start :ref:`editing it `." -msgstr "" - -#: ../../content/applications/productivity/studio/pdf_reports.rst:128 -msgid "Editing PDF reports" -msgstr "" - -#: ../../content/applications/productivity/studio/pdf_reports.rst:130 -msgid "To access the reports available for a model, access the model (e.g., sales orders), click the **Toggle Studio** button, then click :guilabel:`Reports`. Select an existing report to open it or :ref:`create a new one `." -msgstr "" - -#: ../../content/applications/productivity/studio/pdf_reports.rst:135 -msgid "Alternatively, you can also open Studio, click :guilabel:`Reports`, and search for a specific report or model." -msgstr "" - -#: ../../content/applications/productivity/studio/pdf_reports.rst:139 -msgid "It is strongly recommended to **duplicate** the standard report and perform changes in the duplicated version. To duplicate a report, hover the mouse pointer on the top right corner of the report, click the vertical ellipsis icon (:guilabel:`⋮`), and then select :guilabel:`Duplicate`." -msgstr "" - -#: ../../content/applications/productivity/studio/pdf_reports.rst:0 -msgid "Duplicating a PDF report" -msgstr "" - -#: ../../content/applications/productivity/studio/pdf_reports.rst:148 -msgid "Options" -msgstr "" - -#: ../../content/applications/productivity/studio/pdf_reports.rst:150 -msgid "Once you've selected or created a report, you can use the options in the left part of the screen to:" -msgstr "" - -#: ../../content/applications/productivity/studio/pdf_reports.rst:152 -msgid "Change the :guilabel:`Report name`. The new name is applied everywhere (in Studio, under the :guilabel:`Print` button, and in the PDF file name)." -msgstr "" - -#: ../../content/applications/productivity/studio/pdf_reports.rst:154 -msgid "Modify the :guilabel:`Paper format`. If no value is selected, the format defined in the :ref:`default layout ` is used." -msgstr "" - -#: ../../content/applications/productivity/studio/pdf_reports.rst:156 -msgid ":guilabel:`Show in print menu`: to add the report in the :guilabel:`Print` menu available from the record." -msgstr "" - -#: ../../content/applications/productivity/studio/pdf_reports.rst:158 -msgid ":guilabel:`Reload from attachment`: to save the report as an attachment on the record the first time it is generated and reload the original version of the report any subsequent time. This is legally required for invoices and is mainly used in this case." -msgstr "" - -#: ../../content/applications/productivity/studio/pdf_reports.rst:161 -msgid ":guilabel:`Limit visibility to groups`: to limit the availability of the PDF report to specific :doc:`user groups <../../general/users/access_rights>`." -msgstr "" - -#: ../../content/applications/productivity/studio/pdf_reports.rst:163 -msgid ":guilabel:`Edit sources`: to modify the report directly in the :ref:`XML file `." -msgstr "" - -#: ../../content/applications/productivity/studio/pdf_reports.rst:165 -msgid ":guilabel:`Reset report`: to discard all changes made to the report and reset it to its standard version." -msgstr "" - -#: ../../content/applications/productivity/studio/pdf_reports.rst:167 -msgid ":guilabel:`Print preview`: to generate and download a report preview." -msgstr "" - -#: ../../content/applications/productivity/studio/pdf_reports.rst:170 -msgid "Report editor" -msgstr "" - -#: ../../content/applications/productivity/studio/pdf_reports.rst:172 -msgid "The report editor allows you to modify the formatting and contents of the report." -msgstr "" - -#: ../../content/applications/productivity/studio/pdf_reports.rst:175 -msgid "You can :guilabel:`Undo` or :guilabel:`Redo` changes using the related buttons or the shortcuts `CTRL Z` and `CTRL Y`." -msgstr "" - -#: ../../content/applications/productivity/studio/pdf_reports.rst:178 -msgid "Changes are saved automatically when you leave the report or manually using the :guilabel:`Save` button." -msgstr "" - -#: ../../content/applications/productivity/studio/pdf_reports.rst:181 -msgid "You can reset the report to its standard version by clicking the :guilabel:`Reset report` button in the left part of the screen." -msgstr "" - -#: ../../content/applications/productivity/studio/pdf_reports.rst:185 -msgid "Editing the header and footer of a report impacts all standard and custom reports." -msgstr "" - -#: ../../content/applications/productivity/studio/pdf_reports.rst:188 -msgid "Conditional blocks" -msgstr "" - -#: ../../content/applications/productivity/studio/pdf_reports.rst:190 -msgid "The dashed rectangles represent **conditional blocks** (*if/else* statements). These are used to show/hide content based on specific conditions. Click on the block to view the conditions." -msgstr "" - -#: ../../content/applications/productivity/studio/pdf_reports.rst:-1 -msgid "View conditions applied to a block." -msgstr "" - -#: ../../content/applications/productivity/studio/pdf_reports.rst:196 -msgid "Select a value to preview its corresponding output and edit it if necessary." -msgstr "" - -#: ../../content/applications/productivity/studio/pdf_reports.rst:-1 -msgid "Preview the output of another condition." -msgstr "" - -#: ../../content/applications/productivity/studio/pdf_reports.rst:202 -msgid "Conditions can only be edited in :ref:`XML `." -msgstr "" - -#: ../../content/applications/productivity/studio/pdf_reports.rst:205 -msgid "Other content" -msgstr "" - -#: ../../content/applications/productivity/studio/pdf_reports.rst:207 -msgid "There are two types of text content in reports:" -msgstr "" - -#: ../../content/applications/productivity/studio/pdf_reports.rst:209 -msgid "Static text, i.e., the text that's not highlighted in blue, which can be modified directly in the editor." -msgstr "" - -#: ../../content/applications/productivity/studio/pdf_reports.rst:211 -msgid "Dynamic text, i.e., the text that's highlighted in blue, which is replaced by field values when the report is generated, e.g., the SO number or the quotation date." -msgstr "" - -#: ../../content/applications/productivity/studio/pdf_reports.rst:214 -msgid "You can add content (e.g., fields, lists, tables, images, banners, etc.) to the report using commands. Type `/` to open the :ref:`powerbox `, then type the command's name or select it from the list." -msgstr "" - -#: ../../content/applications/productivity/studio/pdf_reports.rst:218 -msgid "To add static text to the report, type the text where you want it." -msgstr "" - -#: ../../content/applications/productivity/studio/pdf_reports.rst:220 -msgid "For more advanced changes, you can :ref:`edit the report in the XML directly `." -msgstr "" - -#: ../../content/applications/productivity/studio/pdf_reports.rst:226 -msgid "Add a field" -msgstr "" - -#: ../../content/applications/productivity/studio/pdf_reports.rst:228 -msgid "To add a field, type `/` and select the :guilabel:`Field` command. In the list that opens, select or search for the field; click the right arrow next to the field name to access the list of related fields if needed. Then, specify the default value and press `Enter`." -msgstr "" - -#: ../../content/applications/productivity/studio/pdf_reports.rst:-1 -msgid "Select a related field." -msgstr "" - -#: ../../content/applications/productivity/studio/pdf_reports.rst:236 -msgid "Add a data table" -msgstr "" - -#: ../../content/applications/productivity/studio/pdf_reports.rst:238 -msgid "Data tables are used to display :ref:`relational fields `. To add a data table, type `/`, select the :guilabel:`Dynamic Table` command, and select the relation to be displayed in the table." -msgstr "" - -#: ../../content/applications/productivity/studio/pdf_reports.rst:243 -msgid "Only relations of type `one2many` or `many2many` can be displayed as data tables." -msgstr "" - -#: ../../content/applications/productivity/studio/pdf_reports.rst:245 -msgid "Once the table has been added, you can add columns using the table tools. Position the cursor on top of the column, then click the purple rectangle and select an option." -msgstr "" - -#: ../../content/applications/productivity/studio/pdf_reports.rst:-1 -msgid "Add a column in a dynamic table." -msgstr "" - -#: ../../content/applications/productivity/studio/pdf_reports.rst:251 -msgid "You can then insert the :ref:`field of your choice ` in the columns. The dialog box that opens shows the source object for the field (e.g., the *Tag* model) and the list of available fields." -msgstr "" - -#: ../../content/applications/productivity/studio/pdf_reports.rst:-1 -msgid "List of available fields for the Tag model." -msgstr "" - -#: ../../content/applications/productivity/studio/pdf_reports.rst:259 -msgid "The default row automatically iterates over the field's content, generating a row on the report for each field value (e.g., one row per tag). You can add static content rows above or below the generated rows using the table tools." -msgstr "" - -#: ../../content/applications/productivity/studio/pdf_reports.rst:262 -msgid "You can also add data tables by :ref:`modifying the report's XML `." -msgstr "" - -#: ../../content/applications/productivity/studio/pdf_reports.rst:265 -msgid "Formatting" -msgstr "" - -#: ../../content/applications/productivity/studio/pdf_reports.rst:267 -msgid "To format text in the report, select it, then format it using the options in the :ref:`knowledge/text-editor`." -msgstr "" - -#: ../../content/applications/productivity/studio/pdf_reports.rst:0 -msgid "Format text using the text editor." -msgstr "" - -#: ../../content/applications/productivity/studio/pdf_reports.rst:276 -msgid "Editing the report's XML" -msgstr "" - -#: ../../content/applications/productivity/studio/pdf_reports.rst:279 -msgid "Modifying the XML directly may result in report issues during :doc:`upgrades <../../../administration/upgrade>`. If this happens, simply copy your changes from the old database into your upgraded database." -msgstr "" - -#: ../../content/applications/productivity/studio/pdf_reports.rst:283 -msgid "To edit the report's XML, click :guilabel:`Edit sources` in the left pane." -msgstr "" - -#: ../../content/applications/productivity/studio/pdf_reports.rst:286 -msgid "Examples" -msgstr "" - -#: ../../content/applications/productivity/studio/pdf_reports.rst:290 -msgid "Sometimes, tables are not properly recognized as such due to complex structures. In those cases, you can still modify them manually in the report XML. For example, with a sales order, you can find the following structure in the XML (simplified for documentation purposes):" -msgstr "" - -#: ../../content/applications/productivity/studio/pdf_reports.rst:318 -msgid "To modify a table, you must ensure that each row has the same number of data cells. For example, in the case above, you need to add a cell in the header section (with e.g., the column title) and another one in the body section with the field content (usually, with a `t-out` or `t-field` directive)." -msgstr "" - -#: ../../content/applications/productivity/studio/pdf_reports.rst:344 -msgid "Cells can span multiple rows or columns. For more information, go to the `Mozilla Developer Network website `_." -msgstr "" - -#: ../../content/applications/productivity/studio/pdf_reports.rst:347 -msgid "For example, you can modify the **Quotation/Order** report to add a column to display the product category in the main table:" -msgstr "" - -#: ../../content/applications/productivity/studio/pdf_reports.rst:0 -msgid "Add a Product Category column in a SO." -msgstr "" - -#: ../../content/applications/productivity/studio/pdf_reports.rst:376 -msgid "To add a table in XML, you need to know the names of the fields and objects you wish to access and display. As an example, let's add a table that details the tags on a sales order:" -msgstr "" - -#: ../../content/applications/productivity/studio/pdf_reports.rst:0 -msgid "Add a data table in XML" -msgstr "" - -#: ../../content/applications/productivity/studio/pdf_reports.rst:407 -msgid "When adding tables manually, style them using `Bootstrap classes `_, like the `table` class included in the example above." -msgstr "" - -#: ../../content/applications/productivity/studio/pdf_reports.rst:413 -msgid "If you want to show/hide content based on specific conditions, you can manually add `if/else` control statements in the report XML." -msgstr "" - -#: ../../content/applications/productivity/studio/pdf_reports.rst:416 -msgid "For example, if you want to hide a custom data table if there are no tags, you can use the `t-if` attribute to define the condition, which is then evaluated as `True` or `False`. The table will not be displayed if there are no tags in the quotation." -msgstr "" - -#: ../../content/applications/productivity/studio/pdf_reports.rst:445 -msgid "If you want to display another block in case the `t-if` statement is evaluated as `False`, you can specify it using the `t-else` statement. The `t-else` block must directly follow the `t-if` block in the document structure. There is no need to specify any condition in the `t-else` attribute. As an example, let's show a quick message explaining that there are no tags on the quotation:" -msgstr "" - -#: ../../content/applications/productivity/studio/pdf_reports.rst:477 -msgid "By using the `t-if/t-else` notation, the report editor recognizes that these sections are mutually exclusive and should be displayed as conditional blocks:" -msgstr "" - -#: ../../content/applications/productivity/studio/pdf_reports.rst:0 -msgid "Output preview if there are tags." -msgstr "" - -#: ../../content/applications/productivity/studio/pdf_reports.rst:483 -msgid "You can switch conditions using the editor to preview their output:" -msgstr "" - -#: ../../content/applications/productivity/studio/pdf_reports.rst:0 -msgid "Output preview if there are no tags." -msgstr "" - -#: ../../content/applications/productivity/studio/pdf_reports.rst:488 -msgid "If you wish to have multiple options, you can also use `t-elif` directives to add intermediary conditions. For example, this is how the title of sales order reports changes based on the condition of the underlying document." -msgstr "" - -#: ../../content/applications/productivity/studio/pdf_reports.rst:501 -msgid "The title *Pro-Forma Invoice* is used depending on some contextual conditions. If these conditions are not met and the state of the document is either `draft` or `sent`, then *Quotation* is used. If none of those conditions are met, the report's title is *Order*." -msgstr "" - -#: ../../content/applications/productivity/studio/pdf_reports.rst:507 -msgid "Working with images in a report can be challenging, as precise control over image size and behavior is not always obvious. You can insert image fields using the report editor (:ref:`by using the /Field command `), but inserting them in XML using the `t-field` directive and accompanying `t-options` attributes provides better sizing and positioning control." -msgstr "" - -#: ../../content/applications/productivity/studio/pdf_reports.rst:513 -msgid "For example, the following code outputs the field `image_128` of the line's product as a 64px-wide image (with an automatic height based on the image's aspect ratio)." -msgstr "" - -#: ../../content/applications/productivity/studio/pdf_reports.rst:520 -msgid "The following options are available for image widgets:" -msgstr "" - -#: ../../content/applications/productivity/studio/pdf_reports.rst:522 -msgid "`width`: width of the image, usually in pixels or CSS length units (e.g., `rem`) (leave empty for auto-width)." -msgstr "" - -#: ../../content/applications/productivity/studio/pdf_reports.rst:524 -msgid "`height`: height of the image, usually in pixels or CSS length units (e.g., `rem`) (leave empty for auto-height)." -msgstr "" - -#: ../../content/applications/productivity/studio/pdf_reports.rst:526 -msgid "`class`: CSS classes applied on the `img` tag; `Bootstrap classes `_ are available." -msgstr "" - -#: ../../content/applications/productivity/studio/pdf_reports.rst:528 -msgid "`alt`: alternative text of the image" -msgstr "" - -#: ../../content/applications/productivity/studio/pdf_reports.rst:529 -msgid "`style`: style attribute; it allows you to override styles more freely than with `Bootstrap classes `_." -msgstr "" - -#: ../../content/applications/productivity/studio/pdf_reports.rst:532 -msgid "These attributes must contain strings, i.e., text enclosed within quotes within quotes, e.g., `t-options-width=\"'64px'\"` (or, alternatively, a valid Python expression)." -msgstr "" - -#: ../../content/applications/productivity/studio/pdf_reports.rst:536 -msgid "The image widget cannot be used on an `img` tag. Instead, set the `t-field` directive on a `span` (for inline content) or `div` (for block content) node." -msgstr "" - -#: ../../content/applications/productivity/studio/pdf_reports.rst:539 -msgid "For example, let's add a column with the product image in the quotation table:" -msgstr "" - -#: ../../content/applications/productivity/studio/pdf_reports.rst:567 -msgid "The `t-options-width` attribute restricts the image width to 64 pixels, and the Bootstrap classes used in `t-options-class` create a thumbnail-like border with rounded corners and a shadow." -msgstr "" - -#: ../../content/applications/productivity/studio/pdf_reports.rst:0 -msgid "Add a column with the product image in the quotation table." -msgstr "" - -#: ../../content/applications/productivity/studio/views.rst:3 -msgid "Views" -msgstr "" - -#: ../../content/applications/productivity/studio/views.rst:5 -msgid "Views are the interface that allows displaying the data contained in a model. One model can have several views, which are simply different ways to show the same data. In Studio, views are organized into four categories: :ref:`general `, :ref:`multiple records `, :ref:`timeline `, and :ref:`reporting `." -msgstr "" - -#: ../../content/applications/productivity/studio/views.rst:12 -msgid "To change the default view of a model, go to :menuselection:`Studio --> Views --> Dropdown menu (⋮) --> Set as Default`." -msgstr "" - -#: ../../content/applications/productivity/studio/views.rst:16 -msgid "You can modify views by using the built-in XML editor. To do so, activate :ref:`Developer mode `, go to the view you want to edit, select the :guilabel:`View` tab and then click on :guilabel:` XML`." -msgstr "" - -#: ../../content/applications/productivity/studio/views.rst:21 -msgid "If you are editing a view using the XML editor, avoid making changes directly to standard views and inherited views, as those would be reset and would not be kept in case of an update or module upgrade. Always make sure you select the right Studio inherited views. Indeed, when you modify a view in Studio by drag-and-dropping a new field, a specific Studio inherited view and its XPath, the latter which defines which part of the view is modified, are automatically generated." -msgstr "" - -#: ../../content/applications/productivity/studio/views.rst:31 -msgid "General views" -msgstr "" - -#: ../../content/applications/productivity/studio/views.rst:34 -#: ../../content/applications/productivity/studio/views.rst:97 -#: ../../content/applications/productivity/studio/views.rst:195 -#: ../../content/applications/productivity/studio/views.rst:311 -msgid "The settings described below are found under the view's :guilabel:`View` tab unless specified otherwise." -msgstr "" - -#: ../../content/applications/productivity/studio/views.rst:40 -msgid "Form" -msgstr "" - -#: ../../content/applications/productivity/studio/views.rst:42 -msgid "The :guilabel:`Form` view is used when creating and editing records, such as contacts, sales orders, products, etc." -msgstr "" - -#: ../../content/applications/productivity/studio/views.rst:45 -msgid "To structure a form, drag-and-drop the :guilabel:`Tabs and Columns` element found under the :guilabel:`+ Add` tab." -msgstr "" - -#: ../../content/applications/productivity/studio/views.rst:47 -#: ../../content/applications/productivity/studio/views.rst:132 -msgid "To prevent users from creating, editing, or deleting records, untick :guilabel:`Can Create`, :guilabel:`Can Edit`, or :guilabel:`Can Delete`." -msgstr "" - -#: ../../content/applications/productivity/studio/views.rst:0 -msgid "Sales order model's Form view" -msgstr "" - -#: ../../content/applications/productivity/studio/views.rst:59 -msgid "Activity" -msgstr "" - -#: ../../content/applications/productivity/studio/views.rst:61 -msgid "The :guilabel:`Activity` view is used to schedule and have an overview of activities (emails, calls, etc.) linked to records." -msgstr "" - -#: ../../content/applications/productivity/studio/views.rst:65 -msgid "This view can only be modified within Studio by editing the XML code." -msgstr "" - -#: ../../content/applications/productivity/studio/views.rst:0 -msgid "Lead/Opportunity model's Activity view" -msgstr "" - -#: ../../content/applications/productivity/studio/views.rst:76 -msgid "Search" -msgstr "" - -#: ../../content/applications/productivity/studio/views.rst:78 -msgid "The :guilabel:`Search` view is added on top of other views to filter, group, and search records." -msgstr "" - -#: ../../content/applications/productivity/studio/views.rst:80 -msgid "To add custom :guilabel:`Filters` and structure them using :guilabel:`Separators`, go to the :guilabel:`+ Add` tab and drag and drop them under :guilabel:`Filters`." -msgstr "" - -#: ../../content/applications/productivity/studio/views.rst:82 -msgid "To add an existing field under the search dropdown menu, go to the :guilabel:`+ Add` tab and drag-and-drop it under :guilabel:`Autocompletion Fields`." -msgstr "" - -#: ../../content/applications/productivity/studio/views.rst:0 -msgid "Project model's Search view on the Kanban view" -msgstr "" - -#: ../../content/applications/productivity/studio/views.rst:94 -msgid "Multiple records views" -msgstr "" - -#: ../../content/applications/productivity/studio/views.rst:103 -msgid "Kanban" -msgstr "" - -#: ../../content/applications/productivity/studio/views.rst:105 -msgid "The :guilabel:`Kanban` view is often used to support business flows by moving records across stages or as an alternative way to display records inside *cards*." -msgstr "" - -#: ../../content/applications/productivity/studio/views.rst:109 -msgid "If the :guilabel:`Kanban` view exists, it is used by default to display data on mobile devices instead of the :ref:`List view `." -msgstr "" - -#: ../../content/applications/productivity/studio/views.rst:112 -msgid "To prevent users from creating new records, untick :guilabel:`Can Create`." -msgstr "" - -#: ../../content/applications/productivity/studio/views.rst:113 -msgid "To create records directly within the view, in a minimalistic form, enable :guilabel:`Quick Create`." -msgstr "" - -#: ../../content/applications/productivity/studio/views.rst:115 -msgid "To change the way records are grouped by default, select a new group under :guilabel:`Default Group by`." -msgstr "" - -#: ../../content/applications/productivity/studio/views.rst:0 -msgid "Project model's Kanban view" -msgstr "" - -#: ../../content/applications/productivity/studio/views.rst:127 -msgid "List" -msgstr "" - -#: ../../content/applications/productivity/studio/views.rst:129 -msgid "The :guilabel:`List` view is used to overview many records at once, look for records, and edit simple records." -msgstr "" - -#: ../../content/applications/productivity/studio/views.rst:134 -msgid "To create and edit records directly within the view, select either :guilabel:`New record on top` or :guilabel:`New record at the bottom` under :guilabel:`Editable`." -msgstr "" - -#: ../../content/applications/productivity/studio/views.rst:138 -msgid "This prevents users from opening records in :ref:`Form view ` from the :guilabel:`List` view." -msgstr "" - -#: ../../content/applications/productivity/studio/views.rst:141 -msgid "To edit several records at once, tick :guilabel:`Enable Mass Editing`." -msgstr "" - -#: ../../content/applications/productivity/studio/views.rst:142 -msgid "To change the way records are sorted by default, select a field under :guilabel:`Sort By`." -msgstr "" - -#: ../../content/applications/productivity/studio/views.rst:145 -msgid "To add a drag handle icon to reorder records manually, add an :ref:`Integer field ` with the :guilabel:`Handle` widget." -msgstr "" - -#: ../../content/applications/productivity/studio/views.rst:0 -msgid "Drag handle icon enabling to sort records manually in List view" -msgstr "" - -#: ../../content/applications/productivity/studio/views.rst:0 -msgid "Sales order model's List view" -msgstr "" - -#: ../../content/applications/productivity/studio/views.rst:161 -msgid "Map" -msgstr "" - -#: ../../content/applications/productivity/studio/views.rst:163 -msgid "The :guilabel:`Map` view is used to display records on a map. For example, it is used in the Field Service app to plan an itinerary between different tasks." -msgstr "" - -#: ../../content/applications/productivity/studio/views.rst:167 -msgid "A :ref:`Many2One field ` linked to the *Contact* model is required to activate the view, as the contact address is used to position records on the map." -msgstr "" - -#: ../../content/applications/productivity/studio/views.rst:170 -msgid "To select which kind of contact should be used on the map, select it under :guilabel:`Contact Field`." -msgstr "" - -#: ../../content/applications/productivity/studio/views.rst:172 -msgid "To hide the name or the address of the record, tick :guilabel:`Hide name` or :guilabel:`Hide Address`." -msgstr "" - -#: ../../content/applications/productivity/studio/views.rst:174 -msgid "To add information from other fields, select them under :guilabel:`Additional Fields`." -msgstr "" - -#: ../../content/applications/productivity/studio/views.rst:175 -msgid "To have a route suggested between the different records, tick :guilabel:`Enable Routing` and select which field should be used to sort records for the routing." -msgstr "" - -#: ../../content/applications/productivity/studio/views.rst:0 -msgid "Task model's Map view" -msgstr "" - -#: ../../content/applications/productivity/studio/views.rst:187 -msgid "Timeline views" -msgstr "" - -#: ../../content/applications/productivity/studio/views.rst:190 -msgid "When you first activate one of the timeline views, you need to select which :ref:`Date ` or :ref:`Date & Time ` fields on your model should be used to define when the records start and stop in order to display them on the view. You can modify the :guilabel:`Start Date Field` and :guilabel:`Stop Date Field` after activating the view." -msgstr "" - -#: ../../content/applications/productivity/studio/views.rst:203 -msgid "The :guilabel:`Calendar` view is used to overview and manage records inside a calendar." -msgstr "" - -#: ../../content/applications/productivity/studio/views.rst:205 -msgid "To create records directly within the view instead of opening the :ref:`Form view `, enable :guilabel:`Quick Create`." -msgstr "" - -#: ../../content/applications/productivity/studio/views.rst:209 -msgid "This only works on specific models that can be *quick-created* using only a *name*. However, most models do not support quick creation and open the :guilabel:`Form` view to fill in the required fields." -msgstr "" - -#: ../../content/applications/productivity/studio/views.rst:213 -msgid "To color records on the calendar, select a field under :guilabel:`Color`. All the records sharing the same value for that field are displayed using the same color." -msgstr "" - -#: ../../content/applications/productivity/studio/views.rst:217 -msgid "As the number of colors is limited, the same color can end up being assigned to different values." -msgstr "" - -#: ../../content/applications/productivity/studio/views.rst:220 -msgid "To display events lasting the whole day at the top of the calendar, select a :ref:`Checkbox field ` that specifies if the event lasts the whole day." -msgstr "" - -#: ../../content/applications/productivity/studio/views.rst:223 -msgid "To choose the default time scale used to display events, select :guilabel:`Day`, :guilabel:`Week`, :guilabel:`Month`, or :guilabel:`Year` under :guilabel:`Default Display Mode`." -msgstr "" - -#: ../../content/applications/productivity/studio/views.rst:227 -msgid "You can also use :guilabel:`Delay Field` to display the duration of the event in hours by selecting a :ref:`Decimal ` or :ref:`Integer ` field on the model which specifies the duration of the event. However, if you set an :guilabel:`End Date Field`, the :guilabel:`Delay Field` will not be taken into account." -msgstr "" - -#: ../../content/applications/productivity/studio/views.rst:0 -msgid "Calendar Event model's Calendar view" -msgstr "" - -#: ../../content/applications/productivity/studio/views.rst:242 -msgid "Cohort" -msgstr "" - -#: ../../content/applications/productivity/studio/views.rst:244 -msgid "The :guilabel:`Cohort` view is used to examine the life cycle of records over a time period. For example, it is used in the Subscriptions app to view the subscriptions' retention rate." -msgstr "" - -#: ../../content/applications/productivity/studio/views.rst:247 -msgid "To display a measure (i.e., the aggregated value of a given field) by default on the view, select a :guilabel:`Measure Field`." -msgstr "" - -#: ../../content/applications/productivity/studio/views.rst:249 -msgid "To choose which time interval is used by default to group results, select :guilabel:`Day`, :guilabel:`Week`, :guilabel:`Month`, or :guilabel:`Year` under :guilabel:`Interval`." -msgstr "" - -#: ../../content/applications/productivity/studio/views.rst:251 -msgid "To change the cohort :guilabel:`Mode`, select either :guilabel:`Retention` :dfn:`the percentage of records staying over a period of time, it starts at 100% and decreases with time` or :guilabel:`Churn` :dfn:`the percentage of records moving out over a period of time - it starts at 0% and increases with time`." -msgstr "" - -#: ../../content/applications/productivity/studio/views.rst:255 -msgid "To change the way the :guilabel:`Timeline` (i.e., the columns) progresses, select either :guilabel:`Forward` (from 0 to +15) or :guilabel:`Backward` (from -15 to 0). For most purposes, the :guilabel:`Forward` timeline is used." -msgstr "" - -#: ../../content/applications/productivity/studio/views.rst:0 -msgid "Subscription model's Cohort view" -msgstr "" - -#: ../../content/applications/productivity/studio/views.rst:268 -msgid "Gantt" -msgstr "" - -#: ../../content/applications/productivity/studio/views.rst:270 -msgid "The :guilabel:`Gantt` view is used to forecast and examine the overall progress of records. Records are represented by a bar under a time scale." -msgstr "" - -#: ../../content/applications/productivity/studio/views.rst:273 -msgid "To prevent users from creating or editing records, untick :guilabel:`Can Create` or :guilabel:`Can Edit`." -msgstr "" - -#: ../../content/applications/productivity/studio/views.rst:275 -msgid "To fill cells in gray whenever a record should not be created there (e.g., on weekends for employees), tick :guilabel:`Display Unavailability`." -msgstr "" - -#: ../../content/applications/productivity/studio/views.rst:279 -msgid "The underlying model must support this feature, and support for it cannot be added using Studio. It is supported for the Project, Time Off, Planning, and Manufacturing apps." -msgstr "" - -#: ../../content/applications/productivity/studio/views.rst:282 -msgid "To show a total row at the bottom, tick :guilabel:`Display Total row`." -msgstr "" - -#: ../../content/applications/productivity/studio/views.rst:283 -msgid "To collapse multiple records in a single row, tick :guilabel:`Collapse First Level`." -msgstr "" - -#: ../../content/applications/productivity/studio/views.rst:284 -msgid "To choose which way records are grouped by default on rows (e.g., per employee or project), select a field under :guilabel:`Default Group by`." -msgstr "" - -#: ../../content/applications/productivity/studio/views.rst:286 -msgid "To define a default time scale to view records, select :guilabel:`Day`, :guilabel:`Week`, :guilabel:`Month`, or :guilabel:`Year` under :guilabel:`Default Scale`." -msgstr "" - -#: ../../content/applications/productivity/studio/views.rst:288 -msgid "To color records on the view, select a field under :guilabel:`Color`. All the records sharing the same value for that field are displayed using the same color." -msgstr "" - -#: ../../content/applications/productivity/studio/views.rst:292 -msgid "As the number of colors is limited, the same color can be assigned to different values." -msgstr "" - -#: ../../content/applications/productivity/studio/views.rst:294 -msgid "To specify with which degree of precision each time scale should be divided by, select :guilabel:`Quarter Hour`, :guilabel:`Half Hour`, or :guilabel:`Hour` under :guilabel:`Day Precision`, :guilabel:`Half Day` or :guilabel:`Day` under :guilabel:`Week Precision`, and :guilabel:`Month Precision`." -msgstr "" - -#: ../../content/applications/productivity/studio/views.rst:0 -msgid "Planning Shift model's Gantt view" -msgstr "" - -#: ../../content/applications/productivity/studio/views.rst:308 -msgid "Reporting views" -msgstr "" - -#: ../../content/applications/productivity/studio/views.rst:317 -msgid "Pivot" -msgstr "" - -#: ../../content/applications/productivity/studio/views.rst:319 -msgid "The :guilabel:`Pivot` view is used to explore and analyze the data contained in records in an interactive manner. It is especially useful to aggregate numeric data, create categories, and drill down the data by expanding and collapsing different levels of data." -msgstr "" - -#: ../../content/applications/productivity/studio/views.rst:323 -msgid "To access all records whose data is aggregated under a cell, tick :guilabel:`Access records from cell`." -msgstr "" - -#: ../../content/applications/productivity/studio/views.rst:325 -msgid "To divide the data into different categories, select field(s) under :guilabel:`Column grouping`, :guilabel:`Row grouping - First level`, or :guilabel:`Row grouping - Second level`." -msgstr "" - -#: ../../content/applications/productivity/studio/views.rst:327 -msgid "To add different types of data to be measured using the view, select a field under :guilabel:`Measures`." -msgstr "" - -#: ../../content/applications/productivity/studio/views.rst:329 -msgid "To display a count of records that made up the aggregated data in a cell, tick :guilabel:`Display count`." -msgstr "" - -#: ../../content/applications/productivity/studio/views.rst:0 -msgid "Purchase Report model's Pivot view" -msgstr "" - -#: ../../content/applications/productivity/studio/views.rst:341 -msgid "Graph" -msgstr "" - -#: ../../content/applications/productivity/studio/views.rst:343 -msgid "The :guilabel:`Graph` view is used to showcase data from records in a bar, line, or pie chart." -msgstr "" - -#: ../../content/applications/productivity/studio/views.rst:345 -msgid "To change the default chart, select :guilabel:`Bar`, :guilabel:`Line`, or :guilabel:`Pie` under :guilabel:`Type`." -msgstr "" - -#: ../../content/applications/productivity/studio/views.rst:347 -msgid "To choose a default data dimension (category), select a field under :guilabel:`First dimension` and, if needed, another under :guilabel:`Second dimension`." -msgstr "" - -#: ../../content/applications/productivity/studio/views.rst:349 -msgid "To select a default type of data to be measured using the view, select a field under :guilabel:`Measure`." -msgstr "" - -#: ../../content/applications/productivity/studio/views.rst:351 -msgid "*For Bar and Line charts only*: To sort the different data categories by their value, select :guilabel:`Ascending` (from lowest to highest value) or :guilabel:`Descending` (from highest to lowest) under :guilabel:`Sorting`." -msgstr "" - -#: ../../content/applications/productivity/studio/views.rst:354 -msgid "*For Bar and Pie charts only*: To access all records whose data is aggregated under a data category on the chart, tick :guilabel:`Access records from graph`." -msgstr "" - -#: ../../content/applications/productivity/studio/views.rst:356 -msgid "*For Bar charts only*: When using two data dimensions (categories), display the two columns on top of each other by default by ticking :guilabel:`Stacked graph`." -msgstr "" - -#: ../../content/applications/productivity/studio/views.rst:0 -msgid "Sales Analysis Report model's Bar chart on Graph view" -msgstr "" - -#: ../../content/applications/productivity/studio/views.rst:368 -msgid "Dashboard" -msgstr "" - -#: ../../content/applications/productivity/studio/views.rst:370 -msgid "The :guilabel:`Dashboard` view is used to display multiple reporting views and key performance indicators. Which elements are displayed on the view depends on the configuration of the other reporting views." -msgstr "" - -#: ../../content/applications/productivity/studio/views.rst:0 -msgid "Sales Analysis Report model's Dashboard view" +#: ../../content/applications/productivity/spreadsheet/templates.rst:137 +msgid "Use the download button under the :guilabel:`Data` column to export a template in JSON format. The file can be imported into another database." msgstr "" #: ../../content/applications/productivity/to_do.rst:3 @@ -6371,6 +2728,3078 @@ msgstr "" msgid "A padlock icon is visible on your private tasks to quickly identify them among your project tasks." msgstr "" +#: ../../content/applications/productivity/voip.rst:7 +msgid "VoIP (Voice over Internet Protocol)" +msgstr "" + +#: ../../content/applications/productivity/voip.rst:10 +msgid "For more information, reference the `Odoo eLearning (video tutorials) on VoIP `_" +msgstr "" + +#: ../../content/applications/productivity/voip/axivox.rst:5 +msgid "Axivox configuration" +msgstr "" + +#: ../../content/applications/productivity/voip/axivox/axivox_config.rst:3 +msgid "VoIP services in Odoo with Axivox" +msgstr "" + +#: ../../content/applications/productivity/voip/axivox/axivox_config.rst:6 +#: ../../content/applications/productivity/voip/onsip.rst:6 +msgid "Introduction" +msgstr "" + +#: ../../content/applications/productivity/voip/axivox/axivox_config.rst:8 +msgid "Odoo VoIP (Voice over Internet Protocol) can be set up to work together with `Axivox `_. In that case, an Asterisk server is **not** necessary, as the infrastructure is hosted and managed by Axivox." +msgstr "" + +#: ../../content/applications/productivity/voip/axivox/axivox_config.rst:12 +msgid "To use this service, `contact Axivox `_ to open an account. Before doing so, verify that Axivox covers the company's area, along with the areas the company's users wish to call." +msgstr "" + +#: ../../content/applications/productivity/voip/axivox/axivox_config.rst:19 +msgid "To configure Axivox in Odoo, go to the :menuselection:`Apps` application, and search for `VoIP`. Then, install the :guilabel:`VoIP` module." +msgstr "" + +#: ../../content/applications/productivity/voip/axivox/axivox_config.rst:22 +msgid "Next, go to :menuselection:`Settings app --> General Settings --> Integrations section`, and fill out the :guilabel:`Asterisk (VoIP)` field:" +msgstr "" + +#: ../../content/applications/productivity/voip/axivox/axivox_config.rst:25 +msgid ":guilabel:`OnSIP Domain`: set the domain created by Axivox for the account (e.g., `yourcompany.axivox.com`)" +msgstr "" + +#: ../../content/applications/productivity/voip/axivox/axivox_config.rst:27 +msgid ":guilabel:`WebSocket`: type in `wss://pabx.axivox.com:3443`" +msgstr "" + +#: ../../content/applications/productivity/voip/axivox/axivox_config.rst:28 +msgid ":guilabel:`VoIP Environment`: set as :guilabel:`Production`" +msgstr "" + +#: ../../content/applications/productivity/voip/axivox/axivox_config.rst:-1 +msgid "Integration of Axivox as VoIP provider in an Odoo database." +msgstr "" + +#: ../../content/applications/productivity/voip/axivox/axivox_config.rst:35 +msgid "Access the domain on the Axivox administrative panel by navigating to `https://manage.axivox.com/ `_. After logging into the portal, go to :menuselection:`Users --> Edit (next to any user) --> SIP Identifiers tab --> Domain`." +msgstr "" + +#: ../../content/applications/productivity/voip/axivox/axivox_config.rst:40 +msgid "Configure VoIP user in Odoo" +msgstr "" + +#: ../../content/applications/productivity/voip/axivox/axivox_config.rst:42 +msgid "Next, the user is configured in Odoo, which **must** take place for every Axivox/Odoo user using VoIP." +msgstr "" + +#: ../../content/applications/productivity/voip/axivox/axivox_config.rst:45 +msgid "In Odoo, go to :menuselection:`Settings app --> Users & Companies --> Users`, then open the desired user's form to configure :abbr:`VoIP (Voice over Internet Protocol)`. Under the :guilabel:`Preferences` tab, fill out the :guilabel:`VOIP Configuration` section:" +msgstr "" + +#: ../../content/applications/productivity/voip/axivox/axivox_config.rst:49 +msgid ":guilabel:`VoIP username` / :guilabel:`Extension number`: (Axivox) :guilabel:`SIP username`" +msgstr "" + +#: ../../content/applications/productivity/voip/axivox/axivox_config.rst:50 +msgid ":guilabel:`OnSip Auth Username`: (Axivox) :guilabel:`SIP username`" +msgstr "" + +#: ../../content/applications/productivity/voip/axivox/axivox_config.rst:51 +msgid ":guilabel:`VoIP Secret`: (Axivox) :guilabel:`SIP Password`" +msgstr "" + +#: ../../content/applications/productivity/voip/axivox/axivox_config.rst:52 +msgid ":guilabel:`Call from another device`: option to always transfer phone calls to handset" +msgstr "" + +#: ../../content/applications/productivity/voip/axivox/axivox_config.rst:53 +msgid ":guilabel:`External device number`: SIP external phone extension" +msgstr "" + +#: ../../content/applications/productivity/voip/axivox/axivox_config.rst:54 +msgid ":guilabel:`Reject incoming calls`: option to reject all incoming calls" +msgstr "" + +#: ../../content/applications/productivity/voip/axivox/axivox_config.rst:55 +msgid ":guilabel:`How to place calls on mobile`: method to make calls on a mobile device" +msgstr "" + +#: ../../content/applications/productivity/voip/axivox/axivox_config.rst:-1 +msgid "Integration of Axivox user in the Odoo user preference." +msgstr "" + +#: ../../content/applications/productivity/voip/axivox/axivox_config.rst:62 +msgid "Access the domain on the Axivox administrative panel by navigating to `https://manage.axivox.com/ `_. After logging into the portal, go to :menuselection:`Users --> Edit (next to the user) --> SIP Identifiers tab --> SIP username / SIP password`." +msgstr "" + +#: ../../content/applications/productivity/voip/axivox/axivox_config.rst:0 +msgid "SIP credentials in the Axivox manager." +msgstr "" + +#: ../../content/applications/productivity/voip/axivox/axivox_config.rst:71 +msgid "When entering the :guilabel:`SIP Password` into the user's :guilabel:`Preferences` tab, this value **must** be typed out manually and **not** pasted in. Pasting in causes a `401 server rejection error`." +msgstr "" + +#: ../../content/applications/productivity/voip/axivox/call_queues.rst:3 +msgid "Call queues" +msgstr "" + +#: ../../content/applications/productivity/voip/axivox/call_queues.rst:5 +msgid "A call queue is a system that organizes and routes incoming calls. When customers call a business, and all of the agents are busy, the call queue lines up the callers in sequential order, based on the time they called in." +msgstr "" + +#: ../../content/applications/productivity/voip/axivox/call_queues.rst:9 +msgid "The callers then wait on hold to be connected to the next available call center agent." +msgstr "" + +#: ../../content/applications/productivity/voip/axivox/call_queues.rst:11 +msgid "Implementing a call queue system reduces stress for employees, and helps build brand trust with customers. Many companies use call queues to set expectations with customers, and to distribute the workload equally amongst employees." +msgstr "" + +#: ../../content/applications/productivity/voip/axivox/call_queues.rst:15 +msgid "This document covers the process required to configure call queues (with advanced settings), as well as how to log into a call queue from the Odoo database." +msgstr "" + +#: ../../content/applications/productivity/voip/axivox/call_queues.rst:19 +msgid ":ref:`voip/axivox/music_on_hold`" +msgstr "" + +#: ../../content/applications/productivity/voip/axivox/call_queues.rst:22 +msgid "Add a queue" +msgstr "" + +#: ../../content/applications/productivity/voip/axivox/call_queues.rst:24 +msgid "To add a call queue in Axivox, navigate to the `Axivox management console `_. In the left menu, click :guilabel:`Queues`. Next, click :guilabel:`Add a queue`. Doing so reveals a blank :guilabel:`New queue` form with various fields to fill out." +msgstr "" + +#: ../../content/applications/productivity/voip/axivox/call_queues.rst:30 +#: ../../content/applications/productivity/whatsapp.rst:273 +#: ../../content/applications/productivity/whatsapp.rst:677 +msgid "Name" +msgstr "" + +#: ../../content/applications/productivity/voip/axivox/call_queues.rst:32 +msgid "Once the :guilabel:`New queue` page appears, enter the :guilabel:`Name` of the queue." +msgstr "" + +#: ../../content/applications/productivity/voip/axivox/call_queues.rst:35 +msgid "Internal extension" +msgstr "" + +#: ../../content/applications/productivity/voip/axivox/call_queues.rst:37 +msgid "Choose an :guilabel:`Internal extension` for the queue. This is a number to be dialed by users of the database to reach the login prompt for the queue." +msgstr "" + +#: ../../content/applications/productivity/voip/axivox/call_queues.rst:41 +msgid "Strategy" +msgstr "" + +#: ../../content/applications/productivity/voip/axivox/call_queues.rst:43 +msgid "Next, is the :guilabel:`Strategy` field. This field determines the call routing of received calls into this queue." +msgstr "" + +#: ../../content/applications/productivity/voip/axivox/call_queues.rst:46 +msgid "The following choices are available in the :guilabel:`Strategy` drop-down menu:" +msgstr "" + +#: ../../content/applications/productivity/voip/axivox/call_queues.rst:48 +msgid ":guilabel:`Call all available agents`" +msgstr "" + +#: ../../content/applications/productivity/voip/axivox/call_queues.rst:49 +msgid ":guilabel:`Calls the agent who has received the call for the longest time`" +msgstr "" + +#: ../../content/applications/productivity/voip/axivox/call_queues.rst:50 +msgid ":guilabel:`Calls the agent who has received the least call`" +msgstr "" + +#: ../../content/applications/productivity/voip/axivox/call_queues.rst:51 +msgid ":guilabel:`Call a random agent`" +msgstr "" + +#: ../../content/applications/productivity/voip/axivox/call_queues.rst:52 +msgid ":guilabel:`Call agents one after the other`" +msgstr "" + +#: ../../content/applications/productivity/voip/axivox/call_queues.rst:53 +msgid ":guilabel:`Call agents one after the other starting with the first in the list`" +msgstr "" + +#: ../../content/applications/productivity/voip/axivox/call_queues.rst:55 +msgid "Choose a strategy that best meets the company's needs for customers in the queue." +msgstr "" + +#: ../../content/applications/productivity/voip/axivox/call_queues.rst:58 +msgid "Maximum waiting time in seconds" +msgstr "" + +#: ../../content/applications/productivity/voip/axivox/call_queues.rst:60 +msgid "In the :guilabel:`Maximum waiting time in seconds` field, determine the longest time a customer waits in the queue before going to a voicemail, or wherever else they are directed to in a dial plan. Enter a time in seconds." +msgstr "" + +#: ../../content/applications/productivity/voip/axivox/call_queues.rst:65 +msgid "Maximum duration of ringing at an agent" +msgstr "" + +#: ../../content/applications/productivity/voip/axivox/call_queues.rst:67 +msgid "In the :guilabel:`Maximum duration of ringing at an agent` field, determine the longest time an individual agent's line rings before moving on to another agent, or moving to the next step in the dial plan. Enter a time in seconds." +msgstr "" + +#: ../../content/applications/productivity/voip/axivox/call_queues.rst:72 +msgid "For more information on dial plans, visit:" +msgstr "" + +#: ../../content/applications/productivity/voip/axivox/call_queues.rst:74 +#: ../../content/applications/productivity/voip/axivox/dynamic_caller_id.rst:36 +msgid ":doc:`dial_plan_basics`" +msgstr "" + +#: ../../content/applications/productivity/voip/axivox/call_queues.rst:75 +#: ../../content/applications/productivity/voip/axivox/dynamic_caller_id.rst:37 +msgid ":doc:`dial_plan_advanced`" +msgstr "" + +#: ../../content/applications/productivity/voip/axivox/call_queues.rst:78 +msgid "Adding agents" +msgstr "" + +#: ../../content/applications/productivity/voip/axivox/call_queues.rst:80 +msgid "The final two fields on the :guilabel:`New queue` form revolve around adding agents. Adding :guilabel:`Static agents` and :guilabel:`Dynamic agents` are two pre-configured methods for adding agents onto the call queue during the configuration." +msgstr "" + +#: ../../content/applications/productivity/voip/axivox/call_queues.rst:87 +msgid "Static agents" +msgstr "" + +#: ../../content/applications/productivity/voip/axivox/call_queues.rst:89 +msgid "When :guilabel:`Static agents` are added, these agents are automatically added to the queue without the need to log in to receive calls." +msgstr "" + +#: ../../content/applications/productivity/voip/axivox/call_queues.rst:95 +msgid "Dynamic agents" +msgstr "" + +#: ../../content/applications/productivity/voip/axivox/call_queues.rst:97 +msgid "When :guilabel:`Dynamic agents` are added, these agents have the ability to log into this queue. They are **not** logged-in automatically, and **must** log in to receive calls." +msgstr "" + +#: ../../content/applications/productivity/voip/axivox/call_queues.rst:100 +msgid "Be sure to :guilabel:`Save` the changes, and click :guilabel:`Apply changes` in the upper-right corner to implement the change in production." +msgstr "" + +#: ../../content/applications/productivity/voip/axivox/call_queues.rst:104 +msgid "Agent connection" +msgstr "" + +#: ../../content/applications/productivity/voip/axivox/call_queues.rst:106 +msgid "There are three ways call agents can connect to an Axivox call queue:" +msgstr "" + +#: ../../content/applications/productivity/voip/axivox/call_queues.rst:108 +msgid "Dynamic agents connect automatically." +msgstr "" + +#: ../../content/applications/productivity/voip/axivox/call_queues.rst:109 +msgid "Manager logs in specific agent(s), via the `Axivox management console `_." +msgstr "" + +#: ../../content/applications/productivity/voip/axivox/call_queues.rst:111 +msgid "Agent connects to the queue in Odoo, via the *VoIP* widget." +msgstr "" + +#: ../../content/applications/productivity/voip/axivox/call_queues.rst:114 +msgid "See the documentation on setting :ref:`voip/axivox/dynamic-agents` in the `Axivox management console `_." +msgstr "" + +#: ../../content/applications/productivity/voip/axivox/call_queues.rst:118 +msgid "Connect via Axivox queue" +msgstr "" + +#: ../../content/applications/productivity/voip/axivox/call_queues.rst:120 +msgid "After the initial configuration of the call queue is completed, with the changes saved and implemented, a manager can log into the `Axivox management console `_ and connect dynamic agents to the queue manually." +msgstr "" + +#: ../../content/applications/productivity/voip/axivox/call_queues.rst:124 +msgid "To connect an agent, click :guilabel:`Queues`, located in the left-hand column. Doing so reveals the :guilabel:`Queues` dashboard, with a few different columns listed:" +msgstr "" + +#: ../../content/applications/productivity/voip/axivox/call_queues.rst:127 +msgid ":guilabel:`Name`: name of the queue." +msgstr "" + +#: ../../content/applications/productivity/voip/axivox/call_queues.rst:128 +msgid ":guilabel:`Extension`: number of the extension to be dialed to reach the queue." +msgstr "" + +#: ../../content/applications/productivity/voip/axivox/call_queues.rst:129 +msgid ":guilabel:`Agent Connection`: number to dial to log into the queue." +msgstr "" + +#: ../../content/applications/productivity/voip/axivox/call_queues.rst:130 +msgid ":guilabel:`Agent disconnection`: number to dial to log out of the queue." +msgstr "" + +#: ../../content/applications/productivity/voip/axivox/call_queues.rst:131 +msgid ":guilabel:`Connected Agents`: name of agent connected to the queue." +msgstr "" + +#: ../../content/applications/productivity/voip/axivox/call_queues.rst:133 +msgid "The following buttons are also available on the :guilabel:`Queues` dashboard:" +msgstr "" + +#: ../../content/applications/productivity/voip/axivox/call_queues.rst:135 +msgid ":guilabel:`Connect an agent`: manually connect an agent to the queue." +msgstr "" + +#: ../../content/applications/productivity/voip/axivox/call_queues.rst:136 +msgid ":guilabel:`Report`: run a report on the queue." +msgstr "" + +#: ../../content/applications/productivity/voip/axivox/call_queues.rst:137 +msgid ":guilabel:`Delete`: delete the queue." +msgstr "" + +#: ../../content/applications/productivity/voip/axivox/call_queues.rst:138 +msgid ":guilabel:`Edit`: make changes to the settings of the queue." +msgstr "" + +#: ../../content/applications/productivity/voip/axivox/call_queues.rst:140 +msgid "When agents are connected to the queue, or are live with a customer, they are displayed under the :guilabel:`Connected Agents` column." +msgstr "" + +#: ../../content/applications/productivity/voip/axivox/call_queues.rst:143 +msgid "If they are static agents, they **always** show up as connected." +msgstr "" + +#: ../../content/applications/productivity/voip/axivox/call_queues.rst:145 +msgid "Connect an agent by clicking the orange button labeled, :guilabel:`Connect an agent`. Then, select the desired agent's name from the drop-down menu, and click :guilabel:`Connect`." +msgstr "" + +#: ../../content/applications/productivity/voip/axivox/call_queues.rst:-1 +msgid "Call queue with connected agents column highlighted and connect an agent and report buttons\n" +"highlighted." +msgstr "" + +#: ../../content/applications/productivity/voip/axivox/call_queues.rst:154 +msgid "For more information on static and dynamic agents, see this documentation:" +msgstr "" + +#: ../../content/applications/productivity/voip/axivox/call_queues.rst:156 +msgid ":ref:`voip/axivox/static-agents`" +msgstr "" + +#: ../../content/applications/productivity/voip/axivox/call_queues.rst:157 +msgid ":ref:`voip/axivox/dynamic-agents`" +msgstr "" + +#: ../../content/applications/productivity/voip/axivox/call_queues.rst:160 +msgid "Report" +msgstr "" + +#: ../../content/applications/productivity/voip/axivox/call_queues.rst:162 +msgid "Click :guilabel:`Report` to check on the reporting for a particular queue, in order to see who connected when, and what phone calls came in and out of the queue. This information is showcased on a separate :guilabel:`Queue report` page, when the green :guilabel:`Report` button is clicked." +msgstr "" + +#: ../../content/applications/productivity/voip/axivox/call_queues.rst:166 +msgid "Reports can be customized by date in the :guilabel:`Period` field, and specified in the :guilabel:`From` and :guilabel:`to` fields. The information can be organized by :guilabel:`Event type`, and :guilabel:`Call ID`." +msgstr "" + +#: ../../content/applications/productivity/voip/axivox/call_queues.rst:170 +msgid "When the custom configurations have been entered, click :guilabel:`Apply`." +msgstr "" + +#: ../../content/applications/productivity/voip/axivox/call_queues.rst:172 +msgid "Each report can be exported to a :abbr:`CSV (comma separated value)` file for further use and analysis, via the :guilabel:`Export to CSV` button." +msgstr "" + +#: ../../content/applications/productivity/voip/axivox/call_queues.rst:175 +msgid "When the :guilabel:`Event type` field is clicked, a drop-down menu appears with the following options:" +msgstr "" + +#: ../../content/applications/productivity/voip/axivox/call_queues.rst:178 +msgid ":guilabel:`The caller quit`" +msgstr "" + +#: ../../content/applications/productivity/voip/axivox/call_queues.rst:179 +msgid ":guilabel:`An agent is connecting`" +msgstr "" + +#: ../../content/applications/productivity/voip/axivox/call_queues.rst:180 +msgid ":guilabel:`An agent is disconnecting`" +msgstr "" + +#: ../../content/applications/productivity/voip/axivox/call_queues.rst:181 +msgid ":guilabel:`The call was terminated (agent hangs up)`" +msgstr "" + +#: ../../content/applications/productivity/voip/axivox/call_queues.rst:182 +msgid ":guilabel:`The call was terminated (caller hangs up)`" +msgstr "" + +#: ../../content/applications/productivity/voip/axivox/call_queues.rst:183 +msgid ":guilabel:`The caller is connected to an agent.`" +msgstr "" + +#: ../../content/applications/productivity/voip/axivox/call_queues.rst:184 +msgid ":guilabel:`Someone is entering the queue`" +msgstr "" + +#: ../../content/applications/productivity/voip/axivox/call_queues.rst:185 +msgid ":guilabel:`The caller exits the queue (no agent is connected)`" +msgstr "" + +#: ../../content/applications/productivity/voip/axivox/call_queues.rst:186 +msgid ":guilabel:`The caller exits the queue (timeout)`" +msgstr "" + +#: ../../content/applications/productivity/voip/axivox/call_queues.rst:187 +msgid ":guilabel:`No one is answering`" +msgstr "" + +#: ../../content/applications/productivity/voip/axivox/call_queues.rst:188 +msgid ":guilabel:`No one is answering, the caller hangs up`" +msgstr "" + +#: ../../content/applications/productivity/voip/axivox/call_queues.rst:189 +msgid ":guilabel:`Transfer`" +msgstr "" + +#: ../../content/applications/productivity/voip/axivox/call_queues.rst:190 +msgid ":guilabel:`Blind Transfer`" +msgstr "" + +#: ../../content/applications/productivity/voip/axivox/call_queues.rst:-1 +msgid "Event types in the Axivox queue reporting feature." +msgstr "" + +#: ../../content/applications/productivity/voip/axivox/call_queues.rst:196 +msgid "There is no limit to how many options can be selected from the :guilabel:`Event type` drop-down menu." +msgstr "" + +#: ../../content/applications/productivity/voip/axivox/call_queues.rst:199 +msgid "Clicking :guilabel:`Check all` selects all the available options from the drop-down menu, and clicking :guilabel:`Uncheck all` removes all selections from the drop-down menu." +msgstr "" + +#: ../../content/applications/productivity/voip/axivox/call_queues.rst:202 +msgid "To select an individual :guilabel:`Event type`, click on the desired option in the drop-down menu." +msgstr "" + +#: ../../content/applications/productivity/voip/axivox/call_queues.rst:-1 +msgid "Axivox queue report with result, event type, and period highlighted." +msgstr "" + +#: ../../content/applications/productivity/voip/axivox/call_queues.rst:209 +msgid "Connect to queue on Odoo" +msgstr "" + +#: ../../content/applications/productivity/voip/axivox/call_queues.rst:211 +msgid "Dynamic agents can connect manually to the Axivox call queue from the Odoo *VoIP* widget, once the *VoIP* app is configured for the individual user in Odoo." +msgstr "" + +#: ../../content/applications/productivity/voip/axivox/call_queues.rst:215 +msgid ":doc:`axivox_config`" +msgstr "" + +#: ../../content/applications/productivity/voip/axivox/call_queues.rst:217 +msgid "To access the Odoo *VoIP* widget, click the :guilabel:`☎️ (phone)` icon in the upper-right corner of the screen, from any window within Odoo." +msgstr "" + +#: ../../content/applications/productivity/voip/axivox/call_queues.rst:221 +msgid "For more information on the Odoo *VoIP* widget, see this documentation: :doc:`../voip_widget`" +msgstr "" + +#: ../../content/applications/productivity/voip/axivox/call_queues.rst:223 +msgid "For an agent to connect to the call queue, simply dial the :guilabel:`Agent connection` number, and press the green call button :guilabel:`📞 (phone)` icon in the *VoIP* widget. Then, the agent hears a short, two-second message indicating the agent is logged in. The call automatically ends (disconnects)." +msgstr "" + +#: ../../content/applications/productivity/voip/axivox/call_queues.rst:228 +msgid "To view the connected agents in a call queue, navigate to the `Axivox management console `_, and click :guilabel:`Queues`, located in the left-hand column." +msgstr "" + +#: ../../content/applications/productivity/voip/axivox/call_queues.rst:231 +msgid "Then, click the green :guilabel:`Refresh` button at the top of the :guilabel:`Connected agents` column. Any agent (static or dynamic) that is connected to the queue currently, appears in the column next to the queue they are logged into." +msgstr "" + +#: ../../content/applications/productivity/voip/axivox/call_queues.rst:235 +msgid "To log out of the queue, open the Odoo *VoIP* widget, dial the :guilabel:`Agent disconnection` number, and press the green call button :guilabel:`📞 (phone)` icon. The agent is disconnected from the queue after a short, two-second message." +msgstr "" + +#: ../../content/applications/productivity/voip/axivox/call_queues.rst:239 +msgid "To manually log a dynamic agent out of a call queue, navigate to the `Axivox management console `_, and click :guilabel:`Queues`, located in the left-hand column. Then, click the green :guilabel:`Refresh` button at the top of the :guilabel:`Connected agents` column." +msgstr "" + +#: ../../content/applications/productivity/voip/axivox/call_queues.rst:243 +msgid "To disconnect an agent manually, click the red :guilabel:`Disconnect` button, and they are immediately disconnected. This can be helpful in situations where agents forget to log out at the end of the day." +msgstr "" + +#: ../../content/applications/productivity/voip/axivox/conference_calls.rst:3 +msgid "Conference calls" +msgstr "" + +#: ../../content/applications/productivity/voip/axivox/conference_calls.rst:5 +msgid "Conference calls help employees connect quickly and efficiently, so matters can be discussed in an open forum of sorts. Attendees can be limited, via a sign-in code. That way, confidential matters stay private." +msgstr "" + +#: ../../content/applications/productivity/voip/axivox/conference_calls.rst:9 +msgid "This document covers the configuration of conference calls in Axivox for use in Odoo *VoIP*." +msgstr "" + +#: ../../content/applications/productivity/voip/axivox/conference_calls.rst:12 +msgid "Add a virtual conference" +msgstr "" + +#: ../../content/applications/productivity/voip/axivox/conference_calls.rst:14 +msgid "To add a virtual conference room, navigate to the `Axivox management console `_. After logging in, click on :guilabel:`Conferences` in the menu on the left." +msgstr "" + +#: ../../content/applications/productivity/voip/axivox/conference_calls.rst:18 +msgid "Next, click the green button labeled, :guilabel:`Add a conference`, and a :guilabel:`New conference` form appears." +msgstr "" + +#: ../../content/applications/productivity/voip/axivox/conference_calls.rst:-1 +#: ../../content/applications/productivity/voip/axivox/conference_calls.rst:-1 +msgid "New conference form on Axivox." +msgstr "" + +#: ../../content/applications/productivity/voip/axivox/conference_calls.rst:25 +msgid "From here, fill in the :guilabel:`Name` field, and set an :guilabel:`Internal extension`." +msgstr "" + +#: ../../content/applications/productivity/voip/axivox/conference_calls.rst:27 +msgid "The internal extension is what everyone in the network uses to quickly dial into the conference call, instead of typing in the whole phone number." +msgstr "" + +#: ../../content/applications/productivity/voip/axivox/conference_calls.rst:31 +msgid "Pick a number between three and five digits long, making it easy to remember and dial." +msgstr "" + +#: ../../content/applications/productivity/voip/axivox/conference_calls.rst:33 +msgid "Next, set the :guilabel:`Access code`, if the conference room requires security. This is a password to get into the conference, once the extension for the conference is dialed. Immediately after dialing the extension, a digital receptionist prompts for the :guilabel:`Access code`." +msgstr "" + +#: ../../content/applications/productivity/voip/axivox/conference_calls.rst:37 +msgid "In the :guilabel:`Administrator extension` field, click the drop-down menu, and select the user's extension that manages the call." +msgstr "" + +#: ../../content/applications/productivity/voip/axivox/conference_calls.rst:40 +msgid "Finally, in the :guilabel:`Wait for the administrator to start the conference` field, click the drop-down menu, and select :guilabel:`Yes` or :guilabel:`No`." +msgstr "" + +#: ../../content/applications/productivity/voip/axivox/conference_calls.rst:43 +msgid "Should the selection be :guilabel:`Yes`, then nobody is allowed to utilize the virtual conference room until the administrator is present, and logged into the conference call." +msgstr "" + +#: ../../content/applications/productivity/voip/axivox/conference_calls.rst:46 +msgid "When all fields are filled in, be sure to :guilabel:`Save` the configuration. Then, click :guilabel:`Apply changes` in the upper-right corner to implement the change in production." +msgstr "" + +#: ../../content/applications/productivity/voip/axivox/conference_calls.rst:49 +msgid "Upon doing so, the conference is added, and the Axivox administrator has the option to :guilabel:`Delete` or :guilabel:`Edit` the conference from the Axivox :guilabel:`Conference` main dashboard." +msgstr "" + +#: ../../content/applications/productivity/voip/axivox/conference_calls.rst:53 +msgid "To invite an Axivox user to a specific conference call, click :guilabel:`Invite` to the right of the desired conference, and proceed to enter the extension or phone number of the invitee in the pop-up window that appears." +msgstr "" + +#: ../../content/applications/productivity/voip/axivox/conference_calls.rst:57 +msgid "Once the extension or number is added into the :guilabel:`Please enter the phone number of the person you want to invite` field, click the green :guilabel:`Invite` button, and the recipient immediately receives a phone call, automatically linking them to the conference." +msgstr "" + +#: ../../content/applications/productivity/voip/axivox/conference_calls.rst:66 +#: ../../content/applications/productivity/voip/axivox/manage_users.rst:32 +msgid "Incoming numbers" +msgstr "" + +#: ../../content/applications/productivity/voip/axivox/conference_calls.rst:68 +msgid "To open a conference to a wider audience, an Axivox conference can be linked to *Incoming numbers*." +msgstr "" + +#: ../../content/applications/productivity/voip/axivox/conference_calls.rst:70 +msgid "To do that, log into the `Axivox management console `_, and click :guilabel:`Incoming numbers` in the menu on the left." +msgstr "" + +#: ../../content/applications/productivity/voip/axivox/conference_calls.rst:73 +msgid "On the :guilabel:`Incoming numbers` dashboard, click :guilabel:`Edit` to the far-right of the :guilabel:`Number` to which the conference should be attached." +msgstr "" + +#: ../../content/applications/productivity/voip/axivox/conference_calls.rst:76 +msgid "Then, under the first field, labeled, :guilabel:`Destination type for voice call`, click the drop-down menu, and select :guilabel:`Conference`." +msgstr "" + +#: ../../content/applications/productivity/voip/axivox/conference_calls.rst:79 +msgid "Next, in the :guilabel:`Conference` field, click the drop-down menu, and select the specific conference that should be attached to this incoming number." +msgstr "" + +#: ../../content/applications/productivity/voip/axivox/conference_calls.rst:82 +msgid "Now, whenever this incoming number is dialed, the caller is let into the conference, if there is not an :guilabel:`Access code` required. If there *is* an :guilabel:`Access code` required, the caller is then prompted to enter the :guilabel:`Access code` to enter the conference." +msgstr "" + +#: ../../content/applications/productivity/voip/axivox/conference_calls.rst:87 +msgid "Start call in Odoo" +msgstr "" + +#: ../../content/applications/productivity/voip/axivox/conference_calls.rst:89 +msgid "Anywhere in the Odoo database, open the *VoIP* widget, by clicking the :guilabel:`☎️ (phone)` icon, located in the upper-right corner. Then, dial the specific extension number for the conference, and click the :guilabel:`📞 (phone)` icon." +msgstr "" + +#: ../../content/applications/productivity/voip/axivox/conference_calls.rst:-1 +msgid "Connecting to a conference extension using the Odoo VoIP widget." +msgstr "" + +#: ../../content/applications/productivity/voip/axivox/conference_calls.rst:97 +msgid "Once the digital receptionist answers, enter the :guilabel:`Access code` (if needed), and press the :guilabel:`# (pound)` icon/key." +msgstr "" + +#: ../../content/applications/productivity/voip/axivox/dial_plan_advanced.rst:3 +msgid "Advanced dial plans" +msgstr "" + +#: ../../content/applications/productivity/voip/axivox/dial_plan_advanced.rst:5 +msgid "Typically, companies have a lot of incoming calls every day, but many do not want their teams to answer calls 24 hours a day, 7 days a week." +msgstr "" + +#: ../../content/applications/productivity/voip/axivox/dial_plan_advanced.rst:8 +msgid "By using Axivox advanced dial plan features, the process can be automated, and routing can be set up for all scenarios. This way, customers are never left waiting, or frustrated, because they cannot get in touch with anyone." +msgstr "" + +#: ../../content/applications/productivity/voip/axivox/dial_plan_advanced.rst:12 +msgid "By utilizing the advanced elements in dial plans, companies can automate call routing for certain days or times, like company holidays. Companies can also allow callers to enter extensions themselves, and get transferred automatically using a digital receptionist. This way, an administrative team does **not** have to be available around the clock." +msgstr "" + +#: ../../content/applications/productivity/voip/axivox/dial_plan_advanced.rst:17 +msgid "There is even the option to route callers, depending on where they are calling from in the world, thus maximizing efficiency." +msgstr "" + +#: ../../content/applications/productivity/voip/axivox/dial_plan_advanced.rst:21 +msgid "For more information on basic dial plans, and how to add elements, visit :doc:`dial_plan_basics`." +msgstr "" + +#: ../../content/applications/productivity/voip/axivox/dial_plan_advanced.rst:24 +msgid "Using a browser add-on for spelling may hinder the use of the visual editor in dial plans. Do **not** use a translator with the Axivox management console." +msgstr "" + +#: ../../content/applications/productivity/voip/axivox/dial_plan_advanced.rst:28 +#: ../../content/applications/productivity/voip/axivox/dial_plan_basics.rst:160 +msgid "Advanced elements" +msgstr "" + +#: ../../content/applications/productivity/voip/axivox/dial_plan_advanced.rst:30 +msgid "In Axivox dial plans (as described in :doc:`dial_plan_basics`), there are two advanced elements that can be used." +msgstr "" + +#: ../../content/applications/productivity/voip/axivox/dial_plan_advanced.rst:33 +#: ../../content/applications/productivity/voip/axivox/dial_plan_basics.rst:164 +msgid ":guilabel:`Record`: recording feature is enabled (requires plan change, enabled in Axivox settings)." +msgstr "" + +#: ../../content/applications/productivity/voip/axivox/dial_plan_advanced.rst:35 +#: ../../content/applications/productivity/voip/axivox/dial_plan_basics.rst:166 +msgid ":guilabel:`Caller ID`: replace the caller ID by the called number or free text." +msgstr "" + +#: ../../content/applications/productivity/voip/axivox/dial_plan_advanced.rst:37 +msgid "To add one of these elements, navigate to the :guilabel:`Dial plans` page, located in the menu on the left side of the `Axivox management console `_." +msgstr "" + +#: ../../content/applications/productivity/voip/axivox/dial_plan_advanced.rst:40 +msgid "Next, click on the :guilabel:`Visual Editor` button to the right of the desired dial plan to edit it. Finally, open the :guilabel:`New element` drop-down menu, select the element, and click :guilabel:`Add`." +msgstr "" + +#: ../../content/applications/productivity/voip/axivox/dial_plan_advanced.rst:-1 +msgid "Visual editor for a dial plan in Axivox, with Add and the dispatcher element highlighted." +msgstr "" + +#: ../../content/applications/productivity/voip/axivox/dial_plan_advanced.rst:48 +#: ../../content/applications/productivity/voip/axivox/dial_plan_advanced.rst:99 +msgid "For more information, visit :ref:`voip/axivox/dial_plans`." +msgstr "" + +#: ../../content/applications/productivity/voip/axivox/dial_plan_advanced.rst:51 +msgid "The :guilabel:`Record` element records calls that are routed through this element, and requires an additional plan change in Axivox." +msgstr "" + +#: ../../content/applications/productivity/voip/axivox/dial_plan_advanced.rst:54 +msgid "To enable recording on Axivox, navigate to :guilabel:`Settings` in the `Axivox management console `_. Then, go to the :guilabel:`Recording` drop-down menu, near the bottom of the page. From there, select :guilabel:`Enabled` from the drop-down menu to enable recording using the :guilabel:`Record` element in a dial plan." +msgstr "" + +#: ../../content/applications/productivity/voip/axivox/dial_plan_advanced.rst:60 +msgid "If the :guilabel:`Recording` drop-down menu is unavailable and unable to change, then consult Axivox to enable the feature." +msgstr "" + +#: ../../content/applications/productivity/voip/axivox/dial_plan_advanced.rst:63 +msgid "The :guilabel:`Caller ID` element allows for the replacement of the caller ID downstream, after routing." +msgstr "" + +#: ../../content/applications/productivity/voip/axivox/dial_plan_advanced.rst:66 +msgid "Upon adding the :guilabel:`Caller ID` element to the dial plan, and double-clicking it to configure it, two options appear." +msgstr "" + +#: ../../content/applications/productivity/voip/axivox/dial_plan_advanced.rst:69 +msgid "The first is a :guilabel:`Free text` field, where any text can be input to replace the caller ID. The second option is :guilabel:`Replace the caller ID by the called number`. This option replaces the caller's ID with the :guilabel:`Incoming number`." +msgstr "" + +#: ../../content/applications/productivity/voip/axivox/dial_plan_advanced.rst:74 +msgid "A company may want to use the :guilabel:`Caller ID` element to replace the :guilabel:`Incoming number`, so employees, or outside transfers, cannot see the number, and information is kept private." +msgstr "" + +#: ../../content/applications/productivity/voip/axivox/dial_plan_advanced.rst:79 +#: ../../content/applications/productivity/voip/axivox/dial_plan_basics.rst:135 +msgid "Basic routing elements" +msgstr "" + +#: ../../content/applications/productivity/voip/axivox/dial_plan_advanced.rst:81 +msgid "Basic routing elements in Axivox dial plans provide extension-based routing. This can be done by adding either a *Menu* to numerically link the dial-by-numbers to an action, or by using a *Digital Receptionist* to automatically route or listen for an extension, based on a key input from the caller." +msgstr "" + +#: ../../content/applications/productivity/voip/axivox/dial_plan_advanced.rst:86 +msgid "The main difference between the two elements is that the *Digital Receptionist* does **not** need to be pre-configured numerically with actions. Instead, it acts as a virtual receptionist." +msgstr "" + +#: ../../content/applications/productivity/voip/axivox/dial_plan_advanced.rst:89 +msgid ":guilabel:`Menu`: add a dial-by-number directory and configured downstream actions (not terminal). For example, a dial-by-numbers function could feature an element, wherein clicking '2' takes the caller to the element linked to '2' on the Menu element in the dial plan." +msgstr "" + +#: ../../content/applications/productivity/voip/axivox/dial_plan_advanced.rst:92 +msgid ":guilabel:`Digital Receptionist`: attach a virtual dispatcher to listen for extensions." +msgstr "" + +#: ../../content/applications/productivity/voip/axivox/dial_plan_advanced.rst:94 +msgid "To add one of these elements, navigate to the :guilabel:`Dial plans` page, located in the menu on the left side of the `Axivox management console `_. Next, click on the :guilabel:`Visual Editor` button to the right of the dial plan, to edit the dial plan. Then, open the :guilabel:`New element` drop-down menu, select the element, and click :guilabel:`Add`." +msgstr "" + +#: ../../content/applications/productivity/voip/axivox/dial_plan_advanced.rst:102 +msgid "Digital receptionist scenario" +msgstr "" + +#: ../../content/applications/productivity/voip/axivox/dial_plan_advanced.rst:104 +msgid "The *Digital Receptionist* element is a listen-feature that accurately routes callers through a dial plan, based on the extension they enter, via the key pad." +msgstr "" + +#: ../../content/applications/productivity/voip/axivox/dial_plan_advanced.rst:107 +msgid "Set a *Digital Receptionist* to eliminate the need of a team, or live receptionist, to be on-call all the time. With that element in place, calls now reach their destination, without a real person interjecting." +msgstr "" + +#: ../../content/applications/productivity/voip/axivox/dial_plan_advanced.rst:111 +msgid "After adding the :guilabel:`Digital Receptionist` element to a dial plan, connect the appropriate endpoints, and double-click on the element to set the :guilabel:`Timeout` on the :guilabel:`receptionist` pop-up window that appears." +msgstr "" + +#: ../../content/applications/productivity/voip/axivox/dial_plan_advanced.rst:115 +msgid "The :guilabel:`Timeout` can be set in `5` second increments, from `5` seconds to `60` seconds." +msgstr "" + +#: ../../content/applications/productivity/voip/axivox/dial_plan_advanced.rst:118 +msgid "The :guilabel:`Digital Receptionist` element **requires** a :guilabel:`Play a file` element on either side of it, to explain what action to take, and when a wrong extension is entered." +msgstr "" + +#: ../../content/applications/productivity/voip/axivox/dial_plan_advanced.rst:122 +msgid "While customizing a dial plan in a :guilabel:`Dialplan Editor` pop-up window, add a :guilabel:`Menu` element, with a :guilabel:`Greeting message` that might read, `Press star to dial an extension`." +msgstr "" + +#: ../../content/applications/productivity/voip/axivox/dial_plan_advanced.rst:126 +msgid "Then, on the :guilabel:`Menu` element, for the :guilabel:`* (star)` option, link a :guilabel:`Play a file` element, that plays an :guilabel:`Audio message` saying, 'Enter the extension of the person you are trying to reach'." +msgstr "" + +#: ../../content/applications/productivity/voip/axivox/dial_plan_advanced.rst:130 +msgid "Following the first :guilabel:`Play a file` element, add the :guilabel:`Digital Receptionist` element, followed by another :guilabel:`Play a file` element, which states, 'That is not a valid extension'." +msgstr "" + +#: ../../content/applications/productivity/voip/axivox/dial_plan_advanced.rst:134 +msgid "This last element is in place to close the loop, should the caller not enter a correct extension." +msgstr "" + +#: ../../content/applications/productivity/voip/axivox/dial_plan_advanced.rst:136 +msgid "Finally, this last :guilabel:`Play a file` element is looped back into the :guilabel:`Menu` element." +msgstr "" + +#: ../../content/applications/productivity/voip/axivox/dial_plan_advanced.rst:0 +msgid "A digital receptionist element highlighted in an example dial plan." +msgstr "" + +#: ../../content/applications/productivity/voip/axivox/dial_plan_advanced.rst:144 +msgid "Dial plan elements can be configured by double-clicking them, and selecting different features of the Axivox console to them." +msgstr "" + +#: ../../content/applications/productivity/voip/axivox/dial_plan_advanced.rst:147 +msgid "For example, an :guilabel:`Audio message` needs to be made, and then selected in a :guilabel:`Play a file` or :guilabel:`Menu` element." +msgstr "" + +#: ../../content/applications/productivity/voip/axivox/dial_plan_advanced.rst:150 +msgid "For more information, see this documentation :ref:`voip/axivox/audio_messages`." +msgstr "" + +#: ../../content/applications/productivity/voip/axivox/dial_plan_advanced.rst:153 +#: ../../content/applications/productivity/voip/axivox/dial_plan_basics.rst:147 +msgid "Advanced routing elements" +msgstr "" + +#: ../../content/applications/productivity/voip/axivox/dial_plan_advanced.rst:155 +msgid "Advanced routing elements route calls automatically as they are received into the incoming number(s). This can be configured using geo-location, whitelisting, or time-based variables. Calls pass through a filter prior to their final destination, and are routed, based on the set variable(s)." +msgstr "" + +#: ../../content/applications/productivity/voip/axivox/dial_plan_advanced.rst:160 +msgid "The following are advanced routing elements:" +msgstr "" + +#: ../../content/applications/productivity/voip/axivox/dial_plan_advanced.rst:162 +msgid ":guilabel:`Dispatcher`: create a call filter to route traffic, based on the geo-location of the caller ID." +msgstr "" + +#: ../../content/applications/productivity/voip/axivox/dial_plan_advanced.rst:164 +msgid ":guilabel:`Access List`: create a tailored access list, with VIP customer preference." +msgstr "" + +#: ../../content/applications/productivity/voip/axivox/dial_plan_advanced.rst:165 +#: ../../content/applications/productivity/voip/axivox/dial_plan_basics.rst:154 +msgid ":guilabel:`Time Condition`: create time conditions to route incoming traffic around holidays, or other sensitive time-frames." +msgstr "" + +#: ../../content/applications/productivity/voip/axivox/dial_plan_advanced.rst:169 +msgid "Whitelisting is a technical term used to create a list of allowed numbers. Conversely, blacklisting is used to create a list of denied numbers." +msgstr "" + +#: ../../content/applications/productivity/voip/axivox/dial_plan_advanced.rst:172 +msgid "To add one of these elements, navigate to the :guilabel:`Dial plans` page, located in the menu on the left side of the `Axivox management console `_. Next, click on the :guilabel:`Visual Editor` button to the right of the dial plan, to edit the dial plan. Then, open the :guilabel:`New element` drop-down menu, select the element, and click :guilabel:`Add`. For more information, visit :ref:`voip/axivox/dial_plans`." +msgstr "" + +#: ../../content/applications/productivity/voip/axivox/dial_plan_advanced.rst:179 +msgid "Dispatcher scenario" +msgstr "" + +#: ../../content/applications/productivity/voip/axivox/dial_plan_advanced.rst:181 +msgid "A *Dispatcher* element is a dial plan feature that directs calls, based on region or geo-location. In most cases, the :guilabel:`Dispatcher` element in a dial plan is linked to the :guilabel:`Start` element, in order to filter or screen calls as they come into an incoming number." +msgstr "" + +#: ../../content/applications/productivity/voip/axivox/dial_plan_advanced.rst:185 +msgid "Double-click the :guilabel:`Dispatcher` element in the :guilabel:`Dialplan Editor` pop-up window to configure it." +msgstr "" + +#: ../../content/applications/productivity/voip/axivox/dial_plan_advanced.rst:188 +msgid "This element checks numbers (routed through this element), according to regular expressions. To add a regular expression, click :guilabel:`Add a line` on the bottom of the :guilabel:`Dispatcher` pop-up window." +msgstr "" + +#: ../../content/applications/productivity/voip/axivox/dial_plan_advanced.rst:192 +msgid "Then, under :guilabel:`Name`, enter a recognizable name to identify this expression. This is the name that appears in the :guilabel:`Dispatcher` element on the dial plan showcased in the :guilabel:`Dialplan Editor` pop-up window." +msgstr "" + +#: ../../content/applications/productivity/voip/axivox/dial_plan_advanced.rst:196 +msgid "In the :guilabel:`Regular expression` field, enter the country code, or area code, which Axivox should route for incoming calls. This is especially helpful when a company would like to filter their customers to certain queues, or users based on the customer's geo-location." +msgstr "" + +#: ../../content/applications/productivity/voip/axivox/dial_plan_advanced.rst:200 +msgid "To specify all numbers behind a certain country code, or area code, include `\\d+` after the country code, or country code + area code." +msgstr "" + +#: ../../content/applications/productivity/voip/axivox/dial_plan_advanced.rst:-1 +msgid "Dispatcher configuration panel, with name, regular expression and add a line highlighted." +msgstr "" + +#: ../../content/applications/productivity/voip/axivox/dial_plan_advanced.rst:208 +msgid "`02\\\\d+`: validates the numbers starting with `02`" +msgstr "" + +#: ../../content/applications/productivity/voip/axivox/dial_plan_advanced.rst:209 +msgid "`00\\\\d+`: validates all numbers beginning with `00`" +msgstr "" + +#: ../../content/applications/productivity/voip/axivox/dial_plan_advanced.rst:210 +msgid "`0052\\\\d+` validates all numbers beginning with `0052` (Mexico country code)" +msgstr "" + +#: ../../content/applications/productivity/voip/axivox/dial_plan_advanced.rst:211 +msgid "`001716\\\\d+`: validates all numbers beginning with `001716` (USA country code + Western New York area code)" +msgstr "" + +#: ../../content/applications/productivity/voip/axivox/dial_plan_advanced.rst:215 +msgid "A regular expression (shortened to \"regex\" or \"regexp\"), sometimes referred to as a \"rational expression,\" is a sequence of characters that specifies a match pattern in text. In other words, a match is made within the given range of numbers." +msgstr "" + +#: ../../content/applications/productivity/voip/axivox/dial_plan_advanced.rst:219 +msgid "When the desired configurations are complete on the :guilabel:`Dispatcher` pop-up window, be sure to click :guilabel:`Save`." +msgstr "" + +#: ../../content/applications/productivity/voip/axivox/dial_plan_advanced.rst:222 +msgid "Upon doing so, the :guilabel:`Dispatcher` element appears with different routes available to configure, based on the :guilabel:`Regular Expressions` that were set." +msgstr "" + +#: ../../content/applications/productivity/voip/axivox/dial_plan_advanced.rst:225 +msgid "Attach these routes to any :guilabel:`New element` in the :guilabel:`Dialplan Editor` pop-up window." +msgstr "" + +#: ../../content/applications/productivity/voip/axivox/dial_plan_advanced.rst:227 +msgid "By default, there is an :guilabel:`Unknown` path that appears on the :guilabel:`Dispatcher` element after setting at least one :guilabel:`Regular Expression`." +msgstr "" + +#: ../../content/applications/productivity/voip/axivox/dial_plan_advanced.rst:230 +msgid "Calls follow this route/path when their number does not match any :guilabel:`Regular Expression` set on the :guilabel:`Dispatcher` element." +msgstr "" + +#: ../../content/applications/productivity/voip/axivox/dial_plan_advanced.rst:-1 +msgid "Dial plan with dispatcher element highlighted." +msgstr "" + +#: ../../content/applications/productivity/voip/axivox/dial_plan_advanced.rst:238 +msgid "Time condition scenario" +msgstr "" + +#: ../../content/applications/productivity/voip/axivox/dial_plan_advanced.rst:240 +msgid "When a :guilabel:`Time Condition` element is added to a dial plan, it has a simple :guilabel:`True` and :guilabel:`False` routing." +msgstr "" + +#: ../../content/applications/productivity/voip/axivox/dial_plan_advanced.rst:243 +msgid "After adding the :guilabel:`Time Condition` element to a dial plan, double-click it to configure the variables. :guilabel:`Hour/Minute`, :guilabel:`Days of the week`, :guilabel:`Day of the month`, and :guilabel:`Month` can all be configured." +msgstr "" + +#: ../../content/applications/productivity/voip/axivox/dial_plan_advanced.rst:247 +msgid "If the time which the caller contacts the incoming number matches the set time conditions, then the :guilabel:`True` path is followed, otherwise the :guilabel:`False` path is followed." +msgstr "" + +#: ../../content/applications/productivity/voip/axivox/dial_plan_advanced.rst:251 +msgid "For a company that is closed yearly for the American Independence Day holiday (July 4th) the following time conditions should be set:" +msgstr "" + +#: ../../content/applications/productivity/voip/axivox/dial_plan_advanced.rst:254 +msgid ":guilabel:`Hour/Minute` - `0:0 to 23:59`" +msgstr "" + +#: ../../content/applications/productivity/voip/axivox/dial_plan_advanced.rst:255 +msgid ":guilabel:`Day of the week` - `All to All`" +msgstr "" + +#: ../../content/applications/productivity/voip/axivox/dial_plan_advanced.rst:256 +msgid ":guilabel:`Day of the month` - `From 4 to 4`" +msgstr "" + +#: ../../content/applications/productivity/voip/axivox/dial_plan_advanced.rst:257 +msgid ":guilabel:`Month` - `July`" +msgstr "" + +#: ../../content/applications/productivity/voip/axivox/dial_plan_advanced.rst:259 +msgid "The :guilabel:`Time Condition` element is especially useful for holidays, weekends, and to set working hours. When a caller reaches a destination where they can be helped, either with a real person or voicemail, this reduces wasted time and hangups." +msgstr "" + +#: ../../content/applications/productivity/voip/axivox/dial_plan_advanced.rst:-1 +msgid "Time condition element set in a dial plan on Axivox. Time condition is highlighted." +msgstr "" + +#: ../../content/applications/productivity/voip/axivox/dial_plan_advanced.rst:268 +msgid "To set the :guilabel:`Timezone` that the :guilabel:`Time Condition` operates under, navigate to `Axivox management console `_, and click :guilabel:`Settings` in the menu on the left. Then, set the :guilabel:`Timezone` using the second field from the bottom, by clicking the drop-down menu." +msgstr "" + +#: ../../content/applications/productivity/voip/axivox/dial_plan_advanced.rst:274 +msgid "Access list scenario" +msgstr "" + +#: ../../content/applications/productivity/voip/axivox/dial_plan_advanced.rst:276 +msgid "An *Access List* element in a dial plan allows for the routing of certain numbers, and disallows (denies) other numbers." +msgstr "" + +#: ../../content/applications/productivity/voip/axivox/dial_plan_advanced.rst:279 +msgid "After adding an :guilabel:`Access List` element to a dial plan, it can be configured by double-clicking on the element directly in the :guilabel:`Dialplan Editor` pop-up window." +msgstr "" + +#: ../../content/applications/productivity/voip/axivox/dial_plan_advanced.rst:282 +msgid "Two fields appear where regular expressions can based in the :guilabel:`Allow` and :guilabel:`Deny` fields of the :guilabel:`Access List` pop-up window." +msgstr "" + +#: ../../content/applications/productivity/voip/axivox/dial_plan_advanced.rst:286 +msgid "For a very important customer, their number can be set in the :guilabel:`Allow` field, and these callers can be sent directly to management." +msgstr "" + +#: ../../content/applications/productivity/voip/axivox/dial_plan_advanced.rst:290 +msgid "A regular expression (shortened to \"regex\" or \"regexp\"), sometimes also referred to as a \"rational expression,\" is a sequence of characters that specifies a match pattern in text." +msgstr "" + +#: ../../content/applications/productivity/voip/axivox/dial_plan_advanced.rst:-1 +msgid "Access list element configuration with the allow/deny fields highlighted." +msgstr "" + +#: ../../content/applications/productivity/voip/axivox/dial_plan_advanced.rst:298 +msgid "`2\\\\d\\\\d`: validates numbers from `200 to 299`" +msgstr "" + +#: ../../content/applications/productivity/voip/axivox/dial_plan_advanced.rst:299 +msgid "`02\\\\d*`: validates all numbers beginning with `02`" +msgstr "" + +#: ../../content/applications/productivity/voip/axivox/dial_plan_advanced.rst:300 +msgid "`0017165551212`: validates the number (`0017165551212`)" +msgstr "" + +#: ../../content/applications/productivity/voip/axivox/dial_plan_advanced.rst:302 +msgid "After setting the :guilabel:`Allow` and :guilabel:`Deny` fields with regular expressions or numbers, click :guilabel:`Save` on the :guilabel:`Access List` pop-up window." +msgstr "" + +#: ../../content/applications/productivity/voip/axivox/dial_plan_advanced.rst:305 +msgid "Then, on the :guilabel:`Access list` element in the dial plan, three paths (or routes) are available to link to further actions." +msgstr "" + +#: ../../content/applications/productivity/voip/axivox/dial_plan_advanced.rst:308 +msgid "Unknown calls can be routed through the regular menu flow by adding a :guilabel:`Menu` element, and connecting it to the :guilabel:`Unknown` path. :guilabel:`Refused` calls can be routed to the :guilabel:`Hang up` element. Lastly, :guilabel:`Authorized` callers can be sent to a specific extension or queue." +msgstr "" + +#: ../../content/applications/productivity/voip/axivox/dial_plan_advanced.rst:-1 +msgid "Access list element highlighted in an example dial plan." +msgstr "" + +#: ../../content/applications/productivity/voip/axivox/dial_plan_advanced.rst:318 +msgid "Switches" +msgstr "" + +#: ../../content/applications/productivity/voip/axivox/dial_plan_advanced.rst:320 +msgid "A *Switch* element in Axivox is a simple activated/deactivated route action." +msgstr "" + +#: ../../content/applications/productivity/voip/axivox/dial_plan_advanced.rst:322 +msgid "These can be activated or chosen quickly, allowing for quick routing changes, without altering the dial plan." +msgstr "" + +#: ../../content/applications/productivity/voip/axivox/dial_plan_advanced.rst:325 +msgid "Alternate routes can be configured, so that in a moments notice, they can be switched to. This could be for new availability, or to adjust traffic flow for any number of reasons." +msgstr "" + +#: ../../content/applications/productivity/voip/axivox/dial_plan_advanced.rst:328 +msgid "Axivox allows for a simple on/off switch, and a multi-switch, which can have several paths to choose from." +msgstr "" + +#: ../../content/applications/productivity/voip/axivox/dial_plan_advanced.rst:331 +msgid ":guilabel:`Switch`: a manual on/off control that can divert traffic, based on whether it is opened (on) or closed (off)." +msgstr "" + +#: ../../content/applications/productivity/voip/axivox/dial_plan_advanced.rst:333 +#: ../../content/applications/productivity/voip/axivox/dial_plan_basics.rst:156 +msgid ":guilabel:`Multi-Switch`: a mechanism to create paths, and turn them on and off, to divert incoming calls." +msgstr "" + +#: ../../content/applications/productivity/voip/axivox/dial_plan_advanced.rst:337 +msgid "Basic switch" +msgstr "" + +#: ../../content/applications/productivity/voip/axivox/dial_plan_advanced.rst:339 +msgid "A :guilabel:`Switch` can be set in the `Axivox management console `_ by navigating to :guilabel:`Switches` in the left menu. To create a new switch click :guilabel:`Add a switch` from the :guilabel:`Switches` dashboard, configure a :guilabel:`Name` for it, and click :guilabel:`Save`." +msgstr "" + +#: ../../content/applications/productivity/voip/axivox/dial_plan_advanced.rst:344 +msgid "Then, toggle the desired switch to either :guilabel:`On` or :guilabel:`Off`, from the :guilabel:`State` column on the :guilabel:`Switches` dashboard." +msgstr "" + +#: ../../content/applications/productivity/voip/axivox/dial_plan_advanced.rst:347 +msgid "This :guilabel:`On` / :guilabel:`Off` state automatically routes traffic in a dial plan, in which this switch is set." +msgstr "" + +#: ../../content/applications/productivity/voip/axivox/dial_plan_advanced.rst:350 +msgid "The traffic travels to the :guilabel:`Active` route when :guilabel:`On` is toggled in the switch. The call traffic travels to the :guilabel:`Inactive` route when :guilabel:`Off` is toggled in the switch." +msgstr "" + +#: ../../content/applications/productivity/voip/axivox/dial_plan_advanced.rst:354 +msgid "Changes can be made on the fly, just be sure to click :guilabel:`Apply changes` to implement the them." +msgstr "" + +#: ../../content/applications/productivity/voip/axivox/dial_plan_advanced.rst:358 +msgid "Add a switch to dial plan" +msgstr "" + +#: ../../content/applications/productivity/voip/axivox/dial_plan_advanced.rst:360 +msgid "To add a :guilabel:`Switch` to a dial plan, navigate to `Axivox management console `_, and click on :guilabel:`Dial plans` in the left menu. Then, click :guilabel:`Visual Editor` next to the desired dial plan to open the :guilabel:`Dialplan Editor` pop-up window." +msgstr "" + +#: ../../content/applications/productivity/voip/axivox/dial_plan_advanced.rst:365 +msgid "Then, from the :guilabel:`New element` drop-down menu, select :guilabel:`Switch`, and then click :guilabel:`Add`. Double-click on the element to further configure the :guilabel:`Switch` element." +msgstr "" + +#: ../../content/applications/productivity/voip/axivox/dial_plan_advanced.rst:-1 +msgid "Switch configuration in a dial plan, with inactive and active routes highlighted." +msgstr "" + +#: ../../content/applications/productivity/voip/axivox/dial_plan_advanced.rst:373 +msgid "Multi-switch" +msgstr "" + +#: ../../content/applications/productivity/voip/axivox/dial_plan_advanced.rst:375 +msgid "A *Multi-Switch* element in Axivox is a switch where multiple paths can be configured, and switched between." +msgstr "" + +#: ../../content/applications/productivity/voip/axivox/dial_plan_advanced.rst:378 +msgid "To configure and set a :guilabel:`Multi-Switch` element, navigate to `Axivox management console `_. Then, click on the :guilabel:`Switches` menu item in the left menu." +msgstr "" + +#: ../../content/applications/productivity/voip/axivox/dial_plan_advanced.rst:381 +msgid "Toggle to the :guilabel:`Multi-switch` tab to create, or set, a pre-configured :guilabel:`Multi-Switch` element." +msgstr "" + +#: ../../content/applications/productivity/voip/axivox/dial_plan_advanced.rst:384 +msgid "To create a new :guilabel:`Multi-Switch`, click :guilabel:`Create new`. Then, enter a :guilabel:`Name` for the element, and then enter the :guilabel:`Available choice`. Enter one :guilabel:`Available choice` per line. Do **not** duplicate any entries." +msgstr "" + +#: ../../content/applications/productivity/voip/axivox/dial_plan_advanced.rst:388 +msgid "Remember to click :guilabel:`Save` when done." +msgstr "" + +#: ../../content/applications/productivity/voip/axivox/dial_plan_advanced.rst:390 +msgid "To select the :guilabel:`State` of the :guilabel:`Multi-Switch`, click the drop-down menu next to the :guilabel:`Multi-Switch` name, under the :guilabel:`Multi-switch` tab on the :guilabel:`Switches` dashboard." +msgstr "" + +#: ../../content/applications/productivity/voip/axivox/dial_plan_advanced.rst:394 +msgid "The :guilabel:`State` chosen is the route that is followed in the dial plan. The :guilabel:`State` can be edited on the fly, just be sure to click :guilabel:`Apply changes`." +msgstr "" + +#: ../../content/applications/productivity/voip/axivox/dial_plan_advanced.rst:398 +msgid "Add a multi-switch to dial plan" +msgstr "" + +#: ../../content/applications/productivity/voip/axivox/dial_plan_advanced.rst:400 +msgid "To add a :guilabel:`Multi-Switch` element to a dial plan, navigate to `Axivox management console `_, and click :guilabel:`Dial plans` in the left menu." +msgstr "" + +#: ../../content/applications/productivity/voip/axivox/dial_plan_advanced.rst:403 +msgid "Then, select or create a dial plan. Next, click :guilabel:`Visual Editor` on the desired dial plan." +msgstr "" + +#: ../../content/applications/productivity/voip/axivox/dial_plan_advanced.rst:405 +msgid "On the :guilabel:`Dialplan Editor` pop-up window that appears, click on the :guilabel:`New element` drop-down menu, and select :guilabel:`Multi-Switch`. Then, click :guilabel:`Add`. Double-click on the element to further configure the :guilabel:`Switch` element." +msgstr "" + +#: ../../content/applications/productivity/voip/axivox/dial_plan_advanced.rst:-1 +msgid "Multi-switch configuration in a dial plan, with chosen route highlighted." +msgstr "" + +#: ../../content/applications/productivity/voip/axivox/dial_plan_basics.rst:3 +msgid "Dial plan basics" +msgstr "" + +#: ../../content/applications/productivity/voip/axivox/dial_plan_basics.rst:5 +msgid "When someone calls a business, they might need to get in contact with customer support, a sales team, or even a person's direct line. The caller might also be in search of some information about the business, such as store hours. Or, they might want to leave a voicemail, so someone from the company can call them back. With dial plans in Axivox, a company can manage how incoming calls like this are handled." +msgstr "" + +#: ../../content/applications/productivity/voip/axivox/dial_plan_basics.rst:11 +msgid "Using proper call architecture through a dial plan, callers get directed to the right people, or to the right information, in a quick, efficient manner." +msgstr "" + +#: ../../content/applications/productivity/voip/axivox/dial_plan_basics.rst:14 +msgid "This document covers the basic configuration of dial plans in Axivox." +msgstr "" + +#: ../../content/applications/productivity/voip/axivox/dial_plan_basics.rst:17 +msgid "For more information on advanced dial plans, visit :doc:`dial_plan_advanced`." +msgstr "" + +#: ../../content/applications/productivity/voip/axivox/dial_plan_basics.rst:20 +msgid "Using a browser add-on for spelling may hinder the use of the visual editor in dial plans. Do not use a translator with the Axivox management console." +msgstr "" + +#: ../../content/applications/productivity/voip/axivox/dial_plan_basics.rst:26 +msgid "Dial plans" +msgstr "" + +#: ../../content/applications/productivity/voip/axivox/dial_plan_basics.rst:28 +msgid "Access dial plans by navigating to `Axivox management console `_, and clicking on :guilabel:`Dial plans` from the menu on the left." +msgstr "" + +#: ../../content/applications/productivity/voip/axivox/dial_plan_basics.rst:31 +msgid "To add a new dial plan from the :guilabel:`Dial plan` page, click the green button labeled, :guilabel:`Add a new dial plan`." +msgstr "" + +#: ../../content/applications/productivity/voip/axivox/dial_plan_basics.rst:35 +msgid "Axivox has no limit to the number of dial plans that can be created. These can be added, and improved upon, at any time. This allows for sandboxes to be created with many different configurations." +msgstr "" + +#: ../../content/applications/productivity/voip/axivox/dial_plan_basics.rst:-1 +msgid "Dial plan dashboard with the edit features and Add a dial plan button highlighted." +msgstr "" + +#: ../../content/applications/productivity/voip/axivox/dial_plan_basics.rst:43 +msgid "To edit an existing dial plan, choose one of the following options to the right of the saved dial plan:" +msgstr "" + +#: ../../content/applications/productivity/voip/axivox/dial_plan_basics.rst:46 +msgid ":guilabel:`Delete`: this action deletes the attached dial plan." +msgstr "" + +#: ../../content/applications/productivity/voip/axivox/dial_plan_basics.rst:47 +msgid ":guilabel:`Edit`: this action allows the user to edit the dial plan." +msgstr "" + +#: ../../content/applications/productivity/voip/axivox/dial_plan_basics.rst:48 +msgid ":guilabel:`Visual Editor`: this action opens a visual editor window, where the dial plan architecture can be viewed and edited." +msgstr "" + +#: ../../content/applications/productivity/voip/axivox/dial_plan_basics.rst:50 +msgid ":guilabel:`Duplicate`: this action duplicates the dial plan, and puts it at the bottom of the list, with an extension of one number (+1) larger than the original extension." +msgstr "" + +#: ../../content/applications/productivity/voip/axivox/dial_plan_basics.rst:54 +msgid "Dialplan editor (visual editor)" +msgstr "" + +#: ../../content/applications/productivity/voip/axivox/dial_plan_basics.rst:56 +msgid "When the :guilabel:`Visual Editor` button is clicked for a dial plan on the :guilabel:`Dial plan` page, a pop-up :guilabel:`Dialplan Editor` window appears." +msgstr "" + +#: ../../content/applications/productivity/voip/axivox/dial_plan_basics.rst:59 +msgid "This pop-up window is the primary place where the architecture, or structure, of the dial plan is configured. In this window, a :abbr:`GUI (graphical user interface)` appears, where various dial plan elements can be configured and linked together." +msgstr "" + +#: ../../content/applications/productivity/voip/axivox/dial_plan_basics.rst:-1 +msgid "Visual editor for an example dial plan, with the new element, Add, and Save buttons\n" +"highlighted." +msgstr "" + +#: ../../content/applications/productivity/voip/axivox/dial_plan_basics.rst:69 +msgid "New dial plans come blank with :guilabel:`New element` options for the user to :guilabel:`Add` and :guilabel:`Save`." +msgstr "" + +#: ../../content/applications/productivity/voip/axivox/dial_plan_basics.rst:72 +msgid "The method for saving in the :guilabel:`Dialplan Editor` is different from saving any other edits in the Axivox management console because the :guilabel:`Save` button **must** be pressed before closing the :menuselection:`Visual editor`." +msgstr "" + +#: ../../content/applications/productivity/voip/axivox/dial_plan_basics.rst:76 +msgid "Then, before these changes can take place on the Axivox platform, the user **must** click :guilabel:`Apply changes` in the upper-right corner of the :guilabel:`Dial plan` page." +msgstr "" + +#: ../../content/applications/productivity/voip/axivox/dial_plan_basics.rst:79 +msgid "From the :guilabel:`Dialplan Editor` pop-up window, users can add a new element to the dial plan. To do that, open the :guilabel:`New element` drop-down menu, and select the desired element. Then, click :guilabel:`Add`." +msgstr "" + +#: ../../content/applications/productivity/voip/axivox/dial_plan_basics.rst:83 +msgid "Doing so adds that element to the visual editor display of the dial plan being modified. This element can be moved where desired amongst the other elements present in the dial plan." +msgstr "" + +#: ../../content/applications/productivity/voip/axivox/dial_plan_basics.rst:86 +msgid "Connect elements in the dial plan by clicking and dragging outward from the :guilabel:`(open circle)` icon on the right side of the element. Doing so reveals an :guilabel:`(arrow)` icon. Proceed to drag this :guilabel:`(arrow)` icon to the desired element in the dial plan that it is meant to connect with." +msgstr "" + +#: ../../content/applications/productivity/voip/axivox/dial_plan_basics.rst:91 +msgid "Connect the :guilabel:`(arrow)` icon to the circle on the left side of the desired element." +msgstr "" + +#: ../../content/applications/productivity/voip/axivox/dial_plan_basics.rst:93 +msgid "Calls displayed in the dial plan flow from left-to-right in the element." +msgstr "" + +#: ../../content/applications/productivity/voip/axivox/dial_plan_basics.rst:95 +msgid "In order to further configure a :guilabel:`New element`, double-click on the element inside the dial plan, to reveal a subsequent pop-up window, wherein additional customizations can be entered." +msgstr "" + +#: ../../content/applications/productivity/voip/axivox/dial_plan_basics.rst:98 +msgid "Each element has a different configuration pop-up window that appears when double-clicked." +msgstr "" + +#: ../../content/applications/productivity/voip/axivox/dial_plan_basics.rst:101 +msgid "All elements **must** have a final destination in the dial plan in order to close a loop. This can be accomplished by implementing the :guilabel:`Hang up` element, or looping the element back to a :guilabel:`Menu` element or :guilabel:`Digital Receptionist` element elsewhere in the dial plan." +msgstr "" + +#: ../../content/applications/productivity/voip/axivox/dial_plan_basics.rst:0 +msgid "Dial plan, shown with highlight looping open end back to the beginning of the menu\n" +"element." +msgstr "" + +#: ../../content/applications/productivity/voip/axivox/dial_plan_basics.rst:111 +msgid "Once all desired dial plan elements and configurations are complete, remember to click :guilabel:`Save` before exiting the :guilabel:`Dialplan Editor` pop-up window. Then, click :guilabel:`Apply changes` on the :guilabel:`Dial plans` page to ensure they are implemented into Axivox production." +msgstr "" + +#: ../../content/applications/productivity/voip/axivox/dial_plan_basics.rst:117 +msgid "Dial plan elements" +msgstr "" + +#: ../../content/applications/productivity/voip/axivox/dial_plan_basics.rst:119 +msgid "The following elements are available in the :guilabel:`New element` drop-down menu, while designing a dial plan in the :guilabel:`Dialplan Editor` pop-up window." +msgstr "" + +#: ../../content/applications/productivity/voip/axivox/dial_plan_basics.rst:123 +msgid "Basic elements" +msgstr "" + +#: ../../content/applications/productivity/voip/axivox/dial_plan_basics.rst:125 +msgid "These are the basic elements that are used in simple dial plans in Axivox:" +msgstr "" + +#: ../../content/applications/productivity/voip/axivox/dial_plan_basics.rst:127 +msgid ":guilabel:`Call`: call an extension or queue." +msgstr "" + +#: ../../content/applications/productivity/voip/axivox/dial_plan_basics.rst:128 +msgid ":guilabel:`Play a file`: play an audio file or voice greeting." +msgstr "" + +#: ../../content/applications/productivity/voip/axivox/dial_plan_basics.rst:129 +msgid ":guilabel:`Voicemail`: forward to a voicemail (terminal)." +msgstr "" + +#: ../../content/applications/productivity/voip/axivox/dial_plan_basics.rst:130 +msgid ":guilabel:`Hang up`: hang up the call (terminal)." +msgstr "" + +#: ../../content/applications/productivity/voip/axivox/dial_plan_basics.rst:131 +msgid ":guilabel:`Queue`: attach a call queue with a group of users to answer a call." +msgstr "" + +#: ../../content/applications/productivity/voip/axivox/dial_plan_basics.rst:132 +msgid ":guilabel:`Conference`: add a conference room for a caller to connect to." +msgstr "" + +#: ../../content/applications/productivity/voip/axivox/dial_plan_basics.rst:137 +msgid "Routing elements change or route the path of a caller, these are some basic routing elements used in Axivox:" +msgstr "" + +#: ../../content/applications/productivity/voip/axivox/dial_plan_basics.rst:140 +msgid ":guilabel:`Menu`: add a dial-by-number directory and configure downstream actions (not terminal)." +msgstr "" + +#: ../../content/applications/productivity/voip/axivox/dial_plan_basics.rst:141 +msgid ":guilabel:`Switch`: attach a manual on/off control that can divert traffic based on whether it is opened (On) or closed (Off)." +msgstr "" + +#: ../../content/applications/productivity/voip/axivox/dial_plan_basics.rst:143 +msgid ":guilabel:`Digital Receptionist`: attach a virtual dispatcher to listen for extensions to connect to." +msgstr "" + +#: ../../content/applications/productivity/voip/axivox/dial_plan_basics.rst:149 +msgid "These are the more advanced elements that route calls in Axivox:" +msgstr "" + +#: ../../content/applications/productivity/voip/axivox/dial_plan_basics.rst:151 +msgid ":guilabel:`Dispatcher`: create a call filter to route traffic based on the geo-location of the caller ID." +msgstr "" + +#: ../../content/applications/productivity/voip/axivox/dial_plan_basics.rst:153 +msgid ":guilabel:`Access List`: create a tailored access list with VIP customer preference." +msgstr "" + +#: ../../content/applications/productivity/voip/axivox/dial_plan_basics.rst:162 +msgid "The following are more advanced elements (not routing) in Axivox:" +msgstr "" + +#: ../../content/applications/productivity/voip/axivox/dial_plan_basics.rst:169 +msgid "Dial plan elements can be configured by double-clicking them, and linking different aspects of the Axivox console to them." +msgstr "" + +#: ../../content/applications/productivity/voip/axivox/dial_plan_basics.rst:173 +msgid "Attach to incoming number" +msgstr "" + +#: ../../content/applications/productivity/voip/axivox/dial_plan_basics.rst:175 +msgid "To attach an existing dial plan to an incoming number, go to `Axivox management console `_ , and click on :guilabel:`Incoming numbers`." +msgstr "" + +#: ../../content/applications/productivity/voip/axivox/dial_plan_basics.rst:178 +msgid "Next, click :guilabel:`Edit` next to the number to which the dial plan should be attached." +msgstr "" + +#: ../../content/applications/productivity/voip/axivox/dial_plan_basics.rst:180 +msgid "Doing so reveals a separate page wherein that number's dial plan can be modified. To do that, select :guilabel:`Dial plan` from the :guilabel:`Destination type for voice call` field drop-down menu. Then, choose the desired dial plan from the :guilabel:`Dial plan` field that appears." +msgstr "" + +#: ../../content/applications/productivity/voip/axivox/dial_plan_basics.rst:184 +msgid "With that in place, that means when that specific number calls in, the configured dial plan is activated, and runs through the prompts to properly route the caller." +msgstr "" + +#: ../../content/applications/productivity/voip/axivox/dial_plan_basics.rst:187 +msgid "Finally, :guilabel:`Save` the changes, and click :guilabel:`Apply changes` in the upper-right corner." +msgstr "" + +#: ../../content/applications/productivity/voip/axivox/dial_plan_basics.rst:191 +msgid "Basic dial plan scenario" +msgstr "" + +#: ../../content/applications/productivity/voip/axivox/dial_plan_basics.rst:193 +msgid "The following showcases a basic dial plan scenario for call routing, where additional elements can be added to expand the setup. This basic dial plan scenario includes the following linked elements :menuselection:`Start --> Play a file --> Menu --> (Hang-up, Calls, Queues, Conferences) --> (Voicemail, Hang-up)`." +msgstr "" + +#: ../../content/applications/productivity/voip/axivox/dial_plan_basics.rst:-1 +msgid "Basic dial plan configuration." +msgstr "" + +#: ../../content/applications/productivity/voip/axivox/dial_plan_basics.rst:203 +msgid "This setup does **not** include any basic or advanced call routing. For more information on call routing, reference this documentation: :doc:`dial_plan_advanced`." +msgstr "" + +#: ../../content/applications/productivity/voip/axivox/dynamic_caller_id.rst:3 +msgid "Dynamic caller ID" +msgstr "" + +#: ../../content/applications/productivity/voip/axivox/dynamic_caller_id.rst:5 +msgid "*Caller ID* identifies the caller when they make a phone call. It allows the recipient of the call to see what number the caller is calling from. Caller ID shows users and clients who is calling, so they can choose to pick up or decline the call." +msgstr "" + +#: ../../content/applications/productivity/voip/axivox/dynamic_caller_id.rst:9 +msgid "Axivox offers a dynamic caller ID option to choose which number is displayed on outgoing calls." +msgstr "" + +#: ../../content/applications/productivity/voip/axivox/dynamic_caller_id.rst:11 +msgid "International numbers can be purchased to do business transactions internationally, via a phone call, from a number that has an area code or country code of the destination being called. By displaying a local number, this can increase customer engagement." +msgstr "" + +#: ../../content/applications/productivity/voip/axivox/dynamic_caller_id.rst:15 +msgid "Some companies have many employees making calls from a call center. These employees are not always available to receive a return phone call from a prospective customer. In this case, :abbr:`VoIP (Voice over Internet Protocol)` can be configured in such a way that dynamic caller ID shows the main company phone number, so any number of employees in the group can answer the call. This way, a call is never missed." +msgstr "" + +#: ../../content/applications/productivity/voip/axivox/dynamic_caller_id.rst:24 +msgid "Default outgoing number" +msgstr "" + +#: ../../content/applications/productivity/voip/axivox/dynamic_caller_id.rst:26 +msgid "In Axivox a *default number* can be set. This is a company's main number. This means, when anyone from the company (user/employee) calls a number outside the company, the default outgoing number shows up automatically on the caller ID." +msgstr "" + +#: ../../content/applications/productivity/voip/axivox/dynamic_caller_id.rst:30 +msgid "If someone from outside the company tries to call back a user/employee, they are then funneled back through the main line (default number). If there is a dial plan set up, they are prompted to make selections. This is especially helpful in cases where employees change positions frequently, or if they leave the company." +msgstr "" + +#: ../../content/applications/productivity/voip/axivox/dynamic_caller_id.rst:39 +msgid "To access the default number, go to the `Axivox management console `_, and log in. Then, click into :guilabel:`Settings` in the left menu, and navigate to :guilabel:`Default outgoing number`." +msgstr "" + +#: ../../content/applications/productivity/voip/axivox/dynamic_caller_id.rst:43 +msgid "From here, change the :guilabel:`Default outgoing number` by clicking the drop-down menu, and making a selection from the incoming phone numbers available on Axivox." +msgstr "" + +#: ../../content/applications/productivity/voip/axivox/dynamic_caller_id.rst:46 +msgid "Be sure to :guilabel:`Save` the changes, then click :guilabel:`Apply changes` in the upper-right corner of the :guilabel:`General Settings` page to implement the change." +msgstr "" + +#: ../../content/applications/productivity/voip/axivox/dynamic_caller_id.rst:49 +msgid "The :guilabel:`Default outgoing number` is what shows up by default in the Axivox management portal. However, the outgoing number can also be configured differently at the user level." +msgstr "" + +#: ../../content/applications/productivity/voip/axivox/dynamic_caller_id.rst:53 +msgid "Users" +msgstr "" + +#: ../../content/applications/productivity/voip/axivox/dynamic_caller_id.rst:55 +msgid "To configure the outgoing number at the user level, log in to the `Axivox management console `_. Next, click :guilabel:`Users` from the menu on the left, and then click :guilabel:`Edit` to the right of the user that is to be configured." +msgstr "" + +#: ../../content/applications/productivity/voip/axivox/dynamic_caller_id.rst:59 +msgid "Under :guilabel:`Outgoing number`, click the drop-down menu to select either the :guilabel:`Default outgoing number` (as specified here: :ref:`voip/axivox/dynamic-caller-id-default`), or any of the incoming numbers on the Axivox account." +msgstr "" + +#: ../../content/applications/productivity/voip/axivox/dynamic_caller_id.rst:63 +msgid "Choosing the :guilabel:`Default` selection in the :guilabel:`Outgoing number` drop-down menu ensures this user has the :guilabel:`Default outgoing number` shown on their caller ID when making calls." +msgstr "" + +#: ../../content/applications/productivity/voip/axivox/dynamic_caller_id.rst:66 +msgid "If a specific number is chosen, and that number is assigned to this user under :guilabel:`Incoming numbers` (in the Axivox console's menu on the left), that means this user has a direct line for customers to reach them." +msgstr "" + +#: ../../content/applications/productivity/voip/axivox/dynamic_caller_id.rst:70 +msgid "Once the desired changes are complete, be sure to click :guilabel:`Save`, then click :guilabel:`Apply changes` in the upper-right corner to implement the change." +msgstr "" + +#: ../../content/applications/productivity/voip/axivox/dynamic_caller_id.rst:74 +msgid "By default, when creating a new user in Axivox, the :guilabel:`Outgoing number` is automatically set to :guilabel:`Default`." +msgstr "" + +#: ../../content/applications/productivity/voip/axivox/dynamic_caller_id.rst:78 +msgid "Advanced options" +msgstr "" + +#: ../../content/applications/productivity/voip/axivox/dynamic_caller_id.rst:80 +msgid "To access the :guilabel:`Advanced options`, navigate to the :guilabel:`Settings` option in the menu on the left of the `Axivox management console `_. Then, click :guilabel:`Advanced options` to the right of :guilabel:`Default outgoing number`." +msgstr "" + +#: ../../content/applications/productivity/voip/axivox/dynamic_caller_id.rst:84 +msgid "By default, there are not any advanced rules set. To create one, click the green :guilabel:`+ (plus)` icon. Doing so reveals a line with two blank fields. From here, different caller IDs can be set up, depending on what location the user/employee is calling from." +msgstr "" + +#: ../../content/applications/productivity/voip/axivox/dynamic_caller_id.rst:88 +msgid "To create a rule, first set the :guilabel:`Destination prefix` in the first empty field. This is the country code, complete with zero(s) in front of it. Then, in the second empty field, select the phone number that should be used for calling out from that country code." +msgstr "" + +#: ../../content/applications/productivity/voip/axivox/dynamic_caller_id.rst:93 +msgid "Check the box for :guilabel:`Apply advanced rules even for users with a default outgoing number configured` to allow these rules to take precedent over all other outgoing configurations." +msgstr "" + +#: ../../content/applications/productivity/voip/axivox/dynamic_caller_id.rst:97 +msgid "The order of the rules can be modified by dragging-and-dropping them into another order. The first matching rule is applied." +msgstr "" + +#: ../../content/applications/productivity/voip/axivox/dynamic_caller_id.rst:101 +msgid "For example, a company wants all users/employees to utilize the configured number for Great Britain when calling from the `0044` country code (Great Britain)." +msgstr "" + +#: ../../content/applications/productivity/voip/axivox/dynamic_caller_id.rst:104 +msgid "To accomplish that, simply type in `0044` into the :guilabel:`Destination prefix` field, and select the number starting with the `+44` country code. Order the rules as necessary, and select the checkbox to supersede all other rules, if needed." +msgstr "" + +#: ../../content/applications/productivity/voip/axivox/dynamic_caller_id.rst:0 +msgid "Advanced options for the default outgoing number." +msgstr "" + +#: ../../content/applications/productivity/voip/axivox/dynamic_caller_id.rst:112 +msgid "Once the desired configurations are complete, be sure to click :guilabel:`Save`, then click :guilabel:`Apply changes` in the upper-right corner to implement the change." +msgstr "" + +#: ../../content/applications/productivity/voip/axivox/manage_users.rst:3 +msgid "Manage users in Axivox" +msgstr "" + +#: ../../content/applications/productivity/voip/axivox/manage_users.rst:5 +msgid "Managing Axivox :abbr:`VoIP (Voice over Internet Protocol)` users is an important part of setting up :abbr:`VoIP (Voice over Internet Protocol)` in an Odoo database. Each Axivox user has a unique name, phone number and/or extension, and a voicemail. This way, they can be reached in a variety of convenient ways." +msgstr "" + +#: ../../content/applications/productivity/voip/axivox/manage_users.rst:10 +msgid "Axivox users are organized in a simple, straightforward way in the Axivox console, so an administrator can manage users quickly and easily." +msgstr "" + +#: ../../content/applications/productivity/voip/axivox/manage_users.rst:14 +msgid "This documentation covers how to configure everything through a provider called, Axivox. Depending on the chosen VoIP provider, the processes to manage users may be different." +msgstr "" + +#: ../../content/applications/productivity/voip/axivox/manage_users.rst:18 +msgid "Overview" +msgstr "" + +#: ../../content/applications/productivity/voip/axivox/manage_users.rst:20 +msgid "Begin at the Axivox management console by navigating to `https://manage.axivox.com `_. Log in with the appropriate administrator credentials." +msgstr "" + +#: ../../content/applications/productivity/voip/axivox/manage_users.rst:24 +msgid "Actions in the Axivox management console **must** be double-saved, in order for the changes to take effect. To save any changes, click :guilabel:`Save` in the individualized changes screen. Then, to implement those changes, click the :guilabel:`Apply Changes` button in the upper-right corner of the console." +msgstr "" + +#: ../../content/applications/productivity/voip/axivox/manage_users.rst:34 +msgid "Incoming numbers are all the numbers a company is paying to use to receive calls." +msgstr "" + +#: ../../content/applications/productivity/voip/axivox/manage_users.rst:36 +msgid "Click on :menuselection:`Incoming numbers` from the menu on the left of the Axivox management console. Doing so reveals the :guilabel:`Incoming numbers` page, where all the incoming numbers are listed, along with their :guilabel:`Destination` and SMS information." +msgstr "" + +#: ../../content/applications/productivity/voip/axivox/manage_users.rst:40 +msgid "The :guilabel:`Destination` determines the action that is taken, or the path the caller follows when dialing said numbers." +msgstr "" + +#: ../../content/applications/productivity/voip/axivox/manage_users.rst:43 +msgid "To edit the :guilabel:`Destination`, click the :guilabel:`Edit` button to the far-right of the incoming number line to be modified. Then, on the :guilabel:`Edit number` page that appears, the :guilabel:`Destination type for voice call` can be changed." +msgstr "" + +#: ../../content/applications/productivity/voip/axivox/manage_users.rst:47 +msgid "The options available in the :guilabel:`Destination type for voice call` drop-down menu are as follows:" +msgstr "" + +#: ../../content/applications/productivity/voip/axivox/manage_users.rst:50 +msgid ":guilabel:`Not configured`" +msgstr "" + +#: ../../content/applications/productivity/voip/axivox/manage_users.rst:51 +msgid ":guilabel:`Extension`" +msgstr "" + +#: ../../content/applications/productivity/voip/axivox/manage_users.rst:52 +msgid ":guilabel:`Dial plan`" +msgstr "" + +#: ../../content/applications/productivity/voip/axivox/manage_users.rst:53 +msgid ":guilabel:`Voicemail`" +msgstr "" + +#: ../../content/applications/productivity/voip/axivox/manage_users.rst:54 +msgid ":guilabel:`Hang up`" +msgstr "" + +#: ../../content/applications/productivity/voip/axivox/manage_users.rst:55 +msgid ":guilabel:`Conference`" +msgstr "" + +#: ../../content/applications/productivity/voip/axivox/manage_users.rst:57 +msgid "Depending on the selection made in the :guilabel:`Destination type for voice call` drop-down menu, a second, selection-specific drop-down menu is populated with further configuration options. Additionally, more fields are revealed, based on the selection made in the :guilabel:`Destination type for voice call` drop-down menu." +msgstr "" + +#: ../../content/applications/productivity/voip/axivox/manage_users.rst:62 +msgid "Once the desired configurations are complete, click :guilabel:`Save`, then click :guilabel:`Apply changes` in the upper-right corner to implement them." +msgstr "" + +#: ../../content/applications/productivity/voip/axivox/manage_users.rst:66 +msgid "New users" +msgstr "" + +#: ../../content/applications/productivity/voip/axivox/manage_users.rst:68 +msgid "Every employee using :abbr:`VoIP (Voice over Internet Protocol)` at the company needs an Axivox user account associated with them." +msgstr "" + +#: ../../content/applications/productivity/voip/axivox/manage_users.rst:71 +msgid "To view existing users in the Axivox management console, click :guilabel:`Users` from the menu on the left of the console. Every user has a :guilabel:`Number`, :guilabel:`Name`, option for a :guilabel:`Voicemail`, and an :guilabel:`Outgoing number` specified." +msgstr "" + +#: ../../content/applications/productivity/voip/axivox/manage_users.rst:75 +msgid "To create a new user in the Axivox console, click :guilabel:`Add a user` to reveal a :guilabel:`New user` form. The following tabs are available for configuring the new user:" +msgstr "" + +#: ../../content/applications/productivity/voip/axivox/manage_users.rst:78 +msgid ":guilabel:`General`: basic information, including the extension of the user, can be set." +msgstr "" + +#: ../../content/applications/productivity/voip/axivox/manage_users.rst:79 +msgid ":guilabel:`Forwardings`: internal forwards on 'no answer' or busy signals." +msgstr "" + +#: ../../content/applications/productivity/voip/axivox/manage_users.rst:80 +msgid ":guilabel:`Follow Me`: external forward configuration." +msgstr "" + +#: ../../content/applications/productivity/voip/axivox/manage_users.rst:81 +msgid ":guilabel:`Keys`: set hot-keys within the :abbr:`VoIP (Voice over Internet Protocol)` system." +msgstr "" + +#: ../../content/applications/productivity/voip/axivox/manage_users.rst:82 +msgid ":guilabel:`SIP Identifiers`: :abbr:`SIP (Session Initiation Protocol)` username and password for external configuration." +msgstr "" + +#: ../../content/applications/productivity/voip/axivox/manage_users.rst:84 +msgid ":guilabel:`Permissions`: set access rights for users in the Axivox management console." +msgstr "" + +#: ../../content/applications/productivity/voip/axivox/manage_users.rst:87 +msgid "General tab" +msgstr "" + +#: ../../content/applications/productivity/voip/axivox/manage_users.rst:89 +msgid "Under the :guilabel:`General` tab of the :guilabel:`New user` form, in the :guilabel:`Extension` field, input an extension that is unique to the user. This is the number internal users dial to reach a specific employee." +msgstr "" + +#: ../../content/applications/productivity/voip/axivox/manage_users.rst:93 +msgid "In the :guilabel:`Name` field, input the employee name." +msgstr "" + +#: ../../content/applications/productivity/voip/axivox/manage_users.rst:95 +msgid "Next, fill out the :guilabel:`Email address of the user` field. A valid email address for the employee should be added here, where the user receives business emails." +msgstr "" + +#: ../../content/applications/productivity/voip/axivox/manage_users.rst:98 +msgid "In the :guilabel:`GSM number` field, enter an alternative number at which the user can be reached. Be sure to include the country code." +msgstr "" + +#: ../../content/applications/productivity/voip/axivox/manage_users.rst:102 +#: ../../content/applications/productivity/voip/onsip.rst:134 +msgid "A country code is a locator code that allows access to the desired country's phone system. The country code is dialed first, prior to the target number. Each country in the world has its own specific country code." +msgstr "" + +#: ../../content/applications/productivity/voip/axivox/manage_users.rst:106 +#: ../../content/applications/productivity/voip/onsip.rst:145 +msgid "For a list of comprehensive country codes, visit: `https://countrycode.org `_." +msgstr "" + +#: ../../content/applications/productivity/voip/axivox/manage_users.rst:-1 +msgid "General tab layout in the Axivox management console." +msgstr "" + +#: ../../content/applications/productivity/voip/axivox/manage_users.rst:113 +msgid "In the :guilabel:`Voicemail` field, select either :guilabel:`Yes` or :guilabel:`No` from the drop-down menu." +msgstr "" + +#: ../../content/applications/productivity/voip/axivox/manage_users.rst:116 +msgid "In the :guilabel:`Directory` field, the administrator has the option to leave it blank, by making no changes, or selecting :guilabel:`Default` from the drop-down menu. The :guilabel:`Directory` is used in the *Digital Receptionist* feature element of a dial-plan." +msgstr "" + +#: ../../content/applications/productivity/voip/axivox/manage_users.rst:120 +msgid "At the bottom of the :guilabel:`General` tab, there are two separate options with selection boxes." +msgstr "" + +#: ../../content/applications/productivity/voip/axivox/manage_users.rst:122 +msgid "The first option is :guilabel:`This user can receive multiple calls at the same time`. By selecting this option, users are able to receive calls when on another call." +msgstr "" + +#: ../../content/applications/productivity/voip/axivox/manage_users.rst:125 +msgid "The second option, :guilabel:`This user must log-in to call`, provides the option to make it mandatory for the user to log in." +msgstr "" + +#: ../../content/applications/productivity/voip/axivox/manage_users.rst:129 +msgid "If a company uses physical VoIP phones on desks, and wants their employees to be able to log in from *any* phone or desk in the office, they would make the selection for :guilabel:`This user must log-in to call`." +msgstr "" + +#: ../../content/applications/productivity/voip/axivox/manage_users.rst:133 +msgid "Once the desired configurations are complete, click :guilabel:`Save`, then click :guilabel:`Apply changes` in the upper-right corner." +msgstr "" + +#: ../../content/applications/productivity/voip/axivox/manage_users.rst:139 +msgid "Forwardings tab" +msgstr "" + +#: ../../content/applications/productivity/voip/axivox/manage_users.rst:141 +msgid "Under the :guilabel:`Forwardings` tab of the :guilabel:`New user` form, a company can decide what happens if someone calls a user, and the call is not answered." +msgstr "" + +#: ../../content/applications/productivity/voip/axivox/manage_users.rst:145 +msgid "Forwardings are disabled when the :guilabel:`Follow Me` option is enabled." +msgstr "" + +#: ../../content/applications/productivity/voip/axivox/manage_users.rst:147 +msgid "For example, under the :guilabel:`Forwarding on no answer` field, when the button for :guilabel:`Add a destination` is selected, the option to add a specific user or phone number is revealed. After entering the :guilabel:`Destination`, a specific time frame can be selected by sliding the :guilabel:`seconds bar` to the desired ring time." +msgstr "" + +#: ../../content/applications/productivity/voip/axivox/manage_users.rst:152 +msgid "Additional :guilabel:`Destinations` can be added on with different ring times." +msgstr "" + +#: ../../content/applications/productivity/voip/axivox/manage_users.rst:155 +msgid "Ring times can be staggered, so the call is forwarded to another user after the first user does not pick up the call. The option to :guilabel:`Send to voicemail as a last resort` is available to the administrator, should the :guilabel:`Destinations` not pick up." +msgstr "" + +#: ../../content/applications/productivity/voip/axivox/manage_users.rst:159 +msgid "Under the :guilabel:`Forwarding on busy` field, an administrator can :guilabel:`Add a destination`. When clicked, they can then set the :guilabel:`Destination` (user) and time frame. Should the original user's :abbr:`VoIP (Voice over Internet Protocol)` extension, or incoming number, be busy, the call is forwarded to the destination(s)." +msgstr "" + +#: ../../content/applications/productivity/voip/axivox/manage_users.rst:-1 +msgid "Manage forwarding calls to different users or phone numbers in the Forwardings tab." +msgstr "" + +#: ../../content/applications/productivity/voip/axivox/manage_users.rst:168 +msgid "When the desired configurations are complete, click :guilabel:`Save`, then click :guilabel:`Apply changes` in the upper-right corner of the page." +msgstr "" + +#: ../../content/applications/productivity/voip/axivox/manage_users.rst:172 +msgid "Follow Me tab" +msgstr "" + +#: ../../content/applications/productivity/voip/axivox/manage_users.rst:174 +msgid "When the :guilabel:`Follow Me` option is selected, under the :guilabel:`Follow Me` tab of the :guilabel:`New user` form, no :menuselection:`Forwardings` can be made." +msgstr "" + +#: ../../content/applications/productivity/voip/axivox/manage_users.rst:177 +msgid "Also, when the :guilabel:`Follow Me` option is selected, the :guilabel:`Add a destination` button can be selected to add users, or a destination phone number, to the original user's account. That way, these added numbers ring when a call is received." +msgstr "" + +#: ../../content/applications/productivity/voip/axivox/manage_users.rst:181 +msgid "After entering the :guilabel:`Destination`, a specific time frame can be made by sliding the :guilabel:`seconds bar` to the desired ring time. Additional :guilabel:`Destinations` can be added with different ring times." +msgstr "" + +#: ../../content/applications/productivity/voip/axivox/manage_users.rst:186 +msgid "The original user's :abbr:`VoIP (Voice over Internet Protocol)` number does **not** ring with this option selected. Ring times can also be staggered, so the call is forwarded to another user after the first user does not pick up the call." +msgstr "" + +#: ../../content/applications/productivity/voip/axivox/manage_users.rst:-1 +msgid "Ring destinations like different users or phone numbers from the Follow Me tab." +msgstr "" + +#: ../../content/applications/productivity/voip/axivox/manage_users.rst:195 +msgid "The Odoo mobile app, or another :abbr:`SIP (Session Initiation Protocol)` mobile client, allows for simultaneous ringing of the user's extension or incoming number. For more information, visit the :doc:`VoIP Mobile Integrations <../devices_integrations>` documentation." +msgstr "" + +#: ../../content/applications/productivity/voip/axivox/manage_users.rst:199 +#: ../../content/applications/productivity/voip/axivox/manage_users.rst:345 +msgid "Once all desired configurations are complete, click :guilabel:`Save`, then click :guilabel:`Apply changes` in the upper-right corner." +msgstr "" + +#: ../../content/applications/productivity/voip/axivox/manage_users.rst:203 +msgid "Keys tab" +msgstr "" + +#: ../../content/applications/productivity/voip/axivox/manage_users.rst:205 +msgid "Under the :guilabel:`Keys` tab of the :guilabel:`New user` form, speed dial actions for the user can be configured. Some more advanced options are available, as well." +msgstr "" + +#: ../../content/applications/productivity/voip/axivox/manage_users.rst:208 +msgid "The following options are available to set to numerical values `1-20`." +msgstr "" + +#: ../../content/applications/productivity/voip/axivox/manage_users.rst:210 +msgid "These actions can be set on each number:" +msgstr "" + +#: ../../content/applications/productivity/voip/axivox/manage_users.rst:212 +msgid ":guilabel:`Not configured`: the default action, which is nothing." +msgstr "" + +#: ../../content/applications/productivity/voip/axivox/manage_users.rst:213 +msgid ":guilabel:`BLF (Busy lamp fields)`: this action shows the status of other users' phones connected to the Axivox phone system. This is primarily used on a desk-phone." +msgstr "" + +#: ../../content/applications/productivity/voip/axivox/manage_users.rst:215 +msgid ":guilabel:`Quick Call`: this action allows for a speed-dial of an external number." +msgstr "" + +#: ../../content/applications/productivity/voip/axivox/manage_users.rst:216 +msgid ":guilabel:`Line`: this action allows the user to call another user." +msgstr "" + +#: ../../content/applications/productivity/voip/axivox/manage_users.rst:217 +msgid ":guilabel:`Switch`: this action allows the user to switch between calls from a desk-phone." +msgstr "" + +#: ../../content/applications/productivity/voip/axivox/manage_users.rst:218 +msgid ":guilabel:`Pickup`: this action allows the user to pick up an incoming call from a desk-phone." +msgstr "" + +#: ../../content/applications/productivity/voip/axivox/manage_users.rst:-1 +msgid "Manage user page with Keys tab highlighted and number 2 key drop-down menu selected (with\n" +"highlight)" +msgstr "" + +#: ../../content/applications/productivity/voip/axivox/manage_users.rst:225 +#: ../../content/applications/productivity/voip/axivox/manage_users.rst:313 +msgid "Once all the desired configurations are complete, click :guilabel:`Save`, then click :guilabel:`Apply changes` in the upper-right corner." +msgstr "" + +#: ../../content/applications/productivity/voip/axivox/manage_users.rst:229 +msgid "Many of the preceding options have secondary options available, as well, that can be used to link a user, or external phone number. These **must** be filled out in conjunction with the initial action." +msgstr "" + +#: ../../content/applications/productivity/voip/axivox/manage_users.rst:234 +msgid "The :guilabel:`Number of keys` field can be changed by entering in the desired numerical value in the :guilabel:`Number of keys` field, located at the top of the :guilabel:`Keys` tab of the :guilabel:`New user` form." +msgstr "" + +#: ../../content/applications/productivity/voip/axivox/manage_users.rst:239 +msgid "SIP Identifiers tab" +msgstr "" + +#: ../../content/applications/productivity/voip/axivox/manage_users.rst:241 +msgid "*SIP*, which stands for Session Initiation Protocol telephony, allows one to make and receive calls through an internet connection. The :guilabel:`SIP Identifiers` tab on the :guilabel:`New user` form, contains credentials needed to configure Axivox users in Odoo and/or a different :abbr:`SIP (Session Initiation Protocol)` mobile client." +msgstr "" + +#: ../../content/applications/productivity/voip/axivox/manage_users.rst:247 +msgid "See the documentation on configuring Axivox, using the SIP identifiers:" +msgstr "" + +#: ../../content/applications/productivity/voip/axivox/manage_users.rst:249 +msgid ":doc:`Use VoIP services in Odoo with Axivox `" +msgstr "" + +#: ../../content/applications/productivity/voip/axivox/manage_users.rst:250 +msgid ":doc:`Axivox Mobile Integrations <../devices_integrations>`" +msgstr "" + +#: ../../content/applications/productivity/voip/axivox/manage_users.rst:252 +msgid "Under the :guilabel:`SIP Identifiers` tab, the :guilabel:`SIP username` field represents the user's information that was entered in the :guilabel:`Extension` field, under the :guilabel:`General` tab." +msgstr "" + +#: ../../content/applications/productivity/voip/axivox/manage_users.rst:255 +msgid "The :guilabel:`Domain` field is assigned to the company by the Axivox representative." +msgstr "" + +#: ../../content/applications/productivity/voip/axivox/manage_users.rst:257 +msgid "The value in the :guilabel:`SIP Password` field is unique for every Axivox user. This value is used to sign into Axivox on Odoo, and for any mobile :abbr:`SIP (Session Initiation Protocol)` clients." +msgstr "" + +#: ../../content/applications/productivity/voip/axivox/manage_users.rst:-1 +msgid "Important credentials used for external configurations of Axivox VoIP." +msgstr "" + +#: ../../content/applications/productivity/voip/axivox/manage_users.rst:264 +msgid "The value listed in the :guilabel:`Address of the proxy server` field is typically: `pabx.axivox.com`, but is subject to change by Axivox, so be sure to check the :guilabel:`SIP Identifiers` tab for the most accurate value." +msgstr "" + +#: ../../content/applications/productivity/voip/axivox/manage_users.rst:268 +msgid "Once all desired configurations have been made, click :guilabel:`Save`, then click :guilabel:`Apply changes` in the upper-right corner." +msgstr "" + +#: ../../content/applications/productivity/voip/axivox/manage_users.rst:272 +msgid "Permissions tab" +msgstr "" + +#: ../../content/applications/productivity/voip/axivox/manage_users.rst:274 +msgid "Under the :guilabel:`Permissions` tab of a :guilabel:`New user` form, a :guilabel:`Username` and :guilabel:`Password` can be entered for the user." +msgstr "" + +#: ../../content/applications/productivity/voip/axivox/manage_users.rst:277 +msgid "Beneath those fields, the following permissions can be granted to Axivox users for portal access:" +msgstr "" + +#: ../../content/applications/productivity/voip/axivox/manage_users.rst:279 +msgid ":guilabel:`User portal access`" +msgstr "" + +#: ../../content/applications/productivity/voip/axivox/manage_users.rst:280 +msgid ":guilabel:`User management`" +msgstr "" + +#: ../../content/applications/productivity/voip/axivox/manage_users.rst:281 +msgid ":guilabel:`Administrator access`" +msgstr "" + +#: ../../content/applications/productivity/voip/axivox/manage_users.rst:282 +msgid ":guilabel:`Phone management`" +msgstr "" + +#: ../../content/applications/productivity/voip/axivox/manage_users.rst:283 +msgid ":guilabel:`User group management`" +msgstr "" + +#: ../../content/applications/productivity/voip/axivox/manage_users.rst:284 +msgid ":guilabel:`Phone number management`" +msgstr "" + +#: ../../content/applications/productivity/voip/axivox/manage_users.rst:285 +msgid ":guilabel:`Dial plan management`" +msgstr "" + +#: ../../content/applications/productivity/voip/axivox/manage_users.rst:286 +msgid ":guilabel:`Pickup group management`" +msgstr "" + +#: ../../content/applications/productivity/voip/axivox/manage_users.rst:287 +msgid ":guilabel:`Switch management`" +msgstr "" + +#: ../../content/applications/productivity/voip/axivox/manage_users.rst:288 +msgid ":guilabel:`Conference management`" +msgstr "" + +#: ../../content/applications/productivity/voip/axivox/manage_users.rst:289 +msgid ":guilabel:`Queue management`" +msgstr "" + +#: ../../content/applications/productivity/voip/axivox/manage_users.rst:290 +msgid ":guilabel:`Voicemail management`" +msgstr "" + +#: ../../content/applications/productivity/voip/axivox/manage_users.rst:291 +msgid ":guilabel:`Audio messages management`" +msgstr "" + +#: ../../content/applications/productivity/voip/axivox/manage_users.rst:292 +msgid ":guilabel:`Music on hold management`" +msgstr "" + +#: ../../content/applications/productivity/voip/axivox/manage_users.rst:293 +msgid ":guilabel:`Directory management`" +msgstr "" + +#: ../../content/applications/productivity/voip/axivox/manage_users.rst:294 +msgid ":guilabel:`Call list`" +msgstr "" + +#: ../../content/applications/productivity/voip/axivox/manage_users.rst:295 +msgid ":guilabel:`Connected user list`" +msgstr "" + +#: ../../content/applications/productivity/voip/axivox/manage_users.rst:296 +msgid ":guilabel:`Global settings`" +msgstr "" + +#: ../../content/applications/productivity/voip/axivox/manage_users.rst:297 +msgid ":guilabel:`Apply changes button`" +msgstr "" + +#: ../../content/applications/productivity/voip/axivox/manage_users.rst:298 +msgid ":guilabel:`Invoice download`" +msgstr "" + +#: ../../content/applications/productivity/voip/axivox/manage_users.rst:299 +msgid ":guilabel:`Invoice details`" +msgstr "" + +#: ../../content/applications/productivity/voip/axivox/manage_users.rst:300 +msgid ":guilabel:`Blacklist management`" +msgstr "" + +#: ../../content/applications/productivity/voip/axivox/manage_users.rst:301 +msgid ":guilabel:`Conference participant management`" +msgstr "" + +#: ../../content/applications/productivity/voip/axivox/manage_users.rst:303 +msgid "To access credentials for the Axivox user portal, navigate to the top of the :menuselection:`Permissions` tab. Then, copy the :guilabel:`Username`, and enter the correct :guilabel:`Password` for the individual user. There is a minimum of 8 characters for a user password." +msgstr "" + +#: ../../content/applications/productivity/voip/axivox/manage_users.rst:309 +msgid "These are the same permissions granted to the Axivox administrator that are listed in the menu on the left in the Axivox management console. Should a selection state :guilabel:`No`, or :guilabel:`No access`, then the menu option does **not** populate for the user." +msgstr "" + +#: ../../content/applications/productivity/voip/axivox/manage_users.rst:316 +msgid "Upon finishing the setup for a new user, an :ref:`voip/axivox/incoming_number` can be linked." +msgstr "" + +#: ../../content/applications/productivity/voip/axivox/manage_users.rst:-1 +msgid "Manage a user page, with the permissions tab highlighted, along with the first permission\n" +"highlighted indicating a no selection." +msgstr "" + +#: ../../content/applications/productivity/voip/axivox/manage_users.rst:326 +msgid "User groups" +msgstr "" + +#: ../../content/applications/productivity/voip/axivox/manage_users.rst:328 +msgid "A user group is a grouping of Axivox users that can be linked to a queue for call center capability." +msgstr "" + +#: ../../content/applications/productivity/voip/axivox/manage_users.rst:331 +msgid "To begin using user groups, navigate to `https://manage.axivox.com `_." +msgstr "" + +#: ../../content/applications/productivity/voip/axivox/manage_users.rst:333 +msgid "Then, log in with the appropriate administrator credentials. From the menu on the left of the Axivox administrative panel, click into :guilabel:`User Groups`." +msgstr "" + +#: ../../content/applications/productivity/voip/axivox/manage_users.rst:336 +msgid "To add a user group from the :guilabel:`User Groups` page, click :guilabel:`Add a group`." +msgstr "" + +#: ../../content/applications/productivity/voip/axivox/manage_users.rst:338 +msgid "Next, name the group, by entering text into the :guilabel:`Name` field. Then, add a member to the group by typing the first few letters of the user's name into the :guilabel:`Members` field. The user populates in a drop-down menu below the field. Then, click on the desired user, and they are added to the user group." +msgstr "" + +#: ../../content/applications/productivity/voip/axivox/manage_users.rst:343 +msgid "Repeat this process to add more users to the group." +msgstr "" + +#: ../../content/applications/productivity/voip/axivox/vm_audio_messages.rst:3 +msgid "Voicemails and audio messages" +msgstr "" + +#: ../../content/applications/productivity/voip/axivox/vm_audio_messages.rst:7 +msgid "Managing voicemail is an important part of any business. A company needs to access their messages with ease, and stay on top of any missed calls. Recording audio messages, like thanking a caller for reaching out, or directing them to the right extension, is also a great way to personalize the business interaction, and set the tone with the customer." +msgstr "" + +#: ../../content/applications/productivity/voip/axivox/vm_audio_messages.rst:12 +msgid "This document covers the configuration of both voicemail and audio messages in the Axivox administrative portal." +msgstr "" + +#: ../../content/applications/productivity/voip/axivox/vm_audio_messages.rst:18 +msgid "Set global language" +msgstr "" + +#: ../../content/applications/productivity/voip/axivox/vm_audio_messages.rst:20 +msgid "To start using voicemails and audio messages with Axivox, the global language should be set in the Axivox admin portal settings. To do that, navigate to `manage.axivox.com `_. After logging into the portal, go to :menuselection:`Settings --> Global language (e.g.: voicemail messages,...)`." +msgstr "" + +#: ../../content/applications/productivity/voip/axivox/vm_audio_messages.rst:25 +msgid "From here, set the language to either: :guilabel:`Francais`, :guilabel:`English`, :guilabel:`Espanol`, or :guilabel:`Deutsch`." +msgstr "" + +#: ../../content/applications/productivity/voip/axivox/vm_audio_messages.rst:28 +msgid "Then, click :guilabel:`Save`, followed by :guilabel:`Apply changes` in the upper-right corner of the :guilabel:`General Settings` page to implement the change into production." +msgstr "" + +#: ../../content/applications/productivity/voip/axivox/vm_audio_messages.rst:34 +msgid "Activate voicemail" +msgstr "" + +#: ../../content/applications/productivity/voip/axivox/vm_audio_messages.rst:36 +msgid "In order for a user to utilize voicemail in Axivox, the voicemail feature **must** be turned on in the Axivox administrative portal. To begin using voicemail with a user, navigate to `manage.axivox.com `_. Then, log in with the appropriate administrator credentials." +msgstr "" + +#: ../../content/applications/productivity/voip/axivox/vm_audio_messages.rst:40 +msgid "On the left menu of the Axivox administrative panel, click into :guilabel:`Users`." +msgstr "" + +#: ../../content/applications/productivity/voip/axivox/vm_audio_messages.rst:42 +msgid "Then, click into the specific user the voicemail should be activated for. Under the section marked, :guilabel:`Voicemail`, open the drop-down menu, and click on :guilabel:`Yes`." +msgstr "" + +#: ../../content/applications/productivity/voip/axivox/vm_audio_messages.rst:45 +msgid "Lastly, :guilabel:`Save` the change, then click :guilabel:`Apply changes` in the upper-right corner of the screen." +msgstr "" + +#: ../../content/applications/productivity/voip/axivox/vm_audio_messages.rst:49 +msgid "Voicemail" +msgstr "" + +#: ../../content/applications/productivity/voip/axivox/vm_audio_messages.rst:51 +msgid "The next step is to set up the individual voicemail boxes on the Axivox administrative portal. To access the portal, visit `manage.axivox.com `_ and log in. Then, navigate to :menuselection:`Voicemails`, located in the menu on the left." +msgstr "" + +#: ../../content/applications/productivity/voip/axivox/vm_audio_messages.rst:55 +msgid "If the voicemail option was activated in the user profile, using this process :ref:`voip/axivox/activate_voicemail`, then a voicemail is automatically created on the :guilabel:`Voicemails` page." +msgstr "" + +#: ../../content/applications/productivity/voip/axivox/vm_audio_messages.rst:60 +msgid "It should be noted that some of the administrative portal language is in French, as Axivox is a Belgian company. The global language is still set to one of the four options as seen here: :ref:`voip/axivox/global_language`." +msgstr "" + +#: ../../content/applications/productivity/voip/axivox/vm_audio_messages.rst:65 +msgid "Manually create voicemail" +msgstr "" + +#: ../../content/applications/productivity/voip/axivox/vm_audio_messages.rst:67 +msgid "To manually create a new voicemail box, click :guilabel:`Add a voicemail` on the :guilabel:`Voicemails` page. Or, edit an existing voicemail box, by clicking :guilabel:`Edit` to the far-right of an existing voicemail box on the :guilabel:`Voicemails` page." +msgstr "" + +#: ../../content/applications/productivity/voip/axivox/vm_audio_messages.rst:72 +msgid "Suppose a sales or support team needs a general voicemail box. The voicemail would need to be created manually, and attached to an incoming number." +msgstr "" + +#: ../../content/applications/productivity/voip/axivox/vm_audio_messages.rst:75 +msgid "The new, manually-created voicemail box should be attached to an incoming number, so it can receive messages. To do so, navigate to :menuselection:`Incoming numbers`, located in the menu on the left. Then, click :guilabel:`Edit` to the far-right of the specific number the voicemail should be linked to." +msgstr "" + +#: ../../content/applications/productivity/voip/axivox/vm_audio_messages.rst:80 +msgid "In the :guilabel:`Destination type for voice call` field, click the drop-down menu, and select :guilabel:`Voicemail`. Then, open the drop-down menu on the next line labeled, :guilabel:`Voicemail`, and select the manually-created voicemail box." +msgstr "" + +#: ../../content/applications/productivity/voip/axivox/vm_audio_messages.rst:85 +msgid "If an incoming number is capable of receiving SMS/text messages, an additional field, :guilabel:`Destination email address for Incoming SMS`, is present." +msgstr "" + +#: ../../content/applications/productivity/voip/axivox/vm_audio_messages.rst:88 +msgid "To determine whether an incoming number is capable of receiving SMS/text messages, click :guilabel:`Incoming numbers` from the menu on the left, then check the :guilabel:`SMS compatible` column for the incoming number." +msgstr "" + +#: ../../content/applications/productivity/voip/axivox/vm_audio_messages.rst:92 +msgid "Then, if applicable, in the field labeled, :guilabel:`Destination email address for Incoming SMS`, enter an email to which incoming text messages sent to the incoming number can be received. Some incoming numbers (US +1) in Axivox are capable of receiving text messages from individuals and automated numbers." +msgstr "" + +#: ../../content/applications/productivity/voip/axivox/vm_audio_messages.rst:97 +msgid "Should this field be left empty, the default destination address is used, instead (as previously set in the beginning of the process for manually creating a voicemail)." +msgstr "" + +#: ../../content/applications/productivity/voip/axivox/vm_audio_messages.rst:100 +msgid "Once all desired configurations are complete, click :guilabel:`Save`, then click :guilabel:`Apply changes` in the upper-right corner of the screen to implement the change into production." +msgstr "" + +#: ../../content/applications/productivity/voip/axivox/vm_audio_messages.rst:104 +#: ../../content/applications/productivity/whatsapp.rst:809 +msgid "Notifications" +msgstr "" + +#: ../../content/applications/productivity/voip/axivox/vm_audio_messages.rst:106 +msgid "Now, whenever a voicemail is received on any of the automatically pre-configured or manually-linked voicemail boxes, an email is sent to the user's email address, as listed in the :guilabel:`Voicemails` page, or in the user's Axivox profile." +msgstr "" + +#: ../../content/applications/productivity/voip/axivox/vm_audio_messages.rst:110 +msgid "This information can be accessed by navigating to :menuselection:`Users` in the left menu, and clicking :guilabel:`Edit` next to the specific user in question." +msgstr "" + +#: ../../content/applications/productivity/voip/axivox/vm_audio_messages.rst:116 +msgid "Forwarding to voicemail" +msgstr "" + +#: ../../content/applications/productivity/voip/axivox/vm_audio_messages.rst:118 +msgid "In Axivox, there are also numerous forwarding settings for a user. To access these forwarding settings, go to `manage.axivox.com `_ and log in." +msgstr "" + +#: ../../content/applications/productivity/voip/axivox/vm_audio_messages.rst:121 +msgid "Next, navigate to :menuselection:`Users`, located in the menu on the left." +msgstr "" + +#: ../../content/applications/productivity/voip/axivox/vm_audio_messages.rst:123 +msgid "From there, click into the specific user the forwarding should be added to. Then, open the :guilabel:`Forwardings` tab." +msgstr "" + +#: ../../content/applications/productivity/voip/axivox/vm_audio_messages.rst:126 +msgid "If the user is busy on another call, or away from the phone, there is an option present in this tab to :guilabel:`Send to voicemail as a last resort`, located in the :guilabel:`Forwarding on no answer` and :guilabel:`Forwarding on busy` fields." +msgstr "" + +#: ../../content/applications/productivity/voip/axivox/vm_audio_messages.rst:-1 +msgid "Send to voicemail as a last resort options highlighted on the Forwardings tab of the user." +msgstr "" + +#: ../../content/applications/productivity/voip/axivox/vm_audio_messages.rst:134 +msgid "If the :guilabel:`Send to voicemail as a last resort` box is ticked, when the forwarding actions stated in each section are not successful, the caller is routed to the voicemail set on the particular user." +msgstr "" + +#: ../../content/applications/productivity/voip/axivox/vm_audio_messages.rst:139 +msgid "For more information on forwarding and transfers, visit :ref:`voip/axivox/forwardings_tab`." +msgstr "" + +#: ../../content/applications/productivity/voip/axivox/vm_audio_messages.rst:141 +msgid "When all the desired configurations are complete, click :guilabel:`Save`, then click :guilabel:`Apply changes` in the upper-right corner of the screen to implement the change." +msgstr "" + +#: ../../content/applications/productivity/voip/axivox/vm_audio_messages.rst:147 +msgid "Audio messages" +msgstr "" + +#: ../../content/applications/productivity/voip/axivox/vm_audio_messages.rst:149 +msgid "It is possible to add audio messages *before* a customer's call is even taken, to inform them about the waiting time for deliveries, the availability of a product, or any other important promotional messages." +msgstr "" + +#: ../../content/applications/productivity/voip/axivox/vm_audio_messages.rst:153 +msgid "To record an audio message in Axivox, navigate to `manage.axivox.com `_ and log in." +msgstr "" + +#: ../../content/applications/productivity/voip/axivox/vm_audio_messages.rst:155 +msgid "Next, click on :guilabel:`Audio messages` in the menu on the left. From the :guilabel:`Audio messages` page, click :guilabel:`Add a message`." +msgstr "" + +#: ../../content/applications/productivity/voip/axivox/vm_audio_messages.rst:158 +msgid "Type in a :guilabel:`Name`, and click :guilabel:`Save`." +msgstr "" + +#: ../../content/applications/productivity/voip/axivox/vm_audio_messages.rst:160 +msgid "Upon clicking :guilabel:`Save`, the browser redirects back to the main :guilabel:`Audio messages` page, where the newly-created message can be found on the list." +msgstr "" + +#: ../../content/applications/productivity/voip/axivox/vm_audio_messages.rst:163 +msgid "There are two different ways to make the audio message. The user could either record the message over the phone, or type the message (in text), and select a computer-generated speaker to read the message." +msgstr "" + +#: ../../content/applications/productivity/voip/axivox/vm_audio_messages.rst:168 +msgid "Record audio message" +msgstr "" + +#: ../../content/applications/productivity/voip/axivox/vm_audio_messages.rst:170 +msgid "To record an audio message over the phone, click the orange button labeled, :guilabel:`Record/Listen`, located to the right of the desired message on the list to record, on the :guilabel:`Audio messages` page." +msgstr "" + +#: ../../content/applications/productivity/voip/axivox/vm_audio_messages.rst:174 +msgid "When clicked, a :guilabel:`Record / listen to a message` pop-up window appears. From here, the message is then recorded, via one of the extensions that is associated with the user. Under :guilabel:`Extension to use for message management` field, click the drop-down menu, and select the extension where Axivox should call to record the message." +msgstr "" + +#: ../../content/applications/productivity/voip/axivox/vm_audio_messages.rst:179 +msgid "Then, click :guilabel:`OK` to begin the call." +msgstr "" + +#: ../../content/applications/productivity/voip/axivox/vm_audio_messages.rst:182 +msgid "The user **must** be active in the production database with :abbr:`VoIP (Voice over Internet Protocol)` configured. To configure :abbr:`VoIP (Voice over Internet Protocol)` for a user, see this documentation: :doc:`axivox_config`." +msgstr "" + +#: ../../content/applications/productivity/voip/axivox/vm_audio_messages.rst:186 +msgid "Upon connecting to the Axivox audio recorder management line, a recorded French-speaking operator provides the following options:" +msgstr "" + +#: ../../content/applications/productivity/voip/axivox/vm_audio_messages.rst:189 +#: ../../content/applications/productivity/voip/axivox/vm_audio_messages.rst:199 +msgid "Press `1` to record a message." +msgstr "" + +#: ../../content/applications/productivity/voip/axivox/vm_audio_messages.rst:190 +#: ../../content/applications/productivity/voip/axivox/vm_audio_messages.rst:200 +msgid "Press `2` to listen to the current message." +msgstr "" + +#: ../../content/applications/productivity/voip/axivox/vm_audio_messages.rst:192 +msgid "Press either `1` or `2`, depending on whether or not there is already a message present in the system for this particular audio message that requires a review, before recording a new one." +msgstr "" + +#: ../../content/applications/productivity/voip/axivox/vm_audio_messages.rst:195 +msgid "Record the new audio message after pressing `1`, then press `#` to end the recording." +msgstr "" + +#: ../../content/applications/productivity/voip/axivox/vm_audio_messages.rst:197 +msgid "The French-speaking operator returns to the line presenting the first set of questions again:" +msgstr "" + +#: ../../content/applications/productivity/voip/axivox/vm_audio_messages.rst:202 +msgid "Press `#` to end the call." +msgstr "" + +#: ../../content/applications/productivity/voip/axivox/vm_audio_messages.rst:205 +msgid "Write audio message" +msgstr "" + +#: ../../content/applications/productivity/voip/axivox/vm_audio_messages.rst:207 +msgid "To type the message, and select a computerized speaker to say the text, navigate to the :menuselection:`Audio messages` in the menu on the left." +msgstr "" + +#: ../../content/applications/productivity/voip/axivox/vm_audio_messages.rst:210 +msgid "From the :guilabel:`Audio messages` page, select the blue button labeled, :guilabel:`Text message`, next to the corresponding audio message :guilabel:`Name` that the message should be attached to." +msgstr "" + +#: ../../content/applications/productivity/voip/axivox/vm_audio_messages.rst:213 +msgid "Doing so reveals a :guilabel:`Convert text to message` pop-up window." +msgstr "" + +#: ../../content/applications/productivity/voip/axivox/vm_audio_messages.rst:215 +msgid "From the :guilabel:`Convert to text message` pop-up window, click the drop-down menu next to the field labeled, :guilabel:`Voice`, and select an option for the :guilabel:`Text` to be read in." +msgstr "" + +#: ../../content/applications/productivity/voip/axivox/vm_audio_messages.rst:218 +msgid "After the :guilabel:`Voice` selection has been made, and the message has been written in the :guilabel:`Text` field, click :guilabel:`Generate` to process the audio file." +msgstr "" + +#: ../../content/applications/productivity/voip/axivox/vm_audio_messages.rst:221 +msgid "The text is read in the same language it is written in the :guilabel:`Text` field. Should the language differ in the :guilabel:`Voice` field, then an accent is used by the computerized speaker." +msgstr "" + +#: ../../content/applications/productivity/voip/axivox/vm_audio_messages.rst:224 +msgid "Finally, when these steps are complete, click :guilabel:`Save` to save the audio message." +msgstr "" + +#: ../../content/applications/productivity/voip/axivox/vm_audio_messages.rst:226 +msgid "To implement the changes, click :guilabel:`Apply changes` in the upper-right corner of the screen." +msgstr "" + +#: ../../content/applications/productivity/voip/axivox/vm_audio_messages.rst:-1 +msgid "Convert text to message window with voice, text, generate button and save highlighted." +msgstr "" + +#: ../../content/applications/productivity/voip/axivox/vm_audio_messages.rst:233 +msgid "To set a greeting or audio message in a dial plan element double-click on the element. This could be a :guilabel:`Play a file` element, or a :guilabel:`Menu` element, in which the caller should encounter an urgent message, or a dial-by-number directory." +msgstr "" + +#: ../../content/applications/productivity/voip/axivox/vm_audio_messages.rst:237 +msgid "For more information on dial plans see this documentation: :doc:`dial_plan_basics` or :doc:`dial_plan_advanced`." +msgstr "" + +#: ../../content/applications/productivity/voip/axivox/vm_audio_messages.rst:243 +msgid "Music on-hold" +msgstr "" + +#: ../../content/applications/productivity/voip/axivox/vm_audio_messages.rst:245 +msgid "Axivox has the option to add custom hold music to the call whenever a caller is waiting for their call to be answered. To add hold music to the Axivox administrative portal, navigate to the `manage.axivox.com `_, and log in." +msgstr "" + +#: ../../content/applications/productivity/voip/axivox/vm_audio_messages.rst:249 +msgid "Then, click on :guilabel:`Music on hold` from the menu on the left, and a :guilabel:`Change the music on hold` pop-up window appears." +msgstr "" + +#: ../../content/applications/productivity/voip/axivox/vm_audio_messages.rst:252 +msgid "On the :guilabel:`Change the music on hold` pop-up window, click the :guilabel:`Choose File` button to select an MP3 (MPEG Audio Layer 3) or WAV (Waveform Audio File Format ) file to be uploaded." +msgstr "" + +#: ../../content/applications/productivity/voip/axivox/vm_audio_messages.rst:256 +msgid "Only :abbr:`MP3 (MPEG Audio Layer 3)` or :abbr:`WAV (Waveform Audio File Format)` files can be uploaded to the Axivox administrative portal." +msgstr "" + +#: ../../content/applications/productivity/voip/axivox/vm_audio_messages.rst:259 +msgid "Once the file is selected, the :guilabel:`Progression` bar shows an upload status. When this activity completes, the window can be closed, by clicking :guilabel:`Close`." +msgstr "" + +#: ../../content/applications/productivity/voip/axivox/vm_audio_messages.rst:262 +msgid "When the desired changes are complete, click :guilabel:`Apply changes` in the upper-right corner of the screen." +msgstr "" + +#: ../../content/applications/productivity/voip/devices_integrations.rst:3 +msgid "Devices and integrations" +msgstr "" + +#: ../../content/applications/productivity/voip/devices_integrations.rst:5 +msgid ":abbr:`VoIP (Voice over Internet Protocol)` can be used on many different devices, such as a computer, tablet, mobile phone, and many more. This is helpful in that it reduces costs, and employees can work from anywhere in the world, so long as they have a broadband internet connection." +msgstr "" + +#: ../../content/applications/productivity/voip/devices_integrations.rst:9 +msgid "Odoo *VoIP* is SIP (Session Initiation Protocol) compatible, which means it can be used with *any* :abbr:`SIP (Session Initiation Protocol)` compatible application." +msgstr "" + +#: ../../content/applications/productivity/voip/devices_integrations.rst:12 +msgid "This document covers the process of setting up Odoo *VoIP* across different devices and integrations." +msgstr "" + +#: ../../content/applications/productivity/voip/devices_integrations.rst:15 +msgid "Odoo is fully-integrated with all Odoo apps, allowing users to click into any app, and schedule a call as an activity in the chatter." +msgstr "" + +#: ../../content/applications/productivity/voip/devices_integrations.rst:19 +msgid "For example, in the *CRM* app, a user can click into an opportunity, and click on :guilabel:`Activities` in the chatter." +msgstr "" + +#: ../../content/applications/productivity/voip/devices_integrations.rst:22 +msgid "Next, they can choose :guilabel:`Call`, and under :guilabel:`Due Date`, they can select a date." +msgstr "" + +#: ../../content/applications/productivity/voip/devices_integrations.rst:24 +msgid "Once they click :guilabel:`Save`, an activity shows up in the chatter." +msgstr "" + +#: ../../content/applications/productivity/voip/devices_integrations.rst:26 +msgid "Should the :guilabel:`Due Date` be for today's date, the activity shows up in the :abbr:`VoIP (Voice over Internet Protocol)` widget." +msgstr "" + +#: ../../content/applications/productivity/voip/devices_integrations.rst:0 +msgid "View of CRM leads and the option to schedule an activity for Odoo Discuss." +msgstr "" + +#: ../../content/applications/productivity/voip/devices_integrations.rst:34 +msgid "Odoo VoIP (laptop/desktop computer)" +msgstr "" + +#: ../../content/applications/productivity/voip/devices_integrations.rst:36 +msgid "The Odoo *VoIP* (Voice over Internet Protocol) module and widget can be used from any browser on a laptop or desktop device. Simply click on the :guilabel:`☎️ (phone)` icon in the upper-right corner, while in the Odoo database, and the widget appears." +msgstr "" + +#: ../../content/applications/productivity/voip/devices_integrations.rst:41 +msgid "To see how to use the :abbr:`VoIP (Voice over Internet Protocol)` widget on a desktop/laptop computer, check out this documentation: :doc:`voip_widget`." +msgstr "" + +#: ../../content/applications/productivity/voip/devices_integrations.rst:45 +msgid "Odoo VoIP (tablet/mobile device)" +msgstr "" + +#: ../../content/applications/productivity/voip/devices_integrations.rst:47 +msgid "The Odoo *VoIP* app can be used on tablets and mobile phones, through the Odoo Android or Apple IOS applications. Additionally, a mobile web browser can be used to access the database." +msgstr "" + +#: ../../content/applications/productivity/voip/devices_integrations.rst:51 +msgid "Odoo Android and Apple IOS applications are no longer being maintained by Odoo on the Android and Apple portals. This means Odoo support only handles limited scopes of Odoo Android or Apple IOS support tickets." +msgstr "" + +#: ../../content/applications/productivity/voip/devices_integrations.rst:56 +msgid "While outgoing calls can be placed using Odoo on a mobile device, be aware that Odoo is **not** a full :abbr:`VoIP (Voice over Internet Protocol)` application, and does **not** ring on incoming calls. If the user needs to be reachable on a mobile device at all times, an app, like Zoiper, should be used. Apps like that stay connected in the background at all times." +msgstr "" + +#: ../../content/applications/productivity/voip/devices_integrations.rst:61 +msgid "For more information, see this documentation: :ref:`voip/zoiper`." +msgstr "" + +#: ../../content/applications/productivity/voip/devices_integrations.rst:63 +msgid "While in the mobile application on a mobile device/tablet, access the Odoo *VoIP* widget, by tapping on the :guilabel:`☎️ (phone)` icon in the upper-right corner. The widget appears in the lower-left corner." +msgstr "" + +#: ../../content/applications/productivity/voip/devices_integrations.rst:67 +msgid "When first making a call from the tablet using the mobile application, the user is prompted to :guilabel:`Allow` the database to use the microphone. Click :guilabel:`Allow` when prompted to continue with the call using the microphone." +msgstr "" + +#: ../../content/applications/productivity/voip/devices_integrations.rst:71 +msgid "This step is **necessary**, whether using the mobile Odoo application or web browser." +msgstr "" + +#: ../../content/applications/productivity/voip/devices_integrations.rst:-1 +msgid "Allow the database to access the microphone." +msgstr "" + +#: ../../content/applications/productivity/voip/devices_integrations.rst:77 +msgid "Odoo then asks how to make the call. The two options are : :guilabel:`VOIP` or :guilabel:`Phone` (should the tablet be enabled for calling). Click the box next to :guilabel:`Remember ?` should this decision be the default moving forward." +msgstr "" + +#: ../../content/applications/productivity/voip/devices_integrations.rst:-1 +msgid "Window prompt to choose whether to use VOIP or the devices phone to make the call." +msgstr "" + +#: ../../content/applications/productivity/voip/devices_integrations.rst:85 +msgid "Here is the layout of what the Odoo *VoIP* app looks like on a mobile device:" +msgstr "" + +#: ../../content/applications/productivity/voip/devices_integrations.rst:-1 +msgid "Layout of what the VoIP app looks like on the a mobile device." +msgstr "" + +#: ../../content/applications/productivity/voip/devices_integrations.rst:94 +msgid "Zoiper Lite" +msgstr "" + +#: ../../content/applications/productivity/voip/devices_integrations.rst:96 +msgid "*Zoiper Lite* is a free :abbr:`VoIP (Voice over Internet Protocol)` :abbr:`SIP (Session Initiation Protocol)` dialer with voice and video." +msgstr "" + +#: ../../content/applications/productivity/voip/devices_integrations.rst:99 +msgid "To start using the *Zoiper* app, download it to the device, via the `Zoiper download page `_." +msgstr "" + +#: ../../content/applications/productivity/voip/devices_integrations.rst:102 +msgid "A mobile device is the most common installation, and this document covers how to set up on the *Zoiper* IOS application. Screenshots and steps may differ depending on the set up conditions." +msgstr "" + +#: ../../content/applications/productivity/voip/devices_integrations.rst:105 +msgid "After installing the *Zoiper* application on the mobile phone, open the application, and tap on :guilabel:`Settings`. Navigate to :menuselection:`Accounts`, and tap on the :guilabel:`+ (plus)` icon to add an account." +msgstr "" + +#: ../../content/applications/productivity/voip/devices_integrations.rst:109 +msgid "If the :abbr:`VoIP (Voice over Internet Protocol)` account is already set up, then click :guilabel:`Yes`. This means an account username and password has already been produced." +msgstr "" + +#: ../../content/applications/productivity/voip/devices_integrations.rst:-1 +msgid "Zoiper account setup, shown in the view from a mobile device." +msgstr "" + +#: ../../content/applications/productivity/voip/devices_integrations.rst:116 +msgid "Next, tap on :guilabel:`Select a provider`. On the screen that populates, tap :guilabel:`Country`, in the upper-right corner, to narrow the providers down to a specific country. Choose the country for the provider that is being configured, then find the :guilabel:`Provider`, and select it." +msgstr "" + +#: ../../content/applications/productivity/voip/devices_integrations.rst:121 +msgid "If the provider being configured is *Axivox*, then select :guilabel:`Belgium`. Then, choose :guilabel:`Axivox` as the provider." +msgstr "" + +#: ../../content/applications/productivity/voip/devices_integrations.rst:-1 +msgid "Zoiper account setup, choosing the provider." +msgstr "" + +#: ../../content/applications/productivity/voip/devices_integrations.rst:128 +msgid "Under :abbr:`SIP (Session Initiation Protocol)` options, enter the :guilabel:`Account name`, :guilabel:`Domain`, :guilabel:`Username`, and :guilabel:`Password`. All this information varies, based on the account." +msgstr "" + +#: ../../content/applications/productivity/voip/devices_integrations.rst:133 +msgid "To access this information, via the *Axivox* portal, navigate to :menuselection:`Users --> Choose user --> Edit --> SIP Identifiers tab`. The :guilabel:`SIP username`, :guilabel:`Domain`, :guilabel:`SIP password`, and :guilabel:`Address of the proxy server` are all present in this tab." +msgstr "" + +#: ../../content/applications/productivity/voip/devices_integrations.rst:141 +msgid "Zoiper Field" +msgstr "" + +#: ../../content/applications/productivity/voip/devices_integrations.rst:142 +msgid "Axivox Field" +msgstr "" + +#: ../../content/applications/productivity/voip/devices_integrations.rst:143 +msgid "Account name" +msgstr "" + +#: ../../content/applications/productivity/voip/devices_integrations.rst:144 +msgid "*Can be anything*" +msgstr "" + +#: ../../content/applications/productivity/voip/devices_integrations.rst:145 +#: ../../content/applications/productivity/voip/devices_integrations.rst:146 +msgid "Domain" +msgstr "" + +#: ../../content/applications/productivity/voip/devices_integrations.rst:147 +msgid "Username" +msgstr "" + +#: ../../content/applications/productivity/voip/devices_integrations.rst:148 +msgid "SIP username" +msgstr "" + +#: ../../content/applications/productivity/voip/devices_integrations.rst:149 +msgid "Password" +msgstr "" + +#: ../../content/applications/productivity/voip/devices_integrations.rst:150 +msgid "SIP password" +msgstr "" + +#: ../../content/applications/productivity/voip/devices_integrations.rst:152 +msgid "Once this account information is entered, click the green :guilabel:`Register` button at the top of the screen. Once the registration information is checked, *Zoiper* populates a message, stating :guilabel:`Registration Status: OK`." +msgstr "" + +#: ../../content/applications/productivity/voip/devices_integrations.rst:156 +msgid "At this point, *Zoiper* is now set up to make phone calls using the :abbr:`VoIP (Voice over Internet Protocol)` service." +msgstr "" + +#: ../../content/applications/productivity/voip/devices_integrations.rst:-1 +msgid "Zoiper account setup, registration successful." +msgstr "" + +#: ../../content/applications/productivity/voip/devices_integrations.rst:164 +msgid "Linphone" +msgstr "" + +#: ../../content/applications/productivity/voip/devices_integrations.rst:166 +msgid "*Linphone* is an open-source :abbr:`VoIP (Voice over Internet Protocol)` :abbr:`SIP (Session Initiation Protocol)` softphone, used for voice, video, messaging (group and individual), as well as conference calls." +msgstr "" + +#: ../../content/applications/productivity/voip/devices_integrations.rst:170 +msgid "To start using the *Linphone* app, download it to the device, via the `Linphone download page `_." +msgstr "" + +#: ../../content/applications/productivity/voip/devices_integrations.rst:173 +msgid "A mobile device is the most common installation, and this document covers how to set up the *Linphone* IOS application. Screenshots and steps may differ depending on the circumstances." +msgstr "" + +#: ../../content/applications/productivity/voip/devices_integrations.rst:176 +msgid "To begin configuring *Linphone* for use with a :abbr:`SIP (Session Initiation Protocol)` provider, first open *Linphone*, and an assistant screen appears." +msgstr "" + +#: ../../content/applications/productivity/voip/devices_integrations.rst:179 +msgid "From this screen, select :guilabel:`Use SIP Account`. Then, on the following screen, enter the :guilabel:`Username`, :guilabel:`Password`, :guilabel:`Domain`, and :guilabel:`Display Name`. Once complete, press :guilabel:`Login`." +msgstr "" + +#: ../../content/applications/productivity/voip/devices_integrations.rst:183 +msgid "At this point, *Linphone* is ready to start making calls, once there is a green button at the top of the application screen that reads, :guilabel:`Connected`." +msgstr "" + +#: ../../content/applications/productivity/voip/devices_integrations.rst:-1 +msgid "Linphone account setup, registration successful." +msgstr "" + +#: ../../content/applications/productivity/voip/devices_integrations.rst:191 +msgid "*Linphone* makes a variety of applications for mobile and desktop devices in operating systems, such as Windows, Linux, Apple, and Android. Because *Linphone* is an open-source project, many new updates are released on a regular basis." +msgstr "" + +#: ../../content/applications/productivity/voip/devices_integrations.rst:195 +msgid "See `Linphone's wiki-documentation page `_." +msgstr "" + +#: ../../content/applications/productivity/voip/onsip.rst:3 +msgid "Use VoIP services in Odoo with OnSIP" +msgstr "" + +#: ../../content/applications/productivity/voip/onsip.rst:8 +msgid "Odoo *VoIP* can be set up to work together with `OnSIP (Odoo Landing Page) `_. OnSIP is a VoIP provider. An account is needed with OnSIP in order to use this service." +msgstr "" + +#: ../../content/applications/productivity/voip/onsip.rst:12 +msgid "Before setting up an account with OnSIP, make sure the company's home area, and the areas that will be called, are covered by OnSIP services." +msgstr "" + +#: ../../content/applications/productivity/voip/onsip.rst:15 +msgid "After opening an OnSIP account, follow the configuration procedure below to configure it on an Odoo database." +msgstr "" + +#: ../../content/applications/productivity/voip/onsip.rst:21 +msgid "To configure the Odoo database to connect to OnSIP services, first navigate to the :menuselection:`Apps application` from the main Odoo dashboard. Then, remove the default `Apps` filter from the :guilabel:`Search...` bar, and search for `OnSIP`." +msgstr "" + +#: ../../content/applications/productivity/voip/onsip.rst:25 +msgid "Next, activate the :guilabel:`VOIP OnSIP` module." +msgstr "" + +#: ../../content/applications/productivity/voip/onsip.rst:-1 +msgid "View of OnSIP app in the app search results." +msgstr "" + +#: ../../content/applications/productivity/voip/onsip.rst:32 +msgid "Odoo VoIP setting" +msgstr "" + +#: ../../content/applications/productivity/voip/onsip.rst:34 +msgid "After installing the *VOIP OnSIP* module, go to the :menuselection:`Settings app`, scroll down to the :guilabel:`Integrations` section, and locate the :guilabel:`Asterisk (VoIP)` fields. Then, proceed to fill in those three fields with the following information:" +msgstr "" + +#: ../../content/applications/productivity/voip/onsip.rst:38 +msgid ":guilabel:`OnSIP Domain`: the domain that was assigned when creating an account on `OnSIP `_." +msgstr "" + +#: ../../content/applications/productivity/voip/onsip.rst:40 +msgid ":guilabel:`WebSocket`: `wss://edge.sip.onsip.com`" +msgstr "" + +#: ../../content/applications/productivity/voip/onsip.rst:41 +msgid ":guilabel:`VoIP Environment`: :guilabel:`Production`" +msgstr "" + +#: ../../content/applications/productivity/voip/onsip.rst:-1 +msgid "VoIP configuration settings in Odoo Settings app." +msgstr "" + +#: ../../content/applications/productivity/voip/onsip.rst:48 +msgid "To access the OnSIP domain, navigate to `OnSIP `_ and log in. Then, click the :guilabel:`Administrators` link in the top-right of the page." +msgstr "" + +#: ../../content/applications/productivity/voip/onsip.rst:51 +msgid "Next, in the left menu, click :guilabel:`Users`, and then select any user. By default, the selected user opens on the :guilabel:`User Info` tab." +msgstr "" + +#: ../../content/applications/productivity/voip/onsip.rst:54 +msgid "Click on the :guilabel:`Phone Settings` tab to reveal OnSIP configuration credentials (first column)." +msgstr "" + +#: ../../content/applications/productivity/voip/onsip.rst:0 +msgid "Domain setting revealed (highlighted) on administrative panel of OnSIP management\n" +"console." +msgstr "" + +#: ../../content/applications/productivity/voip/onsip.rst:63 +msgid "Odoo user setting" +msgstr "" + +#: ../../content/applications/productivity/voip/onsip.rst:65 +msgid "Next, the user needs to be set up in Odoo. Every user associated with an OnSIP user **must** also be configured in the Odoo user's settings/preferences." +msgstr "" + +#: ../../content/applications/productivity/voip/onsip.rst:68 +msgid "To do that, navigate to :menuselection:`Settings app --> Manage Users --> Select the User`." +msgstr "" + +#: ../../content/applications/productivity/voip/onsip.rst:70 +msgid "On the user form, click :guilabel:`Edit` to configure the user's OnSIP account. Then, click the :guilabel:`Preferences` tab, and scroll to the :guilabel:`VoIP Configuration` section." +msgstr "" + +#: ../../content/applications/productivity/voip/onsip.rst:73 +msgid "In this section, fill in the fields with OnSIP credentials." +msgstr "" + +#: ../../content/applications/productivity/voip/onsip.rst:75 +msgid "Fill in the following fields with the associated credentials listed below:" +msgstr "" + +#: ../../content/applications/productivity/voip/onsip.rst:77 +msgid ":guilabel:`Voip Username` = OnSIP :guilabel:`Username`" +msgstr "" + +#: ../../content/applications/productivity/voip/onsip.rst:78 +msgid ":guilabel:`OnSIP Auth Username` = OnSIP :guilabel:`Auth Username`" +msgstr "" + +#: ../../content/applications/productivity/voip/onsip.rst:79 +msgid ":guilabel:`VoIP Secret` = OnSIP :guilabel:`SIP Password`" +msgstr "" + +#: ../../content/applications/productivity/voip/onsip.rst:80 +msgid ":guilabel:`External Device Number` = OnSIP :guilabel:`Ext.` (extension without the `x`)" +msgstr "" + +#: ../../content/applications/productivity/voip/onsip.rst:-1 +msgid "OnSIP user credentials with username, auth username, SIP password, and extension\n" +"highlighted." +msgstr "" + +#: ../../content/applications/productivity/voip/onsip.rst:88 +msgid "The OnSIP extension can be found in the *User* banner line above the tabs." +msgstr "" + +#: ../../content/applications/productivity/voip/onsip.rst:90 +msgid "When these steps are complete, navigate away from the user form in Odoo to save the configurations." +msgstr "" + +#: ../../content/applications/productivity/voip/onsip.rst:92 +msgid "Once saved, Odoo users can make phone calls by clicking the :guilabel:`☎️ (phone)` icon in the top-right corner of Odoo." +msgstr "" + +#: ../../content/applications/productivity/voip/onsip.rst:96 +msgid "Additional setup and troubleshooting steps can be found on `OnSIP's knowledge base `_." +msgstr "" + +#: ../../content/applications/productivity/voip/onsip.rst:100 +msgid "Incoming calls" +msgstr "" + +#: ../../content/applications/productivity/voip/onsip.rst:102 +msgid "The Odoo database also receives incoming calls that produce pop-up windows in Odoo. When those call pop-up windows appear, click the green :guilabel:`📞 (phone)` icon to answer the call." +msgstr "" + +#: ../../content/applications/productivity/voip/onsip.rst:105 +msgid "To ignore the call, click the red :guilabel:`📞 (phone)` icon." +msgstr "" + +#: ../../content/applications/productivity/voip/onsip.rst:-1 +msgid "Incoming call shown in the Odoo VoIP widget." +msgstr "" + +#: ../../content/applications/productivity/voip/onsip.rst:113 +msgid ":doc:`voip_widget`" +msgstr "" + +#: ../../content/applications/productivity/voip/onsip.rst:116 +#: ../../content/applications/productivity/voip/voip_widget.rst:32 +msgid "Troubleshooting" +msgstr "" + +#: ../../content/applications/productivity/voip/onsip.rst:119 +msgid "Missing parameters" +msgstr "" + +#: ../../content/applications/productivity/voip/onsip.rst:121 +msgid "If a *Missing Parameters* message appears in the Odoo widget, make sure to refresh the Odoo browser window (or tab), and try again." +msgstr "" + +#: ../../content/applications/productivity/voip/onsip.rst:-1 +msgid "Missing parameter message in the Odoo VoIP widget." +msgstr "" + +#: ../../content/applications/productivity/voip/onsip.rst:129 +msgid "Incorrect number" +msgstr "" + +#: ../../content/applications/productivity/voip/onsip.rst:131 +msgid "If an *Incorrect Number* message appears in the Odoo widget, make sure to use the international format for the number. This means leading with the international country code." +msgstr "" + +#: ../../content/applications/productivity/voip/onsip.rst:138 +msgid "For example, `16505555555` (where `1` is the international prefix for the United States)." +msgstr "" + +#: ../../content/applications/productivity/voip/onsip.rst:-1 +msgid "Incorrect number message populated in the Odoo VoIP widget." +msgstr "" + +#: ../../content/applications/productivity/voip/onsip.rst:149 +msgid "OnSIP on mobile phone" +msgstr "" + +#: ../../content/applications/productivity/voip/onsip.rst:151 +msgid "In order to make and receive phone calls when the user is not in front of Odoo on their computer, a softphone app on a mobile phone can be used in parallel with Odoo *VoIP*." +msgstr "" + +#: ../../content/applications/productivity/voip/onsip.rst:154 +msgid "This is useful for convenient, on-the-go calls, and to make sure incoming calls are heard. Any SIP softphone will work." +msgstr "" + +#: ../../content/applications/productivity/voip/onsip.rst:158 +msgid ":doc:`devices_integrations`" +msgstr "" + +#: ../../content/applications/productivity/voip/onsip.rst:159 +msgid "`OnSIP App Download `_" +msgstr "" + +#: ../../content/applications/productivity/voip/transfer_forward.rst:3 +msgid "Make, receive, transfer, and forward calls" +msgstr "" + +#: ../../content/applications/productivity/voip/transfer_forward.rst:5 +msgid "Calling prospective clients, customers, or colleagues is an essential part of any business. A company also needs to be available when customers call, in order to build trust and make connections." +msgstr "" + +#: ../../content/applications/productivity/voip/transfer_forward.rst:9 +msgid "This document covers how to make, receive, transfer, and forward calls with Odoo *VoIP*." +msgstr "" + +#: ../../content/applications/productivity/voip/transfer_forward.rst:12 +msgid "Make calls" +msgstr "" + +#: ../../content/applications/productivity/voip/transfer_forward.rst:14 +msgid "Starting on the Odoo dashboard, a call can be made by opening the phone widget in the the upper-right corner, which is represented by a :guilabel:`☎️ (phone)` icon." +msgstr "" + +#: ../../content/applications/productivity/voip/transfer_forward.rst:17 +msgid "Then, a user can click on the :guilabel:`Contacts` tab, and click into any contact in the database to make a call." +msgstr "" + +#: ../../content/applications/productivity/voip/transfer_forward.rst:20 +msgid "Additionally, one can also use the :guilabel:`Search bar` in the :guilabel:`VOIP` pop-up window to find any desired contact." +msgstr "" + +#: ../../content/applications/productivity/voip/transfer_forward.rst:-1 +#: ../../content/applications/productivity/voip/transfer_forward.rst:-1 +msgid "Using the VoIP phone widget to make calls." +msgstr "" + +#: ../../content/applications/productivity/voip/transfer_forward.rst:27 +msgid "To manually make a call, click the :guilabel:`⌨️ (keyboard)` icon, and proceed to manually key in the desired number. Do not forget to lead with the :guilabel:`+ (plus)` icon, followed by the international country code." +msgstr "" + +#: ../../content/applications/productivity/voip/transfer_forward.rst:32 +msgid "For the United States of America, the country code and :guilabel:`+ (plus)` icon, would look like this: `+1`. If one were to dial Belgium, the number would be prefixed by `+32`, and for Great Britain it would be `+44`." +msgstr "" + +#: ../../content/applications/productivity/voip/transfer_forward.rst:36 +msgid "After entering the full number, with the required :guilabel:`+ (plus)` icon prefix and country code, click the green :guilabel:`📞 (phone)` icon to start the call. When finished, click the red :guilabel:`📞 (phone)` icon to end the call." +msgstr "" + +#: ../../content/applications/productivity/voip/transfer_forward.rst:45 +msgid "Receive calls" +msgstr "" + +#: ../../content/applications/productivity/voip/transfer_forward.rst:47 +msgid "An incoming call automatically opens the *VoIP* widget, when a user is using the Odoo database. Should the database be open in another tab, a sound plays (the sound **must** be activated on the device)." +msgstr "" + +#: ../../content/applications/productivity/voip/transfer_forward.rst:51 +msgid "Once back to the tab, the calling screen of the *VoIP* phone widget appears." +msgstr "" + +#: ../../content/applications/productivity/voip/transfer_forward.rst:53 +msgid "Click the green :guilabel:`📞 (phone)` icon to pick up the call, or the red :guilabel:`📞 (phone)` icon to reject the call." +msgstr "" + +#: ../../content/applications/productivity/voip/transfer_forward.rst:-1 +msgid "Incoming call on the VoIP widget, with the call answer and call reject buttons highlighted." +msgstr "" + +#: ../../content/applications/productivity/voip/transfer_forward.rst:61 +msgid "Add to call queue" +msgstr "" + +#: ../../content/applications/productivity/voip/transfer_forward.rst:63 +msgid "All the contacts and customers that need to be called can be seen in one place with the Odoo *VoIP* phone widget, under the :guilabel:`Next activities` tab." +msgstr "" + +#: ../../content/applications/productivity/voip/transfer_forward.rst:-1 +msgid "VoIP widget with next activities highlighted, showing tasks below." +msgstr "" + +#: ../../content/applications/productivity/voip/transfer_forward.rst:70 +msgid "To add a call to the :guilabel:`Next activities` tab, click the green :guilabel:`📞 (phone)` icon, while in kanban view of the *CRM* application." +msgstr "" + +#: ../../content/applications/productivity/voip/transfer_forward.rst:73 +msgid "To remove them from the call queue, hover over the opportunity that has a call scheduled, and click the red :guilabel:`📞 (phone)` icon that appears with the :guilabel:`- (minus)` icon." +msgstr "" + +#: ../../content/applications/productivity/voip/transfer_forward.rst:76 +msgid "When navigating back to the *VoIP* phone widget, **only** the calls that are scheduled immediately for that day appear in the queue under the :guilabel:`Next Activities` tab of the *VoIP* pop-up widget." +msgstr "" + +#: ../../content/applications/productivity/voip/transfer_forward.rst:-1 +msgid "Adding a call to the next activities tab in the VoIP phone widget." +msgstr "" + +#: ../../content/applications/productivity/voip/transfer_forward.rst:84 +msgid "The :guilabel:`Next Activities` tab of the *VoIP* phone widget is integrated with the following Odoo apps: *CRM*, *Project*, and *Helpdesk*." +msgstr "" + +#: ../../content/applications/productivity/voip/transfer_forward.rst:87 +msgid "A call can be added in the chatter of records within those applications." +msgstr "" + +#: ../../content/applications/productivity/voip/transfer_forward.rst:89 +msgid "To manually add a call, via the chatter, click :guilabel:`Activities` (next to the :guilabel:`🕗 (clock)` icon). Under :guilabel:`Activity Type`, select :guilabel:`Call` from the drop-down menu that appears." +msgstr "" + +#: ../../content/applications/productivity/voip/transfer_forward.rst:93 +msgid "Next, set a :guilabel:`Due Date`, and add a :guilabel:`Summary`." +msgstr "" + +#: ../../content/applications/productivity/voip/transfer_forward.rst:95 +msgid "Lastly, change the :guilabel:`Assigned to` field to the person that should make the call. Whomever is set in this last field (:guilabel:`Assigned to`) has this call show up in their :guilabel:`Next Activities` call queue in the Odoo *VoIP* phone widget." +msgstr "" + +#: ../../content/applications/productivity/voip/transfer_forward.rst:100 +msgid "Only calls for the immediate day (today's date) appear in the :guilabel:`Next Activities` tab of the *VoIP* phone widget for that specific user." +msgstr "" + +#: ../../content/applications/productivity/voip/transfer_forward.rst:103 +msgid "If specified, click :guilabel:`Save` or :guilabel:`Open Calendar` to complete the scheduling of the call." +msgstr "" + +#: ../../content/applications/productivity/voip/transfer_forward.rst:107 +msgid "Transfer calls" +msgstr "" + +#: ../../content/applications/productivity/voip/transfer_forward.rst:109 +msgid "A call can be transferred from one user to another in the Odoo *VoIP* phone widget. However, this can **only** occur after speaking to the caller first. Without picking up the call in the Odoo *VoIP* phone widget, the only way to transfer a call is automatically though the provider console/portal." +msgstr "" + +#: ../../content/applications/productivity/voip/transfer_forward.rst:115 +msgid "For more information on transfers, visit :ref:`voip/axivox/forwardings_tab`." +msgstr "" + +#: ../../content/applications/productivity/voip/transfer_forward.rst:117 +msgid "To transfer a call within the Odoo *VoIP* phone widget, first, answer the call using the green :guilabel:`📞 (phone)` icon." +msgstr "" + +#: ../../content/applications/productivity/voip/transfer_forward.rst:120 +msgid "Once the incoming call is answered, click the :guilabel:`↔ (left-right arrow)` icon. Then, enter the extension of the user the call should be forwarded to. Finally, click :guilabel:`Transfer` to route the call to that phone number." +msgstr "" + +#: ../../content/applications/productivity/voip/transfer_forward.rst:125 +msgid "To find the extension for a user, consult the :abbr:`VoIP (Voice over Internet Protocol)` administrator, or, if the user has *Settings* access rights to *Administration*, navigate to :menuselection:`Settings App --> Manage Users --> Select the user --> Preferences --> VOIP --> VoIP username / Extension number`." +msgstr "" + +#: ../../content/applications/productivity/voip/transfer_forward.rst:130 +msgid "For more information on access rights, visit: :doc:`/applications/general/users/access_rights`." +msgstr "" + +#: ../../content/applications/productivity/voip/transfer_forward.rst:-1 +msgid "Transferring a call within the phone widget, with the transfer buttons highlighted." +msgstr "" + +#: ../../content/applications/productivity/voip/transfer_forward.rst:137 +msgid "Forward calls" +msgstr "" + +#: ../../content/applications/productivity/voip/transfer_forward.rst:139 +msgid "To forward a call within the Odoo *VoIP* phone widget, first, answer the call using the green :guilabel:`📞 (phone)` icon. Once the incoming call is answered, click the :guilabel:`↔ (left-right arrow)` icon." +msgstr "" + +#: ../../content/applications/productivity/voip/transfer_forward.rst:143 +msgid "Then, enter the full phone number of the user the call should be forwarded to. Finally, click :guilabel:`Transfer` to route the call to that phone number." +msgstr "" + +#: ../../content/applications/productivity/voip/transfer_forward.rst:147 +msgid "For more information on forwarding, visit :ref:`voip/axivox/forwardings_tab`." +msgstr "" + +#: ../../content/applications/productivity/voip/voip_widget.rst:3 +msgid "VoIP widget" +msgstr "" + +#: ../../content/applications/productivity/voip/voip_widget.rst:5 +msgid "The *VoIP* widget is an add-on made available to Odoo users through the *VoIP* module. It is used to incorporate virtual telephony into the database. The widget is the control center for making and managing calls in Odoo." +msgstr "" + +#: ../../content/applications/productivity/voip/voip_widget.rst:10 +msgid "Phone calls" +msgstr "" + +#: ../../content/applications/productivity/voip/voip_widget.rst:12 +msgid "To make phone calls while in the Odoo database, click the :guilabel:`☎️ (phone)` icon, located in the top navigation bar." +msgstr "" + +#: ../../content/applications/productivity/voip/voip_widget.rst:15 +msgid "When clicked, a :guilabel:`VOIP` pop-up widget appears in the lower-left corner of the Odoo database. The widget allows users to freely navigate throughout the database, while making and receiving calls." +msgstr "" + +#: ../../content/applications/productivity/voip/voip_widget.rst:19 +msgid "When receiving calls in Odoo, the :guilabel:`VOIP` widget rings,and displays a notification. To close the widget, click the :guilabel:`X (close)` icon in the upper-right of the widget's screen." +msgstr "" + +#: ../../content/applications/productivity/voip/voip_widget.rst:23 +msgid "The :abbr:`VoIP (Voice over Internet Protocol)` number is the one provided by Axivox. It can be accessed by navigating to `https://manage.axivox.com/ `_. After logging into the portal, go to :menuselection:`Users --> Outgoing number` (column)." +msgstr "" + +#: ../../content/applications/productivity/voip/voip_widget.rst:-1 +msgid "VoIP call in Odoo." +msgstr "" + +#: ../../content/applications/productivity/voip/voip_widget.rst:35 +msgid "If a *Missing Parameter* error message appears in the Odoo *VoIP* widget, refresh the Odoo window, and try again." +msgstr "" + +#: ../../content/applications/productivity/voip/voip_widget.rst:0 +msgid "\"Missing Parameter\" error message in the Odoo softphone." +msgstr "" + +#: ../../content/applications/productivity/voip/voip_widget.rst:43 +msgid "If an *Incorrect Number* error message appears in the Odoo *VoIP* widget, make sure to use the international format, leading with the :guilabel:`+ (plus)` sign, followed by the international country code." +msgstr "" + +#: ../../content/applications/productivity/voip/voip_widget.rst:47 +msgid "(E.g., +16506913277, where `+1` is the international prefix for the United States.)" +msgstr "" + +#: ../../content/applications/productivity/voip/voip_widget.rst:0 +msgid "\"Incorrect Number\" error message in the Odoo softphone." +msgstr "" + +#: ../../content/applications/productivity/voip/voip_widget.rst:54 +msgid "Tabs" +msgstr "" + +#: ../../content/applications/productivity/voip/voip_widget.rst:56 +msgid "In all, there are three tabs (:guilabel:`Recent`, :guilabel:`Next Activities`, and :guilabel:`Contacts`) present in the *VoIP* widget, which are used for managing calls and day-to-day activities in Odoo." +msgstr "" + +#: ../../content/applications/productivity/voip/voip_widget.rst:61 +msgid "Recent" +msgstr "" + +#: ../../content/applications/productivity/voip/voip_widget.rst:63 +msgid "Under the :guilabel:`Recent` tab of the *VoIP* widget, the call history for the user is available. This includes incoming and outgoing calls. Any number can be clicked to begin a call." +msgstr "" + +#: ../../content/applications/productivity/voip/voip_widget.rst:67 +msgid "Next activities" +msgstr "" + +#: ../../content/applications/productivity/voip/voip_widget.rst:69 +msgid "Under the :guilabel:`Next Activities` tab of the *VoIP* widget, a user can see any activities assigned to them, and which ones are due to be completed for the day." +msgstr "" + +#: ../../content/applications/productivity/voip/voip_widget.rst:72 +msgid "Click an activity from this tab to perform any actions including: Sending an email, accessing their contact, scheduling another activity, or accessing a linked record (such as a Sales Order, Lead/Opportunity, or Project Task)." +msgstr "" + +#: ../../content/applications/productivity/voip/voip_widget.rst:76 +msgid "The user can also mark the activity as complete, edit the details of the activity, or cancel it." +msgstr "" + +#: ../../content/applications/productivity/voip/voip_widget.rst:78 +msgid "To call the customer related to a scheduled activity, click the :guilabel:`📞 (phone)` icon, or click the :guilabel:`⌨️ (keyboard)` icon to dial another number for the customer." +msgstr "" + +#: ../../content/applications/productivity/voip/voip_widget.rst:-1 +msgid "Activity control center on the VoIP widget." +msgstr "" + +#: ../../content/applications/productivity/voip/voip_widget.rst:85 +msgid "Some other icons appear in the *VoIP* widget, categorized by two sections: :guilabel:`Document` and :guilabel:`Activity`." +msgstr "" + +#: ../../content/applications/productivity/voip/voip_widget.rst:88 +msgid "Under the :guilabel:`Document` section, from right to left:" +msgstr "" + +#: ../../content/applications/productivity/voip/voip_widget.rst:90 +msgid ":guilabel:`✉️ (envelope)` icon: sends an email" +msgstr "" + +#: ../../content/applications/productivity/voip/voip_widget.rst:91 +msgid ":guilabel:`👤 (person icon)` icon: redirects to the contact card" +msgstr "" + +#: ../../content/applications/productivity/voip/voip_widget.rst:92 +msgid ":guilabel:`📄 (document)` icon: redirects to the attached record in Odoo" +msgstr "" + +#: ../../content/applications/productivity/voip/voip_widget.rst:93 +msgid ":guilabel:`🕓 (clock)` icon: schedule an activity" +msgstr "" + +#: ../../content/applications/productivity/voip/voip_widget.rst:95 +msgid "Under the :guilabel:`Activity` section, from left to right:" +msgstr "" + +#: ../../content/applications/productivity/voip/voip_widget.rst:97 +msgid ":guilabel:`✔️ (checkmark)` icon: mark activity as done" +msgstr "" + +#: ../../content/applications/productivity/voip/voip_widget.rst:98 +msgid ":guilabel:`✏️ (pencil)` icon: edit the activity" +msgstr "" + +#: ../../content/applications/productivity/voip/voip_widget.rst:99 +msgid ":guilabel:`✖️ (cancel)` icon: cancel the activity" +msgstr "" + +#: ../../content/applications/productivity/voip/voip_widget.rst:102 +msgid "Contacts" +msgstr "" + +#: ../../content/applications/productivity/voip/voip_widget.rst:104 +msgid "Under the :guilabel:`Contacts` tab of the *VoIP* widget, a user can access a contact in the *Contacts* app." +msgstr "" + +#: ../../content/applications/productivity/voip/voip_widget.rst:107 +msgid "Any contact can easily be called by clicking into the contact from the *VoIP* widget's :guilabel:`Contacts` tab." +msgstr "" + +#: ../../content/applications/productivity/voip/voip_widget.rst:110 +msgid "A search feature is also available in the upper-right side of the widget, represented by a :guilabel:`🔍 (magnifying glass)` icon." +msgstr "" + #: ../../content/applications/productivity/whatsapp.rst:3 msgid "WhatsApp" msgstr "" @@ -6384,7 +5813,7 @@ msgid "WhatsApp is an Odoo Enterprise-only application that does not work in Odo msgstr "" #: ../../content/applications/productivity/whatsapp.rst:15 -msgid "For more information on migrating from Odoo Community version to Odoo Enterprise version see this documentation: :doc:`../../../administration/maintain/enterprise`." +msgid "For more information on migrating from Odoo Community version to Odoo Enterprise version see this documentation: :doc:`/administration/on_premise/community_to_enterprise`." msgstr "" #: ../../content/applications/productivity/whatsapp.rst:18 @@ -6683,11 +6112,6 @@ msgstr "" msgid "In another browser tab, navigate to :menuselection:`https://developers.facebook.com --> My Apps --> WhatsApp --> API Configuration`, and then copy the following values from the Meta developer console into the corresponding fields in Odoo:" msgstr "" -#: ../../content/applications/productivity/whatsapp.rst:273 -#: ../../content/applications/productivity/whatsapp.rst:677 -msgid "Name" -msgstr "" - #: ../../content/applications/productivity/whatsapp.rst:274 msgid "Meta Console" msgstr "" @@ -7359,10 +6783,6 @@ msgstr "" msgid "For more information on configuring templates on the Meta developer console visit `Meta's WhatsApp template documentation `_." msgstr "" -#: ../../content/applications/productivity/whatsapp.rst:809 -msgid "Notifications" -msgstr "" - #: ../../content/applications/productivity/whatsapp.rst:811 msgid "Notifications in WhatsApp are handled similar to a message conversation in Odoo. A pop-up window appears with the received conversation from the customer. By default, notifications are set in the WhatsApp business account configuration in Odoo." msgstr "" diff --git a/locale/sources/sales.pot b/locale/sources/sales.pot index fd1e2c17f..4c0f10f64 100644 --- a/locale/sources/sales.pot +++ b/locale/sources/sales.pot @@ -8,7 +8,7 @@ msgid "" msgstr "" "Project-Id-Version: Odoo 17.0\n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2024-03-08 12:48+0000\n" +"POT-Creation-Date: 2024-03-25 16:01+0000\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME \n" "Language-Team: LANGUAGE \n" @@ -72,6 +72,7 @@ msgstr "" #: ../../content/applications/sales/point_of_sale/restaurant/kitchen_printing.rst:10 #: ../../content/applications/sales/point_of_sale/restaurant/tips.rst:11 #: ../../content/applications/sales/point_of_sale/shop/barcode.rst:10 +#: ../../content/applications/sales/point_of_sale/shop/customer_display.rst:12 #: ../../content/applications/sales/point_of_sale/shop/ship_later.rst:10 #: ../../content/applications/sales/sales/invoicing/proforma.rst:14 #: ../../content/applications/sales/sales/products_prices/products/product_images.rst:14 @@ -94,6 +95,7 @@ msgstr "" msgid "Activating this feature adds a new menu, :guilabel:`Leads`, to the header menu bar at the top of the screen." msgstr "" +#: ../../content/applications/sales/crm/acquire_leads/convert.rst:-1 #: ../../content/applications/sales/crm/acquire_leads/convert.rst:-1 msgid "Leads menu on CRM application." msgstr "" @@ -445,7 +447,7 @@ msgid "Users of Odoo Online (SaaS) Enterprise automatically have free trial cred msgstr "" #: ../../content/applications/sales/crm/acquire_leads/lead_mining.rst:92 -msgid ":doc:`../../../general/in_app_purchase`" +msgid ":doc:`/applications/essentials/in_app_purchase`" msgstr "" #: ../../content/applications/sales/crm/acquire_leads/send_quotes.rst:3 @@ -476,6 +478,7 @@ msgstr "" msgid "At the top-left of the form, click the :guilabel:`New Quotation` button." msgstr "" +#: ../../content/applications/sales/crm/acquire_leads/send_quotes.rst:-1 #: ../../content/applications/sales/crm/acquire_leads/send_quotes.rst:-1 msgid "Qualified lead form with New Quotation button emphasized." msgstr "" @@ -868,6 +871,260 @@ msgstr "" msgid "Analyze performance" msgstr "" +#: ../../content/applications/sales/crm/performance/expected_revenue_report.rst:3 +msgid "Expected revenue report" +msgstr "" + +#: ../../content/applications/sales/crm/performance/expected_revenue_report.rst:5 +msgid "*Expected revenue* is the total cash value of leads that are expected to close by a certain date, usually the end of the current month." +msgstr "" + +#: ../../content/applications/sales/crm/performance/expected_revenue_report.rst:8 +msgid "An *expected revenue report* compiles all active leads in a sales pipeline that have a set expected closing date, and compares how sales teams are performing in a given time frame." +msgstr "" + +#: ../../content/applications/sales/crm/performance/expected_revenue_report.rst:-1 +msgid "Close up of the expected closing date on a lead in the CRM app." +msgstr "" + +#: ../../content/applications/sales/crm/performance/expected_revenue_report.rst:15 +msgid "By pulling a monthly expected revenue report, sales managers can see which team members are reaching their goals, and who may need additional assistance to close valuable deals." +msgstr "" + +#: ../../content/applications/sales/crm/performance/expected_revenue_report.rst:19 +msgid "Create an expected revenue report" +msgstr "" + +#: ../../content/applications/sales/crm/performance/expected_revenue_report.rst:21 +msgid "To create an expected revenue report, first navigate to :menuselection:`CRM app --> Reporting --> Pipeline`. This opens the :guilabel:`Pipeline Analysis` dashboard." +msgstr "" + +#: ../../content/applications/sales/crm/performance/expected_revenue_report.rst:25 +msgid "The *Pipeline Analysis* dashboard includes several filters in the search bar by default. Remove these before adding any additional custom filters." +msgstr "" + +#: ../../content/applications/sales/crm/performance/expected_revenue_report.rst:28 +msgid "On the top-left of the report, click :guilabel:`Measures`, then select :guilabel:`Expected Revenue` from the drop-down menu." +msgstr "" + +#: ../../content/applications/sales/crm/performance/expected_revenue_report.rst:31 +msgid "At the top of the page, click the :guilabel:`🔻(triangle pointed down)` icon to the right of the :guilabel:`Search...` bar to open the drop-down menu that contains :guilabel:`Filters`, :guilabel:`Group By`, and :guilabel:`Favorites` columns. Under the :guilabel:`Filters` column, click :guilabel:`Add Custom Filter`, which opens an :guilabel:`Add Custom Filter` pop-up window." +msgstr "" + +#: ../../content/applications/sales/crm/performance/expected_revenue_report.rst:39 +#: ../../content/applications/sales/crm/track_leads/quality_leads_report.rst:53 +#: ../../content/applications/sales/crm/track_leads/unattended_leads_report.rst:68 +msgid "Add custom filters" +msgstr "" + +#: ../../content/applications/sales/crm/performance/expected_revenue_report.rst:41 +msgid "In order to generate an expected revenue report, filters need to be created for the following conditions:" +msgstr "" + +#: ../../content/applications/sales/crm/performance/expected_revenue_report.rst:44 +msgid ":ref:`Expected closing date `: limits results to only include leads expected to close within a specific time frame." +msgstr "" + +#: ../../content/applications/sales/crm/performance/expected_revenue_report.rst:46 +msgid ":ref:`Exclude unassigned leads `: excludes leads without an assigned salesperson." +msgstr "" + +#: ../../content/applications/sales/crm/performance/expected_revenue_report.rst:48 +msgid ":ref:`Specific sales teams `: limits results to only include leads assigned to one or more sales teams. This filter is optional and should not be included if the report is intended for the entire company." +msgstr "" + +#: ../../content/applications/sales/crm/performance/expected_revenue_report.rst:55 +msgid "Add filter for expected closing date" +msgstr "" + +#: ../../content/applications/sales/crm/performance/expected_revenue_report.rst:57 +msgid "On the :guilabel:`Add Custom Filter` pop-up window, click into the first field of the new rule. Type `Expected Closing` into the :guilabel:`Search...` bar, or scroll to select it from the list. Click in the second field and select :guilabel:`is set`. This limits the results to only include leads where an estimated closing date is listed." +msgstr "" + +#: ../../content/applications/sales/crm/performance/expected_revenue_report.rst:62 +msgid "Next, click the :guilabel:`➕ (plus)` icon to the right of the rule to duplicate it." +msgstr "" + +#: ../../content/applications/sales/crm/performance/expected_revenue_report.rst:65 +msgid "Using the :guilabel:`➕ (plus)` icon makes it easy to add multiple rules based on the same filter." +msgstr "" + +#: ../../content/applications/sales/crm/performance/expected_revenue_report.rst:68 +msgid "In the second field of the new rule, select :guilabel:`is between` from the drop-down menu. This creates a set time frame during which the expected closing date must occur for leads to be included in the results." +msgstr "" + +#: ../../content/applications/sales/crm/performance/expected_revenue_report.rst:72 +msgid "Click in each date field, one at a time, and use the calendar popover window to add both a start and end date to the rule. This is usually the beginning and ending of the current month, or fiscal quarter." +msgstr "" + +#: ../../content/applications/sales/crm/performance/expected_revenue_report.rst:79 +#: ../../content/applications/sales/crm/track_leads/quality_leads_report.rst:117 +#: ../../content/applications/sales/crm/track_leads/unattended_leads_report.rst:107 +msgid "Exclude unassigned leads" +msgstr "" + +#: ../../content/applications/sales/crm/performance/expected_revenue_report.rst:81 +msgid "After filtering for the expected closing date, add a :guilabel:`New Rule`. Then, click into the new rule's first field, and type `Salesperson` in the :guilabel:`Search...` bar, or scroll through the list to select it. Click in the rule's second field and select :guilabel:`is set` from the drop-down menu. This excludes any results without an assigned salesperson." +msgstr "" + +#: ../../content/applications/sales/crm/performance/expected_revenue_report.rst:89 +msgid "Add a filter for sales teams" +msgstr "" + +#: ../../content/applications/sales/crm/performance/expected_revenue_report.rst:92 +msgid "This filter is optional. To view results for the entire company, do **not** add this filter, and continue to :ref:`View results `." +msgstr "" + +#: ../../content/applications/sales/crm/performance/expected_revenue_report.rst:95 +#: ../../content/applications/sales/crm/track_leads/quality_leads_report.rst:103 +#: ../../content/applications/sales/crm/track_leads/unattended_leads_report.rst:125 +msgid "To limit the results of the report to one or more sales teams, click :guilabel:`New Rule`. Next, click the first field for the new rule, and type `Sales Team` in the :guilabel:`Search...` bar, or scroll to search through the list to locate it." +msgstr "" + +#: ../../content/applications/sales/crm/performance/expected_revenue_report.rst:99 +msgid "In the rule's second field, select :guilabel:`is in` from the drop-down menu. Selecting this operator limits results to the sales teams indicated in the next field." +msgstr "" + +#: ../../content/applications/sales/crm/performance/expected_revenue_report.rst:102 +msgid "Lastly, click into the third field, and either: make a selection from the complete list revealed in the popover menu, or type the first few characters of the specific sales team's title to quickly find and select it as a parameter." +msgstr "" + +#: ../../content/applications/sales/crm/performance/expected_revenue_report.rst:107 +msgid "Multiple teams can be added to the `Sales Team` rule, where each parameter is treated with an \"or\" (e.g. \"any\") operator in the search logic." +msgstr "" + +#: ../../content/applications/sales/crm/performance/expected_revenue_report.rst:-1 +msgid "Add Custom Filters pop-up window with custom filters configured for expected revenue\n" +"report." +msgstr "" + +#: ../../content/applications/sales/crm/performance/expected_revenue_report.rst:118 +#: ../../content/applications/sales/crm/track_leads/unattended_leads_report.rst:145 +msgid "View results" +msgstr "" + +#: ../../content/applications/sales/crm/performance/expected_revenue_report.rst:120 +#: ../../content/applications/sales/crm/track_leads/quality_leads_report.rst:193 +#: ../../content/applications/sales/crm/track_leads/unattended_leads_report.rst:147 +msgid "At the top of the :guilabel:`Add Custom Filter` form, there is an option to match :guilabel:`any` or :guilabel:`all` of the rules. In order to properly run the report, only records that match **all** of the following filters should be included. Before adding the filters, make sure :guilabel:`all` is selected in this field." +msgstr "" + +#: ../../content/applications/sales/crm/performance/expected_revenue_report.rst:-1 +msgid "Emphasis on the match all filters option on the Add Custom Filter pop-up window." +msgstr "" + +#: ../../content/applications/sales/crm/performance/expected_revenue_report.rst:129 +msgid "At the bottom of the :guilabel:`Add Custom Filter` form, click :guilabel:`Add`." +msgstr "" + +#: ../../content/applications/sales/crm/performance/expected_revenue_report.rst:132 +#: ../../content/applications/sales/crm/performance/win_loss.rst:279 +msgid "View options" +msgstr "" + +#: ../../content/applications/sales/crm/performance/expected_revenue_report.rst:134 +msgid "The expected revenue report benefits from utilizing multiple views. The default graph view can be used to identify which salespeople are expected to bring in the most revenue, while the list view and pivot view provide more detail on specific deals." +msgstr "" + +#: ../../content/applications/sales/crm/performance/expected_revenue_report.rst:140 +#: ../../content/applications/sales/subscriptions/reports.rst:97 +msgid "Graph view" +msgstr "" + +#: ../../content/applications/sales/crm/performance/expected_revenue_report.rst:142 +msgid "The *graph view* is used to visualize data, and is beneficial in identifying patterns and trends." +msgstr "" + +#: ../../content/applications/sales/crm/performance/expected_revenue_report.rst:145 +msgid "*Bar charts* are used to show the distribution of data across several categories or among several salespeople." +msgstr "" + +#: ../../content/applications/sales/crm/performance/expected_revenue_report.rst:148 +msgid "*Line charts* are useful to show changing trends over a period of time." +msgstr "" + +#: ../../content/applications/sales/crm/performance/expected_revenue_report.rst:150 +msgid "*Pie charts* are useful to show the distribution, or comparison, of data among a small number of categories or salespeople, specifically how they form the meaningful part of a whole picture." +msgstr "" + +#: ../../content/applications/sales/crm/performance/expected_revenue_report.rst:154 +msgid "The default view for the expected revenue report is the bar chart, stacked. To change to a different graph view, click one of the icons at the top-left of the report. While both the line chart and bar chart are available in stacked view, the pie chart is not." +msgstr "" + +#: ../../content/applications/sales/crm/performance/expected_revenue_report.rst:0 +msgid "Close up view of the graph icons on the Pipeline analysis report in the CRM app." +msgstr "" + +#: ../../content/applications/sales/crm/performance/expected_revenue_report.rst:162 +msgid "Graph view icons in order: bar chart, line chart, pie chart, stacked." +msgstr "" + +#: ../../content/applications/sales/crm/performance/expected_revenue_report.rst:164 +#: ../../content/applications/sales/subscriptions/reports.rst:158 +msgid "List view" +msgstr "" + +#: ../../content/applications/sales/crm/performance/expected_revenue_report.rst:166 +msgid "The *list view* provides a list of all leads that are expected to close by the designated date. Clicking on a lead in list view opens the record for detailed analysis, but many insights can be gleaned from the basic view." +msgstr "" + +#: ../../content/applications/sales/crm/performance/expected_revenue_report.rst:170 +msgid "To switch to the list view, click the :guilabel:`≣ (list)` icon at the top-right of the report." +msgstr "" + +#: ../../content/applications/sales/crm/performance/expected_revenue_report.rst:0 +msgid "Close up of the list view icon in the CRM app." +msgstr "" + +#: ../../content/applications/sales/crm/performance/expected_revenue_report.rst:177 +msgid "To add additional metrics to the report, click the *additional options menu* indicated by the :guilabel:`toggle` icon at the top-right of the list." +msgstr "" + +#: ../../content/applications/sales/crm/performance/expected_revenue_report.rst:0 +msgid "Close up of the toggle icon in the CRM app." +msgstr "" + +#: ../../content/applications/sales/crm/performance/expected_revenue_report.rst:184 +msgid "Clicking the toggle icon in *list view* opens the *additional options menu*." +msgstr "" + +#: ../../content/applications/sales/crm/performance/expected_revenue_report.rst:186 +msgid "Select any additional metrics from the drop-down menu to add them to the list view. Some options that may be useful are :guilabel:`Expected Closing` and :guilabel:`Probability`." +msgstr "" + +#: ../../content/applications/sales/crm/performance/expected_revenue_report.rst:189 +#: ../../content/applications/sales/subscriptions/reports.rst:135 +msgid "Pivot view" +msgstr "" + +#: ../../content/applications/sales/crm/performance/expected_revenue_report.rst:191 +msgid "The *pivot view* arranges all leads that are expected to close by the designated date into a dynamic table." +msgstr "" + +#: ../../content/applications/sales/crm/performance/expected_revenue_report.rst:194 +msgid "To switch to the pivot view, click the :guilabel:`Pivot` icon at the top-right of the report." +msgstr "" + +#: ../../content/applications/sales/crm/performance/expected_revenue_report.rst:0 +msgid "Close up of the pivot view icon in the CRM app." +msgstr "" + +#: ../../content/applications/sales/crm/performance/expected_revenue_report.rst:200 +msgid "When the pivot view is selected for this report, the X-axis lists the stages in the pipeline, while the Y-axis defaults to group the results by their creation date. To switch these groupings, click the flip access icon (:guilabel:`⇄`) at the top of the report." +msgstr "" + +#: ../../content/applications/sales/crm/performance/expected_revenue_report.rst:204 +msgid "To add additional measures to the report, click the :guilabel:`Measures` button at the top-left of the report. Select any additional metrics from the drop-down menu." +msgstr "" + +#: ../../content/applications/sales/crm/performance/expected_revenue_report.rst:207 +msgid "To add a group to a row or column to the pivot view, click the :guilabel:`➕ (plus sign)` next to :guilabel:`Total`, and then select one of the groups. To remove one, click the :guilabel:`➖ (minus sign)` and de-select the appropriate option." +msgstr "" + +#: ../../content/applications/sales/crm/performance/expected_revenue_report.rst:211 +msgid "Click :guilabel:`Insert in Spreadsheet` to add the pivot view into an editable spreadsheet format within the *Dashboards* app. If the Odoo *Documents* app is installed, the report can be inserted into a blank or existing spreadsheet, and exported." +msgstr "" + #: ../../content/applications/sales/crm/performance/win_loss.rst:3 msgid "Pipeline Analysis" msgstr "" @@ -1339,10 +1596,6 @@ msgstr "" msgid ":guilabel:`Count`: measures the total amount of leads that match the search criteria." msgstr "" -#: ../../content/applications/sales/crm/performance/win_loss.rst:279 -msgid "View options" -msgstr "" - #: ../../content/applications/sales/crm/performance/win_loss.rst:281 msgid "After configuring filters, groupings, and measurements, the :guilabel:`Pipeline Analysis` page can display the data in a variety of ways. By default, the page uses the graph view, but can be changed to a pivot view, cohort view, or list view." msgstr "" @@ -2346,6 +2599,421 @@ msgstr "" msgid "Your customers will no longer be able to keep any secrets from you!" msgstr "" +#: ../../content/applications/sales/crm/track_leads/quality_leads_report.rst:3 +msgid "Quality leads report" +msgstr "" + +#: ../../content/applications/sales/crm/track_leads/quality_leads_report.rst:5 +msgid "A *quality lead* is a lead that is likely to result in a sale. It should match the characteristics most commonly believed to help salespeople close a deal, in addition to more precise criteria that is specific to each organization." +msgstr "" + +#: ../../content/applications/sales/crm/track_leads/quality_leads_report.rst:10 +msgid "The specific criteria that defines a *quality lead* is different for every organization. For more information, see :ref:`Define a quality lead `." +msgstr "" + +#: ../../content/applications/sales/crm/track_leads/quality_leads_report.rst:13 +msgid "A quality leads *report* compares how many quality leads each salesperson has received over a specific amount of time, such as within the past 30 days. Sales managers can use such a report to make more informed decisions when assigning new leads to their team" +msgstr "" + +#: ../../content/applications/sales/crm/track_leads/quality_leads_report.rst:18 +msgid "A sales manager pulls a quality leads report using their company's criteria:" +msgstr "" + +#: ../../content/applications/sales/crm/track_leads/quality_leads_report.rst:20 +msgid "Leads must include a phone number and an email address." +msgstr "" + +#: ../../content/applications/sales/crm/track_leads/quality_leads_report.rst:21 +msgid "The email address must be from a professional domain." +msgstr "" + +#: ../../content/applications/sales/crm/track_leads/quality_leads_report.rst:22 +msgid "The source for the lead must be from a live chat conversation or an appointment with a salesperson." +msgstr "" + +#: ../../content/applications/sales/crm/track_leads/quality_leads_report.rst:25 +msgid "After running the report, the manager can see that, although everyone's ability to close a deal has varied, some members of the sales team have received a higher number of quality leads than others." +msgstr "" + +#: ../../content/applications/sales/crm/track_leads/quality_leads_report.rst:0 +msgid "An example of a quality leads report in the Odoo CRM application." +msgstr "" + +#: ../../content/applications/sales/crm/track_leads/quality_leads_report.rst:33 +msgid "Using this information, the sales manager may decide to assign more quality leads to the sales people currently on the lower end, to balance out the distribution of quality leads." +msgstr "" + +#: ../../content/applications/sales/crm/track_leads/quality_leads_report.rst:39 +msgid "Create a quality leads report" +msgstr "" + +#: ../../content/applications/sales/crm/track_leads/quality_leads_report.rst:41 +msgid "To create a quality leads report, first navigate to :menuselection:`CRM app --> Reporting --> Pipeline` to open the :guilabel:`Pipeline Analysis` dashboard. Click into the :guilabel:`Search...` bar at the top of the page and remove any active filters." +msgstr "" + +#: ../../content/applications/sales/crm/track_leads/quality_leads_report.rst:45 +msgid "Click the :guilabel:`🔻(triangle pointed down)` icon to the right of the :guilabel:`Search...` bar to open the drop-down mega menu that contains :guilabel:`Filters`, :guilabel:`Group By`, and :guilabel:`Favorites` columns. Click :guilabel:`Add Custom Filter`. This opens a :guilabel:`Add Custom Filter` pop-up window." +msgstr "" + +#: ../../content/applications/sales/crm/track_leads/quality_leads_report.rst:50 +#: ../../content/applications/sales/crm/track_leads/unattended_leads_report.rst:65 +msgid "The :guilabel:`Add Custom Filter` pop-up window allows for the creation of more specific filters." +msgstr "" + +#: ../../content/applications/sales/crm/track_leads/quality_leads_report.rst:55 +msgid "In order to generate a quality leads report, filters need to be created for the following conditions:" +msgstr "" + +#: ../../content/applications/sales/crm/track_leads/quality_leads_report.rst:58 +msgid ":ref:`Starting date `: limits results to those created within a specific time frame." +msgstr "" + +#: ../../content/applications/sales/crm/track_leads/quality_leads_report.rst:60 +msgid ":ref:`Specific sales teams `: limits results to only include leads for one or more sales teams. This filter is optional and should not be included if the is intended for the entire company." +msgstr "" + +#: ../../content/applications/sales/crm/track_leads/quality_leads_report.rst:63 +msgid ":ref:`Exclude unassigned leads `: excludes leads without an assigned salesperson." +msgstr "" + +#: ../../content/applications/sales/crm/track_leads/quality_leads_report.rst:65 +msgid ":ref:`Include archived leads `: ensures that both active and inactive leads are included in the results." +msgstr "" + +#: ../../content/applications/sales/crm/track_leads/quality_leads_report.rst:67 +msgid ":ref:`Add rules for quality leads `: includes or excludes results based on criteria that is specific to a company or sales team." +msgstr "" + +#: ../../content/applications/sales/crm/track_leads/quality_leads_report.rst:74 +#: ../../content/applications/sales/crm/track_leads/unattended_leads_report.rst:140 +msgid "An example of the Custom Filter pop-up window with all of the rules configured." +msgstr "" + +#: ../../content/applications/sales/crm/track_leads/quality_leads_report.rst:74 +msgid "An example of the *Custom Filter* pop-up window with all of the default rules configured." +msgstr "" + +#: ../../content/applications/sales/crm/track_leads/quality_leads_report.rst:79 +msgid "Add a starting date filter" +msgstr "" + +#: ../../content/applications/sales/crm/track_leads/quality_leads_report.rst:81 +msgid "Begin by first defining the rule's parameter with a date range, by clicking into the first field, on the left of the row, and typing `Created On` in the :guilabel:`Search...` bar, or by scrolling through the menu's list to locate it." +msgstr "" + +#: ../../content/applications/sales/crm/track_leads/quality_leads_report.rst:85 +msgid "In the rule's operator drop-down menu, define the parameter further by selecting either:" +msgstr "" + +#: ../../content/applications/sales/crm/track_leads/quality_leads_report.rst:87 +msgid ":guilabel:`>= (greater than or equal to)` to specify a start date and include all entries *after* that start date (as well as the initial value itself); or" +msgstr "" + +#: ../../content/applications/sales/crm/track_leads/quality_leads_report.rst:89 +msgid ":guilabel:`is between` to more sharply define a time frame with a clear start and end date. All matching entries that fit within the defined start and end dates are included in the report." +msgstr "" + +#: ../../content/applications/sales/crm/track_leads/quality_leads_report.rst:92 +msgid "With either option, use the pop-up calendar's day and time pickers, in the far right field, to define the respective date range. Setting these values concludes the creation of the first rule." +msgstr "" + +#: ../../content/applications/sales/crm/track_leads/quality_leads_report.rst:98 +msgid "Add a sales team filter" +msgstr "" + +#: ../../content/applications/sales/crm/track_leads/quality_leads_report.rst:101 +msgid "This filter is optional. To view results for the entire company, do **not** add this filter." +msgstr "" + +#: ../../content/applications/sales/crm/track_leads/quality_leads_report.rst:107 +#: ../../content/applications/sales/crm/track_leads/unattended_leads_report.rst:129 +msgid "In the rule's second field, select :guilabel:`is in` from the drop-down menu. Selecting this operator limits results to the sales teams selected in the next field." +msgstr "" + +#: ../../content/applications/sales/crm/track_leads/quality_leads_report.rst:110 +#: ../../content/applications/sales/crm/track_leads/unattended_leads_report.rst:132 +msgid "Lastly, in the third field, select the desired sales team from the drop-down menu. Multiple teams can be added in this field, where each parameter is treated with an \"or\" (e.g. \"any\") operator in the search logic." +msgstr "" + +#: ../../content/applications/sales/crm/track_leads/quality_leads_report.rst:119 +msgid "Next, add a :guilabel:`New Rule`. Then, click into the first field for the new rule, and type `Salesperson` in the :guilabel:`Search...` bar, or scroll to search through the list to locate it." +msgstr "" + +#: ../../content/applications/sales/crm/track_leads/quality_leads_report.rst:122 +#: ../../content/applications/sales/crm/track_leads/unattended_leads_report.rst:113 +msgid "In the rule's second field, select :guilabel:`is set` from the drop-down menu. Selecting this operator excludes any leads not assigned to a specific salesperson." +msgstr "" + +#: ../../content/applications/sales/crm/track_leads/quality_leads_report.rst:128 +msgid "Include archived leads" +msgstr "" + +#: ../../content/applications/sales/crm/track_leads/quality_leads_report.rst:131 +msgid "This filter is also optional, as it adds archived (inactive) leads to the report, however it is recommended to include this since it pulls *all* assigned leads, regardless of status, into the report. This ensures a more accurate representation of assigned leads is captured. However, to pull a report that only includes active leads, do **not** activate this feature." +msgstr "" + +#: ../../content/applications/sales/crm/track_leads/quality_leads_report.rst:136 +msgid "Next, in the upper-right corner of the :guilabel:`Add Custom filter` pop-up window, move the :guilabel:`Include archived` toggle to active." +msgstr "" + +#: ../../content/applications/sales/crm/track_leads/quality_leads_report.rst:-1 +msgid "The Add Custom Filter pop-up with emphasis on the Include Archived toggle." +msgstr "" + +#: ../../content/applications/sales/crm/track_leads/quality_leads_report.rst:143 +msgid "Enabling this feature adds archived (inactive) leads to the report." +msgstr "" + +#: ../../content/applications/sales/crm/track_leads/quality_leads_report.rst:148 +msgid "Add rules for quality leads" +msgstr "" + +#: ../../content/applications/sales/crm/track_leads/quality_leads_report.rst:150 +msgid "The filters added in this step vary, based on how an organization defines a *quality lead*." +msgstr "" + +#: ../../content/applications/sales/crm/track_leads/quality_leads_report.rst:155 +msgid "Define a quality lead" +msgstr "" + +#: ../../content/applications/sales/crm/track_leads/quality_leads_report.rst:157 +msgid "As defined earlier, a *quality lead* is a lead that is likely to result in a won opportunity. Although the exact criteria for a quality lead varies from organization to organization, it is often a combination of factors commonly attributed to positive sales outcomes, in addition to factors valued by the specific organization." +msgstr "" + +#: ../../content/applications/sales/crm/track_leads/quality_leads_report.rst:162 +msgid "In addition to the basic filters and grouping options outlined in the general :ref:`Quality leads report `, consider the following filters when defining a quality lead:" +msgstr "" + +#: ../../content/applications/sales/crm/track_leads/quality_leads_report.rst:166 +msgid ":guilabel:`Email` or :guilabel:`Phone`: the information in these fields can help determine whether or not a lead is a professional contact." +msgstr "" + +#: ../../content/applications/sales/crm/track_leads/quality_leads_report.rst:168 +msgid ":guilabel:`Source`: this field links to the marketing and lead generation efforts from other Odoo applications, including *Live Chat*, *Social Marketing*, and *Email Marketing*." +msgstr "" + +#: ../../content/applications/sales/crm/track_leads/quality_leads_report.rst:170 +msgid ":guilabel:`Stage`: this filter can be used to eliminate or target leads that have reached specific stages." +msgstr "" + +#: ../../content/applications/sales/crm/track_leads/quality_leads_report.rst:172 +msgid ":guilabel:`Medium`: a lead's source can indicate its quality level, as various channels have different won rates and expected revenues." +msgstr "" + +#: ../../content/applications/sales/crm/track_leads/quality_leads_report.rst:174 +msgid ":guilabel:`Campaign`: adding this filter helps track of the success of different marketing efforts to capture high quality leads." +msgstr "" + +#: ../../content/applications/sales/crm/track_leads/quality_leads_report.rst:176 +msgid ":guilabel:`Lost Reason`: exclude leads that may appear to be quality based on various criteria, but have been marked as *lost* for specified reasons." +msgstr "" + +#: ../../content/applications/sales/crm/track_leads/quality_leads_report.rst:178 +msgid ":guilabel:`Tags`: include or exclude results based on one or more customized tags." +msgstr "" + +#: ../../content/applications/sales/crm/track_leads/quality_leads_report.rst:181 +msgid "When adding rules to a custom filter, keep the statements preceding each rule in mind. The statement above a rule determines whether the search results must match **all** of the rules below the statement, or **any** of the rules below the statement." +msgstr "" + +#: ../../content/applications/sales/crm/track_leads/quality_leads_report.rst:0 +msgid "Close up of the match rule options on a add custom filter pop-up window." +msgstr "" + +#: ../../content/applications/sales/crm/track_leads/quality_leads_report.rst:190 +msgid "View the report" +msgstr "" + +#: ../../content/applications/sales/crm/track_leads/quality_leads_report.rst:0 +msgid "Close up on the match all rules option on the add a custom filter pop-up window." +msgstr "" + +#: ../../content/applications/sales/crm/track_leads/quality_leads_report.rst:202 +msgid "After the filters are configured, click :guilabel:`Add`. The default display for the report is a bar graph, where the leads are grouped by *stage*." +msgstr "" + +#: ../../content/applications/sales/crm/track_leads/quality_leads_report.rst:205 +msgid "To group the results by salesperson, click the :guilabel:`🔻(triangle pointed down)` icon to the right of the :guilabel:`Search...` bar to open the drop-down mega menu. Under the :guilabel:`Group By` heading, select :guilabel:`Salesperson`. In the same column, under the :guilabel:`Group By` heading, click :guilabel:`Add a Custom Group`, then select :guilabel:`Active` on the resulting drop-down menu to layer in lead *status*, under the parent :guilabel:`Salesperson` grouping." +msgstr "" + +#: ../../content/applications/sales/crm/track_leads/quality_leads_report.rst:211 +msgid "The report now displays the total count of *quality leads* each salesperson has received in the designated time period. Because there are layered :guilabel:`Group By` filters, the grouped leads are also color-coded to identify whether they are *active* or *marked as lost*." +msgstr "" + +#: ../../content/applications/sales/crm/track_leads/quality_leads_report.rst:216 +msgid "To save this search for later, click the :guilabel:`🔻(triangle pointed down)` icon next to the :guilabel:`Search...` bar to open the drop-down menu. Under the :guilabel:`Favorites` heading, click :guilabel:`Save current search`." +msgstr "" + +#: ../../content/applications/sales/crm/track_leads/quality_leads_report.rst:220 +msgid "In the drop-down menu, rename the report from the default `Pipeline` label to `Quality Leads`, and click :guilabel:`Save`." +msgstr "" + +#: ../../content/applications/sales/crm/track_leads/unattended_leads_report.rst:3 +msgid "Unattended leads report" +msgstr "" + +#: ../../content/applications/sales/crm/track_leads/unattended_leads_report.rst:5 +msgid "*Unattended leads* are leads that have scheduled activities that are either due or past due. Whenever an activity is scheduled, Odoo tracks the due date, and sends email reminders to the users the activity is assigned to." +msgstr "" + +#: ../../content/applications/sales/crm/track_leads/unattended_leads_report.rst:9 +msgid "An *unattended leads report* compiles all active leads in the pipeline with due or past due activities, allowing a sales manager to identify which opportunities require immediate attention." +msgstr "" + +#: ../../content/applications/sales/crm/track_leads/unattended_leads_report.rst:12 +msgid "By pulling a daily unattended leads report, sales managers can remind their teams to address outstanding activities before they become past due, helping avoid neglected leads and reinforcing proactive behaviors in their salespeople." +msgstr "" + +#: ../../content/applications/sales/crm/track_leads/unattended_leads_report.rst:18 +msgid "A sales manager starts their day by pulling an unattended leads report, and upon switching to list view, they see the following:" +msgstr "" + +#: ../../content/applications/sales/crm/track_leads/unattended_leads_report.rst:0 +msgid "List view of a sample Unattended Leads report with the activities emphasized." +msgstr "" + +#: ../../content/applications/sales/crm/track_leads/unattended_leads_report.rst:25 +msgid "Their team member, Mitchell, has two leads in the *Proposition* stage with activities that are due." +msgstr "" + +#: ../../content/applications/sales/crm/track_leads/unattended_leads_report.rst:28 +msgid "The yellow :guilabel:`📞 (phone)` icon indicates that the `Modern Open Space` lead has a phone call activity scheduled for today. The red :guilabel:`✉️ (envelope)` icon indicates that the `5 VP Chairs` lead has an email activity scheduled that is past due." +msgstr "" + +#: ../../content/applications/sales/crm/track_leads/unattended_leads_report.rst:32 +msgid "Clicking on the `5 VP Chairs` lead, the sales manager opens the record of the lead and reviews the chatter. They see that the email was scheduled to be sent two days ago, but Mitchell never marked this activity as done." +msgstr "" + +#: ../../content/applications/sales/crm/track_leads/unattended_leads_report.rst:0 +#: ../../content/applications/sales/crm/track_leads/unattended_leads_report.rst:-1 +msgid "Example of overdue activities notification in the chatter of a lead." +msgstr "" + +#: ../../content/applications/sales/crm/track_leads/unattended_leads_report.rst:41 +msgid "In order to pull a unattended leads report, sales teams **must** be regularly utilizing activity in the *CRM* pipeline, on individual lead and opportunity cards." +msgstr "" + +#: ../../content/applications/sales/crm/track_leads/unattended_leads_report.rst:44 +msgid "It is **not** possible to compile a complete report if the sales people are not using the *Activities* feature in the *chatter*" +msgstr "" + +#: ../../content/applications/sales/crm/track_leads/unattended_leads_report.rst:47 +msgid "For more information, refer to :doc:`Activities <../../../essentials/activities>`" +msgstr "" + +#: ../../content/applications/sales/crm/track_leads/unattended_leads_report.rst:50 +msgid "Create an unattended leads report" +msgstr "" + +#: ../../content/applications/sales/crm/track_leads/unattended_leads_report.rst:52 +msgid "To create an unattended leads report, first navigate to :menuselection:`CRM app --> Reporting --> Pipeline` to open the :guilabel:`Pipeline Analysis` dashboard. Click into the :guilabel:`Search...` bar at the top of the page, and remove all of the default filters." +msgstr "" + +#: ../../content/applications/sales/crm/track_leads/unattended_leads_report.rst:57 +msgid "The :guilabel:`Created on` filter can remain active, as this variable may be useful to include in the report." +msgstr "" + +#: ../../content/applications/sales/crm/track_leads/unattended_leads_report.rst:60 +msgid "Next, add custom filters by clicking the :guilabel:`🔻(triangle pointed down)` icon to the right of the :guilabel:`Search...` bar to open the drop-down menu that contains :guilabel:`Filters`, :guilabel:`Group By`, and :guilabel:`Favorites` columns. Under the :guilabel:`Filters` column, click :guilabel:`Add Custom Filter`, which opens an :guilabel:`Add Custom Filter` pop-up window." +msgstr "" + +#: ../../content/applications/sales/crm/track_leads/unattended_leads_report.rst:70 +msgid "In order to generate an unattended leads report, filters need to be created for the following conditions:" +msgstr "" + +#: ../../content/applications/sales/crm/track_leads/unattended_leads_report.rst:73 +msgid ":ref:`Past due activities `: limits the results to only include leads with an assigned activity where the due date has past. This can be altered to include activities due to occur on the date the report is generated as well." +msgstr "" + +#: ../../content/applications/sales/crm/track_leads/unattended_leads_report.rst:76 +msgid ":ref:`Unassigned leads `: excludes leads without an assigned salesperson." +msgstr "" + +#: ../../content/applications/sales/crm/track_leads/unattended_leads_report.rst:78 +msgid ":ref:`Specific sales teams `: limits results to only include leads assigned to one or more sales teams. This filter is optional and should not be included if the report is intended for the entire company." +msgstr "" + +#: ../../content/applications/sales/crm/track_leads/unattended_leads_report.rst:85 +msgid "Add filter for past due activities" +msgstr "" + +#: ../../content/applications/sales/crm/track_leads/unattended_leads_report.rst:87 +msgid "Click the first field for the new rule, and type `Activities` in the :guilabel:`Search...` bar, or scroll to search through the list to locate it. Then, next to :guilabel:`Activities`, click the :guilabel:`> (greater than sign)` to open a new drop-down menu with secondary conditions." +msgstr "" + +#: ../../content/applications/sales/crm/track_leads/unattended_leads_report.rst:91 +msgid "Type `Due Date` in the :guilabel:`Search...` bar, or scroll to search through the list. Click :guilabel:`Due Date` to add it to the rule." +msgstr "" + +#: ../../content/applications/sales/crm/track_leads/unattended_leads_report.rst:0 +#: ../../content/applications/sales/crm/track_leads/unattended_leads_report.rst:0 +msgid "Custom filter pop-up with emphasis on the options for activities and due date." +msgstr "" + +#: ../../content/applications/sales/crm/track_leads/unattended_leads_report.rst:98 +msgid "Then, click into then next field and select :guilabel:`<=` from the drop-down menu. Selecting this operator includes all activities with a due date up to, and including, the date selected in the next field." +msgstr "" + +#: ../../content/applications/sales/crm/track_leads/unattended_leads_report.rst:102 +msgid "The third field can be left as today's date, or adjusted as needed." +msgstr "" + +#: ../../content/applications/sales/crm/track_leads/unattended_leads_report.rst:109 +msgid "After filtering for activities, add a :guilabel:`New Rule`. Then, click into the first field for the new rule, and type `Salesperson` in the :guilabel:`Search...` bar, or scroll to search through the list to locate it." +msgstr "" + +#: ../../content/applications/sales/crm/track_leads/unattended_leads_report.rst:119 +msgid "Add a Sales team" +msgstr "" + +#: ../../content/applications/sales/crm/track_leads/unattended_leads_report.rst:122 +msgid "This filter is optional. To view results for the entire company, do **not** add this filter, and continue to :ref:`View results `" +msgstr "" + +#: ../../content/applications/sales/crm/track_leads/unattended_leads_report.rst:140 +msgid "An example of the **Add Custom Filter** pop-up window with all of the rules configured." +msgstr "" + +#: ../../content/applications/sales/crm/track_leads/unattended_leads_report.rst:156 +msgid "After the filters are configured, click :guilabel:`Add`. The resulting report displays all leads assigned to a salesperson where an activity is past due, or is due on the current date. The default display is a bar graph, where the leads are grouped by *stage*." +msgstr "" + +#: ../../content/applications/sales/crm/track_leads/unattended_leads_report.rst:160 +msgid "To group the results by salesperson, click the :guilabel:`🔻(triangle pointed down)` icon to the right of the :guilabel:`Search...` bar to open the drop-down menu that contains :guilabel:`Filters`, :guilabel:`Group By`, and :guilabel:`Favorites` columns. Under the :guilabel:`Group By` heading, select :guilabel:`Salesperson`." +msgstr "" + +#: ../../content/applications/sales/crm/track_leads/unattended_leads_report.rst:166 +msgid "The option to group by :guilabel:`Sales Team` is also available under the :guilabel:`Group By` heading." +msgstr "" + +#: ../../content/applications/sales/crm/track_leads/unattended_leads_report.rst:169 +msgid "To change to a *list* view, click the :guilabel:`≣ (list)` icon in the top-right corner of the screen." +msgstr "" + +#: ../../content/applications/sales/crm/track_leads/unattended_leads_report.rst:173 +msgid "Clicking the :guilabel:`(toggle) icon` opens a drop-down menu of additional columns that can be added to the report." +msgstr "" + +#: ../../content/applications/sales/crm/track_leads/unattended_leads_report.rst:176 +msgid "Some options that are beneficial for this report include:" +msgstr "" + +#: ../../content/applications/sales/crm/track_leads/unattended_leads_report.rst:178 +msgid ":guilabel:`Activities`: the summary of the latest activity for this lead." +msgstr "" + +#: ../../content/applications/sales/crm/track_leads/unattended_leads_report.rst:179 +msgid ":guilabel:`Expected Closing`: the estimated date on which the lead will be won." +msgstr "" + +#: ../../content/applications/sales/crm/track_leads/unattended_leads_report.rst:180 +msgid ":guilabel:`Probability`: estimated success rate based on the stage." +msgstr "" + +#: ../../content/applications/sales/crm/track_leads/unattended_leads_report.rst:187 +msgid ":doc:`Activities <../../../essentials/activities>`" +msgstr "" + #: ../../content/applications/sales/point_of_sale.rst:6 msgid "Point of Sale" msgstr "" @@ -2359,7 +3027,7 @@ msgid "`Odoo Tutorials: Point of Sale Tutorials `" +msgid ":doc:`IoT Boxes Documentations `" msgstr "" #: ../../content/applications/sales/point_of_sale.rst:19 @@ -2638,22 +3306,22 @@ msgid "Dropdown menu to select the POS in the app settings" msgstr "" #: ../../content/applications/sales/point_of_sale/configuration.rst:21 -msgid "These settings are available to users with the :doc:`access rights ` :guilabel:`Administration` set as :guilabel:`Settings`." +msgid "These settings are available to users with the :doc:`access rights ` :guilabel:`Administration` set as :guilabel:`Settings`." msgstr "" -#: ../../content/applications/sales/point_of_sale/configuration.rst:25 +#: ../../content/applications/sales/point_of_sale/configuration.rst:24 msgid "You can also configure some settings from the dashboard by clicking the vertical ellipsis button (:guilabel:`⋮`) on a POS card. Doing so opens a popup window, from which you can:" msgstr "" -#: ../../content/applications/sales/point_of_sale/configuration.rst:28 +#: ../../content/applications/sales/point_of_sale/configuration.rst:27 msgid ":doc:`Enable multiple employees to log in. `" msgstr "" -#: ../../content/applications/sales/point_of_sale/configuration.rst:29 -msgid ":doc:`Connect and set up an IoT box. <../../productivity/iot/config/pos>`" +#: ../../content/applications/sales/point_of_sale/configuration.rst:28 +msgid ":doc:`Connect and set up an IoT box. <../../general/iot/config/pos>`" msgstr "" -#: ../../content/applications/sales/point_of_sale/configuration.rst:30 +#: ../../content/applications/sales/point_of_sale/configuration.rst:29 msgid ":doc:`Connect and set up an ePOS printer. `" msgstr "" @@ -2661,15 +3329,15 @@ msgstr "" msgid "popup window to access quick settings in POS" msgstr "" -#: ../../content/applications/sales/point_of_sale/configuration.rst:36 -msgid "These settings are available to users with the :doc:`access rights ` :guilabel:`Point of Sale` set as :guilabel:`Administrator`." +#: ../../content/applications/sales/point_of_sale/configuration.rst:35 +msgid "These settings are available to users with the :doc:`access rights ` :guilabel:`Point of Sale` set as :guilabel:`Administrator`." msgstr "" -#: ../../content/applications/sales/point_of_sale/configuration.rst:41 +#: ../../content/applications/sales/point_of_sale/configuration.rst:39 msgid "Make products available" msgstr "" -#: ../../content/applications/sales/point_of_sale/configuration.rst:43 +#: ../../content/applications/sales/point_of_sale/configuration.rst:41 msgid "To make products available for sale, go to :menuselection:`Point of Sale --> Products --> Products`, and select a product to open the product form. In the :guilabel:`Sales` tab, enable :guilabel:`Available in POS`." msgstr "" @@ -2754,7 +3422,7 @@ msgid "TM-P80 (Wi-Fi® model)" msgstr "" #: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:32 -msgid "To work with Odoo, some models that can be used without an :doc:`IoT box <../../../productivity/iot/config/connect>` may require :doc:`the HTTPS protocol ` to establish a secure connection between the browser and the printer. However, trying to reach the printer's IP address using HTTPS leads to a warning page on most web browsers. In that case, you can temporarily :ref:`force the connection `, which allows you to reach the page in HTTPS and use the ePOS printer in Odoo as long as the browser window stays open." +msgid "To work with Odoo, some models that can be used without an :doc:`IoT box ` may require :doc:`the HTTPS protocol ` to establish a secure connection between the browser and the printer. However, trying to reach the printer's IP address using HTTPS leads to a warning page on most web browsers. In that case, you can temporarily :ref:`force the connection `, which allows you to reach the page in HTTPS and use the ePOS printer in Odoo as long as the browser window stays open." msgstr "" #: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:40 @@ -3235,7 +3903,7 @@ msgstr "" #: ../../content/applications/sales/point_of_sale/payment_methods.rst:25 #: ../../content/applications/sales/point_of_sale/payment_methods/terminals/adyen.rst:78 -#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/ingenico.rst:45 +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/ingenico.rst:46 #: ../../content/applications/sales/point_of_sale/payment_methods/terminals/six.rst:63 #: ../../content/applications/sales/point_of_sale/payment_methods/terminals/worldline.rst:72 msgid "Once the payment method is created, you can select it in your POS settings. To do so, go to the :ref:`POS' settings `, click :guilabel:`Edit`, and add the payment method under the :guilabel:`Payments` section." @@ -3366,7 +4034,7 @@ msgid "Click :guilabel:`Save` at the bottom of the screen to save changes." msgstr "" #: ../../content/applications/sales/point_of_sale/payment_methods/terminals/adyen.rst:67 -#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/ingenico.rst:36 +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/ingenico.rst:37 #: ../../content/applications/sales/point_of_sale/payment_methods/terminals/six.rst:53 #: ../../content/applications/sales/point_of_sale/payment_methods/terminals/stripe.rst:15 #: ../../content/applications/sales/point_of_sale/payment_methods/terminals/worldline.rst:63 @@ -3382,7 +4050,7 @@ msgid "Finally, fill in the mandatory fields with your :ref:`Adyen API key `." +msgid "Connecting an Ingenico Payment Terminal to Odoo is a feature that requires an IoT Box. For more information on how to connect an IoT Box to your database, please refer to the :doc:`IoT documentation `." msgstr "" -#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/ingenico.rst:22 +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/ingenico.rst:23 msgid "Configure the Lane/5000 for Ingenico BENELUX" msgstr "" -#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/ingenico.rst:24 +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/ingenico.rst:25 msgid "Click on the F button of the terminal, then go in the :menuselection:`PoS Menu --> Settings` and enter the settings password." msgstr "" -#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/ingenico.rst:27 +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/ingenico.rst:28 msgid "Now, click on connection change and TCP/IP. Type the IP of your *IoT Box* (you can find it on the form view of your IoT Box). Then, enter 9000 as port. The terminal will restart. Once it is done, go on your *IoT Box* form in Odoo and verify that the terminal has been found." msgstr "" -#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/ingenico.rst:38 +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/ingenico.rst:39 msgid "Enable the payment terminal :ref:`in the application settings ` and :doc:`create the related payment method <../../payment_methods>`. Set the journal type as :guilabel:`Bank` and select :guilabel:`Ingenico` in the :guilabel:`Use a Payment Terminal` field. Then, select your terminal device in the :guilabel:`Payment Terminal Device` field." msgstr "" -#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/ingenico.rst:52 +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/ingenico.rst:53 msgid "In your *PoS interface*, when processing a payment, select a *Payment Method* using a payment terminal. Check that the amount in the tendered column is the one that has to be sent to the payment terminal and click on *Send*. When the payment is successful, the status will change to *Payment Successful*." msgstr "" -#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/ingenico.rst:61 +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/ingenico.rst:62 msgid "If you want to cancel the payment request, click on cancel. You can still retry to send the payment request." msgstr "" -#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/ingenico.rst:64 +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/ingenico.rst:65 msgid "If there is any issue with the payment terminal, you can still force the payment using the *Force Done*. This will allow you to validate the order in Odoo even if the connection between the terminal and Odoo has issues." msgstr "" -#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/ingenico.rst:70 +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/ingenico.rst:71 msgid "This option will only be available if you received an error message telling you the connection failed." msgstr "" -#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/ingenico.rst:73 +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/ingenico.rst:74 msgid "Once your payment is processed, on the payment record, you’ll find the type of card that has been used and the transaction ID." msgstr "" @@ -3495,7 +4163,7 @@ msgid "Connect an IoT box" msgstr "" #: ../../content/applications/sales/point_of_sale/payment_methods/terminals/six.rst:29 -msgid "Connecting a Six payment terminal to Odoo is requires :doc:`using a Raspberry Pi or virtual (for Windows OS only) IoT box `." +msgid "Connecting a Six payment terminal to Odoo is requires :doc:`using a Raspberry Pi or virtual (for Windows OS only) IoT box `." msgstr "" #: ../../content/applications/sales/point_of_sale/payment_methods/terminals/six.rst:33 @@ -3740,7 +4408,7 @@ msgid "Please note that Worldline is currently only available in the Benelux." msgstr "" #: ../../content/applications/sales/point_of_sale/payment_methods/terminals/worldline.rst:17 -msgid "Connecting a Worldline Payment Terminal to Odoo is a feature that requires an IoT Box. For more information on how to connect one to your database, please refer to the :doc:`IoT documentation `." +msgid "Connecting a Worldline Payment Terminal to Odoo is a feature that requires an IoT Box. For more information on how to connect one to your database, please refer to the :doc:`IoT documentation `." msgstr "" #: ../../content/applications/sales/point_of_sale/payment_methods/terminals/worldline.rst:22 @@ -4705,11 +5373,11 @@ msgid "If you use an Epson printer that does not need an IoT box, select :guilab msgstr "" #: ../../content/applications/sales/point_of_sale/restaurant/kitchen_printing.rst:43 -msgid ":doc:`../../../productivity/iot/config/connect`" +msgid ":doc:`/applications/general/iot/config/connect`" msgstr "" #: ../../content/applications/sales/point_of_sale/restaurant/kitchen_printing.rst:44 -msgid ":doc:`../../../productivity/iot/devices/printer`" +msgid ":doc:`/applications/general/iot/devices/printer`" msgstr "" #: ../../content/applications/sales/point_of_sale/restaurant/kitchen_printing.rst:45 @@ -4910,6 +5578,58 @@ msgstr "" msgid "You can also use a barcode scanner to log your employees. To do so, :ref:`restrict access ` to the POS and :ref:`use barcodes to log your employees in ` your POS." msgstr "" +#: ../../content/applications/sales/point_of_sale/shop/customer_display.rst:3 +msgid "Customer display" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/shop/customer_display.rst:5 +msgid "The **customer display** feature provides customers with real-time checkout updates on a secondary display." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/shop/customer_display.rst:-1 +msgid "customer screen" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/shop/customer_display.rst:14 +msgid "Depending on your POS setup, the feature can be displayed :ref:`locally on a secondary screen ` or on :ref:`another monitor connected to an IoT Box `." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/shop/customer_display.rst:18 +msgid "To activate the feature, go to the POS settings, scroll down to the :guilabel:`Connected Devices` section, and tick the :guilabel:`Customer Display` checkbox." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/shop/customer_display.rst:-1 +msgid "customer display setting checkbox" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/shop/customer_display.rst:27 +msgid "Local" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/shop/customer_display.rst:29 +msgid "Connect a second screen to your POS and :ref:`open a POS session `. Then, click :guilabel:`Customer Screen` to open a new window to drag and drop onto the second screen." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/shop/customer_display.rst:35 +msgid "IoT box" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/shop/customer_display.rst:37 +msgid "Connect an IoT box to your database and the second screen to the IoT box. Then, go to :menuselection:`Point of Sale --> Configuration --> Settings`, scroll down to the :guilabel:`Connected Devices` section, tick the :guilabel:`IoT Box` checkbox, and select the second monitor in the :guilabel:`Customer Display` field." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/shop/customer_display.rst:-1 +msgid "iot setting to connect a customer display" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/shop/customer_display.rst:46 +msgid "Both devices need to be connected to the same local network." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/shop/customer_display.rst:49 +msgid ":doc:`../../../general/iot/config/pos`" +msgstr "" + #: ../../content/applications/sales/point_of_sale/shop/sales_order.rst:3 msgid "Sales orders" msgstr "" @@ -4990,6 +5710,7 @@ msgstr "" msgid "You can import serial numbers in Point of Sale. To do so, select a **sales order** or a **quotation** containing tracked products. Then, agree to load the **Lots or Serial Numbers** linked to the :abbr:`SO (sales order)`." msgstr "" +#: ../../content/applications/sales/point_of_sale/shop/serial_numbers.rst:-1 #: ../../content/applications/sales/point_of_sale/shop/serial_numbers.rst:-1 msgid "Pop-up window for serial number import" msgstr "" @@ -5149,6 +5870,7 @@ msgstr "" msgid "To configure additional rental delay costs, availability of rental items, or minimum time of rental, navigate to :menuselection:`Rental app --> Configuration --> Settings`." msgstr "" +#: ../../content/applications/sales/rental.rst:-1 #: ../../content/applications/sales/rental.rst:-1 msgid "How the Settings page appears in the Odoo Rental application." msgstr "" @@ -5354,7 +6076,7 @@ msgid "The :guilabel:`Sign Documents` button/option **only** appears if the :gui msgstr "" #: ../../content/applications/sales/rental.rst:204 -msgid "This feature also requires the :doc:`Sign <../finance/sign>` app. If necessary, Odoo automatically installs it after activating the :guilabel:`Digital Documents` setting." +msgid "This feature also requires the :doc:`Sign <../productivity/sign>` app. If necessary, Odoo automatically installs it after activating the :guilabel:`Digital Documents` setting." msgstr "" #: ../../content/applications/sales/rental.rst:207 @@ -6243,7 +6965,7 @@ msgid "To use images in the listing, another option is to add them as *Attachmen msgstr "" #: ../../content/applications/sales/sales/ebay_connector/manage.rst:62 -msgid "For more information on template configuration in Odoo visit: :doc:`../../../general/email_communication/email_template`." +msgid "For more information on template configuration in Odoo visit: :doc:`../../../general/companies/email_template`." msgstr "" #: ../../content/applications/sales/sales/ebay_connector/manage.rst:66 @@ -6906,7 +7628,7 @@ msgid "If the company uses Odoo on Odoo.com or Odoo.sh platform, the code is alr msgstr "" #: ../../content/applications/sales/sales/ebay_connector/troubleshooting.rst:43 -msgid "If the company uses Odoo with an on-premise setup or through a partner, then the administrator must update the installation as detailed in :doc:`this documentation page ` or by contacting an integrating partner." +msgid "If the company uses Odoo with an on-premise setup or through a partner, then the administrator must update the installation as detailed in :doc:`this documentation page ` or by contacting an integrating partner." msgstr "" #: ../../content/applications/sales/sales/ebay_connector/troubleshooting.rst:48 @@ -7284,6 +8006,7 @@ msgstr "" msgid "On the :guilabel:`Down Payment` product page, in the :guilabel:`General Information` tab, the customer taxes can be modified in the :guilabel:`Customer Taxes` field." msgstr "" +#: ../../content/applications/sales/sales/invoicing/down_payment.rst:-1 #: ../../content/applications/sales/sales/invoicing/down_payment.rst:-1 msgid "How to modify the income account link to down payments." msgstr "" @@ -7568,6 +8291,7 @@ msgstr "" msgid "When :guilabel:`Register Payment` is clicked, a :guilabel:`Register Payment` pop-up window appears. In this pop-up window, the necessary fields are auto-populated with the correct information. After reviewing the information, click :guilabel:`Create Payment`." msgstr "" +#: ../../content/applications/sales/sales/invoicing/expense.rst:-1 #: ../../content/applications/sales/sales/invoicing/expense.rst:-1 msgid "A register payment pop-up window on a customer invoice in Odoo Sales." msgstr "" @@ -7713,6 +8437,7 @@ msgstr "" msgid "On the product form, under the :guilabel:`General Information` tab, the :guilabel:`Product Type` field *must* be set on any of the following options: :guilabel:`Service`, :guilabel:`Event Ticket`, :guilabel:`Event Booth`, or :guilabel:`Course`." msgstr "" +#: ../../content/applications/sales/sales/invoicing/milestone.rst:-1 #: ../../content/applications/sales/sales/invoicing/milestone.rst:-1 msgid "The invoicing policy field drop-down menu with options on product form." msgstr "" @@ -8907,6 +9632,7 @@ msgstr "" msgid "Once the *Accounting* app has been installed, foreign currencies can be added to the database. Navigate to :menuselection:`Accounting app --> Configuration --> Settings`, scroll to the :guilabel:`Currencies` section, and locate the :guilabel:`Main Currency` setting." msgstr "" +#: ../../content/applications/sales/sales/products_prices/prices/currencies.rst:-1 #: ../../content/applications/sales/sales/products_prices/prices/currencies.rst:-1 msgid "How the main currency feature appears on settings page in Odoo Accounting." msgstr "" @@ -9674,6 +10400,7 @@ msgstr "" msgid "From this drop-down menu, select the :guilabel:`Import records` option." msgstr "" +#: ../../content/applications/sales/sales/products_prices/products/import.rst:-1 #: ../../content/applications/sales/sales/products_prices/products/import.rst:-1 msgid "The Import records option selectable from the gear icon on the Products page in Odoo Sales." msgstr "" @@ -11053,6 +11780,7 @@ msgstr "" msgid "Click the :guilabel:`Preview` button, located in the upper-left corner of the quotation, to reveal a preview of the quotation customers would receive, via email, along with the optional products they can potentially add to their order, located in the :guilabel:`Options` section." msgstr "" +#: ../../content/applications/sales/sales/send_quotations/optional_products.rst:-1 #: ../../content/applications/sales/sales/send_quotations/optional_products.rst:-1 msgid "Preview your quotations on Odoo Sales." msgstr "" @@ -11834,58 +12562,62 @@ msgid ":doc:`/applications/sales/subscriptions/automatic_alerts`" msgstr "" #: ../../content/applications/sales/subscriptions.rst:23 +msgid ":doc:`/applications/sales/subscriptions/scheduled_actions`" +msgstr "" + +#: ../../content/applications/sales/subscriptions.rst:24 msgid ":doc:`/applications/sales/subscriptions/reports`" msgstr "" -#: ../../content/applications/sales/subscriptions.rst:28 +#: ../../content/applications/sales/subscriptions.rst:29 msgid "Subscription quotations" msgstr "" -#: ../../content/applications/sales/subscriptions.rst:31 +#: ../../content/applications/sales/subscriptions.rst:32 msgid "Sales orders with a defined recurrence become subscriptions." msgstr "" -#: ../../content/applications/sales/subscriptions.rst:33 +#: ../../content/applications/sales/subscriptions.rst:34 msgid "To create a new subscription, click on :guilabel:`New` from the *Subscription* or the :doc:`Sales ` app. You can either:" msgstr "" -#: ../../content/applications/sales/subscriptions.rst:36 +#: ../../content/applications/sales/subscriptions.rst:37 msgid "Select a :doc:`subscription plan ` to prefill the quotation instantly, or" msgstr "" -#: ../../content/applications/sales/subscriptions.rst:38 +#: ../../content/applications/sales/subscriptions.rst:39 msgid "Fill out the quotation normally, making sure to select a recurrence and an end date if necessary and adding :doc:`recurrent products `." msgstr "" -#: ../../content/applications/sales/subscriptions.rst:42 +#: ../../content/applications/sales/subscriptions.rst:43 msgid "You can define different invoice and delivery addresses by enabling the :doc:`Customer Addresses ` feature." msgstr "" -#: ../../content/applications/sales/subscriptions.rst:48 +#: ../../content/applications/sales/subscriptions.rst:49 msgid "Confirmation" msgstr "" -#: ../../content/applications/sales/subscriptions.rst:50 +#: ../../content/applications/sales/subscriptions.rst:51 msgid "Send the quotation to the customer for confirmation by clicking on :guilabel:`Send by email`, or confirm it immediately by clicking on :guilabel:`Confirm`." msgstr "" -#: ../../content/applications/sales/subscriptions.rst:54 +#: ../../content/applications/sales/subscriptions.rst:55 msgid "Click on :guilabel:`Customer Preview` to preview the customer portal where the customer can view their quotation, sign and pay it, and communicate with you." msgstr "" -#: ../../content/applications/sales/subscriptions.rst:60 +#: ../../content/applications/sales/subscriptions.rst:61 msgid "Automatic payments" msgstr "" -#: ../../content/applications/sales/subscriptions.rst:62 +#: ../../content/applications/sales/subscriptions.rst:63 msgid "You can require the customer to set an automatic payment method and pre-pay the subscription's first occurrence before they can confirm their quotation. To do so, go to the :guilabel:`Other Info` tab of the quotation and check the :guilabel:`Payment` option in the :guilabel:`Online confirmation` field." msgstr "" -#: ../../content/applications/sales/subscriptions.rst:67 +#: ../../content/applications/sales/subscriptions.rst:68 msgid "If you leave :guilabel:`Payment` unchecked, the customer doesn't have to pre-pay to start the subscription. This means that the payment is not automatic and that the customer must pay each invoice manually." msgstr "" -#: ../../content/applications/sales/subscriptions.rst:72 +#: ../../content/applications/sales/subscriptions.rst:73 msgid "If the online confirmation requires a pre-payment, your customer can select only the :ref:`payment providers ` that have the :ref:`tokenization feature `. This ensures that the customer is automatically charged at each new period." msgstr "" @@ -12121,6 +12853,7 @@ msgstr "" #: ../../content/applications/sales/subscriptions/closing.rst:105 #: ../../content/applications/sales/subscriptions/renewals.rst:85 #: ../../content/applications/sales/subscriptions/reports.rst:406 +#: ../../content/applications/sales/subscriptions/scheduled_actions.rst:182 #: ../../content/applications/sales/subscriptions/upselling.rst:103 msgid ":doc:`../subscriptions`" msgstr "" @@ -12129,6 +12862,7 @@ msgstr "" #: ../../content/applications/sales/subscriptions/closing.rst:106 #: ../../content/applications/sales/subscriptions/renewals.rst:86 #: ../../content/applications/sales/subscriptions/reports.rst:407 +#: ../../content/applications/sales/subscriptions/scheduled_actions.rst:183 #: ../../content/applications/sales/subscriptions/upselling.rst:104 msgid ":doc:`plans`" msgstr "" @@ -12137,6 +12871,7 @@ msgstr "" #: ../../content/applications/sales/subscriptions/closing.rst:107 #: ../../content/applications/sales/subscriptions/renewals.rst:87 #: ../../content/applications/sales/subscriptions/reports.rst:408 +#: ../../content/applications/sales/subscriptions/scheduled_actions.rst:184 #: ../../content/applications/sales/subscriptions/upselling.rst:105 msgid ":doc:`products`" msgstr "" @@ -12355,7 +13090,7 @@ msgid ":guilabel:`Online Confirmation`: Check the boxes next to :guilabel:`Signa msgstr "" #: ../../content/applications/sales/subscriptions/plans.rst:32 -msgid ":guilabel:`Confirmation Mail`: Select an :doc:`email template ` for the confirmation email that is automatically sent to the customer after the quotation is confirmed. Leave this field blank to send nothing." +msgid ":guilabel:`Confirmation Mail`: Select an :doc:`email template ` for the confirmation email that is automatically sent to the customer after the quotation is confirmed. Leave this field blank to send nothing." msgstr "" #: ../../content/applications/sales/subscriptions/plans.rst:37 @@ -12698,6 +13433,7 @@ msgstr "" msgid "When the :guilabel:`Renew` button is clicked, Odoo instantly presents a new renewal quotation, complete with a :guilabel:`Renewal Quotation` tag." msgstr "" +#: ../../content/applications/sales/subscriptions/renewals.rst:-1 #: ../../content/applications/sales/subscriptions/renewals.rst:-1 msgid "Renewal quotation in the Odoo Subscriptions application." msgstr "" @@ -12858,10 +13594,6 @@ msgstr "" msgid "Each view has its own series of related view-specific visual options." msgstr "" -#: ../../content/applications/sales/subscriptions/reports.rst:97 -msgid "Graph view" -msgstr "" - #: ../../content/applications/sales/subscriptions/reports.rst:99 msgid "With the graph view selected, the following options appear between the search bar and visual representation of the data. These graph-specific options are located to the right of the :guilabel:`Measures` and :guilabel:`Insert in Spreadsheet` buttons." msgstr "" @@ -12925,10 +13657,6 @@ msgstr "" msgid "When the :guilabel:`Pie Chart` graph view is selected, there are no additional visual options." msgstr "" -#: ../../content/applications/sales/subscriptions/reports.rst:135 -msgid "Pivot view" -msgstr "" - #: ../../content/applications/sales/subscriptions/reports.rst:137 msgid "With the pivot view selected, the subscription metrics are displayed in a data table, which can be fully customized." msgstr "" @@ -12961,10 +13689,6 @@ msgstr "" msgid ":guilabel:`Download xlsx`: the pivot data table is downloaded as an .xlsx file." msgstr "" -#: ../../content/applications/sales/subscriptions/reports.rst:158 -msgid "List view" -msgstr "" - #: ../../content/applications/sales/subscriptions/reports.rst:160 msgid "With the list view selected, the subscription metrics being analyzed are displayed in a simple list, which can be fully customized by using any of the available filters in the drop-down filter menu (accessible via the :guilabel:`▼ (downward facing arrow)` icon to the right of the search bar)." msgstr "" @@ -13232,6 +13956,7 @@ msgstr "" msgid "There is also a default filter in the search bar for :guilabel:`Event Date: Month > Event Type`." msgstr "" +#: ../../content/applications/sales/subscriptions/reports.rst:-1 #: ../../content/applications/sales/subscriptions/reports.rst:-1 msgid "The default appearance of the MRR Breakdown reporting page in Odoo Subscriptions." msgstr "" @@ -13296,6 +14021,7 @@ msgstr "" msgid "There is also a default filter in the search bar for :guilabel:`Event Date: Month`." msgstr "" +#: ../../content/applications/sales/subscriptions/reports.rst:-1 #: ../../content/applications/sales/subscriptions/reports.rst:-1 msgid "The default appearance of the MRR Analysis reporting page in Odoo Subscriptions." msgstr "" @@ -13308,6 +14034,234 @@ msgstr "" msgid "The metric-related options in the :guilabel:`Measures` drop-down menu on the :guilabel:`MRR Analysis` reporting page are:" msgstr "" +#: ../../content/applications/sales/subscriptions/scheduled_actions.rst:3 +msgid "Scheduled actions" +msgstr "" + +#: ../../content/applications/sales/subscriptions/scheduled_actions.rst:5 +msgid "*Scheduled actions* are pre-configured processes that allow users to automate certain tasks within a database, based on a designated schedule or number of occurrences. These tasks can include sending emails, generating invoices, data clean-up, and so much more." +msgstr "" + +#: ../../content/applications/sales/subscriptions/scheduled_actions.rst:9 +msgid "In Odoo, some scheduled actions are active, by default, to ensure that certain functions are triggered automatically, however there are *also* many scheduled action options that appear in the database that are **not** activated by default." +msgstr "" + +#: ../../content/applications/sales/subscriptions/scheduled_actions.rst:13 +msgid "In Odoo *Subscriptions*, there are two scheduled actions that initiate the billing process for active recurring subscriptions, as well as when billing should stop due to subscription expiration." +msgstr "" + +#: ../../content/applications/sales/subscriptions/scheduled_actions.rst:16 +msgid "They are turned on, by default and can be deactivated at any time in order to manage subscriptions manually." +msgstr "" + +#: ../../content/applications/sales/subscriptions/scheduled_actions.rst:20 +msgid "Access scheduled actions" +msgstr "" + +#: ../../content/applications/sales/subscriptions/scheduled_actions.rst:23 +msgid "In order to access scheduled actions, :ref:`developer mode ` **must** be activated." +msgstr "" + +#: ../../content/applications/sales/subscriptions/scheduled_actions.rst:26 +msgid "With developer mode activated, navigate to :menuselection:`Settings app --> Technical --> Scheduled Actions`." +msgstr "" + +#: ../../content/applications/sales/subscriptions/scheduled_actions.rst:-1 +msgid "The scheduled actions option under the technical menu in the Odoo Settings application." +msgstr "" + +#: ../../content/applications/sales/subscriptions/scheduled_actions.rst:33 +msgid "Doing so reveals a dedicated :guilabel:`Scheduled Actions` dashboard. On this page, there is a complete list of scheduled actions for the entire database." +msgstr "" + +#: ../../content/applications/sales/subscriptions/scheduled_actions.rst:36 +msgid "From here, enter `Subscription` in the search bar. Doing so provides three subscription-specific results. The following documentation focuses on the last two results in the list:" +msgstr "" + +#: ../../content/applications/sales/subscriptions/scheduled_actions.rst:39 +msgid ":guilabel:`Sale Subscription: generate recurring invoices and payments`" +msgstr "" + +#: ../../content/applications/sales/subscriptions/scheduled_actions.rst:40 +msgid ":guilabel:`Sale Subscription: subscriptions expiration`" +msgstr "" + +#: ../../content/applications/sales/subscriptions/scheduled_actions.rst:-1 +msgid "The subscription-related results on the scheduled actions page in Odoo Settings." +msgstr "" + +#: ../../content/applications/sales/subscriptions/scheduled_actions.rst:46 +msgid "Determine if a scheduled action is active by looking under the :guilabel:`Active` column, in the it's corresponding row on the :guilabel:`Scheduled Actions` dashboard, for a ticked checkbox; if the checkbox is green with a check mark, the scheduled action is active." +msgstr "" + +#: ../../content/applications/sales/subscriptions/scheduled_actions.rst:50 +msgid "If a scheduled action needs to be activated, click into the desired scheduled action from the list." +msgstr "" + +#: ../../content/applications/sales/subscriptions/scheduled_actions.rst:-1 +msgid "The scheduled action form in the Odoo Settings application." +msgstr "" + +#: ../../content/applications/sales/subscriptions/scheduled_actions.rst:55 +msgid "Then, from the scheduled action form, toggle the switch in the :guilabel:`Active` field to the right. Doing so turns the switch green, indicating that the scheduled action is now `Active`." +msgstr "" + +#: ../../content/applications/sales/subscriptions/scheduled_actions.rst:58 +msgid "The ability to set up how often the scheduled action runs is also available on the scheduled action form, in the :guilabel:`Execute Every` field." +msgstr "" + +#: ../../content/applications/sales/subscriptions/scheduled_actions.rst:62 +msgid "The scheduled action does **not** function correctly if the execution time is less than five minutes. This is a general rule for all scheduled actions." +msgstr "" + +#: ../../content/applications/sales/subscriptions/scheduled_actions.rst:65 +msgid "For more information, read the :doc:`Frequent Technical Questions ` documentation." +msgstr "" + +#: ../../content/applications/sales/subscriptions/scheduled_actions.rst:69 +msgid "Generate recurring invoices and payments" +msgstr "" + +#: ../../content/applications/sales/subscriptions/scheduled_actions.rst:71 +msgid "In order for the :guilabel:`Sale Subscription: generate recurring invoices and payments` scheduled action to properly generate recurring invoices and payments on subscriptions, the *Deferred Expense* and *Deferred Revenue* accounts **must** be set up, in order for Odoo to process various invoices and payments related to subscriptions." +msgstr "" + +#: ../../content/applications/sales/subscriptions/scheduled_actions.rst:76 +msgid "To set up *Deferred Expense* and *Deferred Revenue* accounts, navigate to :menuselection:`Accounting app --> Configuration --> Settings`. Both accounts can be configured in the :guilabel:`Default Accounts` section." +msgstr "" + +#: ../../content/applications/sales/subscriptions/scheduled_actions.rst:-1 +msgid "The necessary deferred account settings in the Odoo Accounting app's settings page." +msgstr "" + +#: ../../content/applications/sales/subscriptions/scheduled_actions.rst:84 +msgid "Once the correct accounts are entered in the :guilabel:`Deferred Expense` and :guilabel:`Deferred Revenue` drop-down menu fields, click :guilabel:`Save` in the upper-left corner." +msgstr "" + +#: ../../content/applications/sales/subscriptions/scheduled_actions.rst:88 +msgid "Create invoice" +msgstr "" + +#: ../../content/applications/sales/subscriptions/scheduled_actions.rst:90 +msgid "Elements related to the :guilabel:`Sale Subscription: generate recurring invoices and payments` scheduled action can be found on confirmed subscription sales orders." +msgstr "" + +#: ../../content/applications/sales/subscriptions/scheduled_actions.rst:93 +msgid "To examine these elements, open any confirmed sales order in the *Subscriptions* application to reveal the subscription sales order form." +msgstr "" + +#: ../../content/applications/sales/subscriptions/scheduled_actions.rst:96 +msgid "On a confirmed subscription sales order form, focus on the :guilabel:`Recurring Plan` and :guilabel:`Date of Next Invoice` fields." +msgstr "" + +#: ../../content/applications/sales/subscriptions/scheduled_actions.rst:-1 +msgid "A confirmed subscription sales order in the Odoo Subscriptions application." +msgstr "" + +#: ../../content/applications/sales/subscriptions/scheduled_actions.rst:103 +msgid "The scheduled action creates an invoice when today's date is the same date as the :guilabel:`Date of Next Invoice`." +msgstr "" + +#: ../../content/applications/sales/subscriptions/scheduled_actions.rst:106 +msgid "Odoo uses the information in the :guilabel:`Recurring Plan` field to update the next invoice date accordingly." +msgstr "" + +#: ../../content/applications/sales/subscriptions/scheduled_actions.rst:110 +msgid "If there is no payment provider set up, Odoo does **not** create an invoice, and the customer is not charged. Instead, the subscription is processed as a free recurring product, and is reflected as such in the *chatter* of the subscription sales order. When this occurs, the following message appears: `Automatic renewal succeeded. Free subscription. Next invoice:[date]. No email sent.`" +msgstr "" + +#: ../../content/applications/sales/subscriptions/scheduled_actions.rst:115 +msgid "Once the invoice for the subscription sales order is created, the invoice can be viewed by clicking the :guilabel:`Invoices` smart button that appears at the top of the subscription sales order." +msgstr "" + +#: ../../content/applications/sales/subscriptions/scheduled_actions.rst:118 +msgid "An email is sent to the customer notifying them of the recurring subscription charge, *if* there is a :guilabel:`Payment Token` on the account." +msgstr "" + +#: ../../content/applications/sales/subscriptions/scheduled_actions.rst:121 +msgid "To check if there is a :guilabel:`Payment Token`, open the :guilabel:`Other Info` tab, and look at the :guilabel:`Payment Token` field, under the :guilabel:`Subscription` section." +msgstr "" + +#: ../../content/applications/sales/subscriptions/scheduled_actions.rst:-1 +msgid "The Payment Token field under the Other Info tab on a subscription sales order form." +msgstr "" + +#: ../../content/applications/sales/subscriptions/scheduled_actions.rst:128 +msgid "If there is no :guilabel:`Payment Token` (i.e. payment provider is `Bank Transfer`), the invoice is created and sent to the customer. The payment **must** be registered manually in this case." +msgstr "" + +#: ../../content/applications/sales/subscriptions/scheduled_actions.rst:132 +msgid "Closing invoices" +msgstr "" + +#: ../../content/applications/sales/subscriptions/scheduled_actions.rst:134 +msgid "The :guilabel:`Sale Subscription: generate recurring invoices and payments` scheduled action also has the ability to close a subscription, if the following conditions are met:" +msgstr "" + +#: ../../content/applications/sales/subscriptions/scheduled_actions.rst:137 +msgid "If the subscription has no :guilabel:`Payment Token`, create and post the invoice." +msgstr "" + +#: ../../content/applications/sales/subscriptions/scheduled_actions.rst:138 +msgid "If the subscription has a :guilabel:`Payment Token`, try to charge." +msgstr "" + +#: ../../content/applications/sales/subscriptions/scheduled_actions.rst:140 +msgid "If the charge is successful, create and post the invoice." +msgstr "" + +#: ../../content/applications/sales/subscriptions/scheduled_actions.rst:141 +msgid "If the charge fails, send reminders periodically." +msgstr "" + +#: ../../content/applications/sales/subscriptions/scheduled_actions.rst:143 +msgid "Close the subscription if it continues to fail for more than fourteen days." +msgstr "" + +#: ../../content/applications/sales/subscriptions/scheduled_actions.rst:146 +msgid "Subscriptions expiration" +msgstr "" + +#: ../../content/applications/sales/subscriptions/scheduled_actions.rst:148 +msgid "The :guilabel:`Sale Subscription: subscriptions expiration` scheduled action checks for all other conditions that may cause a subscription to close automatically. If certain conditions are met, the scheduled action closes that subscription." +msgstr "" + +#: ../../content/applications/sales/subscriptions/scheduled_actions.rst:152 +msgid "First, the :guilabel:`Sale Subscription: subscriptions expiration` scheduled action checks to see if the end date has passed, which is configured on the subscription sales order." +msgstr "" + +#: ../../content/applications/sales/subscriptions/scheduled_actions.rst:-1 +msgid "The expiration date on a subscription sales order in Odoo Subscriptions." +msgstr "" + +#: ../../content/applications/sales/subscriptions/scheduled_actions.rst:159 +msgid "Then, the :guilabel:`Sale Subscription: subscriptions expiration` scheduled action checks if the invoice has not been paid within the payment terms deadline." +msgstr "" + +#: ../../content/applications/sales/subscriptions/scheduled_actions.rst:162 +msgid "To access the invoices attached to a subscription, access the sales order for the subscription product, and click the :guilabel:`Invoices` smart button. Then, look at the :guilabel:`Invoice Date` column." +msgstr "" + +#: ../../content/applications/sales/subscriptions/scheduled_actions.rst:-1 +msgid "The Invoice Date column on subscriptions invoice page in Odoo Subscriptions app." +msgstr "" + +#: ../../content/applications/sales/subscriptions/scheduled_actions.rst:170 +msgid "Unpaid subscriptions with an :guilabel:`Invoice Date` that are past the determined number of days in the :guilabel:`Automatic Closing` field of a :guilabel:`Recurring Plan` are automatically closed by the :guilabel:`Sale Subscription: subscriptions expiration` scheduled action." +msgstr "" + +#: ../../content/applications/sales/subscriptions/scheduled_actions.rst:-1 +msgid "The Automatic Closing field on a Recurring Plan form in Odoo Subscriptions." +msgstr "" + +#: ../../content/applications/sales/subscriptions/scheduled_actions.rst:178 +msgid "For example, if the next invoice date is July 1st, and the :guilabel:`Automatic Closing` is set to '30 Days', the scheduled action would close the subscription on August 1st." +msgstr "" + +#: ../../content/applications/sales/subscriptions/scheduled_actions.rst:185 +msgid ":doc:`automatic_alerts`" +msgstr "" + #: ../../content/applications/sales/subscriptions/upselling.rst:3 #: ../../content/applications/sales/subscriptions/upselling.rst:44 msgid "Upsell subscriptions" diff --git a/locale/sources/services.pot b/locale/sources/services.pot index 15e1ec4ea..d5a38a6e4 100644 --- a/locale/sources/services.pot +++ b/locale/sources/services.pot @@ -8,7 +8,7 @@ msgid "" msgstr "" "Project-Id-Version: Odoo 17.0\n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2024-03-08 12:48+0000\n" +"POT-Creation-Date: 2024-03-25 16:01+0000\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME \n" "Language-Team: LANGUAGE \n" @@ -730,11 +730,11 @@ msgid "Track and bill time" msgstr "" #: ../../content/applications/services/helpdesk/advanced/track_and_bill.rst:5 -msgid "Odoo *Helpdesk* provides teams with the ability to track the amount of hours spent working on a ticket, and to bill a customer for that time. Through integrations with the *Sales*, *Timesheets* and *Accounting* applications, customers can be charged once the work is completed, or before it has even begun." +msgid "Odoo *Helpdesk* provides teams with the ability to track the amount of hours spent working on a ticket, and to bill a customer for that time. Through integrations with the *Sales*, *Timesheets*, *Project* and *Accounting* applications, customers can be charged once the work is completed, or before it has even begun." msgstr "" #: ../../content/applications/services/helpdesk/advanced/track_and_bill.rst:11 -msgid "Since the *Track & Bill Time* features require integration with other applications, enabling them may result in the installation of additional modules (or applications)." +msgid "Since the *Track & Bill Time* features require integration with other applications, enabling them may result in the installation of additional modules or applications." msgstr "" #: ../../content/applications/services/helpdesk/advanced/track_and_bill.rst:14 @@ -746,7 +746,7 @@ msgid "Configure track and bill time features" msgstr "" #: ../../content/applications/services/helpdesk/advanced/track_and_bill.rst:21 -msgid "Before a customer can be invoiced for support services, the *Track & Bill Time* features must first be enabled. These features must be enabled on each *Helpdesk* team where they will be utilized." +msgid "Before a customer can be invoiced for support services, the *Track & Bill Time* features **must** be enabled on each *Helpdesk* team individually." msgstr "" #: ../../content/applications/services/helpdesk/advanced/track_and_bill.rst:25 @@ -754,54 +754,58 @@ msgid "Enable track and bill time on a helpdesk team" msgstr "" #: ../../content/applications/services/helpdesk/advanced/track_and_bill.rst:27 -msgid "To view and enable the :guilabel:`Track & Bill Time` features on a *Helpdesk* team, first navigate to :menuselection:`Helpdesk --> Configuration --> Teams`. Then select a team from the list or :doc:`create a new one `. This will reveal a team's settings page." +msgid "To view and enable the *Track & Bill Time* features on a *Helpdesk* team, first navigate to :menuselection:`Helpdesk app --> Configuration --> Helpdesk Teams`. Then, select a team from the list, or create a :doc:`new one <../overview/getting_started>`. This reveals a team's settings page." msgstr "" -#: ../../content/applications/services/helpdesk/advanced/track_and_bill.rst:32 +#: ../../content/applications/services/helpdesk/advanced/track_and_bill.rst:31 msgid "On the team's settings page, scroll to the :guilabel:`Track & Bill Time` section. Check the boxes labeled :guilabel:`Timesheets` and :guilabel:`Time Billing`." msgstr "" -#: ../../content/applications/services/helpdesk/advanced/track_and_bill.rst:35 +#: ../../content/applications/services/helpdesk/advanced/track_and_bill.rst:34 msgid "Once the :guilabel:`Timesheets` box is checked, a new field appears, labeled :guilabel:`Project`." msgstr "" #: ../../content/applications/services/helpdesk/advanced/track_and_bill.rst:37 -msgid "The project selected in this field is where all the timesheets for this team's tickets will be recorded. Click into the drop-down menu to select a :guilabel:`Project`." +msgid "If this is the first time this feature has been enabled on this database, the page may need to be manually saved and refreshed before the :guilabel:`Project` field appears." msgstr "" #: ../../content/applications/services/helpdesk/advanced/track_and_bill.rst:40 -msgid "To create a new project where the timesheets will be recorded, click into the drop-down menu, type a name for the project, and then click :guilabel:`Create`." +msgid "The project selected in this field represents where all the timesheets for this team's tickets are recorded. Click into the :guilabel:`Project` drop-down menu to select a project." +msgstr "" + +#: ../../content/applications/services/helpdesk/advanced/track_and_bill.rst:43 +msgid "To create a new project where the timesheets are recorded, click into the :guilabel:`Project` drop-down menu, type a name for the project, and then click :guilabel:`Create` from the drop-down menu beneath." msgstr "" #: ../../content/applications/services/helpdesk/advanced/track_and_bill.rst:-1 msgid "View of a helpdesk team settings page emphasizing the track and bill time settings." msgstr "" -#: ../../content/applications/services/helpdesk/advanced/track_and_bill.rst:50 +#: ../../content/applications/services/helpdesk/advanced/track_and_bill.rst:54 msgid "Configure service products" msgstr "" -#: ../../content/applications/services/helpdesk/advanced/track_and_bill.rst:52 -msgid "When the :guilabel:`Time Billing` feature is enabled, a new product is created in the *Sales* app called :guilabel:`Service on Timesheets`. This product can be found under :menuselection:`Sales --> Products --> Products`. Search for `Service on Timesheets` in the :guilabel:`Search...` bar. This is the product that will be used when invoicing for *post-paid support services* after they have been completed." +#: ../../content/applications/services/helpdesk/advanced/track_and_bill.rst:56 +msgid "When the :guilabel:`Time Billing` feature is enabled, a new product is created in the *Sales* app called *Service on Timesheets*. This product can be found under :menuselection:`Sales app--> Products --> Products`. Then, search for `Service on Timesheets` in the :guilabel:`Search...` bar. This is the product that is used when invoicing for *post-paid support services* **after** they have been completed." msgstr "" -#: ../../content/applications/services/helpdesk/advanced/track_and_bill.rst:58 -msgid "Select :guilabel:`Service on Timesheets` from the product page. This reveals the product detail form. The product is configured with the :guilabel:`Product Type` set to :guilabel:`Service` and the :guilabel:`Invoicing Policy` set to :guilabel:`Based on Timesheets`." +#: ../../content/applications/services/helpdesk/advanced/track_and_bill.rst:62 +msgid "Select :guilabel:`Service on Timesheets` from the product page. This reveals the product detail form. The product is configured with the :guilabel:`Product Type` set to :guilabel:`Service` and the :guilabel:`Invoicing Policy` set to :guilabel:`Based on Timesheets`. Make any necessary changes to the product record, such as the :guilabel:`Cost` or :guilabel:`Sales Price`." msgstr "" #: ../../content/applications/services/helpdesk/advanced/track_and_bill.rst:-1 msgid "View of a service product with the invoicing policy set to 'Based on timesheets'." msgstr "" -#: ../../content/applications/services/helpdesk/advanced/track_and_bill.rst:66 -msgid "In order to invoice for support services before the work has been completed (also known as *prepaid support services*), a separate product with a different invoicing policy must be created." +#: ../../content/applications/services/helpdesk/advanced/track_and_bill.rst:71 +msgid "In order to invoice for support services **before** the work has been completed (also known as *prepaid support services*), a separate product with a different invoicing policy must be created." msgstr "" -#: ../../content/applications/services/helpdesk/advanced/track_and_bill.rst:69 -msgid "To create a new service product, go to :menuselection:`Sales --> Products --> Products` and click :guilabel:`New`. This will reveal a blank product detail form." +#: ../../content/applications/services/helpdesk/advanced/track_and_bill.rst:74 +msgid "To create a new service product, go to :menuselection:`Sales app --> Products --> Products`, and click :guilabel:`New`. This reveals a blank product detail form." msgstr "" -#: ../../content/applications/services/helpdesk/advanced/track_and_bill.rst:72 +#: ../../content/applications/services/helpdesk/advanced/track_and_bill.rst:77 msgid "On the new product form, add a :guilabel:`Product Name`, and set the :guilabel:`Product Type` to :guilabel:`Service`. Then, set the :guilabel:`Invoicing Policy` to :guilabel:`Prepaid/Fixed Price`. This means an invoice can be generated and payment can be received for this product before any timesheets entries have been recorded for these services." msgstr "" @@ -809,159 +813,159 @@ msgstr "" msgid "View of a service product with the invoicing policy set to 'prepaid/fixed'." msgstr "" -#: ../../content/applications/services/helpdesk/advanced/track_and_bill.rst:81 +#: ../../content/applications/services/helpdesk/advanced/track_and_bill.rst:86 msgid "Finally, set the :guilabel:`Sales Price`, and confirm that the :guilabel:`Unit of Measure` is set to :guilabel:`Hours`." msgstr "" -#: ../../content/applications/services/helpdesk/advanced/track_and_bill.rst:85 +#: ../../content/applications/services/helpdesk/advanced/track_and_bill.rst:90 msgid "Invoice prepaid support services" msgstr "" -#: ../../content/applications/services/helpdesk/advanced/track_and_bill.rst:87 -msgid "When support services are billed on a fixed price, an invoice can be created before any work is completed on the issue. In this case, a service product with the invoicing policy set to :guilabel:`Prepaid/Fixed Price` would be used, just like :ref:`the section above `." +#: ../../content/applications/services/helpdesk/advanced/track_and_bill.rst:92 +msgid "When support services are billed on a fixed price, an invoice can be created before any work is completed on the issue. In this case, a service product with the *Invoicing Policy* set to *Prepaid/Fixed Price* would be used, just like :ref:`the section above `." msgstr "" -#: ../../content/applications/services/helpdesk/advanced/track_and_bill.rst:93 +#: ../../content/applications/services/helpdesk/advanced/track_and_bill.rst:98 msgid "Create a sales order with prepaid product" msgstr "" -#: ../../content/applications/services/helpdesk/advanced/track_and_bill.rst:95 -msgid "To invoice a customer for prepaid support services, first create a sales order (SO) with the support services product. To do this, go to :menuselection:`Sales --> Orders --> Quotations --> New`, which reveals a blank quotation form." +#: ../../content/applications/services/helpdesk/advanced/track_and_bill.rst:100 +msgid "To invoice a customer for prepaid support services, first create a sales order (SO) with the support services product. To do this, go to :menuselection:`Sales app --> Orders --> Quotations`. Then, click :guilabel:`New` to reveal a blank quotation form." msgstr "" -#: ../../content/applications/services/helpdesk/advanced/track_and_bill.rst:99 +#: ../../content/applications/services/helpdesk/advanced/track_and_bill.rst:104 msgid "Then, fill out the quotation form with the customer information." msgstr "" -#: ../../content/applications/services/helpdesk/advanced/track_and_bill.rst:101 +#: ../../content/applications/services/helpdesk/advanced/track_and_bill.rst:106 msgid "Go to the :guilabel:`Order Lines` tab of the quotation and click :guilabel:`Add a Product`. Then, select the *prepaid services product* configured in the steps above. Update the :guilabel:`Quantity` field with the number of hours." msgstr "" -#: ../../content/applications/services/helpdesk/advanced/track_and_bill.rst:105 +#: ../../content/applications/services/helpdesk/advanced/track_and_bill.rst:110 msgid "After updating any other necessary information, :guilabel:`Confirm` the quotation. This converts the quotation into an :abbr:`SO (sales order)`." msgstr "" -#: ../../content/applications/services/helpdesk/advanced/track_and_bill.rst:109 +#: ../../content/applications/services/helpdesk/advanced/track_and_bill.rst:114 msgid "Create and send an invoice for prepaid services" msgstr "" -#: ../../content/applications/services/helpdesk/advanced/track_and_bill.rst:111 -msgid "Once the :abbr:`SO (sales order)` has been confirmed, click the :guilabel:`Create Invoice` button. This will open a :guilabel:`Create Invoices` pop-up window." +#: ../../content/applications/services/helpdesk/advanced/track_and_bill.rst:116 +msgid "Once the :abbr:`SO (sales order)` has been confirmed, click the :guilabel:`Create Invoice` button. This opens a :guilabel:`Create invoices` pop-up window." msgstr "" -#: ../../content/applications/services/helpdesk/advanced/track_and_bill.rst:114 -msgid "If no down payment will be collected, the :guilabel:`Create Invoice` type can remain as :guilabel:`Regular Invoice`. If a down payment will be collected, choose between either :guilabel:`Down payment (percentage)` or :guilabel:`Down payment (fixed amount)`." +#: ../../content/applications/services/helpdesk/advanced/track_and_bill.rst:119 +msgid "If no down payment is collected, the :guilabel:`Create Invoice` type can remain as :guilabel:`Regular Invoice`. If a :doc:`down payment <../../../sales/sales/invoicing/down_payment>` is collected, choose between either :guilabel:`Down payment (percentage)` or :guilabel:`Down payment (fixed amount)`." msgstr "" -#: ../../content/applications/services/helpdesk/advanced/track_and_bill.rst:118 +#: ../../content/applications/services/helpdesk/advanced/track_and_bill.rst:124 msgid "When the necessary information has been entered, click :guilabel:`Create Draft Invoice`." msgstr "" -#: ../../content/applications/services/helpdesk/advanced/track_and_bill.rst:120 +#: ../../content/applications/services/helpdesk/advanced/track_and_bill.rst:126 msgid "The invoice can then be sent to the customer for payment." msgstr "" -#: ../../content/applications/services/helpdesk/advanced/track_and_bill.rst:123 +#: ../../content/applications/services/helpdesk/advanced/track_and_bill.rst:129 msgid "Create helpdesk ticket for prepaid services" msgstr "" -#: ../../content/applications/services/helpdesk/advanced/track_and_bill.rst:125 +#: ../../content/applications/services/helpdesk/advanced/track_and_bill.rst:131 msgid "To create a *Helpdesk* ticket for prepaid services, navigate to :menuselection:`Helpdesk` and click the :guilabel:`Tickets` button to reveal a specific team's pipeline. Click :guilabel:`New` to create a new ticket." msgstr "" -#: ../../content/applications/services/helpdesk/advanced/track_and_bill.rst:129 +#: ../../content/applications/services/helpdesk/advanced/track_and_bill.rst:135 msgid "On the blank ticket form, create a ticket :guilabel:`Title`, and enter the :guilabel:`Customer` information." msgstr "" -#: ../../content/applications/services/helpdesk/advanced/track_and_bill.rst:132 -msgid "When the customer name is added, the :guilabel:`Sales Order Item` field will automatically populate with the most recent prepaid sales order item that has time remaining." +#: ../../content/applications/services/helpdesk/advanced/track_and_bill.rst:138 +msgid "When the customer name is added, the :guilabel:`Sales Order Item` field automatically populates with the most recent prepaid sales order item that has time remaining." msgstr "" -#: ../../content/applications/services/helpdesk/advanced/track_and_bill.rst:136 +#: ../../content/applications/services/helpdesk/advanced/track_and_bill.rst:142 msgid "Track hours on helpdesk ticket" msgstr "" -#: ../../content/applications/services/helpdesk/advanced/track_and_bill.rst:138 +#: ../../content/applications/services/helpdesk/advanced/track_and_bill.rst:144 msgid "Time spent working on a *Helpdesk* ticket is tracked on the *Timesheets* tab on the specific ticket." msgstr "" -#: ../../content/applications/services/helpdesk/advanced/track_and_bill.rst:140 +#: ../../content/applications/services/helpdesk/advanced/track_and_bill.rst:146 msgid "On the ticket detail form, click on the :guilabel:`Timesheets` tab and click :guilabel:`Add a line`. Choose an :guilabel:`Employee`, add a :guilabel:`Description` of the task, and enter the number of :guilabel:`Hours Spent`." msgstr "" -#: ../../content/applications/services/helpdesk/advanced/track_and_bill.rst:144 -msgid "As new lines are added to :guilabel:`Timesheets` tab, the :guilabel:`Remaining Hours on SO` field is automatically updated." +#: ../../content/applications/services/helpdesk/advanced/track_and_bill.rst:150 +msgid "As new lines are added to :guilabel:`Timesheets` tab, the :guilabel:`Remaining Hours on SO` field, at the bottom-right of the tab, is automatically updated." msgstr "" #: ../../content/applications/services/helpdesk/advanced/track_and_bill.rst:-1 msgid "View of the timesheets tab on a ticket with an emphasis on the remaining hours on an SO." msgstr "" -#: ../../content/applications/services/helpdesk/advanced/track_and_bill.rst:152 -msgid "If the number of hours on the :guilabel:`Timesheets` tab exceeds the number of hours sold, the :guilabel:`Remaining Hours of SO` will turn red." -msgstr "" - -#: ../../content/applications/services/helpdesk/advanced/track_and_bill.rst:155 -msgid "As hours are added to the :guilabel:`Timesheets` tab, they are automatically updated in the :guilabel:`Delivered` field on the :abbr:`SO (sales order)`, as well." -msgstr "" - -#: ../../content/applications/services/helpdesk/advanced/track_and_bill.rst:159 -msgid "Invoice post-paid support services" +#: ../../content/applications/services/helpdesk/advanced/track_and_bill.rst:158 +msgid "If the number of hours on the :guilabel:`Timesheets` tab exceeds the number of hours sold, the :guilabel:`Remaining Hours of SO` turns red." msgstr "" #: ../../content/applications/services/helpdesk/advanced/track_and_bill.rst:161 -msgid "When support services are billed based on the amount of time spent on an issue, an invoice cannot be created before the total number of hours required to solve the problem have been entered on a timesheet. In this case, a service product with the invoicing policy set to :guilabel:`Based on Timesheets` would be used, like the one created above." +msgid "As hours are added to the :guilabel:`Timesheets` tab, they are automatically updated in the :guilabel:`Delivered` field on the :abbr:`SO (sales order)`, as well." +msgstr "" + +#: ../../content/applications/services/helpdesk/advanced/track_and_bill.rst:165 +msgid "Invoice post-paid support services" msgstr "" #: ../../content/applications/services/helpdesk/advanced/track_and_bill.rst:167 +msgid "When support services are billed based on the amount of time spent on an issue, an invoice cannot be created before the total number of hours required to solve the problem have been entered on a timesheet. In this case, a service product with the *Invoicing Policy* set to *Based on Timesheets* would be used, like the one created in :ref:`the section above `." +msgstr "" + +#: ../../content/applications/services/helpdesk/advanced/track_and_bill.rst:174 msgid "Create a sales order with a time-tracked product" msgstr "" -#: ../../content/applications/services/helpdesk/advanced/track_and_bill.rst:169 -msgid "To invoice a customer for post-paid support services, first create a sales order (SO) with the *support services product*. To do this, go to :menuselection:`Sales --> Orders --> Quotations --> New`." -msgstr "" - -#: ../../content/applications/services/helpdesk/advanced/track_and_bill.rst:173 -msgid "Fill out the quotation with the customer information." -msgstr "" - -#: ../../content/applications/services/helpdesk/advanced/track_and_bill.rst:175 -msgid "On the :guilabel:`Order Lines` tab, click :guilabel:`Add a Product`. Select the post-paid services product configured in the steps above. After updating any other necessary information, :guilabel:`Confirm` the quotation." +#: ../../content/applications/services/helpdesk/advanced/track_and_bill.rst:176 +msgid "To invoice a customer for post-paid support services, first create a sales order (SO) with the *support services product*. To do this, go to :menuselection:`Sales app --> Orders --> Quotations`. Then, click :guilabel:`New` to reveal a blank quotation form." msgstr "" #: ../../content/applications/services/helpdesk/advanced/track_and_bill.rst:180 -msgid "Unlike with the prepaid services quotation, Odoo will not allow an invoice to be created at this time. That is because no services have been performed; in other words nothing has been delivered, therefore, there is nothing to invoice." +msgid "Fill out the quotation with the customer information." msgstr "" -#: ../../content/applications/services/helpdesk/advanced/track_and_bill.rst:185 -msgid "Create a helpdesk ticket for time-tracked services" +#: ../../content/applications/services/helpdesk/advanced/track_and_bill.rst:182 +msgid "On the :guilabel:`Order Lines` tab, click :guilabel:`Add a Product`. Select the post-paid services product configured in the steps above. After updating any other necessary information, :guilabel:`Confirm` the quotation." msgstr "" #: ../../content/applications/services/helpdesk/advanced/track_and_bill.rst:187 -msgid "To record a *Timesheet* entry for time-tracker services, go to :menuselection:`Helpdesk` and select the appropriate team for which these services apply." +msgid "Unlike with the prepaid services quotation, Odoo does **not** allow an invoice to be created at this time. That is because no services have been performed; in other words, nothing has been delivered, therefore, there is nothing to invoice." msgstr "" -#: ../../content/applications/services/helpdesk/advanced/track_and_bill.rst:190 -msgid "If there is already an existing ticket for this issue, select it from the kanban view. This will open the ticket details form. If there is no existing ticket for this customer issue, click :guilabel:`New` to create a new ticket and enter the necessary customer information on the blank ticket details form." +#: ../../content/applications/services/helpdesk/advanced/track_and_bill.rst:192 +msgid "Create a helpdesk ticket for time-tracked services" msgstr "" -#: ../../content/applications/services/helpdesk/advanced/track_and_bill.rst:195 -msgid "After selecting or creating a ticket, go to the :guilabel:`Sales Order Line` drop-down menu. Select the :abbr:`SO (sales order)` created in the previous step." +#: ../../content/applications/services/helpdesk/advanced/track_and_bill.rst:194 +msgid "To record a *Timesheet* entry for time-tracker services, go to the :menuselection:`Helpdesk` app, and select the appropriate team for which these services apply." msgstr "" -#: ../../content/applications/services/helpdesk/advanced/track_and_bill.rst:199 +#: ../../content/applications/services/helpdesk/advanced/track_and_bill.rst:197 +msgid "If there is already an existing ticket for this issue, select it from the Kanban view. This opens the ticket details form. If there is no existing ticket for this customer issue, click :guilabel:`New` to create a new ticket and enter the necessary customer information on the blank ticket details form." +msgstr "" + +#: ../../content/applications/services/helpdesk/advanced/track_and_bill.rst:202 +msgid "After selecting or creating a ticket, go to the :guilabel:`Sales Order Item` drop-down menu. Select the :abbr:`SO (sales order)` created in the previous step." +msgstr "" + +#: ../../content/applications/services/helpdesk/advanced/track_and_bill.rst:206 msgid "Track support hours on a ticket" msgstr "" -#: ../../content/applications/services/helpdesk/advanced/track_and_bill.rst:201 +#: ../../content/applications/services/helpdesk/advanced/track_and_bill.rst:208 msgid "In order to create an invoice for a product based on timesheets, hours need to be tracked and recorded. At this point, the service is considered *delivered*. To record hours for this support service, click on the :guilabel:`Timesheets` tab of the ticket." msgstr "" -#: ../../content/applications/services/helpdesk/advanced/track_and_bill.rst:205 +#: ../../content/applications/services/helpdesk/advanced/track_and_bill.rst:212 msgid "Click :guilabel:`Add a Line` to record a new entry. Select an :guilabel:`Employee` from the drop-down menu, and record the time spent in the :guilabel:`Hours Spent` column." msgstr "" -#: ../../content/applications/services/helpdesk/advanced/track_and_bill.rst:208 +#: ../../content/applications/services/helpdesk/advanced/track_and_bill.rst:215 msgid "Repeat these steps as needed until all time spent on the issues has been recorded." msgstr "" @@ -969,19 +973,19 @@ msgstr "" msgid "View of the timesheets tab on a helpdesk ticket." msgstr "" -#: ../../content/applications/services/helpdesk/advanced/track_and_bill.rst:215 +#: ../../content/applications/services/helpdesk/advanced/track_and_bill.rst:222 msgid "Create an invoice for hours tracked on a ticket" msgstr "" -#: ../../content/applications/services/helpdesk/advanced/track_and_bill.rst:217 -msgid "After the customer's issue has been solved, and it is determined no new timesheet entries will be made, an invoice can be created, and the customer can be billed." +#: ../../content/applications/services/helpdesk/advanced/track_and_bill.rst:224 +msgid "After the customer's issue has been solved, and it is determined no new timesheet entries need to be made, an invoice can be created, and the customer can be billed." msgstr "" -#: ../../content/applications/services/helpdesk/advanced/track_and_bill.rst:220 +#: ../../content/applications/services/helpdesk/advanced/track_and_bill.rst:227 msgid "To do this, return to the :abbr:`SO (sales order)` by clicking on the :guilabel:`Sales Order` smart button at the top of the ticket." msgstr "" -#: ../../content/applications/services/helpdesk/advanced/track_and_bill.rst:223 +#: ../../content/applications/services/helpdesk/advanced/track_and_bill.rst:230 msgid "Before creating the invoice, confirm that the number in the :guilabel:`Delivered` column matches the total number of :guilabel:`Hours Spent` listed in the :guilabel:`Timesheets` tab on the ticket." msgstr "" @@ -989,24 +993,32 @@ msgstr "" msgid "View of a sales order with emphasis on the delivered column." msgstr "" -#: ../../content/applications/services/helpdesk/advanced/track_and_bill.rst:230 -msgid "Then, click :guilabel:`Create Invoice`. This will open a :guilabel:`Create Invoices` pop-up window. If no down payment will be collected, the :guilabel:`Create Invoice` type can remain as :guilabel:`Regular Invoice`. If a down payment will be collected, choose between either :guilabel:`Down payment (percentage)` or :guilabel:`Down payment (fixed amount)`." +#: ../../content/applications/services/helpdesk/advanced/track_and_bill.rst:237 +msgid "Then, click :guilabel:`Create Invoice`. This opens a :guilabel:`Create invoice(s)` pop-up window." msgstr "" -#: ../../content/applications/services/helpdesk/advanced/track_and_bill.rst:236 -msgid "Use the :guilabel:`Timesheets Period` field if this invoice should only include timesheets from a certain time period. If this field is left blank, *all* applicable timesheets that have not yet been invoiced will be included." +#: ../../content/applications/services/helpdesk/advanced/track_and_bill.rst:239 +msgid "If no down payment is collected, the :guilabel:`Create Invoice` type can remain as :guilabel:`Regular Invoice`. If a down payment is collected, choose between either :guilabel:`Down payment (percentage)` or :guilabel:`Down payment (fixed amount)`." +msgstr "" + +#: ../../content/applications/services/helpdesk/advanced/track_and_bill.rst:244 +msgid "Use the :guilabel:`Timesheets Period` field if this invoice should **only** include timesheets from a certain time period. If this field is left blank, **all** applicable timesheets that have not yet been invoiced will be included." msgstr "" #: ../../content/applications/services/helpdesk/advanced/track_and_bill.rst:-1 msgid "View of create invoices pop up showing timesheets period fields." msgstr "" -#: ../../content/applications/services/helpdesk/advanced/track_and_bill.rst:244 -msgid "When the necessary information has been entered, click :guilabel:`Create Invoice`. The invoice can then be sent to the customer for payment." +#: ../../content/applications/services/helpdesk/advanced/track_and_bill.rst:252 +msgid "When the necessary information has been entered, click :guilabel:`Create Draft`. The invoice can then be reviewed, edited, and sent to the customer for payment." msgstr "" -#: ../../content/applications/services/helpdesk/advanced/track_and_bill.rst:248 -msgid ":doc:`/applications/inventory_and_mrp/inventory/product_management/product_replenishment/uom`" +#: ../../content/applications/services/helpdesk/advanced/track_and_bill.rst:256 +msgid ":doc:`../../../inventory_and_mrp/inventory/product_management/product_replenishment/uom`" +msgstr "" + +#: ../../content/applications/services/helpdesk/advanced/track_and_bill.rst:257 +msgid ":doc:`../../../sales/sales/invoicing/down_payment`" msgstr "" #: ../../content/applications/services/helpdesk/overview.rst:5 @@ -1205,7 +1217,7 @@ msgid "When an :guilabel:`Email Template` is added to a stage, an email is autom msgstr "" #: ../../content/applications/services/helpdesk/overview/getting_started.rst:172 -msgid "SMS Text Messaging is an :doc:`In-App Purchase (IAP) <../../../general/in_app_purchase/>` service that requires prepaid credits to work. Refer to `SMS Pricing FAQ `_ for additional information." +msgid "SMS Text Messaging is an :doc:`In-App Purchase (IAP) ` service that requires prepaid credits to work. Refer to `SMS Pricing FAQ `_ for additional information." msgstr "" #: ../../content/applications/services/helpdesk/overview/getting_started.rst:176 @@ -1225,7 +1237,8 @@ msgid "View of an SMS template setup page in Odoo Helpdesk" msgstr "" #: ../../content/applications/services/helpdesk/overview/getting_started.rst:189 -msgid ":doc:`../../../general/email_communication/email_template`" +#: ../../content/applications/services/helpdesk/overview/ratings.rst:60 +msgid ":doc:`/applications/general/companies/email_template`" msgstr "" #: ../../content/applications/services/helpdesk/overview/getting_started.rst:192 @@ -1741,10 +1754,6 @@ msgstr "" msgid "Customer ratings can also be viewed through the :guilabel:`Customer Ratings` report. To view this report, go to :menuselection:`Helpdesk --> Reporting --> Customer Ratings`." msgstr "" -#: ../../content/applications/services/helpdesk/overview/ratings.rst:60 -msgid ":doc:`/applications/general/email_communication/email_template`" -msgstr "" - #: ../../content/applications/services/helpdesk/overview/ratings.rst:63 msgid "Publish ratings on the customer portal" msgstr "" @@ -1765,6 +1774,7 @@ msgstr "" msgid "To view the ratings for a team, a customer will log into the portal and navigate to one of their tickets. After clicking on the team name in the :guilabel:`Managed By` field, they will be directed to a page with the team's ratings over the past thirty days." msgstr "" +#: ../../content/applications/services/helpdesk/overview/ratings.rst:-1 #: ../../content/applications/services/helpdesk/overview/ratings.rst:-1 msgid "View of the ratings performance overview from the customer portal." msgstr "" @@ -1907,8 +1917,8 @@ msgstr "" msgid "If a *Helpdesk* team is named `Customer Care`, a *Live Chat* channel is created called `Customer Care`." msgstr "" -#: ../../content/applications/services/helpdesk/overview/receiving_tickets.rst:-1 #: ../../content/applications/services/helpdesk/overview/receiving_tickets.rst:0 +#: ../../content/applications/services/helpdesk/overview/receiving_tickets.rst:-1 msgid "View of the Kanban cards for the available Live Chat channels." msgstr "" @@ -2531,7 +2541,7 @@ msgid ":doc:`Start receiving tickets `" +msgid ":doc:`Odoo reporting `" msgstr "" #: ../../content/applications/services/helpdesk/overview/sla.rst:3 diff --git a/locale/sources/studio.pot b/locale/sources/studio.pot new file mode 100644 index 000000000..884f6872c --- /dev/null +++ b/locale/sources/studio.pot @@ -0,0 +1,1894 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) Odoo S.A. +# This file is distributed under the same license as the Odoo package. +# FIRST AUTHOR , YEAR. +# +#, fuzzy +msgid "" +msgstr "" +"Project-Id-Version: Odoo 17.0\n" +"Report-Msgid-Bugs-To: \n" +"POT-Creation-Date: 2024-03-25 16:01+0000\n" +"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" +"Last-Translator: FULL NAME \n" +"Language-Team: LANGUAGE \n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" + +#: ../../content/applications/studio.rst:6 +msgid "Studio" +msgstr "" + +#: ../../content/applications/studio.rst:17 +msgid "Studio is a toolbox that allows you to customize Odoo without coding knowledge. For example, you can, on any app, add or modify:" +msgstr "" + +#: ../../content/applications/studio.rst:20 +msgid ":doc:`Fields `" +msgstr "" + +#: ../../content/applications/studio.rst:21 +msgid ":doc:`Views `" +msgstr "" + +#: ../../content/applications/studio.rst:22 +msgid ":doc:`Models `" +msgstr "" + +#: ../../content/applications/studio.rst:23 +msgid ":doc:`Automated actions `" +msgstr "" + +#: ../../content/applications/studio.rst:24 +msgid ":doc:`PDF reports `" +msgstr "" + +#: ../../content/applications/studio.rst:25 +msgid "Approval rules" +msgstr "" + +#: ../../content/applications/studio.rst:26 +msgid "Security rules" +msgstr "" + +#: ../../content/applications/studio.rst:28 +msgid "Or you can :doc:`build an app from scratch `." +msgstr "" + +#: ../../content/applications/studio.rst:31 +msgid "`Odoo Tutorials: Studio `_" +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:3 +msgid "Automated actions (automations)" +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:5 +msgid "Automated actions are used to trigger automatic changes based on user actions (e.g., apply a modification when a field is set to a specific value) or on time conditions (e.g., archive a record 7 days after its last update)." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:9 +msgid "To create an automated action with Studio, go to :guilabel:`Automations` from anywhere within Studio." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:12 +msgid "For every automated action you create, the following elements should be defined: the :ref:`studio/automated-actions/model`, the :ref:`studio/automated-actions/trigger`, the :ref:`studio/automated-actions/apply-on`, and the :ref:`studio/automated-actions/action`." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:0 +msgid "Example of an automated action on the Subscription model" +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:25 +msgid "Model" +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:27 +msgid "Select the model where the automated action should be applied." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:30 +msgid "The model you are on when you click on :guilabel:`Automations` is pre-selected by default." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:35 +msgid "Trigger" +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:37 +msgid "Define when the automated action should be applied. Six triggers are available." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:42 +msgid "On Creation" +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:44 +msgid "The action is triggered when a record is created and then saved." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:49 +msgid "On Update" +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:51 +msgid "The action is triggered when a previously saved record is edited and then saved." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:53 +msgid "Use :guilabel:`Trigger Fields` to specify which fields - and only those - trigger the action on their update." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:55 +msgid "To detect when a record changes from one state to another, define a :guilabel:`Before Update Domain` filter, which checks if the condition is satisfied before the record is updated. Then set an :ref:`studio/automated-actions/apply-on` filter, which checks if the condition is met after the record is updated." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:61 +msgid "If you want the automated action to happen when an email address is set on a contact, define the :guilabel:`Before Update Domain` to `Email is not set`, and the :guilabel:`Apply on` domain to `Email is set`." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:0 +msgid "Example of an On Update trigger" +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:72 +msgid "On Creation & Update" +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:74 +msgid "The action is triggered when a record is created and saved or edited afterward and saved." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:79 +msgid "On Deletion" +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:81 +msgid "The action is triggered when a record is deleted." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:84 +msgid "This trigger is rarely used, as archiving records is usually preferred to deletion." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:89 +msgid "Based on Form Modification" +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:91 +msgid "The action is triggered when any change is done to a trigger field's value on the :ref:`Form view `, even before saving the record. This trigger only works on the user interface when a modification is made by a user. If the field is changed through another action and not by the user, the action will not run." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:97 +msgid "This trigger can only be used with the :ref:`Execute Python Code action `, so development is required." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:103 +msgid "Based on Timed Condition" +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:105 +msgid "The action is triggered when a trigger field's date or date & time value is reached." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:107 +msgid "To trigger the action after the :guilabel:`Trigger Date`, add a number of minutes, hours, days, or months under :guilabel:`Delay after trigger date`. To trigger the action before, add a negative number instead." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:112 +msgid "If you want to send a reminder email 30 minutes before the start of a calendar event, select the :guilabel:`Start (Calendar Event)` under :guilabel:`Trigger Date` and set the :guilabel:`Delay after trigger date` to **-30** :guilabel:`Minutes`." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:0 +msgid "Example of a Based on Timed Condition trigger" +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:121 +msgid "By default, the scheduler checks for trigger dates every 4 hours." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:126 +msgid "Apply on" +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:128 +msgid "Define on which records of the model the automated action should be applied. It works the same way as when you apply filters on a model." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:134 +msgid "Action" +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:136 +msgid "Determine what the automated action should do (server action). There are eight types of action to choose from." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:142 +msgid "Execute Python Code" +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:144 +msgid "The action is used to execute Python code. The available variables are described on the :guilabel:`Python Code` tab, which is also used to write your code, or on the :guilabel:`Help` tab." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:147 +msgid "To allow the action to be run through the website, tick :guilabel:`Available on the Website` and add a :guilabel:`Website Path`." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:153 +msgid "Create a new Record" +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:155 +msgid "The action is used to create a new record on any model." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:158 +msgid "Selecting a :guilabel:`Target Model` is only required if you want to target another model than the one you are on." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:161 +msgid "To link the record that triggered the creation of the new record, select a field under :guilabel:`Link Field`. For example, you could create a contact automatically when a lead is turned into an opportunity." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:164 +msgid ":guilabel:`Data to Write` tab: the tab is used to specify the new record's values. After selecting a :guilabel:`Field`, select its :guilabel:`Evaluation Type`:" +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:167 +msgid ":guilabel:`Value`: used to directly give the field's raw value in the :guilabel:`Value` column." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:168 +msgid ":guilabel:`Reference`: used to select the record under the :guilabel:`Record` column and let Studio add the internal ID in the :guilabel:`Value` column." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:172 +msgid "If an automated action creates a new task in a project, you can assign it to a specific user by setting the :guilabel:`Field` to :guilabel:`Responsible User (Project)`, the :guilabel:`Evaluation Type` to :guilabel:`Reference`, and the :guilabel:`Record` to a specific user." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:0 +msgid "Example of a Create a new Record action" +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:181 +msgid ":guilabel:`Python expression`: used to dynamically define the newly created record’s value for a field using Python code in the :guilabel:`Value` column." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:187 +msgid "Update the Record" +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:189 +msgid "The action is used to set value(s) for field(s) of any record on the current model." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:192 +msgid "The process to fill in the :guilabel:`Data to Write` tab is the same as described under :ref:`studio/automated-actions/action/new-record`." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:198 +msgid "Execute several actions" +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:200 +msgid "The action is used to trigger multiple actions at the same time. To do so, click on :guilabel:`Add a line` under the :guilabel:`Actions` tab. In the :guilabel:`Child Actions` pop-up, click on :guilabel:`Create` and configure the action." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:207 +msgid "Send Email" +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:209 +msgid "The action is used to send an email to a contact linked to a specific record. To do so, select or create an :guilabel:`Email Template`." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:215 +msgid "Add Followers" +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:217 +msgid "The action is used to subscribe existing contacts to the record." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:222 +msgid "Create Next Activity" +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:224 +msgid "The action is used to schedule a new activity linked to the record. Use the :guilabel:`Activity` tab to set it up as usual, but instead of the :guilabel:`Assigned to` field, select an :guilabel:`Activity User Type`. Select :guilabel:`Specific User` and add the user under :guilabel:`Responsible` if the activity should always be assigned to the same user. To dynamically target a user linked to the record, select :guilabel:`Generic User From Record` instead and change the :guilabel:`User field name` if necessary." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:232 +msgid "After a lead is turned into an opportunity, you want your automated action to set up a call for the user responsible for the lead. To do so, set the :guilabel:`Activity` to :guilabel:`Call` and set the :guilabel:`Activity User Type` to :guilabel:`Generic User From Record`." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:0 +msgid "Example of a Create Next Activity action" +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:243 +msgid "Send SMS Text Message" +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:245 +msgid "The action is used to send an SMS to a contact linked to the record. To do so, select or create an :guilabel:`SMS Template`." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:249 +msgid "If you want sent messages to be logged in the Chatter, tick :guilabel:`Log as Note`." +msgstr "" + +#: ../../content/applications/studio/fields.rst:3 +msgid "Fields and widgets" +msgstr "" + +#: ../../content/applications/studio/fields.rst:5 +msgid "Fields structure the models of a database. If you picture a model as a table or spreadsheet, fields are the columns where data is stored in the records (i.e., the rows). Fields also define the type of data that is stored within them. How the data is presented and formatted on the :abbr:`UI (User Interface)` is defined by their widget." +msgstr "" + +#: ../../content/applications/studio/fields.rst:10 +msgid "From a technical point of view, there are 15 field types in Odoo. However, you can choose from 20 fields in Studio, as some field types are available more than once with a different default widget." +msgstr "" + +#: ../../content/applications/studio/fields.rst:14 +msgid ":guilabel:`New Fields` can only be added to the :ref:`studio/views/general/form` and :ref:`studio/views/multiple-records/list` views. On other views, you can only add :guilabel:`Existing Fields` :dfn:`(fields already on the model)`." +msgstr "" + +#: ../../content/applications/studio/fields.rst:21 +msgid "Simple fields" +msgstr "" + +#: ../../content/applications/studio/fields.rst:23 +msgid "Simple fields contain basic values, such as text, numbers, files, etc." +msgstr "" + +#: ../../content/applications/studio/fields.rst:26 +#: ../../content/applications/studio/fields.rst:325 +msgid "Non-default widgets, when available, are presented as bullet points below." +msgstr "" + +#: ../../content/applications/studio/fields.rst:31 +msgid "Text (`char`)" +msgstr "" + +#: ../../content/applications/studio/fields.rst:33 +msgid "The :guilabel:`Text` field is used for short text containing any character. One text line is displayed when filling out the field." +msgstr "" + +#: ../../content/applications/studio/fields.rst:36 +#: ../../content/applications/studio/fields.rst:220 +msgid ":guilabel:`Badge`: displays the value inside a rounded shape, similar to a tag. The value cannot be edited on the UI, but a default value can be set." +msgstr "" + +#: ../../content/applications/studio/fields.rst:38 +#: ../../content/applications/studio/fields.rst:71 +msgid ":guilabel:`Copy to Clipboard`: users can copy the value by clicking a button." +msgstr "" + +#: ../../content/applications/studio/fields.rst:39 +msgid ":guilabel:`E-mail`: the value becomes a clickable *mailto* link." +msgstr "" + +#: ../../content/applications/studio/fields.rst:40 +msgid ":guilabel:`Image`: displays an image using a URL. The value cannot be edited manually, but a default value can be set." +msgstr "" + +#: ../../content/applications/studio/fields.rst:44 +msgid "This works differently than selecting the :ref:`Image field ` directly, as the image is not stored in Odoo when using a :guilabel:`Text` field with the :guilabel:`Image` widget. For example, it can be useful if you want to save disk space." +msgstr "" + +#: ../../content/applications/studio/fields.rst:49 +msgid ":guilabel:`Phone`: the value becomes a clickable *tel* link." +msgstr "" + +#: ../../content/applications/studio/fields.rst:52 +msgid "Tick :guilabel:`Enable SMS` to add an option to send an SMS directly from Odoo next to the field." +msgstr "" + +#: ../../content/applications/studio/fields.rst:55 +msgid ":guilabel:`URL`: the value becomes a clickable URL." +msgstr "" + +#: ../../content/applications/studio/fields.rst:0 +msgid "Examples of Text fields with different widgets" +msgstr "" + +#: ../../content/applications/studio/fields.rst:66 +msgid "Multiline Text (`text`)" +msgstr "" + +#: ../../content/applications/studio/fields.rst:68 +msgid "The :guilabel:`Multiline Text` field is used for longer text containing any type of character. Two text lines are displayed on the UI when filling out the field." +msgstr "" + +#: ../../content/applications/studio/fields.rst:0 +msgid "Examples of Multiline Text fields with different widgets" +msgstr "" + +#: ../../content/applications/studio/fields.rst:82 +msgid "Integer (`integer`)" +msgstr "" + +#: ../../content/applications/studio/fields.rst:84 +msgid "The :guilabel:`Integer` field is used for all integer numbers (:dfn:`positive, negative, or zero, without a decimal`)." +msgstr "" + +#: ../../content/applications/studio/fields.rst:87 +msgid ":guilabel:`Percentage Pie`: displays the value inside a percentage circle, usually for a computed value. The value cannot be edited on the UI, but a default value can be set." +msgstr "" + +#: ../../content/applications/studio/fields.rst:89 +#: ../../content/applications/studio/fields.rst:118 +msgid ":guilabel:`Progress Bar`: displays the value next to a percentage bar, usually for a computed value. The field cannot be edited manually, but a default value can be set." +msgstr "" + +#: ../../content/applications/studio/fields.rst:91 +msgid ":guilabel:`Handle`: displays a drag handle icon to order records manually in :ref:`List view `." +msgstr "" + +#: ../../content/applications/studio/fields.rst:0 +msgid "Examples of Integer fields with different widgets" +msgstr "" + +#: ../../content/applications/studio/fields.rst:103 +msgid "Decimal (`float`)" +msgstr "" + +#: ../../content/applications/studio/fields.rst:105 +msgid "The :guilabel:`Decimal` field is used for all decimal numbers (:dfn:`positive, negative, or zero, with a decimal`)." +msgstr "" + +#: ../../content/applications/studio/fields.rst:109 +msgid "Decimal numbers are displayed with two decimals after the decimal point on the UI, but they are stored in the database with more precision." +msgstr "" + +#: ../../content/applications/studio/fields.rst:112 +msgid ":guilabel:`Monetary`: it is similar to using the :ref:`Monetary field `. It is recommended to use the later as it offers more functionalities." +msgstr "" + +#: ../../content/applications/studio/fields.rst:115 +msgid ":guilabel:`Percentage`: displays a percent character `%` after the value." +msgstr "" + +#: ../../content/applications/studio/fields.rst:116 +msgid ":guilabel:`Percentage Pie`: displays the value inside a percentage circle, usually for a computed value. The field cannot be edited manually, but a default value can be set." +msgstr "" + +#: ../../content/applications/studio/fields.rst:120 +msgid ":guilabel:`Time`: the value must follow the *hh:mm* format, with a maximum of 59 minutes." +msgstr "" + +#: ../../content/applications/studio/fields.rst:0 +msgid "Examples of Decimal fields with different widgets" +msgstr "" + +#: ../../content/applications/studio/fields.rst:131 +msgid "Monetary (`monetary`)" +msgstr "" + +#: ../../content/applications/studio/fields.rst:133 +msgid "The :guilabel:`Monetary` field is used for all monetary values." +msgstr "" + +#: ../../content/applications/studio/fields.rst:136 +msgid "When you first add a :guilabel:`Monetary` field, you are prompted to add a :guilabel:`Currency` field if none exists already on the model. Odoo offers to add the :guilabel:`Currency` field for you. Once it is added, add the :guilabel:`Monetary` field again." +msgstr "" + +#: ../../content/applications/studio/fields.rst:0 +msgid "Example of a Monetary field along with its Currency field" +msgstr "" + +#: ../../content/applications/studio/fields.rst:149 +msgid "Html (`html`)" +msgstr "" + +#: ../../content/applications/studio/fields.rst:151 +msgid "The :guilabel:`Html` field is used to add text that can be edited using the Odoo HTML editor." +msgstr "" + +#: ../../content/applications/studio/fields.rst:153 +msgid ":guilabel:`Multiline Text`: disables the Odoo HTML editor to allow editing raw HTML." +msgstr "" + +#: ../../content/applications/studio/fields.rst:0 +msgid "Examples of Html fields with different widgets" +msgstr "" + +#: ../../content/applications/studio/fields.rst:164 +msgid "Date (`date`)" +msgstr "" + +#: ../../content/applications/studio/fields.rst:166 +msgid "The :guilabel:`Date` field is used to select a date on a calendar." +msgstr "" + +#: ../../content/applications/studio/fields.rst:168 +msgid ":guilabel:`Remaining Days`: the remaining number of days before the selected date is displayed (e.g., *In 5 days*), based on the current date." +msgstr "" + +#: ../../content/applications/studio/fields.rst:0 +msgid "Examples of Date fields with different widgets" +msgstr "" + +#: ../../content/applications/studio/fields.rst:180 +msgid "Date & Time (`datetime`)" +msgstr "" + +#: ../../content/applications/studio/fields.rst:182 +msgid "The :guilabel:`Date & Time` field is used to select a date on a calendar and a time on a clock. The user's current time is automatically used if no time is set." +msgstr "" + +#: ../../content/applications/studio/fields.rst:185 +msgid ":guilabel:`Date`: used to record the time without displaying it on the UI." +msgstr "" + +#: ../../content/applications/studio/fields.rst:186 +msgid ":guilabel:`Remaining days`: displays the remaining number of days before the selected date (e.g., *In 5 days*), based on the current date and time." +msgstr "" + +#: ../../content/applications/studio/fields.rst:0 +msgid "Examples of Date & Time fields with different widgets" +msgstr "" + +#: ../../content/applications/studio/fields.rst:198 +msgid "Checkbox (`boolean`)" +msgstr "" + +#: ../../content/applications/studio/fields.rst:200 +msgid "The :guilabel:`Checkbox` field is used when a value should only be true or false, indicated by checking or unchecking a checkbox." +msgstr "" + +#: ../../content/applications/studio/fields.rst:203 +msgid ":guilabel:`Button`: displays a radio button. The widget works without switching to the edit mode." +msgstr "" + +#: ../../content/applications/studio/fields.rst:204 +msgid ":guilabel:`Toggle`: displays a toggle button. The widget works without switching to the edit mode." +msgstr "" + +#: ../../content/applications/studio/fields.rst:0 +msgid "Examples of Checkbox fields with different widgets" +msgstr "" + +#: ../../content/applications/studio/fields.rst:215 +msgid "Selection (`selection`)" +msgstr "" + +#: ../../content/applications/studio/fields.rst:217 +msgid "The :guilabel:`Selection` field is used when users should select a single value from a group of predefined values." +msgstr "" + +#: ../../content/applications/studio/fields.rst:222 +msgid ":guilabel:`Badges`: displays all selectable values simultaneously inside rectangular shapes, organized horizontally." +msgstr "" + +#: ../../content/applications/studio/fields.rst:224 +msgid ":guilabel:`Priority`: displays star symbols instead of values, which can be used to indicate an importance or satisfaction level, for example. This has the same effect as selecting the :ref:`Priority field `, although, for the latter, four priority values are already predefined." +msgstr "" + +#: ../../content/applications/studio/fields.rst:228 +#: ../../content/applications/studio/fields.rst:352 +msgid ":guilabel:`Radio`: displays all selectable values at the same time as radio buttons." +msgstr "" + +#: ../../content/applications/studio/fields.rst:231 +msgid "By default, radio buttons are organized vertically. Tick :guilabel:`display horizontally` to switch the way they are displayed." +msgstr "" + +#: ../../content/applications/studio/fields.rst:0 +msgid "Examples of Selection fields with different widgets" +msgstr "" + +#: ../../content/applications/studio/fields.rst:243 +msgid "Priority (`selection`)" +msgstr "" + +#: ../../content/applications/studio/fields.rst:245 +msgid "The :guilabel:`Priority` field is used to display a three-star rating system, which can be used to indicate importance or satisfaction level. This field type is a :ref:`Selection field ` with the :guilabel:`Priority` widget selected by default and four priority values predefined. Consequently, the :guilabel:`Badge`, :guilabel:`Badges`, :guilabel:`Radio`, and :guilabel:`Selection` widgets have the same effects as described under :ref:`Selection `." +msgstr "" + +#: ../../content/applications/studio/fields.rst:253 +msgid "To change the number of available stars by adding or removing values, click :guilabel:`Edit Values`. Note that the first value is equal to 0 stars (i.e., when no selection is made), so having four values results in a three-star rating system, for example." +msgstr "" + +#: ../../content/applications/studio/fields.rst:0 +msgid "Example of a Priority field" +msgstr "" + +#: ../../content/applications/studio/fields.rst:266 +msgid "File (`binary`)" +msgstr "" + +#: ../../content/applications/studio/fields.rst:268 +msgid "The :guilabel:`File` field is used to upload any type of file, or sign a form (:guilabel:`Sign` widget)." +msgstr "" + +#: ../../content/applications/studio/fields.rst:271 +msgid ":guilabel:`Image`: users can upload an image file, which is then displayed in :ref:`Form view `. This has the same effect as using the :ref:`Image field `." +msgstr "" + +#: ../../content/applications/studio/fields.rst:274 +msgid ":guilabel:`PDF Viewer`: users can upload a PDF file, which can be then browsed from the :ref:`Form view `." +msgstr "" + +#: ../../content/applications/studio/fields.rst:276 +msgid ":guilabel:`Sign`: users can electronically sign the form. This has the same effect as selecting the :ref:`Sign field `." +msgstr "" + +#: ../../content/applications/studio/fields.rst:0 +msgid "Examples of File fields with different widgets" +msgstr "" + +#: ../../content/applications/studio/fields.rst:288 +msgid "Image (`binary`)" +msgstr "" + +#: ../../content/applications/studio/fields.rst:290 +msgid "The :guilabel:`Image` field is used to upload an image and display it in :ref:`Form view `. This field type is a :ref:`File field ` with the :guilabel:`Image` widget selected by default. Consequently, the :guilabel:`File`, :guilabel:`PDF Viewer`, and :guilabel:`Sign` widgets have the same effects as described under :ref:`File `." +msgstr "" + +#: ../../content/applications/studio/fields.rst:297 +msgid "To change the display size of uploaded images, select :guilabel:`Small`, :guilabel:`Medium`, or :guilabel:`Large` under the :guilabel:`Size` option." +msgstr "" + +#: ../../content/applications/studio/fields.rst:303 +msgid "Sign (`binary`)" +msgstr "" + +#: ../../content/applications/studio/fields.rst:305 +msgid "The :guilabel:`Sign` field is used to sign the form electronically. This field type is a :ref:`File field ` with the :guilabel:`Sign` widget selected by default. Consequently, the :guilabel:`File`, :guilabel:`Image`, and :guilabel:`PDF Viewer` widgets have the same effects as described under :ref:`File `." +msgstr "" + +#: ../../content/applications/studio/fields.rst:311 +msgid "To give users the :guilabel:`Auto` option when having to draw their signature, select one of the available :guilabel:`Auto-complete with` fields (:ref:`Text `, :ref:`Many2One `, and :ref:`Related Field ` on the model only). The signature is automatically generated using the data from the selected field." +msgstr "" + +#: ../../content/applications/studio/fields.rst:320 +msgid "Relational fields" +msgstr "" + +#: ../../content/applications/studio/fields.rst:322 +msgid "Relational fields are used to link and display the data from records on another model." +msgstr "" + +#: ../../content/applications/studio/fields.rst:330 +msgid "Many2One (`many2one`)" +msgstr "" + +#: ../../content/applications/studio/fields.rst:332 +msgid "The :guilabel:`Many2One` field is used to link another record (from another model) to the record being edited. The record's name from the other model is then displayed on the record being edited." +msgstr "" + +#: ../../content/applications/studio/fields.rst:336 +msgid "On the *Sales Order* model, the :guilabel:`Customer` field is a :guilabel:`Many2One` field pointing at the *Contact* model. This allows **many** sales orders to be linked to **one** contact (customer)." +msgstr "" + +#: ../../content/applications/studio/fields.rst:0 +msgid "Diagram showing a many2one relationship" +msgstr "" + +#: ../../content/applications/studio/fields.rst:345 +msgid "To prevent users from creating a new record in the linked model, tick :guilabel:`Disable creation`." +msgstr "" + +#: ../../content/applications/studio/fields.rst:347 +msgid "To prevent users from opening records in a pop-up window, tick :guilabel:`Disable opening`." +msgstr "" + +#: ../../content/applications/studio/fields.rst:348 +msgid "To help users only select the right record, click on :guilabel:`Domain` to create a filter." +msgstr "" + +#: ../../content/applications/studio/fields.rst:350 +msgid ":guilabel:`Badge`: displays the value inside a rounded shape, similar to a tag. The value cannot be edited on the UI." +msgstr "" + +#: ../../content/applications/studio/fields.rst:357 +msgid "One2Many (`one2many`)" +msgstr "" + +#: ../../content/applications/studio/fields.rst:359 +msgid "The :guilabel:`One2Many` field is used to display the existing relations between a record on the current model and multiple records from another model." +msgstr "" + +#: ../../content/applications/studio/fields.rst:363 +msgid "You could add a :guilabel:`One2Many` field on the *Contact* model to look at **one** customer's **many** sales orders." +msgstr "" + +#: ../../content/applications/studio/fields.rst:0 +msgid "Diagram showing a one2many relationship" +msgstr "" + +#: ../../content/applications/studio/fields.rst:371 +msgid "To use a :guilabel:`One2Many` field, the two models must have been linked already using a :ref:`Many2One field `. One2Many relations do not exist independently: a reverse-search of existing Many2One relations is performed." +msgstr "" + +#: ../../content/applications/studio/fields.rst:378 +msgid "Lines (`one2many`)" +msgstr "" + +#: ../../content/applications/studio/fields.rst:380 +msgid "The :guilabel:`Lines` field is used to create a table with rows and columns (e.g., the lines of products on a sales order)." +msgstr "" + +#: ../../content/applications/studio/fields.rst:384 +msgid "To modify the columns, click on the :guilabel:`Lines` field and then :guilabel:`Edit List View`. To edit the form that pops up when a user clicks on :guilabel:`Add a line`, click on :guilabel:`Edit Form View` instead." +msgstr "" + +#: ../../content/applications/studio/fields.rst:0 +msgid "Example of a Lines field" +msgstr "" + +#: ../../content/applications/studio/fields.rst:397 +msgid "Many2Many (`many2many`)" +msgstr "" + +#: ../../content/applications/studio/fields.rst:399 +msgid "The :guilabel:`Many2Many` field is used to link multiple records from another model to multiple records on the current model. Many2Many fields can use :guilabel:`Disable creation`, :guilabel:`Disable opening`, :guilabel:`Domain`, just like :ref:`Many2One fields `." +msgstr "" + +#: ../../content/applications/studio/fields.rst:405 +msgid "On the *Task* model, the :guilabel:`Assignees` field is a :guilabel:`Many2Many` field pointing at the *Contact* model. This allows a single user to be assigned to **many** tasks and **many** users to be assigned to a single task." +msgstr "" + +#: ../../content/applications/studio/fields.rst:0 +msgid "Diagram showing many2many relationships" +msgstr "" + +#: ../../content/applications/studio/fields.rst:413 +msgid ":guilabel:`Checkboxes`: users can select several values using checkboxes." +msgstr "" + +#: ../../content/applications/studio/fields.rst:414 +msgid ":guilabel:`Tags`: users can select several values appearing in rounded shapes, also known as *tags*. This has the same effect as selecting the :ref:`Tags field `." +msgstr "" + +#: ../../content/applications/studio/fields.rst:421 +msgid "Tags (`many2many`)" +msgstr "" + +#: ../../content/applications/studio/fields.rst:423 +msgid "The :guilabel:`Tags` field is used to display several values from another model appearing in rounded shapes, also known as *tags*. This field type is a :ref:`Many2Many field ` with the :guilabel:`Tags` widget selected by default. Consequently, the :guilabel:`Checkboxes` and :guilabel:`Many2Many` widgets have the same effects as described under :ref:`Many2Many `." +msgstr "" + +#: ../../content/applications/studio/fields.rst:430 +msgid "To display tags with different background colors, tick :guilabel:`Use colors`." +msgstr "" + +#: ../../content/applications/studio/fields.rst:0 +msgid "Example of a Tags field" +msgstr "" + +#: ../../content/applications/studio/fields.rst:441 +msgid "Related Field (`related`)" +msgstr "" + +#: ../../content/applications/studio/fields.rst:443 +msgid "A :guilabel:`Related Field` is not a relational field per se; no relationship is created between models. It uses an existing relationship to fetch and display information from another record." +msgstr "" + +#: ../../content/applications/studio/fields.rst:447 +msgid "To display the email address of a customer on the *Sales Order* model, use the :guilabel:`Related Field` `partner_id.email` by selecting :guilabel:`Customer` and then :guilabel:`Email`." +msgstr "" + +#: ../../content/applications/studio/fields.rst:453 +msgid "Properties" +msgstr "" + +#: ../../content/applications/studio/fields.rst:455 +msgid ":guilabel:`Invisible`: When it is not necessary for users to view a field on the UI, tick :guilabel:`Invisible`. It helps clear the UI by only showing the essential fields depending on a specific situation." +msgstr "" + +#: ../../content/applications/studio/fields.rst:460 +msgid "On the *Form* view of the *Contact* model, the :guilabel:`Title` field only appears when :guilabel:`Individual` is selected, as that field would not be helpful for a :guilabel:`Company` contact." +msgstr "" + +#: ../../content/applications/studio/fields.rst:465 +msgid "The :guilabel:`Invisible` attribute also applies to Studio. To view hidden fields inside Studio, click on a view's :guilabel:`View` tab and tick :guilabel:`Show Invisible Elements`." +msgstr "" + +#: ../../content/applications/studio/fields.rst:469 +msgid ":guilabel:`Required`: If a field should always be completed by the user before being able to proceed, tick :guilabel:`Required`." +msgstr "" + +#: ../../content/applications/studio/fields.rst:471 +msgid ":guilabel:`Read only`: If users should not be able to modify a field, tick :guilabel:`Read only`." +msgstr "" + +#: ../../content/applications/studio/fields.rst:474 +msgid "You can choose to apply these three properties only for specific records by clicking on :guilabel:`Conditional` and creating a filter." +msgstr "" + +#: ../../content/applications/studio/fields.rst:477 +msgid ":guilabel:`Label`: The :guilabel:`Label` is the field's name on the UI." +msgstr "" + +#: ../../content/applications/studio/fields.rst:480 +msgid "This is not the same name as used in the PostgreSQL database. To view and change the latter, activate the :ref:`Developer mode `, and edit the :guilabel:`Technical Name`." +msgstr "" + +#: ../../content/applications/studio/fields.rst:483 +msgid ":guilabel:`Help Tooltip`: To explain the purpose of a field, write a description under :guilabel:`Help Tooltip`. It is displayed inside a tooltip box when hovering with your mouse over the field's label." +msgstr "" + +#: ../../content/applications/studio/fields.rst:486 +msgid ":guilabel:`Placeholder`: To provide an example of how a field should be completed, write it under :guilabel:`Placeholder`. It is displayed in light gray in lieu of the field's value." +msgstr "" + +#: ../../content/applications/studio/fields.rst:488 +msgid ":guilabel:`Widget`: To change the default appearance or functionality of a field, select one of the available widgets." +msgstr "" + +#: ../../content/applications/studio/fields.rst:490 +msgid ":guilabel:`Default value`: To add a default value to a field when a record is created, use :guilabel:`Default value`." +msgstr "" + +#: ../../content/applications/studio/fields.rst:492 +msgid ":guilabel:`Limit visibility to groups`: To limit which users can see the field, select a user access group." +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:3 +msgid "Models, modules, and apps" +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:5 +msgid "Models determine the logical structure of a database and how data is stored, organized, and manipulated. In other words, a model is a table of information that can be linked with other tables. A model usually represents a business concept, such as a *sales order*, *contact*, or *product*." +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:9 +msgid "Modules and apps contain various elements, such as models, views, data files, web controllers, and static web data." +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:13 +msgid "All apps are modules. Larger, standalone modules are typically referred to as apps, whereas other modules usually serve as add-ons to said apps." +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:19 +msgid "Suggested features" +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:21 +msgid "When you create a new model or app with Studio, you can choose to add up to 14 features to speed up the creation process. These features bundle fields, default settings, and views that are usually used together to provide some standard functionality. Most of these features can be added later on, but adding them from the start makes the model creation process much easier. Furthermore, these features interact together in some cases to increase their usefulness." +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:28 +msgid "Creating a model with the :ref:`studio/models-modules-apps/suggested-features/picture` and :ref:`studio/models-modules-apps/suggested-features/pipeline-stages` features enabled adds the image in the card layout of the :ref:`Kanban view `." +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:0 +msgid "Combination of the Picture and Pipeline stages features on the Kanban view" +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:39 +msgid "Contact details" +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:41 +msgid "Selecting :guilabel:`Contact details` adds to the :ref:`Form view ` a :ref:`Many2One field ` linked to the *Contact* model and two of its :ref:`Related Fields `: :guilabel:`Phone` and :guilabel:`Email`. The :guilabel:`Contact` field is also added to the :ref:`List view `, and the :ref:`Map view ` is activated." +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:0 +msgid "Contact details feature on the Form view" +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:57 +msgid "User assignment" +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:59 +msgid "Selecting :guilabel:`User assignment` adds to the :ref:`Form view ` a :ref:`Many2One field ` linked to the *Contact* model, with the following :guilabel:`Domain`: `Share User is not set` to only allow the selection of *Internal Users*. In addition, the :guilabel:`many2one_avatar_user` widget is used to display the user's avatar. The :guilabel:`Responsible` field is also added to the :ref:`List view `." +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:0 +msgid "User assignment feature on the Form view" +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:75 +msgid "Date & Calendar" +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:77 +msgid "Selecting :guilabel:`Date & Calendar` adds to the :ref:`Form view ` a :ref:`Date field ` and activates the :ref:`Calendar view `." +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:84 +msgid "Date range & Gantt" +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:86 +msgid "Selecting :guilabel:`Date range & Gantt` adds to the :ref:`Form view ` two :ref:`Date fields ` next to each other: one to set a start date, the other to set an end date, using the :guilabel:`daterange` widget, and activates the :ref:`Gantt view `." +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:94 +msgid "Pipeline stages" +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:96 +msgid "Selecting :guilabel:`Pipeline stages` activates the :ref:`Kanban view `, adds several fields such as :ref:`Priority ` and :guilabel:`Kanban State`, and three stages: :guilabel:`New`, :guilabel:`In Progress`, and :guilabel:`Done`. The :guilabel:`Pipeline status bar` and the :guilabel:`Kanban State` field are added to the :ref:`Form view `. The :guilabel:`Color` field is added to the :ref:`List view `." +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:105 +msgid "The :guilabel:`Pipeline stages` feature can be added at a later stage." +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:110 +msgid "Tags" +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:112 +msgid "Selecting :guilabel:`Tags` adds to the :ref:`studio/views/general/form` and :ref:`studio/views/multiple-records/list` views a :ref:`Tags field `, creating a *Tag* model with preconfigured access rights in the process." +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:120 +msgid "Picture" +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:122 +msgid "Selecting :guilabel:`Picture` adds to the top-right of the :ref:`Form view ` an :ref:`Image field `." +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:126 +msgid "The :guilabel:`Picture` feature can be added at a later stage." +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:131 +msgid "Lines" +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:133 +msgid "Selecting :guilabel:`Lines`: adds to the :ref:`Form view ` a :ref:`Lines field ` inside a :guilabel:`Tab` component." +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:139 +msgid "Notes" +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:141 +msgid "Selecting :guilabel:`Notes` adds to the :ref:`Form view ` an :ref:`Html field ` using the full width of the form." +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:147 +msgid "Monetary value" +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:149 +msgid "Selecting :guilabel:`Monetary value` adds to the :ref:`studio/views/general/form` and :ref:`studio/views/multiple-records/list` views a :ref:`Monetary field `. The :ref:`studio/views/reporting/graph` and :ref:`studio/views/reporting/pivot` views are also activated." +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:155 +msgid "A *Currency* field is added and hidden from the view." +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:160 +msgid "Company" +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:162 +msgid "Selecting :guilabel:`Company` adds to the :ref:`studio/views/general/form` and :ref:`studio/views/multiple-records/list` views a :ref:`Many2One field ` linked to the *Company* model." +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:167 +msgid "This is only useful if you work in a multi-company environment." +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:172 +msgid "Custom Sorting" +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:174 +msgid "Selecting :guilabel:`Custom Sorting` adds to the :ref:`List view ` a drag handle icon to manually reorder records." +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:0 +msgid "Custom Sorting feature on the List view" +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:186 +msgid "Chatter" +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:188 +msgid "Selecting :guilabel:`Chatter` adds to the :ref:`Form view ` Chatter functionalities (sending messages, logging notes, and scheduling activities)." +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:192 +msgid "The :guilabel:`Chatter` feature can be added at a later stage." +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:0 +msgid "Chatter feature on the Form view" +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:203 +msgid "Archiving" +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:205 +msgid "Selecting :guilabel:`Archiving` adds to the :ref:`studio/views/general/form` and :ref:`studio/views/multiple-records/list` views the :guilabel:`Archive` action and hides archived records from searches and views by default." +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:212 +msgid "Export and import customizations" +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:214 +msgid "When you do any customization with Studio, a new module named :guilabel:`Studio customizations` is added to your database." +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:217 +msgid "To export these customizations, go to :menuselection:`Main dashboard --> Studio --> Customizations --> Export` to download a ZIP file containing all customizations." +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:220 +msgid "To import and install these customizations in another database, connect to the destination database and go to :menuselection:`Main dashboard --> Studio --> Customizations --> Import`, then upload the exported ZIP file before clicking on the :guilabel:`Import` button." +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:225 +msgid "Before importing, make sure the destination database contains the same apps and modules as the source database. Studio does not add the underlying modules as dependencies of the exported module." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:3 +msgid "PDF reports" +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:5 +msgid "With Studio, you can :ref:`edit existing PDF reports ` (e.g., invoices, quotations, etc.) or :ref:`create new ones `." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:11 +msgid "Default layout" +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:13 +msgid "The default layout of reports is managed outside Studio. Go to :menuselection:`Settings`, then, in the :guilabel:`Companies` section, click :guilabel:`Configure Document Layout`. Layout settings are company-specific but apply to all reports." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:18 +msgid "You can see how the different settings affect the report layout in the report preview on the right, or download a sample invoice PDF by clicking :guilabel:`Download PDF Preview`." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:21 +msgid "Use the following settings:" +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:25 +msgid ":guilabel:`Layout`: Four layouts are available:" +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:29 +msgid "Light" +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:0 +msgid "Light report layout sample" +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:34 +msgid "Boxed" +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:0 +msgid "Boxed report layout sample" +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:39 +msgid "Bold" +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:0 +msgid "Bold report layout sample" +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:44 +msgid "Striped" +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:0 +msgid "Striped report layout sample" +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:51 +msgid ":guilabel:`Font`: Seven fonts are available: Lato, Roboto, Open Sans, Montserrat, Oswald, Raleway, and Tajawal (which supports Arabic and Latin scripts). Go to the `Google Fonts website `_ to preview them." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:57 +msgid ":guilabel:`Company logo`: Click the :guilabel:`Edit` button to upload or change the logo. This adds the logo to the company’s record on the *Company* model, which you can access by going to :menuselection:`Settings` and then clicking :guilabel:`Update Info` in the :guilabel:`Companies` section." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:64 +msgid ":guilabel:`Colors`: Change the primary and secondary colors used to structure reports. The default colors are automatically generated based on the colors of the logo." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:69 +msgid ":guilabel:`Layout background`: The following backgrounds are available:" +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:71 +msgid ":guilabel:`Blank`: nothing is displayed." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:72 +msgid ":guilabel:`Geometric`: an image featuring geometric shapes is displayed in the background." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:73 +msgid ":guilabel:`Custom`: upload a custom background image." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:77 +msgid ":guilabel:`Company tagline`: This is displayed in the header of :ref:`external reports `. You can add multiple lines of text." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:82 +msgid ":guilabel:`Company details`: These are displayed in the header of :ref:`external reports `. You can add multiple lines of text." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:87 +msgid ":guilabel:`Footer`: This text is used in the footer of :ref:`external reports `. You can add multiple lines of text. You can also edit the footer using the :ref:`report editor `." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:93 +msgid ":guilabel:`Paper format`: to define the default paper size of reports. You can select :guilabel:`A4` (21 cm x 29.7 cm), :guilabel:`US Letter` (21.59 cm x 27.54 cm), or :guilabel:`QR codes page`. This can also be defined for individual reports in the :guilabel:`Paper format` field in :ref:`Studio `." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:101 +msgid "Creating new PDF reports" +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:103 +msgid "To create a new report for a model, access the model, click the **Toggle Studio** button, then click :guilabel:`Reports`. Click :guilabel:`New` and, in the popup window that opens, select the type of report. This is solely used to determine what is displayed in the header and footer:" +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:109 +msgid ":guilabel:`External`:" +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:111 +msgid "The header displays the company's :ref:`logo `, :ref:`tagline `, and :ref:`details `." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:114 +msgid "The footer displays the values set in the :ref:`Footer ` field and the page number." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:117 +msgid ":guilabel:`Internal`: The header displays the user's current date and time, :guilabel:`Company Name`, and page number. There is no footer." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:120 +msgid ":guilabel:`Blank`: There is neither a header nor a footer. Click in the upper left corner of the page to edit the report." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:123 +msgid "Once you have created the report, you can start :ref:`editing it `." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:128 +msgid "Editing PDF reports" +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:130 +msgid "To access the reports available for a model, access the model (e.g., sales orders), click the **Toggle Studio** button, then click :guilabel:`Reports`. Select an existing report to open it or :ref:`create a new one `." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:135 +msgid "Alternatively, you can also open Studio, click :guilabel:`Reports`, and search for a specific report or model." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:139 +msgid "It is strongly recommended to **duplicate** the standard report and perform changes in the duplicated version. To duplicate a report, hover the mouse pointer on the top right corner of the report, click the vertical ellipsis icon (:guilabel:`⋮`), and then select :guilabel:`Duplicate`." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:0 +msgid "Duplicating a PDF report" +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:148 +msgid "Options" +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:150 +msgid "Once you've selected or created a report, you can use the options in the left part of the screen to:" +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:152 +msgid "Change the :guilabel:`Report name`. The new name is applied everywhere (in Studio, under the :guilabel:`Print` button, and in the PDF file name)." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:154 +msgid "Modify the :guilabel:`Paper format`. If no value is selected, the format defined in the :ref:`default layout ` is used." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:156 +msgid ":guilabel:`Show in print menu`: to add the report in the :guilabel:`Print` menu available from the record." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:158 +msgid ":guilabel:`Reload from attachment`: to save the report as an attachment on the record the first time it is generated and reload the original version of the report any subsequent time. This is legally required for invoices and is mainly used in this case." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:161 +msgid ":guilabel:`Limit visibility to groups`: to limit the availability of the PDF report to specific :doc:`user groups <../general/users/access_rights>`." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:163 +msgid ":guilabel:`Edit sources`: to modify the report directly in the :ref:`XML file `." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:165 +msgid ":guilabel:`Reset report`: to discard all changes made to the report and reset it to its standard version." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:167 +msgid ":guilabel:`Print preview`: to generate and download a report preview." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:170 +msgid "Report editor" +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:172 +msgid "The report editor allows you to modify the formatting and contents of the report." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:175 +msgid "You can :guilabel:`Undo` or :guilabel:`Redo` changes using the related buttons or the shortcuts `CTRL Z` and `CTRL Y`." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:178 +msgid "Changes are saved automatically when you leave the report or manually using the :guilabel:`Save` button." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:181 +msgid "You can reset the report to its standard version by clicking the :guilabel:`Reset report` button in the left part of the screen." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:185 +msgid "Editing the header and footer of a report impacts all standard and custom reports." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:188 +msgid "Conditional blocks" +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:190 +msgid "The dashed rectangles represent **conditional blocks** (*if/else* statements). These are used to show/hide content based on specific conditions. Click on the block to view the conditions." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:-1 +msgid "View conditions applied to a block." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:196 +msgid "Select a value to preview its corresponding output and edit it if necessary." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:-1 +msgid "Preview the output of another condition." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:202 +msgid "Conditions can only be edited in :ref:`XML `." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:205 +msgid "Other content" +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:207 +msgid "There are two types of text content in reports:" +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:209 +msgid "Static text, i.e., the text that's not highlighted in blue, which can be modified directly in the editor." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:211 +msgid "Dynamic text, i.e., the text that's highlighted in blue, which is replaced by field values when the report is generated, e.g., the SO number or the quotation date." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:214 +msgid "You can add content (e.g., fields, lists, tables, images, banners, etc.) to the report using commands. Type `/` to open the :ref:`powerbox `, then type the command's name or select it from the list." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:218 +msgid "To add static text to the report, type the text where you want it." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:220 +msgid "For more advanced changes, you can :ref:`edit the report in the XML directly `." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:226 +msgid "Add a field" +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:228 +msgid "To add a field, type `/` and select the :guilabel:`Field` command. In the list that opens, select or search for the field; click the right arrow next to the field name to access the list of related fields if needed. Then, specify the default value and press `Enter`." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:-1 +msgid "Select a related field." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:236 +msgid "Add a data table" +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:238 +msgid "Data tables are used to display :ref:`relational fields `. To add a data table, type `/`, select the :guilabel:`Dynamic Table` command, and select the relation to be displayed in the table." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:243 +msgid "Only relations of type `one2many` or `many2many` can be displayed as data tables." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:245 +msgid "Once the table has been added, you can add columns using the table tools. Position the cursor on top of the column, then click the purple rectangle and select an option." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:-1 +msgid "Add a column in a dynamic table." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:251 +msgid "You can then insert the :ref:`field of your choice ` in the columns. The dialog box that opens shows the source object for the field (e.g., the *Tag* model) and the list of available fields." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:-1 +msgid "List of available fields for the Tag model." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:259 +msgid "The default row automatically iterates over the field's content, generating a row on the report for each field value (e.g., one row per tag). You can add static content rows above or below the generated rows using the table tools." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:262 +msgid "You can also add data tables by :ref:`modifying the report's XML `." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:265 +msgid "Formatting" +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:267 +msgid "To format text in the report, select it, then format it using the options in the :ref:`knowledge/text-editor`." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:0 +msgid "Format text using the text editor." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:276 +msgid "Editing the report's XML" +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:279 +msgid "Modifying the XML directly may result in report issues during :doc:`upgrades <../../../administration/upgrade>`. If this happens, simply copy your changes from the old database into your upgraded database." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:283 +msgid "To edit the report's XML, click :guilabel:`Edit sources` in the left pane." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:286 +msgid "Examples" +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:290 +msgid "Sometimes, tables are not properly recognized as such due to complex structures. In those cases, you can still modify them manually in the report XML. For example, with a sales order, you can find the following structure in the XML (simplified for documentation purposes):" +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:318 +msgid "To modify a table, you must ensure that each row has the same number of data cells. For example, in the case above, you need to add a cell in the header section (with e.g., the column title) and another one in the body section with the field content (usually, with a `t-out` or `t-field` directive)." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:344 +msgid "Cells can span multiple rows or columns. For more information, go to the `Mozilla Developer Network website `_." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:347 +msgid "For example, you can modify the **Quotation/Order** report to add a column to display the product category in the main table:" +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:0 +msgid "Add a Product Category column in a SO." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:376 +msgid "To add a table in XML, you need to know the names of the fields and objects you wish to access and display. As an example, let's add a table that details the tags on a sales order:" +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:0 +msgid "Add a data table in XML" +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:407 +msgid "When adding tables manually, style them using `Bootstrap classes `_, like the `table` class included in the example above." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:413 +msgid "If you want to show/hide content based on specific conditions, you can manually add `if/else` control statements in the report XML." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:416 +msgid "For example, if you want to hide a custom data table if there are no tags, you can use the `t-if` attribute to define the condition, which is then evaluated as `True` or `False`. The table will not be displayed if there are no tags in the quotation." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:445 +msgid "If you want to display another block in case the `t-if` statement is evaluated as `False`, you can specify it using the `t-else` statement. The `t-else` block must directly follow the `t-if` block in the document structure. There is no need to specify any condition in the `t-else` attribute. As an example, let's show a quick message explaining that there are no tags on the quotation:" +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:477 +msgid "By using the `t-if/t-else` notation, the report editor recognizes that these sections are mutually exclusive and should be displayed as conditional blocks:" +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:0 +msgid "Output preview if there are tags." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:483 +msgid "You can switch conditions using the editor to preview their output:" +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:0 +msgid "Output preview if there are no tags." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:488 +msgid "If you wish to have multiple options, you can also use `t-elif` directives to add intermediary conditions. For example, this is how the title of sales order reports changes based on the condition of the underlying document." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:501 +msgid "The title *Pro-Forma Invoice* is used depending on some contextual conditions. If these conditions are not met and the state of the document is either `draft` or `sent`, then *Quotation* is used. If none of those conditions are met, the report's title is *Order*." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:507 +msgid "Working with images in a report can be challenging, as precise control over image size and behavior is not always obvious. You can insert image fields using the report editor (:ref:`by using the /Field command `), but inserting them in XML using the `t-field` directive and accompanying `t-options` attributes provides better sizing and positioning control." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:513 +msgid "For example, the following code outputs the field `image_128` of the line's product as a 64px-wide image (with an automatic height based on the image's aspect ratio)." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:520 +msgid "The following options are available for image widgets:" +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:522 +msgid "`width`: width of the image, usually in pixels or CSS length units (e.g., `rem`) (leave empty for auto-width)." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:524 +msgid "`height`: height of the image, usually in pixels or CSS length units (e.g., `rem`) (leave empty for auto-height)." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:526 +msgid "`class`: CSS classes applied on the `img` tag; `Bootstrap classes `_ are available." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:528 +msgid "`alt`: alternative text of the image" +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:529 +msgid "`style`: style attribute; it allows you to override styles more freely than with `Bootstrap classes `_." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:532 +msgid "These attributes must contain strings, i.e., text enclosed within quotes within quotes, e.g., `t-options-width=\"'64px'\"` (or, alternatively, a valid Python expression)." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:536 +msgid "The image widget cannot be used on an `img` tag. Instead, set the `t-field` directive on a `span` (for inline content) or `div` (for block content) node." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:539 +msgid "For example, let's add a column with the product image in the quotation table:" +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:567 +msgid "The `t-options-width` attribute restricts the image width to 64 pixels, and the Bootstrap classes used in `t-options-class` create a thumbnail-like border with rounded corners and a shadow." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:0 +msgid "Add a column with the product image in the quotation table." +msgstr "" + +#: ../../content/applications/studio/views.rst:3 +msgid "Views" +msgstr "" + +#: ../../content/applications/studio/views.rst:5 +msgid "Views are the interface that allows displaying the data contained in a model. One model can have several views, which are simply different ways to show the same data. In Studio, views are organized into four categories: :ref:`general `, :ref:`multiple records `, :ref:`timeline `, and :ref:`reporting `." +msgstr "" + +#: ../../content/applications/studio/views.rst:12 +msgid "To change the default view of a model, go to :menuselection:`Studio --> Views --> Dropdown menu (⋮) --> Set as Default`." +msgstr "" + +#: ../../content/applications/studio/views.rst:16 +msgid "You can modify views by using the built-in XML editor. To do so, activate :ref:`Developer mode `, go to the view you want to edit, select the :guilabel:`View` tab and then click on :guilabel:` XML`." +msgstr "" + +#: ../../content/applications/studio/views.rst:21 +msgid "If you are editing a view using the XML editor, avoid making changes directly to standard views and inherited views, as those would be reset and would not be kept in case of an update or module upgrade. Always make sure you select the right Studio inherited views. Indeed, when you modify a view in Studio by drag-and-dropping a new field, a specific Studio inherited view and its XPath, the latter which defines which part of the view is modified, are automatically generated." +msgstr "" + +#: ../../content/applications/studio/views.rst:31 +msgid "General views" +msgstr "" + +#: ../../content/applications/studio/views.rst:34 +#: ../../content/applications/studio/views.rst:97 +#: ../../content/applications/studio/views.rst:195 +#: ../../content/applications/studio/views.rst:311 +msgid "The settings described below are found under the view's :guilabel:`View` tab unless specified otherwise." +msgstr "" + +#: ../../content/applications/studio/views.rst:40 +msgid "Form" +msgstr "" + +#: ../../content/applications/studio/views.rst:42 +msgid "The :guilabel:`Form` view is used when creating and editing records, such as contacts, sales orders, products, etc." +msgstr "" + +#: ../../content/applications/studio/views.rst:45 +msgid "To structure a form, drag-and-drop the :guilabel:`Tabs and Columns` element found under the :guilabel:`+ Add` tab." +msgstr "" + +#: ../../content/applications/studio/views.rst:47 +#: ../../content/applications/studio/views.rst:132 +msgid "To prevent users from creating, editing, or deleting records, untick :guilabel:`Can Create`, :guilabel:`Can Edit`, or :guilabel:`Can Delete`." +msgstr "" + +#: ../../content/applications/studio/views.rst:0 +msgid "Sales order model's Form view" +msgstr "" + +#: ../../content/applications/studio/views.rst:59 +msgid "Activity" +msgstr "" + +#: ../../content/applications/studio/views.rst:61 +msgid "The :guilabel:`Activity` view is used to schedule and have an overview of activities (emails, calls, etc.) linked to records." +msgstr "" + +#: ../../content/applications/studio/views.rst:65 +msgid "This view can only be modified within Studio by editing the XML code." +msgstr "" + +#: ../../content/applications/studio/views.rst:0 +msgid "Lead/Opportunity model's Activity view" +msgstr "" + +#: ../../content/applications/studio/views.rst:76 +msgid "Search" +msgstr "" + +#: ../../content/applications/studio/views.rst:78 +msgid "The :guilabel:`Search` view is added on top of other views to filter, group, and search records." +msgstr "" + +#: ../../content/applications/studio/views.rst:80 +msgid "To add custom :guilabel:`Filters` and structure them using :guilabel:`Separators`, go to the :guilabel:`+ Add` tab and drag and drop them under :guilabel:`Filters`." +msgstr "" + +#: ../../content/applications/studio/views.rst:82 +msgid "To add an existing field under the search dropdown menu, go to the :guilabel:`+ Add` tab and drag-and-drop it under :guilabel:`Autocompletion Fields`." +msgstr "" + +#: ../../content/applications/studio/views.rst:0 +msgid "Project model's Search view on the Kanban view" +msgstr "" + +#: ../../content/applications/studio/views.rst:94 +msgid "Multiple records views" +msgstr "" + +#: ../../content/applications/studio/views.rst:103 +msgid "Kanban" +msgstr "" + +#: ../../content/applications/studio/views.rst:105 +msgid "The :guilabel:`Kanban` view is often used to support business flows by moving records across stages or as an alternative way to display records inside *cards*." +msgstr "" + +#: ../../content/applications/studio/views.rst:109 +msgid "If the :guilabel:`Kanban` view exists, it is used by default to display data on mobile devices instead of the :ref:`List view `." +msgstr "" + +#: ../../content/applications/studio/views.rst:112 +msgid "To prevent users from creating new records, untick :guilabel:`Can Create`." +msgstr "" + +#: ../../content/applications/studio/views.rst:113 +msgid "To create records directly within the view, in a minimalistic form, enable :guilabel:`Quick Create`." +msgstr "" + +#: ../../content/applications/studio/views.rst:115 +msgid "To change the way records are grouped by default, select a new group under :guilabel:`Default Group by`." +msgstr "" + +#: ../../content/applications/studio/views.rst:0 +msgid "Project model's Kanban view" +msgstr "" + +#: ../../content/applications/studio/views.rst:127 +msgid "List" +msgstr "" + +#: ../../content/applications/studio/views.rst:129 +msgid "The :guilabel:`List` view is used to overview many records at once, look for records, and edit simple records." +msgstr "" + +#: ../../content/applications/studio/views.rst:134 +msgid "To create and edit records directly within the view, select either :guilabel:`New record on top` or :guilabel:`New record at the bottom` under :guilabel:`Editable`." +msgstr "" + +#: ../../content/applications/studio/views.rst:138 +msgid "This prevents users from opening records in :ref:`Form view ` from the :guilabel:`List` view." +msgstr "" + +#: ../../content/applications/studio/views.rst:141 +msgid "To edit several records at once, tick :guilabel:`Enable Mass Editing`." +msgstr "" + +#: ../../content/applications/studio/views.rst:142 +msgid "To change the way records are sorted by default, select a field under :guilabel:`Sort By`." +msgstr "" + +#: ../../content/applications/studio/views.rst:145 +msgid "To add a drag handle icon to reorder records manually, add an :ref:`Integer field ` with the :guilabel:`Handle` widget." +msgstr "" + +#: ../../content/applications/studio/views.rst:0 +msgid "Drag handle icon enabling to sort records manually in List view" +msgstr "" + +#: ../../content/applications/studio/views.rst:0 +msgid "Sales order model's List view" +msgstr "" + +#: ../../content/applications/studio/views.rst:161 +msgid "Map" +msgstr "" + +#: ../../content/applications/studio/views.rst:163 +msgid "The :guilabel:`Map` view is used to display records on a map. For example, it is used in the Field Service app to plan an itinerary between different tasks." +msgstr "" + +#: ../../content/applications/studio/views.rst:167 +msgid "A :ref:`Many2One field ` linked to the *Contact* model is required to activate the view, as the contact address is used to position records on the map." +msgstr "" + +#: ../../content/applications/studio/views.rst:170 +msgid "To select which kind of contact should be used on the map, select it under :guilabel:`Contact Field`." +msgstr "" + +#: ../../content/applications/studio/views.rst:172 +msgid "To hide the name or the address of the record, tick :guilabel:`Hide name` or :guilabel:`Hide Address`." +msgstr "" + +#: ../../content/applications/studio/views.rst:174 +msgid "To add information from other fields, select them under :guilabel:`Additional Fields`." +msgstr "" + +#: ../../content/applications/studio/views.rst:175 +msgid "To have a route suggested between the different records, tick :guilabel:`Enable Routing` and select which field should be used to sort records for the routing." +msgstr "" + +#: ../../content/applications/studio/views.rst:0 +msgid "Task model's Map view" +msgstr "" + +#: ../../content/applications/studio/views.rst:187 +msgid "Timeline views" +msgstr "" + +#: ../../content/applications/studio/views.rst:190 +msgid "When you first activate one of the timeline views, you need to select which :ref:`Date ` or :ref:`Date & Time ` fields on your model should be used to define when the records start and stop in order to display them on the view. You can modify the :guilabel:`Start Date Field` and :guilabel:`Stop Date Field` after activating the view." +msgstr "" + +#: ../../content/applications/studio/views.rst:201 +msgid "Calendar" +msgstr "" + +#: ../../content/applications/studio/views.rst:203 +msgid "The :guilabel:`Calendar` view is used to overview and manage records inside a calendar." +msgstr "" + +#: ../../content/applications/studio/views.rst:205 +msgid "To create records directly within the view instead of opening the :ref:`Form view `, enable :guilabel:`Quick Create`." +msgstr "" + +#: ../../content/applications/studio/views.rst:209 +msgid "This only works on specific models that can be *quick-created* using only a *name*. However, most models do not support quick creation and open the :guilabel:`Form` view to fill in the required fields." +msgstr "" + +#: ../../content/applications/studio/views.rst:213 +msgid "To color records on the calendar, select a field under :guilabel:`Color`. All the records sharing the same value for that field are displayed using the same color." +msgstr "" + +#: ../../content/applications/studio/views.rst:217 +msgid "As the number of colors is limited, the same color can end up being assigned to different values." +msgstr "" + +#: ../../content/applications/studio/views.rst:220 +msgid "To display events lasting the whole day at the top of the calendar, select a :ref:`Checkbox field ` that specifies if the event lasts the whole day." +msgstr "" + +#: ../../content/applications/studio/views.rst:223 +msgid "To choose the default time scale used to display events, select :guilabel:`Day`, :guilabel:`Week`, :guilabel:`Month`, or :guilabel:`Year` under :guilabel:`Default Display Mode`." +msgstr "" + +#: ../../content/applications/studio/views.rst:227 +msgid "You can also use :guilabel:`Delay Field` to display the duration of the event in hours by selecting a :ref:`Decimal ` or :ref:`Integer ` field on the model which specifies the duration of the event. However, if you set an :guilabel:`End Date Field`, the :guilabel:`Delay Field` will not be taken into account." +msgstr "" + +#: ../../content/applications/studio/views.rst:0 +msgid "Calendar Event model's Calendar view" +msgstr "" + +#: ../../content/applications/studio/views.rst:242 +msgid "Cohort" +msgstr "" + +#: ../../content/applications/studio/views.rst:244 +msgid "The :guilabel:`Cohort` view is used to examine the life cycle of records over a time period. For example, it is used in the Subscriptions app to view the subscriptions' retention rate." +msgstr "" + +#: ../../content/applications/studio/views.rst:247 +msgid "To display a measure (i.e., the aggregated value of a given field) by default on the view, select a :guilabel:`Measure Field`." +msgstr "" + +#: ../../content/applications/studio/views.rst:249 +msgid "To choose which time interval is used by default to group results, select :guilabel:`Day`, :guilabel:`Week`, :guilabel:`Month`, or :guilabel:`Year` under :guilabel:`Interval`." +msgstr "" + +#: ../../content/applications/studio/views.rst:251 +msgid "To change the cohort :guilabel:`Mode`, select either :guilabel:`Retention` :dfn:`the percentage of records staying over a period of time, it starts at 100% and decreases with time` or :guilabel:`Churn` :dfn:`the percentage of records moving out over a period of time - it starts at 0% and increases with time`." +msgstr "" + +#: ../../content/applications/studio/views.rst:255 +msgid "To change the way the :guilabel:`Timeline` (i.e., the columns) progresses, select either :guilabel:`Forward` (from 0 to +15) or :guilabel:`Backward` (from -15 to 0). For most purposes, the :guilabel:`Forward` timeline is used." +msgstr "" + +#: ../../content/applications/studio/views.rst:0 +msgid "Subscription model's Cohort view" +msgstr "" + +#: ../../content/applications/studio/views.rst:268 +msgid "Gantt" +msgstr "" + +#: ../../content/applications/studio/views.rst:270 +msgid "The :guilabel:`Gantt` view is used to forecast and examine the overall progress of records. Records are represented by a bar under a time scale." +msgstr "" + +#: ../../content/applications/studio/views.rst:273 +msgid "To prevent users from creating or editing records, untick :guilabel:`Can Create` or :guilabel:`Can Edit`." +msgstr "" + +#: ../../content/applications/studio/views.rst:275 +msgid "To fill cells in gray whenever a record should not be created there (e.g., on weekends for employees), tick :guilabel:`Display Unavailability`." +msgstr "" + +#: ../../content/applications/studio/views.rst:279 +msgid "The underlying model must support this feature, and support for it cannot be added using Studio. It is supported for the Project, Time Off, Planning, and Manufacturing apps." +msgstr "" + +#: ../../content/applications/studio/views.rst:282 +msgid "To show a total row at the bottom, tick :guilabel:`Display Total row`." +msgstr "" + +#: ../../content/applications/studio/views.rst:283 +msgid "To collapse multiple records in a single row, tick :guilabel:`Collapse First Level`." +msgstr "" + +#: ../../content/applications/studio/views.rst:284 +msgid "To choose which way records are grouped by default on rows (e.g., per employee or project), select a field under :guilabel:`Default Group by`." +msgstr "" + +#: ../../content/applications/studio/views.rst:286 +msgid "To define a default time scale to view records, select :guilabel:`Day`, :guilabel:`Week`, :guilabel:`Month`, or :guilabel:`Year` under :guilabel:`Default Scale`." +msgstr "" + +#: ../../content/applications/studio/views.rst:288 +msgid "To color records on the view, select a field under :guilabel:`Color`. All the records sharing the same value for that field are displayed using the same color." +msgstr "" + +#: ../../content/applications/studio/views.rst:292 +msgid "As the number of colors is limited, the same color can be assigned to different values." +msgstr "" + +#: ../../content/applications/studio/views.rst:294 +msgid "To specify with which degree of precision each time scale should be divided by, select :guilabel:`Quarter Hour`, :guilabel:`Half Hour`, or :guilabel:`Hour` under :guilabel:`Day Precision`, :guilabel:`Half Day` or :guilabel:`Day` under :guilabel:`Week Precision`, and :guilabel:`Month Precision`." +msgstr "" + +#: ../../content/applications/studio/views.rst:0 +msgid "Planning Shift model's Gantt view" +msgstr "" + +#: ../../content/applications/studio/views.rst:308 +msgid "Reporting views" +msgstr "" + +#: ../../content/applications/studio/views.rst:317 +msgid "Pivot" +msgstr "" + +#: ../../content/applications/studio/views.rst:319 +msgid "The :guilabel:`Pivot` view is used to explore and analyze the data contained in records in an interactive manner. It is especially useful to aggregate numeric data, create categories, and drill down the data by expanding and collapsing different levels of data." +msgstr "" + +#: ../../content/applications/studio/views.rst:323 +msgid "To access all records whose data is aggregated under a cell, tick :guilabel:`Access records from cell`." +msgstr "" + +#: ../../content/applications/studio/views.rst:325 +msgid "To divide the data into different categories, select field(s) under :guilabel:`Column grouping`, :guilabel:`Row grouping - First level`, or :guilabel:`Row grouping - Second level`." +msgstr "" + +#: ../../content/applications/studio/views.rst:327 +msgid "To add different types of data to be measured using the view, select a field under :guilabel:`Measures`." +msgstr "" + +#: ../../content/applications/studio/views.rst:329 +msgid "To display a count of records that made up the aggregated data in a cell, tick :guilabel:`Display count`." +msgstr "" + +#: ../../content/applications/studio/views.rst:0 +msgid "Purchase Report model's Pivot view" +msgstr "" + +#: ../../content/applications/studio/views.rst:341 +msgid "Graph" +msgstr "" + +#: ../../content/applications/studio/views.rst:343 +msgid "The :guilabel:`Graph` view is used to showcase data from records in a bar, line, or pie chart." +msgstr "" + +#: ../../content/applications/studio/views.rst:345 +msgid "To change the default chart, select :guilabel:`Bar`, :guilabel:`Line`, or :guilabel:`Pie` under :guilabel:`Type`." +msgstr "" + +#: ../../content/applications/studio/views.rst:347 +msgid "To choose a default data dimension (category), select a field under :guilabel:`First dimension` and, if needed, another under :guilabel:`Second dimension`." +msgstr "" + +#: ../../content/applications/studio/views.rst:349 +msgid "To select a default type of data to be measured using the view, select a field under :guilabel:`Measure`." +msgstr "" + +#: ../../content/applications/studio/views.rst:351 +msgid "*For Bar and Line charts only*: To sort the different data categories by their value, select :guilabel:`Ascending` (from lowest to highest value) or :guilabel:`Descending` (from highest to lowest) under :guilabel:`Sorting`." +msgstr "" + +#: ../../content/applications/studio/views.rst:354 +msgid "*For Bar and Pie charts only*: To access all records whose data is aggregated under a data category on the chart, tick :guilabel:`Access records from graph`." +msgstr "" + +#: ../../content/applications/studio/views.rst:356 +msgid "*For Bar charts only*: When using two data dimensions (categories), display the two columns on top of each other by default by ticking :guilabel:`Stacked graph`." +msgstr "" + +#: ../../content/applications/studio/views.rst:0 +msgid "Sales Analysis Report model's Bar chart on Graph view" +msgstr "" + +#: ../../content/applications/studio/views.rst:368 +msgid "Dashboard" +msgstr "" + +#: ../../content/applications/studio/views.rst:370 +msgid "The :guilabel:`Dashboard` view is used to display multiple reporting views and key performance indicators. Which elements are displayed on the view depends on the configuration of the other reporting views." +msgstr "" + +#: ../../content/applications/studio/views.rst:0 +msgid "Sales Analysis Report model's Dashboard view" +msgstr "" diff --git a/locale/sources/websites.pot b/locale/sources/websites.pot index 2c5b300a5..c251d1577 100644 --- a/locale/sources/websites.pot +++ b/locale/sources/websites.pot @@ -8,7 +8,7 @@ msgid "" msgstr "" "Project-Id-Version: Odoo 17.0\n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2024-03-08 12:48+0000\n" +"POT-Creation-Date: 2024-03-25 16:01+0000\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME \n" "Language-Team: LANGUAGE \n" @@ -53,7 +53,7 @@ msgid "Go to your website, click :guilabel:`+New` in the top-right corner, and s msgstr "" #: ../../content/applications/websites/blog.rst:30 -msgid "Illustrate your articles with copyright-free images from :doc:`Unsplash `." +msgid "Illustrate your articles with copyright-free images from :doc:`Unsplash `." msgstr "" #: ../../content/applications/websites/blog.rst:32 @@ -217,7 +217,7 @@ msgid ":guilabel:`Select To Tweet`: visitors are offered to tweet the text they msgstr "" #: ../../content/applications/websites/blog.rst:129 -msgid "Use :ref:`Plausible ` to keep track of the traffic on your blog." +msgid "Use :ref:`Plausible ` to keep track of the traffic on your blog." msgstr "" #: ../../content/applications/websites/ecommerce.rst:8 @@ -328,8 +328,8 @@ msgstr "" msgid "The 'Contact Us' button and '*Not Available For Sale*' text can both be modified using the **website builder** on the product's page (:menuselection:`Edit --> Customize`) by clicking on them." msgstr "" -#: ../../content/applications/websites/ecommerce/checkout_payment_shipping/cart.rst:-1 #: ../../content/applications/websites/ecommerce/checkout_payment_shipping/cart.rst:63 +#: ../../content/applications/websites/ecommerce/checkout_payment_shipping/cart.rst:-1 msgid "Customizable 'Add to Cart' button" msgstr "" @@ -389,8 +389,8 @@ msgstr "" msgid "Note that content added through building blocks is **specific** to each step." msgstr "" -#: ../../content/applications/websites/ecommerce/checkout_payment_shipping/checkout.rst:-1 #: ../../content/applications/websites/ecommerce/checkout_payment_shipping/checkout.rst:16 +#: ../../content/applications/websites/ecommerce/checkout_payment_shipping/checkout.rst:-1 msgid "Checkout steps" msgstr "" @@ -1044,7 +1044,7 @@ msgid "Analytics" msgstr "" #: ../../content/applications/websites/ecommerce/ecommerce_management/performance.rst:33 -msgid "It is possible to link your Odoo website with :ref:`website/analytics/plausible` and :ref:`website/analytics/GA`." +msgid "It is possible to link your Odoo website with :ref:`analytics/plausible` and :ref:`analytics/google-analytics`." msgstr "" #: ../../content/applications/websites/ecommerce/managing_products.rst:5 @@ -3211,7 +3211,7 @@ msgid "If this channel should only be available to site visitors in specific cou msgstr "" #: ../../content/applications/websites/livechat.rst:185 -msgid "In order to track the geographical location of visitors, :guilabel:`GeoIP` must be installed on the database. While this feature is installed by default on *Odoo Online*, *On-Premise* databases will require additional :doc:`setup steps `." +msgid "In order to track the geographical location of visitors, :guilabel:`GeoIP` must be installed on the database. While this feature is installed by default on *Odoo Online*, *On-Premise* databases will require additional :doc:`setup steps `." msgstr "" #: ../../content/applications/websites/livechat.rst:190 @@ -3323,7 +3323,7 @@ msgid "Click on a conversation in the left panel to select it. This will open th msgstr "" #: ../../content/applications/websites/livechat.rst:288 -msgid ":doc:`Get Started with Discuss `" +msgid ":doc:`Get Started with Discuss `" msgstr "" #: ../../content/applications/websites/livechat.rst:289 @@ -3832,11 +3832,11 @@ msgid "View of the message generated from using the /help command in Odoo Live C msgstr "" #: ../../content/applications/websites/livechat/responses.rst:48 -msgid ":doc:`/applications/productivity/discuss/overview/get_started`" +msgid ":doc:`/applications/productivity/discuss`" msgstr "" #: ../../content/applications/websites/livechat/responses.rst:49 -msgid ":doc:`/applications/productivity/discuss/overview/team_communication`" +msgid ":doc:`/applications/productivity/discuss/team_communication`" msgstr "" #: ../../content/applications/websites/livechat/responses.rst:52 @@ -3867,6 +3867,7 @@ msgstr "" msgid "After entering the `/helpdesk` command, type a title for the ticket into the chat window, then press `Enter`." msgstr "" +#: ../../content/applications/websites/livechat/responses.rst:-1 #: ../../content/applications/websites/livechat/responses.rst:-1 msgid "View of the results from a helpdesk search in a Live Chat conversation." msgstr "" @@ -4099,6 +4100,118 @@ msgstr "" msgid "Do not share it publicly or expose it in client-side code." msgstr "" +#: ../../content/applications/websites/website/configuration/cdn.rst:3 +msgid "Set up a content delivery network (CDN)" +msgstr "" + +#: ../../content/applications/websites/website/configuration/cdn.rst:8 +msgid "Deploying with KeyCDN" +msgstr "" + +#: ../../content/applications/websites/website/configuration/cdn.rst:10 +msgid "A :abbr:`CDN (Content Delivery Network)` or *content distribution network*, is a geographically distributed network of servers that provides high speed internet content. The :abbr:`CDN (Content Delivery Network)` provides quick, high-quality content delivery for content-heavy websites." +msgstr "" + +#: ../../content/applications/websites/website/configuration/cdn.rst:14 +msgid "This document will guide you through the setup of a KeyCDN_ account with an Odoo powered website." +msgstr "" + +#: ../../content/applications/websites/website/configuration/cdn.rst:17 +msgid "Create a pull zone in the KeyCDN dashboard" +msgstr "" + +#: ../../content/applications/websites/website/configuration/cdn.rst:19 +msgid "On the KeyCDN dashboard, start by navigating to the :menuselection:`Zones` menu item on the left. On the form, give a value to the :guilabel:`Zone Name`, which will appear as part of the :abbr:`CDN (Content Delivery Network)`'s :abbr:`URL (Uniform Resource Locator)`. Then, set the :guilabel:`Zone Status` to :guilabel:`active` to engage the zone. For the :guilabel:`Zone Type` set the value to :guilabel:`Pull`, and then, finally, under the :guilabel:`Pull Settings`, enter the :guilabel:`Origin URL`— this address should be the full Odoo database :abbr:`URL (Uniform Resource Locator)`." +msgstr "" + +#: ../../content/applications/websites/website/configuration/cdn.rst:28 +msgid "Use ``https://yourdatabase.odoo.com`` and replace the *yourdatabase* subdomain prefix with the actual name of the database. A custom :abbr:`URL (Uniform Resource Locator)` can be used, as well, in place of the Odoo subdomain that was provided to the database." +msgstr "" + +#: ../../content/applications/websites/website/configuration/cdn.rst:-1 +msgid "KeyCDN's Zone configuration page." +msgstr "" + +#: ../../content/applications/websites/website/configuration/cdn.rst:36 +msgid "Under the :guilabel:`General Settings` heading below the zone form, click the :guilabel:`Show all settings` button to expand the zone options. This should be the last option on the page. After expanding the :guilabel:`General Settings` ensure that the :guilabel:`CORS` option is :guilabel:`enabled`." +msgstr "" + +#: ../../content/applications/websites/website/configuration/cdn.rst:41 +msgid "Next, scroll to the bottom of the zone configuration page and :guilabel:`Save` the changes. KeyCDN will indicate that the new zone will be deployed. This can take about 10 minutes." +msgstr "" + +#: ../../content/applications/websites/website/configuration/cdn.rst:-1 +msgid "KeyCDN deploying the new Zone." +msgstr "" + +#: ../../content/applications/websites/website/configuration/cdn.rst:49 +msgid "A new :guilabel:`Zone URL` has been generated for your Zone, in this example it is ``pulltest-xxxxx.kxcdn.com``. This value will differ for each database." +msgstr "" + +#: ../../content/applications/websites/website/configuration/cdn.rst:52 +msgid "Copy this :guilabel:`Zone URL` to a text editor for later, as it will be used in the next steps." +msgstr "" + +#: ../../content/applications/websites/website/configuration/cdn.rst:55 +msgid "Configure the Odoo instance with the new zone" +msgstr "" + +#: ../../content/applications/websites/website/configuration/cdn.rst:57 +msgid "In the Odoo :guilabel:`Website` app, go to the :menuselection:`Settings` and then activate the :guilabel:`Content Delivery Network (CDN)` setting and copy/paste the :guilabel:`Zone URL` value from the earlier step into the :guilabel:`CDN Base URL` field. This field is only visible and configurable when the :ref:`developer mode ` is activated." +msgstr "" + +#: ../../content/applications/websites/website/configuration/cdn.rst:63 +msgid "Ensure that there are two *forward slashes* (`//`) before the :guilabel:`CDN Base URL` and one forward slash (`/`) after the :guilabel:`CDN Base URL`." +msgstr "" + +#: ../../content/applications/websites/website/configuration/cdn.rst:66 +msgid ":guilabel:`Save` the settings when complete." +msgstr "" + +#: ../../content/applications/websites/website/configuration/cdn.rst:-1 +msgid "Activate the CDN setting in Odoo." +msgstr "" + +#: ../../content/applications/websites/website/configuration/cdn.rst:72 +msgid "Now the website is using the CDN for the resources matching the :guilabel:`CDN filters` regular expressions." +msgstr "" + +#: ../../content/applications/websites/website/configuration/cdn.rst:75 +msgid "In the HTML of the Odoo website, the :abbr:`CDN (content delivery network)` integration is evidenced as working properly by checking the :abbr:`URL (Uniform Resource Locators)` of images. The *CDN Base URL* value can be seen by using your web browser's :guilabel:`Inspect` feature on the Odoo website. Look for it's record by searching within the :guilabel:`Network` tab inside of devtools." +msgstr "" + +#: ../../content/applications/websites/website/configuration/cdn.rst:-1 +msgid "The CDN Base URL can be seen using the inspect function on the Odoo website." +msgstr "" + +#: ../../content/applications/websites/website/configuration/cdn.rst:85 +msgid "Prevent security issues by activating cross-origin resource sharing (CORS)" +msgstr "" + +#: ../../content/applications/websites/website/configuration/cdn.rst:87 +msgid "A security restriction in some browsers (such as Mozilla Firefox and Google Chrome) prevents a remotely linked CSS file to fetch relative resources on this same external server." +msgstr "" + +#: ../../content/applications/websites/website/configuration/cdn.rst:90 +msgid "If the :abbr:`CORS (Cross-Origin Resource Sharing)` option isn't enabled in the :guilabel:`CDN Zone`, the more obvious resulting problem on a standard Odoo website will be the lack of *Font Awesome* icons because the font file declared in the *Font Awesome* CSS won't be loaded from the remote server." +msgstr "" + +#: ../../content/applications/websites/website/configuration/cdn.rst:95 +msgid "When these cross-origin resource issues occur, a security error message similar to the output below will appear in the web browser's developer console:" +msgstr "" + +#: ../../content/applications/websites/website/configuration/cdn.rst:98 +msgid "``Font from origin 'http://pulltest-xxxxx.kxcdn.com' has been blocked from loading /shop:1 by Cross-Origin Resource Sharing policy: No 'Access-Control-Allow-Origin' header is present on the requested resource. Origin 'http://yourdatabase.odoo.com' is therefore not allowed access.``" +msgstr "" + +#: ../../content/applications/websites/website/configuration/cdn.rst:-1 +msgid "Error message populated in the browser console." +msgstr "" + +#: ../../content/applications/websites/website/configuration/cdn.rst:106 +msgid "Enabling the :abbr:`CORS (Cross-Origin Resource Sharing)` option in the :abbr:`CDN (Content Delivery Network)` settings fixes this issue." +msgstr "" + #: ../../content/applications/websites/website/configuration/cookies_bar.rst:3 msgid "Cookies bar" msgstr "" @@ -4191,6 +4304,404 @@ msgstr "" msgid "You could add a link providing access to this page, in your website's footer, for example." msgstr "" +#: ../../content/applications/websites/website/configuration/domain_names.rst:3 +msgid "Domain names" +msgstr "" + +#: ../../content/applications/websites/website/configuration/domain_names.rst:5 +msgid "Domain names are text-based addresses identifying online locations, such as websites. They provide a more memorable and recognizable way for people to navigate the internet than numerical IP addresses." +msgstr "" + +#: ../../content/applications/websites/website/configuration/domain_names.rst:8 +msgid "**Odoo Online** and **Odoo.sh** databases use a **subdomain** of the `odoo.com` **domain** by default (e.g., `mycompany.odoo.com`)." +msgstr "" + +#: ../../content/applications/websites/website/configuration/domain_names.rst:11 +msgid "However, you can use a custom domain name instead by :ref:`registering a free domain name ` (only available for Odoo Online databases) or by :ref:`configuring a domain name you already own `." +msgstr "" + +#: ../../content/applications/websites/website/configuration/domain_names.rst:16 +msgid "`Odoo Tutorials: Register a free domain name [video] `_" +msgstr "" + +#: ../../content/applications/websites/website/configuration/domain_names.rst:22 +msgid "Register a free domain name with Odoo" +msgstr "" + +#: ../../content/applications/websites/website/configuration/domain_names.rst:24 +msgid "To register a one-year free domain name for your Odoo Online database, sign in to your account and go to the `database manager `_. Click the gear icon (:guilabel:`⚙️`) next to the database name and select :guilabel:`Domain Names`." +msgstr "" + +#: ../../content/applications/websites/website/configuration/domain_names.rst:-1 +msgid "Accessing a database's domain names configuration" +msgstr "" + +#: ../../content/applications/websites/website/configuration/domain_names.rst:31 +msgid "Search for the desired domain name and check its availability." +msgstr "" + +#: ../../content/applications/websites/website/configuration/domain_names.rst:-1 +msgid "Searching for an available domain name" +msgstr "" + +#: ../../content/applications/websites/website/configuration/domain_names.rst:37 +msgid "Ensure the Website app is installed if the domain name registration option does not appear." +msgstr "" + +#: ../../content/applications/websites/website/configuration/domain_names.rst:39 +msgid "Select the desired domain name, fill in the :guilabel:`Domain Owner` form, and click :guilabel:`Register`. The chosen domain name is directly linked to the database." +msgstr "" + +#: ../../content/applications/websites/website/configuration/domain_names.rst:-1 +msgid "Filling in the domain owner information" +msgstr "" + +#: ../../content/applications/websites/website/configuration/domain_names.rst:45 +msgid "Next, you should :ref:`map your domain name to your Odoo website `." +msgstr "" + +#: ../../content/applications/websites/website/configuration/domain_names.rst:48 +msgid "A verification email from `noreply@domainnameverification.net` will be sent to the email address provided in the :guilabel:`Domain Owner` form. It is essential to verify your email address to keep the domain active and receive the renewal quote before expiration." +msgstr "" + +#: ../../content/applications/websites/website/configuration/domain_names.rst:52 +msgid "The domain name registration is free for the first year. After this period, Odoo will continue to manage the domain in partnership with **Gandi.net**, the domain name registrar, and you will be charged `Gandi.net's renewal rate `_. Odoo sends a renewal quotation every year to the email address mentioned in the :guilabel:`Domain Owner` form several weeks before the expiration date of the domain. The domain is renewed automatically when the quotation is confirmed." +msgstr "" + +#: ../../content/applications/websites/website/configuration/domain_names.rst:60 +msgid "The offer is only available for **Odoo Online** databases." +msgstr "" + +#: ../../content/applications/websites/website/configuration/domain_names.rst:61 +msgid "The offer is limited to **one** domain name per client." +msgstr "" + +#: ../../content/applications/websites/website/configuration/domain_names.rst:62 +msgid "The offer is limited to the registration of a **new** domain name." +msgstr "" + +#: ../../content/applications/websites/website/configuration/domain_names.rst:63 +msgid "The offer is available to *One App Free* plans. Ensure that your website contains enough original content for Odoo to verify that your request is legitimate and respects `Odoo's Acceptable Use Policy `_. Given the high number of requests, it can take Odoo several days to review them." +msgstr "" + +#: ../../content/applications/websites/website/configuration/domain_names.rst:71 +msgid "DNS records" +msgstr "" + +#: ../../content/applications/websites/website/configuration/domain_names.rst:73 +msgid "To manage your free domain name :abbr:`DNS (domain name system)` records, open the `database manager `_, click the gear icon (:guilabel:`⚙️`) next to the database name, select :guilabel:`Domain Names`, and click :guilabel:`DNS`." +msgstr "" + +#: ../../content/applications/websites/website/configuration/domain_names.rst:77 +msgid ":guilabel:`A`: the A record holds the IP address of the domain. It is automatically created and **cannot** be edited or deleted." +msgstr "" + +#: ../../content/applications/websites/website/configuration/domain_names.rst:79 +msgid ":guilabel:`CNAME`: CNAME records forward one domain or subdomain to another domain. One is automatically created to map the `www.` subdomain to the database. If the database is renamed, the CNAME record **must** also be renamed." +msgstr "" + +#: ../../content/applications/websites/website/configuration/domain_names.rst:82 +msgid ":guilabel:`MX`: MX records instruct servers on where to deliver emails." +msgstr "" + +#: ../../content/applications/websites/website/configuration/domain_names.rst:83 +msgid ":guilabel:`TXT`: TXT records can be used for different purposes (e.g., to verify domain name ownership)." +msgstr "" + +#: ../../content/applications/websites/website/configuration/domain_names.rst:86 +msgid "Any modification to the DNS records can take up to **72 hours** to propagate worldwide on all servers." +msgstr "" + +#: ../../content/applications/websites/website/configuration/domain_names.rst:90 +msgid "`Submit a support ticket `_ if you need assistance to manage your domain name." +msgstr "" + +#: ../../content/applications/websites/website/configuration/domain_names.rst:94 +msgid "Mailbox" +msgstr "" + +#: ../../content/applications/websites/website/configuration/domain_names.rst:96 +msgid "The one-year free domain name offer does **not** include a mailbox. There are two options to link your domain name with a mailbox." +msgstr "" + +#: ../../content/applications/websites/website/configuration/domain_names.rst:100 +msgid "Use a subdomain" +msgstr "" + +#: ../../content/applications/websites/website/configuration/domain_names.rst:102 +msgid "You can create a subdomain (e.g., `subdomain.yourdomain.com`) to use as an alias domain for the database. It allows users to create records in the database from emails received on their `email@subdomain.yourdomain.com` alias." +msgstr "" + +#: ../../content/applications/websites/website/configuration/domain_names.rst:106 +msgid "To do so, open the `database manager `_, click the gear icon (:guilabel:`⚙️`) next to the database name, and go to :menuselection:`Domain Names --> DNS --> Add DNS record --> CNAME`. Next, enter the desired subdomain in the :guilabel:`Name` field (e.g., `subdomain`), the original database domain with a period at the end (e.g., `mycompany.odoo.com.`) in the :guilabel:`Content` field, and click :guilabel:`Add record`." +msgstr "" + +#: ../../content/applications/websites/website/configuration/domain_names.rst:112 +msgid "Then, add the alias domain as your *own domain* by clicking :guilabel:`Use my own domain`, entering the alias domain (e.g., `subdomain.yourdomain.com`), clicking :guilabel:`Verify`, and then :guilabel:`I confirm, it's done`." +msgstr "" + +#: ../../content/applications/websites/website/configuration/domain_names.rst:116 +msgid "Finally, go to your database and open the :guilabel:`Settings`. Under the :guilabel:`Alias Domain` field, enter the alias domain (e.g., `subdomain.yourdomain.com`), click :guilabel:`Create`, and then :guilabel:`Save`." +msgstr "" + +#: ../../content/applications/websites/website/configuration/domain_names.rst:121 +msgid "Use an external email provider" +msgstr "" + +#: ../../content/applications/websites/website/configuration/domain_names.rst:123 +msgid "To use an external email provider, you should configure an MX record. To do so, open the `database manager `_, click the gear icon (:guilabel:`⚙️`) next to the database name, click :menuselection:`Domain Names --> DNS --> Add DNS record --> MX`. The values you should enter for the :guilabel:`Name`, :guilabel:`Content`, and :guilabel:`Priority` fields depend on the external email provider." +msgstr "" + +#: ../../content/applications/websites/website/configuration/domain_names.rst:130 +msgid "`Google Workspace: MX record values `_" +msgstr "" + +#: ../../content/applications/websites/website/configuration/domain_names.rst:131 +msgid "`Outlook and Exchange Online: Add an MX record for email `_" +msgstr "" + +#: ../../content/applications/websites/website/configuration/domain_names.rst:136 +msgid "Configure an existing domain name" +msgstr "" + +#: ../../content/applications/websites/website/configuration/domain_names.rst:138 +msgid "If you already have a domain name, you can use it for your Odoo website." +msgstr "" + +#: ../../content/applications/websites/website/configuration/domain_names.rst:141 +msgid "It is strongly recommended to follow **in order** these three steps to avoid any :ref:`SSL certificate validation ` issues:" +msgstr "" + +#: ../../content/applications/websites/website/configuration/domain_names.rst:144 +msgid ":ref:`Add a CNAME record `" +msgstr "" + +#: ../../content/applications/websites/website/configuration/domain_names.rst:145 +msgid ":ref:`Map your domain name to your Odoo database `" +msgstr "" + +#: ../../content/applications/websites/website/configuration/domain_names.rst:146 +msgid ":ref:`Map your domain name to your Odoo website `" +msgstr "" + +#: ../../content/applications/websites/website/configuration/domain_names.rst:151 +msgid "Add a CNAME record" +msgstr "" + +#: ../../content/applications/websites/website/configuration/domain_names.rst:153 +msgid "Creating a CNAME record to forward your domain name to the address of your Odoo database is required." +msgstr "" + +#: ../../content/applications/websites/website/configuration/domain_names.rst:158 +#: ../../content/applications/websites/website/configuration/domain_names.rst:212 +msgid "Odoo Online" +msgstr "" + +#: ../../content/applications/websites/website/configuration/domain_names.rst:160 +msgid "The CNAME record's target address should be your database's address as defined at its creation (e.g., `mycompany.odoo.com`)." +msgstr "" + +#: ../../content/applications/websites/website/configuration/domain_names.rst:163 +#: ../../content/applications/websites/website/configuration/domain_names.rst:222 +msgid "Odoo.sh" +msgstr "" + +#: ../../content/applications/websites/website/configuration/domain_names.rst:165 +msgid "The CNAME record's target address can be the project's main address, which can be found on Odoo.sh by going to :menuselection:`Settings --> Project Name`, or a specific branch (production, staging or development) by going to :menuselection:`Branches --> select the branch --> Settings --> Custom domains`, and clicking :guilabel:`How to set up my domain?`. A message indicates which address your CNAME record should target." +msgstr "" + +#: ../../content/applications/websites/website/configuration/domain_names.rst:171 +msgid "The specific instructions depend on your DNS hosting service." +msgstr "" + +#: ../../content/applications/websites/website/configuration/domain_names.rst:174 +msgid "`GoDaddy: Add a CNAME record `_" +msgstr "" + +#: ../../content/applications/websites/website/configuration/domain_names.rst:175 +msgid "`Namecheap: How to create a CNAME record for your domain `_" +msgstr "" + +#: ../../content/applications/websites/website/configuration/domain_names.rst:176 +msgid "`OVHcloud: Add a new DNS record `_" +msgstr "" + +#: ../../content/applications/websites/website/configuration/domain_names.rst:177 +msgid "`Cloudflare: Manage DNS records `_" +msgstr "" + +#: ../../content/applications/websites/website/configuration/domain_names.rst:180 +msgid "Creating a CNAME record to map the `www` subdomain (`www.yourdomain.com`) as some visitors are used to typing `www.` before entering a domain name." +msgstr "" + +#: ../../content/applications/websites/website/configuration/domain_names.rst:184 +msgid "You own the domain name `yourdomain.com`, and your Odoo Online database's address is `mycompany.odoo.com`. You want to access your Odoo database primarily with the domain `www.yourdomain.com` but also with the naked domain :dfn:`(a domain name without any subdomains or prefixes)` `yourdomain.com`." +msgstr "" + +#: ../../content/applications/websites/website/configuration/domain_names.rst:189 +msgid "To do so, create a CNAME record for the `www` subdomain, with `mycompany.odoo.com` as the target. Next, create a redirect (301 permanent or visible redirect) to redirect visitors from `yourdomain.com` to `wwww.yourdomain.com`." +msgstr "" + +#: ../../content/applications/websites/website/configuration/domain_names.rst:196 +msgid "Map a domain name to an Odoo database" +msgstr "" + +#: ../../content/applications/websites/website/configuration/domain_names.rst:199 +msgid "Ensure you have :ref:`added a CNAME record ` to your domain name's DNS **before** mapping your domain name to your Odoo database." +msgstr "" + +#: ../../content/applications/websites/website/configuration/domain_names.rst:202 +msgid "Failing to do so may prevent the validation of the :ref:`SSL certificate ` and could result in a *certificate name mismatch* error. Web browsers often display this as a warning, such as *\"Your connection is not private\"*." +msgstr "" + +#: ../../content/applications/websites/website/configuration/domain_names.rst:206 +msgid "If you encounter this error after mapping the domain name to your database, wait up to five days, as the validation may still happen. If not, you can `submit a support ticket `_, including screenshots of your CNAME records." +msgstr "" + +#: ../../content/applications/websites/website/configuration/domain_names.rst:214 +msgid "Open the `database manager `_, click the gear icon (:guilabel:`⚙️`) next to the database name, and go to :menuselection:`Domain Names --> Use my own domain`. Then, enter the domain name (e.g., `yourdomain.com`), click :guilabel:`Verify` and :guilabel:`I confirm, it's done`." +msgstr "" + +#: ../../content/applications/websites/website/configuration/domain_names.rst:0 +msgid "Mapping a domain name to an Odoo Online database" +msgstr "" + +#: ../../content/applications/websites/website/configuration/domain_names.rst:224 +msgid "On Odoo.sh, go to :menuselection:`Branches --> select your branch --> Settings --> Custom domains`, type the domain name to add, then click :guilabel:`Add domain`." +msgstr "" + +#: ../../content/applications/websites/website/configuration/domain_names.rst:0 +msgid "Mapping a domain name to an Odoo.sh branch" +msgstr "" + +#: ../../content/applications/websites/website/configuration/domain_names.rst:231 +msgid ":ref:`Odoo.sh branches: settings tab `" +msgstr "" + +#: ../../content/applications/websites/website/configuration/domain_names.rst:236 +msgid "SSL encryption (HTTPS protocol)" +msgstr "" + +#: ../../content/applications/websites/website/configuration/domain_names.rst:238 +msgid "**SSL encryption** allows visitors to navigate a website through a secure connection, which appears as the *https://* protocol at the beginning of a web address rather than the non-secure *http://* protocol." +msgstr "" + +#: ../../content/applications/websites/website/configuration/domain_names.rst:242 +msgid "Odoo generates a separate SSL certificate for each domain :ref:`mapped to a database ` using `Let's Encrypt's certificate authority and ACME protocol `_." +msgstr "" + +#: ../../content/applications/websites/website/configuration/domain_names.rst:247 +msgid "Certificate generation may take up to 24 hours." +msgstr "" + +#: ../../content/applications/websites/website/configuration/domain_names.rst:248 +msgid "Several attempts to validate your certificate are made for five days after you map your domain name to your database." +msgstr "" + +#: ../../content/applications/websites/website/configuration/domain_names.rst:250 +msgid "If you use another service, you can keep using it or change to Odoo's." +msgstr "" + +#: ../../content/applications/websites/website/configuration/domain_names.rst:253 +msgid "No SSL certificate is generated for naked domains :dfn:`(domain names without any subdomains or prefixes)`." +msgstr "" + +#: ../../content/applications/websites/website/configuration/domain_names.rst:259 +msgid "Web base URL of a database" +msgstr "" + +#: ../../content/applications/websites/website/configuration/domain_names.rst:262 +msgid "If the Website app is installed on your database, skip this section and continue from the :ref:`Map a domain name to a website ` section." +msgstr "" + +#: ../../content/applications/websites/website/configuration/domain_names.rst:265 +msgid "The *web base URL* or root URL of a database affects your main website address and all the links sent to your customers (e.g., quotations, portal links, etc.)." +msgstr "" + +#: ../../content/applications/websites/website/configuration/domain_names.rst:268 +msgid "To make your custom domain name the *web base URL* of your database, access your database using your custom domain name and log in as an administrator :dfn:`(a user part of the Settings access right group under Administration)`." +msgstr "" + +#: ../../content/applications/websites/website/configuration/domain_names.rst:273 +msgid "If you access your database with the original Odoo address (e.g., `mycompany.odoo.com`), the *web base URL* of your database will be updated accordingly. To prevent the automatic update of the *web base URL* when an administrator logs in to the database, activate the :ref:`developer mode `, go to :menuselection:`Settings --> Technical --> System Parameters --> New`, and enter `web.base.url.freeze` as the :guilabel:`Key` and `True` as the :guilabel:`Value`." +msgstr "" + +#: ../../content/applications/websites/website/configuration/domain_names.rst:280 +msgid "You can also set the web base URL manually. To do so, activate the :ref:`developer mode `, go to :menuselection:`Settings --> Technical --> System Parameters`, and search for the `web.base.url` key (create it if necessary) and enter the full address of your website as the value (e.g., `https://www.yourdomain.com`). The URL must include the protocol `https://` (or `http://`) and *not* end with a slash (`/`)." +msgstr "" + +#: ../../content/applications/websites/website/configuration/domain_names.rst:289 +msgid "Map a domain name to an Odoo website" +msgstr "" + +#: ../../content/applications/websites/website/configuration/domain_names.rst:291 +msgid "Mapping your domain name to your website is different than mapping it to your database:" +msgstr "" + +#: ../../content/applications/websites/website/configuration/domain_names.rst:293 +msgid "It defines your domain name as the main one for your website, helping search engines to index your website correctly." +msgstr "" + +#: ../../content/applications/websites/website/configuration/domain_names.rst:295 +msgid "It defines your domain name as the base URL for your database, including portal links sent by email to your customers." +msgstr "" + +#: ../../content/applications/websites/website/configuration/domain_names.rst:297 +msgid "If you have multiple websites, it maps your domain name to the appropriate website." +msgstr "" + +#: ../../content/applications/websites/website/configuration/domain_names.rst:299 +msgid "Go to :menuselection:`Website --> Configuration --> Settings`. If you have multiple websites, select the one you want to configure. In the :guilabel:`Domain` field, enter the address of your website (e.g., `https://www.yourdomain.com`) and :guilabel:`Save`." +msgstr "" + +#: ../../content/applications/websites/website/configuration/domain_names.rst:304 +msgid "Mapping your domain name to your Odoo website prevents Google Search from indexing your original database address (e.g., `mycompany.odoo.com`)." +msgstr "" + +#: ../../content/applications/websites/website/configuration/domain_names.rst:307 +msgid "If both addresses are already indexed, it may take some time before the indexation of the second address is removed from Google Search. You can use the `Google Search Console `_ to fix the issue." +msgstr "" + +#: ../../content/applications/websites/website/configuration/domain_names.rst:312 +msgid "If you have multiple websites and companies on your database, make sure to select the right :guilabel:`Company` under :menuselection:`Website --> Configuration --> Settings`. Doing so indicates Odoo which URL to use as the :ref:`base URL ` according to the company in use." +msgstr "" + +#: ../../content/applications/websites/website/configuration/google_search_console.rst:3 +msgid "Google Search Console" +msgstr "" + +#: ../../content/applications/websites/website/configuration/google_search_console.rst:5 +msgid "Google Search Console is a free web service provided by Google that allows website owners to monitor, maintain, and troubleshoot their site's presence in Google Search results. It offers valuable insights into how Google views and interacts with your site, helping you optimize its performance." +msgstr "" + +#: ../../content/applications/websites/website/configuration/google_search_console.rst:10 +msgid "To enable GSC, go to `Google Search Console `_, enter your domain or URL prefix, follow the instructions, and copy the code from Google." +msgstr "" + +#: ../../content/applications/websites/website/configuration/google_search_console.rst:-1 +msgid "Google Search Console domain or URL prefix" +msgstr "" + +#: ../../content/applications/websites/website/configuration/google_search_console.rst:-1 +msgid "Verify domain or URL prefix" +msgstr "" + +#: ../../content/applications/websites/website/configuration/google_search_console.rst:19 +msgid "Then, access your Odoo database, go to :menuselection:`Website --> Configuration --> Settings`, and enable :guilabel:`Google Search Console` in the :guilabel:`SEO` section. Paste the code in the dedicated field." +msgstr "" + +#: ../../content/applications/websites/website/configuration/google_search_console.rst:-1 +msgid "Website Settings pasting GSC code" +msgstr "" + +#: ../../content/applications/websites/website/configuration/google_search_console.rst:27 +msgid "To prevent Google from indexing both your custom domain name `www.example.com` and your original Odoo database URL `www.example.odoo.com`, :ref:`map your domain name with your Odoo website `." +msgstr "" + +#: ../../content/applications/websites/website/configuration/google_search_console.rst:32 +msgid ":doc:`domain_names`" +msgstr "" + #: ../../content/applications/websites/website/configuration/multi_website.rst:3 msgid "Multiple websites" msgstr "" @@ -4200,7 +4711,7 @@ msgid "Odoo allows you to create multiple websites from the same database. This msgstr "" #: ../../content/applications/websites/website/configuration/multi_website.rst:11 -msgid "Each website can be designed and configured independently with its own :doc:`domain name `, theme, pages, menus, :doc:`languages `, :doc:`products <../../ecommerce/managing_products/products>`, assigned sales team, etc. They can also :ref:`share content and pages `." +msgid "Each website can be designed and configured independently with its own :doc:`domain name `, theme, pages, menus, :doc:`languages `, :doc:`products <../../ecommerce/managing_products/products>`, assigned sales team, etc. They can also :ref:`share content and pages `." msgstr "" #: ../../content/applications/websites/website/configuration/multi_website.rst:18 @@ -4229,7 +4740,7 @@ msgid "New website button" msgstr "" #: ../../content/applications/websites/website/configuration/multi_website.rst:32 -msgid "Specify the :guilabel:`Website Name` and :guilabel:`Website domain`. Each website must be published under its own :doc:`domain `." +msgid "Specify the :guilabel:`Website Name` and :guilabel:`Website domain`. Each website must be published under its own :doc:`domain `." msgstr "" #: ../../content/applications/websites/website/configuration/multi_website.rst:34 @@ -4281,7 +4792,7 @@ msgid "Websites are created with the default settings; the settings are not copi msgstr "" #: ../../content/applications/websites/website/configuration/multi_website.rst:75 -msgid "In a :doc:`multi-company environment <../../../general/users/companies>`, each website can be linked to a specific company in your database so that only company-related data (e.g., products, jobs, events, etc.) is displayed on the website. To display company-specific data, set the desired company in the :guilabel:`Company` field." +msgid "In a :doc:`multi-company environment `, each website can be linked to a specific company in your database so that only company-related data (e.g., products, jobs, events, etc.) is displayed on the website. To display company-specific data, set the desired company in the :guilabel:`Company` field." msgstr "" #: ../../content/applications/websites/website/configuration/multi_website.rst:83 @@ -4382,7 +4893,7 @@ msgid "Reporting" msgstr "" #: ../../content/applications/websites/website/configuration/multi_website.rst:155 -msgid "Each website has its own :ref:`analytics `. To switch between websites, click the buttons in the upper right corner." +msgid "Each website has its own :ref:`analytics `. To switch between websites, click the buttons in the upper right corner." msgstr "" #: ../../content/applications/websites/website/configuration/multi_website.rst:-1 @@ -4737,46 +5248,6 @@ msgstr "" msgid "Add a language selector menu." msgstr "" -#: ../../content/applications/websites/website/configuration/unsplash.rst:3 -msgid "Unsplash" -msgstr "" - -#: ../../content/applications/websites/website/configuration/unsplash.rst:5 -msgid "**Unsplash** is a recognized stock photography library integrated with Odoo." -msgstr "" - -#: ../../content/applications/websites/website/configuration/unsplash.rst:7 -msgid "If your database is hosted on **Odoo Online**, you can access Unsplash pictures without configuration." -msgstr "" - -#: ../../content/applications/websites/website/configuration/unsplash.rst:10 -msgid "If your database is hosted on **Odoo.sh or on-premise**, proceed as follows:" -msgstr "" - -#: ../../content/applications/websites/website/configuration/unsplash.rst:12 -msgid "To **generate an Unsplash access key**, create or sign in to an `Unsplash account `_." -msgstr "" - -#: ../../content/applications/websites/website/configuration/unsplash.rst:15 -msgid "Access your `applications dashboard `_, click :guilabel:`New Application`, select all checkboxes, and click :guilabel:`Accept terms`." -msgstr "" - -#: ../../content/applications/websites/website/configuration/unsplash.rst:18 -msgid "In the pop-up window, enter your :guilabel:`Application Name`, starting with the prefix `Odoo:` (e.g., `Odoo: connection`), so Unsplash recognizes it as an Odoo instance. Then, add a :guilabel:`Description` and click :guilabel:`Create application`." -msgstr "" - -#: ../../content/applications/websites/website/configuration/unsplash.rst:22 -msgid "On the application details page, scroll down to the :guilabel:`Keys` section and copy the :guilabel:`Access Key` and :guilabel:`Application ID`." -msgstr "" - -#: ../../content/applications/websites/website/configuration/unsplash.rst:25 -msgid "In Odoo, go to :menuselection:`General Settings` and enable the :guilabel:`Unsplash Image Library` feature. Then, enter the Unsplash :guilabel:`Access Key` and :guilabel:`Application ID`." -msgstr "" - -#: ../../content/applications/websites/website/configuration/unsplash.rst:29 -msgid "As a non-Odoo Online user, you are limited to a test key with a maximum of 50 Unsplash requests per hour." -msgstr "" - #: ../../content/applications/websites/website/mail_groups.rst:3 msgid "Mail groups" msgstr "" @@ -5130,7 +5601,7 @@ msgid "URL redirects" msgstr "" #: ../../content/applications/websites/website/pages.rst:140 -msgid "Redirecting URLs consists in sending visitors and search engines to a URL that is different from the one they originally requested. This technique is used, for example, to prevent broken links when you :ref:`delete a page `, :ref:`modify its URL `, or move your site to a new :doc:`domain `. It can also be used to improve :doc:`pages/seo`." +msgid "Redirecting URLs consists in sending visitors and search engines to a URL that is different from the one they originally requested. This technique is used, for example, to prevent broken links when you :ref:`delete a page `, :ref:`modify its URL `, or move your site to a new :doc:`domain `. It can also be used to improve :doc:`pages/seo`." msgstr "" #: ../../content/applications/websites/website/pages.rst:146 @@ -5530,7 +6001,7 @@ msgid "Website analytics helps website owners monitor how people use their site. msgstr "" #: ../../content/applications/websites/website/reporting/analytics.rst:8 -msgid "You can track your Odoo website's traffic using :ref:`website/analytics/plausible` or :ref:`website/analytics/GA`. We recommend using Plausible.io as it is privacy-friendly, lightweight, and easy to use." +msgid "You can track your Odoo website's traffic using :ref:`analytics/plausible` or :ref:`analytics/google-analytics`. We recommend using Plausible.io as it is privacy-friendly, lightweight, and easy to use." msgstr "" #: ../../content/applications/websites/website/reporting/analytics.rst:12 @@ -5658,6 +6129,7 @@ msgstr "" msgid "If you already have a Google Analytics account, sign in and click the gear icon in the bottom-left corner of the page to access the **Admin** page. Then, click :guilabel:`+ Create Property`." msgstr "" +#: ../../content/applications/websites/website/reporting/analytics.rst:0 #: ../../content/applications/websites/website/reporting/analytics.rst:0 msgid "Measurement ID in Google Analytics." msgstr "" @@ -5803,7 +6275,7 @@ msgid "Activate the developer mode (:menuselection:`Settings --> Activate the de msgstr "" #: ../../content/applications/websites/website/reporting/link_tracker.rst:53 -msgid "Integrated with :ref:`website/analytics/GA`, those trackers allow you to see the number of clicks and visitors to keep you on top of your marketing campaigns." +msgid "Integrated with :ref:`analytics/google-analytics`, those trackers allow you to see the number of clicks and visitors to keep you on top of your marketing campaigns." msgstr "" #: ../../content/applications/websites/website/reporting/link_tracker.rst:55 @@ -5814,59 +6286,59 @@ msgstr "" msgid "Web design" msgstr "" -#: ../../content/applications/websites/website/web_design/building_blocks.rst:3 +#: ../../content/applications/websites/website/web_design/building_blocks.rst:5 msgid "Building blocks" msgstr "" -#: ../../content/applications/websites/website/web_design/building_blocks.rst:5 +#: ../../content/applications/websites/website/web_design/building_blocks.rst:7 msgid "Building blocks let you design your website quickly by dragging and dropping them onto your web pages. Four types of building blocks are available depending on their use: :guilabel:`Structure`, :guilabel:`Features`, :guilabel:`Dynamic Content`, and :guilabel:`Inner Content`." msgstr "" -#: ../../content/applications/websites/website/web_design/building_blocks.rst:10 +#: ../../content/applications/websites/website/web_design/building_blocks.rst:12 msgid "`Odoo Tutorial: Design your first webpage `_" msgstr "" -#: ../../content/applications/websites/website/web_design/building_blocks.rst:13 +#: ../../content/applications/websites/website/web_design/building_blocks.rst:15 msgid "Adding a building block" msgstr "" -#: ../../content/applications/websites/website/web_design/building_blocks.rst:15 +#: ../../content/applications/websites/website/web_design/building_blocks.rst:17 msgid "To add a building block to your website page, click :guilabel:`Edit`, select the desired building block, and drag and drop it to your page. You can add as many blocks as needed." msgstr "" -#: ../../content/applications/websites/website/web_design/building_blocks.rst:18 +#: ../../content/applications/websites/website/web_design/building_blocks.rst:20 msgid "To edit the content of a building block, click on it and go to the :guilabel:`Customize` tab, where available features depend on the block you selected." msgstr "" -#: ../../content/applications/websites/website/web_design/building_blocks.rst:22 +#: ../../content/applications/websites/website/web_design/building_blocks.rst:24 msgid "Color preset and background" msgstr "" -#: ../../content/applications/websites/website/web_design/building_blocks.rst:24 +#: ../../content/applications/websites/website/web_design/building_blocks.rst:26 msgid "You can customize and apply color presets to building blocks. To proceed, select a building block, go to the :guilabel:`Customize` tab, click the :guilabel:`Background` button, and select a :guilabel:`Preset`." msgstr "" -#: ../../content/applications/websites/website/web_design/building_blocks.rst:28 +#: ../../content/applications/websites/website/web_design/building_blocks.rst:30 msgid "When you modify a color preset, all elements using it are automatically updated to match the new configuration." msgstr "" -#: ../../content/applications/websites/website/web_design/building_blocks.rst:32 +#: ../../content/applications/websites/website/web_design/building_blocks.rst:34 msgid ":doc:`Website themes `" msgstr "" -#: ../../content/applications/websites/website/web_design/building_blocks.rst:35 +#: ../../content/applications/websites/website/web_design/building_blocks.rst:37 msgid "Layout: grid and columns" msgstr "" -#: ../../content/applications/websites/website/web_design/building_blocks.rst:37 +#: ../../content/applications/websites/website/web_design/building_blocks.rst:39 msgid "You can choose between two layout styles for most building blocks: grid or columns (cols). To change the default layout, go to the :guilabel:`Customize` tab. Under the :guilabel:`Banner` section, select :guilabel:`Grid` or :guilabel:`Cols` as the :guilabel:`Layout`." msgstr "" -#: ../../content/applications/websites/website/web_design/building_blocks.rst:42 +#: ../../content/applications/websites/website/web_design/building_blocks.rst:44 msgid "Grid" msgstr "" -#: ../../content/applications/websites/website/web_design/building_blocks.rst:44 +#: ../../content/applications/websites/website/web_design/building_blocks.rst:46 msgid "The :guilabel:`Grid` layout allows you to reposition and resize elements, such as images or text, by dragging and dropping them." msgstr "" @@ -5874,7 +6346,7 @@ msgstr "" msgid "When the grid layout is selected, choose an image and drag and drop it where needed." msgstr "" -#: ../../content/applications/websites/website/web_design/building_blocks.rst:51 +#: ../../content/applications/websites/website/web_design/building_blocks.rst:53 msgid "Position images behind the text by using the above/below icons." msgstr "" @@ -5882,11 +6354,11 @@ msgstr "" msgid "Positioning an image behind text" msgstr "" -#: ../../content/applications/websites/website/web_design/building_blocks.rst:57 +#: ../../content/applications/websites/website/web_design/building_blocks.rst:59 msgid "Cols" msgstr "" -#: ../../content/applications/websites/website/web_design/building_blocks.rst:59 +#: ../../content/applications/websites/website/web_design/building_blocks.rst:61 msgid "Choosing the :guilabel:`Cols` layout allows you to determine the number of elements per line within the block." msgstr "" @@ -5894,28 +6366,28 @@ msgstr "" msgid "Setting the number columns" msgstr "" -#: ../../content/applications/websites/website/web_design/building_blocks.rst:66 +#: ../../content/applications/websites/website/web_design/building_blocks.rst:68 msgid "On mobile devices, only one element per column is used by default for better visibility. You can adjust this value by using the :guilabel:`Mobile Preview` mode." msgstr "" +#: ../../content/applications/websites/website/web_design/building_blocks.rst:72 #: ../../content/applications/websites/website/web_design/building_blocks.rst:-1 -#: ../../content/applications/websites/website/web_design/building_blocks.rst:70 msgid "Duplicating a building block" msgstr "" -#: ../../content/applications/websites/website/web_design/building_blocks.rst:72 +#: ../../content/applications/websites/website/web_design/building_blocks.rst:74 msgid "You can duplicate a building block by clicking on the duplicate icon. Once duplicated, the new block appears on your website beneath the original one." msgstr "" -#: ../../content/applications/websites/website/web_design/building_blocks.rst:79 +#: ../../content/applications/websites/website/web_design/building_blocks.rst:81 msgid "Reordering a building block" msgstr "" -#: ../../content/applications/websites/website/web_design/building_blocks.rst:81 +#: ../../content/applications/websites/website/web_design/building_blocks.rst:83 msgid "To reorder a building block, select it and click the up arrow to move it before the previous block or click the down arrow to move it after." msgstr "" -#: ../../content/applications/websites/website/web_design/building_blocks.rst:84 +#: ../../content/applications/websites/website/web_design/building_blocks.rst:86 msgid "You can also use the drag-and-drop icon to move a block manually." msgstr "" @@ -5923,15 +6395,15 @@ msgstr "" msgid "Reordering building blocks" msgstr "" -#: ../../content/applications/websites/website/web_design/building_blocks.rst:90 +#: ../../content/applications/websites/website/web_design/building_blocks.rst:92 msgid "Visibility" msgstr "" -#: ../../content/applications/websites/website/web_design/building_blocks.rst:93 +#: ../../content/applications/websites/website/web_design/building_blocks.rst:95 msgid "Visibility on desktop/mobile" msgstr "" -#: ../../content/applications/websites/website/web_design/building_blocks.rst:95 +#: ../../content/applications/websites/website/web_design/building_blocks.rst:97 msgid "You can hide specific elements depending on the visitor's device. To do so, select the element to hide, and in the :guilabel:`Customize` tab, scroll down to :guilabel:`Visibility`, and click the :guilabel:`Show/Hide on Mobile` or the :guilabel:`Show/Hide on Desktop` icon." msgstr "" @@ -5939,7 +6411,7 @@ msgstr "" msgid "Click the \"show/hide on mobile\" icons to show or hide some elements on mobile." msgstr "" -#: ../../content/applications/websites/website/web_design/building_blocks.rst:103 +#: ../../content/applications/websites/website/web_design/building_blocks.rst:105 msgid "Click the phone icon at the top of the configurator to preview how your website would look on a mobile device." msgstr "" @@ -5947,31 +6419,31 @@ msgstr "" msgid "Mobile phone preview icon" msgstr "" -#: ../../content/applications/websites/website/web_design/building_blocks.rst:110 +#: ../../content/applications/websites/website/web_design/building_blocks.rst:112 msgid "Conditional visibility" msgstr "" -#: ../../content/applications/websites/website/web_design/building_blocks.rst:112 +#: ../../content/applications/websites/website/web_design/building_blocks.rst:114 msgid "You can also hide or show building blocks using other conditions. To do so, select an element, go to :guilabel:`Visibility`, click :guilabel:`No condition`, and select :guilabel:`Conditionally` instead. Then, configure the condition(s) to apply by selecting :guilabel:`Visible for` or :guilabel:`Hidden for` and which :guilabel:`Records` will be impacted." msgstr "" -#: ../../content/applications/websites/website/web_design/building_blocks.rst:118 +#: ../../content/applications/websites/website/web_design/building_blocks.rst:120 msgid ":doc:`Link Tracker and UTMs <../reporting/link_tracker>`" msgstr "" -#: ../../content/applications/websites/website/web_design/building_blocks.rst:121 +#: ../../content/applications/websites/website/web_design/building_blocks.rst:123 msgid "Invisible elements" msgstr "" -#: ../../content/applications/websites/website/web_design/building_blocks.rst:123 +#: ../../content/applications/websites/website/web_design/building_blocks.rst:125 msgid "Depending on the visibility settings, some elements can become hidden from your current view. To make a building block visible again, go to the :guilabel:`Invisible Elements` section at the bottom of the configurator and select a building block." msgstr "" -#: ../../content/applications/websites/website/web_design/building_blocks.rst:128 +#: ../../content/applications/websites/website/web_design/building_blocks.rst:130 msgid "Saving a custom building block" msgstr "" -#: ../../content/applications/websites/website/web_design/building_blocks.rst:130 +#: ../../content/applications/websites/website/web_design/building_blocks.rst:132 msgid "You can save a customized building block and reuse it elsewhere. To do so, select it, navigate to the :guilabel:`Customize` tab, and click the floppy disk icon to save it." msgstr "" @@ -5979,7 +6451,7 @@ msgstr "" msgid "Saving a building block" msgstr "" -#: ../../content/applications/websites/website/web_design/building_blocks.rst:136 +#: ../../content/applications/websites/website/web_design/building_blocks.rst:138 msgid "Saved building blocks are available in the :guilabel:`Custom` section of the :guilabel:`Blocks` tab. Click the pen icon to edit their name." msgstr "" @@ -5987,6 +6459,78 @@ msgstr "" msgid "Custom section with saved building blocks" msgstr "" +#: ../../content/applications/websites/website/web_design/building_blocks/structure.rst:3 +msgid "Structure blocks" +msgstr "" + +#: ../../content/applications/websites/website/web_design/building_blocks/structure.rst:5 +msgid "The website configurator provides a range of :guilabel:`Structure` :doc:`building blocks <../building_blocks>` to design your website's layout, including headings, images, and text." +msgstr "" + +#: ../../content/applications/websites/website/web_design/building_blocks/structure.rst:8 +msgid "To add a block to a web page, click :guilabel:`Edit`, select a block from the :guilabel:`Structure` section, and drag and drop it into the page." +msgstr "" + +#: ../../content/applications/websites/website/web_design/building_blocks/structure.rst:-1 +msgid "Dragging and dropping a building block into a page" +msgstr "" + +#: ../../content/applications/websites/website/web_design/building_blocks/structure.rst:14 +msgid "Below are presented two types of structure blocks: :ref:`Banner ` and :ref:`Masonry `." +msgstr "" + +#: ../../content/applications/websites/website/web_design/building_blocks/structure.rst:20 +msgid "Banner block" +msgstr "" + +#: ../../content/applications/websites/website/web_design/building_blocks/structure.rst:22 +msgid "The :guilabel:`Banner` block combines a title, text, images, and a call to action button, making it suitable for placement at the top of a website." +msgstr "" + +#: ../../content/applications/websites/website/web_design/building_blocks/structure.rst:-1 +msgid "The default banner block" +msgstr "" + +#: ../../content/applications/websites/website/web_design/building_blocks/structure.rst:29 +msgid "Call to action" +msgstr "" + +#: ../../content/applications/websites/website/web_design/building_blocks/structure.rst:31 +msgid "The call to action button encourages visitors to take a specific action, for example, consulting your shop, downloading a file, or making an appointment." +msgstr "" + +#: ../../content/applications/websites/website/web_design/building_blocks/structure.rst:-1 +msgid "Selecting the call to action button" +msgstr "" + +#: ../../content/applications/websites/website/web_design/building_blocks/structure.rst:37 +msgid "To change the button's link, select it and click the :guilabel:`Edit Link` icon. Additional customization options are available in the :guilabel:`Inline Text` section." +msgstr "" + +#: ../../content/applications/websites/website/web_design/building_blocks/structure.rst:-1 +msgid "Configuring the call to action button" +msgstr "" + +#: ../../content/applications/websites/website/web_design/building_blocks/structure.rst:46 +msgid "Masonry block" +msgstr "" + +#: ../../content/applications/websites/website/web_design/building_blocks/structure.rst:48 +msgid "The :guilabel:`Masonry` building block offers a range of templates that associate image and text bricks. To change the default template, go to the :guilabel:`Customize` tab, click :guilabel:`Template` and select one." +msgstr "" + +#: ../../content/applications/websites/website/web_design/building_blocks/structure.rst:-1 +msgid "Selecting a masonry building block template" +msgstr "" + +#: ../../content/applications/websites/website/web_design/building_blocks/structure.rst:56 +msgid "The :guilabel:`Masonry` building block allows you to add text on top of images. To do so, go to the :guilabel:`Customize` tab, scroll to :guilabel:`Add Elements`, and click :guilabel:`Text`." +msgstr "" + +#: ../../content/applications/websites/website/web_design/building_blocks/structure.rst:0 +msgid "Adding text on top of an image" +msgstr "" + #: ../../content/applications/websites/website/web_design/themes.rst:3 msgid "Website themes" msgstr "" @@ -6056,7 +6600,7 @@ msgid ":guilabel:`Input Fields`: Customize fields where you can enter data, e.g. msgstr "" #: ../../content/applications/websites/website/web_design/themes.rst:62 -msgid ":guilabel:`Advanced`: You can hide the header bar of your website using the :guilabel:`Show Header` button, inject :ref:`head and body code `, enter your :guilabel:`Google Map Custom Key`, change the colors of the :guilabel:`Success`, :guilabel:`Info`, :guilabel:`Warning`, and :guilabel:`Error` pop up messages by clicking the related :guilabel:`Status Colors` buttons, and customize the :guilabel:`Grays` elements of your site." +msgid ":guilabel:`Advanced`: You can hide the header bar of your website using the :guilabel:`Show Header` button, inject :ref:`head and body code `, enter your :guilabel:`Google Map Custom Key`, change the colors of the :guilabel:`Success`, :guilabel:`Info`, :guilabel:`Warning`, and :guilabel:`Error` pop up messages by clicking the related :guilabel:`Status Colors` buttons, and customize the :guilabel:`Grays` elements of your site." msgstr "" #: ../../content/applications/websites/website/web_design/themes.rst:70