diff --git a/locale/sources/administration.pot b/locale/sources/administration.pot index 1adc4bac5..76d776e98 100644 --- a/locale/sources/administration.pot +++ b/locale/sources/administration.pot @@ -8,7 +8,7 @@ msgid "" msgstr "" "Project-Id-Version: Odoo 17.0\n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2024-03-25 16:01+0000\n" +"POT-Creation-Date: 2024-04-30 09:16+0000\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME \n" "Language-Team: LANGUAGE \n" @@ -158,7 +158,7 @@ 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." +msgid "Odoo Online's :ref:`intermediary versions ` are not supported by Odoo.sh or on-premise. 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 @@ -240,6 +240,110 @@ msgstr "" msgid "Download a :ref:`backup of your Odoo.sh production database `." msgstr "" +#: ../../content/administration/mobile.rst:3 +msgid "Odoo mobile apps" +msgstr "" + +#: ../../content/administration/mobile.rst:5 +msgid "Two kind of Odoo mobile app exist: the progressive web app (PWA) and store apps. Using the PWA is recommended." +msgstr "" + +#: ../../content/administration/mobile.rst:9 +msgid "Progressive web app (PWA)" +msgstr "" + +#: ../../content/administration/mobile.rst:11 +msgid "PWAs are web-based applications designed to function across different devices and platforms, leveraging web browsers to deliver user experiences similar to native apps." +msgstr "" + +#: ../../content/administration/mobile.rst:14 +msgid "The Odoo PWA features include:" +msgstr "" + +#: ../../content/administration/mobile.rst:16 +msgid "Quick access by adding the PWA to a device's home screen" +msgstr "" + +#: ../../content/administration/mobile.rst:17 +msgid "Seamless and borderless navigation experience" +msgstr "" + +#: ../../content/administration/mobile.rst:18 +msgid "Push notifications" +msgstr "" + +#: ../../content/administration/mobile.rst:19 +msgid "SSO authentication" +msgstr "" + +#: ../../content/administration/mobile.rst:21 +msgid "To install the Odoo PWA, launch a browser supporting PWAs, and sign in to an Odoo database. The instructions to install a PWA depend on the platform and browser used." +msgstr "" + +#: ../../content/administration/mobile.rst:26 +msgid "Android" +msgstr "" + +#: ../../content/administration/mobile.rst:28 +msgid "**Chrome**: open Chrome's menu (:guilabel:`⋮`), select :guilabel:`Install app`, and tap :guilabel:`Install`." +msgstr "" + +#: ../../content/administration/mobile.rst:31 +msgid "**Firefox**: open Firefox's menu (:guilabel:`⋮`), select :guilabel:`Install`, and either touch and hold the Odoo icon or tap :guilabel:`Add automatically`." +msgstr "" + +#: ../../content/administration/mobile.rst:34 +msgid "The PWA can also be installed with **Samsung Internet**, **Edge**, and **Opera**." +msgstr "" + +#: ../../content/administration/mobile.rst:36 +msgid "iOS" +msgstr "" + +#: ../../content/administration/mobile.rst:38 +msgid "**Safari**: open the **Share** menu by tapping the square with an arrow pointing upwards icon, select :guilabel:`Add to Home Screen`, edit the PWA details if desired, and tap :guilabel:`Add`." +msgstr "" + +#: ../../content/administration/mobile.rst:42 +msgid "On iOS 16.4 and above, the PWA can also be installed with **Chrome**, **Firefox**, and **Edge**." +msgstr "" + +#: ../../content/administration/mobile.rst:45 +msgid "Desktop" +msgstr "" + +#: ../../content/administration/mobile.rst:47 +msgid "**Chrome** and **Edge**: click the installation icon at the right of the address bar and click :guilabel:`Install`." +msgstr "" + +#: ../../content/administration/mobile.rst:51 +msgid "`Google Chrome Help: Use progressive web apps `_" +msgstr "" + +#: ../../content/administration/mobile.rst:53 +msgid "`MDN Web Docs: Installing and uninstalling web apps `_" +msgstr "" + +#: ../../content/administration/mobile.rst:55 +msgid "`Microsoft Support: Install, manage, or uninstall apps in Microsoft Edge `_" +msgstr "" + +#: ../../content/administration/mobile.rst:58 +msgid "Store apps" +msgstr "" + +#: ../../content/administration/mobile.rst:60 +msgid "The Odoo mobile apps are available for download on the `Google Play Store `_ and `Apple App Store `_." +msgstr "" + +#: ../../content/administration/mobile.rst:65 +msgid "The iOS app cannot be updated and will be deprecated at some point in the future." +msgstr "" + +#: ../../content/administration/mobile.rst:67 +msgid "While the store apps support multi-accounts, they are not compatible with SS0 authentication." +msgstr "" + #: ../../content/administration/neutralized_database.rst:3 msgid "Neutralized database" msgstr "" @@ -398,8 +502,8 @@ msgstr "" #: ../../content/administration/odoo_online.rst:3 #: ../../content/administration/supported_versions.rst:29 -#: ../../content/administration/upgrade.rst:90 -#: ../../content/administration/upgrade.rst:307 +#: ../../content/administration/upgrade.rst:81 +#: ../../content/administration/upgrade.rst:299 msgid "Odoo Online" msgstr "" @@ -499,64 +603,68 @@ msgstr "" msgid "Duplicated databases expire automatically after 15 days." msgstr "" -#: ../../content/administration/odoo_online.rst:67 -msgid "Rename" +#: ../../content/administration/odoo_online.rst:63 +msgid "A maximum of five duplicates can be made per database. Under extraordinary circumstances, contact `support `_ to raise the limit." msgstr "" #: ../../content/administration/odoo_online.rst:69 +msgid "Rename" +msgstr "" + +#: ../../content/administration/odoo_online.rst:71 msgid "Rename the database and its URL." msgstr "" -#: ../../content/administration/odoo_online.rst:74 +#: ../../content/administration/odoo_online.rst:76 msgid "Download" msgstr "" -#: ../../content/administration/odoo_online.rst:76 +#: ../../content/administration/odoo_online.rst:78 msgid "Download a ZIP file containing a backup of the database." msgstr "" -#: ../../content/administration/odoo_online.rst:79 +#: ../../content/administration/odoo_online.rst:81 msgid "Databases are backed up daily as per the `Odoo Cloud Hosting SLA `_." msgstr "" -#: ../../content/administration/odoo_online.rst:85 +#: ../../content/administration/odoo_online.rst:87 msgid "Domain names" msgstr "" -#: ../../content/administration/odoo_online.rst:87 +#: ../../content/administration/odoo_online.rst:89 msgid "Use a custom :doc:`domain name ` to access the database via another URL." msgstr "" -#: ../../content/administration/odoo_online.rst:91 +#: ../../content/administration/odoo_online.rst:93 msgid "You can :ref:`register a domain name for free `." msgstr "" -#: ../../content/administration/odoo_online.rst:96 +#: ../../content/administration/odoo_online.rst:98 msgid "Tags" msgstr "" -#: ../../content/administration/odoo_online.rst:98 +#: ../../content/administration/odoo_online.rst:100 msgid "Add tags to easily identify and sort your databases." msgstr "" -#: ../../content/administration/odoo_online.rst:101 +#: ../../content/administration/odoo_online.rst:103 msgid "You can search for tags in the search bar." msgstr "" -#: ../../content/administration/odoo_online.rst:106 +#: ../../content/administration/odoo_online.rst:108 #: ../../content/administration/odoo_sh/getting_started/branches.rst:550 msgid "Delete" msgstr "" -#: ../../content/administration/odoo_online.rst:108 +#: ../../content/administration/odoo_online.rst:110 msgid "Delete a database instantly." msgstr "" -#: ../../content/administration/odoo_online.rst:111 +#: ../../content/administration/odoo_online.rst:113 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/odoo_online.rst:114 +#: ../../content/administration/odoo_online.rst:116 msgid "Carefully read the warning message and only proceed if the implications of deleting a database are fully understood." msgstr "" @@ -564,31 +672,31 @@ msgstr "" msgid "The warning message displayed before deleting a database" msgstr "" -#: ../../content/administration/odoo_online.rst:121 +#: ../../content/administration/odoo_online.rst:123 msgid "Only an administrator can delete a database." msgstr "" -#: ../../content/administration/odoo_online.rst:122 +#: ../../content/administration/odoo_online.rst:124 msgid "The database name is immediately made available to anyone." msgstr "" -#: ../../content/administration/odoo_online.rst:123 +#: ../../content/administration/odoo_online.rst:125 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/odoo_online.rst:129 +#: ../../content/administration/odoo_online.rst:131 msgid "Contact us" msgstr "" -#: ../../content/administration/odoo_online.rst:131 +#: ../../content/administration/odoo_online.rst:133 msgid "Access the `Odoo.com support page `_ with the database's details already pre-filled." msgstr "" -#: ../../content/administration/odoo_online.rst:137 +#: ../../content/administration/odoo_online.rst:139 msgid "Invite / remove users" msgstr "" -#: ../../content/administration/odoo_online.rst:139 +#: ../../content/administration/odoo_online.rst:141 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 "" @@ -596,22 +704,22 @@ msgstr "" msgid "Inviting a user on a database" msgstr "" -#: ../../content/administration/odoo_online.rst:145 +#: ../../content/administration/odoo_online.rst:147 msgid "To remove users, select them and click :guilabel:`Remove`." msgstr "" -#: ../../content/administration/odoo_online.rst:148 +#: ../../content/administration/odoo_online.rst:150 msgid ":doc:`/applications/general/users`" msgstr "" -#: ../../content/administration/odoo_online.rst:149 +#: ../../content/administration/odoo_online.rst:151 msgid ":doc:`odoo_accounts`" msgstr "" #: ../../content/administration/odoo_sh.rst:5 #: ../../content/administration/supported_versions.rst:30 -#: ../../content/administration/upgrade.rst:120 -#: ../../content/administration/upgrade.rst:318 +#: ../../content/administration/upgrade.rst:111 +#: ../../content/administration/upgrade.rst:310 msgid "Odoo.sh" msgstr "" @@ -2141,7 +2249,7 @@ msgid "Manually" msgstr "" #: ../../content/administration/odoo_sh/getting_started/first_module.rst:148 -msgid "If you want to create your module structure manually, you can follow the :doc:`/developer/tutorials/getting_started` tutorial to understand the structure of a module and the content of each file." +msgid "If you want to create your module structure manually, you can follow the :doc:`/developer/tutorials/server_framework_101` tutorial to understand the structure of a module and the content of each file." msgstr "" #: ../../content/administration/odoo_sh/getting_started/first_module.rst:153 @@ -2720,15 +2828,16 @@ msgstr "" #: ../../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 +#: ../../content/administration/supported_versions.rst:48 +#: ../../content/administration/supported_versions.rst:49 +#: ../../content/administration/supported_versions.rst:53 +#: ../../content/administration/supported_versions.rst:77 +#: ../../content/administration/supported_versions.rst:78 +#: ../../content/administration/supported_versions.rst:79 +#: ../../content/administration/supported_versions.rst:95 +#: ../../content/administration/supported_versions.rst:96 +#: ../../content/administration/supported_versions.rst:97 msgid "|green|" msgstr "" @@ -2912,8 +3021,8 @@ msgid "The documentation will help you go live with your Odoo.sh project in no t msgstr "" #: ../../content/administration/on_premise.rst:5 -#: ../../content/administration/upgrade.rst:145 -#: ../../content/administration/upgrade.rst:341 +#: ../../content/administration/upgrade.rst:136 +#: ../../content/administration/upgrade.rst:333 msgid "On-premise" msgstr "" @@ -3604,11 +3713,11 @@ msgid "Do **not** install demo data on internet-facing servers. Databases with d msgstr "" #: ../../content/administration/on_premise/deploy.rst:574 -msgid "Use appropriate database filters ( :option:`--db-filter `) to restrict the visibility of your databases according to the hostname. See :ref:`db_filter`. You may also use :option:`-d ` to provide your own (comma-separated) list of available databases to filter from, instead of letting the system fetch them all from the database backend." +msgid "Use appropriate database filters ( :option:`--db-filter `) to restrict the visibility of your databases according to the hostname. See :ref:`dbfilter`. You may also use :option:`-d ` to provide your own (comma-separated) list of available databases to filter from, instead of letting the system fetch them all from the database backend." msgstr "" #: ../../content/administration/on_premise/deploy.rst:581 -msgid "Once your ``db_name`` and ``db_filter`` are configured and only match a single database per hostname, you should set ``list_db`` configuration option to ``False``, to prevent listing databases entirely, and to block access to the database management screens (this is also exposed as the :option:`--no-database-list ` command-line option)" +msgid "Once your ``db_name`` and ``dbfilter`` are configured and only match a single database per hostname, you should set ``list_db`` configuration option to ``False``, to prevent listing databases entirely, and to block access to the database management screens (this is also exposed as the :option:`--no-database-list ` command-line option)" msgstr "" #: ../../content/administration/on_premise/deploy.rst:587 @@ -3724,7 +3833,7 @@ msgid "On production systems, database management operations should always be pe msgstr "" #: ../../content/administration/on_premise/deploy.rst:724 -msgid "Be sure to setup an appropriate ``db_name`` parameter (and optionally, ``db_filter`` too) so that the system can determine the target database for each request, otherwise users will be blocked as they won't be allowed to choose the database themselves." +msgid "Be sure to setup an appropriate ``db_name`` parameter (and optionally, ``dbfilter`` too) so that the system can determine the target database for each request, otherwise users will be blocked as they won't be allowed to choose the database themselves." msgstr "" #: ../../content/administration/on_premise/deploy.rst:729 @@ -4159,7 +4268,7 @@ msgid "It is required to have `Git `_ installed, and it is 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 `." +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 @@ -4219,7 +4328,7 @@ msgid "Use a package manager (`Homebrew `_, `MacPorts `_." msgstr "" -#: ../../content/administration/upgrade.rst:7 +#: ../../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." msgstr "" -#: ../../content/administration/upgrade.rst:15 +#: ../../content/administration/upgrade.rst:13 msgid "The Rolling Release process allows Odoo Online customers to upgrade their database directly from a message prompt sent to the database administrator as soon as a new version is released. The invitation to upgrade is only sent if no issues are detected during the automatic tests." msgstr "" @@ -4833,91 +4952,91 @@ msgstr "" msgid "The upgrade message prompt on the top right of the database" msgstr "" -#: ../../content/administration/upgrade.rst:22 +#: ../../content/administration/upgrade.rst:20 msgid "It is strongly recommended to manually :ref:`test the upgrade first `. Clicking :guilabel:`I want to test first` redirects to `the database manager `_, where it is possible to request an upgraded test database and check it for any discrepancies." msgstr "" -#: ../../content/administration/upgrade.rst:27 +#: ../../content/administration/upgrade.rst:25 msgid "It is **not** recommended to click :guilabel:`Upgrade Now` without testing first, as it immediately triggers the live production database upgrade." msgstr "" -#: ../../content/administration/upgrade.rst:30 +#: ../../content/administration/upgrade.rst:28 msgid "If the Rolling Release process detects an issue with the upgrade, it will be deactivated until the issue is resolved." msgstr "" -#: ../../content/administration/upgrade.rst:33 +#: ../../content/administration/upgrade.rst:31 msgid "An upgrade does not cover:" msgstr "" -#: ../../content/administration/upgrade.rst:35 +#: ../../content/administration/upgrade.rst:33 msgid "Downgrading to a previous version of Odoo" msgstr "" -#: ../../content/administration/upgrade.rst:36 +#: ../../content/administration/upgrade.rst:34 msgid ":doc:`Switching editions ` (e.g., from Community to Enterprise)" msgstr "" -#: ../../content/administration/upgrade.rst:38 +#: ../../content/administration/upgrade.rst:36 msgid ":ref:`Changing hosting type ` (e.g., from on-premise to Odoo Online)" msgstr "" -#: ../../content/administration/upgrade.rst:39 +#: ../../content/administration/upgrade.rst:37 msgid "Migrating from another ERP to Odoo" msgstr "" -#: ../../content/administration/upgrade.rst:42 +#: ../../content/administration/upgrade.rst:40 msgid "If your database contains custom modules, it cannot be upgraded until a version of your custom modules is available for the target version of Odoo. For customers maintaining their own custom modules, we recommend to parallelize the process by :ref:`requesting an upgraded database ` while also :doc:`upgrading the source code of your custom modules `." msgstr "" -#: ../../content/administration/upgrade.rst:50 +#: ../../content/administration/upgrade.rst:47 msgid "Upgrading in a nutshell" msgstr "" -#: ../../content/administration/upgrade.rst:52 +#: ../../content/administration/upgrade.rst:49 msgid "Request an upgraded test database (see :ref:`obtaining an upgraded test database `)." msgstr "" -#: ../../content/administration/upgrade.rst:55 +#: ../../content/administration/upgrade.rst:51 msgid "If applicable, upgrade the source code of your custom module to be compatible with the new version of Odoo (see :doc:`/developer/howtos/upgrade_custom_db`)." msgstr "" -#: ../../content/administration/upgrade.rst:58 +#: ../../content/administration/upgrade.rst:53 msgid "Thoroughly test the upgraded database (see :ref:`testing the new version of the database `)." msgstr "" -#: ../../content/administration/upgrade.rst:61 -msgid "Report any issue encountered during the testing to Odoo via the `support page `__." +#: ../../content/administration/upgrade.rst:55 +msgid "Report any issue encountered during the testing to Odoo by `submitting a ticket for an issue related to my future upgrade (I am testing an upgrade) `_." msgstr "" -#: ../../content/administration/upgrade.rst:64 +#: ../../content/administration/upgrade.rst:57 msgid "Once all issues are resolved and you are confident that the upgraded database can be used as your main database without any issues, plan the upgrade of your production database." msgstr "" -#: ../../content/administration/upgrade.rst:67 +#: ../../content/administration/upgrade.rst:59 msgid "Request the upgrade for the production database, rendering it unavailable for the time it takes to complete the process (see :ref:`upgrading the production database `)." msgstr "" -#: ../../content/administration/upgrade.rst:70 -msgid "Report any issue encountered during the upgrade to Odoo via the `support page `__." +#: ../../content/administration/upgrade.rst:61 +msgid "Report any issue encountered during the upgrade to Odoo by `submitting a ticket for an issue related to my upgrade (production) `_." msgstr "" -#: ../../content/administration/upgrade.rst:76 +#: ../../content/administration/upgrade.rst:67 msgid "Obtaining an upgraded test database" msgstr "" -#: ../../content/administration/upgrade.rst:78 +#: ../../content/administration/upgrade.rst:69 msgid "The `Upgrade page `_ is the main platform for requesting an upgraded database. However, depending on the hosting type, you can upgrade from the command line (on-premise), the `Odoo Online database manager `_, or your `Odoo.sh project `_." msgstr "" -#: ../../content/administration/upgrade.rst:84 +#: ../../content/administration/upgrade.rst:75 msgid "The Upgrade platform follows the same `Privacy Policy `_ as the other Odoo.com services. Visit the `General Data Protection Regulation page `_ to learn more about how Odoo handles your data and privacy." msgstr "" -#: ../../content/administration/upgrade.rst:92 +#: ../../content/administration/upgrade.rst:83 msgid "Odoo Online databases can be manually upgraded via the `database manager `_." msgstr "" -#: ../../content/administration/upgrade.rst:95 +#: ../../content/administration/upgrade.rst:86 msgid "The database manager displays all databases associated with the user's account. Databases not on the most recent version of Odoo display an arrow in a circle icon next to their name, indicating that they can be upgraded." msgstr "" @@ -4925,19 +5044,19 @@ msgstr "" msgid "The database manager with an upgrade button next to the name of a database." msgstr "" -#: ../../content/administration/upgrade.rst:102 +#: ../../content/administration/upgrade.rst:93 msgid "Click the **arrow in a circle** icon to start the upgrade process. In the popup, fill in:" msgstr "" -#: ../../content/administration/upgrade.rst:104 +#: ../../content/administration/upgrade.rst:95 msgid "The **version** of Odoo you want to upgrade to, usually the latest version" msgstr "" -#: ../../content/administration/upgrade.rst:105 +#: ../../content/administration/upgrade.rst:96 msgid "The **email** address that should receive the link to the upgraded database" msgstr "" -#: ../../content/administration/upgrade.rst:106 +#: ../../content/administration/upgrade.rst:97 msgid "The :guilabel:`Purpose` of the upgrade, which is automatically set to :guilabel:`Test` for your first upgrade request" msgstr "" @@ -4945,7 +5064,7 @@ msgstr "" msgid "The \"Upgrade your database\" popup." msgstr "" -#: ../../content/administration/upgrade.rst:112 +#: ../../content/administration/upgrade.rst:103 msgid "The :guilabel:`Upgrade in progress` tag is displayed next to the database name until completion. Once the process succeeds, an email containing a link to the upgraded test database is sent to the address provided. The database can also be accessed from the database manager by clicking the dropdown arrow before the database name." msgstr "" @@ -4953,7 +5072,7 @@ msgstr "" msgid "Clicking the menu arrow displays the upgraded test database." msgstr "" -#: ../../content/administration/upgrade.rst:122 +#: ../../content/administration/upgrade.rst:113 msgid "Odoo.sh is integrated with the upgrade platform to simplify the upgrade process." msgstr "" @@ -4961,275 +5080,275 @@ msgstr "" msgid "Odoo.sh project and tabs" msgstr "" -#: ../../content/administration/upgrade.rst:127 +#: ../../content/administration/upgrade.rst:118 msgid "The **latest production daily automatic backup** is then sent to the `upgrade platform `_." msgstr "" -#: ../../content/administration/upgrade.rst:130 +#: ../../content/administration/upgrade.rst:121 msgid "Once the upgrade platform is done upgrading the backup and uploading it on the branch, it is put in a **special mode**: each time a **commit is pushed** on the branch, a **restore operation** of the upgraded backup and an **update of all the custom modules** occur. This allows you to test your custom modules on a pristine copy of the upgraded database. The log file of the upgrade process can be found in your newly upgraded staging build by going to :file:`~/logs/upgrade.log`." msgstr "" -#: ../../content/administration/upgrade.rst:138 +#: ../../content/administration/upgrade.rst:129 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:143 +#: ../../content/administration/upgrade.rst:134 msgid "Check out the :doc:`/developer/howtos/upgrade_custom_db` page for more information." msgstr "" -#: ../../content/administration/upgrade.rst:147 +#: ../../content/administration/upgrade.rst:138 msgid "The standard upgrade process can be initiated by entering the following command line on the machine where the database is hosted:" msgstr "" -#: ../../content/administration/upgrade.rst:154 +#: ../../content/administration/upgrade.rst:145 msgid "The following command can be used to display the general help and the main commands:" msgstr "" -#: ../../content/administration/upgrade.rst:160 +#: ../../content/administration/upgrade.rst:151 msgid "An upgraded test database can also be requested via the `Upgrade page `_." msgstr "" -#: ../../content/administration/upgrade.rst:164 +#: ../../content/administration/upgrade.rst:155 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. Check out the :doc:`/developer/howtos/upgrade_custom_db` page for more information." msgstr "" -#: ../../content/administration/upgrade.rst:169 +#: ../../content/administration/upgrade.rst:160 msgid "For security reasons, only the person who submitted the upgrade request can download it." msgstr "" -#: ../../content/administration/upgrade.rst:170 +#: ../../content/administration/upgrade.rst:161 msgid "For storage reasons, the database's copy is submitted without a filestore to the upgrade server. Therefore, the upgraded database does not contain the production filestore." msgstr "" -#: ../../content/administration/upgrade.rst:172 +#: ../../content/administration/upgrade.rst:163 msgid "Before restoring the upgraded database, its filestore must be merged with the production filestore to be able to perform tests in the same conditions as it would be in the new version." msgstr "" -#: ../../content/administration/upgrade.rst:175 +#: ../../content/administration/upgrade.rst:166 msgid "The upgraded database contains:" msgstr "" -#: ../../content/administration/upgrade.rst:177 +#: ../../content/administration/upgrade.rst:168 msgid "A `dump.sql` file containing the upgraded database" msgstr "" -#: ../../content/administration/upgrade.rst:178 +#: ../../content/administration/upgrade.rst:169 msgid "A `filestore` folder containing files extracted from in-database records into attachments (if there are any) and new standard Odoo files from the targeted Odoo version (e.g., new images, icons, payment provider's logos, etc.). This is the folder that should be merged with the production filestore in order to get the full upgraded filestore." msgstr "" -#: ../../content/administration/upgrade.rst:185 +#: ../../content/administration/upgrade.rst:176 msgid "You can request multiple test databases if you wish to test an upgrade more than once." msgstr "" -#: ../../content/administration/upgrade.rst:190 +#: ../../content/administration/upgrade.rst:181 msgid "When an upgrade request is completed, an upgrade report is attached to the successful upgrade email, and it becomes available in the Discuss app for users who are part of the \"Administration / Settings\" group. This report provides important information about the changes introduced by the new version." msgstr "" -#: ../../content/administration/upgrade.rst:198 +#: ../../content/administration/upgrade.rst:189 msgid "Testing the new version of the database" msgstr "" -#: ../../content/administration/upgrade.rst:200 +#: ../../content/administration/upgrade.rst:191 msgid "It is essential to spend some time testing the upgraded test database to ensure that you are not stuck in your day-to-day activities by a change in views, behavior, or an error message once the upgrade goes live." msgstr "" -#: ../../content/administration/upgrade.rst:205 +#: ../../content/administration/upgrade.rst:196 msgid "Test databases are neutralized, and some features are disabled to prevent them from impacting the production database:" msgstr "" -#: ../../content/administration/upgrade.rst:208 +#: ../../content/administration/upgrade.rst:199 msgid "Scheduled actions are disabled." msgstr "" -#: ../../content/administration/upgrade.rst:209 +#: ../../content/administration/upgrade.rst:200 msgid "Outgoing mail servers are disabled by archiving the existing ones and adding a fake one." msgstr "" -#: ../../content/administration/upgrade.rst:210 +#: ../../content/administration/upgrade.rst:201 msgid "Payment providers and delivery carriers are reset to the test environment." msgstr "" -#: ../../content/administration/upgrade.rst:211 +#: ../../content/administration/upgrade.rst:202 msgid "Bank synchronization is disabled. Should you want to test the synchronization, contact your bank synchronization provider to get sandbox credentials." msgstr "" -#: ../../content/administration/upgrade.rst:214 +#: ../../content/administration/upgrade.rst:205 msgid "Testing as many of your business flows as possible is strongly recommended to ensure they are working correctly and to get more familiar with the new version." msgstr "" -#: ../../content/administration/upgrade.rst:217 +#: ../../content/administration/upgrade.rst:208 msgid "Basic test checklist" msgstr "" -#: ../../content/administration/upgrade.rst:219 +#: ../../content/administration/upgrade.rst:210 msgid "Are there views that are deactivated in your test database but active in your production database?" msgstr "" -#: ../../content/administration/upgrade.rst:221 +#: ../../content/administration/upgrade.rst:212 msgid "Are your usual views still displayed correctly?" msgstr "" -#: ../../content/administration/upgrade.rst:222 +#: ../../content/administration/upgrade.rst:213 msgid "Are your reports (invoice, sales order, etc.) correctly generated?" msgstr "" -#: ../../content/administration/upgrade.rst:223 +#: ../../content/administration/upgrade.rst:214 msgid "Are your website pages working correctly?" msgstr "" -#: ../../content/administration/upgrade.rst:224 +#: ../../content/administration/upgrade.rst:215 msgid "Are you able to create and modify records? (sales orders, invoices, purchases, users, contacts, companies, etc.)" msgstr "" -#: ../../content/administration/upgrade.rst:226 +#: ../../content/administration/upgrade.rst:217 msgid "Are there any issues with your mail templates?" msgstr "" -#: ../../content/administration/upgrade.rst:227 +#: ../../content/administration/upgrade.rst:218 msgid "Are there any issues with saved translations?" msgstr "" -#: ../../content/administration/upgrade.rst:228 +#: ../../content/administration/upgrade.rst:219 msgid "Are your search filters still present?" msgstr "" -#: ../../content/administration/upgrade.rst:229 +#: ../../content/administration/upgrade.rst:220 msgid "Can you export your data?" msgstr "" -#: ../../content/administration/upgrade.rst:233 +#: ../../content/administration/upgrade.rst:224 msgid "Checking a random product in your product catalog and comparing its test and production data to verify everything is the same (product category, selling price, cost price, vendor, accounts, routes, etc.)." msgstr "" -#: ../../content/administration/upgrade.rst:236 +#: ../../content/administration/upgrade.rst:227 msgid "Buying this product (Purchase app)." msgstr "" -#: ../../content/administration/upgrade.rst:237 +#: ../../content/administration/upgrade.rst:228 msgid "Confirming the reception of this product (Inventory app)." msgstr "" -#: ../../content/administration/upgrade.rst:238 +#: ../../content/administration/upgrade.rst:229 msgid "Checking if the route to receive this product is the same in your production database (Inventory app)." msgstr "" -#: ../../content/administration/upgrade.rst:240 +#: ../../content/administration/upgrade.rst:231 msgid "Selling this product (Sales app) to a random customer." msgstr "" -#: ../../content/administration/upgrade.rst:241 +#: ../../content/administration/upgrade.rst:232 msgid "Opening your customer database (Contacts app), selecting a customer (or company), and checking its data." msgstr "" -#: ../../content/administration/upgrade.rst:243 +#: ../../content/administration/upgrade.rst:234 msgid "Shipping this product (Inventory app)." msgstr "" -#: ../../content/administration/upgrade.rst:244 +#: ../../content/administration/upgrade.rst:235 msgid "Checking if the route to ship this product is the same as in your production database (Inventory app)." msgstr "" -#: ../../content/administration/upgrade.rst:246 +#: ../../content/administration/upgrade.rst:237 msgid "Validating a customer invoice (Invoicing or Accounting app)." msgstr "" -#: ../../content/administration/upgrade.rst:247 +#: ../../content/administration/upgrade.rst:238 msgid "Crediting the invoice (issuing a credit note) and checking if it behaves as in your production database." msgstr "" -#: ../../content/administration/upgrade.rst:249 +#: ../../content/administration/upgrade.rst:240 msgid "Checking your reports' results (Accounting app)." msgstr "" -#: ../../content/administration/upgrade.rst:250 +#: ../../content/administration/upgrade.rst:241 msgid "Randomly checking your taxes, currencies, bank accounts, and fiscal year (Accounting app)." msgstr "" -#: ../../content/administration/upgrade.rst:251 +#: ../../content/administration/upgrade.rst:242 msgid "Making an online order (Website apps) from the product selection in your shop until the checkout process and checking if everything behaves as in your production database." msgstr "" -#: ../../content/administration/upgrade.rst:254 +#: ../../content/administration/upgrade.rst:245 msgid "This list is **not** exhaustive. Extend the example to your other apps based on your use of Odoo." msgstr "" -#: ../../content/administration/upgrade.rst:256 -msgid "If you face an issue while testing your upgraded test database, you can request the assistance of Odoo via the `support page `__ by selecting the option related to testing the upgrade. In any case, it is essential to report any problem encountered during the testing to fix it before upgrading your production database." +#: ../../content/administration/upgrade.rst:247 +msgid "If you face an issue while testing your upgraded test database, you can request the assistance of Odoo by `submitting a ticket for an issue related to my future upgrade (I am testing an upgrade) `_. In any case, it is essential to report any problem encountered during the testing to fix it before upgrading your production database." msgstr "" -#: ../../content/administration/upgrade.rst:261 +#: ../../content/administration/upgrade.rst:252 msgid "You might encounter significant differences with standard views, features, fields, and models during testing. Those changes cannot be reverted on a case-by-case basis. However, if a change introduced by a new version breaks a customization, it is the responsibility of the maintainer of your custom module to make it compatible with the new version of Odoo." msgstr "" -#: ../../content/administration/upgrade.rst:267 +#: ../../content/administration/upgrade.rst:258 msgid "Do not forget to test:" msgstr "" -#: ../../content/administration/upgrade.rst:269 +#: ../../content/administration/upgrade.rst:260 msgid "Integrations with external software (EDI, APIs, etc.)" msgstr "" -#: ../../content/administration/upgrade.rst:270 +#: ../../content/administration/upgrade.rst:261 msgid "Workflows between different apps (online sales with eCommerce, converting a lead all the way to a sales order, delivery of products, etc.)" msgstr "" -#: ../../content/administration/upgrade.rst:272 +#: ../../content/administration/upgrade.rst:263 msgid "Data exports" msgstr "" -#: ../../content/administration/upgrade.rst:273 +#: ../../content/administration/upgrade.rst:264 msgid "Automated actions" msgstr "" -#: ../../content/administration/upgrade.rst:274 +#: ../../content/administration/upgrade.rst:265 msgid "Server actions in the action menu on form views, as well as by selecting multiple records on list views" msgstr "" -#: ../../content/administration/upgrade.rst:280 +#: ../../content/administration/upgrade.rst:271 msgid "Upgrading the production database" msgstr "" -#: ../../content/administration/upgrade.rst:282 -msgid "Once the :ref:`tests ` are completed and you are confident that the upgraded database can be used as your main database without any issues, it is time to plan the go-live day. It can be planned in coordination with Odoo's upgrade support analysts, reachable via the `support page `__." +#: ../../content/administration/upgrade.rst:273 +msgid "Once the :ref:`tests ` are completed and you are confident that the upgraded database can be used as your main database without any issues, it is time to plan the go-live day. It can be planned in coordination with Odoo's upgrade support analysts by `submitting a ticket for an issue related to my future upgrade (I am testing an upgrade) `_." msgstr "" -#: ../../content/administration/upgrade.rst:287 +#: ../../content/administration/upgrade.rst:279 msgid "Your production database will be unavailable during its upgrade. Therefore, we recommend planning the upgrade at a time when the use of the database is minimal." msgstr "" -#: ../../content/administration/upgrade.rst:290 +#: ../../content/administration/upgrade.rst:282 msgid "As the standard upgrade scripts and your database are constantly evolving, it is also recommended to frequently request another upgraded test database to ensure that the upgrade process is still successful, especially if it takes a long time to finish. **Fully rehearsing the upgrade process the day before upgrading the production database is also recommended.**" msgstr "" -#: ../../content/administration/upgrade.rst:296 +#: ../../content/administration/upgrade.rst:288 msgid "Going into production without first testing may lead to:" msgstr "" -#: ../../content/administration/upgrade.rst:298 +#: ../../content/administration/upgrade.rst:290 msgid "Users failing to adjust to the changes and new features" msgstr "" -#: ../../content/administration/upgrade.rst:299 +#: ../../content/administration/upgrade.rst:291 msgid "Business interruptions (e.g., no longer having the possibility to validate an action)" msgstr "" -#: ../../content/administration/upgrade.rst:300 +#: ../../content/administration/upgrade.rst:292 msgid "Poor customer experience (e.g., an eCommerce website that does not work correctly)" msgstr "" -#: ../../content/administration/upgrade.rst:302 +#: ../../content/administration/upgrade.rst:294 msgid "The process of upgrading a production database is similar to upgrading a test database with a few exceptions." msgstr "" -#: ../../content/administration/upgrade.rst:309 +#: ../../content/administration/upgrade.rst:301 msgid "The process is similar to :ref:`obtaining an upgraded test database `, except for the purpose option, which must be set to :guilabel:`Production` instead of :guilabel:`Test`." msgstr "" -#: ../../content/administration/upgrade.rst:314 +#: ../../content/administration/upgrade.rst:306 msgid "Once the upgrade is requested, the database will be unavailable until the upgrade is finished. Once the process is completed, it is impossible to revert to the previous version." msgstr "" -#: ../../content/administration/upgrade.rst:320 +#: ../../content/administration/upgrade.rst:312 msgid "The process is similar to :ref:`obtaining an upgraded test database ` on the :guilabel:`Production` branch." msgstr "" @@ -5237,98 +5356,98 @@ msgstr "" msgid "View from the upgrade tab" msgstr "" -#: ../../content/administration/upgrade.rst:326 +#: ../../content/administration/upgrade.rst:318 msgid "The process is **triggered as soon as a new commit is made** on the branch. This allows the upgrade process to be synchronized with the deployment of the custom modules' upgraded source code. If there are no custom modules, the upgrade process is triggered immediately." msgstr "" -#: ../../content/administration/upgrade.rst:332 +#: ../../content/administration/upgrade.rst:324 msgid "The database is unavailable throughout the process. If anything goes wrong, the platform automatically reverts the upgrade, as it would be for a regular update. In case of success, a backup of the database before the upgrade is created." msgstr "" -#: ../../content/administration/upgrade.rst:336 +#: ../../content/administration/upgrade.rst:328 msgid "The update of your custom modules must be successful to complete the entire upgrade process. Make sure the status of your staging upgrade is :guilabel:`successful` before trying it in production. More information on how to upgrade your custom modules can be found on :doc:`/developer/howtos/upgrade_custom_db`." msgstr "" -#: ../../content/administration/upgrade.rst:343 +#: ../../content/administration/upgrade.rst:335 msgid "The command to upgrade a database to production is similar to the one of upgrading a test database except for the argument `test`, which must be replaced by `production`:" msgstr "" -#: ../../content/administration/upgrade.rst:350 +#: ../../content/administration/upgrade.rst:342 msgid "An upgraded production database can also be requested via the `Upgrade page `_. Once the database is uploaded, any modification to your production database will **not** be present on your upgraded database. This is why we recommend not using it during the upgrade process." msgstr "" -#: ../../content/administration/upgrade.rst:357 +#: ../../content/administration/upgrade.rst:349 msgid "When requesting an upgraded database for production purposes, the copy is submitted without a filestore. Therefore, the upgraded database filestore must be merged with the production filestore before deploying the new version." msgstr "" -#: ../../content/administration/upgrade.rst:361 -msgid "In case of an issue with your production database, you can request the assistance of Odoo via the `support page `__ by selecting the option related to the upgrade in production." +#: ../../content/administration/upgrade.rst:353 +msgid "In case of an issue with your production database, you can request the assistance of Odoo by `submitting a ticket for an issue related to my upgrade (production) `_." msgstr "" -#: ../../content/administration/upgrade.rst:369 +#: ../../content/administration/upgrade.rst:360 msgid "Service-level agreement (SLA)" msgstr "" -#: ../../content/administration/upgrade.rst:371 +#: ../../content/administration/upgrade.rst:362 msgid "With Odoo Enterprise, upgrading a database to the most recent version of Odoo is **free**, including any support required to rectify potential discrepancies in the upgraded database." msgstr "" -#: ../../content/administration/upgrade.rst:374 +#: ../../content/administration/upgrade.rst:365 msgid "Information about the upgrade services included in the Enterprise Licence is available in the :ref:`Odoo Enterprise Subscription Agreement `. However, this section clarifies what upgrade services you can expect." msgstr "" -#: ../../content/administration/upgrade.rst:379 +#: ../../content/administration/upgrade.rst:370 msgid "Upgrade services covered by the SLA" msgstr "" -#: ../../content/administration/upgrade.rst:381 +#: ../../content/administration/upgrade.rst:372 msgid "Databases hosted on Odoo's cloud platforms (Odoo Online and Odoo.sh) or self-hosted (On-Premise) can benefit from upgrade services at all times for:" msgstr "" -#: ../../content/administration/upgrade.rst:384 +#: ../../content/administration/upgrade.rst:375 msgid "the upgrade of all **standard applications**;" msgstr "" -#: ../../content/administration/upgrade.rst:385 +#: ../../content/administration/upgrade.rst:376 msgid "the upgrade of all **customizations created with the Studio app**, as long as Studio is still installed and the respective subscription is still active; and" msgstr "" -#: ../../content/administration/upgrade.rst:387 +#: ../../content/administration/upgrade.rst:378 msgid "the upgrade of all **developments and customizations covered by a maintenance of customizations subscription**." msgstr "" -#: ../../content/administration/upgrade.rst:390 +#: ../../content/administration/upgrade.rst:381 msgid "Upgrade services are limited to the technical conversion and adaptation of a database (standard modules and data) to make it compatible with the version targeted by the upgrade." msgstr "" -#: ../../content/administration/upgrade.rst:394 +#: ../../content/administration/upgrade.rst:385 msgid "Upgrade services not covered by the SLA" msgstr "" -#: ../../content/administration/upgrade.rst:396 +#: ../../content/administration/upgrade.rst:387 msgid "The following upgrade-related services are **not** included:" msgstr "" -#: ../../content/administration/upgrade.rst:398 +#: ../../content/administration/upgrade.rst:389 msgid "the **cleaning** of pre-existing data and configurations while upgrading;" msgstr "" -#: ../../content/administration/upgrade.rst:399 +#: ../../content/administration/upgrade.rst:390 msgid "the upgrade of **custom modules created in-house or by third parties**, including Odoo partners;" msgstr "" -#: ../../content/administration/upgrade.rst:400 +#: ../../content/administration/upgrade.rst:391 msgid "lines of **code added to standard modules**, i.e., customizations created outside the Studio app, code entered manually, and :ref:`automated actions using Python code `; and" msgstr "" -#: ../../content/administration/upgrade.rst:403 +#: ../../content/administration/upgrade.rst:394 msgid "**training** on using the upgraded version's features and workflows." msgstr "" -#: ../../content/administration/upgrade.rst:406 +#: ../../content/administration/upgrade.rst:397 msgid ":doc:`Odoo.sh documentation `" msgstr "" -#: ../../content/administration/upgrade.rst:407 +#: ../../content/administration/upgrade.rst:398 msgid ":doc:`Supported Odoo versions `" msgstr "" diff --git a/locale/sources/contributing.pot b/locale/sources/contributing.pot index d78b111a4..1cb12dc8b 100644 --- a/locale/sources/contributing.pot +++ b/locale/sources/contributing.pot @@ -8,7 +8,7 @@ msgid "" msgstr "" "Project-Id-Version: Odoo 17.0\n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2024-03-08 12:48+0000\n" +"POT-Creation-Date: 2024-04-30 09:16+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 @@ -113,61 +113,72 @@ msgid ":doc:`Guide: Contributing to the codebase `" msgstr "" #: ../../content/contributing.rst:51 -msgid ":doc:`Developer tutorials `" +msgid ":doc:`Developer tutorials `" msgstr "" #: ../../content/contributing.rst:52 -#: ../../content/contributing.rst:65 -msgid "Developers with experience in Python and web development" +msgid ":doc:`How-to guides `" msgstr "" #: ../../content/contributing.rst:53 -msgid "Contribute to the documentation" +#: ../../content/contributing.rst:66 +msgid "Developers with experience in Python and web development" msgstr "" #: ../../content/contributing.rst:54 +msgid "Contribute to the documentation" +msgstr "" + +#: ../../content/contributing.rst:55 msgid "Submit corrections and improvements to the Odoo documentation. The product evolves fast, and it can be challenging to consistently reflect these changes in the documentation. By updating the documentation, you can help many users find their way in Odoo." msgstr "" -#: ../../content/contributing.rst:57 +#: ../../content/contributing.rst:58 msgid ":doc:`Guide: Contributing to the documentation `" msgstr "" -#: ../../content/contributing.rst:58 +#: ../../content/contributing.rst:59 msgid "Anyone interested in improving the Odoo documentation" msgstr "" -#: ../../content/contributing.rst:59 +#: ../../content/contributing.rst:60 msgid "Create custom modules" msgstr "" -#: ../../content/contributing.rst:60 +#: ../../content/contributing.rst:61 msgid "Develop new modules to extend the functionality of Odoo. Custom modules can be made available for free or paid on the Odoo App Store or on any other Odoo modules library. By creating custom modules and making them available to others, you can help grow the Odoo ecosystem and provide additional value to users of the platform." msgstr "" -#: ../../content/contributing.rst:64 +#: ../../content/contributing.rst:65 msgid "`Odoo Apps Store `_" msgstr "" -#: ../../content/contributing.rst:68 +#: ../../content/contributing.rst:69 msgid "It is mainly Odoo employees who develop new features for the codebase and write new content for the documentation. Be sure to discuss any idea for a new feature or page with the Odoo team so they can give you the green light before you begin working on it. Some features may already be in development on their side, and only approved features can be merged." msgstr "" +#: ../../content/contributing/check_mergeability_status.rst:1 +#: ../../content/contributing/check_mergeability_status.rst:1 +#: ../../content/contributing/check_mergeability_status.rst:1 +#: ../../content/contributing/check_mergeability_status.rst:1 #: ../../content/contributing/check_mergeability_status.rst:1 #: ../../content/contributing/check_mergeability_status.rst:1 msgid "At the bottom of the page, check the mergeability status and address any issues." msgstr "" +#: ../../content/contributing/configure_git_authorship.rst:1 #: ../../content/contributing/configure_git_authorship.rst:1 #: ../../content/contributing/configure_git_authorship.rst:1 msgid "Configure Git to identify yourself as the author of your future contributions. Enter the same email address you used to register on GitHub." msgstr "" +#: ../../content/contributing/configure_github_account.rst:1 #: ../../content/contributing/configure_github_account.rst:1 #: ../../content/contributing/configure_github_account.rst:1 msgid "`Generate a new SSH key and register it on your GitHub account `_." msgstr "" +#: ../../content/contributing/create_github_account.rst:1 #: ../../content/contributing/create_github_account.rst:1 #: ../../content/contributing/create_github_account.rst:1 msgid "First, you need to `create a GitHub account `_. Odoo uses GitHub to manage the source code of its products, and this is where you will make your changes and submit them for review." @@ -203,44 +214,50 @@ msgstr "" msgid "Go to `github.com/odoo/odoo `_ and click on the :guilabel:`Fork` button in the top right corner to create a fork (:dfn:`your own copy`) of the repository on your account. Do the same with `github.com/odoo/enterprise `_ if you have access to it. This creates a copy of the codebase to which you can make changes without affecting the main codebase. Skip this step if you work at Odoo." msgstr "" +#: ../../content/contributing/install_git.rst:1 #: ../../content/contributing/install_git.rst:1 #: ../../content/contributing/install_git.rst:1 msgid "`Install Git `_. It is a command-line (:dfn:`a text interface`) tool that allows tracking the history of changes made to a file and, more importantly, working on different versions of that file simultaneously. It means you do not need to worry about overwriting someone else’s pending work when making changes." msgstr "" +#: ../../content/contributing/install_git.rst:6 #: ../../content/contributing/install_git.rst:6 #: ../../content/contributing/install_git.rst:6 msgid "Verify that the installation directory of Git is included in your system's `PATH` variable." msgstr "" +#: ../../content/contributing/install_git.rst:10 +#: ../../content/contributing/install_git.rst:10 #: ../../content/contributing/documentation.rst:97 #: ../../content/contributing/documentation.rst:124 #: ../../content/contributing/documentation.rst:140 #: ../../content/contributing/install_git.rst:10 -#: ../../content/contributing/install_git.rst:10 msgid "Linux and macOS" msgstr "" +#: ../../content/contributing/install_git.rst:12 #: ../../content/contributing/install_git.rst:12 #: ../../content/contributing/install_git.rst:12 msgid "Follow the `guide to update the PATH variable on Linux and macOS `_ with the installation path of Git (by default :file:`/usr/bin/git`)." msgstr "" +#: ../../content/contributing/install_git.rst:16 +#: ../../content/contributing/install_git.rst:16 #: ../../content/contributing/documentation.rst:104 #: ../../content/contributing/documentation.rst:130 #: ../../content/contributing/documentation.rst:146 #: ../../content/contributing/install_git.rst:16 -#: ../../content/contributing/install_git.rst:16 msgid "Windows" msgstr "" +#: ../../content/contributing/install_git.rst:18 #: ../../content/contributing/install_git.rst:18 #: ../../content/contributing/install_git.rst:18 msgid "Follow the `guide to update the PATH variable on Windows `_ with the installation path of Git (by default :file:`C:\\\\Program Files\\\\Git`)." msgstr "" #: ../../content/contributing/development.rst:40 -msgid ":doc:`Install Odoo from the sources <../administration/install/source>`. 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 +303,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 17, which corresponds to branch `17.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 17, which corresponds to branch `17.0`." msgstr "" #: ../../content/contributing/development.rst:99 @@ -368,6 +385,10 @@ msgstr "" msgid "Complete the description and click on the :guilabel:`Create pull request` button again." msgstr "" +#: ../../content/contributing/handle_reviews.rst:1 +#: ../../content/contributing/handle_reviews.rst:1 +#: ../../content/contributing/handle_reviews.rst:1 +#: ../../content/contributing/handle_reviews.rst:1 #: ../../content/contributing/handle_reviews.rst:1 #: ../../content/contributing/handle_reviews.rst:1 msgid "As soon as your :abbr:`PR (Pull Request)` is ready for merging, a member of the Odoo team will be automatically assigned for review. If the reviewer has questions or remarks, they will post them as comments and you will be notified by email. Those comments must be resolved for the contribution to go forward." @@ -1597,6 +1618,9 @@ msgstr "" msgid "Review the summary that you wrote about your changes and click on the :guilabel:`Create pull request` button again." msgstr "" +#: ../../content/contributing/documentation/changes_approved.rst:1 +#: ../../content/contributing/documentation/changes_approved.rst:1 +#: ../../content/contributing/documentation/changes_approved.rst:1 #: ../../content/contributing/documentation/changes_approved.rst:1 #: ../../content/contributing/documentation/changes_approved.rst:1 msgid "Once your changes are approved, the reviewer merges them and they appear online the next day!" @@ -1611,7 +1635,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 17, which corresponds to branch `17.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 17, which corresponds to branch `17.0`." msgstr "" #: ../../content/contributing/documentation.rst:233 diff --git a/locale/sources/essentials.pot b/locale/sources/essentials.pot index e2bac2bb7..da9d1d6dc 100644 --- a/locale/sources/essentials.pot +++ b/locale/sources/essentials.pot @@ -8,7 +8,7 @@ msgid "" msgstr "" "Project-Id-Version: Odoo 17.0\n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2024-03-25 16:01+0000\n" +"POT-Creation-Date: 2024-04-30 09:16+0000\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME \n" "Language-Team: LANGUAGE \n" @@ -345,7 +345,7 @@ msgid "When working with a database, it is sometimes necessary to export data in msgstr "" #: ../../content/applications/essentials/export_import_data.rst:22 -msgid "With Odoo, the values can be exported from any field in any record. To do so, activate the list view (:guilabel:`☰ (three horizontal lines)` icon), on the items that need to be exported, and then select the records that should be exported. To select a record, tick the checkbox next to the corresponding record. Finally, click on :guilabel:`⚙️ Action`, and then :guilabel:`Export`." +msgid "With Odoo, the values can be exported from any field in any record. To do so, activate the list view (:guilabel:`≣ (four horizontal lines)` icon), on the items that need to be exported, and then select the records that should be exported. To select a record, tick the checkbox next to the corresponding record. Finally, click on :guilabel:`⚙️ Action`, and then :guilabel:`Export`." msgstr "" #: ../../content/applications/essentials/export_import_data.rst:-1 @@ -385,26 +385,26 @@ msgid "The :guilabel:`🗑️ (trash can)` icon is used to remove fields. Click msgstr "" #: ../../content/applications/essentials/export_import_data.rst:56 -msgid "For recurring reports, it is helpful to save export presets. Select all the needed fields, and click on the template drop-down menu. Once there, click on :guilabel:`New template`, and give a unique name to the export just created. The next time the same list needs to be exported, select the related template that was previously saved from the drop-down menu." +msgid "For recurring reports, it is helpful to save export presets. Select all the needed fields, and click on the template drop-down menu. Once there, click on :guilabel:`New template`, and give a unique name to the export just created. Click the :guilabel:`💾 (floppy drive)` icon to save the configuration. The next time the same list needs to be exported, select the related template that was previously saved from the drop-down menu." msgstr "" -#: ../../content/applications/essentials/export_import_data.rst:62 +#: ../../content/applications/essentials/export_import_data.rst:63 msgid "It is helpful to know the field's external identifier. For example, :guilabel:`Related Company` in the export user interface is equal to *parent_id* (external identifier). This is helpful because then, the only data exported is what should be modified and re-imported." msgstr "" -#: ../../content/applications/essentials/export_import_data.rst:69 +#: ../../content/applications/essentials/export_import_data.rst:70 msgid "Import data into Odoo" msgstr "" -#: ../../content/applications/essentials/export_import_data.rst:71 +#: ../../content/applications/essentials/export_import_data.rst:72 msgid "Importing data into Odoo is extremely helpful during implementation, or in times where data needs to be updated in bulk. The following documentation covers how to import data into an Odoo database." msgstr "" -#: ../../content/applications/essentials/export_import_data.rst:75 +#: ../../content/applications/essentials/export_import_data.rst:76 msgid "Imports are permanent and **cannot** be undone. However, it is possible to use filters (`created on` or `last modified`) to identify records changed or created by the import." msgstr "" -#: ../../content/applications/essentials/export_import_data.rst:79 +#: ../../content/applications/essentials/export_import_data.rst:80 msgid "Activating :ref:`developer mode ` changes the visible import settings in the left menu. Doing so reveals an :menuselection:`Advanced` menu. Included in this advanced menu are two options: :guilabel:`Track history during import` and :guilabel:`Allow matching with subfields`." msgstr "" @@ -412,35 +412,35 @@ msgstr "" msgid "Advanced import options when developer mode is activated." msgstr "" -#: ../../content/applications/essentials/export_import_data.rst:87 +#: ../../content/applications/essentials/export_import_data.rst:88 msgid "If the model uses openchatter, the :guilabel:`Track history during import` option sets up subscriptions and sends notifications during the import, but leads to a slower import." msgstr "" -#: ../../content/applications/essentials/export_import_data.rst:90 +#: ../../content/applications/essentials/export_import_data.rst:91 msgid "Should the :guilabel:`Allow matching with subfields` option be selected, then all subfields within a field are used to match under the :guilabel:`Odoo Field` while importing." msgstr "" -#: ../../content/applications/essentials/export_import_data.rst:94 +#: ../../content/applications/essentials/export_import_data.rst:95 msgid "Get started" msgstr "" -#: ../../content/applications/essentials/export_import_data.rst:96 +#: ../../content/applications/essentials/export_import_data.rst:97 msgid "Data can be imported on any Odoo business object using either Excel (`.xlsx`) or :abbr:`CSV (Comma-separated Values)` (`.csv`) formats. This includes: contacts, products, bank statements, journal entries, and orders." msgstr "" -#: ../../content/applications/essentials/export_import_data.rst:100 -msgid "Open the view of the object to which the data should be imported/populated, and click on :menuselection:`⭐ Favorites --> Import records`." +#: ../../content/applications/essentials/export_import_data.rst:101 +msgid "Open the view of the object to which the data should be imported/populated, and click on :menuselection:`⚙️ (Action) --> Import records`." msgstr "" #: ../../content/applications/essentials/export_import_data.rst:-1 -msgid "Favorites menu revealed with the import records option highlighted." +msgid "Action menu revealed with the import records option highlighted." msgstr "" -#: ../../content/applications/essentials/export_import_data.rst:107 +#: ../../content/applications/essentials/export_import_data.rst:108 msgid "After clicking :guilabel:`Import records`, Odoo reveals a separate page with templates that can be downloaded and populated with the company's own data. Such templates can be imported in one click, since the data mapping is already done. To download a template click :guilabel:`Import Template for Customers` at the center of the page." msgstr "" -#: ../../content/applications/essentials/export_import_data.rst:113 +#: ../../content/applications/essentials/export_import_data.rst:114 msgid "When importing a :abbr:`CSV (Comma-separated Values)` file, Odoo provides :guilabel:`Formatting` options. These options do **not** appear when importing the proprietary Excel file type (`.xls`, `.xlsx`)." msgstr "" @@ -448,31 +448,31 @@ msgstr "" msgid "Formatting options presented when a CVS file is imported in Odoo." msgstr "" -#: ../../content/applications/essentials/export_import_data.rst:121 +#: ../../content/applications/essentials/export_import_data.rst:122 msgid "Make necessary adjustments to the *Formatting* options, and ensure all columns in the :guilabel:`Odoo field` and :guilabel:`File Column` are free of errors. Finally, click :guilabel:`Import` to import the data." msgstr "" -#: ../../content/applications/essentials/export_import_data.rst:126 +#: ../../content/applications/essentials/export_import_data.rst:127 msgid "Adapt a template" msgstr "" -#: ../../content/applications/essentials/export_import_data.rst:128 +#: ../../content/applications/essentials/export_import_data.rst:129 msgid "Import templates are provided in the import tool of the most common data to import (contacts, products, bank statements, etc.). Open them with any spreadsheet software (*Microsoft Office*, *OpenOffice*, *Google Drive*, etc.)." msgstr "" -#: ../../content/applications/essentials/export_import_data.rst:132 +#: ../../content/applications/essentials/export_import_data.rst:133 msgid "Once the template is downloaded, proceed to follow these steps:" msgstr "" -#: ../../content/applications/essentials/export_import_data.rst:134 +#: ../../content/applications/essentials/export_import_data.rst:135 msgid "Add, remove, and sort columns to best fit the data structure." msgstr "" -#: ../../content/applications/essentials/export_import_data.rst:135 +#: ../../content/applications/essentials/export_import_data.rst:136 msgid "It is strongly advised to **not** remove the :guilabel:`External ID` (ID) column (see why in the next section)." msgstr "" -#: ../../content/applications/essentials/export_import_data.rst:137 +#: ../../content/applications/essentials/export_import_data.rst:138 msgid "Set a unique ID to every record by dragging down the ID sequencing in the :guilabel:`External ID` (ID) column." msgstr "" @@ -480,7 +480,7 @@ msgstr "" msgid "An animation of the mouse dragging down the ID column, so each record has a unique ID." msgstr "" -#: ../../content/applications/essentials/export_import_data.rst:145 +#: ../../content/applications/essentials/export_import_data.rst:146 msgid "When a new column is added, Odoo may not be able to map it automatically, if its label does not fit any field within Odoo. However, new columns can be mapped manually when the import is tested. Search the drop-down menu for the corresponding field." msgstr "" @@ -488,67 +488,67 @@ msgstr "" msgid "Drop-down menu expanded in the initial import screen on Odoo." msgstr "" -#: ../../content/applications/essentials/export_import_data.rst:153 +#: ../../content/applications/essentials/export_import_data.rst:154 msgid "Then, use this field's label in the import file to ensure future imports are successful." msgstr "" -#: ../../content/applications/essentials/export_import_data.rst:156 +#: ../../content/applications/essentials/export_import_data.rst:157 msgid "Another useful way to find out the proper column names to import is to export a sample file using the fields that should be imported. This way, if there is not a sample import template, the names are accurate." msgstr "" -#: ../../content/applications/essentials/export_import_data.rst:161 +#: ../../content/applications/essentials/export_import_data.rst:162 msgid "Import from another application" msgstr "" -#: ../../content/applications/essentials/export_import_data.rst:163 +#: ../../content/applications/essentials/export_import_data.rst:164 msgid "The :guilabel:`External ID` (ID) is a unique identifier for the line item. Feel free to use one from previous software to facilitate the transition to Odoo." msgstr "" -#: ../../content/applications/essentials/export_import_data.rst:166 +#: ../../content/applications/essentials/export_import_data.rst:167 msgid "Setting an ID is not mandatory when importing, but it helps in many cases:" msgstr "" -#: ../../content/applications/essentials/export_import_data.rst:168 +#: ../../content/applications/essentials/export_import_data.rst:169 msgid "Update imports: import the same file several times without creating duplicates." msgstr "" -#: ../../content/applications/essentials/export_import_data.rst:169 +#: ../../content/applications/essentials/export_import_data.rst:170 msgid ":ref:`Import relation fields `." msgstr "" -#: ../../content/applications/essentials/export_import_data.rst:171 +#: ../../content/applications/essentials/export_import_data.rst:172 msgid "To recreate relationships between different records, the unique identifier from the original application should be used to map it to the :guilabel:`External ID` (ID) column in Odoo." msgstr "" -#: ../../content/applications/essentials/export_import_data.rst:174 +#: ../../content/applications/essentials/export_import_data.rst:175 msgid "When another record is imported that links to the first one, use **XXX/ID** (XXX/External ID) for the original unique identifier. This record can also be found using its name." msgstr "" -#: ../../content/applications/essentials/export_import_data.rst:178 +#: ../../content/applications/essentials/export_import_data.rst:179 msgid "It should be noted that there will be a conflict if two or more records have the same name." msgstr "" -#: ../../content/applications/essentials/export_import_data.rst:180 +#: ../../content/applications/essentials/export_import_data.rst:181 msgid "The :guilabel:`External ID` (ID) can also be used to update the original import, if modified data needs to be re-imported later, therefore, it is a good practice to specify it whenever possible." msgstr "" -#: ../../content/applications/essentials/export_import_data.rst:184 +#: ../../content/applications/essentials/export_import_data.rst:185 msgid "Field missing to map column" msgstr "" -#: ../../content/applications/essentials/export_import_data.rst:186 +#: ../../content/applications/essentials/export_import_data.rst:187 msgid "Odoo heuristically tries to find the type of field for each column inside the imported file, based on the first ten lines of the files." msgstr "" -#: ../../content/applications/essentials/export_import_data.rst:189 +#: ../../content/applications/essentials/export_import_data.rst:190 msgid "For example, if there is a column only containing numbers, only the fields with the *integer* type are presented as options." msgstr "" -#: ../../content/applications/essentials/export_import_data.rst:192 +#: ../../content/applications/essentials/export_import_data.rst:193 msgid "While this behavior might be beneficial in most cases, it is also possible that it could fail, or the column may be mapped to a field that is not proposed by default." msgstr "" -#: ../../content/applications/essentials/export_import_data.rst:195 +#: ../../content/applications/essentials/export_import_data.rst:196 msgid "If this happens, check the :guilabel:`Show fields of relation fields (advanced) option`, then a complete list of fields becomes available for each column." msgstr "" @@ -556,324 +556,324 @@ msgstr "" msgid "Searching for the field to match the tax column." msgstr "" -#: ../../content/applications/essentials/export_import_data.rst:203 +#: ../../content/applications/essentials/export_import_data.rst:204 msgid "Change data import format" msgstr "" -#: ../../content/applications/essentials/export_import_data.rst:206 +#: ../../content/applications/essentials/export_import_data.rst:207 msgid "Odoo can automatically detect if a column is a date, and tries to guess the date format from a set of most commonly used date formats. While this process can work for many date formats, some date formats are not recognizable. This can cause confusion, due to day-month inversions; it is difficult to guess which part of a date format is the day, and which part is the month, in a date, such as `01-03-2016`." msgstr "" -#: ../../content/applications/essentials/export_import_data.rst:212 +#: ../../content/applications/essentials/export_import_data.rst:213 msgid "When importing a :abbr:`CSV (Comma-separated Values)` file, Odoo provides :guilabel:`Formatting` options." msgstr "" -#: ../../content/applications/essentials/export_import_data.rst:215 +#: ../../content/applications/essentials/export_import_data.rst:216 msgid "To view which date format Odoo has found from the file, check the :guilabel:`Date Format` that is shown when clicking on options under the file selector. If this format is incorrect, change it to the preferred format using *ISO 8601* to define the format." msgstr "" -#: ../../content/applications/essentials/export_import_data.rst:220 +#: ../../content/applications/essentials/export_import_data.rst:221 msgid "*ISO 8601* is an international standard, covering the worldwide exchange, along with the communication of date and time-related data. For example, the date format should be `YYYY-MM-DD`. So, in the case of July 24th 1981, it should be written as `1981-07-24`." msgstr "" -#: ../../content/applications/essentials/export_import_data.rst:225 +#: ../../content/applications/essentials/export_import_data.rst:226 msgid "When importing Excel files (`.xls`, `.xlsx`), consider using *date cells* to store dates. This maintains locale date formats for display, regardless of how the date is formatted in Odoo. When importing a :abbr:`CSV (Comma-separated Values)` file, use Odoo's :guilabel:`Formatting` section to select the date format columns to import." msgstr "" -#: ../../content/applications/essentials/export_import_data.rst:231 +#: ../../content/applications/essentials/export_import_data.rst:232 msgid "Import numbers with currency signs" msgstr "" -#: ../../content/applications/essentials/export_import_data.rst:233 +#: ../../content/applications/essentials/export_import_data.rst:234 msgid "Odoo fully supports numbers with parenthesis to represent negative signs, as well as numbers with currency signs attached to them. Odoo also automatically detects which thousand/decimal separator is used. If a currency symbol unknown to Odoo is used, it might not be recognized as a number, and the import crashes." msgstr "" -#: ../../content/applications/essentials/export_import_data.rst:239 +#: ../../content/applications/essentials/export_import_data.rst:240 msgid "When importing a :abbr:`CSV (Comma-separated Values)` file, the :guilabel:`Formatting` menu appears on the left-hand column. Under these options, the :guilabel:`Thousands Separator` can be changed." msgstr "" -#: ../../content/applications/essentials/export_import_data.rst:243 +#: ../../content/applications/essentials/export_import_data.rst:244 msgid "Examples of supported numbers (using 'thirty-two thousand' as the figure):" msgstr "" -#: ../../content/applications/essentials/export_import_data.rst:245 +#: ../../content/applications/essentials/export_import_data.rst:246 msgid "32.000,00" msgstr "" -#: ../../content/applications/essentials/export_import_data.rst:246 +#: ../../content/applications/essentials/export_import_data.rst:247 msgid "32000,00" msgstr "" -#: ../../content/applications/essentials/export_import_data.rst:247 +#: ../../content/applications/essentials/export_import_data.rst:248 msgid "32,000.00" msgstr "" -#: ../../content/applications/essentials/export_import_data.rst:248 +#: ../../content/applications/essentials/export_import_data.rst:249 msgid "-32000.00" msgstr "" -#: ../../content/applications/essentials/export_import_data.rst:249 +#: ../../content/applications/essentials/export_import_data.rst:250 msgid "(32000.00)" msgstr "" -#: ../../content/applications/essentials/export_import_data.rst:250 +#: ../../content/applications/essentials/export_import_data.rst:251 msgid "$ 32.000,00" msgstr "" -#: ../../content/applications/essentials/export_import_data.rst:251 +#: ../../content/applications/essentials/export_import_data.rst:252 msgid "(32000.00 €)" msgstr "" -#: ../../content/applications/essentials/export_import_data.rst:253 +#: ../../content/applications/essentials/export_import_data.rst:254 msgid "Example that will not work:" msgstr "" -#: ../../content/applications/essentials/export_import_data.rst:255 +#: ../../content/applications/essentials/export_import_data.rst:256 msgid "ABC 32.000,00" msgstr "" -#: ../../content/applications/essentials/export_import_data.rst:256 +#: ../../content/applications/essentials/export_import_data.rst:257 msgid "$ (32.000,00)" msgstr "" -#: ../../content/applications/essentials/export_import_data.rst:259 +#: ../../content/applications/essentials/export_import_data.rst:260 msgid "A :guilabel:`() (parenthesis)` around the number indicates that the number is a negative value. The currency symbol **must** be placed within the parenthesis for Odoo to recognize it as a negative currency value." msgstr "" -#: ../../content/applications/essentials/export_import_data.rst:264 +#: ../../content/applications/essentials/export_import_data.rst:265 msgid "Import preview table not displayed correctly" msgstr "" -#: ../../content/applications/essentials/export_import_data.rst:266 +#: ../../content/applications/essentials/export_import_data.rst:267 msgid "By default, the import preview is set on commas as field separators, and quotation marks as text delimiters. If the :abbr:`CSV (Comma-separated Values)` file does not have these settings, modify the :guilabel:`Formatting` options (displayed under the :guilabel:`Import` :abbr:`CSV (Comma-separated Values)` file bar after selecting the :abbr:`CSV (Comma-separated Values)` file)." msgstr "" -#: ../../content/applications/essentials/export_import_data.rst:272 +#: ../../content/applications/essentials/export_import_data.rst:273 msgid "If the :abbr:`CSV (Comma-separated Values)` file has a tabulation as a separator, Odoo does **not** detect the separations. The file format options need to be modified in the spreadsheet application. See the following :ref:`Change CSV file format ` section." msgstr "" -#: ../../content/applications/essentials/export_import_data.rst:280 +#: ../../content/applications/essentials/export_import_data.rst:281 msgid "Change CSV file format in spreadsheet application" msgstr "" -#: ../../content/applications/essentials/export_import_data.rst:282 +#: ../../content/applications/essentials/export_import_data.rst:283 msgid "When editing and saving :abbr:`CSV (Comma-separated Values)` files in spreadsheet applications, the computer's regional settings are applied for the separator and delimiter. Odoo suggests using *OpenOffice* or *LibreOffice*, as both applications allow modifications of all three options (from *LibreOffice* application, go to :menuselection:`'Save As' dialog box --> Check the box 'Edit filter settings' --> Save`)." msgstr "" -#: ../../content/applications/essentials/export_import_data.rst:288 +#: ../../content/applications/essentials/export_import_data.rst:289 msgid "Microsoft Excel can modify the encoding when saving (:menuselection:`'Save As' dialog box --> 'Tools' drop-down menu --> Encoding tab`)." msgstr "" -#: ../../content/applications/essentials/export_import_data.rst:292 +#: ../../content/applications/essentials/export_import_data.rst:293 msgid "Difference between Database ID and External ID" msgstr "" -#: ../../content/applications/essentials/export_import_data.rst:294 +#: ../../content/applications/essentials/export_import_data.rst:295 msgid "Some fields define a relationship with another object. For example, the country of a contact is a link to a record of the 'Country' object. When such fields are imported, Odoo has to recreate links between the different records. To help import such fields, Odoo provides three mechanisms." msgstr "" -#: ../../content/applications/essentials/export_import_data.rst:299 +#: ../../content/applications/essentials/export_import_data.rst:300 msgid "**Only one** mechanism should be used per field that is imported." msgstr "" -#: ../../content/applications/essentials/export_import_data.rst:301 +#: ../../content/applications/essentials/export_import_data.rst:302 msgid "For example, to reference the country of a contact, Odoo proposes three different fields to import:" msgstr "" -#: ../../content/applications/essentials/export_import_data.rst:303 +#: ../../content/applications/essentials/export_import_data.rst:304 msgid ":guilabel:`Country`: the name or code of the country" msgstr "" -#: ../../content/applications/essentials/export_import_data.rst:304 +#: ../../content/applications/essentials/export_import_data.rst:305 msgid ":guilabel:`Country/Database ID`: the unique Odoo ID for a record, defined by the ID PostgreSQL column" msgstr "" -#: ../../content/applications/essentials/export_import_data.rst:306 +#: ../../content/applications/essentials/export_import_data.rst:307 msgid ":guilabel:`Country/External ID`: the ID of this record referenced in another application (or the `.XML` file that imported it)" msgstr "" -#: ../../content/applications/essentials/export_import_data.rst:309 +#: ../../content/applications/essentials/export_import_data.rst:310 msgid "For the country of Belgium, for example, use one of these three ways to import:" msgstr "" -#: ../../content/applications/essentials/export_import_data.rst:311 +#: ../../content/applications/essentials/export_import_data.rst:312 msgid ":guilabel:`Country`: `Belgium`" msgstr "" -#: ../../content/applications/essentials/export_import_data.rst:312 +#: ../../content/applications/essentials/export_import_data.rst:313 msgid ":guilabel:`Country/Database ID`: `21`" msgstr "" -#: ../../content/applications/essentials/export_import_data.rst:313 +#: ../../content/applications/essentials/export_import_data.rst:314 msgid ":guilabel:`Country/External ID`: `base.be`" msgstr "" -#: ../../content/applications/essentials/export_import_data.rst:315 +#: ../../content/applications/essentials/export_import_data.rst:316 msgid "According to the company's need, use one of these three ways to reference records in relations. Here is an example when one or the other should be used, according to the need:" msgstr "" -#: ../../content/applications/essentials/export_import_data.rst:318 +#: ../../content/applications/essentials/export_import_data.rst:319 msgid "Use :guilabel:`Country`: this is the easiest way when data comes from :abbr:`CSV (Comma-separated Values)` files that have been created manually." msgstr "" -#: ../../content/applications/essentials/export_import_data.rst:320 +#: ../../content/applications/essentials/export_import_data.rst:321 msgid "Use :guilabel:`Country/Database ID`: this should rarely be used. It is mostly used by developers as the main advantage is to never have conflicts (there may be several records with the same name, but they always have a unique Database ID)" msgstr "" -#: ../../content/applications/essentials/export_import_data.rst:323 +#: ../../content/applications/essentials/export_import_data.rst:324 msgid "Use :guilabel:`Country/External ID`: use *External ID* when importing data from a third-party application." msgstr "" -#: ../../content/applications/essentials/export_import_data.rst:326 +#: ../../content/applications/essentials/export_import_data.rst:327 msgid "When *External IDs* are used, import :abbr:`CSV (Comma-separated Values)` files with the :guilabel:`External ID` (ID) column defining the *External ID* of each record that is imported. Then, a reference can be made to that record with columns, like `Field/External ID`. The following two :abbr:`CSV (Comma-separated Values)` files provide an example for products and their categories." msgstr "" -#: ../../content/applications/essentials/export_import_data.rst:331 +#: ../../content/applications/essentials/export_import_data.rst:332 msgid ":download:`CSV file for categories `" msgstr "" -#: ../../content/applications/essentials/export_import_data.rst:333 +#: ../../content/applications/essentials/export_import_data.rst:334 msgid ":download:`CSV file for Products `" msgstr "" -#: ../../content/applications/essentials/export_import_data.rst:339 +#: ../../content/applications/essentials/export_import_data.rst:340 msgid "Import relation fields" msgstr "" -#: ../../content/applications/essentials/export_import_data.rst:341 +#: ../../content/applications/essentials/export_import_data.rst:342 msgid "An Odoo object is always related to many other objects (e.g. a product is linked to product categories, attributes, vendors, etc.). To import those relations, the records of the related object need to be imported first, from their own list menu." msgstr "" -#: ../../content/applications/essentials/export_import_data.rst:345 +#: ../../content/applications/essentials/export_import_data.rst:346 msgid "This can be achieved by using either the name of the related record, or its ID, depending on the circumstances. The ID is expected when two records have the same name. In such a case add `/ ID` at the end of the column title (e.g. for product attributes: `Product Attributes / Attribute / ID`)." msgstr "" -#: ../../content/applications/essentials/export_import_data.rst:350 +#: ../../content/applications/essentials/export_import_data.rst:351 msgid "Options for multiple matches on fields" msgstr "" -#: ../../content/applications/essentials/export_import_data.rst:352 +#: ../../content/applications/essentials/export_import_data.rst:353 msgid "If, for example, there are two product categories with the child name `Sellable` (e.g. `Misc. Products/Sellable` & `Other Products/Sellable`), the validation is halted, but the data may still be imported. However, Odoo recommends that the data is not imported because it will all be linked to the first `Sellable` category found in the *Product Category* list (`Misc. Products/Sellable`). Odoo, instead, recommends modifying one of the duplicate's values, or the product category hierarchy." msgstr "" -#: ../../content/applications/essentials/export_import_data.rst:359 +#: ../../content/applications/essentials/export_import_data.rst:360 msgid "However, if the company does not wish to change the configuration of product categories, Odoo recommends making use of the *External ID* for this field, 'Category'." msgstr "" -#: ../../content/applications/essentials/export_import_data.rst:363 +#: ../../content/applications/essentials/export_import_data.rst:364 msgid "Import many2many relationship fields" msgstr "" -#: ../../content/applications/essentials/export_import_data.rst:365 +#: ../../content/applications/essentials/export_import_data.rst:366 msgid "The tags should be separated by a comma, without any spacing. For example, if a customer needs to be linked to both tags: `Manufacturer` and `Retailer` then 'Manufacturer,Retailer' needs to be encoded in the same column of the :abbr:`CSV (Comma-separated Values)` file." msgstr "" -#: ../../content/applications/essentials/export_import_data.rst:369 +#: ../../content/applications/essentials/export_import_data.rst:370 msgid ":download:`CSV file for Manufacturer, Retailer `" msgstr "" -#: ../../content/applications/essentials/export_import_data.rst:372 +#: ../../content/applications/essentials/export_import_data.rst:373 msgid "Import one2many relationships" msgstr "" -#: ../../content/applications/essentials/export_import_data.rst:374 +#: ../../content/applications/essentials/export_import_data.rst:375 msgid "If a company wants to import a sales order with several order lines, a specific row **must** be reserved in the :abbr:`CSV (Comma-separated Values)` file for each order line. The first order line is imported on the same row as the information relative to order. Any additional lines need an additional row that does not have any information in the fields relative to the order." msgstr "" -#: ../../content/applications/essentials/export_import_data.rst:379 +#: ../../content/applications/essentials/export_import_data.rst:380 msgid "As an example, here is a :abbr:`CSV (Comma-separated Values)` file of some quotations that can be imported, based on demo data:" msgstr "" -#: ../../content/applications/essentials/export_import_data.rst:382 +#: ../../content/applications/essentials/export_import_data.rst:383 msgid ":download:`File for some Quotations `" msgstr "" -#: ../../content/applications/essentials/export_import_data.rst:385 +#: ../../content/applications/essentials/export_import_data.rst:386 msgid "The following :abbr:`CSV (Comma-separated Values)` file shows how to import purchase orders with their respective purchase order lines:" msgstr "" -#: ../../content/applications/essentials/export_import_data.rst:388 +#: ../../content/applications/essentials/export_import_data.rst:389 msgid ":download:`Purchase orders with their respective purchase order lines `" msgstr "" -#: ../../content/applications/essentials/export_import_data.rst:391 +#: ../../content/applications/essentials/export_import_data.rst:392 msgid "The following :abbr:`CSV (Comma-separated Values)` file shows how to import customers and their respective contacts:" msgstr "" -#: ../../content/applications/essentials/export_import_data.rst:394 +#: ../../content/applications/essentials/export_import_data.rst:395 msgid ":download:`Customers and their respective contacts `" msgstr "" -#: ../../content/applications/essentials/export_import_data.rst:398 +#: ../../content/applications/essentials/export_import_data.rst:399 msgid "Import records several times" msgstr "" -#: ../../content/applications/essentials/export_import_data.rst:400 +#: ../../content/applications/essentials/export_import_data.rst:401 msgid "If an imported file contains one of the columns: :guilabel:`External ID` or :guilabel:`Database ID`, records that have already been imported are modified, instead of being created. This is extremely useful as it allows users to import the same :abbr:`CSV (Comma-separated Values)` file several times, while having made some changes in between two imports." msgstr "" -#: ../../content/applications/essentials/export_import_data.rst:405 +#: ../../content/applications/essentials/export_import_data.rst:406 msgid "Odoo takes care of creating or modifying each record, depending if it is new or not." msgstr "" -#: ../../content/applications/essentials/export_import_data.rst:407 +#: ../../content/applications/essentials/export_import_data.rst:408 msgid "This feature allows a company to use the *Import/Export tool* in Odoo to modify a batch of records in a spreadsheet application." msgstr "" -#: ../../content/applications/essentials/export_import_data.rst:411 +#: ../../content/applications/essentials/export_import_data.rst:412 msgid "Value not provided for a specific field" msgstr "" -#: ../../content/applications/essentials/export_import_data.rst:413 +#: ../../content/applications/essentials/export_import_data.rst:414 msgid "If all fields are not set in the CSV file, Odoo assigns the default value for every non-defined field. But, if fields are set with empty values in the :abbr:`CSV (Comma-separated Values)` file, Odoo sets the empty value in the field, instead of assigning the default value." msgstr "" -#: ../../content/applications/essentials/export_import_data.rst:418 +#: ../../content/applications/essentials/export_import_data.rst:419 msgid "Export/import different tables from an SQL application to Odoo" msgstr "" -#: ../../content/applications/essentials/export_import_data.rst:420 +#: ../../content/applications/essentials/export_import_data.rst:421 msgid "If data needs to be imported from different tables, relations need to be recreated between records belonging to different tables. For instance, if companies and people are imported, the link between each person and the company they work for needs to be recreated." msgstr "" -#: ../../content/applications/essentials/export_import_data.rst:424 +#: ../../content/applications/essentials/export_import_data.rst:425 msgid "To manage relations between tables, use the `External ID` facilities of Odoo. The `External ID` of a record is the unique identifier of this record in another application. The `External ID` must be unique across all records of all objects. It is a good practice to prefix this `External ID` with the name of the application or table. (like, 'company_1', 'person_1' - instead of '1')" msgstr "" -#: ../../content/applications/essentials/export_import_data.rst:429 +#: ../../content/applications/essentials/export_import_data.rst:430 msgid "As an example, suppose there is an SQL database with two tables that are to be imported: companies and people. Each person belongs to one company, so the link between a person and the company they work for must be recreated." msgstr "" -#: ../../content/applications/essentials/export_import_data.rst:433 +#: ../../content/applications/essentials/export_import_data.rst:434 msgid "Test this example, with a :download:`sample of a PostgreSQL database `." msgstr "" -#: ../../content/applications/essentials/export_import_data.rst:436 +#: ../../content/applications/essentials/export_import_data.rst:437 msgid "First, export all companies and their *External ID*. In PSQL, write the following command:" msgstr "" -#: ../../content/applications/essentials/export_import_data.rst:442 +#: ../../content/applications/essentials/export_import_data.rst:443 msgid "This SQL command creates the following :abbr:`CSV (Comma-separated Values)` file:" msgstr "" -#: ../../content/applications/essentials/export_import_data.rst:451 +#: ../../content/applications/essentials/export_import_data.rst:452 msgid "To create the :abbr:`CSV (Comma-separated Values)` file for people linked to companies, use the following SQL command in PSQL:" msgstr "" -#: ../../content/applications/essentials/export_import_data.rst:458 +#: ../../content/applications/essentials/export_import_data.rst:459 msgid "It produces the following :abbr:`CSV (Comma-separated Values)` file:" msgstr "" -#: ../../content/applications/essentials/export_import_data.rst:468 +#: ../../content/applications/essentials/export_import_data.rst:469 msgid "In this file, Fabien and Laurence are working for the Bigees company (`company_1`), and Eric is working for the Organi company. The relation between people and companies is done using the *External ID* of the companies. The *External ID* is prefixed by the name of the table to avoid a conflict of ID between people and companies (`person_1` and `company_1`, who shared the same ID 1 in the original database)." msgstr "" -#: ../../content/applications/essentials/export_import_data.rst:474 +#: ../../content/applications/essentials/export_import_data.rst:475 msgid "The two files produced are ready to be imported in Odoo without any modifications. After having imported these two :abbr:`CSV (Comma-separated Values)` files, there are four contacts and three companies (the first two contacts are linked to the first company). Keep in mind to first import the companies, and then the people." msgstr "" #: ../../content/applications/essentials/in_app_purchase.rst:3 -msgid "In-app purchase (IAP)" +msgid "In-app purchases (IAP)" msgstr "" #: ../../content/applications/essentials/in_app_purchase.rst:7 @@ -893,134 +893,134 @@ msgid "|IAP| services do **not** need to be configured or set up before use. Odo msgstr "" #: ../../content/applications/essentials/in_app_purchase.rst:25 -msgid "Users with an Enterprise version of Odoo Online get free credits to test IAP features." -msgstr "" - -#: ../../content/applications/essentials/in_app_purchase.rst:30 -msgid "IAP services" +msgid "Enterprise Odoo users with a valid subscription get free credits to test IAP features before deciding to purchase more credits for the database. This includes demo/training databases, educational databases, and one-app-free databases." msgstr "" #: ../../content/applications/essentials/in_app_purchase.rst:32 -msgid "|IAP| services are provided by Odoo, as well as third-parties, and have a wide range of uses." +msgid "IAP services" msgstr "" #: ../../content/applications/essentials/in_app_purchase.rst:34 -msgid "The following |IAP| services are provided by Odoo:" +msgid "|IAP| services are provided by Odoo, as well as third-parties, and have a wide range of uses." msgstr "" #: ../../content/applications/essentials/in_app_purchase.rst:36 -msgid ":guilabel:`Documents Digitization`: digitizes scanned or PDF vendor bills, expenses, and resumes with OCR and AI." +msgid "The following |IAP| services are offered by Odoo:" msgstr "" #: ../../content/applications/essentials/in_app_purchase.rst:38 -msgid ":guilabel:`Partner Autocomplete`: automatically populates contact records with corporate data." -msgstr "" - -#: ../../content/applications/essentials/in_app_purchase.rst:39 -msgid ":guilabel:`SMS`: sends SMS text messages to contacts directly from the database." +msgid ":guilabel:`Documents Digitization`: digitizes scanned or PDF vendor bills, expenses, and resumes with OCR and AI." msgstr "" #: ../../content/applications/essentials/in_app_purchase.rst:40 -msgid ":guilabel:`Lead Generation`: generates leads based on a set of criteria, and converts web visitors into quality leads and opportunities." +msgid ":guilabel:`Partner Autocomplete`: automatically populates contact records with corporate data." +msgstr "" + +#: ../../content/applications/essentials/in_app_purchase.rst:41 +msgid ":guilabel:`SMS`: sends SMS text messages to contacts directly from the database." msgstr "" #: ../../content/applications/essentials/in_app_purchase.rst:42 -msgid ":guilabel:`Snailmail`: sends customer invoices and follow-up reports by post, worldwide." +msgid ":guilabel:`Lead Generation`: generates leads based on a set of criteria, and converts web visitors into quality leads and opportunities." msgstr "" #: ../../content/applications/essentials/in_app_purchase.rst:44 -msgid "For more information on every service currently available, visit the `Odoo IAP Catalog `_." +msgid ":guilabel:`Snailmail`: sends customer invoices and follow-up reports by post, worldwide." msgstr "" -#: ../../content/applications/essentials/in_app_purchase.rst:48 +#: ../../content/applications/essentials/in_app_purchase.rst:45 +msgid ":guilabel:`Signer identification with itsme®️`: ask document signatories in Odoo *Sign* to provide their identity using the *itsme®* identity platform, which is available in Belgium and the Netherlands." +msgstr "" + +#: ../../content/applications/essentials/in_app_purchase.rst:49 +msgid "For more information on every service currently available (offered from developers other than Odoo), visit the `Odoo IAP Catalog `_." +msgstr "" + +#: ../../content/applications/essentials/in_app_purchase.rst:53 msgid "Use IAP services" msgstr "" -#: ../../content/applications/essentials/in_app_purchase.rst:50 +#: ../../content/applications/essentials/in_app_purchase.rst:55 msgid "|IAP| services are automatically integrated with Odoo, and do **not** require users to configure any settings. To use a service, simply interact with it wherever it appears in the database." msgstr "" -#: ../../content/applications/essentials/in_app_purchase.rst:54 +#: ../../content/applications/essentials/in_app_purchase.rst:59 msgid "The following flow focuses on the *SMS* |IAP| service being used from a contact's record." msgstr "" -#: ../../content/applications/essentials/in_app_purchase.rst:56 -msgid "This can be done by clicking the :guilabel:`📱 (phone) SMS` icon within the database." +#: ../../content/applications/essentials/in_app_purchase.rst:61 +msgid "This can be done by clicking the :guilabel:`📱 SMS` icon within the database." msgstr "" #: ../../content/applications/essentials/in_app_purchase.rst:-1 msgid "The SMS icon on a typical contact information form located within an Odoo database." msgstr "" -#: ../../content/applications/essentials/in_app_purchase.rst:62 +#: ../../content/applications/essentials/in_app_purchase.rst:67 msgid "One way to utilize the *SMS* |IAP| service with Odoo is showcased in the following steps:" msgstr "" -#: ../../content/applications/essentials/in_app_purchase.rst:64 -msgid "Navigate to the :menuselection:`Contacts application`, and click on a contact with a mobile phone number entered in either the :guilabel:`Phone` or :guilabel:`Mobile` field of the contact form." -msgstr "" - -#: ../../content/applications/essentials/in_app_purchase.rst:67 -msgid "Hover the mouse over the :guilabel:`Phone` or :guilabel:`Mobile` field, and a :guilabel:`📱 (phone) SMS` icon appears to the right." -msgstr "" - #: ../../content/applications/essentials/in_app_purchase.rst:69 -msgid "Click the :guilabel:`📱 (phone) SMS` icon, and a :guilabel:`Send SMS Text Message` pop-up window appears." +msgid "First, navigate to the :menuselection:`Contacts application`, and click on a contact with a mobile phone number entered in either the :guilabel:`Phone` or :guilabel:`Mobile` field of the contact form." msgstr "" -#: ../../content/applications/essentials/in_app_purchase.rst:71 -msgid "Type a message in the :guilabel:`Message` field of the :guilabel:`Send SMS Text Message` pop-up window. Then, click the :guilabel:`Send SMS` button. Odoo then sends the message, via SMS, to the contact, and logs what was sent in the *chatter* of the contact's form." +#: ../../content/applications/essentials/in_app_purchase.rst:73 +msgid "Next, find the :guilabel:`📱 SMS` icon that appears to the right of the :guilabel:`Phone` or :guilabel:`Mobile` fields. Click the :guilabel:`📱 SMS` icon, and a :guilabel:`Send SMS Text Message` pop-up window appears." msgstr "" -#: ../../content/applications/essentials/in_app_purchase.rst:75 +#: ../../content/applications/essentials/in_app_purchase.rst:77 +msgid "Type a message in the :guilabel:`Message` field of the pop-up window. Then, click the :guilabel:`Send SMS` button. Odoo then sends the message, via SMS, to the contact, and logs what was sent in the *chatter* of the contact's form." +msgstr "" + +#: ../../content/applications/essentials/in_app_purchase.rst:81 msgid "Upon sending the SMS message, the prepaid credits for the *SMS* |IAP| service are automatically deducted from the existing credits. If there are not enough credits to send the message, Odoo prompts the user to purchase more." msgstr "" -#: ../../content/applications/essentials/in_app_purchase.rst:80 +#: ../../content/applications/essentials/in_app_purchase.rst:86 msgid "For more information on how to use various |IAP| services, and for more in-depth instructions related to SMS functionality in Odoo, review the documentation below:" msgstr "" -#: ../../content/applications/essentials/in_app_purchase.rst:83 -msgid ":doc:`Lead mining `" +#: ../../content/applications/essentials/in_app_purchase.rst:89 +msgid ":doc:`Lead mining <../sales/crm/acquire_leads/lead_mining>`" msgstr "" -#: ../../content/applications/essentials/in_app_purchase.rst:84 -msgid ":doc:`Enrich your contacts base with Partner Autocomplete `" +#: ../../content/applications/essentials/in_app_purchase.rst:90 +msgid ":doc:`Enrich your contacts base with Partner Autocomplete <../sales/crm/optimize/partner_autocomplete>`" msgstr "" -#: ../../content/applications/essentials/in_app_purchase.rst:86 -msgid ":doc:`SMS essentials `" -msgstr "" - -#: ../../content/applications/essentials/in_app_purchase.rst:91 -msgid "IAP credits" -msgstr "" - -#: ../../content/applications/essentials/in_app_purchase.rst:93 -msgid "Every time an |IAP| service is used, the prepaid credits for that service are spent. Odoo prompts the purchase of more credits when there are not enough credits left to continue using a service. Email alerts can also be set up for when :ref:`credits are low `." +#: ../../content/applications/essentials/in_app_purchase.rst:92 +msgid ":doc:`SMS essentials <../marketing/sms_marketing/essentials/sms_essentials>`" msgstr "" #: ../../content/applications/essentials/in_app_purchase.rst:97 +msgid "IAP credits" +msgstr "" + +#: ../../content/applications/essentials/in_app_purchase.rst:99 +msgid "Every time an |IAP| service is used, the prepaid credits for that service are spent. Odoo prompts the purchase of more credits when there are not enough credits left to continue using a service. Email alerts can also be set up for when :ref:`credits are low `." +msgstr "" + +#: ../../content/applications/essentials/in_app_purchase.rst:103 msgid "Credits are purchased in *Packs* from the `Odoo IAP Catalog `_, and pricing is specific to each service." msgstr "" -#: ../../content/applications/essentials/in_app_purchase.rst:101 +#: ../../content/applications/essentials/in_app_purchase.rst:107 msgid "The `SMS service `_ has four packs available, in denominations of:" msgstr "" -#: ../../content/applications/essentials/in_app_purchase.rst:104 +#: ../../content/applications/essentials/in_app_purchase.rst:110 msgid ":guilabel:`Starter Pack`: 10 credits" msgstr "" -#: ../../content/applications/essentials/in_app_purchase.rst:105 +#: ../../content/applications/essentials/in_app_purchase.rst:111 msgid ":guilabel:`Standard Pack`: 100 credits" msgstr "" -#: ../../content/applications/essentials/in_app_purchase.rst:106 +#: ../../content/applications/essentials/in_app_purchase.rst:112 msgid ":guilabel:`Advanced Pack`: 500 credits" msgstr "" -#: ../../content/applications/essentials/in_app_purchase.rst:107 +#: ../../content/applications/essentials/in_app_purchase.rst:113 msgid ":guilabel:`Expert Pack`: 1,000 credits" msgstr "" @@ -1028,104 +1028,84 @@ msgstr "" msgid "Four different packs of credits for the SMS IAP service." msgstr "" -#: ../../content/applications/essentials/in_app_purchase.rst:113 +#: ../../content/applications/essentials/in_app_purchase.rst:119 msgid "The number of credits consumed depends on the length of the SMS and the country of destination." msgstr "" -#: ../../content/applications/essentials/in_app_purchase.rst:115 -msgid "For more information, refer to the :doc:`SMS Pricing and FAQ ` documentation." +#: ../../content/applications/essentials/in_app_purchase.rst:121 +msgid "For more information, refer to the :doc:`SMS Pricing and FAQ <../marketing/sms_marketing/pricing/pricing_and_faq>` documentation." msgstr "" -#: ../../content/applications/essentials/in_app_purchase.rst:121 +#: ../../content/applications/essentials/in_app_purchase.rst:127 msgid "Buy credits" msgstr "" -#: ../../content/applications/essentials/in_app_purchase.rst:123 +#: ../../content/applications/essentials/in_app_purchase.rst:129 msgid "If there are not enough credits to perform a task, the database automatically prompts the purchase of more credits." msgstr "" -#: ../../content/applications/essentials/in_app_purchase.rst:126 -msgid "Users can check the current balance of credits for each service, and manually purchase more credits, by navigating to the :menuselection:`Settings app --> Search IAP --> View My Services`." -msgstr "" - -#: ../../content/applications/essentials/in_app_purchase.rst:129 -#: ../../content/applications/essentials/in_app_purchase.rst:146 -msgid "Doing so reveals an :guilabel:`IAP Account` page, listing the various |IAP| services in the database. From here, click an |IAP| service to open its :guilabel:`Account Information` page, where additional credits can be purchased." -msgstr "" - -#: ../../content/applications/essentials/in_app_purchase.rst:134 -msgid "Manually buy credits" +#: ../../content/applications/essentials/in_app_purchase.rst:132 +msgid "Users can check the current balance of credits for each service, and manually purchase more credits, by navigating to the :menuselection:`Settings app --> Contacts section`, and beneath the :guilabel:`Odoo IAP` setting, click :guilabel:`View My Services`." msgstr "" #: ../../content/applications/essentials/in_app_purchase.rst:136 +msgid "Doing so reveals an :guilabel:`IAP Service` page, listing the various |IAP| services in the database. From here, click an |IAP| service to open its :guilabel:`Account Information` page, where additional credits can be purchased." +msgstr "" + +#: ../../content/applications/essentials/in_app_purchase.rst:141 +msgid "Manually buy credits" +msgstr "" + +#: ../../content/applications/essentials/in_app_purchase.rst:143 msgid "To manually buy credits in Odoo, follow these steps:" msgstr "" -#: ../../content/applications/essentials/in_app_purchase.rst:138 -#: ../../content/applications/essentials/in_app_purchase.rst:173 -msgid "Go to the :menuselection:`Settings application`." +#: ../../content/applications/essentials/in_app_purchase.rst:145 +msgid "First, go to the :menuselection:`Settings application` and type `IAP` in the :guilabel:`Search...` bar. Alternatively users can scroll down to the :guilabel:`Contacts` section. Under the :guilabel:`Contacts` section, where it says :guilabel:`Odoo IAP`, click :guilabel:`View My Services`." msgstr "" -#: ../../content/applications/essentials/in_app_purchase.rst:139 -#: ../../content/applications/essentials/in_app_purchase.rst:174 -msgid "Type `IAP` in the search bar." -msgstr "" - -#: ../../content/applications/essentials/in_app_purchase.rst:140 -#: ../../content/applications/essentials/in_app_purchase.rst:175 -msgid "Click :guilabel:`View My Services`." -msgstr "" - -#: ../../content/applications/essentials/in_app_purchase.rst:0 +#: ../../content/applications/essentials/in_app_purchase.rst:-1 msgid "The Settings app showing the Odoo IAP heading and View My Services button." msgstr "" -#: ../../content/applications/essentials/in_app_purchase.rst:149 -msgid "On the :guilabel:`Account Information` page, click the :guilabel:`Buy Credit` button." +#: ../../content/applications/essentials/in_app_purchase.rst:154 +msgid "Doing so reveals an :guilabel:`IAP Account` page, listing the various |IAP| services in the database. From here, click an |IAP| service to open its :guilabel:`Account Information` page, where additional credits can be purchased." msgstr "" -#: ../../content/applications/essentials/in_app_purchase.rst:0 -msgid "The Account Information page for an IAP service showing the Buy Credit button." +#: ../../content/applications/essentials/in_app_purchase.rst:158 +msgid "On the :guilabel:`Account Information` page, click the :guilabel:`Buy Credit` button. Doing so loads a :guilabel:`Buy Credits for (IAP Account)` page in a new tab. From here, click :guilabel:`Buy` on the desired pack of credits. Then, follow the prompts to enter payment details, and confirm the order." msgstr "" -#: ../../content/applications/essentials/in_app_purchase.rst:155 -msgid "Doing so loads a :guilabel:`Buy Credits for (IAP Account)` page in a new tab. From here, click :guilabel:`Buy` on the desired pack of credits. Then, follow the prompts to enter payment details, and confirm the order." -msgstr "" - -#: ../../content/applications/essentials/in_app_purchase.rst:0 +#: ../../content/applications/essentials/in_app_purchase.rst:-1 msgid "The SMS service page on IAP.Odoo.com with four packs of credits available for purchase." msgstr "" -#: ../../content/applications/essentials/in_app_purchase.rst:163 +#: ../../content/applications/essentials/in_app_purchase.rst:167 msgid "Once the transaction is complete, the credits are available for use in the database." msgstr "" -#: ../../content/applications/essentials/in_app_purchase.rst:168 +#: ../../content/applications/essentials/in_app_purchase.rst:172 msgid "Low-credit notification" msgstr "" -#: ../../content/applications/essentials/in_app_purchase.rst:170 +#: ../../content/applications/essentials/in_app_purchase.rst:174 msgid "It is possible to be notified when credits are low, in order to avoid running out of credits, while using an |IAP| service. To do that, follow this process:" msgstr "" -#: ../../content/applications/essentials/in_app_purchase.rst:176 +#: ../../content/applications/essentials/in_app_purchase.rst:177 +msgid "Go to the :menuselection:`Settings application`, and type `IAP` in the :guilabel:`Search...` bar. Under the :guilabel:`Contacts` section, where it says :guilabel:`Odoo IAP`, click :guilabel:`View My Services`." +msgstr "" + +#: ../../content/applications/essentials/in_app_purchase.rst:181 msgid "The available |IAP| accounts appear in a list view on the :guilabel:`IAP Account` page. From here, click on the desired |IAP| account to view that service's :guilabel:`Account Information` page." msgstr "" -#: ../../content/applications/essentials/in_app_purchase.rst:179 -msgid "On the :guilabel:`Account Information` page, tick the :guilabel:`Warn Me` box. Doing so reveals two fields on the form: :guilabel:`Threshold` and :guilabel:`Warning Email`." +#: ../../content/applications/essentials/in_app_purchase.rst:184 +msgid "On the :guilabel:`Account Information` page, tick the :guilabel:`Warn Me` checkbox. Doing so reveals two fields on the form: :guilabel:`Threshold` and :guilabel:`Warning Email`." msgstr "" -#: ../../content/applications/essentials/in_app_purchase.rst:0 -msgid "Odoo will send an email alert when credits for this service fall below the threshold." -msgstr "" - -#: ../../content/applications/essentials/in_app_purchase.rst:186 -msgid "In the :guilabel:`Threshold` field, enter an amount of credits Odoo should use as the minimum threshold for this service." -msgstr "" - -#: ../../content/applications/essentials/in_app_purchase.rst:188 -msgid "In the :guilabel:`Warning Email` field, enter the email address that should receive the notification." +#: ../../content/applications/essentials/in_app_purchase.rst:187 +msgid "In the :guilabel:`Threshold` field, enter an amount of credits Odoo should use as the minimum threshold for this service. In the :guilabel:`Warning Email` field, enter the email address that receives the notification." msgstr "" #: ../../content/applications/essentials/in_app_purchase.rst:191 @@ -1350,93 +1330,237 @@ msgid "Regular line chart example" msgstr "" #: ../../content/applications/essentials/search.rst:3 -msgid "Search and filter records" +msgid "Search, filter, and group records" msgstr "" #: ../../content/applications/essentials/search.rst:5 -msgid "Odoo uses filters to include only the most relevant records depending on the purpose of the view you are on. However, you can edit the default filter or search for specific values." +msgid "Odoo allows for the searching, filtering, and grouping of records in a view to display only the most relevant records. The search bar is located at the top of the view, start typing to :ref:`search for values `, or click the :guilabel:`🔽 (down arrow)` icon to access the :ref:`Filter `, :ref:`Group By `, and :ref:`Favorites ` drop-down menus." msgstr "" -#: ../../content/applications/essentials/search.rst:11 -msgid "Preconfigured filters" -msgstr "" - -#: ../../content/applications/essentials/search.rst:13 -msgid "You can modify the default selection of records by clicking :guilabel:`Filters` and selecting one or several **preconfigured filters**." -msgstr "" - -#: ../../content/applications/essentials/search.rst:17 -msgid "On the Sales Analysis report, only records at the sales order stage are selected by default. However, you could *also* include records at the quotation stage by selecting :guilabel:`Quotations`. Furthermore, you could *only* include records from a specific year, for example *2022*, by selecting :menuselection:`Order Date --> 2022`." -msgstr "" - -#: ../../content/applications/essentials/search.rst:0 -msgid "Using preconfigured filters on the Sales Analysis report" -msgstr "" - -#: ../../content/applications/essentials/search.rst:27 -msgid "If you select preconfigured filters from the same group (i.e., that are *not* separated by an horizontal line), the records can match *any* condition to be included. However, if you select filters from different groups, the records have to match *all* condition to be included." -msgstr "" - -#: ../../content/applications/essentials/search.rst:34 -msgid "Custom filters" -msgstr "" - -#: ../../content/applications/essentials/search.rst:36 -msgid "You can create custom filters using most fields present on the model by clicking :menuselection:`Filters --> Add Custom Filter`, selecting a field, an operator, a value, and clicking :guilabel:`Apply`." -msgstr "" - -#: ../../content/applications/essentials/search.rst:41 -msgid "You could *only* include records from a single salesperson on the Sales Analysis report, for example *Mitchell Admin*, by selecting :guilabel:`Salesperson` as the field, :guilabel:`is equal to` as the operator, and typing `Mitchell Admin` as the value." -msgstr "" - -#: ../../content/applications/essentials/search.rst:0 -msgid "Using a custom filter on the Sales Analysis report" -msgstr "" - -#: ../../content/applications/essentials/search.rst:50 -msgid "If the records should *only* match one of several conditions, click :guilabel:`Add a condition` before applying a custom filter. If the records should match *all* conditions, add new custom filters instead." -msgstr "" - -#: ../../content/applications/essentials/search.rst:57 +#: ../../content/applications/essentials/search.rst:14 msgid "Search for values" msgstr "" -#: ../../content/applications/essentials/search.rst:59 -msgid "You can use the search field to quickly look for specific values and add them as a filter. Either type the full value you are searching for and select the desired field, or type a part of the value, click the dropdown button (:guilabel:`⏵`) before the chosen field, and select the exact value you are looking for." +#: ../../content/applications/essentials/search.rst:16 +msgid "Use the search field to quickly look for specific values, and add them as a filter. Type the value to search for, and select the desired option from the drop-down menu to apply the search filter." msgstr "" -#: ../../content/applications/essentials/search.rst:65 -msgid "Instead of adding a custom filter to select records where *Mitchell Admin* is the salesperson on the Sales Analysis report, you could search for `Mitch`, click the dropdown button (:guilabel:`⏵`) next to :guilabel:`Search Salesperson for: Mitch`, and select :guilabel:`Mitchell Admin`." +#: ../../content/applications/essentials/search.rst:20 +msgid "Instead of adding a :ref:`custom filter ` to select records where *Mitchell Admin* is the salesperson on the *Sales Analysis* report (:menuselection:`Sales app --> Reporting --> Sales`), search for `Mitch`, and click the :guilabel:`⏵ (right arrow)` next to :guilabel:`Search Salesperson for: Mitch`, and select :guilabel:`Mitchell Admin`." msgstr "" #: ../../content/applications/essentials/search.rst:0 msgid "Searching for a specific value on the Sales Analysis report" msgstr "" -#: ../../content/applications/essentials/search.rst:75 -msgid "Using the search field is equivalent to using the *contains* operator when adding a custom filter. If you enter a partial value and directly select the desired field, *all* records containing the characters you typed for the selected field will be included." +#: ../../content/applications/essentials/search.rst:30 +msgid "Using the search field is equivalent to using the *contains* operator when adding a :ref:`custom filter `. If a partial value is entered, and the desired field is directly selected (without selecting the :guilabel:`⏵ (right arrow)`), *all* records containing the typed characters for the selected field are included." msgstr "" -#: ../../content/applications/essentials/search.rst:82 -msgid "Group records" +#: ../../content/applications/essentials/search.rst:38 +msgid "Filters" +msgstr "" + +#: ../../content/applications/essentials/search.rst:40 +msgid "Filters are used to select records that meet specific criteria. The default selection of records is specific to each view, but can be modified by selecting one (or several) :ref:`preconfigured filters `, or by adding a :ref:`custom filter `." +msgstr "" + +#: ../../content/applications/essentials/search.rst:47 +msgid "Preconfigured filters" +msgstr "" + +#: ../../content/applications/essentials/search.rst:49 +msgid "Modify the default selection of records by clicking the :guilabel:`🔽 (down arrow)` icon from the search bar, and selecting one (or several) *preconfigured filters* from the :guilabel:`Filters` drop-down menu." +msgstr "" + +#: ../../content/applications/essentials/search.rst:54 +msgid "On the *Sales Analysis* report (:menuselection:`Sales app --> Reporting --> Sales`), only records that are at the *sales order* stage, with an *order date* within the last 365 days, are selected by default." +msgstr "" + +#: ../../content/applications/essentials/search.rst:58 +msgid "To also include records at the *quotation* stage, select :guilabel:`Quotations` from the :guilabel:`Filters`." +msgstr "" + +#: ../../content/applications/essentials/search.rst:61 +msgid "Furthermore, to *only* include sales order and quotation records from a specific year, like 2024, for example, first remove the existing `Order Date: Last 365 Days` filter, by clicking the :guilabel:`❌ (remove)` icon, then select :menuselection:`Order Date --> 2024`." +msgstr "" + +#: ../../content/applications/essentials/search.rst:0 +msgid "Using preconfigured filters on the Sales Analysis report" +msgstr "" + +#: ../../content/applications/essentials/search.rst:70 +msgid "The preconfigured :guilabel:`Filters` are grouped, and each group is separated by a horizontal line. Selecting preconfigured filters from the same group allows records to match *any* of the applied conditions. However, selecting filters from different groups requires records to match *all* of the applied conditions." +msgstr "" + +#: ../../content/applications/essentials/search.rst:78 +msgid "Custom filters" +msgstr "" + +#: ../../content/applications/essentials/search.rst:80 +msgid "If the :ref:`preconfigured filters ` are not specific enough, add a custom filter. To do so, click the :guilabel:`🔽 (down arrow)` icon in the search bar, then select :menuselection:`Filters --> Add Custom Filter`." msgstr "" #: ../../content/applications/essentials/search.rst:84 -msgid "You can click :guilabel:`Group By` below the search field to cluster records together according to one of the **preconfigured groups**." +msgid "The :guilabel:`Add Custom Filter` pop-up window displays the matching option, filter rule, and a toggle to :guilabel:`Include archived` records." msgstr "" -#: ../../content/applications/essentials/search.rst:88 -msgid "You could group the records by salesperson on the Sales Analysis report by clicking :guilabel:`Group By` and selecting :guilabel:`Salesperson`. No records are filtered out." +#: ../../content/applications/essentials/search.rst:-1 +msgid "The Add Custom Filter pop-up window." +msgstr "" + +#: ../../content/applications/essentials/search.rst:91 +msgid "The default matching configuration is to :guilabel:`Match any of the following rules`, indicating that each filter rule is applied independently. To change the matching configuration to :guilabel:`Match all of the following rules`, at least two filter rules must be added to the custom filter." +msgstr "" + +#: ../../content/applications/essentials/search.rst:96 +msgid ":guilabel:`Match all 🔽 of the following rules`: **all** of the filter rules must be met. Logically, this is an *AND* (`&`) operation." +msgstr "" + +#: ../../content/applications/essentials/search.rst:98 +msgid ":guilabel:`Match any 🔽 of the following rules`: **any** of the filter rules can be met. Logically, this is an *OR* (`|`) operation." +msgstr "" + +#: ../../content/applications/essentials/search.rst:101 +msgid "By default, a single filter rule is added to the custom filter. The following describes the structure of a filter rule:" +msgstr "" + +#: ../../content/applications/essentials/search.rst:104 +msgid "The first inline field is the *field name* to filter by. Some fields have refined parameters that are nested within another field. These fields have an :guilabel:`> (arrow)` icon beside them, which can be selected to reveal the nested fields." +msgstr "" + +#: ../../content/applications/essentials/search.rst:107 +msgid "The second inline field is the conditional *operator* used to compare the field name to the value. The :ref:`available conditional operators ` are specific to the field's data type." +msgstr "" + +#: ../../content/applications/essentials/search.rst:110 +msgid "The third inline field is the variable *value* of the field name. The value input may appear as a drop-down menu, a text input, a number input, a date/time input, a boolean selector, or it may be blank, depending on the operator used and the field's data type." +msgstr "" + +#: ../../content/applications/essentials/search.rst:114 +msgid "Three inline buttons are also available to the right of the rule's filter criteria:" +msgstr "" + +#: ../../content/applications/essentials/search.rst:116 +msgid ":guilabel:`➕ (plus sign)`: adds a new rule below the existing rule." +msgstr "" + +#: ../../content/applications/essentials/search.rst:117 +msgid ":guilabel:`(Add branch)`: adds a new group of rules below the existing rule, with the :guilabel:`any` and :guilabel:`all` matching options available to define how each rule within this branch is applied to the filter. If the matching option is set to the same as the parent group, the fields are moved to join the parent group." +msgstr "" + +#: ../../content/applications/essentials/search.rst:123 +msgid "If the matching option is set to :guilabel:`Match all 🔽 of the following rules`, and a new branch is added with its matching option changed from :guilabel:`any 🔽 of` to :guilabel:`all 🔽 of`, the newly-added branch disappears, and its group of rules are moved to the parent group." +msgstr "" + +#: ../../content/applications/essentials/search.rst:128 +msgid ":guilabel:`🗑️ (garbage can)`: deletes the node. If a branch node is deleted, all children of that node are deleted, as well." +msgstr "" + +#: ../../content/applications/essentials/search.rst:131 +msgid "A new filter rule can be added to the custom filter by clicking the :guilabel:`New Rule` button." +msgstr "" + +#: ../../content/applications/essentials/search.rst:133 +msgid "Once the filter criteria are defined, click :guilabel:`Add` to add the custom filter to the view." +msgstr "" + +#: ../../content/applications/essentials/search.rst:136 +msgid "To target all leads and opportunities from the :menuselection:`CRM` app that are in the *Won* stage, and have an expected revenue greater than $1,000, the following should be entered:" +msgstr "" + +#: ../../content/applications/essentials/search.rst:139 +msgid ":guilabel:`Match all 🔽 (down arrow) of the following rules:`" +msgstr "" + +#: ../../content/applications/essentials/search.rst:141 +msgid ":guilabel:`Stage` :guilabel:`is in` :guilabel:`Won`" +msgstr "" + +#: ../../content/applications/essentials/search.rst:142 +msgid ":guilabel:`Expected Revenue` :guilabel:`>` `1,000`" +msgstr "" + +#: ../../content/applications/essentials/search.rst:143 +msgid ":guilabel:`any 🔽 (down arrow)` :guilabel:`of:`" +msgstr "" + +#: ../../content/applications/essentials/search.rst:145 +msgid ":guilabel:`Type` :guilabel:`=` :guilabel:`Lead`" +msgstr "" + +#: ../../content/applications/essentials/search.rst:146 +msgid ":guilabel:`Type` :guilabel:`=` :guilabel:`Opportunity`" +msgstr "" + +#: ../../content/applications/essentials/search.rst:0 +msgid "Adding a custom filter to filter specific records in CRM." +msgstr "" + +#: ../../content/applications/essentials/search.rst:153 +msgid "Activate :ref:`developer-mode` to reveal each field's technical name and data type, as well as the :guilabel:`# Code editor` text area below the filter rules, to view and edit the domain manually." +msgstr "" + +#: ../../content/applications/essentials/search.rst:160 +msgid "Group records" +msgstr "" + +#: ../../content/applications/essentials/search.rst:162 +msgid "The display of records in a view can be clustered together, according to one of the *preconfigured groups*. To do so, click the :guilabel:`🔽 (down arrow)` icon in the search bar, then select one of the :guilabel:`Group By` options from the drop-down menu." +msgstr "" + +#: ../../content/applications/essentials/search.rst:167 +msgid "To group the records by salesperson on the *Sales Analysis* report (:menuselection:`Sales app --> Reporting --> Sales`), click the :guilabel:`Salesperson` option from the :guilabel:`Group By` drop-down menu. The view changes to group the records by salesperson, without filtering out any records." msgstr "" #: ../../content/applications/essentials/search.rst:0 msgid "Grouping records on the Sales Analysis report" msgstr "" -#: ../../content/applications/essentials/search.rst:95 -msgid "You can **customize groups** by using a wide selection of fields present on the model. To do so, click :menuselection:`Group By --> Add Custom Group`, select a field, and click :guilabel:`Apply`." +#: ../../content/applications/essentials/search.rst:176 +msgid "It is possible to *customize groups* by using a field present on the model. To do so, click :menuselection:`Add Custom Group`, and select a field from the drop-down menu." msgstr "" -#: ../../content/applications/essentials/search.rst:99 -msgid "You can use several groups at the same time. The first group you select is the main cluster, the next one you add further divides the main group's categories, and so on." +#: ../../content/applications/essentials/search.rst:180 +msgid "Several groups can be used at the same time. The first group that is selected is the main cluster, the next one that is added further divides the main group's categories, and so on. Furthermore, filters and groups can be used together to refine the view even more." +msgstr "" + +#: ../../content/applications/essentials/search.rst:187 +msgid "Favorites" +msgstr "" + +#: ../../content/applications/essentials/search.rst:189 +msgid "Favorites are a way to save a specific search for future use, or as the new default filter for the view." +msgstr "" + +#: ../../content/applications/essentials/search.rst:192 +msgid "To save the current view as a favorite, click the :guilabel:`🔽 (down arrow)` icon in the search bar, then select the :guilabel:`Save current search` drop-down menu to display the following options:" +msgstr "" + +#: ../../content/applications/essentials/search.rst:196 +msgid "Filter name: name of the favorited search." +msgstr "" + +#: ../../content/applications/essentials/search.rst:197 +msgid ":guilabel:`Default filter`: sets the favorited search as the default filter for the view." +msgstr "" + +#: ../../content/applications/essentials/search.rst:198 +msgid ":guilabel:`Shared`: makes the favorited search available to all users. By default, the favorited search is only available to the user who created it." +msgstr "" + +#: ../../content/applications/essentials/search.rst:201 +msgid "Once the options are set, click :guilabel:`Save` to save the favorited search." +msgstr "" + +#: ../../content/applications/essentials/search.rst:-1 +msgid "Saving a favorite search on the Sales Analysis report" +msgstr "" + +#: ../../content/applications/essentials/search.rst:207 +msgid "Saved favorites can be accessed by clicking the :guilabel:`🔽 (down arrow)` icon in the search bar, then selecting the saved filter in the :guilabel:`Favorites` drop-down menu. To remove a saved favorite, click the :guilabel:`🗑️ (garbage can)` icon next to the favorited search." +msgstr "" + +#: ../../content/applications/essentials/search.rst:212 +msgid "To view *all* favorited searches, first activate :ref:`developer-mode`, and navigate to :menuselection:`Settings app --> Technical --> User Interface: User-defined Filters`. From here, all favorited searches can be viewed, edited, archived, or deleted." msgstr "" diff --git a/locale/sources/finance.pot b/locale/sources/finance.pot index 97f262d1c..e59cbf543 100644 --- a/locale/sources/finance.pot +++ b/locale/sources/finance.pot @@ -8,7 +8,7 @@ msgid "" msgstr "" "Project-Id-Version: Odoo 17.0\n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2024-03-25 16:01+0000\n" +"POT-Creation-Date: 2024-04-30 09:16+0000\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME \n" "Language-Team: LANGUAGE \n" @@ -118,9 +118,9 @@ msgid "The **Partner Ledger** report displays the balance of your customers and msgstr "" #: ../../content/applications/finance/accounting.rst:127 -#: ../../content/applications/finance/accounting/customer_invoices/deferred_revenues.rst:78 +#: ../../content/applications/finance/accounting/customer_invoices/deferred_revenues.rst:79 #: ../../content/applications/finance/accounting/reporting.rst:5 -#: ../../content/applications/finance/accounting/vendor_bills/deferred_expenses.rst:78 +#: ../../content/applications/finance/accounting/vendor_bills/deferred_expenses.rst:79 msgid "Reporting" msgstr "" @@ -130,7 +130,7 @@ msgstr "" #: ../../content/applications/finance/accounting.rst:133 #: ../../content/applications/finance/fiscal_localizations/austria.rst:28 -#: ../../content/applications/finance/fiscal_localizations/chile.rst:1157 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:1206 #: ../../content/applications/finance/fiscal_localizations/colombia.rst:418 msgid "Financial reports" msgstr "" @@ -440,6 +440,7 @@ msgstr "" #: ../../content/applications/finance/fiscal_localizations.rst:21 #: ../../content/applications/finance/fiscal_localizations/argentina.rst:17 #: ../../content/applications/finance/fiscal_localizations/argentina.rst:894 +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:963 #: ../../content/applications/finance/fiscal_localizations/australia.rst:8 #: ../../content/applications/finance/fiscal_localizations/australia.rst:329 #: ../../content/applications/finance/fiscal_localizations/australia.rst:424 @@ -450,8 +451,11 @@ msgstr "" #: ../../content/applications/finance/fiscal_localizations/belgium.rst:256 #: ../../content/applications/finance/fiscal_localizations/belgium.rst:532 #: ../../content/applications/finance/fiscal_localizations/brazil.rst:28 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:764 #: ../../content/applications/finance/fiscal_localizations/colombia.rst:21 #: ../../content/applications/finance/fiscal_localizations/ecuador.rst:34 +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:583 +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:701 #: ../../content/applications/finance/fiscal_localizations/germany.rst:58 #: ../../content/applications/finance/fiscal_localizations/italy.rst:8 #: ../../content/applications/finance/fiscal_localizations/kenya.rst:8 @@ -1672,58 +1676,70 @@ msgid "Belgium: Coded Statement of Account (.CODA)." msgstr "" #: ../../content/applications/finance/accounting/bank/transactions.rst:30 -msgid "To import a file, go to the :guilabel:`Accounting Dashboard`, and in the :guilabel:`Bank` journal, click on :guilabel:`Import Transactions`." +msgid "To import a file, go to the **Accounting Dashboard**, and in the :guilabel:`Bank` journal, click on :guilabel:`Import File`." msgstr "" -#: ../../content/applications/finance/accounting/bank/transactions.rst:-1 -msgid "Import bank transactions from the bank journal" +#: ../../content/applications/finance/accounting/bank/transactions.rst:34 +msgid "Alternatively, you can also:" msgstr "" #: ../../content/applications/finance/accounting/bank/transactions.rst:36 +msgid "click :guilabel:`⋮` on the :guilabel:`Bank` journal and select :guilabel:`Import file`;" +msgstr "" + +#: ../../content/applications/finance/accounting/bank/transactions.rst:37 +msgid "or access the transaction list by clicking :guilabel:`⋮` on the :guilabel:`Bank` journal and selecting :guilabel:`Transactions`, then click the gear icon :guilabel:`(⚙)` and select :guilabel:`Import records`." +msgstr "" + +#: ../../content/applications/finance/accounting/bank/transactions.rst:0 +msgid "Import bank transactions from the bank journal" +msgstr "" + +#: ../../content/applications/finance/accounting/bank/transactions.rst:44 msgid "Next, select the file and upload it." msgstr "" -#: ../../content/applications/finance/accounting/bank/transactions.rst:38 +#: ../../content/applications/finance/accounting/bank/transactions.rst:46 msgid "After setting the necessary formatting options and mapping the file columns with their related Odoo fields, you can run a :guilabel:`Test` and :guilabel:`Import` your bank transactions." msgstr "" -#: ../../content/applications/finance/accounting/bank/transactions.rst:42 +#: ../../content/applications/finance/accounting/bank/transactions.rst:50 msgid ":doc:`/applications/essentials/export_import_data`" msgstr "" -#: ../../content/applications/finance/accounting/bank/transactions.rst:47 +#: ../../content/applications/finance/accounting/bank/transactions.rst:55 msgid "Register bank transactions manually" msgstr "" -#: ../../content/applications/finance/accounting/bank/transactions.rst:49 +#: ../../content/applications/finance/accounting/bank/transactions.rst:57 msgid "You can also record your bank transactions manually. To do so, go to :guilabel:`Accounting Dashboard`, click on the :guilabel:`Bank` journal, and then on :guilabel:`New`. Make sure to fill out the :guilabel:`Partner` and :guilabel:`Label` fields to ease the reconciliation process." msgstr "" -#: ../../content/applications/finance/accounting/bank/transactions.rst:56 +#: ../../content/applications/finance/accounting/bank/transactions.rst:64 msgid "Statements" msgstr "" -#: ../../content/applications/finance/accounting/bank/transactions.rst:58 +#: ../../content/applications/finance/accounting/bank/transactions.rst:66 msgid "A **bank statement** is a document provided by a bank or financial institution that lists the transactions that have occurred in a particular bank account over a specified period of time." msgstr "" -#: ../../content/applications/finance/accounting/bank/transactions.rst:61 +#: ../../content/applications/finance/accounting/bank/transactions.rst:69 msgid "In Odoo Accounting, it is optional to group transactions by their related statement, but depending on your business flow, you may want to record them for control purposes." msgstr "" -#: ../../content/applications/finance/accounting/bank/transactions.rst:65 +#: ../../content/applications/finance/accounting/bank/transactions.rst:73 msgid "If you want to compare the ending balances of your bank statements with the ending balances of your financial records, *don't forget to create an opening transaction* to record the bank account balance as of the date you begin synchronizing or importing transactions. This is necessary to ensure the accuracy of your accounting." msgstr "" -#: ../../content/applications/finance/accounting/bank/transactions.rst:70 +#: ../../content/applications/finance/accounting/bank/transactions.rst:78 msgid "To access a list of statements, go to your :guilabel:`Accounting Dashboard`, click on the vertical ellipsis (:guilabel:`⋮`) button next to the bank or cash journal you want to check, then on :guilabel:`Statements`" msgstr "" -#: ../../content/applications/finance/accounting/bank/transactions.rst:75 +#: ../../content/applications/finance/accounting/bank/transactions.rst:83 msgid "Statement creation from the kanban view" msgstr "" -#: ../../content/applications/finance/accounting/bank/transactions.rst:77 +#: ../../content/applications/finance/accounting/bank/transactions.rst:85 msgid "Open the bank reconciliation view by clicking on the name of the bank journal, and identify the transaction corresponding to the last transaction of your bank statement. Click on the :guilabel:`STATEMENT` button when hovering on the upper separator line." msgstr "" @@ -1731,22 +1747,22 @@ msgstr "" msgid "A \"STATEMENT\" button is visible when hovering on the line separating two transactions." msgstr "" -#: ../../content/applications/finance/accounting/bank/transactions.rst:84 +#: ../../content/applications/finance/accounting/bank/transactions.rst:92 msgid "Fill out the statement's details and save. The newly created statement includes the previous transactions following the last statement." msgstr "" -#: ../../content/applications/finance/accounting/bank/transactions.rst:88 +#: ../../content/applications/finance/accounting/bank/transactions.rst:96 msgid "Statement creation from the list view" msgstr "" -#: ../../content/applications/finance/accounting/bank/transactions.rst:90 +#: ../../content/applications/finance/accounting/bank/transactions.rst:98 msgid "Open the list of transactions by clicking on the name of the bank journal and switching to the list view. Select all the transactions corresponding to the bank statement, and, in the :guilabel:`Statement` column, select an existing statement or create a new one by typing its reference, clicking on :guilabel:`Create and edit...`, filling out the statement's details, and saving." msgstr "" #: ../../content/applications/finance/accounting/customer_invoices.rst:5 #: ../../content/applications/finance/accounting/payments/batch_sdd.rst:90 #: ../../content/applications/finance/fiscal_localizations/brazil.rst:352 -#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:346 +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:363 #: ../../content/applications/finance/fiscal_localizations/mexico.rst:321 msgid "Customer invoices" msgstr "" @@ -2617,31 +2633,31 @@ msgid "Generate deferral entries on validation" msgstr "" #: ../../content/applications/finance/accounting/customer_invoices/deferred_revenues.rst:56 -msgid "Make sure the :guilabel:`Start Date` and :guilabel:`End Date` fields are visible in the :guilabel:`Invoice Lines` tab. In most cases, the :guilabel:`Start Date` should be in the same month as the :guilabel:`Invoice Date`." +msgid "Make sure the :guilabel:`Start Date` and :guilabel:`End Date` fields are visible in the :guilabel:`Invoice Lines` tab. In most cases, the :guilabel:`Start Date` should be in the same month as the :guilabel:`Invoice Date`. Deferred revenue entries are posted from the invoice date and are displayed in the report accordingly." msgstr "" -#: ../../content/applications/finance/accounting/customer_invoices/deferred_revenues.rst:60 +#: ../../content/applications/finance/accounting/customer_invoices/deferred_revenues.rst:61 msgid "For each line of the invoice that should be deferred, specify the start and end dates of the deferral period." msgstr "" -#: ../../content/applications/finance/accounting/customer_invoices/deferred_revenues.rst:63 +#: ../../content/applications/finance/accounting/customer_invoices/deferred_revenues.rst:64 msgid "If the :guilabel:`Generate Entries` field in the **Settings** is set to :guilabel:`On invoice/bill validation`, Odoo automatically generates the deferral entries when the invoice is validated. Click the :guilabel:`Deferred Entries` smart button to see them." msgstr "" -#: ../../content/applications/finance/accounting/customer_invoices/deferred_revenues.rst:67 +#: ../../content/applications/finance/accounting/customer_invoices/deferred_revenues.rst:68 msgid "One entry, dated on the same day as the invoice's accounting date, moves the invoice amounts from the income account to the deferred account. The other entries are deferral entries which, month after month, move the invoice amounts from the deferred account to the income account to recognize the revenue." msgstr "" -#: ../../content/applications/finance/accounting/customer_invoices/deferred_revenues.rst:73 +#: ../../content/applications/finance/accounting/customer_invoices/deferred_revenues.rst:74 msgid "You can defer a January invoice of $1200 over 12 months by specifying a start date of 01/01/2023 and an end date of 12/31/2023. At the end of August, $800 is recognized as an income, whereas $400 remains on the deferred account." msgstr "" -#: ../../content/applications/finance/accounting/customer_invoices/deferred_revenues.rst:80 +#: ../../content/applications/finance/accounting/customer_invoices/deferred_revenues.rst:81 msgid "The deferred revenue report computes an overview of the necessary deferral entries for each account. To access it, go to :menuselection:`Accounting --> Reporting --> Deferred Revenue`." msgstr "" -#: ../../content/applications/finance/accounting/customer_invoices/deferred_revenues.rst:83 -#: ../../content/applications/finance/accounting/vendor_bills/deferred_expenses.rst:83 +#: ../../content/applications/finance/accounting/customer_invoices/deferred_revenues.rst:84 +#: ../../content/applications/finance/accounting/vendor_bills/deferred_expenses.rst:84 msgid "To view the journal items of each account, click on the account name and then :guilabel:`Journal Items`." msgstr "" @@ -2649,192 +2665,192 @@ msgstr "" msgid "Deferred revenue report" msgstr "" -#: ../../content/applications/finance/accounting/customer_invoices/deferred_revenues.rst:90 +#: ../../content/applications/finance/accounting/customer_invoices/deferred_revenues.rst:91 msgid "Only invoices whose accounting date is before the end of the period of the report are taken into account." msgstr "" -#: ../../content/applications/finance/accounting/customer_invoices/deferred_revenues.rst:96 -#: ../../content/applications/finance/accounting/vendor_bills/deferred_expenses.rst:96 +#: ../../content/applications/finance/accounting/customer_invoices/deferred_revenues.rst:97 +#: ../../content/applications/finance/accounting/vendor_bills/deferred_expenses.rst:97 msgid "Generate grouped deferral entries manually" msgstr "" -#: ../../content/applications/finance/accounting/customer_invoices/deferred_revenues.rst:98 -#: ../../content/applications/finance/accounting/vendor_bills/deferred_expenses.rst:98 +#: ../../content/applications/finance/accounting/customer_invoices/deferred_revenues.rst:99 +#: ../../content/applications/finance/accounting/vendor_bills/deferred_expenses.rst:99 msgid "If you have a lot of deferred revenues and wish to reduce the number of journal entries created, you can generate deferral entries manually. To do so, set the :guilabel:`Generate Entries` field in the **Settings** to :guilabel:`Manually & Grouped`. Odoo then aggregates the deferred amounts in a single entry." msgstr "" -#: ../../content/applications/finance/accounting/customer_invoices/deferred_revenues.rst:103 +#: ../../content/applications/finance/accounting/customer_invoices/deferred_revenues.rst:104 msgid "At the end of each month, go to :menuselection:`Accounting --> Reporting --> Deferred Revenue` and click the :guilabel:`Generate Entries` button. This generates two deferral entries:" msgstr "" -#: ../../content/applications/finance/accounting/customer_invoices/deferred_revenues.rst:106 +#: ../../content/applications/finance/accounting/customer_invoices/deferred_revenues.rst:107 msgid "One dated at the end of the month which aggregates, for each account, all the deferred amounts of that month. This means that a part of the deferred revenue is recognized at the end of that period." msgstr "" -#: ../../content/applications/finance/accounting/customer_invoices/deferred_revenues.rst:109 -#: ../../content/applications/finance/accounting/vendor_bills/deferred_expenses.rst:109 +#: ../../content/applications/finance/accounting/customer_invoices/deferred_revenues.rst:110 +#: ../../content/applications/finance/accounting/vendor_bills/deferred_expenses.rst:110 msgid "The reversal of this created entry, dated on the following day (i.e., the first day of the next month) to cancel the previous entry." msgstr "" -#: ../../content/applications/finance/accounting/customer_invoices/deferred_revenues.rst:113 +#: ../../content/applications/finance/accounting/customer_invoices/deferred_revenues.rst:114 msgid "There are two invoices:" msgstr "" -#: ../../content/applications/finance/accounting/customer_invoices/deferred_revenues.rst:115 +#: ../../content/applications/finance/accounting/customer_invoices/deferred_revenues.rst:116 msgid "Invoice A: $1200 to be deferred from 01/01/2023 to 12/31/2023" msgstr "" -#: ../../content/applications/finance/accounting/customer_invoices/deferred_revenues.rst:116 +#: ../../content/applications/finance/accounting/customer_invoices/deferred_revenues.rst:117 msgid "Invoice B: $600 to be deferred from 01/01/2023 to 12/31/2023" msgstr "" -#: ../../content/applications/finance/accounting/customer_invoices/deferred_revenues.rst:133 -#: ../../content/applications/finance/accounting/vendor_bills/deferred_expenses.rst:134 +#: ../../content/applications/finance/accounting/customer_invoices/deferred_revenues.rst:134 +#: ../../content/applications/finance/accounting/vendor_bills/deferred_expenses.rst:135 msgid "In January" msgstr "" -#: ../../content/applications/finance/accounting/customer_invoices/deferred_revenues.rst:119 -#: ../../content/applications/finance/accounting/vendor_bills/deferred_expenses.rst:120 +#: ../../content/applications/finance/accounting/customer_invoices/deferred_revenues.rst:120 +#: ../../content/applications/finance/accounting/vendor_bills/deferred_expenses.rst:121 msgid "At the end of January, after clicking the :guilabel:`Generate Entries` button, there are the following entries:" msgstr "" -#: ../../content/applications/finance/accounting/customer_invoices/deferred_revenues.rst:122 -#: ../../content/applications/finance/accounting/vendor_bills/deferred_expenses.rst:123 +#: ../../content/applications/finance/accounting/customer_invoices/deferred_revenues.rst:123 +#: ../../content/applications/finance/accounting/vendor_bills/deferred_expenses.rst:124 msgid "Entry 1 dated on the 31st January:" msgstr "" -#: ../../content/applications/finance/accounting/customer_invoices/deferred_revenues.rst:124 -#: ../../content/applications/finance/accounting/customer_invoices/deferred_revenues.rst:141 -#: ../../content/applications/finance/accounting/customer_invoices/deferred_revenues.rst:157 +#: ../../content/applications/finance/accounting/customer_invoices/deferred_revenues.rst:125 +#: ../../content/applications/finance/accounting/customer_invoices/deferred_revenues.rst:142 +#: ../../content/applications/finance/accounting/customer_invoices/deferred_revenues.rst:158 msgid "Line 1: Expense account -1200 -600 = **-1800** (cancelling the total of both invoices)" msgstr "" -#: ../../content/applications/finance/accounting/customer_invoices/deferred_revenues.rst:125 +#: ../../content/applications/finance/accounting/customer_invoices/deferred_revenues.rst:126 msgid "Line 2: Expense account 100 + 50 = **150** (recognizing 1/12 of invoice A and invoice B)" msgstr "" -#: ../../content/applications/finance/accounting/customer_invoices/deferred_revenues.rst:126 -#: ../../content/applications/finance/accounting/vendor_bills/deferred_expenses.rst:127 +#: ../../content/applications/finance/accounting/customer_invoices/deferred_revenues.rst:127 +#: ../../content/applications/finance/accounting/vendor_bills/deferred_expenses.rst:128 msgid "Line 3: Deferred account 1800 - 150 = **1650** (amount that has yet to be deferred later on)" msgstr "" -#: ../../content/applications/finance/accounting/customer_invoices/deferred_revenues.rst:129 -#: ../../content/applications/finance/accounting/vendor_bills/deferred_expenses.rst:130 +#: ../../content/applications/finance/accounting/customer_invoices/deferred_revenues.rst:130 +#: ../../content/applications/finance/accounting/vendor_bills/deferred_expenses.rst:131 msgid "Entry 2 dated on the 1st February, the reversal of the previous entry:" msgstr "" -#: ../../content/applications/finance/accounting/customer_invoices/deferred_revenues.rst:131 -#: ../../content/applications/finance/accounting/vendor_bills/deferred_expenses.rst:132 -msgid "Line 1: Expense account **1800**" -msgstr "" - #: ../../content/applications/finance/accounting/customer_invoices/deferred_revenues.rst:132 #: ../../content/applications/finance/accounting/vendor_bills/deferred_expenses.rst:133 -msgid "Line 2: Deferred account **-150**" +msgid "Line 1: Expense account **1800**" msgstr "" #: ../../content/applications/finance/accounting/customer_invoices/deferred_revenues.rst:133 #: ../../content/applications/finance/accounting/vendor_bills/deferred_expenses.rst:134 +msgid "Line 2: Deferred account **-150**" +msgstr "" + +#: ../../content/applications/finance/accounting/customer_invoices/deferred_revenues.rst:134 +#: ../../content/applications/finance/accounting/vendor_bills/deferred_expenses.rst:135 msgid "Line 3: Expense account **-1650**" msgstr "" -#: ../../content/applications/finance/accounting/customer_invoices/deferred_revenues.rst:146 -#: ../../content/applications/finance/accounting/vendor_bills/deferred_expenses.rst:147 +#: ../../content/applications/finance/accounting/customer_invoices/deferred_revenues.rst:147 +#: ../../content/applications/finance/accounting/vendor_bills/deferred_expenses.rst:148 msgid "In February" msgstr "" -#: ../../content/applications/finance/accounting/customer_invoices/deferred_revenues.rst:136 -#: ../../content/applications/finance/accounting/vendor_bills/deferred_expenses.rst:137 +#: ../../content/applications/finance/accounting/customer_invoices/deferred_revenues.rst:137 +#: ../../content/applications/finance/accounting/vendor_bills/deferred_expenses.rst:138 msgid "At the end of February, after clicking the :guilabel:`Generate Entries` button, there are the following entries:" msgstr "" -#: ../../content/applications/finance/accounting/customer_invoices/deferred_revenues.rst:139 -#: ../../content/applications/finance/accounting/vendor_bills/deferred_expenses.rst:140 +#: ../../content/applications/finance/accounting/customer_invoices/deferred_revenues.rst:140 +#: ../../content/applications/finance/accounting/vendor_bills/deferred_expenses.rst:141 msgid "Entry 1 dated on the 28th February:" msgstr "" -#: ../../content/applications/finance/accounting/customer_invoices/deferred_revenues.rst:142 +#: ../../content/applications/finance/accounting/customer_invoices/deferred_revenues.rst:143 msgid "Line 2: Expense account 200 + 100 = **300** (recognizing 2/12 of invoice A and invoice B)" msgstr "" -#: ../../content/applications/finance/accounting/customer_invoices/deferred_revenues.rst:143 -#: ../../content/applications/finance/accounting/vendor_bills/deferred_expenses.rst:144 +#: ../../content/applications/finance/accounting/customer_invoices/deferred_revenues.rst:144 +#: ../../content/applications/finance/accounting/vendor_bills/deferred_expenses.rst:145 msgid "Line 3: Deferred account 1800 - 300 = **1500** (amount that has yet to be deferred later on)" msgstr "" -#: ../../content/applications/finance/accounting/customer_invoices/deferred_revenues.rst:146 -#: ../../content/applications/finance/accounting/vendor_bills/deferred_expenses.rst:147 +#: ../../content/applications/finance/accounting/customer_invoices/deferred_revenues.rst:147 +#: ../../content/applications/finance/accounting/vendor_bills/deferred_expenses.rst:148 msgid "Entry 2 dated on the 1st March, the reversal of the previous entry." msgstr "" -#: ../../content/applications/finance/accounting/customer_invoices/deferred_revenues.rst:149 -#: ../../content/applications/finance/accounting/vendor_bills/deferred_expenses.rst:150 +#: ../../content/applications/finance/accounting/customer_invoices/deferred_revenues.rst:150 +#: ../../content/applications/finance/accounting/vendor_bills/deferred_expenses.rst:151 msgid "From March to October" msgstr "" -#: ../../content/applications/finance/accounting/customer_invoices/deferred_revenues.rst:149 -#: ../../content/applications/finance/accounting/vendor_bills/deferred_expenses.rst:150 +#: ../../content/applications/finance/accounting/customer_invoices/deferred_revenues.rst:150 +#: ../../content/applications/finance/accounting/vendor_bills/deferred_expenses.rst:151 msgid "The same computation is done for each month until October." msgstr "" -#: ../../content/applications/finance/accounting/customer_invoices/deferred_revenues.rst:163 -#: ../../content/applications/finance/accounting/vendor_bills/deferred_expenses.rst:163 +#: ../../content/applications/finance/accounting/customer_invoices/deferred_revenues.rst:164 +#: ../../content/applications/finance/accounting/vendor_bills/deferred_expenses.rst:164 msgid "In November" msgstr "" -#: ../../content/applications/finance/accounting/customer_invoices/deferred_revenues.rst:152 -#: ../../content/applications/finance/accounting/vendor_bills/deferred_expenses.rst:153 +#: ../../content/applications/finance/accounting/customer_invoices/deferred_revenues.rst:153 +#: ../../content/applications/finance/accounting/vendor_bills/deferred_expenses.rst:154 msgid "At the end of November, after clicking the :guilabel:`Generate Entries` button, there are the following entries:" msgstr "" -#: ../../content/applications/finance/accounting/customer_invoices/deferred_revenues.rst:155 -#: ../../content/applications/finance/accounting/vendor_bills/deferred_expenses.rst:156 +#: ../../content/applications/finance/accounting/customer_invoices/deferred_revenues.rst:156 +#: ../../content/applications/finance/accounting/vendor_bills/deferred_expenses.rst:157 msgid "Entry 1 dated on the 30th November:" msgstr "" -#: ../../content/applications/finance/accounting/customer_invoices/deferred_revenues.rst:158 +#: ../../content/applications/finance/accounting/customer_invoices/deferred_revenues.rst:159 msgid "Line 2: Expense account 1100 + 550 = **1650** (recognizing 11/12 of invoice A and invoice B)" msgstr "" -#: ../../content/applications/finance/accounting/customer_invoices/deferred_revenues.rst:160 -#: ../../content/applications/finance/accounting/vendor_bills/deferred_expenses.rst:160 +#: ../../content/applications/finance/accounting/customer_invoices/deferred_revenues.rst:161 +#: ../../content/applications/finance/accounting/vendor_bills/deferred_expenses.rst:161 msgid "Line 3: Deferred account 1800 - 1650 = **150** (amount that has yet to be deferred later on)" msgstr "" -#: ../../content/applications/finance/accounting/customer_invoices/deferred_revenues.rst:163 -#: ../../content/applications/finance/accounting/vendor_bills/deferred_expenses.rst:163 +#: ../../content/applications/finance/accounting/customer_invoices/deferred_revenues.rst:164 +#: ../../content/applications/finance/accounting/vendor_bills/deferred_expenses.rst:164 msgid "Entry 2 dated on the 1st December, the reversal of the previous entry." msgstr "" -#: ../../content/applications/finance/accounting/customer_invoices/deferred_revenues.rst:167 -#: ../../content/applications/finance/accounting/vendor_bills/deferred_expenses.rst:167 +#: ../../content/applications/finance/accounting/customer_invoices/deferred_revenues.rst:168 +#: ../../content/applications/finance/accounting/vendor_bills/deferred_expenses.rst:168 msgid "In December" msgstr "" -#: ../../content/applications/finance/accounting/customer_invoices/deferred_revenues.rst:166 +#: ../../content/applications/finance/accounting/customer_invoices/deferred_revenues.rst:167 msgid "There is no need to generate entries in December. Indeed, if we do the computation for December, we have an amount of 0 to be deferred." msgstr "" -#: ../../content/applications/finance/accounting/customer_invoices/deferred_revenues.rst:176 -#: ../../content/applications/finance/accounting/vendor_bills/deferred_expenses.rst:176 +#: ../../content/applications/finance/accounting/customer_invoices/deferred_revenues.rst:177 +#: ../../content/applications/finance/accounting/vendor_bills/deferred_expenses.rst:177 msgid "In total" msgstr "" -#: ../../content/applications/finance/accounting/customer_invoices/deferred_revenues.rst:170 -#: ../../content/applications/finance/accounting/vendor_bills/deferred_expenses.rst:170 +#: ../../content/applications/finance/accounting/customer_invoices/deferred_revenues.rst:171 +#: ../../content/applications/finance/accounting/vendor_bills/deferred_expenses.rst:171 msgid "If we aggregate everything, we would have:" msgstr "" -#: ../../content/applications/finance/accounting/customer_invoices/deferred_revenues.rst:172 +#: ../../content/applications/finance/accounting/customer_invoices/deferred_revenues.rst:173 msgid "invoice A and invoice B" msgstr "" -#: ../../content/applications/finance/accounting/customer_invoices/deferred_revenues.rst:173 -#: ../../content/applications/finance/accounting/vendor_bills/deferred_expenses.rst:173 +#: ../../content/applications/finance/accounting/customer_invoices/deferred_revenues.rst:174 +#: ../../content/applications/finance/accounting/vendor_bills/deferred_expenses.rst:174 msgid "two entries (one for the deferral and one for the reversal) for each month from January to November" msgstr "" -#: ../../content/applications/finance/accounting/customer_invoices/deferred_revenues.rst:176 +#: ../../content/applications/finance/accounting/customer_invoices/deferred_revenues.rst:177 msgid "Therefore, at the end of December, invoices A and B are fully recognized as income only once in spite of all the created entries thanks to the reversal mechanism." msgstr "" @@ -3948,7 +3964,7 @@ msgid "A square of **15mm by 15mm** on the bottom left corner has to stay clear. msgstr "" #: ../../content/applications/finance/accounting/customer_invoices/snailmail.rst:39 -msgid "The postage area has to stay clear (click :download:`here ` to get more info about the area)." +msgid "The postage area has to stay clear (:download:`download the snailmail PDF template ` for more details)." msgstr "" #: ../../content/applications/finance/accounting/customer_invoices/snailmail.rst:41 @@ -3969,12 +3985,7 @@ msgid "To buy stamps, go to :menuselection:`Accounting --> Configuration --> Set msgstr "" #: ../../content/applications/finance/accounting/customer_invoices/snailmail.rst:55 -#: ../../content/applications/finance/accounting/vendor_bills/invoice_digitization.rst:95 -msgid "If you are on Odoo Online and have the Enterprise version, you benefit from free trial credits to test the feature." -msgstr "" - -#: ../../content/applications/finance/accounting/customer_invoices/snailmail.rst:57 -msgid "Click `here `_ to know about our *Privacy Policy*." +msgid "`Odoo's IAP Privacy Policy `_" msgstr "" #: ../../content/applications/finance/accounting/customer_invoices/terms_conditions.rst:3 @@ -4984,7 +4995,7 @@ msgstr "" #: ../../content/applications/finance/fiscal_localizations/brazil.rst:146 #: ../../content/applications/finance/fiscal_localizations/chile.rst:361 #: ../../content/applications/finance/fiscal_localizations/colombia.rst:247 -#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:241 +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:258 #: ../../content/applications/finance/fiscal_localizations/mexico.rst:1011 #: ../../content/applications/finance/fiscal_localizations/romania.rst:65 #: ../../content/applications/finance/fiscal_localizations/spain.rst:24 @@ -9217,6 +9228,7 @@ msgid "but we want to sell it at 10€, tax included, in our shops or eCommerce msgstr "" #: ../../content/applications/finance/accounting/taxes/B2B_B2C.rst:99 +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:573 msgid "eCommerce" msgstr "" @@ -9548,7 +9560,7 @@ msgid "The :abbr:`OSS (One-Stop Shop)` system introduced by the European Union s msgstr "" #: ../../content/applications/finance/accounting/taxes/eu_distance_selling.rst:52 -#: ../../content/applications/finance/fiscal_localizations/argentina.rst:952 +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:1019 #: ../../content/applications/finance/fiscal_localizations/belgium.rst:85 #: ../../content/applications/finance/fiscal_localizations/spain.rst:42 msgid "Reports" @@ -9695,7 +9707,6 @@ msgid ":doc:`B2B_B2C`" msgstr "" #: ../../content/applications/finance/accounting/taxes/retention.rst:3 -#: ../../content/applications/finance/fiscal_localizations/philippines.rst:28 msgid "Withholding taxes" msgstr "" @@ -9795,6 +9806,7 @@ msgstr "" #: ../../content/applications/finance/fiscal_localizations/argentina.rst:592 #: ../../content/applications/finance/fiscal_localizations/brazil.rst:463 #: ../../content/applications/finance/fiscal_localizations/chile.rst:700 +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:710 #: ../../content/applications/finance/fiscal_localizations/italy.rst:119 msgid "Vendor bills" msgstr "" @@ -10272,26 +10284,26 @@ msgid "Suppose a bill of $1200 must be deferred over 12 months. The :guilabel:`E msgstr "" #: ../../content/applications/finance/accounting/vendor_bills/deferred_expenses.rst:56 -msgid "Make sure the :guilabel:`Start Date` and :guilabel:`End Date` fields are visible in the :guilabel:`Invoice Lines` tab. In most cases, the :guilabel:`Start Date` should be in the same month as the :guilabel:`Bill Date`." +msgid "Make sure the :guilabel:`Start Date` and :guilabel:`End Date` fields are visible in the :guilabel:`Invoice Lines` tab. In most cases, the :guilabel:`Start Date` should be in the same month as the :guilabel:`Bill Date`. Deferred expense entries are posted from the bill date and are displayed in the report accordingly." msgstr "" -#: ../../content/applications/finance/accounting/vendor_bills/deferred_expenses.rst:60 +#: ../../content/applications/finance/accounting/vendor_bills/deferred_expenses.rst:61 msgid "For each line of the bill that should be deferred, specify the start and end dates of the deferral period." msgstr "" -#: ../../content/applications/finance/accounting/vendor_bills/deferred_expenses.rst:63 +#: ../../content/applications/finance/accounting/vendor_bills/deferred_expenses.rst:64 msgid "If the :guilabel:`Generate Entries` field is set to :guilabel:`On invoice/bill validation`, Odoo automatically generates the deferral entries when the bill is validated. Click on the :guilabel:`Deferred Entries` smart button to see them." msgstr "" -#: ../../content/applications/finance/accounting/vendor_bills/deferred_expenses.rst:67 +#: ../../content/applications/finance/accounting/vendor_bills/deferred_expenses.rst:68 msgid "One entry, dated on the same day as the bill's accounting date, moves the bill amounts from the expense account to the deferred account. The other entries are deferral entries which will, month after month, move the bill amounts from the deferred account to the expense account to recognize the expense." msgstr "" -#: ../../content/applications/finance/accounting/vendor_bills/deferred_expenses.rst:73 +#: ../../content/applications/finance/accounting/vendor_bills/deferred_expenses.rst:74 msgid "You can defer a January bill of $1200 over 12 months by specifying a start date of 01/01/2023 and an end date of 12/31/2023. At the end of August, $800 is recognized as an expense, whereas $400 remains on the deferred account." msgstr "" -#: ../../content/applications/finance/accounting/vendor_bills/deferred_expenses.rst:80 +#: ../../content/applications/finance/accounting/vendor_bills/deferred_expenses.rst:81 msgid "The deferred expense report computes an overview of the necessary deferral entries for each account. To access it, go to :menuselection:`Accounting --> Reporting --> Deferred Expense`." msgstr "" @@ -10299,57 +10311,57 @@ msgstr "" msgid "Deferred expense report" msgstr "" -#: ../../content/applications/finance/accounting/vendor_bills/deferred_expenses.rst:90 +#: ../../content/applications/finance/accounting/vendor_bills/deferred_expenses.rst:91 msgid "Only bills whose accounting date is before the end of the period of the report are taken into account." msgstr "" -#: ../../content/applications/finance/accounting/vendor_bills/deferred_expenses.rst:103 +#: ../../content/applications/finance/accounting/vendor_bills/deferred_expenses.rst:104 msgid "At the end of each month, go to the Deferred Expenses report and click the :guilabel:`Generate Entries` button. This generates two deferral entries:" msgstr "" -#: ../../content/applications/finance/accounting/vendor_bills/deferred_expenses.rst:106 +#: ../../content/applications/finance/accounting/vendor_bills/deferred_expenses.rst:107 msgid "One dated at the end of the month which aggregates, for each account, all the deferred amounts of that month. This means that at the end of that period, a part of the deferred expense is recognized." msgstr "" -#: ../../content/applications/finance/accounting/vendor_bills/deferred_expenses.rst:114 +#: ../../content/applications/finance/accounting/vendor_bills/deferred_expenses.rst:115 msgid "There are two bills:" msgstr "" -#: ../../content/applications/finance/accounting/vendor_bills/deferred_expenses.rst:116 +#: ../../content/applications/finance/accounting/vendor_bills/deferred_expenses.rst:117 msgid "Bill A: $1200 to be deferred from 01/01/2023 to 12/31/2023" msgstr "" -#: ../../content/applications/finance/accounting/vendor_bills/deferred_expenses.rst:117 +#: ../../content/applications/finance/accounting/vendor_bills/deferred_expenses.rst:118 msgid "Bill B: $600 to be deferred from 01/01/2023 to 12/31/2023" msgstr "" -#: ../../content/applications/finance/accounting/vendor_bills/deferred_expenses.rst:125 -#: ../../content/applications/finance/accounting/vendor_bills/deferred_expenses.rst:142 -#: ../../content/applications/finance/accounting/vendor_bills/deferred_expenses.rst:158 +#: ../../content/applications/finance/accounting/vendor_bills/deferred_expenses.rst:126 +#: ../../content/applications/finance/accounting/vendor_bills/deferred_expenses.rst:143 +#: ../../content/applications/finance/accounting/vendor_bills/deferred_expenses.rst:159 msgid "Line 1: Expense account -1200 -600 = **-1800** (cancelling the total of both bills)" msgstr "" -#: ../../content/applications/finance/accounting/vendor_bills/deferred_expenses.rst:126 +#: ../../content/applications/finance/accounting/vendor_bills/deferred_expenses.rst:127 msgid "Line 2: Expense account 100 + 50 = **150** (recognizing 1/12 of bill A and bill B)" msgstr "" -#: ../../content/applications/finance/accounting/vendor_bills/deferred_expenses.rst:143 +#: ../../content/applications/finance/accounting/vendor_bills/deferred_expenses.rst:144 msgid "Line 2: Expense account 200 + 100 = **300** (recognizing 2/12 of bill A and bill B)" msgstr "" -#: ../../content/applications/finance/accounting/vendor_bills/deferred_expenses.rst:159 +#: ../../content/applications/finance/accounting/vendor_bills/deferred_expenses.rst:160 msgid "Line 2: Expense account 1100 + 550 = **1650** (recognizing 11/12 of bill A and bill B)" msgstr "" -#: ../../content/applications/finance/accounting/vendor_bills/deferred_expenses.rst:166 +#: ../../content/applications/finance/accounting/vendor_bills/deferred_expenses.rst:167 msgid "There is no need to generate entries in December. Indeed, if we do the computation for December, we will have an amount of 0 to be deferred." msgstr "" -#: ../../content/applications/finance/accounting/vendor_bills/deferred_expenses.rst:172 +#: ../../content/applications/finance/accounting/vendor_bills/deferred_expenses.rst:173 msgid "bill A and bill B" msgstr "" -#: ../../content/applications/finance/accounting/vendor_bills/deferred_expenses.rst:176 +#: ../../content/applications/finance/accounting/vendor_bills/deferred_expenses.rst:177 msgid "Therefore, at the end of December, bills A and B are fully recognized as expense only once in spite of all the created entries thanks to the reversal mechanism." msgstr "" @@ -10449,6 +10461,10 @@ msgstr "" msgid "To buy credits, go to :menuselection:`Accounting --> Configuration --> Settings --> Digitization` and click on :guilabel:`Buy credits`, or go to :menuselection:`Settings --> Odoo IAP` and click on :guilabel:`View My Services`." msgstr "" +#: ../../content/applications/finance/accounting/vendor_bills/invoice_digitization.rst:95 +msgid "If you are on Odoo Online and have the Enterprise version, you benefit from free trial credits to test the feature." +msgstr "" + #: ../../content/applications/finance/accounting/vendor_bills/invoice_digitization.rst:99 msgid "`Our Privacy Policy `_" msgstr "" @@ -11603,7 +11619,7 @@ msgstr "" #: ../../content/applications/finance/fiscal_localizations/argentina.rst:52 #: ../../content/applications/finance/fiscal_localizations/brazil.rst:37 -#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:70 +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:87 #: ../../content/applications/finance/fiscal_localizations/mexico.rst:137 #: ../../content/applications/finance/fiscal_localizations/peru.rst:52 msgid "Configure your company" @@ -11644,7 +11660,7 @@ msgstr "" #: ../../content/applications/finance/fiscal_localizations/argentina.rst:79 #: ../../content/applications/finance/fiscal_localizations/brazil.rst:143 -#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:238 +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:255 msgid "Configure master data" msgstr "" @@ -12731,7 +12747,7 @@ msgstr "" #: ../../content/applications/finance/fiscal_localizations/argentina.rst:923 #: ../../content/applications/finance/fiscal_localizations/brazil.rst:212 #: ../../content/applications/finance/fiscal_localizations/colombia.rst:181 -#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:253 +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:270 #: ../../content/applications/finance/fiscal_localizations/egypt.rst:172 #: ../../content/applications/finance/fiscal_localizations/mexico.rst:251 #: ../../content/applications/finance/fiscal_localizations/mexico.rst:703 @@ -12768,7 +12784,92 @@ msgstr "" msgid ":doc:`Client account creation <../../websites/ecommerce/checkout_payment_shipping/checkout>`" msgstr "" +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:952 +msgid "Liquidity product direct sales" +msgstr "" + #: ../../content/applications/finance/fiscal_localizations/argentina.rst:954 +msgid "Liquidity product direct sales are used for sales involving third parties. For such sales, the seller and the proprietary company of the goods can each register their corresponding sales and purchases." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:959 +msgid ":ref:`Install ` the *Argentinian Electronic Invoicing* module (`l10n_ar_edi`) to use this feature." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:966 +msgid "Purchase journal" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:968 +msgid "A purchase journal is needed to generate an electronic vendor bill with a document type *Liquidity Product*. This journal needs to be synchronized with the AFIP as it will be used to generate the liquidity product electronic document." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:972 +msgid "To modify the existing purchase journal or create a new one, navigate to :menuselection:`Accounting --> Configuration --> Journals`. Then, select the existing purchase journal or click the :guilabel:`New` button, and fill in the following required information:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:976 +msgid ":guilabel:`Type`: select :guilabel:`Purchase`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:977 +msgid ":guilabel:`Use Documents`: check this field to to be able select the electronic document type." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:978 +msgid ":guilabel:`Is AFIP POS`: check this field to be able to generate electronic documents." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:979 +msgid ":guilabel:`AFIP POS System`: select :guilabel:`Electronic Invoice - Web Service` from the drop-down menu in order to send the electronic document to AFIP via web service." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:981 +msgid ":guilabel:`AFIP POS Number`: is the number configured in the AFIP to identify the operations related to this AFIP POS." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:983 +msgid ":guilabel:`AFIP POS Address`: is the field related to the commercial address registered for the POS, which is usually the same address as the company. For example, if a company has multiple stores (fiscal locations) then the AFIP will require the company to have one AFIP POS per location. This location will be printed in the invoice report." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:-1 +msgid "l10n_ar Purchase Journal Configuration." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:993 +msgid "Sales journal" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:995 +msgid "A sales journal is needed to register the invoice when a product is sold to a third party that will then sell the same product. This journal will not be synced with AFIP as the invoice will not be electronic." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:999 +msgid "To modify the existing sales journal or create a new one, navigate to :menuselection:`Accounting --> Configuration --> Journals`. Then, selecting the sales journal or click the :guilabel:`New` button, and fill in the following required information:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:1003 +msgid ":guilabel:`Type`: select :guilabel:`Sales`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:1004 +msgid ":guilabel:`Use Documents`: check this field on the journal to select the electronic document type (in this case the electronic invoice)." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:-1 +msgid "l10n_ar Sales Journal Configuration." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:1012 +#: ../../content/applications/finance/fiscal_localizations/mexico.rst:725 +msgid "Invoicing flow" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:1014 +msgid "Once the configurations are all set, the *Liquidity Product Vendor Bill* will be generated by the company that is selling the product on behalf of another party. For example, a distributor of a specific product." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:1021 msgid "As part of the localization installation, financial reporting for Argentina was added to the :guilabel:`Accounting` dashboard. Access these reports by navigating to :menuselection:`Accounting --> Reporting --> Argentinean Reports`" msgstr "" @@ -12776,72 +12877,68 @@ msgstr "" msgid "Argentinean reports." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/argentina.rst:963 +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:1030 msgid "VAT reports" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/argentina.rst:966 +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:1033 msgid "Sales VAT book" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/argentina.rst:968 -msgid "In this report, all the sales are recorded, which are taken as the basis for the accounting records to determine the VAT (Tax Debit)." -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/argentina.rst:971 -msgid "The :guilabel:`Sales VAT` book report can be exported in a `.zip` file :guilabel:`VAT BOOK (ZIP)` button in the top left, which contains `.txt` files to upload in the AFIP portal." +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:1035 +msgid "This report records all the sales, which are taken as the basis for the accounting records to determine the VAT (Tax Debit). The :guilabel:`Sales VAT` book report can be exported as a `.zip` file using the :guilabel:`VAT BOOK (ZIP)` button at the top left, containing `.txt` files to upload to the AFIP portal." msgstr "" #: ../../content/applications/finance/fiscal_localizations/argentina.rst:-1 msgid "Sales VAT book." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/argentina.rst:979 +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:1045 msgid "Purchases VAT book" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/argentina.rst:981 -msgid "The :guilabel:`Purchases VAT` book report can be exported in a `.zip` file :guilabel:`VAT BOOK (ZIP)` button in the top left, which contains `.txt` files to upload in the AFIP portal." +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:1047 +msgid "The :guilabel:`Purchases VAT` book report can be exported as a `.zip` file using the :guilabel:`VAT BOOK (ZIP)` button at the top left, which contains `.txt` files to upload to the AFIP portal." msgstr "" #: ../../content/applications/finance/fiscal_localizations/argentina.rst:-1 msgid "Purchases VAT book." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/argentina.rst:989 +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:1056 msgid "VAT summary" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/argentina.rst:991 -msgid "Pivot table designed to check the monthly VAT totals. This report is for internal usage, it is not sent to the AFIP." +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:1058 +msgid "Pivot table designed to check the monthly VAT totals. This report is for internal use and is not sent to the AFIP." msgstr "" #: ../../content/applications/finance/fiscal_localizations/argentina.rst:-1 msgid "VAT Summary." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/argentina.rst:999 +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:1066 msgid "IIBB - Reports" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/argentina.rst:1002 +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:1069 msgid "IIBB - Sales by jurisdiction" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/argentina.rst:1004 -msgid "Pivot table where you can validate the gross income in each jurisdiction. Affidavit for the corresponding taxes to pay, therefore it is not sent to the AFIP." +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:1071 +msgid "Pivot table where you can validate the gross income in each jurisdiction. Affidavit for the corresponding taxes to pay; and therefore, it is not sent to the AFIP." msgstr "" #: ../../content/applications/finance/fiscal_localizations/argentina.rst:-1 msgid "IIBB Sales by jurisdiction." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/argentina.rst:1012 +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:1079 msgid "IIBB - Purchases by jurisdiction" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/argentina.rst:1014 -msgid "Pivot table where you can validate the gross purchases in each jurisdiction. Affidavit for the corresponding taxes to pay, therefore it is not sent to the AFIP." +#: ../../content/applications/finance/fiscal_localizations/argentina.rst:1081 +msgid "Pivot table where you can validate the gross purchases in each jurisdiction. Affidavit for the corresponding taxes to pay; and therefore, it is not sent to the AFIP." msgstr "" #: ../../content/applications/finance/fiscal_localizations/argentina.rst:-1 @@ -14251,8 +14348,8 @@ msgid ":guilabel:`Country`" msgstr "" #: ../../content/applications/finance/fiscal_localizations/austria.rst:64 -#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:82 -#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:275 +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:99 +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:292 msgid ":guilabel:`Phone`" msgstr "" @@ -14803,7 +14900,7 @@ msgid "Odoo supports the **Peppol BIS Billing 3.0 (UBL)** electronic invoicing f msgstr "" #: ../../content/applications/finance/fiscal_localizations/belgium.rst:415 -#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:183 +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:200 msgid ":doc:`../accounting/customer_invoices/electronic_invoicing`" msgstr "" @@ -14848,7 +14945,7 @@ msgid "The Odoo POS system is certified for the major versions of databases host msgstr "" #: ../../content/applications/finance/fiscal_localizations/belgium.rst:461 -#: ../../content/applications/finance/payment_providers/stripe.rst:14 +#: ../../content/applications/finance/payment_providers/stripe.rst:18 msgid "Odoo Online" msgstr "" @@ -14959,7 +15056,7 @@ msgid "An FDM, or **black box**, is a government-certified device that works tog msgstr "" #: ../../content/applications/finance/fiscal_localizations/belgium.rst:526 -msgid "Only the FDM from **Boîtenoire.be** with the `FDM certificate number BMC01 `_ is supported by Odoo. `Contact the manufacturer (GCV BMC) `_ to order one." +msgid "Only the FDM from **Boîtenoire.be** with the `FDM certificate number BMC04 `_ is supported by Odoo. `Contact the manufacturer (GCV BMC) `_ to order one." msgstr "" #: ../../content/applications/finance/fiscal_localizations/belgium.rst:534 @@ -14967,7 +15064,7 @@ msgid "Before setting up your database to work with an FDM, ensure you have the msgstr "" #: ../../content/applications/finance/fiscal_localizations/belgium.rst:536 -msgid "a **Boîtenoire.be** (certificate number BMC01) FDM;" +msgid "a **Boîtenoire.be** (certificate number BMC04) FDM;" msgstr "" #: ../../content/applications/finance/fiscal_localizations/belgium.rst:537 @@ -15254,7 +15351,7 @@ msgid "The chart of accounts for Brazil is based on the SPED CoA, which gives a msgstr "" #: ../../content/applications/finance/fiscal_localizations/brazil.rst:156 -#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:250 +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:267 msgid "You can add or delete accounts according to the company's needs." msgstr "" @@ -15335,10 +15432,10 @@ msgid "Odoo automatically creates three products to be used for transportation c msgstr "" #: ../../content/applications/finance/fiscal_localizations/brazil.rst:237 -#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:265 +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:282 #: ../../content/applications/finance/fiscal_localizations/mexico.rst:174 #: ../../content/applications/finance/fiscal_localizations/mexico.rst:656 -#: ../../content/applications/finance/fiscal_localizations/philippines.rst:40 +#: ../../content/applications/finance/fiscal_localizations/philippines.rst:42 msgid "Contacts" msgstr "" @@ -15419,7 +15516,7 @@ msgid "Fiscal position configuration" msgstr "" #: ../../content/applications/finance/fiscal_localizations/brazil.rst:295 -#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:338 +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:355 #: ../../content/applications/finance/fiscal_localizations/mexico.rst:311 msgid "Workflows" msgstr "" @@ -15512,7 +15609,7 @@ msgid ":doc:`Fiscal positions (tax and account mapping) <../accounting/taxes/fis msgstr "" #: ../../content/applications/finance/fiscal_localizations/brazil.rst:349 -#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:92 +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:109 msgid "Electronic documents" msgstr "" @@ -16046,26 +16143,26 @@ msgid "Configuring partner contacts is also required to send :abbr:`SII (Servici msgstr "" #: ../../content/applications/finance/fiscal_localizations/chile.rst:232 -#: ../../content/applications/finance/fiscal_localizations/chile.rst:1047 -#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:78 -#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:271 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:1096 +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:95 +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:288 msgid ":guilabel:`Name`" msgstr "" #: ../../content/applications/finance/fiscal_localizations/chile.rst:233 -#: ../../content/applications/finance/fiscal_localizations/chile.rst:1048 -#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:83 -#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:276 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:1097 +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:100 +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:293 msgid ":guilabel:`Email`" msgstr "" #: ../../content/applications/finance/fiscal_localizations/chile.rst:234 -#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:80 +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:97 msgid ":guilabel:`Identification Number`" msgstr "" #: ../../content/applications/finance/fiscal_localizations/chile.rst:235 -#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:81 +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:98 msgid ":guilabel:`Taxpayer Type`" msgstr "" @@ -16289,7 +16386,7 @@ msgid ":guilabel:`Documents type 33` electronic invoice must have at least one i msgstr "" #: ../../content/applications/finance/fiscal_localizations/chile.rst:423 -#: ../../content/applications/finance/fiscal_localizations/chile.rst:875 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:924 msgid "Validation and DTE status" msgstr "" @@ -16702,55 +16799,117 @@ msgid "If you claim a vendor bill, the status changes from :guilabel:`Draft` to msgstr "" #: ../../content/applications/finance/fiscal_localizations/chile.rst:749 +msgid "Electronic purchase invoice" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:751 +msgid "The *electronic purchase invoice* is a feature included in the `l10n_cl_edi` module." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:753 +msgid "Once all configurations have been made for :ref:`electronic invoices ` (e.g., uploading a valid company certificate, setting up master data, etc.), the electronic purchase invoices need their own :abbr:`CAFs (Folio Authorization Code)`. Please refer to the :ref:`CAF documentation ` to check the details on how to acquire the :abbr:`CAFs (Folio Authorization Code)` for electronic purchase invoices." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:759 +msgid "Electronic purchase invoices are useful when vendors are not obligated to expedite an electronic vendor bill for your purchase. Still, your obligations require a document to be sent to the :abbr:`SII (Servicio de Impuestos Internos)` as proof of purchase." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:766 +msgid "To generate an electronic purchase invoice from a vendor bill, the bill must be created in a purchase journal with the *Use Documents* feature enabled. It is possible to modify an existing purchase journal or create a new one in the following process." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:770 +msgid "To modify the existing purchase journal, or create a new purchase journal, navigate to :menuselection:`Accounting --> Configuration --> Journals`. Then, click the :guilabel:`New` button, and fill in the following required information:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:774 +msgid ":guilabel:`Type`: select :guilabel:`Purchase` from the drop-down menu for vendor bill journals." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:775 +msgid ":guilabel:`Use Documents`: check this field so the journal can generate electronic documents (in this case the electronic purchase invoice)." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:779 +msgid "Generate an electronic purchase invoice" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:781 +msgid "To generate this type of document, it is necessary to create a vendor bill in Odoo. To do so, navigate to :menuselection:`Accounting --> Vendors --> Bills`, and click the :guilabel:`New` button." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:784 +msgid "When all of the electronic purchase invoice information is filled, select the option :guilabel:`(46) Electronic Purchase Invoice` in the :guilabel:`Document Type` field:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:787 +msgid "After the vendor bill is posted:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:789 +msgid "The :abbr:`DTE (Documentos Tributarios Electrónicos)` file (Electronic Tax Document) is automatically created and added to the chatter." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:791 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:865 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:935 +msgid "The :guilabel:`DTE SII Status` is set as :guilabel:`Pending to be sent`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:793 +msgid "Odoo automatically updates the *DTE Status* every night using a scheduled action. To get a response from the :abbr:`SII (Servicio de Impuestos Internos)` immediately, click the :guilabel:`Send now to SII` button." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/chile.rst:798 #: ../../content/applications/finance/fiscal_localizations/mexico.rst:745 msgid "Delivery guide" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:751 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:800 msgid "To install the :guilabel:`Delivery Guide` module, go to :menuselection:`Apps` and search for `Chile (l10n_cl)`. Then click :guilabel:`Install` on the module :guilabel:`Chile - E-Invoicing Delivery Guide`." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:756 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:805 msgid ":guilabel:`Chile - E-Invoicing Delivery Guide` has a dependency with :guilabel:`Chile - Facturación Electrónica`. Odoo will install the dependency automatically when the :guilabel:`Delivery Guide` module is installed." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:760 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:809 msgid "The *Delivery Guide* module includes the ability to send the :abbr:`DTE (Documentos Tributarios Electrónicos)` to :abbr:`SII (Servicio de Impuestos Internos)` and the stamp in PDF reports for deliveries." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:764 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:813 msgid "Once all configurations have been made for :ref:`electronic invoices ` (e.g., uploading a valid company certificate, setting up master data, etc.), delivery guides need their own :abbr:`CAFs (Folio Authorization Code)`. Please refer to the :ref:`CAF documentation ` to check the details on how to acquire the :abbr:`CAF (Folio Authorization Code)` for electronic Delivery Guides." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:770 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:819 msgid "Verify the following important information in the :guilabel:`Price for the Delivery Guide` configuration:" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:773 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:822 msgid ":guilabel:`From Sales Order`: delivery guide takes the product price from the sales order and shows it on the document." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:775 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:824 msgid ":guilabel:`From Product Template`: Odoo takes the price configured in the product template and shows it on the document." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:777 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:826 msgid ":guilabel:`No show price`: no price is shown in the delivery guide." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:779 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:828 msgid "Electronic delivery guides are used to move stock from one place to another and they can represent sales, sampling, consignment, internal transfers, and basically any product move." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:783 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:832 msgid "Delivery guide from a sales process" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:786 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:835 msgid "A delivery guide should **not** be longer than one page or contain more than 60 product lines." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:788 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:837 msgid "When a sales order is created and confirmed, a delivery order is generated. After validating the delivery order, the option to create a delivery guide is activated." msgstr "" @@ -16758,11 +16917,11 @@ msgstr "" msgid "Create Delivery Guide button on a sales process." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:796 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:845 msgid "When clicking on :guilabel:`Create Delivery Guide` for the first time, a warning message pops up, stating the following:" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:799 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:848 msgid "`No se encontró una secuencia para la guía de despacho. Por favor, establezca el primer número dentro del campo número para la guía de despacho`" msgstr "" @@ -16770,32 +16929,27 @@ msgstr "" msgid "First Delivery Guide number warning message." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:806 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:855 msgid "This warning message means the user needs to indicate the next sequence number Odoo has to take to generate the delivery guide (e.g. next available :abbr:`CAF (Folio Authorization Code)` number), and only happens the first time a delivery guide is created in Odoo. After the first document has been correctly generated, Odoo takes the next available number in the :abbr:`CAF (Folio Authorization Code)` file to generate the following delivery guide." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:812 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:861 msgid "After the delivery guide is created:" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:814 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:863 msgid "The :abbr:`DTE (Documentos Tributarios Electrónicos)` file (Electronic Tax Document) is automatically created and added to the :guilabel:`chatter`." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:816 -#: ../../content/applications/finance/fiscal_localizations/chile.rst:886 -msgid "The :guilabel:`DTE SII Status` is set as :guilabel:`Pending to be sent`." -msgstr "" - #: ../../content/applications/finance/fiscal_localizations/chile.rst:-1 msgid "Chatter notes of Delivery Guide creation." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:822 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:871 msgid "The :guilabel:`DTE Status` is automatically updated by Odoo with a scheduled action that runs every night. To get a response from the :abbr:`SII (Servicio de Impuestos Internos)` immediately, press the :guilabel:`Send now to SII` button." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:826 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:875 msgid "Once the delivery guide is sent, it may then be printed by clicking on the :guilabel:`Print Delivery Guide` button." msgstr "" @@ -16803,27 +16957,27 @@ msgstr "" msgid "Printing Delivery Guide PDF." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:833 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:882 msgid "Delivery guide will have fiscal elements that indicate that the document is fiscally valid when printed (if hosted in *Odoo SH* or on *On-premise* remember to manually add the :guilabel:`pdf417gen` library mentioned in the :ref:`Invoice PDF report section `)." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:839 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:888 msgid "Electronic receipt" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:841 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:890 msgid "To install the :guilabel:`Electronic Receipt` module, go to :menuselection:`Apps` and search for `Chile (l10n_cl)`. Then click :guilabel:`Install` on the module :guilabel:`Chile - Electronic Receipt`." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:846 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:895 msgid ":guilabel:`Chile - Electronic Receipt` has a dependency with :guilabel:`Chile - Facturación Electrónica`. Odoo will install the dependency automatically when the :guilabel:`E-invoicing Delivery Guide` module is installed." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:850 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:899 msgid "Once all configurations have been made for :ref:`electronic invoices ` (e.g., uploading a valid company certificate, setting up master data, etc.), electronic receipts need their own :abbr:`CAFs (Folio Authorization Code)`. Please refer to the :ref:`CAF documentation ` to check the details on how to acquire the :abbr:`CAFs (Folio Authorization Code)` for electronic receipts." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:856 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:905 msgid "Electronic receipts are useful when clients do not need an electronic invoice. By default, there is a partner in the database called :guilabel:`Anonymous Final Consumer` with a generic :abbr:`RUT (Rol Único Tributario)` `66666666-6` and taxpayer type of :guilabel:`Final Consumer`. This partner can be used for electronic receipts or a new record may be created for the same purpose." msgstr "" @@ -16831,7 +16985,7 @@ msgstr "" msgid "Electronic Receipt module." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:865 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:914 msgid "Although electronic receipts should be used for final consumers with a generic :abbr:`RUT (Rol Único Tributario)`, it can also be used for specific partners. After the partners and journals are created and configured, the electronic receipts are created in the standard way as electronic invoice, but the type of document :guilabel:`(39) Electronic Receipt` should be selected in the invoice form:" msgstr "" @@ -16839,15 +16993,15 @@ msgstr "" msgid "Document type 39 for Electronic Receipts." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:877 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:926 msgid "When all of the electronic receipt information is filled, manually (or automatically) proceed to validate the receipt from the sales order. By default, :guilabel:`Electronic Invoice` is selected as the :guilabel:`Document Type`, however in order to validate the receipt correctly, make sure to edit the :guilabel:`Document Type` and change to :guilabel:`Electronic Receipt`." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:882 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:931 msgid "After the receipt is posted:" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:884 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:933 msgid "The :abbr:`DTE (Documentos Tributarios Electrónicos)` file (Electronic Tax Document) is created automatically and added to the :guilabel:`chatter`." msgstr "" @@ -16855,35 +17009,35 @@ msgstr "" msgid "Electronic Receipts STE creation status." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:892 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:941 msgid "The :guilabel:`DTE Status` is automatically updated by Odoo with a scheduled action that runs every day at night. To get a response from the :abbr:`SII (Servicio de Impuestos Internos)` immediately, press the :guilabel:`Send now to SII` button." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:896 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:945 msgid "Please refer to the :ref:`DTE Workflow ` for electronic invoices as the workflow for electronic receipt follows the same process." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:900 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:949 msgid "Electronic export of goods" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:902 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:951 msgid "To install the :guilabel:`Electronic Exports of Goods` module, go to :menuselection:`Apps` and search for `Chile (l10n_cl)`. Then click :guilabel:`Install` on the module :guilabel:`Electronic Exports of Goods for Chile`." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:907 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:956 msgid ":guilabel:`Chile - Electronic Exports of Goods for Chile` has a dependency with :guilabel:`Chile - Facturación Electrónica`." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:910 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:959 msgid "Once all configurations have been made for :ref:`electronic invoices ` (e.g., uploading a valid company certificate, setting up master data, etc.), electronic exports of goods need their own :abbr:`CAFs (Folio Authorization Code)`. Please refer to the :ref:`CAF documentation ` to check the details on how to acquire the :abbr:`CAFs (Folio Authorization Code)` for electronic receipts." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:916 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:965 msgid "Electronic invoices for the export of goods are tax documents that are used not only for the :abbr:`SII (Servicio de Impuestos Internos)` but are also used with customs and contain the information required by it." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:921 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:970 msgid "Contact configurations" msgstr "" @@ -16891,11 +17045,11 @@ msgstr "" msgid "Taxpayer Type needed for the Electronic Exports of Goods module." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:928 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:977 msgid "Chilean customs" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:930 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:979 msgid "When creating an electronic exports of goods invoice, these new fields in the :guilabel:`Other Info` tab are required to comply with Chilean regulations." msgstr "" @@ -16903,11 +17057,11 @@ msgstr "" msgid "Chilean customs fields." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:938 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:987 msgid "PDF report" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:940 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:989 msgid "Once the invoice is accepted and validated by the :abbr:`SII (Servicio de Impuestos Internos)` and the PDF is printed, it includes the fiscal elements that indicate that the document is fiscally valid and a new section needed for customs." msgstr "" @@ -16915,11 +17069,11 @@ msgstr "" msgid "PDF report section for the Electronic Exports of Goods PDF Report." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:949 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:998 msgid "eCommerce electronic invoicing" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:951 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:1000 msgid "To install the :guilabel:`Chilean eCommerce` module, go to :menuselection:`Apps, search for the module by its technical name `l10n_cl_edi_website_sale`, and click the :guilabel:`Activate` button." msgstr "" @@ -16927,27 +17081,27 @@ msgstr "" msgid "l10n_cl eCommerce module." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:958 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:1007 msgid "This module enables the features and configurations to:" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:960 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:1009 msgid "Generate electronic documents from the *eCommerce* application" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:961 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:1010 msgid "Support for required fiscal fields in the *eCommerce* application" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:962 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:1011 msgid "Effectively let the final client decide the electronic document to be generated for their purchase" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:965 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:1014 msgid "Once all of the configurations are made for the Chilean :ref:`electronic invoice ` flow, the following configurations are required for the eCommerce flow to be integrated." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:969 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:1018 msgid "To configure your website to generate electronic documents during the sale process, go to :menuselection:`Website --> Configuration --> Settings --> Invoicing` and activate the :guilabel:`Automatic Invoice` feature. Activating this feature allows electronic documents to be automatically generated when an online payment is confirmed." msgstr "" @@ -16955,15 +17109,15 @@ msgstr "" msgid "Invoice Policy and Automatic Invoice configurations." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:978 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:1027 msgid "Since an online payment needs to be confirmed for the *automatic invoice* feature to generate the document, a payment provider must be configured for the related website." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:982 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:1031 msgid "Review the :doc:`../payment_providers` documentation for information on which payment providers are supported in Odoo, and how to configure them." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:985 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:1034 msgid "It is also recommended to configure your products so they are able to be invoiced when an online payment is confirmed. To do so, go to :menuselection:`Website --> eCommerce --> Products` and select the product template of the desired product. Then, set the :guilabel:`Invoicing Policy` to :guilabel:`Ordered quantities`." msgstr "" @@ -16971,12 +17125,12 @@ msgstr "" msgid "Invoice Policy configuration in Products." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:995 -#: ../../content/applications/finance/fiscal_localizations/chile.rst:1081 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:1044 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:1130 msgid "Invoicing flows" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:997 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:1046 msgid "Clients from Chile will be able to select if they need an **invoice** or a **ballot** for their purchase with an extra step added during the checkout process." msgstr "" @@ -16984,7 +17138,7 @@ msgstr "" msgid "Option for EDI Documents for clients." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:1004 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:1053 msgid "If the customer selects the :guilabel:`Electronic Invoice` option, fiscal fields are required to be filled out, including the :guilabel:`Activity Description`, the :guilabel:`Identification Number` and their :guilabel:`DTE Email`." msgstr "" @@ -16992,23 +17146,23 @@ msgstr "" msgid "Fiscal fields required for an Invoice to be requested." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:1012 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:1061 msgid "If the client selects the :guilabel:`Electronic Receipts` option, they will be directed to the next step, and the electronic document will be generated for the *Consumidor Final Anónimo* contact." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:1015 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:1064 msgid "Clients from countries other than Chile, will have their electronic receipts automatically generated for them by Odoo." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:1019 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:1068 msgid "If a purchase through eCommerce requires an export, the customer will need to contact your company to generate an electronic export invoice (*document type 110*), which can be done from the *Accounting* app." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:1024 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:1073 msgid "Point of Sale electronic invoicing" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:1026 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:1075 msgid "To install the :guilabel:`Chilean Module for Point of Sale`, go to the :menuselection:`Apps` application on the main Odoo dashboard, search for the module by its technical name `l10n_cl_edi_pos`, and click the :guilabel:`Activate` button." msgstr "" @@ -17016,47 +17170,47 @@ msgstr "" msgid "l10n_cl POS EDI module." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:1034 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:1083 msgid "This module enables the following features and configurations to:" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:1036 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:1085 msgid "Generate electronic documents from the *Point of Sale* application" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:1037 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:1086 msgid "Support the required fiscal fields for contacts created in the *Point of Sale* application" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:1038 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:1087 msgid "Effectively lets the final client decide the type of electronic document to be generated for their purchase" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:1040 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:1089 msgid "Print QR or 5-digit codes in tickets to access to electronic invoices" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:1042 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:1091 msgid "To configure contacts with the required fiscal information, review the :ref:`partner information ` section, or directly modify a contact. Navigate to :menuselection:`Point of Sale --> Session --> Customers --> Details`, and edit any of the following fields:" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:1049 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:1098 msgid ":guilabel:`Identification Type`" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:1050 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:1099 msgid ":guilabel:`Tax Payer Type`" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:1051 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:1100 msgid ":guilabel:`Type Giro`" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:1052 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:1101 msgid ":guilabel:`DTE Email`" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:1053 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:1102 msgid ":guilabel:`RUT`" msgstr "" @@ -17064,7 +17218,7 @@ msgstr "" msgid "Contact with fiscal information created from POS." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:1059 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:1108 msgid "To configure the products, navigate to :menuselection:`Point of Sale --> Products --> Products` and select a product record. In the :guilabel:`Sales` tab of the product form, it is necessary to mark the product as :guilabel:`Available for POS`, this makes the product available for sale in the *Point of Sale* app." msgstr "" @@ -17072,15 +17226,15 @@ msgstr "" msgid "Product with fiscal information created from POS." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:1068 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:1117 msgid "Optionally, the following features are available for configuration in the :menuselection:`Point of Sale --> Configuration --> Settings --> Bills & Receipts section`:" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:1071 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:1120 msgid ":guilabel:`Use QR code on ticket`: this feature enables a QR code to be printed on the user's receipt so they can easily request an invoice after their purchase" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:1073 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:1122 msgid ":guilabel:`Generate a code on ticket`: this feature enables a 5-digit code to be generated on the receipt, allowing the user to request an invoice through the customer portal" msgstr "" @@ -17088,15 +17242,15 @@ msgstr "" msgid "Configuration to generate QR or 5 digit codes on tickets." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:1083 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:1132 msgid "The following sections cover the invoicing flows for the *Point of Sale* application." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:1086 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:1135 msgid "Electronic receipts: anonymous end user" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:1088 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:1137 msgid "When making a purchase as an anonymous user that does not request an electronic invoice, Odoo automatically selects :guilabel:`Consumidor Final Anónimo` as the contact for the order and generates the electronic receipt." msgstr "" @@ -17104,15 +17258,15 @@ msgstr "" msgid "Automatic contact selection of an anonymous end consumer." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:1097 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:1146 msgid "If the client requests a credit note due to a return of their purchase, the credit note should be made using the *Accounting* app. See the :doc:`credit notes and refunds <../accounting/customer_invoices/credit_notes>` documentation for detailed instructions." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:1102 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:1151 msgid "Electronic receipts: specific customer" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:1104 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:1153 msgid "When specific user makes a purchase that does not request an electronic invoice, Odoo automatically selects the contact for the order as the :guilabel:`Consumidor Final Anónimo`, and allows you to select or create the required customer contact with their fiscal information for the receipt." msgstr "" @@ -17120,16 +17274,16 @@ msgstr "" msgid "Selection of contact for the receipt." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:1113 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:1162 msgid "If the client requests a credit note because of a return of this type of purchase, the credit note and return process can be managed directly from the :abbr:`POS (Point of Sale)` session." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:1117 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:1166 #: ../../content/applications/finance/fiscal_localizations/colombia.rst:260 msgid "Electronic invoices" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:1119 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:1168 msgid "When clients request an electronic invoice, it is possible to select or create the required contact with their fiscal information. When the payment is being made, select the option :guilabel:`Invoice` to generate the document." msgstr "" @@ -17137,15 +17291,15 @@ msgstr "" msgid "Selection of invoice option at payment." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:1128 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:1177 msgid "For both the electronic receipts and invoices, if the product is not affected by taxes, Odoo detects this and generates the correct type of document for tax-exempt sales." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:1132 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:1181 msgid "Returns" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:1134 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:1183 msgid "For electronic receipts (not generated for the *Consumidor Final Anónimo*) and electronic invoices, it is possible to manage the process to return products sold in a :abbr:`POS (Point of Sale)` order by selecting the :guilabel:`Refund` button." msgstr "" @@ -17153,7 +17307,7 @@ msgstr "" msgid "Refund option in the POS application." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:1142 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:1191 msgid "Orders can be searched by the order status or by contact, and be selected for the refund to be based on the client's original order." msgstr "" @@ -17161,23 +17315,23 @@ msgstr "" msgid "Selection of order for the refund process." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:1149 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:1198 msgid "When the return payment is validated, Odoo generates the necessary credit note, referencing the original receipt or invoice, partially or fully canceling the document." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:1153 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:1202 msgid "`Smart tutorial - Electronic invoicing for point of sale `_." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:1160 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:1209 msgid "Balance tributario de 8 columnas" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:1162 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:1211 msgid "This report presents the accounts in detail (with their respective balances), classifying them according to their origin and determining the level of profit or loss that the business had within the evaluated period of time." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:1166 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:1215 msgid "You can find this report in :menuselection:`Accounting --> Reporting --> Balance Sheet` and selecting in the :guilabel:`Report` field the option :guilabel:`Chilean Fiscal Balance (8 Columns) (CL)`." msgstr "" @@ -17189,19 +17343,19 @@ msgstr "" msgid "Chilean Fiscal Balance (8 Columns)." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:1179 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:1228 msgid "Propuesta F29" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:1181 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:1230 msgid "The form *F29* is a new system that the :abbr:`SII (Servicio de Impuestos Internos)` enabled to taxpayers, and that replaces the *Purchase and Sales Books*. This report is integrated by Purchase Register (CR) and the Sales Register (RV). Its purpose is to support the transactions related to VAT, improving its control and declaration." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:1186 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:1235 msgid "This record is supplied by the electronic tax documents (DTE's) that have been received by the :abbr:`SII (Servicio de Impuestos Internos)`." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:1189 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:1238 msgid "You can find this report in :menuselection:`Accounting --> Reporting --> Tax Reports` and selecting the :guilabel:`Report` option :guilabel:`Propuesta F29 (CL)`." msgstr "" @@ -17209,7 +17363,7 @@ msgstr "" msgid "Location of the Propuesta F29 (CL) Report." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:1196 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:1245 msgid "It is possible to set the :abbr:`PPM (Provisional Monthly Payments rate)` and the :guilabel:`Proportional Factor for the fiscal year` from the :menuselection:`Accounting --> Configuration --> Settings`." msgstr "" @@ -17217,7 +17371,7 @@ msgstr "" msgid "Default PPM and Proportional Factor for the Propuesta F29 Report." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:1204 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:1253 msgid "Or manually in the reports by clicking on the :guilabel:`✏️ (pencil)` icon." msgstr "" @@ -17891,23 +18045,71 @@ msgstr "" msgid "Includes all the technical and functional requirements to generate and validate :doc:`Electronics Documents <../accounting/customer_invoices/electronic_invoicing>`, based on the Technical documentation published by the SRI. The authorized documents are: Invoices, Credit Notes, Debit Notes, Withholdings and Purchase liquidations." msgstr "" +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:64 +msgid ":guilabel:`Ecuadorian Accounting Reports`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:65 +msgid "`l10n_ec_reports`" +msgstr "" + #: ../../content/applications/finance/fiscal_localizations/ecuador.rst:66 -msgid "When you install a database from scratch selecting `Ecuador` as the country, Odoo automatically installs the base module :guilabel:`Ecuadorian - Accounting`." +msgid "Includes all the technical and functional requirements to generate forms 103 and 104." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:67 +msgid ":guilabel:`Ecuador - ATS Report`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:68 +msgid "`l10n_ec_reports_ats`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:69 +msgid "Includes all the technical and functional requirements to generate the ATS report XML file ready to be uploaded to the *DIMM Formularios*." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:71 +msgid ":guilabel:`Ecuadorian Website`" msgstr "" #: ../../content/applications/finance/fiscal_localizations/ecuador.rst:72 -msgid "To configure your company information, go to the :guilabel:`Contacts` app and search the name given to your company or activate :ref:`developer mode ` and go to :menuselection:`Company --> Contact` and then edit the contact to configure the following information:" +msgid "`l10n_ec_website_sale`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:73 +msgid "Includes all the technical and functional requirements to generate automatic electronic invoices from a Website sale." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:75 +msgid ":guilabel:`Ecuadorian Point of Sale`" msgstr "" #: ../../content/applications/finance/fiscal_localizations/ecuador.rst:76 +msgid "`l10n_ec_edi_pos`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:77 +msgid "Includes all the technical and functional requirements to generate automatic electronic invoices from a PoS sale." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:81 +msgid "When you install a database from scratch selecting `Ecuador` as the country, Odoo automatically installs the base module :guilabel:`Ecuadorian - Accounting`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:89 +msgid "To configure your company information, go to the :guilabel:`Contacts` app and search the name given to your company or activate :ref:`developer mode ` and go to :menuselection:`Company --> Contact` and then edit the contact to configure the following information:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:93 msgid "Check the :guilabel:`Company` option on top" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:79 +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:96 msgid ":guilabel:`Address`" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:85 +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:102 msgid "Upload company logo and save" msgstr "" @@ -17915,59 +18117,59 @@ msgstr "" msgid "Populate company data for Ecuador in Odoo Contacts." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:94 +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:111 msgid "To upload your information for electronic documents go to :menuselection:`Accounting --> Configuration --> Settings` and search for :command:`Ecuadorian Localization`." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:97 +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:114 msgid "Configure the next information:" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:99 +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:116 msgid ":guilabel:`Company legal name`" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:100 +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:117 msgid ":guilabel:`Use production servers`: check the checkbox if your company is going to do electronic documents in the production environment. If you want to use the testing environment for electronic documents then keep the checkbox unchecked." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:103 +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:120 msgid ":guilabel:`Regime`: select if your company is in General Regular or is qualified as RIMPE." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:104 +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:121 msgid ":guilabel:`Forced to keep accounting books`: check the checkbox if your company has this condition." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:106 +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:123 msgid ":guilabel:`Default taxes for withholdings`" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:107 +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:124 msgid ":guilabel:`Issue withholds`: check the checkbox if your company is going to do electronic withholds." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:109 +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:126 msgid ":guilabel:`Withhold consumibles`: put the code of the withholding for when you buy goods." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:110 +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:127 msgid ":guilabel:`Withhold services`: put the code of the withholding for when you buy services." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:111 +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:128 msgid ":guilabel:`Withhold credit card`: put the code of the withholding for when you buy with credit card" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:113 +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:130 msgid ":guilabel:`Withhold agent number`: put the company withholding agent resolution number, if applicable for your company." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:115 +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:132 msgid ":guilabel:`Electronic Certificate File`: upload electronic certificate and password, then save it." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:116 +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:133 msgid ":guilabel:`Special tax contributor number`: if your company is qualified as a special taxpayer, fill out this field with it's corresponding tax contributor number." msgstr "" @@ -17975,19 +18177,19 @@ msgstr "" msgid "Electronic signature for Ecuador." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:124 +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:141 msgid "When configuring the withholdings in the configuration menu, these suggested withholdings are only for domestic suppliers when no withholdings are setup on their *Taxpayer Type*. Moreover, the Credit Card withholding set up is always used when a Credit or Debit Card SRI Payment Metho is used." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:130 +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:147 msgid "VAT withholding" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:132 +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:149 msgid "This configuration only applies if you are qualified as a *Withholding Agent* by the SRI, otherwise skip this step. To configure your VAT withholding, go to :menuselection:`Accounting --> Accounting --> Configuration --> Ecuadorian SRI: Taxpayer Type SRI`." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:136 +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:153 msgid "You must configure the withholding percentage that applies for each type of taxpayer, specify the :guilabel:`Goods VAT Withholding` and the :guilabel:`Services VAT Withholding`." msgstr "" @@ -17995,71 +18197,71 @@ msgstr "" msgid "Taxpayer Type configuration for Ecuador." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:144 +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:161 msgid "In the case that the :guilabel:`Taxpayer Type` is `RIMPE`, also configure the :guilabel:`Profit Withholding` percentage." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:148 +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:165 msgid "Printer points" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:150 +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:167 msgid "To configure your printer points, go to :menuselection:`Accounting --> Configuration --> Accounting: Journals`." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:153 +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:170 msgid "Printer points need to be configured for each type of electronic document that you need. For example: Customer Invoice, Credit Notes, and Debit Notes" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:156 +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:173 msgid "For each printer point, you need to configure the following information:" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:158 +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:175 msgid ":guilabel:`Journal Name`: in this format `[Emission Entity]-[Emission Point] [Document Type]`, for example: `001-001 Sales Documents`." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:160 +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:177 msgid ":guilabel:`Type`: refers to the type of journal, select `Sales`." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:161 -#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:195 -#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:222 +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:178 +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:212 +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:239 msgid ":guilabel:`Use Documents?`: this checkbox is automatically checked, leave it checked." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:162 -#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:196 -#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:223 +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:179 +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:213 +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:240 msgid ":guilabel:`Emission Entity`: configure the establishment number." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:163 -#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:197 -#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:224 +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:180 +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:214 +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:241 msgid ":guilabel:`Emission Point`: configure the printer point." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:164 -#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:198 -#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:225 +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:181 +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:215 +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:242 msgid ":guilabel:`Emission address`: configure the address of the establishment." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:165 +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:182 msgid ":guilabel:`Default income account`: configure the default income account." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:166 +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:183 msgid ":guilabel:`Dedicated Credit Note Sequence`: check the checkbox if *Credit Notes* are to be generated from this printer point - journal." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:168 +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:185 msgid ":guilabel:`Short Code`: This is the unique code for the sequence of accounting entries, enter a unique 5-digit code, for example: `VT001`" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:171 +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:188 msgid "Customer Invoice, Credit Notes and Debit Notes need to use the same journal as the :guilabel:`Emission Point`, and the :guilabel:`Entity Point` should be unique per journal." msgstr "" @@ -18067,37 +18269,37 @@ msgstr "" msgid "Configuring a printer point for Ecuador electronic document type of Customer Invoices." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:179 +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:196 msgid "In the :guilabel:`Advanced Settings` tab, check the :guilabel:`Electronic Invoicing` checkbox to enable it for Ecuador." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:186 +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:203 msgid "Withholding" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:188 +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:205 msgid "A Withholding Journal must be defined, go to go to :menuselection:`Accounting --> Configuration --> Accounting: Journals` where you need to configure the following information:" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:191 +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:208 msgid ":guilabel:`Journal Name`: in this format `[Emission Entity]-[Emission Point] [Document Type]`, for example: `001-001 Withholding`." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:193 -#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:220 +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:210 +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:237 msgid ":guilabel:`Type`: refers to the type of journal, select `Miscellaneous`." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:194 +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:211 msgid ":guilabel:`Withhold Type`: Configure Purchase Withholding." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:199 +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:216 msgid ":guilabel:`Default account`: configure the default income account." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:200 -#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:226 +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:217 +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:243 msgid ":guilabel:`Short Code`: This is the unique code for the sequence of accounting entries, enter a unique 5-digit code, for example: `RT001`" msgstr "" @@ -18105,24 +18307,24 @@ msgstr "" msgid "Configuring withholding for Ecuador electronic document type of Withholding." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:208 -#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:234 +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:225 +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:251 msgid "In the :guilabel:`Advanced Settings` tab, check the :guilabel:`Electronic Invoicing` checkbox to enable the sending of electronic invoicing for the withholding." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:212 +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:229 msgid "Purchase Liquidations" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:214 +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:231 msgid "When using Purchase Liquidations, a specific journal must be created, go to :menuselection:`Accounting --> Configuration --> Accounting: Journals` and configure the following information:" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:218 +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:235 msgid ":guilabel:`Journal Name`: in this format `[Emission Entity]-[Emission Point] [Document Type]`, for example: `001-001 Withhold`." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:221 +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:238 msgid ":guilabel:`Purchase Liquidations`: check the checkbox to enable purchase liquidations." msgstr "" @@ -18130,19 +18332,19 @@ msgstr "" msgid "Configuring purchase liquidations for Ecuador electronic document type of Withholding." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:243 +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:260 msgid "The :doc:`chart of accounts <../accounting/get_started/chart_of_accounts>` is installed by default as part of the set of data included in the localization module, the accounts are mapped automatically in Taxes, Default Account Payable, Default Account Receivable." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:247 +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:264 msgid "The chart of accounts for Ecuador is based on the most updated version of Superintendency of Companies, which is grouped in several categories and is compatible with NIIF accounting." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:255 +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:272 msgid "In addition to the basic information in your products, you must add the configuration of the withholding code (tax) that applies." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:258 +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:275 msgid "Go to :menuselection:`Accounting --> Vendors: Products` under the tab \"Purchase\"" msgstr "" @@ -18150,23 +18352,23 @@ msgstr "" msgid "Product for Ecuador." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:267 +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:284 msgid "Configure the next information when you create a contact:" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:269 +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:286 msgid "Check the :guilabel:`Company` option on top if it is a contact with RUC, or check :guilabel:`Individual` if it is a contact with cedula or passport." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:272 +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:289 msgid ":guilabel:`Address`: :guilabel:`Street` is a required field to confirm the Electronic Invoice." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:273 +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:290 msgid ":guilabel:`Identification Number`: select an identification type `RUC`, `Cedula`, or `Passport`." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:274 +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:291 msgid ":guilabel:`Taxpayer Type`: select the contact's SRI Taxpayer Type." msgstr "" @@ -18174,15 +18376,15 @@ msgstr "" msgid "Contacts for Ecuador." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:283 +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:300 msgid "The :guilabel:`SRI Taxpayer Type` has inside the configuration of which VAT and Profit withholding will apply when you use this contact on Vendor Bill, and then create a withholding from there." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:288 +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:305 msgid "Review your taxes" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:290 +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:307 msgid "As part of the localization module, taxes are automatically created with its configuration and related financial accounts." msgstr "" @@ -18190,35 +18392,35 @@ msgstr "" msgid "Taxes for Ecuador." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:297 +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:314 msgid "The following options have been automatically configured:" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:299 +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:316 msgid ":guilabel:`Tax Support`: to be configured only in the IVA tax, this option is useful when you register purchase withholdings." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:301 +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:318 msgid ":guilabel:`Code ATS`: to be configured only for income tax withholding codes, it is important when you register the withholding." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:303 +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:320 msgid ":guilabel:`Tax Grids`: configure the codes of 104 form if it is a IVA tax and configure the codes of 103 form if it is a income tax withholding code." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:305 +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:322 msgid ":guilabel:`Tax Name`:" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:307 +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:324 msgid "For IVA tax, format the name as: `IVA [percent] (104, [form code] [tax support code] [tax support short name])`" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:309 +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:326 msgid "For income tax withholding code, format the name as: `Code ATS [Percent of withhold] [withhold name]`" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:312 +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:329 msgid "Once the Ecuador module is installed, the most common taxes are automatically configured. If you need to create an additional one, you can do so, for which you must base yourself on the configuration of the existing taxes." msgstr "" @@ -18226,19 +18428,19 @@ msgstr "" msgid "Taxes with tax support for Ecuador." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:321 +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:338 msgid "Review your Document Types" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:323 +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:340 msgid "Some accounting transactions like *Customer Invoices* and *Vendor Bills* are classified by document types. These are defined by the government fiscal authorities, in this case by the SRI." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:326 +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:343 msgid "Each document type can have a unique sequence per journal where it is assigned. As part of the localization, the document type includes the country on which the document is applicable; also the data is created automatically when the localization module is installed." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:330 +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:347 msgid "The information required for the document types is included by default so the user does not need to fill anything there." msgstr "" @@ -18246,41 +18448,41 @@ msgstr "" msgid "Document types for Ecuador." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:340 +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:357 msgid "Once you have configured your database, you can register your documents." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:343 +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:360 msgid "Sales documents" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:348 +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:365 msgid ":guilabel:`Customer invoices` are electronic documents that, when validated, are sent to SRI. These documents can be created from your sales order or manually. They must contain the following data:" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:351 -#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:395 -#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:428 +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:368 +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:412 +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:445 msgid ":guilabel:`Customer`: type the customer's information." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:352 +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:369 msgid ":guilabel:`Journal`: select the option that matches the printer point for the customer invoice." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:353 +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:370 msgid ":guilabel:`Document Type`: type document type in this format `(01) Invoice`." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:354 -#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:474 -#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:512 +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:371 +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:491 +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:529 msgid ":guilabel:`Payment Method (SRI)`: select how the invoice is going to be paid." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:355 -#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:475 -#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:513 +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:372 +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:492 +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:530 msgid ":guilabel:`Products`: specify the product with the correct taxes." msgstr "" @@ -18288,48 +18490,48 @@ msgstr "" msgid "Customer invoice for Ecuador." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:362 +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:379 msgid "Customer credit note" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:364 +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:381 msgid "The :doc:`Customer credit note <../accounting/customer_invoices/credit_notes>` is an electronic document that, when validated, is sent to SRI. It is necessary to have a validated (posted) invoice in order to register a credit note. On the invoice there is a button named :guilabel:`Credit note`, click on this button to be directed to the :guilabel:`Create credit note` form, then complete the following information:" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:370 +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:387 msgid ":guilabel:`Credit Method`: select the type of credit method." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:372 +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:389 msgid ":guilabel:`Partial Refund`: use this option when you need to type the first number of documents and if it is a partial credit note." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:374 +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:391 msgid ":guilabel:`Full Refund`: use this option if the credit note is for the total invoice and you need the credit note to be auto-validated and reconciled with the invoice." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:376 +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:393 msgid ":guilabel:`Full refund and new draft invoice`: use this option if the credit note is for the total invoice and you need the credit note to be auto-validated and reconciled with the invoice, and auto-create a new draft invoice." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:380 +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:397 msgid ":guilabel:`Reason`: type the reason for the credit note." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:381 +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:398 msgid ":guilabel:`Rollback Date`: select the :guilabel:`specific` options." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:382 +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:399 msgid ":guilabel:`Reversal Date`: type the date." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:383 -#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:416 +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:400 +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:433 msgid ":guilabel:`Use Specific Journal`: select the printer point for your credit note, or leave it empty if you want to use the same journal as the original invoice." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:386 +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:403 msgid "Once reviewed, you can click on the :guilabel:`Reverse` button." msgstr "" @@ -18337,21 +18539,21 @@ msgstr "" msgid "Add Customer Credit Note for Ecuador." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:392 +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:409 msgid "When the :guilabel:`Partial Refund` option is used, you can change the amount of the credit note and then validate it. Before validating the credit note, review the following information:" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:396 -#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:429 +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:413 +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:446 msgid ":guilabel:`Journal`: select the printer point for the customer Credit Note." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:397 +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:414 msgid ":guilabel:`Document Type`: this is the document type `(04) Credit Note`." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:398 -#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:431 +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:415 +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:448 msgid ":guilabel:`Products`: It must specify the product with the correct taxes." msgstr "" @@ -18359,27 +18561,27 @@ msgstr "" msgid "Customer Credit Note for Ecuador." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:405 +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:422 msgid "Customer debit note" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:407 +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:424 msgid "The :guilabel:`Customer debit note` is an electronic document that, when validated, is sent to SRI. It is necessary to have a validated (posted) invoice in order to register a debit note. On the invoice there is a button named :guilabel:`Debit Note`, click on this button to be directed to the :guilabel:`Create debit note` form, then complete the following information:" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:412 +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:429 msgid ":guilabel:`Reason`: type the reason for the debit note." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:413 +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:430 msgid ":guilabel:`Debit note date`: select the :guilabel:`specific` options." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:414 +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:431 msgid ":guilabel:`Copy lines`: select this option if you need to register a debit note with the same lines of invoice." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:419 +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:436 msgid "Once reviewed you can click on the :guilabel:`Create Debit Note` button." msgstr "" @@ -18387,11 +18589,11 @@ msgstr "" msgid "Add Customer Debit Note for Ecuador." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:425 +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:442 msgid "You can change the debit note amount, and then validate it. Before validating the debit note, review the following information:" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:430 +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:447 msgid ":guilabel:`Document Type`: this is the document type `(05) Debit Note`." msgstr "" @@ -18399,27 +18601,27 @@ msgstr "" msgid "Customer Debit Note for Ecuador." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:438 +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:455 msgid "Customer withholding" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:440 +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:457 msgid "The :guilabel:`Customer withholding` is a non-electronic document for your company, this document is issued by the client in order to apply a withholding to the sale." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:443 +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:460 msgid "It is necessary to have a validated (posted) invoice in order to register a customer withholding. On the invoice there is a button named :guilabel:`Add Withhold`, click on this button to be directed to the :guilabel:`Customer withholding` form, then complete the following information:" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:447 +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:464 msgid ":guilabel:`Document Number`: type the withholding number." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:448 +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:465 msgid ":guilabel:`Withhold Lines`: select the taxes that the customer is withholding." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:450 +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:467 msgid "Before validating the withholding, review that the amounts for each tax are the same as the original document." msgstr "" @@ -18427,41 +18629,41 @@ msgstr "" msgid "Customer withhold for Ecuador." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:458 +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:475 msgid "Purchase Documents" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:461 +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:478 #: ../../content/applications/finance/fiscal_localizations/romania.rst:130 msgid "Vendor bill" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:463 +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:480 msgid "The :guilabel:`Vendor bill` is a non-electronic document for your company, this document is issued by your vendor when your company generates a purchase." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:466 +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:483 msgid "The bills can be created from the purchase order or manually, it must contain the following information:" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:469 -#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:506 +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:486 +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:523 msgid ":guilabel:`Vendor`: type the vendor's information." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:470 +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:487 msgid ":guilabel:`Bill Date`: select the date of invoice." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:471 +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:488 msgid ":guilabel:`Journal`: it is the journal for vendor bills." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:472 +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:489 msgid ":guilabel:`Document Type`: this is the document type `(01) Invoice`" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:473 +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:490 msgid ":guilabel:`Document number`: type the document number." msgstr "" @@ -18469,60 +18671,60 @@ msgstr "" msgid "Purchases for Ecuador." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:482 +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:499 msgid "When creating the purchase withholding, verify that the bases (base amounts) are correct. If you need to edit the amount of the tax in the :guilabel:`Vendor bill`, click the :guilabel:`Edit` button. Otherwise, from the :guilabel:`Journal Items` tab click the :guilabel:`Edit` button and set the adjustment to go where you want." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:488 +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:505 msgid "Purchase liquidation" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:490 +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:507 msgid "The :guilabel:`Purchase liquidation` is an electronic document that, when validated, is sent to SRI." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:492 +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:509 msgid "Companies issue this type of electronic document when they purchase, and the vendor does not issue an invoice due to one or more of the following cases:" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:495 +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:512 msgid "Services were provided by non-residents of Ecuador." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:496 +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:513 msgid "Services provided by foreign companies without residency or establishment in Ecuador." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:497 +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:514 msgid "Purchase of goods or services from natural persons not registered with a RUC, who due to their cultural level or hardiness are not able to issue sales receipts or customer invoices." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:499 +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:516 msgid "Reimbursement for the purchase of goods or services to employees in a dependency relationship (full-time employee)." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:501 +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:518 msgid "Services provided by members of collegiate bodies for the exercise of their function." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:503 +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:520 msgid "These types of electronic documents can be created from the :guilabel:`Purchase Order` or manually from the :guilabel:`Vendor Bills` form view. It must contain the following data:" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:507 +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:524 msgid ":guilabel:`Journal`: select the journal for the :guilabel:`Purchase Liquidation` with the correct printer point." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:509 +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:526 msgid ":guilabel:`Document Type`: this is the document type `(03) Purchase Liquidation`" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:510 -#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:530 +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:527 +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:547 msgid ":guilabel:`Document number`: type the document number (sequence), you will only have to do this once, then the sequence will be automatically assigned for the next documents." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:515 +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:532 msgid "Once you review the information you can validate the :guilabel:`Purchase Liquidation`." msgstr "" @@ -18530,23 +18732,23 @@ msgstr "" msgid "Purchase liquidation for Ecuador." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:522 +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:539 msgid "Purchase withholding" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:524 +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:541 msgid "The :guilabel:`Purchase withholding` is an electronic document that, when validated, is sent to SRI." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:526 +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:543 msgid "It is necessary to have an invoice in a validated state in order to register a :guilabel:`Purchase withholding`. On the invoice, there is a button named :guilabel:`Add Withhold`, click on this button to be directed to the :guilabel:`Withholding` form, then complete the following information:" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:532 +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:549 msgid ":guilabel:`Withhold lines`: The taxes appear automatically according to the configuration of products and vendors, you should review if the taxes and tax support are correct, and, if it is not correct, you can edit and select the correct taxes and tax support." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:536 +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:553 msgid "Once you review the information you can validate the :guilabel:`Withholding`." msgstr "" @@ -18554,59 +18756,207 @@ msgstr "" msgid "Purchase withhold for Ecuador." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:543 +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:560 msgid "You can't change the tax support for one that was not included in the configuration of the taxes used on the :guilabel:`Vendor Bill`. To do so, go to the tax applied on the :guilabel:`Vendor Bill` and change the :guilabel:`Tax Support` there." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:547 +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:564 msgid "A withholding tax can be divided into two or more lines, this will depend on whether two or more withholdings percentages apply." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:551 +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:568 msgid "The system suggests a VAT withholding of 30% with tax support 01, you can add your VAT withholding of 70% in a new line with the same tax support, the system will allow you as long as the total of the bases matches the total from the :guilabel:`Vendor Bill`." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:556 +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:575 +msgid "The :ref:`ATS Report module ` enables the following:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:577 +msgid "Choose the SRI Payment Method in each payment method's configuration." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:578 +msgid "Customers can manually input their identification type and identification number during the eCommerce checkout process." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:580 +msgid "Automatically generate a valid electronic invoice for Ecuador at the end of the checkout process." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:586 +msgid "Website" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:588 +msgid "To generate an invoice after the checkout process, navigate to :menuselection:`Website --> Configuration --> Settings` and activate the :guilabel:`Automatic Invoice` option found under the :guilabel:`Invoicing` section." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:593 +msgid "The invoice's email template can be modified from the :guilabel:`Invoice Email Template` field under the :guilabel:`Automatic Invoice` option." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:597 +msgid "The sales journal used for invoicing is the first in the sequence of priority in the :guilabel:`Journal` menu." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:601 +msgid "Payment providers" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:603 +msgid "To activate the payment providers that should be used to capture eCommerce payments, navigate to :menuselection:`Website --> Configuration --> Payment Providers` section and then click on the :guilabel:`View other providers` button under the :guilabel:`Activate Payments` heading. From here, each payment provider can be configured by selecting a provider record. Refer to the :doc:`payment provider <../payment_providers>` documentation for more information." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:610 +#: ../../content/applications/finance/payment_providers.rst:224 +msgid "Payment methods" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:612 +msgid "To activate one or more payment methods for a payment provider, click :guilabel:`→ Enable Payment Methods` within the :guilabel:`Configuration` tab of each provider." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:615 +msgid "When configuring the payment method, it is **mandatory** to set the :guilabel:`SRI Payment Method` for each method. This field appears after you create and save the payment method for the first time." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:620 +msgid "Adding the :guilabel:`SRI Payment Method` is necessary to generate correctly the electronic invoice from an eCommerce sale. Select a **payment method** to access its configuration menu and the field." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:625 +msgid ":doc:`Payment provider <../payment_providers>`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:-1 +msgid "l10n_ec SRI Payment Method." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:632 +msgid "eCommerce workflow" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:635 +msgid "Type and identification number" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:637 +msgid "The client who is making a purchase will have the option to indicate their identification type and number during the checkout process. This information is required to correctly generate the electronic invoice after the checkout is completed." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:-1 +msgid "Website checkout form." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:646 +msgid "Verification is done to ensure the *Identification Number* field is completed and has the correct number of digits. For RUC identification, 13 digits are required. For Cédula, 9 digits are required." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:650 +msgid "After finishing the checkout process, a confirmed invoice is generated, ready to be sent manually or asynchronously to the SRI." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:654 msgid "Financial Reports" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:558 -msgid "In Ecuador, there are fiscal reports that the company presents to SRI. In Odoo, we have two of the main financial reports used by companies. These are the reports 103 and 104." +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:656 +msgid "In Ecuador, there are fiscal reports that the company presents to SRI. Odoo supports two of the main financial reports used by companies: **reports 103** and **104**." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:561 -msgid "To get these reports go to the :guilabel:`Accounting` app and select :menuselection:`Reporting --> Statements Reports --> Tax Report` and then filter by `Tax Report 103` or `Tax Report 104`." +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:659 +msgid "To get these reports, go to the **Accounting** app and select :menuselection:`Reporting --> Statements Reports --> Tax Report` and then filter by `Tax Report 103` or `Tax Report 104`." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:565 +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:663 msgid "Report 103" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:567 +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:665 msgid "This report contains information of income tax withholdings in a given period, this can be reported monthly or semi-annually." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:570 -#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:583 -msgid "You can see the information needed to report, which includes base and tax amounts, which also includes the tax code within the parenthesis in order to report it to the SRI." +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:668 +msgid "You can see the information needed to report, which includes base and tax amounts, but also includes the tax code within the parenthesis in order to report it to the SRI." msgstr "" #: ../../content/applications/finance/fiscal_localizations/ecuador.rst:-1 msgid "Report 103 form for Ecuador." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:578 +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:676 msgid "Report 104" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:580 +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:678 msgid "This report contains information on VAT tax and VAT withholding for a given period, this can be monthly or semi-annually." msgstr "" +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:681 +msgid "You can see the information needed to report, which includes base and tax amounts, but also includes the tax code within the parenthesis to report it to the SRI." +msgstr "" + #: ../../content/applications/finance/fiscal_localizations/ecuador.rst:-1 msgid "Report 104 form for Ecuador." msgstr "" +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:691 +msgid "ATS report" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:693 +msgid ":ref:`Install ` the *ATS Report* (`l10n_ec_reports_ats`) module to enable downloading the ATS report in XML format." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:697 +msgid "The Ecuadorian *ATS Report* module depends on the previous installation of the *Accounting* app and the *Ecuadorian EDI module*." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:703 +msgid "To issue electronic documents, ensure your company is configured as explained in the :ref:`electronic invoice ` section." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:706 +msgid "In the :abbr:`ATS (Anexo Transaccional Simplificado)`, every document generated in Odoo (invoices, vendor bills, sales and purchases withholdings, credit notes, and debit notes) will be included." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:712 +msgid "When generating a vendor bill, it is necessary to register the authorization number from the invoice that the vendor generated for the purchase. To do so, go to :menuselection:`Accounting --> Vendors --> Bills` and select the bill. Then, enter the number from the vendor's invoice in the :guilabel:`Authorization Number` field." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:718 +msgid "Credit and debit notes" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:720 +msgid "When generating a credit note or debit note manually or through importation, it is necessary to link this note to the sales invoice that is being modified by it." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:724 +msgid "Remember to add all required information to the documents before downloading the :abbr:`ATS (Anexo Transaccional Simplificado)` file. For example, add the *Authorization Number* and the *SRI Payment Method* on documents, when needed." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:729 +msgid "XML generation" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:731 +msgid "To generate the :abbr:`ATS (Anexo Transaccional Simplificado)` report, go to :menuselection:`Accounting --> Reports --> Tax Report` and choose a time period for the desired :abbr:`ATS (Anexo Transaccional Simplificado)` report, then click :guilabel:`ATS`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:735 +msgid "The downloaded XML file is ready to be uploaded to *DIMM Formularios*." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:-1 +msgid "ATS report download for Ecuador in Odoo Accounting." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/ecuador.rst:742 +msgid "When downloading the :abbr:`ATS (Anexo Transaccional Simplificado)` report, Odoo generates a warning pop-up alerting the user if a document(s) has missing or incorrect data. Nevertheless, the user can still download the XML file." +msgstr "" + #: ../../content/applications/finance/fiscal_localizations/egypt.rst:3 msgid "Egypt" msgstr "" @@ -23036,10 +23386,6 @@ msgstr "" msgid "If the UoM code of the :guilabel:`Tariff Fraction` is `06`, the correct :guilabel:`UMT Aduana` is `Units`." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/mexico.rst:725 -msgid "Invoicing flow" -msgstr "" - #: ../../content/applications/finance/fiscal_localizations/mexico.rst:727 msgid "Before creating an invoice, it is important to take into account that external trade invoices require to convert the amounts of your product into USD. Therefore, :doc:`multicurrency <../accounting/get_started/multi_currency>` **must** be enabled and *USD* **must** be activated in the :guilabel:`Currencies` section. The correct :guilabel:`Service` to run is :guilabel:`Mexican Bank`." msgstr "" @@ -24602,11 +24948,11 @@ msgid ":ref:`Install ` the :guilabel:`🇵🇭 Philippines` :re msgstr "" #: ../../content/applications/finance/fiscal_localizations/philippines.rst:14 -msgid "When creating a new database and `Philippines` is selected as a country, the fiscal localization module **Philippines - Accounting** is automatically installed." +msgid "When creating a new database and selecting the `Philippines` as a country, the fiscal localization module **Philippines - Accounting** is automatically installed." msgstr "" #: ../../content/applications/finance/fiscal_localizations/philippines.rst:16 -msgid "If installing the module in an existing company, the **chart of accounts** and **taxes** will *not* be replaced if there are already posted journal entries." +msgid "If the module is installed in an existing company, the **chart of accounts** and **taxes** will *not* be replaced if there are already posted journal entries." msgstr "" #: ../../content/applications/finance/fiscal_localizations/philippines.rst:18 @@ -24619,46 +24965,54 @@ msgid "Chart of accounts and taxes" msgstr "" #: ../../content/applications/finance/fiscal_localizations/philippines.rst:23 -msgid "A minimum configuration default chart of accounts is installed, and the following types of taxes are installed and also linked to the relevant account:" +msgid "A minimum configuration default chart of accounts is installed, and the following types of taxes are installed and linked to the relevant account:" msgstr "" #: ../../content/applications/finance/fiscal_localizations/philippines.rst:26 -msgid "VAT 12%" +msgid "Sales and Purchase VAT 12%" msgstr "" #: ../../content/applications/finance/fiscal_localizations/philippines.rst:27 -msgid "VAT Exempt" +msgid "Sales and Purchase VAT Exempt" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/philippines.rst:30 -msgid "For the withholding taxes, there is an additional :guilabel:`Philippines ATC` field under the :guilabel:`Philippines` tab." +#: ../../content/applications/finance/fiscal_localizations/philippines.rst:28 +msgid "Sales and Purchase VAT Zero-Rated" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/philippines.rst:29 +msgid "Purchase Withholding" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/philippines.rst:31 +msgid "For the withholding taxes (:menuselection:`Configuration --> Taxes`), there is an additional :guilabel:`Philippines ATC` field under the :guilabel:`Philippines` tab." msgstr "" #: ../../content/applications/finance/fiscal_localizations/philippines.rst:-1 msgid "Philippines ATC code field set on taxes." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/philippines.rst:36 +#: ../../content/applications/finance/fiscal_localizations/philippines.rst:38 msgid "Taxes' ATC codes are used for the BIR 2307 report. If a tax is created manually, its ATC code must be added." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/philippines.rst:42 +#: ../../content/applications/finance/fiscal_localizations/philippines.rst:44 msgid "When a company or an individual (not belonging to a company) contact is located in the Philippines, fill in the :guilabel:`Tax ID` field with their `Taxpayer Identification Number (TIN)`." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/philippines.rst:45 +#: ../../content/applications/finance/fiscal_localizations/philippines.rst:47 msgid "For individuals not belonging to a company, identify them by using the following additional fields:" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/philippines.rst:47 +#: ../../content/applications/finance/fiscal_localizations/philippines.rst:49 msgid ":guilabel:`First Name`" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/philippines.rst:48 +#: ../../content/applications/finance/fiscal_localizations/philippines.rst:50 msgid ":guilabel:`Middle Name`" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/philippines.rst:49 +#: ../../content/applications/finance/fiscal_localizations/philippines.rst:51 msgid ":guilabel:`Last Name`" msgstr "" @@ -24666,19 +25020,19 @@ msgstr "" msgid "Individual type contact with First, Middle, and Last Name fields." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/philippines.rst:55 +#: ../../content/applications/finance/fiscal_localizations/philippines.rst:57 msgid "For both :guilabel:`Company` and :guilabel:`Individual`, the TIN should follow the `NNN-NNN-NNN-NNNNN` format. The branch code should follow the last digits of the TIN, or else it can be left as `00000`." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/philippines.rst:60 +#: ../../content/applications/finance/fiscal_localizations/philippines.rst:62 msgid "BIR 2307 report" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/philippines.rst:62 -msgid "**BIR 2307** report data, also known as *Certificate of Creditable Tax Withheld at Source*, can be generated for purchase orders and vendor payments with the applicable withholding taxes." +#: ../../content/applications/finance/fiscal_localizations/philippines.rst:64 +msgid "**BIR 2307** report data, also known as `Certificate of Creditable Tax Withheld at Source `_, can be generated for purchase orders and vendor payments with the applicable withholding taxes." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/philippines.rst:65 +#: ../../content/applications/finance/fiscal_localizations/philippines.rst:68 msgid "To generate a BIR 2307 report, select one or multiple vendor bills from the list view, and click :menuselection:`Action --> Download BIR 2307 XLS`." msgstr "" @@ -24686,11 +25040,11 @@ msgstr "" msgid "Multiple vendor bills selected with action to \"Download BIR 2307 XLS\"." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/philippines.rst:71 +#: ../../content/applications/finance/fiscal_localizations/philippines.rst:75 msgid "The same action can be performed on a vendor bill from the form view." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/philippines.rst:73 +#: ../../content/applications/finance/fiscal_localizations/philippines.rst:77 msgid "A pop-up appears to review the selection, then click on :guilabel:`Generate`." msgstr "" @@ -24698,24 +25052,89 @@ msgstr "" msgid "Pop up menu to generate BIR 2307 XLS file." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/philippines.rst:78 +#: ../../content/applications/finance/fiscal_localizations/philippines.rst:82 msgid "This generates the `Form_2307.xls` file that lists all the vendor bill lines with the applicable withholding tax." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/philippines.rst:81 -msgid "The same process above can also be done for a *single* vendor :doc:`payment <../accounting/payments>` if they were linked to one or more :doc:`vendor bills <../accounting/payments>` with applied withholding taxes." +#: ../../content/applications/finance/fiscal_localizations/philippines.rst:85 +msgid "The process above can also be used for a *single* vendor :doc:`payment <../accounting/payments>` if it is linked to one or more :doc:`vendor bills <../accounting/payments>` with applied withholding taxes." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/philippines.rst:86 -msgid "If there is no withholding tax applied, then the XLS file will not generate records for those vendor bill lines." +#: ../../content/applications/finance/fiscal_localizations/philippines.rst:90 +msgid "If no withholding tax is applied, then the XLS file will not generate records for those vendor bill lines." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/philippines.rst:88 -msgid "When grouping payments for multiple bills, Odoo splits the payments based on the contact. From a payment, clicking :menuselection:`Action --> Download BIR 2307 XLS`, generates a report that only includes vendor bills related to that contact." +#: ../../content/applications/finance/fiscal_localizations/philippines.rst:92 +msgid "When grouping payments for multiple bills, Odoo splits the payments based on the contact. From a payment, clicking :menuselection:`Action --> Download BIR 2307 XLS` generates a report that only includes vendor bills related to that contact." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/philippines.rst:93 -msgid "Odoo cannot generate the BIR 2307 PDF report or DAT files directly. The generated `Form_2307.xls` file can be exported to an *external* tool to convert it to BIR DAT or PDF format." +#: ../../content/applications/finance/fiscal_localizations/philippines.rst:97 +msgid "Odoo cannot generate the BIR 2307 PDF report or DAT files directly. The generated :file:`Form_2307.xls` file can be exported to an *external* tool to convert it to BIR DAT or PDF format." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/philippines.rst:102 +#: ../../content/applications/finance/fiscal_localizations/philippines.rst:-1 +msgid "SLSP Report" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/philippines.rst:104 +msgid "The **SLSP** report, also known as the *Summary List of Sales and Purchases*, can be viewed and exported (in XLSX format). The report can be viewed from :menuselection:`Reporting --> Partner Reports --> Summary List of Sales and Purchases`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/philippines.rst:108 +msgid "The report is split into two sections, which can be accessed from their respective buttons at the top:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/philippines.rst:0 +msgid ":guilabel:`Sales` for :abbr:`SLS (Summary List of Sales)` report" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/philippines.rst:0 +msgid "All customer invoices with the associated sales taxes applied are shown in this report." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/philippines.rst:0 +msgid ":guilabel:`Purchases` for :abbr:`SLP (Summary List of Purchases)` report" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/philippines.rst:0 +msgid "All vendor bills with the associated purchase taxes applied are shown in this report." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/philippines.rst:119 +msgid "By default, both reports exclude journal entries containing partners without a TIN number set and those with importation taxes set. To view or hide them, the :guilabel:`Options:` button gives additional filters to include these, among others:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/philippines.rst:123 +msgid "`Including Partners Without TIN`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/philippines.rst:124 +msgid "`Including Importations`" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/philippines.rst:127 +msgid "Odoo cannot generate the DAT files directly. The :guilabel:`Export SLSP` and :guilabel:`XLSX` buttons export an XLSX file, which can be processed using an *external* tool to convert to the DAT format." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/philippines.rst:132 +msgid "2550Q Tax report" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/philippines.rst:134 +msgid "The tax report report is accessible by navigating to :menuselection:`Reporting --> Statement Reports --> Tax Report --> 2550Q(PH)`. The form is based on the latest *2550Q (Quarterly Value-Added Tax Return)* Jan. 2023 version." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/philippines.rst:-1 +msgid "2550Q Tax Report" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/philippines.rst:142 +msgid "Most lines in the tax report are automatically computed based on the taxes. For more accurate reporting and filing of the tax report, manual journal entries can also be mapped to the tax report through preconfigured **Tax Grids** for each tax report line." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/philippines.rst:147 +msgid "Odoo cannot generate the 2550Q BIR formatted PDF report directly. It should be used as a reference when externally filing the form manually or online." msgstr "" #: ../../content/applications/finance/fiscal_localizations/romania.rst:3 @@ -26246,34 +26665,38 @@ msgid "Import your obligations HMRC, filter on the period you want to submit, an msgstr "" #: ../../content/applications/finance/fiscal_localizations/united_kingdom.rst:100 -msgid "Periodic submission to HMRC for multi-company" -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/united_kingdom.rst:102 -msgid "Only one company and one user can connect to HMRC simultaneously. If several UK-based companies are on the same database, the user who submits the HMRC report must follow these instructions before each submission:" -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/united_kingdom.rst:106 -msgid "Log into the company for which the submission has to be done." +msgid "You can use dummy credentials to demo the HMRC flow. To do so, activate the :ref:`developer mode ` and go to :menuselection:`General Settings --> Technical --> System Parameters`. From here, search for `l10n_uk_reports.hmrc_mode` and change the value line to `demo`. You can get such credentials from the `HMRC Developer Hub `_." msgstr "" #: ../../content/applications/finance/fiscal_localizations/united_kingdom.rst:107 -msgid "Go to :guilabel:`General Settings`, and in the :guilabel:`Users` section, click :guilabel:`Manage Users`. Select the user who is connected to HMRC." +msgid "Periodic submission to HMRC for multi-company" msgstr "" #: ../../content/applications/finance/fiscal_localizations/united_kingdom.rst:109 -msgid "Go to the :guilabel:`UK HMRC Integration` tab and click :guilabel:`Reset Authentication Credentials` or :guilabel:`Remove Authentication Credentials` button." -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/united_kingdom.rst:111 -msgid "You can now :ref:`register your company to HMRC ` and submit the tax report for this company." +msgid "Only one company and one user can connect to HMRC simultaneously. If several UK-based companies are on the same database, the user who submits the HMRC report must follow these instructions before each submission:" msgstr "" #: ../../content/applications/finance/fiscal_localizations/united_kingdom.rst:113 -msgid "Repeat the steps for other companies' HMRC submissions." +msgid "Log into the company for which the submission has to be done." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/united_kingdom.rst:114 +msgid "Go to :guilabel:`General Settings`, and in the :guilabel:`Users` section, click :guilabel:`Manage Users`. Select the user who is connected to HMRC." msgstr "" #: ../../content/applications/finance/fiscal_localizations/united_kingdom.rst:116 +msgid "Go to the :guilabel:`UK HMRC Integration` tab and click :guilabel:`Reset Authentication Credentials` or :guilabel:`Remove Authentication Credentials` button." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/united_kingdom.rst:118 +msgid "You can now :ref:`register your company to HMRC ` and submit the tax report for this company." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/united_kingdom.rst:120 +msgid "Repeat the steps for other companies' HMRC submissions." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/united_kingdom.rst:123 msgid "During this process, the :guilabel:`Connect to HMRC` button no longer appears for other UK-based companies." msgstr "" @@ -26505,7 +26928,7 @@ msgid "Select the provider and configure the :guilabel:`Credentials` tab." msgstr "" #: ../../content/applications/finance/payment_providers.rst:193 -#: ../../content/applications/finance/payment_providers/stripe.rst:33 +#: ../../content/applications/finance/payment_providers/stripe.rst:37 msgid "Set the :guilabel:`State` field to :guilabel:`Enabled`." msgstr "" @@ -26533,10 +26956,6 @@ msgstr "" msgid "We recommend using the test mode on a duplicate or a test database to avoid potential issues with your invoice numbering." msgstr "" -#: ../../content/applications/finance/payment_providers.rst:224 -msgid "Payment methods" -msgstr "" - #: ../../content/applications/finance/payment_providers.rst:226 msgid "Each payment provider is related to a list of supported payment methods; the methods listed in the :guilabel:`Payment methods` field in the :guilabel:`Configuration` tab of the payment provider form are the ones that have been activated. To activate or deactivate a payment method for a provider, click :guilabel:`Enable Payment Methods`, then click the toggle button of the related method." msgstr "" @@ -26841,7 +27260,7 @@ msgstr "" #: ../../content/applications/finance/payment_providers/paypal.rst:121 #: ../../content/applications/finance/payment_providers/razorpay.rst:54 #: ../../content/applications/finance/payment_providers/sips.rst:32 -#: ../../content/applications/finance/payment_providers/stripe.rst:114 +#: ../../content/applications/finance/payment_providers/stripe.rst:118 #: ../../content/applications/finance/payment_providers/xendit.rst:47 msgid ":doc:`../payment_providers`" msgstr "" @@ -27994,149 +28413,157 @@ msgid "`Stripe `_ is a United States-based online payment s msgstr "" #: ../../content/applications/finance/payment_providers/stripe.rst:9 +msgid "`List of countries supported by Stripe `_" +msgstr "" + +#: ../../content/applications/finance/payment_providers/stripe.rst:10 +msgid "`List of payment methods supported by Stripe `_" +msgstr "" + +#: ../../content/applications/finance/payment_providers/stripe.rst:13 msgid "Create your Stripe account with Odoo" msgstr "" -#: ../../content/applications/finance/payment_providers/stripe.rst:11 +#: ../../content/applications/finance/payment_providers/stripe.rst:15 msgid "The method to acquire your credentials depends on your hosting type:" msgstr "" -#: ../../content/applications/finance/payment_providers/stripe.rst:16 -#: ../../content/applications/finance/payment_providers/stripe.rst:25 +#: ../../content/applications/finance/payment_providers/stripe.rst:20 +#: ../../content/applications/finance/payment_providers/stripe.rst:29 msgid ":ref:`Navigate to the payment provider Stripe ` and click :guilabel:`Connect Stripe`." msgstr "" -#: ../../content/applications/finance/payment_providers/stripe.rst:18 -#: ../../content/applications/finance/payment_providers/stripe.rst:27 +#: ../../content/applications/finance/payment_providers/stripe.rst:22 +#: ../../content/applications/finance/payment_providers/stripe.rst:31 msgid "Go through the setup process and confirm your email address when Stripe sends you a confirmation email." msgstr "" -#: ../../content/applications/finance/payment_providers/stripe.rst:20 +#: ../../content/applications/finance/payment_providers/stripe.rst:24 msgid "At the end of the process, click :guilabel:`Agree and submit`. If all requested information has been submitted, you are then redirected to Odoo, and your payment provider is enabled." msgstr "" -#: ../../content/applications/finance/payment_providers/stripe.rst:23 +#: ../../content/applications/finance/payment_providers/stripe.rst:27 msgid "Odoo.sh or On-premise" msgstr "" -#: ../../content/applications/finance/payment_providers/stripe.rst:29 +#: ../../content/applications/finance/payment_providers/stripe.rst:33 msgid "At the end of the process, click :guilabel:`Agree and submit`; you are then redirected to the payment provider **Stripe** in Odoo." msgstr "" -#: ../../content/applications/finance/payment_providers/stripe.rst:31 +#: ../../content/applications/finance/payment_providers/stripe.rst:35 msgid ":ref:`Fill in your credentials `." msgstr "" -#: ../../content/applications/finance/payment_providers/stripe.rst:32 +#: ../../content/applications/finance/payment_providers/stripe.rst:36 msgid ":ref:`Generate a webhook `." msgstr "" -#: ../../content/applications/finance/payment_providers/stripe.rst:36 +#: ../../content/applications/finance/payment_providers/stripe.rst:40 msgid "To use an existing Stripe account, :ref:`activate the Developer mode ` and :ref:`enable Stripe manually `. You can then :ref:`Fill in your credentials `, :ref:`generate a webhook `, and enable the payment provider." msgstr "" -#: ../../content/applications/finance/payment_providers/stripe.rst:40 +#: ../../content/applications/finance/payment_providers/stripe.rst:44 msgid "You can also test Stripe using the :ref:`payment_providers/test-mode`. To do so, first, `log into your Stripe dashboard `_ and switch to the **Test mode**. Then, in Odoo, :ref:`activate the Developer mode `, :ref:`navigate to the payment provider Stripe `, :ref:`fill in your API credentials ` with the test keys, and set the :guilabel:`State` field to :guilabel:`Test Mode`." msgstr "" -#: ../../content/applications/finance/payment_providers/stripe.rst:50 +#: ../../content/applications/finance/payment_providers/stripe.rst:54 msgid "Fill in your credentials" msgstr "" -#: ../../content/applications/finance/payment_providers/stripe.rst:52 +#: ../../content/applications/finance/payment_providers/stripe.rst:56 msgid "If your **API credentials** are required to connect with your Stripe account, proceed as follows:" msgstr "" -#: ../../content/applications/finance/payment_providers/stripe.rst:54 +#: ../../content/applications/finance/payment_providers/stripe.rst:58 msgid "Go to `the API keys page on Stripe `_, or log into your Stripe dashboard and go to :menuselection:`Developers --> API Keys`." msgstr "" -#: ../../content/applications/finance/payment_providers/stripe.rst:56 +#: ../../content/applications/finance/payment_providers/stripe.rst:60 msgid "In the :guilabel:`Standard keys` section, copy the :guilabel:`Publishable key` and the :guilabel:`Secret key` and save them for later." msgstr "" -#: ../../content/applications/finance/payment_providers/stripe.rst:58 -#: ../../content/applications/finance/payment_providers/stripe.rst:97 +#: ../../content/applications/finance/payment_providers/stripe.rst:62 +#: ../../content/applications/finance/payment_providers/stripe.rst:101 msgid "In Odoo, :ref:`navigate to the payment provider Stripe `." msgstr "" -#: ../../content/applications/finance/payment_providers/stripe.rst:59 +#: ../../content/applications/finance/payment_providers/stripe.rst:63 msgid "In the :guilabel:`Credentials` tab, fill in the :guilabel:`Publishable Key` and :guilabel:`Secret Key` fields with the values you previously saved." msgstr "" -#: ../../content/applications/finance/payment_providers/stripe.rst:65 +#: ../../content/applications/finance/payment_providers/stripe.rst:69 msgid "Generate a webhook" msgstr "" -#: ../../content/applications/finance/payment_providers/stripe.rst:67 +#: ../../content/applications/finance/payment_providers/stripe.rst:71 msgid "If your **Webhook Signing Secret** is required to connect with your Stripe account, you can create a webhook automatically or manually." msgstr "" -#: ../../content/applications/finance/payment_providers/stripe.rst:71 +#: ../../content/applications/finance/payment_providers/stripe.rst:75 msgid "Create the webhook automatically" msgstr "" -#: ../../content/applications/finance/payment_providers/stripe.rst:73 +#: ../../content/applications/finance/payment_providers/stripe.rst:77 msgid "Make sure your :ref:`Publishable and Secret keys ` are filled in, then click :guilabel:`Generate your webhook`." msgstr "" -#: ../../content/applications/finance/payment_providers/stripe.rst:76 +#: ../../content/applications/finance/payment_providers/stripe.rst:80 msgid "Create the webhook manually" msgstr "" -#: ../../content/applications/finance/payment_providers/stripe.rst:78 +#: ../../content/applications/finance/payment_providers/stripe.rst:82 msgid "Go to the `Webhooks page on Stripe `_, or log into your Stripe dashboard and go to :menuselection:`Developers --> Webhooks`." msgstr "" -#: ../../content/applications/finance/payment_providers/stripe.rst:80 +#: ../../content/applications/finance/payment_providers/stripe.rst:84 msgid "In the :guilabel:`Hosted endpoints` section, click :guilabel:`Add endpoint`. Then, in the :guilabel:`Endpoint URL` field, enter your Odoo database's URL, followed by `/payment/stripe/webhook`, e.g., `https://yourcompany.odoo.com/payment/stripe/webhook`." msgstr "" -#: ../../content/applications/finance/payment_providers/stripe.rst:83 +#: ../../content/applications/finance/payment_providers/stripe.rst:87 msgid "Click :guilabel:`Select events` at the bottom of the form, then select the following events:" msgstr "" -#: ../../content/applications/finance/payment_providers/stripe.rst:86 +#: ../../content/applications/finance/payment_providers/stripe.rst:90 msgid "in the :guilabel:`Charge` section: :guilabel:`charge.refunded` and :guilabel:`charge.refund.updated`;" msgstr "" -#: ../../content/applications/finance/payment_providers/stripe.rst:88 +#: ../../content/applications/finance/payment_providers/stripe.rst:92 msgid "in the :guilabel:`Payment intent` section: :guilabel:`payment_intent.amount_capturable_updated`, :guilabel:`payment_intent.payment_failed`, :guilabel:`payment_intent.processing`, and :guilabel:`payment_intent.succeeded`;" msgstr "" -#: ../../content/applications/finance/payment_providers/stripe.rst:92 +#: ../../content/applications/finance/payment_providers/stripe.rst:96 msgid "in the :guilabel:`Setup intent` section: :guilabel:`setup_intent.succeeded`." msgstr "" -#: ../../content/applications/finance/payment_providers/stripe.rst:94 +#: ../../content/applications/finance/payment_providers/stripe.rst:98 msgid "Click :guilabel:`Add events`." msgstr "" -#: ../../content/applications/finance/payment_providers/stripe.rst:95 +#: ../../content/applications/finance/payment_providers/stripe.rst:99 msgid "Click :guilabel:`Add endpoint`, then click :guilabel:`Reveal` and save your :guilabel:`Signing secret` for later." msgstr "" -#: ../../content/applications/finance/payment_providers/stripe.rst:99 +#: ../../content/applications/finance/payment_providers/stripe.rst:103 msgid "In the :guilabel:`Credentials` tab, fill the :guilabel:`Webhook Signing Secret` field with the value you previously saved." msgstr "" -#: ../../content/applications/finance/payment_providers/stripe.rst:103 +#: ../../content/applications/finance/payment_providers/stripe.rst:107 msgid "You can select other events, but they are currently not processed by Odoo." msgstr "" -#: ../../content/applications/finance/payment_providers/stripe.rst:106 +#: ../../content/applications/finance/payment_providers/stripe.rst:110 msgid "Enable Apple Pay" msgstr "" -#: ../../content/applications/finance/payment_providers/stripe.rst:108 +#: ../../content/applications/finance/payment_providers/stripe.rst:112 msgid "To allow customers to use the Apple Pay button to pay their eCommerce orders, go to the :guilabel:`Configuration` tab, enable :guilabel:`Allow Express Checkout`, and click :guilabel:`Enable Apple Pay`." msgstr "" -#: ../../content/applications/finance/payment_providers/stripe.rst:113 +#: ../../content/applications/finance/payment_providers/stripe.rst:117 msgid ":ref:`Express checkout and Google Pay `" msgstr "" -#: ../../content/applications/finance/payment_providers/stripe.rst:115 +#: ../../content/applications/finance/payment_providers/stripe.rst:119 msgid ":doc:`Use Stripe as a payment terminal in Point of Sale <../../sales/point_of_sale/payment_methods/terminals/stripe>`" msgstr "" diff --git a/locale/sources/general.pot b/locale/sources/general.pot index d5fe7ea05..fcdf1d862 100644 --- a/locale/sources/general.pot +++ b/locale/sources/general.pot @@ -8,7 +8,7 @@ msgid "" msgstr "" "Project-Id-Version: Odoo 17.0\n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2024-03-25 16:01+0000\n" +"POT-Creation-Date: 2024-04-30 09:16+0000\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME \n" "Language-Team: LANGUAGE \n" @@ -117,192 +117,310 @@ msgid "Companies" msgstr "" #: ../../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." +msgid "A centralized management environment allows an administrator to select multiple companies simultaneously, and set their specific warehouses, customers, equipment, and contacts. It provides the ability to generate reports of aggregated figures without switching interfaces, which facilitates daily tasks, and enhances the overall management process." msgstr "" -#: ../../content/applications/general/companies.rst:15 -msgid "Manage companies and records" +#: ../../content/applications/general/companies.rst:13 +msgid "Utilizing a multi-company environment in an Odoo database warrants a subscription change from *Standard* (or *One App Free*) to a *Custom* plan. Should the administrator not migrate the subscription to a *Custom* plan after adding another company, the database risks being deactivated. For more information, consult the `Odoo Pricing page `_." msgstr "" -#: ../../content/applications/general/companies.rst:17 -msgid "Go to :menuselection:`Settings --> Manage Companies` and fill in the form with your company’s information. If a *Parent Company* is selected, records are shared between the two companies (as long as both environments are active)." +#: ../../content/applications/general/companies.rst:19 +msgid "If the customer is on the *Standard* plan, and adds multi-company functionality to the database, it triggers an upsell for the *Custom* plan." msgstr "" -#: ../../content/applications/general/companies.rst:-1 -msgid "Overview of a new company's form in Odoo" +#: ../../content/applications/general/companies.rst:22 +msgid "If they are on a *Yearly* or *Multi-year* contract, this creates an upsell order, with a 30-day limit (risking deactivation). If multi-company functionality is fully removed within that time period, the next time the database pings, the upsell order and limit are removed automatically." msgstr "" #: ../../content/applications/general/companies.rst:26 -msgid "Activate the :ref:`developer mode ` to choose a *Favicon* for each of your companies, and easily identify them by the browser tabs. Set your favicons’ files size to 16x16 or 32x32 pixels. JPG, PNG, GIF, and ICO are extensions accepted." +msgid "If the customer is on a *Monthly* contract, once the next bill is created, and multi-company functionality is still detected while they are on a *Standard* plan, they are automatically switched, and billed on the *Custom* plan." msgstr "" -#: ../../content/applications/general/companies.rst:0 -msgid "View of a web browser and the favicon for a specific company chosen in Odoo" +#: ../../content/applications/general/companies.rst:30 +msgid "Should the customer want to go back to *Standard*, the Customer Success Team **must** be contacted." msgstr "" -#: ../../content/applications/general/companies.rst:35 -msgid "Switch between or select multiple companies by enabling their selection boxes to activate them. The grayed company is the one which environment is in use. To switch environments, click on the company’s name. In the example below, the user has access to three companies, two are activated, and the environment in use is of *JS Store US*." +#: ../../content/applications/general/companies.rst:33 +msgid "To create a new company, navigate to :menuselection:`Settings app --> Companies section`, and click :guilabel:`Manage Companies`. Then, click :guilabel:`New` to create a new company." msgstr "" -#: ../../content/applications/general/companies.rst:-1 -msgid "View of the companies menu through the main dashboard in Odoo" +#: ../../content/applications/general/companies.rst:36 +msgid "Proceed to fill out the new company form that appears." +msgstr "" + +#: ../../content/applications/general/companies.rst:39 +msgid "To archive a company, navigate to :menuselection:`Settings app --> Companies section --> Manage Companies`. Then, tick the checkbox to the left of the company to be archived. If the :guilabel:`Companies` page is not in list view, click the :guilabel:`≣ (four bars)` icon, located in the top-right corner of the page." msgstr "" #: ../../content/applications/general/companies.rst:44 -msgid "Data such as Products, Contacts, and Equipment can be shared or set to be shown for a specific company only. To do so, on their forms, choose between:" +msgid "After selecting the appropriate company, click the :guilabel:`⚙️ Actions` icon, and select :guilabel:`Archive` from the resulting drop-down menu." msgstr "" #: ../../content/applications/general/companies.rst:47 +msgid "To ensure all records related to the archived company are archived, contact Odoo's `Support Team `_." +msgstr "" + +#: ../../content/applications/general/companies.rst:50 +msgid "Should a record not be archived, there is a risk of reactivating the archived company, and creating the upsell again." +msgstr "" + +#: ../../content/applications/general/companies.rst:56 +msgid "Manage companies and records" +msgstr "" + +#: ../../content/applications/general/companies.rst:58 +msgid "Go to :menuselection:`Settings app --> Companies section --> Manage Companies`. Then, either click :guilabel:`New`, and fill in the form with the company's information, or select a pre-existing company to edit it." +msgstr "" + +#: ../../content/applications/general/companies.rst:-1 +msgid "Overview of a new company's form in Odoo." +msgstr "" + +#: ../../content/applications/general/companies.rst:67 +#: ../../content/applications/general/companies.rst:120 +msgid "Activate the :ref:`developer mode ` to set social media accounts and company-specific email system parameters. See this documentation on :doc:`../marketing/social_marketing` and :ref:`email_servers/outbound`." +msgstr "" + +#: ../../content/applications/general/companies.rst:71 +msgid "Companies also have a :guilabel:`Parent Company` set on the company form in :ref:`developer mode `." +msgstr "" + +#: ../../content/applications/general/companies.rst:75 +msgid "Switch between companies" +msgstr "" + +#: ../../content/applications/general/companies.rst:77 +msgid "Switch between (or select) multiple companies, by clicking on the company name, located in the far-right corner of the header menu, anywhere throughout the database. Tick the checkboxes next to the desired company name(s) to activate them. The highlighted company represents the current environment that is in use. To switch environments, click on the desired company name." +msgstr "" + +#: ../../content/applications/general/companies.rst:83 +msgid "In the example below, the user has access to eight companies, two are activated, and the environment the database is in belongs to: *My Company (San Francisco)*." +msgstr "" + +#: ../../content/applications/general/companies.rst:0 +msgid "View of the companies menu through the main dashboard in Odoo." +msgstr "" + +#: ../../content/applications/general/companies.rst:91 +msgid "Share records" +msgstr "" + +#: ../../content/applications/general/companies.rst:93 +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/companies.rst:96 msgid "*A blank field*: the record is shared within all companies." msgstr "" -#: ../../content/applications/general/companies.rst:48 +#: ../../content/applications/general/companies.rst:97 msgid "*Adding a company*: the record is visible to users logged in to that specific company." msgstr "" #: ../../content/applications/general/companies.rst:-1 -msgid "View of a product's form emphasizing the company field in Odoo Sales" +msgid "View of a product's form emphasizing the company field in Odoo Sales." msgstr "" -#: ../../content/applications/general/companies.rst:55 -msgid "Employees' access" +#: ../../content/applications/general/companies.rst:103 +msgid "When an environment is selected from the top menu, along with an additional company, records are shared between the two companies." msgstr "" -#: ../../content/applications/general/companies.rst:57 -msgid "Once companies are created, manage your employees' :doc:`Access Rights ` for *Multi Companies*." +#: ../../content/applications/general/companies.rst:107 +msgid "Branches" +msgstr "" + +#: ../../content/applications/general/companies.rst:109 +msgid "Branches are available to add to a company. Branches can be added by navigating to :menuselection:`Settings app --> Companies section --> Manage Companies`. Then, select the desired company from the list. From the company detail form, open the :guilabel:`Branches` tab. To add a branch, click :guilabel:`Add a line`, and fill out the :guilabel:`Create Branches` pop-up form that appears." +msgstr "" + +#: ../../content/applications/general/companies.rst:-1 +msgid "Add a branch to a company with branches and add a line highlighted." +msgstr "" + +#: ../../content/applications/general/companies.rst:124 +msgid "Branches also have a :guilabel:`Parent Company` set on the branch form in :ref:`developer mode `. Accounting and fiscal localizations for the branch are set on the :guilabel:`Parent Company`. To do so, select the company from the *company selector* in the top menu, and go to :menuselection:`Settings app --> Accounting --> Fiscal Localization`." +msgstr "" + +#: ../../content/applications/general/companies.rst:130 +msgid "Adding a branch to a company triggers an upsell, should the database be in the *Standard* or *One App Free* pricing plans. Adding one or more branches constitutes a multi-company database, and needs to be moved to the *Custom* pricing plan." +msgstr "" + +#: ../../content/applications/general/companies.rst:134 +msgid "For more information on pricing, see `Odoo's pricing `_ page." +msgstr "" + +#: ../../content/applications/general/companies.rst:137 +msgid "Employee access" +msgstr "" + +#: ../../content/applications/general/companies.rst:139 +msgid "Once companies are created, manage the employees' :doc:`Access Rights ` for *Multi Companies*." +msgstr "" + +#: ../../content/applications/general/companies.rst:142 +msgid "To access the *Access Rights*, navigate to :menuselection:`Settings app --> Users section --> Manage Users`." +msgstr "" + +#: ../../content/applications/general/companies.rst:145 +msgid "From the :guilabel:`Users` page, select a user from the list to modify. Then, either change the fields for :guilabel:`Allowed Companies` or :guilabel:`Default Company`." +msgstr "" + +#: ../../content/applications/general/companies.rst:148 +msgid "Multiple companies can be set for :guilabel:`Allowed Companies`, and *only one* can be set as the :guilabel:`Default Company`." msgstr "" #: ../../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" +"in Odoo." msgstr "" -#: ../../content/applications/general/companies.rst:66 -msgid "If a user has multiple companies *activated* on his database, and he is **editing** a record, the editing happens on the record's related company." +#: ../../content/applications/general/companies.rst:156 +msgid "If an administrator has multiple companies activated on the database, and is editing a record, the editing occurs on the record's related company." msgstr "" -#: ../../content/applications/general/companies.rst:69 -msgid "Example: if editing a sale order issued under JS Store US while working on the JS Store Belgium environment, the changes are applied under JS Store US (the company from which the sale order was issued)." +#: ../../content/applications/general/companies.rst:160 +msgid "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/companies.rst:70 -msgid "When **creating** a record, the company taken into account is:" +#: ../../content/applications/general/companies.rst:164 +msgid "When creating a record, the company taken into account is:" msgstr "" -#: ../../content/applications/general/companies.rst:72 -msgid "The current company (the one active) or," +#: ../../content/applications/general/companies.rst:166 +msgid "The current company selected in the company selector, in the upper-right hand of the screen (the one that is highlighted/active)" msgstr "" -#: ../../content/applications/general/companies.rst:73 -msgid "No company is set (on products and contacts’ forms for example) or," +#: ../../content/applications/general/companies.rst:169 +#: ../../content/applications/general/companies.rst:173 +msgid "**OR**" msgstr "" -#: ../../content/applications/general/companies.rst:74 -msgid "The company set is the one linked to the document (the same as if a record is being edited)." +#: ../../content/applications/general/companies.rst:171 +msgid "No company is set (because none is set on the product and contact forms, for example)" msgstr "" -#: ../../content/applications/general/companies.rst:77 -msgid "Documents’ format" +#: ../../content/applications/general/companies.rst:175 +msgid "The company set is the company linked to the document (the same as if a record is being edited)" msgstr "" -#: ../../content/applications/general/companies.rst:79 -msgid "To set documents' formats according to each company, *activate* and *select* the respective one and, under *Settings*, click on *Configure Document Layout*." +#: ../../content/applications/general/companies.rst:178 +msgid "Document format" +msgstr "" + +#: ../../content/applications/general/companies.rst:180 +msgid "To set document formats according to each company, *activate* and *select* the respective company, and, under the :menuselection:`Settings app --> Companies section`, click on :guilabel:`Configure Document Layout` and edit the information as needed." msgstr "" #: ../../content/applications/general/companies.rst:-1 -msgid "View of the settings page emphasizing the document layout field in Odoo" +msgid "View of the settings page emphasizing the document layout field in Odoo." msgstr "" -#: ../../content/applications/general/companies.rst:87 -msgid "Inter-Company Transactions" +#: ../../content/applications/general/companies.rst:188 +msgid ":guilabel:`Company Details` can be edited on the document layout. By default, this field is populated from the company information listed, when navigating here: :menuselection:`Settings app --> Companies section --> Manage Companies`, and select a company from the list." msgstr "" -#: ../../content/applications/general/companies.rst:89 -msgid "First, make sure each one of your companies is properly set in relation to:" +#: ../../content/applications/general/companies.rst:193 +msgid "Inter-company transactions" msgstr "" -#: ../../content/applications/general/companies.rst:91 +#: ../../content/applications/general/companies.rst:195 +msgid "First, activate the :ref:`developer mode `. Then, make sure each one of the companies is properly set in relation to:" +msgstr "" + +#: ../../content/applications/general/companies.rst:198 msgid ":doc:`Chart of Accounts <../finance/accounting/get_started/chart_of_accounts>`" msgstr "" -#: ../../content/applications/general/companies.rst:92 +#: ../../content/applications/general/companies.rst:199 msgid ":doc:`Taxes <../finance/accounting/taxes>`" msgstr "" -#: ../../content/applications/general/companies.rst:93 +#: ../../content/applications/general/companies.rst:200 msgid ":doc:`Fiscal Positions <../finance/accounting/taxes/fiscal_positions>`" msgstr "" -#: ../../content/applications/general/companies.rst:94 +#: ../../content/applications/general/companies.rst:201 msgid ":doc:`Journals <../finance/accounting/bank>`" msgstr "" -#: ../../content/applications/general/companies.rst:95 +#: ../../content/applications/general/companies.rst:202 msgid ":doc:`Fiscal Localizations <../finance/fiscal_localizations>`" msgstr "" -#: ../../content/applications/general/companies.rst:96 +#: ../../content/applications/general/companies.rst:203 msgid ":doc:`Pricelists <../sales/sales/products_prices/prices/pricing>`" msgstr "" -#: ../../content/applications/general/companies.rst:98 -msgid "Now, activate the *Inter-Company Transactions* option under *Settings*. With the respective company *activated* and *selected*, choose if you would like operations between companies to be synchronized at an invoice/bills level or at a sales/purchase orders level." +#: ../../content/applications/general/companies.rst:205 +msgid "Next, navigate to :menuselection:`Settings app --> Companies section --> Manage Companies`. Then, select the desired company from the list. On the company form, select the :guilabel:`Inter-Company Transactions` tab, on the individual company's detail form." +msgstr "" + +#: ../../content/applications/general/companies.rst:209 +msgid "With the respective company activated and selected, choose one of the following :guilabel:`Rule` options:" +msgstr "" + +#: ../../content/applications/general/companies.rst:212 +msgid ":guilabel:`Do not synchronize`: do not synchronize any inter-company transactions." +msgstr "" + +#: ../../content/applications/general/companies.rst:213 +msgid ":guilabel:`Synchronized invoice/bills`: generates a bill/invoice when a company confirms a bill/invoice for the selected company." +msgstr "" + +#: ../../content/applications/general/companies.rst:215 +msgid ":guilabel:`Synchronize Sales Order`: generates a drafted sales order using the selected company warehouse, when a sales order is confirmed for the selected company. If, instead of a drafted sales order, it should be validated, enable :guilabel:`Automatic Validation`.\\*" +msgstr "" + +#: ../../content/applications/general/companies.rst:218 +msgid ":guilabel:`Synchronize Purchase Order`: generates a drafted purchase order using the selected company warehouse, when a purchase order is confirmed for the selected company. If, instead of a drafted purchase order, it should be validated, enable :guilabel:`Automatic Validation`.\\*" +msgstr "" + +#: ../../content/applications/general/companies.rst:221 +msgid ":guilabel:`Synchronize Sales and 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, it should be validated, enable :guilabel:`Automatic Validation`.\\*" +msgstr "" + +#: ../../content/applications/general/companies.rst:226 +msgid "\\* The given option needs to be selected, so :guilabel:`Automatic Validation` appears in the configuration." msgstr "" #: ../../content/applications/general/companies.rst:-1 -msgid "View of the settings page emphasizing the inter company transaction field in Odoo" +msgid "View of the settings page emphasizing the inter company transaction field in Odoo." msgstr "" -#: ../../content/applications/general/companies.rst:106 -msgid "**Synchronize invoice/bills**: generates a bill/invoice when a company confirms a bill/invoice for the selected company." +#: ../../content/applications/general/companies.rst:234 +msgid "Products **must** be configured as :guilabel:`Can be sold` and shared between the companies. See :doc:`../inventory_and_mrp/inventory/product_management/product_tracking/type`." msgstr "" -#: ../../content/applications/general/companies.rst:109 -msgid "*Example:* an invoice posted on JS Store Belgium, for JS Store US, automatically creates a vendor bill on the JS Store US, from the JS Store Belgium." +#: ../../content/applications/general/companies.rst:238 +msgid ":guilabel:`Synchronize invoice/bills`: an invoice posted on `JS Store Belgium`, for `JS Store US`, automatically creates a vendor bill, and 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, it should be validated, enable :guilabel:`Automatic Validation`." msgstr "" -#: ../../content/applications/general/companies.rst:-1 -msgid "View of an invoice for JS Store US created on JS Store Belgium in Odoo" +#: ../../content/applications/general/companies.rst:244 +msgid ":guilabel:`Synchronize sales/purchase order`: 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 :guilabel:`Automatic Validation` feature was enabled)." msgstr "" -#: ../../content/applications/general/companies.rst:116 -msgid "**Synchronize sales/purchase order**: generates a drafted purchase/sales order using the selected company warehouse when a sales/purchase order is confirmed for the selected company. If instead of a drafted purchase/sales order you rather have it validated, enable *Automatic Validation*." +#: ../../content/applications/general/companies.rst:249 +msgid "Remember to test all workflows as a user *other* than the administrator." msgstr "" -#: ../../content/applications/general/companies.rst:120 -msgid "*Example:* when a sale order for JS Store US is confirmed on JS Store Belgium, a purchase order on JS Store Belgium is automatically created (and confirmed if the *Automatic Validation* feature was enabled)." +#: ../../content/applications/general/companies.rst:252 +msgid ":doc:`Multi-company Guidelines <../../developer/howtos/company>`" msgstr "" -#: ../../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/companies.rst:129 -msgid "Products have to be configured as *Can be sold* and must be shared between the companies." -msgstr "" - -#: ../../content/applications/general/companies.rst:132 -msgid "Remember to test all workflows as an user other than the administrator." -msgstr "" - -#: ../../content/applications/general/companies.rst:135 -msgid ":doc:`Multi-company Guidelines `" -msgstr "" - -#: ../../content/applications/general/companies.rst:136 +#: ../../content/applications/general/companies.rst:253 msgid ":doc:`../finance/accounting/get_started/multi_currency`" msgstr "" #: ../../content/applications/general/companies/digest_emails.rst:3 -msgid "Digest Emails" +msgid "Digest emails" msgstr "" #: ../../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." +msgid "*Digest Emails* are periodic snapshots sent via email to users in an organization that include high-level information about how the business is performing." msgstr "" #: ../../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." +msgid "To start sending digest emails, begin by navigating to :menuselection:`Settings app --> Statistics section`, activate the :guilabel:`Digest Emails` feature, and click :guilabel:`Save`." msgstr "" #: ../../content/applications/general/companies/digest_emails.rst:-1 @@ -310,242 +428,447 @@ msgid "Digest Emails section inside General Settings." msgstr "" #: ../../content/applications/general/companies/digest_emails.rst:15 -msgid "You can control a variety of settings for your Digest Emails, such as:" +msgid "A variety of settings can be configured for digest emails, such as:" msgstr "" #: ../../content/applications/general/companies/digest_emails.rst:17 -msgid "which KPIs are shared in the Digest" +msgid "Deciding which :abbr:`KPIs (key performance indicators)` are shared in the digest emails" msgstr "" #: ../../content/applications/general/companies/digest_emails.rst:18 -msgid "how often Digest Emails are sent" +msgid "Determining how often digest emails are sent" msgstr "" #: ../../content/applications/general/companies/digest_emails.rst:19 -msgid "who in your organization receives Digest Emails" +msgid "Choosing who in the organization receives digest emails" msgstr "" #: ../../content/applications/general/companies/digest_emails.rst:20 -msgid "creating custom Digest Email templates" +msgid "Creating custom digest email templates" msgstr "" #: ../../content/applications/general/companies/digest_emails.rst:21 -msgid "adding additional KPIs (Studio required)" +msgid "Adding additional :abbr:`KPIs (key performance indicators)` (*Studio* app required)" msgstr "" #: ../../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." +msgid "By default, the :guilabel:`Digest Email` feature is enabled. :guilabel:`Your Odoo Periodic Digest` serves as the primary template, which includes all :abbr:`KPI (key performance indicator)` measurements across the Odoo database, and is sent daily to administrators." msgstr "" -#: ../../content/applications/general/companies/digest_emails.rst:31 -msgid "Customize *Your Odoo Periodic Digest*" +#: ../../content/applications/general/companies/digest_emails.rst:29 +msgid "When creating duplicates of databases that have sending capabilities (not testing-mode), the digest emails continue to send from the duplicate database, unless deactivated." msgstr "" -#: ../../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/companies/digest_emails.rst:37 -msgid "A popup window appears and presents a variety of editable settings, which include:" +#: ../../content/applications/general/companies/digest_emails.rst:32 +msgid "To deactivate the digest email, navigate to :menuselection:`Settings --> Statistics section`. Then, deactivate the :guilabel:`Digest Emails` feature, by un-ticking the checkbox, and clicking :guilabel:`Save`. See the section on :ref:`digest-emails/deactivate`." msgstr "" #: ../../content/applications/general/companies/digest_emails.rst:39 -msgid "**Digest Title** - what you want your Digest Email to be called" -msgstr "" - -#: ../../content/applications/general/companies/digest_emails.rst:40 -msgid "**Periodicity** - control the regimen in how often Digest Emails are sent" +msgid "Customize default digest email" msgstr "" #: ../../content/applications/general/companies/digest_emails.rst:41 -msgid "**KPIs** - check/uncheck each calculated KPI that appears in Digest Emails" +msgid "To customize the default digest email (*Your Odoo Periodic Digest*), go to :menuselection:`Settings app --> Statistics section --> Digest Email field`. Then, select :guilabel:`Your Odoo Periodic Digest`, and click on the :guilabel:`↗️ (External link)` icon, next to the drop-down menu selection." msgstr "" -#: ../../content/applications/general/companies/digest_emails.rst:42 -msgid "**Recipients** - add/remove users who receive your Digest Emails" +#: ../../content/applications/general/companies/digest_emails.rst:45 +msgid "A pop-up window appears, and presents a variety of editable settings, which include:" msgstr "" -#: ../../content/applications/general/companies/digest_emails.rst:43 -msgid "**Custom** - add your own KPIs (Studio required)" +#: ../../content/applications/general/companies/digest_emails.rst:47 +#: ../../content/applications/general/companies/digest_emails.rst:179 +msgid ":guilabel:`Digest Name`: the name of the digest email." +msgstr "" + +#: ../../content/applications/general/companies/digest_emails.rst:48 +#: ../../content/applications/general/companies/digest_emails.rst:180 +msgid ":guilabel:`Periodicity`: control how often digest emails are sent (:guilabel:`Daily`, :guilabel:`Weekly`, :guilabel:`Monthly`, or :guilabel:`Quarterly`)." +msgstr "" + +#: ../../content/applications/general/companies/digest_emails.rst:50 +#: ../../content/applications/general/companies/digest_emails.rst:182 +msgid ":guilabel:`Next Send Date`: the date on which the digest email will be sent again." +msgstr "" + +#: ../../content/applications/general/companies/digest_emails.rst:51 +#: ../../content/applications/general/companies/digest_emails.rst:183 +msgid ":guilabel:`KPIs` tab: check/uncheck each calculated :abbr:`KPI (key performance indicator)` that appears in digest emails. A ticked box indicates an active :abbr:`KPI (key performance indicator)` in the digest email. See the section on :ref:`digest-emails/kpis`." +msgstr "" + +#: ../../content/applications/general/companies/digest_emails.rst:54 +#: ../../content/applications/general/companies/digest_emails.rst:186 +msgid ":guilabel:`Recipients` tab: add/remove users who receive the digest emails. See the section on :ref:`digest-emails/recipients`." +msgstr "" + +#: ../../content/applications/general/companies/digest_emails.rst:58 +msgid "The :abbr:`KPIs (key performance indicators)` can be customized using Odoo *Studio*. Additional costs to the database subscription are incurred should *Studio* need to be installed. See this section on :ref:`digest-emails/custom-kpi`." msgstr "" #: ../../content/applications/general/companies/digest_emails.rst:-1 msgid "Customize default Digest Email settings and custom KPIs." msgstr "" -#: ../../content/applications/general/companies/digest_emails.rst:52 -msgid "Custom digest emails" +#: ../../content/applications/general/companies/digest_emails.rst:69 +msgid "Deactivate digest email" msgstr "" -#: ../../content/applications/general/companies/digest_emails.rst:54 -msgid "To do so, click on **Configure Digest Emails** and then **Create**." -msgstr "" - -#: ../../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/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/companies/digest_emails.rst:65 -msgid "Custom KPIs with Studio" -msgstr "" - -#: ../../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/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/companies/digest_emails.rst:73 -msgid "In order to create additional fields, you must create two fields on the digest object:" +#: ../../content/applications/general/companies/digest_emails.rst:71 +msgid "To manually deactivate an individual digest email, first navigate to :menuselection:`Settings app --> Statistics section`, and click :guilabel:`Configure Digest Emails`. Then, select the desired digest email from the list that should be deactivated." msgstr "" #: ../../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/companies/digest_emails.rst:76 -msgid "create a computed field called `kpi_myfield_value` that computes your customized KPI" -msgstr "" - -#: ../../content/applications/general/companies/digest_emails.rst:77 -msgid "select your KPI(s) in the KPIs tab." +msgid "Next, click :guilabel:`DEACTIVATE FOR EVERYONE` to deactivate the digest email for everyone, or :guilabel:`UNSUBSCRIBE ME` to remove the logged in user from the mailing list. These buttons are located in the top menu, just above the :guilabel:`Digest Name`." msgstr "" #: ../../content/applications/general/companies/digest_emails.rst:80 +msgid "Manually send digest email" +msgstr "" + +#: ../../content/applications/general/companies/digest_emails.rst:82 +msgid "To manually send a digest email, first navigate to :menuselection:`Settings app --> Statistics section`, and click :guilabel:`Configure Digest Emails`. Then, select the desired digest email, and click :guilabel:`SEND NOW`. This button is located in the top menu, just above the :guilabel:`Digest Name`." +msgstr "" + +#: ../../content/applications/general/companies/digest_emails.rst:90 +msgid "KPIs" +msgstr "" + +#: ../../content/applications/general/companies/digest_emails.rst:92 +msgid "Pre-configured :abbr:`KPIs (key performance indicators)` can be added to the digest email from the :guilabel:`KPIs` tab of the digest email template form." +msgstr "" + +#: ../../content/applications/general/companies/digest_emails.rst:95 +msgid "First, navigate to :menuselection:`Settings app --> Statistics section`, and click :guilabel:`Configure Digest Emails`." +msgstr "" + +#: ../../content/applications/general/companies/digest_emails.rst:98 +msgid "Then, select the desired digest email, and open the :guilabel:`KPIs` tab." +msgstr "" + +#: ../../content/applications/general/companies/digest_emails.rst:100 +msgid "To add a :abbr:`KPI (key performance indicator)` to the digest email, tick the checkbox next to the desired :abbr:`KPI (key performance indicator)`. After all :abbr:`KPIs (key performance indicators)` are added (or deselected), click :guilabel:`Save`." +msgstr "" + +#: ../../content/applications/general/companies/digest_emails.rst:104 +msgid "The following :abbr:`KPIs (key performance indicators)` are available in the :guilabel:`KPIs` tab on a digest email template form out-of-box in Odoo:" +msgstr "" + +#: ../../content/applications/general/companies/digest_emails.rst:-1 +msgid "KPIs listed in the out-of-box digest email." +msgstr "" + +#: ../../content/applications/general/companies/digest_emails.rst:113 +msgid ":guilabel:`General`" +msgstr "" + +#: ../../content/applications/general/companies/digest_emails.rst:112 +msgid ":guilabel:`Connected Users`" +msgstr "" + +#: ../../content/applications/general/companies/digest_emails.rst:113 +msgid ":guilabel:`Messages`" +msgstr "" + +#: ../../content/applications/general/companies/digest_emails.rst:116 +msgid ":guilabel:`Project`" +msgstr "" + +#: ../../content/applications/general/companies/digest_emails.rst:116 +msgid ":guilabel:`Open Tasks`" +msgstr "" + +#: ../../content/applications/general/companies/digest_emails.rst:119 +msgid ":guilabel:`Recruitment`" +msgstr "" + +#: ../../content/applications/general/companies/digest_emails.rst:119 +msgid ":guilabel:`Employees`" +msgstr "" + +#: ../../content/applications/general/companies/digest_emails.rst:123 +msgid ":guilabel:`CRM`" +msgstr "" + +#: ../../content/applications/general/companies/digest_emails.rst:122 +msgid ":guilabel:`New Leads/Opportunities`" +msgstr "" + +#: ../../content/applications/general/companies/digest_emails.rst:123 +msgid ":guilabel:`Opportunities Won`" +msgstr "" + +#: ../../content/applications/general/companies/digest_emails.rst:127 +msgid ":guilabel:`Sales`" +msgstr "" + +#: ../../content/applications/general/companies/digest_emails.rst:126 +msgid ":guilabel:`All Sales`" +msgstr "" + +#: ../../content/applications/general/companies/digest_emails.rst:127 +msgid ":guilabel:`eCommerce Sales`" +msgstr "" + +#: ../../content/applications/general/companies/digest_emails.rst:130 +msgid ":guilabel:`Point of Sale`" +msgstr "" + +#: ../../content/applications/general/companies/digest_emails.rst:130 +msgid ":guilabel:`POS Sales`" +msgstr "" + +#: ../../content/applications/general/companies/digest_emails.rst:135 +msgid ":guilabel:`Live Chat`" +msgstr "" + +#: ../../content/applications/general/companies/digest_emails.rst:133 +msgid ":guilabel:`% of Happiness`" +msgstr "" + +#: ../../content/applications/general/companies/digest_emails.rst:134 +msgid ":guilabel:`Conversations handled`" +msgstr "" + +#: ../../content/applications/general/companies/digest_emails.rst:135 +msgid ":guilabel:`Time to answer (sec)`" +msgstr "" + +#: ../../content/applications/general/companies/digest_emails.rst:138 +msgid ":guilabel:`Helpdesk`" +msgstr "" + +#: ../../content/applications/general/companies/digest_emails.rst:138 +msgid ":guilabel:`Tickets Closed`" +msgstr "" + +#: ../../content/applications/general/companies/digest_emails.rst:142 +msgid ":guilabel:`Invoicing`" +msgstr "" + +#: ../../content/applications/general/companies/digest_emails.rst:141 +msgid ":guilabel:`Revenue`" +msgstr "" + +#: ../../content/applications/general/companies/digest_emails.rst:142 +msgid ":guilabel:`Banks and Cash Moves`" +msgstr "" + +#: ../../content/applications/general/companies/digest_emails.rst:147 +msgid "Recipients" +msgstr "" + +#: ../../content/applications/general/companies/digest_emails.rst:149 +msgid "Digest email recipients are added from the :guilabel:`Recipients` tab of the digest email template form." +msgstr "" + +#: ../../content/applications/general/companies/digest_emails.rst:152 +msgid "To add a recipient, navigate to :menuselection:`Settings app --> Statistics section`, and click :guilabel:`Configure Digest Emails`. Then, select the desired digest email, and open the :guilabel:`Recipients` tab." +msgstr "" + +#: ../../content/applications/general/companies/digest_emails.rst:156 +msgid "To add a recipient, click :guilabel:`Add a line`, and an :guilabel:`Add Recipients` pop-up window appears, with all available users to add as recipients." +msgstr "" + +#: ../../content/applications/general/companies/digest_emails.rst:159 +msgid "From the pop-up window, tick the checkbox next to the :guilabel:`Name` of the user(s), and click the :guilabel:`Select` button." +msgstr "" + +#: ../../content/applications/general/companies/digest_emails.rst:162 +msgid "To remove a user as a recipient, click the :guilabel:`❌ (remove)` icon to the far-right of the user listed in the :guilabel:`Recipients` tab." +msgstr "" + +#: ../../content/applications/general/companies/digest_emails.rst:165 +msgid "Click :guilabel:`Save` to implement the changes." +msgstr "" + +#: ../../content/applications/general/companies/digest_emails.rst:170 +msgid "Create digest emails" +msgstr "" + +#: ../../content/applications/general/companies/digest_emails.rst:172 +msgid "To create a new digest email, navigate to :menuselection:`Settings app --> Statistics section`, and click :guilabel:`Configure Digest Emails`. Then, click :guilabel:`Create` to create a new digest email." +msgstr "" + +#: ../../content/applications/general/companies/digest_emails.rst:176 +msgid "A separate page, with a blank digest email template appears, and presents a variety of editable settings, including:" +msgstr "" + +#: ../../content/applications/general/companies/digest_emails.rst:189 +msgid "From there, give the digest email a :guilabel:`Digest Name`, specify :guilabel:`Periodicity`, choose the desired :abbr:`KPIs (key performance indicators)`, and add :guilabel:`Recipients`, as needed." +msgstr "" + +#: ../../content/applications/general/companies/digest_emails.rst:193 +msgid "After clicking :guilabel:`Save`, the new custom digest email is available as a selection in the :guilabel:`Digest Email` field, located in the :menuselection:`Settings app --> Statistics section`." +msgstr "" + +#: ../../content/applications/general/companies/digest_emails.rst:199 +msgid "Custom KPIs with Odoo Studio" +msgstr "" + +#: ../../content/applications/general/companies/digest_emails.rst:201 +msgid "The :abbr:`KPIs (key performance indicators)` on a digest email template form, in the :guilabel:`KPIs` tab, can be customized using Odoo *Studio*." +msgstr "" + +#: ../../content/applications/general/companies/digest_emails.rst:205 +msgid "Additional costs to the database subscription are incurred, should Odoo *Studio* need to be installed." +msgstr "" + +#: ../../content/applications/general/companies/digest_emails.rst:208 +msgid "To begin, click the :guilabel:`🛠️ (tools)` icon in the top-right of the screen. This is the link to the Odoo *Studio* application." +msgstr "" + +#: ../../content/applications/general/companies/digest_emails.rst:211 +msgid "In order to create additional fields, create two fields on the digest object:" +msgstr "" + +#: ../../content/applications/general/companies/digest_emails.rst:213 +msgid "Create a boolean field called `kpi_myfield`, and display it in the :guilabel:`KPIs` tab." +msgstr "" + +#: ../../content/applications/general/companies/digest_emails.rst:214 +msgid "Create a computed field called `kpi_myfield_value` that computes the customized :abbr:`KPI (key performance indicator)`." +msgstr "" + +#: ../../content/applications/general/companies/digest_emails.rst:216 +msgid "Select the :abbr:`KPIs (key performance indicators)` in the :guilabel:`KPIs` tab." +msgstr "" + +#: ../../content/applications/general/companies/digest_emails.rst:219 +msgid "Here is the `source code `_ for the `digest.py` file, which guides the programmer in the coding of the computed field." +msgstr "" + +#: ../../content/applications/general/companies/digest_emails.rst:224 +msgid "Users can also click the :guilabel:`Recipients` tab, and then the vertical three-dot :guilabel:`(kebab)` menu to edit this view. Either click :guilabel:`EDIT LIST VIEW` or :guilabel:`EDIT FORM VIEW` to modify this tab." +msgstr "" + +#: ../../content/applications/general/companies/digest_emails.rst:229 msgid "Computed values reference table" msgstr "" -#: ../../content/applications/general/companies/digest_emails.rst:83 +#: ../../content/applications/general/companies/digest_emails.rst:232 msgid "LABEL" msgstr "" -#: ../../content/applications/general/companies/digest_emails.rst:83 +#: ../../content/applications/general/companies/digest_emails.rst:232 msgid "VALUE" msgstr "" -#: ../../content/applications/general/companies/digest_emails.rst:85 +#: ../../content/applications/general/companies/digest_emails.rst:234 msgid "Connected Users" msgstr "" -#: ../../content/applications/general/companies/digest_emails.rst:85 +#: ../../content/applications/general/companies/digest_emails.rst:234 msgid "`kpi_res_users_connected_value`" msgstr "" -#: ../../content/applications/general/companies/digest_emails.rst:87 +#: ../../content/applications/general/companies/digest_emails.rst:236 msgid "Messages Sent" msgstr "" -#: ../../content/applications/general/companies/digest_emails.rst:87 +#: ../../content/applications/general/companies/digest_emails.rst:236 msgid "`kpi_mail_message_total_value`" msgstr "" -#: ../../content/applications/general/companies/digest_emails.rst:89 +#: ../../content/applications/general/companies/digest_emails.rst:238 msgid "New Leads" msgstr "" -#: ../../content/applications/general/companies/digest_emails.rst:89 +#: ../../content/applications/general/companies/digest_emails.rst:238 msgid "`kpi_crm_lead_created_value`" msgstr "" -#: ../../content/applications/general/companies/digest_emails.rst:91 +#: ../../content/applications/general/companies/digest_emails.rst:240 msgid "Opportunities Won" msgstr "" -#: ../../content/applications/general/companies/digest_emails.rst:91 +#: ../../content/applications/general/companies/digest_emails.rst:240 msgid "`kpi_crm_opportunities_won_value`" msgstr "" -#: ../../content/applications/general/companies/digest_emails.rst:93 +#: ../../content/applications/general/companies/digest_emails.rst:242 msgid "Open Tasks" msgstr "" -#: ../../content/applications/general/companies/digest_emails.rst:93 +#: ../../content/applications/general/companies/digest_emails.rst:242 msgid "`kpi_project_task_opened_value`" msgstr "" -#: ../../content/applications/general/companies/digest_emails.rst:95 +#: ../../content/applications/general/companies/digest_emails.rst:244 msgid "Tickets Closed" msgstr "" -#: ../../content/applications/general/companies/digest_emails.rst:95 +#: ../../content/applications/general/companies/digest_emails.rst:244 msgid "`kpi_helpdesk_tickets_closed_value`" msgstr "" -#: ../../content/applications/general/companies/digest_emails.rst:97 +#: ../../content/applications/general/companies/digest_emails.rst:246 msgid "% of Happiness" msgstr "" -#: ../../content/applications/general/companies/digest_emails.rst:97 +#: ../../content/applications/general/companies/digest_emails.rst:246 msgid "`kpi_livechat_rating_value`" msgstr "" -#: ../../content/applications/general/companies/digest_emails.rst:99 +#: ../../content/applications/general/companies/digest_emails.rst:248 msgid "Conversations handled" msgstr "" -#: ../../content/applications/general/companies/digest_emails.rst:99 +#: ../../content/applications/general/companies/digest_emails.rst:248 msgid "`kpi_livechat_conversations_value`" msgstr "" -#: ../../content/applications/general/companies/digest_emails.rst:101 +#: ../../content/applications/general/companies/digest_emails.rst:250 msgid "Time to answer (sec)" msgstr "" -#: ../../content/applications/general/companies/digest_emails.rst:101 +#: ../../content/applications/general/companies/digest_emails.rst:250 msgid "`kpi_livechat_response_value`" msgstr "" -#: ../../content/applications/general/companies/digest_emails.rst:103 +#: ../../content/applications/general/companies/digest_emails.rst:252 msgid "All Sales" msgstr "" -#: ../../content/applications/general/companies/digest_emails.rst:103 +#: ../../content/applications/general/companies/digest_emails.rst:252 msgid "`kpi_all_sale_total_value`" msgstr "" -#: ../../content/applications/general/companies/digest_emails.rst:105 +#: ../../content/applications/general/companies/digest_emails.rst:254 msgid "eCommerce Sales" msgstr "" -#: ../../content/applications/general/companies/digest_emails.rst:105 +#: ../../content/applications/general/companies/digest_emails.rst:254 msgid "`kpi_website_sale_total_value`" msgstr "" -#: ../../content/applications/general/companies/digest_emails.rst:107 +#: ../../content/applications/general/companies/digest_emails.rst:256 msgid "Revenue" msgstr "" -#: ../../content/applications/general/companies/digest_emails.rst:107 +#: ../../content/applications/general/companies/digest_emails.rst:256 msgid "`kpi_account_total_revenue_value`" msgstr "" -#: ../../content/applications/general/companies/digest_emails.rst:109 +#: ../../content/applications/general/companies/digest_emails.rst:258 msgid "Bank & Cash Moves" msgstr "" -#: ../../content/applications/general/companies/digest_emails.rst:109 +#: ../../content/applications/general/companies/digest_emails.rst:258 msgid "`kpi_account_bank_cash_value`" msgstr "" -#: ../../content/applications/general/companies/digest_emails.rst:111 +#: ../../content/applications/general/companies/digest_emails.rst:260 msgid "POS Sales" msgstr "" -#: ../../content/applications/general/companies/digest_emails.rst:111 +#: ../../content/applications/general/companies/digest_emails.rst:260 msgid "`kpi_pos_total_value`" msgstr "" -#: ../../content/applications/general/companies/digest_emails.rst:113 +#: ../../content/applications/general/companies/digest_emails.rst:262 msgid "New Employees" msgstr "" -#: ../../content/applications/general/companies/digest_emails.rst:113 +#: ../../content/applications/general/companies/digest_emails.rst:262 msgid "`kpi_hr_recruitment_new_colleagues_value`" msgstr "" @@ -1128,6 +1451,7 @@ msgid "Under :guilabel:`Users` or :guilabel:`Groups`, click on :guilabel:`None S msgstr "" #: ../../content/applications/general/email_communication/azure_oauth.rst:94 +#: ../../content/applications/general/integrations/google_translate.rst:59 msgid "Create credentials" msgstr "" @@ -1311,7 +1635,7 @@ 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 +#: ../../content/applications/general/iot/config/troubleshooting.rst:604 msgid "Setup" msgstr "" @@ -1400,7 +1724,7 @@ msgid "Sometimes, emails from Odoo are misclassified by the different email prov msgstr "" #: ../../content/applications/general/email_communication/email_domain.rst:12 -msgid "It is standard in Odoo that emails are received from ``\"name of the author\" ``. In other words this can be translated to: ``\"name of the author\" <{ICP.mail.from.filter}@{mail.catchall.domain}>``. In this case ICP stands for `ir.config.parameters`, which are the System Parameters. Deliverability is greatly improved with the :ref:`notifications configuration `." +msgid "It is standard in Odoo that emails are received from ``\"name of the author\" ``. In other words this can be translated to: ``\"name of the author\" <{ICP.mail.from.filter}@{mail.catchall.domain}>``. In this case ICP stands for `ir.config_parameter`, which are the System Parameters. Deliverability is greatly improved with the :ref:`notifications configuration `." msgstr "" #: ../../content/applications/general/email_communication/email_domain.rst:18 @@ -1748,91 +2072,91 @@ msgstr "" msgid "These notifications are sent using a default from address. For more information see :ref:`Use a default email address `." msgstr "" -#: ../../content/applications/general/email_communication/email_servers.rst:59 +#: ../../content/applications/general/email_communication/email_servers.rst:61 msgid "Manage outbound messages" msgstr "" -#: ../../content/applications/general/email_communication/email_servers.rst:61 +#: ../../content/applications/general/email_communication/email_servers.rst:63 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 +#: ../../content/applications/general/email_communication/email_servers.rst:70 msgid ":doc:`google_oauth`" msgstr "" -#: ../../content/applications/general/email_communication/email_servers.rst:69 +#: ../../content/applications/general/email_communication/email_servers.rst:71 msgid ":doc:`azure_oauth`" msgstr "" -#: ../../content/applications/general/email_communication/email_servers.rst:72 +#: ../../content/applications/general/email_communication/email_servers.rst:74 msgid "Ensuring the outgoing domain has :abbr:`SPF (Sender Policy Framework)`, :abbr:`DKIM (DomainKeys Identified Mail)` and :abbr:`DMARC (Domain-based Message Authentication, Reporting, & Conformance)` set up on the :abbr:`DNS (Domain Name System)` will improve deliverability. For more information see :doc:`email_domain`." msgstr "" -#: ../../content/applications/general/email_communication/email_servers.rst:80 +#: ../../content/applications/general/email_communication/email_servers.rst:82 msgid "Port restriction" msgstr "" -#: ../../content/applications/general/email_communication/email_servers.rst:82 +#: ../../content/applications/general/email_communication/email_servers.rst:84 msgid "Note that port 25 is blocked for security reasons on the Odoo Online and Odoo.sh platforms. Try using ports 465, 587, or 2525 instead." msgstr "" -#: ../../content/applications/general/email_communication/email_servers.rst:88 +#: ../../content/applications/general/email_communication/email_servers.rst:90 msgid "Use a default \"From\" email address" msgstr "" -#: ../../content/applications/general/email_communication/email_servers.rst:90 +#: ../../content/applications/general/email_communication/email_servers.rst:92 msgid "Sometimes, an email's \"From\" (outgoing) address can belong to a different domain, and that can be a problem." msgstr "" -#: ../../content/applications/general/email_communication/email_servers.rst:93 +#: ../../content/applications/general/email_communication/email_servers.rst:95 msgid "For example, if a customer with the email address `mary\\@customer.example.com` responds to a message, Odoo will try to redistribute that same email to the other subscribers in the thread. However, if the domain `customer.example.com` forbids that kind of usage for security, the email that Odoo is trying to redistribute would get rejected by some recipients' email servers." msgstr "" -#: ../../content/applications/general/email_communication/email_servers.rst:98 +#: ../../content/applications/general/email_communication/email_servers.rst:100 msgid "To avoid that problem, Odoo sends all emails using a \"From\" address from the same authorized domain." msgstr "" -#: ../../content/applications/general/email_communication/email_servers.rst:101 +#: ../../content/applications/general/email_communication/email_servers.rst:103 msgid "Access the :guilabel:`System Parameters` by activating :ref:`developer mode ` and going to :menuselection:`Settings --> Technical --> Parameters --> System Parameters` menu." msgstr "" -#: ../../content/applications/general/email_communication/email_servers.rst:104 +#: ../../content/applications/general/email_communication/email_servers.rst:106 msgid "To force the email address from which emails are sent, a combination of the following keys needs to be set in the system parameters of the database:" msgstr "" -#: ../../content/applications/general/email_communication/email_servers.rst:107 +#: ../../content/applications/general/email_communication/email_servers.rst:109 msgid "`mail.default.from`: accepts the local part or a complete email address as value" msgstr "" -#: ../../content/applications/general/email_communication/email_servers.rst:108 +#: ../../content/applications/general/email_communication/email_servers.rst:110 msgid "`mail.default.from_filter`: accepts a domain name or a full email address as value" msgstr "" -#: ../../content/applications/general/email_communication/email_servers.rst:111 +#: ../../content/applications/general/email_communication/email_servers.rst:113 msgid "The `mail.default.from_filter` works only for `odoo-bin` configurations or the default Odoo email server, otherwise this parameter can be set using the `from_filter` field on `ir.mail_server`." msgstr "" -#: ../../content/applications/general/email_communication/email_servers.rst:114 +#: ../../content/applications/general/email_communication/email_servers.rst:116 msgid "The field can be a domain name or an entire email address, or it can remain empty. If the sender's email address does not match this set filter, then the email will be encapsulated using a combination of the two system parameters: `mail.default.from` and `mail.catchall.domain`." msgstr "" -#: ../../content/applications/general/email_communication/email_servers.rst:119 -msgid "In the following example, the from email address is replaced with the combination of the the two system parameters (`mail.default.from` and `mail.catchall.domain`). This is the default\\ notifications configuration in Odoo: ``“Admin” `` => ``“Admin” ``." +#: ../../content/applications/general/email_communication/email_servers.rst:121 +msgid "In the following example, the from email address is replaced with the combination of the the two system parameters (`mail.default.from` and `mail.catchall.domain`). This is the default \\ notifications configuration in Odoo: ``“Admin” `` => ``“Admin” ``." msgstr "" -#: ../../content/applications/general/email_communication/email_servers.rst:124 +#: ../../content/applications/general/email_communication/email_servers.rst:126 msgid "In other words if the email address of the author does not match `mail.default.from_filter`, the email address is replaced by `mail.default.from` (if it contains a full email address) or a combination of `mail.default.from` and `mail.catchall.domain`." msgstr "" -#: ../../content/applications/general/email_communication/email_servers.rst:128 +#: ../../content/applications/general/email_communication/email_servers.rst:130 msgid "If the `from_filter` contains a full email address, and if the `mail.default.from` is the same as this address, then all of the email addresses that are different from `mail.default.from` will be encapsulated in `mail.default.from`." msgstr "" -#: ../../content/applications/general/email_communication/email_servers.rst:135 +#: ../../content/applications/general/email_communication/email_servers.rst:137 msgid "Utilizing the \"From\" filter on an outgoing email server" msgstr "" -#: ../../content/applications/general/email_communication/email_servers.rst:137 +#: ../../content/applications/general/email_communication/email_servers.rst:139 msgid "The :guilabel:`FROM Filtering` field allows for the use of a specific outgoing email server depending on the :guilabel:`From` email address or domain that Odoo is sending on behalf of. This setting can be used to improve the deliverability or sending success rate of emails sent from the database. Setting the :guilabel:`FROM Filtering` field can also be used to send from different domains in a multi-company environment. Access this field in Odoo by navigating to :menuselection:`Settings --> Discuss --> Custom Mail Servers --> Outgoing Mail Servers --> New`." msgstr "" @@ -1840,107 +2164,107 @@ msgstr "" msgid "Outgoing email server settings and the FROM filter settings." msgstr "" -#: ../../content/applications/general/email_communication/email_servers.rst:148 +#: ../../content/applications/general/email_communication/email_servers.rst:150 msgid "When an email is sent from Odoo while the :guilabel:`FROM Filtering` field is set, an email server is chosen in the following sequence:" msgstr "" -#: ../../content/applications/general/email_communication/email_servers.rst:151 +#: ../../content/applications/general/email_communication/email_servers.rst:153 msgid "First, Odoo searches for an email server that has the same :guilabel:`FROM Filtering` value as the :guilabel:`From` value (email address) defined in the outgoing email. For example, if the :guilabel:`From` value (email address) is `test\\@example.com`, only the email servers that have the :guilabel:`FROM Filtering` value equal to `test\\@example.com` are returned." msgstr "" -#: ../../content/applications/general/email_communication/email_servers.rst:155 +#: ../../content/applications/general/email_communication/email_servers.rst:157 msgid "However, if no email servers are found that use the :guilabel:`From` value, then Odoo searches for an email server that has the same *domain* as the :guilabel:`From` value (email address) defined in the outgoing email. For example, if the :guilabel:`From` email address is `test\\@example.com`, only the email servers that have the :guilabel:`FROM Filtering` value equal to `example.com` are returned." msgstr "" -#: ../../content/applications/general/email_communication/email_servers.rst:161 +#: ../../content/applications/general/email_communication/email_servers.rst:163 msgid "If no email servers are found after checking for the domain, then Odoo returns all email servers that do not have any :guilabel:`FROM Filtering` value(s) set." msgstr "" -#: ../../content/applications/general/email_communication/email_servers.rst:164 +#: ../../content/applications/general/email_communication/email_servers.rst:166 msgid "Should this query return no results, then Odoo performs a search for an email server using the system parameter: `mail.default.from`. First, the email address listed attempts to match an email server, and then the domain attempts to find a match. If no email server is found, Odoo returns the first outgoing email server (sorted by priority)." msgstr "" -#: ../../content/applications/general/email_communication/email_servers.rst:170 +#: ../../content/applications/general/email_communication/email_servers.rst:172 msgid "If several email servers are found, then Odoo uses the first one according to its priority. For example, if there are two email servers, one with a priority of `10` and the other with a priority of `20`, then the email server with a priority of `10` is used first." msgstr "" -#: ../../content/applications/general/email_communication/email_servers.rst:177 +#: ../../content/applications/general/email_communication/email_servers.rst:179 msgid "Set up different dedicated servers for transactional and mass emails" msgstr "" -#: ../../content/applications/general/email_communication/email_servers.rst:179 +#: ../../content/applications/general/email_communication/email_servers.rst:181 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 +#: ../../content/applications/general/email_communication/email_servers.rst:186 msgid "A default outgoing email server is already configured. Do not create an alternative one unless a specific external outgoing email server is needed for technical reasons." msgstr "" -#: ../../content/applications/general/email_communication/email_servers.rst:187 +#: ../../content/applications/general/email_communication/email_servers.rst:189 msgid "To do this, first activate the :ref:`developer mode `, and then go to :menuselection:`Settings --> Technical --> Outgoing` email servers. There, create two outgoing email server settings; one for the transactional emails and one for the mass mailing server. Make sure to give priority to the transactional server over the mass mailing server by providing a lower priority number for the transactional email server." msgstr "" -#: ../../content/applications/general/email_communication/email_servers.rst:193 +#: ../../content/applications/general/email_communication/email_servers.rst:195 msgid "Now, go to :menuselection:`Email Marketing --> Settings` and enable :guilabel:`Dedicated Server`. Choose the appropriate email server. With these settings, Odoo uses the server with the lower priority for transactional emails, and the server here selected for mass mails. Note that in this case, the domain's Sender Policy Framework (SPF) records must be set to include both transactional and mass mail servers." msgstr "" -#: ../../content/applications/general/email_communication/email_servers.rst:200 +#: ../../content/applications/general/email_communication/email_servers.rst:202 msgid ":doc:`email_domain`" msgstr "" -#: ../../content/applications/general/email_communication/email_servers.rst:205 +#: ../../content/applications/general/email_communication/email_servers.rst:207 msgid "Manage inbound messages" msgstr "" -#: ../../content/applications/general/email_communication/email_servers.rst:207 +#: ../../content/applications/general/email_communication/email_servers.rst:209 msgid "Odoo relies on generic email aliases to fetch incoming messages." msgstr "" -#: ../../content/applications/general/email_communication/email_servers.rst:209 +#: ../../content/applications/general/email_communication/email_servers.rst:211 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 +#: ../../content/applications/general/email_communication/email_servers.rst:216 msgid "**Bounced messages** are used as a Return-Path. One example this is especially useful for is in `Odoo Email Marketing `__. In this case bounces are opt-out based on if the email bounced too many times (5) in the last month and the bounces are separated by one week. This is done to avoid blacklisting someone because of a mail server error. If these circumstances are met then the email is considered invalid and is blacklisted. A log note is added on the contact under :guilabel:`Blacklisted Email Addresses` on the :guilabel:`Email Marketing Configuration Menu`." msgstr "" -#: ../../content/applications/general/email_communication/email_servers.rst:222 +#: ../../content/applications/general/email_communication/email_servers.rst:224 msgid "Messages that bounce in the chatter (outside of Email Marketing) will populate a red envelope indicating the failed delivery. This can be helpful to know that a Sales Order or an Invoice did not reach its final destination." msgstr "" -#: ../../content/applications/general/email_communication/email_servers.rst:225 +#: ../../content/applications/general/email_communication/email_servers.rst:227 msgid "**Original messages**: several business objects have their own alias to create new records in Odoo from incoming emails:" msgstr "" -#: ../../content/applications/general/email_communication/email_servers.rst:228 +#: ../../content/applications/general/email_communication/email_servers.rst:230 msgid "Sales channel (to create *Leads* or *Opportunities* in `Odoo CRM `_)" msgstr "" -#: ../../content/applications/general/email_communication/email_servers.rst:230 +#: ../../content/applications/general/email_communication/email_servers.rst:232 msgid "Support channel (to create *Tickets* in `Odoo Helpdesk `_)" msgstr "" -#: ../../content/applications/general/email_communication/email_servers.rst:231 +#: ../../content/applications/general/email_communication/email_servers.rst:233 msgid "Projects (to create new *Tasks* in `Odoo Project `_)" msgstr "" -#: ../../content/applications/general/email_communication/email_servers.rst:233 +#: ../../content/applications/general/email_communication/email_servers.rst:235 msgid "Job positions (to create *Applicants* in `Odoo Recruitment `_)" msgstr "" -#: ../../content/applications/general/email_communication/email_servers.rst:236 +#: ../../content/applications/general/email_communication/email_servers.rst:238 msgid "Depending on the mail server, there might be several methods to fetch emails. The easiest and most recommended method is to manage one email address per Odoo alias in the mail server." msgstr "" -#: ../../content/applications/general/email_communication/email_servers.rst:239 +#: ../../content/applications/general/email_communication/email_servers.rst:241 msgid "Create the corresponding email addresses in the mail server (**catchall@**, **bounce@**, **sales@**, etc.)." msgstr "" -#: ../../content/applications/general/email_communication/email_servers.rst:241 +#: ../../content/applications/general/email_communication/email_servers.rst:243 msgid "Set the :guilabel:`Alias Domain` name in :menuselection:`Settings --> General Settings --> Discuss`. Changing the :guilabel:`Alias Domain` will change the catchall's domain for the database." msgstr "" -#: ../../content/applications/general/email_communication/email_servers.rst:244 +#: ../../content/applications/general/email_communication/email_servers.rst:246 msgid "If the database's hosting type is Odoo on-premise, create an :guilabel:`Incoming Mail Server` in Odoo for each alias. To create a new incoming server go to: :menuselection:`Settings --> Discuss --> Custom Mail Servers --> Incoming Mail Servers --> New` Fill out the form according to the email provider's settings. Leave the :guilabel:`Actions to Perform on Incoming Mails` field blank. Once all the information has been filled out, click on :guilabel:`TEST & CONFIRM`." msgstr "" @@ -1948,87 +2272,87 @@ msgstr "" msgid "Incoming mail server configuration on Odoo." msgstr "" -#: ../../content/applications/general/email_communication/email_servers.rst:254 +#: ../../content/applications/general/email_communication/email_servers.rst:256 msgid "If the database's hosting type is Odoo Online or Odoo.sh, redirecting or forwarding incoming messages to Odoo's domain name instead of the external email server is recommended. That way, incoming messages can be received without delay. Redirections for all email addresses should be set to Odoo's domain name in the email server (e.g. `catchall\\@mydomain.ext` to `catchall\\@mycompany.odoo.com`)." msgstr "" -#: ../../content/applications/general/email_communication/email_servers.rst:260 +#: ../../content/applications/general/email_communication/email_servers.rst:262 msgid "All the aliases are customizable in Odoo. Object aliases can be edited from their respective configuration view by navigating to :menuselection:`Settings --> Technical Menu --> Email --> Aliases`." msgstr "" -#: ../../content/applications/general/email_communication/email_servers.rst:264 +#: ../../content/applications/general/email_communication/email_servers.rst:266 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 +#: ../../content/applications/general/email_communication/email_servers.rst:272 msgid "By default, inbound messages are fetched every 5 minutes for on-premise databases." msgstr "" -#: ../../content/applications/general/email_communication/email_servers.rst:273 +#: ../../content/applications/general/email_communication/email_servers.rst:275 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_servers.rst:278 +#: ../../content/applications/general/email_communication/email_servers.rst:280 msgid "System parameters that prevent feedback loops" msgstr "" -#: ../../content/applications/general/email_communication/email_servers.rst:280 +#: ../../content/applications/general/email_communication/email_servers.rst:282 msgid "There are two system parameters that help prevent email loops from occurring in Odoo. These parameters were introduced in Odoo 16 to prevent aliases from creating too many records and to prevent feedback loops on the catchall reply-to email address. They are present in database but not in the *System Parameters*. To override the following defaults they need to be added in." msgstr "" -#: ../../content/applications/general/email_communication/email_servers.rst:285 +#: ../../content/applications/general/email_communication/email_servers.rst:287 msgid "The two system parameters are as follows:" msgstr "" -#: ../../content/applications/general/email_communication/email_servers.rst:287 +#: ../../content/applications/general/email_communication/email_servers.rst:289 msgid "`mail.gateway.loop.minutes` (120 minutes by default)" msgstr "" -#: ../../content/applications/general/email_communication/email_servers.rst:288 +#: ../../content/applications/general/email_communication/email_servers.rst:290 msgid "`mail.gateway.loop.threshold` (20 by default)" msgstr "" -#: ../../content/applications/general/email_communication/email_servers.rst:290 +#: ../../content/applications/general/email_communication/email_servers.rst:292 msgid "Add these fields in Odoo by first enabling :ref:`developer mode `, and then navigating to :menuselection:`Settings --> Technical Menu --> Parameters --> System Parameters`. Change the value of these parameters, as needed." msgstr "" -#: ../../content/applications/general/email_communication/email_servers.rst:294 +#: ../../content/applications/general/email_communication/email_servers.rst:296 msgid "When an email is received in the Odoo database on the catchall email address or on any alias, Odoo looks at the mail received for the given period of time defined in the system parameter `mail.gateway.loop.minutes`. If the received email was sent to an alias then Odoo will reference the `mail.gateway.loop.threshold` system parameter and determine the value as the number of records this alias is allowed to create in the given period of time (value of `mail.gateway.loop.minutes`)." msgstr "" -#: ../../content/applications/general/email_communication/email_servers.rst:300 +#: ../../content/applications/general/email_communication/email_servers.rst:302 msgid "In addition, when email is received to the catchall email address, Odoo will reference the emails received to the database during the set period of time (as stated by the value in the system parameter: `mail.gateway.loop.minutes`). Odoo will then determine whether any of the emails received match that of the email(s) being received during the specified time-frame, and will prevent a feedback loop from occurring if a duplicate email is detected." msgstr "" -#: ../../content/applications/general/email_communication/email_servers.rst:307 +#: ../../content/applications/general/email_communication/email_servers.rst:309 msgid "Allow alias domain system parameter" msgstr "" -#: ../../content/applications/general/email_communication/email_servers.rst:309 +#: ../../content/applications/general/email_communication/email_servers.rst:311 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_servers.rst:313 +#: ../../content/applications/general/email_communication/email_servers.rst:315 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_servers.rst:318 +#: ../../content/applications/general/email_communication/email_servers.rst:320 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_servers.rst:323 +#: ../../content/applications/general/email_communication/email_servers.rst:325 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_servers.rst:329 +#: ../../content/applications/general/email_communication/email_servers.rst:331 msgid "This alias mismatch issue has been resolved in Odoo 17, however, the `mail.catchall.domain.allowed` system parameter is still used in Odoo 17 for backward compatibility." msgstr "" -#: ../../content/applications/general/email_communication/email_servers.rst:333 +#: ../../content/applications/general/email_communication/email_servers.rst:335 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_servers.rst:338 +#: ../../content/applications/general/email_communication/email_servers.rst:340 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 "" @@ -2180,11 +2504,11 @@ msgstr "" msgid "One of the most common reasons for an email failing to send with no error message is related to :ref:`SPF ` and/or :ref:`DKIM ` configuration. Also, check to make sure the `mail.bounce.alias` is defined in the *system parameters*. Access system parameters in :ref:`developer mode ` by navigating to :menuselection:`Settings app --> Technical menu --> Parameters --> System Parameters`." msgstr "" -#: ../../content/applications/general/email_communication/faq.rst:124 +#: ../../content/applications/general/email_communication/faq.rst:126 msgid "Email is sent late" msgstr "" -#: ../../content/applications/general/email_communication/faq.rst:126 +#: ../../content/applications/general/email_communication/faq.rst:128 msgid "Email campaigns send at a scheduled time, using a delay pre-programed in the database. Odoo uses a delayed task to send emails that are considered \"not urgent\" (newsletter formats, such as: mass mailing, marketing automation, and events). The system utility **cron** can be used to schedule programs to run automatically at predetermined intervals. Odoo uses that policy in order to avoid cluttering the mail servers and, instead, prioritizes individual communication. This **cron** is called :guilabel:`Mail: Email Queue Manager`, and can be accessed in :ref:`developer mode ` by going to :menuselection:`Settings app --> Technical menu --> Automation --> Scheduled Actions`." msgstr "" @@ -2192,119 +2516,119 @@ msgstr "" msgid "Email scheduled to be sent later." msgstr "" -#: ../../content/applications/general/email_communication/faq.rst:140 +#: ../../content/applications/general/email_communication/faq.rst:142 msgid "What is a **cron**? A cron is an action that Odoo runs in the background to execute particular code to complete a task." msgstr "" -#: ../../content/applications/general/email_communication/faq.rst:144 +#: ../../content/applications/general/email_communication/faq.rst:146 msgid "By default, the *Mass Mailing cron* runs every 60 minutes. This can be changed to no less than 5 minutes. However, running the action every 5 minutes would bog down the Odoo database (stress the system), so this is not recommended. To edit the mass mailing cron, select the scheduled action :guilabel:`Mail: Email Queue Manager`, and proceed to make any necessary adjustments." msgstr "" -#: ../../content/applications/general/email_communication/faq.rst:149 +#: ../../content/applications/general/email_communication/faq.rst:151 msgid "Emails that are considered urgent (communication from one person to another, such as sales orders, invoices, purchase orders, etc.) are sent immediately." msgstr "" -#: ../../content/applications/general/email_communication/faq.rst:153 +#: ../../content/applications/general/email_communication/faq.rst:155 msgid "Incoming emails" msgstr "" -#: ../../content/applications/general/email_communication/faq.rst:155 +#: ../../content/applications/general/email_communication/faq.rst:157 msgid "When there is an issue with incoming emails, there might not be an indication, per se, in Odoo. It is the sending email client, who tries to contact a database, that will get a bounce-back message (most of the time a :guilabel:`550: mailbox unavailable` error message)." msgstr "" -#: ../../content/applications/general/email_communication/faq.rst:160 +#: ../../content/applications/general/email_communication/faq.rst:162 msgid "Email is not received" msgstr "" -#: ../../content/applications/general/email_communication/faq.rst:162 +#: ../../content/applications/general/email_communication/faq.rst:164 msgid "The steps that should be taken depend on the Odoo platform where the database is hosted." msgstr "" -#: ../../content/applications/general/email_communication/faq.rst:164 +#: ../../content/applications/general/email_communication/faq.rst:166 msgid "**Odoo.sh** users can find their live logs on the folder :file:`~/logs/`." msgstr "" -#: ../../content/applications/general/email_communication/faq.rst:166 +#: ../../content/applications/general/email_communication/faq.rst:168 msgid "Logs are a stored collection of all the tasks completed in a database. They are a text-only representation, complete with timestamps of every action taken on the Odoo database. This can be helpful to track emails leaving the database. Failure to send can also be seen by logs that indicate that the message tried to send repeatedly. Logs will show every action to the email servers from the database." msgstr "" -#: ../../content/applications/general/email_communication/faq.rst:172 +#: ../../content/applications/general/email_communication/faq.rst:174 msgid "The folder :file:`~/logs/` (accessed by the command line or on the Odoo.sh dashboard) of an Odoo.sh database contains a list of files containing the logs of the database. The log files are created everyday at 5:00 AM (UTC)." msgstr "" -#: ../../content/applications/general/email_communication/faq.rst:177 +#: ../../content/applications/general/email_communication/faq.rst:179 msgid "The two most recent days (today and yesterday) are not compressed, while the older ones are, in order to save space. The naming of the files for today and yesterday are respectively: :file:`odoo.log` and :file:`odoo.log.1`." msgstr "" -#: ../../content/applications/general/email_communication/faq.rst:181 +#: ../../content/applications/general/email_communication/faq.rst:183 msgid "For the following days, they are named with their dates, and then compressed. Use the command :command:`grep` and :command:`zgrep` (for the compressed ones) to search through the files." msgstr "" -#: ../../content/applications/general/email_communication/faq.rst:185 +#: ../../content/applications/general/email_communication/faq.rst:187 msgid "For more information on logs and how to access them via the Odoo.sh dashboard, see :ref:`this administration documentation `." msgstr "" -#: ../../content/applications/general/email_communication/faq.rst:188 +#: ../../content/applications/general/email_communication/faq.rst:190 msgid "For more information on accessing logs via the command line visit :ref:`this developer documentation `." msgstr "" -#: ../../content/applications/general/email_communication/faq.rst:191 +#: ../../content/applications/general/email_communication/faq.rst:193 msgid "**Odoo Online** users won't have access to the logs. However `Odoo Support `_ can be contacted if there is a recurring issue with the same client or domain." msgstr "" -#: ../../content/applications/general/email_communication/faq.rst:196 +#: ../../content/applications/general/email_communication/faq.rst:198 msgid "Get help from Odoo support" msgstr "" -#: ../../content/applications/general/email_communication/faq.rst:198 +#: ../../content/applications/general/email_communication/faq.rst:200 msgid "In order to get helped efficiently, please provide as much information as possible. Here is a list of what can be helpful when reaching out to the Odoo Support team about an issue:" msgstr "" -#: ../../content/applications/general/email_communication/faq.rst:201 +#: ../../content/applications/general/email_communication/faq.rst:203 msgid "Send a copy of the email headers. The `.EML` file (or **headers**) of the email is the file format containing all the technical information required for an investigation. The documentation from the email provider might explain how to access the EML file/header files. Once the headers of the email are obtained, adding it into the Odoo Support ticket is the most efficient way for the Odoo Support team to investigate." msgstr "" -#: ../../content/applications/general/email_communication/faq.rst:208 +#: ../../content/applications/general/email_communication/faq.rst:210 msgid "`Gmail documentation on headers `_" msgstr "" -#: ../../content/applications/general/email_communication/faq.rst:209 +#: ../../content/applications/general/email_communication/faq.rst:211 msgid "`Outlook documentation on headers `_" msgstr "" -#: ../../content/applications/general/email_communication/faq.rst:212 +#: ../../content/applications/general/email_communication/faq.rst:214 msgid "Explain the exact flow that is being followed to normally receive those emails in Odoo. Here are examples of questions whose answers can be useful:" msgstr "" -#: ../../content/applications/general/email_communication/faq.rst:215 +#: ../../content/applications/general/email_communication/faq.rst:217 msgid "Is this a notification message from a reply being received in Odoo?" msgstr "" -#: ../../content/applications/general/email_communication/faq.rst:216 +#: ../../content/applications/general/email_communication/faq.rst:218 msgid "Is this a message being sent from the Odoo database?" msgstr "" -#: ../../content/applications/general/email_communication/faq.rst:217 +#: ../../content/applications/general/email_communication/faq.rst:219 msgid "Is there an incoming email server being used, or is the email somehow being redirected?" msgstr "" -#: ../../content/applications/general/email_communication/faq.rst:218 +#: ../../content/applications/general/email_communication/faq.rst:220 msgid "Is there an example of an email that has been correctly forwarded?" msgstr "" -#: ../../content/applications/general/email_communication/faq.rst:220 +#: ../../content/applications/general/email_communication/faq.rst:222 msgid "Provide answers to the following questions:" msgstr "" -#: ../../content/applications/general/email_communication/faq.rst:222 +#: ../../content/applications/general/email_communication/faq.rst:224 msgid "Is it a generic issue, or is it specific to a use case? If specific to a use case, which one exactly?" msgstr "" -#: ../../content/applications/general/email_communication/faq.rst:224 +#: ../../content/applications/general/email_communication/faq.rst:226 msgid "Is it working as expected? In case the email is sent using Odoo, the bounce email should reach the Odoo database, and display the :ref:`red envelope `." msgstr "" -#: ../../content/applications/general/email_communication/faq.rst:228 +#: ../../content/applications/general/email_communication/faq.rst:230 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 "" @@ -2334,6 +2658,7 @@ msgid "Setup in Google" msgstr "" #: ../../content/applications/general/email_communication/google_oauth.rst:22 +#: ../../content/applications/general/integrations/google_translate.rst:17 msgid "Create a new project" msgstr "" @@ -2350,10 +2675,12 @@ msgid "On the :menuselection:`New Project` screen, rename the :guilabel:`Project msgstr "" #: ../../content/applications/general/email_communication/google_oauth.rst:-1 +#: ../../content/applications/general/integrations/google_translate.rst:-1 msgid "Project Name and Location for Google OAuth." msgstr "" #: ../../content/applications/general/email_communication/google_oauth.rst:42 +#: ../../content/applications/general/integrations/google_translate.rst:39 msgid "Click on :guilabel:`Create` to finish this step." msgstr "" @@ -2834,6 +3161,138 @@ msgstr "" msgid ":doc:`/applications/websites/website/configuration/address_autocomplete`" msgstr "" +#: ../../content/applications/general/integrations/google_translate.rst:3 +msgid "Google Translate" +msgstr "" + +#: ../../content/applications/general/integrations/google_translate.rst:5 +msgid "*Google Translate* can be used to translate user generated text in the Odoo chatter." +msgstr "" + +#: ../../content/applications/general/integrations/google_translate.rst:8 +msgid "Google API console" +msgstr "" + +#: ../../content/applications/general/integrations/google_translate.rst:10 +msgid "A majority of the setup for integrating *Google Translate* into Odoo is done with the *Google API console*. Once the following processes are complete, an *API key* is created to input in Odoo." +msgstr "" + +#: ../../content/applications/general/integrations/google_translate.rst:14 +msgid "`Google Translate setup on Google `_" +msgstr "" + +#: ../../content/applications/general/integrations/google_translate.rst:19 +msgid "To get started, go to the `Google API Console `_. Then, log in with a *Google Workspace* account, if there is one. If not, log in with a personal Gmail account (this should match the email address that has billing attached to it)." +msgstr "" + +#: ../../content/applications/general/integrations/google_translate.rst:23 +msgid "Next, click :guilabel:`Create Project` on the far-right of the :guilabel:`OAuth consent screen`." +msgstr "" + +#: ../../content/applications/general/integrations/google_translate.rst:26 +msgid "If the *Google API Console* has existing projects, click the drop-down menu next to the :guilabel:`Google Cloud` icon, and a pop-over window appears. Next, click :guilabel:`New Project` top-right of the pop-over window." +msgstr "" + +#: ../../content/applications/general/integrations/google_translate.rst:30 +msgid "On the :guilabel:`New Project` screen, rename the :guilabel:`Project name` to `Odoo Translate`, and browse for the :guilabel:`Location`. Set the :guilabel:`Location` as the *Google Workspace organization*. If a personal Gmail account is being used, leave the :guilabel:`Location` as :guilabel:`No Organization`." +msgstr "" + +#: ../../content/applications/general/integrations/google_translate.rst:42 +msgid "API library" +msgstr "" + +#: ../../content/applications/general/integrations/google_translate.rst:44 +msgid "Next, the *Cloud Translation API* needs to be installed on this newly-created project. To do that, click :menuselection:`Library` in the left menu. Then, search the term `Cloud Translation API`, and click into the result. This should be a *Google Enterprise API* labeled :guilabel:`Cloud Translation API`." +msgstr "" + +#: ../../content/applications/general/integrations/google_translate.rst:49 +msgid "Click :guilabel:`Enable` to install the library on this project." +msgstr "" + +#: ../../content/applications/general/integrations/google_translate.rst:52 +msgid "Using the *Google Translate* API **requires** a current billing account with `Google `_." +msgstr "" + +#: ../../content/applications/general/integrations/google_translate.rst:55 +msgid "Once a billing account is setup with *Google* and the library is enabled, click :guilabel:`Manage` to finish configuration on the API." +msgstr "" + +#: ../../content/applications/general/integrations/google_translate.rst:61 +msgid "Now that the project is set up, and the *Cloud Translation API* is enabled, credentials **must** be created. This includes the *API key*." +msgstr "" + +#: ../../content/applications/general/integrations/google_translate.rst:64 +msgid "To begin this process, click :menuselection:`Credentials` in the left sidebar menu." +msgstr "" + +#: ../../content/applications/general/integrations/google_translate.rst:66 +msgid "Then, click :guilabel:`Create Credentials` in the top menu, and select :guilabel:`API key` from the drop-down menu." +msgstr "" + +#: ../../content/applications/general/integrations/google_translate.rst:-1 +msgid "Create an API key in the Google API console." +msgstr "" + +#: ../../content/applications/general/integrations/google_translate.rst:73 +msgid "Copy the :guilabel:`API key` for use in the next section." +msgstr "" + +#: ../../content/applications/general/integrations/google_translate.rst:76 +msgid "For security purposes, the usage of the *API key* can be restricted." +msgstr "" + +#: ../../content/applications/general/integrations/google_translate.rst:78 +msgid "To do that, go to the *API restrictions* by clicking on :guilabel:`Edit API key` in the pop-over window, or by clicking on the listed API key on the :guilabel:`Credentials` page. From here, key restrictions can be set. This includes setting an application to restrict the use of the API key, and whether this API key can call any API." +msgstr "" + +#: ../../content/applications/general/integrations/google_translate.rst:83 +msgid "It is recommended that the Odoo *Translate API* be restricted to **only** allow requests from the configured Odoo database and to the *Cloud Translation API*." +msgstr "" + +#: ../../content/applications/general/integrations/google_translate.rst:86 +msgid "To add the website restriction, click :guilabel:`Websites`, under the :guilabel:`Set an application restriction`. Then, enter the address of the database *Google Translate* is being used in, by clicking on :guilabel:`Add`. Lastly, add the :abbr:`URL (Uniform Resource Locator)`, and click :guilabel:`Done`." +msgstr "" + +#: ../../content/applications/general/integrations/google_translate.rst:91 +msgid "To restrict use of the key to a selected API, first, select :guilabel:`Restrict key`, under the :guilabel:`API restrictions` section. Then use the drop-down menu to choose the API being configured (*Cloud Translation API*)." +msgstr "" + +#: ../../content/applications/general/integrations/google_translate.rst:96 +msgid "Save the API key: copy the API key and store it somewhere secure." +msgstr "" + +#: ../../content/applications/general/integrations/google_translate.rst:97 +msgid "Do **not** share the API key publicly or expose it in client-side code." +msgstr "" + +#: ../../content/applications/general/integrations/google_translate.rst:100 +msgid "Odoo configuration" +msgstr "" + +#: ../../content/applications/general/integrations/google_translate.rst:102 +msgid "To access the integration in Odoo, navigate to the :menuselection:`Settings app --> Discuss section`. Enter the API key into the field labeled :guilabel:`Message Translation`. Then, :guilabel:`Save` the settings, and *Google Translate* can be used in any chatter throughout the database." +msgstr "" + +#: ../../content/applications/general/integrations/google_translate.rst:-1 +msgid "Odoo configuration of the API key from the *Google API Console*." +msgstr "" + +#: ../../content/applications/general/integrations/google_translate.rst:112 +msgid "Translate chatter" +msgstr "" + +#: ../../content/applications/general/integrations/google_translate.rst:114 +msgid "To translate a user's text from another language, click the :guilabel:`... (three dot)` icon menu to the right of the chatter. Then, select :guilabel:`Translate`. The content translates to the *language* set on the user's preferences." +msgstr "" + +#: ../../content/applications/general/integrations/google_translate.rst:-1 +msgid "Google Translate present in an Odoo database's chatter." +msgstr "" + +#: ../../content/applications/general/integrations/google_translate.rst:123 +msgid ":ref:`language/change-user-language`" +msgstr "" + #: ../../content/applications/general/integrations/mail_plugins.rst:5 msgid "Mail Plugins" msgstr "" @@ -3099,7 +3558,11 @@ msgstr "" msgid "More actions button in Outlook" msgstr "" -#: ../../content/applications/general/integrations/mail_plugins/outlook.rst:38 +#: ../../content/applications/general/integrations/mail_plugins/outlook.rst:39 +msgid "For locally installed versions of Microsoft Outlook, access the :guilabel:`Get Add-ins` menu item while in preview mode (**not** with a message open). First, click on the :guilabel:`... (ellipsis)` icon in the upper right of the previewed message, then scroll down, and click on :guilabel:`Get Add-ins`." +msgstr "" + +#: ../../content/applications/general/integrations/mail_plugins/outlook.rst:44 msgid "Following this step, select the :guilabel:`My add-ins` tab on the left-side." msgstr "" @@ -3107,7 +3570,7 @@ msgstr "" msgid "My add-ins in Outlook" msgstr "" -#: ../../content/applications/general/integrations/mail_plugins/outlook.rst:44 +#: ../../content/applications/general/integrations/mail_plugins/outlook.rst:50 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 "" @@ -3115,7 +3578,7 @@ msgstr "" msgid "Custom add-ins in Outlook" msgstr "" -#: ../../content/applications/general/integrations/mail_plugins/outlook.rst:51 +#: ../../content/applications/general/integrations/mail_plugins/outlook.rst:57 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 "" @@ -3123,11 +3586,11 @@ msgstr "" msgid "Custom add-in installation warning in Outlook" msgstr "" -#: ../../content/applications/general/integrations/mail_plugins/outlook.rst:61 +#: ../../content/applications/general/integrations/mail_plugins/outlook.rst:67 msgid "Connect the database" msgstr "" -#: ../../content/applications/general/integrations/mail_plugins/outlook.rst:63 +#: ../../content/applications/general/integrations/mail_plugins/outlook.rst:69 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 "" @@ -3135,7 +3598,7 @@ msgstr "" msgid "Odoo for Outlook add-in button" msgstr "" -#: ../../content/applications/general/integrations/mail_plugins/outlook.rst:71 +#: ../../content/applications/general/integrations/mail_plugins/outlook.rst:77 msgid "The right-side panel can now display **Company Insights**. At the bottom, click on :guilabel:`Login`." msgstr "" @@ -3143,27 +3606,27 @@ msgstr "" msgid "Logging in the Odoo database" msgstr "" -#: ../../content/applications/general/integrations/mail_plugins/outlook.rst:79 +#: ../../content/applications/general/integrations/mail_plugins/outlook.rst:85 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 +#: ../../content/applications/general/integrations/mail_plugins/outlook.rst:89 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 +#: ../../content/applications/general/integrations/mail_plugins/outlook.rst:93 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 +#: ../../content/applications/general/integrations/mail_plugins/outlook.rst:95 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 +#: ../../content/applications/general/integrations/mail_plugins/outlook.rst:100 msgid "Once this is complete, the Outlook panel needs to be opened again." msgstr "" -#: ../../content/applications/general/integrations/mail_plugins/outlook.rst:96 +#: ../../content/applications/general/integrations/mail_plugins/outlook.rst:102 msgid "Now, enter the Odoo database URL and click on :guilabel:`Login`." msgstr "" @@ -3171,7 +3634,7 @@ msgstr "" msgid "Entering the Odoo database URL" msgstr "" -#: ../../content/applications/general/integrations/mail_plugins/outlook.rst:102 +#: ../../content/applications/general/integrations/mail_plugins/outlook.rst:108 msgid "Next, click on :guilabel:`Allow` to open the pop-up window." msgstr "" @@ -3179,7 +3642,7 @@ msgstr "" msgid "New window pop-up warning" msgstr "" -#: ../../content/applications/general/integrations/mail_plugins/outlook.rst:108 +#: ../../content/applications/general/integrations/mail_plugins/outlook.rst:114 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 "" @@ -3187,15 +3650,15 @@ msgstr "" msgid "Allowing the Outlook Plugin to connect to a database" msgstr "" -#: ../../content/applications/general/integrations/mail_plugins/outlook.rst:118 +#: ../../content/applications/general/integrations/mail_plugins/outlook.rst:124 msgid "Add a shortcut to the plugin" msgstr "" -#: ../../content/applications/general/integrations/mail_plugins/outlook.rst:120 +#: ../../content/applications/general/integrations/mail_plugins/outlook.rst:126 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 +#: ../../content/applications/general/integrations/mail_plugins/outlook.rst:129 msgid "In the Outlook mailbox, click on :guilabel:`Settings`, then on :guilabel:`View all Outlook settings`." msgstr "" @@ -3203,7 +3666,7 @@ msgstr "" msgid "Viewing all Outlook settings" msgstr "" -#: ../../content/applications/general/integrations/mail_plugins/outlook.rst:130 +#: ../../content/applications/general/integrations/mail_plugins/outlook.rst:136 msgid "Now, select :guilabel:`Customize actions` under :guilabel:`Mail`, click on :guilabel:`Odoo for Outlook`, and then :guilabel:`Save`." msgstr "" @@ -3212,15 +3675,15 @@ msgstr "" msgid "Odoo for Outlook customized action" msgstr "" -#: ../../content/applications/general/integrations/mail_plugins/outlook.rst:137 +#: ../../content/applications/general/integrations/mail_plugins/outlook.rst:143 msgid "Following this step, open any email; the shortcut should be displayed." msgstr "" -#: ../../content/applications/general/integrations/mail_plugins/outlook.rst:144 +#: ../../content/applications/general/integrations/mail_plugins/outlook.rst:150 msgid "Using the plugin" msgstr "" -#: ../../content/applications/general/integrations/mail_plugins/outlook.rst:146 +#: ../../content/applications/general/integrations/mail_plugins/outlook.rst:152 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 "" @@ -3808,7 +4271,7 @@ msgid "Connect a supported receipt printer to a :abbr:`USB (Universal Serial Bus msgstr "" #: ../../content/applications/general/iot/config/pos.rst:43 -#: ../../content/applications/general/iot/config/troubleshooting.rst:412 +#: ../../content/applications/general/iot/config/troubleshooting.rst:560 msgid "Cash drawer" msgstr "" @@ -3817,7 +4280,7 @@ 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 +#: ../../content/applications/general/iot/config/troubleshooting.rst:508 msgid "Barcode scanner" msgstr "" @@ -3826,7 +4289,7 @@ msgid "In order for the barcode scanner to be compatible it must end barcodes wi msgstr "" #: ../../content/applications/general/iot/config/pos.rst:48 -#: ../../content/applications/general/iot/config/troubleshooting.rst:423 +#: ../../content/applications/general/iot/config/troubleshooting.rst:571 msgid "Scale" msgstr "" @@ -4320,42 +4783,194 @@ 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" +msgid "DYMO LabelWriter print issue" 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." +msgid "The DYMO LabelWriter has a known issue in printing with the :abbr:`IoT (Internet of Things)` box. The OpenPrinting CUPS server installs the printer using :guilabel:`Local RAW Printer` drivers. In order to print anything, the correct :guilabel:`Make and Model` needs to be set, so the correct driver is referenced when using the device." msgstr "" -#: ../../content/applications/general/iot/config/troubleshooting.rst:356 -msgid "Check out Zebra's instructions on printing :abbr:`ZPL (Zebra Programming Language)` files `here `_." +#: ../../content/applications/general/iot/config/troubleshooting.rst:354 +msgid "Additionally, a new printer needs to be added to reduce a print delay that occurs after updating the driver." msgstr "" -#: ../../content/applications/general/iot/config/troubleshooting.rst:363 -msgid "The characters read by the barcode scanner do not match the barcode" +#: ../../content/applications/general/iot/config/troubleshooting.rst:358 +msgid "The DYMO LabelWriter 450 DUO printer is the recommended DYMO printer for use with Odoo and the :abbr:`IoT (Internet of Things)` box. It **must** already be connected to, and recognized on, the :abbr:`IoT (Internet of Things)` box." 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." +#: ../../content/applications/general/iot/config/troubleshooting.rst:362 +msgid "The DYMO LabelWriter 450 DUO printer contains two printers in one: a label printer and a tape printer. Choosing the correct model (either DYMO LabelWriter 450 DUO Label (en) or DYMO LabelWriter 450 DUO Tape (en)) is crucial when configuring the following processes." msgstr "" -#: ../../content/applications/general/iot/config/troubleshooting.rst:370 -msgid "Nothing happens when a barcode is scanned" +#: ../../content/applications/general/iot/config/troubleshooting.rst:366 +msgid "To keep things consistent, both of the following processes detail the configuration for the DYMO LabelWriter 450 DUO Label (en) model. Change the model when needed." msgstr "" #: ../../content/applications/general/iot/config/troubleshooting.rst:372 +msgid "DYMO LabelWriter not printing" +msgstr "" + +#: ../../content/applications/general/iot/config/troubleshooting.rst:374 +msgid "In the case where the DYMO LabelWriter is not printing anything, a new driver needs to be installed." +msgstr "" + +#: ../../content/applications/general/iot/config/troubleshooting.rst:376 +msgid "First, open the OpenPrinting CUPS console by clicking :menuselection:`Printers server` at the bottom of the :abbr:`IoT (Internet of Things)` box homepage. Next, click on :menuselection:`Printers` in the top menu. Click into the printer in question, and select :guilabel:`Maintenance` in the first drop-down menu. Then, select :guilabel:`Modify Printer` in the second drop-down menu." +msgstr "" + +#: ../../content/applications/general/iot/config/troubleshooting.rst:-1 +msgid "Modify the make and model of the DYMO LabelWriter. Maintenance and Modify drop-down menus\n" +"highlighted." +msgstr "" + +#: ../../content/applications/general/iot/config/troubleshooting.rst:386 +msgid "Next, select the specific network connection/printer that the modification should be made on. Click :guilabel:`Continue`." +msgstr "" + +#: ../../content/applications/general/iot/config/troubleshooting.rst:-1 +msgid "Printer selection screen with Continue highlighted." +msgstr "" + +#: ../../content/applications/general/iot/config/troubleshooting.rst:393 +msgid "On the next page, click :guilabel:`Continue` to proceed to set the :guilabel:`Make` of the printer." +msgstr "" + +#: ../../content/applications/general/iot/config/troubleshooting.rst:-1 +msgid "Printer modification screen with Continue highlighted." +msgstr "" + +#: ../../content/applications/general/iot/config/troubleshooting.rst:399 +msgid "Under :guilabel:`Make` select :guilabel:`DYMO` from the menu. Click on :guilabel:`Continue` to set the :guilabel:`Model`." +msgstr "" + +#: ../../content/applications/general/iot/config/troubleshooting.rst:-1 +msgid "Setting the make page, with DYMO and continue highlighted." +msgstr "" + +#: ../../content/applications/general/iot/config/troubleshooting.rst:406 +msgid "On the following page, set the :guilabel:`Model` to :guilabel:`DYMO LabelWriter 450 DUO Label (en)` (or whichever DYMO printer model is being used). Click on :guilabel:`Modify Printer` to complete setting the new driver, a confirmation page will appear." +msgstr "" + +#: ../../content/applications/general/iot/config/troubleshooting.rst:-1 +msgid "Setting the printer model page with DYMO LabelWriter 450 DUO Label (en) highlighted." +msgstr "" + +#: ../../content/applications/general/iot/config/troubleshooting.rst:414 +msgid "After being redirected to a confirmation page, acknowledging a successful update, click on the :menuselection:`Printers` button in the top menu." +msgstr "" + +#: ../../content/applications/general/iot/config/troubleshooting.rst:417 +msgid "All the printers installed on the OpenPrinting CUPS server appear, including the newly updated: :guilabel:`DYMO LabelWriter 450 DUO Label` (or whichever DYMO printer model is being used). Click into the printer that was just updated." +msgstr "" + +#: ../../content/applications/general/iot/config/troubleshooting.rst:421 +msgid "To print a test label, click on the :guilabel:`Maintenance` drop-down menu to the left of the :guilabel:`Administration` drop-down menu, and select :guilabel:`Print Test Page`. The test label will print out with a ten-second delay if the driver update was successful." +msgstr "" + +#: ../../content/applications/general/iot/config/troubleshooting.rst:-1 +#: ../../content/applications/general/iot/config/troubleshooting.rst:-1 +msgid "Printing a test page from the administration drop-down menu in the OpenPrinting CUPs\n" +"server." +msgstr "" + +#: ../../content/applications/general/iot/config/troubleshooting.rst:430 +msgid "To reduce this delay a new printer will need to be added, follow the process below." +msgstr "" + +#: ../../content/applications/general/iot/config/troubleshooting.rst:433 +msgid "DYMO LabelWriter print delay" +msgstr "" + +#: ../../content/applications/general/iot/config/troubleshooting.rst:435 +msgid "To resolve the delay issue after modifying the driver, the printer **must** be reinstalled. To reinstall the printer, open the OpenPrinting CUPS administration page by clicking :menuselection:`Printers server`, at the bottom of the :abbr:`IoT (Internet of Things)` box homepage. Then, click on :menuselection:`Administration` in the top menu, then click :guilabel:`Add a Printer`." +msgstr "" + +#: ../../content/applications/general/iot/config/troubleshooting.rst:442 +msgid "If the DYMO LabelWriter 450 DUO printer is not printing at all, or is not recognizable (has a RAW driver type), then update the drivers on the device. See :ref:`troubleshooting/dymo/update_drivers`." +msgstr "" + +#: ../../content/applications/general/iot/config/troubleshooting.rst:-1 +msgid "Add a printer button highlighted on the Printer CUPS management page." +msgstr "" + +#: ../../content/applications/general/iot/config/troubleshooting.rst:450 +msgid "On the next screen, in the :guilabel:`Local Printers` section, select the :guilabel:`DYMO LabelWriter 450 DUO Label (DYMO LabelWriter 450 DUO Label)` (or whichever DYMO printer model is being used) pre-installed printer. Click :guilabel:`Continue`." +msgstr "" + +#: ../../content/applications/general/iot/config/troubleshooting.rst:-1 +msgid "Add a printer screen on OpenPrinting CUPS with DYMO LabelWriter 450 DUO Label highlighted." +msgstr "" + +#: ../../content/applications/general/iot/config/troubleshooting.rst:458 +msgid "On the following screen, modify the :guilabel:`Name` to something recognizable, as the original printer will still be present. Click :guilabel:`Continue` to be taken to the next screen." +msgstr "" + +#: ../../content/applications/general/iot/config/troubleshooting.rst:-1 +msgid "Rename printer page in the 'Add a Printer' flow, with the name field highlighted." +msgstr "" + +#: ../../content/applications/general/iot/config/troubleshooting.rst:465 +msgid "Next, choose the :guilabel:`Model`. Select :guilabel:`DYMO LabelWriter 450 DUO Label (en)` (or whichever DYMO printer model is being used), and finally, click :guilabel:`Add Printer` to complete the installation." +msgstr "" + +#: ../../content/applications/general/iot/config/troubleshooting.rst:-1 +msgid "Choose model screen on the OpenPrinting CUPS console with model and add a printer\n" +"highlighted." +msgstr "" + +#: ../../content/applications/general/iot/config/troubleshooting.rst:474 +msgid "After being redirected to a confirmation page, acknowledging a successful installation, click on the :menuselection:`Printers` button in the top menu." +msgstr "" + +#: ../../content/applications/general/iot/config/troubleshooting.rst:477 +msgid "All the printers installed on the OpenPrinting CUPS server appear, including the newly installed: :guilabel:`DYMO LabelWriter 450 DUO Label` (or whichever DYMO printer model is being used). Click into the printer that was just installed." +msgstr "" + +#: ../../content/applications/general/iot/config/troubleshooting.rst:-1 +msgid "Printer page with newly installed printer highlighted." +msgstr "" + +#: ../../content/applications/general/iot/config/troubleshooting.rst:485 +msgid "To print a test label, click on the :guilabel:`Maintenance` drop-down menu to the left of the :guilabel:`Administration` drop-down menu, and select :guilabel:`Print Test Page`. The test label should print out immediately (one-to-two seconds delay)." +msgstr "" + +#: ../../content/applications/general/iot/config/troubleshooting.rst:495 +msgid "The Zebra printer does not print anything" +msgstr "" + +#: ../../content/applications/general/iot/config/troubleshooting.rst:497 +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:504 +msgid "Check out Zebra's instructions on printing :abbr:`ZPL (Zebra Programming Language)` files `here `_." +msgstr "" + +#: ../../content/applications/general/iot/config/troubleshooting.rst:511 +msgid "The characters read by the barcode scanner do not match the barcode" +msgstr "" + +#: ../../content/applications/general/iot/config/troubleshooting.rst:513 +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:518 +msgid "Nothing happens when a barcode is scanned" +msgstr "" + +#: ../../content/applications/general/iot/config/troubleshooting.rst:520 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 +#: ../../content/applications/general/iot/config/troubleshooting.rst:526 msgid "The barcode scanner is detected as a keyboard" msgstr "" -#: ../../content/applications/general/iot/config/troubleshooting.rst:381 +#: ../../content/applications/general/iot/config/troubleshooting.rst:529 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 +#: ../../content/applications/general/iot/config/troubleshooting.rst:532 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 "" @@ -4363,15 +4978,15 @@ msgstr "" msgid "Modifying the form view of the barcode scanner." msgstr "" -#: ../../content/applications/general/iot/config/troubleshooting.rst:392 +#: ../../content/applications/general/iot/config/troubleshooting.rst:540 msgid "Barcode scanner processes barcode characters individually" msgstr "" -#: ../../content/applications/general/iot/config/troubleshooting.rst:394 +#: ../../content/applications/general/iot/config/troubleshooting.rst:542 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 +#: ../../content/applications/general/iot/config/troubleshooting.rst:548 msgid "Access the barcode scanner form page by navigating to :menuselection:`IoT App --> Devices --> Barcode Scanner`." msgstr "" @@ -4379,43 +4994,43 @@ msgstr "" msgid "Barcode scanner form page, with keyboard layout option highlighted." msgstr "" -#: ../../content/applications/general/iot/config/troubleshooting.rst:407 +#: ../../content/applications/general/iot/config/troubleshooting.rst:555 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 +#: ../../content/applications/general/iot/config/troubleshooting.rst:563 msgid "The cash drawer does not open" msgstr "" -#: ../../content/applications/general/iot/config/troubleshooting.rst:417 +#: ../../content/applications/general/iot/config/troubleshooting.rst:565 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 +#: ../../content/applications/general/iot/config/troubleshooting.rst:573 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 +#: ../../content/applications/general/iot/config/troubleshooting.rst:577 msgid "Set up Ariva S scales" msgstr "" -#: ../../content/applications/general/iot/config/troubleshooting.rst:431 +#: ../../content/applications/general/iot/config/troubleshooting.rst:579 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 +#: ../../content/applications/general/iot/config/troubleshooting.rst:584 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 +#: ../../content/applications/general/iot/config/troubleshooting.rst:588 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 +#: ../../content/applications/general/iot/config/troubleshooting.rst:592 msgid "Cable" msgstr "" -#: ../../content/applications/general/iot/config/troubleshooting.rst:446 +#: ../../content/applications/general/iot/config/troubleshooting.rst:594 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 "" @@ -4423,43 +5038,43 @@ msgstr "" msgid "Authentic Mettler USB to POS cable, part number 72256236." msgstr "" -#: ../../content/applications/general/iot/config/troubleshooting.rst:458 +#: ../../content/applications/general/iot/config/troubleshooting.rst:606 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 +#: ../../content/applications/general/iot/config/troubleshooting.rst:609 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 +#: ../../content/applications/general/iot/config/troubleshooting.rst:612 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 +#: ../../content/applications/general/iot/config/troubleshooting.rst:615 msgid "Next, press **>T<** until :guilabel:`GRP 3` appears, then press **>0<** to confirm." msgstr "" -#: ../../content/applications/general/iot/config/troubleshooting.rst:469 +#: ../../content/applications/general/iot/config/troubleshooting.rst:617 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 +#: ../../content/applications/general/iot/config/troubleshooting.rst:620 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 +#: ../../content/applications/general/iot/config/troubleshooting.rst:623 msgid "Now, press **>T<** until :guilabel:`EXIT` appears." msgstr "" -#: ../../content/applications/general/iot/config/troubleshooting.rst:478 +#: ../../content/applications/general/iot/config/troubleshooting.rst:626 msgid "Do **not** make any other changes unless otherwise needed." msgstr "" -#: ../../content/applications/general/iot/config/troubleshooting.rst:480 +#: ../../content/applications/general/iot/config/troubleshooting.rst:628 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 +#: ../../content/applications/general/iot/config/troubleshooting.rst:631 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 "" @@ -4543,23 +5158,138 @@ msgstr "" msgid "An alternative software for flashing the micro SD card is `Raspberry Pi Imager `_." msgstr "" +#: ../../content/applications/general/iot/config/updating_iot.rst:77 +msgid "Windows IoT update" +msgstr "" + #: ../../content/applications/general/iot/config/updating_iot.rst:79 +msgid "Windows virtual :abbr:`IoT (Internet of Things)` box may occasionally need an update to work properly." +msgstr "" + +#: ../../content/applications/general/iot/config/updating_iot.rst:82 +msgid "The following processes cover the :ref:`uninstallation ` and :ref:`re-installation ` of the Windows virtual :abbr:`IoT (Internet of Things)` box." +msgstr "" + +#: ../../content/applications/general/iot/config/updating_iot.rst:89 +#: ../../content/applications/general/iot/config/windows_iot.rst:307 +msgid "Uninstalling Windows IoT" +msgstr "" + +#: ../../content/applications/general/iot/config/updating_iot.rst:91 +msgid "Prior to upgrading the Windows virtual :abbr:`IoT (Internet of Things)` box, the previous version should be uninstalled first." +msgstr "" + +#: ../../content/applications/general/iot/config/updating_iot.rst:95 +msgid "Before uninstalling a previous version of the Windows virtual :abbr:`IoT (Internet of Things)` box, ensure that there is a newer version of Windows virtual :abbr:`IoT (Internet of Things)` box available, compared to the version currently installed. To do so, navigate to the `Odoo Nightly builds `_ page." +msgstr "" + +#: ../../content/applications/general/iot/config/updating_iot.rst:100 +msgid "On the :guilabel:`Odoo Nightly builds` page, navigate to :menuselection:`Builds (stable version) --> windows/` to view the date next to the :file:`odoo_(version).latest.exe` file; where *(version)* is equal to the version of Odoo (e.g. 16.0, 17.0). The latest version of the Windows virtual :abbr:`IoT (Internet of Things)` box can be downloaded by selecting this file, or it is always available at the `Odoo Download `_ page." +msgstr "" + +#: ../../content/applications/general/iot/config/updating_iot.rst:106 +msgid "Uninstalling the Windows virtual :abbr:`IoT (Internet of Things)` box is done through the Windows program manager." +msgstr "" + +#: ../../content/applications/general/iot/config/updating_iot.rst:109 +msgid "On any version of Windows, search for `program` to open the :menuselection:`Programs --> Programs and Features` section of the :guilabel:`Control Panel`. Then, select :guilabel:`Uninstall or change a program`. Next, search for `Odoo`, and click the :guilabel:`... (three dot)` menu on the :guilabel:`Odoo.exe` program to uninstall." +msgstr "" + +#: ../../content/applications/general/iot/config/updating_iot.rst:114 +msgid "Confirm the uninstallation, and follow the steps to uninstall through the Odoo uninstall wizard." +msgstr "" + +#: ../../content/applications/general/iot/config/updating_iot.rst:119 +msgid "Download and re-install" +msgstr "" + +#: ../../content/applications/general/iot/config/updating_iot.rst:121 +msgid "The latest version of the Windows virtual :abbr:`IoT (Internet of Things)` box can be downloaded from the `Odoo Nightly builds `_ page or it is always available at the `Odoo Download `_ page." +msgstr "" + +#: ../../content/applications/general/iot/config/updating_iot.rst:125 +msgid "To download from the :guilabel:`Odoo Nightly builds` page, navigate to :menuselection:`Builds (stable version) --> windows/` to and select the :file:`odoo_(version).latest.exe` file; where *(version)* is equal to the version of Odoo (e.g. 16.0, 17.0)." +msgstr "" + +#: ../../content/applications/general/iot/config/updating_iot.rst:129 +msgid "To download from the :guilabel:`Odoo Download` page, find the section for the version of Odoo (e.g. 16.0, 17.0), and select the :guilabel:`Download` button for :guilabel:`Windows`." +msgstr "" + +#: ../../content/applications/general/iot/config/updating_iot.rst:132 +msgid "Next, install and setup the downloaded Odoo :file:`.exe` file. After the instructions screen, click :guilabel:`Next` to start the installation, and agree to the :abbr:`TOS (Terms of Service)`." +msgstr "" + +#: ../../content/applications/general/iot/config/updating_iot.rst:135 +msgid "During the next step of the re-installation, select :guilabel:`Odoo IoT` from the :guilabel:`Select the type of install` drop-down menu." +msgstr "" + +#: ../../content/applications/general/iot/config/updating_iot.rst:139 +#: ../../content/applications/general/iot/config/windows_iot.rst:50 +msgid "For reference, the following should be installed:" +msgstr "" + +#: ../../content/applications/general/iot/config/updating_iot.rst:141 +msgid ":guilabel:`Odoo server`" +msgstr "" + +#: ../../content/applications/general/iot/config/updating_iot.rst:142 +msgid ":guilabel:`Odoo IoT`" +msgstr "" + +#: ../../content/applications/general/iot/config/updating_iot.rst:143 +msgid ":guilabel:`Nginx WebServer`" +msgstr "" + +#: ../../content/applications/general/iot/config/updating_iot.rst:144 +msgid ":guilabel:`Ghostscript interpreter`" +msgstr "" + +#: ../../content/applications/general/iot/config/updating_iot.rst:146 +msgid "Ensure there is enough space on the computer for the installation, then click :guilabel:`Next`." +msgstr "" + +#: ../../content/applications/general/iot/config/updating_iot.rst:149 +msgid "Set the destination and complete the installation" +msgstr "" + +#: ../../content/applications/general/iot/config/updating_iot.rst:151 +msgid "To complete the re-installation, select the :guilabel:`Destination Folder`, and click :guilabel:`Install`." +msgstr "" + +#: ../../content/applications/general/iot/config/updating_iot.rst:155 +msgid "Choosing `C:\\\\odoo` as the install location allows for the *Nginx* server to start. Odoo's Windows virtual :abbr:`IoT (Internet of Things)` box software should **not** be installed inside any of the Windows user's directories. Doing so does **not** allow for *Nginx* to initialize." +msgstr "" + +#: ../../content/applications/general/iot/config/updating_iot.rst:159 +#: ../../content/applications/general/iot/config/windows_iot.rst:74 +msgid "The installation may take a few minutes. When complete, click :guilabel:`Next` to continue." +msgstr "" + +#: ../../content/applications/general/iot/config/updating_iot.rst:161 +msgid "Then, ensure that the :guilabel:`Start Odoo` box is checked, and click :guilabel:`Finish`. After installation, the Odoo server runs, and automatically opens `http://localhost:8069` on a web browser. The webpage should display the :abbr:`IoT (Internet of Things)` box homepage." +msgstr "" + +#: ../../content/applications/general/iot/config/updating_iot.rst:166 +msgid "A :ref:`restart ` of the Windows IoT program may be necessary if the web browser does not display anything." +msgstr "" + +#: ../../content/applications/general/iot/config/updating_iot.rst:172 msgid "Update from the IoT box home page" msgstr "" -#: ../../content/applications/general/iot/config/updating_iot.rst:81 +#: ../../content/applications/general/iot/config/updating_iot.rst:174 msgid "In the background, the :abbr:`IoT (Internet of Things)` box uses a version of Odoo code to run and connect to the Odoo database. This code may need to be updated in order for the :abbr:`IoT (Internet of Things)` box to operate effectively. This operation should be completed on a routine basis, to ensure the :abbr:`IoT (Internet of Things)` system, and its processes, stay up-to-date." msgstr "" -#: ../../content/applications/general/iot/config/updating_iot.rst:86 +#: ../../content/applications/general/iot/config/updating_iot.rst:179 msgid "Go to the :abbr:`IoT (Internet of Things)` box home page by navigating to :menuselection:`IoT app --> IoT Boxes`, and clicking on the :guilabel:`IP address` of the :abbr:`IoT (Internet of Things)` box. Then, click on :guilabel:`Update` (next to the version number)." msgstr "" -#: ../../content/applications/general/iot/config/updating_iot.rst:90 +#: ../../content/applications/general/iot/config/updating_iot.rst:183 msgid "If a new version of the :abbr:`IoT (Internet of Things)` box image is available, an :guilabel:`Upgrade to _xx.xx_` button appears at the bottom of the page. Click this button to upgrade the unit, at which point the :abbr:`IoT (Internet of Things)` box flashes itself to the newer version. All of the previous configurations are then saved." msgstr "" -#: ../../content/applications/general/iot/config/updating_iot.rst:96 +#: ../../content/applications/general/iot/config/updating_iot.rst:189 msgid "This process can take more than 30 minutes. Do **not** turn off, or unplug, the :abbr:`IoT (Internet of Things)` box, as it would leave it in an inconsistent state. This means the :abbr:`IoT (Internet of Things)` box needs to be :ref:`re-flashed ` with a new image." msgstr "" @@ -4567,23 +5297,23 @@ msgstr "" msgid "IoT box software upgrade in the IoT Box Home Page." msgstr "" -#: ../../content/applications/general/iot/config/updating_iot.rst:106 +#: ../../content/applications/general/iot/config/updating_iot.rst:199 msgid "Handler (driver) update" msgstr "" -#: ../../content/applications/general/iot/config/updating_iot.rst:108 +#: ../../content/applications/general/iot/config/updating_iot.rst:201 msgid "There may be some instances where drivers or interfaces need to be updated for individual devices (e.g. scales, measurement tools, etc.). The IoT handler's (drivers and interfaces) code can be modified by syncing them with the configured server handler's code." msgstr "" -#: ../../content/applications/general/iot/config/updating_iot.rst:112 +#: ../../content/applications/general/iot/config/updating_iot.rst:205 msgid "This can be helpful in instances where :abbr:`IoT (Internet of Things)` devices (e.g. scales, measurement tools, etc.) are not working properly with the :abbr:`IoT (Internet of Things)` box." msgstr "" -#: ../../content/applications/general/iot/config/updating_iot.rst:115 +#: ../../content/applications/general/iot/config/updating_iot.rst:208 msgid "For both the Windows :abbr:`IoT (Internet of Things)` (Odoo 16 and higher) and physical :abbr:`IoT (Internet of Things)` box, this process can be performed manually from the :abbr:`IoT (Internet of Things)` box home page. Go to the :abbr:`IoT (Internet of Things)` box home page by navigating to :menuselection:`IoT app --> IoT Boxes`, and clicking on the :guilabel:`IP address` of the :abbr:`IoT (Internet of Things)` box." msgstr "" -#: ../../content/applications/general/iot/config/updating_iot.rst:121 +#: ../../content/applications/general/iot/config/updating_iot.rst:214 msgid "Next, click :guilabel:`Handlers list`, and then select :guilabel:`Load Handlers` at the bottom of the page." msgstr "" @@ -4591,11 +5321,11 @@ msgstr "" msgid "Handlers list on an IoT box with the load handlers button highlighted." msgstr "" -#: ../../content/applications/general/iot/config/updating_iot.rst:129 +#: ../../content/applications/general/iot/config/updating_iot.rst:222 msgid "Handler's code is fetched from the configured server, and it needs to be up-to-date to have the latest fixes and patches." msgstr "" -#: ../../content/applications/general/iot/config/updating_iot.rst:133 +#: ../../content/applications/general/iot/config/updating_iot.rst:226 msgid "A handler update is also performed automatically each time the :abbr:`IoT (Internet of Things)` box is restarted. The only exception to this process is if the *Automatic drivers update* is unchecked in the form view of the :abbr:`IoT (Internet of Things)` box on the Odoo server. This setting can be reached by going to :menuselection:`IoT App --> Select the IoT box --> Automatic drivers update`." msgstr "" @@ -4663,10 +5393,6 @@ msgstr "" msgid "During the next step of the installation, select :guilabel:`Odoo IoT` from the :guilabel:`Select the type of install` drop-down menu." msgstr "" -#: ../../content/applications/general/iot/config/windows_iot.rst:50 -msgid "For reference, the following should be installed:" -msgstr "" - #: ../../content/applications/general/iot/config/windows_iot.rst:52 msgid "**Odoo server**" msgstr "" @@ -4703,10 +5429,6 @@ msgstr "" msgid "Odoo's Windows virtual IoT software should not be installed inside any of the Window's User's directories. Doing so will not allow for Nginx to initialize." msgstr "" -#: ../../content/applications/general/iot/config/windows_iot.rst:74 -msgid "The installation may take a few minutes. When complete, click :guilabel:`Next` to continue." -msgstr "" - #: ../../content/applications/general/iot/config/windows_iot.rst:76 msgid "Ensure that the :guilabel:`Start Odoo` box is checked and click :guilabel:`Finish`. After installation, the Odoo server will run and automatically open `http://localhost:8069` on a web browser. The webpage should display the :abbr:`IoT (Internet of Things)` box homepage." msgstr "" @@ -4836,7 +5558,7 @@ msgid "Configure new rule" msgstr "" #: ../../content/applications/general/iot/config/windows_iot.rst:182 -msgid "On the :menuselection:`Rule Type` screen, select :guilabel:`Port`. Then click :guilabel:`Next`. From the :menuselection:`Protocol and Ports` page leave the rule application to :guilabel:`TCP`. Then, select :guilabel:`Specific Local Ports` for the :guilabel:`ports` option. In the text box, type in `8069`. Finally click :guilabel:`Next` to continue to the next step." +msgid "On the :menuselection:`Rule Type` screen, select :guilabel:`Port`. Then click :guilabel:`Next`. From the :menuselection:`Protocol and Ports` page leave the rule application to :guilabel:`TCP`. Then, select :guilabel:`Specific Local Ports` for the :guilabel:`ports` option. In the text box, type in `8069, 443`. Finally, click :guilabel:`Next` to continue to the next step." msgstr "" #: ../../content/applications/general/iot/config/windows_iot.rst:187 @@ -4847,27 +5569,27 @@ msgstr "" msgid "Finally, assign a new, unique name to the rule. For example, this name can be `Odoo`. Optionally, add a brief description in the :guilabel:`Description` field. Click :guilabel:`Finish` to complete the :guilabel:`Rule Configuration` wizard. Now, the new rule is active and devices can connect to the Windows virtual :abbr:`IoT (Internet of Things)` box." msgstr "" -#: ../../content/applications/general/iot/config/windows_iot.rst:200 +#: ../../content/applications/general/iot/config/windows_iot.rst:202 msgid "Worldline exception" msgstr "" -#: ../../content/applications/general/iot/config/windows_iot.rst:202 -msgid "*Worldline* is a payment terminal that can be connected to Odoo's *PoS* (point of sale) system. It allows for a comprehensive and fluid payment experience for customers. Worldline is available in Benelux (coalition of Belgium, the Netherlands, and Luxembourg)." +#: ../../content/applications/general/iot/config/windows_iot.rst:204 +msgid "*Worldline* is a payment terminal that can be connected to Odoo's *PoS* (point of sale) system. It allows for a comprehensive and fluid payment experience for customers. Worldline is available in Belgium, the Netherlands, and Luxembourg." msgstr "" -#: ../../content/applications/general/iot/config/windows_iot.rst:206 +#: ../../content/applications/general/iot/config/windows_iot.rst:208 msgid "When using the Windows IoT server to connect the Worldline payment terminal, it is necessary to create an exception in the Windows firewall so that a connection can be made between the Odoo database/:abbr:`IoT (Internet of Things)` box and Worldline." msgstr "" -#: ../../content/applications/general/iot/config/windows_iot.rst:211 +#: ../../content/applications/general/iot/config/windows_iot.rst:213 msgid ":doc:`../../../sales/point_of_sale/payment_methods/terminals/worldline`" msgstr "" -#: ../../content/applications/general/iot/config/windows_iot.rst:213 +#: ../../content/applications/general/iot/config/windows_iot.rst:215 msgid "To create the exception, first, open the *Windows Defender Firewall* app on the Windows machine. This can be accomplished by typing `windows defender` in the :guilabel:`Search` bar." msgstr "" -#: ../../content/applications/general/iot/config/windows_iot.rst:216 +#: ../../content/applications/general/iot/config/windows_iot.rst:218 msgid "Next, click :guilabel:`Advanced settings` in the left menu." msgstr "" @@ -4875,7 +5597,7 @@ msgstr "" msgid "Advanced settings option highlighted in the left pane of the Windows Defender Firewall app." msgstr "" -#: ../../content/applications/general/iot/config/windows_iot.rst:222 +#: ../../content/applications/general/iot/config/windows_iot.rst:224 msgid "In the left menu, choose :guilabel:`Inbound Rules`." msgstr "" @@ -4883,7 +5605,7 @@ msgstr "" msgid "Windows Defender left window pane with inbound rules menu item highlighted." msgstr "" -#: ../../content/applications/general/iot/config/windows_iot.rst:228 +#: ../../content/applications/general/iot/config/windows_iot.rst:230 msgid "After selecting :guilabel:`Inbound Rules`, select :guilabel:`New Rule` in the far right menu." msgstr "" @@ -4891,7 +5613,7 @@ msgstr "" msgid "New rule dropdown shown with new rule option highlighted." msgstr "" -#: ../../content/applications/general/iot/config/windows_iot.rst:234 +#: ../../content/applications/general/iot/config/windows_iot.rst:236 msgid "Then, for the :guilabel:`Rule Type`, select the radio button for :guilabel:`Port`. Click :guilabel:`Next` to continue to the rest of the configuration." msgstr "" @@ -4899,11 +5621,11 @@ msgstr "" msgid "Rule Type window open, with the radio button next to port highlighted." msgstr "" -#: ../../content/applications/general/iot/config/windows_iot.rst:241 +#: ../../content/applications/general/iot/config/windows_iot.rst:243 msgid "On the :guilabel:`Protocols and Ports` page, choose the radio button for :guilabel:`TCP`, under :guilabel:`Does this rule apply to TCP or UDP?`." msgstr "" -#: ../../content/applications/general/iot/config/windows_iot.rst:244 +#: ../../content/applications/general/iot/config/windows_iot.rst:246 msgid "Next, under :guilabel:`Does this rule apply to all local ports or specific ports?`, select the radio button for :guilabel:`Specific local ports`. Then, enter `9050`, and click :guilabel:`Next` to continue." msgstr "" @@ -4911,139 +5633,135 @@ msgstr "" msgid "Protocol/port configuration window with TCP, specific port (9050) and Next highlighted." msgstr "" -#: ../../content/applications/general/iot/config/windows_iot.rst:252 +#: ../../content/applications/general/iot/config/windows_iot.rst:254 msgid "The next screen is the :guilabel:`Action` page. Under :guilabel:`What action should be taken when a connection matches the specified conditions?`, choose the radio button for :guilabel:`Allow the connection`. Then, click :guilabel:`Next` to continue." msgstr "" -#: ../../content/applications/general/iot/config/windows_iot.rst:256 +#: ../../content/applications/general/iot/config/windows_iot.rst:258 msgid "A :guilabel:`Profile` page appears. Under :guilabel:`When does this rule apply?`, leave the three boxes checked for: :guilabel:`Domain`, :guilabel:`Private`, and :guilabel:`Public`. Click :guilabel:`Next` to continue to the naming convention page." msgstr "" -#: ../../content/applications/general/iot/config/windows_iot.rst:260 +#: ../../content/applications/general/iot/config/windows_iot.rst:262 msgid "On the :guilabel:`Name` page, enter `Odoo Worldline`, under the :guilabel:`Name` field. Enter a :guilabel:`Description (optional)`. Finally, once ready, click :guilabel:`Finish`." msgstr "" -#: ../../content/applications/general/iot/config/windows_iot.rst:263 +#: ../../content/applications/general/iot/config/windows_iot.rst:265 msgid "The final :guilabel:`Inbound rule` should appear as follows:" msgstr "" -#: ../../content/applications/general/iot/config/windows_iot.rst:270 +#: ../../content/applications/general/iot/config/windows_iot.rst:272 msgid "Odoo Worldline" msgstr "" -#: ../../content/applications/general/iot/config/windows_iot.rst:271 +#: ../../content/applications/general/iot/config/windows_iot.rst:273 msgid "Profile" msgstr "" -#: ../../content/applications/general/iot/config/windows_iot.rst:272 +#: ../../content/applications/general/iot/config/windows_iot.rst:274 msgid "All" msgstr "" -#: ../../content/applications/general/iot/config/windows_iot.rst:273 +#: ../../content/applications/general/iot/config/windows_iot.rst:275 msgid "Enabled" msgstr "" -#: ../../content/applications/general/iot/config/windows_iot.rst:274 +#: ../../content/applications/general/iot/config/windows_iot.rst:276 msgid "Yes" msgstr "" -#: ../../content/applications/general/iot/config/windows_iot.rst:275 +#: ../../content/applications/general/iot/config/windows_iot.rst:277 msgid "Action" msgstr "" -#: ../../content/applications/general/iot/config/windows_iot.rst:276 +#: ../../content/applications/general/iot/config/windows_iot.rst:278 msgid "Allow" msgstr "" -#: ../../content/applications/general/iot/config/windows_iot.rst:277 +#: ../../content/applications/general/iot/config/windows_iot.rst:279 msgid "Override" msgstr "" -#: ../../content/applications/general/iot/config/windows_iot.rst:278 +#: ../../content/applications/general/iot/config/windows_iot.rst:280 msgid "No" msgstr "" -#: ../../content/applications/general/iot/config/windows_iot.rst:279 +#: ../../content/applications/general/iot/config/windows_iot.rst:281 msgid "Program" msgstr "" -#: ../../content/applications/general/iot/config/windows_iot.rst:280 #: ../../content/applications/general/iot/config/windows_iot.rst:282 #: ../../content/applications/general/iot/config/windows_iot.rst:284 -#: ../../content/applications/general/iot/config/windows_iot.rst:290 +#: ../../content/applications/general/iot/config/windows_iot.rst:286 #: ../../content/applications/general/iot/config/windows_iot.rst:292 #: ../../content/applications/general/iot/config/windows_iot.rst:294 #: ../../content/applications/general/iot/config/windows_iot.rst:296 #: ../../content/applications/general/iot/config/windows_iot.rst:298 -#: ../../content/applications/general/iot/config/windows_iot.rst:302 +#: ../../content/applications/general/iot/config/windows_iot.rst:300 +#: ../../content/applications/general/iot/config/windows_iot.rst:304 msgid "Any" msgstr "" -#: ../../content/applications/general/iot/config/windows_iot.rst:281 +#: ../../content/applications/general/iot/config/windows_iot.rst:283 msgid "Local Address" msgstr "" -#: ../../content/applications/general/iot/config/windows_iot.rst:283 +#: ../../content/applications/general/iot/config/windows_iot.rst:285 msgid "Remote Address" msgstr "" -#: ../../content/applications/general/iot/config/windows_iot.rst:285 +#: ../../content/applications/general/iot/config/windows_iot.rst:287 msgid "Protocol" msgstr "" -#: ../../content/applications/general/iot/config/windows_iot.rst:286 +#: ../../content/applications/general/iot/config/windows_iot.rst:288 msgid "TCP" msgstr "" -#: ../../content/applications/general/iot/config/windows_iot.rst:287 +#: ../../content/applications/general/iot/config/windows_iot.rst:289 msgid "Local Port" msgstr "" -#: ../../content/applications/general/iot/config/windows_iot.rst:288 +#: ../../content/applications/general/iot/config/windows_iot.rst:290 msgid "9050" msgstr "" -#: ../../content/applications/general/iot/config/windows_iot.rst:289 +#: ../../content/applications/general/iot/config/windows_iot.rst:291 msgid "Remote Port" msgstr "" -#: ../../content/applications/general/iot/config/windows_iot.rst:291 +#: ../../content/applications/general/iot/config/windows_iot.rst:293 msgid "Authorized Users" msgstr "" -#: ../../content/applications/general/iot/config/windows_iot.rst:293 +#: ../../content/applications/general/iot/config/windows_iot.rst:295 msgid "Authorized Computers" msgstr "" -#: ../../content/applications/general/iot/config/windows_iot.rst:295 +#: ../../content/applications/general/iot/config/windows_iot.rst:297 msgid "Authorized Local Principals" msgstr "" -#: ../../content/applications/general/iot/config/windows_iot.rst:297 +#: ../../content/applications/general/iot/config/windows_iot.rst:299 msgid "Local User Owner" msgstr "" -#: ../../content/applications/general/iot/config/windows_iot.rst:299 +#: ../../content/applications/general/iot/config/windows_iot.rst:301 msgid "PolicyAppld" msgstr "" -#: ../../content/applications/general/iot/config/windows_iot.rst:300 +#: ../../content/applications/general/iot/config/windows_iot.rst:302 msgid "None" msgstr "" -#: ../../content/applications/general/iot/config/windows_iot.rst:301 +#: ../../content/applications/general/iot/config/windows_iot.rst:303 msgid "Application Package" msgstr "" -#: ../../content/applications/general/iot/config/windows_iot.rst:305 -msgid "Uninstalling Windows IoT" -msgstr "" - -#: ../../content/applications/general/iot/config/windows_iot.rst:307 +#: ../../content/applications/general/iot/config/windows_iot.rst:309 msgid "Uninstalling the Windows virtual :abbr:`IoT (Internet of Things)` box is done through the Windows program manager. Using any Windows version, search for `program`. Then, select :guilabel:`Add or Remove Programs` located in the control panel. Search for `Odoo` and click the :guilabel:`three dot menu` to uninstall." msgstr "" -#: ../../content/applications/general/iot/config/windows_iot.rst:312 +#: ../../content/applications/general/iot/config/windows_iot.rst:314 msgid "Confirm the un-installation and follow the steps to uninstall through the Odoo uninstall guide." msgstr "" @@ -5062,7 +5780,7 @@ 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/scale.rst:22 #: ../../content/applications/general/iot/devices/screen.rst:18 msgid "Connection" msgstr "" @@ -5401,15 +6119,31 @@ msgstr "" 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:10 +msgid "In EU member states, `certification is legally required `_ to use a scale as an integrated device." +msgstr "" + #: ../../content/applications/general/iot/devices/scale.rst:12 +msgid "Odoo is not certified in several countries, including France, Germany, and Switzerland. If you reside in one of these countries, you can still use a scale but without integration to your Odoo database." +msgstr "" + +#: ../../content/applications/general/iot/devices/scale.rst:15 +msgid "Alternatively, you have the option to acquire a *non-integrated* certified scale that prints certified labels, which can then be scanned into your Odoo database." +msgstr "" + +#: ../../content/applications/general/iot/devices/scale.rst:19 +msgid "`Directive 2014/31/EU of the European Parliament `_" +msgstr "" + +#: ../../content/applications/general/iot/devices/scale.rst:24 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 +#: ../../content/applications/general/iot/devices/scale.rst:28 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 +#: ../../content/applications/general/iot/devices/scale.rst:30 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 "" @@ -5417,7 +6151,7 @@ msgstr "" msgid "IOT box auto detection." msgstr "" -#: ../../content/applications/general/iot/devices/scale.rst:25 +#: ../../content/applications/general/iot/devices/scale.rst:37 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 "" @@ -5425,19 +6159,19 @@ msgstr "" msgid "View of the IoT box settings and driver list." msgstr "" -#: ../../content/applications/general/iot/devices/scale.rst:34 +#: ../../content/applications/general/iot/devices/scale.rst:46 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 +#: ../../content/applications/general/iot/devices/scale.rst:51 msgid "Use a scale in a point of sale (POS) system" msgstr "" -#: ../../content/applications/general/iot/devices/scale.rst:41 +#: ../../content/applications/general/iot/devices/scale.rst:53 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 +#: ../../content/applications/general/iot/devices/scale.rst:57 msgid "Select the scale from the :guilabel:`Electronic Scale` drop-down menu. Then click :guilabel:`Save` to save the changes, if required." msgstr "" @@ -5445,7 +6179,7 @@ msgstr "" 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 +#: ../../content/applications/general/iot/devices/scale.rst:64 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 "" @@ -5572,11 +6306,12 @@ msgid "Open the screen form view by accessing :menuselection:`IoT app --> Device msgstr "" #: ../../content/applications/general/users.rst:5 +#: ../../content/applications/general/users/access_rights.rst:32 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. An administrator can add as many users as the company needs and, in order to restrict the type of information each user can access, rules can be applied to each user. Users and access rights can be added and changed at any point." msgstr "" #: ../../content/applications/general/users.rst:12 @@ -5587,151 +6322,247 @@ msgstr "" msgid ":doc:`users/access_rights`" msgstr "" -#: ../../content/applications/general/users.rst:18 -msgid "Add individual users" +#: ../../content/applications/general/users.rst:14 +msgid ":ref:`access-rights/superuser`" +msgstr "" + +#: ../../content/applications/general/users.rst:15 +msgid ":ref:`access-rights/groups`" msgstr "" #: ../../content/applications/general/users.rst:20 -msgid "Go to :menuselection:`Settings --> Manage Users` and click on *Create*." +msgid "Add individual users" +msgstr "" + +#: ../../content/applications/general/users.rst:22 +msgid "To add new users, navigate to :menuselection:`Settings app --> Users section --> Manage Users`, and click on :guilabel:`New`." 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." +msgid "View of the settings page emphasizing the manage users field in Odoo." msgstr "" #: ../../content/applications/general/users.rst:29 +msgid "Fill in the form with all the required information. Under the :doc:`Access Rights ` tab, choose the group within each application the user can have access to." +msgstr "" + +#: ../../content/applications/general/users.rst:32 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" +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." +#: ../../content/applications/general/users.rst:38 +msgid "After filling out all the necessary fields on the page, manually :guilabel:`Save`. An invitation email is automatically sent to the user, using the email in the :guilabel:`Email Address` field. The user must click on the link included in the email to accept the invitation, and to create a database 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" +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." +#: ../../content/applications/general/users.rst:48 +msgid "If the company is on a monthly subscription plan, the database automatically updates to reflect the added users. If the company is on a yearly or multi-year plan, an expiration banner appears in the database. An upsell quotation can be created by clicking the banner to update the subscription. Alternatively, `send a support ticket `_ to resolve the issue." msgstr "" -#: ../../content/applications/general/users.rst:45 -msgid "With the :ref:`developer mode ` activated, *User Types* can be selected." +#: ../../content/applications/general/users.rst:55 +msgid "User type" 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" +#: ../../content/applications/general/users.rst:57 +msgid ":guilabel:`User Type` can be selected from the :guilabel:`Access Rights` tab of the user form, accessible via :menuselection:`Settings app --> Users section --> Manage 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*." +msgid "There are three types of users: :guilabel:`Internal User`, :guilabel:`Portal`, and :guilabel:`Public`." msgstr "" -#: ../../content/applications/general/users.rst:64 -msgid "**Never** deactivate the main user (*admin*)." +#: ../../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:69 -msgid "Passwords management" +#: ../../content/applications/general/users.rst:68 +msgid "Users are considered internal database users. Portal users are external users, who only have access to the database portal to view records. See the documentation on :doc:`users/portal`." msgstr "" -#: ../../content/applications/general/users.rst:74 -msgid "Reset passwords" +#: ../../content/applications/general/users.rst:71 +msgid "Public users are those visiting websites, via the website's frontend." msgstr "" -#: ../../content/applications/general/users.rst:79 -msgid "Enable password resets from login page" +#: ../../content/applications/general/users.rst:73 +msgid "The :guilabel:`Portal` and :guilabel:`Public` user options do **not** allow the administrator to choose access rights. These users have specific access rights pre-set (such as, record rules and restricted menus), and usually do not belong to the usual Odoo groups." msgstr "" -#: ../../content/applications/general/users.rst:81 -msgid "It is possible to enable password resets directly from the login page." +#: ../../content/applications/general/users.rst:80 +msgid "Deactivate users" msgstr "" -#: ../../content/applications/general/users.rst:83 -msgid "To do so, go to :menuselection:`Settings --> Permissions`, activate **Password Reset** and *Save*." +#: ../../content/applications/general/users.rst:82 +msgid "To deactivate (i.e. archive) a user, navigate to :menuselection:`Settings app --> Users section --> Manage Users`. Then, tick the checkbox to the left of the user(s) to be deactivated." +msgstr "" + +#: ../../content/applications/general/users.rst:85 +msgid "After selecting the appropriate user to be archived, click the :guilabel:`⚙️ Actions` icon, and select :guilabel:`Archive` from the resulting drop-down menu. Then, click :guilabel:`OK` from the :guilabel:`Confirmation` pop-up window that appears." +msgstr "" + +#: ../../content/applications/general/users.rst:90 +msgid "**Never** deactivate the main/administrator user (admin). Making changes to admin users can have a detrimental impact on the database. This includes *impotent admin*, which means that no user in the database can make changes to the access rights. For this reason, Odoo recommends contacting an Odoo Business Analyst, or our Support Team, before making changes." +msgstr "" + +#: ../../content/applications/general/users.rst:96 +msgid "Error: too many users" +msgstr "" + +#: ../../content/applications/general/users.rst:98 +msgid "If there are more users in an Odoo database than provisioned in the Odoo Enterprise subscription, the following message is displayed." +msgstr "" + +#: ../../content/applications/general/users.rst:-1 +msgid "Too many users on a database error message." +msgstr "" + +#: ../../content/applications/general/users.rst:105 +msgid "When the message appears, the database administrator has 30 days to act before the database expires. The countdown is updated every day." +msgstr "" + +#: ../../content/applications/general/users.rst:108 +msgid "To resolve the issue, either:" +msgstr "" + +#: ../../content/applications/general/users.rst:110 +msgid "Add more users to the 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/applications/general/users.rst:112 +msgid ":ref:`Deactivate users `, and reject the upsell quotation." +msgstr "" + +#: ../../content/applications/general/users.rst:115 +msgid "If the company is on a monthly subscription plan, the database automatically updates to reflect the added users. If the company is on a yearly or multi-year plan, an expiration banner appears in the database. An upsell quotation can be created by clicking the banner to update the subscription. Alternatively, users can `send a support ticket `_ to resolve the issue." +msgstr "" + +#: ../../content/applications/general/users.rst:121 +msgid "Once the database has the correct number of users, the expiration message disappears automatically after a few days, when the next verification occurs." +msgstr "" + +#: ../../content/applications/general/users.rst:127 +msgid "Password management" +msgstr "" + +#: ../../content/applications/general/users.rst:129 +msgid "Password management is an important part of granting users autonomous access to the database at all times. Odoo offers a few different methods to reset a user's password." +msgstr "" + +#: ../../content/applications/general/users.rst:133 +msgid "Odoo has a setting to specify the length needed for a password. This setting can be accessed by navigating to :menuselection:`Settings app --> Permissions` section, and entering the desired password length in the :guilabel:`Minimum Password Length` field. By default the value is `8`." +msgstr "" + +#: ../../content/applications/general/users.rst:-1 +msgid "Minimum Password Length highlighted in the Permissions section of General Settings." +msgstr "" + +#: ../../content/applications/general/users.rst:144 +msgid "Reset password" +msgstr "" + +#: ../../content/applications/general/users.rst:146 +msgid "Sometimes, users might wish to reset their personal password for added security, so they are the only ones with access to the password. Odoo offers two different reset options: one initiated by the user to reset the password, and another where the administrator triggers a reset." +msgstr "" + +#: ../../content/applications/general/users.rst:153 +msgid "Enable password reset from login page" +msgstr "" + +#: ../../content/applications/general/users.rst:155 +msgid "It is possible to enable/disable password resets directly from the login page. This action is completed by the individual user, and this setting is enabled by default." +msgstr "" + +#: ../../content/applications/general/users.rst:158 +msgid "To change this setting, go to :menuselection:`Settings app --> Permissions` section, activate :guilabel:`Password Reset`, and then click :guilabel:`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" +#: ../../content/applications/general/users.rst:165 +msgid "On the login page, click :guilabel:`Reset Password` to initiate the password reset process, and have a reset-token sent to the email on file." 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." +#: ../../content/applications/general/users.rst:-1 +msgid "Login screen on Odoo.com with the password reset option highlighted." 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." +#: ../../content/applications/general/users.rst:175 +msgid "Send reset instructions" msgstr "" -#: ../../content/applications/general/users.rst:101 +#: ../../content/applications/general/users.rst:177 +msgid "Go to :menuselection:`Settings app --> Users & Companies --> Users`, select the user from the list, and click on :guilabel:`Send Password Reset Instructions` on the user form. An email is automatically sent to them with password reset instructions." +msgstr "" + +#: ../../content/applications/general/users.rst:182 +msgid "The :guilabel:`Send Password Reset Instructions` button **only** appears if the Odoo invitation email has already been confirmed by the user. Otherwise, a :guilabel:`Re-send Invitation Email` button appears." +msgstr "" + +#: ../../content/applications/general/users.rst:186 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" +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" +#: ../../content/applications/general/users.rst:196 +msgid "Change user password" 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*." +#: ../../content/applications/general/users.rst:198 +msgid "Go to :menuselection:`Settings app --> Users & Companies --> Users`, and select a user to access its form. Click on the :guilabel:`⚙️ Actions` icon, and select :guilabel:`Change Password` from, the resulting drop-down menu. Enter a new password in the :guilabel:`New Password` column of the :guilabel:`Change Password` pop-up window that appears, and confirm the change by clicking :guilabel:`Change Password`." msgstr "" #: ../../content/applications/general/users.rst:-1 -msgid "Change another user's password on Odoo" +msgid "Change a user's password on Odoo." msgstr "" -#: ../../content/applications/general/users.rst:118 -msgid "Enter a new password and confirm by clicking on *Change Password*." +#: ../../content/applications/general/users.rst:209 +msgid "This operation only modifies the password of the users locally, and does **not** affect their odoo.com account." 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 `." +#: ../../content/applications/general/users.rst:212 +msgid "If the odoo.com password needs to be changed, use the :ref:`send the password reset instructions `. Odoo.com passwords grant access to the *My Databases* page, and other portal features." 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." +#: ../../content/applications/general/users.rst:216 +msgid "After clicking :guilabel:`Change Password`, the page is redirected to an Odoo login page where the database can be re-accessed using the new password." msgstr "" -#: ../../content/applications/general/users.rst:131 +#: ../../content/applications/general/users.rst:222 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." +#: ../../content/applications/general/users.rst:224 +msgid "The :guilabel:`Multi Companies` field on a user form allows an administrator to provide access to multiple companies for users. To configure a multi-company environment for a user, navigate to the desired user by going to: :menuselection:`Settings app --> Users section --> Manage users`. Then, select the user to open their user form, and configure with multi-company 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." +#: ../../content/applications/general/users.rst:229 +msgid "Under :guilabel:`Multi Companies` in the :guilabel:`Access Rights` tab, set the fields labeled :guilabel:`Allowed Companies` and :guilabel:`Default Company`." +msgstr "" + +#: ../../content/applications/general/users.rst:232 +msgid "The :guilabel:`Allowed Companies` field can contain multiple companies. These are the companies the user can access and edit, according to the set access rights. The :guilabel:`Default Company` is the company the user defaults to, upon logging in each time. This field can contain only **one** company." +msgstr "" + +#: ../../content/applications/general/users.rst:238 +msgid "If multi-company access is not configured correctly, it could lead to inconsistent multi-company behaviors. Because of this, only experienced Odoo users should make access rights changes to users for databases with a multi-company configuration. For technical explanations, refer to the developer documentation on :doc:`../../../developer/howtos/company`." msgstr "" #: ../../content/applications/general/users.rst:-1 -msgid "View of a user’s form emphasizing the multi companies field in Odoo" +msgid "View of a user's form emphasizing the multi companies field in Odoo." msgstr "" -#: ../../content/applications/general/users.rst:146 +#: ../../content/applications/general/users.rst:248 msgid ":doc:`companies`" msgstr "" @@ -5836,87 +6667,235 @@ msgid "Don't lose your authenticator, if you do, you will need an *Odoo Administ msgstr "" #: ../../content/applications/general/users/access_rights.rst:3 -msgid "Access Rights" +msgid "Access rights" msgstr "" #: ../../content/applications/general/users/access_rights.rst:5 -msgid "Activate the :ref:`developer mode `, then go to :menuselection:`Settings --> Users & Companies --> Groups`." +msgid "*Access rights* are permissions that determine the content and applications users can access and edit. In Odoo, these permissions can be set for individual users or for groups of users. Limiting permissions to only those who need them ensures that users do not modify or delete anything they should not have access to." msgstr "" -#: ../../content/applications/general/users/access_rights.rst:9 -msgid "Groups" +#: ../../content/applications/general/users/access_rights.rst:10 +msgid "**Only** an *administrator* can change access rights." msgstr "" -#: ../../content/applications/general/users/access_rights.rst:14 -msgid "When choosing the groups the user can have access under :ref:`Access Rights `, details of the rules and inheritances of that group are not shown, so this is when the menu *Groups* comes along. *Groups* are created to define rules to models within an application." +#: ../../content/applications/general/users/access_rights.rst:13 +msgid "Making changes to access rights can have a detrimental impact on the database. This includes *impotent admin*, which means that no user in the database can make changes to the access rights. For this reason, Odoo recommends contacting an Odoo Business Analyst, or our Support Team, before making changes." msgstr "" -#: ../../content/applications/general/users/access_rights.rst:16 -msgid "Under *Users*, have a list of the current ones. The ones with administrative rights are shown in black." -msgstr "" - -#: ../../content/applications/general/users/access_rights.rst:-1 -msgid "View of a group’s form emphasizing the tab users in Odoo" +#: ../../content/applications/general/users/access_rights.rst:19 +msgid "A user **must** have the specific *Administration* access rights set on their user profile, in order to make changes on another user's settings for access rights." msgstr "" #: ../../content/applications/general/users/access_rights.rst:22 -msgid "*Inherited* means that users added to this application group are automatically added to the following ones. In the example below, users who have access to the group *Administrator* of *Sales* also have access to *Website/Restricted Editor* and *Sales/User: All Documents*." +msgid "To access this setting, navigate to :menuselection:`Settings app --> Manage users --> select a user --> Access Rights tab --> Administration section --> Administration field`." +msgstr "" + +#: ../../content/applications/general/users/access_rights.rst:25 +msgid "Once at the setting, an already existing administrator **must** change the setting in the :guilabel:`Administration` field to :guilabel:`Access Rights`." +msgstr "" + +#: ../../content/applications/general/users/access_rights.rst:28 +msgid "Once complete, click :guilabel:`Save` to save the changes, and implement the user as an administrator." +msgstr "" + +#: ../../content/applications/general/users/access_rights.rst:34 +msgid "The access rights for :ref:`individual users ` are set when the user is added to the database, but they can be adjusted at any point in the user's profile." +msgstr "" + +#: ../../content/applications/general/users/access_rights.rst:37 +msgid "To make changes to a user's rights, click on the desired user to edit their profile." msgstr "" #: ../../content/applications/general/users/access_rights.rst:-1 -msgid "View of a group’s form emphasizing the tab inherited in Odoo" +msgid "Users menu in the Users & Companies section of the Settings app of Odoo." msgstr "" -#: ../../content/applications/general/users/access_rights.rst:32 -msgid "Remember to always test the settings being changed in order to ensure that they are being applied to the needed and right users." -msgstr "" - -#: ../../content/applications/general/users/access_rights.rst:35 -msgid "The *Menus* tab is where you define which menus (models) the user can have access to." -msgstr "" - -#: ../../content/applications/general/users/access_rights.rst:-1 -msgid "View of a group’s form emphasizing the tab menus in Odoo" -msgstr "" - -#: ../../content/applications/general/users/access_rights.rst:42 -msgid "*Access Rights* rules are the first level of rights. The field is composed of the object name, which is the technical name given to a model. For each model, enable the following options as appropriate:" -msgstr "" - -#: ../../content/applications/general/users/access_rights.rst:45 -msgid "*Read*: the values of that object can be only seen by the user." +#: ../../content/applications/general/users/access_rights.rst:43 +msgid "On the user's profile page, in the :guilabel:`Access Rights` tab, scroll down to view the current permissions." msgstr "" #: ../../content/applications/general/users/access_rights.rst:46 -msgid "*Write*: the values of that object can be edited by the user." +msgid "For each app, use the drop-down menu to select what level of permission this user should have. The options vary for each section, yet the most common are: :guilabel:`Blank/None`, :guilabel:`User: Own Documents`, :guilabel:`User: All Documents`, or :guilabel:`Administrator`." msgstr "" -#: ../../content/applications/general/users/access_rights.rst:47 -msgid "*Create*: values for that object can be created by the user." -msgstr "" - -#: ../../content/applications/general/users/access_rights.rst:48 -msgid "*Delete*: the values of that object can be deleted by the user." +#: ../../content/applications/general/users/access_rights.rst:50 +msgid "The :guilabel:`Administration` field in the :guilabel:`Access Rights` tab has the following options: :guilabel:`Settings` or :guilabel:`Access Rights`." msgstr "" #: ../../content/applications/general/users/access_rights.rst:-1 -msgid "View of a group’s form emphasizing the tab access rights in Odoo" +msgid "The Sales apps drop-down menu to set the user's level of permissions." msgstr "" -#: ../../content/applications/general/users/access_rights.rst:55 -msgid "As a second layer of editing and visibility rules, *Record Rules* can be formed. They overwrite, or refine, the *Access Rights*." +#: ../../content/applications/general/users/access_rights.rst:60 +msgid "Create and modify groups" msgstr "" -#: ../../content/applications/general/users/access_rights.rst:58 -msgid "A record rule is written using a *Domain*. Domains are conditions used to filter or searching data. Therefore, a domain expression is a list of conditions. For each rule, choose among the following options: *Read*, *Write*, *Create* and *Delete* values." +#: ../../content/applications/general/users/access_rights.rst:62 +msgid "*Groups* are app-specific sets of permissions that are used to manage common access rights for a large amount of users. Administrators can modify the existing groups in Odoo, or create new ones to define rules for models within an application." +msgstr "" + +#: ../../content/applications/general/users/access_rights.rst:66 +msgid "To access groups, first activate Odoo's :ref:`developer mode `, then go to :menuselection:`Settings app --> Users & Companies --> Groups`." msgstr "" #: ../../content/applications/general/users/access_rights.rst:-1 -msgid "View of a group’s form emphasizing the tab record rules in Odoo" +msgid "Groups menu in the Users & Companies section of the Settings app of Odoo." msgstr "" -#: ../../content/applications/general/users/access_rights.rst:65 -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." +#: ../../content/applications/general/users/access_rights.rst:73 +msgid "To create a new group from the :guilabel:`Groups` page, click :guilabel:`Create`. Then, from the blank group form, select an :guilabel:`Application`, and complete the group form (detailed below)." +msgstr "" + +#: ../../content/applications/general/users/access_rights.rst:76 +msgid "To modify existing groups, click on an existing group from the list displayed on the :guilabel:`Groups` page, and edit the contents of the form." +msgstr "" + +#: ../../content/applications/general/users/access_rights.rst:79 +msgid "Enter a :guilabel:`Name` for the group and tick the checkbox next to :guilabel:`Share Group`, if this group was created to set access rights for sharing data with some users." +msgstr "" + +#: ../../content/applications/general/users/access_rights.rst:83 +msgid "Always test the settings being changed to ensure they are being applied to the correct users." +msgstr "" + +#: ../../content/applications/general/users/access_rights.rst:85 +msgid "The group form contains multiple tabs for managing all elements of the group. In each tab, click :guilabel:`Add a line` to add a new row for users or rules, and click the :guilabel:`❌ (remove)` icon to remove a row." +msgstr "" + +#: ../../content/applications/general/users/access_rights.rst:-1 +msgid "Tabs in the Groups form to modify the settings of the group." +msgstr "" + +#: ../../content/applications/general/users/access_rights.rst:93 +msgid ":guilabel:`Users` tab: lists the current users in the group. Users listed in black have administrative rights. Users without administrative access appear in blue. Click :guilabel:`Add a line` to add users to this group." +msgstr "" + +#: ../../content/applications/general/users/access_rights.rst:96 +msgid ":guilabel:`Inherited` tab: inherited means that users added to this group are automatically added to the groups listed on this tab. Click :guilabel:`Add a line` to add inherited groups." +msgstr "" + +#: ../../content/applications/general/users/access_rights.rst:100 +msgid "For example, if the group *Sales/Administrator* lists the group *Website/Restricted Editor* in its :guilabel:`Inherited` tab, then any users added to the *Sales/Administrator* group automatically receive access to the *Website/Restricted Editor* group, as well." +msgstr "" + +#: ../../content/applications/general/users/access_rights.rst:104 +msgid ":guilabel:`Menus` tab: defines which menus/models the group can have access to. Click :guilabel:`Add a line` to add a specific menu." +msgstr "" + +#: ../../content/applications/general/users/access_rights.rst:106 +msgid ":guilabel:`Views` tab: lists which views in Odoo the group has access to. Click :guilabel:`Add a line` to add a view to the group." +msgstr "" + +#: ../../content/applications/general/users/access_rights.rst:108 +msgid ":guilabel:`Access Rights` tab: lists the first level of rights (models) that this group has access rights to. Click :guilabel:`Add a line` to link access rights to this group. In this tab, the :guilabel:`Model` column represents the common name of the menu/model, and the :guilabel:`Name` column represents the technical name given to the model. For each model, enable the following options as appropriate:" +msgstr "" + +#: ../../content/applications/general/users/access_rights.rst:114 +msgid ":guilabel:`Read`: users can see the object's existing values." +msgstr "" + +#: ../../content/applications/general/users/access_rights.rst:115 +msgid ":guilabel:`Write`: users can edit the object's existing values." +msgstr "" + +#: ../../content/applications/general/users/access_rights.rst:116 +msgid ":guilabel:`Create`: users can create new values for the object." +msgstr "" + +#: ../../content/applications/general/users/access_rights.rst:117 +msgid ":guilabel:`Delete`: users can delete values for the object." +msgstr "" + +#: ../../content/applications/general/users/access_rights.rst:120 +msgid "First try searching for the common name of the model in the drop-down menu of the :guilabel:`Model` column. The :guilabel:`Model` technical name can be found by expanding the model common name, which can be done by clicking the :guilabel:`(external link)` icon." +msgstr "" + +#: ../../content/applications/general/users/access_rights.rst:124 +msgid "The model technical name can also be accessed in :ref:`developer mode `." +msgstr "" + +#: ../../content/applications/general/users/access_rights.rst:126 +msgid "On a form, navigate to any field, and hover over the field name. A box of backend information reveals itself with the specific Odoo :guilabel:`Object` name in the backend. This is the technical name of the model that should be added." +msgstr "" + +#: ../../content/applications/general/users/access_rights.rst:0 +msgid "Technical information shown on a field of a model, with object highlighted." +msgstr "" + +#: ../../content/applications/general/users/access_rights.rst:134 +msgid ":guilabel:`Record Rules`: lists the second layer of editing and visibility rights. :guilabel:`Record Rules` overwrite, or refine, the group's access rights. Click :guilabel:`Add a line` to add a record rule to this group. For each rule, choose values for the following options:" +msgstr "" + +#: ../../content/applications/general/users/access_rights.rst:138 +msgid ":guilabel:`Apply for Read`." +msgstr "" + +#: ../../content/applications/general/users/access_rights.rst:139 +msgid ":guilabel:`Apply for Write`." +msgstr "" + +#: ../../content/applications/general/users/access_rights.rst:140 +msgid ":guilabel:`Apply for Create`." +msgstr "" + +#: ../../content/applications/general/users/access_rights.rst:141 +msgid ":guilabel:`Apply for Delete`." +msgstr "" + +#: ../../content/applications/general/users/access_rights.rst:144 +msgid "Record rules are written using a *domain*, or conditions that filter data. A domain expression is a list of such conditions. For example:" +msgstr "" + +#: ../../content/applications/general/users/access_rights.rst:147 +msgid "`[('mrp_production_ids', 'in', user.partner_id.commercial_partner_id.production_ids.ids)]`" +msgstr "" + +#: ../../content/applications/general/users/access_rights.rst:149 +msgid "This record rule is to enable MRP consumption warnings for subcontractors." +msgstr "" + +#: ../../content/applications/general/users/access_rights.rst:151 +msgid "Odoo has a library of preconfigured record rules for ease of use. Users without knowledge of domains (and domain expressions) should consult an Odoo Business Analyst, or the Odoo Support Team, before making changes." +msgstr "" + +#: ../../content/applications/general/users/access_rights.rst:158 +msgid "Superuser mode" +msgstr "" + +#: ../../content/applications/general/users/access_rights.rst:160 +msgid "*Superuser mode* allows the user to bypass record rules and access rights. To activate *Superuser mode*, first, activate :ref:`developer mode `. Then, navigate to the *debug* menu, represented by a :guilabel:`🪲 (bug)` icon, located in the top banner." +msgstr "" + +#: ../../content/applications/general/users/access_rights.rst:164 +msgid "Finally, towards the bottom of the menu, click :guilabel:`Become Superuser`." +msgstr "" + +#: ../../content/applications/general/users/access_rights.rst:167 +msgid "Only users with *Settings* access for the *Administration* section of the *Access Rights* (in their user profile) are allowed to log in to *Superuser mode*." +msgstr "" + +#: ../../content/applications/general/users/access_rights.rst:171 +msgid "*Superuser mode* allows for circumvention of record rules and access rights, and therefore, should be exercised with extreme caution." +msgstr "" + +#: ../../content/applications/general/users/access_rights.rst:174 +msgid "Upon exiting *Superuser mode*, users may be locked out of the database, due to changes that were made. This can cause *impotent admin*, or an administrator without the ability to change access rights/settings." +msgstr "" + +#: ../../content/applications/general/users/access_rights.rst:178 +msgid "In this case contact Odoo Support here: `new help ticket `_. The support team is able to restore access using a support login." +msgstr "" + +#: ../../content/applications/general/users/access_rights.rst:181 +msgid "To leave *Superuser mode*, log out of the account, by navigating to the upper-right corner, and clicking on the :guilabel:`OdooBot` username. Then, select the :guilabel:`Log out` option." +msgstr "" + +#: ../../content/applications/general/users/access_rights.rst:185 +msgid "An alternative way to activate *Superuser mode* is to login as a superuser. To do that, navigate to the login screen, and enter the appropriate :guilabel:`Email` and :guilabel:`Password`." +msgstr "" + +#: ../../content/applications/general/users/access_rights.rst:188 +msgid "Instead of clicking :guilabel:`Login`, click :guilabel:`Log in as superuser`." msgstr "" #: ../../content/applications/general/users/azure.rst:3 @@ -6291,35 +7270,35 @@ msgstr "" msgid "If you check the \"Websites to translate\" checkbox you will have the option to change the navigation language on your website." msgstr "" -#: ../../content/applications/general/users/language.rst:27 +#: ../../content/applications/general/users/language.rst:29 msgid "Change your language" msgstr "" -#: ../../content/applications/general/users/language.rst:29 +#: ../../content/applications/general/users/language.rst:31 msgid "You can change the language to the installed language by going to the drop-down menu at the top right side of the screen, choose **Preferences**." msgstr "" -#: ../../content/applications/general/users/language.rst:36 +#: ../../content/applications/general/users/language.rst:38 msgid "Then change the Language setting to your installed language and click **SAVE.**" msgstr "" -#: ../../content/applications/general/users/language.rst:42 +#: ../../content/applications/general/users/language.rst:44 msgid "Open a new menu to view the changes." msgstr "" -#: ../../content/applications/general/users/language.rst:45 +#: ../../content/applications/general/users/language.rst:47 msgid "Change another user's language" msgstr "" -#: ../../content/applications/general/users/language.rst:47 +#: ../../content/applications/general/users/language.rst:49 msgid "Odoo also gives you the possibility for each user to choose his preferred language." msgstr "" -#: ../../content/applications/general/users/language.rst:50 +#: ../../content/applications/general/users/language.rst:52 msgid "To change the language for a different user, choose :menuselection:`Users --> Users` from the Settings app. Here you have a list of all users and you can choose the user who you'd like to change the language for. Select the user and click on **Edit** in the top left corner. Under Preferences you can change the Language to any previously installed language and click **SAVE.**" msgstr "" -#: ../../content/applications/general/users/language.rst:61 +#: ../../content/applications/general/users/language.rst:63 msgid ":doc:`../../websites/website/configuration/translate`" msgstr "" diff --git a/locale/sources/hr.pot b/locale/sources/hr.pot index e0605c234..69b4105cd 100644 --- a/locale/sources/hr.pot +++ b/locale/sources/hr.pot @@ -8,7 +8,7 @@ msgid "" msgstr "" "Project-Id-Version: Odoo 17.0\n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2024-03-25 16:01+0000\n" +"POT-Creation-Date: 2024-04-30 09:16+0000\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME \n" "Language-Team: LANGUAGE \n" @@ -41,7 +41,7 @@ msgstr "" #: ../../content/applications/hr/appraisals.rst:18 #: ../../content/applications/hr/attendances.rst:66 #: ../../content/applications/hr/frontdesk.rst:13 -#: ../../content/applications/hr/time_off.rst:27 +#: ../../content/applications/hr/time_off.rst:28 msgid "Configuration" msgstr "" @@ -50,7 +50,8 @@ msgid "The :guilabel:`Configuration` menu in the *Appraisals* application is whe msgstr "" #: ../../content/applications/hr/appraisals.rst:25 -#: ../../content/applications/hr/fleet/configuration.rst:13 +#: ../../content/applications/hr/fleet.rst:14 +#: ../../content/applications/hr/lunch.rst:15 #: ../../content/applications/hr/payroll.rst:15 msgid "Settings" msgstr "" @@ -698,7 +699,7 @@ msgstr "" #: ../../content/applications/hr/frontdesk.rst:351 #: ../../content/applications/hr/payroll/reporting.rst:3 #: ../../content/applications/hr/referrals.rst:753 -#: ../../content/applications/hr/time_off.rst:702 +#: ../../content/applications/hr/time_off.rst:893 msgid "Reporting" msgstr "" @@ -1120,7 +1121,7 @@ msgid "The goodbye message with all the employee's check out information." msgstr "" #: ../../content/applications/hr/attendances.rst:364 -#: ../../content/applications/hr/time_off.rst:309 +#: ../../content/applications/hr/time_off.rst:745 msgid "Overview" msgstr "" @@ -1299,6 +1300,7 @@ msgid "The detailed information for an attendance entry." msgstr "" #: ../../content/applications/hr/attendances.rst:498 +#: ../../content/applications/hr/lunch/orders.rst:84 msgid "Errors" msgstr "" @@ -1457,6 +1459,8 @@ msgid "The current company phone number and name are populated in the :guilabel: msgstr "" #: ../../content/applications/hr/employees/new_employee.rst:28 +#: ../../content/applications/hr/fleet/new_vehicle.rst:106 +#: ../../content/applications/hr/fleet/service.rst:117 msgid "General information" msgstr "" @@ -1465,7 +1469,6 @@ msgid "The employee form automatically saves as data is entered. However, the fo msgstr "" #: ../../content/applications/hr/employees/new_employee.rst:35 -#: ../../content/applications/hr/payroll/contracts.rst:39 msgid "Required fields" msgstr "" @@ -1482,7 +1485,6 @@ msgid "A new employee form with the required fields highlighted." msgstr "" #: ../../content/applications/hr/employees/new_employee.rst:47 -#: ../../content/applications/hr/payroll/contracts.rst:66 #: ../../content/applications/hr/recruitment.rst:736 msgid "Optional fields" msgstr "" @@ -1556,7 +1558,7 @@ msgid "Resumé tab" msgstr "" #: ../../content/applications/hr/employees/new_employee.rst:110 -#: ../../content/applications/hr/payroll.rst:861 +#: ../../content/applications/hr/payroll.rst:869 msgid "Resumé" msgstr "" @@ -1992,7 +1994,7 @@ msgid "Depending on the localization setting, the other items that appear in thi msgstr "" #: ../../content/applications/hr/employees/new_employee.rst:509 -msgid ":guilabel:`Application Settings`: enter the employee's :guilabel:`Billing Time Target` for the billing rate leader board in the *Timesheets* application. Next, enter the :guilabel:`Hourly Cost` in a XX.XX format. This is factored in when the employee is working at a :doc:`work center <../../inventory_and_mrp/manufacturing/management/using_work_centers>`." +msgid ":guilabel:`Application Settings`: enter the employee's :guilabel:`Billing Time Target` for the billing rate leader board in the *Timesheets* application. Next, enter the :guilabel:`Hourly Cost` in a XX.XX format. This is factored in when the employee is working at a :doc:`work center <../../inventory_and_mrp/manufacturing/advanced_configuration/using_work_centers>`." msgstr "" #: ../../content/applications/hr/employees/new_employee.rst:514 @@ -2023,630 +2025,843 @@ msgstr "" msgid "All uploaded documents associated with the employee appear in the documents smart-button." msgstr "" -#: ../../content/applications/hr/fleet.rst:7 +#: ../../content/applications/hr/fleet.rst:5 msgid "Fleet" msgstr "" -#: ../../content/applications/hr/fleet.rst:9 -msgid "Odoo *Fleet* organizes all the vehicles, contracts, and repairs of all the vehicles." +#: ../../content/applications/hr/fleet.rst:7 +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:3 -msgid "Configuration menu" +#: ../../content/applications/hr/fleet.rst:16 +msgid "To access the settings menu, go to :menuselection:`Fleet application --> Configuration --> Settings`. There are only 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:5 -msgid "This document outlines all of the configurations and settings for the *Fleet* application, including :ref:`settings `, :ref:`manufacturers `, vehicle :ref:`models `, and model :ref:`categories `." -msgstr "" - -#: ../../content/applications/hr/fleet/configuration.rst:15 -msgid "To access the settings menu, go to :menuselection:`Fleet application --> Configuration --> Settings`. There are two settings that need configuration, the vehicle contract end date alert, and a new vehicle request limit." -msgstr "" - -#: ../../content/applications/hr/fleet/configuration.rst:-1 +#: ../../content/applications/hr/fleet.rst:-1 msgid "Settings available for the Fleet application." msgstr "" -#: ../../content/applications/hr/fleet/configuration.rst:24 -msgid "End date contract alert" +#: ../../content/applications/hr/fleet.rst:25 +msgid "End Date Contract Alert" msgstr "" -#: ../../content/applications/hr/fleet/configuration.rst:26 -msgid "The :guilabel:`End Date Contract Alert` field defines when an alert is sent to the persons responsible for the vehicle contracts. The responsible persons receive an email informing them when a vehicle contract is expiring. How far in advance the email is sent is defined in this field." +#: ../../content/applications/hr/fleet.rst:27 +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:`Information` section of the contract is the one who receives the alert." +#: ../../content/applications/hr/fleet.rst:32 +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 +#: ../../content/applications/hr/fleet.rst:36 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 card. On the vehicle form, click the :guilabel:`Contracts` smart button at the top of the page. The contracts associated only with this vehicle appear in the list. Click on an individual contract to open it. The :guilabel:`Responsible` person is listed on the contract." +#: ../../content/applications/hr/fleet.rst:39 +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" +#: ../../content/applications/hr/fleet.rst:46 +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. After being offered a position, an employee filling out the online salary configurator form is **not** able to request a new car if the number of existing cars is greater than the number specified in the :guilabel:`New Vehicle Request` field. Enter the specific number limit for existing available cars in this field." +#: ../../content/applications/hr/fleet.rst:48 +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 +#: ../../content/applications/hr/fleet.rst:55 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 -#: ../../content/applications/hr/fleet/configuration.rst:102 -msgid "Models" -msgstr "" - -#: ../../content/applications/hr/fleet/configuration.rst:64 +#: ../../content/applications/hr/fleet.rst:62 msgid "Manufacturers" msgstr "" -#: ../../content/applications/hr/fleet/configuration.rst:66 -msgid "Odoo *Fleet* comes pre-configured with sixty-six commonly used car manufacturers in the database, along with their logos. To view the pre-loaded manufacturers, go to :menuselection:`Fleet app --> Configuration --> Models: Manufacturers`." +#: ../../content/applications/hr/fleet.rst:64 +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:70 -msgid "The manufacturers appear in a list view in alphabetical order. Each manufacturer's card lists how many specific models are configured for each particular manufacturer. Odoo comes with forty five pre-configured :ref:`models ` from four major auto manufacturers: Audi, BMW, Mercedes, and Opel." +#: ../../content/applications/hr/fleet.rst:68 +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 +#: ../../content/applications/hr/fleet.rst:-1 msgid "Manufacturer card with the amount of models listed." msgstr "" -#: ../../content/applications/hr/fleet/configuration.rst:82 +#: ../../content/applications/hr/fleet.rst:78 msgid "Add a manufacturer" msgstr "" -#: ../../content/applications/hr/fleet/configuration.rst:84 -msgid "To add a new manufacturer to the database, click :guilabel:`New`, and a blank manufacturer form loads." +#: ../../content/applications/hr/fleet.rst:80 +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 "First, type the name of the manufacturer in the :guilabel:`Name` field. This is the only required field." +#: ../../content/applications/hr/fleet.rst:88 +msgid "Vehicle Models" msgstr "" -#: ../../content/applications/hr/fleet/configuration.rst:90 -msgid "Next, if a photo is available, hover over the image box and click the :guilabel:`✏️ (Pencil)` icon that appears in the lower-left corner." +#: ../../content/applications/hr/fleet.rst:90 +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) needs to be added to the database." msgstr "" -#: ../../content/applications/hr/fleet/configuration.rst:93 -msgid "A file explorer window pops up. Navigate to the file, then click :guilabel:`Open` to select it." +#: ../../content/applications/hr/fleet.rst:98 +msgid "Preconfigured Models" msgstr "" -#: ../../content/applications/hr/fleet/configuration.rst:95 -msgid "The manufacturer form automatically saves as data is entered. However, the form can be saved manually at any time by clicking the :guilabel:`Save manually` option, represented by a :guilabel:`(cloud with an upwards arrow)` icon." +#: ../../content/applications/hr/fleet.rst:100 +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:104 -msgid "Many manufacturers have a variety of models that they produce. Odoo comes with pre-configured car models from four major auto manufacturers: Audi, BMW, Mercedes, and Opel." -msgstr "" - -#: ../../content/applications/hr/fleet/configuration.rst:107 -msgid "If a vehicle *other* than the pre-configured models from these manufacturers is part of a fleet, the model (and/or manufacturer) **must** be added to the database." -msgstr "" - -#: ../../content/applications/hr/fleet/configuration.rst:111 -msgid "Pre-configured models" -msgstr "" - -#: ../../content/applications/hr/fleet/configuration.rst:113 -msgid "The following models are pre-configured in Odoo and do not need to be added to the database:" -msgstr "" - -#: ../../content/applications/hr/fleet/configuration.rst:116 +#: ../../content/applications/hr/fleet.rst:103 msgid "AUDI" msgstr "" -#: ../../content/applications/hr/fleet/configuration.rst:116 +#: ../../content/applications/hr/fleet.rst:103 msgid "BMW" msgstr "" -#: ../../content/applications/hr/fleet/configuration.rst:116 +#: ../../content/applications/hr/fleet.rst:103 +msgid "Eddy Merckx" +msgstr "" + +#: ../../content/applications/hr/fleet.rst:103 msgid "Mercedes" msgstr "" -#: ../../content/applications/hr/fleet/configuration.rst:116 +#: ../../content/applications/hr/fleet.rst:103 msgid "Opel" msgstr "" -#: ../../content/applications/hr/fleet/configuration.rst:118 +#: ../../content/applications/hr/fleet.rst:105 msgid "A1" msgstr "" -#: ../../content/applications/hr/fleet/configuration.rst:118 +#: ../../content/applications/hr/fleet.rst:105 msgid "Serie 1" msgstr "" -#: ../../content/applications/hr/fleet/configuration.rst:118 +#: ../../content/applications/hr/fleet.rst:105 +msgid "SanRemo76" +msgstr "" + +#: ../../content/applications/hr/fleet.rst:105 msgid "Class A" msgstr "" -#: ../../content/applications/hr/fleet/configuration.rst:118 +#: ../../content/applications/hr/fleet.rst:105 msgid "Agilia" msgstr "" -#: ../../content/applications/hr/fleet/configuration.rst:120 +#: ../../content/applications/hr/fleet.rst:107 msgid "A3" msgstr "" -#: ../../content/applications/hr/fleet/configuration.rst:120 +#: ../../content/applications/hr/fleet.rst:107 msgid "Serie 3" msgstr "" -#: ../../content/applications/hr/fleet/configuration.rst:120 +#: ../../content/applications/hr/fleet.rst:107 msgid "Class B" msgstr "" -#: ../../content/applications/hr/fleet/configuration.rst:120 +#: ../../content/applications/hr/fleet.rst:107 msgid "Ampera" msgstr "" -#: ../../content/applications/hr/fleet/configuration.rst:122 +#: ../../content/applications/hr/fleet.rst:109 msgid "A4" msgstr "" -#: ../../content/applications/hr/fleet/configuration.rst:122 +#: ../../content/applications/hr/fleet.rst:109 msgid "Serie 5" msgstr "" -#: ../../content/applications/hr/fleet/configuration.rst:122 +#: ../../content/applications/hr/fleet.rst:109 msgid "Class C" msgstr "" -#: ../../content/applications/hr/fleet/configuration.rst:122 +#: ../../content/applications/hr/fleet.rst:109 msgid "Antara" msgstr "" -#: ../../content/applications/hr/fleet/configuration.rst:124 +#: ../../content/applications/hr/fleet.rst:111 msgid "A5" msgstr "" -#: ../../content/applications/hr/fleet/configuration.rst:124 +#: ../../content/applications/hr/fleet.rst:111 msgid "Serie 6" msgstr "" -#: ../../content/applications/hr/fleet/configuration.rst:124 +#: ../../content/applications/hr/fleet.rst:111 msgid "Class CL" msgstr "" -#: ../../content/applications/hr/fleet/configuration.rst:124 +#: ../../content/applications/hr/fleet.rst:111 msgid "Astra" msgstr "" -#: ../../content/applications/hr/fleet/configuration.rst:126 +#: ../../content/applications/hr/fleet.rst:113 msgid "A6" msgstr "" -#: ../../content/applications/hr/fleet/configuration.rst:126 +#: ../../content/applications/hr/fleet.rst:113 msgid "Serie 7" msgstr "" -#: ../../content/applications/hr/fleet/configuration.rst:126 +#: ../../content/applications/hr/fleet.rst:113 msgid "Class CLS" msgstr "" -#: ../../content/applications/hr/fleet/configuration.rst:126 +#: ../../content/applications/hr/fleet.rst:113 msgid "AstraGTC" msgstr "" -#: ../../content/applications/hr/fleet/configuration.rst:128 +#: ../../content/applications/hr/fleet.rst:115 msgid "A7" msgstr "" -#: ../../content/applications/hr/fleet/configuration.rst:128 +#: ../../content/applications/hr/fleet.rst:115 msgid "Serie Hybrid" msgstr "" -#: ../../content/applications/hr/fleet/configuration.rst:128 +#: ../../content/applications/hr/fleet.rst:115 msgid "Class E" msgstr "" -#: ../../content/applications/hr/fleet/configuration.rst:128 +#: ../../content/applications/hr/fleet.rst:115 msgid "Combo Tour" msgstr "" -#: ../../content/applications/hr/fleet/configuration.rst:130 +#: ../../content/applications/hr/fleet.rst:117 msgid "A8" msgstr "" -#: ../../content/applications/hr/fleet/configuration.rst:130 +#: ../../content/applications/hr/fleet.rst:117 msgid "Serie M" msgstr "" -#: ../../content/applications/hr/fleet/configuration.rst:130 +#: ../../content/applications/hr/fleet.rst:117 msgid "Class GL" msgstr "" -#: ../../content/applications/hr/fleet/configuration.rst:130 +#: ../../content/applications/hr/fleet.rst:117 msgid "Corsa" msgstr "" -#: ../../content/applications/hr/fleet/configuration.rst:132 +#: ../../content/applications/hr/fleet.rst:119 msgid "Q3" msgstr "" -#: ../../content/applications/hr/fleet/configuration.rst:132 +#: ../../content/applications/hr/fleet.rst:119 msgid "Serie X" msgstr "" -#: ../../content/applications/hr/fleet/configuration.rst:132 +#: ../../content/applications/hr/fleet.rst:119 msgid "Class GLK" msgstr "" -#: ../../content/applications/hr/fleet/configuration.rst:132 +#: ../../content/applications/hr/fleet.rst:119 msgid "Insignia" msgstr "" -#: ../../content/applications/hr/fleet/configuration.rst:134 +#: ../../content/applications/hr/fleet.rst:121 msgid "Q5" msgstr "" -#: ../../content/applications/hr/fleet/configuration.rst:134 +#: ../../content/applications/hr/fleet.rst:121 msgid "Serie Z4" msgstr "" -#: ../../content/applications/hr/fleet/configuration.rst:134 +#: ../../content/applications/hr/fleet.rst:121 msgid "Class M" msgstr "" -#: ../../content/applications/hr/fleet/configuration.rst:134 +#: ../../content/applications/hr/fleet.rst:121 msgid "Meriva" msgstr "" -#: ../../content/applications/hr/fleet/configuration.rst:136 +#: ../../content/applications/hr/fleet.rst:123 msgid "Q7" msgstr "" -#: ../../content/applications/hr/fleet/configuration.rst:136 +#: ../../content/applications/hr/fleet.rst:123 msgid "Class R" msgstr "" -#: ../../content/applications/hr/fleet/configuration.rst:136 +#: ../../content/applications/hr/fleet.rst:123 msgid "Mokka" msgstr "" -#: ../../content/applications/hr/fleet/configuration.rst:138 +#: ../../content/applications/hr/fleet.rst:125 msgid "TT" msgstr "" -#: ../../content/applications/hr/fleet/configuration.rst:138 +#: ../../content/applications/hr/fleet.rst:125 msgid "Class S" msgstr "" -#: ../../content/applications/hr/fleet/configuration.rst:138 +#: ../../content/applications/hr/fleet.rst:125 msgid "Zafira" msgstr "" -#: ../../content/applications/hr/fleet/configuration.rst:140 +#: ../../content/applications/hr/fleet.rst:127 msgid "Class SLK" msgstr "" -#: ../../content/applications/hr/fleet/configuration.rst:140 +#: ../../content/applications/hr/fleet.rst:127 msgid "Zafira Tourer" msgstr "" -#: ../../content/applications/hr/fleet/configuration.rst:142 +#: ../../content/applications/hr/fleet.rst:129 msgid "Class SLS" msgstr "" -#: ../../content/applications/hr/fleet/configuration.rst:148 +#: ../../content/applications/hr/fleet.rst:135 msgid "Add a new model" msgstr "" -#: ../../content/applications/hr/fleet/configuration.rst:150 -msgid "New vehicle models can easily be added to the database. To add a new model, navigate to :menuselection:`Fleet app --> Configuration --> Models: Models`. Click the :guilabel:`New` button in the top-left corner and a blank vehicle model form loads." +#: ../../content/applications/hr/fleet.rst:137 +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:154 -#: ../../content/applications/hr/frontdesk.rst:31 -#: ../../content/applications/hr/payroll.rst:881 -#: ../../content/applications/hr/payroll/work_entries.rst:54 -#: ../../content/applications/hr/time_off.rst:416 -msgid "Enter the following information on the form:" -msgstr "" - -#: ../../content/applications/hr/fleet/configuration.rst:157 -msgid "Some fields or sections are based on the localization setting of the company, therefore not all fields or sections may be visible." -msgstr "" - -#: ../../content/applications/hr/fleet/configuration.rst:160 +#: ../../content/applications/hr/fleet.rst:143 msgid ":guilabel:`Model name`: enter the model name in the field." msgstr "" -#: ../../content/applications/hr/fleet/configuration.rst:161 -msgid ":guilabel:`Manufacturer`: select the manufacturer from the drop-down menu. If a logo is configured for the selected manufacturer, the logo automatically loads in the image box in the top-right corner. If the manufacturer is not already configured, type in the manufacturer name and then click :guilabel:`Create` to add the manufacturer, or :guilabel:`Create and edit...` to :ref:`add the manufacturer and the logo ` in a :guilabel:`Create Manufacturer` pop-up window." +#: ../../content/applications/hr/fleet.rst:144 +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:167 -msgid ":guilabel:`Vehicle Type`: select one of two pre-configured vehicle types, either :guilabel:`Car` or :guilabel:`Bike`, from the drop-down menu. The vehicle types are hardcoded in Odoo and are integrated with the *Payroll* application since vehicles can be part of an employee's benefits. Adding additional vehicle types is not possible as it affects payroll." +#: ../../content/applications/hr/fleet.rst:147 +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:171 -msgid ":guilabel:`Category`: select the category the vehicle is categorized under from the drop-down menu. To create a new category, type in the category name and then click :guilabel:`Create \"new category\"`." +#: ../../content/applications/hr/fleet.rst:151 +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:176 +#: ../../content/applications/hr/fleet.rst:156 +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.rst:160 msgid "Information tab" msgstr "" -#: ../../content/applications/hr/fleet/configuration.rst:179 +#: ../../content/applications/hr/fleet.rst:163 msgid "Model" msgstr "" -#: ../../content/applications/hr/fleet/configuration.rst:181 +#: ../../content/applications/hr/fleet.rst:165 msgid ":guilabel:`Seats Number`: enter how many passengers the vehicle can accommodate." msgstr "" -#: ../../content/applications/hr/fleet/configuration.rst:182 +#: ../../content/applications/hr/fleet.rst:166 msgid ":guilabel:`Doors Number`: enter the number of doors the vehicle has." msgstr "" -#: ../../content/applications/hr/fleet/configuration.rst:183 +#: ../../content/applications/hr/fleet.rst:167 msgid ":guilabel:`Color`: enter the color of the vehicle." msgstr "" -#: ../../content/applications/hr/fleet/configuration.rst:184 +#: ../../content/applications/hr/fleet.rst:168 msgid ":guilabel:`Model Year`: enter the year the vehicle was manufactured." msgstr "" -#: ../../content/applications/hr/fleet/configuration.rst:185 +#: ../../content/applications/hr/fleet.rst:169 msgid ":guilabel:`Trailer Hitch`: check this box if the vehicle has a trailer hitch installed." msgstr "" -#: ../../content/applications/hr/fleet/configuration.rst:188 -#: ../../content/applications/hr/payroll.rst:390 +#: ../../content/applications/hr/fleet.rst:172 +#: ../../content/applications/hr/payroll.rst:394 msgid "Salary" msgstr "" -#: ../../content/applications/hr/fleet/configuration.rst:191 +#: ../../content/applications/hr/fleet.rst:175 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:195 -msgid ":guilabel:`Can be requested`: check this box if employees can request this model for a new vehicle." +#: ../../content/applications/hr/fleet.rst:179 +msgid ":guilabel:`Can be requested`: check this box if employees can request this model vehicle." msgstr "" -#: ../../content/applications/hr/fleet/configuration.rst:197 +#: ../../content/applications/hr/fleet.rst:180 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:199 +#: ../../content/applications/hr/fleet.rst:182 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:204 -msgid "Modifying the :guilabel:`CO2 Emissions` field adjusts the value in the :guilabel:`CO2 fee` field." +#: ../../content/applications/hr/fleet.rst:187 +msgid "Modifying the :guilabel:`CO2 Emissions` field will adjust the value in the :guilabel:`CO2 fee` field." msgstr "" -#: ../../content/applications/hr/fleet/configuration.rst:207 -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." +#: ../../content/applications/hr/fleet.rst:190 +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:210 -msgid "This value impacts the gross and net salary of the employee who is assigned to the vehicle. This figure is depreciated over time according to local tax laws." +#: ../../content/applications/hr/fleet.rst:196 +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:213 -msgid "The :guilabel:`Cost (Depreciated)` does **not** depreciate automatically on the *vehicle model*, it **only** depreciates based on the *contract* linked to a specific vehicle and not on the general model." -msgstr "" - -#: ../../content/applications/hr/fleet/configuration.rst:216 -msgid ":guilabel:`Total Cost (Depreciated)`: this value is the :guilabel:`Cost (Depreciated)` and the :guilabel:`C02 fee` fields combined, and is also depreciated over time. This field is automatically calculated and cannot be modified." -msgstr "" - -#: ../../content/applications/hr/fleet/configuration.rst:221 +#: ../../content/applications/hr/fleet.rst:200 msgid "Engine" msgstr "" -#: ../../content/applications/hr/fleet/configuration.rst:223 -msgid ":guilabel:`Fuel Type`: select the type of fuel the vehicle uses from the drop-down menu. The options are :guilabel:`Diesel`, :guilabel:`Gasoline`, :guilabel:`Full Hybrid`, :guilabel:`Plug-in Hybrid Diesel`, :guilabel:`Plug-in Hybrid Gasoline`, :guilabel:`CNG`, :guilabel:`LPG`, :guilabel:`Hydrogen`, or :guilabel:`Electric`." +#: ../../content/applications/hr/fleet.rst:202 +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:227 +#: ../../content/applications/hr/fleet.rst:206 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:229 +#: ../../content/applications/hr/fleet.rst:208 msgid ":guilabel:`CO2 Standard`: enter the standard amount of carbon dioxide in grams per kilometer (g/km) for a similar sized vehicle." msgstr "" -#: ../../content/applications/hr/fleet/configuration.rst:231 +#: ../../content/applications/hr/fleet.rst:210 msgid ":guilabel:`Transmission`: select the transmission type from the drop-down menu, either :guilabel:`Manual` or :guilabel:`Automatic`." msgstr "" -#: ../../content/applications/hr/fleet/configuration.rst:233 +#: ../../content/applications/hr/fleet.rst:212 msgid ":guilabel:`Power`: if the vehicle is electric or hybrid, enter the power the vehicle uses in kilowatts (kW)." msgstr "" -#: ../../content/applications/hr/fleet/configuration.rst:235 +#: ../../content/applications/hr/fleet.rst:214 msgid ":guilabel:`Horsepower`: enter the vehicle's horsepower in this field." msgstr "" -#: ../../content/applications/hr/fleet/configuration.rst:236 +#: ../../content/applications/hr/fleet.rst:215 +#: ../../content/applications/hr/fleet/new_vehicle.rst:290 msgid ":guilabel:`Horsepower Taxation`: enter the amount that is taxed based on the size of the vehicle's engine. This is determined by local taxes and regulations, and varies depending on the location. It is recommended to check with the accounting department to ensure this value is correct." msgstr "" -#: ../../content/applications/hr/fleet/configuration.rst:239 +#: ../../content/applications/hr/fleet.rst:218 msgid ":guilabel:`Tax Deduction`: this field auto-populates according to the engine specifications, and cannot be modified. The percentage is based on the localization settings and local tax laws." msgstr "" -#: ../../content/applications/hr/fleet/configuration.rst:243 +#: ../../content/applications/hr/fleet.rst:222 msgid "Vendors tab" msgstr "" -#: ../../content/applications/hr/fleet/configuration.rst:245 -msgid "Vehicle specific vendors, such as car dealerships, are not listed separately from other vendors. The vendors that a vehicle can be purchased from also appear in the list of vendors in the *Purchase* app." +#: ../../content/applications/hr/fleet.rst:224 +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:249 -msgid "The vendors the specific vehicle model can be purchased from may be added in this tab. To add a vendor, click the :guilabel:`Add` button. An :guilabel:`Add: Vendors` pop-up window loads with a list of all the vendors currently in the database." +#: ../../content/applications/hr/fleet.rst:228 +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:253 -msgid "Select the vendor to add by clicking the checkbox to the left of the vendor name, then click :guilabel:`Select`. There is no limit to the number of vendors that can be added to this list." +#: ../../content/applications/hr/fleet.rst:233 +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:256 -msgid "If a vendor is not in the database, add a vendor by clicking the :guilabel:`New` button at the bottom of the :guilabel:`Add: Vendors` pop-up window. A blank :guilabel:`Create Vendors` pop-up form loads." -msgstr "" - -#: ../../content/applications/hr/fleet/configuration.rst:260 -msgid "Enter the information on the :guilabel:`Create Vendors` form, including the various tabs, then click :guilabel:`Save & Close` to add the vendor and close the window, or :guilabel:`Save & New` to add the current vendor and create another new vendor." -msgstr "" - -#: ../../content/applications/hr/fleet/configuration.rst:-1 +#: ../../content/applications/hr/fleet.rst:-1 msgid "Vendor form to fill out when adding a new vendor." msgstr "" -#: ../../content/applications/hr/fleet/configuration.rst:271 -msgid "Categories" +#: ../../content/applications/hr/fleet.rst:245 +msgid "Model Category" msgstr "" -#: ../../content/applications/hr/fleet/configuration.rst:273 -msgid "To best organize a fleet, it is recommended to have vehicle models housed under a specific category, to more easily see what kinds of vehicles are in the fleet." +#: ../../content/applications/hr/fleet.rst:247 +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:276 -msgid "Model categories are set on the :ref:`vehicle model form `." +#: ../../content/applications/hr/fleet.rst:251 +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:278 -msgid "Unlike manufacturers and models, Odoo does not come with any categories pre-configured; all categories must be added." +#: ../../content/applications/hr/fleet.rst:255 +msgid "Add a new model category" msgstr "" -#: ../../content/applications/hr/fleet/configuration.rst:281 -msgid "To view all the currently configured categories, navigate to :menuselection:`Fleet application --> Configuration --> Models: Categories`. All currently configured categories are displayed in a list view." +#: ../../content/applications/hr/fleet.rst:257 +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:286 -msgid "Add a new category" +#: ../../content/applications/hr/fleet.rst:260 +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:288 -msgid "To add a new category, click the :guilabel:`New` button in the top-left corner. A new entry line appears at the bottom of the list. Type in the new category, then either press the enter key on the keyboard, or click anywhere on the screen, to save the entry." +#: ../../content/applications/hr/fleet.rst:-1 +msgid "List view of the models in the fleet." msgstr "" -#: ../../content/applications/hr/fleet/configuration.rst:292 -msgid "To reorganize how the categories appear in the list, click the :guilabel:`(six small gray boxes)` to the left of the category to be moved, and drag the line to the desired position. The order of the list does not affect the database in any way. However, it may be preferable to view the vehicle categories in a specific order, for example, by size, or the numbers of passengers the vehicle can carry." +#: ../../content/applications/hr/fleet.rst:270 +msgid ":doc:`fleet/new_vehicle`" msgstr "" -#: ../../content/applications/hr/fleet/configuration.rst:-1 -msgid "List view of the categories in the fleet." +#: ../../content/applications/hr/fleet.rst:271 +msgid ":doc:`fleet/service`" msgstr "" #: ../../content/applications/hr/fleet/new_vehicle.rst:3 -msgid "Create new vehicles" +msgid "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." +msgid "Odoo's *Fleet* app manages all vehicles, and the accompanying documentation that comes with vehicle maintenance, and drivers 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`." +msgid "Upon opening the :menuselection:`Fleet` application, all vehicles are organized within the :guilabel:`Vehicles` dashboard, which is the default dashboard for the *Fleet* application. Each vehicle is displayed in its corresponding Kanban stage, based on its status. The default stages are :guilabel:`New Request`, :guilabel:`To Order`, :guilabel:`Registered`, and :guilabel:`Downgraded`." 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`." +#: ../../content/applications/hr/fleet/new_vehicle.rst:13 +msgid "To add a new vehicle to the fleet from the :guilabel:`Vehicles` page, click the :guilabel:`New` button in the top-left corner, and a blank vehicle form loads. Then, proceed to enter the vehicle information on the vehicle form." msgstr "" -#: ../../content/applications/hr/fleet/new_vehicle.rst:18 +#: ../../content/applications/hr/fleet/new_vehicle.rst:17 +msgid "The form auto-saves as data is entered. However, the form can be saved manually at any time by clicking the *save manually* option, represented by a :guilabel:`(cloud upload)` icon, located in the top-left corner of the page." +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:24 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`." +#: ../../content/applications/hr/fleet/new_vehicle.rst:26 +msgid ":guilabel:`Model`: select the vehicle's model from the drop-down menu. Once a model is selected, additional fields may appear on the form." msgstr "" -#: ../../content/applications/hr/fleet/new_vehicle.rst:22 +#: ../../content/applications/hr/fleet/new_vehicle.rst:29 +msgid "If the model is not listed, type in the model name, and click either :guilabel:`Create \"model\"`, or :guilabel:`Create and edit...` to :ref:`create a new model and edit the model details `." +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:32 msgid ":guilabel:`License Plate`: enter the vehicle's license plate number in this field." msgstr "" -#: ../../content/applications/hr/fleet/new_vehicle.rst:23 +#: ../../content/applications/hr/fleet/new_vehicle.rst:33 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." +#: ../../content/applications/hr/fleet/new_vehicle.rst:-1 +msgid "The new vehicle form, showing the model section." 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`." +#: ../../content/applications/hr/fleet/new_vehicle.rst:41 +msgid "The :guilabel:`Model` is the only required field on the new vehicle form. When a model is selected, other fields appear on the vehicle form, and relevant information auto-populates the 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: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." +msgid "Driver section" +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:49 +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: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." +msgid ":guilabel:`Driver`: select the driver from the drop-down menu, or type in a new driver and click either :guilabel:`Create \"driver\"` or :guilabel:`Create and edit...` to :ref:`create a new driver, and edit the driver details `." +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:57 +msgid "A driver does **not** have to be an employee. When creating a new driver, the driver is added to the *Fleet* application, **not** the *Employees* application." 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." +msgid "If the *Contacts* application is installed, the driver information is also stored in the *Contacts* application." msgstr "" -#: ../../content/applications/hr/fleet/new_vehicle.rst:65 -msgid "Vehicle section" +#: ../../content/applications/hr/fleet/new_vehicle.rst:63 +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 appears in this field. If there is no mobility card listed, and one should be added, :ref:`edit the employee record ` in the *Employees* application." 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." +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 \"future driver\"` or :guilabel:`Create and edit...` to :ref:`create a new future driver, and edit the driver details `." 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." +#: ../../content/applications/hr/fleet/new_vehicle.rst:71 +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 are driving next - check this box. Do **not** check this box if the current driver does not plan to change their vehicle." 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`." +#: ../../content/applications/hr/fleet/new_vehicle.rst:75 +msgid ":guilabel:`Assignment Date`: using the drop-down calendar, select when the vehicle is available for another driver. 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 left blank, that indicates the vehicle is currently available, and can be reassigned to another driver. If it is populated, the vehicle is not available for another driver until the selected date." 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." +msgid ":guilabel:`Company`: select the company from the drop-down menu. This field only appears in a multi-company database." 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`." +#: ../../content/applications/hr/fleet/new_vehicle.rst:87 +msgid "Create a new driver" 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." +msgid "If a driver is not already in the system, the new driver should first be configured and added to the database. A new driver can be added either from the :guilabel:`Driver` or :guilabel:`Future Driver` fields on the :ref:`vehicle form `." +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:93 +msgid "First, type in the name of the new driver in either the :guilabel:`Driver` or :guilabel:`Future Driver` field, then click :guilabel:`Create and edit...`. A :guilabel:`Create Driver` or :guilabel:`Create Future Driver` form appears, depending on which field initiated the form." +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:97 +msgid "Both the :guilabel:`Create Driver` and :guilabel:`Create Future Driver` forms are identical." +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:102 +msgid "Depending on the installed applications, different tabs or fields may be visible on the :guilabel:`Create Driver` and :guilabel:`Create Future Driver` forms." +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:108 +msgid "Fill out the following information on the top-half of the form:" +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:110 +msgid ":guilabel:`Individual` or :guilabel:`Company`: choose if the driver being added is an individual driver or a company. Click the radio button to make a selection." +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:113 +msgid "When a selection is made, some fields may disappear from the form. If any of the fields below are not visible, that is because :guilabel:`Company` was selected instead of :guilabel:`Individual`." +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:115 +msgid ":guilabel:`Name`: enter the name of the driver or company in this field." +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:116 +msgid ":guilabel:`Company Name...`: using the drop-down menu, select the company the driver is associated with." +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:119 +#: ../../content/applications/hr/fleet/new_vehicle.rst:145 +msgid "If the :guilabel:`Company` radio button is selected at the top of the form, this field does not appear." +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:121 +#: ../../content/applications/hr/fleet/service.rst:132 +msgid ":guilabel:`Contact`: enter the contact information in this section." +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:123 +#: ../../content/applications/hr/fleet/service.rst:134 +msgid "If desired, the :guilabel:`Contact` field can be changed to a different type of contact. Click on :guilabel:`Contact` to reveal a drop-down menu. The available options to select are :guilabel:`Contact`, :guilabel:`Invoice Address`, :guilabel:`Delivery Address`, :guilabel:`Follow-up Address`, or :guilabel:`Other Address`." +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:128 +#: ../../content/applications/hr/fleet/service.rst:139 +msgid "If desired, select one of these other options for the :guilabel:`Contact` field, and enter the corresponding information." +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:131 +msgid "If the :guilabel:`Company` radio button is selected at the top of the form, this field is labeled :guilabel:`Address` and cannot be modified." +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:134 +msgid ":guilabel:`Tax ID`: enter the driver or company's tax ID in this field." +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:135 +msgid ":guilabel:`Job Position`: enter the driver's job position in this field. If the :guilabel:`Company` radio button is selected at the top of the form, this field does not appear." +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:137 +msgid ":guilabel:`Phone`: enter the driver or company's phone number in this field." +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:138 +msgid ":guilabel:`Mobile`: enter the driver or company's mobile number in this field." +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:139 +msgid ":guilabel:`Email`: enter the driver or company's email address in this field." +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:140 +msgid ":guilabel:`Website`: enter the driver or company's website address in this field." +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:141 +msgid ":guilabel:`Title`: using the drop-down menu, select the driver's title in this field. The default options are :guilabel:`Doctor`, :guilabel:`Madam`, :guilabel:`Miss`, :guilabel:`Mister`, and :guilabel:`Professor`." +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:147 +msgid ":guilabel:`Tags`: using the drop-down menu, select any tags that apply to the driver or company." +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:149 +#: ../../content/applications/hr/fleet/service.rst:160 +msgid "To add a new tag, type in the tag, then click :guilabel:`Create \"tag\"`." +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:151 +#: ../../content/applications/hr/fleet/service.rst:162 +msgid "There is no limit to the number of tags that can be selected." +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:-1 +msgid "The top portion of the create driver form." +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:158 +#: ../../content/applications/hr/fleet/service.rst:173 +msgid "Contacts & Addresses tab" +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:160 +msgid "After completing the top-half of the :guilabel:`Create Driver` or :guilabel:`Create Future Driver` form, add any other contacts and addresses associated with the driver or company in this tab." +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:163 +msgid "To add a new contact, click the :guilabel:`Add` button, and a :guilabel:`Create Contact` pop-up window appears." +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:166 +msgid "Before entering the necessary information on the form, select the type of contact being added from a series radio button options located at the top of the form. Those options are:" +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:169 +msgid ":guilabel:`Contact`: select this option to add general contact details for employees of the associated company." +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:171 +msgid ":guilabel:`Invoice Address`: select this option to add a preferred address for all invoices. When added to the form, this address is selected by default when sending an invoice to the associated company." +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:174 +msgid ":guilabel:`Delivery Address`: select this option to add a preferred address for all deliveries. When added to the form, this address is selected by default when delivering an order to the associated company." +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:177 +#: ../../content/applications/hr/fleet/service.rst:192 +msgid ":guilabel:`Follow-up Address`: select this option to add a preferred address for all follow-up correspondence. When added to the form, this address is selected by default when sending reminders about overdue invoices." +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:180 +msgid ":guilabel:`Other Address`: select this option to add any other necessary addresses for the company or driver." +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:-1 +#: ../../content/applications/hr/fleet/new_vehicle.rst:0 +#: ../../content/applications/hr/fleet/service.rst:-1 +#: ../../content/applications/hr/fleet/service.rst:0 +msgid "The create contact form with all parts filled in." +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:187 +msgid "Depending on the :guilabel:`Contact Type`, some optional fields may not be visible. The available fields are identical to the fields in the :ref:`general information ` section of the new driver form." +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:191 +#: ../../content/applications/hr/fleet/service.rst:206 +msgid "Add any notes to the :guilabel:`Internal notes...` section of the form." +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:193 +msgid "After entering all of the information, click either :guilabel:`Save & Close` to add the one new contact, or :guilabel:`Save & New` to add the current address record and create another address record." +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:197 +#: ../../content/applications/hr/fleet/service.rst:212 +msgid "As contacts are added to this tab, each contact appears in a separate box, with an icon indicating what type of contact is listed." +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:201 +msgid "An :guilabel:`Invoice Address` displays a :guilabel:`💲 (dollar sign)` icon inside that specific address box, whereas a :guilabel:`Delivery Address` displays a :guilabel:`🚚 (truck)` icon inside." +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:210 +#: ../../content/applications/hr/fleet/service.rst:224 +msgid "Sales & Purchase tab" +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:212 +msgid "Enter the following sales and purchasing information, in the :guilabel:`Sales & Purchase` tab of the :guilabel:`Create Driver` or :guilabel:`Create Future Driver` pop-up form for the various sections below." +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:216 +msgid "Depending on the other installed applications, additional fields and sections may appear. The following are all default fields for the *Fleet* application **only**." +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:220 +msgid "Sales section" +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:222 +msgid ":guilabel:`Salesperson`: using the drop-down menu, select the user who is the main point of contact for sales with this driver's company." +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:225 +#: ../../content/applications/hr/fleet/service.rst:236 +msgid "This person **must** be an internal user of the company, meaning they can log into the database as a user." +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:229 +#: ../../content/applications/hr/fleet/service.rst:240 +msgid "Misc" +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:231 +msgid ":guilabel:`Company ID`: if the company has an ID number, **other than** its *tax ID*, enter it in this field." +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:233 +msgid ":guilabel:`Reference`: enter any text to give more information regarding the contact person. This is an internal note to provide any additional information." +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:237 +msgid "A company has several people with the same name, John Smith. The :guilabel:`Reference` field could state `John Smith at X205 - purchaser` to provide additional details." +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:241 +#: ../../content/applications/hr/fleet/service.rst:252 +msgid "Internal Notes tab" +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:243 +msgid "Add any notes that pertain to the driver, or any other necessary information, in this tab." +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:246 +msgid "Vehicle section" +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:248 +msgid "This section of the vehicle form relates to the physical details of the vehicle." +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:250 +msgid "If a preexisting vehicle in the database was selected for the :guilabel:`Model` field in the top portion of the form, some fields may auto-populate, and additional fields may also appear." +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:253 +msgid "Fill in the following fields on the form:" +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:255 +msgid ":guilabel:`Category`: using the drop-down menu, select the vehicle category from the available options. To create a new category, type in the new category name, then click :guilabel:`Create \"category\"`." +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:258 +msgid ":guilabel:`Order Date`: using the drop-down calendar, select the date the vehicle was ordered." +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:259 +msgid ":guilabel:`Registration Date`: using the drop-down calendar, select the date the vehicle was registered." +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:261 +msgid ":guilabel:`Cancellation Date`: using the drop-down calendar, select the date the vehicle lease expires, or when the vehicle is no longer available." +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:263 +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:265 +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:268 +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:270 +msgid ":guilabel:`Location`: type in the specific location where the vehicle is typically located in this field. The entry should clearly explain where the vehicle can be found, such as `Main Garage` or `Building 2 Parking Lot`." msgstr "" #: ../../content/applications/hr/fleet/new_vehicle.rst:-1 @@ -2655,67 +2870,63 @@ msgstr "" msgid "The new vehicle form, showing the vehicle tax section." msgstr "" -#: ../../content/applications/hr/fleet/new_vehicle.rst:97 +#: ../../content/applications/hr/fleet/new_vehicle.rst:279 msgid "Tax Info tab" msgstr "" -#: ../../content/applications/hr/fleet/new_vehicle.rst:100 +#: ../../content/applications/hr/fleet/new_vehicle.rst:281 +msgid "Depending on the localization setting for the database, and what additional applications are installed, other fields may be present on the form." +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:284 +msgid "The sections below are default and appear for all vehicles, regardless of other installed applications or localization settings." +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:288 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 +#: ../../content/applications/hr/fleet/new_vehicle.rst:295 msgid "Contract" msgstr "" -#: ../../content/applications/hr/fleet/new_vehicle.rst:121 +#: ../../content/applications/hr/fleet/new_vehicle.rst:297 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 +#: ../../content/applications/hr/fleet/new_vehicle.rst:299 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 +#: ../../content/applications/hr/fleet/new_vehicle.rst:301 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 +#: ../../content/applications/hr/fleet/new_vehicle.rst:302 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." +#: ../../content/applications/hr/fleet/new_vehicle.rst:305 +msgid "The values listed above 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 +#: ../../content/applications/hr/fleet/new_vehicle.rst:313 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 `." +#: ../../content/applications/hr/fleet/new_vehicle.rst:315 +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." +#: ../../content/applications/hr/fleet/new_vehicle.rst:320 +msgid "Check the information in the :guilabel:`Model` tab to ensure it is accurate. For example, the color of the vehicle, or if a trailer hitch is installed, are examples of common information that may need updating." msgstr "" -#: ../../content/applications/hr/fleet/new_vehicle.rst:153 +#: ../../content/applications/hr/fleet/new_vehicle.rst:329 msgid "Note tab" msgstr "" -#: ../../content/applications/hr/fleet/new_vehicle.rst:155 +#: ../../content/applications/hr/fleet/new_vehicle.rst:331 msgid "Enter any notes for the vehicle in this section." msgstr "" @@ -2727,183 +2938,598 @@ msgstr "" 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`." +msgid "Create service records" msgstr "" -#: ../../content/applications/hr/fleet/service.rst:17 -msgid "The fields are:" +#: ../../content/applications/hr/fleet/service.rst:14 +msgid "To log a service for a vehicle, go to the main :guilabel:`Services` dashboard by navigating to :menuselection:`Fleet app --> Fleet --> Services`. Open a new service form by clicking the :guilabel:`New` button in the top-left corner." msgstr "" -#: ../../content/applications/hr/fleet/service.rst:19 -msgid ":guilabel:`Description`: enter in a short description of the service." +#: ../../content/applications/hr/fleet/service.rst:18 +msgid "Fill out the information on the form. The only two fields that are required to be populated are :guilabel:`Service Type` and :guilabel:`Vehicle`." 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." +#: ../../content/applications/hr/fleet/service.rst:21 +msgid "The service form automatically saves as data is entered. However, the form can be saved manually at any time by clicking the :guilabel:`Save manually` option, represented by a :guilabel:`(cloud upload)` icon." 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." +#: ../../content/applications/hr/fleet/service.rst:25 +msgid "The fields on the form are:" msgstr "" #: ../../content/applications/hr/fleet/service.rst:27 -msgid ":guilabel:`Cost`: enter the cost of the service." +msgid ":guilabel:`Description`: enter a brief description 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." +msgid ":guilabel:`Service Type`: select the type of service performed using the drop-down menu. Or, enter a new type of service, and click either :guilabel:`Create \"service type\"` or :guilabel:`Create and edit...` to :ref:`add the service type and configure it `." 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." +msgid ":guilabel:`Service Types` are **not** pre-configured in Odoo. When logging a service for the first time, the *type* of service needs to be :ref:`created ` before it can be selected." msgstr "" -#: ../../content/applications/hr/fleet/service.rst:36 +#: ../../content/applications/hr/fleet/service.rst:37 +msgid ":guilabel:`Date`: using the calendar popover window, select the date the service was provided, or is scheduled to be performed. Navigate to the desired month using the :guilabel:`< > (arrow)` icons, then click on the date to select it." +msgstr "" + +#: ../../content/applications/hr/fleet/service.rst:40 +msgid ":guilabel:`Cost`: enter the cost of the service." +msgstr "" + +#: ../../content/applications/hr/fleet/service.rst:41 +msgid ":guilabel:`Vendor`: select the vendor who performed the service using 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 and edit...` to :ref:`add and configure the vendor `." +msgstr "" + +#: ../../content/applications/hr/fleet/service.rst:45 +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:`Odometer Value` field appears." +msgstr "" + +#: ../../content/applications/hr/fleet/service.rst:48 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." +#: ../../content/applications/hr/fleet/service.rst:51 +msgid ":guilabel:`Odometer Value`: enter the odometer reading when the service was done. The units of measure are either in kilometers (:guilabel:`km`) or miles (:guilabel:`mi`), depending on how the selected vehicle was configured." 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." +#: ../../content/applications/hr/fleet/service.rst:55 +msgid "When the :guilabel:`Vehicle` is selected, the unit of measure for this field is populated. This comes from the vehicle form." +msgstr "" + +#: ../../content/applications/hr/fleet/service.rst:59 +msgid "To change from kilometers to miles, or vice versa, click the :guilabel:`Internal Link` button to the right of the vehicle selected in the :guilabel:`Vehicle` field." +msgstr "" + +#: ../../content/applications/hr/fleet/service.rst:62 +msgid "Change the unit of measure, then navigate back to the service form, via the breadcrumb links. The unit of measure is then updated in the :guilabel:`Odometer Value` field." +msgstr "" + +#: ../../content/applications/hr/fleet/service.rst:65 +msgid ":guilabel:`Notes`: enter any notes for the repair 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 +#: ../../content/applications/hr/fleet/service.rst:74 +msgid "Create service type" +msgstr "" + +#: ../../content/applications/hr/fleet/service.rst:76 +msgid "Service types must be created from a service form. There is no other way to access the list of service types." +msgstr "" + +#: ../../content/applications/hr/fleet/service.rst:79 +msgid "On the :ref:`service form `, type in the name of the new :guilabel:`Service Type` in the corresponding field. Then, click :guilabel:`Create and edit...`, and a :guilabel:`Create Service Type` pop-up form appears." +msgstr "" + +#: ../../content/applications/hr/fleet/service.rst:83 +msgid "The service type entered on the service form automatically populates the :guilabel:`Name` field, which can be modified, if desired." +msgstr "" + +#: ../../content/applications/hr/fleet/service.rst:86 +msgid "Then, select the :guilabel:`Category` for the new service type from the drop-down menu in that field. The two default options to choose from are :guilabel:`Contract` or :guilabel:`Service`. Additional categories **cannot** be created." +msgstr "" + +#: ../../content/applications/hr/fleet/service.rst:90 +msgid "If the service applies to **only** contracts or services, select the corresponding :guilabel:`Category`. If the service applies to **both** contracts *and* services, leave this field blank." +msgstr "" + +#: ../../content/applications/hr/fleet/service.rst:94 +msgid "When done, click :guilabel:`Save & Close`." +msgstr "" + +#: ../../content/applications/hr/fleet/service.rst:99 +msgid "Create vendor" +msgstr "" + +#: ../../content/applications/hr/fleet/service.rst:101 +msgid "When a service is done for the first time, typically, the vendor is not in the database yet. It is best practice to add the full details for a vendor in the database, so that any necessary information can be easily retrieved." +msgstr "" + +#: ../../content/applications/hr/fleet/service.rst:105 +msgid "On the :ref:`service form `, type in the name of the new :guilabel:`Vendor` in the corresponding field. Then, click :guilabel:`Create and edit...`, and a :guilabel:`Create Vendor` form appears." +msgstr "" + +#: ../../content/applications/hr/fleet/service.rst:109 +msgid "The vendor name entered on the service form populates the :guilabel:`Name` field, by default. This field can be modified, if desired." +msgstr "" + +#: ../../content/applications/hr/fleet/service.rst:113 +msgid "Different tabs or fields may be visible on the :guilabel:`Create Vendor` form, depending on what other applications are installed." +msgstr "" + +#: ../../content/applications/hr/fleet/service.rst:119 +msgid "Fill out the following information in the top-half of the form:" +msgstr "" + +#: ../../content/applications/hr/fleet/service.rst:121 +msgid ":guilabel:`Individual` or :guilabel:`Company`: select whether the new vendor being added is an individual or a company, by clicking the corresponding radio button." +msgstr "" + +#: ../../content/applications/hr/fleet/service.rst:124 +msgid "When a selection is made, some fields may disappear from the form. If any of the fields below are not visible, that is because :guilabel:`Company` was selected, instead of :guilabel:`Individual`." +msgstr "" + +#: ../../content/applications/hr/fleet/service.rst:126 +msgid ":guilabel:`Name`: enter a name for the individual or company in this field." +msgstr "" + +#: ../../content/applications/hr/fleet/service.rst:127 +msgid ":guilabel:`Company Name`: using the drop-down menu, select the company that the vendor is associated with, if any." +msgstr "" + +#: ../../content/applications/hr/fleet/service.rst:130 +#: ../../content/applications/hr/fleet/service.rst:156 +msgid "If the :guilabel:`Company` radio button at the top of the form is selected, this field does not appear." +msgstr "" + +#: ../../content/applications/hr/fleet/service.rst:142 +msgid "If :guilabel:`Company` is selected for the :guilabel:`Individual` or :guilabel:`Company` field, this field is labeled :guilabel:`Address`, and **cannot** be modified." +msgstr "" + +#: ../../content/applications/hr/fleet/service.rst:145 +msgid ":guilabel:`Tax ID`: enter the vendor's tax ID in this field." +msgstr "" + +#: ../../content/applications/hr/fleet/service.rst:146 +msgid ":guilabel:`Job Position`: enter the vendor's job position in this field. If the :guilabel:`Company` radio button at the top of the form is selected, this field does not appear." +msgstr "" + +#: ../../content/applications/hr/fleet/service.rst:148 +#: ../../content/applications/hr/lunch.rst:89 +msgid ":guilabel:`Phone`: enter the vendor's phone number in this field." +msgstr "" + +#: ../../content/applications/hr/fleet/service.rst:149 +msgid ":guilabel:`Mobile`: enter the vendor's mobile number in this field." +msgstr "" + +#: ../../content/applications/hr/fleet/service.rst:150 +msgid ":guilabel:`Email`: enter the vendor's email address in this field." +msgstr "" + +#: ../../content/applications/hr/fleet/service.rst:151 +msgid ":guilabel:`Website`: enter the vendor's website address in this field." +msgstr "" + +#: ../../content/applications/hr/fleet/service.rst:152 +msgid ":guilabel:`Title`: using the drop-down menu, select the vendor's title in this field. The default options are :guilabel:`Doctor`, :guilabel:`Madam`, :guilabel:`Miss`, :guilabel:`Mister`, and :guilabel:`Professor`." +msgstr "" + +#: ../../content/applications/hr/fleet/service.rst:158 +msgid ":guilabel:`Tags`: using the drop-down menu, select any tags that apply to the vendor." +msgstr "" + +#: ../../content/applications/hr/fleet/service.rst:163 +msgid ":guilabel:`Image`: a photo of either the main contact person, or the company logo, can be added to the form. Hover over the :guilabel:`📷 (camera)` box, in the top-right of the form, to reveal a :guilabel:`✏️ (pencil)` icon, and click it. A file explorer window appears. Navigate to the desired file, then click :guilabel:`Open` to select it." +msgstr "" + +#: ../../content/applications/hr/fleet/service.rst:-1 +msgid "The top portion of the create vendor form." +msgstr "" + +#: ../../content/applications/hr/fleet/service.rst:175 +msgid "After the top-half of the :guilabel:`Create Vendor` form is filled out, add any other contacts and addresses associated with the vendor in this tab." +msgstr "" + +#: ../../content/applications/hr/fleet/service.rst:178 +msgid "Click the :guilabel:`Add` button to add a new contact, and a :guilabel:`Create Contact` pop-up window appears." +msgstr "" + +#: ../../content/applications/hr/fleet/service.rst:181 +msgid "Select one of the appropriate contact type options from the radio buttons, located at the top of the pop-up window. Those options are as follows:" +msgstr "" + +#: ../../content/applications/hr/fleet/service.rst:184 +msgid ":guilabel:`Contact`: select this option to add general contact details for employees of the associated vendor." +msgstr "" + +#: ../../content/applications/hr/fleet/service.rst:186 +msgid ":guilabel:`Invoice Address`: select this option to add a preferred address for all invoices. When added to the form, this address is selected by default when sending an invoice to the associated vendor." +msgstr "" + +#: ../../content/applications/hr/fleet/service.rst:189 +msgid ":guilabel:`Delivery Address`: select this option to add a preferred address for all deliveries. When added to the form, this address is selected by default when delivering an order to the associated vendor." +msgstr "" + +#: ../../content/applications/hr/fleet/service.rst:195 +msgid ":guilabel:`Other Address`: select this option to add any other necessary addresses for the vendor." +msgstr "" + +#: ../../content/applications/hr/fleet/service.rst:202 +msgid "If an option *other than* :guilabel:`Contact` is selected for the contact type, an :guilabel:`Address` section appears on the form. Enter the address details in the :guilabel:`Address` section." +msgstr "" + +#: ../../content/applications/hr/fleet/service.rst:208 +msgid "After all of the information is added, click either :guilabel:`Save & Close` to add the one new contact, or :guilabel:`Save & New` to add the current address record and create another address record." +msgstr "" + +#: ../../content/applications/hr/fleet/service.rst:216 +msgid "A :guilabel:`Delivery Address` displays a :guilabel:`⛟ (truck)` icon inside that specific address box, whereas an :guilabel:`Invoice Address` displays a :guilabel:`💵 (dollar bill)` icon inside." +msgstr "" + +#: ../../content/applications/hr/fleet/service.rst:226 +msgid "Enter the following sales and purchasing information for the various sections below. Depending on the other installed applications, additional fields and sections may appear. The following are all default fields for the *Fleet* application only." +msgstr "" + +#: ../../content/applications/hr/fleet/service.rst:231 +msgid "Sales" +msgstr "" + +#: ../../content/applications/hr/fleet/service.rst:233 +msgid ":guilabel:`Salesperson`: using the drop-down menu, select a user as the main point of contact for sales with this vendor." +msgstr "" + +#: ../../content/applications/hr/fleet/service.rst:242 +msgid ":guilabel:`Company ID`: if the company has an ID number **other than** its *tax ID*, enter it in this field." +msgstr "" + +#: ../../content/applications/hr/fleet/service.rst:244 +msgid ":guilabel:`Reference`: enter any text to give more information regarding the contact. This is an internal note to provide any additional information." +msgstr "" + +#: ../../content/applications/hr/fleet/service.rst:248 +msgid "A company has several people with the same name, Mary Jones. The :guilabel:`Reference` field could state `Mary Jones at X108 - returns` to provide additional details." +msgstr "" + +#: ../../content/applications/hr/fleet/service.rst:254 +msgid "Add any notes that pertain to the vendor, or any other necessary information, in this tab." +msgstr "" + +#: ../../content/applications/hr/fleet/service.rst:257 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." +#: ../../content/applications/hr/fleet/service.rst:259 +msgid "To view all services logged in the database, including old and new requests, navigate to :menuselection:`Fleet app --> Fleet --> Services`. All services appear in a list view, including all the details for each service." msgstr "" -#: ../../content/applications/hr/fleet/service.rst:60 +#: ../../content/applications/hr/fleet/service.rst:263 +msgid "The service records are grouped by :ref:`service type `. The number of repairs for each service type appears in parentheses after the name of the service type." +msgstr "" + +#: ../../content/applications/hr/fleet/service.rst:266 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." +#: ../../content/applications/hr/fleet/service.rst:268 +msgid ":guilabel:`Date`: the date that the service, or repair, was performed (or 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." +#: ../../content/applications/hr/fleet/service.rst:270 +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." +#: ../../content/applications/hr/fleet/service.rst:272 +msgid ":guilabel:`Service Type`: the type of service, or repair, performed. This is selected from a list of services that :ref:`must be configured `." msgstr "" -#: ../../content/applications/hr/fleet/service.rst:67 +#: ../../content/applications/hr/fleet/service.rst:274 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." +#: ../../content/applications/hr/fleet/service.rst:275 +msgid ":guilabel:`Driver`: the current driver for the vehicle." msgstr "" -#: ../../content/applications/hr/fleet/service.rst:69 -msgid ":guilabel:`Vendor`: the specific vendor who performed the service or repair." +#: ../../content/applications/hr/fleet/service.rst:276 +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." +#: ../../content/applications/hr/fleet/service.rst:277 +msgid ":guilabel:`Notes`: any information associated with the service, or repair, that is documented to add clarification." 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." +#: ../../content/applications/hr/fleet/service.rst:279 +msgid ":guilabel:`Cost`: the total cost of the service, or repair." 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`." +#: ../../content/applications/hr/fleet/service.rst:280 +msgid ":guilabel:`Stage`: the status of the service, or repair. Options are :guilabel:`New`, :guilabel:`Running`, :guilabel:`Done`, or :guilabel:`Canceled`." +msgstr "" + +#: ../../content/applications/hr/fleet/service.rst:283 +msgid "At the bottom of the :guilabel:`Cost` column, the total cost of all services and repairs are listed." 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 +#: ../../content/applications/hr/fleet/service.rst:290 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." +#: ../../content/applications/hr/fleet/service.rst:292 +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" +msgid "The icons in the top right corner than can be clicked to present the information in\n" "different ways." msgstr "" -#: ../../content/applications/hr/fleet/service.rst:93 +#: ../../content/applications/hr/fleet/service.rst:302 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." +#: ../../content/applications/hr/fleet/service.rst:304 +msgid "The default view of the service records is a list view. This presents all the services, first grouped alphabetically by type of service, then grouped by status." 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." +#: ../../content/applications/hr/fleet/service.rst:307 +msgid "The information can be re-sorted by any column. At the top of each column, hover over the column name, and an arrow appears in the far-right of that column. 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." +#: ../../content/applications/hr/fleet/service.rst:311 +msgid "The default sorting is in descending alphabetical order (A to Z), represented by a :guilabel:`⌄ (down arrow)` icon. Click the :guilabel:`⌄ (down arrow)` icon to reverse the alphabetical order (Z to A). The :guilabel:`⌄ (down arrow)` icon changes to an :guilabel:`^ (up arrow)` icon." msgstr "" -#: ../../content/applications/hr/fleet/service.rst:107 +#: ../../content/applications/hr/fleet/service.rst:315 +msgid "The two exceptions to this sorting are the default :guilabel:`Date` column and the :guilabel:`Cost` column. The :guilabel:`Date` column sorts the information in chronological order (January to December), instead of alphabetical order. The :guilabel:`Cost` column sorts the information by repair price, from lowest to highest." +msgstr "" + +#: ../../content/applications/hr/fleet/service.rst:321 +#: ../../content/applications/hr/fleet/service.rst:401 +msgid "Add a service" +msgstr "" + +#: ../../content/applications/hr/fleet/service.rst:323 +msgid "To add a service record from the list view, click the :guilabel:`New` button, and a service form loads. :ref:`Enter all the information ` on the service form." +msgstr "" + +#: ../../content/applications/hr/fleet/service.rst:326 +msgid "The form automatically saves as data is entered." +msgstr "" + +#: ../../content/applications/hr/fleet/service.rst:329 #: ../../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." +#: ../../content/applications/hr/fleet/service.rst:331 +msgid "To view services by their stage, click the :guilabel:`Kanban` button, which is the second icon in the top-right corner, and appears as two different length bars beneath a line." 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." +#: ../../content/applications/hr/fleet/service.rst:334 +msgid "All services are organized by service type, and appear in the corresponding Kanban column." msgstr "" -#: ../../content/applications/hr/fleet/service.rst:117 -msgid "Graph view" +#: ../../content/applications/hr/fleet/service.rst:336 +msgid "The number of repairs for each type of service appears in the far-right of each Kanban column header." 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." +#: ../../content/applications/hr/fleet/service.rst:339 +msgid "The collective status of the scheduled activities for each service type appears in the color-coded bar beneath each Kanban column title. Repairs with activities scheduled in the future appear green, activities due today appear yellow, overdue activities appear red, and repairs with no activities scheduled appear gray." 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." +#: ../../content/applications/hr/fleet/service.rst:344 +msgid "Each Kanban card displays a color-coded activity-related icon, such as a :guilabel:`🕘 (clock)` icon or :guilabel:`📞 (phone)` icon, for example. These icons indicate both the type of scheduled activity and the status. The status of the activity corresponds to the colors in the status bar. Click on an activity icon to view the details of that specific activity." 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." +#: ../../content/applications/hr/fleet/service.rst:349 +msgid "The length of the color bar is proportionate to the number of corresponding activities with that specific status in that particular stage. Hover over a color section to reveal the number of service records in that specific grouping." 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." +msgid "The service records presented in a Kanban view." +msgstr "" + +#: ../../content/applications/hr/fleet/service.rst:357 +msgid "To view **only** the records with a specific status, click the desired color bar section. The background color for the column changes to a pale hue of the same color (either green, yellow, red, or gray), and the color bar appears striped instead of solid. **Only** repairs and services with the selected status appear in the column." +msgstr "" + +#: ../../content/applications/hr/fleet/service.rst:-1 +msgid "The oil change service records showing only repairs with past-due activities." +msgstr "" + +#: ../../content/applications/hr/fleet/service.rst:369 +msgid "Schedule activities" +msgstr "" + +#: ../../content/applications/hr/fleet/service.rst:371 +msgid "To schedule an activity for a repair or service from the Kanban view, click the activity icon in the lower-right corner of the service record, and click :guilabel:`+ Schedule an activity`. A :guilabel:`Schedule Activity` pop-up window appears." +msgstr "" + +#: ../../content/applications/hr/fleet/service.rst:376 +msgid "Depending on what kind of activity, if any, is scheduled, the activity icon may appear differently. For example, a :guilabel:`📞 (phone)` appears if a phone call is scheduled, or an :guilabel:`✉️ (envelope)` appears if an email is scheduled." +msgstr "" + +#: ../../content/applications/hr/fleet/service.rst:380 +#: ../../content/applications/hr/frontdesk.rst:31 +#: ../../content/applications/hr/lunch.rst:230 +#: ../../content/applications/hr/payroll.rst:889 +#: ../../content/applications/hr/payroll/work_entries.rst:54 +#: ../../content/applications/hr/time_off.rst:219 +msgid "Enter the following information on the form:" +msgstr "" + +#: ../../content/applications/hr/fleet/service.rst:382 +msgid ":guilabel:`Activity Type`: using the drop-down menu, select the activity being scheduled. The default options are :guilabel:`Email`, :guilabel:`Call`, :guilabel:`Meeting`, :guilabel:`To-Do`, and :guilabel:`Upload Document`." +msgstr "" + +#: ../../content/applications/hr/fleet/service.rst:385 +msgid ":guilabel:`Summary`: enter a short description of the activity, such as `Schedule oil change`." +msgstr "" + +#: ../../content/applications/hr/fleet/service.rst:386 +msgid ":guilabel:`Due Date`: using the calendar popover, select the date the activity must be completed. Using the :guilabel:`< (left)` and :guilabel:`> (right)` arrow icons, navigate to the desired month, then click on the date to select it." +msgstr "" + +#: ../../content/applications/hr/fleet/service.rst:389 +msgid ":guilabel:`Assigned to`: using the drop-down menu, select the user responsible for the activity." +msgstr "" + +#: ../../content/applications/hr/fleet/service.rst:390 +msgid ":guilabel:`Notes`: add any notes or details in the blank area in the bottom-half of the form." +msgstr "" + +#: ../../content/applications/hr/fleet/service.rst:392 +msgid "When the :guilabel:`Schedule Activity` is completed, click :guilabel:`Schedule` to schedule the activity, or click :guilabel:`Done & Schedule Next` to schedule the current activity and schedule another activity for the same repair." +msgstr "" + +#: ../../content/applications/hr/fleet/service.rst:397 +msgid "For more detailed information regarding activities, refer to the main :doc:`activities <../../essentials/activities>` document." +msgstr "" + +#: ../../content/applications/hr/fleet/service.rst:403 +msgid "A new repair can be added from this view. Click the :guilabel:`➕ (plus icon)` in the top-right corner of the Kanban column, and a new block appears at the top of the column, beneath the Kanban title." +msgstr "" + +#: ../../content/applications/hr/fleet/service.rst:407 +msgid "Enter a :guilabel:`Title` for the service or repair, then click :guilabel:`Add`. A :guilabel:`Create` service form appears in a pop-up window. :ref:`Enter all the information ` on the service form, then click :guilabel:`Save & Close` to add the record. The new record now appears in the Kanban column." +msgstr "" + +#: ../../content/applications/hr/fleet/service.rst:413 +msgid "Graph view" +msgstr "" + +#: ../../content/applications/hr/fleet/service.rst:415 +msgid "Another way to view the data is in a graph. To change to the graph view, 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:418 +msgid "The default graph view displays the service information in a stacked bar chart, grouped by :guilabel:`Service Type`. The X-axis represents the :guilabel:`Service Type` and the Y-axis represents the :guilabel:`Cost`." +msgstr "" + +#: ../../content/applications/hr/fleet/service.rst:422 +msgid "Each column visually represents the total cost for all repairs and services for that specific :guilabel:`Service Type`. Hover over any bar to reveal a popover window that displays the total :guilabel:`Cost` for the service and repairs the bar represents." +msgstr "" + +#: ../../content/applications/hr/fleet/service.rst:426 +msgid "The graph can change to either a :guilabel:`Line Chart` or a :guilabel:`Pie Chart` by clicking the corresponding button above the graph. Additionally, the graph can display the data in either :guilabel:`Stacked`, :guilabel:`Descending`, or :guilabel:`Ascending` order, by clicking the corresponding buttons." +msgstr "" + +#: ../../content/applications/hr/fleet/service.rst:-1 +msgid "A bar chart view of the services and repairs, with the various option buttons highlighted." +msgstr "" + +#: ../../content/applications/hr/fleet/service.rst:436 +msgid "Pivot view" +msgstr "" + +#: ../../content/applications/hr/fleet/service.rst:438 +msgid "Another way to view the service data is in a spreadsheet pivot table. Click the :guilabel:`Pivot` icon, which is the fourth icon in the top-right, and appears as a small spreadsheet." +msgstr "" + +#: ../../content/applications/hr/fleet/service.rst:441 +msgid "The default way the data is presented shows the total cost of each type of service. The horizontal rows represent the various types of service, with a different service type in its own line. The vertical columns represent the total costs for each specific type of service, further divided by the type of service." +msgstr "" + +#: ../../content/applications/hr/fleet/service.rst:-1 +msgid "The default pivot table view of the services." +msgstr "" + +#: ../../content/applications/hr/fleet/service.rst:450 +msgid "The table can either be inserted in a spreadsheet or downloaded, if desired." +msgstr "" + +#: ../../content/applications/hr/fleet/service.rst:452 +msgid "To add the pivot table to a spreadsheet in Odoo, first, the appearance of the pivot table must change. The default pivot table view does not allow it to be inserted into a spreadsheet (the :guilabel:`Insert in Spreadsheet` button is grayed out)." +msgstr "" + +#: ../../content/applications/hr/fleet/service.rst:456 +msgid "First, click the :guilabel:`➖ (minus)` icon to the left of :guilabel:`Total` at the top of the pivot table. This collapses the service types, leaving only a single :guilabel:`Cost` column visible." +msgstr "" + +#: ../../content/applications/hr/fleet/service.rst:459 +msgid "Then, click the :guilabel:`Insert in Spreadsheet` button, which is no longer grayed out, and a :guilabel:`Select a spreadsheet to insert your pivot` pop-up window appears. Two tabs are visible in this pop-up window, a :guilabel:`Spreadsheets` tab and a :guilabel:`Dashboards` tab." +msgstr "" + +#: ../../content/applications/hr/fleet/service.rst:463 +msgid "Click the desired tab to indicate where the spreadsheet should be placed, either in a :guilabel:`Spreadsheet` or on a :guilabel:`Dashboard`. After clicking the desired option, click :guilabel:`Confirm`. The spreadsheet then loads on the screen." +msgstr "" + +#: ../../content/applications/hr/fleet/service.rst:468 +msgid "Spreadsheets are stored in Odoo's *Documents* application, while dashboards are stored in Odoo's *Dashboards* application." +msgstr "" + +#: ../../content/applications/hr/fleet/service.rst:471 +msgid "Click :guilabel:`Services` in the top-left corner to navigate back to the previous pivot table view." +msgstr "" + +#: ../../content/applications/hr/fleet/service.rst:473 +msgid "To download the table in an *xlsx* format, click the download xlsx icon, represented by a :guilabel:`⬇️ (down arrow above a line)` icon." +msgstr "" + +#: ../../content/applications/hr/fleet/service.rst:477 +msgid "For more detailed information regarding reporting, refer to the main :doc:`reporting <../../essentials/reporting>` document." +msgstr "" + +#: ../../content/applications/hr/fleet/service.rst:481 +msgid "Activity view" +msgstr "" + +#: ../../content/applications/hr/fleet/service.rst:483 +msgid "To view the scheduled activities for services or repairs, click the :guilabel:`🕗 (clock)` activity icon in the top-right corner of the screen. This presents all activities, organized by vehicle and activity type." +msgstr "" + +#: ../../content/applications/hr/fleet/service.rst:487 +msgid "The vertical columns are organized by activity type, and the horizontal lines are organized by vehicle." +msgstr "" + +#: ../../content/applications/hr/fleet/service.rst:490 +msgid "The entries are color-coded according to the status of each activity. Green activities are scheduled in the future, yellow activities are due today, and red activities are overdue." +msgstr "" + +#: ../../content/applications/hr/fleet/service.rst:493 +msgid "The user responsible for the activity appears in a photo in the lower-left corner of each activity entry." +msgstr "" + +#: ../../content/applications/hr/fleet/service.rst:496 +msgid "The due date of each activity is written in the top-center of each activity entry." +msgstr "" + +#: ../../content/applications/hr/fleet/service.rst:498 +msgid "A color-coded bar at the top of each activity column indicates the status of the activities within that column." +msgstr "" + +#: ../../content/applications/hr/fleet/service.rst:501 +msgid "The number of activities for each activity type is written on the right side of the color-coded bar beneath the column name." +msgstr "" + +#: ../../content/applications/hr/fleet/service.rst:-1 +msgid "The activity view, with the columns called out, and an activity box highlighted." +msgstr "" + +#: ../../content/applications/hr/fleet/service.rst:509 +msgid "Schedule an activity" +msgstr "" + +#: ../../content/applications/hr/fleet/service.rst:511 +msgid "To add a service record from the activity view, click :guilabel:`+ Schedule an activity` in the bottom-left corner of the list, and a :guilabel:`Search: Services` pop-up window loads. Click the service that the activity is being scheduled for, and a :guilabel:`Schedule Activity` form loads." +msgstr "" + +#: ../../content/applications/hr/fleet/service.rst:515 +msgid ":ref:`Enter all the information ` on the activity form." +msgstr "" + +#: ../../content/applications/hr/fleet/service.rst:517 +msgid "When the form is complete, click the :guilabel:`Schedule` button. Then, both pop-up windows close, and the activity now appears on the activity view." msgstr "" #: ../../content/applications/hr/frontdesk.rst:3 @@ -3347,6 +3973,1008 @@ msgstr "" msgid "As with all reports in Odoo, the filters and groups can be modified to show other metrics, as well." msgstr "" +#: ../../content/applications/hr/lunch.rst:5 +msgid "Lunch" +msgstr "" + +#: ../../content/applications/hr/lunch.rst:7 +msgid "The *Lunch* application in Odoo allows users a convenient way to order food and pay for their meal directly from the database." +msgstr "" + +#: ../../content/applications/hr/lunch.rst:10 +msgid "Before employees can use the *Lunch* application, there are a number of configurations to consider: settings, vendors, locations, products, product categories, and alerts. Once these are created, employees can view offerings and order food." +msgstr "" + +#: ../../content/applications/hr/lunch.rst:17 +msgid "Only two settings are needed to configure in the *Lunch* app: overdraft settings and notifications. To access the settings, navigate to :menuselection:`Lunch app --> Configuration: Settings`." +msgstr "" + +#: ../../content/applications/hr/lunch.rst:20 +msgid "Configure the following:" +msgstr "" + +#: ../../content/applications/hr/lunch.rst:22 +msgid ":guilabel:`Lunch Overdraft`: enter the maximum overdraft amount for employees. The currency format is determined by the localization setting of the company." +msgstr "" + +#: ../../content/applications/hr/lunch.rst:24 +msgid ":guilabel:`Reception notification`: set the message users receive via the *Discuss* app when their food has been delivered. The default message `Your lunch has been delivered. Enjoy your meal!` populates this field, but can be modified, if desired." +msgstr "" + +#: ../../content/applications/hr/lunch.rst:29 +msgid "If in a database with multiple languages installed, many forms in the *Lunch* application have the option of entering translations for various fields." +msgstr "" + +#: ../../content/applications/hr/lunch.rst:32 +msgid "If translations are available to be configured, a language code appears next to a translatable field on a form. To add translations for that field, click the two letter language code (for example, :guilabel:`EN` for English) and a translation pop-up window appears." +msgstr "" + +#: ../../content/applications/hr/lunch.rst:36 +msgid "The following is an example for the :guilabel:`Reception notification` field in the settings menu:" +msgstr "" + +#: ../../content/applications/hr/lunch.rst:39 +msgid "Navigate to :menuselection:`Lunch app --> Configuration: Settings`. Click the :guilabel:`EN` In the top-right of the text box beneath the :guilabel:`Reception notification` section. A :guilabel:`Translate: company_lunch_notify_message` pop-up window loads with the option to enter a translation for the other languages used by the database." +msgstr "" + +#: ../../content/applications/hr/lunch.rst:44 +msgid "The first column lists the different languages in alphabetical order, with the currently selected language in bold. The second column has the currently configured message in each column. The last column in the far-right provides a text box to type in a translation for each language." +msgstr "" + +#: ../../content/applications/hr/lunch.rst:48 +msgid "Enter the text that should appear for each language, then click :guilabel:`Save`." +msgstr "" + +#: ../../content/applications/hr/lunch.rst:0 +msgid "The translation text box, with the current language highlighted, and the Arabic\n" +"translation field highlighted." +msgstr "" + +#: ../../content/applications/hr/lunch.rst:56 +msgid "Vendors" +msgstr "" + +#: ../../content/applications/hr/lunch.rst:58 +msgid "Before food can be ordered, the restaurants that make the food, referred to as *vendors* in Odoo, **must** be configured." +msgstr "" + +#: ../../content/applications/hr/lunch.rst:61 +msgid "First navigate to :menuselection:`Lunch app --> Configuration: Vendors`, and all currently configured vendors for the *Lunch* app appear in a default Kanban view. To change to a list view, click the :guilabel:`≣ (four horizontal lines)` icon in the top-right corner." +msgstr "" + +#: ../../content/applications/hr/lunch.rst:65 +msgid "To add a new vendor, click the :guilabel:`New` button in the top-left corner, and a new lunch supplier form loads." +msgstr "" + +#: ../../content/applications/hr/lunch.rst:68 +msgid "Fill out the following fields on the form." +msgstr "" + +#: ../../content/applications/hr/lunch.rst:71 +msgid "Vendor information" +msgstr "" + +#: ../../content/applications/hr/lunch.rst:73 +msgid ":guilabel:`Vendor`: enter a name for the vendor." +msgstr "" + +#: ../../content/applications/hr/lunch.rst:74 +msgid ":guilabel:`Vendor`: select the vendor 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 \"vendor\"` to add them, or :guilabel:`Create and edit...` to create the vendor and edit the vendor form. The vendor form allows for more detail, aside from the name, to be entered, such as contact information." +msgstr "" + +#: ../../content/applications/hr/lunch.rst:80 +msgid "If a selection is made to the drop-down :guilabel:`Vendor` field, the text :guilabel:`Vendor` field (above the drop-down :guilabel:`Vendor` field) updates with the name of the vendor chosen from the drop-down menu." +msgstr "" + +#: ../../content/applications/hr/lunch.rst:84 +msgid "The list of vendors that is presented in the drop-down menu is pulled from the *Contacts* application." +msgstr "" + +#: ../../content/applications/hr/lunch.rst:87 +msgid ":guilabel:`Address`: enter the vendor's address in the various fields in this section." +msgstr "" + +#: ../../content/applications/hr/lunch.rst:88 +msgid ":guilabel:`Email`: enter the vendor's email in this field." +msgstr "" + +#: ../../content/applications/hr/lunch.rst:90 +msgid ":guilabel:`Company`: if this vendor is only available to a specific company, select the company from the drop-down menu. If this field is left blank, the vendor's items are available to **all** companies." +msgstr "" + +#: ../../content/applications/hr/lunch.rst:-1 +msgid "The top portion of the vendor form filled out." +msgstr "" + +#: ../../content/applications/hr/lunch.rst:101 +msgid "Availability" +msgstr "" + +#: ../../content/applications/hr/lunch.rst:103 +msgid "The :guilabel:`AVAILABILITY` section presents a table with two rows. The days of the week populate the top row, and the bottom row has checkboxes. Check the corresponding box for each day of the week the vendor is available." +msgstr "" + +#: ../../content/applications/hr/lunch.rst:107 +msgid "By default, Monday through Friday have checkmarks." +msgstr "" + +#: ../../content/applications/hr/lunch.rst:-1 +msgid "The default view of the availability section, with Mon-Fri enabled." +msgstr "" + +#: ../../content/applications/hr/lunch.rst:114 +#: ../../content/applications/hr/lunch/orders.rst:5 +msgid "Orders" +msgstr "" + +#: ../../content/applications/hr/lunch.rst:116 +msgid ":guilabel:`Delivery`: using the drop-down menu, select either :guilabel:`Delivery` if the vendor delivers food to the office, or :guilabel:`No Delivery` if ordered food must be picked up." +msgstr "" + +#: ../../content/applications/hr/lunch.rst:118 +msgid ":guilabel:`Location`: select which locations are able to order from this vendor. Multiple locations can be selected. If this field is left blank, **all** locations can order from the vendor." +msgstr "" + +#: ../../content/applications/hr/lunch.rst:123 +msgid "By default, an `HQ Office` location is created by default when creating a database, and is available to select from the list." +msgstr "" + +#: ../../content/applications/hr/lunch.rst:126 +msgid ":guilabel:`Send Order By`: click the radio button to select how orders are sent to the vendor. The available options are :guilabel:`Phone` or :guilabel:`Email`." +msgstr "" + +#: ../../content/applications/hr/lunch.rst:128 +msgid ":guilabel:`Order Time`: this field appears if :guilabel:`Email` is selected for :guilabel:`Send Order By`. Enter the time that an order must be emailed for the order to be accepted. Enter the time in a `HH:MM` format, then select either :guilabel:`AM` or :guilabel:`PM` from the drop-down next to the time field." +msgstr "" + +#: ../../content/applications/hr/lunch.rst:-1 +msgid "The orders section of a vendor form, with all fields filled out." +msgstr "" + +#: ../../content/applications/hr/lunch.rst:140 +msgid "Extras" +msgstr "" + +#: ../../content/applications/hr/lunch.rst:142 +msgid "When ordering an item in the *Lunch* app, it is possible to show extra items that can be added to an order, sometimes referred to as *add-ons*. These can be configured in any manner that suits the products being offered." +msgstr "" + +#: ../../content/applications/hr/lunch.rst:146 +msgid "By default, Odoo allows for three types of extra items, which can be thought of as *categories*. By default, the first type or *category* of add-ons is labeled `Extras`, the second is labeled `Beverages`, and the third is labeled `Extra Label 3`." +msgstr "" + +#: ../../content/applications/hr/lunch.rst:151 +msgid "When configuring the extras, it is important to keep in mind that all the extras configured will appear for **every item** offered by the vendor. That means that only items which apply to **all** products from the vendor should be added." +msgstr "" + +#: ../../content/applications/hr/lunch.rst:158 +msgid "Configure extras" +msgstr "" + +#: ../../content/applications/hr/lunch.rst:160 +msgid "Enter the following information for each of the three available extra sections:" +msgstr "" + +#: ../../content/applications/hr/lunch.rst:162 +msgid ":guilabel:`Extra (#) Label`: enter a name for the type of extra, such as `Toppings` or `Beverages`. This can be thought of as a *category*." +msgstr "" + +#: ../../content/applications/hr/lunch.rst:164 +msgid ":guilabel:`Extra (#) Quantity`: select how the extras are allowed to be selected. The options are:" +msgstr "" + +#: ../../content/applications/hr/lunch.rst:166 +msgid ":guilabel:`None or More`: select this if the user is not required to select anything." +msgstr "" + +#: ../../content/applications/hr/lunch.rst:167 +msgid ":guilabel:`One or More`: select this to **require** the user to make at least one selection." +msgstr "" + +#: ../../content/applications/hr/lunch.rst:168 +msgid ":guilabel:`Only One`: select this to **require** the user to make only one selection." +msgstr "" + +#: ../../content/applications/hr/lunch.rst:171 +msgid "Add extras" +msgstr "" + +#: ../../content/applications/hr/lunch.rst:173 +msgid "After the labels and quantities have been configured for an extra category, the individual extra items must be added for each category." +msgstr "" + +#: ../../content/applications/hr/lunch.rst:176 +msgid "Click :guilabel:`Add a line` at the bottom of the list that appears on the right-hand side of the extra category. Enter the :guilabel:`Name` and :guilabel:`Price` for each item being added. The price can remain at `$0.00` if there is no cost. This is common for items like disposable silverware or condiments." +msgstr "" + +#: ../../content/applications/hr/lunch.rst:182 +msgid "For a pizzeria that only offers personal pies, see their extras configured as follows:" +msgstr "" + +#: ../../content/applications/hr/lunch.rst:184 +msgid "The first extra is configured for the various toppings they offer. The :guilabel:`Extra 1 Label` is set to `Toppings`, and the :guilabel:`Extra 1 Quantity` is set to :guilabel:`None or More`. The various toppings are then added, with their corresponding costs." +msgstr "" + +#: ../../content/applications/hr/lunch.rst:0 +msgid "The first of the extras configured for pizza toppings." +msgstr "" + +#: ../../content/applications/hr/lunch.rst:192 +msgid "The pizzeria also offers a free beverage with any purchase. To set this up, the :guilabel:`Extra 2 Label` is set to `Beverages`, and the :guilabel:`Extra 1 Quantity` is set to :guilabel:`Only One`. The various beverage choices are added, and the cost for each remains zero." +msgstr "" + +#: ../../content/applications/hr/lunch.rst:0 +msgid "The second of the extras configured for a free beverage with purchase." +msgstr "" + +#: ../../content/applications/hr/lunch.rst:201 +msgid "Locations" +msgstr "" + +#: ../../content/applications/hr/lunch.rst:203 +msgid "By default, Odoo creates an `HQ Office` location when the *Lunch* application is installed. If a company has more than one location, they must be configured." +msgstr "" + +#: ../../content/applications/hr/lunch.rst:206 +msgid "To add a location, navigate to :menuselection:`Lunch app --> Configuration: Locations`. The currently configured locations appear in a list view. Click the :guilabel:`New` button in the top-left corner and a blank line appears beneath the last location in the list." +msgstr "" + +#: ../../content/applications/hr/lunch.rst:210 +msgid "Enter the name of the location in the field. Next, click into the :guilabel:`Address` field to the right of the name, and enter the location's address. It is possible to enter multiple lines in the address field." +msgstr "" + +#: ../../content/applications/hr/lunch.rst:214 +msgid "Repeat this for all locations that need to be added." +msgstr "" + +#: ../../content/applications/hr/lunch.rst:-1 +msgid "A list view of the locations with the new button highlighted." +msgstr "" + +#: ../../content/applications/hr/lunch.rst:221 +msgid "Products" +msgstr "" + +#: ../../content/applications/hr/lunch.rst:223 +msgid "Before any orders can be placed, the individual products that are being offered must be configured, as no products are pre-configured in Odoo, by default." +msgstr "" + +#: ../../content/applications/hr/lunch.rst:226 +msgid "First, navigate to the products page by going to :menuselection:`Lunch app --> Configuration: Products`. Next click the :guilabel:`New` button in the top-left corner and a blank product form loads." +msgstr "" + +#: ../../content/applications/hr/lunch.rst:232 +msgid ":guilabel:`Product Name*`: enter the name for the product." +msgstr "" + +#: ../../content/applications/hr/lunch.rst:233 +msgid ":guilabel:`Product Category*`: using the drop-down menu, select the category this product falls under." +msgstr "" + +#: ../../content/applications/hr/lunch.rst:235 +msgid ":guilabel:`Vendor*`: using the drop-down menu, select the vendor that supplies this product." +msgstr "" + +#: ../../content/applications/hr/lunch.rst:236 +msgid ":guilabel:`Price`: enter the price for the product. The currency is determined by the localization of the company." +msgstr "" + +#: ../../content/applications/hr/lunch.rst:238 +msgid ":guilabel:`Description`: enter a description of the product in this field. This description appears beneath the product photo when users are viewing the options for the day." +msgstr "" + +#: ../../content/applications/hr/lunch.rst:240 +msgid ":guilabel:`New Until`: using the calendar popover, select the date that the product will no longer be labeled as new. Until this date, a green `New` tag appears on the product." +msgstr "" + +#: ../../content/applications/hr/lunch.rst:242 +msgid ":guilabel:`Company`: if the product should only be available to a specific company, select it from the drop-down menu. If this field is left blank, this product is available for all companies in the database." +msgstr "" + +#: ../../content/applications/hr/lunch.rst:245 +msgid "Image: hover over the image box in the top-right corner of the form, and click the :guilabel:`✏️ (pencil)` edit icon that appears. A file explorer pop-up window appears. Navigate to the image, then click :guilabel:`Open`." +msgstr "" + +#: ../../content/applications/hr/lunch.rst:249 +msgid "(*) indicates required field." +msgstr "" + +#: ../../content/applications/hr/lunch.rst:-1 +msgid "A product form filled out for a nine inch pizza." +msgstr "" + +#: ../../content/applications/hr/lunch.rst:256 +msgid "Product categories" +msgstr "" + +#: ../../content/applications/hr/lunch.rst:258 +msgid "Product categories are a way to organize the offerings in the *Lunch* app, and allows for users to quickly filter the offerings when reviewing the menu for the day." +msgstr "" + +#: ../../content/applications/hr/lunch.rst:261 +msgid "To add or modify categories, navigate to :menuselection:`Lunch app --> Configuration: Product Categories`. The available categories appear in a list view. In the *Lunch* app, there are four default categories : :guilabel:`Sandwich`, :guilabel:`Pizza`, :guilabel:`Burger`, and :guilabel:`Drinks`." +msgstr "" + +#: ../../content/applications/hr/lunch.rst:266 +msgid "To add a new category, click the :guilabel:`New` button in the top-left corner, and a blank category form loads. Enter a name in the :guilabel:`Product Category` field. If the category is company-specific and should only appear for a certain company, select the :guilabel:`Company` from the drop-down menu." +msgstr "" + +#: ../../content/applications/hr/lunch.rst:271 +msgid "If desired, add a photo for the category. Hover over the image box in the top-right, and click the :guilabel:`✏️ (pencil)` edit icon that appears. A file explorer pop-up window appears. Navigate to the image, then click :guilabel:`Open`." +msgstr "" + +#: ../../content/applications/hr/lunch.rst:-1 +msgid "The category form, with the fields filled out for a Soup category." +msgstr "" + +#: ../../content/applications/hr/lunch.rst:280 +#: ../../content/applications/hr/referrals.rst:701 +msgid "Alerts" +msgstr "" + +#: ../../content/applications/hr/lunch.rst:282 +msgid "It is possible to set up alerts that can either be displayed in the *Lunch* app, or be sent to specific employees via the *Discuss* app." +msgstr "" + +#: ../../content/applications/hr/lunch.rst:285 +msgid "No alerts are pre-configured by default. To set up an alert, navigate to :menuselection:`Lunch app --> Configuration: Alerts`. Click the :guilabel:`New` button in the top-left corner and a blank lunch alert form loads. Enter the following information on the form:" +msgstr "" + +#: ../../content/applications/hr/lunch.rst:289 +msgid ":guilabel:`Alert Name`: enter a name for the alert. This should be short and descriptive, such as `New Lunch Vendor` or `Order by 11`. This field is **required**." +msgstr "" + +#: ../../content/applications/hr/lunch.rst:291 +msgid ":guilabel:`Display`: select whether the alert is visible in the *Lunch* app (:guilabel:`Alert in app)` or sent to employees via the *Discuss* app in a chat window (:guilabel:`Chat notification`)." +msgstr "" + +#: ../../content/applications/hr/lunch.rst:294 +msgid ":guilabel:`Recipients`: this field only appears if :guilabel:`Chat notification` is selected for the :guilabel:`Display` option. Select who receives the chat alert. The options are: :guilabel:`Everyone`, :guilabel:`Employee who ordered last week`, :guilabel:`Employee who ordered last month`, or :guilabel:`Employee who ordered last year`." +msgstr "" + +#: ../../content/applications/hr/lunch.rst:299 +msgid ":guilabel:`Location`: select the locations the alert should appear for from the drop-down menu. Multiple locations can be selected. This field is **required**, therefore, if the alert applies to all locations, select all the locations from the drop-down menu." +msgstr "" + +#: ../../content/applications/hr/lunch.rst:302 +msgid ":guilabel:`Show Until`: if the alert should expire on a specific date, select the date from the calendar picker." +msgstr "" + +#: ../../content/applications/hr/lunch.rst:304 +msgid ":guilabel:`Active`: this option is on (appears green) by default. To turn off the alert, click the toggle so that it no longer appears green." +msgstr "" + +#: ../../content/applications/hr/lunch.rst:306 +msgid ":guilabel:`Message`: Enter the alert message in this field. This field is **required**." +msgstr "" + +#: ../../content/applications/hr/lunch.rst:307 +msgid ":guilabel:`Notification Time`: select the days of the week the alert should be sent. By default, all seven days are active. Click on a checkbox to change the setting from active to inactive." +msgstr "" + +#: ../../content/applications/hr/lunch.rst:310 +msgid "If :guilabel:`Chat notification` was selected for the :guilabel:`Display` option, a :guilabel:`Time` field also appears. Enter the time the chat message should be sent. Next, select if the time is either :guilabel:`AM` or :guilabel:`PM` using the drop-down menu to the right of the :guilabel:`Time` field." +msgstr "" + +#: ../../content/applications/hr/lunch.rst:-1 +msgid "An alert form with all of the information filled out for a chat alert sent at 10:30 AM,\n" +"asking employees to submit orders by 11:30 AM." +msgstr "" + +#: ../../content/applications/hr/lunch.rst:321 +msgid ":doc:`lunch/orders`" +msgstr "" + +#: ../../content/applications/hr/lunch.rst:322 +msgid ":doc:`lunch/user-accounts`" +msgstr "" + +#: ../../content/applications/hr/lunch.rst:323 +msgid ":doc:`lunch/management`" +msgstr "" + +#: ../../content/applications/hr/lunch/management.rst:3 +msgid "Lunch management" +msgstr "" + +#: ../../content/applications/hr/lunch/management.rst:5 +msgid "In Odoo's *Lunch* application, it is required to have someone manage the orders, vendors, and products. In addition, someone must be responsible for the orders, and notifying employees when their orders have arrived. This can be the same person." +msgstr "" + +#: ../../content/applications/hr/lunch/management.rst:9 +msgid "Orders can be :ref:`canceled `, :ref:`sent to the vendor `, :ref:`confirmed ` upon arrival, and :ref:`employees can be notified `, either from the :ref:`Today's Orders ` dashboard, or the :ref:`Control Vendors ` dashboard." +msgstr "" + +#: ../../content/applications/hr/lunch/management.rst:14 +msgid "To manage the *Lunch* app, users need the appropriate :guilabel:`Administrator` rights. These can be set by navigating to the :menuselection:`Settings app` and selecting :guilabel:`Manage Users`. Then, click on the desired user to view their access rights." +msgstr "" + +#: ../../content/applications/hr/lunch/management.rst:18 +msgid "For more information on access rights, refer to the :doc:`Access rights <../../general/users/access_rights/>` documentation." +msgstr "" + +#: ../../content/applications/hr/lunch/management.rst:22 +msgid "Only users with administration rights are able to view the :guilabel:`Manager` and :guilabel:`Configuration` menus in the *Lunch* application." +msgstr "" + +#: ../../content/applications/hr/lunch/management.rst:28 +msgid "Today's Orders" +msgstr "" + +#: ../../content/applications/hr/lunch/management.rst:30 +msgid "To view and manage the orders for the day, navigate to :menuselection:`Lunch app --> Manager --> Today's Orders`. All orders for the day are presented in a list view on the :guilabel:`Today's Orders` dashboard, with a filter for :guilabel:`Today`, and grouped by :guilabel:`Vendor`, by default." +msgstr "" + +#: ../../content/applications/hr/lunch/management.rst:35 +#: ../../content/applications/hr/lunch/management.rst:160 +msgid "The following information appears in the list:" +msgstr "" + +#: ../../content/applications/hr/lunch/management.rst:37 +#: ../../content/applications/hr/lunch/management.rst:162 +msgid ":guilabel:`Order Date`: the date the order was placed." +msgstr "" + +#: ../../content/applications/hr/lunch/management.rst:38 +#: ../../content/applications/hr/lunch/management.rst:163 +msgid ":guilabel:`Vendor`: the vendor the product is being ordered from." +msgstr "" + +#: ../../content/applications/hr/lunch/management.rst:39 +#: ../../content/applications/hr/lunch/management.rst:164 +msgid ":guilabel:`Product`: the specific product ordered." +msgstr "" + +#: ../../content/applications/hr/lunch/management.rst:40 +#: ../../content/applications/hr/lunch/management.rst:165 +msgid ":guilabel:`Extras`: any extras selected for the product." +msgstr "" + +#: ../../content/applications/hr/lunch/management.rst:41 +#: ../../content/applications/hr/lunch/management.rst:166 +msgid ":guilabel:`Notes`: any information needed to be sent to the vendor." +msgstr "" + +#: ../../content/applications/hr/lunch/management.rst:42 +#: ../../content/applications/hr/lunch/management.rst:167 +msgid ":guilabel:`User`: the user who ordered the product." +msgstr "" + +#: ../../content/applications/hr/lunch/management.rst:43 +#: ../../content/applications/hr/lunch/management.rst:168 +msgid ":guilabel:`Lunch Location`: where the product is set to be delivered." +msgstr "" + +#: ../../content/applications/hr/lunch/management.rst:44 +#: ../../content/applications/hr/lunch/management.rst:169 +msgid ":guilabel:`Price`: the total price for the product, including all extras." +msgstr "" + +#: ../../content/applications/hr/lunch/management.rst:45 +#: ../../content/applications/hr/lunch/management.rst:170 +msgid ":guilabel:`Status`: the current status of the product." +msgstr "" + +#: ../../content/applications/hr/lunch/management.rst:46 +#: ../../content/applications/hr/lunch/management.rst:171 +msgid ":guilabel:`Company`: the company under which the order was placed. This only appears in a multi-company database." +msgstr "" + +#: ../../content/applications/hr/lunch/management.rst:-1 +msgid "The list that appears in the Today's Orders dashboard, with the filters and top column\n" +"names highlighted." +msgstr "" + +#: ../../content/applications/hr/lunch/management.rst:57 +msgid "Cancel orders" +msgstr "" + +#: ../../content/applications/hr/lunch/management.rst:59 +msgid "All users can cancel an order, not just managers of the *Lunch* app." +msgstr "" + +#: ../../content/applications/hr/lunch/management.rst:61 +msgid "To cancel an order from a vendor, individual products **must** be canceled one at a time." +msgstr "" + +#: ../../content/applications/hr/lunch/management.rst:63 +msgid "On the :guilabel:`Today's Orders` dashboard, a :guilabel:`✖️ Cancel` button is shown at the far-right of each product line that can be canceled. Click the :guilabel:`✖️ Cancel` button to cancel the order for that individual product." +msgstr "" + +#: ../../content/applications/hr/lunch/management.rst:68 +msgid "Only products with a red :guilabel:`Status` tag of :guilabel:`Ordered` can be canceled." +msgstr "" + +#: ../../content/applications/hr/lunch/management.rst:-1 +msgid "Order lines with the cancel button highlighted." +msgstr "" + +#: ../../content/applications/hr/lunch/management.rst:77 +msgid "Send orders" +msgstr "" + +#: ../../content/applications/hr/lunch/management.rst:79 +msgid "The first step in managing the *Lunch* app is to send the orders to the vendors." +msgstr "" + +#: ../../content/applications/hr/lunch/management.rst:81 +msgid "When orders are ready to be sent, the manager responsible for sending orders **must** send the orders to the vendor, outside of the database (call, online order, etc.)." +msgstr "" + +#: ../../content/applications/hr/lunch/management.rst:84 +msgid "Once orders have been placed with the vendors, click the :guilabel:`Send Orders` button that appears next to each vendor's name and phone number." +msgstr "" + +#: ../../content/applications/hr/lunch/management.rst:87 +msgid "Once sent, the :guilabel:`Send Orders` button changes to a :guilabel:`Confirm Orders` button, and the :guilabel:`Status` column is updated from red :guilabel:`Ordered` tags to blue :guilabel:`Sent` tags, indicating the order has been sent to the vendor. Users who have placed orders in the *Lunch* app rely on the :guilabel:`Status` tags to track their orders." +msgstr "" + +#: ../../content/applications/hr/lunch/management.rst:-1 +msgid "A vendor's order with the X Cancel and Send Orders buttons highlighted." +msgstr "" + +#: ../../content/applications/hr/lunch/management.rst:99 +msgid "Confirm orders" +msgstr "" + +#: ../../content/applications/hr/lunch/management.rst:101 +msgid "After orders have been sent to the vendor, the next step is to confirm the orders after they have been delivered." +msgstr "" + +#: ../../content/applications/hr/lunch/management.rst:104 +msgid "On the :guilabel:`Today's Orders` dashboard, click the :guilabel:`Confirm Orders` button that appears next to the vendor's name and phone number." +msgstr "" + +#: ../../content/applications/hr/lunch/management.rst:107 +msgid "Once confirmed, the :guilabel:`Confirm Orders` button disappears, and the :guilabel:`Status` column is updated from blue :guilabel:`Sent` tags to green :guilabel:`Received` tags, indicating the vendor has delivered the orders." +msgstr "" + +#: ../../content/applications/hr/lunch/management.rst:111 +msgid "In addition, the :guilabel:`✖️ Cancel` button at the end of each product line changes to a :guilabel:`✉️ Send Notification` button." +msgstr "" + +#: ../../content/applications/hr/lunch/management.rst:114 +msgid "If needed, instead of confirming all of the individual products from a vendor, individual products can be confirmed one at a time. To confirm an individual product, click the :guilabel:`✔️ Confirm` button at the end of the individual product line. When confirming individual products with this method, the :guilabel:`Confirm Orders` button remains on the vendor line." +msgstr "" + +#: ../../content/applications/hr/lunch/management.rst:-1 +msgid "The Today's Orders dashboard, with the two different ways to confirm an order highlighted." +msgstr "" + +#: ../../content/applications/hr/lunch/management.rst:124 +msgid "A vendor receives an order for three pizzas, and an order of garlic knots. When the delivery is made to the company, the *Lunch* manager notices the garlic knots are missing." +msgstr "" + +#: ../../content/applications/hr/lunch/management.rst:127 +msgid "The manager first marks the three pizzas as received, by individually confirming the products with the :guilabel:`✔️ Confirm` button at the end of each product line." +msgstr "" + +#: ../../content/applications/hr/lunch/management.rst:130 +msgid "Later, when the vendor delivers the garlic knots, the manager can either click the :guilabel:`✔️ Confirm` button at the end of the line for the garlic knots, or click the :guilabel:`Confirm Orders` button that appears next to the vendor's name and phone number." +msgstr "" + +#: ../../content/applications/hr/lunch/management.rst:137 +msgid "Notify employees" +msgstr "" + +#: ../../content/applications/hr/lunch/management.rst:139 +msgid "After products are received, and the orders are confirmed, the employees **must** be informed that their orders have been delivered, and are ready to be picked up." +msgstr "" + +#: ../../content/applications/hr/lunch/management.rst:142 +msgid "Unlike sending and confirming orders, notifications must be sent individually, and cannot be sent in a batch." +msgstr "" + +#: ../../content/applications/hr/lunch/management.rst:145 +msgid "To notify the user their product has arrived, click the :guilabel:`✉️ Send Notification` button at the end of each product line. An email is sent to the user informing them their products have been delivered." +msgstr "" + +#: ../../content/applications/hr/lunch/management.rst:152 +msgid "Control Vendors" +msgstr "" + +#: ../../content/applications/hr/lunch/management.rst:154 +msgid "All orders for all vendors, both past and present, can be found in the *Control Vendors* dashboard. To access these records, navigate to :menuselection:`Lunch app --> Manager --> Control Vendors`." +msgstr "" + +#: ../../content/applications/hr/lunch/management.rst:157 +msgid "All orders appear in a list view, grouped alphabetically by :guilabel:`Vendor`. The list loads with all vendors expanded to show all order lines for every vendor, by default." +msgstr "" + +#: ../../content/applications/hr/lunch/management.rst:174 +msgid "Orders can be :ref:`canceled `, :ref:`sent to the vendor `, :ref:`confirmed ` upon arrival, and :ref:`employees can be notified ` using the same method as on the :ref:`Today's Orders ` dashboard." +msgstr "" + +#: ../../content/applications/hr/lunch/management.rst:-1 +msgid "A list view of all the orders as seen in the Control Vendors dashboard." +msgstr "" + +#: ../../content/applications/hr/lunch/management.rst:184 +msgid "The difference between the :ref:`Today's Orders ` dashboard and the :ref:`Control Vendors ` dashboard is that the *Today's Orders* dashboard **only** displays orders for the current day, while the :guilabel:`Control Vendors` dashboard displays **all** orders made in the *Lunch* app." +msgstr "" + +#: ../../content/applications/hr/lunch/management.rst:190 +msgid ":doc:`../lunch`" +msgstr "" + +#: ../../content/applications/hr/lunch/management.rst:191 +msgid ":doc:`orders`" +msgstr "" + +#: ../../content/applications/hr/lunch/management.rst:192 +msgid ":doc:`user-accounts`" +msgstr "" + +#: ../../content/applications/hr/lunch/orders.rst:7 +msgid "When the *Lunch* application is opened, the :guilabel:`Order Your Lunch` dashboard loads. This view is also accessed by navigating to :menuselection:`Lunch app --> My Lunch --> New Order`." +msgstr "" + +#: ../../content/applications/hr/lunch/orders.rst:10 +msgid "The :guilabel:`Order Your Lunch` dashboard provides a summary of lunch offerings, the user's account information, and the current day's orders, along with their statuses." +msgstr "" + +#: ../../content/applications/hr/lunch/orders.rst:14 +msgid "Order Your Lunch" +msgstr "" + +#: ../../content/applications/hr/lunch/orders.rst:16 +msgid "On the main :guilabel:`Order Your Lunch` dashboard, all the necessary information needed to place an order is visible. The default filter for the products is :guilabel:`Available Today`, which is present in the :guilabel:`Search...` bar. This filter shows only products that can be purchased that day, based on the :ref:`vendor's availability `." +msgstr "" + +#: ../../content/applications/hr/lunch/orders.rst:21 +msgid "The left-side of the dashboard displays the various :guilabel:`Categories` of products available, along with the :guilabel:`Vendors` supplying the products. To the right of each line is a number, which indicates how many products are associated with that respective category or vendor." +msgstr "" + +#: ../../content/applications/hr/lunch/orders.rst:25 +msgid "To filter the products by categories or vendors, tick the checkbox next to the desired category or vendor to only view items related to those selections. Multiple selections can be made in each section." +msgstr "" + +#: ../../content/applications/hr/lunch/orders.rst:30 +msgid "If multiple selections are made, **only** products that fall under **all** the selected options are shown." +msgstr "" + +#: ../../content/applications/hr/lunch/orders.rst:33 +msgid "The top portion of the dashboard, which serves as an order summary, displays the user's account information, and the order details for today, if any orders have been placed." +msgstr "" + +#: ../../content/applications/hr/lunch/orders.rst:36 +msgid "The main section, beneath the user's information, displays all the products in a default Kanban view. Each product card displays the name, cost, vendor, photo, and description of the product. If the product is configured as new, it also displays a :guilabel:`New` tag." +msgstr "" + +#: ../../content/applications/hr/lunch/orders.rst:-1 +msgid "The *Lunch* app dashboard with all areas highlighted." +msgstr "" + +#: ../../content/applications/hr/lunch/orders.rst:45 +msgid "Anywhere a vendor's name is listed in the *Lunch* app, such as on Kanban product cards, their phone number is listed, as well." +msgstr "" + +#: ../../content/applications/hr/lunch/orders.rst:48 +msgid "The products can also be displayed in a list view, by clicking the :guilabel:`≣ (four parallel lines)` icon in the top-right corner of the dashboard." +msgstr "" + +#: ../../content/applications/hr/lunch/orders.rst:52 +msgid "Placing orders" +msgstr "" + +#: ../../content/applications/hr/lunch/orders.rst:54 +msgid "To place a lunch order, navigate to the main :guilabel:`Order Your Lunch` dashboard, by either opening the *Lunch* app, or by navigating to :menuselection:`Lunch app --> My Lunch --> New Order`." +msgstr "" + +#: ../../content/applications/hr/lunch/orders.rst:58 +msgid "Add products to an order" +msgstr "" + +#: ../../content/applications/hr/lunch/orders.rst:60 +msgid "From the :guilabel:`Order Your Lunch` dashboard, click on a desired product to add to an order, and the product appears in a :guilabel:`Configure Your Order` pop-up window." +msgstr "" + +#: ../../content/applications/hr/lunch/orders.rst:63 +msgid "At the top of the pop-up window is the product image, name, and price. Beneath that, there is a potential :guilabel:`Extras` field, showcasing any :ref:`extra items or options `. Tick the checkbox next to any desired extras present in the :guilabel:`Extras` field to add them to the order." +msgstr "" + +#: ../../content/applications/hr/lunch/orders.rst:68 +msgid "Each extra option is organized by a category, complete with its name and price. As extras are selected, the displayed price at the top of the pop-up window updates to reflect all current selections." +msgstr "" + +#: ../../content/applications/hr/lunch/orders.rst:72 +msgid "Beneath the :guilabel:`Extras` field is the :guilabel:`Description` of the product, followed by a :guilabel:`Notes` field. The :guilabel:`Notes` field is used to enter any vital information, which is then sent to the vendor regarding the order, such as any special requests or food allergies." +msgstr "" + +#: ../../content/applications/hr/lunch/orders.rst:76 +msgid "When all selections for the product have been made, click the :guilabel:`Add To Cart` button in the lower-left of the pop-up window. To cancel the order, click the :guilabel:`Discard` button." +msgstr "" + +#: ../../content/applications/hr/lunch/orders.rst:-1 +msgid "The pop-up window for a personal pizza, with all the extras highlighted and selected." +msgstr "" + +#: ../../content/applications/hr/lunch/orders.rst:86 +msgid "Depending on how the various :ref:`extras ` are configured for a vendor, it is possible to receive an error when attempting to add products to the cart." +msgstr "" + +#: ../../content/applications/hr/lunch/orders.rst:89 +msgid "An error can occur when a configured product **requires** the user to select an option in the :guilabel:`Extras` field, but the user neglects to make one." +msgstr "" + +#: ../../content/applications/hr/lunch/orders.rst:92 +msgid "When this occurs, a :guilabel:`Validation Error` pop-up window appears. The error is briefly explained in the pop-up window. Click :guilabel:`Close` to close the window, and make any necessary changes to the :guilabel:`Configure Your Order` pop-up window." +msgstr "" + +#: ../../content/applications/hr/lunch/orders.rst:97 +msgid "The vendor, The Pizza Palace, provides a free beverage with any purchase. Their products are configured so that a beverage selection is **required** in the :guilabel:`Extras` field *before* adding one of their products to the cart." +msgstr "" + +#: ../../content/applications/hr/lunch/orders.rst:101 +msgid "If a selection is **not** made, an error occurs. The message that appears is `You have to order one and only one Free Beverage with Purchase`." +msgstr "" + +#: ../../content/applications/hr/lunch/orders.rst:0 +msgid "The :guilabel:`Validation Error` pop-up window with the specific error for the free\n" +"beverage displayed." +msgstr "" + +#: ../../content/applications/hr/lunch/orders.rst:110 +msgid "Your Order summary" +msgstr "" + +#: ../../content/applications/hr/lunch/orders.rst:112 +msgid "When at least one item is added to an order, the items appear at the top of the dashboard in the :guilabel:`Your Order` summary. In addition to the products, users can view the account information, in addition to all the information related to orders placed during the current calendar day." +msgstr "" + +#: ../../content/applications/hr/lunch/orders.rst:116 +msgid "As products are added to an order, they appear at the top center of the summary box. Each product is listed beneath the words :guilabel:`Your Order`, with the product name, quantity, and a status tag." +msgstr "" + +#: ../../content/applications/hr/lunch/orders.rst:119 +msgid "The available tags that can be displayed for each item are:" +msgstr "" + +#: ../../content/applications/hr/lunch/orders.rst:121 +msgid ":guilabel:`To Order`: the product has been added to the cart, but has not been purchased yet by the user." +msgstr "" + +#: ../../content/applications/hr/lunch/orders.rst:123 +msgid ":guilabel:`Ordered`: the product has been purchased by the user, and is waiting to be sent to the vendor by a *Lunch* app manager." +msgstr "" + +#: ../../content/applications/hr/lunch/orders.rst:125 +msgid ":guilabel:`Sent`: the order for the product has been sent to the vendor by a *Lunch* app manager." +msgstr "" + +#: ../../content/applications/hr/lunch/orders.rst:126 +msgid ":guilabel:`Received`: the product has been delivered by the vendor to the user's location, and has been verified as received by a *Lunch* app manager." +msgstr "" + +#: ../../content/applications/hr/lunch/orders.rst:129 +msgid "Product quantities can be adjusted by clicking the :guilabel:`➕ (plus sign)` or :guilabel:`➖ (minus sign)` to the left of the listed product. The product price adjusts in real-time to display the cost for the currently selected quantity of the product." +msgstr "" + +#: ../../content/applications/hr/lunch/orders.rst:133 +msgid "The right side of the :guilabel:`Your Order` summary displays the purchasing information. The :guilabel:`Total` amount for the entire day's lunch order is displayed. The :guilabel:`Already Paid` field indicates how much has been paid that day towards the :guilabel:`Total` amount. The :guilabel:`To Pay` field displays how much of the remaining :guilabel:`Total` amount must be paid, in order to place the currently configured order." +msgstr "" + +#: ../../content/applications/hr/lunch/orders.rst:-1 +msgid "The Your Orders section of the dashboard, with the purchasing information highlighted." +msgstr "" + +#: ../../content/applications/hr/lunch/orders.rst:144 +msgid "Users can place multiple orders throughout the day, and are not restricted to only placing one lunch order each day. Multiple orders might need to be placed, due to users forgetting to add items to an order, or if there are multiple meals that are available to be purchased for the office ()not just lunch), and so on." +msgstr "" + +#: ../../content/applications/hr/lunch/orders.rst:149 +msgid "Depending on the various vendors, and how the vendors and products are configured, it is possible to order breakfast, lunch, dinner, coffee, and/or snacks." +msgstr "" + +#: ../../content/applications/hr/lunch/orders.rst:153 +msgid "Submit an order" +msgstr "" + +#: ../../content/applications/hr/lunch/orders.rst:155 +msgid "To place the order, click the :guilabel:`Order Now` button on the right-side of the :guilabel:`Your Order` summary. The user is charged the amount that is displayed in the :guilabel:`To Pay` field, and the cost is deducted from their *Lunch* account balance." +msgstr "" + +#: ../../content/applications/hr/lunch/orders.rst:159 +msgid "Once the order is placed, the tags for the items just purchased in the :guilabel:`Your Order` field change from orange :guilabel:`To Order` tags to red :guilabel:`Ordered` tags." +msgstr "" + +#: ../../content/applications/hr/lunch/orders.rst:163 +msgid "Track an order" +msgstr "" + +#: ../../content/applications/hr/lunch/orders.rst:165 +msgid "When orders have been sent to the vendors, the tags for the items in the :guilabel:`Your Order` summary change from red :guilabel:`Ordered` tags to blue :guilabel:`Sent` tags." +msgstr "" + +#: ../../content/applications/hr/lunch/orders.rst:168 +msgid "Once orders have been received and verified, the tags change from blue :guilabel:`Sent` tags to green :guilabel:`Received` tags." +msgstr "" + +#: ../../content/applications/hr/lunch/orders.rst:172 +msgid "Receive an order" +msgstr "" + +#: ../../content/applications/hr/lunch/orders.rst:174 +msgid "When orders are received at the delivery location, they are confirmed by a *Lunch* app manager, and a notification is sent to the employee who ordered the food." +msgstr "" + +#: ../../content/applications/hr/lunch/orders.rst:178 +msgid "My Orders" +msgstr "" + +#: ../../content/applications/hr/lunch/orders.rst:180 +msgid "To view a full list of all orders placed in the *Lunch* app for the currently signed-in user, navigate to :menuselection:`Lunch app --> My Lunch --> My Order History`. This navigates to the :guilabel:`My Orders` dashboard. The data is filtered by :guilabel:`My Orders` and grouped by :guilabel:`Order Date: Day`, by default, both of which are located in the :guilabel:`Search...` bar." +msgstr "" + +#: ../../content/applications/hr/lunch/orders.rst:185 +msgid "All products appear in a list view, organized by date. The list displays the :guilabel:`Order Date`, :guilabel:`Vendor`, :guilabel:`Product`, :guilabel:`Extras`, :guilabel:`Notes`, :guilabel:`User`, :guilabel:`Lunch Location`, :guilabel:`Price`, and :guilabel:`Status` information. If in a multi-company database, a :guilabel:`Company` column also appears." +msgstr "" + +#: ../../content/applications/hr/lunch/orders.rst:190 +msgid "The total cost for each order is displayed on the line containing the order date. At the bottom of the list, beneath all the lines, the overall total amount paid for all the orders appears, under the :guilabel:`Price` column." +msgstr "" + +#: ../../content/applications/hr/lunch/orders.rst:194 +msgid "At the end of each product line with a status of :guilabel:`Ordered` or :guilabel:`Sent`, an :guilabel:`X Cancel` button appears. Click :guilabel:`X Cancel` to cancel that product order. Once a product order has been canceled, the money paid for that product is refunded, and appears in the user's account." +msgstr "" + +#: ../../content/applications/hr/lunch/orders.rst:199 +msgid "At the end of each product line with a status of :guilabel:`Received`, a :guilabel:`Re-order` button appears. Click :guilabel:`Re-order` to instantly reorder that same product, with the same extras, if applicable. The new order appears in the list, under the current date, and the product is paid for, with money deducted from the user's account." +msgstr "" + +#: ../../content/applications/hr/lunch/orders.rst:-1 +msgid "The list view that appears when navigating to the My Orders dashboard." +msgstr "" + +#: ../../content/applications/hr/lunch/orders.rst:209 +msgid "My Account" +msgstr "" + +#: ../../content/applications/hr/lunch/orders.rst:211 +msgid "To view a summary of all transactions in the user's account, navigate to :menuselection:`Lunch app --> My Lunch --> My Account History`. Doing so reveals the :guilabel:`My Account` dashboard." +msgstr "" + +#: ../../content/applications/hr/lunch/orders.rst:214 +msgid "The default presentation of the :guilabel:`My Account` dashboard displays all entries, from newest to oldest. The :guilabel:`Date`, :guilabel:`Description`, and :guilabel:`Amount` are the only fields displayed in the list." +msgstr "" + +#: ../../content/applications/hr/lunch/orders.rst:218 +msgid "Entries with a negative figure listed in the :guilabel:`Amount` column represent products purchased in the *Lunch* app. These appear in a `$-XX.XX` format." +msgstr "" + +#: ../../content/applications/hr/lunch/orders.rst:221 +msgid "Entries with a positive balance either represent funds added to the user's lunch account, or canceled orders that were eventually refunded to the user. These appear in a `$XX.XX` format." +msgstr "" + +#: ../../content/applications/hr/lunch/orders.rst:-1 +msgid "The My Account dashboard with the entry for adding funds to the user's lunch account\n" +"highlighted." +msgstr "" + +#: ../../content/applications/hr/lunch/user-accounts.rst:3 +msgid "Manage user accounts" +msgstr "" + +#: ../../content/applications/hr/lunch/user-accounts.rst:5 +msgid "In Odoo's *Lunch* application, users pay for products directly from their *Lunch* app account. For funds to appear in their account, a *Lunch* app manager **must** transfer funds into each user's account." +msgstr "" + +#: ../../content/applications/hr/lunch/user-accounts.rst:10 +msgid "To add funds and manage user accounts, the user must have :guilabel:`Administrator` access rights set for the *Lunch* application. This is verified by navigating to :menuselection:`Settings app --> → Manage Users`. Then, click on a user to view their various settings and access rights." +msgstr "" + +#: ../../content/applications/hr/lunch/user-accounts.rst:14 +msgid "For more information, refer to the :doc:`Access rights <../../general/users/access_rights/>` documentation." +msgstr "" + +#: ../../content/applications/hr/lunch/user-accounts.rst:17 +msgid "The *Lunch* application does **not** directly interface in any way with software or products linked to any monetary accounts or billing. Money **cannot** be transferred from users' bank accounts, nor can users' credit cards be charged." +msgstr "" + +#: ../../content/applications/hr/lunch/user-accounts.rst:21 +msgid "Odoo's *Lunch* application **only** allows for manual entries of cash exchanges that are handled by the *Lunch* app manager. It is up to each individual company to create the method with which lunch accounts are replenished." +msgstr "" + +#: ../../content/applications/hr/lunch/user-accounts.rst:26 +msgid "Some examples of how money can be organized and transferred within a company:" +msgstr "" + +#: ../../content/applications/hr/lunch/user-accounts.rst:28 +msgid "Cash is handed to the *Lunch* app manager, who then updates the user's account." +msgstr "" + +#: ../../content/applications/hr/lunch/user-accounts.rst:29 +msgid "Money is automatically deducted from the user's paychecks, then the *Lunch* app manager updates the account when paychecks are issued. This requires :ref:`adding a salary attachment ` for the user's payslip in the *Payroll* app." +msgstr "" + +#: ../../content/applications/hr/lunch/user-accounts.rst:32 +msgid "Companies can sell \"lunch tickets\" at a set price (for example, one ticket costs $5.00). Users can purchase tickets from a *Lunch* app manager, who then updates the user's account." +msgstr "" + +#: ../../content/applications/hr/lunch/user-accounts.rst:38 +msgid "Cash Moves" +msgstr "" + +#: ../../content/applications/hr/lunch/user-accounts.rst:40 +msgid "To add funds to user accounts, each cash move must be individually logged. To view all cash move records, or create a new cash move, navigate to :menuselection:`Lunch app --> Manager --> Cash Moves`. Doing so reveals the :guilabel:`Cash Moves` dashboard." +msgstr "" + +#: ../../content/applications/hr/lunch/user-accounts.rst:44 +msgid "On the :guilabel:`Cash Moves` dashboard, all cash moves are presented in a default list view, displaying each record's :guilabel:`Date`, :guilabel:`User`, :guilabel:`Description`, and :guilabel:`Amount`. The total of all the cash moves is displayed at the bottom of the :guilabel:`Amount` column." +msgstr "" + +#: ../../content/applications/hr/lunch/user-accounts.rst:-1 +msgid "The list view of all cash moves." +msgstr "" + +#: ../../content/applications/hr/lunch/user-accounts.rst:54 +msgid "Add funds" +msgstr "" + +#: ../../content/applications/hr/lunch/user-accounts.rst:56 +msgid "To add funds to a lunch account, click the :guilabel:`New` button, located in the top-left corner of the :guilabel:`Cash Moves` dashboard." +msgstr "" + +#: ../../content/applications/hr/lunch/user-accounts.rst:59 +msgid "A blank :guilabel:`Cash Moves` form loads. Enter the following information on the form:" +msgstr "" + +#: ../../content/applications/hr/lunch/user-accounts.rst:61 +msgid ":guilabel:`User`: select the user depositing cash into their account from the drop-down menu. If the user is not in the database, they can be created by typing their name in the :guilabel:`User` field, and clicking either :guilabel:`Create \"user\"` or :guilabel:`Create and edit...` to create the user and edit the :guilabel:`Create User` form." +msgstr "" + +#: ../../content/applications/hr/lunch/user-accounts.rst:65 +msgid ":guilabel:`Date`: using the calendar popover, select the date the transaction occurred." +msgstr "" + +#: ../../content/applications/hr/lunch/user-accounts.rst:66 +msgid ":guilabel:`Amount`: enter the amount being added to the lunch account." +msgstr "" + +#: ../../content/applications/hr/lunch/user-accounts.rst:67 +msgid ":guilabel:`Description`: enter a brief description of the transaction." +msgstr "" + +#: ../../content/applications/hr/lunch/user-accounts.rst:-1 +msgid "The cash move form filled out for a transaction of $40.00." +msgstr "" + +#: ../../content/applications/hr/lunch/user-accounts.rst:75 +msgid "Control Accounts" +msgstr "" + +#: ../../content/applications/hr/lunch/user-accounts.rst:77 +msgid "An overview of every transaction in the *Lunch* app, including all cash deposits and purchases, can be viewed on the main *Control Accounts* dashboard. To access this dashboard, navigate to :menuselection:`Lunch app --> Manager --> Control Accounts.`" +msgstr "" + +#: ../../content/applications/hr/lunch/user-accounts.rst:81 +msgid "All transactions are grouped :guilabel:`By Employee`, and listed alphabetically by the user's first name. At the end of the user's name, a number appears. This indicates the number of individual records logged for that user." +msgstr "" + +#: ../../content/applications/hr/lunch/user-accounts.rst:85 +msgid "The default view is to have all individual transactions hidden. To view all transactions for a user, click the :guilabel:`▶ (triangle)` icon to the left of the desired name to expand that specific group." +msgstr "" + +#: ../../content/applications/hr/lunch/user-accounts.rst:89 +msgid "Each record includes the :guilabel:`Date`, :guilabel:`User`, :guilabel:`Description`, and :guilabel:`Amount`." +msgstr "" + +#: ../../content/applications/hr/lunch/user-accounts.rst:-1 +msgid "The Control Accounts dashboard with two employee's transactions expanded." +msgstr "" + +#: ../../content/applications/hr/lunch/user-accounts.rst:97 +msgid "This list only displays the various transactions within the *Lunch* app, and does **not** allow modifications to be made to any records listed." +msgstr "" + +#: ../../content/applications/hr/lunch/user-accounts.rst:100 +msgid "Cash moves can be modified, but **only** from the :ref:`Cash Moves ` dashboard, not from the :guilabel:`Control Accounts` dashboard." +msgstr "" + +#: ../../content/applications/hr/lunch/user-accounts.rst:103 +msgid "It is **not** possible to modify any product-related records." +msgstr "" + #: ../../content/applications/hr/payroll.rst:5 #: ../../content/applications/hr/payroll.rst:81 #: ../../content/applications/hr/payroll/reporting.rst:31 @@ -3458,79 +5086,79 @@ msgstr "" msgid "In order for an employee to be paid, they **must** have an active contract for a specific type of employment. Creating and viewing contract templates, and creating and viewing employment types, is possible from this section of the configuration header menu." msgstr "" -#: ../../content/applications/hr/payroll.rst:102 +#: ../../content/applications/hr/payroll.rst:104 msgid "Templates" msgstr "" -#: ../../content/applications/hr/payroll.rst:104 +#: ../../content/applications/hr/payroll.rst:106 msgid "Contract templates are used with the *Recruitment* application when sending an offer to a candidate. The contract template forms the basis of an offer, and can be modified for specific candidates or employees, when necessary. If a contract template is created or modified in the *Payroll* application, the changes are also reflected in the *Recruitment* application." msgstr "" -#: ../../content/applications/hr/payroll.rst:109 +#: ../../content/applications/hr/payroll.rst:111 msgid "To view all the current contract templates in the database, navigate to :menuselection:`Payroll app --> Configuration --> Contracts: Templates`." msgstr "" -#: ../../content/applications/hr/payroll.rst:112 +#: ../../content/applications/hr/payroll.rst:114 msgid "On the :guilabel:`Contract Templates` page, all current contract templates appear in a list view. To view the details of a contract template, click anywhere on the line to open the contract form. The contract template can be modified from this form. Proceed to make any desired changes to the contract." msgstr "" -#: ../../content/applications/hr/payroll.rst:117 +#: ../../content/applications/hr/payroll.rst:119 msgid "To create a new contract template, click the :guilabel:`New` button. Then, enter the following information on the blank contract template form that appears:" msgstr "" -#: ../../content/applications/hr/payroll.rst:120 +#: ../../content/applications/hr/payroll.rst:122 msgid ":guilabel:`Contract Reference`: enter a brief description for the template. This should be clear and easily understood, as this name appears in the *Recruitment* application, as well." msgstr "" -#: ../../content/applications/hr/payroll.rst:122 +#: ../../content/applications/hr/payroll.rst:124 msgid ":guilabel:`Working Schedule`: select the desired working schedule the contract applies to from the drop-down menu. If a new working schedule is needed, create a :ref:`new working schedule `." msgstr "" -#: ../../content/applications/hr/payroll.rst:125 +#: ../../content/applications/hr/payroll.rst:127 msgid ":guilabel:`Work Entry Source`: select how the work entries are generated. Choices are either:" msgstr "" -#: ../../content/applications/hr/payroll.rst:127 +#: ../../content/applications/hr/payroll.rst:129 msgid ":guilabel:`Working Schedule`: work entries are generated based on the selected working schedule." msgstr "" -#: ../../content/applications/hr/payroll.rst:128 +#: ../../content/applications/hr/payroll.rst:130 msgid ":guilabel:`Attendances`: work entries are generated based on the employee's attendance, as they are logged in the *Attendances* application. Refer to the :ref:`Attendances ` documentation for information on checking in and out." msgstr "" -#: ../../content/applications/hr/payroll.rst:131 +#: ../../content/applications/hr/payroll.rst:133 msgid ":guilabel:`Planning`: work entries are generated based on the employee's planning in the *Planning* application." msgstr "" -#: ../../content/applications/hr/payroll.rst:134 +#: ../../content/applications/hr/payroll.rst:136 msgid ":guilabel:`Salary Structure Type`: select the :ref:`salary structure type ` from the drop-down menu." msgstr "" -#: ../../content/applications/hr/payroll.rst:136 +#: ../../content/applications/hr/payroll.rst:138 msgid ":guilabel:`Department`: select the department the contract template applies to from the drop-down menu. If blank, the template applies to all departments." msgstr "" -#: ../../content/applications/hr/payroll.rst:138 +#: ../../content/applications/hr/payroll.rst:140 msgid ":guilabel:`Job Position`: select the :ref:`job position ` the contract template applies to from the drop-down menu. If blank, the template applies to all job positions." msgstr "" -#: ../../content/applications/hr/payroll.rst:140 +#: ../../content/applications/hr/payroll.rst:142 msgid ":guilabel:`Wage on Payroll`: enter the monthly wage in the field." msgstr "" -#: ../../content/applications/hr/payroll.rst:141 +#: ../../content/applications/hr/payroll.rst:143 msgid ":guilabel:`Contract Type`: select the type of contract from the drop-down menu. This list is the same as the :ref:`Employment Types `." msgstr "" -#: ../../content/applications/hr/payroll.rst:143 +#: ../../content/applications/hr/payroll.rst:145 msgid ":guilabel:`HR Responsible`: select the employee responsible for validating contracts, using this template, from the drop-down menu." msgstr "" -#: ../../content/applications/hr/payroll.rst:145 +#: ../../content/applications/hr/payroll.rst:147 msgid ":guilabel:`New Contract Document Template`: select a default document that a new employee has to sign to accept an offer." msgstr "" -#: ../../content/applications/hr/payroll.rst:147 +#: ../../content/applications/hr/payroll.rst:149 msgid ":guilabel:`Contract Update Document Template`: select a default document that a current employee has to sign to update their contract." msgstr "" @@ -3538,31 +5166,32 @@ msgstr "" msgid "A new contract template form, with the fields filled in." msgstr "" -#: ../../content/applications/hr/payroll.rst:155 +#: ../../content/applications/hr/payroll.rst:157 msgid "Salary information tab" msgstr "" -#: ../../content/applications/hr/payroll.rst:157 +#: ../../content/applications/hr/payroll.rst:159 +#: ../../content/applications/hr/payroll/contracts.rst:104 msgid ":guilabel:`Wage Type`: select either :guilabel:`Fixed Wage` or :guilabel:`Hourly Wage` from the drop-down menu." msgstr "" -#: ../../content/applications/hr/payroll.rst:159 +#: ../../content/applications/hr/payroll.rst:161 msgid ":guilabel:`Schedule Pay`: using the drop-down menu, select how often the employee is paid. Options include :guilabel:`Annually`, :guilabel:`Semi-annually`, :guilabel:`Quarterly`, :guilabel:`Bi-monthly`, :guilabel:`Monthly`, :guilabel:`Semi-monthly`, :guilabel:`Bi-weekly`, :guilabel:`Weekly`, or :guilabel:`Daily`." msgstr "" -#: ../../content/applications/hr/payroll.rst:163 +#: ../../content/applications/hr/payroll.rst:165 msgid ":guilabel:`Wage`: enter the gross wage. The time period presented in this field is based on what is selected for the :guilabel:`Scheduled Pay` field. It is recommended to populate the :guilabel:`Yearly Cost (Real)` field *first*, since that entry updates this field automatically." msgstr "" -#: ../../content/applications/hr/payroll.rst:166 +#: ../../content/applications/hr/payroll.rst:168 msgid ":guilabel:`Yearly Cost (Real)`: enter the total yearly cost the employee costs the employer. When this value is entered, the :guilabel:`Monthly Cost (Real)` is automatically updated." msgstr "" -#: ../../content/applications/hr/payroll.rst:168 +#: ../../content/applications/hr/payroll.rst:170 msgid ":guilabel:`Monthly Cost (Real)`: this field is **not** editable. The value is automatically populated after the :guilabel:`Yearly Cost (Real)` is entered." msgstr "" -#: ../../content/applications/hr/payroll.rst:172 +#: ../../content/applications/hr/payroll.rst:174 msgid "The :guilabel:`Schedule Pay`, :guilabel:`Wage`, and :guilabel:`Yearly Cost (Real)` fields are all linked. If any of these fields are updated, the other two fields automatically update to reflect the change. It is best practice to check these three fields if any modifications have been made, to ensure they are accurate." msgstr "" @@ -3570,47 +5199,47 @@ msgstr "" msgid "The salary information tab, with the fields filled in." msgstr "" -#: ../../content/applications/hr/payroll.rst:182 +#: ../../content/applications/hr/payroll.rst:184 msgid "Pre-tax benefits and post-tax deductions" msgstr "" -#: ../../content/applications/hr/payroll.rst:184 +#: ../../content/applications/hr/payroll.rst:186 msgid "Depending on the localization settings set for the company, the entries presented in this section either vary, or may not appear at all." msgstr "" -#: ../../content/applications/hr/payroll.rst:187 +#: ../../content/applications/hr/payroll.rst:189 msgid "For example, some entries may pertain to retirement accounts, health insurance benefits, and commuter benefits." msgstr "" -#: ../../content/applications/hr/payroll.rst:190 +#: ../../content/applications/hr/payroll.rst:192 msgid "Enter the monetary amounts or percentages to specify how much of the employee's salary goes to the various benefits and/or deductions." msgstr "" -#: ../../content/applications/hr/payroll.rst:196 +#: ../../content/applications/hr/payroll.rst:198 msgid "Employment types" msgstr "" -#: ../../content/applications/hr/payroll.rst:198 +#: ../../content/applications/hr/payroll.rst:200 msgid "To view all the pre-configured employment types, navigate to :menuselection:`Payroll application --> Configuration --> Contracts: Employment Types`." msgstr "" -#: ../../content/applications/hr/payroll.rst:201 +#: ../../content/applications/hr/payroll.rst:203 msgid "The employment types are presented in a list view on the :guilabel:`Employment Types` page." msgstr "" -#: ../../content/applications/hr/payroll.rst:203 +#: ../../content/applications/hr/payroll.rst:205 msgid "The default employment types are :guilabel:`Permanent`, :guilabel:`Temporary`, :guilabel:`Seasonal`, :guilabel:`Interim`, :guilabel:`Full-Time`, :guilabel:`Part-Time`, and :guilabel:`Permanent`." msgstr "" -#: ../../content/applications/hr/payroll.rst:206 +#: ../../content/applications/hr/payroll.rst:208 msgid "To make a new employment type, click the :guilabel:`New` button in the upper-left corner, and a blank line appears at the bottom of the :guilabel:`Employment Types` page." msgstr "" -#: ../../content/applications/hr/payroll.rst:209 +#: ../../content/applications/hr/payroll.rst:211 msgid "On this new blank line, enter the name of the employment type in the :guilabel:`Name` column. If the employment type is country-specific, select the country using the drop-down menu in the :guilabel:`Country` column. If a country is selected, then the employment type is *only* applicable for that specific country." msgstr "" -#: ../../content/applications/hr/payroll.rst:214 +#: ../../content/applications/hr/payroll.rst:216 msgid "To rearrange the order of the employment types, click the :guilabel:`six small gray boxes` icon to the left of the employment type :guilabel:`Name`, and drag the line to the desired position on the list." msgstr "" @@ -3618,32 +5247,32 @@ msgstr "" msgid "The employment types in the database by default, in a list view." msgstr "" -#: ../../content/applications/hr/payroll.rst:223 +#: ../../content/applications/hr/payroll.rst:227 #: ../../content/applications/hr/payroll/work_entries.rst:3 msgid "Work entries" msgstr "" -#: ../../content/applications/hr/payroll.rst:225 +#: ../../content/applications/hr/payroll.rst:229 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:230 +#: ../../content/applications/hr/payroll.rst:234 msgid ":doc:`Manage work entries `" msgstr "" -#: ../../content/applications/hr/payroll.rst:233 +#: ../../content/applications/hr/payroll.rst:237 msgid "Work entry types" msgstr "" -#: ../../content/applications/hr/payroll.rst:235 +#: ../../content/applications/hr/payroll.rst:239 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:240 +#: ../../content/applications/hr/payroll.rst:244 msgid "To view the current work entry types available, go to :menuselection:`Payroll app --> Configuration --> Work Entries --> Work Entry Types`." msgstr "" -#: ../../content/applications/hr/payroll.rst:243 +#: ../../content/applications/hr/payroll.rst:247 msgid "Each work entry type has a code to aid in the creation of payslips, and to ensure all taxes and fees are correctly entered." msgstr "" @@ -3651,116 +5280,117 @@ msgstr "" msgid "List of all work entry types currently available for use, with the payroll code and color." msgstr "" -#: ../../content/applications/hr/payroll.rst:251 +#: ../../content/applications/hr/payroll.rst:255 msgid "New work entry type" msgstr "" -#: ../../content/applications/hr/payroll.rst:253 +#: ../../content/applications/hr/payroll.rst:257 msgid "To create a new :guilabel:`Work Entry Type`, click the :guilabel:`New` button, and enter the information for the following sections on the form." msgstr "" -#: ../../content/applications/hr/payroll.rst:257 -#: ../../content/applications/hr/payroll.rst:717 +#: ../../content/applications/hr/payroll.rst:261 +#: ../../content/applications/hr/payroll.rst:725 +#: ../../content/applications/hr/payroll/contracts.rst:43 msgid "General information section" msgstr "" -#: ../../content/applications/hr/payroll.rst:259 +#: ../../content/applications/hr/payroll.rst:263 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:261 +#: ../../content/applications/hr/payroll.rst:265 msgid ":guilabel:`Payroll 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:264 +#: ../../content/applications/hr/payroll.rst:268 msgid ":guilabel:`DMFA code`: this code is used to identify :abbr:`DMFA (De Multifunctionele Aangifte)` entries on a corresponding :abbr:`DMFA (De Multifunctionele Aangifte)` report. The :abbr:`DMFA (De Multifunctionele Aangifte)` report is a quarterly report that Belgian-based companies are required to submit for social security reporting purposes. This report states the work done by the employees during the quarter, as well as the salaries paid to those employees." msgstr "" -#: ../../content/applications/hr/payroll.rst:269 +#: ../../content/applications/hr/payroll.rst:273 msgid ":guilabel:`External Code`: this code is used for exporting data to a third-party payroll service. Check with the third-party being used to determine the :guilabel:`External Code` to enter for the new work entry type." msgstr "" -#: ../../content/applications/hr/payroll.rst:272 +#: ../../content/applications/hr/payroll.rst:276 msgid ":guilabel:`SDWorx code`: this code is only for companies that use SDWorx, a payroll service provider." msgstr "" -#: ../../content/applications/hr/payroll.rst:274 +#: ../../content/applications/hr/payroll.rst:278 msgid ":guilabel:`Color`: select a color for the particular work entry type." msgstr "" -#: ../../content/applications/hr/payroll.rst:277 +#: ../../content/applications/hr/payroll.rst:281 msgid "Display in payslip section" msgstr "" -#: ../../content/applications/hr/payroll.rst:279 +#: ../../content/applications/hr/payroll.rst:283 msgid ":guilabel:`Rounding`: the rounding method selected determines how quantities on timesheet entries are displayed on the payslip." msgstr "" -#: ../../content/applications/hr/payroll.rst:282 +#: ../../content/applications/hr/payroll.rst:286 msgid ":guilabel:`No Rounding`: a timesheet entry is not modified." msgstr "" -#: ../../content/applications/hr/payroll.rst:283 +#: ../../content/applications/hr/payroll.rst:287 msgid ":guilabel:`Half Day`: a timesheet entry is rounded to the closest half day amount." msgstr "" -#: ../../content/applications/hr/payroll.rst:284 +#: ../../content/applications/hr/payroll.rst:288 msgid ":guilabel:`Day`: a timesheet entry is rounded to the closest full day amount." msgstr "" -#: ../../content/applications/hr/payroll.rst:287 +#: ../../content/applications/hr/payroll.rst:291 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:293 +#: ../../content/applications/hr/payroll.rst:297 msgid "Unpaid section" msgstr "" -#: ../../content/applications/hr/payroll.rst:295 -msgid ":guilabel:`Unpaid in Structures Types`: if the work entry is for work that is not paid, specify which pay structure the unpaid work entry applies to from the drop-down menu. Some situations where work would be logged on a timesheet but no compensation given would be for unpaid internships, unpaid training, or volunteer work." +#: ../../content/applications/hr/payroll.rst:299 +msgid ":guilabel:`Unpaid in Structures Types`: if the work entry is for work that is not paid, specify which pay structure the unpaid work entry applies to from the drop-down menu. Some situations where work is logged on a timesheet, but no compensation given would be for unpaid internships, unpaid training, or volunteer work." msgstr "" -#: ../../content/applications/hr/payroll.rst:301 +#: ../../content/applications/hr/payroll.rst:305 msgid "Valid for advantages section" msgstr "" -#: ../../content/applications/hr/payroll.rst:303 +#: ../../content/applications/hr/payroll.rst:307 msgid ":guilabel:`Meal Voucher`: if the work entry should count towards a meal voucher, check the box." msgstr "" -#: ../../content/applications/hr/payroll.rst:304 +#: ../../content/applications/hr/payroll.rst:308 msgid ":guilabel:`Representation Fees`: if the work entry should count towards representation fees, check the box." msgstr "" -#: ../../content/applications/hr/payroll.rst:306 +#: ../../content/applications/hr/payroll.rst:310 msgid ":guilabel:`Private Car Reimbursement`: if the work entry should count towards a private car reimbursement, check the box." msgstr "" -#: ../../content/applications/hr/payroll.rst:310 +#: ../../content/applications/hr/payroll.rst:314 msgid "Time off options section" msgstr "" -#: ../../content/applications/hr/payroll.rst:312 +#: ../../content/applications/hr/payroll.rst:316 msgid ":guilabel:`Time Off`: check this box if the work entry type can be selected for a time off request, or entry, in the *Time Off* application." msgstr "" -#: ../../content/applications/hr/payroll.rst:315 +#: ../../content/applications/hr/payroll.rst:319 msgid "If :guilabel:`Time Off` is checked, a :guilabel:`Time Off Type` field appears. This field has a drop-down menu to select the specific type of time off, such as `Paid Time Off`, `Sick Time Off`, or `Extra Hours`, for example." msgstr "" -#: ../../content/applications/hr/payroll.rst:319 +#: ../../content/applications/hr/payroll.rst:323 msgid "A new type of time off can be entered in the field, if the listed types of time off in the drop-down menu do **not** display the type of time off needed." msgstr "" -#: ../../content/applications/hr/payroll.rst:321 +#: ../../content/applications/hr/payroll.rst:325 msgid ":guilabel:`Keep Time Off Right`: this is for Belgian-specific companies **only**, and does **not** appear for other localizations. Check this box if the work entry is for time off that affects the time off benefits for the following year. Workers are given time off each year, according to the government, and in some cases, time off taken during a specific time period can affect how much time off the employee receives or accrues the following year." msgstr "" -#: ../../content/applications/hr/payroll.rst:328 +#: ../../content/applications/hr/payroll.rst:332 msgid "Reporting section" msgstr "" -#: ../../content/applications/hr/payroll.rst:330 +#: ../../content/applications/hr/payroll.rst:334 msgid ":guilabel:`Unforeseen Absence`: if the work entry should be visible on the unforeseen absences report, check this box." msgstr "" @@ -3768,23 +5398,23 @@ msgstr "" msgid "New work entry type form with all fields to be filled in." msgstr "" -#: ../../content/applications/hr/payroll.rst:340 +#: ../../content/applications/hr/payroll.rst:344 msgid "Working schedules" msgstr "" -#: ../../content/applications/hr/payroll.rst:342 +#: ../../content/applications/hr/payroll.rst:346 msgid "To view the currently configured working schedules, go to :menuselection:`Payroll app --> Configuration --> Work Entries --> Working Schedules`. The working schedules that are available for an employee's contracts and work entries are found in this list." msgstr "" -#: ../../content/applications/hr/payroll.rst:346 +#: ../../content/applications/hr/payroll.rst:350 msgid "Working schedules are company-specific. Each company **must** identify each type of working schedule they use. If the database is created for only one company, the company column is not available." msgstr "" -#: ../../content/applications/hr/payroll.rst:350 +#: ../../content/applications/hr/payroll.rst:354 msgid "An Odoo database containing multiple companies that use a standard 40-hour work week needs to have a separate working schedule entry for each company that uses the 40-hour standard work week." msgstr "" -#: ../../content/applications/hr/payroll.rst:353 +#: ../../content/applications/hr/payroll.rst:357 msgid "A database with five companies that all use a standard 40-hour work week needs to have five separate 40-hour working schedules configured." msgstr "" @@ -3792,27 +5422,27 @@ msgstr "" msgid "All working schedules available to use currently set up in the database for the company." msgstr "" -#: ../../content/applications/hr/payroll.rst:363 +#: ../../content/applications/hr/payroll.rst:367 msgid "New working schedule" msgstr "" -#: ../../content/applications/hr/payroll.rst:365 +#: ../../content/applications/hr/payroll.rst:369 msgid "To create a new working schedule, click the :guilabel:`New` button, and enter the information on the form." msgstr "" -#: ../../content/applications/hr/payroll.rst:368 +#: ../../content/applications/hr/payroll.rst:372 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:372 +#: ../../content/applications/hr/payroll.rst:376 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:378 +#: ../../content/applications/hr/payroll.rst:382 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:381 +#: ../../content/applications/hr/payroll.rst:385 msgid "If the working time should be in a two-week configuration, click the :guilabel:`Switch to 2 weeks calendar` button in the top left. This creates entries for an :guilabel:`Even week` and an :guilabel:`Odd week`." msgstr "" @@ -3820,23 +5450,23 @@ msgstr "" msgid "New working schedule form." msgstr "" -#: ../../content/applications/hr/payroll.rst:395 +#: ../../content/applications/hr/payroll.rst:399 msgid "Structure types" msgstr "" -#: ../../content/applications/hr/payroll.rst:397 +#: ../../content/applications/hr/payroll.rst:401 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:403 +#: ../../content/applications/hr/payroll.rst:407 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:409 +#: ../../content/applications/hr/payroll.rst:413 msgid "The different :guilabel:`Structure Types` can be seen by navigating to :menuselection:`Payroll app --> Configuration --> Salary --> Structure Types`." msgstr "" -#: ../../content/applications/hr/payroll.rst:412 +#: ../../content/applications/hr/payroll.rst:416 msgid "There are two default structure types configured in Odoo: :guilabel:`Employee` and :guilabel:`Worker`. Typically, :guilabel:`Employee` is used for salaried employees, which is why the wage type is :guilabel:`Monthly Fixed Wage`, and :guilabel:`Worker` is typically used for employees paid by the hour, so the wage type is :guilabel:`Hourly Wage`." msgstr "" @@ -3844,59 +5474,59 @@ msgstr "" msgid "List of all currently configured structure types available to use." msgstr "" -#: ../../content/applications/hr/payroll.rst:422 +#: ../../content/applications/hr/payroll.rst:428 msgid "New structure type" msgstr "" -#: ../../content/applications/hr/payroll.rst:424 +#: ../../content/applications/hr/payroll.rst:430 msgid "To make a new structure type, click the :guilabel:`New` button, and a blank structure type form appears." msgstr "" -#: ../../content/applications/hr/payroll.rst:427 +#: ../../content/applications/hr/payroll.rst:433 msgid "Proceed to enter information in the fields. Most fields are pre-populated, but all the fields can be modified." msgstr "" -#: ../../content/applications/hr/payroll.rst:430 +#: ../../content/applications/hr/payroll.rst:436 msgid ":guilabel:`Structure Type`: enter the name for the new structure type, such as `Employee` or `Worker`." msgstr "" -#: ../../content/applications/hr/payroll.rst:432 +#: ../../content/applications/hr/payroll.rst:438 msgid ":guilabel:`Country`: select the country that the new structure type applies to from the drop-down menu." msgstr "" -#: ../../content/applications/hr/payroll.rst:434 +#: ../../content/applications/hr/payroll.rst:440 msgid ":guilabel:`Wage Type`: select what type of wage the new structure type uses, either :guilabel:`Fixed Wage` or :guilabel:`Hourly Wage`." msgstr "" -#: ../../content/applications/hr/payroll.rst:437 +#: ../../content/applications/hr/payroll.rst:443 msgid "If the type is to be used for salaried employees, who receive the same wage every pay period, select :guilabel:`Fixed Wage`." msgstr "" -#: ../../content/applications/hr/payroll.rst:440 +#: ../../content/applications/hr/payroll.rst:446 msgid "If the type is to be used for employees, who receive wages based on how many hours they worked during a pay period, select :guilabel:`Hourly Wage`." msgstr "" -#: ../../content/applications/hr/payroll.rst:442 +#: ../../content/applications/hr/payroll.rst:448 msgid ":guilabel:`Default Scheduled Pay`: select the typical pay schedule for the new structure type from the drop-down menu. Options are :guilabel:`Monthly`, :guilabel:`Quarterly`, :guilabel:`Semi-annually`, :guilabel:`Annually`, :guilabel:`Weekly`, :guilabel:`Bi-weekly`, :guilabel:`Bi-monthly`. This indicates how often this specific type of structure is paid out." msgstr "" -#: ../../content/applications/hr/payroll.rst:446 +#: ../../content/applications/hr/payroll.rst:452 msgid ":guilabel:`Default Working Hours`: select the default working hours for the new structure type from the drop-down menu. All available working hours for the currently selected company appear in the drop-down menu. The default working hours that are pre-configured in Odoo is the :guilabel:`Standard 40 hours/week` option. If the needed working hours do not appear in the list, a :ref:`new set of default working hours can be created `." msgstr "" -#: ../../content/applications/hr/payroll.rst:451 +#: ../../content/applications/hr/payroll.rst:457 msgid ":guilabel:`Regular Pay Structure`: type in the name for the regular pay structure." msgstr "" -#: ../../content/applications/hr/payroll.rst:452 +#: ../../content/applications/hr/payroll.rst:458 msgid ":guilabel:`Default Work Entry Type`: select the default type of work entry the new structure type falls under from the drop-down menu. The default options include :guilabel:`Attendance`, :guilabel:`Overtime Hours`, :guilabel:`Generic Time Off`, :guilabel:`Compensatory Time Off`, :guilabel:`Home Working`, :guilabel:`Unpaid`, :guilabel:`Sick Time Off`, :guilabel:`Paid Time Off`, :guilabel:`Out Of Contract`, :guilabel:`Extra Hours`, and :guilabel:`Long Term Time Off`." msgstr "" -#: ../../content/applications/hr/payroll.rst:458 +#: ../../content/applications/hr/payroll.rst:464 msgid "To view all the options for the :guilabel:`Default Work Entry Type`, click the :guilabel:`Search More..` button at the bottom of the drop-down list." msgstr "" -#: ../../content/applications/hr/payroll.rst:461 +#: ../../content/applications/hr/payroll.rst:467 msgid "Depending on the localization settings, this list may contain more options in addition to the default options." msgstr "" @@ -3904,75 +5534,75 @@ msgstr "" msgid "New structure type form to fill out when creating a new structure type." msgstr "" -#: ../../content/applications/hr/payroll.rst:471 +#: ../../content/applications/hr/payroll.rst:477 msgid "New default working hours" msgstr "" -#: ../../content/applications/hr/payroll.rst:473 +#: ../../content/applications/hr/payroll.rst:479 msgid "To make new default working hours, type the name for the new working hours in the :guilabel:`Default Working Hours` field on the new structure type form. Click :guilabel:`Create and edit`. A default working hours form pops up. The default working hours form has two sections, a general information section and a tab listing out all the individual working hours by day and time. When the form is completed, click :guilabel:`Save & Close`." msgstr "" -#: ../../content/applications/hr/payroll.rst:479 +#: ../../content/applications/hr/payroll.rst:485 msgid ":guilabel:`Name`: type in the name for the new default working hours. This should be descriptive and clear to understand, such as `Standard 20 Hours/Week`." msgstr "" -#: ../../content/applications/hr/payroll.rst:481 +#: ../../content/applications/hr/payroll.rst:487 msgid ":guilabel:`Company`: select the company that can use these new default working hours from the drop-down menu. Keep in mind, working hours are company-specific, and cannot be shared between companies. Each company needs to have their own working hours set." msgstr "" -#: ../../content/applications/hr/payroll.rst:484 +#: ../../content/applications/hr/payroll.rst:490 msgid ":guilabel:`Average Hour Per Day`: the average hours per day field is auto-populated, based on the working hours configured in the :guilabel:`Working Hours` tab. This entry affects resource planning, since the average daily hours affect what resources can be used, and in what quantity, per work day." msgstr "" -#: ../../content/applications/hr/payroll.rst:488 +#: ../../content/applications/hr/payroll.rst:494 msgid ":guilabel:`Timezone`: select the time zone to be used for the new default working hours from the drop-down menu." msgstr "" -#: ../../content/applications/hr/payroll.rst:490 +#: ../../content/applications/hr/payroll.rst:496 msgid ":guilabel:`Company Full Time`: enter the number of hours per week an employee would need to work to be considered a full-time employee. Typically, this is approximately 40 hours, and this number affects what types of benefits an employee can receive, based on their employment status (full-time vs part-time)." msgstr "" -#: ../../content/applications/hr/payroll.rst:494 +#: ../../content/applications/hr/payroll.rst:500 msgid ":guilabel:`Work Time Rate`: this percentage is auto-generated based on the entry for the :guilabel:`Company Full Time` and the working hours configured in the :guilabel:`Working Hours` tab. This number should be between `0.00%` and `100%`, so if the percentage is above `100%`, it is an indication that the working times and/or :guilabel:`Company Full Time` hours need adjustment." msgstr "" -#: ../../content/applications/hr/payroll.rst:498 +#: ../../content/applications/hr/payroll.rst:504 msgid ":guilabel:`Working Hours` Tab: this tab is where each day's specific working hours are listed. When a new default working hour form is created, the :guilabel:`Working Hours` tab is pre-populated with a default 40-hour week, with each day divided into three timed sections." msgstr "" -#: ../../content/applications/hr/payroll.rst:502 +#: ../../content/applications/hr/payroll.rst:508 msgid "Every day has morning (8:00-12:00), lunch (12:00-13:00), and evening (13:00-17:00) hours configured, using a 24 hour time format." msgstr "" -#: ../../content/applications/hr/payroll.rst:505 +#: ../../content/applications/hr/payroll.rst:511 msgid "To adjust any of these hours, click on the specific field to adjust, and make the adjustment using the drop-down menus, or in the specific case of the times, type in the desired time." msgstr "" -#: ../../content/applications/hr/payroll.rst:508 +#: ../../content/applications/hr/payroll.rst:514 msgid "Keep in mind, working hours are company-specific, and cannot be shared between companies. Each company needs to have their own working hours set." msgstr "" -#: ../../content/applications/hr/payroll.rst:512 +#: ../../content/applications/hr/payroll.rst:518 msgid "If the working hours are not consistent each week, and the hours are on a bi-weekly schedule instead, click the :guilabel:`Switch to 2 week calendar` button at the top of the new default working hours form. This changes the :guilabel:`Working Hours` tab to display two weeks of working times that can be adjusted." msgstr "" -#: ../../content/applications/hr/payroll.rst:518 +#: ../../content/applications/hr/payroll.rst:524 msgid "Structures" msgstr "" -#: ../../content/applications/hr/payroll.rst:520 +#: ../../content/applications/hr/payroll.rst:526 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:523 +#: ../../content/applications/hr/payroll.rst:529 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:527 +#: ../../content/applications/hr/payroll.rst:533 msgid "To view all the various structures for each structure type, go to :menuselection:`Payroll app --> Configuration --> Salary --> Structures`." msgstr "" -#: ../../content/applications/hr/payroll.rst:530 +#: ../../content/applications/hr/payroll.rst:536 msgid "Each :ref:`structure type ` lists the various structures associated with it. Each structure contains a set of rules that define it." msgstr "" @@ -3980,7 +5610,7 @@ msgstr "" msgid "All available salary structures." msgstr "" -#: ../../content/applications/hr/payroll.rst:537 +#: ../../content/applications/hr/payroll.rst:543 msgid "Click on a structure to view its :guilabel:`Salary Rules`. These rules are what calculate the payslip for the employee." msgstr "" @@ -3988,60 +5618,60 @@ msgstr "" msgid "Salary structure details for Regular Pay, listing all the specific Salary Rules." msgstr "" -#: ../../content/applications/hr/payroll.rst:545 -#: ../../content/applications/hr/time_off.rst:193 +#: ../../content/applications/hr/payroll.rst:551 +#: ../../content/applications/hr/time_off.rst:258 msgid "Rules" msgstr "" -#: ../../content/applications/hr/payroll.rst:547 +#: ../../content/applications/hr/payroll.rst:553 msgid "Each structure has a set of *salary rules* to follow for accounting purposes. These rules are configured by the localization, and affect actions in 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:551 +#: ../../content/applications/hr/payroll.rst:557 msgid "To view all the rules, go to :menuselection:`Payroll app --> Configuration --> Salary --> Rules`. Click on a structure (such as :guilabel:`Regular Pay`) to view all the rules." msgstr "" -#: ../../content/applications/hr/payroll.rst:554 +#: ../../content/applications/hr/payroll.rst:560 msgid "To make a new rule, click :guilabel:`New`. A new rule form appears. Enter the following information in the fields." msgstr "" -#: ../../content/applications/hr/payroll.rst:558 +#: ../../content/applications/hr/payroll.rst:564 msgid "Top section" msgstr "" -#: ../../content/applications/hr/payroll.rst:560 +#: ../../content/applications/hr/payroll.rst:566 msgid ":guilabel:`Rule Name`: enter a name for the rule. This field is required." msgstr "" -#: ../../content/applications/hr/payroll.rst:561 +#: ../../content/applications/hr/payroll.rst:567 msgid ":guilabel:`Category`: select a category the rule applies to from the drop-down menu, or enter a new one. This field is required." msgstr "" -#: ../../content/applications/hr/payroll.rst:563 +#: ../../content/applications/hr/payroll.rst:569 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 to use as this affects accounting reports and payroll processing. This field is required." msgstr "" -#: ../../content/applications/hr/payroll.rst:566 +#: ../../content/applications/hr/payroll.rst:572 msgid ":guilabel:`Sequence`: enter a number indicating when this rule is calculated in the sequence of all other rules." msgstr "" -#: ../../content/applications/hr/payroll.rst:568 +#: ../../content/applications/hr/payroll.rst:574 msgid ":guilabel:`Salary Structure`: select a salary structure the rule applies to from the drop-down menu, or enter a new one. This field is required." msgstr "" -#: ../../content/applications/hr/payroll.rst:570 +#: ../../content/applications/hr/payroll.rst:576 msgid ":guilabel:`Active`: enable this toggle, so the rule is available for use. Disable the toggle to hide the rule without deleting it in the database." msgstr "" -#: ../../content/applications/hr/payroll.rst:572 +#: ../../content/applications/hr/payroll.rst:578 msgid ":guilabel:`Appears on payslip`: tick the checkbox to have the rule appear on employee payslips." msgstr "" -#: ../../content/applications/hr/payroll.rst:573 +#: ../../content/applications/hr/payroll.rst:579 msgid ":guilabel:`View on Employer Cost Dashboard`: tick the checkbox to have the rule appear on the :guilabel:`Employer Cost` report, located on the *Payroll* app dashboard." msgstr "" -#: ../../content/applications/hr/payroll.rst:575 +#: ../../content/applications/hr/payroll.rst:581 msgid ":guilabel:`View on Payroll Reporting`: tick the checkbox to have the rule appear on payroll reports." msgstr "" @@ -4049,72 +5679,72 @@ msgstr "" msgid "Enter the information for the new rule on the new rule form." msgstr "" -#: ../../content/applications/hr/payroll.rst:583 +#: ../../content/applications/hr/payroll.rst:589 msgid "General tab" msgstr "" -#: ../../content/applications/hr/payroll.rst:586 +#: ../../content/applications/hr/payroll.rst:592 msgid "Conditions" msgstr "" -#: ../../content/applications/hr/payroll.rst:588 +#: ../../content/applications/hr/payroll.rst:594 msgid ":guilabel:`Condition Based on`: 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). This field is required." msgstr "" -#: ../../content/applications/hr/payroll.rst:594 +#: ../../content/applications/hr/payroll.rst:600 msgid "Computation" msgstr "" -#: ../../content/applications/hr/payroll.rst:596 +#: ../../content/applications/hr/payroll.rst:602 msgid ":guilabel:`Amount Type`: 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. This field is required." msgstr "" -#: ../../content/applications/hr/payroll.rst:602 +#: ../../content/applications/hr/payroll.rst:608 msgid "Company contribution" msgstr "" -#: ../../content/applications/hr/payroll.rst:604 +#: ../../content/applications/hr/payroll.rst:610 msgid ":guilabel:`Partner`: if another company financially contributes to this rule, select the company from the drop-down menu." msgstr "" -#: ../../content/applications/hr/payroll.rst:608 -#: ../../content/applications/hr/payroll.rst:802 +#: ../../content/applications/hr/payroll.rst:614 +#: ../../content/applications/hr/payroll.rst:810 msgid "Description tab" msgstr "" -#: ../../content/applications/hr/payroll.rst:610 +#: ../../content/applications/hr/payroll.rst:616 msgid "Provide any additional information in this tab to help clarify the rule. This tab only appears in the rule form." msgstr "" -#: ../../content/applications/hr/payroll.rst:614 +#: ../../content/applications/hr/payroll.rst:620 msgid "Accounting tab" msgstr "" -#: ../../content/applications/hr/payroll.rst:616 +#: ../../content/applications/hr/payroll.rst:622 msgid ":guilabel:`Debit Account`: select the debit account from the drop-down menu the rule affects." msgstr "" -#: ../../content/applications/hr/payroll.rst:617 +#: ../../content/applications/hr/payroll.rst:623 msgid ":guilabel:`Credit Account`: select the credit account from the drop-down menu the rule affects." msgstr "" -#: ../../content/applications/hr/payroll.rst:618 +#: ../../content/applications/hr/payroll.rst:624 msgid ":guilabel:`Not computed in net accountability`: tick the checkbox to delete the value of this rule in the `Net Salary` rule." msgstr "" -#: ../../content/applications/hr/payroll.rst:622 +#: ../../content/applications/hr/payroll.rst:628 msgid "Rule parameters" msgstr "" -#: ../../content/applications/hr/payroll.rst:625 +#: ../../content/applications/hr/payroll.rst:631 msgid "Currently, the :guilabel:`Rule Parameters` feature found inside the :menuselection:`Payroll app --> Configuration --> Salary --> Rule Parameters` 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:631 +#: ../../content/applications/hr/payroll.rst:637 msgid "Other input types" msgstr "" -#: ../../content/applications/hr/payroll.rst:633 +#: ../../content/applications/hr/payroll.rst:639 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 navigating to :menuselection:`Payroll app --> Configuration --> Salary --> Other Input Types`." msgstr "" @@ -4123,11 +5753,11 @@ msgid "A list of other input types for payroll that can be selected when creatin "a payslip." msgstr "" -#: ../../content/applications/hr/payroll.rst:642 +#: ../../content/applications/hr/payroll.rst:648 msgid "To create a new input type, click the :guilabel:`New` button. Enter the :guilabel:`Description`, the :guilabel:`Code`, and which structure it applies to in the :guilabel:`Availability in Structure` field." msgstr "" -#: ../../content/applications/hr/payroll.rst:647 +#: ../../content/applications/hr/payroll.rst:653 msgid "The :guilabel:`Code` is used in the salary rules to compute payslips. If the :guilabel:`Availability in Structure` field is left blank, it indicates that the new input type is available for all payslips and is not exclusive to a specific structure." msgstr "" @@ -4135,19 +5765,19 @@ msgstr "" msgid "A new Input Type form filled in." msgstr "" -#: ../../content/applications/hr/payroll.rst:656 +#: ../../content/applications/hr/payroll.rst:664 msgid "Salary attachment types" msgstr "" -#: ../../content/applications/hr/payroll.rst:658 +#: ../../content/applications/hr/payroll.rst:666 msgid "Salary attachments, also thought of as \"wage garnishments\", are portions of earnings taken out of a payslip for something specific. Much like all other aspects of payroll configurations, the types of salary attachments **must** be defined." msgstr "" -#: ../../content/applications/hr/payroll.rst:662 +#: ../../content/applications/hr/payroll.rst:670 msgid "To view the currently configured salary attachments, navigate to :menuselection:`Payroll app --> Configuration --> Salary --> Salary Attachment Types`. The default salary attachment types are :guilabel:`Attachment of Salary`, :guilabel:`Assignment of Salary`, and :guilabel:`Child Support`." msgstr "" -#: ../../content/applications/hr/payroll.rst:666 +#: ../../content/applications/hr/payroll.rst:674 msgid "To make a new type of salary attachment, click the :guilabel:`New` button. Then, enter the :guilabel:`Name`, the :guilabel:`Code` (used in the salary rules to compute payslips), and decide if it should have :guilabel:`No End Date`." msgstr "" @@ -4155,27 +5785,27 @@ msgstr "" msgid "A new salary attachment form filled in." msgstr "" -#: ../../content/applications/hr/payroll.rst:675 +#: ../../content/applications/hr/payroll.rst:683 msgid "Salary package configurator" msgstr "" -#: ../../content/applications/hr/payroll.rst:677 +#: ../../content/applications/hr/payroll.rst:685 msgid "The various options under the :guilabel:`Salary Package Configurator` section of the :menuselection:`Payroll app --> Configuration --> Salary Package Configurator` menu all affect an employee's potential salary. These sections (:guilabel:`Benefits`, :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:682 +#: ../../content/applications/hr/payroll.rst:690 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:688 +#: ../../content/applications/hr/payroll.rst:696 msgid "Benefits" msgstr "" -#: ../../content/applications/hr/payroll.rst:690 +#: ../../content/applications/hr/payroll.rst:698 msgid "When offering potential employees a position, there can be certain benefits set in Odoo, in addition to the salary, to make an offer more appealing (such as extra time off, the use of a company car, reimbursement for a phone or internet, etc.)." msgstr "" -#: ../../content/applications/hr/payroll.rst:694 +#: ../../content/applications/hr/payroll.rst:702 msgid "To view the benefits, go to :menuselection:`Payroll app --> Configuration --> Salary Package Configurator: Benefits`. Benefits are grouped by :guilabel:`Structure type`, and the benefit listed for a particular structure type is only available for that specific structure." msgstr "" @@ -4183,67 +5813,67 @@ msgstr "" msgid "A list view of all the benefits available for each structure type." msgstr "" -#: ../../content/applications/hr/payroll.rst:703 +#: ../../content/applications/hr/payroll.rst:711 msgid "A company has two structure types, one labeled :guilabel:`Employee`, and another labeled :guilabel:`Intern`. The :guilabel:`Employee` structure type contains the benefit of using a company car, while the :guilabel:`Intern` structure type has a meal voucher benefit available." msgstr "" -#: ../../content/applications/hr/payroll.rst:707 +#: ../../content/applications/hr/payroll.rst:715 msgid "A person hired under the :guilabel:`Employee` structure type can use the company car benefit, but cannot have meal vouchers. A person hired under the :guilabel:`Intern` structure type would have meal voucher benefits available to them, not the use of a company car." msgstr "" -#: ../../content/applications/hr/payroll.rst:711 +#: ../../content/applications/hr/payroll.rst:719 msgid "To make a new benefit, click the :guilabel:`New` button, and enter the information in the fields on the blank benefits form." msgstr "" -#: ../../content/applications/hr/payroll.rst:714 +#: ../../content/applications/hr/payroll.rst:722 msgid "The various fields for creating a benefit are as follows:" msgstr "" -#: ../../content/applications/hr/payroll.rst:719 +#: ../../content/applications/hr/payroll.rst:727 msgid ":guilabel:`Benefits`: enter the name for the benefit. This field is required." msgstr "" -#: ../../content/applications/hr/payroll.rst:720 +#: ../../content/applications/hr/payroll.rst:728 msgid ":guilabel:`Benefit Field`: select from the drop-down menu the type of benefit this is." msgstr "" -#: ../../content/applications/hr/payroll.rst:721 +#: ../../content/applications/hr/payroll.rst:729 msgid ":guilabel:`Cost Field`: select from the drop-down menu the type of cost incurred by the company for this specific benefit. The default options are :guilabel:`Calendar Changed`, :guilabel:`Yearly Cost (Real)`, :guilabel:`Extra Time Off`, :guilabel:`Hourly Wage`, :guilabel:`Part Time`, :guilabel:`Wage`, :guilabel:`Wage with Holidays`, and :guilabel:`Work time rate`. Depending on the localization settings, additional options are available." msgstr "" -#: ../../content/applications/hr/payroll.rst:726 +#: ../../content/applications/hr/payroll.rst:734 msgid ":guilabel:`Related Type`: select from the drop-down menu what type of benefit it is. Select from :guilabel:`Monthly Benefit in Kind`, :guilabel:`Monthly Benefit in Net`, :guilabel:`Monthly Benefit in Cash`, :guilabel:`Yearly Benefits in Cash`, or :guilabel:`Non Financial Benefits`. This field is required." msgstr "" -#: ../../content/applications/hr/payroll.rst:730 +#: ../../content/applications/hr/payroll.rst:738 msgid ":guilabel:`Benefit Field`: select from the drop-down menu the specific field on the contract the benefit appears." msgstr "" -#: ../../content/applications/hr/payroll.rst:732 +#: ../../content/applications/hr/payroll.rst:740 msgid ":guilabel:`Cost Field`: select the specific field on the contract that the cost of the benefit is linked to, using the drop-down menu. If this field is left blank, the cost of the benefit is not computed in the employee budget." msgstr "" -#: ../../content/applications/hr/payroll.rst:735 +#: ../../content/applications/hr/payroll.rst:743 msgid ":guilabel:`Impacts Net Salary`: tick the checkbox if the benefit should impact the employee's net salary." msgstr "" -#: ../../content/applications/hr/payroll.rst:737 +#: ../../content/applications/hr/payroll.rst:745 msgid ":guilabel:`Requested Documents`: select any document that is required to be submitted for this benefit, from the drop-down menu." msgstr "" -#: ../../content/applications/hr/payroll.rst:739 +#: ../../content/applications/hr/payroll.rst:747 msgid ":guilabel:`Mandatory Benefits`: using the drop-down menu, select the benefit that is required in order for this specific benefit to be offered to the employee." msgstr "" -#: ../../content/applications/hr/payroll.rst:742 +#: ../../content/applications/hr/payroll.rst:750 msgid "For example, a benefit for car insurance would populate `Company Car` in this field. This would allow the car insurance benefit to **only** be displayed if the employee has selected/enabled the benefit of a company car." msgstr "" -#: ../../content/applications/hr/payroll.rst:745 +#: ../../content/applications/hr/payroll.rst:753 msgid ":guilabel:`Salary Structure Type`: select from the drop-down menu which salary structure type this benefit applies to. This field is required." msgstr "" -#: ../../content/applications/hr/payroll.rst:747 +#: ../../content/applications/hr/payroll.rst:755 msgid ":guilabel:`Unit of Measure`: select the metric that the benefit is granted, using the drop-down menu. The options are :guilabel:`Days`, :guilabel:`Percent`, or :guilabel:`Currency`." msgstr "" @@ -4251,99 +5881,100 @@ msgstr "" msgid "A new benefit form filled out for an internet subscription." msgstr "" -#: ../../content/applications/hr/payroll.rst:755 +#: ../../content/applications/hr/payroll.rst:763 msgid "Display section" msgstr "" -#: ../../content/applications/hr/payroll.rst:757 +#: ../../content/applications/hr/payroll.rst:765 msgid ":guilabel:`Show Name`: tick the checkbox to have the benefit name appear in the salary package configurator." msgstr "" -#: ../../content/applications/hr/payroll.rst:759 +#: ../../content/applications/hr/payroll.rst:767 msgid ":guilabel:`Display Type`: select from the drop-down menu how this benefit is displayed. The options are :guilabel:`Always Selected`, :guilabel:`Dropdown`, :guilabel:`Dropdown Group`, :guilabel:`Slider`, :guilabel:`Radio Buttons`, :guilabel:`Manual Input`, or :guilabel:`Text`. This field is required." msgstr "" -#: ../../content/applications/hr/payroll.rst:764 +#: ../../content/applications/hr/payroll.rst:772 msgid "Depending on the selection made, additional configurations need to be made. For example, if :guilabel:`Radio Buttons` is selected, the individual radio buttons must be entered." msgstr "" -#: ../../content/applications/hr/payroll.rst:766 +#: ../../content/applications/hr/payroll.rst:774 msgid ":guilabel:`Icon`: an icon from the `Font Awesome 4 library `_ can be visible for this benefit. Enter the text code for the icon in this field. For example, to display a suitcase icon, the code `fa fa-suitcase` is entered on this line." msgstr "" -#: ../../content/applications/hr/payroll.rst:769 +#: ../../content/applications/hr/payroll.rst:777 msgid ":guilabel:`Hide Description`: tick the checkbox to hide the benefit description if the benefit is not selected by the employee." msgstr "" -#: ../../content/applications/hr/payroll.rst:771 +#: ../../content/applications/hr/payroll.rst:779 msgid ":guilabel:`Folded`: if the benefit should be folded, or hidden, because it is dependant on another benefit selection, tick the checkbox. The following fields appear when this is active:" msgstr "" -#: ../../content/applications/hr/payroll.rst:774 +#: ../../content/applications/hr/payroll.rst:782 msgid ":guilabel:`Fold Label`: enter a name for the folded section of the benefit." msgstr "" -#: ../../content/applications/hr/payroll.rst:775 +#: ../../content/applications/hr/payroll.rst:783 msgid ":guilabel:`Fold Res Field`: select the contract field this benefit is tied to using the drop-down menu. If this field is selected on the contract, then this benefit becomes visible." msgstr "" -#: ../../content/applications/hr/payroll.rst:779 +#: ../../content/applications/hr/payroll.rst:787 msgid "Activity section" msgstr "" -#: ../../content/applications/hr/payroll.rst:781 +#: ../../content/applications/hr/payroll.rst:789 msgid ":guilabel:`Activity Type`: from the drop-down menu, select the activity type that is automatically created when this benefit is selected by the employee." msgstr "" -#: ../../content/applications/hr/payroll.rst:783 +#: ../../content/applications/hr/payroll.rst:791 msgid ":guilabel:`Activity Creation`: select when the activity is created, either when the :guilabel:`Employee signs his contract`, or when the :guilabel:`Contract is countersigned`. Click the radio button next to the desired selection." msgstr "" -#: ../../content/applications/hr/payroll.rst:786 +#: ../../content/applications/hr/payroll.rst:794 msgid ":guilabel:`Activity Creation Type`: select the parameters for when the activity is created, either :guilabel:`When the benefit is set` or :guilabel:`When the benefit is modified`. Click the radio button next to the desired selection." msgstr "" -#: ../../content/applications/hr/payroll.rst:789 +#: ../../content/applications/hr/payroll.rst:797 msgid ":guilabel:`Assigned to`: select the user the activity is automatically assigned to, using the drop-down menu." msgstr "" -#: ../../content/applications/hr/payroll.rst:793 +#: ../../content/applications/hr/payroll.rst:801 +#: ../../content/applications/hr/payroll/contracts.rst:143 msgid "Sign section" msgstr "" -#: ../../content/applications/hr/payroll.rst:795 +#: ../../content/applications/hr/payroll.rst:803 msgid ":guilabel:`Template to Sign`: if the employee is required to sign a document when selecting this benefit, select the document template from the drop-down menu." msgstr "" -#: ../../content/applications/hr/payroll.rst:798 +#: ../../content/applications/hr/payroll.rst:806 msgid "For example, a benefit regarding the use of a company car may require the employee to sign a document acknowledging the company's car policies." msgstr "" -#: ../../content/applications/hr/payroll.rst:804 +#: ../../content/applications/hr/payroll.rst:812 msgid "Provide any additional information in this tab to help clarify the benefit." msgstr "" -#: ../../content/applications/hr/payroll.rst:807 +#: ../../content/applications/hr/payroll.rst:815 msgid "Personal info" msgstr "" -#: ../../content/applications/hr/payroll.rst:809 +#: ../../content/applications/hr/payroll.rst:817 msgid "Every employee in Odoo has an *employee card* which is created when a candidate becomes an employee. This card includes all of their personal information, resume, work information, and documents." msgstr "" -#: ../../content/applications/hr/payroll.rst:813 +#: ../../content/applications/hr/payroll.rst:821 msgid "The personal information is gathered from the salary package configurator section that a candidate fills out after being offered a position. This personal information is then transferred to the employee card when they are hired." msgstr "" -#: ../../content/applications/hr/payroll.rst:817 +#: ../../content/applications/hr/payroll.rst:825 msgid "To view an employee's card, go to the main :menuselection:`Employees` app dashboard, and click on the employee's card." msgstr "" -#: ../../content/applications/hr/payroll.rst:821 +#: ../../content/applications/hr/payroll.rst:829 msgid "An employee card can be thought of as an employee personnel file." msgstr "" -#: ../../content/applications/hr/payroll.rst:823 +#: ../../content/applications/hr/payroll.rst:831 msgid "The :guilabel:`Personal Info` section lists all of the fields that are available to enter on the employee's card. To access this section, go to :menuselection:`Payroll app --> Configuration --> Salary Package Configurator: Personal Info`." msgstr "" @@ -4351,31 +5982,31 @@ msgstr "" msgid "A list of all the personal information that appears on the employee card to enter." msgstr "" -#: ../../content/applications/hr/payroll.rst:831 +#: ../../content/applications/hr/payroll.rst:839 msgid "To edit a personal info entry, select an entry from the list on the :guilabel:`Personal Info` page, and modify the personal info on the form that appears." msgstr "" -#: ../../content/applications/hr/payroll.rst:834 +#: ../../content/applications/hr/payroll.rst:842 msgid "To create a new personal info entry, click the :guilabel:`New` button." msgstr "" -#: ../../content/applications/hr/payroll.rst:836 +#: ../../content/applications/hr/payroll.rst:844 msgid "The required fields, aside from entering the :guilabel:`Information` name, are :guilabel:`Related Model`, :guilabel:`Related Field`, and :guilabel:`Category`." msgstr "" -#: ../../content/applications/hr/payroll.rst:839 +#: ../../content/applications/hr/payroll.rst:847 msgid "Select a :guilabel:`Related Model` from the drop-down menu. :guilabel:`Employee` populates the field by default, but the :guilabel:`Bank Account` option is also available if the information is related to a bank account, instead." msgstr "" -#: ../../content/applications/hr/payroll.rst:843 +#: ../../content/applications/hr/payroll.rst:851 msgid "Select a :guilabel:`Related Field` from the drop-down menu that best describes what kind of personal information this entry is, and where it is stored in the backend. Then, select a :guilabel:`Category` from the drop-down menu that the personal information should be under, such as :guilabel:`Address` or :guilabel:`Personal Documents`." msgstr "" -#: ../../content/applications/hr/payroll.rst:848 +#: ../../content/applications/hr/payroll.rst:856 msgid "The two most important fields on the personal info form are :guilabel:`Is Required` and :guilabel:`Display Type`." msgstr "" -#: ../../content/applications/hr/payroll.rst:851 +#: ../../content/applications/hr/payroll.rst:859 msgid "Checking the :guilabel:`Is Required` box makes the field mandatory on the employee's card. The :guilabel:`Display Type` drop-down menu allows for the information to be entered in a variety of ways, like a :guilabel:`Text` box, to a customizable :guilabel:`Radio` button, a :guilabel:`Checkbox`, a :guilabel:`Document`, and more." msgstr "" @@ -4383,71 +6014,71 @@ msgstr "" msgid "New personal information entry." msgstr "" -#: ../../content/applications/hr/payroll.rst:863 +#: ../../content/applications/hr/payroll.rst:871 msgid "The resumé section, housed within the salary package configurator section of the settings menu, is how salary information rules are configured when offering a position to potential employees." msgstr "" -#: ../../content/applications/hr/payroll.rst:866 +#: ../../content/applications/hr/payroll.rst:874 msgid "When an offer is sent to a prospective employee, the values for the offer are computed from these settings, and appear on the offer page." msgstr "" -#: ../../content/applications/hr/payroll.rst:869 +#: ../../content/applications/hr/payroll.rst:877 msgid "To configure this section, navigate to :menuselection:`Payroll app --> Configuration --> Salary Package Configurator: Resumé`." msgstr "" -#: ../../content/applications/hr/payroll.rst:872 +#: ../../content/applications/hr/payroll.rst:880 msgid "By default, there are three :guilabel:`Salary Structure Types` pre-configured in Odoo: :guilabel:`Worker`, :guilabel:`Employee`, and :guilabel:`None`." msgstr "" -#: ../../content/applications/hr/payroll.rst:875 +#: ../../content/applications/hr/payroll.rst:883 msgid "Each :guilabel:`Salary Structure Type` has several rules configured. These affect how an offer is calculated using that particular :guilabel:`Salary Structure Type`." msgstr "" -#: ../../content/applications/hr/payroll.rst:878 +#: ../../content/applications/hr/payroll.rst:886 msgid "To create a new rule, click the :guilabel:`New` button, and a blank :guilabel:`Contract Salary Resumé` form loads." msgstr "" -#: ../../content/applications/hr/payroll.rst:883 +#: ../../content/applications/hr/payroll.rst:891 msgid ":guilabel:`Information`: type in a name for this field." msgstr "" -#: ../../content/applications/hr/payroll.rst:884 +#: ../../content/applications/hr/payroll.rst:892 msgid ":guilabel:`Category`: select the category this value is housed under, using the drop-down menu. The default options are :guilabel:`Monthly Salary`, :guilabel:`Monthly Benefits`, :guilabel:`Yearly Benefits`, and :guilabel:`Total`." msgstr "" -#: ../../content/applications/hr/payroll.rst:888 +#: ../../content/applications/hr/payroll.rst:896 msgid "New categories can be made if needed." msgstr "" -#: ../../content/applications/hr/payroll.rst:890 +#: ../../content/applications/hr/payroll.rst:898 msgid "Click the :guilabel:`New` button, then enter the name for the new category in the :guilabel:`Name` field. Next, select the :guilabel:`Periodicity` from the drop-down menu, either :guilabel:`Monthly` or :guilabel:`Yearly`. Last, enter a number for the sequence. This corresponds to where this rule appears in the :guilabel:`Salary Structure Type` rule list." msgstr "" -#: ../../content/applications/hr/payroll.rst:895 +#: ../../content/applications/hr/payroll.rst:903 msgid "Finally, click :guilabel:`Save & Close`." msgstr "" -#: ../../content/applications/hr/payroll.rst:896 +#: ../../content/applications/hr/payroll.rst:904 msgid ":guilabel:`Impacts Monthly Total`: tick the checkbox if this value is added in the monthly total calculation." msgstr "" -#: ../../content/applications/hr/payroll.rst:898 +#: ../../content/applications/hr/payroll.rst:906 msgid ":guilabel:`Unit of Measure`: select what kind of value this rule is, either :guilabel:`Currency`, :guilabel:`Days`, or :guilabel:`Percent`." msgstr "" -#: ../../content/applications/hr/payroll.rst:901 +#: ../../content/applications/hr/payroll.rst:909 msgid ":guilabel:`Currency` is for a set monetary value, :guilabel:`Days` is for compensation in the form of time off, and :guilabel:`Percent` is for a monetary value awarded that is based upon another metric, such as commissions." msgstr "" -#: ../../content/applications/hr/payroll.rst:904 +#: ../../content/applications/hr/payroll.rst:912 msgid ":guilabel:`Salary Structure Type`: select which :guilabel:`Salary Structure Type` this rule is nested under, from the drop-down menu." msgstr "" -#: ../../content/applications/hr/payroll.rst:906 +#: ../../content/applications/hr/payroll.rst:914 msgid ":guilabel:`Value Type`: select how the value is computed, using the drop-down menu. The default options are :guilabel:`Fixed Value`, :guilabel:`Contract Value`, :guilabel:`Payslip Value`, :guilabel:`Sum of Benefits Values`, and :guilabel:`Monthly Total`." msgstr "" -#: ../../content/applications/hr/payroll.rst:909 +#: ../../content/applications/hr/payroll.rst:917 msgid ":guilabel:`Code`: select the code this rule applies to from the drop-down menu." msgstr "" @@ -4455,28 +6086,28 @@ msgstr "" msgid "The net wage rule form filled out, with all the information for net pay." msgstr "" -#: ../../content/applications/hr/payroll.rst:916 +#: ../../content/applications/hr/payroll.rst:924 msgid "Jobs" msgstr "" -#: ../../content/applications/hr/payroll.rst:918 +#: ../../content/applications/hr/payroll.rst:926 msgid "Since the *Payroll* application is responsible for paying employees for specific job positions, the complete list of job positions can be found in both the *Payroll* and *Recruitment* applications." msgstr "" -#: ../../content/applications/hr/payroll.rst:924 +#: ../../content/applications/hr/payroll.rst:932 #: ../../content/applications/hr/recruitment/new_job.rst:3 msgid "Job positions" msgstr "" -#: ../../content/applications/hr/payroll.rst:926 +#: ../../content/applications/hr/payroll.rst:934 msgid "The job positions listed in the *Payroll* application are identical to the job positions listed in the *Recruitment* application. If a new job position is added in the *Recruitment* application, it is also visible in the *Payroll* application, and vice versa." msgstr "" -#: ../../content/applications/hr/payroll.rst:930 +#: ../../content/applications/hr/payroll.rst:938 msgid "To view the job positions, navigate to :menuselection:`Payroll app --> Configuration --> Jobs: Job Positions`." msgstr "" -#: ../../content/applications/hr/payroll.rst:933 +#: ../../content/applications/hr/payroll.rst:941 msgid "A list of all the job positions appear, along with the corresponding department, on the :guilabel:`Job Position` page." msgstr "" @@ -4484,317 +6115,442 @@ msgstr "" msgid "A list of all the job positions and corresponding departments." msgstr "" -#: ../../content/applications/hr/payroll.rst:940 +#: ../../content/applications/hr/payroll.rst:948 msgid "To create a new job description, click the :guilabel:`New` button and a job form appears." msgstr "" -#: ../../content/applications/hr/payroll.rst:942 +#: ../../content/applications/hr/payroll.rst:950 msgid "Enter the information on the form for the new position. The information is identical as to the information entered when creating a new job position in the *Recruitment* application." msgstr "" -#: ../../content/applications/hr/payroll.rst:945 +#: ../../content/applications/hr/payroll.rst:953 msgid "Refer to the :doc:`../hr/recruitment/new_job` documentation for more details on how to fill out this form." msgstr "" -#: ../../content/applications/hr/payroll.rst:949 +#: ../../content/applications/hr/payroll.rst:957 msgid ":doc:`payroll/contracts`" msgstr "" -#: ../../content/applications/hr/payroll.rst:950 +#: ../../content/applications/hr/payroll.rst:958 msgid ":doc:`payroll/payslips`" msgstr "" -#: ../../content/applications/hr/payroll.rst:951 +#: ../../content/applications/hr/payroll.rst:959 msgid ":doc:`payroll/work_entries`" msgstr "" -#: ../../content/applications/hr/payroll.rst:952 +#: ../../content/applications/hr/payroll.rst:960 msgid ":doc:`payroll/reporting`" msgstr "" #: ../../content/applications/hr/payroll/contracts.rst:5 -msgid "Every employee in Odoo is required to have a contract in order to be paid. A contract outlines the terms of an employee's position, their compensation, their working hours, and any other details about their position." +msgid "Every employee in Odoo is required to have a contract to be paid. A contract outlines the terms of an employee's job position, compensation, working hours, and any other details specific to their role." 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." +msgid "Contract documents (PDFs) are uploaded and organized using the *Documents* application, and are signed using the *Sign* application. Ensure these applications are installed to send and sign contracts. Please refer to the :doc:`../../productivity/documents` and :doc:`../../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." +msgid "To view the employee contracts, go to :menuselection:`Payroll app --> Contracts --> Contracts` from the top menu. All employee contracts are displayed in a default list view, grouped into four categories: :guilabel:`New`, :guilabel:`Running`, :guilabel:`Expired`, and :guilabel:`Cancelled`." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:19 +msgid "The default view has all categories collapsed. The number of contracts in each category is displayed next to the category name (example: `Running (20)`). To view the list of contracts under any category, click on the category, and the list expands downward, showing all contracts beneath it." 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" +#: ../../content/applications/hr/payroll/contracts.rst:28 +msgid "The list of contracts in the *Payroll* application matches the list of contracts in the *Employees* application." 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." +msgid "Create new contracts" msgstr "" -#: ../../content/applications/hr/payroll/contracts.rst:-1 -msgid "New contract form to be filled in when creating a new contract." +#: ../../content/applications/hr/payroll/contracts.rst:36 +msgid "For an employee to be paid, an active contract is required. When a new contract is needed, click the :guilabel:`New` button on the :guilabel:`Contracts` dashboard. A contract form appears where the information can be entered." 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`." +msgid ":guilabel:`Contact Reference`: type in the name or title for the contract, such as `John Smith Contract`. This field is **required**." 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." +msgid ":guilabel:`Employee`: using the drop-down menu, select the employee that the contract applies to." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:48 +msgid ":guilabel:`Contract Start Date`: the date the contract starts. To choose a date, click the drop-down menu, navigate to the correct month and year with the :guilabel:`< > (arrow)` icons, then click on the desired date. This field is **required**." 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." +msgid ":guilabel:`Contract End Date`: if the contract has a specific end date, click the drop-down menu, navigate to the correct month and year with the :guilabel:`< > (arrow)` icons, then click on the desired date." 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`." +msgid ":guilabel:`Working Schedule`: select one of the working schedules from the drop-down menu. This field is **required**." msgstr "" -#: ../../content/applications/hr/payroll/contracts.rst:57 -msgid ":guilabel:`Working Schedule`: Select one of the working schedules from the drop-down menu." +#: ../../content/applications/hr/payroll/contracts.rst:58 +msgid "The :guilabel:`Working Schedule` drop-down menu displays all the working schedules for the selected company. To modify or add to this list, go to :menuselection:`Payroll app --> Configuration --> Working Schedules`. Click :guilabel:`New`, and create a new working schedule, or click on an existing working schedule and make edits." 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`." +#: ../../content/applications/hr/payroll/contracts.rst:63 +msgid ":guilabel:`Work Entry Source`: select how the :doc:`work entries ` are generated. This field is **required**. Click the radio button next to the desired selection. The options are:" +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:66 +msgid ":guilabel:`Working Schedule`: work entries are generated based on the selected :guilabel:`Working Schedule`." 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." +msgid ":guilabel:`Attendances`: work entries are generated based on the employee's check-in records in the *Attendances* application. (This requires the *Attendances* application)." msgstr "" #: ../../content/applications/hr/payroll/contracts.rst:70 -msgid ":guilabel:`Job Position`: The specific job position the contract applies to." +msgid ":guilabel:`Planning`: work entries are generated based on the planned schedule for the employee from the *Planning* application. (This requires the *Planning* application)." 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." +#: ../../content/applications/hr/payroll/contracts.rst:73 +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 :ref:`new salary structure type ` can be created, if needed." 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." +msgid ":guilabel:`Department`: select the department the contract applies to from the drop-down menu." 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." +#: ../../content/applications/hr/payroll/contracts.rst:77 +msgid ":guilabel:`Job Position`: select the specific job position the contract applies to from the drop-down menu." 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." +msgid "If the selected :guilabel:`Job Position` has a contract template linked to it with a specific :guilabel:`Salary Structure Type`, the :guilabel:`Salary Structure Type` changes to the one associated with that :guilabel:`Job Position`." 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." +#: ../../content/applications/hr/payroll/contracts.rst:85 +msgid ":guilabel:`Wage on Payroll`: enter the employee's monthly wage." msgstr "" -#: ../../content/applications/hr/payroll/contracts.rst:87 -msgid "Contract details" +#: ../../content/applications/hr/payroll/contracts.rst:86 +msgid ":guilabel:`Contract Type`: choose either :guilabel:`Permanent`, :guilabel:`Temporary`, :guilabel:`Seasonal`, :guilabel:`Full-Time`, or :guilabel:`Part-Time` from the drop-down menu." msgstr "" -#: ../../content/applications/hr/payroll/contracts.rst:89 +#: ../../content/applications/hr/payroll/contracts.rst:94 +msgid "New contract form to be filled in when creating a new contract, with required fields\n" +"outlined in red." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:94 +msgid "The general information section filled out, with the required fields highlighted in red." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:97 +msgid "Salary Information tab" +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:99 +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:102 +msgid "The following fields are universal and apply to all localizations:" +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:106 +msgid ":guilabel:`Schedule Pay`: select how often the employee is paid using the drop-down menu. Options are :guilabel:`Annually`, :guilabel:`Semi-annually`, :guilabel:`Quarterly`, :guilabel:`Bi-monthly`, :guilabel:`Monthly`, :guilabel:`Semi-monthly`, :guilabel:`Bi-weekly`, :guilabel:`Weekly`, or :guilabel:`Daily`." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:110 +msgid ":guilabel:`Wage`: enter the employee's gross wage. The metric for the :guilabel:`Wage` is based on what is selected for the :guilabel:`Schedule Pay`." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:114 +msgid "If :guilabel:`Annually` is selected for the :guilabel:`Schedule Pay`, then the :guilabel:`Wage` field appears in a `$0.00/year` format. If the :guilabel:`Schedule Pay` is set to :guilabel:`Bi-weekly`, then the :guilabel:`Wage` field appears in a `$0.00/two weeks` format." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:118 +msgid ":guilabel:`Yearly Cost (Real)`: this field automatically updates after the :guilabel:`Schedule Pay` and :guilabel:`Wage` fields are entered. This amount is the total yearly cost for the employer. This field can be modified. However, if this is modified, the :guilabel:`Wage` field updates, accordingly. Ensure both the :guilabel:`Wage` and :guilabel:`Yearly Cost (Real)` are correct if this field is modified." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:123 +msgid ":guilabel:`Monthly Cost (Real)`: this field automatically updates after the :guilabel:`Schedule Pay` and :guilabel:`Wage` fields are entered. This amount is the total monthly cost for the employer. This field **cannot** be modified, and is calculated based on the :guilabel:`Yearly Cost (Real)`." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:0 +msgid "Optional tabs for a new contract." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:133 +msgid "Contract Details tab" +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:135 msgid "The contract details section allows for the addition and editing of a contract, and the ability to send the contract to the employee for approval and signatures." msgstr "" -#: ../../content/applications/hr/payroll/contracts.rst:-1 +#: ../../content/applications/hr/payroll/contracts.rst:138 +msgid ":guilabel:`Contract Template`: select a pre-existing contract template from the drop-down menu. Contract templates are typically created through the configuration menu, and stored in the *Documents* application." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:145 +msgid ":guilabel:`HR Responsible`: select the person who is responsible for validating the contract from the drop-down menu. This field is required." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:147 +msgid ":guilabel:`New Contract Document Template`: select a contract from the drop-down menu to be modified for this new employee contract. These documents are stored in the *Sign* application." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:149 +msgid ":guilabel:`Contract Update Document Template`: select a contract from the drop-down menu, if the employee has an existing contract that requires updating. These documents are stored in the *Sign* application." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:154 +msgid "The :guilabel:`HR Responsible`, :guilabel:`New Contract Document Template`, and :guilabel:`Contract Update Document Template` fields are only visible if the *Sign* application is installed, along with the `hr_contract_salary` and `hr_contract_salary_payroll` :doc:`modules <../../general/apps_modules>`. The *Sign* application is where the contract templates are stored. This application is required for an employee to sign any contract." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:161 +msgid "Accounting section" +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:163 +msgid ":guilabel:`Analytic Account`: select the account the contract affects from the drop-down menu. It is recommended to check with the accounting department to ensure the correct account is selected." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:167 +msgid "Part Time section" +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:169 +msgid ":guilabel:`Part Time`: tick this box if the employee is working part-time. When active, additional fields appear:" +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:172 +msgid ":guilabel:`% (Percentage)`: enter the percent of time the employee works as compared to a full-time employee." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:174 +msgid ":guilabel:`Standard Calendar`: select the working hours that a typical full-time worker uses from the drop-down menu." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:176 +msgid ":guilabel:`Part Time Work Entry Type`: select the work entry type that generates the balance of a full-time working schedule." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:180 +msgid "If a full-time employee works 40 hours a week, and the employee works 20, enter `50` in the :guilabel:`% (Percentage)` field (50% of 40 hours = 20 hours). The employee generates twenty (20) hours of work entries under the work entry type `part-time`, and another twenty (20) hours of work entries under the work entry type `generic time off`, for a total of forty (40) hours worth of work entries." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:187 +msgid "Notes section" +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:189 +msgid ":guilabel:`Notes`: a text field where any notes for the employee contract are entered for future reference." +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." +#: ../../content/applications/hr/payroll/contracts.rst:197 +msgid "Personal Documents tab" 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." +#: ../../content/applications/hr/payroll/contracts.rst:199 +msgid "Once an :guilabel:`Employee` is selected in the :ref:`General Information section `, the :guilabel:`Personal Documents` tab appears." 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." +#: ../../content/applications/hr/payroll/contracts.rst:202 +msgid "If any documents are needed to keep on file, add them in the :guilabel:`Personal Documents` tab. Depending on what other applications are installed, and what kind of benefits are enabled (and offered) to the employee, the various options to add a file varies. The :guilabel:`Image` option always appears, and is available by default." 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." +#: ../../content/applications/hr/payroll/contracts.rst:207 +msgid "Click the :guilabel:`Upload your file` button next to the corresponding document, navigate to the file, then click :guilabel:`Open` to select the document and add it to the tab." msgstr "" -#: ../../content/applications/hr/payroll/contracts.rst:106 -msgid "Modifying a contract" +#: ../../content/applications/hr/payroll/contracts.rst:211 +msgid "Modifying contract templates" 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." +#: ../../content/applications/hr/payroll/contracts.rst:213 +msgid "Contracts templates can be modified at any point when changes are needed." 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." +#: ../../content/applications/hr/payroll/contracts.rst:215 +msgid "To modify a contract template, refer to the :ref:`contract templates ` section of the main payroll documentation." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:219 +msgid "Salary attachments" +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:221 +msgid "Any automatic deductions or allocations for an employee, such as child support payments and wage garnishments, are referred to as a *salary attachment*. Navigate to :menuselection:`Payroll app --> Contracts --> Salary Attachments` to view a list of all the currently configured salary attachments." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:225 +msgid "Each salary attachment appears with all its relevant details displayed. The :guilabel:`Status` for each attachment is color-coded in the far right column." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:228 +msgid "Currently running salary attachments have a :guilabel:`Status` of :guilabel:`Running`, and appear in green. Salary attachments that have been paid in-full, and are no longer active, have a :guilabel:`Status` of :guilabel:`Completed`, and appear in blue. Cancelled salary attachments have a :guilabel:`Status` of :guilabel:`Cancelled`, and appear in red." msgstr "" #: ../../content/applications/hr/payroll/contracts.rst:-1 -msgid "Edit the details for the contract." +msgid "A list view of all the salary attachments with their status displayed." msgstr "" -#: ../../content/applications/hr/payroll/contracts.rst:121 -msgid ":guilabel:`Tags`: Select any tags associated with the contract." +#: ../../content/applications/hr/payroll/contracts.rst:238 +msgid "New salary attachment" 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." +#: ../../content/applications/hr/payroll/contracts.rst:240 +msgid "To create a new salary attachment from the :guilabel:`Salary Attachment` page, click :guilabel:`New`, and a blank salary attachment form loads. Enter the following information on the form:" 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." +#: ../../content/applications/hr/payroll/contracts.rst:244 +msgid ":guilabel:`Employees`: add any employees the salary attachment applies to using the drop-down menu." 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." +#: ../../content/applications/hr/payroll/contracts.rst:248 +msgid "Multiple employees can be added, if the salary attachment details are identical. After all employees are added, a :guilabel:`Create Individual Attachments` button appears at the top of the form." msgstr "" -#: ../../content/applications/hr/payroll/contracts.rst:129 -msgid ":guilabel:`Who can Sign`: Select either :guilabel:`All Users` or :guilabel:`On Invitation`." +#: ../../content/applications/hr/payroll/contracts.rst:252 +msgid "After the form is completed, click the :guilabel:`Create Individual Attachments` button to create separate salary attachments for each of the employees listed in this field." msgstr "" -#: ../../content/applications/hr/payroll/contracts.rst:131 -msgid ":guilabel:`All Users`: Any user in the organization can sign the contract." +#: ../../content/applications/hr/payroll/contracts.rst:0 +msgid "The Create Individual Attachments button that appears after multiple employees are\n" +"added to the Employees field." msgstr "" -#: ../../content/applications/hr/payroll/contracts.rst:132 -msgid ":guilabel:`On Invitation`: Only users selected in this field can sign the contract." +#: ../../content/applications/hr/payroll/contracts.rst:260 +msgid "This is a time-saving tip, so that separate salary attachments do not need to be created individually. They can be created in a batch using this method." msgstr "" -#: ../../content/applications/hr/payroll/contracts.rst:134 -msgid ":guilabel:`Invited Users`: Select the person(s) that can sign the document." +#: ../../content/applications/hr/payroll/contracts.rst:263 +msgid ":guilabel:`Description`: enter a description for the specific type of salary attachment." 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." +#: ../../content/applications/hr/payroll/contracts.rst:264 +msgid ":guilabel:`Type`: select the :ref:`type of salary attachment ` from the drop-down menu. The options listed come from the salary attachment types configured in the configuration menu." 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." +#: ../../content/applications/hr/payroll/contracts.rst:267 +msgid ":guilabel:`Start Date`: enter the date the salary attachment begins. The first of the current month populates this field, by default. Click on the date, and a calendar appears. Navigate to the desired month and year, using the :guilabel:`< > (arrow)` icons, and click on the date to select it." msgstr "" -#: ../../content/applications/hr/payroll/contracts.rst:144 -msgid "Salary information" +#: ../../content/applications/hr/payroll/contracts.rst:271 +msgid ":guilabel:`Document`: if any documents are needed for the salary attachment, click the :guilabel:`Upload your file` button, and a file explorer appears. Navigate to the file, and click :guilabel:`Open` to select them, and attach them to the form." msgstr "" -#: ../../content/applications/hr/payroll/contracts.rst:-1 -msgid "Optional tabs for a new contract." +#: ../../content/applications/hr/payroll/contracts.rst:274 +msgid ":guilabel:`Monthly Amount`: enter the amount to be taken out of the paycheck each month for this salary attachment." 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." +#: ../../content/applications/hr/payroll/contracts.rst:276 +msgid ":guilabel:`Estimated End Date`: this field only appears after the :guilabel:`Monthly Amount` field is populated, and if the :guilabel:`Type` is **not** set to :guilabel:`Child Support`. This date is when the salary attachment is predicted to end, and is automatically calculated once both, the :guilabel:`Monthly Amount` and :guilabel:`Total Amount`, fields are populated. This is calculated based on how much is required to be paid, and how much is paid towards that amount each month. If either the :guilabel:`Monthly Amount` or :guilabel:`Total Amount` changes, this field automatically updates. It is **not** possible to modify this field." 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`." +#: ../../content/applications/hr/payroll/contracts.rst:283 +msgid ":guilabel:`Total Amount`: enter the total amount to be paid in this field. If :guilabel:`Child Support` is selected for the :guilabel:`Type`, this field does **not** appear." 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:" +#: ../../content/applications/hr/payroll/contracts.rst:291 +msgid "When the total amount has been paid for the salary attachment, navigate to the individual salary attachment, and click the :guilabel:`Mark as Completed` button at the top of the form. This changes the status to :guilabel:`Completed`, and the garnishments are no longer taken out of the employee's paychecks." 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." +#: ../../content/applications/hr/payroll/contracts.rst:297 +msgid "Offers" 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." +#: ../../content/applications/hr/payroll/contracts.rst:299 +msgid "Once a contract has been created or modified, the contract **must** be sent to the employee to be accepted and signed." msgstr "" -#: ../../content/applications/hr/payroll/contracts.rst:180 -msgid ":guilabel:`Child Support`: Any payments taken out specifically for child support." +#: ../../content/applications/hr/payroll/contracts.rst:303 +msgid "Send an offer" 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:" +#: ../../content/applications/hr/payroll/contracts.rst:305 +msgid "Open an individual contract by navigating to :menuselection:`Payroll app --> Contracts -> Contracts`, and click on a contract to open the contract form. Click on the :guilabel:`Generate Offer` button at the top of the page, and a :guilabel:`Generate Simulation Link` pop-up form appears." 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." +#: ../../content/applications/hr/payroll/contracts.rst:314 +msgid "The :guilabel:`Generate Simulation Link` pop-up form contains all the information pulled from the contract, including the :guilabel:`Contract Template`, :guilabel:`Job Position`, :guilabel:`Job Title`, :guilabel:`Department`, :guilabel:`Contract Start Date`, :guilabel:`Default Vehicle`, :guilabel:`Contract Type`, and :guilabel:`Yearly Cost`." msgstr "" -#: ../../content/applications/hr/payroll/contracts.rst:0 -msgid "Sends a link to the employee for the contract." +#: ../../content/applications/hr/payroll/contracts.rst:319 +msgid "At the bottom of the pop-up form is a :guilabel:`Link Expiration Date`. This is the timeframe that the contract offer is valid for. By default, this field is pre-populated with `30 days`, but it can be modified." 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." +#: ../../content/applications/hr/payroll/contracts.rst:323 +msgid "Click the :guilabel:`Send By Email` button, and a :guilabel:`Send Offer Email` template pop-up window appears. Make any modifications to the email, and attach any additional documents needed, then click :guilabel:`Send` to send the offer." 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." +#: ../../content/applications/hr/payroll/contracts.rst:-1 +msgid "The email template pop-up to send an offer." msgstr "" -#: ../../content/applications/hr/payroll/contracts.rst:0 -msgid "Request a signature for the contract via email." +#: ../../content/applications/hr/payroll/contracts.rst:332 +msgid "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: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." +#: ../../content/applications/hr/payroll/contracts.rst:336 +msgid "Accept an offer" +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:338 +msgid "Once the offer email is received, the offer can be accepted, and the contract can be signed." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:340 +msgid "In the offer email, click the :guilabel:`Configure your package` button, and the offer loads in a new tab. Enter the requested information on the form. Next, click the :guilabel:`Review Contract & Sign` button to begin the signing process." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:344 +msgid "Click the :guilabel:`CLICK TO START` button at the top-left of the contract. Follow the prompts to complete the signature request. The contract auto-populates with the information entered on the :guilabel:`Configure your package` page. When done, click the :guilabel:`Validate & Send Completed Document` button at the bottom of the contract." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:349 +msgid "After the document is signed by the (potential) employee, management signs the contract next. The manager's signature is completed directly in the *Sign* application." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:-1 +msgid "The contract offer, ready to sign with the Click to Start button highlighted." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:357 +msgid "Depending on the localization settings, there may be the option to customize the offer in the :guilabel:`Configure your package` tab." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:361 +msgid "View offers" +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:363 +msgid "To view the current offers, navigate to :menuselection:`Payroll app --> Contracts --> Offers`. This presents all offers in a list view, grouped by status, and displays the number of offers in each status category. The statuses are: :guilabel:`Fully Signed`, :guilabel:`Partially Signed`, :guilabel:`In Progress`, and :guilabel:`Expired`." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:368 +msgid "To view the offers with a specific status, click on the status to expand the list. If a specific status has no offers, the status is not visible in the list." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:-1 +msgid "The offers in a list view, grouped by status." msgstr "" #: ../../content/applications/hr/payroll/payslips.rst:3 @@ -4913,23 +6669,23 @@ msgstr "" msgid "If modifications to auto-populated fields are made, it is recommended to check with the accounting department to ensure every entry that affects the *Accounting* application is correct." msgstr "" -#: ../../content/applications/hr/payroll/payslips.rst:104 +#: ../../content/applications/hr/payroll/payslips.rst:106 msgid "Worked days & inputs tab" msgstr "" -#: ../../content/applications/hr/payroll/payslips.rst:106 +#: ../../content/applications/hr/payroll/payslips.rst:108 msgid ":guilabel:`Worked Days`: the entries under :guilabel:`Worked Days` (including the :guilabel:`Type`, :guilabel:`Description`, :guilabel:`Number of Days`, :guilabel:`Number of Hours`, and :guilabel:`Amount`) are automatically filled in, based on what was entered for the :guilabel:`Period`, :guilabel:`Contract`, and :guilabel:`Structure` fields of the payslip form." msgstr "" -#: ../../content/applications/hr/payroll/payslips.rst:110 +#: ../../content/applications/hr/payroll/payslips.rst:112 msgid ":guilabel:`Other Inputs`: additional inputs affecting the payslip can be entered in this section, such as deductions, reimbursements, and expenses." msgstr "" -#: ../../content/applications/hr/payroll/payslips.rst:113 +#: ../../content/applications/hr/payroll/payslips.rst:115 msgid "Click :guilabel:`Add a line` to create an entry in the :guilabel:`Other Inputs` section." msgstr "" -#: ../../content/applications/hr/payroll/payslips.rst:115 +#: ../../content/applications/hr/payroll/payslips.rst:117 msgid "Using the drop-down menu in the :guilabel:`Type` column, select a :guilabel:`Type` for the input. Next, enter a :guilabel:`Description`, if desired. Lastly, enter the amount in the :guilabel:`Count` field." msgstr "" @@ -4937,15 +6693,15 @@ msgstr "" msgid "The fields filled out in the worked days and inputs tab." msgstr "" -#: ../../content/applications/hr/payroll/payslips.rst:124 +#: ../../content/applications/hr/payroll/payslips.rst:126 msgid "Salary computation tab" msgstr "" -#: ../../content/applications/hr/payroll/payslips.rst:126 +#: ../../content/applications/hr/payroll/payslips.rst:128 msgid ":guilabel:`Salary Computation`: the :guilabel:`Salary Computation` tab is automatically filled in after the :guilabel:`Compute Sheet` button is clicked. Doing so displays the wages, deductions, taxes, etc. for the entry." msgstr "" -#: ../../content/applications/hr/payroll/payslips.rst:129 +#: ../../content/applications/hr/payroll/payslips.rst:131 msgid ":guilabel:`Has Negative Net To Report`: click the checkbox if the employee has a negative net amount for this payslip. This **only** appears if the employee's payslip has a negative balance." msgstr "" @@ -4953,43 +6709,43 @@ msgstr "" msgid "The fields filled out in the salary computation tab." msgstr "" -#: ../../content/applications/hr/payroll/payslips.rst:137 +#: ../../content/applications/hr/payroll/payslips.rst:139 msgid "Other info tab" msgstr "" -#: ../../content/applications/hr/payroll/payslips.rst:139 +#: ../../content/applications/hr/payroll/payslips.rst:141 msgid ":guilabel:`Payslip Name`: type in a name for the payslip in this field. The name should be short and descriptive, such as `(Employee Name) April 2023`. This field is **required**." msgstr "" -#: ../../content/applications/hr/payroll/payslips.rst:141 +#: ../../content/applications/hr/payroll/payslips.rst:143 msgid ":guilabel:`Company`: select the company the payslip applies to using the drop-down menu in this field. This field is **required**." msgstr "" -#: ../../content/applications/hr/payroll/payslips.rst:143 +#: ../../content/applications/hr/payroll/payslips.rst:145 msgid ":guilabel:`Close Date`: enter the date that the payment is made to the employee in this field." msgstr "" -#: ../../content/applications/hr/payroll/payslips.rst:145 +#: ../../content/applications/hr/payroll/payslips.rst:147 msgid "Click in the field to reveal a calendar pop-up window. Using the :guilabel:`< > (less-than/greater-than)` icons, navigate to the desired month and year." msgstr "" -#: ../../content/applications/hr/payroll/payslips.rst:148 +#: ../../content/applications/hr/payroll/payslips.rst:150 msgid "Then, click on the desired date to select it." msgstr "" -#: ../../content/applications/hr/payroll/payslips.rst:149 +#: ../../content/applications/hr/payroll/payslips.rst:151 msgid ":guilabel:`Date Account`: enter the date on which the payslip should be posted in this field." msgstr "" -#: ../../content/applications/hr/payroll/payslips.rst:150 +#: ../../content/applications/hr/payroll/payslips.rst:152 msgid ":guilabel:`Salary Journal`: this field auto-populates after selecting an existing :guilabel:`Employee`. This field **cannot** be edited, as it is linked to the *Accounting* application. This field is **required**." msgstr "" -#: ../../content/applications/hr/payroll/payslips.rst:153 +#: ../../content/applications/hr/payroll/payslips.rst:155 msgid ":guilabel:`Accounting Entry`: if applicable, this field is automatically populated once the payslip is confirmed. This field **cannot** be modified." msgstr "" -#: ../../content/applications/hr/payroll/payslips.rst:155 +#: ../../content/applications/hr/payroll/payslips.rst:157 msgid ":guilabel:`Add an Internal Note...`: any note or reference message for the new entry can be typed in this field." msgstr "" @@ -4997,35 +6753,35 @@ msgstr "" msgid "The fields filled out in the other info tab." msgstr "" -#: ../../content/applications/hr/payroll/payslips.rst:163 +#: ../../content/applications/hr/payroll/payslips.rst:165 msgid "Process the new payslip" msgstr "" -#: ../../content/applications/hr/payroll/payslips.rst:165 +#: ../../content/applications/hr/payroll/payslips.rst:167 msgid "When all the necessary information on the payslip is entered, click the :guilabel:`Compute Sheet` button. Upon doing so, all the information on the payslip is saved, and the :guilabel:`Salary Computation` tab auto-populates, based on the information on the employee's contract or attendance records." msgstr "" -#: ../../content/applications/hr/payroll/payslips.rst:170 +#: ../../content/applications/hr/payroll/payslips.rst:172 msgid "If any modifications need to be made, first click the :guilabel:`Cancel` button, then click the :guilabel:`Set to Draft` button. Make any desired changes, then click the :guilabel:`Compute Sheet` button once again, and the changes are reflected in the :guilabel:`Worked Days` and :guilabel:`Salary Computation` tabs." msgstr "" -#: ../../content/applications/hr/payroll/payslips.rst:175 +#: ../../content/applications/hr/payroll/payslips.rst:177 msgid "Once everything on the payslip form is correct, click the :guilabel:`Create Draft Entry` button to create the payslip." msgstr "" -#: ../../content/applications/hr/payroll/payslips.rst:178 +#: ../../content/applications/hr/payroll/payslips.rst:180 msgid "Then, a confirmation pop-up window appears, asking :guilabel:`Are you sure you want to proceed?`. Click :guilabel:`OK` to confirm." msgstr "" -#: ../../content/applications/hr/payroll/payslips.rst:181 +#: ../../content/applications/hr/payroll/payslips.rst:183 msgid "The chatter is automatically updated to show the email sent to the employee, along with a PDF copy of the payslip." msgstr "" -#: ../../content/applications/hr/payroll/payslips.rst:185 +#: ../../content/applications/hr/payroll/payslips.rst:187 msgid "The database may need to be refreshed for the payslip and email to appear." msgstr "" -#: ../../content/applications/hr/payroll/payslips.rst:187 +#: ../../content/applications/hr/payroll/payslips.rst:189 msgid "To print the payslip, click the :guilabel:`Print` button. To cancel the payslip, click the :guilabel:`Cancel` button." msgstr "" @@ -5033,11 +6789,11 @@ msgstr "" msgid "The new payslip is emailed to the employee and the email appears in the chatter." msgstr "" -#: ../../content/applications/hr/payroll/payslips.rst:194 +#: ../../content/applications/hr/payroll/payslips.rst:196 msgid "Next, the payment must be sent to the employee. To do this, click the :guilabel:`Register Payment` button. Doing so reveals a pop-up form, in which the desired :guilabel:`Bank Journal` that the payment should be made against must be selected from a drop-down menu. Then, click the :guilabel:`Confirm` button to confirm the journal, and return to the payslip." msgstr "" -#: ../../content/applications/hr/payroll/payslips.rst:200 +#: ../../content/applications/hr/payroll/payslips.rst:202 msgid "In order for a payslip to be paid, the employee *must* have a bank account entered in their contact information. If there is no bank information, a payslip cannot be paid, and an error appears when the :guilabel:`Make Payment` button is clicked. Banking information can be found in the :ref:`Private Information ` tab on the employee's card in the *Employees* app. Edit the employee card, and add banking information, if it is missing." msgstr "" @@ -5045,19 +6801,19 @@ msgstr "" msgid "Banking information can be entered in an employee's card." msgstr "" -#: ../../content/applications/hr/payroll/payslips.rst:210 +#: ../../content/applications/hr/payroll/payslips.rst:212 msgid "Odoo automatically checks bank account information. If there is an error with the employee's listed bank account, an error appears in a pop-up window, stating, *The employee bank account is untrusted.* If this error appears, update the employee's bank account information on their :ref:`Employee Form `." msgstr "" -#: ../../content/applications/hr/payroll/payslips.rst:215 +#: ../../content/applications/hr/payroll/payslips.rst:217 msgid "If a payment needs to be canceled or refunded, click the corresponding :guilabel:`Cancel` or :guilabel:`Refund` button, located at the top-left of the screen." msgstr "" -#: ../../content/applications/hr/payroll/payslips.rst:219 +#: ../../content/applications/hr/payroll/payslips.rst:221 msgid "Before processing payslips, it is best practice to check the *Warnings* section of the *Payroll* app dashboard. Here, all possible issues concerning payroll appear." msgstr "" -#: ../../content/applications/hr/payroll/payslips.rst:222 +#: ../../content/applications/hr/payroll/payslips.rst:224 msgid "To view the warnings, navigate to :menuselection:`Payroll app --> Dashboard`. The warnings appear in the top-left corner of the dashboard." msgstr "" @@ -5065,47 +6821,47 @@ msgstr "" msgid "The dashboard view of the Payroll app, with the warnings box highlighted." msgstr "" -#: ../../content/applications/hr/payroll/payslips.rst:229 +#: ../../content/applications/hr/payroll/payslips.rst:231 msgid "Warnings are grouped by type, such as `Employees Without Running Contracts` or `Employees Without Bank account Number`. Click on a warning to view all entries associated with that specific issue." msgstr "" -#: ../../content/applications/hr/payroll/payslips.rst:232 +#: ../../content/applications/hr/payroll/payslips.rst:234 msgid "If the warnings are not resolved, at any point in the payslip processing process, an error may occur. Errors appear in a pop-up window, and provide details for the error, and how to resolve them." msgstr "" -#: ../../content/applications/hr/payroll/payslips.rst:236 +#: ../../content/applications/hr/payroll/payslips.rst:238 msgid "Payslips **cannot** be completed if there are any warnings or issues associated with the payslip." msgstr "" -#: ../../content/applications/hr/payroll/payslips.rst:241 +#: ../../content/applications/hr/payroll/payslips.rst:243 msgid "All payslips" msgstr "" -#: ../../content/applications/hr/payroll/payslips.rst:243 +#: ../../content/applications/hr/payroll/payslips.rst:245 msgid "To view all payslips, regardless of status, go to :menuselection:`Payroll app --> Payslips --> All Payslips`. The :guilabel:`Employee Payslips` page loads, displaying all payslips, organized by batch, in a default nested list view." msgstr "" -#: ../../content/applications/hr/payroll/payslips.rst:247 +#: ../../content/applications/hr/payroll/payslips.rst:249 msgid "Click on the :guilabel:`▶ (right arrow)` next to an individual batch name to view all the payslips in that particular batch, along with all the payslip details." msgstr "" -#: ../../content/applications/hr/payroll/payslips.rst:250 +#: ../../content/applications/hr/payroll/payslips.rst:252 msgid "The number of payslips in the batch is written in parenthesis after the batch name. The :guilabel:`Status` for each individual payslip appears on the far-right side, indicating one of the following status options:" msgstr "" -#: ../../content/applications/hr/payroll/payslips.rst:254 +#: ../../content/applications/hr/payroll/payslips.rst:256 msgid ":guilabel:`Draft`: the payslip is created, and there is still time to make edits, since the amounts are not calculated." msgstr "" -#: ../../content/applications/hr/payroll/payslips.rst:256 +#: ../../content/applications/hr/payroll/payslips.rst:258 msgid ":guilabel:`Waiting`: the payslip has been calculated, and the salary details can be found in the *Salary Computation* tab." msgstr "" -#: ../../content/applications/hr/payroll/payslips.rst:258 +#: ../../content/applications/hr/payroll/payslips.rst:260 msgid ":guilabel:`Done`: the payslip is calculated and ready to be paid." msgstr "" -#: ../../content/applications/hr/payroll/payslips.rst:259 +#: ../../content/applications/hr/payroll/payslips.rst:261 msgid ":guilabel:`Paid`: the employee has been paid." msgstr "" @@ -5113,19 +6869,19 @@ msgstr "" msgid "View all payslips organized by batches. Click on the arrow to expand each batch." msgstr "" -#: ../../content/applications/hr/payroll/payslips.rst:265 +#: ../../content/applications/hr/payroll/payslips.rst:267 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:268 +#: ../../content/applications/hr/payroll/payslips.rst:270 msgid "A new payslip can be created from the :guilabel:`Employee Payslips` page, by clicking the :guilabel:`New` button in the upper-left corner. Doing so reveals a separate blank payslip form page. On that blank payslip form page, enter all the necessary information, as described in the :ref:`Create new payslips ` section." msgstr "" -#: ../../content/applications/hr/payroll/payslips.rst:273 +#: ../../content/applications/hr/payroll/payslips.rst:275 msgid "To print PDF versions of payslips from the *Payslips to Pay* or :guilabel:`Employee Payslips` pages, first select the desired payslips by clicking on the individual checkbox to the left of each payslip to be printed. Or, click the box to the left of the :guilabel:`Reference` column title, which selects all visible payslips on the page. Then, click the :guilabel:`Print` button to print the payslips." msgstr "" -#: ../../content/applications/hr/payroll/payslips.rst:279 +#: ../../content/applications/hr/payroll/payslips.rst:281 msgid "Payslips can also be exported to an Excel spreadsheet. To export **all** payslips, click on the :guilabel:`⚙️ (gear)` icon at the end of the words :guilabel:`Employee Payslips` in the top-left corner. This reveals a drop-down menu. Click :guilabel:`Export All` to export all payslips to a spreadsheet." msgstr "" @@ -5133,7 +6889,7 @@ msgstr "" msgid "Click on the Export All smart button to export all payslips to an Excel payslip." msgstr "" -#: ../../content/applications/hr/payroll/payslips.rst:288 +#: ../../content/applications/hr/payroll/payslips.rst:290 msgid "To export only select payslips, first select the payslips to be exported from the list. Then, click the checkbox to the left of each individual payslip to select it. As payslips are selected, a smart button appears in the top-center of the page, indicating the number of selected payslips. Then, click the :guilabel:`⚙️ (gear) Actions` icon in the top-center of the page, and click :guilabel:`Export`." msgstr "" @@ -5141,19 +6897,19 @@ msgstr "" msgid "The individual list of employee ayslips with three selected to be exported." msgstr "" -#: ../../content/applications/hr/payroll/payslips.rst:299 +#: ../../content/applications/hr/payroll/payslips.rst:301 msgid "Both *To Pay* and *All Payslips* display all the detailed information for each payslip." msgstr "" -#: ../../content/applications/hr/payroll/payslips.rst:302 +#: ../../content/applications/hr/payroll/payslips.rst:304 msgid "Batches" msgstr "" -#: ../../content/applications/hr/payroll/payslips.rst:304 +#: ../../content/applications/hr/payroll/payslips.rst:306 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:308 +#: ../../content/applications/hr/payroll/payslips.rst:310 msgid "Each batch displays the :guilabel:`Name`, :guilabel:`Date From` and :guilabel:`Date To` dates, its :guilabel:`Status`, the number of payslips in the batch (:guilabel:`Payslips Count`), and the :guilabel:`Company`." msgstr "" @@ -5161,23 +6917,23 @@ msgstr "" msgid "View displaying all batches created." msgstr "" -#: ../../content/applications/hr/payroll/payslips.rst:317 +#: ../../content/applications/hr/payroll/payslips.rst:319 msgid "Create a new batch" msgstr "" -#: ../../content/applications/hr/payroll/payslips.rst:319 +#: ../../content/applications/hr/payroll/payslips.rst:321 msgid "To create a new batch of payslips from the :guilabel:`Payslips Batches` page (:menuselection:`Payroll app --> Payslips --> Batches`), click the :guilabel:`New` button in the top-left corner. Doing so reveals a blank payslip batch form on a separate page." msgstr "" -#: ../../content/applications/hr/payroll/payslips.rst:323 +#: ../../content/applications/hr/payroll/payslips.rst:325 msgid "On the new payslip batch form, enter the :guilabel:`Batch Name`." msgstr "" -#: ../../content/applications/hr/payroll/payslips.rst:325 +#: ../../content/applications/hr/payroll/payslips.rst:327 msgid "Next, select the date range to which the batch applies. Click into one of the :guilabel:`Period` fields, and a calendar pop-up window appears. From this calendar pop-up window, navigate to the correct month, and click on the corresponding day for both the start and end dates of the batch." msgstr "" -#: ../../content/applications/hr/payroll/payslips.rst:329 +#: ../../content/applications/hr/payroll/payslips.rst:331 msgid "The current company populates the :guilabel:`Company` field. If operating in a multi-company environment, it is **not** possible to modify the :guilabel:`Company` from the form. The batch **must** be created while in the database for the desired company." msgstr "" @@ -5185,15 +6941,15 @@ msgstr "" msgid "Enter the details for the new batch." msgstr "" -#: ../../content/applications/hr/payroll/payslips.rst:340 +#: ../../content/applications/hr/payroll/payslips.rst:342 msgid "Process a batch" msgstr "" -#: ../../content/applications/hr/payroll/payslips.rst:342 +#: ../../content/applications/hr/payroll/payslips.rst:344 msgid "Click on an individual batch to view the details for that batch on a separate page. On this batch detail page, different options (buttons) appear at the top, depending on the status of the batch:" msgstr "" -#: ../../content/applications/hr/payroll/payslips.rst:345 +#: ../../content/applications/hr/payroll/payslips.rst:347 msgid ":guilabel:`New` status: batches without any payslips added to them have a status of :guilabel:`New`. The following button options appear for these batches:" msgstr "" @@ -5201,27 +6957,27 @@ msgstr "" msgid "A batch with a status of new, with the available buttons highlighted." msgstr "" -#: ../../content/applications/hr/payroll/payslips.rst:352 +#: ../../content/applications/hr/payroll/payslips.rst:354 msgid ":guilabel:`Add Payslips`: click the :guilabel:`Add Payslips` button to add payslips to the batch, and an :guilabel:`Add Payslips` pop-up window appears. Only payslips that can be added to the batch (payslips not currently part of a batch) appear on the list." msgstr "" -#: ../../content/applications/hr/payroll/payslips.rst:356 +#: ../../content/applications/hr/payroll/payslips.rst:358 msgid "Select the desired payslips by clicking the checkbox to the left of each payslip name, then click the :guilabel:`Select` button to add them to the batch. Once payslips are selected and added to the batch, the status changes to :guilabel:`Confirmed`." msgstr "" -#: ../../content/applications/hr/payroll/payslips.rst:360 +#: ../../content/applications/hr/payroll/payslips.rst:362 msgid ":guilabel:`Generate Payslips`: after payslips have been added to the batch, click the :guilabel:`Generate Payslips` button to process the payslips and create individual payslips in the database." msgstr "" -#: ../../content/applications/hr/payroll/payslips.rst:364 +#: ../../content/applications/hr/payroll/payslips.rst:366 msgid "A :guilabel:`Generate Payslips` pop-up window appears. If only a specific :guilabel:`Salary Structure` and/or specific :guilabel:`Department` is desired to make payslips for, select them from the corresponding drop-down menus. If no selections are made, then all payslips listed in the pop-up window are processed as usual." msgstr "" -#: ../../content/applications/hr/payroll/payslips.rst:369 +#: ../../content/applications/hr/payroll/payslips.rst:371 msgid "Click the :guilabel:`Generate` button to create the payslips. The :guilabel:`Generate Payslips` button changes to a :guilabel:`Create Draft Entry` button, and the status changes to :guilabel:`Confirmed`." msgstr "" -#: ../../content/applications/hr/payroll/payslips.rst:373 +#: ../../content/applications/hr/payroll/payslips.rst:375 msgid ":guilabel:`Confirmed` status: batches that have been created and have payslips in them, but the payslips have *not* been processed, have a status of :guilabel:`Confirmed`. The following two button options appear for these batches:" msgstr "" @@ -5229,16 +6985,16 @@ msgstr "" msgid "A batch with a status of confirmed, with the available buttons highlighted." msgstr "" -#: ../../content/applications/hr/payroll/payslips.rst:381 +#: ../../content/applications/hr/payroll/payslips.rst:383 msgid ":guilabel:`Create Draft Entry`: click the :guilabel:`Create Draft Entry` button to confirm the individual payslips (and the batch), and create a draft of the payslips. The batch now has a status of :guilabel:`Done`." msgstr "" -#: ../../content/applications/hr/payroll/payslips.rst:384 -#: ../../content/applications/hr/payroll/payslips.rst:406 +#: ../../content/applications/hr/payroll/payslips.rst:386 +#: ../../content/applications/hr/payroll/payslips.rst:408 msgid ":guilabel:`Set to Draft`: if at any point the batch needs to be reverted back to a status of :guilabel:`New`, click the :guilabel:`Set to Draft` button. This action does **not** remove any payslips that have already been added to the batch." msgstr "" -#: ../../content/applications/hr/payroll/payslips.rst:388 +#: ../../content/applications/hr/payroll/payslips.rst:390 msgid ":guilabel:`Done` status: batches with confirmed payslips in them have a status of :guilabel:`Done`. The following button options appear for these batches:" msgstr "" @@ -5246,23 +7002,23 @@ msgstr "" msgid "A batch with a status of done, with the available buttons highlighted." msgstr "" -#: ../../content/applications/hr/payroll/payslips.rst:395 +#: ../../content/applications/hr/payroll/payslips.rst:397 msgid ":guilabel:`Create Payment Report`: click the :guilabel:`Create Payment Report` button, and a :guilabel:`Select a bank journal` pop-up window appears. Select the correct bank journal from the drop-down menu." msgstr "" -#: ../../content/applications/hr/payroll/payslips.rst:399 +#: ../../content/applications/hr/payroll/payslips.rst:401 msgid "The batch name appears in the :guilabel:`File name` field, but this can be modified, if desired. Finally, click :guilabel:`Confirm` to process the payslips, and pay the employees." msgstr "" -#: ../../content/applications/hr/payroll/payslips.rst:401 +#: ../../content/applications/hr/payroll/payslips.rst:403 msgid ":guilabel:`Mark as paid`: after the payments have been created via the :guilabel:`Create Payment Report` button, the payslips need to be marked as paid in the database." msgstr "" -#: ../../content/applications/hr/payroll/payslips.rst:404 +#: ../../content/applications/hr/payroll/payslips.rst:406 msgid "Click the :guilabel:`Mark as paid` button, and the status of the batch changes to :guilabel:`Paid`." msgstr "" -#: ../../content/applications/hr/payroll/payslips.rst:410 +#: ../../content/applications/hr/payroll/payslips.rst:412 msgid ":guilabel:`Paid` status: batches that have been completed have a status of :guilabel:`Paid`. No other button options appear for this status." msgstr "" @@ -5270,31 +7026,31 @@ msgstr "" msgid "A batch with a status of paid, with the available buttons highlighted." msgstr "" -#: ../../content/applications/hr/payroll/payslips.rst:417 +#: ../../content/applications/hr/payroll/payslips.rst:419 msgid "On the batch detail page, the individual payslips in the batch are accessible, via the :guilabel:`Payslips` smart button, located above the batch information, in the center. Click the :guilabel:`Payslips` smart button to view a list of all the individual payslips." msgstr "" -#: ../../content/applications/hr/payroll/payslips.rst:421 +#: ../../content/applications/hr/payroll/payslips.rst:423 msgid "Use the breadcrumb menu to navigate back to the individual batch detail page, or back to the list of all batches." msgstr "" -#: ../../content/applications/hr/payroll/payslips.rst:425 +#: ../../content/applications/hr/payroll/payslips.rst:427 msgid "Generate warrant payslips" msgstr "" -#: ../../content/applications/hr/payroll/payslips.rst:427 +#: ../../content/applications/hr/payroll/payslips.rst:429 msgid "Commissions are paid to employees in Odoo using *warrant payslips*." msgstr "" -#: ../../content/applications/hr/payroll/payslips.rst:429 +#: ../../content/applications/hr/payroll/payslips.rst:431 msgid "Warrant payslips can be generated directly from the :guilabel:`Payslips Batches` page (:menuselection:`Payroll app --> Payslips --> Batches`)." msgstr "" -#: ../../content/applications/hr/payroll/payslips.rst:432 +#: ../../content/applications/hr/payroll/payslips.rst:434 msgid "First, select the desired batches by clicking the box to the left of each batch for which commission payslips should be created. Next, click the :guilabel:`Generate Warrant Payslips` button at the top of the page." msgstr "" -#: ../../content/applications/hr/payroll/payslips.rst:436 +#: ../../content/applications/hr/payroll/payslips.rst:438 msgid "Doing so reveals a :guilabel:`Generate Warrant Payslips` pop-up window, in which the necessary information **must** be filled out." msgstr "" @@ -5302,35 +7058,35 @@ msgstr "" msgid "Enter the commission details." msgstr "" -#: ../../content/applications/hr/payroll/payslips.rst:443 +#: ../../content/applications/hr/payroll/payslips.rst:445 msgid "In this pop-up window, click on the drop-down menus, located beside the :guilabel:`Period` field, to reveal calendar pop-up windows. On these calendar pop-up windows, select the desired period for which the payslips are being generated. Using the :guilabel:`< (left)` and :guilabel:`> (right)` arrow icons, navigate to the correct month, and click on the date to select it." msgstr "" -#: ../../content/applications/hr/payroll/payslips.rst:448 +#: ../../content/applications/hr/payroll/payslips.rst:450 msgid "In the :guilabel:`Department` field, select the desired department from the drop-down menu." msgstr "" -#: ../../content/applications/hr/payroll/payslips.rst:450 +#: ../../content/applications/hr/payroll/payslips.rst:452 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:453 +#: ../../content/applications/hr/payroll/payslips.rst:455 msgid "Under the :guilabel:`Employee` section, enter the :guilabel:`Commission Amount` for each employee in the far-right column. To remove an employee, click the :guilabel:`🗑️ (trash)` icon to remove the line." msgstr "" -#: ../../content/applications/hr/payroll/payslips.rst:457 +#: ../../content/applications/hr/payroll/payslips.rst:459 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:460 +#: ../../content/applications/hr/payroll/payslips.rst:462 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:463 +#: ../../content/applications/hr/payroll/payslips.rst:465 msgid "Once all the commissions are properly entered, click the :guilabel:`Generate Payslips` button to create the warrant payslips in a batch." msgstr "" -#: ../../content/applications/hr/payroll/payslips.rst:466 +#: ../../content/applications/hr/payroll/payslips.rst:468 msgid ":ref:`Process the batch ` in the same way as a typical batch to complete the payment process." msgstr "" @@ -6068,7 +7824,6 @@ msgid ":ref:`Configure work entries `" msgstr "" #: ../../content/applications/hr/recruitment.rst:6 -#: ../../content/applications/hr/recruitment/new_job.rst:51 msgid "Recruitment" msgstr "" @@ -6878,46 +8633,54 @@ msgid "Fill out the rest of the form. For detailed information on the fields, re 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." +msgid "In Odoo *Recruitment*, all job positions are shown on the default dashboard in the *Recruitment* app. This includes positions that are being actively recruited for, as well as inactive positions." 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." +#: ../../content/applications/hr/recruitment/new_job.rst:8 +msgid "Each job position is shown in an individual Kanban card. If the job position is active, and candidates can apply, a :guilabel:`Published` banner appears in the top-right corner of the card." msgstr "" -#: ../../content/applications/hr/recruitment/new_job.rst:13 +#: ../../content/applications/hr/recruitment/new_job.rst:11 msgid "View submitted applications by clicking anywhere on a job position card." msgstr "" #: ../../content/applications/hr/recruitment/new_job.rst:-1 -msgid "Main dashboard view of Recruitment showing all job positions." +msgid "Main dashboard view of Recruitment app showing all job positions." msgstr "" -#: ../../content/applications/hr/recruitment/new_job.rst:20 +#: ../../content/applications/hr/recruitment/new_job.rst:18 msgid "Create a new job position" msgstr "" -#: ../../content/applications/hr/recruitment/new_job.rst:22 -msgid "Create a new job position from the main Recruitment dashboard by clicking the :guilabel:`New` button in the top-left corner." +#: ../../content/applications/hr/recruitment/new_job.rst:20 +msgid "To create a new job position from the main dashboard in the *Recruitment* app, click the :guilabel:`New` button in the top-left corner, and a :guilabel:`Create a Job Position` modal appears." msgstr "" -#: ../../content/applications/hr/recruitment/new_job.rst:25 -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." +#: ../../content/applications/hr/recruitment/new_job.rst:24 +msgid "First, enter the name of the :guilabel:`Job Position` (such as `Sales Manager`, `Mechanical Engineer`, etc.) in the field." +msgstr "" + +#: ../../content/applications/hr/recruitment/new_job.rst:27 +msgid "Next, enter an :guilabel:`Application email` by typing in the first half of the email address in the first field, then select the second half of the email using the drop-down menu in the second field. Applicants can send a resumé to this specific email address, and Odoo creates an application for them automatically." +msgstr "" + +#: ../../content/applications/hr/recruitment/new_job.rst:32 +msgid "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:33 -msgid "Once the job position has been created, it will appear as a card in the kanban view on the main :guilabel:`Recruitment` dashboard." +#: ../../content/applications/hr/recruitment/new_job.rst:39 +msgid "Once the job position has been created, it appears as a card in the Kanban view on the main *Recruitment* app dashboard." msgstr "" -#: ../../content/applications/hr/recruitment/new_job.rst:37 +#: ../../content/applications/hr/recruitment/new_job.rst:43 msgid "Edit a new job position" msgstr "" -#: ../../content/applications/hr/recruitment/new_job.rst:39 +#: ../../content/applications/hr/recruitment/new_job.rst:45 msgid "After 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:`Configuration` to edit the details." msgstr "" @@ -6925,485 +8688,120 @@ msgstr "" msgid "Edit the job position card." msgstr "" -#: ../../content/applications/hr/recruitment/new_job.rst:47 -msgid "Enter the job description in the :guilabel:`Job Summary` tab. This information is what is visible to potential applicants when searching for available jobs." -msgstr "" - #: ../../content/applications/hr/recruitment/new_job.rst:53 -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." +msgid "All the basic information about the job position is listed under the :guilabel:`Recruitment` tab." msgstr "" -#: ../../content/applications/hr/recruitment/new_job.rst:57 -msgid "The fields can be filled out as follows:" +#: ../../content/applications/hr/recruitment/new_job.rst:55 +msgid "None of the fields are required, but it is important to configure and populate the :guilabel:`Department`, :guilabel:`Location`, :guilabel:`Employment Type`, and :guilabel:`Job Summary` fields, as they are all visible to prospective applicants on the website." msgstr "" #: ../../content/applications/hr/recruitment/new_job.rst:59 -msgid ":guilabel:`Department`: select the relevant department for the job position." -msgstr "" - -#: ../../content/applications/hr/recruitment/new_job.rst:60 -msgid ":guilabel:`Job Location`: select the physical address for the job." +msgid "The fields can be filled out as follows:" msgstr "" #: ../../content/applications/hr/recruitment/new_job.rst:61 -msgid ":guilabel:`Employment Type`: select what type of position the job is, such as :guilabel:`Full-Time`, :guilabel:`Part-Time`, etc." +msgid ":guilabel:`Department`: select the relevant department for the job position. This is visible on the website." msgstr "" #: ../../content/applications/hr/recruitment/new_job.rst:63 -msgid ":guilabel:`Company`: select the company the job is for." -msgstr "" - -#: ../../content/applications/hr/recruitment/new_job.rst:64 -msgid ":guilabel:`Target`: enter the number of employees to be hired for this position." +msgid ":guilabel:`Job Location`: select the physical address for the job. If the job position is remote, leave this field blank. This is visible on the website." msgstr "" #: ../../content/applications/hr/recruitment/new_job.rst:65 -msgid ":guilabel:`Is Published`: activate this option to publish the job online." -msgstr "" - -#: ../../content/applications/hr/recruitment/new_job.rst:66 -msgid ":guilabel:`Website`: select the website where the job will be published." +msgid ":guilabel:`Email Alias`: enter an email address to which applicants can send a resumé. Once emailed, Odoo automatically creates an application for them." msgstr "" #: ../../content/applications/hr/recruitment/new_job.rst:67 -msgid ":guilabel:`Recruiter`: select the person who will be doing the recruiting for this role." +msgid ":guilabel:`Employment Type`: select what type of position the job is, using the drop-down menu. The default options are :guilabel:`Permanent`, :guilabel:`Temporary`, :guilabel:`Seasonal`, :guilabel:`Interim`, :guilabel:`Full-Time`, and :guilabel:`Part-Time`. This is visible on the website." msgstr "" -#: ../../content/applications/hr/recruitment/new_job.rst:68 -msgid ":guilabel:`Interviewers`: select who should perform the interview(s). Multiple people can be selected." +#: ../../content/applications/hr/recruitment/new_job.rst:71 +msgid ":guilabel:`Company`: select the company the job is for. This field only appears if using a multi-company database." msgstr "" -#: ../../content/applications/hr/recruitment/new_job.rst:70 -msgid ":guilabel:`Interview Form`: select an :ref:`Interview form ` that applicants will fill out prior to their interview." -msgstr "" - -#: ../../content/applications/hr/recruitment/new_job.rst:72 -msgid ":guilabel:`Contract Template`: select a contract template that will be used when offering the job to a candidate." +#: ../../content/applications/hr/recruitment/new_job.rst:73 +msgid ":guilabel:`Target`: enter the number of employees to be hired for this position." msgstr "" #: ../../content/applications/hr/recruitment/new_job.rst:74 -msgid ":guilabel:`Process Details` section: this section contains information that is displayed online for the job position. This informs the applicants of the timeline and steps for the recruitment process, so they know when to expect a reply." +msgid ":guilabel:`Is Published`: activate this option to publish the job online." msgstr "" -#: ../../content/applications/hr/recruitment/new_job.rst:78 -msgid ":guilabel:`Time to Answer`: enter the number of days before the applicant is contacted." +#: ../../content/applications/hr/recruitment/new_job.rst:75 +msgid ":guilabel:`Website`: select the website the job is published on." +msgstr "" + +#: ../../content/applications/hr/recruitment/new_job.rst:76 +msgid ":guilabel:`Recruiter`: select the person responsible for recruiting this role." +msgstr "" + +#: ../../content/applications/hr/recruitment/new_job.rst:77 +msgid ":guilabel:`Interviewers`: select who should perform the interviews. Multiple people can be selected." msgstr "" #: ../../content/applications/hr/recruitment/new_job.rst:79 -msgid ":guilabel:`Process`: enter the various stages the candidate will go through during the recruitment process." +msgid ":guilabel:`Interview Form`: select an :ref:`Interview form ` that applicants fill out prior to their interview." msgstr "" #: ../../content/applications/hr/recruitment/new_job.rst:81 +msgid ":guilabel:`Contract Template`: select a contract template to be used when offering the job to a candidate." +msgstr "" + +#: ../../content/applications/hr/recruitment/new_job.rst:83 +msgid ":guilabel:`Process Details` section: this section contains information that is displayed online for the job position. This informs the applicants of the timeline and steps for the recruitment process, so they know when to expect a reply." +msgstr "" + +#: ../../content/applications/hr/recruitment/new_job.rst:87 +msgid ":guilabel:`Time to Answer`: enter the number of days before the applicant is contacted." +msgstr "" + +#: ../../content/applications/hr/recruitment/new_job.rst:88 +msgid ":guilabel:`Process`: enter the various stages the candidate goes through during the recruitment process." +msgstr "" + +#: ../../content/applications/hr/recruitment/new_job.rst:90 msgid ":guilabel:`Days to get an Offer`: enter the number of days before the applicant should expect an offer after the recruitment process has ended." msgstr "" -#: ../../content/applications/hr/recruitment/new_job.rst:85 +#: ../../content/applications/hr/recruitment/new_job.rst:94 msgid "The :guilabel:`Process Details` section is a text field. All answers are typed in rather than selected from a drop-down menu. The text is displayed on the website exactly as it appears in this tab." msgstr "" +#: ../../content/applications/hr/recruitment/new_job.rst:98 +msgid "Finally, enter the job description in the :guilabel:`Job Summary` tab." +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:96 +#: ../../content/applications/hr/recruitment/new_job.rst:107 msgid "Create interview form" msgstr "" -#: ../../content/applications/hr/recruitment/new_job.rst:98 +#: ../../content/applications/hr/recruitment/new_job.rst:109 msgid "An *Interview Form* is used to determine if a candidate is a good fit for a job position. Interview forms can be as specific or general as desired, and can take the form of a certification, an exam, or a general questionnaire. Interview forms are determined by the recruitment team." msgstr "" -#: ../../content/applications/hr/recruitment/new_job.rst:102 -msgid "All interview forms must be created, there are no pre-configured forms in Odoo. To create an interview form, start from the recruitment tab of the :guilabel:`Job Position` form. In the :guilabel:`Interview Form` field, enter a name for the new interview form. As the name is typed, several options populate beneath the entry, :guilabel:`Create (interview form name)`, :guilabel:`View all`, and :guilabel:`Create and edit...`. Click :guilabel:`Create and edit...`. and a :guilabel:`Create Interview Form` pop-up window appears." -msgstr "" - -#: ../../content/applications/hr/recruitment/new_job.rst:110 -msgid "The option :guilabel:`View all` only appears if there are any interview forms already created. If no interview forms exist, the only options available are :guilabel:`Create (interview form name)`, and :guilabel:`Create and edit...`." -msgstr "" - -#: ../../content/applications/hr/recruitment/new_job.rst:114 -msgid "First, enter a name for the form in the :guilabel:`Name` field. This should be indicative of when the form should be used. For example, is the form specific to a job position, or is it a general form that can be used for all recruitment scenarios?" +#: ../../content/applications/hr/recruitment/new_job.rst:113 +msgid "Before creating an interview form, ensure the proper settings are enabled. Navigate to :menuselection:`Recruitment app --> Configuration --> Settings`, and under the :guilabel:`Recruitment Process` section, ensure the :guilabel:`Send Interview Survey` option is enabled." msgstr "" #: ../../content/applications/hr/recruitment/new_job.rst:118 -msgid "Next, select what kind of interview form is being created. The default is :guilabel:`Custom`, which is pre-selected. The various options are :guilabel:`Survey`, :guilabel:`Live session`, :guilabel:`Assessment`, :guilabel:`Custom`, and :guilabel:`Appraisal`." -msgstr "" - -#: ../../content/applications/hr/recruitment/new_job.rst:122 -msgid "Then select the person responsible for the form from the drop-down menu for the :guilabel:`Responsible` field." -msgstr "" - -#: ../../content/applications/hr/recruitment/new_job.rst:125 -msgid "If desired, an image can be added to the interview form. Mouse over the camera icon on the far right and a :guilabel:`✏️ (pencil)` icon appears. Click the :guilabel:`✏️ (pencil)` icon and a file explorer window appears. Navigate to the desired image file, then click :guilabel:`Open` to select it." +msgid "Since there are no pre-configured forms in Odoo, all interview forms must be created. To create an interview form, start from the :guilabel:`Recruitment` tab of the :guilabel:`Job Position` form. In the :guilabel:`Interview Form` field, enter a name for the new interview form. As the name is typed, several options populate beneath the entry: :guilabel:`Create (interview form name)`, :guilabel:`Search More...`, and :guilabel:`Create and edit...`. Click :guilabel:`Create and edit...` and a :guilabel:`Create Interview Form` modal appears." msgstr "" #: ../../content/applications/hr/recruitment/new_job.rst:-1 -msgid "The top portion of the new interview form with everything filled out and selected." +msgid "The blank interview form modal." msgstr "" -#: ../../content/applications/hr/recruitment/new_job.rst:135 -#: ../../content/applications/hr/recruitment/new_job.rst:351 -msgid "Questions" +#: ../../content/applications/hr/recruitment/new_job.rst:130 +msgid "The option :guilabel:`Search More...` only appears if there are any interview forms already created. If no interview forms exist, the only options available are :guilabel:`Create (interview form name)`, and :guilabel:`Create and edit...`." msgstr "" -#: ../../content/applications/hr/recruitment/new_job.rst:137 -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:141 -msgid "Next, click :guilabel:`Add a question` to add a question to the section. A :guilabel:`Create Sections and Questions` pop-up window appears where the question details are entered. Type out the question in the top line." -msgstr "" - -#: ../../content/applications/hr/recruitment/new_job.rst:145 -msgid "There are several :guilabel:`Question Types` to choose from:" -msgstr "" - -#: ../../content/applications/hr/recruitment/new_job.rst:147 -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:149 -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:151 -msgid ":guilabel:`Multiple Lines Text Box`: allows the applicant to enter several lines of text" -msgstr "" - -#: ../../content/applications/hr/recruitment/new_job.rst:152 -msgid ":guilabel:`Single Line Text Box`: limits the applicant to only a single line of text" -msgstr "" - -#: ../../content/applications/hr/recruitment/new_job.rst:153 -msgid ":guilabel:`Numerical Value`: only allows a number to be entered" -msgstr "" - -#: ../../content/applications/hr/recruitment/new_job.rst:154 -msgid ":guilabel:`Date`: a calendar module is presented to select a date" -msgstr "" - -#: ../../content/applications/hr/recruitment/new_job.rst:155 -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:156 -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:159 -msgid "After selecting a question type, a sample question appears in gray. This represents how the question 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:166 -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:169 -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:176 -#: ../../content/applications/hr/recruitment/new_job.rst:269 -msgid "Answers" -msgstr "" - -#: ../../content/applications/hr/recruitment/new_job.rst:178 -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 question type is selected, the :guilabel:`Answers` tab remains hidden from view." -msgstr "" - -#: ../../content/applications/hr/recruitment/new_job.rst:185 -msgid "Multiple choice" -msgstr "" - -#: ../../content/applications/hr/recruitment/new_job.rst:187 -msgid "For both the :guilabel:`Multiple choice: only one answer` and :guilabel:`Multiple choice: multiple answers allowed` question type, the answers are populated in the same way." -msgstr "" - -#: ../../content/applications/hr/recruitment/new_job.rst:190 -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:194 -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 image file, select it, then click :guilabel:`Open` to select it." -msgstr "" - -#: ../../content/applications/hr/recruitment/new_job.rst:199 -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 six small squares 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:204 -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:211 -msgid "Single Line Text Box" -msgstr "" - -#: ../../content/applications/hr/recruitment/new_job.rst:213 -msgid "If the :guilabel:`Single Line Text Box` question type is selected, only two checkboxes appear in the :guilabel:`Answers` tab:" -msgstr "" - -#: ../../content/applications/hr/recruitment/new_job.rst:216 -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:219 -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:223 -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:0 -msgid "The three possible checkboxes that can appear if a single line of text is selected\n" -"for the question type." -msgstr "" - -#: ../../content/applications/hr/recruitment/new_job.rst:231 -msgid "Matrix" -msgstr "" - -#: ../../content/applications/hr/recruitment/new_job.rst:233 -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:238 -msgid "For a :guilabel:`Matrix` 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:242 -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:251 -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:255 -#: ../../content/applications/hr/recruitment/new_job.rst:440 -msgid "Description" -msgstr "" - -#: ../../content/applications/hr/recruitment/new_job.rst:257 -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:261 -#: ../../content/applications/hr/recruitment/new_job.rst:345 -msgid "Options" -msgstr "" - -#: ../../content/applications/hr/recruitment/new_job.rst:263 -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:271 -msgid ":guilabel:`Multiple choice: only one answer` and :guilabel:`Multiple choice: multiple answers allowed`: a :guilabel:`Show Comments Field` option appears. Activate the option to allow the applicant to answer the question by typing in an answer (or comment). A :guilabel:`Comment Message` and :guilabel:`Comment is an answer` field appear if activated. Enter the text to appear in the :guilabel:`Comment Message` field. This should be helpful to the applicant, such as `If other, please specify`. Last, if the comment should be logged as the applicant's answer, activate the box." -msgstr "" - -#: ../../content/applications/hr/recruitment/new_job.rst:278 -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:280 -msgid ":guilabel:`Single Line Text Box` and :guilabel:`Numerical Value`: a :guilabel:`Validate entry` option appears. Activate this option if what the applicant enters must be a numerical value, *and* needs to be verified. The answer can *only* be verified if it is a numerical entry. When activated, several other options appear. Enter the values for the :guilabel:`Min/Max Limits` in the two fields. 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:287 -msgid ":guilabel:`Date` and :guilabel:`Datetime`: a :guilabel:`Validate entry` option appears. Activate this option if the applicant's answer needs to be verified. When activated, several other options appear. Enter the date ranges for the :guilabel:`Min/Max Limits` in the two fields. Click on a field, either the :guilabel:`minimum` or :guilabel:`maximum`, and a calendar appears. Select the dates for the corresponding fields. Next, enter the text that appears when the answer given does not fit within the designated minimum and maximum dates. 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:295 -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. 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` and :guilabel:`Comment is an answer` field appear. Enter the text to appear in the :guilabel:`Comment Message` field. This should be an instruction helpful to the applicant, such as `If other, please specify`. Last, if the comment should be logged as the applicant's answer, activate the box." -msgstr "" - -#: ../../content/applications/hr/recruitment/new_job.rst:304 -msgid "Constraints" -msgstr "" - -#: ../../content/applications/hr/recruitment/new_job.rst:306 -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 (*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:313 -msgid "Layout" -msgstr "" - -#: ../../content/applications/hr/recruitment/new_job.rst:315 -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:322 -msgid "To further illustrate a triggering question, the following is an example that is applicable to recruitment. The question, `Do you have experience with managing a sales team?` 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 prior experience managing a sales team?`." -msgstr "" - -#: ../../content/applications/hr/recruitment/new_job.rst:328 -msgid "To properly configure this example, activate the :guilabel:`Conditional Display` option. Then, select `Do you have experience with managing a sales team?` 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:338 -msgid "Live Sessions" -msgstr "" - -#: ../../content/applications/hr/recruitment/new_job.rst:340 -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:347 -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:353 -msgid ":guilabel:`Pagination`: choose how the questions should be displayed." -msgstr "" - -#: ../../content/applications/hr/recruitment/new_job.rst:355 -msgid ":guilabel:`One page per question`: display a single question on each page." -msgstr "" - -#: ../../content/applications/hr/recruitment/new_job.rst:356 -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:358 -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:362 -msgid ":guilabel:`Display Progress as`: choose how to display the percentage of questions remaining to answer. This option only appears if either :guilabel:`One page per question` or :guilabel:`One page per section` is selected for :guilabel:`Pagination`." -msgstr "" - -#: ../../content/applications/hr/recruitment/new_job.rst:366 -msgid ":guilabel:`Percentage left`: display the remaining amount in a percentage (%)." -msgstr "" - -#: ../../content/applications/hr/recruitment/new_job.rst:367 -msgid ":guilabel:`Number`: display the remaining amount in a numerical value." -msgstr "" - -#: ../../content/applications/hr/recruitment/new_job.rst:370 -msgid ":guilabel:`Question Selection`: choose which questions are presented." -msgstr "" - -#: ../../content/applications/hr/recruitment/new_job.rst:372 -msgid ":guilabel:`All questions`: display the entire form, with all questions form all sections." -msgstr "" - -#: ../../content/applications/hr/recruitment/new_job.rst:373 -msgid ":guilabel:`Randomized per Section`: display only a random selection of questions from each section." -msgstr "" - -#: ../../content/applications/hr/recruitment/new_job.rst:377 -msgid ":guilabel:`Back Button`: activate this option if the applicant is able to click a back button to go back to previous questions." -msgstr "" - -#: ../../content/applications/hr/recruitment/new_job.rst:381 -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:386 -msgid "Time & Scoring" -msgstr "" - -#: ../../content/applications/hr/recruitment/new_job.rst:388 -msgid ":guilabel:`Survey Time Limit`: activate this option 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:391 -msgid ":guilabel:`Scoring`: choose how the questions should be scored." -msgstr "" - -#: ../../content/applications/hr/recruitment/new_job.rst:393 -msgid ":guilabel:`No scoring`: select this option to not score the form." -msgstr "" - -#: ../../content/applications/hr/recruitment/new_job.rst:394 -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:396 -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:399 -msgid ":guilabel:`Required Score (%)`: this option appears if one of the scoring options was selected. 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:403 -msgid ":guilabel:`Is a Certification`: activate this option if the form is a certification exam. When activated, 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:407 -msgid ":guilabel:`Certified Email Template`: if the :guilabel:`Is a Certification` box is activated, 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:413 -msgid "Participants" -msgstr "" - -#: ../../content/applications/hr/recruitment/new_job.rst:415 -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:417 -msgid ":guilabel:`Require Login`: activate this option 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:419 -msgid ":guilabel:`Limit Attempts`: if there is a limit to how many times the exam can be taken, activate this box, then enter the maximum attempt number in the field next to it." -msgstr "" - -#: ../../content/applications/hr/recruitment/new_job.rst:423 -msgid "Live Session" -msgstr "" - -#: ../../content/applications/hr/recruitment/new_job.rst:425 -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:427 -msgid ":guilabel:`Session Link`: the link appears in a box next to the :guilabel:`Session Link` option. Click the :guilabel:`Copy` button to copy the link." -msgstr "" - -#: ../../content/applications/hr/recruitment/new_job.rst:429 -msgid ":guilabel:`Reward quick answers`: if the exam is to be taken live, activate this option to award more points to participants who answer quickly." -msgstr "" - -#: ../../content/applications/hr/recruitment/new_job.rst:432 -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:442 -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:446 -msgid "End Message" -msgstr "" - -#: ../../content/applications/hr/recruitment/new_job.rst:448 -msgid "After the survey is complete, the message entered in this tab is displayed for the applicant." +#: ../../content/applications/hr/recruitment/new_job.rst:134 +msgid "Proceed to fill out the modal interview form as a typical survey. For specific directions on how to create a survey, refer to the :doc:`survey essentials <../../marketing/surveys/create>` document, which provides step-by-step instructions on how to create and configure a survey." msgstr "" #: ../../content/applications/hr/referrals.rst:3 @@ -8092,10 +9490,6 @@ msgstr "" 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 "" @@ -8181,869 +9575,1102 @@ 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." +msgid "Odoo's *Time Off* application serves as a centralized hub for all time-off-related information. This application manages 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." +#: ../../content/applications/hr/time_off.rst:8 +msgid "Users can :ref:`request time off `, and see an overview of their requests and time off balances. Managers can :ref:`allocate time off ` to individuals, teams, or the whole company, and :ref:`approve time off requests `." msgstr "" -#: ../../content/applications/hr/time_off.rst:16 +#: ../../content/applications/hr/time_off.rst:12 +msgid "Detailed :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:17 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 +#: ../../content/applications/hr/time_off.rst:20 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." +#: ../../content/applications/hr/time_off.rst:23 +msgid "To better understand how access rights affect the *Time Off* application, refer to the :doc:`employees/new_employee` document, specifically the section about configuring the work information tab." msgstr "" -#: ../../content/applications/hr/time_off.rst:29 +#: ../../content/applications/hr/time_off.rst:30 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 +#: ../../content/applications/hr/time_off.rst:37 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." +#: ../../content/applications/hr/time_off.rst:39 +msgid "To view the currently configured time off types, navigate to :menuselection:`Time Off app --> Configuration --> Time Off Types`. The time off types are presented in a list view." msgstr "" -#: ../../content/applications/hr/time_off.rst:45 -msgid "Create time off type" +#: ../../content/applications/hr/time_off.rst:42 +msgid "The *Time Off* application comes with four pre-configured time off types: :guilabel:`Paid Time Off`, :guilabel:`Sick Time Off`, :guilabel:`Unpaid`, and :guilabel:`Compensatory Days`. These can be modified to suit business needs or used as-is." 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." +msgid "Create time off type" 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:" +#: ../../content/applications/hr/time_off.rst:49 +msgid "To create a new time off type, navigate to :menuselection:`Time Off app --> Configuration --> Time Off Types`. From here, click the :guilabel:`New` button to reveal a blank time off type form." msgstr "" -#: ../../content/applications/hr/time_off.rst:54 -msgid "Time off requests section" +#: ../../content/applications/hr/time_off.rst:52 +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:56 -msgid ":guilabel:`Approval`: select what specific kind of approval is required for the time off type. The options are:" +msgid "The only **required** fields on the time off type form are the name of the :guilabel:`Time Off Type`, the :guilabel:`Take Time Off In`, and the :guilabel:`Kind of Time Off`. In addition, the :guilabel:`Time Off Requests` and :guilabel:`Allocation Requests` sections **must** be configured." 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." +#: ../../content/applications/hr/time_off.rst:62 +msgid "Time Off Requests section" 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." +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: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." +msgid ":guilabel:`No Validation`: no approvals are required when requesting this type of time off. The time off request is automatically approved." 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." +#: ../../content/applications/hr/time_off.rst:69 +msgid ":guilabel:`By Time Off Officer`: only the specified :ref:`Time Off Officer `, set on this form in the :guilabel:`Notified 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:72 +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: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)." +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:80 -msgid ":guilabel:`Hours`: if the time off can be taken in hourly increments." +msgid "Allocation Requests section" msgstr "" -#: ../../content/applications/hr/time_off.rst:84 -msgid ":guilabel:`Deduct Extra Hours`: tick this box if the time off request should factor in any extra time accrued by the employee" -msgstr "" - -#: ../../content/applications/hr/time_off.rst:88 -msgid "For example, if an employee worked two (2) extra hours for the week, and requests five (5) hours of time off, the request would be for three (3) hours, since the two (2) additionally worked hours are used first, and deducted from the request." -msgstr "" - -#: ../../content/applications/hr/time_off.rst:92 -msgid ":guilabel:`Allow To Join Supporting Document`: tick this box to allow the employee to attach documents to the time off request. This is useful in situations where documentation is required, such as long-term medical leave." -msgstr "" - -#: ../../content/applications/hr/time_off.rst:95 -msgid ":guilabel:`Kind of Leave`: select from the drop-down menu the type of leave this time off type is, either :guilabel:`Time Off` or :guilabel:`Other`." -msgstr "" - -#: ../../content/applications/hr/time_off.rst:97 -msgid ":guilabel:`Company`: if multiple companies are created in the database, and this time off type only applies to one company, select the company from the drop-down menu. If this field is left blank, the time off type applies to all companies in the database." -msgstr "" - -#: ../../content/applications/hr/time_off.rst:102 -msgid "Allocation requests section" -msgstr "" - -#: ../../content/applications/hr/time_off.rst:104 +#: ../../content/applications/hr/time_off.rst:82 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:108 +#: ../../content/applications/hr/time_off.rst:86 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:112 -msgid "For example, if ten (10) days are allocated to the employee for this particular type of time off, and this option is enabled, the employee may submit a request for more than ten (10) days." -msgstr "" - -#: ../../content/applications/hr/time_off.rst:115 +#: ../../content/applications/hr/time_off.rst:89 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:118 -msgid ":guilabel:`Approval`: select the type of approval(s) required for the allocation of this particular type of time off." +#: ../../content/applications/hr/time_off.rst:93 +msgid "Ten days are allocated to the employee for this particular type of time off, and the :guilabel:`Extra Days Requests Allowed` option is enabled. The employee wants to take a vacation for twelve days. They may submit a request for two additional days, since the :guilabel:`Extra Days Requests Allowed` option is enabled." msgstr "" -#: ../../content/applications/hr/time_off.rst:121 -msgid ":guilabel:`No validation needed` indicates that no approvals are required." +#: ../../content/applications/hr/time_off.rst:99 +msgid "It is important to note that requesting additional time off does **not** guarantee that time off is granted." msgstr "" -#: ../../content/applications/hr/time_off.rst:122 +#: ../../content/applications/hr/time_off.rst:102 +msgid ":guilabel:`Approval`: select the type of approvals required for the allocation of this particular time off type." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:105 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:124 -msgid ":guilabel:`Set by Time Off Officer` indicates that the :ref:`Time Off Officer ` set on this form must allocate the time off." +#: ../../content/applications/hr/time_off.rst:107 +msgid ":guilabel:`No validation needed` indicates that no approvals are required." msgstr "" -#: ../../content/applications/hr/time_off.rst:128 -msgid "Payroll section" +#: ../../content/applications/hr/time_off.rst:110 +msgid "Configuration section" msgstr "" -#: ../../content/applications/hr/time_off.rst:130 -msgid "If the time off type should create :doc:`../hr/payroll/work_entries` in the *Payroll* application, select the :guilabel:`Work Entry Type` from the drop-down list." +#: ../../content/applications/hr/time_off.rst:114 +msgid ":guilabel:`Notified Time Off Officer`: select the person who is notified and responsible for approving requests and allocations for this specific type of time off." msgstr "" -#: ../../content/applications/hr/time_off.rst:134 -msgid "Timesheets section" +#: ../../content/applications/hr/time_off.rst:116 +msgid ":guilabel:`Take Time Off in`: select the format the time off is requested in from the drop-down menu." msgstr "" -#: ../../content/applications/hr/time_off.rst:137 -msgid "The :guilabel:`Timesheets` section only appears if the user is in developer mode. Refer to the :ref:`developer-mode` document for details on how to access the developer mode." +#: ../../content/applications/hr/time_off.rst:119 +msgid "The options are:" msgstr "" -#: ../../content/applications/hr/time_off.rst:140 -msgid "When an employee takes time off and is also using timesheets, Odoo creates entries in the timesheet for the time off. This section defines how they are entered." +#: ../../content/applications/hr/time_off.rst:121 +msgid ":guilabel:`Day`: if time off can only be requested in full day increments (8 hours)." msgstr "" -#: ../../content/applications/hr/time_off.rst:143 -msgid ":guilabel:`Project`: select the project that the time off type entries appear in." +#: ../../content/applications/hr/time_off.rst:122 +msgid ":guilabel:`Half Day`: if time off can only be requested in half day increments (4 hours)." msgstr "" -#: ../../content/applications/hr/time_off.rst:144 -msgid ":guilabel:`Task`: select the task that appears in the timesheet for this time off type. The options are: :guilabel:`Time Off`, :guilabel:`Meeting`, or :guilabel:`Training`." +#: ../../content/applications/hr/time_off.rst:123 +msgid ":guilabel:`Hours`: if the time off can be taken in hourly increments." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:127 +msgid ":guilabel:`Deduct Extra Hours`: enable this option if the time off request should factor in any extra time accrued by the employee" +msgstr "" + +#: ../../content/applications/hr/time_off.rst:131 +msgid "If an employee works two extra hours for the week, and requests five hours of time off, the request would be for three hours, since the two extra worked hours are used first, and deducted from the request." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:135 +msgid ":guilabel:`Allow To Attach Supporting Document`: enable this option 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:138 +msgid ":guilabel:`Kind of Time Off`: select from the drop-down menu the type of time off this is, either :guilabel:`Worked Time` or :guilabel:`Absence`. :guilabel:`Worked Time` indicates that the time off taken counts toward worked time for any type of accrual the employee is working towards, whereas :guilabel:`Absence` does not count toward any type of accrual." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:142 +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. This field **only** appears in a multi-company database." msgstr "" #: ../../content/applications/hr/time_off.rst:148 -msgid "Display option section" +msgid "Negative Cap section" msgstr "" #: ../../content/applications/hr/time_off.rst:150 -msgid ":guilabel:`Color`: select a color to be used in the *Time Off* application dashboard." +msgid "Enable the :guilabel:`Allow Negative Cap` option if employees are able to request more time off than they currently have, allowing a negative balance. If enabled, an :guilabel:`Amount in Negative` field appears. In this field, enter the maximum amount of negative time allowed, in days." msgstr "" -#: ../../content/applications/hr/time_off.rst:151 -msgid ":guilabel:`Cover Image`: select an icon to be used in the *Time Off* application dashboard." +#: ../../content/applications/hr/time_off.rst:155 +msgid "Sara currently has three days of the time off type `Vacation`. She is planning a trip that requires five days of time off." msgstr "" -#: ../../content/applications/hr/time_off.rst:154 -msgid "The only required fields on the time off type form are the name of the :guilabel:`Time Off Type`, the :guilabel:`Approval`, the :guilabel:`Responsible Time Off Officer`, :guilabel:`Take Time Off in`, :guilabel:`Kind of Leave`, and the :guilabel:`Allocation Requests` section." +#: ../../content/applications/hr/time_off.rst:158 +msgid "The `Vacation` time off type has the :guilabel:`Allow Negative Cap` option enabled, and the :guilabel:`Amount in Negative` is set to five." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:161 +msgid "These settings allow Sara to submit a request for five days of the `Vacation` time off type. If approved, her `Vacation` time off balance will be negative two (-2) days." msgstr "" #: ../../content/applications/hr/time_off.rst:-1 -msgid "Time off type form with all the information filled out for sick time off." +msgid "The top half of the time off type form, with all the information filled out for sick time\n" +"off." msgstr "" -#: ../../content/applications/hr/time_off.rst:165 -msgid "Accrual plans" +#: ../../content/applications/hr/time_off.rst:170 +msgid "Payroll section" msgstr "" -#: ../../content/applications/hr/time_off.rst:167 -msgid "Some time off is earned through an accrual plan, meaning that for every specified amount of time an employee works (hour, day, week, etc), they earn or *accrue* a specified amount of time off." -msgstr "" - -#: ../../content/applications/hr/time_off.rst:171 -msgid "If an employee accrues a vacation day for every week they work, they would earn 0.2 vacation days for each hour they work. At the end of a forty (40) hour work week, they earn a whole vacation day (8 hours)." +#: ../../content/applications/hr/time_off.rst:172 +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:176 -msgid "Create accrual plan" +msgid "Timesheets section" msgstr "" -#: ../../content/applications/hr/time_off.rst:178 -msgid "To create a new accrual plan, navigate to :menuselection:`Time Off app --> Configuration --> Accrual Plans`. Then, click the :guilabel:`Create` button, which reveals a blank accrual plan form." +#: ../../content/applications/hr/time_off.rst:179 +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:181 -msgid "Enter the accrual plan name in the :guilabel:`Name` field. If the accrual plan only applies to a specific time off type, select it from the drop-down menu. If this accrual plan is available for all time off types, leave this field blank." +#: ../../content/applications/hr/time_off.rst:182 +msgid "When an employee takes time off, and is also using timesheets, Odoo creates entries in the *Timesheets* application for the time off. This section defines how they are entered." msgstr "" #: ../../content/applications/hr/time_off.rst:185 -msgid "Next, select how the :guilabel:`Level Transition` occurs, either :guilabel:`Immediately` or :guilabel:`After this accrual's period`. By default, the first level begins once the time off is approved if the time off is based on an accrual plan. If :guilabel:`Immediately` is selected, then the next level begins according to the time frame set on the level. If :guilabel:`After this accrual's period` is selected, the next level does not begin until the first level is completed according to the rules set on it." +msgid ":guilabel:`Project`: select the project that the time off type entries appear in." msgstr "" -#: ../../content/applications/hr/time_off.rst:195 -msgid "Rules must be created in order for the accrual plan to accrue time off." +#: ../../content/applications/hr/time_off.rst:186 +msgid ":guilabel:`Task`: select the task that appears in the timesheet for this time off type. The default options are: :guilabel:`Time Off`, :guilabel:`Meeting`, or :guilabel:`Training`." msgstr "" -#: ../../content/applications/hr/time_off.rst:197 -msgid "To create a new rule, click the :guilabel:`Add A New Level` button right beneath the word `Rules`, and a :guilabel:`Create Level` pop-up form appears." +#: ../../content/applications/hr/time_off.rst:190 +msgid "Display Option section" msgstr "" -#: ../../content/applications/hr/time_off.rst:200 -msgid "Fill out the following fields on the form:" +#: ../../content/applications/hr/time_off.rst:192 +msgid ":guilabel:`Color`: select a color to be used in the *Time Off* application dashboard." msgstr "" -#: ../../content/applications/hr/time_off.rst:202 -msgid ":guilabel:`Start after (#) (time period) after allocation date`: enter the number and value of the time period that must pass before the employee starts to accumulate time off. The first value is numerical; enter a number in the first field." +#: ../../content/applications/hr/time_off.rst:193 +msgid ":guilabel:`Cover Image`: select an icon to be used in the *Time Off* application dashboard." msgstr "" -#: ../../content/applications/hr/time_off.rst:206 -msgid "Then, select the type of time period using the drop-down menu in the second field. The options are: :guilabel:`day(s)`, :guilabel:`month(s)`, or :guilabel:`year(s)`." +#: ../../content/applications/hr/time_off.rst:-1 +msgid "The lower half of the time off type form, with all the information filled out for sick time\n" +"off." msgstr "" -#: ../../content/applications/hr/time_off.rst:208 -msgid ":guilabel:`Based on worked time`: tick this box if the accrual of time off is based on the time the employee has worked. If an employee takes time off that is *not* considered a worked day, Odoo will not count that day towards their accrual plan." +#: ../../content/applications/hr/time_off.rst:203 +msgid "Accrual plans" msgstr "" -#: ../../content/applications/hr/time_off.rst:211 -msgid ":guilabel:`Rate (#) (time)`: enter the rate of time off that is accumulated. The first value is numerical; enter a number in the first field. Whole numbers are not necessary, any decimal value may be entered." +#: ../../content/applications/hr/time_off.rst:205 +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:215 -msgid "Next, in the second field, select the type of time accrued using the drop-down menu. The options are either :guilabel:`Days` or :guilabel:`Hours`." +#: ../../content/applications/hr/time_off.rst:209 +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 hour work week, they would earn one whole vacation day (8 hours)." msgstr "" -#: ../../content/applications/hr/time_off.rst:217 -msgid ":guilabel:`Frequency (X)`: select how often the employee accrues the time off for this rule using the drop-down menu. The options are :guilabel:`Daily`, :guilabel:`Weekly`, :guilabel:`Twice a month`, :guilabel:`Monthly`, :guilabel:`Twice a year`, or :guilabel:`Yearly`." +#: ../../content/applications/hr/time_off.rst:214 +msgid "Create accrual plan" +msgstr "" + +#: ../../content/applications/hr/time_off.rst:216 +msgid "To create a new accrual plan, navigate to :menuselection:`Time Off app --> Configuration --> Accrual Plans`. Then, click the :guilabel:`New` button, which reveals a blank accrual plan form." msgstr "" #: ../../content/applications/hr/time_off.rst:221 -msgid "Depending on the selection, more fields appear to specify exactly when the accrual renews." +msgid ":guilabel:`Name`: enter the accrual plan name." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:222 +msgid ":guilabel:`Accrued Gain Time`: select when the employee begins to accrue time off, either :guilabel:`At the start of the accrual period` or :guilabel:`At the end of the accrual period`." msgstr "" #: ../../content/applications/hr/time_off.rst:224 -msgid "If the employee should accrue one vacation day for every week worked, the :guilabel:`Rate` is set to `1`, and the :guilabel:`Frequency` entry is set to `Frequency (Weekly) on (Friday)`. Only the :guilabel:`Frequency` and :guilabel:`Weekday` fields appear." +msgid ":guilabel:`Carry-Over Time`: select when the employee received previously earned time. The options are:" msgstr "" -#: ../../content/applications/hr/time_off.rst:228 -msgid "If the employee should accrue ten (10)vacation days each year, and they receive these days every year on the first of January, the :guilabel:`Rate` is set to `10`, and the :guilabel:`Frequency` entry is set to `Frequency (Yearly) on the (1) of (January)`. The :guilabel:`Frequency`, :guilabel:`Date`, and :guilabel:`Month` fields appear." +#: ../../content/applications/hr/time_off.rst:227 +msgid ":guilabel:`At the start of the year`: select this if the accrual rolls over on January 1 of the upcoming year." msgstr "" -#: ../../content/applications/hr/time_off.rst:233 -msgid ":guilabel:`Limit to`: enter a maximum amount of days the employee can accrue with this plan." +#: ../../content/applications/hr/time_off.rst:229 +msgid ":guilabel:`At the allocation date`: select this if the accrual rolls over as soon as time is allocated to the employee." msgstr "" -#: ../../content/applications/hr/time_off.rst:234 -msgid ":guilabel:`At the end of the calendar year, unused accruals will be`: select from the drop-down menu how unused time off is handled." +#: ../../content/applications/hr/time_off.rst:231 +msgid ":guilabel:`Other`: select this option if neither of the other two options are applicable. When selected, a :guilabel:`Carry-Over Date` field appears. Select the date using the two drop-down menus, one for the day and one for the month." msgstr "" -#: ../../content/applications/hr/time_off.rst:237 -msgid "The options are either :guilabel:`Transferred to the next year`, which rolls over unused time to the next calendar year, or :guilabel:`Lost`, which means any unused time off is gone." +#: ../../content/applications/hr/time_off.rst:235 +msgid ":guilabel:`Based on worked time`: enable this option if time off accrual is determined by the employee's worked hours. Days **not** considered as worked time do **not** contribute to the accrual plan in Odoo." msgstr "" -#: ../../content/applications/hr/time_off.rst:-1 -msgid "A level form with all the data filled out." +#: ../../content/applications/hr/time_off.rst:238 +msgid ":guilabel:`Milestone Transition`: this selection determines when employees move up to a new milestone. If they qualify to change milestones in the middle of a pay period, select if the employee changes milestones :guilabel:`Immediately` or :guilabel:`After this accrual's period` (after the current pay period)." msgstr "" #: ../../content/applications/hr/time_off.rst:244 -msgid "When the form is filled out, click :guilabel:`Save & Close` to save the form and close the pop-up, or :guilabel:`Save & New` to save the form and create a new rule. Add as many levels as desired." +msgid "The :guilabel:`Milestone Transition` field is **only** visible after a minimum of two :ref:`rules ` have been configured on the accrual plan." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:247 +msgid ":guilabel:`Company`: using the drop-down menu, select the company the accrual plan applies to. If left blank, the accrual plan can be used for all companies. This field only appears in a multi-company database." msgstr "" #: ../../content/applications/hr/time_off.rst:-1 -msgid "An accrual form with all the entries filled out." +msgid "An accrual plan form with all the entries filled out." msgstr "" -#: ../../content/applications/hr/time_off.rst:254 -msgid "Public holidays" +#: ../../content/applications/hr/time_off.rst:260 +msgid "Rules must be created in order for employees to accrue time off from the accrual plan." msgstr "" -#: ../../content/applications/hr/time_off.rst:256 -msgid "Most countries have public or national holidays, and some companies may have specific days they are closed and/or give extra days as holidays." -msgstr "" - -#: ../../content/applications/hr/time_off.rst:259 -msgid "It is important to configure these days in Odoo, so employees are aware of the days they have off, and do not request time off on days that are already set as a public holiday (non-working days)." -msgstr "" - -#: ../../content/applications/hr/time_off.rst:263 -msgid "Create public holiday" +#: ../../content/applications/hr/time_off.rst:262 +msgid "To create a new rule, click the :guilabel:`New Milestone` button in the gray :guilabel:`Rules` section, and a :guilabel:`Create Milestone` modal form appears." msgstr "" #: ../../content/applications/hr/time_off.rst:265 -msgid "To create a public holiday, navigate to :menuselection:`Time Off app --> Configuration --> Public Holidays`." +msgid "Fill out the following fields on the form:" msgstr "" -#: ../../content/applications/hr/time_off.rst:268 -msgid "All currently configured public holidays appear in a list view." +#: ../../content/applications/hr/time_off.rst:267 +msgid ":guilabel:`Employee accrue`: select the parameters for earned time off in this section." msgstr "" -#: ../../content/applications/hr/time_off.rst:270 -msgid "Click the :guilabel:`Create` button, and a new line appears at the bottom of the list." +#: ../../content/applications/hr/time_off.rst:269 +msgid "First, select either :guilabel:`Days` or :guilabel:`Hours` for the increment of accrued time using the drop-down menu." msgstr "" #: ../../content/applications/hr/time_off.rst:272 -msgid "Enter the following information:" -msgstr "" - -#: ../../content/applications/hr/time_off.rst:274 -msgid ":guilabel:`Name`: enter the name of the holiday." +msgid "Next, enter the numerical amount of the selected parameter that is accrued. The numerical format is `X.XXXX`, so that partial days or hours can also be configured." msgstr "" #: ../../content/applications/hr/time_off.rst:275 -msgid ":guilabel:`Company`: if in a multi-company database, the current company populates this field by default. It is not possible to edit this field." +msgid "Last, select how often the time is accrued using the drop-down menu. The default options are :guilabel:`Hourly`, :guilabel:`Daily`, :guilabel:`Weekly`, :guilabel:`Twice a month`, :guilabel:`Monthly`, :guilabel:`Twice a year`, and :guilabel:`Yearly`." msgstr "" -#: ../../content/applications/hr/time_off.rst:277 -msgid ":guilabel:`Start Date`: using the date and time picker, select the date and time that the holiday starts. By default, this field is configured for the current date. The start time is set according to the start time for the company (according to the :ref:`working times `). If the user's computer is set to a different time zone, the start time is adjusted according to the difference in the time zone compared to the company's time zone." +#: ../../content/applications/hr/time_off.rst:279 +msgid "Depending on which option is selected, additional fields may appear. For example, if :guilabel:`Twice a month` is selected, two additional fields appear, to specify the two days of each month that the milestone occurs." msgstr "" #: ../../content/applications/hr/time_off.rst:282 -msgid ":guilabel:`End Date`: using the date and time picker, select the date and time that the holiday ends. By default, this field is configured for the current date, and the time is set to the end time for the company (according to the :ref:`working times `). If the user's computer is set to a different time zone, the start time is adjusted according to the difference in the time zone compared to the company's time zone." +msgid ":guilabel:`Cap accrued time`: if there is a maximum amount of days the employee can accrue with this plan, enable this option." msgstr "" -#: ../../content/applications/hr/time_off.rst:289 -msgid "A company is located in San Francisco, and the working times are 9:00 AM - 6:00 PM (an eight (8) hour work day with a one (1) hour lunch break). A user is located in New York, and their computer time zone is set to Eastern. When they create a Public Holiday, the start time appears as 12:00 PM - 9:00 PM, since the time zone is accounted for. If a different user is located in Los Angeles, and their computer time zone is set to Pacific, when they create a Public Holiday, the time appears as 9:00 AM - 6:00 PM." +#: ../../content/applications/hr/time_off.rst:285 +msgid "When enabled, two additional fields appear beneath it. Select the type of time period from the drop-down menu, either :guilabel:`Days` or :guilabel:`Hours`." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:288 +msgid "Then, enter a numerical value in the field to specify the maximum amount of time that can be accrued." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:290 +msgid ":guilabel:`Milestone reached`: 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:294 +msgid "Then, select the type of time period using the drop-down menu in the second field. The options are: :guilabel:`Days`, :guilabel:`Months`, or :guilabel:`Years`." msgstr "" #: ../../content/applications/hr/time_off.rst:296 -msgid ":guilabel:`Working Hours`: if the holiday should only apply to employees who have a specific set of working hours, select the working hours from the drop-down menu. If left blank, the holiday applies to all employees." +msgid ":guilabel:`Carry over`: select how any unused time off is handled. The options are either:" +msgstr "" + +#: ../../content/applications/hr/time_off.rst:298 +msgid ":guilabel:`None. Accrued time reset to 0`: any unused time off is gone." msgstr "" #: ../../content/applications/hr/time_off.rst:299 -msgid ":guilabel:`Work Entry Type`: if using the *Payroll* application, this field defines how the work entry for the holiday appears. Select the work entry type from the drop-down menu." +msgid ":guilabel:`All accrued time carried over`: all unused time off is rolled over to the next calendar year." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:301 +msgid ":guilabel:`Carry over with a maximum`: unused time off is rolled over to the next calendar year, but there is a cap. An :guilabel:`Up to` field appears if this is selected. Enter the maximum number of :guilabel:`Days` that can roll over to the following year. Any time off beyond this parameter is lost." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:306 +msgid "Once the form is completed, click :guilabel:`Save & Close` to save the form and close the modal, or click :guilabel:`Save & New` to save the form and create another milestone. Add as many milestones as desired." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:-1 +msgid "A milestone form with all the entries filled out." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:317 +msgid "Public holidays" +msgstr "" + +#: ../../content/applications/hr/time_off.rst:319 +msgid "To observe public or national holidays, and provide extra days off as holidays to employees, configure the observed *public holidays* in Odoo." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:322 +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:325 +msgid "Additionally, all public holidays configured in the *Time Off* app are also reflected in any app that uses working schedules, such as *Calendar*, *Planning*, *Manufacturing*, and more." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:328 +msgid "Due to Odoo's integration with other apps that use working schedules, it is considered best practice to ensure *all* public holidays are configured." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:332 +msgid "Create public holiday" +msgstr "" + +#: ../../content/applications/hr/time_off.rst:334 +msgid "To create a public holiday, navigate to :menuselection:`Time Off app --> Configuration --> Public Holidays`." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:337 +msgid "All currently configured public holidays appear in a list view." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:339 +msgid "Click the :guilabel:`New` button, and a new line appears at the bottom of the list." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:341 +#: ../../content/applications/hr/time_off.rst:403 +msgid "Enter the following information on that new line:" +msgstr "" + +#: ../../content/applications/hr/time_off.rst:343 +msgid ":guilabel:`Name`: enter the name of the holiday." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:344 +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:348 +msgid "The :guilabel:`Company` field is hidden by default. To view this field, click the two dots in the top-right corner of the list, to the far-right of the column titles, and activate the :guilabel:`Company` selection from the drop-down menu that appears." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:352 +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 schedules `). 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:357 +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 schedules `). 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:364 +msgid "A company located in San Francisco operates from 9:00 AM - 6:00 PM, with an eight hour work day and one hour lunch break." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:367 +msgid "For a user in New York, with a computer time zone set to Eastern Standard Time, a created public holiday displays a start time of 12:00 PM - 9:00 PM, accounting for the three hour time zone difference." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:371 +msgid "Similarly, a user located in Los Angeles, with a computer time zone set to Pacific Standard Time, sees a public holiday time as 9:00 AM - 6:00 PM." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:374 +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:377 +msgid ":guilabel:`Work Entry Type`: if using the *Payroll* application, this field defines how the :ref:`work entries ` for the holiday appear. 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:311 -msgid "To view a color-coded schedule of both the user's time off, and/or the team managed by them, navigate to :menuselection:`Time Off app --> Overview`. This presents a calendar with the default filter of :guilabel:`My Team`, in a month view." -msgstr "" - -#: ../../content/applications/hr/time_off.rst:315 -msgid "To change the time period displayed, click on either the :guilabel:`Day`, :guilabel:`Week`, :guilabel:`Month`, or :guilabel:`Year` buttons to present the calendar in that corresponding view." -msgstr "" - -#: ../../content/applications/hr/time_off.rst:318 -msgid "Each team member is displayed on a line, and any time off they requested, regardless of the status (:guilabel:`Validated` or :guilabel:`To Approve`), appears on the calendar." -msgstr "" - -#: ../../content/applications/hr/time_off.rst:321 -msgid "Each employee is color-coded. The employee's color is selected at random and does not correspond to the type of time off they requested." -msgstr "" - -#: ../../content/applications/hr/time_off.rst:324 -msgid "The status of the time of is represented by the color of the request either appearing solid (:guilabel:`Validated`) or striped (:guilabel:`To Approve`)." -msgstr "" - -#: ../../content/applications/hr/time_off.rst:327 -msgid "The number of days or hours requested is written on the request (if there is enough space)." -msgstr "" - -#: ../../content/applications/hr/time_off.rst:329 -msgid "At the bottom of the calendar, a bar graph shows how many people are projected to be out on any given day. The number on the bar represents the number of employees out for those highlighted days." -msgstr "" - -#: ../../content/applications/hr/time_off.rst:332 -msgid "Hover over a time off entry to view the details for the specific time off entry. The total number of hours or days are listed, along with the start and end time of the time off." -msgstr "" - -#: ../../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:342 -msgid "Allocate time off" -msgstr "" - -#: ../../content/applications/hr/time_off.rst:344 -msgid "Once time off types and accrual plans have been configured, the next step is to allocate, or give, time off to employees. This section is only visible to users who have either :guilabel:`Time Off Officer` or :guilabel:`Administrator` access rights for the *Time Off* application." -msgstr "" - -#: ../../content/applications/hr/time_off.rst:348 -msgid "To create a new allocation, navigate to :menuselection:`Time Off app --> Approvals --> Allocations`." -msgstr "" - -#: ../../content/applications/hr/time_off.rst:350 -msgid "This presents a list of all current allocations, including their respective status." -msgstr "" - -#: ../../content/applications/hr/time_off.rst:352 -msgid "Click :guilabel:`Create` to allocate time off, and a blank allocation form appears." -msgstr "" - -#: ../../content/applications/hr/time_off.rst:354 -msgid "After entering a name for the allocation on the first blank field of the form, enter the following information:" -msgstr "" - -#: ../../content/applications/hr/time_off.rst:357 -msgid ":guilabel:`Time Off Type`: using the drop-down menu, select the type of time off that is being allocated to the employees." -msgstr "" - -#: ../../content/applications/hr/time_off.rst:359 -msgid ":guilabel:`Allocation Type`: select either :guilabel:`Regular Allocation` or :guilabel:`Accrual Allocation`." -msgstr "" - -#: ../../content/applications/hr/time_off.rst:361 -msgid ":guilabel:`Accrual Plan`: if :guilabel:`Accrual Allocation` is selected for the :guilabel:`Allocation Type`, the :guilabel:`Accrual Plan` field appears. Using the drop-down menu, select the accrual plan with which the allocation is associated. An accrual plan **must** be selected for an :guilabel:`Accrual Allocation`." -msgstr "" - -#: ../../content/applications/hr/time_off.rst:365 -msgid ":guilabel:`Validity Period/Start Date`: if :guilabel:`Regular Allocation` is selected for the :guilabel:`Allocation Type`, this field is labeled :guilabel:`Validity Period`." -msgstr "" - -#: ../../content/applications/hr/time_off.rst:368 -msgid "Using the calendar, select the beginning date for the allocation. If the allocation expires, select the expiration date in the next date field. If the time off does *not* expire, leave the second date field blank." -msgstr "" - -#: ../../content/applications/hr/time_off.rst:372 -msgid "If :guilabel:`Accrual Allocation` is selected for the :guilabel:`Allocation Type`, this field is labeled :guilabel:`Start Date`." -msgstr "" - -#: ../../content/applications/hr/time_off.rst:375 -msgid "Using the calendar picker, select the start date for the allocation. If the allocation expires, select the expiration date in the :guilabel:`Run until` field. If the time off does *not* expire, leave the :guilabel:`Run until` field blank." -msgstr "" - -#: ../../content/applications/hr/time_off.rst:378 -msgid ":guilabel:`Duration`: enter the amount of time that is being allocated to the employees. This field displays the time in either :guilabel:`Hours` or :guilabel:`Days`, depending on how the selected :ref:`Time Off Type ` is configured (in days or hours)." -msgstr "" - -#: ../../content/applications/hr/time_off.rst:381 -msgid ":guilabel:`Mode`: using the drop-down menu, select how the allocation is assigned. This selection determines who receives the time off allocation. The options are :guilabel:`By Employee`, :guilabel:`By Company`, :guilabel:`By Department`, or :guilabel:`By Employee Tag`." -msgstr "" - -#: ../../content/applications/hr/time_off.rst:385 -msgid "Depending on what was selected for the :guilabel:`Mode`, this following field is labeled either: :guilabel:`Employees`, :guilabel:`Company`, :guilabel:`Department`, or :guilabel:`Employee Tag`." +#: ../../content/applications/hr/time_off.rst:386 +msgid "Mandatory days" msgstr "" #: ../../content/applications/hr/time_off.rst:388 -msgid "Using the drop-down menu, indicate the specific employees, company, department, or employee tags who are receiving this time off." +msgid "Some companies have special days where specific departments, or the entire staff, is required to be present, and time off is not allowed on those specific days." msgstr "" #: ../../content/applications/hr/time_off.rst:391 -msgid "Multiple selections can be made for either :guilabel:`Employees` or :guilabel:`Employee Tag`." +msgid "These types of days are called *mandatory days* in Odoo. These can be configured to be company-wide, or department specific. When configured, employees in the specified department or company are unable to submit time off requests for these mandatory days." msgstr "" -#: ../../content/applications/hr/time_off.rst:393 -msgid "Only one selection can be made for the :guilabel:`Company` or :guilabel:`Department`." +#: ../../content/applications/hr/time_off.rst:396 +msgid "Create mandatory days" msgstr "" -#: ../../content/applications/hr/time_off.rst:394 -msgid ":guilabel:`Add a reason...`: if any description or note is necessary to explain the time off allocation, enter it in this field at the bottom of the form." +#: ../../content/applications/hr/time_off.rst:398 +msgid "No mandatory days are configured in Odoo by default. To create a mandatory day, navigate to :menuselection:`Time Off app --> Configuration --> Mandatory Days`." msgstr "" -#: ../../content/applications/hr/time_off.rst:400 -msgid "Request time off" +#: ../../content/applications/hr/time_off.rst:401 +msgid "Click the :guilabel:`New` button in the top-left corner, and a blank line appears in the list." msgstr "" -#: ../../content/applications/hr/time_off.rst:402 -msgid "Once an employee has been allocated time off, a request to use the time off can be submitted. Time off can be requested in one of two ways, either from the :ref:`dashboard ` or from the :guilabel:`My Time Off` view." +#: ../../content/applications/hr/time_off.rst:405 +msgid ":guilabel:`Name`: enter the name of the mandatory day." msgstr "" #: ../../content/applications/hr/time_off.rst:406 -msgid "To access the dashboard, navigate to :menuselection:`Time Off app --> My Time Off --> Dashboard`. This is also the default view for the *Time Off* application." +msgid ":guilabel:`Company`: if in a multi-company database, this field is visible, and the current company populates this field by default. Using the drop-down menu, select the company the mandatory day is for." msgstr "" #: ../../content/applications/hr/time_off.rst:409 -msgid "To access :guilabel:`My Time Off`, navigate to :menuselection:`Time Off app --> My Time Off --> My Time Off`. This presents a list view of all the time off requests for the employee." +msgid ":guilabel:`Departments`: this column is hidden by default. First, click the :guilabel:`(optional columns)` icon in the top-right corner, next to :guilabel:`Colors`, and then click the checkbox next to :guilabel:`Departments` to reveal that column." msgstr "" -#: ../../content/applications/hr/time_off.rst:412 -msgid "To create a new request for time off, click either the :guilabel:`New Time Off` button on the main *Time Off* dashboard, or the :guilabel:`Create` button in the :guilabel:`My Time Off` list view. Both buttons open a new time off request form." +#: ../../content/applications/hr/time_off.rst:413 +msgid "Next, select the desired departments from the drop-down menu. Multiple departments can be selected, and there is no limit to the amount of departments that can be added." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:416 +msgid "If this field is left blank, the mandatory day applies to the entire company." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:417 +msgid ":guilabel:`Start Date`: using the calendar picker, select the date the mandatory day starts." msgstr "" #: ../../content/applications/hr/time_off.rst:418 -msgid ":guilabel:`Time Off Type`: select the type of time off being requested from the drop-down menu." +msgid ":guilabel:`End Date`: using the calendar picker, select the date the mandatory day ends. If creating a single mandatory day, the end date should be the same as the start date." msgstr "" -#: ../../content/applications/hr/time_off.rst:419 -msgid ":guilabel:`Dates`: enter the dates that the time off will fall under. There are two fields to populate, the :guilabel:`From` and :guilabel:`To` fields. Click on either the :guilabel:`From` or :guilabel:`To` field, and a calendar pop-up appears." +#: ../../content/applications/hr/time_off.rst:420 +msgid ":guilabel:`Color`: if desired, select a color from the available presented options. If no color is desired, select the `No color` option, represented by a white box with a red line diagonally across it. The selected color appears on the main *Time Off* application dashboard, in both the calendar and in the legend." msgstr "" -#: ../../content/applications/hr/time_off.rst:423 -msgid "Click on the start date, then click on the end date. The selected start and end dates appear in deep purple, and the dates between them appear in pale purple (if applicable)." +#: ../../content/applications/hr/time_off.rst:-1 +msgid "The Mandatory Days section with three configured days." msgstr "" -#: ../../content/applications/hr/time_off.rst:426 -msgid "If the time off requested is for a single day, click on the start date, then click the same date again for the end date." +#: ../../content/applications/hr/time_off.rst:432 +msgid "Allocate time off" msgstr "" -#: ../../content/applications/hr/time_off.rst:429 -msgid "When the correct dates are selected/highlighted, click the :guilabel:`Apply` button." +#: ../../content/applications/hr/time_off.rst:434 +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:431 -msgid "The dates now populate the :guilabel:`From` and :guilabel:`To` fields." -msgstr "" - -#: ../../content/applications/hr/time_off.rst:433 -msgid ":guilabel:`Half Day`: if the time off request is for a half day, tick this box. When this is selected, the :guilabel:`From` date field disappears, and is replaced with a drop-down menu. Select either :guilabel:`Morning` or :guilabel:`Afternoon` to indicate which half of the day is being requested." -msgstr "" - -#: ../../content/applications/hr/time_off.rst:437 -msgid ":guilabel:`Custom Hours`: if the time off requested is not a whole or half day, tick this box. A :guilabel:`From` and :guilabel:`To` field appears beneath this option if selected. Using the drop-down menu, select the start and end time for the time off request." +#: ../../content/applications/hr/time_off.rst:438 +msgid "To create a new allocation, navigate to :menuselection:`Time Off app --> Management --> Allocations`." msgstr "" #: ../../content/applications/hr/time_off.rst:441 -msgid ":guilabel:`Duration`: this field updates automatically once the :guilabel:`Date` section is completed. If the :guilabel:`Date` section is modified, this section automatically updates to reflect the total time off requested. This field is in either hours or days, depending on the :guilabel:`Date` selections." +msgid "This presents a list of all current allocations, including their respective statuses." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:443 +msgid "Click :guilabel:`New` to allocate time off, and a blank allocation form appears." msgstr "" #: ../../content/applications/hr/time_off.rst:445 +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:448 +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:450 +msgid ":guilabel:`Allocation Type`: select either :guilabel:`Regular Allocation` or :guilabel:`Accrual Allocation`. If the allocation is **not** based on an accrual plan, select :guilabel:`Regular Allocation`." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:453 +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:457 +msgid ":guilabel:`Validity Period/Start Date`: if :guilabel:`Regular Allocation` is selected for the :guilabel:`Allocation Type`, this field is labeled :guilabel:`Validity Period`. 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:462 +msgid "The current date populates the first date field by default. To select another date, click on the pre-populated date to reveal a popover calendar window. Navigate to the desired start date for the allocation, and click on the date to select it." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:466 +msgid "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. `No Limit` appears in the field if no date is selected." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:470 +msgid "If :guilabel:`Accrual Allocation` is selected for the :guilabel:`Allocation Type`, this second field is labeled :guilabel:`Run until`." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:472 +msgid ":guilabel:`Allocation`: 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 hours or days)." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:475 +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:479 +msgid "Depending on what is 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:482 +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:485 +msgid "Multiple selections can be made for either :guilabel:`Employees` or :guilabel:`Employee Tag`." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:487 +msgid "Only one selection can be made for the :guilabel:`Company` or :guilabel:`Department`." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:488 +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:-1 +msgid "A new allocation form with all the fields filled out for the annual two week vacation\n" +"granted to all employees." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:499 +msgid "Request time off" +msgstr "" + +#: ../../content/applications/hr/time_off.rst:501 +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 :ref:`My Time Off ` view." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:505 +msgid "To create a new request for time off, click the :guilabel:`New` button on either the main *Time Off* :guilabel:`Dashboard` or the :guilabel:`My Time Off` list view." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:509 +msgid "Both :guilabel:`New` buttons allow the user to request time off, but when requested from the :guilabel:`Dashboard`, a :guilabel:`New Time Off` request form appears in a modal. When requested from the :guilabel:`My Time Off` list view, the screen navigates to a new time off request page, instead." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:514 +msgid "Enter the following information on the :guilabel:`New Time Off` request form:" +msgstr "" + +#: ../../content/applications/hr/time_off.rst:516 +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:517 +msgid ":guilabel:`Dates`: enter the dates that the time off falls under. There are two fields to populate, the start and end dates. Click on either date field and a popover calendar appears." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:520 +msgid "Click on the start date, then click on the end date. The selected start and end dates are circled, and the dates between them are highlighted (if applicable)." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:523 +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:526 +msgid "When the correct dates are selected/highlighted, click the :guilabel:`Apply` button." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:528 +msgid "The selected dates now populate the two portions of the :guilabel:`Dates` field." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:530 +msgid "If the selected :guilabel:`Time Off Type` is configured to have the time off taken in hours, the following two fields also appear:" +msgstr "" + +#: ../../content/applications/hr/time_off.rst:533 +msgid ":guilabel:`Half Day`: if the time off request is for a half day, check this box. When this is selected, the second date field disappears, and is replaced with a drop-down menu. From that 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:537 +msgid ":guilabel:`Custom Hours`: if the time off requested is not a whole or half day, check 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:541 +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 how the selected :guilabel:`Time Off Type` is configured." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:545 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:447 +#: ../../content/applications/hr/time_off.rst:547 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:451 -msgid "Navigate to the file(s) to attach, then click the :guilabel:`Open` button. The files then appear on the time off request form. Multiple documents can be attached, if necessary." +#: ../../content/applications/hr/time_off.rst:551 +msgid "Navigate to the desired files to attach, select them, 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:454 -#: ../../content/applications/hr/time_off.rst:494 -msgid "When the form is complete, click the :guilabel:`Save` button to save the information, and submit the request." +#: ../../content/applications/hr/time_off.rst:554 +#: ../../content/applications/hr/time_off.rst:604 +msgid "If the request was created from the :guilabel:`Dashboard`, click the :guilabel:`Save & Close` button to save the information and submit the request." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:557 +msgid "If the form was completed from the :guilabel:`My Time Off` list view, the information is automatically saved as it is entered. However, the form can be saved manually at any time by clicking the *save manually* button, represented by a :guilabel:`(cloud upload)` icon." 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:464 +#: ../../content/applications/hr/time_off.rst:568 msgid "Request allocation" msgstr "" -#: ../../content/applications/hr/time_off.rst:466 -msgid "If an employee has used all their time off, or is going to run out of time off, they can request an allocation for additional time. Allocations can be requested in one of two ways, either from the :ref:`dashboard ` or the :guilabel:`My Allocations` view." +#: ../../content/applications/hr/time_off.rst:570 +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 :ref:`My Allocations ` view." msgstr "" -#: ../../content/applications/hr/time_off.rst:470 -msgid "To access the dashboard, navigate to the :menuselection:`Time Off app --> My Time Off --> Dashboard`. This is also the default view for the *Time Off* application." +#: ../../content/applications/hr/time_off.rst:574 +msgid "To create a new allocation request, click either the :guilabel:`New Allocation Request` button on the main *Time Off* dashboard, or the :guilabel:`New` button in the :guilabel:`My Allocations` list view. Both buttons open a new allocation request form." msgstr "" -#: ../../content/applications/hr/time_off.rst:473 -msgid "To access :guilabel:`My Allocations`, navigate to the :menuselection:`Time Off app --> My Time Off --> My Allocations`. This presents a list view of all the allocations for the employee." +#: ../../content/applications/hr/time_off.rst:579 +msgid "Both :guilabel:`New` buttons open a :guilabel:`New Allocation` request form, but when requested from the :guilabel:`Dashboard`, the form appears in a modal. When requested from the :guilabel:`My Allocations` list view, the screen navigates to a new allocation request page, instead." msgstr "" -#: ../../content/applications/hr/time_off.rst:476 -msgid "To create a new allocation request, click either the :guilabel:`Allocation Request` button on the main *Time Off* dashboard, or the :guilabel:`Create` button in the :guilabel:`My Allocations` list view. Both buttons open a new allocation request form." +#: ../../content/applications/hr/time_off.rst:584 +msgid "Enter the following information on the :guilabel:`New Allocation` request form:" msgstr "" -#: ../../content/applications/hr/time_off.rst:480 -msgid "After entering a name for the allocation in the first blank line on the form, enter the following information:" +#: ../../content/applications/hr/time_off.rst:586 +msgid ":guilabel:`Time Off Type`: select the type of time off being requested for the allocation from the drop-down menu. After a selection is made, the title updates with the time off type." msgstr "" -#: ../../content/applications/hr/time_off.rst:483 -msgid ":guilabel:`Time Off Type`: select the type of time off being requested for the allocation from the drop-down menu." +#: ../../content/applications/hr/time_off.rst:588 +msgid ":guilabel:`Validity Period`: this field **only** appears if requesting an allocation with a time off type that has the :guilabel:`Take Time Off in` field :ref:`configured ` to either :guilabel:`Day` or :guilabel:`Half Day`. This field does **not** appear if the :guilabel:`Take Time Off in` field is set to :guilabel:`Hours`." msgstr "" -#: ../../content/applications/hr/time_off.rst:485 -msgid ":guilabel:`Validity Period`: the current date populates the start date by default. If there is no expiration on the time off type, there is no date populated as the end date. If the time off type has an expiration date, the date automatically populates the end date field once the form is saved." +#: ../../content/applications/hr/time_off.rst:593 +msgid "Using the calendar selector, select a start and end date the allocation is valid for. By default, the current date populates the first field, and :guilabel:`No Limit` populates the second field." msgstr "" -#: ../../content/applications/hr/time_off.rst:489 -msgid ":guilabel:`Duration`: enter the amount of time being requested. The format (either days or hours) is in the same format as the time off type." +#: ../../content/applications/hr/time_off.rst:596 +msgid "Adjust both of these dates, if desired." msgstr "" -#: ../../content/applications/hr/time_off.rst:491 +#: ../../content/applications/hr/time_off.rst:597 +msgid ":guilabel:`Allocation`: enter the amount of time being requested in this field. The format is presented in either days or hours, depending on how the time off type is configured. Once this field is populated, the name of the allocation request is updated to include the amount of time being requested." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:601 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:607 +msgid "If the form was completed from the :guilabel:`My Allocations` list view, the information is automatically saved as it is entered. However, the form can be saved manually at any time by clicking the *save manually* button, represented by a :guilabel:`(cloud upload)` icon." +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:503 -msgid "Approvals" +#: ../../content/applications/hr/time_off.rst:619 +msgid "Management" msgstr "" -#: ../../content/applications/hr/time_off.rst:505 -msgid "Most requests for time off and allocations need to go through the approval process, prior to the time off being allocated, and then granted to an employee. Requests either need one or two approvals, depending on how the specific type of time off is configured." +#: ../../content/applications/hr/time_off.rst:621 +msgid "Time off and allocation requests typically undergo an approval process before being granted. Requests either need one or two approvals, if any, depending on how the specific type of time off is configured. These are all housed under the :guilabel:`Management` section of the *Time Off* application." msgstr "" -#: ../../content/applications/hr/time_off.rst:509 -msgid "Only users who can approve allocation and time off requests have the :guilabel:`Approvals` section visible in the *Time Off* application." +#: ../../content/applications/hr/time_off.rst:626 +msgid "Only users who can approve allocation and time off requests have the :guilabel:`Management` section visible in the *Time Off* application." msgstr "" -#: ../../content/applications/hr/time_off.rst:513 -msgid "Approve allocations" +#: ../../content/applications/hr/time_off.rst:632 +msgid "Manage time off" msgstr "" -#: ../../content/applications/hr/time_off.rst:515 -msgid "To view allocations that need approval, navigate to :menuselection:`Time Off app --> Approvals --> Allocations`. The only allocations visible on this list are for employees the user has either :guilabel:`Time Off Officer` or :guilabel:`Administrator` access rights for in the *Time Off* application." +#: ../../content/applications/hr/time_off.rst:634 +msgid "To view time off requests that need approval, navigate to :menuselection:`Time Off app --> Management --> 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 in the *Time Off* application." msgstr "" -#: ../../content/applications/hr/time_off.rst:520 -msgid "The default filters that are configured to be in place when navigating to the :guilabel:`Allocations` list are :guilabel:`My Team` and :guilabel:`Active Employee`. This *only* presents employees on the user's team (who they manage) and active employees. Inactive users are not shown." +#: ../../content/applications/hr/time_off.rst:639 +msgid "The default filter in the :guilabel:`Time Off` list is `Waiting For Me`. This only presents time off requests that need to be approved for current employees on the user's team, with a status of either :guilabel:`To Approve` or :guilabel:`Second Approval`." msgstr "" -#: ../../content/applications/hr/time_off.rst:525 -msgid "The left side of the screen has various grouping options to narrow down the presented allocation requests." +#: ../../content/applications/hr/time_off.rst:643 +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`, :guilabel:`To Approve`, and :guilabel:`Second Approval`. The various departments the user is a member of, and manages employees under, also appear on the left side of the screen, under :guilabel:`Departments`." msgstr "" -#: ../../content/applications/hr/time_off.rst:528 -msgid "The options are :guilabel:`To Approve`, :guilabel:`To Submit`, :guilabel:`Refused`, and :guilabel:`Approved`." +#: ../../content/applications/hr/time_off.rst:650 +msgid "If there are no requests that fall under one of the status options or departments, that status or department is **not** visible on the left-side menu." msgstr "" -#: ../../content/applications/hr/time_off.rst:531 -msgid "To view all allocation requests, click :guilabel:`All`." +#: ../../content/applications/hr/time_off.rst:653 +msgid "To display time off requests for specific departments only, click on the :guilabel:`Department` on the left-hand side. Only requests within the selected department are then presented." msgstr "" -#: ../../content/applications/hr/time_off.rst:533 -msgid "It is also possible to display allocation requests by department. Click on the department to only present allocations for that specific department." -msgstr "" - -#: ../../content/applications/hr/time_off.rst:537 -msgid "The groupings on the left side only present allocation requests that fall under the default filters of :guilabel:`My Team` and :guilabel:`Active Employee`. Only the statuses for allocation requests that fall under those filters are presented on the left side." -msgstr "" - -#: ../../content/applications/hr/time_off.rst:541 -msgid "For example, if there are no requests with a status of :guilabel:`To Submit`, that status option does not appear in the left-hand side." -msgstr "" - -#: ../../content/applications/hr/time_off.rst:544 -msgid "All departments for the user's employees appear in the list. If there are no allocation requests that fall under that department matching the pre-configured filters, the list is blank." -msgstr "" - -#: ../../content/applications/hr/time_off.rst:547 -msgid "It is always possible to remove any of the pre-configured filters, by clicking the :guilabel:`✖️ (remove)` icon on the specific filter to remove it." -msgstr "" - -#: ../../content/applications/hr/time_off.rst:550 -#: ../../content/applications/hr/time_off.rst:599 +#: ../../content/applications/hr/time_off.rst:656 +#: ../../content/applications/hr/time_off.rst:721 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:553 -msgid "The :guilabel:`To Approve` requests are highlighted in yellow, :guilabel:`Approved` requests are highlighted in green, :guilabel:`To Submit` (drafts) requests are highlighted in blue, and the :guilabel:`Refused` requests are highlighted in gray." +#: ../../content/applications/hr/time_off.rst:659 +msgid "The :guilabel:`To Approve` and :guilabel:`Second Approval` requests are highlighted in yellow and are the only ones that appear in the list by default. If the `Waiting For Me` 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:557 -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:564 -msgid "If more details are needed, click anywhere on the allocation request line (except for :guilabel:`✔ Validate` and :guilabel:`✖️ Refuse`) to view the request in detail." -msgstr "" - -#: ../../content/applications/hr/time_off.rst:567 -msgid "Depending on the rights of the user, changes can be made on the allocation request form that appears. To modify the request, click the :guilabel:`Edit` button, make any desired changes, then click :guilabel:`Save`." -msgstr "" - -#: ../../content/applications/hr/time_off.rst:571 -msgid "It is also possible to approve or refuse the request from this form. Click the :guilabel:`Validate` button to approve, or the :guilabel:`Refuse` button to refuse the request." -msgstr "" - -#: ../../content/applications/hr/time_off.rst:577 -msgid "Approve time off" -msgstr "" - -#: ../../content/applications/hr/time_off.rst:579 -msgid "To view time off requests that need approval, navigate to :menuselection:`Time Off app --> Approvals --> Time Off`. The only time off requests visible on this list are for employees the user has either :guilabel:`Time Off Officer` or :guilabel:`Administrator` access rights for the *Time Off* application." -msgstr "" - -#: ../../content/applications/hr/time_off.rst:584 -msgid "The default filters in the :guilabel:`Time Off` list are :guilabel:`To Approve`, :guilabel:`My Team`, :guilabel:`Active Employee`, and :guilabel:`Active Time Off`. This only presents time off requests that need to be approved for current employees on the user's team, for requests that are active and *not* in a draft mode." -msgstr "" - -#: ../../content/applications/hr/time_off.rst:589 -msgid "The left side of the screen has various grouping options to narrow down the presented time off requests. Since only time off requests that need to be approved are shown, the only status options are :guilabel:`All` and :guilabel:`To Approve`." -msgstr "" - -#: ../../content/applications/hr/time_off.rst:593 -msgid "To view requests with other statuses, first remove the :guilabel:`To Approve` filter, by clicking the :guilabel:`✖️ (remove)` icon next to the :guilabel:`To Approve` filter to remove it." -msgstr "" - -#: ../../content/applications/hr/time_off.rst:596 -msgid "To display time off requests for specific departments, click on the department on the left-hand side. Only requests within the selected department are then presented." -msgstr "" - -#: ../../content/applications/hr/time_off.rst:602 -msgid "The :guilabel:`To Approve` requests are highlighted in yellow, and are the only ones that appear in the list by default. If the :guilabel:`To Approve` filter is removed, then all statuses appear. :guilabel:`Approved` requests are highlighted in green, :guilabel:`To Submit` (drafts) requests are highlighted in blue, and the :guilabel:`Refused` requests are highlighted in gray." -msgstr "" - -#: ../../content/applications/hr/time_off.rst:607 -msgid "To approve a time off request, click :guilabel:`👍 Approve` at the end of the line, to refuse a request, click :guilabel:`✖️ Refuse`." +#: ../../content/applications/hr/time_off.rst:665 +msgid "To approve a time off request, click the :guilabel:`👍 Approve` button at the end of the line. To validate a time off request that has already been approved, and is waiting on a second approval, click the :guilabel:`✔️ Validate` button at the end of the line. To refuse a request, click the :guilabel:`✖️ Refuse` button at the far end of the line." 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:614 -msgid "If more details are needed, click anywhere on the time off request line (except for :guilabel:`👍 Approve` and :guilabel:`✖️ Refuse`) to load the time off request form. Depending on the rights of the user, changes can be made." +#: ../../content/applications/hr/time_off.rst:674 +msgid "For more details, click anywhere on the time off request line (except for the :guilabel:`👍 Approve`, :guilabel:`✔️ Validate`, and :guilabel:`✖️ Refuse` buttons) 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:618 -msgid "To modify the request, click the :guilabel:`Edit` button, make any desired changes, then click :guilabel:`Save`." +#: ../../content/applications/hr/time_off.rst:678 +msgid "To modify the request, make any desired changes to the form. All changes are automatically saved." msgstr "" -#: ../../content/applications/hr/time_off.rst:621 +#: ../../content/applications/hr/time_off.rst:680 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:625 -#: ../../content/applications/hr/time_off.rst:676 -msgid "My time off" +#: ../../content/applications/hr/time_off.rst:684 +msgid "Manage allocations" msgstr "" -#: ../../content/applications/hr/time_off.rst:627 -msgid "The :guilabel:`My Time Off` section of the *Time Off* application contains the time off dashboard, as well as the user's time off requests and allocations." +#: ../../content/applications/hr/time_off.rst:686 +msgid "To view allocations that need approval, navigate to :menuselection:`Time Off app --> Management --> 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:633 +#: ../../content/applications/hr/time_off.rst:691 +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:696 +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:699 +msgid "The :guilabel:`Status` options are :guilabel:`To Approve`, :guilabel:`Refused`, and :guilabel:`Approved`. Click on a specific :guilabel:`Status` to view only requests with that status. To view all allocation requests, click :guilabel:`All`." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:703 +msgid "It is also possible to display allocation requests by department. Click on the :guilabel:`Department` in the left side of the screen to only present allocations for that specific department." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:708 +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:712 +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:715 +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:718 +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:724 +msgid "The :guilabel:`To Approve` requests are highlighted in yellow, :guilabel:`Approved` requests are highlighted in green, and the :guilabel:`Refused` requests are highlighted in gray." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:727 +msgid "To approve an allocation request, click the :guilabel:`✔ Validate` button at the end of the line. To refuse a request, click the :guilabel:`✖️ Refuse` button." +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:734 +msgid "If more details are needed, click anywhere on the allocation request line (except for the :guilabel:`✔ Validate` and :guilabel:`✖️ Refuse` buttons) to view the request in detail." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:737 +msgid "Depending on the rights of the user, changes can be made to the allocation request form that appears. To modify the request, make any desired changes to the form. All changes are automatically saved." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:741 +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:747 +msgid "To view a color-coded schedule of the user's time off, and/or of the team managed by them, navigate to :menuselection:`Time Off app --> Overview`. This presents a calendar with the default filter of `My Team`, in a month view." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:751 +msgid "To change the time period displayed, click on the :guilabel:`Month` button to reveal a drop-down menu. Then, select either :guilabel:`Day`, :guilabel:`Week`, or :guilabel:`Year` to present the calendar in that corresponding view." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:755 +msgid "To navigate forward or backward in time, in the selected increment (:guilabel:`Month`, :guilabel:`Week`, etc.), click the :guilabel:`← (left arrow)` or :guilabel:`→ (right arrow)` to move either forward or backward in that specified amount of time." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:759 +msgid "For example, if :guilabel:`Month` is selected, the arrows adjust the view by one month." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:761 +msgid "To return to a view containing the current day, click the :guilabel:`Today` button at any time." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:763 +msgid "Team members are listed alphabetically on individual lines, and their requested time off, regardless of the status (*validated* or *to approve*), is visible on the calendar." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:766 +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:769 +msgid "The status of the time off is represented by the color detail of the request, either appearing solid (*validated*) or striped (*to approve*)." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:772 +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:774 +msgid "At the bottom of the calendar, in the :guilabel:`Total` line, a bar graph shows how many people are projected to be out on any given day. The number on each individual bar represents the number of employees out for those highlighted days." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:778 +msgid "Click on 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. To view the details of the time off request in a modal, click the :guilabel:`View` button." +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:787 +msgid "My time" +msgstr "" + +#: ../../content/applications/hr/time_off.rst:789 +msgid "The :guilabel:`My Time` 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:795 msgid "Dashboard" msgstr "" -#: ../../content/applications/hr/time_off.rst:635 -msgid "All users have access to the time off dashboard, which is the default view in the *Time Off* application. The dashboard can also be accessed at any point in the application by navigating to :menuselection:`Time Off app --> My Time Off --> Dashboard`." +#: ../../content/applications/hr/time_off.rst:797 +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 --> Dashboard`." msgstr "" -#: ../../content/applications/hr/time_off.rst:639 +#: ../../content/applications/hr/time_off.rst:801 msgid "The current year is displayed, and the current day is highlighted in red." msgstr "" -#: ../../content/applications/hr/time_off.rst:641 -msgid "To change the view, click on the desired button at the top. The options are :guilabel:`Day`, :guilabel:`Week`, :guilabel:`Month`, or :guilabel:`Year` (the default)." +#: ../../content/applications/hr/time_off.rst:803 +msgid "To change the view, click on the :guilabel:`Year` button to reveal a drop-down menu. Then, select either :guilabel:`Day`, :guilabel:`Week`, or :guilabel:`Month` to present the calendar in that corresponding view." msgstr "" -#: ../../content/applications/hr/time_off.rst:644 -msgid "To change the presented dates, click the left and right arrows on either side of the :guilabel:`Today` button. The calendar view adjusts in increments of the presented view." +#: ../../content/applications/hr/time_off.rst:807 +msgid "To change the presented dates, click the :guilabel:`← (left arrow)` or :guilabel:`→ (right arrow)` icons to the left of the :guilabel:`Year` button. The calendar view adjusts in increments of the presented view." msgstr "" -#: ../../content/applications/hr/time_off.rst:647 -msgid "For example, if :guilabel:`Week` is selected, the arrows adjust the view by one week." +#: ../../content/applications/hr/time_off.rst:811 +msgid "For example, if :guilabel:`Year` is selected, the arrows adjust the view by one year." msgstr "" -#: ../../content/applications/hr/time_off.rst:649 +#: ../../content/applications/hr/time_off.rst:813 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:652 -msgid "Above the calendar view is a summary of the users time off balances. Every time off type that has been allocated appears in its own summary box. Each summary lists the type of time off, the corresponding icon, the current available balance (in hours or days), and an expiration date (if applicable)." +#: ../../content/applications/hr/time_off.rst:816 +msgid "Above the calendar view is a summary of the user's 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:657 -msgid "The legend on the right side of the calendar view displays the various time off types, with their corresponding colors. The status of the time off requests are shown as well." +#: ../../content/applications/hr/time_off.rst:821 +msgid "To view the full details of a time off balance, click the :guilabel:`? (question mark)` icon at the end of the :guilabel:`(DAYS/HOURS) AVAILABLE` on the time off summary. The complete details are presented in a popover window, including the :guilabel:`Allocated` time, future :guilabel:`Accrual` time, :guilabel:`Approved` time off scheduled, :guilabel:`Planned` time off, and the currently :guilabel:`Available` time off." msgstr "" -#: ../../content/applications/hr/time_off.rst:660 -msgid "Time off that has been validated appears in a solid color (in the color specified in the Time Off Types part of the legend). Time off requests that still need to be approved appear with white stripes in the color. Refused time off requests have a colored line through the dates." +#: ../../content/applications/hr/time_off.rst:-1 +msgid "A view of the complete time off balance details in the popover window." msgstr "" -#: ../../content/applications/hr/time_off.rst:664 -msgid "New time off requests can be made from the dashboard. Click the :guilabel:`New Time Off` button at the top of the dashboard, and a new :ref:`time off form ` appears." +#: ../../content/applications/hr/time_off.rst:831 +msgid "A user is also able to see how much time off they will have accrued in the future. On the right side of the time off summary blocks, there is a :guilabel:`Balance at the (date)` field. Click on the date, and a calendar selector popover appears." msgstr "" -#: ../../content/applications/hr/time_off.rst:667 -msgid "New allocation requests can also be made from the dashboard. Click the :guilabel:`Allocation Request` button at the top of the dashboard to request more time off, and a new :ref:`allocation form ` appears." +#: ../../content/applications/hr/time_off.rst:835 +msgid "The current date is the default date selected. Navigate to the desired date, and Odoo displays the time off balances the user will have on that date. This takes into account all time off currently planned and approved. To return to the current date, click the :guilabel:`Today` button to the right of the date field." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:840 +msgid "On the right side of the calendar, the various time off types are displayed, with their corresponding colors. The :guilabel:`Legend` explains how the various statuses for time off requests are presented." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:844 +msgid "Time off that has been validated appears in a solid color (in the color specified in the :guilabel:`Time Off Type` section above the :guilabel:`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:849 +msgid "New time off requests can be made from the dashboard. Click the :guilabel:`New` button at the top of the dashboard, and a :ref:`New Time Off ` modal appears." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:852 +msgid "New allocation requests can also be made from the dashboard. Click the :guilabel:`New Allocation Request` button at the top of the dashboard to request more time off, and a :ref:`New Allocation ` modal 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:678 -msgid "To view a list of all the user's time off requests, navigate to :menuselection:`Time Off app --> My Time Off --> My Time Off`. Here, all time off requests appear in a list view, both past and present." +#: ../../content/applications/hr/time_off.rst:863 +msgid "My time off" msgstr "" -#: ../../content/applications/hr/time_off.rst:682 -msgid "Other than the employee's name, the list includes the following information for each request: the :guilabel:`Time Off Type`, :guilabel:`Description`, :guilabel:`Start Date`, :guilabel:`End Date`, :guilabel:`Duration`, and the :guilabel:`Status`." +#: ../../content/applications/hr/time_off.rst:865 +msgid "To view a list of all the user's time off requests, navigate to :menuselection:`Time Off app --> My Time --> My Time Off`. Here, all time off requests, both past and present, appear in a list view." msgstr "" -#: ../../content/applications/hr/time_off.rst:686 -msgid "A new time off request can be made from this view. Click the :guilabel:`Create` button to :ref:`request time off `." +#: ../../content/applications/hr/time_off.rst:868 +msgid "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:690 +#: ../../content/applications/hr/time_off.rst:872 +msgid "A new time off request can be made from this view. Click the :guilabel:`New` button to :ref:`request time off `." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:878 msgid "My allocations" msgstr "" -#: ../../content/applications/hr/time_off.rst:692 -msgid "To view a list of all the users allocations, navigate to :menuselection:`Time Off app --> My Time Off --> My Allocations`. All allocations and requested allocations appear in a list view." +#: ../../content/applications/hr/time_off.rst:880 +msgid "To view a list of all the user's allocations, navigate to :menuselection:`Time Off app --> My Time --> My Allocations`. All allocations and requested allocations appear in a list view." msgstr "" -#: ../../content/applications/hr/time_off.rst:695 -msgid "The information presented includes: the :guilabel:`Time Off Type`, :guilabel:`Description`, :guilabel:`Duration`, :guilabel:`Allocation Type`, and the :guilabel:`Status`." +#: ../../content/applications/hr/time_off.rst:883 +msgid "The information presented on the :guilabel:`My Allocations` page includes: the :guilabel:`Time Off Type`, :guilabel:`Description`, :guilabel:`Amount`, :guilabel:`Allocation Type`, and :guilabel:`Status`." msgstr "" -#: ../../content/applications/hr/time_off.rst:698 -msgid "A new allocation request can be made from this view, as well. Click the :guilabel:`Create` button to :ref:`request an allocation `." +#: ../../content/applications/hr/time_off.rst:887 +msgid "A new allocation request can be made from this view, as well. Click the :guilabel:`New` button to :ref:`request an allocation `." msgstr "" -#: ../../content/applications/hr/time_off.rst:704 +#: ../../content/applications/hr/time_off.rst:895 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:709 +#: ../../content/applications/hr/time_off.rst:899 +msgid "Any report can be added to a spreadsheet through the *Insert in Spreadsheet* button that appears in the top-left of a report. If the *Documents* application is installed, an option to add the report to a spreadsheet appears. If not, the report can be added to a *Dashboard*." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:904 msgid "By employee" msgstr "" -#: ../../content/applications/hr/time_off.rst:711 +#: ../../content/applications/hr/time_off.rst:906 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:714 -msgid "The default report is a stacked bar chart with the filters of :guilabel:`Active Employee` and :guilabel:`Type` in place." +#: ../../content/applications/hr/time_off.rst:909 +msgid "The default report presents the current year's data in a list view, displaying all the employees in alphabetical order. Each employee's line is collapsed by default. To expand a line, click anywhere on the line." msgstr "" -#: ../../content/applications/hr/time_off.rst:717 -msgid "Each employee is displayed in their own column, with the bar displaying how many days of each type of time off type they requested." +#: ../../content/applications/hr/time_off.rst:913 +msgid "The view expands, and has the time off requests organized by time off type. Click anywhere on a time off type line to expand it, and view all the individual time off requests that fall under that type." msgstr "" -#: ../../content/applications/hr/time_off.rst:720 -msgid "The report can be displayed in other ways. Click the various options at the top of the report to view the data differently." -msgstr "" - -#: ../../content/applications/hr/time_off.rst:723 -msgid "The graph options are :guilabel:`Bar Chart`, :guilabel:`Line Chart`, or :guilabel:`Pie Chart`. The :guilabel:`Bar Chart` includes an option to present the data :guilabel:`Stacked`. Both the :guilabel:`Bar Chart` and :guilabel:`Line Chart` have options to present the data in either :guilabel:`Descending` or :guilabel:`Ascending` order." +#: ../../content/applications/hr/time_off.rst:916 +msgid "The information shown in the list includes: the :guilabel:`Employee` name, :guilabel:`Number of Days` off requested, the :guilabel:`Start Date`, :guilabel:`End Date`, :guilabel:`Status`, and :guilabel:`Description`." msgstr "" #: ../../content/applications/hr/time_off.rst:-1 -msgid "Report of time off, shown by each employee in a stacked bar chart." +msgid "Report of time off, shown by each employee in a list view." msgstr "" -#: ../../content/applications/hr/time_off.rst:733 +#: ../../content/applications/hr/time_off.rst:924 +msgid "The report can be displayed in other ways, as well. Click the corresponding button option in the top-right corner of the page to view the data in that specific way. The various options are a :guilabel:`List` (the default view), :guilabel:`Graph`, :guilabel:`Pivot` table, or :guilabel:`Calendar` view." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:-1 +msgid "The various other views highlighted, for the employee time off report." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:933 +#: ../../content/applications/hr/time_off.rst:960 +msgid "When a selection has been made, additional options appear for that particular selection. For more detailed information on the reports and their various options, refer to the :doc:`reporting <../essentials/reporting>` documentation." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:938 msgid "By type" msgstr "" -#: ../../content/applications/hr/time_off.rst:735 -msgid "To view a list of approved time off, organized by time off type, navigate to :menuselection:`Time Off app --> Reporting --> by Type`. This shows each time off type in its own section." +#: ../../content/applications/hr/time_off.rst:940 +msgid "To view a list of all time off, organized by time off type, navigate to :menuselection:`Time Off app --> Reporting --> by Type`. This shows all time off requests in a default bar chart." msgstr "" -#: ../../content/applications/hr/time_off.rst:738 -msgid "Click on a time off type to expand the list. Each request is listed, with the following information displayed: the :guilabel:`Employee`, :guilabel:`Number of Days`, :guilabel:`Request Type`, :guilabel:`Start Date`, :guilabel:`End Date`, :guilabel:`Status`, and the :guilabel:`Description`." -msgstr "" - -#: ../../content/applications/hr/time_off.rst:742 -msgid "The default filters in place for this report are :guilabel:`Approved Requests`, :guilabel:`Active Employee`, the :guilabel:`Current Year`, and the :guilabel:`Type`." +#: ../../content/applications/hr/time_off.rst:943 +msgid "Hover over a bar to view the :guilabel:`Duration (Days)` of that specific time off type." msgstr "" #: ../../content/applications/hr/time_off.rst:-1 -msgid "Report of time off by type, with each request detailed in the list." +msgid "The various time off types, and how many days requested, in a bar chart. Details are\n" +"highlighted in a red box." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:950 +msgid "Click on a bar to go to a detailed list view of all the time off requests for that time off type." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:952 +msgid "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:956 +msgid "The report can be displayed in other ways, as well. Click the corresponding button option in the top-right corner of the page to view the data in that way. The various options are a :guilabel:`Graph` (the default view), :guilabel:`List`, or :guilabel:`Pivot` table." msgstr "" diff --git a/locale/sources/inventory_and_mrp.pot b/locale/sources/inventory_and_mrp.pot index 0e3eced03..5a2250c41 100644 --- a/locale/sources/inventory_and_mrp.pot +++ b/locale/sources/inventory_and_mrp.pot @@ -8,7 +8,7 @@ msgid "" msgstr "" "Project-Id-Version: Odoo 17.0\n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2024-03-25 16:01+0000\n" +"POT-Creation-Date: 2024-04-30 09:16+0000\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME \n" "Language-Team: LANGUAGE \n" @@ -29,7 +29,7 @@ msgid "**Odoo Barcode** allows users to assign barcodes to individual products a msgstr "" #: ../../content/applications/inventory_and_mrp/barcode.rst:15 -msgid "`Odoo Tutorials: Barcode Basics `_" +msgid "`Odoo Tutorials: Barcode `_" msgstr "" #: ../../content/applications/inventory_and_mrp/barcode/operations.rst:5 @@ -1139,11 +1139,12 @@ msgstr "" #: ../../content/applications/inventory_and_mrp/barcode/setup/software.rst:14 #: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/strategies.rst:53 #: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/uom.rst:21 +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/create_sn.rst:33 #: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/package.rst:38 #: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/packaging.rst:13 -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/invoicing.rst:18 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/invoicing.rst:19 #: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/label_type.rst:13 -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/labels.rst:15 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/labels.rst:12 #: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/multipack.rst:11 #: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/delivery_three_steps.rst:18 #: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_three_steps.rst:16 @@ -1153,22 +1154,27 @@ msgstr "" #: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/reservation_methods/manually.rst:19 #: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/delivery_method.rst:17 #: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/starshipit_shipping.rst:104 -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/third_party_shipper.rst:16 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/third_party_shipper.rst:49 #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/batch_transfers.rst:22 #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/cluster_picking.rst:48 #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/cross_dock.rst:18 #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/putaway.rst:21 #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/putaway.rst:104 #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/wave_transfers.rst:16 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/cycle_counts.rst:15 #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/resupply_warehouses.rst:11 #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/warehouses_locations.rst:44 -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/integrating_landed_costs.rst:11 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/integrating_landed_costs.rst:20 #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/removal_strategies.rst:45 -#: ../../content/applications/inventory_and_mrp/manufacturing/management/subcontracting.rst:23 -#: ../../content/applications/inventory_and_mrp/manufacturing/management/use_mps.rst:11 -#: ../../content/applications/inventory_and_mrp/manufacturing/management/work_center_time_off.rst:15 -#: ../../content/applications/inventory_and_mrp/manufacturing/management/work_order_dependencies.rst:13 -#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/control_bills.rst:10 +#: ../../content/applications/inventory_and_mrp/manufacturing/advanced_configuration/work_order_dependencies.rst:13 +#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/subcontracting.rst:32 +#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/subcontracting_basic.rst:23 +#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/subcontracting_dropship.rst:41 +#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/subcontracting_resupply.rst:40 +#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/use_mps.rst:11 +#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/work_center_time_off.rst:15 +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/calls_for_tenders.rst:26 +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/control_bills.rst:17 #: ../../content/applications/inventory_and_mrp/purchase/products/temporary_reordering.rst:31 msgid "Configuration" msgstr "" @@ -2733,105 +2739,6 @@ msgstr "" msgid "If multiple routes are enabled for a product but no preferred route is set for its reordering rule, the product is reordered using the selected route that is listed first on the :guilabel:`Inventory` tab of the product form." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/scrap_inventory.rst:3 -msgid "Scrap inventory" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/scrap_inventory.rst:5 -msgid "In some cases, a product in inventory may be damaged or found to be defective. If it is not possible to repair or return the product, Odoo *Inventory* allows users to scrap it, ensuring that usable inventory counts remain accurate." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/scrap_inventory.rst:10 -#: ../../content/applications/inventory_and_mrp/manufacturing/management/scrap_manufacturing.rst:25 -msgid "Scrap orders can be viewed by navigating to :menuselection:`Inventory --> Operations --> Scrap`. Each scrap order shows the date and time the order was created, along with the product and quantity that was scrapped." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/scrap_inventory.rst:14 -msgid "To view the total quantity of each item scrapped, navigate to :menuselection:`Inventory --> Configuration --> Locations`. Remove the :guilabel:`Internal` filter from the :guilabel:`Search...` bar to display virtual locations. Finally, select the :guilabel:`Virtual Locations/Scrap` location." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/scrap_inventory.rst:19 -msgid "By default, scrapping a product removes it from physical inventory, and places it in a virtual location titled *Virtual Locations/Scrap*. A virtual location is **not** a physical space, but rather a designation in Odoo that is used to track items that are no longer in physical inventory." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/scrap_inventory.rst:23 -#: ../../content/applications/inventory_and_mrp/manufacturing/management/configure_manufacturing_product.rst:68 -#: ../../content/applications/inventory_and_mrp/manufacturing/management/work_order_dependencies.rst:30 -msgid "Learn more" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/scrap_inventory.rst:25 -msgid "For more information about virtual locations, see the documentation about the different types of :ref:`locations `." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/scrap_inventory.rst:29 -msgid "Scrap from stock" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/scrap_inventory.rst:31 -msgid "To scrap a product located in inventory, begin by navigating to :menuselection:`Inventory --> Operations --> Scrap`. On the :guilabel:`Scrap Orders` page, click :guilabel:`Create` to configure a new scrap order." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/scrap_inventory.rst:35 -msgid "On the scrap order, select the product being scrapped from the :guilabel:`Product` drop-down menu, then enter the quantity in the :guilabel:`Quantity` field. The :guilabel:`Source Location` defaults to the location where the product is stored, and the :guilabel:`Scrap Location` defaults to :guilabel:`Virtual Locations/Scrap`, but either of these can be changed by selecting a different location from their respective drop-down menus." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/scrap_inventory.rst:-1 -msgid "A new scrap order." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/scrap_inventory.rst:45 -msgid "Finally, click :guilabel:`Validate` to scrap the product. The on-hand inventory count for the scrapped product updates to subtract the scrapped quantity." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/scrap_inventory.rst:49 -msgid "Scrap from a receipt, transfer, or delivery" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/scrap_inventory.rst:51 -msgid "It is also possible to scrap products during the receipt, transfer, and delivery operations. This can be necessary if any products are found to be defective when receiving them into inventory, transferring them from one location to another, or preparing them for delivery." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/scrap_inventory.rst:55 -msgid "To scrap a product during the receipt, transfer, or delivery operations, begin by navigating to the :menuselection:`Inventory` app. On the :guilabel:`Overview` page, select the :guilabel:`# TO PROCESS` button on the :guilabel:`Receipts`, :guilabel:`Internal Transfers`, or :guilabel:`Delivery Orders` card, depending on the type of operation the product is being scrapped from." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/scrap_inventory.rst:61 -msgid "For the :guilabel:`Internal Transfers` card to appear on the :menuselection:`Overview` page of the :menuselection:`Inventory` app, the :guilabel:`Storage Locations` setting must be enabled. To do so, navigate to :menuselection:`Configuration --> Settings`, then enable the checkbox next to :guilabel:`Storage Locations` under the :guilabel:`Warehouse` heading." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/scrap_inventory.rst:66 -msgid "Alternatively, a list of all delivery orders, receipts, and transfers can be viewed by navigating to :menuselection:`Inventory --> Operations --> Transfers`." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/scrap_inventory.rst:69 -msgid "Next, open a delivery order, receipt, or transfer from the corresponding page by clicking on it. A :guilabel:`Scrap` button appears at the top of the page. Click it to open the :guilabel:`Scrap` pop-up window." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/scrap_inventory.rst:-1 -msgid "The scrap pop-up in the Inventory app." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/scrap_inventory.rst:78 -msgid "The :guilabel:`Scrap` button will only appear on a receipt that has been validated. This is because Odoo only allows products to be scrapped once they have been entered into inventory." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/scrap_inventory.rst:81 -msgid "On the :guilabel:`Scrap` pop-up window, select the product being scrapped from the :guilabel:`Product` drop-down menu. Then, enter the quantity in the :guilabel:`Quantity` field." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/scrap_inventory.rst:84 -msgid "The :guilabel:`Source Location` defaults to the location where the product is stored, and the :guilabel:`Scrap Location` defaults to :guilabel:`Virtual Locations/Scrap`, but either of these can be changed by selecting a different location from their respective drop-down menus." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/scrap_inventory.rst:88 -msgid "Finally, click :guilabel:`Done` to scrap the product. After doing so, the :guilabel:`Scrap` pop-up window disappears and a :guilabel:`Scraps` smart button appears in the top right of the page. Click it to view all of the scrap orders created from that operation." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/scrap_inventory.rst:-1 -msgid "The Scraps smart button." -msgstr "" - #: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/strategies.rst:3 msgid "Selecting a replenishment strategy" msgstr "" @@ -3255,6 +3162,233 @@ msgstr "" msgid "Product tracking" msgstr "" +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/create_sn.rst:3 +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/create_sn.rst:98 +msgid "Assign serial numbers" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/create_sn.rst:5 +msgid "Assigning serial numbers to individual products allows the for tracking of properties, :doc:`expiration dates `, and location throughout the supply chain, which particularly benefits manufacturers providing after-sales services." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/create_sn.rst:10 +msgid "`Odoo Tutorials: Serial Numbers `_" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/create_sn.rst:11 +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/differences.rst:18 +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/lots.rst:19 +msgid ":doc:`serial_numbers`" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/create_sn.rst:13 +msgid "In Odoo, serial numbers are assigned to products:" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/create_sn.rst:15 +msgid "in the :ref:`Detailed Operations page ` on a receipt" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/create_sn.rst:17 +msgid "by clicking the :ref:`Assign Serial Numbers ` button on a receipt" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/create_sn.rst:19 +msgid "in the :ref:`Open: Stock move window ` on a receipt" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/create_sn.rst:21 +msgid "when closing a manufacturing order" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/create_sn.rst:22 +msgid "when making an inventory adjustment" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/create_sn.rst:30 +msgid "Display the Detailed Operations smart button and bulleted list icon on a receipt." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/create_sn.rst:30 +msgid "Display the **Detailed Operations** smart button and bulleted list icon on a receipt." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/create_sn.rst:35 +msgid "To assign serial numbers to products, activate the :guilabel:`Lots and Serial Numbers` feature in :menuselection:`Inventory app --> Configuration --> Settings`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/create_sn.rst:38 +msgid "Then, in the :guilabel:`Inventory` tab of an item's product form, set the :guilabel:`Tracking` field to :guilabel:`By Unique Serial Number`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/create_sn.rst:42 +msgid ":ref:`Enable serial numbers `" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/create_sn.rst:43 +msgid ":ref:`Track products by serial numbers `" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/create_sn.rst:47 +msgid "Next, enable creating new serial numbers by going to :menuselection:`Inventory app --> Configuration --> Operations Types`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/create_sn.rst:50 +msgid "From the :guilabel:`Operations Types` page, select the desired operation type (e.g. :guilabel:`Receipts`, :guilabel:`Delivery Orders`, or :guilabel:`Manufacturing`), and select the :guilabel:`Create New` option in the :guilabel:`Lots/Serial Numbers` section of the operation type's configuration page." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/create_sn.rst:-1 +msgid "Show \"Create New\" option is selected on the Receipts operation type." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/create_sn.rst:62 +msgid "Detailed Operations" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/create_sn.rst:64 +msgid "Serial numbers can be assigned to products when entering stock for the first time, from the :guilabel:`Detailed Operations` page on the receipt. Receipts can be accessed by navigating to :menuselection:`Inventory app --> Operations --> Receipts`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/create_sn.rst:69 +msgid "Serial numbers can **not** be assigned to products on a request for quotation (RfQ) or purchase order (PO) — **only** on a receipt." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/create_sn.rst:0 +msgid "Show the purchase order and the Receipt smart button" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/create_sn.rst:76 +msgid "Screenshot of a \"Purchase Order\" with the \"Receipt\" smart button at the top." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/create_sn.rst:78 +msgid "To record an item's serial number before receiving the item, follow the steps in the next sections to assign serial numbers, but do **not** click the receipt's :guilabel:`Validate` button, until the products are received from the vendor." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/create_sn.rst:82 +msgid "Assign a single serial number to a product by clicking the :guilabel:`Detailed Operations` smart button on a receipt." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/create_sn.rst:85 +msgid "In the :guilabel:`Lot/Serial Number Name` column, manually type in the serial number for a single product." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/create_sn.rst:-1 +msgid "Add a line on the Detailed Operations page to assign serial numbers." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/create_sn.rst:92 +msgid "When finished, click the receipt's breadcrumbs, and the assigned serial numbers are automatically saved." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/create_sn.rst:100 +msgid "To generate new serial numbers in a sequence, click the :guilabel:`+ (plus)` icon in the :ref:`product line `." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/create_sn.rst:-1 +msgid "Show the plus icon in the product line." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/create_sn.rst:108 +msgid "If the icon is not visible, ensure the :guilabel:`Create New` option is selected in the :ref:`receipt's configuration page `." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/create_sn.rst:111 +msgid "Doing so opens the :guilabel:`Assign Serial Numbers` pop-up window. The :guilabel:`Number of SN` field is auto-filled based on the product quantity requiring serial numbers. Manually input the first serial number in the :guilabel:`First SN` field, and click :guilabel:`Assign Serial Numbers` to generate a sequence of serial numbers based on the first serial number entered." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/create_sn.rst:-1 +msgid "Show Assign Serial numbers pop-up." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/create_sn.rst:123 +msgid "Stock move pop-up window" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/create_sn.rst:125 +msgid "For various methods of assigning serial numbers in bulk, click the :guilabel:`⦙≣ (bulleted list)` icon in the :ref:`product line ` of a receipt." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/create_sn.rst:130 +msgid "Add a line" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/create_sn.rst:132 +msgid "In the :guilabel:`Open: Stock move` pop-up window that appears, manually input the serial numbers in the :guilabel:`Lot/Serial Number` column." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/create_sn.rst:-1 +msgid "Add a line on the Stock move pop-up." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/create_sn.rst:140 +msgid "Generate Serials" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/create_sn.rst:142 +msgid "Assign multiple serial numbers at once by clicking the :guilabel:`Generate Serials/Lots` button in the :guilabel:`Open: Stock move` pop-up window." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/create_sn.rst:-1 +msgid "Show generate serials button." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/create_sn.rst:149 +msgid "Doing so opens the :guilabel:`Generate Serial numbers` pop-up window, where the first serial number is entered in the :guilabel:`First SN` field to generate a sequence of serial numbers, based on the first serial number entered." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/create_sn.rst:153 +msgid "For more details on how to fill in this pop-up window, :ref:`refer to this section `." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/create_sn.rst:157 +msgid "Import Serials" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/create_sn.rst:159 +msgid "Assign multiple serial numbers at once by clicking the :guilabel:`Import Serials/Lots` button in the :guilabel:`Open: Stock move` pop-up window." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/create_sn.rst:163 +msgid "If the button is not visible, ensure the :guilabel:`Create New` option is selected in the :ref:`receipt's configuration page `." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/create_sn.rst:166 +msgid "Doing so opens the :guilabel:`Import Lots` pop-up window. Enter each serial number on a separate line in the :guilabel:`Lots/Serial numbers` text field." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/create_sn.rst:170 +msgid "Copy/paste serial numbers from an existing excel spreadsheet and add them to the :guilabel:`Lots/Serial numbers` text field." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/create_sn.rst:0 +msgid "Show excel sheet to copy serial numbers from." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/create_sn.rst:177 +msgid "Tick the :guilabel:`Keep current lines` checkbox to add serial numbers to the list of products, and serial numbers in the :guilabel:`Lot/Serial Number` table, in the :guilabel:`Open: Stock move` pop-up window. To replace the serial numbers in the list, leave the :guilabel:`Keep current lines` option unchecked." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/create_sn.rst:182 +msgid "Finally, click :guilabel:`Generate`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/create_sn.rst:185 +msgid "For a receipt with a :guilabel:`Demand` of `3.00` products, one product has already been assigned a serial number in the :guilabel:`Open: Stock move` pop-up window." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/create_sn.rst:188 +msgid "So, in the :guilabel:`Import Lots` pop-up window, two serial numbers, `124` and `125` are assigned to the remaining products by entering the following in the :guilabel:`Lots/Serial numbers` input field:" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/create_sn.rst:197 +msgid "The :guilabel:`Keep current lines` option is selected to add these two serial numbers **in addition** to the serial number, `123`, that has already been assigned." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/create_sn.rst:0 +msgid "Show example of correctly inputting serial numbers in the text field." +msgstr "" + #: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/differences.rst:3 msgid "Difference between lots and serial numbers" msgstr "" @@ -3275,14 +3409,9 @@ msgstr "" msgid ":doc:`lots`" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/differences.rst:18 -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/lots.rst:19 -msgid ":doc:`serial_numbers`" -msgstr "" - #: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/differences.rst:21 #: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/lots.rst:22 -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/serial_numbers.rst:20 +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/serial_numbers.rst:22 msgid "Enable lots & serial numbers" msgstr "" @@ -3332,7 +3461,6 @@ msgid "Serial numbers can contain many different types of characters: numbers, l msgstr "" #: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/differences.rst:67 -#: ../../content/applications/inventory_and_mrp/manufacturing/management/subcontracting.rst:114 msgid "Traceability" msgstr "" @@ -3729,7 +3857,7 @@ msgid "A detailed description of this specific lot or serial number can also be msgstr "" #: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/lots.rst:80 -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/serial_numbers.rst:81 +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/serial_numbers.rst:83 msgid "When all desired configurations are complete, click the :guilabel:`Save` button to save all changes." msgstr "" @@ -3842,7 +3970,7 @@ msgid "On this blank quotation form, fill out the necessary information by addin msgstr "" #: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/lots.rst:185 -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/serial_numbers.rst:221 +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/serial_numbers.rst:195 msgid "Then, choose the desired quantity to sell by changing the number in the :guilabel:`Quantity` column." msgstr "" @@ -3851,13 +3979,12 @@ msgid "Once the quotation has been filled out, click the :guilabel:`Confirm` but msgstr "" #: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/lots.rst:191 -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/serial_numbers.rst:227 +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/serial_numbers.rst:201 msgid "Click the :guilabel:`Delivery` smart button to view the warehouse receipt form for that specific :abbr:`SO (sales order)`." msgstr "" #: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/lots.rst:194 -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/serial_numbers.rst:132 -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/serial_numbers.rst:230 +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/serial_numbers.rst:204 msgid "From here, click the :guilabel:`Additional Options` menu, represented by a `hamburger` icon (four horizontal lines, located to the right of the :guilabel:`Unit of Measure` column in the :guilabel:`Operations` tab). Clicking that icon reveals a :guilabel:`Detailed Operations` pop-up." msgstr "" @@ -4328,7 +4455,7 @@ msgstr "" msgid ":doc:`/applications/inventory_and_mrp/inventory/product_management/product_tracking/lots`" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/serial_numbers.rst:22 +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/serial_numbers.rst:24 msgid "To track products using serial numbers, the :guilabel:`Lots & Serial Numbers` feature must be enabled. To enable this, go to :menuselection:`Inventory app --> Configuration --> Settings`, scroll down to the :guilabel:`Traceability` section, and click the box next to :guilabel:`Lots & Serial Numbers`. Remember to click the :guilabel:`Save` button to save changes." msgstr "" @@ -4336,19 +4463,19 @@ msgstr "" msgid "Enabled lots and serial numbers setting." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/serial_numbers.rst:34 +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/serial_numbers.rst:36 msgid "Configure serial number tracking on products" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/serial_numbers.rst:36 +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/serial_numbers.rst:38 msgid "Once the :guilabel:`Lots & Serial Numbers` setting has been activated, individual products can now be tracked using serial numbers. To configure this, go to :menuselection:`Inventory app --> Products --> Products`, and choose a desired product to track." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/serial_numbers.rst:40 +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/serial_numbers.rst:42 msgid "Once on the product form, click :guilabel:`Edit`, and click the :guilabel:`Inventory` tab." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/serial_numbers.rst:42 +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/serial_numbers.rst:44 msgid "Once on the product form, click :guilabel:`Edit`, navigate to the :guilabel:`Inventory` tab, and scroll to the :guilabel:`Traceability` section. Then, select the :guilabel:`By Unique Serial Number` option, and click :guilabel:`Save` to save the changes. Existing or new serial numbers can now be selected and assigned to newly-received or manufactured batches of this product." msgstr "" @@ -4356,31 +4483,31 @@ msgstr "" msgid "Enabled serial number tracking on product form." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/serial_numbers.rst:52 +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/serial_numbers.rst:54 msgid "If a product doesn't have a serial number assigned to it, a user error pop-up window will appear. The error message states that the product(s) in stock have no lot/serial number. However, a lot/serial number can be assigned to the product by making an inventory adjustment." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/serial_numbers.rst:57 +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/serial_numbers.rst:59 msgid "Create new serial numbers for products already in stock" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/serial_numbers.rst:59 +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/serial_numbers.rst:61 msgid "New serial numbers can be created for products already in stock with no assigned serial number. To do this, go to :menuselection:`Inventory --> Products --> Lots/Serial Numbers`, and click :guilabel:`Create`. Doing so reveals a blank lots/serial numbers form. On this form, a new :guilabel:`Lot/Serial Number` is generated automatically." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/serial_numbers.rst:65 +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/serial_numbers.rst:67 msgid "While Odoo automatically generates a new lot/serial number to follow the most recent number, it can be edited and changed to any desired number, by clicking the line under the :guilabel:`Lot/Serial Number` field, and changing the generated number." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/serial_numbers.rst:69 +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/serial_numbers.rst:71 msgid "Once the :guilabel:`Lot/Serial Number` is generated, click the blank field next to :guilabel:`Product` to reveal a drop-down menu. From this menu, select the product to which this new number will be assigned." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/serial_numbers.rst:73 +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/serial_numbers.rst:75 msgid "This form also provides the option to adjust the :guilabel:`Quantity`, to assign a unique :guilabel:`Internal Reference` number (for traceability purposes), and to assign this specific lot/serial number configuration to a specific website in the :guilabel:`Website` field (if working in a multi-website environment)." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/serial_numbers.rst:78 +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/serial_numbers.rst:80 msgid "A detailed description of this specific lot/serial number can also be added in the :guilabel:`Description` tab below." msgstr "" @@ -4388,99 +4515,67 @@ msgstr "" msgid "New serial number created for existing product stock." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/serial_numbers.rst:87 +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/serial_numbers.rst:89 msgid "After a new serial number has been created, assigned to the desired product, and saved, navigate back to the product form, by going to :menuselection:`Products --> Products`, and selecting the product that this newly-created serial number was just assigned to." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/serial_numbers.rst:91 +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/serial_numbers.rst:93 msgid "On that product's detail form, click the :guilabel:`Lot/Serial Numbers` smart button to view the new serial number." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/serial_numbers.rst:95 +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/serial_numbers.rst:97 msgid "Manage serial numbers for shipping and receiving" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/serial_numbers.rst:97 +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/serial_numbers.rst:99 msgid "Serial numbers can be assigned for both **incoming** and **outgoing** goods. For incoming goods, serial numbers are assigned directly on the purchase order form. For outgoing goods, serial numbers are assigned directly on the sales order form." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/serial_numbers.rst:102 -msgid "Manage serial numbers on receipts" -msgstr "" - #: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/serial_numbers.rst:104 -msgid "Assigning serial numbers to **incoming** goods can be done directly from the purchase order (PO)." +msgid "Assign serial numbers to newly received products" msgstr "" #: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/serial_numbers.rst:106 -msgid "To create a :abbr:`PO (purchase order)`, go to the :menuselection:`Purchase app --> Create`. Doing so reveals a new, blank request for quotation (RFQ) form." +msgid "Assigning serial numbers to **incoming** goods can be done on the receipt, by clicking the :ref:`Detailed Operations smart button ` or by clicking the :guilabel:`⦙≣ (bulleted list)` icon in the product line." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/serial_numbers.rst:109 -msgid "On this :abbr:`RFQ (request for quotation)` form, fill out the necessary information, by adding a :guilabel:`Vendor`, and by adding the desired products to the :guilabel:`Product` lines, by clicking :guilabel:`Add a product`, under the :guilabel:`Products` tab." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/serial_numbers.rst:113 -msgid "Choose the desired quantity of the product to order, by changing the number in the :guilabel:`Quantity` column." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/serial_numbers.rst:116 -msgid "When the necessary configurations are complete, click :guilabel:`Confirm Order`. This will convert the :abbr:`RFQ (request for quotation)` to a purchase order." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/serial_numbers.rst:119 -msgid "Then, click the :guilabel:`Receipt` smart button to be taken to the warehouse receipt form page for that specific :abbr:`PO (purchase order)`." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/serial_numbers.rst:123 -msgid "Clicking :guilabel:`Validate` before assigning a serial number to the ordered product quantities will cause a :guilabel:`User Error` pop-up to appear. The pop-up requires entry of a lot or serial number for the ordered products. The :abbr:`RFQ (request for quotation)` **cannot** be validated without a serial number being assigned." +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/serial_numbers.rst:111 +msgid ":doc:`create_sn`" msgstr "" #: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/serial_numbers.rst:-1 +msgid "Display the bulleted list icon and Detailed Operations smart buttons." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/serial_numbers.rst:118 +msgid "Clicking :guilabel:`Validate` before assigning a serial number to received quantities will cause a :guilabel:`User Error` pop-up to appear. The pop-up requires entry of a lot or serial number for the ordered products. The :abbr:`RFQ (request for quotation)` **cannot** be validated without a serial number being assigned." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/serial_numbers.rst:0 msgid "User error popup prompting serial number entry." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/serial_numbers.rst:136 -msgid "In this pop-up, configure a number of different fields, including the assignation of a serial number (or serial numbers) under the :guilabel:`Lot/Serial Number Name` column, located at the bottom of the pop-up." +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/serial_numbers.rst:127 +msgid "There are multiple ways to do this: manually assigning serial numbers, automatically assigning serial numbers, and copy/pasting serial numbers from a spreadsheet." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/serial_numbers.rst:140 -msgid "There are three ways to do this: manually assigning serial numbers, automatically assigning serial numbers, and copy/pasting serial numbers from a spreadsheet." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/serial_numbers.rst:144 -msgid "Assign serial numbers manually" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/serial_numbers.rst:146 -msgid "To assign serial numbers manually, click :guilabel:`Add a line` from the :guilabel:`Detailed Operations` pop-up, and first choose the location where the product will be stored under the :guilabel:`To` column." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/serial_numbers.rst:150 -msgid "Then, type a new :guilabel:`Serial Number Name`, and set the :guilabel:`Done` quantity in the appropriate columns." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/serial_numbers.rst:153 -msgid "Repeat this process for the quantity of products shown in the :guilabel:`Demand` field, and until the :guilabel:`Quantity Done` field displays the correct (matching) number of products processed." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/serial_numbers.rst:157 +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/serial_numbers.rst:131 msgid "Assign serial numbers automatically" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/serial_numbers.rst:159 +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/serial_numbers.rst:133 msgid "If a large quantity of products need individual serial numbers assigned to them, Odoo can automatically generate and assign serial numbers to each of the individual products." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/serial_numbers.rst:162 +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/serial_numbers.rst:136 msgid "To accomplish this, start with the :guilabel:`First SN` field in the :guilabel:`Detailed Operations` pop-up window, and type the first serial number in the desired order to be assigned." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/serial_numbers.rst:165 +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/serial_numbers.rst:139 msgid "Then, in the :guilabel:`Number of SN` field, type the total number of items that need newly-generated unique serial numbers assigned to them." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/serial_numbers.rst:168 +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/serial_numbers.rst:142 msgid "Finally, click :guilabel:`Assign Serial Numbers`, and a list will populate with new serial numbers matching the ordered quantity of products." msgstr "" @@ -4488,15 +4583,15 @@ msgstr "" msgid "Automatic serial number assignment in detailed operations popup." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/serial_numbers.rst:176 +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/serial_numbers.rst:150 msgid "Copy/paste serial numbers from a spreadsheet" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/serial_numbers.rst:178 +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/serial_numbers.rst:152 msgid "To copy and paste serial numbers from an existing spreadsheet, first populate a spreadsheet with all of the serial numbers received from the supplier (or manually chosen 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." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/serial_numbers.rst:183 +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/serial_numbers.rst:157 msgid "From here, the :guilabel:`To` locations and :guilabel:`Done` quantities can be manually entered in each of the serial number lines." msgstr "" @@ -4504,47 +4599,47 @@ msgstr "" msgid "List of serial numbers copied in Excel spreadsheet." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/serial_numbers.rst:191 +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/serial_numbers.rst:165 msgid "For purchase orders that include large quantities of products to receive, the best method of serial number assignment is to automatically assign serial numbers using the :guilabel:`Assign Serial Numbers` button located on the :abbr:`PO (purchase order)`. This prevents any serial numbers from being reused or duplicated, and improves traceability reporting." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/serial_numbers.rst:196 +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/serial_numbers.rst:170 msgid "Once all product quantities have been assigned a serial number, click the :guilabel:`Confirm` button to close the pop-up. Then, click :guilabel:`Validate`." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/serial_numbers.rst:199 +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/serial_numbers.rst:173 msgid "A :guilabel:`Traceability` smart button appears upon validating the receipt. Click the :guilabel:`Traceability` smart button to see the updated :guilabel:`Traceability Report`, which includes: a :guilabel:`Reference` document, the :guilabel:`Product` being traced, the :guilabel:`Lot/Serial #`, and more." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/serial_numbers.rst:204 +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/serial_numbers.rst:178 msgid "Once all product quantities have been assigned a serial number, click :guilabel:`Confirm` to close the popup, and click :guilabel:`Validate`. A :guilabel:`Traceability` smart button will appear upon validating the receipt. Click the :guilabel:`Traceability` smart button to see the updated :guilabel:`Traceability Report`, which includes: a :guilabel:`Reference` document, the :guilabel:`Product` being traced, the :guilabel:`Lot/Serial #`, and more." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/serial_numbers.rst:211 +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/serial_numbers.rst:185 msgid "Manage serial numbers on delivery orders" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/serial_numbers.rst:213 +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/serial_numbers.rst:187 msgid "Assigning serial numbers to **outgoing** goods can be done directly from the sales order (SO)." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/serial_numbers.rst:215 +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/serial_numbers.rst:189 msgid "To create an :abbr:`SO (sales order)`, navigate to the :menuselection:`Sales` app, and click the :guilabel:`Create` button. Doing so reveals a new, blank quotation form. On this blank quotation form, fill out the necessary information, by adding a :guilabel:`Customer`, and adding products to the :guilabel:`Product` lines (in the :guilabel:`Order Lines` tab), by clicking :guilabel:`Add a product`." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/serial_numbers.rst:223 +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/serial_numbers.rst:197 msgid "Once the quotation has been filled out, click the :guilabel:`Confirm` button to confirm the quotation. When the quotation is confirmed, the quotation becomes an :abbr:`SO (sales order)`, and a :guilabel:`Delivery` smart button appears." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/serial_numbers.rst:234 +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/serial_numbers.rst:208 msgid "In the pop-up, a :guilabel:`Lot/Serial Number` will be chosen by default, with each product of the total :guilabel:`Reserved` quantity listed with their unique serial numbers (most likely listed in sequential order)." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/serial_numbers.rst:238 +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/serial_numbers.rst:212 msgid "To manually change a product's serial number, click the drop-down menu under :guilabel:`Lot/Serial Number`, and choose (or type) the desired serial number. Then, mark the :guilabel:`Done` quantities, and click :guilabel:`Confirm` to close the pop-up." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/serial_numbers.rst:242 +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/serial_numbers.rst:216 msgid "Finally, click the :guilabel:`Validate` button to deliver the products." msgstr "" @@ -4552,31 +4647,31 @@ msgstr "" msgid "Serial numbers listed in detailed operations popup." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/serial_numbers.rst:248 +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/serial_numbers.rst:222 msgid "Upon validating the delivery order, a :guilabel:`Traceability` smart button appears. Click the :guilabel:`Traceability` smart button to see the updated :guilabel:`Traceability Report`, which includes: a :guilabel:`Reference` document, the :guilabel:`Product` being traced, the :guilabel:`Date`, and the :guilabel:`Lot/Serial #` assigned." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/serial_numbers.rst:253 +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/serial_numbers.rst:227 msgid "The :guilabel:`Traceability Report` can also include a :guilabel:`Reference` receipt from the previous purchase order (PO), if any of the product quantities shared a serial number assigned during receipt of that specific :abbr:`PO (purchase order)`." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/serial_numbers.rst:258 +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/serial_numbers.rst:232 msgid "Manage serial numbers for different operations types" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/serial_numbers.rst:260 +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/serial_numbers.rst:234 msgid "By default in Odoo, the creation of new serial numbers is only allowed upon **receiving** products from a purchase order. **Existing** serial numbers cannot be used. For sales orders, the opposite is true: new serial numbers cannot be created on the delivery order, only existing serial numbers can be used." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/serial_numbers.rst:265 +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/serial_numbers.rst:239 msgid "To change the ability to use new (or existing) serial numbers on any operation type, go to :menuselection:`Inventory app --> Configuration --> Operations Types`, and select the desired :guilabel:`Operation Type`." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/serial_numbers.rst:269 +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/serial_numbers.rst:243 msgid "For the :guilabel:`Receipts` operation type, found on the :guilabel:`Operations Types` page, the :guilabel:`Use Existing Lots/Serial Numbers` option can be enabled, by selecting :guilabel:`Receipts` from the :guilabel:`Operations Types` page, clicking :guilabel:`Edit`, and then clicking the checkbox beside the :guilabel:`Use Existing Lots/Serial Numbers` option (in the :guilabel:`Traceability` section). Lastly, click the :guilabel:`Save` button to save the changes." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/serial_numbers.rst:275 +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/serial_numbers.rst:249 msgid "For the :guilabel:`Delivery Orders` operation type, located on the :guilabel:`Operations Types` page, the :guilabel:`Create New Lots/Serial Numbers` option can be enabled, by selecting :guilabel:`Delivery Orders` from the :guilabel:`Operations Types` page, clicking :guilabel:`Edit`, and clicking the checkbox beside the :guilabel:`Create New Lots/Serial Numbers` option (in the :guilabel:`Traceability` section). Be sure to click :guilabel:`Save` to save changes." msgstr "" @@ -4584,27 +4679,27 @@ msgstr "" msgid "Enabled traceability setting in operations type form." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/serial_numbers.rst:286 +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/serial_numbers.rst:260 msgid "Serial number traceability" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/serial_numbers.rst:288 +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/serial_numbers.rst:262 msgid "Manufacturers and companies can refer to the traceability reports to see the entire lifecycle of a product: where it came from (and when), where it was stored, and who it went to." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/serial_numbers.rst:291 +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/serial_numbers.rst:265 msgid "To see the full traceability of a product, or group by serial numbers, go to :menuselection:`Inventory app --> Products --> Lots/Serial Numbers`. Doing so reveals the :guilabel:`Lots/Serial Numbers` dashboard." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/serial_numbers.rst:295 +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/serial_numbers.rst:269 msgid "From here, products with serial numbers assigned to them will be listed by default, and can be expanded to show what serial numbers have been specifically assigned to them." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/serial_numbers.rst:298 +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/serial_numbers.rst:272 msgid "To group by serial numbers (or lots), first remove any default filters from the search bar in the upper-right corner. Then, click :guilabel:`Group By`, and select :guilabel:`Add Custom Group`, which reveals a mini drop-down menu. From this mini drop-down menu, select :guilabel:`Lot/Serial Number`, and click :guilabel:`Apply`." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/serial_numbers.rst:303 +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/serial_numbers.rst:277 msgid "Doing so reveals all existing serial numbers and lots, and can be expanded to show all quantities of products with that assigned number. For unique serial numbers that are not reused, there should be just one product per serial number." msgstr "" @@ -4612,11 +4707,11 @@ msgstr "" msgid "Serial numbers reporting page with drop-down lists." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/serial_numbers.rst:312 +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/serial_numbers.rst:286 msgid "For additional information regarding an individual serial number (or lot number), click the line item for the serial number to reveal that specific serial number's :guilabel:`Serial Number` form. From this form, click the :guilabel:`Location` and :guilabel:`Traceability` smart buttons to see all stock on-hand using that serial number, and any operations made using that serial number." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/serial_numbers.rst:319 +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/serial_numbers.rst:293 msgid ":doc:`/applications/inventory_and_mrp/inventory/product_management/product_tracking/differences`" msgstr "" @@ -4783,6 +4878,7 @@ msgstr "" #: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/type.rst:94 #: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/type.rst:163 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/integrating_landed_costs.rst:80 msgid "Create purchase order" msgstr "" @@ -4941,10 +5037,7 @@ msgid "How to cancel a shipping request to a shipper?" msgstr "" #: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/cancel.rst:6 -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/invoicing.rst:8 #: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/label_type.rst:6 -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/labels.rst:6 -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/third_party_shipper.rst:8 msgid "Overview" msgstr "" @@ -4989,12 +5082,12 @@ msgid "After cancelling the shipping request, you can change the carrier you wan msgstr "" #: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/cancel.rst:50 -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/labels.rst:115 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/labels.rst:122 msgid ":doc:`invoicing`" msgstr "" #: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/cancel.rst:51 -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/labels.rst:116 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/labels.rst:123 msgid ":doc:`multipack`" msgstr "" @@ -5079,87 +5172,149 @@ msgid "Click the green button on the Dropship card to view all dropship orders." msgstr "" #: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/invoicing.rst:3 -msgid "How to invoice the shipping cost to the customer?" +msgid "Shipping cost invoicing" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/invoicing.rst:7 +msgid "Invoicing customers for shipping after delivery ensures accurate charges based on real-time shipping factors like distance, weight, and method." msgstr "" #: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/invoicing.rst:10 -msgid "There are two ways to invoice the shipping costs:" +msgid "In Odoo, shipping costs can be invoiced in two ways:" msgstr "" #: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/invoicing.rst:12 -msgid "Agree with the customer over a cost and seal it down in the sale order" +msgid "Agree with the customer on a fixed cost and :ref:`include it in the sale order. `" msgstr "" #: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/invoicing.rst:15 -msgid "Invoice the real cost of the shipping." +msgid ":ref:`Invoice shipping costs to the customer post-delivery `, reflecting the actual expenses incurred by the business." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/invoicing.rst:20 -msgid "To configure the price of your delivery methods, go to the **Inventory** app, click on :menuselection:`Configuration --> Delivery --> Delivery Methods`." +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/invoicing.rst:21 +msgid "To set prices to delivery methods, go to :menuselection:`Inventory app --> Configuration --> Settings`. Under the :guilabel:`Shipping` section, enable the :guilabel:`Delivery Methods` feature. Then, click :guilabel:`Save`." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/invoicing.rst:23 -msgid "You can manually set a price for the shipping: It can be fixed or based on rules." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/invoicing.rst:26 -msgid "Or you can use the transportation company computation system by :doc:`integrating a third-party shipper <../setup_configuration/third_party_shipper>`." +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/invoicing.rst:-1 +msgid "Enable the \"Delivery Methods\" feature in Settings." msgstr "" #: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/invoicing.rst:30 -msgid "How to invoice the shipping costs to the customer?" +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/delivery_method.rst:30 +msgid "Add shipping method" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/invoicing.rst:33 -msgid "Invoice the price set on the sale order" +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/invoicing.rst:32 +msgid "Next, configure the the price of each delivery method by going to :menuselection:`Inventory app --> Configuration --> Shipping Methods` and click the :guilabel:`Create` button. Doing so opens a form to provide details about the shipping provider, including:" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/invoicing.rst:35 -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/invoicing.rst:57 -msgid "On your sale order, choose the carrier that will be used. Click on **Delivery Method** to choose the right one." +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/invoicing.rst:36 +msgid ":guilabel:`Shipping Method` (*required*) the name of the delivery method (e.g. `flat-rate shipping`, `same day delivery`, etc.)." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/invoicing.rst:41 -msgid "The price is computed when you **save** the sale order or when you click on **Set price**." +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/invoicing.rst:38 +msgid ":guilabel:`Provider` (*required*): choose the delivery service, like FedEx, if using a third-party carrier Ensure the integration with the shipping carrier is properly installed and select the provider from the drop-down menu." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/invoicing.rst:44 -msgid "To invoice the price of the delivery charge on the sale order, click on **Set price**, it will add a line with the name of the delivery method as a product. It may vary from the real price." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/invoicing.rst:48 -msgid "When you create the invoice, it will take the price set on the sale order." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/invoicing.rst:55 -msgid "Invoice the real shipping costs" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/invoicing.rst:63 -msgid "The price is computed when you **save** the sale order. Confirm the sale order and proceed to deliver the product." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/invoicing.rst:66 -msgid "The real shipping cost is computed when the delivery order is validated, you can see the real cost in the chatter of the delivery order." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/invoicing.rst:72 -msgid "Go back to the sale order, the real cost is now added to the sale order." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/invoicing.rst:78 -msgid "When you create the invoice, it will take the price computed by the carrier." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/invoicing.rst:85 -msgid "If you split the delivery and make several ones, each delivery order will add a line to the sale order." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/invoicing.rst:89 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/invoicing.rst:43 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/invoicing.rst:124 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/labels.rst:23 msgid ":doc:`../setup_configuration/third_party_shipper`" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/invoicing.rst:90 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/invoicing.rst:45 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/delivery_method.rst:61 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/third_party_shipper.rst:121 +msgid ":guilabel:`Company`: if the shipping method should apply to a specific company, select it from the drop-down menu. Leave the field blank to apply the method to all companies." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/invoicing.rst:48 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/delivery_method.rst:59 +msgid ":guilabel:`Website`: configure shipping methods for an e-commerce page. Select the applicable website from the drop-down menu, or leave it blank to apply the method to all web pages." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/invoicing.rst:51 +msgid ":guilabel:`Delivery Product` (*required*): the product listed on the :ref:`sales order line ` as the delivery charge." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/invoicing.rst:53 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/delivery_method.rst:68 +msgid ":guilabel:`Free if order amount is above`: checking this box enables free shipping if the customer spends above the specified amount." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/invoicing.rst:59 +msgid "Invoice cost on sales order" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/invoicing.rst:61 +msgid "To invoice shipping costs on the sales order, before the item is delivered, go to the :menuselection:`Sales app` and select the desired sales order." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/invoicing.rst:64 +msgid "On the sales order, click the :guilabel:`Add Shipping` button at the bottom-right corner." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/invoicing.rst:-1 +msgid "Click \"Add Shipping\" button at the bottom right, near the total." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/invoicing.rst:70 +msgid "In the :guilabel:`Add a shipping method` pop-up window, choose the intended carrier in the :guilabel:`Shipping Method` field." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/invoicing.rst:73 +msgid "Then, click the :guilabel:`Get Rate` button to the calculate shipping price based on real-time shipping data Odoo's shipping carrier integration." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/invoicing.rst:76 +msgid "The :guilabel:`Cost` is automatically calculated using the weight of the items in the order. Finally, click the :guilabel:`Add` button to close the window." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/invoicing.rst:-1 +msgid "Calculate shipping by selecting a shipping method." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/invoicing.rst:85 +msgid "On the sales order, the delivery product appears in the :guilabel:`Order Lines` tab, with the :guilabel:`Unit Price` set as the shipping cost calculated in the :guilabel:`Add a shipping method` pop-up window." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/invoicing.rst:-1 +msgid "Show delivery product on the sales order line." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/invoicing.rst:93 +msgid "Finally, after the product is delivered, click the :guilabel:`Create invoice` button, and an invoice is created that includes the shipping cost that was added earlier." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/invoicing.rst:-1 +msgid "Show \"Create Invoice\" button." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/invoicing.rst:100 +msgid "Then, click the :guilabel:`Create and View Invoice` button, and a draft invoice is generated, with the shipping cost included in the :guilabel:`Invoice Lines` tab." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/invoicing.rst:-1 +msgid "Show delivery product in the invoice line." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/invoicing.rst:110 +msgid "Invoice real shipping costs" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/invoicing.rst:112 +msgid "To modify the invoice to reflect the real cost of shipping, follow the steps :ref:`above ` to create an invoice with a delivery product with a :guilabel:`Unit Price` of zero." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/invoicing.rst:116 +msgid "Then, on a draft invoice, modify the :guilabel:`Unit Price` to reflect the real shipping cost. Finally, invoice the customer the adjusted shipping cost by clicking :guilabel:`Confirm`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/invoicing.rst:-1 +msgid "Show delivery product on the invoice line." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/invoicing.rst:125 msgid ":doc:`labels`" msgstr "" @@ -5194,7 +5349,7 @@ msgstr "" #: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/label_type.rst:35 #: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/delivery_three_steps.rst:48 #: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_one_step.rst:93 -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_two_steps.rst:141 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_two_steps.rst:130 msgid "Create a sales order" msgstr "" @@ -5243,121 +5398,112 @@ msgid "Half page letter size FedEx shipping label." msgstr "" #: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/labels.rst:3 -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/labels.rst:85 -msgid "How to print shipping labels?" +msgid "Print shipping labels" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/labels.rst:8 -msgid "Odoo can handle various delivery methods, including third party shippers linked with the transportation company tracking system. It allows you to manage the transport company, the real prices and the destination. And finally, you will be able to print the shipping labels directly from Odoo." +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/labels.rst:7 +msgid "Integrate Odoo with :doc:`third-party shipping carriers <../setup_configuration/third_party_shipper>` to automatically generate shipping labels that includes prices, destination addresses, tracking numbers, and barcodes." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/labels.rst:18 -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/third_party_shipper.rst:19 -msgid "Install the shipper company connector module" +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/labels.rst:14 +msgid "To generate labels for a third-party shipping carrier, first :doc:`install the third-party shipping connector <../setup_configuration/third_party_shipper>`. Then, configure and activate the :ref:`delivery method `, being sure to set the :guilabel:`Integration Level` to :guilabel:`Get Rate and Create Shipment` to generate shipping labels. Finally, provide the company's :ref:`source address ` and :ref:`product weights `." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/labels.rst:20 -msgid "In the **Inventory** module, click on :menuselection:`Configuration --> Settings`. Under **Shipping Connectors**, flag the transportation companies you want to integrate :" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/labels.rst:27 -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/third_party_shipper.rst:28 -msgid "Then click on **Apply**." +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/labels.rst:-1 +msgid "Set the \"Get Rate and Create Shipment\" option." msgstr "" #: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/labels.rst:30 -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/third_party_shipper.rst:35 -msgid "Configure the delivery method" +msgid "Print tracking labels" msgstr "" #: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/labels.rst:32 -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/third_party_shipper.rst:37 -msgid "To configure your delivery methods, go to the **Inventory** module, click on :menuselection:`Configuration --> Delivery Methods`." +msgid "Tracking labels are generated after the delivery order (DO) is validated." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/labels.rst:35 -msgid "The delivery methods for the chosen shippers have been automatically created." +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/labels.rst:34 +msgid "When both the *Sales* and *Inventory* apps are installed, begin on the :menuselection:`Sales app`, and proceed to the desired quotation to :ref:`add the shipping cost `, confirm the sales order, and validate the |DO|." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/labels.rst:41 -msgid "In the **Pricing** tab, the name of the provider means that the delivery will be handled and computed by the shipper system." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/labels.rst:44 -msgid "The configuration of the shipper is split into two columns :" +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/labels.rst:38 +msgid "If only the *Inventory* app is installed, create :abbr:`DOs (Delivery Orders)` directly in the :menuselection:`Inventory` app , :ref:`add the third-party carrier ` in the :guilabel:`Carrier` field, and validate the |DO|." msgstr "" #: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/labels.rst:46 -msgid "The first one is linked to **your account** (develop key, password,...). For more information, please refer to the provider website." +msgid "Add shipping on quotation" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/labels.rst:49 -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/third_party_shipper.rst:64 -msgid "The second column varies according to the **provider**. You can choose the packaging type, the service type, the weight unit..." +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/labels.rst:48 +msgid "To generate a tracking label for an order, begin by creating a quotation in :menuselection:`Sales app --> Orders --> Quotations`, clicking :guilabel:`New`, and filling out the quotation form. Then, click the :guilabel:`Add Shipping` button in the bottom-right corner of the quotation." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/labels.rst:52 -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/third_party_shipper.rst:67 -msgid "Uncheck **Test Mode** when you are done with the testings." +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/labels.rst:-1 +msgid "Show the \"Add Shipping\" button on the quotation." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/labels.rst:55 -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/third_party_shipper.rst:79 -msgid "Company configuration" +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/labels.rst:56 +msgid "In the resulting pop-up window, select the intended carrier from the :guilabel:`Shipping Method` drop-down menu. Clicking :guilabel:`Get Rate` displays the shipping cost for the customer, via the third-party carrier in the :guilabel:`Cost` field." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/labels.rst:57 -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/third_party_shipper.rst:81 -msgid "In order to compute the right price, the provider needs your company information. Be sure your address and phone number are correctly encoded." +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/labels.rst:61 +msgid "If clicking :guilabel:`Get Rate` results in an error, ensure the :ref:`warehouse's address ` and :ref:`weight of products in the order ` are properly configured." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/labels.rst:64 -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/third_party_shipper.rst:88 -msgid "To check your information, go to the **Settings** application and click on **General Settings**. Click on the first link **Configure your company data**." +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/labels.rst:65 +msgid "Click :guilabel:`Add` to add the cost to the quotation, which is listed as the :ref:`configured delivery product `. Finally, click :guilabel:`Confirm` on the quotation, and click the :guilabel:`Delivery` smart button to access the |DO|." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/labels.rst:68 -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/third_party_shipper.rst:92 -msgid "Product configuration" +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/labels.rst:-1 +msgid "Show \"Get rate\" pop-up window." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/labels.rst:70 -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/third_party_shipper.rst:94 -msgid "The shipper companies need the weight of your product, otherwise the price computation cannot be done." +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/labels.rst:75 +msgid "For users who do not have the *Sales* app installed, the shipping carrier is specified in a delivery order's :guilabel:`Carrier` field of the :guilabel:`Additional Info` tab." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/labels.rst:73 -msgid "Go the **Sales** module, click on :menuselection:`Sales --> Products`. Open the products you want to ship and set a weight on it." +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/labels.rst:0 +msgid "Show the \"Additional Info\" tab of a delivery order." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/labels.rst:80 -msgid "The weight on the product form is expressed in kilograms. Don't forget to do the conversion if you are used to the imperial measurement system." +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/labels.rst:85 +msgid "Validate delivery order" msgstr "" #: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/labels.rst:87 -msgid "The delivery order created from the sale order will take the shipping information from it, but you can change the carrier if you want to." +msgid "On a delivery order form, navigate to the :guilabel:`Additional Info` tab to ensure the third-party shipping carrier has been added to the :guilabel:`Carrier` field." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/labels.rst:90 -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/third_party_shipper.rst:137 -msgid "If you create a delivery transfer from the inventory module, you can add the third party shipper in the additional info tab." +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/labels.rst:91 +msgid "If the *Sales* app is not installed, the third-party carrier is set in the :guilabel:`Carrier` field." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/labels.rst:96 -msgid "Click on **Validate** to receive the tracking number and **the label(s)**." +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/labels.rst:94 +msgid "After the items in the order have been packed, click :guilabel:`Validate` to get the shipping carrier's tracking number, and generate the shipping label." msgstr "" #: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/labels.rst:98 -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/third_party_shipper.rst:153 -msgid "The label to stick on your package is available in the history underneath :" +msgid "Create or select an existing delivery order by going to the :menuselection:`Inventory` app, and selecting the :guilabel:`Delivery Orders` card." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/labels.rst:104 -msgid "Click on it to open the document and print it :" +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/labels.rst:101 +msgid "The :guilabel:`Tracking Reference` number is generated in the :guilabel:`Additional Info` tab of the delivery order. Click the :guilabel:`Tracking` smart button to access the tracking link from the shipping carrier's website." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/labels.rst:110 -msgid "If you are doing multi-packages shippings, most of the time, there will be one label per package. Each label will appear in the delivery history." +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/labels.rst:105 +msgid "The tracking label is found in PDF format in the chatter." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/labels.rst:-1 +msgid "Show generated shipping label in the chatter." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/labels.rst:112 +msgid "For multi-package shipping, one label is generated per package. Each label appears in the chatter." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/labels.rst:119 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/labels.rst:119 +msgid "Sample label generated from Odoo's shipping connector with FedEx." msgstr "" #: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/advanced_operations_shipping/multipack.rst:3 @@ -5882,7 +6028,7 @@ msgid "To create a new quote, navigate to :menuselection:`Sales app --> Create`, msgstr "" #: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/delivery_three_steps.rst:54 -msgid "A :guilabel:`Delivery` smart button appears in the top right of the quotation form. Clicking it shows the picking order, packing order, and the delivery order associated with the sales order." +msgid "A :guilabel:`Delivery` smart button appears in the top right of the quotation form. Clicking it opens the picking order to move the ordered product from `WH/Stock` to `WH/Packing Zone`." msgstr "" #: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/delivery_three_steps.rst:-1 @@ -5895,83 +6041,71 @@ msgid "Process a picking" msgstr "" #: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/delivery_three_steps.rst:65 -msgid "The picking, packing, and delivery orders will be created once the sales order is confirmed. To view these transfers, go to :menuselection:`Inventory --> Operations --> Transfers`." +msgid "The picking order will be created once the sales order is confirmed. To view the picking, navigate to the :menuselection:`Inventory app`, and locate the :guilabel:`Pick` task card on the :guilabel:`Inventory Overview` dashboard." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/delivery_three_steps.rst:69 +msgid "Click the :guilabel:`# To Process` button, which reveals the picking order generated from the previously confirmed sales order." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/delivery_three_steps.rst:72 +msgid "Click on the picking to process. If the product is in stock, Odoo will automatically reserve the product. Click :guilabel:`Validate` to mark the picking as done, and complete the transfer to the :guilabel:`Packing Zone`." msgstr "" #: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/delivery_three_steps.rst:-1 -msgid "Ready status for the pick operation while the packing and delivery operations are waiting\n" -"another operation." +msgid "Picking order operation showing source location and destination location." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/delivery_three_steps.rst:73 -msgid "The status of the picking will be :guilabel:`Ready`, since the product must be picked from stock before it can be packed. The status of the packing order and delivery order will both be :guilabel:`Waiting Another Operation`, since the packing and delivery cannot happen until the picking is completed. The status of the delivery order will only change to :guilabel:`Ready` when the packing has been marked :guilabel:`Done`." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/delivery_three_steps.rst:79 -msgid "The receipt can also be found in the *Inventory* application. In the :guilabel:`Overview` dashboard, click the :guilabel:`1 To Process` smart button in the :guilabel:`Pick` kanban card." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/delivery_three_steps.rst:-1 -msgid "The pick order can be seen in the Inventory Kanban view." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/delivery_three_steps.rst:86 -msgid "Click on the picking to process. If the product is in stock, Odoo will automatically reserve the product. Click :guilabel:`Validate` to mark the picking as done, and complete the transfer to the :guilabel:`Packing Zone`. Then the packing order will be ready. Since the documents are linked, the products which have been previously picked are automatically reserved on the packing order." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/delivery_three_steps.rst:-1 -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_two_steps.rst:-1 -msgid "Validate the picking by clicking Validate." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/delivery_three_steps.rst:96 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/delivery_three_steps.rst:81 msgid "Process a packing" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/delivery_three_steps.rst:98 -msgid "The packing order will be ready to be processed once the picking is completed, and can be found in the :menuselection:`Inventory` application :guilabel:`Overview` dashboard. Click the :guilabel:`1 To Process` smart button in the :guilabel:`Pack` kanban card." +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/delivery_three_steps.rst:83 +msgid "After validating the picking, the packing order is ready to process. Click back to the :guilabel:`Inventory Overview`, and locate the :guilabel:`Pack` task card on the dashboard." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/delivery_three_steps.rst:-1 -msgid "The packing order can be seen in the Inventory kanban view." +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/delivery_three_steps.rst:86 +msgid "Click the :guilabel:`# To Process` button (in this case, :guilabel:`1 To Process`). This reveals the packing order generated from the previously confirmed sales order." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/delivery_three_steps.rst:106 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/delivery_three_steps.rst:89 msgid "Click on the packing order associated with the sales order, then click on :guilabel:`Validate` to complete the packing." msgstr "" #: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/delivery_three_steps.rst:-1 -msgid "Click Validate on the packing order to transfer the product from the packing zone to the\n" -"output location." +msgid "Packing order operation showing source location and destination location." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/delivery_three_steps.rst:114 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/delivery_three_steps.rst:96 msgid "Once the packing order is validated, the product leaves the :guilabel:`WH/Packing Zone` location and moves to the :guilabel:`WH/Output` location. Then, the status of the document will change to :guilabel:`Done`." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/delivery_three_steps.rst:119 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/delivery_three_steps.rst:101 msgid "Process a delivery" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/delivery_three_steps.rst:121 -msgid "The delivery order will be ready to be processed once the packing is completed, and can be found in the :menuselection:`Inventory` application :guilabel:`Overview` dashboard. Click the :guilabel:`1 To Process` smart button in the :guilabel:`Delivery Orders` kanban card." +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/delivery_three_steps.rst:103 +msgid "Once the packing order has been validated, the delivery order is ready to process. Navigate back to the original sales order to process the delivery by going to :menuselection:`Sales app`, and selecting the sales order created previously." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/delivery_three_steps.rst:108 +msgid "Delivery orders can *also* be accessed by going to :menuselection:`Inventory app --> Operations --> Deliveries`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/delivery_three_steps.rst:111 +msgid "The :guilabel:`Delivery` smart button now indicates there are 3 transfers, instead of one. Clicking the :guilabel:`Delivery` smart button shows the three operations for this sales order: the picking, the packing, and the delivery." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/delivery_three_steps.rst:115 +msgid "Click the delivery (WH/OUT) transfer to open the delivery order. Then, click :guilabel:`Validate`." msgstr "" #: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/delivery_three_steps.rst:-1 -msgid "The delivery order can be seen in the Delivery Orders Kanban view." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/delivery_three_steps.rst:129 -msgid "Click on the delivery order associated with the sales order, then click on :guilabel:`Validate` to complete the move." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/delivery_three_steps.rst:-1 -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_two_steps.rst:-1 msgid "Click Validate on the delivery order to transfer the product from the output location to\n" "the customer location." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/delivery_three_steps.rst:137 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/delivery_three_steps.rst:122 msgid "Once the delivery order is validated, the product leaves the :guilabel:`WH/Output` location and moves to the :guilabel:`Partners/Customers` location. Then, the status of the document will change to :guilabel:`Done`." msgstr "" @@ -6032,7 +6166,6 @@ msgid "Receipt smart button appears on the confirmed purchase order." msgstr "" #: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_one_step.rst:54 -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_two_steps.rst:91 msgid "Purchase order receipts can also be found in the :menuselection:`Inventory` application. In the :guilabel:`Overview` dashboard, click the :guilabel:`# to Process` smart button in the :guilabel:`Receipts` kanban card." msgstr "" @@ -6041,7 +6174,7 @@ msgid "Receipt kanban card's 1 to Process smart button." msgstr "" #: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_one_step.rst:63 -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_two_steps.rst:100 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_two_steps.rst:91 #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/warehouse_replenishment_transfer.rst:97 msgid "Process the receipt" msgstr "" @@ -6092,7 +6225,7 @@ msgid "Delivery Orders kanban card's 1 to Process smart button." msgstr "" #: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_one_step.rst:120 -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_two_steps.rst:194 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_two_steps.rst:172 msgid "Process the delivery" msgstr "" @@ -6169,7 +6302,7 @@ msgid "For businesses with multiple warehouses that have different step configur msgstr "" #: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_two_steps.rst:83 -msgid "After confirming the :abbr:`PO (Purchase Order)`, a :guilabel:`Receipt` smart button will appear in the top of the :abbr:`PO (Purchase Order)` form — click it to reveal the associated receipt." +msgid "After confirming the :abbr:`PO (Purchase Order)`, a :guilabel:`Receipt` smart button appears at the top of the :abbr:`PO (Purchase Order)` form. Click it to reveal the new receipt (WH/IN) operation." msgstr "" #: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_two_steps.rst:-1 @@ -6177,108 +6310,116 @@ msgstr "" msgid "After confirming a purchase order, a Receipt smart button will appear." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_two_steps.rst:0 -msgid "One receipt ready to process in the Inventory Overview kanban view." +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_two_steps.rst:93 +msgid "Once the purchase order is confirmed, a receipt is generated and ready to process." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_two_steps.rst:102 -msgid "The receipt and internal transfer will be created once the purchase order is confirmed. The status of the receipt will be :guilabel:`Ready`, since the receipt must be processed first. The status of the internal transfer will be :guilabel:`Waiting Another Operation`, since the transfer cannot happen until the receipt is completed. The status of the internal transfer will only change to :guilabel:`Ready` once the receipt has been marked as :guilabel:`Done`." +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_two_steps.rst:95 +msgid "Navigate to the :menuselection:`Inventory app`, and locate the :guilabel:`Receipts` task card on the :guilabel:`Inventory Overview` dashboard. This reveals a list of all receipts to process." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_two_steps.rst:108 -msgid "Click on the :guilabel:`Receipt` associated with the purchase order, then click :guilabel:`Validate` to complete the receipt and move the product to the :guilabel:`Input Location`." +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_two_steps.rst:98 +msgid "Click on the :guilabel:`Receipt` associated with the purchase order, then click :guilabel:`Validate` to complete the receipt and move the product to :guilabel:`WH/Input`." msgstr "" #: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_two_steps.rst:-1 -msgid "Validate the receipt by clicking Validate, then the product will be transferred to the\n" -"WH/Input location." +msgid "Receipt form for product move to WH/Input." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_two_steps.rst:117 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_two_steps.rst:106 msgid "Process the internal transfer" msgstr "" +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_two_steps.rst:108 +msgid "Once the receipt is validated, an internal transfer is created and ready to process." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_two_steps.rst:110 +msgid "Click back to the :guilabel:`Inventory Overview` in the breadcrumbs, and locate the :guilabel:`Internal Transfers` task card." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_two_steps.rst:113 +msgid "Click the :guilabel:`# To Process` button to reveal a list of all internal transfers to process, and select the transfer associated with the previously validated receipt." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_two_steps.rst:116 +msgid "Click :guilabel:`Validate` to complete the transfer and move the product from :guilabel:`WH/Input` to :guilabel:`WH/Stock`." +msgstr "" + #: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_two_steps.rst:119 -msgid "Once the product is in the :guilabel:`Input Location`, the internal transfer is ready to move the product into stock. Navigate to the :menuselection:`Inventory` app, and on the :guilabel:`Inventory Overview` dashboard, click the :guilabel:`# To Process` smart button in the :guilabel:`Internal Transfers` kanban card." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_two_steps.rst:-1 -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_three_steps.rst:-1 -msgid "One Internal Transfer ready to process in the Inventory Overview kanban view." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_two_steps.rst:128 -msgid "Click on the :guilabel:`Transfer` associated with the purchase order, then click :guilabel:`Validate` to complete the receipt and move the product to stock. Once the transfer is validated, the product enters the stock and is available for customer deliveries or manufacturing orders." +msgid "Once the transfer is validated, the product enters inventory and is available for customer deliveries or manufacturing orders." msgstr "" #: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_two_steps.rst:-1 msgid "Validate the internal transfer to move the item to stock." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_two_steps.rst:138 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_two_steps.rst:127 msgid "Process a delivery order in two steps (pick + ship)" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_two_steps.rst:143 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_two_steps.rst:132 msgid "In the :menuselection:`Sales` application, create a new quote by clicking :guilabel:`New`. Select (or create) a :guilabel:`Customer`, add a storable :guilabel:`Product` to the order lines, and then click :guilabel:`Confirm`." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_two_steps.rst:147 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_two_steps.rst:136 msgid "After confirming the :abbr:`SO (Sales Order)`, a :guilabel:`Delivery` smart button will appear in the top, above the :abbr:`SO (Sales Order)` form. Click the :guilabel:`Delivery` smart button to reveal the associated receipt." msgstr "" #: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_two_steps.rst:-1 -msgid "After confirming the sales order, the Delivery smart button appears showing two items\n" -"associated with it." +msgid "Delivery smart button on sales order form." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_two_steps.rst:157 -msgid "Sales order receipts can also be found in the :menuselection:`Inventory` application. In the :guilabel:`Overview` dashboard, click the :guilabel:`# To Process` smart button in the :guilabel:`Pick` kanban card." +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_two_steps.rst:145 +msgid "Sales order receipts can also be found in the :menuselection:`Inventory` application. In the :guilabel:`Overview` dashboard, click the :guilabel:`# To Process` smart button in the :guilabel:`Pick` Kanban card." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_two_steps.rst:0 -msgid "The pick order can be seen in the Inventory kanban view." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_two_steps.rst:166 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_two_steps.rst:150 msgid "Process the picking" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_two_steps.rst:168 -msgid "The picking and delivery order will be created once the sales order is confirmed. When the :guilabel:`Delivery` smart button appears, click it to reveal the :guilabel:`Transfers` dashboard, which lists both the picking and the delivery orders." +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_two_steps.rst:152 +msgid "Once the sales order is confirmed, a picking order is generated and ready to process." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_two_steps.rst:172 -msgid "The status of the picking will be :guilabel:`Ready`, since the product must be picked from stock before it can be shipped. The status of the delivery order will be :guilabel:`Waiting Another Operation`, since the delivery cannot happen until the picking is completed. The status of the delivery order will only change to :guilabel:`Ready` once the picking has been marked as :guilabel:`Done`." +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_two_steps.rst:154 +msgid "Navigate to the :menuselection:`Inventory app`, and locate the :guilabel:`Pick` task card on the :guilabel:`Inventory Overview` dashboard. This reveals a list of all pickings to process." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_two_steps.rst:157 +msgid "Click on the picking (WH/PICK) operation associated with the sales order to reveal the picking order." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_two_steps.rst:160 +msgid "Click :guilabel:`Check Availability` on the picking order form. If the product is in stock, Odoo automatically reserves the product. Quantities can also be manually set by changing the value in the :guilabel:`Quantity` column to match the value in the :guilabel:`Demand` column." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_two_steps.rst:164 +msgid "Once ready, click :guilabel:`Validate` to complete the picking and move the product from :guilabel:`WH/Stock` to :guilabel:`WH/Output.`" msgstr "" #: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_two_steps.rst:-1 -msgid "Ready status for the pick operation while the delivery operation is Waiting Another\n" -"Operation." +msgid "Picking operation form moving product to WH/Output." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_two_steps.rst:183 -msgid "Click on the picking delivery order to begin processing it. If the product is in stock, Odoo will automatically reserve the product. Click :guilabel:`Validate` to mark the picking as :guilabel:`Done`, then the delivery order will be ready for processing. Since the documents are linked, the products which have been previously picked are automatically reserved on the delivery order." +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_two_steps.rst:174 +msgid "Once the picking has been processed, the delivery order is generated, and can be processed." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_two_steps.rst:196 -msgid "The delivery order will be ready to be processed once the picking is completed, and can be found in the :menuselection:`Inventory` application, on the :guilabel:`Inventory Overview` dashboard. Click the :guilabel:`# To Process` smart button in the :guilabel:`Delivery Orders` kanban card to begin." +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_two_steps.rst:176 +msgid "Navigate back to the original sales order by going to :menuselection:`Sales app`, and selecting the associated sales order." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_two_steps.rst:201 -msgid "The delivery order associated with the :abbr:`SO (Sales Order)` can also be quickly accessed by clicking on the :guilabel:`Delivery` smart button again, and choosing the delivery order on the :guilabel:`Transfers` page (which should now be marked as :guilabel:`Ready`)." +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_two_steps.rst:179 +msgid "The :guilabel:`Delivery` smart button now indicates there are two transfers. Click the :guilabel:`Delivery` smart button to reveal each transfer tied to this sales order: the completed picking, and the new delivery (WH/OUT) operation. Click the delivery operation to open the delivery order." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_two_steps.rst:184 +msgid "Once ready, click :guilabel:`Validate` to complete the delivery." msgstr "" #: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_two_steps.rst:-1 -msgid "The delivery order can be seen in the Inventory Kanban view." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_two_steps.rst:209 -msgid "Click on the delivery order associated with the :abbr:`SO (Sales Order)`, then click on :guilabel:`Validate` to complete the move." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_two_steps.rst:217 -msgid "Once the delivery order is validated, the product leaves the :guilabel:`WH/Output` location on the :guilabel:`Transfers` dashboard and moves to the :guilabel:`Partners/Customers` location. Then, the status of the document will change to :guilabel:`Done`." +msgid "Delivery operation form moving product to customer location." msgstr "" #: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_three_steps.rst:3 @@ -6334,65 +6475,67 @@ msgid "Process a receipt" msgstr "" #: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_three_steps.rst:65 -msgid "One receipt and two internal transfers (one transfer to quality, and a subsequent transfer to stock) will be created once the purchase order is confirmed. To view these transfers, go to :menuselection:`Inventory --> Operations --> Transfers`." +msgid "Once the purchase order (PO) is confirmed, a receipt (`WH/IN`) operation is generated and ready to process." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_three_steps.rst:-1 -msgid "The status of the three receipt transfers will show which operation is ready and which ones\n" -"are waiting another operation." +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_three_steps.rst:68 +msgid "The receipt can be confirmed from the original purchase order form, or it can be accessed by navigating to the :menuselection:`Inventory app`, and locating the :guilabel:`Receipts` task card." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_three_steps.rst:71 +msgid "Click the :guilabel:`# To Process` button to reveal all incoming receipts to process. Click the receipt associated with the previous purchase order." msgstr "" #: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_three_steps.rst:74 -msgid "The status of the receipt transferring the product to the input location will be :guilabel:`Ready`, since the receipt must be processed before any other operation can occur. The status of the two internal transfers will be :guilabel:`Waiting Another Operation`, since the transfers cannot be processed until the linked step before each transfer is completed." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_three_steps.rst:79 -msgid "The status of the first internal transfer to *quality* will only change to :guilabel:`Ready` when the receipt has been marked :guilabel:`Done`. The status for the second internal transfer to *stock* will be marked :guilabel:`Ready` only after the transfer to quality has been marked :guilabel:`Done`." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_three_steps.rst:84 -msgid "The receipt can also be found in the :menuselection:`Inventory` application. In the :guilabel:`Overview` dashboard, click the :guilabel:`1 To Process` smart button in the :guilabel:`Receipts` kanban card." +msgid "Click :guilabel:`Validate` to validate the receipt, and move the product to the destination location, :guilabel:`WH/Input`." msgstr "" #: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_three_steps.rst:-1 -msgid "One Receipt ready to process in the Inventory Overview kanban view." +msgid "Receipt operation for product being moved to WH/Input location." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_three_steps.rst:92 -msgid "Click on the receipt associated with the purchase order, then click :guilabel:`Validate` to complete the receipt and move the product to the :guilabel:`Input Location`." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_three_steps.rst:-1 -msgid "Validate the receipt by clicking Validate, and the product will be transferred to the\n" -"WH/Quality location." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_three_steps.rst:101 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_three_steps.rst:82 msgid "Process a transfer to Quality Control" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_three_steps.rst:103 -msgid "Once the product is in the :guilabel:`Input Location`, the internal transfer is ready to move the product to :guilabel:`Quality Control`. In the :menuselection:`Inventory` :guilabel:`Overview` dashboard, click the :guilabel:`1 To Process` smart button in the :guilabel:`Internal Transfers` kanban card." +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_three_steps.rst:84 +msgid "Once the receipt has been validated, an internal transfer operation to move the product to quality control is ready to process." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_three_steps.rst:112 -msgid "Click on the :guilabel:`Transfer` associated with the purchase order, then click :guilabel:`Validate` to complete the transfer and move the product to the :guilabel:`Quality Control` location. Once the transfer is validated, the product is ready for the quality inspection, but is not available for manufacturing or delivery orders." +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_three_steps.rst:87 +msgid "Click :guilabel:`Inventory Overview` in the breadcrumbs to navigate back to the dashboard, and locate the :guilabel:`Internal Transfers` task card." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_three_steps.rst:90 +msgid "Select the :guilabel:`# To Process` button to reveal all internal transfers to process. Then, choose the internal transfer associated with the validated receipt." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_three_steps.rst:93 +msgid "Once ready, click :guilabel:`Validate` to complete the transfer, and move the product from :guilabel:`WH/Input` to :guilabel:`WH/Quality Control`." msgstr "" #: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_three_steps.rst:-1 -msgid "Validate the internal transfer to move the item to the Quality Control location." +msgid "Internal transfer for product being moved to quality control zone." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_three_steps.rst:122 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_three_steps.rst:101 msgid "Process a transfer to stock" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_three_steps.rst:124 -msgid "Once the product is in the :guilabel:`Quality Control` location, the final internal transfer is ready to move the product to :guilabel:`Stock`. In the :guilabel:`Inventory` overview dashboard, click the :guilabel:`1 To Process` smart button in the :guilabel:`Internal Transfers` Kanban card." +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_three_steps.rst:103 +msgid "Once the internal transfer to move the product to quality control has been validated, another internal transfer operation to move the product into warehouse stock is ready to process." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_three_steps.rst:128 -msgid "Click on the final :guilabel:`Transfer` associated with the purchase order, then click :guilabel:`Validate` to complete the transfer and move the product to stock. Once the transfer is validated, the product enters the stock and is available for customer deliveries or manufacturing orders." +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_three_steps.rst:106 +msgid "Click :guilabel:`YourCompany: Internal Transfers` in the breadcrumbs to reveal the list of all internal transfers to process. Then, select the new internal transfer to move the product from `WH/Quality Control` to `WH/Stock`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_three_steps.rst:110 +msgid "Once ready, click :guilabel:`Validate` to complete the transfer, and move the product from :guilabel:`WH/Quality Control` to :guilabel:`WH/Stock`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_three_steps.rst:-1 +msgid "Internal transfer for product being moved to warehouse stock." msgstr "" #: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/shipments_deliveries.rst:3 @@ -6400,128 +6543,151 @@ msgid "Incoming shipments and delivery orders" msgstr "" #: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/shipments_deliveries.rst:5 -msgid "There are several ways to handle how a warehouse receives products (receipts) and ships products (deliveries). Depending on several factors, such as the type of products stocked and sold, warehouse size, and the amount of daily confirmed receipts and delivery orders, the way products are handled when coming in and out of the warehouse can vary a lot. Different settings can be configured for receipts and deliveries; they do not have to be configured to have the same number of steps." +msgid "In Odoo, there are many different ways to process receipts and deliveries for products moving in and out of a warehouse." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/shipments_deliveries.rst:8 +msgid "A company's preferred method of receiving, or shipping, products depends on several factors, such as the type of products stocked and sold, the size of the warehouse, the amount of receipts and delivery orders processed daily, and so on." msgstr "" #: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/shipments_deliveries.rst:12 +msgid "Enabling the *Multi-Step Routes* feature in Odoo's *Inventory* app settings allows users to change the manner in which receipts and deliveries are processed in the database." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/shipments_deliveries.rst:16 msgid "`Using Routes (eLearning Tutorial) `_" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/shipments_deliveries.rst:13 -msgid "`Push & Pull Rules (eLearning Tutorial) `_" -msgstr "" - #: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/shipments_deliveries.rst:17 -msgid "Choosing the right inventory flow to handle receipts and deliveries" +msgid "`Push & Pull Rules (eLearning Tutorial) `_" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/shipments_deliveries.rst:19 -msgid "By default, Odoo handles shipping and receiving in three different ways: in one, two, or three steps. The simplest configuration is one step, which is the default. Each additional step required for a warehouse for either the receiving or shipping process will add an additional layer of operations to perform before a product is either received or shipped. These configurations depend entirely on the requirements for the products stored, such as performing quality checks on received products, or using special packaging on shipped products." +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/shipments_deliveries.rst:20 +msgid "The default incoming and outgoing routes in Odoo are set to receive and deliver goods in one step. However, once the *Multi-Step Routes* feature is enabled, the incoming and outgoing routes can be changed to either two steps or three steps." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/shipments_deliveries.rst:27 -msgid "One-step flow" +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/shipments_deliveries.rst:25 +msgid "To activate the *Multi-Step Routes* feature, navigate to :menuselection:`Inventory app --> Configuration --> Settings`. Under the :guilabel:`Warehouse` section, tick the checkbox next to :guilabel:`Multi-Step Routes`, and click :guilabel:`Save`." msgstr "" #: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/shipments_deliveries.rst:29 -msgid "The receiving and shipping rules for a one-step configuration are as follows:" +msgid "Doing so *also* enables the :guilabel:`Storage Locations` feature, if not already enabled." msgstr "" #: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/shipments_deliveries.rst:31 -msgid "**Receipt**: Receive products directly into stock. No intermediate steps between receipt and stock occur, such as a transfer to a quality control location." +msgid "Adding additional steps to receipts and deliveries moving in and out of the warehouse adds additional operations that must be completed *before* a product is finally received or shipped." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/shipments_deliveries.rst:33 -msgid "**Shipping**: Ship products directly from stock. No intermediate steps between stock and shipping occur, such as a transfer to a packing location." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/shipments_deliveries.rst:35 -msgid "Can only be used if not using :abbr:`FIFO (First In, First Out)`, :abbr:`LIFO (Last In, First Out)`, or :abbr:`FEFO (First Expired, First Out)` removal strategies." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/shipments_deliveries.rst:37 -msgid "Receipts and/or deliveries are handled quickly." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/shipments_deliveries.rst:38 -msgid "Recommended for small warehouses with low stock levels, and for non-perishable items." +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/shipments_deliveries.rst:34 +msgid "These configurations vary, depending on the needs of the business. They also depend on any requirements for the products stored, including the performance of quality control checks on received products, or the use of special packaging on shipped products." msgstr "" #: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/shipments_deliveries.rst:39 -msgid "Items are received or shipped directly into/from stock." +msgid "One-step flow" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/shipments_deliveries.rst:42 -msgid ":doc:`receipts_delivery_one_step`" +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/shipments_deliveries.rst:41 +msgid "The receiving and shipping rules for a one-step configuration are as follows:" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/shipments_deliveries.rst:43 +msgid "**Receipt**: receive products directly from vendors into stock. *No* intermediate steps between receipt and input to stock occur." msgstr "" #: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/shipments_deliveries.rst:45 -msgid "Two-step flow" +msgid "**Shipping**: ship products directly from warehouse stock to customer. *No* intermediate steps occur before shipping." msgstr "" #: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/shipments_deliveries.rst:47 -msgid "The receiving and shipping rules for a two-step configuration are as follows:" +msgid "Can *only* be used if **not** using First In, First Out (FIFO), Last In, First Out (LIFO), or First Expired, First Out (FEFO) removal strategies." msgstr "" #: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/shipments_deliveries.rst:49 -msgid "**Input + stock**: Bring products to an input location *before* moving into stock. Products can be organized by different internal storage locations, such as various shelves, freezers, and locked areas, before being stocked in the warehouse." +msgid "Items are received or shipped directly into/from stock." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/shipments_deliveries.rst:52 -msgid "**Pick + ship**: Bring products to an output location before shipping. Packages can be organized by different carriers or shipping docks before being shipped." +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/shipments_deliveries.rst:50 +msgid "Suited for warehouses that require receipts and/or deliveries to be handled quickly." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/shipments_deliveries.rst:51 +msgid "Recommended for small warehouses with low stock levels, and for non-perishable items." msgstr "" #: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/shipments_deliveries.rst:54 -msgid "Minimum requirement to use lot numbers or serial numbers to track products with a :abbr:`FIFO (First In, First Out)`, :abbr:`LIFO (Last In, First Out)` or :abbr:`FEFO (First Expired, First Out)` removal strategy." +msgid ":doc:`receipts_delivery_one_step`" msgstr "" #: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/shipments_deliveries.rst:57 -msgid "Recommended for larger warehouses with high stock levels, or when stocking large items (such as mattresses, large furniture, heavy machinery, etc.)." +msgid "Two-step flow" msgstr "" #: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/shipments_deliveries.rst:59 -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/shipments_deliveries.rst:80 -msgid "Products received will not be available for manufacturing, shipping, etc., until they are transferred into stock." +msgid "The receiving and shipping rules for a two-step configuration are as follows:" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/shipments_deliveries.rst:63 -msgid ":ref:`Process receipts and deliveries in two steps `" +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/shipments_deliveries.rst:61 +msgid "**Input + stock**: bring products to an input location *before* moving into stock. Products can be organized by different internal storage locations, such as various shelves, freezers, and locked areas, before being stocked in the warehouse." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/shipments_deliveries.rst:64 +msgid "**Pick + ship**: bring products to an output location before shipping. Packages can be organized by different carriers, or moved to shipping docks before being shipped." msgstr "" #: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/shipments_deliveries.rst:66 -msgid "Three-step flow" +msgid "Minimum requirement to use lot numbers, or serial numbers, to track products with a :abbr:`FIFO (First In, First Out)`, :abbr:`LIFO (Last In, First Out)`, or :abbr:`FEFO (First Expired, First Out)` removal strategy." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/shipments_deliveries.rst:68 -msgid "The receiving and shipping rules for a three-step configuration are as follows:" +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/shipments_deliveries.rst:69 +msgid "Products received will not be available for manufacturing, shipping, etc., until they are transferred into warehouse stock." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/shipments_deliveries.rst:70 -msgid "**Input + quality + stock**: Receive products at the input location, transfer them to a quality control area, and move the ones that pass inspection into stock." +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/shipments_deliveries.rst:71 +msgid "Recommended for larger warehouses with high stock levels, or when stocking large items (e.g., mattresses, large furniture, heavy machinery, etc.)." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/shipments_deliveries.rst:72 -msgid "**Pick + pack + ship**: Pick products according to their removal strategy, pack them in a dedicated packing area, and bring them to an output location for shipping." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/shipments_deliveries.rst:74 -msgid "Can be used when tracking products by lot or serial numbers when using a :abbr:`FIFO (First In, First Out)`, :abbr:`LIFO (Last In, First Out)`, or :abbr:`FEFO (First Expired, First Out)` removal strategy." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/shipments_deliveries.rst:77 -msgid "Recommended for very large warehouses with very high stock levels." +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/shipments_deliveries.rst:75 +msgid ":doc:`receipts_delivery_two_steps`" msgstr "" #: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/shipments_deliveries.rst:78 -msgid "Required for any warehouse needing to perform quality control inspections before receiving items into stock." +msgid "Three-step flow" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/shipments_deliveries.rst:80 +msgid "The receiving and shipping rules for a three-step configuration are as follows:" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/shipments_deliveries.rst:82 +msgid "**Input + quality + stock**: receive products at the input location, transfer them to a quality control area, and move the ones that pass inspection into stock." msgstr "" #: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/shipments_deliveries.rst:84 -msgid ":ref:`Process receipts in three steps `" +msgid "**Pick + pack + ship**: pick products according to their removal strategy, pack them in a dedicated packing area, and bring them to an output location for shipping." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/shipments_deliveries.rst:85 -msgid ":ref:`Process deliveries in three steps `" +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/shipments_deliveries.rst:86 +msgid "Can be used when tracking products by lot or serial numbers when using :abbr:`FIFO (First In, First Out)`, :abbr:`LIFO (Last In, First Out)`, or :abbr:`FEFO (First Expired, First Out)` removal strategy." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/shipments_deliveries.rst:89 +msgid "Products received will not be available for manufacturing, shipping, etc., until they are transferred into stock." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/shipments_deliveries.rst:91 +msgid "Required for any warehouse needing to perform quality control inspections before receiving items into stock." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/shipments_deliveries.rst:93 +msgid "Recommended for very large warehouses with very high stock levels." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/shipments_deliveries.rst:96 +msgid ":doc:`receipts_three_steps`" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/shipments_deliveries.rst:97 +msgid ":doc:`delivery_three_steps`" msgstr "" #: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/reservation_methods.rst:6 @@ -7049,10 +7215,6 @@ msgstr "" msgid "Install the *Delivery Costs* module." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/delivery_method.rst:30 -msgid "Add shipping method" -msgstr "" - #: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/delivery_method.rst:32 msgid "To configure delivery methods, go to :menuselection:`Inventory app --> Configuration --> Shipping Methods`." msgstr "" @@ -7089,59 +7251,47 @@ msgstr "" msgid "For more details on configuring custom shipping methods, such as :ref:`fixed price `, :ref:`based on rules `, or :ref:`pickup in store ` options, refer to their respective sections below." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/delivery_method.rst:59 -msgid ":guilabel:`Website`: configure shipping methods for an e-commerce page. Select the applicable website from the drop-down menu, or leave it blank to apply the method to all web pages." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/delivery_method.rst:61 -msgid ":guilabel:`Company`: if the shipping method should apply to a specific company, select it from the drop-down menu. Leave the field blank to apply the method to all companies." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/delivery_method.rst:63 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/delivery_method.rst:66 msgid ":guilabel:`Delivery Product` (*Required field*): the product listed on the :ref:`sales order line ` as the delivery charge." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/delivery_method.rst:65 -msgid ":guilabel:`Free if order amount is above`: checking this box enables free shipping if the customer spends above the specified amount." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/delivery_method.rst:68 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/delivery_method.rst:71 msgid "For examples on how to configure specific shipping methods, refer to the sections below." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/delivery_method.rst:73 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/delivery_method.rst:76 msgid "Fixed price" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/delivery_method.rst:75 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/delivery_method.rst:78 msgid "To configure a shipping price that is the same for all orders, go to :menuselection:`Inventory app --> Configuration --> Shipping Methods`. Then, click :guilabel:`New`, and on the shipping method form, set the :guilabel:`Provider` to the :guilabel:`Fixed Price` option. Selecting this option makes the :guilabel:`Fixed Price` field become available, which is where the fixed rate shipping amount is defined." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/delivery_method.rst:81 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/delivery_method.rst:84 msgid "To enable free shipping if the amount of the order exceeds a specified amount, check the box :guilabel:`Free if order amount is above` and fill in the amount." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/delivery_method.rst:85 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/delivery_method.rst:88 msgid "To set up `$20` flat-rate shipping that becomes free if the customer spends over `$100`, fill in the following fields:" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/delivery_method.rst:88 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/delivery_method.rst:91 msgid ":guilabel:`Shipping Method`: `Flat-rate shipping`" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/delivery_method.rst:89 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/delivery_method.rst:92 msgid ":guilabel:`Provider`: :guilabel:`Fixed Price`" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/delivery_method.rst:90 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/delivery_method.rst:93 msgid ":guilabel:`Fixed Price`: `$20.00`" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/delivery_method.rst:91 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/delivery_method.rst:94 msgid ":guilabel:`Free if order amount is above`: `$100.00`" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/delivery_method.rst:92 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/delivery_method.rst:95 msgid ":guilabel:`Delivery Product`: `[SHIP] Flat`" msgstr "" @@ -7149,27 +7299,27 @@ msgstr "" msgid "Example of filling out a shipping method." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/delivery_method.rst:101 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/delivery_method.rst:104 msgid "Based on rules" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/delivery_method.rst:103 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/delivery_method.rst:106 msgid "To calculate the price of shipping based on pricing rules, set the :guilabel:`Provider` field to the :guilabel:`Based on Rules` option. Optionally, adjust :guilabel:`Margin on Rate` and :guilabel:`Additional margin` to include additional shipping costs." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/delivery_method.rst:108 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/delivery_method.rst:111 msgid "Create pricing rules" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/delivery_method.rst:110 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/delivery_method.rst:113 msgid "Navigate to the :guilabel:`Pricing` tab and click :guilabel:`Add a line`. Doing so opens the :guilabel:`Create Pricing Rules` window, where the :guilabel:`Condition` related to the product weight, volume, price, or quantity is compared to a defined amount to calculate the :guilabel:`Delivery Cost`." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/delivery_method.rst:115 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/delivery_method.rst:118 msgid "Once finished, click either :guilabel:`Save & New` to add another rule, or :guilabel:`Save & Close`." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/delivery_method.rst:118 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/delivery_method.rst:121 msgid "To charge customers $20 in shipping for orders with five or fewer products, set the :guilabel:`Condition` to `Quantity <= 5.00`, and the :guilabel:`Delivery Cost` to `$20`." msgstr "" @@ -7177,37 +7327,37 @@ msgstr "" msgid "Display window to add a pricing rule. Set a condition and delivery cost." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/delivery_method.rst:125 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/delivery_method.rst:128 msgid "To restrict shipping to specific destinations on the eCommerce website, in the shipping method form, navigate to the :guilabel:`Destination Availability` tab and define the :guilabel:`Countries`, :guilabel:`States`, and :guilabel:`Zip Prefixes`. Leave these fields empty if all locations apply." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/delivery_method.rst:130 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/delivery_method.rst:133 msgid "Calculate delivery cost" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/delivery_method.rst:132 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/delivery_method.rst:135 msgid "Shipping cost is the :guilabel:`Delivery cost` specified in the rule that satisfies the :guilabel:`Condition`, plus any extra charges from the :guilabel:`Margin on rate` and :guilabel:`Additional margin`." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/delivery_method.rst:136 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/delivery_method.rst:139 msgid "Total = Rule's~Delivery~Cost + (Margin~on~rate \\times Rule's~Delivery~Cost) + Additional~margin\n" "\n" "" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/delivery_method.rst:140 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/delivery_method.rst:143 msgid "With the two following rules set up:" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/delivery_method.rst:142 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/delivery_method.rst:145 msgid "If the order contains five or fewer products, shipping is $20" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/delivery_method.rst:143 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/delivery_method.rst:146 msgid "If the order contains more than five products, shipping is $50." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/delivery_method.rst:145 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/delivery_method.rst:148 msgid ":guilabel:`Margin on Rate` is `10%` and :guilabel:`Additional margin` is `$9.00`." msgstr "" @@ -7215,51 +7365,51 @@ msgstr "" msgid "Show example of \"Based on rules\" shipping method with margins configured." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/delivery_method.rst:151 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/delivery_method.rst:154 msgid "When the first rule is applied, the delivery cost is $31 (20 + (0.1 * 20) + 9). When the second rule is applied, the delivery cost is $64 (50 + (0.1 * 50) + 9)." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/delivery_method.rst:157 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/delivery_method.rst:160 msgid "Pickup in store" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/delivery_method.rst:159 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/delivery_method.rst:162 msgid "To configure in-store pickup, select :guilabel:`Pickup in store` in the :guilabel:`Provider` field and specify the pickup location in :guilabel:`Warehouse`." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/delivery_method.rst:162 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/delivery_method.rst:165 msgid "To invoice the customer for the shipping cost to the pickup location, choose the :guilabel:`Get Rate and Create Shipment` option in the :guilabel:`Integration Level` field. Then, pick either the :guilabel:`Estimated cost` or :guilabel:`Real cost` radio options in the :guilabel:`Invoicing Policy` field to decide whether the added shipping charge on the sales order is the precise cost from the shipping carrier." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/delivery_method.rst:169 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/delivery_method.rst:172 msgid ":ref:`Invoice cost of shipping `" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/delivery_method.rst:174 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/delivery_method.rst:177 msgid "Add shipping" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/delivery_method.rst:176 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/delivery_method.rst:179 msgid "Shipping methods can be added to sales orders in the form of delivery products, which appear as individual line items. First, navigate to the desired sales order by going to :menuselection:`Sales app --> Orders --> Orders`." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/delivery_method.rst:180 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/delivery_method.rst:183 msgid "On the sales order, click the :guilabel:`Add shipping` button, which opens the :guilabel:`Add a shipping method` pop-up window. Then, choose a :guilabel:`Shipping Method` from the list." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/delivery_method.rst:183 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/delivery_method.rst:186 msgid "The :guilabel:`Total Order Weight` is pre-filled based on product weights (that are defined in the :guilabel:`Inventory` tab for each product form). Edit the field to specify the exact weight, and then click :guilabel:`Add` to add the shipping method." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/delivery_method.rst:188 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/delivery_method.rst:191 msgid "The amount defined in :guilabel:`Total Order Weight` overwrites the total product weights defined on the product form." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/delivery_method.rst:191 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/delivery_method.rst:194 msgid "The shipping cost is added to the *sales order line* as the :guilabel:`Delivery Product` detailed on the shipping method form." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/delivery_method.rst:195 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/delivery_method.rst:198 msgid "`Furniture Delivery`, a delivery product with a fixed rate of `$200`, is added to sales order `S00088`." msgstr "" @@ -7267,11 +7417,12 @@ msgstr "" msgid "Show delivery order on the sales order line." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/delivery_method.rst:203 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/delivery_method.rst:206 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/third_party_shipper.rst:255 msgid "Delivery order" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/delivery_method.rst:205 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/delivery_method.rst:208 msgid "The shipping method added to the sales order is linked to the shipping carrier details on the delivery order. To add or change the delivery method on the delivery itself, go to the :guilabel:`Additional Info` tab and modify the :guilabel:`Carrier` field." msgstr "" @@ -7348,6 +7499,7 @@ msgid "Odoo integration of Sendcloud works on free Sendcloud plans *only* if a b msgstr "" #: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/sendcloud_shipping.rst:35 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/third_party_shipper.rst:174 msgid "Warehouse configuration" msgstr "" @@ -7425,6 +7577,7 @@ msgstr "" #: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/sendcloud_shipping.rst:83 #: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/starshipit_shipping.rst:90 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/ups_credentials.rst:158 msgid "Setup in Odoo" msgstr "" @@ -7978,215 +8131,677 @@ msgid "If a delivery order is cancelled in Odoo, it will be automatically archiv msgstr "" #: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/third_party_shipper.rst:3 -msgid "How to integrate a third party shipper?" +msgid "Third-party shipping carriers" msgstr "" #: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/third_party_shipper.rst:10 -msgid "Odoo can handle various delivery methods, including third party shippers. Odoo can be linked with the transportation company tracking system. It will allow you to manage the transport company, the real prices and the destination." +msgid "Users can link third-party shipping carriers to Odoo databases, in order to verify carriers' delivery to specific addresses, :doc:`automatically calculate shipping costs `, and :doc:`generate shipping labels <../advanced_operations_shipping/labels>`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/third_party_shipper.rst:14 +msgid "In Odoo, shipping carriers can be applied to a sales order (SO), invoice, or delivery order. For tips on resolving common issues when configuring shipping connectors, skip to the :ref:`Troubleshooting ` section." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/third_party_shipper.rst:19 +msgid ":doc:`dhl_credentials`" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/third_party_shipper.rst:20 +msgid ":doc:`sendcloud_shipping`" msgstr "" #: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/third_party_shipper.rst:21 -msgid "In the inventory module, click on :menuselection:`Configuration --> Settings`. Under **Shipping Connectors**, flag the transportation companies you want to integrate :" +msgid ":doc:`ups_credentials`" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/third_party_shipper.rst:23 +msgid "The following is a list of available shipping connectors in Odoo:" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/third_party_shipper.rst:29 +msgid "Carrier" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/third_party_shipper.rst:30 +msgid "Region availability" msgstr "" #: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/third_party_shipper.rst:31 -msgid "If you want to integrate delivery methods in your e-commerce, you'll have to install the **eCommerce Delivery** module." +msgid "FedEx" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/third_party_shipper.rst:32 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/third_party_shipper.rst:34 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/third_party_shipper.rst:36 +msgid "All" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/third_party_shipper.rst:33 +msgid ":doc:`DHL `" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/third_party_shipper.rst:35 +msgid ":doc:`UPS `" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/third_party_shipper.rst:37 +msgid "US Postal Service" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/third_party_shipper.rst:38 +msgid "United States of America" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/third_party_shipper.rst:39 +msgid ":doc:`Sendcloud `" msgstr "" #: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/third_party_shipper.rst:40 -msgid "The delivery methods for the chosen shippers have been automatically created. Most of the time, there will be **2** delivery methods for the same provider: one for **international** shipping and the other for **domestic** shipping." +msgid "EU" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/third_party_shipper.rst:41 +msgid "Bpost" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/third_party_shipper.rst:42 +msgid "Belgium" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/third_party_shipper.rst:43 +msgid "Easypost" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/third_party_shipper.rst:44 +msgid "North America" msgstr "" #: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/third_party_shipper.rst:45 -msgid "You can create other methods with the same provider with other configuration, for example the **Packaging Type**." +msgid "Shiprocket" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/third_party_shipper.rst:48 -msgid "You can change the **Name** of the delivery method. This is the name that will appear on your ecommerce." +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/third_party_shipper.rst:46 +msgid "India" msgstr "" #: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/third_party_shipper.rst:51 -msgid "Flag **Shipping enabled** when you are ready to use it." +msgid "To ensure proper setup of a third-party shipping carrier with Odoo, follow these steps:" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/third_party_shipper.rst:53 +msgid ":ref:`Install the shipping connector `." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/third_party_shipper.rst:54 +msgid ":ref:`Set up delivery method `." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/third_party_shipper.rst:55 +msgid ":ref:`Activate production environment `." msgstr "" #: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/third_party_shipper.rst:56 -msgid "In the pricing tab, the name of the provider chosen under the **Price computation** means that the pricing will be computed by the shipper system." +msgid ":ref:`Configure warehouse `." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/third_party_shipper.rst:59 -msgid "The configuration of the shipper is split into two columns:" +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/third_party_shipper.rst:57 +msgid ":ref:`Specify weight of products `." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/third_party_shipper.rst:61 -msgid "The first one is linked to **your account** (developer key, password,...). For more information, please refer to the provider website." +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/third_party_shipper.rst:62 +msgid "Install shipping connector" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/third_party_shipper.rst:69 -msgid "Finally you can limit the delivery method to a few destinations. You can limit it to some countries, states or even zip codes. This feature limits the list of countries on your e-commerce. It is useful for the domestic providers. For example, USPS US only delivers from the United States to the United States." +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/third_party_shipper.rst:64 +msgid "To install shipping connectors, go to :menuselection:`Inventory app --> Configuration --> Settings`." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/third_party_shipper.rst:97 -msgid "Go the menu :menuselection:`Sales --> Sales --> Products`. Open the products you want to ship and set a weight on it." +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/third_party_shipper.rst:66 +msgid "Under the :guilabel:`Shipping Connectors` section, tick the third-party shipping carrier's checkbox to install it. Multiple third-party shipping connectors can be selected at once. Then, click :guilabel:`Save`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/third_party_shipper.rst:71 +msgid ":doc:`Delivery methods ` can also be integrated with operations in the *Sales*, *eCommerce*, and *Website* apps. To install, refer to the :ref:`install apps and modules ` documentation." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/third_party_shipper.rst:-1 +msgid "Options of available shipping connectors in Odoo." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/third_party_shipper.rst:82 +msgid "Delivery method" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/third_party_shipper.rst:84 +msgid "To configure the API credentials, and activate the shipping carrier, begin by going to :menuselection:`Inventory app --> Configuration --> Shipping Methods`, and select the desired delivery method." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/third_party_shipper.rst:89 +msgid "The list often includes **two** delivery methods from the same :guilabel:`Provider`: one for international shipping and one for domestic shipping." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/third_party_shipper.rst:92 +msgid "Additional delivery methods can be created for specific purposes, such as :doc:`packaging <../../product_management/product_tracking/packaging>`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/third_party_shipper.rst:96 +msgid ":doc:`Configure delivery methods `" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/third_party_shipper.rst:99 +msgid "Ensure the delivery method is published when it should be available on the *Website* app. To publish a delivery method on the website, click the desired delivery method, then click the :guilabel:`Unpublished` smart button. Doing so changes that smart button to read: :guilabel:`Published`." msgstr "" #: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/third_party_shipper.rst:104 -msgid "The weight on the product form is expressed in kilograms. Don't forget to make the conversion if you are used to the imperial measurement system." +msgid "The :guilabel:`Shipping Method` page contains details about the provider, including:" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/third_party_shipper.rst:109 -msgid "Sale process" +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/third_party_shipper.rst:106 +msgid ":guilabel:`Shipping Method` (*Required field*): the name of the delivery method (e.g. `FedEx US`, `FedEx EU`, etc.)." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/third_party_shipper.rst:112 -msgid "Sale order" +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/third_party_shipper.rst:108 +msgid ":guilabel:`Website`: configure shipping methods for an *eCommerce* page that is connected to a specific website in the database. Select the applicable website from the drop-down menu, or leave it blank to apply the method to all web pages." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/third_party_shipper.rst:117 -msgid "You can now choose the carrier on your sale order. Click on **Delivery method** to choose the right one." +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/third_party_shipper.rst:111 +msgid ":guilabel:`Provider` (*Required field*): choose the third-party delivery service, like FedEx. Upon choosing a provider, the :guilabel:`Integration Level`, :guilabel:`Invoicing Policy` and :guilabel:`Insurance Percentage` fields become available." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/third_party_shipper.rst:120 -msgid "The price is computed when you save the sale order or when you click on **Set price**." +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/third_party_shipper.rst:114 +msgid ":guilabel:`Integration Level`: choose :guilabel:`Get Rate` to simply get an :ref:`estimated shipment cost ` on an |SO| or invoice." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/third_party_shipper.rst:118 +msgid "Select :guilabel:`Get Rate and Create Shipment` to also :doc:`generate shipping labels <../advanced_operations_shipping/labels>`." msgstr "" #: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/third_party_shipper.rst:123 -msgid "If you want to invoice the price of the delivery charge on the sale order, click on **Set price**, it will add a line with the name of the delivery method as a product. It may vary from the real price." +msgid ":guilabel:`Delivery Product` (*Required field*): the delivery charge name that is added to the |SO| or invoice." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/third_party_shipper.rst:127 -msgid "Otherwise, the real price (computed when the delivery is validated) will automatically be added to the invoice. For more information, please read the document :doc:`../advanced_operations_shipping/invoicing`." +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/third_party_shipper.rst:125 +msgid ":guilabel:`Invoicing Policy`: select and calculate an :guilabel:`Estimated cost` of shipping directly from the shipping carrier. If the :guilabel:`Real cost` of shipping is wanted instead, refer to this :doc:`doc about invoicing real shipping costs <../advanced_operations_shipping/invoicing>`." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/third_party_shipper.rst:132 -msgid "Delivery" +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/third_party_shipper.rst:129 +msgid ":guilabel:`Margin on Rate`: specify an additional percentage amount added to the base shipping rate to cover extra costs, such as handling fees, packaging materials, exchange rates, etc." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/third_party_shipper.rst:134 -msgid "The delivery created from the sale order will take the shipping information from it. You can change the carrier if you want to." +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/third_party_shipper.rst:131 +msgid ":guilabel:`Free if order amount is above`: enables free shipping for orders surpassing a specified amount entered in the corresponding :guilabel:`Amount` field." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/third_party_shipper.rst:143 -msgid "The weight is computed based on the products weights. The shipping cost will be computed once the transfer is validated." +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/third_party_shipper.rst:133 +msgid ":guilabel:`Insurance Percentage`: specify a percentage amount of the shipping costs reimbursed to the senders if the package is lost or stolen in transit." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/third_party_shipper.rst:146 -msgid "Click on **Validate** to receive the tracking number. The **Carrier Tracking ref** field will automatically be filled. Click on the **Tracking** button to check your delivery on the provider website." +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/third_party_shipper.rst:140 +msgid "Screenshot of a FedEx shipping method." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/third_party_shipper.rst:160 -msgid ":doc:`../advanced_operations_shipping/invoicing`" +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/third_party_shipper.rst:140 +msgid "**Shipping Method** configuration page for `FedEx US`." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/third_party_shipper.rst:161 -msgid ":doc:`../advanced_operations_shipping/labels`" +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/third_party_shipper.rst:142 +msgid "In the :guilabel:`Configuration` tab, fill out the API credential fields (e.g. API key, password, account number, etc.). Depending on the third-party shipping carrier chosen in the :guilabel:`Provider` field, the :guilabel:`Configuration` tab will contain different required fields. For more details about configuring specific carriers' credentials, refer to the following documents:" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/third_party_shipper.rst:149 +msgid ":doc:`DHL credentials `" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/third_party_shipper.rst:150 +msgid ":doc:`Sendcloud credentials `" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/third_party_shipper.rst:151 +msgid ":doc:`UPS credentials `" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/third_party_shipper.rst:156 +msgid "Production environment" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/third_party_shipper.rst:158 +msgid "With the delivery method details configured, click the :guilabel:`Test Environment` smart button to set it to :guilabel:`Production Environment`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/third_party_shipper.rst:162 +msgid "Setting the delivery method to :guilabel:`Production` creates **real** shipping labels, and users are at risk of being charged through their carrier account (e.g. UPS, FedEx, etc.) **before** users charge customers for shipping. Verify all configurations are correct before launching the delivery method to :guilabel:`Production`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/third_party_shipper.rst:-1 +msgid "Show the \"Test Environment\" smart button." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/third_party_shipper.rst:176 +msgid "Ensure the warehouse's :guilabel:`Address` (including ZIP code) and :guilabel:`Phone` number are entered accurately. To do that, go to :menuselection:`Inventory app --> Configuration --> Warehouses`, and select the desired warehouse." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/third_party_shipper.rst:180 +msgid "On the warehouse configuration page, open the warehouse contact page by clicking the :guilabel:`Company` field." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/third_party_shipper.rst:-1 +msgid "Highlight the \"Company\" field." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/third_party_shipper.rst:187 +msgid "Verify that the :guilabel:`Address` and :guilabel:`Phone` number are correct, as they are required for the shipping connector to work properly." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/third_party_shipper.rst:-1 +msgid "Show company address and phone number." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/third_party_shipper.rst:197 +msgid "Product weight" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/third_party_shipper.rst:199 +msgid "For the carrier integration to work properly, specify the weight of products by going to :menuselection:`Inventory app --> Products --> Products`, and selecting the desired product." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/third_party_shipper.rst:202 +msgid "Then, switch to the :guilabel:`Inventory` tab, and define the :guilabel:`Weight` of the product in the :guilabel:`Logistics` section." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/third_party_shipper.rst:-1 +msgid "Display the \"Weight\" field in the Inventory tab of the product form." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/third_party_shipper.rst:210 +msgid "Apply third-party shipping carrier" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/third_party_shipper.rst:212 +msgid "Shipping carriers can be applied on a :abbr:`SO (Sales Order)`, invoice, or delivery order." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/third_party_shipper.rst:214 +msgid "After configuring the third-party carrier's :ref:`delivery method ` in Odoo, create or navigate to a quotation by going to :menuselection:`Sales app --> Orders --> Quotations`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/third_party_shipper.rst:221 +msgid "Sales order" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/third_party_shipper.rst:223 +msgid "To assign a third-party shipping carrier, and get an estimated cost of shipping, begin by going to :menuselection:`Sales app --> Orders --> Quotations`. Create or select an existing quotation, and add the cost of shipping through a third-party carrier to a quotation, by clicking the :guilabel:`Add Shipping` button in the bottom-right corner of the :guilabel:`Order Lines` tab." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/third_party_shipper.rst:-1 +msgid "Show the \"Add shipping\" button at the bottom of a quotation." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/third_party_shipper.rst:232 +msgid "In the resulting :guilabel:`Add a shipping method` pop-up window, select the intended carrier from the :guilabel:`Shipping Method` drop-down menu. The :guilabel:`Cost` field is automatically filled based on:" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/third_party_shipper.rst:236 +msgid "the amount specified in the :guilabel:`Total Order Weight` field (if it is not provided, the sum of :ref:`product weights ` in the order is used)" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/third_party_shipper.rst:238 +msgid "the distance between the warehouse's :ref:`source address ` and the customer's address." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/third_party_shipper.rst:243 +msgid "After selecting a third-party provider in the :guilabel:`Shipping Method` field, click :guilabel:`Get Rate` in the :guilabel:`Add a shipping method` pop-up window to get the estimated cost through the shipping connector. Then, click the :guilabel:`Add` button to add the delivery charge to the |SO| or invoice." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/third_party_shipper.rst:249 +msgid ":doc:`Charge customers for shipping after product delivery <../advanced_operations_shipping/invoicing>`" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/third_party_shipper.rst:257 +msgid "For users making shipments without installing the *Sales* app, assign the shipping carrier to the delivery order, by first going to the :menuselection:`Inventory` app. Then, from the :guilabel:`Inventory Overview` dashboard, select the :guilabel:`Delivery Orders` operation type, and choose the desired delivery order that is not already marked as :guilabel:`Done` or :guilabel:`Cancelled`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/third_party_shipper.rst:263 +msgid "In the :guilabel:`Additional info` tab, set the :guilabel:`Carrier` field to the desired third-party shipping carrier. When the delivery method is set to :ref:`production mode `, a :guilabel:`Tracking Reference` is provided." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/third_party_shipper.rst:269 +msgid ":doc:`Generate shipping labels <../advanced_operations_shipping/labels>`" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/third_party_shipper.rst:-1 +msgid "Show the delivery order's \"Additional info\" tab." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/third_party_shipper.rst:278 +msgid "Troubleshooting" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/third_party_shipper.rst:280 +msgid "Since shipping connectors can sometimes be complex to set up, here are some checks to try when things are not working as expected:" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/third_party_shipper.rst:283 +msgid "Ensure the :ref:`warehouse information ` (e.g., address and phone number) in Odoo is correct **and** matches the records saved in the shipping provider's website." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/third_party_shipper.rst:286 +msgid "Verify that the :ref:`package type ` and parameters are valid for the shipping carrier. To check, ensure the shipment can be directly created on the shipping carrier's website." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/third_party_shipper.rst:289 +msgid "When encountering a price mismatch between Odoo's estimated cost and the provider's charge, first ensure the delivery method is set to :ref:`production environment `." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/third_party_shipper.rst:293 +msgid "Then, create the shipment in both the carrier's website and Odoo, and verify the prices are the same across Odoo, the shipping provider, and in the *debug logs*." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/third_party_shipper.rst:297 +msgid "When checking for a price mismatch in the debug logs, if the request says the package weighs six kilograms, but the response from FedEx says the package weights seven kilograms, it concludes that the issue is on FedEx's side." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/third_party_shipper.rst:302 +msgid "Debug log" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/third_party_shipper.rst:304 +msgid "Track shipping data inconsistencies by activating debug logging. To do that, go to the delivery method's configuration page (:menuselection:`Inventory app --> Configuration --> Shipping Method`), and select the desired shipping method. Click the :guilabel:`No Debugging` smart button to activate :guilabel:`Debug Requests`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/third_party_shipper.rst:-1 +msgid "Show the \"No Debug\" smart button." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/third_party_shipper.rst:313 +msgid "With :guilabel:`Debug Requests` activated, each time the shipping connector is used to estimate the cost of shipping, records are saved in the :guilabel:`Logging` report. To access the report, turn on :ref:`developer mode `, and go to :menuselection:`Settings app --> Technical --> Database Structure section --> Logging`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/third_party_shipper.rst:319 +msgid "Logs are created for a shipping method each time the :ref:`Get Rate ` button is clicked on :abbr:`SOs (Sales Orders)` and invoices, **and** when a customer adds the shipping carrier to their order through the *Website* app." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/third_party_shipper.rst:-1 +msgid "Show how to find the \"Logging\" option from the \"Technical\" menu." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/third_party_shipper.rst:328 +msgid "Click the *HTTP request* line item to open a detailed page, and verify the correct information is sent from Odoo to the shipping carrier. In the *HTTP response*, verify that the same information is received." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/third_party_shipper.rst:-1 +msgid "Show debug request history in Settings > Technical > Logging." msgstr "" #: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/ups_credentials.rst:3 -msgid "How to get UPS credentials for integration with Odoo?" +msgid "UPS integration" msgstr "" #: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/ups_credentials.rst:5 -msgid "In order to use the Odoo UPS API, you will need:" +msgid "UPS is a shipping carrier service that integrates with Odoo to coordinate shipping to all regions. Once integrated, users can create shipping methods that estimate shipping costs and :doc:`generate labels <../advanced_operations_shipping/labels>`." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/ups_credentials.rst:7 -msgid "A UPS.com user ID and password" +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/ups_credentials.rst:10 +msgid ":doc:`third_party_shipper`" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/ups_credentials.rst:9 -msgid "A UPS account number" +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/ups_credentials.rst:12 +msgid "To set up the UPS shipping connector in Odoo, complete these steps:" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/ups_credentials.rst:11 -msgid "An Access Key" +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/ups_credentials.rst:14 +msgid "Create a UPS account to get :ref:`account number `" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/ups_credentials.rst:13 -msgid "An Access Key is a 16 character alphanumeric code that allows access to the UPS Developer Kit API Development and Production servers." +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/ups_credentials.rst:16 +msgid "Create UPS developer account to get :ref:`client credentials `" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/ups_credentials.rst:17 -msgid "Create a UPS Account" +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/ups_credentials.rst:18 +msgid "Set up shipping method in Odoo" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/ups_credentials.rst:19 -msgid "Note that only customers located in the US can open a UPS account online. If you are located outside the US, you will need to contact UPS Customer Service in order to to open an account." +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/ups_credentials.rst:21 +msgid "UPS account setup" msgstr "" #: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/ups_credentials.rst:23 -msgid "You can read additional information about opening a UPS account on the their website, on the page, `How to Open a UPS Account Online `_" +msgid "To get started, go to the `UPS website `_ and click the :guilabel:`Log In` button in the top-right corner to log in or create a UPS account." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/ups_credentials.rst:27 -msgid "If you don't already have a UPS account, you can create one along with your online profile by following these steps:" +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/ups_credentials.rst:26 +msgid "After logging in, click the profile icon in the top-right corner, and select :guilabel:`Accounts and Payment` from the drop-down menu." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/ups_credentials.rst:30 -msgid "1. Access the UPS.com web site at `www.ups.com `__, and click the **New User** link at the top of the page." +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/ups_credentials.rst:-1 +msgid "Show how to navigate to the \"Accounts and Payment\" page from the home screen." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/ups_credentials.rst:34 -msgid "2. Click the **Register for MyUPS** button, and follow the prompts to complete the registration process." +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/ups_credentials.rst:33 +msgid "On the :guilabel:`Accounts and Payment Options` page, two accounts must be configured: an Odoo shipment account and a payment card." msgstr "" #: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/ups_credentials.rst:37 -msgid "If you already have a UPS account, you can add it to your online profile as follows:" +msgid "Shipping account" msgstr "" #: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/ups_credentials.rst:39 -msgid "Log in to the `UPS.com website `_) using your UPS.com User ID and Password." +msgid "To add an Odoo shipment account, select :guilabel:`Add New Account` from the :guilabel:`Add a Payment Method` drop-down menu, and click :guilabel:`Add`." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/ups_credentials.rst:41 -msgid "Click the **My UPS** tab." +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/ups_credentials.rst:-1 +msgid "Display \"Add an account\" option from the drop-down menu." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/ups_credentials.rst:43 -msgid "Click the **Account Summary** link." +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/ups_credentials.rst:46 +msgid "On the next screen, labeled :guilabel:`Open a Shipping Account`, complete the forms to configure the shipping account type (e.g. :guilabel:`Business`) and if any regulated items will be shipped. Then finish the remaining three steps in the wizard to :guilabel:`Add Addresses`, :guilabel:`Verify Identity`, and :guilabel:`Explore Discounts`, with the last option being optional." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/ups_credentials.rst:45 -msgid "4. Click the **Add an Existing UPS Account** link in the **UPS Account Details** section of the page." +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/ups_credentials.rst:51 +msgid "When complete, submit the application on the last page of the wizard to finish setting up the shipping account." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/ups_credentials.rst:48 -msgid "5. In the **Add New Account** screen, enter the **UPS Account Number**, **Account Name**, and **Postal Code** fields. The country defaults to United States.q" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/ups_credentials.rst:52 -msgid "Click the **Next** button to continue." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/ups_credentials.rst:55 -msgid "Get an Access Key" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/ups_credentials.rst:57 -msgid "After you have added your UPS account number to your user profile you can request an Access Key from UPS using the steps below:" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/ups_credentials.rst:60 -msgid "Go to the `UPS Developer Kit web page `_" +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/ups_credentials.rst:-1 +msgid "Display UPS form to fill out company shipping information." msgstr "" #: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/ups_credentials.rst:61 -msgid "Log into UPS.com with your user ID and password" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/ups_credentials.rst:62 -msgid "Click on the link **Request an access key**." +msgid "Get account number" msgstr "" #: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/ups_credentials.rst:63 -msgid "Verify your contact information" +msgid "With the shipping account set up, the UPS :guilabel:`Account Number` becomes available. To access it, navigate to :menuselection:`Profile --> Accounts and Payment` and refer to the shipping account's :guilabel:`Number` field." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/ups_credentials.rst:64 -msgid "Click the **Request Access Key** button." +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/ups_credentials.rst:-1 +msgid "Show Account \"Number\" field for the shipping account." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/ups_credentials.rst:66 -msgid "The **Access Key** will be provided to you on the web page, and an email with the Access Key will be sent to the email address of the primary contact." +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/ups_credentials.rst:72 +msgid "Payment card" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/ups_credentials.rst:74 +msgid "Navigate back to the :guilabel:`Accounts and Payments` page and select the :guilabel:`Add Payment Card` option from the :guilabel:`Add a Payment Method` drop-down menu. Then, complete the form to add the credit card information." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/ups_credentials.rst:-1 +msgid "Show \"Add Payment Card\" option from the drop-down." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/ups_credentials.rst:83 +msgid "UPS developer account setup" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/ups_credentials.rst:85 +msgid "Next, log into the `UPS developer account `_ to generate the developer key. To begin, click the profile icon in the top-right corner, and choose the :guilabel:`Apps` option from the drop-down menu." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/ups_credentials.rst:-1 +msgid "Display the \"Apps\" drop-down option after clicking the profile picture icon." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/ups_credentials.rst:94 +msgid "Add app" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/ups_credentials.rst:96 +msgid "Then, click the :guilabel:`Add Apps` button to begin filling out the form. In the :guilabel:`I need API credentials because \\*` field, select :guilabel:`I want to integrate UPS technology into my business`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/ups_credentials.rst:100 +msgid "Under the next label, :guilabel:`Choose an account to associate with these credentials. \\*`, select :guilabel:`Add existing account` from the drop-down menu in the corresponding field, and then select the :ref:`account number ` linked to the UPS account created in the previous step." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/ups_credentials.rst:-1 +msgid "Show form to fill in the UPS account number." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/ups_credentials.rst:109 +msgid "Click :guilabel:`Next`, and proceed to the :guilabel:`Add App` form, and fill out the fields:" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/ups_credentials.rst:111 +msgid ":guilabel:`App Name`: Type the name to identify the app by." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/ups_credentials.rst:112 +msgid ":guilabel:`Callback URL`: Type the URL of the Odoo database, in the format: `https://databaseName.odoo.com`. Do **not** include `www` in the URL." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/ups_credentials.rst:115 +msgid "In the :guilabel:`Add Products` section on the right, search for and click the :guilabel:`+ (plus)` icon to add the following products to the app:" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/ups_credentials.rst:118 +msgid ":guilabel:`Authorization (O Auth)`: Used to generate the authorization token to request information from the UPS API." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/ups_credentials.rst:120 +msgid ":guilabel:`Address Validation`: Validates addresses at the street level in the United States and Puerto Rico." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/ups_credentials.rst:122 +msgid ":guilabel:`Locator`: Enables search for UPS shipping locations based on type and available services." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/ups_credentials.rst:124 +msgid ":guilabel:`Paperless Documents`: Enables the upload of document images to link to shipments." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/ups_credentials.rst:125 +msgid ":guilabel:`Shipping`: Enables UPS shipping services, such as preparing packages for shipment, managing returns, and canceling scheduled shipments." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/ups_credentials.rst:127 +msgid ":guilabel:`Rating`: Compare delivery services and shipping rates." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/ups_credentials.rst:129 +msgid "Finally, click :guilabel:`Save` and accept UPS's terms and conditions." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/ups_credentials.rst:132 +msgid "`UPS API Catalog `_" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/ups_credentials.rst:-1 +msgid "Show \"Add Apps\" form, where the app details are configured." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/ups_credentials.rst:141 +msgid "Client ID and Client Secret" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/ups_credentials.rst:143 +msgid "With the new app created, in the :menuselection:`Profile --> My Apps --> App` page, select the app from the :guilabel:`Credentials` section to view the UPS credentials." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/ups_credentials.rst:-1 +msgid "Show newly created app in the \"My Apps\" section." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/ups_credentials.rst:150 +msgid "In the :guilabel:`Credentials` section, copy the :guilabel:`Client ID` and :guilabel:`Client Secret` key." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/ups_credentials.rst:-1 +msgid "Display the \"Client ID\" and \"Client Secret\" key." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/ups_credentials.rst:160 +msgid "With the credentials obtained, configure the UPS shipping method in Odoo by going to :menuselection:`Inventory app --> Configuration --> Shipping Methods`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/ups_credentials.rst:163 +msgid "On the :guilabel:`Shipping Methods` page, click the :guilabel:`New` button." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/ups_credentials.rst:166 +msgid "For existing UPS shipping methods whose :guilabel:`Provider` is :guilabel:`UPS Legacy`, archive it and create a new shipping method using :guilabel:`UPS`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/ups_credentials.rst:169 +msgid "In the :guilabel:`Provider` field, select :guilabel:`UPS`. Doing so reveals the :guilabel:`UPS Configuration` tab, where various fields must be entered. For details instructions on configuring the other fields on the shipping method, refer to the :doc:`Configure third-party carrier ` documentation." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/ups_credentials.rst:174 +msgid "In the :guilabel:`UPS Configuration` tab, complete the following fields:" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/ups_credentials.rst:176 +msgid ":guilabel:`UPS Account Number`: (*required*) Get the :ref:`account number ` from the UPS portal." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/ups_credentials.rst:178 +msgid ":guilabel:`UPS Client ID`: (*required*) Get the :ref:`Client ID ` from the UPS developer website." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/ups_credentials.rst:180 +msgid ":guilabel:`UPS Client Secret`: (*required*) Get the :ref:`Client Secret ` key from the UPS developer website." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/ups_credentials.rst:182 +msgid ":guilabel:`UPS Service Type`: Select from the drop-down menu the type of shipping service." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/ups_credentials.rst:183 +msgid ":guilabel:`UPS Package Type`: (*required*) Select from the drop-down menu the :doc:`package type <../../product_management/product_tracking/package>` that is supported for the shipping service." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/ups_credentials.rst:185 +msgid ":guilabel:`Package Weight Unit`: The unit of measure for the package weight." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/ups_credentials.rst:186 +msgid ":guilabel:`Package Size Unit`: The unit of measure for the package dimensions." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/ups_credentials.rst:187 +msgid ":guilabel:`Label Format`: Choose the label format shipping labels: :guilabel:`PDF`, :guilabel:`ZPL`, :guilabel:`EPL`, or :guilabel:`SPL`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/ups_credentials.rst:-1 +msgid "Show the \"UPS Configuration\" tab on the Shipping Methods form." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/ups_credentials.rst:194 +msgid "In the :guilabel:`Options` section, the following features are available:" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/ups_credentials.rst:196 +msgid ":guilabel:`Bill My Account`: Charge the user's UPS account for shipping in the *eCommerce* app." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/ups_credentials.rst:197 +msgid ":guilabel:`Collect on Delivery`: Collect payment from customers for shipping after the shipment is delivered." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/ups_credentials.rst:199 +msgid ":guilabel:`Generate Return Label`: Print the return label for the order after the delivery order is validated." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/ups_credentials.rst:201 +msgid ":guilabel:`Duties paid by`: Select whether duties or other fees are charged to the :guilabel:`Sender` or :guilabel:`Recipient` of the order." msgstr "" #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage.rst:5 @@ -8458,7 +9073,7 @@ msgid "In a batch transfer for 2 `Cabinet with Doors`, 3 `Acoustic Bloc Screens` msgstr "" #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/batch_transfers.rst:229 -msgid "`1/2` units of the `Cabinet with Doors` has already been picked, and after scanning the product barcode for the second cabinet, Odoo prompts the user to `Scan a serial number` to record the unique serial number for :ref:`product tracking `." +msgid "`1/2` units of the `Cabinet with Doors` has already been picked, and after scanning the product barcode for the second cabinet, Odoo prompts the user to `Scan a serial number` to record the unique serial number for :ref:`product tracking `." msgstr "" #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/batch_transfers.rst:0 @@ -8777,135 +9392,6 @@ msgstr "" msgid "The delivery order is now ready to be processed and can be validated too." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/cycle_counts.rst:3 -msgid "Cycle counts" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/cycle_counts.rst:5 -msgid "For most companies, warehouse stock only needs to be counted once a year. This is why, by default, after making an *inventory adjustment* in Odoo, the scheduled date for the next inventory count is set for the 31st of December of the current year." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/cycle_counts.rst:9 -msgid "However, for some businesses, it's crucial to have an accurate inventory count at all times. These companies use *cycle counts* to keep critical stock levels accurate. Cycle counting is a method by which companies count their inventory more often in certain *locations*, to ensure that their physical inventory counts match their inventory records." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/cycle_counts.rst:15 -msgid "Activate storage locations" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/cycle_counts.rst:17 -msgid "In Odoo, cycle counts are location-based. Therefore, the *storage locations* feature needs to be enabled before performing a cycle count." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/cycle_counts.rst:20 -msgid "To enable this feature, navigate to :menuselection:`Inventory app --> Configuration --> Settings`, and scroll down to the :guilabel:`Warehouse` section. Then, click the checkbox next to :guilabel:`Storage Locations`. Click :guilabel:`Save` to save all changes." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/cycle_counts.rst:-1 -msgid "Enabled storage locations setting in inventory settings." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/cycle_counts.rst:29 -msgid "Change inventory count frequency by location" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/cycle_counts.rst:31 -msgid "Now that the storage locations setting is enabled, the inventory count frequency can be changed for specific locations created in the warehouse." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/cycle_counts.rst:34 -msgid "To view and edit locations, navigate to :menuselection:`Inventory app --> Configuration --> Locations`. This reveals a :guilabel:`Locations` page containing every location currently created and listed in the warehouse." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/cycle_counts.rst:38 -msgid "From this page, click into a location to reveal the settings and configuration page for that location. Click :guilabel:`Edit` to edit the location settings." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/cycle_counts.rst:41 -msgid "Under the :guilabel:`Cyclic Inventory` section, locate the :guilabel:`Inventory Frequency (Days)` field, which should be set to `0` (if this location has not been edited previously). In this field, change the value to whichever number of days is desired." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/cycle_counts.rst:-1 -msgid "Location frequency setting on location." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/cycle_counts.rst:50 -msgid "A location that needs an inventory count every 30 days should have the :guilabel:`Inventory Frequency (Days)` value set to `30`." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/cycle_counts.rst:53 -msgid "Once the frequency has been changed to the desired number of days, click :guilabel:`Save` to save changes. Now, once an inventory adjustment is applied to this location, the next scheduled count date is automatically set, based on the value entered into the :guilabel:`Inventory Frequency (Days)` field." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/cycle_counts.rst:59 -msgid "Count inventory by location" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/cycle_counts.rst:61 -msgid "To perform a cycle count for a specific location in the warehouse, navigate to :menuselection:`Inventory app --> Operations --> Inventory Adjustments`. This reveals an :guilabel:`Inventory Adjustments` page containing all products currently in stock, with each product listed on its own line." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/cycle_counts.rst:66 -msgid "From this page, the :guilabel:`Filters` and :guilabel:`Group By` buttons (at the top of the page, under the :guilabel:`Search...` bar), can be used to select specific locations and perform inventory counts." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/cycle_counts.rst:-1 -msgid "Inventory adjustments page." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/cycle_counts.rst:74 -msgid "To select a specific location and view all products within that location, click :guilabel:`Group By`, then click :guilabel:`Add Custom Group` to reveal a new drop-down menu to the right." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/cycle_counts.rst:77 -msgid "Click :guilabel:`Location` from the drop-down menu, then click :guilabel:`Apply`. The page now displays condensed drop-down menus of each location in the warehouse that has products in stock, and a cycle count can be performed for all products in that location." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/cycle_counts.rst:82 -msgid "In large warehouses with multiple locations and a high volume of products, it might be easier to search for the specific location desired. To do this, from the :guilabel:`Inventory Adjustments` page, click :guilabel:`Filters`. Then, click :guilabel:`Add Custom Filter` to reveal a new menu to the right. Click this menu to reveal three drop-downs." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/cycle_counts.rst:87 -msgid "For the first field, click and select :guilabel:`Location` from the drop-down. For the second field, leave the :guilabel:`contains` value as is. For the third field, type in the name of the location that is being searched for. Click :guilabel:`Apply` for that location to appear on the page." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/cycle_counts.rst:-1 -msgid "Applied filters and group by on inventory adjustments page." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/cycle_counts.rst:97 -msgid "Change full inventory count frequency" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/cycle_counts.rst:99 -msgid "While cycle counts are typically performed per location, the scheduled date for full inventory counts of everything in-stock in the warehouse can also be manually changed to push the date up sooner than the date listed." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/cycle_counts.rst:103 -msgid "To modify the default scheduled date, go to :menuselection:`Inventory app --> Configuration --> Settings`. Then, in the :guilabel:`Operations` section, locate the :guilabel:`Annual Inventory Day and Month` setting field, which includes a drop-down that is set to `31` :guilabel:`December` by default." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/cycle_counts.rst:-1 -msgid "Frequency field in inventory app settings." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/cycle_counts.rst:112 -msgid "To change the day, click the `31`, and change it to a day within the range `1-31`, depending on the desired month of the year." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/cycle_counts.rst:115 -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/count_products.rst:196 -msgid "Then, to change the month, click :guilabel:`December` to reveal the drop-down menu, and select the desired month." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/cycle_counts.rst:118 -msgid "Once all changes have been made, click :guilabel:`Save` to save all changes." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/cycle_counts.rst:121 -msgid ":doc:`../inventory_management/count_products`" -msgstr "" - #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/owned_stock.rst:3 msgid "Consignment: buy and sell stock without owning it" msgstr "" @@ -9626,15 +10112,15 @@ msgstr "" msgid "Inventory adjustments" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/count_products.rst:7 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/count_products.rst:5 msgid "In any warehouse management system, the recorded inventory counts in the database might not always match the actual inventory counts in the warehouse. The discrepancy between the two counts can be due to damages, human errors, theft, or other factors. As such, inventory adjustments must be made to reconcile the differences, and ensure that the recorded counts in the database match the actual counts in the warehouse." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/count_products.rst:14 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/count_products.rst:12 msgid "Inventory Adjustments page" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/count_products.rst:16 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/count_products.rst:14 msgid "To view the *Inventory Adjustments* page, navigate to :menuselection:`Inventory app --> Operations --> Inventory Adjustments`." msgstr "" @@ -9642,100 +10128,100 @@ msgstr "" msgid "In stock products listed on the Inventory adjustments page." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/count_products.rst:23 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/count_products.rst:21 msgid "On the :guilabel:`Inventory Adjustments` page, all products that are currently in stock are listed, with each product line containing the following information:" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/count_products.rst:26 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/count_products.rst:24 msgid ":guilabel:`Location`: the specific location in the warehouse where a product is stored." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/count_products.rst:27 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/count_products.rst:25 msgid ":guilabel:`Product`: the product whose quantity is listed on the inventory adjustment line." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/count_products.rst:28 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/count_products.rst:26 msgid ":guilabel:`Lot/Serial Number`: the tracking identifier assigned to the specific product listed. It can contain letters, numbers, or a combination of both." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/count_products.rst:32 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/count_products.rst:30 msgid "If a specific product has a quantity of more than `1.00` in stock, and more than one serial number (or lot number) assigned to it, each uniquely-identified product is displayed on its own product line with its own lot/serial number, displayed under the :guilabel:`Lot/Serial Number` column." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/count_products.rst:37 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/count_products.rst:35 msgid ":guilabel:`On Hand Quantity`: the quantity of the product currently recorded in the database." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/count_products.rst:38 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/count_products.rst:36 msgid ":guilabel:`UoM`: the *unit of measure* in which the product is measured. Unless otherwise specified (i.e., in :guilabel:`Pounds` or :guilabel:`Ounces`), the default :abbr:`UoM (Unit of Measure)` is :guilabel:`Units`." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/count_products.rst:41 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/count_products.rst:39 msgid ":guilabel:`Counted Quantity`: the real quantity counted during an inventory count. This field is left blank by default, but can be changed, depending on if it matches the :guilabel:`On Hand Quantity` or not." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/count_products.rst:44 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/count_products.rst:42 msgid ":guilabel:`Difference`: the difference between the :guilabel:`On Hand Quantity` and :guilabel:`Counted Quantity`, once an inventory adjustment is made. The difference is automatically calculated after every inventory adjustment." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/count_products.rst:47 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/count_products.rst:45 msgid ":guilabel:`Scheduled Date`: the date at which a count should be made. If not otherwise specified, this date will default to the 31st of December of the current year." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/count_products.rst:49 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/count_products.rst:47 msgid ":guilabel:`User`: the person assigned to the count in the database. This can either be the person physically counting the inventory, or applying the count in the database." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/count_products.rst:51 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/count_products.rst:49 msgid ":guilabel:`Product Category`: the category assigned internally to a specific product. Unless otherwise specified (i.e., as :guilabel:`Consumable` or :guilabel:`Rental`), the default *Product Category* is set to :guilabel:`All`." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/count_products.rst:54 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/count_products.rst:52 msgid ":guilabel:`Available Quantity`: the quantity of a specific product that is currently available, based on any outstanding/uncompleted sales orders, purchase orders, or manufacturing orders that might change the available quantity once fulfilled." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/count_products.rst:57 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/count_products.rst:55 msgid ":guilabel:`Accounting Date`: the date on which the adjustments will be accounted in the Odoo *Accounting* app." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/count_products.rst:59 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/count_products.rst:57 msgid ":guilabel:`Company`: the company whose database these inventory adjustments are being made on. The company is listed in the top right corner of the database, next to the user currently logged in." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/count_products.rst:63 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/count_products.rst:61 msgid "Some columns are hidden by default. To reveal these columns, click the :guilabel:`additional options` button (three dots icon) to the far right of the form's top row, and select any desired column to reveal by clicking the checkbox next to that option." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/count_products.rst:68 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/count_products.rst:66 msgid "Create an inventory adjustment" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/count_products.rst:70 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/count_products.rst:68 msgid "To create a new inventory adjustment from the :menuselection:`Inventory Adjustments` page, click :guilabel:`Create`. Doing so creates a new, blank inventory adjustment line at the bottom of the page." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/count_products.rst:74 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/count_products.rst:72 msgid "On this blank inventory adjustment line, click the drop-down menu under the :guilabel:`Product` column, and select a product. If the selected product is tracked using either lots or serial numbers, the desired lot or serial number can also be chosen from the drop-down menu under the :guilabel:`Lot/Serial Number` column." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/count_products.rst:79 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/count_products.rst:77 msgid "Next, set the value in the :guilabel:`Counted Quantity` column to the quantity counted for that product during the inventory adjustment process." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/count_products.rst:83 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/count_products.rst:81 msgid "The :guilabel:`Counted Quantity` for new inventory adjustments is set to `0.00` by default. An inventory move with `0.00` :guilabel:`Quantity Done` is recorded in the product's inventory adjustment history, so it should be set to reflect the actual quantity counted." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/count_products.rst:87 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/count_products.rst:85 msgid "To the right of the :guilabel:`Counted Quantity` column, the :guilabel:`Scheduled Date` and :guilabel:`User` can also be changed via their respective drop-down menus. Changing the :guilabel:`Scheduled Date` changes the date that the inventory adjustment should be processed on, and selecting a responsible :guilabel:`User` assigns a user to the specific inventory adjustment (for traceability purposes)." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/count_products.rst:93 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/count_products.rst:91 msgid "Once all changes have been made to the new inventory adjustment line, click away from the line. Doing so saves the adjustment, and moves the line to the top of the page." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/count_products.rst:96 -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/count_products.rst:158 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/count_products.rst:94 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/count_products.rst:156 msgid "If the :guilabel:`Counted Quantity` is greater than the :guilabel:`On Hand Quantity`, the value in the :guilabel:`Difference` column is **green**. If the :guilabel:`Counted Quantity` is less than the :guilabel:`On Hand Quantity`, the value in the :guilabel:`Difference` column is **red**. If the quantities match, and haven't been changed at all, no value appears in the :guilabel:`Difference` column." msgstr "" @@ -9743,19 +10229,19 @@ msgstr "" msgid "Difference column on inventory adjustments page." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/count_products.rst:106 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/count_products.rst:104 msgid "At this stage, the count (:dfn:`inventory adjustment`) is recorded, but not yet applied. This means that the quantity on hand before the adjustment has not yet been updated to match the new, real counted quantity." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/count_products.rst:110 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/count_products.rst:108 msgid "There are two ways to apply the new inventory adjustment. The first way is to click the :guilabel:`Apply` button on the line at the far right of the page. The second way is to click the checkbox on the far left of the line. Doing so reveals new button options at the top of the page, one of which is an :guilabel:`Apply` button. Clicking this button instead causes an :guilabel:`Inventory Adjustment Reference / Reason` pop-up window to appear." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/count_products.rst:116 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/count_products.rst:114 msgid "From this pop-up menu, a reference or reason can be assigned to the inventory adjustment. By default, the :guilabel:`Inventory Reference / Reason` field is pre-populated with the date the adjustment is being made on, but can be changed to reflect whatever reference or reason is desired." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/count_products.rst:120 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/count_products.rst:118 msgid "Once ready, click :guilabel:`Apply` to apply the inventory adjustment." msgstr "" @@ -9763,19 +10249,19 @@ msgstr "" msgid "Apply all option applies the inventory adjustment once a reason is specified." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/count_products.rst:127 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/count_products.rst:125 msgid "Count products" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/count_products.rst:129 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/count_products.rst:127 msgid "Counting products is a recurring activity in a warehouse. Once a count is complete, go to :menuselection:`Inventory app --> Operations --> Inventory Adjustments` to update the :guilabel:`Counted Quantity` column for each product line." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/count_products.rst:133 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/count_products.rst:131 msgid "On each product line, identify whether the value in the :guilabel:`On Hand Quantity` column recorded in the database matches the newly-counted value. If the recorded value and the counted value do match, click the :guilabel:`Set` button (target icon) at the far right of the product line." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/count_products.rst:137 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/count_products.rst:135 msgid "Doing so copies the value from the :guilabel:`On Hand Quantity` column over to the :guilabel:`Counted Quantity` column, and sets the value of the :guilabel:`Difference` column to `0.00`. Subsequently, once applied, an inventory move with `0.00` :guilabel:`Quantity Done` is recorded in the product's inventory adjustment history." msgstr "" @@ -9783,19 +10269,19 @@ msgstr "" msgid "Zero count inventory adjustment move." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/count_products.rst:146 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/count_products.rst:144 msgid "If the newly-counted value for a given product does **not** match the value in the :guilabel:`On Hand Quantity` recorded in the database, instead of clicking the :guilabel:`Set` button, record the real value in the field in the :guilabel:`Counted Quantity` column." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/count_products.rst:150 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/count_products.rst:148 msgid "To do so, click the field in the :guilabel:`Counted Quantity` column on the specific inventory adjustment line for the product whose count is being changed. This automatically assigns a :guilabel:`Counted Quantity` of `0.00`." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/count_products.rst:154 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/count_products.rst:152 msgid "To change this value, type in a new value that matches the real, newly-counted value. Then, click away from the line. Doing so saves the adjustment, and automatically adjusts the value in the :guilabel:`Difference` column." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/count_products.rst:164 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/count_products.rst:162 msgid "Subsequently, once applied, a move with the difference between the :guilabel:`On Hand Quantity` and the :guilabel:`Counted Quantity` is recorded in the product's inventory adjustment history." msgstr "" @@ -9803,19 +10289,19 @@ msgstr "" msgid "Inventory Adjustments History dashboard detailing a list of prior product moves." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/count_products.rst:172 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/count_products.rst:170 msgid "Sometimes a count occurs, but cannot be applied in the database right away. In the time between the actual count and applying the inventory adjustment, product moves can occur. In that case, the on-hand quantity in the database can change and no longer be consistent with the counted quantity. As an extra precaution, Odoo asks for confirmation before applying the inventory adjustment." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/count_products.rst:179 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/count_products.rst:177 msgid "Change inventory count frequency" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/count_products.rst:181 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/count_products.rst:179 msgid "By default, the *scheduled date* for inventory adjustments are always scheduled for the 31st of December of the current year. However, for some companies, it is crucial that they have an accurate inventory count at all times. In such cases, the default scheduled date can be modified." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/count_products.rst:185 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/count_products.rst:183 msgid "To modify the default scheduled date, go to :menuselection:`Inventory app --> Configuration --> Settings`. Then, in the :guilabel:`Operations` section, locate the :guilabel:`Annual Inventory Day and Month` setting, which includes a drop-down menu that is set to `31 December` by default." msgstr "" @@ -9823,27 +10309,32 @@ msgstr "" msgid "Adjust the next inventory count date with the Annual Inventory Day and Month setting." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/count_products.rst:193 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/count_products.rst:191 msgid "To change the day, click the :guilabel:`31`, and change it to a day within the range `1-31`, depending on the desired month of the year." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/count_products.rst:199 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/count_products.rst:194 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/cycle_counts.rst:117 +msgid "Then, to change the month, click :guilabel:`December` to reveal the drop-down menu, and select the desired month." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/count_products.rst:197 msgid "Once all desired changes have been made, click :guilabel:`Save` to save all changes." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/count_products.rst:202 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/count_products.rst:200 msgid "Plan big inventory counts" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/count_products.rst:204 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/count_products.rst:202 msgid "To plan big inventory counts, such as a full count of everything currently in stock, first navigate to :menuselection:`Inventory app --> Operations --> Inventory Adjustments`." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/count_products.rst:207 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/count_products.rst:205 msgid "Then, select the desired products to be counted by clicking the checkbox on the far left of each product line." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/count_products.rst:211 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/count_products.rst:209 msgid "To request a count of **all** products currently in stock, click the checkbox at the very top of the table, in the header row next to the :guilabel:`Location` label. This selects **all** product lines." msgstr "" @@ -9851,36 +10342,36 @@ msgstr "" msgid "Request a count popup on inventory adjustments page." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/count_products.rst:219 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/count_products.rst:217 msgid "Once all desired products have been selected, click the :guilabel:`Request a Count` button at the top of the page. This causes a :guilabel:`Request a Count` pop-up window to appear. From this pop-up, fill in the following information:" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/count_products.rst:223 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/count_products.rst:221 msgid ":guilabel:`Inventory Date`: the planned date of the count." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/count_products.rst:224 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/count_products.rst:222 msgid ":guilabel:`User`: the user responsible for the count." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/count_products.rst:225 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/count_products.rst:223 msgid ":guilabel:`Accounting Date`: the date at which the inventory adjustment will be accounted." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/count_products.rst:226 -msgid ":guilabel:`Count`: to leave the on-hand quantity of each product line blank, select :guilabel:`Leave Empty`. To prefill the on-hand quantity of each product line with the current value recorded in the database, select :guilabel:`Set Current Value`." +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/count_products.rst:224 +msgid ":guilabel:`Count`: to leave the on-hand quantity of each product line blank, select :guilabel:`Leave Empty`. To pre-fill the on-hand quantity of each product line with the current value recorded in the database, select :guilabel:`Set Current Value`." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/count_products.rst:230 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/count_products.rst:228 msgid "Finally, once ready, click :guilabel:`Confirm` to request the count." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/count_products.rst:233 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/count_products.rst:231 msgid "In the Odoo *Barcode* app, users can only view inventory counts that are assigned to **them**, and are scheduled for **today** or **earlier**." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/count_products.rst:237 -msgid ":doc:`/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/cycle_counts`" +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/count_products.rst:235 +msgid ":doc:`cycle_counts`" msgstr "" #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/create_a_second_warehouse.rst:3 @@ -10031,6 +10522,138 @@ msgstr "" msgid "After adding all the products already stored in the new warehouse, click :guilabel:`Validate Inventory` to complete the inventory adjustment. The values in the :guilabel:`On Hand` column will update to reflect those in the :guilabel:`Counted` column and the products added will appear in the inventory of the new warehouse." msgstr "" +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/cycle_counts.rst:3 +msgid "Cycle counts" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/cycle_counts.rst:5 +msgid "For most companies, warehouse stock only needs to be counted once a year. This is why, by default, after making an *inventory adjustment* in Odoo, the scheduled date for the next inventory count is set for the 31st of December of the current year." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/cycle_counts.rst:9 +msgid "However, for some businesses, it's crucial to have an accurate inventory count at all times. These companies use *cycle counts* to keep critical stock levels accurate. Cycle counting is a method by which companies count their inventory more often in certain *locations*, to ensure that their physical inventory counts match their inventory records." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/cycle_counts.rst:17 +msgid "In Odoo, cycle counts are performed by location. Therefore, the *Storage Locations* feature needs to be enabled before performing a cycle count." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/cycle_counts.rst:20 +msgid "To enable this feature, navigate to :menuselection:`Inventory app --> Configuration --> Settings`, and scroll down to the :guilabel:`Warehouse` section. Then, tick the checkbox next to :guilabel:`Storage Locations`, and click :guilabel:`Save`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/cycle_counts.rst:-1 +msgid "Enabled Storage Locations setting in inventory settings." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/cycle_counts.rst:29 +msgid "Change inventory count frequency by location" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/cycle_counts.rst:31 +msgid "Once the *Storage Locations* feature is enabled, and there are multiple locations created in the warehouse, the inventory count frequency can be changed for specific locations." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/cycle_counts.rst:34 +msgid "To view and edit locations, navigate to :menuselection:`Inventory app --> Configuration --> Locations`. This reveals a :guilabel:`Locations` page containing every location currently created and listed in the warehouse." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/cycle_counts.rst:38 +msgid "From this page, click into a location to reveal the settings and configuration page for that location." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/cycle_counts.rst:41 +msgid "Under the :guilabel:`Cyclic Counting` section, locate the :guilabel:`Inventory Frequency (Days)` field, which should be set to `0` by default (if this location has not been edited previously). In this field, change the value to any number of days desired for the frequency of counts." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/cycle_counts.rst:-1 +msgid "Location frequency setting on location." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/cycle_counts.rst:50 +msgid "A location that needs an inventory count every 30 days should have the :guilabel:`Inventory Frequency (Days)` value set to `30`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/cycle_counts.rst:53 +msgid "Now, once an inventory adjustment is applied to this location, the next scheduled count date is automatically set, based on the value entered into the :guilabel:`Inventory Frequency (Days)` field." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/cycle_counts.rst:57 +msgid "Count inventory by location" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/cycle_counts.rst:59 +msgid "To perform a cycle count for a specific location in the warehouse, navigate to :menuselection:`Inventory app --> Operations --> Physical Inventory`. This reveals an :guilabel:`Inventory Adjustments` page containing all products currently in-stock, with each product listed on its own line." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/cycle_counts.rst:64 +msgid "From this page, the :guilabel:`Filters` and :guilabel:`Group By` options (accessible by clicking the :guilabel:`⬇️ (down arrow)` icon, to the right of the :guilabel:`Search...` bar), can be used to select specific locations and perform inventory counts." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/cycle_counts.rst:68 +msgid "To select a specific location, and view all products within that location, click the :guilabel:`⬇️ (down arrow)` icon, to the right of the :guilabel:`Search...` bar. Then, in the :guilabel:`Group By` column, click :guilabel:`Add Custom Group` to reveal a new drop-down menu." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/cycle_counts.rst:-1 +msgid "Filters and Group By menu on Inventory Adjustments page." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/cycle_counts.rst:76 +msgid "Click :guilabel:`Location` from the drop-down menu. Doing so sorts products into their storage locations on the :guilabel:`Inventory Adjustments` page, and a cycle count can be performed for all products in that location." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/cycle_counts.rst:81 +msgid "In large warehouses with multiple locations and a high volume of products, it might be easier to search for the specific location desired. To do this, from the :guilabel:`Inventory Adjustments` page, click the :guilabel:`⬇️ (down arrow)` icon to the right of the :guilabel:`Search...` bar." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/cycle_counts.rst:85 +msgid "Then, in the :guilabel:`Filters` column, click :guilabel:`Add Custom Filter` to open an :guilabel:`Add Custom Filter` pop-up window." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/cycle_counts.rst:88 +msgid "In the first field, click the value and select :guilabel:`Location` from the list of options. Select :guilabel:`contains` in the second field. In the third field, type in the name of the location being searched for." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/cycle_counts.rst:92 +msgid "Click :guilabel:`Add` for that location to appear on the page." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/cycle_counts.rst:0 +msgid "Add Custom Filter pop-up window with location values entered." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/cycle_counts.rst:99 +msgid "Change full inventory count frequency" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/cycle_counts.rst:101 +msgid "While cycle counts are typically performed per location, the scheduled date for full inventory counts of all in-stock products in the warehouse can also be manually changed, to push the date up sooner than the date listed." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/cycle_counts.rst:105 +msgid "To modify the default scheduled date, go to :menuselection:`Inventory app --> Configuration --> Settings`. Then, in the :guilabel:`Operations` section, locate the :guilabel:`Annual Inventory Day and Month` setting field, which includes a drop-down field that is set to `31` :guilabel:`December`, by default." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/cycle_counts.rst:-1 +msgid "Frequency field in inventory app settings." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/cycle_counts.rst:114 +msgid "To change the day, click the `31`, and change it to a day within the range `1-31`, depending on the desired month of the year." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/cycle_counts.rst:120 +msgid "Once all necessary changes have been made, click :guilabel:`Save`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/cycle_counts.rst:123 +msgid ":doc:`count_products`" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/cycle_counts.rst:124 +msgid ":doc:`use_locations`" +msgstr "" + #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/resupply_warehouses.rst:3 msgid "Resupply from another warehouse" msgstr "" @@ -10095,6 +10718,105 @@ msgstr "" msgid "A receipt for stock received to one warehouse from another." msgstr "" +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/scrap_inventory.rst:3 +msgid "Scrap inventory" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/scrap_inventory.rst:5 +msgid "In some cases, a product in inventory may be damaged or found to be defective. If it is not possible to repair or return the product, Odoo *Inventory* allows users to scrap it, ensuring that usable inventory counts remain accurate." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/scrap_inventory.rst:10 +#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/scrap_manufacturing.rst:25 +msgid "Scrap orders can be viewed by navigating to :menuselection:`Inventory --> Operations --> Scrap`. Each scrap order shows the date and time the order was created, along with the product and quantity that was scrapped." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/scrap_inventory.rst:14 +msgid "To view the total quantity of each item scrapped, navigate to :menuselection:`Inventory --> Configuration --> Locations`. Remove the :guilabel:`Internal` filter from the :guilabel:`Search...` bar to display virtual locations. Finally, select the :guilabel:`Virtual Locations/Scrap` location." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/scrap_inventory.rst:19 +msgid "By default, scrapping a product removes it from physical inventory, and places it in a virtual location titled *Virtual Locations/Scrap*. A virtual location is **not** a physical space, but rather a designation in Odoo that is used to track items that are no longer in physical inventory." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/scrap_inventory.rst:23 +#: ../../content/applications/inventory_and_mrp/manufacturing/advanced_configuration/work_order_dependencies.rst:30 +#: ../../content/applications/inventory_and_mrp/manufacturing/basic_setup/configure_manufacturing_product.rst:68 +msgid "Learn more" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/scrap_inventory.rst:25 +msgid "For more information about virtual locations, see the documentation about the different types of :ref:`locations `." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/scrap_inventory.rst:29 +msgid "Scrap from stock" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/scrap_inventory.rst:31 +msgid "To scrap a product located in inventory, begin by navigating to :menuselection:`Inventory --> Operations --> Scrap`. On the :guilabel:`Scrap Orders` page, click :guilabel:`Create` to configure a new scrap order." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/scrap_inventory.rst:35 +msgid "On the scrap order, select the product being scrapped from the :guilabel:`Product` drop-down menu, then enter the quantity in the :guilabel:`Quantity` field. The :guilabel:`Source Location` defaults to the location where the product is stored, and the :guilabel:`Scrap Location` defaults to :guilabel:`Virtual Locations/Scrap`, but either of these can be changed by selecting a different location from their respective drop-down menus." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/scrap_inventory.rst:-1 +msgid "A new scrap order." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/scrap_inventory.rst:45 +msgid "Finally, click :guilabel:`Validate` to scrap the product. The on-hand inventory count for the scrapped product updates to subtract the scrapped quantity." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/scrap_inventory.rst:49 +msgid "Scrap from a receipt, transfer, or delivery" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/scrap_inventory.rst:51 +msgid "It is also possible to scrap products during the receipt, transfer, and delivery operations. This can be necessary if any products are found to be defective when receiving them into inventory, transferring them from one location to another, or preparing them for delivery." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/scrap_inventory.rst:55 +msgid "To scrap a product during the receipt, transfer, or delivery operations, begin by navigating to the :menuselection:`Inventory` app. On the :guilabel:`Overview` page, select the :guilabel:`# TO PROCESS` button on the :guilabel:`Receipts`, :guilabel:`Internal Transfers`, or :guilabel:`Delivery Orders` card, depending on the type of operation the product is being scrapped from." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/scrap_inventory.rst:61 +msgid "For the :guilabel:`Internal Transfers` card to appear on the :menuselection:`Overview` page of the :menuselection:`Inventory` app, the :guilabel:`Storage Locations` setting must be enabled. To do so, navigate to :menuselection:`Configuration --> Settings`, then enable the checkbox next to :guilabel:`Storage Locations` under the :guilabel:`Warehouse` heading." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/scrap_inventory.rst:66 +msgid "Alternatively, a list of all delivery orders, receipts, and transfers can be viewed by navigating to :menuselection:`Inventory --> Operations --> Transfers`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/scrap_inventory.rst:69 +msgid "Next, open a delivery order, receipt, or transfer from the corresponding page by clicking on it. A :guilabel:`Scrap` button appears at the top of the page. Click it to open the :guilabel:`Scrap` pop-up window." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/scrap_inventory.rst:-1 +msgid "The scrap pop-up in the Inventory app." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/scrap_inventory.rst:78 +msgid "The :guilabel:`Scrap` button will only appear on a receipt that has been validated. This is because Odoo only allows products to be scrapped once they have been entered into inventory." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/scrap_inventory.rst:81 +msgid "On the :guilabel:`Scrap` pop-up window, select the product being scrapped from the :guilabel:`Product` drop-down menu. Then, enter the quantity in the :guilabel:`Quantity` field." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/scrap_inventory.rst:84 +msgid "The :guilabel:`Source Location` defaults to the location where the product is stored, and the :guilabel:`Scrap Location` defaults to :guilabel:`Virtual Locations/Scrap`, but either of these can be changed by selecting a different location from their respective drop-down menus." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/scrap_inventory.rst:88 +msgid "Finally, click :guilabel:`Done` to scrap the product. After doing so, the :guilabel:`Scrap` pop-up window disappears and a :guilabel:`Scraps` smart button appears in the top right of the page. Click it to view all of the scrap orders created from that operation." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/scrap_inventory.rst:-1 +msgid "The Scraps smart button." +msgstr "" + #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_locations.rst:3 msgid "Locations" msgstr "" @@ -10180,7 +10902,7 @@ msgid "To create the location hierarchy in the example above, set the warehouse msgstr "" #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_routes.rst:5 -msgid "Routes and Pull/Push Rules" +msgid "Routes and push/pull rules" msgstr "" #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_routes.rst:7 @@ -10212,86 +10934,86 @@ msgid "View of a generic push to rule when receiving products." msgstr "" #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_routes.rst:36 -msgid "Here is an example of a fulfillment route. In the morning, items are picked for all the orders that need to be prepared during the day. These items are picked from storage locations and moved to the picking area, close to where the orders are packed. Then, the orders are packed in their respective boxes and conveyors bring them close to the shipping docks, ready to be delivered to customers." +msgid "Here is an example of a fulfillment route. In the morning, items are picked for all the orders that need to be prepared during the day. These items are picked from storage locations and moved to the picking area, close to where the orders are packed. Then, the orders are packed in their respective boxes, and conveyor belts bring them to the shipping docks, ready to be delivered to customers." msgstr "" #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_routes.rst:-1 msgid "View of a generic pull from rule when preparing deliveries." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_routes.rst:47 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_routes.rst:46 msgid "Pull rules" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_routes.rst:49 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_routes.rst:48 msgid "With *Pull Rules*, a demand for some products triggers procurements, while *Push Rules* are triggered by products arriving in a specific location." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_routes.rst:52 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_routes.rst:51 msgid "Pull Rules are used to fulfill a sales order. Odoo generates a need at the *Customer Location* for each product in the order. Because pull rules are triggered by a need, Odoo looks for a pull rule defined on the *Customer Location*." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_routes.rst:56 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_routes.rst:55 msgid "In this case, a \"delivery order\" pull rule that transfers products from the *Shipping Area* to the *Customer Location* is found, and a transfer between the two locations is created." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_routes.rst:59 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_routes.rst:58 msgid "Then, Odoo finds another pull rule that tries to fulfill the need for the *Shipping Area*: the \"packing\" rule that transfers products from the *Packing Area* to the *Shipping Area*. Finally, other pull rules are triggered until a transfer between the *Stock* and the *Picking Area* is created." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_routes.rst:65 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_routes.rst:64 msgid "All these product transfers are automatically generated by Odoo based on the pull rules, starting from the end (the customer location) and going backward (the stock warehouse). While working, the operator processes these transfers in the opposite order: first the picking, then the packing, and finally the delivery order." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_routes.rst:71 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_routes.rst:70 msgid "Push rules" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_routes.rst:73 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_routes.rst:72 msgid "On the other hand, *Push Rules* are much easier to understand. Instead of generating documents based on needs, they are triggered in real time when products arrive in a specific location. Push rules basically say: \"when a product arrives at a specific location, move it to another location.\"" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_routes.rst:77 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_routes.rst:76 msgid "An example of a push rule would be: when a product arrives in the *Receipt Area*, move it to the *Storage Location*. As different push rules can be applied to different products, the user can assign different storage locations for different products." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_routes.rst:81 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_routes.rst:80 msgid "Another push rule could be: when products arrive at a location, move them to the *Quality Control Area*. Then, once the quality check is done, move them to their *Storage Location*." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_routes.rst:85 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_routes.rst:84 msgid "Push rules can only be triggered if there are no pull rules that have already generated the product transfers." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_routes.rst:89 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_routes.rst:88 msgid "Sets of push/pull rules like those are called *Routes*. The grouping on the rule decides if products are grouped in the same transfer or not. For example, during the picking operation, all orders and their products are grouped in one transfer, whereas the packing operation respects the grouping per customer order." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_routes.rst:97 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_routes.rst:96 msgid "Use routes and rules" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_routes.rst:99 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_routes.rst:98 msgid "Since *Routes* are a collection of *Push and Pull Rules*, Odoo helps you manage advanced route configurations such as:" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_routes.rst:102 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_routes.rst:101 msgid "Manage product manufacturing chains." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_routes.rst:103 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_routes.rst:102 msgid "Manage default locations per product." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_routes.rst:104 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_routes.rst:103 msgid "Define routes within the stock warehouse according to business needs, such as quality control, after-sales services, or supplier returns." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_routes.rst:106 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_routes.rst:105 msgid "Help rental management by generating automated return moves for rented products." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_routes.rst:108 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_routes.rst:107 msgid "To configure a route for a product, first, open the :guilabel:`Inventory` application and go to :menuselection:`Configuration --> Settings`. Then, in the :guilabel:`Warehouse` section, enable the :guilabel:`Multi-Step Routes` feature and click :guilabel:`Save`." msgstr "" @@ -10299,27 +11021,27 @@ msgstr "" msgid "Activate the Multi-Step Routes feature in Odoo Inventory." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_routes.rst:117 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_routes.rst:116 msgid "The :guilabel:`Storage Locations` feature is automatically activated with the :guilabel:`Multi-Step Routes` feature." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_routes.rst:120 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_routes.rst:119 msgid "Once this first step is completed, the user can use pre-configured routes that come with Odoo, or they can create custom routes." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_routes.rst:124 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_routes.rst:123 msgid "Pre-configured routes" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_routes.rst:126 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_routes.rst:125 msgid "To access Odoo's pre-configured routes, go to :menuselection:`Inventory --> Configuration --> Warehouses`. Then, open a warehouse form. In the :guilabel:`Warehouse Configuration` tab, the user can view the warehouse's pre-configured routes for :guilabel:`Incoming Shipments` and :guilabel:`Outgoing Shipments`." msgstr "" #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_routes.rst:-1 -msgid "A preconfigured warehouse in Odoo Inventory." +msgid "A pre-configured warehouse in Odoo Inventory." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_routes.rst:135 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_routes.rst:134 msgid "Some more advanced routes, such as pick-pack-ship, are also available. The user can select the route that best fits their business needs. Once the :guilabel:`Incoming Shipments` and :guilabel:`Outgoing Shipments` routes are set, head to :menuselection:`Inventory --> Configuration --> Routes` to see the specific routes that Odoo generated." msgstr "" @@ -10327,7 +11049,7 @@ msgstr "" msgid "View of all the preconfigured routes Odoo offers." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_routes.rst:144 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_routes.rst:143 msgid "On the :guilabel:`Routes` page, click on a route to open the route form. In the route form, the user can view which places the route is :guilabel:`Applicable On`. The user can also set the route to only apply on a specific :guilabel:`Company`. This is useful for multi-company environments; for example, a user can have a company and warehouse in Country A and a second company and warehouse in Country B." msgstr "" @@ -10335,7 +11057,7 @@ msgstr "" msgid "View of a route example applicable on product categories and warehouses." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_routes.rst:154 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_routes.rst:153 msgid "At the bottom of the route form, the user can view the specific :guilabel:`Rules` for the route. Each :guilabel:`Rule` has an :guilabel:`Action`, a :guilabel:`Source Location`, and a :guilabel:`Destination Location`." msgstr "" @@ -10343,11 +11065,11 @@ msgstr "" msgid "An example of rules with push & pull actions in Odoo Inventory." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_routes.rst:163 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_routes.rst:162 msgid "Custom Routes" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_routes.rst:165 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_routes.rst:164 msgid "To create a custom route, go to :menuselection:`Inventory --> Configuration --> Routes`, and click on :guilabel:`Create`. Next, choose the places where this route can be selected. A route can be applicable on a combination of places." msgstr "" @@ -10355,15 +11077,15 @@ msgstr "" msgid "View of a pick-pack-ship route." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_routes.rst:173 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_routes.rst:172 msgid "Each place has a different behavior, so it is important to tick only the useful ones and adapt each route accordingly. Then, configure the :guilabel:`Rules` of the route." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_routes.rst:176 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_routes.rst:175 msgid "If the route is applicable on a product category, the route still needs to be manually set on the product category form by going to :menuselection:`Inventory --> Configuration --> Product Categories`. Then, select the product category and open the form. Next, click :guilabel:`Edit` and under the :guilabel:`Logistics` section, set the :guilabel:`Routes`." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_routes.rst:181 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_routes.rst:180 msgid "When applying the route on a product category, all the rules configured in the route are applied to **every** product in the category. This can be helpful if the business uses the dropshipping process for all the products from the same category." msgstr "" @@ -10371,7 +11093,7 @@ msgstr "" msgid "View of a route applied to the \"all\" product category." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_routes.rst:189 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_routes.rst:188 msgid "The same behavior applies to the warehouses. If the route can apply to :guilabel:`Warehouses`, all the transfers occurring inside the chosen warehouse that meet the conditions of the route's rules will then follow that route." msgstr "" @@ -10379,11 +11101,11 @@ msgstr "" msgid "View of the warehouse drop-down menu when selecting applicable on warehouse." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_routes.rst:197 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_routes.rst:196 msgid "If the route is applicable on :guilabel:`Sales Order Lines`, it is more or less the opposite. The route must be manually chosen when creating a quotation. This is useful if some products go through different routes." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_routes.rst:201 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_routes.rst:200 msgid "Remember to toggle the visibility of the :guilabel:`Route` column on the quotation/sales order. Then, the route can be chosen on each line of the quotation/sales order." msgstr "" @@ -10391,11 +11113,11 @@ msgstr "" msgid "View of the menu allowing to add new lines to sales orders." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_routes.rst:208 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_routes.rst:207 msgid "Finally, there are routes that can be applied to products. Those work more or less like the product categories: once selected, the route must be manually set on the product form." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_routes.rst:211 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_routes.rst:210 msgid "To set a route on a product, go to :menuselection:`Inventory --> Products --> Products` and select the desired product. Then, go to the :guilabel:`Inventory` tab and under the :guilabel:`Operations` section, select the :guilabel:`Routes`." msgstr "" @@ -10403,15 +11125,15 @@ msgstr "" msgid "View of a product form, where the route must be selected." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_routes.rst:220 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_routes.rst:219 msgid "Rules must be set on the route in order for the route to work." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_routes.rst:223 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_routes.rst:222 msgid "Rules" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_routes.rst:225 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_routes.rst:224 msgid "The rules are defined on the route form. First, go to :menuselection:`Inventory --> Configuration --> Routes` and open the desired route form. Next, click :guilabel:`Edit` and in the :guilabel:`Rules` section, click on :guilabel:`Add a line`." msgstr "" @@ -10419,27 +11141,27 @@ msgstr "" msgid "View of the rules menu, where it is possible to add new rules." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_routes.rst:233 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_routes.rst:232 msgid "The available rules trigger various actions. If Odoo offers *Push* and *Pull* rules, others are also available. Each rule has an :guilabel:`Action`:" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_routes.rst:236 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_routes.rst:235 msgid ":guilabel:`Pull From`: this rule is triggered by a need for the product in a specific location. The need can come from a sales order being validated or from a manufacturing order requiring a specific component. When the need appears in the destination location, Odoo generates a picking to fulfill this need." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_routes.rst:240 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_routes.rst:239 msgid ":guilabel:`Push To`: this rule is triggered by the arrival of some products in the defined source location. In the case of the user moving products to the source location, Odoo generates a picking to move those products to the destination location." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_routes.rst:243 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_routes.rst:242 msgid ":guilabel:`Pull & Push`: this rule allows the generation of pickings in the two situations explained above. This means that when products are required at a specific location, a transfer is created from the previous location to fulfill that need. This creates a need in the previous location and a rule is triggered to fulfill it. Once the second need is fulfilled, the products are pushed to the destination location and all the needs are fulfilled." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_routes.rst:248 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_routes.rst:247 msgid ":guilabel:`Buy`: when products are needed at the destination location, a request for quotation is created to fulfill the need." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_routes.rst:250 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_routes.rst:249 msgid ":guilabel:`Manufacture`: when products are needed in the source location, a manufacturing order is created to fulfill the need." msgstr "" @@ -10448,55 +11170,47 @@ msgid "Overview of a \"Pull From\" rule that creates a transfer between the stoc "zone." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_routes.rst:258 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_routes.rst:257 msgid "The :guilabel:`Operation Type` must also be defined on the rule. This defines which kind of picking is created from the rule." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_routes.rst:261 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_routes.rst:260 msgid "If the rule's :guilabel:`Action` is set to :guilabel:`Pull From` or :guilabel:`Pull & Push`, a :guilabel:`Supply Method` must be set. The :guilabel:`Supply Method` defines what happens at the source location:" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_routes.rst:265 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_routes.rst:264 msgid ":guilabel:`Take From Stock`: the products are taken from the available stock of the source location." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_routes.rst:267 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_routes.rst:266 msgid ":guilabel:`Trigger Another Rule`: the system tries to find a stock rule to bring the products to the source location. The available stock is ignored." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_routes.rst:269 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_routes.rst:268 msgid ":guilabel:`Take From Stock, if Unavailable, Trigger Another Rule`: the products are taken from the available stock of the source location. If there is no stock available, the system tries to find a rule to bring the products to the source location." msgstr "" #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_routes.rst:273 -msgid "In the *Scheduling* section, you can determine how Odoo behaves when one of the chain's pickings is rescheduled. In case you decide to **Propagate Rescheduling**, the next move is also to be rescheduled." +msgid "Example flow" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_routes.rst:277 -msgid "If you prefer having the choice to reschedule the next move, you can decide to receive an alert in the form of a *next activity*." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_routes.rst:281 -msgid "Sample full route flow" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_routes.rst:283 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_routes.rst:275 msgid "In this example, let's use a custom *Pick - Pack - Ship* route to try a full flow with an advanced custom route." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_routes.rst:286 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_routes.rst:278 msgid "First, a quick look at the route's rules and their supply methods. There are three rules, all :guilabel:`Pull From` rules. The :guilabel:`Supply Methods` for each rule are the following:" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_routes.rst:289 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_routes.rst:281 msgid ":guilabel:`Take From Stock`: When products are needed in the :guilabel:`WH/Packing Zone`, *picks* (internal transfers from :guilabel:`WH/Stock` to :guilabel:`WH/Packing Zone`) are created from :guilabel:`WH/Stock` to fulfill the need." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_routes.rst:292 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_routes.rst:284 msgid ":guilabel:`Trigger Another Rule`: When products are needed in :guilabel:`WH/Output`, *packs* (internal transfers from :guilabel:`WH/Packing Zone` to :guilabel:`WH/Output`) are created from :guilabel:`WH/Packing Zone` to fulfill the need." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_routes.rst:295 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_routes.rst:287 msgid ":guilabel:`Trigger Another Rule`: When products are needed in :guilabel:`Partner Locations/Customers`, *delivery orders* are created from :guilabel:`WH/Output` to fulfill the need." msgstr "" @@ -10504,7 +11218,7 @@ msgstr "" msgid "Overview of all the transfers created by the pick - pack - ship route." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_routes.rst:303 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_routes.rst:295 msgid "This means that, when a customer orders products that have a *pick - pack - ship* route set on it, a delivery order is created to fulfill the order." msgstr "" @@ -10512,7 +11226,7 @@ msgstr "" msgid "View of the operations created by a pull from transfer." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_routes.rst:311 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_routes.rst:303 msgid "If the source document for multiple tranfers is the same sales order, the status is not the same. The status will be :guilabel:`Waiting Another Operation` if the previous transfer in the list is not done yet." msgstr "" @@ -10520,7 +11234,7 @@ msgstr "" msgid "View of the transfers' various statuses at the beginning of the process." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_routes.rst:319 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_routes.rst:311 msgid "To prepare the delivery order, packed products are needed at the output area, so an internal transfer is requested from the packing zone." msgstr "" @@ -10528,7 +11242,7 @@ msgstr "" msgid "View of the detailed operations for a transfer between the packing and output zones." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_routes.rst:326 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_routes.rst:318 msgid "Obviously, the packing zone needs products ready to be packed. So, an internal transfer is requested to the stock and employees can gather the required products from the warehouse." msgstr "" @@ -10536,11 +11250,11 @@ msgstr "" msgid "View of the detailed operations for a transfer between the stock and packing zones." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_routes.rst:333 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_routes.rst:325 msgid "As explained in the introduction of the documentation, the last step in the process (for this route, the delivery order) is the first to be triggered, which then triggers other rules until we reach the first step in the process (here, the internal transfer from the stock to the packing area). Now, everything is ready to be processed so the customer can get the ordered items." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_routes.rst:338 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_routes.rst:330 msgid "In this example, the product is delivered to the customer when all the rules have been triggered and the transfers are done." msgstr "" @@ -10806,79 +11520,199 @@ msgid "Inventory valuation" msgstr "" #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/integrating_landed_costs.rst:3 -msgid "Integrating additional costs to products (landed costs)" +msgid "Landed costs" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/integrating_landed_costs.rst:7 -msgid "The landed cost feature in Odoo allows the user to include additional costs (shipment, insurance, customs duties, etc.) into the cost of the product." +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/integrating_landed_costs.rst:12 +msgid "When shipping products to customers, the landed cost is the total price of a product or shipment, including all expenses associated with shipping the product." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/integrating_landed_costs.rst:13 -msgid "First, go to :menuselection:`Inventory --> Configuration --> Settings --> Valuation` and activate the :guilabel:`Landed Costs` feature. Odoo also gives the option to set a :guilabel:`Default Journal` in which the landed costs accounting entries will be recorded." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/integrating_landed_costs.rst:-1 -msgid "Activate the landed cost feature in Inventory settings." +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/integrating_landed_costs.rst:15 +msgid "In Odoo, the *Landed Costs* feature is used to take additional costs into account when calculating the valuation of a product. This includes the cost of shipment, insurance, customs duties, taxes, and other fees." msgstr "" #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/integrating_landed_costs.rst:22 -msgid "Add costs to products" +msgid "To add landed costs to products, the *Landed Costs* feature must first be enabled. To enable this feature, navigate to :menuselection:`Inventory app --> Configuration --> Settings`, and scroll to the :guilabel:`Valuation` section." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/integrating_landed_costs.rst:25 -msgid "Receive the vendor bill" +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/integrating_landed_costs.rst:26 +msgid "Tick the checkbox next to the :guilabel:`Landed Costs` option, and click :guilabel:`Save` to save changes." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/integrating_landed_costs.rst:27 -msgid "After a vendor fulfills a purchase order and sends a bill, click :guilabel:`Create Bill` on the purchase order to create a vendor bill in Odoo. If the vendor bill includes landed costs, such as custom duties, tick the box in the :guilabel:`Landed Costs` column on the vendor bill invoice line." +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/integrating_landed_costs.rst:29 +msgid "Once the page refreshes, a new :guilabel:`Default Journal` field appears below the :guilabel:`Landed Costs` feature in the :guilabel:`Valuation` section." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/integrating_landed_costs.rst:32 +msgid "Click the :guilabel:`Default Journal` drop-down menu to reveal a list of accounting journals. Select a journal for which all accounting entries related to landed costs should be recorded." msgstr "" #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/integrating_landed_costs.rst:-1 -msgid "Enable Landed Costs option on vendor bill line." +msgid "Landed Costs feature and resulting Default Journal field in the Inventory settings." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/integrating_landed_costs.rst:35 -msgid "For charges that are always landed costs, create a landed cost product in Odoo. That way, the landed cost product can be quickly added to the vendor bill as an invoice line instead of manually entering the landed cost information every time a vendor bill comes in." +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/integrating_landed_costs.rst:40 +msgid "Create landed cost product" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/integrating_landed_costs.rst:39 -msgid "First, create a new product in :menuselection:`Inventory --> Products --> Products --> Create`. Next, name the landed cost product. Then, set the :guilabel:`Product Type` to :guilabel:`Service`. A landed cost product must always be a service product type. After that, go to the :guilabel:`Purchase` tab and check the box next to :guilabel:`Is a Landed Cost`. Finally, click :guilabel:`Save` to finish creating the landed cost product." +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/integrating_landed_costs.rst:42 +msgid "For charges that are consistently added as landed costs, a landed cost product can be created in Odoo. This way, a landed cost product can be quickly added to a vendor bill as an invoice line, instead of having to be manually entered every time a new vendor bill is created." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/integrating_landed_costs.rst:45 -msgid "If this product is always a landed cost, you can also define it on the product and avoid having to tick the box on each vendor bill." +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/integrating_landed_costs.rst:46 +msgid "To do this, create a new product by going to :menuselection:`Inventory app --> Products --> Products`, and clicking :guilabel:`New`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/integrating_landed_costs.rst:49 +msgid "Assign a name to the landed cost product in the :guilabel:`Product Name` field (i.e. `International Shipping`). In the :guilabel:`Product Type` field, click the drop-down menu, and select :guilabel:`Service` as the :guilabel:`Product Type`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/integrating_landed_costs.rst:54 +msgid "Landed cost products **must** have their :guilabel:`Product Type` set to :guilabel:`Service`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/integrating_landed_costs.rst:56 +msgid "Click the :guilabel:`Purchase` tab, and tick the checkbox next to :guilabel:`Is a Landed Cost` in the :guilabel:`Vendor Bills` section. Once ticked, a new :guilabel:`Default Split Method` field appears below it, prompting a selection. Clicking that drop-down menu reveals the following options:" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/integrating_landed_costs.rst:60 +msgid ":guilabel:`Equal`: splits the cost equally across each product included in the receipt, regardless of the quantity of each." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/integrating_landed_costs.rst:62 +msgid ":guilabel:`By Quantity`: splits the cost across each unit of all products in the receipt." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/integrating_landed_costs.rst:63 +msgid ":guilabel:`By Current Cost`: splits the cost according to the cost of each product unit, so a product with a higher cost receives a greater share of the landed cost." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/integrating_landed_costs.rst:65 +msgid ":guilabel:`By Weight`: splits the cost, according to the weight of the products in the receipt." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/integrating_landed_costs.rst:66 +msgid ":guilabel:`By Volume`: splits the cost, according to the volume of the products in the receipt." msgstr "" #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/integrating_landed_costs.rst:-1 -msgid "Option to define a product as a landed cost." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/integrating_landed_costs.rst:52 -msgid "Once the landed cost is added to the vendor bill (either by checking the :guilabel:`Landed Cost` option on the invoice line or adding a landed cost product to the bill), click the :guilabel:`Create Landed Costs` button at the top of the bill. Odoo automatically creates a landed cost record with the set landed cost pre-filled in the :guilabel:`Additional Costs` product lines. From here, decide which picking the additional costs apply to by clicking :guilabel:`Edit` and selecting the picking reference number from the :guilabel:`Transfers` drop-down menu. Finally, click :guilabel:`Save`." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/integrating_landed_costs.rst:-1 -msgid "Use a warehouse transfer to cover a landed cost in the accounting journal." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/integrating_landed_costs.rst:64 -msgid "After setting the picking, click :guilabel:`Compute` on the landed cost record. Then, go to the :guilabel:`Valuation Adjustments` tab to see the impact of the landed costs. Finally, click :guilabel:`Validate` to post the landed cost entry to the accounting journal." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/integrating_landed_costs.rst:68 -msgid "The user can access the journal entry that has been created by the landed cost by clicking on the :guilabel:`Journal Entry`." +msgid "Is a Landed Cost checkbox and Default Split Method on service type product form." msgstr "" #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/integrating_landed_costs.rst:72 -msgid "The product that the landed cost is applied to must have a product category set to a :abbr:`FIFO (First In, First Out)` or an :abbr:`AVCO (Average Costing)` method." +msgid "When creating new vendor bills, this product can be added as an invoice line as a landed cost." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/integrating_landed_costs.rst:75 +msgid "To apply a landed cost on a vendor bill, the products included in the original |PO| **must** belong to a *Product Category* with its *Force Removal Strategy* set to |FIFO|, and its *Costing Method* set to |AVCO|." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/integrating_landed_costs.rst:82 +msgid "Navigate to :menuselection:`Purchase app --> New` to create a new request for quotation (RfQ). In the :guilabel:`Vendor` field, add a vendor to order products from. Then, click :guilabel:`Add a product`, under the :guilabel:`Products` tab, to add products to the |RfQ|." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/integrating_landed_costs.rst:86 +msgid "Once ready, click :guilabel:`Confirm Order` to confirm the order. Then, click :guilabel:`Receive Products` once the products have been received, followed by :guilabel:`Validate`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/integrating_landed_costs.rst:90 +msgid "Create vendor bill" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/integrating_landed_costs.rst:92 +msgid "Once the vendor fulfills the |PO| and sends a bill, a vendor bill can be created from the |PO| in Odoo." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/integrating_landed_costs.rst:95 +msgid "Navigate to the :menuselection:`Purchase app`, and click into the |PO| for which a vendor bill should be created. Then, click :guilabel:`Create Bill`. This opens a new :guilabel:`Vendor Bill` in the :guilabel:`Draft` stage." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/integrating_landed_costs.rst:99 +msgid "In the :guilabel:`Bill Date` field, click the line to open a calendar popover menu, and select the date on which this draft bill should be billed." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/integrating_landed_costs.rst:102 +msgid "Then, under the :guilabel:`Invoice Lines` tab, click :guilabel:`Add a line`, and click the drop-down menu in the :guilabel:`Product` column to select the previously created landed cost product. Click the :guilabel:`Save manually (cloud with arrow)` icon to update the draft bill." msgstr "" #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/integrating_landed_costs.rst:-1 -msgid "Landed cost journal entry" +msgid "Landed Costs column checkboxes for product and landed cost." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/integrating_landed_costs.rst:80 -msgid "Landed cost records can also be directly created in :menuselection:`Inventory --> Operations --> Landed Costs`, it is not necessary to create a landed cost record from the vendor bill." +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/integrating_landed_costs.rst:110 +msgid "In the :guilabel:`Landed Costs` column, the product ordered from the vendor does **not** have its checkbox ticked, while the landed cost product's checkbox **is** ticked. This differentiates landed costs from all other costs displayed on the bill." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/integrating_landed_costs.rst:114 +msgid "Additionally, at the top of the form, a :guilabel:`Create Landed Costs` button appears." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/integrating_landed_costs.rst:-1 +msgid "Create Landed Costs button on vendor bill." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/integrating_landed_costs.rst:121 +msgid "Add landed cost" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/integrating_landed_costs.rst:123 +msgid "Once a landed cost is added to the vendor bill, click :guilabel:`Create Landed Costs` at the top of the vendor bill." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/integrating_landed_costs.rst:126 +msgid "Doing so automatically creates a landed cost record, with a set landed cost pre-filled in the product line in the :guilabel:`Additional Costs` tab." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/integrating_landed_costs.rst:129 +msgid "From the :guilabel:`Landed Cost` form, click the :guilabel:`Transfers` drop-down menu, and select which transfer the landed cost belongs to." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/integrating_landed_costs.rst:-1 +msgid "Landed cost form with selected receipt transfer." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/integrating_landed_costs.rst:137 +msgid "In addition to creating landed costs directly from a vendor bill, landed cost records can *also* be created by navigating to :menuselection:`Inventory app --> Operations --> Landed Costs`, and clicking :guilabel:`New`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/integrating_landed_costs.rst:141 +msgid "After setting the picking from the :guilabel:`Transfers` drop-down menu, click :guilabel:`Compute` (at the bottom of the form, under the :guilabel:`Total:` cost)." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/integrating_landed_costs.rst:144 +msgid "Click the :guilabel:`Valuation Adjustments` tab to see the impact of the landed costs. The :guilabel:`Original Value` column lists the original price of the |PO|, the :guilabel:`Additional Landed Cost` column displays the landed cost, and the :guilabel:`New Value` displays the sum of the two, for the total cost of the |PO|." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/integrating_landed_costs.rst:149 +msgid "Once ready, click :guilabel:`Validate` to post the landed cost entry to the accounting journal." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/integrating_landed_costs.rst:151 +msgid "This causes a :guilabel:`Valuation` smart button to appear at the top of the form. Click the :guilabel:`Valuation` smart button to open a :guilabel:`Stock Valuation` page, with the product's updated valuation listed." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/integrating_landed_costs.rst:156 +msgid "For a :guilabel:`Valuation` smart button to appear upon validation, the product's :guilabel:`Product Type` **must** be set to :guilabel:`Storable`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/integrating_landed_costs.rst:159 +msgid "To view the valuation of *every* product, including landed costs, navigate to :menuselection:`Inventory app --> Reporting --> Valuation`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/integrating_landed_costs.rst:163 +msgid "Each journal entry created for a landed cost on a vendor bill can be viewed in the *Accounting* app." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/integrating_landed_costs.rst:166 +msgid "To locate these journal entries, navigate to :menuselection:`Accounting app --> Accounting --> Journal Entries`, and locate the correct entry, by number (i.e. `PBNK1/2024/XXXXX`)." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/integrating_landed_costs.rst:169 +msgid "Click into the journal entry to view the :guilabel:`Journal Items`, and other information about the entry." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/integrating_landed_costs.rst:0 +msgid "Journal Entry form for landed cost created from vendor bill." msgstr "" #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:3 @@ -12077,6 +12911,491 @@ msgstr "" msgid "To see the maintenance requests for a piece of equipment, go to the page for the equipment and select :guilabel:`Maintenance` in the top right corner of the form." msgstr "" +#: ../../content/applications/inventory_and_mrp/maintenance/maintenance_calendar.rst:3 +msgid "Maintenance calendar" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/maintenance/maintenance_calendar.rst:7 +msgid "Avoiding equipment breakdowns, and blocks in warehouse work centers, requires constant equipment maintenance. Timely corrective maintenance for machines and tools that break unexpectedly, as well as preventive maintenance to ensure that such issues are avoided, are key to keeping warehouse operations running smoothly." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/maintenance/maintenance_calendar.rst:12 +msgid "In Odoo *Maintenance*, users can access the *Maintenance Calendar* to create, schedule, and edit both corrective and preventive maintenance requests, to stay on top of equipment and work centers." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/maintenance/maintenance_calendar.rst:16 +#: ../../content/applications/inventory_and_mrp/maintenance/maintenance_requests.rst:16 +msgid "Create maintenance request" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/maintenance/maintenance_calendar.rst:18 +msgid "Maintenance requests can be created directly from the *Maintenance Calendar*. To access the calendar, navigate to :menuselection:`Maintenance app --> Maintenance --> Maintenance Calendar`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/maintenance/maintenance_calendar.rst:21 +msgid "To create a new request, click anywhere on the calendar. Doing so opens a :guilabel:`New Event` pop-up window. In the :guilabel:`Name:` field, assign a title to the new request." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/maintenance/maintenance_calendar.rst:-1 +msgid "New event creation pop-up window." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/maintenance/maintenance_calendar.rst:28 +msgid "Clicking :guilabel:`Create` on the pop-up window saves the new request with no additional details. If the request's creation should be canceled, click :guilabel:`Cancel`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/maintenance/maintenance_calendar.rst:31 +msgid "To add more details and schedule the request for a specific date and time, click :guilabel:`Edit`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/maintenance/maintenance_calendar.rst:33 +msgid "Clicking :guilabel:`Edit` opens a blank maintenance request form, where various details about the request can be filled out." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/maintenance/maintenance_calendar.rst:37 +msgid "Edit maintenance request" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/maintenance/maintenance_calendar.rst:39 +msgid "In the :guilabel:`Request` field, assign a title to the new request. In the :guilabel:`Created By` field, from the drop-down menu, select which user the request was created by. By default, this field populates with the user actually creating the request." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/maintenance/maintenance_calendar.rst:-1 +msgid "New maintenance request form creation." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/maintenance/maintenance_calendar.rst:47 +msgid "In the :guilabel:`For` field, from the drop-down menu, select if this request is being created for a piece of :guilabel:`Equipment`, or a :guilabel:`Work Center`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/maintenance/maintenance_calendar.rst:51 +msgid "If :guilabel:`Work Center` is selected in the :guilabel:`For` field's drop-down menu, two additional fields appear on the form: :guilabel:`Work Center` and :guilabel:`Block Workcenter`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/maintenance/maintenance_calendar.rst:54 +msgid "In the :guilabel:`Work Center` field, select which work center in the warehouse this maintenance request applies to." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/maintenance/maintenance_calendar.rst:57 +msgid "If the :guilabel:`Block Workcenter` option's checkbox is ticked, it is not possible to plan work orders, or other maintenance requests, in this work center during the time that this request is being performed." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/maintenance/maintenance_calendar.rst:61 +msgid "If :guilabel:`Equipment` is selected in the :guilabel:`For` field, which it is by default, select which machine or tool requires maintenance from the :guilabel:`Equipment` field. Once a specific piece of equipment is selected, a greyed-out :guilabel:`Category` field appears, listing the *Equipment Category* to which the equipment belongs." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/maintenance/maintenance_calendar.rst:66 +msgid "In the :guilabel:`Worksheet Template` field, if necessary, click the drop-down menu to select a worksheet template. These templates are custom templates that can be filled out by the employee performing the maintenance." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/maintenance/maintenance_calendar.rst:70 +msgid "Under the :guilabel:`Category` field, the :guilabel:`Request Date` field displays the date requested for the maintenance to happen." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/maintenance/maintenance_calendar.rst:73 +msgid "The :guilabel:`Maintenance Type` field provides two selectable radio button options: :guilabel:`Corrective` and :guilabel:`Preventive`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/maintenance/maintenance_calendar.rst:76 +msgid ":guilabel:`Corrective` maintenance is for requests that arise for immediate needs, such as broken equipment, while :guilabel:`Preventive` maintenance is for planned requests, to avoid breakdowns in the future." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/maintenance/maintenance_calendar.rst:80 +msgid "If this request is tied to a specific |MO|, select that |MO| from the :guilabel:`Manufacturing Order` field." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/maintenance/maintenance_calendar.rst:83 +msgid "From the drop-down menu for the :guilabel:`Team` field, select the desired maintenance team who will perform the maintenance. In the :guilabel:`Responsible` field, select the technician responsible for the request." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/maintenance/maintenance_calendar.rst:-1 +msgid "Filled-out details of maintenance request form." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/maintenance/maintenance_calendar.rst:91 +msgid "In the :guilabel:`Scheduled Date` field, click the date to open a calendar popover. From this popover, select the planned date of the maintenance, and click :guilabel:`Apply` to save the date." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/maintenance/maintenance_calendar.rst:94 +msgid "In the :guilabel:`Duration` field, enter the the amount of hours (in a `00:00` format) that the maintenance is planned to take." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/maintenance/maintenance_calendar.rst:97 +msgid "In the :guilabel:`Priority` field, choose a priority between one and three :guilabel:`⭐⭐⭐ (stars)`. This indicates the importance of the maintenance request." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/maintenance/maintenance_calendar.rst:100 +msgid "If working in a multi-company environment, from the drop-down menu in the :guilabel:`Company` field, select the company to which this maintenance request belongs." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/maintenance/maintenance_calendar.rst:103 +msgid "At the bottom of the form, there are two tabs: :guilabel:`Notes` and :guilabel:`Instructions`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/maintenance/maintenance_calendar.rst:105 +msgid "In the :guilabel:`Notes` tab, type out any internal notes for the team or technician assigned to the request, if necessary." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/maintenance/maintenance_calendar.rst:108 +msgid "In the :guilabel:`Instructions` tab, if necessary, select one of the three radio button options to provide maintenance instructions to the assigned team or technician. The available methods for providing instructions are via :guilabel:`PDF`, :guilabel:`Google Slide`, or :guilabel:`Text`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/maintenance/maintenance_calendar.rst:-1 +msgid "Instructions tab options on maintenance request form." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/maintenance/maintenance_calendar.rst:117 +msgid "Calendar elements" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/maintenance/maintenance_calendar.rst:119 +msgid "The *Maintenance Calendar* provides various views, search functions, and filters to help keep track of the progress of ongoing and planned maintenance requests." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/maintenance/maintenance_calendar.rst:122 +msgid "The following sections describe elements found across various views of the calendar." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/maintenance/maintenance_calendar.rst:125 +msgid "Filters and Favorites" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/maintenance/maintenance_calendar.rst:127 +msgid "To access the maintenance calendar, navigate to :menuselection:`Maintenance app --> Maintenance --> Maintenance Calendar`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/maintenance/maintenance_calendar.rst:130 +msgid "To add and remove filters for sorting data on the *Maintenance Calendar*, click the :guilabel:`🔻 (triangle pointed down)` icon, to the right of the search bar at the top of the page." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/maintenance/maintenance_calendar.rst:133 +msgid "The left-hand side of the resulting drop-down menu lists all the different :guilabel:`Filters` users can select. By default, :guilabel:`To Do` and :guilabel:`Active` are selected, so all open requests are displayed." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/maintenance/maintenance_calendar.rst:138 +msgid "To add a custom filter to the :guilabel:`Maintenance Calendar`, click :guilabel:`Add Custom Filter`, under the :guilabel:`Filters` section of the drop-down menu. This opens an :guilabel:`Add Custom Filter` pop-up window." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/maintenance/maintenance_calendar.rst:142 +msgid "From this pop-up window, configure the properties of the new rule for the filter. Once ready, click :guilabel:`Add`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/maintenance/maintenance_calendar.rst:145 +msgid "The right-hand side of the drop-down menu lists the :guilabel:`Favorites`, or any searches that have been saved as a favorite to be revisited at a later date." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/maintenance/maintenance_calendar.rst:-1 +msgid "Favorites section of filters drop-down menu." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/maintenance/maintenance_calendar.rst:152 +msgid "To save a new :guilabel:`Favorite` search, select the desired :guilabel:`Filters`. Then, click :guilabel:`Save current search`. In the field directly below :guilabel:`Save current search`, assign a name to the search." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/maintenance/maintenance_calendar.rst:156 +msgid "Under the assigned name, there are two options, to save the current search either as the :guilabel:`Default filter`, or as a :guilabel:`Shared` filter." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/maintenance/maintenance_calendar.rst:159 +msgid "Selecting :guilabel:`Default filter` sets this filter as the default when opening this calendar view." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/maintenance/maintenance_calendar.rst:162 +msgid "Selecting the :guilabel:`Shared` filter makes this filter available to other users." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/maintenance/maintenance_calendar.rst:164 +msgid "Once ready, click :guilabel:`Save`. When clicked, the new :guilabel:`Favorite` filter appears in the :guilabel:`Favorites` column, and a :guilabel:`⭐ (gold star)` icon appears with the filter's name in the search bar." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/maintenance/maintenance_calendar.rst:169 +msgid "Views" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/maintenance/maintenance_calendar.rst:171 +msgid "The :guilabel:`Maintenance Calendar` is available in six different views: :guilabel:`Calendar` (default), :guilabel:`Kanban`, :guilabel:`List`, :guilabel:`Pivot`, :guilabel:`Graph`, and :guilabel:`Activity`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/maintenance/maintenance_calendar.rst:-1 +msgid "Different view type icons for maintenance calendar." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/maintenance/maintenance_calendar.rst:180 +msgid "Calendar view" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/maintenance/maintenance_calendar.rst:182 +msgid ":guilabel:`Calendar` is the default view displayed when the :guilabel:`Maintenance Calendar` is opened. There are a number of options in this view type for sorting and grouping information about maintenance requests." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/maintenance/maintenance_calendar.rst:186 +msgid "In the top-left corner of the page, there is a drop-down menu set to :guilabel:`Week`, by default. Clicking that drop-down menu reveals the different periods of time, in which the calendar can be viewed: :guilabel:`Day`, :guilabel:`Month`, and :guilabel:`Year`. There is also an option to :guilabel:`Show weekends`, selected by default. If unselected, weekends are not shown on the calendar." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/maintenance/maintenance_calendar.rst:-1 +msgid "Calendar period drop-down menu options." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/maintenance/maintenance_calendar.rst:196 +msgid "To the left of this menu, there is a :guilabel:`⬅️ (left arrow)` icon and a :guilabel:`➡️ (right arrow)` icon. Clicking these arrows moves the calendar backward or forward in time, respectively." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/maintenance/maintenance_calendar.rst:199 +msgid "To the right of the drop-down menu set to :guilabel:`Week`, by default, is a :guilabel:`Today` button. Clicking this button resets the calendar to view today's date, no matter which point in time is being viewed before clicking it." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/maintenance/maintenance_calendar.rst:203 +msgid "At the far-right side of the page is a sidebar column, containing a minimized calendar set to today's date, and a :guilabel:`Technician` list, displaying all the *Technicians* with requests currently open. Click the :guilabel:`(panel)` icon at the top of this sidebar to open or close the sidebar." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/maintenance/maintenance_calendar.rst:209 +msgid "The :guilabel:`Technician` list only displays if technicians are assigned to open requests, and individual technicians are only listed, if they are listed as :guilabel:`Responsible` on at least **one** maintenance request form." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/maintenance/maintenance_calendar.rst:214 +msgid "Kanban view" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/maintenance/maintenance_calendar.rst:216 +msgid "With the :guilabel:`Kanban` view, all open maintenance requests are displayed in Kanban-style columns, in their respective stages of the maintenance process." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/maintenance/maintenance_calendar.rst:219 +msgid "Each maintenance request appears on its own task card, and each task card can be dragged-and-dropped to a different stage of the Kanban pipeline." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/maintenance/maintenance_calendar.rst:222 +msgid "Each column has a name (i.e. :guilabel:`In Progress`). Hovering at the top of a column reveals a :guilabel:`⚙️ (gear)` icon. Clicking the :guilabel:`⚙️ (gear)` icon reveals a list of options for that column: :guilabel:`Fold`, :guilabel:`Edit`, :guilabel:`Automations`, and :guilabel:`Delete`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/maintenance/maintenance_calendar.rst:-1 +msgid "Column options for stage in Kanban view." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/maintenance/maintenance_calendar.rst:230 +msgid "Clicking :guilabel:`Fold` folds the column to hide its contents." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/maintenance/maintenance_calendar.rst:232 +msgid "Clicking :guilabel:`Edit` opens an :guilabel:`Edit: (stage name)` pop-up window, with the corresponding stage name, wherein the column's details can be edited. The following are the column options that can be edited:" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/maintenance/maintenance_calendar.rst:-1 +msgid "Edit In Progress pop-up window." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/maintenance/maintenance_calendar.rst:240 +msgid ":guilabel:`Name`: the name of the stage in the Kanban pipeline." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/maintenance/maintenance_calendar.rst:241 +msgid ":guilabel:`Folded in Maintenance Pipe`: when checked, this stage's column is folded by default in the :guilabel:`Kanban` view type." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/maintenance/maintenance_calendar.rst:243 +msgid ":guilabel:`Request Confirmed`: when this box is not ticked, and the maintenance request type is set to *Work Center*, no leave is created for the respective work center when a maintenance request is created. If the box *is* ticked, the work center is automatically blocked for the listed duration, either at the specified date, or as soon as possible, if the work center is unavailable." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/maintenance/maintenance_calendar.rst:248 +msgid ":guilabel:`Sequence`: the order in the maintenance process, in which this stage appears." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/maintenance/maintenance_calendar.rst:249 +msgid ":guilabel:`Request Done`: if ticked, this box indicates this stage is the final step of the maintenance process. Requests moved to this stage are closed." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/maintenance/maintenance_calendar.rst:252 +msgid "Once ready, click :guilabel:`Save & Close`. If no changes have been made, click :guilabel:`Discard`, or click the :guilabel:`X` icon to close the pop-up window." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/maintenance/maintenance_calendar.rst:256 +msgid "List view" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/maintenance/maintenance_calendar.rst:258 +msgid "With the :guilabel:`List` view selected, all open maintenance requests are displayed in a list, with information about each request listed in its respective row." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/maintenance/maintenance_calendar.rst:261 +msgid "The columns of information displayed in this view type are the following:" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/maintenance/maintenance_calendar.rst:263 +msgid ":guilabel:`Subjects`: the name assigned to the maintenance request." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/maintenance/maintenance_calendar.rst:264 +msgid ":guilabel:`Employee`: the employee who originally created the maintenance request." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/maintenance/maintenance_calendar.rst:265 +msgid ":guilabel:`Technician`: the technician responsible for the maintenance request." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/maintenance/maintenance_calendar.rst:266 +msgid ":guilabel:`Category`: the category the equipment being repaired belongs to." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/maintenance/maintenance_calendar.rst:267 +msgid ":guilabel:`Stage`: the stage of the maintenance process the request is currently in." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/maintenance/maintenance_calendar.rst:268 +msgid ":guilabel:`Company`: if in a multi-company environment, the company in the database the request is assigned to." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/maintenance/maintenance_calendar.rst:272 +msgid "Pivot view" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/maintenance/maintenance_calendar.rst:274 +msgid "With the :guilabel:`Pivot` view selected, maintenance requests are displayed in a pivot table, and can be customized to show different data metrics." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/maintenance/maintenance_calendar.rst:277 +msgid "To add more data to the pivot table, click the :guilabel:`Measures` button to reveal a drop-down menu. By default, :guilabel:`Count` is selected. Additional options to add to the table are :guilabel:`Additional Leaves to Plan Ahead`, :guilabel:`Duration`, and :guilabel:`Repeat Every`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/maintenance/maintenance_calendar.rst:-1 +msgid "Measures options on Pivot view page." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/maintenance/maintenance_calendar.rst:285 +msgid "To the right of the :guilabel:`Measures` button is the :guilabel:`Insert in Spreadsheet` button. Clicking this button opens a pop-up window titled :guilabel:`Select a spreadsheet to insert your pivot.`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/maintenance/maintenance_calendar.rst:289 +msgid "There are two tabs in this pop-up window: :guilabel:`Spreadsheets` and :guilabel:`Dashboards`. Click into one of these tabs, and select a spreadsheet or dashboard in the database to add this pivot table to. Once ready, click :guilabel:`Confirm`. If this table shouldn't be added to a spreadsheet or dashboard, click :guilabel:`Cancel`, or click the :guilabel:`X` icon to close the pop-up window." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/maintenance/maintenance_calendar.rst:294 +msgid "To the right of the :guilabel:`Insert in Spreadsheet` button are three buttons:" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/maintenance/maintenance_calendar.rst:296 +msgid ":guilabel:`Flip axis`: the x and y axis of the pivot data table flip." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/maintenance/maintenance_calendar.rst:297 +msgid ":guilabel:`Expand all`: all the available rows and columns of the pivot data table expand fully." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/maintenance/maintenance_calendar.rst:298 +msgid ":guilabel:`Download xlsx`: the pivot data table is downloaded as an .xlsx file." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/maintenance/maintenance_calendar.rst:301 +msgid "Graph view" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/maintenance/maintenance_calendar.rst:303 +msgid "With the graph view selected, the following options appear between the search bar and visual representation of the data. These graph-specific options are located to the right of the :guilabel:`Measures` and :guilabel:`Insert in Spreadsheet` buttons." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/maintenance/maintenance_calendar.rst:-1 +msgid "Graph type icons on Graph view page." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/maintenance/maintenance_calendar.rst:311 +msgid "There are three different types of graphs available to users to view the data:" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/maintenance/maintenance_calendar.rst:313 +msgid ":guilabel:`Bar Chart`: the data is displayed in a bar chart." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/maintenance/maintenance_calendar.rst:314 +msgid ":guilabel:`Line Chart`: the data is displayed in a line chart." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/maintenance/maintenance_calendar.rst:315 +msgid ":guilabel:`Pie Chart`: the data is displayed in a pie chart." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/maintenance/maintenance_calendar.rst:317 +msgid "When viewing the data as a :guilabel:`Bar Chart` graph, the data can be formatted in the following ways:" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/maintenance/maintenance_calendar.rst:320 +#: ../../content/applications/inventory_and_mrp/maintenance/maintenance_calendar.rst:327 +msgid ":guilabel:`Stacked`: the data is stacked on the graph." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/maintenance/maintenance_calendar.rst:321 +#: ../../content/applications/inventory_and_mrp/maintenance/maintenance_calendar.rst:329 +msgid ":guilabel:`Descending`: the data is displayed in descending order." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/maintenance/maintenance_calendar.rst:322 +#: ../../content/applications/inventory_and_mrp/maintenance/maintenance_calendar.rst:330 +msgid ":guilabel:`Ascending`: the data is displayed in ascending order." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/maintenance/maintenance_calendar.rst:324 +msgid "When viewing the data as a :guilabel:`Line Chart` graph, the data can be formatted in the following ways:" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/maintenance/maintenance_calendar.rst:328 +msgid ":guilabel:`Cumulative`: the data is increasingly accumulated." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/maintenance/maintenance_calendar.rst:332 +msgid "When viewing the data as a :guilabel:`Pie Chart` graph, all relevant data is displayed by default, and no additional formatting options are available." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/maintenance/maintenance_calendar.rst:336 +msgid "Activity view" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/maintenance/maintenance_calendar.rst:338 +msgid "With the :guilabel:`Activity` view selected, all open maintenance requests are listed in their own row, with the ability to schedule activities related to those requests." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/maintenance/maintenance_calendar.rst:-1 +msgid "Maintenance requests on Activity view." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/maintenance/maintenance_calendar.rst:345 +msgid "Maintenance requests are listed in the :guilabel:`Maintenance Request` column as activities. Clicking a request opens a :guilabel:`Maintenance Request` popover that indicates the status of the request, and the responsible technician. To schedule an activity directly from the popover, click :guilabel:`➕ Schedule an activity`. This opens a :guilabel:`Schedule Activity` pop-up window." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/maintenance/maintenance_calendar.rst:350 +msgid "From the pop-up window, choose the :guilabel:`Activity Type`, provide a :guilabel:`Summary`, schedule a :guilabel:`Due Date`, and choose the responsible user in the :guilabel:`Assigned to` field." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/maintenance/maintenance_calendar.rst:-1 +msgid "Schedule Activity pop-up window." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/maintenance/maintenance_calendar.rst:358 +msgid "Type any additional notes for the new activity in the blank space under the greyed-out :guilabel:`Log a note...` field. When clicked, this changes to :guilabel:`Type \"/\" for commands`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/maintenance/maintenance_calendar.rst:361 +msgid "Once ready, click :guilabel:`Schedule` to schedule the activity. Alternatively, click :guilabel:`Schedule & Mark as Done` to close the activity, click :guilabel:`Done & Schedule Next` to close the activity and open a new one, or click :guilabel:`Cancel` to cancel the activity." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/maintenance/maintenance_calendar.rst:365 +msgid "With the :guilabel:`Activity` view selected, each activity type available when scheduling an activity is listed as its own column. These columns are :guilabel:`Email`, :guilabel:`Call`, :guilabel:`Meeting`, :guilabel:`Maintenance Request`, :guilabel:`To-Do`, :guilabel:`Upload Document`, :guilabel:`Request Signature`, and :guilabel:`Grant Approval`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/maintenance/maintenance_calendar.rst:370 +msgid "To schedule an activity with that specific activity type, click into any blank box on the corresponding row for the desired maintenance request, and click the :guilabel:`➕ (plus)` icon. This opens an :guilabel:`Odoo` pop-up window, wherein the activity can be scheduled." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/maintenance/maintenance_calendar.rst:-1 +msgid "Odoo pop-up schedule activity window." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/maintenance/maintenance_calendar.rst:379 +msgid ":doc:`maintenance_requests`" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/maintenance/maintenance_calendar.rst:380 +#: ../../content/applications/inventory_and_mrp/maintenance/maintenance_setup.rst:243 +msgid ":doc:`add_new_equipment`" +msgstr "" + #: ../../content/applications/inventory_and_mrp/maintenance/maintenance_requests.rst:3 msgid "Maintenance requests" msgstr "" @@ -12089,10 +13408,6 @@ msgstr "" msgid "In Odoo *Maintenance*, users can create *maintenance requests* to schedule and track the progress of equipment and work center maintenance." msgstr "" -#: ../../content/applications/inventory_and_mrp/maintenance/maintenance_requests.rst:16 -msgid "Create maintenance request" -msgstr "" - #: ../../content/applications/inventory_and_mrp/maintenance/maintenance_requests.rst:18 msgid "To create a new maintenance request, navigate to :menuselection:`Maintenance app --> Maintenance --> Maintenance Requests`, and click :guilabel:`New`." msgstr "" @@ -12197,1938 +13512,1508 @@ msgstr "" msgid "Failed maintenance requests should be moved to the :guilabel:`Scrap` stage, indicating the specified piece of equipment, or work center, could not be repaired, and must instead be scrapped." msgstr "" -#: ../../content/applications/inventory_and_mrp/manufacturing.rst:8 -msgid "Manufacturing" +#: ../../content/applications/inventory_and_mrp/maintenance/maintenance_setup.rst:3 +msgid "Maintenance setup" msgstr "" -#: ../../content/applications/inventory_and_mrp/manufacturing.rst:10 -msgid "**Odoo Manufacturing** helps manufacturers schedule, plan, and process manufacturing orders. With the work center control panel, put tablets on the shop floor to control work orders in real-time and allow workers to trigger maintenance operations, feedback loops, quality issues, etc." +#: ../../content/applications/inventory_and_mrp/maintenance/maintenance_setup.rst:8 +msgid "Odoo *Maintenance* helps companies schedule corrective and preventive maintenance on equipment used in their warehouse. This helps companies avoid equipment breakdowns, blocks in warehouse work centers, and emergency repair costs." msgstr "" -#: ../../content/applications/inventory_and_mrp/manufacturing.rst:15 -msgid "`Odoo Tutorials: MRP `_" +#: ../../content/applications/inventory_and_mrp/maintenance/maintenance_setup.rst:13 +msgid "Maintenance teams" msgstr "" -#: ../../content/applications/inventory_and_mrp/manufacturing.rst:16 -msgid "`Odoo Tutorials: Barcode Scanner `_" +#: ../../content/applications/inventory_and_mrp/maintenance/maintenance_setup.rst:15 +msgid "When creating maintenance requests, a *maintenance team* can be assigned to the request as the team responsible for handling the request." msgstr "" -#: ../../content/applications/inventory_and_mrp/manufacturing.rst:17 -msgid ":doc:`IoT Boxes (MES) `" +#: ../../content/applications/inventory_and_mrp/maintenance/maintenance_setup.rst:18 +msgid "To view existing maintenance teams, navigate to :menuselection:`Maintenance app --> Configuration --> Maintenance Teams`." msgstr "" -#: ../../content/applications/inventory_and_mrp/manufacturing/management.rst:5 -msgid "Manufacturing workflows" +#: ../../content/applications/inventory_and_mrp/maintenance/maintenance_setup.rst:21 +msgid "From the resulting :guilabel:`Teams` page, a list of all existing teams (if any) is displayed, with the :guilabel:`Team Name`, :guilabel:`Team Members`, and :guilabel:`Company` listed in the columns, by default." msgstr "" -#: ../../content/applications/inventory_and_mrp/manufacturing/management/bill_configuration.rst:3 -msgid "Bill of materials" +#: ../../content/applications/inventory_and_mrp/maintenance/maintenance_setup.rst:-1 +msgid "List of Teams on Maintenance Teams page." msgstr "" -#: ../../content/applications/inventory_and_mrp/manufacturing/management/bill_configuration.rst:7 -msgid "A *bill of materials* (or *BoM* for short) is a document that defines the quantity of each component required to make or deliver a finished product. It can also include various operations and the individual step guidelines needed to complete a production process." +#: ../../content/applications/inventory_and_mrp/maintenance/maintenance_setup.rst:29 +msgid "To add a new team, click :guilabel:`New`. This adds a blank line at the bottom of the list of teams. In the blank field that appears below the :guilabel:`Team Name` column, assign a name to the new maintenance team." msgstr "" -#: ../../content/applications/inventory_and_mrp/manufacturing/management/bill_configuration.rst:11 -msgid "In Odoo Manufacturing, multiple :abbr:`BoMs (Bills of Materials)` can be linked to each product, so even product variants can have their own tailored :abbr:`BoMs (Bills of Materials)`." +#: ../../content/applications/inventory_and_mrp/maintenance/maintenance_setup.rst:33 +msgid "In the :guilabel:`Team Members` column, click the field to reveal a drop-down menu with existing users in the database. Choose which users should be members of the new maintenance team." msgstr "" -#: ../../content/applications/inventory_and_mrp/manufacturing/management/bill_configuration.rst:14 -msgid "Correctly setting up a :abbr:`BoM (Bill of Materials)` helps optimize the manufacturing process and save time." +#: ../../content/applications/inventory_and_mrp/maintenance/maintenance_setup.rst:36 +msgid "Click :guilabel:`Search More...` to open a :guilabel:`Search: Team Members` pop-up window to search for users **not** shown on the initial drop-down menu." msgstr "" -#: ../../content/applications/inventory_and_mrp/manufacturing/management/bill_configuration.rst:18 -msgid "Set up a bill of materials (BoM)" +#: ../../content/applications/inventory_and_mrp/maintenance/maintenance_setup.rst:-1 +msgid "Search: Team Members pop-up window." msgstr "" -#: ../../content/applications/inventory_and_mrp/manufacturing/management/bill_configuration.rst:20 -msgid "The simplest :abbr:`BoM (Bill of Materials)` setup is one without operations or instructions, only components. In this case, the production is solely managed using *Manufacturing Orders*." +#: ../../content/applications/inventory_and_mrp/maintenance/maintenance_setup.rst:43 +msgid "In the :guilabel:`Company` column, if in a multi-company environment, click the drop-down menu to select the company in the database to which this new maintenance team belongs." msgstr "" -#: ../../content/applications/inventory_and_mrp/manufacturing/management/bill_configuration.rst:23 -msgid "To create a :abbr:`BoM (Bill of Materials)` from the :guilabel:`Manufacturing` module, go to :menuselection:`Products --> Bills of Materials`. Then, click :guilabel:`Create`. Next, specify the :guilabel:`Product`." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/manufacturing/management/bill_configuration.rst:28 -msgid "A :abbr:`BoM (Bill of Materials)` can also be created directly from the product form, in which case the :guilabel:`Product` field is pre-filled." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/manufacturing/management/bill_configuration.rst:31 -msgid "For a standard :abbr:`BoM (Bill of Materials)`, set the :guilabel:`BoM Type` to :guilabel:`Manufacture this Product`. Then, click :guilabel:`Add a Line` to specify the various components that make up the production of the final product and their respective quantities. New components can be created quickly through the :abbr:`BoM (Bill of Materials)`, or can be created beforehand in :menuselection:`Manufacturing --> Products --> Products --> Create`. Finally, click :guilabel:`Save` to finish creating the :abbr:`BoM (Bill of Materials)`." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/manufacturing/management/bill_configuration.rst:-1 -msgid "Set up a Bill of Materials." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/manufacturing/management/bill_configuration.rst:43 -msgid "Specify a bill of materials (BoM) for a product variant" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/manufacturing/management/bill_configuration.rst:45 -msgid ":abbr:`BoMs (Bills of Materials)` can also be assigned to specific *Product Variants*, with two setup options available to choose from." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/manufacturing/management/bill_configuration.rst:49 -msgid "In order to assign :abbr:`BoMs (Bills of Materials)` to product variants, the product's variant attributes must already be configured on the product form." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/manufacturing/management/bill_configuration.rst:52 -msgid "The first method is to create one :abbr:`BoM (Bill of Materials)` per variant by creating a new :abbr:`BoM (Bill of Materials)` and specifying the :guilabel:`Product Variant`. The second method is to create one master :abbr:`BoM (Bill of Materials)` that contains all of the components, and specify which variant each component applies to using the :guilabel:`Apply on Variants` column." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/manufacturing/management/bill_configuration.rst:-1 -msgid "Product Variants in the Bill of Materials." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/manufacturing/management/bill_configuration.rst:62 -msgid "Set up operations" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/manufacturing/management/bill_configuration.rst:64 -msgid "Add an :guilabel:`Operation` to a :abbr:`BoM (Bill of Materials)` to specify instructions for production and register time spent on an operation. To use this feature, first enable the :guilabel:`Work Orders` feature in :menuselection:`Manufacturing --> Configuration --> Settings --> Operations`." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/manufacturing/management/bill_configuration.rst:69 -msgid "Then, when creating a new :abbr:`BoM (Bill of Materials)`, click on the :guilabel:`Operations` tab and click :guilabel:`Add a line` to add a new operation. In the :guilabel:`Create Operations` box, give the operation a name, specify the :guilabel:`Work Center` and duration settings. Like components, Odoo gives the option to specify a product variant in the :guilabel:`Apply on Variants` field so the operation only applies to that variant. Finally, click :guilabel:`Save & Close`." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/manufacturing/management/bill_configuration.rst:76 -msgid "Each operation is unique, as it is always exclusively linked to one :abbr:`BoM (Bill of Materials)`. Operations can be reused when configuring a new :abbr:`BoM (Bill of Materials)`, with the :guilabel:`Copy Existing Operations` feature." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/manufacturing/management/bill_configuration.rst:-1 -msgid "Copy Existing Operations feature." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/manufacturing/management/bill_configuration.rst:85 -msgid "Add by-products to a bill of materials (BoM)" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/manufacturing/management/bill_configuration.rst:87 -msgid "A *By-Product* is a residual product that is created during production in addition to the main product of a :abbr:`BoM (Bill of Materials)`. Unlike the primary product, there can be more than one by-product on a :abbr:`BoM (Bill of Materials)`." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/manufacturing/management/bill_configuration.rst:91 -msgid "To add by-products to a :abbr:`BoM (Bill of Materials)`, first enable the :guilabel:`By-Products` feature in :menuselection:`Manufacturing --> Configuration --> Settings --> Operations`." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/manufacturing/management/bill_configuration.rst:94 -msgid "Once the feature is enabled, you can add by-products to a :abbr:`BoM (Bill of Materials)` by clicking on the :guilabel:`Operations` tab and clicking :guilabel:`Add a line`. Then, name the by-product and indicate the :guilabel:`Quantity` and the :guilabel:`Unit of Measure`. If the :abbr:`BoM (Bill of Materials)` has configured operations, specify exactly which operation the by-product is produced from in the :guilabel:`Produced in Operation` field. Finally, click :guilabel:`Save`." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/manufacturing/management/configure_manufacturing_product.rst:3 -msgid "Manufacturing product configuration" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/manufacturing/management/configure_manufacturing_product.rst:8 -msgid "In order to manufacture a product in Odoo *Manufacturing*, the product must be properly configured. Doing so consists of enabling the *Manufacturing* route and configuring a bill of materials (BoM) for the product. Once these steps are completed, the product is selectable when creating a new manufacturing order." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/manufacturing/management/configure_manufacturing_product.rst:14 -msgid "Activate the Manufacture route" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/manufacturing/management/configure_manufacturing_product.rst:16 -msgid "The Manufacture route is activated for each product on its own product page. To do so, begin by navigating to :menuselection:`Manufacturing --> Products --> Products`. Then, select an existing product, or create a new one by clicking :guilabel:`New`." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/manufacturing/management/configure_manufacturing_product.rst:20 -msgid "On the product page, select the :guilabel:`Inventory` tab, then enable the :guilabel:`Manufacture` checkbox in the :guilabel:`Routes` section. This tells Odoo the product can be manufactured." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/manufacturing/management/configure_manufacturing_product.rst:-1 -msgid "The Manufacturing route on the Inventory tab of a product page." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/manufacturing/management/configure_manufacturing_product.rst:28 -msgid "Configure a bill of materials (BoM)" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/manufacturing/management/configure_manufacturing_product.rst:30 -msgid "Next, a |BOM| must be configured for the product so Odoo knows how it is manufactured. A |BOM| is a list of the components and operations required to manufacture a product." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/manufacturing/management/configure_manufacturing_product.rst:33 -msgid "To create a |BOM| for a specific product, navigate to :menuselection:`Manufacturing --> Products --> Products`, then select the product. On the product page, click the :guilabel:`Bill of Materials` smart button at the top of the page, then select :guilabel:`New` to configure a new |BOM|." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/manufacturing/management/configure_manufacturing_product.rst:-1 -msgid "The Bill of Materials smart button on a product page." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/manufacturing/management/configure_manufacturing_product.rst:41 -msgid "On the |BOM|, the :guilabel:`Product` field auto-populates with the product. In the :guilabel:`Quantity` field, specify the number of units that the BoM produces." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/manufacturing/management/configure_manufacturing_product.rst:44 -msgid "Add a component to the |BOM| by selecting the :guilabel:`Components` tab and clicking :guilabel:`Add a line`. Select a component from the :guilabel:`Component` drop-down menu, then enter the quantity in the :guilabel:`Quantity` field. Continue adding components on new lines until all components have been added." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/manufacturing/management/configure_manufacturing_product.rst:-1 -msgid "The Components tab on a bill of materials." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/manufacturing/management/configure_manufacturing_product.rst:53 -msgid "Next, select the :guilabel:`Operations` tab. Click :guilabel:`Add a line` and a :guilabel:`Create Operations` pop-up window appears. In the :guilabel:`Operation` field, specify the name of the operation being added (e.g. Assemble, Cut, etc.). Select the work center where the operation will be carried out from the :guilabel:`Work Center` drop-down menu. Finally, click :guilabel:`Save & Close` to finish adding operations, or :guilabel:`Save & New` to add more." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/manufacturing/management/configure_manufacturing_product.rst:60 -msgid "The :guilabel:`Operations` tab only appears if the :guilabel:`Work Orders` setting is enabled. To do so, navigate to :menuselection:`Manufacturing --> Configuration --> Settings`, then enable the :guilabel:`Work Orders` checkbox." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/manufacturing/management/configure_manufacturing_product.rst:-1 -msgid "The Operations tab on a bill of materials." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/manufacturing/management/configure_manufacturing_product.rst:70 -msgid "The section above provides instructions for creating a basic |BOM| that allows a product to be manufactured in Odoo. However, it is by no means an exhaustive summary of all the options available when configuring a |BOM|. For more information about bills of materials, see the documentation on how to :ref:`create a bill of materials `." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/manufacturing/management/kit_shipping.rst:3 -msgid "Use kits" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/manufacturing/management/kit_shipping.rst:5 -msgid "In Odoo, a *kit* is a type of bill of materials (BoM) that can be manufactured and sold. Kits are sets of unassembled components sold to customers. They may be sold as standalone products, but are also useful tools for managing more complex bills of materials (BoMs)." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/manufacturing/management/kit_shipping.rst:10 -msgid "To use, manufacture, and sell kits, both the :guilabel:`Manufacturing` and :guilabel:`Inventory` apps need to be installed." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/manufacturing/management/kit_shipping.rst:14 -msgid "Create the kit as a product" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/manufacturing/management/kit_shipping.rst:16 -msgid "To use a kit as a sellable product, or simply as a component organization tool, the kit should first be created as a product." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/manufacturing/management/kit_shipping.rst:19 -msgid "To create a kit product, go to :menuselection:`Inventory app --> Products --> Products`, and click :guilabel:`Create`." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/manufacturing/management/kit_shipping.rst:22 -msgid "Then, assign a name to the new kit product. Next, under the :guilabel:`General Information` tab, set the :guilabel:`Product Type` to :guilabel:`Consumable`. Kit products work best as consumables, because the stock on-hand for kits is typically not tracked." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/manufacturing/management/kit_shipping.rst:27 -msgid "Although kits should almost always be set to :guilabel:`Consumable`, companies using **Anglo-Saxon** accounting might need to create kits as a :guilabel:`Storable Product`. This is because when processing invoices for kits, the Cost of Goods Sold (COGS) will be posted in accounting journals." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/manufacturing/management/kit_shipping.rst:32 -msgid "Unlike storable products, the :guilabel:`Routes` designation under the :guilabel:`Inventory` tab does not matter for kits, since Odoo uses the routes of the kit's individual components for replenishment purposes. All other parameters for the kit product may be modified according to preference. Once ready, click :guilabel:`Save` to save the new product." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/manufacturing/management/kit_shipping.rst:37 -msgid "The kit's components must also be configured as products via :menuselection:`Inventory app --> Products --> Products`. These components require no specific configuration." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/manufacturing/management/kit_shipping.rst:41 -msgid "Set up the kit BoM" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/manufacturing/management/kit_shipping.rst:43 -msgid "After fully configuring the kit product and its components, a new :abbr:`BoM (bill of materials)` can be created for the kit product." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/manufacturing/management/kit_shipping.rst:46 -msgid "To do so, go to :menuselection:`Manufacturing app --> Products --> Bills of Materials`, and click :guilabel:`Create`. Next to the :guilabel:`Product` field, click the drop-down menu to reveal a list of products, and select the previously configured kit product." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/manufacturing/management/kit_shipping.rst:50 -msgid "Then, for the :guilabel:`BoM Type` field, select the :guilabel:`Kit` option. Finally, under the :guilabel:`Components` tab, click :guilabel:`Add a line`, and add each desired component, and specify their quantities under the :guilabel:`Quantity` column." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/manufacturing/management/kit_shipping.rst:54 -msgid "Once ready, click :guilabel:`Save` to save the newly-created :abbr:`BoM (bill of materials)`." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/manufacturing/management/kit_shipping.rst:-1 -msgid "Kit selection on the bill of materials." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/manufacturing/management/kit_shipping.rst:60 -msgid "If the kit is solely being used as a sellable product, then only components need to be added under the :guilabel:`Components` tab, and configuring manufacturing operations is not necessary." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/manufacturing/management/kit_shipping.rst:64 -msgid "When a kit is sold as a product, it appears as a single line item on the quotation and sales order. However, on delivery orders, each component of the kit is listed." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/manufacturing/management/kit_shipping.rst:68 -msgid "Use kits to manage complex BoMs" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/manufacturing/management/kit_shipping.rst:70 -msgid "Kits are also used to manage multi-level :abbr:`BoMs (bills of materials)`. These are products that contain **other** :abbr:`BoM (bill of materials)` products as components, and therefore require *nested* :abbr:`BoMs (bills of materials)`. Incorporating pre-configured kits into multi-level :abbr:`BoMs (bills of materials)` allows for cleaner organization of bundled products." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/manufacturing/management/kit_shipping.rst:75 -msgid "To configure this type of :abbr:`BoM (bill of materials)` with a kit as a component, go to :menuselection:`Manufacturing app --> Products --> Bills of Materials`, and click :guilabel:`Create`." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/manufacturing/management/kit_shipping.rst:79 -msgid "Next to the :guilabel:`Product` field, click the drop-down menu to reveal a list of products, and select the desired :abbr:`BoM (bill of materials)` product. Then, for the :guilabel:`BoM Type` field, select the :guilabel:`Manufacture this product` option." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/manufacturing/management/kit_shipping.rst:83 -msgid "Under the :guilabel:`Components` tab, click :guilabel:`Add a line`, and select a kit as the component. Adding the kit as a component eliminates the need to add the kit's components individually. Any :guilabel:`BoM Type` can be used for the higher-level product's :abbr:`BoM (bill of materials)`." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/manufacturing/management/kit_shipping.rst:88 +#: ../../content/applications/inventory_and_mrp/maintenance/maintenance_setup.rst:46 +#: ../../content/applications/inventory_and_mrp/manufacturing/advanced_configuration/kit_shipping.rst:88 msgid "Once ready, click :guilabel:`Save` to save changes." msgstr "" -#: ../../content/applications/inventory_and_mrp/manufacturing/management/kit_shipping.rst:-1 +#: ../../content/applications/inventory_and_mrp/maintenance/maintenance_setup.rst:49 +msgid "The team members assigned to maintenance teams are also referred to as *Technicians*, when viewing the *Maintenance Calendar*." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/maintenance/maintenance_setup.rst:52 +msgid "Navigate to :menuselection:`Maintenance app --> Maintenance --> Maintenance Calendar`, and click on an existing maintenance request. From the resulting popover, locate the :guilabel:`Technician` field. The name listed in the field is the team member, and is the user responsible for that particular request." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/maintenance/maintenance_setup.rst:-1 +msgid "Maintenance request popover with Technician field shown." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/maintenance/maintenance_setup.rst:61 +msgid "At the far-right side of the page is a sidebar column, containing a minimized calendar set to today's date, and a :guilabel:`Technician` list, displaying all the technicians (or team members) with requests currently open." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/maintenance/maintenance_setup.rst:66 +msgid "Equipment" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/maintenance/maintenance_setup.rst:68 +msgid "In Odoo *Maintenance*, *equipment* refers to machines and tools used internally in warehouse work centers. Equipment can include technology such as computers or tablets, power tools, machines used for manufacturing, and more." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/maintenance/maintenance_setup.rst:73 +msgid "Equipment categories" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/maintenance/maintenance_setup.rst:75 +msgid "Each piece of equipment belongs to an *equipment category*. Before adding new equipment, make sure that a fitting equipment category is created." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/maintenance/maintenance_setup.rst:78 +msgid "To create a new equipment category, navigate to :menuselection:`Maintenance app --> Configuration --> Equipment Categories`, and click :guilabel:`New`. Doing so opens a blank equipment category form." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/maintenance/maintenance_setup.rst:-1 +msgid "Equipment category form with various information filled out." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/maintenance/maintenance_setup.rst:86 +msgid "On the blank form, assign a name in the :guilabel:`Category Name` field." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/maintenance/maintenance_setup.rst:88 +msgid "In the :guilabel:`Responsible` field, assign a user to be responsible for the equipment in this category, if necessary. By default, the user who creates the category is selected as :guilabel:`Responsible`, by default." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/maintenance/maintenance_setup.rst:92 +msgid "If in a multi-company environment, click the drop-down menu in the :guilabel:`Company` field, and select the company in the database to whom the equipment in this category belongs." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/maintenance/maintenance_setup.rst:95 +msgid "In the :guilabel:`Email Alias` field, assign an email alias to this category, if necessary." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/maintenance/maintenance_setup.rst:97 +msgid "In the :guilabel:`Comments` field, type any comments or notes for internal users to reference in relation to this category, if necessary." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/maintenance/maintenance_setup.rst:101 +msgid "Once a new equipment category is created, all equipment belonging to that category, as well as any past or currently open maintenance requests, are available from the equipment category form." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/maintenance/maintenance_setup.rst:104 +msgid "Navigate to :menuselection:`Maintenance app --> Configuration --> Equipment Categories`, and select a category to view. Locate the :guilabel:`Equipment` and :guilabel:`Maintenance` smart buttons at the top of the form." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/maintenance/maintenance_setup.rst:-1 +msgid "Equipment and Maintenance smart buttons on equipment category form." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/maintenance/maintenance_setup.rst:112 +msgid "Click the :guilabel:`Equipment` smart button to view all equipment belonging to this category. Click the :guilabel:`Maintenance` smart button to view any past, or currently open, maintenance requests." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/maintenance/maintenance_setup.rst:117 +msgid "Machines & tools" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/maintenance/maintenance_setup.rst:119 +msgid "To add new equipment, navigate to :menuselection:`Maintenance app --> Equipment --> Machines & Tools`, and click :guilabel:`New`. This opens a blank equipment form." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/maintenance/maintenance_setup.rst:122 +msgid "In the :guilabel:`Name` field, assign a name for the new equipment. In the :guilabel:`Equipment Category` field, click the drop-down menu and select which category this new equipment should belong to." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/maintenance/maintenance_setup.rst:126 +msgid "If in a multi-company environment, click the drop-down menu in the :guilabel:`Company` field, and select the company in the database to whom the new equipment belongs." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/maintenance/maintenance_setup.rst:129 +msgid "In the :guilabel:`Used By` field, select from one of three radio button options: :guilabel:`Department`, :guilabel:`Employee`, or :guilabel:`Other`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/maintenance/maintenance_setup.rst:-1 +msgid "Left-hand side of information fields on new equipment form." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/maintenance/maintenance_setup.rst:136 +msgid "If :guilabel:`Department` is selected, a :guilabel:`Department` field appears below the :guilabel:`Used By` field. Click the drop-down menu and select the department that uses this equipment." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/maintenance/maintenance_setup.rst:140 +msgid "If :guilabel:`Employee` is selected, an :guilabel:`Employee` field appears below the :guilabel:`Used By` field. Click the drop-down menu, and select the employee who uses this equipment." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/maintenance/maintenance_setup.rst:143 +msgid "If the :guilabel:`Other` option is selected, both the :guilabel:`Department` and :guilabel:`Employee` fields appear below the :guilabel:`Used By` field. Click the drop-down menus for the respective fields, and choose which department and employee uses this equipment." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/maintenance/maintenance_setup.rst:147 +msgid "In the :guilabel:`Maintenance Team` field, select the team responsible for this equipment. In the :guilabel:`Technician` field, select the team member/user responsible for this equipment." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/maintenance/maintenance_setup.rst:-1 +msgid "Right-hand side of information fields on new equipment form." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/maintenance/maintenance_setup.rst:154 +msgid "In the :guilabel:`Used in location` field, enter the location wherein this equipment will be used, if not in an internal work center (e.g. in an office)." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/maintenance/maintenance_setup.rst:157 +msgid "In the :guilabel:`Work Center` field, click the drop-down menu, and select which work center this equipment will be used in." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/maintenance/maintenance_setup.rst:160 +msgid "In the blank space under the :guilabel:`Description` tab at the bottom of the form, add any relevant information describing the equipment for users to reference." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/maintenance/maintenance_setup.rst:164 +msgid "Product Information tab" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/maintenance/maintenance_setup.rst:166 +msgid "To add any relevant information while creating a new piece of equipment, from the equipment form, click the :guilabel:`Product Information` tab." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/maintenance/maintenance_setup.rst:-1 +msgid "Product Information tab with available fields below it." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/maintenance/maintenance_setup.rst:173 +msgid "In the :guilabel:`Vendor` field, add the vendor from which the equipment was purchased. In the :guilabel:`Vendor Reference` field, add the product reference number obtained from the vendor, if applicable." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/maintenance/maintenance_setup.rst:177 +msgid "In the :guilabel:`Model` field, specify which model this equipment is, if applicable. If the equipment is serialized, add a serial number in the :guilabel:`Serial Number` field." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/maintenance/maintenance_setup.rst:180 +msgid "In the :guilabel:`Effective Date` field, click the date to reveal a calendar popover, and select a date. This date indicates when this equipment was first put in use, and will be used to compute the Mean Time Between Failure (MTBF) in the equipment's :guilabel:`Maintenance` tab." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/maintenance/maintenance_setup.rst:184 +msgid "In the :guilabel:`Cost` field, specify how much the equipment cost to acquire, if applicable." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/maintenance/maintenance_setup.rst:186 +msgid "If the equipment is covered under a warranty, specify the :guilabel:`Warranty Expiration Date` by selecting a date from the calendar popover in that field." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/maintenance/maintenance_setup.rst:190 +msgid "Maintenance tab" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/maintenance/maintenance_setup.rst:192 +msgid "Various maintenance metrics are available for each piece of equipment, and are automatically computed, based on corrective maintenance, and planned preventive maintenance." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/maintenance/maintenance_setup.rst:195 +msgid "To view the maintenance metrics for a specific piece of equipment, from the equipment form, click the :guilabel:`Maintenance` tab." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/maintenance/maintenance_setup.rst:-1 +msgid "Maintenance tab on equipment form showing computed metrics fields." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/maintenance/maintenance_setup.rst:202 +msgid "Doing so reveals the following fields:" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/maintenance/maintenance_setup.rst:204 +msgid ":guilabel:`Expected Mean Time Between Failure`: the amount of time (in days) before the next failure is expected. This is the **only** field not greyed-out, and the **only** field users can edit." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/maintenance/maintenance_setup.rst:207 +msgid ":guilabel:`Mean Time Between Failure`: the amount of time (in days) between reported failures. This value is computed based on completed corrective maintenances." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/maintenance/maintenance_setup.rst:209 +msgid ":guilabel:`Estimated Next Failure`: the date on which the next failure is expected. This date is computed as the Latest Failure Date + |MTBF|." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/maintenance/maintenance_setup.rst:211 +msgid ":guilabel:`Latest Failure`: The date of the latest failure. The value in this field updates once a failure is reported for this equipment." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/maintenance/maintenance_setup.rst:213 +msgid ":guilabel:`Mean Time To Repair`: the amount of time (in days) it takes to repair this equipment upon failure. This value updates once a maintenance request is completed for this equipment." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/maintenance/maintenance_setup.rst:217 +msgid "Work centers" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/maintenance/maintenance_setup.rst:219 +msgid "To view the work centers where equipment is being used, and how the equipment is being used in them, navigate to :menuselection:`Maintenance app --> Equipment --> Work Centers`, and click into a work center." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/maintenance/maintenance_setup.rst:223 +msgid "From the resulting work center form, click the :guilabel:`Equipment` tab to view all machines and tools being used in that specific work center." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/maintenance/maintenance_setup.rst:226 +msgid "Each piece of equipment is listed with certain relevant information: the :guilabel:`Equipment Name`, the responsible :guilabel:`Technician`, the :guilabel:`Equipment Category` it belongs to, and a few important maintenance metrics: its |MTBF|, |MTTR|, and :guilabel:`Est. Next Failure` date." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/maintenance/maintenance_setup.rst:-1 +msgid "List of equipment included in a work center." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/maintenance/maintenance_setup.rst:235 +msgid "To add new equipment to a work center directly from the work center form, click :guilabel:`Add a line` under the :guilabel:`Equipment` tab. This opens an :guilabel:`Add: Maintenance Equipment` pop-up window." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/maintenance/maintenance_setup.rst:239 +msgid "From the pop-up window, select the equipment that should be added to the work center, and click :guilabel:`Select`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing.rst:7 +msgid "Manufacturing" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing.rst:9 +msgid "**Odoo Manufacturing** helps manufacturers schedule, plan, and process manufacturing orders. With the work center control panel, put tablets on the shop floor to control work orders in real-time and allow workers to trigger maintenance operations, feedback loops, quality issues, etc." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing.rst:14 +msgid "`Odoo Tutorials: MRP `_" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing.rst:15 +msgid "`Odoo Tutorials: Barcode Scanner `_" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing.rst:16 +msgid ":doc:`IoT Boxes (MES) `" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/advanced_configuration.rst:5 +msgid "Advanced configuration" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/advanced_configuration/kit_shipping.rst:3 +msgid "Use kits" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/advanced_configuration/kit_shipping.rst:5 +msgid "In Odoo, a *kit* is a type of bill of materials (BoM) that can be manufactured and sold. Kits are sets of unassembled components sold to customers. They may be sold as standalone products, but are also useful tools for managing more complex bills of materials (BoMs)." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/advanced_configuration/kit_shipping.rst:10 +msgid "To use, manufacture, and sell kits, both the :guilabel:`Manufacturing` and :guilabel:`Inventory` apps need to be installed." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/advanced_configuration/kit_shipping.rst:14 +msgid "Create the kit as a product" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/advanced_configuration/kit_shipping.rst:16 +msgid "To use a kit as a sellable product, or simply as a component organization tool, the kit should first be created as a product." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/advanced_configuration/kit_shipping.rst:19 +msgid "To create a kit product, go to :menuselection:`Inventory app --> Products --> Products`, and click :guilabel:`Create`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/advanced_configuration/kit_shipping.rst:22 +msgid "Then, assign a name to the new kit product. Next, under the :guilabel:`General Information` tab, set the :guilabel:`Product Type` to :guilabel:`Consumable`. Kit products work best as consumables, because the stock on-hand for kits is typically not tracked." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/advanced_configuration/kit_shipping.rst:27 +msgid "Although kits should almost always be set to :guilabel:`Consumable`, companies using **Anglo-Saxon** accounting might need to create kits as a :guilabel:`Storable Product`. This is because when processing invoices for kits, the Cost of Goods Sold (COGS) will be posted in accounting journals." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/advanced_configuration/kit_shipping.rst:32 +msgid "Unlike storable products, the :guilabel:`Routes` designation under the :guilabel:`Inventory` tab does not matter for kits, since Odoo uses the routes of the kit's individual components for replenishment purposes. All other parameters for the kit product may be modified according to preference. Once ready, click :guilabel:`Save` to save the new product." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/advanced_configuration/kit_shipping.rst:37 +msgid "The kit's components must also be configured as products via :menuselection:`Inventory app --> Products --> Products`. These components require no specific configuration." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/advanced_configuration/kit_shipping.rst:41 +msgid "Set up the kit BoM" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/advanced_configuration/kit_shipping.rst:43 +msgid "After fully configuring the kit product and its components, a new :abbr:`BoM (bill of materials)` can be created for the kit product." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/advanced_configuration/kit_shipping.rst:46 +msgid "To do so, go to :menuselection:`Manufacturing app --> Products --> Bills of Materials`, and click :guilabel:`Create`. Next to the :guilabel:`Product` field, click the drop-down menu to reveal a list of products, and select the previously configured kit product." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/advanced_configuration/kit_shipping.rst:50 +msgid "Then, for the :guilabel:`BoM Type` field, select the :guilabel:`Kit` option. Finally, under the :guilabel:`Components` tab, click :guilabel:`Add a line`, and add each desired component, and specify their quantities under the :guilabel:`Quantity` column." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/advanced_configuration/kit_shipping.rst:54 +msgid "Once ready, click :guilabel:`Save` to save the newly-created :abbr:`BoM (bill of materials)`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/advanced_configuration/kit_shipping.rst:-1 +msgid "Kit selection on the bill of materials." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/advanced_configuration/kit_shipping.rst:60 +msgid "If the kit is solely being used as a sellable product, then only components need to be added under the :guilabel:`Components` tab, and configuring manufacturing operations is not necessary." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/advanced_configuration/kit_shipping.rst:64 +msgid "When a kit is sold as a product, it appears as a single line item on the quotation and sales order. However, on delivery orders, each component of the kit is listed." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/advanced_configuration/kit_shipping.rst:68 +msgid "Use kits to manage complex BoMs" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/advanced_configuration/kit_shipping.rst:70 +msgid "Kits are also used to manage multi-level :abbr:`BoMs (bills of materials)`. These are products that contain **other** :abbr:`BoM (bill of materials)` products as components, and therefore require *nested* :abbr:`BoMs (bills of materials)`. Incorporating pre-configured kits into multi-level :abbr:`BoMs (bills of materials)` allows for cleaner organization of bundled products." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/advanced_configuration/kit_shipping.rst:75 +msgid "To configure this type of :abbr:`BoM (bill of materials)` with a kit as a component, go to :menuselection:`Manufacturing app --> Products --> Bills of Materials`, and click :guilabel:`Create`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/advanced_configuration/kit_shipping.rst:79 +msgid "Next to the :guilabel:`Product` field, click the drop-down menu to reveal a list of products, and select the desired :abbr:`BoM (bill of materials)` product. Then, for the :guilabel:`BoM Type` field, select the :guilabel:`Manufacture this product` option." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/advanced_configuration/kit_shipping.rst:83 +msgid "Under the :guilabel:`Components` tab, click :guilabel:`Add a line`, and select a kit as the component. Adding the kit as a component eliminates the need to add the kit's components individually. Any :guilabel:`BoM Type` can be used for the higher-level product's :abbr:`BoM (bill of materials)`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/advanced_configuration/kit_shipping.rst:-1 msgid "Kit as a component in a multilevel bill of materials." msgstr "" -#: ../../content/applications/inventory_and_mrp/manufacturing/management/kit_shipping.rst:95 +#: ../../content/applications/inventory_and_mrp/manufacturing/advanced_configuration/kit_shipping.rst:95 msgid "Structure & cost" msgstr "" -#: ../../content/applications/inventory_and_mrp/manufacturing/management/kit_shipping.rst:97 +#: ../../content/applications/inventory_and_mrp/manufacturing/advanced_configuration/kit_shipping.rst:97 msgid "To access a comprehensive overview of the multi-level :abbr:`BoM's (bill of material's)` components, click on the :guilabel:`Structure & Cost` smart button. Sublevel :abbr:`BoMs (bills of materials)` can be expanded and viewed from this report." msgstr "" -#: ../../content/applications/inventory_and_mrp/manufacturing/management/kit_shipping.rst:-1 +#: ../../content/applications/inventory_and_mrp/manufacturing/advanced_configuration/kit_shipping.rst:-1 msgid "Expanded kit in the Structure and Cost report." msgstr "" -#: ../../content/applications/inventory_and_mrp/manufacturing/management/kit_shipping.rst:105 +#: ../../content/applications/inventory_and_mrp/manufacturing/advanced_configuration/kit_shipping.rst:105 msgid "When creating a manufacturing order for a product with a multi-level :abbr:`BoM (bill of materials)`, the kit product automatically expands to show all components. Any operations in the kit's :abbr:`BoM (bill of materials)` are also added to the list of work orders on the manufacturing order." msgstr "" -#: ../../content/applications/inventory_and_mrp/manufacturing/management/kit_shipping.rst:111 +#: ../../content/applications/inventory_and_mrp/manufacturing/advanced_configuration/kit_shipping.rst:111 msgid "Kits are primarily used to bundle components together for organization or sale. To manage multi-level products that require manufactured sub-components, refer to :doc:`this documentation ` on sub-assemblies." msgstr "" -#: ../../content/applications/inventory_and_mrp/manufacturing/management/manufacturing_backorders.rst:3 -msgid "Manufacturing backorders" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/manufacturing/management/manufacturing_backorders.rst:7 -msgid "In some cases, the full quantity of a manufacturing order cannot be produced immediately. When this happens, Odoo *Manufacturing* allows for the manufacturing of partial quantities of the order and creates a *backorder* for the remaining amount." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/manufacturing/management/manufacturing_backorders.rst:11 -msgid "In the *Manufacturing* app, creating a backorder splits the original manufacturing order into two orders. The reference tag for each order is the tag used for the original order, followed by a hyphen and then an additional number to indicate that it's a backorder." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/manufacturing/management/manufacturing_backorders.rst:16 -msgid "A company creates a manufacturing order with the reference tag *WH/MO/00175*, for 10 units of *Product X*. After starting work on the manufacturing order, the employee working the production line realizes there are only enough components in stock to produce five units of the product." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/manufacturing/management/manufacturing_backorders.rst:20 -msgid "Instead of waiting for additional stock of the components, they manufacture five units and create a backorder for the remaining five. This splits the manufacturing order into two separate orders: *WH/MO/00175-001* and *WH/MO/00175-002*." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/manufacturing/management/manufacturing_backorders.rst:24 -msgid "Order *001* contains the five units that have been manufactured, and is immediately marked as :guilabel:`Done`. Order *002* contains the five units that still need to be manufactured and is marked as :guilabel:`In Progress`. Once the remaining components are available, the employee returns to order *002* and manufactures the remaining units before closing the order." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/manufacturing/management/manufacturing_backorders.rst:30 -msgid "Create a manufacturing backorder" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/manufacturing/management/manufacturing_backorders.rst:32 -msgid "To create a backorder for part of a manufacturing order, begin by navigating to :menuselection:`Manufacturing --> Operations --> Manufacturing Orders`. Select a manufacturing order with a quantity of two or more or create one by clicking :guilabel:`Create`." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/manufacturing/management/manufacturing_backorders.rst:36 -msgid "If a new manufacturing order is created, select a product from the :guilabel:`Product` drop-down menu and enter a quantity of two or more in the :guilabel:`Quantity` field, then click :guilabel:`Confirm` to confirm the order." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/manufacturing/management/manufacturing_backorders.rst:40 -msgid "After manufacturing the quantity that is being produced immediately, enter that number in the :guilabel:`Quantity` field at the top of the manufacturing order." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/manufacturing/management/manufacturing_backorders.rst:-1 -msgid "The quantity field on a manufacturing order." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/manufacturing/management/manufacturing_backorders.rst:47 -msgid "Next, click :guilabel:`Validate`, and a :guilabel:`You produced less than initial demand` pop-up window appears, from which a backorder can be created. Click :guilabel:`Create Backorder` to split the manufacturing order into two separate orders, with the reference tags *WH/MO/XXXXX-001* and *WH/MO/XXXXX-002*." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/manufacturing/management/manufacturing_backorders.rst:-1 -msgid "The Create Backorder button on the \"You produced less than initial demand\" pop-up window." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/manufacturing/management/manufacturing_backorders.rst:56 -msgid "Order *001* contains the items that have been manufactured, and is closed immediately. Order *002* is the backorder that contains the items that have yet to be manufactured, and remains open, to be completed at a later date." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/manufacturing/management/manufacturing_backorders.rst:60 -msgid "Once the remaining units can be manufactured, navigate to :menuselection:`Manufacturing --> Operations --> Manufacturing Orders`, and then select the backorder manufacturing order. If all of the remaining units are manufactured immediately, simply click :guilabel:`Validate` to close the order." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/manufacturing/management/manufacturing_backorders.rst:65 -msgid "If only some of the remaining units are manufactured immediately, create another backorder for the remainder by following the steps detailed in this section." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/manufacturing/management/manufacturing_backorders.rst:69 -msgid "Create a backorder in Shop Floor" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/manufacturing/management/manufacturing_backorders.rst:71 -msgid "Backorders for manufacturing orders can also be created from the *Shop Floor* module." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/manufacturing/management/manufacturing_backorders.rst:74 -msgid "In order to use the *Shop Floor* module, the *Work Orders* setting must be enabled. To do so, navigate to :menuselection:`Manufacturing --> Configuration --> Settings`, enable the :guilabel:`Work Orders` checkbox, and then click :guilabel:`Save`." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/manufacturing/management/manufacturing_backorders.rst:78 -msgid "To create a backorder from the *Shop Floor* module, begin by navigating to :menuselection:`Manufacturing --> Operations --> Manufacturing Orders`. Select an |MO| for multiple units of a product, for which a backorder needs to be created." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/manufacturing/management/manufacturing_backorders.rst:82 -#: ../../content/applications/inventory_and_mrp/quality/quality_check_types/pass_fail_check.rst:121 -#: ../../content/applications/inventory_and_mrp/quality/quality_check_types/picture_check.rst:133 -#: ../../content/applications/inventory_and_mrp/quality/quality_management/quality_checks.rst:129 -msgid "On the |MO|, select the :guilabel:`Work Orders` tab, and then click the :guilabel:`Open Work Order (external link icon)` button on the line of the work order to be processed. On the resulting :guilabel:`Work Orders` pop-up window, click the :guilabel:`Open Shop Floor` button to open the *Shop Floor* module." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/manufacturing/management/manufacturing_backorders.rst:87 -#: ../../content/applications/inventory_and_mrp/quality/quality_check_types/instructions_check.rst:80 -#: ../../content/applications/inventory_and_mrp/quality/quality_check_types/pass_fail_check.rst:126 -#: ../../content/applications/inventory_and_mrp/quality/quality_management/quality_checks.rst:138 -msgid "When accessed from a specific work order, the *Shop Floor* module opens to the page for the work center where the order is configured to be processed, and isolates the work order's card so that no other cards are shown." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/manufacturing/management/manufacturing_backorders.rst:91 -msgid "Complete the steps on the work order's card until the :guilabel:`Register Production` step is reached, and then click on it to open the :guilabel:`Register Production` pop-up window." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/manufacturing/management/manufacturing_backorders.rst:95 -msgid "Do **not** click the :guilabel:`# Units` button on the right side of the step. Doing so automatically registers the full amount of units as having been produced." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/manufacturing/management/manufacturing_backorders.rst:98 -msgid "On the :guilabel:`Register Production` pop-up window, enter the number of units produced in the :guilabel:`Quantity` field. Make sure the number entered is *less* than the number of units listed to the right of the field. Then, click :guilabel:`Validate`." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/manufacturing/management/manufacturing_backorders.rst:-1 -msgid "The Register Production pop-up window in the Shop Floor module." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/manufacturing/management/manufacturing_backorders.rst:106 -msgid "The pop-up window disappears and the :guilabel:`# Units` button on the work order's card updates to reflect the number of units produced, as a fraction of the number of units for which the |MO| was originally created." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/manufacturing/management/manufacturing_backorders.rst:110 -msgid "Next, click the :guilabel:`Mark as Done` button at the bottom-right of the work order's card. The work order card begins to fade away. Once it disappears completely, a new work order card appears, titled with the original |MO|'s reference number with a `-002` tag added to the end of it." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/manufacturing/management/manufacturing_backorders.rst:114 -msgid "This new reference number represents the backorder |MO|. The original |MO|'s reference number now appears with a `-001` tag added to the end of it to distinguish it from the backorder |MO|." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/manufacturing/management/manufacturing_backorders.rst:117 -msgid "If the original |MO| has no remaining work orders, it can be closed by selecting the :guilabel:`All` filter in the top navigation of the *Shop Floor* module, and then clicking :guilabel:`Close Production` at the bottom of the |MO|'s card." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/manufacturing/management/manufacturing_backorders.rst:121 -msgid "If the original |MO| has remaining work orders that must be completed before it can be closed, cards for these work orders appear on the *Shop Floor* pages for the work centers where they are configured to be carried out. They can be processed as normal, and additional backorders can be created from their work order cards using the instructions detailed in this section." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/manufacturing/management/manufacturing_backorders.rst:126 -msgid "Once the current work order for the backorder |MO| is ready to be processed, this can also be completed as normal, and an additional backorder can be created from its work order card by following the instructions detailed in this section." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/manufacturing/management/manufacturing_backorders.rst:130 -msgid "After the final work order for the backorder |MO| has been completed, the |MO| can be closed by clicking the :guilabel:`Close Production` button at the bottom of the work order's card." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/manufacturing/management/one_step_manufacturing.rst:3 -msgid "One-step manufacturing" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/manufacturing/management/one_step_manufacturing.rst:9 -msgid "Odoo *Manufacturing* allows users to manufacture products using one, two, or three steps. When using one-step manufacturing, Odoo creates a manufacturing order (MO), but does not generate transfers for the movement of components out of inventory or finished products into stock. Inventory counts still update based on the number of components used and products manufactured, but the act of transferring them to and from inventory is not tracked." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/manufacturing/management/one_step_manufacturing.rst:16 -#: ../../content/applications/inventory_and_mrp/manufacturing/management/three_step_manufacturing.rst:15 -#: ../../content/applications/inventory_and_mrp/manufacturing/management/two_step_manufacturing.rst:16 -msgid "The number of steps used in manufacturing is set at the warehouse level, allowing for each warehouse to use a different number of steps. To change the number of steps used for a specific warehouse, begin by navigating to :menuselection:`Inventory --> Configuration --> Warehouses`, and then select a warehouse from the :guilabel:`Warehouses` screen." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/manufacturing/management/one_step_manufacturing.rst:21 -#: ../../content/applications/inventory_and_mrp/manufacturing/management/three_step_manufacturing.rst:20 -#: ../../content/applications/inventory_and_mrp/manufacturing/management/two_step_manufacturing.rst:21 -msgid "On the :guilabel:`Warehouse Configuration` tab, find the :guilabel:`Manufacture` radio input field, and select one of the three options: :guilabel:`Manufacture (1 step)`, :guilabel:`Pick components and then manufacture (2 steps)`, or :guilabel:`Pick components, manufacture and then store products (3 steps)`." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/manufacturing/management/one_step_manufacturing.rst:0 -#: ../../content/applications/inventory_and_mrp/manufacturing/management/three_step_manufacturing.rst:0 -#: ../../content/applications/inventory_and_mrp/manufacturing/management/two_step_manufacturing.rst:0 -msgid "The Manufacture radio input field on a warehouse configuration page." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/manufacturing/management/one_step_manufacturing.rst:31 -#: ../../content/applications/inventory_and_mrp/manufacturing/management/three_step_manufacturing.rst:30 -#: ../../content/applications/inventory_and_mrp/manufacturing/management/two_step_manufacturing.rst:31 -msgid "Products must be properly configured before they can be manufactured in Odoo. For details on how to do so, see the documentation on how to :ref:`configure a product for manufacturing `." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/manufacturing/management/one_step_manufacturing.rst:36 -#: ../../content/applications/inventory_and_mrp/manufacturing/management/three_step_manufacturing.rst:35 -#: ../../content/applications/inventory_and_mrp/manufacturing/management/two_step_manufacturing.rst:36 -msgid "Create manufacturing order" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/manufacturing/management/one_step_manufacturing.rst:38 -#: ../../content/applications/inventory_and_mrp/manufacturing/management/three_step_manufacturing.rst:37 -#: ../../content/applications/inventory_and_mrp/manufacturing/management/two_step_manufacturing.rst:38 -msgid "To manufacture a product in Odoo *Manufacturing*, begin by navigating to :menuselection:`Manufacturing --> Operations --> Manufacturing Orders`, and then click :guilabel:`New` to create a new |MO|." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/manufacturing/management/one_step_manufacturing.rst:42 -msgid "On the new |MO|, select the product to be produced from the :guilabel:`Product` drop-down menu. The :guilabel:`Bill of Material` field auto-populates with the associated bill of materials (BoM)." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/manufacturing/management/one_step_manufacturing.rst:45 -#: ../../content/applications/inventory_and_mrp/manufacturing/management/three_step_manufacturing.rst:44 -#: ../../content/applications/inventory_and_mrp/manufacturing/management/two_step_manufacturing.rst:45 -msgid "If a product has more than one |BOM| configured for it, the specific |BOM| can be selected in the :guilabel:`Bill of Material` field, and the :guilabel:`Product` field auto-populates with the associated product." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/manufacturing/management/one_step_manufacturing.rst:49 -#: ../../content/applications/inventory_and_mrp/manufacturing/management/three_step_manufacturing.rst:48 -#: ../../content/applications/inventory_and_mrp/manufacturing/management/two_step_manufacturing.rst:49 -msgid "After a |BOM| has been selected, the :guilabel:`Components` and :guilabel:`Work Orders` tabs auto-populate with the components and operations specified on the |BOM|. If additional components or operations are required for the |MO| being configured, add them to the :guilabel:`Components` and :guilabel:`Work Orders` tabs by clicking :guilabel:`Add a line`." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/manufacturing/management/one_step_manufacturing.rst:54 -#: ../../content/applications/inventory_and_mrp/manufacturing/management/three_step_manufacturing.rst:53 -#: ../../content/applications/inventory_and_mrp/manufacturing/management/two_step_manufacturing.rst:54 -msgid "Finally, click :guilabel:`Confirm` to confirm the |MO|." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/manufacturing/management/one_step_manufacturing.rst:57 -#: ../../content/applications/inventory_and_mrp/manufacturing/management/three_step_manufacturing.rst:80 -#: ../../content/applications/inventory_and_mrp/manufacturing/management/two_step_manufacturing.rst:77 -msgid "Process manufacturing order" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/manufacturing/management/one_step_manufacturing.rst:59 -#: ../../content/applications/inventory_and_mrp/manufacturing/management/three_step_manufacturing.rst:82 -#: ../../content/applications/inventory_and_mrp/manufacturing/management/two_step_manufacturing.rst:79 -msgid "An |MO| is processed by completing all of the work orders listed under its :guilabel:`Work Orders` tab. This can be done on the |MO| itself, or from the work order tablet view." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/manufacturing/management/one_step_manufacturing.rst:63 -#: ../../content/applications/inventory_and_mrp/manufacturing/management/three_step_manufacturing.rst:86 -#: ../../content/applications/inventory_and_mrp/manufacturing/management/two_step_manufacturing.rst:83 -msgid "Basic workflow" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/manufacturing/management/one_step_manufacturing.rst:65 -#: ../../content/applications/inventory_and_mrp/manufacturing/management/two_step_manufacturing.rst:85 -msgid "To complete work orders from the |MO| itself, begin by navigating to :menuselection:`Manufacturing --> Operations --> Manufacturing Orders`, and then select an |MO|." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/manufacturing/management/one_step_manufacturing.rst:68 -#: ../../content/applications/inventory_and_mrp/manufacturing/management/three_step_manufacturing.rst:91 -msgid "On the |MO| page, select the :guilabel:`Work Orders` tab. Once work begins on the first work order that needs to be completed, click the :guilabel:`Start` button for that work order. Odoo *Manufacturing* then starts a timer that keeps track of how long the work order takes to complete." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/manufacturing/management/one_step_manufacturing.rst:-1 -msgid "The Start button for an operation on a manufacturing order." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/manufacturing/management/one_step_manufacturing.rst:76 -#: ../../content/applications/inventory_and_mrp/manufacturing/management/three_step_manufacturing.rst:99 -#: ../../content/applications/inventory_and_mrp/manufacturing/management/two_step_manufacturing.rst:96 -msgid "When the work order is completed, click the :guilabel:`Done` button for that work order. Repeat the same process for each work order listed on the :guilabel:`Work Orders` tab." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/manufacturing/management/one_step_manufacturing.rst:-1 -msgid "The Done button for an operation on a manufacturing order." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/manufacturing/management/one_step_manufacturing.rst:83 -#: ../../content/applications/inventory_and_mrp/manufacturing/management/three_step_manufacturing.rst:106 -#: ../../content/applications/inventory_and_mrp/manufacturing/management/two_step_manufacturing.rst:103 -msgid "After completing all of the work orders, click :guilabel:`Produce All` at the top of the screen to mark the |MO| as :guilabel:`Done`, and register the manufactured product(s) into inventory." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/manufacturing/management/one_step_manufacturing.rst:87 -#: ../../content/applications/inventory_and_mrp/manufacturing/management/three_step_manufacturing.rst:110 -#: ../../content/applications/inventory_and_mrp/manufacturing/management/two_step_manufacturing.rst:107 -msgid "Shop Floor workflow" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/manufacturing/management/one_step_manufacturing.rst:89 -#: ../../content/applications/inventory_and_mrp/manufacturing/management/three_step_manufacturing.rst:112 -#: ../../content/applications/inventory_and_mrp/manufacturing/management/two_step_manufacturing.rst:109 -msgid "To complete the work orders for an |MO| using the *Shop Floor* module, begin by navigating to :menuselection:`Manufacturing --> Operations --> Manufacturing Orders`, and then select an |MO|." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/manufacturing/management/one_step_manufacturing.rst:92 -#: ../../content/applications/inventory_and_mrp/manufacturing/management/three_step_manufacturing.rst:115 -#: ../../content/applications/inventory_and_mrp/manufacturing/management/two_step_manufacturing.rst:112 -msgid "On the |MO|, click on the :guilabel:`Work Orders` tab, and then select the :guilabel:`↗️ (square with arrow coming out of it)` button on the line of the first work order to be processed. Doing so opens a :guilabel:`Work Orders` pop-up window, with details and processing options for the work order." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/manufacturing/management/one_step_manufacturing.rst:97 -#: ../../content/applications/inventory_and_mrp/manufacturing/management/three_step_manufacturing.rst:120 -#: ../../content/applications/inventory_and_mrp/manufacturing/management/two_step_manufacturing.rst:117 -msgid "On the pop-up window, select the :guilabel:`Open Shop Floor` button at the top-left of the window to open the *Shop Floor* module." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/manufacturing/management/one_step_manufacturing.rst:-1 -#: ../../content/applications/inventory_and_mrp/manufacturing/management/three_step_manufacturing.rst:-1 -#: ../../content/applications/inventory_and_mrp/manufacturing/management/two_step_manufacturing.rst:-1 -msgid "The Open Shop Floor button for a work order on a manufacturing order." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/manufacturing/management/one_step_manufacturing.rst:104 -#: ../../content/applications/inventory_and_mrp/manufacturing/management/three_step_manufacturing.rst:127 -#: ../../content/applications/inventory_and_mrp/manufacturing/management/two_step_manufacturing.rst:124 -msgid "When accessed directly from a specific work order within an |MO|, *Shop Floor* defaults to the page for the work center where the work order is configured to be carried out. The page shows a card for the work order that displays the |MO| number, the product and number of units to be produced, and the steps required to complete the work order." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/manufacturing/management/one_step_manufacturing.rst:-1 -#: ../../content/applications/inventory_and_mrp/manufacturing/management/three_step_manufacturing.rst:-1 -#: ../../content/applications/inventory_and_mrp/manufacturing/management/two_step_manufacturing.rst:-1 -msgid "A work order card on a work center page in the Shop Floor module." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/manufacturing/management/one_step_manufacturing.rst:113 -#: ../../content/applications/inventory_and_mrp/manufacturing/management/two_step_manufacturing.rst:133 -msgid "A work order is processed by completing each step listed on its card. This can be done by clicking on a step and following the instructions listed on the pop-up window that appears. Once the step is completed, click :guilabel:`Next` to move on to the next step, if any are required." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/manufacturing/management/one_step_manufacturing.rst:117 -#: ../../content/applications/inventory_and_mrp/manufacturing/management/three_step_manufacturing.rst:140 -#: ../../content/applications/inventory_and_mrp/manufacturing/management/two_step_manufacturing.rst:137 -msgid "Alternatively, work order steps can be completed by clicking the checkbox that appears on the right side of the step's line on the work order card. When using this method, the step is automatically marked as completed, without a pop-up window appearing." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/manufacturing/management/one_step_manufacturing.rst:121 -#: ../../content/applications/inventory_and_mrp/manufacturing/management/three_step_manufacturing.rst:144 -#: ../../content/applications/inventory_and_mrp/manufacturing/management/two_step_manufacturing.rst:141 -msgid "The final step on a work order card is titled *Register Production*. This step is used to register the number of product units that were produced. If the number produced is equal to the number that the |MO| was created for, click the :guilabel:`# Units` button on the right side of the line to automatically register that number as the quantity produced." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/manufacturing/management/one_step_manufacturing.rst:126 -#: ../../content/applications/inventory_and_mrp/manufacturing/management/three_step_manufacturing.rst:149 -#: ../../content/applications/inventory_and_mrp/manufacturing/management/two_step_manufacturing.rst:146 -msgid "If a different number must be entered, click the :guilabel:`Register Production` step to open a pop-up window. Enter the number of units produced in the :guilabel:`Units` field, and then click :guilabel:`Validate` to register that number." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/manufacturing/management/one_step_manufacturing.rst:131 -#: ../../content/applications/inventory_and_mrp/manufacturing/management/three_step_manufacturing.rst:154 -#: ../../content/applications/inventory_and_mrp/manufacturing/management/two_step_manufacturing.rst:151 -msgid "The *Register Production* step appears on every work order card. It must be completed for the first work order that is processed. After doing so, the step appears as already completed for each remaining work order in the |MO|." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/manufacturing/management/one_step_manufacturing.rst:135 -#: ../../content/applications/inventory_and_mrp/manufacturing/management/three_step_manufacturing.rst:158 -#: ../../content/applications/inventory_and_mrp/manufacturing/management/two_step_manufacturing.rst:155 -msgid "After completing all of the steps for a work order, a button appears on the footer of the work order card. If any other work orders must be completed before the |MO| can be closed, the button is titled :guilabel:`Mark as Done`. If there are no additional work orders to complete, the button is titled :guilabel:`Close Production`." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/manufacturing/management/one_step_manufacturing.rst:140 -#: ../../content/applications/inventory_and_mrp/manufacturing/management/three_step_manufacturing.rst:163 -#: ../../content/applications/inventory_and_mrp/manufacturing/management/two_step_manufacturing.rst:160 -msgid "Clicking :guilabel:`Mark as Done` causes the work order card to fade away. Once it disappears completely, the work order's status is marked as *Finished* on the |MO|, and the next work order appears in the *Shop Floor* module, on the page of the work center where it is configured to be carried out. Any additional work orders can be processed using the instructions detailed in this section." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/manufacturing/management/one_step_manufacturing.rst:146 -#: ../../content/applications/inventory_and_mrp/manufacturing/management/three_step_manufacturing.rst:169 -#: ../../content/applications/inventory_and_mrp/manufacturing/management/two_step_manufacturing.rst:166 -msgid "Clicking :guilabel:`Close Production` causes the work order card to fade away. Once it disappears, the |MO| is marked as *Done*, and the units of the product that were produced are entered into inventory." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/manufacturing/management/one_step_manufacturing.rst:150 -#: ../../content/applications/inventory_and_mrp/manufacturing/management/three_step_manufacturing.rst:173 -#: ../../content/applications/inventory_and_mrp/manufacturing/management/two_step_manufacturing.rst:170 -msgid "After clicking :guilabel:`Mark as Done` or :guilabel:`Close Production`, each button is replaced by an :guilabel:`Undo` button. Click the :guilabel:`Undo` button before the work order card fades away to keep the work order open." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/manufacturing/management/one_step_manufacturing.rst:155 -#: ../../content/applications/inventory_and_mrp/manufacturing/management/three_step_manufacturing.rst:178 -#: ../../content/applications/inventory_and_mrp/manufacturing/management/two_step_manufacturing.rst:175 -msgid "This section details the basic workflow for processing an |MO| in the *Shop Floor* module. For a more in-depth explanation of the module and all of its features, please see the :ref:`Shop Floor overview ` documentation." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/manufacturing/management/product_variants.rst:3 +#: ../../content/applications/inventory_and_mrp/manufacturing/advanced_configuration/product_variants.rst:3 msgid "Managing BoMs for product variants" msgstr "" -#: ../../content/applications/inventory_and_mrp/manufacturing/management/product_variants.rst:5 +#: ../../content/applications/inventory_and_mrp/manufacturing/advanced_configuration/product_variants.rst:5 msgid "Odoo allows one bill of materials (BoM) to be used for multiple variants of the same product. Having a consolidated :abbr:`BoM (bill of materials)` for a product with variants saves time by preventing the need to manage multiple :abbr:`BoMs (bills of materials)`." msgstr "" -#: ../../content/applications/inventory_and_mrp/manufacturing/management/product_variants.rst:10 +#: ../../content/applications/inventory_and_mrp/manufacturing/advanced_configuration/product_variants.rst:10 msgid "Activate product variants" msgstr "" -#: ../../content/applications/inventory_and_mrp/manufacturing/management/product_variants.rst:12 +#: ../../content/applications/inventory_and_mrp/manufacturing/advanced_configuration/product_variants.rst:12 msgid "To activate the product variants feature, navigate to :menuselection:`Inventory app --> Configuration --> Settings`, and scroll down to the :guilabel:`Products` section. Then, click the checkbox to enable the :guilabel:`Variants` option. After that, click :guilabel:`Save` to apply the setting." msgstr "" -#: ../../content/applications/inventory_and_mrp/manufacturing/management/product_variants.rst:17 +#: ../../content/applications/inventory_and_mrp/manufacturing/advanced_configuration/product_variants.rst:17 msgid "For more information on configuring product variants, refer to the :doc:`product variants <../../../sales/sales/products_prices/products/variants>` documentation." msgstr "" -#: ../../content/applications/inventory_and_mrp/manufacturing/management/product_variants.rst:-1 +#: ../../content/applications/inventory_and_mrp/manufacturing/advanced_configuration/product_variants.rst:-1 msgid "Selecting \"Variants\" from Inventory app settings." msgstr "" -#: ../../content/applications/inventory_and_mrp/manufacturing/management/product_variants.rst:25 +#: ../../content/applications/inventory_and_mrp/manufacturing/advanced_configuration/product_variants.rst:25 msgid "Create custom product attributes" msgstr "" -#: ../../content/applications/inventory_and_mrp/manufacturing/management/product_variants.rst:27 +#: ../../content/applications/inventory_and_mrp/manufacturing/advanced_configuration/product_variants.rst:27 msgid "Once the product variants feature is activated, create and edit product attributes on the :guilabel:`Attributes` page." msgstr "" -#: ../../content/applications/inventory_and_mrp/manufacturing/management/product_variants.rst:30 +#: ../../content/applications/inventory_and_mrp/manufacturing/advanced_configuration/product_variants.rst:30 msgid "The :guilabel:`Attributes` page is accessible either from :menuselection:`Inventory app --> Configuration --> Settings` by clicking the :guilabel:`Attributes` button, or by clicking :menuselection:`Inventory app --> Configuration --> Attributes`." msgstr "" -#: ../../content/applications/inventory_and_mrp/manufacturing/management/product_variants.rst:34 +#: ../../content/applications/inventory_and_mrp/manufacturing/advanced_configuration/product_variants.rst:34 msgid "Once on the :guilabel:`Attributes` page, either click into an existing attribute, or click :guilabel:`Create` to create a new one. Clicking :guilabel:`Create` reveals a new, blank form for customizing an attribute. For an existing attribute, click :guilabel:`Edit` on its form to make changes." msgstr "" -#: ../../content/applications/inventory_and_mrp/manufacturing/management/product_variants.rst:39 +#: ../../content/applications/inventory_and_mrp/manufacturing/advanced_configuration/product_variants.rst:39 msgid "Assign an :guilabel:`Attribute Name`, and choose a category from the :guilabel:`Category` field's drop-down menu. Then, select the desired options next to the :guilabel:`Display Type` and :guilabel:`Variants Creation Mode` fields. Once the desired options are selected, click :guilabel:`Add a line` under the :guilabel:`Attribute Values` tab to add a new value." msgstr "" -#: ../../content/applications/inventory_and_mrp/manufacturing/management/product_variants.rst:45 +#: ../../content/applications/inventory_and_mrp/manufacturing/advanced_configuration/product_variants.rst:45 msgid "Included on the :guilabel:`Value` row is a :guilabel:`Is custom value` checkbox. If selected, this value will be recognized as a custom value, which allows customers to type special customization requests upon ordering a custom variant of a product." msgstr "" -#: ../../content/applications/inventory_and_mrp/manufacturing/management/product_variants.rst:0 +#: ../../content/applications/inventory_and_mrp/manufacturing/advanced_configuration/product_variants.rst:0 msgid "Product variant attribute configuration screen." msgstr "" -#: ../../content/applications/inventory_and_mrp/manufacturing/management/product_variants.rst:54 +#: ../../content/applications/inventory_and_mrp/manufacturing/advanced_configuration/product_variants.rst:54 msgid "Once all desired :guilabel:`Values` have been added, click :guilabel:`Save` to save the new attribute." msgstr "" -#: ../../content/applications/inventory_and_mrp/manufacturing/management/product_variants.rst:58 +#: ../../content/applications/inventory_and_mrp/manufacturing/advanced_configuration/product_variants.rst:58 msgid "Add product variants on the product form" msgstr "" -#: ../../content/applications/inventory_and_mrp/manufacturing/management/product_variants.rst:60 +#: ../../content/applications/inventory_and_mrp/manufacturing/advanced_configuration/product_variants.rst:60 msgid "Created attributes can be applied on specific variants for particular products. To add product variants to a product, navigate to the product form by going to :menuselection:`Inventory app --> Products --> Products`. To make changes to the product, click :guilabel:`Edit`. Then, click the :guilabel:`Variants` tab." msgstr "" -#: ../../content/applications/inventory_and_mrp/manufacturing/management/product_variants.rst:65 +#: ../../content/applications/inventory_and_mrp/manufacturing/advanced_configuration/product_variants.rst:65 msgid "Under the :guilabel:`Attribute` header, click :guilabel:`Add a line` to add a new attribute, and select one to add from the drop-down menu." msgstr "" -#: ../../content/applications/inventory_and_mrp/manufacturing/management/product_variants.rst:68 +#: ../../content/applications/inventory_and_mrp/manufacturing/advanced_configuration/product_variants.rst:68 msgid "Then, under the :guilabel:`Values` header, click the drop-down menu to choose from the list of existing values. Click on each desired value to add them, and repeat this process for any additional attributes that should be added to the product." msgstr "" -#: ../../content/applications/inventory_and_mrp/manufacturing/management/product_variants.rst:72 +#: ../../content/applications/inventory_and_mrp/manufacturing/advanced_configuration/product_variants.rst:72 msgid "Once finished, click :guilabel:`Save` to save changes." msgstr "" -#: ../../content/applications/inventory_and_mrp/manufacturing/management/product_variants.rst:-1 +#: ../../content/applications/inventory_and_mrp/manufacturing/advanced_configuration/product_variants.rst:-1 msgid "Product form variants tab with values and attributes." msgstr "" -#: ../../content/applications/inventory_and_mrp/manufacturing/management/product_variants.rst:79 +#: ../../content/applications/inventory_and_mrp/manufacturing/advanced_configuration/product_variants.rst:79 msgid ":abbr:`BoM (bill of materials)` products with multiple variants that are manufactured in-house should either have a **0,0 reordering rule** set up, or have their replenishment routes set to *Replenish on Order (MTO)*." msgstr "" -#: ../../content/applications/inventory_and_mrp/manufacturing/management/product_variants.rst:84 +#: ../../content/applications/inventory_and_mrp/manufacturing/advanced_configuration/product_variants.rst:84 msgid "Apply BoM components to product variants" msgstr "" -#: ../../content/applications/inventory_and_mrp/manufacturing/management/product_variants.rst:86 +#: ../../content/applications/inventory_and_mrp/manufacturing/advanced_configuration/product_variants.rst:86 msgid "Next, create a new :abbr:`BoM (bill of materials)`. Or, edit an existing one, by going to :menuselection:`Manufacturing app --> Products --> Bills of Materials`. Then, click :guilabel:`Create` to open a new :guilabel:`Bills of Materials` form to configure from scratch." msgstr "" -#: ../../content/applications/inventory_and_mrp/manufacturing/management/product_variants.rst:90 +#: ../../content/applications/inventory_and_mrp/manufacturing/advanced_configuration/product_variants.rst:90 msgid "Add a product to the :abbr:`BoM (bill of materials)` by clicking the drop-down menu in the :guilabel:`Product` field and selecting the desired product." msgstr "" -#: ../../content/applications/inventory_and_mrp/manufacturing/management/product_variants.rst:93 +#: ../../content/applications/inventory_and_mrp/manufacturing/advanced_configuration/product_variants.rst:93 msgid "Then, add components by clicking :guilabel:`Add a line` under the :guilabel:`Component` section of the :guilabel:`Components` tab, and choosing the desired components from the drop-down menu." msgstr "" -#: ../../content/applications/inventory_and_mrp/manufacturing/management/product_variants.rst:96 +#: ../../content/applications/inventory_and_mrp/manufacturing/advanced_configuration/product_variants.rst:96 msgid "Choose the desired values in the :guilabel:`Quantity` and :guilabel:`Product Unit of Measure` columns. Then, choose the desired values in the :guilabel:`Apply on Variants` column." msgstr "" -#: ../../content/applications/inventory_and_mrp/manufacturing/management/product_variants.rst:100 +#: ../../content/applications/inventory_and_mrp/manufacturing/advanced_configuration/product_variants.rst:100 msgid "The :guilabel:`Apply on Variants` option to assign components to specific product variants on the :abbr:`BoM (bill of materials)` is available once the :guilabel:`Variants` setting is activated from the :menuselection:`Inventory` application. If the :guilabel:`Apply on Variants` field is not immediately visible, activate it from the additional options menu (three-dots icon, to the right of the header row)." msgstr "" -#: ../../content/applications/inventory_and_mrp/manufacturing/management/product_variants.rst:-1 +#: ../../content/applications/inventory_and_mrp/manufacturing/advanced_configuration/product_variants.rst:-1 msgid "\"Apply on Variants\" option on the additional options menu." msgstr "" -#: ../../content/applications/inventory_and_mrp/manufacturing/management/product_variants.rst:110 +#: ../../content/applications/inventory_and_mrp/manufacturing/advanced_configuration/product_variants.rst:110 msgid "Each component can be assigned to multiple variants. Components with no variants specified are used in every variant of the product. The same principle applies when configuring operations and by-products." msgstr "" -#: ../../content/applications/inventory_and_mrp/manufacturing/management/product_variants.rst:114 +#: ../../content/applications/inventory_and_mrp/manufacturing/advanced_configuration/product_variants.rst:114 msgid "When defining variant :abbr:`BoMs (bills of material)` by component assignment, the :guilabel:`Product Variant` field in the main section of the :abbr:`BoM (bill of materials)` should be left blank. This field is *only* used when creating a :abbr:`BoM (bill of materials)` specifically for one product variant." msgstr "" -#: ../../content/applications/inventory_and_mrp/manufacturing/management/product_variants.rst:119 +#: ../../content/applications/inventory_and_mrp/manufacturing/advanced_configuration/product_variants.rst:119 msgid "When all desired configurations have been made to the :abbr:`BoM (bill of materials)`, click :guilabel:`Save` at the top of the form to save changes." msgstr "" -#: ../../content/applications/inventory_and_mrp/manufacturing/management/product_variants.rst:123 +#: ../../content/applications/inventory_and_mrp/manufacturing/advanced_configuration/product_variants.rst:123 msgid "For components that only apply for specific variants, choose which operations the components should be consumed in. If the :guilabel:`Consumed in Operation` column is *not* immediately visible, activate it from the additional options menu (three-dots icon, to the right of the header row)." msgstr "" -#: ../../content/applications/inventory_and_mrp/manufacturing/management/product_variants.rst:129 +#: ../../content/applications/inventory_and_mrp/manufacturing/advanced_configuration/product_variants.rst:129 msgid "Sell and manufacture variants of BoM products" msgstr "" -#: ../../content/applications/inventory_and_mrp/manufacturing/management/product_variants.rst:131 +#: ../../content/applications/inventory_and_mrp/manufacturing/advanced_configuration/product_variants.rst:131 msgid "To sell and manufacture variants of :abbr:`BoM (bill of materials)` products to order, navigate to :menuselection:`Sales app --> Create` to create a new quotation." msgstr "" -#: ../../content/applications/inventory_and_mrp/manufacturing/management/product_variants.rst:135 +#: ../../content/applications/inventory_and_mrp/manufacturing/advanced_configuration/product_variants.rst:135 msgid "Sell variant of BoM product" msgstr "" -#: ../../content/applications/inventory_and_mrp/manufacturing/management/product_variants.rst:137 +#: ../../content/applications/inventory_and_mrp/manufacturing/advanced_configuration/product_variants.rst:137 msgid "Once on the blank :guilabel:`Quotation` form, click the drop-down next to the :guilabel:`Customer` field to add a customer." msgstr "" -#: ../../content/applications/inventory_and_mrp/manufacturing/management/product_variants.rst:140 +#: ../../content/applications/inventory_and_mrp/manufacturing/advanced_configuration/product_variants.rst:140 msgid "Then, under the :guilabel:`Order Lines` tab, click :guilabel:`Add a product`, and select the previously-created :abbr:`BoM (bill of materials)` product with variants from the drop-down menu. Doing so reveals a :guilabel:`Configure a product` pop-up." msgstr "" -#: ../../content/applications/inventory_and_mrp/manufacturing/management/product_variants.rst:144 +#: ../../content/applications/inventory_and_mrp/manufacturing/advanced_configuration/product_variants.rst:144 msgid "From the pop-up window, click the desired attribute options to configure the correct variant of the product to manufacture. Then, click the green :guilabel:`+` or :guilabel:`-` icons next to the `1` to change the quantity to sell and manufacture, if desired." msgstr "" -#: ../../content/applications/inventory_and_mrp/manufacturing/management/product_variants.rst:-1 +#: ../../content/applications/inventory_and_mrp/manufacturing/advanced_configuration/product_variants.rst:-1 msgid "Configure a product pop-up for choosing variant attributes." msgstr "" -#: ../../content/applications/inventory_and_mrp/manufacturing/management/product_variants.rst:152 +#: ../../content/applications/inventory_and_mrp/manufacturing/advanced_configuration/product_variants.rst:152 msgid "Once all the specifications have been chosen, click :guilabel:`Add`. This will change the pop-up to a second :guilabel:`Configure` pop-up, where available optional products will appear, if they have been created previously." msgstr "" -#: ../../content/applications/inventory_and_mrp/manufacturing/management/product_variants.rst:156 +#: ../../content/applications/inventory_and_mrp/manufacturing/advanced_configuration/product_variants.rst:156 msgid "Once ready, click :guilabel:`Confirm` to close the pop-up." msgstr "" -#: ../../content/applications/inventory_and_mrp/manufacturing/management/product_variants.rst:158 +#: ../../content/applications/inventory_and_mrp/manufacturing/advanced_configuration/product_variants.rst:158 msgid "Then, click :guilabel:`Save` to save all changes, and click :guilabel:`Confirm` at the top of the :guilabel:`Quotation` form to create and confirm a new sales order (SO)." msgstr "" -#: ../../content/applications/inventory_and_mrp/manufacturing/management/product_variants.rst:162 +#: ../../content/applications/inventory_and_mrp/manufacturing/advanced_configuration/product_variants.rst:162 msgid "Manufacture variant of BoM product" msgstr "" -#: ../../content/applications/inventory_and_mrp/manufacturing/management/product_variants.rst:164 +#: ../../content/applications/inventory_and_mrp/manufacturing/advanced_configuration/product_variants.rst:164 msgid "Once the :abbr:`SO (sales order)` is confirmed, a :guilabel:`Manufacturing` smart button appears at the top of the :abbr:`SO (sales order)` form. Click the :guilabel:`Manufacturing` smart button to open the :guilabel:`Manufacturing Order` form." msgstr "" -#: ../../content/applications/inventory_and_mrp/manufacturing/management/product_variants.rst:168 +#: ../../content/applications/inventory_and_mrp/manufacturing/advanced_configuration/product_variants.rst:168 msgid "On this form, under the :guilabel:`Components` tab, the appropriate components for the chosen variant are listed. And, depending on the variant, different components will be listed. To see any mandatory or optional :guilabel:`Operation` steps, click the :guilabel:`Work Orders` tab." msgstr "" -#: ../../content/applications/inventory_and_mrp/manufacturing/management/product_variants.rst:172 +#: ../../content/applications/inventory_and_mrp/manufacturing/advanced_configuration/product_variants.rst:172 msgid "To enter the tablet view work order screen, click the :guilabel:`tablet icon` to the right of the row for the desired operation to be completed." msgstr "" -#: ../../content/applications/inventory_and_mrp/manufacturing/management/product_variants.rst:175 +#: ../../content/applications/inventory_and_mrp/manufacturing/advanced_configuration/product_variants.rst:175 msgid "From the tablet view, click :guilabel:`Mark as Done` as the operation progresses to complete the operation steps." msgstr "" -#: ../../content/applications/inventory_and_mrp/manufacturing/management/product_variants.rst:178 +#: ../../content/applications/inventory_and_mrp/manufacturing/advanced_configuration/product_variants.rst:178 msgid "Alternatively, click the :guilabel:`Mark as Done` button at the top of the manufacturing order form to complete the order." msgstr "" -#: ../../content/applications/inventory_and_mrp/manufacturing/management/product_variants.rst:-1 +#: ../../content/applications/inventory_and_mrp/manufacturing/advanced_configuration/product_variants.rst:-1 msgid "Manufacturing order for variant of BoM product." msgstr "" -#: ../../content/applications/inventory_and_mrp/manufacturing/management/product_variants.rst:185 +#: ../../content/applications/inventory_and_mrp/manufacturing/advanced_configuration/product_variants.rst:185 msgid "Then, navigate back to the :abbr:`SO (sales order)` via the breadcrumbs at the top of the page." msgstr "" -#: ../../content/applications/inventory_and_mrp/manufacturing/management/product_variants.rst:187 +#: ../../content/applications/inventory_and_mrp/manufacturing/advanced_configuration/product_variants.rst:187 msgid "Now that the product has been manufactured, click the :guilabel:`Delivery` smart button to deliver the product to the customer. From the :guilabel:`Delivery Order` form, click :guilabel:`Validate`, then click :guilabel:`Apply` to deliver the product." msgstr "" -#: ../../content/applications/inventory_and_mrp/manufacturing/management/product_variants.rst:191 +#: ../../content/applications/inventory_and_mrp/manufacturing/advanced_configuration/product_variants.rst:191 msgid "To finish the sale, click back to the :abbr:`SO (sales order)` via the :guilabel:`breadcrumbs` at the top of the page again. Then, click :guilabel:`Create Invoice` followed by :guilabel:`Create Invoice` again to invoice the customer for the order." msgstr "" -#: ../../content/applications/inventory_and_mrp/manufacturing/management/scrap_manufacturing.rst:3 -msgid "Scrap during manufacturing" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/manufacturing/management/scrap_manufacturing.rst:7 -msgid "During the manufacturing process, the need to scrap manufacturing components or finished products may arise. This can be necessary if a component or product is damaged, or unusable for any other reason." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/manufacturing/management/scrap_manufacturing.rst:11 -msgid "By default, scrapping a component or finished product removes it from physical inventory and places it in a virtual location titled *Virtual Locations/Scrap*. A virtual location is **not** a physical space, but rather a designation in Odoo that is used to track items that are no longer in physical inventory." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/manufacturing/management/scrap_manufacturing.rst:17 -msgid "For more information, see the documentation about the different types of :ref:`locations `." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/manufacturing/management/scrap_manufacturing.rst:20 -msgid "Components can be scrapped from both the *Manufacturing* app and the *Shop Floor* module, before the associated manufacturing order (MO) is closed. Finished products can only be scrapped from the *Manufacturing* app, and only after closing the associated |MO|." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/manufacturing/management/scrap_manufacturing.rst:29 -msgid "To view the total quantity of each item scrapped, navigate to :menuselection:`Inventory --> Configuration --> Locations`, then remove the :guilabel:`Internal` filter from the :guilabel:`Search...` bar to display all virtual locations. From the list, select the :guilabel:`Virtual Locations/Scrap` location." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/manufacturing/management/scrap_manufacturing.rst:37 -#: ../../content/applications/inventory_and_mrp/manufacturing/management/scrap_manufacturing.rst:75 -msgid "Scrap pop-up window" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/manufacturing/management/scrap_manufacturing.rst:39 -msgid "Scrapping components and finished products is done through the :guilabel:`Scrap` pop-up window. The pop-up window can be accessed from an |MO| in the backend, or the *Shop Floor* module." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/manufacturing/management/scrap_manufacturing.rst:43 -msgid "Scrap component from Manufacturing" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/manufacturing/management/scrap_manufacturing.rst:45 -msgid "To scrap a component from an |MO|, begin by navigating to :menuselection:`Manufacturing --> Operations --> Manufacturing Orders`, and then select an |MO|. At the top of the |MO|, click the :guilabel:`Scrap` button to open the :guilabel:`Scrap` pop-up window." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/manufacturing/management/scrap_manufacturing.rst:50 -msgid "Scrap finished product from Manufacturing" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/manufacturing/management/scrap_manufacturing.rst:52 -msgid "To scrap a finished product from an |MO|, begin by navigating to :menuselection:`Manufacturing --> Operations --> Manufacturing Orders`. Select an open |MO|, and then click the :guilabel:`Produce All` button to close it." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/manufacturing/management/scrap_manufacturing.rst:56 -msgid "To select an |MO| that has already been closed, navigate to :menuselection:`Manufacturing --> Operations --> Manufacturing Orders`, remove the :guilabel:`To Do` filter from the :guilabel:`Search...` bar, and then select the desired |MO|." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/manufacturing/management/scrap_manufacturing.rst:60 -msgid "Once closed, click the :guilabel:`Scrap` button at the top of the |MO| to open the :guilabel:`Scrap` pop-up window." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/manufacturing/management/scrap_manufacturing.rst:64 -msgid "Scrap component from Shop Floor" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/manufacturing/management/scrap_manufacturing.rst:66 -msgid "To scrap a component from the *Shop Floor* module, begin by navigating to :menuselection:`Shop Floor`. Then, either click the :guilabel:`⋮ (three vertical dots)` button on an |MO| card, or select a work center from the top navigation, and click the :guilabel:`⋮ (three vertical dots)` button on a work order card." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/manufacturing/management/scrap_manufacturing.rst:71 -msgid "Either method opens the :guilabel:`What do you want to do?` pop-up window. Click the :guilabel:`Scrap` button on the window to open the :guilabel:`Scrap` pop-up window." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/manufacturing/management/scrap_manufacturing.rst:77 -msgid "After opening the scrap pop-up window using one of the methods :ref:`detailed above `, select the component or finished product being scrapped, from the :guilabel:`Product` drop-down menu." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/manufacturing/management/scrap_manufacturing.rst:81 -msgid "In the :guilabel:`Quantity` field, enter the quantity being scrapped." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/manufacturing/management/scrap_manufacturing.rst:83 -msgid "By default, the :guilabel:`Source Location` field is set to the warehouse's pre-production location, while the :guilabel:`Scrap Location` field is set to the :guilabel:`Virtual Locations/Scrap` location. If either the source or scrap location should be changed, select a different location from their respective drop-down menus." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/manufacturing/management/scrap_manufacturing.rst:88 -msgid "Enable the :guilabel:`Replenish Scrapped Quantities` checkbox if a picking order should be created to replace the scrapped component(s) upon confirmation of the scrap order. This option should only be enabled for warehouses with :doc:`two-step ` or :doc:`three-step ` manufacturing enabled, since components are not picked as part of the :doc:`one-step ` manufacturing process." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/manufacturing/management/scrap_manufacturing.rst:-1 -msgid "The Scrap pop-up window." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/manufacturing/management/scrap_manufacturing.rst:98 -msgid "Click the :guilabel:`Scrap` button to scrap the selected component. After one or more scrap orders have been created, a :guilabel:`Scraps` smart button appears at the top of the screen. Click it to view a list of all scrap orders for the |MO|." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/manufacturing/management/scrap_manufacturing.rst:102 -msgid "If a picking order was automatically created to replenish the scrapped components, it can be accessed by opening the :menuselection:`Inventory` app, clicking the :guilabel:`# To Process` button on the :guilabel:`Pick Components` card, and selecting the order." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/manufacturing/management/split_merge.rst:3 -msgid "Split and merge manufacturing orders" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/manufacturing/management/split_merge.rst:5 -msgid "In Odoo *Manufacturing*, it is possible to create manufacturing orders for a single unit of an item, or multiple units of the same item. In some cases, it may be necessary to split a manufacturing order that contains multiple units into two or more orders, or to merge two or more orders into a single order." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/manufacturing/management/split_merge.rst:11 -msgid "A manufacturing order can only contain one unit of a product, or multiple units of a single product that all use the same Bill of Materials (BoM). As a result, it is only possible to merge manufacturing orders when every order contains the same product being manufactured with the same BoM." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/manufacturing/management/split_merge.rst:17 -msgid "Split manufacturing orders" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/manufacturing/management/split_merge.rst:19 -msgid "To split a manufacturing order into multiple orders, begin by navigating to :menuselection:`Manufacturing --> Operations --> Manufacturing Orders`, then select a manufacturing order. At the top of the page, next to the :guilabel:`New` button, the manufacturing order's reference number appears with a :guilabel:`⚙️ (settings)` button next to it." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/manufacturing/management/split_merge.rst:24 -msgid "Click the :guilabel:`⚙️ (settings)` button to open the general settings for the manufacturing order, then select :guilabel:`Split`." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/manufacturing/management/split_merge.rst:-1 -msgid "The Settings and Split buttons on a manufacturing order." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/manufacturing/management/split_merge.rst:31 -msgid "After selecting :guilabel:`Split`, a :guilabel:`Split production` pop-up window appears. In the :guilabel:`Split #` field, enter the number of manufacturing orders that the original order should be split into, then click outside of the field. A table appears below, with a line for each new manufacturing order that will be created by the split. In the :guilabel:`Quantity To Produce` column, enter the number of units that will be assigned to each new manufacturing order. Finally, click :guilabel:`Split` to split the manufacturing order." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/manufacturing/management/split_merge.rst:-1 -msgid "The Split production pop-up window for a manufacturing order." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/manufacturing/management/split_merge.rst:42 -msgid "After clicking :guilabel:`Split`, the original manufacturing order is split into the number of orders that was specified in the :guilabel:`Split #` field. The reference numbers for the new manufacturing orders are the reference number for the original order with *-###* tags added to the end." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/manufacturing/management/split_merge.rst:48 -msgid "Manufacturing order *WH/MO/00012* is split into three separate orders. The reference numbers for the new orders are *WH/MO/00012-001*, *WH/MO/00012-002*, and *WH/MO/00012-003*." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/manufacturing/management/split_merge.rst:52 -msgid "Merge manufacturing orders" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/manufacturing/management/split_merge.rst:54 -msgid "To merge two or more manufacturing orders into a single order, begin by navigating to :menuselection:`Manufacturing --> Operations --> Manufacturing Orders`. Select the manufacturing orders that will be merged by activating the checkbox to the left of the name of each order." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/manufacturing/management/split_merge.rst:-1 -msgid "Select manufacturing orders that will be merged by clicking the checkbox for each." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/manufacturing/management/split_merge.rst:62 -msgid "Once all manufacturing orders have been selected, click the :guilabel:`Actions` button at the top of the page, then select :guilabel:`Merge` from the drop-down menu." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/manufacturing/management/split_merge.rst:-1 -msgid "The Actions and Merge buttons on the Manufacturing Orders page." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/manufacturing/management/split_merge.rst:69 -msgid "The selected manufacturing orders are merged into a single order. The reference number for the new manufacturing order is the next sequential number that has *not* already been assigned to an order." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/manufacturing/management/split_merge.rst:73 -msgid "The last reference number used for a manufacturing order was *WH/MO/00012*. Two manufacturing orders, *WH/MO/00008* and *WH/MO/00009*, are merged into a single order. The reference number for the manufacturing order created by the merger is *WH/MO/00013*." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/manufacturing/management/split_merge.rst:77 -msgid "In the :guilabel:`Source` field for the manufacturing order created by the merger, the reference numbers of the manufacturing orders that were merged are listed." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/manufacturing/management/split_merge.rst:81 -msgid "Manufacturing orders *WH/MO/00009* and *WH/MO/00010* are merged to create *WH/MO/00011*. The source field for *WH/MO/00011* lists both *WH/MO/00009* and *WH/MO/00010*." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/manufacturing/management/sub_assemblies.rst:3 +#: ../../content/applications/inventory_and_mrp/manufacturing/advanced_configuration/sub_assemblies.rst:3 msgid "Manage semi-finished products" msgstr "" -#: ../../content/applications/inventory_and_mrp/manufacturing/management/sub_assemblies.rst:5 +#: ../../content/applications/inventory_and_mrp/manufacturing/advanced_configuration/sub_assemblies.rst:5 msgid "A *semi-finished product*, also known as a *subassembly*, is a manufactured product that is used as a component in another product's bill of materials (BoM). Semi-finished products are used to simplify complex :abbr:`BoMs (Bills of Materials)` or to more accurately represent a manufacturing flow. A :abbr:`BoM (Bill of Materials)` that contains semi-finished products is referred to as a *multilevel BoM*, where the main *top-level product* and its subassemblies are distinguished." msgstr "" -#: ../../content/applications/inventory_and_mrp/manufacturing/management/sub_assemblies.rst:12 +#: ../../content/applications/inventory_and_mrp/manufacturing/advanced_configuration/sub_assemblies.rst:12 msgid "Configure semi-finished products" msgstr "" -#: ../../content/applications/inventory_and_mrp/manufacturing/management/sub_assemblies.rst:14 +#: ../../content/applications/inventory_and_mrp/manufacturing/advanced_configuration/sub_assemblies.rst:14 msgid "To set up a multilevel :abbr:`BoM (Bill of Materials)`, the top-level product and semi-finished products must be configured. Therefore, the first step is to create the semi-finished products and their :abbr:`BoMs (Bills of Materials)`." msgstr "" -#: ../../content/applications/inventory_and_mrp/manufacturing/management/sub_assemblies.rst:19 -msgid ":doc:`bill_configuration`" +#: ../../content/applications/inventory_and_mrp/manufacturing/advanced_configuration/sub_assemblies.rst:19 +msgid ":doc:`../basic_setup/bill_configuration`" msgstr "" -#: ../../content/applications/inventory_and_mrp/manufacturing/management/sub_assemblies.rst:-1 +#: ../../content/applications/inventory_and_mrp/manufacturing/advanced_configuration/sub_assemblies.rst:-1 msgid "A bill of materials for a semi-finished product." msgstr "" -#: ../../content/applications/inventory_and_mrp/manufacturing/management/sub_assemblies.rst:26 +#: ../../content/applications/inventory_and_mrp/manufacturing/advanced_configuration/sub_assemblies.rst:26 msgid "Create the top-level bill of materials (BoM)" msgstr "" -#: ../../content/applications/inventory_and_mrp/manufacturing/management/sub_assemblies.rst:28 +#: ../../content/applications/inventory_and_mrp/manufacturing/advanced_configuration/sub_assemblies.rst:28 msgid "After the semi-finished products are fully configured, navigate to :menuselection:`Manufacturing --> Products --> Products`. Then, :guilabel:`Create` the top-level product. Configure the product's specifications as desired, and be sure to :guilabel:`Save`." msgstr "" -#: ../../content/applications/inventory_and_mrp/manufacturing/management/sub_assemblies.rst:32 +#: ../../content/applications/inventory_and_mrp/manufacturing/advanced_configuration/sub_assemblies.rst:32 msgid "Once the top-level product is configured, click the :guilabel:`Bill of Materials` smart button on the product form, then click :guilabel:`Create` to make a :abbr:`BoM (Bill of Materials)` for the top-level product. Then, simply add the semi-finished products to this :abbr:`BoM (Bill of Materials)`, along with any other necessary components." msgstr "" -#: ../../content/applications/inventory_and_mrp/manufacturing/management/sub_assemblies.rst:-1 +#: ../../content/applications/inventory_and_mrp/manufacturing/advanced_configuration/sub_assemblies.rst:-1 msgid "A bill of materials for a top-level product, containing a subassembly component." msgstr "" -#: ../../content/applications/inventory_and_mrp/manufacturing/management/sub_assemblies.rst:42 +#: ../../content/applications/inventory_and_mrp/manufacturing/advanced_configuration/sub_assemblies.rst:42 msgid "Manage production planning" msgstr "" -#: ../../content/applications/inventory_and_mrp/manufacturing/management/sub_assemblies.rst:44 +#: ../../content/applications/inventory_and_mrp/manufacturing/advanced_configuration/sub_assemblies.rst:44 msgid "There are several methods to manage manufacturing order automation for products with multilevel :abbr:`BoMs (Bills of Materials)`." msgstr "" -#: ../../content/applications/inventory_and_mrp/manufacturing/management/sub_assemblies.rst:48 +#: ../../content/applications/inventory_and_mrp/manufacturing/advanced_configuration/sub_assemblies.rst:48 msgid "Semi-finished products are specifically used to manage manufacturable products with multilevel BoMs. If a BoM is being created simply to organize components or bundle sellable products, using :doc:`Kits ` is the more appropriate option." msgstr "" -#: ../../content/applications/inventory_and_mrp/manufacturing/management/sub_assemblies.rst:52 +#: ../../content/applications/inventory_and_mrp/manufacturing/advanced_configuration/sub_assemblies.rst:52 msgid "To automatically trigger manufacturing orders for semi-finished products after confirming a manufacturing order for the main product, there are two options:" msgstr "" -#: ../../content/applications/inventory_and_mrp/manufacturing/management/sub_assemblies.rst:55 +#: ../../content/applications/inventory_and_mrp/manufacturing/advanced_configuration/sub_assemblies.rst:55 msgid "**Option 1 (recommended):** Create *Reordering Rules* for the semi-finished products and set both the minimum and maximum desired stock quantities to `0`." msgstr "" -#: ../../content/applications/inventory_and_mrp/manufacturing/management/sub_assemblies.rst:59 +#: ../../content/applications/inventory_and_mrp/manufacturing/advanced_configuration/sub_assemblies.rst:59 #: ../../content/applications/inventory_and_mrp/purchase/products/temporary_reordering.rst:28 msgid ":doc:`../../purchase/products/reordering`" msgstr "" -#: ../../content/applications/inventory_and_mrp/manufacturing/management/sub_assemblies.rst:61 +#: ../../content/applications/inventory_and_mrp/manufacturing/advanced_configuration/sub_assemblies.rst:61 msgid "**Option 2:** Activate the :guilabel:`Replenish on Order (MTO)` and :guilabel:`Manufacture` routes under the :guilabel:`Inventory` tab of the semi-finished product's product form." msgstr "" -#: ../../content/applications/inventory_and_mrp/manufacturing/management/sub_assemblies.rst:64 +#: ../../content/applications/inventory_and_mrp/manufacturing/advanced_configuration/sub_assemblies.rst:64 msgid "Option 1 is more flexible than Option 2 and is therefore recommended. Reordering rules do not directly link demand to replenishment, and therefore allow stocks to be unreserved and redirected to other orders, if necessary. The Replenish on Order (MTO) route creates a unique link between the semi-finished and top-level products, exclusively reserving quantities for the confirmed top-level manufacturing order." msgstr "" -#: ../../content/applications/inventory_and_mrp/manufacturing/management/sub_assemblies.rst:70 +#: ../../content/applications/inventory_and_mrp/manufacturing/advanced_configuration/sub_assemblies.rst:70 msgid "Regardless of the method chosen, semi-finished products must be fully manufactured before manufacturing can begin on the top-level product." msgstr "" -#: ../../content/applications/inventory_and_mrp/manufacturing/management/sub_assemblies.rst:-1 +#: ../../content/applications/inventory_and_mrp/manufacturing/advanced_configuration/sub_assemblies.rst:-1 msgid "A manufacturing order for a top-level product." msgstr "" -#: ../../content/applications/inventory_and_mrp/manufacturing/management/subcontracting.rst:3 -msgid "Subcontract your Manufacturing" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/manufacturing/management/subcontracting.rst:5 -msgid "Outsourcing a portion or all of your company’s manufacturing needs is not easy. To make it work correctly, you have to:" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/manufacturing/management/subcontracting.rst:8 -msgid "Manage the inventory of raw materials at your subcontractor" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/manufacturing/management/subcontracting.rst:9 -msgid "Ship raw material to your subcontractors, at the right time" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/manufacturing/management/subcontracting.rst:10 -msgid "Control incoming goods quality" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/manufacturing/management/subcontracting.rst:11 -msgid "Control subcontractors bills" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/manufacturing/management/subcontracting.rst:13 -msgid "Here is an example of subcontracting the manufacturing of “C”, which is produced out of raw materials “A” and “B”." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/manufacturing/management/subcontracting.rst:20 -msgid "With its MRP subcontracting feature, Odoo helps you handle this flow easily." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/manufacturing/management/subcontracting.rst:25 -msgid "To use the subcontracting feature, go to :menuselection:`Manufacturing --> Configuration --> Settings` and tick the box *Subcontracting*." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/manufacturing/management/subcontracting.rst:32 -msgid "To define if a product must be subcontracted, use a *Bill of Materials (BoM)* of type *Subcontracting*." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/manufacturing/management/subcontracting.rst:35 -msgid "To create a new *BoM*, go to :menuselection:`Manufacturing --> Products --> Bill of Materials` and hit create. Then, list the components your subcontractor needs to manufacture the product. For costing purposes, you might want to register all the components, even the ones that are sourced directly from the subcontractor." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/manufacturing/management/subcontracting.rst:41 -msgid "Once you have set the *BoM Type* to *Subcontracting*, specify one or several subcontractors." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/manufacturing/management/subcontracting.rst:49 -msgid "Basic Subcontracting Flow" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/manufacturing/management/subcontracting.rst:51 -msgid "To let your subcontractor know how many products you need, create and send them purchase orders (PO). To do so, go to the *Purchase* app and create a new purchase order. Be sure to send the PO to a vendor that is defined as a subcontractor on the *BoM* of these products." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/manufacturing/management/subcontracting.rst:60 -msgid "Once the *PO* is validated (1), a pending receipt is created. When the products are received, validate the receipt (2), with the actual quantity received. As a result, Odoo does the following things for you:" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/manufacturing/management/subcontracting.rst:64 -msgid "Consumes the respective components at the subcontractor’s location, based on the *BoM* and your input (3);" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/manufacturing/management/subcontracting.rst:66 -msgid "Produces the finished goods at the subcontractor’s location (4);" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/manufacturing/management/subcontracting.rst:68 -msgid "Moves products from that subcontractor’s location to YourCompany via the validated receipt (5)." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/manufacturing/management/subcontracting.rst:73 -msgid "The *PO* is optional. If you create a receipt manually, with the right subcontractor, Odoo still performs all the moves. This can be useful if the subcontractor does not bill a fixed price per item, but rather the time and materials used." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/manufacturing/management/subcontracting.rst:79 -msgid "Inventory Valuation" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/manufacturing/management/subcontracting.rst:81 -msgid "The cost of the manufactured product “C” is defined as:" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/manufacturing/management/subcontracting.rst:83 -msgid "**C = A + B + s**" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/manufacturing/management/subcontracting.rst:85 -msgid "With:" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/manufacturing/management/subcontracting.rst:87 -msgid "**A**: Cost of raw materials coming from YourCompany;" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/manufacturing/management/subcontracting.rst:90 -msgid "**B**: Cost of raw materials sourced directly from the" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/manufacturing/management/subcontracting.rst:90 -msgid "subcontractor;" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/manufacturing/management/subcontracting.rst:92 -msgid "**s**: Cost of the subcontracted service." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/manufacturing/management/subcontracting.rst:94 -msgid "Sending raw materials to your subcontractors (**A**) does not impact the inventory valuation, as the components are still valued as part of your stock. This is managed by making the *Subcontracting Location* an *Internal Location*." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/manufacturing/management/subcontracting.rst:99 -msgid "Then, the vendor price set on the product C form has to be what has to be paid to the subcontractor for his parts and service time: **B + s**. The product cost has to be: **A + B + s**, how much the product is valued in the accounting." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/manufacturing/management/subcontracting.rst:104 -msgid "Finally, the subcontractor bill then matches the purchase order, with the proposed price coming from the finished products C." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/manufacturing/management/subcontracting.rst:108 -msgid "If managing the replenishment of raw materials **B** at your subcontractor’s location is not needed, simply include the cost of **B** in the subcontractor’s price **s** and remove the products *B* from the *BoM*." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/manufacturing/management/subcontracting.rst:116 -msgid "In case the received products from the subcontractor contain tracked components, their serial or lot numbers need to be specified during the receipt." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/manufacturing/management/subcontracting.rst:120 -msgid "In that case, on the receipt of the subcontracted product, a *Record Components* button appears. Click on it to open a dialog box and record the serial/lot numbers of the components. If the finished product is also tracked, its serial/lot number can be registered here too." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/manufacturing/management/subcontracting.rst:129 -msgid "For audit purposes, it is possible to check the lot numbers recorded on a receipt by using the icon on the right of the finished products:" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/manufacturing/management/subcontracting.rst:136 -msgid "Also note that in case flexible consumption has been selected on the subcontracted BOM for a non-tracked product, the record components option will also appear optionally on each move line, if you want to register more or less component consumption at your subcontracting location, when receiving your final product." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/manufacturing/management/subcontracting.rst:145 -msgid "As you can see, the reception of both of these non-tracked products can either be executed by selecting the 'Set Quantities' Option or via the move line hamburger menus." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/manufacturing/management/subcontracting.rst:149 -msgid "Automate Replenishment of Subcontractors" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/manufacturing/management/subcontracting.rst:151 -msgid "There are two ways to automate the supply of raw materials to your subcontractors when purchasing the final product. The chosen method depends on whether or not you want the materials to transit through your warehouse. Both of these methods are described as pull style mechanisms as their trigger is the inital PO to the subcontractor, which creates a need at the subcontracting location, for raw material." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/manufacturing/management/subcontracting.rst:158 -msgid "If you are supplying your subcontractor with raw material from your own warehouse, you must activate the 'Resupply Subcontractor on Order' route as shown below. If this is a component that you buy from a vendor, the buy route should also be activated." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/manufacturing/management/subcontracting.rst:169 -msgid "Now, if you want your vendor to resupply your subcontractor directly, you must choose the 'Dropship Subcontractor on Order' option instead. In order for this option to be active on the product form, you must first activate the dropship option from :menuselection:`Purchase --> Configuration --> Settings --> Dropshipping`. Once the PO to the subcontractor is validated, this route will create a dropship RFQ from your vendor to that subcontractor. You then just need to review and validate it." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/manufacturing/management/subcontracting.rst:182 -msgid "Note that the buy route is not selected in this case, as the dropship route is a buy route already." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/manufacturing/management/subcontracting.rst:185 -msgid "Finally, if you want to track the stock of these raw materials at your subcontracting location(s), then you must activate *Multi-locations* in :menuselection:`Inventory --> Configuration --> Settings --> Storage locations`." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/manufacturing/management/subcontracting.rst:189 -msgid "From the location form, you are then able to access the Current Stock." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/manufacturing/management/subcontracting.rst:198 -msgid "Manual Replenishment" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/manufacturing/management/subcontracting.rst:200 -msgid "You can also choose to replenish your subcontractors manually." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/manufacturing/management/subcontracting.rst:202 -msgid "If you want to send components to your subcontractor at your own convenience, select the 'Resupply Subcontractor' Operation Type from the *Inventory* Module, and create a picking, specifying to which subcontractor you are delivering to." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/manufacturing/management/subcontracting.rst:210 -msgid "Alternatively, you can also manually ask your vendor to resupply your subcontractor by creating a dropship type PO, with your subcontractor set as the delivery address." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/manufacturing/management/three_step_manufacturing.rst:3 -msgid "Three-step manufacturing" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/manufacturing/management/three_step_manufacturing.rst:9 -msgid "Odoo *Manufacturing* allows users to manufacture products using one, two, or three steps. When using three-step manufacturing, Odoo creates a pick components transfer, a manufacturing order (MO), and a store finished products transfer, and updates inventory counts based on the number of components removed, and finished products created." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/manufacturing/management/three_step_manufacturing.rst:41 -#: ../../content/applications/inventory_and_mrp/manufacturing/management/two_step_manufacturing.rst:42 -msgid "On the new |MO|, select the product to be produced from the :guilabel:`Product` drop-down menu. The :guilabel:`Bill of Material` field auto-populates with the associated Bill of Materials (BoM)." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/manufacturing/management/three_step_manufacturing.rst:56 -#: ../../content/applications/inventory_and_mrp/manufacturing/management/two_step_manufacturing.rst:57 -msgid "Process pick components transfer" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/manufacturing/management/three_step_manufacturing.rst:58 -msgid "After confirming a three-step |MO|, a :guilabel:`Transfers` smart button appears at the top of the page. Click it to be taken to the :guilabel:`Transfers` page for the |MO|. The page lists two transfers: *WH/PC/XXXXX* (the pick components transfer), and *WH/SFP/XXXXX* (the store finished products transfer)." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/manufacturing/management/three_step_manufacturing.rst:63 -msgid "Select :guilabel:`WH/PC/XXXXX` to open the pick components transfer for the |MO|. This transfer is used to track the movement of components from the locations where they are stored to the location where they are used to manufacture the product." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/manufacturing/management/three_step_manufacturing.rst:67 -#: ../../content/applications/inventory_and_mrp/manufacturing/management/two_step_manufacturing.rst:64 -msgid "After transferring the components out of their storage location, click :guilabel:`Validate` at the top of the transfer, followed by :guilabel:`Apply` on the :guilabel:`Immediate Transfer?` pop-up window that appears. Doing so marks the transfer as :guilabel:`Done`, and updates inventory counts to reflect the quantity of components transferred." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/manufacturing/management/three_step_manufacturing.rst:72 -#: ../../content/applications/inventory_and_mrp/manufacturing/management/two_step_manufacturing.rst:69 -msgid "Finally, return to the |MO| by clicking the :guilabel:`WH/MO/XXXXX` breadcrumb at the top of the page." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/manufacturing/management/three_step_manufacturing.rst:-1 -#: ../../content/applications/inventory_and_mrp/manufacturing/management/two_step_manufacturing.rst:-1 -msgid "The manufacturing order bread crumb on a pick components transfer." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/manufacturing/management/three_step_manufacturing.rst:88 -msgid "To complete work orders from the |MO| itself, begin by navigating to :menuselection:`Manufacturing --> Operations --> Manufacturing Orders`, and then select a manufacturing order." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/manufacturing/management/three_step_manufacturing.rst:-1 -msgid "The Start button for a work order on a manufacturing order." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/manufacturing/management/three_step_manufacturing.rst:-1 -msgid "The Done button for an work order on a manufacturing order." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/manufacturing/management/three_step_manufacturing.rst:136 -msgid "A work order is processed by completing each step listed on its card. This can be done by clicking on a step, and following the instructions listed on the pop-up window that appears. Once the step is completed, click :guilabel:`Next` to move on to the next step, if any are required." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/manufacturing/management/three_step_manufacturing.rst:183 -msgid "Process finished product transfer" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/manufacturing/management/three_step_manufacturing.rst:185 -msgid "After completing the |MO|, return to the order's :guilabel:`Transfers` page by clicking the :guilabel:`Transfers` button at the top of the order. This time, select :guilabel:`WH/SFP/XXXXX` to open the store finished products transfer. This transfer is used to track the movement of finished products from the location where they were manufactured to the location where they are stored." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/manufacturing/management/three_step_manufacturing.rst:190 -msgid "After transferring the finished products to their storage location, click :guilabel:`Validate` at the top of the transfer, followed by :guilabel:`Apply` on the :guilabel:`Immediate Transfer?` pop-up window that appears. Doing so marks the transfer as :guilabel:`Done`, and updates inventory counts to reflect the quantity of finished products transferred." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/manufacturing/management/two_step_manufacturing.rst:3 -msgid "Two-step manufacturing" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/manufacturing/management/two_step_manufacturing.rst:9 -msgid "Odoo *Manufacturing* allows users to manufacture products using one, two, or three steps. When using two-step manufacturing, Odoo creates a manufacturing order (MO) and a pick components transfer, but does not generate a transfer for the movement of finished products into stock. Inventory counts still update based on the number of products manufactured, but the act of transferring them to and from inventory is not tracked." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/manufacturing/management/two_step_manufacturing.rst:59 -msgid "After confirming a two-step |MO|, a :guilabel:`Transfers` smart button appears at the top of the page. Click it to open the pick components transfer for the |MO|. This transfer is used to track the movement of components from the locations where they are stored to the location where they are used to manufacture the product." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/manufacturing/management/two_step_manufacturing.rst:88 -msgid "On the |MO| page, select the :guilabel:`Work Orders` tab. Once work begins on the first work order that needs to be completed, click the :guilabel:`Start` button for that operation. Odoo *Manufacturing* then starts a timer that keeps track of how long the work order takes to complete." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/manufacturing/management/two_step_manufacturing.rst:-1 -msgid "The Start button for an work order on a manufacturing order." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/manufacturing/management/two_step_manufacturing.rst:-1 -msgid "The Done button for a work order on a manufacturing order." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/manufacturing/management/use_mps.rst:3 -msgid "Use the Master Production Schedule" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/manufacturing/management/use_mps.rst:7 -msgid "The Master Production Schedule (MPS) is a valuable tool to plan your production based on your demand forecast." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/manufacturing/management/use_mps.rst:13 -msgid "Go to the :menuselection:`Manufacturing app --> Configuration --> Settings` and activate the Master Production Schedule feature before hitting save." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/manufacturing/management/use_mps.rst:17 -msgid "In the MPS settings, you can define the time range of your MPS (month/week/day) and the number of periods you want to display at all times." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/manufacturing/management/use_mps.rst:20 -msgid "Now, go to :menuselection:`Planning --> Master Production Schedule` and click on *add a product*. You can now define your safety stock target (= the stock you want to have on hand at the end of the period) and the minimum and maximum quantities that must or can be replenished in each period." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/manufacturing/management/use_mps.rst:28 -msgid "In the MPS view, you can decide which information you would like to display by clicking on *rows*. For instance, the *Actual demand* will show you which quantity of products has already been ordered for the period, or *Available to Promise*, what can still be sold during that same period (what you plan to replenish - what is already sold during the period). You can also decide to hide rows if you like." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/manufacturing/management/use_mps.rst:38 -msgid "Estimate your demand and launch replenishment" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/manufacturing/management/use_mps.rst:40 -msgid "The next step is to estimate the demand for the chosen period. This is done in the *Forecasted Demand* Row. You can easily, at any time, compare the demand forecast with the actual demand (= confirmed sales). The demand forecast for a finished product will impact the indirect demand for its components." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/manufacturing/management/use_mps.rst:48 -msgid "Once the forecasted demand has been set, the quantity to replenish for the different periods will automatically be computed. The replenishments you are supposed to launch based on your lead times (vendor lead time or manufacturing lead time) are then displayed in green. You can now launch the replenishment by clicking on the replenish button." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/manufacturing/management/use_mps.rst:54 -msgid "Depending on the configuration of the product (buy vs. manufacture), requests for quotations or manufacturing orders will be created. You can easily access those by clicking on the *Actual Replenishment* cell." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/manufacturing/management/use_mps.rst:61 -msgid "In case you manually edit the *Suggested Replenishment* quantity, a small cross will appear on the left hand side of the cell. In case you want to go back to the automatically computed value given by Odoo, simply click the cross." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/manufacturing/management/use_mps.rst:67 -msgid "Cells color signification" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/manufacturing/management/use_mps.rst:69 -msgid "The cells, which are part of the *Suggested Replenishment* line, can take different colors depending on the situation:" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/manufacturing/management/use_mps.rst:72 -msgid "**Green**: quantity of products which should be replenished to reach the expected safety stock considering the demand forecast and the indirect demand forecast." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/manufacturing/management/use_mps.rst:74 -msgid "**Grey**: replenishment order has already been generated, and its quantity still matches current data." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/manufacturing/management/use_mps.rst:76 -msgid "**Red**: replenishment order has already been generated, and its quantity was too high considering current data." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/manufacturing/management/use_mps.rst:78 -msgid "**Orange**: replenishment order has already been generated, and its quantity was too low considering current data." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/manufacturing/management/use_mps.rst:80 -msgid "The *Forecasted stock* line can also contain red cells, which means the stock will be negative during the period in question." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/manufacturing/management/use_mps.rst:84 -msgid "What if I have underestimated the demand?" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/manufacturing/management/use_mps.rst:86 -msgid "You can still increase the demand forecast. It will impact the quantity to replenish. The cell will become orange, and you’ll be able to launch a new replenishment." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/manufacturing/management/use_mps.rst:91 -msgid "What if I have overestimated the demand?" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/manufacturing/management/use_mps.rst:93 -msgid "You can decrease the demand forecast. The cell will become red to inform you that you’ve ordered more than planned. If you’re still able to do it, you can cancel some RFQ or MO manually." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/manufacturing/management/use_mps.rst:98 -msgid "What if I wrongly added a product to the MPS?" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/manufacturing/management/use_mps.rst:100 -msgid "You can easily remove a product from the MPS by clicking the small bin on the right of its name." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/manufacturing/management/using_work_centers.rst:3 +#: ../../content/applications/inventory_and_mrp/manufacturing/advanced_configuration/using_work_centers.rst:3 msgid "Manage work orders using work centers" msgstr "" -#: ../../content/applications/inventory_and_mrp/manufacturing/management/using_work_centers.rst:5 +#: ../../content/applications/inventory_and_mrp/manufacturing/advanced_configuration/using_work_centers.rst:5 msgid "Odoo Manufacturing allows for work orders to be carried out at specific work centers. When a manufacturing order is created for a product, any work orders listed in the :guilabel:`Operations` tab of the product bill of materials (BoM) will be automatically created as well and assigned to the specified work center. Work orders can be managed in the :guilabel:`Manufacturing` module by selecting :menuselection:`Operations --> Work Orders`." msgstr "" -#: ../../content/applications/inventory_and_mrp/manufacturing/management/using_work_centers.rst:11 +#: ../../content/applications/inventory_and_mrp/manufacturing/advanced_configuration/using_work_centers.rst:11 msgid "In order to use work centers, the :guilabel:`Work Orders` feature must first be enabled. To do so, go to the :guilabel:`Manufacturing` module, select :menuselection:`Configuration --> Settings`, and activate the checkbox next to :guilabel:`Work Orders`. Work centers can then be created and managed by selecting :menuselection:`Configuration --> Work Centers`." msgstr "" -#: ../../content/applications/inventory_and_mrp/manufacturing/management/using_work_centers.rst:17 +#: ../../content/applications/inventory_and_mrp/manufacturing/advanced_configuration/using_work_centers.rst:17 msgid "Create a work center" msgstr "" -#: ../../content/applications/inventory_and_mrp/manufacturing/management/using_work_centers.rst:19 +#: ../../content/applications/inventory_and_mrp/manufacturing/advanced_configuration/using_work_centers.rst:19 msgid "Within the :guilabel:`Manufacturing` module, select :menuselection:`Configuration --> Work Centers --> Create`. The work center form can then be filled out as follows:" msgstr "" -#: ../../content/applications/inventory_and_mrp/manufacturing/management/using_work_centers.rst:22 +#: ../../content/applications/inventory_and_mrp/manufacturing/advanced_configuration/using_work_centers.rst:22 msgid ":guilabel:`Work Center Name`: give the work center a concise name that describes the type of operations it will be used for" msgstr "" -#: ../../content/applications/inventory_and_mrp/manufacturing/management/using_work_centers.rst:24 +#: ../../content/applications/inventory_and_mrp/manufacturing/advanced_configuration/using_work_centers.rst:24 msgid ":guilabel:`Alternative Workcenters`: specify an alternative work center for operations to be carried out at if the main work center is not available" msgstr "" -#: ../../content/applications/inventory_and_mrp/manufacturing/management/using_work_centers.rst:26 +#: ../../content/applications/inventory_and_mrp/manufacturing/advanced_configuration/using_work_centers.rst:26 msgid ":guilabel:`Code`: assign the work center a reference code" msgstr "" -#: ../../content/applications/inventory_and_mrp/manufacturing/management/using_work_centers.rst:27 +#: ../../content/applications/inventory_and_mrp/manufacturing/advanced_configuration/using_work_centers.rst:27 msgid ":guilabel:`Working Hours`: define the number of hours that the work center can be in use each week" msgstr "" -#: ../../content/applications/inventory_and_mrp/manufacturing/management/using_work_centers.rst:28 +#: ../../content/applications/inventory_and_mrp/manufacturing/advanced_configuration/using_work_centers.rst:28 msgid ":guilabel:`Company`: select the company that the work center belongs to" msgstr "" -#: ../../content/applications/inventory_and_mrp/manufacturing/management/using_work_centers.rst:-1 +#: ../../content/applications/inventory_and_mrp/manufacturing/advanced_configuration/using_work_centers.rst:-1 msgid "An example of a fully configured work center form." msgstr "" -#: ../../content/applications/inventory_and_mrp/manufacturing/management/using_work_centers.rst:37 +#: ../../content/applications/inventory_and_mrp/manufacturing/advanced_configuration/using_work_centers.rst:37 msgid "Set standards for work center productivity" msgstr "" -#: ../../content/applications/inventory_and_mrp/manufacturing/management/using_work_centers.rst:39 +#: ../../content/applications/inventory_and_mrp/manufacturing/advanced_configuration/using_work_centers.rst:39 msgid "The :guilabel:`General Information` tab on the work center form allows for productivity goals to be assigned to a work center:" msgstr "" -#: ../../content/applications/inventory_and_mrp/manufacturing/management/using_work_centers.rst:42 +#: ../../content/applications/inventory_and_mrp/manufacturing/advanced_configuration/using_work_centers.rst:42 msgid ":guilabel:`Time Efficiency`: used to calculate the expected duration of a work order at the work center; for example, if a work order normally takes one hour and the efficiency is set to 200%, the work order will take 30 minutes" msgstr "" -#: ../../content/applications/inventory_and_mrp/manufacturing/management/using_work_centers.rst:45 +#: ../../content/applications/inventory_and_mrp/manufacturing/advanced_configuration/using_work_centers.rst:45 msgid ":guilabel:`Capacity`: the number of operations that can be performed at the work center simultaneously" msgstr "" -#: ../../content/applications/inventory_and_mrp/manufacturing/management/using_work_centers.rst:47 +#: ../../content/applications/inventory_and_mrp/manufacturing/advanced_configuration/using_work_centers.rst:47 msgid ":guilabel:`OEE Target`: the target for efficiency at the work center" msgstr "" -#: ../../content/applications/inventory_and_mrp/manufacturing/management/using_work_centers.rst:48 +#: ../../content/applications/inventory_and_mrp/manufacturing/advanced_configuration/using_work_centers.rst:48 msgid ":guilabel:`Time before prod.`: setup time required before work can commence" msgstr "" -#: ../../content/applications/inventory_and_mrp/manufacturing/management/using_work_centers.rst:49 +#: ../../content/applications/inventory_and_mrp/manufacturing/advanced_configuration/using_work_centers.rst:49 msgid ":guilabel:`Time after prod.`: breakdown or cleanup time required after work is finished" msgstr "" -#: ../../content/applications/inventory_and_mrp/manufacturing/management/using_work_centers.rst:50 +#: ../../content/applications/inventory_and_mrp/manufacturing/advanced_configuration/using_work_centers.rst:50 msgid ":guilabel:`Cost per hour`: the cost of operating the work center for one hour" msgstr "" -#: ../../content/applications/inventory_and_mrp/manufacturing/management/using_work_centers.rst:51 +#: ../../content/applications/inventory_and_mrp/manufacturing/advanced_configuration/using_work_centers.rst:51 msgid ":guilabel:`Analytic Account`: the account where the cost of the work center should be recorded" msgstr "" -#: ../../content/applications/inventory_and_mrp/manufacturing/management/using_work_centers.rst:-1 +#: ../../content/applications/inventory_and_mrp/manufacturing/advanced_configuration/using_work_centers.rst:-1 msgid "The general information tab of the work center form." msgstr "" -#: ../../content/applications/inventory_and_mrp/manufacturing/management/using_work_centers.rst:58 +#: ../../content/applications/inventory_and_mrp/manufacturing/advanced_configuration/using_work_centers.rst:58 msgid "Assign equipment to a work center" msgstr "" -#: ../../content/applications/inventory_and_mrp/manufacturing/management/using_work_centers.rst:60 +#: ../../content/applications/inventory_and_mrp/manufacturing/advanced_configuration/using_work_centers.rst:60 msgid "Using the :guilabel:`Equipment` tab, it is possible for specific pieces of equipment to be assigned to a work center. The following information will be displayed for each piece of equipment added:" msgstr "" -#: ../../content/applications/inventory_and_mrp/manufacturing/management/using_work_centers.rst:63 +#: ../../content/applications/inventory_and_mrp/manufacturing/advanced_configuration/using_work_centers.rst:63 msgid ":guilabel:`Equipment Name`: the name of the piece of equipment" msgstr "" -#: ../../content/applications/inventory_and_mrp/manufacturing/management/using_work_centers.rst:64 +#: ../../content/applications/inventory_and_mrp/manufacturing/advanced_configuration/using_work_centers.rst:64 msgid ":guilabel:`Technician`: the technician responsible for servicing the equipment" msgstr "" -#: ../../content/applications/inventory_and_mrp/manufacturing/management/using_work_centers.rst:65 +#: ../../content/applications/inventory_and_mrp/manufacturing/advanced_configuration/using_work_centers.rst:65 msgid ":guilabel:`Equipment Category`: the category the equipment belongs to" msgstr "" -#: ../../content/applications/inventory_and_mrp/manufacturing/management/using_work_centers.rst:66 +#: ../../content/applications/inventory_and_mrp/manufacturing/advanced_configuration/using_work_centers.rst:66 msgid ":guilabel:`MTBF`: mean time between failures; the average time that the piece of equipment will operate before failing" msgstr "" -#: ../../content/applications/inventory_and_mrp/manufacturing/management/using_work_centers.rst:68 +#: ../../content/applications/inventory_and_mrp/manufacturing/advanced_configuration/using_work_centers.rst:68 msgid ":guilabel:`MTTR`: mean time to recovery; the average time it takes for the equipment to become fully operational again" msgstr "" -#: ../../content/applications/inventory_and_mrp/manufacturing/management/using_work_centers.rst:70 +#: ../../content/applications/inventory_and_mrp/manufacturing/advanced_configuration/using_work_centers.rst:70 msgid ":guilabel:`Est. Next Failure`: an estimate of when the next equipment failure will occur" msgstr "" -#: ../../content/applications/inventory_and_mrp/manufacturing/management/using_work_centers.rst:-1 +#: ../../content/applications/inventory_and_mrp/manufacturing/advanced_configuration/using_work_centers.rst:-1 msgid "The equipment tab of the work center form." msgstr "" -#: ../../content/applications/inventory_and_mrp/manufacturing/management/using_work_centers.rst:77 +#: ../../content/applications/inventory_and_mrp/manufacturing/advanced_configuration/using_work_centers.rst:77 msgid ":guilabel:`MTBF`, :guilabel:`MTTR`, and :guilabel:`Est. Next Failure` are all calculated automatically based on past failure data, if any exists." msgstr "" -#: ../../content/applications/inventory_and_mrp/manufacturing/management/using_work_centers.rst:83 +#: ../../content/applications/inventory_and_mrp/manufacturing/advanced_configuration/using_work_centers.rst:83 msgid "Integrate IoT devices" msgstr "" -#: ../../content/applications/inventory_and_mrp/manufacturing/management/using_work_centers.rst:85 +#: ../../content/applications/inventory_and_mrp/manufacturing/advanced_configuration/using_work_centers.rst:85 msgid "The :guilabel:`IoT Triggers` tab enables the integration of :abbr:`IoT (Internet of Things)` devices with a work center:" msgstr "" -#: ../../content/applications/inventory_and_mrp/manufacturing/management/using_work_centers.rst:88 +#: ../../content/applications/inventory_and_mrp/manufacturing/advanced_configuration/using_work_centers.rst:88 msgid ":guilabel:`Device`: specifies the IoT device to be triggered" msgstr "" -#: ../../content/applications/inventory_and_mrp/manufacturing/management/using_work_centers.rst:89 +#: ../../content/applications/inventory_and_mrp/manufacturing/advanced_configuration/using_work_centers.rst:89 msgid ":guilabel:`Key`: the security key for the device" msgstr "" -#: ../../content/applications/inventory_and_mrp/manufacturing/management/using_work_centers.rst:90 +#: ../../content/applications/inventory_and_mrp/manufacturing/advanced_configuration/using_work_centers.rst:90 msgid ":guilabel:`Action`: the IoT device action triggered" msgstr "" -#: ../../content/applications/inventory_and_mrp/manufacturing/management/using_work_centers.rst:-1 +#: ../../content/applications/inventory_and_mrp/manufacturing/advanced_configuration/using_work_centers.rst:-1 msgid "The IoT Triggers tab of the work center form." msgstr "" -#: ../../content/applications/inventory_and_mrp/manufacturing/management/using_work_centers.rst:97 +#: ../../content/applications/inventory_and_mrp/manufacturing/advanced_configuration/using_work_centers.rst:97 msgid "Use case: configure an alternative work center" msgstr "" -#: ../../content/applications/inventory_and_mrp/manufacturing/management/using_work_centers.rst:99 +#: ../../content/applications/inventory_and_mrp/manufacturing/advanced_configuration/using_work_centers.rst:99 msgid "When a work center is at capacity, it cannot accept any new work orders. Instead of waiting for the work center to become available, it is possible to specify an alternative work center where surplus work orders should be carried out." msgstr "" -#: ../../content/applications/inventory_and_mrp/manufacturing/management/using_work_centers.rst:103 +#: ../../content/applications/inventory_and_mrp/manufacturing/advanced_configuration/using_work_centers.rst:103 msgid "Begin by creating a new work center. Configure the :guilabel:`Equipment` tab so that it has all of the same equipment as the main work center. This will ensure that the same tasks can be carried out at both work centers. Navigate to the main work center and include the new work center in the :guilabel:`Alternative Workcenters` selection field." msgstr "" -#: ../../content/applications/inventory_and_mrp/manufacturing/management/using_work_centers.rst:108 +#: ../../content/applications/inventory_and_mrp/manufacturing/advanced_configuration/using_work_centers.rst:108 msgid "Now, create a new manufacturing order that uses the main work center for one of its operations. The main work center will automatically be selected for the operation in the :guilabel:`Work Orders` tab. After confirming the manufacturing order, click the :guilabel:`Plan` button that appears at the top left of the form." msgstr "" -#: ../../content/applications/inventory_and_mrp/manufacturing/management/using_work_centers.rst:-1 +#: ../../content/applications/inventory_and_mrp/manufacturing/advanced_configuration/using_work_centers.rst:-1 msgid "Click the plan button to automatically select an available work center." msgstr "" -#: ../../content/applications/inventory_and_mrp/manufacturing/management/using_work_centers.rst:117 +#: ../../content/applications/inventory_and_mrp/manufacturing/advanced_configuration/using_work_centers.rst:117 msgid "If the main work center is at capacity, the work center selected for the operation will be automatically changed to the alternative work center." msgstr "" -#: ../../content/applications/inventory_and_mrp/manufacturing/management/using_work_centers.rst:-1 +#: ../../content/applications/inventory_and_mrp/manufacturing/advanced_configuration/using_work_centers.rst:-1 msgid "The alternative work center is automatically selected." msgstr "" -#: ../../content/applications/inventory_and_mrp/manufacturing/management/using_work_centers.rst:125 +#: ../../content/applications/inventory_and_mrp/manufacturing/advanced_configuration/using_work_centers.rst:125 msgid "Monitor work center performance" msgstr "" -#: ../../content/applications/inventory_and_mrp/manufacturing/management/using_work_centers.rst:127 +#: ../../content/applications/inventory_and_mrp/manufacturing/advanced_configuration/using_work_centers.rst:127 msgid "Performance for an individual work center can be viewed by selecting :menuselection:`Configuration --> Work Centers`, and clicking on a work center. A variety of metrics showing work center performance can be viewed at the top right of the form:" msgstr "" -#: ../../content/applications/inventory_and_mrp/manufacturing/management/using_work_centers.rst:131 +#: ../../content/applications/inventory_and_mrp/manufacturing/advanced_configuration/using_work_centers.rst:131 msgid ":guilabel:`OEE`: overall effective efficiency, the percentage of time that the work center has been fully productive" msgstr "" -#: ../../content/applications/inventory_and_mrp/manufacturing/management/using_work_centers.rst:133 +#: ../../content/applications/inventory_and_mrp/manufacturing/advanced_configuration/using_work_centers.rst:133 msgid ":guilabel:`Lost`: the amount of time lost due to work stoppages" msgstr "" -#: ../../content/applications/inventory_and_mrp/manufacturing/management/using_work_centers.rst:134 +#: ../../content/applications/inventory_and_mrp/manufacturing/advanced_configuration/using_work_centers.rst:134 msgid ":guilabel:`Load`: the amount of time it will take to complete the current workload" msgstr "" -#: ../../content/applications/inventory_and_mrp/manufacturing/management/using_work_centers.rst:135 +#: ../../content/applications/inventory_and_mrp/manufacturing/advanced_configuration/using_work_centers.rst:135 msgid ":guilabel:`Performance`: the real duration of work time, shown as a percentage of the expected duration" msgstr "" -#: ../../content/applications/inventory_and_mrp/manufacturing/management/work_center_time_off.rst:3 -msgid "Make work centers unavailable using Time Off" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/manufacturing/management/work_center_time_off.rst:5 -msgid "In Odoo, *work centers* are used to carry out manufacturing operations at specific locations. However, if a work center cannot be used for some reason, work orders begin to pile up at the work center until it is operational again." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/manufacturing/management/work_center_time_off.rst:9 -msgid "As a result, it is necessary to make the work center unavailable in Odoo so that the platform routes new work orders to alternative work centers that are operational. Using Odoo *Time Off*, it is possible to designate a work center as being unavailable for a set period of time. Doing so ensures that manufacturing operations can continue until the impacted work center is available again." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/manufacturing/management/work_center_time_off.rst:17 -msgid "Before a work center can be designated as unavailable, the Odoo platform must be properly configured. First, it is necessary to enable :ref:`developer mode `. This allows the :guilabel:`Time Off` smart button to appear on each work center's :guilabel:`Working Hours` pop-up window." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/manufacturing/management/work_center_time_off.rst:22 -msgid "Enable developer mode by going to :menuselection:`Settings`, scrolling to the bottom of the page, and clicking :guilabel:`Activate the developer mode` under the :guilabel:`Developer Tools` heading." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/manufacturing/management/work_center_time_off.rst:-1 -msgid "The \"Activate the developer mode\" button." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/manufacturing/management/work_center_time_off.rst:29 -msgid "Next, install the *Time Off* app. This is the app used for assigning time off to all resources within Odoo, including employees and work centers. Navigate to :menuselection:`Apps`, then type `Time Off` in the :guilabel:`Search...` bar. The card for the :guilabel:`Time Off` module should be the only one that appears on the page. Click the green :guilabel:`Install` button on the card to install the app." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/manufacturing/management/work_center_time_off.rst:-1 -msgid "The Time Off module installation card." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/manufacturing/management/work_center_time_off.rst:39 -msgid "The last step is to properly configure work centers. For this workflow, it is necessary to have at least two work centers: one that is made unavailable and a second that receives the work orders that the other cannot accept. If no second work center is configured, Odoo cannot route work orders away from the unavailable work center and they will pile up in its queue." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/manufacturing/management/work_center_time_off.rst:44 -msgid "To create a work center, navigate to :menuselection:`Manufacturing --> Configuration --> Work Centers --> Create`." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/manufacturing/management/work_center_time_off.rst:47 -msgid "Make sure that both work centers have the same equipment listed under the :guilabel:`Equipment` tab. This ensures that operations carried out at one work center can also be performed at the other." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/manufacturing/management/work_center_time_off.rst:-1 -msgid "The equipment tab on a work center form." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/manufacturing/management/work_center_time_off.rst:54 -msgid "For the work center that will be made unavailable, select the second work center on the :guilabel:`Alternative Workcenters` drop-down menu. Now, Odoo knows to send work orders to the second work center when the first is unavailable for any reason." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/manufacturing/management/work_center_time_off.rst:-1 -msgid "A work center form configured with an alternative work center." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/manufacturing/management/work_center_time_off.rst:63 -msgid "Add time off for a work center" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/manufacturing/management/work_center_time_off.rst:65 -msgid "With configuration completed, time off can now be assigned to the work center that will be made unavailable. Begin by navigating to :menuselection:`Manufacturing --> Configuration --> Work Centers` and selecting the affected work center. Click :guilabel:`Edit`, and then the :guilabel:`↗ (external link)` button next to the :guilabel:`Working Hours` drop-down menu." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/manufacturing/management/work_center_time_off.rst:-1 -msgid "The Working Hours \"External link\" button on the work center form." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/manufacturing/management/work_center_time_off.rst:74 -msgid "A pop-up appears, titled :guilabel:`Open: Working Hours`. The standard working hours for the work center are listed here, along with various other details about it. Since developer mode was enabled, there is a :guilabel:`Time Off` button in the top right of the pop-up. Click it to be taken to the :guilabel:`Resource Time Off` page." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/manufacturing/management/work_center_time_off.rst:-1 -msgid "The Time Off button on the Working Hours pop-up." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/manufacturing/management/work_center_time_off.rst:83 -msgid "On this page, click :guilabel:`Create` to configure a new time-off entry. On the time-off form, note the :guilabel:`Reason` for the work center closure (broken, maintenance, etc.), select the affected work center as the :guilabel:`Resource`, and choose a :guilabel:`Start Date` and :guilabel:`End Date` to specify the period during which the work center will be unavailable. Click :guilabel:`Save` and the time off for the work center is logged in Odoo." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/manufacturing/management/work_center_time_off.rst:-1 -msgid "The \"Resource Time Off\" form." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/manufacturing/management/work_center_time_off.rst:94 -msgid "Route orders to an alternative work center" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/manufacturing/management/work_center_time_off.rst:96 -msgid "Once a work center is within its specified time-off period, work orders sent to it can be automatically routed to an alternative work center using the :guilabel:`Plan` button." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/manufacturing/management/work_center_time_off.rst:99 -msgid "Begin by creating a new manufacturing order by selecting :menuselection:`Operations --> Manufacturing Orders --> Create`. On the manufacturing order form, specify a :guilabel:`Product` that uses the unavailable work center for one of its operations. Click :guilabel:`Confirm` to confirm the work order." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/manufacturing/management/work_center_time_off.rst:104 -msgid "On the confirmed work order, select the :guilabel:`Work Orders` tab. By default, the unavailable work center is specified in the :guilabel:`Work Center` column. There is also a green :guilabel:`Plan` button on the top left of the page." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/manufacturing/management/work_center_time_off.rst:-1 -msgid "The Plan button on a manufacturing order." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/manufacturing/management/work_center_time_off.rst:112 -msgid "Click :guilabel:`Plan` and the work center listed under the :guilabel:`Work Orders` tab is automatically changed to the alternative work center." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/manufacturing/management/work_center_time_off.rst:-1 -msgid "The selected work center updates automatically after clicking the Plan button." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/manufacturing/management/work_center_time_off.rst:119 -msgid "Once the time-off period for the unavailable work center ends, Odoo recognizes that the work center is available again. At this point, clicking the :guilabel:`Plan` button does not route work orders to an alternative work center unless the first one is at capacity." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/manufacturing/management/work_order_dependencies.rst:3 +#: ../../content/applications/inventory_and_mrp/manufacturing/advanced_configuration/work_order_dependencies.rst:3 msgid "Work order dependencies" msgstr "" -#: ../../content/applications/inventory_and_mrp/manufacturing/management/work_order_dependencies.rst:7 +#: ../../content/applications/inventory_and_mrp/manufacturing/advanced_configuration/work_order_dependencies.rst:7 msgid "When manufacturing certain products, specific operations may need to be completed before others can begin. In order to ensure operations are carried out in the correct order, Odoo *Manufacturing* features a *work order dependencies* setting. Enabling this setting allows for operations on a Bill of Materials (BoM) to be *blocked* by other operations that should occur first." msgstr "" -#: ../../content/applications/inventory_and_mrp/manufacturing/management/work_order_dependencies.rst:15 +#: ../../content/applications/inventory_and_mrp/manufacturing/advanced_configuration/work_order_dependencies.rst:15 msgid "The *work order dependencies* setting is not enabled by default. To enable it, begin by navigating to :menuselection:`Manufacturing --> Configuration --> Settings`. Then, enable the :guilabel:`Work Orders` setting, if it is not already active." msgstr "" -#: ../../content/applications/inventory_and_mrp/manufacturing/management/work_order_dependencies.rst:19 +#: ../../content/applications/inventory_and_mrp/manufacturing/advanced_configuration/work_order_dependencies.rst:19 msgid "After enabling the :guilabel:`Work Orders` setting, the :guilabel:`Work Order Dependencies` setting appears below it. Enable :guilabel:`Work Order Dependencies`, then click :guilabel:`Save` to confirm the changes." msgstr "" -#: ../../content/applications/inventory_and_mrp/manufacturing/management/work_order_dependencies.rst:24 +#: ../../content/applications/inventory_and_mrp/manufacturing/advanced_configuration/work_order_dependencies.rst:24 msgid "Add dependencies to BoM" msgstr "" -#: ../../content/applications/inventory_and_mrp/manufacturing/management/work_order_dependencies.rst:26 +#: ../../content/applications/inventory_and_mrp/manufacturing/advanced_configuration/work_order_dependencies.rst:26 msgid "Work order dependencies are configured on a product's |BOM|. To do so, navigate to :menuselection:`Manufacturing --> Products --> Bills of Materials`, then select a |BOM|, or create a new one by clicking :guilabel:`New`." msgstr "" -#: ../../content/applications/inventory_and_mrp/manufacturing/management/work_order_dependencies.rst:32 +#: ../../content/applications/inventory_and_mrp/manufacturing/advanced_configuration/work_order_dependencies.rst:32 msgid "For a complete guide on how to properly configure a new |BOM|, see the documentation on :ref:`creating a bill of materials `." msgstr "" -#: ../../content/applications/inventory_and_mrp/manufacturing/management/work_order_dependencies.rst:35 +#: ../../content/applications/inventory_and_mrp/manufacturing/advanced_configuration/work_order_dependencies.rst:35 msgid "On the |BOM|, click on the :guilabel:`Miscellaneous` tab, then enable the :guilabel:`Operation Dependencies` checkbox. This makes a new :guilabel:`Blocked By` option available in the settings of the :guilabel:`Operations` tab." msgstr "" -#: ../../content/applications/inventory_and_mrp/manufacturing/management/work_order_dependencies.rst:-1 +#: ../../content/applications/inventory_and_mrp/manufacturing/advanced_configuration/work_order_dependencies.rst:-1 msgid "The Operation Dependencies checkbox on the Miscellaneous tab of a BoM." msgstr "" -#: ../../content/applications/inventory_and_mrp/manufacturing/management/work_order_dependencies.rst:43 +#: ../../content/applications/inventory_and_mrp/manufacturing/advanced_configuration/work_order_dependencies.rst:43 msgid "Next, click on the :guilabel:`Operations` tab. On the top-right of the tab, click on the tab's :guilabel:`settings` button, then enable the :guilabel:`Blocked By` checkbox. This makes a :guilabel:`Blocked By` field appear for each operation on the :guilabel:`Operations` tab." msgstr "" -#: ../../content/applications/inventory_and_mrp/manufacturing/management/work_order_dependencies.rst:-1 +#: ../../content/applications/inventory_and_mrp/manufacturing/advanced_configuration/work_order_dependencies.rst:-1 msgid "The settings for the Operations tab on a BoM." msgstr "" -#: ../../content/applications/inventory_and_mrp/manufacturing/management/work_order_dependencies.rst:51 +#: ../../content/applications/inventory_and_mrp/manufacturing/advanced_configuration/work_order_dependencies.rst:51 msgid "In the line of the operation that should be blocked by another operation, click the :guilabel:`Blocked By` field, and an :guilabel:`Open: Operations` pop-up window appears. In the :guilabel:`Blocked By` drop-down field on the pop-up window, select the blocking operation that must be completed *before* the operation that is blocked." msgstr "" -#: ../../content/applications/inventory_and_mrp/manufacturing/management/work_order_dependencies.rst:-1 +#: ../../content/applications/inventory_and_mrp/manufacturing/advanced_configuration/work_order_dependencies.rst:-1 msgid "The Blocked By drop-down field for an operation on a BoM." msgstr "" -#: ../../content/applications/inventory_and_mrp/manufacturing/management/work_order_dependencies.rst:60 +#: ../../content/applications/inventory_and_mrp/manufacturing/advanced_configuration/work_order_dependencies.rst:60 msgid "Finally, save the |BOM| by clicking :guilabel:`Save`." msgstr "" -#: ../../content/applications/inventory_and_mrp/manufacturing/management/work_order_dependencies.rst:63 +#: ../../content/applications/inventory_and_mrp/manufacturing/advanced_configuration/work_order_dependencies.rst:63 msgid "Plan work orders using dependencies" msgstr "" -#: ../../content/applications/inventory_and_mrp/manufacturing/management/work_order_dependencies.rst:65 +#: ../../content/applications/inventory_and_mrp/manufacturing/advanced_configuration/work_order_dependencies.rst:65 msgid "Once work order dependencies have been configured on a |BOM|, Odoo *Manufacturing* is able to plan when work orders are scheduled, based on their dependencies. To plan the work orders for a manufacturing order, begin by navigating to :menuselection:`Manufacturing --> Operations --> Manufacturing Orders`." msgstr "" -#: ../../content/applications/inventory_and_mrp/manufacturing/management/work_order_dependencies.rst:70 +#: ../../content/applications/inventory_and_mrp/manufacturing/advanced_configuration/work_order_dependencies.rst:70 msgid "Next, select a manufacturing order for a product with work order dependencies set on its |BOM|, or create a new manufacturing order by clicking :guilabel:`New`. If a new manufacturing order is created, select a |BOM| configured with work order dependencies from the :guilabel:`Bill of Material` drop-down field, then click :guilabel:`Confirm`." msgstr "" -#: ../../content/applications/inventory_and_mrp/manufacturing/management/work_order_dependencies.rst:75 +#: ../../content/applications/inventory_and_mrp/manufacturing/advanced_configuration/work_order_dependencies.rst:75 msgid "After confirming the manufacturing order, select the :guilabel:`Work Orders` tab to view the work orders required to complete it. Any work orders that are *not* blocked by a different work order display a `Ready` tag in the :guilabel:`Status` section." msgstr "" -#: ../../content/applications/inventory_and_mrp/manufacturing/management/work_order_dependencies.rst:79 +#: ../../content/applications/inventory_and_mrp/manufacturing/advanced_configuration/work_order_dependencies.rst:79 msgid "Work orders that are blocked by one or more work orders display a `Waiting for another WO` tag instead. Once the blocking work order(s) are completed, the tag updates to `Ready`." msgstr "" -#: ../../content/applications/inventory_and_mrp/manufacturing/management/work_order_dependencies.rst:-1 +#: ../../content/applications/inventory_and_mrp/manufacturing/advanced_configuration/work_order_dependencies.rst:-1 msgid "The status tags for work orders on a manufacturing order." msgstr "" -#: ../../content/applications/inventory_and_mrp/manufacturing/management/work_order_dependencies.rst:86 +#: ../../content/applications/inventory_and_mrp/manufacturing/advanced_configuration/work_order_dependencies.rst:86 msgid "To schedule the manufacturing order's work orders, click the :guilabel:`Plan` button at the top of the page. After doing so, the :guilabel:`Scheduled Start Date` field for each work order on the :guilabel:`Work Orders` tab auto-fills with the scheduled start date and time. A blocked work order is scheduled at the end of the time period specified in the :guilabel:`Expected Duration` field of the work order that precedes it." msgstr "" -#: ../../content/applications/inventory_and_mrp/manufacturing/management/work_order_dependencies.rst:-1 +#: ../../content/applications/inventory_and_mrp/manufacturing/advanced_configuration/work_order_dependencies.rst:-1 msgid "The Scheduled Start Date field for work orders on a manufacturing order." msgstr "" -#: ../../content/applications/inventory_and_mrp/manufacturing/management/work_order_dependencies.rst:97 +#: ../../content/applications/inventory_and_mrp/manufacturing/advanced_configuration/work_order_dependencies.rst:97 msgid "A manufacturing order is created for Product A. The manufacturing order has two operations: Cut and Assemble. Each operation has an expected duration of 60 minutes, and the Assemble operation is blocked by the Cut operation." msgstr "" -#: ../../content/applications/inventory_and_mrp/manufacturing/management/work_order_dependencies.rst:101 +#: ../../content/applications/inventory_and_mrp/manufacturing/advanced_configuration/work_order_dependencies.rst:101 msgid "The :guilabel:`Plan` button for the manufacturing order is clicked at 1:30 pm, and the Cut operation is scheduled to begin immediately. Since the Cut operation has an expected duration of 60 minutes, the Assemble operation is scheduled to begin at 2:30 pm." msgstr "" -#: ../../content/applications/inventory_and_mrp/manufacturing/management/work_order_dependencies.rst:106 +#: ../../content/applications/inventory_and_mrp/manufacturing/advanced_configuration/work_order_dependencies.rst:106 msgid "Planning by workcenter" msgstr "" -#: ../../content/applications/inventory_and_mrp/manufacturing/management/work_order_dependencies.rst:108 +#: ../../content/applications/inventory_and_mrp/manufacturing/advanced_configuration/work_order_dependencies.rst:108 msgid "To see a visual representation of how work orders are planned, navigate to the :guilabel:`Work Orders Planning` page by going to :menuselection:`Manufacturing --> Planning --> Planning by Workcenter`. This page shows a timeline of all the work orders scheduled for each operation." msgstr "" -#: ../../content/applications/inventory_and_mrp/manufacturing/management/work_order_dependencies.rst:112 +#: ../../content/applications/inventory_and_mrp/manufacturing/advanced_configuration/work_order_dependencies.rst:112 msgid "If one work order is blocked by the completion of another, the work order that is blocked is shown as scheduled to start after the work order blocking it. In addition, an arrow connects the two work orders, leading from the blocking operation to the blocked operation." msgstr "" -#: ../../content/applications/inventory_and_mrp/manufacturing/management/work_order_dependencies.rst:-1 +#: ../../content/applications/inventory_and_mrp/manufacturing/advanced_configuration/work_order_dependencies.rst:-1 msgid "The arrow connecting a blocked work order to the work order blocking it." msgstr "" +#: ../../content/applications/inventory_and_mrp/manufacturing/basic_setup.rst:5 +msgid "Basic setup" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/basic_setup/bill_configuration.rst:3 +msgid "Bill of materials" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/basic_setup/bill_configuration.rst:7 +msgid "A *bill of materials* (or *BoM* for short) is a document that defines the quantity of each component required to make or deliver a finished product. It can also include various operations and the individual step guidelines needed to complete a production process." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/basic_setup/bill_configuration.rst:11 +msgid "In Odoo Manufacturing, multiple :abbr:`BoMs (Bills of Materials)` can be linked to each product, so even product variants can have their own tailored :abbr:`BoMs (Bills of Materials)`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/basic_setup/bill_configuration.rst:14 +msgid "Correctly setting up a :abbr:`BoM (Bill of Materials)` helps optimize the manufacturing process and save time." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/basic_setup/bill_configuration.rst:18 +msgid "Set up a bill of materials (BoM)" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/basic_setup/bill_configuration.rst:20 +msgid "The simplest :abbr:`BoM (Bill of Materials)` setup is one without operations or instructions, only components. In this case, the production is solely managed using *Manufacturing Orders*." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/basic_setup/bill_configuration.rst:23 +msgid "To create a :abbr:`BoM (Bill of Materials)` from the :guilabel:`Manufacturing` module, go to :menuselection:`Products --> Bills of Materials`. Then, click :guilabel:`Create`. Next, specify the :guilabel:`Product`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/basic_setup/bill_configuration.rst:28 +msgid "A :abbr:`BoM (Bill of Materials)` can also be created directly from the product form, in which case the :guilabel:`Product` field is pre-filled." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/basic_setup/bill_configuration.rst:31 +msgid "For a standard :abbr:`BoM (Bill of Materials)`, set the :guilabel:`BoM Type` to :guilabel:`Manufacture this Product`. Then, click :guilabel:`Add a Line` to specify the various components that make up the production of the final product and their respective quantities. New components can be created quickly through the :abbr:`BoM (Bill of Materials)`, or can be created beforehand in :menuselection:`Manufacturing --> Products --> Products --> Create`. Finally, click :guilabel:`Save` to finish creating the :abbr:`BoM (Bill of Materials)`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/basic_setup/bill_configuration.rst:-1 +msgid "Set up a Bill of Materials." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/basic_setup/bill_configuration.rst:43 +msgid "Specify a bill of materials (BoM) for a product variant" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/basic_setup/bill_configuration.rst:45 +msgid ":abbr:`BoMs (Bills of Materials)` can also be assigned to specific *Product Variants*, with two setup options available to choose from." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/basic_setup/bill_configuration.rst:49 +msgid "In order to assign :abbr:`BoMs (Bills of Materials)` to product variants, the product's variant attributes must already be configured on the product form." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/basic_setup/bill_configuration.rst:52 +msgid "The first method is to create one :abbr:`BoM (Bill of Materials)` per variant by creating a new :abbr:`BoM (Bill of Materials)` and specifying the :guilabel:`Product Variant`. The second method is to create one master :abbr:`BoM (Bill of Materials)` that contains all of the components, and specify which variant each component applies to using the :guilabel:`Apply on Variants` column." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/basic_setup/bill_configuration.rst:-1 +msgid "Product Variants in the Bill of Materials." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/basic_setup/bill_configuration.rst:62 +msgid "Set up operations" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/basic_setup/bill_configuration.rst:64 +msgid "Add an :guilabel:`Operation` to a :abbr:`BoM (Bill of Materials)` to specify instructions for production and register time spent on an operation. To use this feature, first enable the :guilabel:`Work Orders` feature in :menuselection:`Manufacturing --> Configuration --> Settings --> Operations`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/basic_setup/bill_configuration.rst:69 +msgid "Then, when creating a new :abbr:`BoM (Bill of Materials)`, click on the :guilabel:`Operations` tab and click :guilabel:`Add a line` to add a new operation. In the :guilabel:`Create Operations` box, give the operation a name, specify the :guilabel:`Work Center` and duration settings. Like components, Odoo gives the option to specify a product variant in the :guilabel:`Apply on Variants` field so the operation only applies to that variant. Finally, click :guilabel:`Save & Close`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/basic_setup/bill_configuration.rst:76 +msgid "Each operation is unique, as it is always exclusively linked to one :abbr:`BoM (Bill of Materials)`. Operations can be reused when configuring a new :abbr:`BoM (Bill of Materials)`, with the :guilabel:`Copy Existing Operations` feature." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/basic_setup/bill_configuration.rst:-1 +msgid "Copy Existing Operations feature." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/basic_setup/bill_configuration.rst:85 +msgid "Add by-products to a bill of materials (BoM)" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/basic_setup/bill_configuration.rst:87 +msgid "A *By-Product* is a residual product that is created during production in addition to the main product of a :abbr:`BoM (Bill of Materials)`. Unlike the primary product, there can be more than one by-product on a :abbr:`BoM (Bill of Materials)`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/basic_setup/bill_configuration.rst:91 +msgid "To add by-products to a :abbr:`BoM (Bill of Materials)`, first enable the :guilabel:`By-Products` feature in :menuselection:`Manufacturing --> Configuration --> Settings --> Operations`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/basic_setup/bill_configuration.rst:94 +msgid "Once the feature is enabled, you can add by-products to a :abbr:`BoM (Bill of Materials)` by clicking on the :guilabel:`Operations` tab and clicking :guilabel:`Add a line`. Then, name the by-product and indicate the :guilabel:`Quantity` and the :guilabel:`Unit of Measure`. If the :abbr:`BoM (Bill of Materials)` has configured operations, specify exactly which operation the by-product is produced from in the :guilabel:`Produced in Operation` field. Finally, click :guilabel:`Save`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/basic_setup/configure_manufacturing_product.rst:3 +msgid "Manufacturing product configuration" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/basic_setup/configure_manufacturing_product.rst:8 +msgid "In order to manufacture a product in Odoo *Manufacturing*, the product must be properly configured. Doing so consists of enabling the *Manufacturing* route and configuring a bill of materials (BoM) for the product. Once these steps are completed, the product is selectable when creating a new manufacturing order." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/basic_setup/configure_manufacturing_product.rst:14 +msgid "Activate the Manufacture route" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/basic_setup/configure_manufacturing_product.rst:16 +msgid "The Manufacture route is activated for each product on its own product page. To do so, begin by navigating to :menuselection:`Manufacturing --> Products --> Products`. Then, select an existing product, or create a new one by clicking :guilabel:`New`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/basic_setup/configure_manufacturing_product.rst:20 +msgid "On the product page, select the :guilabel:`Inventory` tab, then enable the :guilabel:`Manufacture` checkbox in the :guilabel:`Routes` section. This tells Odoo the product can be manufactured." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/basic_setup/configure_manufacturing_product.rst:-1 +msgid "The Manufacturing route on the Inventory tab of a product page." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/basic_setup/configure_manufacturing_product.rst:28 +msgid "Configure a bill of materials (BoM)" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/basic_setup/configure_manufacturing_product.rst:30 +msgid "Next, a |BOM| must be configured for the product so Odoo knows how it is manufactured. A |BOM| is a list of the components and operations required to manufacture a product." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/basic_setup/configure_manufacturing_product.rst:33 +msgid "To create a |BOM| for a specific product, navigate to :menuselection:`Manufacturing --> Products --> Products`, then select the product. On the product page, click the :guilabel:`Bill of Materials` smart button at the top of the page, then select :guilabel:`New` to configure a new |BOM|." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/basic_setup/configure_manufacturing_product.rst:-1 +msgid "The Bill of Materials smart button on a product page." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/basic_setup/configure_manufacturing_product.rst:41 +msgid "On the |BOM|, the :guilabel:`Product` field auto-populates with the product. In the :guilabel:`Quantity` field, specify the number of units that the BoM produces." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/basic_setup/configure_manufacturing_product.rst:44 +msgid "Add a component to the |BOM| by selecting the :guilabel:`Components` tab and clicking :guilabel:`Add a line`. Select a component from the :guilabel:`Component` drop-down menu, then enter the quantity in the :guilabel:`Quantity` field. Continue adding components on new lines until all components have been added." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/basic_setup/configure_manufacturing_product.rst:-1 +msgid "The Components tab on a bill of materials." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/basic_setup/configure_manufacturing_product.rst:53 +msgid "Next, select the :guilabel:`Operations` tab. Click :guilabel:`Add a line` and a :guilabel:`Create Operations` pop-up window appears. In the :guilabel:`Operation` field, specify the name of the operation being added (e.g. Assemble, Cut, etc.). Select the work center where the operation will be carried out from the :guilabel:`Work Center` drop-down menu. Finally, click :guilabel:`Save & Close` to finish adding operations, or :guilabel:`Save & New` to add more." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/basic_setup/configure_manufacturing_product.rst:60 +msgid "The :guilabel:`Operations` tab only appears if the :guilabel:`Work Orders` setting is enabled. To do so, navigate to :menuselection:`Manufacturing --> Configuration --> Settings`, then enable the :guilabel:`Work Orders` checkbox." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/basic_setup/configure_manufacturing_product.rst:-1 +msgid "The Operations tab on a bill of materials." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/basic_setup/configure_manufacturing_product.rst:70 +msgid "The section above provides instructions for creating a basic |BOM| that allows a product to be manufactured in Odoo. However, it is by no means an exhaustive summary of all the options available when configuring a |BOM|. For more information about bills of materials, see the documentation on how to :ref:`create a bill of materials `." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/basic_setup/one_step_manufacturing.rst:3 +msgid "One-step manufacturing" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/basic_setup/one_step_manufacturing.rst:9 +msgid "Odoo *Manufacturing* allows users to manufacture products using one, two, or three steps. When using one-step manufacturing, Odoo creates a manufacturing order (MO), but does not generate transfers for the movement of components out of inventory or finished products into stock. Inventory counts still update based on the number of components used and products manufactured, but the act of transferring them to and from inventory is not tracked." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/basic_setup/one_step_manufacturing.rst:16 +#: ../../content/applications/inventory_and_mrp/manufacturing/basic_setup/three_step_manufacturing.rst:15 +#: ../../content/applications/inventory_and_mrp/manufacturing/basic_setup/two_step_manufacturing.rst:16 +msgid "The number of steps used in manufacturing is set at the warehouse level, allowing for each warehouse to use a different number of steps. To change the number of steps used for a specific warehouse, begin by navigating to :menuselection:`Inventory --> Configuration --> Warehouses`, and then select a warehouse from the :guilabel:`Warehouses` screen." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/basic_setup/one_step_manufacturing.rst:21 +#: ../../content/applications/inventory_and_mrp/manufacturing/basic_setup/three_step_manufacturing.rst:20 +#: ../../content/applications/inventory_and_mrp/manufacturing/basic_setup/two_step_manufacturing.rst:21 +msgid "On the :guilabel:`Warehouse Configuration` tab, find the :guilabel:`Manufacture` radio input field, and select one of the three options: :guilabel:`Manufacture (1 step)`, :guilabel:`Pick components and then manufacture (2 steps)`, or :guilabel:`Pick components, manufacture and then store products (3 steps)`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/basic_setup/one_step_manufacturing.rst:0 +#: ../../content/applications/inventory_and_mrp/manufacturing/basic_setup/three_step_manufacturing.rst:0 +#: ../../content/applications/inventory_and_mrp/manufacturing/basic_setup/two_step_manufacturing.rst:0 +msgid "The Manufacture radio input field on a warehouse configuration page." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/basic_setup/one_step_manufacturing.rst:31 +#: ../../content/applications/inventory_and_mrp/manufacturing/basic_setup/three_step_manufacturing.rst:30 +#: ../../content/applications/inventory_and_mrp/manufacturing/basic_setup/two_step_manufacturing.rst:31 +msgid "Products must be properly configured before they can be manufactured in Odoo. For details on how to do so, see the documentation on how to :ref:`configure a product for manufacturing `." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/basic_setup/one_step_manufacturing.rst:36 +#: ../../content/applications/inventory_and_mrp/manufacturing/basic_setup/three_step_manufacturing.rst:35 +#: ../../content/applications/inventory_and_mrp/manufacturing/basic_setup/two_step_manufacturing.rst:36 +msgid "Create manufacturing order" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/basic_setup/one_step_manufacturing.rst:38 +#: ../../content/applications/inventory_and_mrp/manufacturing/basic_setup/three_step_manufacturing.rst:37 +#: ../../content/applications/inventory_and_mrp/manufacturing/basic_setup/two_step_manufacturing.rst:38 +msgid "To manufacture a product in Odoo *Manufacturing*, begin by navigating to :menuselection:`Manufacturing --> Operations --> Manufacturing Orders`, and then click :guilabel:`New` to create a new |MO|." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/basic_setup/one_step_manufacturing.rst:42 +msgid "On the new |MO|, select the product to be produced from the :guilabel:`Product` drop-down menu. The :guilabel:`Bill of Material` field auto-populates with the associated bill of materials (BoM)." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/basic_setup/one_step_manufacturing.rst:45 +#: ../../content/applications/inventory_and_mrp/manufacturing/basic_setup/three_step_manufacturing.rst:44 +#: ../../content/applications/inventory_and_mrp/manufacturing/basic_setup/two_step_manufacturing.rst:45 +msgid "If a product has more than one |BOM| configured for it, the specific |BOM| can be selected in the :guilabel:`Bill of Material` field, and the :guilabel:`Product` field auto-populates with the associated product." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/basic_setup/one_step_manufacturing.rst:49 +#: ../../content/applications/inventory_and_mrp/manufacturing/basic_setup/three_step_manufacturing.rst:48 +#: ../../content/applications/inventory_and_mrp/manufacturing/basic_setup/two_step_manufacturing.rst:49 +msgid "After a |BOM| has been selected, the :guilabel:`Components` and :guilabel:`Work Orders` tabs auto-populate with the components and operations specified on the |BOM|. If additional components or operations are required for the |MO| being configured, add them to the :guilabel:`Components` and :guilabel:`Work Orders` tabs by clicking :guilabel:`Add a line`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/basic_setup/one_step_manufacturing.rst:54 +#: ../../content/applications/inventory_and_mrp/manufacturing/basic_setup/three_step_manufacturing.rst:53 +#: ../../content/applications/inventory_and_mrp/manufacturing/basic_setup/two_step_manufacturing.rst:54 +msgid "Finally, click :guilabel:`Confirm` to confirm the |MO|." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/basic_setup/one_step_manufacturing.rst:57 +#: ../../content/applications/inventory_and_mrp/manufacturing/basic_setup/three_step_manufacturing.rst:80 +#: ../../content/applications/inventory_and_mrp/manufacturing/basic_setup/two_step_manufacturing.rst:77 +msgid "Process manufacturing order" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/basic_setup/one_step_manufacturing.rst:59 +#: ../../content/applications/inventory_and_mrp/manufacturing/basic_setup/three_step_manufacturing.rst:82 +#: ../../content/applications/inventory_and_mrp/manufacturing/basic_setup/two_step_manufacturing.rst:79 +msgid "An |MO| is processed by completing all of the work orders listed under its :guilabel:`Work Orders` tab. This can be done on the |MO| itself, or from the work order tablet view." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/basic_setup/one_step_manufacturing.rst:63 +#: ../../content/applications/inventory_and_mrp/manufacturing/basic_setup/three_step_manufacturing.rst:86 +#: ../../content/applications/inventory_and_mrp/manufacturing/basic_setup/two_step_manufacturing.rst:83 +msgid "Basic workflow" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/basic_setup/one_step_manufacturing.rst:65 +#: ../../content/applications/inventory_and_mrp/manufacturing/basic_setup/two_step_manufacturing.rst:85 +msgid "To complete work orders from the |MO| itself, begin by navigating to :menuselection:`Manufacturing --> Operations --> Manufacturing Orders`, and then select an |MO|." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/basic_setup/one_step_manufacturing.rst:68 +#: ../../content/applications/inventory_and_mrp/manufacturing/basic_setup/three_step_manufacturing.rst:91 +msgid "On the |MO| page, select the :guilabel:`Work Orders` tab. Once work begins on the first work order that needs to be completed, click the :guilabel:`Start` button for that work order. Odoo *Manufacturing* then starts a timer that keeps track of how long the work order takes to complete." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/basic_setup/one_step_manufacturing.rst:-1 +msgid "The Start button for an operation on a manufacturing order." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/basic_setup/one_step_manufacturing.rst:76 +#: ../../content/applications/inventory_and_mrp/manufacturing/basic_setup/three_step_manufacturing.rst:99 +#: ../../content/applications/inventory_and_mrp/manufacturing/basic_setup/two_step_manufacturing.rst:96 +msgid "When the work order is completed, click the :guilabel:`Done` button for that work order. Repeat the same process for each work order listed on the :guilabel:`Work Orders` tab." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/basic_setup/one_step_manufacturing.rst:-1 +msgid "The Done button for an operation on a manufacturing order." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/basic_setup/one_step_manufacturing.rst:83 +#: ../../content/applications/inventory_and_mrp/manufacturing/basic_setup/three_step_manufacturing.rst:106 +#: ../../content/applications/inventory_and_mrp/manufacturing/basic_setup/two_step_manufacturing.rst:103 +msgid "After completing all of the work orders, click :guilabel:`Produce All` at the top of the screen to mark the |MO| as :guilabel:`Done`, and register the manufactured product(s) into inventory." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/basic_setup/one_step_manufacturing.rst:87 +#: ../../content/applications/inventory_and_mrp/manufacturing/basic_setup/three_step_manufacturing.rst:110 +#: ../../content/applications/inventory_and_mrp/manufacturing/basic_setup/two_step_manufacturing.rst:107 +msgid "Shop Floor workflow" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/basic_setup/one_step_manufacturing.rst:89 +#: ../../content/applications/inventory_and_mrp/manufacturing/basic_setup/three_step_manufacturing.rst:112 +#: ../../content/applications/inventory_and_mrp/manufacturing/basic_setup/two_step_manufacturing.rst:109 +msgid "To complete the work orders for an |MO| using the *Shop Floor* module, begin by navigating to :menuselection:`Manufacturing --> Operations --> Manufacturing Orders`, and then select an |MO|." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/basic_setup/one_step_manufacturing.rst:92 +#: ../../content/applications/inventory_and_mrp/manufacturing/basic_setup/three_step_manufacturing.rst:115 +#: ../../content/applications/inventory_and_mrp/manufacturing/basic_setup/two_step_manufacturing.rst:112 +msgid "On the |MO|, click on the :guilabel:`Work Orders` tab, and then select the :guilabel:`↗️ (square with arrow coming out of it)` button on the line of the first work order to be processed. Doing so opens a :guilabel:`Work Orders` pop-up window, with details and processing options for the work order." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/basic_setup/one_step_manufacturing.rst:97 +#: ../../content/applications/inventory_and_mrp/manufacturing/basic_setup/three_step_manufacturing.rst:120 +#: ../../content/applications/inventory_and_mrp/manufacturing/basic_setup/two_step_manufacturing.rst:117 +msgid "On the pop-up window, select the :guilabel:`Open Shop Floor` button at the top-left of the window to open the *Shop Floor* module." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/basic_setup/one_step_manufacturing.rst:-1 +#: ../../content/applications/inventory_and_mrp/manufacturing/basic_setup/three_step_manufacturing.rst:-1 +#: ../../content/applications/inventory_and_mrp/manufacturing/basic_setup/two_step_manufacturing.rst:-1 +msgid "The Open Shop Floor button for a work order on a manufacturing order." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/basic_setup/one_step_manufacturing.rst:104 +#: ../../content/applications/inventory_and_mrp/manufacturing/basic_setup/three_step_manufacturing.rst:127 +#: ../../content/applications/inventory_and_mrp/manufacturing/basic_setup/two_step_manufacturing.rst:124 +msgid "When accessed directly from a specific work order within an |MO|, *Shop Floor* defaults to the page for the work center where the work order is configured to be carried out. The page shows a card for the work order that displays the |MO| number, the product and number of units to be produced, and the steps required to complete the work order." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/basic_setup/one_step_manufacturing.rst:-1 +#: ../../content/applications/inventory_and_mrp/manufacturing/basic_setup/three_step_manufacturing.rst:-1 +#: ../../content/applications/inventory_and_mrp/manufacturing/basic_setup/two_step_manufacturing.rst:-1 +msgid "A work order card on a work center page in the Shop Floor module." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/basic_setup/one_step_manufacturing.rst:113 +#: ../../content/applications/inventory_and_mrp/manufacturing/basic_setup/two_step_manufacturing.rst:133 +msgid "A work order is processed by completing each step listed on its card. This can be done by clicking on a step and following the instructions listed on the pop-up window that appears. Once the step is completed, click :guilabel:`Next` to move on to the next step, if any are required." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/basic_setup/one_step_manufacturing.rst:117 +#: ../../content/applications/inventory_and_mrp/manufacturing/basic_setup/three_step_manufacturing.rst:140 +#: ../../content/applications/inventory_and_mrp/manufacturing/basic_setup/two_step_manufacturing.rst:137 +msgid "Alternatively, work order steps can be completed by clicking the checkbox that appears on the right side of the step's line on the work order card. When using this method, the step is automatically marked as completed, without a pop-up window appearing." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/basic_setup/one_step_manufacturing.rst:121 +#: ../../content/applications/inventory_and_mrp/manufacturing/basic_setup/three_step_manufacturing.rst:144 +#: ../../content/applications/inventory_and_mrp/manufacturing/basic_setup/two_step_manufacturing.rst:141 +msgid "The final step on a work order card is titled *Register Production*. This step is used to register the number of product units that were produced. If the number produced is equal to the number that the |MO| was created for, click the :guilabel:`# Units` button on the right side of the line to automatically register that number as the quantity produced." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/basic_setup/one_step_manufacturing.rst:126 +#: ../../content/applications/inventory_and_mrp/manufacturing/basic_setup/three_step_manufacturing.rst:149 +#: ../../content/applications/inventory_and_mrp/manufacturing/basic_setup/two_step_manufacturing.rst:146 +msgid "If a different number must be entered, click the :guilabel:`Register Production` step to open a pop-up window. Enter the number of units produced in the :guilabel:`Units` field, and then click :guilabel:`Validate` to register that number." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/basic_setup/one_step_manufacturing.rst:131 +#: ../../content/applications/inventory_and_mrp/manufacturing/basic_setup/three_step_manufacturing.rst:154 +#: ../../content/applications/inventory_and_mrp/manufacturing/basic_setup/two_step_manufacturing.rst:151 +msgid "The *Register Production* step appears on every work order card. It must be completed for the first work order that is processed. After doing so, the step appears as already completed for each remaining work order in the |MO|." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/basic_setup/one_step_manufacturing.rst:135 +#: ../../content/applications/inventory_and_mrp/manufacturing/basic_setup/three_step_manufacturing.rst:158 +#: ../../content/applications/inventory_and_mrp/manufacturing/basic_setup/two_step_manufacturing.rst:155 +msgid "After completing all of the steps for a work order, a button appears on the footer of the work order card. If any other work orders must be completed before the |MO| can be closed, the button is titled :guilabel:`Mark as Done`. If there are no additional work orders to complete, the button is titled :guilabel:`Close Production`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/basic_setup/one_step_manufacturing.rst:140 +#: ../../content/applications/inventory_and_mrp/manufacturing/basic_setup/three_step_manufacturing.rst:163 +#: ../../content/applications/inventory_and_mrp/manufacturing/basic_setup/two_step_manufacturing.rst:160 +msgid "Clicking :guilabel:`Mark as Done` causes the work order card to fade away. Once it disappears completely, the work order's status is marked as *Finished* on the |MO|, and the next work order appears in the *Shop Floor* module, on the page of the work center where it is configured to be carried out. Any additional work orders can be processed using the instructions detailed in this section." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/basic_setup/one_step_manufacturing.rst:146 +#: ../../content/applications/inventory_and_mrp/manufacturing/basic_setup/three_step_manufacturing.rst:169 +#: ../../content/applications/inventory_and_mrp/manufacturing/basic_setup/two_step_manufacturing.rst:166 +msgid "Clicking :guilabel:`Close Production` causes the work order card to fade away. Once it disappears, the |MO| is marked as *Done*, and the units of the product that were produced are entered into inventory." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/basic_setup/one_step_manufacturing.rst:150 +#: ../../content/applications/inventory_and_mrp/manufacturing/basic_setup/three_step_manufacturing.rst:173 +#: ../../content/applications/inventory_and_mrp/manufacturing/basic_setup/two_step_manufacturing.rst:170 +msgid "After clicking :guilabel:`Mark as Done` or :guilabel:`Close Production`, each button is replaced by an :guilabel:`Undo` button. Click the :guilabel:`Undo` button before the work order card fades away to keep the work order open." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/basic_setup/one_step_manufacturing.rst:155 +#: ../../content/applications/inventory_and_mrp/manufacturing/basic_setup/three_step_manufacturing.rst:178 +#: ../../content/applications/inventory_and_mrp/manufacturing/basic_setup/two_step_manufacturing.rst:175 +msgid "This section details the basic workflow for processing an |MO| in the *Shop Floor* module. For a more in-depth explanation of the module and all of its features, please see the :ref:`Shop Floor overview ` documentation." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/basic_setup/three_step_manufacturing.rst:3 +msgid "Three-step manufacturing" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/basic_setup/three_step_manufacturing.rst:9 +msgid "Odoo *Manufacturing* allows users to manufacture products using one, two, or three steps. When using three-step manufacturing, Odoo creates a pick components transfer, a manufacturing order (MO), and a store finished products transfer, and updates inventory counts based on the number of components removed, and finished products created." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/basic_setup/three_step_manufacturing.rst:41 +#: ../../content/applications/inventory_and_mrp/manufacturing/basic_setup/two_step_manufacturing.rst:42 +msgid "On the new |MO|, select the product to be produced from the :guilabel:`Product` drop-down menu. The :guilabel:`Bill of Material` field auto-populates with the associated Bill of Materials (BoM)." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/basic_setup/three_step_manufacturing.rst:56 +#: ../../content/applications/inventory_and_mrp/manufacturing/basic_setup/two_step_manufacturing.rst:57 +msgid "Process pick components transfer" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/basic_setup/three_step_manufacturing.rst:58 +msgid "After confirming a three-step |MO|, a :guilabel:`Transfers` smart button appears at the top of the page. Click it to be taken to the :guilabel:`Transfers` page for the |MO|. The page lists two transfers: *WH/PC/XXXXX* (the pick components transfer), and *WH/SFP/XXXXX* (the store finished products transfer)." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/basic_setup/three_step_manufacturing.rst:63 +msgid "Select :guilabel:`WH/PC/XXXXX` to open the pick components transfer for the |MO|. This transfer is used to track the movement of components from the locations where they are stored to the location where they are used to manufacture the product." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/basic_setup/three_step_manufacturing.rst:67 +#: ../../content/applications/inventory_and_mrp/manufacturing/basic_setup/two_step_manufacturing.rst:64 +msgid "After transferring the components out of their storage location, click :guilabel:`Validate` at the top of the transfer, followed by :guilabel:`Apply` on the :guilabel:`Immediate Transfer?` pop-up window that appears. Doing so marks the transfer as :guilabel:`Done`, and updates inventory counts to reflect the quantity of components transferred." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/basic_setup/three_step_manufacturing.rst:72 +#: ../../content/applications/inventory_and_mrp/manufacturing/basic_setup/two_step_manufacturing.rst:69 +msgid "Finally, return to the |MO| by clicking the :guilabel:`WH/MO/XXXXX` breadcrumb at the top of the page." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/basic_setup/three_step_manufacturing.rst:-1 +#: ../../content/applications/inventory_and_mrp/manufacturing/basic_setup/two_step_manufacturing.rst:-1 +msgid "The manufacturing order bread crumb on a pick components transfer." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/basic_setup/three_step_manufacturing.rst:88 +msgid "To complete work orders from the |MO| itself, begin by navigating to :menuselection:`Manufacturing --> Operations --> Manufacturing Orders`, and then select a manufacturing order." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/basic_setup/three_step_manufacturing.rst:-1 +msgid "The Start button for a work order on a manufacturing order." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/basic_setup/three_step_manufacturing.rst:-1 +msgid "The Done button for an work order on a manufacturing order." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/basic_setup/three_step_manufacturing.rst:136 +msgid "A work order is processed by completing each step listed on its card. This can be done by clicking on a step, and following the instructions listed on the pop-up window that appears. Once the step is completed, click :guilabel:`Next` to move on to the next step, if any are required." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/basic_setup/three_step_manufacturing.rst:183 +msgid "Process finished product transfer" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/basic_setup/three_step_manufacturing.rst:185 +msgid "After completing the |MO|, return to the order's :guilabel:`Transfers` page by clicking the :guilabel:`Transfers` button at the top of the order. This time, select :guilabel:`WH/SFP/XXXXX` to open the store finished products transfer. This transfer is used to track the movement of finished products from the location where they were manufactured to the location where they are stored." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/basic_setup/three_step_manufacturing.rst:190 +msgid "After transferring the finished products to their storage location, click :guilabel:`Validate` at the top of the transfer, followed by :guilabel:`Apply` on the :guilabel:`Immediate Transfer?` pop-up window that appears. Doing so marks the transfer as :guilabel:`Done`, and updates inventory counts to reflect the quantity of finished products transferred." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/basic_setup/two_step_manufacturing.rst:3 +msgid "Two-step manufacturing" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/basic_setup/two_step_manufacturing.rst:9 +msgid "Odoo *Manufacturing* allows users to manufacture products using one, two, or three steps. When using two-step manufacturing, Odoo creates a manufacturing order (MO) and a pick components transfer, but does not generate a transfer for the movement of finished products into stock. Inventory counts still update based on the number of products manufactured, but the act of transferring them to and from inventory is not tracked." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/basic_setup/two_step_manufacturing.rst:59 +msgid "After confirming a two-step |MO|, a :guilabel:`Transfers` smart button appears at the top of the page. Click it to open the pick components transfer for the |MO|. This transfer is used to track the movement of components from the locations where they are stored to the location where they are used to manufacture the product." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/basic_setup/two_step_manufacturing.rst:88 +msgid "On the |MO| page, select the :guilabel:`Work Orders` tab. Once work begins on the first work order that needs to be completed, click the :guilabel:`Start` button for that operation. Odoo *Manufacturing* then starts a timer that keeps track of how long the work order takes to complete." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/basic_setup/two_step_manufacturing.rst:-1 +msgid "The Start button for an work order on a manufacturing order." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/basic_setup/two_step_manufacturing.rst:-1 +msgid "The Done button for a work order on a manufacturing order." +msgstr "" + #: ../../content/applications/inventory_and_mrp/manufacturing/shop_floor.rst:5 msgid "Shop Floor" msgstr "" @@ -14154,7 +15039,7 @@ msgid "To check the version number of an Odoo database, navigate to :menuselecti msgstr "" #: ../../content/applications/inventory_and_mrp/manufacturing/shop_floor/shop_floor_overview.rst:26 -msgid "To switch to a newer version of Odoo, see the documentation on :ref:`upgrading a database `." +msgid "To switch to a newer version of Odoo, see the documentation on :doc:`upgrading a database <../../../../administration/upgrade>`." msgstr "" #: ../../content/applications/inventory_and_mrp/manufacturing/shop_floor/shop_floor_overview.rst:30 @@ -14351,6 +15236,1588 @@ msgstr "" msgid "The operator panel of the Shop Floor module, showing three employees signed in." msgstr "" +#: ../../content/applications/inventory_and_mrp/manufacturing/shop_floor/shop_floor_tracking.rst:3 +msgid "Shop Floor time tracking" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/shop_floor/shop_floor_tracking.rst:8 +msgid "By signing in to the Odoo *Shop Floor* module as *operators*, employees are able to track the amount of time they spend working on each work order." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/shop_floor/shop_floor_tracking.rst:11 +msgid "Odoo tracks the time it takes to complete each work order, as well as the time each operator spends on each work order." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/shop_floor/shop_floor_tracking.rst:15 +msgid "Operator sign in" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/shop_floor/shop_floor_tracking.rst:17 +msgid "To sign in to the *Shop Floor* module as an operator, sign in to the Odoo database, and open the :menuselection:`Shop Floor` module. The employee profile that is signed in to the database is automatically signed in as an operator." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/shop_floor/shop_floor_tracking.rst:21 +msgid "All active operators are listed in the operator panel on the left side of the module. The panel can be opened or collapsed by clicking the :guilabel:`show/hide panel (white square with black column on left side)` button, located in the top-left corner of the module." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/shop_floor/shop_floor_tracking.rst:-1 +msgid "The operator panel in the Shop Floor module, with the show/hide panel button above it." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/shop_floor/shop_floor_tracking.rst:29 +msgid "To sign in to *Shop Floor* as a different employee, click the :guilabel:`+ Add Operator` button at the bottom of the panel. Doing so opens the :guilabel:`Select Employee` pop-up window, which lists every employee that is able to sign in to the module." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/shop_floor/shop_floor_tracking.rst:33 +msgid "Click on a specific employee to sign in using their profile. If no PIN code is required to sign in as that employee, the profile will be signed in automatically." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/shop_floor/shop_floor_tracking.rst:36 +msgid "If a PIN code is required, a :guilabel:`Password?` pop-up window appears, showing a number pad, from which the code can be entered. Enter the code using the number pad, and click :guilabel:`Confirm` to sign in to the *Shop Floor* module." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/shop_floor/shop_floor_tracking.rst:-1 +msgid "The \"Password?\" pop-up window, which is used to enter an operator PIN code." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/shop_floor/shop_floor_tracking.rst:45 +msgid "A PIN code can be set for each employee, which must be entered each time they sign in to the *Shop Floor* module, check in or out in the *Kiosk Mode* of the *Attendances* application, or sign in as a cashier in the *Point of Sale* application." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/shop_floor/shop_floor_tracking.rst:49 +msgid "To set an employee PIN, navigate to the :menuselection:`Employees` app, and select a specific employee. At the bottom of the employee's form, click on the :guilabel:`HR Settings` tab, and enter a numerical code in the :guilabel:`PIN Code` field." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/shop_floor/shop_floor_tracking.rst:53 +msgid "Once an employee is signed in to the module, their name appears in the operator panel, along with every other employee that has signed in. While the panel can list multiple employees, only one employee can be active at any given time, on a single instance of the *Shop Floor* module." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/shop_floor/shop_floor_tracking.rst:57 +msgid "Click on an employee's name to make their profile active. The active employee appears highlighted in blue, while employees that are signed in, but not active, have their names faded out." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/shop_floor/shop_floor_tracking.rst:60 +msgid "To sign out a specific employee from the module, click the :guilabel:`X (remove)` button next to their name, in the operator panel." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/shop_floor/shop_floor_tracking.rst:64 +msgid "Track work order duration" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/shop_floor/shop_floor_tracking.rst:66 +msgid "To track time spent working on a work order, begin by selecting the employee working on it from the operator panel." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/shop_floor/shop_floor_tracking.rst:69 +msgid "Next, navigate to the page for the work center where the work order is scheduled to be carried out. This can be done by selecting the work center from the top navigation in the *Shop Floor* module, or by clicking the name of the work center on the card for the manufacturing order (MO) that the work order is a part of." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/shop_floor/shop_floor_tracking.rst:74 +msgid "On the page for the work center, find the card for the work order. Once work begins, click the header of the work order card to start timing the duration it takes to complete. This duration is displayed by a timer on the header of the work order card, which tracks the collective time spent working on the work order, by all employees." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/shop_floor/shop_floor_tracking.rst:-1 +msgid "A work order card with an active timer." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/shop_floor/shop_floor_tracking.rst:83 +msgid "In addition, the reference number of the work order appears in the operator panel, under the name of the employee working on it, along with a second timer, which tracks the amount of time the employee has spent on the work order individually. This timer only reflects work done during the current session, even if the employee has previously worked on the work order." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/shop_floor/shop_floor_tracking.rst:88 +msgid "Employees are able to work on multiple work orders simultaneously, and track their time for each. The reference number for each work order being worked on appears below the employee's name, along with a timer." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/shop_floor/shop_floor_tracking.rst:-1 +msgid "An employee card in the operator panel, showing two work order timers." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/shop_floor/shop_floor_tracking.rst:96 +msgid "To pause the timer on the work order card, and remove the work order from below the employee's name on the operator panel, click the header a second time." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/shop_floor/shop_floor_tracking.rst:99 +msgid "Once the work order is completed, click the :guilabel:`Mark as Done` button at the bottom of the work order card, which causes the card to fade away. If the timer is still active, it stops once the card disappears completely." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/shop_floor/shop_floor_tracking.rst:104 +msgid "View work order duration" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/shop_floor/shop_floor_tracking.rst:106 +msgid "To view the duration of a work order, navigate to :menuselection:`Manufacturing app --> Operations --> Manufacturing Orders`, and select an |MO|." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/shop_floor/shop_floor_tracking.rst:109 +msgid "To view and select |MOs| that have been completed and marked as *Done*, remove the :guilabel:`To Do` filter from the :guilabel:`Search...` bar, by clicking on the :guilabel:`X (close)` button on the right side of the filter." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/shop_floor/shop_floor_tracking.rst:113 +msgid "On the page for the |MO|, click on the :guilabel:`Work Orders` tab to see a list of all work orders included in the |MO|. The time it took to complete each work order is displayed in the :guilabel:`Real Duration` column of the tab." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/shop_floor/shop_floor_tracking.rst:117 +msgid "The *Real Duration* represents the total time spent working on the work order by all workers who worked on it. It includes time tracked in the *Shop Floor* module, as well as time tracked on the :guilabel:`Work Orders` tab of the |MO| itself." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/workflows.rst:5 +msgid "Workflows" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/manufacturing_backorders.rst:3 +msgid "Manufacturing backorders" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/manufacturing_backorders.rst:7 +msgid "In some cases, the full quantity of a manufacturing order cannot be produced immediately. When this happens, Odoo *Manufacturing* allows for the manufacturing of partial quantities of the order and creates a *backorder* for the remaining amount." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/manufacturing_backorders.rst:11 +msgid "In the *Manufacturing* app, creating a backorder splits the original manufacturing order into two orders. The reference tag for each order is the tag used for the original order, followed by a hyphen and then an additional number to indicate that it's a backorder." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/manufacturing_backorders.rst:16 +msgid "A company creates a manufacturing order with the reference tag *WH/MO/00175*, for 10 units of *Product X*. After starting work on the manufacturing order, the employee working the production line realizes there are only enough components in stock to produce five units of the product." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/manufacturing_backorders.rst:20 +msgid "Instead of waiting for additional stock of the components, they manufacture five units and create a backorder for the remaining five. This splits the manufacturing order into two separate orders: *WH/MO/00175-001* and *WH/MO/00175-002*." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/manufacturing_backorders.rst:24 +msgid "Order *001* contains the five units that have been manufactured, and is immediately marked as :guilabel:`Done`. Order *002* contains the five units that still need to be manufactured and is marked as :guilabel:`In Progress`. Once the remaining components are available, the employee returns to order *002* and manufactures the remaining units before closing the order." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/manufacturing_backorders.rst:30 +msgid "Create a manufacturing backorder" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/manufacturing_backorders.rst:32 +msgid "To create a backorder for part of a manufacturing order, begin by navigating to :menuselection:`Manufacturing --> Operations --> Manufacturing Orders`. Select a manufacturing order with a quantity of two or more or create one by clicking :guilabel:`Create`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/manufacturing_backorders.rst:36 +msgid "If a new manufacturing order is created, select a product from the :guilabel:`Product` drop-down menu and enter a quantity of two or more in the :guilabel:`Quantity` field, then click :guilabel:`Confirm` to confirm the order." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/manufacturing_backorders.rst:40 +msgid "After manufacturing the quantity that is being produced immediately, enter that number in the :guilabel:`Quantity` field at the top of the manufacturing order." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/manufacturing_backorders.rst:-1 +msgid "The quantity field on a manufacturing order." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/manufacturing_backorders.rst:47 +msgid "Next, click :guilabel:`Validate`, and a :guilabel:`You produced less than initial demand` pop-up window appears, from which a backorder can be created. Click :guilabel:`Create Backorder` to split the manufacturing order into two separate orders, with the reference tags *WH/MO/XXXXX-001* and *WH/MO/XXXXX-002*." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/manufacturing_backorders.rst:-1 +msgid "The Create Backorder button on the \"You produced less than initial demand\" pop-up window." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/manufacturing_backorders.rst:56 +msgid "Order *001* contains the items that have been manufactured, and is closed immediately. Order *002* is the backorder that contains the items that have yet to be manufactured, and remains open, to be completed at a later date." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/manufacturing_backorders.rst:60 +msgid "Once the remaining units can be manufactured, navigate to :menuselection:`Manufacturing --> Operations --> Manufacturing Orders`, and then select the backorder manufacturing order. If all of the remaining units are manufactured immediately, simply click :guilabel:`Validate` to close the order." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/manufacturing_backorders.rst:65 +msgid "If only some of the remaining units are manufactured immediately, create another backorder for the remainder by following the steps detailed in this section." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/manufacturing_backorders.rst:69 +msgid "Create a backorder in Shop Floor" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/manufacturing_backorders.rst:71 +msgid "Backorders for manufacturing orders can also be created from the *Shop Floor* module." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/manufacturing_backorders.rst:74 +msgid "In order to use the *Shop Floor* module, the *Work Orders* setting must be enabled. To do so, navigate to :menuselection:`Manufacturing --> Configuration --> Settings`, enable the :guilabel:`Work Orders` checkbox, and then click :guilabel:`Save`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/manufacturing_backorders.rst:78 +msgid "To create a backorder from the *Shop Floor* module, begin by navigating to :menuselection:`Manufacturing --> Operations --> Manufacturing Orders`. Select an |MO| for multiple units of a product, for which a backorder needs to be created." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/manufacturing_backorders.rst:82 +#: ../../content/applications/inventory_and_mrp/quality/quality_check_types/pass_fail_check.rst:121 +#: ../../content/applications/inventory_and_mrp/quality/quality_check_types/picture_check.rst:133 +#: ../../content/applications/inventory_and_mrp/quality/quality_management/quality_checks.rst:129 +msgid "On the |MO|, select the :guilabel:`Work Orders` tab, and then click the :guilabel:`Open Work Order (external link icon)` button on the line of the work order to be processed. On the resulting :guilabel:`Work Orders` pop-up window, click the :guilabel:`Open Shop Floor` button to open the *Shop Floor* module." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/manufacturing_backorders.rst:87 +#: ../../content/applications/inventory_and_mrp/quality/quality_check_types/instructions_check.rst:80 +#: ../../content/applications/inventory_and_mrp/quality/quality_check_types/pass_fail_check.rst:126 +#: ../../content/applications/inventory_and_mrp/quality/quality_management/quality_checks.rst:138 +msgid "When accessed from a specific work order, the *Shop Floor* module opens to the page for the work center where the order is configured to be processed, and isolates the work order's card so that no other cards are shown." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/manufacturing_backorders.rst:91 +msgid "Complete the steps on the work order's card until the :guilabel:`Register Production` step is reached, and then click on it to open the :guilabel:`Register Production` pop-up window." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/manufacturing_backorders.rst:95 +msgid "Do **not** click the :guilabel:`# Units` button on the right side of the step. Doing so automatically registers the full amount of units as having been produced." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/manufacturing_backorders.rst:98 +msgid "On the :guilabel:`Register Production` pop-up window, enter the number of units produced in the :guilabel:`Quantity` field. Make sure the number entered is *less* than the number of units listed to the right of the field. Then, click :guilabel:`Validate`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/manufacturing_backorders.rst:-1 +msgid "The Register Production pop-up window in the Shop Floor module." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/manufacturing_backorders.rst:106 +msgid "The pop-up window disappears and the :guilabel:`# Units` button on the work order's card updates to reflect the number of units produced, as a fraction of the number of units for which the |MO| was originally created." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/manufacturing_backorders.rst:110 +msgid "Next, click the :guilabel:`Mark as Done` button at the bottom-right of the work order's card. The work order card begins to fade away. Once it disappears completely, a new work order card appears, titled with the original |MO|'s reference number with a `-002` tag added to the end of it." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/manufacturing_backorders.rst:114 +msgid "This new reference number represents the backorder |MO|. The original |MO|'s reference number now appears with a `-001` tag added to the end of it to distinguish it from the backorder |MO|." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/manufacturing_backorders.rst:117 +msgid "If the original |MO| has no remaining work orders, it can be closed by selecting the :guilabel:`All` filter in the top navigation of the *Shop Floor* module, and then clicking :guilabel:`Close Production` at the bottom of the |MO|'s card." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/manufacturing_backorders.rst:121 +msgid "If the original |MO| has remaining work orders that must be completed before it can be closed, cards for these work orders appear on the *Shop Floor* pages for the work centers where they are configured to be carried out. They can be processed as normal, and additional backorders can be created from their work order cards using the instructions detailed in this section." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/manufacturing_backorders.rst:126 +msgid "Once the current work order for the backorder |MO| is ready to be processed, this can also be completed as normal, and an additional backorder can be created from its work order card by following the instructions detailed in this section." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/manufacturing_backorders.rst:130 +msgid "After the final work order for the backorder |MO| has been completed, the |MO| can be closed by clicking the :guilabel:`Close Production` button at the bottom of the work order's card." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/scrap_manufacturing.rst:3 +msgid "Scrap during manufacturing" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/scrap_manufacturing.rst:7 +msgid "During the manufacturing process, the need to scrap manufacturing components or finished products may arise. This can be necessary if a component or product is damaged, or unusable for any other reason." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/scrap_manufacturing.rst:11 +msgid "By default, scrapping a component or finished product removes it from physical inventory and places it in a virtual location titled *Virtual Locations/Scrap*. A virtual location is **not** a physical space, but rather a designation in Odoo that is used to track items that are no longer in physical inventory." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/scrap_manufacturing.rst:17 +msgid "For more information, see the documentation about the different types of :ref:`locations `." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/scrap_manufacturing.rst:20 +msgid "Components can be scrapped from both the *Manufacturing* app and the *Shop Floor* module, before the associated manufacturing order (MO) is closed. Finished products can only be scrapped from the *Manufacturing* app, and only after closing the associated |MO|." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/scrap_manufacturing.rst:29 +msgid "To view the total quantity of each item scrapped, navigate to :menuselection:`Inventory --> Configuration --> Locations`, then remove the :guilabel:`Internal` filter from the :guilabel:`Search...` bar to display all virtual locations. From the list, select the :guilabel:`Virtual Locations/Scrap` location." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/scrap_manufacturing.rst:37 +#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/scrap_manufacturing.rst:75 +msgid "Scrap pop-up window" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/scrap_manufacturing.rst:39 +msgid "Scrapping components and finished products is done through the :guilabel:`Scrap` pop-up window. The pop-up window can be accessed from an |MO| in the backend, or the *Shop Floor* module." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/scrap_manufacturing.rst:43 +msgid "Scrap component from Manufacturing" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/scrap_manufacturing.rst:45 +msgid "To scrap a component from an |MO|, begin by navigating to :menuselection:`Manufacturing --> Operations --> Manufacturing Orders`, and then select an |MO|. At the top of the |MO|, click the :guilabel:`Scrap` button to open the :guilabel:`Scrap` pop-up window." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/scrap_manufacturing.rst:50 +msgid "Scrap finished product from Manufacturing" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/scrap_manufacturing.rst:52 +msgid "To scrap a finished product from an |MO|, begin by navigating to :menuselection:`Manufacturing --> Operations --> Manufacturing Orders`. Select an open |MO|, and then click the :guilabel:`Produce All` button to close it." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/scrap_manufacturing.rst:56 +msgid "To select an |MO| that has already been closed, navigate to :menuselection:`Manufacturing --> Operations --> Manufacturing Orders`, remove the :guilabel:`To Do` filter from the :guilabel:`Search...` bar, and then select the desired |MO|." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/scrap_manufacturing.rst:60 +msgid "Once closed, click the :guilabel:`Scrap` button at the top of the |MO| to open the :guilabel:`Scrap` pop-up window." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/scrap_manufacturing.rst:64 +msgid "Scrap component from Shop Floor" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/scrap_manufacturing.rst:66 +msgid "To scrap a component from the *Shop Floor* module, begin by navigating to :menuselection:`Shop Floor`. Then, either click the :guilabel:`⋮ (three vertical dots)` button on an |MO| card, or select a work center from the top navigation, and click the :guilabel:`⋮ (three vertical dots)` button on a work order card." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/scrap_manufacturing.rst:71 +msgid "Either method opens the :guilabel:`What do you want to do?` pop-up window. Click the :guilabel:`Scrap` button on the window to open the :guilabel:`Scrap` pop-up window." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/scrap_manufacturing.rst:77 +msgid "After opening the scrap pop-up window using one of the methods :ref:`detailed above `, select the component or finished product being scrapped, from the :guilabel:`Product` drop-down menu." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/scrap_manufacturing.rst:81 +msgid "In the :guilabel:`Quantity` field, enter the quantity being scrapped." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/scrap_manufacturing.rst:83 +msgid "By default, the :guilabel:`Source Location` field is set to the warehouse's pre-production location, while the :guilabel:`Scrap Location` field is set to the :guilabel:`Virtual Locations/Scrap` location. If either the source or scrap location should be changed, select a different location from their respective drop-down menus." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/scrap_manufacturing.rst:88 +msgid "Enable the :guilabel:`Replenish Scrapped Quantities` checkbox if a picking order should be created to replace the scrapped component(s) upon confirmation of the scrap order. This option should only be enabled for warehouses with :doc:`two-step <../basic_setup/two_step_manufacturing>` or :doc:`three-step <../basic_setup/three_step_manufacturing>` manufacturing enabled, since components are not picked as part of the :doc:`one-step <../basic_setup/one_step_manufacturing>` manufacturing process." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/scrap_manufacturing.rst:-1 +msgid "The Scrap pop-up window." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/scrap_manufacturing.rst:99 +msgid "Click the :guilabel:`Scrap` button to scrap the selected component. After one or more scrap orders have been created, a :guilabel:`Scraps` smart button appears at the top of the screen. Click it to view a list of all scrap orders for the |MO|." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/scrap_manufacturing.rst:103 +msgid "If a picking order was automatically created to replenish the scrapped components, it can be accessed by opening the :menuselection:`Inventory` app, clicking the :guilabel:`# To Process` button on the :guilabel:`Pick Components` card, and selecting the order." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/split_merge.rst:3 +msgid "Split and merge manufacturing orders" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/split_merge.rst:5 +msgid "In Odoo *Manufacturing*, it is possible to create manufacturing orders for a single unit of an item, or multiple units of the same item. In some cases, it may be necessary to split a manufacturing order that contains multiple units into two or more orders, or to merge two or more orders into a single order." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/split_merge.rst:11 +msgid "A manufacturing order can only contain one unit of a product, or multiple units of a single product that all use the same Bill of Materials (BoM). As a result, it is only possible to merge manufacturing orders when every order contains the same product being manufactured with the same BoM." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/split_merge.rst:17 +msgid "Split manufacturing orders" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/split_merge.rst:19 +msgid "To split a manufacturing order into multiple orders, begin by navigating to :menuselection:`Manufacturing --> Operations --> Manufacturing Orders`, then select a manufacturing order. At the top of the page, next to the :guilabel:`New` button, the manufacturing order's reference number appears with a :guilabel:`⚙️ (settings)` button next to it." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/split_merge.rst:24 +msgid "Click the :guilabel:`⚙️ (settings)` button to open the general settings for the manufacturing order, then select :guilabel:`Split`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/split_merge.rst:-1 +msgid "The Settings and Split buttons on a manufacturing order." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/split_merge.rst:31 +msgid "After selecting :guilabel:`Split`, a :guilabel:`Split production` pop-up window appears. In the :guilabel:`Split #` field, enter the number of manufacturing orders that the original order should be split into, then click outside of the field. A table appears below, with a line for each new manufacturing order that will be created by the split. In the :guilabel:`Quantity To Produce` column, enter the number of units that will be assigned to each new manufacturing order. Finally, click :guilabel:`Split` to split the manufacturing order." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/split_merge.rst:-1 +msgid "The Split production pop-up window for a manufacturing order." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/split_merge.rst:42 +msgid "After clicking :guilabel:`Split`, the original manufacturing order is split into the number of orders that was specified in the :guilabel:`Split #` field. The reference numbers for the new manufacturing orders are the reference number for the original order with *-###* tags added to the end." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/split_merge.rst:48 +msgid "Manufacturing order *WH/MO/00012* is split into three separate orders. The reference numbers for the new orders are *WH/MO/00012-001*, *WH/MO/00012-002*, and *WH/MO/00012-003*." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/split_merge.rst:52 +msgid "Merge manufacturing orders" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/split_merge.rst:54 +msgid "To merge two or more manufacturing orders into a single order, begin by navigating to :menuselection:`Manufacturing --> Operations --> Manufacturing Orders`. Select the manufacturing orders that will be merged by activating the checkbox to the left of the name of each order." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/split_merge.rst:-1 +msgid "Select manufacturing orders that will be merged by clicking the checkbox for each." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/split_merge.rst:62 +msgid "Once all manufacturing orders have been selected, click the :guilabel:`Actions` button at the top of the page, then select :guilabel:`Merge` from the drop-down menu." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/split_merge.rst:-1 +msgid "The Actions and Merge buttons on the Manufacturing Orders page." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/split_merge.rst:69 +msgid "The selected manufacturing orders are merged into a single order. The reference number for the new manufacturing order is the next sequential number that has *not* already been assigned to an order." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/split_merge.rst:73 +msgid "The last reference number used for a manufacturing order was *WH/MO/00012*. Two manufacturing orders, *WH/MO/00008* and *WH/MO/00009*, are merged into a single order. The reference number for the manufacturing order created by the merger is *WH/MO/00013*." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/split_merge.rst:77 +msgid "In the :guilabel:`Source` field for the manufacturing order created by the merger, the reference numbers of the manufacturing orders that were merged are listed." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/split_merge.rst:81 +msgid "Manufacturing orders *WH/MO/00009* and *WH/MO/00010* are merged to create *WH/MO/00011*. The source field for *WH/MO/00011* lists both *WH/MO/00009* and *WH/MO/00010*." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/subcontracting.rst:3 +msgid "Subcontracting overview" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/subcontracting.rst:7 +msgid "In manufacturing, *subcontracting* is the process of a company engaging a third-party manufacturer, or subcontractor, to manufacture products that are then sold by the contracting company." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/subcontracting.rst:10 +msgid "Subcontracting provides a variety of benefits for both the contracting company and the subcontractor." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/subcontracting.rst:13 +msgid "For the contracting company, subcontracting allows them to sell a wide variety of manufactured products, without having to worry about investing in and maintaining the equipment and labor required to handle the manufacturing themselves." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/subcontracting.rst:17 +msgid "This helps contracting companies stay flexible throughout economic cycles, as they can easily increase or decrease their engagements with subcontractors, as necessitated by the current moment. It also means they are able to focus on tasks they excel at, while delegating more specialized work to subcontractors." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/subcontracting.rst:22 +msgid "On the other side of the relationship, subcontracting allows subcontractors to specialize in more niche areas of production, which might not be as profitable outside the bounds of a subcontracting engagement. In certain arrangements, it also provides them with the flexibility to choose which projects they accept or decline, and how many they work on at any given time." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/subcontracting.rst:27 +msgid "In Odoo, companies can configure their subcontracting workflows based on a variety of different factors, including how components are sourced, and what happens to finished products once they are manufactured." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/subcontracting.rst:34 +msgid "To enable subcontracting in Odoo, navigate to :menuselection:`Manufacturing app --> Configuration --> Settings`, and tick the checkbox next to the :guilabel:`Subcontracting` setting, under the :guilabel:`Operations` heading. Then, click :guilabel:`Save`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/subcontracting.rst:-1 +msgid "The Subcontracting setting in the manufacturing app." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/subcontracting.rst:42 +msgid "With subcontracting enabled, a few different features become available in Odoo:" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/subcontracting.rst:44 +msgid "On bills of materials (BoMs), the *BoM Type* field now includes a *Subcontracting* option. Enabling the *Subcontracting* |BoM| type designates the |BoM|'s product as a subcontracted product, which means Odoo knows that it is produced by a subcontractor, and not by the company that owns the Odoo database." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/subcontracting.rst:48 +msgid "Two subcontracting routes become available in the *Inventory* app, and can be assigned to specific products, on the *Inventory* tab of their product pages:" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/subcontracting.rst:51 +msgid "*Resupply Subcontractor on Order*" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/subcontracting.rst:52 +msgid "*Dropship Subcontractor on Order*" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/subcontracting.rst:55 +msgid "Subcontracting workflows" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/subcontracting.rst:57 +msgid "In Odoo, there are three subcontracting workflows, the main difference between them being *how* the subcontractor obtains the necessary components:" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/subcontracting.rst:60 +msgid "In the *basic* subcontracting workflow, the subcontractor is fully responsible for obtaining the components. This workflow is outlined in the :doc:`subcontracting_basic` documentation." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/subcontracting.rst:62 +msgid "In the *Resupply Subcontractor on Order* workflow, the contracting company sends the components from their warehouse to the subcontractor. This workflow is outlined in the :doc:`subcontracting_resupply` documentation." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/subcontracting.rst:65 +msgid "In the *Dropship Subcontractor on Order* workflow, the contracting company purchases the components from a vendor, and has them delivered directly to the subcontractor. This workflow is outlined in the :doc:`subcontracting_dropship` documentation." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/subcontracting.rst:69 +msgid "In addition to how a subcontractor obtains components, it is also necessary to consider why a product is being subcontracted, as well as what happens to products once they are manufactured by the subcontractor." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/subcontracting.rst:73 +msgid "In terms of why a product is being subcontracted, the two main reasons are to fulfill a customer order, or to replenish the quantity of stock on-hand." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/subcontracting.rst:76 +msgid "In terms of what happens to products once they are manufactured, they can either be shipped to the contracting company, or dropshipped directly to an end customer." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/subcontracting.rst:79 +msgid "Each of the three subcontracting workflows described above can be configured to facilitate any of these possibilities, and the methods for doing so are outlined in their respective documentation." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/subcontracting.rst:83 +msgid "Subcontracted product valuation" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/subcontracting.rst:85 +msgid "The valuation of a subcontracted product depends upon a few different variables:" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/subcontracting.rst:87 +msgid "The cost of the required components, if provided by the contracting company; from here on referred to as `C`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/subcontracting.rst:89 +msgid "The price paid to the subcontractor for the service of manufacturing the subcontracted product; from here on referred to as `M`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/subcontracting.rst:91 +msgid "The cost of shipping components to the subcontractor, and having them shipped back to the contracting company; from here on referred to as `S`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/subcontracting.rst:93 +msgid "The cost of dropshipping, if the components are shipped by the subcontractor to the end customer; from here on referred to as `D`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/subcontracting.rst:95 +msgid "Any other associated costs, like import taxes, etc.; from here on referred to as `x`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/subcontracting.rst:97 +msgid "Therefore, the total valuation of a subcontracted product (`P`) can be represented by the following equation:" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/subcontracting.rst:100 +msgid "P = C + M + S + D + x\n" +"\n" +"" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/subcontracting.rst:103 +msgid "It is important to note that not every subcontracted product valuation will include all of these variables. For example, if the product is not dropshipped to the end customer, then there is no need to factor in the cost of dropshipping." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/subcontracting_basic.rst:3 +msgid "Basic subcontracting" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/subcontracting_basic.rst:10 +#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/subcontracting_dropship.rst:12 +#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/subcontracting_resupply.rst:10 +msgid "In manufacturing, subcontracting is the process of a company engaging a third-party manufacturer, or subcontractor, to manufacture products that are then sold by the contracting company." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/subcontracting_basic.rst:13 +msgid "In basic subcontracting, the subcontractor is responsible for acquiring the necessary components. This means that the contracting company only has to worry about what happens to subcontracted products once they are produced." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/subcontracting_basic.rst:17 +msgid "The workflow for purchasing a product manufactured using basic subcontracting is similar to the one used when purchasing a non-subcontracted product from a vendor. The main differences are the way that subcontracted products are configured, and the fact that subcontracted products take longer to be sent from the vendor, since they must first be manufactured by them." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/subcontracting_basic.rst:25 +msgid "To use subcontracting in Odoo, navigate to :menuselection:`Manufacturing app --> Configuration --> Settings`, and tick the checkbox next to the :guilabel:`Subcontracting` setting, under the :guilabel:`Operations` heading. Then, click :guilabel:`Save`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/subcontracting_basic.rst:29 +msgid "Once the :guilabel:`Subcontracting` setting is enabled, it is also necessary to properly configure the subcontracted product, and the product's |BoM|." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/subcontracting_basic.rst:35 +#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/subcontracting_dropship.rst:51 +#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/subcontracting_resupply.rst:53 +msgid "Configure product" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/subcontracting_basic.rst:37 +msgid "To configure a product for basic subcontracting, navigate to :menuselection:`Inventory app --> Products --> Products`, and select a product, or create a new one by clicking :guilabel:`New`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/subcontracting_basic.rst:40 +msgid "On the product form, select the :guilabel:`Purchase` tab, and add the product's subcontractor as a vendor by clicking :guilabel:`Add a line`, selecting the subcontractor in the :guilabel:`Vendor` drop-down menu, and entering a price in the :guilabel:`Price` field." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/subcontracting_basic.rst:44 +msgid "Then, click on the :guilabel:`Inventory` tab, and use the :guilabel:`Routes` field to configure a route that determines what happens to the finished product once it has been manufactured by the subcontractor." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/subcontracting_basic.rst:48 +msgid "If the finished product is shipped back to the contracting company, make sure the :guilabel:`Buy` route is selected. In addition, select the :guilabel:`Replenish on Order (MTO)` route to automatically create a |PO| for the product upon confirmation of a sales order (SO), unless there is enough stock on-hand to fulfill the |SO|." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/subcontracting_basic.rst:53 +msgid "If the finished product is shipped directly to the customer by the subcontractor, make sure that **only** the :guilabel:`Dropship` route is selected." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/subcontracting_basic.rst:57 +#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/subcontracting_resupply.rst:83 +msgid "Configure BoM" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/subcontracting_basic.rst:59 +msgid "To configure a |BoM| for basic subcontracting, click the :guilabel:`Bill of Materials` smart button on the product form, and select the desired |BoM|." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/subcontracting_basic.rst:62 +#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/subcontracting_dropship.rst:78 +#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/subcontracting_resupply.rst:88 +msgid "Alternatively, navigate to :menuselection:`Manufacturing app --> Products --> Bills of Materials`, and select the |BoM| for the subcontracted product." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/subcontracting_basic.rst:66 +#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/subcontracting_dropship.rst:82 +#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/subcontracting_resupply.rst:92 +msgid "For a full overview of |BoM| configuration, see the :doc:`Bill of materials <../basic_setup/bill_configuration>` documentation." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/subcontracting_basic.rst:69 +#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/subcontracting_dropship.rst:85 +#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/subcontracting_resupply.rst:95 +msgid "In the :guilabel:`BoM Type` field, select the :guilabel:`Subcontracting` option. Then, add one or more subcontractors in the :guilabel:`Subcontractors` field that appears below." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/subcontracting_basic.rst:-1 +#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/subcontracting_dropship.rst:-1 +#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/subcontracting_resupply.rst:-1 +msgid "The \"BoM Type\" field on a BoM, configured to manufacture the product using subcontracting." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/subcontracting_basic.rst:76 +msgid "Finally, click on the :guilabel:`Miscellaneous` tab. In the :guilabel:`Manuf. Lead Time` field, enter the number of days it takes the subcontractor to manufacture the product. This number is factored in when calculating the product's expected arrival date." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/subcontracting_basic.rst:81 +msgid "When using basic subcontracting, there is no need to list components in the :guilabel:`Components` tab of the |BoM|, since the components required for manufacturing, and the means by which they are acquired, are handled by the subcontractor." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/subcontracting_basic.rst:86 +msgid "Basic subcontracting workflow" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/subcontracting_basic.rst:88 +msgid "The basic subcontracting workflow consists of up to four steps:" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/subcontracting_basic.rst:90 +msgid "Create a sales order (SO) for the subcontracted product; doing so creates a |PO| to purchase the product from the subcontractor." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/subcontracting_basic.rst:92 +msgid "Confirm the |PO| created in the previous step, or create a new |PO|; doing so creates a receipt order or a dropship order." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/subcontracting_basic.rst:94 +msgid "Process the receipt once the subcontractor has finished manufacturing the subcontracted product, and shipped it back to the contracting company, **OR** process the dropship order to ship the product directly to the customer." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/subcontracting_basic.rst:97 +#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/subcontracting_resupply.rst:135 +msgid "If the workflow was started by creating an |SO|, and the finished product is not dropshipped to the end customer, process the delivery order once the product is shipped to the customer." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/subcontracting_basic.rst:100 +#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/subcontracting_dropship.rst:138 +#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/subcontracting_resupply.rst:138 +msgid "The specific number of steps depends on the reason that the subcontracted product is being purchased from the subcontractor." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/subcontracting_basic.rst:103 +#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/subcontracting_resupply.rst:141 +msgid "If the reason is to fulfill a specific customer order, the process starts with creating an |SO|, and ends with delivering the product to the customer, or having the subcontractor dropship it to them." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/subcontracting_basic.rst:106 +#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/subcontracting_resupply.rst:144 +msgid "If the reason is to increase the quantity of stock on-hand, the process starts with creating a |PO|, and ends with receiving the product into inventory." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/subcontracting_basic.rst:110 +#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/subcontracting_resupply.rst:169 +msgid "Create SO" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/subcontracting_basic.rst:112 +#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/subcontracting_dropship.rst:150 +#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/subcontracting_resupply.rst:171 +msgid "It is only necessary to complete this step if the product is being purchased from the subcontractor to fulfill a customer need. If the product is being purchased to increase the quantity of stock on-hand, move on to the next step." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/subcontracting_basic.rst:116 +#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/subcontracting_dropship.rst:154 +#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/subcontracting_resupply.rst:175 +msgid "To create a new |SO|, navigate to :menuselection:`Sales app --> Orders --> Orders`, and click :guilabel:`New`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/subcontracting_basic.rst:119 +#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/subcontracting_resupply.rst:178 +msgid "Select the customer in the :guilabel:`Customer` drop-down menu. Then, click :guilabel:`Add a product` on the :guilabel:`Order Lines` tab, select a subcontracted product in the :guilabel:`Product` drop-down menu, and enter a quantity in the :guilabel:`Quantity` field." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/subcontracting_basic.rst:123 +#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/subcontracting_resupply.rst:182 +msgid "Click :guilabel:`Confirm` to confirm the |SO|, at which point a :guilabel:`Purchase` smart button appears at the top of the page. This opens the |PO| created to purchase the subcontracted product from the subcontractor." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/subcontracting_basic.rst:128 +msgid "An |SO| for the product only creates a |PO| if the *Replenish on Order (MTO)* route is enabled on the product's form, **and** there is not enough stock of the product on-hand to fulfill the |SO|." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/subcontracting_basic.rst:131 +msgid "If there is enough stock on-hand, confirming an |SO| for the product creates a delivery order instead, because Odoo assumes that the |SO| is fulfilled using the stock in the warehouse." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/subcontracting_basic.rst:134 +#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/subcontracting_resupply.rst:193 +msgid "This is not the case for subcontracted products that are dropshipped to the end customer. In that case, a |PO| is **always** created, even if there is enough stock on-hand." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/subcontracting_basic.rst:138 +#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/subcontracting_resupply.rst:197 +msgid "Process PO" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/subcontracting_basic.rst:140 +msgid "If a |PO| was created in the previous step, navigate to it by clicking the :guilabel:`Purchase` smart button at the top of the |SO|, or by going to :guilabel:`Purchase app --> Orders --> Purchase Orders`, and selecting the |PO|. Then, click :guilabel:`Confirm Order` to confirm it, and move on to the next step." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/subcontracting_basic.rst:145 +#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/subcontracting_resupply.rst:202 +msgid "If a |PO| was not created in the previous step, do so now by navigating to :menuselection:`Purchase app --> Orders --> Purchase Orders`, and clicking :guilabel:`New`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/subcontracting_basic.rst:148 +#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/subcontracting_resupply.rst:205 +msgid "Begin filling out the |PO| by selecting a subcontractor from the :guilabel:`Vendor` drop-down menu. In the :guilabel:`Products` tab, click :guilabel:`Add a product` to create a new product line. Select a subcontracted product in the :guilabel:`Product` field, and enter the quantity in the :guilabel:`Quantity` field. Finally, click :guilabel:`Confirm Order` to confirm the |PO|." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/subcontracting_basic.rst:153 +msgid "When a |PO| is confirmed for a product manufactured using basic subcontracting, a receipt or dropship order is automatically created, and can be accessed from the corresponding :guilabel:`Receipt` or :guilabel:`Dropship` smart button that appears at the top of the |PO|." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/subcontracting_basic.rst:161 +msgid "A PO for a basic subcontracting product, with a Receipt smart button at the top of the page." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/subcontracting_basic.rst:161 +msgid "PO for a basic subcontracting product, with a Receipt smart button at the top of the page." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/subcontracting_basic.rst:164 +#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/subcontracting_dropship.rst:237 +#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/subcontracting_resupply.rst:242 +msgid "Process receipt or dropship order" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/subcontracting_basic.rst:166 +msgid "Once the subcontractor has finished manufacturing the product, they either ship it to the contracting company, or dropship it to the end customer, depending on how the product was :ref:`configured `." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/subcontracting_basic.rst:171 +#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/subcontracting_resupply.rst:249 +msgid "Process receipt" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/subcontracting_basic.rst:173 +#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/subcontracting_resupply.rst:251 +msgid "If the subcontractor ships the finished product to the contracting company, once it has been received, navigate to :menuselection:`Purchase app --> Orders --> Purchase Orders`, and select the |PO|." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/subcontracting_basic.rst:177 +#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/subcontracting_resupply.rst:255 +msgid "Click the :guilabel:`Receive Products` button at the top of the |PO|, or the :guilabel:`Receipt` smart button at the top of the page, to open the receipt. Then, click :guilabel:`Validate` at the top of the receipt to enter the product into inventory." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/subcontracting_basic.rst:182 +#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/subcontracting_resupply.rst:260 +msgid "Process dropship order" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/subcontracting_basic.rst:184 +#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/subcontracting_resupply.rst:262 +msgid "If the subcontractor dropships the product, once they have sent it, navigate to :menuselection:`Purchase app --> Orders --> Purchase Orders`, and select the |PO|." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/subcontracting_basic.rst:187 +#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/subcontracting_resupply.rst:265 +msgid "Select the :guilabel:`Dropship` smart button at the top of the page to open the dropship order, and click :guilabel:`Validate` at the top of the order to confirm that the product has been sent to the customer." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/subcontracting_basic.rst:192 +#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/subcontracting_dropship.rst:254 +#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/subcontracting_resupply.rst:270 +msgid "Process delivery order" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/subcontracting_basic.rst:194 +#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/subcontracting_dropship.rst:256 +msgid "If the subcontracting workflow was started by a customer |SO|, and the finished product was **not** dropshipped to the customer, but rather delivered to the contracting company, it is necessary to ship the product to the customer, and process the delivery order." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/subcontracting_basic.rst:198 +msgid "Once the product has been shipped to the customer, navigate to the :menuselection:`Sales` app, and select the |SO|. Select the :guilabel:`Delivery` smart button at the top of the page to open the delivery order, and click :guilabel:`Validate` on the order to confirm that the product has been shipped." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/subcontracting_dropship.rst:3 +msgid "Dropship to subcontractor" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/subcontracting_dropship.rst:15 +msgid "In Odoo, the *Dropship Subcontractor on Order* route is used to purchase the necessary components for a subcontracted product from the vendor, and have them delivered directly to the subcontractor, each time a purchase order (PO) for that product is confirmed." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/subcontracting_dropship.rst:19 +msgid "The subcontractor then uses the components to manufacture the desired product, before shipping it back to the contracting company." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/subcontracting_dropship.rst:23 +msgid "It is necessary to understand the differences between the *Dropship* and *Dropship Subcontractor on Order* routes. While both routes involve dropshipping, they are used for different purposes." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/subcontracting_dropship.rst:26 +msgid "The *Dropship* route is used to purchase products from a vendor, and have them shipped directly to the end customer." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/subcontracting_dropship.rst:29 +msgid "The *Dropship Subcontractor on Order* route is used to purchase components from a vendor, and have them shipped directly to a subcontractor. By default, finished products are then sent from the subcontractor back to the contracting company." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/subcontracting_dropship.rst:33 +msgid "However, it is possible to combine both the *Dropship* and *Dropship Subcontractor on Order* routes so they are used for the same product. In this workflow, components are dropshipped to the subcontractor, who then ships the finished product directly to the end customer." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/subcontracting_dropship.rst:37 +msgid "This can be achieved by following steps one through five in the :ref:`workflow section ` of this doc." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/subcontracting_dropship.rst:43 +msgid "To use the *Dropship Subcontractor on Order* route, navigate to :menuselection:`Manufacturing app --> Configuration --> Settings`, and enable the checkbox next to :guilabel:`Subcontracting`, under the :guilabel:`Operations` heading." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/subcontracting_dropship.rst:47 +msgid "Once the *Subcontracting* setting is enabled, it is also necessary to properly configure the subcontracted product, the product's |BoM|, and the components listed on the |BoM|." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/subcontracting_dropship.rst:53 +msgid "To configure a product for the *Dropship Subcontractor on Order* route, navigate to :menuselection:`Inventory app --> Products --> Products`, and select a product, or create a new one by clicking :guilabel:`New`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/subcontracting_dropship.rst:57 +#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/subcontracting_resupply.rst:59 +msgid "Select the :guilabel:`Purchase` tab, and add the product's subcontractor as a vendor by clicking :guilabel:`Add a line`, selecting the subcontractor in the :guilabel:`Vendor` drop-down menu, and entering a price in the :guilabel:`Price` field." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/subcontracting_dropship.rst:61 +#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/subcontracting_resupply.rst:71 +msgid "Then, click on the :guilabel:`Inventory` tab to configure a route that determines what happens to the finished product, once it has been manufactured by the subcontractor." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/subcontracting_dropship.rst:64 +msgid "If the finished product is shipped back to the contracting company, make sure that the :guilabel:`Buy` route is selected. In addition, select the :guilabel:`Replenish on Order (MTO)` route to automatically create a |PO| for the product upon confirmation of a |SO|, unless there is enough stock on-hand to fulfill the |SO|." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/subcontracting_dropship.rst:69 +#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/subcontracting_resupply.rst:79 +msgid "If the finished product is shipped directly to the customer by the subcontractor, make sure that only the :guilabel:`Dropship` route is selected." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/subcontracting_dropship.rst:73 +msgid "Configure bill of materials" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/subcontracting_dropship.rst:75 +msgid "To configure a |BoM| for the *Dropship Subcontractor on Order* route, click the :guilabel:`Bill of Materials` smart button on the product's page, and select the |BoM|." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/subcontracting_dropship.rst:92 +#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/subcontracting_resupply.rst:102 +msgid "Finally, make sure that all necessary components are specified on the :guilabel:`Components` tab. To add a new component, click :guilabel:`Add a line`, select the component in the :guilabel:`Component` drop-down menu, and specify the required quantity in the :guilabel:`Quantity` field." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/subcontracting_dropship.rst:97 +msgid "Configure Components" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/subcontracting_dropship.rst:99 +msgid "To configure components for the *Dropship Subcontractor on Order* route, navigate to each component from the |BoM| by selecting the component's name in the :guilabel:`Components` tab, and clicking the :guilabel:`➡️ (right arrow)` button to the right of the name." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/subcontracting_dropship.rst:103 +#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/subcontracting_resupply.rst:113 +msgid "Alternatively, navigate to each component by going to :menuselection:`Inventory app --> Products --> Products`, and selecting the component." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/subcontracting_dropship.rst:106 +msgid "On the component product form, select the :guilabel:`Purchase` tab, and add a vendor by clicking :guilabel:`Add a line`, selecting the vendor in the :guilabel:`Vendor` field, and adding the price they sell the product for in the :guilabel:`Price` field. This is the vendor that sends components to the subcontractor, once they are purchased." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/subcontracting_dropship.rst:111 +msgid "Then, click on the :guilabel:`Inventory` tab and select the :guilabel:`Dropship Subcontractor on Order` route in the :guilabel:`Routes` section." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/subcontracting_dropship.rst:114 +msgid "Repeat the process for every component that must be dropshipped to the subcontractor." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/subcontracting_dropship.rst:119 +msgid "Dropship subcontractor on order workflow" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/subcontracting_dropship.rst:121 +msgid "The dropship subcontractor on order workflow consists of up to six steps:" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/subcontracting_dropship.rst:123 +msgid "Create a sales order (SO) for the subcontracted product; doing so creates a *subcontractor* |PO| to purchase the product from the subcontractor." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/subcontracting_dropship.rst:125 +msgid "Confirm the |PO| created in the previous step, or create a new |PO|; doing so creates a request for quotation (RfQ) to purchase the components from the vendor, as well as a receipt order or a dropship order." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/subcontracting_dropship.rst:128 +msgid "Confirm the |RfQ| to turn it into a second |PO| (*vendor* |PO|); doing so creates a *Dropship Subcontractor* order." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/subcontracting_dropship.rst:130 +msgid "Process the *Dropship Subcontractor* order once the vendor has sent the components to the subcontractor." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/subcontracting_dropship.rst:132 +msgid "Process the receipt once the subcontractor has finished manufacturing the subcontracted product, and shipped it back to the contracting company **OR** process the dropship order to ship the product directly to the end customer." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/subcontracting_dropship.rst:135 +msgid "If the workflow was started by creating an |SO|, and the finished product is not dropshipped to the end customer, process the delivery order once the product has been shipped to the customer." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/subcontracting_dropship.rst:141 +msgid "If the reason is to fulfill a specific customer order, the process starts with creating an SO, and ends with delivering the product to the customer, or having the subcontractor dropship it to them." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/subcontracting_dropship.rst:144 +msgid "If the reason is to increase quantity of stock on-hand, the process starts with creating a PO, and ends with receiving the product into inventory." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/subcontracting_dropship.rst:148 +msgid "Create an SO" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/subcontracting_dropship.rst:157 +msgid "Select the customer in the :guilabel:`Customer` drop-down menu. Then, click :guilabel:`Add a product` on the :guilabel:`Order Lines` tab, select the product in the :guilabel:`Product` drop-down menu, and enter a quantity in the :guilabel:`Quantity` field." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/subcontracting_dropship.rst:161 +msgid "Click :guilabel:`Confirm` to confirm the |SO|, at which point a :guilabel:`Purchase` smart button appears at the top of the page. This is the *subcontractor* |PO|, or the |PO| created to purchase the subcontracted product from the subcontractor." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/subcontracting_dropship.rst:166 +msgid "An |SO| for the product only creates a *subcontractor* |PO| if the *Replenish on Order (MTO)* route is enabled on the product's page, **and** there is no stock of the product on-hand." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/subcontracting_dropship.rst:169 +msgid "If there is stock on-hand, confirming an |SO| for the product will instead create a delivery order, because Odoo assumes that the |SO| is fulfilled using the stock in the warehouse." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/subcontracting_dropship.rst:172 +msgid "This is not the case for subcontracted products that are dropshipped to the end customer. In that case, a *subcontractor* |PO| is **always** created, even if there is stock on-hand." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/subcontracting_dropship.rst:176 +msgid "Process subcontractor PO" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/subcontracting_dropship.rst:178 +msgid "If a *subcontractor* |PO| was not created in the previous step, do so now by navigating to :menuselection:`Purchase app --> Orders --> Purchase Orders`, and clicking :guilabel:`New`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/subcontracting_dropship.rst:181 +msgid "Begin filling out the |PO| by selecting a subcontractor from the :guilabel:`Vendor` drop-down menu." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/subcontracting_dropship.rst:183 +msgid "In the :guilabel:`Products` tab, click :guilabel:`Add a product` to create a new product line. Select a product produced by the subcontractor in the :guilabel:`Product` field, and enter the quantity in the :guilabel:`Quantity` field." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/subcontracting_dropship.rst:187 +msgid "Finally, click :guilabel:`Confirm Order` to confirm the *subcontractor* |PO|." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/subcontracting_dropship.rst:189 +msgid "When a |PO| is confirmed for a product that requires dropshipping components to a subcontractor, a receipt or dropship order is automatically created, and can be accessed from the corresponding :guilabel:`Receipt` or :guilabel:`Dropship` smart button that appears at the top of the |PO|." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/subcontracting_dropship.rst:-1 +msgid "A subcontractor PO for a *Dropship Subcontractor on Order* product, with a Receipt smart\n" +"button at the top of the page." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/subcontracting_dropship.rst:198 +msgid "In addition, an |RfQ| is created for the components that are purchased from the vendor and sent to the subcontractor. However, the |RfQ| **IS NOT** automatically linked to the *subcontractor* |PO|." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/subcontracting_dropship.rst:201 +msgid "Once the |RfQ| is confirmed and becomes a *vendor* |PO|, a *Dropship Subcontractor* order is created. This order is linked to both the *vendor* |PO| and the *subcontractor* |PO|." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/subcontracting_dropship.rst:205 +msgid "Confirm vendor RfQ" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/subcontracting_dropship.rst:207 +msgid "To access the |RfQ| created by confirming the *subcontractor* |PO|, navigate to :menuselection:`Purchase app --> Orders --> Requests for Quotation`. Select the |RfQ| that lists the correct vendor in the :guilabel:`Vendor` field, and the reference number of the receipt that was created after confirming *subcontractor* |PO|, in the :guilabel:`Source Document` field." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/subcontracting_dropship.rst:212 +msgid "On the |RfQ|, the :guilabel:`Deliver To` field reads :guilabel:`Dropship Subcontractor`, and the :guilabel:`Dropship Address` field shows the name of the subcontractor to whom components are being dropshipped." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/subcontracting_dropship.rst:216 +msgid "Click :guilabel:`Confirm Order` to turn the |RfQ| into a *vendor* |PO|, and confirm the purchase of components from the vendor. After doing so, a :guilabel:`Dropship` smart button appears at the top of the *vendor* |PO|, and a :guilabel:`Resupply` smart button appears at the top of the *subcontractor* |PO|." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/subcontracting_dropship.rst:-1 +msgid "A vendor PO for the components of a *Dropship Subcontractor on Order* product, with a\n" +"Dropship smart button at the top of the page." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/subcontracting_dropship.rst:227 +msgid "Process Dropship Subcontractor order" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/subcontracting_dropship.rst:229 +msgid "Once the components have been delivered to the subcontractor, navigate to :menuselection:`Purchase app --> Orders --> Purchase Orders`, and select the *vendor* |PO| or the *subcontractor* |PO|. Then, click the :guilabel:`Dropship` smart button or the :guilabel:`Resupply` smart button, respectively." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/subcontracting_dropship.rst:233 +msgid "Clicking either button opens the *Dropship Subcontractor* order. Click the :guilabel:`Validate` button at the top of the order to confirm that the subcontractor has received the components." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/subcontracting_dropship.rst:239 +msgid "Once the subcontractor has manufactured the finished product, navigate to :menuselection:`Purchase app --> Orders --> Purchase Orders`, and select the *subcontractor* |PO|." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/subcontracting_dropship.rst:242 +msgid "If the subcontracted product should be received into inventory, once the product arrives, click the :guilabel:`Receive Products` button at the top of the *subcontractor* |PO| to open the receipt. Then, click :guilabel:`Validate` at the top of the receipt to register the product into inventory." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/subcontracting_dropship.rst:246 +msgid "Alternatively, select the :guilabel:`Receipt` smart button at the top of the *subcontractor* |PO|, and click :guilabel:`Validate` at the top of the receipt." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/subcontracting_dropship.rst:249 +msgid "If the subcontracted product should be dropshipped, select the :guilabel:`Dropship` button at the top of the page to open the dropship order, and click :guilabel:`Validate` once the subcontractor has sent the product to the customer." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/subcontracting_dropship.rst:260 +msgid "Once the product has been shipped to the customer, navigate to the :menuselection:`Sales` app, and select the |SO|. Select the :guilabel:`Delivery` smart button at the top of the page to open the delivery order, and click :guilabel:`Validate` to confirm that the product has been shipped to the customer." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/subcontracting_resupply.rst:3 +msgid "Resupply subcontractor" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/subcontracting_resupply.rst:13 +msgid "In Odoo, the *Resupply Subcontractor on Order* route is used to deliver the necessary components for a subcontracted product to the subcontractor, each time a purchase order (PO) for that product is confirmed." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/subcontracting_resupply.rst:17 +msgid "The subcontractor then uses the components to manufacture the desired product, before shipping it back to the contracting company, or dropshipping it to the end customer." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/subcontracting_resupply.rst:21 +msgid "It is necessary to understand the differences between the *Resupply Subcontractor on Order* and the *Dropship Subcontractor on Order* routes." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/subcontracting_resupply.rst:24 +msgid "While both routes are used to supply a subcontractor with the components required for manufacturing a product, they differ in how the components are sourced." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/subcontracting_resupply.rst:27 +msgid "When using *Resupply Subcontractor on Order*, components are shipped from the warehouse of the contracting company." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/subcontracting_resupply.rst:30 +msgid "When using *Dropship Subcontractor on Order*, components are purchased from a vendor and shipped directly to the subcontractor." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/subcontracting_resupply.rst:33 +msgid "The choice of which route to use depends upon the specific requirements of the subcontracting company and their subcontractors." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/subcontracting_resupply.rst:36 +msgid "See the :doc:`subcontracting_dropship` documentation for a full overview of the *Dropship Subcontractor on Order* route." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/subcontracting_resupply.rst:42 +msgid "To use the *Resupply Subcontractor on Order* route, navigate to :menuselection:`Manufacturing app --> Configuration --> Settings`, and enable the checkbox next to :guilabel:`Subcontracting`, under the :guilabel:`Operations` heading." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/subcontracting_resupply.rst:46 +msgid "Once the *Subcontracting* setting is enabled, it is also necessary to properly configure the subcontracted product, the product's bill of materials (BoM), and the components listed on the |BoM|." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/subcontracting_resupply.rst:55 +msgid "To configure a product for the *Resupply Subcontractor on Order* route, navigate to :menuselection:`Inventory app --> Products --> Products`, and select a product, or create a new one by clicking :guilabel:`New`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/subcontracting_resupply.rst:64 +msgid "The value entered in the :guilabel:`Price` field on the :guilabel:`Purchase` tab of the of the subcontracted product's page is the amount paid to the subcontractor for the manufacturing of the product." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/subcontracting_resupply.rst:68 +msgid "This does not represent the total cost of the product, which includes other elements, like the cost of the product's components." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/subcontracting_resupply.rst:74 +msgid "If the finished product is shipped back to the contracting company, make sure that the :guilabel:`Buy` route is selected. In addition, select the :guilabel:`Replenish on Order (MTO)` route to automatically create a |PO| for the product upon confirmation of a sales order (SO), unless there is enough stock on-hand to fulfill the |SO|." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/subcontracting_resupply.rst:85 +msgid "To configure a |BoM| for the *Resupply Subcontractor on Order* route, click the :guilabel:`Bill of Materials` smart button on the product's page, and select the |BoM|." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/subcontracting_resupply.rst:107 +msgid "Configure components" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/subcontracting_resupply.rst:109 +msgid "To configure components for the *Resupply Subcontractor on Order* route, navigate to each component from the |BoM| by selecting the component's name in the :guilabel:`Components` tab, and clicking the :guilabel:`➡️ (right arrow)` button to the right of the name." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/subcontracting_resupply.rst:116 +msgid "On the component product form, click on the :guilabel:`Inventory` tab and select the :guilabel:`Resupply Subcontractor on Order` route in the :guilabel:`Routes` section." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/subcontracting_resupply.rst:119 +msgid "Repeat the process for every component that must be sent to the subcontractor." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/subcontracting_resupply.rst:122 +msgid "Resupply subcontractor on order workflow" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/subcontracting_resupply.rst:124 +msgid "The resupply subcontractor on order workflow consists of up to five steps:" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/subcontracting_resupply.rst:126 +msgid "Create an |SO| for the subcontracted product; doing so creates a |PO| to purchase the product from the subcontractor." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/subcontracting_resupply.rst:128 +msgid "Confirm the |PO| created in the previous step, or create a new |PO|; doing so creates a *Resupply Subcontractor* order, as well as a receipt order or a dropship order." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/subcontracting_resupply.rst:130 +msgid "Process the *Resupply Subcontractor* order once components for the subcontracted product have been sent to the subcontractor." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/subcontracting_resupply.rst:132 +msgid "Process the receipt once the subcontractor has finished manufacturing the subcontracted product, and shipped it back to the contracting company **OR** process the dropship order to ship the product directly to the customer." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/subcontracting_resupply.rst:149 +msgid "While the *Resupply Subcontractor on Order* route can be used to automatically resupply a subcontractor upon confirmation of a |PO|, it is also possible to create a resupply order manually. This workflow is useful when it is necessary to resupply the subcontractor without creating a |PO|." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/subcontracting_resupply.rst:154 +msgid "To resupply a subcontractor manually, navigate to the :menuselection:`Inventory` app, and click on the :guilabel:`Resupply Subcontractor` card. Create a new *Resupply Subcontractor* order by clicking :guilabel:`New`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/subcontracting_resupply.rst:158 +msgid "In the :guilabel:`Delivery Address` field, select the subcontractor to whom the components should be sent." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/subcontracting_resupply.rst:161 +msgid "Then, add each component to the :guilabel:`Operations` tab by clicking :guilabel:`Add a line`, selecting the component in the :guilabel:`Product` drop-down field, and specifying a quantity in the :guilabel:`Demand` field." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/subcontracting_resupply.rst:165 +msgid "Finally, click :guilabel:`Mark as Todo` to register the order. Once the components have been sent to the subcontractor, click :guilabel:`Validate` to confirm that the order has been sent." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/subcontracting_resupply.rst:187 +msgid "An |SO| for the product only creates a |PO| if the *Replenish on Order (MTO)* route is enabled on the product's page, **and** there is not enough stock of the product on-hand to fulfill the |SO|." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/subcontracting_resupply.rst:190 +msgid "If there is enough stock on-hand, confirming an |SO| for the product instead creates a delivery order, because Odoo assumes that the |SO| is fulfilled using the stock in the warehouse." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/subcontracting_resupply.rst:199 +msgid "If a |PO| was created in the previous step, navigate to :guilabel:`Purchase app --> Orders --> Purchase Orders`, and select the |PO|. Then, click :guilabel:`Confirm Order` to confirm it." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/subcontracting_resupply.rst:210 +msgid "When a |PO| is confirmed for a product that requires resupplying a subcontractor with components, a receipt or dropship order is automatically created, and can be accessed from the corresponding :guilabel:`Receipt` or :guilabel:`Dropship` smart button that appears at the top of the |PO|." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/subcontracting_resupply.rst:214 +msgid "In addition, a *Resupply Subcontractor* order is created to ship the required components to the subcontractor. This order can also be accessed from the |PO|, by clicking the :guilabel:`Resupply` smart button at the top of the page." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/subcontracting_resupply.rst:223 +msgid "A PO for a *Resupply Subcontractor on Order* product, with Resupply and Receipt smart\n" +"buttons at the top of the page." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/subcontracting_resupply.rst:223 +msgid "A PO for a *Resupply Subcontractor on Order* product, with Resupply and Receipt smart buttons at the top of the page." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/subcontracting_resupply.rst:227 +msgid "Process Resupply Subcontractor order" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/subcontracting_resupply.rst:229 +msgid "Once the subcontracted product's components have been sent to the subcontractor, navigate to :menuselection:`Purchase app --> Orders --> Purchase Orders`, and select the |PO|." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/subcontracting_resupply.rst:232 +msgid "Click the :guilabel:`Resupply` smart button at the top of the screen to open the *Resupply Subcontractor* order, and click :guilabel:`Validate` to confirm that the components have been sent to the subcontractor." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/subcontracting_resupply.rst:236 +msgid "Alternatively, navigate to the :menuselection:`Inventory` app, click the :guilabel:`# To Process` button on the :guilabel:`Resupply Subcontractor` card, and select the *Resupply Subcontractor* order. Then, click :guilabel:`Validate` to confirm that the components have been sent to the subcontractor." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/subcontracting_resupply.rst:244 +msgid "Once the subcontractor has finished manufacturing the product, they either ship it to the contracting company, or dropship it to the end customer, depending on how the product was :ref:`configured `." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/subcontracting_resupply.rst:272 +msgid "If the subcontracting workflow was started by a customer |SO|, and the finished product was **NOT** dropshipped to the customer, but rather delivered to the contracting company, it is necessary to ship the product to the customer, and process the delivery order." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/subcontracting_resupply.rst:276 +msgid "Once the product has been shipped to the customer, navigate to the :menuselection:`Sales` app, and select the |SO|. Select the :guilabel:`Delivery` smart button at the top of the page to open the delivery order, and click :guilabel:`Validate` on the order to confirm that the product has been shipped to the customer." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/unbuild_orders.rst:3 +msgid "Unbuild orders" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/unbuild_orders.rst:7 +msgid "In some cases, it is necessary to dismantle manufactured products into their individual components. This may be required if too many units of a product were built, or if the components of one product must be reclaimed to use in the manufacturing of another." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/unbuild_orders.rst:11 +msgid "In Odoo *Manufacturing*, products can be dismantled, and their components returned to inventory, using *unbuild orders*. By using unbuild orders to accomplish this task, inventory counts for the finished product and its components remain accurate, based on the quantity of products dismantled, and the quantity of components reclaimed." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/unbuild_orders.rst:17 +msgid "Create unbuild order" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/unbuild_orders.rst:19 +msgid "A new unbuild order can be created by navigating to :menuselection:`Manufacturing app --> Operations --> Unbuild Orders`, and clicking :guilabel:`New`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/unbuild_orders.rst:22 +msgid "Begin filling out the new unbuild order by selecting a :guilabel:`Product` to unbuild. After doing so, the :guilabel:`Bill of Material` field auto-populates with the corresponding bill of materials (BoM). If a different |BoM| should be used, click on the :guilabel:`Bill of Material` field, and select it from the drop-down menu." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/unbuild_orders.rst:27 +msgid "Alternatively, a specific |BoM| can be selected in the :guilabel:`Bill of Material` field before selecting a product, which causes the corresponding product to auto-populate in the :guilabel:`Product` field." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/unbuild_orders.rst:31 +msgid "Next, specify the :guilabel:`Quantity` of the product that is being unbuilt." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/unbuild_orders.rst:33 +msgid "If the product being unbuilt was originally manufactured in a specific manufacturing order (MO), select it in the :guilabel:`Manufacturing Order` field." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/unbuild_orders.rst:36 +msgid "In the :guilabel:`Source Location` field, select the location where the product being unbuilt is currently stored." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/unbuild_orders.rst:39 +msgid "In the :guilabel:`Destination Location` field, select the location where the reclaimed components are stored after the unbuild order is completed." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/unbuild_orders.rst:42 +msgid "If the *Lots & Serial Numbers* feature is enabled in the settings of the *Inventory* app, a :guilabel:`Lot/Serial Number` field appears on the unbuild order, which can be used to specify the lot(s) or serial number(s) of the product being unbuilt, if any are assigned." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/unbuild_orders.rst:46 +msgid "If the Odoo database has been configured with multiple companies, a :guilabel:`Company` field appears on the unbuild order, which can be used to specify the company that owns the product being unbuilt." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/unbuild_orders.rst:50 +msgid "Finally, once the product has been unbuilt, click the :guilabel:`Unbuild` button at the top of the order to confirm that it has been completed." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/unbuild_orders.rst:-1 +msgid "A filled-out unbuild order." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/unbuild_orders.rst:58 +msgid "While it is possible to create unbuild orders for products that have zero (or fewer) units on-hand, this is not advised, since it can lead to inventory inconsistencies." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/unbuild_orders.rst:61 +msgid "If an unbuild order is created for a product with zero (or fewer) units on-hand, a pop-up window appears, warning the user that there is an insufficient quantity to unbuild." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/unbuild_orders.rst:64 +msgid "To ignore the warning, and proceed with the unbuild order, click :guilabel:`Confirm` at the bottom of the pop-up window. To return to the unconfirmed unbuild order, click :guilabel:`Discard`, instead." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/unbuild_orders.rst:0 +msgid "The insufficient quantity pop-up that appears after trying to confirm an unbuild order\n" +"for a product with zero or fewer units on hand." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/unbuild_orders.rst:73 +msgid "After completing an unbuild order, inventory counts automatically update, based on the quantity of products unbuilt, and the quantity of components reclaimed." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/unbuild_orders.rst:77 +msgid "A `Coat Rack` product is comprised of one `Wooden Pole` component and six `Wooden Dowel` components." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/unbuild_orders.rst:80 +msgid "An unbuild order is created for one unit of the `Coat Rack`. Once the order is completed, the on-hand quantity of `Coat Racks` decreases by one, while the on-hand quantities of `Wooden Poles` and `Wooden Dowels` increase by one and six, respectively." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/unbuild_orders.rst:85 +msgid "Scrap unusable components" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/unbuild_orders.rst:87 +msgid "In some cases, components may be unusable after the unbuilding process is completed. To ensure that inventory counts accurately reflect the quantity of usable components on-hand, any component that can no longer be used should be removed from inventory using a :doc:`scrap order <../../inventory/warehouses_storage/inventory_management/scrap_inventory>`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/use_mps.rst:3 +msgid "Use the Master Production Schedule" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/use_mps.rst:7 +msgid "The Master Production Schedule (MPS) is a valuable tool to plan your production based on your demand forecast." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/use_mps.rst:13 +msgid "Go to the :menuselection:`Manufacturing app --> Configuration --> Settings` and activate the Master Production Schedule feature before hitting save." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/use_mps.rst:17 +msgid "In the MPS settings, you can define the time range of your MPS (month/week/day) and the number of periods you want to display at all times." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/use_mps.rst:20 +msgid "Now, go to :menuselection:`Planning --> Master Production Schedule` and click on *add a product*. You can now define your safety stock target (= the stock you want to have on hand at the end of the period) and the minimum and maximum quantities that must or can be replenished in each period." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/use_mps.rst:28 +msgid "In the MPS view, you can decide which information you would like to display by clicking on *rows*. For instance, the *Actual demand* will show you which quantity of products has already been ordered for the period, or *Available to Promise*, what can still be sold during that same period (what you plan to replenish - what is already sold during the period). You can also decide to hide rows if you like." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/use_mps.rst:38 +msgid "Estimate your demand and launch replenishment" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/use_mps.rst:40 +msgid "The next step is to estimate the demand for the chosen period. This is done in the *Forecasted Demand* Row. You can easily, at any time, compare the demand forecast with the actual demand (= confirmed sales). The demand forecast for a finished product will impact the indirect demand for its components." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/use_mps.rst:48 +msgid "Once the forecasted demand has been set, the quantity to replenish for the different periods will automatically be computed. The replenishments you are supposed to launch based on your lead times (vendor lead time or manufacturing lead time) are then displayed in green. You can now launch the replenishment by clicking on the replenish button." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/use_mps.rst:54 +msgid "Depending on the configuration of the product (buy vs. manufacture), requests for quotations or manufacturing orders will be created. You can easily access those by clicking on the *Actual Replenishment* cell." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/use_mps.rst:61 +msgid "In case you manually edit the *Suggested Replenishment* quantity, a small cross will appear on the left hand side of the cell. In case you want to go back to the automatically computed value given by Odoo, simply click the cross." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/use_mps.rst:67 +msgid "Cells color signification" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/use_mps.rst:69 +msgid "The cells, which are part of the *Suggested Replenishment* line, can take different colors depending on the situation:" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/use_mps.rst:72 +msgid "**Green**: quantity of products which should be replenished to reach the expected safety stock considering the demand forecast and the indirect demand forecast." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/use_mps.rst:74 +msgid "**Grey**: replenishment order has already been generated, and its quantity still matches current data." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/use_mps.rst:76 +msgid "**Red**: replenishment order has already been generated, and its quantity was too high considering current data." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/use_mps.rst:78 +msgid "**Orange**: replenishment order has already been generated, and its quantity was too low considering current data." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/use_mps.rst:80 +msgid "The *Forecasted stock* line can also contain red cells, which means the stock will be negative during the period in question." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/use_mps.rst:84 +msgid "What if I have underestimated the demand?" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/use_mps.rst:86 +msgid "You can still increase the demand forecast. It will impact the quantity to replenish. The cell will become orange, and you’ll be able to launch a new replenishment." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/use_mps.rst:91 +msgid "What if I have overestimated the demand?" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/use_mps.rst:93 +msgid "You can decrease the demand forecast. The cell will become red to inform you that you’ve ordered more than planned. If you’re still able to do it, you can cancel some RFQ or MO manually." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/use_mps.rst:98 +msgid "What if I wrongly added a product to the MPS?" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/use_mps.rst:100 +msgid "You can easily remove a product from the MPS by clicking the small bin on the right of its name." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/work_center_time_off.rst:3 +msgid "Make work centers unavailable using Time Off" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/work_center_time_off.rst:5 +msgid "In Odoo, *work centers* are used to carry out manufacturing operations at specific locations. However, if a work center cannot be used for some reason, work orders begin to pile up at the work center until it is operational again." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/work_center_time_off.rst:9 +msgid "As a result, it is necessary to make the work center unavailable in Odoo so that the platform routes new work orders to alternative work centers that are operational. Using Odoo *Time Off*, it is possible to designate a work center as being unavailable for a set period of time. Doing so ensures that manufacturing operations can continue until the impacted work center is available again." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/work_center_time_off.rst:17 +msgid "Before a work center can be designated as unavailable, the Odoo platform must be properly configured. First, it is necessary to enable :ref:`developer mode `. This allows the :guilabel:`Time Off` smart button to appear on each work center's :guilabel:`Working Hours` pop-up window." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/work_center_time_off.rst:22 +msgid "Enable developer mode by going to :menuselection:`Settings`, scrolling to the bottom of the page, and clicking :guilabel:`Activate the developer mode` under the :guilabel:`Developer Tools` heading." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/work_center_time_off.rst:-1 +msgid "The \"Activate the developer mode\" button." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/work_center_time_off.rst:29 +msgid "Next, install the *Time Off* app. This is the app used for assigning time off to all resources within Odoo, including employees and work centers. Navigate to :menuselection:`Apps`, then type `Time Off` in the :guilabel:`Search...` bar. The card for the :guilabel:`Time Off` module should be the only one that appears on the page. Click the green :guilabel:`Install` button on the card to install the app." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/work_center_time_off.rst:-1 +msgid "The Time Off module installation card." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/work_center_time_off.rst:39 +msgid "The last step is to properly configure work centers. For this workflow, it is necessary to have at least two work centers: one that is made unavailable and a second that receives the work orders that the other cannot accept. If no second work center is configured, Odoo cannot route work orders away from the unavailable work center and they will pile up in its queue." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/work_center_time_off.rst:44 +msgid "To create a work center, navigate to :menuselection:`Manufacturing --> Configuration --> Work Centers --> Create`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/work_center_time_off.rst:47 +msgid "Make sure that both work centers have the same equipment listed under the :guilabel:`Equipment` tab. This ensures that operations carried out at one work center can also be performed at the other." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/work_center_time_off.rst:-1 +msgid "The equipment tab on a work center form." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/work_center_time_off.rst:54 +msgid "For the work center that will be made unavailable, select the second work center on the :guilabel:`Alternative Workcenters` drop-down menu. Now, Odoo knows to send work orders to the second work center when the first is unavailable for any reason." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/work_center_time_off.rst:-1 +msgid "A work center form configured with an alternative work center." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/work_center_time_off.rst:63 +msgid "Add time off for a work center" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/work_center_time_off.rst:65 +msgid "With configuration completed, time off can now be assigned to the work center that will be made unavailable. Begin by navigating to :menuselection:`Manufacturing --> Configuration --> Work Centers` and selecting the affected work center. Click :guilabel:`Edit`, and then the :guilabel:`↗ (external link)` button next to the :guilabel:`Working Hours` drop-down menu." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/work_center_time_off.rst:-1 +msgid "The Working Hours \"External link\" button on the work center form." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/work_center_time_off.rst:74 +msgid "A pop-up appears, titled :guilabel:`Open: Working Hours`. The standard working hours for the work center are listed here, along with various other details about it. Since developer mode was enabled, there is a :guilabel:`Time Off` button in the top right of the pop-up. Click it to be taken to the :guilabel:`Resource Time Off` page." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/work_center_time_off.rst:-1 +msgid "The Time Off button on the Working Hours pop-up." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/work_center_time_off.rst:83 +msgid "On this page, click :guilabel:`Create` to configure a new time-off entry. On the time-off form, note the :guilabel:`Reason` for the work center closure (broken, maintenance, etc.), select the affected work center as the :guilabel:`Resource`, and choose a :guilabel:`Start Date` and :guilabel:`End Date` to specify the period during which the work center will be unavailable. Click :guilabel:`Save` and the time off for the work center is logged in Odoo." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/work_center_time_off.rst:-1 +msgid "The \"Resource Time Off\" form." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/work_center_time_off.rst:94 +msgid "Route orders to an alternative work center" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/work_center_time_off.rst:96 +msgid "Once a work center is within its specified time-off period, work orders sent to it can be automatically routed to an alternative work center using the :guilabel:`Plan` button." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/work_center_time_off.rst:99 +msgid "Begin by creating a new manufacturing order by selecting :menuselection:`Operations --> Manufacturing Orders --> Create`. On the manufacturing order form, specify a :guilabel:`Product` that uses the unavailable work center for one of its operations. Click :guilabel:`Confirm` to confirm the work order." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/work_center_time_off.rst:104 +msgid "On the confirmed work order, select the :guilabel:`Work Orders` tab. By default, the unavailable work center is specified in the :guilabel:`Work Center` column. There is also a green :guilabel:`Plan` button on the top left of the page." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/work_center_time_off.rst:-1 +msgid "The Plan button on a manufacturing order." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/work_center_time_off.rst:112 +msgid "Click :guilabel:`Plan` and the work center listed under the :guilabel:`Work Orders` tab is automatically changed to the alternative work center." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/work_center_time_off.rst:-1 +msgid "The selected work center updates automatically after clicking the Plan button." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/work_center_time_off.rst:119 +msgid "Once the time-off period for the unavailable work center ends, Odoo recognizes that the work center is available again. At this point, clicking the :guilabel:`Plan` button does not route work orders to an alternative work center unless the first one is at capacity." +msgstr "" + #: ../../content/applications/inventory_and_mrp/plm.rst:8 msgid "Product lifecycle management" msgstr "" @@ -15657,229 +18124,335 @@ msgid ":doc:`calls_for_tenders`" msgstr "" #: ../../content/applications/inventory_and_mrp/purchase/manage_deals/calls_for_tenders.rst:3 -msgid "Create alternative requests for quotation for multiple vendors" +msgid "Alternative RfQs" msgstr "" -#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/calls_for_tenders.rst:5 -msgid "Sometimes, companies might want to request offers from multiple vendors at the same time, by inviting those vendors to submit offers for similar goods or services all at once. This helps companies to select the cheapest (and fastest) vendors, depending on their specific business needs." +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/calls_for_tenders.rst:12 +msgid "Sometimes, companies might want to request offers from multiple vendors at the same time, by inviting those vendors to submit offers for similar goods or services all at once. This helps companies to select the cheapest, fastest vendors, depending on their specific business needs." msgstr "" -#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/calls_for_tenders.rst:9 -msgid "In Odoo, this can be done by adding alternative requests for quotation (RFQs) for different vendors. Once a response is received from each vendor, the product lines from each :abbr:`RFQ (Request for Quotation)` can be compared, and a decision can be made for which products to purchase from which vendors." +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/calls_for_tenders.rst:16 +msgid "In Odoo, this can be done by creating alternative requests for quotation (RfQs) for different vendors. Once a response is received from each vendor, the product lines from each |RfQ| can be compared, and a decision can be made for which products to purchase from which vendors." msgstr "" -#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/calls_for_tenders.rst:14 -msgid "Sometimes referred to as a *call for tender*, this process is primarily used by organizations in the public sector, who are legally bound to use it when making a purchase. However, private companies can also use alternative :abbr:`RFQs (Requests for Quotation)` to spend money efficiently, as well." +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/calls_for_tenders.rst:21 +msgid "Sometimes referred to as a *call for tender*, this process is primarily used by organizations in the public sector, who are legally bound to use it when making a purchase. However, private companies can also use alternative |RfQs| to spend money efficiently." msgstr "" -#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/calls_for_tenders.rst:20 -msgid ":doc:`blanket_orders`" +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/calls_for_tenders.rst:28 +msgid "To create alternative |RfQs|, the *Purchase Agreements* feature **must** be enabled in the *Purchase* app settings. To enable the feature, navigate to :menuselection:`Purchase app --> Configuration --> Settings`. Under the :guilabel:`Orders` section, click the checkbox for :guilabel:`Purchase Agreements`." msgstr "" -#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/calls_for_tenders.rst:23 -msgid "Configure purchase agreement settings" +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/calls_for_tenders.rst:33 +msgid "Then, click :guilabel:`Save` to apply the change." msgstr "" -#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/calls_for_tenders.rst:25 -msgid "To create alternative :abbr:`RFQs (Requests for Quotation)` directly from a quotation, the *Purchase Agreements* feature first needs to be enabled in the settings of the *Purchase* app. To do this, go to :menuselection:`Purchase --> Configuration --> Settings`, and under the :guilabel:`Orders` section, click the checkbox next to :guilabel:`Purchase Agreements`. Doing so will enable the ability to create alternative :abbr:`RFQs (Requests for Quotation)`, as well as the ability to create *blanket orders*." +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/calls_for_tenders.rst:35 +msgid "Doing so enables the ability to create alternative |RfQs|, as well as *blanket orders*." msgstr "" -#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/calls_for_tenders.rst:37 -msgid "To save time on a *call for tender*, custom vendors, prices, and delivery lead times can be set in the :guilabel:`Purchase` tab on a product form. To do so, navigate to :menuselection:`Purchase --> Products --> Products`, and select a product to edit. From the product form, click the :guilabel:`Purchase tab`, then click :guilabel:`Add a line`. From the drop-down menu, choose a vendor to set under the :guilabel:`Vendor` column, and set a :guilabel:`Price` and :guilabel:`Delivery Lead Time` if desired. Clicking the :guilabel:`additional options (two-dots)` icon provides additional visibility options to add to the line item." +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/calls_for_tenders.rst:42 +msgid "To save time creating alternative |RfQs|, custom vendors, prices, and delivery lead times can be set in the :guilabel:`Purchase` tab of a product form." msgstr "" -#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/calls_for_tenders.rst:47 -msgid "Create an :abbr:`RFQ (Request for Quotation)`" +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/calls_for_tenders.rst:45 +msgid "To do that, navigate to :menuselection:`Purchase app --> Products --> Products`, and select a product to edit. On the product form, click the :guilabel:`Purchase` tab, and click :guilabel:`Add a line`." msgstr "" #: ../../content/applications/inventory_and_mrp/purchase/manage_deals/calls_for_tenders.rst:49 -#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/calls_for_tenders.rst:148 -msgid "To create a new :abbr:`RFQ (Request for Quotation)`, navigate to the :menuselection:`Purchase` app, and click :guilabel:`New`." +msgid "From the drop-down menu, choose a vendor to set under the :guilabel:`Vendor` column, then set a :guilabel:`Price` and :guilabel:`Delivery Lead Time`, if necessary. Clicking the :guilabel:`(optional columns drop-down toggle)` icon, at the top right of the header row, provides additional column options to add to the line item." msgstr "" -#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/calls_for_tenders.rst:52 -#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/calls_for_tenders.rst:151 -msgid "Then, add information to the :abbr:`RFQ (Request for Quotation)` form: add a vendor from the drop-down next to the :guilabel:`Vendor` field, and click :guilabel:`Add a product` to select a product from the drop-down menu in the :guilabel:`Product` column. Then, set the desired purchase quantity in the :guilabel:`Quantity` column, and change the purchase price in the :guilabel:`Unit Price` column, if desired." +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/calls_for_tenders.rst:57 +msgid "Create an |RfQ|" msgstr "" -#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/calls_for_tenders.rst:58 -msgid "Clicking the :guilabel:`additional options (two-dots)` icon provides additional visibility options to add to the line item. Repeat these steps to add as many options as desired, including the :guilabel:`UoM` (Units of Measure) to purchase the products in, and the :guilabel:`Expected Arrival` date." +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/calls_for_tenders.rst:59 +msgid "To create a new |RfQ|, navigate to the :menuselection:`Purchase` app, and click :guilabel:`New`." msgstr "" -#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/calls_for_tenders.rst:63 -msgid "Once ready, click :guilabel:`Send by Email`. This causes a :guilabel:`Compose Email` pop-up window to appear, wherein the message to the vendor can be customized. Once ready, click :guilabel:`Send`. This turns the :abbr:`RFQ (Request for Quotation)` into a purchase order (PO), and sends an email to the vendor listed on the purchase order form." +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/calls_for_tenders.rst:61 +msgid "On the blank |RfQ| form, add a vendor from the drop-down menu, next to the :guilabel:`Vendor` field. Then, click :guilabel:`Add a product`, in the :guilabel:`Products` tab, to select a product from the drop-down menu in the :guilabel:`Product` column." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/calls_for_tenders.rst:65 +msgid "Then, set the desired quantity to purchase in the :guilabel:`Quantity` column, and change the purchase price in the :guilabel:`Unit Price` column, if necessary." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/calls_for_tenders.rst:68 +msgid "Clicking the :guilabel:`(optional columns drop-down toggle)` icon, at the top right of the header row, provides additional column options to add to the line item." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/calls_for_tenders.rst:71 +msgid "Repeat these steps to add as many column options in the :guilabel:`Products` tab as desired, including the :guilabel:`UoM` (Units of Measure) to purchase the products in, and the :guilabel:`Expected Arrival` date." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/calls_for_tenders.rst:75 +msgid "Once ready, click :guilabel:`Send by Email`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/calls_for_tenders.rst:77 +msgid "This opens a :guilabel:`Compose Email` pop-up window, wherein the message to the vendor can be customized, and attachments can be added, if needed. Once ready, click :guilabel:`Send`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/calls_for_tenders.rst:80 +msgid "This sends an email to the vendor listed on the |RfQ| form." msgstr "" #: ../../content/applications/inventory_and_mrp/purchase/manage_deals/calls_for_tenders.rst:-1 msgid "Compose and send quotation email pop-up." msgstr "" -#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/calls_for_tenders.rst:73 -msgid "Sending emails to each vendor can be useful when creating alternative :abbr:`RFQs (Requests for Quotation)`, because vendors can confirm if their past prices still hold today, which can help companies choose the best offers for them." +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/calls_for_tenders.rst:87 +msgid "Sending emails to each vendor can be useful when creating alternative |RfQs|, because vendors can confirm if their past prices still hold today, which helps companies choose the best offers." msgstr "" -#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/calls_for_tenders.rst:78 -msgid "Create alternatives to an :abbr:`RFQ (Request for Quotation)`" +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/calls_for_tenders.rst:93 +msgid "Create alternative |RfQs|" msgstr "" -#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/calls_for_tenders.rst:80 -msgid "Once a :abbr:`PO (Purchase Order)` is created and sent by email to a vendor, alternative :abbr:`RFQs (Requests for Quotation)` can be created and sent to additional, alternate vendors to compare prices, delivery times, and other factors to make a decision from which vendors to order which products." +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/calls_for_tenders.rst:95 +msgid "Once a |PO| is created and sent to a vendor, alternative |RfQs| can be created for additional vendors to compare prices, delivery times, and other factors, to help make a decision for the order." msgstr "" -#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/calls_for_tenders.rst:85 -msgid "To create alternative :abbr:`RFQs (Requests for Quotation)`, click the :guilabel:`Alternatives` tab from the purchase order form, then click :guilabel:`Create Alternative`. When clicked, a :guilabel:`Create alternative` pop-up window appears." +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/calls_for_tenders.rst:98 +msgid "To create alternative |RfQs| from the original, click the :guilabel:`Alternatives` tab. Then, click :guilabel:`Create Alternative`. When clicked, a :guilabel:`Create alternative` pop-up window appears." msgstr "" #: ../../content/applications/inventory_and_mrp/purchase/manage_deals/calls_for_tenders.rst:-1 msgid "Calls for tenders pop-up to create alternative quotation." msgstr "" -#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/calls_for_tenders.rst:93 -msgid "From this window, select a new/different vendor from the drop-down menu next to the :guilabel:`Vendor` field to assign this alternative quotation to." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/calls_for_tenders.rst:96 -msgid "Next to this, there is a :guilabel:`Copy Products` checkbox that is selected by default. When selected, the product quantities of the original :abbr:`PO (Purchase Order)` are copied to the alternative. For this first alternative quotation, leave the checkbox checked. Once finished, click :guilabel:`Create Alternative`. This creates (and navigates to) a new :abbr:`PO (Purchase Order)`." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/calls_for_tenders.rst:101 -msgid "Since the :guilabel:`Create Alternative` checkbox was left checked, this new purchase order form is already populated with the same products, quantities, and other details as the previous, original :abbr:`PO (Purchase Order)`." -msgstr "" - #: ../../content/applications/inventory_and_mrp/purchase/manage_deals/calls_for_tenders.rst:106 -msgid "When the :guilabel:`Copy Products` checkbox is selected while creating an alternative quotation, additional products do not need to be added on the purchase order form unless desired. However, if a chosen vendor is listed in the :guilabel:`Vendor` column under the :guilabel:`Purchase` tab on a product form included in the purchase order, the values set on the product form carry over to the :abbr:`PO (Purchase Order)`, and have to be changed manually, if desired." +msgid "From this window, select an alternative vendor from the drop-down menu next to the :guilabel:`Vendor` field, to whom the alternative quotation is assigned." msgstr "" -#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/calls_for_tenders.rst:112 -msgid "Once ready, create a second alternative quotation by clicking the :guilabel:`Alternatives` tab, and once again, click :guilabel:`Create Alternative`. This causes the :guilabel:`Create alternative` pop-up window to appear again. This time, choose a different vendor from the drop-down menu next to :guilabel:`Vendor`, and this time, *uncheck* the :guilabel:`Copy Products` checkbox. Then, click :guilabel:`Create Alternative`." +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/calls_for_tenders.rst:109 +msgid "Next to this, there is a :guilabel:`Copy Products` checkbox that is selected by default. When selected, the product quantities of the original |RfQ| are copied over to the alternative. For this first alternative quotation, leave the checkbox checked. Once finished, click :guilabel:`Create Alternative`. This opens a new |RfQ| form." msgstr "" -#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/calls_for_tenders.rst:119 -msgid "If an alternative quotation needs to be removed from the :guilabel:`Alternatives` tab, they can be individually removed by clicking on the :guilabel:`Remove (X)` icon at the end of their row." +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/calls_for_tenders.rst:114 +msgid "Since the :guilabel:`Create Alternative` checkbox was left checked, the new form is already pre-populated with the same products, quantities, and other details as the previous, original |RfQ|." msgstr "" -#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/calls_for_tenders.rst:122 -msgid "This creates a third, new purchase order. But, since the product quantities of the original :abbr:`PO (Purchase Order)` were *not* copied over, the product lines are empty, and new products need to be added by clicking :guilabel:`Add a product`, and selecting the desired products from the drop-down menu. Once the desired number of products are added, click :guilabel:`Send by Email`." +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/calls_for_tenders.rst:118 +msgid "When the :guilabel:`Copy Products` checkbox is selected while creating an alternative quotation, additional products do **not** need to be added, unless desired." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/calls_for_tenders.rst:121 +msgid "However, if a chosen vendor is listed in the :guilabel:`Vendor` column under a specific product form included in the order, the values set on the product form carry over to the |RfQ|, and **must** be changed manually, if necessary." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/calls_for_tenders.rst:125 +msgid "Once ready, create a second alternative quotation by clicking the :guilabel:`Alternatives` tab, followed by :guilabel:`Create Alternative`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/calls_for_tenders.rst:129 +msgid "An option to :guilabel:`Compare Product Lines` also appears. Clicking this navigates to the :guilabel:`Compare Order Lines` page, where alternative |RfQs| can be compared, side-by-side. For more information on this, refer to the :ref:`Compare Product Lines ` section." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/calls_for_tenders.rst:134 +msgid "This opens the :guilabel:`Create alternative` pop-up window. Once again, choose a different vendor from the drop-down menu next to :guilabel:`Vendor`. For this particular |RfQ|, however, *uncheck* the :guilabel:`Copy Products` checkbox. Doing so removes all products on the new alternative |RfQ|, leaving it blank. The specific products which should be ordered from this particular vendor can be added in as needed." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/calls_for_tenders.rst:140 +msgid "Once ready, click :guilabel:`Create Alternative`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/calls_for_tenders.rst:143 +msgid "If an alternative quotation should be removed from the :guilabel:`Alternatives` tab, they can be individually removed by clicking on the :guilabel:`X (remove)` icon at the end of their row." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/calls_for_tenders.rst:146 +msgid "This creates a third, new |RfQ|. But, since the product quantities of the original |RfQ| were **not** copied over, the product lines are empty, and new products can be added as needed by clicking :guilabel:`Add a product`, and selecting the desired products from the drop-down menu." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/calls_for_tenders.rst:150 +msgid "Once the desired number of specific products are added, click :guilabel:`Send by Email`." msgstr "" #: ../../content/applications/inventory_and_mrp/purchase/manage_deals/calls_for_tenders.rst:-1 msgid "Blank alternative quotation with alternatives in breadcrumbs." msgstr "" -#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/calls_for_tenders.rst:131 -msgid "This causes a :guilabel:`Compose Email` pop-up window to appear, wherein the message to the vendor can be customized. Once ready, click :guilabel:`Send` to send an email to the vendor listed on the purchase order form." +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/calls_for_tenders.rst:156 +msgid "This opens a :guilabel:`Compose Email` pop-up window, wherein the message to the vendor can be customized, and attachments can be added, if necessary. Once ready, click :guilabel:`Send`." msgstr "" -#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/calls_for_tenders.rst:135 -msgid "From this newest purchase order form, click the :guilabel:`Alternatives` tab. Under this tab, all three purchase orders can be seen in the :guilabel:`Reference` column. Additionally, the vendors are listed under the :guilabel:`Vendor` column, and the order :guilabel:`Total` and :guilabel:`Status` of the orders are in the rows, as well." +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/calls_for_tenders.rst:159 +msgid "From this newest form, click the :guilabel:`Alternatives` tab. Under this tab, all three |RfQs| can be seen in the :guilabel:`Reference` column. Additionally, the vendors are listed under the :guilabel:`Vendor` column, and the order :guilabel:`Total` (and :guilabel:`Status`) of the orders are in the rows, as well." msgstr "" -#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/calls_for_tenders.rst:141 -msgid "Link a new :abbr:`RFQ (Request for Quotation)` to existing quotations" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/calls_for_tenders.rst:143 -msgid "Creating alternative quotations directly from a purchase order form under the :guilabel:`Alternatives` tab is the easiest way to create and link quotations. However, separate :abbr:`RFQs (Requests for Quotation)` can also be linked *after* the fact, even if they are created completely separately at first." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/calls_for_tenders.rst:157 -msgid "Once ready, click :guilabel:`Send by Email`. This causes a :guilabel:`Compose Email` pop-up window to appear, wherein the message to the vendor can be customized. Once ready, click :guilabel:`Send` to send an email to the vendor listed on the purchase order form." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/calls_for_tenders.rst:161 -msgid "Then, click the :guilabel:`Alternatives` tab once more. Since this new :abbr:`PO (Purchase Order)` was created separately, there are no other orders linked yet. To link this order with the alternatives created previously, click :guilabel:`Link to Existing RfQ` on the first line in the :guilabel:`Vendor` column." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/calls_for_tenders.rst:-1 -msgid "pop-up to link new quotation to existing RFQs." +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/calls_for_tenders.rst:164 +msgid "The date in the :guilabel:`Expected Arrival` column is calculated for each vendor, based on any pre-configured lead times in the vendor and product forms." msgstr "" #: ../../content/applications/inventory_and_mrp/purchase/manage_deals/calls_for_tenders.rst:170 -msgid "This causes an :guilabel:`Add: Alternative POs` pop-up window to appear. Select the three purchase orders created previously, and click :guilabel:`Select`. All of these orders are now copied to this :abbr:`PO (Purchase Order)` under the :guilabel:`Alternatives` tab." +msgid "Link new |RfQ| to existing quotations" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/calls_for_tenders.rst:172 +msgid "Even if a quotation is not created directly from the :guilabel:`Alternatives` tab of another |RfQ|, it can still be linked to existing |RfQs|." msgstr "" #: ../../content/applications/inventory_and_mrp/purchase/manage_deals/calls_for_tenders.rst:175 -msgid "If a large number of purchase orders are being processed and the previous :abbr:`POs (Purchase Orders)` can't be located, try clicking :menuselection:`Group By --> Vendor` under the search bar at the top of the pop-up window to group by the vendors selected on the previous orders." +msgid "To do that, begin by creating a new |RfQ|. Navigate to :menuselection:`Purchase app --> New`. Fill out the |RfQ|, according to the :ref:`previous instructions `." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/calls_for_tenders.rst:178 +msgid "Then, once ready, click the :guilabel:`Alternatives` tab. Since this new |RfQ| was created separately, there are no other orders linked yet." msgstr "" #: ../../content/applications/inventory_and_mrp/purchase/manage_deals/calls_for_tenders.rst:181 -msgid "Compare product lines" +msgid "However, to link this |RfQ| with existing alternatives, click :guilabel:`Link to Existing RfQ` on the first line in the :guilabel:`Vendor` column." msgstr "" -#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/calls_for_tenders.rst:183 -msgid "When there are multiple :abbr:`RFQs (Requests for Quotation)` linked as alternatives, they can be compared side-by-side in order to determine which vendors offer the best deals on which products. To compare each quotation, go to the :menuselection:`Purchase` app, and select one of the quotations created previously." +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/calls_for_tenders.rst:-1 +msgid "Pop-up to link new quotation to existing RFQs." msgstr "" #: ../../content/applications/inventory_and_mrp/purchase/manage_deals/calls_for_tenders.rst:188 -msgid "Then, click the :guilabel:`Alternatives` tab to see all the linked :abbr:`RFQs (Requests for Quotation)`. Next, under the :guilabel:`Create Alternative` tab, click :guilabel:`Compare Product Lines`. This navigates to a Compare Order Lines page." +msgid "This opens an :guilabel:`Add: Alternative POs` pop-up window. Select the desired previously-created |RfQs|, and click :guilabel:`Select`. All of these orders are now copied to this |RfQ|, and can be found under the :guilabel:`Alternatives` tab." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/calls_for_tenders.rst:193 +msgid "If a large number of |POs| are being processed, and the previous |POs| can't be located, click the :guilabel:`⬇️ (down arrow)` icon to the right of the search bar, at the top of the pop-up window." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/calls_for_tenders.rst:197 +msgid "Then, under the :guilabel:`Group By` section, click :guilabel:`Vendor`. Vendors are displayed in their own nested drop-down lists, and each vendor's list can be expanded to view open |POs| for that vendor." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/calls_for_tenders.rst:204 +msgid "Compare product lines" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/calls_for_tenders.rst:206 +msgid "Alternative |RfQs| can be compared side-by-side, in order to determine which vendors offer the best deals on the products included in the orders." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/calls_for_tenders.rst:209 +msgid "To compare alternative |RfQs|, navigate to the :menuselection:`Purchase` app, and select one of the previously-created |RfQs|." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/calls_for_tenders.rst:212 +msgid "Then, click the :guilabel:`Alternatives` tab to see all linked |RfQs|. Next, under the :guilabel:`Create Alternative` option, click :guilabel:`Compare Product Lines`. This navigates to the :guilabel:`Compare Order Lines` page." msgstr "" #: ../../content/applications/inventory_and_mrp/purchase/manage_deals/calls_for_tenders.rst:-1 msgid "Compare Product Lines page for alternative RFQs." msgstr "" -#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/calls_for_tenders.rst:196 -msgid "The Compare Order Lines page, by default, groups by :guilabel:`Product`. Each product included in any of the :abbr:`RFQs (Requests for Quotation)` is displayed in its own drop-down, along with all of the :abbr:`PO (Purchase Order)` numbers in the :guilabel:`Reference` column." +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/calls_for_tenders.rst:220 +msgid "The :guilabel:`Compare Order Lines` page, by default, groups by :guilabel:`Product`. Each product included in any of the |RfQs| is displayed in its own nested drop-down list, and features all of the |PO| numbers in the :guilabel:`Reference` column." msgstr "" -#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/calls_for_tenders.rst:200 -msgid "Additional columns on this page include the :guilabel:`Vendor` from which products were ordered, the :guilabel:`Status` of the quotation (i.e., RFQ, RFQ Sent); the :guilabel:`Quantity` of products ordered from each vendor; the :guilabel:`Unit Price` per product and :guilabel:`Total` price of the order, and more." +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/calls_for_tenders.rst:224 +msgid "Additional columns on this page include the :guilabel:`Vendor` from which products were ordered, :guilabel:`OTD`, the :guilabel:`Reference` number, the :guilabel:`Status` of the quotation (e.g., :guilabel:`RFQ`, :guilabel:`RFQ Sent`, etc.), the product :guilabel:`Description`, the :guilabel:`Expected Arrival` date, the :guilabel:`Quantity` of products ordered from each vendor, the :guilabel:`Unit of Measure` used for each product (if any), the :guilabel:`Unit Price` per product, the :guilabel:`Total` price of the order, and the :guilabel:`Currency` applied to the order." msgstr "" -#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/calls_for_tenders.rst:206 -msgid "To remove product lines from the Compare Order Lines page, click :guilabel:`Clear` at the far right end of that product line's row. This removes this product as a chooseable option from the page, and changes the :guilabel:`Total` price of that product on the page to **0**. On the purchase order form in which that product was included, its ordered quantity is changed to **0**, as well." +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/calls_for_tenders.rst:233 +msgid "To remove product lines from the :guilabel:`Compare Order Lines` page, click :guilabel:`Clear` at the far-right end of that product line's row." msgstr "" -#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/calls_for_tenders.rst:212 -msgid "Once the best offers have been identified, at the end of each row, individual products can be selected by clicking :guilabel:`Choose`. Once all the desired products have been chosen, click :guilabel:`Requests for Quotation` (in the breadcrumbs, at the top of the page) to navigate back to an overview of all :abbr:`RFQs (Requests for Quotation)`." +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/calls_for_tenders.rst:236 +msgid "Doing so removes this specific product as a selectable option from the page, and changes the :guilabel:`Total` price of that product on the page to `0`." msgstr "" -#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/calls_for_tenders.rst:218 +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/calls_for_tenders.rst:239 +msgid "Additionally, on the |RfQ| form, in which that product was included, its ordered quantity is also changed to `0`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/calls_for_tenders.rst:242 +msgid "Once the best offers have been identified, individual products can be selected by clicking the :guilabel:`Choose` button at the end of each corresponding row." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/calls_for_tenders.rst:245 +msgid "Once all desired products have been chosen, click :guilabel:`Requests for Quotation` (in the breadcrumbs, at the top of the page) to navigate back to an overview of all |RfQs|." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/calls_for_tenders.rst:251 msgid "Cancel (or keep) alternatives" msgstr "" -#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/calls_for_tenders.rst:220 -msgid "Now that the desired products have been chosen, based on which vendors provided the best offer, the other :abbr:`RFQs (Requests for Quotation)` (from which no products were chosen) can be canceled." +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/calls_for_tenders.rst:253 +msgid "Once the desired products have been chosen from the :guilabel:`Compare Order Lines` page, the remaining |RfQs|, from which no products were chosen, can be canceled." msgstr "" -#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/calls_for_tenders.rst:223 -msgid "Under the :guilabel:`Total` column, at the far right of each row, the orders from which no products were chosen have automatically had their total cost set to **0**. Although they haven't been canceled yet, this means that they can ultimately be canceled without repercussions, *after* the desired purchase orders have been confirmed." +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/calls_for_tenders.rst:256 +msgid "The cost in the :guilabel:`Total` column for each product that wasn't chosen is automatically set to `0`, indicated at the far-right of each corresponding row." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/calls_for_tenders.rst:259 +msgid "Although they haven't been canceled yet, this indicates that each of those orders can be canceled without having an effect on the other live orders, once those orders have been confirmed." msgstr "" #: ../../content/applications/inventory_and_mrp/purchase/manage_deals/calls_for_tenders.rst:-1 msgid "Canceled quotations in the Purchase app overview." msgstr "" -#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/calls_for_tenders.rst:232 -msgid "To confirm a quotation that contains the chosen product quantities, click into one. Then, click :guilabel:`Confirm Order`. This causes an :guilabel:`Alternative Warning` pop-up window to appear. From there, either :guilabel:`Cancel Alternatives` or :guilabel:`Keep Alternatives` can be clicked. If this :abbr:`PO (Purchase Order)` should *not* be confirmed, click :guilabel:`Cancel`." +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/calls_for_tenders.rst:266 +msgid "To confirm an |RfQ| for which products were selected, click into one, and click :guilabel:`Confirm Order`." msgstr "" -#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/calls_for_tenders.rst:237 -msgid ":guilabel:`Cancel Alternatives` automatically cancels the alternative purchase orders. :guilabel:`Keep Alternatives` keeps the alternative purchase orders open, so they can still be accessed if any additional product quantities need to be ordered. Once all products are ordered, :guilabel:`Cancel Alternatives` can be selected from whichever :abbr:`PO (Purchase Order)` is open." +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/calls_for_tenders.rst:269 +msgid "This causes a pop-up window reading :guilabel:`What about the alternative Requests for Quotations?` to appear. From the pop-up window, two options are presented: :guilabel:`Cancel Alternatives` and :guilabel:`Keep Alternatives`." msgstr "" -#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/calls_for_tenders.rst:242 -msgid "To view a detailed form of one of the :abbr:`RFQs (Requests for Quotation)` listed, click the line item for that quotation. This causes an :guilabel:`Open: Alternative POs` pop-up window to appear, from which all details of that particular quotation can be viewed. Click :guilabel:`Close` when finished." +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/calls_for_tenders.rst:273 +msgid "If this |PO| should **not** be confirmed, click :guilabel:`Discard`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/calls_for_tenders.rst:275 +msgid "Selecting :guilabel:`Cancel Alternatives` automatically cancels the alternative |RfQs|. Selecting :guilabel:`Keep Alternatives` keeps the alternative |RfQs| open, so they can still be accessed, if any additional product quantities need to be ordered later." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/calls_for_tenders.rst:279 +msgid "Once all products are ordered, :guilabel:`Cancel Alternatives` can be selected from whichever |PO| is open at that time." msgstr "" #: ../../content/applications/inventory_and_mrp/purchase/manage_deals/calls_for_tenders.rst:-1 msgid "Keep or cancel pop-up for alternative RFQs." msgstr "" -#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/calls_for_tenders.rst:251 -msgid "From the :guilabel:`Alternative Warning` pop-up window, click :guilabel:`Keep Alternatives` to keep all alternative quotations open for now. Then, click :guilabel:`Requests for Quotation` (in the breadcrumbs, at the top of the page) to navigate back to an overview of all :abbr:`RFQs (Requests for Quotation)`." +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/calls_for_tenders.rst:286 +msgid "To view a detailed form of one of the |RfQs| listed, click the line item for that quotation. This opens an :guilabel:`Open: Alternative POs` pop-up window, from which all details of that particular |RfQ| can be viewed." msgstr "" -#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/calls_for_tenders.rst:256 -msgid "Click into the remaining quotation(s) that contain products that need to be ordered, and click :guilabel:`Confirm Order`. This causes the :guilabel:`Alternative Warning` pop-up window to appear again. This time, click :guilabel:`Cancel Alternatives` to cancel all other alternative :abbr:`RFQs` linked with this quotation." +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/calls_for_tenders.rst:290 +msgid "Once ready, click :guilabel:`Close` to close the pop-up window." msgstr "" -#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/calls_for_tenders.rst:261 -msgid "Finally, click :guilabel:`Requests for Quotation` (in the breadcrumbs, at the top of the page) to navigate back to an overview of all :abbr:`RFQs (Requests for Quotation)`. The canceled orders can be seen greyed out and listed with a :guilabel:`Cancelled` status under the :guilabel:`Status` column at the far right of their rows." +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/calls_for_tenders.rst:292 +msgid "If all alternative |RfQs| should stay open, from the :guilabel:`What about the alternative Requests for Quotations?` pop-up window, click :guilabel:`Keep Alternatives`." msgstr "" -#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/calls_for_tenders.rst:266 -msgid "Now that all product quantities have been ordered, the purchase process can be followed, and continued to completion, until the products are received into the warehouse." +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/calls_for_tenders.rst:295 +msgid "Then, click :guilabel:`Requests for Quotation` (in the breadcrumbs, at the top of the page) to navigate back to an overview of all |RfQs|." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/calls_for_tenders.rst:298 +msgid "Click into the remaining |RfQs| that contain products that need to be ordered, and click :guilabel:`Confirm Order`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/calls_for_tenders.rst:301 +msgid "This opens the :guilabel:`What about the alternative Requests for Quotations?` pop-up window. If desired, and the remaining alternative |RfQs| are no longer needed, click :guilabel:`Cancel Alternatives` to cancel all other alternative |RfQs| linked with this order." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/calls_for_tenders.rst:305 +msgid "Finally, click :guilabel:`Requests for Quotation` (in the breadcrumbs, at the top of the page) to navigate back to an overview of all |RfQs|." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/calls_for_tenders.rst:308 +msgid "The canceled orders can be seen, greyed out and listed with a :guilabel:`Cancelled` status, under the :guilabel:`Status` column at the far-right of their respective rows." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/calls_for_tenders.rst:311 +msgid "Now that all product quantities have been ordered, the purchase process can be completed, and the products can be received into the warehouse." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/calls_for_tenders.rst:315 +msgid ":doc:`blanket_orders`" msgstr "" #: ../../content/applications/inventory_and_mrp/purchase/manage_deals/control_bills.rst:3 @@ -15887,169 +18460,195 @@ msgstr "" msgid "Bill control policies" msgstr "" -#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/control_bills.rst:5 -msgid "In Odoo, the *bill control* policy determines the quantities billed by vendors on every purchase order, for ordered or received quantities. The policy selected in the settings will act as the default value and will be applied to any new product created." +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/control_bills.rst:10 +msgid "In Odoo's *Purchase* app, the *bill control* policy determines the quantities billed by vendors on every purchase order (PO), for either ordered or received quantities." msgstr "" -#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/control_bills.rst:12 -msgid "To view the default bill control policy and make changes, go to :menuselection:`Purchase --> Configuration --> Settings`, and scroll down to the :guilabel:`Invoicing` section. Here, there are the two :guilabel:`Bill Control` policy options: :guilabel:`Ordered quantities` and :guilabel:`Received quantities`." +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/control_bills.rst:13 +msgid "The policy selected in the *Purchase* app settings acts as the default value, and is applied to any new product created." msgstr "" -#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/control_bills.rst:17 -#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/manage.rst:28 -msgid "The policy selected will be the default for any new product created. The definition of each policy is as follows:" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/control_bills.rst:20 -#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/manage.rst:31 -msgid ":guilabel:`Ordered quantities`: creates a vendor bill as soon as a purchase order is confirmed. The products and quantities in the purchase order are used to generate a draft bill." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/control_bills.rst:22 -msgid ":guilabel:`Received quantities`: a bill is created only *after* part of the total order has been received. The products and quantities *received* are used to generate a draft bill. An error message will appear if creation of a vendor bill is attempted without receiving anything." +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/control_bills.rst:19 +msgid "To configure the *bill control* policy, navigate to :menuselection:`Purchase app --> Configuration --> Settings`, and scroll down to the :guilabel:`Invoicing` section. Under :guilabel:`Bill Control`, select either :guilabel:`Ordered quantities` or :guilabel:`Received quantities`. Then, click :guilabel:`Save`." msgstr "" #: ../../content/applications/inventory_and_mrp/purchase/manage_deals/control_bills.rst:-1 +msgid "Selected bill control policy in Purchase app settings." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/control_bills.rst:28 +msgid ":guilabel:`Ordered quantities`: creates a vendor bill as soon as a |PO| is confirmed. The products and quantities in the |PO| are used to generate a draft bill." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/control_bills.rst:30 +msgid ":guilabel:`Received quantities`: a bill is created only *after* part of the total order has been received. The products and quantities received are used to generate a draft bill. An error message appears if creation of a vendor bill is attempted without receiving anything." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/control_bills.rst:0 msgid "Bill control policy draft bill error message." msgstr "" -#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/control_bills.rst:31 -msgid "If one or two products need a different control policy, the default bill control setting can be overridden by going to the :guilabel:`Purchase` tab in a product's template and modifying its :guilabel:`Control Policy` field." +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/control_bills.rst:39 +msgid "If a specific product should use a different control policy than selected in the *Purchase* app settings, the :guilabel:`Bill Control` policy for that product can be changed from its product form." msgstr "" -#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/control_bills.rst:36 -msgid "Example flow: Ordered quantities" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/control_bills.rst:38 -msgid "To complete an example workflow using the *ordered quantities* bill control policy, first go to :menuselection:`Purchase --> Configuration --> Settings`, scroll down to the :guilabel:`Invoicing` section, and select :guilabel:`Ordered quantities`. Then, :guilabel:`Save` changes." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/control_bills.rst:42 -msgid "In the :guilabel:`Purchase` app, create a new :abbr:`RFQ (Request for Quotation)`. Fill out the information on the quotation form, add products to the invoice lines, and click :guilabel:`Confirm Order`. Then, click :guilabel:`Create Bill`. Since the policy is set to *ordered quantities*, the draft bill can be confirmed as soon as it is created, without any products actually being received." +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/control_bills.rst:43 +msgid "To do that, navigate to :menuselection:`Purchase app --> Products --> Products`, and select a product. From the product form, click the :guilabel:`Purchase` tab. Under the :guilabel:`Vendor Bills` section, modify the selection in the :guilabel:`Control Policy` field." msgstr "" #: ../../content/applications/inventory_and_mrp/purchase/manage_deals/control_bills.rst:48 -msgid "Example flow: Received quantities" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/control_bills.rst:50 -msgid "To complete an example workflow using the *received quantities* bill control policy, first go to :menuselection:`Purchase --> Configuration --> Settings`, scroll down to the :guilabel:`Invoicing` section, and select :guilabel:`Received quantities`. Then, :guilabel:`Save` changes." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/control_bills.rst:54 -msgid "In the :guilabel:`Purchase` app, create a new :abbr:`RFQ (Request for Quotation)`. Fill out the information on the quotation form, add products to the invoice lines, and click :guilabel:`Confirm Order`. Then, click on the :guilabel:`Receipt smart button`. Set the quantities in the :guilabel:`Done` column to match the quantities in the :guilabel:`Demand` column, and :guilabel:`Validate` the changes. Then, in the purchase order, click :guilabel:`Create Bill` and :guilabel:`Confirm`. Since the policy is set to *received quantities*, the draft bill can be confirmed *only* when at least some of the quantities are received." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/control_bills.rst:63 #: ../../content/applications/inventory_and_mrp/purchase/manage_deals/manage.rst:46 msgid "3-way matching" msgstr "" -#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/control_bills.rst:65 -msgid "Activating :guilabel:`3-way matching` ensures that vendor bills are only paid once some or all of the products included in the purchase order have actually been received. To activate it, go to :menuselection:`Purchase --> Configuration --> Settings`, and scroll down to the :guilabel:`Invoicing` section. Then, click :guilabel:`3-way matching: purchases, receptions, and bills`." +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/control_bills.rst:50 +msgid "The *3-way matching* feature ensures vendor bills are only paid once some (or all) of the products included in the |PO| have been received." msgstr "" -#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/control_bills.rst:72 -msgid "3-way matching is *only* intended to work when the bill control policy is set to *received quantities*." +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/control_bills.rst:53 +msgid "To activate *3-way matching*, navigate to :menuselection:`Purchase app --> Configuration --> Settings`, and scroll down to the :guilabel:`Invoicing` section. Then, tick the checkbox for :guilabel:`3-way matching` to enable the feature, and click :guilabel:`Save`." msgstr "" -#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/control_bills.rst:76 +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/control_bills.rst:-1 +msgid "Enabled 3-way matching feature in Purchase app settings." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/control_bills.rst:62 +msgid "The :guilabel:`3-way matching` feature **only** works with the :guilabel:`Bill Control` policy set to :guilabel:`Received quantities`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/control_bills.rst:66 msgid "Pay vendor bills with 3-way matching" msgstr "" -#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/control_bills.rst:78 -msgid "When :guilabel:`3-way matching` is activated, vendor bills will display the :guilabel:`Should Be Paid` field under the :guilabel:`Other Info` tab. When a new vendor bill is created, the field will be set to :guilabel:`Yes`, since a bill can't be created until at least some of the products included in a purchase order have been received." +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/control_bills.rst:68 +msgid "When *3-way matching* is enabled, vendor bills display a :guilabel:`Should Be Paid` field under the :guilabel:`Other Info` tab. When a new vendor bill is created, the field is set to :guilabel:`Yes`, since a bill **cannot** be created until at least some of the products included in a |PO| have been received." msgstr "" -#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/control_bills.rst:-1 -msgid "Draft bill should be paid field status." +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/control_bills.rst:73 +msgid "To create a vendor bill from a |PO|, navigate to :menuselection:`Purchase app --> Orders --> Purchase Orders`. From the :guilabel:`Purchase Orders` page, select the desired |PO| from the list. Then, click :guilabel:`Create Bill`. Doing so opens a new draft :guilabel:`Vendor Bill` form, in the :guilabel:`Draft` stage. Click the :guilabel:`Other Info` tab, and locate the :guilabel:`Should Be Paid` field." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/control_bills.rst:80 +msgid "The |PO| selected from the list **must not** be billed yet, or an :guilabel:`Invalid Operation` pop-up window appears. This occurs for |POs| with a :guilabel:`Received quantities` policy, and a :guilabel:`Fully Billed` :guilabel:`Billing Status`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/control_bills.rst:0 +msgid "Invalid Operation pop-up window for billed Purchase Order." msgstr "" #: ../../content/applications/inventory_and_mrp/purchase/manage_deals/control_bills.rst:88 -msgid "If the total quantity of products from a purchase order has not been received, Odoo only includes the products that *have* been received in the draft vendor bill." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/control_bills.rst:91 -msgid "Draft bills can be edited to increase the billed quantity, change the price of the products in the bill, and add additional products to the bill. If this is done, the :guilabel:`Should Be Paid` field status will be set to :guilabel:`Exception`. This means that Odoo notices the discrepancy, but doesn't block the changes or display an error message, since there might be a valid reason for making changes to the draft bill." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/control_bills.rst:97 -msgid "Once payment has been registered for a vendor bill and displays the green :guilabel:`Paid` banner, the :guilabel:`Should Be Paid` field status will be set to :guilabel:`No`." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/control_bills.rst:101 -msgid "The :guilabel:`Should Be Paid` status on bills is set automatically by Odoo. However, the status can be changed manually by clicking the field's drop-down menu inside the :guilabel:`Other Info` tab." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/control_bills.rst:106 -msgid "View a purchase order's billing status" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/control_bills.rst:108 -msgid "When a purchase order is confirmed, its :guilabel:`Billing Status` can be viewed under the :guilabel:`Other Information` tab on the purchase order form." +msgid "Click the drop-down menu next to :guilabel:`Should Be Paid` to view the available options: :guilabel:`Yes`, :guilabel:`No`, and :guilabel:`Exception`." msgstr "" #: ../../content/applications/inventory_and_mrp/purchase/manage_deals/control_bills.rst:-1 -msgid "Purchase order billing status." +msgid "Should Be Paid field status on draft vendor bill." msgstr "" -#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/control_bills.rst:115 -msgid "Below is a list of the different statuses that a :guilabel:`Billing Status` could appear as and when they are displayed, depending on the bill control policy used." +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/control_bills.rst:96 +msgid "If the total quantity of products from a |PO| has not been received, Odoo only includes the products that *have* been received in the draft vendor bill." msgstr "" -#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/control_bills.rst:119 -msgid ":guilabel:`Billing Status`" +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/control_bills.rst:99 +msgid "Draft vendor bills can be edited to increase the billed quantity, change the price of the products in the bill, and add additional products to the bill." msgstr "" -#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/control_bills.rst:119 -msgid "**Conditions**" +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/control_bills.rst:102 +msgid "If the draft bill's information is changed, the :guilabel:`Should Be Paid` field status is set to :guilabel:`Exception`. This means that Odoo notices the discrepancy, but does not block the changes or display an error message, since there might be a valid reason for making changes to the draft bill." msgstr "" -#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/control_bills.rst:121 -msgid "*On received quantities*" +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/control_bills.rst:107 +msgid "To process the vendor bill, select a date in the :guilabel:`Bill Date` field, and click :guilabel:`Confirm`, followed by :guilabel:`Register Payment`." msgstr "" -#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/control_bills.rst:121 -msgid "*On ordered quantities*" +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/control_bills.rst:110 +msgid "This opens a :guilabel:`Register Payment` pop-up window. From this window, accounting information is pre-populated based on the database's accounting settings. Click :guilabel:`Create Payment` to process the vendor bill." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/control_bills.rst:114 +msgid "Once payment has been registered for a vendor bill, and the bill displays the green :guilabel:`Paid` banner, the :guilabel:`Should Be Paid` field status is set to :guilabel:`No`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/control_bills.rst:118 +msgid "The :guilabel:`Should Be Paid` status on bills is automatically set by Odoo. However, the status can be manually changed by clicking the field's drop-down menu inside the :guilabel:`Other Info` tab." msgstr "" #: ../../content/applications/inventory_and_mrp/purchase/manage_deals/control_bills.rst:123 -msgid ":guilabel:`Nothing to Bill`" +msgid "View a purchase order's billing status" msgstr "" -#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/control_bills.rst:123 +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/control_bills.rst:125 +msgid "Once a |PO| is confirmed, its :guilabel:`Billing Status` can be viewed under the :guilabel:`Other Information` tab on the |PO| form." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/control_bills.rst:128 +msgid "To view the :guilabel:`Billing Status` of a |PO|, navigate to :menuselection:`Purchase app --> Orders --> Purchase Orders`, and select a |PO| to view." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/control_bills.rst:131 +msgid "Click the :guilabel:`Other Information` tab, and locate the :guilabel:`Billing Status` field." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/control_bills.rst:-1 +msgid "Billing status field on a purchase order form." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/control_bills.rst:137 +msgid "The table below details the different values the :guilabel:`Billing Status` field could read, and when they are displayed, depending on the *Bill Control* policy used." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/control_bills.rst:144 +msgid "Billing Status" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/control_bills.rst:145 +msgid "On received quantities" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/control_bills.rst:146 +msgid "On ordered quantities" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/control_bills.rst:147 +msgid "Nothing to Bill" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/control_bills.rst:148 msgid "PO confirmed; no products received" msgstr "" -#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/control_bills.rst:123 +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/control_bills.rst:149 msgid "*Not applicable*" msgstr "" -#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/control_bills.rst:125 -msgid ":guilabel:`Waiting Bills`" +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/control_bills.rst:150 +msgid "Waiting Bills" msgstr "" -#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/control_bills.rst:125 +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/control_bills.rst:151 msgid "All/some products received; bill not created" msgstr "" -#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/control_bills.rst:125 +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/control_bills.rst:152 msgid "PO confirmed" msgstr "" -#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/control_bills.rst:127 -msgid ":guilabel:`Fully Billed`" +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/control_bills.rst:153 +msgid "Fully Billed" msgstr "" -#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/control_bills.rst:127 +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/control_bills.rst:154 msgid "All/some products received; draft bill created" msgstr "" -#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/control_bills.rst:127 +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/control_bills.rst:155 msgid "Draft bill created" msgstr "" +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/control_bills.rst:158 +msgid ":doc:`manage`" +msgstr "" + #: ../../content/applications/inventory_and_mrp/purchase/manage_deals/manage.rst:3 msgid "Manage vendor bills" msgstr "" @@ -16074,6 +18673,14 @@ msgstr "" msgid "Bill control policies in purchase app settings." msgstr "" +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/manage.rst:28 +msgid "The policy selected will be the default for any new product created. The definition of each policy is as follows:" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/purchase/manage_deals/manage.rst:31 +msgid ":guilabel:`Ordered quantities`: creates a vendor bill as soon as a purchase order is confirmed. The products and quantities in the purchase order are used to generate a draft bill." +msgstr "" + #: ../../content/applications/inventory_and_mrp/purchase/manage_deals/manage.rst:33 msgid ":guilabel:`Received quantities`: a bill is only created **after** part of the total order has been received. The products and quantities **received** are used to generate a draft bill." msgstr "" @@ -16673,16 +19280,16 @@ msgstr "" msgid "Set a product's units of measure using your own units in Odoo Purchase" msgstr "" -#: ../../content/applications/inventory_and_mrp/quality.rst:8 +#: ../../content/applications/inventory_and_mrp/quality.rst:7 msgid "Quality" msgstr "" -#: ../../content/applications/inventory_and_mrp/quality.rst:10 +#: ../../content/applications/inventory_and_mrp/quality.rst:9 msgid "**Odoo Quality** helps ensure product quality throughout manufacturing processes and inventory movements. Conduct quality checks, automate quality inspection frequency, and create quality alerts when issues arise." msgstr "" -#: ../../content/applications/inventory_and_mrp/quality.rst:15 -msgid "`Odoo Tutorials: Managing Quality Checks `_" +#: ../../content/applications/inventory_and_mrp/quality.rst:14 +msgid "`Odoo Tutorials: Quality Overview `_" msgstr "" #: ../../content/applications/inventory_and_mrp/quality/quality_check_types.rst:5 @@ -17704,3 +20311,323 @@ msgstr "" #: ../../content/applications/inventory_and_mrp/quality/quality_management/quality_control_points.rst:-1 msgid "A QCP configured to create Pass - Fail checks for a work order operation." msgstr "" + +#: ../../content/applications/inventory_and_mrp/repairs.rst:8 +msgid "Repairs" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/repairs.rst:10 +msgid "Odoo *Repairs* assists companies in creating and processing repairs for damaged products returned by customers." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/repairs/repair_orders.rst:3 +msgid "Process repair orders" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/repairs/repair_orders.rst:10 +msgid "Sometimes, products delivered to customers can break or be damaged in transit, and need to be returned for a refund, delivery of a replacement product, or repairs." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/repairs/repair_orders.rst:13 +msgid "In Odoo, repairs for products returned by customers can be tracked in the *Repairs* app. Once repaired, products can be redelivered to the customer." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/repairs/repair_orders.rst:16 +msgid "The return and repair process for damaged products typically follows the below steps:" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/repairs/repair_orders.rst:18 +msgid ":ref:`Process return order for damaged product `" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/repairs/repair_orders.rst:19 +msgid ":ref:`Create repair order for returned product `" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/repairs/repair_orders.rst:20 +msgid ":ref:`Return repaired product to customer `" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/repairs/repair_orders.rst:25 +msgid "Return order" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/repairs/repair_orders.rst:27 +msgid "Returns can be processed in Odoo via *reverse transfers*, created directly from a sales order (SO) once products have been delivered to a customer." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/repairs/repair_orders.rst:30 +msgid "To create a return, navigate to the :menuselection:`Sales app`, and click into an |SO| from which a product should be returned. Then, from the |SO| form, click the :guilabel:`Delivery` smart button. Doing so opens the delivery order (DO) form." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/repairs/repair_orders.rst:34 +msgid "From this form, click :guilabel:`Return`. This opens a :guilabel:`Reverse Transfer` pop-up window." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/repairs/repair_orders.rst:-1 +#: ../../content/applications/inventory_and_mrp/repairs/repair_orders.rst:-1 +msgid "Reverse transfer pop-up window on delivery order form." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/repairs/repair_orders.rst:40 +#: ../../content/applications/inventory_and_mrp/repairs/repair_orders.rst:253 +msgid "This pop-up lists the :guilabel:`Product` included in the order, the :guilabel:`Quantity` delivered to the customer, and the :guilabel:`Unit of Measure` the product was in." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/repairs/repair_orders.rst:43 +#: ../../content/applications/inventory_and_mrp/repairs/repair_orders.rst:256 +msgid "Click the value in the :guilabel:`Quantity` field to change the quantity of the product to be returned, if necessary." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/repairs/repair_orders.rst:46 +#: ../../content/applications/inventory_and_mrp/repairs/repair_orders.rst:259 +msgid "Click the :guilabel:`🗑️ (trash)` icon at the far-right of the product line to remove it from the return, if necessary." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/repairs/repair_orders.rst:49 +msgid "Once ready, click :guilabel:`Return` to confirm the return. This creates a new receipt for the returned products." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/repairs/repair_orders.rst:52 +msgid "Once the product has been returned to the warehouse, receipt of the return can be registered in the database by clicking :guilabel:`Validate` from the reverse transfer form." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/repairs/repair_orders.rst:56 +msgid "Once a reverse transfer for a return is validated, the value in the :guilabel:`Delivered` column on the original |SO| updates to reflect the difference between the original :guilabel:`Quantity` ordered, and the :guilabel:`Quantity` returned by the customer." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/repairs/repair_orders.rst:0 +msgid "Delivered and Quantity columns on sales order after return." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/repairs/repair_orders.rst:67 +msgid "Create repair order" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/repairs/repair_orders.rst:69 +msgid "Once products have been returned, their repairs can be tracked by creating a repair order (RO)." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/repairs/repair_orders.rst:71 +msgid "To create a new |RO|, navigate to :menuselection:`Repairs app`, and click :guilabel:`New`. This opens a blank |RO| form." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/repairs/repair_orders.rst:-1 +msgid "Left-hand side of blank repair order form." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/repairs/repair_orders.rst:78 +msgid "On this form, begin by selecting a :guilabel:`Customer`. The customer selected should be for whom the order will be invoiced and delivered." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/repairs/repair_orders.rst:81 +msgid "In the :guilabel:`Product to Repair` field, click the drop-down menu to select the product that needs repair. If necessary, click :guilabel:`Search More...` to open a :guilabel:`Search: Product to Repair` pop-up window, and browse all products in the database." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/repairs/repair_orders.rst:85 +msgid "Once a :guilabel:`Product to Repair` is selected, a new :guilabel:`Product Quantity` field appears below it. In that field, enter the quantity (in a `0.00` format) of the product that requires repair." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/repairs/repair_orders.rst:89 +msgid "To the right of that value, click the drop-down list to select the unit of measure (UoM) for the product." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/repairs/repair_orders.rst:92 +msgid "In the :guilabel:`Return` field, click the drop-down menu and select the return order from which the product to be repaired comes from." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/repairs/repair_orders.rst:95 +msgid "Tick the :guilabel:`Under Warranty` checkbox, if the product being repaired is covered by a warranty. If ticked, the :guilabel:`Customer` is not charged for all the parts used in the repair order." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/repairs/repair_orders.rst:99 +msgid "In the :guilabel:`Scheduled Date` field, click the date to reveal a calendar popover window. From this calendar, select a date for the repair, and click :guilabel:`Apply`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/repairs/repair_orders.rst:-1 +msgid "Right-hand side of blank repair order form." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/repairs/repair_orders.rst:106 +msgid "In the :guilabel:`Responsible` field, click the drop-down menu and select the user who should be responsible for the repair." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/repairs/repair_orders.rst:109 +msgid "In the :guilabel:`Company` field, if in a multi-company environment, select which company this |RO| belongs to." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/repairs/repair_orders.rst:112 +msgid "In the :guilabel:`Tags` field, click the drop-down menu and select which tags should be applied to this |RO|." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/repairs/repair_orders.rst:116 +msgid "Parts tab" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/repairs/repair_orders.rst:118 +msgid "Add, remove, or recycle parts in the :guilabel:`Parts` tab. To do so, click :guilabel:`Add a line` at the bottom of the form." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/repairs/repair_orders.rst:121 +msgid "In the :guilabel:`Type` column, click the box to reveal three options to choose from: :guilabel:`Add` (selected by default), :guilabel:`Remove`, and :guilabel:`Recycle`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/repairs/repair_orders.rst:-1 +msgid "Type column options or new part under Parts tab." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/repairs/repair_orders.rst:128 +msgid "Choosing :guilabel:`Add` adds this part to the |RO|. Adding parts lists components for use in the repair. If the components are used, the user completing the repair can record they were used. If they were not used, the user can indicate that, too, and the components can be saved for another use." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/repairs/repair_orders.rst:133 +msgid "Choosing :guilabel:`Remove` removes this part from the |RO|. Removing parts lists components that should be removed from the product being repaired during the repair process. If the parts are removed, the user completing the repair can indicate they were removed." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/repairs/repair_orders.rst:137 +msgid "Choosing :guilabel:`Recycle` recycles this part from the |RO|, designating it for later use or to be repurposed for another use in the warehouse." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/repairs/repair_orders.rst:140 +msgid "In the :guilabel:`Product` column, select which product (part) should be added, removed, or recycled. In the :guilabel:`Demand` column, change the quantity, if necessary, to indicate what quantity of this part should be used in the repair process." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/repairs/repair_orders.rst:144 +msgid "In the :guilabel:`Done` column, change the value (in a `0.00` format) once the part has been successfully added, removed, or recycled." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/repairs/repair_orders.rst:147 +msgid "In the :guilabel:`Unit of Measure` column, select the |UoM| for the part." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/repairs/repair_orders.rst:149 +msgid "Finally, in the :guilabel:`Used` column, tick the checkbox once the part has been used in the repair process." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/repairs/repair_orders.rst:152 +msgid "To add additional columns to the line, click the :guilabel:`(optional columns drop-down)` icon, at the far-right of the header row. Select the desired options to add to the line." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/repairs/repair_orders.rst:-1 +msgid "Optional additional options to add to new part line." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/repairs/repair_orders.rst:160 +msgid "Repair Notes and Miscellaneous tabs" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/repairs/repair_orders.rst:162 +msgid "Click the :guilabel:`Repair Notes` tab to add internal notes about this specific |RO|, and anything the user performing the repair might need to know." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/repairs/repair_orders.rst:165 +msgid "Click the blank text field to begin writing notes." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/repairs/repair_orders.rst:167 +msgid "Click the :guilabel:`Miscellaneous` tab to see the :guilabel:`Operation Type` for this repair. By default, this is set to :guilabel:`YourCompany: Repairs`, indicating this is a repair type operation." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/repairs/repair_orders.rst:171 +msgid "Once all desired configurations have been made on the |RO| form, click :guilabel:`Confirm Repair`. This moves the |RO| to the :guilabel:`Confirmed` stage, and reserves the necessary components needed for the repair." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/repairs/repair_orders.rst:175 +msgid "A new :guilabel:`Forecasted` column appears on the product lines under the :guilabel:`Parts` tab, displaying the availability of all components needed for the repair." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/repairs/repair_orders.rst:178 +msgid "Once ready, click :guilabel:`Start Repair`. This moves the |RO| to the :guilabel:`Under Repair` stage (in the upper-right corner). If the |RO| should be canceled, click :guilabel:`Cancel Repair`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/repairs/repair_orders.rst:181 +msgid "Once all products have been successfully repaired, the |RO| is completed. To register this in the database, click :guilabel:`End Repair`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/repairs/repair_orders.rst:185 +msgid "If all parts added to the |RO| were not used, clicking :guilabel:`End Repair` causes an :guilabel:`Uncomplete Move(s)` pop-up window to appear." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/repairs/repair_orders.rst:-1 +msgid "Uncomplete Moves pop-up window for unused parts." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/repairs/repair_orders.rst:192 +msgid "The pop-up window informs the user that there is a difference between the initial demand and the actual quantity used for the order." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/repairs/repair_orders.rst:195 +msgid "If the :guilabel:`Used` quantity should be changed, click :guilabel:`Discard` or close the pop-up window. If the order should be confirmed, click :guilabel:`Validate`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/repairs/repair_orders.rst:198 +msgid "This moves the |RO| to the :guilabel:`Repaired` stage. A :guilabel:`Product Moves` smart button also appears above the form." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/repairs/repair_orders.rst:201 +msgid "Click the :guilabel:`Product Moves` smart button to view the product's moves history during and after the repair process." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/repairs/repair_orders.rst:-1 +msgid "Moves history of product included in the repair order." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/repairs/repair_orders.rst:211 +msgid "Return product to customer" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/repairs/repair_orders.rst:214 +msgid "Product is under warranty" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/repairs/repair_orders.rst:216 +msgid "Once the product has been successfully repaired, it can be returned to the customer." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/repairs/repair_orders.rst:219 +msgid "Product is not under warranty" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/repairs/repair_orders.rst:221 +msgid "If the product is not under warranty, or should the customer bear the repair costs, click :guilabel:`Create Quotation`. This opens a new |SO| form, pre-populated with the parts used in the |RO|, with the total cost of the repair calculated." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/repairs/repair_orders.rst:-1 +msgid "Pre-populated new quotation for parts included in repair order." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/repairs/repair_orders.rst:229 +msgid "If this |SO| should be sent to the customer, click :guilabel:`Confirm`, and proceed to invoice the customer for the repair." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/repairs/repair_orders.rst:233 +msgid "If the customer should be charged for a repair service, a service type product can be created and added to the |SO| for a repaired product." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/repairs/repair_orders.rst:236 +msgid "To return the product to the customer, navigate to the :menuselection:`Sales app`, and select the original |SO| from which the initial return was processed. Then, click the :guilabel:`Delivery` smart button." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/repairs/repair_orders.rst:240 +msgid "From the resulting list of operations, click the reverse transfer, indicated by the :guilabel:`Source Document`, which should read `Return of WH/OUT/XXXXX`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/repairs/repair_orders.rst:243 +msgid "This opens the return form. At the top of this form, a :guilabel:`Repair Orders` smart button now appears, linking this return to the completed |RO|." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/repairs/repair_orders.rst:246 +msgid "Click :guilabel:`Return` at the top of the form. This opens a :guilabel:`Reverse Transfer` pop-up window." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/repairs/repair_orders.rst:262 +msgid "Once ready, click :guilabel:`Return` to confirm the return. This creates a new delivery for the returned products." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/repairs/repair_orders.rst:265 +msgid "When the delivery has been processed and the product has been returned to the customer, click :guilabel:`Validate` to validate the delivery." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/repairs/repair_orders.rst:269 +msgid ":doc:`../../sales/sales/products_prices/returns`" +msgstr "" diff --git a/locale/sources/marketing.pot b/locale/sources/marketing.pot index 51694c5fd..5d3457116 100644 --- a/locale/sources/marketing.pot +++ b/locale/sources/marketing.pot @@ -8,7 +8,7 @@ msgid "" msgstr "" "Project-Id-Version: Odoo 17.0\n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2024-03-25 16:01+0000\n" +"POT-Creation-Date: 2024-04-30 09:16+0000\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME \n" "Language-Team: LANGUAGE \n" @@ -20,531 +20,1437 @@ msgstr "" msgid "Marketing" msgstr "" -#: ../../content/applications/marketing/email_marketing.rst:6 -msgid "Email marketing" +#: ../../content/applications/marketing/email_marketing.rst:5 +msgid "Email Marketing" msgstr "" -#: ../../content/applications/marketing/email_marketing.rst:8 -msgid "Emails are an effective, fully-customizable form of communication that are able to reach any target audience - large or small. The success of an email is easily measurable, especially when a creative call-to-action is involved." +#: ../../content/applications/marketing/email_marketing.rst:7 +msgid "The Odoo *Email Marketing* app provides drag-and-drop design tools, pre-built templates, and other interactive features to create engaging email campaigns. The *Email Marketing* app also provides| detailed reporting metrics to track the campaigns' overall effectiveness." msgstr "" #: ../../content/applications/marketing/email_marketing.rst:12 -msgid "Odoo *Email Marketing* provides professional-grade email design tools, templates, and features, designed to simplify the otherwise complex process required to create engaging emails, build successful campaigns, and track their overall effectiveness in a single application." +msgid "`Odoo Tutorial: Email Marketing `_" msgstr "" -#: ../../content/applications/marketing/email_marketing.rst:17 -#: ../../content/applications/marketing/email_marketing.rst:219 -msgid ":doc:`/applications/marketing/email_marketing/mailing_lists`" -msgstr "" - -#: ../../content/applications/marketing/email_marketing.rst:18 -msgid ":doc:`/applications/marketing/email_marketing/unsubscriptions`" -msgstr "" - -#: ../../content/applications/marketing/email_marketing.rst:21 +#: ../../content/applications/marketing/email_marketing.rst:35 msgid "Email marketing dashboard" msgstr "" -#: ../../content/applications/marketing/email_marketing.rst:23 -msgid "To get started, click on the :menuselection:`Email Marketing` app icon, located on the main Odoo dashboard, which leads to the main :guilabel:`Email Marketing` dashboard (in the default kanban view)." -msgstr "" - -#: ../../content/applications/marketing/email_marketing.rst:27 -msgid "To see all the mailings in the database, remove the default :guilabel:`My Mailings` filter from the search bar." +#: ../../content/applications/marketing/email_marketing.rst:37 +msgid "After installing the application, click the :menuselection:`Email Marketing` app icon from the main Odoo dashboard. Doing so reveals the main :guilabel:`Mailings` dashboard in the default list view." msgstr "" #: ../../content/applications/marketing/email_marketing.rst:-1 msgid "View of the main dashboard of the Odoo Email Marketing application." msgstr "" -#: ../../content/applications/marketing/email_marketing.rst:35 -msgid "In the search bar, by default, the filter: :guilabel:`My Mailings` is present. That means the only information being seen (at that time) on the :guilabel:`Email Marketing` dashboard are emails that the current user has created, sent, or is responsible for." -msgstr "" - -#: ../../content/applications/marketing/email_marketing.rst:39 -msgid "This filter can be removed by clicking the :guilabel:`X` next to :guilabel:`My Mailings` in the search bar. Doing so, reveals all the information for every email in the database." -msgstr "" - -#: ../../content/applications/marketing/email_marketing.rst:43 -msgid "Default kanban view and stages" -msgstr "" - -#: ../../content/applications/marketing/email_marketing.rst:45 -msgid "The four kanban columns each represent the various stages of emails that have been built or sent within the *Email Marketing* application." +#: ../../content/applications/marketing/email_marketing.rst:44 +msgid "In the search bar, the default filter of :guilabel:`My Mailings` is present to show all the mailings related to the current user. To remove that filter, click the :guilabel:`✖️ (remove)` icon next to the filter in the search bar. Doing so reveals all the mailings in the database." msgstr "" #: ../../content/applications/marketing/email_marketing.rst:48 -msgid "The stages are: :guilabel:`Draft`, :guilabel:`In Queue`, :guilabel:`Sending`, :guilabel:`Sent`." -msgstr "" - -#: ../../content/applications/marketing/email_marketing.rst:50 -msgid ":guilabel:`Draft`: means the email is still being written/created." +msgid "The information on the :guilabel:`Mailings` dashboard has four different view options, located in the upper-right corner as individual icons." msgstr "" #: ../../content/applications/marketing/email_marketing.rst:51 -msgid ":guilabel:`In Queue`: means the email is scheduled, and sent at a later date." -msgstr "" - -#: ../../content/applications/marketing/email_marketing.rst:52 -msgid ":guilabel:`Sending`: means the email is currently being sent to its recipients." +msgid "The view options, from left-to-right, are:" msgstr "" #: ../../content/applications/marketing/email_marketing.rst:53 -msgid ":guilabel:`Sent`: means the email has already been sent to its recipients." +msgid ":ref:`List ` (default view)" +msgstr "" + +#: ../../content/applications/marketing/email_marketing.rst:54 +msgid ":ref:`Kanban `" msgstr "" #: ../../content/applications/marketing/email_marketing.rst:55 -msgid "In each stage, there are drag-and-drop cards representing the email campaigns that have been created, and the stage they are in represents the current status of that mailing." +msgid ":ref:`Calendar `" msgstr "" -#: ../../content/applications/marketing/email_marketing.rst:58 -msgid "Each mailing block on the :guilabel:`Email Marketing` dashboard provides key information related to that specific email." +#: ../../content/applications/marketing/email_marketing.rst:56 +msgid ":ref:`Graph `" msgstr "" #: ../../content/applications/marketing/email_marketing.rst:61 -msgid "When the cursor hovers over the upper-right corner of an email campaign card, three vertical dots (:guilabel:`⋮`) appear. When clicked, a mini drop-down menu reveals the option to color-code the email :guilabel:`Delete` the email altogether, or :guilabel:`Archive` the message for potential future use." +#: ../../content/applications/marketing/email_marketing.rst:733 +#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:420 +#: ../../content/applications/marketing/surveys.rst:145 +msgid "List view" +msgstr "" + +#: ../../content/applications/marketing/email_marketing.rst:63 +msgid "The list view, represented by the :guilabel:`☰ (horizontal lines)` icon in the upper-right corner, is the default view of the :guilabel:`Mailings` dashboard in the :guilabel:`Email Marketing` app." +msgstr "" + +#: ../../content/applications/marketing/email_marketing.rst:66 +msgid "While in list view, there are columns dedicated to different aspects of information related to the listed emails. Those columns are as follows:" +msgstr "" + +#: ../../content/applications/marketing/email_marketing.rst:69 +msgid ":guilabel:`Date`: the date the email was sent." +msgstr "" + +#: ../../content/applications/marketing/email_marketing.rst:70 +msgid ":guilabel:`Subject`: the subject of the email." +msgstr "" + +#: ../../content/applications/marketing/email_marketing.rst:71 +msgid ":guilabel:`Responsible`: the user who created the email, or the user who has been assigned to the email." +msgstr "" + +#: ../../content/applications/marketing/email_marketing.rst:73 +msgid ":guilabel:`Sent`: how many times the email has been sent." +msgstr "" + +#: ../../content/applications/marketing/email_marketing.rst:74 +msgid ":guilabel:`Delivered (%)`: percentage of sent emails that have been successfully delivered." +msgstr "" + +#: ../../content/applications/marketing/email_marketing.rst:75 +msgid ":guilabel:`Opened (%)`: percentage of sent emails that have been opened by the recipients." +msgstr "" + +#: ../../content/applications/marketing/email_marketing.rst:76 +msgid ":guilabel:`Clicked (%)`: percentage of sent emails that have been clicked by the recipients." +msgstr "" + +#: ../../content/applications/marketing/email_marketing.rst:77 +msgid ":guilabel:`Replied (%)`: percentage of sent emails that have been replied to by the recipients." +msgstr "" + +#: ../../content/applications/marketing/email_marketing.rst:78 +msgid ":guilabel:`Status`: the status of the email (:guilabel:`Draft`, :guilabel:`In Queue`, or :guilabel:`Sent`)." +msgstr "" + +#: ../../content/applications/marketing/email_marketing.rst:81 +msgid "To add or remove columns, click the :guilabel:`Additional Options (two horizontal lines with dots)` icon, located to the far-right of the column titles in list view. Doing so reveals a drop-down menu of additional column options." +msgstr "" + +#: ../../content/applications/marketing/email_marketing.rst:88 +#: ../../content/applications/marketing/email_marketing.rst:706 +#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:391 +msgid "Kanban view" +msgstr "" + +#: ../../content/applications/marketing/email_marketing.rst:90 +msgid "The Kanban view, represented by the :guilabel:`(inverted bar graph)` icon, can be accessed in the upper-right corner of the :guilabel:`Mailings` dashboard in the :guilabel:`Email Marketing` app." +msgstr "" + +#: ../../content/applications/marketing/email_marketing.rst:-1 +msgid "Kanban view of the main dashboard of the Odoo Email Marketing application." +msgstr "" + +#: ../../content/applications/marketing/email_marketing.rst:97 +msgid "While in Kanban view, the email information is displayed in the various stages." +msgstr "" + +#: ../../content/applications/marketing/email_marketing.rst:99 +msgid "The stages are: :guilabel:`Draft`, :guilabel:`In Queue`, :guilabel:`Sending`, and :guilabel:`Sent`." +msgstr "" + +#: ../../content/applications/marketing/email_marketing.rst:101 +msgid ":guilabel:`Draft`: the email is still being written/created." +msgstr "" + +#: ../../content/applications/marketing/email_marketing.rst:102 +msgid ":guilabel:`In Queue`: the email is scheduled to be sent at a later date." +msgstr "" + +#: ../../content/applications/marketing/email_marketing.rst:103 +msgid ":guilabel:`Sending`: the email is currently being sent to its recipients." +msgstr "" + +#: ../../content/applications/marketing/email_marketing.rst:104 +msgid ":guilabel:`Sent`: the email has already been sent to its recipients." +msgstr "" + +#: ../../content/applications/marketing/email_marketing.rst:106 +msgid "In each stage, there are drag-and-drop cards representing the emails that have been created/sent, and the stage they are in represents the current status of that mailing." +msgstr "" + +#: ../../content/applications/marketing/email_marketing.rst:109 +msgid "Each card on the :guilabel:`Mailings` dashboard provides key information related to that specific email." +msgstr "" + +#: ../../content/applications/marketing/email_marketing.rst:112 +msgid "When the cursor hovers over the upper-right corner of an email campaign card, a :guilabel:`⋮ (three vertical dots)` icon appears. When clicked, a mini drop-down menu reveals the option to color-code the email, :guilabel:`Delete` the email, or :guilabel:`Archive` the message for potential future use." msgstr "" #: ../../content/applications/marketing/email_marketing.rst:-1 msgid "View of the three-dot drop-down menu on the Odoo Email Marketing dashboard." msgstr "" -#: ../../content/applications/marketing/email_marketing.rst:70 -msgid "In the upper-right corner of the main :guilabel:`Email Marketing` dashboard, there are other view options to choose from: :guilabel:`List` and :guilabel:`Graph`." +#: ../../content/applications/marketing/email_marketing.rst:124 +#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:404 +msgid "Calendar view" msgstr "" -#: ../../content/applications/marketing/email_marketing.rst:74 -#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:420 -msgid "List view" +#: ../../content/applications/marketing/email_marketing.rst:126 +msgid "The calendar view, represented by a :guilabel:`📆 (calendar)` icon, can be accessed in the upper-right corner of the :guilabel:`Mailings` dashboard in the :guilabel:`Email Marketing` app." msgstr "" -#: ../../content/applications/marketing/email_marketing.rst:76 -msgid "The :guilabel:`List` view (represented by the :guilabel:`☰ (three vertical lines)` icon) provides the same key information, but in a classic list format." +#: ../../content/applications/marketing/email_marketing.rst:129 +msgid "While in calendar view, a monthly calendar (by default), shows when the mailings have been sent or are scheduled to be sent." msgstr "" #: ../../content/applications/marketing/email_marketing.rst:-1 -msgid "How the List view appears in the Odoo Email Marketing application." +msgid "Calendar view of the mailings dashboard in the Email Marketing application." msgstr "" -#: ../../content/applications/marketing/email_marketing.rst:84 +#: ../../content/applications/marketing/email_marketing.rst:136 +msgid "The current date is represented by a :guilabel:`🔴 (red circle)` icon over the date on the calendar." +msgstr "" + +#: ../../content/applications/marketing/email_marketing.rst:138 +msgid "To the right of the calendar, the options to filter the results by :guilabel:`Responsible` and/or :guilabel:`Status` are available, via checkboxes." +msgstr "" + +#: ../../content/applications/marketing/email_marketing.rst:142 +msgid "To hide the right sidebar, click the :guilabel:`(panel-right)` icon, located above the sidebar." +msgstr "" + +#: ../../content/applications/marketing/email_marketing.rst:144 +msgid "In the top-left corner, above the calendar, the option to change the time period being displayed is available via a drop-down menu, which shows :guilabel:`Month`, by default. When clicked, the drop-down menu that appears reveals the options: :guilabel:`Day`, :guilabel:`Week`, :guilabel:`Month` (default), :guilabel:`Year`, and :guilabel:`Show weekends` (selected by default)." +msgstr "" + +#: ../../content/applications/marketing/email_marketing.rst:149 +msgid "Clicking any of those options changes the calendar display to reflect that desired amount of time." +msgstr "" + +#: ../../content/applications/marketing/email_marketing.rst:151 +msgid "Clicking either :guilabel:`⬅️ (left arrow)` icon or :guilabel:`➡️ (right arrow)` icon changes the calendar to a previous or future time, depending on what is clicked, based on the chosen amount of time being represented." +msgstr "" + +#: ../../content/applications/marketing/email_marketing.rst:155 +msgid "To jump back to the current date, click the :guilabel:`Today` button." +msgstr "" + +#: ../../content/applications/marketing/email_marketing.rst:160 msgid "Graph view" msgstr "" -#: ../../content/applications/marketing/email_marketing.rst:86 -msgid "The :guilabel:`Graph` view (represented by the :guilabel:`📊 (bar graph)` icon) provides the same key information, but in a variety of customizable graph (and chart) layouts." +#: ../../content/applications/marketing/email_marketing.rst:162 +msgid "The graph view, represented by a :guilabel:`(line graph)` icon, can be accessed in the upper-right corner of the :guilabel:`Mailings` dashboard in the :guilabel:`Email Marketing` app." +msgstr "" + +#: ../../content/applications/marketing/email_marketing.rst:165 +msgid "While in graph view, the status of the emails on the :guilabel:`Mailings` page is represented in a bar graph, but other graph view options can be implemented, if needed." msgstr "" #: ../../content/applications/marketing/email_marketing.rst:-1 msgid "How the Graph view appears in the Odoo Email Marketing application." msgstr "" -#: ../../content/applications/marketing/email_marketing.rst:93 -msgid "In the upper-left corner, there is a :guilabel:`Measures` menu, providing even more filter options to further customize the graph views." +#: ../../content/applications/marketing/email_marketing.rst:172 +msgid "In the upper-left corner, above the graph, there is a :guilabel:`Measures` drop-down menu. When clicked, different filter options become available to further customize the graph views." msgstr "" -#: ../../content/applications/marketing/email_marketing.rst:96 -msgid "Those :guilabel:`Measures` options are: :guilabel:`A/B Testing percentage`, :guilabel:`Color Index`, and :guilabel:`Count` (which is selected, by default)." +#: ../../content/applications/marketing/email_marketing.rst:175 +msgid "Those :guilabel:`Measures` options are: :guilabel:`A/B Testing percentage` and :guilabel:`Count` (default)." msgstr "" -#: ../../content/applications/marketing/email_marketing.rst:100 -msgid "Filters, Group By, and Favorites search options" +#: ../../content/applications/marketing/email_marketing.rst:178 +msgid "To the right of the :guilabel:`Measures` drop-down menu is an :guilabel:`Insert in Spreadsheet` button, if the *Documents* application is installed. When clicked, a pop-up window appears, in which the ability to add the graph to a spreadsheet or dashboard becomes available." msgstr "" -#: ../../content/applications/marketing/email_marketing.rst:102 -msgid "Regardless of the view chosen for the :guilabel:`Email Marketing` dashboard, the :guilabel:`Filters`, :guilabel:`Group by`, and :guilabel:`Favorites` options are always available." +#: ../../content/applications/marketing/email_marketing.rst:182 +msgid "Beside the :guilabel:`Measures` drop-down menu and :guilabel:`Insert in Spreadsheet` button are different graph view options. From left-to-right, those graph view options are: :guilabel:`(bar chart)` (default), :guilabel:`(line chart)`, and :guilabel:`(pie chart)`." msgstr "" -#: ../../content/applications/marketing/email_marketing.rst:105 -msgid "These options provide various ways to specify and organize the information seen on the :guilabel:`Email Marketing` dashboard." +#: ../../content/applications/marketing/email_marketing.rst:187 +msgid "Each graph view option provides its own series of additional view options, which appear to the right of the selected graph view option." msgstr "" -#: ../../content/applications/marketing/email_marketing.rst:110 +#: ../../content/applications/marketing/email_marketing.rst:191 +msgid "Search options" +msgstr "" + +#: ../../content/applications/marketing/email_marketing.rst:193 +msgid "Regardless of the view chosen for the :guilabel:`Mailings` dashboard in the :guilabel:`Email Marketing` app, the :guilabel:`Filters`, :guilabel:`Group by`, and :guilabel:`Favorites` options are always available to further customize the information being displayed." +msgstr "" + +#: ../../content/applications/marketing/email_marketing.rst:197 +msgid "To access those options, click the :guilabel:`(downward arrow)` icon, located to the right of the search bar. Doing so reveals a drop-down mega menu featuring those filtering and grouping options." +msgstr "" + +#: ../../content/applications/marketing/email_marketing.rst:-1 +msgid "The drop-down mega menu of search options the Odoo Email Marketing application." +msgstr "" + +#: ../../content/applications/marketing/email_marketing.rst:204 +msgid "These options provide various ways to specify and organize the information seen on the :guilabel:`Mailings` dashboard." +msgstr "" + +#: ../../content/applications/marketing/email_marketing.rst:209 msgid "Filters" msgstr "" -#: ../../content/applications/marketing/email_marketing.rst:112 -msgid "This drop-down menu provides different ways to filter email campaigns on the dashboard. The options are: :guilabel:`My Mailings`, :guilabel:`Sent Date`, :guilabel:`Archived`, and :guilabel:`Add Custom Filter`. If :guilabel:`Add Custom Filter` is selected, Odoo reveals an additional drop-down menu, with three customizable fields to fill in, in order to retrieve results that fit more specific criteria." +#: ../../content/applications/marketing/email_marketing.rst:211 +msgid "This section of the drop-down mega menu provides different ways to filter email results being shown on the :guilabel:`Mailings` dashboard in the :guilabel:`Email Marketing` app." msgstr "" #: ../../content/applications/marketing/email_marketing.rst:0 msgid "View of filters drop-down menu options on the Odoo Email Marketing dashboard." msgstr "" -#: ../../content/applications/marketing/email_marketing.rst:121 +#: ../../content/applications/marketing/email_marketing.rst:218 +msgid "The options are: :guilabel:`My Mailings`, :guilabel:`Sent Date`, :guilabel:`A/B Tests`, :guilabel:`A/B Tests to review`, :guilabel:`Archived`, and :guilabel:`Add Custom Filter`." +msgstr "" + +#: ../../content/applications/marketing/email_marketing.rst:221 +msgid "If :guilabel:`Add Custom Filter` is selected, Odoo reveals a pop-up window, with three customizable fields to fill in, in order to create custom filter rules for Odoo to use to retrieve results that fit more specific criteria." +msgstr "" + +#: ../../content/applications/marketing/email_marketing.rst:0 +msgid "Add custom filter pop-up window that appears in Odoo Email Marketing app." +msgstr "" + +#: ../../content/applications/marketing/email_marketing.rst:229 msgid "Group By" msgstr "" -#: ../../content/applications/marketing/email_marketing.rst:123 -msgid "This drop-down menu provides additional ways to organize the data on the dashboard by grouping them in specific ways. Using this drop-down menu, the data can be grouped by the messages' :guilabel:`Status`, or who it was :guilabel:`Sent By`." -msgstr "" - -#: ../../content/applications/marketing/email_marketing.rst:127 -msgid "There is also the option to group the data by :guilabel:`Sent Period`, which has its own sub-menu of options to choose from. The :guilabel:`Sent Period` options are :guilabel:`Year`, :guilabel:`Quarter`, :guilabel:`Month`, :guilabel:`Week`, and :guilabel:`Day`." -msgstr "" - -#: ../../content/applications/marketing/email_marketing.rst:131 -msgid "If none of the above :guilabel:`Group By` options deliver the desired results, click :guilabel:`Add Custom Group` at the bottom of the drop-down menu. Doing so reveals a new field, wherein custom criteria can be selected and applied, thus delivering any grouping of data that may be desired." +#: ../../content/applications/marketing/email_marketing.rst:231 +msgid "This section of the drop-down mega menu provides different ways to group email results being shown on the :guilabel:`Mailings` dashboard in the :guilabel:`Email Marketing` app." msgstr "" #: ../../content/applications/marketing/email_marketing.rst:0 msgid "View of the Group By drop-down menu on the Odoo Email Marketing application." msgstr "" -#: ../../content/applications/marketing/email_marketing.rst:139 +#: ../../content/applications/marketing/email_marketing.rst:238 +msgid "Using this section, the data can be grouped by the messages' :guilabel:`Status`, or who it was :guilabel:`Sent By`." +msgstr "" + +#: ../../content/applications/marketing/email_marketing.rst:241 +msgid "There is also the option to group the data by :guilabel:`Sent Period`, which has its own sub-menu of options to choose from. The :guilabel:`Sent Period` options are :guilabel:`Year`, :guilabel:`Quarter`, :guilabel:`Month`, :guilabel:`Week`, and :guilabel:`Day`." +msgstr "" + +#: ../../content/applications/marketing/email_marketing.rst:245 +msgid "If none of the above :guilabel:`Group By` options deliver the desired results, click :guilabel:`Add Custom Group` at the bottom of the :guilabel:`Group By` section. Doing so reveals a drop-down menu, wherein custom criteria can be selected and applied, thus delivering any grouping of data that may be desired." +msgstr "" + +#: ../../content/applications/marketing/email_marketing.rst:250 msgid "Favorites" msgstr "" -#: ../../content/applications/marketing/email_marketing.rst:141 -msgid "This drop-down menu provides different ways to incorporate past search filters and other record-related options to customize the dashboard. The options are: :guilabel:`Save current search`, :guilabel:`Import records`, :guilabel:`Add to my dashboard`, and :guilabel:`Add to Google Spreadsheet`." +#: ../../content/applications/marketing/email_marketing.rst:252 +msgid "This section provides the opportunity to save custom filters and/or groupings for future use. To utilize this section, click the :guilabel:`Save current search` field, which reveals additional fields." msgstr "" #: ../../content/applications/marketing/email_marketing.rst:0 msgid "View of the Favorites drop-down menu on the Odoo Email Marketing application." msgstr "" -#: ../../content/applications/marketing/email_marketing.rst:150 +#: ../../content/applications/marketing/email_marketing.rst:260 +msgid "Give the favorited filter/grouping a title on the blank line above the checkboxes for :guilabel:`Default filter` and :guilabel:`Shared`." +msgstr "" + +#: ../../content/applications/marketing/email_marketing.rst:263 +msgid "Ticking the box for :guilabel:`Default filter` makes this favorited filter/grouping the default option. Ticking the box for :guilabel:`Shared` allows other users to see and use this favorited filter/grouping." +msgstr "" + +#: ../../content/applications/marketing/email_marketing.rst:267 +msgid "When all desired options are configured, click :guilabel:`Save` to save the filter/grouping in the :guilabel:`Favorites` section of the mega drop-down menu." +msgstr "" + +#: ../../content/applications/marketing/email_marketing.rst:271 msgid "Settings" msgstr "" -#: ../../content/applications/marketing/email_marketing.rst:152 -msgid "To view (and modify) the *Email Marketing* settings, navigate to :menuselection:`Email Marketing application --> Configuration --> Settings`." +#: ../../content/applications/marketing/email_marketing.rst:273 +msgid "To view and modify the *Email Marketing* settings, navigate to :menuselection:`Email Marketing app --> Configuration --> Settings`." +msgstr "" + +#: ../../content/applications/marketing/email_marketing.rst:-1 +msgid "View of the Configuration menu with Settings page in the Odoo Email Marketing application." +msgstr "" + +#: ../../content/applications/marketing/email_marketing.rst:280 +msgid "On the :guilabel:`Settings` page, there are four features available." msgstr "" #: ../../content/applications/marketing/email_marketing.rst:-1 msgid "View of the Settings page in the Odoo Email Marketing application." msgstr "" -#: ../../content/applications/marketing/email_marketing.rst:159 -msgid "On this :guilabel:`Settings` page, there are three features available. The features are: :guilabel:`Mailing Campaigns`, :guilabel:`Blacklist Option when Unsubscribing`, and :guilabel:`Dedicated Server`." +#: ../../content/applications/marketing/email_marketing.rst:286 +msgid "The features are:" msgstr "" -#: ../../content/applications/marketing/email_marketing.rst:163 +#: ../../content/applications/marketing/email_marketing.rst:288 msgid ":guilabel:`Mailing Campaigns`: enables the option to manage mass mailing campaigns." msgstr "" -#: ../../content/applications/marketing/email_marketing.rst:164 +#: ../../content/applications/marketing/email_marketing.rst:289 msgid ":guilabel:`Blacklist Option when Unsubscribing`: allows recipients to blacklist themselves from future mailings during the unsubscribing process." msgstr "" -#: ../../content/applications/marketing/email_marketing.rst:166 +#: ../../content/applications/marketing/email_marketing.rst:291 msgid ":guilabel:`Dedicated Server`: provides the option to utilize a separate, dedicated server for mailings. When enabled, Odoo reveals a new field (and link), in which the specific server configurations must be entered, in order for it to connect properly to Odoo." msgstr "" -#: ../../content/applications/marketing/email_marketing.rst:171 +#: ../../content/applications/marketing/email_marketing.rst:294 +msgid ":guilabel:`24H Stat Mailing Reports`: allows users to check how well mailings have performed a day after it has been sent." +msgstr "" + +#: ../../content/applications/marketing/email_marketing.rst:300 msgid "Create an email" msgstr "" -#: ../../content/applications/marketing/email_marketing.rst:173 -msgid "To create an email, open the :menuselection:`Email Marketing` application, and click the :guilabel:`Create` button in the upper-left corner." +#: ../../content/applications/marketing/email_marketing.rst:302 +msgid "To create an email, open the :menuselection:`Email Marketing` application, and click the :guilabel:`New` button in the upper-left corner of the :guilabel:`Mailings` dashboard page." msgstr "" -#: ../../content/applications/marketing/email_marketing.rst:176 -msgid "Clicking :guilabel:`Create` reveals a blank email detail form." +#: ../../content/applications/marketing/email_marketing.rst:305 +msgid "Clicking :guilabel:`New` reveals a blank email form." msgstr "" #: ../../content/applications/marketing/email_marketing.rst:-1 msgid "View of a blank email detail form in Odoo Email Marketing application." msgstr "" -#: ../../content/applications/marketing/email_marketing.rst:182 -msgid "First, enter a :guilabel:`Subject` to the email. The :guilabel:`Subject` is visible in the recipients' inbox, allowing them to get quickly see what the message is about." +#: ../../content/applications/marketing/email_marketing.rst:311 +msgid "On the email form, there are fields for the :ref:`Subject ` and :ref:`Recipients ` of the email." msgstr "" -#: ../../content/applications/marketing/email_marketing.rst:186 -msgid "The :guilabel:`Subject` field is mandatory. An email can not be sent without a :guilabel:`Subject`." +#: ../../content/applications/marketing/email_marketing.rst:314 +msgid "Beneath that, there are three tabs: :ref:`Mail Body `, :ref:`A/B Tests `, and :ref:`Settings `." msgstr "" -#: ../../content/applications/marketing/email_marketing.rst:190 -msgid "The :guilabel:`☺ (smiley face)` icon at the end of the :guilabel:`Subject` field (and :guilabel:`Preview Text` field) represents emojis. Click that :guilabel:`☺ (smiley face)` icon to reveal a menu of emojis that can be used in either field." +#: ../../content/applications/marketing/email_marketing.rst:320 +msgid "Subject" msgstr "" -#: ../../content/applications/marketing/email_marketing.rst:194 -msgid "Next, there is the option to enter some :guilabel:`Preview Text`. This text is a catchy preview sentence that encourages recipients to open the message. In most inboxes, this is displayed next to the subject." +#: ../../content/applications/marketing/email_marketing.rst:322 +msgid "First, enter a :guilabel:`Subject` to the email. The :guilabel:`Subject` is visible in the recipients' inbox, allowing them to quickly see what the message is about." msgstr "" -#: ../../content/applications/marketing/email_marketing.rst:199 -msgid "Keep the :guilabel:`Preview Text` empty to show the first characters of the email content, instead." +#: ../../content/applications/marketing/email_marketing.rst:326 +msgid "The :guilabel:`Subject` field is mandatory. An email can **not** be sent without a :guilabel:`Subject`." msgstr "" -#: ../../content/applications/marketing/email_marketing.rst:203 +#: ../../content/applications/marketing/email_marketing.rst:329 +msgid "The :guilabel:`(smiley face with a plus sign)` icon at the end of the :guilabel:`Subject` field represents emojis that can be added to the :guilabel:`Subject` field. Clicking that icon reveals a pop-up menu of emojis that can be used." +msgstr "" + +#: ../../content/applications/marketing/email_marketing.rst:333 +msgid "Beside the :guilabel:`(smiley face with a plus sign)` icon at the end of the :guilabel:`Subject` field is an empty :guilabel:`(star)` icon. When clicked, the :guilabel:`(star)` icon turns gold, and the email is saved as a template in the :guilabel:`Mail Body` tab, which can be used again in the future." +msgstr "" + +#: ../../content/applications/marketing/email_marketing.rst:341 msgid "Recipients" msgstr "" -#: ../../content/applications/marketing/email_marketing.rst:205 -msgid "After that, it's time to choose the recipients of this email, which can be completed in the :guilabel:`Recipients` field." +#: ../../content/applications/marketing/email_marketing.rst:343 +msgid "Beneath the :guilabel:`Subject` field on the email form is the :guilabel:`Recipients` field. In this field, select the recipients of the email. By default, the :guilabel:`Mailing List` option is selected, but clicking the field reveals a drop-down menu of other recipient options." +msgstr "" + +#: ../../content/applications/marketing/email_marketing.rst:347 +msgid "With the default :guilabel:`Mailing List` option selected, a specific mailing list **must** be chosen from the adjacent :guilabel:`Select mailing lists` field drop-down menu." +msgstr "" + +#: ../../content/applications/marketing/email_marketing.rst:351 +msgid "More than one mailing list can be chosen from the :guilabel:`Select mailing lists` field." +msgstr "" + +#: ../../content/applications/marketing/email_marketing.rst:353 +msgid "Odoo then sends the email to contacts on that specific mailing list(s)." +msgstr "" + +#: ../../content/applications/marketing/email_marketing.rst:356 +#: ../../content/applications/marketing/email_marketing.rst:822 +msgid ":doc:`email_marketing/mailing_lists`" +msgstr "" + +#: ../../content/applications/marketing/email_marketing.rst:358 +msgid "When the :guilabel:`Recipients` field is clicked, a drop-down menu of other options is revealed. Each option provides different ways Odoo can create a target audience for the email." msgstr "" #: ../../content/applications/marketing/email_marketing.rst:-1 msgid "View of recipients drop-down menu in the Odoo Email Marketing application." msgstr "" -#: ../../content/applications/marketing/email_marketing.rst:212 -msgid "The default option is :guilabel:`Mailing List`. If :guilabel:`Mailing List` option is selected, a specific :guilabel:`Mailing List` needs to be chosen from the adjacent :guilabel:`Select mailing lists` field drop-down menu." +#: ../../content/applications/marketing/email_marketing.rst:365 +msgid "Those options (excluding the default :guilabel:`Mailing List`) provide the option to create a more specified recipient filter, in an equation-like format, which appears beneath the :guilabel:`Recipients` field." msgstr "" -#: ../../content/applications/marketing/email_marketing.rst:216 -msgid "Then, Odoo will only send this email to contacts on that specific mailing list." +#: ../../content/applications/marketing/email_marketing.rst:369 +msgid "The :guilabel:`Recipients` field options, other than the default :guilabel:`Mailing List` option, are as follows:" msgstr "" -#: ../../content/applications/marketing/email_marketing.rst:221 -msgid "When the :guilabel:`Recipients` field is clicked, a drop-down menu of other options is revealed. Each option provides different ways Odoo can create a target audience for the email." +#: ../../content/applications/marketing/email_marketing.rst:372 +msgid ":guilabel:`Contact`: ties specifically to the *Contacts* app, and includes all the contacts entered in the database." msgstr "" -#: ../../content/applications/marketing/email_marketing.rst:224 -msgid "Those options (excluding the default :guilabel:`Mailing List`) provide the option to create a more specified recipient filter, in an equation-like format." +#: ../../content/applications/marketing/email_marketing.rst:374 +msgid ":guilabel:`Event Registration`: ties specifically to the *Events* app, and provides opportunities to interact with event registrants, in order to communicate important information about the event(s), or nurture other valuable actions, such as post-event surveys, purchases, etc." msgstr "" -#: ../../content/applications/marketing/email_marketing.rst:227 -msgid "The :guilabel:`Recipients` field options are as follows:" +#: ../../content/applications/marketing/email_marketing.rst:377 +msgid ":guilabel:`Lead/Opportunity`: ties specifically to records in the *CRM* application, which opens up a number of opportunities to influence sales or purchase decisions." msgstr "" -#: ../../content/applications/marketing/email_marketing.rst:229 -msgid ":guilabel:`Applicant`: filter focuses on specific job applicants in the database." +#: ../../content/applications/marketing/email_marketing.rst:379 +msgid ":guilabel:`Mailing Contact`: ties specifically to the *Email Marketing* app, and focuses on specific mailing contacts that have been entered in that specific application, and are related to a specific mailing list. These contacts are also unique because they do *not* have their own contact card in the *Contacts* application. This list can be accessed by navigating to :menuselection:`Email Marketing app --> Mailing Lists --> Mailing List Contacts`." msgstr "" -#: ../../content/applications/marketing/email_marketing.rst:230 -msgid ":guilabel:`Contact`: filter focuses on specific contacts in the database." +#: ../../content/applications/marketing/email_marketing.rst:384 +msgid ":guilabel:`Sales Order`: ties specifically to the *Sales* app, and focuses on a specific sales orders in the database." msgstr "" -#: ../../content/applications/marketing/email_marketing.rst:231 -msgid ":guilabel:`Event Registration`: filter focuses on people in the database who purchased event registrations." +#: ../../content/applications/marketing/email_marketing.rst:388 +msgid "Add recipient filter" msgstr "" -#: ../../content/applications/marketing/email_marketing.rst:233 -msgid ":guilabel:`Event Track`: filter focuses on people in the database who hosted a specific talk (track) at an event." +#: ../../content/applications/marketing/email_marketing.rst:390 +msgid "To add a more specific recipient filter to any :guilabel:`Recipient` option, select any recipient option (other than :guilabel:`Mailing List`), and click the :guilabel:`Modify filter (right-facing arrow)` icon beneath the :guilabel:`Recipient` field to reveal three subsequent filter rule fields, formatted like an equation." msgstr "" -#: ../../content/applications/marketing/email_marketing.rst:235 -msgid ":guilabel:`Lead/Opportunity`: filter focuses on leads or opportunities in the database." +#: ../../content/applications/marketing/email_marketing.rst:395 +msgid "It is highly recommended that users implement detailed targeting criteria for the :guilabel:`Recipients` field. Typically, a single line of targeting logic is not sufficient enough for an email campaign." msgstr "" -#: ../../content/applications/marketing/email_marketing.rst:236 -msgid ":guilabel:`Mailing Contact`: filter focuses on specific mailing contacts in the database." +#: ../../content/applications/marketing/email_marketing.rst:399 +msgid "While the :guilabel:`Mailing List` option is adequate for the :guilabel:`Recipients` field, the :guilabel:`Lead/Opportunity` and :guilabel:`Event Registration` options provide far more detailed targeting criteria, which can be added on top of those seed sources." msgstr "" -#: ../../content/applications/marketing/email_marketing.rst:237 -msgid ":guilabel:`Sales Order`: filter focuses on a specific sales orders in the database." -msgstr "" - -#: ../../content/applications/marketing/email_marketing.rst:239 -msgid "If the specified recipient fields don't automatically reveal themselves, simply click the :guilabel:`Add Filter` button beneath the :guilabel:`Recipients` field, and Odoo reveals the necessary equation fields to further drill down the target recipients for this mailing." -msgstr "" - -#: ../../content/applications/marketing/email_marketing.rst:244 -msgid "Add a recipient filter" -msgstr "" - -#: ../../content/applications/marketing/email_marketing.rst:246 -msgid "To add a more specified recipient filter, select any recipient option (other than :guilabel:`Mailing List`), and clicking :guilabel:`Add Filter`, if needed, to reveal three fields, formatted like an equation." -msgstr "" - -#: ../../content/applications/marketing/email_marketing.rst:250 -msgid "To reveal the sub-menu options, click each field, and make the desired selections, until the preferred configuration has been achieved. The number of :guilabel:`Records` that match the rule(s) are indicated to the right of the :guilabel:`Recipients` field, in green." +#: ../../content/applications/marketing/email_marketing.rst:404 +msgid "For example, with the :guilabel:`Lead/Opportunity` option chosen in the :guilabel:`Recipients` field, users can add various custom criteria related to :guilabel:`Created on` dates, :guilabel:`Stages`, :guilabel:`Tags`, :guilabel:`Lost Reasons`, :guilabel:`Sales Teams`, :guilabel:`Active` statuses, :guilabel:`Country`, and so much more." msgstr "" +#: ../../content/applications/marketing/email_marketing.rst:0 #: ../../content/applications/marketing/email_marketing.rst:-1 msgid "View of how recipient filters can be customized in Odoo Email Marketing." msgstr "" -#: ../../content/applications/marketing/email_marketing.rst:259 +#: ../../content/applications/marketing/email_marketing.rst:413 +msgid "To reveal the sub-menu options within the filter rule fields, click each field, and make the desired selections, until the preferred configuration has been achieved." +msgstr "" + +#: ../../content/applications/marketing/email_marketing.rst:416 +msgid "The number of :guilabel:`records` in the database that match the configured rule(s) are indicated beneath the configured filter rule(s), in green." +msgstr "" + +#: ../../content/applications/marketing/email_marketing.rst:424 #: ../../content/applications/marketing/events/event_essentials.rst:191 msgid "Some sub-menu options in the first rule field allow for a second choice to provide even more specificity." msgstr "" -#: ../../content/applications/marketing/email_marketing.rst:262 -msgid "To the right of each rule, are :guilabel:`× (Delete node)`, :guilabel:`＋ (Add node)`, and :guilabel:`⋯ (Add branch)` icons." +#: ../../content/applications/marketing/email_marketing.rst:427 +msgid "To the right of each rule, there are three additional options, represented by :guilabel:`➕ (plus sign)`, :guilabel:`(sitemap)`, and :guilabel:`🗑️ (trash)` icons." msgstr "" -#: ../../content/applications/marketing/email_marketing.rst:265 -msgid "The :guilabel:`× (Delete node)` icon deletes a specific node (line) of the rule. The :guilabel:`＋ (Add node)` icon adds a node (line) to the rule. And, the :guilabel:`⋯ (Add branch)` icon adds a branch to the node. A branch means two additional, indented sub-nodes are added to the rule, providing even more specificity to the line above it." +#: ../../content/applications/marketing/email_marketing.rst:430 +msgid "The :guilabel:`➕ (plus sign)` icon adds a new node (line) to the overall targeting logic." msgstr "" -#: ../../content/applications/marketing/email_marketing.rst:271 -msgid "Mail body tab" +#: ../../content/applications/marketing/email_marketing.rst:431 +msgid "The :guilabel:`(sitemap)` icon adds a branch to the node. A branch contains two additional, indented sub-nodes that are related to that specific rule, providing even more specificity to the parent line above it." msgstr "" -#: ../../content/applications/marketing/email_marketing.rst:273 -msgid "At the bottom of the email form are two tabs: :guilabel:`Mail Body` and :guilabel:`Settings`. Let's focus on :guilabel:`Mail Body` tab first." +#: ../../content/applications/marketing/email_marketing.rst:434 +msgid "The :guilabel:`🗑️ (trash)` icon deletes a specific node (line) in the array of logic." msgstr "" -#: ../../content/applications/marketing/email_marketing.rst:276 -msgid "In the :guilabel:`Mail Body` tab, there are a number of pre-configured message templates to choose from. Select the desired template, and modify every element of its design details with Odoo's drag-and-drop building blocks, located on the right sidebar. Each building block provides unique features and professional design elements." +#: ../../content/applications/marketing/email_marketing.rst:439 +msgid "Mail Body tab" +msgstr "" + +#: ../../content/applications/marketing/email_marketing.rst:441 +msgid "In the :guilabel:`Mail Body` tab, there are a number of pre-configured message templates to choose from." msgstr "" #: ../../content/applications/marketing/email_marketing.rst:-1 -msgid "View of the building blocks used to create mailings in Odoo Email Marketing application." +msgid "View of the templates in the Mail Body tab in Odoo Email Marketing application." msgstr "" -#: ../../content/applications/marketing/email_marketing.rst:286 -msgid "To build an email from scratch, select the :guilabel:`Plain Text` template, and Odoo provides a blank email canvas, which can be customized in a number of ways - either by using the front-end rich text editor that accepts slash (:guilabel:`/`) commands, or with the XML code editor when :ref:`Developer Mode (debug mode) ` is engaged, and the :guilabel:`` icon is clicked." +#: ../../content/applications/marketing/email_marketing.rst:448 +msgid "Select the desired template, and proceed to modify every element of its design details with Odoo's drag-and-drop building blocks, which appear on the right sidebar when a template is chosen." msgstr "" -#: ../../content/applications/marketing/email_marketing.rst:293 +#: ../../content/applications/marketing/email_marketing.rst:-1 +msgid "View of the building blocks in the Mail Body tab in Odoo Email Marketing application." +msgstr "" + +#: ../../content/applications/marketing/email_marketing.rst:455 +msgid "The features on the sidebar used to create and customize emails are separated into three sections: :guilabel:`Blocks`, :guilabel:`Customize`, and :guilabel:`Design`." +msgstr "" + +#: ../../content/applications/marketing/email_marketing.rst:458 +msgid "Each building block provides unique features and professional design elements. To use a building block, drag-and-drop the desired block element onto the body of the email being built. Once dropped, various aspects of the building block can be customized." +msgstr "" + +#: ../../content/applications/marketing/email_marketing.rst:463 +msgid "To build an email from the ground up, without any building block elements, select the :guilabel:`Plain Text` template. When selected, Odoo provides a completely blank email canvas, which can be customized in a number of way using the front-end rich text editor that accepts forward slash `/` commands." +msgstr "" + +#: ../../content/applications/marketing/email_marketing.rst:468 +msgid "When `/` is typed into the blank body of the email, while using a :guilabel:`Plain Text` template, a drop-down menu of various design elements appears, which can be used to create the desired email design." +msgstr "" + +#: ../../content/applications/marketing/email_marketing.rst:0 +msgid "View of the rich text editor drop-down in the Odoo Email Marketing application." +msgstr "" + +#: ../../content/applications/marketing/email_marketing.rst:479 +msgid "A/B Tests tab" +msgstr "" + +#: ../../content/applications/marketing/email_marketing.rst:481 +msgid "Initially, when the :guilabel:`A/B Tests` tab is opened on an email form, the only option available is :guilabel:`Allow A/B Testing`. This is **not** a required option." +msgstr "" + +#: ../../content/applications/marketing/email_marketing.rst:484 +msgid "If this option is enabled, recipients are only mailed *once* for the entirety of the campaign." +msgstr "" + +#: ../../content/applications/marketing/email_marketing.rst:486 +msgid "This allows the user to send different versions of the same mailing to randomly selected recipients to gauge the effectiveness of various designs, formats, layouts, content, and so on -- without any duplicate messages being sent." +msgstr "" + +#: ../../content/applications/marketing/email_marketing.rst:490 +msgid "When the checkbox beside :guilabel:`Allow A/B Testing` is ticked, an :guilabel:`on (%)` field appears, in which the user determines the percentage of the pre-configured recipients that are going to be sent this current version of the mailing as part of the test." +msgstr "" + +#: ../../content/applications/marketing/email_marketing.rst:495 +msgid "The default figure in the :guilabel:`on (%)` field is `10`, but that figure can be changed at any time." +msgstr "" + +#: ../../content/applications/marketing/email_marketing.rst:498 +msgid "Beneath that, two additional fields appear:" +msgstr "" + +#: ../../content/applications/marketing/email_marketing.rst:500 +msgid "The :guilabel:`Winner Selection` field provides a drop-down menu of options, wherein the user decides what criteria should be used to determine the \"winning\" version of the email tests that are sent." +msgstr "" + +#: ../../content/applications/marketing/email_marketing.rst:504 +msgid "The options in the :guilabel:`Winner Selection` field are as follows:" +msgstr "" + +#: ../../content/applications/marketing/email_marketing.rst:506 +msgid ":guilabel:`Manual`: allows the user to determine the \"winning\" version of the mailing. This option removes the :guilabel:`Send Final On` field." +msgstr "" + +#: ../../content/applications/marketing/email_marketing.rst:508 +msgid ":guilabel:`Highest Open Rate` (default): the mailing with the highest open rate is determined to be the \"winning\" version." +msgstr "" + +#: ../../content/applications/marketing/email_marketing.rst:510 +msgid ":guilabel:`Highest Click Rate`: the mailing with the highest click rate is determined to be the \"winning\" version." +msgstr "" + +#: ../../content/applications/marketing/email_marketing.rst:512 +msgid ":guilabel:`Highest Reply Rate`: the mailing with the highest reply rate is determined to be the \"winning\" version." +msgstr "" + +#: ../../content/applications/marketing/email_marketing.rst:514 +msgid ":guilabel:`Leads`: the mailing with the most leads generated is determined to be the \"winning\" version." +msgstr "" + +#: ../../content/applications/marketing/email_marketing.rst:516 +msgid ":guilabel:`Quotations`: the mailing with the most quotations generated is determined to be the \"winning\" version." +msgstr "" + +#: ../../content/applications/marketing/email_marketing.rst:518 +msgid ":guilabel:`Revenues`: the mailing with the most revenue generated is determined to be the \"winning\" version." +msgstr "" + +#: ../../content/applications/marketing/email_marketing.rst:521 +msgid "The :guilabel:`Send Final On` field allows users to choose a date that is used to know *when* Odoo should determine the \"winning\" email, and subsequently, send that version of the email to the remaining recipients." +msgstr "" + +#: ../../content/applications/marketing/email_marketing.rst:-1 +msgid "View of the A/B Tests tab in Odoo Email Marketing application." +msgstr "" + +#: ../../content/applications/marketing/email_marketing.rst:529 +msgid "To the right of those fields is a :guilabel:`Create an Alternative Version` button. When clicked, Odoo presents a new :guilabel:`Mail Body` tab for the user to create an alternate version of the email to test." +msgstr "" + +#: ../../content/applications/marketing/email_marketing.rst:536 msgid "Settings tab" msgstr "" -#: ../../content/applications/marketing/email_marketing.rst:295 -msgid "To the right of the :guilabel:`Mail Body` tab is the :guilabel:`Settings` tab." +#: ../../content/applications/marketing/email_marketing.rst:538 +msgid "The options present in the :guilabel:`Settings` tab of the mail form are divided into two sections: :guilabel:`Email Content` and :guilabel:`Tracking`." msgstr "" -#: ../../content/applications/marketing/email_marketing.rst:298 -msgid "The options available in the :guilabel:`Settings` tab will be different, depending on if the :guilabel:`Mailing Campaigns` feature is activated in the :guilabel:`Settings` page of the :menuselection:`Email Marketing` application (:menuselection:`Email Marketing --> Configuration --> Settings`)." +#: ../../content/applications/marketing/email_marketing.rst:542 +msgid "The options available in the :guilabel:`Settings` tab vary depending on if the *Mailing Campaigns* feature is activated in :menuselection:`Email Marketing --> Configuration --> Settings`. See :ref:`email_marketing/mailing-campaigns` for more information." msgstr "" -#: ../../content/applications/marketing/email_marketing.rst:303 -msgid "Without the :guilabel:`Mailing Campaigns` feature activated, the :guilabel:`Settings` tab on the email detail form looks like this:" +#: ../../content/applications/marketing/email_marketing.rst:546 +msgid "Without the *Mailing Campaigns* feature activated, the :guilabel:`Settings` tab on the email form only contains the :guilabel:`Preview Text`, :guilabel:`Send From`, :guilabel:`Reply To`, :guilabel:`Attachments`, and :guilabel:`Responsible` fields." msgstr "" #: ../../content/applications/marketing/email_marketing.rst:-1 -msgid "View of settings tab in Odoo Email Marketing app, without settings activated." +msgid "View of settings tab in Odoo Email Marketing app, without campaign setting activated." msgstr "" -#: ../../content/applications/marketing/email_marketing.rst:310 -msgid ":guilabel:`Responsible`: choose an employee (in the database) to be responsible for this particular email." +#: ../../content/applications/marketing/email_marketing.rst:555 +msgid "Email content" msgstr "" -#: ../../content/applications/marketing/email_marketing.rst:312 -msgid ":guilabel:`Send From`: designate an email alias that'll display as the sender of this particular email." +#: ../../content/applications/marketing/email_marketing.rst:557 +msgid ":guilabel:`Preview Text`: allows the user to enter a preview sentence to encourage recipients to open the email. In most inboxes, this is displayed next to the subject. If left empty, the first characters of the email content appear, instead. The ability to add an emoji in this field is available, as well, via the :guilabel:`(smiley face with a plus sign)` icon." msgstr "" -#: ../../content/applications/marketing/email_marketing.rst:314 -msgid ":guilabel:`Reply To`: designate an email alias to whom all the replies to this particular email will be sent." +#: ../../content/applications/marketing/email_marketing.rst:561 +msgid ":guilabel:`Send From`: designate an email alias that displays as the sender of this particular email." msgstr "" -#: ../../content/applications/marketing/email_marketing.rst:316 -msgid ":guilabel:`Attachments`: if any specific documents are required (or helpful) for this event invite, they can be sent along with this email, by clicking :guilabel:`ATTACH A FILE`, and adding the appropriate document(s)." +#: ../../content/applications/marketing/email_marketing.rst:563 +msgid ":guilabel:`Reply To`: designate an email alias to whom all the replies of this particular email are sent." msgstr "" -#: ../../content/applications/marketing/email_marketing.rst:320 -msgid "When the :guilabel:`Mailing Campaigns` feature *is* activated, additional :guilabel:`Marketing` options appear in the :guilabel:`Settings` tab, which look like this:" +#: ../../content/applications/marketing/email_marketing.rst:565 +msgid ":guilabel:`Attach a file`: if any specific files are required (or helpful) for this email, click the :guilabel:`Attachments` button, and upload the desired file(s) to the email." +msgstr "" + +#: ../../content/applications/marketing/email_marketing.rst:569 +msgid "Tracking" +msgstr "" + +#: ../../content/applications/marketing/email_marketing.rst:571 +msgid ":guilabel:`Responsible`: designate a user in the database to be responsible for this particular email." +msgstr "" + +#: ../../content/applications/marketing/email_marketing.rst:575 +msgid "If the *Mailing Campaign* feature *is* activated, an additional :guilabel:`Campaign` field appears in the :guilabel:`Tracking` section of the :guilabel:`Settings` tab." msgstr "" #: ../../content/applications/marketing/email_marketing.rst:-1 -msgid "View of settings tab in Odoo Email Marketing when settings are activated." +msgid "View of settings tab in Odoo Email Marketing when campaign setting is activated." msgstr "" -#: ../../content/applications/marketing/email_marketing.rst:327 -msgid "The additional features are: :guilabel:`Mailing Campaign`, :guilabel:`Allow A/B Testing`, and :guilabel:`A/B Testing percentage`." +#: ../../content/applications/marketing/email_marketing.rst:582 +msgid "The additional :guilabel:`Campaign` field allows users to attach this particular email to a mailing campaign, if desired." msgstr "" -#: ../../content/applications/marketing/email_marketing.rst:331 +#: ../../content/applications/marketing/email_marketing.rst:585 +msgid "If the desired campaign is not available in the initial drop-down menu, select :guilabel:`Search More` to reveal a complete list of all mailing campaigns in the database." +msgstr "" + +#: ../../content/applications/marketing/email_marketing.rst:588 +msgid "Or, type the name of the desired mailing campaign in the :guilabel:`Campaign` field, until Odoo reveals the desired campaign in the drop-down menu. Then, select the desired campaign." +msgstr "" + +#: ../../content/applications/marketing/email_marketing.rst:592 +msgid "Send, schedule, test" +msgstr "" + +#: ../../content/applications/marketing/email_marketing.rst:594 +msgid "Once the mailing is finalized, the following options can be utilized, via buttons located in the upper-left corner of the email form: :ref:`Send `, :ref:`Schedule `, and :ref:`Test `." +msgstr "" + +#: ../../content/applications/marketing/email_marketing.rst:601 +msgid "Send" +msgstr "" + +#: ../../content/applications/marketing/email_marketing.rst:603 +msgid "The :guilabel:`Send` button reveals a :guilabel:`Ready to unleash emails?` pop-up window." +msgstr "" + +#: ../../content/applications/marketing/email_marketing.rst:-1 +msgid "View of pop-up window that appears when the send button on an email form is clicked." +msgstr "" + +#: ../../content/applications/marketing/email_marketing.rst:609 +msgid "When the :guilabel:`Send to all` button is clicked, Odoo sends the email to the desired recipients. Once Odoo has sent the mailing, the status changes to :guilabel:`Sent`." +msgstr "" + +#: ../../content/applications/marketing/email_marketing.rst:615 +msgid "Schedule" +msgstr "" + +#: ../../content/applications/marketing/email_marketing.rst:617 +msgid "The :guilabel:`Schedule` button reveals a :guilabel:`When do you want to send your mailing?` pop-up window." +msgstr "" + +#: ../../content/applications/marketing/email_marketing.rst:-1 +#: ../../content/applications/marketing/email_marketing.rst:-1 +msgid "View of pop-up window that appears when the schedule button on an email form is clicked." +msgstr "" + +#: ../../content/applications/marketing/email_marketing.rst:624 +msgid "In this pop-up window, click the :guilabel:`Send on` field to reveal a calendar pop-up window." +msgstr "" + +#: ../../content/applications/marketing/email_marketing.rst:630 +msgid "From the calendar pop-up window, select the future date and time for Odoo to send this email. Then, click :guilabel:`✔️ Apply`. When a date and time are chosen, click the :guilabel:`Schedule` button, and the status of the mailing changes to :guilabel:`In Queue`." +msgstr "" + +#: ../../content/applications/marketing/email_marketing.rst:637 +msgid "Test" +msgstr "" + +#: ../../content/applications/marketing/email_marketing.rst:639 +msgid "The :guilabel:`Test` button reveals a :guilabel:`Test Mailing` pop-up window." +msgstr "" + +#: ../../content/applications/marketing/email_marketing.rst:-1 +msgid "View of pop-up window that appears when the test button on an email form is clicked." +msgstr "" + +#: ../../content/applications/marketing/email_marketing.rst:645 +msgid "From this pop-up window, enter the email addresses of the contacts to whom Odoo should send this test email in the :guilabel:`Recipients` field. Multiple contacts can be added in this field, if desired." +msgstr "" + +#: ../../content/applications/marketing/email_marketing.rst:649 +msgid "Once all the desired email addresses have been entered in the :guilabel:`Recipients` field, click the :guilabel:`Send Test` button." +msgstr "" + +#: ../../content/applications/marketing/email_marketing.rst:653 +msgid "By default, there's a daily limit applied for **all emails** sent throughout **all applications**. So, if there are remaining emails to be sent after a limit has been reached, those mailings are **not** sent automatically the next day. The sending needs to be forced, by opening the email and clicking :guilabel:`Retry`." +msgstr "" + +#: ../../content/applications/marketing/email_marketing.rst:661 msgid "Mailing campaigns" msgstr "" -#: ../../content/applications/marketing/email_marketing.rst:333 -msgid "The :guilabel:`Mailing Campaign` field provides the option to add this particular email to a previously-made email campaign in the database. Click the empty field to reveal a drop-down menu containing all previously-made mailing campaigns in the database." +#: ../../content/applications/marketing/email_marketing.rst:663 +msgid "The *Email Marketing* application provides users with the ability to build mailing campaigns." +msgstr "" + +#: ../../content/applications/marketing/email_marketing.rst:665 +msgid "In order to create and customize mailing campaigns, the *Mailing Campaigns* feature **must** be activated in the *Settings* page of the *Email Marketing* application. To do that, navigate to :menuselection:`Email Marketing app --> Configuration --> Settings`, tick the box beside :guilabel:`Mailing Campaigns`, and click the :guilabel:`Save` button." msgstr "" #: ../../content/applications/marketing/email_marketing.rst:-1 -msgid "View of a mailing campaign drop-down menu in Odoo Email Marketing application." +msgid "View of the campaign feature setting in Odoo Email Marketing." msgstr "" -#: ../../content/applications/marketing/email_marketing.rst:341 -msgid "If the desired campaign isn't available in the initial drop-down menu, select :guilabel:`Search More` to reveal a complete list of all mailing campaigns in the database. Or, type the name of the desired mailing campaign in the :guilabel:`Mailing Campaign` field, until Odoo reveals the desired campaign in the drop-down menu. Then, select the desired campaign." +#: ../../content/applications/marketing/email_marketing.rst:674 +msgid "Once the :guilabel:`Mailing Campaigns` feature is activated, a new :guilabel:`Campaigns` menu option appears in the header." msgstr "" -#: ../../content/applications/marketing/email_marketing.rst:347 -msgid "Create new mailing campaign (from Settings tab)" +#: ../../content/applications/marketing/email_marketing.rst:677 +msgid "When that is clicked, Odoo reveals a separate :guilabel:`Campaigns` page, displaying all the mailing campaigns in the database, and the current stage they are in, showcased in a default Kanban view." msgstr "" -#: ../../content/applications/marketing/email_marketing.rst:349 -msgid "To create a new campaign from this :guilabel:`Mailing Campaign` field, start typing the name of this new campaign, and select :guilabel:`Create [Campaign Name]` or :guilabel:`Create and Edit...`." +#: ../../content/applications/marketing/email_marketing.rst:-1 +msgid "View of the campaign page in Odoo Email Marketing." msgstr "" -#: ../../content/applications/marketing/email_marketing.rst:352 -msgid "Click :guilabel:`Create` to add this new mailing campaign to the database, and modify its settings in the future. And click :guilabel:`Create and Edit...` to add this new mailing campaign to the database, and Odoo reveals a pop-up window." +#: ../../content/applications/marketing/email_marketing.rst:685 +msgid "This information can also be viewed in a list, by clicking the :guilabel:`☰ (horizontal lines)` icon in the upper-right corner." +msgstr "" + +#: ../../content/applications/marketing/email_marketing.rst:688 +msgid "Clicking any campaign from the :guilabel:`Campaigns` page reveals that campaign's form." +msgstr "" + +#: ../../content/applications/marketing/email_marketing.rst:690 +msgid "There are two different ways to create and customize campaigns in the *Email Marketing* application, either directly from the :ref:`Campaigns page ` or through the :ref:`Settings tab ` on an email form." +msgstr "" + +#: ../../content/applications/marketing/email_marketing.rst:697 +msgid "Create mailing campaign (from campaigns page)" +msgstr "" + +#: ../../content/applications/marketing/email_marketing.rst:699 +msgid "When the *Mailing Campaigns* feature is activated, a new *Campaigns* option appears in the header of the *Email Marketing* application. Campaigns can be created directly on the *Campaigns* page in the *Email Marketing* app." +msgstr "" + +#: ../../content/applications/marketing/email_marketing.rst:703 +msgid "To do that, navigate to :menuselection:`Email Marketing app --> Campaigns --> New`." +msgstr "" + +#: ../../content/applications/marketing/email_marketing.rst:708 +msgid "When the :guilabel:`New` button is clicked in the default Kanban view on the :guilabel:`Campaigns` page, a Kanban card appears in the :guilabel:`New` stage." +msgstr "" + +#: ../../content/applications/marketing/email_marketing.rst:-1 +msgid "View of the campaign pop-up kanban in Odoo Email Marketing." +msgstr "" + +#: ../../content/applications/marketing/email_marketing.rst:715 +msgid "New campaign cards can also be made by clicking the :guilabel:`➕ (plus sign)` at the top of any Kanban stage on the :guilabel:`Campaigns` page." +msgstr "" + +#: ../../content/applications/marketing/email_marketing.rst:718 +msgid "When the new campaign Kanban card appears, the options to enter a :guilabel:`Campaign Name`, a :guilabel:`Responsible`, and :guilabel:`Tags` become readily available." +msgstr "" + +#: ../../content/applications/marketing/email_marketing.rst:721 +msgid "To add the campaign to the Kanban stage, click the :guilabel:`Add` button." +msgstr "" + +#: ../../content/applications/marketing/email_marketing.rst:723 +msgid "To delete the campaign, click the :guilabel:`🗑️ (trash can)` icon." +msgstr "" + +#: ../../content/applications/marketing/email_marketing.rst:725 +msgid "To further customize the campaign, click the :guilabel:`Edit` button, which reveals the campaign form for additional modifications." +msgstr "" + +#: ../../content/applications/marketing/email_marketing.rst:729 +msgid "A :guilabel:`Campaign Name` **must** be entered in the Kanban card, in order for the :guilabel:`Edit` button to reveal the campaign form for further modifications." +msgstr "" + +#: ../../content/applications/marketing/email_marketing.rst:735 +msgid "To enter the list view on the :guilabel:`Campaigns` page, click the :guilabel:`☰ (horizontal lines)` icon in the upper-right corner. Doing so reveals all campaign information in a list format." +msgstr "" + +#: ../../content/applications/marketing/email_marketing.rst:-1 +msgid "View of the campaign page in list view in Odoo Email Marketing." +msgstr "" + +#: ../../content/applications/marketing/email_marketing.rst:742 +msgid "To create a campaign from the :guilabel:`Campaigns` page while in list view, click the :guilabel:`New` button. Doing so reveals a blank campaign form." +msgstr "" + +#: ../../content/applications/marketing/email_marketing.rst:-1 +msgid "View of the blank campaign form in Odoo Email Marketing." +msgstr "" + +#: ../../content/applications/marketing/email_marketing.rst:749 +msgid "From this campaign form, a :guilabel:`Campaign Name`, a :guilabel:`Responsible`, and :guilabel:`Tags` can be added." +msgstr "" + +#: ../../content/applications/marketing/email_marketing.rst:752 +msgid "At the top of the form, various metric-related smart buttons can be seen that showcase specific analytics related to the campaign. Those smart buttons are: :guilabel:`Revenues`, :guilabel:`Quotations`, :guilabel:`Opportunities`, and :guilabel:`Clicks`." +msgstr "" + +#: ../../content/applications/marketing/email_marketing.rst:757 +msgid "Once a :guilabel:`Campaign Name` is entered and saved, additional buttons appear at the top of the campaign form." +msgstr "" + +#: ../../content/applications/marketing/email_marketing.rst:760 +msgid "Those additional buttons are: :guilabel:`Send Mailing` and :guilabel:`Send SMS`." +msgstr "" + +#: ../../content/applications/marketing/email_marketing.rst:763 +msgid "Campaign form" +msgstr "" + +#: ../../content/applications/marketing/email_marketing.rst:765 +msgid "On the campaign form (after clicking :guilabel:`Edit` from the Kanban card, or selecting an existing campaign from the :guilabel:`Campaigns` page) there are additional options and metrics available." +msgstr "" + +#: ../../content/applications/marketing/email_marketing.rst:-1 +msgid "View of the campaign form in Odoo Email Marketing." +msgstr "" + +#: ../../content/applications/marketing/email_marketing.rst:772 +msgid "At the top of the form, various smart buttons can be seen that showcase specific analytics related to the campaign. Those smart buttons are: :guilabel:`Revenues`, :guilabel:`Quotations`, :guilabel:`Opportunities`, and :guilabel:`Clicks`." +msgstr "" + +#: ../../content/applications/marketing/email_marketing.rst:776 +msgid "There are also buttons to :guilabel:`Send Mailing`, :guilabel:`Send SMS`, :guilabel:`Add Post`, and :guilabel:`Add Push` (push notification)." +msgstr "" + +#: ../../content/applications/marketing/email_marketing.rst:780 +msgid "If the :guilabel:`Send Mailing` and :guilabel:`Send SMS` buttons are not readily available, enter a :guilabel:`Campaign Name`, then save (either manually or automatically). Doing so reveals those buttons." +msgstr "" + +#: ../../content/applications/marketing/email_marketing.rst:784 +msgid "The status of the campaign can be viewed in the upper-right corner of the campaign form, as well." +msgstr "" + +#: ../../content/applications/marketing/email_marketing.rst:789 +msgid "Create mailing campaign (from settings tab)" +msgstr "" + +#: ../../content/applications/marketing/email_marketing.rst:791 +msgid "To create a new campaign from the :guilabel:`Settings` tab of a mailing form, click the :guilabel:`Campaign` field, and start typing the name of the new campaign. Then, select either :guilabel:`Create \"[Campaign Name]\"` or :guilabel:`Create and edit...` from the drop-down menu that appears." +msgstr "" + +#: ../../content/applications/marketing/email_marketing.rst:-1 +msgid "View of the mailing campaign creation in the Settings tab of an email form." +msgstr "" + +#: ../../content/applications/marketing/email_marketing.rst:800 +msgid "Select :guilabel:`Create` to add this new mailing campaign to the database, and modify its settings in the future." +msgstr "" + +#: ../../content/applications/marketing/email_marketing.rst:803 +msgid "Select :guilabel:`Create and Edit...` to add this new mailing campaign to the database, and reveal a :guilabel:`Create Campaign` pop-up window." msgstr "" #: ../../content/applications/marketing/email_marketing.rst:-1 msgid "View of the email mailing campaign pop-up window in Odoo Email Marketing application." msgstr "" -#: ../../content/applications/marketing/email_marketing.rst:360 -msgid "Here, the new mailing campaign can be further customized. Adjust the :guilabel:`Campaign Name`, assign a :guilabel:`Responsible`, and add :guilabel:`Tags`." +#: ../../content/applications/marketing/email_marketing.rst:810 +msgid "Here, the new mailing campaign can be further customized. Users can adjust the :guilabel:`Campaign Name`, assign a :guilabel:`Responsible`, and add :guilabel:`Tags`." msgstr "" -#: ../../content/applications/marketing/email_marketing.rst:363 -msgid "The top row of the :guilabel:`Create: Mailing Campaign` pop-up window is filled with analytical smart buttons. Each of which displays various metrics related to the campaign. When clicked, Odoo reveals a separate, more detailed page with even more in-depth statistics." +#: ../../content/applications/marketing/email_marketing.rst:813 +msgid "Buttons to :guilabel:`Add Post` or :guilabel:`Send Push` (push notifications) are also available." msgstr "" -#: ../../content/applications/marketing/email_marketing.rst:367 -msgid "The option to instantly a new communication from this pop-up window is available in the upper-left corner. The adjustable status bar is located in the upper-right." +#: ../../content/applications/marketing/email_marketing.rst:815 +msgid "There is also a status located in the upper-right corner of the :guilabel:`Create Campaign` pop-up window." msgstr "" -#: ../../content/applications/marketing/email_marketing.rst:370 -msgid "When all modifications are ready to be finalized, click :guilabel:`Save`. To delete the entire campaign, click :guilabel:`Discard`." +#: ../../content/applications/marketing/email_marketing.rst:818 +msgid "When all modifications are ready to be finalized, click :guilabel:`Save & Close`. To delete the entire campaign, click :guilabel:`Discard`." msgstr "" -#: ../../content/applications/marketing/email_marketing.rst:374 -msgid "Create new mailing campaign (from Campaigns page)" +#: ../../content/applications/marketing/email_marketing.rst:823 +msgid ":doc:`email_marketing/unsubscriptions`" msgstr "" -#: ../../content/applications/marketing/email_marketing.rst:376 -msgid "When the :guilabel:`Mailing Campaigns` feature is activated, a new :guilabel:`Campaigns` option appears in the header of the *Email Marketing* application. Campaigns can also be created on this :guilabel:`Campaigns` page in the *Email Marketing* app." +#: ../../content/applications/marketing/email_marketing.rst:824 +msgid ":doc:`email_marketing/lost_leads_email`" msgstr "" -#: ../../content/applications/marketing/email_marketing.rst:380 -msgid "To do that, navigate to :menuselection:`Email Marketing app --> Campaigns --> Create`. When that's clicked, a pop-up window appears, in which the :guilabel:`Campaign Name`, :guilabel:`Responsible`, and :guilabel:`Tags` can be added directly on the :guilabel:`Campaigns` dashboard." +#: ../../content/applications/marketing/email_marketing/lost_leads_email.rst:3 +msgid "Lost leads reactivation email" msgstr "" -#: ../../content/applications/marketing/email_marketing.rst:-1 -msgid "View of the campaign pop-up window in Odoo Email Marketing." +#: ../../content/applications/marketing/email_marketing/lost_leads_email.rst:5 +msgid "In Odoo, lost leads are removed from the active *CRM* pipeline, but can still be targeted with the *Email Marketing* application for strategic campaign purposes, such as lost leads reactivation." msgstr "" -#: ../../content/applications/marketing/email_marketing.rst:388 -msgid "Click :guilabel:`Add` to add the campaign to the database, and freely edit it later on. Or, click :guilabel:`Edit` and Odoo reveals the campaign template form on a separate page, providing the opportunity to further edit the campaign, send communications related to the campaign, and analyze various metrics related to the campaign, via the smart buttons at the top of the form." +#: ../../content/applications/marketing/email_marketing/lost_leads_email.rst:8 +msgid "A lost leads reactivation email looks at the leads that were lost during a specific period of time, and uses custom filters and lost reasons to exclude undesirable leads from the mailing list." msgstr "" -#: ../../content/applications/marketing/email_marketing.rst:394 -msgid "A/B testing" +#: ../../content/applications/marketing/email_marketing/lost_leads_email.rst:11 +msgid "Once a lost leads reactivation email is complete, it can be sent as is, modified and sent to different groups for A/B testing, or saved as a template for later." msgstr "" -#: ../../content/applications/marketing/email_marketing.rst:396 -msgid "Back in the :guilabel:`Settings` tab of the mailing, if the :guilabel:`Allow A/B Testing` box is checked, recipients are only be mailed to once. This allows different mailings to be sent to randomly selected recipients. This tests the overall effectiveness of the mailing, and eliminates the need for duplicate messages." +#: ../../content/applications/marketing/email_marketing/lost_leads_email.rst:15 +msgid "A warehouse has leftover merchandise from a limited run of items from last year. To help clear out the excess inventory, the warehouse manager creates a lost leads email to reach out to old opportunities that were lost, and inform them that the limited merchandise is back in stock." msgstr "" -#: ../../content/applications/marketing/email_marketing.rst:401 -msgid "The :guilabel:`A/B Testing percentage` field represents the percentage of contacts in the database that this message will be mailed to, as a part of the :guilabel:`A/B Testing`. Enter a number between `1-100`. The recipients are randomly chosen." +#: ../../content/applications/marketing/email_marketing/lost_leads_email.rst:19 +msgid "The warehouse manager uses the following filters for a lost leads email:" msgstr "" -#: ../../content/applications/marketing/email_marketing.rst:406 -msgid "Send, schedule, or test" +#: ../../content/applications/marketing/email_marketing/lost_leads_email.rst:21 +msgid ":guilabel:`Blacklist` *is* `not set`" msgstr "" -#: ../../content/applications/marketing/email_marketing.rst:408 -msgid "After finalizing the mailing, Odoo provides the following options in the upper-left corner of the email template page. Those options are: :guilabel:`Send`, :guilabel:`Schedule`, and :guilabel:`Test`." +#: ../../content/applications/marketing/email_marketing/lost_leads_email.rst:22 +msgid ":guilabel:`Created on` *>=* `01/01/2024 00:00:01`" msgstr "" -#: ../../content/applications/marketing/email_marketing.rst:412 -msgid "While in :guilabel:`Edit` mode, there are also buttons to :guilabel:`Save` or :guilabel:`Discard` the mailing, as well." +#: ../../content/applications/marketing/email_marketing/lost_leads_email.rst:23 +msgid ":guilabel:`Stage` *is not in* `New`, `Qualified`, or `Won`" msgstr "" -#: ../../content/applications/marketing/email_marketing.rst:415 -msgid ":guilabel:`Send` - Click to have Odoo send the email to the desired recipients. When Odoo has sent the mailing, the status changes to *Sent*." +#: ../../content/applications/marketing/email_marketing/lost_leads_email.rst:24 +msgid ":guilabel:`Lost Reason` *is in* `Not enough stock`" msgstr "" -#: ../../content/applications/marketing/email_marketing.rst:417 -msgid ":guilabel:`Schedule` - Click to reveal a pop-up window, in which a future date-time is chosen. Odoo sends the mailing to the desired recipients at that specified date-time. When a date-time is chosen, the status of the mailing changes to *In Queue*." +#: ../../content/applications/marketing/email_marketing/lost_leads_email.rst:25 +msgid "and either :guilabel:`Active` *is* `set` or `not set`" msgstr "" -#: ../../content/applications/marketing/email_marketing.rst:420 -msgid ":guilabel:`Test` - Click to reveal a pop-up window, in which Odoo allows a sample email to be sent for testing purposes. Enter the desired recipient's email address in the :guilabel:`Recipients` field, and click :guilabel:`Send Sample Mail`." +#: ../../content/applications/marketing/email_marketing/lost_leads_email.rst:0 +msgid "A lost leads reactivation filter list excluding lost reasons like Too Expensive." msgstr "" -#: ../../content/applications/marketing/email_marketing.rst:423 -msgid ":guilabel:`Save` - Click to save the mailing as a draft, which can be edited (and sent) at a later date. When clicked, the status of the mailing stays as :guilabel:`Draft`." +#: ../../content/applications/marketing/email_marketing/lost_leads_email.rst:32 +msgid "As filters are added and removed, pay attention to the :guilabel:`# record(s)` value below the filtering section. This value indicates the total number of records that match the current criteria." msgstr "" -#: ../../content/applications/marketing/email_marketing.rst:425 -msgid ":guilabel:`Discard` - Click to discard any changes that have been made since the last save." +#: ../../content/applications/marketing/email_marketing/lost_leads_email.rst:36 +msgid "To view a list of all matching records, click the :guilabel:`# record(s)` text." msgstr "" -#: ../../content/applications/marketing/email_marketing.rst:428 -msgid "When :guilabel:`Save` or :guilabel:`Discard` is selected (while in :guilabel:`Edit` mode), those options are replaced with an :guilabel:`Edit` button and a :guilabel:`Create` button. Click :guilabel:`Edit` to re-enter :guilabel:`Edit` mode. Click :guilabel:`Create` to start creating a new mailing." +#: ../../content/applications/marketing/email_marketing/lost_leads_email.rst:0 +msgid "The # record(s) text is located below the list of Recipient filters." msgstr "" -#: ../../content/applications/marketing/email_marketing.rst:434 -msgid "By default, there's a daily limit applied for **all emails** sent throughout *all* applications. So, if there are remaining emails to be sent after a limit has been reached, those mailings *will not* be sent automatically the next day. The sending needs to be forced, by opening the email and clicking :guilabel:`Retry`." +#: ../../content/applications/marketing/email_marketing/lost_leads_email.rst:43 +msgid "Minimum requirements" +msgstr "" + +#: ../../content/applications/marketing/email_marketing/lost_leads_email.rst:45 +msgid "In order to create and deliver a lost leads reactivation email campaign, the *CRM* and *Email Marketing* applications **must** be :ref:`installed ` and configured." +msgstr "" + +#: ../../content/applications/marketing/email_marketing/lost_leads_email.rst:48 +msgid "Here are the minimum necessary filters that pertain to a lost leads reactivation mailing campaign:" +msgstr "" + +#: ../../content/applications/marketing/email_marketing/lost_leads_email.rst:50 +msgid "The :ref:`Recipients ` field **must** be set to the *Lead/Opportunity* model." +msgstr "" + +#: ../../content/applications/marketing/email_marketing/lost_leads_email.rst:52 +msgid "A :ref:`Blacklist ` filter to exclude unsubscribed recipients." +msgstr "" + +#: ../../content/applications/marketing/email_marketing/lost_leads_email.rst:53 +msgid "A :ref:`Created on ` to target leads that were lost during a specific period of time." +msgstr "" + +#: ../../content/applications/marketing/email_marketing/lost_leads_email.rst:55 +msgid ":ref:`Stage ` filter(s) to exclude leads that were already won, or are still active in new stages of the sales pipeline (i.e. *New*, *Qualified*, etc.). These values will be different per organization; however, it's minimally viable to exclude all the leads in the *Won* stage." +msgstr "" + +#: ../../content/applications/marketing/email_marketing/lost_leads_email.rst:59 +msgid "One or more :ref:`Lost Reason ` filters to exclude undesired leads, such as duplicate, spam, or irrelevant records." +msgstr "" + +#: ../../content/applications/marketing/email_marketing/lost_leads_email.rst:61 +msgid "A pair of :ref:`Active ` filters to target *both* active and inactive leads." +msgstr "" + +#: ../../content/applications/marketing/email_marketing/lost_leads_email.rst:65 +msgid "Add the necessary filters" +msgstr "" + +#: ../../content/applications/marketing/email_marketing/lost_leads_email.rst:67 +msgid "First, navigate to the :menuselection:`Email Marketing` app, and on the :guilabel:`Mailings` page, click the :guilabel:`New` button in the top-left corner." +msgstr "" + +#: ../../content/applications/marketing/email_marketing/lost_leads_email.rst:72 +msgid "On the new :guilabel:`Mailings` form, enter an appropriate :guilabel:`Subject` line for the email in the corresponding field. Then, in the :guilabel:`Recipients` field, choose the :guilabel:`Lead/Opportunity` model from the drop-down menu." +msgstr "" + +#: ../../content/applications/marketing/email_marketing/lost_leads_email.rst:78 +msgid "In the rules section, located beneath the :guilabel:`Recipients` field, click the modify filter (:guilabel:`▶ (triangle pointing right)`) icon to expand the filter rules. Leave the default :guilabel:`Blacklist` rule in place." +msgstr "" + +#: ../../content/applications/marketing/email_marketing/lost_leads_email.rst:85 +msgid "Created on" +msgstr "" + +#: ../../content/applications/marketing/email_marketing/lost_leads_email.rst:87 +msgid "Begin by clicking :guilabel:`New Rule` beneath the default :guilabel:`Blacklist` rule. Then, click the first field of the new rule that appears, and select the :guilabel:`Created on` parameter from the drop-down menu. With that in place, a specific time period during which the targeted leads were lost can be designated (e.g. 30 days prior, 90 days prior, previous year, etc.)." +msgstr "" + +#: ../../content/applications/marketing/email_marketing/lost_leads_email.rst:92 +msgid "Then, in the second field, select :guilabel:`<= (less than or equal to)`, :guilabel:`>= (greater than or equal to)`, or :guilabel:`is between` as a date operator, in order to frame the time selection chosen in the third field." +msgstr "" + +#: ../../content/applications/marketing/email_marketing/lost_leads_email.rst:96 +msgid "In the third field, use the calendar popover window to select dates, and click :guilabel:`Apply` to lock in the time range." +msgstr "" + +#: ../../content/applications/marketing/email_marketing/lost_leads_email.rst:-1 +msgid "A custom filter rule setting the time period to be anything before today's date." +msgstr "" + +#: ../../content/applications/marketing/email_marketing/lost_leads_email.rst:104 +msgid "When there is more than one rule applied, make sure the statement at the top of the :guilabel:`Recipients` filter list reads: :guilabel:`Match all of the following rules`. If it does not, click on the statement, and select :guilabel:`all` from the drop-down menu (as opposed to :guilabel:`any`)." +msgstr "" + +#: ../../content/applications/marketing/email_marketing/lost_leads_email.rst:0 +msgid "The statement at the top of the filters list, with the drop-down menu open." +msgstr "" + +#: ../../content/applications/marketing/email_marketing/lost_leads_email.rst:116 +msgid "Stage" +msgstr "" + +#: ../../content/applications/marketing/email_marketing/lost_leads_email.rst:118 +msgid "Now, add the :guilabel:`Stage` filter to exclude leads that are in the *New*, *Qualified*, and *Won* stages of the sales pipeline." +msgstr "" + +#: ../../content/applications/marketing/email_marketing/lost_leads_email.rst:122 +msgid "This step assumes that the *New*, *Qualified*, and *Won* stages exist in the CRM pipeline; however, stage names may differ from business to business. Refer to the database's actual stage names in the *CRM* app's pipeline to complete this step, accordingly." +msgstr "" + +#: ../../content/applications/marketing/email_marketing/lost_leads_email.rst:126 +msgid "Begin again by clicking :guilabel:`New Rule` and select :guilabel:`Stage` from the first field's drop-down menu. In the second field, select the :guilabel:`is not in` operator, and in the third field, select the :guilabel:`New`, :guilabel:`Qualified` and :guilabel:`Won` stages to define the rule's parameters." +msgstr "" + +#: ../../content/applications/marketing/email_marketing/lost_leads_email.rst:131 +msgid "When the rule is added in this way, the logic in the third field renders as :code:`OR` (`|`) statements." +msgstr "" + +#: ../../content/applications/marketing/email_marketing/lost_leads_email.rst:-1 +msgid "Include multiple Stages in the filtering rule, using the \"is in\" operator." +msgstr "" + +#: ../../content/applications/marketing/email_marketing/lost_leads_email.rst:139 +msgid "Another way to add *Stage* rules, is to do so on a one-rule-per-row basis using the :guilabel:`contains` or :guilabel:`does not contain` operators, and manually typing out the defining characters in each stage name. This method, however, only allows for one selection at a time, which can be useful for quickly turning on/off filters in the :guilabel:`Search...` bar." +msgstr "" + +#: ../../content/applications/marketing/email_marketing/lost_leads_email.rst:0 +msgid "Three filter rules requiring that the Stage does not contain New, Qualified, or Won." +msgstr "" + +#: ../../content/applications/marketing/email_marketing/lost_leads_email.rst:151 +msgid "Lost Reason" +msgstr "" + +#: ../../content/applications/marketing/email_marketing/lost_leads_email.rst:153 +msgid "Next, add one or more :guilabel:`Lost Reason` rules to exclude leads that should **not** be targeted for specific :doc:`lost reasons <../../sales/crm/pipeline/lost_opportunities>`." +msgstr "" + +#: ../../content/applications/marketing/email_marketing/lost_leads_email.rst:156 +msgid "To do that, create another :guilabel:`New Rule`, once again. Then, in the rule's first field, select :guilabel:`Lost Reason` from the drop-down menu. For the operator, choose either :guilabel:`is not in` or :guilabel:`does not contain` from the drop-down menu. With either selection, use the third field to enter a lost reason (or multiple lost reasons, depending on your operator choice) to include in the rule." +msgstr "" + +#: ../../content/applications/marketing/email_marketing/lost_leads_email.rst:162 +msgid "If choosing the :guilabel:`does not contain` operator, then repeat the preceding steps to add more lost reasons, as needed, where each lost reason occupies one rule row at a time." +msgstr "" + +#: ../../content/applications/marketing/email_marketing/lost_leads_email.rst:165 +msgid "For more information, refer to the section below outlining how to :ref:`select appropriate lost reasons `." +msgstr "" + +#: ../../content/applications/marketing/email_marketing/lost_leads_email.rst:-1 +msgid "A list of filter rules that exclude all lost reasons other than the desired reason." +msgstr "" + +#: ../../content/applications/marketing/email_marketing/lost_leads_email.rst:175 +msgid "Active" +msgstr "" + +#: ../../content/applications/marketing/email_marketing/lost_leads_email.rst:177 +msgid "Finally, add a pair of :guilabel:`Active` filters to include both active and inactive leads for the campaign." +msgstr "" + +#: ../../content/applications/marketing/email_marketing/lost_leads_email.rst:181 +msgid "Adding both active *and* inactive lead records is necessary to capture the full scope of lost leads in the database. Doing one without the other greatly impacts the number of targetable records for the email campaign, and does **not** include a complete or accurate lost leads audience." +msgstr "" + +#: ../../content/applications/marketing/email_marketing/lost_leads_email.rst:186 +msgid "First, click the :guilabel:`(Add Branch)` icon on the most recently created rule (e.g. :guilabel:`Lost Reason`), which is the middle of three icons located to the right of the rule row. Doing so adds a pair of :guilabel:`any of` rules. Then, in the top rule's first field of the newly-created branch, select the :guilabel:`Active` parameter from the drop-down menu. The rule then automatically fills out to read: :guilabel:`Active` *is* `set`." +msgstr "" + +#: ../../content/applications/marketing/email_marketing/lost_leads_email.rst:192 +msgid "For the first field of the bottom rule of the branch, select :guilabel:`Active` from the drop-down menu again. However, this time, select :guilabel:`is not` from the operator drop-down menu in the second field. The rule should then read: :guilabel:`Active` *is not* `set`." +msgstr "" + +#: ../../content/applications/marketing/email_marketing/lost_leads_email.rst:-1 +msgid "A pair of Match Any Of filter rules that include both active and inactive leads." +msgstr "" + +#: ../../content/applications/marketing/email_marketing/lost_leads_email.rst:201 +msgid "Add body content" +msgstr "" + +#: ../../content/applications/marketing/email_marketing/lost_leads_email.rst:203 +msgid "Now, with the domain section of the email campaign complete, create the body content of the email using any of the premade stylized templates, or choose between the :guilabel:`Plain Text` or :guilabel:`Start From Scratch` options for more granular control. For more information, refer to the *Email Marketing* :ref:`documentation on how to create an email `." +msgstr "" + +#: ../../content/applications/marketing/email_marketing/lost_leads_email.rst:209 +msgid "To save the set of filters for later use, click :guilabel:`Save as Favorite Filter 💾 (floppy disk)`, enter a name (such as `Lost Leads`), and click :guilabel:`Add`." +msgstr "" + +#: ../../content/applications/marketing/email_marketing/lost_leads_email.rst:0 +msgid "The Save as Favorite Filter pop-up can save the lost leads criteria for later." +msgstr "" + +#: ../../content/applications/marketing/email_marketing/lost_leads_email.rst:217 +msgid "Send or schedule" +msgstr "" + +#: ../../content/applications/marketing/email_marketing/lost_leads_email.rst:219 +msgid "Once all the components of the email campaign are complete, either:" +msgstr "" + +#: ../../content/applications/marketing/email_marketing/lost_leads_email.rst:221 +msgid "click the purple :guilabel:`Send` button at the top-left of the form to immediately send the email; or" +msgstr "" + +#: ../../content/applications/marketing/email_marketing/lost_leads_email.rst:223 +msgid "click the gray :guilabel:`Schedule` button, located to the right of the :guilabel:`Send` button, to send the email at a future date and time." +msgstr "" + +#: ../../content/applications/marketing/email_marketing/lost_leads_email.rst:227 +msgid "Consider using *A/B Testing* to send an alternate version of the email to a percentage of the target leads. This can help determine what subject lines and body content produce the best click-through rates, before sending a final version to the remaining leads." +msgstr "" + +#: ../../content/applications/marketing/email_marketing/lost_leads_email.rst:231 +msgid "To do so, open the :guilabel:`A/B Tests` tab on the mailing form and check the box next to :guilabel:`Allow A/B Testing`. Then, adjust the parameters as needed, and click :guilabel:`Create an Alternative Version`." +msgstr "" + +#: ../../content/applications/marketing/email_marketing/lost_leads_email.rst:0 +msgid "The A/B Tests tab with the Allow A/B Testing box checked to create an alternate version." +msgstr "" + +#: ../../content/applications/marketing/email_marketing/lost_leads_email.rst:242 +msgid "Select appropriate lost reasons" +msgstr "" + +#: ../../content/applications/marketing/email_marketing/lost_leads_email.rst:244 +msgid "When a lead is marked as lost, Odoo recommends selecting a *Lost Reason* to indicate why the opportunity did not result in a sale. Doing so keeps the pipeline organized and reporting data accurate, and generates potential to follow up with the lead in the future." +msgstr "" + +#: ../../content/applications/marketing/email_marketing/lost_leads_email.rst:248 +msgid "If an existing *Lost Reason* is not applicable, users with the necessary permissions can create new ones, which means the lost reasons in a database can vary from organization to organization, and from pipeline to pipeline." +msgstr "" + +#: ../../content/applications/marketing/email_marketing/lost_leads_email.rst:252 +msgid "For more information on *Lost Reasons*, including the creation of them, refer to :doc:`../../sales/crm/pipeline/lost_opportunities`." +msgstr "" + +#: ../../content/applications/marketing/email_marketing/lost_leads_email.rst:255 +msgid "By default, Odoo includes a few common *Lost Reasons*, such as:" +msgstr "" + +#: ../../content/applications/marketing/email_marketing/lost_leads_email.rst:257 +msgid "*Too expensive*" +msgstr "" + +#: ../../content/applications/marketing/email_marketing/lost_leads_email.rst:258 +msgid "*We don't have people/skills*" +msgstr "" + +#: ../../content/applications/marketing/email_marketing/lost_leads_email.rst:259 +msgid "*Not enough stock*" +msgstr "" + +#: ../../content/applications/marketing/email_marketing/lost_leads_email.rst:261 +msgid "When determining which reasons to include in a lost leads reactivation email, consider what the email is advertising, in order pinpoint one or more relevant lost reasons. Then, add a rule stating, :guilabel:`Lost Reason` *does not contain* `_____` for every reason in the database, **except** for the relevant one(s)." +msgstr "" + +#: ../../content/applications/marketing/email_marketing/lost_leads_email.rst:267 +msgid "If the email advertises a selection of previously-limited merchandise that is now back in stock, it makes sense to target leads with the lost reason: *not enough stock*." +msgstr "" + +#: ../../content/applications/marketing/email_marketing/lost_leads_email.rst:0 +msgid "A list of filter rules that exclude all lost reasons except for Out of Stock." +msgstr "" + +#: ../../content/applications/marketing/email_marketing/lost_leads_email.rst:274 +msgid "If the email advertises a price reduction, it makes sense to target leads with the lost reason: *too expensive*." +msgstr "" + +#: ../../content/applications/marketing/email_marketing/lost_leads_email.rst:0 +msgid "A list of filter rules that exclude all lost reasons except for Too Expensive." +msgstr "" + +#: ../../content/applications/marketing/email_marketing/lost_leads_email.rst:282 +msgid "Analyze the results" +msgstr "" + +#: ../../content/applications/marketing/email_marketing/lost_leads_email.rst:284 +msgid "After sending a lost leads reactivation email, marketing teams can use the smart buttons along the top of the email to analyze the results, and determine follow-up actions." +msgstr "" + +#: ../../content/applications/marketing/email_marketing/lost_leads_email.rst:287 +msgid "Clicking on any of the smart buttons opens a list of records matching that button's specific criteria." +msgstr "" + +#: ../../content/applications/marketing/email_marketing/lost_leads_email.rst:-1 +msgid "The Mailing page of a sent email showing the smart buttons along the top of the page." +msgstr "" + +#: ../../content/applications/marketing/email_marketing/lost_leads_email.rst:294 +msgid "The smart buttons include:" +msgstr "" + +#: ../../content/applications/marketing/email_marketing/lost_leads_email.rst:296 +msgid ":guilabel:`Sent`: total number of emails sent." +msgstr "" + +#: ../../content/applications/marketing/email_marketing/lost_leads_email.rst:297 +msgid ":guilabel:`Opened`: percentage of recipients that opened the email." +msgstr "" + +#: ../../content/applications/marketing/email_marketing/lost_leads_email.rst:298 +msgid ":guilabel:`Replied`: percentage of recipients that replied to the email." +msgstr "" + +#: ../../content/applications/marketing/email_marketing/lost_leads_email.rst:299 +msgid ":guilabel:`Clicked`: click-through rate (%) of recipients that clicked on a link in the email." +msgstr "" + +#: ../../content/applications/marketing/email_marketing/lost_leads_email.rst:300 +msgid ":guilabel:`Leads/Opportunities`: number of leads (or opportunities) that have been created in the *CRM* pipeline, as a result of the email campaign." +msgstr "" + +#: ../../content/applications/marketing/email_marketing/lost_leads_email.rst:302 +msgid ":guilabel:`Quotations`: number of quotations that have been created in the *Sales* application, as a result of the email." +msgstr "" + +#: ../../content/applications/marketing/email_marketing/lost_leads_email.rst:304 +msgid ":guilabel:`Invoiced`: total revenues generated, as a result of the email campaign, via invoices sent to, and paid by, customers. These values are recorded in either the *Invoicing* or *Accounting* application, depending on which app is installed in the database." +msgstr "" + +#: ../../content/applications/marketing/email_marketing/lost_leads_email.rst:307 +msgid ":guilabel:`Received`: percentage of recipients that received the email." +msgstr "" + +#: ../../content/applications/marketing/email_marketing/lost_leads_email.rst:308 +msgid ":guilabel:`Bounced`: percentage of emails that bounced (:dfn:`not delivered`)." +msgstr "" + +#: ../../content/applications/marketing/email_marketing/lost_leads_email.rst:309 +msgid ":guilabel:`Ignored`: the number of recipients that received the email, but have not interacted with it in a meaningful way (i.e. opened, clicked, etc.)." +msgstr "" + +#: ../../content/applications/marketing/email_marketing/lost_leads_email.rst:313 +msgid "Email nurturing" +msgstr "" + +#: ../../content/applications/marketing/email_marketing/lost_leads_email.rst:315 +msgid "*Email nurturing* (sometimes referred to as *lead nurturing*) is the process of sending a series of timely and relevant \"nudge\" emails to connect with a lead, build a deeper relationship, and ultimately convert the lead into a sale." +msgstr "" + +#: ../../content/applications/marketing/email_marketing/lost_leads_email.rst:319 +msgid "The point of nurturing is to keep the email campaign \"visible\" or at the top of a lead's inbox, until they are ready to buy." +msgstr "" + +#: ../../content/applications/marketing/email_marketing/lost_leads_email.rst:322 +msgid "There are many approaches to effective lead nurturing, but they often involve:" +msgstr "" + +#: ../../content/applications/marketing/email_marketing/lost_leads_email.rst:324 +msgid "Sending an initial email (such as, a lost leads reactivation email)." +msgstr "" + +#: ../../content/applications/marketing/email_marketing/lost_leads_email.rst:325 +msgid "Sending a follow-up email each week (or according to specific triggers) for the duration of the campaign." +msgstr "" + +#: ../../content/applications/marketing/email_marketing/lost_leads_email.rst:327 +msgid "Continuously analyzing results to learn what approaches have resulted in sales." +msgstr "" + +#: ../../content/applications/marketing/email_marketing/lost_leads_email.rst:328 +msgid "Continuously adjusting the approach to remain \"visible\" at the top of the lead's inbox, and hopefully, get a meaningful response from the lead." +msgstr "" + +#: ../../content/applications/marketing/email_marketing/lost_leads_email.rst:331 +msgid "As a campaign progresses, a marketing team may send different follow-up emails depending on how a lead responded the previous week." +msgstr "" + +#: ../../content/applications/marketing/email_marketing/lost_leads_email.rst:335 +msgid "A marketing team wants to advertise a restocking of limited-run merchandise to all leads with a lost reason of *not enough stock*. They develop the following three-week long lead nurturing campaign." +msgstr "" + +#: ../../content/applications/marketing/email_marketing/lost_leads_email.rst:339 +msgid "**Week 1:** the marketing team sends an initial email, with the subject line: *“Limited run merchandise is back in stock! Act now!”*" +msgstr "" + +#: ../../content/applications/marketing/email_marketing/lost_leads_email.rst:341 +msgid "**Week 2:** the marketing team sends two different emails, depending on how a lead responded." +msgstr "" + +#: ../../content/applications/marketing/email_marketing/lost_leads_email.rst:343 +msgid "If a lead ignored the Week 1 email: *“Stock is almost out, did you get yours?”*" +msgstr "" + +#: ../../content/applications/marketing/email_marketing/lost_leads_email.rst:344 +msgid "If a lead clicked on the Week 1 email: *\"You still have time to add this to your collection\"*" +msgstr "" + +#: ../../content/applications/marketing/email_marketing/lost_leads_email.rst:346 +msgid "**Week 3:** the marketing team sends a final email to all leads who have not been converted stating: *“20% off, don't miss your last chance to get these items before they're gone!”*" +msgstr "" + +#: ../../content/applications/marketing/email_marketing/lost_leads_email.rst:349 +msgid "Throughout the campaign, the marketing team continuously refers to the smart buttons along the top of the mailing page to see what percentages of leads are opening, clicking on, or ignoring the emails. They also regularly analyze reports on how many opportunities, quotations, and invoices have been generated by the campaign." +msgstr "" + +#: ../../content/applications/marketing/email_marketing/lost_leads_email.rst:355 +#: ../../content/applications/marketing/email_marketing/mailing_lists.rst:223 +#: ../../content/applications/marketing/email_marketing/unsubscriptions.rst:129 +msgid ":doc:`../email_marketing`" +msgstr "" + +#: ../../content/applications/marketing/email_marketing/lost_leads_email.rst:356 +#: ../../content/applications/marketing/email_marketing/mailing_lists.rst:224 +msgid ":doc:`unsubscriptions`" +msgstr "" + +#: ../../content/applications/marketing/email_marketing/lost_leads_email.rst:357 +msgid ":doc:`../marketing_automation`" msgstr "" #: ../../content/applications/marketing/email_marketing/mailing_lists.rst:3 @@ -817,15 +1723,6 @@ msgstr "" msgid "Now, when a visitor enters their email address, and clicks the button to subscribe, they are instantly subscribed to that pre-configured mailing list. They are also added as a contact for that mailing list in Odoo *Email Marketing*." msgstr "" -#: ../../content/applications/marketing/email_marketing/mailing_lists.rst:223 -#: ../../content/applications/marketing/email_marketing/unsubscriptions.rst:129 -msgid ":doc:`../email_marketing`" -msgstr "" - -#: ../../content/applications/marketing/email_marketing/mailing_lists.rst:224 -msgid ":doc:`unsubscriptions`" -msgstr "" - #: ../../content/applications/marketing/email_marketing/unsubscriptions.rst:3 msgid "Manage unsubscriptions (blacklist)" msgstr "" @@ -1564,7 +2461,7 @@ msgid "While the application is designed to be user-friendly for quickly creatin msgstr "" #: ../../content/applications/marketing/marketing_automation.rst:15 -msgid "Get started by creating a :ref:`new campaign from scratch ` or start with a :ref:`campaign template `." +msgid "Get started by creating a :ref:`new campaign from scratch ` or start with a :ref:`campaign template `." msgstr "" #: ../../content/applications/marketing/marketing_automation.rst:19 @@ -1602,7 +2499,7 @@ msgid "A *campaign* refers to a workflow of activities that are automatically ex msgstr "" #: ../../content/applications/marketing/marketing_automation.rst:71 -msgid "A new campaign can be created from scratch or from a :ref:`template `." +msgid "A new campaign can be created from scratch or from a :ref:`template `." msgstr "" #: ../../content/applications/marketing/marketing_automation.rst:74 @@ -1728,7 +2625,7 @@ msgid "The number of participants engaged in a running, or stopped, campaign are msgstr "" #: ../../content/applications/marketing/marketing_automation.rst:151 -msgid ":doc:`Target an audience `" +msgid ":doc:`Audience targeting `" msgstr "" #: ../../content/applications/marketing/marketing_automation.rst:154 @@ -1740,6 +2637,7 @@ msgid "A *workflow* consists of an activity, many activities, or a sequence of a msgstr "" #: ../../content/applications/marketing/marketing_automation.rst:160 +#: ../../content/applications/marketing/marketing_automation/workflow_activities.rst:19 msgid "Activities" msgstr "" @@ -1752,200 +2650,190 @@ msgid "To create one of the following activities, click :guilabel:`Add new activ msgstr "" #: ../../content/applications/marketing/marketing_automation.rst:169 -msgid ":guilabel:`Email`: send an email to the target audience." -msgstr "" - -#: ../../content/applications/marketing/marketing_automation.rst:170 -msgid ":guilabel:`SMS`: send an SMS to the target audience." +#: ../../content/applications/marketing/marketing_automation/workflow_activities.rst:53 +msgid ":ref:`Email `: an email that is sent to the target audience." msgstr "" #: ../../content/applications/marketing/marketing_automation.rst:171 -msgid ":guilabel:`Server Action`: executes an automated action." +#: ../../content/applications/marketing/marketing_automation/workflow_activities.rst:55 +msgid ":ref:`Server action `: an internal action within the database that is executed." msgstr "" -#: ../../content/applications/marketing/marketing_automation.rst:174 -msgid ":doc:`marketing_automation/workflow_activities`" +#: ../../content/applications/marketing/marketing_automation.rst:173 +#: ../../content/applications/marketing/marketing_automation/workflow_activities.rst:57 +msgid ":ref:`SMS `: a text message that is sent to the target audience." msgstr "" #: ../../content/applications/marketing/marketing_automation.rst:177 +msgid ":doc:`marketing_automation/workflow_activities`" +msgstr "" + +#: ../../content/applications/marketing/marketing_automation.rst:180 msgid "Testing and running" msgstr "" -#: ../../content/applications/marketing/marketing_automation.rst:179 +#: ../../content/applications/marketing/marketing_automation.rst:182 msgid "Once a campaign has been created, it can be tested to ensure the workflow is functioning as expected, to check for errors, and correct any mistakes before it reaches its target audience." msgstr "" -#: ../../content/applications/marketing/marketing_automation.rst:182 +#: ../../content/applications/marketing/marketing_automation.rst:185 msgid "After testing, the campaign can be launched to start engaging the target audience. The campaign can also be launched *without* testing, if the user is confident in the workflow." msgstr "" -#: ../../content/applications/marketing/marketing_automation.rst:186 +#: ../../content/applications/marketing/marketing_automation.rst:189 msgid ":doc:`marketing_automation/testing_running`" msgstr "" -#: ../../content/applications/marketing/marketing_automation.rst:189 +#: ../../content/applications/marketing/marketing_automation.rst:192 msgid "Reporting" msgstr "" -#: ../../content/applications/marketing/marketing_automation.rst:191 +#: ../../content/applications/marketing/marketing_automation.rst:194 msgid "A range of reporting metrics are available to measure the success of each campaign. Navigate to :menuselection:`Marketing Automation app --> Reporting` to access the following menu options:" msgstr "" -#: ../../content/applications/marketing/marketing_automation.rst:194 +#: ../../content/applications/marketing/marketing_automation.rst:197 msgid ":guilabel:`Link Tracker`: displays the metrics of links to track the number of clicks." msgstr "" -#: ../../content/applications/marketing/marketing_automation.rst:195 +#: ../../content/applications/marketing/marketing_automation.rst:198 msgid ":guilabel:`Traces`: displays the results of all activities from all campaigns." msgstr "" -#: ../../content/applications/marketing/marketing_automation.rst:196 +#: ../../content/applications/marketing/marketing_automation.rst:199 msgid ":guilabel:`Participants`: displays an overview of the participants of all campaigns." msgstr "" -#: ../../content/applications/marketing/marketing_automation.rst:198 +#: ../../content/applications/marketing/marketing_automation.rst:201 msgid "Additionally, each activity within the workflow of a campaign displays its engagement metrics." msgstr "" -#: ../../content/applications/marketing/marketing_automation.rst:201 +#: ../../content/applications/marketing/marketing_automation.rst:204 msgid ":doc:`marketing_automation/understanding_metrics`" msgstr "" #: ../../content/applications/marketing/marketing_automation/target_audience.rst:3 -msgid "Target an audience" +msgid "Audience targeting" msgstr "" #: ../../content/applications/marketing/marketing_automation/target_audience.rst:5 -msgid "Delivering marketing campaigns to the right audience is paramount when trying to grow a business. The Odoo *Marketing Automation* application helps marketers to do just that by providing detailed filtering tools, which can be as simple (or as complex) as necessary, to reach the right customers at the right time." +msgid "The :guilabel:`Target` and :guilabel:`Filter` fields on the campaign form, also referred to as the *domain*, contain the parameters used to define the target audience for the campaign's reach (i.e., the unique contact records in the database, and imported list, etc.)." msgstr "" -#: ../../content/applications/marketing/marketing_automation/target_audience.rst:11 -msgid "Configure target filters" +#: ../../content/applications/marketing/marketing_automation/target_audience.rst:9 +msgid ":guilabel:`Target`: specifies the type of records available for use in the campaign, such as :guilabel:`Lead/Opportunity`, :guilabel:`Event Registration`, :guilabel:`Contact`, The assigned records model determines the fields that are available throughout the campaign, including the fields available in the :guilabel:`Filter` section, and in dynamic placeholders." msgstr "" #: ../../content/applications/marketing/marketing_automation/target_audience.rst:13 -msgid "When configuring the target filters on a marketing campaign, there are some options that have an :guilabel:`> (arrow)` icon beside them. The :guilabel:`> (arrow)` icon signifies that the particular filter has more refined parameters within it that can be customized." +msgid ":guilabel:`Save as Favorite Filter`: saves the current :guilabel:`Filter` for future use with the current :guilabel:`Target` model, and can be managed from the :menuselection:`Marketing Automation app --> Configuration --> Favorite Filters` menu." msgstr "" -#: ../../content/applications/marketing/marketing_automation/target_audience.rst:-1 -#: ../../content/applications/marketing/marketing_automation/target_audience.rst:-1 -msgid "The drop-down filter menu in the Marketing Automation application." +#: ../../content/applications/marketing/marketing_automation/target_audience.rst:16 +msgid ":guilabel:`Unicity based on`: specifies the :guilabel:`Target` model field where duplicates should be avoided. Traditionally, the :guilabel:`Email` field is used, but any available field can be used." msgstr "" -#: ../../content/applications/marketing/marketing_automation/target_audience.rst:21 -msgid "Filters can be extended by adding *branches* and *nodes*. A *node* adds another filtering parameter to a group of targeting conditions (e.g. a new line), and a *branch* creates a narrowly refined cluster of parameters, allowing filters to be grouped with :guilabel:`ANY` or :guilabel:`ALL` statements." +#: ../../content/applications/marketing/marketing_automation/target_audience.rst:19 +msgid ":guilabel:`Filter`: contains an interactive form with configurable logic to further refine the targeting parameters under the chosen :guilabel:`Target` model. See more details in the :ref:`marketing_automation/defining-filters` section." +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/target_audience.rst:22 +msgid ":guilabel:`Include archived`: allows or disallows the inclusion of archived records in the target audience." msgstr "" #: ../../content/applications/marketing/marketing_automation/target_audience.rst:26 -msgid "Every time a new branch is created, there are two options:" -msgstr "" - -#: ../../content/applications/marketing/marketing_automation/target_audience.rst:28 -msgid "Either the records can match :guilabel:`ALL` criteria for the upcoming rules (creating an AND statement where *all* criteria must match)." +msgid "A :guilabel:`Responsible` user can be assigned to the campaign by activating :ref:`developer-mode`." msgstr "" #: ../../content/applications/marketing/marketing_automation/target_audience.rst:30 -msgid "Or, the records can match :guilabel:`ANY` criteria for the upcoming rules (creating an OR statement where *only one* of the criteria must match)." -msgstr "" - -#: ../../content/applications/marketing/marketing_automation/target_audience.rst:33 -msgid "To change between these two options, simply click the drop-down arrow icon in the green box and select :guilabel:`ANY` or :guilabel:`ALL`." +msgid "Each activity in a campaign's workflow can target a subset of the target audience; see the :doc:`workflow_activities` documentation for more information." msgstr "" #: ../../content/applications/marketing/marketing_automation/target_audience.rst:36 -msgid "To add a node, click on the :guilabel:`➕ (plus sign)` icon, and to add another branch click on the :guilabel:`⋯ (ellipses)` icon. To exclude a node or a branch, click on :guilabel:`✖ (delete)` icon to delete it." +msgid "Defining filters" msgstr "" -#: ../../content/applications/marketing/marketing_automation/target_audience.rst:45 -msgid "Use cases" +#: ../../content/applications/marketing/marketing_automation/target_audience.rst:38 +msgid "The default campaign :guilabel:`Filter` configuration is set to :guilabel:`Match all records`, indicating that the campaign is targeting **all** records of the :guilabel:`Target` model." msgstr "" -#: ../../content/applications/marketing/marketing_automation/target_audience.rst:47 -msgid "The following scenarios outline different combinations of filters a marketing campaign might commonly use." +#: ../../content/applications/marketing/marketing_automation/target_audience.rst:41 +msgid "To refine the :guilabel:`Filter` rules of a campaign, click the :guilabel:`➕ Add condition` button to reveal a new row with configurable rule parameters. See the :ref:`Search, filter, and group records ` documentation for more information on how to create filter rules." msgstr "" -#: ../../content/applications/marketing/marketing_automation/target_audience.rst:51 -msgid "Scenario #1: Narrow target down to new opportunities in the pipeline" +#: ../../content/applications/marketing/marketing_automation/target_audience.rst:-1 +msgid "A new filter rule row on the campaign form Filters." msgstr "" -#: ../../content/applications/marketing/marketing_automation/target_audience.rst:53 -msgid "While in *Edit mode* on a campaign template form (by clicking the :guilabel:`Edit` button), select the :guilabel:`Target` field, and click :guilabel:`Search More` from the drop-down menu. Then, search for :guilabel:`Lead/Opportunity`, and select it." +#: ../../content/applications/marketing/marketing_automation/target_audience.rst:49 +msgid "At the bottom of the filter rules is a :guilabel:`# record(s)` button, which indicates the total number of records targeted by this domain. Select the :guilabel:`# record(s)` button to open a :guilabel:`Selected records` pop-up window, in which the targeted records can be viewed." msgstr "" -#: ../../content/applications/marketing/marketing_automation/target_audience.rst:57 -msgid "Next, click :guilabel:`Add Filter` in the :guilabel:`Filter` field. Then, click on the default :guilabel:`ID` filter option in the first portion of the filter equation. Doing so reveals a drop-down menu full of filter options. From this drop-down, scroll down (or search for) :guilabel:`Type`." +#: ../../content/applications/marketing/marketing_automation/target_audience.rst:54 +msgid "Activate :ref:`developer-mode` to reveal each field's technical name and data type, as well as the :guilabel:`# Code editor` text area below the filter rules, to view and edit the domain manually." +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/target_audience.rst:59 +msgid "To target all leads and opportunities from the *CRM* app that are in the *New* stage, and have an expected revenue greater than $1,000, the following should be entered:" msgstr "" #: ../../content/applications/marketing/marketing_automation/target_audience.rst:62 -msgid "Keep the second portion of the filter equation on the default :guilabel:`🟰 (equal sign)` icon." +msgid ":guilabel:`Target`: `Lead/Opportunity`" +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/target_audience.rst:63 +msgid ":guilabel:`Unicity based on`: `Email (Lead/Opportunity)`" msgstr "" #: ../../content/applications/marketing/marketing_automation/target_audience.rst:64 -msgid "Next, change the third (and final) portion of the filter equation from :guilabel:`Lead` to :guilabel:`Opportunity`. The number of :guilabel:`Records` that fit this specific filter equation changes as the equation is customized." +msgid ":guilabel:`Filter`: :guilabel:`Match` :guilabel:`all 🔽 (down arrow)` :guilabel:`of the following rules:`" +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/target_audience.rst:67 +msgid ":guilabel:`Stage` :guilabel:`is in` :guilabel:`New`" msgstr "" #: ../../content/applications/marketing/marketing_automation/target_audience.rst:68 -msgid "Add another node to this filter by clicking the :guilabel:`➕ (plus sign)` icon to the right of the equation." +msgid ":guilabel:`Expected Revenue` :guilabel:`>` `1,000`" +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/target_audience.rst:69 +msgid ":guilabel:`any 🔽 (down arrow)` :guilabel:`of:`" msgstr "" #: ../../content/applications/marketing/marketing_automation/target_audience.rst:71 -msgid "With \"new\" opportunities being the target of this filter, the second node will focus on *only* locating opportunities that are in the :guilabel:`New` stage of the pipeline. To do that, select the default :guilabel:`ID` from the first portion of the second filter equation, and scroll down (or search for) :guilabel:`Stage` from the field drop-down menu." +msgid ":guilabel:`Type` :guilabel:`=` :guilabel:`Lead`" msgstr "" -#: ../../content/applications/marketing/marketing_automation/target_audience.rst:76 -msgid "Once again, leave the second portion of the filter equation on :guilabel:`🟰 (equal sign)` icon." +#: ../../content/applications/marketing/marketing_automation/target_audience.rst:72 +msgid ":guilabel:`Type` :guilabel:`=` :guilabel:`Opportunity`" msgstr "" -#: ../../content/applications/marketing/marketing_automation/target_audience.rst:78 -msgid "Lastly, highlight the default value in the third (and final) portion of the second filter equation, and type in `New`. With that in place, Odoo only targets opportunities that are in the \"New\" stage of the pipeline." +#: ../../content/applications/marketing/marketing_automation/target_audience.rst:74 +msgid "With the above configuration, the campaign targets :guilabel:`157 record(s)`." msgstr "" -#: ../../content/applications/marketing/marketing_automation/target_audience.rst:-1 -msgid "A standard scenario using filters in the Odoo Marketing Automation app." +#: ../../content/applications/marketing/marketing_automation/target_audience.rst:0 +msgid "A domain configuration in a Marketing Automation campaign." msgstr "" -#: ../../content/applications/marketing/marketing_automation/target_audience.rst:87 -msgid "Scenario #2: Narrow down target to event attendees who purchased a specific ticket" +#: ../../content/applications/marketing/marketing_automation/target_audience.rst:81 +msgid ":ref:`Domain developer documentation `" msgstr "" -#: ../../content/applications/marketing/marketing_automation/target_audience.rst:89 -msgid "While in *Edit mode* on a campaign template form (by clicking the :guilabel:`Edit` button), select the :guilabel:`Target` field, and click :guilabel:`Search More` from the drop-down menu. Then, scroll down (or search for) :guilabel:`Event`, and select it." +#: ../../content/applications/marketing/marketing_automation/target_audience.rst:82 +#: ../../content/applications/marketing/marketing_automation/testing_running.rst:153 +#: ../../content/applications/marketing/marketing_automation/understanding_metrics.rst:50 +msgid ":doc:`workflow_activities`" msgstr "" -#: ../../content/applications/marketing/marketing_automation/target_audience.rst:93 -msgid "Next, click :guilabel:`Add Filter` in the :guilabel:`Filter` field. Click on the default :guilabel:`ID` filter option in the first portion of the filter equation. Doing so reveals a drop-down menu full of filter options. From this drop-down, scroll down (or search for) :guilabel:`Event`." +#: ../../content/applications/marketing/marketing_automation/target_audience.rst:83 +#: ../../content/applications/marketing/marketing_automation/workflow_activities.rst:335 +msgid ":doc:`testing_running`" msgstr "" -#: ../../content/applications/marketing/marketing_automation/target_audience.rst:98 -msgid "Click the default :guilabel:`🟰 (equal sign)` icon in the second portion of the filter equation. This reveals a drop-down menu. From this drop-down menu, select :guilabel:`contains`." -msgstr "" - -#: ../../content/applications/marketing/marketing_automation/target_audience.rst:101 -msgid "In the third (and final) empty portion of the filter equation, type in the name of the event(s) that Odoo should consider for this campaign filter." -msgstr "" - -#: ../../content/applications/marketing/marketing_automation/target_audience.rst:104 -msgid "Then, add another node to this filter by clicking the :guilabel:`➕ (plus sign)` icon to the right of the equation." -msgstr "" - -#: ../../content/applications/marketing/marketing_automation/target_audience.rst:107 -msgid "The second node will focus on targeting this campaign to attendees who purchase a specific type of ticket to the aforementioned event(s) mentioned in the first filter equation." -msgstr "" - -#: ../../content/applications/marketing/marketing_automation/target_audience.rst:110 -msgid "To do that, select the default :guilabel:`ID` from the first portion of the second filter equation, and scroll down (or search for) :guilabel:`Event Ticket` from the field drop-down menu. Then, in that same drop-down menu, select :guilabel:`Name`." -msgstr "" - -#: ../../content/applications/marketing/marketing_automation/target_audience.rst:114 -msgid "Once again, click the default :guilabel:`🟰 (equal sign)` icon in the second portion of the filter equation, and select :guilabel:`contains`." -msgstr "" - -#: ../../content/applications/marketing/marketing_automation/target_audience.rst:117 -msgid "Lastly, in the third (and final) portion of the second filter equation, which is blank, type in the name of the ticket type that should be used for the filter. In this case, :guilabel:`Standard` is the name of the event ticket type for this sample filter." -msgstr "" - -#: ../../content/applications/marketing/marketing_automation/target_audience.rst:-1 -msgid "An event ticket filter in the Odoo Marketing Automation application." +#: ../../content/applications/marketing/marketing_automation/target_audience.rst:84 +#: ../../content/applications/marketing/marketing_automation/workflow_activities.rst:336 +msgid ":doc:`understanding_metrics`" msgstr "" #: ../../content/applications/marketing/marketing_automation/testing_running.rst:3 @@ -2117,15 +3005,10 @@ msgid ":doc:`Campaign configuration <../marketing_automation>`" msgstr "" #: ../../content/applications/marketing/marketing_automation/testing_running.rst:152 -#: ../../content/applications/marketing/marketing_automation/workflow_activities.rst:188 +#: ../../content/applications/marketing/marketing_automation/workflow_activities.rst:337 msgid ":doc:`target_audience`" msgstr "" -#: ../../content/applications/marketing/marketing_automation/testing_running.rst:153 -#: ../../content/applications/marketing/marketing_automation/understanding_metrics.rst:50 -msgid ":doc:`workflow_activities`" -msgstr "" - #: ../../content/applications/marketing/marketing_automation/understanding_metrics.rst:3 msgid "Campaign metrics" msgstr "" @@ -2302,55 +3185,60 @@ msgid "Campaign workflow activities" msgstr "" #: ../../content/applications/marketing/marketing_automation/workflow_activities.rst:5 -msgid "When creating a marketing campaign in the *Marketing Automation* app, users can plan marketing activities that can be triggered when certain actions or inactions occur. These can be activities such as, automated emails, SMS, or internal server actions." +msgid "A *workflow* is the overall *activity* structure of a marketing automation campaign. There can only be a single workflow in each campaign. However, a workflow can be made up of any number of :ref:`activities ` to meet the needs of the campaign." msgstr "" -#: ../../content/applications/marketing/marketing_automation/workflow_activities.rst:10 -msgid "Add workflow activities" +#: ../../content/applications/marketing/marketing_automation/workflow_activities.rst:13 +msgid "A workflow in an Odoo Marketing Automation campaign." msgstr "" -#: ../../content/applications/marketing/marketing_automation/workflow_activities.rst:12 -msgid "To add workflow activities to a marketing campaign, navigate to the bottom of a pre-existing or new campaign detail form, beneath the target audience configuration fields, and click :guilabel:`Add new activity`." +#: ../../content/applications/marketing/marketing_automation/workflow_activities.rst:13 +msgid "Workflow sequence of three activities; the last child activity has a :ref:`trigger type ` of **Mail: not opened**." msgstr "" -#: ../../content/applications/marketing/marketing_automation/workflow_activities.rst:16 -msgid "Doing so reveals a :guilabel:`Create Activities` pop-up window. This pop-up window is a blank activity template, where specific parameters can be set for that particular activity." +#: ../../content/applications/marketing/marketing_automation/workflow_activities.rst:21 +msgid "Activities are the methods of communication or server actions, organized in a workflow, that are executed within a campaign; they are the building blocks of the campaign's workflow." msgstr "" -#: ../../content/applications/marketing/marketing_automation/workflow_activities.rst:-1 -msgid "A workflow activity template pop-up window in Odoo Marketing Automation." +#: ../../content/applications/marketing/marketing_automation/workflow_activities.rst:24 +msgid "A new activity can be added to the workflow on a campaign form by selecting an existing campaign or :ref:`creating a new campaign ` from the :menuselection:`Marketing Automation app --> Campaigns` dashboard, then clicking the :guilabel:`Add new activity` button in the :guilabel:`Workflow` section. Doing so opens the :guilabel:`Create Activities` pop-up window." msgstr "" -#: ../../content/applications/marketing/marketing_automation/workflow_activities.rst:23 -msgid "First, enter a name for the activity in the :guilabel:`Activity Name` field. Then, proceed to configure the following options." -msgstr "" - -#: ../../content/applications/marketing/marketing_automation/workflow_activities.rst:26 -msgid "Once ready, either click: :guilabel:`Save & Close` to save the activity and close the pop-up form, :guilabel:`Save & New` to save the activity and instantly create an additional activity on a fresh :guilabel:`Create Activities` pop-up form, or :guilabel:`Discard` to delete the activity." -msgstr "" - -#: ../../content/applications/marketing/marketing_automation/workflow_activities.rst:31 -msgid "Activity types" +#: ../../content/applications/marketing/marketing_automation/workflow_activities.rst:29 +msgid "First, define the name of the activity in the :guilabel:`Activity Name` field, and select the :ref:`type of activity ` to be executed from the :guilabel:`Activity Type` field." msgstr "" #: ../../content/applications/marketing/marketing_automation/workflow_activities.rst:33 -msgid "Then, select the :guilabel:`Activity Type`. Choose between :guilabel:`Email`, :guilabel:`Server Action` (an internal action within the database), or :guilabel:`SMS`." +msgid "Then, configure the activity's :ref:`Trigger `, and optionally, the :ref:`Expiry Duration ` and the :ref:`DOMAIN ` of the activity." msgstr "" -#: ../../content/applications/marketing/marketing_automation/workflow_activities.rst:36 -msgid "The field below the :guilabel:`Activity Type` changes, depending on the chosen :guilabel:`Activity Type`." +#: ../../content/applications/marketing/marketing_automation/workflow_activities.rst:37 +msgid "Once the activity is fully configured, click :guilabel:`Save & Close` to add it to the campaign's workflow, or click :guilabel:`Save & New` to add the activity to the workflow and open a new :guilabel:`Create Activities` pop-up window to add another activity. Clicking :guilabel:`Discard` closes the pop-up window without saving the activity." msgstr "" -#: ../../content/applications/marketing/marketing_automation/workflow_activities.rst:40 -msgid "Email activity" +#: ../../content/applications/marketing/marketing_automation/workflow_activities.rst:-1 +msgid "The create activities pop-up window." msgstr "" -#: ../../content/applications/marketing/marketing_automation/workflow_activities.rst:42 -msgid "If :guilabel:`Email` is the :guilabel:`Activity Type`, the option to choose a premade/pre-configured :guilabel:`Mail Template` becomes available. A mail template can also be created on-the-fly, as well." +#: ../../content/applications/marketing/marketing_automation/workflow_activities.rst:49 +msgid "Activity types" msgstr "" -#: ../../content/applications/marketing/marketing_automation/workflow_activities.rst:46 -msgid "To create a new template directly from the :guilabel:`Mail Template` field, start typing the title of the new template into the blank field beside :guilabel:`Mail Template`, and select :guilabel:`Create and edit...` to reveal a :guilabel:`Create Marketing Template` pop-up window." +#: ../../content/applications/marketing/marketing_automation/workflow_activities.rst:51 +msgid "There are three different types of activities available in the *Marketing Automation* app:" +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/workflow_activities.rst:63 +#: ../../content/applications/marketing/marketing_automation/workflow_activities.rst:288 +msgid "Email" +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/workflow_activities.rst:65 +msgid "If :guilabel:`Email` is selected as the :guilabel:`Activity Type`, the option to :guilabel:`Pick a Template` in the :guilabel:`Mail Template` field is available." +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/workflow_activities.rst:68 +msgid "To create a new template directly from the :guilabel:`Mail Template` field, start typing the title of the new template, then select :guilabel:`Create and edit...` to reveal a :guilabel:`Create Marketing Template` pop-up window. Proceed to create and configure the new email template." msgstr "" #: ../../content/applications/marketing/marketing_automation/workflow_activities.rst:-1 @@ -2358,276 +3246,340 @@ msgstr "" msgid "The create and edit email drop-down option on create activities pop-up window." msgstr "" -#: ../../content/applications/marketing/marketing_automation/workflow_activities.rst:54 -msgid "In that pop-up window, proceed to create and configure the new email template." +#: ../../content/applications/marketing/marketing_automation/workflow_activities.rst:76 +msgid "Once the email template is configured, click :guilabel:`Save & Close` to save the activity, and return to the :guilabel:`Create Activities` pop-up window, in order to continue to configure the :ref:`trigger `." msgstr "" -#: ../../content/applications/marketing/marketing_automation/workflow_activities.rst:-1 -msgid "The create marketing template email pop-up window in Odoo Marketing Automation." -msgstr "" - -#: ../../content/applications/marketing/marketing_automation/workflow_activities.rst:61 -msgid "Server action activity" -msgstr "" - -#: ../../content/applications/marketing/marketing_automation/workflow_activities.rst:63 -msgid "If :guilabel:`Server Action` is the :guilabel:`Activity Type`, the option to choose a specific :guilabel:`Server Action` (e.g. Message for sales person, Create Leads on Website clicks, etc.) becomes available." -msgstr "" - -#: ../../content/applications/marketing/marketing_automation/workflow_activities.rst:67 -msgid "The option to create a new server action directly from the :guilabel:`Server Action` is also available. To do that, type in the name of the new action, then click :guilabel:`Create and Edit...` from the drop-down menu." -msgstr "" - -#: ../../content/applications/marketing/marketing_automation/workflow_activities.rst:-1 -msgid "The create and edit option in the server action field on campaign detail form." -msgstr "" - -#: ../../content/applications/marketing/marketing_automation/workflow_activities.rst:75 -msgid "Or, as an alternative, click the empty :guilabel:`Server Action` field to reveal a drop-down menu, and select :guilabel:`Search More...` to reveal a :guilabel:`Search: Server Action` pop-up window, containing all the pre-configured server action options to choose from." -msgstr "" - -#: ../../content/applications/marketing/marketing_automation/workflow_activities.rst:79 -msgid "To create a new server action from this pop-up window, and click :guilabel:`New`." -msgstr "" - -#: ../../content/applications/marketing/marketing_automation/workflow_activities.rst:-1 -msgid "The new button found on a server action pop-up in Odoo marketing automation application." +#: ../../content/applications/marketing/marketing_automation/workflow_activities.rst:81 +msgid "The title used for the :guilabel:`Mail Template` **must** be unique from any other mail template titles in the campaign, and it also serves as the subject of the email." msgstr "" #: ../../content/applications/marketing/marketing_automation/workflow_activities.rst:85 -msgid "Either option reveals a blank :guilabel:`Create Server Action` pop-up, wherein a custom server action can be created and configured." +msgid ":doc:`Creating and configuring email templates <../email_marketing>`" msgstr "" -#: ../../content/applications/marketing/marketing_automation/workflow_activities.rst:89 -msgid "SMS activity" +#: ../../content/applications/marketing/marketing_automation/workflow_activities.rst:90 +msgid "Server action" msgstr "" -#: ../../content/applications/marketing/marketing_automation/workflow_activities.rst:91 -msgid "If :guilabel:`SMS` is the :guilabel:`Activity Type`, the option to choose a premade/pre-configured :guilabel:`SMS Template` becomes available. A SMS template can also be created on-the-fly directly from this field." -msgstr "" - -#: ../../content/applications/marketing/marketing_automation/workflow_activities.rst:95 -msgid "To create a new template directly from the :guilabel:`SMS Template` field, start typing the title of the new template into the blank field beside :guilabel:`SMS Template`, and select :guilabel:`Create and edit...` from the drop-down menu." -msgstr "" - -#: ../../content/applications/marketing/marketing_automation/workflow_activities.rst:103 -msgid "Doing so reveals a :guilabel:`Create Marketing Template` pop-up window. In that pop-up window, proceed to create and configure the new SMS template." +#: ../../content/applications/marketing/marketing_automation/workflow_activities.rst:92 +msgid "If :guilabel:`Server Action` is selected as the :guilabel:`Activity Type`, the option to :guilabel:`Pick a Server Action` in the :guilabel:`Server Action` field is available. This field is a drop-down menu containing all the pre-configured server actions for the campaign's :guilabel:`Target` model. Optionally, :ref:`create a new server action `." msgstr "" #: ../../content/applications/marketing/marketing_automation/workflow_activities.rst:-1 -msgid "The create marketing template pop-up window to create a SMS template on-the-fly." +msgid "The Server Action drop-down menu on create activities pop-up window." msgstr "" -#: ../../content/applications/marketing/marketing_automation/workflow_activities.rst:111 -msgid "Trigger" +#: ../../content/applications/marketing/marketing_automation/workflow_activities.rst:102 +msgid "After selecting a pre-configured server action, no other activity type configuration is needed. Click :guilabel:`Save & Close` to save the activity, and return to the :guilabel:`Create Activities` pop-up window, in order to configure the :ref:`trigger `." +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/workflow_activities.rst:107 +msgid "To view all server actions in the database, activate :ref:`developer-mode`, and navigate to :menuselection:`Settings app --> Technical --> Actions --> Server Actions` dashboard." msgstr "" #: ../../content/applications/marketing/marketing_automation/workflow_activities.rst:113 -msgid "The :guilabel:`Trigger` field on the :guilabel:`Create Activities` pop-up form allows users to choose when the designated workflow activity should be triggered." +msgid "Create a new server action" msgstr "" -#: ../../content/applications/marketing/marketing_automation/workflow_activities.rst:116 -msgid "Start by selecting a number in the top field. In the next :guilabel:`Trigger` field, designate if it should be :guilabel:`Hours`, :guilabel:`Days`, :guilabel:`Weeks`, or :guilabel:`Months`. Then, click the final field, where it reads :guilabel:`beginning of the workflow` be default to reveal a a drop-down menu of other trigger options." +#: ../../content/applications/marketing/marketing_automation/workflow_activities.rst:115 +msgid "The option to create a new server action is also available. To do so, type in the :guilabel:`Server Action` field a title for the new action, then click :guilabel:`Create and edit...`. Doing so reveals a blank :guilabel:`Create Server Action` pop-up window, wherein a custom server action can be created and configured." msgstr "" #: ../../content/applications/marketing/marketing_automation/workflow_activities.rst:-1 -msgid "A list of the trigger options available on the workflow activities pop-up form." +msgid "The Create Server Action pop-up window." msgstr "" -#: ../../content/applications/marketing/marketing_automation/workflow_activities.rst:125 -msgid "The trigger options are as follows:" +#: ../../content/applications/marketing/marketing_automation/workflow_activities.rst:124 +msgid "On the :guilabel:`Create Server Action` pop-up window, select the :guilabel:`Type` of server action. The configuration fields change, depending on the selected :guilabel:`Type`:" msgstr "" #: ../../content/applications/marketing/marketing_automation/workflow_activities.rst:127 -msgid ":guilabel:`beginning of the workflow`: the activity will be triggered at the previously-configured time after the beginning of the entire workflow." +msgid ":guilabel:`Update Record`: update the values of a record." +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/workflow_activities.rst:128 +msgid ":guilabel:`Create Activity`: create an activity with the *Discuss* app." msgstr "" #: ../../content/applications/marketing/marketing_automation/workflow_activities.rst:129 -msgid ":guilabel:`another activity`: the activity will be triggered at the previously-configured time after another specific activity in the workflow." +msgid ":guilabel:`Send Email`: post a message, a note, or send an email with the *Discuss* app." +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/workflow_activities.rst:130 +msgid ":guilabel:`Send SMS`: send an SMS, and log them on documents, with the *SMS* app." msgstr "" #: ../../content/applications/marketing/marketing_automation/workflow_activities.rst:131 -msgid ":guilabel:`Mail:opened`: the activity will be triggered at the previously-configured time if the sent mail in the workflow has been opened by the recipient." +msgid ":guilabel:`Add Followers` or :guilabel:`Remove Followers`: add or remove followers on a record with the *Discuss* app." msgstr "" #: ../../content/applications/marketing/marketing_automation/workflow_activities.rst:133 -msgid ":guilabel:`Mail:not opened`: the activity will be triggered at the previously-configured time if the sent mail in the workflow has not been opened by the recipient." +msgid ":guilabel:`Create Record`: create a new record with new values." +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/workflow_activities.rst:134 +msgid ":guilabel:`Execute Code`: execute a block of Python code." msgstr "" #: ../../content/applications/marketing/marketing_automation/workflow_activities.rst:135 -msgid ":guilabel:`Mail: replied`: the activity will be triggered at the previously-configured time if the sent mail in the workflow has been replied to by the recipient." +msgid ":guilabel:`Send Webhook Notification`: send a POST request to an external system." msgstr "" -#: ../../content/applications/marketing/marketing_automation/workflow_activities.rst:137 -msgid ":guilabel:`Mail: not replied`: the activity will be triggered at the previously-configured time if the sent mail in the workflow has not been replied to by the recipient." +#: ../../content/applications/marketing/marketing_automation/workflow_activities.rst:136 +msgid ":guilabel:`Execute Existing Actions`: define an action that triggers several other server actions." msgstr "" #: ../../content/applications/marketing/marketing_automation/workflow_activities.rst:139 -msgid ":guilabel:`Mail: clicked`: the activity will be triggered at the previously-configured time if the sent mail in the workflow has been clicked by the recipient, after it's been opened." +msgid "Once the server action is configured, click :guilabel:`Save & Close` to save the activity, and return to the :guilabel:`Create Activities` pop-up window, in order to configure the :ref:`trigger `." msgstr "" -#: ../../content/applications/marketing/marketing_automation/workflow_activities.rst:141 -msgid ":guilabel:`Mail: not clicked`: the activity will be triggered at the previously-configured time if the sent mail in the workflow has not been clicked by the recipient, after it's been opened." +#: ../../content/applications/marketing/marketing_automation/workflow_activities.rst:144 +msgid "Some of the server action types have advanced configurations available when :ref:`developer-mode` is activated, such as specifying the :guilabel:`Allowed Groups` that can execute this server action." msgstr "" -#: ../../content/applications/marketing/marketing_automation/workflow_activities.rst:143 -msgid ":guilabel:`Mail: bounced`: the activity will be triggered at the previously-configured time if the sent mail in the workflow has been bounced back for any reason." -msgstr "" - -#: ../../content/applications/marketing/marketing_automation/workflow_activities.rst:145 -msgid ":guilabel:`SMS: clicked`: the activity will be triggered at the previously-configured time if the sent SMS in the workflow has been clicked by the recipient, after it's been opened." -msgstr "" - -#: ../../content/applications/marketing/marketing_automation/workflow_activities.rst:147 -msgid ":guilabel:`SMS: not clicked`: the activity will be triggered at the previously-configured time if the sent SMS in the workflow has not been clicked by the recipient, after it's been opened." -msgstr "" - -#: ../../content/applications/marketing/marketing_automation/workflow_activities.rst:149 -msgid ":guilabel:`SMS: bounced`: the activity will be triggered at the previously-configured time if the sent SMS in the workflow has been bounced back for any reason." +#: ../../content/applications/marketing/marketing_automation/workflow_activities.rst:151 +#: ../../content/applications/marketing/marketing_automation/workflow_activities.rst:315 +msgid "SMS" msgstr "" #: ../../content/applications/marketing/marketing_automation/workflow_activities.rst:153 -msgid "Expiry duration" +msgid "If :guilabel:`SMS` is selected as the :guilabel:`Activity Type`, the option to :guilabel:`Pick a Template` in the :guilabel:`SMS Template` field is available." msgstr "" -#: ../../content/applications/marketing/marketing_automation/workflow_activities.rst:155 -msgid "Next, on the :guilabel:`Create Activities` pop-up form is the :guilabel:`Expiry Duration` option." +#: ../../content/applications/marketing/marketing_automation/workflow_activities.rst:156 +msgid "To create a new template directly from the :guilabel:`SMS Template` field, start typing the title of the new template, and select :guilabel:`Create and edit...` to reveal a :guilabel:`Create Marketing Template` pop-up window. Proceed to create and configure the new SMS template." msgstr "" -#: ../../content/applications/marketing/marketing_automation/workflow_activities.rst:157 -msgid "The :guilabel:`Expiry Duration` checkbox provides the option to configure the activity to stop the actions after a specific amount of time (after the scheduled date)." +#: ../../content/applications/marketing/marketing_automation/workflow_activities.rst:164 +msgid "Once the SMS template is configured, click :guilabel:`Save & Close` to save the activity, and return to the :guilabel:`Create Activities` pop-up window, in order to configure the :ref:`trigger `." msgstr "" -#: ../../content/applications/marketing/marketing_automation/workflow_activities.rst:160 -msgid "When selected, a :guilabel:`Cancel after` field appears, in which the number of :guilabel:`Hours, Days, Weeks, or Months` can be configured for the actions to cease after the initial date." +#: ../../content/applications/marketing/marketing_automation/workflow_activities.rst:169 +msgid ":doc:`Creating and configuring SMS templates <../sms_marketing/essentials/sms_essentials>`" +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/workflow_activities.rst:174 +msgid "Trigger" +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/workflow_activities.rst:176 +msgid "Once an :ref:`activity type ` is configured, the next step in the :guilabel:`Create Activities` pop-up window is to define when the activity should be executed. This is done in the :guilabel:`Trigger` field group." msgstr "" #: ../../content/applications/marketing/marketing_automation/workflow_activities.rst:-1 -msgid "A list of the expiry duration options available on the workflow activities pop-up form." -msgstr "" - -#: ../../content/applications/marketing/marketing_automation/workflow_activities.rst:168 -msgid "Activity and applied filters" -msgstr "" - -#: ../../content/applications/marketing/marketing_automation/workflow_activities.rst:170 -msgid "Moving down into the :guilabel:`Domain` section of the :guilabel:`Create Activities` pop-up form, there is the :guilabel:`Activity Filter` and :guilabel:`Applied Filter` fields." -msgstr "" - -#: ../../content/applications/marketing/marketing_automation/workflow_activities.rst:173 -msgid "The :guilabel:`Activity Filter` field provides the option to configure a recipient filter domain that applies to this activity *and* its child activities. In works in the same fashion as a typical target audience filter." -msgstr "" - -#: ../../content/applications/marketing/marketing_automation/workflow_activities.rst:177 -msgid "To add an activity filter, click :guilabel:`Add condition` in the :guilabel:`Activity Filter` field and proceed to configure a custom activity filter equation rule(s)." -msgstr "" - -#: ../../content/applications/marketing/marketing_automation/workflow_activities.rst:-1 -msgid "How to add an activity filter to a workflow activity in Odoo Marketing Automation." +msgid "The trigger field group on Create Activities pop-up window." msgstr "" #: ../../content/applications/marketing/marketing_automation/workflow_activities.rst:184 -msgid "This option is not a required field. If left alone, the activity applies to all records related to the target audience of the overall campaign." +msgid "To set an execution delay for the activity from when the :ref:`trigger type ` occurs, type a whole number in the *interval number* input (e.g. `2` is valid, `0` is also valid, and `1.5` is not)." msgstr "" -#: ../../content/applications/marketing/marketing_automation/workflow_activities.rst:190 -msgid "The :guilabel:`Applied Filter` field is non-configurable. It's simply a summary of when the activity will be performed, *only* if it satisfies the specified domain (e.g. the rules configured in the :guilabel:`Activity Filter` field)." +#: ../../content/applications/marketing/marketing_automation/workflow_activities.rst:188 +msgid "Next, select the unit of time for the interval number in the *interval type* drop-down menu, the options are: :guilabel:`Hours`, :guilabel:`Days`, :guilabel:`Weeks`, and :guilabel:`Months`." msgstr "" -#: ../../content/applications/marketing/marketing_automation/workflow_activities.rst:195 -msgid "After the activity's settings are fully configured, click :guilabel:`Save & Close` to save the activity and return to the marketing automation campaign form, :guilabel:`Save & New` to save the activity and immediately create another one in a fresh :guilabel:`Create Activities` pop-up window, or :guilabel:`Discard` to delete the activity and return to the marketing automation campaign form." +#: ../../content/applications/marketing/marketing_automation/workflow_activities.rst:192 +msgid "If the interval number is set to `0` and the interval type is set to :guilabel:`Hours`, the activity will be executed immediately after the trigger type occurs (at the next scheduled run of the :ref:`Mail: Email Queue Manager cron `)." msgstr "" -#: ../../content/applications/marketing/marketing_automation/workflow_activities.rst:202 -msgid "Workflow activity" +#: ../../content/applications/marketing/marketing_automation/workflow_activities.rst:199 +msgid "Trigger type" +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/workflow_activities.rst:201 +msgid "To define the event occurrence that sets the activity into motion, select a *trigger type* from the drop-down menu:" msgstr "" #: ../../content/applications/marketing/marketing_automation/workflow_activities.rst:204 -msgid "Once an activity is created and saved, it appears as an activity card in the :guilabel:`Workflow` section, located at the bottom of the marketing automation campaign form. The analytics related to each activity is displayed as a line graph." +msgid ":guilabel:`beginning of workflow`: the activity is executed when the campaign is started." msgstr "" -#: ../../content/applications/marketing/marketing_automation/workflow_activities.rst:-1 -msgid "Typical workflow activity in Odoo Marketing Automation." +#: ../../content/applications/marketing/marketing_automation/workflow_activities.rst:206 +msgid "All other trigger types reveal a drop-down menu :guilabel:`Activity` field containing all of the other activities in the campaign. Selecting one of these types converts this activity into a :ref:`child activity ` to be executed directly after the selected :guilabel:`Activity`:" +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/workflow_activities.rst:211 +msgid ":guilabel:`another activity`: to be executed after another activity in the campaign." msgstr "" #: ../../content/applications/marketing/marketing_automation/workflow_activities.rst:212 -msgid "The configured :guilabel:`Trigger` time for that activity can be found to the left of the :guilabel:`Workflow Activity` card in the :guilabel:`Workflow` section." +msgid ":guilabel:`Mail: opened`: the activity's email was opened by the participant." +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/workflow_activities.rst:213 +msgid ":guilabel:`Mail: not opened`: the activity's email was **not** opened by the participant." +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/workflow_activities.rst:214 +msgid ":guilabel:`Mail: replied`: the activity's email was replied to by the participant." msgstr "" #: ../../content/applications/marketing/marketing_automation/workflow_activities.rst:215 -msgid "Once the activity has been triggered, a figure representing the number of :guilabel:`Success` or :guilabel:`Rejected` activities will be displayed to the right of the graph." +msgid ":guilabel:`Mail: not replied`: the activity's email was **not** replied to by the participant." +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/workflow_activities.rst:216 +msgid ":guilabel:`Mail: clicked`: a link in the activity's email was clicked by the participant." +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/workflow_activities.rst:217 +msgid ":guilabel:`Mail: not clicked`: a link in the activity's email was **not** clicked by the participant." msgstr "" #: ../../content/applications/marketing/marketing_automation/workflow_activities.rst:219 -msgid "If the :guilabel:`Activity Type` of the activity is set to :guilabel:`Email` or :guilabel:`SMS`, there are more in-depth analytics beneath the activity graph data, detailing how many messages have been :guilabel:`Sent`, and what percentage of those have been :guilabel:`Clicked`, :guilabel:`Replied` to, or :guilabel:`Bounced`." +msgid ":guilabel:`Mail: bounced`: the activity's email has bounced." +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/workflow_activities.rst:220 +msgid ":guilabel:`SMS: clicked`: a link in the activity's SMS was clicked by the participant." +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/workflow_activities.rst:221 +msgid ":guilabel:`SMS: not clicked`: a link in the activity's SMS was **not** clicked by the participant." +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/workflow_activities.rst:222 +msgid ":guilabel:`SMS: bounced`: the activity's SMS has bounced." msgstr "" #: ../../content/applications/marketing/marketing_automation/workflow_activities.rst:225 -msgid "Child activities" +msgid "If the trigger type is set to :guilabel:`Mail: clicked`, this activity is converted to a :ref:`child activity ` and will execute **after** a participant clicks on a link from the parent activity defined in the :guilabel:`Activity` field." msgstr "" -#: ../../content/applications/marketing/marketing_automation/workflow_activities.rst:227 -msgid "There is also the option to add a *child activity* by clicking :guilabel:`Add child activity`, located at the bottom of each activity block in the :guilabel:`Workflow` section of a marketing campaign form." +#: ../../content/applications/marketing/marketing_automation/workflow_activities.rst:232 +msgid "Expiry duration" msgstr "" -#: ../../content/applications/marketing/marketing_automation/workflow_activities.rst:231 -msgid "Child activities are sub-activities that are connected to and triggered by the activity above it, which is known as its *parent activity*. A child activity is easy to recognize, as its slightly indented beneath its parent activity." +#: ../../content/applications/marketing/marketing_automation/workflow_activities.rst:234 +msgid "Optionally, an :guilabel:`Expiry Duration` can be defined in the :guilabel:`Create Activities` pop-up window to cancel the execution of this activity after a specific amount of time. Selecting this checkbox reveals the :guilabel:`Cancel after` field with *interval* and *interval type* inputs." msgstr "" -#: ../../content/applications/marketing/marketing_automation/workflow_activities.rst:-1 -msgid "A typical child activity indented beneath its parent activity." +#: ../../content/applications/marketing/marketing_automation/workflow_activities.rst:238 +msgid "Type a whole number in the interval number input (e.g. `2` is valid, `0` is also valid, and `1.5` is not). Then, select the unit of time for the interval number in the interval type drop-down menu, the options are: :guilabel:`Hours`, :guilabel:`Days`, :guilabel:`Weeks`, and :guilabel:`Months`." msgstr "" -#: ../../content/applications/marketing/marketing_automation/workflow_activities.rst:239 -msgid "Odoo provides a number of triggering options to launch a child activity - all of which depend on the trigger configurations related to its parent activity. Under the desired parent activity, hover over :guilabel:`Add child activity`, to reveal a menu of child activity trigger options." -msgstr "" - -#: ../../content/applications/marketing/marketing_automation/workflow_activities.rst:-1 -msgid "The various child activity trigger options in the workflow section of a campaign." -msgstr "" - -#: ../../content/applications/marketing/marketing_automation/workflow_activities.rst:247 -msgid "Select any of the following child activity triggers:" +#: ../../content/applications/marketing/marketing_automation/workflow_activities.rst:243 +msgid "If the interval number is set to `2` and the interval type is set to :guilabel:`Days`, the activity will be cancelled if it has not been executed within 2 days of the trigger type." msgstr "" #: ../../content/applications/marketing/marketing_automation/workflow_activities.rst:249 -msgid ":guilabel:`Add Another Activity`: instantly adds another activity." -msgstr "" - -#: ../../content/applications/marketing/marketing_automation/workflow_activities.rst:250 -msgid ":guilabel:`Opened`: the next activity will be triggered if the recipient opens the mailing." +msgid "Activity domain" msgstr "" #: ../../content/applications/marketing/marketing_automation/workflow_activities.rst:251 -msgid ":guilabel:`Not Opened`: the next activity will be triggered if the recipient does not open the mailing." -msgstr "" - -#: ../../content/applications/marketing/marketing_automation/workflow_activities.rst:253 -msgid ":guilabel:`Replied`: the next activity will be triggered if the recipient replies to the mailing." +msgid "The :guilabel:`DOMAIN` section of the :guilabel:`Create Activities` pop-up window contains fields to further filter the target audience of the activity." msgstr "" #: ../../content/applications/marketing/marketing_automation/workflow_activities.rst:254 -msgid ":guilabel:`Not Replied`: the next activity will be triggered if the recipient does not reply to the mailing." -msgstr "" - -#: ../../content/applications/marketing/marketing_automation/workflow_activities.rst:256 -msgid ":guilabel:`Clicked`: the next activity will be triggered if the recipient clicks on a link included in the mailing." -msgstr "" - -#: ../../content/applications/marketing/marketing_automation/workflow_activities.rst:258 -msgid ":guilabel:`Not Clicked`: the next activity will be triggered if the recipient does not click on a link included in the mailing." +msgid "The :guilabel:`Activity Filter` field focuses this activity, **and** its :ref:`child activities `, even further on a specific group of the campaign's filter. The process is the same as :ref:`defining filters ` for the campaign, and the fields that are available to filter are also specific to the :guilabel:`Target` of the campaign." msgstr "" #: ../../content/applications/marketing/marketing_automation/workflow_activities.rst:260 -msgid ":guilabel:`Bounced`: the next activity will be triggered if the mailing is bounced (not sent)." +msgid "The :guilabel:`# record(s)` beside the :guilabel:`Activity Filter` field indicates how many records are currently being targeted by this :guilabel:`Activity Filter`." msgstr "" -#: ../../content/applications/marketing/marketing_automation/workflow_activities.rst:262 -msgid "Once a trigger is selected, the user can configure the child activity the same way they would for a regular workflow activity." +#: ../../content/applications/marketing/marketing_automation/workflow_activities.rst:263 +msgid "The :guilabel:`Applied Filter` displays the combined filters from the :guilabel:`Activity Filter` and the inherited campaign :doc:`Filter `. This field is read-only." msgstr "" #: ../../content/applications/marketing/marketing_automation/workflow_activities.rst:266 -msgid ":doc:`testing_running`" +msgid "The :guilabel:`# record(s)` beside the :guilabel:`Applied Filter` field indicates how many records, in total, are currently being targeted by the activity." +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/workflow_activities.rst:272 +msgid "Child activities" +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/workflow_activities.rst:274 +msgid "Activities that are connected to, and triggered by, another activity are known as, *child activities*." +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/workflow_activities.rst:277 +msgid "The activity that triggers a child activity is known as its *parent activity*." +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/workflow_activities.rst:279 +msgid "A child activity can be added to a campaign's workflow by hovering over the :guilabel:`➕ Add child activity` button, located beneath the desired parent activity." +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/workflow_activities.rst:282 +msgid "The child activity's :ref:`trigger types ` are specific to the parent :ref:`activity type ` (*Email*, *SMS*, or *Server Action*), and are as follows:" +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/workflow_activities.rst:0 +msgid "The trigger types for child activities of an email activity." +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/workflow_activities.rst:294 +#: ../../content/applications/marketing/marketing_automation/workflow_activities.rst:321 +msgid "Each trigger the child activity on the following conditions of the parent activity:" +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/workflow_activities.rst:296 +#: ../../content/applications/marketing/marketing_automation/workflow_activities.rst:313 +#: ../../content/applications/marketing/marketing_automation/workflow_activities.rst:323 +msgid ":guilabel:`Add Another Activity`: to be executed after the parent activity." +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/workflow_activities.rst:297 +msgid ":guilabel:`Opened`: the email was opened by the participant." +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/workflow_activities.rst:298 +msgid ":guilabel:`Not Opened`: the email was **not** opened by the participant." +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/workflow_activities.rst:299 +msgid ":guilabel:`Replied`: the email was replied to by the participant." +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/workflow_activities.rst:300 +msgid ":guilabel:`Not Replied`: the email was **not** replied to by the participant." +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/workflow_activities.rst:301 +msgid ":guilabel:`Clicked`: a link in the email was clicked by the participant." +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/workflow_activities.rst:302 +msgid ":guilabel:`Not Clicked`: a link in the email was **not** clicked by the participant." +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/workflow_activities.rst:303 +msgid ":guilabel:`Bounced`: the email has bounced." +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/workflow_activities.rst:305 +msgid "Server Action" +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/workflow_activities.rst:0 +msgid "The trigger types for child activities of a server action activity." +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/workflow_activities.rst:311 +msgid "Triggers the child activity on the following condition of the parent activity:" +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/workflow_activities.rst:0 +msgid "The trigger types for child activities of an SMS activity." +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/workflow_activities.rst:324 +msgid ":guilabel:`Clicked`: a link in the SMS was clicked by the participant." +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/workflow_activities.rst:325 +msgid ":guilabel:`Not Clicked`: a link in the SMS was **not** clicked by the participant." +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/workflow_activities.rst:326 +msgid ":guilabel:`Bounced`: the SMS has bounced." +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/workflow_activities.rst:328 +msgid "Once a trigger type is selected, the :guilabel:`Create Activities` pop-up window opens to configure the child activity. The process is the same as :ref:`creating a new activity `, with the exception that the :guilabel:`Trigger` field is pre-filled with the selected trigger type, and the :guilabel:`Activity` field has the parent activity selected." msgstr "" #: ../../content/applications/marketing/sms_marketing.rst:8 @@ -3027,34 +3979,34 @@ msgid "To create (or edit) a mailing list, go to :menuselection:`Mailing Lists - msgstr "" #: ../../content/applications/marketing/sms_marketing/essentials/sms_essentials.rst:64 -msgid "To learn more about mailing lists and contacts, check out :doc:`mailing_lists_blacklists`" +msgid "To learn more about mailing lists and contacts, check out :doc:`mailing_lists_blacklists`." msgstr "" #: ../../content/applications/marketing/sms_marketing/essentials/sms_essentials.rst:-1 msgid "View of the mailing list page in the SMS marketing application." msgstr "" -#: ../../content/applications/marketing/sms_marketing/essentials/sms_essentials.rst:71 +#: ../../content/applications/marketing/sms_marketing/essentials/sms_essentials.rst:70 msgid "To reveal all the possible options in the :guilabel:`Recipients` field, click the field to see all the choices Odoo makes available." msgstr "" -#: ../../content/applications/marketing/sms_marketing/essentials/sms_essentials.rst:74 +#: ../../content/applications/marketing/sms_marketing/essentials/sms_essentials.rst:73 msgid "When another field (other than :guilabel:`Mailing List`) is selected, the option to specify that chosen field even further becomes available — either with a default recipient filter equation that appears automatically (which can be customized to fit any business need), or, if no default recipient filter equation is present, an :guilabel:`Add Filter` button will appear." msgstr "" -#: ../../content/applications/marketing/sms_marketing/essentials/sms_essentials.rst:79 +#: ../../content/applications/marketing/sms_marketing/essentials/sms_essentials.rst:78 msgid "Clicking the :guilabel:`Add Filter` button, reveals fully customizable domain rule fields, which can be configured similar to an equation. You can create multiple recipient rules, if necessary." msgstr "" -#: ../../content/applications/marketing/sms_marketing/essentials/sms_essentials.rst:82 +#: ../../content/applications/marketing/sms_marketing/essentials/sms_essentials.rst:81 msgid "Then, Odoo will only send the :abbr:`SMS (Short Message Service)` to recipients who fit into whatever criteria is configured in those fields. Multiple rules can be added." msgstr "" -#: ../../content/applications/marketing/sms_marketing/essentials/sms_essentials.rst:86 +#: ../../content/applications/marketing/sms_marketing/essentials/sms_essentials.rst:85 msgid "If :guilabel:`Contact` is chosen, all of the *Contacts* records in the Odoo database (vendors, customers, etc.) will receive the :abbr:`SMS (Short Message Service)`, by default — unless more specific recipient rules are entered." msgstr "" -#: ../../content/applications/marketing/sms_marketing/essentials/sms_essentials.rst:90 +#: ../../content/applications/marketing/sms_marketing/essentials/sms_essentials.rst:89 msgid "For instance, the message below will only be sent to contacts in the database that are located in the United States (e.g. `Country` > `Country Name` equals `United States`), and they haven't blacklisted themselves from any mailings (e.g. `Blacklist` > `is` > `not set`)." msgstr "" @@ -3062,15 +4014,15 @@ msgstr "" msgid "Contact recipients on SMS marketing." msgstr "" -#: ../../content/applications/marketing/sms_marketing/essentials/sms_essentials.rst:99 +#: ../../content/applications/marketing/sms_marketing/essentials/sms_essentials.rst:98 msgid "Writing SMS messages" msgstr "" -#: ../../content/applications/marketing/sms_marketing/essentials/sms_essentials.rst:101 +#: ../../content/applications/marketing/sms_marketing/essentials/sms_essentials.rst:100 msgid "Enter the content of the :abbr:`SMS (Short Message Service)` in the text field, found in the :guilabel:`SMS Content` tab. Links and emojis can also be included. Beneath the text field, Odoo displays how many characters are used in the message, along with how many :abbr:`SMS (Short Message Service)` mailings it will take to deliver the complete message." msgstr "" -#: ../../content/applications/marketing/sms_marketing/essentials/sms_essentials.rst:107 +#: ../../content/applications/marketing/sms_marketing/essentials/sms_essentials.rst:106 msgid "To check the price of sending an :abbr:`SMS (Short Message Service)` for a country, click on the :guilabel:`Information` icon." msgstr "" @@ -3078,19 +4030,19 @@ msgstr "" msgid "SMS price check icon." msgstr "" -#: ../../content/applications/marketing/sms_marketing/essentials/sms_essentials.rst:115 +#: ../../content/applications/marketing/sms_marketing/essentials/sms_essentials.rst:114 msgid "Credits must be purchased from Odoo in order to take advantage of the *SMS Marketing* app; :abbr:`SMS (Short Message Service)` messages will not be sent without credits." msgstr "" -#: ../../content/applications/marketing/sms_marketing/essentials/sms_essentials.rst:119 +#: ../../content/applications/marketing/sms_marketing/essentials/sms_essentials.rst:118 msgid "`Odoo SMS - FAQ `_" msgstr "" -#: ../../content/applications/marketing/sms_marketing/essentials/sms_essentials.rst:122 +#: ../../content/applications/marketing/sms_marketing/essentials/sms_essentials.rst:121 msgid "Track links used in SMS messages" msgstr "" -#: ../../content/applications/marketing/sms_marketing/essentials/sms_essentials.rst:124 +#: ../../content/applications/marketing/sms_marketing/essentials/sms_essentials.rst:123 msgid "When links are used in :abbr:`SMS (Short Message Service)` messages, Odoo automatically generates link trackers to gather analytical data and metrics related to those specific links, which can be found by going to :menuselection:`Configuration --> Link Tracker`." msgstr "" @@ -3098,15 +4050,15 @@ msgstr "" msgid "SMS Link Tracker page." msgstr "" -#: ../../content/applications/marketing/sms_marketing/essentials/sms_essentials.rst:133 +#: ../../content/applications/marketing/sms_marketing/essentials/sms_essentials.rst:132 msgid "Adjust SMS settings" msgstr "" -#: ../../content/applications/marketing/sms_marketing/essentials/sms_essentials.rst:135 +#: ../../content/applications/marketing/sms_marketing/essentials/sms_essentials.rst:134 msgid "Under the :guilabel:`Settings` tab of the SMS template, there is an option to :guilabel:`Include opt-out link`. If activated, the recipient is able to unsubscribe from the mailing list, thus avoiding all future mailings." msgstr "" -#: ../../content/applications/marketing/sms_marketing/essentials/sms_essentials.rst:139 +#: ../../content/applications/marketing/sms_marketing/essentials/sms_essentials.rst:138 msgid "An employee can be designated as the :guilabel:`Responsible` in the :guilabel:`Tracking` section of the :guilabel:`Settings` tab, as well." msgstr "" @@ -3114,39 +4066,39 @@ msgstr "" msgid "SMS Settings tab." msgstr "" -#: ../../content/applications/marketing/sms_marketing/essentials/sms_essentials.rst:147 +#: ../../content/applications/marketing/sms_marketing/essentials/sms_essentials.rst:146 msgid "Send SMS messages" msgstr "" -#: ../../content/applications/marketing/sms_marketing/essentials/sms_essentials.rst:149 +#: ../../content/applications/marketing/sms_marketing/essentials/sms_essentials.rst:148 msgid "Once a mailing is created, choose when Odoo should deliver the message from the following options:" msgstr "" -#: ../../content/applications/marketing/sms_marketing/essentials/sms_essentials.rst:151 +#: ../../content/applications/marketing/sms_marketing/essentials/sms_essentials.rst:150 msgid ":guilabel:`Send`: sends the message immediately. Consider using this option if the recipient list is highly refined, or in cases that involve fast approaching deadlines, such as a \"flash sale.\"" msgstr "" -#: ../../content/applications/marketing/sms_marketing/essentials/sms_essentials.rst:153 +#: ../../content/applications/marketing/sms_marketing/essentials/sms_essentials.rst:152 msgid ":guilabel:`Schedule`: choose a day (and time) for Odoo to send the mailing. This is typically the best option for mailings related to a specific event. Such a method can also be used to promote a limited-time offer, or to help plan a company's content strategy in advance." msgstr "" -#: ../../content/applications/marketing/sms_marketing/essentials/sms_essentials.rst:156 +#: ../../content/applications/marketing/sms_marketing/essentials/sms_essentials.rst:155 msgid ":guilabel:`Test`: allows for an :abbr:`SMS (Short Message Service)` to be sent to one or multiple numbers for test purposes. Remember to use a comma between phone numbers if multiple numbers are used as recipients." msgstr "" -#: ../../content/applications/marketing/sms_marketing/essentials/sms_essentials.rst:161 +#: ../../content/applications/marketing/sms_marketing/essentials/sms_essentials.rst:160 msgid "Visualize reports" msgstr "" -#: ../../content/applications/marketing/sms_marketing/essentials/sms_essentials.rst:163 +#: ../../content/applications/marketing/sms_marketing/essentials/sms_essentials.rst:162 msgid "On the :guilabel:`Reporting` page (accessible via the :menuselection:`Reporting` option in the header menu), there are options to apply different combinations of :guilabel:`Filters` and :guilabel:`Measures` to view metrics in a number of different layouts (e.g. :guilabel:`Graph`, :guilabel:`List`, and :guilabel:`Cohort` views.)" msgstr "" -#: ../../content/applications/marketing/sms_marketing/essentials/sms_essentials.rst:168 +#: ../../content/applications/marketing/sms_marketing/essentials/sms_essentials.rst:167 msgid "Each :guilabel:`Reporting` metric view option allows for more extensive performance analysis of :abbr:`SMS (Short Message Service)` mailings." msgstr "" -#: ../../content/applications/marketing/sms_marketing/essentials/sms_essentials.rst:171 +#: ../../content/applications/marketing/sms_marketing/essentials/sms_essentials.rst:170 msgid "For example, while in the default :guilabel:`Graph` view, :abbr:`SMS (Short Message Service)` data is visualized as different graphs and charts, which can be sorted and grouped in various ways (e.g. :guilabel:`Measures` drop down menu)." msgstr "" @@ -3154,14 +4106,142 @@ msgstr "" msgid "Reporting page in SMS Marketing." msgstr "" -#: ../../content/applications/marketing/sms_marketing/essentials/sms_essentials.rst:180 +#: ../../content/applications/marketing/sms_marketing/essentials/sms_essentials.rst:179 +msgid "SMS messages can be sent using automation rules in Odoo. Odoo *Studio* is required to use automation rules." +msgstr "" + +#: ../../content/applications/marketing/sms_marketing/essentials/sms_essentials.rst:182 +msgid "To install Odoo *Studio*, go to the :menuselection:`Apps application`. Then, using the :guilabel:`Search...` bar, search for `studio`." +msgstr "" + +#: ../../content/applications/marketing/sms_marketing/essentials/sms_essentials.rst:185 +msgid "If it is not already installed, click :guilabel:`Install`." +msgstr "" + +#: ../../content/applications/marketing/sms_marketing/essentials/sms_essentials.rst:187 +msgid "Adding the *Studio* application upgrades the subscription status to *Custom*, which increases the cost. Consult `support `_, or reach out to the database's customer success manager, with any questions on making the change." +msgstr "" + +#: ../../content/applications/marketing/sms_marketing/essentials/sms_essentials.rst:191 +msgid "To use automation rules, navigate in :ref:`developer mode `, to :menuselection:`Settings app --> Technical menu --> Automation section --> Automation Rules`. Then, click :guilabel:`New` to create a new rule." +msgstr "" + +#: ../../content/applications/marketing/sms_marketing/essentials/sms_essentials.rst:195 +msgid "Enter a name for the automation rule, and select a :guilabel:`Model` to implement this rule on." +msgstr "" + +#: ../../content/applications/marketing/sms_marketing/essentials/sms_essentials.rst:197 +msgid "Based on the selection for the :guilabel:`Trigger`, additional fields will populate below. Set the :guilabel:`Trigger` to one of the following options:" +msgstr "" + +#: ../../content/applications/marketing/sms_marketing/essentials/sms_essentials.rst:200 +msgid ":guilabel:`Values Updated`" +msgstr "" + +#: ../../content/applications/marketing/sms_marketing/essentials/sms_essentials.rst:202 +msgid ":guilabel:`User is set`" +msgstr "" + +#: ../../content/applications/marketing/sms_marketing/essentials/sms_essentials.rst:203 +msgid ":guilabel:`State is set to`" +msgstr "" + +#: ../../content/applications/marketing/sms_marketing/essentials/sms_essentials.rst:204 +msgid ":guilabel:`On archived`" +msgstr "" + +#: ../../content/applications/marketing/sms_marketing/essentials/sms_essentials.rst:205 +msgid ":guilabel:`On unarchived`" +msgstr "" + +#: ../../content/applications/marketing/sms_marketing/essentials/sms_essentials.rst:207 +msgid ":guilabel:`Timing Conditions`" +msgstr "" + +#: ../../content/applications/marketing/sms_marketing/essentials/sms_essentials.rst:209 +msgid ":guilabel:`Based on date field`" +msgstr "" + +#: ../../content/applications/marketing/sms_marketing/essentials/sms_essentials.rst:210 +msgid ":guilabel:`After creation`" +msgstr "" + +#: ../../content/applications/marketing/sms_marketing/essentials/sms_essentials.rst:211 +msgid ":guilabel:`After last update`" +msgstr "" + +#: ../../content/applications/marketing/sms_marketing/essentials/sms_essentials.rst:213 +msgid ":guilabel:`Custom`" +msgstr "" + +#: ../../content/applications/marketing/sms_marketing/essentials/sms_essentials.rst:215 +msgid ":guilabel:`On save`" +msgstr "" + +#: ../../content/applications/marketing/sms_marketing/essentials/sms_essentials.rst:216 +msgid ":guilabel:`On deletion`" +msgstr "" + +#: ../../content/applications/marketing/sms_marketing/essentials/sms_essentials.rst:217 +msgid ":guilabel:`On UI change`" +msgstr "" + +#: ../../content/applications/marketing/sms_marketing/essentials/sms_essentials.rst:219 +msgid ":guilabel:`External`" +msgstr "" + +#: ../../content/applications/marketing/sms_marketing/essentials/sms_essentials.rst:221 +msgid ":guilabel:`On webhook`" +msgstr "" + +#: ../../content/applications/marketing/sms_marketing/essentials/sms_essentials.rst:223 +msgid "Other options may appear based on the :guilabel:`Model` selected. For example if the :guilabel:`Calendar Event` model is selected, then the following options appear in addition to those above:" +msgstr "" + +#: ../../content/applications/marketing/sms_marketing/essentials/sms_essentials.rst:227 +msgid ":guilabel:`Email Events`" +msgstr "" + +#: ../../content/applications/marketing/sms_marketing/essentials/sms_essentials.rst:229 +msgid ":guilabel:`On incoming message`" +msgstr "" + +#: ../../content/applications/marketing/sms_marketing/essentials/sms_essentials.rst:230 +msgid ":guilabel:`On outgoing message`" +msgstr "" + +#: ../../content/applications/marketing/sms_marketing/essentials/sms_essentials.rst:232 +msgid "Under the :guilabel:`Before Update Domain` field, set a condition to be met before updating the record. Click :guilabel:`Edit Domain` to set record parameters." +msgstr "" + +#: ../../content/applications/marketing/sms_marketing/essentials/sms_essentials.rst:235 +msgid "Under the :guilabel:`Actions To Do` tab, select :guilabel:`Add an action`. Next, in the resulting :guilabel:`Create Actions` pop-up window, select :guilabel:`Send SMS`, and set the :guilabel:`Allowed Groups`. :guilabel:`Allowed Groups` are the access rights groups that are allowed to execute this rule. Leave the field empty to allow all groups. See this documentation: :ref:`access-rights/groups`." +msgstr "" + +#: ../../content/applications/marketing/sms_marketing/essentials/sms_essentials.rst:241 +msgid "Next, set the :guilabel:`SMS Template` and choose whether the SMS message should be logged as a note, by making a selection in the drop-down menu: :guilabel:`Send SMS as`. Click :guilabel:`Save and Close` to save the changes to this new action." +msgstr "" + +#: ../../content/applications/marketing/sms_marketing/essentials/sms_essentials.rst:-1 +msgid "Automation rule template with rule to do, SMS template and log as note highlighted." +msgstr "" + +#: ../../content/applications/marketing/sms_marketing/essentials/sms_essentials.rst:249 +msgid "Add any necessary notes under the :guilabel:`Notes` tab. Finally, navigate away from the completed automation rule, or manually save (by clicking the :guilabel:`☁️ (cloud)` icon), to implement the change." +msgstr "" + +#: ../../content/applications/marketing/sms_marketing/essentials/sms_essentials.rst:254 msgid ":doc:`sms_campaign_settings`" msgstr "" -#: ../../content/applications/marketing/sms_marketing/essentials/sms_essentials.rst:181 +#: ../../content/applications/marketing/sms_marketing/essentials/sms_essentials.rst:255 msgid ":doc:`mailing_lists_blacklists`" msgstr "" +#: ../../content/applications/marketing/sms_marketing/essentials/sms_essentials.rst:256 +msgid ":doc:`../../../essentials/in_app_purchase`" +msgstr "" + #: ../../content/applications/marketing/sms_marketing/pricing.rst:5 msgid "Pricing and FAQ" msgstr "" @@ -3943,10 +5023,6 @@ msgstr "" msgid "The view options are located in the upper right corner of the :guilabel:`Posts` page, beneath the search bar." msgstr "" -#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:391 -msgid "Kanban view" -msgstr "" - #: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:393 msgid "By default, Odoo displays the posts in a kanban view. The information on this page can be sorted even further, via the left sidebar, where all connected social accounts and posts can be quickly seen, accessed, and analyzed." msgstr "" @@ -3959,10 +5035,6 @@ msgstr "" msgid "Kanban view of the posts page in the Odoo Social Marketing application." msgstr "" -#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:404 -msgid "Calendar view" -msgstr "" - #: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:406 msgid "The calendar view option displays a visual representation of posts in a calendar format of when posts were published, or are scheduled to be published. This option provides a clear overview of any planned day, week, or month, and Odoo displays all drafted, scheduled, and published posts." msgstr "" @@ -4116,342 +5188,1142 @@ msgstr "" msgid "Surveys" msgstr "" -#: ../../content/applications/marketing/surveys.rst:8 +#: ../../content/applications/marketing/surveys.rst:7 +msgid "Companies gather valuable insights from customers and employees through surveys, aiding informed decision-making." +msgstr "" + +#: ../../content/applications/marketing/surveys.rst:10 +msgid "With Odoo *Surveys*, users create various surveys, questionnaires, certifications, assessments, and so much more. These can be used to collect feedback, evaluate the success of a recent event, and measure the satisfaction of customers and/or employees. This process yields valuable insights into shifting market trends." +msgstr "" + +#: ../../content/applications/marketing/surveys.rst:16 msgid "`Odoo Tutorials: Surveys `_" msgstr "" +#: ../../content/applications/marketing/surveys.rst:19 +msgid "Dashboard" +msgstr "" + +#: ../../content/applications/marketing/surveys.rst:21 +msgid "Upon opening the *Surveys* application, Odoo presents the main dashboard of the *Surveys* application, otherwise known as the :guilabel:`Surveys` page." +msgstr "" + +#: ../../content/applications/marketing/surveys.rst:-1 +msgid "The Odoo Surveys application dashboard in the default Kanban view." +msgstr "" + +#: ../../content/applications/marketing/surveys.rst:29 +msgid "The *Surveys* dashboard can be accessed at any time throughout the application by clicking :menuselection:`Surveys` from the header menu." +msgstr "" + +#: ../../content/applications/marketing/surveys.rst:32 +msgid "In the upper-left corner, there is a :guilabel:`New` button. When clicked, Odoo presents a blank survey form that can be used to create a survey." +msgstr "" + +#: ../../content/applications/marketing/surveys.rst:35 +msgid "On the dashboard, all the surveys that have been created in the database are displayed in a default Kanban view." +msgstr "" + +#: ../../content/applications/marketing/surveys.rst:38 +msgid "From left-to-right, after the survey name, the user who is responsible for it, and the month it was created, each line on the *Surveys* dashboard shows the following:" +msgstr "" + +#: ../../content/applications/marketing/surveys.rst:41 +msgid "Number of :guilabel:`Questions` in that particular survey" +msgstr "" + +#: ../../content/applications/marketing/surveys.rst:42 +msgid ":guilabel:`Average Duration` of the survey (how long it typically takes a participant to complete)" +msgstr "" + +#: ../../content/applications/marketing/surveys.rst:43 +msgid "Number of :guilabel:`Registered` participants for the survey" +msgstr "" + +#: ../../content/applications/marketing/surveys.rst:44 +msgid "Number of times that particular survey has been :guilabel:`Completed`" +msgstr "" + +#: ../../content/applications/marketing/surveys.rst:45 +msgid "Percentage and data bar showcasing how many people have :guilabel:`Passed` or become :guilabel:`Certified`" +msgstr "" + +#: ../../content/applications/marketing/surveys.rst:49 +msgid "The :guilabel:`Passed` percentage and bar **only** appears when a *Required Score* has been configured for that particular survey." +msgstr "" + +#: ../../content/applications/marketing/surveys.rst:52 +msgid "The :guilabel:`Certified` percentage and bar **only** appears if that particular survey has the *Is a Certification* option enabled on the survey form." +msgstr "" + +#: ../../content/applications/marketing/surveys.rst:55 +msgid "If neither :guilabel:`Passed` nor :guilabel:`Certified` appear on the line, that indicates the survey is without a *Required Score* and was not enabled with the *Is a Certification* option." +msgstr "" + +#: ../../content/applications/marketing/surveys.rst:58 +msgid "Number of :guilabel:`Courses` related to that survey, which **only** appears if more than one course has been created and attached to a single survey" +msgstr "" + +#: ../../content/applications/marketing/surveys.rst:62 +msgid "A half-trophy background image behind the survey name indicates that the survey is a *Certification*." +msgstr "" + +#: ../../content/applications/marketing/surveys.rst:65 +msgid "To the far-right of those data points on the survey lines, located on the *Surveys* application dashboard, are a collection of buttons." +msgstr "" + +#: ../../content/applications/marketing/surveys.rst:68 +msgid "Those buttons are as follows:" +msgstr "" + +#: ../../content/applications/marketing/surveys.rst:70 +msgid ":guilabel:`Share`: click to reveal a :guilabel:`Share a Survey` pop-up form that can be used to invite potential participants to the survey - complete with a :guilabel:`Survey Link` that can be copied and sent to potential participants, and a :guilabel:`Send by Email` toggle switch." +msgstr "" + +#: ../../content/applications/marketing/surveys.rst:74 +msgid "When the :guilabel:`Send by Email` toggle is active (green switch), additional fields appear, in which :guilabel:`Recipients`, :guilabel:`Additional Emails`, and a :guilabel:`Subject` can be added to the email." +msgstr "" + +#: ../../content/applications/marketing/surveys.rst:78 +msgid "Below that, a dynamic email template, complete with a :guilabel:`Start Certification` button appears, which can be modified, as well, if needed." +msgstr "" + +#: ../../content/applications/marketing/surveys.rst:81 +msgid ":guilabel:`Attachments` can be added to the email, as well as an :guilabel:`Answer deadline` can be set, if needed." +msgstr "" + +#: ../../content/applications/marketing/surveys.rst:84 +#: ../../content/applications/marketing/surveys/create.rst:296 +msgid "Once modifications are complete, click :guilabel:`Send` to send that email invite to all the email addresses/contacts listed in the :guilabel:`Recipients` field." +msgstr "" + +#: ../../content/applications/marketing/surveys.rst:0 +#: ../../content/applications/marketing/surveys/create.rst:-1 +msgid "The 'Share a Survey' pop-up window in Odoo Surveys with the Send by Email toggled on." +msgstr "" + +#: ../../content/applications/marketing/surveys.rst:92 +msgid "The default :guilabel:`Mail Template` for survey invites can be edited by navigating to :menuselection:`Settings --> Technical --> Email Templates` and searching for `Survey: Invite`." +msgstr "" + +#: ../../content/applications/marketing/surveys.rst:96 +msgid "The :guilabel:`Send by Email` toggle switch is **not** present when the survey line has zero questions." +msgstr "" + +#: ../../content/applications/marketing/surveys.rst:99 +msgid "The :guilabel:`Survey Link` only appears when the survey's *Access Mode* is set to *Anyone with the link*." +msgstr "" + +#: ../../content/applications/marketing/surveys.rst:102 +msgid "The :guilabel:`Additional Emails` field only appears when the survey's *Require Login* field is **not** active." +msgstr "" + +#: ../../content/applications/marketing/surveys.rst:105 +msgid ":guilabel:`Test`: click to take a test version of the survey in a new tab, from the point-of-view of a survey participant, in order to check for any errors or inconsistencies." +msgstr "" + +#: ../../content/applications/marketing/surveys.rst:107 +msgid ":guilabel:`See results`: click to reveal a new tab showcasing detailed metrics and graphical representations of all survey participants, questions, and responses for deeper analysis." +msgstr "" + +#: ../../content/applications/marketing/surveys.rst:109 +msgid ":guilabel:`Start Live Session`: click to initiate a *Live session* survey, and reveal a session manager window in a new tab. This button is **not** present for surveys that have enabled the *Is a Certification* option on the survey form." +msgstr "" + +#: ../../content/applications/marketing/surveys.rst:112 +msgid ":guilabel:`End Live Session`: click to end a *Live session* survey that has been officially started. This button option **only** appears on survey lines that have previously initiated a live session." +msgstr "" + +#: ../../content/applications/marketing/surveys.rst:116 +msgid "Above the buttons that are located to the far-right of the survey lines, a :guilabel:`⋮ (three dots)` icon appears when the cursor hovers over that particular line. When the :guilabel:`⋮ (three dots)` icon is clicked, a drop-down menu with some configuration-related options appear:" +msgstr "" + +#: ../../content/applications/marketing/surveys.rst:120 +msgid "The options are:" +msgstr "" + +#: ../../content/applications/marketing/surveys.rst:122 +msgid ":guilabel:`Edit Survey`: when clicked, Odoo reveals the survey form for that particular survey, which can then be modified in a number of different ways." +msgstr "" + +#: ../../content/applications/marketing/surveys.rst:124 +msgid ":guilabel:`Share`: when clicked, Odoo reveals the :guilabel:`Share a Survey` pop-up form that can be used to invite potential participants to the survey." +msgstr "" + +#: ../../content/applications/marketing/surveys.rst:126 +msgid ":guilabel:`Delete`: when clicked, Odoo presents a pop-up window, wherein the user **must** confirm they want to delete the survey entirely, which they can do by clicking the :guilabel:`Delete` button at the bottom of the pop-up window." +msgstr "" + +#: ../../content/applications/marketing/surveys.rst:129 +msgid ":guilabel:`Color`: users can opt to choose a color to add to the survey line on the dashboard for added organizational purposes, if needed." +msgstr "" + +#: ../../content/applications/marketing/surveys.rst:-1 +msgid "The three-dot drop-down menu of options that appears on the Odoo Surveys dashboard." +msgstr "" + +#: ../../content/applications/marketing/surveys.rst:136 +msgid "Beneath the buttons that are located to the far-right of the survey lines, there is an *Activities* button, represented by a :guilabel:`🕘 (clock)` icon. When clicked, a mini pop-up window appears, from which activities related to that particular survey can be scheduled and customized." +msgstr "" + +#: ../../content/applications/marketing/surveys.rst:-1 +msgid "The Schedule Activities drop-down menu that appears on the Odoo Surveys dashboard." +msgstr "" + +#: ../../content/applications/marketing/surveys.rst:147 +msgid "The *Surveys* dashboard is shown in the Kanban view, by default, but there is also a list view option available in the upper-right corner, represented by a :guilabel:`≣ (bars)` icon." +msgstr "" + +#: ../../content/applications/marketing/surveys.rst:150 +msgid "When the :guilabel:`≣ (bars)` icon is clicked, the survey related data is displayed in a list view." +msgstr "" + +#: ../../content/applications/marketing/surveys.rst:-1 +msgid "The list view option located on the Odoo Surveys application dashboard." +msgstr "" + +#: ../../content/applications/marketing/surveys.rst:156 +msgid "The columns shown on the *Surveys* app dashboard, while in list view, are as follows:" +msgstr "" + +#: ../../content/applications/marketing/surveys.rst:158 +msgid ":guilabel:`Survey Title`" +msgstr "" + +#: ../../content/applications/marketing/surveys.rst:159 +msgid ":guilabel:`Responsible`" +msgstr "" + +#: ../../content/applications/marketing/surveys.rst:160 +msgid ":guilabel:`Average Duration`" +msgstr "" + +#: ../../content/applications/marketing/surveys.rst:161 +msgid ":guilabel:`Registered`" +msgstr "" + +#: ../../content/applications/marketing/surveys.rst:162 +msgid ":guilabel:`Success Ratio (%)`" +msgstr "" + +#: ../../content/applications/marketing/surveys.rst:163 +msgid ":guilabel:`Avg Score (%)`" +msgstr "" + +#: ../../content/applications/marketing/surveys.rst:166 +msgid "Additional columns can be added to the *Surveys* application dashboard, while in list view, by clicking the *additional options* drop-down menu, located to the far-right of the column titles, represented by a :guilabel:`(slider with two dots)` icon." +msgstr "" + +#: ../../content/applications/marketing/surveys.rst:171 +msgid "Activities view" +msgstr "" + +#: ../../content/applications/marketing/surveys.rst:173 +msgid "To have the *Surveys* application dashboard display nothing but the activities associated to the surveys in the database, click the :guilabel:`🕘 (clock)` icon to the far-right of the other view options, located in the upper-right corner." +msgstr "" + +#: ../../content/applications/marketing/surveys.rst:-1 +msgid "The activities view option located on the Odoo Surveys dashboard." +msgstr "" + +#: ../../content/applications/marketing/surveys.rst:181 +msgid "Doing so reveals a table with rows and columns. The rows show the different surveys in the database, and the columns depict the various activity types." +msgstr "" + +#: ../../content/applications/marketing/surveys.rst:185 +msgid "A new survey cannot be created in this view, as it is solely for the purpose of creating and viewing scheduled activities." +msgstr "" + +#: ../../content/applications/marketing/surveys/analysis.rst:3 +msgid "Survey analysis" +msgstr "" + +#: ../../content/applications/marketing/surveys/analysis.rst:5 +msgid "After surveys have been created and sent to participants, it is only a matter of time before the responses start to come in. When they do, it is important to know where and how to analyze them in the Odoo *Surveys* application." +msgstr "" + +#: ../../content/applications/marketing/surveys/analysis.rst:9 +msgid "Fortunately, Odoo provides numerous ways to view survey responses, allowing users to access and analyze survey responses as they are submitted." +msgstr "" + +#: ../../content/applications/marketing/surveys/analysis.rst:13 +msgid "See results" +msgstr "" + +#: ../../content/applications/marketing/surveys/analysis.rst:15 +msgid "Upon opening the :menuselection:`Surveys` application, the main dashboard reveals a list of all the surveys in the database, along with pertinent information related to each one." +msgstr "" + +#: ../../content/applications/marketing/surveys/analysis.rst:18 +msgid "By default, every survey line showcases its number of :guilabel:`Questions`, :guilabel:`Average Duration`, and how many participants have :guilabel:`Registered` or :guilabel:`Completed` the survey." +msgstr "" + +#: ../../content/applications/marketing/surveys/analysis.rst:22 +msgid "There are also elements showing the percentage of how many participants :guilabel:`Passed` (if a *Required Score (%)* was configured), or how many participants became :guilabel:`Certified` (if the *Is a Certification* option was configured)." +msgstr "" + +#: ../../content/applications/marketing/surveys/analysis.rst:27 +msgid "To learn more about the different analytical elements found on the :guilabel:`Surveys` dashboard, check out the :doc:`Survey Essentials <../surveys/create>` documentation." +msgstr "" + +#: ../../content/applications/marketing/surveys/analysis.rst:30 +msgid "On the :guilabel:`Surveys` dashboard, to the far-right of each survey line displayed in the default list view, there is a :guilabel:`See results` button." +msgstr "" + +#: ../../content/applications/marketing/surveys/analysis.rst:-1 +msgid "The 'See Results' button present on the main dashboard of the Odoo Surveys application." +msgstr "" + +#: ../../content/applications/marketing/surveys/analysis.rst:37 +msgid "When the :guilabel:`See results` button is clicked, a new browser tab opens, revealing a separate page filled with all of that particular survey's results and responses, with an informative :guilabel:`Results Overview` and some filtering drop-down menus at the top." +msgstr "" + +#: ../../content/applications/marketing/surveys/analysis.rst:-1 +msgid "Typical survey results page when 'See results' is clicked from the Odoo Surveys dashboard." +msgstr "" + +#: ../../content/applications/marketing/surveys/analysis.rst:45 +msgid "At the top of the page, there is an :guilabel:`Edit Survey` link, in the middle of a blue header banner. When clicked, Odoo returns the user to the survey form for that particular survey." +msgstr "" + +#: ../../content/applications/marketing/surveys/analysis.rst:48 +msgid "Beneath that, is the title of the survey, and its description, if one was configured for it on its survey form." +msgstr "" + +#: ../../content/applications/marketing/surveys/analysis.rst:51 +msgid "To the right of the survey title, there are two drop-down menus with various filtering options, which can be used to personalize and segment the survey results in a number of different ways." +msgstr "" + +#: ../../content/applications/marketing/surveys/analysis.rst:54 +msgid "The first filter drop-down menu is set on the default :guilabel:`All Surveys` option, meaning the results below are showing results and responses from all the submitted surveys, regardless if they have been fully completed or not." +msgstr "" + +#: ../../content/applications/marketing/surveys/analysis.rst:58 +msgid "When that drop-down menu is clicked open, another option, :guilabel:`Completed surveys`, appears." +msgstr "" + +#: ../../content/applications/marketing/surveys/analysis.rst:-1 +msgid "The 'All surveys' drop-down menu opened on the 'See results' page of the Odoo Surveys app." +msgstr "" + +#: ../../content/applications/marketing/surveys/analysis.rst:64 +msgid "With that drop-down menu open, the number corresponding to each filter option appears to the right of each option." +msgstr "" + +#: ../../content/applications/marketing/surveys/analysis.rst:67 +msgid "To the right of that drop-down menu of filter options, is another drop-down menu of filter options that can be used to further customize the results showcased on this page." +msgstr "" + +#: ../../content/applications/marketing/surveys/analysis.rst:70 +msgid "That drop-down menu is set to the :guilabel:`Passed and Failed` option, by default. This option shows the results and responses from all participants who have passed or failed this particular survey." +msgstr "" + +#: ../../content/applications/marketing/surveys/analysis.rst:75 +msgid "This second drop-down menu of filter options **only** appears if the survey being analyzed has a *Scoring* option configured, or if the *Is a Certification* feature has been enabled." +msgstr "" + +#: ../../content/applications/marketing/surveys/analysis.rst:78 +msgid "When that second drop-down menu of filter options is clicked open, two additional options appear: :guilabel:`Passed only` and :guilabel:`Failed only`." +msgstr "" + +#: ../../content/applications/marketing/surveys/analysis.rst:-1 +msgid "The 'Passed and Failed' drop-down menu on the 'See results' page of the Odoo Surveys app." +msgstr "" + +#: ../../content/applications/marketing/surveys/analysis.rst:85 +msgid "Each option would filter the results below to only show responses from participants who have passed the survey, or who have failed the survey, respectively." +msgstr "" + +#: ../../content/applications/marketing/surveys/analysis.rst:88 +msgid "Directly beneath the survey title, there is a :guilabel:`Print` button. When clicked, the entire results page can be printed." +msgstr "" + +#: ../../content/applications/marketing/surveys/analysis.rst:91 +msgid "The :guilabel:`Results Overview` section is below the survey title, filter option drop-down menus, and :guilabel:`Print` button." +msgstr "" + +#: ../../content/applications/marketing/surveys/analysis.rst:-1 +msgid "The 'Results Overview' section on the 'See results' page in the Odoo Surveys application." +msgstr "" + +#: ../../content/applications/marketing/surveys/analysis.rst:98 +msgid "This section of the results page provides a summarized collection of useful survey-related data and metrics for quick analysis." +msgstr "" + +#: ../../content/applications/marketing/surveys/analysis.rst:102 +msgid "Question analysis" +msgstr "" + +#: ../../content/applications/marketing/surveys/analysis.rst:104 +msgid "Directly beneath the :guilabel:`Results Overview` section is where the results and responses of the survey are found." +msgstr "" + +#: ../../content/applications/marketing/surveys/analysis.rst:108 +msgid "The various sections of the survey, if there were any, appear at the top of their corresponding questions on the results page, as well, for added organization." +msgstr "" + +#: ../../content/applications/marketing/surveys/analysis.rst:111 +msgid "Every question that was a part of the survey is shown, along with an in-depth breakdown, and visual representation, of how it was answered by participants, beneath the :guilabel:`Results Overview` section." +msgstr "" + +#: ../../content/applications/marketing/surveys/analysis.rst:115 +msgid "Each question is displayed above its corresponding results. To the left of the question is an :guilabel:`👁️ (eye)` icon. When clicked, Odoo hides the visual and data-related results and responses. When clicked again, that question's visual and data-related results re-appear." +msgstr "" + +#: ../../content/applications/marketing/surveys/analysis.rst:119 +msgid "To the far-right of the question, there are indicators to see how many participants :guilabel:`Responded` and how many :guilabel:`Skipped` the question." +msgstr "" + +#: ../../content/applications/marketing/surveys/analysis.rst:-1 +msgid "The Responded and Skipped indicators on the 'See results' page in Odoo Surveys." +msgstr "" + +#: ../../content/applications/marketing/surveys/analysis.rst:126 +msgid "If the question required the participant to enter in their own answer, without any options to choose from, like entering a specific number or date, for example, there is also an indicator to showcase how many users answered the question :guilabel:`Correct`." +msgstr "" + +#: ../../content/applications/marketing/surveys/analysis.rst:-1 +msgid "Sample of a 'correct' indicator on the 'See results' page in the Odoo Surveys application." +msgstr "" + +#: ../../content/applications/marketing/surveys/analysis.rst:135 +msgid "Even if there is no configured *correct* response for question of this nature, the :guilabel:`Correct` indicator still appears, although, it displays a `0`." +msgstr "" + +#: ../../content/applications/marketing/surveys/analysis.rst:138 +msgid "This would occur for opinion-based questions, like `When would be a good time to hold another sale?`" +msgstr "" + +#: ../../content/applications/marketing/surveys/analysis.rst:141 +msgid "If there is only one correct response to a multiple choice question, those results and responses are represented by a :guilabel:`Pie Graph`. The correct answer is indicated by a :guilabel:`✔️ (checkmark)` icon next to the correct answer option, in the legend above the graph." +msgstr "" + +#: ../../content/applications/marketing/surveys/analysis.rst:-1 +msgid "Typical pie graph results on the 'See results' page in the Odoo Surveys application." +msgstr "" + +#: ../../content/applications/marketing/surveys/analysis.rst:149 +msgid "If there are multiple correct answer options (or no correct answers at all) for a multiple choice question, those results and responses are represented by a :guilabel:`Bar Graph`." +msgstr "" + +#: ../../content/applications/marketing/surveys/analysis.rst:-1 +msgid "Typical bar graph results on the 'See results' page in the Odoo Surveys application." +msgstr "" + +#: ../../content/applications/marketing/surveys/analysis.rst:156 +msgid "Each multiple choice question has a :guilabel:`Graph` tab and an :guilabel:`Data` tab. The graph-related tab is shown by default." +msgstr "" + +#: ../../content/applications/marketing/surveys/analysis.rst:159 +msgid "The :guilabel:`Data` tab shows all the provided :guilabel:`Answer` options for the question. The :guilabel:`User Choice` (with percentages and votes) along with the :guilabel:`Score` of each option." +msgstr "" + +#: ../../content/applications/marketing/surveys/analysis.rst:-1 +msgid "Typical 'Data' tab on the 'See results' page in the Odoo Surveys application." +msgstr "" + +#: ../../content/applications/marketing/surveys/analysis.rst:167 +msgid "Other question types, wherein there were no answer options for the participant to choose from, there is a :guilabel:`Most Common` tab and an :guilabel:`All Data` tab." +msgstr "" + +#: ../../content/applications/marketing/surveys/analysis.rst:170 +msgid "The :guilabel:`Most Common` tab shows the :guilabel:`User Responses`, the :guilabel:`Occurrence`, and the :guilabel:`Score` (if applicable)." +msgstr "" + +#: ../../content/applications/marketing/surveys/analysis.rst:-1 +msgid "Typical 'Most Common' tab on the 'See results' page in the Odoo Surveys application." +msgstr "" + +#: ../../content/applications/marketing/surveys/analysis.rst:177 +msgid "The :guilabel:`All Data` tab shows a list of all the submitted responses to that particular question." +msgstr "" + +#: ../../content/applications/marketing/surveys/analysis.rst:-1 +msgid "Typical 'All Data' tab on the 'See results' page in the Odoo Surveys application." +msgstr "" + +#: ../../content/applications/marketing/surveys/analysis.rst:184 +msgid "If a question is looking for participants to enter a numerical value as a response, :guilabel:`Maximum`, :guilabel:`Minimum`, and :guilabel:`Average` indicators appear to the far-right of the results tabs." +msgstr "" + +#: ../../content/applications/marketing/surveys/analysis.rst:-1 +msgid "The Maximum, Minimum, and Average indicators on the 'See results' page in Odoo Surveys." +msgstr "" + +#: ../../content/applications/marketing/surveys/analysis.rst:192 +msgid "A :guilabel:`filter` icon is also present either to the right of the :guilabel:`User Choice` column in a :guilabel:`Data` tab, or to the far-right of a :guilabel:`User Response` line in an :guilabel:`All Data` tab." +msgstr "" + +#: ../../content/applications/marketing/surveys/analysis.rst:-1 +msgid "Typical 'Filter' icon on the 'See results' page in the Odoo Surveys application." +msgstr "" + +#: ../../content/applications/marketing/surveys/analysis.rst:200 +msgid "When that :guilabel:`filter` icon is clicked, Odoo returns the user to the top of the results page, with that chosen filter applied, showing the results of each question for participants who submitted that particular answer for that specific question." +msgstr "" + +#: ../../content/applications/marketing/surveys/analysis.rst:-1 +msgid "The applied filter on the 'See results' page in the Odoo Surveys application." +msgstr "" + +#: ../../content/applications/marketing/surveys/analysis.rst:208 +msgid "Therefore, showcasing the remaining results for participants who answered that specific question in the same way. To remove that filter, and reveal all the results once again, click :guilabel:`Remove all filters` or click the :guilabel:`✖️ (X)` icon in the filter box at the top of the results page." +msgstr "" + +#: ../../content/applications/marketing/surveys/analysis.rst:213 +msgid "Participations" +msgstr "" + +#: ../../content/applications/marketing/surveys/analysis.rst:215 +msgid "To view a consolidated list of participation results for a specific survey, navigate to :menuselection:`Surveys app`, select the desired survey from the list, and click the :guilabel:`Participations` smart button at the top of the survey form." +msgstr "" + +#: ../../content/applications/marketing/surveys/analysis.rst:-1 +msgid "The Participations smart button at the top of a survey form in Odoo Surveys." +msgstr "" + +#: ../../content/applications/marketing/surveys/analysis.rst:223 +msgid "Doing so reveals a separate :guilabel:`Participations` page, showcasing the participants for that specific survey, along with a collection of pertinent information related to each one." +msgstr "" + +#: ../../content/applications/marketing/surveys/analysis.rst:-1 +msgid "The Participations page for a singular survey in the Odoo Surveys application." +msgstr "" + +#: ../../content/applications/marketing/surveys/analysis.rst:230 +msgid "Here, users can view information related to individual participants who took that specific survey. If they desire to see a more detailed breakdown of their various answers and responses, they can click on any participant, and Odoo reveals a separate page showing that participant's survey details, along with their submitted answers." +msgstr "" + +#: ../../content/applications/marketing/surveys/analysis.rst:-1 +msgid "An individual participant's detail form in the Odoo Surveys application." +msgstr "" + +#: ../../content/applications/marketing/surveys/analysis.rst:239 +msgid "To view a consolidated list of all participants of every survey in the database, navigate to :menuselection:`Surveys app --> Participations`. Here, every survey in the database is shown in a default nested list. Beside each survey title has the number of participants in parenthesis." +msgstr "" + +#: ../../content/applications/marketing/surveys/analysis.rst:-1 +msgid "The Participations page for all surveys in the Odoo Surveys application." +msgstr "" + +#: ../../content/applications/marketing/surveys/analysis.rst:247 +msgid "When a survey is un-nested from this list, by clicking the survey title, the corresponding participants, along with their response-related data for that survey, appear on the page." +msgstr "" + +#: ../../content/applications/marketing/surveys/analysis.rst:250 +msgid "The :guilabel:`Participations` page can also be viewed in a Kanban layout, as well." +msgstr "" + +#: ../../content/applications/marketing/surveys/analysis.rst:-1 +msgid "The Participations page in the Kanban view in the Odoo Surveys application." +msgstr "" + +#: ../../content/applications/marketing/surveys/analysis.rst:257 +#: ../../content/applications/marketing/surveys/live_session.rst:219 +msgid ":doc:`create`" +msgstr "" + +#: ../../content/applications/marketing/surveys/analysis.rst:258 +#: ../../content/applications/marketing/surveys/create.rst:331 +#: ../../content/applications/marketing/surveys/live_session.rst:221 +msgid ":doc:`scoring`" +msgstr "" + #: ../../content/applications/marketing/surveys/create.rst:3 -msgid "Survey essentials" +msgid "Create surveys" msgstr "" #: ../../content/applications/marketing/surveys/create.rst:5 -msgid "Companies often use surveys to collect valuable information from their customers and employees, which in turn, allows them to make more informed business decisions." +msgid "To create a survey in the Odoo *Surveys* application, navigate to :menuselection:`Surveys app --> New` to reveal a blank survey form." msgstr "" -#: ../../content/applications/marketing/surveys/create.rst:8 -msgid "In Odoo, surveys are used to collect customer feedback, evaluate the success of a recent event, measure the satisfaction of customers (or employees), and gain more insight into shifting market sentiments." +#: ../../content/applications/marketing/surveys/create.rst:9 +msgid "The :guilabel:`New` button is **not** present on the *Surveys* dashboard if in the *Activities* view." msgstr "" #: ../../content/applications/marketing/surveys/create.rst:13 -msgid "Getting started" +msgid "Survey form" msgstr "" -#: ../../content/applications/marketing/surveys/create.rst:15 -msgid "To begin, open the :guilabel:`Surveys` application and click :guilabel:`Create`. Odoo then redirects the page to a blank survey template form." +#: ../../content/applications/marketing/surveys/create.rst:-1 +msgid "How a blank survey form looks in the Odoo Surveys application." msgstr "" -#: ../../content/applications/marketing/surveys/create.rst:18 -msgid "On the survey form, add a :guilabel:`Survey Title` and then add a cover image to the survey by hovering over the photo icon and clicking on the :guilabel:`Edit (pencil)` icon. When the file explorer window opens, choose an image from the local files." +#: ../../content/applications/marketing/surveys/create.rst:19 +msgid "At the top of the survey form are four radio buttons, each representing a survey style. The radio button options are:" msgstr "" #: ../../content/applications/marketing/surveys/create.rst:22 -msgid "Below the :guilabel:`Survey Title` are various tabs in which the survey questions and format can be created and customized. These tabs are labeled as follows:" +msgid ":guilabel:`Survey`" +msgstr "" + +#: ../../content/applications/marketing/surveys/create.rst:23 +msgid ":guilabel:`Live Session`" +msgstr "" + +#: ../../content/applications/marketing/surveys/create.rst:24 +msgid ":guilabel:`Assessment`" msgstr "" #: ../../content/applications/marketing/surveys/create.rst:25 -msgid ":guilabel:`Questions`: the list of questions to be asked in the survey" -msgstr "" - -#: ../../content/applications/marketing/surveys/create.rst:26 -msgid ":guilabel:`Description`: contextual information to aid in understanding the survey" +msgid ":guilabel:`Custom` (selected by default)" msgstr "" #: ../../content/applications/marketing/surveys/create.rst:27 -msgid ":guilabel:`Options`: choices for survey respondents to answer the questions" +msgid "These options are here to streamline the survey-making process, by providing users with automated settings and options that are ideally specific to those types of surveys. Each of those survey type options comes equipped with its own specific selection of options." msgstr "" -#: ../../content/applications/marketing/surveys/create.rst:-1 -msgid "Various tabs that can be found on the survey template page." +#: ../../content/applications/marketing/surveys/create.rst:31 +msgid "The :guilabel:`Custom` option, selected by default, offers all the options from every potential survey type (located in the :guilabel:`Options` tab)." msgstr "" #: ../../content/applications/marketing/surveys/create.rst:34 -msgid "Questions tab" +msgid "Beneath those radio survey type options is a blank field in which a name for the survey **must** be entered." msgstr "" -#: ../../content/applications/marketing/surveys/create.rst:36 -msgid "Add questions and sections to the survey in the :guilabel:`Questions` tab. A section divides the survey into parts in order to visually group similar questions together. To make a section, click :guilabel:`Add a section` and type in a section name. Then, add questions or drag and drop questions into the divided sections." +#: ../../content/applications/marketing/surveys/create.rst:37 +msgid "Below the survey name field, is the :guilabel:`Responsible` field. Choose a user from the drop-down menu to be in charge of the survey. By default, the user who initially created the survey is selected as the default :guilabel:`Responsible`." msgstr "" #: ../../content/applications/marketing/surveys/create.rst:41 -msgid "Clicking :guilabel:`Add a question` opens the :guilabel:`Create Sections and Questions` pop-up to create and customize the survey question." +msgid "To the right of those fields, and above the tabs, is the option to add a background image, represented by a :guilabel:`📷 (camera)` icon. When clicked, the option to upload an image becomes available. This image would be used as the background image for the entire survey. This is **not** a required option." msgstr "" -#: ../../content/applications/marketing/surveys/create.rst:-1 -msgid "The survey question pop-up window." +#: ../../content/applications/marketing/surveys/create.rst:46 +msgid "Below those fields and options are four tabs: :guilabel:`Questions`, :guilabel:`Options`, :guilabel:`Description`, and :guilabel:`End Message`." msgstr "" -#: ../../content/applications/marketing/surveys/create.rst:49 -msgid "Create questions" +#: ../../content/applications/marketing/surveys/create.rst:50 +#: ../../content/applications/marketing/surveys/time_random.rst:20 +msgid "Questions tab" msgstr "" -#: ../../content/applications/marketing/surveys/create.rst:51 -msgid "In the :guilabel:`Create Sections and Questions` pop-up, type the question in the :guilabel:`Question` field. Then, choose the :guilabel:`Question Type`. A preview of how the question type looks is shown in the preview window." +#: ../../content/applications/marketing/surveys/create.rst:52 +msgid "View, access, add, and/or delete questions and sections to the survey in the :guilabel:`Questions` tab." msgstr "" #: ../../content/applications/marketing/surveys/create.rst:55 -msgid "Choose from the following :guilabel:`Question Types`:" -msgstr "" - -#: ../../content/applications/marketing/surveys/create.rst:57 -msgid ":guilabel:`Multiple Lines Text Box`" +#: ../../content/applications/marketing/surveys/time_random.rst:25 +msgid "By default, two columns are present in the :guilabel:`Questions` tab: :guilabel:`Title` (i.e. the question) and :guilabel:`Question Type`." msgstr "" #: ../../content/applications/marketing/surveys/create.rst:58 -msgid ":guilabel:`Single Line Text Box`" -msgstr "" - -#: ../../content/applications/marketing/surveys/create.rst:59 -msgid ":guilabel:`Numerical Value`" -msgstr "" - -#: ../../content/applications/marketing/surveys/create.rst:60 -msgid ":guilabel:`Date`" -msgstr "" - -#: ../../content/applications/marketing/surveys/create.rst:61 -msgid ":guilabel:`Datetime`" +#: ../../content/applications/marketing/surveys/time_random.rst:28 +msgid "If the :guilabel:`Randomized per Section` option is enabled in the :guilabel:`Options` tab of the survey form, a column titled, :guilabel:`# Questions Randomly Picked` appears in the :guilabel:`Questions` tab." msgstr "" #: ../../content/applications/marketing/surveys/create.rst:62 -msgid ":guilabel:`Multiple choice: only one answer`" +msgid "Indicate whether questions require a mandatory answer by clicking the :guilabel:`(optional columns)` icon to the far-right of the column titles. Then, select :guilabel:`Mandatory Answer` from the drop-down menu to reveal the :guilabel:`Mandatory Answer` column in the :guilabel:`Questions` tab." msgstr "" -#: ../../content/applications/marketing/surveys/create.rst:63 -msgid ":guilabel:`Multiple choice: multiple answers allowed`" +#: ../../content/applications/marketing/surveys/create.rst:-1 +msgid "The slider drop-down menu with the Mandatory Answer option selected in Odoo Surveys." msgstr "" -#: ../../content/applications/marketing/surveys/create.rst:64 -msgid ":guilabel:`Matrix`" +#: ../../content/applications/marketing/surveys/create.rst:71 +msgid "Add a question" msgstr "" -#: ../../content/applications/marketing/surveys/create.rst:67 -msgid "Different features appear in the :guilabel:`Answers` and :guilabel:`Options` tabs, depending on the :guilabel:`Question Type` chosen. However, the :guilabel:`Description` tab always remains the same, regardless of what question is chosen." +#: ../../content/applications/marketing/surveys/create.rst:73 +msgid "To add a question to a survey, click :guilabel:`Add a question` in the :guilabel:`Questions` tab, and proceed to fill out the :guilabel:`Create Sections and Questions` pop-up window that appears." msgstr "" -#: ../../content/applications/marketing/surveys/create.rst:72 -msgid "Create sections and questions" +#: ../../content/applications/marketing/surveys/create.rst:76 +msgid "To learn how to create and customize questions, refer to the :doc:`create questions ` documentation." msgstr "" -#: ../../content/applications/marketing/surveys/create.rst:74 -msgid "Once a :guilabel:`Question Type` has been selected, there are three possible tabs where information can be customized for the question. These include the :guilabel:`Answers` (if applicable), :guilabel:`Description`, and :guilabel:`Options` tabs." +#: ../../content/applications/marketing/surveys/create.rst:80 +#: ../../content/applications/marketing/surveys/time_random.rst:73 +msgid "There **must** be a survey title entered in order for the :guilabel:`Create Sections and Questions` pop-up window to appear. If no title is entered for the survey, an error pop-up message appears in the upper-right corner, instructing the user to enter a survey title." msgstr "" -#: ../../content/applications/marketing/surveys/create.rst:78 -msgid "Each tab offers a variety of different features depending on what :guilabel:`Question Type` was chosen." -msgstr "" - -#: ../../content/applications/marketing/surveys/create.rst:81 -msgid "For example, in the :guilabel:`Options` tab, the following options may appear:" -msgstr "" - -#: ../../content/applications/marketing/surveys/create.rst:83 -msgid ":guilabel:`Mandatory Answer`: the question must be answered." -msgstr "" - -#: ../../content/applications/marketing/surveys/create.rst:84 -msgid ":guilabel:`Matrix Type`: for matrix-type questions, select if one choice or multiple choices can be selected per row." -msgstr "" - -#: ../../content/applications/marketing/surveys/create.rst:86 -msgid ":guilabel:`Number of columns`: select how many columns are displayed." +#: ../../content/applications/marketing/surveys/create.rst:85 +msgid "Add a section" msgstr "" #: ../../content/applications/marketing/surveys/create.rst:87 -msgid ":guilabel:`Images on answers`: allow images on the answer options." +#: ../../content/applications/marketing/surveys/time_random.rst:43 +msgid "A *section* divides the survey into organized parts, in order to visually group similar questions together. To make a section, click :guilabel:`Add a section` at the bottom of the :guilabel:`Questions` tab, proceed to type in a desired name for the section, then either press :kbd:`Enter` or click away." msgstr "" -#: ../../content/applications/marketing/surveys/create.rst:88 -msgid ":guilabel:`Conditional Display`: determine if the question is displayed based on the participant's answer to a previous question." -msgstr "" - -#: ../../content/applications/marketing/surveys/create.rst:90 -msgid ":guilabel:`Show Comments Field`: allow the participant to type a comment in a text box." -msgstr "" - -#: ../../content/applications/marketing/surveys/create.rst:91 -msgid ":guilabel:`Question Time Limit`: for live session surveys, set a time limit for the question." +#: ../../content/applications/marketing/surveys/create.rst:92 +#: ../../content/applications/marketing/surveys/time_random.rst:48 +msgid "The section line appears in dark gray in the :guilabel:`Questions` tab." msgstr "" #: ../../content/applications/marketing/surveys/create.rst:94 -msgid "Conditional Display" +msgid "Then, drag-and-drop desired questions beneath a section, or drag-and-drop a section title on top of (i.e. *before*) the desired question(s) in the survey. Doing so populates the section with questions that align with its theme." msgstr "" -#: ../../content/applications/marketing/surveys/create.rst:96 -msgid ":guilabel:`Conditional Display` means the question is only displayed if the specified conditional answer has been selected in a previous question." -msgstr "" - -#: ../../content/applications/marketing/surveys/create.rst:99 -msgid "When the box next to :guilabel:`Conditional Display` is selected, the :guilabel:`Triggering Question` field appears. Select a question from the survey." +#: ../../content/applications/marketing/surveys/create.rst:98 +#: ../../content/applications/marketing/surveys/time_random.rst:54 +msgid "If the :guilabel:`Randomized per Section` option is enabled in the :guilabel:`Options` tab of the survey form, the number `1` appears, by default, on the section line, beneath the :guilabel:`# Questions Randomly Picked` column." msgstr "" #: ../../content/applications/marketing/surveys/create.rst:102 -msgid "Then, a :guilabel:`Triggering Answer` field appears. Here, select which answer will trigger this :guilabel:`Conditional Display` question." -msgstr "" - -#: ../../content/applications/marketing/surveys/create.rst:106 -msgid "Options tab" +#: ../../content/applications/marketing/surveys/time_random.rst:58 +msgid "This indicates that `1` question from that section will be picked at random for each participant taking the survey, bypassing every other, non-chosen question from that section. To change that number, select that figure, and type in the desired number in its place. Then, either press :kbd:`Enter`, or click away." msgstr "" #: ../../content/applications/marketing/surveys/create.rst:108 -msgid "Back on the main survey template form, under the :guilabel:`Options` tab, there are different sections of settings that can be modified." +#: ../../content/applications/marketing/surveys/live_session.rst:57 +#: ../../content/applications/marketing/surveys/time_random.rst:207 +msgid "Options tab" msgstr "" -#: ../../content/applications/marketing/surveys/create.rst:111 -msgid "The sections include:" -msgstr "" - -#: ../../content/applications/marketing/surveys/create.rst:113 -msgid ":guilabel:`Questions`: focuses on the overall presentation of the survey" +#: ../../content/applications/marketing/surveys/create.rst:110 +msgid "In the :guilabel:`Options` tab of the survey form, there are many options to choose from, separated in four different sections: :guilabel:`Questions`, :guilabel:`Time & Scoring`, :guilabel:`Participants`, and :guilabel:`Live Session`." msgstr "" #: ../../content/applications/marketing/surveys/create.rst:114 -msgid ":guilabel:`Scoring`: decides how the survey is scored" +msgid "The options available in this tab vary on the survey type chosen, via the radio buttons at the top of the survey form: :guilabel:`Survey`, :guilabel:`Live Session`, :guilabel:`Assessment`, or :guilabel:`Custom`." msgstr "" -#: ../../content/applications/marketing/surveys/create.rst:115 -msgid ":guilabel:`Candidates`: manages access to the survey" -msgstr "" - -#: ../../content/applications/marketing/surveys/create.rst:116 -msgid ":guilabel:`Live Session`: enables the survey into a real-time group activity." -msgstr "" - -#: ../../content/applications/marketing/surveys/create.rst:119 -msgid "Questions" -msgstr "" - -#: ../../content/applications/marketing/surveys/create.rst:121 -msgid "First, select the :guilabel:`Layout` of the survey. The following options can be chosen:" +#: ../../content/applications/marketing/surveys/create.rst:118 +msgid "The :guilabel:`Custom` survey type showcases all the possible options in the :guilabel:`Options` tab. So, if any of the following options do **not** appear in the :guilabel:`Options` tab, it is likely because the selected survey type does not offer it." msgstr "" #: ../../content/applications/marketing/surveys/create.rst:123 -msgid ":guilabel:`One page with all the questions`" +#: ../../content/applications/marketing/surveys/live_session.rst:66 +msgid "Questions section" msgstr "" -#: ../../content/applications/marketing/surveys/create.rst:124 -msgid ":guilabel:`One page per section`" +#: ../../content/applications/marketing/surveys/create.rst:-1 +msgid "The Questions section of the Options tab on a survey form in Odoo Surveys." msgstr "" -#: ../../content/applications/marketing/surveys/create.rst:125 -msgid ":guilabel:`One page per question`" +#: ../../content/applications/marketing/surveys/create.rst:129 +msgid "The first field in the :guilabel:`Questions` section revolves around the :guilabel:`Pagination`, or overall layout, of the survey." msgstr "" -#: ../../content/applications/marketing/surveys/create.rst:127 -msgid "If either the :guilabel:`One page per section` or :guilabel:`One page per question` options are chosen, then the :guilabel:`Back Button` option appears. If selected, the :guilabel:`Back Button` option allows the participant to go back to a question during the survey." +#: ../../content/applications/marketing/surveys/create.rst:132 +msgid "Choose between :guilabel:`One page per question`, :guilabel:`One page per section`, or :guilabel:`One page with all the questions` in the :guilabel:`Pagination` field." msgstr "" -#: ../../content/applications/marketing/surveys/create.rst:131 -msgid "Under the :guilabel:`Layout` options is the :guilabel:`Progression Mode` setting, which indicates how the participant's progress during the survey is displayed. It is shown as either a :guilabel:`Percentage` or a :guilabel:`Number`." +#: ../../content/applications/marketing/surveys/create.rst:136 +msgid "If :guilabel:`One page with all the questions` is selected, all the remaining options in the :guilabel:`Questions` field, apart from :guilabel:`Question Selection` is removed, as they are no longer needed." msgstr "" -#: ../../content/applications/marketing/surveys/create.rst:135 -msgid "Next, there is an option available to add a :guilabel:`Survey Time Limit`. To implement this option, simply check the box, and enter the amount of time (in minutes) participants have to complete the survey." +#: ../../content/applications/marketing/surveys/create.rst:140 +msgid "Next, select one of the following options in the :guilabel:`Display Progress as` field:" msgstr "" -#: ../../content/applications/marketing/surveys/create.rst:139 -msgid "After the :guilabel:`Survey Time Limit` option is a section labeled :guilabel:`Selection`. Here, questions can be :guilabel:`Randomized per section`, in other words, the number of random questions can be configured by section. This mode is ignored in a live session." +#: ../../content/applications/marketing/surveys/create.rst:142 +msgid ":guilabel:`Percentage left`: displays the percentage of the survey remaining to participants." msgstr "" -#: ../../content/applications/marketing/surveys/create.rst:144 +#: ../../content/applications/marketing/surveys/create.rst:143 +msgid ":guilabel:`Number`: display the number of questions answered along with the total number of questions to answer." +msgstr "" + +#: ../../content/applications/marketing/surveys/create.rst:146 +msgid "In the :guilabel:`Question Selection` field choose to have the survey show :guilabel:`All questions` or :guilabel:`Randomized per Section`. If :guilabel:`Randomized per Section` a new column appears in the :guilabel:`Questions` tab, titled: :guilabel:`# Questions Randomly Picked`." +msgstr "" + +#: ../../content/applications/marketing/surveys/create.rst:150 +msgid "In the :guilabel:`# Questions Randomly Picked` column, designate how many questions, in that particular section, should be chosen at random to the participant." +msgstr "" + +#: ../../content/applications/marketing/surveys/create.rst:153 +msgid "Lastly, there is the :guilabel:`Allow Roaming` option. When enabled, participants are able to navigate back to previous pages in the survey." +msgstr "" + +#: ../../content/applications/marketing/surveys/create.rst:157 +#: ../../content/applications/marketing/surveys/live_session.rst:85 +msgid "Time & Scoring section" +msgstr "" + +#: ../../content/applications/marketing/surveys/create.rst:-1 +msgid "The Time and Scoring section of the Options tab on a survey form in Odoo Surveys." +msgstr "" + +#: ../../content/applications/marketing/surveys/create.rst:163 +msgid "The first option in the :guilabel:`Time & Scoring` section is the :guilabel:`Survey Time Limit` option. If enabled, proceed to enter in an amount of time (in :guilabel:`minutes`) to be set as the time limit for the survey." +msgstr "" + +#: ../../content/applications/marketing/surveys/create.rst:167 +msgid "Next, in the :guilabel:`Scoring` section, determine whether there should be: :guilabel:`No scoring`, :guilabel:`Scoring with answers after each page`, :guilabel:`Scoring with answers at the end`, or :guilabel:`Scoring without answers`." +msgstr "" + +#: ../../content/applications/marketing/surveys/create.rst:171 +msgid "If the :guilabel:`No scoring` option is selected, no other options are available in this section. However, if any *other* :guilabel:`Scoring` option is selected, two additional fields appear: :guilabel:`Required Score (%)` and :guilabel:`Is a Certification`." +msgstr "" + +#: ../../content/applications/marketing/surveys/create.rst:175 +msgid "In the :guilabel:`Required Score (%)` field, enter the minimum percentage participants **must** earn in order to pass the survey. Scores below this threshold are considered fails. This figure is also used to determine if a participant is 'certified' or not, if the :guilabel:`Is a Certification` option is enabled." +msgstr "" + +#: ../../content/applications/marketing/surveys/create.rst:180 +msgid "If the :guilabel:`Is a Certification` option is enabled, that makes the survey a *Certification*, which is represented on the main *Surveys* app dashboard via a half-tropy image behind the survey title, while in the default Kanban view. Or, via a full-trophy icon, while in list view." +msgstr "" + +#: ../../content/applications/marketing/surveys/create.rst:184 +msgid "When the :guilabel:`Is a Certification` option is enabled, three additional fields appear -- one beside the option, and two below." +msgstr "" + +#: ../../content/applications/marketing/surveys/create.rst:187 +msgid "In the field that appears beside the option, users can select (and :guilabel:`Preview`) a certification template." +msgstr "" + +#: ../../content/applications/marketing/surveys/create.rst:190 +msgid "Beneath that, in the :guilabel:`Certified Email Template` field, users can select a preconfigured email template, or create one on-the-fly, to be sent to certified participants of the survey upon completion." +msgstr "" + +#: ../../content/applications/marketing/surveys/create.rst:194 +msgid "Lastly, if the :guilabel:`Give Badge` field is enabled, a preconfigured badge is then displayed on the contact page for that certified survey participant." +msgstr "" + +#: ../../content/applications/marketing/surveys/create.rst:198 +#: ../../content/applications/marketing/surveys/live_session.rst:105 +msgid "Participants section" +msgstr "" + +#: ../../content/applications/marketing/surveys/create.rst:-1 +msgid "The Participants section of the Options tab on a survey form in Odoo Surveys." +msgstr "" + +#: ../../content/applications/marketing/surveys/create.rst:204 +msgid "The first available option in the :guilabel:`Participants` section is the :guilabel:`Access Mode` field. This is where users can determine who has access to the survey. Users can select either: :guilabel:`Anyone with the link` or :guilabel:`Invited people only`." +msgstr "" + +#: ../../content/applications/marketing/surveys/create.rst:208 +msgid "Next, there is the option to :guilabel:`Require Login`. Enabling this feature means users **must** login before being able to take the survey, even if they have a valid token." +msgstr "" + +#: ../../content/applications/marketing/surveys/create.rst:211 +msgid "Lastly, in there is the :guilabel:`Limit Attempts` field. If enabled, an additional field appears beside it, in which users can determine how many times users can attempt this survey." +msgstr "" + +#: ../../content/applications/marketing/surveys/create.rst:215 +#: ../../content/applications/marketing/surveys/live_session.rst:117 +msgid "Live Session section" +msgstr "" + +#: ../../content/applications/marketing/surveys/create.rst:-1 +msgid "The Live Session section of the Options tab on a survey form in Odoo Surveys." +msgstr "" + +#: ../../content/applications/marketing/surveys/create.rst:222 +msgid "The :guilabel:`Live Session` section in the :guilabel:`Options` tab of the survey form **only** pertains to *Live Session* surveys." +msgstr "" + +#: ../../content/applications/marketing/surveys/create.rst:225 +msgid "The first option in the :guilabel:`Live Session` section is the :guilabel:`Session Code` field. In this field, enter a custom code, consisting of letters, numbers, and/or symbols, to be used by participants in order to access the live session survey." +msgstr "" + +#: ../../content/applications/marketing/surveys/create.rst:229 +msgid "Next, is the :guilabel:`Session Link` field, which **cannot** be customized, but it *can* be sent out to potential participants." +msgstr "" + +#: ../../content/applications/marketing/surveys/create.rst:233 +msgid "If a :guilabel:`Session Code` has been entered, the URL in the :guilabel:`Session Link` field ends with that specific :guilabel:`Session Code`." +msgstr "" + +#: ../../content/applications/marketing/surveys/create.rst:236 +msgid "If that complete :guilabel:`Session Link` (ending in the custom :guilabel:`Session Code`) is used by participants to access the live session survey, that link would *already* be entered for them. At that point, they'd simply have to wait until the host of the live session begins the survey, and then they'd be able to enter." +msgstr "" + +#: ../../content/applications/marketing/surveys/create.rst:241 +msgid "If the :guilabel:`Session Link` (ending in the custom :guilabel:`Session Code`) is sent **without** including the :guilabel:`Session Code` ending, participants trying to access the live session, via that link, will need to enter the custom :guilabel:`Session Code` to gain access." +msgstr "" + +#: ../../content/applications/marketing/surveys/create.rst:245 +msgid "If the :guilabel:`Session Code` field is empty, a slightly longer, more complicated URL populates the :guilabel:`Session Link` field. When participants attempt to access the live session via that link (without a configured :guilabel:`Session Code`), all they have to do is wait for the host of the live session to begin the survey, and they'd be able to participate." +msgstr "" + +#: ../../content/applications/marketing/surveys/create.rst:250 +msgid "Lastly, in the :guilabel:`Live Session` section, there is the option to :guilabel:`Reward quick answers`. If that option is enabled, participants who submit their answer quickly receive more points." +msgstr "" + +#: ../../content/applications/marketing/surveys/create.rst:255 +#: ../../content/applications/marketing/surveys/time_random.rst:198 +msgid "Description tab" +msgstr "" + +#: ../../content/applications/marketing/surveys/create.rst:257 +msgid "In this non-required tab, users can enter a custom description about the survey, along with any explanations or guidance that a survey participant may need in order to properly participate (and complete) the survey." +msgstr "" + +#: ../../content/applications/marketing/surveys/create.rst:262 +msgid "End Message tab" +msgstr "" + +#: ../../content/applications/marketing/surveys/create.rst:264 +msgid "In this non-required tab, users can enter a custom message that participants see upon completing the survey." +msgstr "" + +#: ../../content/applications/marketing/surveys/create.rst:268 +msgid "Survey form buttons" +msgstr "" + +#: ../../content/applications/marketing/surveys/create.rst:270 +msgid "Once the survey has been configured properly, and questions have been added, the user can utilize any of the available buttons in the upper-left corner of the survey form." +msgstr "" + +#: ../../content/applications/marketing/surveys/create.rst:-1 +msgid "The various buttons on a survey form in Odoo Surveys." +msgstr "" + +#: ../../content/applications/marketing/surveys/create.rst:277 +msgid "Those buttons are the following:" +msgstr "" + +#: ../../content/applications/marketing/surveys/create.rst:279 +msgid ":guilabel:`Share`: click to reveal a :guilabel:`Share a Survey` pop-up form that can be used to invite potential participants to the survey — complete with a :guilabel:`Survey Link` that can be copied and sent to potential participants, and a :guilabel:`Send by Email` toggle switch." +msgstr "" + +#: ../../content/applications/marketing/surveys/create.rst:-1 +msgid "The 'Share a Survey' pop-up window that appears in the Odoo Surveys application." +msgstr "" + +#: ../../content/applications/marketing/surveys/create.rst:287 +msgid "When the :guilabel:`Send by Email` toggle is in the 'on' position, indicated by a green switch, additional fields appear, in which :guilabel:`Recipients` and a :guilabel:`Subject` can be added to the email. Below that, a dynamic email template, complete with a :guilabel:`Start Certification` button appears, which can also be modified." +msgstr "" + +#: ../../content/applications/marketing/surveys/create.rst:298 +msgid ":guilabel:`See results`: this button **only** appears if there has been at least one participant who has completed the survey. Clicking :guilabel:`See results` reveals a separate tab containing a visual analysis of the survey questions and responses. For more information, check out the :doc:`scoring surveys ` documentation." +msgstr "" + +#: ../../content/applications/marketing/surveys/create.rst:302 +msgid ":guilabel:`Create Live Session`: clicking this button opens the *Session Manager* in a separate tab. It also allows participants to access the live session, but the actual survey does **not** begin until the user hosting the live session survey clicks the :guilabel:`Start` button on the *Session Manager* window." +msgstr "" + +#: ../../content/applications/marketing/surveys/create.rst:307 +msgid "Additionally, when :guilabel:`Create Live Session` has been clicked, and the *Session Manager* tab has been opened, the :guilabel:`Create Live Session` button on the survey form is replaced with two new buttons: :guilabel:`Open Session Manager` and :guilabel:`Close Live Session`." +msgstr "" + +#: ../../content/applications/marketing/surveys/create.rst:311 +msgid "Clicking :guilabel:`Open Session Manager` opens another separate tab to the *Session Manager*, and clicking :guilabel:`Close Live Session` closes, and subsequently ends, the live session." +msgstr "" + +#: ../../content/applications/marketing/surveys/create.rst:313 +msgid ":guilabel:`Test`: clicking this button opens a new tab to a test version of the survey, in order for the user to check for errors or inconsistencies, from the point-of-view of a participant. Users can tell if they are in a test version of the survey if there is a blue banner at the top of the screen, reading: `This is a Test Survey --> Edit Survey`." +msgstr "" + +#: ../../content/applications/marketing/surveys/create.rst:318 +msgid "If the link in the blue banner is clicked, Odoo returns the user to the survey form." +msgstr "" + +#: ../../content/applications/marketing/surveys/create.rst:319 +msgid ":guilabel:`Print`: clicking this button opens a new tab to a printable version of the survey that the user can proceed to print for their records." +msgstr "" + +#: ../../content/applications/marketing/surveys/create.rst:321 +msgid ":guilabel:`Close`: clicking this button closes the survey (i.e. archives it), which is represented by a red :guilabel:`Archived` banner across the top-right corner of the survey form." +msgstr "" + +#: ../../content/applications/marketing/surveys/create.rst:324 +msgid "When this button is clicked, and the survey is closed, a single button appears in the upper-right corner of the survey form, titled: :guilabel:`Reopen`. When :guilabel:`Reopen` is clicked the survey is reopened (i.e. unarchived), and the :guilabel:`Archived` banner is removed from the survey form." +msgstr "" + +#: ../../content/applications/marketing/surveys/create.rst:330 +#: ../../content/applications/marketing/surveys/live_session.rst:220 #: ../../content/applications/marketing/surveys/scoring.rst:56 msgid ":doc:`time_random`" msgstr "" -#: ../../content/applications/marketing/surveys/create.rst:147 -msgid "Scoring" +#: ../../content/applications/marketing/surveys/live_session.rst:3 +msgid "Live Session surveys" msgstr "" -#: ../../content/applications/marketing/surveys/create.rst:149 -msgid "The following options are available when deciding how a :guilabel:`Scoring` method:" +#: ../../content/applications/marketing/surveys/live_session.rst:5 +msgid "With the Odoo *Surveys* application, users can enhance in-person demonstrations and presentations with the *Live Session* feature." msgstr "" -#: ../../content/applications/marketing/surveys/create.rst:151 -msgid ":guilabel:`No scoring`" +#: ../../content/applications/marketing/surveys/live_session.rst:8 +msgid "*Live Session* surveys function the same way as a normal survey, but with a host or moderator, who presents the questions to participants, reveals their responses in real-time, and controls the tempo of the survey." msgstr "" -#: ../../content/applications/marketing/surveys/create.rst:152 -msgid ":guilabel:`Scoring with answers at the end`" +#: ../../content/applications/marketing/surveys/live_session.rst:12 +msgid "In *Live Session* surveys, participants access the survey experience via a custom URL, and sign in with an optional access code. When the survey has begun, the host presents one question at a time." msgstr "" -#: ../../content/applications/marketing/surveys/create.rst:153 -msgid ":guilabel:`Scoring without answers at the end`" +#: ../../content/applications/marketing/surveys/live_session.rst:15 +msgid "Then, the audience of participants submit their answer, either via their computer or mobile device, and once the responses have been gathered, the host reveals all the participant's responses, in real time, with each answer's results displayed as a bar graph." msgstr "" -#: ../../content/applications/marketing/surveys/create.rst:155 -msgid "If either the :guilabel:`Scoring with answers at the end` or :guilabel:`Scoring without answers at the end` options are selected, a :guilabel:`Success %` field appears. Set the percentage of correct answers needed to pass the survey." +#: ../../content/applications/marketing/surveys/live_session.rst:-1 +msgid "Rendered concept of how a Live Session question and answer result appears in Odoo Surveys." msgstr "" -#: ../../content/applications/marketing/surveys/create.rst:159 -msgid "Next, there is the option to make the survey a certification. To do so, check the box next to the option labeled :guilabel:`Is a Certification`, and two additional fields appear. Select a color theme in the :guilabel:`Certification Template` field and then choose an :guilabel:`Email Template`. When a participant passes the certification with the required score, an email from Odoo will automatically be sent to that person using the selected email template." +#: ../../content/applications/marketing/surveys/live_session.rst:24 +msgid "Create Live Session survey" msgstr "" -#: ../../content/applications/marketing/surveys/create.rst:165 -msgid "If the :guilabel:`Give Badge` feature is enabled and the :guilabel:`Certification Badge` is set, the survey participant also receives a badge upon passing the certification." +#: ../../content/applications/marketing/surveys/live_session.rst:26 +msgid "To create a *Live Session* survey, begin by opening the *Surveys* application. From the :guilabel:`Surveys` dashboard, click the :guilabel:`New` button to reveal a blank survey form." msgstr "" -#: ../../content/applications/marketing/surveys/create.rst:169 -#: ../../content/applications/marketing/surveys/time_random.rst:48 -msgid ":doc:`scoring`" +#: ../../content/applications/marketing/surveys/live_session.rst:29 +msgid "Any of the survey type options (:guilabel:`Survey`, :guilabel:`Live Session`, :guilabel:`Assessment`, or :guilabel:`Custom`), presented as radio buttons at the top of the survey, can be used to create a *Live Session*." msgstr "" -#: ../../content/applications/marketing/surveys/create.rst:172 -msgid "Candidates" +#: ../../content/applications/marketing/surveys/live_session.rst:33 +msgid "However, selecting the :guilabel:`Live Session` survey type radio button streamlines the process because Odoo auto-selects the optimal settings and options for a *Live Session* survey when that option is selected." msgstr "" -#: ../../content/applications/marketing/surveys/create.rst:174 -msgid "To determine access to the survey, the :guilabel:`Access Mode` has two options to choose between: :guilabel:`Anyone with the link` and :guilabel:`Invited people only`." +#: ../../content/applications/marketing/surveys/live_session.rst:38 +msgid "If the :guilabel:`Is a Certification` option is enabled in the :guilabel:`Options` tab, the survey **cannot** be used as a *Live Session* survey." msgstr "" -#: ../../content/applications/marketing/surveys/create.rst:177 -msgid "Below the :guilabel:`Appraisal Managers Only` checkbox is the :guilabel:`Login Required` option to require a login to participate in the survey. If this option is activated, an :guilabel:`Attempts Limit` field also populates, in which the number of survey attempts is defined for the participant." +#: ../../content/applications/marketing/surveys/live_session.rst:41 +msgid "With the desired survey radio button option selected, proceed to :doc:`create a survey <../surveys/create>` with :doc:`questions and sections <../surveys/time_random>`." msgstr "" -#: ../../content/applications/marketing/surveys/create.rst:182 -msgid "Live Session" +#: ../../content/applications/marketing/surveys/live_session.rst:44 +msgid "While creating questions for the *Live Session* survey, open the :guilabel:`Options` tab on the :guilabel:`Create Sections and Questions` pop-up form, in order to reveal the :guilabel:`Live Sessions` section, which only has one available feature: :guilabel:`Question Time Limit`." msgstr "" -#: ../../content/applications/marketing/surveys/create.rst:184 -msgid "The :guilabel:`Live Session` section is dedicated to users who are conducting surveys in real-time, wherein they directly engage with and collect answers from a live audience." +#: ../../content/applications/marketing/surveys/live_session.rst:48 +msgid "When the :guilabel:`Question Time Limit` option is enabled, a new field appears beside it, wherein the user **must** enter the desired amount of time (in seconds) the participant gets to answer the question." msgstr "" -#: ../../content/applications/marketing/surveys/create.rst:187 -msgid "Customize the :guilabel:`Session Code` here; this code is needed for participants to access the live session survey. Reward participants for quick answers by selecting the checkbox labeled :guilabel:`Reward quick answers`. By checking it, attendees will get more points if they answer quickly." +#: ../../content/applications/marketing/surveys/live_session.rst:-1 +msgid "The Live Session question time limit option for questions in the Odoo Surveys application." msgstr "" -#: ../../content/applications/marketing/surveys/create.rst:193 -msgid "Description tab" +#: ../../content/applications/marketing/surveys/live_session.rst:59 +msgid "After the questions have been created for the *Live Session* survey, open the :guilabel:`Options` tab of the survey form to further configure the survey." msgstr "" -#: ../../content/applications/marketing/surveys/create.rst:195 -msgid "Back on the main survey template page is the :guilabel:`Description` tab, where a custom description of the survey can be added. This is displayed beneath the title on the survey's homepage, which is on the front end of the website made through the Odoo :guilabel:`Website` app." +#: ../../content/applications/marketing/surveys/live_session.rst:62 +msgid "The :guilabel:`Options` tab is organized into four sections: :guilabel:`Questions`, :guilabel:`Time & Scoring`, :guilabel:`Participants`, and :guilabel:`Live Session`." msgstr "" -#: ../../content/applications/marketing/surveys/create.rst:200 -msgid "Test and share the survey" +#: ../../content/applications/marketing/surveys/live_session.rst:68 +msgid "Regardless of the option selected for the :guilabel:`Pagination` field, the *Live Session* survey *only* shows :guilabel:`One page per question`, and will default to that option when the :guilabel:`Create Live Session` button is clicked, and a *Live Session* survey officially begins." msgstr "" -#: ../../content/applications/marketing/surveys/create.rst:202 -msgid "Once the survey is created and saved, run a test to check for possible errors before finally sending it out to the participants by clicking :guilabel:`Test` in the upper left corner of the survey template page." +#: ../../content/applications/marketing/surveys/live_session.rst:73 +msgid "The :guilabel:`One page per question` option in the :guilabel:`Pagination` field is selected by default, and no other options appear in the :guilabel:`Questions` section, when the :guilabel:`Live Session` survey type radio button is selected." msgstr "" -#: ../../content/applications/marketing/surveys/create.rst:206 -msgid "When activated, Odoo redirects the page to a test version of the survey on the front end of the website. This page displays how the survey will look to participants. Proceed to run through the survey, like a normal participant, to check for errors." +#: ../../content/applications/marketing/surveys/live_session.rst:77 +msgid "The :guilabel:`Display Progress as` and :guilabel:`Question Selection` options are still viable and active options for *Live Session* surveys, if desired, but they are **not** required." msgstr "" -#: ../../content/applications/marketing/surveys/create.rst:210 -msgid "To return to the survey template form in the backend, simply click the :guilabel:`This is a test survey. Edit Survey` link in the blue banner along the top of the page. Once Odoo redirects the page to the survey template in the backend, make any further changes, as needed, before officially sending the survey out to participants." +#: ../../content/applications/marketing/surveys/live_session.rst:80 +msgid "However, the :guilabel:`Allow Roaming` feature is **not** available during *Live Session* surveys whatsoever, as the host/moderator controls the survey, and participants have no control over what question they see, or when they see it." msgstr "" -#: ../../content/applications/marketing/surveys/create.rst:215 -msgid "When the survey is ready to be shared with the audience, click the :guilabel:`Start Survey` button in the upper-left corner of the survey template form. Then, click :guilabel:`Share`." +#: ../../content/applications/marketing/surveys/live_session.rst:87 +msgid "The :guilabel:`Survey Time Limit` option is **not** applicable for *Live Session* surveys. This option does not even appear in the :guilabel:`Time & Scoring` section of the :guilabel:`Options` tab if the :guilabel:`Live Session` survey type radio button option is selected." msgstr "" -#: ../../content/applications/marketing/surveys/create.rst:218 -msgid "In the pop-up window, add the survey recipients in the :guilabel:`Recipients` field (for existing contacts in the Odoo database) or the :guilabel:`Additional emails` field (for contacts that do not want to be listed in the Odoo database). Finally, click :guilabel:`Send`." +#: ../../content/applications/marketing/surveys/live_session.rst:92 +msgid "While the :guilabel:`Survey Time Limit` option is not applicable for *Live Session* surveys, each question *can* be affixed with its own *Question Time Limit*, via the *Options* tab of the question pop-up form. Those question-specific time limits *do* work with *Live Session* surveys." msgstr "" -#: ../../content/applications/marketing/surveys/create.rst:222 -msgid "As answers are received, check them by clicking the :guilabel:`Answers` smart button on the survey template form, or the :guilabel:`See Results` button in the upper left corner. To end the survey, click the :guilabel:`Close` button on the survey template form." +#: ../../content/applications/marketing/surveys/live_session.rst:96 +msgid "If desired, any :guilabel:`Scoring` option, and subsequent :guilabel:`Required Score (%)` option are available to use with *Live Session* surveys." +msgstr "" + +#: ../../content/applications/marketing/surveys/live_session.rst:99 +msgid "However, if the :guilabel:`Is a Certification` option is enabled, the survey **cannot** be used as a *Live Session* survey. The :guilabel:`Is a Certification` option does **not** appear in the :guilabel:`Time & Scoring` section of the :guilabel:`Options` tab if the :guilabel:`Live Session` survey type radio button option is selected." +msgstr "" + +#: ../../content/applications/marketing/surveys/live_session.rst:107 +msgid "The :guilabel:`Access Mode` field is set to the :guilabel:`Anyone with the link` option when the survey is used as a *Live Session*. The :guilabel:`Anyone with the link` option **cannot** be modified if the :guilabel:`Live Session` survey type radio button option is selected." +msgstr "" + +#: ../../content/applications/marketing/surveys/live_session.rst:111 +msgid "The :guilabel:`Require Login` option is available for *Live Session* surveys. However, if the :guilabel:`Live Session` survey type radio button option is selected, the usual :guilabel:`Limit Attempts` field that appears when :guilabel:`Require Login` is enabled does **not** appear, as live session participants only get to attempt the survey once, as the host leads them through it." +msgstr "" + +#: ../../content/applications/marketing/surveys/live_session.rst:119 +msgid "The :guilabel:`Session Code` field allows users to create unique codes for participants to use, in order to gain access to the *Live Session* survey. This code can consist of any combination of letters, numbers, and/or symbols." +msgstr "" + +#: ../../content/applications/marketing/surveys/live_session.rst:123 +msgid "The :guilabel:`Session Code` field is **not** required, however, it is encouraged because it adds a level of exclusivity to the survey and, without a :guilabel:`Session Code`, the URL that appears in the following :guilabel:`Session Link` field becomes far more complex." +msgstr "" + +#: ../../content/applications/marketing/surveys/live_session.rst:128 +msgid "If a :guilabel:`Session Code` is **not** entered, participants can access the survey, via the :guilabel:`Session Link` without needing a host, and the fundamental elements of the *Live Session* are lost, as the survey is then just a normal questionnaire, without any real-time results." +msgstr "" + +#: ../../content/applications/marketing/surveys/live_session.rst:133 +msgid "With a :guilabel:`Session Code`, the URL in the non-modifiable :guilabel:`Session Link` field is simplified, and ends with the :guilabel:`Session Code`, preceded by `/s/`." +msgstr "" + +#: ../../content/applications/marketing/surveys/live_session.rst:137 +msgid "If `1212` has been entered as the :guilabel:`Session Code`, the URL in the :guilabel:`Session Link` field begins with the basic URL of the database (e.g. `sample-database.odoo.com`), followed by: `/s/1212`." +msgstr "" + +#: ../../content/applications/marketing/surveys/live_session.rst:141 +msgid "So, collectively, that sample :guilabel:`Session Link` would be: `sample-database.odoo.com/s/1212`." +msgstr "" + +#: ../../content/applications/marketing/surveys/live_session.rst:145 +msgid "If a user sends out the :guilabel:`Session Link` URL in its complete form - :guilabel:`Session Code` and all - participants would *not* need to enter in a code, as it would already be entered for them. That complete link places the participant in a virtual waiting room, where they simply need to wait for the host to officially start the *Live Session* survey." +msgstr "" + +#: ../../content/applications/marketing/surveys/live_session.rst:150 +msgid "If a user sends out the :guilabel:`Session Link` URL - *except* for the :guilabel:`Session Code` at the end (i.e. the entire URL *through* `.../s/`) - participants would be taken to a page, wherein they would need to enter the specific :guilabel:`Session Code` in order to access the *Live Session*." +msgstr "" + +#: ../../content/applications/marketing/surveys/live_session.rst:155 +msgid "If any :guilabel:`Scoring` option has been enabled, the opportunity to :guilabel:`Reward quick answers` is also available with *Live Session* surveys." +msgstr "" + +#: ../../content/applications/marketing/surveys/live_session.rst:159 +msgid "Start Live Session surveys" +msgstr "" + +#: ../../content/applications/marketing/surveys/live_session.rst:161 +msgid "Once all the questions and configurations are complete, users can click the :guilabel:`Create Live Session` button at the top of the survey form. Doing so opens a new browser tab to the *Session Manager*." +msgstr "" + +#: ../../content/applications/marketing/surveys/live_session.rst:165 +msgid "When the :guilabel:`Create Live Session` button has been clicked, and the *Live Session* has begun, a new :guilabel:`Open Session Manager` button appears on the survey form, which opens a new browser tab to the *Session Manager*. If the *Live Session* has already begun, that button leads the user to the question or section the *Live Session* is currently on." +msgstr "" + +#: ../../content/applications/marketing/surveys/live_session.rst:170 +msgid "Additionally, a :guilabel:`Close Live Session` button appears on the survey form. When that button is clicked, the *Live Session* survey closes." +msgstr "" + +#: ../../content/applications/marketing/surveys/live_session.rst:173 +msgid "The *Session Manager* is controlled by the host/moderator of the *Live Session* survey, and is typically shown on a projection or screen, so the participants can collectively view the questions and real-time responses, as the host/moderator guides them through the *Live Session*." +msgstr "" + +#: ../../content/applications/marketing/surveys/live_session.rst:178 +msgid "The participant can see and answer the questions from their computer or mobile device, but the results and real-time responses can **only** be seen on the *Session Manager*." +msgstr "" + +#: ../../content/applications/marketing/surveys/live_session.rst:181 +msgid "Initially, the *Session Manager* shows the title of the *Live Session* survey, the link needed to access it, and a :guilabel:`Waiting for attendees...` counter, which populates as participants enter the *Live Session* survey." +msgstr "" + +#: ../../content/applications/marketing/surveys/live_session.rst:185 +msgid "Once the desired amount of participants have entered the *Live Session* survey, the host/moderator can click the :guilabel:`Start` button on the right side of the *Session Manager* window to begin the *Live Session*." +msgstr "" + +#: ../../content/applications/marketing/surveys/live_session.rst:190 +msgid "If the survey begins with a section title on the survey form, that section title appears in the *Session Manager*, and the participant's view of the survey informs them to `Pay attention to the host screen until the next question`. This message appears whenever a section title appears during a *Live Session*." +msgstr "" + +#: ../../content/applications/marketing/surveys/live_session.rst:195 +msgid "When the first question appears on the survey, the *Session Manager* shows the question above an empty bar graph, showing the potential answer options on the x-axis. The participants see the question and selectable answer options on their computer or mobile device." +msgstr "" + +#: ../../content/applications/marketing/surveys/live_session.rst:199 +msgid "As participants submit their answers, a progress bar, in the upper-left corner of the *Session Manager*, fills in. This is how *Live Session* hosts/moderators know when every participant has submitted their responses." +msgstr "" + +#: ../../content/applications/marketing/surveys/live_session.rst:203 +msgid "Then, when the desired amount of participants have submitted their responses, the host/moderator clicks the :guilabel:`Show Results` button on the right side of the *Session Manager* to reveal the collective real-time responses on the bar graph." +msgstr "" + +#: ../../content/applications/marketing/surveys/live_session.rst:207 +msgid "Once the host/moderator feels like the participants have had enough time to view the real-time results, via the populated bar graph, they can click the :guilabel:`Show Correct Answer(s)` button on the right side of the *Session Manager* window. Doing so highlights the correct response, if one has been designated, in green. All incorrect responses are highlighted in red." +msgstr "" + +#: ../../content/applications/marketing/surveys/live_session.rst:212 +msgid "When the host/moderator feels the participants have had enough time to take in the correct and incorrect responses, via the bar graph on the *Session Manager*, they can click the :guilabel:`Next` button to move on to the next portion of the survey." +msgstr "" + +#: ../../content/applications/marketing/surveys/live_session.rst:216 +msgid "Repeat this process until the survey is complete." msgstr "" #: ../../content/applications/marketing/surveys/scoring.rst:3 @@ -4507,49 +6379,351 @@ msgid "Example of how a badge looks on the eLearning portion of the website." msgstr "" #: ../../content/applications/marketing/surveys/time_random.rst:3 -msgid "Timed and randomized questions" +#: ../../content/applications/marketing/surveys/time_random.rst:64 +msgid "Create questions" msgstr "" #: ../../content/applications/marketing/surveys/time_random.rst:5 -msgid "When creating a survey in Odoo, there are options to set a time limit on the survey and randomize the questions." +msgid "In Odoo *Surveys*, crafting and tailoring survey questions is crucial for :doc:`creating and customizing surveys <../surveys/create>`." msgstr "" -#: ../../content/applications/marketing/surveys/time_random.rst:9 -msgid "Time limit" +#: ../../content/applications/marketing/surveys/time_random.rst:8 +msgid "Fortunately, Odoo provides numerous ways to configure tailored questions for any kind of survey." msgstr "" -#: ../../content/applications/marketing/surveys/time_random.rst:11 -msgid "During a timed survey, participants must finish the survey within a specified period of time. A common use case for implementing a time limit is that it greatly reduces the chance of participants looking up responses via external resources (e.g. web search), and reduces the survey to a \"closed book\" testing environment." +#: ../../content/applications/marketing/surveys/time_random.rst:10 +msgid "To access a list of *all* the questions that have been created in the database, navigate to :menuselection:`Surveys app --> Questions & Answers --> Questions`. There, users can view and modify any question from any survey." msgstr "" -#: ../../content/applications/marketing/surveys/time_random.rst:16 -msgid "Find the :guilabel:`Survey Time Limit` setting in the :guilabel:`Options` tab of the survey form, under the :guilabel:`Questions` section." +#: ../../content/applications/marketing/surveys/time_random.rst:14 +msgid "However, there is only one place in the Odoo *Surveys* application where survey questions can be created. To do that, navigate to a survey form, by going to :menuselection:`Surveys app --> New`, or by selecting any pre-existing survey from the :guilabel:`Surveys` page (:menuselection:`Surveys app --> Surveys`)." +msgstr "" + +#: ../../content/applications/marketing/surveys/time_random.rst:22 +msgid "On a survey form, users can view, access, add, and/or delete questions (and sections) in the :guilabel:`Questions` tab." +msgstr "" + +#: ../../content/applications/marketing/surveys/time_random.rst:32 +msgid "To reveal the :guilabel:`Mandatory Answer` column on the :guilabel:`Questions` tab, which indicates if questions require a mandatory answer or not, click the :guilabel:`(optional columns)` icon located to the far-right of the column titles." msgstr "" #: ../../content/applications/marketing/surveys/time_random.rst:-1 -msgid "Time limit field in the options tab of a survey template form." +msgid "The slider drop-down menu showing the Mandatory Answer option in Odoo Surveys." msgstr "" -#: ../../content/applications/marketing/surveys/time_random.rst:23 -msgid "When the :guilabel:`Survey Time Limit` option is checked, a timer will be displayed on every page of the survey, letting participants keep track of the time remaining while the survey is active." +#: ../../content/applications/marketing/surveys/time_random.rst:41 +msgid "Create sections" msgstr "" -#: ../../content/applications/marketing/surveys/time_random.rst:27 -msgid "Participants that do not submit their survey by the preconfigured time limit will *not* have their answers saved." +#: ../../content/applications/marketing/surveys/time_random.rst:50 +msgid "Then, drag-and-drop desired questions beneath a section, or drag-and-drop a section title on top of (i.e. *before*) the desired question(s) in the survey, in order to populate the section with specific questions that fit the theme of the section." msgstr "" -#: ../../content/applications/marketing/surveys/time_random.rst:31 -msgid "Randomized selection" +#: ../../content/applications/marketing/surveys/time_random.rst:66 +msgid "To create questions for the survey, click :guilabel:`Add a question` in the :guilabel:`Questions` tab." msgstr "" -#: ../../content/applications/marketing/surveys/time_random.rst:33 -msgid "When a survey is randomized, Odoo shuffles the questions and reveals them in a random order every time a participant begins the questionnaire. Using randomization as a survey method discourages participants from looking at each other's responses, and helps control for individual testing." +#: ../../content/applications/marketing/surveys/time_random.rst:69 +msgid "Clicking :guilabel:`Add a question` opens the :guilabel:`Create Sections and Questions` pop-up window, in which a survey question can be created." msgstr "" -#: ../../content/applications/marketing/surveys/time_random.rst:37 -msgid "To randomize a survey, click the :guilabel:`Options` tab on the survey form. In the :guilabel:`Questions` section, select :guilabel:`Randomized per section` for the :guilabel:`Selection` field. After enabling, navigate to the :guilabel:`Questions` tab and look in the :guilabel:`Random questions count` column. From there, determine how many questions (per section) Odoo should select and display during the shuffling of questions." +#: ../../content/applications/marketing/surveys/time_random.rst:77 +msgid "When all desired configurations are complete click either :guilabel:`Save & Close` to save the question and return to the survey form, or :guilabel:`Save & New` to save the question and create a new one right away in a fresh :guilabel:`Create Sections and Questions` pop-up window." +msgstr "" + +#: ../../content/applications/marketing/surveys/time_random.rst:81 +msgid "Click :guilabel:`Discard` to discard the question entirely." +msgstr "" + +#: ../../content/applications/marketing/surveys/time_random.rst:84 +msgid "Create Sections and Questions pop-up window" msgstr "" #: ../../content/applications/marketing/surveys/time_random.rst:-1 -msgid "Randomized question count in the questions tab of a survey." +msgid "The Create Sections and Questions pop-up form in Odoo Surveys." +msgstr "" + +#: ../../content/applications/marketing/surveys/time_random.rst:90 +msgid "In the :guilabel:`Create Sections and Questions` pop-up window, start by typing the question into the :guilabel:`Question` field, located at the top of the pop-up window." +msgstr "" + +#: ../../content/applications/marketing/surveys/time_random.rst:93 +msgid "Then, choose the desired :guilabel:`Question Type`. A preview of each :guilabel:`Question Type` is to the right of the :guilabel:`Question Type` field, when a :guilabel:`Question Type` is selected." +msgstr "" + +#: ../../content/applications/marketing/surveys/time_random.rst:96 +msgid "Choose from the following :guilabel:`Question Types`:" +msgstr "" + +#: ../../content/applications/marketing/surveys/time_random.rst:98 +msgid ":guilabel:`Multiple choice: only one answer`: a multiple choice question, where only one answer is permitted." +msgstr "" + +#: ../../content/applications/marketing/surveys/time_random.rst:100 +msgid ":guilabel:`Multiple choice: multiple answers allowed`: a multiple choice question, where more than answer is permitted." +msgstr "" + +#: ../../content/applications/marketing/surveys/time_random.rst:102 +msgid ":guilabel:`Multiple Lines Text Box`: an open-ended question, where participants can type in a multiple line response." +msgstr "" + +#: ../../content/applications/marketing/surveys/time_random.rst:104 +msgid ":guilabel:`Single Line Text Box`: an open-ended question, where participants can type in a single line response." +msgstr "" + +#: ../../content/applications/marketing/surveys/time_random.rst:106 +msgid ":guilabel:`Numerical Value`: a number-based question, where participants must enter a number as a response." +msgstr "" + +#: ../../content/applications/marketing/surveys/time_random.rst:108 +msgid ":guilabel:`Date`: a date-based question, where participants must enter a date (year-month-day) as a response." +msgstr "" + +#: ../../content/applications/marketing/surveys/time_random.rst:110 +msgid ":guilabel:`Datetime`: a date-based question, where participants must enter a date *and* time (year-month-day, hour-minute-second) as a response." +msgstr "" + +#: ../../content/applications/marketing/surveys/time_random.rst:112 +msgid ":guilabel:`Matrix`: a multiple-choice, multiple question, in a table/chart layout, where participants are presented with different questions on each row, and different answer options on each column." +msgstr "" + +#: ../../content/applications/marketing/surveys/time_random.rst:117 +msgid "Different features appear in the :guilabel:`Answers` and :guilabel:`Options` tabs, depending on the chosen :guilabel:`Question Type`." +msgstr "" + +#: ../../content/applications/marketing/surveys/time_random.rst:120 +msgid "However, the :guilabel:`Description` tab **always** remains the same, regardless of the question type chosen." +msgstr "" + +#: ../../content/applications/marketing/surveys/time_random.rst:123 +msgid "Once a :guilabel:`Question Type` has been selected, there are three possible tabs where information can be customized for the question. These include the :guilabel:`Answers` tab (if applicable for the chosen :guilabel:`Question Type`), the :guilabel:`Description` tab, and the :guilabel:`Options` tab." +msgstr "" + +#: ../../content/applications/marketing/surveys/time_random.rst:127 +msgid "Each tab offers a variety of different features, depending on what :guilabel:`Question Type` was chosen." +msgstr "" + +#: ../../content/applications/marketing/surveys/time_random.rst:131 +msgid "Answers tab" +msgstr "" + +#: ../../content/applications/marketing/surveys/time_random.rst:133 +msgid "The :guilabel:`Answers` tab **only** appears if the selected :guilabel:`Question Type` provides answer options to the participant." +msgstr "" + +#: ../../content/applications/marketing/surveys/time_random.rst:136 +msgid "However, if a custom response is required to answer the selected :guilabel:`Question Type`, like a :guilabel:`Multiple Lines Text Box`, for example. Or, if the answer to the :guilabel:`Question Type` is a number, date, or datetime, the :guilabel:`Answers` tab disappears completely." +msgstr "" + +#: ../../content/applications/marketing/surveys/time_random.rst:140 +msgid "If the :guilabel:`Single Line Text Box` is selected as the :guilabel:`Question Type`, the :guilabel:`Answers` tab remains, although it only provides two checkbox options: :guilabel:`Input must be an email` and :guilabel:`Save as user nickname`." +msgstr "" + +#: ../../content/applications/marketing/surveys/time_random.rst:-1 +msgid "The Single Line Text box question type answers tab in Odoo Surveys." +msgstr "" + +#: ../../content/applications/marketing/surveys/time_random.rst:148 +msgid "If the :guilabel:`Input must be an email` option is enabled, a new field, :guilabel:`Save as user email` appears. If that box is ticked, Odoo saves the participant's answer to that specific question as their email address." +msgstr "" + +#: ../../content/applications/marketing/surveys/time_random.rst:152 +msgid "If the :guilabel:`Save as user nickname` option is enabled, Odoo saves the participant's answer as its nickname." +msgstr "" + +#: ../../content/applications/marketing/surveys/time_random.rst:155 +msgid "For all other applicable :guilabel:`Question Type` options that provide answer options to the participant, the :guilabel:`Answers` tab appears the same." +msgstr "" + +#: ../../content/applications/marketing/surveys/time_random.rst:-1 +msgid "The answer tab with a multiple choice answer option selected in Odoo Surveys." +msgstr "" + +#: ../../content/applications/marketing/surveys/time_random.rst:162 +msgid "From here, users can add answer options by clicking :guilabel:`Add a line`, and typing in the various answer options for that question. Then, either press :kbd:`Enter` to lock in that answer option and immediately add another one. Or, click away to simply lock in that answer option." +msgstr "" + +#: ../../content/applications/marketing/surveys/time_random.rst:166 +msgid "The entered answer options appear in the :guilabel:`Choices` column of the :guilabel:`Answers` tab." +msgstr "" + +#: ../../content/applications/marketing/surveys/time_random.rst:168 +msgid "If any *Scoring* option is enabled in the :guilabel:`Options` tab of the survey form, the :guilabel:`Correct` and :guilabel:`Score` columns appear to the right of the :guilabel:`Choices` column." +msgstr "" + +#: ../../content/applications/marketing/surveys/time_random.rst:172 +msgid "To mark an answer option as correct, tick the box beneath the :guilabel:`Correct` column for the respective question. If :guilabel:`Multiple choice: multiple answers allowed` is set as the :guilabel:`Question Type`, multiple answers in the :guilabel:`Choices` column can be marked as :guilabel:`Correct`." +msgstr "" + +#: ../../content/applications/marketing/surveys/time_random.rst:177 +msgid "In the :guilabel:`Score` column, designate how many points (if any) should be rewarded to the participant for entering that specific answer. It is possible to enter a negative amount as the :guilabel:`Score` to take points away for an incorrect response." +msgstr "" + +#: ../../content/applications/marketing/surveys/time_random.rst:181 +msgid "The option to upload a corresponding image to accompany the answer options is available on the question line, beneath the :guilabel:`Image` column, by clicking :guilabel:`Upload your file`, and uploading the desired image." +msgstr "" + +#: ../../content/applications/marketing/surveys/time_random.rst:185 +msgid "To delete any answer option, click the :guilabel:`🗑️ (trash can)` icon to the far-right of the question line." +msgstr "" + +#: ../../content/applications/marketing/surveys/time_random.rst:188 +msgid "An exception to that is if the :guilabel:`Matrix` option is selected as the :guilabel:`Question Type`. If that's chosen, the :guilabel:`Answers` tab remains, but below the typical :guilabel:`Choices` section, there is a :guilabel:`Rows` section. That's because the :guilabel:`Matrix` option provides an answer table for participants to fill out." +msgstr "" + +#: ../../content/applications/marketing/surveys/time_random.rst:-1 +msgid "The answer tab with a matrix question type selected in Odoo Surveys." +msgstr "" + +#: ../../content/applications/marketing/surveys/time_random.rst:200 +msgid "In the :guilabel:`Description` tab of the :guilabel:`Create Sections and Questions` pop-up window is used to provide any kind of guidelines, instructions, or any other type of supplemental material deemed necessary to help participants answer/understand the question." +msgstr "" + +#: ../../content/applications/marketing/surveys/time_random.rst:204 +msgid "Entering a description is **not** required." +msgstr "" + +#: ../../content/applications/marketing/surveys/time_random.rst:209 +msgid "In the :guilabel:`Options` tab of the :guilabel:`Create Sections and Questions` pop-up window, there are four available sections: :guilabel:`Answers`, :guilabel:`Constraints`, :guilabel:`Conditional Display`, and :guilabel:`Live Sessions`." +msgstr "" + +#: ../../content/applications/marketing/surveys/time_random.rst:214 +msgid "Answers section" +msgstr "" + +#: ../../content/applications/marketing/surveys/time_random.rst:217 +msgid "Fields in the :guilabel:`Answers` section in the :guilabel:`Options` tab of the :guilabel:`Create Sections and Questions` pop-up window vary, depending on the selected :guilabel:`Question Type` and overall :guilabel:`Options` configured on the survey form." +msgstr "" + +#: ../../content/applications/marketing/surveys/time_random.rst:222 +msgid "Multiple Choice question types" +msgstr "" + +#: ../../content/applications/marketing/surveys/time_random.rst:224 +msgid "If the selected :guilabel:`Question Type` is either :guilabel:`Multiple choice: only one answer` or :guilabel:`Multiple choice: multiple answers allowed`, there is a :guilabel:`Show Comments Field` present in the :guilabel:`Answers` section." +msgstr "" + +#: ../../content/applications/marketing/surveys/time_random.rst:228 +msgid "When enabled, two additional fields appear: :guilabel:`Comment Message` and :guilabel:`Comment is an answer`." +msgstr "" + +#: ../../content/applications/marketing/surveys/time_random.rst:-1 +msgid "The answers section of the options tab when a multiple choice question type is selected." +msgstr "" + +#: ../../content/applications/marketing/surveys/time_random.rst:235 +msgid "In the :guilabel:`Comment Message` field, type in a guiding message to help participants know what is expected of them (e.g. `If other, please specify`)." +msgstr "" + +#: ../../content/applications/marketing/surveys/time_random.rst:238 +msgid "If the :guilabel:`Comment is an answer` option is enabled, Odoo takes the participant's commented response as an answer, and not just commentary on the question. This is best utilized in surveys where there is no scoring option enabled." +msgstr "" + +#: ../../content/applications/marketing/surveys/time_random.rst:243 +msgid "Multiple Lines Text Box question type" +msgstr "" + +#: ../../content/applications/marketing/surveys/time_random.rst:245 +msgid "If the selected :guilabel:`Question Type` is :guilabel:`Multiple Lines Text Box`, a :guilabel:`Placeholder` field appears in the :guilabel:`Answers` section of the :guilabel:`Options` tab." +msgstr "" + +#: ../../content/applications/marketing/surveys/time_random.rst:-1 +msgid "The placeholder field when a multiple lines text box option is chosen in Odoo Surveys." +msgstr "" + +#: ../../content/applications/marketing/surveys/time_random.rst:253 +#: ../../content/applications/marketing/surveys/time_random.rst:276 +msgid "In the :guilabel:`Placeholder` field, enter a guiding direction to help participants know what they should write in the :guilabel:`Multiple Lines Text Box` presented to them." +msgstr "" + +#: ../../content/applications/marketing/surveys/time_random.rst:257 +msgid "Single Line Text Box, Numerical Value, Date, Datetime question types" +msgstr "" + +#: ../../content/applications/marketing/surveys/time_random.rst:259 +msgid "If the selected :guilabel:`Question Type` is :guilabel:`Single Line Text Box`, :guilabel:`Numerical Value`, :guilabel:`Date`, or :guilabel:`Datetime`, two options appear in the :guilabel:`Answers` section of the :guilabel:`Options` tab: :guilabel:`Validate Entry` and :guilabel:`Placeholder`." +msgstr "" + +#: ../../content/applications/marketing/surveys/time_random.rst:263 +msgid "If the :guilabel:`Validate Entry` option is enabled, two additional fields appear beneath: :guilabel:`Min/Max Limits` and :guilabel:`Validation Error`." +msgstr "" + +#: ../../content/applications/marketing/surveys/time_random.rst:-1 +msgid "The answers section of the option tab when a single line text box question type is chosen." +msgstr "" + +#: ../../content/applications/marketing/surveys/time_random.rst:270 +msgid "In the :guilabel:`Min/Max Limits` field, designate the minimum and maximum allowed quantities for that specific question." +msgstr "" + +#: ../../content/applications/marketing/surveys/time_random.rst:273 +msgid "In the :guilabel:`Validation Error` field, enter a custom message that Odoo displays when an answer is not valid." +msgstr "" + +#: ../../content/applications/marketing/surveys/time_random.rst:280 +msgid "Constraints section" +msgstr "" + +#: ../../content/applications/marketing/surveys/time_random.rst:282 +msgid "The :guilabel:`Constraints` section in the :guilabel:`Options` tab is the same, regardless of the selected :guilabel:`Question Type`." +msgstr "" + +#: ../../content/applications/marketing/surveys/time_random.rst:-1 +msgid "The Constraints section in the options tab in Odoo Surveys." +msgstr "" + +#: ../../content/applications/marketing/surveys/time_random.rst:289 +msgid "In the :guilabel:`Constraints` section, there is one option available: :guilabel:`Mandatory Answer`." +msgstr "" + +#: ../../content/applications/marketing/surveys/time_random.rst:291 +msgid "When :guilabel:`Mandatory Answer` is enabled, that means that specific question requires an answer from the participant before they can move on. Also, when :guilabel:`Mandatory Answer` is enabled, that reveals an additional field: :guilabel:`Error Message`." +msgstr "" + +#: ../../content/applications/marketing/surveys/time_random.rst:295 +msgid "In the :guilabel:`Error Message` field, enter a custom error message prompting the participant to provide an answer for this question." +msgstr "" + +#: ../../content/applications/marketing/surveys/time_random.rst:299 +msgid "Conditional Display section" +msgstr "" + +#: ../../content/applications/marketing/surveys/time_random.rst:301 +msgid ":guilabel:`Conditional Display` means the question is **only** displayed if a specified conditional answer(s) (i.e. :guilabel:`Triggering Answers`) has been selected in a previous question(s)." +msgstr "" + +#: ../../content/applications/marketing/surveys/time_random.rst:305 +msgid "The :guilabel:`Conditional Display` section of the :guilabel:`Options` tab is **not** available when questions are randomly picked." +msgstr "" + +#: ../../content/applications/marketing/surveys/time_random.rst:308 +msgid "There is only one field in the :guilabel:`Conditional Display` section: :guilabel:`Triggering Answers`." +msgstr "" + +#: ../../content/applications/marketing/surveys/time_random.rst:-1 +msgid "The Conditional Display section of the options tab in the Odoo Surveys application." +msgstr "" + +#: ../../content/applications/marketing/surveys/time_random.rst:315 +msgid "In the :guilabel:`Triggering Answers` field, select specific responses from previous questions that would trigger this question. More than one answer can be selected. Leave the field empty if the question should always be displayed." +msgstr "" + +#: ../../content/applications/marketing/surveys/time_random.rst:320 +msgid "Live Sessions section" +msgstr "" + +#: ../../content/applications/marketing/surveys/time_random.rst:322 +msgid "The option in the :guilabel:`Live Sessions` section of the :guilabel:`Options` tab are **only** supported by *Live Session* surveys." +msgstr "" + +#: ../../content/applications/marketing/surveys/time_random.rst:325 +msgid "There is only one option available in the :guilabel:`Live Sessions` section: :guilabel:`Question Time Limit`." +msgstr "" + +#: ../../content/applications/marketing/surveys/time_random.rst:-1 +msgid "The Live Sessions section of the Option tab in the Odoo Surveys application." +msgstr "" + +#: ../../content/applications/marketing/surveys/time_random.rst:332 +msgid "When the :guilabel:`Question Time Limit` option is enabled, designate how much time (in :guilabel:`seconds`) participants have to answer the question during a *Live Session* survey." msgstr "" diff --git a/locale/sources/productivity.pot b/locale/sources/productivity.pot index 97239bab1..d0dbd97bb 100644 --- a/locale/sources/productivity.pot +++ b/locale/sources/productivity.pot @@ -8,7 +8,7 @@ msgid "" msgstr "" "Project-Id-Version: Odoo 17.0\n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2024-03-25 16:01+0000\n" +"POT-Creation-Date: 2024-04-30 09:16+0000\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME \n" "Language-Team: LANGUAGE \n" @@ -217,7 +217,152 @@ msgid "Removing a contact from an event causes Google to send a cancellation to msgstr "" #: ../../content/applications/productivity/calendar/google.rst:154 -msgid "Events can be created in Google Calendar without sending a notification by selecting :guilabel:`Don't Send` when prompted to send invitation emails." +msgid "Events can be created in *Google Calendar* without sending a notification by selecting :guilabel:`Don't Send` when prompted to send invitation emails." +msgstr "" + +#: ../../content/applications/productivity/calendar/google.rst:158 +#: ../../content/applications/productivity/calendar/outlook.rst:211 +msgid "Troubleshoot sync" +msgstr "" + +#: ../../content/applications/productivity/calendar/google.rst:160 +msgid "There may be times when the *Google Calendar* account does not sync correctly with Odoo. Sync issues can be seen in the database logs." +msgstr "" + +#: ../../content/applications/productivity/calendar/google.rst:163 +msgid "In these cases, the account needs troubleshooting. A reset can be performed using the :guilabel:`Reset Account` button, which can be accessed by navigating to :menuselection:`Settings app --> Manage Users`. Then, select the user to modify the calendar, and click the :guilabel:`Calendar` tab." +msgstr "" + +#: ../../content/applications/productivity/calendar/google.rst:-1 +#: ../../content/applications/productivity/calendar/outlook.rst:-1 +msgid "Reset buttons highlighted on the calendar tab of the user." +msgstr "" + +#: ../../content/applications/productivity/calendar/google.rst:172 +#: ../../content/applications/productivity/calendar/outlook.rst:225 +msgid "Next, click :guilabel:`Reset Account` under the correct calendar." +msgstr "" + +#: ../../content/applications/productivity/calendar/google.rst:175 +#: ../../content/applications/productivity/calendar/outlook.rst:228 +msgid "Reset options" +msgstr "" + +#: ../../content/applications/productivity/calendar/google.rst:177 +msgid "The following reset options are available for troubleshooting Google calendar sync with Odoo:" +msgstr "" + +#: ../../content/applications/productivity/calendar/google.rst:-1 +msgid "Google calendar reset options in Odoo." +msgstr "" + +#: ../../content/applications/productivity/calendar/google.rst:183 +#: ../../content/applications/productivity/calendar/outlook.rst:237 +msgid ":guilabel:`User's Existing Events`:" +msgstr "" + +#: ../../content/applications/productivity/calendar/google.rst:185 +#: ../../content/applications/productivity/calendar/outlook.rst:239 +msgid ":guilabel:`Leave them untouched`: no changes to the events." +msgstr "" + +#: ../../content/applications/productivity/calendar/google.rst:186 +msgid ":guilabel:`Delete from the current Google Calendar account`: delete the events from *Google Calendar*." +msgstr "" + +#: ../../content/applications/productivity/calendar/google.rst:188 +#: ../../content/applications/productivity/calendar/outlook.rst:242 +msgid ":guilabel:`Delete from Odoo`: delete the events from the Odoo calendar." +msgstr "" + +#: ../../content/applications/productivity/calendar/google.rst:189 +msgid ":guilabel:`Delete from both`: delete the events from both *Google Calendar* and Odoo calendar." +msgstr "" + +#: ../../content/applications/productivity/calendar/google.rst:191 +#: ../../content/applications/productivity/calendar/outlook.rst:246 +msgid ":guilabel:`Next Synchronization`:" +msgstr "" + +#: ../../content/applications/productivity/calendar/google.rst:193 +msgid ":guilabel:`Synchronize only new events`: sync new events on *Google Calendar* and/or Odoo calendar." +msgstr "" + +#: ../../content/applications/productivity/calendar/google.rst:195 +msgid ":guilabel:`Synchronize all existing events`: sync all events on *Google Calendar* and/or Odoo calendar." +msgstr "" + +#: ../../content/applications/productivity/calendar/google.rst:198 +#: ../../content/applications/productivity/calendar/outlook.rst:253 +msgid "Click :guilabel:`Confirm` after making the selection to modify the user's events and the calendar synchronization." +msgstr "" + +#: ../../content/applications/productivity/calendar/google.rst:202 +msgid "Google OAuth FAQ" +msgstr "" + +#: ../../content/applications/productivity/calendar/google.rst:204 +msgid "At times there can be misconfigurations that take place, and troubleshooting is needed to resolve the issue. Below are the most common errors that may occur when configuring the *Google Calendar* for use with Odoo." +msgstr "" + +#: ../../content/applications/productivity/calendar/google.rst:209 +msgid "Production vs. testing publishing status" +msgstr "" + +#: ../../content/applications/productivity/calendar/google.rst:211 +msgid "Choosing :guilabel:`Production` as the :guilabel:`Publishing Status` (instead of :guilabel:`Testing`) displays the following warning message:" +msgstr "" + +#: ../../content/applications/productivity/calendar/google.rst:214 +msgid "`OAuth is limited to 100 sensitive scope logins until the OAuth consent screen is verified. This may require a verification process that can take several days.`" +msgstr "" + +#: ../../content/applications/productivity/calendar/google.rst:217 +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/productivity/calendar/google.rst:222 +msgid "No test users added" +msgstr "" + +#: ../../content/applications/productivity/calendar/google.rst:224 +msgid "If no test users are added to the :guilabel:`OAuth consent screen`, then an :guilabel:`Error 403: access_denied` populates." +msgstr "" + +#: ../../content/applications/productivity/calendar/google.rst:-1 +msgid "403 Access Denied Error." +msgstr "" + +#: ../../content/applications/productivity/calendar/google.rst:231 +msgid "To correct this error, return to the :guilabel:`OAuth consent screen`, under :guilabel:`APIs & Services`, and add test users to the app. Add the email to be configured in Odoo." +msgstr "" + +#: ../../content/applications/productivity/calendar/google.rst:235 +msgid "Application Type" +msgstr "" + +#: ../../content/applications/productivity/calendar/google.rst:237 +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 (:guilabel:`Error 400:redirect_uri_mismatch`)." +msgstr "" + +#: ../../content/applications/productivity/calendar/google.rst:-1 +msgid "Error 400 Redirect URI Mismatch." +msgstr "" + +#: ../../content/applications/productivity/calendar/google.rst:245 +msgid "To correct this error, delete the existing credentials, and create new credentials, by selecting :guilabel:`Web Application` for the :guilabel:`Application Type`." +msgstr "" + +#: ../../content/applications/productivity/calendar/google.rst:248 +msgid "Then, under :guilabel:`Authorized redirect URIs`, click :guilabel:`ADD URI`, and type: `https://yourdbname.odoo.com/google_account/authentication` in the field, being sure to replace *yourdbname* in the URL with the **real** Odoo database name." +msgstr "" + +#: ../../content/applications/productivity/calendar/google.rst:253 +msgid "Ensure that the domain (used in the URI: `https://yourdbname.odoo.com/google_account/authentication`) is the exact same domain as configured in the `web.base.url` system parameter." +msgstr "" + +#: ../../content/applications/productivity/calendar/google.rst:257 +msgid "Access the `web.base.url` by activating :ref:`developer mode `, and navigating to :menuselection:`Settings app --> Technical header menu --> Parameters section --> System Parameters`." msgstr "" #: ../../content/applications/productivity/calendar/outlook.rst:3 @@ -225,169 +370,271 @@ msgid "Outlook Calendar synchronization" msgstr "" #: ../../content/applications/productivity/calendar/outlook.rst:5 -msgid "Synchronizing a user's Outlook Calendar with Odoo is useful for keeping track of their tasks and appointments across all related applications." +msgid "Synchronizing a user's *Outlook Calendar* with Odoo is useful for keeping track of tasks and appointments across all related applications." msgstr "" #: ../../content/applications/productivity/calendar/outlook.rst:9 -msgid ":doc:`/applications/general/users/azure`" +msgid ":doc:`../../general/users/azure`" msgstr "" #: ../../content/applications/productivity/calendar/outlook.rst:10 -msgid ":doc:`/applications/general/email_communication/azure_oauth`" +msgid ":doc:`../../general/email_communication/azure_oauth`" msgstr "" #: ../../content/applications/productivity/calendar/outlook.rst:13 -msgid "Register the application with Microsoft Azure" +msgid "Microsoft Azure setup" msgstr "" #: ../../content/applications/productivity/calendar/outlook.rst:15 -msgid "To sync the Outlook Calendar with Odoo's Calendar, a Microsoft Azure account is needed. Creating an account is free for users who have never tried or paid for Azure. For more information, `click here `_." +msgid "To sync the *Outlook Calendar* with Odoo's *Calendar*, a Microsoft *Azure* account is required. Creating an account is free for users who have never tried, or paid for, *Azure*. For more information, view the account options on the `Azure website `_." msgstr "" -#: ../../content/applications/productivity/calendar/outlook.rst:19 -msgid "Refer to `Microsoft's documentation `_ on how to set up an Microsoft Entra ID (formally called *Microsoft Azure Active Directory (Azure AD)*), which is a representation of an organization to manage and register apps." +#: ../../content/applications/productivity/calendar/outlook.rst:20 +msgid "Refer to `Microsoft's documentation `_ on how to set up a Microsoft *Entra ID* (formally called Microsoft *Azure Active Directory (Azure AD)*). This is an API console to manage and register Microsoft applications." msgstr "" -#: ../../content/applications/productivity/calendar/outlook.rst:24 -msgid "Then, `Register an Application `_, choosing the appropriate :guilabel:`Supported account type`. Users who wish to connect their Outlook calendar to Odoo should select the :guilabel:`Accounts in any organizational directory (Any Microsoft Entra ID directory - Multitenant) and personal Microsoft accounts (e.g. Skype, Xbox)` option for :guilabel:`Supported account types`." +#: ../../content/applications/productivity/calendar/outlook.rst:25 +msgid "Existing Microsoft *Entra ID* users should log in at the `Microsoft Azure developer portal `_. Next, select :guilabel:`View` under the section labeled :guilabel:`Manage Microsoft Entra ID`." msgstr "" #: ../../content/applications/productivity/calendar/outlook.rst:30 -msgid "When configuring the :guilabel:`Redirect URI`, choose :guilabel:`Web` and copy the Odoo database URI (URL) followed by `/microsoft_account/authentication`." +msgid "Register application" msgstr "" -#: ../../content/applications/productivity/calendar/outlook.rst:34 -msgid "Enter `https://www.companyname.odoo.com/microsoft_account/authentication` for the :guilabel:`Redirect URI`." +#: ../../content/applications/productivity/calendar/outlook.rst:32 +msgid "After logging in with the Microsoft *Entra ID*, `register an application `_." +msgstr "" + +#: ../../content/applications/productivity/calendar/outlook.rst:35 +msgid "To create an application, click :guilabel:`+ Add` in the top menu. From the resulting drop-down menu, select :guilabel:`App Registration`." +msgstr "" + +#: ../../content/applications/productivity/calendar/outlook.rst:-1 +msgid "Microsoft Azure management page with + Add and App Registration menu highlighted." +msgstr "" + +#: ../../content/applications/productivity/calendar/outlook.rst:42 +msgid "Enter a unique :guilabel:`Name` for the connected application." +msgstr "" + +#: ../../content/applications/productivity/calendar/outlook.rst:44 +msgid "Choosing the appropriate :guilabel:`Supported account type` is essential, or else the connected application will not work. Users who wish to connect their *Outlook Calendar* to Odoo should select the :guilabel:`Accounts in any organizational directory (Any Microsoft Entra ID directory - Multitenant) and personal Microsoft accounts (e.g. Skype, Xbox)` option for :guilabel:`Supported account types`." +msgstr "" + +#: ../../content/applications/productivity/calendar/outlook.rst:50 +msgid "When configuring the :guilabel:`Redirect URI`, choose the :guilabel:`Web` option from the first drop-down menu. Then, enter the Odoo database URI (URL) followed by `/microsoft_account/authentication`." +msgstr "" + +#: ../../content/applications/productivity/calendar/outlook.rst:55 +msgid "Enter `https://yourdbname.odoo.com/microsoft_account/authentication` for the :guilabel:`Redirect URI`. Replace `yourdbname.odoo.com` with the :abbr:`URL (Uniform Resource Locator)`." +msgstr "" + +#: ../../content/applications/productivity/calendar/outlook.rst:59 +msgid "Ensure the database's :abbr:`URL (Uniform Resource Locator)` (domain) used in the URI is the exact same domain as the one configured on the `web.base.url` system parameter." +msgstr "" + +#: ../../content/applications/productivity/calendar/outlook.rst:62 +msgid "Access the `web.base.url` by activating :ref:`developer mode `, and navigating to :menuselection:`Settings app --> Technical header menu --> Parameters section --> System Parameters`. Then, select it from the :guilabel:`Key` list on the :guilabel:`System Parameters` page." msgstr "" #: ../../content/applications/productivity/calendar/outlook.rst:-1 msgid "The \"Supported account type\" and \"Redirect URI\" settings in the Microsoft Entra ID portal." msgstr "" -#: ../../content/applications/productivity/calendar/outlook.rst:41 -msgid "For more information on the restrictions and limitations of URIs, `check this page `_." +#: ../../content/applications/productivity/calendar/outlook.rst:71 +msgid "For more information on the restrictions and limitations of URIs, check Microsoft's `Redirect URI (reply URL) restrictions and limitations `_ page." msgstr "" -#: ../../content/applications/productivity/calendar/outlook.rst:44 -msgid "Regarding the application credentials, the user *must* add a client secret, which allows Odoo to authenticate itself, requiring no interaction from the user's side. :guilabel:`Certificates` are optional." +#: ../../content/applications/productivity/calendar/outlook.rst:75 +msgid "Finally, on the application registration page, click :guilabel:`Register` button to complete the application registration. The :guilabel:`Application (client) ID` is produced. Copy this value, as it is needed later, in the :ref:`outlook_calendar/odoo_setup`." msgstr "" -#: ../../content/applications/productivity/calendar/outlook.rst:48 -msgid "To do add a client secret, click :guilabel:`Add a certificate or secret` and then click :guilabel:`New client secret`. Next, type a :guilabel:`Description` and select when the client secret :guilabel:`Expires`." +#: ../../content/applications/productivity/calendar/outlook.rst:-1 +msgid "Application client ID highlighted in the essentials section of the newly created\n" +"application." msgstr "" -#: ../../content/applications/productivity/calendar/outlook.rst:52 -msgid "Since resetting the synchronization can be tricky, Odoo recommends setting the maximum allowed expiration date for the client secret (24 months), so there is no need to re-synchronize soon. Finally, click :guilabel:`Add` to generate the client secret (:guilabel:`Secret ID`)." +#: ../../content/applications/productivity/calendar/outlook.rst:85 +msgid "Create client secret" msgstr "" -#: ../../content/applications/productivity/calendar/outlook.rst:57 +#: ../../content/applications/productivity/calendar/outlook.rst:87 +msgid "The second credential needed to complete the synchronization of the Microsoft *Outlook Calendar* is the *Client Secret*. The user **must** add a client secret, as this allows Odoo to authenticate itself, requiring no interaction from the user's side. *Certificates* are optional." +msgstr "" + +#: ../../content/applications/productivity/calendar/outlook.rst:91 +msgid "To add a client secret, click :menuselection:`Certificates & secrets` in the left menu. Then click :guilabel:`+ New client secret` to create the client secret." +msgstr "" + +#: ../../content/applications/productivity/calendar/outlook.rst:-1 +msgid "New client secret page with certificates and secrets menu and new client secret option\n" +"highlighted." +msgstr "" + +#: ../../content/applications/productivity/calendar/outlook.rst:99 +msgid "Next, type a :guilabel:`Description`, and select when the client secret :guilabel:`Expires`. Available options include: :guilabel:`90 days (3 months)`, :guilabel:`365 days (12 months)`, :guilabel:`545 days (18 months)`, :guilabel:`730 days (24 months)` or :guilabel:`Custom`. The :guilabel:`Custom` option allows the administrator to set a :guilabel:`Start` and :guilabel:`End` date." +msgstr "" + +#: ../../content/applications/productivity/calendar/outlook.rst:105 +msgid "Finally, click :guilabel:`Add` to :guilabel:`Add a client secret`." +msgstr "" + +#: ../../content/applications/productivity/calendar/outlook.rst:108 +msgid "Since resetting the synchronization can be tricky, Odoo recommends setting the maximum allowed expiration date for the client secret (24 months or custom), so there is no need to re-synchronize soon." +msgstr "" + +#: ../../content/applications/productivity/calendar/outlook.rst:112 +msgid "Copy the :guilabel:`Value` for use in the next section." +msgstr "" + +#: ../../content/applications/productivity/calendar/outlook.rst:115 +msgid "Client secret values cannot be viewed, except immediately after creation. Be sure to save the secret when created *before* leaving the page." +msgstr "" + +#: ../../content/applications/productivity/calendar/outlook.rst:121 msgid "Configuration in Odoo" msgstr "" -#: ../../content/applications/productivity/calendar/outlook.rst:59 -msgid "In the Odoo database, go to :menuselection:`Settings app --> Calendar` in the left menu and activate the :guilabel:`Outlook Calendar` setting." +#: ../../content/applications/productivity/calendar/outlook.rst:123 +msgid "In the Odoo database, go to :menuselection:`Settings app --> Integrations section`, and tick the checkbox beside the :guilabel:`Outlook Calendar` setting. Remember to click :guilabel:`Save` to implement the changes." msgstr "" #: ../../content/applications/productivity/calendar/outlook.rst:-1 msgid "The \"Outlook Calendar\" setting activated in Odoo." msgstr "" -#: ../../content/applications/productivity/calendar/outlook.rst:66 -msgid "From the Microsoft Azure portal, under the :guilabel:`Overview` section of the application, copy the :guilabel:`Application (Client) ID`, and paste it into the :guilabel:`Client ID` field in Odoo." +#: ../../content/applications/productivity/calendar/outlook.rst:131 +msgid "From the Microsoft *Azure* portal, under the :guilabel:`Overview` section of the application, copy the :guilabel:`Application (Client) ID`, if it has not already been copied, and paste it into the :guilabel:`Client ID` field in Odoo." msgstr "" #: ../../content/applications/productivity/calendar/outlook.rst:-1 msgid "The \"Client ID\" in the Microsoft Azure portal." msgstr "" -#: ../../content/applications/productivity/calendar/outlook.rst:73 -msgid "In the Microsoft Azure portal, under the :guilabel:`Certificates & secrets` section, copy the :guilabel:`Client Secret Value` and paste it into the :guilabel:`Client Secret` field in Odoo." +#: ../../content/applications/productivity/calendar/outlook.rst:139 +msgid "Copy the previously-acquired :guilabel:`Value` (Client Secret Value), and paste it into the :guilabel:`Client Secret` field in Odoo." msgstr "" #: ../../content/applications/productivity/calendar/outlook.rst:-1 msgid "The \"Client Secret\" token to be copied from Microsoft to Odoo." msgstr "" -#: ../../content/applications/productivity/calendar/outlook.rst:80 +#: ../../content/applications/productivity/calendar/outlook.rst:146 msgid "Finally, on the Odoo :menuselection:`Settings --> General Settings` page, click :guilabel:`Save`." msgstr "" -#: ../../content/applications/productivity/calendar/outlook.rst:85 +#: ../../content/applications/productivity/calendar/outlook.rst:151 msgid "Sync with Outlook" msgstr "" -#: ../../content/applications/productivity/calendar/outlook.rst:89 +#: ../../content/applications/productivity/calendar/outlook.rst:155 msgid "Odoo highly recommends testing the Outlook calendar synchronization on a test database and a test email address (that is not used for any other purpose) before attempting to sync the desired Outlook Calendar with the user's production database." msgstr "" -#: ../../content/applications/productivity/calendar/outlook.rst:93 +#: ../../content/applications/productivity/calendar/outlook.rst:159 msgid "If the user has any past, present, or future events on their Odoo calendar before syncing their Outlook calendar, Outlook will treat the events pulled from Odoo's calendar during the sync as new events, causing an email notification to be sent from Outlook to all the event attendees." msgstr "" -#: ../../content/applications/productivity/calendar/outlook.rst:97 +#: ../../content/applications/productivity/calendar/outlook.rst:163 msgid "To avoid unwanted emails being sent to all past, present, and future event attendees, the user must add the events from the Odoo calendar to the Outlook calendar before the first ever sync, delete the events from Odoo, and then start the sync." msgstr "" -#: ../../content/applications/productivity/calendar/outlook.rst:101 +#: ../../content/applications/productivity/calendar/outlook.rst:167 msgid "Even after synchronizing the Odoo Calendar with the Outlook calendar, Outlook will still send a notification to all event participants every time an event is edited (created, deleted, unarchived, or event date/time changed), with no exceptions. This is a limitation that cannot be fixed from Odoo's side." msgstr "" -#: ../../content/applications/productivity/calendar/outlook.rst:106 +#: ../../content/applications/productivity/calendar/outlook.rst:172 msgid "In summary, once a user synchronizes their Outlook calendar with the Odoo calendar:" msgstr "" -#: ../../content/applications/productivity/calendar/outlook.rst:108 +#: ../../content/applications/productivity/calendar/outlook.rst:174 msgid "Creating an event in Odoo causes Outlook to send an invitation to all event attendees." msgstr "" -#: ../../content/applications/productivity/calendar/outlook.rst:109 +#: ../../content/applications/productivity/calendar/outlook.rst:175 msgid "Deleting an event in Odoo causes Outlook to send a cancellation to all event attendees." msgstr "" -#: ../../content/applications/productivity/calendar/outlook.rst:110 +#: ../../content/applications/productivity/calendar/outlook.rst:176 msgid "Unarchiving an event in Odoo causes Outlook to send an invitation to all event attendees." msgstr "" -#: ../../content/applications/productivity/calendar/outlook.rst:111 +#: ../../content/applications/productivity/calendar/outlook.rst:177 msgid "Archiving an event in Odoo causes Outlook to send a cancellation to all event attendees." msgstr "" -#: ../../content/applications/productivity/calendar/outlook.rst:112 +#: ../../content/applications/productivity/calendar/outlook.rst:178 msgid "Adding a contact to an event causes Outlook to send an invitation to all event attendees." msgstr "" -#: ../../content/applications/productivity/calendar/outlook.rst:113 +#: ../../content/applications/productivity/calendar/outlook.rst:179 msgid "Removing a contact from an event causes Outlook to send a cancellation to all event attendees." msgstr "" -#: ../../content/applications/productivity/calendar/outlook.rst:116 +#: ../../content/applications/productivity/calendar/outlook.rst:182 msgid "Sync Odoo Calendar and Outlook" msgstr "" -#: ../../content/applications/productivity/calendar/outlook.rst:118 -msgid "In the Odoo database, go to the :guilabel:`Calendar` module and click the :guilabel:`Outlook` sync button. The page will redirect to a Microsoft login page, and the user is asked to log in to their account, if they are not already, and grant the required permissions." +#: ../../content/applications/productivity/calendar/outlook.rst:184 +msgid "In the Odoo database, open to the *Calendar* module, and click the :guilabel:`Outlook` sync button on the right-side of the page, beneath the monthly calendar." msgstr "" #: ../../content/applications/productivity/calendar/outlook.rst:-1 msgid "The \"Outlook\" sync button in Odoo Calendar." msgstr "" -#: ../../content/applications/productivity/calendar/outlook.rst:126 -msgid "The synchronization is a two-way process, meaning that events are reconciled in both accounts (Outlook and Odoo)." +#: ../../content/applications/productivity/calendar/outlook.rst:191 +msgid "The synchronization is a two-way process, meaning that events are reconciled in both accounts (*Outlook* and Odoo). The page redirects to a Microsoft login page, and the user is asked to log in to their account, if they are not already. Finally, grant the required permissions by clicking :guilabel:`Accept`." msgstr "" -#: ../../content/applications/productivity/calendar/outlook.rst:130 -msgid "All users that want to use the synchronization simply need to :ref:`sync their calendar with Outlook `. The configuration of Microsoft's Azure account is only done once, as Microsoft Entra ID tenants' Client IDs and Client Secrets are unique, and represent an organization that helps the user to manage a specific instance of Microsoft cloud services for their internal and external users." +#: ../../content/applications/productivity/calendar/outlook.rst:-1 +msgid "Authentication process on Microsoft Outlook OAuth page." msgstr "" -#: ../../content/applications/productivity/calendar/outlook.rst:137 -msgid ":doc:`/applications/general/integrations/mail_plugins/outlook`" +#: ../../content/applications/productivity/calendar/outlook.rst:201 +msgid "All users that want to use the synchronization simply need to :ref:`sync their calendar with Outlook `. The configuration of Microsoft's *Azure* account is only done once, as Microsoft *Entra ID* tenants' client IDs and client secrets are unique, and help the user manage a specific instance of Microsoft cloud services for internal and external users." msgstr "" -#: ../../content/applications/productivity/calendar/outlook.rst:138 +#: ../../content/applications/productivity/calendar/outlook.rst:207 +msgid ":doc:`../../general/integrations/mail_plugins/outlook`" +msgstr "" + +#: ../../content/applications/productivity/calendar/outlook.rst:208 msgid ":doc:`google`" msgstr "" +#: ../../content/applications/productivity/calendar/outlook.rst:213 +msgid "There may be times when the *Microsoft Outlook Calendar* account does not sync correctly with Odoo. Sync issues can be seen in the database logs." +msgstr "" + +#: ../../content/applications/productivity/calendar/outlook.rst:216 +msgid "In these cases, the account needs troubleshooting. A reset can be performed using the :guilabel:`Reset Account` button, which can be accessed by navigating to :menuselection:`Settings app --> Manage Users`. Then, select the user to modify the calendar, and click on the :guilabel:`Calendar` tab." +msgstr "" + +#: ../../content/applications/productivity/calendar/outlook.rst:230 +msgid "The following reset options are available for troubleshooting *Microsoft Outlook Calendar* sync with Odoo:" +msgstr "" + +#: ../../content/applications/productivity/calendar/outlook.rst:-1 +msgid "Outlook calendar reset options in Odoo." +msgstr "" + +#: ../../content/applications/productivity/calendar/outlook.rst:240 +msgid ":guilabel:`Delete from the current Microsoft Calendar account`: delete the events from *Microsoft Outlook Calendar*." +msgstr "" + +#: ../../content/applications/productivity/calendar/outlook.rst:243 +msgid ":guilabel:`Delete from both`: delete the events from both *Microsoft Outlook Calendar* and Odoo calendar." +msgstr "" + +#: ../../content/applications/productivity/calendar/outlook.rst:248 +msgid ":guilabel:`Synchronize only new events`: sync new events on *Microsoft Outlook Calendar* and/or Odoo calendar." +msgstr "" + +#: ../../content/applications/productivity/calendar/outlook.rst:250 +msgid ":guilabel:`Synchronize all existing events`: sync all events on *Microsoft Outlook Calendar* and/or Odoo calendar." +msgstr "" + #: ../../content/applications/productivity/discuss.rst:6 msgid "Discuss" msgstr "" @@ -511,6 +758,481 @@ msgstr "" msgid ":doc:`/applications/essentials/activities`" msgstr "" +#: ../../content/applications/productivity/discuss/chatter.rst:3 +msgid "Chatter" +msgstr "" + +#: ../../content/applications/productivity/discuss/chatter.rst:5 +msgid "The *Chatter* feature is integrated throughout Odoo to streamline communication, maintain traceability, and provide accountability among team members. Chatter windows, known as *composers*, are located on almost every record within the database, and allow users to communicate with both internal users and external contacts." +msgstr "" + +#: ../../content/applications/productivity/discuss/chatter.rst:10 +msgid "Chatter composers also enable users to log notes, upload files, and schedule activities." +msgstr "" + +#: ../../content/applications/productivity/discuss/chatter.rst:13 +msgid "Chatter thread" +msgstr "" + +#: ../../content/applications/productivity/discuss/chatter.rst:15 +msgid "A *chatter thread* can be found on most pages in the database, and serves as a record of the updates and edits made to a record. A note is logged in the chatter thread when a change is made. The note includes details of the change, and a time stamp." +msgstr "" + +#: ../../content/applications/productivity/discuss/chatter.rst:20 +msgid "A user, Mitchell Admin, needs to update the email address of a contact. After they save the changes to the contact record, a note is logged in the chatter of the contact record with the following information:" +msgstr "" + +#: ../../content/applications/productivity/discuss/chatter.rst:24 +msgid "The date when the change occurred." +msgstr "" + +#: ../../content/applications/productivity/discuss/chatter.rst:25 +msgid "The email address as it was previously listed." +msgstr "" + +#: ../../content/applications/productivity/discuss/chatter.rst:26 +msgid "The updated email address." +msgstr "" + +#: ../../content/applications/productivity/discuss/chatter.rst:0 +msgid "A close up of a chatter thread with an update to a contact record." +msgstr "" + +#: ../../content/applications/productivity/discuss/chatter.rst:32 +msgid "If a record was created, or edited, via an imported file, or was otherwise updated through an intervention by the system, the chatter thread creates a log note, and credits the change to OdooBot." +msgstr "" + +#: ../../content/applications/productivity/discuss/chatter.rst:-1 +msgid "A close up of a chatter thread of an OdooBot created contact record." +msgstr "" + +#: ../../content/applications/productivity/discuss/chatter.rst:43 +msgid "Add followers" +msgstr "" + +#: ../../content/applications/productivity/discuss/chatter.rst:45 +msgid "A *follower* is a user or contact that is added to a record and is notified when the record is updated, based on specific :ref:`follower subscription settings `. Followers can add themselves, or can be added by another user." +msgstr "" + +#: ../../content/applications/productivity/discuss/chatter.rst:50 +msgid "If a user creates, or is assigned to a record, they are automatically added as a follower." +msgstr "" + +#: ../../content/applications/productivity/discuss/chatter.rst:52 +msgid "To follow a record, navigate to any record with a chatter thread. For example, to open a *Helpdesk* ticket, navigate to :menuselection:`Helpdesk app --> Tickets --> All Tickets`, and select a ticket from the list to open it." +msgstr "" + +#: ../../content/applications/productivity/discuss/chatter.rst:56 +msgid "At the top-right, above the chatter composer, click :guilabel:`Follow`. Doing this changes the button to read :guilabel:`Following`. Click it again to :guilabel:`Unfollow`." +msgstr "" + +#: ../../content/applications/productivity/discuss/chatter.rst:60 +msgid "Manage followers" +msgstr "" + +#: ../../content/applications/productivity/discuss/chatter.rst:62 +msgid "To add another user, or contact, as a follower, click the :guilabel:`👤 (user)` icon. This opens a drop-down list of the current followers. Click :guilabel:`Add Followers` to open an :guilabel:`Invite Follower` pop-up window." +msgstr "" + +#: ../../content/applications/productivity/discuss/chatter.rst:66 +msgid "Select one or more contacts from the :guilabel:`Recipients` drop-down list. To notify the contacts, tick the :guilabel:`Send Notification` checkbox. Edit the message template as desired, then click :guilabel:`Add Followers`." +msgstr "" + +#: ../../content/applications/productivity/discuss/chatter.rst:70 +msgid "To remove followers, click the :guilabel:`👤 (user)` icon to open the current followers list. Find the name of the follower to be removed, and click the :guilabel:`x` icon." +msgstr "" + +#: ../../content/applications/productivity/discuss/chatter.rst:76 +msgid "Edit follower subscription" +msgstr "" + +#: ../../content/applications/productivity/discuss/chatter.rst:78 +msgid "The updates a follower receives can vary based on their subscription settings. To see the type of updates a follower is subscribed to, and to edit the list, click the :guilabel:`👤 (user)` icon. Find the appropriate follower in the list, then click the :guilabel:`✏️ (pencil)` icon. This opens the :guilabel:`Edit Subscription` pop-up window for the follower." +msgstr "" + +#: ../../content/applications/productivity/discuss/chatter.rst:83 +msgid "The list of available subscription settings varies depending on the record type. For example, a follower of a *Helpdesk* ticket may be informed when the ticket is rated. This option would not be available for the followers of a *CRM* opportunity." +msgstr "" + +#: ../../content/applications/productivity/discuss/chatter.rst:87 +msgid "Tick the checkbox for any updates the follower should receive, and clear the checkbox for any updates they should **not** receive. Click :guilabel:`Apply` when finished." +msgstr "" + +#: ../../content/applications/productivity/discuss/chatter.rst:94 +msgid "The Edit Subscription window on a Helpdesk ticket." +msgstr "" + +#: ../../content/applications/productivity/discuss/chatter.rst:94 +msgid "The Edit Subscription options vary depending on the record type. These are the options for a Helpdesk ticket." +msgstr "" + +#: ../../content/applications/productivity/discuss/chatter.rst:100 +msgid "Log notes" +msgstr "" + +#: ../../content/applications/productivity/discuss/chatter.rst:102 +msgid "The chatter function includes the ability to log internal notes on individual records. These notes are only accessible to internal users, and are available on any records that feature a chatter thread." +msgstr "" + +#: ../../content/applications/productivity/discuss/chatter.rst:106 +msgid "To log an internal note, first navigate to a record. For example, to open a *CRM* opportunity, navigate to :menuselection:`CRM app --> Sales --> My Pipeline`, and click on the Kanban card of an opportunity to open it. Then, at the top-right, above the chatter composer, click :guilabel:`Log note`." +msgstr "" + +#: ../../content/applications/productivity/discuss/chatter.rst:111 +msgid "Enter the note in the chatter composer. To tag an internal user, type `@`, and begin typing the name of the person to tag. Then, select a name from the drop-down menu. Depending on their notification settings, the user is notified by email, or through Odoo." +msgstr "" + +#: ../../content/applications/productivity/discuss/chatter.rst:116 +msgid "Outside contacts can also be tagged in an internal log note. The contact then receives an email with the contents of the note they were tagged in, including any attachments added directly to the note. If they respond to the email, their response is logged in the chatter, and they are added to the record as a follower." +msgstr "" + +#: ../../content/applications/productivity/discuss/chatter.rst:121 +msgid "Outside contacts are **not** able to log in to view the entire chatter thread, and are only notified of specific updates, based on their :ref:`follower subscription settings `, or when they are tagged directly." +msgstr "" + +#: ../../content/applications/productivity/discuss/chatter.rst:128 +msgid "Send messages" +msgstr "" + +#: ../../content/applications/productivity/discuss/chatter.rst:130 +msgid "Chatter composers can send messages to outside contacts, without having to leave the database, or open a different application. This makes it easy to communicate with potential customers in the *Sales* and *CRM* applications, or vendors in the *Purchase* app." +msgstr "" + +#: ../../content/applications/productivity/discuss/chatter.rst:134 +msgid "To send a message, first navigate to a record. For example, to send a message from a *CRM* opportunity, navigate to :menuselection:`CRM app --> Sales --> My Pipeline`, and click on the Kanban card of an opportunity to open it. Then, at the top-right, above the chatter composer, click :guilabel:`Send message`." +msgstr "" + +#: ../../content/applications/productivity/discuss/chatter.rst:140 +msgid "Press :command:`Ctrl + Enter` to send a message, instead of using the :guilabel:`Send` button." +msgstr "" + +#: ../../content/applications/productivity/discuss/chatter.rst:142 +msgid "If any :ref:`followers ` have been added to the record, they are added as recipients of the message." +msgstr "" + +#: ../../content/applications/productivity/discuss/chatter.rst:146 +msgid ":ref:`Followers ` of a record are added as recipients of a message automatically. If a follower should **not** receive a message, they must be removed as a follower before the message is sent, or a note is logged." +msgstr "" + +#: ../../content/applications/productivity/discuss/chatter.rst:-1 +msgid "A chatter composer preparing to send a message to the followers of a CRM opportunity and\n" +"the customer listed on the opportunity record." +msgstr "" + +#: ../../content/applications/productivity/discuss/chatter.rst:156 +msgid "Expand full composer" +msgstr "" + +#: ../../content/applications/productivity/discuss/chatter.rst:158 +msgid "The chatter composer can be expanded to a larger pop-up window, allowing for additional customizations." +msgstr "" + +#: ../../content/applications/productivity/discuss/chatter.rst:161 +msgid "To open the full composer, click the :guilabel:`expand` icon in the bottom-right corner of the composer window." +msgstr "" + +#: ../../content/applications/productivity/discuss/chatter.rst:168 +msgid "A chatter composer with emphasis on the expand icon." +msgstr "" + +#: ../../content/applications/productivity/discuss/chatter.rst:168 +msgid "The expand icon in a chatter composer." +msgstr "" + +#: ../../content/applications/productivity/discuss/chatter.rst:170 +msgid "Doing this opens a :guilabel:`Compose Email` pop-up window. Confirm or edit the intended :guilabel:`Recipients` of the message, or add additional recipients. The :guilabel:`Subject` field auto-populates based on the title of the record, though it can be edited, if desired." +msgstr "" + +#: ../../content/applications/productivity/discuss/chatter.rst:174 +msgid "To use an :doc:`email template <../../general/companies/email_template/>` for the message, select it from the drop-down menu in the :guilabel:`Load template` field." +msgstr "" + +#: ../../content/applications/productivity/discuss/chatter.rst:178 +msgid "The number and type of templates available vary, based on the record the message is created from." +msgstr "" + +#: ../../content/applications/productivity/discuss/chatter.rst:180 +msgid "Click :guilabel:`📎 Attachments` to add any files to the message, then click :guilabel:`Send`." +msgstr "" + +#: ../../content/applications/productivity/discuss/chatter.rst:-1 +msgid "The expanded full chatter composer in the CRM application." +msgstr "" + +#: ../../content/applications/productivity/discuss/chatter.rst:187 +msgid "Edit sent messages" +msgstr "" + +#: ../../content/applications/productivity/discuss/chatter.rst:189 +msgid "Messages can be edited after they are sent, to fix typos, correct mistakes, or add missing information." +msgstr "" + +#: ../../content/applications/productivity/discuss/chatter.rst:193 +msgid "When messages are edited after they have been sent, an updated message is **not** sent to the recipient." +msgstr "" + +#: ../../content/applications/productivity/discuss/chatter.rst:196 +msgid "To edit a sent message, click the :guilabel:`... (ellipsis)` icon menu to the right of the message. Then, select :guilabel:`Edit`. Make any necessary adjustments to the message." +msgstr "" + +#: ../../content/applications/productivity/discuss/chatter.rst:-1 +msgid "The edit message option in a chatter thread." +msgstr "" + +#: ../../content/applications/productivity/discuss/chatter.rst:203 +msgid "To save the changes, press :command:`Ctrl + Enter`. To discard the changes, press :command:`Escape`." +msgstr "" + +#: ../../content/applications/productivity/discuss/chatter.rst:206 +msgid "Users with Admin-level access rights can edit any sent messages. Users without Admin rights can **only** edit messages they created." +msgstr "" + +#: ../../content/applications/productivity/discuss/chatter.rst:212 +msgid "Search messages" +msgstr "" + +#: ../../content/applications/productivity/discuss/chatter.rst:214 +msgid "Chatter threads can become long after a while, because of all the information they contain. To make it easier to find a specific entry, users can search the text of messages and notes for specific keywords." +msgstr "" + +#: ../../content/applications/productivity/discuss/chatter.rst:218 +msgid "First, select a record with a chatter thread. For example, to search a *CRM* opportunity, navigate to :menuselection:`CRM app --> Sales --> My Pipeline`, and click on the Kanban card of an opportunity to open it. Then, at the top-right, above the chatter composer, click the :guilabel:`🔍 (magnifying glass)` icon to open the search bar." +msgstr "" + +#: ../../content/applications/productivity/discuss/chatter.rst:223 +msgid "Enter a keyword or phrase into the search bar, then hit :command:`Enter`, or click the :guilabel:`🔍 (magnifying glass)` icon to the right of the search bar. Any messages or notes containing the keyword or phrase entered are listed below the search bar, with the keyword highlighted." +msgstr "" + +#: ../../content/applications/productivity/discuss/chatter.rst:227 +msgid "To be taken directly to a particular message in the chatter thread, hover over the upper-right corner of the result to reveal a :guilabel:`Jump` button. Click this button to be directed to that message's location in the thread." +msgstr "" + +#: ../../content/applications/productivity/discuss/chatter.rst:235 +msgid "Search results in a chatter thread emphasising the search icon and the jump button." +msgstr "" + +#: ../../content/applications/productivity/discuss/chatter.rst:235 +msgid "Search results in a chatter thread. Hover over the upper-right corner of a result to see the **Jump** option. Click it to be taken directly to that message in the chatter thread." +msgstr "" + +#: ../../content/applications/productivity/discuss/chatter.rst:241 +msgid "Schedule activities" +msgstr "" + +#: ../../content/applications/productivity/discuss/chatter.rst:243 +msgid "*Activities* are follow-up tasks tied to a record in an Odoo database. Activities can be scheduled on any database page that contains a chatter thread, Kanban view, list view, or activities view of an application." +msgstr "" + +#: ../../content/applications/productivity/discuss/chatter.rst:247 +msgid "To schedule an activity through a chatter thread, click the :guilabel:`Activities` button, located at the top of the chatter on any record. On the :guilabel:`Schedule Activity` pop-up window that appears, select an :guilabel:`Activity Type` from the drop-down menu." +msgstr "" + +#: ../../content/applications/productivity/discuss/chatter.rst:252 +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/productivity/discuss/chatter.rst:256 +msgid "Enter a title for the activity in the :guilabel:`Summary` field, located in the :guilabel:`Schedule Activity` pop-up window." +msgstr "" + +#: ../../content/applications/productivity/discuss/chatter.rst:259 +msgid "Select a name from the :guilabel:`Assigned to` drop-down menu to assign the activity to a different user. Otherwise, the user creating the activity is automatically assigned." +msgstr "" + +#: ../../content/applications/productivity/discuss/chatter.rst:262 +msgid "Add any additional information in the optional :guilabel:`Log a note...` field." +msgstr "" + +#: ../../content/applications/productivity/discuss/chatter.rst:265 +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/productivity/discuss/chatter.rst:269 +msgid "Lastly, click one of the following buttons:" +msgstr "" + +#: ../../content/applications/productivity/discuss/chatter.rst:271 +msgid ":guilabel:`Schedule`: adds the activity to the chatter under :guilabel:`Planned activities`." +msgstr "" + +#: ../../content/applications/productivity/discuss/chatter.rst:272 +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/productivity/discuss/chatter.rst:274 +msgid ":guilabel:`Done \\& Schedule Next`: adds the task under :guilabel:`Today` marked as done, and opens a new activity window." +msgstr "" + +#: ../../content/applications/productivity/discuss/chatter.rst:276 +msgid ":guilabel:`Discard`: discards any changes made on the pop-up window." +msgstr "" + +#: ../../content/applications/productivity/discuss/chatter.rst:278 +msgid "Scheduled activities are added to the chatter for the record under :guilabel:`Planned activities`, and are color-coded based on their due date." +msgstr "" + +#: ../../content/applications/productivity/discuss/chatter.rst:281 +msgid "**Red** icons indicate an overdue activity." +msgstr "" + +#: ../../content/applications/productivity/discuss/chatter.rst:282 +msgid "**Yellow** icons indicate an activity with a due date scheduled for the current date." +msgstr "" + +#: ../../content/applications/productivity/discuss/chatter.rst:283 +msgid "**Green** icons indicate an activity with a due date scheduled in the future." +msgstr "" + +#: ../../content/applications/productivity/discuss/chatter.rst:-1 +msgid "A chatter thread with planned activities with varying due dates." +msgstr "" + +#: ../../content/applications/productivity/discuss/chatter.rst:290 +msgid "Click the :guilabel:`ℹ️ (info)` icon next to a planned activity to see additional details." +msgstr "" + +#: ../../content/applications/productivity/discuss/chatter.rst:0 +msgid "A detailed view of a planned activity." +msgstr "" + +#: ../../content/applications/productivity/discuss/chatter.rst:296 +msgid "After completing an activity, click :guilabel:`Mark Done` under the activity entry in the chatter. This opens a :guilabel:`Mark Done` pop-up window, where additional notes about the activity can be entered. After adding any comments to the pop-up window, click: :guilabel:`Done \\& Schedule Next`, :guilabel:`Done`, or :guilabel:`Discard`." +msgstr "" + +#: ../../content/applications/productivity/discuss/chatter.rst:301 +msgid "After the activity is marked complete, an entry with the activity type, title, and any other details that were included in the pop-up window are listed in the chatter." +msgstr "" + +#: ../../content/applications/productivity/discuss/chatter.rst:-1 +msgid "A chatter thread with a completed activity, included additional details." +msgstr "" + +#: ../../content/applications/productivity/discuss/chatter.rst:311 +msgid "Attach files" +msgstr "" + +#: ../../content/applications/productivity/discuss/chatter.rst:313 +msgid "Files can be added as attachments in the chatter, either to send with messages, or to include with a record." +msgstr "" + +#: ../../content/applications/productivity/discuss/chatter.rst:317 +msgid "After a file has been added to a chatter thread, it can be downloaded by any user with access to the thread. Click the :guilabel:`📎 (paperclip)` icon to make the files header visible, if necessary. Then, click the download icon on the file to download it." +msgstr "" + +#: ../../content/applications/productivity/discuss/chatter.rst:321 +msgid "To attach a file, click the :guilabel:`📎 (paperclip)` icon located at the top of the chatter composer of any record that contains a chatter thread." +msgstr "" + +#: ../../content/applications/productivity/discuss/chatter.rst:324 +msgid "This opens a file explorer pop-up window. Navigate to the desired file, select it, then click :guilabel:`Open` to add it to the record. Alternatively, files can be dragged and dropped directly onto a chatter thread." +msgstr "" + +#: ../../content/applications/productivity/discuss/chatter.rst:328 +msgid "After files have been added, they are listed in the chatter thread, under a :guilabel:`Files` heading." +msgstr "" + +#: ../../content/applications/productivity/discuss/chatter.rst:332 +msgid "After at least one file has been added to a chatter record, a new button labeled :guilabel:`Attach files` appears below the :guilabel:`Files` heading. To attach any additional files, this is the button that **must** be used, instead of the :guilabel:`📎 (paperclip)` icon at the top of the chatter thread." +msgstr "" + +#: ../../content/applications/productivity/discuss/chatter.rst:337 +msgid "After the :guilabel:`Files` section heading appears in the thread, clicking the :guilabel:`📎 (paperclip)` icon no longer opens a file explorer pop-up window. Instead, clicking the :guilabel:`📎 (paperclip)` icon toggles the :guilabel:`Files` section from visible to invisible in the chatter thread." +msgstr "" + +#: ../../content/applications/productivity/discuss/chatter.rst:0 +msgid "A chatter thread with a file attached and the Attach files button added." +msgstr "" + +#: ../../content/applications/productivity/discuss/chatter.rst:349 +msgid "Integrations" +msgstr "" + +#: ../../content/applications/productivity/discuss/chatter.rst:351 +msgid "Beyond the standard features, additional integrations can be enabled to work with the chatter feature, specifically *WhatsApp* and *Google Translate*." +msgstr "" + +#: ../../content/applications/productivity/discuss/chatter.rst:355 +msgid "Before the *WhatsApp* and *Google Translate* integrations can be used with the chatter, they **must** be configured. Step-by-step instructions on how to set-up each of these features can be found in the documentation below:" +msgstr "" + +#: ../../content/applications/productivity/discuss/chatter.rst:359 +#: ../../content/applications/productivity/discuss/chatter.rst:418 +msgid ":doc:`WhatsApp <../whatsapp>`" +msgstr "" + +#: ../../content/applications/productivity/discuss/chatter.rst:360 +msgid ":doc:`Google Translate <../../general/integrations/google_translate>`" +msgstr "" + +#: ../../content/applications/productivity/discuss/chatter.rst:363 +#: ../../content/applications/productivity/whatsapp.rst:3 +msgid "WhatsApp" +msgstr "" + +#: ../../content/applications/productivity/discuss/chatter.rst:365 +msgid "*WhatsApp* is an instant messaging and voice-over-IP app that allows users to send and receive messages, as well as share content." +msgstr "" + +#: ../../content/applications/productivity/discuss/chatter.rst:369 +msgid "*WhatsApp* is an Odoo Enterprise-only application that does **not** work in the Odoo Community edition. To sign up for an Odoo Enterprise edition, click here: `Odoo Free Trial `_." +msgstr "" + +#: ../../content/applications/productivity/discuss/chatter.rst:373 +msgid "After *WhatsApp* has been configured and enabled within a database, a :guilabel:`WhatsApp` button is added above the chatter composer on any applicable record. If one or more approved *WhatsApp* templates are found for that model, clicking this button opens a :guilabel:`Send WhatsApp Message` pop-up window." +msgstr "" + +#: ../../content/applications/productivity/discuss/chatter.rst:379 +msgid "*WhatsApp* templates **must** be approved before they can be used. See :ref:`WhatsApp templates ` for more information." +msgstr "" + +#: ../../content/applications/productivity/discuss/chatter.rst:-1 +msgid "A send WhatsApp message pop-up window." +msgstr "" + +#: ../../content/applications/productivity/discuss/chatter.rst:387 +msgid "Google Translate" +msgstr "" + +#: ../../content/applications/productivity/discuss/chatter.rst:389 +msgid "*Google Translate* can be used to translate user-generated text in the Odoo chatter." +msgstr "" + +#: ../../content/applications/productivity/discuss/chatter.rst:391 +msgid "To enable *Google Translate* on a database, an *API key* must first :doc:`be created <../../general/integrations/google_translate>` through the `Google API Console `_." +msgstr "" + +#: ../../content/applications/productivity/discuss/chatter.rst:395 +msgid "After creating the API key, navigate to the :menuselection:`Settings app --> Discuss section` and paste the key in the :guilabel:`Message Translation` field. Click :guilabel:`Save` to save the changes." +msgstr "" + +#: ../../content/applications/productivity/discuss/chatter.rst:400 +msgid "Translate a chatter message" +msgstr "" + +#: ../../content/applications/productivity/discuss/chatter.rst:402 +msgid "To translate a user's text from another language, click the :guilabel:`... (ellipsis)` icon menu to the right of the chatter. Then, select :guilabel:`Translate`. The content translates to the language set in the :doc:`user's preferences <../../general/users/language/>`." +msgstr "" + +#: ../../content/applications/productivity/discuss/chatter.rst:-1 +msgid "alt text" +msgstr "" + +#: ../../content/applications/productivity/discuss/chatter.rst:411 +msgid "Using the *Google Translate* API **requires** a current billing account with `Google `_." +msgstr "" + +#: ../../content/applications/productivity/discuss/chatter.rst:415 +msgid ":doc:`Discuss <../discuss>`" +msgstr "" + +#: ../../content/applications/productivity/discuss/chatter.rst:416 +msgid ":doc:`Discuss Channels <../discuss/team_communication/>`" +msgstr "" + +#: ../../content/applications/productivity/discuss/chatter.rst:417 +msgid ":doc:`Activities <../../essentials/activities>`" +msgstr "" + #: ../../content/applications/productivity/discuss/ice_servers.rst:3 msgid "Configure ICE servers with Twilio" msgstr "" @@ -749,7 +1471,7 @@ msgstr "" #: ../../content/applications/productivity/documents.rst:16 #: ../../content/applications/productivity/voip/axivox/axivox_config.rst:17 -#: ../../content/applications/productivity/voip/onsip.rst:19 +#: ../../content/applications/productivity/voip/onsip.rst:33 msgid "Configuration" msgstr "" @@ -2284,35 +3006,35 @@ msgstr "" msgid "Spreadsheet" msgstr "" -#: ../../content/applications/productivity/spreadsheet.rst:14 +#: ../../content/applications/productivity/spreadsheet.rst:15 msgid "Spreadsheet lets you organize, analyze, and visualize your data in tabular form. Among others, you can:" msgstr "" -#: ../../content/applications/productivity/spreadsheet.rst:17 +#: ../../content/applications/productivity/spreadsheet.rst:18 msgid ":doc:`Insert and link your Odoo data (pivots, graphs, lists, and menus) `." msgstr "" -#: ../../content/applications/productivity/spreadsheet.rst:18 -msgid ":doc:`Use default templates or create new ones `." -msgstr "" - #: ../../content/applications/productivity/spreadsheet.rst:19 -msgid "Format data." +msgid ":doc:`Use formulas and functions `." msgstr "" #: ../../content/applications/productivity/spreadsheet.rst:20 -msgid "Use formulas and functions." +msgid ":doc:`Use default templates or create new ones `." msgstr "" #: ../../content/applications/productivity/spreadsheet.rst:21 +msgid "Format data." +msgstr "" + +#: ../../content/applications/productivity/spreadsheet.rst:22 msgid "Sort and filter data." msgstr "" -#: ../../content/applications/productivity/spreadsheet.rst:26 +#: ../../content/applications/productivity/spreadsheet.rst:27 msgid "Glossary" msgstr "" -#: ../../content/applications/productivity/spreadsheet.rst:28 +#: ../../content/applications/productivity/spreadsheet.rst:29 msgid "Some of Spreadsheet's main :abbr:`UI (user interface)` elements are highlighted and defined below." msgstr "" @@ -2320,38 +3042,2660 @@ msgstr "" msgid "Spreadsheet main UI elements" msgstr "" -#: ../../content/applications/productivity/spreadsheet.rst:34 +#: ../../content/applications/productivity/spreadsheet.rst:35 msgid "Menu bar" msgstr "" -#: ../../content/applications/productivity/spreadsheet.rst:35 +#: ../../content/applications/productivity/spreadsheet.rst:36 msgid "Top bar" msgstr "" -#: ../../content/applications/productivity/spreadsheet.rst:36 +#: ../../content/applications/productivity/spreadsheet.rst:37 msgid "Formula bar" msgstr "" -#: ../../content/applications/productivity/spreadsheet.rst:37 +#: ../../content/applications/productivity/spreadsheet.rst:38 msgid "Filters button" msgstr "" -#: ../../content/applications/productivity/spreadsheet.rst:38 +#: ../../content/applications/productivity/spreadsheet.rst:39 msgid "Row header" msgstr "" -#: ../../content/applications/productivity/spreadsheet.rst:39 +#: ../../content/applications/productivity/spreadsheet.rst:40 msgid "Column header" msgstr "" -#: ../../content/applications/productivity/spreadsheet.rst:40 +#: ../../content/applications/productivity/spreadsheet.rst:41 msgid "Cell menu" msgstr "" -#: ../../content/applications/productivity/spreadsheet.rst:41 +#: ../../content/applications/productivity/spreadsheet.rst:42 msgid "Bottom bar" msgstr "" +#: ../../content/applications/productivity/spreadsheet/functions.rst:3 +msgid "Functions" +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/functions.rst:5 +msgid "Spreadsheet functions are divided in the following categories:" +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/functions.rst:7 +msgid ":ref:`Array `" +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/functions.rst:8 +msgid ":ref:`Database `" +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/functions.rst:9 +msgid ":ref:`Date `" +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/functions.rst:10 +msgid ":ref:`Engineering `" +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/functions.rst:11 +msgid ":ref:`Filter `" +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/functions.rst:12 +msgid ":ref:`Financial `" +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/functions.rst:13 +msgid ":ref:`Info `" +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/functions.rst:14 +msgid ":ref:`Logical `" +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/functions.rst:15 +msgid ":ref:`Lookup `" +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/functions.rst:16 +msgid ":ref:`Math `" +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/functions.rst:17 +msgid ":ref:`Misc `" +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/functions.rst:18 +msgid ":ref:`Odoo `" +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/functions.rst:19 +msgid ":ref:`Operators `" +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/functions.rst:20 +msgid ":ref:`Statistical `" +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/functions.rst:21 +msgid ":ref:`Text `" +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/functions.rst:22 +msgid ":ref:`Web `" +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/functions.rst:25 +msgid "Formulas containing functions that are not compatible with Excel are replaced by their evaluated result when exporting a spreadsheet." +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/functions.rst:31 +msgid "Array" +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/functions.rst:37 +#: ../../content/applications/productivity/spreadsheet/functions.rst:89 +#: ../../content/applications/productivity/spreadsheet/functions.rst:125 +#: ../../content/applications/productivity/spreadsheet/functions.rst:201 +#: ../../content/applications/productivity/spreadsheet/functions.rst:215 +#: ../../content/applications/productivity/spreadsheet/functions.rst:231 +#: ../../content/applications/productivity/spreadsheet/functions.rst:341 +#: ../../content/applications/productivity/spreadsheet/functions.rst:371 +#: ../../content/applications/productivity/spreadsheet/functions.rst:403 +#: ../../content/applications/productivity/spreadsheet/functions.rst:437 +#: ../../content/applications/productivity/spreadsheet/functions.rst:565 +#: ../../content/applications/productivity/spreadsheet/functions.rst:579 +#: ../../content/applications/productivity/spreadsheet/functions.rst:617 +#: ../../content/applications/productivity/spreadsheet/functions.rst:659 +#: ../../content/applications/productivity/spreadsheet/functions.rst:779 +#: ../../content/applications/productivity/spreadsheet/functions.rst:831 +msgid "Name and arguments" +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/functions.rst:38 +#: ../../content/applications/productivity/spreadsheet/functions.rst:90 +#: ../../content/applications/productivity/spreadsheet/functions.rst:126 +#: ../../content/applications/productivity/spreadsheet/functions.rst:202 +#: ../../content/applications/productivity/spreadsheet/functions.rst:216 +#: ../../content/applications/productivity/spreadsheet/functions.rst:232 +#: ../../content/applications/productivity/spreadsheet/functions.rst:342 +#: ../../content/applications/productivity/spreadsheet/functions.rst:372 +#: ../../content/applications/productivity/spreadsheet/functions.rst:404 +#: ../../content/applications/productivity/spreadsheet/functions.rst:438 +#: ../../content/applications/productivity/spreadsheet/functions.rst:566 +#: ../../content/applications/productivity/spreadsheet/functions.rst:580 +#: ../../content/applications/productivity/spreadsheet/functions.rst:618 +#: ../../content/applications/productivity/spreadsheet/functions.rst:660 +#: ../../content/applications/productivity/spreadsheet/functions.rst:780 +#: ../../content/applications/productivity/spreadsheet/functions.rst:832 +msgid "Description or link" +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/functions.rst:39 +msgid "ARRAY.CONSTRAIN(input_range, rows, columns)" +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/functions.rst:40 +msgid "Returns a result array constrained to a specific width and height (not compatible with Excel)" +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/functions.rst:41 +msgid "CHOOSECOLS(array, col_num, [col_num2, ...])" +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/functions.rst:42 +msgid "`Excel CHOOSECOLS article `_" +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/functions.rst:43 +msgid "CHOOSEROWS(array, row_num, [row_num2, ...])" +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/functions.rst:44 +msgid "`Excel CHOOSEROWS article `_" +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/functions.rst:45 +msgid "EXPAND(array, rows, [columns], [pad_with])" +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/functions.rst:46 +msgid "`Excel EXPAND article `_" +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/functions.rst:47 +msgid "FLATTEN(range, [range2, ...])" +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/functions.rst:48 +msgid "Flattens all the values from one or more ranges into a single column (not compatible with Excel)" +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/functions.rst:49 +msgid "FREQUENCY(data, classes)" +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/functions.rst:50 +msgid "`Excel FREQUENCY article `_" +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/functions.rst:51 +msgid "HSTACK(range1, [range2, ...])" +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/functions.rst:52 +msgid "`Excel HSTACK article `_" +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/functions.rst:53 +msgid "MDETERM(square_matrix)" +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/functions.rst:54 +msgid "`Excel MDETERM article `_" +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/functions.rst:55 +msgid "MINVERSE(square_matrix)" +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/functions.rst:56 +msgid "`Excel MINVERSE article `_" +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/functions.rst:57 +msgid "MMULT(matrix1, matrix2)" +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/functions.rst:58 +msgid "`Excel MMULT article `_" +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/functions.rst:59 +msgid "SUMPRODUCT(range1, [range2, ...])" +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/functions.rst:60 +msgid "`Excel SUMPRODUCT article `_" +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/functions.rst:61 +msgid "SUMX2MY2(array_x, array_y)" +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/functions.rst:62 +msgid "`Excel SUMX2MY2 article `_" +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/functions.rst:63 +msgid "SUMX2PY2(array_x, array_y)" +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/functions.rst:64 +msgid "`Excel SUMX2PY2 article `_" +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/functions.rst:65 +msgid "SUMXMY2(array_x, array_y)" +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/functions.rst:66 +msgid "`Excel SUMXMY2 article `_" +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/functions.rst:67 +msgid "TOCOL(array, [ignore], [scan_by_column])" +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/functions.rst:68 +msgid "`Excel TOCOL article `_" +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/functions.rst:69 +msgid "TOROW(array, [ignore], [scan_by_column])" +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/functions.rst:70 +msgid "`Excel TOROW article `_" +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/functions.rst:71 +msgid "TRANSPOSE(range)" +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/functions.rst:72 +msgid "`Excel TRANSPOSE article `_" +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/functions.rst:73 +msgid "VSTACK(range1, [range2, ...])" +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/functions.rst:74 +msgid "`Excel VSTACK article `_" +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/functions.rst:75 +msgid "WRAPCOLS(range, wrap_count, [pad_with])" +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/functions.rst:76 +msgid "`Excel WRAPCOLS article `_" +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/functions.rst:77 +msgid "WRAPROWS(range, wrap_count, [pad_with])" +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/functions.rst:78 +msgid "`Excel WRAPROWS article `_" +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/functions.rst:83 +msgid "Database" +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/functions.rst:91 +msgid "DAVERAGE(database, field, criteria)" +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/functions.rst:92 +msgid "`Excel DAVERAGE article `_" +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/functions.rst:93 +msgid "DCOUNT(database, field, criteria)" +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/functions.rst:94 +msgid "`Excel DCOUNT article `_" +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/functions.rst:95 +msgid "DCOUNTA(database, field, criteria)" +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/functions.rst:96 +msgid "`Excel DCOUNTA article `_" +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/functions.rst:97 +msgid "DGET(database, field, criteria)" +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/functions.rst:98 +msgid "`Excel DGET article `_" +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/functions.rst:99 +msgid "DMAX(database, field, criteria)" +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/functions.rst:100 +msgid "`Excel DMAX article `_" +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/functions.rst:101 +msgid "DMIN(database, field, criteria)" +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/functions.rst:102 +msgid "`Excel DMIN article `_" +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/functions.rst:103 +msgid "DPRODUCT(database, field, criteria)" +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/functions.rst:104 +msgid "`Excel DPRODUCT article `_" +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/functions.rst:105 +msgid "DSTDEV(database, field, criteria)" +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/functions.rst:106 +msgid "`Excel DSTDEV article `_" +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/functions.rst:107 +msgid "DSTDEVP(database, field, criteria)" +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/functions.rst:108 +msgid "`Excel DSTDEVP article `_" +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/functions.rst:109 +msgid "DSUM(database, field, criteria)" +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/functions.rst:110 +msgid "`Excel DSUM article `_" +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/functions.rst:111 +msgid "DVAR(database, field, criteria)" +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/functions.rst:112 +msgid "`Excel DVAR article `_" +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/functions.rst:113 +msgid "DVARP(database, field, criteria)" +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/functions.rst:114 +msgid "`Excel DVARP article `_" +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/functions.rst:119 +msgid "Date" +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/functions.rst:127 +msgid "DATE(year, month, day)" +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/functions.rst:128 +msgid "`Excel DATE article `_" +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/functions.rst:129 +msgid "DATEDIF(start_date, end_date, unit)" +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/functions.rst:130 +msgid "`Excel DATEDIF article `_" +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/functions.rst:131 +msgid "DATEVALUE(date_string)" +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/functions.rst:132 +msgid "`Excel DATEVALUE article `_" +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/functions.rst:133 +msgid "DAY(date)" +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/functions.rst:134 +msgid "`Excel DAY article `_" +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/functions.rst:135 +msgid "DAYS(end_date, start_date)" +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/functions.rst:136 +msgid "`Excel DAYS article `_" +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/functions.rst:137 +msgid "DAYS360(start_date, end_date, [method])" +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/functions.rst:138 +msgid "`Excel DAYS360 article `_" +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/functions.rst:139 +msgid "EDATE(start_date, months)" +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/functions.rst:140 +msgid "`Excel EDATE article `_" +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/functions.rst:141 +msgid "EOMONTH(start_date, months)" +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/functions.rst:142 +msgid "`Excel EOMONTH article `_" +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/functions.rst:143 +msgid "HOUR(time)" +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/functions.rst:144 +msgid "`Excel HOUR article `_" +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/functions.rst:145 +msgid "ISOWEEKNUM(date)" +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/functions.rst:146 +msgid "`Excel ISOWEEKNUM article `_" +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/functions.rst:147 +msgid "MINUTE(time)" +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/functions.rst:148 +msgid "`Excel MINUTE article `_" +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/functions.rst:149 +msgid "MONTH(date)" +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/functions.rst:150 +msgid "`Excel MONTH article `_" +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/functions.rst:151 +msgid "NETWORKDAYS(start_date, end_date, [holidays])" +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/functions.rst:152 +msgid "`Excel NETWORKDAYS article `_" +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/functions.rst:153 +msgid "NETWORKDAYS.INTL(start_date, end_date, [weekend], [holidays])" +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/functions.rst:154 +msgid "`Excel NETWORKDAYS.INTL article `_" +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/functions.rst:155 +msgid "NOW()" +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/functions.rst:156 +msgid "`Excel NOW article `_" +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/functions.rst:157 +msgid "SECOND(time)" +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/functions.rst:158 +msgid "`Excel SECOND article `_" +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/functions.rst:159 +msgid "TIME(hour, minute, second)" +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/functions.rst:160 +msgid "`Excel TIME article `_" +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/functions.rst:161 +msgid "TIMEVALUE(time_string)" +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/functions.rst:162 +msgid "`Excel TIMEVALUE article `_" +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/functions.rst:163 +msgid "TODAY()" +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/functions.rst:164 +msgid "`Excel TODAY article `_" +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/functions.rst:165 +msgid "WEEKDAY(date, [type])" +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/functions.rst:166 +msgid "`Excel WEEKDAY article `_" +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/functions.rst:167 +msgid "WEEKNUM(date, [type])" +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/functions.rst:168 +msgid "`Excel WEEKNUM article `_" +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/functions.rst:169 +msgid "WORKDAY(start_date, num_days, [holidays])" +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/functions.rst:170 +msgid "`Excel WORKDAY article `_" +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/functions.rst:171 +msgid "WORKDAY.INTL(start_date, num_days, [weekend], [holidays])" +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/functions.rst:172 +msgid "`Excel WORKDAY.INTL article `_" +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/functions.rst:173 +msgid "YEAR(date)" +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/functions.rst:174 +msgid "`Excel YEAR article `_" +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/functions.rst:175 +msgid "YEARFRAC(start_date, end_date, [day_count_convention])" +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/functions.rst:176 +msgid "Exact number of years between two dates (not compatible with Excel)" +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/functions.rst:177 +msgid "MONTH.START(date)" +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/functions.rst:178 +msgid "First day of the month preceding a date (not compatible with Excel)" +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/functions.rst:179 +msgid "MONTH.END(date)" +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/functions.rst:180 +msgid "Last day of the month following a date (not compatible with Excel)" +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/functions.rst:181 +msgid "QUARTER(date)" +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/functions.rst:182 +msgid "Quarter of the year a specific date falls in (not compatible with Excel)" +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/functions.rst:183 +msgid "QUARTER.START(date)" +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/functions.rst:184 +msgid "First day of the quarter of the year a specific date falls in (not compatible with Excel)" +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/functions.rst:185 +msgid "QUARTER.END(date)" +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/functions.rst:186 +msgid "Last day of the quarter of the year a specific date falls in (not compatible with Excel)" +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/functions.rst:187 +msgid "YEAR.START(date)" +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/functions.rst:188 +msgid "First day of the year a specific date falls in (not compatible with Excel)" +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/functions.rst:189 +msgid "YEAR.END(date)" +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/functions.rst:190 +msgid "Last day of the year a specific date falls in (not compatible with Excel)" +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/functions.rst:195 +msgid "Engineering" +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/functions.rst:203 +msgid "DELTA(number1, [number2])" +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/functions.rst:204 +msgid "`Excel DELTA article `_" +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/functions.rst:209 +msgid "Filter" +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/functions.rst:217 +msgid "FILTER(range, condition1, [condition2, ...])" +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/functions.rst:218 +msgid "`Excel FILTER article `_" +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/functions.rst:219 +msgid "UNIQUE(range, [by_column], [exactly_once])" +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/functions.rst:220 +msgid "`Excel UNIQUE article `_" +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/functions.rst:225 +msgid "Financial" +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/functions.rst:233 +msgid "ACCRINTM(issue, maturity, rate, redemption, [day_count_convention])" +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/functions.rst:234 +msgid "`Excel ACCRINTM article `_" +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/functions.rst:235 +msgid "AMORLINC(cost, purchase_date, first_period_end, salvage, period, rate, [day_count_convention])" +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/functions.rst:236 +msgid "`Excel AMORLINC article `_" +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/functions.rst:237 +msgid "COUPDAYS(settlement, maturity, frequency, [day_count_convention])" +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/functions.rst:238 +msgid "`Excel COUPDAYS article `_" +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/functions.rst:239 +msgid "COUPDAYBS(settlement, maturity, frequency, [day_count_convention])" +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/functions.rst:240 +msgid "`Excel COUPDAYBS article `_" +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/functions.rst:241 +msgid "COUPDAYSNC(settlement, maturity, frequency, [day_count_convention])" +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/functions.rst:242 +msgid "`Excel COUPDAYSNC article `_" +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/functions.rst:243 +msgid "COUPNCD(settlement, maturity, frequency, [day_count_convention])" +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/functions.rst:244 +msgid "`Excel COUPNCD article `_" +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/functions.rst:245 +msgid "COUPNUM(settlement, maturity, frequency, [day_count_convention])" +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/functions.rst:246 +msgid "`Excel COUPNUM article `_" +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/functions.rst:247 +msgid "COUPPCD(settlement, maturity, frequency, [day_count_convention])" +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/functions.rst:248 +msgid "`Excel COUPPCD article `_" +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/functions.rst:249 +msgid "CUMIPMT(rate, number_of_periods, present_value, first_period, last_period, [end_or_beginning])" +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/functions.rst:250 +msgid "`Excel CUMIPMT article `_" +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/functions.rst:251 +msgid "CUMPRINC(rate, number_of_periods, present_value, first_period, last_period, [end_or_beginning])" +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/functions.rst:252 +msgid "`Excel CUMPRINC article `_" +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/functions.rst:253 +msgid "DB(cost, salvage, life, period, [month])" +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/functions.rst:254 +msgid "`Excel DB article `_" +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/functions.rst:255 +msgid "DDB(cost, salvage, life, period, [factor])" +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/functions.rst:256 +msgid "`Excel DDB article `_" +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/functions.rst:257 +msgid "DISC(settlement, maturity, price, redemption, [day_count_convention])" +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/functions.rst:258 +msgid "`Excel DISC article `_" +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/functions.rst:259 +msgid "DOLLARDE(fractional_price, unit)" +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/functions.rst:260 +msgid "`Excel DOLLARDE article `_" +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/functions.rst:261 +msgid "DOLLARFR(decimal_price, unit)" +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/functions.rst:262 +msgid "`Excel DOLLARFR article `_" +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/functions.rst:263 +msgid "DURATION(settlement, maturity, rate, yield, frequency, [day_count_convention])" +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/functions.rst:264 +msgid "`Excel DURATION article `_" +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/functions.rst:265 +msgid "EFFECT(nominal_rate, periods_per_year)" +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/functions.rst:266 +msgid "`Excel EFFECT article `_" +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/functions.rst:267 +msgid "FV(rate, number_of_periods, payment_amount, [present_value], [end_or_beginning])" +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/functions.rst:268 +msgid "`Excel FV article `_" +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/functions.rst:269 +msgid "FVSCHEDULE(principal, rate_schedule)" +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/functions.rst:270 +msgid "`Excel FVSCHEDULE article `_" +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/functions.rst:271 +msgid "INTRATE(settlement, maturity, investment, redemption, [day_count_convention])" +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/functions.rst:272 +msgid "`Excel INTRATE article `_" +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/functions.rst:273 +msgid "IPMT(rate, period, number_of_periods, present_value, [future_value], [end_or_beginning])" +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/functions.rst:274 +msgid "`Excel IPMT article `_" +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/functions.rst:275 +msgid "IRR(cashflow_amounts, [rate_guess])" +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/functions.rst:276 +msgid "`Excel IRR article `_" +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/functions.rst:277 +msgid "ISPMT(rate, period, number_of_periods, present_value)" +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/functions.rst:278 +msgid "`Excel ISPMT article `_" +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/functions.rst:279 +msgid "MDURATION(settlement, maturity, rate, yield, frequency, [day_count_convention])" +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/functions.rst:280 +msgid "`Excel MDURATION article `_" +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/functions.rst:281 +msgid "MIRR(cashflow_amounts, financing_rate, reinvestment_return_rate)" +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/functions.rst:282 +msgid "`Excel MIRR article `_" +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/functions.rst:283 +msgid "NOMINAL(effective_rate, periods_per_year)" +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/functions.rst:284 +msgid "`Excel NOMINAL article `_" +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/functions.rst:285 +msgid "NPER(rate, payment_amount, present_value, [future_value], [end_or_beginning])" +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/functions.rst:286 +msgid "`Excel NPER article `_" +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/functions.rst:287 +msgid "NPV(discount, cashflow1, [cashflow2, ...])" +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/functions.rst:288 +msgid "`Excel NPV article `_" +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/functions.rst:289 +msgid "PDURATION(rate, present_value, future_value)" +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/functions.rst:290 +msgid "`Excel PDURATION article `_" +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/functions.rst:291 +msgid "PMT(rate, number_of_periods, present_value, [future_value], [end_or_beginning])" +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/functions.rst:292 +msgid "`Excel PMT article `_" +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/functions.rst:293 +msgid "PPMT(rate, period, number_of_periods, present_value, [future_value], [end_or_beginning])" +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/functions.rst:294 +msgid "`Excel PPMT article `_" +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/functions.rst:295 +msgid "PV(rate, number_of_periods, payment_amount, [future_value], [end_or_beginning])" +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/functions.rst:296 +msgid "`Excel PV article `_" +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/functions.rst:297 +msgid "PRICE(settlement, maturity, rate, yield, redemption, frequency, [day_count_convention])" +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/functions.rst:298 +msgid "`Excel PRICE article `_" +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/functions.rst:299 +msgid "PRICEDISC(settlement, maturity, discount, redemption, [day_count_convention])" +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/functions.rst:300 +msgid "`Excel PRICEDISC article `_" +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/functions.rst:301 +msgid "PRICEMAT(settlement, maturity, issue, rate, yield, [day_count_convention])" +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/functions.rst:302 +msgid "`Excel PRICEMAT article `_" +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/functions.rst:303 +msgid "RATE(number_of_periods, payment_per_period, present_value, [future_value], [end_or_beginning], [rate_guess])" +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/functions.rst:304 +msgid "`Excel RATE article `_" +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/functions.rst:305 +msgid "RECEIVED(settlement, maturity, investment, discount, [day_count_convention])" +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/functions.rst:306 +msgid "`Excel RECEIVED article `_" +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/functions.rst:307 +msgid "RRI(number_of_periods, present_value, future_value)" +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/functions.rst:308 +msgid "`Excel RRI article `_" +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/functions.rst:309 +msgid "SLN(cost, salvage, life)" +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/functions.rst:310 +msgid "`Excel SLN article `_" +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/functions.rst:311 +msgid "SYD(cost, salvage, life, period)" +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/functions.rst:312 +msgid "`Excel SYD article `_" +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/functions.rst:313 +msgid "TBILLPRICE(settlement, maturity, discount)" +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/functions.rst:314 +msgid "`Excel TBILLPRICE article `_" +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/functions.rst:315 +msgid "TBILLEQ(settlement, maturity, discount)" +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/functions.rst:316 +msgid "`Excel TBILLEQ article `_" +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/functions.rst:317 +msgid "TBILLYIELD(settlement, maturity, price)" +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/functions.rst:318 +msgid "`Excel TBILLYIELD article `_" +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/functions.rst:319 +msgid "VDB(cost, salvage, life, start, end, [factor], [no_switch])" +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/functions.rst:320 +msgid "`Excel VDB article `_" +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/functions.rst:321 +msgid "XIRR(cashflow_amounts, cashflow_dates, [rate_guess])" +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/functions.rst:322 +msgid "`Excel XIRR article `_" +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/functions.rst:323 +msgid "XNPV(discount, cashflow_amounts, cashflow_dates)" +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/functions.rst:324 +msgid "`Excel XNPV article `_" +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/functions.rst:325 +msgid "YIELD(settlement, maturity, rate, price, redemption, frequency, [day_count_convention])" +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/functions.rst:326 +msgid "`Excel YIELD article `_" +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/functions.rst:327 +msgid "YIELDDISC(settlement, maturity, price, redemption, [day_count_convention])" +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/functions.rst:328 +msgid "`Excel YIELDDISC article `_" +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/functions.rst:329 +msgid "YIELDMAT(settlement, maturity, issue, rate, price, [day_count_convention])" +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/functions.rst:330 +msgid "`Excel YIELDMAT article `_" +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/functions.rst:335 +msgid "Info" +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/functions.rst:343 +msgid "ISERR(value)" +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/functions.rst:344 +#: ../../content/applications/productivity/spreadsheet/functions.rst:346 +#: ../../content/applications/productivity/spreadsheet/functions.rst:348 +#: ../../content/applications/productivity/spreadsheet/functions.rst:350 +#: ../../content/applications/productivity/spreadsheet/functions.rst:352 +#: ../../content/applications/productivity/spreadsheet/functions.rst:354 +#: ../../content/applications/productivity/spreadsheet/functions.rst:356 +#: ../../content/applications/productivity/spreadsheet/functions.rst:358 +msgid "`Excel IS article `_" +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/functions.rst:345 +msgid "ISERROR(value)" +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/functions.rst:347 +msgid "ISLOGICAL(value)" +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/functions.rst:349 +msgid "ISNA(value)" +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/functions.rst:351 +msgid "ISNONTEXT(value)" +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/functions.rst:353 +msgid "ISNUMBER(value)" +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/functions.rst:355 +msgid "ISTEXT(value)" +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/functions.rst:357 +msgid "ISBLANK(value)" +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/functions.rst:359 +msgid "NA()" +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/functions.rst:360 +msgid "`Excel NA article `_" +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/functions.rst:365 +msgid "Logical" +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/functions.rst:373 +msgid "AND(logical_expression1, [logical_expression2, ...])" +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/functions.rst:374 +msgid "`Excel AND article `_" +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/functions.rst:375 +msgid "FALSE()" +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/functions.rst:376 +msgid "`Excel FALSE article `_" +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/functions.rst:377 +msgid "IF(logical_expression, value_if_true, [value_if_false])" +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/functions.rst:378 +msgid "`Excel IF article `_" +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/functions.rst:379 +msgid "IFERROR(value, [value_if_error])" +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/functions.rst:380 +msgid "`Excel IFERROR article `_" +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/functions.rst:381 +msgid "IFNA(value, [value_if_error])" +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/functions.rst:382 +msgid "`Excel IFNA article `_" +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/functions.rst:383 +msgid "IFS(condition1, value1, [condition2, ...], [value2, ...])" +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/functions.rst:384 +msgid "`Excel IFS article `_" +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/functions.rst:385 +msgid "NOT(logical_expression)" +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/functions.rst:386 +msgid "`Excel NOT article `_" +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/functions.rst:387 +msgid "OR(logical_expression1, [logical_expression2, ...])" +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/functions.rst:388 +msgid "`Excel OR article `_" +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/functions.rst:389 +msgid "TRUE()" +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/functions.rst:390 +msgid "`Excel TRUE article `_" +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/functions.rst:391 +msgid "XOR(logical_expression1, [logical_expression2, ...])" +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/functions.rst:392 +msgid "`Excel XOR article `_" +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/functions.rst:397 +msgid "Lookup" +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/functions.rst:405 +msgid "ADDRESS(row, column, [absolute_relative_mode], [use_a1_notation], [sheet])" +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/functions.rst:406 +msgid "`Excel ADDRESS article `_" +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/functions.rst:407 +msgid "COLUMN([cell_reference])" +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/functions.rst:408 +msgid "`Excel COLUMN article `_" +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/functions.rst:409 +msgid "COLUMNS(range)" +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/functions.rst:410 +msgid "`Excel COLUMNS article `_" +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/functions.rst:411 +msgid "HLOOKUP(search_key, range, index, [is_sorted])" +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/functions.rst:412 +msgid "`Excel HLOOKUP article `_" +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/functions.rst:413 +msgid "INDEX(reference, row, column)" +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/functions.rst:414 +msgid "`Excel INDEX article `_" +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/functions.rst:415 +msgid "LOOKUP(search_key, search_array, [result_range])" +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/functions.rst:416 +msgid "`Excel LOOKUP article `_" +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/functions.rst:417 +msgid "MATCH(search_key, range, [search_type])" +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/functions.rst:418 +msgid "`Excel MATCH article `_" +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/functions.rst:419 +msgid "ROW([cell_reference])" +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/functions.rst:420 +msgid "`Excel ROW article `_" +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/functions.rst:421 +msgid "ROWS(range)" +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/functions.rst:422 +msgid "`Excel ROWS article `_" +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/functions.rst:423 +msgid "VLOOKUP(search_key, range, index, [is_sorted])" +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/functions.rst:424 +msgid "`Excel VLOOKUP article `_" +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/functions.rst:425 +msgid "XLOOKUP(search_key, lookup_range, return_range, [if_not_found], [match_mode], [search_mode])" +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/functions.rst:426 +msgid "`Excel XLOOKUP article `_" +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/functions.rst:431 +msgid "Math" +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/functions.rst:439 +msgid "ABS(value)" +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/functions.rst:440 +msgid "`Excel ABS article `_" +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/functions.rst:441 +msgid "ACOS(value)" +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/functions.rst:442 +msgid "`Excel ACOS article `_" +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/functions.rst:443 +msgid "ACOSH(value)" +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/functions.rst:444 +msgid "`Excel ACOSH article `_" +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/functions.rst:445 +msgid "ACOT(value)" +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/functions.rst:446 +msgid "`Excel ACOT article `_" +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/functions.rst:447 +msgid "ACOTH(value)" +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/functions.rst:448 +msgid "`Excel ACOTH article `_" +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/functions.rst:449 +msgid "ASIN(value)" +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/functions.rst:450 +msgid "`Excel ASIN article `_" +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/functions.rst:451 +msgid "ASINH(value)" +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/functions.rst:452 +msgid "`Excel ASINH article `_" +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/functions.rst:453 +msgid "ATAN(value)" +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/functions.rst:454 +msgid "`Excel ATAN article `_" +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/functions.rst:455 +msgid "ATAN2(x, y)" +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/functions.rst:456 +msgid "`Excel ATAN2 article `_" +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/functions.rst:457 +msgid "ATANH(value)" +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/functions.rst:458 +msgid "`Excel ATANH article `_" +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/functions.rst:459 +msgid "CEILING(value, [factor])" +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/functions.rst:460 +msgid "`Excel CEILING article `_" +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/functions.rst:461 +msgid "CEILING.MATH(number, [significance], [mode])" +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/functions.rst:462 +msgid "`Excel CEILING.MATH article `_" +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/functions.rst:463 +msgid "CEILING.PRECISE(number, [significance])" +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/functions.rst:464 +msgid "`Excel CEILING.PRECISE article `_" +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/functions.rst:465 +msgid "COS(angle)" +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/functions.rst:466 +msgid "`Excel COS article `_" +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/functions.rst:467 +msgid "COSH(value)" +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/functions.rst:468 +msgid "`Excel COSH article `_" +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/functions.rst:469 +msgid "COT(angle)" +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/functions.rst:470 +msgid "`Excel COT article `_" +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/functions.rst:471 +msgid "COTH(value)" +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/functions.rst:472 +msgid "`Excel COTH article `_" +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/functions.rst:473 +msgid "COUNTBLANK(value1, [value2, ...])" +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/functions.rst:474 +msgid "`Excel COUNTBLANK article `_" +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/functions.rst:475 +msgid "COUNTIF(range, criterion)" +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/functions.rst:476 +msgid "`Excel COUNTIF article `_" +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/functions.rst:477 +msgid "COUNTIFS(criteria_range1, criterion1, [criteria_range2, ...], [criterion2, ...])" +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/functions.rst:478 +msgid "`Excel COUNTIFS article `_" +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/functions.rst:479 +msgid "COUNTUNIQUE(value1, [value2, ...])" +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/functions.rst:480 +msgid "Counts number of unique values in a range (not compatible with Excel)" +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/functions.rst:481 +msgid "COUNTUNIQUEIFS(range, criteria_range1, criterion1, [criteria_range2, ...], [criterion2, ...])" +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/functions.rst:482 +msgid "Counts number of unique values in a range, filtered by a set of criteria (not compatible with Excel)" +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/functions.rst:483 +msgid "CSC(angle)" +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/functions.rst:484 +msgid "`Excel CSC article `_" +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/functions.rst:485 +msgid "CSCH(value)" +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/functions.rst:486 +msgid "`Excel CSCH article `_" +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/functions.rst:487 +msgid "DECIMAL(value, base)" +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/functions.rst:488 +msgid "`Excel DECIMAL article `_" +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/functions.rst:489 +msgid "DEGREES(angle)" +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/functions.rst:490 +msgid "`Excel DEGREES article `_" +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/functions.rst:491 +msgid "EXP(value)" +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/functions.rst:492 +msgid "`Excel EXP article `_" +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/functions.rst:493 +msgid "FLOOR(value, [factor])" +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/functions.rst:494 +msgid "`Excel FLOOR article `_" +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/functions.rst:495 +msgid "FLOOR.MATH(number, [significance], [mode])" +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/functions.rst:496 +msgid "`Excel FLOOR.MATH article `_" +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/functions.rst:497 +msgid "FLOOR.PRECISE(number, [significance])" +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/functions.rst:498 +msgid "`Excel FLOOR.PRECISE article `_" +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/functions.rst:499 +msgid "INT(value)" +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/functions.rst:500 +msgid "`Excel INT article `_" +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/functions.rst:501 +msgid "ISEVEN(value)" +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/functions.rst:502 +msgid "`Excel ISEVEN article `_" +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/functions.rst:503 +msgid "ISO.CEILING(number, [significance])" +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/functions.rst:504 +msgid "`Excel ISO.CEILING article `_" +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/functions.rst:505 +msgid "ISODD(value)" +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/functions.rst:506 +msgid "`Excel ISODD article `_" +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/functions.rst:507 +msgid "LN(value)" +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/functions.rst:508 +msgid "`Excel LN article `_" +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/functions.rst:509 +msgid "MOD(dividend, divisor)" +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/functions.rst:510 +msgid "`Excel MOD article `_" +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/functions.rst:511 +msgid "MUNIT(dimension)" +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/functions.rst:512 +msgid "`Excel MUNIT article `_" +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/functions.rst:513 +msgid "ODD(value)" +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/functions.rst:514 +msgid "`Excel ODD article `_" +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/functions.rst:515 +msgid "PI()" +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/functions.rst:516 +msgid "`Excel PI article `_" +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/functions.rst:517 +msgid "POWER(base, exponent)" +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/functions.rst:518 +msgid "`Excel POWER article `_" +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/functions.rst:519 +msgid "PRODUCT(factor1, [factor2, ...])" +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/functions.rst:520 +msgid "`Excel PRODUCT article `_" +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/functions.rst:521 +msgid "RAND()" +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/functions.rst:522 +msgid "`Excel RAND article `_" +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/functions.rst:523 +msgid "RANDARRAY([rows], [columns], [min], [max], [whole_number])" +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/functions.rst:524 +msgid "`Excel RANDARRAY article `_" +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/functions.rst:525 +msgid "RANDBETWEEN(low, high)" +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/functions.rst:526 +msgid "`Excel RANDBETWEEN article `_" +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/functions.rst:527 +msgid "ROUND(value, [places])" +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/functions.rst:528 +msgid "`Excel ROUND article `_" +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/functions.rst:529 +msgid "ROUNDDOWN(value, [places])" +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/functions.rst:530 +msgid "`Excel ROUNDDOWN article `_" +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/functions.rst:531 +msgid "ROUNDUP(value, [places])" +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/functions.rst:532 +msgid "`Excel ROUNDUP article `_" +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/functions.rst:533 +msgid "SEC(angle)" +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/functions.rst:534 +msgid "`Excel SEC article `_" +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/functions.rst:535 +msgid "SECH(value)" +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/functions.rst:536 +msgid "`Excel SECH article `_" +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/functions.rst:537 +msgid "SIN(angle)" +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/functions.rst:538 +msgid "`Excel SIN article `_" +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/functions.rst:539 +msgid "SINH(value)" +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/functions.rst:540 +msgid "`Excel SINH article `_" +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/functions.rst:541 +msgid "SQRT(value)" +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/functions.rst:542 +msgid "`Excel SQRT article `_" +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/functions.rst:543 +msgid "SUM(value1, [value2, ...])" +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/functions.rst:544 +msgid "`Excel SUM article `_" +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/functions.rst:545 +msgid "SUMIF(criteria_range, criterion, [sum_range])" +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/functions.rst:546 +msgid "`Excel SUMIF article `_" +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/functions.rst:547 +msgid "SUMIFS(sum_range, criteria_range1, criterion1, [criteria_range2, ...], [criterion2, ...])" +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/functions.rst:548 +msgid "`Excel SUMIFS article `_" +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/functions.rst:549 +msgid "TAN(angle)" +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/functions.rst:550 +msgid "`Excel TAN article `_" +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/functions.rst:551 +msgid "TANH(value)" +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/functions.rst:552 +msgid "`Excel TANH article `_" +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/functions.rst:553 +msgid "TRUNC(value, [places])" +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/functions.rst:554 +msgid "`Excel TRUNC article `_" +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/functions.rst:559 +msgid "Misc" +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/functions.rst:567 +msgid "FORMAT.LARGE.NUMBER(value, [unit])" +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/functions.rst:568 +msgid "Apply a large number format (not compatible with Excel)" +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/functions.rst:573 +msgid "Odoo" +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/functions.rst:581 +msgid "ODOO.CREDIT(account_codes, date_range, [offset], [company_id], [include_unposted])" +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/functions.rst:582 +msgid "Get the total credit for the specified account(s) and period (not compatible with Excel)" +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/functions.rst:583 +msgid "ODOO.DEBIT(account_codes, date_range, [offset], [company_id], [include_unposted])" +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/functions.rst:584 +msgid "Get the total debit for the specified account(s) and period (not compatible with Excel)" +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/functions.rst:585 +msgid "ODOO.BALANCE(account_codes, date_range, [offset], [company_id], [include_unposted])" +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/functions.rst:586 +msgid "Get the total balance for the specified account(s) and period (not compatible with Excel)" +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/functions.rst:587 +msgid "ODOO.FISCALYEAR.START(day, [company_id])" +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/functions.rst:588 +msgid "Returns the starting date of the fiscal year encompassing the provided date (not compatible with Excel)" +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/functions.rst:589 +msgid "ODOO.FISCALYEAR.END(day, [company_id])" +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/functions.rst:590 +msgid "Returns the ending date of the fiscal year encompassing the provided date (not compatible with Excel)" +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/functions.rst:591 +msgid "ODOO.ACCOUNT.GROUP(type)" +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/functions.rst:592 +msgid "Returns the account ids of a given group (not compatible with Excel)" +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/functions.rst:593 +msgid "ODOO.CURRENCY.RATE(currency_from, currency_to, [date])" +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/functions.rst:594 +msgid "This function takes in two currency codes as arguments, and returns the exchange rate from the first currency to the second as float (not compatible with Excel)" +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/functions.rst:595 +msgid "ODOO.LIST(list_id, index, field_name)" +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/functions.rst:596 +msgid "Get the value from a list (not compatible with Excel)" +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/functions.rst:597 +msgid "ODOO.LIST.HEADER(list_id, field_name)" +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/functions.rst:598 +msgid "Get the header of a list (not compatible with Excel)" +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/functions.rst:599 +msgid "ODOO.FILTER.VALUE(filter_name)" +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/functions.rst:600 +msgid "Return the current value of a spreadsheet filter (not compatible with Excel)" +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/functions.rst:601 +msgid "ODOO.PIVOT(pivot_id, measure_name, [domain_field_name, ...], [domain_value, ...])" +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/functions.rst:602 +msgid "Get the value from a pivot (not compatible with Excel)" +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/functions.rst:603 +msgid "ODOO.PIVOT.HEADER(pivot_id, [domain_field_name, ...], [domain_value, ...])" +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/functions.rst:604 +msgid "Get the header of a pivot (not compatible with Excel)" +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/functions.rst:605 +msgid "ODOO.PIVOT.TABLE(pivot_id, [row_count], [include_total], [include_column_titles])" +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/functions.rst:606 +msgid "Get a pivot table (not compatible with Excel)" +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/functions.rst:611 +msgid "Operators" +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/functions.rst:619 +msgid "ADD(value1, value2)" +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/functions.rst:620 +msgid "Sum of two numbers (not compatible with Excel)" +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/functions.rst:621 +msgid "CONCAT(value1, value2)" +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/functions.rst:622 +msgid "`Excel CONCAT article `_" +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/functions.rst:623 +msgid "DIVIDE(dividend, divisor)" +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/functions.rst:624 +msgid "One number divided by another (not compatible with Excel)" +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/functions.rst:625 +msgid "EQ(value1, value2)" +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/functions.rst:626 +msgid "Equal (not compatible with Excel)" +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/functions.rst:627 +msgid "GT(value1, value2)" +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/functions.rst:628 +msgid "Strictly greater than (not compatible with Excel)" +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/functions.rst:629 +msgid "GTE(value1, value2)" +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/functions.rst:630 +msgid "Greater than or equal to (not compatible with Excel)" +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/functions.rst:631 +msgid "LT(value1, value2)" +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/functions.rst:632 +msgid "Less than (not compatible with Excel)" +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/functions.rst:633 +msgid "LTE(value1, value2)" +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/functions.rst:634 +msgid "Less than or equal to (not compatible with Excel)" +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/functions.rst:635 +msgid "MINUS(value1, value2)" +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/functions.rst:636 +msgid "Difference of two numbers (not compatible with Excel)" +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/functions.rst:637 +msgid "MULTIPLY(factor1, factor2)" +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/functions.rst:638 +msgid "Product of two numbers (not compatible with Excel)" +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/functions.rst:639 +msgid "NE(value1, value2)" +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/functions.rst:640 +msgid "Not equal (not compatible with Excel)" +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/functions.rst:641 +msgid "POW(base, exponent)" +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/functions.rst:642 +msgid "A number raised to a power (not compatible with Excel)" +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/functions.rst:643 +msgid "UMINUS(value)" +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/functions.rst:644 +msgid "A number with the sign reversed (not compatible with Excel)" +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/functions.rst:645 +msgid "UNARY.PERCENT(percentage)" +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/functions.rst:646 +msgid "Value interpreted as a percentage (not compatible with Excel)" +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/functions.rst:647 +msgid "UPLUS(value)" +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/functions.rst:648 +msgid "A specified number, unchanged (not compatible with Excel)" +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/functions.rst:653 +msgid "Statistical" +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/functions.rst:661 +msgid "AVEDEV(value1, [value2, ...])" +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/functions.rst:662 +msgid "`Excel AVEDEV article `_" +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/functions.rst:663 +msgid "AVERAGE(value1, [value2, ...])" +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/functions.rst:664 +msgid "`Excel AVERAGE article `_" +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/functions.rst:665 +msgid "AVERAGE.WEIGHTED(values, weights, [additional_values, ...], [additional_weights, ...])" +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/functions.rst:666 +msgid "Weighted average (not compatible with Excel)" +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/functions.rst:667 +msgid "AVERAGEA(value1, [value2, ...])" +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/functions.rst:668 +msgid "`Excel AVERAGEA article `_" +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/functions.rst:669 +msgid "AVERAGEIF(criteria_range, criterion, [average_range])" +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/functions.rst:670 +msgid "`Excel AVERAGEIF article `_" +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/functions.rst:671 +msgid "AVERAGEIFS(average_range, criteria_range1, criterion1, [criteria_range2, ...], [criterion2, ...])" +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/functions.rst:672 +msgid "`Excel AVERAGEIFS article `_" +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/functions.rst:673 +msgid "CORREL(data_y, data_x)" +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/functions.rst:674 +msgid "`Excel CORREL article `_" +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/functions.rst:675 +msgid "COUNT(value1, [value2, ...])" +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/functions.rst:676 +msgid "`Excel COUNT article `_" +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/functions.rst:677 +msgid "COUNTA(value1, [value2, ...])" +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/functions.rst:678 +msgid "`Excel COUNTA article `_" +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/functions.rst:679 +msgid "COVAR(data_y, data_x)" +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/functions.rst:680 +msgid "`Excel COVAR article `_" +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/functions.rst:681 +msgid "COVARIANCE.P(data_y, data_x)" +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/functions.rst:682 +msgid "`Excel COVARIANCE.P article `_" +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/functions.rst:683 +msgid "COVARIANCE.S(data_y, data_x)" +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/functions.rst:684 +msgid "`Excel COVARIANCE.S article `_" +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/functions.rst:685 +msgid "FORECAST(x, data_y, data_x)" +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/functions.rst:686 +msgid "`Excel FORECAST article `_" +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/functions.rst:687 +msgid "GROWTH(known_data_y, [known_data_x], [new_data_x], [b])" +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/functions.rst:688 +msgid "Fits points to exponential growth trend (not compatible with Excel)" +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/functions.rst:689 +msgid "INTERCEPT(data_y, data_x)" +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/functions.rst:690 +msgid "`Excel INTERCEPT article `_" +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/functions.rst:691 +msgid "LARGE(data, n)" +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/functions.rst:692 +msgid "`Excel LARGE article `_" +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/functions.rst:693 +msgid "LINEST(data_y, [data_x], [calculate_b], [verbose])" +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/functions.rst:694 +msgid "`Excel LINEST article `_" +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/functions.rst:695 +msgid "LOGEST(data_y, [data_x], [calculate_b], [verbose])" +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/functions.rst:696 +msgid "`Excel LOGEST article `_" +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/functions.rst:697 +msgid "MATTHEWS(data_x, data_y)" +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/functions.rst:698 +msgid "Compute the Matthews correlation coefficient of a dataset (not compatible with Excel)" +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/functions.rst:699 +msgid "MAX(value1, [value2, ...])" +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/functions.rst:700 +msgid "`Excel MAX article `_" +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/functions.rst:701 +msgid "MAXA(value1, [value2, ...])" +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/functions.rst:702 +msgid "`Excel MAXA article `_" +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/functions.rst:703 +msgid "MAXIFS(range, criteria_range1, criterion1, [criteria_range2, ...], [criterion2, ...])" +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/functions.rst:704 +msgid "`Excel MAXIFS article `_" +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/functions.rst:705 +msgid "MEDIAN(value1, [value2, ...])" +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/functions.rst:706 +msgid "`Excel MEDIAN article `_" +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/functions.rst:707 +msgid "MIN(value1, [value2, ...])" +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/functions.rst:708 +msgid "`Excel MIN article `_" +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/functions.rst:709 +msgid "MINA(value1, [value2, ...])" +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/functions.rst:710 +msgid "`Excel MINA article `_" +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/functions.rst:711 +msgid "MINIFS(range, criteria_range1, criterion1, [criteria_range2, ...], [criterion2, ...])" +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/functions.rst:712 +msgid "`Excel MINIFS article `_" +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/functions.rst:713 +msgid "PEARSON(data_y, data_x)" +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/functions.rst:714 +msgid "`Excel PEARSON article `_" +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/functions.rst:715 +msgid "PERCENTILE(data, percentile)" +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/functions.rst:716 +msgid "`Excel PERCENTILE article `_" +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/functions.rst:717 +msgid "PERCENTILE.EXC(data, percentile)" +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/functions.rst:718 +msgid "`Excel PERCENTILE.EXC article `_" +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/functions.rst:719 +msgid "PERCENTILE.INC(data, percentile)" +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/functions.rst:720 +msgid "`Excel PERCENTILE.INC article `_" +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/functions.rst:721 +msgid "POLYFIT.COEFFS(data_y, data_x, order, [intercept])" +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/functions.rst:722 +msgid "Compute the coefficients of polynomial regression of the dataset (not compatible with Excel)" +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/functions.rst:723 +msgid "POLYFIT.FORECAST(x, data_y, data_x, order, [intercept])" +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/functions.rst:724 +msgid "Predict value by computing a polynomial regression of the dataset (not compatible with Excel)" +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/functions.rst:725 +msgid "QUARTILE(data, quartile_number)" +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/functions.rst:726 +msgid "`Excel QUARTILE article `_" +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/functions.rst:727 +msgid "QUARTILE.EXC(data, quartile_number)" +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/functions.rst:728 +msgid "`Excel QUARTILE.EXC article `_" +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/functions.rst:729 +msgid "QUARTILE.INC(data, quartile_number)" +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/functions.rst:730 +msgid "`Excel QUARTILE.INC article `_" +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/functions.rst:731 +msgid "RANK(value, data, [is_ascending])" +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/functions.rst:732 +msgid "`Excel RANK article `_" +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/functions.rst:733 +msgid "RSQ(data_y, data_x)" +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/functions.rst:734 +msgid "`Excel RSQ article `_" +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/functions.rst:735 +msgid "SMALL(data, n)" +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/functions.rst:736 +msgid "`Excel SMALL article `_" +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/functions.rst:737 +msgid "SLOPE(data_y, data_x)" +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/functions.rst:738 +msgid "`Excel SLOPE article `_" +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/functions.rst:739 +msgid "SPEARMAN(data_y, data_x)" +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/functions.rst:740 +msgid "Compute the Spearman rank correlation coefficient of a dataset (not compatible with Excel)" +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/functions.rst:741 +msgid "STDEV(value1, [value2, ...])" +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/functions.rst:742 +msgid "`Excel STDEV article `_" +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/functions.rst:743 +msgid "STDEV.P(value1, [value2, ...])" +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/functions.rst:744 +msgid "`Excel STDEV.P article `_" +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/functions.rst:745 +msgid "STDEV.S(value1, [value2, ...])" +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/functions.rst:746 +msgid "`Excel STDEV.S article `_" +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/functions.rst:747 +msgid "STDEVA(value1, [value2, ...])" +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/functions.rst:748 +msgid "`Excel STDEVA article `_" +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/functions.rst:749 +msgid "STDEVP(value1, [value2, ...])" +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/functions.rst:750 +msgid "`Excel STDEVP article `_" +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/functions.rst:751 +msgid "STDEVPA(value1, [value2, ...])" +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/functions.rst:752 +msgid "`Excel STDEVPA article `_" +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/functions.rst:753 +msgid "STEYX(data_y, data_x)" +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/functions.rst:754 +msgid "`Excel STEYX article `_" +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/functions.rst:755 +msgid "TREND(known_data_y, [known_data_x], [new_data_x], [b])" +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/functions.rst:756 +msgid "Fits points to linear trend derived via least-squares (not compatible with Excel)" +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/functions.rst:757 +msgid "VAR(value1, [value2, ...])" +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/functions.rst:758 +msgid "`Excel VAR article `_" +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/functions.rst:759 +msgid "VAR.P(value1, [value2, ...])" +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/functions.rst:760 +msgid "`Excel VAR.P article `_" +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/functions.rst:761 +msgid "VAR.S(value1, [value2, ...])" +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/functions.rst:762 +msgid "`Excel VAR.S article `_" +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/functions.rst:763 +msgid "VARA(value1, [value2, ...])" +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/functions.rst:764 +msgid "`Excel VARA article `_" +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/functions.rst:765 +msgid "VARP(value1, [value2, ...])" +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/functions.rst:766 +msgid "`Excel VARP article `_" +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/functions.rst:767 +msgid "VARPA(value1, [value2, ...])" +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/functions.rst:768 +msgid "`Excel VARPA article `_" +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/functions.rst:773 +#: ../../content/applications/productivity/whatsapp.rst:584 +msgid "Text" +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/functions.rst:781 +msgid "CHAR(table_number)" +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/functions.rst:782 +msgid "`Excel CHAR article `_" +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/functions.rst:783 +msgid "CLEAN(text)" +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/functions.rst:784 +msgid "`Excel CLEAN article `_" +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/functions.rst:785 +msgid "CONCATENATE(string1, [string2, ...])" +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/functions.rst:786 +msgid "`Excel CONCATENATE article `_" +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/functions.rst:787 +msgid "EXACT(string1, string2)" +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/functions.rst:788 +msgid "`Excel EXACT article `_" +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/functions.rst:789 +msgid "FIND(search_for, text_to_search, [starting_at])" +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/functions.rst:790 +msgid "`Excel FIND article `_" +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/functions.rst:791 +msgid "JOIN(delimiter, value_or_array1, [value_or_array2, ...])" +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/functions.rst:792 +msgid "Concatenates elements of arrays with delimiter (not compatible with Excel)" +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/functions.rst:793 +msgid "LEFT(text, [number_of_characters])" +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/functions.rst:794 +msgid "`Excel LEFT article `_" +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/functions.rst:795 +msgid "LEN(text)" +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/functions.rst:796 +msgid "`Excel LEN article `_" +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/functions.rst:797 +msgid "LOWER(text)" +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/functions.rst:798 +msgid "`Excel LOWER article `_" +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/functions.rst:799 +msgid "MID(text, starting_at, extract_length)" +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/functions.rst:800 +msgid "`Excel MID article `_" +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/functions.rst:801 +msgid "PROPER(text_to_capitalize)" +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/functions.rst:802 +msgid "`Excel PROPER article `_" +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/functions.rst:803 +msgid "REPLACE(text, position, length, new_text)" +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/functions.rst:804 +msgid "`Excel REPLACE article `_" +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/functions.rst:805 +msgid "RIGHT(text, [number_of_characters])" +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/functions.rst:806 +msgid "`Excel RIGHT article `_" +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/functions.rst:807 +msgid "SEARCH(search_for, text_to_search, [starting_at])" +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/functions.rst:808 +msgid "`Excel SEARCH article `_" +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/functions.rst:809 +msgid "SPLIT(text, delimiter, [split_by_each], [remove_empty_text])" +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/functions.rst:810 +msgid "`Excel TEXTSPLIT article `_" +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/functions.rst:811 +msgid "SUBSTITUTE(text_to_search, search_for, replace_with, [occurrence_number])" +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/functions.rst:812 +msgid "`Excel SUBSTITUTE article `_" +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/functions.rst:813 +msgid "TEXT(number, format)" +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/functions.rst:814 +msgid "`Excel TEXT article `_" +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/functions.rst:815 +msgid "TEXTJOIN(delimiter, ignore_empty, text1, [text2, ...])" +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/functions.rst:816 +msgid "`Excel TEXTJOIN article `_" +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/functions.rst:817 +msgid "TRIM(text)" +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/functions.rst:818 +msgid "`Excel TRIM article `_" +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/functions.rst:819 +msgid "UPPER(text)" +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/functions.rst:820 +msgid "`Excel UPPER article `_" +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/functions.rst:825 +msgid "Web" +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/functions.rst:833 +msgid "HYPERLINK(url, [link_label])" +msgstr "" + +#: ../../content/applications/productivity/spreadsheet/functions.rst:834 +msgid "`Excel HYPERLINK article `_" +msgstr "" + #: ../../content/applications/productivity/spreadsheet/insert.rst:3 msgid "Link Odoo data" msgstr "" @@ -2745,7 +6089,7 @@ msgid "VoIP services in Odoo with Axivox" msgstr "" #: ../../content/applications/productivity/voip/axivox/axivox_config.rst:6 -#: ../../content/applications/productivity/voip/onsip.rst:6 +#: ../../content/applications/productivity/voip/onsip.rst:20 msgid "Introduction" msgstr "" @@ -4371,12 +7715,12 @@ msgid "In the :guilabel:`GSM number` field, enter an alternative number at which msgstr "" #: ../../content/applications/productivity/voip/axivox/manage_users.rst:102 -#: ../../content/applications/productivity/voip/onsip.rst:134 +#: ../../content/applications/productivity/voip/onsip.rst:148 msgid "A country code is a locator code that allows access to the desired country's phone system. The country code is dialed first, prior to the target number. Each country in the world has its own specific country code." msgstr "" #: ../../content/applications/productivity/voip/axivox/manage_users.rst:106 -#: ../../content/applications/productivity/voip/onsip.rst:145 +#: ../../content/applications/productivity/voip/onsip.rst:159 msgid "For a list of comprehensive country codes, visit: `https://countrycode.org `_." msgstr "" @@ -5284,23 +8628,39 @@ msgstr "" msgid "Use VoIP services in Odoo with OnSIP" msgstr "" -#: ../../content/applications/productivity/voip/onsip.rst:8 +#: ../../content/applications/productivity/voip/onsip.rst:6 +msgid "OnSIP :abbr:`VoIP (voice over internet protocol)` services are only available in the **United States** (US). OnSIP :abbr:`VoIP (voice over internet protocol)` services are widely available in the lower-48, contiguous United States. In Alaska or Hawaii, charges for service can be higher." +msgstr "" + +#: ../../content/applications/productivity/voip/onsip.rst:10 +msgid "Additionally, a :abbr:`US (United States)` billing address, and :abbr:`US (United States)` credit card are required to use the service." +msgstr "" + +#: ../../content/applications/productivity/voip/onsip.rst:13 +msgid "Before setting up an account with OnSIP, the business will need to make sure the business telephone numbers are portable to OnSIP." +msgstr "" + +#: ../../content/applications/productivity/voip/onsip.rst:16 +msgid "OnSIP makes every attempt to work with all telephone service providers. However, certain local or regional guidelines may preclude the company's current provider from releasing the number." +msgstr "" + +#: ../../content/applications/productivity/voip/onsip.rst:22 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 +#: ../../content/applications/productivity/voip/onsip.rst:26 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 +#: ../../content/applications/productivity/voip/onsip.rst:29 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 +#: ../../content/applications/productivity/voip/onsip.rst:35 msgid "To configure the Odoo database to connect to OnSIP services, first navigate to the :menuselection:`Apps application` from the main Odoo dashboard. Then, remove the default `Apps` filter from the :guilabel:`Search...` bar, and search for `OnSIP`." msgstr "" -#: ../../content/applications/productivity/voip/onsip.rst:25 +#: ../../content/applications/productivity/voip/onsip.rst:39 msgid "Next, activate the :guilabel:`VOIP OnSIP` module." msgstr "" @@ -5308,23 +8668,23 @@ msgstr "" msgid "View of OnSIP app in the app search results." msgstr "" -#: ../../content/applications/productivity/voip/onsip.rst:32 +#: ../../content/applications/productivity/voip/onsip.rst:46 msgid "Odoo VoIP setting" msgstr "" -#: ../../content/applications/productivity/voip/onsip.rst:34 +#: ../../content/applications/productivity/voip/onsip.rst:48 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 +#: ../../content/applications/productivity/voip/onsip.rst:52 msgid ":guilabel:`OnSIP Domain`: the domain that was assigned when creating an account on `OnSIP `_." msgstr "" -#: ../../content/applications/productivity/voip/onsip.rst:40 +#: ../../content/applications/productivity/voip/onsip.rst:54 msgid ":guilabel:`WebSocket`: `wss://edge.sip.onsip.com`" msgstr "" -#: ../../content/applications/productivity/voip/onsip.rst:41 +#: ../../content/applications/productivity/voip/onsip.rst:55 msgid ":guilabel:`VoIP Environment`: :guilabel:`Production`" msgstr "" @@ -5332,15 +8692,15 @@ msgstr "" msgid "VoIP configuration settings in Odoo Settings app." msgstr "" -#: ../../content/applications/productivity/voip/onsip.rst:48 +#: ../../content/applications/productivity/voip/onsip.rst:62 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 +#: ../../content/applications/productivity/voip/onsip.rst:65 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 +#: ../../content/applications/productivity/voip/onsip.rst:68 msgid "Click on the :guilabel:`Phone Settings` tab to reveal OnSIP configuration credentials (first column)." msgstr "" @@ -5349,43 +8709,43 @@ msgid "Domain setting revealed (highlighted) on administrative panel of OnSIP ma "console." msgstr "" -#: ../../content/applications/productivity/voip/onsip.rst:63 +#: ../../content/applications/productivity/voip/onsip.rst:77 msgid "Odoo user setting" msgstr "" -#: ../../content/applications/productivity/voip/onsip.rst:65 +#: ../../content/applications/productivity/voip/onsip.rst:79 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 +#: ../../content/applications/productivity/voip/onsip.rst:82 msgid "To do that, navigate to :menuselection:`Settings app --> Manage Users --> Select the User`." msgstr "" -#: ../../content/applications/productivity/voip/onsip.rst:70 +#: ../../content/applications/productivity/voip/onsip.rst:84 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 +#: ../../content/applications/productivity/voip/onsip.rst:87 msgid "In this section, fill in the fields with OnSIP credentials." msgstr "" -#: ../../content/applications/productivity/voip/onsip.rst:75 +#: ../../content/applications/productivity/voip/onsip.rst:89 msgid "Fill in the following fields with the associated credentials listed below:" msgstr "" -#: ../../content/applications/productivity/voip/onsip.rst:77 +#: ../../content/applications/productivity/voip/onsip.rst:91 msgid ":guilabel:`Voip Username` = OnSIP :guilabel:`Username`" msgstr "" -#: ../../content/applications/productivity/voip/onsip.rst:78 +#: ../../content/applications/productivity/voip/onsip.rst:92 msgid ":guilabel:`OnSIP Auth Username` = OnSIP :guilabel:`Auth Username`" msgstr "" -#: ../../content/applications/productivity/voip/onsip.rst:79 +#: ../../content/applications/productivity/voip/onsip.rst:93 msgid ":guilabel:`VoIP Secret` = OnSIP :guilabel:`SIP Password`" msgstr "" -#: ../../content/applications/productivity/voip/onsip.rst:80 +#: ../../content/applications/productivity/voip/onsip.rst:94 msgid ":guilabel:`External Device Number` = OnSIP :guilabel:`Ext.` (extension without the `x`)" msgstr "" @@ -5394,31 +8754,31 @@ msgid "OnSIP user credentials with username, auth username, SIP password, and ex "highlighted." msgstr "" -#: ../../content/applications/productivity/voip/onsip.rst:88 +#: ../../content/applications/productivity/voip/onsip.rst:102 msgid "The OnSIP extension can be found in the *User* banner line above the tabs." msgstr "" -#: ../../content/applications/productivity/voip/onsip.rst:90 +#: ../../content/applications/productivity/voip/onsip.rst:104 msgid "When these steps are complete, navigate away from the user form in Odoo to save the configurations." msgstr "" -#: ../../content/applications/productivity/voip/onsip.rst:92 +#: ../../content/applications/productivity/voip/onsip.rst:106 msgid "Once saved, Odoo users can make phone calls by clicking the :guilabel:`☎️ (phone)` icon in the top-right corner of Odoo." msgstr "" -#: ../../content/applications/productivity/voip/onsip.rst:96 +#: ../../content/applications/productivity/voip/onsip.rst:110 msgid "Additional setup and troubleshooting steps can be found on `OnSIP's knowledge base `_." msgstr "" -#: ../../content/applications/productivity/voip/onsip.rst:100 +#: ../../content/applications/productivity/voip/onsip.rst:114 msgid "Incoming calls" msgstr "" -#: ../../content/applications/productivity/voip/onsip.rst:102 +#: ../../content/applications/productivity/voip/onsip.rst:116 msgid "The Odoo database also receives incoming calls that produce pop-up windows in Odoo. When those call pop-up windows appear, click the green :guilabel:`📞 (phone)` icon to answer the call." msgstr "" -#: ../../content/applications/productivity/voip/onsip.rst:105 +#: ../../content/applications/productivity/voip/onsip.rst:119 msgid "To ignore the call, click the red :guilabel:`📞 (phone)` icon." msgstr "" @@ -5426,20 +8786,20 @@ msgstr "" msgid "Incoming call shown in the Odoo VoIP widget." msgstr "" -#: ../../content/applications/productivity/voip/onsip.rst:113 +#: ../../content/applications/productivity/voip/onsip.rst:127 msgid ":doc:`voip_widget`" msgstr "" -#: ../../content/applications/productivity/voip/onsip.rst:116 +#: ../../content/applications/productivity/voip/onsip.rst:130 #: ../../content/applications/productivity/voip/voip_widget.rst:32 msgid "Troubleshooting" msgstr "" -#: ../../content/applications/productivity/voip/onsip.rst:119 +#: ../../content/applications/productivity/voip/onsip.rst:133 msgid "Missing parameters" msgstr "" -#: ../../content/applications/productivity/voip/onsip.rst:121 +#: ../../content/applications/productivity/voip/onsip.rst:135 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 "" @@ -5447,15 +8807,15 @@ msgstr "" msgid "Missing parameter message in the Odoo VoIP widget." msgstr "" -#: ../../content/applications/productivity/voip/onsip.rst:129 +#: ../../content/applications/productivity/voip/onsip.rst:143 msgid "Incorrect number" msgstr "" -#: ../../content/applications/productivity/voip/onsip.rst:131 +#: ../../content/applications/productivity/voip/onsip.rst:145 msgid "If an *Incorrect Number* message appears in the Odoo widget, make sure to use the international format for the number. This means leading with the international country code." msgstr "" -#: ../../content/applications/productivity/voip/onsip.rst:138 +#: ../../content/applications/productivity/voip/onsip.rst:152 msgid "For example, `16505555555` (where `1` is the international prefix for the United States)." msgstr "" @@ -5463,23 +8823,23 @@ msgstr "" msgid "Incorrect number message populated in the Odoo VoIP widget." msgstr "" -#: ../../content/applications/productivity/voip/onsip.rst:149 +#: ../../content/applications/productivity/voip/onsip.rst:163 msgid "OnSIP on mobile phone" msgstr "" -#: ../../content/applications/productivity/voip/onsip.rst:151 +#: ../../content/applications/productivity/voip/onsip.rst:165 msgid "In order to make and receive phone calls when the user is not in front of Odoo on their computer, a softphone app on a mobile phone can be used in parallel with Odoo *VoIP*." msgstr "" -#: ../../content/applications/productivity/voip/onsip.rst:154 +#: ../../content/applications/productivity/voip/onsip.rst:168 msgid "This is useful for convenient, on-the-go calls, and to make sure incoming calls are heard. Any SIP softphone will work." msgstr "" -#: ../../content/applications/productivity/voip/onsip.rst:158 +#: ../../content/applications/productivity/voip/onsip.rst:172 msgid ":doc:`devices_integrations`" msgstr "" -#: ../../content/applications/productivity/voip/onsip.rst:159 +#: ../../content/applications/productivity/voip/onsip.rst:173 msgid "`OnSIP App Download `_" msgstr "" @@ -5800,10 +9160,6 @@ msgstr "" msgid "A search feature is also available in the upper-right side of the widget, represented by a :guilabel:`🔍 (magnifying glass)` icon." msgstr "" -#: ../../content/applications/productivity/whatsapp.rst:3 -msgid "WhatsApp" -msgstr "" - #: ../../content/applications/productivity/whatsapp.rst:5 msgid "**WhatsApp** is an instant messaging and voice-over-IP app that allows users to send messages, make calls, and share content. Businesses can use `WhatsApp Business `_ to communicate with their customers by text, send documents and provide support." msgstr "" @@ -6481,10 +9837,6 @@ msgstr "" msgid "The available :guilabel:`Header types` are as follows:" msgstr "" -#: ../../content/applications/productivity/whatsapp.rst:584 -msgid "Text" -msgstr "" - #: ../../content/applications/productivity/whatsapp.rst:585 msgid "Image" msgstr "" diff --git a/locale/sources/sales.pot b/locale/sources/sales.pot index 4c0f10f64..f5a444bbd 100644 --- a/locale/sources/sales.pot +++ b/locale/sources/sales.pot @@ -8,7 +8,7 @@ msgid "" msgstr "" "Project-Id-Version: Odoo 17.0\n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2024-03-25 16:01+0000\n" +"POT-Creation-Date: 2024-04-30 09:16+0000\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME \n" "Language-Team: LANGUAGE \n" @@ -42,30 +42,30 @@ msgid "Convert leads into opportunities" msgstr "" #: ../../content/applications/sales/crm/acquire_leads/convert.rst:5 -msgid "*Leads* act as qualifying steps before an opportunity is created. This provides additional time before a potential opportunity is assigned to a sales person." +msgid "*Leads* act as a qualifying step before an opportunity is created. This provides additional time to review its potential, and gauge its viability, before the opportunity is assigned to a salesperson." msgstr "" #: ../../content/applications/sales/crm/acquire_leads/convert.rst:9 #: ../../content/applications/sales/crm/acquire_leads/lead_mining.rst:10 -#: ../../content/applications/sales/crm/optimize/gamification.rst:11 -#: ../../content/applications/sales/crm/optimize/partner_autocomplete.rst:9 +#: ../../content/applications/sales/crm/optimize/gamification.rst:10 +#: ../../content/applications/sales/crm/optimize/partner_autocomplete.rst:27 #: ../../content/applications/sales/crm/track_leads/lead_scoring.rst:44 -#: ../../content/applications/sales/crm/track_leads/prospect_visits.rst:12 #: ../../content/applications/sales/point_of_sale/combos.rst:16 #: ../../content/applications/sales/point_of_sale/configuration.rst:6 #: ../../content/applications/sales/point_of_sale/employee_login.rst:13 #: ../../content/applications/sales/point_of_sale/payment_methods/terminals.rst:13 -#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/adyen.rst:13 -#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/ingenico.rst:12 +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/adyen.rst:20 +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/ingenico.rst:15 #: ../../content/applications/sales/point_of_sale/payment_methods/terminals/six.rst:14 -#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/stripe.rst:12 +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/stripe.rst:19 #: ../../content/applications/sales/point_of_sale/payment_methods/terminals/vantiv.rst:17 -#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/worldline.rst:12 +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/worldline.rst:16 #: ../../content/applications/sales/point_of_sale/pricing/cash_rounding.rst:17 +#: ../../content/applications/sales/point_of_sale/pricing/electronic_labels.rst:16 #: ../../content/applications/sales/point_of_sale/pricing/fiscal_position.rst:16 #: ../../content/applications/sales/point_of_sale/pricing/loyalty.rst:9 #: ../../content/applications/sales/point_of_sale/pricing/pricelists.rst:12 -#: ../../content/applications/sales/point_of_sale/receipts_invoices.rst:52 +#: ../../content/applications/sales/point_of_sale/receipts_invoices.rst:53 #: ../../content/applications/sales/point_of_sale/restaurant.rst:22 #: ../../content/applications/sales/point_of_sale/restaurant/bill_printing.rst:10 #: ../../content/applications/sales/point_of_sale/restaurant/floors_tables.rst:22 @@ -92,7 +92,7 @@ msgid "Leads setting on CRM configuration page." msgstr "" #: ../../content/applications/sales/crm/acquire_leads/convert.rst:18 -msgid "Activating this feature adds a new menu, :guilabel:`Leads`, to the header menu bar at the top of the screen." +msgid "Activating this feature adds a new menu option, :guilabel:`Leads`, to the header bar, located along the top of the screen." msgstr "" #: ../../content/applications/sales/crm/acquire_leads/convert.rst:-1 @@ -101,38 +101,51 @@ msgid "Leads menu on CRM application." msgstr "" #: ../../content/applications/sales/crm/acquire_leads/convert.rst:25 -msgid "Once the *Leads* setting has been activated, it applies to all sales teams by default. To turn off leads for a specific team, navigate to :menuselection:`CRM app --> Configuration --> Sales Teams`. Then, select a team from the list to open the record, and uncheck the :guilabel:`Leads` box. Once done, click :guilabel:`Save`." +msgid "Once the *Leads* setting has been activated, it applies to all sales teams by default. To turn off leads for a specific team, navigate to :menuselection:`CRM app --> Configuration --> Sales Teams`. Then, select a team from the list to open that team's configuration page. Clear the :guilabel:`Leads` checkbox, located beneath the :guilabel:`Sales Team` field, then click :guilabel:`Save`." msgstr "" -#: ../../content/applications/sales/crm/acquire_leads/convert.rst:35 +#: ../../content/applications/sales/crm/acquire_leads/convert.rst:36 msgid "Convert a lead into an opportunity" msgstr "" -#: ../../content/applications/sales/crm/acquire_leads/convert.rst:37 -msgid "To convert a lead into an *opportunity*, navigate to :menuselection:`CRM --> Leads`, and click on a :guilabel:`Lead` from the list to open it." +#: ../../content/applications/sales/crm/acquire_leads/convert.rst:38 +msgid "To convert a lead into an *opportunity*, navigate to :menuselection:`CRM app --> Leads`, and click on a lead from the list to open it." msgstr "" -#: ../../content/applications/sales/crm/acquire_leads/convert.rst:40 -msgid "In the upper-left corner of the screen, click the :guilabel:`Convert to Opportunity` button, which opens a :guilabel:`Convert to opportunity` pop-up window." +#: ../../content/applications/sales/crm/acquire_leads/convert.rst:42 +msgid "If a :guilabel:`Similar Leads` smart button appears at the top of the page for the lead, it indicates a similar lead or opportunity already exists in the database. Before converting this lead, click the smart button to confirm if the lead should be merged." +msgstr "" + +#: ../../content/applications/sales/crm/acquire_leads/convert.rst:0 +msgid "Close up of a lead with emphasis on the Similar Leads smart button." +msgstr "" + +#: ../../content/applications/sales/crm/acquire_leads/convert.rst:50 +msgid "Click the :guilabel:`Convert to Opportunity` button, located at the top-left of the page." msgstr "" #: ../../content/applications/sales/crm/acquire_leads/convert.rst:-1 msgid "Create opportunity button on a lead record." msgstr "" -#: ../../content/applications/sales/crm/acquire_leads/convert.rst:47 -msgid "On the :guilabel:`Convert to opportunity` pop-up window, in the :guilabel:`Conversion action` field, select the :guilabel:`Convert to opportunity` option." -msgstr "" - -#: ../../content/applications/sales/crm/acquire_leads/convert.rst:51 -msgid "If a lead, or an opportunity, already exists in the database for this customer, Odoo automatically suggests merging both leads/opportunities. For more information on merging leads and opportunities, see the section on how to :ref:`merge leads ` below." -msgstr "" - #: ../../content/applications/sales/crm/acquire_leads/convert.rst:56 -msgid "Then, select a :guilabel:`Salesperson` and a :guilabel:`Sales Team` to which the opportunity should be assigned." +msgid "This opens a :guilabel:`Convert to opportunity` pop-up modal. Here, in the :guilabel:`Conversion Action` field, select the :guilabel:`Convert to opportunity` option." msgstr "" -#: ../../content/applications/sales/crm/acquire_leads/convert.rst:59 +#: ../../content/applications/sales/crm/acquire_leads/convert.rst:60 +msgid "To merge this lead with an existing similar lead or opportunity, select :guilabel:`Merge with existing opportunities` in the :guilabel:`Conversion Action` field. This generates a list of the similar leads/opportunities to be merged." +msgstr "" + +#: ../../content/applications/sales/crm/acquire_leads/convert.rst:64 +#: ../../content/applications/sales/crm/pipeline/merge_similar.rst:37 +msgid "When merging, Odoo gives priority to whichever lead/opportunity was created in the system first, merging the information into the first created lead/opportunity. However, if a lead and an opportunity are being merged, the resulting record is referred to as an opportunity, regardless of which record was created first." +msgstr "" + +#: ../../content/applications/sales/crm/acquire_leads/convert.rst:69 +msgid "Then, select a :guilabel:`Salesperson` and a :guilabel:`Sales Team` to which the opportunity should be assigned. Neither field is required, though if a selection is made in the :guilabel:`Salesperson` field, the :guilabel:`Sales Team` field is populated automatically, based on the salesperson's team assignments." +msgstr "" + +#: ../../content/applications/sales/crm/acquire_leads/convert.rst:74 msgid "If the lead has already been assigned to a salesperson or a team, these fields automatically populate with that information." msgstr "" @@ -140,68 +153,32 @@ msgstr "" msgid "Create opportunity pop-up." msgstr "" -#: ../../content/applications/sales/crm/acquire_leads/convert.rst:66 +#: ../../content/applications/sales/crm/acquire_leads/convert.rst:81 msgid "Under the :guilabel:`Customer` heading, choose from the following options:" msgstr "" -#: ../../content/applications/sales/crm/acquire_leads/convert.rst:68 -msgid ":guilabel:`Create a new customer`: Choose this option to use the information in the lead to create a new customer." +#: ../../content/applications/sales/crm/acquire_leads/convert.rst:83 +msgid ":guilabel:`Create a new customer`: choose this option to use the information in the lead to create a new customer record." msgstr "" -#: ../../content/applications/sales/crm/acquire_leads/convert.rst:70 -msgid ":guilabel:`Link to an existing customer`: Choose this option, then select a customer from the resulting drop-down menu, to link this opportunity to the existing customer record." +#: ../../content/applications/sales/crm/acquire_leads/convert.rst:85 +msgid ":guilabel:`Link to an existing customer`: choose this option, then select a customer from the resulting drop-down menu, to link this opportunity to an existing customer record." msgstr "" -#: ../../content/applications/sales/crm/acquire_leads/convert.rst:72 -msgid ":guilabel:`Do not link to a customer`: Choose this option to convert the lead, but not link it to a new or existing customer." -msgstr "" - -#: ../../content/applications/sales/crm/acquire_leads/convert.rst:75 -msgid "Lastly, when all configurations are complete, click :guilabel:`Create Opportunity`." -msgstr "" - -#: ../../content/applications/sales/crm/acquire_leads/convert.rst:80 -msgid "Merge leads and opportunities" -msgstr "" - -#: ../../content/applications/sales/crm/acquire_leads/convert.rst:82 -msgid "Odoo automatically detects similar leads and opportunities by comparing the email addresses of the associated contacts. If a similar lead/opportunity is found, a :guilabel:`Similar Lead` smart button appears at the top of the lead/opportunity record." -msgstr "" - -#: ../../content/applications/sales/crm/acquire_leads/convert.rst:-1 -msgid "Similar leads smart button." +#: ../../content/applications/sales/crm/acquire_leads/convert.rst:87 +msgid ":guilabel:`Do not link to a customer`: choose this option to convert the lead, but not link it to a new or existing customer." msgstr "" #: ../../content/applications/sales/crm/acquire_leads/convert.rst:90 -msgid "To compare the details of the similar leads/opportunities, click the :guilabel:`Similar Leads` button. This opens a kanban view with only the similar leads/opportunities. Click into each card to view the details for each lead/opportunity, and confirm if they should be merged." +msgid "Lastly, when all configurations are complete, click :guilabel:`Create Opportunity`." +msgstr "" + +#: ../../content/applications/sales/crm/acquire_leads/convert.rst:92 +msgid "To view the newly created opportunity, navigate to :menuselection:`CRM app --> My Pipeline`." msgstr "" #: ../../content/applications/sales/crm/acquire_leads/convert.rst:95 -msgid "When merging, Odoo gives priority to whichever lead/opportunity was created in the system first, merging the information into the first created lead/opportunity. However, if a lead and an opportunity are being merged, the resulting record is referred to as an opportunity, regardless of which record was created first." -msgstr "" - -#: ../../content/applications/sales/crm/acquire_leads/convert.rst:100 -msgid "After confirming that the leads/opportunities should be merged, return to the kanban view using breadcrumbs, or by clicking the :guilabel:`Similar Lead` smart button. Click the :guilabel:`☰ (three vertical lines)` icon to change to list view." -msgstr "" - -#: ../../content/applications/sales/crm/acquire_leads/convert.rst:104 -msgid "Check the box on the left of the page for the leads/opportunities to be merged. Then, click the :guilabel:`Action ⚙️ (gear)` icon at the top of the page, to reveal a drop-down menu. From that drop-down menu, select the :guilabel:`Merge` option to merge the selected opportunities (or leads)." -msgstr "" - -#: ../../content/applications/sales/crm/acquire_leads/convert.rst:108 -msgid "When :guilabel:`Merge` is selected from the :guilabel:`Action ⚙️ (gear)` drop-down menu, a :guilabel:`Merge` pop-up window appears. In that pop-up window, decide to :guilabel:`Assign opportunities to` a :guilabel:`Salesperson` and/or :guilabel:`Sales Team`." -msgstr "" - -#: ../../content/applications/sales/crm/acquire_leads/convert.rst:112 -msgid "Below those fields, the leads/opportunities to merge are listed, along with their related information. To merge those selected leads/opportunities, click :guilabel:`Merge`." -msgstr "" - -#: ../../content/applications/sales/crm/acquire_leads/convert.rst:116 -msgid "When merging opportunities, no information is lost. Data from the other opportunity is logged in the chatter, and the information fields, for reference." -msgstr "" - -#: ../../content/applications/sales/crm/acquire_leads/convert.rst:-1 -msgid "Merge option from action menu in list view." +msgid "Some filters may need to be removed from the :guilabel:`Search...` bar on the top :guilabel:`Pipeline` page to view all opportunities." msgstr "" #: ../../content/applications/sales/crm/acquire_leads/generate_leads.rst:3 @@ -409,7 +386,8 @@ msgid "Make sure to be aware of the latest EU regulations when receiving contact msgstr "" #: ../../content/applications/sales/crm/acquire_leads/lead_mining.rst:59 -#: ../../content/applications/sales/crm/optimize/partner_autocomplete.rst:36 +#: ../../content/applications/sales/crm/optimize/lead_enrichment.rst:94 +#: ../../content/applications/sales/crm/optimize/partner_autocomplete.rst:61 #: ../../content/applications/sales/rental.rst:88 msgid "Pricing" msgstr "" @@ -439,11 +417,14 @@ msgid "Credits may also be purchased by navigating to the :menuselection:`Settin msgstr "" #: ../../content/applications/sales/crm/acquire_leads/lead_mining.rst:-1 +#: ../../content/applications/sales/crm/optimize/lead_enrichment.rst:-1 msgid "Buy credits in the Odoo IAP settings." msgstr "" -#: ../../content/applications/sales/crm/acquire_leads/lead_mining.rst:88 -msgid "Users of Odoo Online (SaaS) Enterprise automatically have free trial credits in their database to test any IAP features." +#: ../../content/applications/sales/crm/acquire_leads/lead_mining.rst:87 +#: ../../content/applications/sales/crm/optimize/lead_enrichment.rst:16 +#: ../../content/applications/sales/crm/optimize/partner_autocomplete.rst:78 +msgid "Enterprise Odoo users with a valid subscription get free credits to test :abbr:`IAP (In-App Purchase)` features before deciding to purchase more credits for the database. This includes demo/training databases, educational databases, and one-app-free databases." msgstr "" #: ../../content/applications/sales/crm/acquire_leads/lead_mining.rst:92 @@ -680,6 +661,8 @@ msgid "Additional notes and comments can be added in the :guilabel:`Closing Note msgstr "" #: ../../content/applications/sales/crm/acquire_leads/send_quotes.rst:171 +#: ../../content/applications/sales/crm/pipeline/lost_opportunities.rst:34 +#: ../../content/applications/sales/crm/pipeline/lost_opportunities.rst:188 msgid "When all the desired information has been entered in the :guilabel:`Mark Lost` pop-up window, click :guilabel:`Mark as Lost`." msgstr "" @@ -704,167 +687,692 @@ msgid "Optimize your Day-to-Day work" msgstr "" #: ../../content/applications/sales/crm/optimize/gamification.rst:3 -msgid "How to motivate and reward my salespeople?" +msgid "CRM Gamification" msgstr "" #: ../../content/applications/sales/crm/optimize/gamification.rst:5 -msgid "Challenging your employees to reach specific targets with goals and rewards is an excellent way to reinforce good habits and improve your salespeople productivity. The Gamification module gives you simple and creative ways to motivate and evaluate your employees with real-time recognition and badges inspired by game mechanics." +msgid "In Odoo's *CRM* app, *gamification tools* provide the opportunity to evaluate and motivate users through customizable challenges, goals, and rewards. Goals are created to target actions within the *CRM* app, and can be tracked and rewarded automatically to participating sales teams." msgstr "" -#: ../../content/applications/sales/crm/optimize/gamification.rst:13 -msgid "Install the *Gamification* module, or the *CRM gamification* one, which adds some useful data (goals and challenges) that can be used on *CRM/Sale*." +#: ../../content/applications/sales/crm/optimize/gamification.rst:12 +msgid "To install the *Gamification* module, navigate to the :menuselection:`Apps` application. Click into the :guilabel:`Search...` bar at the top of the page and remove the :guilabel:`Apps` filter. Type `Gamification` to search." +msgstr "" + +#: ../../content/applications/sales/crm/optimize/gamification.rst:16 +msgid "If the :guilabel:`Gamification` module is **not** already installed, click :guilabel:`Install`. After completing the installation, return to the :menuselection:`Apps` application and search for `Gamification` again." +msgstr "" + +#: ../../content/applications/sales/crm/optimize/gamification.rst:20 +msgid "On the :guilabel:`CRM Gamification` module, click :guilabel:`Install`. This module features goals and challenges related to the *CRM* and *Sales* applications." msgstr "" #: ../../content/applications/sales/crm/optimize/gamification.rst:-1 -msgid "View of the gamification module being installed in Odoo" +msgid "View of the gamification module being installed in Odoo." msgstr "" -#: ../../content/applications/sales/crm/optimize/gamification.rst:21 -msgid "Create a challenge" +#: ../../content/applications/sales/crm/optimize/gamification.rst:28 +msgid "If both the *CRM* and *Sales* apps are installed, the *CRM Gamification* module is automatically installed on the database." msgstr "" -#: ../../content/applications/sales/crm/optimize/gamification.rst:23 -msgid "Now, create your first challenge by going to :menuselection:`Settings --> Gamification Tools --> Challenges`." +#: ../../content/applications/sales/crm/optimize/gamification.rst:31 +msgid "To access the *Gamification Tools* menu, first enable :ref:`developer-mode`." msgstr "" -#: ../../content/applications/sales/crm/optimize/gamification.rst:27 -msgid "As the gamification tool is a one-time technical setup, you need to activate the technical features in order to access the configuration. To do so, go to *Settings* and *Activate the developer mode*." +#: ../../content/applications/sales/crm/optimize/gamification.rst:33 +msgid "Next, navigate to :menuselection:`Settings app --> Gamification Tools`." msgstr "" #: ../../content/applications/sales/crm/optimize/gamification.rst:-1 msgid "View if the gamification tools menu in Odoo Settings" msgstr "" -#: ../../content/applications/sales/crm/optimize/gamification.rst:35 -msgid "A challenge is a mission that you send to your sales team. It can include one or several goals, set for a specific period of time. Configure your challenge as follows:" -msgstr "" - -#: ../../content/applications/sales/crm/optimize/gamification.rst:38 -msgid "Assign the salespeople to be challenged;" -msgstr "" - -#: ../../content/applications/sales/crm/optimize/gamification.rst:39 -msgid "Assign a responsible;" -msgstr "" - -#: ../../content/applications/sales/crm/optimize/gamification.rst:40 -msgid "Set up the periodicity along with the start and the end date;" -msgstr "" - -#: ../../content/applications/sales/crm/optimize/gamification.rst:41 -msgid "Select your goals;" -msgstr "" - #: ../../content/applications/sales/crm/optimize/gamification.rst:42 -msgid "Set up your rewards (badges)." +msgid "Create badges" msgstr "" -#: ../../content/applications/sales/crm/optimize/gamification.rst:45 -msgid "Badges are granted when a challenge is finished. This is either at the end of a running period (eg: end of the month for a monthly challenge), at the end date of a challenge (if no periodicity is set), or when the challenge is manually closed." +#: ../../content/applications/sales/crm/optimize/gamification.rst:44 +msgid "*Badges* are awarded to users when they have completed a challenge. Different badges can be awarded based on the type of task completed, and can be issued to more than one user, depending on the time they accomplish the goal." msgstr "" -#: ../../content/applications/sales/crm/optimize/gamification.rst:49 -msgid "In the example below, 2 employees are being challenged with a *Monthly Sales Target*. The challenge is based on 2 goals: the total amount invoiced and number of new leads generated. At the end of the month, the winner will be granted with a badge." +#: ../../content/applications/sales/crm/optimize/gamification.rst:48 +msgid "To view the existing badges, or create a new one, navigate to :menuselection:`Settings --> Gamification Tools --> Badges`." msgstr "" #: ../../content/applications/sales/crm/optimize/gamification.rst:-1 -msgid "View of the challenge form and a challenge being created for Odoo Sales" +msgid "View of the badges page in Odoo." msgstr "" -#: ../../content/applications/sales/crm/optimize/gamification.rst:58 -msgid "Set up goals" +#: ../../content/applications/sales/crm/optimize/gamification.rst:56 +msgid "Some badges can be awarded outside of challenges, as well. Select the Kanban card for the desired badge, then click :guilabel:`Grant`. This opens a :guilabel:`Grant Badge` pop-up window. Select a user from the :guilabel:`Who would you like to reward?` field." msgstr "" #: ../../content/applications/sales/crm/optimize/gamification.rst:60 -msgid "The users can be evaluated using goals and numerical objectives to reach." +msgid "Add any additional information regarding why the user is receiving the reward in the field below, then click :guilabel:`Grant Badge`." msgstr "" -#: ../../content/applications/sales/crm/optimize/gamification.rst:62 -msgid "**Goals** are assigned through *challenges* that evaluate (see image above) and compare members of a team throughout time." +#: ../../content/applications/sales/crm/optimize/gamification.rst:63 +msgid "To create a new badge, click :guilabel:`New` at the top-left of the page to open a blank form. Enter a name for the :guilabel:`Badge`, followed by a description." msgstr "" #: ../../content/applications/sales/crm/optimize/gamification.rst:66 -msgid "You can create a new goal on the fly from a *Challenge* by clicking on *Add new item*, under *Goals*. Select the business object according to your company's needs. Examples: number of new leads, time to qualify a lead, total amount invoiced in a specific week, month or any other time frame based on your management preferences, etc." +msgid "The :guilabel:`Allowance to Grant` field determines when a badge can be granted, and by whom:" msgstr "" -#: ../../content/applications/sales/crm/optimize/gamification.rst:-1 -msgid "View of the goal definition form and a goal definition being created for Odoo Sales" +#: ../../content/applications/sales/crm/optimize/gamification.rst:68 +msgid ":guilabel:`Everyone`: this badge can be manually granted by any user." msgstr "" -#: ../../content/applications/sales/crm/optimize/gamification.rst:73 -msgid "Goals may include your database setup as well (e.g. set your company data and a timezone, create new users, etc.)." +#: ../../content/applications/sales/crm/optimize/gamification.rst:69 +msgid ":guilabel:`A selected list of users`: this badge can only be granted by a select group of users. If this option is selected, it generates a new field, :guilabel:`Authorized Users`. Choose the appropriate users from this drop-down list." msgstr "" -#: ../../content/applications/sales/crm/optimize/gamification.rst:77 -msgid "Set up rewards" +#: ../../content/applications/sales/crm/optimize/gamification.rst:72 +msgid ":guilabel:`People having some badges`: this badge can only be granted by users who have already been awarded a specific badge. If this option is selected it generates a new field, :guilabel:`Required Badges`. Use this drop-down list to select the badge(s) a user must have before they can award this badge to others." +msgstr "" + +#: ../../content/applications/sales/crm/optimize/gamification.rst:76 +msgid ":guilabel:`No one, assigned through challenges`: this badge cannot be manually granted, it can only be awarded through challenges." msgstr "" #: ../../content/applications/sales/crm/optimize/gamification.rst:79 -msgid "For non-numerical achievements, **Badges** can be granted to users. From a simple thank you to an exceptional achievement, a badge is an easy way to express gratitude to a user for their good work. To create and grant badges to your employees based on their performance, go to :menuselection:`Settings --> Gamification Tools --> Badges`." +msgid "To limit the number of badges a user can send, tick the :guilabel:`Monthly Limited Spending` checkbox. This sets a limit on the number of times a user can grant this badge. In the :guilabel:`Limitation Number` field, enter the maximum number of times this badge can be sent per month, per person." msgstr "" #: ../../content/applications/sales/crm/optimize/gamification.rst:-1 -msgid "View of the badges page in Odoo" +msgid "The details page for a new badge." +msgstr "" + +#: ../../content/applications/sales/crm/optimize/gamification.rst:91 +msgid "Create a challenge" +msgstr "" + +#: ../../content/applications/sales/crm/optimize/gamification.rst:93 +msgid "To create a challenge, navigate to to :menuselection:`Settings --> Gamification Tools --> Challenges`. Click :guilabel:`New` in the top-left corner to open a blank challenge form." +msgstr "" + +#: ../../content/applications/sales/crm/optimize/gamification.rst:96 +msgid "At the top of the form, enter a :guilabel:`Challenge Name`." +msgstr "" + +#: ../../content/applications/sales/crm/optimize/gamification.rst:99 +msgid "Create assignment rules" +msgstr "" + +#: ../../content/applications/sales/crm/optimize/gamification.rst:101 +msgid "To assign the challenge to specific users, one or more assignment rules must be utilized." +msgstr "" + +#: ../../content/applications/sales/crm/optimize/gamification.rst:103 +msgid "Click into the first field under :guilabel:`Assign Challenge to`, and select a parameter from the drop-down list to define the rule. Then, click into the next field to define the rule's operator. If necessary, click into the third field to further define the parameter." +msgstr "" + +#: ../../content/applications/sales/crm/optimize/gamification.rst:108 +msgid "To include all users with permissions in the *Sales* app, create a rule with the following parameters: - :guilabel:`Groups` - :guilabel:`is in` - `Sales/User: Own Documents Only`" +msgstr "" + +#: ../../content/applications/sales/crm/optimize/gamification.rst:0 +msgid "View of the assignation rules section of a Challenge form." +msgstr "" + +#: ../../content/applications/sales/crm/optimize/gamification.rst:118 +msgid "In the :guilabel:`Periodicity` field, select a time frame for goals to be automatically assessed." +msgstr "" + +#: ../../content/applications/sales/crm/optimize/gamification.rst:121 +msgid "Add goals" +msgstr "" + +#: ../../content/applications/sales/crm/optimize/gamification.rst:123 +msgid "Challenges can be based on a single goal, or can include multiple goals with different targets. To add a goal to the challenge, click :guilabel:`Add a line` on the :guilabel:`Goals` tab." +msgstr "" + +#: ../../content/applications/sales/crm/optimize/gamification.rst:126 +msgid "In the :guilabel:`Goal Definition` field, choose a goal from the drop-down list. The :guilabel:`Condition` field automatically updates to reflect the condition set on the goal definition." +msgstr "" + +#: ../../content/applications/sales/crm/optimize/gamification.rst:131 +msgid "The *CRM Gamification* module contains preconfigured goals geared towards salesteams:" +msgstr "" + +#: ../../content/applications/sales/crm/optimize/gamification.rst:133 +msgid ":guilabel:`New Leads`" +msgstr "" + +#: ../../content/applications/sales/crm/optimize/gamification.rst:134 +msgid ":guilabel:`Time to Qualify a Lead`" +msgstr "" + +#: ../../content/applications/sales/crm/optimize/gamification.rst:135 +msgid ":guilabel:`Days to Close a Dead`" +msgstr "" + +#: ../../content/applications/sales/crm/optimize/gamification.rst:136 +msgid ":guilabel:`New Opportunities`" +msgstr "" + +#: ../../content/applications/sales/crm/optimize/gamification.rst:137 +msgid ":guilabel:`New Sales Orders`" +msgstr "" + +#: ../../content/applications/sales/crm/optimize/gamification.rst:139 +msgid "Enter a :guilabel:`Target` for the goal based on the :guilabel:`Suffix`." +msgstr "" + +#: ../../content/applications/sales/crm/optimize/gamification.rst:141 +msgid "Repeat these steps for each additional goal." +msgstr "" + +#: ../../content/applications/sales/crm/optimize/gamification.rst:-1 +msgid "The goals tab of a challenge form." +msgstr "" + +#: ../../content/applications/sales/crm/optimize/gamification.rst:148 +msgid "Add rewards" +msgstr "" + +#: ../../content/applications/sales/crm/optimize/gamification.rst:150 +msgid "Next, click the :guilabel:`Reward` tab. Choose the :ref:`badges ` to be awarded :guilabel:`For 1st User` and :guilabel:`For Every Succeeding User` by selecting them from the drop-down lists." +msgstr "" + +#: ../../content/applications/sales/crm/optimize/gamification.rst:155 +msgid "Badges are granted when a challenge is finished. This is either at the end of a running period, at the end date of a challenge, or when the challenge is manually closed." +msgstr "" + +#: ../../content/applications/sales/crm/optimize/gamification.rst:158 +msgid "After setup is complete, click the :guilabel:`Start Challenge` button at the top-left of the page to begin the challenge." +msgstr "" + +#: ../../content/applications/sales/crm/optimize/lead_enrichment.rst:3 +msgid "Lead enrichment" +msgstr "" + +#: ../../content/applications/sales/crm/optimize/lead_enrichment.rst:5 +msgid "*Lead enrichment* is a service that provides business information for a contact attached to a lead. Lead enrichment is an In-App Purchase (IAP) that requires credits to use, and is available for existing leads in an Odoo database." +msgstr "" + +#: ../../content/applications/sales/crm/optimize/lead_enrichment.rst:9 +msgid "The information provided by lead enrichment can include general information about the business (including full business name and logo), social media accounts, :guilabel:`Company type`, :guilabel:`Founded` information, :guilabel:`Sectors` information, the number of :guilabel:`Employees`, :guilabel:`Estimated revenue`, :guilabel:`Phone` number, :guilabel:`Timezone`, and :guilabel:`Technologies Used`." +msgstr "" + +#: ../../content/applications/sales/crm/optimize/lead_enrichment.rst:21 +msgid "The *leads* feature **must** be activated in the *CRM* settings page in order to use lead enrichment. To access the *CRM* settings, navigate to :menuselection:`CRM app --> Configuration --> Settings`. Under the :guilabel:`CRM` section activate the :guilabel:`Leads` option and click :guilabel:`Save`." +msgstr "" + +#: ../../content/applications/sales/crm/optimize/lead_enrichment.rst:27 +msgid "Lead enrichment set up" +msgstr "" + +#: ../../content/applications/sales/crm/optimize/lead_enrichment.rst:29 +msgid "To set up lead enrichment in the *CRM* application, navigate to :menuselection:`CRM app --> Configuration --> Settings`. Then, under the :guilabel:`Lead Generation` section, tick the checkbox next to :guilabel:`Lead Enrichment`, and select either :guilabel:`Enrich leads on demand only` or :guilabel:`Enrich all leads automatically`. Click the :guilabel:`Save` button to activate the changes." +msgstr "" + +#: ../../content/applications/sales/crm/optimize/lead_enrichment.rst:-1 +msgid "CRM lead generation settings page, with lead enrichment activation highlighted, and enrich\n" +"leads on demand only chosen." +msgstr "" + +#: ../../content/applications/sales/crm/optimize/lead_enrichment.rst:41 +msgid "Enrich leads" +msgstr "" + +#: ../../content/applications/sales/crm/optimize/lead_enrichment.rst:43 +msgid "Enrichment of leads is based on the domain of the email address of the customer set on the lead. There are two different ways that a lead can be enriched: *automatically* or *manually*." +msgstr "" + +#: ../../content/applications/sales/crm/optimize/lead_enrichment.rst:47 +msgid "Automatically enrich leads" +msgstr "" + +#: ../../content/applications/sales/crm/optimize/lead_enrichment.rst:49 +msgid "During set up, if :guilabel:`Enrich all leads automatically` was selected on the *CRM* :guilabel:`Settings` page, then no action needs to be taken by the user to enrich the lead. A scheduled action runs automatically, every sixty minutes, and enrichment occurs on leads, after a remote database is contacted." +msgstr "" + +#: ../../content/applications/sales/crm/optimize/lead_enrichment.rst:55 +msgid "To access the cron that runs for the automatic lead enrichment, activate :ref:`developer mode `, and navigate to :menuselection:`Settings app --> Technical menu --> Automation section --> Scheduled Actions`. In the :guilabel:`Search...` bar, type in `CRM`. Click into the result labeled :guilabel:`CRM: enrich leads (IAP)`, and make any necessary adjustments. In the :guilabel:`Execute Every` field, enter a value greater than, or equal to, five minutes." +msgstr "" + +#: ../../content/applications/sales/crm/optimize/lead_enrichment.rst:62 +msgid "The following is an example of lead enrichment data that has been autocompleted successfully:" +msgstr "" + +#: ../../content/applications/sales/crm/optimize/lead_enrichment.rst:0 +msgid "Chatter showing lead enrichment data." +msgstr "" + +#: ../../content/applications/sales/crm/optimize/lead_enrichment.rst:69 +msgid "Manually enrich leads" +msgstr "" + +#: ../../content/applications/sales/crm/optimize/lead_enrichment.rst:71 +msgid "If the :guilabel:`Enrich leads on demand only` option was selected on the *CRM* :guilabel:`Settings` page, when activating :guilabel:`Lead Enrichment`, each lead that a user wishes to enrich **must** be manually enriched. This is achieved by clicking the :guilabel:`Enrich` button in the top menu of the lead." +msgstr "" + +#: ../../content/applications/sales/crm/optimize/lead_enrichment.rst:76 +msgid "The same information will be retrieved at the same :abbr:`IAP (In-App Puchase)` credit cost (one per enrichment). This method of enrichment is useful when every lead does not need to be enriched, or cost is an issue." +msgstr "" + +#: ../../content/applications/sales/crm/optimize/lead_enrichment.rst:-1 +msgid "Manual enrich button feature highlighted on the CRM lead." +msgstr "" + +#: ../../content/applications/sales/crm/optimize/lead_enrichment.rst:85 +msgid "Manually enrich leads in bulk using the *list* view. First, navigate to :menuselection:`CRM app --> Leads`, and click the list view button (:guilabel:`☰ (three horizontal lines)` icon). Next, tick the checkboxes for the leads that should be manually enriched. Finally, click the :guilabel:`⚙️ Action` icon, and select :guilabel:`Enrich` from the resulting drop-down menu. This can also be achieved from the *My Pipeline* page. To do so, simply open the *CRM* app, or navigate to :menuselection:`CRM app --> Sales --> My Pipeline`. Either route reveals leads and opportunities on the :guilabel:`Pipeline` page." +msgstr "" + +#: ../../content/applications/sales/crm/optimize/lead_enrichment.rst:96 +msgid "Lead enrichment is an In-App Purchase (IAP) feature, and each enriched lead costs one credit." +msgstr "" + +#: ../../content/applications/sales/crm/optimize/lead_enrichment.rst:99 +msgid "See here for full pricing information: `Lead Generation by Odoo IAP `_." +msgstr "" + +#: ../../content/applications/sales/crm/optimize/lead_enrichment.rst:102 +msgid "To buy credits, navigate to :menuselection:`CRM app --> Configuration --> Settings`. In the :guilabel:`Lead Generation` section, under the :guilabel:`Lead Enrichment` feature, click on :guilabel:`Buy Credits`." +msgstr "" + +#: ../../content/applications/sales/crm/optimize/lead_enrichment.rst:-1 +msgid "Buy credits from the lead enrichment settings." +msgstr "" + +#: ../../content/applications/sales/crm/optimize/lead_enrichment.rst:110 +msgid "Credits and balances may also be purchased by navigating to the :menuselection:`Settings app`. In the :guilabel:`Contacts` section, under the :guilabel:`Odoo IAP` feature, click on :guilabel:`View My Services`." +msgstr "" + +#: ../../content/applications/sales/crm/optimize/lead_enrichment.rst:119 +#: ../../content/applications/sales/crm/optimize/partner_autocomplete.rst:83 +msgid ":doc:`../../../essentials/in_app_purchase`" +msgstr "" + +#: ../../content/applications/sales/crm/optimize/lead_enrichment.rst:122 +msgid "When collecting a company's contact information, make sure to be aware of the latest EU regulations. For more information about General Data Protection Regulation, refer to: `Odoo GDPR `__." msgstr "" #: ../../content/applications/sales/crm/optimize/partner_autocomplete.rst:3 -msgid "Enrich your contacts base with Partner Autocomplete" +msgid "Enrich contacts with partner autocomplete" msgstr "" #: ../../content/applications/sales/crm/optimize/partner_autocomplete.rst:5 -msgid "Partner Autocomplete helps you to enrich your contacts database with corporate data. Select one of the companies suggested in the dropdown, and quickly get all the information you need." +msgid "*Partner autocomplete* enriches the contacts database with corporate data. In any module, enter the new company name into the :guilabel:`Customer` field (`partner_id` technical field), and select one of the companies suggested in the drop-down menu. Instantly get valuable company information full of hard-to-find data for a desired company." msgstr "" #: ../../content/applications/sales/crm/optimize/partner_autocomplete.rst:11 -msgid "Go to :menuselection:`Settings --> Contacts` and activate the *Partner Autocomplete* feature." +msgid "A company **cannot** already be manually entered in the *Contacts* application prior to enriching it with data." +msgstr "" + +#: ../../content/applications/sales/crm/optimize/partner_autocomplete.rst:14 +msgid "The information provided by partner autocomplete can include general information about the business (including full business name and logo), social media accounts, :guilabel:`Company type`, :guilabel:`Founded` information, :guilabel:`Sectors` information, the number of :guilabel:`Employees`, :guilabel:`Estimated revenue`, :guilabel:`Phone` number, :guilabel:`Timezone`, and :guilabel:`Technologies Used`." +msgstr "" + +#: ../../content/applications/sales/crm/optimize/partner_autocomplete.rst:21 +msgid "When getting a company's contact information make sure to be aware of the latest EU regulations. For more information about General Data Protection Regulation refer to: `Odoo GDPR `_. In Odoo, individual contact information cannot be searched for with the partner autocomplete feature." +msgstr "" + +#: ../../content/applications/sales/crm/optimize/partner_autocomplete.rst:29 +msgid "Go to :menuselection:`Settings app --> Contacts section`. Then, activate the :guilabel:`Partner Autocomplete` feature, by ticking the checkbox beside it, and clicking :guilabel:`Save`." msgstr "" #: ../../content/applications/sales/crm/optimize/partner_autocomplete.rst:-1 -msgid "View of settings page and the activations of the feature in Odoo" +msgid "View of settings page and the activations of the feature in Odoo." msgstr "" -#: ../../content/applications/sales/crm/optimize/partner_autocomplete.rst:18 -msgid "Enrich your contacts with corporate data" +#: ../../content/applications/sales/crm/optimize/partner_autocomplete.rst:37 +msgid "Enrich contacts with corporate data" msgstr "" -#: ../../content/applications/sales/crm/optimize/partner_autocomplete.rst:22 -msgid "From any module, once you start to create a new contact typing the name of it, the system will suggest a potential match. If you select it, the contact will be populated with corporate data." +#: ../../content/applications/sales/crm/optimize/partner_autocomplete.rst:39 +msgid "From any module, as the user is typing in the name of a new company contact, Odoo reveals a large drop-down menu of potential match suggestions. If any are selected, the contact is then populated with corporate data related to that specific selection." msgstr "" -#: ../../content/applications/sales/crm/optimize/partner_autocomplete.rst:23 -msgid "For example, after typing *Odoo*, you will get the following information:" +#: ../../content/applications/sales/crm/optimize/partner_autocomplete.rst:43 +msgid "For example, after typing `Odoo`, the following information populates:" msgstr "" #: ../../content/applications/sales/crm/optimize/partner_autocomplete.rst:-1 msgid "Creating a new contact in Odoo" msgstr "" +#: ../../content/applications/sales/crm/optimize/partner_autocomplete.rst:49 +msgid "In the chatter, the following information populates about the company, after clicking on the desired pre-populated contact:" +msgstr "" + #: ../../content/applications/sales/crm/optimize/partner_autocomplete.rst:-1 msgid "View of the information being shown about odoo with the autocomplete option in Odoo" msgstr "" -#: ../../content/applications/sales/crm/optimize/partner_autocomplete.rst:33 -msgid "Partner Autocomplete also works if you enter a VAT number instead of a company name." +#: ../../content/applications/sales/crm/optimize/partner_autocomplete.rst:57 +msgid "Partner Autocomplete also works if a :abbr:`VAT (value-added tax)` number is entered instead of company name." msgstr "" -#: ../../content/applications/sales/crm/optimize/partner_autocomplete.rst:39 -msgid "*Partner Autocomplete* is an *In-App Purchase (IAP)* service, which requires prepaid credits to be used. Each request will consume one credit." +#: ../../content/applications/sales/crm/optimize/partner_autocomplete.rst:63 +msgid "*Partner Autocomplete* is an *In-App Purchase (IAP)* service, which requires prepaid credits to be used. Each request consumes one credit." msgstr "" -#: ../../content/applications/sales/crm/optimize/partner_autocomplete.rst:41 -msgid "To buy credits, go to :menuselection:`Settings --> Contacts --> Partner Autocomplete or Odoo IAP --> View My Services` and select a package." +#: ../../content/applications/sales/crm/optimize/partner_autocomplete.rst:66 +msgid "To buy credits, go to :menuselection:`Settings app --> Contacts section`. Then, locate either the :guilabel:`Partner Autocomplete` feature and click :guilabel:`Buy credits`, or locate the :guilabel:`Odoo IAP` feature and click :guilabel:`View My Services`. From the resulting page, select a desired package." msgstr "" -#: ../../content/applications/sales/crm/optimize/partner_autocomplete.rst:44 -msgid "If you run out of credits, the only information that will be populated when clicking on the suggested company will be the website link and the logo." +#: ../../content/applications/sales/crm/optimize/partner_autocomplete.rst:72 +msgid "If the database runs out of credits, the only information populated when clicking on the suggested company will be the website link and the logo." msgstr "" -#: ../../content/applications/sales/crm/optimize/partner_autocomplete.rst:46 -msgid "If you are on Odoo Online and you have the Enterprise version, you benefit from free trial credits to test the feature." +#: ../../content/applications/sales/crm/optimize/partner_autocomplete.rst:75 +msgid "Learn about our `Privacy Policy `_." msgstr "" -#: ../../content/applications/sales/crm/optimize/partner_autocomplete.rst:48 -msgid "Learn about our *Privacy Policy* `here `_." +#: ../../content/applications/sales/crm/optimize/utilize_activities.rst:3 +msgid "Utilize activities for sales teams" +msgstr "" + +#: ../../content/applications/sales/crm/optimize/utilize_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/sales/crm/optimize/utilize_activities.rst:13 +msgid "The summary view of activities for leads and opportunities in an Odoo database." +msgstr "" + +#: ../../content/applications/sales/crm/optimize/utilize_activities.rst:13 +msgid "Planned Activities for Leads and Opportunities." +msgstr "" + +#: ../../content/applications/sales/crm/optimize/utilize_activities.rst:16 +msgid "Activity types" +msgstr "" + +#: ../../content/applications/sales/crm/optimize/utilize_activities.rst:18 +msgid "A set of preconfigured activity types is available in the *CRM* app. To view the list of available activity types, navigate to the :menuselection:`CRM app --> Configuration --> Activity Types`." +msgstr "" + +#: ../../content/applications/sales/crm/optimize/utilize_activities.rst:22 +msgid "Additional activity types are available within the database, and can be utilized through different applications. To access the complete list of activity types, go to the :menuselection:`Settings app`, then scroll to the :guilabel:`Discuss` section, and click :guilabel:`Activity Types`." +msgstr "" + +#: ../../content/applications/sales/crm/optimize/utilize_activities.rst:27 +msgid "The preconfigured activity types for the *CRM* app are as follows:" +msgstr "" + +#: ../../content/applications/sales/crm/optimize/utilize_activities.rst:29 +msgid ":guilabel:`Email`: adds a reminder to the chatter that prompts the salesperson to send an email." +msgstr "" + +#: ../../content/applications/sales/crm/optimize/utilize_activities.rst:30 +msgid ":guilabel:`Call`: opens a calendar link where the salesperson can schedule time to call the contact." +msgstr "" + +#: ../../content/applications/sales/crm/optimize/utilize_activities.rst:32 +msgid ":guilabel:`Meeting`: opens a calendar link where the salesperson can schedule time to have a meeting with the contact." +msgstr "" + +#: ../../content/applications/sales/crm/optimize/utilize_activities.rst:34 +msgid ":guilabel:`To Do`: adds a general reminder task to the chatter." +msgstr "" + +#: ../../content/applications/sales/crm/optimize/utilize_activities.rst:35 +msgid ":guilabel:`Upload Document`: adds a link on the activity where an external document can be uploaded. Note that the *Documents* app is **not** required to utilize this activity type." +msgstr "" + +#: ../../content/applications/sales/crm/optimize/utilize_activities.rst:39 +msgid "If other applications are installed, such as *Sales* or *Accounting*, other activity types are made available in the *CRM* app." +msgstr "" + +#: ../../content/applications/sales/crm/optimize/utilize_activities.rst:45 +msgid "Create a new activity type" +msgstr "" + +#: ../../content/applications/sales/crm/optimize/utilize_activities.rst:47 +msgid "To create a new activity type, click :guilabel:`New` at the top-left of the page to open a blank form." +msgstr "" + +#: ../../content/applications/sales/crm/optimize/utilize_activities.rst:50 +msgid "At the top of the form, start by choosing a :guilabel:`Name` for the new activity type." +msgstr "" + +#: ../../content/applications/sales/crm/optimize/utilize_activities.rst:53 +msgid "Activity settings" +msgstr "" + +#: ../../content/applications/sales/crm/optimize/utilize_activities.rst:56 +msgid "Action" +msgstr "" + +#: ../../content/applications/sales/crm/optimize/utilize_activities.rst:58 +msgid "The *Action* field specifies the intent of the activity. Some actions trigger specific behaviors after an activity is scheduled." +msgstr "" + +#: ../../content/applications/sales/crm/optimize/utilize_activities.rst:61 +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/sales/crm/optimize/utilize_activities.rst:63 +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/sales/crm/optimize/utilize_activities.rst:65 +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/sales/crm/optimize/utilize_activities.rst:-1 +msgid "The Activity settings on a new activity type with emphasis on the Action field." +msgstr "" + +#: ../../content/applications/sales/crm/optimize/utilize_activities.rst:73 +msgid "The actions available to select on an activity type vary, depending on the applications currently installed in the database." +msgstr "" + +#: ../../content/applications/sales/crm/optimize/utilize_activities.rst:77 +msgid "Default user" +msgstr "" + +#: ../../content/applications/sales/crm/optimize/utilize_activities.rst:79 +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/sales/crm/optimize/utilize_activities.rst:84 +msgid "Default summary" +msgstr "" + +#: ../../content/applications/sales/crm/optimize/utilize_activities.rst:86 +msgid "To include notes whenever this activity type is created, enter them into the :guilabel:`Default Summary` field." +msgstr "" + +#: ../../content/applications/sales/crm/optimize/utilize_activities.rst:90 +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/sales/crm/optimize/utilize_activities.rst:95 +msgid "Next activity" +msgstr "" + +#: ../../content/applications/sales/crm/optimize/utilize_activities.rst:97 +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/sales/crm/optimize/utilize_activities.rst:101 +msgid "Suggest next activity" +msgstr "" + +#: ../../content/applications/sales/crm/optimize/utilize_activities.rst:103 +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/sales/crm/optimize/utilize_activities.rst:-1 +msgid "The Next Activity section on a new activity type form." +msgstr "" + +#: ../../content/applications/sales/crm/optimize/utilize_activities.rst:111 +#: ../../content/applications/sales/crm/optimize/utilize_activities.rst:139 +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/sales/crm/optimize/utilize_activities.rst:116 +#: ../../content/applications/sales/crm/optimize/utilize_activities.rst:144 +msgid "This :guilabel:`Schedule` field information can be altered before the activity is scheduled." +msgstr "" + +#: ../../content/applications/sales/crm/optimize/utilize_activities.rst:118 +#: ../../content/applications/sales/crm/optimize/utilize_activities.rst:146 +msgid "When all configurations are complete, click :guilabel:`Save`." +msgstr "" + +#: ../../content/applications/sales/crm/optimize/utilize_activities.rst:121 +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/sales/crm/optimize/utilize_activities.rst:0 +msgid "A schedule activity pop-up with emphasis on the recommended activities." +msgstr "" + +#: ../../content/applications/sales/crm/optimize/utilize_activities.rst:130 +msgid "Trigger next activity" +msgstr "" + +#: ../../content/applications/sales/crm/optimize/utilize_activities.rst:132 +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/sales/crm/optimize/utilize_activities.rst:135 +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/sales/crm/optimize/utilize_activities.rst:149 +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/sales/crm/optimize/utilize_activities.rst:154 +msgid "Activity tracking" +msgstr "" + +#: ../../content/applications/sales/crm/optimize/utilize_activities.rst:156 +msgid "To keep the pipeline up to date with the most accurate view of the status of activities, as soon as a lead is interacted with, the associated activity should be marked as *Done*. This ensures the next activity can be scheduled as needed. It also prevents the pipeline from becoming cluttered with past due activities." +msgstr "" + +#: ../../content/applications/sales/crm/optimize/utilize_activities.rst:161 +msgid "The pipeline is most effective when it is kept up-to-date and accurate to the interactions it is tracking." +msgstr "" + +#: ../../content/applications/sales/crm/optimize/utilize_activities.rst:167 +msgid "Activity plans" +msgstr "" + +#: ../../content/applications/sales/crm/optimize/utilize_activities.rst:169 +msgid "*Activity plans* are preconfigured sequences of activities. When an activity plan is launched, every activity in the sequence is scheduled automatically." +msgstr "" + +#: ../../content/applications/sales/crm/optimize/utilize_activities.rst:172 +msgid "To create a new plan, navigate to :menuselection:`CRM app --> Configuration --> Activity Plan`. Click :guilabel:`New` at the top-left of the page to open a blank :guilabel:`Lead Plans` form." +msgstr "" + +#: ../../content/applications/sales/crm/optimize/utilize_activities.rst:175 +msgid "Enter a name for the new plan in the :guilabel:`Plan Name` field. On the :guilabel:`Activities to Create` tab, click :guilabel:`Add a line` to add a new activity." +msgstr "" + +#: ../../content/applications/sales/crm/optimize/utilize_activities.rst:178 +msgid "Select an :guilabel:`Activity Type` from the drop-down menu. Click :guilabel:`Search More` to see a complete list of available activity types, or to create a :ref:`new one `." +msgstr "" + +#: ../../content/applications/sales/crm/optimize/utilize_activities.rst:182 +msgid "Next, in the :guilabel:`Summary` field, enter any details to describe the specifics of the activity, including instructions for the salesperson or information due upon the completion of the activity. The contents of this field are included with the scheduled activity, and can be edited later." +msgstr "" + +#: ../../content/applications/sales/crm/optimize/utilize_activities.rst:186 +msgid "In the :guilabel:`Assignment` field, select one of the following options:" +msgstr "" + +#: ../../content/applications/sales/crm/optimize/utilize_activities.rst:188 +msgid ":guilabel:`Ask at launch`: activities are assigned to a user when the plan is scheduled." +msgstr "" + +#: ../../content/applications/sales/crm/optimize/utilize_activities.rst:189 +msgid ":guilabel:`Default user`: activities are always assigned to a specific user." +msgstr "" + +#: ../../content/applications/sales/crm/optimize/utilize_activities.rst:191 +msgid "If :guilabel:`Default user` is selected in the :guilabel:`Assignment` field, choose a user in the :guilabel:`Assigned to` field." +msgstr "" + +#: ../../content/applications/sales/crm/optimize/utilize_activities.rst:195 +msgid "Activity plans can feature activities that are assigned to default users and users assigned at the plan launch." +msgstr "" + +#: ../../content/applications/sales/crm/optimize/utilize_activities.rst:0 +msgid "A Lead Plan form with scheduled activities." +msgstr "" + +#: ../../content/applications/sales/crm/optimize/utilize_activities.rst:202 +msgid "Next, configure the timeline for the activity. Activities can be scheduled to occur either before the plan date or after. Use the :guilabel:`Interval` and :guilabel:`Units` fields to set the deadline for this activity. Lastly, in the :guilabel:`Trigger` field, select whether the activity should occur before or after the plan date." +msgstr "" + +#: ../../content/applications/sales/crm/optimize/utilize_activities.rst:208 +msgid "An activity plan is created to handle high priority leads. Specifically, these leads should be contacted quickly, with a meeting scheduled within two days of the initial contact. The plan is configured with the following activities:" +msgstr "" + +#: ../../content/applications/sales/crm/optimize/utilize_activities.rst:212 +msgid "Email two days **before** plan date" +msgstr "" + +#: ../../content/applications/sales/crm/optimize/utilize_activities.rst:213 +msgid "Meeting zero days **before** plan date" +msgstr "" + +#: ../../content/applications/sales/crm/optimize/utilize_activities.rst:214 +msgid "Make quote three days **after** plan date" +msgstr "" + +#: ../../content/applications/sales/crm/optimize/utilize_activities.rst:215 +msgid "Upload document three days **after** plan date" +msgstr "" + +#: ../../content/applications/sales/crm/optimize/utilize_activities.rst:216 +msgid "Follow-up five days **after** plan date" +msgstr "" + +#: ../../content/applications/sales/crm/optimize/utilize_activities.rst:218 +msgid "This sets the *plan date* as the meeting deadline, which is the objective of the plan. Before that date, there is lead time to contact the customer and prepare for the meeting. After that date, the salesperson has time to create a quote, upload the document, and follow-up." +msgstr "" + +#: ../../content/applications/sales/crm/optimize/utilize_activities.rst:222 +msgid "Repeat these steps for each activity included in the plan." +msgstr "" + +#: ../../content/applications/sales/crm/optimize/utilize_activities.rst:225 +msgid "Launch an activity plan" +msgstr "" + +#: ../../content/applications/sales/crm/optimize/utilize_activities.rst:227 +msgid "To launch an activity plan on a *CRM* opportunity, navigate to :menuselection:`CRM app` and click on the Kanban card of an opportunity to open it." +msgstr "" + +#: ../../content/applications/sales/crm/optimize/utilize_activities.rst:230 +msgid "At the top-right of the chatter, click :guilabel:`Activities` to open the :guilabel:`Schedule Activity` pop-up window." +msgstr "" + +#: ../../content/applications/sales/crm/optimize/utilize_activities.rst:233 +msgid "In the :guilabel:`Plan` field, select the desired activity plan to launch. This generates a :guilabel:`Plan summary`, listing out the activities included in the plan. Select a :guilabel:`Plan Date` using the calendar popover. This updates the :guilabel:`Plan summary` with deadlines based on the intervals configured on the :ref:`activity plan `." +msgstr "" + +#: ../../content/applications/sales/crm/optimize/utilize_activities.rst:238 +msgid "Select a user in the :guilabel:`Assigned To` field. This user is assigned to any of the activities on the plan were configured with :guilabel:`Ask at launch` in the :guilabel:`Assignment` field." +msgstr "" + +#: ../../content/applications/sales/crm/optimize/utilize_activities.rst:-1 +msgid "The schedule activity pop-up window with an Activity plan selected." +msgstr "" + +#: ../../content/applications/sales/crm/optimize/utilize_activities.rst:245 +msgid "Click :guilabel:`Schedule`." +msgstr "" + +#: ../../content/applications/sales/crm/optimize/utilize_activities.rst:247 +msgid "The details of the plan are added to the chatter, in addition to each of the activities." +msgstr "" + +#: ../../content/applications/sales/crm/optimize/utilize_activities.rst:-1 +msgid "The chatter thread of a CRM opportunity with a launched activity plan." +msgstr "" + +#: ../../content/applications/sales/crm/optimize/utilize_activities.rst:254 +msgid ":doc:`Activities `" msgstr "" #: ../../content/applications/sales/crm/performance.rst:5 @@ -2132,137 +2640,370 @@ msgid "Manage lost opportunities" msgstr "" #: ../../content/applications/sales/crm/pipeline/lost_opportunities.rst:5 -msgid "Not all opportunities result in successful sales. In order to keep the pipeline up to date, lost opportunities need to be identified. Specifying the reason why an opportunity was lost provides additional insight that can prove useful for future opportunities." +msgid "Not every opportunity results in a successful sale. To keep the pipeline up-to-date, *lost* opportunities need to be identified. Specifying why an opportunity was lost provides additional insight that can prove useful for future opportunities." msgstr "" #: ../../content/applications/sales/crm/pipeline/lost_opportunities.rst:10 -msgid "Mark a lead as lost" +msgid "Mark an opportunity as lost" msgstr "" #: ../../content/applications/sales/crm/pipeline/lost_opportunities.rst:12 -msgid "To mark a lead as lost, open the :menuselection:`CRM` application, and select a lead from the pipeline, by clicking on its corresponding kanban card. Doing so reveals that lead's detail form." +msgid "To mark an opportunity as lost, first open the :menuselection:`CRM app`, and select an opportunity from the pipeline, by clicking on its corresponding Kanban card. Doing so reveals that opportunity's detail form." msgstr "" -#: ../../content/applications/sales/crm/pipeline/lost_opportunities.rst:15 -msgid "Then, click :guilabel:`Lost`, located at the top of the lead's detail form." +#: ../../content/applications/sales/crm/pipeline/lost_opportunities.rst:16 +msgid "Then, click :guilabel:`Lost`, located at the top of the opportunity's detail form." msgstr "" #: ../../content/applications/sales/crm/pipeline/lost_opportunities.rst:-1 msgid "Buttons from the top of an opportunity record with the lost button emphasized." msgstr "" -#: ../../content/applications/sales/crm/pipeline/lost_opportunities.rst:21 -msgid "This opens the :guilabel:`Lost Reason` popup. From the drop-down, choose an existing lost reason. If no applicable reason is available, create a new one by entering it into the :guilabel:`Lost Reason` field, and clicking :guilabel:`Create`." +#: ../../content/applications/sales/crm/pipeline/lost_opportunities.rst:22 +#: ../../content/applications/sales/crm/pipeline/lost_opportunities.rst:181 +msgid "This opens the :guilabel:`Mark Lost` pop-up window. From the :guilabel:`Lost Reason` drop-down menu, choose an existing lost reason. If no applicable reason is available, create a new one by entering it into the :guilabel:`Lost Reason` field, and clicking :guilabel:`Create`." msgstr "" -#: ../../content/applications/sales/crm/pipeline/lost_opportunities.rst:25 -msgid "Additional notes and comments can be added below the lost reason designated in the :guilabel:`Lost Reason` field." +#: ../../content/applications/sales/crm/pipeline/lost_opportunities.rst:26 +msgid "Additional notes and comments can be added below the lost reason in the designated :guilabel:`Closing Note` field." msgstr "" -#: ../../content/applications/sales/crm/pipeline/lost_opportunities.rst:28 -msgid "When all the desired information has been entered in the :guilabel:`Lost Reason` pop-up window, click :guilabel:`Submit`." +#: ../../content/applications/sales/crm/pipeline/lost_opportunities.rst:30 +msgid "Neither the :guilabel:`Lost Reason` field, nor the :guilabel:`Closing Note` field, on the :guilabel:`Mark Lost` pop-up window are required. However, it is recommended to include this information for the sake of traceability, accountability, and reporting purposes." msgstr "" #: ../../content/applications/sales/crm/pipeline/lost_opportunities.rst:-1 msgid "Lost reasons popup with sample reasons." msgstr "" -#: ../../content/applications/sales/crm/pipeline/lost_opportunities.rst:35 -msgid "Upon clicking :guilabel:`Submit`, the pop-up window disappears, and Odoo returns to the lead detail form, where a new red :guilabel:`Lost` banner is now present in the upper-right corner of the lead." +#: ../../content/applications/sales/crm/pipeline/lost_opportunities.rst:41 +msgid "After clicking :guilabel:`Mark as Lost`, a red :guilabel:`Lost` banner is added to the upper-right corner of the opportunity." msgstr "" -#: ../../content/applications/sales/crm/pipeline/lost_opportunities.rst:39 +#: ../../content/applications/sales/crm/pipeline/lost_opportunities.rst:-1 +msgid "A lost opportunity with the lost banner added." +msgstr "" + +#: ../../content/applications/sales/crm/pipeline/lost_opportunities.rst:51 msgid "Create/edit lost reasons" msgstr "" -#: ../../content/applications/sales/crm/pipeline/lost_opportunities.rst:41 +#: ../../content/applications/sales/crm/pipeline/lost_opportunities.rst:53 msgid "To create a new lost reason, or edit an existing one, navigate to :menuselection:`CRM app --> Configuration --> Lost Reasons`." msgstr "" -#: ../../content/applications/sales/crm/pipeline/lost_opportunities.rst:44 -msgid "To edit an existing reason, click on the reason that should be modified. When clicked, that reason becomes highlighted. Once highlighted, change the description of the selected lost reason by editing the :guilabel:`Description` field. When done, click :guilabel:`Save` in the upper-left corner." -msgstr "" - -#: ../../content/applications/sales/crm/pipeline/lost_opportunities.rst:48 -msgid "To create a new lost reason, click :guilabel:`Create` in the upper-left corner of the :guilabel:`Lost Reasons` page. Doing so reveals a new blank line in the :guilabel:`Description` field. Then, proceed to type in the new lost reason in that new line. Once ready, click :guilabel:`Save`." -msgstr "" - -#: ../../content/applications/sales/crm/pipeline/lost_opportunities.rst:54 -msgid "Retrieve lost opportunities" -msgstr "" - #: ../../content/applications/sales/crm/pipeline/lost_opportunities.rst:56 -msgid "To retrieve lost opportunities in Odoo *CRM*, open the :menuselection:`CRM app` to the main :guilabel:`Pipeline` dashboard. Then, click the :guilabel:`Filters` drop-down menu, located beneath the search bar." +msgid "To edit an existing lost reason:" +msgstr "" + +#: ../../content/applications/sales/crm/pipeline/lost_opportunities.rst:58 +msgid "Click on the reason to be edited to highlight it." +msgstr "" + +#: ../../content/applications/sales/crm/pipeline/lost_opportunities.rst:59 +msgid "Change the selected lost reason by editing the :guilabel:`Description` field." +msgstr "" + +#: ../../content/applications/sales/crm/pipeline/lost_opportunities.rst:60 +msgid "When finished, click :guilabel:`Save` in the upper-left corner." +msgstr "" + +#: ../../content/applications/sales/crm/pipeline/lost_opportunities.rst:62 +msgid "To create a new lost reason:" +msgstr "" + +#: ../../content/applications/sales/crm/pipeline/lost_opportunities.rst:64 +msgid "Click :guilabel:`New` in the upper-left corner of the :guilabel:`Lost Reasons` page." +msgstr "" + +#: ../../content/applications/sales/crm/pipeline/lost_opportunities.rst:65 +msgid "In the new blank line, click in the :guilabel:`Description` field, then type the new lost reason." +msgstr "" + +#: ../../content/applications/sales/crm/pipeline/lost_opportunities.rst:66 +msgid "When finished, click :guilabel:`Save`." +msgstr "" + +#: ../../content/applications/sales/crm/pipeline/lost_opportunities.rst:69 +msgid "View lost opportunities" +msgstr "" + +#: ../../content/applications/sales/crm/pipeline/lost_opportunities.rst:71 +msgid "To retrieve lost opportunities in Odoo *CRM*, open the :menuselection:`CRM app`. On the main :guilabel:`Pipeline` dashboard, click into the :guilabel:`Search...` bar at the top of the page, and remove all of the default filters." msgstr "" #: ../../content/applications/sales/crm/pipeline/lost_opportunities.rst:-1 msgid "Search bar with lost filter emphasized." msgstr "" -#: ../../content/applications/sales/crm/pipeline/lost_opportunities.rst:64 -msgid "From the :guilabel:`Filters` drop-down menu, select the :guilabel:`Lost` option. Upon selecting :guilabel:`Lost`, only the leads that have been marked as `Lost` appear on the :guilabel:`Pipeline` page." +#: ../../content/applications/sales/crm/pipeline/lost_opportunities.rst:79 +msgid "Open the :guilabel:`Filters` drop-down menu, by clicking the :guilabel:`🔻(triangle pointed down)` icon to the right of the :guilabel:`Search...` bar to open the drop-down menu containing :guilabel:`Filters`, :guilabel:`Group By`, and :guilabel:`Favorites` options, designated into respective columns." msgstr "" -#: ../../content/applications/sales/crm/pipeline/lost_opportunities.rst:68 -msgid "To filter leads by a specific lost reason, select :menuselection:`Filters --> Add Custom Filter`. Doing so reveals another drop-down menu with three fields." +#: ../../content/applications/sales/crm/pipeline/lost_opportunities.rst:84 +msgid "Select the :guilabel:`Lost` option from the :guilabel:`Filters` section. Upon selecting :guilabel:`Lost`, only the opportunities marked as `Lost` appear on the :guilabel:`Pipeline` page." msgstr "" -#: ../../content/applications/sales/crm/pipeline/lost_opportunities.rst:71 -msgid "In the top field drop-down menu, select :guilabel:`Lost Reason`. In the second field drop-down menu, select :guilabel:`Contains`. Then, in the third field of the :guilabel:`Add Custom Field` sub menu, type in the specific keyword(s). Lastly, click :guilabel:`Apply`. Upon clicking :guilabel:`Apply`, Odoo reveals all the lost leads with a reason that contains that specified keyword(s)." +#: ../../content/applications/sales/crm/pipeline/lost_opportunities.rst:88 +msgid "Sort opportunities by lost reason" +msgstr "" + +#: ../../content/applications/sales/crm/pipeline/lost_opportunities.rst:90 +msgid "To filter opportunities by a specific lost reason, click the :guilabel:`🔻(triangle pointed down)` icon to the right of the :guilabel:`Search...` bar again to open the drop-down menu. In addition to the :guilabel:`Lost` filter, under the :guilabel:`Filters` column, click :guilabel:`Add Custom Filter`, which opens an :guilabel:`Add Custom Filter` pop-up window." +msgstr "" + +#: ../../content/applications/sales/crm/pipeline/lost_opportunities.rst:95 +msgid "On the :guilabel:`Add Custom Filter` pop-up window, click in the first field, and type `Lost Reason` in the :guilabel:`Search...` bar, or scroll to search through the list to locate it. Then, click into the next field, and select :guilabel:`=` from the drop-down menu. Click into the third field, and select a lost reason from the drop-down menu. Finally, click :guilabel:`Add`." msgstr "" #: ../../content/applications/sales/crm/pipeline/lost_opportunities.rst:-1 msgid "Search bar with custom filter added for lost reason." msgstr "" -#: ../../content/applications/sales/crm/pipeline/lost_opportunities.rst:81 +#: ../../content/applications/sales/crm/pipeline/lost_opportunities.rst:105 +msgid "To view results for more than one lost reason, select the operator :guilabel:`is in` in the second field of the custom filter in the :guilabel:`Add Custom Filter` pop-up window. Choosing this operator makes it possible to choose multiple lost reasons in the third field." +msgstr "" + +#: ../../content/applications/sales/crm/pipeline/lost_opportunities.rst:0 +msgid "Add Custom Filter pop-up with multiple lost reasons selected." +msgstr "" + +#: ../../content/applications/sales/crm/pipeline/lost_opportunities.rst:114 msgid "Restore lost opportunities" msgstr "" -#: ../../content/applications/sales/crm/pipeline/lost_opportunities.rst:83 -msgid "To restore a lost opportunity, navigate to the main :guilabel:`Pipeline` dashboard on the *CRM* app, open the :guilabel:`Filters` drop-down menu, and select the :guilabel:`Lost` option. Doing so reveals all the lost opportunities on the :guilabel:`Pipeline` page." +#: ../../content/applications/sales/crm/pipeline/lost_opportunities.rst:116 +msgid "To restore a lost opportunity, open the :menuselection:`CRM app` to reveal the :guilabel:`Pipeline` dashboard. Or, navigate to :menuselection:`CRM app --> Sales --> My Pipeline`. From here, click the :guilabel:`🔻(triangle pointed down)` icon to the right of the :guilabel:`Search...` bar to open the drop-down menu that contains :guilabel:`Filters`, :guilabel:`Group By`, and :guilabel:`Favorites` columns." msgstr "" -#: ../../content/applications/sales/crm/pipeline/lost_opportunities.rst:87 -msgid "Then, click on the kanban card of the desired lost opportunity to restore, which opens that lead's detail form." +#: ../../content/applications/sales/crm/pipeline/lost_opportunities.rst:122 +msgid "Under the :guilabel:`Filters` column, select :guilabel:`Lost`. Doing so reveals all the lost opportunities on the :guilabel:`Pipeline` page." msgstr "" -#: ../../content/applications/sales/crm/pipeline/lost_opportunities.rst:90 -msgid "From the lost lead's detail form, click :guilabel:`Restore` in the upper-left corner. Doing so removes the red :guilabel:`Lost` banner from the lead form, signifying the lead has been restored." +#: ../../content/applications/sales/crm/pipeline/lost_opportunities.rst:126 +msgid "To see all opportunities in the database, remove the default :guilabel:`My Pipeline` filter from the :guilabel:`Search...` bar." +msgstr "" + +#: ../../content/applications/sales/crm/pipeline/lost_opportunities.rst:129 +msgid "Then, click on the Kanban card of the desired lost opportunity to restore, which opens that opportunity's detail form." +msgstr "" + +#: ../../content/applications/sales/crm/pipeline/lost_opportunities.rst:132 +msgid "From the lost opportunity's detail form, click :guilabel:`Restore` in the upper-left corner. Doing so removes the red :guilabel:`Lost` banner from the opportunity form, signifying the opportunity has been restored." msgstr "" #: ../../content/applications/sales/crm/pipeline/lost_opportunities.rst:-1 msgid "Lost opportunity with emphasis on the Restore button." msgstr "" -#: ../../content/applications/sales/crm/pipeline/lost_opportunities.rst:98 +#: ../../content/applications/sales/crm/pipeline/lost_opportunities.rst:141 msgid "Restore multiple opportunities at once" msgstr "" -#: ../../content/applications/sales/crm/pipeline/lost_opportunities.rst:100 +#: ../../content/applications/sales/crm/pipeline/lost_opportunities.rst:143 msgid "To restore multiple opportunities at once, navigate to the main :guilabel:`Pipeline` dashboard in the *CRM* app, open the :guilabel:`Filters` drop-down menu, and select the :guilabel:`Lost` option." msgstr "" -#: ../../content/applications/sales/crm/pipeline/lost_opportunities.rst:103 -msgid "Next, select the list view option, which is represented by the three-line :guilabel:`☰ (list)` icon in the upper-right corner. Doing so places all the leads from the :guilabel:`Pipeline` page in a list form. With the list form chosen, select the checkbox to the left of each desired opportunity/lead to be restored." +#: ../../content/applications/sales/crm/pipeline/lost_opportunities.rst:146 +msgid "Next, select the list view option, represented by the :guilabel:`≣ (list)` icon in the upper-right corner. Doing so places all the opportunities from the :guilabel:`Pipeline` page in a list view. With the list view chosen, select the checkbox to the left of each opportunity to be restored." msgstr "" -#: ../../content/applications/sales/crm/pipeline/lost_opportunities.rst:108 -msgid "Once the desired opportunities/leads have been selected, click the :guilabel:`⚙️ Action (gear)` drop-down menu at the top of the :guilabel:`Pipeline` page. From the :guilabel:`⚙️ Action (gear)` drop-down menu, select :guilabel:`Unarchive`." +#: ../../content/applications/sales/crm/pipeline/lost_opportunities.rst:150 +msgid "Once the desired opportunities have been selected, click the :guilabel:`⚙️ Actions` drop-down menu at the top of the :guilabel:`Pipeline` page. From the :guilabel:`⚙️ Actions` drop-down menu, select :guilabel:`Unarchive`." msgstr "" -#: ../../content/applications/sales/crm/pipeline/lost_opportunities.rst:112 -msgid "Doing so removes those selected lost opportunities from the :guilabel:`Pipeline` page because they no longer fit into the `Lost` filter criteria. To reveal these newly-restored leads, delete the `Lost` filter from the search bar." +#: ../../content/applications/sales/crm/pipeline/lost_opportunities.rst:154 +msgid "Doing so removes those selected opportunities from the :guilabel:`Pipeline` page because they no longer fit the :guilabel:`Lost` filter criteria. Delete the :guilabel:`Lost` filter from the search bar to reveal these newly-restored opportunities." msgstr "" #: ../../content/applications/sales/crm/pipeline/lost_opportunities.rst:-1 msgid "Action button from list view with the Unarchive option emphasized." msgstr "" -#: ../../content/applications/sales/crm/pipeline/lost_opportunities.rst:121 +#: ../../content/applications/sales/crm/pipeline/lost_opportunities.rst:163 +msgid "Manage lost leads" +msgstr "" + +#: ../../content/applications/sales/crm/pipeline/lost_opportunities.rst:165 +msgid "If *Leads* are enabled on a database, they can be marked as *lost* in the same manner as opportunities. Leads use the same :ref:`lost reasons ` as opportunities." +msgstr "" + +#: ../../content/applications/sales/crm/pipeline/lost_opportunities.rst:169 +msgid "To enable leads, navigate to :menuselection:`CRM app --> Configuration --> Settings` and check the :guilabel:`Leads` checkbox. Then, click :guilabel:`Save`. This adds a new :guilabel:`Leads` menu to the header menu bar at the top of the page." +msgstr "" + +#: ../../content/applications/sales/crm/pipeline/lost_opportunities.rst:174 +msgid "Mark a lead as lost" +msgstr "" + +#: ../../content/applications/sales/crm/pipeline/lost_opportunities.rst:176 +msgid "To mark a lead as lost, navigate to :menuselection:`CRM app --> Leads`, and select a lead from the list. Doing so reveals that lead's detail form." +msgstr "" + +#: ../../content/applications/sales/crm/pipeline/lost_opportunities.rst:179 +msgid "Then, click :guilabel:`Lost`, located at the top of the lead's detail form." +msgstr "" + +#: ../../content/applications/sales/crm/pipeline/lost_opportunities.rst:185 +msgid "Additional notes and comments can be added below the lost reason designated in the :guilabel:`Closing Note` field." +msgstr "" + +#: ../../content/applications/sales/crm/pipeline/lost_opportunities.rst:192 +msgid "Restore lost leads" +msgstr "" + +#: ../../content/applications/sales/crm/pipeline/lost_opportunities.rst:194 +msgid "To restore a lost lead, navigate to :menuselection:`CRM app --> Leads`, then click the :guilabel:`🔻 (triangle pointed down)` icon to the right of the :guilabel:`Search...` bar to open the drop-down menu that contains the :guilabel:`Filters`, :guilabel:`Group By`, and :guilabel:`Favorites` columns." +msgstr "" + +#: ../../content/applications/sales/crm/pipeline/lost_opportunities.rst:198 +msgid "Under the :guilabel:`Filters` column, select :guilabel:`Lost`. Doing so reveals all the lost leads on the :guilabel:`Leads` page." +msgstr "" + +#: ../../content/applications/sales/crm/pipeline/lost_opportunities.rst:201 +msgid "Then, click on the desired lost lead to restore, which opens that lead's detail form." +msgstr "" + +#: ../../content/applications/sales/crm/pipeline/lost_opportunities.rst:203 +msgid "From the lost lead's detail form, click :guilabel:`Restore` in the upper-left corner. Doing so removes the red :guilabel:`Lost` banner from the lead form, signifying the lead has been restored." +msgstr "" + +#: ../../content/applications/sales/crm/pipeline/lost_opportunities.rst:207 +msgid "Restore multiple leads at once" +msgstr "" + +#: ../../content/applications/sales/crm/pipeline/lost_opportunities.rst:209 +msgid "To restore multiple leads at once, navigate to :menuselection:`CRM app --> Leads`, open the :guilabel:`Filters` drop-down menu, and select the :guilabel:`Lost` option. Select the checkbox to the left of each lead to be restored." +msgstr "" + +#: ../../content/applications/sales/crm/pipeline/lost_opportunities.rst:213 +msgid "Once the desired leads have been selected, click the :guilabel:`⚙️ Actions` drop-down menu at the top of the :guilabel:`Leads` page. From the :guilabel:`⚙️ Actions` drop-down menu, select :guilabel:`Unarchive`." +msgstr "" + +#: ../../content/applications/sales/crm/pipeline/lost_opportunities.rst:217 +msgid "Doing so removes those selected leads from the :guilabel:`Leads` page because they no longer fit the :guilabel:`Lost` filter criteria. Delete the :guilabel:`Lost` filter from the :guilabel:`Search...` bar to reveal these newly-restored leads." +msgstr "" + +#: ../../content/applications/sales/crm/pipeline/lost_opportunities.rst:222 msgid ":doc:`../performance/win_loss`" msgstr "" +#: ../../content/applications/sales/crm/pipeline/merge_similar.rst:3 +msgid "Merge similar leads and opportunities" +msgstr "" + +#: ../../content/applications/sales/crm/pipeline/merge_similar.rst:5 +msgid "Odoo automatically detects similar *leads* and *opportunities* within the *CRM* app. Identifying these duplicated records allows them to be merged without losing any information in the process. Not only does this help keep the *pipeline* organized, but it also prevents customers from being contacted by more than one salesperson." +msgstr "" + +#: ../../content/applications/sales/crm/pipeline/merge_similar.rst:11 +msgid "When merging opportunities, no information is lost. Data from the other opportunity is logged in the chatter, and the information fields, for reference." +msgstr "" + +#: ../../content/applications/sales/crm/pipeline/merge_similar.rst:15 +msgid "Identify similar leads and opportunities" +msgstr "" + +#: ../../content/applications/sales/crm/pipeline/merge_similar.rst:17 +msgid "Similar leads and opportunities are identified by comparing the *email address* and *phone number* of the associated contact. If a similar lead/opportunity is found, a *Similar Leads* smart button appears at the top of the lead (or opportunity) record." +msgstr "" + +#: ../../content/applications/sales/crm/pipeline/merge_similar.rst:-1 +msgid "An opportunity record with emphasis on the Similar Leads smart button." +msgstr "" + +#: ../../content/applications/sales/crm/pipeline/merge_similar.rst:26 +msgid "Comparing similar leads and opportunities" +msgstr "" + +#: ../../content/applications/sales/crm/pipeline/merge_similar.rst:28 +msgid "To compare the details of similar leads/opportunities, navigate to :menuselection:`CRM app --> Pipeline` or :menuselection:`CRM app --> Leads`. Open a lead or opportunity, and click the Doing so opens a Kanban view that only displays similar leads/opportunities. Click on a card to view the details for the lead/opportunity, and confirm if they should be merged." +msgstr "" + +#: ../../content/applications/sales/crm/pipeline/merge_similar.rst:34 +msgid "Merging similar leads and opportunities" +msgstr "" + +#: ../../content/applications/sales/crm/pipeline/merge_similar.rst:42 +msgid "After confirming that the leads/opportunities should be merged, return to the Kanban view using the breadcrumb link, or by clicking the :guilabel:`Similar Leads` smart button. Click the :guilabel:`≣ (view list)` icon to change to list view." +msgstr "" + +#: ../../content/applications/sales/crm/pipeline/merge_similar.rst:46 +msgid "Check the box on the left of the page for the leads/opportunities to be merged. Then, click the :guilabel:`⚙️ Actions` icon at the top of the page, to reveal a drop-down menu. From that drop-down menu, select the :guilabel:`Merge` option to merge the selected opportunities or leads." +msgstr "" + +#: ../../content/applications/sales/crm/pipeline/merge_similar.rst:50 +msgid "When :guilabel:`Merge` is selected from the :guilabel:`⚙️ Actions` drop-down menu, a :guilabel:`Merge` pop-up modal appears. In that pop-up modal, under the :guilabel:`Assign opportunities to` heading, select a :guilabel:`Salesperson` and :guilabel:`Sales Team` from the appropriate drop-down menus." +msgstr "" + +#: ../../content/applications/sales/crm/pipeline/merge_similar.rst:55 +msgid "Below those fields, the leads/opportunities to merge are listed, along with their related information. To merge those selected leads/opportunities, click :guilabel:`Merge`." +msgstr "" + +#: ../../content/applications/sales/crm/pipeline/merge_similar.rst:-1 +msgid "List of similar leads and opportunities selected for merge in the CRM app." +msgstr "" + +#: ../../content/applications/sales/crm/pipeline/merge_similar.rst:63 +msgid "Merging is an irreversible action. Do **not** merge leads/opportunities unless absolutely certain they should be combined." +msgstr "" + +#: ../../content/applications/sales/crm/pipeline/merge_similar.rst:67 +msgid "When leads/opportunities should not be merged" +msgstr "" + +#: ../../content/applications/sales/crm/pipeline/merge_similar.rst:69 +msgid "There may be instances where a similar lead or opportunity is identified, but should *not* be merged. These circumstances vary, based on the processes of the sales team and organization. Some potential scenarios are listed below." +msgstr "" + +#: ../../content/applications/sales/crm/pipeline/merge_similar.rst:74 +msgid "Lost leads" +msgstr "" + +#: ../../content/applications/sales/crm/pipeline/merge_similar.rst:76 +msgid "If a lead/opportunity has been marked as :doc:`lost `, it can still be merged with an active lead or opportunity. The resulting lead/opportunity is marked active, and added to the pipeline." +msgstr "" + +#: ../../content/applications/sales/crm/pipeline/merge_similar.rst:81 +msgid "Different contact within an organization" +msgstr "" + +#: ../../content/applications/sales/crm/pipeline/merge_similar.rst:83 +msgid "Leads/opportunities from the same organization, but with different points of contact, may not have the same needs. In this case, it is beneficial to *not* merge these records, though assigning the same salesperson, or sales team, can prevent duplicated work and miscommunication." +msgstr "" + +#: ../../content/applications/sales/crm/pipeline/merge_similar.rst:88 +msgid "Existing duplicates with more than one salesperson" +msgstr "" + +#: ../../content/applications/sales/crm/pipeline/merge_similar.rst:90 +msgid "If more than one lead/opportunity exists in the database, there may be multiple salespeople assigned to them, who are actively working on them independently. While these leads/opportunities may need to be managed separately, it is recommended that any affected salespeople be tagged in an internal note for visibility." +msgstr "" + +#: ../../content/applications/sales/crm/pipeline/merge_similar.rst:96 +msgid "Contact information is similar but not exact" +msgstr "" + +#: ../../content/applications/sales/crm/pipeline/merge_similar.rst:98 +msgid "Similar leads and opportunities are identified by comparing the email addresses and phone numbers of the associated contacts. However, if the email address is *similar*, but not *exact*, they may need to remain independent." +msgstr "" + +#: ../../content/applications/sales/crm/pipeline/merge_similar.rst:103 +msgid "Three different leads were added to the pipeline and assigned to different salespeople. They were identified as *Similar Leads* due to the email addresses of the contacts." +msgstr "" + +#: ../../content/applications/sales/crm/pipeline/merge_similar.rst:106 +msgid "Two of the leads appear to come from the same individual, `Robin`, and have identical email addresses. These leads should be merged." +msgstr "" + +#: ../../content/applications/sales/crm/pipeline/merge_similar.rst:109 +msgid "The third lead has the same email domain, but the address is different, as is the contact name. While this lead is most likely from the same organization, it is from a different contact, and should **not** be merged." +msgstr "" + +#: ../../content/applications/sales/crm/pipeline/merge_similar.rst:0 +msgid "List of similar leads with emphasis on the contact information in the CRM app." +msgstr "" + #: ../../content/applications/sales/crm/pipeline/multi_sales_team.rst:3 msgid "Multiple sales teams" msgstr "" @@ -2551,54 +3292,6 @@ msgstr "" msgid "To manually assign leads to this sales team, click on the :guilabel:`Assign Leads` button at the top of the sales team configuration page. This will assign any leads that are currently unassigned and match this team's specified domain." msgstr "" -#: ../../content/applications/sales/crm/track_leads/prospect_visits.rst:3 -msgid "Track your prospects visits" -msgstr "" - -#: ../../content/applications/sales/crm/track_leads/prospect_visits.rst:5 -msgid "Tracking your website pages will give you much more information about the interests of your website visitors." -msgstr "" - -#: ../../content/applications/sales/crm/track_leads/prospect_visits.rst:8 -msgid "Every tracked page they visit will be recorded on your lead/opportunity if they use the contact form on your website." -msgstr "" - -#: ../../content/applications/sales/crm/track_leads/prospect_visits.rst:14 -msgid "To use this feature, install the free module *Lead Scoring* under your *Apps* page (only available in Odoo Enterprise)." -msgstr "" - -#: ../../content/applications/sales/crm/track_leads/prospect_visits.rst:21 -msgid "Track a webpage" -msgstr "" - -#: ../../content/applications/sales/crm/track_leads/prospect_visits.rst:23 -msgid "Go to any static page you want to track on your website and under the *Promote* tab you will find *Optimize SEO*" -msgstr "" - -#: ../../content/applications/sales/crm/track_leads/prospect_visits.rst:29 -msgid "There you will see a *Track Page* checkbox to track this page." -msgstr "" - -#: ../../content/applications/sales/crm/track_leads/prospect_visits.rst:35 -msgid "See visited pages in your leads/opportunities" -msgstr "" - -#: ../../content/applications/sales/crm/track_leads/prospect_visits.rst:37 -msgid "Now each time a lead is created from the contact form it will keep track of the pages visited by that visitor. You have two ways to see those pages, on the top right corner of your lead/opportunity you can see a *Page Views* button but also further down you will see them in the chatter." -msgstr "" - -#: ../../content/applications/sales/crm/track_leads/prospect_visits.rst:43 -msgid "Both will update if the viewers comes back to your website and visits more pages." -msgstr "" - -#: ../../content/applications/sales/crm/track_leads/prospect_visits.rst:52 -msgid "The feature will not repeat multiple viewings of the same pages in the chatter." -msgstr "" - -#: ../../content/applications/sales/crm/track_leads/prospect_visits.rst:55 -msgid "Your customers will no longer be able to keep any secrets from you!" -msgstr "" - #: ../../content/applications/sales/crm/track_leads/quality_leads_report.rst:3 msgid "Quality leads report" msgstr "" @@ -3285,6 +3978,7 @@ msgstr "" #: ../../content/applications/sales/point_of_sale/combos.rst:54 #: ../../content/applications/sales/point_of_sale/employee_login.rst:26 +#: ../../content/applications/sales/point_of_sale/pricing/electronic_labels.rst:122 #: ../../content/applications/sales/point_of_sale/shop/ship_later.rst:32 msgid "Practical application" msgstr "" @@ -3345,113 +4039,162 @@ msgstr "" msgid "Making a product available in your POS." msgstr "" +#: ../../content/applications/sales/point_of_sale/configuration/epos_printers.rst:3 +msgid "ePOS printers" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/configuration/epos_printers.rst:5 +msgid "ePOS printers are designed to work seamlessly with Point of Sale systems. Once connected, these devices automatically share information, allowing for direct printing of tickets from the POS system to the ePOS printer." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/configuration/epos_printers.rst:10 +msgid "Epson printers using Wi-Fi/Ethernet connections and following the `EPOS SDK Javascript protocol `_ are compatible with Odoo **without** needing an :doc:`IoT Box `." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/configuration/epos_printers.rst:14 +msgid "Thermal printers using ESC/POS or StarPRNT protocol are compatible **with** an :doc:`IoT Box `." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/configuration/epos_printers.rst:16 +msgid "Epson printers using only USB connections are compatible **with** an :doc:`IoT Box `." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/configuration/epos_printers.rst:18 +msgid "Epson printers that connect via Bluetooth are **not compatible**." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/configuration/epos_printers.rst:21 +msgid ":doc:`https`" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/configuration/epos_printers.rst:22 +#: ../../content/applications/sales/point_of_sale/configuration/https.rst:22 +msgid ":doc:`epos_ssc`" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/configuration/epos_printers.rst:25 +msgid "Directly supported ePOS printers" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/configuration/epos_printers.rst:27 +msgid "The following ePOS printers are directly compatible with Odoo without needing an :doc:`IoT Box `." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/configuration/epos_printers.rst:30 +msgid "Epson TM-m30 i/ii/iii (Wi-Fi/Ethernet models only; Recommended)" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/configuration/epos_printers.rst:31 +msgid "Epson TM-H6000IV-DT (Receipt printer only)" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/configuration/epos_printers.rst:32 +msgid "Epson TM-T70II-DT" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/configuration/epos_printers.rst:33 +msgid "Epson TM-T88V-DT" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/configuration/epos_printers.rst:34 +msgid "Epson TM-L90-i" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/configuration/epos_printers.rst:35 +msgid "Epson TM-T20II-i" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/configuration/epos_printers.rst:36 +msgid "Epson TM-T70-i" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/configuration/epos_printers.rst:37 +msgid "Epson TM-T82II-i" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/configuration/epos_printers.rst:38 +msgid "Epson TM-T83II-i" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/configuration/epos_printers.rst:39 +msgid "Epson TM-U220-i" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/configuration/epos_printers.rst:40 +msgid "Epson TM-m10" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/configuration/epos_printers.rst:41 +msgid "Epson TM-P20 (Wi-Fi® model)" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/configuration/epos_printers.rst:42 +msgid "Epson TM-P60II (Receipt: Wi-Fi® model)" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/configuration/epos_printers.rst:43 +msgid "Epson TM-P60II (Peeler: Wi-Fi® model)" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/configuration/epos_printers.rst:44 +msgid "Epson TM-P80 (Wi-Fi® model)" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/configuration/epos_printers.rst:47 +msgid "ePOS printers with IoT Box integration" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/configuration/epos_printers.rst:49 +msgid "The following printers require an :doc:`IoT Box ` to be compatible with Odoo:" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/configuration/epos_printers.rst:52 +msgid "Epson TM-T20 family (incompatible ePOS software)" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/configuration/epos_printers.rst:53 +msgid "Epson TM-T88 family (incompatible ePOS software)" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/configuration/epos_printers.rst:54 +msgid "Epson TM-U220 family (incompatible ePOS software)" +msgstr "" + #: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:5 msgid "Self-signed certificate for ePOS printers" msgstr "" #: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:7 -msgid "ePOS printers are designed to work seamlessly with Point of Sale systems. Once connected, the two devices automatically share information, enabling the direct printing of tickets from the POS system to the ePOS printer." -msgstr "" - -#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:12 -msgid "These `Epson ePOS printers `_ are compatible with Odoo:" +msgid "To work with Odoo, some printer 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:15 -msgid "TM-H6000IV-DT (Receipt printer only)" -msgstr "" - -#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:16 -msgid "TM-T70II-DT" -msgstr "" - -#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:17 -msgid "TM-T88V-DT" -msgstr "" - -#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:18 -msgid "TM-L90-i" -msgstr "" - -#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:19 -msgid "TM-T20II-i" -msgstr "" - -#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:20 -msgid "TM-T70-i" -msgstr "" - -#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:21 -msgid "TM-T82II-i" -msgstr "" - -#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:22 -msgid "TM-T83II-i" -msgstr "" - -#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:23 -msgid "TM-T88V-i" -msgstr "" - -#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:24 -msgid "TM-U220-i" -msgstr "" - -#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:25 -msgid "TM-m10" -msgstr "" - -#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:26 -msgid "TM-m30" -msgstr "" - -#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:27 -msgid "TM-P20 (Wi-Fi® model)" -msgstr "" - -#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:28 -msgid "TM-P60II (Receipt: Wi-Fi® model)" -msgstr "" - -#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:29 -msgid "TM-P60II (Peeler: Wi-Fi® model)" -msgstr "" - -#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:30 -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 ` 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 msgid "The connection is lost after closing the browser window. Therefore, this method should only be used as a **workaround** or as a pre-requisite for the :ref:`following instructions `." msgstr "" -#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:47 +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:22 msgid "Generate, export, and import self-signed certificates" msgstr "" -#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:49 +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:24 msgid "For a long-term solution, you must generate a **self-signed certificate**. Then, export and import it into your browser." msgstr "" -#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:53 +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:28 msgid "**Generating** an SSL certificate should only be done **once**. If you create another certificate, devices using the previous one will lose HTTPS access." msgstr "" -#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:58 +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:33 msgid "Windows 10 & Linux OS" msgstr "" -#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:62 -#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:191 +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:37 +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:166 msgid "Generate a self-signed certificate" msgstr "" -#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:64 -#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:193 +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:39 +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:168 msgid "Navigate to the ePOS' IP address (e.g., `https://192.168.1.25`) and force the connection by clicking :guilabel:`Advanced` and :guilabel:`Proceed to [IP address] (unsafe)`." msgstr "" @@ -3459,44 +4202,44 @@ msgstr "" msgid "warning page about the connection privacy on Google Chrome" msgstr "" -#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:72 -#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:201 +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:47 +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:176 msgid "Warning page on Google Chrome, Windows 10" msgstr "" -#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:74 -#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:203 +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:49 +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:178 msgid "Then, sign in using your printer credentials to access the ePOS printer settings. To sign in, enter `epson` in the :guilabel:`ID` field and your printer serial number in the :guilabel:`Password` field." msgstr "" -#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:78 -#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:207 +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:53 +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:182 msgid "Click :guilabel:`Certificate List` in the :guilabel:`Authentication` section, and click :guilabel:`create` to generate a new **Self-Signed Certificate**. The :guilabel:`Common Name` should be automatically filled out. If not, fill it in with the printer IP address number. Select the years the certificate will be valid in the :guilabel:`Validity Period` field, click :guilabel:`Create`, and :guilabel:`Reset` or manually restart the printer." msgstr "" -#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:85 -#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:214 +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:60 +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:189 msgid "The self-signed certificate is generated. Reload the page and click :guilabel:`SSL/TLS` in the :guilabel:`Security` section to ensure **Selfsigned Certificate** is correctly selected in the :guilabel:`Server Certificate` section." msgstr "" -#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:89 -#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:218 +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:64 +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:193 msgid "Export a self-signed certificate" msgstr "" -#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:91 -#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:220 +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:66 +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:195 msgid "The export process is heavily dependent on the :abbr:`OS (Operating System)` and the browser. Start by accessing your ePOS printer settings on your web browser by navigating to its IP address (e.g., `https://192.168.1.25`). Then, force the connection as explained in the **Generate a self-signed certificate tab**." msgstr "" -#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:96 -#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:156 -#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:225 +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:71 +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:131 +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:200 msgid "If you are using **Google Chrome**," msgstr "" -#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:98 -#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:227 +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:73 +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:202 msgid "click :guilabel:`Not secure` next to the search bar, and :guilabel:`Certificate is not valid`;" msgstr "" @@ -3504,45 +4247,45 @@ msgstr "" msgid "Connection to the printer not secure button in Google Chrome browser." msgstr "" -#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:104 -#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:233 +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:79 +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:208 msgid "go to the :guilabel:`Details` tab and click :guilabel:`Export`;" msgstr "" -#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:105 -#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:234 +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:80 +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:209 msgid "add `.crt` at the end of the file name to ensure it has the correct extension;" msgstr "" -#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:106 -#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:235 +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:81 +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:210 msgid "select :guilabel:`Base64-encoded ASCII, single certificate`, at the bottom of the pop-up window;" msgstr "" -#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:108 -#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:125 -#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:237 -#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:254 +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:83 +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:100 +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:212 +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:229 msgid "save, and the certificate is exported." msgstr "" -#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:111 +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:86 msgid "Make sure that the certificate ends with the extension `.crt`. Otherwise, some browsers might not see the file during the import process." msgstr "" -#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:114 -#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:168 -#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:243 +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:89 +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:143 +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:218 msgid "If you are using **Mozilla Firefox**," msgstr "" -#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:116 -#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:245 +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:91 +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:220 msgid "click the **lock-shaped** icon on the left of the address bar;" msgstr "" -#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:117 -#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:246 +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:92 +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:221 msgid "go to :menuselection:`Connection not secure --> More information --> Security tab --> View certificate`;" msgstr "" @@ -3550,122 +4293,122 @@ msgstr "" msgid "Connection is not secure button in Mozilla Firefox browser" msgstr "" -#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:123 -#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:252 +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:98 +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:227 msgid "scroll down to the :guilabel:`Miscellaneous` section;" msgstr "" -#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:124 -#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:253 +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:99 +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:228 msgid "click :guilabel:`PEM (cert)` in the :guilabel:`Download` section;" msgstr "" -#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:127 +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:102 msgid "Import a self-signed certificate" msgstr "" -#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:129 +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:104 msgid "The import process is heavily dependent on the :abbr:`OS (Operating System)` and the browser." msgstr "" -#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:134 +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:109 msgid "Windows 10" msgstr "" -#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:136 +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:111 msgid "Windows 10 manages certificates, which means that self-signed certificates must be imported from the certification file rather than the browser. To do so," msgstr "" -#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:139 +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:114 msgid "open the Windows File Explorer and locate the downloaded certification file;" msgstr "" -#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:140 +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:115 msgid "right-click on the certification file and click :guilabel:`Install Certificate`;" msgstr "" -#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:142 +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:117 msgid "select where to install the certificate and for whom - either for the :guilabel:`Current User` or all users (:guilabel:`Local Machine`). Then, click :guilabel:`Next`;" msgstr "" -#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:145 +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:120 msgid "on the `Certificate Store` screen, tick :guilabel:`Place all certificates in the following store`, click :guilabel:`Browse...`, and select :guilabel:`Trusted Root Certification Authorities`;" msgstr "" -#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:151 +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:126 msgid "click :guilabel:`Finish`, accept the pop-up security window;" msgstr "" -#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:152 +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:127 msgid "restart the computer to make sure that the changes are applied." msgstr "" -#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:154 +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:129 msgid "Linux" msgstr "" -#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:158 +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:133 msgid "open Chrome;" msgstr "" -#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:159 +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:134 msgid "go to :menuselection:`Settings --> Privacy and security --> Security --> Manage certificates`;" msgstr "" -#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:161 +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:136 msgid "go to the :guilabel:`Authorities` tab, click :guilabel:`Import`, and select the exported certification file;" msgstr "" -#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:163 +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:138 msgid "accept all warnings;" msgstr "" -#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:164 +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:139 msgid "click :guilabel:`ok`;" msgstr "" -#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:165 -#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:175 +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:140 +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:150 msgid "restart your browser." msgstr "" -#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:170 +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:145 msgid "open Firefox;" msgstr "" -#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:171 +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:146 msgid "go to :menuselection:`Settings --> Privacy & Security --> Security --> View Certificates... --> Import`;" msgstr "" -#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:173 +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:148 msgid "select the exported certification file;" msgstr "" -#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:174 +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:149 msgid "tick the checkboxes and validate;" msgstr "" -#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:177 +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:152 msgid "Mac OS" msgstr "" -#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:179 +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:154 msgid "On Mac OS, you can secure the connection for all browsers by following these steps:" msgstr "" -#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:181 +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:156 msgid "open Safari and navigate to your printer's IP address. Doing so leads to a warning page;" msgstr "" -#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:182 +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:157 msgid "on the warning page, go to :menuselection:`Show Details --> visit this website --> Visit Website`, validate;" msgstr "" -#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:184 +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:159 msgid "reboot the printer so you can use it with any other browser." msgstr "" -#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:186 +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:161 msgid "To generate and export an SSL certificate and send it to IOS devices, open **Google Chrome** or **Mozilla Firefox**. Then," msgstr "" @@ -3677,7 +4420,7 @@ msgstr "" msgid "Connection to the printer not secure button in Google Chrome" msgstr "" -#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:240 +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:215 msgid "Make sure that the certificate ends with the extension `.crt`. Otherwise, some browsers might not find the file during the import process." msgstr "" @@ -3685,99 +4428,99 @@ msgstr "" msgid "Connection is not secure button in Mozilla Firefox" msgstr "" -#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:256 +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:231 msgid "Android OS" msgstr "" -#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:258 +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:233 msgid "To import an SSL certificate into an Android device, first create and export it from a computer. Next, transfer the `.crt` file to the device using email, Bluetooth, or USB. Once the file is on the device," msgstr "" -#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:262 +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:237 msgid "open the settings and search for `certificate`;" msgstr "" -#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:263 +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:238 msgid "click :guilabel:`Certificate AC` (Install from device storage);" msgstr "" -#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:264 +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:239 msgid "select the certificate file to install it on the device." msgstr "" -#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:267 +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:242 msgid "The specific steps for installing a certificate may vary depending on the version of Android and the device manufacturer." msgstr "" -#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:270 +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:245 msgid "iOS" msgstr "" -#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:272 +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:247 msgid "To import an SSL certificate into an iOS device, first create and export it from a computer. Then, transfer the `.crt` file to the device using email, Bluetooth, or any file-sharing service." msgstr "" -#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:276 +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:251 msgid "Downloading this file triggers a warning pop-up window. Click :guilabel:`Allow` to download the configuration profile, and close the second pop-up window. Then," msgstr "" -#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:279 +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:254 msgid "go to the **Settings App** on the iOS device;" msgstr "" -#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:280 +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:255 msgid "click :guilabel:`Profile Downloaded` under the user's details box;" msgstr "" -#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:281 +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:256 msgid "locate the downloaded `.crt` file and select it;" msgstr "" -#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:282 +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:257 msgid "click :guilabel:`Install` on the top right of the screen;" msgstr "" -#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:283 +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:258 msgid "if a passcode is set on the device, enter the passcode;" msgstr "" -#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:284 +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:259 msgid "click :guilabel:`Install` on the top right of the certificate warning screen and the pop-up window;" msgstr "" -#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:286 +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:261 msgid "click :guilabel:`Done`." msgstr "" -#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:290 +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:265 msgid "The certificate is installed, but it still needs to be authenticated. To do so," msgstr "" -#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:292 +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:267 msgid "go to :menuselection:`Settings --> General --> About > Certificate Trust Settings`;" msgstr "" -#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:293 +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:268 msgid "enable the installed certificate using the **slide button**;" msgstr "" -#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:294 +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:269 msgid "click :guilabel:`Continue` on the pop-up window." msgstr "" -#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:297 +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:272 msgid "If you need to export SSL certificates from an operating system or web browser that has not been mentioned, search for `export SSL certificate` + `the name of your browser or operating system` in your preferred search engine." msgstr "" -#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:300 +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:275 msgid "Similarly, to import SSL certificates from an unmentioned OS or browser, search for `import SSL certificate root authority` + `the name of your browser or operating system` in your preferred search engine." msgstr "" -#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:305 +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:280 msgid "Check if the certificate was imported correctly" msgstr "" -#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:307 +#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:282 msgid "To confirm your printer's connection is secure, connect to its IP address using HTTPS. For example, navigate to `https://192.168.1.25` in your browser. If the SSL certificate has been applied correctly, you should no longer see a warning page, and the address bar should display a padlock icon, indicating that the connection is secure." msgstr "" @@ -3786,7 +4529,7 @@ msgid "Secure connection (HTTPS)" msgstr "" #: ../../content/applications/sales/point_of_sale/configuration/https.rst:5 -msgid "If **Direct Devices** is enabled in a Point of Sale settings (for example, if you use an ePos printer), HTTP becomes the default protocol." +msgid "If **Direct Devices** is enabled in a Point of Sale settings (for example, if you use an :doc:`ePos printer `), HTTP becomes the default protocol." msgstr "" #: ../../content/applications/sales/point_of_sale/configuration/https.rst:9 @@ -3809,10 +4552,6 @@ msgstr "" msgid "**Value**: `True`" msgstr "" -#: ../../content/applications/sales/point_of_sale/configuration/https.rst:22 -msgid ":doc:`epos_ssc`" -msgstr "" - #: ../../content/applications/sales/point_of_sale/employee_login.rst:3 msgid "Multi-employee management" msgstr "" @@ -3902,10 +4641,10 @@ msgid ":doc:`payment_methods/terminals`." 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:46 +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/adyen.rst:84 +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/ingenico.rst:49 #: ../../content/applications/sales/point_of_sale/payment_methods/terminals/six.rst:63 -#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/worldline.rst:72 +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/worldline.rst:81 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 "" @@ -3966,98 +4705,114 @@ msgid "Connecting an **Adyen payment terminal** allows you to offer a fluid paym msgstr "" #: ../../content/applications/sales/point_of_sale/payment_methods/terminals/adyen.rst:9 -msgid "Adyen works only with businesses processing **more** than **10 million annually** or invoicing a **minimum** of **1,000** transactions **per month**." +msgid "Adyen payment terminals do not require an :doc:`IoT Box `." msgstr "" -#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/adyen.rst:15 +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/adyen.rst:10 +msgid "Adyen terminals can be used in many countries, but not worldwide. Check the `List of countries supported by Adyen `_." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/adyen.rst:12 +msgid "Adyen works only with businesses processing more than **$10 million annually** or invoicing a minimum of **1,000 transactions per month**." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/adyen.rst:16 +msgid "`List of payment methods supported by Adyen `_" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/adyen.rst:17 +msgid "`List of Adyen terminals `_" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/adyen.rst:22 msgid "Start by creating your Adyen account on `Adyen's website `_. Then, board your terminal following the steps described on your terminal's screen." msgstr "" -#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/adyen.rst:19 -msgid "`Adyen Docs - Payment terminal quickstart guides `_." +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/adyen.rst:26 +msgid "`Adyen Docs - Payment terminal quickstart guides `_" msgstr "" -#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/adyen.rst:25 +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/adyen.rst:31 msgid "Generate an Adyen API key" msgstr "" -#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/adyen.rst:27 +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/adyen.rst:33 msgid "The **Adyen API key** is used to authenticate requests from your Adyen terminal. To generate an API key, go to your :menuselection:`Adyen account --> Developers --> API credentials`, and **create** new credentials or select **existing** ones. Click :guilabel:`Generate an API key` and save the key to paste it into the Odoo :guilabel:`Adyen API key` field at :ref:`the payment method creation `." msgstr "" -#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/adyen.rst:34 +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/adyen.rst:40 msgid "`Adyen Docs - API credentials `_." msgstr "" -#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/adyen.rst:40 +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/adyen.rst:46 msgid "Locate the Adyen terminal identifier" msgstr "" -#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/adyen.rst:42 +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/adyen.rst:48 msgid "The **Adyen Terminal Identifier** is the terminal's serial number, which is used to identify the hardware." msgstr "" -#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/adyen.rst:45 +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/adyen.rst:51 msgid "To find this number, go to your :menuselection:`Adyen account --> Point of Sale --> Terminals`, select the terminal to link with, and save its serial number to paste it into the Odoo :guilabel:`Adyen Terminal Identifier` field at :ref:`the payment method creation `." msgstr "" -#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/adyen.rst:51 +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/adyen.rst:57 msgid "Set the Event URLs" msgstr "" -#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/adyen.rst:53 +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/adyen.rst:59 msgid "For Odoo to know when a payment is made, you must configure the terminal **Event URLs**. To do so," msgstr "" -#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/adyen.rst:55 +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/adyen.rst:61 msgid "Log in to `Adyen's website `_;" msgstr "" -#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/adyen.rst:56 +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/adyen.rst:62 msgid "Go to :menuselection:`Adyen's dashboard --> Point of Sale --> Terminals` and select the connected terminal;" msgstr "" -#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/adyen.rst:58 +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/adyen.rst:64 msgid "From the terminal settings, click :guilabel:`Integrations`;" msgstr "" -#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/adyen.rst:59 +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/adyen.rst:65 msgid "Set the :guilabel:`Switch to decrypted mode to edit this setting` field as :guilabel:`Decrypted`;" msgstr "" -#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/adyen.rst:60 +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/adyen.rst:66 msgid "Click the **pencil icon** button and enter your server address, followed by `/pos_adyen/notification` in the :guilabel:`Event URLs` field;" msgstr "" -#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/adyen.rst:62 +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/adyen.rst:68 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:37 +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/adyen.rst:73 +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/ingenico.rst:40 #: ../../content/applications/sales/point_of_sale/payment_methods/terminals/six.rst:53 -#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/stripe.rst:15 -#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/worldline.rst:63 +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/stripe.rst:22 +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/worldline.rst:72 msgid "Configure the payment method" msgstr "" -#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/adyen.rst:69 +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/adyen.rst:75 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:`Adyen` in the :guilabel:`Use a Payment Terminal` field." msgstr "" -#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/adyen.rst:73 +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/adyen.rst:79 msgid "Finally, fill in the mandatory fields with your :ref:`Adyen API key `, :ref:`Adyen Terminal Identifier `, and :guilabel:`Adyen Merchant Account`." msgstr "" -#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/adyen.rst:83 -#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/ingenico.rst:51 +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/adyen.rst:89 +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/ingenico.rst:54 #: ../../content/applications/sales/point_of_sale/payment_methods/terminals/six.rst:68 -#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/stripe.rst:86 -#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/worldline.rst:87 +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/stripe.rst:93 +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/worldline.rst:96 msgid "Pay with a payment terminal" msgstr "" -#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/adyen.rst:85 +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/adyen.rst:91 msgid "When processing a payment, select :guilabel:`Adyen` as the payment method. Check the amount and click on :guilabel:`Send`. Once the payment is successful, the status changes to :guilabel:`Payment Successful`." msgstr "" @@ -4071,7 +4826,7 @@ msgstr "" msgid "This option is only available after receiving an error message informing you that the connection failed." msgstr "" -#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/adyen.rst:94 +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/adyen.rst:100 msgid "To cancel the payment request, click on :guilabel:`cancel`." msgstr "" @@ -4085,52 +4840,62 @@ msgstr "" msgid "Connecting a payment terminal allows you to offer a fluid payment flow to your customers and ease the work of your cashiers." msgstr "" -#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/ingenico.rst:8 -msgid "Please note that Ingenico is currently only available for customers in the Benelux." +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/ingenico.rst:9 +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/worldline.rst:9 +msgid "Worldline payment terminals require an :doc:`IoT Box `." msgstr "" -#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/ingenico.rst:15 -#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/worldline.rst:15 +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/ingenico.rst:10 +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/worldline.rst:10 +msgid "Worldline is currently only available in Belgium, the Netherlands and Luxembourg." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/ingenico.rst:11 +msgid "Odoo works with the Ingenico Lane/, Desk/, and Move/ payment terminals as they support the TLV communication protocol through TCP/IP." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/ingenico.rst:18 +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/worldline.rst:19 msgid "Connect an IoT Box" msgstr "" -#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/ingenico.rst:17 +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/ingenico.rst:20 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:23 +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/ingenico.rst:26 msgid "Configure the Lane/5000 for Ingenico BENELUX" msgstr "" -#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/ingenico.rst:25 +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/ingenico.rst:28 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:28 +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/ingenico.rst:31 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:39 +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/ingenico.rst:42 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:53 +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/ingenico.rst:56 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:62 +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/ingenico.rst:65 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:65 +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/ingenico.rst:68 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:71 +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/ingenico.rst:74 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:74 +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/ingenico.rst:77 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 "" @@ -4203,7 +4968,7 @@ msgid "Paying with Six" msgstr "" #: ../../content/applications/sales/point_of_sale/payment_methods/terminals/six.rst:79 -#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/worldline.rst:92 +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/worldline.rst:101 msgid "Once your payment is processed, the type of card used and the transaction ID appear on the payment record." msgstr "" @@ -4224,30 +4989,46 @@ msgid "Stripe" msgstr "" #: ../../content/applications/sales/point_of_sale/payment_methods/terminals/stripe.rst:9 -msgid ":doc:`Use Stripe as payment provider. <../../../../finance/payment_providers/stripe>`" +msgid "Stripe payment terminals do not require an :doc:`IoT Box `" msgstr "" -#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/stripe.rst:17 -msgid "Activate **Stripe** in the settings by going to :menuselection:`Point of Sale --> Configuration --> Settings --> Payment Terminals` and enabling :guilabel:`Stripe`." +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/stripe.rst:10 +msgid "Stripe terminals can be used in many countries, but not worldwide. Check the `global availability for Stripe Terminal `_." msgstr "" -#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/stripe.rst:20 -msgid "Then, create the payment method:" +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/stripe.rst:12 +msgid "Stripe's integration works with `Stripe Terminal smart readers `_" msgstr "" -#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/stripe.rst:22 -msgid "Go to :menuselection:`Point of Sale --> Configuration --> Payment Methods`, click :guilabel:`Create`, and complete the :guilabel:`Method` field with your payment method's name;" +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/stripe.rst:15 +msgid ":doc:`Stripe as payment provider <../../../../finance/payment_providers/stripe>`" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/stripe.rst:16 +msgid "`List of payment methods supported by Stripe `_" msgstr "" #: ../../content/applications/sales/point_of_sale/payment_methods/terminals/stripe.rst:24 -msgid "Set the :guilabel:`Journal` field as :guilabel:`Bank` and the :guilabel:`Use a Payment Terminal` field as :guilabel:`Stripe`;" -msgstr "" - -#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/stripe.rst:26 -msgid "Enter your payment terminal serial number in the :guilabel:`Stripe Serial Number` field;" +msgid "Activate **Stripe** in the settings by going to :menuselection:`Point of Sale --> Configuration --> Settings --> Payment Terminals` and enabling :guilabel:`Stripe`." msgstr "" #: ../../content/applications/sales/point_of_sale/payment_methods/terminals/stripe.rst:27 +msgid "Then, create the payment method:" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/stripe.rst:29 +msgid "Go to :menuselection:`Point of Sale --> Configuration --> Payment Methods`, click :guilabel:`Create`, and complete the :guilabel:`Method` field with your payment method's name;" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/stripe.rst:31 +msgid "Set the :guilabel:`Journal` field as :guilabel:`Bank` and the :guilabel:`Use a Payment Terminal` field as :guilabel:`Stripe`;" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/stripe.rst:33 +msgid "Enter your payment terminal serial number in the :guilabel:`Stripe Serial Number` field;" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/stripe.rst:34 msgid "Click :guilabel:`Don't forget to complete Stripe connect before using this payment method.`" msgstr "" @@ -4255,23 +5036,23 @@ msgstr "" msgid "payment method creation form" msgstr "" -#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/stripe.rst:34 +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/stripe.rst:41 msgid "Click :guilabel:`Identify Customer` to allow this payment method **exclusively** for identified customers. For any unidentified customers to be able to pay with Stripe, leave the :guilabel:`Identify Customer` field unchecked." msgstr "" -#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/stripe.rst:37 +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/stripe.rst:44 msgid "The :guilabel:`Outstanding Account` and the :guilabel:`Intermediary Account` can stay empty to use the default accounts." msgstr "" -#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/stripe.rst:39 +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/stripe.rst:46 msgid "Find your payment terminal serial number under the device or on `Stripe's dashboard `_." msgstr "" -#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/stripe.rst:43 +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/stripe.rst:50 msgid "Connect Stripe to Odoo" msgstr "" -#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/stripe.rst:45 +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/stripe.rst:52 msgid "Click :guilabel:`Connect Stripe`. Doing so redirects you automatically to a configuration page. Fill in all the information to create your Stripe account and link it with Odoo. Once the forms are completed, the API keys (:guilabel:`Publishable Key` and :guilabel:`Secret Key`) can be retrieved on **Stripe's** website. To do so, click :guilabel:`Get your Secret and Publishable keys`, click the keys to copy them, and paste them into the corresponding fields in Odoo. Your terminal is ready to be configured in a POS." msgstr "" @@ -4279,83 +5060,83 @@ msgstr "" msgid "stripe connection form" msgstr "" -#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/stripe.rst:57 +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/stripe.rst:64 msgid "When you use **Stripe** exclusively in Point of Sale, you only need the **Secret Key** to use your terminal." msgstr "" -#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/stripe.rst:59 +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/stripe.rst:66 msgid "When you use Stripe as **payment provider**, the :guilabel:`State` can stay set as :guilabel:`Disabled`." msgstr "" -#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/stripe.rst:61 +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/stripe.rst:68 msgid "For databases hosted **On-Premise**, the :guilabel:`Connect Stripe` button does not work. To retrieve the API keys manually, log in to your `Stripe dashboard `_, type `API` in the search bar, and click :guilabel:`Developers > API`." msgstr "" -#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/stripe.rst:67 +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/stripe.rst:74 msgid "Configure the payment terminal" msgstr "" -#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/stripe.rst:69 +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/stripe.rst:76 msgid "Swipe right on your payment terminal, click :guilabel:`Settings`, enter the admin PIN code, validate and select your network." msgstr "" -#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/stripe.rst:73 +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/stripe.rst:80 msgid "The device must be connected to a secured WI-FI network." msgstr "" -#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/stripe.rst:74 +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/stripe.rst:81 msgid "Your Odoo database and payment terminal must share the same network." msgstr "" -#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/stripe.rst:75 +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/stripe.rst:82 msgid "You must enter the admin PIN code to access your payment terminal settings. By default, this code is `07139`." msgstr "" -#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/stripe.rst:79 +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/stripe.rst:86 msgid "Link the payment method to a POS" msgstr "" -#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/stripe.rst:81 +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/stripe.rst:88 msgid "To add a **payment method** to your point of sale, go to :menuselection:`Point of Sale --> Configuration --> Settings`. Select the POS, scroll down to the :guilabel:`Payments` section, and add your payment method for **Stripe** in the :guilabel:`Payment Methods` field." msgstr "" -#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/stripe.rst:88 +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/stripe.rst:95 msgid "When processing a payment, select :guilabel:`Stripe` as the payment method. Check the amount and click :guilabel:`Send`. Once the payment is successful, the status changes to :guilabel:`Payment Successful`. To cancel the payment request, click :guilabel:`cancel`." msgstr "" -#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/stripe.rst:97 +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/stripe.rst:104 msgid "The terminal must have at least 10% battery level to use it." msgstr "" -#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/stripe.rst:98 +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/stripe.rst:105 msgid "The device does not work for payments under €0.50." msgstr "" -#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/stripe.rst:101 +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/stripe.rst:108 msgid "Troubleshooting" msgstr "" -#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/stripe.rst:104 +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/stripe.rst:111 msgid "Payment terminal unavailable in your Stripe account" msgstr "" -#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/stripe.rst:106 +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/stripe.rst:113 msgid "If the payment terminal is unavailable in your Stripe account, you must add it manually:" msgstr "" -#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/stripe.rst:108 +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/stripe.rst:115 msgid "Log into your `Stripe's dashboard `_ and go to :menuselection:`Stripe dashboard --> Payments --> Readers --> Locations`;" msgstr "" -#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/stripe.rst:110 +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/stripe.rst:117 msgid "Add a location by clicking the :guilabel:`+ New` button or selecting an already created location;" msgstr "" -#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/stripe.rst:111 +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/stripe.rst:118 msgid "Click the :guilabel:`+ New` button in the :guilabel:`Readers` box and fill in the required information." msgstr "" -#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/stripe.rst:115 +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/stripe.rst:122 msgid "You must provide a **registration code**. To retrieve that code, swipe right on your device, enter the admin PIN code (by default: `07139`), validate, and click :guilabel:`Generate a registration code`." msgstr "" @@ -4403,43 +5184,43 @@ msgstr "" msgid "Worldline" msgstr "" -#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/worldline.rst:9 -msgid "Please note that Worldline is currently only available in the Benelux." +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/worldline.rst:11 +msgid "Odoo is compatible with Worldline terminals that use the CTEP protocol (e.g., the Yomani XR and Yoximo terminals). If you have any doubts, contact your payment provider to ensure your terminal's compatibility." msgstr "" -#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/worldline.rst:17 +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/worldline.rst:21 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 +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/worldline.rst:26 msgid "Configure the protocol" msgstr "" -#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/worldline.rst:24 +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/worldline.rst:28 msgid "From your terminal, click on :menuselection:`\".\" --> 3 --> stop --> 3 --> 0 --> 9`. Enter the technician password **\"1235789\"** and click on :menuselection:`OK --> 4 --> 2`. Then, click on :menuselection:`Change --> CTEP (as Protocole ECR) --> OK`. Click on **OK** thrice on the subsequent screens (*CTEP ticket ECR*, *ECR ticket width*, and *Character set*). Finally, press **Stop** three times; the terminal automatically restarts." msgstr "" -#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/worldline.rst:31 +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/worldline.rst:35 msgid "Set the IP address" msgstr "" -#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/worldline.rst:33 +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/worldline.rst:37 msgid "From your terminal, click on :menuselection:`\".\" --> 3 --> stop --> 3 --> 0 --> 9`. Enter the technician password **\"1235789\"** and click on :menuselection:`OK --> 4 --> 9`. Then, click on :menuselection:`Change --> TCP/IP` (*TCP physical configuration* screen) :menuselection:`--> OK --> OK` (*TCP Configuration client* screen)." msgstr "" -#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/worldline.rst:38 +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/worldline.rst:42 msgid "Finally, set up the hostname and port number." msgstr "" -#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/worldline.rst:41 +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/worldline.rst:45 msgid "Hostname" msgstr "" -#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/worldline.rst:44 +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/worldline.rst:48 msgid "To set up the hostname, enter your IoT box's IP address' sequence numbers and press **OK** at each \".\" until you reach the colon symbol." msgstr "" -#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/worldline.rst:45 +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/worldline.rst:49 msgid "Then, press **OK** twice." msgstr "" @@ -4451,51 +5232,55 @@ msgstr "" msgid "On the *Hostname screen*, type :menuselection:`10 --> OK --> 30 --> OK --> 19 --> OK --> 4 --> OK --> OK`." msgstr "" -#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/worldline.rst:53 +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/worldline.rst:57 msgid "Your IoT box's IP address is available in your IoT Box application's database." msgstr "" -#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/worldline.rst:56 +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/worldline.rst:60 msgid "Port number" msgstr "" -#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/worldline.rst:58 +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/worldline.rst:62 msgid "On the *Port number* screen, enter **9001** (or **9050** for Windows) and click on :menuselection:`OK` (*ECR protocol SSL no*) :menuselection:`--> OK`. Click on **Stop** three times; the terminal automatically restarts." msgstr "" -#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/worldline.rst:65 +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/worldline.rst:67 +msgid "For **Windows** IoT devices, it is necessary to add a firewall exception. Follow the :ref:`additional instructions in the Windows IoT documentation ` to add the exception to Windows Firewall." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/worldline.rst:74 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:`Worldline` 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/worldline.rst:79 +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/worldline.rst:88 msgid "Technician password: `1235789`" msgstr "" -#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/worldline.rst:80 +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/worldline.rst:89 msgid "To reach Wordline's technical assistance, call `02 727 61 11` and choose \"merchant\". Your call is automatically transferred to the desired service." msgstr "" -#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/worldline.rst:82 +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/worldline.rst:91 msgid "Configure the cashier terminal if you have both a customer and a cashier terminal." msgstr "" -#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/worldline.rst:83 +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/worldline.rst:92 msgid "To avoid blocking the terminal, check the initial configuration beforehand." msgstr "" -#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/worldline.rst:84 +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/worldline.rst:93 msgid "Set a fixed IP to your IoT Box’s router to prevent losing the connexion." msgstr "" -#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/worldline.rst:89 +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/worldline.rst:98 msgid "When processing a payment, select *Worldline* as payment method. Check the amount and click on *Send*. Once the payment is successful, the status changes to *Payment Successful*." msgstr "" -#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/worldline.rst:99 +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/worldline.rst:108 msgid "In case of connexion issues between Odoo and the payment terminal, force the payment by clicking on *Force Done*, which allows you to validate the order. This option is only available after receiving an error message informing you that the connection failed." msgstr "" -#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/worldline.rst:102 +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/worldline.rst:111 msgid "To cancel the payment request, click on **cancel**." msgstr "" @@ -4711,6 +5496,233 @@ msgstr "" msgid "Click on it to instantly update the prices with the selected pricelist. Then, you can finalize the order." msgstr "" +#: ../../content/applications/sales/point_of_sale/pricing/electronic_labels.rst:3 +msgid "Electronic shelf labels" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/pricing/electronic_labels.rst:5 +msgid "Electronic shelf labels allow you to display product information like prices and barcodes on store shelves and to synchronize them remotely from the backend. This removes the need to print new labels when product information changes." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/pricing/electronic_labels.rst:-1 +msgid "electronic label from Pricer" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/pricing/electronic_labels.rst:13 +msgid "Odoo uses electronic labels from `Pricer `_." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/pricing/electronic_labels.rst:19 +msgid "Pricer setup" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/pricing/electronic_labels.rst:21 +msgid "`Get in touch with Pricer `_ to create and configure your Pricer account." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/pricing/electronic_labels.rst:23 +msgid "Create your stores: one pricer store equates to one physical store." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/pricing/electronic_labels.rst:24 +msgid "Link as many transceivers as needed to the Pricer store(s)." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/pricing/electronic_labels.rst:25 +msgid "Create the following variables to share product information between your Odoo database system and Pricer. These variables act like placeholders on the label template." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/pricing/electronic_labels.rst:28 +msgid "`itemId`: this holds the unique internal identifier assigned to each product" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/pricing/electronic_labels.rst:29 +msgid "`itemName`: the actual name of the product" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/pricing/electronic_labels.rst:30 +msgid "`price`: the selling price of the product, including any applicable taxes" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/pricing/electronic_labels.rst:31 +msgid "`presentation`: the template name used in Pricer for displaying the product information on the label" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/pricing/electronic_labels.rst:33 +msgid "`currency`: the currency of your company (e.g., USD, EUR)" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/pricing/electronic_labels.rst:34 +msgid "`barcode`: the barcode number associated with each product" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/pricing/electronic_labels.rst:37 +msgid "The names for these variables must be **identical** in your Pricer database." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/pricing/electronic_labels.rst:39 +msgid "Create a template named `NORMAL`. This template is used to display information on your digital tags." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/pricing/electronic_labels.rst:42 +msgid "Once your account, stores, variables, and template are configured on Pricer, you can proceed with the setup of your Odoo database." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/pricing/electronic_labels.rst:46 +msgid "The account associated with your Pricer store must have access to send API requests to Pricer." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/pricing/electronic_labels.rst:49 +msgid "Odoo setup" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/pricing/electronic_labels.rst:51 +msgid "As a pre-requisite, :ref:`activate ` the :guilabel:`POS Pricer` module *(technical name: pos_pricer)* to have all the required features to use Pricer electronic tags." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/pricing/electronic_labels.rst:-1 +msgid "Installing POS Pricer module from Apps" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/pricing/electronic_labels.rst:57 +msgid "Once the module is activated, configure your :ref:`pricer stores ` and associate :ref:`Pricer tags ` with your products." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/pricing/electronic_labels.rst:63 +msgid "Pricer stores" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/pricing/electronic_labels.rst:65 +msgid "Similarly to the configuration in Pricer, you need to create one pricer store per physical location. To do so, go to :menuselection:`Point of Sale --> Configuration --> Pricer Stores`, click :guilabel:`New`, and fill in the line with the required information:" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/pricing/electronic_labels.rst:69 +msgid ":guilabel:`Store Name`: you can put any name of your liking." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/pricing/electronic_labels.rst:70 +msgid ":guilabel:`Pricer Tenant Name`: the name of your company account in Pricer, usually followed by `-country_code`. This value is provided by Pricer." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/pricing/electronic_labels.rst:72 +msgid ":guilabel:`Pricer Login`: the login of your Pricer account." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/pricing/electronic_labels.rst:73 +msgid ":guilabel:`Pricer Password`: the password of your Pricer account." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/pricing/electronic_labels.rst:74 +msgid ":guilabel:`Pricer Store ID`: the ID of the related Pricer store as defined on your Pricer database." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/pricing/electronic_labels.rst:-1 +msgid "Configuring a Pricer Store" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/pricing/electronic_labels.rst:81 +msgid "The :guilabel:`Pricer Tags` column is updated automatically when a label is linked to a product." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/pricing/electronic_labels.rst:83 +msgid "The :guilabel:`Last Update` and :guilabel:`Last Update Status` columns are updated automatically when the tags are updated." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/pricing/electronic_labels.rst:89 +msgid "Pricer tags" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/pricing/electronic_labels.rst:91 +msgid "For a label to display specific product information, the label needs to be associated with the product. To do so:" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/pricing/electronic_labels.rst:94 +msgid "Open the product form by going to :menuselection:`Point of Sale --> Products --> Products` and clicking :guilabel:`New` or selecting an existing product." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/pricing/electronic_labels.rst:98 +msgid "If you are creating a new product, configure and save it before associating any Pricer tags." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/pricing/electronic_labels.rst:100 +msgid "Go to the :guilabel:`Sales` tab, scroll to the :guilabel:`Pricer` section, and select the corresponding :guilabel:`Pricer Store`." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/pricing/electronic_labels.rst:0 +msgid "Linking Pricer tags to products" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/pricing/electronic_labels.rst:107 +msgid "Fill in the :guilabel:`Pricer tags ids` field by copying the label's ID from the label itself or scanning its barcode." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/pricing/electronic_labels.rst:111 +msgid "Pricer tag IDs are composed of a letter followed by 16 digits." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/pricing/electronic_labels.rst:114 +msgid "We recommended using a barcode scanner to speed up the encoding process." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/pricing/electronic_labels.rst:115 +msgid "When setting up Pricer with Odoo for the first time, it is recommended that you configure only one product first. Before configuring more products, ensure you can display their information on a Pricer tag." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/pricing/electronic_labels.rst:119 +msgid "Now that you have a product associated with a Pricer tag, we can send its information to Pricer." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/pricing/electronic_labels.rst:124 +msgid "Odoo automatically sends requests to Pricer to synchronize the tags every 12 hours if you make any modifications to:" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/pricing/electronic_labels.rst:127 +#: ../../content/applications/sales/point_of_sale/pricing/electronic_labels.rst:137 +msgid "Product name, price, barcode, or customer taxes" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/pricing/electronic_labels.rst:128 +#: ../../content/applications/sales/point_of_sale/pricing/electronic_labels.rst:138 +msgid "Currency" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/pricing/electronic_labels.rst:129 +#: ../../content/applications/sales/point_of_sale/pricing/electronic_labels.rst:139 +msgid "Associated Pricer store or Pricer tags" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/pricing/electronic_labels.rst:131 +msgid "To force the update, activate the :ref:`developer mode `. Then:" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/pricing/electronic_labels.rst:133 +msgid "Go to :menuselection:`Point of Sale --> Configuration --> Pricer Store`." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/pricing/electronic_labels.rst:134 +msgid "Select the desired store(s)." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/pricing/electronic_labels.rst:135 +msgid "Click :guilabel:`Update tags` to update all tags affected by changes to:" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/pricing/electronic_labels.rst:141 +msgid "Alternatively, click :guilabel:`Update all tags` to force the update of every tag, regardless of whether changes were made." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/pricing/electronic_labels.rst:-1 +msgid "Update all Pricer tags" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/pricing/electronic_labels.rst:147 +msgid "If Pricer has processed and accepted the request, the status field shows :guilabel:`Update successfully sent to Pricer`. If there is any issue, the system displays an error message." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/pricing/electronic_labels.rst:151 +msgid "If a request sent to Pricer fails, Odoo still considers that the product has been updated. In that case, we recommend forcing the update of all tags." +msgstr "" + #: ../../content/applications/sales/point_of_sale/pricing/fiscal_position.rst:3 msgid "Flexible taxes (fiscal positions)" msgstr "" @@ -5000,11 +6012,15 @@ msgstr "" msgid ":doc:`restaurant/bill_printing`" msgstr "" -#: ../../content/applications/sales/point_of_sale/receipts_invoices.rst:24 +#: ../../content/applications/sales/point_of_sale/receipts_invoices.rst:22 +msgid ":doc:`configuration/epos_printers`" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/receipts_invoices.rst:25 msgid "Reprint a receipt" msgstr "" -#: ../../content/applications/sales/point_of_sale/receipts_invoices.rst:26 +#: ../../content/applications/sales/point_of_sale/receipts_invoices.rst:27 msgid "From the POS interface, click :guilabel:`Orders`, open the dropdown selection menu next to the search bar, and change the default :guilabel:`All active orders` filter to :guilabel:`Paid`. Then, select the corresponding order and click :guilabel:`Print Receipt`." msgstr "" @@ -5012,23 +6028,23 @@ msgstr "" msgid "Print receipt button from the backend" msgstr "" -#: ../../content/applications/sales/point_of_sale/receipts_invoices.rst:34 +#: ../../content/applications/sales/point_of_sale/receipts_invoices.rst:35 msgid "You can filter the list of orders using the search bar. Type in your reference and click :guilabel:`Receipt Number`, :guilabel:`Date`, or :guilabel:`Customer`." msgstr "" -#: ../../content/applications/sales/point_of_sale/receipts_invoices.rst:40 +#: ../../content/applications/sales/point_of_sale/receipts_invoices.rst:41 msgid "Invoices" msgstr "" -#: ../../content/applications/sales/point_of_sale/receipts_invoices.rst:42 +#: ../../content/applications/sales/point_of_sale/receipts_invoices.rst:43 msgid "Point of Sale allows you to issue and print invoices for :ref:`registered customers ` upon payment and retrieve all past invoiced orders." msgstr "" -#: ../../content/applications/sales/point_of_sale/receipts_invoices.rst:46 +#: ../../content/applications/sales/point_of_sale/receipts_invoices.rst:47 msgid "An invoice created in a POS creates an entry into the corresponding :ref:`accounting journal `, previously :ref:`set up `." msgstr "" -#: ../../content/applications/sales/point_of_sale/receipts_invoices.rst:54 +#: ../../content/applications/sales/point_of_sale/receipts_invoices.rst:55 msgid "To define what journals will be used for a specific POS, go to the :ref:`POS' settings ` and scroll down to the accounting section. Then, you can determine the accounting journals used by default for orders and invoices in the :guilabel:`Default Journals` section." msgstr "" @@ -5036,35 +6052,35 @@ msgstr "" msgid "accounting section in the POS settings" msgstr "" -#: ../../content/applications/sales/point_of_sale/receipts_invoices.rst:63 +#: ../../content/applications/sales/point_of_sale/receipts_invoices.rst:64 msgid "Invoice a customer" msgstr "" -#: ../../content/applications/sales/point_of_sale/receipts_invoices.rst:65 +#: ../../content/applications/sales/point_of_sale/receipts_invoices.rst:66 msgid "Upon processing a payment, click :guilabel:`Invoice` underneath the customer's name to issue an invoice for that order." msgstr "" -#: ../../content/applications/sales/point_of_sale/receipts_invoices.rst:68 +#: ../../content/applications/sales/point_of_sale/receipts_invoices.rst:69 msgid "Select the payment method and click :guilabel:`Validate`. The **invoice** is automatically issued and ready to be downloaded and/or printed." msgstr "" -#: ../../content/applications/sales/point_of_sale/receipts_invoices.rst:72 +#: ../../content/applications/sales/point_of_sale/receipts_invoices.rst:73 msgid "To be able to issue an invoice, a :ref:`customer ` must be selected." msgstr "" -#: ../../content/applications/sales/point_of_sale/receipts_invoices.rst:75 +#: ../../content/applications/sales/point_of_sale/receipts_invoices.rst:76 msgid "Retrieve invoices" msgstr "" -#: ../../content/applications/sales/point_of_sale/receipts_invoices.rst:77 +#: ../../content/applications/sales/point_of_sale/receipts_invoices.rst:78 msgid "To retrieve invoices from the **POS dashboard**," msgstr "" -#: ../../content/applications/sales/point_of_sale/receipts_invoices.rst:79 +#: ../../content/applications/sales/point_of_sale/receipts_invoices.rst:80 msgid "access all orders made through your POS by going to :menuselection:`Point of Sale --> Orders --> Orders`;" msgstr "" -#: ../../content/applications/sales/point_of_sale/receipts_invoices.rst:81 +#: ../../content/applications/sales/point_of_sale/receipts_invoices.rst:82 msgid "to access an order's invoice, open the **order form** by selecting the order, then click :guilabel:`Invoice`." msgstr "" @@ -5072,19 +6088,19 @@ msgstr "" msgid "invoice smart button from an order form" msgstr "" -#: ../../content/applications/sales/point_of_sale/receipts_invoices.rst:88 +#: ../../content/applications/sales/point_of_sale/receipts_invoices.rst:89 msgid "**Invoiced orders** can be identified by the :guilabel:`Invoiced` status in the :guilabel:`Status` column." msgstr "" -#: ../../content/applications/sales/point_of_sale/receipts_invoices.rst:90 +#: ../../content/applications/sales/point_of_sale/receipts_invoices.rst:91 msgid "You can filter the list of orders to invoiced orders by clicking :guilabel:`Filters` and :guilabel:`Invoiced`." msgstr "" -#: ../../content/applications/sales/point_of_sale/receipts_invoices.rst:94 +#: ../../content/applications/sales/point_of_sale/receipts_invoices.rst:95 msgid "QR codes to generate invoices" msgstr "" -#: ../../content/applications/sales/point_of_sale/receipts_invoices.rst:96 +#: ../../content/applications/sales/point_of_sale/receipts_invoices.rst:97 msgid "Customers can also request an invoice by scanning the **QR code** printed on their receipt. Upon scanning, they must fill in a form with their billing information and click :guilabel:`Get my invoice`. On the one hand, doing so generates an invoice available for download. On the other hand, the order status goes from :guilabel:`Paid` or :guilabel:`Posted` to :guilabel:`Invoiced` in the Odoo backend." msgstr "" @@ -5092,7 +6108,7 @@ msgstr "" msgid "order status change" msgstr "" -#: ../../content/applications/sales/point_of_sale/receipts_invoices.rst:105 +#: ../../content/applications/sales/point_of_sale/receipts_invoices.rst:106 msgid "To use this feature, you have to enable QR codes on receipts by going to :menuselection:`Point of Sale --> Configuration --> Settings`. Then, select the POS in the :guilabel:`Point of Sale` field, scroll down to the :guilabel:`Bills & Receipts` section and enable :guilabel:`Use QR code on ticket`." msgstr "" @@ -7278,7 +8294,7 @@ msgid "Setting up bill of materials with base product and linked products." msgstr "" #: ../../content/applications/sales/sales/ebay_connector/setup.rst:138 -msgid ":doc:`../../../inventory_and_mrp/manufacturing/management/bill_configuration/`" +msgid ":doc:`../../../inventory_and_mrp/manufacturing/basic_setup/bill_configuration/`" msgstr "" #: ../../content/applications/sales/sales/ebay_connector/setup.rst:140 @@ -12805,51 +13821,55 @@ msgstr "" msgid "When the :guilabel:`Trigger Now` button is clicked, Odoo will trigger the action on *all* linked subscriptions, regardless of possible timed conditions." msgstr "" -#: ../../content/applications/sales/subscriptions/automatic_alerts.rst:131 +#: ../../content/applications/sales/subscriptions/automatic_alerts.rst:132 +msgid "Sending a SMS text message in Odoo requires In-App Purchase (IAP) credit or tokens. For more information on :abbr:`IAP (In-App Purchase)`, visit :doc:`../../essentials/in_app_purchase`. For more information on sending SMS messages, visit :doc:`../../marketing/sms_marketing/essentials/sms_essentials`." +msgstr "" + +#: ../../content/applications/sales/subscriptions/automatic_alerts.rst:137 msgid "If :guilabel:`Timed Condition` is selected in the :guilabel:`Trigger On` field, the following fields appear:" msgstr "" -#: ../../content/applications/sales/subscriptions/automatic_alerts.rst:134 +#: ../../content/applications/sales/subscriptions/automatic_alerts.rst:140 msgid ":guilabel:`Trigger Date`: represents when the condition should be triggered. If left blank, the action is created upon subscription creation *and* updates." msgstr "" -#: ../../content/applications/sales/subscriptions/automatic_alerts.rst:136 +#: ../../content/applications/sales/subscriptions/automatic_alerts.rst:142 msgid ":guilabel:`Delay After Trigger`: select a delayed amount of time (:guilabel:`Minutes`, :guilabel:`Hours`, :guilabel:`Days`, or :guilabel:`Months`) for Odoo to wait before triggering the configured action. If a negative number is entered, the \"delay\" will occur *before* the :guilabel:`Trigger Date`." msgstr "" -#: ../../content/applications/sales/subscriptions/automatic_alerts.rst:142 +#: ../../content/applications/sales/subscriptions/automatic_alerts.rst:148 msgid "Activity section" msgstr "" -#: ../../content/applications/sales/subscriptions/automatic_alerts.rst:144 +#: ../../content/applications/sales/subscriptions/automatic_alerts.rst:150 msgid "If :guilabel:`Create next activity` is selected in the :guilabel:`Action To Do` field, an :guilabel:`Activity` section appears at the bottom of the :guilabel:`Automation Rules` form." msgstr "" -#: ../../content/applications/sales/subscriptions/automatic_alerts.rst:147 +#: ../../content/applications/sales/subscriptions/automatic_alerts.rst:153 msgid ":guilabel:`Activity Type`: select an pre-configured activity type from the drop-down menu." msgstr "" -#: ../../content/applications/sales/subscriptions/automatic_alerts.rst:148 +#: ../../content/applications/sales/subscriptions/automatic_alerts.rst:154 msgid ":guilabel:`Title`: enter a custom title for the chosen activity." msgstr "" -#: ../../content/applications/sales/subscriptions/automatic_alerts.rst:149 +#: ../../content/applications/sales/subscriptions/automatic_alerts.rst:155 msgid ":guilabel:`Note`: leave a note for the employee to whom the activity is assigned." msgstr "" -#: ../../content/applications/sales/subscriptions/automatic_alerts.rst:150 +#: ../../content/applications/sales/subscriptions/automatic_alerts.rst:156 msgid ":guilabel:`Due Date In`: enter an amount of days within which the activity should be completed." msgstr "" -#: ../../content/applications/sales/subscriptions/automatic_alerts.rst:151 +#: ../../content/applications/sales/subscriptions/automatic_alerts.rst:157 msgid ":guilabel:`Assign To`: choose to assign the specified activity to either: :guilabel:`Subscription Salesperson`, :guilabel:`Sales Team Leader`, or :guilabel:`Specific Users`." msgstr "" -#: ../../content/applications/sales/subscriptions/automatic_alerts.rst:155 +#: ../../content/applications/sales/subscriptions/automatic_alerts.rst:161 msgid "If :guilabel:`Specific Users` is selected as the :guilabel:`Assign To` option, a new :guilabel:`Specific Users` field appears beneath it, where a specific employee(s) can be chosen as the assignee(s) for the configured activity." msgstr "" -#: ../../content/applications/sales/subscriptions/automatic_alerts.rst:160 +#: ../../content/applications/sales/subscriptions/automatic_alerts.rst:166 #: ../../content/applications/sales/subscriptions/closing.rst:105 #: ../../content/applications/sales/subscriptions/renewals.rst:85 #: ../../content/applications/sales/subscriptions/reports.rst:406 @@ -12858,7 +13878,7 @@ msgstr "" msgid ":doc:`../subscriptions`" msgstr "" -#: ../../content/applications/sales/subscriptions/automatic_alerts.rst:161 +#: ../../content/applications/sales/subscriptions/automatic_alerts.rst:167 #: ../../content/applications/sales/subscriptions/closing.rst:106 #: ../../content/applications/sales/subscriptions/renewals.rst:86 #: ../../content/applications/sales/subscriptions/reports.rst:407 @@ -12867,7 +13887,7 @@ msgstr "" msgid ":doc:`plans`" msgstr "" -#: ../../content/applications/sales/subscriptions/automatic_alerts.rst:162 +#: ../../content/applications/sales/subscriptions/automatic_alerts.rst:168 #: ../../content/applications/sales/subscriptions/closing.rst:107 #: ../../content/applications/sales/subscriptions/renewals.rst:87 #: ../../content/applications/sales/subscriptions/reports.rst:408 @@ -12876,6 +13896,10 @@ msgstr "" msgid ":doc:`products`" msgstr "" +#: ../../content/applications/sales/subscriptions/automatic_alerts.rst:169 +msgid ":doc:`../../essentials/in_app_purchase`" +msgstr "" + #: ../../content/applications/sales/subscriptions/closing.rst:3 msgid "Close subscriptions" msgstr "" @@ -12989,7 +14013,7 @@ msgid "In addition, the specified :guilabel:`Close Reason` appears on the subscr msgstr "" #: ../../content/applications/sales/subscriptions/ecommerce.rst:3 -msgid "Use subscriptions in the eCommerce shop" +msgid "Subscriptions in the eCommerce shop" msgstr "" #: ../../content/applications/sales/subscriptions/ecommerce.rst:5 @@ -12997,35 +14021,47 @@ msgid "Subscription products can be sold in the Odoo *eCommerce* shop just like msgstr "" #: ../../content/applications/sales/subscriptions/ecommerce.rst:7 -msgid "However, by default, the eCommerce product page only displays the shortest recurrence period listed in the :guilabel:`Time-based pricing` tab of the product form. For example, if a subscription product has *monthly* and *yearly* recurrence periods configured, then only the monthly price appears on the eCommerce page for that product by default." +msgid "However, by default, the eCommerce product page **only** displays the shortest recurrence period listed in the :guilabel:`Recurring Prices` tab of the product form." msgstr "" -#: ../../content/applications/sales/subscriptions/ecommerce.rst:12 +#: ../../content/applications/sales/subscriptions/ecommerce.rst:10 +msgid "For example, if a subscription product has *monthly* and *annaul* recurrence periods configured, then *only* the monthly price appears on the eCommerce page for that product, by default." +msgstr "" + +#: ../../content/applications/sales/subscriptions/ecommerce.rst:13 msgid "To add more recurrence periods to the eCommerce product page, create a *product variant* for each recurrence period." msgstr "" -#: ../../content/applications/sales/subscriptions/ecommerce.rst:16 +#: ../../content/applications/sales/subscriptions/ecommerce.rst:17 msgid ":doc:`Configure subscription products `" msgstr "" -#: ../../content/applications/sales/subscriptions/ecommerce.rst:17 +#: ../../content/applications/sales/subscriptions/ecommerce.rst:18 msgid ":doc:`Product variants `" msgstr "" -#: ../../content/applications/sales/subscriptions/ecommerce.rst:20 +#: ../../content/applications/sales/subscriptions/ecommerce.rst:21 msgid "Create recurrence periods as product variants" msgstr "" -#: ../../content/applications/sales/subscriptions/ecommerce.rst:22 -msgid "To set up each recurrence period as a product variant, go to :menuselection:`Subscriptions --> Subscriptions --> Products` and select a product. In the :guilabel:`Attributes & Variants` tab, click :guilabel:`Add a line`." +#: ../../content/applications/sales/subscriptions/ecommerce.rst:23 +msgid "To set up each recurrence period as a product variant, go to :menuselection:`Subscriptions app --> Products --> Products`, and select a product. In the :guilabel:`Attributes & Variants` tab, click :guilabel:`Add a line`." msgstr "" -#: ../../content/applications/sales/subscriptions/ecommerce.rst:26 -msgid "Create an :guilabel:`Attribute` called `Billing Period` (or something similar) by typing in the name and clicking :guilabel:`Create`. This attribute name appears as the option heading on the product page of the eCommerce shop." +#: ../../content/applications/sales/subscriptions/ecommerce.rst:27 +msgid "Then proceed to create an :guilabel:`Attribute` called `Billing Period` (or something similar), by typing in the name, and clicking :guilabel:`Create` from the mini drop-down menu that appears. This attribute name appears as option heading on the product page of the eCommerce shop." msgstr "" -#: ../../content/applications/sales/subscriptions/ecommerce.rst:30 -msgid "Next, create :guilabel:`Values` that correspond to the recurrence periods that are configured in the :guilabel:`Time-based pricing` tab of the product form. Type in the name of the recurrence period, then click :guilabel:`Create`. These value names appear as selectable options on the product page of the eCommerce shop." +#: ../../content/applications/sales/subscriptions/ecommerce.rst:31 +msgid "Next, create :guilabel:`Values` that correspond to the recurrence periods that are configured in the :guilabel:`Recurring Prices` tab of the product form." +msgstr "" + +#: ../../content/applications/sales/subscriptions/ecommerce.rst:34 +msgid "To do that, type in the name of the recurrence period in the :guilabel:`Values` column, on the same :guilabel:`Attribute` line, in the :guilabel:`Attributes & Variants` tab. Then, click :guilabel:`Create` from the mini drop-down menu that appears." +msgstr "" + +#: ../../content/applications/sales/subscriptions/ecommerce.rst:38 +msgid "These value names appear as selectable options on the product page of the eCommerce shop." msgstr "" #: ../../content/applications/sales/subscriptions/ecommerce.rst:-1 @@ -13033,16 +14069,16 @@ msgid "Recurrence periods configured as product variants in the \"Attributes & V "the product form." msgstr "" -#: ../../content/applications/sales/subscriptions/ecommerce.rst:40 -msgid "Click on the :guilabel:`☁️ (cloud)` icon at the top of the page to save manually. After saving, a :guilabel:`Product Variants` column appears on the :guilabel:`Time-based pricing` tab. Assign the product variants to their corresponding recurrence periods and prices." +#: ../../content/applications/sales/subscriptions/ecommerce.rst:45 +msgid "With those configurations in place and saved, a :guilabel:`Product Variants` column appears in the :guilabel:`Recurring Prices` tab. Proceed to assign the different :guilabel:`Product Variants` to their corresponding recurrence :guilabel:`Period` and :guilabel:`Price`." msgstr "" #: ../../content/applications/sales/subscriptions/ecommerce.rst:-1 msgid "Product variants on the \"Time-based pricing\" tab of the product form." msgstr "" -#: ../../content/applications/sales/subscriptions/ecommerce.rst:48 -msgid "The product variants are now available for selection on the eCommerce product page." +#: ../../content/applications/sales/subscriptions/ecommerce.rst:53 +msgid "After following those aforementioned steps, the product variants are available for selection on the eCommerce product page." msgstr "" #: ../../content/applications/sales/subscriptions/ecommerce.rst:-1 diff --git a/locale/sources/services.pot b/locale/sources/services.pot index d5a38a6e4..5fcc8037a 100644 --- a/locale/sources/services.pot +++ b/locale/sources/services.pot @@ -8,7 +8,7 @@ msgid "" msgstr "" "Project-Id-Version: Odoo 17.0\n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2024-03-25 16:01+0000\n" +"POT-Creation-Date: 2024-04-30 09:16+0000\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME \n" "Language-Team: LANGUAGE \n" @@ -3419,51 +3419,47 @@ msgstr "" msgid "To enable recurring tasks, go to :menuselection:`Project --> Configuration --> Settings`, then activate :guilabel:`Recurring Tasks`, and press :guilabel:`Save`." msgstr "" -#: ../../content/applications/services/project/tasks/recurring_tasks.rst:18 -msgid "Recurring tasks are now activated on all existing projects. The feature can be deactivated on an individual project by clicking the drop-down menu button :guilabel:`⋮` next to the project name, then going to :menuselection:`Settings --> Settings --> Task Management` and disabling :guilabel:`Recurring Tasks`." -msgstr "" - -#: ../../content/applications/services/project/tasks/recurring_tasks.rst:24 +#: ../../content/applications/services/project/tasks/recurring_tasks.rst:19 msgid "Set up task recurrence" msgstr "" -#: ../../content/applications/services/project/tasks/recurring_tasks.rst:26 +#: ../../content/applications/services/project/tasks/recurring_tasks.rst:21 msgid "In an existing task, press the :guilabel:`Recurrent` button next to the :guilabel:`Planned date`. Then, configure :guilabel:`Repeat Every` field according to your needs." msgstr "" -#: ../../content/applications/services/project/tasks/recurring_tasks.rst:29 +#: ../../content/applications/services/project/tasks/recurring_tasks.rst:24 msgid "A new task in recurrence will be created once either of this conditions is met: - Previous task in recurrence has been closed. - On the day of the planned recurrence." msgstr "" -#: ../../content/applications/services/project/tasks/recurring_tasks.rst:33 +#: ../../content/applications/services/project/tasks/recurring_tasks.rst:28 msgid "The new task is created on your project dashboard with the following configuration:" msgstr "" -#: ../../content/applications/services/project/tasks/recurring_tasks.rst:35 +#: ../../content/applications/services/project/tasks/recurring_tasks.rst:30 msgid ":guilabel:`Stage`: first stage of the project dashboard (:guilabel:`New` or equivalent);" msgstr "" -#: ../../content/applications/services/project/tasks/recurring_tasks.rst:36 +#: ../../content/applications/services/project/tasks/recurring_tasks.rst:31 msgid ":guilabel:`Name`, :guilabel:`Description`, :guilabel:`Project`, :guilabel:`Assignees`, :guilabel:`Customer`, :guilabel:`Tags`: copied from the original task;" msgstr "" -#: ../../content/applications/services/project/tasks/recurring_tasks.rst:38 +#: ../../content/applications/services/project/tasks/recurring_tasks.rst:33 msgid ":guilabel:`Milestones`, :guilabel:`Deadline`, :guilabel:`Timesheets`, :guilabel:`Chatter`, :guilabel:`Activities`, :guilabel:`Subtasks`: those fields are not copied;" msgstr "" -#: ../../content/applications/services/project/tasks/recurring_tasks.rst:41 +#: ../../content/applications/services/project/tasks/recurring_tasks.rst:36 msgid "A **smart button** on the task displays the total number of existing recurrences." msgstr "" -#: ../../content/applications/services/project/tasks/recurring_tasks.rst:44 +#: ../../content/applications/services/project/tasks/recurring_tasks.rst:39 msgid "Edit or stop task recurrence" msgstr "" -#: ../../content/applications/services/project/tasks/recurring_tasks.rst:46 +#: ../../content/applications/services/project/tasks/recurring_tasks.rst:41 msgid "**To edit** the recurrence, open the last task in recurrence. Any changes made on the task will be applied to the tasks that will be created in the future." msgstr "" -#: ../../content/applications/services/project/tasks/recurring_tasks.rst:49 +#: ../../content/applications/services/project/tasks/recurring_tasks.rst:44 msgid "**To stop** the recurrence, open the last task in recurrence and press the :guilabel:`Recurrent` button next to the :guilabel:`Planned date`." msgstr "" diff --git a/locale/sources/websites.pot b/locale/sources/websites.pot index c251d1577..d77a64328 100644 --- a/locale/sources/websites.pot +++ b/locale/sources/websites.pot @@ -8,7 +8,7 @@ msgid "" msgstr "" "Project-Id-Version: Odoo 17.0\n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2024-03-25 16:01+0000\n" +"POT-Creation-Date: 2024-04-30 09:16+0000\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME \n" "Language-Team: LANGUAGE \n" @@ -1048,6 +1048,7 @@ msgid "It is possible to link your Odoo website with :ref:`analytics/plausible` msgstr "" #: ../../content/applications/websites/ecommerce/managing_products.rst:5 +#: ../../content/applications/websites/website/web_design/building_blocks/dynamic_content.rst:76 msgid "Products" msgstr "" @@ -1824,7 +1825,7 @@ msgid "If you are selling non-prepackaged kits (i.e., the kits are made of indiv msgstr "" #: ../../content/applications/websites/ecommerce/managing_products/products.rst:247 -msgid ":doc:`../../../inventory_and_mrp/manufacturing/management/kit_shipping`" +msgid ":doc:`../../../inventory_and_mrp/manufacturing/advanced_configuration/kit_shipping`" msgstr "" #: ../../content/applications/websites/ecommerce/managing_products/products.rst:250 @@ -2001,6 +2002,7 @@ msgid "Add a description to your course." msgstr "" #: ../../content/applications/websites/elearning.rst:67 +#: ../../content/applications/websites/livechat.rst:94 msgid "Options tab" msgstr "" @@ -2994,99 +2996,107 @@ msgstr "" msgid "Manage all posts by going to :menuselection:`Website --> Configuration --> Forum: Forums`, selecting the forum, and clicking the :guilabel:`Posts` smart button. By clicking the :guilabel:`Actions` button, it is possible to :guilabel:`Export`, :guilabel:`Archive`, :guilabel:`Unarchive`, or :guilabel:`Delete` one or multiple posts." msgstr "" -#: ../../content/applications/websites/livechat.rst:6 +#: ../../content/applications/websites/livechat.rst:5 msgid "Live Chat" msgstr "" -#: ../../content/applications/websites/livechat.rst:8 -msgid "Odoo *Live Chat* allows users to communicate with website visitors in real time. With *Live Chat*, leads can be qualified for their sales potential, support questions can be answered quickly, and issues can be directed to the appropriate team for further investigation (or follow up). *Live Chat* also provides the opportunity for instant feedback from customers." +#: ../../content/applications/websites/livechat.rst:7 +msgid "Odoo *Live Chat* allows users to communicate with website visitors in real-time. With *Live Chat*, leads can be qualified for their sales potential, support questions can be answered quickly, and issues can be directed to the appropriate team for further investigation or follow up. *Live Chat* also provides the opportunity for instant feedback from customers." msgstr "" -#: ../../content/applications/websites/livechat.rst:14 +#: ../../content/applications/websites/livechat.rst:13 msgid "Enable Live Chat" msgstr "" -#: ../../content/applications/websites/livechat.rst:16 -msgid "In order to enable *Live Chat*, the *Live Chat* application needs to be installed. This can be done in one of two ways." +#: ../../content/applications/websites/livechat.rst:15 +msgid "The *Live Chat* application can be installed multiple ways:" msgstr "" -#: ../../content/applications/websites/livechat.rst:19 -msgid "Go to :menuselection:`Apps --> Live Chat` and click :guilabel:`Install`." +#: ../../content/applications/websites/livechat.rst:17 +msgid "Go to :menuselection:`Apps application --> Live Chat` and click :guilabel:`Install`." msgstr "" -#: ../../content/applications/websites/livechat.rst:20 -msgid "In the :menuselection:`Website` application, go to :menuselection:`Configuration --> Settings`, scroll to the :guilabel:`Email & Marketing` section, check the box next to :guilabel:`Livechat`, and click :guilabel:`Save`." +#: ../../content/applications/websites/livechat.rst:18 +msgid "Go to the :menuselection:`Helpdesk app --> Configuration --> Helpdesk Teams` list view, select a team, and on the team's settings page, click the checkbox next to :guilabel:`Live Chat`, under the :guilabel:`Channels` section." msgstr "" -#: ../../content/applications/websites/livechat.rst:-1 +#: ../../content/applications/websites/livechat.rst:21 +msgid "In the :menuselection:`Website` app, go to :menuselection:`Configuration --> Settings`, scroll to the :guilabel:`Email & Marketing` section, check the box next to :guilabel:`Livechat`, and click :guilabel:`Save`." +msgstr "" + +#: ../../content/applications/websites/livechat.rst:0 msgid "View of the settings page and the live chat feature for Odoo Live Chat." msgstr "" -#: ../../content/applications/websites/livechat.rst:28 -msgid "After the :guilabel:`Live Chat` application is installed, a live chat :guilabel:`Channel` will be created by default and automatically selected in the drop-down." +#: ../../content/applications/websites/livechat.rst:30 +msgid "After the *Live Chat* application is installed, a live chat *Channel* is created by default." msgstr "" -#: ../../content/applications/websites/livechat.rst:32 -msgid "Create a new live chat channel" +#: ../../content/applications/websites/livechat.rst:33 +msgid "Create live chat channels" msgstr "" -#: ../../content/applications/websites/livechat.rst:34 -msgid "To create a new live chat *Channel*, go to :menuselection:`Main Odoo Dashboard --> Live Chat app --> New`. This will open a blank channel detail form. Enter the name of the new channel in the :guilabel:`Channel Name` field." +#: ../../content/applications/websites/livechat.rst:35 +msgid "To create a new live chat *Channel*, go to :menuselection:`Main Odoo Dashboard --> Live Chat app --> New`. This opens a blank channel detail form. Enter the name of the new channel in the :guilabel:`Channel Name` field." msgstr "" #: ../../content/applications/websites/livechat.rst:-1 msgid "View of a live chat channel form for Odoo Live Chat." msgstr "" -#: ../../content/applications/websites/livechat.rst:42 -msgid "To configure the remaining tabs on the channel detail form (:guilabel:`Operators`, :guilabel:`Options`, :guilabel:`Channel Rules`, and :guilabel:`Widgets`), follow the steps below." -msgstr "" - -#: ../../content/applications/websites/livechat.rst:46 -msgid "Operators" +#: ../../content/applications/websites/livechat.rst:43 +msgid "To configure the remaining tabs on the channel detail form (:ref:`Operators `, :ref:`Options `, :ref:`Channel Rules `, and :ref:`Widget `), follow the steps below." msgstr "" #: ../../content/applications/websites/livechat.rst:48 -msgid "*Operators* are the users who will respond to live chat requests from customers. When a user is added as an operator in a live chat channel, they will be able to receive chats from website visitors wherever they are in the database. Chat windows will open in the bottom right corner of the screen." +msgid "The channel detail form for any channel can be accessed by navigating back to the :guilabel:`Website Live Chat Channels` dashboard, via the breadcrumbs. Find the Kanban card for the appropriate live chat channel, hover over it, and then click on the :guilabel:`⋮ (three dots)` icon to open the drop-down menu. Click :guilabel:`Configure Channel` to open the channel detail form." +msgstr "" + +#: ../../content/applications/websites/livechat.rst:57 +msgid "Operators tab" +msgstr "" + +#: ../../content/applications/websites/livechat.rst:59 +msgid "*Operators* are the users who act as agents and respond to live chat requests from customers. When a user is added as an operator in a live chat channel, they can receive chats from website visitors wherever they are in the database. Chat windows open in the bottom-right corner of the screen." msgstr "" #: ../../content/applications/websites/livechat.rst:-1 msgid "View of a live chat pop up window in an Odoo database." msgstr "" -#: ../../content/applications/websites/livechat.rst:57 -msgid "The user who originally created the live chat channel will be added as an operator by default." -msgstr "" - -#: ../../content/applications/websites/livechat.rst:59 -msgid "To add additional users, navigate back to the :guilabel:`Website Live Chat Channels` dashboard via the breadcrumbs and click on the appropriate :guilabel:`Live Chat Channel`. Then, on the channel detail form, under the :guilabel:`Operators` tab, click :guilabel:`ADD` to reveal an :guilabel:`Add: Operators` pop-up window." -msgstr "" - -#: ../../content/applications/websites/livechat.rst:64 -msgid "In the pop-up window, search for the desired user(s). Then, click the checkbox next to the user(s) to be added, and click :guilabel:`SELECT`." -msgstr "" - #: ../../content/applications/websites/livechat.rst:67 -msgid "New operators can be created and added to the list directly from this pop-up, as well, by clicking :guilabel:`New`, and filling out the :guilabel:`Create Operators` pop-up form. When the form is complete, click :guilabel:`SAVE & CLOSE` (or :guilabel:`SAVE & NEW` for multiple record creations)." +msgid "On the channel detail form, click the :guilabel:`Operators` tab. The user who originally created the live chat channel has been added as an operator by default." msgstr "" -#: ../../content/applications/websites/livechat.rst:72 -msgid "Current operators can be edited (or removed) by clicking on their respective boxes in the :guilabel:`Operators` tab, which reveals a separate :guilabel:`Open: Operators` pop-up. In that pop-up, adjust any information as needed, and click :guilabel:`Save`, or click :guilabel:`Remove` to remove that operator from the channel." +#: ../../content/applications/websites/livechat.rst:71 +msgid "Current operators can be edited, or removed, by clicking on their respective boxes in the :guilabel:`Operators` tab, which reveals a separate :guilabel:`Open: Operators` modal. In that modal, adjust any information, as needed. Then, click :guilabel:`Save`, or click :guilabel:`Remove` to remove that operator from the channel." +msgstr "" + +#: ../../content/applications/websites/livechat.rst:76 +msgid "Click :guilabel:`Add` to reveal an :guilabel:`Add: Operators` modal." msgstr "" #: ../../content/applications/websites/livechat.rst:78 -msgid "Options" +msgid "In the modal, scroll to find the desired users, or enter their name in the :guilabel:`Search...` bar. Then, click the checkbox next to the users to be added, and click :guilabel:`Select`." msgstr "" -#: ../../content/applications/websites/livechat.rst:80 -msgid "The :guilabel:`Options` tab on the live chat channel details form contains the visual and text settings for the live chat window." -msgstr "" - -#: ../../content/applications/websites/livechat.rst:84 -msgid "Livechat button" +#: ../../content/applications/websites/livechat.rst:81 +msgid "New operators can be created and added to the list directly from this modal, as well, by clicking :guilabel:`New`, and filling out the :guilabel:`Create Operators` form. When the form is complete, click :guilabel:`Save & Close`, or :guilabel:`Save & New` for multiple record creations." msgstr "" #: ../../content/applications/websites/livechat.rst:86 +msgid "Creating a new user can impact the status of an Odoo subscription, as the total number of users in a database counts towards the billing rate. Proceed with caution before creating a new user. If a user already exists, adding them as an operator will **not** alter the subscription or billing rate for a database." +msgstr "" + +#: ../../content/applications/websites/livechat.rst:96 +msgid "The :guilabel:`Options` tab on the live chat channel detail form contains the visual and text settings for the live chat window." +msgstr "" + +#: ../../content/applications/websites/livechat.rst:102 +msgid "Livechat button" +msgstr "" + +#: ../../content/applications/websites/livechat.rst:104 msgid "The *Livechat Button* is the icon that appears in the bottom corner of the website." msgstr "" @@ -3094,179 +3104,179 @@ msgstr "" msgid "View of an Odoo website emphasizing the livechat button." msgstr "" -#: ../../content/applications/websites/livechat.rst:92 -msgid "Change the text in the :guilabel:`Text of the Button` field to update the greeting displayed in the text bubble when the live chat button appears on the website." +#: ../../content/applications/websites/livechat.rst:110 +msgid "Change the text in the :guilabel:`Notification text` field to update the greeting displayed in the text bubble when the live chat button appears on the website." msgstr "" -#: ../../content/applications/websites/livechat.rst:95 -msgid "Change the :guilabel:`Livechat Button Color` by clicking a color bubble to open the color selection window. Click the :guilabel:`🔄 (refresh)` icon to the right of the color bubbles to reset the colors to the default selection." +#: ../../content/applications/websites/livechat.rst:113 +msgid "The :guilabel:`Livechat Button Color` alters the color of the live chat button as it appears on the website. To change the color, click on a color bubble to open the color selection window, then click and drag the circle along the color gradient. Click out of the selection window once complete. Click the :guilabel:`🔁 (refresh)` icon to the right of the color bubbles to reset the colors to the default selection." msgstr "" -#: ../../content/applications/websites/livechat.rst:100 -msgid "Color selection, for the button or header, can be made manually using a slider or through RGB, HSL, or HEX color code entries from the pop-up color selection window that appears when either of the color bubbles are clicked. Different options will be available, depending on your operating system." +#: ../../content/applications/websites/livechat.rst:120 +msgid "Color selection, for the button or header, can be made manually using a slider or through RGB, HSL, or HEX color code entries from the pop-up color selection window that appears when either of the color bubbles are clicked. Different options are available, depending on the operating system." msgstr "" -#: ../../content/applications/websites/livechat.rst:106 +#: ../../content/applications/websites/livechat.rst:126 msgid "Livechat window" msgstr "" -#: ../../content/applications/websites/livechat.rst:108 +#: ../../content/applications/websites/livechat.rst:128 msgid "The *Livechat Window* is the space where the live chat conversation with website visitors takes place." msgstr "" -#: ../../content/applications/websites/livechat.rst:111 -msgid "Edit the :guilabel:`Welcome Message` to change the message a visitor sees when they open a new chat session. This message will appear as though it is sent by a live chat operator, and acts as both a greeting and an invitation to continue the conversation." +#: ../../content/applications/websites/livechat.rst:131 +msgid "Edit the :guilabel:`Welcome Message` to change the message a visitor sees when they open a new chat session. This message appears as though it is sent by a live chat operator, and acts as both a greeting and an invitation to continue the conversation." msgstr "" -#: ../../content/applications/websites/livechat.rst:115 -msgid "Edit the :guilabel:`Chat Input Placeholder` to alter the text that appears in the box where visitors will type their replies." +#: ../../content/applications/websites/livechat.rst:135 +msgid "Edit the :guilabel:`Chat Input Placeholder` to alter the text that appears in the box where visitors type their replies. This message prompts the visitor to initiate the chat." msgstr "" -#: ../../content/applications/websites/livechat.rst:118 -msgid "The *Channel Header* is the colored bar at the top of the chat window. The :guilabel:`Channel Header Color` can be changed following the same steps as the *Livechat Button Color* above." +#: ../../content/applications/websites/livechat.rst:138 +msgid "The *Channel Header* is the colored bar at the top of the chat window. The :guilabel:`Channel Header Color` can be changed following the same steps as the :ref:`Livechat button `." msgstr "" -#: ../../content/applications/websites/livechat.rst:124 -msgid "The Livechat Window with a purple header. The chat input placeholder reads \"Ask Something...\"" +#: ../../content/applications/websites/livechat.rst:145 +msgid "The live chat window with a purple channel header and placeholder text that reads, \"Say Something...\"" msgstr "" -#: ../../content/applications/websites/livechat.rst:127 -msgid "Channel rules" +#: ../../content/applications/websites/livechat.rst:151 +msgid "Channel Rules tab" msgstr "" -#: ../../content/applications/websites/livechat.rst:129 -msgid "The :guilabel:`Channel Rules` tab on the live chat channel details form determines when the *Live Chat Window* opens on the website, by configuring when a :guilabel:`URL Regex` action is triggered (e.g., a page visit)." +#: ../../content/applications/websites/livechat.rst:153 +msgid "The :guilabel:`Channel Rules` tab on the live chat channel detail form determines when the live chat window opens on the website, by configuring when a :guilabel:`URL Regex` action is triggered, such as a page visit." msgstr "" -#: ../../content/applications/websites/livechat.rst:133 -msgid "To create a new channel rule, click :guilabel:`Add a line`. This opens the :guilabel:`Open: Rules` pop-up." +#: ../../content/applications/websites/livechat.rst:157 +msgid "To create a new channel rule, click :guilabel:`Add a line`. This opens the :guilabel:`Create Rules` modal." msgstr "" #: ../../content/applications/websites/livechat.rst:-1 msgid "View of a channel's rules form for Odoo Live Chat." msgstr "" -#: ../../content/applications/websites/livechat.rst:141 +#: ../../content/applications/websites/livechat.rst:165 msgid "Create new rules" msgstr "" -#: ../../content/applications/websites/livechat.rst:143 -msgid "Fill out the fields on the :guilabel:`Open: Rules` pop-up as instructed below, then click :guilabel:`Save`." -msgstr "" - -#: ../../content/applications/websites/livechat.rst:148 -msgid "Live Chat Button" -msgstr "" - -#: ../../content/applications/websites/livechat.rst:150 -msgid "The *Livechat Button* is the icon that appears in the bottom corner of the website. Select from one of the following display options:" -msgstr "" - -#: ../../content/applications/websites/livechat.rst:153 -msgid ":guilabel:`Show` displays the chat button on the page(s)." -msgstr "" - -#: ../../content/applications/websites/livechat.rst:154 -msgid ":guilabel:`Show with notification` displays the chat button, as well as a floating text bubble next to the button." -msgstr "" - -#: ../../content/applications/websites/livechat.rst:156 -msgid ":guilabel:`Open automatically` displays the button and automatically opens the chat window after a specified amount of time (designated in the :guilabel:`Open automatically timer` field)." -msgstr "" - -#: ../../content/applications/websites/livechat.rst:159 -msgid ":guilabel:`Hide` hides the chat button on the page(s)." -msgstr "" - -#: ../../content/applications/websites/livechat.rst:161 -msgid "Chatbot" -msgstr "" - -#: ../../content/applications/websites/livechat.rst:163 -msgid "If a *Chatbot* will be included on this channel, select it from the dropdown. If the chatbot will only be active when no operators are active, check the box labeled :guilabel:`Enabled only if no operator`." -msgstr "" - #: ../../content/applications/websites/livechat.rst:167 -msgid "URL Regex" -msgstr "" - -#: ../../content/applications/websites/livechat.rst:169 -msgid "In the :guilabel:`URL Regex` field, input the relative URL of the page where the chat button should appear." +msgid "Fill out the fields on the :guilabel:`Create Rules` modal, as instructed below. Then, click :guilabel:`Save & Close`." msgstr "" #: ../../content/applications/websites/livechat.rst:172 -msgid "Open automatically timer" +msgid "Live Chat Button" msgstr "" #: ../../content/applications/websites/livechat.rst:174 -msgid "This field designates the amount of time (in seconds) a page will be open before the chat window will open. If the :guilabel:`Livechat Button` for this rule is not set to :guilabel:`Open automatically`, this field will be ignored." +msgid "The *Live Chat Button* is the icon that appears in the bottom corner of the website. Select from one of the following display options:" +msgstr "" + +#: ../../content/applications/websites/livechat.rst:177 +msgid ":guilabel:`Show`: displays the chat button on the page." msgstr "" #: ../../content/applications/websites/livechat.rst:178 -msgid "Country" +msgid ":guilabel:`Show with notification`: displays the chat button, as well as a floating text bubble next to the button." msgstr "" #: ../../content/applications/websites/livechat.rst:180 -msgid "If this channel should only be available to site visitors in specific countries, add them to the :guilabel:`Country` field. If this field is left blank, the channel will be available to all site visitors, regardless of location." +msgid ":guilabel:`Open automatically`: displays the button and automatically opens the chat window after a specified amount of time (designated in the :guilabel:`Open automatically timer` field, which is revealed when selecting this option)." +msgstr "" + +#: ../../content/applications/websites/livechat.rst:183 +msgid ":guilabel:`Hide`: hides the chat button on the page." msgstr "" #: ../../content/applications/websites/livechat.rst:185 -msgid "In order to track the geographical location of visitors, :guilabel:`GeoIP` must be installed on the database. While this feature is installed by default on *Odoo Online*, *On-Premise* databases will require additional :doc:`setup steps `." +msgid "Chatbot" msgstr "" -#: ../../content/applications/websites/livechat.rst:190 -msgid "Widget" +#: ../../content/applications/websites/livechat.rst:187 +msgid "To include a :doc:`Chatbot ` on this channel, select it from the drop-down menu. If the chatbot should only be active when no operators are active, check the box labeled :guilabel:`Enabled only if no operator`." msgstr "" -#: ../../content/applications/websites/livechat.rst:192 -msgid "The :guilabel:`Widget` tab on the live chat channel details form provides the shortcode for an embeddable website widget. This code can be added to a website to provide access to a live chat window." +#: ../../content/applications/websites/livechat.rst:191 +msgid "The :guilabel:`Enabled only if no operator` field is **only** visible if a chatbot is selected in the :guilabel:`Chatbot` field." +msgstr "" + +#: ../../content/applications/websites/livechat.rst:194 +msgid "URL Regex" msgstr "" #: ../../content/applications/websites/livechat.rst:196 -msgid "The live chat widget can be added to websites created through Odoo by navigating to the :menuselection:`Website --> Configuration --> Settings`. Then scroll to the :guilabel:`Livechat` section, and select the channel to add to the site. Click :guilabel:`Save` to apply." +msgid "The *URL Regex* specifies the web pages where this rule should be applied. In the :guilabel:`URL Regex` field, input the relative URL of the page where the chat button should appear." msgstr "" #: ../../content/applications/websites/livechat.rst:200 -msgid "To add the widget to a website created on a third-party platform, click the first :guilabel:`COPY` button on the :guilabel:`Widget` tab and paste the code into the `` tag on the site." +msgid "Open automatically timer" msgstr "" -#: ../../content/applications/websites/livechat.rst:203 -msgid "Likewise, to send a live chat session to a customer, click the second :guilabel:`COPY` button on the :guilabel:`Widget` tab. This link can be sent directly to a customer, and once they click the link, it will open a new chat." +#: ../../content/applications/websites/livechat.rst:202 +msgid "This field designates the amount of time (in seconds) a page should be open before the chat window opens. This field **only** appears if the :guilabel:`Live Chat Button` for this rule is set to :guilabel:`Open automatically`." +msgstr "" + +#: ../../content/applications/websites/livechat.rst:206 +msgid "Country" +msgstr "" + +#: ../../content/applications/websites/livechat.rst:208 +msgid "If this channel should only be available to site visitors in specific countries, add them to the :guilabel:`Country` field. If this field is left blank, the channel is available to all site visitors, regardless of location." +msgstr "" + +#: ../../content/applications/websites/livechat.rst:213 +msgid "In order to track the geographical location of visitors, *GeoIP* **must** be installed on the database. While this feature is installed by default on *Odoo Online* databases, *On-Premise* databases require additional :doc:`setup steps `." +msgstr "" + +#: ../../content/applications/websites/livechat.rst:220 +msgid "Widget tab" +msgstr "" + +#: ../../content/applications/websites/livechat.rst:222 +msgid "The :guilabel:`Widget` tab on the live chat channel detail form provides the code for a website widget. This code can be added to a website to provide access to a live chat window." +msgstr "" + +#: ../../content/applications/websites/livechat.rst:226 +msgid "The live chat widget can be added to websites created through Odoo by navigating to :menuselection:`Website app --> Configuration --> Settings`. Then, scroll to the :menuselection:`Email & Marketing` section. In the :guilabel:`Channel` field, select the channel to add to the site. Click :guilabel:`Save` to apply." +msgstr "" + +#: ../../content/applications/websites/livechat.rst:231 +msgid "To add the widget to a website created on a third-party platform, click the first :guilabel:`COPY` button on the :guilabel:`Widget` tab, and paste the code into the `` tag on the site." +msgstr "" + +#: ../../content/applications/websites/livechat.rst:234 +msgid "Likewise, to send a live chat session to a customer, click the second :guilabel:`COPY` button on the :guilabel:`Widget` tab. This link can be sent directly to a customer. When they click the link, they are redirected to a new chat window." msgstr "" #: ../../content/applications/websites/livechat.rst:-1 msgid "View of the widget tab for Odoo Live Chat." msgstr "" -#: ../../content/applications/websites/livechat.rst:212 +#: ../../content/applications/websites/livechat.rst:243 msgid "Participate in a conversation" msgstr "" -#: ../../content/applications/websites/livechat.rst:214 -msgid "As explained above, *operators* are the users who will respond to live chat requests from customers. The information below outlines the necessary steps for operators participating in live chat conversations on an Odoo database." +#: ../../content/applications/websites/livechat.rst:245 +msgid "As explained above, *operators* are the users who respond to live chat requests from customers. The information below outlines the necessary steps for operators participating in live chat conversations on an Odoo database." msgstr "" -#: ../../content/applications/websites/livechat.rst:219 +#: ../../content/applications/websites/livechat.rst:250 msgid "Set an online chat name" msgstr "" -#: ../../content/applications/websites/livechat.rst:221 -msgid "Before participating in a live chat, operators should update their *Online Chat Name*. This is the name that will be displayed to site visitors in the live chat conversation." +#: ../../content/applications/websites/livechat.rst:252 +msgid "Before participating in a live chat, operators may choose to update their *Online Chat Name*. This is the name that is displayed to site visitors in the live chat conversation." msgstr "" -#: ../../content/applications/websites/livechat.rst:224 -msgid "To update the :guilabel:`Online Chat Name`, click on the user name in the upper-right corner of any page in the database. Select :guilabel:`My Profile` to open the Profile page. On the right side of the :guilabel:`Preferences` tab, locate the :guilabel:`Online Chat Name` field and enter the preferred name." +#: ../../content/applications/websites/livechat.rst:255 +msgid "To update the :guilabel:`Online Chat Name`, click on the user avatar in the top-right corner of any page in the database. Select :guilabel:`My Profile` from the drop-down menu to open the profile page. On the right side of the :guilabel:`Preferences` tab, locate the :guilabel:`Online Chat Name` field, and enter a preferred name." msgstr "" -#: ../../content/applications/websites/livechat.rst:-1 -msgid "View of the My Profile option in Odoo." +#: ../../content/applications/websites/livechat.rst:260 +msgid "If a user's :guilabel:`Online Chat Name` is not set, the name displayed defaults to the user's name that is designated on their profile page." msgstr "" -#: ../../content/applications/websites/livechat.rst:233 -msgid "If a users :guilabel:`Online Chat Name` is not set, the name displayed will default to the :guilabel:`User Name`." -msgstr "" - -#: ../../content/applications/websites/livechat.rst:237 +#: ../../content/applications/websites/livechat.rst:264 msgid "A user has their full name as their :guilabel:`User Name`, but they do not want to include their last name in a live chat conversation. They would then set their :guilabel:`Online Chat Name` to include only their first name." msgstr "" @@ -3274,60 +3284,84 @@ msgstr "" msgid "View of user profile in Odoo, emphasizing the Online Chat name field." msgstr "" -#: ../../content/applications/websites/livechat.rst:246 +#: ../../content/applications/websites/livechat.rst:273 +msgid "Set online chat languages" +msgstr "" + +#: ../../content/applications/websites/livechat.rst:275 +msgid "If an operator speaks multiple languages, they can add this information to their user profile. This information can then be used to determine what conversations the operator is assigned. A visitor's language is determined, via their browser's language settings." +msgstr "" + +#: ../../content/applications/websites/livechat.rst:279 +msgid "To add *Online Chat Languages*, click on the user avatar in the top-right corner of any page in the database. Select :guilabel:`My Profile` from the drop-down menu to open the profile page. On the right side of the :guilabel:`Preferences` tab, click into the :guilabel:`Online Chat Language` field, and select one or more languages from the drop-down menu." +msgstr "" + +#: ../../content/applications/websites/livechat.rst:285 +msgid "Conversations are assigned to operators based on a number of criteria, including availability and the number of ongoing conversations. While the operator's main language and additional languages are taken into consideration, they do **not** supersede all other criteria." +msgstr "" + +#: ../../content/applications/websites/livechat.rst:290 msgid "Join or leave a channel" msgstr "" -#: ../../content/applications/websites/livechat.rst:248 -msgid "To join a live chat channel, go to the :menuselection:`Live Chat` app and click the :guilabel:`JOIN` button on the kanban card for the appropriate channel." +#: ../../content/applications/websites/livechat.rst:292 +msgid "To join a live chat channel, go to the :menuselection:`Live Chat app --> Channels`, and click the :guilabel:`Join` button on the Kanban card for the appropriate channel." msgstr "" -#: ../../content/applications/websites/livechat.rst:251 -msgid "Any channel where the user is currently active will show a :guilabel:`LEAVE` button. Click this button to disconnect from the channel." +#: ../../content/applications/websites/livechat.rst:295 +msgid "Any channel where the user is currently active shows a :guilabel:`Leave` button. Click this button to disconnect from the channel." msgstr "" #: ../../content/applications/websites/livechat.rst:-1 msgid "View of a channel form and the option to join a channel for Odoo Live Chat." msgstr "" -#: ../../content/applications/websites/livechat.rst:259 -msgid "*Operators* that do not show any activity in Odoo for more than thirty minutes will be considered disconnected, and subsequently removed from the channel." +#: ../../content/applications/websites/livechat.rst:303 +msgid "Operators that do not show any activity in Odoo for more than thirty minutes are considered disconnected, and subsequently removed from the channel." msgstr "" -#: ../../content/applications/websites/livechat.rst:263 +#: ../../content/applications/websites/livechat.rst:307 msgid "Manage live chat requests" msgstr "" -#: ../../content/applications/websites/livechat.rst:265 -msgid "When an operator is active in a channel, chat windows will open in the bottom right corner of the screen, no matter where they are in the database. They can participate in conversations without leaving their current location." +#: ../../content/applications/websites/livechat.rst:309 +msgid "When an operator is active in a channel, chat windows open in the bottom-right corner of the screen, no matter where they are in the database. They can participate in conversations without leaving their current location." msgstr "" -#: ../../content/applications/websites/livechat.rst:270 -msgid "Conversations can also be accessed by clicking the :guilabel:`Conversations` icon in the menu bar." +#: ../../content/applications/websites/livechat.rst:314 +msgid "Conversations can also be accessed by clicking the :guilabel:`(comments)` icon in the menu bar. bar." msgstr "" #: ../../content/applications/websites/livechat.rst:0 -msgid "View of the menu bar in Odoo emphasizing the conversations icon." +msgid "View of the menu bar in Odoo emphasizing the comments icon." msgstr "" -#: ../../content/applications/websites/livechat.rst:277 -msgid "Live chat conversations can also be viewed by navigating to :menuselection:`Dashboard --> Discuss`. New conversations will appear in bold under the :guilabel:`LIVECHAT` heading along the left panel." +#: ../../content/applications/websites/livechat.rst:321 +msgid "Live chat conversations can also be viewed by navigating to :menuselection:`Discuss app`. New conversations appear in bold under the :guilabel:`LIVECHAT` heading, located along the left panel." msgstr "" #: ../../content/applications/websites/livechat.rst:-1 msgid "View of the discuss application with a message sent through live chat in Odoo." msgstr "" -#: ../../content/applications/websites/livechat.rst:284 -msgid "Click on a conversation in the left panel to select it. This will open the conversation. From this view, an operator can participate in the chat the same as they would in the normal chat window." +#: ../../content/applications/websites/livechat.rst:328 +msgid "Click on a conversation in the left panel to select it. This opens the conversation. From this view, an operator can participate in the chat the same as they would in the normal chat window." msgstr "" -#: ../../content/applications/websites/livechat.rst:288 -msgid ":doc:`Get Started with Discuss `" +#: ../../content/applications/websites/livechat.rst:332 +msgid ":doc:`../productivity/discuss`" msgstr "" -#: ../../content/applications/websites/livechat.rst:289 -msgid ":doc:`/applications/websites/livechat/responses`" +#: ../../content/applications/websites/livechat.rst:333 +msgid ":doc:`livechat/responses`" +msgstr "" + +#: ../../content/applications/websites/livechat.rst:334 +msgid ":doc:`livechat/ratings`" +msgstr "" + +#: ../../content/applications/websites/livechat.rst:335 +msgid ":doc:`livechat/chatbots`" msgstr "" #: ../../content/applications/websites/livechat/chatbots.rst:3 @@ -3339,7 +3373,7 @@ msgid "A *Chatbot* is a program designed to mimic a conversation with a live hum msgstr "" #: ../../content/applications/websites/livechat/chatbots.rst:10 -msgid "Chatbots can be customized to fill various roles, from customer support, to creating leads, to collecting contact information. The goal of the chatbot depends on the page of the website they are assigned, and the messages included in the script, among other criteria." +msgid "Chatbots can be customized to fill various roles, from customer support, to creating leads, to collecting contact information. The goal of each chatbot can vary based on several criteria, including the webpage where it is located, and the information it captures." msgstr "" #: ../../content/applications/websites/livechat/chatbots.rst:-1 @@ -3352,206 +3386,226 @@ msgid "Build a chatbot" msgstr "" #: ../../content/applications/websites/livechat/chatbots.rst:21 -msgid "Before creating a new chatbot, the *Live Chat* application must first be installed on the database. This can be done directly from the :menuselection:`Apps` menu by searching for `Live Chat` in the :guilabel:`search bar` and clicking :guilabel:`Install`." +msgid "Before creating a new chatbot, the *Live Chat* application must first be installed on the database. This can be done directly from the :menuselection:`Apps` application, by searching for `Live Chat` in the :guilabel:`Search...` bar, and clicking :guilabel:`Install`." msgstr "" #: ../../content/applications/websites/livechat/chatbots.rst:25 -msgid "Alternatively, *Live Chat* can be installed and enabled by navigating to the :menuselection:`Website application --> Configuration --> Settings`, and checking the box labeled :guilabel:`Livechat`. Once enabled, the database will refresh, and the *Live Chat* application is accessible." +msgid "Once the *Live Chat* application has been installed on the database, go to :menuselection:`Live Chat app --> Configuration --> Chatbots`." msgstr "" #: ../../content/applications/websites/livechat/chatbots.rst:29 -msgid "Once the *Live Chat* application has been installed on the database, open it, and go to :menuselection:`Configuration --> Chatbots`." +msgid "When the *Live Chat* app is installed, a sample chatbot is created, named *Welcome Bot*. This chatbot has a preconfigured script that walks through a few basic steps, including asking for a visitor's email address, and forwarding the conversation to an operator." msgstr "" #: ../../content/applications/websites/livechat/chatbots.rst:33 -msgid "When the *Live Chat* app is installed, a sample chatbot is created, named *Welcome Bot*. This chatbot has a pre-configured script that walks through a few basic steps, including asking for a visitor's email address, and forwarding the conversation to an operator." -msgstr "" - -#: ../../content/applications/websites/livechat/chatbots.rst:37 msgid "*Welcome Bot* can be used as a starting point. The existing steps can be edited or removed, and new steps can be added to customize the script, as needed." msgstr "" -#: ../../content/applications/websites/livechat/chatbots.rst:40 -msgid "*Welcome Bot* can be deleted (or archived)." +#: ../../content/applications/websites/livechat/chatbots.rst:36 +msgid "*Welcome Bot* can be deleted or archived, if necessary." msgstr "" #: ../../content/applications/websites/livechat/chatbots.rst:0 msgid "View of the Welcome Bot script in Odoo Live Chat." msgstr "" -#: ../../content/applications/websites/livechat/chatbots.rst:46 +#: ../../content/applications/websites/livechat/chatbots.rst:42 msgid "To create a new chatbot, navigate to the :guilabel:`Chatbot` page (:menuselection:`Live Chat app --> Configuration --> Chatbots`) and click :guilabel:`New`. This opens a blank chatbot details page." msgstr "" -#: ../../content/applications/websites/livechat/chatbots.rst:49 +#: ../../content/applications/websites/livechat/chatbots.rst:45 msgid "On the blank chatbot details page, enter a name in the :guilabel:`Chatbot Name` field and click on the :guilabel:`Edit Image` icon in the upper right corner of the form to add a photo." msgstr "" -#: ../../content/applications/websites/livechat/chatbots.rst:53 +#: ../../content/applications/websites/livechat/chatbots.rst:49 msgid "Chatbot scripts" msgstr "" +#: ../../content/applications/websites/livechat/chatbots.rst:51 +msgid "After the new chatbot has been created and named, the next step is to create a script. Chatbot conversations follow an accompanying script. These scripts are comprised of lines of dialog, each designed to deliver or capture information." +msgstr "" + #: ../../content/applications/websites/livechat/chatbots.rst:55 -msgid "Once the new chatbot has been created and named, the next step is to create a script. Chatbot conversations follow an accompanying script. These scripts are comprised of lines of dialogue, each designed to either deliver or capture information." +msgid "To create a chatbot script, click :guilabel:`Add a Line` in the :guilabel:`Script` tab of the chatbot detail page, and a :guilabel:`Create Script Steps` modal appears." msgstr "" #: ../../content/applications/websites/livechat/chatbots.rst:59 -msgid "To create a chatbot script, navigate to the :guilabel:`Script` tab of the chatbot details page, and click :guilabel:`Add a Line` to open the :guilabel:`Create Script Steps` pop-up form." +msgid "This form must be filled out for **each** line of text (dialog) that the chatbot could deliver during the conversation." msgstr "" #: ../../content/applications/websites/livechat/chatbots.rst:62 -msgid "This form must be filled out for each line of text (dialogue) that the chatbot could potentially deliver during the conversation." +msgid "First, enter the content of the message in the :guilabel:`Message` field. Then, select an option from the :guilabel:`Step Type` and :guilabel:`Only If` drop-down menus." msgstr "" -#: ../../content/applications/websites/livechat/chatbots.rst:65 -msgid "First, enter the content of the message in the :guilabel:`Message` field. Then, select an option from the :guilabel:`Step Types` drop-down menu." -msgstr "" - -#: ../../content/applications/websites/livechat/chatbots.rst:69 +#: ../../content/applications/websites/livechat/chatbots.rst:66 msgid "Step types" msgstr "" -#: ../../content/applications/websites/livechat/chatbots.rst:71 -msgid "The :guilabel:`Step Type` selected depends on the intended purpose of the message. The available options in the :guilabel:`Step Type` drop-down are listed below, as well as their use, and any additional information:" +#: ../../content/applications/websites/livechat/chatbots.rst:68 +msgid "The :guilabel:`Step Type` selected depends on the intended purpose of the message. The available options in the :guilabel:`Step Type` drop-down menu are detailed below:" msgstr "" -#: ../../content/applications/websites/livechat/chatbots.rst:76 +#: ../../content/applications/websites/livechat/chatbots.rst:72 msgid "Text" msgstr "" +#: ../../content/applications/websites/livechat/chatbots.rst:74 +msgid "This step is used for messages where no answer is expected or necessary. Text steps can be used for greetings, to offer resources, such as documentation, or provide links to specific web pages." +msgstr "" + #: ../../content/applications/websites/livechat/chatbots.rst:78 -msgid "This step is used for messages where no answer is expected (or necessary). Text steps can be used for greetings and/or to deliver information." +msgid "*Text* step types are only intended to deliver information, and do **not** allow for any visitor input. As such, they **must** be followed by additional steps to continue the conversation." msgstr "" #: ../../content/applications/websites/livechat/chatbots.rst:82 -msgid "Text step types are only intended to deliver information, and do not allow for any visitor input. As such, they need to be followed by additional steps to continue the conversation." -msgstr "" - -#: ../../content/applications/websites/livechat/chatbots.rst:86 msgid "Question" msgstr "" -#: ../../content/applications/websites/livechat/chatbots.rst:88 +#: ../../content/applications/websites/livechat/chatbots.rst:84 msgid "This step asks a question and provides a set of answers. The visitor clicks on one answer, which either leads to a new step in the conversation, or can lead to an optional link to a new webpage." msgstr "" -#: ../../content/applications/websites/livechat/chatbots.rst:92 -msgid "It is helpful to add a catchall answer to question steps (ex: \"Something else\"). This helps visitors continue the conversation, even if their needs don't exactly fit with any of the other answers." +#: ../../content/applications/websites/livechat/chatbots.rst:87 +msgid "Enter the question in the :guilabel:`Message` field. Then, under the :guilabel:`Answer` heading, click :guilabel:`Add a Line` to create a blank answer line." msgstr "" -#: ../../content/applications/websites/livechat/chatbots.rst:97 -msgid "Email" +#: ../../content/applications/websites/livechat/chatbots.rst:90 +msgid "Proceed to enter the answer as it should appear to the visitor. To turn the answer into a link that redirects the visitor when selected, add the URL to the answer line under the :guilabel:`Optional Link` heading." +msgstr "" + +#: ../../content/applications/websites/livechat/chatbots.rst:94 +msgid "Repeat these steps for every answer to be included for the question." +msgstr "" + +#: ../../content/applications/websites/livechat/chatbots.rst:96 +msgid "Click :guilabel:`Save & Close` or :guilabel:`Save & New`." msgstr "" #: ../../content/applications/websites/livechat/chatbots.rst:99 +msgid "It is helpful to add a catchall answer to question steps (e.g: `Something else`). This helps visitors continue the conversation, even if their needs do not exactly fit with any of the other answers." +msgstr "" + +#: ../../content/applications/websites/livechat/chatbots.rst:104 +msgid "Email" +msgstr "" + +#: ../../content/applications/websites/livechat/chatbots.rst:106 msgid "This step prompts visitors to provide their email address, which is stored and can be used by team members later to follow up with additional information." msgstr "" -#: ../../content/applications/websites/livechat/chatbots.rst:102 -msgid "The only accepted inputs for this step type are email addresses that are in a valid format. If a visitor attempts to enter anything other than a valid email address, the chatbot responds with a message stating it does not recognize the information submitted." +#: ../../content/applications/websites/livechat/chatbots.rst:109 +msgid "The **only** accepted inputs for this step type are email addresses that are in a valid format. If a visitor attempts to enter anything other than a valid email address, the chatbot responds with a message stating it does not recognize the information submitted." msgstr "" #: ../../content/applications/websites/livechat/chatbots.rst:-1 msgid "View of a chatbot responding to an invalid email." msgstr "" -#: ../../content/applications/websites/livechat/chatbots.rst:111 +#: ../../content/applications/websites/livechat/chatbots.rst:118 msgid "Phone" msgstr "" -#: ../../content/applications/websites/livechat/chatbots.rst:113 -msgid "Similar to email, this step type prompts the visitor to enter their phone number, which can be used at a later time to follow up with additional information, or to schedule demos, and more." +#: ../../content/applications/websites/livechat/chatbots.rst:120 +msgid "Similar to email, this step type prompts the visitor to enter their phone number, which can be used to follow up with additional information, schedule demos, and more." msgstr "" -#: ../../content/applications/websites/livechat/chatbots.rst:117 -msgid "Due to the vast number of formats used for phone numbers worldwide, responses to this step type are **not** validated for formatting." +#: ../../content/applications/websites/livechat/chatbots.rst:124 +msgid "Due to the vast number of formats used for phone numbers worldwide, responses to this step type are **not** validated for formatting, and can include both numbers and special characters." msgstr "" -#: ../../content/applications/websites/livechat/chatbots.rst:121 +#: ../../content/applications/websites/livechat/chatbots.rst:128 msgid "Forward to Operator" msgstr "" -#: ../../content/applications/websites/livechat/chatbots.rst:123 -msgid "This step forwards the conversation to an active live chat operator, so that they can continue assisting the visitor. As the conversation transcript is passed on to the operator they are able to pick up where the chatbot left off. This not only saves time for all parties involved, it can also help qualify conversations before they reach live human operators." +#: ../../content/applications/websites/livechat/chatbots.rst:130 +msgid "This step forwards the conversation to an active live chat operator, so they can continue assisting the visitor. As the conversation transcript is passed on to the operator, they can pick up where the chatbot left off. This not only saves time for all parties involved, it can also help qualify conversations before they reach live operators." msgstr "" -#: ../../content/applications/websites/livechat/chatbots.rst:129 -msgid "If no active operator is available on the channel, the chatbot continues the conversation with the visitor. Therefore, additional steps should be added after this one to ensure that there is no abrupt end to the conversation." +#: ../../content/applications/websites/livechat/chatbots.rst:136 +msgid "If no active operator is available on the channel, the chatbot continues the conversation with the visitor. Therefore, additional steps should be added after this one to ensure there is no abrupt end to the conversation. The additional steps can both inform visitors about the lack of available operators (e.g. `Uh-oh, it looks like none of our operators are available`) and continue the conversation (e.g. `Would you like to leave your email address?`)." msgstr "" #: ../../content/applications/websites/livechat/chatbots.rst:0 msgid "View of a chatbot follow up messages when no live chat operator is available." msgstr "" -#: ../../content/applications/websites/livechat/chatbots.rst:138 +#: ../../content/applications/websites/livechat/chatbots.rst:147 msgid "Free Input/Multi-Line" msgstr "" -#: ../../content/applications/websites/livechat/chatbots.rst:140 -msgid "The free input step allows visitors to respond to questions without providing pre-written responses. Information provided in these responses is stored in the chat transcripts." +#: ../../content/applications/websites/livechat/chatbots.rst:149 +msgid "The *free input* step allows visitors to respond to questions without providing pre-written responses. Information provided in these responses is stored in the chat transcripts." msgstr "" -#: ../../content/applications/websites/livechat/chatbots.rst:143 -msgid "Choose between :guilabel:`Free Input` and :guilabel:`Free Input (Multi-Line)` depending on the type and amount of information being requested from the visitor." +#: ../../content/applications/websites/livechat/chatbots.rst:152 +msgid "Choose between :guilabel:`Free Input` and :guilabel:`Free Input (Multi-Line)` depending on the type and amount of information the visitor is asked to provide." msgstr "" -#: ../../content/applications/websites/livechat/chatbots.rst:147 +#: ../../content/applications/websites/livechat/chatbots.rst:156 msgid "Create Lead" msgstr "" -#: ../../content/applications/websites/livechat/chatbots.rst:149 -msgid "This step creates a lead in the *CRM* application. Select an option from the :guilabel:`Sales Team` drop-down to assign the created lead to a specific team." -msgstr "" - -#: ../../content/applications/websites/livechat/chatbots.rst:153 -msgid "Create Ticket" -msgstr "" - -#: ../../content/applications/websites/livechat/chatbots.rst:155 -msgid "This step creates a :doc:`ticket ` in the *Helpdesk* application. Select an option from the :guilabel:`Helpdesk Team` drop-down to assign the created ticket to a specific team." -msgstr "" - -#: ../../content/applications/websites/livechat/chatbots.rst:160 -msgid "Only if" +#: ../../content/applications/websites/livechat/chatbots.rst:158 +msgid "This step creates a lead in the *CRM* application. Select an option from the :guilabel:`Sales Team` drop-down field that appears to assign the created lead to a specific team." msgstr "" #: ../../content/applications/websites/livechat/chatbots.rst:162 -msgid "Chatbot scripts operate on an if/then basis, which means the next question presented to the visitor is determined by the answer they provide to the previous question." +msgid "This step is **only** available if the *CRM* application is installed on the database." msgstr "" #: ../../content/applications/websites/livechat/chatbots.rst:165 -msgid "To continue the progression of the conversation, the form for a new step contains a field labeled :guilabel:`Only If`. This field is where the progression of questions is defined." +msgid "Create Ticket" msgstr "" -#: ../../content/applications/websites/livechat/chatbots.rst:168 -msgid "If a step is intended to follow all of the previous messages, this field can be left empty. However, if a message should **only** be sent conditionally, based on a previous response (or several previous responses), those responses need to be added to this field." +#: ../../content/applications/websites/livechat/chatbots.rst:167 +msgid "This step creates a :doc:`ticket <../../services/helpdesk/overview/receiving_tickets>` in the *Helpdesk* application. Select an option from the :guilabel:`Helpdesk Team` drop-down field that appears to assign the created ticket to a specific team." msgstr "" -#: ../../content/applications/websites/livechat/chatbots.rst:173 -msgid "If there are any selections made in the :guilabel:`Only If` field, the step will **not** be shown in a conversation unless **all** of the answers have been selected. Only include selections in this field if they are necessary for this step to be displayed." +#: ../../content/applications/websites/livechat/chatbots.rst:172 +msgid "This step is **only** available if the *Helpdesk* application is installed on the database." msgstr "" -#: ../../content/applications/websites/livechat/chatbots.rst:178 +#: ../../content/applications/websites/livechat/chatbots.rst:175 +msgid "Only if" +msgstr "" + +#: ../../content/applications/websites/livechat/chatbots.rst:177 +msgid "Chatbot scripts operate on an if/then basis, which means the next question presented to the visitor is determined by the answer provided to the previous question." +msgstr "" + +#: ../../content/applications/websites/livechat/chatbots.rst:180 +msgid "To continue the progression of the conversation, the :guilabel:`Create Script Steps` form for a new step contains a field labeled :guilabel:`Only If`. This field is where the progression of questions is defined." +msgstr "" + +#: ../../content/applications/websites/livechat/chatbots.rst:184 +msgid "If a step is intended to follow all of the previous messages, this field can be left empty. However, if a message should **only** be sent conditionally, based on a previous response, or several previous responses, those responses **must** be added to this field." +msgstr "" + +#: ../../content/applications/websites/livechat/chatbots.rst:189 +msgid "If any selections are made in the :guilabel:`Only If` field, they must **all** be selected during the conversation *before* this step will be included. Only include selections in this field if they are necessary for this step to be displayed." +msgstr "" + +#: ../../content/applications/websites/livechat/chatbots.rst:194 msgid "In the *Welcome Bot* script, a visitor can ask about pricing information. If the visitor selects this response, a step is included to forward the conversation to an operator. The chatbot first sends a message informing the visitor that it is checking to see if an operator is available to chat." msgstr "" -#: ../../content/applications/websites/livechat/chatbots.rst:183 +#: ../../content/applications/websites/livechat/chatbots.rst:199 msgid "However, this message should **only** be delivered if the visitor requests pricing information. In that situation, the conversation would proceed as below:" msgstr "" -#: ../../content/applications/websites/livechat/chatbots.rst:186 +#: ../../content/applications/websites/livechat/chatbots.rst:202 msgid "Welcome Bot: \"*What are you looking for?*\"" msgstr "" -#: ../../content/applications/websites/livechat/chatbots.rst:187 +#: ../../content/applications/websites/livechat/chatbots.rst:203 msgid "Visitor: \"**I have a pricing question.**\"" msgstr "" -#: ../../content/applications/websites/livechat/chatbots.rst:188 +#: ../../content/applications/websites/livechat/chatbots.rst:204 msgid "Welcome Bot: \"*Hmmm, let me check if I can find someone that could help you with that...*\"" msgstr "" -#: ../../content/applications/websites/livechat/chatbots.rst:190 +#: ../../content/applications/websites/livechat/chatbots.rst:206 msgid "In the details form for the :guilabel:`Text` step, the *I have a pricing question* response has been selected in the :guilabel:`Only If` field. As such, this step is **only** shown in conversations where that response has been selected." msgstr "" @@ -3559,51 +3613,59 @@ msgstr "" msgid "View of the new message form emphasizing the Only If field." msgstr "" -#: ../../content/applications/websites/livechat/chatbots.rst:199 +#: ../../content/applications/websites/livechat/chatbots.rst:215 msgid "Script testing" msgstr "" -#: ../../content/applications/websites/livechat/chatbots.rst:201 -msgid "In order to ensure all visitors have a satisfactory experience with the chatbot, each message needs to lead to a natural conclusion. Chatbot scripts should be tested to confirm there are no dead-ends, and to get an understanding of what the visitor sees when they interact with the chatbot." +#: ../../content/applications/websites/livechat/chatbots.rst:217 +msgid "To ensure all visitors have a satisfactory experience with the chatbot, each message needs to lead to a natural conclusion. Chatbot scripts should be tested to confirm there are no dead-ends, and to understand what the visitor sees when they interact with the chatbot." msgstr "" -#: ../../content/applications/websites/livechat/chatbots.rst:206 -msgid "If there is an answer or input provided by the visitor that is **not** assigned a corresponding follow-up response, the conversation stops (*dead-end*). Since the visitor cannot re-engage the chatbot, they will have to re-start the conversation, by refreshing the chat window, or their browser." +#: ../../content/applications/websites/livechat/chatbots.rst:222 +msgid "If the visitor provides an answer, or input, that is **not** assigned a corresponding follow-up response, the conversation stops (*dead-ends*). Since the visitor cannot re-engage the chatbot, they must restart the conversation by refreshing the chat window, or their browser." msgstr "" -#: ../../content/applications/websites/livechat/chatbots.rst:211 +#: ../../content/applications/websites/livechat/chatbots.rst:226 msgid "To test the performance of a chatbot, first click on the :guilabel:`Test` button at the top-left of the chatbot script page. Then, upon being redirected to the testing screen, answer the chatbot prompts the same way a potential site visitor would." msgstr "" -#: ../../content/applications/websites/livechat/chatbots.rst:215 +#: ../../content/applications/websites/livechat/chatbots.rst:230 msgid "When the script has reached an end-point, the message *Conversation ended...Restart* appears at the bottom of the chat window. To begin the conversation at the beginning of the script, click on :guilabel:`Restart`. To return to the script page, click :guilabel:`Back to edit mode` at the top of the page." msgstr "" -#: ../../content/applications/websites/livechat/chatbots.rst:221 +#: ../../content/applications/websites/livechat/chatbots.rst:236 msgid "Add chatbot to a channel" msgstr "" -#: ../../content/applications/websites/livechat/chatbots.rst:223 +#: ../../content/applications/websites/livechat/chatbots.rst:238 msgid "After a chatbot has been created and tested, it needs to be added to a live chat channel." msgstr "" -#: ../../content/applications/websites/livechat/chatbots.rst:225 -msgid "First, open the :menuselection:`Live Chat` application, and select the kanban card for a :guilabel:`Channel`, or create a :doc:`new one `. Click on the :guilabel:`Channel Rules` tab. Then, open an existing rule, or create a new one by clicking :guilabel:`Add a line`." +#: ../../content/applications/websites/livechat/chatbots.rst:240 +msgid "First, open the :menuselection:`Live Chat` application, find the Kanban card for the appropriate live chat channel, hover over it, and click the :guilabel:`⋮ (three dots)` icon to open the drop-down menu. Click :guilabel:`Configure Channel` to open the channel detail form." msgstr "" -#: ../../content/applications/websites/livechat/chatbots.rst:230 -msgid "On the :guilabel:`Create Rules` pop-up detail form, choose the appropriate chatbot in the :guilabel:`Chatbot` field." +#: ../../content/applications/websites/livechat/chatbots.rst:245 +msgid "To create a new live chat channel, open the :menuselection:`Live Chat app` and click :guilabel:`New`. See :doc:`Live Chat <../livechat>` for more information." msgstr "" -#: ../../content/applications/websites/livechat/chatbots.rst:233 -msgid "If the chatbot should **only** be active if there are no available live chat operators, check the box labeled :guilabel:`Enabled only if no operator`." +#: ../../content/applications/websites/livechat/chatbots.rst:248 +msgid "Click on the :guilabel:`Channel Rules` tab. Then, open an existing rule, or create a new one by clicking :guilabel:`Add a line`." +msgstr "" + +#: ../../content/applications/websites/livechat/chatbots.rst:251 +msgid "On the :guilabel:`Create Rules` modal, choose the appropriate chatbot in the :guilabel:`Chatbot` field." +msgstr "" + +#: ../../content/applications/websites/livechat/chatbots.rst:254 +msgid "If the chatbot should **only** be active if there are no live chat operators available, check the box labeled :guilabel:`Enabled only if no operator`." msgstr "" #: ../../content/applications/websites/livechat/chatbots.rst:-1 msgid "View of the channel rules emphasizing the chatbot field." msgstr "" -#: ../../content/applications/websites/livechat/chatbots.rst:241 +#: ../../content/applications/websites/livechat/chatbots.rst:262 msgid ":doc:`Live chat channel rules `" msgstr "" @@ -3775,6 +3837,272 @@ msgstr "" msgid ":doc:`/applications/websites/website`" msgstr "" +#: ../../content/applications/websites/livechat/reports.rst:3 +msgid "Reports" +msgstr "" + +#: ../../content/applications/websites/livechat/reports.rst:5 +msgid "Odoo *Live Chat* includes several reports that allow for the monitoring of operator performance and the identification of trends in customer conversations." +msgstr "" + +#: ../../content/applications/websites/livechat/reports.rst:9 +msgid "Available reports" +msgstr "" + +#: ../../content/applications/websites/livechat/reports.rst:11 +msgid "The following reports are included in the *Live Chat* app:" +msgstr "" + +#: ../../content/applications/websites/livechat/reports.rst:13 +msgid ":ref:`Sessions History `" +msgstr "" + +#: ../../content/applications/websites/livechat/reports.rst:14 +msgid ":ref:`Session Statistics `" +msgstr "" + +#: ../../content/applications/websites/livechat/reports.rst:15 +msgid ":ref:`Operator Analysis `" +msgstr "" + +#: ../../content/applications/websites/livechat/reports.rst:18 +msgid "The *Live Chat Ratings Report* can also be accessed through the :guilabel:`Report` menu. For more information on this report, and on the *Live Chat* rating process, see :doc:`Live Chat Ratings <../livechat/ratings>`." +msgstr "" + +#: ../../content/applications/websites/livechat/reports.rst:22 +msgid "To access a drop-down menu of all the available reports, navigate to :menuselection:`Live Chat app --> Report`." +msgstr "" + +#: ../../content/applications/websites/livechat/reports.rst:28 +msgid "Sessions History" +msgstr "" + +#: ../../content/applications/websites/livechat/reports.rst:30 +msgid "The *Sessions History* report displays an overview of live chat sessions, including session dates, participant name and country, session duration, the number of messages, and the rating. It also provides access to the complete transcripts of live chat sessions." +msgstr "" + +#: ../../content/applications/websites/livechat/reports.rst:34 +msgid "To access this report, navigate to :menuselection:`Live Chat app --> Report --> Sessions History`." +msgstr "" + +#: ../../content/applications/websites/livechat/reports.rst:-1 +msgid "Example of the Sessions History report from the Live Chat application." +msgstr "" + +#: ../../content/applications/websites/livechat/reports.rst:40 +msgid "The information in this report can be exported, or inserted into a spreadsheet." +msgstr "" + +#: ../../content/applications/websites/livechat/reports.rst:42 +msgid "Click the :guilabel:`⚙️ (gear)` icon to the right of the :guilabel:`History` page title, in the top-left corner. Doing so reveals a drop-down menu." +msgstr "" + +#: ../../content/applications/websites/livechat/reports.rst:45 +msgid "From the drop-down menu, click :guilabel:`Export All` to export all sessions to a spreadsheet, or :guilabel:`Insert list in spreadsheet` to insert the information in a new, or existing, spreadsheet." +msgstr "" + +#: ../../content/applications/websites/livechat/reports.rst:48 +msgid "To only export select sessions, first select the desired sessions to be exported from the list, by clicking the checkbox to the left of each individual session. With the sessions selected, click the :guilabel:`⚙️ (gear) Actions` icon in the top-center of the page, and click :guilabel:`Export` or :guilabel:`Insert list in spreadsheet`." +msgstr "" + +#: ../../content/applications/websites/livechat/reports.rst:53 +msgid "To view the transcript of an individual conversation, click anywhere on the entry line. This opens the *Discuss* thread for the conversation." +msgstr "" + +#: ../../content/applications/websites/livechat/reports.rst:56 +msgid "In the *Discuss* thread, the conversation view displays the entire transcript of the conversation. At the top of the conversation, there is a list of the web pages the visitor browsed before beginning their chat session, along with corresponding time stamps. If the visitor left a rating, it is included at the end of the transcript." +msgstr "" + +#: ../../content/applications/websites/livechat/reports.rst:-1 +msgid "View of the chat transcript in the Discuss application." +msgstr "" + +#: ../../content/applications/websites/livechat/reports.rst:68 +msgid "Session Statistics" +msgstr "" + +#: ../../content/applications/websites/livechat/reports.rst:70 +msgid "The *Session Statistics* report provides a statistical overview of live chat sessions. The default view for this report displays sessions grouped by the date of creation." +msgstr "" + +#: ../../content/applications/websites/livechat/reports.rst:73 +msgid "To access this report, navigate to :menuselection:`Live Chat app --> Reports --> Session Statistics`." +msgstr "" + +#: ../../content/applications/websites/livechat/reports.rst:80 +msgid "Example of the Sessions Statistics report from the Live Chat application." +msgstr "" + +#: ../../content/applications/websites/livechat/reports.rst:80 +msgid "The stacked bar graph view of the *Session Statistics* report, with results grouped by Creation Date (hour), then by rating." +msgstr "" + +#: ../../content/applications/websites/livechat/reports.rst:83 +#: ../../content/applications/websites/livechat/reports.rst:115 +msgid "To view a different measure, click the :guilabel:`Measures` drop-down menu at the top-left of the report. The measures available for this report include:" +msgstr "" + +#: ../../content/applications/websites/livechat/reports.rst:86 +msgid ":guilabel:`# of speakers`: number of participants in the conversation." +msgstr "" + +#: ../../content/applications/websites/livechat/reports.rst:87 +msgid ":guilabel:`Days of activity`: number of days since the operator's first session." +msgstr "" + +#: ../../content/applications/websites/livechat/reports.rst:88 +msgid ":guilabel:`Duration of Session (min)`: the duration of a conversation, in minutes." +msgstr "" + +#: ../../content/applications/websites/livechat/reports.rst:89 +msgid ":guilabel:`Is visitor anonymous`: denotes whether the conversation participant is anonymous." +msgstr "" + +#: ../../content/applications/websites/livechat/reports.rst:90 +msgid ":guilabel:`Messages per session`: the total number of messages sent in a conversation. This measure is included in the default view." +msgstr "" + +#: ../../content/applications/websites/livechat/reports.rst:92 +msgid ":guilabel:`Rating`: the rating received by an operator at the end of a session, if one was provided." +msgstr "" + +#: ../../content/applications/websites/livechat/reports.rst:94 +msgid ":guilabel:`Session not rated`: denotes if a session did **not** receive a rating at the end of the conversation." +msgstr "" + +#: ../../content/applications/websites/livechat/reports.rst:96 +msgid ":guilabel:`Time to answer (sec)`: the average time, in seconds, before an operator responds to a chat request." +msgstr "" + +#: ../../content/applications/websites/livechat/reports.rst:98 +msgid ":guilabel:`Visitor is Happy`: denotes whether a positive rating was provided. If the visitor gave either a negative or neutral rating, they are considered *unhappy*." +msgstr "" + +#: ../../content/applications/websites/livechat/reports.rst:100 +#: ../../content/applications/websites/livechat/reports.rst:124 +msgid ":guilabel:`Count`: the total number of sessions." +msgstr "" + +#: ../../content/applications/websites/livechat/reports.rst:105 +msgid "Operator Analysis" +msgstr "" + +#: ../../content/applications/websites/livechat/reports.rst:107 +msgid "The *Operator Analysis* report is used to monitor the performance of individual live chat operators." +msgstr "" + +#: ../../content/applications/websites/livechat/reports.rst:109 +msgid "To access the report, navigate to :menuselection:`Live Chat app --> Reports --> Operator Analysis`." +msgstr "" + +#: ../../content/applications/websites/livechat/reports.rst:111 +msgid "The default view for this report is a bar chart, which only displays conversations from the current month, as indicated by the :guilabel:`This Month` default search filter. Conversations are grouped by operator." +msgstr "" + +#: ../../content/applications/websites/livechat/reports.rst:118 +msgid ":guilabel:`# of Sessions`: the number of sessions an operator participated in. This measure is included by default." +msgstr "" + +#: ../../content/applications/websites/livechat/reports.rst:120 +msgid ":guilabel:`Average duration`: the average duration of a conversation, in seconds." +msgstr "" + +#: ../../content/applications/websites/livechat/reports.rst:121 +msgid ":guilabel:`Average rating`: the average rating received by the operator." +msgstr "" + +#: ../../content/applications/websites/livechat/reports.rst:122 +msgid ":guilabel:`Time to answer`: the average amount of time before the operator responds to a chat request, in seconds." +msgstr "" + +#: ../../content/applications/websites/livechat/reports.rst:-1 +msgid "Example of the Operator Analysis report from the Live Chat application." +msgstr "" + +#: ../../content/applications/websites/livechat/reports.rst:131 +msgid "View and filter options" +msgstr "" + +#: ../../content/applications/websites/livechat/reports.rst:133 +msgid "On any Odoo report, the view and filter options vary, depending on what data is being analyzed, measured, and grouped. See below for additional information on the available views for the *Live Chat* reports." +msgstr "" + +#: ../../content/applications/websites/livechat/reports.rst:138 +msgid "The :ref:`Sessions History ` report is **only** available in list view." +msgstr "" + +#: ../../content/applications/websites/livechat/reports.rst:142 +msgid "Pivot view" +msgstr "" + +#: ../../content/applications/websites/livechat/reports.rst:144 +msgid "The *pivot* view presents data in an interactive manner. The :ref:`Session Statistics ` and :ref:`Operator Analysis ` reports are available in pivot view." +msgstr "" + +#: ../../content/applications/websites/livechat/reports.rst:148 +msgid "The pivot view can be accessed on a report by selecting the :guilabel:`grid icon` at the top-right of the screen." +msgstr "" + +#: ../../content/applications/websites/livechat/reports.rst:151 +msgid "To add a group to a row or column, click the :guilabel:`➕ (plus sign)` icon next to :guilabel:`Total`, and then select one of the groups from the drop-down menu that appears. To remove one, click the :guilabel:`➖ (minus sign)` icon, and de-select the appropriate option." +msgstr "" + +#: ../../content/applications/websites/livechat/reports.rst:156 +msgid "Graph view" +msgstr "" + +#: ../../content/applications/websites/livechat/reports.rst:158 +msgid "The *graph* view presents data in either a *bar*, *line*, or *pie* chart. The :ref:`Session Statistics ` and :ref:`Operator Analysis ` reports are available in graph view." +msgstr "" + +#: ../../content/applications/websites/livechat/reports.rst:162 +msgid "Switch to the graph view by selecting the :guilabel:`line chart` icon at the top-right of the screen. To switch between the different charts, select the desired view's corresponding icon at the top-left of the chart, while in graph view." +msgstr "" + +#: ../../content/applications/websites/livechat/reports.rst:167 +msgid "Both the bar chart and line chart can utilize the *stacked* view option. This presents two or more groups of data on top of each other, instead of next to each other, making it easier to compare data." +msgstr "" + +#: ../../content/applications/websites/livechat/reports.rst:172 +msgid "Save and share a favorite search" +msgstr "" + +#: ../../content/applications/websites/livechat/reports.rst:174 +msgid "The *Favorites* feature found on reports allows users to save their most commonly used filters, without having to reconstruct them every time they are needed." +msgstr "" + +#: ../../content/applications/websites/livechat/reports.rst:177 +msgid "To create and save a filter to the *Favorites* section on the search bar drop-down menu, follow the steps below:" +msgstr "" + +#: ../../content/applications/websites/livechat/reports.rst:180 +msgid "Set the necessary parameters using the :guilabel:`Filters` and :guilabel:`Group By` options available in the :guilabel:`Search...` bar drop-down menu and the :guilabel:`Measures` drop-down menu at the top-left of the report." +msgstr "" + +#: ../../content/applications/websites/livechat/reports.rst:183 +msgid "Click the :guilabel:`🔻(triangle pointed down)` icon next to the :guilabel:`Search...` bar to open the drop-down menu." +msgstr "" + +#: ../../content/applications/websites/livechat/reports.rst:185 +msgid "Under the :guilabel:`Favorites` heading, click :guilabel:`Save current search`." +msgstr "" + +#: ../../content/applications/websites/livechat/reports.rst:186 +msgid "Rename the search." +msgstr "" + +#: ../../content/applications/websites/livechat/reports.rst:187 +msgid "Select :guilabel:`Default filter` to have these filter settings automatically displayed when the report is opened. Otherwise, leave it blank." +msgstr "" + +#: ../../content/applications/websites/livechat/reports.rst:189 +msgid "Select :guilabel:`Shared` to make this filter available to all other database users. If this box is not checked, the filter is only available to the user who creates it." +msgstr "" + +#: ../../content/applications/websites/livechat/reports.rst:191 +msgid "Click :guilabel:`Save` to preserve the configuration for future use." +msgstr "" + #: ../../content/applications/websites/livechat/responses.rst:3 msgid "Commands and canned responses" msgstr "" @@ -4489,53 +4817,53 @@ 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." +msgid "Adding 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:157 #: ../../content/applications/websites/website/configuration/domain_names.rst:212 msgid "Odoo Online" msgstr "" -#: ../../content/applications/websites/website/configuration/domain_names.rst:160 +#: ../../content/applications/websites/website/configuration/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/applications/websites/website/configuration/domain_names.rst:163 +#: ../../content/applications/websites/website/configuration/domain_names.rst:162 #: ../../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." +#: ../../content/applications/websites/website/configuration/domain_names.rst:164 +msgid "The CNAME record's target address should 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 +#: ../../content/applications/websites/website/configuration/domain_names.rst:170 msgid "The specific instructions depend on your DNS hosting service." msgstr "" -#: ../../content/applications/websites/website/configuration/domain_names.rst:174 +#: ../../content/applications/websites/website/configuration/domain_names.rst:173 msgid "`GoDaddy: Add a CNAME record `_" msgstr "" -#: ../../content/applications/websites/website/configuration/domain_names.rst:175 +#: ../../content/applications/websites/website/configuration/domain_names.rst:174 msgid "`Namecheap: How to create a CNAME record for your domain `_" msgstr "" -#: ../../content/applications/websites/website/configuration/domain_names.rst:176 +#: ../../content/applications/websites/website/configuration/domain_names.rst:175 msgid "`OVHcloud: Add a new DNS record `_" msgstr "" -#: ../../content/applications/websites/website/configuration/domain_names.rst:177 +#: ../../content/applications/websites/website/configuration/domain_names.rst:176 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." +msgid "Odoo only supports subdomains. To use your naked domain name :dfn:`(a domain name without any subdomains or prefixes)` (`yourdomain.com`), create a redirection 301 to redirect visitors to `www.yourdomain.com`." 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`." +#: ../../content/applications/websites/website/configuration/domain_names.rst:185 +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` and also with the naked domain `yourdomain.com`." msgstr "" #: ../../content/applications/websites/website/configuration/domain_names.rst:189 @@ -6207,79 +6535,91 @@ msgid "The data is collected in the marketing tools used to monitor the website msgstr "" #: ../../content/applications/websites/website/reporting/link_tracker.rst:3 -msgid "Link trackers" +msgid "Link tracker" msgstr "" #: ../../content/applications/websites/website/reporting/link_tracker.rst:5 -msgid "Link Trackers allow you to track your marketing campaigns (emails, banner ads, blog posts, social media posts, affiliate links, etc.). This way, you are able to identify your best traffic sources and make informed decisions about the distribution of your marketing budget." +msgid "The link tracker allow you to create tracked links to measure your marketing campaigns' effectiveness. They let you determine which channels bring you the most visitors and make informed decisions." msgstr "" #: ../../content/applications/websites/website/reporting/link_tracker.rst:12 -msgid "Go to :menuselection:`Website --> Configuration --> Settings` and activate *Link Trackers*." +msgid "The :guilabel:`Link Tracker` module is not installed by default. You need to enable the :guilabel:`Email Marketing` option by going to :menuselection:`Website --> Configuration --> Settings.` Alternatively, you can :doc:`install <../../../general/apps_modules>` the :guilabel:`Link Tracker` module itself or one of the marketing apps." msgstr "" -#: ../../content/applications/websites/website/reporting/link_tracker.rst:-1 -msgid "View of Website settings page emphasizing the link trackers field in Odoo Website" +#: ../../content/applications/websites/website/reporting/link_tracker.rst:18 +msgid "Create a traceable URL" msgstr "" -#: ../../content/applications/websites/website/reporting/link_tracker.rst:19 -msgid "Set up traceable URLs" +#: ../../content/applications/websites/website/reporting/link_tracker.rst:20 +msgid "To create and manage tracked links, navigate to :menuselection:`Website --> Site --> Link Tracker`. Fill in the following information and click :guilabel:`Get tracked link` to generate a tracking URL." msgstr "" -#: ../../content/applications/websites/website/reporting/link_tracker.rst:21 -msgid "Go to :menuselection:`Website --> Go to website --> Promote --> Track this page`. Here, you are able to get a specific tracked URL based on the campaign, medium, and source being used." +#: ../../content/applications/websites/website/reporting/link_tracker.rst:23 +msgid ":guilabel:`URL`: The URL which is the target of the campaign. It is automatically populated with the URL from where you access the menu." msgstr "" -#: ../../content/applications/websites/website/reporting/link_tracker.rst:-1 -msgid "View of the link tracker fields for Odoo Website" -msgstr "" - -#: ../../content/applications/websites/website/reporting/link_tracker.rst:28 -msgid "**URL**: url of the page you want to track (e.g. the home page or a product's page)." +#: ../../content/applications/websites/website/reporting/link_tracker.rst:26 +msgid ":guilabel:`Campaign`: The specific campaign the link should be associated with. This parameter is used to distinguish the different campaigns." msgstr "" #: ../../content/applications/websites/website/reporting/link_tracker.rst:29 -msgid "**Campaign**: context of your link (e.g. a special promotion)." +msgid ":guilabel:`Medium`: The medium describes the category or method through which the visitor arrives at your site, such as organic search, paid search, social media ad, email, etc." msgstr "" -#: ../../content/applications/websites/website/reporting/link_tracker.rst:30 -msgid "**Medium**: channel used to share (deliver) your link (e.g. an email or a Facebook ad)." -msgstr "" - -#: ../../content/applications/websites/website/reporting/link_tracker.rst:31 -msgid "**Source**: platform where the traffic originates (e.g. Google or Twitter)." -msgstr "" - -#: ../../content/applications/websites/website/reporting/link_tracker.rst:33 -msgid "Now, click on *Get tracked link* to generate a URL that you can post or send by the source you have decided on." -msgstr "" - -#: ../../content/applications/websites/website/reporting/link_tracker.rst:37 -msgid "Follow-up on tracked links" -msgstr "" - -#: ../../content/applications/websites/website/reporting/link_tracker.rst:39 -msgid "To look at statistics of your links, go to :menuselection:`Website --> Go to website --> Promote --> Track this page`. Besides being able to see the *Most Clicked* and *Recently Used* links, you can also see complete statistics by clicking on *Stats*, including the number of clicks, and the country of origin for those clicks." +#: ../../content/applications/websites/website/reporting/link_tracker.rst:32 +msgid ":guilabel:`Source`: The source identifies the precise platform or website that referred the visitor, such as a search engine, a newsletter, or a website." msgstr "" #: ../../content/applications/websites/website/reporting/link_tracker.rst:-1 -msgid "View of the tracked list emphasizing the statistics buttons in Odoo Website" +msgid "Create a link tracker URL" msgstr "" -#: ../../content/applications/websites/website/reporting/link_tracker.rst:50 -msgid "You can also access the link tracker on *odoo.com/r* via your browser." +#: ../../content/applications/websites/website/reporting/link_tracker.rst:38 +msgid "The :guilabel:`Campaign`, :guilabel:`Medium`, and :guilabel:`Source` are called :abbr:`UTM (Urchin Tracking Module)` parameters. They are incorporated in the tracked URL." msgstr "" -#: ../../content/applications/websites/website/reporting/link_tracker.rst:51 -msgid "Activate the developer mode (:menuselection:`Settings --> Activate the developer mode`) and get access to the *Link Tracker* module and its back-end functionalities." +#: ../../content/applications/websites/website/reporting/link_tracker.rst:42 +msgid "Website visibility" msgstr "" -#: ../../content/applications/websites/website/reporting/link_tracker.rst:53 -msgid "Integrated with :ref:`analytics/google-analytics`, those trackers allow you to see the number of clicks and visitors to keep you on top of your marketing campaigns." +#: ../../content/applications/websites/website/reporting/link_tracker.rst:44 +msgid "You can use the :abbr:`UTM (Urchin Tracking Module)` parameters to hide or show building blocks for specific audiences. To achieve this, click the :guilabel:`Edit` button on your website, select a building block, go to the :guilabel:`Customize` tab, scroll down to :guilabel:`Visibility`, and click :guilabel:`Conditionally`." msgstr "" -#: ../../content/applications/websites/website/reporting/link_tracker.rst:55 -msgid "The integration with the :doc:`CRM ` application allows you to understand where your leads and opportunities are coming from." +#: ../../content/applications/websites/website/reporting/link_tracker.rst:-1 +msgid "Use the conditional visibility to display site elements to specific audiences." +msgstr "" + +#: ../../content/applications/websites/website/reporting/link_tracker.rst:52 +msgid "For each parameter available in the :ref:`Visibility ` section, you can choose :guilabel:`Visible for` or :guilabel:`Hidden for` and select the record you want from the dropdown list." +msgstr "" + +#: ../../content/applications/websites/website/reporting/link_tracker.rst:57 +msgid "Tracked links overview" +msgstr "" + +#: ../../content/applications/websites/website/reporting/link_tracker.rst:59 +msgid "To get an overview of your tracked links, go to :menuselection:`Website --> Site --> Link Tracker` and scroll down to :guilabel:`Your tracked links` section." +msgstr "" + +#: ../../content/applications/websites/website/reporting/link_tracker.rst:-1 +msgid "Get an overview of all the links you track." +msgstr "" + +#: ../../content/applications/websites/website/reporting/link_tracker.rst:66 +msgid "Statistics" +msgstr "" + +#: ../../content/applications/websites/website/reporting/link_tracker.rst:68 +msgid "To measure the performance of tracked links, click the :guilabel:`Stats` button." +msgstr "" + +#: ../../content/applications/websites/website/reporting/link_tracker.rst:-1 +msgid "View the statistics related to a specific tracked link." +msgstr "" + +#: ../../content/applications/websites/website/reporting/link_tracker.rst:73 +msgid "Scroll down to the :guilabel:`Statistics` section to get an overview of the number of clicks of your tracked links. You can display information for a specific period by clicking the :guilabel:`All Time`, :guilabel:`Last Month`, or :guilabel:`Last Week` options." msgstr "" #: ../../content/applications/websites/website/web_design.rst:5 @@ -6395,15 +6735,15 @@ msgstr "" msgid "Reordering building blocks" msgstr "" -#: ../../content/applications/websites/website/web_design/building_blocks.rst:92 +#: ../../content/applications/websites/website/web_design/building_blocks.rst:94 msgid "Visibility" msgstr "" -#: ../../content/applications/websites/website/web_design/building_blocks.rst:95 +#: ../../content/applications/websites/website/web_design/building_blocks.rst:97 msgid "Visibility on desktop/mobile" msgstr "" -#: ../../content/applications/websites/website/web_design/building_blocks.rst:97 +#: ../../content/applications/websites/website/web_design/building_blocks.rst:99 msgid "You can hide specific elements depending on the visitor's device. To do so, select the element to hide, and in the :guilabel:`Customize` tab, scroll down to :guilabel:`Visibility`, and click the :guilabel:`Show/Hide on Mobile` or the :guilabel:`Show/Hide on Desktop` icon." msgstr "" @@ -6411,7 +6751,7 @@ msgstr "" msgid "Click the \"show/hide on mobile\" icons to show or hide some elements on mobile." msgstr "" -#: ../../content/applications/websites/website/web_design/building_blocks.rst:105 +#: ../../content/applications/websites/website/web_design/building_blocks.rst:107 msgid "Click the phone icon at the top of the configurator to preview how your website would look on a mobile device." msgstr "" @@ -6419,31 +6759,31 @@ msgstr "" msgid "Mobile phone preview icon" msgstr "" -#: ../../content/applications/websites/website/web_design/building_blocks.rst:112 +#: ../../content/applications/websites/website/web_design/building_blocks.rst:114 msgid "Conditional visibility" msgstr "" -#: ../../content/applications/websites/website/web_design/building_blocks.rst:114 +#: ../../content/applications/websites/website/web_design/building_blocks.rst:116 msgid "You can also hide or show building blocks using other conditions. To do so, select an element, go to :guilabel:`Visibility`, click :guilabel:`No condition`, and select :guilabel:`Conditionally` instead. Then, configure the condition(s) to apply by selecting :guilabel:`Visible for` or :guilabel:`Hidden for` and which :guilabel:`Records` will be impacted." msgstr "" -#: ../../content/applications/websites/website/web_design/building_blocks.rst:120 -msgid ":doc:`Link Tracker and UTMs <../reporting/link_tracker>`" -msgstr "" - -#: ../../content/applications/websites/website/web_design/building_blocks.rst:123 -msgid "Invisible elements" +#: ../../content/applications/websites/website/web_design/building_blocks.rst:122 +msgid ":doc:`Link Tracker <../reporting/link_tracker>`" msgstr "" #: ../../content/applications/websites/website/web_design/building_blocks.rst:125 +msgid "Invisible elements" +msgstr "" + +#: ../../content/applications/websites/website/web_design/building_blocks.rst:127 msgid "Depending on the visibility settings, some elements can become hidden from your current view. To make a building block visible again, go to the :guilabel:`Invisible Elements` section at the bottom of the configurator and select a building block." msgstr "" -#: ../../content/applications/websites/website/web_design/building_blocks.rst:130 +#: ../../content/applications/websites/website/web_design/building_blocks.rst:132 msgid "Saving a custom building block" msgstr "" -#: ../../content/applications/websites/website/web_design/building_blocks.rst:132 +#: ../../content/applications/websites/website/web_design/building_blocks.rst:134 msgid "You can save a customized building block and reuse it elsewhere. To do so, select it, navigate to the :guilabel:`Customize` tab, and click the floppy disk icon to save it." msgstr "" @@ -6451,7 +6791,7 @@ msgstr "" msgid "Saving a building block" msgstr "" -#: ../../content/applications/websites/website/web_design/building_blocks.rst:138 +#: ../../content/applications/websites/website/web_design/building_blocks.rst:140 msgid "Saved building blocks are available in the :guilabel:`Custom` section of the :guilabel:`Blocks` tab. Click the pen icon to edit their name." msgstr "" @@ -6459,8 +6799,158 @@ msgstr "" msgid "Custom section with saved building blocks" msgstr "" +#: ../../content/applications/websites/website/web_design/building_blocks/dynamic_content.rst:3 +msgid "Dynamic content" +msgstr "" + +#: ../../content/applications/websites/website/web_design/building_blocks/dynamic_content.rst:5 +msgid "The :guilabel:`Dynamic Content` building blocks, such as :ref:`Form `, :ref:`Products `, :ref:`Embed Code `, or :doc:`Blog Posts <../../../blog>`, help you create interactive and visually appealing layouts for your web pages." +msgstr "" + +#: ../../content/applications/websites/website/web_design/building_blocks/dynamic_content.rst:11 +#: ../../content/applications/websites/website/web_design/building_blocks/inner_content.rst:10 +#: ../../content/applications/websites/website/web_design/building_blocks/structure.rst:12 +msgid "To add a building block, click :guilabel:`Edit`, select the desired building block under the :guilabel:`Blocks` tab, and drag and drop it onto the page. To access its settings, click it and go to the :guilabel:`Customize` tab, where the available options depend on the type of block selected." +msgstr "" + +#: ../../content/applications/websites/website/web_design/building_blocks/dynamic_content.rst:19 +msgid "Form" +msgstr "" + +#: ../../content/applications/websites/website/web_design/building_blocks/dynamic_content.rst:21 +msgid "The :guilabel:`Form` block is used to collect information from website visitors and create records in your database." +msgstr "" + +#: ../../content/applications/websites/website/web_design/building_blocks/dynamic_content.rst:-1 +msgid "Example of a form block" +msgstr "" + +#: ../../content/applications/websites/website/web_design/building_blocks/dynamic_content.rst:28 +msgid "Action" +msgstr "" + +#: ../../content/applications/websites/website/web_design/building_blocks/dynamic_content.rst:30 +msgid "By default, submitting the form **sends you an email** containing what the visitor entered. Depending on the apps installed on your database, new actions that can automatically create records become available:" +msgstr "" + +#: ../../content/applications/websites/website/web_design/building_blocks/dynamic_content.rst:34 +msgid ":guilabel:`Apply for a Job` (Recruitment)" +msgstr "" + +#: ../../content/applications/websites/website/web_design/building_blocks/dynamic_content.rst:35 +msgid ":guilabel:`Create a Customer` (eCommerce)" +msgstr "" + +#: ../../content/applications/websites/website/web_design/building_blocks/dynamic_content.rst:36 +msgid ":guilabel:`Create a Ticket` (Helpdesk)" +msgstr "" + +#: ../../content/applications/websites/website/web_design/building_blocks/dynamic_content.rst:37 +msgid ":guilabel:`Create an Opportunity` (CRM)" +msgstr "" + +#: ../../content/applications/websites/website/web_design/building_blocks/dynamic_content.rst:38 +msgid ":guilabel:`Subscribe to Newsletter` (Email Marketing)" +msgstr "" + +#: ../../content/applications/websites/website/web_design/building_blocks/dynamic_content.rst:39 +msgid ":guilabel:`Create a Task` (Project)" +msgstr "" + +#: ../../content/applications/websites/website/web_design/building_blocks/dynamic_content.rst:41 +msgid "Select another action with the :guilabel:`Action` field found under the :guilabel:`Customize` tab's :guilabel:`Form` section." +msgstr "" + +#: ../../content/applications/websites/website/web_design/building_blocks/dynamic_content.rst:-1 +msgid "Editing a form to change its action" +msgstr "" + +#: ../../content/applications/websites/website/web_design/building_blocks/dynamic_content.rst:47 +msgid "By default, actions redirect visitors to a *thank you* page after submitting the form. Use the :guilabel:`URL` field to change where they are redirected. It is also possible to let visitors stay on the form's page by selecting :guilabel:`Nothing` or :guilabel:`Show Message` under the :guilabel:`On Success` field." +msgstr "" + +#: ../../content/applications/websites/website/web_design/building_blocks/dynamic_content.rst:53 +msgid "Fields" +msgstr "" + +#: ../../content/applications/websites/website/web_design/building_blocks/dynamic_content.rst:55 +msgid "To add a new field to the form, click the :guilabel:`+ Field` button found next to the Customize tab's :guilabel:`Form` or :guilabel:`Field` section. By default, new fields are *text* fields. To change the type, use the :guilabel:`Type` field and select an option under the :guilabel:`Custom Field` heading." +msgstr "" + +#: ../../content/applications/websites/website/web_design/building_blocks/dynamic_content.rst:0 +msgid "All types of form fields" +msgstr "" + +#: ../../content/applications/websites/website/web_design/building_blocks/dynamic_content.rst:65 +msgid "Some fields are visually similar, but the data entered must follow a specific format." +msgstr "" + +#: ../../content/applications/websites/website/web_design/building_blocks/dynamic_content.rst:67 +msgid "It is also possible to select an :guilabel:`Existing Field` from a database and use the data it contains. The fields available depend on the selected action." +msgstr "" + +#: ../../content/applications/websites/website/web_design/building_blocks/dynamic_content.rst:71 +msgid "Property fields added to the database can also be used." +msgstr "" + +#: ../../content/applications/websites/website/web_design/building_blocks/dynamic_content.rst:78 +msgid "The :guilabel:`Products` block is available after installing the eCommerce app. It is used to display a selection of products sold on your website." +msgstr "" + +#: ../../content/applications/websites/website/web_design/building_blocks/dynamic_content.rst:-1 +msgid "Example of a products block" +msgstr "" + +#: ../../content/applications/websites/website/web_design/building_blocks/dynamic_content.rst:84 +msgid "By default, the block displays the :guilabel:`Newest Products`. To change which products are shown, go to the :guilabel:`Customize` tab's :guilabel:`Products` section and select as :guilabel:`Filter` the :guilabel:`Recently Sold Products` or :guilabel:`Recently Viewed Products` option." +msgstr "" + +#: ../../content/applications/websites/website/web_design/building_blocks/dynamic_content.rst:88 +msgid "In addition, it is possible to display products from a single category only by selecting one with the :guilabel:`Category` field." +msgstr "" + +#: ../../content/applications/websites/website/web_design/building_blocks/dynamic_content.rst:94 +msgid "Embed code" +msgstr "" + +#: ../../content/applications/websites/website/web_design/building_blocks/dynamic_content.rst:96 +msgid "Embedding code allows you to integrate content from third-party services into a page, such as videos from YouTube, maps from Google Maps, social media posts from Instagram, etc." +msgstr "" + +#: ../../content/applications/websites/website/web_design/building_blocks/dynamic_content.rst:-1 +msgid "Add the link to the embedded code you want to point to" +msgstr "" + +#: ../../content/applications/websites/website/web_design/building_blocks/dynamic_content.rst:102 +msgid "After adding the block to a page, click the :guilabel:`Edit` button found under the :guilabel:`Customize` tab's :guilabel:`Embed Code` section and enter the code, replacing the code used to show the block's instructions." +msgstr "" + +#: ../../content/applications/websites/website/web_design/building_blocks/inner_content.rst:3 +msgid "Inner content" +msgstr "" + +#: ../../content/applications/websites/website/web_design/building_blocks/inner_content.rst:5 +msgid "The :guilabel:`Inner content` :doc:`building blocks <../building_blocks>` allow you to add elements such as videos, images, and :ref:`social media buttons `, into pre-existing blocks." +msgstr "" + +#: ../../content/applications/websites/website/web_design/building_blocks/inner_content.rst:18 +msgid "Social media" +msgstr "" + +#: ../../content/applications/websites/website/web_design/building_blocks/inner_content.rst:20 +msgid "The :guilabel:`Social Media` block inserts clickable buttons leading to your social network's URL. By default, the buttons display the icons of seven major social networks. You can click :guilabel:`Add New Social Network` to create a new button and switch the buttons next to a URL to turn them on or off." +msgstr "" + +#: ../../content/applications/websites/website/web_design/building_blocks/inner_content.rst:-1 +msgid "The social media building block and its settings" +msgstr "" + +#: ../../content/applications/websites/website/web_design/building_blocks/inner_content.rst:30 +msgid "You cannot edit the default icons but can edit the ones you added by clicking :guilabel:`Add New Social Network`. To do so, select the icon, then click the :guilabel:`Replace` button found under the :guilabel:`Customize` tab's :guilabel:`Icon` section, and either select one of the available icons or click the :guilabel:`Images` tab and upload an image or add its URL." +msgstr "" + #: ../../content/applications/websites/website/web_design/building_blocks/structure.rst:3 -msgid "Structure blocks" +msgid "Structure" msgstr "" #: ../../content/applications/websites/website/web_design/building_blocks/structure.rst:5 @@ -6468,19 +6958,11 @@ msgid "The website configurator provides a range of :guilabel:`Structure` :doc:` msgstr "" #: ../../content/applications/websites/website/web_design/building_blocks/structure.rst:8 -msgid "To add a block to a web page, click :guilabel:`Edit`, select a block from the :guilabel:`Structure` section, and drag and drop it into the page." -msgstr "" - -#: ../../content/applications/websites/website/web_design/building_blocks/structure.rst:-1 -msgid "Dragging and dropping a building block into a page" -msgstr "" - -#: ../../content/applications/websites/website/web_design/building_blocks/structure.rst:14 msgid "Below are presented two types of structure blocks: :ref:`Banner ` and :ref:`Masonry `." msgstr "" #: ../../content/applications/websites/website/web_design/building_blocks/structure.rst:20 -msgid "Banner block" +msgid "Banner" msgstr "" #: ../../content/applications/websites/website/web_design/building_blocks/structure.rst:22 @@ -6512,11 +6994,11 @@ msgid "Configuring the call to action button" msgstr "" #: ../../content/applications/websites/website/web_design/building_blocks/structure.rst:46 -msgid "Masonry block" +msgid "Masonry" msgstr "" #: ../../content/applications/websites/website/web_design/building_blocks/structure.rst:48 -msgid "The :guilabel:`Masonry` building block offers a range of templates that associate image and text bricks. To change the default template, go to the :guilabel:`Customize` tab, click :guilabel:`Template` and select one." +msgid "The :guilabel:`Masonry` block offers a range of templates that associate image and text bricks. To change the default template, go to the :guilabel:`Customize` tab, click :guilabel:`Template` and select one." msgstr "" #: ../../content/applications/websites/website/web_design/building_blocks/structure.rst:-1 @@ -6524,7 +7006,7 @@ msgid "Selecting a masonry building block template" msgstr "" #: ../../content/applications/websites/website/web_design/building_blocks/structure.rst:56 -msgid "The :guilabel:`Masonry` building block allows you to add text on top of images. To do so, go to the :guilabel:`Customize` tab, scroll to :guilabel:`Add Elements`, and click :guilabel:`Text`." +msgid "The :guilabel:`Masonry` block allows you to add text on top of images. To do so, go to the :guilabel:`Customize` tab, scroll to :guilabel:`Add Elements`, and click :guilabel:`Text`." msgstr "" #: ../../content/applications/websites/website/web_design/building_blocks/structure.rst:0