diff --git a/.tx/config b/.tx/config index 6e85625ec..b1fb481e2 100644 --- a/.tx/config +++ b/.tx/config @@ -11,6 +11,11 @@ file_filter = locale//LC_MESSAGES/applications.po source_file = locale/sources/applications.pot source_lang = en +[o:odoo:p:odoo-15-doc:r:essentials] +file_filter = locale//LC_MESSAGES/essentials.po +source_file = locale/sources/essentials.pot +source_lang = en + [o:odoo:p:odoo-15-doc:r:finance] file_filter = locale//LC_MESSAGES/finance.po source_file = locale/sources/finance.pot @@ -21,6 +26,11 @@ file_filter = locale//LC_MESSAGES/general.po source_file = locale/sources/general.pot source_lang = en +[o:odoo:p:odoo-15-doc:r:hr] +file_filter = locale//LC_MESSAGES/hr.po +source_file = locale/sources/hr.pot +source_lang = en + [o:odoo:p:odoo-15-doc:r:index] file_filter = locale//LC_MESSAGES/index.po source_file = locale/sources/index.pot @@ -61,6 +71,11 @@ file_filter = locale//LC_MESSAGES/settings.po source_file = locale/sources/settings.pot source_lang = en +[o:odoo:p:odoo-15-doc:r:studio] +file_filter = locale//LC_MESSAGES/studio.po +source_file = locale/sources/studio.pot +source_lang = en + [o:odoo:p:odoo-15-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 7e1dd8bc9..350e0a301 100644 --- a/locale/sources/administration.pot +++ b/locale/sources/administration.pot @@ -8,7 +8,7 @@ msgid "" msgstr "" "Project-Id-Version: Odoo 15.0\n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2024-03-05 13:22+0000\n" +"POT-Creation-Date: 2024-03-20 10:19+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,2922 +26,380 @@ 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:189 -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/9.5/main/pg_hba.conf`` set:" -msgstr "" - -#: ../../content/administration/install/deploy.rst:108 -msgid "in ``/etc/postgresql/9.5/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-running requests such as long polling. 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:373 -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:`--longpolling-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 ``/longpolling`` 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:347 -msgid "Odoo as a WSGI Application" -msgstr "" - -#: ../../content/administration/install/deploy.rst:349 -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:355 -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:360 -msgid "Cron Workers" -msgstr "" - -#: ../../content/administration/install/deploy.rst:362 -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:367 -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:375 -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 HTTP requests but doesn't need a lot of processing power. All requests whose path starts with ``/longpolling`` 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:381 -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 ``/longpolling`` are directed to this server, either on the :option:`--http-port ` (multi-threading server) or on the :option:`--longpolling-port ` (multi-processing server)." -msgstr "" - -#: ../../content/administration/install/deploy.rst:388 -msgid "Serving Static Files" -msgstr "" - -#: ../../content/administration/install/deploy.rst:390 -msgid "For development convenience, Odoo directly serves all static files 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:394 -msgid "Odoo static files live in each module's ``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:398 -msgid "Todo" -msgstr "" - -#: ../../content/administration/install/deploy.rst:398 -msgid "test whether it would be interesting to serve filestored attachments via this, and how (e.g. possibility of mapping ir.attachment id to filestore hash in the database?)" -msgstr "" - -#: ../../content/administration/install/deploy.rst:405 -msgid "Security" -msgstr "" - -#: ../../content/administration/install/deploy.rst:407 -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:411 -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:417 -msgid "When deploying an internet-facing server, please be sure to consider the following security-related topics:" -msgstr "" - -#: ../../content/administration/install/deploy.rst:420 -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:423 -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:428 -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:432 -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:439 -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:445 -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:450 -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:454 -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:457 -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:464 -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:470 -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:474 -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:478 -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:482 -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:493 -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:504 -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:507 -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:510 -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:518 -msgid "Blocking Brute Force Attacks" -msgstr "" - -#: ../../content/administration/install/deploy.rst:520 -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:524 -msgid "The log entries will have the following form." -msgstr "" - -#: ../../content/administration/install/deploy.rst:526 -msgid "Failed login::" -msgstr "" - -#: ../../content/administration/install/deploy.rst:530 -msgid "Successful login::" -msgstr "" - -#: ../../content/administration/install/deploy.rst:535 -msgid "These logs can be easily analyzed by an intrusion prevention system such as `fail2ban`." -msgstr "" - -#: ../../content/administration/install/deploy.rst:537 -msgid "For example, the following fail2ban filter definition should match a failed login::" -msgstr "" - -#: ../../content/administration/install/deploy.rst:544 -msgid "This could be used with a jail definition to block the attacking IP on HTTP(S)." -msgstr "" - -#: ../../content/administration/install/deploy.rst:546 -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:560 -msgid "Database Manager Security" -msgstr "" - -#: ../../content/administration/install/deploy.rst:562 -msgid ":ref:`setup/deploy/odoo` mentioned ``admin_passwd`` in passing." -msgstr "" - -#: ../../content/administration/install/deploy.rst:564 -msgid "This setting is used on all database management screens (to create, delete, dump or restore databases)." -msgstr "" - -#: ../../content/administration/install/deploy.rst:567 -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:573 -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:579 -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:582 -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:587 -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:591 -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:595 -msgid "It should be stored securely, and should be generated randomly e.g." -msgstr "" - -#: ../../content/administration/install/deploy.rst:601 -msgid "which will generate a 32 characters pseudorandom printable string." -msgstr "" - -#: ../../content/administration/install/deploy.rst:604 -msgid "Supported Browsers" -msgstr "" - -#: ../../content/administration/install/deploy.rst:606 -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:609 -msgid "Here are the supported browsers:" -msgstr "" - -#: ../../content/administration/install/deploy.rst:611 -msgid "Google Chrome" -msgstr "" - -#: ../../content/administration/install/deploy.rst:612 -msgid "Mozilla Firefox" -msgstr "" - -#: ../../content/administration/install/deploy.rst:613 -msgid "Microsoft Edge" -msgstr "" - -#: ../../content/administration/install/deploy.rst:614 -msgid "Apple Safari" -msgstr "" - -#: ../../content/administration/install/deploy.rst:616 -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:621 -msgid "Since Odoo 13.0, ES6 is supported. Therefore, IE support is dropped." -msgstr "" - -#: ../../content/administration/install/deploy.rst:624 -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:627 -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:631 -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:12 -msgid "Please note that the installation depends on your computer's operating system and distribution. We will assume that a Linux operating system is being used." +#: ../../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:18 -msgid "Install `geoip2 `__ Python library" +#: ../../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:20 -msgid "Download the `GeoLite2 City database `_. You should end up with a file called ``GeoLite2-City.mmdb``" +#: ../../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 "Move the file to the folder ``/usr/share/GeoIP/``" +#: ../../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:27 -msgid "Restart the server" +#: ../../content/administration.rst:31 +msgid "A `Docker `_ base image is available for development or deployment." msgstr "" -#: ../../content/administration/install/geo_ip.rst:30 -msgid "If you can't/don't want to locate the geoip database in ``/usr/share/GeoIP/``, you can use the ``--geoip-db`` option of the Odoo command line interface. This option takes the absolute path to the GeoIP database file and uses it as the GeoIP database. For example:" +#: ../../content/administration.rst:37 +msgid "Editions" msgstr "" -#: ../../content/administration/install/geo_ip.rst:39 -msgid ":doc:`CLI documentation `." +#: ../../content/administration.rst:39 +msgid "There are two different editions." msgstr "" -#: ../../content/administration/install/geo_ip.rst:42 -msgid "``GeoIP`` Python library can also be used. However this version is discontinued since January 1. See `GeoLite Legacy databases are now discontinued `_" +#: ../../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:47 -msgid "How to test GeoIP geolocation in your Odoo website" +#: ../../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:49 -msgid "Go to your website. Open the web page that you want to test ``GeoIP``." +#: ../../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:50 -msgid "Choose :menuselection:`Customize --> HTML/CSS/JS Editor`." +#: ../../content/administration/hosting.rst:3 +msgid "Hosting" msgstr "" -#: ../../content/administration/install/geo_ip.rst:51 -msgid "Add the following piece of XML in the page :" +#: ../../content/administration/hosting.rst:8 +msgid "Change hosting solution" msgstr "" -#: ../../content/administration/install/geo_ip.rst:57 -msgid "You should end up with a dictionary indicating the location of the IP address." +#: ../../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:63 -msgid "If the curly braces are empty ``{}``, it can be for any of the following reasons :" +#: ../../content/administration/hosting.rst:14 +msgid "Transferring an on-premise database" msgstr "" -#: ../../content/administration/install/geo_ip.rst:65 -msgid "The browsing IP address is the localhost (``127.0.0.1``) or a local area network one (``192.168.*.*``)" +#: ../../content/administration/hosting.rst:17 +#: ../../content/administration/hosting.rst:85 +msgid "To Odoo Online" msgstr "" -#: ../../content/administration/install/geo_ip.rst:67 -msgid "If a reversed proxy is used, make sure to configure it correctly. See :option:`proxy mode `" +#: ../../content/administration/hosting.rst:20 +#: ../../content/administration/hosting.rst:88 +msgid "Odoo Online is *not* compatible with **non-standard apps**." msgstr "" -#: ../../content/administration/install/geo_ip.rst:69 -msgid "``geoip2`` is not installed or the GeoIP database file wasn't found" +#: ../../content/administration/hosting.rst:21 +msgid "The database's current version must be :doc:`supported `." msgstr "" -#: ../../content/administration/install/geo_ip.rst:70 -msgid "The GeoIP database was unable to resolve the given IP address" +#: ../../content/administration/hosting.rst:23 +msgid "Create a :ref:`duplicate of the database `." msgstr "" -#: ../../content/administration/install/online.rst:3 -msgid "Online" +#: ../../content/administration/hosting.rst:24 +msgid "In this duplicate, uninstall all **non-standard apps**." 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:25 +msgid "Use the database manager to grab a *dump with filestore*." msgstr "" -#: ../../content/administration/install/online.rst:8 -msgid "Demo" +#: ../../content/administration/hosting.rst:26 +msgid "`Submit a support ticket `_ including the following:" 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:28 +#: ../../content/administration/hosting.rst:93 +msgid "your **subscription number**," 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: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:100 +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:104 +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:72 +msgid "To Odoo.sh" +msgstr "" + +#: ../../content/administration/hosting.rst:42 +#: ../../content/administration/hosting.rst:78 +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 +#: ../../content/administration/hosting.rst:113 +msgid "To on-premise" +msgstr "" + +#: ../../content/administration/hosting.rst:65 +#: ../../content/administration/hosting.rst:74 +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:69 +#: ../../content/administration/hosting.rst:116 +msgid "Restore the database from the database manager on your local server using the backup." +msgstr "" + +#: ../../content/administration/hosting.rst:82 +msgid "Transferring an Odoo.sh database" +msgstr "" + +#: ../../content/administration/hosting.rst:90 +msgid "Uninstall all **non-standard apps** in a staging build before doing it in the production build." +msgstr "" + +#: ../../content/administration/hosting.rst:91 +msgid "`Create a support ticket `_ including the following:" +msgstr "" + +#: ../../content/administration/hosting.rst:94 +msgid "the **URL** you want to use for the database (e.g., `company.odoo.com`)," +msgstr "" + +#: ../../content/administration/hosting.rst:95 +msgid "which **branch** should be migrated," +msgstr "" + +#: ../../content/administration/hosting.rst:96 +msgid "in which **region** you want the database to be hosted (Americas, Europe, or Asia)," +msgstr "" + +#: ../../content/administration/hosting.rst:97 +msgid "which user(s) will be the **administrator(s)**, and" +msgstr "" + +#: ../../content/administration/hosting.rst:98 +msgid "**when** (and in which timezone) you want the database to be up and running." +msgstr "" + +#: ../../content/administration/hosting.rst:106 +msgid "Select the **region** closest to most of your users to reduce latency." +msgstr "" + +#: ../../content/administration/hosting.rst:107 +msgid "Future **administrator(s)** must have an Odoo.com account." +msgstr "" + +#: ../../content/administration/hosting.rst:108 +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:110 +msgid "Databases are **not reachable** during their migration." +msgstr "" + +#: ../../content/administration/hosting.rst:115 +msgid "Download a :ref:`backup of your Odoo.sh production database `." +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:125 -#: ../../content/administration/install/source.rst:148 -#: ../../content/administration/install/source.rst:170 -#: ../../content/administration/install/source.rst:195 -#: ../../content/administration/install/source.rst:224 -#: ../../content/administration/install/source.rst:267 -#: ../../content/administration/install/source.rst:380 -#: ../../content/administration/install/source.rst:442 -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:274 -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:412 -msgid "`wkhtmltopdf` is not installed through **pip** and must be installed manually in `version 0.12.5 `_ 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 15 '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 15 '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:129 -#: ../../content/administration/install/source.rst:154 -#: ../../content/administration/install/source.rst:176 -#: ../../content/administration/install/source.rst:204 -#: ../../content/administration/install/source.rst:235 -#: ../../content/administration/install/source.rst:320 -#: ../../content/administration/install/source.rst:389 -#: ../../content/administration/install/source.rst:452 -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:137 -#: ../../content/administration/install/source.rst:160 -#: ../../content/administration/install/source.rst:182 -#: ../../content/administration/install/source.rst:209 -#: ../../content/administration/install/source.rst:249 -#: ../../content/administration/install/source.rst:343 -#: ../../content/administration/install/source.rst:401 -#: ../../content/administration/install/source.rst:463 -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.7** or later to run." -msgstr "" - -#: ../../content/administration/install/source.rst:127 -msgid "Use a package manager to download and install Python 3 if needed." -msgstr "" - -#: ../../content/administration/install/source.rst:131 -msgid "`Download the latest version of Python 3 `_ and install it." -msgstr "" - -#: ../../content/administration/install/source.rst:134 -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:139 -msgid "Use a package manager (`Homebrew `_, `MacPorts `_) to download and install Python 3 if needed." -msgstr "" - -#: ../../content/administration/install/source.rst:143 -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:166 -msgid "Verify that `pip `_ is also installed for this version." -msgstr "" - -#: ../../content/administration/install/source.rst:191 -msgid "Odoo uses PostgreSQL as its database management system." -msgstr "" - -#: ../../content/administration/install/source.rst:197 -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:206 -msgid "`Download PostgreSQL `_ (supported versions: 12.0 or above) and install it." -msgstr "" - -#: ../../content/administration/install/source.rst:211 -msgid "Use `Postgres.app `_ to download and install PostgreSQL (supported version: 12.0 or above)." -msgstr "" - -#: ../../content/administration/install/source.rst:215 -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:219 -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:232 -#: ../../content/administration/install/source.rst:257 -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:237 -msgid "Add PostgreSQL's `bin` directory (by default: :file:`C:\\\\Program Files\\\\PostgreSQL\\\\\\\\bin`) to the `PATH`." -msgstr "" - -#: ../../content/administration/install/source.rst:239 -msgid "Create a postgres user with a password using the pg admin gui:" -msgstr "" - -#: ../../content/administration/install/source.rst:241 -msgid "Open **pgAdmin**." -msgstr "" - -#: ../../content/administration/install/source.rst:242 -msgid "Double-click the server to create a connection." -msgstr "" - -#: ../../content/administration/install/source.rst:243 -msgid "Select :menuselection:`Object --> Create --> Login/Group Role`." -msgstr "" - -#: ../../content/administration/install/source.rst:244 -msgid "Enter the username in the **Role Name** field (e.g., `odoo`)." -msgstr "" - -#: ../../content/administration/install/source.rst:245 -msgid "Open the **Definition** tab, enter a password (e.g., `odoo`), and click **Save**." -msgstr "" - -#: ../../content/administration/install/source.rst:246 -msgid "Open the **Privileges** tab and switch **Can login?** to `Yes` and **Create database?** to `Yes`." -msgstr "" - -#: ../../content/administration/install/source.rst:263 -msgid "Dependencies" -msgstr "" - -#: ../../content/administration/install/source.rst:269 -msgid "Using **distribution packages** is the preferred way of installing dependencies. Alternatively, install the Python dependencies with **pip**." -msgstr "" - -#: ../../content/administration/install/source.rst:276 -msgid "For Debian-based systems, the packages are listed in the `debian/control `_ file of the Odoo sources." -msgstr "" - -#: ../../content/administration/install/source.rst:279 -msgid "On Debian/Ubuntu, the following commands should install the required packages:" -msgstr "" - -#: ../../content/administration/install/source.rst:286 -msgid "Install with pip" -msgstr "" - -#: ../../content/administration/install/source.rst:288 -msgid "As some of the Python packages need a compilation step, they require system libraries to be installed." -msgstr "" - -#: ../../content/administration/install/source.rst:291 -msgid "On Debian/Ubuntu, the following command should install these required libraries:" -msgstr "" - -#: ../../content/administration/install/source.rst:297 -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:301 -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:308 -#: ../../content/administration/install/source.rst:330 -#: ../../content/administration/install/source.rst:349 -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:312 -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:322 -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:326 -#: ../../content/administration/install/source.rst:345 -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:334 -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:353 -msgid "Navigate to the path of the Odoo Community installation (`CommunityPath`) and run **pip** on the requirements file:" -msgstr "" - -#: ../../content/administration/install/source.rst:363 -msgid "Non-Python dependencies must be installed with a package manager (`Homebrew `_, `MacPorts `_)." -msgstr "" - -#: ../../content/administration/install/source.rst:366 -msgid "Download and install the **Command Line Tools**:" -msgstr "" - -#: ../../content/administration/install/source.rst:372 -msgid "Use the package manager to install non-Python dependencies." -msgstr "" - -#: ../../content/administration/install/source.rst:375 -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:382 -msgid "Download and install **nodejs** and **npm** with a package manager." -msgstr "" - -#: ../../content/administration/install/source.rst:383 -#: ../../content/administration/install/source.rst:392 -#: ../../content/administration/install/source.rst:405 -msgid "Install `rtlcss`:" -msgstr "" - -#: ../../content/administration/install/source.rst:391 -msgid "Download and install `nodejs `_." -msgstr "" - -#: ../../content/administration/install/source.rst:398 -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:403 -msgid "Download and install **nodejs** with a package manager (`Homebrew `_, `MacPorts `_)." -msgstr "" - -#: ../../content/administration/install/source.rst:420 -msgid "Running Odoo" -msgstr "" - -#: ../../content/administration/install/source.rst:422 -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:425 -msgid "To configure the server, either specify :ref:`command-line arguments ` or a :ref:`configuration file `." -msgstr "" - -#: ../../content/administration/install/source.rst:429 -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:433 -msgid "Common necessary configurations are:" -msgstr "" - -#: ../../content/administration/install/source.rst:435 -msgid "PostgreSQL user and password." -msgstr "" - -#: ../../content/administration/install/source.rst:436 -msgid "Custom addon paths beyond the defaults to load custom modules." -msgstr "" - -#: ../../content/administration/install/source.rst:438 -msgid "A typical way to run the server would be:" -msgstr "" - -#: ../../content/administration/install/source.rst:449 -#: ../../content/administration/install/source.rst:470 -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:459 -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:473 -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:478 -msgid "From there, create and manage new :doc:`users <../../applications/general/users/manage_users>`." -msgstr "" - -#: ../../content/administration/install/source.rst:479 -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:483 -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`. Enable :guilabel:`Custom Email Servers` field, enter the :guilabel:`Alias Domain` (e.g., `subdomain.yourdomain.com`) and click :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/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 @@ -2948,722 +407,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 labelled 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 @@ -4601,6 +1482,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 "" @@ -4902,7 +1787,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 @@ -5018,7 +1903,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 @@ -5138,7 +2023,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 @@ -5736,6 +2621,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" @@ -5915,8 +2841,1853 @@ 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:150 +#: ../../content/administration/upgrade.rst:342 +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:189 +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/9.5/main/pg_hba.conf`` set:" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:108 +msgid "in ``/etc/postgresql/9.5/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-running requests such as long polling. 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:373 +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:`--longpolling-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 ``/longpolling`` 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:347 +msgid "Odoo as a WSGI Application" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:349 +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:355 +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:360 +msgid "Cron Workers" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:362 +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:367 +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:375 +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 HTTP requests but doesn't need a lot of processing power. All requests whose path starts with ``/longpolling`` 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:381 +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 ``/longpolling`` are directed to this server, either on the :option:`--http-port ` (multi-threading server) or on the :option:`--longpolling-port ` (multi-processing server)." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:388 +msgid "Serving Static Files" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:390 +msgid "For development convenience, Odoo directly serves all static files 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:394 +msgid "Odoo static files live in each module's ``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:398 +msgid "Todo" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:398 +msgid "test whether it would be interesting to serve filestored attachments via this, and how (e.g. possibility of mapping ir.attachment id to filestore hash in the database?)" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:405 +msgid "Security" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:407 +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:411 +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:417 +msgid "When deploying an internet-facing server, please be sure to consider the following security-related topics:" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:420 +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:423 +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:428 +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:432 +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:439 +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:445 +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:450 +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:454 +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:457 +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:464 +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:470 +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:474 +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:478 +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:482 +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:493 +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:504 +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:507 +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:510 +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:518 +msgid "Blocking Brute Force Attacks" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:520 +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:524 +msgid "The log entries will have the following form." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:526 +msgid "Failed login::" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:530 +msgid "Successful login::" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:535 +msgid "These logs can be easily analyzed by an intrusion prevention system such as `fail2ban`." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:537 +msgid "For example, the following fail2ban filter definition should match a failed login::" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:544 +msgid "This could be used with a jail definition to block the attacking IP on HTTP(S)." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:546 +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:560 +msgid "Database Manager Security" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:562 +msgid ":ref:`setup/deploy/odoo` mentioned ``admin_passwd`` in passing." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:564 +msgid "This setting is used on all database management screens (to create, delete, dump or restore databases)." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:567 +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:573 +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:579 +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:582 +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:587 +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:591 +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:595 +msgid "It should be stored securely, and should be generated randomly e.g." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:601 +msgid "which will generate a 32 characters pseudorandom printable string." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:604 +msgid "Supported Browsers" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:606 +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:609 +msgid "Here are the supported browsers:" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:611 +msgid "Google Chrome" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:612 +msgid "Mozilla Firefox" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:613 +msgid "Microsoft Edge" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:614 +msgid "Apple Safari" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:616 +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:621 +msgid "Since Odoo 13.0, ES6 is supported. Therefore, IE support is dropped." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:624 +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:627 +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:631 +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:12 +msgid "Please note that the installation depends on your computer's operating system and distribution. We will assume that a Linux operating system is being used." +msgstr "" + +#: ../../content/administration/on_premise/geo_ip.rst:18 +msgid "Install `geoip2 `__ Python library" +msgstr "" + +#: ../../content/administration/on_premise/geo_ip.rst:20 +msgid "Download the `GeoLite2 City database `_. You should end up with a file called ``GeoLite2-City.mmdb``" +msgstr "" + +#: ../../content/administration/on_premise/geo_ip.rst:25 +msgid "Move the file to the folder ``/usr/share/GeoIP/``" +msgstr "" + +#: ../../content/administration/on_premise/geo_ip.rst:27 +msgid "Restart the server" +msgstr "" + +#: ../../content/administration/on_premise/geo_ip.rst:30 +msgid "If you can't/don't want to locate the geoip database in ``/usr/share/GeoIP/``, you can use the ``--geoip-db`` option of the Odoo command line interface. This option takes the absolute path to the GeoIP database file and uses it as the GeoIP database. For example:" +msgstr "" + +#: ../../content/administration/on_premise/geo_ip.rst:39 +msgid ":doc:`CLI documentation `." +msgstr "" + +#: ../../content/administration/on_premise/geo_ip.rst:42 +msgid "``GeoIP`` Python library can also be used. However this version is discontinued since January 1. See `GeoLite Legacy databases are now discontinued `_" +msgstr "" + +#: ../../content/administration/on_premise/geo_ip.rst:47 +msgid "How to test GeoIP geolocation in your Odoo website" +msgstr "" + +#: ../../content/administration/on_premise/geo_ip.rst:49 +msgid "Go to your website. Open the web page that you want to test ``GeoIP``." +msgstr "" + +#: ../../content/administration/on_premise/geo_ip.rst:50 +msgid "Choose :menuselection:`Customize --> HTML/CSS/JS Editor`." +msgstr "" + +#: ../../content/administration/on_premise/geo_ip.rst:51 +msgid "Add the following piece of XML in the page :" +msgstr "" + +#: ../../content/administration/on_premise/geo_ip.rst:57 +msgid "You should end up with a dictionary indicating the location of the IP address." +msgstr "" + +#: ../../content/administration/on_premise/geo_ip.rst:63 +msgid "If the curly braces are empty ``{}``, it can be for any of the following reasons :" +msgstr "" + +#: ../../content/administration/on_premise/geo_ip.rst:65 +msgid "The browsing IP address is the localhost (``127.0.0.1``) or a local area network one (``192.168.*.*``)" +msgstr "" + +#: ../../content/administration/on_premise/geo_ip.rst:67 +msgid "If a reversed proxy is used, make sure to configure it correctly. See :option:`proxy mode `" +msgstr "" + +#: ../../content/administration/on_premise/geo_ip.rst:69 +msgid "``geoip2`` is not installed or the GeoIP database file wasn't found" +msgstr "" + +#: ../../content/administration/on_premise/geo_ip.rst:70 +msgid "The GeoIP database was unable to resolve the given IP address" +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:125 +#: ../../content/administration/on_premise/source.rst:148 +#: ../../content/administration/on_premise/source.rst:170 +#: ../../content/administration/on_premise/source.rst:195 +#: ../../content/administration/on_premise/source.rst:224 +#: ../../content/administration/on_premise/source.rst:267 +#: ../../content/administration/on_premise/source.rst:380 +#: ../../content/administration/on_premise/source.rst:442 +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:274 +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:412 +msgid "`wkhtmltopdf` is not installed through **pip** and must be installed manually in `version 0.12.5 `_ 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 15 '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 15 '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:129 +#: ../../content/administration/on_premise/source.rst:154 +#: ../../content/administration/on_premise/source.rst:176 +#: ../../content/administration/on_premise/source.rst:204 +#: ../../content/administration/on_premise/source.rst:235 +#: ../../content/administration/on_premise/source.rst:320 +#: ../../content/administration/on_premise/source.rst:389 +#: ../../content/administration/on_premise/source.rst:452 +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:137 +#: ../../content/administration/on_premise/source.rst:160 +#: ../../content/administration/on_premise/source.rst:182 +#: ../../content/administration/on_premise/source.rst:209 +#: ../../content/administration/on_premise/source.rst:249 +#: ../../content/administration/on_premise/source.rst:343 +#: ../../content/administration/on_premise/source.rst:401 +#: ../../content/administration/on_premise/source.rst:463 +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.7** or later to run." +msgstr "" + +#: ../../content/administration/on_premise/source.rst:127 +msgid "Use a package manager to download and install Python 3 if needed." +msgstr "" + +#: ../../content/administration/on_premise/source.rst:131 +msgid "`Download the latest version of Python 3 `_ and install it." +msgstr "" + +#: ../../content/administration/on_premise/source.rst:134 +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:139 +msgid "Use a package manager (`Homebrew `_, `MacPorts `_) to download and install Python 3 if needed." +msgstr "" + +#: ../../content/administration/on_premise/source.rst:143 +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:166 +msgid "Verify that `pip `_ is also installed for this version." +msgstr "" + +#: ../../content/administration/on_premise/source.rst:191 +msgid "Odoo uses PostgreSQL as its database management system." +msgstr "" + +#: ../../content/administration/on_premise/source.rst:197 +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:206 +msgid "`Download PostgreSQL `_ (supported versions: 12.0 or above) and install it." +msgstr "" + +#: ../../content/administration/on_premise/source.rst:211 +msgid "Use `Postgres.app `_ to download and install PostgreSQL (supported version: 12.0 or above)." +msgstr "" + +#: ../../content/administration/on_premise/source.rst:215 +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:219 +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:232 +#: ../../content/administration/on_premise/source.rst:257 +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:237 +msgid "Add PostgreSQL's `bin` directory (by default: :file:`C:\\\\Program Files\\\\PostgreSQL\\\\\\\\bin`) to the `PATH`." +msgstr "" + +#: ../../content/administration/on_premise/source.rst:239 +msgid "Create a postgres user with a password using the pg admin gui:" +msgstr "" + +#: ../../content/administration/on_premise/source.rst:241 +msgid "Open **pgAdmin**." +msgstr "" + +#: ../../content/administration/on_premise/source.rst:242 +msgid "Double-click the server to create a connection." +msgstr "" + +#: ../../content/administration/on_premise/source.rst:243 +msgid "Select :menuselection:`Object --> Create --> Login/Group Role`." +msgstr "" + +#: ../../content/administration/on_premise/source.rst:244 +msgid "Enter the username in the **Role Name** field (e.g., `odoo`)." +msgstr "" + +#: ../../content/administration/on_premise/source.rst:245 +msgid "Open the **Definition** tab, enter a password (e.g., `odoo`), and click **Save**." +msgstr "" + +#: ../../content/administration/on_premise/source.rst:246 +msgid "Open the **Privileges** tab and switch **Can login?** to `Yes` and **Create database?** to `Yes`." +msgstr "" + +#: ../../content/administration/on_premise/source.rst:263 +msgid "Dependencies" +msgstr "" + +#: ../../content/administration/on_premise/source.rst:269 +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:276 +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:279 +msgid "On Debian/Ubuntu, the following commands should install the required packages:" +msgstr "" + +#: ../../content/administration/on_premise/source.rst:286 +msgid "Install with pip" +msgstr "" + +#: ../../content/administration/on_premise/source.rst:288 +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:291 +msgid "On Debian/Ubuntu, the following command should install these required libraries:" +msgstr "" + +#: ../../content/administration/on_premise/source.rst:297 +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:301 +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:308 +#: ../../content/administration/on_premise/source.rst:330 +#: ../../content/administration/on_premise/source.rst:349 +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:312 +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:322 +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:326 +#: ../../content/administration/on_premise/source.rst:345 +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:334 +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:353 +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:363 +msgid "Non-Python dependencies must be installed with a package manager (`Homebrew `_, `MacPorts `_)." +msgstr "" + +#: ../../content/administration/on_premise/source.rst:366 +msgid "Download and install the **Command Line Tools**:" +msgstr "" + +#: ../../content/administration/on_premise/source.rst:372 +msgid "Use the package manager to install non-Python dependencies." +msgstr "" + +#: ../../content/administration/on_premise/source.rst:375 +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:382 +msgid "Download and install **nodejs** and **npm** with a package manager." +msgstr "" + +#: ../../content/administration/on_premise/source.rst:383 +#: ../../content/administration/on_premise/source.rst:392 +#: ../../content/administration/on_premise/source.rst:405 +msgid "Install `rtlcss`:" +msgstr "" + +#: ../../content/administration/on_premise/source.rst:391 +msgid "Download and install `nodejs `_." +msgstr "" + +#: ../../content/administration/on_premise/source.rst:398 +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:403 +msgid "Download and install **nodejs** with a package manager (`Homebrew `_, `MacPorts `_)." +msgstr "" + +#: ../../content/administration/on_premise/source.rst:420 +msgid "Running Odoo" +msgstr "" + +#: ../../content/administration/on_premise/source.rst:422 +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:425 +msgid "To configure the server, either specify :ref:`command-line arguments ` or a :ref:`configuration file `." +msgstr "" + +#: ../../content/administration/on_premise/source.rst:429 +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:433 +msgid "Common necessary configurations are:" +msgstr "" + +#: ../../content/administration/on_premise/source.rst:435 +msgid "PostgreSQL user and password." +msgstr "" + +#: ../../content/administration/on_premise/source.rst:436 +msgid "Custom addon paths beyond the defaults to load custom modules." +msgstr "" + +#: ../../content/administration/on_premise/source.rst:438 +msgid "A typical way to run the server would be:" +msgstr "" + +#: ../../content/administration/on_premise/source.rst:449 +#: ../../content/administration/on_premise/source.rst:470 +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:459 +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:473 +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:478 +msgid "From there, create and manage new :doc:`users <../../applications/general/users>`." +msgstr "" + +#: ../../content/administration/on_premise/source.rst:479 +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:483 +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 labelled 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:5 -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:13 @@ -5948,11 +4719,11 @@ msgid "Downgrading to a previous version of Odoo" msgstr "" #: ../../content/administration/upgrade.rst:34 -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:35 -msgid ":doc:`Changing hosting type ` (e.g., from on-premise to Odoo Online)" +#: ../../content/administration/upgrade.rst:36 +msgid ":ref:`Changing hosting type ` (e.g., from on-premise to Odoo Online)" msgstr "" #: ../../content/administration/upgrade.rst:37 @@ -6067,11 +4838,6 @@ msgstr "" msgid "In databases where custom modules are installed, their source code must be up-to-date with the target version of Odoo before the upgrade can be performed. If there are none, the \"update on commit\" mode is skipped, the upgraded database is built as soon as it is transferred from the upgrade platform, and the upgrade mode is exited." msgstr "" -#: ../../content/administration/upgrade.rst:150 -#: ../../content/administration/upgrade.rst:342 -msgid "On-premise" -msgstr "" - #: ../../content/administration/upgrade.rst:152 msgid "The standard upgrade process can be initiated by entering the following command line on the machine where the database is hosted:" msgstr "" @@ -6421,5 +5187,5 @@ msgid ":doc:`Odoo.sh documentation `" msgstr "" #: ../../content/administration/upgrade.rst:408 -msgid ":doc:`Supported Odoo versions `" +msgid ":doc:`Supported Odoo versions `" msgstr "" diff --git a/locale/sources/contributing.pot b/locale/sources/contributing.pot index 1a6bb3717..6361f4beb 100644 --- a/locale/sources/contributing.pot +++ b/locale/sources/contributing.pot @@ -8,7 +8,7 @@ msgid "" msgstr "" "Project-Id-Version: Odoo 15.0\n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2023-12-18 20:35+0000\n" +"POT-Creation-Date: 2024-03-20 10:19+0000\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME \n" "Language-Team: LANGUAGE \n" @@ -69,7 +69,7 @@ msgid "Submit bug reports" msgstr "" #: ../../content/contributing.rst:33 -msgid "Help improve the stability of Odoo by reporting the bugs that you discover in :doc:`supported versions ` directly to Odoo support. Make sure to include as many details (version, environment, test scenario...) as possible. If you don't have the Odoo Enterprise license required for contacting the support, open a new issue on the GitHub repository of Odoo." +msgid "Help improve the stability of Odoo by reporting the bugs that you discover in :doc:`supported versions ` directly to Odoo support. Make sure to include as many details (version, environment, test scenario...) as possible. If you don't have the Odoo Enterprise license required for contacting the support, open a new issue on the GitHub repository of Odoo." msgstr "" #: ../../content/contributing.rst:38 @@ -240,7 +240,7 @@ msgid "Follow the `guide to update the PATH variable on Windows `. Make sure to fetch the sources through Git with SSH." +msgid ":doc:`Install Odoo from the sources <../administration/on_premise/source>`. Make sure to fetch the sources through Git with SSH." msgstr "" #: ../../content/contributing/development.rst:42 @@ -286,7 +286,7 @@ msgid "Now that your environment is set up, you can start contributing to the co msgstr "" #: ../../content/contributing/development.rst:95 -msgid "Choose the version of Odoo to which you want to make changes. Keep in mind that contributions targeting an :doc:`unsupported version of Odoo ` are not accepted. This guide assumes that the changes target Odoo 15, which corresponds to branch `15.0`." +msgid "Choose the version of Odoo to which you want to make changes. Keep in mind that contributions targeting an :doc:`unsupported version of Odoo ` are not accepted. This guide assumes that the changes target Odoo 15, which corresponds to branch `15.0`." msgstr "" #: ../../content/contributing/development.rst:99 @@ -1387,7 +1387,7 @@ msgid "Now that your environment is set up, you can start contributing to the do msgstr "" #: ../../content/contributing/documentation.rst:211 -msgid "Choose the version of the documentation to which you want to make changes. Keep in mind that contributions targeting an :doc:`unsupported version of Odoo ` are not accepted. This guide assumes that the changes target the documentation of Odoo 15, which corresponds to branch `15.0`." +msgid "Choose the version of the documentation to which you want to make changes. Keep in mind that contributions targeting an :doc:`unsupported version of Odoo ` are not accepted. This guide assumes that the changes target the documentation of Odoo 15, which corresponds to branch `15.0`." msgstr "" #: ../../content/contributing/documentation.rst:233 diff --git a/locale/sources/essentials.pot b/locale/sources/essentials.pot new file mode 100644 index 000000000..902871a27 --- /dev/null +++ b/locale/sources/essentials.pot @@ -0,0 +1,829 @@ +# 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 15.0\n" +"Report-Msgid-Bugs-To: \n" +"POT-Creation-Date: 2024-03-20 10:19+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 +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:8 +msgid "Export data from Odoo" +msgstr "" + +#: ../../content/applications/essentials/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)." +msgstr "" + +#: ../../content/applications/essentials/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*." +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: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:" +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:-1 +msgid "overview of all the options to take into account when exporting data in Odoo" +msgstr "" + +#: ../../content/applications/essentials/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." +msgstr "" + +#: ../../content/applications/essentials/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." +msgstr "" + +#: ../../content/applications/essentials/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!" +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:44 +msgid "The + button is there to add fields to the \"to export\" list." +msgstr "" + +#: ../../content/applications/essentials/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." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:48 +msgid "The trashcan is there if you need to remove fields." +msgstr "" + +#: ../../content/applications/essentials/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." +msgstr "" + +#: ../../content/applications/essentials/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." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:63 +msgid "Import data into Odoo" +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:66 +msgid "How to start" +msgstr "" + +#: ../../content/applications/essentials/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!" +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:72 +msgid "Open the view of the object you want to populate and click on :menuselection:`Favorites --> Import records`." +msgstr "" + +#: ../../content/applications/essentials/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." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:83 +msgid "How to adapt the template" +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:85 +msgid "Add, remove and sort columns to fit at best your data structure." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:86 +msgid "We advise to not remove the **ID** one (see why in the next section)." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:87 +#: ../../content/applications/essentials/export_import_data.rst:376 +msgid "Set a unique ID to every single record by dragging down the ID sequencing." +msgstr "" + +#: ../../content/applications/essentials/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." +msgstr "" + +#: ../../content/applications/essentials/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." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:104 +msgid "How to import from another application" +msgstr "" + +#: ../../content/applications/essentials/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." +msgstr "" + +#: ../../content/applications/essentials/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." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:120 +msgid "I cannot find the field I want to map my column to" +msgstr "" + +#: ../../content/applications/essentials/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." +msgstr "" + +#: ../../content/applications/essentials/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." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:139 +msgid "Where can I change the date import format?" +msgstr "" + +#: ../../content/applications/essentials/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'." +msgstr "" + +#: ../../content/applications/essentials/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." +msgstr "" + +#: ../../content/applications/essentials/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." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:157 +msgid "Can I import numbers with currency sign (e.g.: $32.00)?" +msgstr "" + +#: ../../content/applications/essentials/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." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:164 +msgid "Examples of supported numbers (using thirty-two thousands as an example):" +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:166 +msgid "32.000,00" +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:167 +msgid "32000,00" +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:168 +msgid "32,000.00" +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:169 +msgid "-32000.00" +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:170 +msgid "(32000.00)" +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:171 +msgid "$ 32.000,00" +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:172 +msgid "(32000.00 €)" +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:174 +msgid "Example that will not work:" +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:176 +msgid "ABC 32.000,00" +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:177 +msgid "$ (32.000,00)" +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:180 +msgid "What can I do when the Import preview table isn't displayed correctly?" +msgstr "" + +#: ../../content/applications/essentials/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)." +msgstr "" + +#: ../../content/applications/essentials/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." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:191 +msgid "How can I change the CSV file format options when saving in my spreadsheet application?" +msgstr "" + +#: ../../content/applications/essentials/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`)." +msgstr "" + +#: ../../content/applications/essentials/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`)." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:202 +msgid "What's the difference between Database ID and External ID?" +msgstr "" + +#: ../../content/applications/essentials/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." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:209 +msgid "For example, to reference the country of a contact, Odoo proposes you 3 different fields to import:" +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:211 +msgid "Country: the name or code of the country" +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:212 +msgid "Country/Database ID: the unique Odoo ID for a record, defined by the ID postgresql column" +msgstr "" + +#: ../../content/applications/essentials/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)" +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:216 +msgid "For the country Belgium, you can use one of these 3 ways to import:" +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:218 +msgid "Country: Belgium" +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:219 +msgid "Country/Database ID: 21" +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:220 +msgid "Country/External ID: base.be" +msgstr "" + +#: ../../content/applications/essentials/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:" +msgstr "" + +#: ../../content/applications/essentials/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." +msgstr "" + +#: ../../content/applications/essentials/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)" +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:230 +msgid "Use Country/External ID: Use External ID when you import data from a third party application." +msgstr "" + +#: ../../content/applications/essentials/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." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:237 +msgid ":download:`CSV file for categories `." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:240 +msgid ":download:`CSV file for Products `." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:244 +msgid "What can I do if I have multiple matches for a field?" +msgstr "" + +#: ../../content/applications/essentials/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." +msgstr "" + +#: ../../content/applications/essentials/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'." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:256 +msgid "How can I import a many2many relationship field (e.g. a customer that has multiple tags)?" +msgstr "" + +#: ../../content/applications/essentials/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." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:262 +msgid ":download:`CSV file for Manufacturer, Retailer `" +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:266 +msgid "How can I import a one2many relationship (e.g. several Order Lines of a Sales Order)?" +msgstr "" + +#: ../../content/applications/essentials/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." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:275 +msgid ":download:`File for some Quotations `." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:277 +msgid "The following CSV file shows how to import purchase orders with their respective purchase order lines:" +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:280 +msgid ":download:`Purchase orders with their respective purchase order lines `." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:282 +msgid "The following CSV file shows how to import customers and their respective contacts:" +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:284 +msgid ":download:`Customers and their respective contacts `." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:287 +msgid "Can I import several times the same record?" +msgstr "" + +#: ../../content/applications/essentials/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." +msgstr "" + +#: ../../content/applications/essentials/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." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:298 +msgid "What happens if I do not provide a value for a specific field?" +msgstr "" + +#: ../../content/applications/essentials/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." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:305 +msgid "How to export/import different tables from an SQL application to Odoo?" +msgstr "" + +#: ../../content/applications/essentials/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)." +msgstr "" + +#: ../../content/applications/essentials/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')" +msgstr "" + +#: ../../content/applications/essentials/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 `)" +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:322 +msgid "We will first export all companies and their \"External ID\". In PSQL, write the following command:" +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:328 +msgid "This SQL command will create the following CSV file:" +msgstr "" + +#: ../../content/applications/essentials/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:" +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:343 +msgid "It will produce the following CSV file:" +msgstr "" + +#: ../../content/applications/essentials/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)." +msgstr "" + +#: ../../content/applications/essentials/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." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:364 +msgid "How to adapt an import template" +msgstr "" + +#: ../../content/applications/essentials/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.)." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:372 +msgid "How to customize the file" +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:374 +msgid "Remove columns you don't need. We advise to not remove the *ID* one (see why here below)." +msgstr "" + +#: ../../content/applications/essentials/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." +msgstr "" + +#: ../../content/applications/essentials/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." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:392 +msgid "Why an “ID” column" +msgstr "" + +#: ../../content/applications/essentials/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." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:397 +msgid "Setting an ID is not mandatory when importing but it helps in many cases:" +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:399 +msgid "Update imports: you can import the same file several times without creating duplicates;" +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:400 +msgid "Import relation fields (see here below)." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:403 +msgid "How to import relation fields" +msgstr "" + +#: ../../content/applications/essentials/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." +msgstr "" + +#: ../../content/applications/essentials/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)." +msgstr "" + +#: ../../content/applications/essentials/in_app_purchase.rst:3 +msgid "In-App Purchase (IAP)" +msgstr "" + +#: ../../content/applications/essentials/in_app_purchase.rst:5 +msgid "In-App Purchases (IAP) gives access to additional services through Odoo. For instance, it allows you to send SMS Text Messages or to send Invoices by post directly from your database." +msgstr "" + +#: ../../content/applications/essentials/in_app_purchase.rst:9 +msgid "Buying Credits" +msgstr "" + +#: ../../content/applications/essentials/in_app_purchase.rst:11 +msgid "Each IAP Service relies on prepaid credits to work and has its own pricing. To consult your current balance or to recharge your account, go to :menuselection:`Settings --> Odoo IAP --> View my Services`." +msgstr "" + +#: ../../content/applications/essentials/in_app_purchase.rst:19 +msgid "If you are on Odoo Online and have the Enterprise version, you benefit from free credits to test our IAP features." +msgstr "" + +#: ../../content/applications/essentials/in_app_purchase.rst:23 +msgid "IAP accounts" +msgstr "" + +#: ../../content/applications/essentials/in_app_purchase.rst:25 +msgid "Credits to use IAP services are stored on IAP accounts, which are specific to each service. By default, IAP accounts are common to all companies, but can be restricted to specific ones. Activate the :ref:`developer mode `, then go to :menuselection:`Technical Settings --> IAP Account`." +msgstr "" + +#: ../../content/applications/essentials/in_app_purchase.rst:34 +msgid "An IAP account can be disabled by appending `+disabled` to its token. Reverting this change will re-enable the account." +msgstr "" + +#: ../../content/applications/essentials/in_app_purchase.rst:38 +msgid "IAP Portal" +msgstr "" + +#: ../../content/applications/essentials/in_app_purchase.rst:40 +msgid "The IAP Portal is a platform regrouping your IAP Services. It is accessible from :menuselection:`Settings app --> Odoo IAP --> View my Services`. From there, you can view your current balance, recharge your credits and set a reminder when your balance falls below a threshold." +msgstr "" + +#: ../../content/applications/essentials/in_app_purchase.rst:48 +msgid "Get notified when credits are low" +msgstr "" + +#: ../../content/applications/essentials/in_app_purchase.rst:50 +msgid "To be notified when it’s time to recharge your credits, you can go to your IAP Portal through :menuselection:`Settings app --> Odoo IAP --> View my Services`, unfold a service and check the Receive threshold warning option. Then, you can provide a minimum amount of credits and email addresses. Now, every time that the limit is reached, an automatic reminder will be sent by email!" +msgstr "" diff --git a/locale/sources/finance.pot b/locale/sources/finance.pot index 4e4d34da6..b8103398e 100644 --- a/locale/sources/finance.pot +++ b/locale/sources/finance.pot @@ -8,7 +8,7 @@ msgid "" msgstr "" "Project-Id-Version: Odoo 15.0\n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2024-03-05 13:22+0000\n" +"POT-Creation-Date: 2024-03-20 10:19+0000\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME \n" "Language-Team: LANGUAGE \n" @@ -129,12 +129,12 @@ msgid "Statement" msgstr "" #: ../../content/applications/finance/accounting.rst:129 -#: ../../content/applications/finance/accounting/customer_invoices.rst:214 +#: ../../content/applications/finance/accounting/customer_invoices.rst:212 msgid "Balance sheet" msgstr "" #: ../../content/applications/finance/accounting.rst:131 -#: ../../content/applications/finance/accounting/customer_invoices.rst:204 +#: ../../content/applications/finance/accounting/customer_invoices.rst:202 msgid "Profit and loss" msgstr "" @@ -1761,87 +1761,83 @@ 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:52 #: ../../content/applications/finance/accounting/payments/internal_transfers.rst:69 #: ../../content/applications/finance/accounting/payments/internal_transfers.rst:119 @@ -1851,18 +1847,18 @@ msgstr "" 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:53 #: ../../content/applications/finance/accounting/payments/internal_transfers.rst:70 #: ../../content/applications/finance/accounting/payments/internal_transfers.rst:120 @@ -1875,8 +1871,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:54 #: ../../content/applications/finance/accounting/payments/internal_transfers.rst:71 #: ../../content/applications/finance/accounting/payments/internal_transfers.rst:121 @@ -1889,31 +1885,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:168 #: ../../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:164 #: ../../content/applications/finance/fiscal_localizations/chile.rst:198 @@ -1927,12 +1923,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/chile.rst:265 #: ../../content/applications/finance/fiscal_localizations/switzerland.rst:130 @@ -1942,7 +1938,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:170 #: ../../content/applications/finance/accounting/get_started/cheat_sheet.rst:224 #: ../../content/applications/finance/accounting/get_started/cheat_sheet.rst:226 @@ -1954,19 +1950,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:236 #: ../../content/applications/finance/accounting/get_started/cheat_sheet.rst:252 #: ../../content/applications/finance/accounting/payments/checks.rst:108 @@ -1975,75 +1971,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:192 +#: ../../content/applications/finance/accounting/customer_invoices.rst:190 msgid "Customer aging report:" msgstr "" -#: ../../content/applications/finance/accounting/customer_invoices.rst:194 +#: ../../content/applications/finance/accounting/customer_invoices.rst:192 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:198 +#: ../../content/applications/finance/accounting/customer_invoices.rst:196 msgid "Use the aging report to determine which customers are overdue and begin your collection efforts." msgstr "" -#: ../../content/applications/finance/accounting/customer_invoices.rst:206 +#: ../../content/applications/finance/accounting/customer_invoices.rst:204 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:216 +#: ../../content/applications/finance/accounting/customer_invoices.rst:214 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:223 +#: ../../content/applications/finance/accounting/customer_invoices.rst:221 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 "" @@ -3497,7 +3493,7 @@ 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 @@ -6002,11 +5998,11 @@ msgid "You can send reminder emails in batches from the :guilabel:`Follow-up Rep msgstr "" #: ../../content/applications/finance/accounting/payments/follow_up.rst:97 -msgid ":doc:`../../../general/in_app_purchase`" +msgid ":doc:`/applications/essentials/in_app_purchase`" msgstr "" #: ../../content/applications/finance/accounting/payments/follow_up.rst:98 -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:99 @@ -10036,7 +10032,7 @@ msgid "`Test Odoo's invoice digitization ` app, you can 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 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:56 @@ -10107,190 +10103,6 @@ msgstr "" msgid "`Our Privacy Policy `_." 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 type of file (max 64MB per file on Odoo Online), and organize them in various workspaces." -msgstr "" - -#: ../../content/applications/finance/documents.rst:11 -msgid "`Odoo Documents: product page `_" -msgstr "" - -#: ../../content/applications/finance/documents.rst:14 -msgid "Workflow actions" -msgstr "" - -#: ../../content/applications/finance/documents.rst:16 -msgid "Workflow actions are automated actions you can create and customize at the level of each workspace. They appear next to a file whenever it meets the criteria you set. That way you can, for example, add tags to a file or move it to another workspace with a single click. Workflow actions help you streamline the management of your documents and your overall business operations." -msgstr "" - -#: ../../content/applications/finance/documents.rst:22 -msgid "Create workflow actions" -msgstr "" - -#: ../../content/applications/finance/documents.rst:24 -msgid "To create workflow actions, go to :menuselection:`Documents --> Configuration --> Workspaces` and select the workspace where the action should apply. Click on the *Actions* smart button, and then on *Create*." -msgstr "" - -#: ../../content/applications/finance/documents.rst:-1 -msgid "Workflow actions smart button in Odoo Documents" -msgstr "" - -#: ../../content/applications/finance/documents.rst:33 -msgid "An action applies to all *Child Workspaces* under the *Parent Workspace* you selected." -msgstr "" - -#: ../../content/applications/finance/documents.rst:36 -msgid "If you use the :ref:`developer mode `, you can directly access all your actions by going to :menuselection:`Documents --> Configuration --> Actions`." -msgstr "" - -#: ../../content/applications/finance/documents.rst:40 -msgid "Set the conditions" -msgstr "" - -#: ../../content/applications/finance/documents.rst:42 -msgid "After naming your workflow action, you can set the conditions that trigger the appearance of the action button on the right-side panel when selecting a file." -msgstr "" - -#: ../../content/applications/finance/documents.rst:45 -msgid "There are three basic types of conditions you can set:" -msgstr "" - -#: ../../content/applications/finance/documents.rst:47 -msgid "**Tags**: you can both use the *Contains* and *Does not contain* conditions, meaning the files *must have* or *mustn't have* the tags set here." -msgstr "" - -#: ../../content/applications/finance/documents.rst:50 -msgid "**Contact**: the files must be associated with the contact set here." -msgstr "" - -#: ../../content/applications/finance/documents.rst:52 -msgid "**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:59 -msgid "If you don't set any conditions, the action button appears for all files located inside the selected workspace." -msgstr "" - -#: ../../content/applications/finance/documents.rst:63 -msgid "Advanced condition type: domain" -msgstr "" - -#: ../../content/applications/finance/documents.rst:66 -msgid "It is recommended to have some knowledge of Odoo development to properly configure *Domain* filters." -msgstr "" - -#: ../../content/applications/finance/documents.rst:69 -msgid "To access the *Domain* condition, the :ref:`developer mode ` needs to be activated. Once that's done, select the *Domain* condition type, and click on *Add Filter*." -msgstr "" - -#: ../../content/applications/finance/documents.rst:-1 -msgid "Activating the domain condition type in Odoo Documents" -msgstr "" - -#: ../../content/applications/finance/documents.rst:76 -msgid "To create a rule, you typically select a field, an operator, and a value. For example, if you want to add a workflow action to all the PDF files inside a workspace, set the field to *Mime Type*, the operator to *contains*, and the value to *pdf*." -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:84 -msgid "Click on *Add node* (plus-circle icon) and *Add branch* (ellipsis icon) to add conditions and sub-conditions. You can then specify if your rule should match *ALL* or *ANY* conditions. You can also edit the rule directly using the *Code editor*." -msgstr "" - -#: ../../content/applications/finance/documents.rst:-1 -msgid "Add a node or a branch to a workflow action's condition in Odoo Documents" -msgstr "" - -#: ../../content/applications/finance/documents.rst:93 -msgid "Configure the actions" -msgstr "" - -#: ../../content/applications/finance/documents.rst:95 -msgid "Select the *Actions* tab to set up your action. You can simultaneously:" -msgstr "" - -#: ../../content/applications/finance/documents.rst:97 -msgid "**Set Contact**: add a contact to the file, or replace an existing contact with a new one." -msgstr "" - -#: ../../content/applications/finance/documents.rst:98 -msgid "**Set Owner**: add an owner to the file, or replace an existing owner with a new one." -msgstr "" - -#: ../../content/applications/finance/documents.rst:99 -msgid "**Move to Workspace**: move the file to any workspace." -msgstr "" - -#: ../../content/applications/finance/documents.rst:100 -msgid "**Create**: create one of the following items attached to the file in your database:" -msgstr "" - -#: ../../content/applications/finance/documents.rst:102 -msgid "**Product template**: create a product you can edit directly." -msgstr "" - -#: ../../content/applications/finance/documents.rst:103 -msgid "**Task**: create a Project task you can edit directly." -msgstr "" - -#: ../../content/applications/finance/documents.rst:104 -msgid "**Signature request**: create a new Sign template to send out." -msgstr "" - -#: ../../content/applications/finance/documents.rst:105 -msgid "**Sign directly**: create a Sign template to sign directly." -msgstr "" - -#: ../../content/applications/finance/documents.rst:106 -msgid "**Vendor bill**: create a vendor bill using OCR and AI to scrape information from the file content." -msgstr "" - -#: ../../content/applications/finance/documents.rst:108 -msgid "**Customer invoice**: create a customer invoice using OCR and AI to scrape information from the file." -msgstr "" - -#: ../../content/applications/finance/documents.rst:110 -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:112 -msgid "**Credit note**: create a customer credit note using OCR and AI to scrape information from the file." -msgstr "" - -#: ../../content/applications/finance/documents.rst:114 -msgid "**Applicant**: create a new HR application you can edit directly." -msgstr "" - -#: ../../content/applications/finance/documents.rst:116 -msgid "**Set Tags**: add, remove, and replace any number of tags." -msgstr "" - -#: ../../content/applications/finance/documents.rst:117 -msgid "**Activities - Mark all as Done**: mark all activities linked to the file as done." -msgstr "" - -#: ../../content/applications/finance/documents.rst:118 -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/expenses.rst:5 #: ../../content/applications/finance/fiscal_localizations/united_arab_emirates.rst:104 #: ../../content/applications/finance/fiscal_localizations/united_arab_emirates.rst:107 @@ -10507,7 +10319,7 @@ msgid "Create the domain alias by clicking the link." msgstr "" #: ../../content/applications/finance/expenses.rst:210 -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:216 @@ -10659,7 +10471,7 @@ msgid ":guilabel:`Settings`: The user has access to the entire *Settings* app wi msgstr "" #: ../../content/applications/finance/expenses.rst:367 -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:370 @@ -12404,7 +12216,7 @@ msgid "Odoo 14.0" msgstr "" #: ../../content/applications/finance/fiscal_localizations/belgium.rst:56 -msgid ":doc:`/administration/maintain/supported_versions`" +msgid ":doc:`/administration/supported_versions`" msgstr "" #: ../../content/applications/finance/fiscal_localizations/belgium.rst:58 @@ -12544,7 +12356,7 @@ msgid "the Mac address of your IoT Box." msgstr "" #: ../../content/applications/finance/fiscal_localizations/belgium.rst:156 -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." +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 @@ -14565,7 +14377,7 @@ msgid "`Odoo: Download Odoo `_" 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 @@ -15401,7 +15213,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 @@ -17193,7 +17005,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 @@ -17205,7 +17017,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 @@ -17698,7 +17510,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 @@ -21884,163 +21696,3 @@ msgstr "" #: ../../content/applications/finance/payment_acquirers/wire_transfer.rst:52 msgid ":ref:`payment_acquirers/journal`" 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." -msgstr "" - -#: ../../content/applications/finance/sign.rst:7 -msgid "You can upload any PDF file and add drag-and-dropping fields on it. These fields are automatically filled out with the user's detail if they are logged in." -msgstr "" - -#: ../../content/applications/finance/sign.rst:11 -msgid "`Odoo Sign: product page `_" -msgstr "" - -#: ../../content/applications/finance/sign.rst:12 -msgid "`Odoo Tutorials: Sign `_" -msgstr "" - -#: ../../content/applications/finance/sign.rst:17 -msgid "Validity of electronic signatures" -msgstr "" - -#: ../../content/applications/finance/sign.rst:19 -msgid "The legal validity of electronic signatures generated by Odoo depends on the legislation of your country. Companies doing business abroad should consider electronic signature laws of other countries as well." -msgstr "" - -#: ../../content/applications/finance/sign.rst:24 -msgid "In the European Union" -msgstr "" - -#: ../../content/applications/finance/sign.rst:26 -msgid "The `eIDAS regulation `_ establishes the framework for electronic signatures in all `27 member states of the European Union `_." -msgstr "" - -#: ../../content/applications/finance/sign.rst:30 -msgid "It distinguishes three types of electronic signatures:" -msgstr "" - -#: ../../content/applications/finance/sign.rst:32 -msgid "Electronic signatures" -msgstr "" - -#: ../../content/applications/finance/sign.rst:33 -msgid "Advanced electronic signatures" -msgstr "" - -#: ../../content/applications/finance/sign.rst:34 -msgid "Qualified electronic signatures" -msgstr "" - -#: ../../content/applications/finance/sign.rst:36 -msgid "Odoo generates the first type, regular electronic signatures, and these signatures can produce legal effects in the EU, as the regulation states that “an electronic signature shall not be denied legal effect and admissibility as evidence in legal proceedings solely on the grounds that it is in an electronic form or that it does not meet the requirements for qualified electronic signatures.”" -msgstr "" - -#: ../../content/applications/finance/sign.rst:41 -msgid "Note that electronic signatures may not be automatically recognized as valid. You may need to bring supporting evidence of a signature’s validity." -msgstr "" - -#: ../../content/applications/finance/sign.rst:45 -msgid "In the United States of America" -msgstr "" - -#: ../../content/applications/finance/sign.rst:47 -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:56 -msgid "Overall, to be recognized as valid, electronic signatures have to meet five criteria:" -msgstr "" - -#: ../../content/applications/finance/sign.rst:58 -msgid "A 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 electronically signing a document." -msgstr "" - -#: ../../content/applications/finance/sign.rst:61 -msgid "A signer must first express or imply their consent to conduct business electronically." -msgstr "" - -#: ../../content/applications/finance/sign.rst:62 -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:64 -msgid "The signature must be associated with the document being signed, for example, by keeping a record detailing how the signature was captured." -msgstr "" - -#: ../../content/applications/finance/sign.rst:66 -msgid "Electronically signed documents need to be retained and available for later reference by all parties involved, for example, by providing the signer either a fully-executed copy or the option to download a copy." -msgstr "" - -#: ../../content/applications/finance/sign.rst:71 -msgid "The information provided here does not constitute legal advice; it is provided for general informational purposes only. As laws governing electronic signatures rapidly evolve, we cannot guarantee whether all information is up to date or not. We advise contacting a local attorney for legal advice regarding electronic signature compliance and validity." -msgstr "" - -#: ../../content/applications/finance/sign.rst:79 -msgid "Field Types" -msgstr "" - -#: ../../content/applications/finance/sign.rst:81 -msgid "By configuring your own *Field Types*, also known as *Signature Item Types*, you can make the signing process even faster for your customers, partners, and employees." -msgstr "" - -#: ../../content/applications/finance/sign.rst:84 -msgid "To create and customize fields, activate the :ref:`developer mode `. Then head to :menuselection:`Documents --> Configuration --> Field Types` and click on *Create*." -msgstr "" - -#: ../../content/applications/finance/sign.rst:87 -msgid "After giving your new field a name, select one of the six *Types* available:" -msgstr "" - -#: ../../content/applications/finance/sign.rst:89 -msgid "**Signature**: users are prompted to enter their signature either by drawing it, automatically generating one based on their name, or uploading a local file (usually an image). Each subsequent *Signature* field then reuses the data entered in the first field." -msgstr "" - -#: ../../content/applications/finance/sign.rst:92 -msgid "**Initial**: users are prompted to enter their initials, in a similar way to the *Signature* field." -msgstr "" - -#: ../../content/applications/finance/sign.rst:94 -msgid "**Text**: users enter text on a single line." -msgstr "" - -#: ../../content/applications/finance/sign.rst:95 -msgid "**Multiline Text**: users enter text on multiple lines." -msgstr "" - -#: ../../content/applications/finance/sign.rst:96 -msgid "**Checkbox**: users can tick a box (e.g.,to mark their approval or consent)." -msgstr "" - -#: ../../content/applications/finance/sign.rst:97 -msgid "**Selection**: users choose a single option from a variety of options." -msgstr "" - -#: ../../content/applications/finance/sign.rst:99 -msgid "Next, you have the option to auto-complete fields for users based on their Odoo profile information by using *Automatic Partner Field*. To this end, the *Name*, *Email*, *Phone*, and *Company* fields are preconfigured in your database." -msgstr "" - -#: ../../content/applications/finance/sign.rst:104 -msgid "Users can freely edit auto-completed fields." -msgstr "" - -#: ../../content/applications/finance/sign.rst:-1 -msgid "Company field example in Odoo Sign" -msgstr "" - -#: ../../content/applications/finance/sign.rst:110 -msgid "You can then change the size of the field by editing the *Default Width* and *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:115 -msgid "Next, write a *Tip*. Tips are displayed inside arrows on the left-hand side of the user's screen during the signing process. You can also use a *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 "" diff --git a/locale/sources/general.pot b/locale/sources/general.pot index 568ba0d4d..37bd83fd1 100644 --- a/locale/sources/general.pot +++ b/locale/sources/general.pot @@ -8,7 +8,7 @@ msgid "" msgstr "" "Project-Id-Version: Odoo 15.0\n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2024-03-05 13:22+0000\n" +"POT-Creation-Date: 2024-03-20 10:19+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,812 @@ 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:13 +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: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)." 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: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." 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: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*." 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: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:" msgstr "" -#: ../../content/applications/general/auth/2fa.rst:43 -msgid "Setting up two-factor authentication" +#: ../../content/applications/general/companies.rst:45 +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:46 +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:53 +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:55 +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: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." 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: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)." 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:68 +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:70 +msgid "The current company (the one active) or," msgstr "" -#: ../../content/applications/general/auth/2fa.rst:107 -msgid "Logging in" +#: ../../content/applications/general/companies.rst:71 +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:72 +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:75 +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:77 +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:85 +msgid "Inter-Company Transactions" msgstr "" -#: ../../content/applications/general/auth/azure.rst:3 -msgid "Microsoft Azure sign-in authentication" +#: ../../content/applications/general/companies.rst:87 +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:89 +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:90 +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:91 +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:92 +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:93 +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:94 +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: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." 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:104 +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: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." 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: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*." 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: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)." 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:127 +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:130 +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:133 +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:134 +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." 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:32 +msgid "*Dynamic placeholders* (text that references fields within Odoo to auto-fill information on the template) are available for the :guilabel:`Email Configuration` fields, the :guilabel:`Subject`, and the :guilabel:`Language`." msgstr "" -#: ../../content/applications/general/auth/ldap.rst:3 -msgid "Sign in with LDAP" +#: ../../content/applications/general/companies/email_template.rst:37 +msgid "Powerbox" 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:39 +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:7 -msgid "Click on **Create** in Setup the :abbr:`LDAP (Lightweight Directory Access Protocol)` Server." +#: ../../content/applications/general/companies/email_template.rst:43 +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:-1 -msgid "LDAP Authentication checkbox highlighted in the integrations settings on Odoo." +#: ../../content/applications/general/companies/email_template.rst:46 +msgid ":guilabel:`Basic Blocks`" msgstr "" -#: ../../content/applications/general/auth/ldap.rst:-1 -msgid "Create highlighted in the LDAP server settings." +#: ../../content/applications/general/companies/email_template.rst:48 +msgid ":guilabel:`Heading 1`: Big section heading." msgstr "" -#: ../../content/applications/general/auth/ldap.rst:17 -msgid "Choose the company using the LDAP." +#: ../../content/applications/general/companies/email_template.rst:49 +msgid ":guilabel:`Heading 2`: Medium section heading." 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:50 +msgid ":guilabel:`Heading 3`: Small section heading." 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:51 +msgid ":guilabel:`Text`: Paragraph block." msgstr "" -#: ../../content/applications/general/auth/ldap.rst:25 -msgid "Tick **Use TLS** if the server is compatible." +#: ../../content/applications/general/companies/email_template.rst:52 +msgid ":guilabel:`Bulleted list`: Create a simple bulleted list." 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:53 +msgid ":guilabel:`Numbered list`: Create a list with numbering." 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:54 +msgid ":guilabel:`Checklist`: Track tasks with a checklist." 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:55 +msgid ":guilabel:`Table`: Insert a table." 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:56 +msgid ":guilabel:`Switch direction`: Switch the text's direction." msgstr "" -#: ../../content/applications/general/auth/ldap.rst:41 -msgid "In **LDAP filter**, enter ``uid=%s``" +#: ../../content/applications/general/companies/email_template.rst:57 +msgid ":guilabel:`Separator`: Insert a horizontal rule separator." 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:`Quote`: Add a blockquote section." 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:`Code`: Add a code section." 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:`Appointment`: Add a specific appointment." 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:`Calendar`: Schedule an appointment." +msgstr "" + +#: ../../content/applications/general/companies/email_template.rst:63 +msgid ":guilabel:`Navigation`" +msgstr "" + +#: ../../content/applications/general/companies/email_template.rst:65 +msgid ":guilabel:`Link`: Add a link." +msgstr "" + +#: ../../content/applications/general/companies/email_template.rst:66 +msgid ":guilabel:`Button`: Add a button." +msgstr "" + +#: ../../content/applications/general/companies/email_template.rst:68 +msgid ":guilabel:`Medias`" +msgstr "" + +#: ../../content/applications/general/companies/email_template.rst:70 +msgid ":guilabel:`Image`: Insert an image." +msgstr "" + +#: ../../content/applications/general/companies/email_template.rst:73 +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:83 +msgid "XML/HTML code editor" +msgstr "" + +#: ../../content/applications/general/companies/email_template.rst:85 +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:95 +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:100 +msgid "Dynamic placeholders" +msgstr "" + +#: ../../content/applications/general/companies/email_template.rst:102 +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:106 +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:112 +msgid "Dynamic placeholders are encoded to display fields from within the database. Dynamic placeholders can **only** 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:116 +msgid "Dynamic placeholders can be used with the following fields on an email template:" +msgstr "" + +#: ../../content/applications/general/companies/email_template.rst:118 +msgid ":guilabel:`Subject` (:guilabel:`Content` tab)" +msgstr "" + +#: ../../content/applications/general/companies/email_template.rst:119 +msgid ":guilabel:`From` (:guilabel:`Email Configuration` tab)" +msgstr "" + +#: ../../content/applications/general/companies/email_template.rst:120 +msgid ":guilabel:`To (Emails)` (:guilabel:`Email Configuration` tab)" +msgstr "" + +#: ../../content/applications/general/companies/email_template.rst:121 +msgid ":guilabel:`To (Partners)` (:guilabel:`Email Configuration` tab)" +msgstr "" + +#: ../../content/applications/general/companies/email_template.rst:122 +msgid ":guilabel:`CC` (:guilabel:`Email Configuration` tab)" +msgstr "" + +#: ../../content/applications/general/companies/email_template.rst:123 +msgid ":guilabel:`Reply-To` (:guilabel:`Email Configuration` tab)" +msgstr "" + +#: ../../content/applications/general/companies/email_template.rst:124 +msgid ":guilabel:`Language` (:guilabel:`Advanced Settings` tab)" +msgstr "" + +#: ../../content/applications/general/companies/email_template.rst:126 +msgid "The :guilabel:`Dynamic Placeholder Generator`, which is the last tab on the email template, creates placeholders for the aforementioned fields. Dynamic placeholders may also be inserted in the HTML code, but this task is out of the scope of Odoo Support." +msgstr "" + +#: ../../content/applications/general/companies/email_template.rst:130 +msgid "To use the *Dynamic Placeholder Generator*, navigate to the :guilabel:`Dynamic Placeholder Generator` tab. Select the field that the dynamic placeholder should reference using the :guilabel:`Field` drop-down menu. Should a :guilabel:`Sub-Model` or :guilabel:`Sub-Field` need to be specified, set those by selecting the corresponding drop-down menu. These fields should be set automatically after setting the :guilabel:`Field`, although in some instances these fields will remain empty. The dynamic placeholder will appear in the :guilabel:`Placeholder Expression` field. Copy and paste the placeholder expression into the appropriate field in the tabs of the email template, as listed in the bulleted list above." +msgstr "" + +#: ../../content/applications/general/companies/email_template.rst:140 +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:144 +msgid "To search the available fields, simply click the drop-down menu next to :guilabel:`Field` and select one, or click :guilabel:`Search More` to select from all of the available fields for the model that the email template is created for." +msgstr "" + +#: ../../content/applications/general/companies/email_template.rst:149 +msgid ":doc:`/applications/studio/models_modules_apps`." +msgstr "" + +#: ../../content/applications/general/companies/email_template.rst:152 +msgid "These fields can also be accessed in :ref:`developer mode `. On a contact form (or other relevant form in Odoo), navigate to the information that should be referenced in the dynamic placeholder, and hover over the field name. A box of backend information will reveal itself with the specific Odoo :guilabel:`Field` name in the backend. Search for this field in the :guilabel:`Field` drop-down menu in the email template." +msgstr "" + +#: ../../content/applications/general/companies/email_template.rst:0 +msgid "Backend information box of fields on a model." +msgstr "" + +#: ../../content/applications/general/companies/email_template.rst:163 +msgid ":ref:`Views and fields in the developer documentation `." +msgstr "" + +#: ../../content/applications/general/companies/email_template.rst:166 +msgid "Customizing email templates are out of the scope of Odoo Support." +msgstr "" + +#: ../../content/applications/general/companies/email_template.rst:169 +msgid "Default reply on email templates" +msgstr "" + +#: ../../content/applications/general/companies/email_template.rst:171 +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:176 +msgid "A 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:183 +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:186 +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:191 +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:201 +msgid "Transactional emails and corresponding URLs" +msgstr "" + +#: ../../content/applications/general/companies/email_template.rst:203 +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:206 +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:210 +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:214 +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:220 +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:226 +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:232 +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:237 +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:242 +msgid "For more information about how to configure domains, check out the :doc:`domain name documentation `." +msgstr "" + +#: ../../content/applications/general/companies/email_template.rst:246 +msgid "Updating translations within email templates" +msgstr "" + +#: ../../content/applications/general/companies/email_template.rst:248 +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:253 +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:257 +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:266 +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:269 +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:278 +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 +997,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 +1697,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 +1729,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 +1845,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 +1873,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 +1933,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 @@ -1599,348 +1944,36 @@ msgstr "" msgid "This value can be changed in :ref:`developer mode `. Go to :menuselection:`Settings --> Technical --> Automation --> Scheduled Actions` and look for :guilabel:`Mail: Fetchmail Service`." msgstr "" -#: ../../content/applications/general/email_communication/email_template.rst:3 -msgid "Email templates" +#: ../../content/applications/general/email_communication/email_servers.rst:278 +msgid "Allow alias domain system parameter" msgstr "" -#: ../../content/applications/general/email_communication/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." +#: ../../content/applications/general/email_communication/email_servers.rst:280 +msgid "Incoming aliases are set in the Odoo database to create records by receiving incoming emails. To view aliases set in the Odoo database, first activate the :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:284 +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:289 +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:294 +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:299 +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: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:304 +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:29 -msgid "Additionally, the XML/HTML code of the email template can be edited directly, via the :guilabel:`` icon." -msgstr "" - -#: ../../content/applications/general/email_communication/email_template.rst:32 -msgid "*Dynamic placeholders* (text that references fields within Odoo to auto-fill information on the template) are available for the :guilabel:`Email Configuration` fields, the :guilabel:`Subject`, and the :guilabel:`Language`." -msgstr "" - -#: ../../content/applications/general/email_communication/email_template.rst:37 -msgid "Powerbox" -msgstr "" - -#: ../../content/applications/general/email_communication/email_template.rst:39 -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:43 -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:46 -msgid ":guilabel:`Basic Blocks`" -msgstr "" - -#: ../../content/applications/general/email_communication/email_template.rst:48 -msgid ":guilabel:`Heading 1`: Big section heading." -msgstr "" - -#: ../../content/applications/general/email_communication/email_template.rst:49 -msgid ":guilabel:`Heading 2`: Medium section heading." -msgstr "" - -#: ../../content/applications/general/email_communication/email_template.rst:50 -msgid ":guilabel:`Heading 3`: Small section heading." -msgstr "" - -#: ../../content/applications/general/email_communication/email_template.rst:51 -msgid ":guilabel:`Text`: Paragraph block." -msgstr "" - -#: ../../content/applications/general/email_communication/email_template.rst:52 -msgid ":guilabel:`Bulleted list`: Create a simple bulleted list." -msgstr "" - -#: ../../content/applications/general/email_communication/email_template.rst:53 -msgid ":guilabel:`Numbered list`: Create a list with numbering." -msgstr "" - -#: ../../content/applications/general/email_communication/email_template.rst:54 -msgid ":guilabel:`Checklist`: Track tasks with a checklist." -msgstr "" - -#: ../../content/applications/general/email_communication/email_template.rst:55 -msgid ":guilabel:`Table`: Insert a table." -msgstr "" - -#: ../../content/applications/general/email_communication/email_template.rst:56 -msgid ":guilabel:`Switch direction`: Switch the text's direction." -msgstr "" - -#: ../../content/applications/general/email_communication/email_template.rst:57 -msgid ":guilabel:`Separator`: Insert a horizontal rule separator." -msgstr "" - -#: ../../content/applications/general/email_communication/email_template.rst:58 -msgid ":guilabel:`Quote`: Add a blockquote section." -msgstr "" - -#: ../../content/applications/general/email_communication/email_template.rst:59 -msgid ":guilabel:`Code`: Add a code section." -msgstr "" - -#: ../../content/applications/general/email_communication/email_template.rst:60 -msgid ":guilabel:`Appointment`: Add a specific appointment." -msgstr "" - -#: ../../content/applications/general/email_communication/email_template.rst:61 -msgid ":guilabel:`Calendar`: Schedule an appointment." -msgstr "" - -#: ../../content/applications/general/email_communication/email_template.rst:63 -msgid ":guilabel:`Navigation`" -msgstr "" - -#: ../../content/applications/general/email_communication/email_template.rst:65 -msgid ":guilabel:`Link`: Add a link." -msgstr "" - -#: ../../content/applications/general/email_communication/email_template.rst:66 -msgid ":guilabel:`Button`: Add a button." -msgstr "" - -#: ../../content/applications/general/email_communication/email_template.rst:68 -msgid ":guilabel:`Medias`" -msgstr "" - -#: ../../content/applications/general/email_communication/email_template.rst:70 -msgid ":guilabel:`Image`: Insert an image." -msgstr "" - -#: ../../content/applications/general/email_communication/email_template.rst:73 -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:83 -msgid "XML/HTML code editor" -msgstr "" - -#: ../../content/applications/general/email_communication/email_template.rst:85 -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:95 -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:100 -msgid "Dynamic placeholders" -msgstr "" - -#: ../../content/applications/general/email_communication/email_template.rst:102 -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:106 -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:112 -msgid "Dynamic placeholders are encoded to display fields from within the database. Dynamic placeholders can **only** 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:116 -msgid "Dynamic placeholders can be used with the following fields on an email template:" -msgstr "" - -#: ../../content/applications/general/email_communication/email_template.rst:118 -msgid ":guilabel:`Subject` (:guilabel:`Content` tab)" -msgstr "" - -#: ../../content/applications/general/email_communication/email_template.rst:119 -msgid ":guilabel:`From` (:guilabel:`Email Configuration` tab)" -msgstr "" - -#: ../../content/applications/general/email_communication/email_template.rst:120 -msgid ":guilabel:`To (Emails)` (:guilabel:`Email Configuration` tab)" -msgstr "" - -#: ../../content/applications/general/email_communication/email_template.rst:121 -msgid ":guilabel:`To (Partners)` (:guilabel:`Email Configuration` tab)" -msgstr "" - -#: ../../content/applications/general/email_communication/email_template.rst:122 -msgid ":guilabel:`CC` (:guilabel:`Email Configuration` tab)" -msgstr "" - -#: ../../content/applications/general/email_communication/email_template.rst:123 -msgid ":guilabel:`Reply-To` (:guilabel:`Email Configuration` tab)" -msgstr "" - -#: ../../content/applications/general/email_communication/email_template.rst:124 -msgid ":guilabel:`Language` (:guilabel:`Advanced Settings` tab)" -msgstr "" - -#: ../../content/applications/general/email_communication/email_template.rst:126 -msgid "The :guilabel:`Dynamic Placeholder Generator`, which is the last tab on the email template, creates placeholders for the aforementioned fields. Dynamic placeholders may also be inserted in the HTML code, but this task is out of the scope of Odoo Support." -msgstr "" - -#: ../../content/applications/general/email_communication/email_template.rst:130 -msgid "To use the *Dynamic Placeholder Generator*, navigate to the :guilabel:`Dynamic Placeholder Generator` tab. Select the field that the dynamic placeholder should reference using the :guilabel:`Field` drop-down menu. Should a :guilabel:`Sub-Model` or :guilabel:`Sub-Field` need to be specified, set those by selecting the corresponding drop-down menu. These fields should be set automatically after setting the :guilabel:`Field`, although in some instances these fields will remain empty. The dynamic placeholder will appear in the :guilabel:`Placeholder Expression` field. Copy and paste the placeholder expression into the appropriate field in the tabs of the email template, as listed in the bulleted list above." -msgstr "" - -#: ../../content/applications/general/email_communication/email_template.rst:140 -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:144 -msgid "To search the available fields, simply click the drop-down menu next to :guilabel:`Field` and select one, or click :guilabel:`Search More` to select 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:149 -msgid ":doc:`../../productivity/studio/models_modules_apps`." -msgstr "" - -#: ../../content/applications/general/email_communication/email_template.rst:152 -msgid "These fields can also be accessed in :ref:`developer mode `. On a contact form (or other relevant form in Odoo), navigate to the information that should be referenced in the dynamic placeholder, and hover over the field name. A box of backend information will reveal itself with the specific Odoo :guilabel:`Field` name in the backend. Search for this field in the :guilabel:`Field` drop-down menu in the email template." -msgstr "" - -#: ../../content/applications/general/email_communication/email_template.rst:0 -msgid "Backend information box of fields on a model." -msgstr "" - -#: ../../content/applications/general/email_communication/email_template.rst:163 -msgid ":ref:`Views and fields in the developer documentation `." -msgstr "" - -#: ../../content/applications/general/email_communication/email_template.rst:166 -msgid "Customizing email templates are out of the scope of Odoo Support." -msgstr "" - -#: ../../content/applications/general/email_communication/email_template.rst:169 -msgid "Default reply on email templates" -msgstr "" - -#: ../../content/applications/general/email_communication/email_template.rst:171 -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:176 -msgid "A 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:183 -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:186 -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:191 -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:201 -msgid "Transactional emails and corresponding URLs" -msgstr "" - -#: ../../content/applications/general/email_communication/email_template.rst:203 -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:206 -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:210 -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:214 -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:220 -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:226 -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:232 -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:237 -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:242 -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:246 -msgid "Updating translations within email templates" -msgstr "" - -#: ../../content/applications/general/email_communication/email_template.rst:248 -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:253 -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:257 -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:266 -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:269 -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:278 -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 @@ -2215,565 +2248,3031 @@ 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 +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 API :guilabel:`Key`" msgstr "" -#: ../../content/applications/general/geolocation.rst:-1 +#: ../../content/applications/general/integrations/geolocation.rst:-1 msgid "Google Places API key" 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:5 -msgid "In-App Purchases (IAP) gives access to additional services through Odoo. For instance, it allows you to send SMS Text Messages or to send Invoices by post directly from your database." +#: ../../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:9 -msgid "Buying Credits" +#: ../../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:11 -msgid "Each IAP Service relies on prepaid credits to work and has its own pricing. To consult your current balance or to recharge your account, go to :menuselection:`Settings --> Odoo IAP --> View my Services`." +#: ../../content/applications/general/integrations/mail_plugins.rst:17 +msgid "Generating tasks in any Odoo project." msgstr "" -#: ../../content/applications/general/in_app_purchase.rst:19 -msgid "If you are on Odoo Online and have the Enterprise version, you benefit from free credits to test our IAP features." +#: ../../content/applications/general/integrations/mail_plugins.rst:18 +msgid "Creating tickets in the Helpdesk app." msgstr "" -#: ../../content/applications/general/in_app_purchase.rst:23 -msgid "IAP accounts" +#: ../../content/applications/general/integrations/mail_plugins.rst:19 +msgid "Searching and storing insights on your contacts." msgstr "" -#: ../../content/applications/general/in_app_purchase.rst:25 -msgid "Credits to use IAP services are stored on IAP accounts, which are specific to each service. By default, IAP accounts are common to all companies, but can be restricted to specific ones. Activate the :ref:`developer mode `, then go to :menuselection:`Technical Settings --> IAP Account`." +#: ../../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:34 -msgid "An IAP account can be disabled by appending `+disabled` to its token. Reverting this change will re-enable the account." +#: ../../content/applications/general/integrations/mail_plugins.rst:27 +msgid "Pricing" msgstr "" -#: ../../content/applications/general/in_app_purchase.rst:38 -msgid "IAP Portal" +#: ../../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:40 -msgid "The IAP Portal is a platform regrouping your IAP Services. It is accessible from :menuselection:`Settings app --> Odoo IAP --> View my Services`. From there, you can view your current balance, recharge your credits and set a reminder when your balance falls below a threshold." +#: ../../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:48 -msgid "Get notified when credits are low" +#: ../../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:50 -msgid "To be notified when it’s time to recharge your credits, you can go to your IAP Portal through :menuselection:`Settings app --> Odoo IAP --> View my Services`, unfold a service and check the Receive threshold warning option. Then, you can provide a minimum amount of credits and email addresses. Now, every time that the limit is reached, an automatic reminder will be sent by email!" +#: ../../content/applications/general/integrations/mail_plugins.rst:41 +msgid "Lead Generation IAP service" +msgstr "" + +#: ../../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/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/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/integrations/mail_plugins.rst:52 +msgid "Check out the `Lead Generation IAP service Privacy Policy `_." +msgstr "" + +#: ../../content/applications/general/integrations/mail_plugins.rst:56 +msgid ":doc:`../../essentials/in_app_purchase`" +msgstr "" + +#: ../../content/applications/general/integrations/mail_plugins.rst:57 +msgid "`Odoo Tutorials: Lead Enrichment `_" +msgstr "" + +#: ../../content/applications/general/integrations/mail_plugins/gmail.rst:3 +msgid "Gmail Plugin" +msgstr "" + +#: ../../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/integrations/mail_plugins/gmail.rst:9 +msgid "Odoo Online users" +msgstr "" + +#: ../../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/integrations/mail_plugins/gmail.rst:15 +#: ../../content/applications/general/integrations/mail_plugins/gmail.rst:94 +msgid "Install the Gmail Plugin" +msgstr "" + +#: ../../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/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/integrations/mail_plugins/gmail.rst:-1 +msgid "Plus sign icon on the Gmail inbox side panel." +msgstr "" + +#: ../../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/integrations/mail_plugins/gmail.rst:-1 +msgid "Odoo Inbox Addin on Google Workspace Marketplace." +msgstr "" + +#: ../../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/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/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/integrations/mail_plugins/gmail.rst:43 +#: ../../content/applications/general/integrations/mail_plugins/gmail.rst:134 +msgid "Configure the Odoo database" +msgstr "" + +#: ../../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/integrations/mail_plugins/gmail.rst:-1 +msgid "The Mail Plugin feature in the Settings." +msgstr "" + +#: ../../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/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/integrations/mail_plugins/gmail.rst:-1 +msgid "The Authorize Access button in the right sidebar of the Odoo plugin panel." +msgstr "" + +#: ../../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/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/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/integrations/mail_plugins/gmail.rst:78 +msgid "Odoo On-Premise users" +msgstr "" + +#: ../../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/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/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/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/integrations/mail_plugins/gmail.rst:-1 +msgid "Download the ZIP file from the Odoo GitHub repository for Mail Plugins." +msgstr "" + +#: ../../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/integrations/mail_plugins/gmail.rst:108 +msgid "Delete the following three lines of text from the :file:`login.ts` file:" +msgstr "" + +#: ../../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/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/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/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/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/integrations/mail_plugins/outlook.rst:3 +msgid "Outlook Plugin" +msgstr "" + +#: ../../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/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/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/integrations/mail_plugins/outlook.rst:17 +msgid "Enable Mail Plugin" +msgstr "" + +#: ../../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/integrations/mail_plugins/outlook.rst:25 +msgid "Install the Outlook Plugin" +msgstr "" + +#: ../../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/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/integrations/mail_plugins/outlook.rst:-1 +msgid "More actions button in Outlook" +msgstr "" + +#: ../../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/integrations/mail_plugins/outlook.rst:-1 +msgid "My add-ins in Outlook" +msgstr "" + +#: ../../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/integrations/mail_plugins/outlook.rst:-1 +msgid "Custom add-ins in Outlook" +msgstr "" + +#: ../../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/integrations/mail_plugins/outlook.rst:-1 +msgid "Custom add-in installation warning in Outlook" +msgstr "" + +#: ../../content/applications/general/integrations/mail_plugins/outlook.rst:61 +msgid "Connect the database" +msgstr "" + +#: ../../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/integrations/mail_plugins/outlook.rst:-1 +msgid "Odoo for Outlook add-in button" +msgstr "" + +#: ../../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/integrations/mail_plugins/outlook.rst:-1 +msgid "Logging in the Odoo database" +msgstr "" + +#: ../../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/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/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/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/integrations/mail_plugins/outlook.rst:94 +msgid "Once this is complete, the Outlook panel needs to be opened again." +msgstr "" + +#: ../../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/integrations/mail_plugins/outlook.rst:-1 +msgid "Entering the Odoo database URL" +msgstr "" + +#: ../../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/integrations/mail_plugins/outlook.rst:-1 +msgid "New window pop-up warning" +msgstr "" + +#: ../../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/integrations/mail_plugins/outlook.rst:-1 +msgid "Allowing the Outlook Plugin to connect to a database" +msgstr "" + +#: ../../content/applications/general/integrations/mail_plugins/outlook.rst:118 +msgid "Add a shortcut to the plugin" +msgstr "" + +#: ../../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/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/integrations/mail_plugins/outlook.rst:-1 +msgid "Viewing all Outlook settings" +msgstr "" + +#: ../../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/integrations/mail_plugins/outlook.rst:-1 +msgid "Odoo for Outlook customized action" +msgstr "" + +#: ../../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/integrations/mail_plugins/outlook.rst:144 +msgid "Using the plugin" +msgstr "" + +#: ../../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/integrations/unsplash.rst:3 +msgid "Unsplash (free images)" +msgstr "" + +#: ../../content/applications/general/integrations/unsplash.rst:6 +msgid "Generate an Unsplash access key" +msgstr "" + +#: ../../content/applications/general/integrations/unsplash.rst:9 +msgid "**As an Odoo Online user**, you are ready to use Unsplash. You won't need to follow this guide to set up Unsplash information since you will use our own Odoo Unsplash key in a transparent way." +msgstr "" + +#: ../../content/applications/general/integrations/unsplash.rst:13 +msgid "Generate an Unsplash access key for non-Odoo Online users" +msgstr "" + +#: ../../content/applications/general/integrations/unsplash.rst:15 +msgid "Create an account on `Unsplash.com `_." +msgstr "" + +#: ../../content/applications/general/integrations/unsplash.rst:17 +msgid "Go to your `applications dashboard `_ and click on **New Application**." +msgstr "" + +#: ../../content/applications/general/integrations/unsplash.rst:23 +msgid "Accept the conditions and click on **Accept terms**." +msgstr "" + +#: ../../content/applications/general/integrations/unsplash.rst:28 +msgid "You will be prompted to insert an **Application name** and a **Description**. Please prefix your application name by \"**Odoo:** \" so that Unsplash can recognize it as an Odoo instance. Once done, click on **Create application**." +msgstr "" + +#: ../../content/applications/general/integrations/unsplash.rst:35 +msgid "You should be redirected to your application details page. Scroll down a bit to find your **access key**." +msgstr "" + +#: ../../content/applications/general/integrations/unsplash.rst:42 +msgid "**As a non-Odoo Online user**, you won't be able to register for a production Unsplash key and will be limited to your test key that has a restriction of 50 Unsplash requests per hour." +msgstr "" + +#: ../../content/applications/general/integrations/unsplash.rst:46 +msgid "Generate an Unsplash application ID" +msgstr "" + +#: ../../content/applications/general/integrations/unsplash.rst:49 +msgid "You should first create and set up your Unsplash application." +msgstr "" + +#: ../../content/applications/general/integrations/unsplash.rst:51 +msgid "Go to your `applications dashboard `_ and click on your newly created Unsplash application under **Your applications**." +msgstr "" + +#: ../../content/applications/general/integrations/unsplash.rst:57 +msgid "You will be redirected to your application details page. The **application ID** will be visible in your browser's URL. The URL should be something like ``https://unsplash.com/oauth/applications/``" +msgstr "" + +#: ../../content/applications/general/integrations/unsplash.rst:65 +msgid "**As a non-Odoo Online user**, you won't be able to register for a production Unsplash key and will be limited to your test key that has a 50 Unsplash requests per hour restriction." +msgstr "" + +#: ../../content/applications/general/iot.rst:8 +msgid "Internet of Things (IoT)" +msgstr "" + +#: ../../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/iot/config/connect.rst:3 +msgid "Connect an IoT box to Odoo" +msgstr "" + +#: ../../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/iot/config/connect.rst:11 +msgid "`IoT Box FAQ `_" +msgstr "" + +#: ../../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/iot/config/connect.rst:-1 +msgid "The Internet of Things (IoT) app on the Odoo database." +msgstr "" + +#: ../../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/iot/config/connect.rst:-1 +msgid "Connecting an IoT box to the Odoo database." +msgstr "" + +#: ../../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/iot/config/connect.rst:-1 +msgid "Connection steps for a wired connection or WiFi connection." +msgstr "" + +#: ../../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 :doc:`flashed ` with the most up-to-date disk image." +msgstr "" + +#: ../../content/applications/general/iot/config/connect.rst:46 +msgid "Ethernet connection" +msgstr "" + +#: ../../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/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/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/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/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/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/iot/config/connect.rst:79 +msgid "WiFi connection" +msgstr "" + +#: ../../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/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/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/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/iot/config/connect.rst:-1 +msgid "WiFi networks available on the computer." +msgstr "" + +#: ../../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/iot/config/connect.rst:-1 +msgid "Enter the server token into the IoT box." +msgstr "" + +#: ../../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/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/iot/config/connect.rst:-1 +msgid "Configuring the WiFi for the IoT box." +msgstr "" + +#: ../../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/iot/config/connect.rst:-1 +msgid "The IoT box has been successfully configured on the Odoo database." +msgstr "" + +#: ../../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/iot/config/connect.rst:139 +msgid "Manually connecting the IoT box using the token" +msgstr "" + +#: ../../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/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/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/flash_sdcard.rst:3 +msgid "Flashing the SD card" +msgstr "" + +#: ../../content/applications/general/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." +msgstr "" + +#: ../../content/applications/general/iot/config/flash_sdcard.rst:10 +msgid "Upgrade from the IoT box home page" +msgstr "" + +#: ../../content/applications/general/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)." +msgstr "" + +#: ../../content/applications/general/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." +msgstr "" + +#: ../../content/applications/general/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`." +msgstr "" + +#: ../../content/applications/general/iot/config/flash_sdcard.rst:-1 +msgid "IoT box software upgrade in the IoT Box Home Page." +msgstr "" + +#: ../../content/applications/general/iot/config/flash_sdcard.rst:34 +msgid "Upgrade with Etcher Software" +msgstr "" + +#: ../../content/applications/general/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." +msgstr "" + +#: ../../content/applications/general/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." +msgstr "" + +#: ../../content/applications/general/iot/config/flash_sdcard.rst:44 +msgid "Then download the version-specific :abbr:`IoT (Internet of Things)` image from `nightly `_." +msgstr "" + +#: ../../content/applications/general/iot/config/flash_sdcard.rst:47 +msgid "The following are image versions on the `nightly `_ website with their corresponding Odoo database version:" +msgstr "" + +#: ../../content/applications/general/iot/config/flash_sdcard.rst:50 +msgid "Odoo V16 --> iotbox-latest.zip" +msgstr "" + +#: ../../content/applications/general/iot/config/flash_sdcard.rst:51 +msgid "Odoo V15 --> iotboxv21_10.zip" +msgstr "" + +#: ../../content/applications/general/iot/config/flash_sdcard.rst:52 +msgid "Odoo V14 --> iotboxv21_04.zip" +msgstr "" + +#: ../../content/applications/general/iot/config/flash_sdcard.rst:53 +msgid "Odoo V13 --> iotboxv20_10.zip" +msgstr "" + +#: ../../content/applications/general/iot/config/flash_sdcard.rst:55 +msgid "The images should be downloaded and extracted to a convenient file location." +msgstr "" + +#: ../../content/applications/general/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." +msgstr "" + +#: ../../content/applications/general/iot/config/flash_sdcard.rst:-1 +msgid "Balena's Etcher software dashboard." +msgstr "" + +#: ../../content/applications/general/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 `_." +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 +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 +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 will need to be re-flashed to update the image (see :doc:`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 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/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/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/measurement_tool.rst:66 +#: ../../content/applications/general/iot/devices/printer.rst:70 +msgid ":doc:`../../../inventory_and_mrp/manufacturing/quality_control/quality_control_points`" +msgstr "" + +#: ../../content/applications/general/iot/devices/camera.rst:59 +#: ../../content/applications/general/iot/devices/measurement_tool.rst:67 +#: ../../content/applications/general/iot/devices/printer.rst:71 +msgid ":doc:`../../../inventory_and_mrp/manufacturing/quality_control/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:90 +#: ../../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:5 +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:9 +msgid "Find the list of supported devices here: `Supported devices `_." +msgstr "" + +#: ../../content/applications/general/iot/devices/measurement_tool.rst:13 +msgid "Connect with universal serial bus (USB)" +msgstr "" + +#: ../../content/applications/general/iot/devices/measurement_tool.rst:15 +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:24 +msgid "Connect with bluetooth" +msgstr "" + +#: ../../content/applications/general/iot/devices/measurement_tool.rst:26 +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:35 +msgid "Link a measurement tool to a quality control point in the manufacturing process" +msgstr "" + +#: ../../content/applications/general/iot/devices/measurement_tool.rst:37 +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:41 +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:45 +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:48 +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:56 +#: ../../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:61 +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:70 +msgid "Link a measurement tool to a work center in the Manufacturing app" +msgstr "" + +#: ../../content/applications/general/iot/devices/measurement_tool.rst:72 +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:76 +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:82 +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:86 +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:67 +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 @@ -2860,185 +5359,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:11 -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:13 -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:22 -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:31 -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:40 -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:43 -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:44 -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:51 -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:53 -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:62 -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:65 -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:66 -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:68 -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:69 -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:70 -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:73 -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:75 -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:83 -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:85 -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:87 -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:88 -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:89 -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:90 -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:91 -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:92 -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:94 -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:102 -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:105 -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:112 -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:116 -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:125 -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:128 -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:131 -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:132 -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:156 +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 @@ -3097,261 +5763,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 @@ -3533,6 +6014,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 "" @@ -3552,3070 +6037,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:`SIP Login` / :guilabel:`Browser's Extension`: (Axivox) :guilabel:`SIP username`" -msgstr "" - -#: ../../content/applications/general/voip/axivox/axivox_config.rst:50 -msgid ":guilabel:`Handset Extension`: SIP external phone extension" -msgstr "" - -#: ../../content/applications/general/voip/axivox/axivox_config.rst:51 -msgid ":guilabel:`SIP Password`: (Axivox) :guilabel:`SIP Password`" -msgstr "" - -#: ../../content/applications/general/voip/axivox/axivox_config.rst:52 -msgid ":guilabel:`Mobile call`: method to make calls on a mobile device" -msgstr "" - -#: ../../content/applications/general/voip/axivox/axivox_config.rst:53 -msgid ":guilabel:`OnSIP authorization User`: (Axivox) :guilabel:`SIP username`" -msgstr "" - -#: ../../content/applications/general/voip/axivox/axivox_config.rst:54 -msgid ":guilabel:`Always Redirect to Handset`: option to always transfer phone calls to handset" -msgstr "" - -#: ../../content/applications/general/voip/axivox/axivox_config.rst:55 -msgid ":guilabel:`Reject All Incoming Calls`: option to reject all incoming calls" -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:135 -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:146 -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 `VoIP OnSIP`." -msgstr "" - -#: ../../content/applications/general/voip/onsip.rst:24 -msgid "Next, install 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:`SIP Login` / :guilabel:`Browser's Extension` = OnSIP :guilabel:`Username`" -msgstr "" - -#: ../../content/applications/general/voip/onsip.rst:77 -msgid ":guilabel:`OnSIP authorization User` = OnSIP :guilabel:`Auth Username`" -msgstr "" - -#: ../../content/applications/general/voip/onsip.rst:78 -msgid ":guilabel:`Handset Extension` = OnSIP :guilabel:`Ext.` (extension without the `x`)" -msgstr "" - -#: ../../content/applications/general/voip/onsip.rst:79 -msgid ":guilabel:`SIP Password` = OnSIP :guilabel:`SIP Password`" -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, click :guilabel:`Save` on the user form in Odoo to save the configurations." -msgstr "" - -#: ../../content/applications/general/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/general/voip/onsip.rst:96 -msgid "Additional setup and troubleshooting steps can be found on `OnSIP's knowledge base `_." -msgstr "" - -#: ../../content/applications/general/voip/onsip.rst:100 -msgid "Incoming calls" -msgstr "" - -#: ../../content/applications/general/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/general/voip/onsip.rst:105 -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:113 -msgid ":doc:`voip_widget`" -msgstr "" - -#: ../../content/applications/general/voip/onsip.rst:116 -#: ../../content/applications/general/voip/voip_widget.rst:32 -msgid "Troubleshooting" -msgstr "" - -#: ../../content/applications/general/voip/onsip.rst:119 -msgid "Missing parameters" -msgstr "" - -#: ../../content/applications/general/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/general/voip/onsip.rst:-1 -msgid "Missing parameter message in the Odoo VoIP widget." -msgstr "" - -#: ../../content/applications/general/voip/onsip.rst:129 -msgid "Incorrect number" -msgstr "" - -#: ../../content/applications/general/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 :guilabel:`+ (plus)` sign, followed by the international country code." -msgstr "" - -#: ../../content/applications/general/voip/onsip.rst:139 -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:150 -msgid "OnSIP on mobile phone" -msgstr "" - -#: ../../content/applications/general/voip/onsip.rst:152 -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:155 -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:159 -msgid ":doc:`devices_integrations`" -msgstr "" - -#: ../../content/applications/general/voip/onsip.rst:160 -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:`➣ (paper airplane)` 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 new file mode 100644 index 000000000..5a4c0ffe0 --- /dev/null +++ b/locale/sources/hr.pot @@ -0,0 +1,5728 @@ +# 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 15.0\n" +"Report-Msgid-Bugs-To: \n" +"POT-Creation-Date: 2024-03-20 10:19+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/hr.rst:5 +msgid "Human resources" +msgstr "" + +#: ../../content/applications/hr/attendances.rst:8 +msgid "Attendances" +msgstr "" + +#: ../../content/applications/hr/attendances.rst:10 +msgid "**Odoo Attendances** functions as a time clock. Employees check in and check out of work, while managers can see who is available at any given time." +msgstr "" + +#: ../../content/applications/hr/attendances.rst:14 +msgid "`Odoo Tutorials: Attendances `_" +msgstr "" + +#: ../../content/applications/hr/attendances/hardware.rst:3 +msgid "Hardware" +msgstr "" + +#: ../../content/applications/hr/attendances/hardware.rst:6 +msgid "Kiosk management" +msgstr "" + +#: ../../content/applications/hr/attendances/hardware.rst:8 +msgid "A kiosk is a self-service station that allows employees to check in and check out for work shifts." +msgstr "" + +#: ../../content/applications/hr/attendances/hardware.rst:10 +msgid "There are two ways to set up a kiosk:" +msgstr "" + +#: ../../content/applications/hr/attendances/hardware.rst:12 +msgid "**Laptop and desktop PC**" +msgstr "" + +#: ../../content/applications/hr/attendances/hardware.rst:14 +msgid "Running a kiosk in a web browser is the cheapest and most flexible option. You can print employee badges with any thermal or inkjet printer compatible with your web browser." +msgstr "" + +#: ../../content/applications/hr/attendances/hardware.rst:17 +msgid "**Tablet and mobile phone (Android or iOS)**" +msgstr "" + +#: ../../content/applications/hr/attendances/hardware.rst:19 +msgid "Tablets and mobile phones take up much less space, and their touchscreens are easy to use. Consider putting them in a secure stand at the front desk or mounting them securely on a wall." +msgstr "" + +#: ../../content/applications/hr/attendances/hardware.rst:23 +msgid "We recommend using an iPad together with the `Heckler Design WindFall Stand `_" +msgstr "" + +#: ../../content/applications/hr/attendances/hardware.rst:27 +msgid "RFID key fob readers" +msgstr "" + +#: ../../content/applications/hr/attendances/hardware.rst:29 +msgid "Employees can scan personal RFID key fobs with an RFID reader to manage check-ins and check-outs quickly and easily." +msgstr "" + +#: ../../content/applications/hr/attendances/hardware.rst:-1 +msgid "An RFID key fob is placed on an RFID reader" +msgstr "" + +#: ../../content/applications/hr/attendances/hardware.rst:38 +msgid "We recommend using the `Neuftech USB RFID Reader `_." +msgstr "" + +#: ../../content/applications/hr/attendances/hardware.rst:41 +#: ../../content/applications/hr/attendances/hardware.rst:57 +msgid "An IoT box is **not** required." +msgstr "" + +#: ../../content/applications/hr/attendances/hardware.rst:44 +msgid "Barcode scanners" +msgstr "" + +#: ../../content/applications/hr/attendances/hardware.rst:46 +msgid "Employees can scan the barcode on their employee badges to manage check-ins and check-outs quickly and easily. The kiosk mode works with most USB barcode scanners connected directly to a computer. Bluetooth barcode scanners are also supported natively." +msgstr "" + +#: ../../content/applications/hr/attendances/hardware.rst:51 +msgid "We recommend using the `Honeywell product line `_. If the barcode scanner is connected directly to a computer, it must be configured to use the computer's keyboard layout." +msgstr "" + +#: ../../content/applications/hr/employees.rst:7 +msgid "Employees" +msgstr "" + +#: ../../content/applications/hr/employees.rst:9 +msgid "Odoo *Employees* organizes a company's employee records, contracts, and departments." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:3 +msgid "Add a new employee" +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:5 +msgid "When a new employee is hired, the first step is to create a new employee form. Starting in the :menuselection:`Employees` app dashboard, click the :guilabel:`Create` button to create a new employee form. Fill out the required information (underlined in bold) and any additional details, then click :guilabel:`Save`." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:-1 +msgid "Create a new employee card." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:15 +msgid "The current company phone number and name is populated in the :guilabel:`Work Phone` and :guilabel:`Company` fields." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:19 +msgid "General information" +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:22 +#: ../../content/applications/hr/payroll/contracts.rst:39 +#: ../../content/applications/hr/payroll/payslips.rst:51 +msgid "Required fields" +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:24 +msgid ":guilabel:`Name`: Enter the employee's name." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:25 +msgid ":guilabel:`Company`: Select the company from the drop-down menu that the new employee is hired by, or create a new company by typing the name in the field." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:33 +#: ../../content/applications/hr/payroll/contracts.rst:66 +#: ../../content/applications/hr/payroll/payslips.rst:91 +#: ../../content/applications/hr/recruitment.rst:736 +msgid "Optional fields" +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:35 +msgid ":guilabel:`Photo`: In the top right image box of the employee card, click on the :guilabel:`✏️ (pencil)` edit icon to select a photo to upload." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:37 +msgid ":guilabel:`Job Position`: Enter the employee's job position title." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:38 +msgid "Tags: Click on a tag in the drop-down menu to add any tags applicable to the employee. Any tag can be created in this field by typing it in. Once created, the new tag is available for all employee cards. There is no limit to the amount of tags that can be added." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:41 +msgid "Work Contact Information: Enter the employees :guilabel:`Work Mobile`, :guilabel:`Work Phone`, :guilabel:`Work Email`, and/or :guilabel:`Company` name." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:43 +msgid ":guilabel:`Department`: Select the employee's department from the drop-down menu." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:44 +msgid ":guilabel:`Manager`: Select the employee's manager from the drop-down menu." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:45 +msgid ":guilabel:`Coach`: Select the employee's coach from the drop-down menu." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:48 +msgid "After a :guilabel:`Manager` is selected, if the :guilabel:`Coach` field is blank, the selected manager automatically populates the :guilabel:`Coach` field." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:52 +msgid "To make edits to the selected :guilabel:`Department`, :guilabel:`Manager`, :guilabel:`Coach`, or :guilabel:`Company`, click the :guilabel:`External Link` button next to the respective selection. The :guilabel:`External Link` button opens the selected form, allowing for modifications. Click :guilabel:`Save` after any edits are made." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:58 +msgid "Additional information tabs" +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:61 +msgid "Resumé tab" +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:64 +msgid "Resumé" +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:66 +msgid "Next, enter the employee's work history in the :guilabel:`Resumé` tab. Each resumé line must be entered individually. Click :guilabel:`Create a New Entry`, and the :guilabel:`Create Resumé lines` form appears. Enter the following information for each entry." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:-1 +msgid "Add information for the previous work experience in this form." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:74 +msgid ":guilabel:`Title`: Type in the title of the previous work experience." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:75 +msgid ":guilabel:`Type`: From the drop-down menu, select either :guilabel:`Experience`, :guilabel:`Education`, :guilabel:`Internal Certification`, :guilabel:`Internal Training`, or type in a new entry." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:78 +msgid ":guilabel:`Display Type`: Select either :guilabel:`Classic`, :guilabel:`Certification`, or :guilabel:`Course` from the drop-down menu." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:80 +msgid ":guilabel:`Date Start` and :guilabel:`Date End`: Enter the start and end dates for the work experience. To select a date, use the :guilabel:`< (left)` and :guilabel:`> (right)` arrow icons to scroll to the desired month, then click on the day to select it." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:83 +msgid ":guilabel:`Description`: Enter any relevant details in the field." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:85 +msgid "Once all the information is entered, click the :guilabel:`Save & Close` button if there is only one entry to add, or click the :guilabel:`Save & New` button to save the current entry and create another resumé line." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:90 +msgid "After the new employee form is saved, the current position and company is automatically added to the :guilabel:`Resumé` tab as :guilabel:`Experience`, with the end date listed as :guilabel:`Current`." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:95 +msgid "Skills" +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:97 +msgid "An employee's skills can be entered in the :guilabel:`Resumé` tab in the same manner a resumé line is created. Click the :guilabel:`Create a New Entry` button under :guilabel:`Skills` and a :guilabel:`Create Skills` form appears. Fill in the information on the form." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:-1 +msgid "Create a new skill for the employee." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:105 +msgid ":guilabel:`Skill Type`: Select a :ref:`skill type ` by clicking the radio button next to the skill type." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:107 +msgid ":guilabel:`Skill`: The corresponding skills associated with the selected :guilabel:`Skill Type` appear in a drop-down menu. For example, selecting :guilabel:`Language` as the :guilabel:`Skill Type` presents a variety of languages to select from under the :guilabel:`Skills` field. Select the appropriate pre-configured skill, or type in a new one." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:111 +msgid ":guilabel:`Skill Level`: Pre-defined skill levels associated with the selected :guilabel:`Skill Type` appear in a drop-down menu. Select a skill level, then the progress bar automatically displays the pre-defined progress for that skill level. Skill levels and progress can be modified in the :guilabel:`Skill Level` pop-up form, which is accessed via the :guilabel:`External Link` button next to :guilabel:`Skill Level` field." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:117 +msgid "Once all the information is entered, click the :guilabel:`Save & Close` button if there is only one entry to add, or click the :guilabel:`Save & New` button to save the current entry and create another skill." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:121 +msgid "To delete any line from the :guilabel:`Resumé` tab, click the :guilabel:`🗑️ (trash can)` icon to delete the entry. Add a new line by clicking the :guilabel:`Add` button next to the corresponding section." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:128 +msgid "Skill types" +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:130 +msgid "In order to add a skill to an employee's form, the :guilabel:`Skill Types` must be configured. Go to :menuselection:`Employees app --> Configuration --> Skill Types` to view the currently configured skill types and create new skill types. Click :guilabel:`Create` and a new :guilabel:`Skill Type` form appears. Fill out all the details and then click :guilabel:`Save`. Repeat this for all the skill types needed." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:136 +msgid ":guilabel:`Skill Type`: Enter the name of the skill type. This should be somewhat generic, since the specific skills listed will be housed under this category." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:138 +msgid ":guilabel:`Skills`: Click :guilabel:`Add a line` and enter the information for the new skill, then repeat for all other needed skills." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:140 +msgid ":guilabel:`Levels`: Click :guilabel:`Add a line` and a :guilabel:`Create Levels` form appears. Enter the name of the level, and assign a percentage (0-100) for that level. Click :guilabel:`Save & New` to save the entry and add another level, or click :guilabel:`Save & Close` to save the level and close the form." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:146 +msgid "To add a math skill set, enter `Math` in the :guilabel:`Name` field. Next, in the :guilabel:`Skills` field, enter `Algebra`, `Calculus`, and `Trigonometry`. Last, in the :guilabel:`Levels` field enter `Beginner`, `Intermediate`, and `Expert`, with the :guilabel:`Progress` listed as `25`, `50`, and `100`, respectively. Then, either click :guilabel:`Save & Close` or :guilabel:`Save & New`." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:0 +msgid "Add new math skills and levels with the skill types form." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:159 +msgid "Work information tab" +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:161 +msgid "The :guilabel:`Work Information` tab is where the employee's specific job related information is housed. Their working schedule, various roles, who approves their specific requests (time off, timesheets, and expenses), and specific work location details are listed here. Enter the following information for the new employee." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:166 +msgid ":guilabel:`Location`: Select the :guilabel:`Work Address` and :guilabel:`Work Location` from the corresponding drop-down menus. The work address :guilabel:`External Link` button opens up the selected company form in a window, and allows for editing. The :guilabel:`Work Location` is the specific location details, such as a floor or building. If a new work location is needed, add the location by typing it in the field." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:171 +msgid ":guilabel:`Approvers`: Using the drop-down menus, select the users responsible for approving :guilabel:`Time Off`, :guilabel:`Expenses`, and :guilabel:`Timesheets` for the employee. The :guilabel:`External Link` button opens a form with the approver's :guilabel:`Name`, :guilabel:`Email Address`, :guilabel:`Company`, :guilabel:`Phone`, and :guilabel:`Mobile` fields. These can be modified, if needed. Click :guilabel:`Save` after making any edits." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:176 +msgid ":guilabel:`Schedule`: Select the :guilabel:`Working Hours` and :guilabel:`Timezone` (both required) for the employee. The :guilabel:`External Link` button opens up a detailed view of the specific daily working hours. Working hours can be modified or deleted here. Click :guilabel:`Save` to save any changes." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:180 +msgid ":guilabel:`Planning`: The :guilabel:`Planning` section affects the *Planning* app, and will only appear if the *Planning* app is installed. Click on a planning role from the drop-down menu for both the :guilabel:`Default Planning Role` and the :guilabel:`Planning Roles` fields to add a role. There is no limit to the amount of :guilabel:`Planning Roles` that can be selected for an employee, but there can only be one :guilabel:`Default Planning Role`. The default is the *typical* role that the employee performs, where the :guilabel:`Planning Roles` are *all* the specific roles the employee is able to perform." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:0 +msgid "Add the work information to the Work Information tab." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:193 +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. 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:198 +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 "" + +#: ../../content/applications/hr/employees/new_employee.rst:201 +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:203 +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:208 +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:211 +msgid "Each individual working time is company-specific, so for multi-company databases, each company needs to have its own working hours set." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:214 +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. To add or modify a working time, go to the :menuselection:`Payroll app --> Configuration --> Working Times`, and add a new working time or edit an existing one." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:219 +msgid "After the new working time is created, set the working hours for the employee." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:222 +msgid "Private information tab" +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:224 +msgid "No information in the :guilabel:`Private Information` tab is required, 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:229 +msgid "Here, the employee's :guilabel:`Private Contact`, :guilabel:`Marital Status`, :guilabel:`Emergency Contact`, :guilabel:`Education`, :guilabel:`Citizenship`, :guilabel:`Dependant`, and :guilabel:`Work Permit` information is entered. Fields are entered either using a drop-down menu, clicking a check box, or typing in the information." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:234 +msgid ":guilabel:`Private Contact`: Enter the personal :guilabel:`Address` for the employee. The selection can be made with the drop-down menu. If the information is not available, type in the name for the new address. To edit the new address, click the :guilabel:`External Link` button to open the address form. On the address form, enter the necessary details, then click :guilabel:`Save`" +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:240 +msgid "Some other information in the :guilabel:`Private Contact` section may auto-populate, if the address is already listed in the drop-down menu." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:243 +msgid "Next, enter the employee's :guilabel:`Email` address and :guilabel:`Phone` number in the corresponding fields." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:246 +msgid "Select the employee's preferred :guilabel:`Language` from the drop-down menu." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:248 +msgid "Enter the employee's :guilabel:`Bank Account Number` using the drop-down menu. 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` for appears. Fill in the information, then click :guilabel:`Save`." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:253 +msgid "Finally, 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:256 +msgid ":guilabel:`Marital Status`: Select either :guilabel:`Single`, :guilabel:`Married`, :guilabel:`Legal Cohabitant`, :guilabel:`Widower`, or :guilabel:`Divorced` from the drop-down menu." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:259 +msgid ":guilabel:`Emergency`: Type in the name and phone number of the employee's emergency contact." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:260 +msgid ":guilabel:`Education`: Select the highest level of education completed by the employee from the :guilabel:`Certificate Level` drop-down menu. Options include :guilabel:`Graduate`, :guilabel:`Bachelor`, :guilabel:`Master`, :guilabel:`Doctor`, or :guilabel:`Other`. 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:264 +msgid ":guilabel:`Citizenship`: This section houses all the information relevant to the citizenship of the employee. Some selections use a drop-down menu, as does the :guilabel:`Nationality (Country)`, :guilabel:`Gender`, and :guilabel:`Country of Birth` sections. The :guilabel:`Date of Birth` uses a calendar module 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. Type in the information for the :guilabel:`Identification No`, :guilabel:`Passport No`, and :guilabel:`Place of Birth` fields." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:272 +msgid ":guilabel:`Dependant`: If the employee has any children, enter the :guilabel:`Number of Children` in the field." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:274 +msgid ":guilabel:`Work Permit`: If the employee has a work permit, enter the information in this section. Type in the :guilabel:`Visa No` and/or :guilabel:`Work Permit No` in the corresponding fields. Using the calendar module, select the :guilabel:`Visa Expire Date` and/or the :guilabel:`Work Permit Expiration Date` to enter the expiration date(s). If available, upload a digital copy of the 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:-1 +msgid "Add the private information to the Private Information tab." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:288 +msgid "HR settings tab" +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:290 +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:294 +msgid ":guilabel:`Status`: Select an :guilabel:`Employee Type` and, if applicable, a :ref:`Related User `, with the drop-down menus." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:296 +msgid ":guilabel:`Payroll`: Select the :guilabel:`Current Contract` and :guilabel:`Job Position` from the drop-down menus. If applicable, enter the :guilabel:`Registration Number` in this section." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:298 +msgid ":guilabel:`Previous Employer`: This section appears only for Belgian companies, and will not be visible for other locations. These are days that will be paid to the new employee. Enter any :guilabel:`Simple Holiday Pay to Recover`, :guilabel:`Number of Days to recover`, and :guilabel:`Recovered Simple Holiday Pay` from a previous employer, for both N and N-1 categories." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:302 +msgid ":guilabel:`Previous Occupations`: This section appears ony for Belgian companies, and will not be visible for other locations. Click :guilabel:`Add a line` to enter information for each previous occupation. Enter the number of :guilabel:`Months`, the :guilabel:`Amount`, and the :guilabel:`Occupational Rate` in the corresponding fields. Click the :guilabel:`🗑️ (trash can)` icon to delete a line." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:307 +msgid ":guilabel:`Attendance/Point of Sale`: The employee's :guilabel:`Badge ID` and :guilabel:`PIN Code` 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:310 +msgid ":guilabel:`Application Settings`: If applicable, enter the :guilabel:`Fleet Mobility Card` number. Enter the employee's cost per hour 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>`. This value affects the manufacturing costs for a product, if the value of the manufactured product is not a fixed amount." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:-1 +msgid "Enter any information prompted in the HR Settings tab for the employee." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:323 +msgid "Employees do not also need to be users. An employee does **not** count towards 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:327 +msgid "In the :guilabel:`Related User` field, type in the name of the user to add, then click :guilabel:`Create and Edit...`. A :guilabel:`Create: Related User` form appears. Type in the :guilabel:`Name`, :guilabel:`Email Address`, and then select the :guilabel:`Company` from the drop-down menu. Click :guilabel:`Save` after the information is entered. Once the record is saved, the new user appears in the :guilabel:`Related User` field." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:334 +msgid "Documents" +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:336 +msgid "All documents associated with an employee are stored in the *Documents* app. The number of documents associated with the employee appear in the :guilabel:`Documents` smart button on the employee form. Click on the smart button, and all the documents appear. For more information on the *Documents* app, refer to the :doc:`Documents documentation `." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:-1 +msgid "All uploaded documents associated with the employee appear in the documents smart-button." +msgstr "" + +#: ../../content/applications/hr/fleet.rst:7 +msgid "Fleet" +msgstr "" + +#: ../../content/applications/hr/fleet.rst:9 +msgid "Odoo *Fleet* organizes all the vehicles, contracts, and repairs of all the vehicles." +msgstr "" + +#: ../../content/applications/hr/fleet/configuration.rst:3 +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 `." +msgstr "" + +#: ../../content/applications/hr/fleet/configuration.rst:13 +#: ../../content/applications/hr/payroll.rst:18 +msgid "Settings" +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." +msgstr "" + +#: ../../content/applications/hr/fleet/configuration.rst:-1 +msgid "Settings available for the Fleet application." +msgstr "" + +#: ../../content/applications/hr/fleet/configuration.rst:24 +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." +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." +msgstr "" + +#: ../../content/applications/hr/fleet/configuration.rst:35 +msgid "To access all contracts, navigate to :menuselection:`Fleet app --> Fleet --> Contracts` and all contracts appear in the list. Click on a :guilabel:`Contract` to view it." +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." +msgstr "" + +#: ../../content/applications/hr/fleet/configuration.rst:45 +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." +msgstr "" + +#: ../../content/applications/hr/fleet/configuration.rst:54 +msgid "If the :guilabel:`New Vehicle Request` limit is set to 20 vehicles, and there are 25 vehicles available, an employee would not be able to request a new vehicle. If there are only 10 cars available, then the employee would be able to request a new vehicle." +msgstr "" + +#: ../../content/applications/hr/fleet/configuration.rst:61 +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`." +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)." +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 +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`." +msgstr "" + +#: ../../content/applications/hr/fleet/configuration.rst:87 +msgid "Vehicle Models" +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." +msgstr "" + +#: ../../content/applications/hr/fleet/configuration.rst:97 +msgid "Preconfigured Models" +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:" +msgstr "" + +#: ../../content/applications/hr/fleet/configuration.rst:102 +msgid "AUDI" +msgstr "" + +#: ../../content/applications/hr/fleet/configuration.rst:102 +msgid "BMW" +msgstr "" + +#: ../../content/applications/hr/fleet/configuration.rst:102 +msgid "Eddy Merckx" +msgstr "" + +#: ../../content/applications/hr/fleet/configuration.rst:102 +msgid "Mercedes" +msgstr "" + +#: ../../content/applications/hr/fleet/configuration.rst:102 +msgid "Opel" +msgstr "" + +#: ../../content/applications/hr/fleet/configuration.rst:104 +msgid "A1" +msgstr "" + +#: ../../content/applications/hr/fleet/configuration.rst:104 +msgid "Serie 1" +msgstr "" + +#: ../../content/applications/hr/fleet/configuration.rst:104 +msgid "SanRemo76" +msgstr "" + +#: ../../content/applications/hr/fleet/configuration.rst:104 +msgid "Class A" +msgstr "" + +#: ../../content/applications/hr/fleet/configuration.rst:104 +msgid "Agilia" +msgstr "" + +#: ../../content/applications/hr/fleet/configuration.rst:106 +msgid "A3" +msgstr "" + +#: ../../content/applications/hr/fleet/configuration.rst:106 +msgid "Serie 3" +msgstr "" + +#: ../../content/applications/hr/fleet/configuration.rst:106 +msgid "Class B" +msgstr "" + +#: ../../content/applications/hr/fleet/configuration.rst:106 +msgid "Ampera" +msgstr "" + +#: ../../content/applications/hr/fleet/configuration.rst:108 +msgid "A4" +msgstr "" + +#: ../../content/applications/hr/fleet/configuration.rst:108 +msgid "Serie 5" +msgstr "" + +#: ../../content/applications/hr/fleet/configuration.rst:108 +msgid "Class C" +msgstr "" + +#: ../../content/applications/hr/fleet/configuration.rst:108 +msgid "Antara" +msgstr "" + +#: ../../content/applications/hr/fleet/configuration.rst:110 +msgid "A5" +msgstr "" + +#: ../../content/applications/hr/fleet/configuration.rst:110 +msgid "Serie 6" +msgstr "" + +#: ../../content/applications/hr/fleet/configuration.rst:110 +msgid "Class CL" +msgstr "" + +#: ../../content/applications/hr/fleet/configuration.rst:110 +msgid "Astra" +msgstr "" + +#: ../../content/applications/hr/fleet/configuration.rst:112 +msgid "A6" +msgstr "" + +#: ../../content/applications/hr/fleet/configuration.rst:112 +msgid "Serie 7" +msgstr "" + +#: ../../content/applications/hr/fleet/configuration.rst:112 +msgid "Class CLS" +msgstr "" + +#: ../../content/applications/hr/fleet/configuration.rst:112 +msgid "AstraGTC" +msgstr "" + +#: ../../content/applications/hr/fleet/configuration.rst:114 +msgid "A7" +msgstr "" + +#: ../../content/applications/hr/fleet/configuration.rst:114 +msgid "Serie Hybrid" +msgstr "" + +#: ../../content/applications/hr/fleet/configuration.rst:114 +msgid "Class E" +msgstr "" + +#: ../../content/applications/hr/fleet/configuration.rst:114 +msgid "Combo Tour" +msgstr "" + +#: ../../content/applications/hr/fleet/configuration.rst:116 +msgid "A8" +msgstr "" + +#: ../../content/applications/hr/fleet/configuration.rst:116 +msgid "Serie M" +msgstr "" + +#: ../../content/applications/hr/fleet/configuration.rst:116 +msgid "Class GL" +msgstr "" + +#: ../../content/applications/hr/fleet/configuration.rst:116 +msgid "Corsa" +msgstr "" + +#: ../../content/applications/hr/fleet/configuration.rst:118 +msgid "Q3" +msgstr "" + +#: ../../content/applications/hr/fleet/configuration.rst:118 +msgid "Serie X" +msgstr "" + +#: ../../content/applications/hr/fleet/configuration.rst:118 +msgid "Class GLK" +msgstr "" + +#: ../../content/applications/hr/fleet/configuration.rst:118 +msgid "Insignia" +msgstr "" + +#: ../../content/applications/hr/fleet/configuration.rst:120 +msgid "Q5" +msgstr "" + +#: ../../content/applications/hr/fleet/configuration.rst:120 +msgid "Serie Z4" +msgstr "" + +#: ../../content/applications/hr/fleet/configuration.rst:120 +msgid "Class M" +msgstr "" + +#: ../../content/applications/hr/fleet/configuration.rst:120 +msgid "Meriva" +msgstr "" + +#: ../../content/applications/hr/fleet/configuration.rst:122 +msgid "Q7" +msgstr "" + +#: ../../content/applications/hr/fleet/configuration.rst:122 +msgid "Class R" +msgstr "" + +#: ../../content/applications/hr/fleet/configuration.rst:122 +msgid "Mokka" +msgstr "" + +#: ../../content/applications/hr/fleet/configuration.rst:124 +msgid "TT" +msgstr "" + +#: ../../content/applications/hr/fleet/configuration.rst:124 +msgid "Class S" +msgstr "" + +#: ../../content/applications/hr/fleet/configuration.rst:124 +msgid "Zafira" +msgstr "" + +#: ../../content/applications/hr/fleet/configuration.rst:126 +msgid "Class SLK" +msgstr "" + +#: ../../content/applications/hr/fleet/configuration.rst:126 +msgid "Zafira Tourer" +msgstr "" + +#: ../../content/applications/hr/fleet/configuration.rst:128 +msgid "Class SLS" +msgstr "" + +#: ../../content/applications/hr/fleet/configuration.rst:134 +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." +msgstr "" + +#: ../../content/applications/hr/fleet/configuration.rst:142 +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." +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." +msgstr "" + +#: ../../content/applications/hr/fleet/configuration.rst:171 +#: ../../content/applications/hr/payroll.rst:147 +msgid "Salary" +msgstr "" + +#: ../../content/applications/hr/fleet/configuration.rst:174 +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." +msgstr "" + +#: ../../content/applications/hr/fleet/configuration.rst:179 +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 +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." +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." +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)." +msgstr "" + +#: ../../content/applications/hr/fleet/configuration.rst:213 +msgid ":guilabel:`Horsepower`: enter the vehicle's horsepower in this field." +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." +msgstr "" + +#: ../../content/applications/hr/fleet/configuration.rst:221 +msgid "Vendors tab" +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." +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." +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." +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" +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 `." +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." +msgstr "" + +#: ../../content/applications/hr/fleet/configuration.rst:254 +msgid "Add a new model category" +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." +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." +msgstr "" + +#: ../../content/applications/hr/fleet/configuration.rst:-1 +msgid "List view of the models in the fleet." +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:3 +msgid "Create new vehicles" +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:5 +msgid "Odoo's *Fleet* app manages all vehicles and the accompanying documentation that comes with vehicle maintenance and driver's records." +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:8 +msgid "All vehicles are organized on the main :guilabel:`Fleet` dashboard. Each vehicle has its own *vehicle form*, which is displayed as a card in the kanban view, according to it's status. Every vehicle form is displayed in its current corresponding kanban stage. The default stages are :guilabel:`New Request`, :guilabel:`To Order`, :guilabel:`Ordered`, :guilabel:`Registered`, :guilabel:`Downgraded`, :guilabel:`Reserve`, and :guilabel:`Waiting List`." +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:14 +msgid "To add a new vehicle to the fleet, click the :guilabel:`Create` button, and a blank vehicle form loads. Enter the vehicle information in the vehicle form, then click :guilabel:`Save`." +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:18 +msgid "Vehicle form fields" +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:20 +msgid ":guilabel:`Model`: select the vehicle's model from the drop-down menu. If the model is not listed, type in the model name and click either :guilabel:`Create` or :guilabel:`Create and Edit`." +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:22 +msgid ":guilabel:`License Plate`: enter the vehicle's license plate number in this field." +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:23 +msgid ":guilabel:`Tags`: select any tags from the drop-down menu, or type in a new tag. There is no limit on the amount of tags that can be selected." +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:27 +msgid "The :guilabel:`Model` is the only required field on the new vehicle form. When a model is selected, other fields will appear on the vehicle form, and relevant information will auto-populate fields that apply to the model. If some of the fields do not appear, this may indicate there is no model selected." +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:33 +msgid "Driver section" +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:35 +msgid "This section of the vehicle form relates to the person who is currently driving the car, as well as any plans for a change in the driver in the future, and when." +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:38 +msgid ":guilabel:`Driver`: select the driver from the drop-down menu, or type in a new driver and click either :guilabel:`Create` or :guilabel:`Create and Edit`." +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:40 +msgid ":guilabel:`Mobility Card`: if the selected driver has a mobility card listed on their employee card in the *Employees* application, the mobility card number will appear in this field. If there is no mobility card listed and one should be added, :ref:`edit the employee card ` in the *Employees* application." +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:44 +msgid ":guilabel:`Future Driver`: if the next driver for the vehicle is known, select the next driver from the drop-down menu, or type in the next driver and click either :guilabel:`Create` or :guilabel:`Create and Edit`." +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:47 +msgid ":guilabel:`Plan To Change Car`: if the current driver set for this vehicle plans to change their vehicle, either because they are waiting on a new vehicle that is being ordered, or this is a temporary vehicle assignment and they know which vehicle they will be driving next, check this box. If the current driver does not plan to change their vehicle and use this current vehicle, do not check this box." +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:52 +msgid ":guilabel:`Assignment Date`: select the date the vehicle will be available for another driver using the drop-down calendar. Select the date by navigating to the correct month and year using the :guilabel:`⬅️ (left arrow)` and :guilabel:`➡️ (right arrow)` icons, then click on the specific day. If this field is blank, this indicates the vehicle is currently available and can be reassigned to another driver. If it is populated, the vehicle will not be available to assign to another driver until the date entered." +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:60 +msgid "A driver does **not** have to be an employee, but a driver must be listed in the *Contacts* application. When creating a new driver, the driver is added to the *Contacts* application, not the *Employees* application." +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:65 +msgid "Vehicle section" +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:67 +msgid "This section of the vehicle form relates to the physical vehicle, it's various properties, when it was added, where it is located, and who is managing it." +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:70 +msgid ":guilabel:`Immatriculation Date`: select the date the vehicle is acquired using the drop-down calendar." +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:72 +msgid ":guilabel:`Cancellation Date`: select the date the vehicle lease will expire, or when the vehicle will be no longer available, using the drop-down calendar." +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:74 +msgid ":guilabel:`Chassis Number`: enter the chassis number in the field. This is known in some countries as the :abbr:`VIN (Vehicle Identification Number)` number." +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:76 +msgid ":guilabel:`Last Odometer`: enter the last known odometer reading in the number field. Using the drop-down menu next to the number field, select whether the odometer reading is in kilometers :guilabel:`(km)` or miles :guilabel:`(mi)`." +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:79 +msgid ":guilabel:`Fleet Manager`: select the fleet manager from the drop-down menu, or type in a new fleet manager and click either :guilabel:`Create` or :guilabel:`Create and Edit`." +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:81 +msgid ":guilabel:`Location`: type in the location for the vehicle in the field. The most common scenario for when this field would be populated is if a company has several office locations. The typical office location where the vehicle is located would be the location entered." +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:84 +msgid ":guilabel:`Company`: select the company that the vehicle will be used for and associated with from the drop-down menu, or type in a new company and click either :guilabel:`Create` or :guilabel:`Create and Edit`." +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:89 +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 +msgid "The new vehicle form, showing the vehicle tax section." +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:97 +msgid "Tax Info tab" +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:100 +msgid "Fiscality" +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:102 +msgid ":guilabel:`Horsepower Taxation`: enter the amount that is taxed based on the size of the vehicles 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/new_vehicle.rst:105 +msgid ":guilabel:`Disallowed Expense Rate`: this is the amount of non-deductible expenses for the vehicle. This amount is not counted towards any deductions on a tax return or as an allowable expense when calculating taxable income. It is recommended to check with the accounting department to ensure the value(s) entered are correct." +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:110 +msgid ":guilabel:`Start Date`: enter the :guilabel:`Start Date` and :guilabel:`(%) Percentage` for when the :guilabel:`Disallowed Expense Rate` value goes into effect. Click :guilabel:`Add a line` to enter a date. Click on the blank line to display a calendar. Select the date by navigating to the correct month and year using the :guilabel:`⬅️ (left arrow)` and :guilabel:`➡️ (right arrow)` icons, then click on the specific day. Enter the percentage that is disallowed in the :guilabel:`% (percent)` field to the right of the date. The percentage should be entered in an XX.XX format. Repeat this for all entries needed." +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:119 +msgid "Contract" +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:121 +msgid ":guilabel:`First Contract Date`: select the start date for the vehicle's first contract using the drop-down calendar. Typically this is the day the vehicle is purchased or leased." +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:123 +msgid ":guilabel:`Catalog Value (VAT Incl.)`: enter the MSRP (Manufacturer's Suggested Retail Price) for the vehicle at the time of purchase or lease." +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:125 +msgid ":guilabel:`Purchase Value`: enter the purchase price or the value of the lease for the vehicle." +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:126 +msgid ":guilabel:`Residual Value`: enter the current value of the vehicle." +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:129 +msgid "The values listed above will affect the accounting department. It is recommended to check with the accounting department for more information and/or assistance with these values." +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:137 +msgid "Model tab" +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:139 +msgid "If the model for the new vehicle is already configured in the database, the :guilabel:`Model` tab will be populated with the corresponding information. If the model is not already in the database and the :guilabel:`Model` tab needs to be configured, :ref:`configure the new vehicle model `." +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:144 +msgid "Check the information in the :guilabel:`Model` tab to ensure it is accurate. For example, the color of the vehicle, or whether there is a trailer hitch installed or not, are examples of information that may need updating." +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:153 +msgid "Note tab" +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:155 +msgid "Enter any notes for the vehicle in this section." +msgstr "" + +#: ../../content/applications/hr/fleet/service.rst:3 +msgid "Services" +msgstr "" + +#: ../../content/applications/hr/fleet/service.rst:5 +msgid "To properly maintain a fleet of vehicles, regular maintenance as well as periodic repairs are needed. Scheduling repairs and managing services for an entire fleet is necessary to ensure all vehicles are in good working order when they are needed." +msgstr "" + +#: ../../content/applications/hr/fleet/service.rst:10 +msgid "Create a service record" +msgstr "" + +#: ../../content/applications/hr/fleet/service.rst:12 +msgid "To log a service, go to the main services dashboard by navigating to :menuselection:`Fleet app --> Fleet --> Services`. Click :guilabel:`Create` and a service form appears. Fill in the information on the form and click :guilabel:`Save`. The only two fields that are required to be populated are :guilabel:`Service Type` and :guilabel:`Vehicle`." +msgstr "" + +#: ../../content/applications/hr/fleet/service.rst:17 +msgid "The fields are:" +msgstr "" + +#: ../../content/applications/hr/fleet/service.rst:19 +msgid ":guilabel:`Description`: enter in a short description of the service." +msgstr "" + +#: ../../content/applications/hr/fleet/service.rst:20 +msgid ":guilabel:`Service Type`: select the type of service performed from the drop-down menu, or type in a new type of service and click either :guilabel:`Create` or :guilabel:`Create & Edit...`. This list is not pre-configured in Odoo. When creating a fleet and logging a service, the types of service need to be created." +msgstr "" + +#: ../../content/applications/hr/fleet/service.rst:24 +msgid ":guilabel:`Date`: using the calendar module, select the date the service was provided or is scheduled to be performed. Navigate to the desired month using the left and right arrow icons, then click on the date to select it." +msgstr "" + +#: ../../content/applications/hr/fleet/service.rst:27 +msgid ":guilabel:`Cost`: enter the cost of the service." +msgstr "" + +#: ../../content/applications/hr/fleet/service.rst:28 +msgid ":guilabel:`Vendor`: select the vendor who performed the service from the drop-down menu. If the vendor has not already been entered in the system, type in the vendor name and click either :guilabel:`Create` to add them, or :guilabel:`Create & Edit...` to create the vendor and edit the vendor form. The vendor form allows for other details aside form the name to be entered, such as contact information." +msgstr "" + +#: ../../content/applications/hr/fleet/service.rst:33 +msgid ":guilabel:`Vehicle`: select the vehicle that was serviced from the drop-down menu. When the vehicle is selected, the :guilabel:`Driver` field is populated, and the unit of measure for the :guilabel:`Mileage` field appears." +msgstr "" + +#: ../../content/applications/hr/fleet/service.rst:36 +msgid ":guilabel:`Driver`: the current driver listed for the selected vehicle is populated when the :guilabel:`Vehicle` is selected. If the driver needs to be changed, another driver can be selected from the drop-down menu." +msgstr "" + +#: ../../content/applications/hr/fleet/service.rst:39 +msgid ":guilabel:`Odometer Value`: enter the odometer reading when the service was done. The units of measure will either be in kilometers (:guilabel:`km`) or miles (:guilabel:`mi`). When the :guilabel:`Vehicle` is selected, the units of measure is populated. This comes from the vehicle form. To change from kilometers to miles, or vice versa, click the :guilabel:`External Link` button next to the vehicle selected in the :guilabel:`Vehicle` field. Change the unit of measure, then click :guilabel:`Save`. the unit of measure will be updated in the :guilabel:`Odometer Value` field." +msgstr "" + +#: ../../content/applications/hr/fleet/service.rst:46 +msgid ":guilabel:`Notes`: enter any notes for the repair in the notes tab at the bottom of the service form." +msgstr "" + +#: ../../content/applications/hr/fleet/service.rst:-1 +msgid "Enter the information for a new service. The required fields are Service Type and Vehicle." +msgstr "" + +#: ../../content/applications/hr/fleet/service.rst:54 +msgid "List of services" +msgstr "" + +#: ../../content/applications/hr/fleet/service.rst:56 +msgid "To view all services logged in the database, including old and new requests, go to :menuselection:`Fleet application --> Fleet --> Services`. All services appear in a list view, including all the details for each service." +msgstr "" + +#: ../../content/applications/hr/fleet/service.rst:60 +msgid "Each service listed displays the following information:" +msgstr "" + +#: ../../content/applications/hr/fleet/service.rst:62 +msgid ":guilabel:`Date`: the date service or repair was performed or is requested to be performed." +msgstr "" + +#: ../../content/applications/hr/fleet/service.rst:63 +msgid ":guilabel:`Description`: a short description of the specific type of service or repair performed to clarify the specific service." +msgstr "" + +#: ../../content/applications/hr/fleet/service.rst:65 +msgid ":guilabel:`Service Type`: the service or repair performed. This is selected from a list of services that must be configured." +msgstr "" + +#: ../../content/applications/hr/fleet/service.rst:67 +msgid ":guilabel:`Vehicle`: the specific vehicle the service was performed on." +msgstr "" + +#: ../../content/applications/hr/fleet/service.rst:68 +msgid ":guilabel:`Driver`: who the current driver is for the vehicle." +msgstr "" + +#: ../../content/applications/hr/fleet/service.rst:69 +msgid ":guilabel:`Vendor`: the specific vendor who performed the service or repair." +msgstr "" + +#: ../../content/applications/hr/fleet/service.rst:70 +msgid ":guilabel:`Cost`: the total cost for the service or repair." +msgstr "" + +#: ../../content/applications/hr/fleet/service.rst:71 +msgid ":guilabel:`Notes`: any information associated with the service or repair that is documented to add clarification." +msgstr "" + +#: ../../content/applications/hr/fleet/service.rst:73 +msgid ":guilabel:`Stage`: the status of the service or repair. Options are :guilabel:`New`, :guilabel:`Running`, :guilabel:`Canceled`, or :guilabel:`Done`." +msgstr "" + +#: ../../content/applications/hr/fleet/service.rst:-1 +msgid "The full list of services in the Odoo database." +msgstr "" + +#: ../../content/applications/hr/fleet/service.rst:81 +msgid "View services" +msgstr "" + +#: ../../content/applications/hr/fleet/service.rst:83 +msgid "It is recommended to view the list of services in one of several pre-configured ways to better view the information presented. In the top right corner of the list, there are several icons that when clicked, sort the data in different ways." +msgstr "" + +#: ../../content/applications/hr/fleet/service.rst:-1 +msgid "The icons in the top right corner than cn be clicked to present the information in\n" +"different ways." +msgstr "" + +#: ../../content/applications/hr/fleet/service.rst:93 +msgid "List view" +msgstr "" + +#: ../../content/applications/hr/fleet/service.rst:95 +msgid "The default view of the services is the list view. This presents all the services in chronological order, from oldest to newest, in a list." +msgstr "" + +#: ../../content/applications/hr/fleet/service.rst:98 +msgid "The information can be sorted by any column. At the top of each column, hover over the column name. An arrow appears to the right of the name. Click the arrow to sort the data by that specific column." +msgstr "" + +#: ../../content/applications/hr/fleet/service.rst:101 +msgid "The default sorting is descending alphabetical order (A to Z). Click the arrow again to reverse the order, and go in reverse alphabetical order (Z to A). The one exception to this sorting is the default :guilabel:`Date` column, which sorts the information in chronological order (January to December) instead of alphabetical order." +msgstr "" + +#: ../../content/applications/hr/fleet/service.rst:107 +#: ../../content/applications/hr/recruitment.rst:33 +msgid "Kanban view" +msgstr "" + +#: ../../content/applications/hr/fleet/service.rst:109 +msgid "To view services by their stage, click on the :guilabel:`Kanban icon`, which is the second icon in the top right, and appears as four black squares in a cube." +msgstr "" + +#: ../../content/applications/hr/fleet/service.rst:112 +msgid "All the services with the same status appear in the corresponding column, from :guilabel:`Running` to :guilabel:`Cancelled`. To change the status of a service, simply click and drag the service card to the desired stage." +msgstr "" + +#: ../../content/applications/hr/fleet/service.rst:117 +msgid "Graph view" +msgstr "" + +#: ../../content/applications/hr/fleet/service.rst:119 +msgid "Another way to view the data is in a graph. To view the graph, click the :guilabel:`Graph icon`, which is the third icon in the top right, and appears as a small graph." +msgstr "" + +#: ../../content/applications/hr/fleet/service.rst:122 +msgid "The graph displays the information in a graph where the X axis represents the :guilabel:`Date` and the Y axis represents the :guilabel:`Cost`. Each column represents a single month, and then is further organized by vehicle. Each vehicle is represented by a different color, and each month's bar is divided by each vehicle." +msgstr "" + +#: ../../content/applications/hr/fleet/service.rst:128 +msgid "Pivot view" +msgstr "" + +#: ../../content/applications/hr/fleet/service.rst:130 +msgid "The final way to view the service data is in a spreadsheet pivot table. Click on the :guilabel:`Pivot icon`, which is the last icon in the top right, and appears as a small spreadsheet." +msgstr "" + +#: ../../content/applications/hr/fleet/service.rst:133 +msgid "The data presented in the table shows the cost of each service or repair. The rows represent the vendors, and each vehicle that was serviced by them appears beneath each vendor. The column represent the different service types performed." +msgstr "" + +#: ../../content/applications/hr/fleet/service.rst:137 +msgid "The table can be inserted in a spreadsheet or downloaded. To add the pivot table to a spreadsheet in Odoo, click :guilabel:`Insert In Spreadsheet` and a pop-up appears. Select the spreadsheet the data should be added to from the drop-down menu, and click :guilabel:`Confirm`. The spreadsheet then loads on the screen. The spreadsheets are stored in Odoo's *Documents* application. To download the table in an `xlsx` format, click the :guilabel:`Download` icon." +msgstr "" + +#: ../../content/applications/hr/fleet/service.rst:-1 +msgid "Download the pivot table to an xlsx file, or insert the data in a spreadsheet in Odoo's\n" +"Documents application." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:6 +#: ../../content/applications/hr/payroll/reporting.rst:39 +msgid "Payroll" +msgstr "" + +#: ../../content/applications/hr/payroll.rst:8 +msgid "Odoo *Payroll* is used to process work entries and create payslips for employees, including both regular pay and commission. Payroll works in conjunction with other Odoo apps, such as *Employees*, *Timesheets*, *Time Off*, and *Attendances*." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:12 +msgid "The *Payroll* app helps ensure there are no issues or conflicts when validating work entries, handles country-specific localizations to ensure that payslips follow local rules and taxes, and allows for salary assignments. Payroll configuration is critical to ensure accurate and timely processing of payslips." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:20 +msgid "To access the *Settings*, go to :menuselection:`Payroll --> Configuration --> Settings`. Whether or not payslips are posted in accounting, and whether SEPA payments are created, is selected here." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:23 +msgid "The :guilabel:`Settings` screen is where localization settings are configured. *Localizations* are country-specific settings pre-configured in Odoo at the creation of the database, and account for all taxes, fees, and allowances for that particular country. The :guilabel:`Localization` section of the :guilabel:`Settings` includes a detailed view of all benefits provided to employees." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:-1 +msgid "Settings available for Payroll." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:32 +msgid "Any country-specific localizations are set up in the :guilabel:`Localization` section of the :guilabel:`Settings` screen. All localization items are pre-populated when the country is specified during the creation of the database. It is not recommended to alter the localization settings unless specifically required." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:40 +#: ../../content/applications/hr/payroll/work_entries.rst:3 +msgid "Work entries" +msgstr "" + +#: ../../content/applications/hr/payroll.rst:42 +msgid "A *work entry* is an individual record on an employee's timesheet. Work entries can be configured to account for all types of work and time off, such as :guilabel:`Attendance`, :guilabel:`Sick Time Off`, :guilabel:`Training`, or :guilabel:`Public Holiday`." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:47 +msgid "Work entry types" +msgstr "" + +#: ../../content/applications/hr/payroll.rst:49 +msgid "When creating a work entry in the *Payroll* application, or when an employee enters information in the *Timesheets* application, a :guilabel:`Work Entry Type` needs to be selected. The list of :guilabel:`Work Entry Types` is automatically created based on localization settings set in the database." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:54 +msgid "To view the current work entry types available, go to :menuselection:`Payroll --> Configuration --> Work Entry Types`." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:57 +msgid "Each work entry type has a code to aid in the creation of payslips, and ensure all taxes and fees are correctly entered." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:-1 +msgid "List of all work entry types currently available." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:65 +msgid "New work entry type" +msgstr "" + +#: ../../content/applications/hr/payroll.rst:67 +msgid "To create a new work entry type, click the :guilabel:`Create` button. Enter the information on the form:" +msgstr "" + +#: ../../content/applications/hr/payroll.rst:70 +msgid ":guilabel:`Work Entry Type Name`: The name should be short and descriptive, such as `Sick Time` or `Public Holiday`." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:72 +msgid ":guilabel:`Code`: This code appears with the work entry type on timesheets and payslips. Since the code is used in conjunction with the *Accounting* application, it is advised to check with the accounting department for a code to use." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:75 +msgid ":guilabel:`DMFA Code`: This code is used to identify DMFA entries on a corresponding DMFA report, and is for Belgian-based companies only." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:77 +msgid ":guilabel:`Color`: Select a color for the particular work entry type." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:78 +msgid ":guilabel:`Rounding`: The rounding method determines how timesheet entries are displayed on the payslip." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:81 +msgid ":guilabel:`No Rounding`: A timesheet entry is not modified." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:82 +msgid ":guilabel:`Half Day`: A timesheet entry is rounded to the closest half day amount." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:83 +msgid ":guilabel:`Day`: A timesheet entry is rounded to the closest full day amount." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:86 +msgid "If the working time is set to an 8-hour work day (40-hour work week), and an employee enters a time of 5.5 hours on a timesheet, and :guilabel:`Rounding` is set to :guilabel:`No Rounding`, the entry remains 5.5 hours. If :guilabel:`Rounding` is set to :guilabel:`Half Day`, the entry is changed to 4 hours. If it is set to :guilabel:`Day`, it is changed to 8 hours." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:91 +msgid ":guilabel:`Unpaid in Structures Types`: If the work entry is for unpaid work, specify which pay structure the work entry can apply to from the drop-down menu." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:93 +msgid "Check boxes: If any of the items in the list apply to the work entry, check off the box by clicking it. If :guilabel:`Time Off` is checked off, a :guilabel:`Time Off Type` field appears. This field has a drop-down menu to select the specific type of time off, or a new type of time off can be entered." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:-1 +msgid "New work entry type form." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:105 +msgid "Working times" +msgstr "" + +#: ../../content/applications/hr/payroll.rst:107 +msgid "To view the currently configured working times, go to :menuselection:`Payroll --> Configuration --> Working Times`. The working times that are available for an employee's contracts and work entries are found in this list." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:111 +msgid "Working times are company-specific. Each company must identify each type of working time they use. For example, an Odoo database containing multiple companies that use a standard 40-hour work week needs to have a separate working time entry for each company that uses the 40-hour standard work week." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:-1 +msgid "All working times currently set up in the database." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:121 +msgid "New working time" +msgstr "" + +#: ../../content/applications/hr/payroll.rst:123 +msgid "To create a new working time, click the :guilabel:`Create` button. Enter the information on the form." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:-1 +msgid "New working type form." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:130 +msgid "The fields are auto-populated for a regular 40-hour work week but can be modified. First, change the name of the working time by modifying the text in the :guilabel:`Name` field. Next, make any adjustments to the days and times that apply to the new working time." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:134 +msgid "In the :guilabel:`Working Hours` tab, modify the :guilabel:`Day of Week`, :guilabel:`Day Period`, and :guilabel:`Work Entry Type` selections by clicking on the drop-down menus in each column and making the desired selection. The :guilabel:`Work From` and :guilabel:`Work To` columns are modified by typing in the time." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:140 +msgid "The :guilabel:`Work From` and :guilabel:`Work To` times must be in a 24-hour format. For example, `2:00 PM` would be entered as `14:00`." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:143 +msgid "If the working time should be in a two-week configuration, click the :guilabel:`Switch To 2 Week Calendar` button. This creates entries for an :guilabel:`Even week` and an :guilabel:`Odd week`." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:152 +msgid "Structure types" +msgstr "" + +#: ../../content/applications/hr/payroll.rst:154 +msgid "In Odoo, an employee's payslip is based on *structures* and *structure types*, which both affect how an employee enters timesheets. Each structure type is an individual set of rules for processing a timesheet entry, which consists of different structures nested within it. Structure types define how often an employee gets paid, the working hours, and if wages are based on a salary (fixed) or how many hours the employee worked (varied)." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:160 +msgid "For example, a structure type could be `Employee`, and that structure type could have two different structures in it: a `Regular Pay` structure which includes all the separate rules for processing regular pay, as well as a structure for an `End of Year Bonus` which includes the rules only for the end of year bonus. Both the `Regular Pay` structure and `End of Year Bonus` structure are structures within the `Employee` structure type." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:166 +msgid "The different structure types can be seen by going to :menuselection:`Payroll --> Configuration --> Structure Types`." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:169 +msgid "There are two default structure types configured in Odoo: *Employee* and *Worker*. Typically, *Employee* is used for salaried employees, which is why the wage type is *Monthly Fixed Wage*, and *Worker* is typically used for employees paid by the hour, so the wage type is *Hourly Wage*." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:-1 +msgid "List of all structure types." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:177 +msgid "Click the :guilabel:`Create` button to make a new structure type. Most fields are pre-populated, but all fields can be edited. Once the fields are edited, click the :guilabel:`Save` button to save the changes, or click :guilabel:`Discard` to delete the entry." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:-1 +msgid "New structure type box." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:186 +msgid "Structures" +msgstr "" + +#: ../../content/applications/hr/payroll.rst:188 +msgid "*Salary structures* are the different ways an employee gets paid within a specific *structure*, and are specifically defined by various rules." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:191 +msgid "The amount of structures a company needs for each structure type depends on how many different ways employees are paid, and how their pay is calculated. For example, a common structure that could be useful to add may be a `Bonus`." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:195 +msgid "To view all the various structures for each structure type, go to :menuselection:`Payroll --> Configuration --> Structures`." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:-1 +msgid "All available salary structures." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:202 +msgid "Each :ref:`structure type ` lists the various structures associated with it. Each structure contains a set of rules that define it." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:205 +msgid "Click on a structure to view its :guilabel:`Salary Rules`. These rules are what calculate the payslip for the employee." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:-1 +msgid "Salary structure details for Regular Pay." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:213 +#: ../../content/applications/hr/time_off.rst:191 +msgid "Rules" +msgstr "" + +#: ../../content/applications/hr/payroll.rst:215 +msgid "Each structure has a set of *salary rules* to follow for accounting purposes. These rules are configured by the localization, and affect the *Accounting* application, so modifications to the default rules, or the creation of new rules, should only be done when necessary." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:219 +msgid "To view all the rules, go to :menuselection:`Payroll app --> Configuration --> Rules`. Click on a structure (such as :guilabel:`Regular Pay`) to view all the rules." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:-1 +msgid "Rules for each salary structure type." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:226 +msgid "To make a new rule, click :guilabel:`Create`. A new rule form appears. Enter the information in the fields, then click :guilabel:`Save`." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:-1 +msgid "Enter the information for the new rule." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:233 +msgid "The required fields for a rule are:" +msgstr "" + +#: ../../content/applications/hr/payroll.rst:235 +msgid ":guilabel:`Name`: Enter a name for the rule." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:236 +msgid ":guilabel:`Category`: Select a category the rule applies to from the drop-down menu, or enter a new one." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:238 +msgid ":guilabel:`Code`: Enter a code to be used for this new rule. It is recommended to coordinate with the accounting department for a code as this will affect them." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:240 +msgid ":guilabel:`Salary Structure`: Select a salary structure the rule applies to from the drop-down menu, or enter a new one." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:242 +msgid ":guilabel:`Condition Based on`: In the :guilabel:`General` tab, select from the drop-down menu whether the rule is :guilabel:`Always True` (always applies), a :guilabel:`Range` (applies to a specific range, which is entered beneath the selection), or a :guilabel:`Python Expression` (the code is entered beneath the selection)." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:246 +msgid ":guilabel:`Amount Type`: In the :guilabel:`General` tab, select from the drop-down menu whether the amount is a :guilabel:`Fixed Amount`, a :guilabel:`Percentage (%)`, or a :guilabel:`Python Code`. Depending on what is selected, the fixed amount, percentage, or Python code needs to be entered next." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:252 +msgid "Rule parameters" +msgstr "" + +#: ../../content/applications/hr/payroll.rst:255 +msgid "Currently, the :guilabel:`Rule Parameters` feature found inside the :menuselection:`Payroll app --> Configuration` menu is still in development and only serves a specific use case for Belgian markets. The documentation will be updated when this section has matured to more markets." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:260 +msgid "Other input types" +msgstr "" + +#: ../../content/applications/hr/payroll.rst:262 +msgid "When creating payslips, it is sometimes necessary to add other entries for specific circumstances, like expenses, reimbursements, or deductions. These other inputs can be configured by going to :menuselection:`Payroll --> Configuration --> Other Input Types`." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:-1 +msgid "Other input types for payroll." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:270 +msgid "To create a new input type, click the :guilabel:`Create` button. Enter the :guilabel:`Description`, the :guilabel:`Code`, and which structure it applies to in the :guilabel:`Availability in Structure` field. If the input type applies to all structures, leave the :guilabel:`Availability in Structure` field blank. Click the :guilabel:`Save` button to save the changes, or click :guilabel:`Discard` to delete the entry." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:-1 +msgid "Create a new Input Type." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:281 +msgid "Salary package configurator" +msgstr "" + +#: ../../content/applications/hr/payroll.rst:283 +msgid "The various options under the :guilabel:`Salary Package Configurator` section of the :menuselection:`Payroll --> Configuration` menu all affect an employee's potential salary. These sections (:guilabel:`Advantages`, :guilabel:`Personal Info`, and :guilabel:`Resume`) specify what benefits can be offered to an employee in their salary package." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:288 +msgid "Depending on what information an employee enters (such as deductions, dependents, etc.), their salary is adjusted accordingly. When an applicant applies for a job on the company website, the sections under :guilabel:`Salary Package Configurator` directly affect what the applicant sees, and what is populated as the applicant enters information." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:294 +msgid "Advantages" +msgstr "" + +#: ../../content/applications/hr/payroll.rst:296 +msgid "When offering potential employees a position, there can be certain *advantages* set in Odoo in addition to the salary to make the offer more appealing (such as extra time off, access to a company car, reimbursement for a phone or internet, etc.)." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:300 +msgid "To see the advantages, go to :menuselection:`Payroll --> Configuration --> Advantages`. Advantages are grouped by :guilabel:`Structure type`." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:-1 +msgid "Settings available for payroll." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:307 +msgid "To make a new advantage, click the :guilabel:`Create` button. Enter the information in the fields, then click the :guilabel:`Save` button to save the changes, or click :guilabel:`Discard` to delete the entry." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:-1 +msgid "List of advantages employee's can have." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:315 +msgid "The required fields for an advantage are:" +msgstr "" + +#: ../../content/applications/hr/payroll.rst:317 +msgid ":guilabel:`Name`: Enter the name for the advantage." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:318 +msgid ":guilabel:`Advantage Field`: Select from the drop-down menu what field in the payslip this advantage appears under." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:320 +msgid ":guilabel:`Advantage Type`: Select from the drop-down menu what type of advantage the benefit is. Select from :guilabel:`Monthly Benefit in Kind`, :guilabel:`Monthly Advantages in Net`, :guilabel:`Monthly Advantages in Cash`, or :guilabel:`Yearly Advantages in Cash`." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:323 +msgid ":guilabel:`Salary Structure Type`: Select from the drop-down menu which salary structure type this advantage applies to." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:327 +msgid "Personal info" +msgstr "" + +#: ../../content/applications/hr/payroll.rst:329 +msgid "Every employee in Odoo has an *employee card* that includes all of their personal information, resume, work information, and documents. To view an employee's card, go to the main :menuselection:`Payroll` app dashboard, and click on the employee's card, or go to :menuselection:`Payroll --> Employees --> Employees` and click on the employee's card. Employee cards can also be viewed by going to the :menuselection:`Employees` app." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:336 +msgid "An employee card can be thought of as an employee personnel file." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:338 +msgid "The *Personal Information* section lists all of the fields that are available to enter on the employee's card. To access this section, go to :menuselection:`Payroll --> Configuration --> Personal Info`." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:-1 +msgid "Personal information that appear on employee cards to enter." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:346 +msgid "To edit an entry, select it from the list. Then, click the :guilabel:`Edit` button, and modify the entry. When done, click :guilabel:`Save` or :guilabel:`Discard` to save the information or cancel the edits." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:-1 +msgid "New personal information entry." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:354 +msgid "The two most important fields on the personal info form are :guilabel:`Is Required` and :guilabel:`Display Type`. Checking the :guilabel:`Is Required` box makes the field mandatory on the employee's card." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:358 +msgid "The :guilabel:`Display Type` drop-down menu allows for the information to be entered in a variety of ways, from a :guilabel:`Text` box, to a customizable :guilabel:`Radio` button, a :guilabel:`Checkbox`, a :guilabel:`Document`, and more." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:362 +msgid "Once the information is entered, click the :guilabel:`Save` button to save the entry." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:365 +msgid "Resume" +msgstr "" + +#: ../../content/applications/hr/payroll.rst:368 +msgid "Currently, the :guilabel:`Resume` feature found inside the :menuselection:`Payroll app --> Configuration` menu is still in development and only serves a specific use case for Belgian markets. The documentation will be updated when this section has matured to more markets." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:3 +msgid "Contracts" +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/productivity/documents` and :doc:`/applications/productivity/sign` documentation." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:15 +msgid "To view the employee contracts, go to the :menuselection:`Payroll app --> Employees --> Contracts` from the top menu. All employee contracts, and their current contract status, are displayed in a default kanban view. The default view displays both running contracts and contracts that need action. Expired and canceled contracts are hidden in the default view." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:-1 +msgid "Contracts dashboard view showing running contracts and contracts with issues." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:25 +msgid "The list of contracts in the *Payroll* application matches the list of contracts in the *Employees* application. The default contracts view in the *Payroll* application displays running contracts and contracts needing attention, while the default contracts view in the *Employees* application displays all contracts in a kanban view, organized by their stage, regardless of status. All contracts can be viewed by changing the filters." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:32 +msgid "Create a new contract" +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:34 +msgid "In order for an employee to be paid, an active contract is required. If a new contract is needed, click the :guilabel:`Create` button on the contracts dashboard. A contract form appears where the information can be entered. Required fields are underlined in bold." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:-1 +msgid "New contract form to be filled in when creating a new contract." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:45 +msgid ":guilabel:`Contact Reference`: Type in the name or title for the contract, such as `John Smith Contract`." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:47 +msgid ":guilabel:`Company`: Select the company the contract applies to by clicking on the drop-down menu. A new company can be created by typing the name in the field, then clicking either :guilabel:`Create` to create the new company, or :guilabel:`Create and Edit` to create the new company and edit the company details." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:51 +msgid ":guilabel:`Salary Structure Type`: Select one of the salary structure types from the drop-down menu. The default salary structure types are :guilabel:`Employee` or :guilabel:`Worker`. A new salary structure type can be created by typing the name in the field." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:54 +msgid ":guilabel:`Start Date`: The date the contract starts. Choose a date by clicking on the drop-down menu, navigating to the correct month and year by using the :guilabel:`< > (arrow)` icons, then clicking on the :guilabel:`date`." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:57 +msgid ":guilabel:`Working Schedule`: Select one of the working schedules from the drop-down menu." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:60 +msgid "The :guilabel:`Working Schedule` drop-down menu displays all the working times for the selected :guilabel:`Company`. To modify or add to this list, go to :menuselection:`Payroll --> Configuration --> Working Times` and either :guilabel:`Create` a new working time or click on an existing working time and edit it by clicking :guilabel:`Edit`." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:68 +msgid ":guilabel:`Employee`: Name of the employee that the contract applies to." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:69 +msgid ":guilabel:`Department`: The department the contract applies to." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:70 +msgid ":guilabel:`Job Position`: The specific job position the contract applies to." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:71 +msgid ":guilabel:`Contract Type`: Choose from :guilabel:`CDI`, :guilabel:`CDD`, or :guilabel:`PFI` from the drop-down menu." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:74 +msgid ":guilabel:`CDI` is an open-ended contract with only a start date but no end date." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:75 +msgid ":guilabel:`CDD` is a contract with both a start date and an end date." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:76 +msgid ":guilabel:`PFI` is a Belgian-specific contract used when hiring employees that need training, and covers the training period specifically." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:79 +msgid ":guilabel:`End Date`: If the contract has a specific end date, click the drop-down menu, navigate to the correct month and year using the arrow icons, then click on the date." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:81 +msgid ":guilabel:`HR Responsible`: If there is a specific person in HR that is responsible for the contract, select the person from the drop-down menu." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:83 +msgid ":guilabel:`Analytic Account`: This field allows a link between the contract and a specific analytic account for accounting purposes." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:87 +msgid "Contract details" +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:89 +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 +msgid "Contract details in optional tabs for a new contract." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:96 +msgid ":guilabel:`Contract Template`: Select a pre-existing contract template from the drop-down menu. Contract templates are typically created through the *Recruitment* application." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:98 +msgid ":guilabel:`New Contract Document Template`: Select a contract from the drop-down menu to be modified for this new employee contract." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:100 +msgid ":guilabel:`Contract Update Document Template`: Select a contract from the drop-down menu if the employee has an existing contract that requires updating." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:102 +msgid ":guilabel:`Notes`: The notes field is a text field where any notes for the employee contract can be entered for future reference." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:106 +msgid "Modifying a contract" +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:108 +msgid "Click the :guilabel:`External Link` button at the end of each line to open the corresponding contract template and make any changes." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:115 +msgid "A pop-up window appears with all the contract details. Modify the fields for the contract as needed." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:-1 +msgid "Edit the details for the contract." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:121 +msgid ":guilabel:`Tags`: Select any tags associated with the contract." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:122 +msgid ":guilabel:`Signed Document Workspace`: This is where the signatures are stored. Choose a pre-configured workspace or create a new one." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:124 +msgid ":guilabel:`Signed Document Tags`: Select or create any tags associated only with the signed contract as opposed to the original unsigned contract." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:126 +msgid ":guilabel:`Redirect Link`: Enter a redirect link for the employee to access the contract. A redirect link takes the user from one URL to another, in this case, to the newly updated contract specifically written for them." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:129 +msgid ":guilabel:`Who can Sign`: Select either :guilabel:`All Users` or :guilabel:`On Invitation`." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:131 +msgid ":guilabel:`All Users`: Any user in the organization can sign the contract." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:132 +msgid ":guilabel:`On Invitation`: Only users selected in this field can sign the contract." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:134 +msgid ":guilabel:`Invited Users`: Select the person(s) that can sign the document." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:135 +msgid ":guilabel:`Document`: The attached document can be replaced by clicking the :guilabel:`✏️ (pencil)` icon. A pop-up window appears so another document can be selected for upload. The file must be a PDF. To remove the document, click the :guilabel:`🗑️ (trash can)` icon." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:139 +msgid "Once the edits are complete, click the :guilabel:`Save` button. All the information for the selected contract template populates the fields in the :guilabel:`Salary Information` tab. Any additional tabs, such as :guilabel:`Personal Documents`, appears if applicable." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:144 +msgid "Salary information" +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:-1 +msgid "Optional tabs for a new contract." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:150 +msgid "This section is where the specific salary details are defined. This section is country-specific, so depending on where the company is located, these fields may vary." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:153 +msgid "Enter the amount in the various fields, or check a box to apply a benefit. Some options that can be entered here include :guilabel:`Meal Vouchers`, :guilabel:`Fuel Card`, :guilabel:`Internet`, :guilabel:`Paid Time Off`, etc." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:157 +msgid "Some fields may be automatically filled in based off of the contracts selected in the :guilabel:`Contract Details` tab." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:161 +msgid "Attachment of salary" +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:163 +msgid "Any automatic deductions or allocations for an employee, such as child support payments and wage garnishments, are referred to as a *salary attachment*. This section is where all of these deductions or allocations are set." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:167 +msgid "To add a new deduction, click :guilabel:`Add a line`. Type in a description for the allocation under :guilabel:`Description`." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:-1 +msgid "Enter a new line for each type of garnishment." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:174 +msgid "Select the :guilabel:`Garnished Type` from the drop-down menu. Choose from:" +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:176 +msgid ":guilabel:`Attachment of Salary`: Any payments taken out towards something that is *not* child support. Typically any garnishments such as lawsuit payments, payments toward taxes owed, etc." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:178 +msgid ":guilabel:`Assignment of Salary`: Any deduction that is not required but voluntary, such as a pre-tax allocation to a college savings account." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:180 +msgid ":guilabel:`Child Support`: Any payments taken out specifically for child support." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:182 +msgid "Enter the start and end dates the entry applies to. Click on the drop-down menu under :guilabel:`From` and :guilabel:`To`, navigate to the correct month and year by using the :guilabel:`< > (arrow)` icons, then click on the :guilabel:`date`." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:186 +msgid "Last, enter the :guilabel:`Amount` that each payslip pays towards the entry." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:188 +msgid "To delete a line, click the :guilabel:`🗑️ (trash can)` icon at the end of the line." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:191 +msgid "Save and send the contract" +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:193 +msgid "Once a contract has been created and/or modified, save the contract by clicking the :guilabel:`Save` button. Next, the contract must be sent to the employee to be signed." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:196 +msgid "Click on one of the following buttons to send the contract to the employee:" +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:-1 +msgid "Send the contract to the employee via one of the buttons." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:202 +msgid ":guilabel:`Generate Simulation Link`: This option is for Belgian companies only. Clicking this opens a pop-up window that contains the basic information from the contract as well as a link for the contract when using the salary configurator. Click :guilabel:`Send Offer` to send an email to the employee so they can sign the contract." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:0 +msgid "Sends a link to the employee for the contract." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:212 +msgid "In order to send a contract using the :guilabel:`Generate Simulation Link`, there must be a signature field in the contract PDF being sent to the employee so they can sign it." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:215 +msgid ":guilabel:`Signature Request`: Click this and a pop-up window appears where an email can be typed to the employee. Select the document, such as a contract, NDA, or Homeworking Policy, from the drop-down menu, and fill out the email section. Click :guilabel:`Send` when the email is ready to be sent." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:0 +msgid "Request a signature for the contract via email." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:224 +msgid ":guilabel:`Credit Time`: This option is for Belgian companies only. When clicked, a pop-up window appears that allows for the changing of working times, and can compute time off." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:3 +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." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:10 +msgid "The :guilabel:`Payslips` drop-down header of the :menuselection:`Payroll` application consists of three sections: :guilabel:`To Pay`, :guilabel:`All Payslips`, and :guilabel:`Batches`." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:13 +msgid "These three sections provide all the tools needed to create payslips for employees, including individual payslips, a batch of payslips, or commission payslips." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:-1 +msgid "Payslips menu selection in Payroll." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:21 +msgid "To pay" +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:23 +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 "" + +#: ../../content/applications/hr/payroll/payslips.rst:-1 +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." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:36 +msgid "Clicking on an individual payslip entry will show the details for the individual payslip." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:41 +msgid "Create 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." +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." +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." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:-1 +msgid "The necessary fields for a new payslip." +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." +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." +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." +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`." +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." +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." +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." +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." +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." +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." +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." +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." +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." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:116 +msgid "Save and process new payslip" +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." +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." +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." +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." +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." +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." +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." +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 +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)." +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`." +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." +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." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:183 +msgid "`Done` indicates the payslip is calculated and ready to be 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 +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." +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." +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." +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 +msgid "Both *To Pay* and *All Payslips* display all the detailed information for each payslip." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:218 +msgid "Batches" +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:220 +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`." +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 +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." +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." +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." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:299 +msgid "Lastly, in the :guilabel:`Company` field, select the company these payslips are written against." +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." +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." +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." +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." +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." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:-1 +msgid "Generate payslips for the new batch." +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." +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." +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." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:333 +msgid "Once the payslips have been successfully generated, the screen returns to the payslip batch form." +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`." +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." +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." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:347 +msgid "Generate commission payslips" +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." +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." +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." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:366 +msgid "In the :guilabel:`Department` field, select the desired department from the drop-down menu." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:368 +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." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:375 +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." +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." +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." +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:3 +#: ../../content/applications/hr/referrals.rst:753 +#: ../../content/applications/hr/time_off.rst:700 +msgid "Reporting" +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." +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:11 +msgid "To view a report, go to :menuselection:`Payroll --> Reporting` and click on the specific report." +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:-1 +msgid "Report dashboard view." +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.`" +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." +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`." +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:-1 +msgid "Favorite options for reports." +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:41 +msgid "Click on :menuselection:`Payroll --> Reporting --> Payroll` to display the :guilabel:`Payroll Analysis` report." +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`." +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:61 +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." +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:73 +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." +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." +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." +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:91 +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." +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:101 +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." +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." +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" +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." +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`." +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." +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:192 +msgid "Attachment of Salary" +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." +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." +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." +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." +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:-1 +msgid "Select the options that be displayed in the 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`." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:5 +msgid "The *Work Entries* dashboard, which can be found by going to :menuselection:`Payroll --> Work Entries --> Work Entries`, provides a visual overview of the individual time sheets of every employee, with each day split into a morning shift and an afternoon shift." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:-1 +msgid "Work Entries dashboard view showing all employee's work entries." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:13 +msgid "To change the view so that only the entries for a single day, week, or month are shown, click on one of the corresponding links for :guilabel:`Day`, :guilabel:`Week`, or :guilabel:`Month`, located at the top of the dashboard." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:17 +msgid "Use the :guilabel:`⬅️ (left arrow)` and :guilabel:`➡️ (right arrow)` icons on the left and right side of the :guilabel:`Today` button to adjust the displayed dates. The arrows will adjust the date based on the type of time selected. For example, if month is selected, the arrows will move one month with each click of the arrow. If week or day is selected, the time will move by either a week or a day for each click of the arrow, respectively." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:24 +msgid "Adding a new work entry" +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:26 +msgid "If a work entry is missing and needs to be added, such as sick time or time off, click :guilabel:`Add` to create a new work entry. A pop-up will appear, with several fields to fill in." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:29 +msgid "Enter the :guilabel:`Work Entry Name`, such as `Sick Time` or any other short description. Select the :guilabel:`Employee` and the :guilabel:`Work Entry Type` from the respective drop-down lists." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:-1 +msgid "Filling in the work entry Create form in Odoo." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:36 +msgid "Next, enter the date and time for the work entry in the :guilabel:`From` and :guilabel:`To` drop-downs. First, select the date by navigating to the correct month and year using the :guilabel:`⬅️ (left arrow)` and :guilabel:`➡️ (right arrow)` icons, then click on the specific day." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:40 +msgid "Then, select the time by clicking on the :guilabel:`⏰ (clock)` icon, and using the :guilabel:`⬆️ (up arrow)` and :guilabel:`⬇️ (down arrow)` icons for each section to enter the hour, minute, and second for the time period." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:44 +msgid "The :guilabel:`Period` will display the hours based on the :guilabel:`To` and :guilabel:`From` entries." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:48 +msgid "Before clicking either :guilabel:`Save & Close` or :guilabel:`Save & New`, it is good to double check the :guilabel:`Period` to ensure the time stated corresponds to the :guilabel:`To` and :guilabel:`From` fields." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:0 +msgid "Hours entered in the Period field." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:56 +msgid "Once the information is entered, click :guilabel:`Save & Close` to save the entry and close the pop-up, or :guilabel:`Save & New` to save the entry and create another :guilabel:`Work Entry Type`." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:60 +msgid "Regenerate work entries" +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:62 +msgid "After a work entry has been either added or modified, the work entries need to be regenerated for the affected employee(s). Click on the :guilabel:`Regenerate Work Entries` button at the top of the main dashboard, and a pop-up will appear." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:66 +msgid "Select the :guilabel:`Employee` to regenerate work entries for from the :guilabel:`drop-down menu`, and adjust the :guilabel:`From` and :guilabel:`To` fields so the correct date range is displayed. Click the :guilabel:`Regenerate Work Entries` button and the work entries will be recreated. Once finished, the pop-up will close." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:-1 +msgid "Regenerate a work entry for a particular employee." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:76 +msgid "Conflicts" +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:78 +msgid "A conflict appears for any request that has not been approved, such as sick time or vacation, or if there are any errors on the work entry, such as required fields being left blank. Conflicts are required to be resolved before payslips can be generated." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:82 +msgid "Any work entry that has a conflict to be resolved is indicated on the main :guilabel:`Work Entry` overview dashboard, located by going to :menuselection:`Payroll --> Work Entries --> Conflicts`, where only conflicts needing resolution are shown." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:-1 +msgid "Conflicts dashboard view showing all employee's conflicts in work entries." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:90 +msgid "Conflicts are indicated with an orange triangle in the top left corner of each individual entry. Click on an individual work entry to see the conflict details in a pop-up." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:93 +msgid "The conflict is briefly explained in an orange text box." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:-1 +msgid "Details for a conflict appear in the pop-up." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:99 +msgid "The :guilabel:`Work Entry Name`, :guilabel:`Employee`, and :guilabel:`Work Entry Type` are listed on the left side of the pop-up. The :guilabel:`From` and :guilabel:`To` date range, as well as the total time requested (in hours), appear in the :guilabel:`Period` field on the right side." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:103 +msgid "If there is a conflict because a time-off request for the same time already exists in the system, the time-off will be entered in the :guilabel:`Time Off` field. Clicking the :guilabel:`External Link` button next to the :guilabel:`Time Off` entry will bring up the duplicate time-off request." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:107 +msgid "The details for the time-off request appear in the pop-up. The request can be modified if needed. Click either the :guilabel:`Validate` or :guilabel:`Refuse` button to approve or deny the request, then click the :guilabel:`Save` button to save the changes." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:-1 +msgid "Edit and/or validate a duplicate time-off request." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:115 +msgid "Once the duplicate time-off request has been approved and saved, the screen goes back to the conflict. Click :guilabel:`Refuse Time Off` or :guilabel:`Approve Time Off` via the buttons in the top right to either approve or deny the request. Repeat for all conflicts until there are no conflicts to resolve." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:120 +msgid "After conflicts have been resolved, work entries must be regenerated for each employee by clicking the :guilabel:`Regenerate Work Entries` button, and entering the corresponding information for each employee." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:-1 +msgid "Regenerate Work Entries button on the Work Entries Regeneration form." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:129 +msgid "Generating payslips" +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:131 +msgid "To generate payslips, navigate to the time period the payslips should be generated for, either day, week, or month. When the desired pay period is displayed, click the :guilabel:`Generate Payslips` button." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:-1 +msgid "Generate Payslips button on the Work Entry dashboard." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:140 +msgid "If the :guilabel:`Generate Payslips` button is not active (appears light turquoise instead of dark turquoise), that indicates there are conflicts. *Solve conflicts first* will appear as a warning when :guilabel:`Generate Payslips` is moused over. Resolve all conflicts before generating payslips." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:145 +msgid "A batch entry will appear for the time period selected. The batch name appears at the top in the :guilabel:`Name` field, typically listing the month and year for the particular batch." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:148 +msgid "The date range the payslips apply to appears in the :guilabel:`Period` field. The company appears in the :guilabel:`Company` field, along with an option to mark the payslips as a credit note. To make changes, click the :guilabel:`Edit` button in the top left, make any changes, then click either :guilabel:`Save` to accept the changes or :guilabel:`Discard` to revert to the original data." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:-1 +msgid "Batch information that appears when making a batch." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:157 +msgid "Click the :guilabel:`Create Draft Entry` button to create the payslips for the batch." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:159 +msgid "Click on the :guilabel:`Payslips` button in the top right to view all the payslips for the batch." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:162 +msgid "Payslips will have a status of *Waiting* until the :guilabel:`Create Draft Entry` button has been clicked. After, the payslip status will change to *Done*." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:165 +msgid "Payslips can be printed by clicking the box next to each payslip to print, or clicking the box next to :guilabel:`Reference` to select all the payslips at once. Click the :guilabel:`Print` button, and a PDF file will be created with all the specified payslips." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:-1 +msgid "Print button for printing the payslips." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:174 +msgid ":ref:`Configure work entries `" +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:6 +#: ../../content/applications/hr/recruitment/new_job.rst:60 +msgid "Recruitment" +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:8 +msgid "Odoo keeps all job applicants organized with a pre-configured series of steps and stages that each applicant goes through. Each stage has a specific step(s) that should be performed. These range from scheduling a phone call, conducting an interview, to sending a job offer, just to name a few. This process is referred to as the 'applicant flow'." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:13 +msgid "When an applicant applies for a job position, an *applicant card* is automatically created in Odoo's *Recruitment* app for that specific job position. As the applicant progresses through the recruitment pipeline, the recruitment team moves their card from one stage to the next." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:17 +msgid ":ref:`Stages can be configured ` so that an email is automatically sent out using a set, pre-configured template as soon as an applicant's card enters a stage. These automated emails are defined on each stage in the applicant flow." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:21 +msgid "The applicant flow explained in this document is the default flow in Odoo, and goes through the applicant flow when using the *Recruitment* application's default configuration. The applicant flow is able to be modified to suit the specific recruitment flow for any business." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:26 +msgid "The applicant flow with all its stages are universal and applies to all job positions, unless specified. :ref:`A specific stage can be configured ` to be job-specific, meaning that specific stage is only visible for that specific job position. Otherwise, if a new stage is created, or an existing stage is modified, those changes will be visible on all job positions." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:35 +msgid "To access the kanban view for a job position, navigate to the main :menuselection:`Recruitment app` dashboard, which is the default view when opening the application. All job positions appear on the main dashboard. Click the :guilabel:`New Applications` smart button on a job position card to navigate to the kanban view for all the applicants for that particular job position." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:-1 +msgid "Main dashboard view of job position card, showing new applications button." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:44 +msgid "Inside the job application, the kanban stages appear, with all the applicants populated in their respective columns, indicating what stage they are currently in. There are five default stages in Odoo:" +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:48 +msgid ":ref:`Initial Qualification `" +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:49 +msgid ":ref:`First Interview `" +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:50 +msgid ":ref:`Second Interview `" +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:51 +msgid ":ref:`Contract Proposal `" +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:52 +msgid ":ref:`Contract Signed `" +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:54 +msgid "The last column, :guilabel:`Contract Signed`, is folded by default, meaning that the column appears in gray and the applicants in it are hidden from view. To expand the folded stage and view the applicant cards for that column, click anywhere on the thin gray column that says the stage name and the column expands, revealing the applicants." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:-1 +msgid "Expand a folded column by clicking on it in the kanban view." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:63 +msgid "Each stage has a color-coded bar beneath the stage name, giving information about the applicant's status in the stage. The colors are:" +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:66 +msgid ":guilabel:`Green`: there are applicants in the stage with an activity that is either already scheduled or needs to be scheduled in the future (such as a phone call or interview), according to the parameters for that particular stage." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:69 +msgid ":guilabel:`Yellow`: there are applicants in the stage with an activity either scheduled for today or due to be scheduled today." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:71 +msgid ":guilabel:`Red`: there are applicants in the stage with overdue activities which need to be scheduled." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:73 +msgid ":guilabel:`Gray`: there are either no activities currently scheduled and no future activities that are required to be scheduled, or there are no applicants currently in the stage." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:79 +msgid "Customize stages" +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:81 +msgid "Stages can be modified, added, or deleted to best meet the needs of the particular hiring steps of a business." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:85 +msgid "New stage" +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:87 +msgid "To create a new stage, click on :guilabel:`+ Add a Column` and a new column appears. Enter the title for the new stage in the :guilabel:`Column title` field, then click :guilabel:`Add`. The new column appears, and another new stage is available to create. If no new stages are needed, click anywhere on the screen to exit the new column creation." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:-1 +msgid "The plus sign to click in order to add a new column to the kanban stages." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:99 +msgid "Modify stage" +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:101 +msgid "To modify the settings of a stage, hover over the name of the stage, and a :guilabel:`⚙️ (gear)` icon appears in the upper right hand side of the stage. Click on the :guilabel:`⚙️ (gear)` icon and a menu appears. Then click on the :guilabel:`Edit Stage` option. An :guilabel:`Edit Column` form appears. Make any modifications to the form, then click :guilabel:`Save` when done." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:-1 +msgid "The gear icon that appears when a column name is moused over, and the drop-down menu it\n" +"displays when clicked." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:112 +msgid "Edit column form" +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:114 +msgid "The :guilabel:`Edit Column` form is where the stage's settings are configured. The only required fields are the :guilabel:`Stage Name`, and the :guilabel:`Tooltips` section." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:117 +msgid "The fields to be populated or modified are:" +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:119 +msgid ":guilabel:`Stage Name`: type in a name for the stage." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:120 +msgid ":guilabel:`Email Template`: select an email template to be used from the drop-down menu. If a template is selected, when the applicant card enters the stage, an email will automatically be sent to the applicant using the selected template." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:123 +msgid ":guilabel:`Folded in Kanban`: check the box to have the stage appear folded (hidden) at all times in the default view." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:125 +msgid ":guilabel:`Hired Stage`: check the box if this stage indicates that the applicant is hired. When an applicant's card enters this stage, the card displays a :guilabel:`Hired` banner in the upper right corner. If this box is checked, this stage is used to determine the hire date of an applicant." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:129 +msgid ":guilabel:`Job Specific`: if the stage only applies to a specific job position(s), select the job position(s) from the drop-down menu. Multiple job positions can be selected." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:131 +msgid ":guilabel:`Show in Referrals`: check the box if this stage should be seen in the *Referrals* application, and allow the referrer to accrue points when a referral of theirs reaches this stage. If this is active, a :guilabel:`Points` field appears. Enter the amount of referral points the employee receives when an applicant enters this stage." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:135 +msgid ":guilabel:`Tooltips` section: there are three pre-configured labels (colored circles) for each applicant's card, indicating its status. These colors are displayed at the top of each stage to reflect the statuses of the applicants in the stage. The *names* for the label can be modified, but the label itself (the color) cannot. The default names and labels are: :guilabel:`In Progress` (gray), :guilabel:`Blocked` (red), and :guilabel:`Ready for Next Stage` (green)." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:140 +msgid ":guilabel:`Requirements`: enter any internal notes for this stage explaining any requirements of the stage." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:144 +msgid "Delete stage" +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:146 +msgid "If a stage is no longer needed, the stage can be deleted. To delete a stage, hover over the name of the stage, and a :guilabel:`⚙️ (gear)` icon appears. First, click on the :guilabel:`⚙️ (gear)` icon to reveal a drop-down menu, then click :guilabel:`Delete`. A pop-up warning appears, asking :guilabel:`Are you sure you want to remove this column?`. Click :guilabel:`OK` to delete the column." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:152 +msgid "If there are applicants currently in the stage being deleted, an error pops up when attempting to delete the stage, explaining that there are records in the stage which need to be deleted, archived, or moved to a different stage before deleting." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:157 +msgid "Email templates" +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:159 +msgid "To communicate with the applicant, Odoo has several pre-configured email templates that can be used. The pre-configured email templates and when to use them are as follows:" +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:162 +msgid ":guilabel:`Applicant: Acknowledgement`: this template is used to let the applicant know that their application was received. This email is automatically sent out once the applicant is in the :guilabel:`First Interview` stage." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:165 +msgid ":guilabel:`Applicant: Interest`: this template is used to let the applicant know that they have passed the :guilabel:`Initial Qualification` stage and they will be contacted to set up an interview with the recruiter." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:168 +msgid ":guilabel:`Applicant: Not interested anymore`: this template is used when an applicant communicates that they are no longer interested in the position, and thanks them for their time and consideration." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:171 +msgid ":guilabel:`Applicant: Refuse`: this template is used when an applicant is no longer being considered for the position." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:173 +msgid ":guilabel:`Applicant: Your Salary Package`: this template is used when offering an applicant a position. This informs the applicant they can configure their salary package." +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/companies/email_template` document." +msgstr "" + +#: ../../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 "" + +#: ../../content/applications/hr/recruitment.rst:-1 +msgid "Send an email from the chatter." +msgstr "" + +#: ../../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: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: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: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:212 +msgid "Stage flow" +msgstr "" + +#: ../../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: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 "" + +#: ../../content/applications/hr/recruitment.rst:-1 +msgid "Change the stage of an applicant by clicking on the desired stage at the top of the\n" +"applicant's card." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:233 +msgid "Initial qualification" +msgstr "" + +#: ../../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: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: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:255 +msgid "Send interview" +msgstr "" + +#: ../../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: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: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: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: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: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: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: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: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: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 "" + +#: ../../content/applications/hr/recruitment.rst:-1 +msgid "Send a custom survey, also referred to as an interview form, to an applicant using a\n" +"pre-configured template." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:314 +msgid "Refuse" +msgstr "" + +#: ../../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: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: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: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: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 "" + +#: ../../content/applications/hr/recruitment.rst:-1 +msgid "An applicant's card with the refused banner appearing in the top right corner in red." +msgstr "" + +#: ../../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:360 +msgid "New applicant" +msgstr "" + +#: ../../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:371 +msgid "Quick add" +msgstr "" + +#: ../../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 "" + +#: ../../content/applications/hr/recruitment.rst:-1 +msgid "All the fields for a new applicant form entered when using the Quick Add option." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:383 +msgid "Enter the following information on the card:" +msgstr "" + +#: ../../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:`Email`: enter the applicant's email address." +msgstr "" + +#: ../../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: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: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:407 +msgid "Create" +msgstr "" + +#: ../../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: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: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:426 +msgid "Applicant section" +msgstr "" + +#: ../../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:436 +msgid ":guilabel:`Phone`: enter the applicant's phone number." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:437 +msgid ":guilabel:`Mobile`: enter the applicant's mobile number." +msgstr "" + +#: ../../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: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: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: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: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: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:459 +msgid "Job section" +msgstr "" + +#: ../../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: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:466 +msgid ":guilabel:`Department`: select the department the job position falls under from the drop-down menu." +msgstr "" + +#: ../../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:471 +msgid "Contract section" +msgstr "" + +#: ../../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: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: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: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: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:488 +msgid "Application summary tab" +msgstr "" + +#: ../../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 "" + +#: ../../content/applications/hr/recruitment.rst:-1 +msgid "All the fields for a new applicant form entered." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:500 +msgid "First interview" +msgstr "" + +#: ../../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 "" + +#: ../../content/applications/hr/recruitment.rst:-1 +msgid "An applicant's card moves from one stage t another by using the click and drag method." +msgstr "" + +#: ../../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:520 +msgid "Schedule a meeting" +msgstr "" + +#: ../../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: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: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: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: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 "" + +#: ../../content/applications/hr/recruitment.rst:-1 +msgid "The calendar view, highlighting how to change the displayed meetings." +msgstr "" + +#: ../../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: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:564 +msgid "New event card" +msgstr "" + +#: ../../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: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: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:578 +msgid "Meeting details tab" +msgstr "" + +#: ../../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: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: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: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: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: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: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:602 +msgid ":guilabel:`Location`: enter the location for the meeting." +msgstr "" + +#: ../../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: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:608 +msgid "Options tab" +msgstr "" + +#: ../../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: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: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 "" + +#: ../../content/applications/hr/recruitment.rst:-1 +msgid "A new meeting card with all the details populated, and ready to save." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:629 +msgid "Send meeting to attendees" +msgstr "" + +#: ../../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: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 "" + +#: ../../content/applications/hr/recruitment.rst:-1 +msgid "Enter the information to send the event via email." +msgstr "" + +#: ../../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: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: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 "" + +#: ../../content/applications/hr/recruitment.rst:-1 +msgid "Send a text message to the attendees of the meeting." +msgstr "" + +#: ../../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:676 +msgid "Second interview" +msgstr "" + +#: ../../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: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:691 +msgid "Contract proposal" +msgstr "" + +#: ../../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: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: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:711 +msgid "Universal fields" +msgstr "" + +#: ../../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: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:718 +msgid ":guilabel:`Job Title`: the name of the position being offered to the applicant." +msgstr "" + +#: ../../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:723 +msgid ":guilabel:`Yearly Cost`: the annual salary being offered." +msgstr "" + +#: ../../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: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: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: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: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:749 +msgid ":guilabel:`Force New Cars List`: check this box to offer a new vehicle to the applicant." +msgstr "" + +#: ../../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:752 +msgid ":guilabel:`Canteen Cost`: enter the amount that is offered to the applicant for the cafeteria." +msgstr "" + +#: ../../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 "" + +#: ../../content/applications/hr/recruitment.rst:-1 +msgid "Format the offer to send to the applicant. Make any modifications before sending." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:761 +msgid "Send offer" +msgstr "" + +#: ../../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: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: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 "" + +#: ../../content/applications/hr/recruitment.rst:-1 +msgid "Send an email to the applicant with a link to the offered salary." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:787 +msgid "Contract signed" +msgstr "" + +#: ../../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: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: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 "" + +#: ../../content/applications/hr/recruitment.rst:-1 +msgid "Hired banner in the top right corner of applicant card." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:807 +msgid "Create employee" +msgstr "" + +#: ../../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: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 "" + +#: ../../content/applications/hr/recruitment/new_job.rst:3 +msgid "Job positions" +msgstr "" + +#: ../../content/applications/hr/recruitment/new_job.rst:5 +msgid "In the default :menuselection:`Recruitment` dashboard view, all job positions are shown, regardless of status. Current published positions with active applicants are shown, as well as job positions that have been created but have not yet been published." +msgstr "" + +#: ../../content/applications/hr/recruitment/new_job.rst:9 +msgid "Each job position is shown in an individual kanban card. If the job position is active and candidates can apply, then a :guilabel:`Published` banner will appear in the top-right corner of the card." +msgstr "" + +#: ../../content/applications/hr/recruitment/new_job.rst:13 +msgid "View submitted applications by clicking the :guilabel:`# Applications` button, with `#` being the number of applications received. If a position is not published, a :guilabel:`Start Recruitment` button will appear instead." +msgstr "" + +#: ../../content/applications/hr/recruitment/new_job.rst:-1 +msgid "Main dashboard view of Recruitment showing all job positions." +msgstr "" + +#: ../../content/applications/hr/recruitment/new_job.rst:22 +msgid "Create a new job position" +msgstr "" + +#: ../../content/applications/hr/recruitment/new_job.rst:24 +msgid "There are two ways a job position can be created: from the main :guilabel:`Recruitment` dashboard, or from the :guilabel:`Configuration` menu." +msgstr "" + +#: ../../content/applications/hr/recruitment/new_job.rst:27 +msgid "To create a job position from the :guilabel:`Configuration` menu, go to :menuselection:`Recruitment app --> Configuration --> Job Positions`. The job positions in this view are displayed in a list." +msgstr "" + +#: ../../content/applications/hr/recruitment/new_job.rst:30 +msgid "Create a new job position from the :guilabel:`Job Positions` dashboard by clicking the :guilabel:`Create` button in the top-left corner." +msgstr "" + +#: ../../content/applications/hr/recruitment/new_job.rst:33 +msgid "Then, a :guilabel:`Create a Job Position` pop-up window will appear. From here, enter the name of the position (such as `Sales Manager`, `Mechanical Engineer`, etc.). When complete, click the :guilabel:`Create` button to save the entry, or the :guilabel:`Discard` button to delete it." +msgstr "" + +#: ../../content/applications/hr/recruitment/new_job.rst:-1 +msgid "Create a new job position." +msgstr "" + +#: ../../content/applications/hr/recruitment/new_job.rst:41 +msgid "Once the job position has been created, it will appear as a card in the kanban view on the main :guilabel:`Recruitment`` dashboard, as well as in the list view on the :guilabel:`Configuration` dashboard." +msgstr "" + +#: ../../content/applications/hr/recruitment/new_job.rst:46 +msgid "Edit a new job position" +msgstr "" + +#: ../../content/applications/hr/recruitment/new_job.rst:48 +msgid "Once the job position is created, it's time to enter the details for the position. Click on the :guilabel:`⋮ (three dots)` icon in the upper-right corner of the relevant card to reveal several options, and then click :guilabel:`Edit` to edit the details." +msgstr "" + +#: ../../content/applications/hr/recruitment/new_job.rst:-1 +msgid "Edit the job position card." +msgstr "" + +#: ../../content/applications/hr/recruitment/new_job.rst:56 +msgid "Enter the job description in the :guilabel:`Job Description` tab. This information is what is visible to potential employees when searching for available jobs." +msgstr "" + +#: ../../content/applications/hr/recruitment/new_job.rst:62 +msgid "All the basic information about the job position is listed under the :guilabel:`Recruitment` tab. None of the fields are required, but it is a good idea to provide at least a few details, such as where the job is located." +msgstr "" + +#: ../../content/applications/hr/recruitment/new_job.rst:66 +msgid "The fields can be filled out as follows:" +msgstr "" + +#: ../../content/applications/hr/recruitment/new_job.rst:68 +msgid ":guilabel:`Company`: Select the company the job is for." +msgstr "" + +#: ../../content/applications/hr/recruitment/new_job.rst:69 +msgid ":guilabel:`Website`: Select the website where the job will be published." +msgstr "" + +#: ../../content/applications/hr/recruitment/new_job.rst:70 +msgid ":guilabel:`Department`: Select the relevant department for the job position." +msgstr "" + +#: ../../content/applications/hr/recruitment/new_job.rst:71 +msgid ":guilabel:`Job Location`: Select the physical address for the job." +msgstr "" + +#: ../../content/applications/hr/recruitment/new_job.rst:72 +msgid ":guilabel:`Expected New Employees`: Enter the number of employees to be hired for this position." +msgstr "" + +#: ../../content/applications/hr/recruitment/new_job.rst:73 +msgid ":guilabel:`Is Published`: Check the box to publish the job online." +msgstr "" + +#: ../../content/applications/hr/recruitment/new_job.rst:74 +msgid ":guilabel:`Contract Template`: Select a contract template that will be used when offering the job to a candidate." +msgstr "" + +#: ../../content/applications/hr/recruitment/new_job.rst:76 +msgid ":guilabel:`Interviewers`: Select who should perform the interview(s). Multiple people can be selected." +msgstr "" + +#: ../../content/applications/hr/recruitment/new_job.rst:78 +msgid ":guilabel:`Interview Form`: Select a form that applicants will fill out prior to their interview, or create a new form. Once selected, a :guilabel:`Display (Name) Form` button will appear next to the selected form. Click on this to see how the form will be displayed to the candidate on the front end." +msgstr "" + +#: ../../content/applications/hr/recruitment/new_job.rst:-1 +msgid "The interview form will display a link to see the form as the candidate will." +msgstr "" + +#: ../../content/applications/hr/recruitment/new_job.rst:87 +msgid ":guilabel:`Recruiter`: Select the person who will be doing the recruiting for this role." +msgstr "" + +#: ../../content/applications/hr/recruitment/new_job.rst:-1 +msgid "Enter job information details in the recruitment tab." +msgstr "" + +#: ../../content/applications/hr/recruitment/new_job.rst:94 +msgid "Create interview form" +msgstr "" + +#: ../../content/applications/hr/recruitment/new_job.rst:96 +msgid "Once a job position has been made, the :guilabel:`Interview Form` needs to be created. In the kanban view of the :menuselection:`Recruitment` dashboard, click on the :guilabel:`⋮ (three dots)` icon in the upper-right corner of the card to reveal several options, and then click :guilabel:`Create Interview Form`." +msgstr "" + +#: ../../content/applications/hr/recruitment/new_job.rst:-1 +msgid "Create an interview form for the new position." +msgstr "" + +#: ../../content/applications/hr/recruitment/new_job.rst:105 +msgid "Next the survey form loads. The :guilabel:`Survey Title` is pre-populated based on the job description. Then, select the person :guilabel:`Responsible` for the survey from the drop-down menu." +msgstr "" + +#: ../../content/applications/hr/recruitment/new_job.rst:109 +#: ../../content/applications/hr/recruitment/new_job.rst:309 +msgid "Questions" +msgstr "" + +#: ../../content/applications/hr/recruitment/new_job.rst:111 +msgid "In the :guilabel:`Questions` tab, click on :guilabel:`Add a section` to add a section to the form. A line appears, and a section heading can be entered. When complete, click off the line, or press enter to lock in the new section on the form." +msgstr "" + +#: ../../content/applications/hr/recruitment/new_job.rst:119 +msgid "Next, click :guilabel:`Add a question` to add a question to the section. A pop-up window appears to enter the question details. Type out the question in the top line." +msgstr "" + +#: ../../content/applications/hr/recruitment/new_job.rst:122 +msgid "There are several *Question Types* to choose from:" +msgstr "" + +#: ../../content/applications/hr/recruitment/new_job.rst:124 +msgid ":guilabel:`Multiple choice: only one answer`: a multiple choice question that only allows the candidate to select one answer" +msgstr "" + +#: ../../content/applications/hr/recruitment/new_job.rst:126 +msgid ":guilabel:`Multiple choice: multiple answers allowed`: a multiple choice question that allows the candidate to select multiple answers" +msgstr "" + +#: ../../content/applications/hr/recruitment/new_job.rst:128 +msgid ":guilabel:`Multiple Lines Text Box`: allows the applicant to enter several lines of text" +msgstr "" + +#: ../../content/applications/hr/recruitment/new_job.rst:129 +msgid ":guilabel:`Single Line Text Box`: limits the applicant to only a single line of text" +msgstr "" + +#: ../../content/applications/hr/recruitment/new_job.rst:130 +msgid ":guilabel:`Numerical Value`: only allows a number to be entered" +msgstr "" + +#: ../../content/applications/hr/recruitment/new_job.rst:131 +msgid ":guilabel:`Date`: a calendar module is presented to select a date" +msgstr "" + +#: ../../content/applications/hr/recruitment/new_job.rst:132 +msgid ":guilabel:`Datetime`: a calendar module and a clock icon is presented to select a date and time" +msgstr "" + +#: ../../content/applications/hr/recruitment/new_job.rst:133 +msgid ":guilabel:`Matrix`: a customizable table that allows the candidate to choose an answer for each row" +msgstr "" + +#: ../../content/applications/hr/recruitment/new_job.rst:136 +msgid "After selecting a question type, a sample question appears in gray. This represents how the question format will be displayed to applicants." +msgstr "" + +#: ../../content/applications/hr/recruitment/new_job.rst:-1 +msgid "Add a new question to the interview form." +msgstr "" + +#: ../../content/applications/hr/recruitment/new_job.rst:143 +msgid "Questions and sections can be reorganized. Move them by clicking and dragging individual section headings or question lines to their desired position(s)." +msgstr "" + +#: ../../content/applications/hr/recruitment/new_job.rst:146 +msgid "Sections are indicated by a gray background, while questions have a white background." +msgstr "" + +#: ../../content/applications/hr/recruitment/new_job.rst:-1 +msgid "A sample of categories and questions for a candidate." +msgstr "" + +#: ../../content/applications/hr/recruitment/new_job.rst:153 +#: ../../content/applications/hr/recruitment/new_job.rst:241 +msgid "Answers" +msgstr "" + +#: ../../content/applications/hr/recruitment/new_job.rst:155 +msgid "If :guilabel:`Multiple choice: only one answer`, :guilabel:`Multiple choice: multiple answers allowed`, :guilabel:`Single Line Text Box`, or :guilabel:`Matrix` is selected for the :guilabel:`Question Type`, an :guilabel:`Answers` tab appears beneath the question. If another :guilabel:`Question Type` is selected, the :guilabel:`Answers` tab remains hidden from view." +msgstr "" + +#: ../../content/applications/hr/recruitment/new_job.rst:162 +msgid "Multiple choice" +msgstr "" + +#: ../../content/applications/hr/recruitment/new_job.rst:164 +msgid "For both the :guilabel:`Multiple choice: only one answer` and :guilabel:`Multiple choice: multiple answers allowed` question types, the answers are populated in the same way." +msgstr "" + +#: ../../content/applications/hr/recruitment/new_job.rst:167 +msgid "First, in the :guilabel:`Answers` tab, click :guilabel:`Add a line`. A line appears, and an answer can be entered. After typing in the answer, click off the line, or press enter to lock in the new answer on the form and have another answer line appear." +msgstr "" + +#: ../../content/applications/hr/recruitment/new_job.rst:171 +msgid "If desired, an image can be attached to the answer. Click on a line to select it, and an :guilabel:`Upload your file` button appears on the right side. Click the :guilabel:`Upload your file` button and a file explorer window appears. Navigate to the photo file, select it, then click :guilabel:`Open` to select it." +msgstr "" + +#: ../../content/applications/hr/recruitment/new_job.rst:176 +msgid "Repeat this for all the answers to be added for the multiple choice question. The answers can be rearranged in any order. To move an answer, click on the :guilabel:`↕️ (Up-down arrows)` on the far left of each answer line, and drag the answer to the desired position. The order the answers appear in the form is the order the answers will appear online." +msgstr "" + +#: ../../content/applications/hr/recruitment/new_job.rst:181 +msgid "To delete a line, click on the :guilabel:`🗑️ (trash can)` icon on the far right side of the answer line." +msgstr "" + +#: ../../content/applications/hr/recruitment/new_job.rst:0 +msgid "Answers to a multiple choice question, where each line has a different answer listed." +msgstr "" + +#: ../../content/applications/hr/recruitment/new_job.rst:188 +msgid "Single Line Text Box" +msgstr "" + +#: ../../content/applications/hr/recruitment/new_job.rst:190 +msgid "If the :guilabel:`Single Line Text Box` is selected for the :guilabel:`Question Type`, only two checkboxes appear in the :guilabel:`Answers` tab:" +msgstr "" + +#: ../../content/applications/hr/recruitment/new_job.rst:193 +msgid ":guilabel:`Input must be an email`: Activate this option if the answer must be in the format of an email address." +msgstr "" + +#: ../../content/applications/hr/recruitment/new_job.rst:196 +msgid ":guilabel:`Save as user email?`: This option appears if :guilabel:`Input must be an email` is selected. This saves the email entered on the form as the user's email, and will be used anytime Odoo contacts the user via email." +msgstr "" + +#: ../../content/applications/hr/recruitment/new_job.rst:200 +msgid ":guilabel:`Save as user nickname?`: Activate this option to populate the answer as the user's nickname. This is stored and used anywhere Odoo uses a nickname." +msgstr "" + +#: ../../content/applications/hr/recruitment/new_job.rst:203 +msgid "Matrix" +msgstr "" + +#: ../../content/applications/hr/recruitment/new_job.rst:205 +msgid "Sometimes, a question is asked that does not fit a standard answer format, and is best suited for a matrix. For example, asking an applicant what is their availability to work compared to the various shifts is a perfect question for a matrix format. In this example, an applicant can click on all the shifts they are available to work." +msgstr "" + +#: ../../content/applications/hr/recruitment/new_job.rst:210 +msgid "For a :guilabel:`Matrix` :guilabel:`Question Type`, there are two sets of data that need to be input. The rows and columns must both be configured. The columns are represented by the :guilabel:`Choices` section, while the rows are configured in the :guilabel:`Rows` section." +msgstr "" + +#: ../../content/applications/hr/recruitment/new_job.rst:214 +msgid "The method for populating both sections is the same. In the :guilabel:`Answers` tab, click :guilabel:`Add a line` in either the :guilabel:`Choices` or :guilabel:`Row` section. A line appears, and an answer can be entered. After typing in the answer, click off the line, or press enter to lock in the new answer on the form and have another answer line appear. Repeat this for all answers for both the :guilabel:`Choices` and :guilabel:`Rows` sections." +msgstr "" + +#: ../../content/applications/hr/recruitment/new_job.rst:223 +msgid "This is an example matrix that asks an applicant what shifts they are available to work on Saturdays and Sundays, either morning, afternoon, or evening." +msgstr "" + +#: ../../content/applications/hr/recruitment/new_job.rst:227 +#: ../../content/applications/hr/recruitment/new_job.rst:383 +msgid "Description" +msgstr "" + +#: ../../content/applications/hr/recruitment/new_job.rst:229 +msgid "Enter any information that may be helpful to an applicant. This description will appear for this specific question only, and therefore should be question-specific and not generalized." +msgstr "" + +#: ../../content/applications/hr/recruitment/new_job.rst:233 +#: ../../content/applications/hr/recruitment/new_job.rst:303 +msgid "Options" +msgstr "" + +#: ../../content/applications/hr/recruitment/new_job.rst:235 +msgid "To view the options that are available to set for a question, click on the :guilabel:`Options` tab. The :guilabel:`Layout`, :guilabel:`Constraints`, and :guilabel:`Live Sessions` sections are universal for all :guilabel:`Question Types`, while the :guilabel:`Answers` tab is specific to the :guilabel:`Question Type` selected, and changes based on the selection." +msgstr "" + +#: ../../content/applications/hr/recruitment/new_job.rst:243 +msgid ":guilabel:`Multiple choice: only one answer` and :guilabel:`Multiple choice: multiple answers allowed`: The :guilabel:`Answers` section is blank, with no choices needed to be made." +msgstr "" + +#: ../../content/applications/hr/recruitment/new_job.rst:245 +msgid ":guilabel:`Multiple Lines Text Box`: A :guilabel:`Placeholder` field appears. Enter any text that should appear with the question to help clarify how the applicant should answer." +msgstr "" + +#: ../../content/applications/hr/recruitment/new_job.rst:247 +msgid ":guilabel:`Single Line Text Box`, :guilabel:`Numerical Value`, :guilabel:`Date`, and :guilabel:`Datetime`: A :guilabel:`Validate entry` option appears. Activate this option if what the applicant enters must be verified as adhering to the parameters set in this section. When activated, several other options appear. Enter the :guilabel:`Minimum` and :guilabel:`Maximum` values in the corresponding fields. Depending on the :guilabel:`Question Type` selected, these fields may reference characters, numbers, or dates. Next, enter the text that appears when the answer given does not fit within the designated minimum and maximum parameters. Last, enter any text in the :guilabel:`Placeholder` field to provide any additional information or directions to assist the applicant." +msgstr "" + +#: ../../content/applications/hr/recruitment/new_job.rst:256 +msgid ":guilabel:`Matrix`: The first option that appears is :guilabel:`Matrix Type`. Select either :guilabel:`One choice per row` or :guilabel:`Multiple choices per row` using the drop-down menu." +msgstr "" + +#: ../../content/applications/hr/recruitment/new_job.rst:260 +msgid "Constraints" +msgstr "" + +#: ../../content/applications/hr/recruitment/new_job.rst:262 +msgid "If the question is required to be answered by the applicant, activate the box next to :guilabel:`Mandatory Answer`. An :guilabel:`Error message` field appears, with some example text in gray (:guilabel:`This question requires an answer`). Enter the message that should appear if the applicant attempts to move on to the next question without answering this required one. The text should explain that the question must be answered." +msgstr "" + +#: ../../content/applications/hr/recruitment/new_job.rst:269 +msgid "Layout" +msgstr "" + +#: ../../content/applications/hr/recruitment/new_job.rst:271 +msgid "If the question should only appear if a previous question is answered in a specific way, activate the :guilabel:`Conditional Display` option. A new :guilabel:`Triggering Question` field appears. Using the drop-down menu, select the previous question this new question is linked to. Once a previous question is selected, a :guilabel:`Triggering Answer` field appears. Select the answer that must be selected in order for the new question to appear." +msgstr "" + +#: ../../content/applications/hr/recruitment/new_job.rst:277 +msgid "The next option is :guilabel:`Show Comments Field`. Activate the option if there should be a comment displayed to the applicant. If activated, a :guilabel:`Comment Message` field appears. Enter the text to appear in the :guilabel:`Comment Message` field." +msgstr "" + +#: ../../content/applications/hr/recruitment/new_job.rst:282 +msgid "To further illustrate a triggering question, the following is an example that is applicable to recruitment. The question, `Do you have management experience?` is already added. A new question is then added, `How many years of experience?`. This question should *only* appear if the applicant selected `Yes` to the question `Do you have management experience?`." +msgstr "" + +#: ../../content/applications/hr/recruitment/new_job.rst:287 +msgid "To properly configure this example, activate the :guilabel:`Conditional Display` option. Then, select `Do you have management experience?` as the :guilabel:`Triggering Question`. Then, select :guilabel:`Yes` for the triggering answer." +msgstr "" + +#: ../../content/applications/hr/recruitment/new_job.rst:0 +msgid "The layout field when properly configured for a conditional question." +msgstr "" + +#: ../../content/applications/hr/recruitment/new_job.rst:296 +msgid "Live Sessions" +msgstr "" + +#: ../../content/applications/hr/recruitment/new_job.rst:298 +msgid "If the question is for a live session, activate the :guilabel:`Question Time Limit` option. A :guilabel:`seconds` field appears. Enter the amount of time allotted for the applicant to enter the answer, in seconds." +msgstr "" + +#: ../../content/applications/hr/recruitment/new_job.rst:305 +msgid "Next, configure the various options for the interview form. Click the :guilabel:`Options` tab to view all the options to configure, by category." +msgstr "" + +#: ../../content/applications/hr/recruitment/new_job.rst:311 +msgid ":guilabel:`Pagination`: Choose how the questions should be displayed." +msgstr "" + +#: ../../content/applications/hr/recruitment/new_job.rst:313 +msgid ":guilabel:`One page with all the questions`: Display all sections and questions at the same time." +msgstr "" + +#: ../../content/applications/hr/recruitment/new_job.rst:315 +msgid ":guilabel:`One page per section`: Display each section with the corresponding questions on an individual page." +msgstr "" + +#: ../../content/applications/hr/recruitment/new_job.rst:317 +msgid ":guilabel:`One page per question`: Display a single question on each page." +msgstr "" + +#: ../../content/applications/hr/recruitment/new_job.rst:319 +msgid ":guilabel:`Question Selection`: Choose which questions are presented." +msgstr "" + +#: ../../content/applications/hr/recruitment/new_job.rst:321 +msgid ":guilabel:`All questions`: Display the entire form, with all questions form all sections." +msgstr "" + +#: ../../content/applications/hr/recruitment/new_job.rst:322 +msgid ":guilabel:`Randomized per Section`: Display only a random selection of questions from each section." +msgstr "" + +#: ../../content/applications/hr/recruitment/new_job.rst:326 +msgid "Although it is a selectable option, the :guilabel:`Randomized per section` option should only be used if receiving partial information/an incomplete survey from every applicant is acceptable to the business." +msgstr "" + +#: ../../content/applications/hr/recruitment/new_job.rst:331 +msgid "Time & Scoring" +msgstr "" + +#: ../../content/applications/hr/recruitment/new_job.rst:333 +msgid ":guilabel:`Survey Time Limit`: Check this box to limit the time allowed to complete the form. When selected, a field to enter the minutes appears next to the checked box. Enter the time (using an XX:XX minute/second format) in the field." +msgstr "" + +#: ../../content/applications/hr/recruitment/new_job.rst:336 +msgid ":guilabel:`Scoring`: Choose how the questions should be scored." +msgstr "" + +#: ../../content/applications/hr/recruitment/new_job.rst:338 +msgid ":guilabel:`No scoring`: Select this option to not score the form." +msgstr "" + +#: ../../content/applications/hr/recruitment/new_job.rst:339 +msgid ":guilabel:`Scoring with answers at the end`: Select this option to score the form and display the correct answers for the candidate when they are finished with the form." +msgstr "" + +#: ../../content/applications/hr/recruitment/new_job.rst:341 +msgid ":guilabel:`Scoring without answers at the end`: Select this option to score the form but not display the answers to the candidate." +msgstr "" + +#: ../../content/applications/hr/recruitment/new_job.rst:344 +msgid ":guilabel:`Required Score (%)`: If one of the scoring options was selected, a :guilabel:`Required Score (%)` field appears. Enter the percentage the candidate needs to pass the exam (example, 80.00%). The entry should be written in an “XX.XX” format." +msgstr "" + +#: ../../content/applications/hr/recruitment/new_job.rst:348 +msgid ":guilabel:`Is a Certification`: Check this box if the form is a certification exam. When checked, a drop-down menu appears next to the checkbox. Select one of the default formats for the PDF certificate that will be sent to the candidate after completing the certification exam. Click the :guilabel:`Preview` button to view an example of the PDF certificate." +msgstr "" + +#: ../../content/applications/hr/recruitment/new_job.rst:352 +msgid ":guilabel:`Certified Email Template`: If the :guilabel:`Is a Certification` box is checked, a :guilabel:`Certified Email Template` appears. Select the email template from the drop-down menu that is to be used when the applicant passes the test. Click the :guilabel:`External Link` icon to the right of the email template to preview the email." +msgstr "" + +#: ../../content/applications/hr/recruitment/new_job.rst:358 +msgid "Participants" +msgstr "" + +#: ../../content/applications/hr/recruitment/new_job.rst:360 +msgid ":guilabel:`Access Mode`: Specify who can access the exam. Either :guilabel:`Anyone with the link` or :guilabel:`Invited people only`." +msgstr "" + +#: ../../content/applications/hr/recruitment/new_job.rst:362 +msgid ":guilabel:`Require Login`: Check this box to require candidates to log in before taking the exam, whether they have a valid token or not." +msgstr "" + +#: ../../content/applications/hr/recruitment/new_job.rst:364 +msgid ":guilabel:`Limit Attempts`: If there is a limit to how many times the exam can be taken, check this box, then enter the maximum attempt number in the field next to it." +msgstr "" + +#: ../../content/applications/hr/recruitment/new_job.rst:368 +msgid "Live Session" +msgstr "" + +#: ../../content/applications/hr/recruitment/new_job.rst:370 +msgid ":guilabel:`Session Code`: Enter the access code that will allow the viewers into the live exam session." +msgstr "" + +#: ../../content/applications/hr/recruitment/new_job.rst:372 +msgid ":guilabel:`Reward quick answers`: If the exam is to be taken live, check this box to award more points to participants who answer quickly." +msgstr "" + +#: ../../content/applications/hr/recruitment/new_job.rst:375 +msgid "After all fields have been entered, click the :guilabel:`Save` button to save the changes, or click :guilabel:`Discard` to delete the changes." +msgstr "" + +#: ../../content/applications/hr/recruitment/new_job.rst:-1 +msgid "Various options to configure for the interview form." +msgstr "" + +#: ../../content/applications/hr/recruitment/new_job.rst:385 +msgid "When the applicant begins the survey, the text entered in this tab appears at the top of the survey page. Enter any information or descriptions that would be helpful to the applicant." +msgstr "" + +#: ../../content/applications/hr/recruitment/new_job.rst:389 +msgid "End Message" +msgstr "" + +#: ../../content/applications/hr/recruitment/new_job.rst:391 +msgid "Once the survey is complete the message entered in this tab is displayed for the applicant." +msgstr "" + +#: ../../content/applications/hr/referrals.rst:3 +msgid "Referrals" +msgstr "" + +#: ../../content/applications/hr/referrals.rst:5 +msgid "Odoo's *Referrals* application is a centralized place where all information regarding referrals is housed, from points earned, coworkers hired, and rewards selected. Users can recommend people they know for job positions, then earn referral points as those people progress through the recruitment pipeline. Once enough referral points are earned, they can be exchanged for prizes. The Referrals application integrates with the *Employees*, *Recruitment*, and *Website* applications, all of which must be installed in order for the *Referrals* application to function." +msgstr "" + +#: ../../content/applications/hr/referrals.rst:12 +msgid "The only configuration needed for the Referrals application after it is installed are the :ref:`rewards `; everything else is pre-configured when Odoo Referrals is installed." +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` and :doc:`../general/users/access_rights`." +msgstr "" + +#: ../../content/applications/hr/referrals.rst:23 +msgid "Onboarding" +msgstr "" + +#: ../../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: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:34 +msgid "The text that appears on each slide is as follows:" +msgstr "" + +#: ../../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:38 +msgid ":guilabel:`Browse through open job positions, promote them on social media, or refer friends.`" +msgstr "" + +#: ../../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:40 +msgid ":guilabel:`Compete against your colleagues to build the best justice league!`" +msgstr "" + +#: ../../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: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 "" + +#: ../../content/applications/hr/referrals.rst:-1 +msgid "An onboarding slide with the skip and next buttons visible at the bottom." +msgstr "" + +#: ../../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:65 +msgid "Modifying onboarding slides" +msgstr "" + +#: ../../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: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: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:85 +msgid "To save any changes, click :guilabel:`Save`, or click :guilabel:`Discard` to delete any changes and revert to the original content." +msgstr "" + +#: ../../content/applications/hr/referrals.rst:-1 +msgid "An onboarding slide in edit mode, with the main fields highlighted." +msgstr "" + +#: ../../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 "" + +#: ../../content/applications/hr/referrals.rst:-1 +msgid "The onboarding slides in a list, with the drag and drop arrows highlighted." +msgstr "" + +#: ../../content/applications/hr/referrals.rst:103 +msgid "Share job positions" +msgstr "" + +#: ../../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:113 +msgid "View Jobs" +msgstr "" + +#: ../../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 "" + +#: ../../content/applications/hr/referrals.rst:-1 +msgid "The 'View Jobs' screen, displaying all current open job positions. All information is\n" +"displayed on the card." +msgstr "" + +#: ../../content/applications/hr/referrals.rst:124 +msgid "Each job position card contains the following information:" +msgstr "" + +#: ../../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: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:130 +msgid "The points a user will earn when an applicant applies for the position." +msgstr "" + +#: ../../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: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: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:143 +msgid "Refer friends" +msgstr "" + +#: ../../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: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: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: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 "" + +#: ../../content/applications/hr/referrals.rst:-1 +msgid "Referral email pop-up window with the email message inside it." +msgstr "" + +#: ../../content/applications/hr/referrals.rst:167 +msgid "Share a job" +msgstr "" + +#: ../../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 "" + +#: ../../content/applications/hr/referrals.rst:-1 +msgid "The various sharing icons that appear for each job." +msgstr "" + +#: ../../content/applications/hr/referrals.rst:179 +msgid "Link" +msgstr "" + +#: ../../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:188 +msgid "Facebook" +msgstr "" + +#: ../../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: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: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 "" + +#: ../../content/applications/hr/referrals.rst:-1 +msgid "The view on Facebook when sharing a job description. All the various ways to share are\n" +"highlighted, as are all the required settings." +msgstr "" + +#: ../../content/applications/hr/referrals.rst:216 +msgid "Share to news feed or story" +msgstr "" + +#: ../../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: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: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:236 +msgid "Share on a friend's timeline" +msgstr "" + +#: ../../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: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: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:249 +msgid "Share in a group" +msgstr "" + +#: ../../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: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:264 +msgid "Share in an event" +msgstr "" + +#: ../../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: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:278 +msgid "Share in a private message" +msgstr "" + +#: ../../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: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: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:293 +msgid "X/Twitter" +msgstr "" + +#: ../../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:301 +msgid "The default message is:" +msgstr "" + +#: ../../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: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: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: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: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: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 "" + +#: ../../content/applications/hr/referrals.rst:-1 +msgid "The X/Twitter pop-up when sharing a job description. All the other items than can be added\n" +"to the message are highlighted, as is the visibility setting and the post button." +msgstr "" + +#: ../../content/applications/hr/referrals.rst:336 +msgid "LinkedIn" +msgstr "" + +#: ../../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: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:348 +msgid "Share in a post" +msgstr "" + +#: ../../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: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: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: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:375 +msgid "Finally, once the post is edited and the settings have been selected, click :guilabel:`Post` to share the job position." +msgstr "" + +#: ../../content/applications/hr/referrals.rst:-1 +msgid "A linkedIn post to share a job. The job position is highlighted as is the post button." +msgstr "" + +#: ../../content/applications/hr/referrals.rst:383 +msgid "Send as private message" +msgstr "" + +#: ../../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:399 +msgid "Email a friend" +msgstr "" + +#: ../../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: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:410 +msgid "The email body is also populated with pre-configured text. The text that appears is:" +msgstr "" + +#: ../../content/applications/hr/referrals.rst:412 +msgid "`Hello,`" +msgstr "" + +#: ../../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:416 +msgid "`See Job Offers`" +msgstr "" + +#: ../../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:426 +msgid "Hired referrals" +msgstr "" + +#: ../../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: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: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: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 "" + +#: ../../content/applications/hr/referrals.rst:-1 +msgid "The hired screen. A selection of avatars are presented to chose from, with any already\n" +"chosen are greyed out." +msgstr "" + +#: ../../content/applications/hr/referrals.rst:450 +msgid "Modify friends" +msgstr "" + +#: ../../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: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: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: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: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 "" + +#: ../../content/applications/hr/referrals.rst:-1 +msgid "A friend form in edit mode." +msgstr "" + +#: ../../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: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:491 +msgid "Referral points" +msgstr "" + +#: ../../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: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: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: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:513 +msgid "My referrals" +msgstr "" + +#: ../../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: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: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:527 +msgid "Points" +msgstr "" + +#: ../../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: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: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:542 +msgid "The pre-configured point structure for referrals is as follows:" +msgstr "" + +#: ../../content/applications/hr/referrals.rst:544 +msgid ":guilabel:`Initial Qualification`: 1 point" +msgstr "" + +#: ../../content/applications/hr/referrals.rst:545 +msgid ":guilabel:`First Interview`: 20 points" +msgstr "" + +#: ../../content/applications/hr/referrals.rst:546 +msgid ":guilabel:`Second Interview`: 9 points" +msgstr "" + +#: ../../content/applications/hr/referrals.rst:547 +msgid ":guilabel:`Contract Proposal`: 5 points" +msgstr "" + +#: ../../content/applications/hr/referrals.rst:548 +msgid ":guilabel:`Contract Signed`: 50 points" +msgstr "" + +#: ../../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:557 +msgid "Rewards" +msgstr "" + +#: ../../content/applications/hr/referrals.rst:560 +msgid "Create rewards" +msgstr "" + +#: ../../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:567 +msgid ":guilabel:`Product Name`: Enter the name as it should appear for the reward." +msgstr "" + +#: ../../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: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: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: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: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:582 +msgid "The only required fields are the :guilabel:`Product Name`, :guilabel:`Company`, and :guilabel:`Description`." +msgstr "" + +#: ../../content/applications/hr/referrals.rst:-1 +msgid "A filled out reward form with all details entered." +msgstr "" + +#: ../../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:595 +msgid "Redeem rewards" +msgstr "" + +#: ../../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: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: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 "" + +#: ../../content/applications/hr/referrals.rst:-1 +msgid "Buy button appears below a mug and backpack reward, while the bicycle reward states how\n" +"many more reward points are needed to redeem." +msgstr "" + +#: ../../content/applications/hr/referrals.rst:620 +msgid "Levels" +msgstr "" + +#: ../../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: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: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:636 +msgid "Modify levels" +msgstr "" + +#: ../../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: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: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: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 "" + +#: ../../content/applications/hr/referrals.rst:-1 +msgid "A level form in edit mode." +msgstr "" + +#: ../../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:676 +msgid "Level up" +msgstr "" + +#: ../../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: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:687 +msgid "Leveling up does not cost the user any points, the user simply needs to earn the specified amount of points required." +msgstr "" + +#: ../../content/applications/hr/referrals.rst:-1 +msgid "A 'Click to level up!' appears beneath the user's image, and a large 'Level up!' appears\n" +"above their image." +msgstr "" + +#: ../../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:701 +msgid "Alerts" +msgstr "" + +#: ../../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: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 "" + +#: ../../content/applications/hr/referrals.rst:-1 +msgid "Two alert banners appear above the user's photo." +msgstr "" + +#: ../../content/applications/hr/referrals.rst:718 +msgid "Create an alert" +msgstr "" + +#: ../../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:724 +msgid "Click :guilabel:`Create` and a blank alert form loads. Enter the following information on the form:" +msgstr "" + +#: ../../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: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: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: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: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:739 +msgid ":guilabel:`Not Clickable`: The alert only displays text, there is no link to click." +msgstr "" + +#: ../../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: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 "" + +#: ../../content/applications/hr/referrals.rst:-1 +msgid "An alert form completely filled in with all selections entered." +msgstr "" + +#: ../../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: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: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: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: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 "" + +#: ../../content/applications/hr/time_off.rst:3 +msgid "Time Off" +msgstr "" + +#: ../../content/applications/hr/time_off.rst:5 +msgid "Odoo's *Time Off* application is a centralized place, where all time off information is housed. The *Time Off* app manages everything related to requests, balances, allocations, approvals, and reports." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:9 +msgid "Users can :ref:`request time off `, managers can :ref:`approve time off requests `, :ref:`allocate time off ` to individuals, teams, or the whole company, :ref:`reports ` can be run to see how much time off (and what kinds of time off) are being used, :ref:`accrual plans ` can be created, and :ref:`public holidays ` can be set." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:16 +msgid "Be advised, only users with specific access rights can see all aspects of the *Time Off* application." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:19 +msgid "All users can access the :guilabel:`My Time Off` and :guilabel:`Overview` sections of the *Time Off* application. All other sections require specific access rights." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:22 +msgid "To better understand how access rights affect the *Time Off* application, refer to the :doc:`/applications/hr/employees/new_employee` document, specifically the section about configuring the work information tab." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:27 +msgid "Configuration" +msgstr "" + +#: ../../content/applications/hr/time_off.rst:29 +msgid "In order to allocate time off to employees, and for employees to request and use their time off, the various time off types must be configured first, then allocated to employees (if allocation is required)." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:36 +msgid "Time off types" +msgstr "" + +#: ../../content/applications/hr/time_off.rst:38 +msgid "To view the currently configured time off types, navigate to :menuselection:`Time Off application --> Configuration --> Time Off Types`. The time off types are presented in a list view. The *Time Off* application comes with four types of time off pre-configured: :guilabel:`Paid Time Off`, :guilabel:`Sick Time Off`, :guilabel:`Unpaid`, and :guilabel:`Compensatory Days`. Any of these may be modified to suit the needs of the businesses, or can be used as-is." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:45 +msgid "Create time off type" +msgstr "" + +#: ../../content/applications/hr/time_off.rst:47 +msgid "To create a new time off type, navigate to :menuselection:`Time Off app --> Configuration --> Time Off Types`. From here, click the :guilabel:`Create` button to reveal a blank time off type form." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:50 +msgid "Enter the name for the particular type of time off in the blank line at the top of the form, such as `Sick Time` or `Vacation`. Then, enter the following information on the form:" +msgstr "" + +#: ../../content/applications/hr/time_off.rst:54 +msgid "Time off requests section" +msgstr "" + +#: ../../content/applications/hr/time_off.rst:56 +msgid ":guilabel:`Approval`: select what specific kind of approval is required for the time off type. The options are:" +msgstr "" + +#: ../../content/applications/hr/time_off.rst:59 +msgid ":guilabel:`No Validation`: no approvals are required when requesting this type of time off. The time off request is automatically approved when requested." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:61 +msgid ":guilabel:`By Time Off Officer`: only the specified :ref:`Time Off Officer `, set on this form in the :guilabel:`Responsible Time Off Officer` field, is required to approve the time off request. This option is selected by default." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:64 +msgid ":guilabel:`By Employee's Approver`: only the employee's specified approver for time off, which is set on the *Work Information* tab on the :ref:`employee's form `, is required to approve the time off request." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:67 +msgid ":guilabel:`By Employee's Approver and Time Off Officer`: both the employee's :ref:`specified time off approver` and the :ref:`Time Off Officer ` are required to approve the time off request." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:73 +msgid ":guilabel:`Responsible Time Off Officer`: select the person responsible for approving requests and allocations for this specific type of time off." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:75 +msgid ":guilabel:`Take Time Off in`: select the format the time off is requested from the drop-down menu. The options are:" +msgstr "" + +#: ../../content/applications/hr/time_off.rst:78 +msgid ":guilabel:`Day`: if time off can only be requested in full day increments (8 hours)." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:79 +msgid ":guilabel:`Half Day`: if time off can only be requested in half day increments (4 hours)." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:80 +msgid ":guilabel:`Hours`: if the time off can be taken in hourly increments." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:82 +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 +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 +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 +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 +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 +msgid "Allocation requests section" +msgstr "" + +#: ../../content/applications/hr/time_off.rst:102 +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 +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 +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 +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 +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 +msgid ":guilabel:`No validation needed` indicates that no approvals are required." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:120 +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 +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 +msgid "Payroll section" +msgstr "" + +#: ../../content/applications/hr/time_off.rst:128 +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 +msgid "Timesheets section" +msgstr "" + +#: ../../content/applications/hr/time_off.rst:135 +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 +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 +msgid ":guilabel:`Project`: select the project that the time off type entries appear in." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:142 +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 +msgid "Display option section" +msgstr "" + +#: ../../content/applications/hr/time_off.rst:148 +msgid ":guilabel:`Color`: select a color to be used in the *Time Off* application dashboard." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:149 +msgid ":guilabel:`Cover Image`: select an icon to be used in the *Time Off* application dashboard." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:152 +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 "" + +#: ../../content/applications/hr/time_off.rst:-1 +msgid "Time off type form with all the information filled out for sick time off." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:163 +msgid "Accrual plans" +msgstr "" + +#: ../../content/applications/hr/time_off.rst:165 +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 +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 +msgid "Create accrual plan" +msgstr "" + +#: ../../content/applications/hr/time_off.rst:176 +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 +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 +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 +msgid "Rules must be created in order for the accrual plan to accrue time off." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:195 +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 +msgid "Fill out the following fields on the form:" +msgstr "" + +#: ../../content/applications/hr/time_off.rst:200 +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 +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 +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 +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 +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 +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 +msgid "Depending on the selection, more fields appear to specify exactly when the accrual renews." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:222 +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 +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 +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 +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 +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 "" + +#: ../../content/applications/hr/time_off.rst:-1 +msgid "A level form with all the data filled out." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:242 +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 "" + +#: ../../content/applications/hr/time_off.rst:-1 +msgid "An accrual form with all the entries filled out." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:252 +msgid "Public holidays" +msgstr "" + +#: ../../content/applications/hr/time_off.rst:254 +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 +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 +msgid "Create public holiday" +msgstr "" + +#: ../../content/applications/hr/time_off.rst:263 +msgid "To create a public holiday, navigate to :menuselection:`Time Off app --> Configuration --> Public Holidays`." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:266 +msgid "All currently configured public holidays appear in a list view." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:268 +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 +msgid "Enter the following information:" +msgstr "" + +#: ../../content/applications/hr/time_off.rst:272 +msgid ":guilabel:`Name`: enter the name of the holiday." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:273 +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 +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 +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 +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 +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 +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 "" + +#: ../../content/applications/hr/time_off.rst:-1 +msgid "The list of public holidays in the configuration menu." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:307 +msgid "Overview" +msgstr "" + +#: ../../content/applications/hr/time_off.rst:309 +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 +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 +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 +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 +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 +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 +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 +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 "" + +#: ../../content/applications/hr/time_off.rst:-1 +msgid "Overview of the user's team, with time off requests shown." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:340 +msgid "Allocate time off" +msgstr "" + +#: ../../content/applications/hr/time_off.rst:342 +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 +msgid "To create a new allocation, navigate to :menuselection:`Time Off app --> Approvals --> Allocations`." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:348 +msgid "This presents a list of all current allocations, including their respective status." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:350 +msgid "Click :guilabel:`Create` to allocate time off, and a blank allocation form appears." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:352 +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 +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 +msgid ":guilabel:`Allocation Type`: select either :guilabel:`Regular Allocation` or :guilabel:`Accrual Allocation`." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:359 +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 +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 +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 +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 +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 +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 +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 +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 +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 +msgid "Multiple selections can be made for either :guilabel:`Employees` or :guilabel:`Employee Tag`." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:391 +msgid "Only one selection can be made for the :guilabel:`Company` or :guilabel:`Department`." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:392 +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 +msgid "Request time off" +msgstr "" + +#: ../../content/applications/hr/time_off.rst:400 +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 +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 +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 +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:414 +msgid "Enter the following information on the form:" +msgstr "" + +#: ../../content/applications/hr/time_off.rst:416 +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 +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 +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 +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 +msgid "When the correct dates are selected/highlighted, click the :guilabel:`Apply` button." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:429 +msgid "The dates now populate the :guilabel:`From` and :guilabel:`To` fields." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:431 +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 +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 +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 +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 +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 +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 +msgid "When the form is complete, click the :guilabel:`Save` button to save the information, and submit the request." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:-1 +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 +msgid "Request allocation" +msgstr "" + +#: ../../content/applications/hr/time_off.rst:464 +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 +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 +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 +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 +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 +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 +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 +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 +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 "" + +#: ../../content/applications/hr/time_off.rst:-1 +msgid "An allocation request form filled out for an employee requesting an additional week of\n" +"sick time." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:501 +msgid "Approvals" +msgstr "" + +#: ../../content/applications/hr/time_off.rst:503 +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 +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 +msgid "Approve allocations" +msgstr "" + +#: ../../content/applications/hr/time_off.rst:513 +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 +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 +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 +msgid "The options are :guilabel:`To Approve`, :guilabel:`To Submit`, :guilabel:`Refused`, and :guilabel:`Approved`." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:529 +msgid "To view all allocation requests, click :guilabel:`All`." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:531 +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 +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 +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 +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 +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 +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 +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 +msgid "To approve an allocation request, click :guilabel:`✔ Validate` at the end of the line, to refuse a request, click :guilabel:`✖️ Refuse`." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:-1 +msgid "Allocations with the filter, groupings, and status sections highlighted." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:562 +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 +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 +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 +msgid "Approve time off" +msgstr "" + +#: ../../content/applications/hr/time_off.rst:577 +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 +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 +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 +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 +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 +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 +msgid "To approve a time off request, click :guilabel:`👍 Approve` at the end of the line, to refuse a request, click :guilabel:`✖️ Refuse`." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:-1 +msgid "Time off requests with the filter, groupings, and status sections highlighted." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:612 +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 +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 +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 +msgid "My time off" +msgstr "" + +#: ../../content/applications/hr/time_off.rst:625 +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 +msgid "Dashboard" +msgstr "" + +#: ../../content/applications/hr/time_off.rst:633 +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 +msgid "The current year is displayed, and the current day is highlighted in red." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:639 +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 +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 +msgid "For example, if :guilabel:`Week` is selected, the arrows adjust the view by one week." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:647 +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 +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 +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 +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 +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 +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 "" + +#: ../../content/applications/hr/time_off.rst:-1 +msgid "Time off dashboard view with the legend, time off summaries, and view buttons highlighted." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:676 +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 +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 +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 +msgid "My allocations" +msgstr "" + +#: ../../content/applications/hr/time_off.rst:690 +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 +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 +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 +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 +msgid "By employee" +msgstr "" + +#: ../../content/applications/hr/time_off.rst:709 +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 +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 +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 +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 +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 "" + +#: ../../content/applications/hr/time_off.rst:-1 +msgid "Report of time off, shown by each employee in a stacked bar chart." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:731 +msgid "By type" +msgstr "" + +#: ../../content/applications/hr/time_off.rst:733 +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 +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 +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 "" + +#: ../../content/applications/hr/time_off.rst:-1 +msgid "Report of time off by type, with each request detailed in the list." +msgstr "" diff --git a/locale/sources/inventory_and_mrp.pot b/locale/sources/inventory_and_mrp.pot index 1f6334bfa..9853efae1 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 15.0\n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2024-03-05 13:22+0000\n" +"POT-Creation-Date: 2024-03-20 10:19+0000\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME \n" "Language-Team: LANGUAGE \n" @@ -201,7 +201,7 @@ msgstr "" msgid "This navigates to a new, blank page where the desired product, quantity, and source location must be chosen." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/barcode/operations/adjustments.rst:0 +#: ../../content/applications/inventory_and_mrp/inventory/barcode/operations/adjustments.rst:132 msgid "Keypad to add products on Barcode Inventory Client Action page." msgstr "" @@ -841,6 +841,7 @@ msgid "(91) ([!\"%-/0-9:-?A-Z_a-z]{0,90})" msgstr "" #: ../../content/applications/inventory_and_mrp/inventory/barcode/operations/gs1_nomenclature.rst:225 +#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/putaway.rst:77 msgid "Package type" msgstr "" @@ -897,6 +898,7 @@ msgstr "" #: ../../content/applications/inventory_and_mrp/inventory/barcode/operations/gs1_usage.rst:40 #: ../../content/applications/inventory_and_mrp/inventory/barcode/operations/gs1_usage.rst:168 +#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/putaway.rst:78 msgid "Product" msgstr "" @@ -945,8 +947,8 @@ msgstr "" #: ../../content/applications/inventory_and_mrp/inventory/management/warehouses/resupply_warehouses.rst:11 #: ../../content/applications/inventory_and_mrp/inventory/management/warehouses/warehouses_locations.rst:44 #: ../../content/applications/inventory_and_mrp/inventory/routes/concepts/cross_dock.rst:18 -#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/putaway.rst:18 -#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/putaway.rst:84 +#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/putaway.rst:21 +#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/putaway.rst:104 #: ../../content/applications/inventory_and_mrp/inventory/shipping/operation/invoicing.rst:16 #: ../../content/applications/inventory_and_mrp/inventory/shipping/operation/label_type.rst:13 #: ../../content/applications/inventory_and_mrp/inventory/shipping/operation/labels.rst:15 @@ -2611,7 +2613,7 @@ msgstr "" msgid "**Manually assign lot numbers**: Click :guilabel:`Add a line` and choose the location the products will be stored in under the :guilabel:`To` column. Then, type a new :guilabel:`Lot Number Name` and set the :guilabel:`Done` quantity." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/lots.rst:0 +#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/lots.rst:144 msgid "Assign lot number detailed operations popup." msgstr "" @@ -2623,7 +2625,7 @@ msgstr "" msgid "**Copy/paste lot numbers from a spreadsheet**: Populate a spreadsheet with all of the lot numbers received from the supplier (or manually chosen to assign upon receipt). Then, copy and paste them in the :guilabel:`Lot/Serial Number Name` column. Odoo will automatically create the necessary number of lines based on the amount of numbers pasted in the column. From here, the :guilabel:`To` locations and :guilabel:`Done` quantities can be manually entered in each of the lot number lines." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/lots.rst:0 +#: ../../content/applications/inventory_and_mrp/inventory/management/lots_serial_numbers/lots.rst:159 msgid "List of lot numbers copied on excel spreadsheet." msgstr "" @@ -7083,175 +7085,227 @@ msgstr "" msgid "Putaway rules" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/putaway.rst:6 -msgid "What is a Putaway Rule?" +#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/putaway.rst:5 +msgid "Putaway is the process of routing products to appropriate storage locations upon shipment arrival." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/putaway.rst:8 -msgid "A good warehouse implementation makes sure that products automatically move to their appropriate destination location. To make that process easier, Odoo uses *Putaway Rules*. Putaway is the process of taking products from the received shipments and putting them into the appropriate location." +#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/putaway.rst:7 +msgid "Odoo can accomplish this seamlessly using *putaway rules*, which dictate how products move through specified warehouse locations." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/putaway.rst:10 +msgid "Upon shipment arrival, operations are generated based on putaway rules to efficiently move products to specified locations, and ensure easy retrieval for future delivery orders." msgstr "" #: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/putaway.rst:13 -msgid "If, for example, a warehouse contains volatile substances, it is important to make sure that certain products are not stored close to each other because of a potential chemical reaction. That's where putaway rules intervene, to avoid storing products wrongly." +msgid "In warehouses that process specific kinds of products, putaway rules can also prevent volatile substances from being stored in close proximity, by directing them to different locations determined by the warehouse manager." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/putaway.rst:20 -msgid "In the :guilabel:`Inventory` app, go to :menuselection:`Configuration --> Settings` and activate the :guilabel:`Multi-Step Routes` feature. By doing so, the :guilabel:`Storage Locations` feature is also automatically activated." +#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/putaway.rst:18 +msgid "`Odoo Tutorials: Putaway Rules `_" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/putaway.rst:23 +msgid "To use putaway rules, navigate to :menuselection:`Inventory app --> Configuration --> Settings`, and activate the :guilabel:`Multi-Step Routes` feature under the :guilabel:`Warehouse` section. By doing so, the :guilabel:`Storage Locations` feature is also automatically activated." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/putaway.rst:27 +msgid "Finally, click :guilabel:`Save`." msgstr "" #: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/putaway.rst:-1 msgid "Activate Multi-Step Routes in Inventory configuration settings." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/putaway.rst:29 -msgid "Setting up a putaway rule" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/putaway.rst:31 -msgid "In some cases, like for a retail shop storing fruits and vegetables, products should be stored in different locations depending on several factors like frequency, size, product category, specific environment needs, and so on." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/putaway.rst:35 -msgid "In this example, suppose there is one warehouse location, **WH/Stock**, with the following sub-locations:" +#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/putaway.rst:36 +msgid "Define putaway rule" msgstr "" #: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/putaway.rst:38 -msgid "WH/Stock/Pallets" +msgid "To manage where specific products are routed for storage, navigate to :menuselection:`Inventory app --> Configuration --> Putaway Rules`. Use the :guilabel:`Create` button to configure a new putaway rule on a :guilabel:`Product` or :guilabel:`Product Category` that the rule affects." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/putaway.rst:40 -msgid "WH/Stock/Pallets/PAL1" +#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/putaway.rst:43 +msgid "Putaway rules can be defined either per product/product category, and/or package type (the *Packages* setting must be enabled in :menuselection:`Inventory app --> Configuration --> Settings` for that)." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/putaway.rst:41 -msgid "WH/Stock/Pallets/PAL2" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/putaway.rst:42 -msgid "WH/Stock/Pallets/PAL3" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/putaway.rst:44 -msgid "WH/Stock/Shelf 1" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/putaway.rst:46 -msgid "WH/Stock/Shelf 2" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/putaway.rst:48 -msgid "WH/Stock/Shelf 2/Small Refrigerator" +#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/putaway.rst:47 +msgid "In the same line, the :guilabel:`When product arrives in` location is where the putaway rule is triggered to create an operation to move the product to the :guilabel:`Store to` location." msgstr "" #: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/putaway.rst:50 -msgid "WH/Stock/Shelf 3" +msgid "For this to work, the :guilabel:`Store to` location must be a *sub-location* of the first (e.g., `WH/Stock/Fruits` is a specific, named location inside `WH/Stock` to make the products stored here easier to find)." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/putaway.rst:52 -msgid "Manage those locations with putaway rules. To create a putaway rule, open the :guilabel:`Inventory` app and go to :menuselection:`Configuration --> Putaway Rules`. Then, click on :guilabel:`Create` and configure a putaway rule that indicated the main location the product will enter before being redirected to the right storage location." +#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/putaway.rst:55 +msgid "In a warehouse location, **WH/Stock**, there are the following sub-locations:" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/putaway.rst:57 +msgid "WH/Stock/Fruits" msgstr "" #: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/putaway.rst:58 -msgid "The putaway rules can be defined either per product/product category and/or package type (the :guilabel:`Packages` setting must be enabled for that). Putaway rules are read sequentially until a match is found." +msgid "WH/Stock/Vegetables" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/putaway.rst:62 -msgid "Take the following example:" +#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/putaway.rst:60 +msgid "Ensure all apples are stored in the fruits section by filling the field :guilabel:`Store to` with the location `WH/Stock/Fruits` when the :guilabel:`Product`, `Apple` arrives in `WH/Stock`." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/putaway.rst:64 -msgid "If water (category All/drinks) is received, whatever the package, it will be redirected to WH/Stock/Shelf 2/Small Refrigerator." +#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/putaway.rst:63 +msgid "Repeat this for all products and hit :guilabel:`Save`." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/putaway.rst:66 -msgid "If orange juice cans, packaged in boxes, are received, they will be redirected to WH/Stock/Shelf 2." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/putaway.rst:68 -msgid "If water or apple juice bottles, packaged in boxes, are received, they will be redirected to WH/Stock/Shelf 3." +#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/putaway.rst:0 +msgid "Create putaway rules for apples and carrots." msgstr "" #: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/putaway.rst:70 -msgid "If a pallet of lemonade cans are receieved, it will be redirected to WH/Stock/Pallets/PAL1." +msgid "Putaway rule priority" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/putaway.rst:-1 -msgid "Some examples of putaway rules." +#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/putaway.rst:72 +msgid "Odoo selects a putaway rule based on the following priority list (from highest to lowest) until a match is found:" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/putaway.rst:77 -msgid "Using Storage Categories" +#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/putaway.rst:75 +msgid "Package type and product" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/putaway.rst:76 +msgid "Package type and product category" msgstr "" #: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/putaway.rst:79 -msgid "A *Storage Category* is an extra location attribute. Storage categories allow the user to define the quantity of products that can be stored in the location and how the location will be selected with putaway rules." +msgid "Product category" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/putaway.rst:82 +msgid "The product `Lemonade can` has the following putaway rules configured:" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/putaway.rst:84 +msgid "When receiving a `Pallet` (:guilabel:`Package Type`) of `Lemonade cans`, it is redirected to `WH/Stock/Pallets/PAL1`." msgstr "" #: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/putaway.rst:86 -msgid "In the :guilabel:`Inventory` app, go to :menuselection:`Configuration --> Settings` and activate the :guilabel:`Storage Categories` feature. By doing so, the :guilabel:`Storage Locations` feature is also automatically activated." +msgid "`Lemonade can`'s :guilabel:`Product Category` is `All/drinks`, and when receiving a `Box` of any item in this product category, items are redirected to `WH/Stock/Shelf 1`." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/putaway.rst:91 -msgid "Create a Storage Category" +#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/putaway.rst:88 +msgid "Any product on a `Pallet` is redirected to `WH/Stock/Pallets`" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/putaway.rst:93 -msgid "To create a storage category, go to :menuselection:`Inventory --> Configuration --> Storage Categories` and click :guilabel:`Create`. Then, click :guilabel:`Save` and click :guilabel:`Storage Categories` or go to :menuselection:`Configuration --> Storage Categories` to create a new storage category." +#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/putaway.rst:89 +msgid "The product `Lemonade can` is redirected to `WH/Stock/Shelf 2`" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/putaway.rst:-1 -msgid "Create Storage Categories inside Odoo Inventory configuration settings." +#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/putaway.rst:90 +msgid "Items in the `All/drinks` product category are redirected to `WH/Stock/Small Refrigerator`." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/putaway.rst:102 -msgid "First, click :guilabel:`Create` and type a name for the storage category." +#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/putaway.rst:0 +msgid "Some examples of putaway rules." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/putaway.rst:104 -msgid "Then, there are options to limit the capacity by weight, by product, or by package type. The :guilabel:`Allow New Product` field defines when the location is considered available to store a product:" +#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/putaway.rst:97 +msgid "Storage categories" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/putaway.rst:108 -msgid ":guilabel:`If location is empty`: a product can be added there only if the location is empty." +#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/putaway.rst:99 +msgid "A *storage category* is an extra location attribute. Storage categories allow the user to define the quantity of products that can be stored in the location, and how the location will be selected with putaway rules." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/putaway.rst:109 -msgid ":guilabel:`If products are the same`: a product can be added there only if the same product is already there." +#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/putaway.rst:106 +msgid "To enable storage categories, go to :menuselection:`Inventory app --> Configuration --> Settings`, and activate the :guilabel:`Storage Categories` feature in the :guilabel:`Warehouse` section. Then, click :guilabel:`Save`." msgstr "" #: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/putaway.rst:111 -msgid ":guilabel:`Allow mixed products`: several different products can be stored in this location at the same time." +msgid "The :guilabel:`Storage Locations` feature **must** be enabled to enable :guilabel:`Storage Categories`." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/putaway.rst:114 -msgid "Once the storage category settings are saved, the storage category can be linked to a location." +#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/putaway.rst:115 +msgid "Define storage category" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/putaway.rst:-1 -msgid "When a Storage Category is created, it can be linked to a warehouse location." +#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/putaway.rst:117 +msgid "To create a storage category, go to :menuselection:`Inventory app --> Configuration --> Storage Categories` and click :guilabel:`Create`." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/putaway.rst:121 -msgid "Storage categories in putaway rules" +#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/putaway.rst:120 +msgid "On the storage category form, type a name for the :guilabel:`Storage Category` field." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/putaway.rst:123 -msgid "To continue the example from above, apply the \"High Frequency Pallets\" on the PAL1 and PAL2 locations and rework the putaway rules as follows:" +#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/putaway.rst:122 +msgid "Options are available to limit the capacity by weight, by product, or by package type. The :guilabel:`Allow New Product` field defines when the location is considered available to store a product:" msgstr "" #: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/putaway.rst:126 -msgid "Assume one pallet of lemonade cans is received:" +msgid ":guilabel:`If location is empty`: a product can be added there only if the location is empty." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/putaway.rst:128 -msgid "If PAL1 and PAL2 are empty, the pallet will be redirected to WH/Stock/Pallets/PAL1." +#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/putaway.rst:127 +msgid ":guilabel:`If products are the same`: a product can be added there only if the same product is already there." msgstr "" #: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/putaway.rst:129 +msgid ":guilabel:`Allow mixed products`: several different products can be stored in this location at the same time." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/putaway.rst:133 +msgid "Create putaway rules for pallet-stored items and ensure real-time storage capacity checks by creating the `High Frequency pallets` storage category." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/putaway.rst:136 +msgid "Name the :guilabel:`Storage Category`, and select :guilabel:`If all products are same` in the :guilabel:`Allow New Product` field." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/putaway.rst:139 +msgid "Then, define package capacity in the :guilabel:`Capacity by Package` tab, specifying the number of packages for the designated :guilabel:`Package Type` and setting a maximum of `2.00` `Pallets` for a specific location." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/putaway.rst:0 +msgid "Create a storage category on the page." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/putaway.rst:147 +msgid "Once the storage category settings are saved, the storage category can be linked to a location." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/putaway.rst:149 +msgid "To do that, navigate to the location by going to :menuselection:`Inventory app --> Configuration --> Locations`, and select the location. Click :guilabel:`Edit` and select the created category in the :guilabel:`Storage Category` field." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/putaway.rst:154 +msgid "Assign the `High Frequency pallets` storage category to the `WH/Stock/pallets/PAL 1` sub-location." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/putaway.rst:0 +msgid "When a Storage Category is created, it can be linked to a warehouse location." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/putaway.rst:162 +msgid "Storage categories in putaway rules" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/putaway.rst:164 +msgid "To continue the example from above, apply the `High Frequency Pallets` on the `PAL1` and `PAL2` locations and :ref:`rework the putaway rules ` as follows:" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/putaway.rst:167 +msgid "Assume one pallet of lemonade cans is received:" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/putaway.rst:169 +msgid "If PAL1 and PAL2 are empty, the pallet will be redirected to WH/Stock/Pallets/PAL1." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/putaway.rst:170 msgid "If PAL1 is full, the pallet will be redirected to WH/Stock/Pallets/PAL2." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/putaway.rst:130 +#: ../../content/applications/inventory_and_mrp/inventory/routes/strategies/putaway.rst:171 msgid "If PAL1 and 2 are full, the pallet will be redirected to WH/Stock/Pallets." msgstr "" @@ -8465,7 +8519,7 @@ msgid "`Odoo Tutorials: MRP `_" 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/maintenance.rst:5 diff --git a/locale/sources/productivity.pot b/locale/sources/productivity.pot index ed3c996ab..b83d96b02 100644 --- a/locale/sources/productivity.pot +++ b/locale/sources/productivity.pot @@ -8,7 +8,7 @@ msgid "" msgstr "" "Project-Id-Version: Odoo 15.0\n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2024-03-05 13:22+0000\n" +"POT-Creation-Date: 2024-03-20 10:19+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 @@ -382,4590 +381,3744 @@ 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:99 +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/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:98 -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:99 -msgid ":doc:`plan_activities`" +#: ../../content/applications/productivity/discuss/team_communication.rst:98 +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 type of file (max 64MB per file on Odoo Online), and organize them in various workspaces." +msgstr "" + +#: ../../content/applications/productivity/documents.rst:11 +msgid "`Odoo Documents: product page `_" +msgstr "" + +#: ../../content/applications/productivity/documents.rst:14 +msgid "Workflow actions" +msgstr "" + +#: ../../content/applications/productivity/documents.rst:16 +msgid "Workflow actions are automated actions you can create and customize at the level of each workspace. They appear next to a file whenever it meets the criteria you set. That way you can, for example, add tags to a file or move it to another workspace with a single click. Workflow actions help you streamline the management of your documents and your overall business operations." +msgstr "" + +#: ../../content/applications/productivity/documents.rst:22 +msgid "Create workflow actions" +msgstr "" + +#: ../../content/applications/productivity/documents.rst:24 +msgid "To create workflow actions, go to :menuselection:`Documents --> Configuration --> Workspaces` and select the workspace where the action should apply. Click on the *Actions* smart button, and then on *Create*." +msgstr "" + +#: ../../content/applications/productivity/documents.rst:-1 +msgid "Workflow actions smart button in Odoo Documents" +msgstr "" + +#: ../../content/applications/productivity/documents.rst:33 +msgid "An action applies to all *Child Workspaces* under the *Parent Workspace* you selected." +msgstr "" + +#: ../../content/applications/productivity/documents.rst:36 +msgid "If you use the :ref:`developer mode `, you can directly access all your actions by going to :menuselection:`Documents --> Configuration --> Actions`." +msgstr "" + +#: ../../content/applications/productivity/documents.rst:40 +msgid "Set the conditions" +msgstr "" + +#: ../../content/applications/productivity/documents.rst:42 +msgid "After naming your workflow action, you can set the conditions that trigger the appearance of the action button on the right-side panel when selecting a file." +msgstr "" + +#: ../../content/applications/productivity/documents.rst:45 +msgid "There are three basic types of conditions you can set:" +msgstr "" + +#: ../../content/applications/productivity/documents.rst:47 +msgid "**Tags**: you can both use the *Contains* and *Does not contain* conditions, meaning the files *must have* or *mustn't have* the tags set here." +msgstr "" + +#: ../../content/applications/productivity/documents.rst:50 +msgid "**Contact**: the files must be associated with the contact set here." +msgstr "" + +#: ../../content/applications/productivity/documents.rst:52 +msgid "**Owner**: the files must be associated with the owner set here." +msgstr "" + +#: ../../content/applications/productivity/documents.rst:-1 +msgid "Example of a workflow action's basic condition in Odoo Documents" +msgstr "" + +#: ../../content/applications/productivity/documents.rst:59 +msgid "If you don't set any conditions, the action button appears for all files located inside the selected workspace." +msgstr "" + +#: ../../content/applications/productivity/documents.rst:63 +msgid "Advanced condition type: domain" +msgstr "" + +#: ../../content/applications/productivity/documents.rst:66 +msgid "It is recommended to have some knowledge of Odoo development to properly configure *Domain* filters." +msgstr "" + +#: ../../content/applications/productivity/documents.rst:69 +msgid "To access the *Domain* condition, the :ref:`developer mode ` needs to be activated. Once that's done, select the *Domain* condition type, and click on *Add Filter*." +msgstr "" + +#: ../../content/applications/productivity/documents.rst:-1 +msgid "Activating the domain condition type in Odoo Documents" +msgstr "" + +#: ../../content/applications/productivity/documents.rst:76 +msgid "To create a rule, you typically select a field, an operator, and a value. For example, if you want to add a workflow action to all the PDF files inside a workspace, set the field to *Mime Type*, the operator to *contains*, and the value to *pdf*." +msgstr "" + +#: ../../content/applications/productivity/documents.rst:-1 +msgid "Example of a workflow action's domain condition in Odoo Documents" +msgstr "" + +#: ../../content/applications/productivity/documents.rst:84 +msgid "Click on *Add node* (plus-circle icon) and *Add branch* (ellipsis icon) to add conditions and sub-conditions. You can then specify if your rule should match *ALL* or *ANY* conditions. You can also edit the rule directly using the *Code editor*." +msgstr "" + +#: ../../content/applications/productivity/documents.rst:-1 +msgid "Add a node or a branch to a workflow action's condition in Odoo Documents" +msgstr "" + +#: ../../content/applications/productivity/documents.rst:93 +msgid "Configure the actions" +msgstr "" + +#: ../../content/applications/productivity/documents.rst:95 +msgid "Select the *Actions* tab to set up your action. You can simultaneously:" +msgstr "" + +#: ../../content/applications/productivity/documents.rst:97 +msgid "**Set Contact**: add a contact to the file, or replace an existing contact with a new one." +msgstr "" + +#: ../../content/applications/productivity/documents.rst:98 +msgid "**Set Owner**: add an owner to the file, or replace an existing owner with a new one." +msgstr "" + +#: ../../content/applications/productivity/documents.rst:99 +msgid "**Move to Workspace**: move the file to any workspace." +msgstr "" + +#: ../../content/applications/productivity/documents.rst:100 +msgid "**Create**: create one of the following items attached to the file in your database:" +msgstr "" + +#: ../../content/applications/productivity/documents.rst:102 +msgid "**Product template**: create a product you can edit directly." +msgstr "" + +#: ../../content/applications/productivity/documents.rst:103 +msgid "**Task**: create a Project task you can edit directly." +msgstr "" + +#: ../../content/applications/productivity/documents.rst:104 +msgid "**Signature request**: create a new Sign template to send out." +msgstr "" + +#: ../../content/applications/productivity/documents.rst:105 +msgid "**Sign directly**: create a Sign template to sign directly." +msgstr "" + +#: ../../content/applications/productivity/documents.rst:106 +msgid "**Vendor bill**: create a vendor bill using OCR and AI to scrape information from the file content." +msgstr "" + +#: ../../content/applications/productivity/documents.rst:108 +msgid "**Customer invoice**: create a customer invoice using OCR and AI to scrape information from the file." +msgstr "" + +#: ../../content/applications/productivity/documents.rst:110 +msgid "**Vendor credit note**: create a vendor credit note using OCR and AI to scrape information from the file." +msgstr "" + +#: ../../content/applications/productivity/documents.rst:112 +msgid "**Credit note**: create a customer credit note using OCR and AI to scrape information from the file." +msgstr "" + +#: ../../content/applications/productivity/documents.rst:114 +msgid "**Applicant**: create a new HR application you can edit directly." +msgstr "" + +#: ../../content/applications/productivity/documents.rst:116 +msgid "**Set Tags**: add, remove, and replace any number of tags." +msgstr "" + +#: ../../content/applications/productivity/documents.rst:117 +msgid "**Activities - Mark all as Done**: mark all activities linked to the file as done." +msgstr "" + +#: ../../content/applications/productivity/documents.rst:118 +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/documents.rst:-1 +msgid "Example of a workflow action Odoo Documents" +msgstr "" + +#: ../../content/applications/productivity/sign.rst:3 +msgid "Sign" +msgstr "" + +#: ../../content/applications/productivity/sign.rst:5 +msgid "**Odoo Sign** allows you to send, sign and approve documents online." +msgstr "" + +#: ../../content/applications/productivity/sign.rst:7 +msgid "You can upload any PDF file and add drag-and-dropping fields on it. These fields are automatically filled out with the user's detail if they are logged in." +msgstr "" + +#: ../../content/applications/productivity/sign.rst:11 +msgid "`Odoo Sign: product page `_" +msgstr "" + +#: ../../content/applications/productivity/sign.rst:12 +msgid "`Odoo Tutorials: Sign `_" +msgstr "" + +#: ../../content/applications/productivity/sign.rst:17 +msgid "Validity of electronic signatures" +msgstr "" + +#: ../../content/applications/productivity/sign.rst:19 +msgid "The legal validity of electronic signatures generated by Odoo depends on the legislation of your country. Companies doing business abroad should consider electronic signature laws of other countries as well." +msgstr "" + +#: ../../content/applications/productivity/sign.rst:24 +msgid "In the European Union" +msgstr "" + +#: ../../content/applications/productivity/sign.rst:26 +msgid "The `eIDAS regulation `_ establishes the framework for electronic signatures in all `27 member states of the European Union `_." +msgstr "" + +#: ../../content/applications/productivity/sign.rst:30 +msgid "It distinguishes three types of electronic signatures:" +msgstr "" + +#: ../../content/applications/productivity/sign.rst:32 +msgid "Electronic signatures" +msgstr "" + +#: ../../content/applications/productivity/sign.rst:33 +msgid "Advanced electronic signatures" +msgstr "" + +#: ../../content/applications/productivity/sign.rst:34 +msgid "Qualified electronic signatures" +msgstr "" + +#: ../../content/applications/productivity/sign.rst:36 +msgid "Odoo generates the first type, regular electronic signatures, and these signatures can produce legal effects in the EU, as the regulation states that “an electronic signature shall not be denied legal effect and admissibility as evidence in legal proceedings solely on the grounds that it is in an electronic form or that it does not meet the requirements for qualified electronic signatures.”" +msgstr "" + +#: ../../content/applications/productivity/sign.rst:41 +msgid "Note that electronic signatures may not be automatically recognized as valid. You may need to bring supporting evidence of a signature’s validity." +msgstr "" + +#: ../../content/applications/productivity/sign.rst:45 +msgid "In the United States of America" +msgstr "" + +#: ../../content/applications/productivity/sign.rst:47 +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/sign.rst:56 +msgid "Overall, to be recognized as valid, electronic signatures have to meet five criteria:" +msgstr "" + +#: ../../content/applications/productivity/sign.rst:58 +msgid "A 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 electronically signing a document." +msgstr "" + +#: ../../content/applications/productivity/sign.rst:61 +msgid "A signer must first express or imply their consent to conduct business electronically." +msgstr "" + +#: ../../content/applications/productivity/sign.rst:62 +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/sign.rst:64 +msgid "The signature must be associated with the document being signed, for example, by keeping a record detailing how the signature was captured." +msgstr "" + +#: ../../content/applications/productivity/sign.rst:66 +msgid "Electronically signed documents need to be retained and available for later reference by all parties involved, for example, by providing the signer either a fully-executed copy or the option to download a copy." +msgstr "" + +#: ../../content/applications/productivity/sign.rst:71 +msgid "The information provided here does not constitute legal advice; it is provided for general informational purposes only. As laws governing electronic signatures rapidly evolve, we cannot guarantee whether all information is up to date or not. We advise contacting a local attorney for legal advice regarding electronic signature compliance and validity." +msgstr "" + +#: ../../content/applications/productivity/sign.rst:79 +msgid "Field Types" +msgstr "" + +#: ../../content/applications/productivity/sign.rst:81 +msgid "By configuring your own *Field Types*, also known as *Signature Item Types*, you can make the signing process even faster for your customers, partners, and employees." +msgstr "" + +#: ../../content/applications/productivity/sign.rst:84 +msgid "To create and customize fields, activate the :ref:`developer mode `. Then head to :menuselection:`Documents --> Configuration --> Field Types` and click on *Create*." +msgstr "" + +#: ../../content/applications/productivity/sign.rst:87 +msgid "After giving your new field a name, select one of the six *Types* available:" +msgstr "" + +#: ../../content/applications/productivity/sign.rst:89 +msgid "**Signature**: users are prompted to enter their signature either by drawing it, automatically generating one based on their name, or uploading a local file (usually an image). Each subsequent *Signature* field then reuses the data entered in the first field." +msgstr "" + +#: ../../content/applications/productivity/sign.rst:92 +msgid "**Initial**: users are prompted to enter their initials, in a similar way to the *Signature* field." +msgstr "" + +#: ../../content/applications/productivity/sign.rst:94 +msgid "**Text**: users enter text on a single line." +msgstr "" + +#: ../../content/applications/productivity/sign.rst:95 +msgid "**Multiline Text**: users enter text on multiple lines." +msgstr "" + +#: ../../content/applications/productivity/sign.rst:96 +msgid "**Checkbox**: users can tick a box (e.g.,to mark their approval or consent)." +msgstr "" + +#: ../../content/applications/productivity/sign.rst:97 +msgid "**Selection**: users choose a single option from a variety of options." +msgstr "" + +#: ../../content/applications/productivity/sign.rst:99 +msgid "Next, you have the option to auto-complete fields for users based on their Odoo profile information by using *Automatic Partner Field*. To this end, the *Name*, *Email*, *Phone*, and *Company* fields are preconfigured in your database." +msgstr "" + +#: ../../content/applications/productivity/sign.rst:104 +msgid "Users can freely edit auto-completed fields." +msgstr "" + +#: ../../content/applications/productivity/sign.rst:-1 +msgid "Company field example in Odoo Sign" +msgstr "" + +#: ../../content/applications/productivity/sign.rst:110 +msgid "You can then change the size of the field by editing the *Default Width* and *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/sign.rst:115 +msgid "Next, write a *Tip*. Tips are displayed inside arrows on the left-hand side of the user's screen during the signing process. You can also use a *Placeholder* text to be displayed inside the field before it is completed." +msgstr "" + +#: ../../content/applications/productivity/sign.rst:-1 +msgid "Tip and placeholder example in Odoo Sign" +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: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/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/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/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/iot/config/connect.rst:11 -msgid "`IoT Box FAQ `_" +#: ../../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/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/voip/axivox/axivox_config.rst:27 +msgid ":guilabel:`WebSocket`: type in `wss://pabx.axivox.com:3443`" msgstr "" -#: ../../content/applications/productivity/iot/config/connect.rst:-1 -msgid "The Internet of Things (IoT) app on the Odoo database." +#: ../../content/applications/productivity/voip/axivox/axivox_config.rst:28 +msgid ":guilabel:`VoIP Environment`: set as :guilabel:`Production`" 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/voip/axivox/axivox_config.rst:-1 +msgid "Integration of Axivox as VoIP provider in an Odoo database." msgstr "" -#: ../../content/applications/productivity/iot/config/connect.rst:-1 -msgid "Connecting an IoT box to the Odoo database." +#: ../../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/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/voip/axivox/axivox_config.rst:40 +msgid "Configure VoIP user in Odoo" msgstr "" -#: ../../content/applications/productivity/iot/config/connect.rst:-1 -msgid "Connection steps for a wired connection or WiFi connection." +#: ../../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/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/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/iot/config/connect.rst:46 -msgid "Ethernet connection" +#: ../../content/applications/productivity/voip/axivox/axivox_config.rst:49 +msgid ":guilabel:`SIP Login` / :guilabel:`Browser's Extension`: (Axivox) :guilabel:`SIP username`" 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/voip/axivox/axivox_config.rst:50 +msgid ":guilabel:`Handset Extension`: SIP external phone extension" 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/voip/axivox/axivox_config.rst:51 +msgid ":guilabel:`SIP Password`: (Axivox) :guilabel:`SIP Password`" 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/voip/axivox/axivox_config.rst:52 +msgid ":guilabel:`Mobile call`: method to make calls on a mobile device" 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/voip/axivox/axivox_config.rst:53 +msgid ":guilabel:`OnSIP authorization User`: (Axivox) :guilabel:`SIP username`" 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/voip/axivox/axivox_config.rst:54 +msgid ":guilabel:`Always Redirect to Handset`: option to always transfer phone calls to handset" 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/voip/axivox/axivox_config.rst:55 +msgid ":guilabel:`Reject All Incoming Calls`: option to reject all incoming calls" msgstr "" -#: ../../content/applications/productivity/iot/config/connect.rst:79 -msgid "WiFi connection" +#: ../../content/applications/productivity/voip/axivox/axivox_config.rst:-1 +msgid "Integration of Axivox user in the Odoo user preference." 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/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/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/voip/axivox/axivox_config.rst:0 +msgid "SIP credentials in the Axivox manager." 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/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/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/voip/axivox/call_queues.rst:3 +msgid "Call queues" msgstr "" -#: ../../content/applications/productivity/iot/config/connect.rst:-1 -msgid "WiFi networks available on the computer." +#: ../../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/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/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/iot/config/connect.rst:-1 -msgid "Enter the server token into the IoT box." +#: ../../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/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/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/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/voip/axivox/call_queues.rst:19 +msgid ":ref:`voip/axivox/music_on_hold`" msgstr "" -#: ../../content/applications/productivity/iot/config/connect.rst:-1 -msgid "Configuring the WiFi for the IoT box." +#: ../../content/applications/productivity/voip/axivox/call_queues.rst:22 +msgid "Add a queue" 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/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/iot/config/connect.rst:-1 -msgid "The IoT box has been successfully configured on the Odoo database." +#: ../../content/applications/productivity/voip/axivox/call_queues.rst:30 +msgid "Name" 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/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/iot/config/connect.rst:139 -msgid "Manually connecting the IoT box using the token" +#: ../../content/applications/productivity/voip/axivox/call_queues.rst:35 +msgid "Internal extension" 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/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/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/voip/axivox/call_queues.rst:41 +msgid "Strategy" 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/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/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/voip/axivox/call_queues.rst:46 +msgid "The following choices are available in the :guilabel:`Strategy` drop-down menu:" 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/voip/axivox/call_queues.rst:48 +msgid ":guilabel:`Call all available agents`" msgstr "" -#: ../../content/applications/productivity/iot/config/connect.rst:167 -msgid "IoT box schema" +#: ../../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/iot/config/connect.rst:170 -msgid "Raspberry Pi 4" +#: ../../content/applications/productivity/voip/axivox/call_queues.rst:50 +msgid ":guilabel:`Calls the agent who has received the least call`" msgstr "" -#: ../../content/applications/productivity/iot/config/connect.rst:174 -msgid "The Odoo IoT box (Raspberry Pi 4) schema with labels." +#: ../../content/applications/productivity/voip/axivox/call_queues.rst:51 +msgid ":guilabel:`Call a random agent`" msgstr "" -#: ../../content/applications/productivity/iot/config/connect.rst:177 -msgid "Raspberry Pi 3" +#: ../../content/applications/productivity/voip/axivox/call_queues.rst:52 +msgid ":guilabel:`Call agents one after the other`" msgstr "" -#: ../../content/applications/productivity/iot/config/connect.rst:181 -msgid "The Odoo IoT box (Raspberry Pi 3) schema with labels." +#: ../../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/iot/config/flash_sdcard.rst:3 -msgid "Flashing the SD card" +#: ../../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/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/voip/axivox/call_queues.rst:58 +msgid "Maximum waiting time in seconds" msgstr "" -#: ../../content/applications/productivity/iot/config/flash_sdcard.rst:10 -msgid "Upgrade from the IoT box home page" +#: ../../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/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/voip/axivox/call_queues.rst:65 +msgid "Maximum duration of ringing at an agent" 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/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/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/voip/axivox/call_queues.rst:72 +msgid "For more information on dial plans, visit:" msgstr "" -#: ../../content/applications/productivity/iot/config/flash_sdcard.rst:-1 -msgid "IoT box software upgrade in the IoT Box Home Page." +#: ../../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/iot/config/flash_sdcard.rst:34 -msgid "Upgrade with Etcher Software" +#: ../../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/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/voip/axivox/call_queues.rst:78 +msgid "Adding agents" 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/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/iot/config/flash_sdcard.rst:44 -msgid "Then download the version-specific :abbr:`IoT (Internet of Things)` image from `nightly `_." +#: ../../content/applications/productivity/voip/axivox/call_queues.rst:87 +msgid "Static agents" 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/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/iot/config/flash_sdcard.rst:50 -msgid "Odoo V16 --> iotbox-latest.zip" +#: ../../content/applications/productivity/voip/axivox/call_queues.rst:95 +msgid "Dynamic agents" msgstr "" -#: ../../content/applications/productivity/iot/config/flash_sdcard.rst:51 -msgid "Odoo V15 --> iotboxv21_10.zip" +#: ../../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/iot/config/flash_sdcard.rst:52 -msgid "Odoo V14 --> iotboxv21_04.zip" +#: ../../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/iot/config/flash_sdcard.rst:53 -msgid "Odoo V13 --> iotboxv20_10.zip" +#: ../../content/applications/productivity/voip/axivox/call_queues.rst:104 +msgid "Agent connection" 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/voip/axivox/call_queues.rst:106 +msgid "There are three ways call agents can connect to an Axivox call queue:" 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/voip/axivox/call_queues.rst:108 +msgid "Dynamic agents connect automatically." msgstr "" -#: ../../content/applications/productivity/iot/config/flash_sdcard.rst:-1 -msgid "Balena's Etcher software dashboard." +#: ../../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/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/voip/axivox/call_queues.rst:111 +msgid "Agent connects to the queue in Odoo, via the *VoIP* widget." msgstr "" -#: ../../content/applications/productivity/iot/config/https_certificate_iot.rst:5 -msgid "HTTPS certificate (IoT)" +#: ../../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/iot/config/https_certificate_iot.rst:8 -msgid "What is HTTPS?" +#: ../../content/applications/productivity/voip/axivox/call_queues.rst:118 +msgid "Connect via Axivox queue" 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/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/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/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/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/voip/axivox/call_queues.rst:127 +msgid ":guilabel:`Name`: name of the queue." 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/voip/axivox/call_queues.rst:128 +msgid ":guilabel:`Extension`: number of the extension to be dialed to reach the queue." msgstr "" -#: ../../content/applications/productivity/iot/config/https_certificate_iot.rst:29 -msgid "Why is it needed?" +#: ../../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/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/voip/axivox/call_queues.rst:130 +msgid ":guilabel:`Agent disconnection`: number to dial to log out of the queue." 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/voip/axivox/call_queues.rst:131 +msgid ":guilabel:`Connected Agents`: name of agent connected to the queue." 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/voip/axivox/call_queues.rst:133 +msgid "The following buttons are also available on the :guilabel:`Queues` dashboard:" 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/voip/axivox/call_queues.rst:135 +msgid ":guilabel:`Connect an agent`: manually connect an agent to the queue." msgstr "" -#: ../../content/applications/productivity/iot/config/https_certificate_iot.rst:48 -msgid "Internet of Things (IoT) eligibility" +#: ../../content/applications/productivity/voip/axivox/call_queues.rst:136 +msgid ":guilabel:`Report`: run a report on the queue." 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/voip/axivox/call_queues.rst:137 +msgid ":guilabel:`Delete`: delete the queue." msgstr "" -#: ../../content/applications/productivity/iot/config/https_certificate_iot.rst:52 -msgid "The Odoo subscription must:" +#: ../../content/applications/productivity/voip/axivox/call_queues.rst:138 +msgid ":guilabel:`Edit`: make changes to the settings of the queue." msgstr "" -#: ../../content/applications/productivity/iot/config/https_certificate_iot.rst:54 -msgid "Have an :guilabel:`IoT Box Subscription` line." +#: ../../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/iot/config/https_certificate_iot.rst:55 -msgid ":guilabel:`Status` must be :guilabel:`In Progress`." +#: ../../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/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/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/iot/config/https_certificate_iot.rst:0 -msgid "Odoo.com portal subscriptions filtered by \"in progress\"." +#: ../../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/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/voip/axivox/call_queues.rst:154 +msgid "For more information on static and dynamic agents, see this documentation:" 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/voip/axivox/call_queues.rst:156 +msgid ":ref:`voip/axivox/static-agents`" msgstr "" -#: ../../content/applications/productivity/iot/config/https_certificate_iot.rst:72 -msgid "Troubleshooting Hypertext Transfer Protocol Secure (HTTPS) certificate errors" +#: ../../content/applications/productivity/voip/axivox/call_queues.rst:157 +msgid ":ref:`voip/axivox/dynamic-agents`" 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/voip/axivox/call_queues.rst:160 +msgid "Report" 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/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/iot/config/https_certificate_iot.rst:84 -msgid "`ERR_IOT_HTTPS_CHECK_NO_SERVER`" +#: ../../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/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/voip/axivox/call_queues.rst:170 +msgid "When the custom configurations have been entered, click :guilabel:`Apply`." 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/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/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/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/iot/config/https_certificate_iot.rst:91 -msgid "Ensure that the server is configured." +#: ../../content/applications/productivity/voip/axivox/call_queues.rst:178 +msgid ":guilabel:`The caller quit`" msgstr "" -#: ../../content/applications/productivity/iot/config/https_certificate_iot.rst:94 -msgid ":doc:`/applications/productivity/iot/config/connect`" +#: ../../content/applications/productivity/voip/axivox/call_queues.rst:179 +msgid ":guilabel:`An agent is connecting`" msgstr "" -#: ../../content/applications/productivity/iot/config/https_certificate_iot.rst:97 -msgid "`ERR_IOT_HTTPS_CHECK_CERT_READ_EXCEPTION`" +#: ../../content/applications/productivity/voip/axivox/call_queues.rst:180 +msgid ":guilabel:`An agent is disconnecting`" 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/voip/axivox/call_queues.rst:181 +msgid ":guilabel:`The call was terminated (agent hangs up)`" 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/voip/axivox/call_queues.rst:182 +msgid ":guilabel:`The call was terminated (caller hangs up)`" msgstr "" -#: ../../content/applications/productivity/iot/config/https_certificate_iot.rst:107 -msgid "`ERR_IOT_HTTPS_LOAD_NO_CREDENTIAL`" +#: ../../content/applications/productivity/voip/axivox/call_queues.rst:183 +msgid ":guilabel:`The caller is connected to an agent.`" 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/voip/axivox/call_queues.rst:184 +msgid ":guilabel:`Someone is entering the queue`" 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`." +#: ../../content/applications/productivity/voip/axivox/call_queues.rst:185 +msgid ":guilabel:`The caller exits the queue (no agent is connected)`" msgstr "" -#: ../../content/applications/productivity/iot/config/https_certificate_iot.rst:117 -msgid "`ERR_IOT_HTTPS_LOAD_REQUEST_EXCEPTION`" +#: ../../content/applications/productivity/voip/axivox/call_queues.rst:186 +msgid ":guilabel:`The caller exits the queue (timeout)`" 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:" +#: ../../content/applications/productivity/voip/axivox/call_queues.rst:187 +msgid ":guilabel:`No one is answering`" 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." +#: ../../content/applications/productivity/voip/axivox/call_queues.rst:188 +msgid ":guilabel:`No one is answering, the caller hangs up`" 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.)." +#: ../../content/applications/productivity/voip/axivox/call_queues.rst:189 +msgid ":guilabel:`Transfer`" 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." +#: ../../content/applications/productivity/voip/axivox/call_queues.rst:190 +msgid ":guilabel:`Blind Transfer`" 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." +#: ../../content/applications/productivity/voip/axivox/call_queues.rst:-1 +msgid "Event types in the Axivox queue reporting feature." msgstr "" -#: ../../content/applications/productivity/iot/config/https_certificate_iot.rst:140 -msgid "`ERR_IOT_HTTPS_LOAD_REQUEST_STATUS`" +#: ../../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/iot/config/https_certificate_iot.rst:143 -msgid "The IoT-box was able to reach ``_ but received an unusual `HTTP response (status codes) `_." +#: ../../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/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." +#: ../../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/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." +#: ../../content/applications/productivity/voip/axivox/call_queues.rst:-1 +msgid "Axivox queue report with result, event type, and period highlighted." 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." +#: ../../content/applications/productivity/voip/axivox/call_queues.rst:209 +msgid "Connect to queue on Odoo" 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." +#: ../../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/iot/config/https_certificate_iot.rst:162 -msgid "`ERR_IOT_HTTPS_LOAD_REQUEST_NO_RESULT`" +#: ../../content/applications/productivity/voip/axivox/call_queues.rst:215 +msgid ":doc:`axivox_config`" 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." +#: ../../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/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 `." +#: ../../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/iot/config/https_certificate_iot.rst:173 -msgid "How to ensure that the HTTPS certificate is correct" +#: ../../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/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." +#: ../../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/iot/config/https_certificate_iot.rst:-1 -msgid "Odoo IoT app IoT box with .odoo-iot.com domain." +#: ../../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/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." +#: ../../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/iot/config/https_certificate_iot.rst:191 -msgid "Example of valid SSL certificate details on the browser." +#: ../../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/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)`." +#: ../../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/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." +#: ../../content/applications/productivity/voip/axivox/conference_calls.rst:3 +msgid "Conference calls" msgstr "" -#: ../../content/applications/productivity/iot/config/https_certificate_iot.rst:-1 -msgid "IoT box homepage with HTTPS certificate OK status." +#: ../../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/iot/config/https_certificate_iot.rst:202 -msgid "Domain Name System (DNS) issue" +#: ../../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/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`)." +#: ../../content/applications/productivity/voip/axivox/conference_calls.rst:12 +msgid "Add a virtual conference" 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:" +#: ../../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/iot/config/https_certificate_iot.rst:213 -msgid "Chrome" +#: ../../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/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." +#: ../../content/applications/productivity/voip/axivox/conference_calls.rst:-1 +msgid "New conference form on Axivox." msgstr "" -#: ../../content/applications/productivity/iot/config/https_certificate_iot.rst:222 -msgid "Firefox" +#: ../../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/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." +#: ../../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/iot/config/https_certificate_iot.rst:230 -msgid "Edge" +#: ../../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/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." +#: ../../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/iot/config/https_certificate_iot.rst:240 -msgid "Domain Name System (DNS) issue solution" +#: ../../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/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 `_." +#: ../../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/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." +#: ../../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/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)`." +#: ../../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/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." +#: ../../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/iot/config/pos.rst:3 -msgid "Use an IoT box with a PoS" +#: ../../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/iot/config/pos.rst:6 -msgid "Prerequisites" +#: ../../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/iot/config/pos.rst:8 -msgid "Before starting, make sure the following equipment is available:" +#: ../../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/iot/config/pos.rst:10 -msgid "An :abbr:`IoT (Internet of Things)` box, with its power adapter." +#: ../../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/iot/config/pos.rst:11 -msgid "A computer or tablet with an up-to-date web browser." +#: ../../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/iot/config/pos.rst:12 -msgid "Odoo Online or an Odoo instance with the *Point of Sale* and *IoT* applications installed." +#: ../../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/iot/config/pos.rst:13 -msgid "A local network set up with :abbr:`DHCP (Dynamic Host Configuration Protocol)` (this is the default setting)." +#: ../../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/iot/config/pos.rst:15 -msgid "An RJ45 Ethernet Cable (optional, but preferred over WiFi, which is already built in)." +#: ../../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/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 `_." +#: ../../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/iot/config/pos.rst:21 -msgid "Setup" +#: ../../content/applications/productivity/voip/axivox/conference_calls.rst:87 +msgid "Start call in Odoo" msgstr "" -#: ../../content/applications/productivity/iot/config/pos.rst:25 -msgid "A suggested configuration for a point of sale system." +#: ../../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/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 `." +#: ../../content/applications/productivity/voip/axivox/conference_calls.rst:-1 +msgid "Connecting to a conference extension using the Odoo VoIP widget." msgstr "" -#: ../../content/applications/productivity/iot/config/pos.rst:31 -msgid "Then, connect the peripheral devices to the :abbr:`IoT (Internet of Things)` box." +#: ../../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/iot/config/pos.rst:37 -msgid "Device Name" +#: ../../content/applications/productivity/voip/axivox/dial_plan_advanced.rst:3 +msgid "Advanced dial plans" msgstr "" -#: ../../content/applications/productivity/iot/config/pos.rst:38 -msgid "Instructions" +#: ../../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/iot/config/pos.rst:39 -#: ../../content/applications/productivity/iot/config/troubleshooting.rst:66 -msgid "Printer" +#: ../../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/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`." +#: ../../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/iot/config/pos.rst:43 -#: ../../content/applications/productivity/iot/config/troubleshooting.rst:412 -msgid "Cash drawer" +#: ../../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/iot/config/pos.rst:44 -msgid "The cash drawer should be connected to the printer with an RJ25 cable." +#: ../../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/iot/config/pos.rst:45 -#: ../../content/applications/productivity/iot/config/troubleshooting.rst:360 -msgid "Barcode scanner" +#: ../../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/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." +#: ../../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/iot/config/pos.rst:48 -msgid "Scale" +#: ../../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/iot/config/pos.rst:49 -msgid "Connect the scale and power it on. Refer to :doc:`/applications/productivity/iot/devices/scale`." +#: ../../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/iot/config/pos.rst:51 -msgid "Customer display" +#: ../../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/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`." +#: ../../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/iot/config/pos.rst:54 -msgid "Payment terminal" +#: ../../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/iot/config/pos.rst:55 -msgid "The connection process depends on the terminal. Refer to the :doc:`payment terminals documentation `." +#: ../../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/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." +#: ../../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/iot/config/pos.rst:-1 -msgid "Configuring the connected devices in the POS application." +#: ../../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/iot/config/pos.rst:67 -msgid "Once set up is done, a new :abbr:`PoS (Point of Sale)` session can be launched." +#: ../../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/iot/config/troubleshooting.rst:3 +#: ../../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:135 +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:146 +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 +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 `VoIP OnSIP`." +msgstr "" + +#: ../../content/applications/productivity/voip/onsip.rst:25 +msgid "Next, install 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:`SIP Login` / :guilabel:`Browser's Extension` = OnSIP :guilabel:`Username`" +msgstr "" + +#: ../../content/applications/productivity/voip/onsip.rst:78 +msgid ":guilabel:`OnSIP authorization User` = OnSIP :guilabel:`Auth Username`" +msgstr "" + +#: ../../content/applications/productivity/voip/onsip.rst:79 +msgid ":guilabel:`Handset Extension` = OnSIP :guilabel:`Ext.` (extension without the `x`)" +msgstr "" + +#: ../../content/applications/productivity/voip/onsip.rst:80 +msgid ":guilabel:`SIP Password` = OnSIP :guilabel:`SIP Password`" +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, click :guilabel:`Save` on the user form in Odoo to save the configurations." +msgstr "" + +#: ../../content/applications/productivity/voip/onsip.rst:93 +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:97 +msgid "Additional setup and troubleshooting steps can be found on `OnSIP's knowledge base `_." +msgstr "" + +#: ../../content/applications/productivity/voip/onsip.rst:101 +msgid "Incoming calls" +msgstr "" + +#: ../../content/applications/productivity/voip/onsip.rst:103 +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:106 +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:114 +msgid ":doc:`voip_widget`" +msgstr "" + +#: ../../content/applications/productivity/voip/onsip.rst:117 +#: ../../content/applications/productivity/voip/voip_widget.rst:32 msgid "Troubleshooting" msgstr "" -#: ../../content/applications/productivity/iot/config/troubleshooting.rst:6 -msgid "IoT box connection" +#: ../../content/applications/productivity/voip/onsip.rst:120 +msgid "Missing parameters" msgstr "" -#: ../../content/applications/productivity/iot/config/troubleshooting.rst:9 -msgid "Unable to locate the pairing code to connect the IoT box" +#: ../../content/applications/productivity/voip/onsip.rst:122 +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/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." +#: ../../content/applications/productivity/voip/onsip.rst:-1 +msgid "Missing parameter message in the Odoo VoIP widget." msgstr "" -#: ../../content/applications/productivity/iot/config/troubleshooting.rst:14 -msgid "The pairing code does not show under the following circumstances:" +#: ../../content/applications/productivity/voip/onsip.rst:130 +msgid "Incorrect number" msgstr "" -#: ../../content/applications/productivity/iot/config/troubleshooting.rst:16 -msgid "The :abbr:`IoT (Internet of Things)` box is already connected to an Odoo database." +#: ../../content/applications/productivity/voip/onsip.rst:132 +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/iot/config/troubleshooting.rst:17 -msgid "The :abbr:`IoT (Internet of Things)` box is not connected to the Internet." +#: ../../content/applications/productivity/voip/onsip.rst:139 +msgid "For example, `16505555555` (where `1` is the international prefix for the United States)." 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." +#: ../../content/applications/productivity/voip/onsip.rst:-1 +msgid "Incorrect number message populated in the Odoo VoIP widget." 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 `)." +#: ../../content/applications/productivity/voip/onsip.rst:150 +msgid "OnSIP on mobile phone" 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." +#: ../../content/applications/productivity/voip/onsip.rst:152 +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/iot/config/troubleshooting.rst:30 -msgid "IoT box is connected but it is not showing in the database" +#: ../../content/applications/productivity/voip/onsip.rst:155 +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/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." +#: ../../content/applications/productivity/voip/onsip.rst:159 +msgid ":doc:`devices_integrations`" 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." +#: ../../content/applications/productivity/voip/onsip.rst:160 +msgid "`OnSIP App Download `_" msgstr "" -#: ../../content/applications/productivity/iot/config/troubleshooting.rst:41 -msgid "The IoT box is connected to the Odoo database, but cannot be reached" +#: ../../content/applications/productivity/voip/transfer_forward.rst:3 +msgid "Make, receive, transfer, and forward calls" 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." +#: ../../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/iot/config/troubleshooting.rst:48 -msgid "The HTTPS certificate does not generate" +#: ../../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/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." +#: ../../content/applications/productivity/voip/transfer_forward.rst:12 +msgid "Make calls" 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." +#: ../../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/iot/config/troubleshooting.rst:63 -msgid ":doc:`HTTPS certificate (IoT) `" +#: ../../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/iot/config/troubleshooting.rst:69 -msgid "The printer is not detected" +#: ../../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/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`." +#: ../../content/applications/productivity/voip/transfer_forward.rst:-1 +msgid "Using the VoIP phone widget to make calls." msgstr "" -#: ../../content/applications/productivity/iot/config/troubleshooting.rst:-1 -msgid "The IoT box Home Page landing page." +#: ../../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/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." +#: ../../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/iot/config/troubleshooting.rst:83 -msgid "The printer outputs random text" +#: ../../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/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." +#: ../../content/applications/productivity/voip/transfer_forward.rst:45 +msgid "Receive calls" 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." +#: ../../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/iot/config/troubleshooting.rst:-1 -msgid "Edit the printer connected to the IoT box." +#: ../../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/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." +#: ../../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/iot/config/troubleshooting.rst:104 -msgid "Epson configuration special case" +#: ../../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/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:" +#: ../../content/applications/productivity/voip/transfer_forward.rst:61 +msgid "Add to call queue" msgstr "" -#: ../../content/applications/productivity/iot/config/troubleshooting.rst:109 -msgid "TM-U220" +#: ../../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/iot/config/troubleshooting.rst:110 -msgid "TM-U230" +#: ../../content/applications/productivity/voip/transfer_forward.rst:-1 +msgid "VoIP widget with next activities highlighted, showing tasks below." msgstr "" -#: ../../content/applications/productivity/iot/config/troubleshooting.rst:111 -msgid "TM-P60" +#: ../../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/iot/config/troubleshooting.rst:112 -msgid "TMP-P60II" +#: ../../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/iot/config/troubleshooting.rst:114 -msgid "Bypass this issue by configuring the printer to use the `ESC *` command instead." +#: ../../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/iot/config/troubleshooting.rst:117 -msgid "Process to force ESC * command" +#: ../../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/iot/config/troubleshooting.rst:120 -msgid "Epson printer compatibility" +#: ../../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/iot/config/troubleshooting.rst:122 -msgid "The first step is to check whether the printer is incompatible with `GS v 0` command." +#: ../../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/iot/config/troubleshooting.rst:126 -msgid "`Epson GS v 0 documentation `_ for `GS v 0` compatible printers." +#: ../../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/iot/config/troubleshooting.rst:128 -msgid "`Epson ESC * documentation `_ for `ESC *` compatible printers." +#: ../../content/applications/productivity/voip/transfer_forward.rst:93 +msgid "Next, set a :guilabel:`Due Date`, and add a :guilabel:`Summary`." 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." +#: ../../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/iot/config/troubleshooting.rst:136 -msgid "IoT box configuration for ESC *" +#: ../../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/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." +#: ../../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/iot/config/troubleshooting.rst:143 -msgid "**Choosing the printer**" +#: ../../content/applications/productivity/voip/transfer_forward.rst:107 +msgid "Transfer calls" 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`." +#: ../../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/iot/config/troubleshooting.rst:150 -msgid "If the name of the printer is still uncertain, take the following steps:" +#: ../../content/applications/productivity/voip/transfer_forward.rst:115 +msgid "For more information on transfers, visit :ref:`voip/axivox/forwardings_tab`." msgstr "" -#: ../../content/applications/productivity/iot/config/troubleshooting.rst:152 -msgid "Take note of the listed printers on the *CUPS* page." +#: ../../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/iot/config/troubleshooting.rst:153 -msgid "Turn the printer off and refresh the page." +#: ../../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/iot/config/troubleshooting.rst:154 -msgid "Now compare the difference with the first list to see which printer disappeared." +#: ../../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/iot/config/troubleshooting.rst:155 -msgid "Turn the printer back on and refresh the page again." +#: ../../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/iot/config/troubleshooting.rst:156 -msgid "Double-check the list again to see if the printer re-appears." +#: ../../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/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." +#: ../../content/applications/productivity/voip/transfer_forward.rst:137 +msgid "Forward calls" msgstr "" -#: ../../content/applications/productivity/iot/config/troubleshooting.rst:161 -msgid "This can be :guilabel:`Unknown` under :guilabel:`Local printers`." +#: ../../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/iot/config/troubleshooting.rst:163 -msgid "**CUPS naming convention**" +#: ../../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/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." +#: ../../content/applications/productivity/voip/transfer_forward.rst:147 +msgid "For more information on forwarding, visit :ref:`voip/axivox/forwardings_tab`." msgstr "" -#: ../../content/applications/productivity/iot/config/troubleshooting.rst:170 -msgid "The :guilabel:`Name` should match this convention: `__IMC___...___`" +#: ../../content/applications/productivity/voip/voip_widget.rst:3 +msgid "VoIP widget" msgstr "" -#: ../../content/applications/productivity/iot/config/troubleshooting.rst:173 -msgid "A breakdown of the naming convention:" +#: ../../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/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)." +#: ../../content/applications/productivity/voip/voip_widget.rst:10 +msgid "Phone calls" msgstr "" -#: ../../content/applications/productivity/iot/config/troubleshooting.rst:177 -msgid "`IMC`: This stands for *Image Mode Column* (the simplified name for `ESC *`)." +#: ../../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/iot/config/troubleshooting.rst:178 -msgid "`param_1`: This stands for the specific parameter:" +#: ../../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/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." +#: ../../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/iot/config/troubleshooting.rst:184 -msgid "`100` is the original size, `50` is half the size, `200` is twice the size." +#: ../../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/iot/config/troubleshooting.rst:186 -msgid "`LDV`: *Low Density Vertical* (will be set to *High Density Vertical* if not specified)." +#: ../../content/applications/productivity/voip/voip_widget.rst:-1 +msgid "VoIP call in Odoo." msgstr "" -#: ../../content/applications/productivity/iot/config/troubleshooting.rst:187 -msgid "`LDH`: *Low Density Horizontal* (will be set to *High Density Horizontal* if not specified)." +#: ../../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/iot/config/troubleshooting.rst:190 -msgid "*Density* parameters might need to be configured in a particular way depending on the printer model." +#: ../../content/applications/productivity/voip/voip_widget.rst:0 +msgid "\"Missing Parameter\" error message in the Odoo softphone." 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." +#: ../../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/iot/config/troubleshooting.rst:199 -msgid "The following are examples of proper and improper name formatting:" +#: ../../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/iot/config/troubleshooting.rst:201 -msgid "Proper name formatting:" +#: ../../content/applications/productivity/voip/voip_widget.rst:0 +msgid "\"Incorrect Number\" error message in the Odoo softphone." msgstr "" -#: ../../content/applications/productivity/iot/config/troubleshooting.rst:203 -msgid "`EPSONTMm30II__IMC__`" +#: ../../content/applications/productivity/voip/voip_widget.rst:54 +msgid "Tabs" msgstr "" -#: ../../content/applications/productivity/iot/config/troubleshooting.rst:204 -msgid "`EPSON_TM_U220__IMC_LDV_LDH_SCALE80__`" +#: ../../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/iot/config/troubleshooting.rst:206 -msgid "Improper name formatting (this will not prevent printing, but the result might not have the expected printed output):" +#: ../../content/applications/productivity/voip/voip_widget.rst:61 +msgid "Recent" msgstr "" -#: ../../content/applications/productivity/iot/config/troubleshooting.rst:209 -msgid "`EPSON TMm 30II` -> The name cannot have spaces." +#: ../../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/iot/config/troubleshooting.rst:210 -msgid "`EPSONTMm30II` -> The name itself is correct, but it will not use `ESC *`." +#: ../../content/applications/productivity/voip/voip_widget.rst:67 +msgid "Next activities" msgstr "" -#: ../../content/applications/productivity/iot/config/troubleshooting.rst:211 -msgid "`EPSONTMm30II__IMC` -> This name is missing the end `__`." +#: ../../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/iot/config/troubleshooting.rst:212 -msgid "`EPSONTMm30II__IMC_XDV__` -> The parameter `XDV` does not match any existing parameters." +#: ../../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/iot/config/troubleshooting.rst:213 -msgid "`EPSONTMm30II__IMC_SCALE__` -> The parameter `SCALE` is missing the scale value." +#: ../../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/iot/config/troubleshooting.rst:215 -msgid "**Finish adding a printer**" +#: ../../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/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)`." +#: ../../content/applications/productivity/voip/voip_widget.rst:-1 +msgid "Activity control center on the VoIP widget." 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." +#: ../../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/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)." +#: ../../content/applications/productivity/voip/voip_widget.rst:88 +msgid "Under the :guilabel:`Document` section, from right to left:" msgstr "" -#: ../../content/applications/productivity/iot/config/troubleshooting.rst:227 -msgid "**Adding the printer to Odoo PoS**" +#: ../../content/applications/productivity/voip/voip_widget.rst:90 +msgid ":guilabel:`➣ (paper airplane)` icon: sends an email" 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`." +#: ../../content/applications/productivity/voip/voip_widget.rst:91 +msgid ":guilabel:`👤 (person icon)` icon: redirects to the contact card" 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." +#: ../../content/applications/productivity/voip/voip_widget.rst:92 +msgid ":guilabel:`📄 (document)` icon: redirects to the attached record in Odoo" msgstr "" -#: ../../content/applications/productivity/iot/config/troubleshooting.rst:240 -msgid "**Example setup of the Epson TM-U220B printer using ESC**" +#: ../../content/applications/productivity/voip/voip_widget.rst:93 +msgid ":guilabel:`🕓 (clock)` icon: schedule an activity" 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):" +#: ../../content/applications/productivity/voip/voip_widget.rst:95 +msgid "Under the :guilabel:`Activity` section, from left to right:" msgstr "" -#: ../../content/applications/productivity/iot/config/troubleshooting.rst:0 -msgid "Properly formatted receipt picture from a demo database." +#: ../../content/applications/productivity/voip/voip_widget.rst:97 +msgid ":guilabel:`✔️ (checkmark)` icon: mark activity as done" 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:" +#: ../../content/applications/productivity/voip/voip_widget.rst:98 +msgid ":guilabel:`✏️ (pencil)` icon: edit the activity" msgstr "" -#: ../../content/applications/productivity/iot/config/troubleshooting.rst:0 -msgid "Printer paper with seemingly random characters." +#: ../../content/applications/productivity/voip/voip_widget.rst:99 +msgid ":guilabel:`✖️ (cancel)` icon: cancel the activity" 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." +#: ../../content/applications/productivity/voip/voip_widget.rst:102 +msgid "Contacts" 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 *`." +#: ../../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/iot/config/troubleshooting.rst:0 -msgid "Epson compatibility evaluation from Epson website." +#: ../../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/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/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/measurement_tool.rst:66 -#: ../../content/applications/productivity/iot/devices/printer.rst:70 -msgid ":doc:`../../../inventory_and_mrp/manufacturing/quality_control/quality_control_points`" -msgstr "" - -#: ../../content/applications/productivity/iot/devices/camera.rst:59 -#: ../../content/applications/productivity/iot/devices/measurement_tool.rst:67 -#: ../../content/applications/productivity/iot/devices/printer.rst:71 -msgid ":doc:`../../../inventory_and_mrp/manufacturing/quality_control/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:90 -#: ../../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:5 -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:9 -msgid "Find the list of supported devices here: `Supported devices `_." -msgstr "" - -#: ../../content/applications/productivity/iot/devices/measurement_tool.rst:13 -msgid "Connect with universal serial bus (USB)" -msgstr "" - -#: ../../content/applications/productivity/iot/devices/measurement_tool.rst:15 -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:24 -msgid "Connect with bluetooth" -msgstr "" - -#: ../../content/applications/productivity/iot/devices/measurement_tool.rst:26 -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:35 -msgid "Link a measurement tool to a quality control point in the manufacturing process" -msgstr "" - -#: ../../content/applications/productivity/iot/devices/measurement_tool.rst:37 -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:41 -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:45 -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:48 -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:56 -#: ../../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:61 -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:70 -msgid "Link a measurement tool to a work center in the Manufacturing app" -msgstr "" - -#: ../../content/applications/productivity/iot/devices/measurement_tool.rst:72 -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:76 -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:82 -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:86 -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." -msgstr "" - -#: ../../content/applications/productivity/mail_plugins.rst:5 -msgid "Mail Plugins" -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:" -msgstr "" - -#: ../../content/applications/productivity/mail_plugins.rst:16 -msgid "Creating leads and centralizing prospects' emails into the CRM app." -msgstr "" - -#: ../../content/applications/productivity/mail_plugins.rst:17 -msgid "Generating tasks in any Odoo project." -msgstr "" - -#: ../../content/applications/productivity/mail_plugins.rst:18 -msgid "Creating tickets in the Helpdesk app." -msgstr "" - -#: ../../content/applications/productivity/mail_plugins.rst:19 -msgid "Searching and storing insights on your contacts." -msgstr "" - -#: ../../content/applications/productivity/mail_plugins.rst:21 -msgid "Mail Plugins are available for :doc:`Outlook ` and :doc:`Gmail `." -msgstr "" - -#: ../../content/applications/productivity/mail_plugins.rst:27 -msgid "Pricing" -msgstr "" - -#: ../../content/applications/productivity/mail_plugins.rst:29 -msgid "Mail Plugins are **free** to install and use." -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**." -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." -msgstr "" - -#: ../../content/applications/productivity/mail_plugins.rst:41 -msgid "Lead Generation IAP service" -msgstr "" - -#: ../../content/applications/productivity/mail_plugins.rst:43 -msgid "Lead Enrichment uses the *Lead Generation IAP service*. Each request consumes one *Lead Generation credit*." -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." -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." -msgstr "" - -#: ../../content/applications/productivity/mail_plugins.rst:52 -msgid "Check out the `Lead Generation IAP service Privacy Policy `_." -msgstr "" - -#: ../../content/applications/productivity/mail_plugins.rst:56 -msgid ":doc:`../general/in_app_purchase`" -msgstr "" - -#: ../../content/applications/productivity/mail_plugins.rst:57 -msgid "`Odoo Tutorials: Lead Enrichment `_" -msgstr "" - -#: ../../content/applications/productivity/mail_plugins/gmail.rst:3 -msgid "Gmail Plugin" -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." -msgstr "" - -#: ../../content/applications/productivity/mail_plugins/gmail.rst:9 -msgid "Odoo Online users" -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." -msgstr "" - -#: ../../content/applications/productivity/mail_plugins/gmail.rst:15 -#: ../../content/applications/productivity/mail_plugins/gmail.rst:94 -msgid "Install the Gmail Plugin" -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." -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." -msgstr "" - -#: ../../content/applications/productivity/mail_plugins/gmail.rst:-1 -msgid "Plus sign icon on the Gmail inbox side panel." -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`." -msgstr "" - -#: ../../content/applications/productivity/mail_plugins/gmail.rst:-1 -msgid "Odoo Inbox Addin on Google Workspace Marketplace." -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 `_." -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." -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." -msgstr "" - -#: ../../content/applications/productivity/mail_plugins/gmail.rst:43 -#: ../../content/applications/productivity/mail_plugins/gmail.rst:134 -msgid "Configure the Odoo database" -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`." -msgstr "" - -#: ../../content/applications/productivity/mail_plugins/gmail.rst:-1 -msgid "The Mail Plugin feature in the Settings." -msgstr "" - -#: ../../content/applications/productivity/mail_plugins/gmail.rst:55 -#: ../../content/applications/productivity/mail_plugins/gmail.rst:145 -msgid "Configure the Gmail inbox" -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." -msgstr "" - -#: ../../content/applications/productivity/mail_plugins/gmail.rst:-1 -msgid "The Authorize Access button in the right sidebar of the Odoo plugin panel." -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." -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`." -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." -msgstr "" - -#: ../../content/applications/productivity/mail_plugins/gmail.rst:78 -msgid "Odoo On-Premise users" -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." -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 `_.)" -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." -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." -msgstr "" - -#: ../../content/applications/productivity/mail_plugins/gmail.rst:-1 -msgid "Download the ZIP file from the Odoo GitHub repository for Mail Plugins." -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." -msgstr "" - -#: ../../content/applications/productivity/mail_plugins/gmail.rst:108 -msgid "Delete the following three lines of text from the :file:`login.ts` file:" -msgstr "" - -#: ../../content/applications/productivity/mail_plugins/gmail.rst:116 -msgid "This removes the `odoo.com` domain constraint from the Gmail Plugin program." -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." -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." -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." -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." -msgstr "" - -#: ../../content/applications/productivity/mail_plugins/outlook.rst:3 -msgid "Outlook Plugin" -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." -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." -msgstr "" - -#: ../../content/applications/productivity/mail_plugins/outlook.rst:17 -msgid "Enable Mail Plugin" -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." -msgstr "" - -#: ../../content/applications/productivity/mail_plugins/outlook.rst:25 -msgid "Install the Outlook Plugin" -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 `_." -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`." -msgstr "" - -#: ../../content/applications/productivity/mail_plugins/outlook.rst:-1 -msgid "More actions button in Outlook" -msgstr "" - -#: ../../content/applications/productivity/mail_plugins/outlook.rst:38 -msgid "Following this step, select the :guilabel:`My add-ins` tab on the left-side." -msgstr "" - -#: ../../content/applications/productivity/mail_plugins/outlook.rst:-1 -msgid "My add-ins in Outlook" -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...`" -msgstr "" - -#: ../../content/applications/productivity/mail_plugins/outlook.rst:-1 -msgid "Custom add-ins in Outlook" -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`." -msgstr "" - -#: ../../content/applications/productivity/mail_plugins/outlook.rst:-1 -msgid "Custom add-in installation warning in Outlook" -msgstr "" - -#: ../../content/applications/productivity/mail_plugins/outlook.rst:61 -msgid "Connect the database" -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`." -msgstr "" - -#: ../../content/applications/productivity/mail_plugins/outlook.rst:-1 -msgid "Odoo for Outlook add-in button" -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`." -msgstr "" - -#: ../../content/applications/productivity/mail_plugins/outlook.rst:-1 -msgid "Logging in the Odoo database" -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 `." -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." -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." -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`." -msgstr "" - -#: ../../content/applications/productivity/mail_plugins/outlook.rst:94 -msgid "Once this is complete, the Outlook panel needs to be opened again." -msgstr "" - -#: ../../content/applications/productivity/mail_plugins/outlook.rst:96 -msgid "Now, enter the Odoo database URL and click on :guilabel:`Login`." -msgstr "" - -#: ../../content/applications/productivity/mail_plugins/outlook.rst:-1 -msgid "Entering the Odoo database URL" -msgstr "" - -#: ../../content/applications/productivity/mail_plugins/outlook.rst:102 -msgid "Next, click on :guilabel:`Allow` to open the pop-up window." -msgstr "" - -#: ../../content/applications/productivity/mail_plugins/outlook.rst:-1 -msgid "New window pop-up warning" -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." -msgstr "" - -#: ../../content/applications/productivity/mail_plugins/outlook.rst:-1 -msgid "Allowing the Outlook Plugin to connect to a database" -msgstr "" - -#: ../../content/applications/productivity/mail_plugins/outlook.rst:118 -msgid "Add a shortcut to the plugin" -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." -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`." -msgstr "" - -#: ../../content/applications/productivity/mail_plugins/outlook.rst:-1 -msgid "Viewing all Outlook settings" -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`." -msgstr "" - -#: ../../content/applications/productivity/mail_plugins/outlook.rst:-1 -msgid "Odoo for Outlook customized action" -msgstr "" - -#: ../../content/applications/productivity/mail_plugins/outlook.rst:137 -msgid "Following this step, open any email; the shortcut should be displayed." -msgstr "" - -#: ../../content/applications/productivity/mail_plugins/outlook.rst:144 -msgid "Using the plugin" -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." -msgstr "" - -#: ../../content/applications/productivity/studio.rst:6 -msgid "Studio" -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:" -msgstr "" - -#: ../../content/applications/productivity/studio.rst:20 -msgid ":doc:`Fields `" -msgstr "" - -#: ../../content/applications/productivity/studio.rst:21 -msgid ":doc:`Views `" -msgstr "" - -#: ../../content/applications/productivity/studio.rst:22 -msgid ":doc:`Models `" -msgstr "" - -#: ../../content/applications/productivity/studio.rst:23 -msgid ":doc:`Automated actions `" -msgstr "" - -#: ../../content/applications/productivity/studio.rst:24 -msgid ":doc:`PDF reports `" -msgstr "" - -#: ../../content/applications/productivity/studio.rst:25 -msgid "Approval rules" -msgstr "" - -#: ../../content/applications/productivity/studio.rst:26 -msgid "Security rules" -msgstr "" - -#: ../../content/applications/productivity/studio.rst:28 -msgid "Or you can :doc:`build an app from scratch `." -msgstr "" - -#: ../../content/applications/productivity/studio.rst:31 -msgid "`Odoo Tutorials: Studio `_" -msgstr "" - -#: ../../content/applications/productivity/studio/automated_actions.rst:3 -msgid "Automated actions (automations)" -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)." -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." -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`." -msgstr "" - -#: ../../content/applications/productivity/studio/automated_actions.rst:0 -msgid "Example of an automated action on the Subscription model" -msgstr "" - -#: ../../content/applications/productivity/studio/automated_actions.rst:25 -msgid "Model" -msgstr "" - -#: ../../content/applications/productivity/studio/automated_actions.rst:27 -msgid "Select the model where the automated action should be applied." -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." -msgstr "" - -#: ../../content/applications/productivity/studio/automated_actions.rst:35 -msgid "Trigger" -msgstr "" - -#: ../../content/applications/productivity/studio/automated_actions.rst:37 -msgid "Define when the automated action should be applied. Six triggers are available." -msgstr "" - -#: ../../content/applications/productivity/studio/automated_actions.rst:42 -msgid "On Creation" -msgstr "" - -#: ../../content/applications/productivity/studio/automated_actions.rst:44 -msgid "The action is triggered when a record is created and then saved." -msgstr "" - -#: ../../content/applications/productivity/studio/automated_actions.rst:49 -msgid "On Update" -msgstr "" - -#: ../../content/applications/productivity/studio/automated_actions.rst:51 -msgid "The action is triggered when a previously saved record is edited and then saved." -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." -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." -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`." -msgstr "" - -#: ../../content/applications/productivity/studio/automated_actions.rst:0 -msgid "Example of an On Update trigger" -msgstr "" - -#: ../../content/applications/productivity/studio/automated_actions.rst:72 -msgid "On Creation & Update" -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." -msgstr "" - -#: ../../content/applications/productivity/studio/automated_actions.rst:79 -msgid "On Deletion" -msgstr "" - -#: ../../content/applications/productivity/studio/automated_actions.rst:81 -msgid "The action is triggered when a record is deleted." -msgstr "" - -#: ../../content/applications/productivity/studio/automated_actions.rst:84 -msgid "This trigger is rarely used, as archiving records is usually preferred to deletion." -msgstr "" - -#: ../../content/applications/productivity/studio/automated_actions.rst:89 -msgid "Based on Form Modification" -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." -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." -msgstr "" - -#: ../../content/applications/productivity/studio/automated_actions.rst:103 -msgid "Based on Timed Condition" -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." -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." -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`." -msgstr "" - -#: ../../content/applications/productivity/studio/automated_actions.rst:0 -msgid "Example of a Based on Timed Condition trigger" -msgstr "" - -#: ../../content/applications/productivity/studio/automated_actions.rst:121 -msgid "By default, the scheduler checks for trigger dates every 4 hours." -msgstr "" - -#: ../../content/applications/productivity/studio/automated_actions.rst:126 -msgid "Apply on" -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." -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." -msgstr "" - -#: ../../content/applications/productivity/studio/automated_actions.rst:142 -msgid "Execute Python Code" -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." -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`." -msgstr "" - -#: ../../content/applications/productivity/studio/automated_actions.rst:153 -msgid "Create a new Record" -msgstr "" - -#: ../../content/applications/productivity/studio/automated_actions.rst:155 -msgid "The action is used to create a new record on any model." -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." -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." -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`:" -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." -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." -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." -msgstr "" - -#: ../../content/applications/productivity/studio/automated_actions.rst:0 -msgid "Example of a Create a new Record action" -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." -msgstr "" - -#: ../../content/applications/productivity/studio/automated_actions.rst:187 -msgid "Update the Record" -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." -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`." -msgstr "" - -#: ../../content/applications/productivity/studio/automated_actions.rst:198 -msgid "Execute several actions" -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." -msgstr "" - -#: ../../content/applications/productivity/studio/automated_actions.rst:207 -msgid "Send Email" -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`." -msgstr "" - -#: ../../content/applications/productivity/studio/automated_actions.rst:215 -msgid "Add Followers" -msgstr "" - -#: ../../content/applications/productivity/studio/automated_actions.rst:217 -msgid "The action is used to subscribe existing contacts to the record." -msgstr "" - -#: ../../content/applications/productivity/studio/automated_actions.rst:222 -msgid "Create Next Activity" -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." -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`." -msgstr "" - -#: ../../content/applications/productivity/studio/automated_actions.rst:0 -msgid "Example of a Create Next Activity action" -msgstr "" - -#: ../../content/applications/productivity/studio/automated_actions.rst:243 -msgid "Send SMS Text Message" -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`." -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`." -msgstr "" - -#: ../../content/applications/productivity/studio/fields.rst:3 -msgid "Fields and widgets" -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." -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:453 -msgid "Properties" -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 edit existing PDF reports (e.g., orders and quotations) or create new ones." -msgstr "" - -#: ../../content/applications/productivity/studio/pdf_reports.rst:8 -msgid "To edit a standard PDF report, it is strongly recommended to **duplicate** it and make changes to the duplicated version, as changes made to standard reports will be overwritten after an Odoo upgrade. To duplicate a report, go to :menuselection:`Studio --> Reports`. 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:20 -msgid "Default layout" -msgstr "" - -#: ../../content/applications/productivity/studio/pdf_reports.rst:22 -msgid "The default layout of reports is managed outside Studio. Go to :menuselection:`Settings --> Companies: Document Layout --> Configure Document Layout`. Layout settings apply to all reports but only to the current company." -msgstr "" - -#: ../../content/applications/productivity/studio/pdf_reports.rst:27 -msgid "Use :guilabel:`Download PDF Preview` to view how the different settings affect the layout of a sample invoice." -msgstr "" - -#: ../../content/applications/productivity/studio/pdf_reports.rst:33 -msgid "Layout" -msgstr "" - -#: ../../content/applications/productivity/studio/pdf_reports.rst:35 -msgid "Four layouts are available." -msgstr "" - -#: ../../content/applications/productivity/studio/pdf_reports.rst:39 -msgid "Light" -msgstr "" - -#: ../../content/applications/productivity/studio/pdf_reports.rst:0 -msgid "Light report layout sample" -msgstr "" - -#: ../../content/applications/productivity/studio/pdf_reports.rst:44 -msgid "Boxed" -msgstr "" - -#: ../../content/applications/productivity/studio/pdf_reports.rst:0 -msgid "Boxed report layout sample" -msgstr "" - -#: ../../content/applications/productivity/studio/pdf_reports.rst:49 -msgid "Bold" -msgstr "" - -#: ../../content/applications/productivity/studio/pdf_reports.rst:0 -msgid "Bold report layout sample" -msgstr "" - -#: ../../content/applications/productivity/studio/pdf_reports.rst:54 -msgid "Striped" -msgstr "" - -#: ../../content/applications/productivity/studio/pdf_reports.rst:0 -msgid "Striped report layout sample" -msgstr "" - -#: ../../content/applications/productivity/studio/pdf_reports.rst:62 -msgid "Font" -msgstr "" - -#: ../../content/applications/productivity/studio/pdf_reports.rst:64 -msgid "Seven fonts are available. Click on the links below to preview them on `Google Fonts `_." -msgstr "" - -#: ../../content/applications/productivity/studio/pdf_reports.rst:67 -msgid "`Lato `_" -msgstr "" - -#: ../../content/applications/productivity/studio/pdf_reports.rst:68 -msgid "`Roboto `_" -msgstr "" - -#: ../../content/applications/productivity/studio/pdf_reports.rst:69 -msgid "`Open Sans `_" -msgstr "" - -#: ../../content/applications/productivity/studio/pdf_reports.rst:70 -msgid "`Montserrat `_" -msgstr "" - -#: ../../content/applications/productivity/studio/pdf_reports.rst:71 -msgid "`Oswald `_" -msgstr "" - -#: ../../content/applications/productivity/studio/pdf_reports.rst:72 -msgid "`Raleway `_" -msgstr "" - -#: ../../content/applications/productivity/studio/pdf_reports.rst:73 -msgid "`Tajawal `_" -msgstr "" - -#: ../../content/applications/productivity/studio/pdf_reports.rst:76 -msgid ":guilabel:`Tajawal` supports both Arabic and Latin scripts." -msgstr "" - -#: ../../content/applications/productivity/studio/pdf_reports.rst:81 -msgid "Company logo" -msgstr "" - -#: ../../content/applications/productivity/studio/pdf_reports.rst:83 -msgid "Upload an image file to add a :guilabel:`Company Logo`." -msgstr "" - -#: ../../content/applications/productivity/studio/pdf_reports.rst:86 -msgid "This adds the logo to the company’s record on the *Company* model, which you can access by going to :menuselection:`General Settings --> Companies --> Update Info`." -msgstr "" - -#: ../../content/applications/productivity/studio/pdf_reports.rst:92 -msgid "Colors" -msgstr "" - -#: ../../content/applications/productivity/studio/pdf_reports.rst:94 -msgid "Change the primary and secondary colors used throughout reports to highlight important elements. The default colors are automatically generated based on the colors of the logo." -msgstr "" - -#: ../../content/applications/productivity/studio/pdf_reports.rst:100 -msgid "Layout background" -msgstr "" - -#: ../../content/applications/productivity/studio/pdf_reports.rst:102 -msgid "Change the :guilabel:`Layout Background` of the report:" -msgstr "" - -#: ../../content/applications/productivity/studio/pdf_reports.rst:104 -msgid ":guilabel:`Blank`: nothing is displayed." -msgstr "" - -#: ../../content/applications/productivity/studio/pdf_reports.rst:105 -msgid ":guilabel:`Geometric`: an image featuring geometric shapes is displayed in the background." -msgstr "" - -#: ../../content/applications/productivity/studio/pdf_reports.rst:106 -msgid ":guilabel:`Custom`: use a custom background image by uploading one." -msgstr "" - -#: ../../content/applications/productivity/studio/pdf_reports.rst:111 -msgid "Company tagline" -msgstr "" - -#: ../../content/applications/productivity/studio/pdf_reports.rst:113 -msgid "The :guilabel:`Company Tagline` is displayed on the header of :ref:`External reports `. You can add multiple lines of text." -msgstr "" - -#: ../../content/applications/productivity/studio/pdf_reports.rst:119 -msgid "Company details" -msgstr "" - -#: ../../content/applications/productivity/studio/pdf_reports.rst:121 -msgid "The :guilabel:`Company Details` are displayed on the header of :ref:`External reports `. You can add multiple lines of text." -msgstr "" - -#: ../../content/applications/productivity/studio/pdf_reports.rst:127 -msgid "Footer" -msgstr "" - -#: ../../content/applications/productivity/studio/pdf_reports.rst:129 -msgid "Use the :guilabel:`Footer` field to put any text in the :ref:`External reports' ` footers. You can add multiple lines of text." -msgstr "" - -#: ../../content/applications/productivity/studio/pdf_reports.rst:135 -msgid "Paper format" -msgstr "" - -#: ../../content/applications/productivity/studio/pdf_reports.rst:137 -msgid "Use the :guilabel:`Paper format` field to change the paper size of reports. You can either select :guilabel:`A4` (21 cm x 29.7 cm) or :guilabel:`US Letter` (21.59 cm x 27.54 cm)." -msgstr "" - -#: ../../content/applications/productivity/studio/pdf_reports.rst:141 -msgid "You can change the :guilabel:`Paper format` on individual reports. Open the app containing the report, then go to :menuselection:`Studio --> Reports --> Select or Create a report --> Report --> Select a Paper format`." -msgstr "" - -#: ../../content/applications/productivity/studio/pdf_reports.rst:-1 -msgid "Configuration pop-up window for the default layout of PDF reports" -msgstr "" - -#: ../../content/applications/productivity/studio/pdf_reports.rst:151 -msgid "Header and footer" -msgstr "" - -#: ../../content/applications/productivity/studio/pdf_reports.rst:153 -msgid "When creating a new report in Studio, you must choose between one of three styles of reports first. This is solely used to determine what is displayed on the header and footer. To do so, go to the app on which you want to add a new report, then :menuselection:`Studio button --> Reports --> Create` and select :ref:`studio/pdf-reports/header-footer/external`, :ref:`studio/pdf-reports/header-footer/internal`, or :ref:`studio/pdf-reports/header-footer/blank`." -msgstr "" - -#: ../../content/applications/productivity/studio/pdf_reports.rst:162 -msgid "External" -msgstr "" - -#: ../../content/applications/productivity/studio/pdf_reports.rst:164 -msgid "The header displays the company :ref:`studio/pdf-reports/default-layout/logo` and several values set on the *Company* model: the :guilabel:`Company Name`, :guilabel:`Phone`, :guilabel:`Email`, and :guilabel:`Website`." -msgstr "" - -#: ../../content/applications/productivity/studio/pdf_reports.rst:169 -msgid "To change a company's information, go to :menuselection:`Settings --> Companies --> Update Info`." -msgstr "" - -#: ../../content/applications/productivity/studio/pdf_reports.rst:-1 -msgid "Example of an External header" -msgstr "" - -#: ../../content/applications/productivity/studio/pdf_reports.rst:174 -msgid "The footer displays the values set on the :ref:`studio/pdf-reports/default-layout/footer`, :ref:`studio/pdf-reports/default-layout/details`, and :ref:`studio/pdf-reports/default-layout/tagline` fields, as well as the page number." -msgstr "" - -#: ../../content/applications/productivity/studio/pdf_reports.rst:-1 -msgid "Example of an External footer" -msgstr "" - -#: ../../content/applications/productivity/studio/pdf_reports.rst:184 -msgid "Internal" -msgstr "" - -#: ../../content/applications/productivity/studio/pdf_reports.rst:186 -msgid "The header displays the user's current date and time, :guilabel:`Company Name`, and page number." -msgstr "" - -#: ../../content/applications/productivity/studio/pdf_reports.rst:188 -msgid "There is no footer." -msgstr "" - -#: ../../content/applications/productivity/studio/pdf_reports.rst:193 -msgid "Blank" -msgstr "" - -#: ../../content/applications/productivity/studio/pdf_reports.rst:195 -msgid "There is neither a header nor a footer." -msgstr "" - -#: ../../content/applications/productivity/studio/pdf_reports.rst:200 -msgid "Add tab" -msgstr "" - -#: ../../content/applications/productivity/studio/pdf_reports.rst:202 -msgid "After opening an existing report or creating a new one, go to the :guilabel:`Add` tab to add or edit elements. The elements are organized into four categories: :ref:`studio/pdf-reports/elements/block`, :ref:`studio/pdf-reports/elements/inline`, :ref:`studio/pdf-reports/elements/table`, and :ref:`studio/pdf-reports/elements/column`." -msgstr "" - -#: ../../content/applications/productivity/studio/pdf_reports.rst:210 -msgid "Block" -msgstr "" - -#: ../../content/applications/productivity/studio/pdf_reports.rst:212 -msgid "Block elements start on a new line and occupy the full width of the page." -msgstr "" - -#: ../../content/applications/productivity/studio/pdf_reports.rst:215 -msgid "You can set an element's width by selecting it and going to the :guilabel:`Options` tab." -msgstr "" - -#: ../../content/applications/productivity/studio/pdf_reports.rst:217 -#: ../../content/applications/productivity/studio/pdf_reports.rst:246 -msgid ":guilabel:`Text`: add any text using small font size by default." -msgstr "" - -#: ../../content/applications/productivity/studio/pdf_reports.rst:219 -msgid ":guilabel:`Title Block`: add any text using larger font size by default." -msgstr "" - -#: ../../content/applications/productivity/studio/pdf_reports.rst:221 -msgid ":guilabel:`Image`: add an image. You can either upload one from your device, add one from an URL, or select one already existing on your database." -msgstr "" - -#: ../../content/applications/productivity/studio/pdf_reports.rst:224 -#: ../../content/applications/productivity/studio/pdf_reports.rst:248 -msgid ":guilabel:`Field`: dynamically add a field's value." -msgstr "" - -#: ../../content/applications/productivity/studio/pdf_reports.rst:226 -msgid ":guilabel:`Field & Label`: to dynamically add a field's value and label." -msgstr "" - -#: ../../content/applications/productivity/studio/pdf_reports.rst:228 -msgid ":guilabel:`Address Block`: to dynamically add the values, if any, of a contact's (`res.partner` model): *Name*, *Address*, *Phone*, *Mobile*, and *Email*." -msgstr "" - -#: ../../content/applications/productivity/studio/pdf_reports.rst:0 -msgid "Example of an Address Block" -msgstr "" - -#: ../../content/applications/productivity/studio/pdf_reports.rst:237 -msgid "Inline" -msgstr "" - -#: ../../content/applications/productivity/studio/pdf_reports.rst:239 -msgid "Inline elements are used around other elements. They do not start on a new line and the width adapts to length of the content." -msgstr "" - -#: ../../content/applications/productivity/studio/pdf_reports.rst:243 -msgid "You can set an element's width and margins by selecting it and going to the :guilabel:`Options` tab." -msgstr "" - -#: ../../content/applications/productivity/studio/pdf_reports.rst:253 -msgid "Table" -msgstr "" - -#: ../../content/applications/productivity/studio/pdf_reports.rst:255 -msgid "Table elements are used together to create a data table." -msgstr "" - -#: ../../content/applications/productivity/studio/pdf_reports.rst:257 -msgid ":guilabel:`Data table`: create a table and dynamically add a first column displaying the *Name* values of a :ref:`Many2Many ` or :ref:`One2Many ` field on your model." -msgstr "" - -#: ../../content/applications/productivity/studio/pdf_reports.rst:0 -msgid "Example of a Data table" -msgstr "" - -#: ../../content/applications/productivity/studio/pdf_reports.rst:264 -msgid ":guilabel:`Field Column`: add a new column to the table displaying the values of a :ref:`Related Field ` to the one used to create the :guilabel:`Data table`." -msgstr "" - -#: ../../content/applications/productivity/studio/pdf_reports.rst:268 -msgid ":guilabel:`Text in Cell`: add any text within an existing table cell." -msgstr "" - -#: ../../content/applications/productivity/studio/pdf_reports.rst:270 -msgid ":guilabel:`Field in Cell`: add, within an existing table cell, the values of a :ref:`Related Field ` to the one used to create the :guilabel:`Data table`." -msgstr "" - -#: ../../content/applications/productivity/studio/pdf_reports.rst:274 -msgid ":guilabel:`Subtotal & Total`: add an existing :guilabel:`Total` field's value. If a :guilabel:`Taxes` field exists, the untaxed and taxes amounts are added before the total amount." -msgstr "" - -#: ../../content/applications/productivity/studio/pdf_reports.rst:280 -msgid "Column" -msgstr "" - -#: ../../content/applications/productivity/studio/pdf_reports.rst:282 -msgid "Columns are used to add multiple :ref:`blocks ` elements on the same line." -msgstr "" - -#: ../../content/applications/productivity/studio/pdf_reports.rst:285 -msgid ":guilabel:`Two Columns`: add any text in two different columns." -msgstr "" - -#: ../../content/applications/productivity/studio/pdf_reports.rst:287 -msgid ":guilabel:`Three Columns`: add any text in three different columns." -msgstr "" - -#: ../../content/applications/productivity/studio/pdf_reports.rst:290 -msgid "Report tab" -msgstr "" - -#: ../../content/applications/productivity/studio/pdf_reports.rst:292 -msgid "Several configuration options are available under the :guilabel:`Report` tab." -msgstr "" - -#: ../../content/applications/productivity/studio/pdf_reports.rst:294 -msgid ":guilabel:`Name`: change the report name. The new name is applied everywhere (in Studio, under the :guilabel:`Print` button, and for the PDF file name)." -msgstr "" - -#: ../../content/applications/productivity/studio/pdf_reports.rst:297 -msgid ":guilabel:`Paper format`: change the paper size of the report." -msgstr "" - -#: ../../content/applications/productivity/studio/pdf_reports.rst:299 -msgid ":guilabel:`Add in print`: add the report under the :guilabel:`🖶 Print` button available on the record." -msgstr "" - -#: ../../content/applications/productivity/studio/pdf_reports.rst:302 -msgid ":guilabel:`Limit visibility to groups`: limit the availability of the PDF report to specific :doc:`user groups <../../general/users/access_rights>`." -msgstr "" - -#: ../../content/applications/productivity/studio/pdf_reports.rst:306 -msgid "Options tab" -msgstr "" - -#: ../../content/applications/productivity/studio/pdf_reports.rst:308 -msgid "Select an element on the report to access the element's options and edit it." -msgstr "" - -#: ../../content/applications/productivity/studio/pdf_reports.rst:-1 -msgid "The Options tab for a text element" -msgstr "" - -#: ../../content/applications/productivity/studio/pdf_reports.rst:314 -msgid "You can select and edit multiple elements at the same time by clicking on the different sections or divisions (e.g., `div`, `table`, etc.)." -msgstr "" - -#: ../../content/applications/productivity/studio/pdf_reports.rst:317 -msgid "Below are presented some of the most common options:" -msgstr "" - -#: ../../content/applications/productivity/studio/pdf_reports.rst:319 -msgid ":guilabel:`Margins`: add spacing at the :guilabel:`top`, :guilabel:`right`, :guilabel:`bottom`, and :guilabel:`left` of the element." -msgstr "" - -#: ../../content/applications/productivity/studio/pdf_reports.rst:322 -msgid ":guilabel:`Width`: set the element's maximum width." -msgstr "" - -#: ../../content/applications/productivity/studio/pdf_reports.rst:324 -msgid ":guilabel:`Visible if`: set under which condition(s) the element should be displayed." -msgstr "" - -#: ../../content/applications/productivity/studio/pdf_reports.rst:326 -msgid ":guilabel:`Visible for`: set for which :doc:`users groups <../../general/users/access_rights>` the element should be displayed." -msgstr "" - -#: ../../content/applications/productivity/studio/pdf_reports.rst:329 -msgid ":guilabel:`Remove from View`: remove the element from the report's view." -msgstr "" - -#: ../../content/applications/productivity/studio/pdf_reports.rst:331 -msgid ":guilabel:`Text decoration`: bold, italicize, and underline the font." -msgstr "" - -#: ../../content/applications/productivity/studio/pdf_reports.rst:333 -msgid ":guilabel:`Alignment`: align the element to the left, center, or right of the report." -msgstr "" - -#: ../../content/applications/productivity/studio/pdf_reports.rst:335 -msgid ":guilabel:`Font style`: use one of the default font styles." -msgstr "" - -#: ../../content/applications/productivity/studio/pdf_reports.rst:337 -msgid ":guilabel:`Colors`: change the font's color and the background color." -msgstr "" - -#: ../../content/applications/productivity/studio/pdf_reports.rst:340 -msgid "You may need to select a section or division above the element you want to edit to see some of the options described above." -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/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/sales.pot b/locale/sources/sales.pot index ad21b6d87..3b3ad0525 100644 --- a/locale/sources/sales.pot +++ b/locale/sources/sales.pot @@ -8,7 +8,7 @@ msgid "" msgstr "" "Project-Id-Version: Odoo 15.0\n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2024-03-05 13:22+0000\n" +"POT-Creation-Date: 2024-03-20 10:19+0000\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME \n" "Language-Team: LANGUAGE \n" @@ -442,7 +442,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 @@ -1290,7 +1290,7 @@ msgid "`Odoo Tutorials: Point of Sale Tutorials `" +msgid ":doc:`IoT Boxes Documentations `" msgstr "" #: ../../content/applications/sales/point_of_sale.rst:19 @@ -1558,7 +1558,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 @@ -2047,7 +2047,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/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." msgstr "" @@ -2173,7 +2173,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/worldline.rst:63 msgid "Configure the payment method" msgstr "" @@ -2187,7 +2187,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 "" @@ -2369,7 +2369,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 @@ -3679,7 +3679,7 @@ msgid "Digital Documents settings in Odoo Rental" msgstr "" #: ../../content/applications/sales/rental.rst:76 -msgid "This feature requires the :doc:`Sign <../finance/sign>` app. If necessary, Odoo installs it after activating *Digital Documents*." +msgid "This feature requires the :doc:`Sign <../productivity/sign>` app. If necessary, Odoo installs it after activating *Digital Documents*." msgstr "" #: ../../content/applications/sales/rental.rst:79 @@ -3929,7 +3929,7 @@ msgstr "" #: ../../content/applications/sales/sales/amazon_connector/features.rst:88 #: ../../content/applications/sales/sales/amazon_connector/manage.rst:132 -#: ../../content/applications/sales/sales/amazon_connector/update.rst:59 +#: ../../content/applications/sales/sales/amazon_connector/update.rst:58 #: ../../content/applications/sales/sales/ebay_connector/linking_listings.rst:16 #: ../../content/applications/sales/sales/ebay_connector/manage.rst:30 #: ../../content/applications/sales/sales/ebay_connector/troubleshooting.rst:8 @@ -3938,7 +3938,7 @@ msgstr "" #: ../../content/applications/sales/sales/amazon_connector/features.rst:89 #: ../../content/applications/sales/sales/amazon_connector/setup.rst:119 -#: ../../content/applications/sales/sales/amazon_connector/update.rst:60 +#: ../../content/applications/sales/sales/amazon_connector/update.rst:59 #: ../../content/applications/sales/sales/ebay_connector/linking_listings.rst:17 #: ../../content/applications/sales/sales/ebay_connector/setup.rst:17 #: ../../content/applications/sales/sales/ebay_connector/troubleshooting.rst:9 @@ -4071,7 +4071,7 @@ msgstr "" #: ../../content/applications/sales/sales/amazon_connector/manage.rst:131 #: ../../content/applications/sales/sales/amazon_connector/setup.rst:118 -#: ../../content/applications/sales/sales/amazon_connector/update.rst:58 +#: ../../content/applications/sales/sales/amazon_connector/update.rst:57 msgid ":doc:`features`" msgstr "" @@ -4205,35 +4205,35 @@ msgid "If you use Odoo on Odoo.com or Odoo.sh platform, your code is already up- msgstr "" #: ../../content/applications/sales/sales/amazon_connector/update.rst:25 -msgid "If you use Odoo with an on-premise setup or through a partner, then you must update your installation as detailed in :doc:`this documentation page ` or by contacting your integrating partner." +msgid "If you use Odoo with an on-premise setup or through a partner, then you must update your installation as detailed in :doc:`this documentation page ` or by contacting your integrating partner." msgstr "" -#: ../../content/applications/sales/sales/amazon_connector/update.rst:31 +#: ../../content/applications/sales/sales/amazon_connector/update.rst:30 #: ../../content/applications/sales/sales/ebay_connector/troubleshooting.rst:48 msgid "Update the list of available modules" msgstr "" -#: ../../content/applications/sales/sales/amazon_connector/update.rst:33 +#: ../../content/applications/sales/sales/amazon_connector/update.rst:32 msgid "New modules must be *discovered* by your Odoo instance to be available in the **Apps** menu." msgstr "" -#: ../../content/applications/sales/sales/amazon_connector/update.rst:36 +#: ../../content/applications/sales/sales/amazon_connector/update.rst:35 msgid "To do so, activate the :ref:`developer mode `, and go to :menuselection:`Apps --> Update Apps List`. A wizard will ask for confirmation." msgstr "" -#: ../../content/applications/sales/sales/amazon_connector/update.rst:40 +#: ../../content/applications/sales/sales/amazon_connector/update.rst:39 msgid "Install the Amazon/Selling Partner API Patch" msgstr "" -#: ../../content/applications/sales/sales/amazon_connector/update.rst:43 +#: ../../content/applications/sales/sales/amazon_connector/update.rst:42 msgid "You should never install new modules in your production database without first testing them in a duplicate or staging environment. For Odoo.com customers, a duplicate database can be created from the database management page. For Odoo.sh users, you should use a staging or duplicate database. For on-premise users, you should use a staging environment---contact your integrating partner for more information regarding how to test a new module in your particular setup." msgstr "" -#: ../../content/applications/sales/sales/amazon_connector/update.rst:49 +#: ../../content/applications/sales/sales/amazon_connector/update.rst:48 msgid "The module should now be available in your :guilabel:`Apps` menu. Remove the ``Apps`` filter and search for ``Amazon``; the module :guilabel:`Amazon/Selling Partner API Patch` should be available for installation. If you cannot find the module after having updated the list of available modules, it means your Odoo source code is not up-to-date; refer to step one of this page." msgstr "" -#: ../../content/applications/sales/sales/amazon_connector/update.rst:54 +#: ../../content/applications/sales/sales/amazon_connector/update.rst:53 msgid "Once the module is installed, link your Amazon account by following the instructions on the :doc:`setup ` page." msgstr "" @@ -4457,7 +4457,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 @@ -5116,7 +5116,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:50 diff --git a/locale/sources/studio.pot b/locale/sources/studio.pot new file mode 100644 index 000000000..b10f18136 --- /dev/null +++ b/locale/sources/studio.pot @@ -0,0 +1,1860 @@ +# 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 15.0\n" +"Report-Msgid-Bugs-To: \n" +"POT-Creation-Date: 2024-03-20 10:19+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 edit existing PDF reports (e.g., orders and quotations) or create new ones." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:8 +msgid "To edit a standard PDF report, it is strongly recommended to **duplicate** it and make changes to the duplicated version, as changes made to standard reports will be overwritten after an Odoo upgrade. To duplicate a report, go to :menuselection:`Studio --> Reports`. 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:20 +msgid "Default layout" +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:22 +msgid "The default layout of reports is managed outside Studio. Go to :menuselection:`Settings --> Companies: Document Layout --> Configure Document Layout`. Layout settings apply to all reports but only to the current company." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:27 +msgid "Use :guilabel:`Download PDF Preview` to view how the different settings affect the layout of a sample invoice." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:33 +msgid "Layout" +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:35 +msgid "Four layouts are available." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:39 +msgid "Light" +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:0 +msgid "Light report layout sample" +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:44 +msgid "Boxed" +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:0 +msgid "Boxed report layout sample" +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:49 +msgid "Bold" +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:0 +msgid "Bold report layout sample" +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:54 +msgid "Striped" +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:0 +msgid "Striped report layout sample" +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:62 +msgid "Font" +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:64 +msgid "Seven fonts are available. Click on the links below to preview them on `Google Fonts `_." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:67 +msgid "`Lato `_" +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:68 +msgid "`Roboto `_" +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:69 +msgid "`Open Sans `_" +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:70 +msgid "`Montserrat `_" +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:71 +msgid "`Oswald `_" +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:72 +msgid "`Raleway `_" +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:73 +msgid "`Tajawal `_" +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:76 +msgid ":guilabel:`Tajawal` supports both Arabic and Latin scripts." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:81 +msgid "Company logo" +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:83 +msgid "Upload an image file to add a :guilabel:`Company Logo`." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:86 +msgid "This adds the logo to the company’s record on the *Company* model, which you can access by going to :menuselection:`General Settings --> Companies --> Update Info`." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:92 +msgid "Colors" +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:94 +msgid "Change the primary and secondary colors used throughout reports to highlight important elements. The default colors are automatically generated based on the colors of the logo." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:100 +msgid "Layout background" +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:102 +msgid "Change the :guilabel:`Layout Background` of the report:" +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:104 +msgid ":guilabel:`Blank`: nothing is displayed." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:105 +msgid ":guilabel:`Geometric`: an image featuring geometric shapes is displayed in the background." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:106 +msgid ":guilabel:`Custom`: use a custom background image by uploading one." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:111 +msgid "Company tagline" +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:113 +msgid "The :guilabel:`Company Tagline` is displayed on the header of :ref:`External reports `. You can add multiple lines of text." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:119 +msgid "Company details" +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:121 +msgid "The :guilabel:`Company Details` are displayed on the header of :ref:`External reports `. You can add multiple lines of text." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:127 +msgid "Footer" +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:129 +msgid "Use the :guilabel:`Footer` field to put any text in the :ref:`External reports' ` footers. You can add multiple lines of text." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:135 +msgid "Paper format" +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:137 +msgid "Use the :guilabel:`Paper format` field to change the paper size of reports. You can either select :guilabel:`A4` (21 cm x 29.7 cm) or :guilabel:`US Letter` (21.59 cm x 27.54 cm)." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:141 +msgid "You can change the :guilabel:`Paper format` on individual reports. Open the app containing the report, then go to :menuselection:`Studio --> Reports --> Select or Create a report --> Report --> Select a Paper format`." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:-1 +msgid "Configuration pop-up window for the default layout of PDF reports" +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:151 +msgid "Header and footer" +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:153 +msgid "When creating a new report in Studio, you must choose between one of three styles of reports first. This is solely used to determine what is displayed on the header and footer. To do so, go to the app on which you want to add a new report, then :menuselection:`Studio button --> Reports --> Create` and select :ref:`studio/pdf-reports/header-footer/external`, :ref:`studio/pdf-reports/header-footer/internal`, or :ref:`studio/pdf-reports/header-footer/blank`." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:162 +msgid "External" +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:164 +msgid "The header displays the company :ref:`studio/pdf-reports/default-layout/logo` and several values set on the *Company* model: the :guilabel:`Company Name`, :guilabel:`Phone`, :guilabel:`Email`, and :guilabel:`Website`." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:169 +msgid "To change a company's information, go to :menuselection:`Settings --> Companies --> Update Info`." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:-1 +msgid "Example of an External header" +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:174 +msgid "The footer displays the values set on the :ref:`studio/pdf-reports/default-layout/footer`, :ref:`studio/pdf-reports/default-layout/details`, and :ref:`studio/pdf-reports/default-layout/tagline` fields, as well as the page number." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:-1 +msgid "Example of an External footer" +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:184 +msgid "Internal" +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:186 +msgid "The header displays the user's current date and time, :guilabel:`Company Name`, and page number." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:188 +msgid "There is no footer." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:193 +msgid "Blank" +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:195 +msgid "There is neither a header nor a footer." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:200 +msgid "Add tab" +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:202 +msgid "After opening an existing report or creating a new one, go to the :guilabel:`Add` tab to add or edit elements. The elements are organized into four categories: :ref:`studio/pdf-reports/elements/block`, :ref:`studio/pdf-reports/elements/inline`, :ref:`studio/pdf-reports/elements/table`, and :ref:`studio/pdf-reports/elements/column`." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:210 +msgid "Block" +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:212 +msgid "Block elements start on a new line and occupy the full width of the page." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:215 +msgid "You can set an element's width by selecting it and going to the :guilabel:`Options` tab." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:217 +#: ../../content/applications/studio/pdf_reports.rst:246 +msgid ":guilabel:`Text`: add any text using small font size by default." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:219 +msgid ":guilabel:`Title Block`: add any text using larger font size by default." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:221 +msgid ":guilabel:`Image`: add an image. You can either upload one from your device, add one from an URL, or select one already existing on your database." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:224 +#: ../../content/applications/studio/pdf_reports.rst:248 +msgid ":guilabel:`Field`: dynamically add a field's value." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:226 +msgid ":guilabel:`Field & Label`: to dynamically add a field's value and label." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:228 +msgid ":guilabel:`Address Block`: to dynamically add the values, if any, of a contact's (`res.partner` model): *Name*, *Address*, *Phone*, *Mobile*, and *Email*." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:0 +msgid "Example of an Address Block" +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:237 +msgid "Inline" +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:239 +msgid "Inline elements are used around other elements. They do not start on a new line and the width adapts to length of the content." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:243 +msgid "You can set an element's width and margins by selecting it and going to the :guilabel:`Options` tab." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:253 +msgid "Table" +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:255 +msgid "Table elements are used together to create a data table." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:257 +msgid ":guilabel:`Data table`: create a table and dynamically add a first column displaying the *Name* values of a :ref:`Many2Many ` or :ref:`One2Many ` field on your model." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:0 +msgid "Example of a Data table" +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:264 +msgid ":guilabel:`Field Column`: add a new column to the table displaying the values of a :ref:`Related Field ` to the one used to create the :guilabel:`Data table`." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:268 +msgid ":guilabel:`Text in Cell`: add any text within an existing table cell." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:270 +msgid ":guilabel:`Field in Cell`: add, within an existing table cell, the values of a :ref:`Related Field ` to the one used to create the :guilabel:`Data table`." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:274 +msgid ":guilabel:`Subtotal & Total`: add an existing :guilabel:`Total` field's value. If a :guilabel:`Taxes` field exists, the untaxed and taxes amounts are added before the total amount." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:280 +msgid "Column" +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:282 +msgid "Columns are used to add multiple :ref:`blocks ` elements on the same line." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:285 +msgid ":guilabel:`Two Columns`: add any text in two different columns." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:287 +msgid ":guilabel:`Three Columns`: add any text in three different columns." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:290 +msgid "Report tab" +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:292 +msgid "Several configuration options are available under the :guilabel:`Report` tab." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:294 +msgid ":guilabel:`Name`: change the report name. The new name is applied everywhere (in Studio, under the :guilabel:`Print` button, and for the PDF file name)." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:297 +msgid ":guilabel:`Paper format`: change the paper size of the report." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:299 +msgid ":guilabel:`Add in print`: add the report under the :guilabel:`🖶 Print` button available on the record." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:302 +msgid ":guilabel:`Limit visibility to groups`: limit the availability of the PDF report to specific :doc:`user groups `." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:306 +msgid "Options tab" +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:308 +msgid "Select an element on the report to access the element's options and edit it." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:-1 +msgid "The Options tab for a text element" +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:314 +msgid "You can select and edit multiple elements at the same time by clicking on the different sections or divisions (e.g., `div`, `table`, etc.)." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:317 +msgid "Below are presented some of the most common options:" +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:319 +msgid ":guilabel:`Margins`: add spacing at the :guilabel:`top`, :guilabel:`right`, :guilabel:`bottom`, and :guilabel:`left` of the element." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:322 +msgid ":guilabel:`Width`: set the element's maximum width." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:324 +msgid ":guilabel:`Visible if`: set under which condition(s) the element should be displayed." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:326 +msgid ":guilabel:`Visible for`: set for which :doc:`users groups ` the element should be displayed." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:329 +msgid ":guilabel:`Remove from View`: remove the element from the report's view." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:331 +msgid ":guilabel:`Text decoration`: bold, italicize, and underline the font." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:333 +msgid ":guilabel:`Alignment`: align the element to the left, center, or right of the report." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:335 +msgid ":guilabel:`Font style`: use one of the default font styles." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:337 +msgid ":guilabel:`Colors`: change the font's color and the background color." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:340 +msgid "You may need to select a section or division above the element you want to edit to see some of the options described above." +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 c7574d019..be4063d2f 100644 --- a/locale/sources/websites.pot +++ b/locale/sources/websites.pot @@ -8,7 +8,7 @@ msgid "" msgstr "" "Project-Id-Version: Odoo 15.0\n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2024-03-05 13:22+0000\n" +"POT-Creation-Date: 2024-03-20 10:19+0000\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME \n" "Language-Team: LANGUAGE \n" @@ -923,6 +923,480 @@ msgstr "" msgid "Configuration" 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/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`. Enable :guilabel:`Custom Email Servers`, enter the :guilabel:`Alias Domain` (e.g., `subdomain.yourdomain.com`) and click :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/multi_website.rst:3 msgid "Multiple websites" msgstr "" @@ -1032,11 +1506,11 @@ msgid "As said earlier, your websites can either share the same domain name or u msgstr "" #: ../../content/applications/websites/website/configuration/multi_website.rst:122 -msgid "Geo IP is installed by default in Odoo Online. If you run Odoo on-premise, don’t forget to install *GeoIP* library. See :doc:`/administration/install/geo_ip`" +msgid "Geo IP is installed by default in Odoo Online. If you run Odoo on-premise, don’t forget to install *GeoIP* library. See :doc:`/administration/on_premise/geo_ip`" msgstr "" #: ../../content/applications/websites/website/configuration/multi_website.rst:127 -msgid ":doc:`/administration/maintain/domain_names`" +msgid ":doc:`domain_names`" msgstr "" #: ../../content/applications/websites/website/configuration/multi_website.rst:129 @@ -1395,66 +1869,6 @@ msgstr "" msgid "To translate the content of the website, click on **Translate** (here **Traduire** since we want to translate the website in French)." msgstr "" -#: ../../content/applications/websites/website/configuration/unsplash.rst:3 -msgid "Unsplash (free images)" -msgstr "" - -#: ../../content/applications/websites/website/configuration/unsplash.rst:6 -msgid "Generate an Unsplash access key" -msgstr "" - -#: ../../content/applications/websites/website/configuration/unsplash.rst:9 -msgid "**As an Odoo Online user**, you are ready to use Unsplash. You won't need to follow this guide to set up Unsplash information since you will use our own Odoo Unsplash key in a transparent way." -msgstr "" - -#: ../../content/applications/websites/website/configuration/unsplash.rst:13 -msgid "Generate an Unsplash access key for non-Odoo Online users" -msgstr "" - -#: ../../content/applications/websites/website/configuration/unsplash.rst:15 -msgid "Create an account on `Unsplash.com `_." -msgstr "" - -#: ../../content/applications/websites/website/configuration/unsplash.rst:17 -msgid "Go to your `applications dashboard `_ and click on **New Application**." -msgstr "" - -#: ../../content/applications/websites/website/configuration/unsplash.rst:23 -msgid "Accept the conditions and click on **Accept terms**." -msgstr "" - -#: ../../content/applications/websites/website/configuration/unsplash.rst:28 -msgid "You will be prompted to insert an **Application name** and a **Description**. Please prefix your application name by \"**Odoo:** \" so that Unsplash can recognize it as an Odoo instance. Once done, click on **Create application**." -msgstr "" - -#: ../../content/applications/websites/website/configuration/unsplash.rst:35 -msgid "You should be redirected to your application details page. Scroll down a bit to find your **access key**." -msgstr "" - -#: ../../content/applications/websites/website/configuration/unsplash.rst:42 -msgid "**As a non-Odoo Online user**, you won't be able to register for a production Unsplash key and will be limited to your test key that has a restriction of 50 Unsplash requests per hour." -msgstr "" - -#: ../../content/applications/websites/website/configuration/unsplash.rst:46 -msgid "Generate an Unsplash application ID" -msgstr "" - -#: ../../content/applications/websites/website/configuration/unsplash.rst:49 -msgid "You should first create and set up your Unsplash application." -msgstr "" - -#: ../../content/applications/websites/website/configuration/unsplash.rst:51 -msgid "Go to your `applications dashboard `_ and click on your newly created Unsplash application under **Your applications**." -msgstr "" - -#: ../../content/applications/websites/website/configuration/unsplash.rst:57 -msgid "You will be redirected to your application details page. The **application ID** will be visible in your browser's URL. The URL should be something like ``https://unsplash.com/oauth/applications/``" -msgstr "" - -#: ../../content/applications/websites/website/configuration/unsplash.rst:65 -msgid "**As a non-Odoo Online user**, you won't be able to register for a production Unsplash key and will be limited to your test key that has a 50 Unsplash requests per hour restriction." -msgstr "" - #: ../../content/applications/websites/website/mail_groups.rst:3 msgid "Mail groups" msgstr "" @@ -1571,7 +1985,7 @@ msgstr "" msgid "To moderate messages, go to :menuselection:`Website --> Groups --> Mailing List Groups`, select the mail group, and click the :guilabel:`To review` smart button. You can moderate messages using the buttons at the end of the message line or select a message to view its content and moderate it accordingly." msgstr "" -#: ../../content/applications/websites/website/mail_groups.rst:0 +#: ../../content/applications/websites/website/mail_groups.rst:93 msgid "Moderation buttons in the message line." msgstr ""