diff --git a/locale/sources/administration.pot b/locale/sources/administration.pot index 5f0f44fb0..f541e97a7 100644 --- a/locale/sources/administration.pot +++ b/locale/sources/administration.pot @@ -8,7 +8,7 @@ msgid "" msgstr "" "Project-Id-Version: Odoo saas-16.1\n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2023-12-19 13:26+0000\n" +"POT-Creation-Date: 2024-01-19 10:30+0000\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME \n" "Language-Team: LANGUAGE \n" @@ -890,6 +890,82 @@ msgstr "" msgid "If you don't have access/manage your email server, use :ref:`inbound messages `." msgstr "" +#: ../../content/administration/install/geo_ip.rst:3 +msgid "Geo IP" +msgstr "" + +#: ../../content/administration/install/geo_ip.rst:6 +msgid "This documentation only applies to On-premise databases." +msgstr "" + +#: ../../content/administration/install/geo_ip.rst:9 +msgid "Installation" +msgstr "" + +#: ../../content/administration/install/geo_ip.rst:11 +msgid "Download both the GeoLite2 City and Country `databases `_. You should end up with two files called :file:`GeoLite2-City.mmdb` and :file:`GeoLite2-Country.mmdb`." +msgstr "" + +#: ../../content/administration/install/geo_ip.rst:15 +msgid "Move the files to the folder :file:`/usr/share/GeoIP/`." +msgstr "" + +#: ../../content/administration/install/geo_ip.rst:22 +msgid "Restart the server" +msgstr "" + +#: ../../content/administration/install/geo_ip.rst:25 +msgid "If you don't want to locate the geoip database in :file:`/usr/share/GeoIP/`, use the :option:`--geoip-city-db ` and :option:`--geoip-country-db ` options of the Odoo command line interface. These options take the absolute path to the GeoIP database file and use it as the GeoIP database. For example:" +msgstr "" + +#: ../../content/administration/install/geo_ip.rst:36 +msgid ":doc:`CLI documentation `." +msgstr "" + +#: ../../content/administration/install/geo_ip.rst:39 +msgid "Test GeoIP geolocation in your Odoo website" +msgstr "" + +#: ../../content/administration/install/geo_ip.rst:41 +msgid "Edit a web page to include some geo-ip information such as the country name of the current request IP address. To do so:" +msgstr "" + +#: ../../content/administration/install/geo_ip.rst:44 +msgid "Go to your website. Open the web page that you want to test ``GeoIP``." +msgstr "" + +#: ../../content/administration/install/geo_ip.rst:45 +msgid "Choose :menuselection:`Customize --> HTML/CSS/JS Editor`." +msgstr "" + +#: ../../content/administration/install/geo_ip.rst:46 +msgid "Add the following piece of XML in the page :" +msgstr "" + +#: ../../content/administration/install/geo_ip.rst:52 +msgid "Save and refresh the page." +msgstr "" + +#: ../../content/administration/install/geo_ip.rst:54 +msgid "Geo-ip is working if you read your country name displayed in bold in the middle of the page." +msgstr "" + +#: ../../content/administration/install/geo_ip.rst:56 +msgid "In case you read \"**geoip failure**\" instead then the geolocalization failed. The common causes are:" +msgstr "" + +#: ../../content/administration/install/geo_ip.rst:58 +msgid "The browsing IP address is the localhost (``127.0.0.1``) or a local area network one. If you don't know, you can access your website using mobile data." +msgstr "" + +#: ../../content/administration/install/geo_ip.rst:60 +msgid "You are using a reverse-proxy (apache, nginx) in front of Odoo but didn't start Odoo with the proxy-mode enabled. See :option:`proxy mode `." +msgstr "" + +#: ../../content/administration/install/geo_ip.rst:62 +msgid "The GeoIP database is corrupt, missing or unaccessible. In such case a warning was logged in the server logs." +msgstr "" + #: ../../content/administration/install/online.rst:3 msgid "Online" msgstr "" @@ -910,8 +986,8 @@ msgstr "" #: ../../content/administration/maintain/domain_names.rst:166 #: ../../content/administration/maintain/domain_names.rst:236 #: ../../content/administration/maintain/supported_versions.rst:29 -#: ../../content/administration/upgrade.rst:92 -#: ../../content/administration/upgrade.rst:309 +#: ../../content/administration/upgrade.rst:90 +#: ../../content/administration/upgrade.rst:307 msgid "Odoo Online" msgstr "" @@ -2001,8 +2077,8 @@ msgstr "" #: ../../content/administration/maintain/domain_names.rst:250 #: ../../content/administration/maintain/supported_versions.rst:30 #: ../../content/administration/odoo_sh.rst:5 -#: ../../content/administration/upgrade.rst:122 -#: ../../content/administration/upgrade.rst:320 +#: ../../content/administration/upgrade.rst:120 +#: ../../content/administration/upgrade.rst:318 msgid "Odoo.sh" msgstr "" @@ -3148,11 +3224,11 @@ msgid "To remove users, select them and click :guilabel:`Remove`." msgstr "" #: ../../content/administration/maintain/odoo_online.rst:132 -msgid ":doc:`../../applications/general/users/manage_users`" +msgid ":doc:`/applications/general/users/manage_users`" msgstr "" #: ../../content/administration/maintain/odoo_online.rst:133 -msgid ":doc:`../../applications/general/users/delete_account`" +msgid ":doc:`/applications/general/users/odoo_account`" msgstr "" #: ../../content/administration/maintain/on_premise.rst:3 @@ -6027,58 +6103,58 @@ msgid "Migrating from another ERP to Odoo" msgstr "" #: ../../content/administration/upgrade.rst:42 -msgid "If your database contains a **custom module**, you must first upgrade its source code to be compatible with the new version of Odoo **before upgrading**." +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:49 +#: ../../content/administration/upgrade.rst:50 msgid "Upgrading in a nutshell" msgstr "" -#: ../../content/administration/upgrade.rst:51 +#: ../../content/administration/upgrade.rst:52 msgid "Request an upgraded test database (see :ref:`obtaining an upgraded test database `)." msgstr "" -#: ../../content/administration/upgrade.rst:54 +#: ../../content/administration/upgrade.rst:55 +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 msgid "Thoroughly test the upgraded database (see :ref:`testing the new version of the database `)." msgstr "" -#: ../../content/administration/upgrade.rst:57 +#: ../../content/administration/upgrade.rst:61 msgid "Report any issue encountered during the testing to Odoo via the `support page `__." msgstr "" -#: ../../content/administration/upgrade.rst:60 -msgid "(If applicable) : upgrade the source code of your custom module to be compatible with the new version of Odoo." -msgstr "" - -#: ../../content/administration/upgrade.rst:63 +#: ../../content/administration/upgrade.rst:64 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:66 +#: ../../content/administration/upgrade.rst:67 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:69 +#: ../../content/administration/upgrade.rst:70 msgid "Report any issue encountered during the upgrade to Odoo via the `support page `__." msgstr "" -#: ../../content/administration/upgrade.rst:78 +#: ../../content/administration/upgrade.rst:76 msgid "Obtaining an upgraded test database" msgstr "" -#: ../../content/administration/upgrade.rst:80 +#: ../../content/administration/upgrade.rst:78 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:86 +#: ../../content/administration/upgrade.rst:84 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:94 +#: ../../content/administration/upgrade.rst:92 msgid "Odoo Online databases can be manually upgraded via the `database manager `_." msgstr "" -#: ../../content/administration/upgrade.rst:97 +#: ../../content/administration/upgrade.rst:95 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 "" @@ -6086,19 +6162,19 @@ msgstr "" msgid "The database manager with an upgrade button next to the name of a database." msgstr "" -#: ../../content/administration/upgrade.rst:104 +#: ../../content/administration/upgrade.rst:102 msgid "Click the **arrow in a circle** icon to start the upgrade process. In the popup, fill in:" msgstr "" -#: ../../content/administration/upgrade.rst:106 +#: ../../content/administration/upgrade.rst:104 msgid "The **version** of Odoo you want to upgrade to, usually the latest version" msgstr "" -#: ../../content/administration/upgrade.rst:107 +#: ../../content/administration/upgrade.rst:105 msgid "The **email** address that should receive the link to the upgraded database" msgstr "" -#: ../../content/administration/upgrade.rst:108 +#: ../../content/administration/upgrade.rst:106 msgid "The :guilabel:`Purpose` of the upgrade, which is automatically set to :guilabel:`Test` for your first upgrade request" msgstr "" @@ -6106,7 +6182,7 @@ msgstr "" msgid "The \"Upgrade your database\" popup." msgstr "" -#: ../../content/administration/upgrade.rst:114 +#: ../../content/administration/upgrade.rst:112 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 "" @@ -6114,7 +6190,7 @@ msgstr "" msgid "Clicking the menu arrow displays the upgraded test database." msgstr "" -#: ../../content/administration/upgrade.rst:124 +#: ../../content/administration/upgrade.rst:122 msgid "Odoo.sh is integrated with the upgrade platform to simplify the upgrade process." msgstr "" @@ -6122,272 +6198,280 @@ msgstr "" msgid "Odoo.sh project and tabs" msgstr "" -#: ../../content/administration/upgrade.rst:129 +#: ../../content/administration/upgrade.rst:127 msgid "The **latest production daily automatic backup** is then sent to the `upgrade platform `_." msgstr "" -#: ../../content/administration/upgrade.rst:132 +#: ../../content/administration/upgrade.rst:130 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:140 +#: ../../content/administration/upgrade.rst:138 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:152 -#: ../../content/administration/upgrade.rst:344 +#: ../../content/administration/upgrade.rst:143 +msgid "Check out the :doc:`/developer/howtos/upgrade_custom_db` page for more information." +msgstr "" + +#: ../../content/administration/upgrade.rst:145 +#: ../../content/administration/upgrade.rst:341 msgid "On-premise" msgstr "" -#: ../../content/administration/upgrade.rst:154 +#: ../../content/administration/upgrade.rst:147 msgid "The standard upgrade process can be initiated by entering the following command line on the machine where the database is hosted:" msgstr "" -#: ../../content/administration/upgrade.rst:161 +#: ../../content/administration/upgrade.rst:154 msgid "The following command can be used to display the general help and the main commands:" msgstr "" -#: ../../content/administration/upgrade.rst:167 +#: ../../content/administration/upgrade.rst:160 msgid "An upgraded test database can also be requested via the `Upgrade page `_." msgstr "" -#: ../../content/administration/upgrade.rst:171 +#: ../../content/administration/upgrade.rst:164 +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 msgid "For security reasons, only the person who submitted the upgrade request can download it." msgstr "" -#: ../../content/administration/upgrade.rst:172 +#: ../../content/administration/upgrade.rst:170 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:174 +#: ../../content/administration/upgrade.rst:172 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:177 +#: ../../content/administration/upgrade.rst:175 msgid "The upgraded database contains:" msgstr "" -#: ../../content/administration/upgrade.rst:179 +#: ../../content/administration/upgrade.rst:177 msgid "A `dump.sql` file containing the upgraded database" msgstr "" -#: ../../content/administration/upgrade.rst:180 +#: ../../content/administration/upgrade.rst:178 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:187 +#: ../../content/administration/upgrade.rst:185 msgid "You can request multiple test databases if you wish to test an upgrade more than once." msgstr "" -#: ../../content/administration/upgrade.rst:192 +#: ../../content/administration/upgrade.rst:190 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:200 +#: ../../content/administration/upgrade.rst:198 msgid "Testing the new version of the database" msgstr "" -#: ../../content/administration/upgrade.rst:202 +#: ../../content/administration/upgrade.rst:200 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:207 +#: ../../content/administration/upgrade.rst:205 msgid "Test databases are neutralized, and some features are disabled to prevent them from impacting the production database:" msgstr "" -#: ../../content/administration/upgrade.rst:210 +#: ../../content/administration/upgrade.rst:208 msgid "Scheduled actions are disabled." msgstr "" -#: ../../content/administration/upgrade.rst:211 +#: ../../content/administration/upgrade.rst:209 msgid "Outgoing mail servers are disabled by archiving the existing ones and adding a fake one." msgstr "" -#: ../../content/administration/upgrade.rst:212 +#: ../../content/administration/upgrade.rst:210 msgid "Payment providers and delivery carriers are reset to the test environment." msgstr "" -#: ../../content/administration/upgrade.rst:213 +#: ../../content/administration/upgrade.rst:211 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:216 +#: ../../content/administration/upgrade.rst:214 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:219 +#: ../../content/administration/upgrade.rst:217 msgid "Basic test checklist" msgstr "" -#: ../../content/administration/upgrade.rst:221 +#: ../../content/administration/upgrade.rst:219 msgid "Are there views that are deactivated in your test database but active in your production database?" msgstr "" -#: ../../content/administration/upgrade.rst:223 +#: ../../content/administration/upgrade.rst:221 msgid "Are your usual views still displayed correctly?" msgstr "" -#: ../../content/administration/upgrade.rst:224 +#: ../../content/administration/upgrade.rst:222 msgid "Are your reports (invoice, sales order, etc.) correctly generated?" msgstr "" -#: ../../content/administration/upgrade.rst:225 +#: ../../content/administration/upgrade.rst:223 msgid "Are your website pages working correctly?" msgstr "" -#: ../../content/administration/upgrade.rst:226 +#: ../../content/administration/upgrade.rst:224 msgid "Are you able to create and modify records? (sales orders, invoices, purchases, users, contacts, companies, etc.)" msgstr "" -#: ../../content/administration/upgrade.rst:228 +#: ../../content/administration/upgrade.rst:226 msgid "Are there any issues with your mail templates?" msgstr "" -#: ../../content/administration/upgrade.rst:229 +#: ../../content/administration/upgrade.rst:227 msgid "Are there any issues with saved translations?" msgstr "" -#: ../../content/administration/upgrade.rst:230 +#: ../../content/administration/upgrade.rst:228 msgid "Are your search filters still present?" msgstr "" -#: ../../content/administration/upgrade.rst:231 +#: ../../content/administration/upgrade.rst:229 msgid "Can you export your data?" msgstr "" -#: ../../content/administration/upgrade.rst:235 +#: ../../content/administration/upgrade.rst:233 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:238 +#: ../../content/administration/upgrade.rst:236 msgid "Buying this product (Purchase app)." msgstr "" -#: ../../content/administration/upgrade.rst:239 +#: ../../content/administration/upgrade.rst:237 msgid "Confirming the reception of this product (Inventory app)." msgstr "" -#: ../../content/administration/upgrade.rst:240 +#: ../../content/administration/upgrade.rst:238 msgid "Checking if the route to receive this product is the same in your production database (Inventory app)." msgstr "" -#: ../../content/administration/upgrade.rst:242 +#: ../../content/administration/upgrade.rst:240 msgid "Selling this product (Sales app) to a random customer." msgstr "" -#: ../../content/administration/upgrade.rst:243 +#: ../../content/administration/upgrade.rst:241 msgid "Opening your customer database (Contacts app), selecting a customer (or company), and checking its data." msgstr "" -#: ../../content/administration/upgrade.rst:245 +#: ../../content/administration/upgrade.rst:243 msgid "Shipping this product (Inventory app)." msgstr "" -#: ../../content/administration/upgrade.rst:246 +#: ../../content/administration/upgrade.rst:244 msgid "Checking if the route to ship this product is the same as in your production database (Inventory app)." msgstr "" -#: ../../content/administration/upgrade.rst:248 +#: ../../content/administration/upgrade.rst:246 msgid "Validating a customer invoice (Invoicing or Accounting app)." msgstr "" -#: ../../content/administration/upgrade.rst:249 +#: ../../content/administration/upgrade.rst:247 msgid "Crediting the invoice (issuing a credit note) and checking if it behaves as in your production database." msgstr "" -#: ../../content/administration/upgrade.rst:251 +#: ../../content/administration/upgrade.rst:249 msgid "Checking your reports' results (Accounting app)." msgstr "" -#: ../../content/administration/upgrade.rst:252 +#: ../../content/administration/upgrade.rst:250 msgid "Randomly checking your taxes, currencies, bank accounts, and fiscal year (Accounting app)." msgstr "" -#: ../../content/administration/upgrade.rst:253 +#: ../../content/administration/upgrade.rst:251 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:256 +#: ../../content/administration/upgrade.rst:254 msgid "This list is **not** exhaustive. Extend the example to your other apps based on your use of Odoo." msgstr "" -#: ../../content/administration/upgrade.rst:258 +#: ../../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." msgstr "" -#: ../../content/administration/upgrade.rst:263 +#: ../../content/administration/upgrade.rst:261 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:269 +#: ../../content/administration/upgrade.rst:267 msgid "Do not forget to test:" msgstr "" -#: ../../content/administration/upgrade.rst:271 +#: ../../content/administration/upgrade.rst:269 msgid "Integrations with external software (EDI, APIs, etc.)" msgstr "" -#: ../../content/administration/upgrade.rst:272 +#: ../../content/administration/upgrade.rst:270 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:274 +#: ../../content/administration/upgrade.rst:272 msgid "Data exports" msgstr "" -#: ../../content/administration/upgrade.rst:275 +#: ../../content/administration/upgrade.rst:273 msgid "Automated actions" msgstr "" -#: ../../content/administration/upgrade.rst:276 +#: ../../content/administration/upgrade.rst:274 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:282 +#: ../../content/administration/upgrade.rst:280 msgid "Upgrading the production database" msgstr "" -#: ../../content/administration/upgrade.rst:284 +#: ../../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 `__." msgstr "" -#: ../../content/administration/upgrade.rst:289 +#: ../../content/administration/upgrade.rst:287 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:292 -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." +#: ../../content/administration/upgrade.rst:290 +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:298 +#: ../../content/administration/upgrade.rst:296 msgid "Going into production without first testing may lead to:" msgstr "" -#: ../../content/administration/upgrade.rst:300 +#: ../../content/administration/upgrade.rst:298 msgid "Users failing to adjust to the changes and new features" msgstr "" -#: ../../content/administration/upgrade.rst:301 +#: ../../content/administration/upgrade.rst:299 msgid "Business interruptions (e.g., no longer having the possibility to validate an action)" msgstr "" -#: ../../content/administration/upgrade.rst:302 +#: ../../content/administration/upgrade.rst:300 msgid "Poor customer experience (e.g., an eCommerce website that does not work correctly)" msgstr "" -#: ../../content/administration/upgrade.rst:304 +#: ../../content/administration/upgrade.rst:302 msgid "The process of upgrading a production database is similar to upgrading a test database with a few exceptions." msgstr "" -#: ../../content/administration/upgrade.rst:311 +#: ../../content/administration/upgrade.rst:309 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:316 +#: ../../content/administration/upgrade.rst:314 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:322 +#: ../../content/administration/upgrade.rst:320 msgid "The process is similar to :ref:`obtaining an upgraded test database ` on the :guilabel:`Production` branch." msgstr "" @@ -6395,98 +6479,98 @@ msgstr "" msgid "View from the upgrade tab" msgstr "" -#: ../../content/administration/upgrade.rst:328 +#: ../../content/administration/upgrade.rst:326 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:334 +#: ../../content/administration/upgrade.rst:332 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:338 -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." +#: ../../content/administration/upgrade.rst:336 +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:346 +#: ../../content/administration/upgrade.rst:343 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:353 +#: ../../content/administration/upgrade.rst:350 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:360 +#: ../../content/administration/upgrade.rst:357 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:364 +#: ../../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." msgstr "" -#: ../../content/administration/upgrade.rst:372 +#: ../../content/administration/upgrade.rst:369 msgid "Service-level agreement (SLA)" msgstr "" -#: ../../content/administration/upgrade.rst:374 +#: ../../content/administration/upgrade.rst:371 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:377 +#: ../../content/administration/upgrade.rst:374 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:382 +#: ../../content/administration/upgrade.rst:379 msgid "Upgrade services covered by the SLA" msgstr "" -#: ../../content/administration/upgrade.rst:384 +#: ../../content/administration/upgrade.rst:381 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:387 +#: ../../content/administration/upgrade.rst:384 msgid "the upgrade of all **standard applications**;" msgstr "" -#: ../../content/administration/upgrade.rst:388 +#: ../../content/administration/upgrade.rst:385 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:390 +#: ../../content/administration/upgrade.rst:387 msgid "the upgrade of all **developments and customizations covered by a maintenance of customizations subscription**." msgstr "" -#: ../../content/administration/upgrade.rst:393 +#: ../../content/administration/upgrade.rst:390 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:397 +#: ../../content/administration/upgrade.rst:394 msgid "Upgrade services not covered by the SLA" msgstr "" -#: ../../content/administration/upgrade.rst:399 +#: ../../content/administration/upgrade.rst:396 msgid "The following upgrade-related services are **not** included:" msgstr "" -#: ../../content/administration/upgrade.rst:401 +#: ../../content/administration/upgrade.rst:398 msgid "the **cleaning** of pre-existing data and configurations while upgrading;" msgstr "" -#: ../../content/administration/upgrade.rst:402 +#: ../../content/administration/upgrade.rst:399 msgid "the upgrade of **custom modules created in-house or by third parties**, including Odoo partners;" msgstr "" -#: ../../content/administration/upgrade.rst:403 +#: ../../content/administration/upgrade.rst:400 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:406 +#: ../../content/administration/upgrade.rst:403 msgid "**training** on using the upgraded version's features and workflows." msgstr "" -#: ../../content/administration/upgrade.rst:409 +#: ../../content/administration/upgrade.rst:406 msgid ":doc:`Odoo.sh documentation `" msgstr "" -#: ../../content/administration/upgrade.rst:410 +#: ../../content/administration/upgrade.rst:407 msgid ":doc:`Supported Odoo versions `" msgstr "" diff --git a/locale/sources/developer.pot b/locale/sources/developer.pot index 0c7270a82..bedb7fc23 100644 --- a/locale/sources/developer.pot +++ b/locale/sources/developer.pot @@ -8,7 +8,7 @@ msgid "" msgstr "" "Project-Id-Version: Odoo saas-16.1\n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2023-12-19 13:26+0000\n" +"POT-Creation-Date: 2024-01-19 10:30+0000\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME \n" "Language-Team: LANGUAGE \n" @@ -504,6 +504,7 @@ msgid "When the field `company_id` is made required on a model, a good practice msgstr "" #: ../../content/developer/howtos/company.rst:168 +#: ../../content/developer/howtos/upgrade_custom_db.rst:132 #: ../../content/developer/howtos/website_themes/setup.rst:75 #: ../../content/developer/howtos/website_themes/theming.rst:496 #: ../../content/developer/reference/backend/views.rst:6 @@ -1157,6 +1158,7 @@ msgstr "" #: ../../content/developer/howtos/scss_tips.rst:85 #: ../../content/developer/howtos/scss_tips.rst:86 +#: ../../content/developer/howtos/upgrade_custom_db.rst:114 #: ../../content/developer/howtos/website_themes/shapes.rst:139 msgid "..." msgstr "" @@ -1425,6 +1427,351 @@ msgstr "" msgid "**Do** in the case where the translation lookup is done when the JS file is *read*, use `_lt` instead of `_t` to translate the term when it is *used*::" msgstr "" +#: ../../content/developer/howtos/upgrade_custom_db.rst:3 +msgid "Upgrade a customized database" +msgstr "" + +#: ../../content/developer/howtos/upgrade_custom_db.rst:5 +msgid "Upgrading to a new version of Odoo can be challenging, especially if the database you work on contains custom modules. This page intent is to explain the technical process of upgrading a database with customized modules. Refer to :doc:`Upgrade documentation ` for guidance on how to upgrade a database without customized modules." +msgstr "" + +#: ../../content/developer/howtos/upgrade_custom_db.rst:10 +msgid "We consider a custom module, any module that extends the standard code of Odoo and that was not built with the Studio app. Before upgrading such a module, or before requesting its upgrade, have a look at the :ref:`upgrade/sla` to make sure who's responsible for it." +msgstr "" + +#: ../../content/developer/howtos/upgrade_custom_db.rst:14 +msgid "While working on what we refer to as the **custom upgrade** of your database, keep in mind the goals of an upgrade:" +msgstr "" + +#: ../../content/developer/howtos/upgrade_custom_db.rst:17 +msgid "Stay supported" +msgstr "" + +#: ../../content/developer/howtos/upgrade_custom_db.rst:18 +msgid "Get the latest features" +msgstr "" + +#: ../../content/developer/howtos/upgrade_custom_db.rst:19 +msgid "Enjoy the performance improvement" +msgstr "" + +#: ../../content/developer/howtos/upgrade_custom_db.rst:20 +msgid "Reduce the technical debt" +msgstr "" + +#: ../../content/developer/howtos/upgrade_custom_db.rst:21 +msgid "Benefit from security improvements" +msgstr "" + +#: ../../content/developer/howtos/upgrade_custom_db.rst:23 +msgid "With every new version of Odoo, changes are introduced. These changes can impact modules on which customization have been developed. This is the reason why upgrading a database that contains custom modules requires additional steps in order to upgrade the source code." +msgstr "" + +#: ../../content/developer/howtos/upgrade_custom_db.rst:27 +msgid "These are the steps to follow to upgrade customized databases:" +msgstr "" + +#: ../../content/developer/howtos/upgrade_custom_db.rst:29 +msgid ":ref:`Stop the devolopments and challenge them `." +msgstr "" + +#: ../../content/developer/howtos/upgrade_custom_db.rst:30 +msgid ":ref:`Request an upgraded database `." +msgstr "" + +#: ../../content/developer/howtos/upgrade_custom_db.rst:31 +msgid ":ref:`Make your module installable on an empty database `." +msgstr "" + +#: ../../content/developer/howtos/upgrade_custom_db.rst:32 +msgid ":ref:`Make your module installable on the upgraded database `." +msgstr "" + +#: ../../content/developer/howtos/upgrade_custom_db.rst:33 +msgid ":ref:`Test extensively and do a rehearsal `." +msgstr "" + +#: ../../content/developer/howtos/upgrade_custom_db.rst:34 +msgid ":ref:`Upgrade the production database `." +msgstr "" + +#: ../../content/developer/howtos/upgrade_custom_db.rst:40 +msgid "Step 1: Stop the developments" +msgstr "" + +#: ../../content/developer/howtos/upgrade_custom_db.rst:42 +msgid "Starting an upgrade requires commitment and development resources. If developments keep being made at the same time, those features will need to be re-upgraded and tested every time you change them. This is why we recommend a complete freeze of the codebase when starting the upgrade process. Needless to say, bug fixing is exempt from this recommendation." +msgstr "" + +#: ../../content/developer/howtos/upgrade_custom_db.rst:47 +msgid "Once you have stopped development, it is a good practice to assess the developments made and compare them with the features introduced between your current version and the version you are targeting. Challenge the developments as much as possible and find functional workarounds. Removing redundancy between your developments and the standard version of Odoo will lead to an eased upgrade process and reduce technical debt." +msgstr "" + +#: ../../content/developer/howtos/upgrade_custom_db.rst:54 +msgid "You can find information on the changes between versions in the `Release Notes `_." +msgstr "" + +#: ../../content/developer/howtos/upgrade_custom_db.rst:61 +msgid "Step 2: Request an upgraded database" +msgstr "" + +#: ../../content/developer/howtos/upgrade_custom_db.rst:63 +msgid "Once the developments have stopped for the custom modules and the implemented features have been challenged to remove redundancy and unnecessary code, the next step is to request an upgraded test database. To do so, follow the steps mentioned in :ref:`upgrade/request-test-database`, depending on the hosting type of your database." +msgstr "" + +#: ../../content/developer/howtos/upgrade_custom_db.rst:68 +msgid "The purpose of this stage is not to start working with the custom modules in the upgraded database, but to make sure the standard upgrade process works seamlessly, and the test database is delivered properly. If that's not the case, and the upgrade request fails, request the assistance of Odoo via the `support page `_ by selecting the option related to testing the upgrade." +msgstr "" + +#: ../../content/developer/howtos/upgrade_custom_db.rst:78 +msgid "Step 3: Empty database" +msgstr "" + +#: ../../content/developer/howtos/upgrade_custom_db.rst:80 +msgid "Before working on an upgraded test database, we recommend to make the custom developments work on an empty database in the targeted version of your upgrade. This ensures that the customization is compatible with the new version of Odoo, allows to analyze how it behaves and interacts with the new features, and guarantees that they will not cause any issues when upgrading the database." +msgstr "" + +#: ../../content/developer/howtos/upgrade_custom_db.rst:85 +msgid "Making the custom modules work in an empty database also helps avoid changes and wrong configurations that might be present in the production database (like studio customization, customized website pages, email templates or translations). They are not intrinsically related to the custom modules and that can raise unwanted issues in this stage of the upgraded process." +msgstr "" + +#: ../../content/developer/howtos/upgrade_custom_db.rst:90 +msgid "To make custom modules work on an empty database we advise to follow these steps:" +msgstr "" + +#: ../../content/developer/howtos/upgrade_custom_db.rst:92 +msgid ":ref:`upgrade_custom/empty_database/modules_installable`" +msgstr "" + +#: ../../content/developer/howtos/upgrade_custom_db.rst:93 +msgid ":ref:`upgrade_custom/empty_database/test_fixes`" +msgstr "" + +#: ../../content/developer/howtos/upgrade_custom_db.rst:94 +msgid ":ref:`upgrade_custom/empty_database/clean_code`" +msgstr "" + +#: ../../content/developer/howtos/upgrade_custom_db.rst:95 +msgid ":ref:`Make standard tests run successfully `" +msgstr "" + +#: ../../content/developer/howtos/upgrade_custom_db.rst:100 +msgid "Make custom modules installable" +msgstr "" + +#: ../../content/developer/howtos/upgrade_custom_db.rst:102 +msgid "The first step is to make the custom modules installable in the new Odoo version. This means, starting by ensuring there are no tracebacks or warnings during their installation. For this, install the custom modules, one by one, in an empty database of the new Odoo version and fix the tracebacks and warnings that arise from that." +msgstr "" + +#: ../../content/developer/howtos/upgrade_custom_db.rst:107 +msgid "This process will help detect issues during the installation of the modules. For example:" +msgstr "" + +#: ../../content/developer/howtos/upgrade_custom_db.rst:109 +msgid "Invalid module dependencies." +msgstr "" + +#: ../../content/developer/howtos/upgrade_custom_db.rst:110 +msgid "Syntax change: assets declaration, OWL updates, attrs." +msgstr "" + +#: ../../content/developer/howtos/upgrade_custom_db.rst:111 +msgid "References to standard fields, models, views not existing anymore or renamed." +msgstr "" + +#: ../../content/developer/howtos/upgrade_custom_db.rst:112 +msgid "Xpath that moved or were removed from views." +msgstr "" + +#: ../../content/developer/howtos/upgrade_custom_db.rst:113 +msgid "Methods renamed or removed." +msgstr "" + +#: ../../content/developer/howtos/upgrade_custom_db.rst:119 +msgid "Test and fixes" +msgstr "" + +#: ../../content/developer/howtos/upgrade_custom_db.rst:121 +msgid "Once there are no more tracebacks when installing the modules, the next step is to test them. Even if the custom modules are installable on an empty database, this does not guarantee there are no errors during their execution. Because of this, we encourage to test thoroughly all the customization to make sure everything is working as expected." +msgstr "" + +#: ../../content/developer/howtos/upgrade_custom_db.rst:126 +msgid "This process will help detect further issues that are not identified during the module installation and can only be detected in runtime. For example, deprecated calls to standard python or OWL functions, non-existing references to standard fields, etc." +msgstr "" + +#: ../../content/developer/howtos/upgrade_custom_db.rst:130 +msgid "We recommend to test all the customization, especially the following elements:" +msgstr "" + +#: ../../content/developer/howtos/upgrade_custom_db.rst:133 +msgid "Email templates" +msgstr "" + +#: ../../content/developer/howtos/upgrade_custom_db.rst:134 +msgid "Reports" +msgstr "" + +#: ../../content/developer/howtos/upgrade_custom_db.rst:135 +msgid "Server actions and automated actions" +msgstr "" + +#: ../../content/developer/howtos/upgrade_custom_db.rst:136 +msgid "Changes in the standard workflows" +msgstr "" + +#: ../../content/developer/howtos/upgrade_custom_db.rst:137 +#: ../../content/developer/tutorials/backend.rst:715 +msgid "Computed fields" +msgstr "" + +#: ../../content/developer/howtos/upgrade_custom_db.rst:139 +msgid "We also encourage to write automated tests to save time during the testing iterations, increase the test coverage, and ensure that the changes and fixes introduced do not break the existing flows. If there are tests already implemented in the customization, make sure they are upgraded to the new Odoo version and run successfully, fixing issues that might be present." +msgstr "" + +#: ../../content/developer/howtos/upgrade_custom_db.rst:147 +msgid "Clean the code" +msgstr "" + +#: ../../content/developer/howtos/upgrade_custom_db.rst:149 +msgid "At this stage of the upgrade process, we also suggest to clean the code as much as possible. This includes:" +msgstr "" + +#: ../../content/developer/howtos/upgrade_custom_db.rst:152 +msgid "Remove redundant and unnecessary code." +msgstr "" + +#: ../../content/developer/howtos/upgrade_custom_db.rst:153 +msgid "Remove features that are now part of Odoo standard, as described in :ref:`upgrade_custom/stop_developments`." +msgstr "" + +#: ../../content/developer/howtos/upgrade_custom_db.rst:155 +msgid "Clean commented code if it is not needed anymore." +msgstr "" + +#: ../../content/developer/howtos/upgrade_custom_db.rst:156 +msgid "Refactor the code (functions, fields, views, reports, etc.) if needed." +msgstr "" + +#: ../../content/developer/howtos/upgrade_custom_db.rst:161 +msgid "Standard tests" +msgstr "" + +#: ../../content/developer/howtos/upgrade_custom_db.rst:163 +msgid "Once the previous steps are completed, we advise to make sure all standard tests associated to the dependencies of the custom module pass. Standard tests ensure the validation of the code logic and prevent data corruption. They will help you identify bugs or unwanted behavior before you work on your database." +msgstr "" + +#: ../../content/developer/howtos/upgrade_custom_db.rst:168 +msgid "In case there are standard test failing, we suggest to analyze the reason for their failure:" +msgstr "" + +#: ../../content/developer/howtos/upgrade_custom_db.rst:170 +msgid "The customization changes the standard workflow: Adapt the standard test to your workflow." +msgstr "" + +#: ../../content/developer/howtos/upgrade_custom_db.rst:171 +msgid "The customization did not take into account a special flow: Adapt your customization to ensure it works for all the standard workflows." +msgstr "" + +#: ../../content/developer/howtos/upgrade_custom_db.rst:178 +msgid "Step 4: Upgraded database" +msgstr "" + +#: ../../content/developer/howtos/upgrade_custom_db.rst:180 +msgid "Once the custom modules are installable and working properly in an empty database, it is time to make them work on an :ref:`upgraded database `." +msgstr "" + +#: ../../content/developer/howtos/upgrade_custom_db.rst:183 +msgid "To make sure the custom code is working flawlessly in the new version, follow these steps:" +msgstr "" + +#: ../../content/developer/howtos/upgrade_custom_db.rst:185 +msgid ":ref:`upgrade_custom/upgraded_database/migrate_data`" +msgstr "" + +#: ../../content/developer/howtos/upgrade_custom_db.rst:186 +msgid ":ref:`upgrade_custom/upgraded_database/test_custom`" +msgstr "" + +#: ../../content/developer/howtos/upgrade_custom_db.rst:191 +msgid "Migrate the data" +msgstr "" + +#: ../../content/developer/howtos/upgrade_custom_db.rst:193 +msgid "During the upgrade of the custom modules, you might have to use migration scripts to reflect changes from the source code to their corresponding data." +msgstr "" + +#: ../../content/developer/howtos/upgrade_custom_db.rst:196 +msgid "Any technical data that was renamed during the upgrade of the custom code (models, fields, external identifiers) should be renamed using migration scripts to avoid data loss during the module upgrade." +msgstr "" + +#: ../../content/developer/howtos/upgrade_custom_db.rst:199 +msgid "Data from standard models removed from the source code of the newer Odoo version and from the database during the standard upgrade process might need to be recovered from the old model table if it is still present." +msgstr "" + +#: ../../content/developer/howtos/upgrade_custom_db.rst:203 +msgid "Migration scripts can also be used to:" +msgstr "" + +#: ../../content/developer/howtos/upgrade_custom_db.rst:205 +msgid "Ease the processing time of an upgrade. For example, to store the value of computed stored fields on models with an excessive number of records by using SQL queries." +msgstr "" + +#: ../../content/developer/howtos/upgrade_custom_db.rst:207 +msgid "Recompute fields in case the computation of their value has changed." +msgstr "" + +#: ../../content/developer/howtos/upgrade_custom_db.rst:208 +msgid "Uninstall unwanted custom modules." +msgstr "" + +#: ../../content/developer/howtos/upgrade_custom_db.rst:209 +msgid "Correct faulty data or wrong configurations." +msgstr "" + +#: ../../content/developer/howtos/upgrade_custom_db.rst:214 +msgid "Test the custom modules" +msgstr "" + +#: ../../content/developer/howtos/upgrade_custom_db.rst:216 +msgid "To make sure the custom modules work properly with your data in the upgraded database, they need to be tested as well. This helps ensure both the standard and the custom data stored in the database are consistent and that nothing was lost during the upgrade process." +msgstr "" + +#: ../../content/developer/howtos/upgrade_custom_db.rst:220 +msgid "Things to pay attention to:" +msgstr "" + +#: ../../content/developer/howtos/upgrade_custom_db.rst:222 +msgid "Views not working: During the upgrade, if a view causes issues because of its content, it gets disabled. You can find the information on disabled views on the :ref:`Upgrade report `. This view needs to be activated again. To achieve this, we recommend the use of migration scripts." +msgstr "" + +#: ../../content/developer/howtos/upgrade_custom_db.rst:226 +msgid ":doc:`Module data <../tutorials/define_module_data>` not updated: Custom records that have the ``noupdate`` flag are not updated when upgrading the module in the new database. For the custom data that needs to be updated due to changes in the new version, we recommend to use migration scripts to do so." +msgstr "" + +#: ../../content/developer/howtos/upgrade_custom_db.rst:235 +msgid "Step 5: Testing and rehearsal" +msgstr "" + +#: ../../content/developer/howtos/upgrade_custom_db.rst:237 +msgid "When the custom modules are working properly in the upgraded database, it is crucial to do another round of testing to assess the database usability and detect any issues that might have gone unnoticed in previous tests. For further information about testing the upgraded database, check :ref:`upgrade/test_your_db`." +msgstr "" + +#: ../../content/developer/howtos/upgrade_custom_db.rst:242 +msgid "As mentioned in :ref:`upgrade/upgrade-prod`, both standard upgrade scripts and your database are constantly evolving. Therefore it is highly recommended to frequently request new upgraded test databases and ensure that the upgrade process is still successful." +msgstr "" + +#: ../../content/developer/howtos/upgrade_custom_db.rst:246 +msgid "In addition to that, make a full rehearsal of the upgrade process the day before upgrading the production database to avoid undesired behavior during the upgrade and to detect any issue that might have occurred with the migrated data." +msgstr "" + +#: ../../content/developer/howtos/upgrade_custom_db.rst:254 +msgid "Step 6: Production upgrade" +msgstr "" + +#: ../../content/developer/howtos/upgrade_custom_db.rst:256 +msgid "Once you are confident about upgrading your production database, follow the process described on :ref:`upgrade/upgrade-prod`, depending on the hosting type of your database." +msgstr "" + #: ../../content/developer/howtos/web_services.rst:3 msgid "Web Services" msgstr "" @@ -3622,7 +3969,7 @@ msgid ":option:`--addons-path `" msgstr "" #: ../../content/developer/howtos/website_themes/setup.rst:213 -#: ../../content/developer/reference/cli.rst:807 +#: ../../content/developer/reference/cli.rst:829 msgid "Comma-separated list of directories in which modules are stored. These directories are scanned for modules." msgstr "" @@ -13838,435 +14185,447 @@ msgid "Logging" msgstr "" #: ../../content/developer/reference/cli.rst:472 -msgid "By default, Odoo displays all logging of level_ ``info`` except for workflow logging (``warning`` only), and log output is sent to ``stdout``. Various options are available to redirect logging to other destinations and to customize the amount of logging output." +msgid "By default, Odoo displays all logging of level_ ``INFO``, ``WARNING`` and ``ERROR``. All logs independently of the level are output on ``stderr``. Various options are available to redirect logging to other destinations and to customize the verbosity." msgstr "" -#: ../../content/developer/reference/cli.rst:479 -msgid "sends logging output to the specified file instead of stdout. On Unix, the file `can be managed by external log rotation programs `_ and will automatically be reopened when replaced" +#: ../../content/developer/reference/cli.rst:478 +msgid "sends logging output to the specified file instead of ``stderr``. On Unix, the file `can be managed by external log rotation programs `_ and will automatically be reopened when replaced" msgstr "" -#: ../../content/developer/reference/cli.rst:486 +#: ../../content/developer/reference/cli.rst:485 msgid "logs to the system's event logger: `syslog on unices `_ and `the Event Log on Windows `_." msgstr "" -#: ../../content/developer/reference/cli.rst:489 +#: ../../content/developer/reference/cli.rst:488 msgid "Neither is configurable" msgstr "" -#: ../../content/developer/reference/cli.rst:493 +#: ../../content/developer/reference/cli.rst:492 msgid "logs to the ``ir.logging`` model (``ir_logging`` table) of the specified database. The database can be the name of a database in the \"current\" PostgreSQL, or `a PostgreSQL URI`_ for e.g. log aggregation." msgstr "" -#: ../../content/developer/reference/cli.rst:499 +#: ../../content/developer/reference/cli.rst:498 msgid ":samp:`{LOGGER}:{LEVEL}`, enables ``LOGGER`` at the provided ``LEVEL`` e.g. ``odoo.models:DEBUG`` will enable all logging messages at or above ``DEBUG`` level in the models." msgstr "" -#: ../../content/developer/reference/cli.rst:503 +#: ../../content/developer/reference/cli.rst:502 msgid "The colon ``:`` is mandatory" msgstr "" -#: ../../content/developer/reference/cli.rst:504 +#: ../../content/developer/reference/cli.rst:503 msgid "The logger can be omitted to configure the root (default) handler" msgstr "" -#: ../../content/developer/reference/cli.rst:505 +#: ../../content/developer/reference/cli.rst:504 msgid "If the level is omitted, the logger is set to ``INFO``" msgstr "" -#: ../../content/developer/reference/cli.rst:507 +#: ../../content/developer/reference/cli.rst:506 msgid "The option can be repeated to configure multiple loggers e.g." msgstr "" -#: ../../content/developer/reference/cli.rst:515 +#: ../../content/developer/reference/cli.rst:514 msgid "enables DEBUG logging of HTTP requests and responses, equivalent to ``--log-handler=odoo.http:DEBUG``" msgstr "" -#: ../../content/developer/reference/cli.rst:520 +#: ../../content/developer/reference/cli.rst:519 msgid "enables DEBUG logging of SQL querying, equivalent to ``--log-handler=odoo.sql_db:DEBUG``" msgstr "" -#: ../../content/developer/reference/cli.rst:525 +#: ../../content/developer/reference/cli.rst:524 msgid "Shortcut to more easily set predefined levels on specific loggers. \"real\" levels (``critical``, ``error``, ``warn``, ``debug``) are set on the ``odoo`` and ``werkzeug`` loggers (except for ``debug`` which is only set on ``odoo``)." msgstr "" -#: ../../content/developer/reference/cli.rst:530 +#: ../../content/developer/reference/cli.rst:529 msgid "Odoo also provides debugging pseudo-levels which apply to different sets of loggers:" msgstr "" -#: ../../content/developer/reference/cli.rst:535 +#: ../../content/developer/reference/cli.rst:534 msgid "``debug_sql``" msgstr "" -#: ../../content/developer/reference/cli.rst:534 +#: ../../content/developer/reference/cli.rst:533 msgid "sets the SQL logger to ``debug``" msgstr "" -#: ../../content/developer/reference/cli.rst:536 +#: ../../content/developer/reference/cli.rst:535 msgid "equivalent to ``--log-sql``" msgstr "" -#: ../../content/developer/reference/cli.rst:539 +#: ../../content/developer/reference/cli.rst:538 msgid "``debug_rpc``" msgstr "" -#: ../../content/developer/reference/cli.rst:538 +#: ../../content/developer/reference/cli.rst:537 msgid "sets the ``odoo`` and HTTP request loggers to ``debug``" msgstr "" -#: ../../content/developer/reference/cli.rst:540 +#: ../../content/developer/reference/cli.rst:539 msgid "equivalent to ``--log-level debug --log-request``" msgstr "" -#: ../../content/developer/reference/cli.rst:545 +#: ../../content/developer/reference/cli.rst:544 msgid "``debug_rpc_answer``" msgstr "" -#: ../../content/developer/reference/cli.rst:542 +#: ../../content/developer/reference/cli.rst:541 msgid "sets the ``odoo`` and HTTP request and response loggers to ``debug``" msgstr "" -#: ../../content/developer/reference/cli.rst:545 +#: ../../content/developer/reference/cli.rst:544 msgid "equivalent to ``--log-level debug --log-request --log-response``" msgstr "" -#: ../../content/developer/reference/cli.rst:549 +#: ../../content/developer/reference/cli.rst:548 msgid "In case of conflict between :option:`--log-level` and :option:`--log-handler`, the latter is used" msgstr "" -#: ../../content/developer/reference/cli.rst:555 +#: ../../content/developer/reference/cli.rst:554 msgid "Multiprocessing" msgstr "" -#: ../../content/developer/reference/cli.rst:559 +#: ../../content/developer/reference/cli.rst:558 msgid "if ``count`` is not 0 (the default), enables multiprocessing and sets up the specified number of HTTP workers (sub-processes processing HTTP and RPC requests)." msgstr "" -#: ../../content/developer/reference/cli.rst:563 +#: ../../content/developer/reference/cli.rst:562 msgid "multiprocessing mode is only available on Unix-based systems" msgstr "" -#: ../../content/developer/reference/cli.rst:565 +#: ../../content/developer/reference/cli.rst:564 msgid "A number of options allow limiting and recycling workers:" msgstr "" -#: ../../content/developer/reference/cli.rst:569 +#: ../../content/developer/reference/cli.rst:568 msgid "Number of requests a worker will process before being recycled and restarted." msgstr "" -#: ../../content/developer/reference/cli.rst:572 +#: ../../content/developer/reference/cli.rst:571 msgid "Defaults to *8196*." msgstr "" -#: ../../content/developer/reference/cli.rst:576 +#: ../../content/developer/reference/cli.rst:575 msgid "Maximum allowed virtual memory per worker in bytes. If the limit is exceeded, the worker is killed and recycled at the end of the current request." msgstr "" -#: ../../content/developer/reference/cli.rst:579 +#: ../../content/developer/reference/cli.rst:578 msgid "Defaults to *2048MiB (2048\\*1024\\*1024B)*." msgstr "" -#: ../../content/developer/reference/cli.rst:583 +#: ../../content/developer/reference/cli.rst:582 msgid "Hard limit on virtual memory in bytes, any worker exceeding the limit will be immediately killed without waiting for the end of the current request processing." msgstr "" -#: ../../content/developer/reference/cli.rst:587 +#: ../../content/developer/reference/cli.rst:586 msgid "Defaults to *2560MiB (2560\\*1024\\*1024B)*." msgstr "" -#: ../../content/developer/reference/cli.rst:591 +#: ../../content/developer/reference/cli.rst:590 msgid "Prevents the worker from using more than CPU seconds for each request. If the limit is exceeded, the worker is killed." msgstr "" -#: ../../content/developer/reference/cli.rst:594 +#: ../../content/developer/reference/cli.rst:593 msgid "Defaults to *60*." msgstr "" -#: ../../content/developer/reference/cli.rst:598 +#: ../../content/developer/reference/cli.rst:597 msgid "Prevents the worker from taking longer than seconds to process a request. If the limit is exceeded, the worker is killed." msgstr "" -#: ../../content/developer/reference/cli.rst:601 +#: ../../content/developer/reference/cli.rst:600 msgid "Differs from :option:`--limit-time-cpu` in that this is a \"wall time\" limit including e.g. SQL queries." msgstr "" -#: ../../content/developer/reference/cli.rst:604 +#: ../../content/developer/reference/cli.rst:603 msgid "Defaults to *120*." msgstr "" -#: ../../content/developer/reference/cli.rst:608 +#: ../../content/developer/reference/cli.rst:607 msgid "number of workers dedicated to :ref:`cron ` jobs. Defaults to *2*. The workers are threads in multi-threading mode and processes in multi-processing mode." msgstr "" -#: ../../content/developer/reference/cli.rst:611 +#: ../../content/developer/reference/cli.rst:610 msgid "For multi-processing mode, this is in addition to the HTTP worker processes." msgstr "" -#: ../../content/developer/reference/cli.rst:616 +#: ../../content/developer/reference/cli.rst:615 msgid "Configuration file" msgstr "" -#: ../../content/developer/reference/cli.rst:620 +#: ../../content/developer/reference/cli.rst:619 msgid "Most of the command-line options can also be specified via a configuration file. Most of the time, they use similar names with the prefix ``-`` removed and other ``-`` are replaced by ``_`` e.g. :option:`--db-template` becomes ``db_template``." msgstr "" -#: ../../content/developer/reference/cli.rst:625 +#: ../../content/developer/reference/cli.rst:624 msgid "Some conversions don't match the pattern:" msgstr "" -#: ../../content/developer/reference/cli.rst:627 +#: ../../content/developer/reference/cli.rst:626 msgid ":option:`--db-filter` becomes ``dbfilter``" msgstr "" -#: ../../content/developer/reference/cli.rst:628 +#: ../../content/developer/reference/cli.rst:627 msgid ":option:`--no-http` corresponds to the ``http_enable`` boolean" msgstr "" -#: ../../content/developer/reference/cli.rst:629 +#: ../../content/developer/reference/cli.rst:628 msgid "logging presets (all options starting with ``--log-`` except for :option:`--log-handler` and :option:`--log-db`) just add content to ``log_handler``, use that directly in the configuration file" msgstr "" -#: ../../content/developer/reference/cli.rst:632 +#: ../../content/developer/reference/cli.rst:631 msgid ":option:`--smtp` is stored as ``smtp_server``" msgstr "" -#: ../../content/developer/reference/cli.rst:633 +#: ../../content/developer/reference/cli.rst:632 msgid ":option:`--database` is stored as ``db_name``" msgstr "" -#: ../../content/developer/reference/cli.rst:634 +#: ../../content/developer/reference/cli.rst:633 msgid ":option:`--i18n-import` and :option:`--i18n-export` aren't available at all from configuration files" msgstr "" -#: ../../content/developer/reference/cli.rst:639 +#: ../../content/developer/reference/cli.rst:638 msgid "The default configuration file is :file:`{$HOME}/.odoorc` which can be overridden using :option:`--config `. Specifying :option:`--save ` will save the current configuration state back to that file. The configuration items relative to the command-line are to be specified in the section ``[options]``." msgstr "" -#: ../../content/developer/reference/cli.rst:645 +#: ../../content/developer/reference/cli.rst:644 msgid "Here is a sample file:" msgstr "" -#: ../../content/developer/reference/cli.rst:670 +#: ../../content/developer/reference/cli.rst:669 msgid "Shell" msgstr "" -#: ../../content/developer/reference/cli.rst:672 -msgid "Odoo command-line also allows to launch odoo as a python console environment. This enables direct interaction with the :ref:`orm ` and its functionalities." +#: ../../content/developer/reference/cli.rst:671 +msgid "The Odoo command line also allows launching Odoo as a Python console environment, enabling direct interaction with the :ref:`orm ` and its functionalities." msgstr "" -#: ../../content/developer/reference/cli.rst:682 -msgid "Specify a preferred REPL to use in shell mode." +#: ../../content/developer/reference/cli.rst:680 +msgid "Adding an exclamation mark to all contacts' names:" msgstr "" -#: ../../content/developer/reference/cli.rst:688 -msgid "Scaffolding" +#: ../../content/developer/reference/cli.rst:696 +msgid "By default, the shell is running in transaction mode. This means that any change made to the database is rolled back when exiting the shell. To commit changes, use `env.cr.commit()`." msgstr "" -#: ../../content/developer/reference/cli.rst:692 -msgid "Scaffolding is the automated creation of a skeleton structure to simplify bootstrapping (of new modules, in the case of Odoo). While not necessary it avoids the tedium of setting up basic structures and looking up what all starting requirements are." -msgstr "" - -#: ../../content/developer/reference/cli.rst:697 -msgid "Scaffolding is available via the :command:`odoo-bin scaffold` subcommand." +#: ../../content/developer/reference/cli.rst:701 +msgid "Specify a preferred REPL to use in shell mode. This shell is started with the `env` variable already initialized to be able to access the ORM and other Odoo modules." msgstr "" #: ../../content/developer/reference/cli.rst:705 -msgid "the name of the module to create, may munged in various manners to generate programmatic names (e.g. module directory name, model names, …)" +msgid ":ref:`reference/orm/environment`" msgstr "" #: ../../content/developer/reference/cli.rst:710 -msgid "directory in which to create the new module, defaults to the current directory" +msgid "Scaffolding" msgstr "" -#: ../../content/developer/reference/cli.rst:715 -msgid "a template directory, files are passed through jinja2_ then copied to the ``destination`` directory" +#: ../../content/developer/reference/cli.rst:714 +msgid "Scaffolding is the automated creation of a skeleton structure to simplify bootstrapping (of new modules, in the case of Odoo). While not necessary it avoids the tedium of setting up basic structures and looking up what all starting requirements are." msgstr "" #: ../../content/developer/reference/cli.rst:719 +msgid "Scaffolding is available via the :command:`odoo-bin scaffold` subcommand." +msgstr "" + +#: ../../content/developer/reference/cli.rst:727 +msgid "the name of the module to create, may munged in various manners to generate programmatic names (e.g. module directory name, model names, …)" +msgstr "" + +#: ../../content/developer/reference/cli.rst:732 +msgid "directory in which to create the new module, defaults to the current directory" +msgstr "" + +#: ../../content/developer/reference/cli.rst:737 +msgid "a template directory, files are passed through jinja2_ then copied to the ``destination`` directory" +msgstr "" + +#: ../../content/developer/reference/cli.rst:741 msgid "This will create module *my_module* in directory */addons/*." msgstr "" -#: ../../content/developer/reference/cli.rst:724 +#: ../../content/developer/reference/cli.rst:746 msgid "Database Population" msgstr "" -#: ../../content/developer/reference/cli.rst:728 +#: ../../content/developer/reference/cli.rst:750 msgid "Odoo CLI supports database population features. If the feature is :ref:`implemented on a given model `, it allows automatic data generation of the model's records to test your modules in databases containing non-trivial amounts of records." msgstr "" -#: ../../content/developer/reference/cli.rst:739 +#: ../../content/developer/reference/cli.rst:761 msgid "list of models for which the database should be filled" msgstr "" -#: ../../content/developer/reference/cli.rst:743 +#: ../../content/developer/reference/cli.rst:765 msgid "population size, the actual records number depends on the model's `_populate_sizes` attribute. The generated records content is specified by the :meth:`~odoo.models._populate_factories` method of a given model (cf. the :file:`populate` folder of modules for further details)." msgstr "" -#: ../../content/developer/reference/cli.rst:748 +#: ../../content/developer/reference/cli.rst:770 msgid ":ref:`reference/performance/populate`" msgstr "" -#: ../../content/developer/reference/cli.rst:753 +#: ../../content/developer/reference/cli.rst:775 msgid "Cloc" msgstr "" -#: ../../content/developer/reference/cli.rst:757 +#: ../../content/developer/reference/cli.rst:779 msgid "Odoo Cloc is a tool to count the number of relevant lines written in Python, Javascript, CSS, SCSS, or XML. This can be used as a rough metric for pricing maintenance of extra modules." msgstr "" -#: ../../content/developer/reference/cli.rst:762 +#: ../../content/developer/reference/cli.rst:784 msgid "Command-line options" msgstr "" -#: ../../content/developer/reference/cli.rst:767 +#: ../../content/developer/reference/cli.rst:789 msgid "Process the code of all extra modules installed on the provided database, and of all server actions and computed fields manually created in the provided database." msgstr "" -#: ../../content/developer/reference/cli.rst:769 +#: ../../content/developer/reference/cli.rst:791 msgid "The :option:`--addons-path` option is required to specify the path(s) to the module folder(s)." msgstr "" -#: ../../content/developer/reference/cli.rst:772 +#: ../../content/developer/reference/cli.rst:794 msgid "If combined with :option:`--path`, the count will be that of the sum of both options' results (with possible overlaps). At least one of these two options is required to specify which code to process." msgstr "" -#: ../../content/developer/reference/cli.rst:779 +#: ../../content/developer/reference/cli.rst:801 msgid ":ref:`reference/cmdline/cloc/database-option`" msgstr "" -#: ../../content/developer/reference/cli.rst:784 +#: ../../content/developer/reference/cli.rst:806 msgid "Process the files in the provided path." msgstr "" -#: ../../content/developer/reference/cli.rst:787 +#: ../../content/developer/reference/cli.rst:809 msgid "If combined with :option:`--database`, the count will be that of the sum of both options' results (with possible overlaps). At least one of these two options is required to specify which code to process." msgstr "" -#: ../../content/developer/reference/cli.rst:794 +#: ../../content/developer/reference/cli.rst:816 msgid "Multiple paths can be provided by repeating the option." msgstr "" -#: ../../content/developer/reference/cli.rst:801 +#: ../../content/developer/reference/cli.rst:823 msgid ":ref:`reference/cmdline/cloc/path-option`" msgstr "" -#: ../../content/developer/reference/cli.rst:808 +#: ../../content/developer/reference/cli.rst:830 msgid "Required if the :option:`--database` option is used." msgstr "" -#: ../../content/developer/reference/cli.rst:813 +#: ../../content/developer/reference/cli.rst:835 msgid "Specify a configuration file to use in place of the :option:`--addons-path` option." msgstr "" -#: ../../content/developer/reference/cli.rst:822 +#: ../../content/developer/reference/cli.rst:844 msgid "Show the details of lines counted for each file." msgstr "" -#: ../../content/developer/reference/cli.rst:826 +#: ../../content/developer/reference/cli.rst:848 msgid "Processed files" msgstr "" -#: ../../content/developer/reference/cli.rst:831 +#: ../../content/developer/reference/cli.rst:853 msgid "With the :option:`--database` option" msgstr "" -#: ../../content/developer/reference/cli.rst:833 +#: ../../content/developer/reference/cli.rst:855 msgid "Odoo Cloc counts the lines in each file of extra installed modules in a given database. In addition, it counts the Python lines of server actions and custom computed fields that have been directly created in the database or imported. Finally, it counts the lines of code of Javascript, CSS, and SCSS files, and of QWeb views from imported modules." msgstr "" -#: ../../content/developer/reference/cli.rst:839 +#: ../../content/developer/reference/cli.rst:861 msgid "Some files are excluded from the count by default:" msgstr "" -#: ../../content/developer/reference/cli.rst:841 +#: ../../content/developer/reference/cli.rst:863 msgid "The manifest (:file:`__manifest__.py` or :file:`__openerp__.py`)" msgstr "" -#: ../../content/developer/reference/cli.rst:842 +#: ../../content/developer/reference/cli.rst:864 msgid "The contents of the folder :file:`static/lib`" msgstr "" -#: ../../content/developer/reference/cli.rst:843 +#: ../../content/developer/reference/cli.rst:865 msgid "The tests defined in the folder :file:`tests` and :file:`static/tests`" msgstr "" -#: ../../content/developer/reference/cli.rst:844 +#: ../../content/developer/reference/cli.rst:866 msgid "The migrations scripts defined in the folder :file:`migrations` and `upgrades`" msgstr "" -#: ../../content/developer/reference/cli.rst:845 +#: ../../content/developer/reference/cli.rst:867 msgid "The XML files declared in the ``demo`` or ``demo_xml`` sections of the manifest" msgstr "" -#: ../../content/developer/reference/cli.rst:847 +#: ../../content/developer/reference/cli.rst:869 msgid "For special cases, a list of files that should be ignored by Odoo Cloc can be defined per module. This is specified by the ``cloc_exclude`` entry of the manifest:" msgstr "" -#: ../../content/developer/reference/cli.rst:860 +#: ../../content/developer/reference/cli.rst:882 msgid "The pattern ``**/*`` can be used to ignore an entire module. This can be useful to exclude a module from maintenance service costs." msgstr "" -#: ../../content/developer/reference/cli.rst:862 +#: ../../content/developer/reference/cli.rst:884 msgid "For more information about the pattern syntax, see `glob `_." msgstr "" -#: ../../content/developer/reference/cli.rst:867 +#: ../../content/developer/reference/cli.rst:889 msgid "With the :option:`--path` option" msgstr "" -#: ../../content/developer/reference/cli.rst:869 +#: ../../content/developer/reference/cli.rst:891 msgid "This method works the same as with the :ref:`--database option ` if a manifest file is present in the given folder. Otherwise, it counts all files." msgstr "" -#: ../../content/developer/reference/cli.rst:875 +#: ../../content/developer/reference/cli.rst:897 msgid "Identifying Extra Modules" msgstr "" -#: ../../content/developer/reference/cli.rst:877 +#: ../../content/developer/reference/cli.rst:899 msgid "To distinguish between standard and extra modules, Odoo Cloc uses the following heuristic: modules that are located (real file system path, after following symbolic links) in the same parent directory as the ``base``, ``web`` or ``web_enterprise`` standard modules are considered standard. Other modules are treated as extra modules." msgstr "" -#: ../../content/developer/reference/cli.rst:884 +#: ../../content/developer/reference/cli.rst:906 #: ../../content/developer/reference/frontend/services.rst:662 msgid "Error Handling" msgstr "" -#: ../../content/developer/reference/cli.rst:886 +#: ../../content/developer/reference/cli.rst:908 msgid "Some file cannot be counted by Odoo Cloc. Those file are reported at the end of the output." msgstr "" -#: ../../content/developer/reference/cli.rst:890 +#: ../../content/developer/reference/cli.rst:912 msgid "Max file size exceeded" msgstr "" -#: ../../content/developer/reference/cli.rst:892 +#: ../../content/developer/reference/cli.rst:914 msgid "Odoo Cloc rejects any file larger than 25MB. Usually, source files are smaller than 1 MB. If a file is rejected, it may be:" msgstr "" -#: ../../content/developer/reference/cli.rst:895 +#: ../../content/developer/reference/cli.rst:917 msgid "A generated XML file that contains lots of data. It should be excluded in the manifest." msgstr "" -#: ../../content/developer/reference/cli.rst:896 +#: ../../content/developer/reference/cli.rst:918 msgid "A JavaScript library that should be placed in the :file:`static/lib` folder." msgstr "" -#: ../../content/developer/reference/cli.rst:899 +#: ../../content/developer/reference/cli.rst:921 msgid "Syntax Error" msgstr "" -#: ../../content/developer/reference/cli.rst:901 +#: ../../content/developer/reference/cli.rst:923 msgid "Odoo Cloc cannot count the lines of code of a Python file with a syntax problem. If an extra module contains such files, they should be fixed to allow the module to load. If the module works despite the presence of those files, they are probably not loaded and should therefore be removed from the module, or at least excluded in the manifest via ``cloc_exclude``." msgstr "" -#: ../../content/developer/reference/cli.rst:908 +#: ../../content/developer/reference/cli.rst:930 msgid "TSConfig Generator" msgstr "" -#: ../../content/developer/reference/cli.rst:912 +#: ../../content/developer/reference/cli.rst:934 msgid "When working on javascript, there are ways to help your editor providing you with powerful auto-completion. One of those ways is the use of a tsconfig.json file. Originally meant for typescript, editors can use its information with plain javascript also. With this config file, you will now have full auto-completion across modules." msgstr "" -#: ../../content/developer/reference/cli.rst:917 +#: ../../content/developer/reference/cli.rst:939 msgid "The command to generate this files takes as many unnamed arguments as you need. Those are relative paths to your addon directories. In the example below, we move up one folder to save the tsconfig file in the folder containing community and enterprise." msgstr "" @@ -23930,10 +24289,6 @@ msgstr "" msgid "The value of a computed field usually depends on the values of other fields on the computed record. The ORM expects the developer to specify those dependencies on the compute method with the decorator :func:`~odoo.api.depends`. The given dependencies are used by the ORM to trigger the recomputation of the field whenever some of its dependencies have been modified::" msgstr "" -#: ../../content/developer/tutorials/backend.rst:715 -msgid "Computed fields" -msgstr "" - #: ../../content/developer/tutorials/backend.rst:717 msgid "Add the percentage of taken seats to the *Session* model" msgstr "" diff --git a/locale/sources/finance.pot b/locale/sources/finance.pot index 0f7096453..e616f84ce 100644 --- a/locale/sources/finance.pot +++ b/locale/sources/finance.pot @@ -8,7 +8,7 @@ msgid "" msgstr "" "Project-Id-Version: Odoo saas-16.1\n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2023-12-19 13:26+0000\n" +"POT-Creation-Date: 2024-01-19 10:30+0000\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME \n" "Language-Team: LANGUAGE \n" @@ -119,7 +119,7 @@ msgid "The following financial :doc:`reports ` are availab msgstr "" #: ../../content/applications/finance/accounting.rst:127 -#: ../../content/applications/finance/fiscal_localizations/chile.rst:951 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:947 #: ../../content/applications/finance/fiscal_localizations/colombia.rst:418 msgid "Financial reports" msgstr "" @@ -719,7 +719,7 @@ msgid "If your connection with the proxy is disconnected, you can reconnect with msgstr "" #: ../../content/applications/finance/accounting/bank/bank_synchronization.rst:109 -msgid "This disconnection can be caused by the Odoo support. In this case, please contact the `support `_ directly with your client id or the reference of the error listed in the chatter." +msgid "If you are unable to reconnect using the :guilabel:`Fetch Account` button, please contact the `support `_ directly with your client id or the reference of the error listed in the chatter." msgstr "" #: ../../content/applications/finance/accounting/bank/bank_synchronization.rst:116 @@ -1939,8 +1939,8 @@ msgstr "" #: ../../content/applications/finance/fiscal_localizations/argentina.rst:167 #: ../../content/applications/finance/fiscal_localizations/belgium.rst:71 #: ../../content/applications/finance/fiscal_localizations/brazil.rst:168 -#: ../../content/applications/finance/fiscal_localizations/chile.rst:368 -#: ../../content/applications/finance/fiscal_localizations/chile.rst:378 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:364 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:374 #: ../../content/applications/finance/fiscal_localizations/colombia.rst:192 #: ../../content/applications/finance/fiscal_localizations/mexico.rst:186 #: ../../content/applications/finance/fiscal_localizations/peru.rst:73 @@ -4673,7 +4673,7 @@ msgstr "" #: ../../content/applications/finance/accounting/get_started/multi_currency.rst:87 #: ../../content/applications/finance/fiscal_localizations/belgium.rst:56 #: ../../content/applications/finance/fiscal_localizations/brazil.rst:154 -#: ../../content/applications/finance/fiscal_localizations/chile.rst:363 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:359 #: ../../content/applications/finance/fiscal_localizations/colombia.rst:247 #: ../../content/applications/finance/fiscal_localizations/ecuador.rst:241 #: ../../content/applications/finance/fiscal_localizations/mexico.rst:1011 @@ -4756,9 +4756,9 @@ msgid "Account Types" msgstr "" #: ../../content/applications/finance/accounting/get_started/chart_of_accounts.rst:56 -#: ../../content/applications/finance/accounting/reporting.rst:36 +#: ../../content/applications/finance/accounting/reporting.rst:38 #: ../../content/applications/finance/fiscal_localizations/germany.rst:23 -#: ../../content/applications/finance/fiscal_localizations/spain.rst:27 +#: ../../content/applications/finance/fiscal_localizations/spain.rst:29 msgid "Balance Sheet" msgstr "" @@ -5222,7 +5222,6 @@ msgid "Total to pay" msgstr "" #: ../../content/applications/finance/accounting/get_started/cheat_sheet.rst:190 -#: ../../content/applications/finance/accounting/reporting.rst:149 msgid "Bank Reconciliation" msgstr "" @@ -5379,7 +5378,7 @@ msgstr "" #: ../../content/applications/finance/accounting/get_started/multi_currency.rst:99 #: ../../content/applications/finance/fiscal_localizations/argentina.rst:252 -#: ../../content/applications/finance/fiscal_localizations/chile.rst:280 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:276 #: ../../content/applications/finance/fiscal_localizations/france.rst:194 #: ../../content/applications/finance/fiscal_localizations/india.rst:101 #: ../../content/applications/finance/fiscal_localizations/peru.rst:299 @@ -5532,15 +5531,15 @@ msgid "Payments" msgstr "" #: ../../content/applications/finance/accounting/payments.rst:7 -msgid "In Odoo, payments can either be linked automatically to an invoice or bill or be stand-alone records for use at a later date." +msgid "In Odoo, payments can either be automatically linked to an invoice or bill or be stand-alone records for use at a later date:" msgstr "" #: ../../content/applications/finance/accounting/payments.rst:10 -msgid "If a payment is **linked to an invoice or bill**, it reduces the amount due of the invoice. You can have multiple payments related to the same invoice." +msgid "If a payment is **linked to an invoice or bill**, it reduces/settles the amount due of the invoice. You can have multiple payments related to the same invoice." msgstr "" #: ../../content/applications/finance/accounting/payments.rst:13 -msgid "If a payment is **not linked to an invoice or bill**, the customer has an outstanding credit with your company, or your company has an outstanding debit with a vendor. You can use those outstanding amounts to reduce unpaid invoices/bills." +msgid "If a payment is **not linked to an invoice or bill**, the customer has an outstanding credit with your company, or your company has an outstanding debit with a vendor. You can use those outstanding amounts to reduce/settle unpaid invoices/bills." msgstr "" #: ../../content/applications/finance/accounting/payments.rst:18 @@ -5548,9 +5547,6 @@ msgid ":doc:`Internal transfers `" msgstr "" #: ../../content/applications/finance/accounting/payments.rst:19 -#: ../../content/applications/finance/accounting/payments.rst:54 -#: ../../content/applications/finance/accounting/payments.rst:78 -#: ../../content/applications/finance/accounting/payments.rst:131 msgid ":doc:`bank/reconciliation`" msgstr "" @@ -5563,111 +5559,123 @@ msgid "Registering payment from an invoice or bill" msgstr "" #: ../../content/applications/finance/accounting/payments.rst:26 -msgid "When clicking on :guilabel:`Register payment` in a customer invoice or vendor bill, it generates a new journal entry and changes the amount due according to the amount of the payment. The counterpart is reflected in an outstanding receipts or payments account. At this point, the customer invoice or vendor bill is marked as :guilabel:`In payment`. Then, when the outstanding account is reconciled with a bank statement line, the invoice or vendor bill changes to the :guilabel:`Paid` status." +msgid "When clicking :guilabel:`Register payment` in a customer invoice or vendor bill, it generates a new journal entry and changes the amount due according to the payment amount. The counterpart is reflected in an :ref:`outstanding ` **receipts** or **payments** account. At this point, the customer invoice or vendor bill is marked as :guilabel:`In payment`. Then, when the outstanding account is reconciled with a bank statement line, the invoice or vendor bill changes to the :guilabel:`Paid` status." msgstr "" -#: ../../content/applications/finance/accounting/payments.rst:32 -msgid "The information icon near the payment line displays more information about the payment. You can access additional information, such as the related journal, by clicking on :guilabel:`View`." +#: ../../content/applications/finance/accounting/payments.rst:33 +msgid "The information icon near the payment line displays more information about the payment. You can access additional information, such as the related journal, by clicking :guilabel:`View`." msgstr "" #: ../../content/applications/finance/accounting/payments.rst:-1 -msgid "See detailed information of a payment" +msgid "See detailed information of a payment." msgstr "" -#: ../../content/applications/finance/accounting/payments.rst:39 -msgid "The customer invoice or vendor bill should be in the status :guilabel:`Posted` to register the payment." +#: ../../content/applications/finance/accounting/payments.rst:40 +msgid "The customer invoice or vendor bill must be in the :guilabel:`Posted` status to register the payment." msgstr "" -#: ../../content/applications/finance/accounting/payments.rst:41 -msgid "When clicking on :guilabel:`Register payment`, you can select the amount to pay and make a partial or full payment." +#: ../../content/applications/finance/accounting/payments.rst:42 +msgid "If you unreconcile a payment, it still appears in your books but is no longer linked to the invoice." msgstr "" -#: ../../content/applications/finance/accounting/payments.rst:43 -msgid "If your main bank account is set as :ref:`outstanding account `, and the payment is made in Odoo (not related to a bank statement), invoices and bills are directly registered in the status :guilabel:`Paid`." -msgstr "" - -#: ../../content/applications/finance/accounting/payments.rst:46 -msgid "If you unreconciled a payment, it still appears in your books but is no longer linked to the invoice." -msgstr "" - -#: ../../content/applications/finance/accounting/payments.rst:48 +#: ../../content/applications/finance/accounting/payments.rst:44 msgid "If you (un)reconcile a payment in a different currency, a journal entry is automatically created to post the currency exchange gains/losses (reversal) amount." msgstr "" -#: ../../content/applications/finance/accounting/payments.rst:50 +#: ../../content/applications/finance/accounting/payments.rst:46 msgid "If you (un)reconcile a payment and an invoice having cash basis taxes, a journal entry is automatically created to post the cash basis tax (reversal) amount." msgstr "" -#: ../../content/applications/finance/accounting/payments.rst:57 +#: ../../content/applications/finance/accounting/payments.rst:50 +msgid "If your main bank account is set as an :ref:`outstanding account `, and the payment is registered in Odoo (not through a related bank statement), invoices and bills are directly registered as :guilabel:`Paid`." +msgstr "" + +#: ../../content/applications/finance/accounting/payments.rst:55 msgid "Registering payments not tied to an invoice or bill" msgstr "" -#: ../../content/applications/finance/accounting/payments.rst:59 -msgid "When a new payment is registered via the menu :menuselection:`Customers / Vendors --> Payments`, it is not directly linked to an invoice or bill. Instead, the account receivable or the account payable are matched with the outstanding account until they are manually matched with their related invoice or bill." +#: ../../content/applications/finance/accounting/payments.rst:57 +msgid "When a new payment is registered via :menuselection:`Customers / Vendors --> Payments` menu, it is not directly linked to an invoice or bill. Instead, the account receivable or the account payable is matched with the **outstanding account** until it is manually matched with its related invoice or bill." msgstr "" -#: ../../content/applications/finance/accounting/payments.rst:65 +#: ../../content/applications/finance/accounting/payments.rst:63 msgid "Matching invoices and bills with payments" msgstr "" -#: ../../content/applications/finance/accounting/payments.rst:67 -msgid "A blue banner appears when you validate a new invoice or bill and there is an outstanding payment for this specific customer or vendor. It can easily be matched from the invoice or the bill by clicking on :guilabel:`ADD` under :guilabel:`Outstanding Credits` or :guilabel:`Outstanding Debits`." +#: ../../content/applications/finance/accounting/payments.rst:65 +msgid "A blue banner appears when you validate a new invoice/bill and an **outstanding payment** exists for this specific customer or vendor. It can easily be matched from the invoice or bill by clicking :guilabel:`ADD` under :guilabel:`Outstanding Credits` or :guilabel:`Outstanding Debits`." msgstr "" #: ../../content/applications/finance/accounting/payments.rst:-1 -msgid "Shows the ADD option to reconcile an invoice or a bill with a payment" +msgid "Shows the ADD option to reconcile an invoice or a bill with a payment." msgstr "" -#: ../../content/applications/finance/accounting/payments.rst:74 -msgid "The invoice or bill is now marked as :guilabel:`In payment` until it is reconciled with the bank statement." +#: ../../content/applications/finance/accounting/payments.rst:72 +msgid "The invoice or bill is now marked as :guilabel:`In payment` until it is reconciled with its corresponding bank statement." msgstr "" -#: ../../content/applications/finance/accounting/payments.rst:83 +#: ../../content/applications/finance/accounting/payments.rst:78 msgid "Batch payment" msgstr "" -#: ../../content/applications/finance/accounting/payments.rst:85 -msgid "Batch payments allow you to group different payments to ease :doc:`reconciliation `. They are also useful when you deposit checks to the bank or for SEPA Payments. To do so, go to :menuselection:`Accounting --> Customers --> Batch Payments` or :menuselection:`Accounting --> Vendors --> Batch Payments`. In the list view of payments, you can select several payments and group them in a batch by clicking on :menuselection:`Action --> Create Batch Payment`." +#: ../../content/applications/finance/accounting/payments.rst:80 +msgid "Batch payments allow you to group different payments to ease :doc:`reconciliation `. They are also useful when you deposit :doc:`checks ` to the bank or for :doc:`SEPA payments `. To do so, go to :menuselection:`Accounting --> Customers --> Batch Payments` or :menuselection:`Accounting --> Vendors --> Batch Payments`. In the list view of payments, you can select and group several payments in a batch by clicking :menuselection:`Action --> Create Batch Payment`." msgstr "" -#: ../../content/applications/finance/accounting/payments.rst:93 +#: ../../content/applications/finance/accounting/payments.rst:88 msgid ":doc:`payments/batch`" msgstr "" -#: ../../content/applications/finance/accounting/payments.rst:94 +#: ../../content/applications/finance/accounting/payments.rst:89 msgid ":doc:`payments/batch_sdd`" msgstr "" -#: ../../content/applications/finance/accounting/payments.rst:99 +#: ../../content/applications/finance/accounting/payments.rst:94 msgid "Payments matching" msgstr "" -#: ../../content/applications/finance/accounting/payments.rst:101 -msgid "The :guilabel:`Payments matching` tool opens all unreconciled customer invoices or vendor bills and gives you the opportunity to process them all one by one, doing the matching of all their payments and invoices at once. You can reach this tool from the :menuselection:`Accounting Dashboard --> Customer Invoices / Vendor Bills`, and click on :guilabel:`⋮` and select :guilabel:`Payments Matching`, or by going to :menuselection:`Accounting --> Reconciliation`." -msgstr "" - -#: ../../content/applications/finance/accounting/payments.rst:108 -msgid "During the :doc:`reconciliation `, if the sum of the debits and credits does not match, there is a remaining balance. This either needs to be reconciled at a later date or needs to be written off directly." -msgstr "" - -#: ../../content/applications/finance/accounting/payments.rst:113 -msgid "Batch payments matching" -msgstr "" - -#: ../../content/applications/finance/accounting/payments.rst:115 -msgid "To reconcile several outstanding payments or invoices at once, for a specific customer or vendor, the batch reconciliation feature can be used. Go to :menuselection:`Accounting --> Reporting --> Aged Receivable / Aged Payable`. You now see all transactions that have not been reconciled yet, and when you select a customer or vendor, the :guilabel:`Reconcile` option is displayed." +#: ../../content/applications/finance/accounting/payments.rst:96 +msgid "The :guilabel:`Payments matching` tool opens all unreconciled customer invoices or vendor bills and allows you to process them individually, matching all payments and invoices in one place. You can reach this tool from the :menuselection:`Accounting Dashboard --> Customer Invoices / Vendor Bills`, click the drop-down menu button (:guilabel:`⋮`), and select :guilabel:`Payments Matching`, or go to :menuselection:`Accounting --> Accounting --> Reconciliation`." msgstr "" #: ../../content/applications/finance/accounting/payments.rst:-1 -msgid "See the reconcile option" +msgid "Payments matching menu in the drop-down menu." msgstr "" -#: ../../content/applications/finance/accounting/payments.rst:124 +#: ../../content/applications/finance/accounting/payments.rst:106 +msgid "During the :doc:`reconciliation `, if the sum of the debits and credits does not match, there is a remaining balance. This either needs to be reconciled at a later date or needs to be written off directly." +msgstr "" + +#: ../../content/applications/finance/accounting/payments.rst:111 +msgid "Batch payments matching" +msgstr "" + +#: ../../content/applications/finance/accounting/payments.rst:113 +msgid "You can use the batch reconciliation feature to reconcile several outstanding payments or invoices simultaneously for a specific customer or vendor. Go to :menuselection:`Accounting --> Reporting --> Aged Receivable / Aged Payable`. You can see all transactions that have not been reconciled yet for that partner, and when you select a customer or vendor, the :guilabel:`Reconcile` option is displayed." +msgstr "" + +#: ../../content/applications/finance/accounting/payments.rst:-1 +msgid "See the reconcile option." +msgstr "" + +#: ../../content/applications/finance/accounting/payments.rst:123 +msgid "Registering a partial payment" +msgstr "" + +#: ../../content/applications/finance/accounting/payments.rst:125 +msgid "To register a **partial payment**, click :guilabel:`Register payment` from the related invoice or bill, and enter the amount received or paid. Upon entering the amount, a prompt appears to decide whether to :guilabel:`Keep open` the invoice or bill, or :guilabel:`Mark as fully paid`. Select :guilabel:`Keep open` and click :guilabel:`Create payment`. The invoice or bill is now marked as :guilabel:`Partial`. Select :guilabel:`Mark as fully paid` if you wish to settle the invoice or bill with a difference in the amount." +msgstr "" + +#: ../../content/applications/finance/accounting/payments.rst:-1 +msgid "Partial payment of an invoice or bill." +msgstr "" + +#: ../../content/applications/finance/accounting/payments.rst:136 msgid "Reconciling payments with bank statements" msgstr "" -#: ../../content/applications/finance/accounting/payments.rst:126 -msgid "Once a payment has been registered, the status of the invoice or bill is :guilabel:`In payment`. The next step is to reconcile it with the related bank statement line to have the transaction finalized and the invoice or bill marked as :guilabel:`Paid`." +#: ../../content/applications/finance/accounting/payments.rst:138 +msgid "Once a payment has been registered, the status of the invoice or bill is :guilabel:`In payment`. The next step is :doc:`reconciling ` it with the related bank statement line to have the transaction finalized and the invoice or bill marked as :guilabel:`Paid`." msgstr "" #: ../../content/applications/finance/accounting/payments/batch.rst:3 @@ -6360,67 +6368,6 @@ msgstr "" msgid "Bank Account (BANK B)" msgstr "" -#: ../../content/applications/finance/accounting/payments/multiple.rst:3 -msgid "Pay several bills at once" -msgstr "" - -#: ../../content/applications/finance/accounting/payments/multiple.rst:5 -msgid "Odoo offers the possibility of grouping multiple bills' payments into one, facilitating the reconciliation process." -msgstr "" - -#: ../../content/applications/finance/accounting/payments/multiple.rst:9 -#: ../../content/applications/finance/accounting/vendor_bills.rst:13 -msgid ":doc:`/applications/inventory_and_mrp/purchase/manage_deals/manage`" -msgstr "" - -#: ../../content/applications/finance/accounting/payments/multiple.rst:10 -msgid ":doc:`/applications/finance/accounting/bank/reconciliation`" -msgstr "" - -#: ../../content/applications/finance/accounting/payments/multiple.rst:13 -msgid "Group payments" -msgstr "" - -#: ../../content/applications/finance/accounting/payments/multiple.rst:15 -msgid "To register the payment of multiple bills at once, go to :menuselection:`Accounting app --> Vendors --> Bills`. Then, select the bills you wish to register a payment for by **ticking** the boxes next to the bills. When done, either click :guilabel:`Register Payment` or :menuselection:`Action --> Register Payment`." -msgstr "" - -#: ../../content/applications/finance/accounting/payments/multiple.rst:-1 -msgid "Register payment button." -msgstr "" - -#: ../../content/applications/finance/accounting/payments/multiple.rst:25 -msgid "Payments can only be registered for :guilabel:`posted` bills." -msgstr "" - -#: ../../content/applications/finance/accounting/payments/multiple.rst:27 -msgid "When registering the payments, a **pop-up window** appears. From here, you can either create **separate payments** for each bill all at once by clicking :guilabel:`Create Payment`, *or* create one payment by combining **all** bills' payments. To **combine** all payments, tick the :guilabel:`Group Payments` box." -msgstr "" - -#: ../../content/applications/finance/accounting/payments/multiple.rst:33 -msgid "The :guilabel:`Group Payments` option only appears when selecting two or more bills." -msgstr "" - -#: ../../content/applications/finance/accounting/payments/multiple.rst:-1 -msgid "Group payments options when registering a payment." -msgstr "" - -#: ../../content/applications/finance/accounting/payments/multiple.rst:39 -msgid "When selecting :guilabel:`Group Payments`, the :guilabel:`amount, currency, date and memo` are all set automatically, but you can modify them according to your needs." -msgstr "" - -#: ../../content/applications/finance/accounting/payments/multiple.rst:43 -msgid "Partial group payments with cash discounts" -msgstr "" - -#: ../../content/applications/finance/accounting/payments/multiple.rst:45 -msgid "In case of **partial group payments with cash discounts**, you can follow the steps found on the :doc:`cash discount documentation page `. Make sure to apply the :doc:`payment terms ` to the **bills** *instead* of the invoices." -msgstr "" - -#: ../../content/applications/finance/accounting/payments/multiple.rst:53 -msgid ":doc:`/applications/finance/accounting/customer_invoices/payment_terms`" -msgstr "" - #: ../../content/applications/finance/accounting/payments/online.rst:5 msgid "Online payments" msgstr "" @@ -6542,74 +6489,78 @@ msgid "Activate checks payment methods" msgstr "" #: ../../content/applications/finance/accounting/payments/pay_checks.rst:15 -msgid "To activate the checks payment method, go to :menuselection:`Accounting --> Configuration --> Checks`, there you can activate the payment method as well as set up the :guilabel:`Check Layout`. Once activated the :guilabel:`Checks` setting, the feature is automatically setup for your :guilabel:`Outgoing Payments`." +msgid "To activate the checks payment method, go to :menuselection:`Accounting --> Configuration --> Settings`, and scroll down to the :guilabel:`Vendor Payments` section. There, you can activate the payment method as well as set up the :guilabel:`Check Layout`." msgstr "" -#: ../../content/applications/finance/accounting/payments/pay_checks.rst:21 +#: ../../content/applications/finance/accounting/payments/pay_checks.rst:20 +msgid "Once the :guilabel:`Checks` setting is activated, the **Checks** payment method is automatically set up in the :guilabel:`Outgoing Payments` tabs of **bank** journals." +msgstr "" + +#: ../../content/applications/finance/accounting/payments/pay_checks.rst:22 msgid "Some countries require specific modules to print checks; such modules may be installed by default. For instance, the :guilabel:`U.S. Checks Layout` module is required to print U.S. checks." msgstr "" -#: ../../content/applications/finance/accounting/payments/pay_checks.rst:26 +#: ../../content/applications/finance/accounting/payments/pay_checks.rst:27 msgid "Compatible check stationery for printing checks" msgstr "" -#: ../../content/applications/finance/accounting/payments/pay_checks.rst:29 +#: ../../content/applications/finance/accounting/payments/pay_checks.rst:30 msgid "United States" msgstr "" -#: ../../content/applications/finance/accounting/payments/pay_checks.rst:31 +#: ../../content/applications/finance/accounting/payments/pay_checks.rst:32 msgid "For the United States, Odoo supports by default the check formats of:" msgstr "" -#: ../../content/applications/finance/accounting/payments/pay_checks.rst:33 +#: ../../content/applications/finance/accounting/payments/pay_checks.rst:34 msgid "**Quickbooks & Quicken**: check on top, stubs in the middle and bottom;" msgstr "" -#: ../../content/applications/finance/accounting/payments/pay_checks.rst:34 +#: ../../content/applications/finance/accounting/payments/pay_checks.rst:35 msgid "**Peachtree**: check in the middle, stubs on top and bottom;" msgstr "" -#: ../../content/applications/finance/accounting/payments/pay_checks.rst:35 +#: ../../content/applications/finance/accounting/payments/pay_checks.rst:36 msgid "**ADP**: check in the bottom, and stubs on the top." msgstr "" -#: ../../content/applications/finance/accounting/payments/pay_checks.rst:38 +#: ../../content/applications/finance/accounting/payments/pay_checks.rst:39 msgid "Pay a supplier bill with a check" msgstr "" -#: ../../content/applications/finance/accounting/payments/pay_checks.rst:40 +#: ../../content/applications/finance/accounting/payments/pay_checks.rst:41 msgid "Paying a supplier with a check is done in three steps:" msgstr "" -#: ../../content/applications/finance/accounting/payments/pay_checks.rst:42 +#: ../../content/applications/finance/accounting/payments/pay_checks.rst:43 msgid "registering a payment" msgstr "" -#: ../../content/applications/finance/accounting/payments/pay_checks.rst:43 +#: ../../content/applications/finance/accounting/payments/pay_checks.rst:44 msgid "printing checks in batch for all registered payments" msgstr "" -#: ../../content/applications/finance/accounting/payments/pay_checks.rst:44 +#: ../../content/applications/finance/accounting/payments/pay_checks.rst:45 msgid "reconciling bank statements" msgstr "" -#: ../../content/applications/finance/accounting/payments/pay_checks.rst:47 +#: ../../content/applications/finance/accounting/payments/pay_checks.rst:48 msgid "Register a payment by check" msgstr "" -#: ../../content/applications/finance/accounting/payments/pay_checks.rst:49 +#: ../../content/applications/finance/accounting/payments/pay_checks.rst:50 msgid "To register a payment, open any supplier bill from the menu :menuselection:`Purchases --> Vendor Bills`. Once the supplier bill is validated, you can register a payment. Set the :guilabel:`Payment Method` to :guilabel:`Checks` and validate the payment." msgstr "" -#: ../../content/applications/finance/accounting/payments/pay_checks.rst:55 +#: ../../content/applications/finance/accounting/payments/pay_checks.rst:56 msgid "Print checks" msgstr "" -#: ../../content/applications/finance/accounting/payments/pay_checks.rst:57 +#: ../../content/applications/finance/accounting/payments/pay_checks.rst:58 msgid "On your :guilabel:`Accounting Dashboard` in the :guilabel:`Bank` Journal, you can see the number of checks registered. By clicking on :guilabel:`Checks to print` you have got the possibility to print the reconciled checks." msgstr "" -#: ../../content/applications/finance/accounting/payments/pay_checks.rst:61 +#: ../../content/applications/finance/accounting/payments/pay_checks.rst:62 msgid "To print all checks in batch, select all payments from the list view and click on :guilabel:`Print`." msgstr "" @@ -6750,139 +6701,155 @@ msgid "Main reports available" msgstr "" #: ../../content/applications/finance/accounting/reporting.rst:10 -msgid "Besides the reports created specifically in each localisation module, a few very useful **generic** and **dynamic reports** are available for all countries :" +msgid "Odoo includes **generic** and **dynamic** reports available for all countries, regardless of the :doc:`localization package <../../finance/fiscal_localizations>` installed:" msgstr "" -#: ../../content/applications/finance/accounting/reporting.rst:14 +#: ../../content/applications/finance/accounting/reporting.rst:13 msgid "**Balance Sheet**" msgstr "" -#: ../../content/applications/finance/accounting/reporting.rst:15 +#: ../../content/applications/finance/accounting/reporting.rst:14 msgid "**Profit and Loss**" msgstr "" -#: ../../content/applications/finance/accounting/reporting.rst:16 +#: ../../content/applications/finance/accounting/reporting.rst:15 msgid "**Executive Summary**" msgstr "" -#: ../../content/applications/finance/accounting/reporting.rst:17 +#: ../../content/applications/finance/accounting/reporting.rst:16 msgid "**General Ledger**" msgstr "" -#: ../../content/applications/finance/accounting/reporting.rst:18 +#: ../../content/applications/finance/accounting/reporting.rst:17 msgid "**Aged Payable**" msgstr "" -#: ../../content/applications/finance/accounting/reporting.rst:19 +#: ../../content/applications/finance/accounting/reporting.rst:18 msgid "**Aged Receivable**" msgstr "" -#: ../../content/applications/finance/accounting/reporting.rst:20 +#: ../../content/applications/finance/accounting/reporting.rst:19 msgid "**Cash Flow Statement**" msgstr "" -#: ../../content/applications/finance/accounting/reporting.rst:21 +#: ../../content/applications/finance/accounting/reporting.rst:20 msgid "**Tax Report**" msgstr "" #: ../../content/applications/finance/accounting/reporting.rst:22 -msgid "**Bank Reconciliation**" +msgid "Reports can be **annotated, printed, and drilled down** to see details (payments, invoices, journal items, etc.) by clicking the **down** arrow. Reports can also be exported to **PDF** or **XLSX** format by clicking :guilabel:`PDF` or :guilabel:`XLSX` at the top of the page." msgstr "" -#: ../../content/applications/finance/accounting/reporting.rst:24 -msgid "You can annotate every reports to print them and report to your adviser. Export to xls to manage extra analysis. Drill down in the reports to see more details (payments, invoices, journal items, etc.)." +#: ../../content/applications/finance/accounting/reporting.rst:-1 +msgid "Annotate reports." msgstr "" -#: ../../content/applications/finance/accounting/reporting.rst:28 -msgid "You can also compare values with another period. Choose how many periods you want to compare the chosen time period with. You can choose up to 12 periods back from the date of the report if you don't want to use the default **Previous 1 Period** option." +#: ../../content/applications/finance/accounting/reporting.rst:29 +msgid "You can compare values across periods by using the :guilabel:`Comparison` menu and selecting the periods you want to compare." msgstr "" -#: ../../content/applications/finance/accounting/reporting.rst:38 -msgid "The **Balance Sheet** shows a snapshot of the assets, liabilities and equity of your organisation as at a particular date." +#: ../../content/applications/finance/accounting/reporting.rst:-1 +msgid "Comparison menu to compare time periods." msgstr "" -#: ../../content/applications/finance/accounting/reporting.rst:44 +#: ../../content/applications/finance/accounting/reporting.rst:40 +msgid "The **Balance Sheet** shows a snapshot of your organization's assets, liabilities, and equity at a particular date." +msgstr "" + +#: ../../content/applications/finance/accounting/reporting.rst:-1 +msgid "Balance sheet report of Odoo." +msgstr "" + +#: ../../content/applications/finance/accounting/reporting.rst:49 msgid "Profit and Loss" msgstr "" -#: ../../content/applications/finance/accounting/reporting.rst:46 -msgid "The **Profit and Loss** report (or **Income Statement**) shows your organisation's net income, by deducting expenses from revenue for the report period." +#: ../../content/applications/finance/accounting/reporting.rst:51 +msgid "The **Profit and Loss** report (or **Income Statement**) shows your company's net income by deducting expenses from revenue for the reporting period." msgstr "" -#: ../../content/applications/finance/accounting/reporting.rst:53 +#: ../../content/applications/finance/accounting/reporting.rst:-1 +msgid "Profit and Loss report of Odoo" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting.rst:60 msgid "Executive Summary" msgstr "" -#: ../../content/applications/finance/accounting/reporting.rst:55 -msgid "The **Executive Summary** allows for a quick look at all the important figures you need to run your company." -msgstr "" - -#: ../../content/applications/finance/accounting/reporting.rst:58 -msgid "In very basic terms, this is what each of the items in this section is reporting :" -msgstr "" - -#: ../../content/applications/finance/accounting/reporting.rst:73 -msgid "**Performance:**" +#: ../../content/applications/finance/accounting/reporting.rst:62 +msgid "The **Executive Summary** allows a quick look at all the important figures to run your company." msgstr "" #: ../../content/applications/finance/accounting/reporting.rst:64 +msgid "In basic terms, this is what each item in the following section reports:" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting.rst:74 +msgid "**Performance:**" +msgstr "" + +#: ../../content/applications/finance/accounting/reporting.rst:68 msgid "**Gross profit margin:**" msgstr "" -#: ../../content/applications/finance/accounting/reporting.rst:63 -msgid "The contribution each individual sale made by your business less any direct costs needed to make those sales (things like labour, materials, etc)." +#: ../../content/applications/finance/accounting/reporting.rst:68 +msgid "The contribution of all sales made by your business **minus** any direct costs needed to make those sales (labor, materials, etc.)." msgstr "" -#: ../../content/applications/finance/accounting/reporting.rst:70 +#: ../../content/applications/finance/accounting/reporting.rst:72 msgid "**Net profit margin:**" msgstr "" -#: ../../content/applications/finance/accounting/reporting.rst:67 -msgid "The contribution each individual sale made by your business less any direct costs needed to make those sales, as well as any fixed overheads your company has (things like rent, electricity, taxes you need to pay as a result of those sales)." +#: ../../content/applications/finance/accounting/reporting.rst:71 +msgid "The contribution of all sales made by your business **minus** any direct costs needed to make those sales *and* fixed overheads your company has (electricity, rent, taxes to be paid as a result of those sales, etc.)." msgstr "" -#: ../../content/applications/finance/accounting/reporting.rst:73 -msgid "**Return on investment (p.a.):**" +#: ../../content/applications/finance/accounting/reporting.rst:74 +msgid "**Return on investment (per annum):**" msgstr "" -#: ../../content/applications/finance/accounting/reporting.rst:73 -msgid "The ratio of net profit made, to the amount of assets the company used to make those profits." +#: ../../content/applications/finance/accounting/reporting.rst:75 +msgid "The ratio of net profit made to the amount of assets the company used to make those profits." msgstr "" -#: ../../content/applications/finance/accounting/reporting.rst:93 +#: ../../content/applications/finance/accounting/reporting.rst:90 msgid "**Position:**" msgstr "" -#: ../../content/applications/finance/accounting/reporting.rst:77 -msgid "**Average debtor days:**" +#: ../../content/applications/finance/accounting/reporting.rst:78 +msgid "**Average debtors days:**" msgstr "" -#: ../../content/applications/finance/accounting/reporting.rst:77 -msgid "The average number of days it takes your customers to pay you (fully), across all your customer invoices." +#: ../../content/applications/finance/accounting/reporting.rst:78 +msgid "The average number of days it takes your customers to (fully) pay you across all your customer invoices." msgstr "" #: ../../content/applications/finance/accounting/reporting.rst:80 -msgid "**Average creditor days:**" +msgid "**Average creditors days:**" msgstr "" -#: ../../content/applications/finance/accounting/reporting.rst:80 -msgid "The average number of days it takes you to pay your suppliers (fully) across all your bills." +#: ../../content/applications/finance/accounting/reporting.rst:81 +msgid "The average number of days it takes you to (fully) pay your suppliers across all your bills." msgstr "" -#: ../../content/applications/finance/accounting/reporting.rst:85 -msgid "**Short term cash forecast:**" +#: ../../content/applications/finance/accounting/reporting.rst:84 +msgid "**Short-term cash forecast:**" msgstr "" #: ../../content/applications/finance/accounting/reporting.rst:83 -msgid "How much cash is expected in or out of your organisation in the next month i.e. balance of your **Sales account** for the month less the balance of your **Purchases account** for the month." +msgid "How much cash is expected in or out of your business in the next month, i.e., the balance of your **Sales account** for the month **minus** the balance of your **Purchases account** for the month." msgstr "" -#: ../../content/applications/finance/accounting/reporting.rst:93 +#: ../../content/applications/finance/accounting/reporting.rst:90 msgid "**Current assets to liabilities:**" msgstr "" -#: ../../content/applications/finance/accounting/reporting.rst:88 -msgid "Also referred to as **current ratio**, this is the ratio of current assets (assets that could be turned into cash within a year) to the current liabilities (liabilities which will be due in the next year). This is typically used as as a measure of a company's ability to service its debt." +#: ../../content/applications/finance/accounting/reporting.rst:87 +msgid "Also referred to as **current ratio**, this is the ratio of current assets (:dfn:`assets that could be turned into cash within a year`) to the current liabilities (:dfn:`liabilities that will be due in the next year`). It is typically used to measure a company's ability to service its debt." +msgstr "" + +#: ../../content/applications/finance/accounting/reporting.rst:-1 +msgid "Executive summary report in Odoo." msgstr "" #: ../../content/applications/finance/accounting/reporting.rst:98 @@ -6890,7 +6857,11 @@ msgid "General Ledger" msgstr "" #: ../../content/applications/finance/accounting/reporting.rst:100 -msgid "The **General Ledger Report** shows all transactions from all accounts for a chosen date range. The initial summary report shows the totals for each account and from there you can view a detailed transaction report or any exceptions. This report is useful for checking every transaction that occurred during a certain period of time." +msgid "The **General Ledger Report** shows all transactions from all accounts for a chosen date range. The initial summary report shows each account's totals; from here, you can view a detailed transaction report or any exceptions. This report helps check every transaction that occurred during a specific period." +msgstr "" + +#: ../../content/applications/finance/accounting/reporting.rst:-1 +msgid "General Ledger report in Odoo." msgstr "" #: ../../content/applications/finance/accounting/reporting.rst:111 @@ -6898,7 +6869,11 @@ msgid "Aged Payable" msgstr "" #: ../../content/applications/finance/accounting/reporting.rst:113 -msgid "Run the **Aged Payable Details** report to display information on individual bills, credit notes and overpayments owed by you, and how long these have gone unpaid." +msgid "Run the **Aged Payable Details** report to display information on individual bills, credit notes, and overpayments you owe and how long these have gone unpaid." +msgstr "" + +#: ../../content/applications/finance/accounting/reporting.rst:-1 +msgid "Aged Payable report in Odoo." msgstr "" #: ../../content/applications/finance/accounting/reporting.rst:122 @@ -6906,26 +6881,38 @@ msgid "Aged Receivable" msgstr "" #: ../../content/applications/finance/accounting/reporting.rst:124 -msgid "The **Aged Receivables** report shows the sales invoices that were awaiting payment during a selected month and several months prior." +msgid "The **Aged Receivables** report shows the sales invoices awaiting payment during a selected month and several months prior." msgstr "" -#: ../../content/applications/finance/accounting/reporting.rst:130 +#: ../../content/applications/finance/accounting/reporting.rst:-1 +msgid "Aged Receivable report in Odoo." +msgstr "" + +#: ../../content/applications/finance/accounting/reporting.rst:133 msgid "Cash Flow Statement" msgstr "" -#: ../../content/applications/finance/accounting/reporting.rst:132 -msgid "The **Cash Flow Statement** shows how changes in balance sheet accounts and income affect cash and cash equivalents, and breaks the analysis down to operating, investing and financing activities." +#: ../../content/applications/finance/accounting/reporting.rst:135 +msgid "The **Cash Flow Statement** shows how changes in balance sheet accounts and income affect cash and cash equivalents and breaks the analysis down to operating, investing, and financing activities." msgstr "" -#: ../../content/applications/finance/accounting/reporting.rst:141 +#: ../../content/applications/finance/accounting/reporting.rst:-1 +msgid "Cash Flow Statement report in Odoo." +msgstr "" + +#: ../../content/applications/finance/accounting/reporting.rst:144 #: ../../content/applications/finance/accounting/reporting/tax_returns.rst:101 msgid "Tax Report" msgstr "" -#: ../../content/applications/finance/accounting/reporting.rst:143 +#: ../../content/applications/finance/accounting/reporting.rst:146 msgid "This report allows you to see the **net** and **tax amounts** for all the taxes grouped by type (sale/purchase)." msgstr "" +#: ../../content/applications/finance/accounting/reporting.rst:-1 +msgid "Tax report in Odoo." +msgstr "" + #: ../../content/applications/finance/accounting/reporting/analytic_accounting.rst:3 msgid "Analytic accounting" msgstr "" @@ -9624,7 +9611,7 @@ msgstr "" #: ../../content/applications/finance/accounting/vendor_bills.rst:5 #: ../../content/applications/finance/fiscal_localizations/argentina.rst:588 -#: ../../content/applications/finance/fiscal_localizations/chile.rst:702 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:698 #: ../../content/applications/finance/fiscal_localizations/italy.rst:279 msgid "Vendor bills" msgstr "" @@ -9637,6 +9624,10 @@ msgstr "" msgid "Tutorial `Registering a vendor bill `_" msgstr "" +#: ../../content/applications/finance/accounting/vendor_bills.rst:13 +msgid ":doc:`/applications/inventory_and_mrp/purchase/manage_deals/manage`" +msgstr "" + #: ../../content/applications/finance/accounting/vendor_bills.rst:16 msgid "Bill creation" msgstr "" @@ -11912,7 +11903,7 @@ msgid "A list showing less common Argentinean tax options, which are labeled as msgstr "" #: ../../content/applications/finance/fiscal_localizations/argentina.rst:200 -#: ../../content/applications/finance/fiscal_localizations/chile.rst:254 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:250 msgid "Document types" msgstr "" @@ -11969,7 +11960,7 @@ msgid "document types grouped by letters." msgstr "" #: ../../content/applications/finance/fiscal_localizations/argentina.rst:243 -#: ../../content/applications/finance/fiscal_localizations/chile.rst:271 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:267 msgid "Use on invoices" msgstr "" @@ -12086,7 +12077,7 @@ msgid "When creating :guilabel:`Purchase Journals`, it's possible to define whet msgstr "" #: ../../content/applications/finance/fiscal_localizations/argentina.rst:330 -#: ../../content/applications/finance/fiscal_localizations/chile.rst:393 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:389 #: ../../content/applications/finance/fiscal_localizations/peru.rst:351 msgid "Usage and testing" msgstr "" @@ -13124,7 +13115,7 @@ msgid "The Belgian chart of accounts includes pre-configured accounts as describ msgstr "" #: ../../content/applications/finance/fiscal_localizations/belgium.rst:66 -#: ../../content/applications/finance/fiscal_localizations/chile.rst:375 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:371 #: ../../content/applications/finance/fiscal_localizations/romania.rst:79 msgid ":doc:`../accounting/get_started/chart_of_accounts`" msgstr "" @@ -13719,7 +13710,7 @@ msgstr "" #: ../../content/applications/finance/fiscal_localizations/brazil.rst:70 #: ../../content/applications/finance/fiscal_localizations/brazil.rst:233 -#: ../../content/applications/finance/fiscal_localizations/chile.rst:234 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:230 #: ../../content/applications/finance/fiscal_localizations/ecuador.rst:78 #: ../../content/applications/finance/fiscal_localizations/ecuador.rst:271 msgid ":guilabel:`Name`" @@ -13754,7 +13745,7 @@ msgstr "" #: ../../content/applications/finance/fiscal_localizations/brazil.rst:78 #: ../../content/applications/finance/fiscal_localizations/brazil.rst:240 -#: ../../content/applications/finance/fiscal_localizations/chile.rst:235 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:231 #: ../../content/applications/finance/fiscal_localizations/ecuador.rst:83 #: ../../content/applications/finance/fiscal_localizations/ecuador.rst:276 msgid ":guilabel:`Email`" @@ -14177,7 +14168,7 @@ msgid "Adds the *Propuesta F29* and *Balance Tributario (8 columnas)* reports." msgstr "" #: ../../content/applications/finance/fiscal_localizations/chile.rst:40 -msgid ":guilabel:`Chile - E-invoiving`" +msgid ":guilabel:`Chile - E-invoicing`" msgstr "" #: ../../content/applications/finance/fiscal_localizations/chile.rst:41 @@ -14201,7 +14192,7 @@ msgid "Includes all technical and functional requirements to generate and receiv msgstr "" #: ../../content/applications/finance/fiscal_localizations/chile.rst:48 -msgid ":guilabel:`Electronic Esports of Goods for Chile`" +msgid ":guilabel:`Electronic Exports of Goods for Chile`" msgstr "" #: ../../content/applications/finance/fiscal_localizations/chile.rst:49 @@ -14213,12 +14204,10 @@ msgid "Includes technical and functional requirements to generate electronic inv msgstr "" #: ../../content/applications/finance/fiscal_localizations/chile.rst:52 -#: ../../content/applications/finance/fiscal_localizations/chile.rst:56 msgid ":guilabel:`Chile - E-Invoicing Delivery Guide`" msgstr "" #: ../../content/applications/finance/fiscal_localizations/chile.rst:53 -#: ../../content/applications/finance/fiscal_localizations/chile.rst:57 msgid "`l10n_cl_edi_stock`" msgstr "" @@ -14227,157 +14216,153 @@ msgid "Includes all technical and functional requirements to generate delivery g msgstr "" #: ../../content/applications/finance/fiscal_localizations/chile.rst:58 -msgid "Includes all technical and functional requirements to generate delivery guides online based on the :abbr:`SII (Servicio de Impuestos Internos)` regulations." -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/chile.rst:62 msgid "Odoo automatically installs the appropriate package for the company according to the country selected at the creation of the database." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:64 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:60 msgid "The *Chile - E-Invoicing Delivery Guide* module depends on the *Inventory* application." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:67 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:63 msgid "All features are only available if the company already completed the `SII Sistema de Facturación de Mercado `_ certification process." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:72 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:68 #: ../../content/applications/finance/fiscal_localizations/italy.rst:41 #: ../../content/applications/finance/fiscal_localizations/saudi_arabia.rst:38 msgid "Company information" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:74 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:70 msgid "Navigate to :menuselection:`Settings --> Companies: Update Info` and ensure the following company information is up-to-date and correctly filled in:" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:77 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:73 msgid ":guilabel:`Company Name`" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:78 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:74 msgid ":guilabel:`Address`:" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:80 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:76 msgid ":guilabel:`Street`" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:81 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:77 msgid ":guilabel:`City`" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:82 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:78 msgid ":guilabel:`State`" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:83 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:79 msgid ":guilabel:`ZIP`" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:84 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:80 msgid ":guilabel:`Country`" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:86 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:82 msgid ":guilabel:`Tax ID`: enter the identification number for the selected :ref:`Taxpayer Type `." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:88 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:84 msgid ":guilabel:`Activity Names`: select up to four activity codes." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:89 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:85 msgid ":guilabel:`Company Activity Description`: enter a short description of the company's activity." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:92 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:88 msgid "Accounting settings" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:94 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:90 msgid "Next, navigate to :menuselection:`Accounting --> Configuration --> Settings --> Chilean Localization` and follow the instructions to configure the:" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:97 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:93 msgid ":ref:`Fiscal information `" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:98 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:94 msgid ":ref:`Electronic invoice data `" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:99 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:95 msgid ":ref:`DTE incoming email server `" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:100 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:96 msgid ":ref:`Signature certificates `" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:105 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:101 #: ../../content/applications/finance/fiscal_localizations/colombia.rst:162 msgid "Fiscal information" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:107 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:103 msgid "Configure the following :guilabel:`Tax payer information`:" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:109 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:105 msgid ":guilabel:`Taxpayer Type` by selecting the taxpayer type that applies:" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:111 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:107 msgid ":guilabel:`VAT Affected (1st Category)`: for invoices that charge taxes to customers" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:112 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:108 msgid ":guilabel:`Fees Receipt Issuer (2nd Category)`: for suppliers who issue fees receipt (Boleta)" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:113 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:109 msgid ":guilabel:`End consumer`: only issues receipts" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:114 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:110 msgid ":guilabel:`Foreigner`" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:116 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:112 msgid ":guilabel:`SII Office`: select your company's :abbr:`SII (Servicio de Impuestos Internos)` regional office" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:122 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:118 msgid "Electronic invoice data" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:124 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:120 msgid "Select your :guilabel:`SII Web Services` environment:" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:126 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:122 msgid ":guilabel:`SII - Test`: for test databases using test :abbr:`CAFs (Folio Authorization Code)` obtained from the :abbr:`SII (Servicio de Impuestos Internos)`. In this mode, the direct connection flows can be tested, with the files being sent to the :abbr:`SII (Servicio de Impuestos Internos)`." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:130 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:126 msgid ":guilabel:`SII - Production`: for production databases." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:131 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:127 msgid ":guilabel:`SII - Demo Mode`: files are created and accepted automatically in demo mode but are **not** sent to the :abbr:`SII (Servicio de Impuestos Internos)`. For this reason, rejection errors or *Accepted with Objections* will not appear in this mode. Every internal validation can be tested in demo mode. Avoid selecting this option in a production database." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:136 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:132 msgid "Then, enter the :guilabel:`Legal Electronic Invoicing Data`:" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:138 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:134 msgid ":guilabel:`SII Resolution N°`" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:139 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:135 msgid ":guilabel:`SII Resolution Date`" msgstr "" @@ -14385,71 +14370,71 @@ msgstr "" msgid "Required information for electronic invoice." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:148 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:144 msgid "DTE incoming email server" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:150 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:146 msgid "The :abbr:`DTE (Documentos Tributarios Electrónicos)` :guilabel:`Email Box Electronic Invoicing` can be defined to receive your customers' claim and acceptance emails. Enabling this option from :menuselection:`Accounting --> Configuration --> Settings --> Chilean Localization` is necessary if you want to use *Email Box Electronic Invoicing* as the :abbr:`DTE (Documentos Tributarios Electrónicos)` incoming email server." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:157 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:153 msgid "In order to receive your SII documents, it's necessary to set up your own email server. More information on how to do this can be found in this documentation: :doc:`../../general/email_communication/email_servers`" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:161 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:157 msgid "Begin by clicking :guilabel:`Configure DTE Incoming Email`, then click :guilabel:`New` to add a server and fill in the following fields:" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:164 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:160 msgid ":guilabel:`Name`: give the server a name." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:165 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:161 msgid ":guilabel:`Server Type`: select the server type used." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:167 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:163 msgid ":guilabel:`IMAP Server`" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:168 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:164 msgid ":guilabel:`POP Server`" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:169 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:165 msgid ":guilabel:`Local Server`: uses a local script to fetch emails and create new records. The script can be found in the :guilabel:`Configuration` section with this option selected." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:171 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:167 msgid ":guilabel:`Gmail OAuth Authentication`: requires your Gmail API credentials to be configured in the general settings. A direct link to the configuration can be found in the :guilabel:`Login Information` section." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:175 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:171 msgid ":guilabel:`DTE Server`: enable this option. By checking this option, this email account will be used to receive the electronic invoices from the suppliers, and communications from the :abbr:`SII (Servicio de Impuestos Internos)` regarding the electronic invoices issued. In this case, this email should match both emails declared on the :abbr:`SII (Servicio de Impuestos Internos)` site in the section: *ACTUALIZACION DE DATOS DEL CONTRIBUYENTE*, *Mail Contacto SII* and *Mail Contacto Empresas*." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:182 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:178 msgid "In the :guilabel:`Server & Login` tab (for IMAP and POP servers):" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:184 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:180 msgid ":guilabel:`Server Name`: enter the hostname or IP of the server." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:185 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:181 msgid ":guilabel:`Port`: enter the server port." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:186 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:182 msgid ":guilabel:`SSL/TLS`: enable this option if connections are encrypted using the SSL/TLS protocol." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:187 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:183 msgid ":guilabel:`Username`: enter the server login username." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:188 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:184 msgid ":guilabel:`Password`: enter the server login password." msgstr "" @@ -14457,32 +14442,32 @@ msgstr "" msgid "Incoming email server configuration for Chilean DTE." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:195 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:191 msgid "Before going live, it is recommended to archive or remove all emails related to vendor bills that are not required to be processed in Odoo from your inbox." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:201 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:197 #: ../../content/applications/finance/fiscal_localizations/peru.rst:219 msgid "Certificate" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:203 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:199 msgid "A digital certificate in `.pfx` format is required to generate the electronic invoice signature. To add one, click :guilabel:`Configure Signature Certificates` under the :guilabel:`Signature Certificates` section. Then, click :guilabel:`New` to configure the certificate:" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:207 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:203 msgid ":guilabel:`Certificate Key`: click :guilabel:`Upload your file` and select the `.pfx` file." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:208 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:204 msgid ":guilabel:`Certificate Passkey`: enter the file's passphrase." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:209 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:205 msgid ":guilabel:`Subject Serial Number`: depending on the certificate format, the field might not be automatically populated. In that case, enter the certificate's legal representative :abbr:`RUT (Rol Único Tributario)`." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:212 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:208 msgid ":guilabel:`Certificate Owner`: select one if you need to restrict the certificate for a specific user. Leave the field empty to share it with all billing users." msgstr "" @@ -14490,52 +14475,52 @@ msgstr "" msgid "Digital certificate configuration." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:220 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:216 #: ../../content/applications/finance/fiscal_localizations/mexico.rst:565 #: ../../content/applications/finance/fiscal_localizations/peru.rst:230 msgid "Multicurrency" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:222 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:218 msgid "The official currency rate is provided by `Chilean mindicador.cl `_. Navigate to :menuselection:`Accounting --> Configuration --> Settings --> Currencies: Automatic Currency Rates` to set an :guilabel:`Interval` for when the rate is automatically updated, or to select another :guilabel:`Service`." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:228 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:224 #: ../../content/applications/finance/fiscal_localizations/france.rst:306 msgid "Partner information" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:230 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:226 msgid "Configuring partner contacts is also required to send :abbr:`SII (Servicio de Impuestos Internos)` electronic invoices. Open the :menuselection:`Contacts` app to do so and fill in the following fields on a new or existing contact form." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:236 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:232 #: ../../content/applications/finance/fiscal_localizations/ecuador.rst:80 msgid ":guilabel:`Identification Number`" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:237 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:233 #: ../../content/applications/finance/fiscal_localizations/ecuador.rst:81 msgid ":guilabel:`Taxpayer Type`" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:238 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:234 msgid ":guilabel:`Activity Description`" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:240 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:236 msgid "In the :guilabel:`Electronic Invoicing` tab:" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:242 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:238 msgid ":guilabel:`DTE Email`: enter the sender's email address for the partner." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:243 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:239 msgid ":guilabel:`Delivery Guide Price`: select which price the delivery guide displays, if any." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:246 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:242 msgid "The :guilabel:`DTE Email` is the email used for sending electronic documents and must be set in the contact that will be part of an electronic document." msgstr "" @@ -14543,11 +14528,11 @@ msgstr "" msgid "Chilean electronic invoice data for partners." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:256 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:252 msgid "Accounting documents are categorized by :abbr:`SII (Servicio de Impuestos Internos)`-defined document types." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:259 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:255 msgid "Document types are created automatically upon installation of the localization module, and can be managed by navigating to :menuselection:`Accounting --> Configuration --> Document Types`." msgstr "" @@ -14555,166 +14540,166 @@ msgstr "" msgid "Chilean fiscal document types list." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:267 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:263 msgid "Several document types are inactive by default but can be activated by toggling the :guilabel:`Active` option." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:273 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:269 msgid "The document type on each transaction is determined by:" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:275 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:271 msgid "The journal related to the invoice, identifying if the journal uses documents." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:276 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:272 msgid "The condition applied based on the type of issuer and recipient (e.g., the buyer or vendor's fiscal regime)." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:282 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:278 msgid "*Sales journals* in Odoo usually represent a business unit or location." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:285 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:281 msgid "Ventas Santiago." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:286 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:282 msgid "Ventas Valparaiso." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:288 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:284 msgid "For retail stores it is common to have one journal per :abbr:`POS (Point of Sale)`." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:291 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:287 msgid "Cashier 1." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:292 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:288 msgid "Cashier 2." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:294 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:290 msgid "The *purchase* transactions can be managed with a single journal, but sometimes companies use more than one journal in order to handle some accounting transactions that are not related to vendor bills. This configuration can easily be set by using the following model." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:299 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:295 msgid "Tax payments to the government." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:300 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:296 msgid "Employees payments." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:303 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:299 msgid "Create a sales journal" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:305 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:301 msgid "To create a sales 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:308 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:304 msgid ":guilabel:`Type`: select :guilabel:`Sale` from the drop-down menu for customer invoice journals." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:309 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:305 msgid ":guilabel:`Point of sale type`: if the sales journal will be used for electronic documents, the option :guilabel:`Online` must be selected. Otherwise, if the journal is used for invoices imported from a previous system or if you are using the :abbr:`SII (Servicio de Impuestos Internos)` portal *Facturación MiPyme*, you can use the option :guilabel:`Manual`." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:313 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:309 msgid ":guilabel:`Use Documents`: check this field if the journal will use document types. This field is only applicable to purchase and sales journals that can be related to the different sets of document types available in Chile. By default, all the sales journals created will use documents." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:317 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:313 msgid "Next, from the :guilabel:`Jounal Entries` tab, define the :guilabel:`Default Income Account` and :guilabel:`Dedicated Credit Note Squence` in the :guilabel:`Accounting Information` section. Configuring these fields is required for one of the debit notes :ref:`use cases `." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:324 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:320 msgid "CAF" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:326 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:322 msgid "A *folio authorization code* (CAF) is required for each document type that will be issued electronically. The :abbr:`CAF (Folio Authorization Code)` is a file the :abbr:`SII (Servicio de Impuestos Internos)` provides to the issuer with the folios/sequences authorized for the electronic invoice documents." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:331 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:327 msgid "Your company can request multiple folios and obtain several :abbr:`CAFs (Folio Authorization Codes)` linked to different folio ranges. These :abbr:`CAFs (Folio Authorization Code)` are shared within all journals, so you only need one active :abbr:`CAF (Folio Authorization Code)` per document type, and it will be applied to all journals." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:336 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:332 msgid "Please refer to the `SII documentation `_ to check the details on how to acquire the :abbr:`CAF (Folio Authorization Code)` files." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:340 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:336 msgid "The :abbr:`CAFs (Folio Authorization Code)` required by the :abbr:`SII (Servicio de Impuestos Internos)` are different from production to test (certification mode). Make sure you have the correct :abbr:`CAF (Folio Authorization Code)` set depending on your environment." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:345 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:341 msgid "Upload CAF files" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:347 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:343 msgid "Once the :abbr:`CAF (Folio Authorization Code)` files have been acquired from the :abbr:`SII (Servicio de Impuestos Internos)` portal, they need to be uploaded in the database by navigating to :menuselection:`Accounting --> Configuration: Chilean SII --> CAFs`. Then, click the :guilabel:`New` begin the configuration. On the :abbr:`CAF (Folio Authorization Code)` form, upload your :abbr:`CAF (Folio Authorization Code)` file by clicking the :guilabel:`Upload your file` button and then click :guilabel:`Save`." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:354 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:350 msgid "Once uploaded, the status changes to :guilabel:`In Use`. At this moment, when a transaction is used for this document type, the invoice number takes the first folio in the sequence." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:358 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:354 msgid "The document types have to be active before uploading the :abbr:`CAF (Folio Authorization Code)` files. In case some folios have been used in the previous system, the next valid folio has to be set when the first transaction is created." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:365 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:361 msgid "The chart of accounts is installed by default as part of the data set included in the localization module. The accounts are mapped automatically in:" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:369 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:365 msgid "Default Account Payable" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:370 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:366 #: ../../content/applications/finance/fiscal_localizations/peru.rst:75 msgid "Default Account Receivable" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:371 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:367 msgid "Transfer Accounts" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:372 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:368 msgid "Conversion Rate" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:380 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:376 msgid "As part of the localization module, taxes are created automatically with their related financial account and configuration. These taxes can be managed from :menuselection:`Accounting --> Configuration --> Taxes`." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:384 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:380 msgid "Chile has several tax types, the most common ones are:" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:386 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:382 msgid "**VAT**: the regular VAT can have several rates." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:387 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:383 msgid "**ILA**: the tax for alcoholic drinks." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:390 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:386 #: ../../content/applications/finance/fiscal_localizations/egypt.rst:125 #: ../../content/applications/finance/fiscal_localizations/romania.rst:106 msgid ":doc:`../accounting/taxes`" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:396 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:392 msgid "Electronic invoice workflow" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:398 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:394 msgid "In the Chilean localization, the electronic invoice workflow includes customer invoice issuance and vendor bill reception. The following diagram explains how information is shared to the :abbr:`SII (Servicio de Impuestos Internos)`, customers, and vendors." msgstr "" @@ -14722,11 +14707,11 @@ msgstr "" msgid "Diagram with Electronic invoice transactions." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:407 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:403 msgid "Customer invoice emission" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:409 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:405 msgid "After the partners and journals are created and configured, the invoices are created in the standard way. For Chile, one of the differences is the document type that is automatically selected based on the taxpayer. The document type can be changed manually if needed on the invoice by navigating to :menuselection:`Accounting --> Customers --> Invoices`." msgstr "" @@ -14734,24 +14719,24 @@ msgstr "" msgid "Customer invoice document type selection." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:419 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:415 msgid ":guilabel:`Documents type 33` electronic invoice must have at least one item with tax, otherwise the :abbr:`SII (Servicio de Impuestos Internos)` rejects the document validation." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:425 -#: ../../content/applications/finance/fiscal_localizations/chile.rst:877 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:421 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:873 msgid "Validation and DTE status" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:427 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:423 msgid "Once all invoice information is filled, either manually or automatically when generated from a sales order, validate the invoice. After the invoice is posted:" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:430 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:426 msgid "The :abbr:`DTE (Documentos Tributarios Electrónicos)` file is created automatically and recorded in the chatter." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:432 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:428 msgid "The :abbr:`DTE (Documentos Tributarios Electrónicos)` :abbr:`SII (Servicio de Impuestos Internos)` status is set as :guilabel:`Pending` to be sent." msgstr "" @@ -14759,7 +14744,7 @@ msgstr "" msgid "DTE XML File displayed in chatter." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:439 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:435 msgid "The :abbr:`DTE (Documentos Tributarios Electrónicos)` status is updated automatically by Odoo with a scheduled action that runs every day at night, if the response from the :abbr:`SII (Servicio de Impuestos Internos)` is needed immediately, you can do it manually as well by following the :abbr:`DTE (Documentos Tributarios Electrónicos)` status workflow:" msgstr "" @@ -14767,11 +14752,11 @@ msgstr "" msgid "Transition of DTE status flow." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:448 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:444 msgid "The first step is to send the :abbr:`DTE (Documentos Tributarios Electrónicos)` to the :abbr:`SII (Servicio de Impuestos Internos)`. This can be sent manually by clicking the :guilabel:`Enviar Ahora` button. This generates a :guilabel:`SII Tack number` for the invoice, which is used to check the details sent by the :abbr:`SII (Servicio de Impuestos Internos)` via email. Then, the :guilabel:`DTE status` is updated to :guilabel:`Ask for Status`." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:453 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:449 msgid "Once the :abbr:`SII (Servicio de Impuestos Internos)` response is received, Odoo updates the :guilabel:`DTE status`. To do it manually, click on the button :guilabel:`Verify on SII`. The result can either be :guilabel:`Accepted`, :guilabel:`Accepted With Objection` or :guilabel:`Rejected`." msgstr "" @@ -14779,7 +14764,7 @@ msgstr "" msgid "Identification transaction for invoice and Status update." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:463 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:459 msgid "There are intermediate statuses in the :abbr:`SII (Serviciqo de Impuestos Internos)` before acceptance or rejection. It's recommended to **NOT** continuously click :guilabel:`Verify in SII` for smooth processing." msgstr "" @@ -14787,35 +14772,35 @@ msgstr "" msgid "Electronic invoice data statuses." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:471 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:467 msgid "The final response from the :abbr:`SII (Servicio de Impuestos Internos)` can take on one of these values:" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:474 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:470 msgid ":guilabel:`Accepted`: indicates the invoice information is correct, our document is now fiscally valid and it's automatically sent to the customer." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:476 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:472 msgid ":guilabel:`Accepted with objections`: indicates the invoice information is correct, but a minor issue was identified, nevertheless the document is now fiscally valid and it's automatically sent to the customer." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:479 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:475 msgid ":guilabel:`Rejected`: indicates the invoice information is incorrect and must be corrected. Details are sent to emails you registered in the :abbr:`SII (Servicio de Impuestos Internos)`. If it is properly configured in Odoo, the details are also retrieved in the chatter once the email server is processed." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:484 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:480 msgid "If the invoice is rejected please follow these steps:" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:486 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:482 msgid "Change the document to :guilabel:`Draft`." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:487 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:483 msgid "Make the required corrections based on the message received from the :abbr:`SII (Servicio de Impuestos Internos)` in the chatter." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:489 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:485 msgid "Post the invoice again." msgstr "" @@ -14823,11 +14808,11 @@ msgstr "" msgid "Message when an invoice is rejected." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:496 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:492 msgid "Crossed references" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:498 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:494 msgid "When the invoice is created, as a result of another fiscal document, the information related to the originator document must be registered in the :guilabel:`Cross-Reference` tab. This tab is commonly used for credit or debit notes, however, in some cases it can be used for customer invoices, as well. In the case of the credit and debit notes, they are set automatically by Odoo." msgstr "" @@ -14835,14 +14820,14 @@ msgstr "" msgid "Crossed referenced document(s)." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:510 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:506 #: ../../content/applications/finance/fiscal_localizations/india.rst:133 #: ../../content/applications/finance/fiscal_localizations/india.rst:271 #: ../../content/applications/finance/fiscal_localizations/peru.rst:-1 msgid "Invoice PDF report" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:512 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:508 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." msgstr "" @@ -14850,31 +14835,31 @@ msgstr "" msgid "SII Validation fiscal elements." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:521 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:517 msgid "If you are hosted in Odoo SH or On-Premise, you should manually install the `pdf417gen `_ library. Use the following command to install it: :command:`pip install pdf417gen`." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:526 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:522 msgid "Commercial validation" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:528 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:524 msgid "Once the invoice has been sent to the customer:" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:530 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:526 msgid ":guilabel:`DTE Partner Status` changes to :guilabel:`Sent`." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:531 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:527 msgid "The customer must send a reception confirmation email." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:532 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:528 msgid "Subsequently, if commercial terms and invoice data are correct, an acceptance confirmation is sent; otherwise, a claim is sent." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:534 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:530 msgid "The field :guilabel:`DTE Acceptance Status` is updated automatically." msgstr "" @@ -14882,11 +14867,11 @@ msgstr "" msgid "Message with the commercial acceptance from the customer." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:541 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:537 msgid "Processed for claimed invoices" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:543 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:539 msgid "Once the invoice has been accepted by the :abbr:`SII (Servicio de Impuestos Internos)`, **it can not be cancelled in Odoo**. In case you get a claim for your customer, the correct way to proceed is with a credit note to either cancel the invoice or correct it. Please refer to the :ref:`chile/credit-notes` section for more details." msgstr "" @@ -14894,12 +14879,12 @@ msgstr "" msgid "Invoice Commercial status updated to claimed." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:553 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:549 #: ../../content/applications/finance/fiscal_localizations/colombia.rst:403 msgid "Common errors" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:555 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:551 msgid "There are multiple reasons behind a rejection from the :abbr:`SII (Servicio de Impuestos Internos)`, but these are some of the common errors you might have and how to solve them:" msgstr "" @@ -14959,33 +14944,33 @@ msgstr "" msgid "**Hint:** there are just five reasons why this error could show up and all of them are related to the *Caratula* section of the XML:" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:587 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:583 msgid "The company's :abbr:`RUT (Rol Único Tributario)` number is incorrect or missing." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:588 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:584 msgid "The certificate owner :abbr:`RUT (Rol Único Tributario)` number is incorrect or missing." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:589 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:585 msgid "The :abbr:`SII's (Servicio de Impuestos Internos)` :abbr:`RUT (Rol Único Tributario)` number (this should be correct by default) is incorrect or missing." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:591 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:587 msgid "The resolution date is incorrect or missing." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:592 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:588 msgid "The resolution number is incorrect or missing." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:597 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:593 #: ../../content/applications/finance/fiscal_localizations/colombia.rst:344 #: ../../content/applications/finance/fiscal_localizations/mexico.rst:348 msgid "Credit notes" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:599 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:595 msgid "When a cancellation or correction is needed over a validated invoice, a credit note must be generated. It is important to consider that a :abbr:`CAF (Folio Authorization Code)` file is required for the credit note, which is identified as :guilabel:`Document Type` :guilabel:`61` in the :abbr:`SII (Servicio de Impuestos Internos)`. Please refer to the :ref:`CAF section ` for more information on the process to load the :abbr:`CAF (Folio Authorization Code)` on each document type." msgstr "" @@ -14993,16 +14978,16 @@ msgstr "" msgid "Creation of CAF for Credit notes." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:611 -#: ../../content/applications/finance/fiscal_localizations/chile.rst:667 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:607 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:663 msgid "Use cases" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:614 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:610 msgid "Cancel referenced document" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:616 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:612 msgid "In case you need to cancel or invalidate an invoice, navigate to :menuselection:`Accounting --> Customers --> Invoices` and select the desired invoice. Then, use the button :guilabel:`Add Credit Note` and select :guilabel:`Full Refund`, in this case the :abbr:`SII (Servicio de Impuestos Internos)` reference code is automatically set to :guilabel:`Anula Documento de referencia`." msgstr "" @@ -15010,11 +14995,11 @@ msgstr "" msgid "Credit note canceling the referenced document." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:626 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:622 msgid "Correct referenced document" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:628 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:624 msgid "If a correction in the invoice information is required, for example the street name on the original invoice is wrong, then use the button :guilabel:`Add Credit Note`, select :guilabel:`Partial Refund` and select the option :guilabel:`Only Text Correction`. In this case the :guilabel:`SII Reference Code` field is automatically set to :guilabel:`Corrects Referenced Document Text`." msgstr "" @@ -15022,7 +15007,7 @@ msgstr "" msgid "Credit note correcting referenced document text." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:637 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:633 msgid "Odoo creates a credit note with the corrected text in an invoice and :guilabel:`Price` `0.00`." msgstr "" @@ -15030,15 +15015,15 @@ msgstr "" msgid "Credit note with the corrected value on the invoice lines." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:644 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:640 msgid "Make sure to define the :guilabel:`Default Credit Account` in the sales journal specifically for this use case." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:648 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:644 msgid "Corrects referenced document amount" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:650 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:646 msgid "When a correction on the amounts is required, use the button :guilabel:`Add Credit note` and select :guilabel:`Partial Refund`. In this case the :guilabel:`SII Reference Code` is automatically set to :guilabel:`Corrige el monto del Documento de Referencia`." msgstr "" @@ -15046,20 +15031,20 @@ msgstr "" msgid "Credit note for partial refund to correct amounts, using the SII reference code 3." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:659 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:655 #: ../../content/applications/finance/fiscal_localizations/colombia.rst:368 msgid "Debit notes" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:661 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:657 msgid "In Chilean localization, debit notes, in addition to credit notes, can be created using the :guilabel:`Add Debit Note` button, with two main use cases." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:670 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:666 msgid "Add debt on invoices" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:672 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:668 msgid "The primary use case for debit notes is to increase the value of an existing invoice. To do so, select option :guilabel:`3. Corrige el monto del Documento de Referencia` for the :guilabel:`Reference Code SII` field." msgstr "" @@ -15067,7 +15052,7 @@ msgstr "" msgid "Debit note correcting referenced document amount." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:680 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:676 msgid "In this case Odoo automatically includes the :guilabel:`Source Invoice` in the :guilabel:`Cross Reference` tab." msgstr "" @@ -15075,15 +15060,15 @@ msgstr "" msgid "Automatic reference to invoice in a debit note." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:688 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:684 msgid "You can only add debit notes to an invoice already accepted by the SII." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:691 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:687 msgid "Cancel credit notes" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:693 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:689 msgid "In Chile, debits notes are used to cancel a valid credit note. To do this, click the :guilabel:`Add Debit Note` button and select the :guilabel:`1: Anula Documentos de referencia` option for the :guilabel:`Reference Code SII` field." msgstr "" @@ -15091,47 +15076,47 @@ msgstr "" msgid "Debit note to cancel the referenced document (credit note)." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:704 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:700 msgid "As part of the Chilean localization, you can configure your incoming email server to match the one you have registered in the :abbr:`SII (Servicio de Impuestos Internos)` in order to:" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:707 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:703 msgid "Automatically receive the vendor bills :abbr:`DTE (Documentos Tributarios Electrónicos)` and create the vendor bill based on this information." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:709 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:705 msgid "Automatically send the reception acknowledgement to your vendor." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:710 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:706 msgid "Accept or claim the document and send this status to your vendor." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:713 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:709 msgid "Reception" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:715 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:711 msgid "As soon as the vendor email with the attached :abbr:`DTE (Documentos Tributarios Electrónicos)` is received:" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:718 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:714 msgid "The vendor bill maps all the information included in the XML." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:719 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:715 msgid "An email is sent to the vendor with the reception acknowledgement." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:720 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:716 msgid "The :guilabel:`DTE Status` is set as :guilabel:`Acuse de Recibido Enviado`." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:723 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:719 msgid "Acceptation" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:725 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:721 msgid "If all the commercial information is correct on your vendor bill, then you can accept the document using the :guilabel:`Aceptar Documento` button. Once this is done, the :guilabel:`DTE Acceptation Status` changes to :guilabel:`Accepted` and an email of acceptance is sent to the vendor." msgstr "" @@ -15139,11 +15124,11 @@ msgstr "" msgid "Button for accepting vendor bills." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:734 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:730 msgid "Claim" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:736 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:732 msgid "In case there is a commercial issue or the information is not correct on your vendor bill, you can claim the document before validating it, using the :guilabel:`Claim` button. Once this is done, the :guilabel:`DTE Acceptation Status` changes to :guilabel:`Claim` and a rejection email is sent to the vendor." msgstr "" @@ -15152,60 +15137,60 @@ msgid "Claim button in vendor bills to inform the vendor all the document is com "rejected." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:746 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:742 msgid "If you claim a vendor bill, the status changes from :guilabel:`Draft` to :guilabel:`Cancel` automatically. Considering this as best practice, all the claimed documents should be canceled as they won't be valid for your accounting records." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:751 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:747 #: ../../content/applications/finance/fiscal_localizations/mexico.rst:745 msgid "Delivery guide" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:753 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:749 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:758 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:754 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:762 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:758 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:766 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:762 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:772 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:768 msgid "Verify the following important information in the :guilabel:`Price for the Delivery Guide` configuration:" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:775 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:771 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:777 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:773 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:779 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:775 msgid ":guilabel:`No show price`: no price is shown in the delivery guide." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:781 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:777 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:785 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:781 msgid "Delivery guide from a sales process" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:788 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:784 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:790 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:786 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 "" @@ -15213,11 +15198,11 @@ msgstr "" msgid "Create Delivery Guide button on a sales process." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:798 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:794 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:801 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:797 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 "" @@ -15225,20 +15210,20 @@ msgstr "" msgid "First Delivery Guide number warning message." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:808 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:804 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:814 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:810 msgid "After the delivery guide is created:" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:816 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:812 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:818 -#: ../../content/applications/finance/fiscal_localizations/chile.rst:888 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:814 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:884 msgid "The :guilabel:`DTE SII Status` is set as :guilabel:`Pending to be sent`." msgstr "" @@ -15246,11 +15231,11 @@ msgstr "" msgid "Chatter notes of Delivery Guide creation." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:824 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:820 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:828 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:824 msgid "Once the delivery guide is sent, it may then be printed by clicking on the :guilabel:`Print Delivery Guide` button." msgstr "" @@ -15258,27 +15243,27 @@ msgstr "" msgid "Printing Delivery Guide PDF." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:835 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:831 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:841 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:837 msgid "Electronic receipt" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:843 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:839 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:848 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:844 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:852 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:848 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:858 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:854 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 "" @@ -15286,7 +15271,7 @@ msgstr "" msgid "Electronic Receipt module." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:867 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:863 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 "" @@ -15294,15 +15279,15 @@ msgstr "" msgid "Document type 39 for Electronic Receipts." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:879 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:875 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:884 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:880 msgid "After the receipt is posted:" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:886 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:882 msgid "The :abbr:`DTE (Documentos Tributarios Electrónicos)` file (Electronic Tax Document) is created automatically and added to the :guilabel:`chatter`." msgstr "" @@ -15310,35 +15295,35 @@ msgstr "" msgid "Electronic Receipts STE creation status." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:894 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:890 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:898 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:894 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:902 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:898 msgid "Electronic export of goods" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:904 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:900 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:909 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:905 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:912 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:908 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:918 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:914 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:923 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:919 msgid "Contact configurations" msgstr "" @@ -15346,11 +15331,11 @@ msgstr "" msgid "Taxpayer Type needed for the Electronic Exports of Goods module." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:930 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:926 msgid "Chilean customs" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:932 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:928 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 "" @@ -15358,11 +15343,11 @@ msgstr "" msgid "Chilean customs fields." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:940 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:936 msgid "PDF report" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:942 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:938 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 "" @@ -15370,15 +15355,15 @@ msgstr "" msgid "PDF report section for the Electronic Exports of Goods PDF Report." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:954 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:950 msgid "Balance tributario de 8 columnas" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:956 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:952 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:960 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:956 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 "" @@ -15390,19 +15375,19 @@ msgstr "" msgid "Chilean Fiscal Balance (8 Columns)." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:973 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:969 msgid "Propuesta F29" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:975 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:971 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:980 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:976 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:983 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:979 msgid "You can find this report in :menuselection:`Accounting --> Reporting --> Tax Reports` and selecting the :guilabel:`Report` option :guilabel:`Propuesta F29 (CL)`." msgstr "" @@ -15410,7 +15395,7 @@ msgstr "" msgid "Location of the Propuesta F29 (CL) Report." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:990 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:986 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 "" @@ -15418,7 +15403,7 @@ msgstr "" msgid "Default PPM and Proportional Factor for the Propuesta F29 Report." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/chile.rst:998 +#: ../../content/applications/finance/fiscal_localizations/chile.rst:994 msgid "Or manually in the reports by clicking on the :guilabel:`✏️ (pencil)` icon." msgstr "" @@ -16937,7 +16922,7 @@ msgstr "" #: ../../content/applications/finance/payment_providers/asiapay.rst:27 #: ../../content/applications/finance/payment_providers/buckaroo.rst:27 #: ../../content/applications/finance/payment_providers/flutterwave.rst:29 -#: ../../content/applications/finance/payment_providers/mercado_pago.rst:27 +#: ../../content/applications/finance/payment_providers/mercado_pago.rst:30 #: ../../content/applications/finance/payment_providers/razorpay.rst:29 msgid "Configuration on Odoo" msgstr "" @@ -18147,7 +18132,6 @@ msgid "The chart of accounts SKR03 and SKR04 are both supported in Odoo. You can msgstr "" #: ../../content/applications/finance/fiscal_localizations/germany.rst:12 -#: ../../content/applications/finance/fiscal_localizations/spain.rst:17 msgid "Be careful, you can only change the accounting package as long as you have not created any accounting entry." msgstr "" @@ -22272,7 +22256,7 @@ msgid "This generates the `Form_2307.xls` file that lists all the vendor bill li 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/multiple>` with applied withholding taxes." +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." msgstr "" #: ../../content/applications/finance/fiscal_localizations/philippines.rst:86 @@ -22656,11 +22640,11 @@ msgid "Spain" msgstr "" #: ../../content/applications/finance/fiscal_localizations/spain.rst:6 -msgid "Spanish Chart of Accounts" +msgid "Spanish chart of accounts" msgstr "" #: ../../content/applications/finance/fiscal_localizations/spain.rst:8 -msgid "In Odoo, there are several Spanish Chart of Accounts that are available by default:" +msgid "Several Spanish charts of accounts are available by default in Odoo:" msgstr "" #: ../../content/applications/finance/fiscal_localizations/spain.rst:10 @@ -22676,33 +22660,45 @@ msgid "PGCE Entitades" msgstr "" #: ../../content/applications/finance/fiscal_localizations/spain.rst:14 -msgid "You can choose the one you want by going in :menuselection:`Accounting --> Configuration` then choose the package you want in the **Fiscal Localization** section." +msgid "To choose the one you want, go to :menuselection:`Accounting --> Configuration --> Settings`, then select a package in the :guilabel:`Fiscal localization` section." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/spain.rst:20 +#: ../../content/applications/finance/fiscal_localizations/spain.rst:18 msgid "When you create a new Odoo Online database, the PGCE PYMEs 2008 is installed by default." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/spain.rst:23 -msgid "Spanish Accounting Reports" +#: ../../content/applications/finance/fiscal_localizations/spain.rst:21 +msgid "You can only change the accounting package as long as you have not created any accounting entry." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/spain.rst:25 -msgid "If the Spanish Accounting Localization is installed, you will have access to accounting reports specific to Spain:" +#: ../../content/applications/finance/fiscal_localizations/spain.rst:24 +msgid "Spanish accounting reports" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/spain.rst:28 -msgid "Tax Report (Modelo 111)" -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/spain.rst:29 -msgid "Tax Report (Modelo 115)" +#: ../../content/applications/finance/fiscal_localizations/spain.rst:26 +msgid "If the Spanish accounting localization is installed, you have access to accounting reports specific to Spain:" msgstr "" #: ../../content/applications/finance/fiscal_localizations/spain.rst:30 +msgid "Tax Report (Modelo 111)" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/spain.rst:31 +msgid "Tax Report (Modelo 115)" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/spain.rst:32 msgid "Tax Report (Modelo 303)" msgstr "" +#: ../../content/applications/finance/fiscal_localizations/spain.rst:33 +msgid "Tax Report (Modelo 347)" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/spain.rst:34 +msgid "Tax Report (Modelo 349)" +msgstr "" + #: ../../content/applications/finance/fiscal_localizations/switzerland.rst:3 msgid "Switzerland" msgstr "" @@ -24145,7 +24141,7 @@ msgstr "" #: ../../content/applications/finance/payment_providers/authorize.rst:51 #: ../../content/applications/finance/payment_providers/buckaroo.rst:37 #: ../../content/applications/finance/payment_providers/flutterwave.rst:44 -#: ../../content/applications/finance/payment_providers/mercado_pago.rst:36 +#: ../../content/applications/finance/payment_providers/mercado_pago.rst:39 #: ../../content/applications/finance/payment_providers/mollie.rst:31 #: ../../content/applications/finance/payment_providers/paypal.rst:161 #: ../../content/applications/finance/payment_providers/razorpay.rst:46 @@ -24446,7 +24442,7 @@ msgstr "" #: ../../content/applications/finance/payment_providers/amazon_payment_services.rst:44 #: ../../content/applications/finance/payment_providers/asiapay.rst:39 #: ../../content/applications/finance/payment_providers/flutterwave.rst:36 -#: ../../content/applications/finance/payment_providers/mercado_pago.rst:33 +#: ../../content/applications/finance/payment_providers/mercado_pago.rst:36 #: ../../content/applications/finance/payment_providers/razorpay.rst:36 msgid "Configure the rest of the options to your liking." msgstr "" @@ -24871,12 +24867,20 @@ msgstr "" msgid "If you are trying Mercado Pago as a test, select :guilabel:`Credienciales de prueba` in the left part of the application page, then copy the test :guilabel:`Access token`." msgstr "" -#: ../../content/applications/finance/payment_providers/mercado_pago.rst:29 +#: ../../content/applications/finance/payment_providers/mercado_pago.rst:-1 +msgid "Production and testing credentials in Mercado Pago." +msgstr "" + +#: ../../content/applications/finance/payment_providers/mercado_pago.rst:32 msgid ":ref:`Navigate to the payment provider Mercado Pago ` and change its state to :guilabel:`Enabled`." msgstr "" -#: ../../content/applications/finance/payment_providers/mercado_pago.rst:31 -msgid "In the :guilabel:`Credentials` tab, fill in the :guilabel:`Access Token` with the value you saved at the step :ref:`payment_providers/mercado_pago/configure_dashboard`." +#: ../../content/applications/finance/payment_providers/mercado_pago.rst:34 +msgid "In the :guilabel:`Credentials` tab, fill in the :guilabel:`Access Token` with the value you saved at the :ref:`payment_providers/mercado_pago/configure_dashboard` step." +msgstr "" + +#: ../../content/applications/finance/payment_providers/mercado_pago.rst:40 +msgid "`Mercado Pago Odoo webinar `_" msgstr "" #: ../../content/applications/finance/payment_providers/mollie.rst:3 diff --git a/locale/sources/general.pot b/locale/sources/general.pot index dd47ff3b9..f3eeba247 100644 --- a/locale/sources/general.pot +++ b/locale/sources/general.pot @@ -8,7 +8,7 @@ msgid "" msgstr "" "Project-Id-Version: Odoo saas-16.1\n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2023-12-19 13:26+0000\n" +"POT-Creation-Date: 2024-01-19 10:30+0000\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME \n" "Language-Team: LANGUAGE \n" @@ -3330,30 +3330,6 @@ msgstr "" msgid ":doc:`../../finance/accounting/get_started/multi_currency`" msgstr "" -#: ../../content/applications/general/users/delete_account.rst:3 -msgid "Deleting an Odoo.com Account" -msgstr "" - -#: ../../content/applications/general/users/delete_account.rst:5 -msgid "To delete your Odoo.com account, access the delete option by clicking on the user icon. The delete option can be accessed by going to :menuselection:`My Account --> Edit Security Settings --> Delete Account`. It can also be accessed by going to https://www.odoo.com/my/home." -msgstr "" - -#: ../../content/applications/general/users/delete_account.rst:10 -msgid "Deleting an Odoo account is irreversible. Take caution when performing this action as the Odoo.com account will not be retrievable." -msgstr "" - -#: ../../content/applications/general/users/delete_account.rst:13 -msgid "Upon clicking the :guilabel:`Delete Account` button, a pop-up window will appear, asking you to confirm the account deletion." -msgstr "" - -#: ../../content/applications/general/users/delete_account.rst:-1 -msgid "Clicking on the Delete Account button will populate a window verifying the change." -msgstr "" - -#: ../../content/applications/general/users/delete_account.rst:20 -msgid "Confirm the deletion by entering the :guilabel:`password` and the :guilabel:`login` for the account being deleted. Click the :guilabel:`Delete Account` button to confirm the deletion." -msgstr "" - #: ../../content/applications/general/users/language.rst:3 msgid "Change language" msgstr "" @@ -3574,91 +3550,184 @@ msgstr "" msgid ":doc:`companies`" msgstr "" +#: ../../content/applications/general/users/odoo_account.rst:3 +msgid "Odoo.com account changes" +msgstr "" + +#: ../../content/applications/general/users/odoo_account.rst:5 +msgid "This documentation is dedicated to edits made to an Odoo.com account. The following processes describe how to delete an Odoo.com account, and how to change the password on an Odoo.com account." +msgstr "" + +#: ../../content/applications/general/users/odoo_account.rst:9 +msgid "Delete Odoo.com account" +msgstr "" + +#: ../../content/applications/general/users/odoo_account.rst:11 +msgid "To delete an Odoo.com account, start by clicking the profile icon in the upper-right corner (represented by the username and icon) to reveal a drop-down menu. From the drop-down menu, select :guilabel:`My Odoo.com account`, which reveals the user portal." +msgstr "" + +#: ../../content/applications/general/users/odoo_account.rst:15 +msgid "From the user portal, the delete option can be accessed by going to :menuselection:`My Account --> Edit Security Settings --> Delete Account`. It can also be accessed by going to `https://www.odoo.com/my/home `_." +msgstr "" + +#: ../../content/applications/general/users/odoo_account.rst:20 +msgid "Deleting an Odoo account is irreversible. Be careful performing this action, as the Odoo.com account is **not** retrievable once deleted." +msgstr "" + +#: ../../content/applications/general/users/odoo_account.rst:23 +msgid "Upon clicking the :guilabel:`Delete Account` button, a pop-up window appears, requesting confirmation for the account deletion." +msgstr "" + +#: ../../content/applications/general/users/odoo_account.rst:-1 +msgid "Clicking on the Delete Account button will populate a window verifying the change." +msgstr "" + +#: ../../content/applications/general/users/odoo_account.rst:30 +msgid "To confirm the deletion, enter the :guilabel:`Password` and the :guilabel:`Login` for the account being deleted. Then, click the :guilabel:`Delete Account` button to confirm the deletion." +msgstr "" + +#: ../../content/applications/general/users/odoo_account.rst:34 +msgid "Odoo.com account password change" +msgstr "" + +#: ../../content/applications/general/users/odoo_account.rst:36 +msgid "To change an Odoo.com account password, first login into the Odoo.com user account from the Odoo.com login page. After logging-in, go to the upper-right corner of the screen, and click the :guilabel:`▼ (down arrow)` icon next to the profile icon. Then, select :guilabel:`My Account`, and a portal dashboard appears." +msgstr "" + +#: ../../content/applications/general/users/odoo_account.rst:41 +msgid "To change the Odoo.com password, click on the :guilabel:`Edit Security Settings` link, below the :menuselection:`Account Security` section. Next, make the necessary changes by typing in the current :guilabel:`Password`, :guilabel:`New Password`, and verify the new password. Lastly, click on :guilabel:`Change Password` to complete the password change." +msgstr "" + +#: ../../content/applications/general/users/odoo_account.rst:47 +msgid "If a customer would like to change the login, contact Odoo support `here `_." +msgstr "" + +#: ../../content/applications/general/users/odoo_account.rst:51 +msgid "Passwords for Odoo.com users and portal users remain separate, even if the same email address is used." +msgstr "" + +#: ../../content/applications/general/users/odoo_account.rst:55 +#: ../../content/applications/general/users/portal.rst:143 +msgid "Add two-factor authentication" +msgstr "" + +#: ../../content/applications/general/users/odoo_account.rst:57 +msgid "To add two-factor authentication, login into the Odoo.com user account from the Odoo.com login page. After logging-in, go to the upper-right corner of the screen, and click the :guilabel:`▼ (down arrow)` icon next to the :guilabel:`profile icon`. Then, select :guilabel:`My Account`, and a portal dashboard appears." +msgstr "" + +#: ../../content/applications/general/users/odoo_account.rst:62 +msgid "If the user would like to turn on two-factor authentication (2FA) for Odoo.com access, click on the :guilabel:`Edit Security Settings` link below the :menuselection:`Account Security` section." +msgstr "" + +#: ../../content/applications/general/users/odoo_account.rst:65 +msgid "Click on :guilabel:`Enable two-factor authentication` to turn on :abbr:`2FA (two-factor authentication)`. Then, confirm the current password in the :guilabel:`Password` field. Next, click on :guilabel:`Confirm Password`. Following that, activate :abbr:`2FA (two-factor authentication)` in a :abbr:`2FA (two-factor authentication)` app (Google Authenticator, Authy, etc.), by scanning the :guilabel:`QR code` or entering a :guilabel:`Verification Code`." +msgstr "" + +#: ../../content/applications/general/users/odoo_account.rst:71 +msgid "Finally, click on :guilabel:`Enable two-factor authentication` to complete the setup." +msgstr "" + +#: ../../content/applications/general/users/odoo_account.rst:74 +msgid "Under :guilabel:`My Account` Odoo.com users can also access the following:" +msgstr "" + +#: ../../content/applications/general/users/odoo_account.rst:76 +msgid ":guilabel:`My Partner dashboard`" +msgstr "" + +#: ../../content/applications/general/users/odoo_account.rst:77 +msgid ":guilabel:`My In-App Services`" +msgstr "" + +#: ../../content/applications/general/users/odoo_account.rst:78 +msgid ":guilabel:`My Apps Dashboard`" +msgstr "" + #: ../../content/applications/general/users/portal.rst:3 msgid "Portal access" msgstr "" -#: ../../content/applications/general/users/portal.rst:5 +#: ../../content/applications/general/users/portal.rst:7 msgid "Portal access is given to users who need the ability to view certain documents or information within an Odoo database." msgstr "" -#: ../../content/applications/general/users/portal.rst:8 +#: ../../content/applications/general/users/portal.rst:10 msgid "Some common use cases for providing portal access include allowing customers to read/view any or all of the following in Odoo:" msgstr "" -#: ../../content/applications/general/users/portal.rst:11 +#: ../../content/applications/general/users/portal.rst:13 msgid "leads/opportunities" msgstr "" -#: ../../content/applications/general/users/portal.rst:12 +#: ../../content/applications/general/users/portal.rst:14 msgid "quotations/sales orders" msgstr "" -#: ../../content/applications/general/users/portal.rst:13 +#: ../../content/applications/general/users/portal.rst:15 msgid "purchase orders" msgstr "" -#: ../../content/applications/general/users/portal.rst:14 +#: ../../content/applications/general/users/portal.rst:16 msgid "invoices & bills" msgstr "" -#: ../../content/applications/general/users/portal.rst:15 +#: ../../content/applications/general/users/portal.rst:17 msgid "projects" msgstr "" -#: ../../content/applications/general/users/portal.rst:16 +#: ../../content/applications/general/users/portal.rst:18 msgid "tasks" msgstr "" -#: ../../content/applications/general/users/portal.rst:17 +#: ../../content/applications/general/users/portal.rst:19 msgid "timesheets" msgstr "" -#: ../../content/applications/general/users/portal.rst:18 +#: ../../content/applications/general/users/portal.rst:20 msgid "tickets" msgstr "" -#: ../../content/applications/general/users/portal.rst:19 +#: ../../content/applications/general/users/portal.rst:21 msgid "signatures" msgstr "" -#: ../../content/applications/general/users/portal.rst:20 +#: ../../content/applications/general/users/portal.rst:22 msgid "subscriptions" msgstr "" -#: ../../content/applications/general/users/portal.rst:23 +#: ../../content/applications/general/users/portal.rst:25 msgid "Portal users only have read/view access, and will not be able to edit any documents in the database." msgstr "" -#: ../../content/applications/general/users/portal.rst:27 +#: ../../content/applications/general/users/portal.rst:29 msgid "Provide portal access to customers" msgstr "" -#: ../../content/applications/general/users/portal.rst:29 +#: ../../content/applications/general/users/portal.rst:31 msgid "From the main Odoo dashboard, select the :guilabel:`Contacts` application. If the contact is not yet created in the database, click on the :guilabel:`Create` button, enter the details of the contact, and then click :guilabel:`Save`. Otherwise, choose an existing contact, and then click on the :guilabel:`Action` drop-down menu located at the top-center of the interface." msgstr "" #: ../../content/applications/general/users/portal.rst:-1 -msgid "Use the Contacts application to give portal access to users" -msgstr "" - -#: ../../content/applications/general/users/portal.rst:38 -msgid "Then select :guilabel:`Grant portal access`. A pop-up window appears, listing three fields:" +msgid "Use the Contacts application to give portal access to users." msgstr "" #: ../../content/applications/general/users/portal.rst:40 -msgid ":guilabel:`Contact`: the recorded name of the contact in the Odoo database" -msgstr "" - -#: ../../content/applications/general/users/portal.rst:41 -msgid ":guilabel:`Email`: the contact's email address that they will use to log into the portal" +msgid "Then select :guilabel:`Grant portal access`. A pop-up window appears, listing three fields:" msgstr "" #: ../../content/applications/general/users/portal.rst:42 -msgid ":guilabel:`In Portal`: whether or not the user has portal access" +msgid ":guilabel:`Contact`: the recorded name of the contact in the Odoo database" +msgstr "" + +#: ../../content/applications/general/users/portal.rst:43 +msgid ":guilabel:`Email`: the contact's email address that they will use to log into the portal" msgstr "" #: ../../content/applications/general/users/portal.rst:44 +msgid ":guilabel:`In Portal`: whether or not the user has portal access" +msgstr "" + +#: ../../content/applications/general/users/portal.rst:46 msgid "To grant portal access, first enter the contact's :guilabel:`Email` they will use to log into the portal. Then, check the box under the :guilabel:`In Portal` column. Optionally, add text to the invitation message the contact will receive. Then click :guilabel:`Apply` to finish." msgstr "" @@ -3667,18 +3736,112 @@ msgid "An email address and corresponding checkbox for the contact need to be fi "sending a portal invitation." msgstr "" -#: ../../content/applications/general/users/portal.rst:53 +#: ../../content/applications/general/users/portal.rst:55 msgid "An email will be sent to the specified email address, indicating that the contact is now a portal user for that Odoo database." msgstr "" -#: ../../content/applications/general/users/portal.rst:57 +#: ../../content/applications/general/users/portal.rst:59 msgid "To grant portal access to multiple users at once, navigate to a company contact, then click :menuselection:`Action --> Grant portal access` to view a list of all of the company's related contacts. Check the box under the :guilabel:`In Portal` column for all the contacts that need portal access, then click :guilabel:`Apply`." msgstr "" -#: ../../content/applications/general/users/portal.rst:63 +#: ../../content/applications/general/users/portal.rst:65 msgid "At any time, portal access can be revoked by navigating to the contact, clicking :menuselection:`Action --> Grant portal access`, and then unselecting the checkbox under the :guilabel:`In Portal` column and clicking :guilabel:`Apply`." msgstr "" +#: ../../content/applications/general/users/portal.rst:72 +msgid "Change portal username" +msgstr "" + +#: ../../content/applications/general/users/portal.rst:74 +msgid "There may be times when a portal user wants to change their user login. This can be done by any user in the database with administrator access rights. The following process outlines the necessary steps to change the portal user login." +msgstr "" + +#: ../../content/applications/general/users/portal.rst:79 +msgid ":doc:`See the documentation on setting access rights `." +msgstr "" + +#: ../../content/applications/general/users/portal.rst:82 +msgid "First, navigate to :menuselection:`Settings app --> Users`. Then, under :guilabel:`Filters`, select :guilabel:`Portal Users`, or select :guilabel:`Add Custom Filter` and set the following configuration :guilabel:`Groups` > :guilabel:`contains` > `portal`. After making this selection, search for (and open) the portal user that needs to be edited." +msgstr "" + +#: ../../content/applications/general/users/portal.rst:87 +msgid "Next, click :guilabel:`Edit` (if necessary), click into the :guilabel:`Email Address` field, and proceed to make any necessary changes to this field. The :guilabel:`Email Address` field is used to log into the Odoo portal." +msgstr "" + +#: ../../content/applications/general/users/portal.rst:92 +msgid "Changing the :guilabel:`Email Address` (or login) only changes the *username* on the customer's portal login." +msgstr "" + +#: ../../content/applications/general/users/portal.rst:95 +msgid "In order to change the contact email, this change needs to take place on the contact template in the *Contacts* app. Alternatively, the customer can change their email directly from the portal, but the login **cannot** be changed. :ref:`See change customer info `." +msgstr "" + +#: ../../content/applications/general/users/portal.rst:100 +msgid "Customer portal changes" +msgstr "" + +#: ../../content/applications/general/users/portal.rst:102 +msgid "There may be times when the customer would like to make changes to their contact information, password/security, or payment information attached to the portal account. This can be performed by the customer from their portal. The following process is how a customer can change their contact information." +msgstr "" + +#: ../../content/applications/general/users/portal.rst:110 +msgid "Change customer info" +msgstr "" + +#: ../../content/applications/general/users/portal.rst:112 +msgid "First enter the username and password (login) into the database login page to access the portal user account. A portal dashboard will appear upon successfully logging in. Portal documents from the various installed Odoo applications will appear with the number count of each." +msgstr "" + +#: ../../content/applications/general/users/portal.rst:117 +msgid ":ref:`Portal access documentation `." +msgstr "" + +#: ../../content/applications/general/users/portal.rst:119 +msgid "Next, navigate to the upper-right corner of the portal, and click the :guilabel:`Edit` button, next to the :guilabel:`Details` section. Then, change the pertinent information, and click :guilabel:`Confirm`." +msgstr "" + +#: ../../content/applications/general/users/portal.rst:124 +msgid "Change password" +msgstr "" + +#: ../../content/applications/general/users/portal.rst:126 +#: ../../content/applications/general/users/portal.rst:145 +#: ../../content/applications/general/users/portal.rst:162 +msgid "First enter the username and password (login) into the database login page to access the portal user account. A portal dashboard will appear upon successfully logging in." +msgstr "" + +#: ../../content/applications/general/users/portal.rst:129 +msgid "If the customer would like to change their password for portal access, click on the :guilabel:`Edit Security Settings` link, below the :guilabel:`Account Security` section. Then, make the necessary changes, by typing in the current :guilabel:`Password`, :guilabel:`New Password`, and verify the new password. Lastly, click on :guilabel:`Change Password` to complete the password change." +msgstr "" + +#: ../../content/applications/general/users/portal.rst:135 +msgid "If a customer would like to change the login, as documented above, contact the Odoo database point-of-contact. :ref:`See above documentation on changing the portal username `." +msgstr "" + +#: ../../content/applications/general/users/portal.rst:139 +msgid "Passwords for portal users and Odoo.com users remain separate, even if the same email address is used." +msgstr "" + +#: ../../content/applications/general/users/portal.rst:148 +msgid "If the customer would like to turn on two-factor authentication (2FA) for portal access, click on the :guilabel:`Edit Security Settings` link, below the :guilabel:`Account Security` section." +msgstr "" + +#: ../../content/applications/general/users/portal.rst:151 +msgid "Click on :guilabel:`Enable two-factor authentication` to turn on :abbr:`2FA (two-factor authentication)`. Confirm the current portal password in the :guilabel:`Password` field. Then, click on :guilabel:`Confirm Password`. Next, activate :abbr:`2FA (two-factor authentication)` in a :abbr:`2FA (two-factor authentication)` app (Google Authenticator, Authy, etc.), by scanning the :guilabel:`QR code` or entering a :guilabel:`Verification Code`." +msgstr "" + +#: ../../content/applications/general/users/portal.rst:157 +msgid "Finally, click :guilabel:`Enable two-factor authentication` to complete the setup." +msgstr "" + +#: ../../content/applications/general/users/portal.rst:160 +msgid "Change payment info" +msgstr "" + +#: ../../content/applications/general/users/portal.rst:165 +msgid "If the customer would like to manage payment options, navigate to the :guilabel:`Manage payment methods` in the menu on the right. Then, add the new payment information, and select :guilabel:`Add new card`." +msgstr "" + #: ../../content/applications/general/voip.rst:5 msgid "VoIP (Voice over Internet Protocol)" msgstr "" diff --git a/locale/sources/hr.pot b/locale/sources/hr.pot index 56ef9b63e..ba40195b9 100644 --- a/locale/sources/hr.pot +++ b/locale/sources/hr.pot @@ -8,7 +8,7 @@ msgid "" msgstr "" "Project-Id-Version: Odoo saas-16.1\n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2023-12-19 13:26+0000\n" +"POT-Creation-Date: 2024-01-19 10:30+0000\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME \n" "Language-Team: LANGUAGE \n" @@ -110,390 +110,1253 @@ msgid "Odoo *Employees* organizes a company's employee records, contracts, and d msgstr "" #: ../../content/applications/hr/employees/new_employee.rst:3 -msgid "Add a new employee" +msgid "Create a new employee" msgstr "" #: ../../content/applications/hr/employees/new_employee.rst:5 -msgid "When a new employee is hired, the first step is to create a new employee form. Starting in the :menuselection:`Employees` app dashboard, click the :guilabel:`Create` button to create a new employee form. Fill out the required information (underlined in bold) and any additional details, then click :guilabel:`Save`." +msgid "When a new employee is hired, the first step is to create a new employee record. Starting in the :menuselection:`Employees` app dashboard, click the :guilabel:`New` button and a new employee form appears. Fill out the required information and any additional details." msgstr "" #: ../../content/applications/hr/employees/new_employee.rst:-1 -msgid "Create a new employee card." +msgid "Create a new employee form with all fields filled out." msgstr "" -#: ../../content/applications/hr/employees/new_employee.rst:15 +#: ../../content/applications/hr/employees/new_employee.rst:14 msgid "The current company phone number and name is populated in the :guilabel:`Work Phone` and :guilabel:`Company` fields." msgstr "" -#: ../../content/applications/hr/employees/new_employee.rst:19 +#: ../../content/applications/hr/employees/new_employee.rst:18 msgid "General information" msgstr "" -#: ../../content/applications/hr/employees/new_employee.rst:22 +#: ../../content/applications/hr/employees/new_employee.rst:20 +msgid "The employee form automatically saves as data is entered, but the save manually icon (a could with an up arrow inside it) may be clicked at any time to manually save the form." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:24 #: ../../content/applications/hr/payroll/contracts.rst:39 #: ../../content/applications/hr/payroll/payslips.rst:51 msgid "Required fields" msgstr "" -#: ../../content/applications/hr/employees/new_employee.rst:24 +#: ../../content/applications/hr/employees/new_employee.rst:26 msgid ":guilabel:`Name`: Enter the employee's name." msgstr "" -#: ../../content/applications/hr/employees/new_employee.rst:25 +#: ../../content/applications/hr/employees/new_employee.rst:27 msgid ":guilabel:`Company`: Select the company from the drop-down menu that the new employee is hired by, or create a new company by typing the name in the field." msgstr "" -#: ../../content/applications/hr/employees/new_employee.rst:33 -#: ../../content/applications/hr/payroll/contracts.rst:66 -#: ../../content/applications/hr/payroll/payslips.rst:91 -msgid "Optional fields" +#: ../../content/applications/hr/employees/new_employee.rst:-1 +msgid "A new employee form with the required fields highlighted." msgstr "" #: ../../content/applications/hr/employees/new_employee.rst:35 -msgid ":guilabel:`Photo`: In the top right image box of the employee card, click on the :guilabel:`✏️ (pencil)` edit icon to select a photo to upload." +#: ../../content/applications/hr/payroll/contracts.rst:66 +#: ../../content/applications/hr/payroll/payslips.rst:91 +#: ../../content/applications/hr/recruitment.rst:737 +msgid "Optional fields" msgstr "" #: ../../content/applications/hr/employees/new_employee.rst:37 -msgid ":guilabel:`Job Position`: Enter the employee's job position title." +msgid ":guilabel:`Photo`: In the top right image box of the employee form, click on the :guilabel:`✏️ (pencil)` edit icon to select a photo to upload." msgstr "" -#: ../../content/applications/hr/employees/new_employee.rst:38 -msgid "Tags: Click on a tag in the drop-down menu to add any tags applicable to the employee. Any tag can be created in this field by typing it in. Once created, the new tag is available for all employee cards. There is no limit to the amount of tags that can be added." -msgstr "" - -#: ../../content/applications/hr/employees/new_employee.rst:41 -msgid "Work Contact Information: Enter the employees :guilabel:`Work Mobile`, :guilabel:`Work Phone`, :guilabel:`Work Email`, and/or :guilabel:`Company` name." -msgstr "" - -#: ../../content/applications/hr/employees/new_employee.rst:43 -msgid ":guilabel:`Department`: Select the employee's department from the drop-down menu." -msgstr "" - -#: ../../content/applications/hr/employees/new_employee.rst:44 -msgid ":guilabel:`Manager`: Select the employee's manager from the drop-down menu." +#: ../../content/applications/hr/employees/new_employee.rst:39 +msgid ":guilabel:`Job Position`: Enter the employee's job position title under their name, or select the job position from the :guilabel:`Job Position` drop-down menu to have this field auto-populate. The :guilabel:`Job Position` field under the employee name can be modified and does not need to match the selection made in the :guilabel:`Job Position` drop-down." msgstr "" #: ../../content/applications/hr/employees/new_employee.rst:45 -msgid ":guilabel:`Coach`: Select the employee's coach from the drop-down menu." +msgid "It is recommended to have the job positions match, but if desired, the typed-in description in this field can contain more information than the selected drop-down job position." msgstr "" #: ../../content/applications/hr/employees/new_employee.rst:48 -msgid "After a :guilabel:`Manager` is selected, if the :guilabel:`Coach` field is blank, the selected manager automatically populates the :guilabel:`Coach` field." +msgid "An example where this may be applicable is if someone is hired for a sales representative position configured as :guilabel:`Sales Representative` in the *Recruitment* app, and that is selected for the drop-down :guilabel:`Job Position` field." msgstr "" #: ../../content/applications/hr/employees/new_employee.rst:52 -msgid "To make edits to the selected :guilabel:`Department`, :guilabel:`Manager`, :guilabel:`Coach`, or :guilabel:`Company`, click the :guilabel:`External Link` button next to the respective selection. The :guilabel:`External Link` button opens the selected form, allowing for modifications. Click :guilabel:`Save` after any edits are made." +msgid "In the typed in job position field beneath the employee's name, the position could be more specific, such as `Sales Representative - Subscriptions` if the employee is focused solely on subscription sales." msgstr "" -#: ../../content/applications/hr/employees/new_employee.rst:58 -msgid "Additional information tabs" +#: ../../content/applications/hr/employees/new_employee.rst:0 +msgid "Both job position fields entered but with different information." msgstr "" -#: ../../content/applications/hr/employees/new_employee.rst:61 -msgid "Resumé tab" +#: ../../content/applications/hr/employees/new_employee.rst:60 +msgid "Tags: Click on a tag in the drop-down menu to add any tags applicable to the employee. Any tag can be created in this field by typing it in. Once created, the new tag is available for all employee records. There is no limit to the amount of tags that can be added." msgstr "" -#: ../../content/applications/hr/employees/new_employee.rst:64 -msgid "Resumé" +#: ../../content/applications/hr/employees/new_employee.rst:63 +msgid "Work Contact Information: Enter the employee's :guilabel:`Work Mobile`, :guilabel:`Work Phone`, :guilabel:`Work Email`, and/or :guilabel:`Company` name." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:65 +msgid ":guilabel:`Department`: Select the employee's department from the drop-down menu." msgstr "" #: ../../content/applications/hr/employees/new_employee.rst:66 -msgid "Next, enter the employee's work history in the :guilabel:`Resumé` tab. Each resumé line must be entered individually. Click :guilabel:`Create a New Entry`, and the :guilabel:`Create Resumé lines` form appears. Enter the following information for each entry." +msgid ":guilabel:`Job Position`: Select the employee's job position from the drop-down menu. Once a selection is made, the :guilabel:`Job Position` field beneath the employee's name automatically updates to reflect the currently selected job position. These positions are from the :doc:`Recruitment <../../hr/recruitment/new_job/>` application, and reflect the currently \\ configured job positions." msgstr "" -#: ../../content/applications/hr/employees/new_employee.rst:-1 -msgid "Add information for the previous work experience in this form." +#: ../../content/applications/hr/employees/new_employee.rst:71 +msgid ":guilabel:`Manager`: Select the employee's manager from the drop-down menu." msgstr "" -#: ../../content/applications/hr/employees/new_employee.rst:74 -msgid ":guilabel:`Title`: Type in the title of the previous work experience." +#: ../../content/applications/hr/employees/new_employee.rst:72 +msgid ":guilabel:`Coach`: Select the employee's coach from the drop-down menu." msgstr "" -#: ../../content/applications/hr/employees/new_employee.rst:75 -msgid ":guilabel:`Type`: From the drop-down menu, select either :guilabel:`Experience`, :guilabel:`Education`, :guilabel:`Internal Certification`, :guilabel:`Internal Training`, or type in a new entry." +#: ../../content/applications/hr/employees/new_employee.rst:73 +msgid ":guilabel:`Next Appraisal Date`: This date automatically populates with a date that is computed according to the settings configured in the *Appraisals* application. This date can be modified using the calendar selector." msgstr "" #: ../../content/applications/hr/employees/new_employee.rst:78 -msgid ":guilabel:`Display Type`: Select either :guilabel:`Classic`, :guilabel:`Certification`, or :guilabel:`Course` from the drop-down menu." +msgid "After a :guilabel:`Manager` is selected, if the :guilabel:`Coach` field is blank, the selected manager automatically populates the :guilabel:`Coach` field." msgstr "" -#: ../../content/applications/hr/employees/new_employee.rst:80 -msgid ":guilabel:`Date Start` and :guilabel:`Date End`: Enter the start and end dates for the work experience. To select a date, use the :guilabel:`< (left)` and :guilabel:`> (right)` arrow icons to scroll to the desired month, then click on the day to select it." +#: ../../content/applications/hr/employees/new_employee.rst:82 +msgid "To make edits to the selected :guilabel:`Department`, :guilabel:`Manager`, :guilabel:`Coach`, or :guilabel:`Company`, click the :guilabel:`Internal Link` arrow next to the respective selection. The :guilabel:`Internal Link` arrow opens the selected form, allowing for modifications. Click :guilabel:`Save` after any edits are made." msgstr "" -#: ../../content/applications/hr/employees/new_employee.rst:83 -msgid ":guilabel:`Description`: Enter any relevant details in the field." +#: ../../content/applications/hr/employees/new_employee.rst:88 +msgid "Additional information tabs" msgstr "" -#: ../../content/applications/hr/employees/new_employee.rst:85 -msgid "Once all the information is entered, click the :guilabel:`Save & Close` button if there is only one entry to add, or click the :guilabel:`Save & New` button to save the current entry and create another resumé line." +#: ../../content/applications/hr/employees/new_employee.rst:91 +msgid "Resumé tab" msgstr "" -#: ../../content/applications/hr/employees/new_employee.rst:90 -msgid "After the new employee form is saved, the current position and company is automatically added to the :guilabel:`Resumé` tab as :guilabel:`Experience`, with the end date listed as :guilabel:`Current`." +#: ../../content/applications/hr/employees/new_employee.rst:94 +msgid "Resumé" msgstr "" -#: ../../content/applications/hr/employees/new_employee.rst:95 -msgid "Skills" -msgstr "" - -#: ../../content/applications/hr/employees/new_employee.rst:97 -msgid "An employee's skills can be entered in the :guilabel:`Resumé` tab in the same manner a resumé line is created. Click the :guilabel:`Create a New Entry` button under :guilabel:`Skills` and a :guilabel:`Create Skills` form appears. Fill in the information on the form." +#: ../../content/applications/hr/employees/new_employee.rst:96 +msgid "Next, enter the employee's work history in the :guilabel:`Resumé` tab. Each resumé line must be entered individually. When creating an entry for the first time, click :guilabel:`Create a new entry`, and the :guilabel:`Create Resumé lines` form appears. After an entry is added, the :guilabel:`Create a new entry` button is replaced with an :guilabel:`Add` button. Enter the following information for each entry." msgstr "" #: ../../content/applications/hr/employees/new_employee.rst:-1 -msgid "Create a new skill for the employee." +msgid "A resumé entry form with all the information populated." msgstr "" -#: ../../content/applications/hr/employees/new_employee.rst:105 -msgid ":guilabel:`Skill Type`: Select a :ref:`skill type ` by clicking the radio button next to the skill type." +#: ../../content/applications/hr/employees/new_employee.rst:106 +msgid ":guilabel:`Title`: Type in the title of the previous work experience." msgstr "" #: ../../content/applications/hr/employees/new_employee.rst:107 -msgid ":guilabel:`Skill`: The corresponding skills associated with the selected :guilabel:`Skill Type` appear in a drop-down menu. For example, selecting :guilabel:`Language` as the :guilabel:`Skill Type` presents a variety of languages to select from under the :guilabel:`Skills` field. Select the appropriate pre-configured skill, or type in a new one." +msgid ":guilabel:`Type`: From the drop-down menu, select either :guilabel:`Experience`, :guilabel:`Education`, :guilabel:`Side Projects`, :guilabel:`Internal Certification`, :guilabel:`Completed Internal Training`, or type in a new entry, then click :guilabel:`Create \"(new entry)\"`." msgstr "" #: ../../content/applications/hr/employees/new_employee.rst:111 -msgid ":guilabel:`Skill Level`: Pre-defined skill levels associated with the selected :guilabel:`Skill Type` appear in a drop-down menu. Select a skill level, then the progress bar automatically displays the pre-defined progress for that skill level. Skill levels and progress can be modified in the :guilabel:`Skill Level` pop-up form, which is accessed via the :guilabel:`External Link` button next to :guilabel:`Skill Level` field." +msgid ":guilabel:`Display Type`: Select either :guilabel:`Classic`, :guilabel:`Certification`, or :guilabel:`Course` from the drop-down menu." msgstr "" -#: ../../content/applications/hr/employees/new_employee.rst:117 -msgid "Once all the information is entered, click the :guilabel:`Save & Close` button if there is only one entry to add, or click the :guilabel:`Save & New` button to save the current entry and create another skill." +#: ../../content/applications/hr/employees/new_employee.rst:113 +msgid ":guilabel:`Date Start` and :guilabel:`Date End`: Enter the start and end dates for the work experience. To select a date, use the :guilabel:`< (left)` and :guilabel:`> (right)` arrow icons to scroll to the desired month, then click on the day to select it." msgstr "" -#: ../../content/applications/hr/employees/new_employee.rst:121 -msgid "To delete any line from the :guilabel:`Resumé` tab, click the :guilabel:`🗑️ (trash can)` icon to delete the entry. Add a new line by clicking the :guilabel:`Add` button next to the corresponding section." +#: ../../content/applications/hr/employees/new_employee.rst:116 +msgid ":guilabel:`Description`: Enter any relevant details in the field." msgstr "" -#: ../../content/applications/hr/employees/new_employee.rst:128 -msgid "Skill types" +#: ../../content/applications/hr/employees/new_employee.rst:118 +msgid "Once all the information is entered, click the :guilabel:`Save & Close` button if there is only one entry to add, or click the :guilabel:`Save & New` button to save the current entry and create another resumé line." msgstr "" -#: ../../content/applications/hr/employees/new_employee.rst:130 -msgid "In order to add a skill to an employee's form, the :guilabel:`Skill Types` must be configured. Go to :menuselection:`Employees app --> Configuration --> Skill Types` to view the currently configured skill types and create new skill types. Click :guilabel:`Create` and a new :guilabel:`Skill Type` form appears. Fill out all the details and then click :guilabel:`Save`. Repeat this for all the skill types needed." +#: ../../content/applications/hr/employees/new_employee.rst:123 +msgid "After the new employee form is saved, the current position and company is automatically added to the :guilabel:`Resumé` tab, with the end date listed as *current*." msgstr "" -#: ../../content/applications/hr/employees/new_employee.rst:136 -msgid ":guilabel:`Skill Type`: Enter the name of the skill type. This should be somewhat generic, since the specific skills listed will be housed under this category." +#: ../../content/applications/hr/employees/new_employee.rst:127 +msgid "Skills" msgstr "" -#: ../../content/applications/hr/employees/new_employee.rst:138 -msgid ":guilabel:`Skills`: Click :guilabel:`Add a line` and enter the information for the new skill, then repeat for all other needed skills." -msgstr "" - -#: ../../content/applications/hr/employees/new_employee.rst:140 -msgid ":guilabel:`Levels`: Click :guilabel:`Add a line` and a :guilabel:`Create Levels` form appears. Enter the name of the level, and assign a percentage (0-100) for that level. Click :guilabel:`Save & New` to save the entry and add another level, or click :guilabel:`Save & Close` to save the level and close the form." -msgstr "" - -#: ../../content/applications/hr/employees/new_employee.rst:146 -msgid "To add a math skill set, enter `Math` in the :guilabel:`Name` field. Next, in the :guilabel:`Skills` field, enter `Algebra`, `Calculus`, and `Trigonometry`. Last, in the :guilabel:`Levels` field enter `Beginner`, `Intermediate`, and `Expert`, with the :guilabel:`Progress` listed as `25`, `50`, and `100`, respectively. Then, either click :guilabel:`Save & Close` or :guilabel:`Save & New`." -msgstr "" - -#: ../../content/applications/hr/employees/new_employee.rst:0 -msgid "Add new math skills and levels with the skill types form." -msgstr "" - -#: ../../content/applications/hr/employees/new_employee.rst:157 -msgid "Work information tab" -msgstr "" - -#: ../../content/applications/hr/employees/new_employee.rst:159 -msgid "The :guilabel:`Work Information` tab is where the employee's specific job related information is housed. Their working schedule, various roles, who approves their specific requests (time off, timesheets, and expenses), and specific work location details are listed here. Enter the following information for the new employee." -msgstr "" - -#: ../../content/applications/hr/employees/new_employee.rst:164 -msgid ":guilabel:`Location`: Select the :guilabel:`Work Address` and :guilabel:`Work Location` from the corresponding drop-down menus. The work address :guilabel:`External Link` button opens up the selected company form in a window, and allows for editing. The :guilabel:`Work Location` is the specific location details, such as a floor or building. If a new work location is needed, add the location by typing it in the field." -msgstr "" - -#: ../../content/applications/hr/employees/new_employee.rst:169 -msgid ":guilabel:`Approvers`: Using the drop-down menus, select the users responsible for approving :guilabel:`Time Off`, :guilabel:`Expenses`, and :guilabel:`Timesheets` for the employee. The :guilabel:`External Link` button opens a form with the approver's :guilabel:`Name`, :guilabel:`Email Address`, :guilabel:`Company`, :guilabel:`Phone`, and :guilabel:`Mobile` fields. These can be modified, if needed. Click :guilabel:`Save` after making any edits." -msgstr "" - -#: ../../content/applications/hr/employees/new_employee.rst:174 -msgid ":guilabel:`Schedule`: Select the :guilabel:`Working Hours` and :guilabel:`Timezone` (both required) for the employee. The :guilabel:`External Link` button opens up a detailed view of the specific daily working hours. Working hours can be modified or deleted here. Click :guilabel:`Save` to save any changes." -msgstr "" - -#: ../../content/applications/hr/employees/new_employee.rst:178 -msgid ":guilabel:`Planning`: The :guilabel:`Planning` section affects the *Planning* app, and will only appear if the *Planning* app is installed. Click on a planning role from the drop-down menu for both the :guilabel:`Default Planning Role` and the :guilabel:`Planning Roles` fields to add a role. There is no limit to the amount of :guilabel:`Planning Roles` that can be selected for an employee, but there can only be one :guilabel:`Default Planning Role`. The default is the *typical* role that the employee performs, where the :guilabel:`Planning Roles` are *all* the specific roles the employee is able to perform." -msgstr "" - -#: ../../content/applications/hr/employees/new_employee.rst:0 -msgid "Add the work information to the Work Information tab." -msgstr "" - -#: ../../content/applications/hr/employees/new_employee.rst:191 -msgid "The users that appear in the drop-down menu for the :guilabel:`Approvers` section must have *Administrator* rights set for the corresponding human resources role. To check who has these rights, go to :menuselection:`Settings app --> Users --> Manage Users`. Click on an employee, and check the :guilabel:`Human Resources` section of the :guilabel:`Access Rights` tab." -msgstr "" - -#: ../../content/applications/hr/employees/new_employee.rst:196 -msgid "In order for the user to appear as an approver for :guilabel:`Expenses`, they must have either :guilabel:`Team Approver`, :guilabel:`All Approver`, or :guilabel:`Administrator` set for the :guilabel:`Expenses` role." -msgstr "" - -#: ../../content/applications/hr/employees/new_employee.rst:199 -msgid "In order for the user to appear as an approver for :guilabel:`Time Off`, they must have either :guilabel:`Officer` or :guilabel:`Administrator` set for the :guilabel:`Time Off` role." -msgstr "" - -#: ../../content/applications/hr/employees/new_employee.rst:201 -msgid "In order for the user to appear as an approver for :guilabel:`Timesheets`, they must have either :guilabel:`Manager`, :guilabel:`Officer`, or :guilabel:`Administrator` set for the :guilabel:`Payroll` role." -msgstr "" - -#: ../../content/applications/hr/employees/new_employee.rst:206 -msgid ":guilabel:`Working Hours` are related to a company's working times, and an employee cannot have working hours that are outside of a company's working times." -msgstr "" - -#: ../../content/applications/hr/employees/new_employee.rst:209 -msgid "Each individual working time is company-specific, so for multi-company databases, each company needs to have its own working hours set." -msgstr "" - -#: ../../content/applications/hr/employees/new_employee.rst:212 -msgid "If an employee's working hours are not configured as a working time for the company, new working times can be added, or existing working times can be modified. To add or modify a working time, go to the :menuselection:`Payroll app --> Configuration --> Working Times`, and add a new working time or edit an existing one." -msgstr "" - -#: ../../content/applications/hr/employees/new_employee.rst:217 -msgid "After the new working time is created, set the working hours for the employee." -msgstr "" - -#: ../../content/applications/hr/employees/new_employee.rst:220 -msgid "Private information tab" -msgstr "" - -#: ../../content/applications/hr/employees/new_employee.rst:222 -msgid "No information in the :guilabel:`Private Information` tab is required, however, some information in this section may be critical for the company's payroll department. In order to properly process payslips and ensure all deductions are accounted for, the employee's personal information should be entered." -msgstr "" - -#: ../../content/applications/hr/employees/new_employee.rst:227 -msgid "Here, the employee's :guilabel:`Private Contact`, :guilabel:`Marital Status`, :guilabel:`Emergency Contact`, :guilabel:`Education`, :guilabel:`Citizenship`, :guilabel:`Dependant`, and :guilabel:`Work Permit` information is entered. Fields are entered either using a drop-down menu, clicking a check box, or typing in the information." -msgstr "" - -#: ../../content/applications/hr/employees/new_employee.rst:232 -msgid ":guilabel:`Private Contact`: Enter the personal :guilabel:`Address` for the employee. The selection can be made with the drop-down menu. If the information is not available, type in the name for the new address. To edit the new address, click the :guilabel:`External Link` button to open the address form. On the address form, enter the necessary details, then click :guilabel:`Save`" -msgstr "" - -#: ../../content/applications/hr/employees/new_employee.rst:238 -msgid "Some other information in the :guilabel:`Private Contact` section may auto-populate, if the address is already listed in the drop-down menu." -msgstr "" - -#: ../../content/applications/hr/employees/new_employee.rst:241 -msgid "Next, enter the employee's :guilabel:`Email` address and :guilabel:`Phone` number in the corresponding fields." -msgstr "" - -#: ../../content/applications/hr/employees/new_employee.rst:244 -msgid "Select the employee's preferred :guilabel:`Language` from the drop-down menu." -msgstr "" - -#: ../../content/applications/hr/employees/new_employee.rst:246 -msgid "Enter the employee's :guilabel:`Bank Account Number` using the drop-down menu. If the bank is not already configured (the typical situation when creating a new employee) enter the bank account number, and click :guilabel:`Create and Edit`. A :guilabel:`Create: Bank Account Number` for appears. Fill in the information, then click :guilabel:`Save`." -msgstr "" - -#: ../../content/applications/hr/employees/new_employee.rst:251 -msgid "Finally, enter the :guilabel:`Home-Work Distance` in the field. This field is only necessary if the employee is receiving any type of commuter benefits." -msgstr "" - -#: ../../content/applications/hr/employees/new_employee.rst:254 -msgid ":guilabel:`Marital Status`: Select either :guilabel:`Single`, :guilabel:`Married`, :guilabel:`Legal Cohabitant`, :guilabel:`Widower`, or :guilabel:`Divorced` from the drop-down menu." -msgstr "" - -#: ../../content/applications/hr/employees/new_employee.rst:257 -msgid ":guilabel:`Emergency`: Type in the name and phone number of the employee's emergency contact." -msgstr "" - -#: ../../content/applications/hr/employees/new_employee.rst:258 -msgid ":guilabel:`Education`: Select the highest level of education completed by the employee from the :guilabel:`Certificate Level` drop-down menu. Options include :guilabel:`Graduate`, :guilabel:`Bachelor`, :guilabel:`Master`, :guilabel:`Doctor`, or :guilabel:`Other`. Type in the :guilabel:`Field of Study`, and the name of the :guilabel:`School` in the respective fields." -msgstr "" - -#: ../../content/applications/hr/employees/new_employee.rst:262 -msgid ":guilabel:`Citizenship`: This section houses all the information relevant to the citizenship of the employee. Some selections use a drop-down menu, as does the :guilabel:`Nationality (Country)`, :guilabel:`Gender`, and :guilabel:`Country of Birth` sections. The :guilabel:`Date of Birth` uses a calendar module to select the date. First, click on the name of the month, then the year, to access the year ranges. Use the :guilabel:`< (left)` and :guilabel:`> (right)` arrow icons, navigate to the correct year range, and click on the year. Next, click on the month. Last, click on the day to select the date. Type in the information for the :guilabel:`Identification No`, :guilabel:`Passport No`, and :guilabel:`Place of Birth` fields." -msgstr "" - -#: ../../content/applications/hr/employees/new_employee.rst:270 -msgid ":guilabel:`Dependant`: If the employee has any children, enter the :guilabel:`Number of Children` in the field." -msgstr "" - -#: ../../content/applications/hr/employees/new_employee.rst:272 -msgid ":guilabel:`Work Permit`: If the employee has a work permit, enter the information in this section. Type in the :guilabel:`Visa No` and/or :guilabel:`Work Permit No` in the corresponding fields. Using the calendar module, select the :guilabel:`Visa Expire Date` and/or the :guilabel:`Work Permit Expiration Date` to enter the expiration date(s). If available, upload a digital copy of the work permit document. Click :guilabel:`Upload Your File`, navigate to the work permit file in the file explorer, and click :guilabel:`Open`." +#: ../../content/applications/hr/employees/new_employee.rst:129 +msgid "An employee's skills can be entered in the :guilabel:`Resumé` tab in the same manner that a resumé line is created. When creating a skill for the first time, click the :guilabel:`Create a new entry` button under :guilabel:`Skills` and a :guilabel:`Create Skills` form appears. After a skill is added, the :guilabel:`Create a new entry` button is replaced with an :guilabel:`Add` button. Enter the following information for each skill." msgstr "" #: ../../content/applications/hr/employees/new_employee.rst:-1 -msgid "Add the private information to the Private Information tab." +msgid "A skill form with the information filled out." msgstr "" -#: ../../content/applications/hr/employees/new_employee.rst:284 -msgid "HR settings tab" +#: ../../content/applications/hr/employees/new_employee.rst:139 +msgid ":guilabel:`Skill Type`: Select a :ref:`skill type ` by clicking the radio button next to the skill type." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:141 +msgid ":guilabel:`Skill`: After selecting a :guilabel:`Skill Type`, the corresponding skills associated with that selected :guilabel:`Skill Type` appear in a drop-down menu. For example, selecting :guilabel:`Language` as the :guilabel:`Skill Type` presents a variety of languages to select from under the :guilabel:`Skills` field. Select the appropriate pre-configured skill, or type in a new skill, then click :guilabel:`Create \"(new skill)\"`." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:146 +msgid ":guilabel:`Skill Level`: Pre-defined skill levels associated with the selected :guilabel:`Skill Type` appear in a drop-down menu. First, select a :guilabel:`Skill Level`, then the progress bar automatically displays the pre-defined progress for that specific skill level. Skill levels and progress can be modified in the :guilabel:`Skill Level` pop-up form, which is accessed via the :guilabel:`Internal Link` arrow next to :guilabel:`Skill Level` field." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:152 +msgid "Once all the information is entered, click the :guilabel:`Save & Close` button if there is only one skill to add, or click the :guilabel:`Save & New` button to save the current entry and immediately create a new entry." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:156 +msgid "To delete any line from the :guilabel:`Resumé` tab, click the :guilabel:`🗑️ (trash can)` icon to delete the entry. Add a new line by clicking the :guilabel:`Add` button next to the corresponding section." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:163 +msgid "Skill Types" +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:165 +msgid "In order to add a skill to an employee's form, the :guilabel:`Skill Types` must be configured. Go to :menuselection:`Employees app --> Configuration --> Employee: Skill Types` to view the currently configured skill types and create new skill types. Click :guilabel:`New` and a new :guilabel:`Skill Type` form appears. Fill out all the details for the new skill type. Repeat this for all the skill types needed." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:171 +msgid ":guilabel:`Skill Type`: Enter the name of the skill type. This will act as the parent category for more specific skills and should be generic." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:173 +msgid ":guilabel:`Skills`: Click :guilabel:`Add a line` and enter the name for the new skill, then repeat for all other needed skills." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:175 +msgid ":guilabel:`Levels`: Click :guilabel:`Add a line` and a :guilabel:`Create Levels` form appears. Enter the name of the level, and assign a number for the :guilabel:`Progress` percentage (0-100) for that level. Click :guilabel:`Save & New` to save the entry and add another level, or click :guilabel:`Save & Close` to save the level and close the form. Once all the levels are entered, click the :guilabel:`Save manually` icon at the top of the screen. Next, select a default level for this skill type. Click :guilabel:`Set Default` on the line to be the default value. This is typically the lowest level, but any level can be set as the default. A check mark appears in the :guilabel:`Default Level` column, indicating which level is the default." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:185 +msgid "To add a math skill set, enter `Math` in the :guilabel:`Name` field. Next, in the :guilabel:`Skills` field, enter `Algebra`, `Calculus`, and `Trigonometry`. Last, in the :guilabel:`Levels` field enter `Beginner`, `Intermediate`, and `Expert`, with the :guilabel:`Progress` listed as `25`, `50`, and `100`, respectively. Then, click :guilabel:`Save & Close`, then click the :guilabel:`Save manually` icon at the top. Last, click :guilabel:`Set Default` on the `Beginner` line to set this as the default skill level." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:0 +msgid "A skill form for a Math skill type, with all the information entered." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:197 +msgid "Work Information tab" +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:199 +msgid "The Work Information tab is where the employee's specific job related information is housed. Their working schedule, various roles, who approves their specific requests (time off, timesheets, and expenses), and specific work location details are listed here. Click on the :guilabel:`Work Information` tab to access this section, and enter the following information for the new employee." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:204 +msgid ":guilabel:`Location`: Select the :guilabel:`Work Address` from the drop-down menu. To modify the address, hover over the first line (if there are multiple lines) of the address to reveal an :guilabel:`Internal Link` arrow. Click the :guilabel:`Internal Link` arrow to open up the company form, and make any edits. Use the breadcrumb menu to navigate back to the new employee form when done. If a new work address is needed, add the address by typing it in the field, then click :guilabel:`Create (new address)` to add the address, or :guilabel:`Create and edit...` to add the new address and edit the address form." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:211 +msgid ":guilabel:`Approvers`: In order to see this section, the user must have either :guilabel:`Administrator` or :guilabel:`Officer: Manage all employees` rights set for the :guilabel:`Employees` application. Using the drop-down menus, select the users responsible for approving :guilabel:`Expenses`, :guilabel:`Time Off`, and :guilabel:`Timesheets` for the employee. Hover over any of the selections to reveal the :guilabel:`Internal Link` arrow. Click the :guilabel:`Internal Link` arrow to open a form with the approver's :guilabel:`Name`, :guilabel:`Email Address`, :guilabel:`Company`, :guilabel:`Phone`, :guilabel:`Mobile`, and :guilabel:`Default Warehouse` fields. These can be modified, if needed. Use the breadcrumb menu to navigate back to the new employee form when done." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:220 +msgid ":guilabel:`Homeworking`: Using the drop-down menu, select the specific location the employee will work from, for each day of the week. The default options are :guilabel:`Home`, :guilabel:`Office`, or :guilabel:`Other`. A new location can be typed into the field, then click either :guilabel:`Create (new location)` to add the location, or :guilabel:`Create and edit...` to add the new location and edit the form. After edits are done, click :guilabel:`Save & Close`, and the new location is added, and populates the field. For days the employee does not work, for example, Saturday and Sunday, leave the field blank (:guilabel:`Unspecified`)." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:229 +msgid "It is also possible to add or modify work locations by navigating to :menuselection:`Employees app --> Configuration --> Employee: Work Locations`. Click :guilabel:`New` to create a new location, then enter the details on the form. To modify a location, click on an existing location, then make any changes on the form." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:234 +msgid ":guilabel:`Schedule`: Select the :guilabel:`Working Hours` and :guilabel:`Timezone` for the employee. The :guilabel:`Internal Link` arrow opens up a detailed view of the specific daily working hours. Working hours can be modified or deleted here." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:239 +msgid "Working hours can also be modified in the *Payroll* application, where they are referred to as :guilabel:`Working Schedules`. For more information on how to create or modify :guilabel:`Working Schedules` in Payroll, refer to the :doc:`../../hr/payroll` documentation." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:243 +msgid ":guilabel:`Planning`: Click on a role from the drop-down menu for both the :guilabel:`Roles` and the :guilabel:`Default Role` fields to add a role. There is no limit to the amount of :guilabel:`Roles` that can be selected for an employee, but there can only be one :guilabel:`Default Role`. The default role is the *typical* role that the employee performs, where the :guilabel:`Roles` are *all* the specific roles the employee is able to perform. The :guilabel:`Default Role` must be selected as a :guilabel:`Role`, if not, when the :guilabel:`Default Role` is selected, that role is automatically added to the list of :guilabel:`Roles`." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:253 +msgid "The :guilabel:`Planning` section affects the *Planning* app, and will only appear if the *Planning* app is installed. When planning work in the *Planning* app, employees can only be scheduled for specific work that corresponds to their selected roles. For example, only an employee with a *Functional Tester* role can be assigned to perform any activity that requires a *Functional Tester*." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:260 +msgid "The users that appear in the drop-down menu for the :guilabel:`Approvers` section must have *Administrator* rights set for the corresponding human resources role. To check who has these rights, go to :menuselection:`Settings app --> Users --> → Manage Users`. Click on an employee, and check the :guilabel:`Human Resources` section of the :guilabel:`Access Rights` tab." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:265 +msgid "In order for the user to appear as an approver for :guilabel:`Expenses`, they must have either :guilabel:`Team Approver`, :guilabel:`All Approver`, or :guilabel:`Administrator` set for the :guilabel:`Expenses` role." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:268 +msgid "In order for the user to appear as an approver for :guilabel:`Time Off`, they must have either :guilabel:`Officer` or :guilabel:`Administrator` set for the :guilabel:`Time Off` role." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:270 +msgid "In order for the user to appear as an approver for :guilabel:`Timesheets`, they must have either :guilabel:`Manager`, :guilabel:`Officer`, or :guilabel:`Administrator` set for the :guilabel:`Payroll` role." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:275 +msgid ":guilabel:`Working Hours` are related to a company's working times, and an employee cannot have working hours that are outside of a company's working times." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:278 +msgid "Each individual working time is company-specific, so for multi-company databases, each company needs to have its own working hours set." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:281 +msgid "If an employee's working hours are not configured as a working time for the company, new working times can be added, or existing working times can be modified. To add or modify a working time, go to the :menuselection:`Payroll app --> Configuration --> Working Times`, and add a new working time or edit an existing one." msgstr "" #: ../../content/applications/hr/employees/new_employee.rst:286 -msgid "This tab provides various fields for different information, depending on the country the company is located. Different fields are configured for different locations, however some sections appear regardless." +msgid "After the new working time is created, or an existing one is modified, select the employee's working hours using the drop-down menu in the :guilabel:`Schedule` section of the :guilabel:`Work Information` tab." msgstr "" -#: ../../content/applications/hr/employees/new_employee.rst:290 -msgid ":guilabel:`Status`: Select an :guilabel:`Employee Type` and, if applicable, a :ref:`Related User `, with the drop-down menus." +#: ../../content/applications/hr/employees/new_employee.rst:291 +msgid "Private Information tab" msgstr "" -#: ../../content/applications/hr/employees/new_employee.rst:292 -msgid ":guilabel:`Payroll`: Select the :guilabel:`Current Contract` and :guilabel:`Job Position` from the drop-down menus. If applicable, enter the :guilabel:`Registration Number` in this section." -msgstr "" - -#: ../../content/applications/hr/employees/new_employee.rst:294 -msgid ":guilabel:`Previous Employer`: This section appears only for Belgian companies, and will not be visible for other locations. These are days that will be paid to the new employee. Enter any :guilabel:`Simple Holiday Pay to Recover`, :guilabel:`Number of Days to recover`, and :guilabel:`Recovered Simple Holiday Pay` from a previous employer, for both N and N-1 categories." +#: ../../content/applications/hr/employees/new_employee.rst:293 +msgid "No information in the :guilabel:`Private Information` tab is required to create an employee, however, some information in this section may be critical for the company's payroll department. In order to properly process payslips and ensure all deductions are accounted for, the employee's personal information should be entered." msgstr "" #: ../../content/applications/hr/employees/new_employee.rst:298 -msgid ":guilabel:`Previous Occupations`: This section appears ony for Belgian companies, and will not be visible for other locations. Click :guilabel:`Add a line` to enter information for each previous occupation. Enter the number of :guilabel:`Months`, the :guilabel:`Amount`, and the :guilabel:`Occupational Rate` in the corresponding fields. Click the :guilabel:`🗑️ (trash can)` icon to delete a line." +msgid "Here, the employee's :guilabel:`Private Contact`, :guilabel:`Education`, :guilabel:`Work Permit`, :guilabel:`Family Status`, :guilabel:`Emergency` contact, and :guilabel:`Citizenship` information is entered. Fields are entered either using a drop-down menu, activating a check box, or typing in the information." msgstr "" #: ../../content/applications/hr/employees/new_employee.rst:303 -msgid ":guilabel:`Attendance/Point of Sale`: The employee's :guilabel:`Badge ID` and :guilabel:`PIN Code` can be entered here, if the employee needs/has one. Click :guilabel:`Generate` next to the :guilabel:`Badge ID` to create a badge ID." +msgid ":guilabel:`Private Contact`: Enter the personal :guilabel:`Address` for the employee. The selection can be made with the drop-down menu. If the information is not available, type in the name for the new address. To edit the new address, click the :guilabel:`Internal Link` arrow to open the address form. On the address form, enter or edit the necessary details. Some other information in the :guilabel:`Private Contact` section may auto-populate, if the address is already listed in the drop-down menu." msgstr "" -#: ../../content/applications/hr/employees/new_employee.rst:306 -msgid ":guilabel:`Application Settings`: If applicable, enter the :guilabel:`Fleet Mobility Card` number. Enter the employee's cost per hour in a $XX.XX format. This is factored in when the employee is working at a :doc:`work center <../../inventory_and_mrp/manufacturing/management/using_work_centers>`. This value affects the manufacturing costs for a product, if the value of the manufactured product is not a fixed amount." +#: ../../content/applications/hr/employees/new_employee.rst:310 +msgid "Enter the employee's :guilabel:`Email` address and :guilabel:`Phone` number in the respective fields. Next, enter the employee's :guilabel:`Bank Account Number` using the drop-down menu. If the bank is not already configured (the typical situation when creating a new employee) enter the bank account number, and click :guilabel:`Create and edit..`. A :guilabel:`Create Bank Account Number` form loads. Fill in the information, then click :guilabel:`Save & Close`." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:316 +msgid "Then, select the employee's preferred :guilabel:`Language` from the drop-down menu. Next, enter the :guilabel:`Home-Work Distance` in the field. This field is only necessary if the employee is receiving any type of commuter benefits. Lastly, enter the employee's license plate information in the :guilabel:`Private Car Plate` field." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:320 +msgid ":guilabel:`Education`: Select the highest level of education completed by the employee from the :guilabel:`Certificate Level` drop-down menu. Options include :guilabel:`Graduate`, :guilabel:`Bachelor`, :guilabel:`Master`, :guilabel:`Doctor`, or :guilabel:`Other`. Type in the :guilabel:`Field of Study`, and the name of the :guilabel:`School` in the respective fields." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:324 +msgid ":guilabel:`Work Permit`: If the employee has a work permit, enter the information in this section. Type in the :guilabel:`Visa No` (visa number) and/or :guilabel:`Work Permit No` (work permit number) in the corresponding fields. Using the calendar selector, select the :guilabel:`Visa Expire Date` and/or the :guilabel:`Work Permit Expiration Date` to enter the expiration date(s). If available, upload a digital copy of the work permit document. Click :guilabel:`Upload Your File`, navigate to the work permit file in the file explorer, and click :guilabel:`Open`." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:330 +msgid ":guilabel:`Family Status`: Select the current :guilabel:`Marital Status` using the drop-down menu, either :guilabel:`Single`, :guilabel:`Married`, :guilabel:`Legal Cohabitant`, :guilabel:`Widower`, or :guilabel:`Divorced`. If the employee has any dependent children, enter the :guilabel:`Number of Dependent Children` in the field." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:334 +msgid ":guilabel:`Emergency`: Type in the :guilabel:`Contact Name` and :guilabel:`Contact Phone` number of the employee's emergency contact in the respective fields." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:336 +msgid ":guilabel:`Citizenship`: This section contains all the information relevant to the citizenship of the employee. Some fields use a drop-down menu, as the :guilabel:`Nationality (Country)`, :guilabel:`Gender`, and :guilabel:`Country of Birth` fields do. The :guilabel:`Date of Birth` uses a calendar selector to select the date. First, click on the name of the month, then the year, to access the year ranges. Use the :guilabel:`< (left)` and :guilabel:`> (right)` arrow icons, navigate to the correct year range, and click on the year. Next, click on the month. Last, click on the day to select the date. Type in the information for the :guilabel:`Identification No` (identification number, :guilabel:`Passport No` (passport number), and :guilabel:`Place of Birth` fields. Last, if the employee is not a resident of the country they are working in, activate the check box next to the :guilabel:`Non-resident` field." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:350 +msgid "HR Settings tab" +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:352 +msgid "This tab provides various fields for different information, depending on the country the company is located. Different fields are configured for different locations, however some sections appear regardless." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:356 +msgid ":guilabel:`Status`: Select an :guilabel:`Employee Type` and, if applicable, a :guilabel:`Related User`, with the drop-down menus. The :guilabel:`Employee Type` options include :guilabel:`Employee`, :guilabel:`Student`, :guilabel:`Trainee`, :guilabel:`Contractor`, or :guilabel:`Freelancer`." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:362 +msgid "Employees do not also need to be users. *Employees* do **not** count towards the Odoo subscription billing, while *Users* **do** count towards billing. If the new employee should also be a user, the user must be created. After the :guilabel:`User` is created and saved, the new user will appear in the :guilabel:`Related User` field." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:367 +msgid "After the employee is created, create the user. Click the :guilabel:`⚙️ (gear)` icon, then click :guilabel:`Create User`. A :guilabel:`Create User` form appears. Type in the :guilabel:`Name` and :guilabel:`Email Address`, and then select the :guilabel:`Company` from the drop-down menu. Click :guilabel:`Save` after the information is entered, and the employee record is automatically updated with the newly created user populating the :guilabel:`Related User` field." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:373 +msgid "Users can also be created manually. For more information on how to manually add a user, refer to the :doc:`../../general/users/manage_users` document." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:376 +msgid ":guilabel:`Payroll`: If applicable, enter the :guilabel:`Registration Number of the Employee` in this section. The :guilabel:`Attestation (N-1)` and :guilabel:`Attestation (N)` sections appear only for Belgian companies, and will not be visible for other locations. These sections log the days that will be paid to the new employee. Enter any :guilabel:`Amount to recover`, :guilabel:`Number of days`, and :guilabel:`Recovered Amount` of :guilabel:`Holiday Attest (year) - Simple Holiday Pay from previous employer to recover in (year)`, for both N and N-1 categories. For the :guilabel:`Holiday Attest (year) - Previous occupation for Double Holiday Pay Recovery in (year)` section, click :guilabel:`Add a line`, and enter the number of :guilabel:`Months`, the :guilabel:`Amount`, and :guilabel:`Occupation Rate`. Repeat for all entries. Click the :guilabel:`🗑️ (trash can)` icon to delete a line." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:386 +msgid ":guilabel:`SD WORX`: Enter the employee's seven digit :guilabel:`SDWorx code` in this field, if applicable." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:388 +msgid ":guilabel:`Attendance/Point of Sale/Manufacturing`: The employee's :guilabel:`PIN Code` and :guilabel:`Badge ID` can be entered here, if the employee needs/has one. Click :guilabel:`Generate` next to the :guilabel:`Badge ID` to create a badge ID. The :guilabel:`PIN Code` is used to sign in and out of the *Attendance* app kiosk, and a :abbr:`POS (Point Of Sale)` system." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:393 +msgid ":guilabel:`Application Settings`: Enter the employee's :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>`. This value affects the manufacturing costs for a product, if the value of the manufactured product is not a fixed amount. This value does not affect the *Payroll* application. If applicable, enter the :guilabel:`Fleet Mobility Card` number." msgstr "" #: ../../content/applications/hr/employees/new_employee.rst:-1 msgid "Enter any information prompted in the HR Settings tab for the employee." msgstr "" -#: ../../content/applications/hr/employees/new_employee.rst:319 -msgid "Employees do not also need to be users. An employee does **not** count towards billing, while *Users* **do** count towards billing. If the new employee should also be a user, the user must be created." -msgstr "" - -#: ../../content/applications/hr/employees/new_employee.rst:323 -msgid "In the :guilabel:`Related User` field, type in the name of the user to add, then click :guilabel:`Create and Edit...`. A :guilabel:`Create: Related User` form appears. Type in the :guilabel:`Name`, :guilabel:`Email Address`, and then select the :guilabel:`Company` from the drop-down menu. Click :guilabel:`Save` after the information is entered. Once the record is saved, the new user appears in the :guilabel:`Related User` field." -msgstr "" - -#: ../../content/applications/hr/employees/new_employee.rst:330 +#: ../../content/applications/hr/employees/new_employee.rst:405 msgid "Documents" msgstr "" -#: ../../content/applications/hr/employees/new_employee.rst:332 -msgid "All documents associated with an employee are stored in the *Documents* app. The number of documents associated with the employee appear in the :guilabel:`Documents` smart button on the employee form. Click on the smart button, and all the documents appear. For more information on the *Documents* app, refer to the :doc:`Documents documentation `." +#: ../../content/applications/hr/employees/new_employee.rst:407 +msgid "All documents associated with an employee are stored in the :guilabel:`Documents` app. The number of documents associated with the employee appear in the :guilabel:`Documents` smart button above the employee record. Click on the smart button, and all the documents appear. For more information on the :guilabel:`Documents` app, refer to the :doc:`../../finance/documents` documentation." msgstr "" #: ../../content/applications/hr/employees/new_employee.rst:-1 msgid "All uploaded documents associated with the employee appear in the documents smart-button." msgstr "" -#: ../../content/applications/hr/payroll.rst:5 -msgid "Payroll" +#: ../../content/applications/hr/fleet.rst:7 +msgid "Fleet" msgstr "" -#: ../../content/applications/hr/payroll.rst:7 -msgid "Odoo *Payroll* is used to process work entries and create payslips for employees, including both regular pay and commission. Payroll works in conjunction with other Odoo apps, such as *Employees*, *Timesheets*, *Time Off*, and *Attendances*." +#: ../../content/applications/hr/fleet.rst:9 +msgid "Odoo *Fleet* organizes all the vehicles, contracts, and repairs of all the vehicles." msgstr "" -#: ../../content/applications/hr/payroll.rst:11 -msgid "The *Payroll* app helps ensure there are no issues or conflicts when validating work entries, handles country-specific localizations to ensure that payslips follow local rules and taxes, and allows for salary assignments. Payroll configuration is critical to ensure accurate and timely processing of payslips." +#: ../../content/applications/hr/fleet/configuration.rst:3 +msgid "Configuration menu" msgstr "" -#: ../../content/applications/hr/payroll.rst:17 +#: ../../content/applications/hr/fleet/configuration.rst:5 +msgid "This document outlines all of the configurations and settings for the *Fleet* application, including :ref:`settings `, :ref:`manufacturers `, :ref:`vehicle models `, and :ref:`model categories `." +msgstr "" + +#: ../../content/applications/hr/fleet/configuration.rst:13 +#: ../../content/applications/hr/payroll.rst:18 msgid "Settings" msgstr "" -#: ../../content/applications/hr/payroll.rst:19 +#: ../../content/applications/hr/fleet/configuration.rst:15 +msgid "To access the settings menu, go to :menuselection:`Fleet application --> Configuration --> Settings`. There are two settings that need configuration, the vehicle contract end date alert delay, and a new vehicle request limit." +msgstr "" + +#: ../../content/applications/hr/fleet/configuration.rst:-1 +msgid "Settings available for the Fleet application." +msgstr "" + +#: ../../content/applications/hr/fleet/configuration.rst:24 +msgid "End Date Contract Alert" +msgstr "" + +#: ../../content/applications/hr/fleet/configuration.rst:26 +msgid "The :guilabel:`End Date Contract Alert` field defines an alert delay for the persons responsible for vehicle contracts. The responsible person(s) will receive an email informing them a vehicle contract is about to expire in the number of days defined in this field." +msgstr "" + +#: ../../content/applications/hr/fleet/configuration.rst:31 +msgid "To determine who the responsible person is for a contract, open an individual contract. The person listed as :guilabel:`Responsible` under the :guilabel:`Contract Information` section of the contract is the person who will receive the alert." +msgstr "" + +#: ../../content/applications/hr/fleet/configuration.rst:35 +msgid "To access all contracts, navigate to :menuselection:`Fleet app --> Fleet --> Contracts` and all contracts appear in the list. Click on a :guilabel:`Contract` to view it." +msgstr "" + +#: ../../content/applications/hr/fleet/configuration.rst:38 +msgid "An individual contract can also be found by navigating to :menuselection:`Fleet app --> Fleet --> Fleet` and clicking on an individual vehicle. On the vehicle form, click the :guilabel:`Contracts` smart button at the top of the page. The contract(s) associated with this vehicle only appears in the list. Click on an individual contract to open it. The :guilabel:`Responsible` person is listed on the contract." +msgstr "" + +#: ../../content/applications/hr/fleet/configuration.rst:45 +msgid "New Vehicle Request" +msgstr "" + +#: ../../content/applications/hr/fleet/configuration.rst:47 +msgid "The :guilabel:`New Vehicle Request` field sets a limit on how many new vehicles are requested based on fleet availability. An employee filling out the salary configurator form (after being offered a position), will *not* be able to request a new car if the number of existing cars is greater than the number specified in the :guilabel:`New Vehicle Request` field. Enter the specific number limit for existing available cars in this field." +msgstr "" + +#: ../../content/applications/hr/fleet/configuration.rst:54 +msgid "If the :guilabel:`New Vehicle Request` limit is set to 20 vehicles, and there are 25 vehicles available, an employee would not be able to request a new vehicle. If there are only 10 cars available, then the employee would be able to request a new vehicle." +msgstr "" + +#: ../../content/applications/hr/fleet/configuration.rst:61 +msgid "Manufacturers" +msgstr "" + +#: ../../content/applications/hr/fleet/configuration.rst:63 +msgid "Odoo *Fleet* comes pre-configured with sixty-six commonly used car and bicycle manufacturers in the database, along with their logos. To view the pre-loaded manufacturers, go to :menuselection:`Fleet app --> Configuration --> Manufacturers`." +msgstr "" + +#: ../../content/applications/hr/fleet/configuration.rst:67 +msgid "The manufacturers appear in a list view in alphabetical order. Each manufacturer's card lists how many specific models are configured for each particular manufacturer. Odoo comes with forty six pre-configured :ref:`models ` from four major auto manufacturers and one major bicycle manufacturer: Audi, BMW, Mercedes, Opel (cars), and Eddy Merckx (bicycle)." +msgstr "" + +#: ../../content/applications/hr/fleet/configuration.rst:-1 +msgid "Manufacturer card with the amount of models listed." +msgstr "" + +#: ../../content/applications/hr/fleet/configuration.rst:77 +msgid "Add a manufacturer" +msgstr "" + +#: ../../content/applications/hr/fleet/configuration.rst:79 +msgid "To add a new manufacturer to the database, click :guilabel:`Create`. A manufacturer form will load. Only two pieces of information are needed, the :guilabel:`Name` of the manufacturer, and the logo. Type the name of the manufacturer in the name field, and select an image to upload for the logo. When the information is entered, click :guilabel:`Save`." +msgstr "" + +#: ../../content/applications/hr/fleet/configuration.rst:87 +msgid "Vehicle Models" +msgstr "" + +#: ../../content/applications/hr/fleet/configuration.rst:89 +msgid "Many manufacturers have a variety of models that they produce. When adding a vehicle to the fleet, it is important to specify the vehicle model being added. Odoo comes with pre-configured car models from four major auto manufacturers, and one pre-configured bicycle model from one bicycle manufacturer: Audi, BMW, Mercedes, Opel (cars), and Eddy Merckx (bicycle). If a vehicle *other* than the pre-configured models from these manufacturers are part of a fleet, the model (and/or manufacturer) will need to be added to the database." +msgstr "" + +#: ../../content/applications/hr/fleet/configuration.rst:97 +msgid "Preconfigured Models" +msgstr "" + +#: ../../content/applications/hr/fleet/configuration.rst:99 +msgid "The following models are pre-loaded in Odoo and do not need to be added to the database:" +msgstr "" + +#: ../../content/applications/hr/fleet/configuration.rst:102 +msgid "AUDI" +msgstr "" + +#: ../../content/applications/hr/fleet/configuration.rst:102 +msgid "BMW" +msgstr "" + +#: ../../content/applications/hr/fleet/configuration.rst:102 +msgid "Eddy Merckx" +msgstr "" + +#: ../../content/applications/hr/fleet/configuration.rst:102 +msgid "Mercedes" +msgstr "" + +#: ../../content/applications/hr/fleet/configuration.rst:102 +msgid "Opel" +msgstr "" + +#: ../../content/applications/hr/fleet/configuration.rst:104 +msgid "A1" +msgstr "" + +#: ../../content/applications/hr/fleet/configuration.rst:104 +msgid "Serie 1" +msgstr "" + +#: ../../content/applications/hr/fleet/configuration.rst:104 +msgid "SanRemo76" +msgstr "" + +#: ../../content/applications/hr/fleet/configuration.rst:104 +msgid "Class A" +msgstr "" + +#: ../../content/applications/hr/fleet/configuration.rst:104 +msgid "Agilia" +msgstr "" + +#: ../../content/applications/hr/fleet/configuration.rst:106 +msgid "A3" +msgstr "" + +#: ../../content/applications/hr/fleet/configuration.rst:106 +msgid "Serie 3" +msgstr "" + +#: ../../content/applications/hr/fleet/configuration.rst:106 +msgid "Class B" +msgstr "" + +#: ../../content/applications/hr/fleet/configuration.rst:106 +msgid "Ampera" +msgstr "" + +#: ../../content/applications/hr/fleet/configuration.rst:108 +msgid "A4" +msgstr "" + +#: ../../content/applications/hr/fleet/configuration.rst:108 +msgid "Serie 5" +msgstr "" + +#: ../../content/applications/hr/fleet/configuration.rst:108 +msgid "Class C" +msgstr "" + +#: ../../content/applications/hr/fleet/configuration.rst:108 +msgid "Antara" +msgstr "" + +#: ../../content/applications/hr/fleet/configuration.rst:110 +msgid "A5" +msgstr "" + +#: ../../content/applications/hr/fleet/configuration.rst:110 +msgid "Serie 6" +msgstr "" + +#: ../../content/applications/hr/fleet/configuration.rst:110 +msgid "Class CL" +msgstr "" + +#: ../../content/applications/hr/fleet/configuration.rst:110 +msgid "Astra" +msgstr "" + +#: ../../content/applications/hr/fleet/configuration.rst:112 +msgid "A6" +msgstr "" + +#: ../../content/applications/hr/fleet/configuration.rst:112 +msgid "Serie 7" +msgstr "" + +#: ../../content/applications/hr/fleet/configuration.rst:112 +msgid "Class CLS" +msgstr "" + +#: ../../content/applications/hr/fleet/configuration.rst:112 +msgid "AstraGTC" +msgstr "" + +#: ../../content/applications/hr/fleet/configuration.rst:114 +msgid "A7" +msgstr "" + +#: ../../content/applications/hr/fleet/configuration.rst:114 +msgid "Serie Hybrid" +msgstr "" + +#: ../../content/applications/hr/fleet/configuration.rst:114 +msgid "Class E" +msgstr "" + +#: ../../content/applications/hr/fleet/configuration.rst:114 +msgid "Combo Tour" +msgstr "" + +#: ../../content/applications/hr/fleet/configuration.rst:116 +msgid "A8" +msgstr "" + +#: ../../content/applications/hr/fleet/configuration.rst:116 +msgid "Serie M" +msgstr "" + +#: ../../content/applications/hr/fleet/configuration.rst:116 +msgid "Class GL" +msgstr "" + +#: ../../content/applications/hr/fleet/configuration.rst:116 +msgid "Corsa" +msgstr "" + +#: ../../content/applications/hr/fleet/configuration.rst:118 +msgid "Q3" +msgstr "" + +#: ../../content/applications/hr/fleet/configuration.rst:118 +msgid "Serie X" +msgstr "" + +#: ../../content/applications/hr/fleet/configuration.rst:118 +msgid "Class GLK" +msgstr "" + +#: ../../content/applications/hr/fleet/configuration.rst:118 +msgid "Insignia" +msgstr "" + +#: ../../content/applications/hr/fleet/configuration.rst:120 +msgid "Q5" +msgstr "" + +#: ../../content/applications/hr/fleet/configuration.rst:120 +msgid "Serie Z4" +msgstr "" + +#: ../../content/applications/hr/fleet/configuration.rst:120 +msgid "Class M" +msgstr "" + +#: ../../content/applications/hr/fleet/configuration.rst:120 +msgid "Meriva" +msgstr "" + +#: ../../content/applications/hr/fleet/configuration.rst:122 +msgid "Q7" +msgstr "" + +#: ../../content/applications/hr/fleet/configuration.rst:122 +msgid "Class R" +msgstr "" + +#: ../../content/applications/hr/fleet/configuration.rst:122 +msgid "Mokka" +msgstr "" + +#: ../../content/applications/hr/fleet/configuration.rst:124 +msgid "TT" +msgstr "" + +#: ../../content/applications/hr/fleet/configuration.rst:124 +msgid "Class S" +msgstr "" + +#: ../../content/applications/hr/fleet/configuration.rst:124 +msgid "Zafira" +msgstr "" + +#: ../../content/applications/hr/fleet/configuration.rst:126 +msgid "Class SLK" +msgstr "" + +#: ../../content/applications/hr/fleet/configuration.rst:126 +msgid "Zafira Tourer" +msgstr "" + +#: ../../content/applications/hr/fleet/configuration.rst:128 +msgid "Class SLS" +msgstr "" + +#: ../../content/applications/hr/fleet/configuration.rst:134 +msgid "Add a new model" +msgstr "" + +#: ../../content/applications/hr/fleet/configuration.rst:136 +msgid "New vehicle models can easily be added to the database. To add a new model, navigate to :menuselection:`Fleet app --> Configuration --> Vehicle Models`. Click :guilabel:`Create` and a vehicle model form will load. Enter the following information on the form, then click :guilabel:`Save`. Be advised, some fields are specific to Belgian based companies, so not all fields or sections may be visible depending on the location of the company." +msgstr "" + +#: ../../content/applications/hr/fleet/configuration.rst:142 +msgid ":guilabel:`Model name`: enter the model name in the field." +msgstr "" + +#: ../../content/applications/hr/fleet/configuration.rst:143 +msgid ":guilabel:`Manufacturer`: select the manufacturer from the drop-down menu. If the manufacturer is not configured, type in the manufacturer and then click :guilabel:`Create` or :guilabel:`Create & Edit`." +msgstr "" + +#: ../../content/applications/hr/fleet/configuration.rst:146 +msgid ":guilabel:`Vehicle Type`: select one of two preconfigured vehicle types, either :guilabel:`Car` or :guilabel:`Bike`, from the drop-down menu. The vehicle types are hardcoded in Odoo and are integrated with the *Payroll* application since vehicles can be part of an employee's benefits. Adding additional vehicle types is not possible as it will affect payroll." +msgstr "" + +#: ../../content/applications/hr/fleet/configuration.rst:150 +msgid ":guilabel:`Category`: select the category the vehicle is categorized under from the drop-down menu. To create a new category, type in the category and then click :guilabel:`Create (new category)`." +msgstr "" + +#: ../../content/applications/hr/fleet/configuration.rst:155 +msgid "When the manufacturer is selected, the logo for the manufacturer will automatically load in the image box in the top right corner." +msgstr "" + +#: ../../content/applications/hr/fleet/configuration.rst:159 +msgid "Information tab" +msgstr "" + +#: ../../content/applications/hr/fleet/configuration.rst:162 +msgid "Model" +msgstr "" + +#: ../../content/applications/hr/fleet/configuration.rst:164 +msgid ":guilabel:`Seats Number`: enter how many passengers the vehicle can accommodate." +msgstr "" + +#: ../../content/applications/hr/fleet/configuration.rst:165 +msgid ":guilabel:`Doors Number`: enter the number of doors the vehicle has." +msgstr "" + +#: ../../content/applications/hr/fleet/configuration.rst:166 +msgid ":guilabel:`Color`: enter the color of the vehicle." +msgstr "" + +#: ../../content/applications/hr/fleet/configuration.rst:167 +msgid ":guilabel:`Model Year`: enter the year the vehicle was manufactured." +msgstr "" + +#: ../../content/applications/hr/fleet/configuration.rst:168 +msgid ":guilabel:`Trailer Hitch`: check this box if the vehicle has a trailer hitch installed." +msgstr "" + +#: ../../content/applications/hr/fleet/configuration.rst:171 +#: ../../content/applications/hr/payroll.rst:211 +msgid "Salary" +msgstr "" + +#: ../../content/applications/hr/fleet/configuration.rst:174 +msgid "The :guilabel:`Salary` section only appears for Belgian-based companies, and only if the company has their localization setting set to Belgium. The cost values are all **monthly** with the exception of the :guilabel:`Catalog Value (VAT Incl.)`." +msgstr "" + +#: ../../content/applications/hr/fleet/configuration.rst:178 +msgid ":guilabel:`Can be requested`: check this box if employees can request this model vehicle." +msgstr "" + +#: ../../content/applications/hr/fleet/configuration.rst:179 +msgid ":guilabel:`Catalog Value (VAT Incl.)`: enter the :abbr:`MSRP (Manufacturer's Suggested Retail Price)` for the vehicle at the time of purchase or lease." +msgstr "" + +#: ../../content/applications/hr/fleet/configuration.rst:181 +msgid ":guilabel:`C02 fee`: this value is automatically calculated based on Belgian laws and regulations, and cannot be modified. The value is based on the value entered in the :guilabel:`CO2 Emissions` field in the :guilabel:`Engine` section of the vehicle form." +msgstr "" + +#: ../../content/applications/hr/fleet/configuration.rst:186 +msgid "Modifying the :guilabel:`CO2 Emissions` field will adjust the value in the :guilabel:`CO2 fee` field." +msgstr "" + +#: ../../content/applications/hr/fleet/configuration.rst:189 +msgid ":guilabel:`Cost (Depreciated)`: enter the monthly cost for the vehicle, which appears in the salary configurator that is available to a future employee when they are offered a job position. This value impacts the gross and net salary of the employee who is assigned to the vehicle. This figure is depreciated over time according to local tax laws. The :guilabel:`Cost (Depreciated)` does not depreciate automatically on the *vehicle model*, it only depreciates based on the *contract* linked to a specific vehicle and not on the general model." +msgstr "" + +#: ../../content/applications/hr/fleet/configuration.rst:195 +msgid ":guilabel:`Total Cost (Depreciated)`: this value is the :guilabel:`Cost (Depreciated)` and the :guilabel:`C02 fee` fields combined, and also is depreciated over time." +msgstr "" + +#: ../../content/applications/hr/fleet/configuration.rst:199 +msgid "Engine" +msgstr "" + +#: ../../content/applications/hr/fleet/configuration.rst:201 +msgid ":guilabel:`Fuel Type`: select the type of fuel the vehicle uses form the drop-down menu. The options are :guilabel:`Diesel`, :guilabel:`Gasoline`, :guilabel:`Hybrid Diesel`, :guilabel:`Hybrid Gasoline`, :guilabel:`Plug-in Hybrid Diesel`, :guilabel:`Plug-in Hybrid Gasoline`, :guilabel:`CNG`, :guilabel:`LPG`, :guilabel:`Hydrogen`, or :guilabel:`Electric`." +msgstr "" + +#: ../../content/applications/hr/fleet/configuration.rst:205 +msgid ":guilabel:`CO2 Emissions`: enter the average carbon dioxide emissions the vehicle produces in grams per kilometer (g/km). This information is provided by the car manufacturer." +msgstr "" + +#: ../../content/applications/hr/fleet/configuration.rst:207 +msgid ":guilabel:`CO2 Standard`: enter the standard amount of carbon dioxide in grams per kilometer (g/km) for a similar sized vehicle." +msgstr "" + +#: ../../content/applications/hr/fleet/configuration.rst:209 +msgid ":guilabel:`Transmission`: select the transmission type from the drop-down menu, either :guilabel:`Manual` or :guilabel:`Automatic`." +msgstr "" + +#: ../../content/applications/hr/fleet/configuration.rst:211 +msgid ":guilabel:`Power`: if the vehicle is electric or hybrid, enter the power the vehicle uses in kilowatts (kW)." +msgstr "" + +#: ../../content/applications/hr/fleet/configuration.rst:213 +msgid ":guilabel:`Horsepower`: enter the vehicle's horsepower in this field." +msgstr "" + +#: ../../content/applications/hr/fleet/configuration.rst:214 +msgid ":guilabel:`Horsepower Taxation`: enter the amount that is taxed based on the size of the vehicle's engine. This is determined by local taxes and regulations, and varies depending on the location. It is recommended to check with the accounting department to ensure this value is correct." +msgstr "" + +#: ../../content/applications/hr/fleet/configuration.rst:217 +msgid ":guilabel:`Tax Deduction`: this field auto-populates according to the engine specifications, and cannot be modified. The percentage is based on the localization settings and local tax laws." +msgstr "" + +#: ../../content/applications/hr/fleet/configuration.rst:221 +msgid "Vendors tab" +msgstr "" + +#: ../../content/applications/hr/fleet/configuration.rst:223 +msgid "Vehicle specific vendors, such as car dealerships, are not listed separately from other vendors. The vendors that a vehicle can be purchased from also appear in the list of vendors used by the *Purchase* app." +msgstr "" + +#: ../../content/applications/hr/fleet/configuration.rst:227 +msgid "The vendor(s) the vehicle can be purchased from may be added in this tab. To add a vendor, click :guilabel:`Add`, and a pop-up loads with a list of all the vendors currently in the database. Select the vendor to add by clicking the checkbox next to the vendor name, then click :guilabel:`Select`. There is no limit to the number of vendors that can be added to this list." +msgstr "" + +#: ../../content/applications/hr/fleet/configuration.rst:232 +msgid "If a vendor is not in the database, add a vendor by clicking :guilabel:`Create`. A vendor form will load. Enter the information in the vendor tab, then click :guilabel:`Save & Close` to add the vendor and close the window, or :guilabel:`Save & New` to add the current vendor and create another new vendor." +msgstr "" + +#: ../../content/applications/hr/fleet/configuration.rst:-1 +msgid "Vendor form to fill out when adding a new vendor." +msgstr "" + +#: ../../content/applications/hr/fleet/configuration.rst:244 +msgid "Model Category" +msgstr "" + +#: ../../content/applications/hr/fleet/configuration.rst:246 +msgid "To best organize a fleet, it is recommended to have vehicle models housed under a specific category, to more easily see what kinds of vehicles are in the fleet. Model categories are set on the :ref:`vehicle model form `." +msgstr "" + +#: ../../content/applications/hr/fleet/configuration.rst:250 +msgid "To view all the models currently set up, navigate to :menuselection:`Fleet application --> Configuration --> Model Category`. All models are displayed in a list view." +msgstr "" + +#: ../../content/applications/hr/fleet/configuration.rst:254 +msgid "Add a new model category" +msgstr "" + +#: ../../content/applications/hr/fleet/configuration.rst:256 +msgid "To add a new category, click :guilabel:`Create`. A new entry line appears at the bottom of the list. Type in the new category, then click :guilabel:`Save` to save the entry." +msgstr "" + +#: ../../content/applications/hr/fleet/configuration.rst:259 +msgid "To reorganize how the categories appear in the list, click on the up and down arrows to the left of the category to be moved, and drag the line to the desired position. The order of the list does not affect the database in any way. However, it may be preferable to view the vehicle categories in a specific order, for example, by size, or the numbers of passengers the vehicle can carry." +msgstr "" + +#: ../../content/applications/hr/fleet/configuration.rst:-1 +msgid "List view of the models in the fleet." +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:3 +msgid "Create new vehicles" +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:5 +msgid "Odoo's *Fleet* app manages all vehicles and the accompanying documentation that comes with vehicle maintenance and driver's records." +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:8 +msgid "All vehicles are organized on the main :guilabel:`Fleet` dashboard. Each vehicle has its own *vehicle form*, which is displayed as a card in the kanban view, according to it's status. Every vehicle form is displayed in its current corresponding kanban stage. The default stages are :guilabel:`New Request`, :guilabel:`To Order`, :guilabel:`Ordered`, :guilabel:`Registered`, :guilabel:`Downgraded`, :guilabel:`Reserve`, and :guilabel:`Waiting List`." +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:14 +msgid "To add a new vehicle to the fleet, click the :guilabel:`Create` button, and a blank vehicle form loads. Enter the vehicle information in the vehicle form, then click :guilabel:`Save`." +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:18 +msgid "Vehicle form fields" +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:20 +msgid ":guilabel:`Model`: select the vehicle's model from the drop-down menu. If the model is not listed, type in the model name and click either :guilabel:`Create` or :guilabel:`Create and Edit`." +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:22 +msgid ":guilabel:`License Plate`: enter the vehicle's license plate number in this field." +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:23 +msgid ":guilabel:`Tags`: select any tags from the drop-down menu, or type in a new tag. There is no limit on the amount of tags that can be selected." +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:27 +msgid "The :guilabel:`Model` is the only required field on the new vehicle form. When a model is selected, other fields will appear on the vehicle form, and relevant information will auto-populate fields that apply to the model. If some of the fields do not appear, this may indicate there is no model selected." +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:33 +msgid "Driver section" +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:35 +msgid "This section of the vehicle form relates to the person who is currently driving the car, as well as any plans for a change in the driver in the future, and when." +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:38 +msgid ":guilabel:`Driver`: select the driver from the drop-down menu, or type in a new driver and click either :guilabel:`Create` or :guilabel:`Create and Edit`." +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:40 +msgid ":guilabel:`Mobility Card`: if the selected driver has a mobility card listed on their employee card in the *Employees* application, the mobility card number will appear in this field. If there is no mobility card listed and one should be added, :ref:`edit the employee card ` in the *Employees* application." +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:44 +msgid ":guilabel:`Future Driver`: if the next driver for the vehicle is known, select the next driver from the drop-down menu, or type in the next driver and click either :guilabel:`Create` or :guilabel:`Create and Edit`." +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:47 +msgid ":guilabel:`Plan To Change Car`: if the current driver set for this vehicle plans to change their vehicle, either because they are waiting on a new vehicle that is being ordered, or this is a temporary vehicle assignment and they know which vehicle they will be driving next, check this box. If the current driver does not plan to change their vehicle and use this current vehicle, do not check this box." +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:52 +msgid ":guilabel:`Assignment Date`: select the date the vehicle will be available for another driver using the drop-down calendar. Select the date by navigating to the correct month and year using the :guilabel:`⬅️ (left arrow)` and :guilabel:`➡️ (right arrow)` icons, then click on the specific day. If this field is blank, this indicates the vehicle is currently available and can be reassigned to another driver. If it is populated, the vehicle will not be available to assign to another driver until the date entered." +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:60 +msgid "A driver does **not** have to be an employee, but a driver must be listed in the *Contacts* application. When creating a new driver, the driver is added to the *Contacts* application, not the *Employees* application." +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:65 +msgid "Vehicle section" +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:67 +msgid "This section of the vehicle form relates to the physical vehicle, it's various properties, when it was added, where it is located, and who is managing it." +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:70 +msgid ":guilabel:`Immatriculation Date`: select the date the vehicle is acquired using the drop-down calendar." +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:72 +msgid ":guilabel:`Cancellation Date`: select the date the vehicle lease will expire, or when the vehicle will be no longer available, using the drop-down calendar." +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:74 +msgid ":guilabel:`Chassis Number`: enter the chassis number in the field. This is known in some countries as the :abbr:`VIN (Vehicle Identification Number)` number." +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:76 +msgid ":guilabel:`Last Odometer`: enter the last known odometer reading in the number field. Using the drop-down menu next to the number field, select whether the odometer reading is in kilometers :guilabel:`(km)` or miles :guilabel:`(mi)`." +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:79 +msgid ":guilabel:`Fleet Manager`: select the fleet manager from the drop-down menu, or type in a new fleet manager and click either :guilabel:`Create` or :guilabel:`Create and Edit`." +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:81 +msgid ":guilabel:`Location`: type in the location for the vehicle in the field. The most common scenario for when this field would be populated is if a company has several office locations. The typical office location where the vehicle is located would be the location entered." +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:84 +msgid ":guilabel:`Company`: select the company that the vehicle will be used for and associated with from the drop-down menu, or type in a new company and click either :guilabel:`Create` or :guilabel:`Create and Edit`." +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:89 +msgid "Creating a new company may cause a subscription price change depending on the current plan. Refer to `Odoo's pricing plan `_ for more details." +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:-1 +msgid "The new vehicle form, showing the vehicle tax section." +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:97 +msgid "Tax Info tab" +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:100 +msgid "Fiscality" +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:102 +msgid ":guilabel:`Horsepower Taxation`: enter the amount that is taxed based on the size of the vehicles engine. This is determined by local taxes and regulations, and varies depending on the location. It is recommended to check with the accounting department to ensure this value is correct." +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:105 +msgid ":guilabel:`Disallowed Expense Rate`: this is the amount of non-deductible expenses for the vehicle. This amount is not counted towards any deductions on a tax return or as an allowable expense when calculating taxable income. It is recommended to check with the accounting department to ensure the value(s) entered are correct." +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:110 +msgid ":guilabel:`Start Date`: enter the :guilabel:`Start Date` and :guilabel:`(%) Percentage` for when the :guilabel:`Disallowed Expense Rate` value goes into effect. Click :guilabel:`Add a line` to enter a date. Click on the blank line to display a calendar. Select the date by navigating to the correct month and year using the :guilabel:`⬅️ (left arrow)` and :guilabel:`➡️ (right arrow)` icons, then click on the specific day. Enter the percentage that is disallowed in the :guilabel:`% (percent)` field to the right of the date. The percentage should be entered in an XX.XX format. Repeat this for all entries needed." +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:119 +msgid "Contract" +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:121 +msgid ":guilabel:`First Contract Date`: select the start date for the vehicle's first contract using the drop-down calendar. Typically this is the day the vehicle is purchased or leased." +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:123 +msgid ":guilabel:`Catalog Value (VAT Incl.)`: enter the MSRP (Manufacturer's Suggested Retail Price) for the vehicle at the time of purchase or lease." +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:125 +msgid ":guilabel:`Purchase Value`: enter the purchase price or the value of the lease for the vehicle." +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:126 +msgid ":guilabel:`Residual Value`: enter the current value of the vehicle." +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:129 +msgid "The values listed above will affect the accounting department. It is recommended to check with the accounting department for more information and/or assistance with these values." +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:137 +msgid "Model tab" +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:139 +msgid "If the model for the new vehicle is already configured in the database, the :guilabel:`Model` tab will be populated with the corresponding information. If the model is not already in the database and the :guilabel:`Model` tab needs to be configured, :ref:`configure the new vehicle model `." +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:144 +msgid "Check the information in the :guilabel:`Model` tab to ensure it is accurate. For example, the color of the vehicle, or whether there is a trailer hitch installed or not, are examples of information that may need updating." +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:153 +msgid "Note tab" +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:155 +msgid "Enter any notes for the vehicle in this section." +msgstr "" + +#: ../../content/applications/hr/fleet/service.rst:3 +msgid "Services" +msgstr "" + +#: ../../content/applications/hr/fleet/service.rst:5 +msgid "To properly maintain a fleet of vehicles, regular maintenance as well as periodic repairs are needed. Scheduling repairs and managing services for an entire fleet is necessary to ensure all vehicles are in good working order when they are needed." +msgstr "" + +#: ../../content/applications/hr/fleet/service.rst:10 +msgid "Create a service record" +msgstr "" + +#: ../../content/applications/hr/fleet/service.rst:12 +msgid "To log a service, go to the main services dashboard by navigating to :menuselection:`Fleet app --> Fleet --> Services`. Click :guilabel:`Create` and a service form appears. Fill in the information on the form and click :guilabel:`Save`. The only two fields that are required to be populated are :guilabel:`Service Type` and :guilabel:`Vehicle`." +msgstr "" + +#: ../../content/applications/hr/fleet/service.rst:17 +msgid "The fields are:" +msgstr "" + +#: ../../content/applications/hr/fleet/service.rst:19 +msgid ":guilabel:`Description`: enter in a short description of the service." +msgstr "" + +#: ../../content/applications/hr/fleet/service.rst:20 +msgid ":guilabel:`Service Type`: select the type of service performed from the drop-down menu, or type in a new type of service and click either :guilabel:`Create` or :guilabel:`Create & Edit...`. This list is not pre-configured in Odoo. When creating a fleet and logging a service, the types of service need to be created." +msgstr "" + +#: ../../content/applications/hr/fleet/service.rst:24 +msgid ":guilabel:`Date`: using the calendar module, select the date the service was provided or is scheduled to be performed. Navigate to the desired month using the left and right arrow icons, then click on the date to select it." +msgstr "" + +#: ../../content/applications/hr/fleet/service.rst:27 +msgid ":guilabel:`Cost`: enter the cost of the service." +msgstr "" + +#: ../../content/applications/hr/fleet/service.rst:28 +msgid ":guilabel:`Vendor`: select the vendor who performed the service from the drop-down menu. If the vendor has not already been entered in the system, type in the vendor name and click either :guilabel:`Create` to add them, or :guilabel:`Create & Edit...` to create the vendor and edit the vendor form. The vendor form allows for other details aside form the name to be entered, such as contact information." +msgstr "" + +#: ../../content/applications/hr/fleet/service.rst:33 +msgid ":guilabel:`Vehicle`: select the vehicle that was serviced from the drop-down menu. When the vehicle is selected, the :guilabel:`Driver` field is populated, and the unit of measure for the :guilabel:`Mileage` field appears." +msgstr "" + +#: ../../content/applications/hr/fleet/service.rst:36 +msgid ":guilabel:`Driver`: the current driver listed for the selected vehicle is populated when the :guilabel:`Vehicle` is selected. If the driver needs to be changed, another driver can be selected from the drop-down menu." +msgstr "" + +#: ../../content/applications/hr/fleet/service.rst:39 +msgid ":guilabel:`Odometer Value`: enter the odometer reading when the service was done. The units of measure will either be in kilometers (:guilabel:`km`) or miles (:guilabel:`mi`). When the :guilabel:`Vehicle` is selected, the units of measure is populated. This comes from the vehicle form. To change from kilometers to miles, or vice versa, click the :guilabel:`External Link` button next to the vehicle selected in the :guilabel:`Vehicle` field. Change the unit of measure, then click :guilabel:`Save`. the unit of measure will be updated in the :guilabel:`Odometer Value` field." +msgstr "" + +#: ../../content/applications/hr/fleet/service.rst:46 +msgid ":guilabel:`Notes`: enter any notes for the repair in the notes tab at the bottom of the service form." +msgstr "" + +#: ../../content/applications/hr/fleet/service.rst:-1 +msgid "Enter the information for a new service. The required fields are Service Type and Vehicle." +msgstr "" + +#: ../../content/applications/hr/fleet/service.rst:54 +msgid "List of services" +msgstr "" + +#: ../../content/applications/hr/fleet/service.rst:56 +msgid "To view all services logged in the database, including old and new requests, go to :menuselection:`Fleet application --> Fleet --> Services`. All services appear in a list view, including all the details for each service." +msgstr "" + +#: ../../content/applications/hr/fleet/service.rst:60 +msgid "Each service listed displays the following information:" +msgstr "" + +#: ../../content/applications/hr/fleet/service.rst:62 +msgid ":guilabel:`Date`: the date service or repair was performed or is requested to be performed." +msgstr "" + +#: ../../content/applications/hr/fleet/service.rst:63 +msgid ":guilabel:`Description`: a short description of the specific type of service or repair performed to clarify the specific service." +msgstr "" + +#: ../../content/applications/hr/fleet/service.rst:65 +msgid ":guilabel:`Service Type`: the service or repair performed. This is selected from a list of services that must be configured." +msgstr "" + +#: ../../content/applications/hr/fleet/service.rst:67 +msgid ":guilabel:`Vehicle`: the specific vehicle the service was performed on." +msgstr "" + +#: ../../content/applications/hr/fleet/service.rst:68 +msgid ":guilabel:`Driver`: who the current driver is for the vehicle." +msgstr "" + +#: ../../content/applications/hr/fleet/service.rst:69 +msgid ":guilabel:`Vendor`: the specific vendor who performed the service or repair." +msgstr "" + +#: ../../content/applications/hr/fleet/service.rst:70 +msgid ":guilabel:`Cost`: the total cost for the service or repair." +msgstr "" + +#: ../../content/applications/hr/fleet/service.rst:71 +msgid ":guilabel:`Notes`: any information associated with the service or repair that is documented to add clarification." +msgstr "" + +#: ../../content/applications/hr/fleet/service.rst:73 +msgid ":guilabel:`Stage`: the status of the service or repair. Options are :guilabel:`New`, :guilabel:`Running`, :guilabel:`Canceled`, or :guilabel:`Done`." +msgstr "" + +#: ../../content/applications/hr/fleet/service.rst:-1 +msgid "The full list of services in the Odoo database." +msgstr "" + +#: ../../content/applications/hr/fleet/service.rst:81 +msgid "View services" +msgstr "" + +#: ../../content/applications/hr/fleet/service.rst:83 +msgid "It is recommended to view the list of services in one of several pre-configured ways to better view the information presented. In the top right corner of the list, there are several icons that when clicked, sort the data in different ways." +msgstr "" + +#: ../../content/applications/hr/fleet/service.rst:-1 +msgid "The icons in the top right corner than cn be clicked to present the information in\n" +"different ways." +msgstr "" + +#: ../../content/applications/hr/fleet/service.rst:93 +msgid "List view" +msgstr "" + +#: ../../content/applications/hr/fleet/service.rst:95 +msgid "The default view of the services is the list view. This presents all the services in chronological order, from oldest to newest, in a list." +msgstr "" + +#: ../../content/applications/hr/fleet/service.rst:98 +msgid "The information can be sorted by any column. At the top of each column, hover over the column name. An arrow appears to the right of the name. Click the arrow to sort the data by that specific column." +msgstr "" + +#: ../../content/applications/hr/fleet/service.rst:101 +msgid "The default sorting is descending alphabetical order (A to Z). Click the arrow again to reverse the order, and go in reverse alphabetical order (Z to A). The one exception to this sorting is the default :guilabel:`Date` column, which sorts the information in chronological order (January to December) instead of alphabetical order." +msgstr "" + +#: ../../content/applications/hr/fleet/service.rst:107 +#: ../../content/applications/hr/recruitment.rst:33 +msgid "Kanban view" +msgstr "" + +#: ../../content/applications/hr/fleet/service.rst:109 +msgid "To view services by their stage, click on the :guilabel:`Kanban icon`, which is the second icon in the top right, and appears as four black squares in a cube." +msgstr "" + +#: ../../content/applications/hr/fleet/service.rst:112 +msgid "All the services with the same status appear in the corresponding column, from :guilabel:`Running` to :guilabel:`Cancelled`. To change the status of a service, simply click and drag the service card to the desired stage." +msgstr "" + +#: ../../content/applications/hr/fleet/service.rst:117 +msgid "Graph view" +msgstr "" + +#: ../../content/applications/hr/fleet/service.rst:119 +msgid "Another way to view the data is in a graph. To view the graph, click the :guilabel:`Graph icon`, which is the third icon in the top right, and appears as a small graph." +msgstr "" + +#: ../../content/applications/hr/fleet/service.rst:122 +msgid "The graph displays the information in a graph where the X axis represents the :guilabel:`Date` and the Y axis represents the :guilabel:`Cost`. Each column represents a single month, and then is further organized by vehicle. Each vehicle is represented by a different color, and each month's bar is divided by each vehicle." +msgstr "" + +#: ../../content/applications/hr/fleet/service.rst:128 +msgid "Pivot view" +msgstr "" + +#: ../../content/applications/hr/fleet/service.rst:130 +msgid "The final way to view the service data is in a spreadsheet pivot table. Click on the :guilabel:`Pivot icon`, which is the last icon in the top right, and appears as a small spreadsheet." +msgstr "" + +#: ../../content/applications/hr/fleet/service.rst:133 +msgid "The data presented in the table shows the cost of each service or repair. The rows represent the vendors, and each vehicle that was serviced by them appears beneath each vendor. The column represent the different service types performed." +msgstr "" + +#: ../../content/applications/hr/fleet/service.rst:137 +msgid "The table can be inserted in a spreadsheet or downloaded. To add the pivot table to a spreadsheet in Odoo, click :guilabel:`Insert In Spreadsheet` and a pop-up appears. Select the spreadsheet the data should be added to from the drop-down menu, and click :guilabel:`Confirm`. The spreadsheet then loads on the screen. The spreadsheets are stored in Odoo's *Documents* application. To download the table in an `xlsx` format, click the :guilabel:`Download` icon." +msgstr "" + +#: ../../content/applications/hr/fleet/service.rst:-1 +msgid "Download the pivot table to an xlsx file, or insert the data in a spreadsheet in Odoo's\n" +"Documents application." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:6 +#: ../../content/applications/hr/payroll/reporting.rst:39 +msgid "Payroll" +msgstr "" + +#: ../../content/applications/hr/payroll.rst:8 +msgid "Odoo *Payroll* is used to process work entries and create payslips for employees, including both regular pay and commission. Payroll works in conjunction with other Odoo apps, such as *Employees*, *Timesheets*, *Time Off*, and *Attendances*." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:12 +msgid "The *Payroll* app helps ensure there are no issues or conflicts when validating work entries, handles country-specific localizations to ensure that payslips follow local rules and taxes, and allows for salary assignments. Payroll configuration is critical to ensure accurate and timely processing of payslips." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:20 msgid "To access the *Settings*, go to :menuselection:`Payroll --> Configuration --> Settings`. Whether or not payslips are posted in accounting, and whether SEPA payments are created, is selected here." msgstr "" -#: ../../content/applications/hr/payroll.rst:22 +#: ../../content/applications/hr/payroll.rst:23 msgid "The :guilabel:`Settings` screen is where localization settings are configured. *Localizations* are country-specific settings pre-configured in Odoo at the creation of the database, and account for all taxes, fees, and allowances for that particular country. The :guilabel:`Localization` section of the :guilabel:`Settings` includes a detailed view of all benefits provided to employees." msgstr "" @@ -501,385 +1364,563 @@ msgstr "" msgid "Settings available for Payroll." msgstr "" -#: ../../content/applications/hr/payroll.rst:31 +#: ../../content/applications/hr/payroll.rst:32 msgid "Any country-specific localizations are set up in the :guilabel:`Localization` section of the :guilabel:`Settings` screen. All localization items are pre-populated when the country is specified during the creation of the database. It is not recommended to alter the localization settings unless specifically required." msgstr "" -#: ../../content/applications/hr/payroll.rst:39 +#: ../../content/applications/hr/payroll.rst:38 +msgid "Odoo can handle a multi-company configuration. This is generally done when there is a main company or office location, such as a headquarters, and there are other offices/branches around the country or globe, that fall under that main company or headquarters. In Odoo, each company, including the headquarters, would be setup as their own company/branch using the multi-company method." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:44 +msgid "Each individual company can have a different localization setting configured for that specific company, since company locations can vary and be located anywhere in the world, where rules and laws differ. For more information on companies refer to :doc:`this documentation <../general/users/companies>` on setting up companies." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:52 #: ../../content/applications/hr/payroll/work_entries.rst:3 msgid "Work entries" msgstr "" -#: ../../content/applications/hr/payroll.rst:41 +#: ../../content/applications/hr/payroll.rst:54 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:46 +#: ../../content/applications/hr/payroll.rst:59 msgid ":doc:`Manage work entries `" msgstr "" -#: ../../content/applications/hr/payroll.rst:49 +#: ../../content/applications/hr/payroll.rst:62 msgid "Work entry types" msgstr "" -#: ../../content/applications/hr/payroll.rst:51 +#: ../../content/applications/hr/payroll.rst:64 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:56 -msgid "To view the current work entry types available, go to :menuselection:`Payroll --> Configuration --> Work Entry Types`." -msgstr "" - -#: ../../content/applications/hr/payroll.rst:59 -msgid "Each work entry type has a code to aid in the creation of payslips, and ensure all taxes and fees are correctly entered." -msgstr "" - -#: ../../content/applications/hr/payroll.rst:-1 -msgid "List of all work entry types currently available." -msgstr "" - -#: ../../content/applications/hr/payroll.rst:67 -msgid "New work entry type" -msgstr "" - #: ../../content/applications/hr/payroll.rst:69 -msgid "To create a new work entry type, click the :guilabel:`Create` button. Enter the information on the form:" +msgid "To view the current work entry types available, go to :menuselection:`Payroll --> Configuration --> Work Entries --> Work Entry Types`." msgstr "" #: ../../content/applications/hr/payroll.rst:72 -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:74 -msgid ":guilabel:`Code`: This code appears with the work entry type on timesheets and payslips. Since the code is used in conjunction with the *Accounting* application, it is advised to check with the accounting department for a code to use." -msgstr "" - -#: ../../content/applications/hr/payroll.rst:77 -msgid ":guilabel:`Sequence`: The sequence determines the order that the work entry is computed in the payslip list." -msgstr "" - -#: ../../content/applications/hr/payroll.rst:79 -msgid "Check boxes: If any of the items in the list applies to the work entry, check off the box by clicking it. If :guilabel:`Time Off` is checked off, a :guilabel:`Time Off Type` field appears. This field has a drop-down menu to select the specific type of time off, or a new type of time off can be entered." +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 "" #: ../../content/applications/hr/payroll.rst:-1 -msgid "New work entry type form." +msgid "List of all work entry types currently available for use, with the payroll code and color." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:80 +msgid "New work entry type" +msgstr "" + +#: ../../content/applications/hr/payroll.rst:82 +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:86 +msgid "General information section" msgstr "" #: ../../content/applications/hr/payroll.rst:88 -msgid ":guilabel:`Rounding`: The rounding method determines how timesheet entries are displayed on the payslip." +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:91 -msgid ":guilabel:`No Rounding`: A timesheet entry is not modified." -msgstr "" - -#: ../../content/applications/hr/payroll.rst:92 -msgid ":guilabel:`Half Day`: A timesheet entry is rounded to the closest half day amount." +#: ../../content/applications/hr/payroll.rst:90 +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:93 -msgid ":guilabel:`Day`: A timesheet entry is rounded to the closest full day amount." +msgid ":guilabel:`DMFA code`: This code is used to identify :abbr:`DMFA (De Multifunctionele Aangifte)` entries on a corresponding DMFA report. The DMFA 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:96 -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." +#: ../../content/applications/hr/payroll.rst:97 +msgid ":guilabel:`External Code`: This code is used for exporting data to a third-party payroll service. Check with the third-party being used in order to determine the :guilabel:`External Code` to enter for the new work entry type." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:100 +msgid ":guilabel:`SDWorx code`: This code is only for companies that use SDWorx, a payroll service provider." msgstr "" #: ../../content/applications/hr/payroll.rst:102 -msgid "Working times" +msgid ":guilabel:`Color`: Select a color for the particular work entry type." msgstr "" -#: ../../content/applications/hr/payroll.rst:104 -msgid "To view the currently configured working times, go to :menuselection:`Payroll --> Configuration --> Working Times`. The working times that are available for an employee's contracts and work entries are found in this list." +#: ../../content/applications/hr/payroll.rst:105 +msgid "Display in payslip section" msgstr "" -#: ../../content/applications/hr/payroll.rst:108 -msgid "Working times are company-specific. Each company must identify each type of working time they use. For example, an Odoo database containing multiple companies that use a standard 40-hour work week needs to have a separate working time entry for each company that uses the 40-hour standard work week." +#: ../../content/applications/hr/payroll.rst:107 +msgid ":guilabel:`Rounding`: The rounding method selected determines how quantities on timesheet entries are displayed on the payslip." msgstr "" -#: ../../content/applications/hr/payroll.rst:-1 -msgid "All working times currently set up in the database." +#: ../../content/applications/hr/payroll.rst:110 +msgid ":guilabel:`No Rounding`: A timesheet entry is not modified." msgstr "" -#: ../../content/applications/hr/payroll.rst:118 -msgid "New working time" +#: ../../content/applications/hr/payroll.rst:111 +msgid ":guilabel:`Half Day`: A timesheet entry is rounded to the closest half day amount." msgstr "" -#: ../../content/applications/hr/payroll.rst:120 -msgid "To create a new working time, click the :guilabel:`Create` button. Enter the information on the form." +#: ../../content/applications/hr/payroll.rst:112 +msgid ":guilabel:`Day`: A timesheet entry is rounded to the closest full day amount." msgstr "" -#: ../../content/applications/hr/payroll.rst:-1 -msgid "New working type form." +#: ../../content/applications/hr/payroll.rst:115 +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:127 -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." +#: ../../content/applications/hr/payroll.rst:121 +msgid "Unpaid section" +msgstr "" + +#: ../../content/applications/hr/payroll.rst:123 +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." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:129 +msgid "Valid for advantages section" msgstr "" #: ../../content/applications/hr/payroll.rst:131 -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." +msgid ":guilabel:`Meal Voucher`: If the work entry should count towards a meal voucher, check the box." msgstr "" -#: ../../content/applications/hr/payroll.rst:137 -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`." +#: ../../content/applications/hr/payroll.rst:132 +msgid ":guilabel:`Representation Fees`: If the work entry should count towards representation fees, check the box." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:134 +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:138 +msgid "Time off options section" msgstr "" #: ../../content/applications/hr/payroll.rst:140 -msgid "If the working time should be in a two-week configuration, click the :guilabel:`Switch To 2 Week Calendar` button. This creates entries for an :guilabel:`Even week` and an :guilabel:`Odd week`." +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. 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. 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:144 -msgid "Salary" +#: ../../content/applications/hr/payroll.rst:146 +msgid ":guilabel:`Keep Time Off Right`: This is for Belgian-specific companies only, and will not appear for other localizations. Check this box if the work entry is for time off that will affect 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 will receive or accrue the following year." msgstr "" -#: ../../content/applications/hr/payroll.rst:149 -msgid "Structure types" +#: ../../content/applications/hr/payroll.rst:153 +msgid "Reporting section" msgstr "" -#: ../../content/applications/hr/payroll.rst:151 -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)." +#: ../../content/applications/hr/payroll.rst:155 +msgid ":guilabel:`Unforeseen Absence`: If the work entry should be visible on the unforeseen absences report, check this box." msgstr "" -#: ../../content/applications/hr/payroll.rst:157 -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." +#: ../../content/applications/hr/payroll.rst:-1 +msgid "New work entry type form with all fields to be filled in." msgstr "" #: ../../content/applications/hr/payroll.rst:163 -msgid "The different structure types can be seen by going to :menuselection:`Payroll --> Configuration --> Structure Types`." +msgid "Working schedules" msgstr "" -#: ../../content/applications/hr/payroll.rst:166 +#: ../../content/applications/hr/payroll.rst:165 +msgid "To view the currently configured working schedules, go to :menuselection:`Payroll --> 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:169 +msgid "Working schedules are company-specific. Each company must identify each type of working schedule they use." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:173 +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:176 +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 "" + +#: ../../content/applications/hr/payroll.rst:-1 +msgid "All working schedules available to use currently set up in the database for the company." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:184 +msgid "New working schedule" +msgstr "" + +#: ../../content/applications/hr/payroll.rst:186 +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:189 +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:193 +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:199 +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:202 +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 "" + +#: ../../content/applications/hr/payroll.rst:-1 +msgid "New working schedule form." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:216 +msgid "Structure types" +msgstr "" + +#: ../../content/applications/hr/payroll.rst:218 +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:224 +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:230 +msgid "The different structure types can be seen by going to :menuselection:`Payroll --> Configuration --> Salary --> Structure Types`." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:233 msgid "There are two default structure types configured in Odoo: *Employee* and *Worker*. Typically, *Employee* is used for salaried employees, which is why the wage type is *Monthly Fixed Wage*, and *Worker* is typically used for employees paid by the hour, so the wage type is *Hourly Wage*." msgstr "" #: ../../content/applications/hr/payroll.rst:-1 -msgid "List of all structure types." +msgid "List of all currently configured structure types available to use." msgstr "" -#: ../../content/applications/hr/payroll.rst:174 -msgid "Click the :guilabel:`Create` button to make a new structure type. Most fields are pre-populated, but all fields can be edited. Once the fields are edited, click the :guilabel:`Save` button to save the changes, or click :guilabel:`Discard` to delete the entry." +#: ../../content/applications/hr/payroll.rst:242 +msgid "New structure type" +msgstr "" + +#: ../../content/applications/hr/payroll.rst:244 +msgid "To make a new structure type, click the :guilabel:`New` button and a structure type form appears. Enter the information in the fields. Most fields are pre-populated, but all the fields can be modified." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:248 +msgid ":guilabel:`Structure Type`: Enter the name for the new structure type, such as 'Employee' or 'Worker'." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:250 +msgid ":guilabel:`Country`: Select the country that the new structure type applies to from the drop-down menu." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:252 +msgid ":guilabel:`Wage Type`: Select what type of wage the new structure type will use, either :guilabel:`Monthly Fixed Wage` or :guilabel:`Hourly Wage`. If the wage type is going to be used for salaried employees who receive the same wage every pay period, select :guilabel:`Monthly Fixed Wage`. If the wage type is going 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:257 +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 type of structure type is paid out." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:261 +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:266 +msgid ":guilabel:`Regular Pay Structure`: Type in the name for the regular pay structure." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:267 +msgid ":guilabel:`Default Work Entry Type`: Select the default type of work entry the new structure type will fall under from the drop-down menu. 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`, and :guilabel:`Out Of Contract`." msgstr "" #: ../../content/applications/hr/payroll.rst:-1 -msgid "New structure type box." +msgid "New structure type form to fill out when creating a new structure type." msgstr "" -#: ../../content/applications/hr/payroll.rst:183 +#: ../../content/applications/hr/payroll.rst:280 +msgid "New default working hours" +msgstr "" + +#: ../../content/applications/hr/payroll.rst:282 +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 will pop 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 filled out, click :guilabel:`Save & Close`." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:288 +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:290 +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 shard between companies. Each company needs to have their own working hours set." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:293 +msgid ":guilabel:`Average Hour Per Day`: The average hours per day field will be auto-populated based on the working hours configured in the *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:297 +msgid ":guilabel:`Timezone`: Select the timezone that the new default working hours will be used for from the drop-down menu." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:299 +msgid ":guilabel:`Company Full Time`: Enter the number of hours per week an employee would need to work in order 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:303 +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 *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:307 +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 working hours tab is pre-populated with a default 40-hour week, with each day divided into three timed sections. 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. 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:316 +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 will change the working hours tab to display two weeks of working times that can be adjusted." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:322 msgid "Structures" msgstr "" -#: ../../content/applications/hr/payroll.rst:185 +#: ../../content/applications/hr/payroll.rst:324 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:188 +#: ../../content/applications/hr/payroll.rst:327 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:192 -msgid "To view all the various structures for each structure type, go to :menuselection:`Payroll --> Configuration --> Structures`." +#: ../../content/applications/hr/payroll.rst:331 +msgid "To view all the various structures for each structure type, go to :menuselection:`Payroll --> Configuration --> Salary --> Structures`." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:334 +msgid "Each :ref:`structure type ` lists the various structures associated with it. Each structure contains a set of rules that define it." msgstr "" #: ../../content/applications/hr/payroll.rst:-1 msgid "All available salary structures." msgstr "" -#: ../../content/applications/hr/payroll.rst:199 -msgid "Each :ref:`structure type ` lists the various structures associated with it. Each structure contains a set of rules that define it." -msgstr "" - -#: ../../content/applications/hr/payroll.rst:202 +#: ../../content/applications/hr/payroll.rst:341 msgid "Click on a structure to view its :guilabel:`Salary Rules`. These rules are what calculate the payslip for the employee." msgstr "" #: ../../content/applications/hr/payroll.rst:-1 -msgid "Salary structure details for Regular Pay." +msgid "Salary structure details for Regular Pay, listing all the specific Salary Rules." msgstr "" -#: ../../content/applications/hr/payroll.rst:210 +#: ../../content/applications/hr/payroll.rst:349 msgid "Rules" msgstr "" -#: ../../content/applications/hr/payroll.rst:212 -msgid "Each structure has a set of *salary rules* to follow for accounting purposes. These rules are configured by the localization, and affect the *Accounting* application, so modifications to the default rules, or the creation of new rules, should only be done when necessary." +#: ../../content/applications/hr/payroll.rst:351 +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:216 -msgid "To view all the rules, go to :menuselection:`Payroll app --> Configuration --> Rules`. Click on a structure (such as :guilabel:`Regular Pay`) to view all the rules." +#: ../../content/applications/hr/payroll.rst:355 +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:-1 -msgid "Rules for each salary structure type." +#: ../../content/applications/hr/payroll.rst:358 +msgid "To make a new rule, click :guilabel:`New`. A new rule form appears. Enter the information in the fields." msgstr "" -#: ../../content/applications/hr/payroll.rst:223 -msgid "To make a new rule, click :guilabel:`Create`. A new rule form appears. Enter the information in the fields, then click :guilabel:`Save`." -msgstr "" - -#: ../../content/applications/hr/payroll.rst:-1 -msgid "Enter the information for the new rule." -msgstr "" - -#: ../../content/applications/hr/payroll.rst:230 +#: ../../content/applications/hr/payroll.rst:361 msgid "The required fields for a rule are:" msgstr "" -#: ../../content/applications/hr/payroll.rst:232 +#: ../../content/applications/hr/payroll.rst:363 msgid ":guilabel:`Name`: Enter a name for the rule." msgstr "" -#: ../../content/applications/hr/payroll.rst:233 +#: ../../content/applications/hr/payroll.rst:364 msgid ":guilabel:`Category`: Select a category the rule applies to from the drop-down menu, or enter a new one." msgstr "" -#: ../../content/applications/hr/payroll.rst:235 -msgid ":guilabel:`Code`: Enter a code to be used for this new rule. It is recommended to coordinate with the accounting department for a code as this will affect them." +#: ../../content/applications/hr/payroll.rst:366 +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 will affect accounting reports and payroll processing." msgstr "" -#: ../../content/applications/hr/payroll.rst:237 +#: ../../content/applications/hr/payroll.rst:369 msgid ":guilabel:`Salary Structure`: Select a salary structure the rule applies to from the drop-down menu, or enter a new one." msgstr "" -#: ../../content/applications/hr/payroll.rst:239 +#: ../../content/applications/hr/payroll.rst:371 msgid ":guilabel:`Condition Based on`: In the :guilabel:`General` tab, select from the drop-down menu whether the rule is :guilabel:`Always True` (always applies), a :guilabel:`Range` (applies to a specific range, which is entered beneath the selection), or a :guilabel:`Python Expression` (the code is entered beneath the selection)." msgstr "" -#: ../../content/applications/hr/payroll.rst:243 +#: ../../content/applications/hr/payroll.rst:375 msgid ":guilabel:`Amount Type`: In the :guilabel:`General` tab, select from the drop-down menu whether the amount is a :guilabel:`Fixed Amount`, a :guilabel:`Percentage (%)`, or a :guilabel:`Python Code`. Depending on what is selected, the fixed amount, percentage, or Python code needs to be entered next." msgstr "" -#: ../../content/applications/hr/payroll.rst:249 +#: ../../content/applications/hr/payroll.rst:-1 +msgid "Enter the information for the new rule on the new rule form." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:385 msgid "Rule parameters" msgstr "" -#: ../../content/applications/hr/payroll.rst:252 -msgid "Currently, the :guilabel:`Rule Parameters` feature found inside the :menuselection:`Payroll app --> Configuration` menu is still in development and only serves a specific use case for Belgian markets. The documentation will be updated when this section has matured to more markets." +#: ../../content/applications/hr/payroll.rst:388 +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:257 +#: ../../content/applications/hr/payroll.rst:394 msgid "Other input types" msgstr "" -#: ../../content/applications/hr/payroll.rst:259 -msgid "When creating payslips, it is sometimes necessary to add other entries for specific circumstances, like expenses, reimbursements, or deductions. These other inputs can be configured by going to :menuselection:`Payroll --> Configuration --> Other Input Types`." +#: ../../content/applications/hr/payroll.rst:396 +msgid "When creating payslips, it is sometimes necessary to add other entries for specific circumstances, like expenses, reimbursements, or deductions. These other inputs can be configured by going to :menuselection:`Payroll --> Configuration --> Salary --> Other Input Types`." msgstr "" #: ../../content/applications/hr/payroll.rst:-1 -msgid "Other input types for payroll." +msgid "A list of other input types for payroll that can be selected when creating a new entry for\n" +"a payslip." msgstr "" -#: ../../content/applications/hr/payroll.rst:267 -msgid "To create a new input type, click the :guilabel:`Create` button. Enter the :guilabel:`Description`, the :guilabel:`Code`, and which structure it applies to in the :guilabel:`Availability in Structure` field. Click the :guilabel:`Save` button to save the changes, or click :guilabel:`Discard` to delete the entry." +#: ../../content/applications/hr/payroll.rst:405 +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:410 +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 "" #: ../../content/applications/hr/payroll.rst:-1 msgid "Create a new Input Type." msgstr "" -#: ../../content/applications/hr/payroll.rst:277 +#: ../../content/applications/hr/payroll.rst:419 msgid "Salary package configurator" msgstr "" -#: ../../content/applications/hr/payroll.rst:279 -msgid "The various options under the :guilabel:`Salary Package Configurator` section of the :menuselection:`Payroll --> Configuration` menu all affect an employee's potential salary. These sections (:guilabel:`Advantages`, :guilabel:`Personal Info`, and :guilabel:`Resume`) specify what benefits can be offered to an employee in their salary package." +#: ../../content/applications/hr/payroll.rst:421 +msgid "The various options under the :guilabel:`Salary Package Configurator` section of the :menuselection:`Payroll --> Configuration --> Salary Package Configurator` menu all affect an employee's potential salary. These sections (:guilabel:`Advantages`, :guilabel:`Personal Info`, :guilabel:`Resume`, and :guilabel:`Offers`) specify what benefits can be offered to an employee in their salary package." msgstr "" -#: ../../content/applications/hr/payroll.rst:284 +#: ../../content/applications/hr/payroll.rst:427 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:290 +#: ../../content/applications/hr/payroll.rst:433 msgid "Advantages" msgstr "" -#: ../../content/applications/hr/payroll.rst:292 -msgid "When offering potential employees a position, there can be certain *advantages* set in Odoo in addition to the salary to make the offer more appealing (such as extra time off, access to a company car, reimbursement for a phone or internet, etc.)." +#: ../../content/applications/hr/payroll.rst:435 +msgid "When offering potential employees a position, there can be certain *advantages* or 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:296 -msgid "To see the advantages, go to :menuselection:`Payroll --> Configuration --> Advantages`. Advantages are grouped by :guilabel:`Structure type`." +#: ../../content/applications/hr/payroll.rst:439 +msgid "To see the advantages, go to :menuselection:`Payroll --> Configuration --> Salary Package Configurator --> Advantages`. Advantages are grouped by :guilabel:`Structure type`, and the advantage listed for a particular structure type is only available for that specific structure." msgstr "" #: ../../content/applications/hr/payroll.rst:-1 -msgid "Settings available for payroll." +msgid "A list view of all the advantages or benefits that is available for each structure type." msgstr "" -#: ../../content/applications/hr/payroll.rst:303 -msgid "To make a new advantage, click the :guilabel:`Create` button. Enter the information in the fields, then click the :guilabel:`Save` button to save the changes, or click :guilabel:`Discard` to delete the entry." +#: ../../content/applications/hr/payroll.rst:448 +msgid "A company has two structure types, one labeled :guilabel:`Employee`, and anther labeled :guilabel:`Intern`. The :guilabel:`Employee` structure type contains an advantage of using a company car, while the :guilabel:`Intern` structure type does not. Instead, the :guilabel:`Intern` structure type has a meal voucher advantage available, while the :guilabel:`Employee` structure type does not." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:454 +msgid "A person hired under the :guilabel:`Employee` structure type can use a company car, but cannot have meal vouchers. The opposite is true for someone hired under the :guilabel:`Intern` structure type. They would have meal vouchers available to them, not the use of a company car." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:458 +msgid "To make a new advantage, click the :guilabel:`New` button, and enter the information in the fields. The required fields for an advantage are:" +msgstr "" + +#: ../../content/applications/hr/payroll.rst:461 +msgid ":guilabel:`Name`: Enter the name for the advantage." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:462 +msgid ":guilabel:`Advantage Field`: Select from the drop-down menu what field in the payslip this advantage appears under." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:464 +msgid ":guilabel:`Advantage Type`: Select from the drop-down menu what type of advantage the benefit is. Select from :guilabel:`Monthly Benefit in Kind`, :guilabel:`Monthly Advantages in Net`, :guilabel:`Monthly Advantages in Cash`, or :guilabel:`Yearly Advantages in Cash`." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:467 +msgid ":guilabel:`Salary Structure Type`: Select from the drop-down menu which salary structure type this advantage applies to." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:469 +msgid ":guilabel:`Display Type`: Select from the drop-down menu how this advantage is displayed." msgstr "" #: ../../content/applications/hr/payroll.rst:-1 msgid "List of advantages employee's can have." msgstr "" -#: ../../content/applications/hr/payroll.rst:311 -msgid "The required fields for an advantage are:" -msgstr "" - -#: ../../content/applications/hr/payroll.rst:313 -msgid ":guilabel:`Name`: Enter the name for the advantage." -msgstr "" - -#: ../../content/applications/hr/payroll.rst:314 -msgid ":guilabel:`Advantage Field`: Select from the drop-down menu what field in the payslip this advantage appears under." -msgstr "" - -#: ../../content/applications/hr/payroll.rst:316 -msgid ":guilabel:`Advantage Type`: Select from the drop-down menu what type of advantage the benefit is. Select from :guilabel:`Monthly Benefit in Kind`, :guilabel:`Monthly Advantages in Net`, :guilabel:`Monthly Advantages in Cash`, or :guilabel:`Yearly Advantages in Cash`." -msgstr "" - -#: ../../content/applications/hr/payroll.rst:319 -msgid ":guilabel:`Salary Structure Type`: Select from the drop-down menu which salary structure type this advantage applies to." -msgstr "" - -#: ../../content/applications/hr/payroll.rst:323 +#: ../../content/applications/hr/payroll.rst:476 msgid "Personal info" msgstr "" -#: ../../content/applications/hr/payroll.rst:325 -msgid "Every employee in Odoo has an *employee card* that includes all of their personal information, resume, work information, and documents. To view an employee's card, go to the main :menuselection:`Payroll` app dashboard, and click on the employee's card, or go to :menuselection:`Payroll --> Employees --> Employees` and click on the employee's card. Employee cards can also be viewed by going to the :menuselection:`Employees` app." +#: ../../content/applications/hr/payroll.rst:478 +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:332 +#: ../../content/applications/hr/payroll.rst:482 +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:486 +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:490 msgid "An employee card can be thought of as an employee personnel file." msgstr "" -#: ../../content/applications/hr/payroll.rst:334 -msgid "The *Personal Information* section lists all of the fields that are available to enter on the employee's card. To access this section, go to :menuselection:`Payroll --> Configuration --> Personal Info`." +#: ../../content/applications/hr/payroll.rst:492 +msgid "The *Personal Information* section lists all of the fields that are available to enter on the employee's card. To access this section, go to :menuselection:`Payroll --> Configuration --> Salary Package Configurator --> Personal Info`." msgstr "" #: ../../content/applications/hr/payroll.rst:-1 -msgid "Personal information that appear on employee cards to enter." +msgid "A list of all the personal information that appears on employee card to enter." msgstr "" -#: ../../content/applications/hr/payroll.rst:342 -msgid "To edit an entry, select it from the list. Then, click the :guilabel:`Edit` button, and modify the entry. When done, click :guilabel:`Save` or :guilabel:`Discard` to save the information or cancel the edits." +#: ../../content/applications/hr/payroll.rst:500 +msgid "To edit a personal info entry, select the entry from the list, and modify the personal info. To create a new personal info entry, click the :guilabel:`New` button." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:503 +msgid "The required fields, aside from entering the :guilabel:`Information` name, are :guilabel:`Related Model`, :guilabel:`Related Field`, and :guilabel:`Category`. 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. 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 going to be stored in the backed. 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:512 +msgid "The two most important fields on the personal info form are :guilabel:`Is Required` and :guilabel:`Display Type`. Checking the :guilabel:`Is Required` box makes the field mandatory on the employee's card. The :guilabel:`Display Type` drop-down menu allows for the information to be entered in a variety of ways, from a :guilabel:`Text` box, to a customizable :guilabel:`Radio` button, a :guilabel:`Checkbox`, a :guilabel:`Document`, and more." msgstr "" #: ../../content/applications/hr/payroll.rst:-1 msgid "New personal information entry." msgstr "" -#: ../../content/applications/hr/payroll.rst:350 -msgid "The two most important fields on the personal info form are :guilabel:`Is Required` and :guilabel:`Display Type`. Checking the :guilabel:`Is Required` box makes the field mandatory on the employee's card." -msgstr "" - -#: ../../content/applications/hr/payroll.rst:354 -msgid "The :guilabel:`Display Type` drop-down menu allows for the information to be entered in a variety of ways, from a :guilabel:`Text` box, to a customizable :guilabel:`Radio` button, a :guilabel:`Checkbox`, a :guilabel:`Document`, and more." -msgstr "" - -#: ../../content/applications/hr/payroll.rst:358 -msgid "Once the information is entered, click the :guilabel:`Save` button to save the entry." -msgstr "" - -#: ../../content/applications/hr/payroll.rst:361 +#: ../../content/applications/hr/payroll.rst:523 msgid "Resume" msgstr "" -#: ../../content/applications/hr/payroll.rst:364 -msgid "Currently, the :guilabel:`Resume` feature found inside the :menuselection:`Payroll app --> Configuration` menu is still in development and only serves a specific use case for Belgian markets. The documentation will be updated when this section has matured to more markets." +#: ../../content/applications/hr/payroll.rst:526 +msgid "Currently, the :guilabel:`Resume` feature found inside the :menuselection:`Payroll app --> Configuration --> Salary Package Configurator --> Resume` 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:532 +msgid "Offers" +msgstr "" + +#: ../../content/applications/hr/payroll.rst:534 +msgid "When a candidate is offered a position, there are several items that need to be tracked in order for a business to stay organized, such as where in the offer process the candidate is, how long the offer is valid for, as well as all the offer details. These details are all stored in each *offers* record." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:539 +msgid "To view all offers, go to :menuselection:`Payroll --> Configuration --> Salary Package Configurator --> Offers`. All offers that have been sent to either potential candidates or current employees appears in this list. The status, offer start date and expiration date, amount of the contract, and more, can all be found in this list. Offers sent via the :guilabel:`Recruitment` application appear here, but there is an option to create a new offer from the :guilabel:`Payroll` application as well." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:-1 +msgid "A list of all offers given to a current employee or potential candidate along with the\n" +"status of the offer." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:550 +msgid "To create a new offer, click the :guilabel:`New` button. The two required fields are the :guilabel:`Contract Template`, and the :guilabel:`Company`. Select the :guilabel:`Contract Template` and :guilabel:`Company` from the drop-down menus. Fill in any other details for the offer, such as the :guilabel:`Job Title`, :guilabel:`Department`, the :guilabel:`Contract Start Date` and the :guilabel:`Offer Validity Date`." msgstr "" #: ../../content/applications/hr/payroll/contracts.rst:3 @@ -1586,6 +2627,178 @@ msgstr "" msgid "Once all the commissions are properly entered, click the :guilabel:`Generate Payslips` button to create the commission payslips." msgstr "" +#: ../../content/applications/hr/payroll/reporting.rst:3 +#: ../../content/applications/hr/referrals.rst:754 +msgid "Reporting" +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:5 +msgid "The :guilabel:`Reporting` section of the *Payroll* app offers a variety of reports to choose from. The :guilabel:`Payroll`, :guilabel:`Meal Vouchers`, :guilabel:`Attachment of Salary`, and :guilabel:`DMFA` reports are universal and available for all companies regardless of location. The :guilabel:`Paid Time Off Allocation`, :guilabel:`273S Sheet`, and :guilabel:`274.XX Sheets` reports are specific to Belgian companies only." +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:11 +msgid "To view a report, go to :menuselection:`Payroll --> Reporting` and click on the specific report." +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:-1 +msgid "Report dashboard view." +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:17 +msgid "If a report is unavailable to a company, a user error pops up, stating `You must be logged in to a Belgian company to use this feature.`" +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:20 +msgid "At the top of each report, click on :guilabel:`Filters` to display the optional filters for the specific report. Filters show information that matches the specific filter parameters. For example, when selecting the :guilabel:`Last 365 Day Payslip` filter, only payslips for the last 365 days appear. All reports have the option to add a custom filter, and each have different default custom filter options. Select the parameters, then click the :guilabel:`Apply` button." +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:30 +msgid "Clicking on :guilabel:`Favorites` displays three options: :guilabel:`Save the current search`, :guilabel:`Add the search to the dashboard`, or :guilabel:`Insert the search to a Google spreadsheet`." +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:-1 +msgid "Favorite options for reports." +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:41 +msgid "Click on :menuselection:`Payroll --> Reporting --> Payroll` to display the :guilabel:`Payroll Analysis` report." +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:48 +msgid "This shows all the payslips generated in the last 365 days. The report can display metrics for a variety of parameters. Click the :guilabel:`Measures` box to view a drop-down menu with the various options to display. The options available include: :guilabel:`# Payslip`, :guilabel:`Basic Wage`, :guilabel:`Basic Wage for Time Off`, :guilabel:`Days of Paid Time Off`, :guilabel:`Days of Unforeseen Absence`, :guilabel:`Days of Unpaid Time Off`, :guilabel:`Gross Wage`, :guilabel:`Net Wage`, :guilabel:`Number of Days`, :guilabel:`Number of Hours`, :guilabel:`Work Days`, :guilabel:`Work Hours`, and :guilabel:`Count`." +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:61 +msgid "Line chart" +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:63 +msgid "A line chart is the default view for the *Payroll Analysis* report. If a different view was selected, click on the :guilabel:`Line Chart` icon (middle icon) in the menu bar to change the view back to a line chart. An option to display the line chart in ascending or descending order appears at the end of the options." +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:73 +msgid "Bar chart" +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:75 +msgid "To display the data in a bar chart, click on the :guilabel:`Bar Chart` icon (first icon) in the menu bar." +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:82 +msgid "Click the :guilabel:`Stacked` icon to view the bar chart in a stacked format (where multiple values appear in each column). An option to display the columns in ascending or descending order appears at the end of the options." +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:87 +msgid "Clicking an option enables it. To disable the option, click it again. When the option is enabled it appears grey. When it is inactive, it appears white." +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:91 +msgid "Pie chart" +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:93 +msgid "To display the data in a pie chart, click on the :guilabel:`Pie Chart` icon (last icon) in the menu bar. There are no additional options available in this view." +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:101 +msgid "Pivot table" +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:103 +msgid "The bottom half of the :guilabel:`Payroll Analysis` dashboard presents a pivot table no matter which type of chart is selected for the top of the dashboard. The default information displayed is the number of payslips, net wage, gross wage, days of paid time off, and days of unpaid time off. The information is divided by department. To display more information on the report, select the :guilabel:`Measures` drop-down menu, then click on any other items to display." +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:113 +msgid "To sort the entries by a specific column, such as :guilabel:`Net Wage`, click on the column name twice. The first click selects the column, and the second click sorts the information in descending order." +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:-1 +msgid "To sort information by descending order, click the column head twice." +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:121 +#: ../../content/applications/hr/payroll/reporting.rst:172 +msgid "To export the data in an XLSX format, click the :guilabel:`Download xlsx` icon. The information will be downloaded into an Excel spreadsheet." +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:-1 +msgid "Download an Excel spreadsheet of the data by clicking the download button." +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:128 +#: ../../content/applications/hr/payroll/reporting.rst:179 +msgid "The data can be inserted into a spreadsheet by clicking the :guilabel:`Insert in Spreadsheet` button. A pop-up appears asking which spreadsheet to place the information in. Select an existing spreadsheet or enter the name for a new spreadsheet. Click the :guilabel:`Confirm` button to move to a spreadsheet view with all the information populated." +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:-1 +msgid "Send the data to a spreadsheet." +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:137 +msgid "Once in the spreadsheet view, click on :guilabel:`File`, then select :guilabel:`Save` to save the data, or :guilabel:`Save as Template` to save the setting as a template to use in the future." +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:141 +#: ../../content/applications/hr/payroll/reporting.rst:188 +msgid "The *Documents* application must be installed in order to use the :guilabel:`Insert in Spreadsheet` option." +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:146 +msgid "Meal Vouchers" +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:148 +msgid ":guilabel:`Meal Vouchers` provides an overview of the meal vouchers used by employees, and can be shown by :guilabel:`Day`, :guilabel:`Week`, :guilabel:`Month`, :guilabel:`Quarter`, or :guilabel:`Year`. The default view is by month." +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:-1 +msgid "Meal voucher" +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:156 +msgid "To change the displayed view, click on :guilabel:`Total`. The data collapses, showing only the count column. Click on :guilabel:`Total` again, then hover over :guilabel:`Day`, then click on one of the other time-period options available." +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:164 +msgid "It is possible to compare the current meal voucher report to the one for the previous time period or the previous year. To view these comparisons, click on the :guilabel:`Comparison` drop-down menu at the top, then select either :guilabel:`Date: Previous Period` or :guilabel:`Date: Previous Year`." +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:184 +msgid "Once in the spreadsheet view, click on :guilabel:`File`, then select :guilabel:`Save` to save the data, or :guilabel:`Save as Template` to save the settings as a template to use in the future." +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:192 +msgid "Attachment of Salary" +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:194 +msgid "The :guilabel:`Attachment of Salary` report shows all deductions or allocations per employee, such as child support payments and wage garnishments." +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:-1 +msgid "View the Attachment of Salary report that shows all salary garnishments." +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:201 +msgid "The employees are listed in the left-side column, while the different deductions are listed in the top row, organized by month." +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:204 +msgid "The report can be exported as a XLSX file, or inserted into a spreadsheet, using the corresponding buttons at the top." +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:207 +msgid "Clicking on the :guilabel:`Measures` button shows options for how the data is displayed. :guilabel:`Assignment of salary`, :guilabel:`Attachment of salary`, :guilabel:`Child support`, and :guilabel:`Count`, can all be selected or deselected by clicking on the item. If an item has a check mark, it is displayed." +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:-1 +msgid "Select the options that be displayed in the report." +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:216 +msgid "The salary attachment report can be compared to the one for the previous time period or the previous year. To view these comparisons, click on the on the :guilabel:`Comparison` drop-down menu at the top, then select either :guilabel:`Payslip End Date: Previous Period` or :guilabel:`Payslip End Date: Previous Year`." +msgstr "" + #: ../../content/applications/hr/payroll/work_entries.rst:5 msgid "The *Work Entries* dashboard, which can be found by going to :menuselection:`Payroll --> Work Entries --> Work Entries`, provides a visual overview of the individual time sheets of every employee, with each day split into a morning shift and an afternoon shift." msgstr "" @@ -1766,11 +2979,824 @@ msgstr "" msgid ":ref:`Configure work entries `" msgstr "" -#: ../../content/applications/hr/recruitment.rst:5 -#: ../../content/applications/hr/recruitment/new_job.rst:60 +#: ../../content/applications/hr/recruitment.rst:6 +#: ../../content/applications/hr/recruitment/new_job.rst:51 msgid "Recruitment" msgstr "" +#: ../../content/applications/hr/recruitment.rst:8 +msgid "Odoo keeps all job applicants organized with a pre-configured series of steps and stages that each applicant goes through. Each stage has a specific step(s) that should be performed. These range from scheduling a phone call, conducting an interview, to sending a job offer, just to name a few. This process is referred to as the 'applicant flow'." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:13 +msgid "When an applicant applies for a job position, an *applicant card* is automatically created in Odoo's *Recruitment* app for that specific job position. As the applicant progresses through the recruitment pipeline, the recruitment team moves their card from one stage to the next." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:17 +msgid ":ref:`Stages can be configured ` so that an email is automatically sent out using a set, pre-configured template as soon as an applicant's card enters a stage. These automated emails are defined on each stage in the applicant flow." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:21 +msgid "The applicant flow explained in this document is the default flow in Odoo, and goes through the applicant flow when using the *Recruitment* application's default configuration. The applicant flow is able to be modified to suit the specific recruitment flow for any business." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:26 +msgid "The applicant flow with all its stages are universal and applies to all job positions, unless specified. :ref:`A specific stage can be configured ` to be job-specific, meaning that specific stage is only visible for that specific job position. Otherwise, if a new stage is created, or an existing stage is modified, those changes will be visible on all job positions." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:35 +msgid "To access the kanban view for a job position, navigate to the main :menuselection:`Recruitment app` dashboard, which is the default view when opening the application. All job positions appear on the main dashboard. Click the :guilabel:`New Applications` smart button on a job position card to navigate to the kanban view for all the applicants for that particular job position." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:-1 +msgid "Main dashboard view of job position card, showing new applications button." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:44 +msgid "Inside the job application, the kanban stages appear, with all the applicants populated in their respective columns, indicating what stage they are currently in. There are five default stages in Odoo:" +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:48 +msgid ":ref:`Initial Qualification `" +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:49 +msgid ":ref:`First Interview `" +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:50 +msgid ":ref:`Second Interview `" +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:51 +msgid ":ref:`Contract Proposal `" +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:52 +msgid ":ref:`Contract Signed `" +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:54 +msgid "The last column, :guilabel:`Contract Signed`, is folded by default, meaning that the column appears in gray and the applicants in it are hidden from view. To expand the folded stage and view the applicant cards for that column, click anywhere on the thin gray column that says the stage name and the column expands, revealing the applicants." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:-1 +msgid "Expand a folded column by clicking on it in the kanban view." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:63 +msgid "Each stage has a color-coded bar beneath the stage name, giving information about the applicant's status in the stage. The colors are:" +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:66 +msgid ":guilabel:`Green`: there are applicants in the stage with an activity that is either already scheduled or needs to be scheduled in the future (such as a phone call or interview), according to the parameters for that particular stage." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:69 +msgid ":guilabel:`Yellow`: there are applicants in the stage with an activity either scheduled for today or due to be scheduled today." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:71 +msgid ":guilabel:`Red`: there are applicants in the stage with overdue activities which need to be scheduled." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:73 +msgid ":guilabel:`Gray`: there are either no activities currently scheduled and no future activities that are required to be scheduled, or there are no applicants currently in the stage." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:79 +msgid "Customize stages" +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:81 +msgid "Stages can be modified, added, or deleted to best meet the needs of the particular hiring steps of a business." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:85 +msgid "New stage" +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:87 +msgid "To create a new stage, click on :guilabel:`+ Add a Column` and a new column appears. Enter the title for the new stage in the :guilabel:`Column title` field, then click :guilabel:`Add`. The new column appears, and another new stage is available to create. If no new stages are needed, click anywhere on the screen to exit the new column creation." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:-1 +msgid "The plus sign to click in order to add a new column to the kanban stages." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:99 +msgid "Modify stage" +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:101 +msgid "To modify the settings of a stage, hover over the name of the stage, and a :guilabel:`⚙️ (gear)` icon appears in the upper right hand side of the stage. Click on the :guilabel:`⚙️ (gear)` icon and a menu appears. Then click on the :guilabel:`Edit Stage` option. An :guilabel:`Edit Column` form appears. Make any modifications to the form, then click :guilabel:`Save` when done." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:-1 +msgid "The gear icon that appears when a column name is moused over, and the drop-down menu it\n" +"displays when clicked." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:112 +msgid "Edit column form" +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:114 +msgid "The :guilabel:`Edit Column` form is where the stage's settings are configured. The only required fields are the :guilabel:`Stage Name`, and the :guilabel:`Tooltips` section." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:117 +msgid "The fields to be populated or modified are:" +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:119 +msgid ":guilabel:`Stage Name`: type in a name for the stage." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:120 +msgid ":guilabel:`Email Template`: select an email template to be used from the drop-down menu. If a template is selected, when the applicant card enters the stage, an email will automatically be sent to the applicant using the selected template." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:123 +msgid ":guilabel:`Folded in Kanban`: check the box to have the stage appear folded (hidden) at all times in the default view." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:125 +msgid ":guilabel:`Hired Stage`: check the box if this stage indicates that the applicant is hired. When an applicant's card enters this stage, the card displays a :guilabel:`Hired` banner in the upper right corner. If this box is checked, this stage is used to determine the hire date of an applicant." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:129 +msgid ":guilabel:`Job Specific`: if the stage only applies to a specific job position(s), select the job position(s) from the drop-down menu. Multiple job positions can be selected." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:131 +msgid ":guilabel:`Show in Referrals`: check the box if this stage should be seen in the *Referrals* application, and allow the referrer to accrue points when a referral of theirs reaches this stage. If this is active, a :guilabel:`Points` field appears. Enter the amount of referral points the employee receives when an applicant enters this stage." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:135 +msgid ":guilabel:`Tooltips` section: there are three pre-configured labels (colored circles) for each applicant's card, indicating its status. These colors are displayed at the top of each stage to reflect the statuses of the applicants in the stage. The *names* for the label can be modified, but the label itself (the color) cannot. The default names and labels are: :guilabel:`In Progress` (gray), :guilabel:`Blocked` (red), and :guilabel:`Ready for Next Stage` (green)." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:140 +msgid ":guilabel:`Requirements`: enter any internal notes for this stage explaining any requirements of the stage." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:144 +msgid "Delete stage" +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:146 +msgid "If a stage is no longer needed, the stage can be deleted. To delete a stage, hover over the name of the stage, and a :guilabel:`⚙️ (gear)` icon appears. First, click on the :guilabel:`⚙️ (gear)` icon to reveal a drop-down menu, then click :guilabel:`Delete`. A pop-up warning appears, asking :guilabel:`Are you sure you want to remove this column?`. Click :guilabel:`OK` to delete the column." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:152 +msgid "If there are applicants currently in the stage being deleted, an error pops up when attempting to delete the stage, explaining that there are records in the stage which need to be deleted, archived, or moved to a different stage before deleting." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:157 +msgid "Email templates" +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:159 +msgid "To communicate with the applicant, Odoo has several pre-configured email templates that can be used. The pre-configured email templates and when to use them are as follows:" +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:162 +msgid ":guilabel:`Applicant: Acknowledgement`: this template is used to let the applicant know that their application was received. This email is automatically sent out once the applicant is in the :guilabel:`First Interview` stage." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:165 +msgid ":guilabel:`Applicant: Interest`: this template is used to let the applicant know that they have passed the :guilabel:`Initial Qualification` stage and they will be contacted to set up an interview with the recruiter." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:168 +msgid ":guilabel:`Applicant: Not interested anymore`: this template is used when an applicant communicates that they are no longer interested in the position, and thanks them for their time and consideration." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:171 +msgid ":guilabel:`Applicant: Refuse`: this template is used when an applicant is no longer being considered for the position." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:173 +msgid ":guilabel:`Applicant: Your Salary Package`: this template is used when offering an applicant a position. This informs the applicant they can configure their salary package." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:177 +msgid "Email templates can be created, modified, and deleted to suit the needs of a business. For more information on email templates, refer to the :doc:`../general/email_communication/email_template` document." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:181 +msgid "To manually send an email click :guilabel:`Send message` in the chatter. A text box appears, as well as the applicant's email address. Click the :guilabel:`⤢ (double arrow)` full composer icon in the bottom right corner of the :guilabel:`Send Message` tab in the chatter." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:-1 +msgid "Send an email from the chatter." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:189 +msgid "An email composer pop-up loads, with the :guilabel:`Recipients` and :guilabel:`Subject` pre-populated. The applicant's email address is entered on the :guilabel:`Recipients` line, and the :guilabel:`Subject` is `Re: (Subject / Application Name)`. The email body is empty by default." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:193 +msgid "To use a pre-configured email template, click the drop-down next to the :guilabel:`Load template` field in the lower right section of the window. Pre-configured email templates may contain dynamic placeholders so unique information can be populated in the email for a more personalized message to the applicant. There are several pre-configured email templates to choose from. Depending on the template selected, the email subject and/or body may change." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:200 +msgid "Only the email templates that are configured for the model will load. There are other email templates pre-configured in Odoo, but if they are not configured for the recruitment application, they will not appear in the list of available templates." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:204 +msgid "If any attachments are to be added, click the :guilabel:`Attach A File` button in the lower left corner. Navigate to the file to be attached, then click :guilabel:`Open` to attach it. To delete an attachment, click the :guilabel:`X (Delete)` icon to the right of the attachment. If any changes need to be made to the email, edit the body of the email. If the edits should be saved to be used in the future, the email can be saved as a new template. Click the :guilabel:`Save As New Template` button in the bottom right corner. To send the email, click :guilabel:`Send` and the email will be sent to the applicant. The email then appears in the chatter." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:213 +msgid "Stage flow" +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:215 +msgid "In order to move an applicant's card from one stage to another, the applicant's card can either be dragged and dropped in the kanban view to the desired stage, or the stage can be modified on the applicant's card." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:219 +msgid "To change the stage on the applicant's card, click on the applicant's card in the kanban view to go to a detailed view of the card. The current stage for the card is highlighted in purple at the top, above the card. Simply click the desired stage for the card, and the stage changes. A log note indicating the stage change appears in the chatter. Navigate back to the kanban view by clicking on :guilabel:`Applications` in the breadcrumb menu in the top left, and the applicant's card now appears in the new stage." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:-1 +msgid "Change the stage of an applicant by clicking on the desired stage at the top of the\n" +"applicant's card." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:234 +msgid "Initial qualification" +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:237 +msgid "The following information is based on Odoo's default recruitment pipeline flow. Be advised that if modifications are made to create a customized recruitment pipeline flow, it will vary from the following information." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:241 +msgid "All applicants appear in the :guilabel:`Initial Qualification` stage, whether submitted online or if the applicant is manually entered by a recruiter. When the applicant's card is created, Odoo automatically populates the applicant's :guilabel:`Name`, :guilabel:`Email address`, and :guilabel:`Phone number` on the applicant's card. This information is required when applying for a job position." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:247 +msgid "If the applicant entered any information in the :guilabel:`Short Introduction` section of the online application, it is populated in the :guilabel:`Application Summary` tab at the bottom of the applicant's card. If a resumé was attached to the online application, the resumé appears in the attachments section of the chatter, and is also stored in the *Documents* application. To find the recruitment documents stored in the Documents application, navigate to the main :menuselection:`Documents` dashboard, and click the folder labeled :guilabel:`Recruitment` on the right side. All recruitment documents will be stored within that folder." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:256 +msgid "Send interview" +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:258 +msgid "At any point in the hiring process, an *interview* can be sent to the applicant to obtain more information. These interviews are custom-made, and can be formatted in a variety of ways." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:261 +msgid "Odoo uses the term *interview*, but these can be thought of as questionnaires, surveys, tests, certifications, etc. Custom interviews can be formatted to suit each individual job position's needs. For example, a job position for a computer programmer could have an interview in the form of a programming quiz to determine the skill level of the applicant. A job position for a restaurant server could have a questionnaire inquiring about the applicant's availability, if the desired applicant needs to be available on weekend evenings. For more information on creating and editing interview forms, refer to the :doc:`../hr/recruitment/new_job` documentation." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:270 +msgid "In order to send an email to an applicant, there must be an email address on the applicant's card. If an email address is not entered on the applicant's card, when :guilabel:`Send Interview` is clicked, the applicant's card appears instead of the :guilabel:`Survey` pop-up window. Enter the email address in the email field, then click :guilabel:`Save`. Once the applicant's card is saved, the applicant's card closes and the :guilabel:`Survey` pop-up window appears." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:276 +msgid "To send an interview to an applicant, click on an applicant's card to navigate to a detailed view of the applicant's card. At the top of the applicant's card, click the button labeled :guilabel:`Send Interview`." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:280 +msgid "If the applicant's card has an email address on file, a :guilabel:`Survey` pop-up window appears, with all the information populated. If an email is not on the applicant's card, then a contact form appears. Enter the applicants email address, then click :guilabel:`Save`. The card closes and the :guilabel:`Survey` pop-up window appears." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:285 +msgid "Odoo refers to the interview forms as *surveys*. These email templates also use dynamic placeholders to personalize the email to the applicant and the job position. Add any additional recipients for the survey if more people should receive the email. If an email is in the database as a contact, add that contact on the :guilabel:`Recipients` line. If an email should be sent to someone who is not in the database as a contact, and they should **not** be added as a contact, add their email to the :guilabel:`Additional emails` line." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:292 +msgid "If any attachments need to be added, click the :guilabel:`Attachments` button and a file explorer window appears. Navigate to the desired file, then click :guilabel:`Open` to attach it to the email. The attachment loads, and is listed above the :guilabel:`Attachments` button." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:296 +msgid "If the emailed interview must be completed by a specific date, select a date for the :guilabel:`Answer deadline` in the lower-right area of the pop-up window. Click on the line next to :guilabel:`Answer deadline`, and a calendar selector appears. Use the :guilabel:`< (left)` and :guilabel:`> (right)` arrows on either side of the month to navigate to the desired month, then click on the :guilabel:`day` to select the date." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:302 +msgid "The :guilabel:`Mail template` field is pre-populated based on the configuration for the interview. A different template can be chosen from the drop-down menu if desired. If a new template is selected, the new email template loads in the email body." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:306 +msgid "To send the email with the interview link to the applicant, click :guilabel:`Send` at the bottom of the email pop-up." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:-1 +msgid "Send a custom survey, also referred to as an interview form, to an applicant using a\n" +"pre-configured template." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:315 +msgid "Refuse" +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:317 +msgid "At any point in the recruitment pipeline, an applicant can be refused from the job application process. To refuse an applicant, click on an applicant's card to navigate to a detailed view of the applicant's card. At the top of the applicant's card, there are several buttons. Click the one labeled :guilabel:`Refuse`." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:322 +msgid "A :guilabel:`Refuse Reason` pop-up appears. Select the :guilabel:`Refuse Reason` from the drop-down menu. The default refuse reasons in Odoo are: :guilabel:`Doesn't fit the job requirements`, :guilabel:`The applicant is not interested anymore`, and :guilabel:`The applicant gets a better offer`. These three refusal reasons have pre-configured email templates associated with them. Additional refusal reasons can be created and existing ones can be modified or deleted. To add a new refusal reason, type in the name of the reason, then click :guilabel:`Create and Edit...`. A :guilabel:`Create: Refuse Reason` pop-up window appears. Type in the name of the new email template in the :guilabel:`Email Template` field, and click :guilabel:`Create and Edit...`. A :guilabel:`Create: Email Template` window loads. Configure the new email template, then click :guilabel:`Save`." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:334 +msgid "Pre-configured email templates in Odoo sometimes use dynamic placeholders, which are customized pieces of data that populate dynamic content. For example, if the applicant's name is a piece of dynamic content, the applicant's name will appear anytime that dynamic placeholder appears on the email template. For more detailed information on email templates, refer to the :doc:`../general/email_communication/email_template` documentation." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:340 +msgid "An email template populates the :guilabel:`Email Template` field after a refusal reason is selected. If an email should not be sent to the applicant, uncheck the :guilabel:`Send Email` checkbox. To view the email template, click the :guilabel:`External Link` icon to the right of the email template selected. The email template loads in the pop-up window, and can be modified if needed. After making modifications, click :guilabel:`Save`. To close the email template, click :guilabel:`Discard`." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:346 +msgid "To send the refusal email to the applicant, click :guilabel:`Send`. The refusal email is sent to the applicant, and a :guilabel:`Refused` banner appears on the applicant's card." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:-1 +msgid "An applicant's card with the refused banner appearing in the top right corner in red." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:353 +msgid "After refusal, the applicant's card is no longer visible in the job position's kanban view. To view refused applicants, navigate to the :menuselection:`Recruitment app --> Applications --> All Applications`. All applications for all job positions are presented in a list view. To view the refused applicants only, click :guilabel:`Filters`, then click :guilabel:`Archived/Refused`. All applicants that have been archived and/or refused appear in the list. To further organize this list and view refusals by job position, click :guilabel:`≣ Group By`, then click :guilabel:`Job`." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:361 +msgid "New applicant" +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:363 +msgid "An applicant card can be manually added if needed. If an applicant needs to be added to the list of prospective candidates and an applicant card has not been created yet (they have not applied for the job online yet) an applicant card can be easily added from the job position kanban view in one of two ways, using either the :ref:`Quick add ` icon or the :ref:`Create ` button." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:372 +msgid "Quick add" +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:374 +msgid "Quickly add a new applicant using the :guilabel:`Quick add` icon. If not already in the job position kanban view, navigate to the main recruitment dashboard, and click the :guilabel:`New Applicants` button on the job position card that the applicant should be added to. Then, click on the small :guilabel:`+ (plus sign) Quick add` icon in the top right of the :guilabel:`Initial Qualification` stage to quickly add a new applicant." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:-1 +msgid "All the fields for a new applicant form entered when using the Quick Add option." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:384 +msgid "Enter the following information on the card:" +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:386 +msgid ":guilabel:`Subject/Application Name`: this is the only required field. Enter the title for the card. Typically this is the applicant's name and job position being applied to, for example: `Laura Smith - Experienced Developer`. This field is not visible in the kanban view (unless in the Developer mode), but is visible on the individual card." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:390 +#: ../../content/applications/hr/recruitment.rst:435 +msgid ":guilabel:`Applicant's Name`: enter the applicant's name." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:391 +#: ../../content/applications/hr/recruitment.rst:436 +msgid ":guilabel:`Email`: enter the applicant's email address." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:392 +msgid ":guilabel:`Applied Job`: the current job position populates this field. If needed, the job position can be changed by selecting a different position from the drop-down menu. If a different job position is selected, after the card is created, the card will appear in the selected job position." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:397 +msgid "After the information is entered, click :guilabel:`Add`. The applicant appears in the list, and a new blank applicant card appears. Click either the :guilabel:`🗑️ (delete)` icon or click anywhere on the screen to close the card." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:401 +msgid "If preferred, after entering the applicant name, click :guilabel:`Edit` and a detailed :guilabel:`Applicant Form` loads. :ref:`Enter the information on the form `, then click :guilabel:`Save`" +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:408 +msgid "Create" +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:410 +msgid "Add a new applicant including all the relevant information using the :guilabel:`Create` button. If not already in the kanban view for the job position to add an applicant to, navigate to the main recruitment dashboard, and click the :guilabel:`New Applicants` button on the job position card that the applicant should be added to. Then, click the :guilabel:`Create` button in the top left of the kanban view and an applicant form loads." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:416 +msgid "Certain fields on the applicant card may be pre-populated, depending on how the job position is configured. Typically, the :guilabel:`Job` section, as well as the :guilabel:`Recruiter` field, are all pre-populated." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:420 +msgid "Enter the following information on the new applicant form. Note that not all fields listed below may be visible. Depending on installed applications and configurations, some fields may not be displayed." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:427 +msgid "Applicant section" +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:429 +msgid ":guilabel:`Subject/Application Name`: this is the only required field. Enter the title for the card. Typically this is the applicant's name and job position being applied to, for example: `Laura Smith - Experienced Developer`. This field is not visible in the kanban view, unless the :guilabel:`Applicant's Name` is left blank. If there is no :guilabel:`Applicant's Name`, then the :guilabel:`Subject/Application Name` is what is displayed on the applicant card in the kanban view." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:437 +msgid ":guilabel:`Phone`: enter the applicant's phone number." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:438 +msgid ":guilabel:`Mobile`: enter the applicant's mobile number." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:439 +msgid ":guilabel:`Degree`: select the applicant's highest level of education earned from the drop-down menu. Options are :guilabel:`Graduate`, :guilabel:`Bachelor Degree`, :guilabel:`Master Degree`, or :guilabel:`Doctoral Degree`. The :guilabel:`Graduate` option indicates graduating the highest level of school before a Bachelor's degree, such as a high school or secondary school diploma, depending on the country." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:444 +msgid ":guilabel:`Tags`: select as many tags as desired from the drop-down menu. To add a tag that does not exist, type in the tag name, the click :guilabel:`Create \"new tag\"`." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:446 +msgid ":guilabel:`Interviewer`: select the person who will be conducting the interview(s) from the drop-down menu. The person must have either *recruiter* or *officer* rights configured for the Recruitment application in order to appear on the drop-down." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:449 +msgid ":guilabel:`Recruiter`: select the person responsible for the entire recruitment process for the job position. Only *users* can be selected, and all users are presented in the drop-down to select from." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:452 +msgid ":guilabel:`Appreciation`: click on one of the stars to select a rating for the applicant. One star indicates :guilabel:`Good`, two stars indicates :guilabel:`Very Good`, and three stars indicates :guilabel:`Excellent.`" +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:455 +msgid ":guilabel:`Referred By User`: if referral points are to be earned for this job position in the *Referrals* application, select the user who referred the applicant from the drop-down menu. The *Referrals* application must be installed for this to appear." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:460 +msgid "Job section" +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:462 +msgid "The following fields are pre-populated when creating a new applicant, as long as these field are specified on the Job Position. Editing the fields is possible, if desired." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:465 +msgid ":guilabel:`Applied Job`: select the job position the applicant is applying to from the drop-down menu." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:467 +msgid ":guilabel:`Department`: select the department the job position falls under from the drop-down menu." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:469 +msgid ":guilabel:`Company`: select the company the job positions is for using the drop-down menu." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:472 +msgid "Contract section" +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:474 +msgid ":guilabel:`Expected Salary`: enter the amount the applicant is requesting for the role in this field. The number should be in a `XX,XXX.XX` format. The currency is determined by the localization setting for the company." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:477 +msgid ":guilabel:`Expected Salary - Extra advantages...`: if any extra advantages are requested by the applicant, enter it in this field. This should be short and descriptive, such as `1 week extra vacation` or `dental plan`." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:480 +msgid ":guilabel:`Proposed Salary`: enter the amount to be offered to the applicant for the role in this field. The number should be in a `XX,XXX.XX` format." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:482 +msgid ":guilabel:`Proposed Salary - Extra advantages...`: if any extra advantages are offered to the applicant, enter it in this field. This should be short and descriptive, such as `1 week extra vacation` or `dental plan`." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:485 +msgid ":guilabel:`Availability`: using the calendar module in the drop-down menu, select the available start date for the applicant." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:489 +msgid "Application summary tab" +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:491 +msgid "Any additional details or notes that should be added to the applicant's card can be typed into this field." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:-1 +msgid "All the fields for a new applicant form entered." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:501 +msgid "First interview" +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:503 +msgid "After an applicant has passed the :guilabel:`Initial Qualification` stage, they can be moved to the :guilabel:`First Interview` stage in the job position kanban view. To move the applicant to the next stage, drag and drop the applicant's card to the :guilabel:`First Interview` stage, or click on the :guilabel:`First Interview` stage button at the top of the individual applicant's card." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:-1 +msgid "An applicant's card moves from one stage t another by using the click and drag method." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:512 +msgid "When the applicant's card moves to the :guilabel:`First Interview` stage, an acknowledgement email is automatically sent to the applicant. The email is created using an email template titled :guilabel:`Applicant: Acknowledgement`. This email template is pre-configured in Odoo, and contains dynamic placeholders for the job position, the recruiter's name, and the company's information. Once the email is sent, the email appears in the chatter." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:521 +msgid "Schedule a meeting" +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:523 +msgid "When a date and time have been agreed upon for both the applicant and interviewer, the interview can be scheduled. To schedule an interview, whether a phone or in-person interview, click the :guilabel:`Meeting` smart button at the top of the applicant's record." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:527 +msgid "The applicant's card can be found by navigating to the :menuselection:`Recruitment application` dashboard, click on a :guilabel:`New Applications` button in the job position card, then click on the applicant's card." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:532 +msgid "The meeting smart button will display :guilabel:`No Meeting` if no meetings are currently scheduled. For new applicants who are new to the :guilabel:`First Interview` stage, this will be the default. If there are any meetings already scheduled, the smart button will display :guilabel:`Next Meeting` with the date of the upcoming meeting." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:537 +msgid "Doing so loads the *Calendar* application, showing the currently scheduled meetings and events for the user. The meetings and events displayed are for the employees who are listed under the :guilabel:`Attendees` section on the right side of the calendar view. To change the currently loaded meetings and events being displayed, uncheck the person who's calendar events are to be hidden. Only the checked attendees will be visible on the calendar." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:543 +msgid "The default view is the week view. To change the calendar view, click on a button to present the calendar in a different view, either :guilabel:`Day`, :guilabel:`Month`, or :guilabel:`Year`. To change the displayed date range for the calendar, either use the :guilabel:`⬅️ (Left)`, :guilabel:`➡️ (Right)`, or :guilabel:`Today` buttons above the calendar, or click on a date in the calendar on the right side of the displayed calendar." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:-1 +msgid "The calendar view, highlighting how to change the displayed meetings." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:553 +msgid "To add a meeting to the calendar, click on the day the meeting is to take place, or click on the start time of the meeting and drag to the end time, to select the date, time, and the length of the meeting. If the calendar is displaying the day or week view, click on the day *and* the time slot the meeting is to take place. A :guilabel:`New Event` pop up appears, with the :guilabel:`Meeting Subject` populated with the applicant card's :guilabel:`Subject/Application Name`. The default time slot is 30 minutes. If the information is correct, click :guilabel:`Create` to add the meeting to the calendar, or click :guilabel:`Edit` to modify the meeting." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:561 +msgid "If :guilabel:`Edit` is clicked, an expanded :guilabel:`New Event` card loads. Make any changes needed to the form." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:565 +msgid "New event card" +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:567 +msgid "The fields available to populate or modify on the detailed :guilabel:`New Event` card are as follows. The only required fields to enter are the :guilabel:`Meeting Subject`, :guilabel:`Starting At`, and :guilabel:`Ending At` fields. Once the card details are entered, click :guilabel:`Save` to save the changes and create the meeting." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:572 +msgid ":guilabel:`Meeting Subject`: enter the subject for the meeting. This should clearly indicate the purpose of the meeting. The default subject is the :guilabel:`Subject/Application Name` on the applicant's card." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:575 +msgid ":guilabel:`Attendees`: select the people who should be in attendance. The default employee listed is the person who is creating the meeting. Add as many other people as desired." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:579 +msgid "Meeting details tab" +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:581 +msgid ":guilabel:`Starting At`: using the drop-down calendar, select the date and time for the meeting start time." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:583 +msgid ":guilabel:`Ending At`: using the drop-down calendar, select the date and time for the meeting end time." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:585 +msgid ":guilabel:`Duration`: this field auto populates based on the :guilabel:`Starting At` and :guilabel:`Ending At` times entered. If the meeting time is adjusted, this field automatically adjusts to the correct duration length." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:588 +msgid ":guilabel:`All Day`: if the meeting is an all day long event, check the box next to :guilabel:`All Day`. After this box is checked, the :guilabel:`Duration` field is hidden from view, a well as the meeting start and end times." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:591 +msgid ":guilabel:`Organizer`: the employee who created the meeting is populated in this field. Use the drop-down menu to change the selected employee." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:593 +msgid ":guilabel:`Description`: enter a brief description in this field. There is an option to enter formatted text, such as numbered lists, headings, tables, as well as links, photos, and more. Use the powerbox feature, by typing a `/`, and a list of options are presented. Scroll through the options and click on the desired item. The item appears in the field and can be modified. Each command presents a different pop-up window. Follow the instructions for each command to complete the entry." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:599 +msgid ":guilabel:`Reminders`: select a reminder from the drop-down menu. Options include :guilabel:`Notification`, :guilabel:`Email`, and :guilabel:`SMS Text Message`, each with a specific time period before the event (hours, days, etc). The reminder chosen will alert the meeting participants of the meeting via the selected option." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:603 +msgid ":guilabel:`Location`: enter the location for the meeting." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:604 +msgid ":guilabel:`Meeting URL`: if the meeting is virtual, enter the meeting link in this field." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:605 +msgid ":guilabel:`Tags`: select any tag(s) for the meeting using the drop-down menu. There is no limit to the number of tags that can be used." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:609 +msgid "Options tab" +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:611 +msgid ":guilabel:`Recurrent`: if the meeting should repeat at a selected interval (not typical for a first interview), check the box next to :guilabel:`Recurrent`. This reveals a recurrence section. Enter the details for how often the meeting should repeat, including an end time." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:614 +msgid ":guilabel:`Privacy`: select the visibility of this meeting. Options are :guilabel:`Public`, :guilabel:`Private`, and :guilabel:`Only internal users`. :guilabel:`Public` allows for everyone to see the meeting, :guilabel:`Private` allows only the attendees listed on the meeting to see the meeting, and :guilabel:`Only internal users` allows anyone logged into the company database to see the meeting." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:619 +msgid ":guilabel:`Show as`: select from the drop-down whether the meeting time should appear as :guilabel:`Busy` or :guilabel:`Available` in the attendees' schedules. Setting this field to :guilabel:`Available` allows other meetings to be scheduled for the same time. It is recommended to set this field to :guilabel:`Busy`, so no other meetings can be scheduled for the attendees at the same time." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:-1 +msgid "A new meeting card with all the details populated, and ready to save." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:630 +msgid "Send meeting to attendees" +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:632 +msgid "Once changes have been entered and the meeting details are correct, the meeting can be sent to the attendees via email or text message." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:635 +msgid "To send the meeting via email, click the :guilabel:`Email` button next to the list of attendees. A :guilabel:`Contact Attendees` email configurator pop-up appears. A pre-formatted email using the default :guilabel:`Calendar: Event Update` email template populates the email body field. The followers of the document (job application), as well as the user who created the meeting are added as :guilabel:`Recipients` by default. Add the applicant's email address to the list to send the email to the applicant as well. Make any other desired changes to the email. If an attachment is needed, click the :guilabel:`Attach A File` button, navigate to the file, then click :guilabel:`Open`. Once the email is ready to be sent, click :guilabel:`Send`." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:-1 +msgid "Enter the information to send the event via email." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:648 +msgid "To send the meeting via text message, click the :guilabel:`SMS` button next to the list of attendees. A :guilabel:`Send SMS Text Message` pop-up appears. At the top, in a blue box, information appears regarding the message. The first line lists how many records (phone numbers) are selected. The second line lists the number of recipients and how many of them are invalid. If a contact does not have a valid phone number listed, click :guilabel:`Close`, and edit the attendee's record, then redo these steps." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:656 +msgid "It is *not* recommended to check the box to send to all the records in the :guilabel:`Send SMS Text Message` pop-up. This would send a message to all contacts with a valid phone number." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:659 +msgid "When the message reads :guilabel:`0 are invalid`, type in the message to be sent in the :guilabel:`Message` field. Beneath the message field, the number of characters, as well as the amount of text messages required to send the message (according to GSM7 criteria) appears. Click :guilabel:`Put In Queue` to have the text sent later, after any other messages are scheduled, or click :guilabel:`Send Now` to send the message immediately." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:-1 +msgid "Send a text message to the attendees of the meeting." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:670 +msgid "Sending text messages is not a default capability with Odoo. To send text messages, credits are required, which need to be purchased. For more information on IAP credits and plans, refer to the :doc:`../general/in_app_purchase` documentation." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:677 +msgid "Second interview" +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:679 +msgid "After an applicant has passed the :guilabel:`First Interview` stage, they can be moved to the :guilabel:`Second Interview` stage. To move the applicant to the next stage, drag and drop the applicant's card to the :guilabel:`Second Interview` stage, or click on the :guilabel:`Second Interview` stage button at the top of the individual applicant's card." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:684 +msgid "When the applicant's card moves to the :guilabel:`Second Interview` stage, there are no automatic activities or emails configured for this stage, unlike for the :guilabel:`First Interview` stage. The recruiter can now :ref:`schedule a second interview ` with the applicant, following the same process as for the first interview." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:692 +msgid "Contract proposal" +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:694 +msgid "When the applicant has passed the interview stages and an offer is ready to be sent, they can be moved to the :guilabel:`Contract Proposal` stage. Drag and drop the applicant's card to the :guilabel:`Contract Proposal` stage, or click on the :guilabel:`Contract Proposal` stage button at the top right of the individual applicant's card." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:699 +msgid "The next step is to send an offer to the applicant. On the applicant's card, click the :guilabel:`Generate Offer` button. A :guilabel:`Generate a Simulation Link` pop-up appears. All fields are pre-populated with information from the job position, except for the :guilabel:`Force New Cars List`, :guilabel:`Default Vehicle`, and the :guilabel:`Canteen Cost` (this is set to `0.00`)." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:706 +msgid "Not all fields may appear on the :guilabel:`Generate a Simulation Link` pop-up. Depending on the localization setting for the company and the applications installed, some fields may not appear. For example if the *Fleet* application is not installed, the fields related to vehicles will not appear on the pop-up." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:712 +msgid "Universal fields" +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:714 +msgid "The following fields appear for all offers sent to applicants regardless of localization settings." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:716 +msgid ":guilabel:`Offer Template`: the template currently being used to populate the :guilabel:`Generate a Simulation Link` pop-up. To modify the template, click the :guilabel:`External link` icon to the right of the drop-down arrow. Make any changes, then click :guilabel:`Save`." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:719 +msgid ":guilabel:`Job Title`: the name of the position being offered to the applicant." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:720 +msgid ":guilabel:`Contract Start Date`: the date the contract takes effect. The default date is the current date. To modify the date, click the drop-down to reveal a calendar. Use the :guilabel:`< (left)` and :guilabel:`> (right)` arrows on either side of the month to navigate to the desired month, then click on the :guilabel:`day` to select the date." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:724 +msgid ":guilabel:`Yearly Cost`: the annual salary being offered." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:725 +msgid ":guilabel:`Offer Link`: this link takes the applicant to a webpage where they can enter their personal information, which will be imported to their employee record when created. If applicable, the applicant can modify their salary package (this option is not available for all localizations). Lastly, this is where the applicant accepts the offer by clicking :guilabel:`Review Contract & Sign` to accept the contract and sign it using the *Sign* application." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:733 +msgid "The *Sign* application must be installed in order for a document to be signed. Ensure the *Sign* application is installed to use this feature." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:739 +msgid "The following fields will only appear if specific localization settings are selected, and/or certain applications are installed. For example if the *Fleet* application is not installed, none of the optional fields related to vehicles will appear, such as :guilabel:`Force New Cars List` or :guilabel:`Default Vehicle`." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:744 +msgid ":guilabel:`Job Position`: the official title of the job being offered to the applicant, from the :guilabel:`Job Position` card. To modify the name, click the :guilabel:`External link` icon to the right of the drop-down arrow. Make any changes, then click :guilabel:`Save`." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:747 +msgid ":guilabel:`Department`: the department the job position falls under. To modify the department, click the :guilabel:`External link` icon to the right of the drop-down arrow. Make any changes, then click :guilabel:`Save`." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:750 +msgid ":guilabel:`Force New Cars List`: check this box to offer a new vehicle to the applicant." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:751 +msgid ":guilabel:`Default Vehicle`: using the drop-down menu, select the vehicle that will be assigned to the applicant." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:753 +msgid ":guilabel:`Canteen Cost`: enter the amount that is offered to the applicant for the cafeteria." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:754 +msgid ":guilabel:`Contract Type`: using the drop-down menu, select the type of contract that is being offered." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:-1 +msgid "Format the offer to send to the applicant. Make any modifications before sending." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:762 +msgid "Send offer" +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:764 +msgid "To send the offer to the applicant, click :guilabel:`Send`. If the applicant does not have an email address listed on their applicant card, the applicant form appears so their email can be configured. If there is already an email configured on the applicant's card, the email pop-up appears instead. If prompted with the applicant's card, enter the applicant's email address in the :guilabel:`Email` field, then click :guilabel:`Save`. The applicant form closes and the email pop-up appears." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:770 +msgid "The :guilabel:`Applicant: Your Salary Package` email template is used, and the :guilabel:`Recipients`, :guilabel:`Subject`, and email body are pre-populated based on the email template. If any attachments need to be added, click the :guilabel:`Attachments` button and a file explorer window appears. Navigate to the desired file, then click :guilabel:`Open` to attach it to the email. The attachment loads, and is listed above the :guilabel:`Attachments` button. Once the email is ready to send, click :guilabel:`Send`." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:778 +msgid "To send an offer, ensure the *Sign* application is installed. This is necessary so the offer can be sent to the applicant by the recruiter. The applicant does not need any software installed." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:-1 +msgid "Send an email to the applicant with a link to the offered salary." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:788 +msgid "Contract signed" +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:790 +msgid "Once the applicant has accepted the offer and signed the contract, the next step is to move the applicant to the :guilabel:`Contract Signed` stage. To move the applicant to the next stage, drag and drop the applicant's card to the :guilabel:`Contract Signed` stage, or click the :guilabel:`More` button at the top of the applicant's card to reveal the :guilabel:`Contract Signed` stage button at the top of the individual applicant's card, and click :guilabel:`Contract Signed`." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:797 +msgid "The :guilabel:`Contract Signed` stage is folded in the kanban view, but the card may still be dragged and dropped into that stage." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:800 +msgid "Once the applicant's card moves to the :guilabel:`Contract Signed` stage, a green :guilabel:`Hired` banner appears in the top right of the applicant's card." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:-1 +msgid "Hired banner in the top right corner of applicant card." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:808 +msgid "Create employee" +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:810 +msgid "Once the applicant has been hired, the next step is to create an employee record of them. On the applicant's card, click the :guilabel:`Create Employee` button in the top left. An employee form appears, and any information from the applicant's card that can be imported into the employee card appears in the form." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:815 +msgid "Fill out the rest of the form. For detailed information on the fields, refer to the :doc:`employees/new_employee` documentation. When done, click :guilabel:`Save`. The employee record is now saved in the *Employees* app." +msgstr "" + #: ../../content/applications/hr/recruitment/new_job.rst:3 msgid "Job positions" msgstr "" @@ -1784,30 +3810,22 @@ msgid "Each job position is shown in an individual kanban card. If the job posit msgstr "" #: ../../content/applications/hr/recruitment/new_job.rst:13 -msgid "View submitted applications by clicking the :guilabel:`# Applications` button, with `#` being the number of applications received. If a position is not published, a :guilabel:`Start Recruitment` button will appear instead." +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." msgstr "" -#: ../../content/applications/hr/recruitment/new_job.rst:22 +#: ../../content/applications/hr/recruitment/new_job.rst:20 msgid "Create a new job position" msgstr "" -#: ../../content/applications/hr/recruitment/new_job.rst:24 -msgid "There are two ways a job position can be created: from the main :guilabel:`Recruitment` dashboard, or from the :guilabel:`Configuration` menu." +#: ../../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." msgstr "" -#: ../../content/applications/hr/recruitment/new_job.rst:27 -msgid "To create a job position from the :guilabel:`Configuration` menu, go to :menuselection:`Recruitment app --> Configuration --> Job Positions`. The job positions in this view are displayed in a list." -msgstr "" - -#: ../../content/applications/hr/recruitment/new_job.rst:30 -msgid "Create a new job position from the :guilabel:`Job Positions` dashboard by clicking the :guilabel:`Create` button in the top-left corner." -msgstr "" - -#: ../../content/applications/hr/recruitment/new_job.rst:33 +#: ../../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." msgstr "" @@ -1815,143 +3833,200 @@ msgstr "" msgid "Create a new job position." msgstr "" -#: ../../content/applications/hr/recruitment/new_job.rst:41 -msgid "Once the job position has been created, it will appear as a card in the kanban view on the main :guilabel:`Recruitment`` dashboard, as well as in the list view on the :guilabel:`Configuration` dashboard." +#: ../../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." msgstr "" -#: ../../content/applications/hr/recruitment/new_job.rst:46 +#: ../../content/applications/hr/recruitment/new_job.rst:37 msgid "Edit a new job position" msgstr "" -#: ../../content/applications/hr/recruitment/new_job.rst:48 -msgid "Once the job position is created, it's time to enter the details for the position. Click on the :guilabel:`⋮ (three dots)` icon in the upper-right corner of the relevant card to reveal several options, and then click :guilabel:`Edit` to edit the details." +#: ../../content/applications/hr/recruitment/new_job.rst:39 +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 "" #: ../../content/applications/hr/recruitment/new_job.rst:-1 msgid "Edit the job position card." msgstr "" -#: ../../content/applications/hr/recruitment/new_job.rst:56 -msgid "Enter the job description in the :guilabel:`Job Description` tab. This information is what is visible to potential employees when searching for available jobs." +#: ../../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:62 +#: ../../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." msgstr "" -#: ../../content/applications/hr/recruitment/new_job.rst:66 +#: ../../content/applications/hr/recruitment/new_job.rst:57 msgid "The fields can be filled out as follows:" msgstr "" -#: ../../content/applications/hr/recruitment/new_job.rst:68 -msgid ":guilabel:`Company`: Select the company the job is for." +#: ../../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:69 -msgid ":guilabel:`Website`: Select the website where the job will be published." +#: ../../content/applications/hr/recruitment/new_job.rst:60 +msgid ":guilabel:`Job Location`: select the physical address for the job." +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." +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." +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." +msgstr "" + +#: ../../content/applications/hr/recruitment/new_job.rst:67 +msgid ":guilabel:`Recruiter`: select the person who will be doing the recruiting for this role." +msgstr "" + +#: ../../content/applications/hr/recruitment/new_job.rst:68 +msgid ":guilabel:`Interviewers`: select who should perform the interview(s). Multiple people can be selected." msgstr "" #: ../../content/applications/hr/recruitment/new_job.rst:70 -msgid ":guilabel:`Department`: Select the relevant department for the job position." -msgstr "" - -#: ../../content/applications/hr/recruitment/new_job.rst:71 -msgid ":guilabel:`Expected New Employees`: Enter the number of employees to be hired for this position." +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." +msgid ":guilabel:`Contract Template`: select a contract template that will be used when offering the job to a candidate." msgstr "" #: ../../content/applications/hr/recruitment/new_job.rst:74 -msgid ":guilabel:`Interview Form`: Select a form that applicants will fill out prior to their interview, or create a new form. Once selected, a :guilabel:`Display (Name) Form` button will appear next to the selected form. Click on this to see how the form will be displayed to the candidate on the front end." +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:0 -msgid "The interview form will display a link to see the form as the candidate will." +#: ../../content/applications/hr/recruitment/new_job.rst:78 +msgid ":guilabel:`Time to Answer`: enter the number of days before the applicant is contacted." msgstr "" -#: ../../content/applications/hr/recruitment/new_job.rst:83 -msgid ":guilabel:`Recruiter`: Select the person who will be doing the recruiting for this role." +#: ../../content/applications/hr/recruitment/new_job.rst:79 +msgid ":guilabel:`Process`: enter the various stages the candidate will go through during the recruitment process." +msgstr "" + +#: ../../content/applications/hr/recruitment/new_job.rst:81 +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 +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:-1 msgid "Enter job information details in the recruitment tab." msgstr "" -#: ../../content/applications/hr/recruitment/new_job.rst:90 -msgid "Appraisals" -msgstr "" - -#: ../../content/applications/hr/recruitment/new_job.rst:92 -msgid "This tab displays the :guilabel:`Employee Feedback Template` and the :guilabel:`Manager Feedback Template`, both of which will be used after the employee has been hired, the predetermined time has passed, and feedback is requested." -msgstr "" - -#: ../../content/applications/hr/recruitment/new_job.rst:97 +#: ../../content/applications/hr/recruitment/new_job.rst:96 msgid "Create interview form" msgstr "" -#: ../../content/applications/hr/recruitment/new_job.rst:99 -msgid "Once a job position has been made, the :guilabel:`Interview Form` needs to be created. In the kanban view of the :menuselection:`Recruitment` dashboard, click on the :guilabel:`⋮ (three dots)` icon in the upper-right corner of the card to reveal several options, and then click :guilabel:`Create Interview Form`." +#: ../../content/applications/hr/recruitment/new_job.rst:98 +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:-1 -msgid "Create an interview form for the new position." +#: ../../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:108 -msgid "Click on :guilabel:`Add a section` to add a section to the form. A line will appear, 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." +#: ../../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:116 -msgid "Next, click :guilabel:`Add a question` to add a question to the section. A pop-up window appears to enter the question details. Type out the question in the top line." +#: ../../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?" msgstr "" -#: ../../content/applications/hr/recruitment/new_job.rst:119 -msgid "There are several *Question Types* to choose from:" -msgstr "" - -#: ../../content/applications/hr/recruitment/new_job.rst:121 -msgid ":guilabel:`Multiple Lines Text Box`: allows the applicant to enter several lines of text" +#: ../../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 ":guilabel:`Single Line Text Box`: limits the applicant to only a single line of text" -msgstr "" - -#: ../../content/applications/hr/recruitment/new_job.rst:123 -msgid ":guilabel:`Numerical Value`: only allows a number to be entered" -msgstr "" - -#: ../../content/applications/hr/recruitment/new_job.rst:124 -msgid ":guilabel:`Date`: a calendar module is presented to select a date" +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 ":guilabel:`Datetime`: a calendar module and a clock icon is presented to select a date and time" +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." msgstr "" -#: ../../content/applications/hr/recruitment/new_job.rst:126 +#: ../../content/applications/hr/recruitment/new_job.rst:-1 +msgid "The top portion of the new interview form with everything filled out and selected." +msgstr "" + +#: ../../content/applications/hr/recruitment/new_job.rst:135 +#: ../../content/applications/hr/recruitment/new_job.rst:351 +msgid "Questions" +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:128 +#: ../../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:130 +#: ../../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:137 +#: ../../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:140 +#: ../../content/applications/hr/recruitment/new_job.rst:169 msgid "Sections are indicated by a gray background, while questions have a white background." msgstr "" @@ -1959,106 +4034,1068 @@ msgstr "" msgid "A sample of categories and questions for a candidate." msgstr "" -#: ../../content/applications/hr/recruitment/new_job.rst:146 -msgid "Next, configure the 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:150 -msgid "Questions" -msgstr "" - -#: ../../content/applications/hr/recruitment/new_job.rst:152 -msgid ":guilabel:`Layout`: Choose how the questions should be displayed." -msgstr "" - -#: ../../content/applications/hr/recruitment/new_job.rst:154 -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:156 -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:158 -msgid ":guilabel:`One page per question`: Display a single question on each page." -msgstr "" - -#: ../../content/applications/hr/recruitment/new_job.rst:160 -msgid ":guilabel:`Progression Mode`: Display the progress the candidate is making, either as a :guilabel:`Percentage`, or as a :guilabel:`Number`." -msgstr "" - -#: ../../content/applications/hr/recruitment/new_job.rst:162 -msgid ":guilabel:`Survey Time Limit`: Check this box to limit the time allowed to complete the form. When selected, a field to enter the minutes appears next to the checked box. Enter the time (using an XX:XX minute/second format) in the field." -msgstr "" - -#: ../../content/applications/hr/recruitment/new_job.rst:165 -msgid ":guilabel:`Selection`: Display the entire form (e.g. :guilabel:`All questions`), or only a random selection of questions from each section (:guilabel:`Randomized per section`)." -msgstr "" - -#: ../../content/applications/hr/recruitment/new_job.rst:169 -msgid "Although it is a selectable option, the :guilabel:`Randomized per section` option is not typically selected for an interview form." -msgstr "" - -#: ../../content/applications/hr/recruitment/new_job.rst:173 -msgid "Scoring" -msgstr "" - -#: ../../content/applications/hr/recruitment/new_job.rst:175 -msgid ":guilabel:`No scoring`: Select this option to not score the form." -msgstr "" - #: ../../content/applications/hr/recruitment/new_job.rst:176 -msgid ":guilabel:`Scoring with answers at the end`: Select this option to score the form and display the" -msgstr "" - -#: ../../content/applications/hr/recruitment/new_job.rst:177 -msgid "correct answers for the candidate when they are finished with the form." +#: ../../content/applications/hr/recruitment/new_job.rst:269 +msgid "Answers" msgstr "" #: ../../content/applications/hr/recruitment/new_job.rst:178 -msgid ":guilabel:`Scoring without answers at the end`: Select this option to score the form but not display the answers to the candidate." +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:181 -msgid "If one of the scoring options was selected, a :guilabel:`Success %` field will appear. Enter the percentage the candidate needs to pass the exam (example, 80.00%). The entry should be written in an “XX.XX” format." +#: ../../content/applications/hr/recruitment/new_job.rst:185 +msgid "Multiple choice" msgstr "" -#: ../../content/applications/hr/recruitment/new_job.rst:186 -msgid "Candidates" -msgstr "" - -#: ../../content/applications/hr/recruitment/new_job.rst:188 -msgid ":guilabel:`Access Mode`: Specify who can access the exam. Either :guilabel:`Anyone with the link` or :guilabel:`Invited people only`." +#: ../../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 ":guilabel:`Appraisal Managers Only`: Check this box so only the managers who are reviewing the exam can see the answers. If left unchecked, anyone can view the results." -msgstr "" - -#: ../../content/applications/hr/recruitment/new_job.rst:192 -msgid ":guilabel:`Login Required`: Check this box to require candidates to log in before taking the exam, whether they have a valid token or not." +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 ":guilabel:`Attempts Limit`: If there is a limit to how many times the exam can be taken, check this box, then enter the maximum attempt number in the field next to it." +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:198 +#: ../../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:200 -msgid ":guilabel:`Reward quick answers`: If the exam is to be taken live, check this box to award more points to participants who answer quickly." +#: ../../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:202 -msgid ":guilabel:`Session Code`: Enter an access code that will allow the viewers into the live exam session." +#: ../../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:205 +#: ../../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." +msgstr "" + +#: ../../content/applications/hr/referrals.rst:3 +msgid "Referrals" +msgstr "" + +#: ../../content/applications/hr/referrals.rst:5 +msgid "Odoo's *Referrals* application is a centralized place where all information regarding referrals is housed, from points earned, coworkers hired, and rewards selected. Users can recommend people they know for job positions, then earn referral points as those people progress through the recruitment pipeline. Once enough referral points are earned, they can be exchanged for prizes. The Referrals application integrates with the *Employees*, *Recruitment*, and *Website* applications, all of which must be installed in order for the *Referrals* application to function." +msgstr "" + +#: ../../content/applications/hr/referrals.rst:12 +msgid "The only configuration needed for the Referrals application after it is installed are the :ref:`rewards `; everything else is pre-configured when Odoo Referrals is installed." +msgstr "" + +#: ../../content/applications/hr/referrals.rst:16 +msgid "Any user with either :guilabel:`Referral User`, :guilabel:`Officer`, or :guilabel:`Administrator` rights for the Recruitment application has access to the Referrals application. Only user's with :guilabel:`Administrator` rights for the Recruitment application have access to the :ref:`reporting ` and configurations menus. For more information on users and access rights, refer to these documents: :doc:`../general/users/manage_users` and :doc:`../general/users/access_rights`." +msgstr "" + +#: ../../content/applications/hr/referrals.rst:24 +msgid "Onboarding" +msgstr "" + +#: ../../content/applications/hr/referrals.rst:26 +msgid "When opening the *Referrals* application for the first time, a pre-configured onboarding script appears. This is in the form of four slides, each explaining the different parts of the Referrals application. At the top of the dashboard, the following message is displayed throughout all the onboarding slides: :guilabel:`GATHER YOUR TEAM! Job Referral Program`. Behind this main message is an image, and beneath it some more explanatory text." +msgstr "" + +#: ../../content/applications/hr/referrals.rst:32 +msgid "Each of the onboarding slides has a corresponding image and message that is displayed. After reading each message, click the :guilabel:`Next` button to advance to the next slide." +msgstr "" + +#: ../../content/applications/hr/referrals.rst:35 +msgid "The text that appears on each slide is as follows:" +msgstr "" + +#: ../../content/applications/hr/referrals.rst:37 +msgid ":guilabel:`Oh no! Villains are lurking the city! Help us recruit a team of superheroes to save the day!`" +msgstr "" + +#: ../../content/applications/hr/referrals.rst:39 +msgid ":guilabel:`Browse through open job positions, promote them on social media, or refer friends.`" +msgstr "" + +#: ../../content/applications/hr/referrals.rst:40 +msgid ":guilabel:`Collect points and exchange them for awesome gifts in the shop.`" +msgstr "" + +#: ../../content/applications/hr/referrals.rst:41 +msgid ":guilabel:`Compete against your colleagues to build the best justice league!`" +msgstr "" + +#: ../../content/applications/hr/referrals.rst:44 +msgid "The onboarding slides will appear every time the Referrals application is opened, until all the slides have been viewed and the :guilabel:`Start Now` button has been clicked. If the onboarding is exited at any point, or if the :guilabel:`Start Now` button has *not* been clicked, the onboarding slides will begin again when the Referrals application is opened. Once the :guilabel:`Start Now` button has been clicked, the onboarding slides will not be seen again, and the main dashboard will load when the Referrals application is opened from that point on." +msgstr "" + +#: ../../content/applications/hr/referrals.rst:51 +msgid "At any point during onboarding, the :guilabel:`Skip` button may be clicked. This exits the onboarding, and the main Referrals dashboard loads. If :guilabel:`Skip` is clicked, onboarding slides will not load anymore when opening the Referrals application." +msgstr "" + +#: ../../content/applications/hr/referrals.rst:-1 +msgid "An onboarding slide with the skip and next buttons visible at the bottom." +msgstr "" + +#: ../../content/applications/hr/referrals.rst:60 +msgid "If there are any candidates hired that the user had referred prior to opening the Referrals app (meaning the onboarding slides have not appeared before), when :guilabel:`Start Now` is clicked at the end of onboarding, instead of going to the main dashboard, a :ref:`hired ` screen appears instead." +msgstr "" + +#: ../../content/applications/hr/referrals.rst:66 +msgid "Modifying onboarding slides" +msgstr "" + +#: ../../content/applications/hr/referrals.rst:68 +msgid "Onboarding slides can be modified if desired. Only users with :guilabel:`Administrator` rights for the Recruitment application can modify onboarding slides. To edit a slide, navigate to :menuselection:`Referrals app --> Configuration --> Onboarding.` Each line displays the text for the individual onboarding slide. To edit an onboarding slide, click on an individual slide line to open the slide's onboarding form, then click :guilabel:`Edit`." +msgstr "" + +#: ../../content/applications/hr/referrals.rst:74 +msgid "Make any changes to the message in the :guilabel:`Text` box. To change the order the slide appear in the onboarding, the :guilabel:`Sequence` can be modified. Type in the corresponding number to indicate the order in which the slides should be displayed. A :guilabel:`Company` may be selected, however, if this field is populated, that slide will only be displayed for that particular company." +msgstr "" + +#: ../../content/applications/hr/referrals.rst:79 +msgid "The image can be modified as well. Hover over the image thumbnail in the top right corner of the form. A :guilabel:`✏️ (pencil)` icon and :guilabel:`🗑️ (garbage can)` icon appear. Click the :guilabel:`✏️ (pencil)` icon to change the image. A file navigator window loads. Navigate to the desired image, select it, then click :guilabel:`Open`. The new image appears in the thumbnail. To delete an image, click the :guilabel:`🗑️ (garbage can)` icon, then select a new image using the :guilabel:`✏️ (pencil)` icon." +msgstr "" + +#: ../../content/applications/hr/referrals.rst:86 +msgid "To save any changes, click :guilabel:`Save`, or click :guilabel:`Discard` to delete any changes and revert to the original content." +msgstr "" + +#: ../../content/applications/hr/referrals.rst:-1 +msgid "An onboarding slide in edit mode, with the main fields highlighted." +msgstr "" + +#: ../../content/applications/hr/referrals.rst:93 +msgid "The order of the slides can also be changed directly in the Onboarding dashboard, without having to edit an individual onboarding slide. Click the up and down arrow symbol that appears after the checkbox and before the slide text, and drag the slide to the desired position. The :guilabel:`Sequence` automatically changes on all the slide's onboarding forms, reflecting the new sequence." +msgstr "" + +#: ../../content/applications/hr/referrals.rst:-1 +msgid "The onboarding slides in a list, with the drag and drop arrows highlighted." +msgstr "" + +#: ../../content/applications/hr/referrals.rst:104 +msgid "Share job positions" +msgstr "" + +#: ../../content/applications/hr/referrals.rst:106 +msgid "In order to earn referral points, a user must first share a job position so the applicant can apply for the position. There are several ways to share job positions within the Referrals application, through the :ref:`View Jobs ` button and the :ref:`Email A Friend ` button." +msgstr "" + +#: ../../content/applications/hr/referrals.rst:114 +msgid "View Jobs" +msgstr "" + +#: ../../content/applications/hr/referrals.rst:116 +msgid "To see all job positions that are actively recruiting candidates, click the :guilabel:`View Jobs` button on the main Referrals dashboard. This presents all job positions, with each individual job presented in its own card." +msgstr "" + +#: ../../content/applications/hr/referrals.rst:-1 +msgid "The 'View Jobs' screen, displaying all current open job positions. All information is\n" +"displayed on the card." +msgstr "" + +#: ../../content/applications/hr/referrals.rst:125 +msgid "Each job position card contains the following information:" +msgstr "" + +#: ../../content/applications/hr/referrals.rst:127 +msgid "The title of the job position. This information is taken from the :guilabel:`Job Position` field of the job form." +msgstr "" + +#: ../../content/applications/hr/referrals.rst:129 +msgid "The number of positions being recruited. This information is taken from the :guilabel:`Expected New Employees` field of the :guilabel:`Recruitment` tab of the job form." +msgstr "" + +#: ../../content/applications/hr/referrals.rst:131 +msgid "The points a user will earn when an applicant applies for the position." +msgstr "" + +#: ../../content/applications/hr/referrals.rst:132 +msgid "The job description detailing the job position. This information is taken from the :guilabel:`Job Position` tab of the job form." +msgstr "" + +#: ../../content/applications/hr/referrals.rst:135 +msgid "To see all the details for a job position, click the :guilabel:`More Info` button on the specific card. This opens the job position webpage in a new browser tab. This is what an applicant sees before applying for a position." +msgstr "" + +#: ../../content/applications/hr/referrals.rst:140 +msgid "Only published job positions will be visible in the Referrals app. To check which job positions are published or not, refer to the :doc:`recruitment/new_job` documentation." +msgstr "" + +#: ../../content/applications/hr/referrals.rst:144 +msgid "Refer friends" +msgstr "" + +#: ../../content/applications/hr/referrals.rst:146 +msgid "To share a job position with someone, click the :guilabel:`Refer Friend` button on the specific job position card. A pre-configured :guilabel:`Send Job Offer by Mail` email pop-up window appears. Enter the recipient's email address in the :guilabel:`Email` field." +msgstr "" + +#: ../../content/applications/hr/referrals.rst:150 +msgid "The subject and body are populated using a default template. The subject `Job for you` appears, and can be modified if desired." +msgstr "" + +#: ../../content/applications/hr/referrals.rst:153 +msgid "The specific title of the job position will populate the :guilabel:`Job Position` placeholder in the email body. The `See Job Offer` text in the email body is an individualized tracking link to the specific job position listed on the website. When the prospective employee receives the email, the link will send them to the job position page, where they can apply for the position, and the person who referred them is tracked in the Referrals application." +msgstr "" + +#: ../../content/applications/hr/referrals.rst:159 +msgid "If desired, add any text or closing salutation to the email body. When all edits have been made, click :guilabel:`Send Email` to send the email, or click :guilabel:`Cancel` to close the email pop-up window." +msgstr "" + +#: ../../content/applications/hr/referrals.rst:-1 +msgid "Referral email pop-up window with the email message inside it." +msgstr "" + +#: ../../content/applications/hr/referrals.rst:168 +msgid "Share a job" +msgstr "" + +#: ../../content/applications/hr/referrals.rst:170 +msgid "There are several other ways to share a job position aside from sending an email, via social media platforms and tracking links to the job position. At the bottom of each job position card are four icons and corresponding tracking links that can be used to share the job position, keeping track of applicants in the Referrals application." +msgstr "" + +#: ../../content/applications/hr/referrals.rst:-1 +msgid "The various sharing icons that appear for each job." +msgstr "" + +#: ../../content/applications/hr/referrals.rst:180 +msgid "Link" +msgstr "" + +#: ../../content/applications/hr/referrals.rst:182 +msgid "To share the job position with a customized tracking link, click the :guilabel:`Share Now` button with the :guilabel:`🔗 (chain)` icon inside it. A :guilabel:`Link to Share` pop-up window appears with the tracking link. Click :guilabel:`Copy` to copy the link. After the link is copied, click the :guilabel:`Close` button to close the pop-up. Next, share the link with the prospective employee however desired." +msgstr "" + +#: ../../content/applications/hr/referrals.rst:189 +msgid "Facebook" +msgstr "" + +#: ../../content/applications/hr/referrals.rst:191 +msgid "To share the job position using Facebook, click the :guilabel:`Share Now` button with the :guilabel:`f (Facebook icon)` inside it. If the user is already logged into Facebook, when the :guilabel:`f (Facebook icon)` is clicked, a :guilabel:`Share on Facebook` page loads in a new tab, with the link populated in the main body of the new post. If the user is *not* already logged in, a log-in screen loads instead, prompting the user to log-in to Facebook first." +msgstr "" + +#: ../../content/applications/hr/referrals.rst:197 +msgid "Type in any additional information to add to the post, in the space directly below your name. If desired, :guilabel:`tag` users, :guilabel:`check-in` at a location, or add a :guilabel:`status` to the post. To tag a user, click the :guilabel:`Tag Friends` icon and select the people to tag to the post. To add a check-in location, click the :guilabel:`Check in` icon, and select the location from the pop-up of predetermined locations based on your current location. To add a :guilabel:`status`, click the :guilabel:`Feeling/Activity` icon, then select either the feeling or the activity type, and lastly, if an activity type was selected, select the specific activity." +msgstr "" + +#: ../../content/applications/hr/referrals.rst:205 +msgid "There are five methods to share the job position, :guilabel:`Your Story`, :guilabel:`Share on a Friend's Timeline`, :guilabel:`Share in a Group`, :guilabel:`Share in an Event`, and :guilabel:`Share in a Private Message`. To select the sharing method, click the drop-down menu located at the top of the page, directly beneath the :guilabel:`Share on Facebook` banner." +msgstr "" + +#: ../../content/applications/hr/referrals.rst:-1 +msgid "The view on Facebook when sharing a job description. All the various ways to share are\n" +"highlighted, as are all the required settings." +msgstr "" + +#: ../../content/applications/hr/referrals.rst:217 +msgid "Share to news feed or story" +msgstr "" + +#: ../../content/applications/hr/referrals.rst:219 +msgid "The default sharing method is through the :guilabel:`News Feed`, :guilabel:`Story`, or both. At the lower portion of the form are radio buttons next to the two options, :guilabel:`Feed` (for the News Feed) and :guilabel:`Your Story` for stories. When :guilabel:`Share to News Feed or Story` is selected, these buttons are active, if another option is selected, these radio buttons are greyed out. Activate the radio button(s) to indicate how the job position should be shared, either in the news feed, the story, or both." +msgstr "" + +#: ../../content/applications/hr/referrals.rst:226 +msgid "The :guilabel:`Share to news feed or story` option allows for specific privacy settings to be selected. In the lower right corner of the screen, there are two drop-down menu options, one for the :guilabel:`Feed` option, the other for the :guilabel:`Your story` option. Select the posting parameters from the drop-down menus. The :guilabel:`Feed` ad :guilabel:`Your story` options appear different from user to user, depending on what privacy settings have been created in Facebook. :guilabel:`Public` and :guilabel:`Friends` are default options, but other options that the user may have configured will appear as well, such as custom groups." +msgstr "" + +#: ../../content/applications/hr/referrals.rst:234 +msgid "When the post and/or story is ready to be shared, click the blue :guilabel:`Post to Facebook` button at the bottom of the screen." +msgstr "" + +#: ../../content/applications/hr/referrals.rst:237 +msgid "Share on a friend's timeline" +msgstr "" + +#: ../../content/applications/hr/referrals.rst:239 +msgid "Instead of making a public post on the user's on Facebook page, the job position can be shared directly on a friend's timeline. Click the :guilabel:`Share to News Feed or Story` drop-down menu near the top of the page, and select :guilabel:`Share on a Fried's Timeline`." +msgstr "" + +#: ../../content/applications/hr/referrals.rst:243 +msgid "When selected, a :guilabel:`Friend` field appears below the selection. Begin to type in the friend's name. As the name is typed, a list appears, populated with names that match what is entered. Select the friend from the list. **Only** one friend can be selected." +msgstr "" + +#: ../../content/applications/hr/referrals.rst:247 +#: ../../content/applications/hr/referrals.rst:262 +#: ../../content/applications/hr/referrals.rst:276 +msgid "When the post is ready to be shared, click the blue :guilabel:`Post to Facebook` button at the bottom of the screen." +msgstr "" + +#: ../../content/applications/hr/referrals.rst:250 +msgid "Share in a group" +msgstr "" + +#: ../../content/applications/hr/referrals.rst:252 +msgid "To reach a specific audience and not share the job position publicly with everyone, a job can be shared in a group. Click the :guilabel:`Share to News Feed or Story` drop-down menu near the top of the page, and select :guilabel:`Share in a Group`." +msgstr "" + +#: ../../content/applications/hr/referrals.rst:256 +msgid "When selected, a :guilabel:`Group` field appears below the selection. The available groups that can be posted to are groups the user is currently a member of. Job positions cannot be shared with groups the user has not joined. Begin to type in the name of the group. As the group name is typed, a list appears, populated with the group names that match what is entered. Select the group from the list. Only one group can be selected." +msgstr "" + +#: ../../content/applications/hr/referrals.rst:265 +msgid "Share in an event" +msgstr "" + +#: ../../content/applications/hr/referrals.rst:267 +msgid "A job position can also be shared on an event page. Click the :guilabel:`Share to News Feed or Story` drop-down menu near the top of the page, and select :guilabel:`Share in an Event`." +msgstr "" + +#: ../../content/applications/hr/referrals.rst:270 +msgid "When selected, an :guilabel:`Event` field appears below the selection. The available events that can be posted to are events the user is invited to. This includes events that the user has not responded to yet, and events that have occurred in the past. Begin to type in the name of the event. As the event name is typed, a list appears, populated with the events that match what is entered. Select the event from the list. Only one event can be selected." +msgstr "" + +#: ../../content/applications/hr/referrals.rst:279 +msgid "Share in a private message" +msgstr "" + +#: ../../content/applications/hr/referrals.rst:281 +msgid "The last option is to share a job position privately instead of publicly, in a Facebook message. Click the :guilabel:`Share to News Feed or Story` drop-down menu near the top of the page, and select :guilabel:`Share in an Private Message`." +msgstr "" + +#: ../../content/applications/hr/referrals.rst:285 +msgid "When selected, a :guilabel:`To` field appears below the selection. Begin to type in the friend's name. As the name is typed, a list appears, populated with names that match what is entered. Select the friend from the list. Multiple friends can be selected and added to a single message. Repeat this process for each friend to be added." +msgstr "" + +#: ../../content/applications/hr/referrals.rst:290 +msgid "When the message is ready to be sent, click the blue :guilabel:`Send message` button at the bottom of the screen." +msgstr "" + +#: ../../content/applications/hr/referrals.rst:294 +msgid "X/Twitter" +msgstr "" + +#: ../../content/applications/hr/referrals.rst:296 +msgid "A job position can also be shared on X/Twitter. Click the :guilabel:`Share Now` button with the bird icon inside it. If the user is already signed in to X/Twitter, when the :guilabel:`Share Now` icon is clicked, an X/Twitter page loads in a new tab with a pre-populated message ready to post, in a draft pop-up. If the user is *not* already signed in, a sign-in screen loads instead, prompting the user to sign in to X/Twitter." +msgstr "" + +#: ../../content/applications/hr/referrals.rst:302 +msgid "The default message is:" +msgstr "" + +#: ../../content/applications/hr/referrals.rst:304 +msgid ":guilabel:`Amazing job offer for (Job Position)! Check it live: (link to Job Position)`" +msgstr "" + +#: ../../content/applications/hr/referrals.rst:306 +msgid "Type in any additional information or make any edits to the message. If desired, click the :guilabel:`X` in the top left corner of the thumbnail preview of the webpage to remove it. To adjust the audience for the message, click the drop-down button labeled :guilabel:`Everyone`. Select the preferred audience from the drop-down menu. The default option is :guilabel:`Everyone`, and the other options is :guilabel:`Circle`. The :guilabel:`Circle` is a group of people that the user has selected in X/Twitter." +msgstr "" + +#: ../../content/applications/hr/referrals.rst:313 +msgid "The default setting is :guilabel:`🌎 (globe) Everyone can reply`, an allows everyone on X/Twitter to reply to the message. To change this, click the :guilabel:`🌎 (globe) Everyone can reply` button in the lower left section of the message. There are four options presented: :guilabel:`Everyone`, :guilabel:`Accounts you follow`, :guilabel:`Verified accounts`, and :guilabel:`Only accounts you mention`. Selecting one of the other options restricts who can reply to the message." +msgstr "" + +#: ../../content/applications/hr/referrals.rst:319 +msgid "There are various other items that can be added to the message. Media (photos, videos, etc), GIF's, polls, emojis, and a location may all be added. Click the corresponding icon in the bottom left of the message and follow the prompts to add the desired additional elements." +msgstr "" + +#: ../../content/applications/hr/referrals.rst:323 +msgid "To have the message posted at a future date and time, click the :guilabel:`Schedule` icon in the lower left of the message window. It is the fifth icon from the left. Enter the date and time that the message should be posted using the date and time selector presented. Click :guilabel:`Confirm` to add the scheduled time to the message." +msgstr "" + +#: ../../content/applications/hr/referrals.rst:328 +msgid "To post the message, click :guilabel:`Post`. The message will be immediately posted, or, if it was scheduled, will be posted at the scheduled date and time." +msgstr "" + +#: ../../content/applications/hr/referrals.rst:-1 +msgid "The X/Twitter pop-up when sharing a job description. All the other items than can be added\n" +"to the message are highlighted, as is the visibility setting and the post button." +msgstr "" + +#: ../../content/applications/hr/referrals.rst:337 +msgid "LinkedIn" +msgstr "" + +#: ../../content/applications/hr/referrals.rst:339 +msgid "To share a job position on LinkedIn, click the :guilabel:`Share Now` button with the :guilabel:`in (LinkedIn logo)` inside it. If the user is already logged into LinkedIn, when the :guilabel:`Share Now` button is clicked, a new tab loads in LinkedIn, with a link to the job position at the top. If the user is *not* already logged in, a log-in screen loads instead, prompting the user to log-in to LinkedIn first." +msgstr "" + +#: ../../content/applications/hr/referrals.rst:345 +msgid "The job position can be shared either in a public post, or in a private message to an individual or group of individuals." +msgstr "" + +#: ../../content/applications/hr/referrals.rst:349 +msgid "Share in a post" +msgstr "" + +#: ../../content/applications/hr/referrals.rst:351 +msgid "To share the job position in a public post, click the :guilabel:`✏️ (pencil) Share in a post` button in the lower-left corner of the screen. A :guilabel:`Create a post` window loads, with the job position link populated. Enter any other information to the post in the field." +msgstr "" + +#: ../../content/applications/hr/referrals.rst:355 +msgid "To change the audience that will see the post, click the :guilabel:`🌎 (globe) Anyone` drop-down, located directly beneath the account name. Click on the desired selection, then click the :guilabel:`Save` button on the far right side of the screen, beneath the last listed option." +msgstr "" + +#: ../../content/applications/hr/referrals.rst:359 +msgid ":guilabel:`Anyone` allows anyone on LinkedIn to see the post. :guilabel:`Connections only` will only share the post with people who are connected with the user, and will be hidden from everyone else. :guilabel:`Group` shares the post with a specific group the user is a member of. The post can only be shared with one group; posting to multiple groups at once is not available. If :guilabel:`Group` is selected, a page loads with a list of all the groups the user is currently a member of. Click on a group to select it, then click the :guilabel:`Save` button in the lower right corner." +msgstr "" + +#: ../../content/applications/hr/referrals.rst:367 +msgid "Next, select who can comment on the post. To change this setting, click on the :guilabel:`💬 (speech bubble) Anyone` button located beneath the body of the post. A page loads with the various options. Click on one of the three options to select it. The three options are :guilabel:`Anyone`, :guilabel:`Connections only`, and :guilabel:`No one`. The default option is :guilabel:`Anyone`, which allows anyone with a LinkedIn account to comment on the post. :guilabel:`Connections only` will only allow people who are connected with the user to comment on the post. :guilabel:`No one` turns off commenting. After making a selection, click the :guilabel:`Save` button in the far lower right corner." +msgstr "" + +#: ../../content/applications/hr/referrals.rst:376 +msgid "Finally, once the post is edited and the settings have been selected, click :guilabel:`Post` to share the job position." +msgstr "" + +#: ../../content/applications/hr/referrals.rst:-1 +msgid "A linkedIn post to share a job. The job position is highlighted as is the post button." +msgstr "" + +#: ../../content/applications/hr/referrals.rst:384 +msgid "Send as private message" +msgstr "" + +#: ../../content/applications/hr/referrals.rst:386 +msgid "Instead of making a public post, the post can be sent to a connection in a private message. To do so, click the :guilabel:`Send as private message` button in the lower left corner. A message window loads with the link to the job description in the bottom of the window. First, select the recipient(s) for the message. Type the name in the :guilabel:`Search for message recipients` field. As the name is typed in, any matching connections appear. Click on a connection to add them. Repeat this for all the recipients to send the message to. There is no limit on the number of connections that can be messaged. Next, enter any additional text in the message body. Click :guilabel:`Send` in the lower right corner to send the message. A :guilabel:`Message successfully sent!` screen loads. Two options are presented, :guilabel:`View Message` and :guilabel:`Continue to LinkedIn`. Click on the desired selection to navigate to that choice, or close the browser tab to exit." +msgstr "" + +#: ../../content/applications/hr/referrals.rst:400 +msgid "Email a friend" +msgstr "" + +#: ../../content/applications/hr/referrals.rst:402 +msgid "Another way to share job opportunities is to share the entire current list of open job positions instead of one job position at a time. To do this, navigate to the main *Referrals* app dashboard. Click the :guilabel:`Email a friend` button at the bottom of the screen. A :guilabel:`Send Job Offer by Mail` pop-up window appears." +msgstr "" + +#: ../../content/applications/hr/referrals.rst:407 +msgid "Enter the email address(es) in the :guilabel:`Email` line. The email can be sent to multiple recipients, simply enter a comma followed by a single space after each email address. The :guilabel:`Subject` is pre-configured with `Job for you`, but can be edited." +msgstr "" + +#: ../../content/applications/hr/referrals.rst:411 +msgid "The email body is also populated with pre-configured text. The text that appears is:" +msgstr "" + +#: ../../content/applications/hr/referrals.rst:413 +msgid "`Hello,`" +msgstr "" + +#: ../../content/applications/hr/referrals.rst:415 +msgid "`There are some amazing job offers in my company! Have a look, they can be interesting for you`" +msgstr "" + +#: ../../content/applications/hr/referrals.rst:417 +msgid "`See Job Offers`" +msgstr "" + +#: ../../content/applications/hr/referrals.rst:419 +msgid "The `See Job Offers` text is a tracking link to a complete list of all job positions currently being recruited for, that are live on the company's website (published). Add any additional text and/or make any edits to the message body, then click :guilabel:`Send Mail` to send the email. The message will be sent and the window will close." +msgstr "" + +#: ../../content/applications/hr/referrals.rst:427 +msgid "Hired referrals" +msgstr "" + +#: ../../content/applications/hr/referrals.rst:429 +msgid "When a candidate that has been referred by a user is hired, the user \"grows their superhero team\" and adds superhero avatars to their Referrals dashboard." +msgstr "" + +#: ../../content/applications/hr/referrals.rst:432 +msgid "After a referral has been hired, when the user next opens the Referrals app, instead of the main dashboard, a hired page loads. The text :guilabel:`(Referral Name) has been hired! Choose an avatar for your new friend!` appears." +msgstr "" + +#: ../../content/applications/hr/referrals.rst:436 +msgid "Below this message are five avatar thumbnails to choose from. If an avatar has already been assigned to a referral, the thumbnail is greyed out, and the name the avatar has been chosen for appears beneath the avatar. Click on an available avatar to select it." +msgstr "" + +#: ../../content/applications/hr/referrals.rst:440 +msgid "If more than one referral was hired since opening the Referrals application, after selecting the first avatar, the user is prompted to select another avatar for the subsequent hired referral. Once all avatars have been selected, the dashboard loads and all the avatars are now visible. Mouse over each avatar and their name is displayed above them." +msgstr "" + +#: ../../content/applications/hr/referrals.rst:-1 +msgid "The hired screen. A selection of avatars are presented to chose from, with any already\n" +"chosen are greyed out." +msgstr "" + +#: ../../content/applications/hr/referrals.rst:451 +msgid "Modify friends" +msgstr "" + +#: ../../content/applications/hr/referrals.rst:453 +msgid "Friend avatars are able to be modified in the same manner that :ref:`levels ` are modified. Only users with :guilabel:`Administrator` rights for the Recruitment application can make modifications to friends. The pre-configured friends can be seen and modified by navigating to :menuselection:`Referrals app --> Configuration --> Friends`. Each friend avatar appears in the :guilabel:`Dashboard Image` column, and the corresponding name appears in the :guilabel:`Friend Name` column. The default images are a motley group of hero characters, ranging from robots to dogs." +msgstr "" + +#: ../../content/applications/hr/referrals.rst:460 +msgid "To modify a friend's dashboard image, thumbnail, name, or position, click on an individual friend to open the referral friend form. Click :guilabel:`Edit` to make modifications. Type the name in the :guilabel:`Friend Name` field. The name is solely to differentiate the friends in the configuration menu; the friend's name is not visible anywhere else in the Referrals application." +msgstr "" + +#: ../../content/applications/hr/referrals.rst:465 +msgid "The :guilabel:`Position` can be set to either :guilabel:`Front` or :guilabel:`Back`. This determines the position of the friend in relation to the user's super hero avatar. Click the radio button next to the desired selection, and the friend will appear either in front of or behind the user's avatar when activated." +msgstr "" + +#: ../../content/applications/hr/referrals.rst:470 +msgid "If desired, both the thumbnail :guilabel:`Image` and the :guilabel:`Dashboard Image` can be modified. Hover over the image being replaced to reveal a :guilabel:`✏️ (pencil)` icon and :guilabel:`🗑️ (garbage can)` icon. Click the :guilabel:`✏️ (pencil)` icon and a file explorer window appears. Navigate to the desired image file then click :guilabel:`Open` to select it." +msgstr "" + +#: ../../content/applications/hr/referrals.rst:475 +#: ../../content/applications/hr/referrals.rst:660 +msgid "Once all changes have been made, click the :guilabel:`Save` button to save the changes, or click the :guilabel:`Discard` button to revert to the original information." +msgstr "" + +#: ../../content/applications/hr/referrals.rst:-1 +msgid "A friend form in edit mode." +msgstr "" + +#: ../../content/applications/hr/referrals.rst:483 +#: ../../content/applications/hr/referrals.rst:668 +msgid "It is not advised to edit the images. An image file must have a transparent background in order for it to render properly. Only users with knowledge about transparent images should attempt adjusting any images in the Referrals application." +msgstr "" + +#: ../../content/applications/hr/referrals.rst:487 +msgid "Once an image is changed and the friend is saved, it is **not possible** to revert to the original image. To revert to the original image, the Referrals application must be *uninstalled then reinstalled.*" +msgstr "" + +#: ../../content/applications/hr/referrals.rst:492 +msgid "Referral points" +msgstr "" + +#: ../../content/applications/hr/referrals.rst:494 +msgid "The referral program is based on earning points that are then exchanged for rewards. On the main Referrals application dashboard, the top displays a summary of the user's current points. The left side of the summary displays the total points earned, and the right side displays the points that are available to spend." +msgstr "" + +#: ../../content/applications/hr/referrals.rst:499 +msgid "To see the various referrals and the points earned for each, click on one of the buttons directly beneath the avatars. The options are :guilabel:`Referrals`, :guilabel:`Ongoing`, and :guilabel:`Successful`." +msgstr "" + +#: ../../content/applications/hr/referrals.rst:503 +msgid "The current number of referrals who are still active in the recruitment pipeline, and have not yet been hired or refused, appear above the :guilabel:`Ongoing` button. The number of referrals who have been hired appear above the :guilabel:`Successful` button. The total number of referrals (both the ongoing and successful referrals combined) appear above the :guilabel:`Referrals` button." +msgstr "" + +#: ../../content/applications/hr/referrals.rst:509 +msgid "To view the referrals associated with each of the categories, :guilabel:`Referrals`, :guilabel:`Ongoing`, and :guilabel:`Successful`, click on the corresponding button. All the referrals for that specific category are displayed." +msgstr "" + +#: ../../content/applications/hr/referrals.rst:514 +msgid "My referrals" +msgstr "" + +#: ../../content/applications/hr/referrals.rst:516 +msgid "To see all the referrals (both ongoing and successful) click the :guilabel:`Referrals` button. A :guilabel:`My Referral` window loads. This screen displays all the referrals, with each referral in its own referral card." +msgstr "" + +#: ../../content/applications/hr/referrals.rst:520 +msgid "A successful referral has a green line down the left side of the card, and displays a :guilabel:`✓ Hired` image in the top right corner of the card. Referrals that are in process display an :guilabel:`In Progress` image in the top right corner." +msgstr "" + +#: ../../content/applications/hr/referrals.rst:524 +msgid "Each referral card lists the name of the applicant, the department the job position is in, the name of the job position, the person responsible for filling the role (recruiter), and the points earned." +msgstr "" + +#: ../../content/applications/hr/referrals.rst:528 +msgid "Points" +msgstr "" + +#: ../../content/applications/hr/referrals.rst:530 +msgid "The points that can be earned for a referral are the same across all job positions. Each stage of the recruitment process has corresponding points assigned to it. The stages listed correspond to the stages configured in the *Recruitment* application." +msgstr "" + +#: ../../content/applications/hr/referrals.rst:534 +msgid "On each individual referral card, beneath the points earned is a bar chart that displays how many points have been earned out of the total possible points that can be earned if the applicant is hired." +msgstr "" + +#: ../../content/applications/hr/referrals.rst:538 +msgid "Beneath the bar chart is a list of the various recruitment stages and the points earned when the referral moves to that stage. If a stage has been achieved and the points have been earned, a green check mark appears next to the stage." +msgstr "" + +#: ../../content/applications/hr/referrals.rst:543 +msgid "The pre-configured point structure for referrals is as follows:" +msgstr "" + +#: ../../content/applications/hr/referrals.rst:545 +msgid ":guilabel:`Initial Qualification`: 1 point" +msgstr "" + +#: ../../content/applications/hr/referrals.rst:546 +msgid ":guilabel:`First Interview`: 20 points" +msgstr "" + +#: ../../content/applications/hr/referrals.rst:547 +msgid ":guilabel:`Second Interview`: 9 points" +msgstr "" + +#: ../../content/applications/hr/referrals.rst:548 +msgid ":guilabel:`Contract Proposal`: 5 points" +msgstr "" + +#: ../../content/applications/hr/referrals.rst:549 +msgid ":guilabel:`Contract Signed`: 50 points" +msgstr "" + +#: ../../content/applications/hr/referrals.rst:551 +msgid "The total points earned for a referral that is hired is 85 points. Modifications of the points earned for each stage is done in the Recruitment application. Refer to the :ref:`Recruitment ` documentation to modify the points for each stage." +msgstr "" + +#: ../../content/applications/hr/referrals.rst:558 +msgid "Rewards" +msgstr "" + +#: ../../content/applications/hr/referrals.rst:561 +msgid "Create rewards" +msgstr "" + +#: ../../content/applications/hr/referrals.rst:563 +msgid "The rewards are the only configurations needed when setting up the Referrals application. Only users with :guilabel:`Administrator` rights for the Recruitment application can create or modify rewards. To add rewards, navigate to :menuselection:`Referrals app --> Configuration --> Rewards`. Click :guilabel:`Create` and a reward form loads. Enter the following information on the form:" +msgstr "" + +#: ../../content/applications/hr/referrals.rst:568 +msgid ":guilabel:`Product Name`: Enter the name as it should appear for the reward." +msgstr "" + +#: ../../content/applications/hr/referrals.rst:569 +msgid ":guilabel:`Cost`: Enter the amount of points required to redeem the reward." +msgstr "" + +#: ../../content/applications/hr/referrals.rst:570 +msgid ":guilabel:`Company`: Using the drop-down menu, select the company the reward will appear for. If a reward is to be used for several companies, each company needs to have a record of the reward, with the company listed on the form." +msgstr "" + +#: ../../content/applications/hr/referrals.rst:573 +msgid ":guilabel:`Gift Responsible`: Select the person who will be responsible for procuring and delivering the reward to the recipient, using the drop-down menu. This person is alerted when the reward is purchased, so they know when to deliver the reward to the recipient." +msgstr "" + +#: ../../content/applications/hr/referrals.rst:576 +msgid ":guilabel:`Description`: Type in the description for the reward. This will be visible on the reward card, beneath the title." +msgstr "" + +#: ../../content/applications/hr/referrals.rst:578 +msgid ":guilabel:`Photo`: Add a photo of the reward, which appears on the rewards page. Hover over the image square, and two icons appear, a :guilabel:`✏️ (pencil)` and a :guilabel:`🗑️ (garbage can)`. Click the :guilabel:`✏️ (pencil)` icon and a file explorer appears. Navigate to the photo file, then click :guilabel:`Open` to select it." +msgstr "" + +#: ../../content/applications/hr/referrals.rst:583 +msgid "The only required fields are the :guilabel:`Product Name`, :guilabel:`Company`, and :guilabel:`Description`." +msgstr "" + +#: ../../content/applications/hr/referrals.rst:-1 +msgid "A filled out reward form with all details entered." +msgstr "" + +#: ../../content/applications/hr/referrals.rst:591 +msgid "It is advised to enter a :guilabel:`Cost` and add a :guilabel:`Photo`. If a cost is not entered, the default cost will be listed as zero, which would list the reward as free in the reward shop. If a photo is not selected, a placeholder icon will be displayed on the rewards page." +msgstr "" + +#: ../../content/applications/hr/referrals.rst:596 +msgid "Redeem rewards" +msgstr "" + +#: ../../content/applications/hr/referrals.rst:598 +msgid "To redeem points for a reward, click the :guilabel:`Rewards` button on the main Referrals dashboard. All the configured rewards are listed in individual reward cards. The points required to purchase the reward is listed in the top right corner of the card. If the user has enough points to purchase a reward, a :guilabel:`🧺 (basket) Buy` button appears at the bottom of the reward card. If they do not have enough points for a reward, the reward card displays :guilabel:`You need another (x) points to buy this` instead of a buy button." +msgstr "" + +#: ../../content/applications/hr/referrals.rst:605 +msgid "Click the :guilabel:`🧺 (basket) Buy` button on a reward to purchase it. A confirmation pop-up appears, asking if the user is sure they want to purchase the reward. Click :guilabel:`OK` to purchase the item, or :guilabel:`Cancel` to close the window and cancel the purchase." +msgstr "" + +#: ../../content/applications/hr/referrals.rst:609 +msgid "After :guilabel:`OK` is clicked, the pop-up window closes, and the points used to purchase the reward are subtracted from the user's available points. The rewards presented are now updated to reflect the user's current available points." +msgstr "" + +#: ../../content/applications/hr/referrals.rst:-1 +msgid "Buy button appears below a mug and backpack reward, while the bicycle reward states how\n" +"many more reward points are needed to redeem." +msgstr "" + +#: ../../content/applications/hr/referrals.rst:621 +msgid "Levels" +msgstr "" + +#: ../../content/applications/hr/referrals.rst:623 +msgid "The referrals application has pre-configured levels that are reflected in the user's avatar on the Referrals dashboard. As a user refers potential employees and earns points, they can *level up*, much like in a video game." +msgstr "" + +#: ../../content/applications/hr/referrals.rst:627 +msgid "Levels have no functional impact on the performance of the application. They are solely used for the purpose of adding achievement tiers for participants to aim for, gamifying referrals for the user." +msgstr "" + +#: ../../content/applications/hr/referrals.rst:630 +msgid "The user's current level is displayed at the top of the main Referrals application dashboard, directly beneath their photo, in a :guilabel:`Level: X` format. In addition, a colored ring appears around the user's photo, indicating how many points the user currently has, and how many additional points they need to level up. The cyan colored portion of the ring represents points earned, while the white colored portion represents the points still needed before they can level up." +msgstr "" + +#: ../../content/applications/hr/referrals.rst:637 +msgid "Modify levels" +msgstr "" + +#: ../../content/applications/hr/referrals.rst:639 +msgid "Only users with :guilabel:`Administrator` rights for the Recruitment application can modify levels. The pre-configured levels can be seen and modified by navigating to :menuselection:`Referrals app --> Configuration --> Levels`. Each avatar appears in the :guilabel:`Image` column, and the corresponding level number appears in the :guilabel:`Level Name` column. The default images are of Odoo superheroes, and each level adds an additional element to their avatar, such as capes and shields." +msgstr "" + +#: ../../content/applications/hr/referrals.rst:646 +msgid "To modify a level's image, name, or points required to reach the level, click on an individual level in the list to open the level form. Click :guilabel:`Edit` to make modifications." +msgstr "" + +#: ../../content/applications/hr/referrals.rst:649 +msgid "Type in the name or number of the level in the :guilabel:`Level Name` field. What is entered is displayed beneath the user's photo on the main dashboard when they reach that level. Enter the number of referral points needed to reach that level in the :guilabel:`Requirements` field. The points needed to level up are the total accumulated points earned over the lifetime of the employee, not additional points from the previous level that must be earned." +msgstr "" + +#: ../../content/applications/hr/referrals.rst:655 +msgid "If desired, the :guilabel:`Image` can also be modified. Hover over the image to reveal a :guilabel:`✏️ (pencil)` icon and :guilabel:`🗑️ (garbage can)` icon. Click the :guilabel:`✏️ (pencil)` icon and a file explorer window appears. Navigate to the desired image file then click :guilabel:`Open` to select it." +msgstr "" + +#: ../../content/applications/hr/referrals.rst:-1 +msgid "A level form in edit mode." +msgstr "" + +#: ../../content/applications/hr/referrals.rst:672 +msgid "Once an image is changed and the level is saved, it is **not possible** to revert to the original image. To revert to the original image, the Referrals application must be *uninstalled then reinstalled.*" +msgstr "" + +#: ../../content/applications/hr/referrals.rst:677 +msgid "Level up" +msgstr "" + +#: ../../content/applications/hr/referrals.rst:679 +msgid "Once enough points have been accumulated to level up, the circle around the user's photo is completely filled in with a cyan color, a large image stating :guilabel:`Level up!` appears above the photo, and the phrase :guilabel:`Click to level up!` appears beneath the user's photo and current level." +msgstr "" + +#: ../../content/applications/hr/referrals.rst:684 +msgid "Click on either the :guilabel:`LEVEL UP!` graphic, the user's photo, or the text :guilabel:`Click to level up!` beneath the user's photo to level up the user. The user's avatar changes to the current level, and the ring around the photo is updated to indicate the current amount of points." +msgstr "" + +#: ../../content/applications/hr/referrals.rst:688 +msgid "Leveling up does not cost the user any points, the user simply needs to earn the specified amount of points required." +msgstr "" + +#: ../../content/applications/hr/referrals.rst:-1 +msgid "A 'Click to level up!' appears beneath the user's image, and a large 'Level up!' appears\n" +"above their image." +msgstr "" + +#: ../../content/applications/hr/referrals.rst:697 +msgid "Once a user has reached the highest configured level, they will continue to accrue points that can be redeemed for rewards, but they are no longer able to level up. The ring around their photo remains solid cyan." +msgstr "" + +#: ../../content/applications/hr/referrals.rst:702 +msgid "Alerts" +msgstr "" + +#: ../../content/applications/hr/referrals.rst:704 +msgid "In the Referrals application, it is possible to post a message, also referred to as an *alert*, at the top of the dashboard to share important information with users. These alerts appear as a thin semi-transparent banner, with the word :guilabel:`New!` appearing on the far left. The text for the alert is in the center of the banner, and on the far right side is an :guilabel:`X`." +msgstr "" + +#: ../../content/applications/hr/referrals.rst:709 +msgid "Alerts appear on the main dashboard for the specified time configured on the individual alert. If a user does not wish to see a specific alert again, click the :guilabel:`X` in the far right side of the alert. This removes the alert from the dashboard and will not appear again, even when opening the Referrals application for the first time in a new session." +msgstr "" + +#: ../../content/applications/hr/referrals.rst:-1 +msgid "Two alert banners appear above the user's photo." +msgstr "" + +#: ../../content/applications/hr/referrals.rst:719 +msgid "Create an alert" +msgstr "" + +#: ../../content/applications/hr/referrals.rst:721 +msgid "Only users with :guilabel:`Administrator` rights for the Recruitment application can create alerts. To add a new alert, navigate to the :menuselection:`Referrals application --> Configuration --> Alerts`." +msgstr "" + +#: ../../content/applications/hr/referrals.rst:725 +msgid "Click :guilabel:`Create` and a blank alert form loads. Enter the following information on the form:" +msgstr "" + +#: ../../content/applications/hr/referrals.rst:727 +msgid ":guilabel:`Date From`: The date the alert starts. On this date, the alert will be visible on the dashboard." +msgstr "" + +#: ../../content/applications/hr/referrals.rst:729 +msgid ":guilabel:`Date To`: The date the alert ends. After this date, the alert will be hidden from view." +msgstr "" + +#: ../../content/applications/hr/referrals.rst:730 +msgid ":guilabel:`Company`: The current company populates this field by default. To modify the company the alert should be displayed for, select the company from the drop-down menu. If this field remains blank, the alert is visible to everyone with access to the Referrals application. If a company is specified, only user's within that company (who also have access to the Referrals application) will see the alert." +msgstr "" + +#: ../../content/applications/hr/referrals.rst:735 +msgid ":guilabel:`Alert`: Enter the text for the alert. This message appears inside the alert banner on the main dashboard." +msgstr "" + +#: ../../content/applications/hr/referrals.rst:737 +msgid ":guilabel:`On Click`: There are three options for the alert. Click the radio button next to the desired selection. The options are:" +msgstr "" + +#: ../../content/applications/hr/referrals.rst:740 +msgid ":guilabel:`Not Clickable`: The alert only displays text, there is no link to click." +msgstr "" + +#: ../../content/applications/hr/referrals.rst:741 +msgid ":guilabel:`Go to All Jobs`: The alert contains a link that when clicked, navigates to the website with all the currently posted job positions." +msgstr "" + +#: ../../content/applications/hr/referrals.rst:743 +msgid ":guilabel:`Specify URL`: The alert contains a link to a specific URL, that when clicked, navigates to that URL. When selected, a :guilabel:`URL` field appears below the :guilabel:`On Click` section. Enter the URL in the field." +msgstr "" + +#: ../../content/applications/hr/referrals.rst:-1 +msgid "An alert form completely filled in with all selections entered." +msgstr "" + +#: ../../content/applications/hr/referrals.rst:756 +msgid "Only users with :guilabel:`Administrator` rights for the Recruitment application have access to the Reporting feature in Referrals. To access the reports, click :menuselection:`Referrals application --> Reporting`. The main view is the Reporting Dashboard view, which contains three sections." +msgstr "" + +#: ../../content/applications/hr/referrals.rst:760 +msgid "In the top portion of the window, the report displays a bar chart of how many referred candidates are hired, and how many are still in the hiring pipeline. The candidates are further divided by channel, showing specifically where the referral came from, such as a direct referral, Facebook, etc. If a channel does not appear on the report, that indicates there are no referrals from that particular channel." +msgstr "" + +#: ../../content/applications/hr/referrals.rst:766 +msgid "The middle third provides all the specific data that has been tracked. This includes how many total points have been earned across all referrals, how many applicants were referred, hired, or refused, how many applicants the current logged-in user referred, how many total points were earned, and how many points were given for refused applicants." +msgstr "" + +#: ../../content/applications/hr/referrals.rst:771 +msgid "The bottom third displays a pivot table. This table can be inserted into a new or existing spreadsheet. To do so, click the :guilabel:`Insert in Spreadsheet` button right above the chart. A pop-up appears, asking which spreadsheet to insert the pivot chart into. Select the desired spreadsheet from the drop-down menu, or select :guilabel:`New Spreadsheet`. Click :guilabel:`Confirm` and the selected spreadsheet loads, with the new table in it." +msgstr "" + +#: ../../content/applications/hr/referrals.rst:778 +msgid "The spreadsheet is stored in the *Documents* application. This application needs to be installed in order to use the :guilabel:`Insert in Spreadsheet` option." +msgstr "" diff --git a/locale/sources/inventory_and_mrp.pot b/locale/sources/inventory_and_mrp.pot index 953a4700e..120fdcf2c 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 saas-16.1\n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2023-12-19 13:26+0000\n" +"POT-Creation-Date: 2024-01-19 10:30+0000\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME \n" "Language-Team: LANGUAGE \n" @@ -38,35 +38,179 @@ msgid "Daily operations" msgstr "" #: ../../content/applications/inventory_and_mrp/barcode/operations/adjustments.rst:3 -msgid "Process to an Inventory Adjustment with Barcodes" +msgid "Apply inventory adjustments with barcodes" msgstr "" #: ../../content/applications/inventory_and_mrp/barcode/operations/adjustments.rst:5 -msgid "To process an inventory adjustment by using barcodes, you first need to open the *Barcode* app. Then, from the application, click on *Inventory Adjustments*." +msgid "In a warehouse, the recorded inventory counts in the database might not always match the actual, real inventory counts. In such cases, inventory adjustments can be made to reconcile the differences, and ensure that the recorded counts in the database match the actual counts in the warehouse. In Odoo, the *Barcode* app can be used to make these adjustments." msgstr "" -#: ../../content/applications/inventory_and_mrp/barcode/operations/adjustments.rst:13 -msgid "If you want to fully work with barcodes, you can download the sheet *Commands for Inventory*." +#: ../../content/applications/inventory_and_mrp/barcode/operations/adjustments.rst:10 +msgid "These adjustments can be done in real time using an Odoo-compatible barcode scanner or the Odoo mobile app." msgstr "" -#: ../../content/applications/inventory_and_mrp/barcode/operations/adjustments.rst:16 -msgid "Once you have clicked on *Inventory Adjustments*, Odoo will automatically create one. Note that, if you work with multi-location, you first need to specify in which location the inventory adjustment takes place." +#: ../../content/applications/inventory_and_mrp/barcode/operations/adjustments.rst:14 +msgid "For a list of Odoo-compatible barcode mobile scanners, and other hardware for the *Inventory* and *Barcode* apps, refer to the `Odoo Inventory • Hardware page `_." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/adjustments.rst:19 +msgid ":doc:`../../inventory/warehouses_storage/inventory_management/count_products`" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/adjustments.rst:22 +#: ../../content/applications/inventory_and_mrp/barcode/operations/receipts_deliveries.rst:15 +#: ../../content/applications/inventory_and_mrp/barcode/operations/transfers_scratch.rst:13 +msgid "Enable Barcode app" msgstr "" #: ../../content/applications/inventory_and_mrp/barcode/operations/adjustments.rst:24 -msgid "If you don’t work with multi-location, you will be able to scan the different products you want to include in the inventory adjustment." +msgid "To use the *Barcode* app to create and apply inventory adjustments, it **must** be installed by enabling the feature from the settings of the *Inventory* app." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/adjustments.rst:27 +msgid "To do so, go to the :menuselection:`Inventory app --> Configuration --> Settings`. Then, scroll down to the :guilabel:`Barcode` section, and click the checkbox next to the :guilabel:`Barcode Scanner` option." msgstr "" #: ../../content/applications/inventory_and_mrp/barcode/operations/adjustments.rst:31 -msgid "If you have 5 identical articles, scan it 5 times or use the keyboard to set the quantity." +#: ../../content/applications/inventory_and_mrp/barcode/operations/receipts_deliveries.rst:24 +#: ../../content/applications/inventory_and_mrp/barcode/operations/transfers_scratch.rst:22 +msgid "Once the checkbox is ticked, click :guilabel:`Save` at the top of the page to save changes." msgstr "" -#: ../../content/applications/inventory_and_mrp/barcode/operations/adjustments.rst:34 -msgid "Besides using the barcode scanner, you can also manually add a product if necessary. To do so, click on *Add Product* and fill the information in manually." +#: ../../content/applications/inventory_and_mrp/barcode/operations/adjustments.rst:33 +msgid "After saving, a new drop-down menu appears under the :guilabel:`Barcode Scanner` option, labeled :guilabel:`Barcode Nomenclature`, where either :guilabel:`Default Nomenclature` or :guilabel:`Default GS1 Nomenclature` can be selected. Each nomenclature option determines how scanners interpret barcodes in Odoo." msgstr "" -#: ../../content/applications/inventory_and_mrp/barcode/operations/adjustments.rst:44 -msgid "When you have scanned all the items of the location, validate the inventory manually or scan the *Validate* barcode." +#: ../../content/applications/inventory_and_mrp/barcode/operations/adjustments.rst:38 +msgid "There is also a :guilabel:`Configure Product Barcodes` internal link arrow, along with a set of :guilabel:`Print` buttons for printing barcode commands and a barcode demo sheet." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/adjustments.rst:-1 +#: ../../content/applications/inventory_and_mrp/barcode/operations/receipts_deliveries.rst:-1 +#: ../../content/applications/inventory_and_mrp/barcode/operations/transfers_scratch.rst:-1 +msgid "Enabled Barcode feature in Inventory app settings." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/adjustments.rst:46 +msgid "For more information on setting up and configuring the :guilabel:`Barcode` app, refer to the :doc:`Set up your barcode scanner <../setup/hardware>` and :doc:`Activate the Barcodes in Odoo <../setup/software>` docs." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/adjustments.rst:51 +msgid "Perform an inventory adjustment" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/adjustments.rst:53 +msgid "Begin by navigating to the :menuselection:`Barcode app --> Barcode Scanning` dashboard, where different options will be displayed, including :guilabel:`Operations`, :guilabel:`Inventory Adjustments`, and :guilabel:`Batch Transfers`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/adjustments.rst:57 +msgid "To create and apply inventory adjustments, click on the :guilabel:`Inventory Adjustments` button at the bottom of the screen." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/adjustments.rst:60 +#: ../../content/applications/inventory_and_mrp/barcode/operations/adjustments.rst:123 +msgid "Doing so navigates to the *Barcode Inventory Client Action* page, labeled as :guilabel:`Inventory Adjustment` in the top header section." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/adjustments.rst:-1 +#: ../../content/applications/inventory_and_mrp/barcode/operations/receipts_deliveries.rst:-1 +#: ../../content/applications/inventory_and_mrp/barcode/operations/transfers_scratch.rst:-1 +msgid "Barcode app start screen with scanner." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/adjustments.rst:67 +msgid "To begin the adjustment, first scan the *source location*, which is the current location in the warehouse of the product whose count should be adjusted. Then, scan the product barcode(s)." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/adjustments.rst:70 +msgid "The barcode of a specific product can be scanned multiple times to increase the quantity of that product in the adjustment." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/adjustments.rst:74 +msgid "If the warehouse *multi-location* feature is **not** enabled in the database, a source location does not need to be scanned. Instead, simply scan the product barcode to start the inventory adjustment." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/adjustments.rst:78 +msgid "Alternatively, the quantity can be changed by clicking the :guilabel:`✏️ (pencil)` icon on the far right of the product line." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/adjustments.rst:81 +msgid "Doing so opens a separate window with a keypad. Edit the number in the :guilabel:`Quantity` line to change the quantity. Additionally, the :guilabel:`+1` and :guilabel:`-1` buttons can be clicked to add or subtract quantity of the product, and the number keys can be used to add quantity, as well." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/adjustments.rst:86 +msgid "In the below inventory adjustment, the source location `WH/Stock/Shelf/2` was scanned, assigning the location. Then, the barcode for the product `[FURN_7888] Desk Stand with Screen` was scanned 3 times, increasing the units in the adjustment. Additional products can be added to this adjustment by scanning the barcodes for those specific products." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/adjustments.rst:0 +msgid "Barcode Inventory Client Action page with inventory adjustment." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/adjustments.rst:95 +msgid "To complete the inventory adjustment, click the green :guilabel:`✅ Apply` button with the check mark at the bottom of the page." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/adjustments.rst:98 +#: ../../content/applications/inventory_and_mrp/barcode/operations/adjustments.rst:150 +msgid "Once applied, Odoo navigates back to the :guilabel:`Barcode Scanning` screen. A small green banner appears in the top right corner, confirming validation of the adjustment." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/adjustments.rst:101 +#: ../../content/applications/inventory_and_mrp/barcode/operations/transfers_scratch.rst:180 +msgid "Did you know?" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/adjustments.rst:103 +msgid "Odoo's *Barcode* application provides demo data with barcodes to explore the features of the app. These can be used for testing purposes, and can be printed from the home screen of the app." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/adjustments.rst:106 +msgid "To access this demo data, navigate to the :menuselection:`Barcode app` and click :guilabel:`stock barcodes sheet` and :guilabel:`commands for Inventory` (bolded and highlighted in blue) in the information pop-up window above the scanner." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/adjustments.rst:0 +#: ../../content/applications/inventory_and_mrp/barcode/operations/transfers_scratch.rst:0 +msgid "Demo data prompt pop-up on Barcode app main screen." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/adjustments.rst:115 +msgid "Manually add products to inventory adjustment" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/adjustments.rst:117 +msgid "When the barcodes for the location or product are not available, Odoo *Barcode* can still be used to perform inventory adjustments." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/adjustments.rst:120 +msgid "To do this, navigate to the :menuselection:`Barcode app --> Barcode Scanning --> Inventory Adjustments`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/adjustments.rst:126 +msgid "To manually add products to this adjustment, click the white :guilabel:`➕ Add Product` button at the bottom of the screen." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/adjustments.rst:129 +msgid "This navigates to a new, blank page where the desired product, quantity, and source location must be chosen." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/adjustments.rst:0 +msgid "Keypad to add products on Barcode Inventory Client Action page." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/adjustments.rst:136 +msgid "First, click the :guilabel:`Product` line, and choose the product whose stock count should be adjusted. Then, manually enter the quantity of that product, either by changing the `1` in the :guilabel:`Quantity` line, or by clicking the :guilabel:`+1` and :guilabel:`-1` buttons to add or subtract quantity of the product. The number pad can be used to add quantity, as well." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/adjustments.rst:141 +msgid "Below the number pad is the :guilabel:`location` line, which should read `WH/Stock` by default. Click this line to reveal a drop-down menu of locations to choose from, and choose the :guilabel:`source location` for this inventory adjustment." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/adjustments.rst:145 +msgid "Once ready, click :guilabel:`Confirm` to confirm the changes." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/adjustments.rst:147 +msgid "To apply the inventory adjustment, click the green :guilabel:`✅ Apply` button with the check mark, at the bottom of the page." msgstr "" #: ../../content/applications/inventory_and_mrp/barcode/operations/barcode_nomenclature.rst:3 @@ -930,7 +1074,7 @@ msgid "Full GS1 barcode" msgstr "" #: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_usage.rst:147 -msgid "01206116289360043 000000050 10LOT0002" +msgid "0120611628936004 3000000050 10LOT0002" msgstr "" #: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_usage.rst:149 @@ -1025,96 +1169,394 @@ msgstr "" msgid "Reception stock move record for 52.1 kg of peaches." msgstr "" -#: ../../content/applications/inventory_and_mrp/barcode/operations/internal.rst:3 -msgid "Process to Transfers" +#: ../../content/applications/inventory_and_mrp/barcode/operations/receipts_deliveries.rst:3 +msgid "Process receipts and deliveries with barcodes" msgstr "" -#: ../../content/applications/inventory_and_mrp/barcode/operations/internal.rst:8 -msgid "Simple Transfers" +#: ../../content/applications/inventory_and_mrp/barcode/operations/receipts_deliveries.rst:7 +msgid "The *Barcode* app can be used to process receipts, deliveries, and other types of operations in real time using a barcode scanner or the Odoo mobile app." msgstr "" -#: ../../content/applications/inventory_and_mrp/barcode/operations/internal.rst:10 -msgid "To process a transfer from the *Barcode* app, the first step is to go to *Operations*." +#: ../../content/applications/inventory_and_mrp/barcode/operations/receipts_deliveries.rst:10 +msgid "This makes it possible to process operations on the warehouse floor when they happen, instead of having to wait to validate transfers from a computer. Processing operations this way can help to properly attribute barcodes to the appropriate products, pickings, locations, and more." msgstr "" -#: ../../content/applications/inventory_and_mrp/barcode/operations/internal.rst:16 -msgid "Then, you have the choice to either enter an existing transfer, by going to the corresponding operation type and manually selecting the one you want to enter, or by scanning the barcode of the transfer." +#: ../../content/applications/inventory_and_mrp/barcode/operations/receipts_deliveries.rst:17 +#: ../../content/applications/inventory_and_mrp/barcode/operations/transfers_scratch.rst:15 +msgid "To use the *Barcode* app to process transfers, it must be installed by enabling the feature from the settings of the *Inventory* app." msgstr "" -#: ../../content/applications/inventory_and_mrp/barcode/operations/internal.rst:26 -msgid "From there, you will be able to scan the products that are part of the existing transfer and/or add new products to this transfer. Once all the products have been scanned, you can validate the transfer to proceed with the stock moves." +#: ../../content/applications/inventory_and_mrp/barcode/operations/receipts_deliveries.rst:20 +#: ../../content/applications/inventory_and_mrp/barcode/operations/transfers_scratch.rst:18 +msgid "To do so, go to the :menuselection:`Inventory app --> Configuration --> Settings`. Then, scroll down to the :guilabel:`Barcode` section, and click the checkbox next to the :guilabel:`Barcode Scanner` feature." msgstr "" -#: ../../content/applications/inventory_and_mrp/barcode/operations/internal.rst:35 -msgid "If you have different storage locations in your warehouse, you can add additional steps for the different operation types." +#: ../../content/applications/inventory_and_mrp/barcode/operations/receipts_deliveries.rst:26 +msgid "Once the page has refreshed, new options will be displayed under the :guilabel:`Barcode Scanner` feature: :guilabel:`Barcode Nomenclature` (with a corresponding drop-down menu), where either :guilabel:`Default Nomenclature` or :guilabel:`Default GS1 Nomenclature` can be selected." msgstr "" -#: ../../content/applications/inventory_and_mrp/barcode/operations/internal.rst:41 -msgid "Receipts" +#: ../../content/applications/inventory_and_mrp/barcode/operations/receipts_deliveries.rst:30 +#: ../../content/applications/inventory_and_mrp/barcode/operations/transfers_scratch.rst:29 +msgid "There is also a :guilabel:`Configure Product Barcodes` internal link arrow, and a set of :guilabel:`Print` buttons for printing barcode commands and a barcode demo sheet." msgstr "" -#: ../../content/applications/inventory_and_mrp/barcode/operations/internal.rst:43 -msgid "When receiving a product in stock, you need to scan its barcode in order to identify it in the system. Once done, you can either make it enter the main location of the transfer, for example WH/Stock, or scan a location barcode to make it enter a sub-location of the main location." +#: ../../content/applications/inventory_and_mrp/barcode/operations/receipts_deliveries.rst:37 +#: ../../content/applications/inventory_and_mrp/barcode/operations/transfers_scratch.rst:36 +msgid "For more on setting up and configuring the :guilabel:`Barcode` app, refer to the :doc:`Set up your barcode scanner <../setup/hardware>` and :doc:`Activate the Barcodes in Odoo <../setup/software>` documentation pages." msgstr "" -#: ../../content/applications/inventory_and_mrp/barcode/operations/internal.rst:52 -msgid "If you want the product to enter WH/Stock in our example, you can simply scan the next product." +#: ../../content/applications/inventory_and_mrp/barcode/operations/receipts_deliveries.rst:44 +msgid "Scan barcodes for receipts" msgstr "" -#: ../../content/applications/inventory_and_mrp/barcode/operations/internal.rst:56 -msgid "Delivery Orders" +#: ../../content/applications/inventory_and_mrp/barcode/operations/receipts_deliveries.rst:46 +msgid "To process warehouse receipts for incoming products, there first needs to be a purchase order (PO) created, and a receipt operation to process." msgstr "" -#: ../../content/applications/inventory_and_mrp/barcode/operations/internal.rst:58 -msgid "When delivering a product, you have to scan the source location if it is different than the one initially set on the transfer. Then, you can start scanning the products that are delivered from this specific location." +#: ../../content/applications/inventory_and_mrp/barcode/operations/receipts_deliveries.rst:49 +msgid "To create a :abbr:`PO (purchase order)`, navigate to the :menuselection:`Purchase app --> Create` to create a new request for quotation (RFQ)." msgstr "" -#: ../../content/applications/inventory_and_mrp/barcode/operations/internal.rst:66 -msgid "Once the different products have been scanned, you have the possibility to scan another location, such as WH/Stock, and another page will be added to your delivery order. You can move from one to the other thanks to the *Previous* and *Next* buttons." +#: ../../content/applications/inventory_and_mrp/barcode/operations/receipts_deliveries.rst:52 +msgid "From the blank :abbr:`RFQ (request for quotation)` form, click the drop-down menu next to the :guilabel:`Vendor` field to add a vendor. Then, on the :guilabel:`Product` line under the :guilabel:`Products` tab, click :guilabel:`Add a product`, and select the desired product(s) to add to the quotation." msgstr "" -#: ../../content/applications/inventory_and_mrp/barcode/operations/internal.rst:74 -msgid "Now, you can validate your transfer. To do so, click on *Next* until you reach the last page of the transfer. There, you will be able to validate it." +#: ../../content/applications/inventory_and_mrp/barcode/operations/receipts_deliveries.rst:57 +msgid "Once ready, click :guilabel:`Save` at the top of the form, then click :guilabel:`Confirm Order` to confirm the :abbr:`RFQ (request for quotation)` to a :abbr:`PO (purchase order)`." msgstr "" -#: ../../content/applications/inventory_and_mrp/barcode/operations/internal.rst:82 -msgid "Internal Transfers" +#: ../../content/applications/inventory_and_mrp/barcode/operations/receipts_deliveries.rst:-1 +msgid "Completed purchase order for barcode product." msgstr "" -#: ../../content/applications/inventory_and_mrp/barcode/operations/internal.rst:84 -msgid "When realizing an internal transfer with multi-location, you first have to scan the source location of the product. Then, you can scan the product in itself, before having to scan the barcode of the destination location." +#: ../../content/applications/inventory_and_mrp/barcode/operations/receipts_deliveries.rst:64 +msgid "To process and scan barcodes for warehouse receipts, navigate to the :menuselection:`Barcode app`." msgstr "" -#: ../../content/applications/inventory_and_mrp/barcode/operations/internal.rst:89 -msgid "If the source and destination of the internal transfers are already correct, you don’t need to scan them." +#: ../../content/applications/inventory_and_mrp/barcode/operations/receipts_deliveries.rst:66 +msgid "Once inside the :guilabel:`Barcode app`, a :guilabel:`Barcode Scanning` screen displaying different options is presented. To process receipts, click on the :guilabel:`Operations` button at the bottom of the screen. This navigates to an :menuselection:`Operations` overview page." msgstr "" -#: ../../content/applications/inventory_and_mrp/barcode/operations/internal.rst:93 -msgid "Transfers with Tracked Products" +#: ../../content/applications/inventory_and_mrp/barcode/operations/receipts_deliveries.rst:74 +msgid "From this page, locate the :guilabel:`Receipts` card, and click the :guilabel:`# To Process` button to view all outstanding receipts. Then, select the desired receipt operation to process. This navigates to the barcode transfer screen." msgstr "" -#: ../../content/applications/inventory_and_mrp/barcode/operations/internal.rst:95 -msgid "If you work with products tracked by lot/serial numbers, you have two ways of working:" +#: ../../content/applications/inventory_and_mrp/barcode/operations/receipts_deliveries.rst:79 +msgid "If *only* using a barcode scanner or the Odoo mobile app, the barcodes for each transfer of a corresponding operation type can be scanned to be processed easily. Once scanned, the products that are part of an existing transfer can be scanned, and new products can be added to the transfer, as well. Once all products have been scanned, validate the transfer to proceed with the stock moves." msgstr "" -#: ../../content/applications/inventory_and_mrp/barcode/operations/internal.rst:98 -msgid "If you work with serial/lot numbers taking all products into consideration, you can scan the barcode of the lot/serial number and Odoo will increase the quantity of the product, setting its lot/serial number." +#: ../../content/applications/inventory_and_mrp/barcode/operations/receipts_deliveries.rst:85 +msgid "From this screen, an overview of all receipts to process within that transfer (**WH/IN/000XX**) is shown. At the bottom of the screen, there are options to :guilabel:`Add Product` or :guilabel:`Validate`, depending on if products need to be added to the operation, or if the whole operation should be validated at once." msgstr "" -#: ../../content/applications/inventory_and_mrp/barcode/operations/internal.rst:103 -msgid "If you have the same lot/serial number for different products, you can work by scanning the product barcode first, and then the barcode of the lot/serial number." +#: ../../content/applications/inventory_and_mrp/barcode/operations/receipts_deliveries.rst:-1 +#: ../../content/applications/inventory_and_mrp/barcode/operations/transfers_scratch.rst:-1 +msgid "Overview of receipts in transfer to scan." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/receipts_deliveries.rst:94 +msgid "To process and scan each product individually, choose a specific product line. The :guilabel:`+#` button (in this case, :guilabel:`+10`) can be clicked to indicate receipt of that product, or the :guilabel:`pencil` icon can be clicked to open a new screen to edit that product line." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/receipts_deliveries.rst:98 +msgid "From this screen, the product that's being received is listed. Under the product name, the :guilabel:`Quantity` line can be edited. Either change the `0` in the line to the desired quantity, or click the :guilabel:`/# Units` button (in this case, :guilabel:`/10 Units`) to automatically fill the quantity ordered from the :abbr:`PO (purchase order)`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/receipts_deliveries.rst:104 +msgid "In the reception operation `WH/IN/00019`, `10 Units` of the `Barcode Product` is expected to be received. `[BARCODE_PROD]` is the :guilabel:`Internal Reference` set on the product form. Scan the barcode of the `Barcode Product` to receive one unit. Afterwards, click the :guilabel:`pencil` icon to manually enter the received quantities." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/receipts_deliveries.rst:0 +#: ../../content/applications/inventory_and_mrp/barcode/operations/transfers_scratch.rst:0 +msgid "Product line editor for individual transfer in Barcode app." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/receipts_deliveries.rst:113 +#: ../../content/applications/inventory_and_mrp/barcode/operations/receipts_deliveries.rst:179 +msgid "Additionally, the :guilabel:`+1` and :guilabel:`-1` buttons can be clicked to add or subtract quantity of the product, and the :guilabel:`number keys` can be used to add quantity, as well." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/receipts_deliveries.rst:116 +msgid "Below the :guilabel:`number keys` is the :guilabel:`location` line, which reads `WH/Stock` by default, unless another *location* is listed on the product itself. Click this line to reveal a drop-down menu of additional locations to choose from." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/receipts_deliveries.rst:120 +#: ../../content/applications/inventory_and_mrp/barcode/operations/receipts_deliveries.rst:194 +#: ../../content/applications/inventory_and_mrp/barcode/operations/transfers_scratch.rst:158 +#: ../../content/applications/inventory_and_mrp/barcode/operations/transfers_scratch.rst:211 +msgid "Once ready, click :guilabel:`Confirm` to confirm the changes made to the product line." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/receipts_deliveries.rst:122 +msgid "Then, from the overview page with all receipts to process within that transfer (**WH/IN/000XX**), click the :guilabel:`+#` button on the product line for the products being received, and click :guilabel:`Validate`. The receipt has now been processed, and the :guilabel:`Barcode app` can be closed out." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/receipts_deliveries.rst:-1 +msgid "Overview of receipts in transfer to validate." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/receipts_deliveries.rst:132 +msgid "Scan barcodes for delivery orders" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/receipts_deliveries.rst:134 +msgid "To process warehouse deliveries for outgoing products, there first needs to be a sales order (SO) created, and a delivery operation to process." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/receipts_deliveries.rst:137 +msgid "To create a :abbr:`SO (sales order)`, navigate to the :menuselection:`Sales app --> Create` to create a new quotation." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/receipts_deliveries.rst:140 +msgid "From the blank quotation form, click the drop-down menu next to the :guilabel:`Customer` field to add a customer. Then, on the :guilabel:`Product` line under the :guilabel:`Order Lines` tab, click :guilabel:`Add a product`, and select the desired product(s) to add to the quotation." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/receipts_deliveries.rst:144 +msgid "Once ready, click :guilabel:`Save` at the top of the form, and click :guilabel:`Confirm Order` to confirm the quotation to a :abbr:`SO (sales order)`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/receipts_deliveries.rst:-1 +msgid "Completed sales order for barcode product." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/receipts_deliveries.rst:151 +msgid "To process and scan barcodes for warehouse deliveries, navigate to the :menuselection:`Barcode app`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/receipts_deliveries.rst:153 +msgid "Once inside the :guilabel:`Barcode app`, a :guilabel:`Barcode Scanning` screen displaying different options is presented. To process deliveries, click on the :guilabel:`Operations` button at the bottom of the screen. This navigates to an :guilabel:`Operations` overview page." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/receipts_deliveries.rst:157 +msgid "From this page, locate the :guilabel:`Delivery Orders` card, and click the :guilabel:`# To Process` button to view all outstanding deliveries. Then, select the desired delivery order to process. This navigates to the barcode transfer screen." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/receipts_deliveries.rst:-1 +msgid "Operations overview page in Barcode app dashboard." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/receipts_deliveries.rst:165 +msgid "From this screen, an overview of all deliveries to process within that transfer (**WH/OUT/000XX**) is shown. At the bottom of the screen, there are options to :guilabel:`Add Product` or :guilabel:`Validate`, depending on if products need to be added to the operation, or if the whole operation should be validated at once." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/receipts_deliveries.rst:170 +msgid "To process and scan each product individually, choose a specific product line. The :guilabel:`+1` button can be clicked to indicate delivery of that product, or the :guilabel:`pencil icon` can be clicked to open a new screen to edit that product line." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/receipts_deliveries.rst:174 +msgid "From this screen, the product that's being delivered is listed. Under the product name, the :guilabel:`Quantity` line can be edited. Either change the `0` in the line to the desired quantity, or click the :guilabel:`/# Units` button (in this case, :guilabel:`/10 Units`) to automatically fill the quantity ordered from the :abbr:`SO (sales order)`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/receipts_deliveries.rst:182 +msgid "Below the :guilabel:`number keys` is the :guilabel:`location` line, which reads `WH/Stock` by default, unless another location is listed on the product itself." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/receipts_deliveries.rst:185 +msgid "This is the location that the product is being pulled from for delivery. Click this line to reveal a drop-down menu of additional locations to choose from (if this product is stored in multiple locations in the warehouse)." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/receipts_deliveries.rst:190 +msgid "For warehouses that have multiple different storage locations, putaway rules, and removal strategies, additional steps can be added for various operation types, while using the *Barcode* app." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/receipts_deliveries.rst:196 +msgid "Then, from the overview page with all receipts to process within that transfer (**WH/OUT/000XX**), click the :guilabel:`+#` button on the product line for the products being received, and click :guilabel:`Validate`. The delivery has now been processed, and the *Barcode* app can be closed out." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/receipts_deliveries.rst:-1 +msgid "Overview of deliveries in transfer to validate." msgstr "" #: ../../content/applications/inventory_and_mrp/barcode/operations/transfers_scratch.rst:3 -msgid "Create a Transfer from Scratch" +msgid "Create and process transfers with barcodes" msgstr "" #: ../../content/applications/inventory_and_mrp/barcode/operations/transfers_scratch.rst:5 -msgid "To create a transfer from the *Barcode* application, you first need to print the operation type barcodes. To do so, you can download the *Stock barcode sheet* from the home page of the app." +msgid "The *Barcode* app can be used to process internal transfers for all types of products, including transfers for products tracked using lots or serial numbers. Transfers can be created from scratch in real time using an Odoo-compatible barcode scanner or the Odoo mobile app." msgstr "" -#: ../../content/applications/inventory_and_mrp/barcode/operations/transfers_scratch.rst:12 -msgid "Once done, you can scan the one for which you want to create a new document. Then, an empty document will be created and you will be able to scan your products to populate it." +#: ../../content/applications/inventory_and_mrp/barcode/operations/transfers_scratch.rst:9 +msgid "For a list of Odoo-compatible barcode mobile scanners, and other hardware for the *Inventory* app, refer to the `Odoo Inventory • Hardware page `_." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/transfers_scratch.rst:24 +msgid "When the page has refreshed, new options are displayed under the :guilabel:`Barcode Scanner` feature: :guilabel:`Barcode Nomenclature` (with a corresponding drop-down menu), where either :guilabel:`Default Nomenclature` or :guilabel:`Default GS1 Nomenclature` can be selected. The nomenclature selected changes how scanners interpret barcodes in Odoo." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/transfers_scratch.rst:41 +msgid "Scan barcodes for internal transfers" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/transfers_scratch.rst:43 +msgid "To create and process internal transfers for products in a warehouse, the :guilabel:`Storage Locations` and :guilabel:`Multi-Step Routes` features **must** be enabled." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/transfers_scratch.rst:46 +msgid "To do so, go to the :menuselection:`Inventory app --> Configuration --> Settings`. Then, scroll down to the :guilabel:`Warehouse` section, and click the checkboxes next to :guilabel:`Storage Locations` and :guilabel:`Multi-Step Routes`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/transfers_scratch.rst:50 +msgid "Then, click :guilabel:`Save` at the top of the page to save changes." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/transfers_scratch.rst:53 +msgid "Create an internal transfer" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/transfers_scratch.rst:55 +msgid "To process existing internal transfers, there first needs to be an internal transfer created, and an operation to process." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/transfers_scratch.rst:58 +msgid "To create an internal transfer, navigate to the :menuselection:`Inventory app`. From the :guilabel:`Inventory Overview` dashboard, locate the :guilabel:`Internal Transfers` card, and click on the :guilabel:`0 To Process` button." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/transfers_scratch.rst:62 +msgid "Then, click :guilabel:`Create` in the top left of the resulting page. This navigates to a new :guilabel:`Internal Transfer` form." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/transfers_scratch.rst:65 +msgid "On this blank form, the :guilabel:`Operation Type` is automatically listed as :guilabel:`Internal Transfers`. Under that field, the :guilabel:`Source Location` and :guilabel:`Destination Location` are set as :guilabel:`WH/Stock` by default, but can be changed to whichever locations the products are being moved from, and moved to." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/transfers_scratch.rst:-1 +msgid "Blank internal transfer form with source location and destination location." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/transfers_scratch.rst:74 +msgid "Once the desired locations have been selected, products can be added to the transfer. On the :guilabel:`Product` line under the :guilabel:`Products` tab, click :guilabel:`Add a product`, and select the desired product(s) to add to the transfer." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/transfers_scratch.rst:78 +msgid "Once ready, click :guilabel:`Save` at the top of the form to save the new internal transfer. Once saved, click the :guilabel:`Detailed Operations` icon (four lines, at the far right of the :guilabel:`Product` line) to open the :guilabel:`Detailed Operations` pop-up window." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/transfers_scratch.rst:-1 +msgid "Internal transfer detailed operations pop-up window." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/transfers_scratch.rst:86 +msgid "From the pop-up, click :guilabel:`Add a line`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/transfers_scratch.rst:88 +msgid "Then, in the :guilabel:`To` column, change the location from :guilabel:`WH/Stock` to a different location, where the products should be moved." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/transfers_scratch.rst:91 +msgid "Next, in the :guilabel:`Done` column, change the quantity to the desired quantity to transfer. Once ready, click :guilabel:`Confirm` to close out the pop-up window." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/transfers_scratch.rst:95 +msgid "Scan barcodes for internal transfer" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/transfers_scratch.rst:97 +msgid "To process and scan barcodes for internal transfers, navigate to the :menuselection:`Barcode app`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/transfers_scratch.rst:99 +msgid "Once inside the :guilabel:`Barcode app`, a :guilabel:`Barcode Scanning` screen displaying different options is presented." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/transfers_scratch.rst:102 +msgid "To process internal transfers, click on the :guilabel:`Operations` button at the bottom of the screen. This navigates to an :menuselection:`Operations` overview page." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/transfers_scratch.rst:109 +msgid "From this page, locate the :guilabel:`Internal Transfers` card, and click the :guilabel:`# To Process` button to view all outstanding internal transfers. Then, select the desired operation to process. This navigates to the barcode transfer screen." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/transfers_scratch.rst:114 +msgid "When using the *Barcode* app without the *Inventory* app (**only** if using a barcode scanner or the Odoo mobile app), the barcodes for each transfer of a corresponding operation type can be scanned to be processed easily." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/transfers_scratch.rst:118 +msgid "Once scanned, the products that are part of an existing transfer can be scanned, and new products can be added to the transfer, as well. Once all products have been scanned, validate the transfer to proceed with the stock moves." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/transfers_scratch.rst:122 +msgid "From this screen, an overview of all products to process within that specific internal transfer (**WH/INT/000XX**) is shown. At the bottom of the screen, there are options to :guilabel:`Add Product` or :guilabel:`Validate`, depending on if products need to be added to the operation, or if the whole operation should be validated at once." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/transfers_scratch.rst:131 +msgid "Then, scan the barcode of the product to process the internal transfer." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/transfers_scratch.rst:133 +msgid "Or, to process and scan each product individually, choose a specific product line. The :guilabel:`+ 1` button can be clicked to add additional quantity of that product to the transfer, or the :guilabel:`pencil icon` can be clicked to open a new screen to edit that product line." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/transfers_scratch.rst:137 +msgid "In the product's pop-up window, the product and the units to process is displayed with a number pad. Under the product name, the :guilabel:`Quantity` line can be edited. Change the number in the line to the quantity listed to be transferred on the internal transfer form." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/transfers_scratch.rst:142 +msgid "In the internal transfer operation `WH/INT/000XX`, `50 Units` of the `Transfer Product` is moved from `WH/Stock` to `WH/Stock/Shelf 1`. `[TRANSFER_PROD]` is the :guilabel:`Internal Reference` set on the product form. Scan the barcode of the `Transfer Product` to receive one unit. Afterwards, click the :guilabel:`pencil icon` to manually enter the transferred quantities." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/transfers_scratch.rst:151 +msgid "Additionally, the :guilabel:`+1` and :guilabel:`-1` buttons can be clicked to add or subtract quantity of the product, and the number keys can be used to add quantity, as well." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/transfers_scratch.rst:154 +msgid "Below the number keys are the two :guilabel:`location` lines, which read whichever locations were previously specified on the internal transfer form, in this case `WH/Stock` and `WH/Stock/Shelf 1`. Click these lines to reveal a drop-down menu of additional locations to choose from." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/transfers_scratch.rst:160 +msgid "Then, from the overview page with all products to process within that transfer (**WH/INT/000XX**), click :guilabel:`Validate`. The receipt has now been processed, and the *Barcode* app can be closed out." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/transfers_scratch.rst:165 +msgid "The *Barcode* app can also be used to scan products in internal transfers containing unique lot numbers and serial numbers." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/transfers_scratch.rst:168 +msgid "From the barcode transfer screen, scan the barcode of a lot or serial number, and Odoo automatically increases the quantity of the product to the quantity recorded in the database. If the same lot or serial number is shared between different products, scan the product barcode first, then the barcode of the lot/serial number." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/transfers_scratch.rst:174 +msgid "Create a transfer from scratch" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/transfers_scratch.rst:176 +msgid "In addition to processing and scanning barcodes for existing, previously-created internal transfers, the *Barcode* app can also be used to create transfers from scratch, simply by scanning a printed operation type barcode." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/transfers_scratch.rst:182 +msgid "Odoo's *Barcode* application provides demo data with barcodes to explore the features of the app. These can be used for testing purposes, and can be printed from the home screen of the app. To access this demo data, navigate to the :menuselection:`Barcode app` and click :guilabel:`stock barcodes sheet` (bolded and highlighted in blue) in the information pop-up above the scanner." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/transfers_scratch.rst:191 +msgid "To do this, first navigate to the :menuselection:`Barcode app`. Once inside the *Barcode* app, a :guilabel:`Barcode Scanning` screen displaying different options is presented." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/transfers_scratch.rst:194 +msgid "From this screen, when using a USB or bluetooth barcode scanner, directly scan the product barcode." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/transfers_scratch.rst:196 +msgid "When using a smartphone as the barcode scanner, click the :guilabel:`Tap to Scan` button (next to the camera icon, at the center of the screen). This opens a :guilabel:`Barcode Scanner` pop-up screen that enables the camera of the device being used." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/transfers_scratch.rst:200 +msgid "Face the camera toward the printed operation type barcode to scan it. Doing so processes the barcode, and navigates to a barcode transfer screen." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/transfers_scratch.rst:203 +msgid "From this screen, an overview of all products to process within that specific internal transfer (**WH/INT/000XX**) is shown. Since this is a new transfer created from scratch, however, there should not be any products listed on the page." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/transfers_scratch.rst:207 +msgid "To add products, scan the product barcode. If the barcode is not available, manually enter the product into the system by clicking the :guilabel:`Add Product` button at the bottom of the screen, and add the products and product quantities that should be transferred." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/transfers_scratch.rst:-1 +msgid "Blank product editor in scratch internal transfer." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/barcode/operations/transfers_scratch.rst:217 +msgid "Then, from the overview page with all products to process within that transfer (**WH/INT/000XX**), click :guilabel:`Validate`. The internal transfer has now been processed, and the *Barcode* app can be closed out." msgstr "" #: ../../content/applications/inventory_and_mrp/barcode/setup.rst:5 @@ -2019,55 +2461,111 @@ msgid "Product tracking" msgstr "" #: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/differences.rst:3 -msgid "What's the difference between lots and serial numbers?" +msgid "Difference between lots and serial numbers" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/differences.rst:6 -msgid "Introduction" +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/differences.rst:5 +msgid "*Lots* and *serial numbers* are the two ways to identify and track products in Odoo. While there are similarities between the two traceability methods, there are also notable differences that affect receipts, deliveries, and inventory reports." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/differences.rst:8 -msgid "In Odoo, lots and serial numbers have similarities in their functional system but are different in their behavior. They are both managed within the **Inventory**, **Purchases** and **Sales** app." +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/differences.rst:9 +msgid "A *lot* usually indicates a specific batch of an item that was received, is currently stored, or was shipped from a warehouse. However, it can also pertain to a batch of products manufactured in-house, as well." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/differences.rst:12 -msgid "**Lots** correspond to a certain number of products you received and store altogether in one single pack." +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/differences.rst:13 +msgid "A *serial number* is a unique identifier assigned incrementally (or sequentially) to an item or product, used to distinguish it from other items or products." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/differences.rst:15 -msgid "**Serial numbers** are identification numbers given to one product in particular, to allow to track the history of the item from reception to delivery and after-sales." +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/differences.rst:17 +msgid ":doc:`lots`" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/differences.rst:20 -msgid "When to use" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/differences.rst:22 -msgid "**Lots** are interesting for products you receive in great quantity and for which a lot number can help in reportings, quality controls, or any other info. Lots will help identify a number of pieces having for instance a production fault. It can be useful for a batch production of clothes or food." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/differences.rst:28 -msgid "**Serial numbers** are interesting for items that could require after-sales service, such as smartphones, laptops, fridges, and any electronic devices. You could use the manufacturer's serial number or your own, depending on the way you manage these products" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/differences.rst:34 -msgid "When not to use" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/differences.rst:36 -msgid "Storing consumable products such as kitchen roll, toilet paper, pens and paper blocks in lots would make no sense at all, as there are very few chances that you can return them for production fault." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/differences.rst:40 -msgid "On the other hand, giving a serial number to every product is a time-consuming task that will have a purpose only in the case of items that have a warranty and/or after-sales services. Putting a serial number on bread, for instance, makes no sense at all." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/differences.rst:46 +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/differences.rst:18 msgid ":doc:`serial_numbers`" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/differences.rst:47 -msgid ":doc:`lots`" +#: ../../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 +msgid "Enable lots & serial numbers" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/differences.rst:23 +msgid "To track products using lots and serial numbers, the *Lots & Serial Numbers* feature must be enabled." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/differences.rst:26 +msgid "To do that, go to the :menuselection:`Inventory app --> Configuration --> Settings`, scroll down to the :guilabel:`Traceability` section, and click the box next to :guilabel:`Lots & Serial Numbers`. Then, click the :guilabel:`Save` button to save changes." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/differences.rst:-1 +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/lots.rst:-1 +msgid "Enabled lots and serial numbers feature in inventory settings." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/differences.rst:35 +msgid "When to use lots" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/differences.rst:37 +msgid "Lots are useful for products that are manufactured or received in large quantities, such as clothes or food. Lots and can be used to trace a product back to a group, which is especially useful when managing product recalls or expiration dates." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/differences.rst:0 +msgid "Created lot with quantity of products in it." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/differences.rst:46 +msgid "Manufacturers assign lot numbers to groups of products that have common properties; this can lead to multiple goods sharing the same lot number. This helps identify a number of products in a single group, and allows for end-to-end traceability of these products through each step in their life cycles." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/differences.rst:52 +msgid "When to use serial numbers" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/differences.rst:54 +msgid "The goal of assigning serial numbers to individual products is to make sure every item's history is identifiable when it travels through the supply chain. This can be especially useful for manufacturers that provide after-sales services related to products they sell and deliver." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/differences.rst:0 +msgid "List of serial numbers for product." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/differences.rst:63 +msgid "Serial numbers can contain many different types of characters: numbers, letters, typographical symbols, or a mixture of all three types." +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 "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/differences.rst:69 +msgid "Manufacturers and companies can refer to traceability reports to see the entire life cycle of a product. These reports include vital information, like where it came from (and when), where it was stored, and to whom it was sent." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/differences.rst:73 +msgid "To see the full traceability of a product, or group products by lots and/or 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/differences.rst:77 +msgid "From here, products with lots or serial numbers assigned to them are listed by default. They can also be expanded to show what lots or serial numbers have been specifically assigned to them." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/differences.rst:80 +msgid "To group by lots or serial numbers, 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/differences.rst:85 +msgid "Doing so reveals all existing lots and serial numbers, and each can be expanded to show all product quantities with that assigned number. For unique serial numbers that are *not* reused, there should *only* be one product per serial number." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/differences.rst:-1 +msgid "Reporting page with drop-down lists of lots and serial numbers." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/differences.rst:94 +msgid "For additional information regarding an individual lot number or serial number, click the line item for the lot or serial number to reveal that specific number's :guilabel:`Lot` or :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. Any operations made using that lot or serial number can be found here, as well." msgstr "" #: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/expiration_dates.rst:3 @@ -2390,19 +2888,10 @@ msgstr "" msgid ":doc:`/applications/inventory_and_mrp/inventory/product_management/product_tracking/serial_numbers`" msgstr "" -#: ../../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 -msgid "Enable lots & serial numbers" -msgstr "" - #: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/lots.rst:24 msgid "To track products using lots, the *Lots & Serial Numbers* feature must be enabled. Go to the :menuselection:`Inventory app --> Configuration --> Settings`, scroll down to the :guilabel:`Traceability` section, and click the box next to :guilabel:`Lots & Serial Numbers`. Then, click the :guilabel:`Save` button to save changes." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/lots.rst:-1 -msgid "Enabled lots and serial numbers feature in inventory settings." -msgstr "" - #: ../../content/applications/inventory_and_mrp/inventory/product_management/product_tracking/lots.rst:36 msgid "Track products by lots" msgstr "" @@ -3912,7 +4401,7 @@ msgid "Activate multi-step routes and storage locations in inventory settings." msgstr "" #: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/delivery_three_steps.rst:30 -msgid "Next, the warehouse needs to be configured for three step deliveries. To do this, go to :menuselection:`Inventory --> Configuration --> Warehouses`, and click :guilabel:`Edit` to edit the :guilabel:`Warehouse`. Then, select :guilabel:`Pack goods, send goods in output and then deliver (3 steps)` for :guilabel:`Outgoing Shipments`. Then :guilabel:`Save` the changes." +msgid "Next, the warehouse needs to be configured for three step deliveries. To do this, go to :menuselection:`Inventory app --> Configuration --> Warehouses`, and click on the :guilabel:`warehouse` to edit. Then, select :guilabel:`Pack goods, send goods in output and then deliver (3 steps)` for :guilabel:`Outgoing Shipments`." msgstr "" #: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/delivery_three_steps.rst:-1 @@ -3920,19 +4409,19 @@ msgid "Set outgoing shipment option to deliver in three steps." msgstr "" #: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/delivery_three_steps.rst:39 -msgid "Activating three-step receipts and deliveries will create two new internal locations: a *Packing Zone* (WH/Packing Zone), and *Output* (WH/Output). To rename these locations, go to :menuselection:`Configuration --> Locations`, select the :guilabel:`Location` to change, click :guilabel:`Edit`, update the name, and finally, click :guilabel:`Save`." +msgid "Activating three-step receipts and deliveries creates two new internal locations: a *Packing Zone* (WH/Packing Zone), and *Output* (WH/Output). To rename these locations, go to :menuselection:`Inventory app --> Configuration --> Locations`, click on the :guilabel:`Location` to change, and update the name." msgstr "" #: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/delivery_three_steps.rst:45 -msgid "Process a delivery order in three steps (pick + pack + ship)" +msgid "Deliver in three steps (pick + pack + ship)" msgstr "" #: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/delivery_three_steps.rst:50 -msgid "In the :menuselection:`Sales` application, create a new quote by clicking :guilabel:`Create`. Select a :guilabel:`Customer`, add a storable :guilabel:`Product`, and click :guilabel:`Confirm`." +msgid "To create a new quote, navigate to :menuselection:`Sales app --> Create`, which reveals a blank quotation form. On the blank quotation form, select a :guilabel:`Customer`, add a storable :guilabel:`Product`, and click :guilabel:`Confirm`." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/delivery_three_steps.rst:53 -msgid "A :guilabel:`Delivery` smart button will appear in the top right. Clicking on it will show the picking order, packing order, and the delivery order, which are all associated with the sales order." +#: ../../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." msgstr "" #: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/delivery_three_steps.rst:-1 @@ -3940,11 +4429,11 @@ msgid "After confirming the sales order, the Delivery smart button appears showi "associated with it." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/delivery_three_steps.rst:62 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/delivery_three_steps.rst:63 msgid "Process a picking" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/delivery_three_steps.rst:64 +#: ../../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`." msgstr "" @@ -3953,11 +4442,11 @@ msgid "Ready status for the pick operation while the packing and delivery operat "another operation." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/delivery_three_steps.rst:72 +#: ../../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:78 +#: ../../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 "" @@ -3965,7 +4454,7 @@ msgstr "" 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:85 +#: ../../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 "" @@ -3974,11 +4463,11 @@ msgstr "" msgid "Validate the picking by clicking Validate." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/delivery_three_steps.rst:95 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/delivery_three_steps.rst:96 msgid "Process a packing" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/delivery_three_steps.rst:97 +#: ../../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." msgstr "" @@ -3986,7 +4475,7 @@ msgstr "" msgid "The packing order can be seen in the Inventory kanban view." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/delivery_three_steps.rst:105 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/delivery_three_steps.rst:106 msgid "Click on the packing order associated with the sales order, then click on :guilabel:`Validate` to complete the packing." msgstr "" @@ -3995,15 +4484,15 @@ msgid "Click Validate on the packing order to transfer the product from the pack "output location." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/delivery_three_steps.rst:113 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/delivery_three_steps.rst:114 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:118 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/delivery_three_steps.rst:119 msgid "Process a delivery" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/delivery_three_steps.rst:120 +#: ../../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." msgstr "" @@ -4011,7 +4500,7 @@ msgstr "" 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:128 +#: ../../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 "" @@ -4021,7 +4510,7 @@ msgid "Click Validate on the delivery order to transfer the product from the out "the customer location." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/delivery_three_steps.rst:136 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/delivery_three_steps.rst:137 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 "" @@ -4063,7 +4552,7 @@ msgstr "" #: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_one_step.rst:37 #: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_delivery_two_steps.rst:69 -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_three_steps.rst:46 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_three_steps.rst:48 msgid "Create a purchase order" msgstr "" @@ -4352,34 +4841,38 @@ msgid "Activate multi-step routes and storage locations in Inventory settings." msgstr "" #: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_three_steps.rst:28 -msgid "Next, the warehouse needs to be configured for three-step receipts. Go to :menuselection:`Inventory --> Configuration --> Warehouses`, and click :guilabel:`Edit` to edit the warehouse. Then, select :guilabel:`Receive goods in input, then quality and then stock (3 steps)` for :guilabel:`Incoming Shipments`. Then, :guilabel:`Save` the changes." +msgid "Next, the warehouse needs to be configured for three-step receipts. To do that, go to :menuselection:`Inventory app --> Configuration --> Warehouses`, and select the desired warehouse to be edited. Doing so reveals the detail form for that specific warehouse." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_three_steps.rst:32 +msgid "On that :guilabel:`Warehouse` detail form page, select :guilabel:`Receive goods in input, then quality and then stock (3 steps)` for :guilabel:`Incoming Shipments`." msgstr "" #: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_three_steps.rst:-1 msgid "Set incoming shipment option to receive in three steps." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_three_steps.rst:37 -msgid "Activating three-step receipts and deliveries will create two new internal locations: *Input* (WH/Input), and *Quality Control* (WH/Quality Control). To rename these locations, go to :menuselection:`Configuration --> Locations`, select the :guilabel:`Location` to change, click :guilabel:`Edit`, update the name, and finally, click :guilabel:`Save`." +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_three_steps.rst:39 +msgid "Activating three-step receipts and deliveries creates two new internal locations: *Input* (WH/Input), and *Quality Control* (WH/Quality Control). To rename these locations, go to :menuselection:`Inventory app --> Configuration --> Locations`, then click on the desired location to change (or update) the name." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_three_steps.rst:43 -msgid "Process a receipt in three steps (input + quality + stock)" +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_three_steps.rst:45 +msgid "Receive in three steps (input + quality + stock)" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_three_steps.rst:48 -msgid "In the :menuselection:`Purchase` application, create a new quote by clicking :guilabel:`Create`. Select a :guilabel:`Vendor`, add a storable :guilabel:`Product`, and click :guilabel:`Confirm Order`." +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_three_steps.rst:50 +msgid "To create a new :abbr:`RfQ (Request for Quotation)`, navigate to :menuselection:`Purchase app --> New`, which reveals a blank :abbr:`RfQ (Request for Quotation)` form page. On this page, select a :guilabel:`Vendor`, add a storable :guilabel:`Product`, and click :guilabel:`Confirm Order`." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_three_steps.rst:52 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_three_steps.rst:54 msgid "A :guilabel:`Receipt` smart button will appear in the top right, and the receipt will be associated with the purchase order. Clicking on the :guilabel:`Receipt` smart button will show the receipt order." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_three_steps.rst:61 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_three_steps.rst:63 msgid "Process a receipt" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_three_steps.rst:63 +#: ../../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`." msgstr "" @@ -4388,15 +4881,15 @@ msgid "The status of the three receipt transfers will show which operation is re "are waiting another operation." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_three_steps.rst:72 +#: ../../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:77 +#: ../../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:82 +#: ../../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." msgstr "" @@ -4404,7 +4897,7 @@ msgstr "" msgid "One Receipt ready to process in the Inventory Overview kanban view." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_three_steps.rst:90 +#: ../../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 "" @@ -4413,15 +4906,15 @@ msgid "Validate the receipt by clicking Validate, and the product will be transf "WH/Quality location." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_three_steps.rst:99 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_three_steps.rst:101 msgid "Process a transfer to Quality Control" 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: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." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_three_steps.rst:110 +#: ../../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." msgstr "" @@ -4429,15 +4922,15 @@ msgstr "" msgid "Validate the internal transfer to move the item to the Quality Control location." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_three_steps.rst:120 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_three_steps.rst:122 msgid "Process a transfer to stock" 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: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." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/receipts_three_steps.rst:126 +#: ../../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." msgstr "" @@ -9704,7 +10197,7 @@ msgid "Managing BoMs for product variants" msgstr "" #: ../../content/applications/inventory_and_mrp/manufacturing/management/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 BoM for a product with variants saves time by preventing the need to manage multiple BoMs." +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 @@ -9712,35 +10205,199 @@ msgid "Activate product variants" msgstr "" #: ../../content/applications/inventory_and_mrp/manufacturing/management/product_variants.rst:12 -msgid "To activate variants, simply navigate to :menuselection:`Inventory --> Configuration --> Settings --> Products`, and then enable the :guilabel:`Variants` option. After that, click :guilabel:`Save` to apply the setting. For more information on configuring product variants, refer to :doc:`this page <../../../sales/sales/products_prices/products/variants>`." +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 +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 msgid "Selecting \"Variants\" from Inventory app settings." msgstr "" -#: ../../content/applications/inventory_and_mrp/manufacturing/management/product_variants.rst:22 +#: ../../content/applications/inventory_and_mrp/manufacturing/management/product_variants.rst:25 +msgid "Create custom product attributes" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/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 +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 +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 +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 +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 +msgid "Product variant attribute configuration screen." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/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 +msgid "Add product variants on the product form" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/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 +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 +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 +msgid "Once finished, click :guilabel:`Save` to save changes." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/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 +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 msgid "Apply BoM components to product variants" msgstr "" -#: ../../content/applications/inventory_and_mrp/manufacturing/management/product_variants.rst:24 -msgid "Next, create a new BoM or edit an existing one by going to :menuselection:`Manufacturing --> Products --> Bills of Materials`. Then, click :guilabel:`Edit`. The :guilabel:`Apply on Variants` option to assign components to specific product variants on the BoM is available once the :guilabel:`Variants` setting is activated from the :guilabel:`Inventory` application. If the :guilabel:`Apply on Variants` field is not immediately visible, activate it from the additional options menu." +#: ../../content/applications/inventory_and_mrp/manufacturing/management/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 +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 +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 +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 +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 msgid "\"Apply on Variants\" option on the additional options menu." msgstr "" -#: ../../content/applications/inventory_and_mrp/manufacturing/management/product_variants.rst:35 +#: ../../content/applications/inventory_and_mrp/manufacturing/management/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:39 -msgid "When defining variant BoMs by component assignment, the :guilabel:`Product Variant` field in the main section of the BoM should be left blank, as shown below. This field is used only when creating a BoM specifically for one product variant." +#: ../../content/applications/inventory_and_mrp/manufacturing/management/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 +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 +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 +msgid "Sell and manufacture variants of BoM products" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/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 +msgid "Sell variant of BoM product" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/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 +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 +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 -msgid "Applying components to multiple variants." +msgid "Configure a product pop-up for choosing variant attributes." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/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 +msgid "Once ready, click :guilabel:`Confirm` to close the pop-up." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/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 +msgid "Manufacture variant of BoM product" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/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 +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 +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 +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 +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 +msgid "Manufacturing order for variant of BoM product." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/management/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 +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 +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 @@ -10127,10 +10784,6 @@ msgstr "" 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:114 -msgid "Traceability" -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 "" diff --git a/locale/sources/legal.pot b/locale/sources/legal.pot index 179e5d128..69c56b02f 100644 --- a/locale/sources/legal.pot +++ b/locale/sources/legal.pot @@ -8,7 +8,7 @@ msgid "" msgstr "" "Project-Id-Version: Odoo saas-16.1\n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2023-10-10 06:13+0000\n" +"POT-Creation-Date: 2024-01-19 10:30+0000\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME \n" "Language-Team: LANGUAGE \n" @@ -272,6 +272,7 @@ msgid "`Download PDF `_" msgstr "" -#: ../../content/legal/terms/i18n/enterprise_es.rst:12 -msgid "Esta es una traducción al español del \"Odoo Enterprise Subscription Agreement\". Esta traducción se proporciona con la esperanza de que facilite la comprensión, pero no tiene valor legal. La única referencia oficial de los términos y condiciones del \"Odoo Enterprise Subscription Agreement\" es :ref:`la versión original en inglés `" -msgstr "" - -#: ../../content/legal/terms/i18n/enterprise_es.rst:21 +#: ../../content/legal/terms/i18n/enterprise_es.rst:18 msgid "Al suscribirse a los servicios de Odoo Enterprise (en adelante “los Servicios”) proporcionados por Odoo SA y sus filiales (en adelante denominadas conjuntamente “Odoo SA”), relacionados con las versiones Odoo Enterprise o Odoo community (en adelante “el Software”) y alojados en los servidores de la nube de Odoo SA (en adelante “Servicio en la Nube”) o en servidores locales (en adelante “Auto-hospedaje”), usted (en adelante “el Cliente”) acepta los términos y condiciones establecidos a continuación (en adelante “el Acuerdo”)." msgstr "" -#: ../../content/legal/terms/i18n/enterprise_es.rst:31 +#: ../../content/legal/terms/i18n/enterprise_es.rst:28 msgid "1 Término del Acuerdo" msgstr "" -#: ../../content/legal/terms/i18n/enterprise_es.rst:33 +#: ../../content/legal/terms/i18n/enterprise_es.rst:30 msgid "La duración de la suscripción (en adelante el “Plazo”) será indicada por escrito en este Acuerdo, y comenzará a partir de la fecha de firma del Acuerdo. La suscripción se considerará renovada automáticamente por un período igual al Plazo estipulado originalmente, salvo que alguna de las partes del Acuerdo proporcione un aviso por escrito expresando su deseo de culminar los Servicios al menos 30 días antes de la fecha de culminación del Acuerdo." msgstr "" -#: ../../content/legal/terms/i18n/enterprise_es.rst:42 +#: ../../content/legal/terms/i18n/enterprise_es.rst:39 msgid "2 Definiciones" msgstr "" -#: ../../content/legal/terms/i18n/enterprise_es.rst:48 +#: ../../content/legal/terms/i18n/enterprise_es.rst:45 msgid "Usuario" msgstr "" -#: ../../content/legal/terms/i18n/enterprise_es.rst:45 +#: ../../content/legal/terms/i18n/enterprise_es.rst:42 msgid "El término usuario hace referencia a cualquier cuenta de usuario identificada como activa en el Software, con potestates de creación y/o edición. No se consideran como Usuarios a las cuentas desactivadas y aquellas cuentas utilizadas por personas (o sistemas) que solo tienen acceso limitado al Software a través del portal del usuario." msgstr "" -#: ../../content/legal/terms/i18n/enterprise_es.rst:53 +#: ../../content/legal/terms/i18n/enterprise_es.rst:49 msgid "Aplicación" msgstr "" -#: ../../content/legal/terms/i18n/enterprise_es.rst:51 -msgid "Una ‘aplicación’ es un grupo especializado de funciones disponibles para ser instaladas en el Software, las cuales están enunciadas en la sección de Precios del `sitio web de Odoo SA `__" +#: ../../content/legal/terms/i18n/enterprise_es.rst:48 +msgid "Una ‘Aplicación’ es un grupo especializado de funciones disponibles para ser instaladas en el Software." msgstr "" -#: ../../content/legal/terms/i18n/enterprise_es.rst:59 +#: ../../content/legal/terms/i18n/enterprise_es.rst:55 msgid "Partner de Odoo" msgstr "" -#: ../../content/legal/terms/i18n/enterprise_es.rst:56 +#: ../../content/legal/terms/i18n/enterprise_es.rst:52 msgid "Un ‘Partner’ de Odoo es una empresa o individuo externo a Odoo SA que ofrece servicios relacionados con el Software, y quien ha sido seleccionado por el Cliente para trabajar directamente con él. En cualquier momento, el cliente puede decidir trabajar con un Partner diferente o con Odoo SA directamente (sujeto a previo aviso)." msgstr "" -#: ../../content/legal/terms/i18n/enterprise_es.rst:66 -msgid "Módulo adicional" -msgstr "" - #: ../../content/legal/terms/i18n/enterprise_es.rst:62 -msgid "Un módulo adicional es un directorio de archivos de código fuente, o un conjunto de personalizaciones basadas en lenguaje de programación Python, creadas en una base de datos (por ejemplo, con Odoo Studio), que agrega características o cambia el comportamiento estándar de Software. Pueden haber sido desarrolladas por el Cliente, por Odoo SA, por un Partner de Odoo en nombre del Cliente o por terceros." +msgid "Módulo Adicional" msgstr "" -#: ../../content/legal/terms/i18n/enterprise_es.rst:71 -msgid "Módulo adicional de mantenimiento" +#: ../../content/legal/terms/i18n/enterprise_es.rst:58 +msgid "Un Módulo Adicional es un directorio de archivos de código fuente, o un conjunto de personalizaciones basadas en lenguaje de programación Python, creadas en una base de datos (por ejemplo, con Odoo Studio), que agrega características o cambia el comportamiento estándar de Software. Pueden haber sido desarrolladas por el Cliente, por Odoo SA, por un Partner de Odoo en nombre del Cliente o por terceros." msgstr "" -#: ../../content/legal/terms/i18n/enterprise_es.rst:69 -msgid "Un módulo adicional de mantenimiento es un módulo adicional por el cual el Cliente ha elegido pagar un costo de mantenimiento con el fin de obtener servicios de soporte, actualizaciones y corrección de errores." +#: ../../content/legal/terms/i18n/enterprise_es.rst:67 +msgid "Módulo Adicional Cubierto" msgstr "" -#: ../../content/legal/terms/i18n/enterprise_es.rst:80 -msgid "Error/Bug" +#: ../../content/legal/terms/i18n/enterprise_es.rst:65 +msgid "Un Módulo Adicional Cubierto es un Módulo Adicional por el cual el Cliente ha elegido pagar un costo de mantenimiento con el fin de obtener servicios de soporte, actualizaciones y corrección de Bugs." msgstr "" -#: ../../content/legal/terms/i18n/enterprise_es.rst:74 -msgid "Se considera como ‘bug’ a cualquier falla del Software o de un módulo adicional de mantenimiento que resulte en una disrupción completa, una cadena de errores o un fallo de seguridad, y que no es causado directamente por una instalación o configuración defectuosa. El incumplimiento de algunas especificaciones o requisitos será considerado como un Bug a la discreción de Odoo SA (por ejemplo, cuando el Software no cumple con el comportamiento ni los resultados para el cual fue diseñado, o cuando una característica específica del país deja de cumplir los requisitos legales de contabilidad)." +#: ../../content/legal/terms/i18n/enterprise_es.rst:70 +msgid "Se considera un Bug cualquier falla del Software o de un Módulo Adicional Cubierto que resulte en una parada completa, mensaje de error de fallo, o un fallo de seguridad, y que no es causado directamente por una instalación o configuración defectuosa. El incumplimiento de algunas especificaciones o requisitos será considerado como un Bug a la discreción de Odoo SA (por ejemplo, cuando el Software no cumple con el comportamiento ni los resultados para el cual fue diseñado, o cuando una característica específica del país deja de cumplir los requisitos legales de contabilidad)." msgstr "" -#: ../../content/legal/terms/i18n/enterprise_es.rst:85 +#: ../../content/legal/terms/i18n/enterprise_es.rst:81 msgid "Versiones Cubiertas" msgstr "" -#: ../../content/legal/terms/i18n/enterprise_es.rst:83 +#: ../../content/legal/terms/i18n/enterprise_es.rst:79 msgid "A menos que se especifique lo contrario, los Servicios proporcionados por en virtud de este Acuerdo son únicamente aplicables a las versiones cubiertas del Software, las cuales incluyen las últimas tres (3) versiones publicadas." msgstr "" +#: ../../content/legal/terms/i18n/enterprise_es.rst:85 +msgid "Plan de Suscripción" +msgstr "" + +#: ../../content/legal/terms/i18n/enterprise_es.rst:84 +msgid "Un Plan de Suscripción define un conjunto de Aplicaciones, funciones y soluciones de alojamiento cubiertas por este Acuerdo, y se define por escrito al concluir este Acuerdo." +msgstr "" + #: ../../content/legal/terms/i18n/enterprise_es.rst:90 msgid "3 Acceso al Software" msgstr "" @@ -1576,7 +1577,7 @@ msgid "Durante la vigencia de este Acuerdo, Odoo SA le otorga al Cliente una lic msgstr "" #: ../../content/legal/terms/i18n/enterprise_es.rst:102 -msgid "El Cliente acepta tomar todas las medidas necesarias para garantizar que no se modificará la parte del Software que ejecuta y verifica el uso y la recolección de estadísticas válidas, incluyendo pero sin limitarse a la ejecución de una instancia, el número de usuarios, las aplicaciones instaladas y el número de líneas de códigos incluidas en los módulos adicionales de mantenimiento." +msgid "El Cliente acepta tomar todas las medidas necesarias para garantizar que no se modificará la parte del Software que ejecuta y verifica el uso y la recolección de estadísticas válidas, incluyendo pero sin limitarse a la ejecución de una instancia, el número de usuarios, las aplicaciones instaladas y el número de líneas de códigos incluidas en los Módulos Adicionales Cubiertos." msgstr "" #: ../../content/legal/terms/i18n/enterprise_es.rst:107 @@ -1588,7 +1589,7 @@ msgid "Después de la expiración o terminación de este Acuerdo, la licencia co msgstr "" #: ../../content/legal/terms/i18n/enterprise_es.rst:115 -msgid "En caso de que exista algún incumplimiento por parte del Cliente a los términos de esta sección, el Cliente acuerda indemnizar a Odoo SA una cuota adicional equivalente al 300% del precio aplicable por el número actual de usuarios y aplicaciones instaladas." +msgid "En caso de que exista algún incumplimiento por parte del Cliente a los términos de esta sección, el Cliente acuerda indemnizar a Odoo SA una cuota adicional equivalente al 300% del precio aplicable por el número actual de usuarios." msgstr "" #: ../../content/legal/terms/i18n/enterprise_es.rst:122 @@ -1600,7 +1601,7 @@ msgid "4.1 Servicio de corrección de Bugs" msgstr "" #: ../../content/legal/terms/i18n/enterprise_es.rst:129 -msgid "Durante la vigencia de este Acuerdo, Odoo SA se compromete a hacer todos los esfuerzos razonables para remediar cualquier Bug presente en el Software y los Módulos adicionales de mantenimiento, que haya reportado el Cliente a través del medio apropiado (como el formulario del sitio web o vía llamada telefónica a los numeros enlistados en `Odoo Help `__, o cuando se trabaja con un Partner a través del medio establecido por el Partner), y a manejar las solicitudes del Cliente dentro de 2 días hábiles posteriores a la creación del reporte por parte del Cliente." +msgid "Durante la vigencia de este Acuerdo, Odoo SA se compromete a hacer todos los esfuerzos razonables para remediar cualquier Bug presente en el Software y los Módulos Adicionales Cubiertos, que haya reportado el Cliente a través del medio apropiado (como el formulario del sitio web o vía llamada telefónica a los numeros enlistados en `Odoo Help `__, o cuando se trabaja con un Partner a través del medio establecido por el Partner), y a manejar las solicitudes del Cliente dentro de 2 días hábiles posteriores a la creación del reporte por parte del Cliente." msgstr "" #: ../../content/legal/terms/i18n/enterprise_es.rst:137 @@ -1612,7 +1613,7 @@ msgid "Cuando se corrige un Bug de cualquiera de las versiones cubiertas, Odoo S msgstr "" #: ../../content/legal/terms/i18n/enterprise_es.rst:144 -msgid "Las partes de este Acuerdo reconocen que Odoo SA no es responsable de los Bugs en el Software o en los módulos adicionales de mantenimiento de conformidad con lo establecido en la sección 7.3 de este Acuerdo y en la licencia del Software." +msgid "Las partes de este Acuerdo reconocen que Odoo SA no es responsable de los Bugs en el Software o en los Módulos Adicionales Cubiertos de conformidad con lo establecido en la sección 7.3 de este Acuerdo y en la licencia del Software." msgstr "" #: ../../content/legal/terms/i18n/enterprise_es.rst:149 @@ -1664,7 +1665,7 @@ msgid "El Servicio de Actualización se limita a la conversión técnica y adapt msgstr "" #: ../../content/legal/terms/i18n/enterprise_es.rst:205 -msgid "El Cliente tiene la responsabilidad de verificar y validar la base de datos actualizada para detectar bugs, analizar e impacto de los cambios y las nuevas funcionalidades implementadas en la Versión Deseada, y de convertir y adaptar cualquier extensión del Software desarrollada por terceros que haya sido instalada antes de la actualización a la Versión Deseada (por ejemplo, módulos adicionales sin mantenimiento de Odoo). El Cliente puede enviar múltiples solicitudes de actualización de una base de datos hasta que se haya logrado un resultado aceptable." +msgid "El Cliente tiene la responsabilidad de verificar y validar la base de datos actualizada para detectar Bugs, analizar e impacto de los cambios y las nuevas funcionalidades implementadas en la Versión Deseada, y de convertir y adaptar cualquier extensión del Software desarrollada por terceros que haya sido instalada antes de la actualización a la Versión Deseada (por ejemplo, módulos adicionales sin mantenimiento de Odoo). El Cliente puede enviar múltiples solicitudes de actualización de una base de datos hasta que se haya logrado un resultado aceptable." msgstr "" #: ../../content/legal/terms/i18n/enterprise_es.rst:215 @@ -1708,7 +1709,7 @@ msgid "Alcance" msgstr "" #: ../../content/legal/terms/i18n/enterprise_es.rst:239 -msgid "Durante la vigencia del presente Acuerdo, el Cliente puede crear un número ilimitado de tickets de soporte sin costos adicionales, exclusivamente para preguntas relacionadas a Bugs (consultar sección :ref:`bugfix_es`) u orientación en cuanto al uso de las funcionalidades estándares del Software y de los módulos adicionales de mantenimiento." +msgid "Durante la vigencia del presente Acuerdo, el Cliente puede crear un número ilimitado de tickets de soporte sin costos adicionales, exclusivamente para preguntas relacionadas a Bugs (consultar sección :ref:`bugfix_es`) u orientación en cuanto al uso de las funcionalidades estándares del Software y de los Módulos Adicionales Cubiertos." msgstr "" #: ../../content/legal/terms/i18n/enterprise_es.rst:244 @@ -1732,11 +1733,11 @@ msgid "Para la corrección de Bugs, soporte y servicios de actualización, el Cl msgstr "" #: ../../content/legal/terms/i18n/enterprise_es.rst:264 -msgid "Odoo SA subcontratará los servicios relacionados a los Módulos adicionales de mantenimiento al Partner de Odoo, quien se convierte en el principal punto de contacto del Cliente en caso que el Cliente decida trabajar con un Partner de Odoo. El Partner de Odoo puede contactar a Odoo SA en nombre del Cliente para obtener asistencia de segundo nivel con respecto a las características estándar del Software." +msgid "Odoo SA subcontratará los servicios relacionados a los Módulos Adicionales Cubiertos al Partner de Odoo, quien se convierte en el principal punto de contacto del Cliente en caso que el Cliente decida trabajar con un Partner de Odoo. El Partner de Odoo puede contactar a Odoo SA en nombre del Cliente para obtener asistencia de segundo nivel con respecto a las características estándar del Software." msgstr "" #: ../../content/legal/terms/i18n/enterprise_es.rst:270 -msgid "Si el cliente decide trabajar con Odoo SA directamente, los servicios relacionados con los módulos adicionales de mantenimiento serán cubiertos por Odoo SA siempre que el Cliente esté alojado en la plataforma de la nube de Odoo." +msgid "Si el cliente decide trabajar con Odoo SA directamente, los servicios relacionados con los Módulos Adicionales Cubioertos serán cubiertos por Odoo SA siempre que el Cliente esté alojado en la plataforma de la nube de Odoo." msgstr "" #: ../../content/legal/terms/i18n/enterprise_es.rst:277 @@ -1748,322 +1749,322 @@ msgid "5.1 Cargos estándares" msgstr "" #: ../../content/legal/terms/i18n/enterprise_es.rst:284 -msgid "Los cargos estándares de la suscripción de Odoo Enterprise y los Servicios están basados en la cantidad de Usuarios y las Aplicaciones instaladas que utiliza el Cliente y se especifican por escrito al concluir el Acuerdo." +msgid "Los cargos estándares de la suscripción de Odoo Enterprise y los Servicios están basados en la cantidad de Usuarios y el Plan de Suscripción utilizado por el Cliente, y se especifican por escrito al concluir el Acuerdo." msgstr "" #: ../../content/legal/terms/i18n/enterprise_es.rst:288 -msgid "Si el Cliente tiene más usuarios o aplicaciones instaladas durante el Plazo que las especificadas en el momento de la celebración de este Acuerdo, el Cliente acepta pagar (al inicio del nuevo Plazo) una tarifa adicional equivalente al precio aplicable de conformidad con la lista de precios por aquellos usuarios o aplicaciones adicionales, por el resto del Plazo." +msgid "Si durante el Plazo del Acuerdo, el Cliente tiene más Usuarios o utiliza funciones que requieren otro Plan de Suscripción diferente al especificado en el momento de la conclusión de este Acuerdo, el Cliente acepta pagar una tarifa adicional equivalente al precio aplicable de conformidad con la lista de precios (en el momento de la desviación del número especificado de Usuarios o del Plan de Suscripción) por los Usuarios adicionales o el Plan de Suscripción requerido, por el resto del Plazo." msgstr "" -#: ../../content/legal/terms/i18n/enterprise_es.rst:293 -msgid "Además, los servicios de los módulos adicionales de mantenimiento se cobran en función al número de líneas de código de estos módulos. Cuando el cliente opta por el mantenimiento de estos módulos adicionales de mantenimiento, el costo es una tarifa mensual de 16 € por 100 líneas de código (redondeadas a las siguientes 100), al menos que se especifique lo contrario por escrito al celebrar este Acuerdo. Las líneas de código serán contadas con el comando ‘cloc’ del Software, e incluyen todas las líneas de texto en el código fuente de esos módulos, independientemente del lenguaje de programación (Python, Javascript, XML, etc), excluyendo líneas en blanco, comentarios y archivos que no se cargan al instalar o ejecutar el software." +#: ../../content/legal/terms/i18n/enterprise_es.rst:295 +msgid "Además, los servicios de los Módulos Adicionales Cubiertos se cobran en función al número de líneas de código de estos módulos. Cuando el cliente opta por el mantenimiento de Módulos Adicionales Cubiertos, el costo es una tarifa mensual de 16 € por 100 líneas de código (redondeadas a las siguientes 100), al menos que se especifique lo contrario por escrito al celebrar este Acuerdo. Las líneas de código serán contadas con el comando ‘cloc’ del Software, e incluyen todas las líneas de texto en el código fuente de esos módulos, independientemente del lenguaje de programación (Python, Javascript, XML, etc), excluyendo líneas en blanco, comentarios y archivos que no se cargan al instalar o ejecutar el software." msgstr "" -#: ../../content/legal/terms/i18n/enterprise_es.rst:302 -msgid "Cuando el Cliente solicita una actualización, por cada módulo adicional de mantenimiento que no haya sido cubierto por los costos de mantenimiento durante los últimos 12 meses, Odoo SA puede cobrar una tarifa adicional única de 16 € por cada 100 líneas de código, por cada mes faltante de cobertura." -msgstr "" - -#: ../../content/legal/terms/i18n/enterprise_es.rst:309 -msgid "5.2 Cargos de renovación" +#: ../../content/legal/terms/i18n/enterprise_es.rst:304 +msgid "Cuando el Cliente solicita una actualización, por cada Módulo Adicional Cubierto que no haya sido cubierto por los costos de mantenimiento durante los últimos 12 meses, Odoo SA puede cobrar una tarifa adicional única, por cada mes faltante de cobertura." msgstr "" #: ../../content/legal/terms/i18n/enterprise_es.rst:311 -msgid "Siguiendo la renovación descrita en la sección :ref:`term_es` del presente Acuerdo, si los cargos aplicados durante el Plazo anterior (excluyendo cualquier “Descuento para usuarios iniciales”) son más bajos que el precio aplicable en la lista de precios actual, dichos cargos podrán aumentar 7% como máximo." +msgid "5.2 Cargos de renovación" msgstr "" -#: ../../content/legal/terms/i18n/enterprise_es.rst:319 -msgid "5.3 Impuestos" +#: ../../content/legal/terms/i18n/enterprise_es.rst:313 +msgid "Siguiendo la renovación descrita en la sección :ref:`term_es` del presente Acuerdo, si los cargos aplicados durante el Plazo anterior son más bajos que el precio aplicable en la lista de precios actual, dichos cargos podrán aumentar 7% como máximo." msgstr "" #: ../../content/legal/terms/i18n/enterprise_es.rst:321 +msgid "5.3 Impuestos" +msgstr "" + +#: ../../content/legal/terms/i18n/enterprise_es.rst:323 msgid "Todas las tarifas y cargos son exclusivos de todos los impuestos, tarifas o cargos federales, provinciales, estatales, locales o gubernamentales aplicables (conjuntamente los “Impuestos”). El Cliente es responsable de pagar todos los Impuestos asociados con las compras realizadas por el Cliente en virtud de este Acuerdo, excepto cuando Odoo SA esté legítimamente obligado a pagar o recolectar los Impuestos que el Cliente debe asumir." msgstr "" -#: ../../content/legal/terms/i18n/enterprise_es.rst:330 +#: ../../content/legal/terms/i18n/enterprise_es.rst:332 msgid "6 Condiciones de los servicios" msgstr "" -#: ../../content/legal/terms/i18n/enterprise_es.rst:333 +#: ../../content/legal/terms/i18n/enterprise_es.rst:335 msgid "6.1 Obligaciones del cliente" msgstr "" -#: ../../content/legal/terms/i18n/enterprise_es.rst:335 +#: ../../content/legal/terms/i18n/enterprise_es.rst:337 msgid "El Cliente se compromete a:" msgstr "" -#: ../../content/legal/terms/i18n/enterprise_es.rst:337 +#: ../../content/legal/terms/i18n/enterprise_es.rst:339 msgid "Pagar a Odoo SA cualquier cargo aplicable por los Servicios del presente Acuerdo, según las condiciones de pago especificadas en la factura correspondiente;" msgstr "" -#: ../../content/legal/terms/i18n/enterprise_es.rst:341 -msgid "Notificar inmediatamente a Odoo SA cuando su número real de usarios o aplicaciones instaladas exceda el número especificado al final del Acuerdo y, en este caso, el pago de la tarifa adicional aplicable como se describe en la sección :ref:`charges_standard_es`;" +#: ../../content/legal/terms/i18n/enterprise_es.rst:343 +msgid "Notificar inmediatamente a Odoo SA cuando su número real de Usarios exceda la cantidad especificada al momento de la conclusión del Acuerdo, y en este caso, pagar la tarifa adicional aplicable como se describe en la sección :ref:`charges_standard_es`;" msgstr "" -#: ../../content/legal/terms/i18n/enterprise_es.rst:346 +#: ../../content/legal/terms/i18n/enterprise_es.rst:348 msgid "Tomar todas las medidas necesarias para garantizar la ejecución no modificada de la parte del Software que verifica la validez del uso de Odoo Enterprise Edition, como se describe en la sección :ref:`enterprise_access_es`;" msgstr "" -#: ../../content/legal/terms/i18n/enterprise_es.rst:350 +#: ../../content/legal/terms/i18n/enterprise_es.rst:352 msgid "Designar a 1 persona de contacto dedicada del Cliente durante toda la duración del Acuerdo;" msgstr "" -#: ../../content/legal/terms/i18n/enterprise_es.rst:352 +#: ../../content/legal/terms/i18n/enterprise_es.rst:354 msgid "Designar a 1 persona de contacto que se dedique al Cliente a lo largo de la Duración del Acuerdo;" msgstr "" -#: ../../content/legal/terms/i18n/enterprise_es.rst:354 +#: ../../content/legal/terms/i18n/enterprise_es.rst:356 msgid "Notificar por escrito a Odoo SA 30 días antes de cambiar el punto principal de contacto para trabajar con otro Partner de Odoo o directamente con Odoo SA" msgstr "" -#: ../../content/legal/terms/i18n/enterprise_es.rst:358 +#: ../../content/legal/terms/i18n/enterprise_es.rst:360 msgid "Cuando el Cliente elige usar la Plataforma en la nube, el Cliente acuerda además:" msgstr "" -#: ../../content/legal/terms/i18n/enterprise_es.rst:361 +#: ../../content/legal/terms/i18n/enterprise_es.rst:363 msgid "Tomar todas las medidas razonables para mantener sus cuentas de Usuario seguras, incluso al elegir una contraseña segura y no compartirla con nadie más;" msgstr "" -#: ../../content/legal/terms/i18n/enterprise_es.rst:365 +#: ../../content/legal/terms/i18n/enterprise_es.rst:367 msgid "Hacer uso razonable de los servicios de alojamiento, cone xclusiónde cualquier actividad ilegal o actividades abusivas, y observar estrictamente las reglas descritas en la Política de uso aceptable publicada en `acceptable use `__." msgstr "" -#: ../../content/legal/terms/i18n/enterprise_es.rst:369 +#: ../../content/legal/terms/i18n/enterprise_es.rst:371 msgid "Cuando el Cliente elige la opción de Auto-alojamiento, el Cliente acepta además:" msgstr "" -#: ../../content/legal/terms/i18n/enterprise_es.rst:372 +#: ../../content/legal/terms/i18n/enterprise_es.rst:374 msgid "Tomar todas las medidas razonables para proteger los archivos y las bases de datos del Cliente y para garantizar que los datos del Cliente sean seguros y estén protegidos, reconociendo que Odoo SA no se hace responsable de ninguna pérdida de datos" msgstr "" -#: ../../content/legal/terms/i18n/enterprise_es.rst:376 -msgid "Otorgar a Odoo SA el acceso necesario para verificar la validez de la Edición Enterprise de Odoo uso a solicitud (por ejemplo, si la validación automática no es válida para el Cliente);" +#: ../../content/legal/terms/i18n/enterprise_es.rst:378 +msgid "Otorgar a Odoo SA el acceso necesario para verificar la validez de la Edición Enterprise de Odoo uso a solicitud (por ejemplo, si la validación automática no es válida para el Cliente)." msgstr "" -#: ../../content/legal/terms/i18n/enterprise_es.rst:380 +#: ../../content/legal/terms/i18n/enterprise_es.rst:382 msgid "6.2 No solicitar o contratar" msgstr "" -#: ../../content/legal/terms/i18n/enterprise_es.rst:381 +#: ../../content/legal/terms/i18n/enterprise_es.rst:384 msgid "Excepto cuando la otra Parte de su consentimiento por escrito, cada una de las Partes, sus filiales y representantes acuerdan no solicitar u ofrecer empleo a ningún empleado de la otra Parte que esté involucrado en la prestación o el uso de los Servicios en virtud de este Acuerdo, durante la vigencia del Acuerdo y por un periodo de 12 meses a partir de la fecha de terminación o vencimiento de este Acuerdo. En caso que ocurra algún incumplimiento de las condiciones de esta sección, se dará por terminado el contrato con el empleado en cuestión y la Parte que ha incumplido esta prohibición acuerda indemnizar a la otra Parte la cifra de treinta mil euros 30.000 EUR (€)." msgstr "" -#: ../../content/legal/terms/i18n/enterprise_es.rst:392 +#: ../../content/legal/terms/i18n/enterprise_es.rst:395 msgid "6.3 Publicidad" msgstr "" -#: ../../content/legal/terms/i18n/enterprise_es.rst:394 +#: ../../content/legal/terms/i18n/enterprise_es.rst:397 msgid "Salvo que se notifique lo contrario por escrito, cada Parte otorga a la otra una licencia mundial intransferible, no exclusiva, libre de regalías, para reproducir y mostrar el nombre, logotipos y marcas de la otra Parte, con el único propósito de referirse a la otra Parte como su cliente o proveedor, en sitios web, comunicados de prensa y otros medios de marketing." msgstr "" -#: ../../content/legal/terms/i18n/enterprise_es.rst:402 +#: ../../content/legal/terms/i18n/enterprise_es.rst:405 msgid "6.4 Confidencialidad" msgstr "" -#: ../../content/legal/terms/i18n/enterprise_es.rst:410 +#: ../../content/legal/terms/i18n/enterprise_es.rst:413 msgid "Definición de \"Información confidencial\":" msgstr "" -#: ../../content/legal/terms/i18n/enterprise_es.rst:405 +#: ../../content/legal/terms/i18n/enterprise_es.rst:408 msgid "Toda la información divulgada por una de las Partes del presente Acuerdo, ya sea oralmente o por escrito, designada como confidencial o razonablemente considerada confidencial dada la naturaleza de la información y las circunstancias de divulgación. En particular, cualquier información relacionada a los negocios, asuntos, productos, desarrollos, secretos comerciales, “know-how”, el personal, los clientes y los proveedores de cualquiera de las Partes del presente Acuerdo, debe ser considerada como confidencial." msgstr "" -#: ../../content/legal/terms/i18n/enterprise_es.rst:412 +#: ../../content/legal/terms/i18n/enterprise_es.rst:415 msgid "Para cualquier tipo de información confidencial recibida durante el Plazo de este Acuerdo, la Parte que haya recibido la información confidencial hará uso del mismo grado de precaución que usaría esta Parte para proteger la confidencialidad de información similar que le pertenezca con un grado de precaución razonable." msgstr "" -#: ../../content/legal/terms/i18n/enterprise_es.rst:417 +#: ../../content/legal/terms/i18n/enterprise_es.rst:420 msgid "La Parte que haya recibido la información confidencial puede dar a conocer Información Confidencial de la Parte que haya divulgado dicha información en la medida en que la ley se lo permita. La Parte que haya recibido la información confidencial le dará aviso previo a la Parte que haya divulgado dicha información sobre la información que planea dar a conocer, en la medida en que la ley se lo permita." msgstr "" -#: ../../content/legal/terms/i18n/enterprise_es.rst:426 +#: ../../content/legal/terms/i18n/enterprise_es.rst:429 msgid "6.5 Protección de datos" msgstr "" -#: ../../content/legal/terms/i18n/enterprise_es.rst:431 +#: ../../content/legal/terms/i18n/enterprise_es.rst:434 msgid "Definiciones" msgstr "" -#: ../../content/legal/terms/i18n/enterprise_es.rst:429 +#: ../../content/legal/terms/i18n/enterprise_es.rst:432 msgid "Los términos “Datos Personales”, “Responsable del tratamiento”, “Tratamiento” tienen los mismos significados que en el Reglamento (UE) 2016/679 y la Directiva 2002/58 / CE, y cualquier reglamento o legislación que los modifique o sustituya (en adelante, “Legislacion de Proteccion de Datos”)." msgstr "" -#: ../../content/legal/terms/i18n/enterprise_es.rst:434 +#: ../../content/legal/terms/i18n/enterprise_es.rst:437 msgid "Procesamiento de datos personales" msgstr "" -#: ../../content/legal/terms/i18n/enterprise_es.rst:436 +#: ../../content/legal/terms/i18n/enterprise_es.rst:439 msgid "Las Partes reconocen que la base de datos del Cliente puede contener Datos Personales, de los cuales el Cliente es el Responsable del tratamiento. Esta data será procesada por Odoo SA cuando el Cliente lo indique, al usar cualquiera de los Servicios que requieran una base de datos (por ejemplo, el servicio de hospedaje en la nube o los servicios de actualizaciones), o si el Cliente transfiere su base de datos o una parte de su base de datos a Odoo SA por cualquier motivo relacionado con este Acuerdo." msgstr "" -#: ../../content/legal/terms/i18n/enterprise_es.rst:443 +#: ../../content/legal/terms/i18n/enterprise_es.rst:446 msgid "Este procesamiento se realizará de conformidad con la legislación de protección de datos. En particular, Odoo SA se compromete a:" msgstr "" -#: ../../content/legal/terms/i18n/enterprise_es.rst:446 +#: ../../content/legal/terms/i18n/enterprise_es.rst:449 msgid "(a) Solo procesar los datos personales cuando y como lo indique el Cliente, y para elp ropósito de realizar uno de los Servicios en virtud de este Acuerdo, a menos que sea requerido por la ley, en cuyo caso, Odoo SA proporcionará un aviso previo al Cliente, a menos que la ley lo prohíba;" msgstr "" -#: ../../content/legal/terms/i18n/enterprise_es.rst:449 +#: ../../content/legal/terms/i18n/enterprise_es.rst:452 msgid "(b) garantizar que todas las personas dentro de Odoo SA” autorizadas para procesar los Datos personales estén comprometidos con la confidencialidad;" msgstr "" -#: ../../content/legal/terms/i18n/enterprise_es.rst:451 +#: ../../content/legal/terms/i18n/enterprise_es.rst:454 msgid "(c) implementar y mantener medidas técnicas y organizativas adecuadas para proteger los datos personales contra el procesamiento no autorizado o ilegal y contra la pérdida accidental, destrucción, daño, robo, alteración o divulgación;" msgstr "" -#: ../../content/legal/terms/i18n/enterprise_es.rst:454 +#: ../../content/legal/terms/i18n/enterprise_es.rst:457 msgid "(d) enviará sin demora al Cliente cualquier solicitud de protección de datos que se haya enviado a Odoo SA con respecto a la base de datos del Cliente;" msgstr "" -#: ../../content/legal/terms/i18n/enterprise_es.rst:456 +#: ../../content/legal/terms/i18n/enterprise_es.rst:459 msgid "(e) notificar al Cliente inmediatamente al momento de conocer y confirmar cualquier accidente, el procesamiento no autorizado o ilegal de, la divulgación o el acceso a los datos personales;" msgstr "" -#: ../../content/legal/terms/i18n/enterprise_es.rst:458 +#: ../../content/legal/terms/i18n/enterprise_es.rst:461 msgid "(f) notificar al Cliente si las instrucciones de procesamiento infringen la Protección de datos aplicables a la legislación, en opinión de Odoo SA;" msgstr "" -#: ../../content/legal/terms/i18n/enterprise_es.rst:460 +#: ../../content/legal/terms/i18n/enterprise_es.rst:463 msgid "(g) poner a disposición del Cliente toda la información necesaria para demostrar el cumplimiento con la legislación de protección de datos, permitir y contribuir razonablemente a las auditorías, incluidas las inspecciones, realizadas o exigidas por el Cliente;" msgstr "" -#: ../../content/legal/terms/i18n/enterprise_es.rst:463 +#: ../../content/legal/terms/i18n/enterprise_es.rst:466 msgid "(h) eliminar permanentemente todas las copias de la base de datos del Cliente en posesión de Odoo SA, o devolver dichos datos, a elección del Cliente, a la terminación de este Acuerdo, sujeto a los retrasos especificados en la Política de privacidad de Odoo SA (`Privacy `__)." msgstr "" -#: ../../content/legal/terms/i18n/enterprise_es.rst:468 +#: ../../content/legal/terms/i18n/enterprise_es.rst:471 msgid "En relación a los puntos (d) y (f), el Cliente acepta proporcionar a Odoo SA información de contacto precisa en todo momento, según sea necesario para notificar al responsable de la Legislación de Protección de Datos del Cliente." msgstr "" -#: ../../content/legal/terms/i18n/enterprise_es.rst:473 +#: ../../content/legal/terms/i18n/enterprise_es.rst:476 msgid "Sub procesadores" msgstr "" -#: ../../content/legal/terms/i18n/enterprise_es.rst:475 +#: ../../content/legal/terms/i18n/enterprise_es.rst:478 msgid "El Cliente reconoce y acepta que, para proporcionar los Servicios, Odoo SA puede utilizar a terceros como proveedores de servicios para procesar Datos Personales (en adelante “Sub-procesadores”). Odoo SA se compromete a utilizar Sub-procesadores únicamente de conformidad con la Legislación de Protección de Datos. Este uso estará amparado bajo un contrato entre Odoo SA y el Sub-procesador que de garantías para estos servicios." msgstr "" -#: ../../content/legal/terms/i18n/enterprise_es.rst:481 +#: ../../content/legal/terms/i18n/enterprise_es.rst:484 msgid "La Política de privacidad de Odoo SA, publicada en `Odoo Privacy `_ establece información actualizada en relación a los nombres y propósitos de los Sub-procesadores que se encuentran actualmente en uso por Odoo SA para la ejecución de los Servicios." msgstr "" -#: ../../content/legal/terms/i18n/enterprise_es.rst:488 +#: ../../content/legal/terms/i18n/enterprise_es.rst:491 msgid "6.6 Terminación" msgstr "" -#: ../../content/legal/terms/i18n/enterprise_es.rst:490 +#: ../../content/legal/terms/i18n/enterprise_es.rst:493 msgid "En el supuesto de que alguna de las Partes incumpla con alguna de sus obligaciones establecidas en el presente Acuerdo, y si dicho incumplimiento no ha sido subsanado entre los siguientes 30 días contados a partir de la fecha de notificación escrita de dicho incumplimiento, este Acuerdo se considerará como terminado inmediatamente por la Parte que ha cumplido sus obligaciones." msgstr "" -#: ../../content/legal/terms/i18n/enterprise_es.rst:495 +#: ../../content/legal/terms/i18n/enterprise_es.rst:498 msgid "De igual manera, Odoo SA puede terminar el Acuerdo inmediatamente si el Cliente no cumple con su obligación de pago del Servicio dentro de los 21 días siguientes a la fecha de la respectiva facturación, y después de haber emitido al menos 3 recordatorios de pago." msgstr "" -#: ../../content/legal/terms/i18n/enterprise_es.rst:499 +#: ../../content/legal/terms/i18n/enterprise_es.rst:502 msgid "Disposiciones supervivientes: Las secciones \":ref:`confidentiality_es`\", “:ref:`disclaimers_es`\",“:ref:`liability_es`\", y “:ref:`general_provisions_es`” estarán vigentes incluso después de cualquier terminación o vencimiento del presente Acuerdo." msgstr "" -#: ../../content/legal/terms/i18n/enterprise_es.rst:506 +#: ../../content/legal/terms/i18n/enterprise_es.rst:509 msgid "7 Garantías, Renuncias, Responsabilidad Civil." msgstr "" -#: ../../content/legal/terms/i18n/enterprise_es.rst:511 +#: ../../content/legal/terms/i18n/enterprise_es.rst:514 msgid "7.1 Garantías" msgstr "" -#: ../../content/legal/terms/i18n/enterprise_es.rst:513 +#: ../../content/legal/terms/i18n/enterprise_es.rst:516 msgid "Odoo SA posee los derechos de autor o un equivalente [#cla1]_ sobre el 100% del código del Software. Odoo SA confirma que todas las bibliotecas de software necesarias para el uso del Software están disponibles bajo una licencia compatible con la licencia del Software." msgstr "" -#: ../../content/legal/terms/i18n/enterprise_es.rst:517 +#: ../../content/legal/terms/i18n/enterprise_es.rst:520 msgid "Durante la vigencia del presente Acuerdo, Odoo SA se compromete a emplear esfuerzos comercialmente razonables para ejecutar los Servicios de conformidad con los estándares de la industria generalmente aceptados, siempre que:" msgstr "" -#: ../../content/legal/terms/i18n/enterprise_es.rst:521 +#: ../../content/legal/terms/i18n/enterprise_es.rst:524 msgid "Los sistemas informáticos del Cliente se encuentren en un buen estado operacional y, para el alojamiento en servidores propios, el Software será instalado en un ambiente adecuado y operativo;" msgstr "" -#: ../../content/legal/terms/i18n/enterprise_es.rst:524 +#: ../../content/legal/terms/i18n/enterprise_es.rst:527 msgid "El Cliente brindará información pertinente para la resolución de problemas y, para el alojamiento en servidores propios, cualquier acceso que Odoo SA pueda necesitar para identificar, reproducir y solventar los problemas;" msgstr "" -#: ../../content/legal/terms/i18n/enterprise_es.rst:528 +#: ../../content/legal/terms/i18n/enterprise_es.rst:531 msgid "Todas las cantidades debidas a Odoo SA hayan sido pagadas." msgstr "" -#: ../../content/legal/terms/i18n/enterprise_es.rst:530 +#: ../../content/legal/terms/i18n/enterprise_es.rst:533 msgid "Odoo SA está obligado únicamente a reanudar la ejecución de los Servicios sin cargos adicionales en caso que Odoo SA incumpla alguna de las garantías establecidas. Este será el único y exclusivo recurso que el Cliente podrá usar." msgstr "" -#: ../../content/legal/terms/i18n/enterprise_es.rst:534 +#: ../../content/legal/terms/i18n/enterprise_es.rst:537 msgid "Contribuciones externas son cubiertas por el Acuerdo de Licencia de Derechos de Autor, el cual provee a Odoo SA una licencia de derechos de autor y de patente permanente, gratis e irrevocable." msgstr "" -#: ../../content/legal/terms/i18n/enterprise_es.rst:538 +#: ../../content/legal/terms/i18n/enterprise_es.rst:541 msgid "Las contribuciones externas están cubiertas por un `acuerdo de licencia de derechos de autor `__, que proporciona una licencia de derechos de autor y patente permanente, gratuita e irrevocable a Odoo SA." msgstr "" -#: ../../content/legal/terms/i18n/enterprise_es.rst:546 +#: ../../content/legal/terms/i18n/enterprise_es.rst:549 msgid "7.2 Aviso legal" msgstr "" -#: ../../content/legal/terms/i18n/enterprise_es.rst:548 +#: ../../content/legal/terms/i18n/enterprise_es.rst:551 msgid "Excepto por lo establecido expresamente en este Acuerdo, ninguna de las Partes podrá ofrecer garantías de ningún tipo, ya sean expresas, implícitas, estatutarias o de otro tipo, y cada Parte rechaza cualquier garantía implícita, tal y como garantías de comercialización, idóneas para un propósito especifico o de no cumplimiento, en la medida máxima permitida por la ley aplicable." msgstr "" -#: ../../content/legal/terms/i18n/enterprise_es.rst:553 +#: ../../content/legal/terms/i18n/enterprise_es.rst:556 msgid "Odoo SA no garantiza que el Software cumpla con leyes o regulaciones locales o internacionales." msgstr "" -#: ../../content/legal/terms/i18n/enterprise_es.rst:558 +#: ../../content/legal/terms/i18n/enterprise_es.rst:561 msgid "7.3 Limitación de responsabilidad" msgstr "" -#: ../../content/legal/terms/i18n/enterprise_es.rst:560 +#: ../../content/legal/terms/i18n/enterprise_es.rst:563 msgid "De conformidad a la medida máxima permitida por la ley, la responsabilidad agregada de cada una de las Partes junto con sus afiliados que surjan de o estén relacionados con este Acuerdo, no excederá el 50% del monto total pagado por el Cliente en virtud de este Acuerdo durante los 12 meses inmediatamente anteriores a la fecha del evento que da lugar a tal reclamo. Las reclamaciones múltiples no ampliarán esta limitación." msgstr "" -#: ../../content/legal/terms/i18n/enterprise_es.rst:566 -msgid "En ningún caso, ninguna de las Parte o sus afiliados serán responsables por daños directos, especiales, ejemplares, incidentales o consecuentes de cualquier tipo, incluidos, entre otros, la pérdida de ingresos, ganancias, ahorros, pérdida de negocios u otras pérdidas financieras, costos de inactividad o demora, datos perdidos o dañados, que surjan de o en conexión con este Acuerdo, independientemente de la forma de acción, ya sea en contrato, responsabilidad civil (incluida negligencia estricta) o cualquier otra teoría legal o equitativa, incluso si una de las Partes o sus afiliados han sido informados de la posibilidad de tales daños, o si las medidas de una de las Partes o sus afiliados no cumplen con su propósito esencial." +#: ../../content/legal/terms/i18n/enterprise_es.rst:569 +msgid "En ningún caso, ninguna de las Parte o sus afiliados serán responsables por daños directos, especiales, ejemplares, incidentales o consecuentes de cualquier tipo, incluidos, entre otros, la pérdida de ingresos, ganancias, ahorros, pérdida de negocios u otras pérdidas financieras, costos de inactividad o demora, datos perdidos o dañados, que surjan de o en conexión con este Acuerdo, independientemente de la forma de acción, ya sea en contrato, agravio u otra forma, incluso si una de las Partes o sus afiliados han sido informados de la posibilidad de tales daños, o si el remedio de una de las Partes o sus afiliados no cumplen con su propósito esencial." msgstr "" -#: ../../content/legal/terms/i18n/enterprise_es.rst:578 +#: ../../content/legal/terms/i18n/enterprise_es.rst:581 msgid "7.4 Fuerza mayor" msgstr "" -#: ../../content/legal/terms/i18n/enterprise_es.rst:580 +#: ../../content/legal/terms/i18n/enterprise_es.rst:583 msgid "Ninguna de las Partes será responsable ante la otra Parte por la demora o la falta de cumplimiento de sus obligaciones estipuladas en este Acuerdo cuando tal incumplimiento o retraso sea causado por fuerza mayor, tal y como regulaciones gubernamentales, incendios, huelgas, guerras, inundaciones, accidentes, epidemias, embargos, apropiaciones de instalaciones o productos en su totalidad o en parte por cualquier autoridad gubernamental o pública, o cualquier otra causa o causas, ya sean de naturaleza similares o diferentes, que están más allá del control razonable de dicha parte siempre que tal causa o causas existan efectivamente." msgstr "" -#: ../../content/legal/terms/i18n/enterprise_es.rst:591 +#: ../../content/legal/terms/i18n/enterprise_es.rst:594 msgid "8 Disposiciones generales" msgstr "" -#: ../../content/legal/terms/i18n/enterprise_es.rst:596 +#: ../../content/legal/terms/i18n/enterprise_es.rst:599 msgid "8.1 Ley aplicable" msgstr "" -#: ../../content/legal/terms/i18n/enterprise_es.rst:598 +#: ../../content/legal/terms/i18n/enterprise_es.rst:601 msgid "Este Acuerdo y todos los pedidos del Cliente estarán sujetos a las leyes del Reino de Bélgica. Cualquier disputa que surja en relación a este Acuerdo o de cualquier pedido del Cliente será sujeta a la jurisdicción exclusiva del Tribunal de Nivelles pertinente para litigar estas disputas." msgstr "" -#: ../../content/legal/terms/i18n/enterprise_es.rst:605 +#: ../../content/legal/terms/i18n/enterprise_es.rst:608 msgid "8.2 Divisibilidad" msgstr "" -#: ../../content/legal/terms/i18n/enterprise_es.rst:607 +#: ../../content/legal/terms/i18n/enterprise_es.rst:610 msgid "En caso de que una o más de las disposiciones establecidas en este Acuerdo o cualquiera de sus aplicaciones sean inválidas, ilegales o no exigibles en algún aspecto, la validez, legalidad y exigibilidad de las disposiciones restantes del presente Acuerdo y sus aplicaciones no se verán afectadas ni menoscabadas ninguna manera. Ambas Partes se comprometen a reemplazar cualquier provisión inválida, ilegal o inaplicable de este Acuerdo por una provisión válida que tenga el mismo efecto y objetivo." msgstr "" -#: ../../content/legal/terms/i18n/enterprise_es.rst:617 +#: ../../content/legal/terms/i18n/enterprise_es.rst:620 msgid "9 Apéndice A: Licencia de Odoo Enterprise Edition" msgstr "" -#: ../../content/legal/terms/i18n/enterprise_es.rst:621 +#: ../../content/legal/terms/i18n/enterprise_es.rst:624 msgid "La versión Enterprise de Odoo tiene la licencia Odoo Enterprise Edition v1.0, la cual es definida de la siguiente manera:" msgstr "" -#: ../../content/legal/terms/i18n/enterprise_es.rst:630 +#: ../../content/legal/terms/i18n/enterprise_es.rst:633 msgid "Ver :ref:`odoo_enterprise_license`." msgstr "" @@ -3877,135 +3878,131 @@ msgstr "" msgid "`Download PDF `_" msgstr "" -#: ../../content/legal/terms/i18n/partnership_es.rst:11 -msgid "Esta es una traducción al español del \"Odoo Partnership Agreement\". Esta traducción se proporciona con la esperanza de que facilitará la comprensión, pero no tiene valor legal. La única referencia oficial de los términos y condiciones del \"Odoo Partnership Agreement\" es :ref:`la versión original en inglés `." -msgstr "" - -#: ../../content/legal/terms/i18n/partnership_es.rst:29 +#: ../../content/legal/terms/i18n/partnership_es.rst:15 msgid "Versión 11 - 2023-05-19" msgstr "" -#: ../../content/legal/terms/i18n/partnership_es.rst:31 +#: ../../content/legal/terms/i18n/partnership_es.rst:17 #: ../../content/legal/terms/i18n/partnership_fr.rst:27 msgid "ENTRE:" msgstr "" -#: ../../content/legal/terms/i18n/partnership_es.rst:32 +#: ../../content/legal/terms/i18n/partnership_es.rst:18 msgid "Odoo S.A., una empresa que tiene su sede social en Chaussée de Namur, 40, 1367 Grand-Rosière," msgstr "" -#: ../../content/legal/terms/i18n/partnership_es.rst:33 +#: ../../content/legal/terms/i18n/partnership_es.rst:19 msgid "Bélgica, y sus filiales (en adelante denominados conjuntamente “ODOO”)" msgstr "" -#: ../../content/legal/terms/i18n/partnership_es.rst:34 +#: ../../content/legal/terms/i18n/partnership_es.rst:20 msgid "Y:" msgstr "" -#: ../../content/legal/terms/i18n/partnership_es.rst:35 +#: ../../content/legal/terms/i18n/partnership_es.rst:21 msgid "_____________________________________________, una empresa que tiene su domicilio social en" msgstr "" -#: ../../content/legal/terms/i18n/partnership_es.rst:36 +#: ../../content/legal/terms/i18n/partnership_es.rst:22 #: ../../content/legal/terms/i18n/partnership_fr.rst:32 #: ../../content/legal/terms/partnership.rst:28 msgid "_____________________________________________________________________________________." msgstr "" -#: ../../content/legal/terms/i18n/partnership_es.rst:37 +#: ../../content/legal/terms/i18n/partnership_es.rst:23 msgid "(en adelante denominado “EL COLABORADOR”)" msgstr "" -#: ../../content/legal/terms/i18n/partnership_es.rst:39 +#: ../../content/legal/terms/i18n/partnership_es.rst:25 msgid "ODOO y EL COLABORADOR se denominan individualmente “Parte” y conjuntamente “las Partes”." msgstr "" -#: ../../content/legal/terms/i18n/partnership_es.rst:42 +#: ../../content/legal/terms/i18n/partnership_es.rst:28 msgid "1 Objeto" msgstr "" -#: ../../content/legal/terms/i18n/partnership_es.rst:43 +#: ../../content/legal/terms/i18n/partnership_es.rst:30 msgid "El presente Contrato tiene por objeto regular las condiciones bajo las cuales ODOO presta servicios a EL COLABORADOR, acceso al software Odoo Enterprise Edition, y bajo las cuales EL COLABORADOR cumple con las obligaciones establecidas a continuación." msgstr "" -#: ../../content/legal/terms/i18n/partnership_es.rst:47 +#: ../../content/legal/terms/i18n/partnership_es.rst:34 msgid "Por la presente ODOO nombra a EL COLABORADOR, y EL COLABORADOR acepta ser nombrado, socio no exclusivo para promover y vender “Odoo Enterprise Edition” a los clientes." msgstr "" -#: ../../content/legal/terms/i18n/partnership_es.rst:50 +#: ../../content/legal/terms/i18n/partnership_es.rst:37 msgid "EL COLABORADOR se compromete a hacer su mejor esfuerzo para vender contratos de Odoo Enterprise a sus clientes. En apoyo a esta afirmación, EL COLABORADOR dará prioridad a la comercialización de la versión “Odoo Enterprise Edition” a clientes potenciales y clientes. EL COLABORADOR siempre tiene la posibilidad de vender servicios con otras versiones del software, como “Odoo Community Edition”, en caso de ser necesario." msgstr "" -#: ../../content/legal/terms/i18n/partnership_es.rst:57 +#: ../../content/legal/terms/i18n/partnership_es.rst:44 msgid "2 Duración del Contrato" msgstr "" -#: ../../content/legal/terms/i18n/partnership_es.rst:58 +#: ../../content/legal/terms/i18n/partnership_es.rst:46 msgid "La duración de este contrato será de un año (\"la Duración\") a partir de la fecha de la firma. Se renueva automáticamente por una duración igual, a menos que cualquiera de las partes notifique por escrito a la otra parte su terminación como mínimo 30 días antes del final de la duración." msgstr "" -#: ../../content/legal/terms/i18n/partnership_es.rst:63 +#: ../../content/legal/terms/i18n/partnership_es.rst:51 msgid "3 Acceso a Odoo Enterprise Edition" msgstr "" -#: ../../content/legal/terms/i18n/partnership_es.rst:66 +#: ../../content/legal/terms/i18n/partnership_es.rst:54 msgid "3.1 Acceso a la plataforma del proyecto" msgstr "" -#: ../../content/legal/terms/i18n/partnership_es.rst:67 +#: ../../content/legal/terms/i18n/partnership_es.rst:56 msgid "Para ayudar a EL COLABORADOR a promover Odoo Enterprise Edition, ODOO otorga a EL COLABORADOR acceso a su repositorio de código del proyecto para todas las “Aplicaciones Odoo Enterprise Edition”, en los términos establecidos en :ref:`appendix_p_a_es` y las condiciones restringidas del presente Contrato." msgstr "" -#: ../../content/legal/terms/i18n/partnership_es.rst:72 +#: ../../content/legal/terms/i18n/partnership_es.rst:61 msgid "Además, ODOO otorga a EL COLABORADOR acceso gratuito a la plataforma ODOO.SH con fines de prueba y desarrollo." msgstr "" -#: ../../content/legal/terms/i18n/partnership_es.rst:75 +#: ../../content/legal/terms/i18n/partnership_es.rst:64 msgid "EL COLABORADOR no tiene permitido bloquear, restringir o limitar de ninguna manera el acceso y uso de la Licencia Odoo Enterprise Edition por parte del cliente, sin consulta previa y autorización por escrito de ODOO." msgstr "" -#: ../../content/legal/terms/i18n/partnership_es.rst:82 +#: ../../content/legal/terms/i18n/partnership_es.rst:71 msgid "3.2 Restricciones" msgstr "" -#: ../../content/legal/terms/i18n/partnership_es.rst:83 +#: ../../content/legal/terms/i18n/partnership_es.rst:73 msgid "EL COLABORADOR se compromete a mantener la confidencialidad del código fuente de las aplicaciones Odoo Enterprise Edition entre su personal. El acceso al código fuente de Odoo Enterprise Edition para los clientes se rige por el Contrato de suscripción de Odoo Enterprise. EL COLABORADOR se compromete a NO redistribuir este código a terceros sin el permiso por escrito de ODOO." msgstr "" -#: ../../content/legal/terms/i18n/partnership_es.rst:89 +#: ../../content/legal/terms/i18n/partnership_es.rst:79 msgid "PARTNER se compromete a no ofrecer servicios en Odoo Enterprise Edition a clientes que no estén cubiertos por una suscripción de Odoo Enterprise, incluso durante la fase de implementación." msgstr "" -#: ../../content/legal/terms/i18n/partnership_es.rst:92 +#: ../../content/legal/terms/i18n/partnership_es.rst:82 msgid "A pesar de lo anterior, EL COLABORADOR se compromete a preservar por completo la integridad del código de Odoo Enterprise Edition necesario para verificar la validez del uso de Odoo Enterprise Edition y para recopilar estadísticas necesarias para este fin." msgstr "" -#: ../../content/legal/terms/i18n/partnership_es.rst:98 +#: ../../content/legal/terms/i18n/partnership_es.rst:88 msgid "4 Servicios de colaboración" msgstr "" -#: ../../content/legal/terms/i18n/partnership_es.rst:101 +#: ../../content/legal/terms/i18n/partnership_es.rst:91 msgid "4.1 Niveles de colaboración" msgstr "" -#: ../../content/legal/terms/i18n/partnership_es.rst:102 +#: ../../content/legal/terms/i18n/partnership_es.rst:93 msgid "El programa de socios de Odoo consta de dos tipos de asociaciones y cuatro niveles; \"Learning Partners\" es para empresas que desean todo lo necesario para comenzar a implementar Odoo, sin visibilidad como socio oficial hasta que obtengan la experiencia requerida; \"Official Partners\" es para empresas que desean la visibilidad como Ready, Silver y Gold, según su experiencia con Odoo." msgstr "" -#: ../../content/legal/terms/i18n/partnership_es.rst:108 +#: ../../content/legal/terms/i18n/partnership_es.rst:99 msgid "El nivel de colaboración otorgado a EL COLABORADOR depende de los *nuevos usuarios netos de Odoo Enterprise vendidos* en los últimos 12 meses, el número de recursos certificados y la Tasa de Retención de clientes. Los *nuevos usuarios netos de Odoo Enterprise vendidos* incluyen nuevos clientes, ventas adicionales a clientes existentes, reducciones en ventas a clientes existentes y la pérdida de clientes. Las renovaciones de contratos existentes no se cuentan como parte del número de usuarios vendidos, pero EL COLABORADOR aún recibe una comisión por estos contratos según se establece en la sección :ref:`benefits_es`." msgstr "" -#: ../../content/legal/terms/i18n/partnership_es.rst:117 +#: ../../content/legal/terms/i18n/partnership_es.rst:108 msgid "La tabla siguiente resume los requisitos para cada nivel de colaboración." msgstr "" -#: ../../content/legal/terms/i18n/partnership_es.rst:119 +#: ../../content/legal/terms/i18n/partnership_es.rst:110 msgid "La *Tasa de Retención* de clientes se calcula dividiendo el número total de clientes de Odoo Enterprise adquiridos por EL COLABORADOR en los últimos 3 años que están actualmente activos, entre el número total de clientes de Odoo Enterprise adquiridos por EL COLABORADOR en los últimos 3 años." msgstr "" -#: ../../content/legal/terms/i18n/partnership_es.rst:124 -#: ../../content/legal/terms/i18n/partnership_es.rst:157 +#: ../../content/legal/terms/i18n/partnership_es.rst:115 +#: ../../content/legal/terms/i18n/partnership_es.rst:148 #: ../../content/legal/terms/i18n/partnership_fr.rst:120 #: ../../content/legal/terms/i18n/partnership_fr.rst:153 #: ../../content/legal/terms/partnership.rst:112 @@ -4013,8 +4010,8 @@ msgstr "" msgid "Learning Partner" msgstr "" -#: ../../content/legal/terms/i18n/partnership_es.rst:124 -#: ../../content/legal/terms/i18n/partnership_es.rst:157 +#: ../../content/legal/terms/i18n/partnership_es.rst:115 +#: ../../content/legal/terms/i18n/partnership_es.rst:148 #: ../../content/legal/terms/i18n/partnership_fr.rst:120 #: ../../content/legal/terms/i18n/partnership_fr.rst:153 #: ../../content/legal/terms/partnership.rst:112 @@ -4022,8 +4019,8 @@ msgstr "" msgid "Official: Ready" msgstr "" -#: ../../content/legal/terms/i18n/partnership_es.rst:124 -#: ../../content/legal/terms/i18n/partnership_es.rst:157 +#: ../../content/legal/terms/i18n/partnership_es.rst:115 +#: ../../content/legal/terms/i18n/partnership_es.rst:148 #: ../../content/legal/terms/i18n/partnership_fr.rst:120 #: ../../content/legal/terms/i18n/partnership_fr.rst:153 #: ../../content/legal/terms/partnership.rst:112 @@ -4031,8 +4028,8 @@ msgstr "" msgid "Official: Silver" msgstr "" -#: ../../content/legal/terms/i18n/partnership_es.rst:124 -#: ../../content/legal/terms/i18n/partnership_es.rst:157 +#: ../../content/legal/terms/i18n/partnership_es.rst:115 +#: ../../content/legal/terms/i18n/partnership_es.rst:148 #: ../../content/legal/terms/i18n/partnership_fr.rst:120 #: ../../content/legal/terms/i18n/partnership_fr.rst:153 #: ../../content/legal/terms/partnership.rst:112 @@ -4040,12 +4037,12 @@ msgstr "" msgid "Official: Gold" msgstr "" -#: ../../content/legal/terms/i18n/partnership_es.rst:126 +#: ../../content/legal/terms/i18n/partnership_es.rst:117 msgid "Nuevos Usuarios netos de Odoo Enterprise vendidos anualmente" msgstr "" -#: ../../content/legal/terms/i18n/partnership_es.rst:126 -#: ../../content/legal/terms/i18n/partnership_es.rst:129 +#: ../../content/legal/terms/i18n/partnership_es.rst:117 +#: ../../content/legal/terms/i18n/partnership_es.rst:120 #: ../../content/legal/terms/i18n/partnership_fr.rst:122 #: ../../content/legal/terms/i18n/partnership_fr.rst:125 #: ../../content/legal/terms/partnership.rst:114 @@ -4053,175 +4050,175 @@ msgstr "" msgid "0" msgstr "" -#: ../../content/legal/terms/i18n/partnership_es.rst:126 +#: ../../content/legal/terms/i18n/partnership_es.rst:117 #: ../../content/legal/terms/i18n/partnership_fr.rst:122 #: ../../content/legal/terms/partnership.rst:114 msgid "10" msgstr "" -#: ../../content/legal/terms/i18n/partnership_es.rst:126 +#: ../../content/legal/terms/i18n/partnership_es.rst:117 msgid "50" msgstr "" -#: ../../content/legal/terms/i18n/partnership_es.rst:126 +#: ../../content/legal/terms/i18n/partnership_es.rst:117 #: ../../content/legal/terms/i18n/partnership_fr.rst:122 #: ../../content/legal/terms/partnership.rst:114 msgid "300" msgstr "" -#: ../../content/legal/terms/i18n/partnership_es.rst:129 +#: ../../content/legal/terms/i18n/partnership_es.rst:120 msgid "Número de empleados certificados en al menos uno de las 3 últimas versiones de Odoo" msgstr "" -#: ../../content/legal/terms/i18n/partnership_es.rst:129 +#: ../../content/legal/terms/i18n/partnership_es.rst:120 #: ../../content/legal/terms/i18n/partnership_fr.rst:125 #: ../../content/legal/terms/partnership.rst:116 msgid "1" msgstr "" -#: ../../content/legal/terms/i18n/partnership_es.rst:129 +#: ../../content/legal/terms/i18n/partnership_es.rst:120 #: ../../content/legal/terms/i18n/partnership_fr.rst:125 #: ../../content/legal/terms/partnership.rst:116 msgid "3" msgstr "" -#: ../../content/legal/terms/i18n/partnership_es.rst:129 +#: ../../content/legal/terms/i18n/partnership_es.rst:120 #: ../../content/legal/terms/i18n/partnership_fr.rst:125 #: ../../content/legal/terms/partnership.rst:116 msgid "6" msgstr "" -#: ../../content/legal/terms/i18n/partnership_es.rst:132 +#: ../../content/legal/terms/i18n/partnership_es.rst:123 msgid "Tasa de Retención mínima" msgstr "" -#: ../../content/legal/terms/i18n/partnership_es.rst:132 +#: ../../content/legal/terms/i18n/partnership_es.rst:123 #: ../../content/legal/terms/i18n/partnership_fr.rst:128 #: ../../content/legal/terms/partnership.rst:119 msgid "n/a" msgstr "" -#: ../../content/legal/terms/i18n/partnership_es.rst:132 +#: ../../content/legal/terms/i18n/partnership_es.rst:123 #: ../../content/legal/terms/i18n/partnership_fr.rst:128 #: ../../content/legal/terms/partnership.rst:119 msgid "70%" msgstr "" -#: ../../content/legal/terms/i18n/partnership_es.rst:132 +#: ../../content/legal/terms/i18n/partnership_es.rst:123 #: ../../content/legal/terms/i18n/partnership_fr.rst:128 #: ../../content/legal/terms/partnership.rst:119 msgid "80%" msgstr "" -#: ../../content/legal/terms/i18n/partnership_es.rst:135 +#: ../../content/legal/terms/i18n/partnership_es.rst:126 msgid "Las certificaciones son personales, por lo que cuando un miembro certificado del personal deja la empresa, EL COLABORADOR debe notificarlo a ODOO para que actualice la cantidad de recursos certificados activos para el contrato de colaboración." msgstr "" -#: ../../content/legal/terms/i18n/partnership_es.rst:139 +#: ../../content/legal/terms/i18n/partnership_es.rst:130 msgid "ODOO revisará trimestralmente el nivel de colaboración de EL COLABORADOR y lo ajustará al nivel más alto para el cual se cumplan los 3 requisitos." msgstr "" -#: ../../content/legal/terms/i18n/partnership_es.rst:142 +#: ../../content/legal/terms/i18n/partnership_es.rst:133 msgid "Sin embargo, los \"Official Partners\" pueden actualizarse automáticamente a un nivel superior una vez que alcancen los 3 requisitos para ese nivel de colaboración." msgstr "" -#: ../../content/legal/terms/i18n/partnership_es.rst:148 +#: ../../content/legal/terms/i18n/partnership_es.rst:139 msgid "4.2 Ventajas" msgstr "" -#: ../../content/legal/terms/i18n/partnership_es.rst:150 +#: ../../content/legal/terms/i18n/partnership_es.rst:141 msgid "En la tabla siguiente se describen los detalles de las ventajas para cada nivel de colaboración:" msgstr "" -#: ../../content/legal/terms/i18n/partnership_es.rst:159 +#: ../../content/legal/terms/i18n/partnership_es.rst:150 msgid "**Reconocimiento**" msgstr "" -#: ../../content/legal/terms/i18n/partnership_es.rst:161 +#: ../../content/legal/terms/i18n/partnership_es.rst:152 msgid "Visibilidad en odoo.com" msgstr "" -#: ../../content/legal/terms/i18n/partnership_es.rst:161 -#: ../../content/legal/terms/i18n/partnership_es.rst:190 -#: ../../content/legal/terms/i18n/partnership_es.rst:197 +#: ../../content/legal/terms/i18n/partnership_es.rst:152 +#: ../../content/legal/terms/i18n/partnership_es.rst:181 +#: ../../content/legal/terms/i18n/partnership_es.rst:188 #: ../../content/legal/terms/partnership.rst:148 #: ../../content/legal/terms/partnership.rst:178 #: ../../content/legal/terms/partnership.rst:185 msgid "No" msgstr "" -#: ../../content/legal/terms/i18n/partnership_es.rst:161 +#: ../../content/legal/terms/i18n/partnership_es.rst:152 #: ../../content/legal/terms/i18n/partnership_fr.rst:157 #: ../../content/legal/terms/partnership.rst:148 msgid "\"Ready Partner\"" msgstr "" -#: ../../content/legal/terms/i18n/partnership_es.rst:161 +#: ../../content/legal/terms/i18n/partnership_es.rst:152 #: ../../content/legal/terms/i18n/partnership_fr.rst:157 #: ../../content/legal/terms/partnership.rst:148 msgid "\"Silver Partner\"" msgstr "" -#: ../../content/legal/terms/i18n/partnership_es.rst:161 +#: ../../content/legal/terms/i18n/partnership_es.rst:152 #: ../../content/legal/terms/i18n/partnership_fr.rst:157 #: ../../content/legal/terms/partnership.rst:148 msgid "\"Gold Partner\"" msgstr "" -#: ../../content/legal/terms/i18n/partnership_es.rst:163 +#: ../../content/legal/terms/i18n/partnership_es.rst:154 msgid "Derechos de uso de la marca registrada “Odoo” y logotipos" msgstr "" -#: ../../content/legal/terms/i18n/partnership_es.rst:163 +#: ../../content/legal/terms/i18n/partnership_es.rst:154 +#: ../../content/legal/terms/i18n/partnership_es.rst:159 +#: ../../content/legal/terms/i18n/partnership_es.rst:161 +#: ../../content/legal/terms/i18n/partnership_es.rst:165 #: ../../content/legal/terms/i18n/partnership_es.rst:168 -#: ../../content/legal/terms/i18n/partnership_es.rst:170 -#: ../../content/legal/terms/i18n/partnership_es.rst:174 -#: ../../content/legal/terms/i18n/partnership_es.rst:177 -#: ../../content/legal/terms/i18n/partnership_es.rst:180 -#: ../../content/legal/terms/i18n/partnership_es.rst:190 -#: ../../content/legal/terms/i18n/partnership_es.rst:195 -#: ../../content/legal/terms/i18n/partnership_es.rst:197 +#: ../../content/legal/terms/i18n/partnership_es.rst:171 +#: ../../content/legal/terms/i18n/partnership_es.rst:181 +#: ../../content/legal/terms/i18n/partnership_es.rst:186 +#: ../../content/legal/terms/i18n/partnership_es.rst:188 msgid "Sí" msgstr "" -#: ../../content/legal/terms/i18n/partnership_es.rst:166 +#: ../../content/legal/terms/i18n/partnership_es.rst:157 msgid "**Ventajas de la formación**" msgstr "" -#: ../../content/legal/terms/i18n/partnership_es.rst:168 +#: ../../content/legal/terms/i18n/partnership_es.rst:159 msgid "Coaching de ventas y webinars" msgstr "" -#: ../../content/legal/terms/i18n/partnership_es.rst:170 +#: ../../content/legal/terms/i18n/partnership_es.rst:161 msgid "Acceso a la base de conocimiento Odoo" msgstr "" -#: ../../content/legal/terms/i18n/partnership_es.rst:172 +#: ../../content/legal/terms/i18n/partnership_es.rst:163 msgid "**Ventajas del software**" msgstr "" -#: ../../content/legal/terms/i18n/partnership_es.rst:174 +#: ../../content/legal/terms/i18n/partnership_es.rst:165 msgid "Acceso al código fuente de Odoo Enterprise y repositorio Github" msgstr "" -#: ../../content/legal/terms/i18n/partnership_es.rst:177 +#: ../../content/legal/terms/i18n/partnership_es.rst:168 msgid "Código de extensión de prueba de Odoo Enterprise" msgstr "" -#: ../../content/legal/terms/i18n/partnership_es.rst:180 +#: ../../content/legal/terms/i18n/partnership_es.rst:171 msgid "Acceso a Odoo.sh con fines de prueba y desarrollo." msgstr "" -#: ../../content/legal/terms/i18n/partnership_es.rst:183 +#: ../../content/legal/terms/i18n/partnership_es.rst:174 msgid "**Ventajas de las ventas**" msgstr "" -#: ../../content/legal/terms/i18n/partnership_es.rst:185 +#: ../../content/legal/terms/i18n/partnership_es.rst:176 msgid "Comisión por la plataforma Odoo SH [#s1]_" msgstr "" -#: ../../content/legal/terms/i18n/partnership_es.rst:185 -#: ../../content/legal/terms/i18n/partnership_es.rst:188 +#: ../../content/legal/terms/i18n/partnership_es.rst:176 +#: ../../content/legal/terms/i18n/partnership_es.rst:179 #: ../../content/legal/terms/i18n/partnership_fr.rst:179 #: ../../content/legal/terms/i18n/partnership_fr.rst:182 #: ../../content/legal/terms/partnership.rst:171 @@ -4229,189 +4226,189 @@ msgstr "" msgid "10%" msgstr "" -#: ../../content/legal/terms/i18n/partnership_es.rst:185 +#: ../../content/legal/terms/i18n/partnership_es.rst:176 #: ../../content/legal/terms/i18n/partnership_fr.rst:179 #: ../../content/legal/terms/partnership.rst:171 msgid "50%" msgstr "" -#: ../../content/legal/terms/i18n/partnership_es.rst:188 +#: ../../content/legal/terms/i18n/partnership_es.rst:179 msgid "Comisión por Odoo Enterprise" msgstr "" -#: ../../content/legal/terms/i18n/partnership_es.rst:188 +#: ../../content/legal/terms/i18n/partnership_es.rst:179 #: ../../content/legal/terms/i18n/partnership_fr.rst:182 #: ../../content/legal/terms/partnership.rst:173 msgid "15%" msgstr "" -#: ../../content/legal/terms/i18n/partnership_es.rst:188 +#: ../../content/legal/terms/i18n/partnership_es.rst:179 #: ../../content/legal/terms/i18n/partnership_fr.rst:182 #: ../../content/legal/terms/partnership.rst:173 msgid "20%" msgstr "" -#: ../../content/legal/terms/i18n/partnership_es.rst:190 +#: ../../content/legal/terms/i18n/partnership_es.rst:181 msgid "Acceso a un gestor de cuentas especializado y Partner Dashboard" msgstr "" -#: ../../content/legal/terms/i18n/partnership_es.rst:193 +#: ../../content/legal/terms/i18n/partnership_es.rst:184 msgid "**Ventajas de marketing**" msgstr "" -#: ../../content/legal/terms/i18n/partnership_es.rst:195 +#: ../../content/legal/terms/i18n/partnership_es.rst:186 msgid "Material de marketing" msgstr "" -#: ../../content/legal/terms/i18n/partnership_es.rst:197 +#: ../../content/legal/terms/i18n/partnership_es.rst:188 msgid "Evento de EL COLABORADOR - Asistencia y promoción de ODOO" msgstr "" -#: ../../content/legal/terms/i18n/partnership_es.rst:201 +#: ../../content/legal/terms/i18n/partnership_es.rst:192 msgid "hasta un máximo de 150€ (o $180) de comisión mensual por suscripción, o 1440€ (o $1728) de comisión anual por suscripción." msgstr "" -#: ../../content/legal/terms/i18n/partnership_es.rst:205 +#: ../../content/legal/terms/i18n/partnership_es.rst:196 msgid "4.3 Reconocimiento de socios" msgstr "" -#: ../../content/legal/terms/i18n/partnership_es.rst:206 +#: ../../content/legal/terms/i18n/partnership_es.rst:198 msgid "ODOO promocionará EL COLABORADOR como socio oficial en el sitio web oficial (odoo.com)." msgstr "" -#: ../../content/legal/terms/i18n/partnership_es.rst:208 +#: ../../content/legal/terms/i18n/partnership_es.rst:200 msgid "ODOO concede a EL COLABORADOR, de forma no exclusiva, el derecho a usar y reproducir el logotipo de socio de ODOO del nivel de colaboración correspondiente y el nombre “Odoo” en relación con este contrato de colaboración." msgstr "" -#: ../../content/legal/terms/i18n/partnership_es.rst:212 +#: ../../content/legal/terms/i18n/partnership_es.rst:204 msgid "Cada Parte se compromete a respetar todos los derechos de la otra Parte en todos los elementos mencionados en el párrafo anterior y, más concretamente, cada Parte debe abstenerse de causar cualquier analogía o crear confusión entre sus respectivas compañías en el público general, por cualquier motivo y por cualquier medio." msgstr "" -#: ../../content/legal/terms/i18n/partnership_es.rst:218 +#: ../../content/legal/terms/i18n/partnership_es.rst:210 msgid "4.4 Ventajas de la formación" msgstr "" -#: ../../content/legal/terms/i18n/partnership_es.rst:219 +#: ../../content/legal/terms/i18n/partnership_es.rst:212 msgid "EL COLABORADOR tiene acceso a la base de conocimiento de ODOO durante la duración de este Contrato. La base de conocimiento de ODOO es una plataforma electrónica en línea que contiene un conjunto de documentos comerciales, funcionales y de marketing para ayudar a EL COLABORADOR a adquirir y aprovechar el conocimiento de Odoo, hacer crecer su negocio, atraer más clientes y crear conciencia de marca." msgstr "" -#: ../../content/legal/terms/i18n/partnership_es.rst:225 +#: ../../content/legal/terms/i18n/partnership_es.rst:218 msgid "EL COLABORADOR podrá acceder al coaching comercial facilitado por su gestor de cuentas especializado, designado por ODOO." msgstr "" -#: ../../content/legal/terms/i18n/partnership_es.rst:228 +#: ../../content/legal/terms/i18n/partnership_es.rst:221 msgid "EL COLABORADOR también tiene la opción de comprar servicios de soporte o de formación suscribiéndose a un Success Pack de Odoo, por una tarifa adicional." msgstr "" -#: ../../content/legal/terms/i18n/partnership_es.rst:232 +#: ../../content/legal/terms/i18n/partnership_es.rst:225 msgid "4.5 Comisiones por los servicios de Odoo vendidos por EL COLABORADOR" msgstr "" -#: ../../content/legal/terms/i18n/partnership_es.rst:233 +#: ../../content/legal/terms/i18n/partnership_es.rst:227 msgid "Para los servicios ODOO comprados por un cliente a través de EL COLABORADOR, y siempre que el PARTNER mantenga una relación contractual con el cliente correspondiente, EL COLABORADOR ecibirá una comisión de acuerdo con la tabla de la sección :ref:`benefits_es` y su nivel de asociación en la fecha de la factura del cliente." msgstr "" -#: ../../content/legal/terms/i18n/partnership_es.rst:240 +#: ../../content/legal/terms/i18n/partnership_es.rst:234 msgid "5 Tarifas" msgstr "" -#: ../../content/legal/terms/i18n/partnership_es.rst:241 +#: ../../content/legal/terms/i18n/partnership_es.rst:236 msgid "EL COLABORADOR se compromete a pagar la tarifa de la colaboración al recibir la factura anual enviada por ODOO. La tarifa se especificará por escrito al momento de la firma de este contracto." msgstr "" -#: ../../content/legal/terms/i18n/partnership_es.rst:244 +#: ../../content/legal/terms/i18n/partnership_es.rst:239 msgid "EL COLABORADOR reconoce que la tarifa de colaboración mencionadas anteriormente no son reembolsables." msgstr "" -#: ../../content/legal/terms/i18n/partnership_es.rst:246 +#: ../../content/legal/terms/i18n/partnership_es.rst:241 msgid "Todos los honorarios y cargos son exclusivos de todos los impuestos, tarifas o cargos gubernamentales, federales, provinciales, estatales, locales u otros aplicables (en conjunto, \"Impuestos\"). EL COLABORADOR es responsable de pagar todos los Impuestos asociados a las compras realizadas por EL COLABORADOR bajo este Contrato, excepto cuando ODOO esté legalmente obligado a pagar o recaudar Impuestos de los cuales EL COLABORADOR es responsable." msgstr "" -#: ../../content/legal/terms/i18n/partnership_es.rst:253 +#: ../../content/legal/terms/i18n/partnership_es.rst:248 msgid "6 Resolución" msgstr "" -#: ../../content/legal/terms/i18n/partnership_es.rst:254 +#: ../../content/legal/terms/i18n/partnership_es.rst:250 msgid "En el caso de que cualquiera de las Partes no cumpla con cualquiera de sus obligaciones que se derivan de este documento, y si tal incumplimiento no se ha rectificado en un período de 30 días naturales a partir de la notificación por escrito de dicho incumplimiento, la Parte que no incumplió sus obligaciones puede rescindir este contrato inmediatamente." msgstr "" -#: ../../content/legal/terms/i18n/partnership_es.rst:261 +#: ../../content/legal/terms/i18n/partnership_es.rst:257 msgid "Disposiciones subsistentes:" msgstr "" -#: ../../content/legal/terms/i18n/partnership_es.rst:260 +#: ../../content/legal/terms/i18n/partnership_es.rst:256 msgid "Las secciones « :ref:`restrictions_es` », « :ref:`p_liability_es` », y « :ref:`gov_law_es` » mantendrán su vigencia tras cualquier resolución o expiración de este contrato." msgstr "" -#: ../../content/legal/terms/i18n/partnership_es.rst:264 +#: ../../content/legal/terms/i18n/partnership_es.rst:260 msgid "6.1 Consecuencia de la resolución" msgstr "" -#: ../../content/legal/terms/i18n/partnership_es.rst:269 +#: ../../content/legal/terms/i18n/partnership_es.rst:266 msgid "En el momento de la resolución de este contrato, EL COLABORADOR:" msgstr "" -#: ../../content/legal/terms/i18n/partnership_es.rst:266 +#: ../../content/legal/terms/i18n/partnership_es.rst:263 msgid "no deberá utilizar más los materiales y/o la marca Odoo ni reclamar la existencia de ninguna colaboración o relación con ODOO;" msgstr "" -#: ../../content/legal/terms/i18n/partnership_es.rst:268 +#: ../../content/legal/terms/i18n/partnership_es.rst:265 msgid "deberá cumplir con sus obligaciones durante cualquier período de aviso previo a dicha resolución;" msgstr "" -#: ../../content/legal/terms/i18n/partnership_es.rst:269 +#: ../../content/legal/terms/i18n/partnership_es.rst:266 msgid "ya no podrá usar Odoo Enterprise para fines de desarrollo, prueba o producción" msgstr "" -#: ../../content/legal/terms/i18n/partnership_es.rst:274 +#: ../../content/legal/terms/i18n/partnership_es.rst:271 msgid "7 Responsabilidad e indemnizaciones" msgstr "" -#: ../../content/legal/terms/i18n/partnership_es.rst:275 +#: ../../content/legal/terms/i18n/partnership_es.rst:273 msgid "Ambas Partes están vinculadas por una obligación de medios aquí descrita." msgstr "" -#: ../../content/legal/terms/i18n/partnership_es.rst:277 +#: ../../content/legal/terms/i18n/partnership_es.rst:275 msgid "En la medida máxima permitida por la ley, la responsabilidad de cada Parte por cualquier reclamo, pérdida, daño o gasto derivado de cualquier manera o bajo cualquier circunstancia del presente contrato se limitará a los daños directos demostrados, pero en ningún caso excederá por todos los eventos o series de eventos relacionados que ocasionen daños la cantidad total de las tarifas pagadas por EL COLABORADOR en el transcurso de los seis (6) meses inmediatamente anteriores a la fecha del evento que dio lugar a dicha reclamación." msgstr "" -#: ../../content/legal/terms/i18n/partnership_es.rst:284 +#: ../../content/legal/terms/i18n/partnership_es.rst:282 msgid "En ningún caso cada Parte será responsable de ningún daño indirecto o consecuente, incluyendo, entre otros, pero no limitándose a, reclamaciones de clientes o terceros, pérdidas de ingresos, ganancias, ahorros, pérdidas de negocios y otras pérdidas financieras, costos de paralización y retraso, datos perdidos o dañados derivados o relacionados con el cumplimiento de sus obligaciones en virtud de este Contrato." msgstr "" -#: ../../content/legal/terms/i18n/partnership_es.rst:290 +#: ../../content/legal/terms/i18n/partnership_es.rst:288 msgid "EL COLABORADOR reconoce que no tiene ninguna expectativa y que no ha recibido garantías de recuperar ninguna inversión realizada en la ejecución de este contrato y el programa de socios de Odoo o de obtener ninguna cantidad anticipada de ganancias en virtud de este contrato." msgstr "" -#: ../../content/legal/terms/i18n/partnership_es.rst:296 +#: ../../content/legal/terms/i18n/partnership_es.rst:294 msgid "8 Imagen de marca" msgstr "" -#: ../../content/legal/terms/i18n/partnership_es.rst:297 +#: ../../content/legal/terms/i18n/partnership_es.rst:296 msgid "La marca \"Odoo\" (incluida la palabra y sus representaciones visuales y logotipos) es exclusiva propiedad de ODOO." msgstr "" -#: ../../content/legal/terms/i18n/partnership_es.rst:300 +#: ../../content/legal/terms/i18n/partnership_es.rst:299 msgid "ODOO autoriza a PARTNER a usar la marca \"Odoo\" para promocionar sus productos y servicios, solo por la Duración del Contrato, siempre que:" msgstr "" -#: ../../content/legal/terms/i18n/partnership_es.rst:303 +#: ../../content/legal/terms/i18n/partnership_es.rst:302 msgid "no hay confusión posible de que el servicio sea proporcionado por PARTNER, no por ODOO;" msgstr "" -#: ../../content/legal/terms/i18n/partnership_es.rst:304 +#: ../../content/legal/terms/i18n/partnership_es.rst:303 msgid "PARTNER no use la palabra \"Odoo\" en el nombre de su compañía, nombre de producto, nombre de dominio y no registrar ninguna marca que la incluya." msgstr "" -#: ../../content/legal/terms/i18n/partnership_es.rst:307 +#: ../../content/legal/terms/i18n/partnership_es.rst:306 msgid "Ambas Partes se abstendrán de dañar de ninguna manera la imagen de marca y la reputación de la otra Parte en el cumplimiento de este contrato." msgstr "" -#: ../../content/legal/terms/i18n/partnership_es.rst:310 +#: ../../content/legal/terms/i18n/partnership_es.rst:309 msgid "El incumplimiento de las disposiciones de esta sección será causa de resolución de este Contrato." msgstr "" -#: ../../content/legal/terms/i18n/partnership_es.rst:314 +#: ../../content/legal/terms/i18n/partnership_es.rst:313 msgid "8.1 Publicidad" msgstr "" @@ -4423,44 +4420,44 @@ msgstr "" msgid "8.2 No captación o contratación" msgstr "" -#: ../../content/legal/terms/i18n/partnership_es.rst:324 +#: ../../content/legal/terms/i18n/partnership_es.rst:325 msgid "Excepto cuando la otra Parte dé su consentimiento por escrito, cada Parte, sus afiliados y representantes acuerdan no captar u ofrecer empleo a ningún empleado de la otra Parte que participe en la realización o uso de los servicios de este contrato, durante la duración de este contrato y por un período de 24 meses a partir de la fecha de resolución o expiración de este contrato. En caso de cualquier incumplimiento de las condiciones de esta sección que conduzca al despido de dicho empleado con este objetivo, la Parte incumplidora se compromete a pagar a la otra parte la cantidad de 30 000,00 EUR (€) (treinta mil euros)." msgstr "" -#: ../../content/legal/terms/i18n/partnership_es.rst:335 +#: ../../content/legal/terms/i18n/partnership_es.rst:336 msgid "8.3 Contratistas independientes" msgstr "" -#: ../../content/legal/terms/i18n/partnership_es.rst:336 +#: ../../content/legal/terms/i18n/partnership_es.rst:338 msgid "Las Partes son contratistas independientes, y este contrato no debe interpretarse como la configuración de cualquier Parte como socia, empresa conjunta o fiduciaria de la otra, como la creación de otra forma de asociación legal que exigiría responsabilidad a una Parte por la acción o la falta de acción de la otra, o como la prestación a cada Parte del derecho, poder o autoridad (expresa o implícita) para crear cualquier deber u obligación de la otra." msgstr "" -#: ../../content/legal/terms/i18n/partnership_es.rst:346 +#: ../../content/legal/terms/i18n/partnership_es.rst:348 msgid "9 Ley y jurisdicción aplicables" msgstr "" -#: ../../content/legal/terms/i18n/partnership_es.rst:347 +#: ../../content/legal/terms/i18n/partnership_es.rst:350 msgid "Este contrato se rige y se interpreta de acuerdo con las leyes de Bélgica. Todas las disputas que surjan en relación con este contrato para las que no se pueda encontrar una solución amistosa serán resueltas definitivamente en los Tribunales de Bélgica en Nivelles." msgstr "" #: ../../content/legal/terms/i18n/partnership_es.rst:-1 -#: ../../content/legal/terms/i18n/partnership_es.rst:367 +#: ../../content/legal/terms/i18n/partnership_es.rst:370 msgid "Firmas" msgstr "" -#: ../../content/legal/terms/i18n/partnership_es.rst:369 +#: ../../content/legal/terms/i18n/partnership_es.rst:372 msgid "Por ODOO," msgstr "" -#: ../../content/legal/terms/i18n/partnership_es.rst:369 +#: ../../content/legal/terms/i18n/partnership_es.rst:372 msgid "Por EL COLABORADOR" msgstr "" -#: ../../content/legal/terms/i18n/partnership_es.rst:377 +#: ../../content/legal/terms/i18n/partnership_es.rst:380 msgid "|vnegspace| |hspace| Por ODOO, |hspace| Por EL COLABORADOR, |vspace|" msgstr "" -#: ../../content/legal/terms/i18n/partnership_es.rst:385 +#: ../../content/legal/terms/i18n/partnership_es.rst:388 msgid "10 Anexo A: Licencia Odoo Enterprise Edition" msgstr "" diff --git a/locale/sources/marketing.pot b/locale/sources/marketing.pot index 6da990456..db86dafce 100644 --- a/locale/sources/marketing.pot +++ b/locale/sources/marketing.pot @@ -8,7 +8,7 @@ msgid "" msgstr "" "Project-Id-Version: Odoo saas-16.1\n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2023-10-27 12:38+0000\n" +"POT-Creation-Date: 2024-01-19 10:30+0000\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME \n" "Language-Team: LANGUAGE \n" @@ -116,7 +116,7 @@ msgid "In the upper-right corner of the main :guilabel:`Email Marketing` dashboa msgstr "" #: ../../content/applications/marketing/email_marketing.rst:74 -#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:237 +#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:420 msgid "List view" msgstr "" @@ -1382,91 +1382,181 @@ msgid "Advanced" msgstr "" #: ../../content/applications/marketing/marketing_automation/advanced/understanding_metrics.rst:3 -msgid "Understanding metrics" +msgid "Campaign metrics" msgstr "" #: ../../content/applications/marketing/marketing_automation/advanced/understanding_metrics.rst:5 -msgid "Metrics are detailed statistics that measure the progress and success of marketing campaigns. When creating marketing activities in a workflow, Odoo visually displays various metrics related to the campaign with detailed graphs and in-depth data." +msgid "*Campaign metrics* are detailed statistics and analytics within a marketing campaign, measuring its success and effectiveness. Triggered marketing activities populate relevant activity blocks with real-time metrics, in the campaign detail form." msgstr "" #: ../../content/applications/marketing/marketing_automation/advanced/understanding_metrics.rst:10 -msgid "A typical line graph in a marketing automation workflow showcasing the success rate of an email." +msgid "Activity analytics" msgstr "" -#: ../../content/applications/marketing/marketing_automation/advanced/understanding_metrics.rst:0 -msgid "An example of a marketing automation campaign in Odoo." -msgstr "" - -#: ../../content/applications/marketing/marketing_automation/advanced/understanding_metrics.rst:16 -msgid "In this case, the :guilabel:`Target` of this campaign is set to :guilabel:`Lead/Opportunity`, and was narrowed down to *only* focus on the leads (or opportunities) whose :guilabel:`Tag Name` contains a value of `product` — and *also* have an email address set up in the database." -msgstr "" - -#: ../../content/applications/marketing/marketing_automation/advanced/understanding_metrics.rst:20 -msgid "Beneath the filter nodes, Odoo displays how many records in the database fall into the previously-specified criteria filter." -msgstr "" - -#: ../../content/applications/marketing/marketing_automation/advanced/understanding_metrics.rst:24 -msgid "Below, there are 18 records in the database that match the criteria." -msgstr "" - -#: ../../content/applications/marketing/marketing_automation/advanced/understanding_metrics.rst:0 -msgid "Lead generation filters used to refine records on automation campaigns in Odoo." -msgstr "" - -#: ../../content/applications/marketing/marketing_automation/advanced/understanding_metrics.rst:30 -msgid "At the top of the marketing automation campaign form, there are a series of smart buttons. The :guilabel:`Participations` smart button in this example indicates that, out of those 18 records, 25 have become participants. In other words, they have matched the criteria, and have already interacted with the campaign in one way or another." -msgstr "" - -#: ../../content/applications/marketing/marketing_automation/advanced/understanding_metrics.rst:36 -msgid ":guilabel:`Records` represent a real-time number. Therefore, while the workflow is running, changes in opportunity records (deletions, additions, or adjustments) may occur." -msgstr "" - -#: ../../content/applications/marketing/marketing_automation/advanced/understanding_metrics.rst:39 -msgid "This means there will be real-time updates to the number of :guilabel:`Records`, but such updates do *not* change the number of :guilabel:`Participants`, as the metric *will not* exclude opportunities that have already been set as :guilabel:`Participants` before — Odoo just adds new ones." -msgstr "" - -#: ../../content/applications/marketing/marketing_automation/advanced/understanding_metrics.rst:44 -msgid "That's why the number of :guilabel:`Records` can be different from the number of :guilabel:`Participants` from time to time." +#: ../../content/applications/marketing/marketing_automation/advanced/understanding_metrics.rst:12 +msgid "In the :guilabel:`Workflow` section of a campaign detail form in the *Marketing Automation* app, where the various campaign activities are located, a collection of useful data can be found on every individual activity block, like number of communications :guilabel:`Sent`, percentage of messages that have been :guilabel:`Clicked`, and more." msgstr "" #: ../../content/applications/marketing/marketing_automation/advanced/understanding_metrics.rst:-1 -msgid "Difference between real-time record count and total participants on a marketing campaign." +msgid "An activity block in the workflow section with useful analytical data in Odoo." +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/advanced/understanding_metrics.rst:21 +msgid "To the left of the activity block, the configured :doc:`trigger time <../getting_started/workflow_activities>` is displayed as a duration (either :guilabel:`Hours`, :guilabel:`Days`, :guilabel:`Weeks`, or :guilabel:`Months`) if it corresponds to period after the workflow begins." +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/advanced/understanding_metrics.rst:27 +msgid "If the trigger time is dependent on another activity or triggering action (e.g. :guilabel:`Mail: Replied`, etc.) the time is displayed, along with the necessary action for that activity to be activated (e.g. `Replied after 2 Hours`)." +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/advanced/understanding_metrics.rst:0 +msgid "Time trigger display when dependent on another activity in Odoo Marketing Automation." +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/advanced/understanding_metrics.rst:35 +msgid "In the activity block, an icon represents each activity type. An :guilabel:`✉️ (envelope)` icon means the activity is an email. Three tiny, interlocking :guilabel:`⚙️ (gear)` icons means the activity is an internal action. And, a small, basic :guilabel:`📱 (mobile)` icon means the activity is an SMS." +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/advanced/understanding_metrics.rst:41 +msgid "The activity type name is also displayed in smaller font below the activity title." +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/advanced/understanding_metrics.rst:43 +msgid "Beside the activity icon, at the top of the activity block, is the title of the activity. To the right of the activity title, there are :guilabel:`Edit` and :guilabel:`Delete` buttons." +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/advanced/understanding_metrics.rst:46 +msgid "Click :guilabel:`Edit` to open the :guilabel:`Open: Activities` pop-up form for that specific activity, in which that activity can be modified. Click the :guilabel:`Delete` button to completely delete that specific activity from the workflow." msgstr "" #: ../../content/applications/marketing/marketing_automation/advanced/understanding_metrics.rst:51 -msgid "Whenever the system runs, updating numbers and triggering actions, it will look at the :guilabel:`Target` model, and check if new :guilabel:`Records` have been added (or modified), which always keeps the flow up-to-date." +msgid ":doc:`/applications/marketing/marketing_automation/getting_started/workflow_activities`" +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/advanced/understanding_metrics.rst:54 +msgid "Activity graph tab" msgstr "" #: ../../content/applications/marketing/marketing_automation/advanced/understanding_metrics.rst:56 -msgid "The :guilabel:`Filter` here is applied to *all* activities. Leads that lose that specific tag (`product`) in the meantime will be excluded from later activities." +msgid "In every activity block, the :guilabel:`Graph (pie chart icon)` tab is open by default, displaying related metrics as a simple line graph. The success metrics are represented in `green` and the rejected metrics are represented in `red`." msgstr "" #: ../../content/applications/marketing/marketing_automation/advanced/understanding_metrics.rst:60 -msgid "Filters can also be applied to individual activities, in the :guilabel:`Domain` section of the :guilabel:`Activity` pop-up form. Use this feature to specify an individual filter that will *only* be performed if the records satisfy *both* filter criteria — the activity filter and its specific domain filter." +msgid "Numerical representations of both :guilabel:`Success` and :guilabel:`Rejected` activities are shown to the right of the line graph." msgstr "" -#: ../../content/applications/marketing/marketing_automation/advanced/understanding_metrics.rst:66 -msgid "When configuring an SMS activity, make sure a certain phone number is set, in order to avoid triggering a SMS that would never be sent." +#: ../../content/applications/marketing/marketing_automation/advanced/understanding_metrics.rst:64 +msgid "Hovering over any point in the line graph of the activity block reveals a notated breakdown of data for that specific date." msgstr "" #: ../../content/applications/marketing/marketing_automation/advanced/understanding_metrics.rst:0 -msgid "A relevant targeting filter that applies to a type of individual activity." +msgid "Hovering over any point in line graph reveals notated breakdown of data in Odoo." msgstr "" -#: ../../content/applications/marketing/marketing_automation/advanced/understanding_metrics.rst:73 -msgid ":guilabel:`Success` represents the number of times that the searching for participants — who match the criteria filter(s) of that activity — was performed successfully, in relation to the total number of participants. If a participant does *not* match the conditions, it will be added to the :guilabel:`Rejected` number." +#: ../../content/applications/marketing/marketing_automation/advanced/understanding_metrics.rst:71 +msgid "Beneath the graph in the activity block, for *Email* or *SMS* activity types, a line of accessible data figures provide a bird's eye view of the campaign activity, including: :guilabel:`Sent` (numerical), :guilabel:`Clicked` (percentage), :guilabel:`Replied` (percentage), and :guilabel:`Bounced` (percentage)." +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/advanced/understanding_metrics.rst:77 +msgid "Clicking any of those stats on the :guilabel:`DETAILS` line, beneath the line graph, reveals a separate page containing every specific record for that particular data point." +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/advanced/understanding_metrics.rst:81 +msgid "Activity filter tab" +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/advanced/understanding_metrics.rst:83 +msgid "Next to the :guilabel:`Graph` tab on the activity block, there's the option to open a :guilabel:`Filter` tab (represented by a :guilabel:`filter/funnel` icon)." msgstr "" #: ../../content/applications/marketing/marketing_automation/advanced/understanding_metrics.rst:-1 -msgid "Overview showing participants who do or do not match filtering criteria on an activity." +msgid "What a campaign activity filter tab looks like in Odoo Marketing Automation." msgstr "" -#: ../../content/applications/marketing/marketing_automation/advanced/understanding_metrics.rst:82 -msgid "Hovering over the graph on an automation activity block, Odoo displays the number of successful and rejected participants, per day, over the last 15 days." +#: ../../content/applications/marketing/marketing_automation/advanced/understanding_metrics.rst:90 +msgid "Clicking the :guilabel:`Filter` tab on an activity block, reveals what the specific filters are for that particular campaign activity, and how many records in the database match that specific criteria." msgstr "" -#: ../../content/applications/marketing/marketing_automation/advanced/understanding_metrics.rst:86 -msgid "Whenever a new record is added to the :guilabel:`Target` model, it's automatically added to the workflow, and it will start the workflow from the beginning (:guilabel:`Parent Action`)." +#: ../../content/applications/marketing/marketing_automation/advanced/understanding_metrics.rst:95 +msgid "Clicking the :guilabel:`records` link beneath the displayed filter reveals a separate pop-up window containing a list of all the records that match that specific campaign activity rule(s)." +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/advanced/understanding_metrics.rst:99 +msgid "Link tracker" +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/advanced/understanding_metrics.rst:101 +msgid "Odoo tracks all URLs used in marketing campaigns. To access and analyze those URLs, navigate to :menuselection:`Marketing Automation app --> Reporting --> Link Tracker`. Doing so reveals a :guilabel:`Link Statistics` page, wherein all campaign-related URLs can be analyzed." +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/advanced/understanding_metrics.rst:109 +msgid "The default view on the :guilabel:`Link Statistics` page is the :guilabel:`Bar Chart` view, but there are different view options available in the upper-left corner. There is the option to view the statistics as a :guilabel:`Line Chart` or :guilabel:`Pie Chart`." +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/advanced/understanding_metrics.rst:113 +msgid "Beside that, there is also the option to view the statistics as :guilabel:`Stacked`, and the data can be put into :guilabel:`Descending` or :guilabel:`Ascending` order." +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/advanced/understanding_metrics.rst:116 +msgid "To the far-left of the view options, there is the :guilabel:`Measures` drop-down menu. When clicked, the options to view the :guilabel:`Number of Clicks` or total :guilabel:`Count` are available. And, to the right of the :guilabel:`Measures` drop-down menu, there's the ability to add any data to a spreadsheet by clicking the :guilabel:`Insert in Spreadsheet` button." +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/advanced/understanding_metrics.rst:121 +#: ../../content/applications/marketing/marketing_automation/advanced/understanding_metrics.rst:153 +#: ../../content/applications/marketing/marketing_automation/advanced/understanding_metrics.rst:180 +msgid "Also, in the upper-right corner of the :guilabel:`Link Statistics` page, to the far-right of the search bar, there are additional view options to choose from: the default :guilabel:`Graph` view, the :guilabel:`Pivot` table view, and the :guilabel:`List` view." +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/advanced/understanding_metrics.rst:126 +msgid "Traces" +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/advanced/understanding_metrics.rst:128 +msgid "Odoo tracks all activities used in every marketing campaign. The data related to these activities can be accessed and analyzed in the :guilabel:`Traces` page, which can be found by navigating to :menuselection:`Marketing Automation app --> Reporting --> Traces`." +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/advanced/understanding_metrics.rst:-1 +msgid "The Traces page in the Odoo Marketing Automation application." +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/advanced/understanding_metrics.rst:136 +msgid "The default view on the :guilabel:`Traces` page is the :guilabel:`Bar Chart` view, but there are different view options available in the upper-left corner. There is the option to view the statistics as a :guilabel:`Line Chart` or :guilabel:`Pie Chart`." +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/advanced/understanding_metrics.rst:140 +msgid "At the top of the graph, there's a color key, informing the user which activities have been :guilabel:`Processed`, :guilabel:`Scheduled`, and :guilabel:`Rejected`. There's also an outline indicator to inform users of the :guilabel:`Sum` of certain activities, as well." +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/advanced/understanding_metrics.rst:144 +msgid "Beside the various view option in the upper-left corner of the :guilabel:`Traces` page, there is also the option to view the statistics as :guilabel:`Stacked`, and the data can be put into :guilabel:`Descending` or :guilabel:`Ascending` order." +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/advanced/understanding_metrics.rst:148 +msgid "To the far-left of the view options, there is the :guilabel:`Measures` drop-down menu. When clicked, the options to view the :guilabel:`Document ID` or total :guilabel:`Count` are available. And, to the right of the :guilabel:`Measures` drop-down menu, there's the ability to add any data to a spreadsheet by clicking the :guilabel:`Insert in Spreadsheet` button." +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/advanced/understanding_metrics.rst:158 +msgid "Participants" +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/advanced/understanding_metrics.rst:160 +msgid "Odoo tracks all participants related to every marketing campaign. The data related to these participants can be accessed and analyzed in the :guilabel:`Participants` page, which can be found by navigating to :menuselection:`Marketing Automation app --> Reporting --> Participants`." +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/advanced/understanding_metrics.rst:-1 +msgid "The Participants page in the Odoo Marketing Automation application." +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/advanced/understanding_metrics.rst:168 +msgid "The default view on the :guilabel:`Participants` page is the :guilabel:`Pie Chart` view, but there are different view options available in the upper-left corner. There is the option to view the statistics as a :guilabel:`Line Chart` or :guilabel:`Bar Chart`." +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/advanced/understanding_metrics.rst:172 +msgid "At the top of the graph, there's a color key that describes the type of participants found in the graph." +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/advanced/understanding_metrics.rst:175 +msgid "To the far-left of the view options, there is the :guilabel:`Measures` drop-down menu. When clicked, the options to view the :guilabel:`Record ID` or total :guilabel:`Count` are available. And, to the right of the :guilabel:`Measures` drop-down menu, there's the ability to add any data to a spreadsheet by clicking the :guilabel:`Insert in Spreadsheet` button." msgstr "" #: ../../content/applications/marketing/marketing_automation/getting_started.rst:5 @@ -1474,100 +1564,133 @@ msgid "Getting Started" msgstr "" #: ../../content/applications/marketing/marketing_automation/getting_started/first_campaign.rst:3 -#: ../../content/applications/marketing/surveys/create.rst:13 -msgid "Getting started" +msgid "Marketing automation campaigns" msgstr "" #: ../../content/applications/marketing/marketing_automation/getting_started/first_campaign.rst:5 -msgid "The Odoo *Marketing Automation* app automates a variety of marketing tasks, by combining specific rules and filters to generate timed actions. Instead of manually having to build each stage of a campaign (such as a series of timed massmails), the *Marketing Automation* app allows marketers to build the entire campaign, and all of its stages, in one place on a single dashboard." +msgid "The Odoo *Marketing Automation* app automates a variety of marketing tasks by combining specific rules and filters to generate timed actions. Instead of manually having to build each stage of a campaign (like a series of timed massmails), the *Marketing Automation* app allows marketers to build the entire campaign, and all of its stages, in one place---on one dashboard." msgstr "" #: ../../content/applications/marketing/marketing_automation/getting_started/first_campaign.rst:11 -msgid "Create a campaign" +msgid "Campaign configuration" msgstr "" #: ../../content/applications/marketing/marketing_automation/getting_started/first_campaign.rst:13 -msgid "To create a new automated marketing campaign, open the :menuselection:`Marketing Automation` app, and click the :guilabel:`Create` button in the upper-left corner. Doing so reveals a blank marketing automation campaign detail form on a separate page." -msgstr "" - -#: ../../content/applications/marketing/marketing_automation/getting_started/first_campaign.rst:17 -msgid "On the blank marketing automation campaign page, the following smart buttons and fields are available:" +msgid "To create a new automated marketing campaign, navigate to :menuselection:`Marketing Automation app --> New` to reveal a blank campaign form." msgstr "" #: ../../content/applications/marketing/marketing_automation/getting_started/first_campaign.rst:-1 -msgid "A dashboard showing the creation of a new marketing automation campaign in Odoo." +msgid "A blank marketing automation campaign form in Odoo Marketing Automation application." msgstr "" -#: ../../content/applications/marketing/marketing_automation/getting_started/first_campaign.rst:24 -msgid "**Smart buttons**" +#: ../../content/applications/marketing/marketing_automation/getting_started/first_campaign.rst:20 +msgid "After entering a name for the marketing campaign, configure the target audience in the remaining fields." +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/getting_started/first_campaign.rst:23 +msgid "A target audience can be configured by entering specific criteria for Odoo to use when determining to whom this marketing automation campaign should be sent." msgstr "" #: ../../content/applications/marketing/marketing_automation/getting_started/first_campaign.rst:26 -msgid ":guilabel:`Templates`: represents the number of pre-configured mail templates being used in this particular campaign. (Templates can always be created on-the-fly, as well)." +msgid "In the :guilabel:`Target` field, use the drop-down menu to choose which model the target audience filters should be based on (e.g. :guilabel:`Contact`, :guilabel:`Lead/Opportunity`, :guilabel:`Sales Order`, etc.)." msgstr "" -#: ../../content/applications/marketing/marketing_automation/getting_started/first_campaign.rst:28 -msgid ":guilabel:`SMS`: represents the number of personalized SMS messages connected to this campaign." +#: ../../content/applications/marketing/marketing_automation/getting_started/first_campaign.rst:30 +msgid "Select :guilabel:`Search More...` from the drop-down menu to reveal a :guilabel:`Search: Target` pop-up window containing all of the available targeting options." msgstr "" -#: ../../content/applications/marketing/marketing_automation/getting_started/first_campaign.rst:29 -msgid ":guilabel:`Clicks`: represents the number of times attached links have been clicked by recipients of this campaign." -msgstr "" - -#: ../../content/applications/marketing/marketing_automation/getting_started/first_campaign.rst:31 -msgid ":guilabel:`Participants`: represents the number of contacts that have directly participated in this campaign." -msgstr "" - -#: ../../content/applications/marketing/marketing_automation/getting_started/first_campaign.rst:34 -msgid "**Fields**" -msgstr "" - -#: ../../content/applications/marketing/marketing_automation/getting_started/first_campaign.rst:36 -msgid ":guilabel:`Name`: represents the name of the marketing automation campaign being created." +#: ../../content/applications/marketing/marketing_automation/getting_started/first_campaign.rst:33 +msgid "Once a :guilabel:`Target` is selected, there's a :guilabel:`Unicity based on` field. This field is used to avoid duplicates based on the model chosen in the :guilabel:`Target` field." msgstr "" #: ../../content/applications/marketing/marketing_automation/getting_started/first_campaign.rst:37 -msgid ":guilabel:`Target`: this field is a drop-down menu to choose which model is targeted by this campaign (i.e., by Contacts, Sales Order, Lead/Opportunity, etc.)." +msgid "If :guilabel:`Customers` is chosen as the :guilabel:`Target`, select :guilabel:`Email` in the :guilabel:`Unicity based on` field so Odoo only processes one record for each customer email address." msgstr "" -#: ../../content/applications/marketing/marketing_automation/getting_started/first_campaign.rst:39 -msgid ":guilabel:`Filter`: this field provides numerous configurable criteria that can be used to further narrow down the target recipients/audience for the marketing automation campaign." +#: ../../content/applications/marketing/marketing_automation/getting_started/first_campaign.rst:41 +msgid "Select :guilabel:`Search More...` from the :guilabel:`Unicity based on` drop-down menu to reveal all available options in a pop-up window." msgstr "" -#: ../../content/applications/marketing/marketing_automation/getting_started/first_campaign.rst:43 -msgid "Campaign filters" +#: ../../content/applications/marketing/marketing_automation/getting_started/first_campaign.rst:44 +msgid "Last on the campaign form is the :guilabel:`Filter` field. This is where more specific targeting options can be layered into the campaign to further narrow the number and type of recipients that receive the marketing automation material." msgstr "" -#: ../../content/applications/marketing/marketing_automation/getting_started/first_campaign.rst:45 -msgid "To add a :guilabel:`Filter` to the target audience, click :guilabel:`Add Filter`, and a node field appears. In the node field, a custom equation can be configured for Odoo to use when filtering who to include (and exclude) in this specific marketing campaign." -msgstr "" - -#: ../../content/applications/marketing/marketing_automation/getting_started/first_campaign.rst:-1 -msgid "A filter node in Odoo Marketing Automation." +#: ../../content/applications/marketing/marketing_automation/getting_started/first_campaign.rst:48 +msgid "If left alone, the :guilabel:`Filter` field reads: :guilabel:`Match all records`. That means Odoo uses the :guilabel:`Target` and :guilabel:`Unicity based on` fields to determine who the recipients will be. The number of recipients is represented beneath as :guilabel:`record(s)`." msgstr "" #: ../../content/applications/marketing/marketing_automation/getting_started/first_campaign.rst:53 -msgid "When the first field of the node is clicked, a nested drop-down menu of options appears on the screen, wherein specific criteria is chosen based on needs of the campaign. The remaining fields on the node further define the criteria determining which records to include (or exclude) in the execution of the campaign." +msgid "Campaign filter rules" msgstr "" -#: ../../content/applications/marketing/marketing_automation/getting_started/first_campaign.rst:58 -msgid "To add another node, click the :guilabel:`➕ (plus sign)` icon to the right of the filtering rule. To add a branch of multiple nodes at the same time, click the :guilabel:`⋯ (ellipses)` icon." +#: ../../content/applications/marketing/marketing_automation/getting_started/first_campaign.rst:55 +msgid "To add a more specific filter to a marketing automation campaign, click the :guilabel:`Add condition` button in the :guilabel:`Filter` field. Doing so reveals a series of other configurable filter rule fields." msgstr "" -#: ../../content/applications/marketing/marketing_automation/getting_started/first_campaign.rst:61 -msgid "For further information on filters, refer to :doc:`this documentation page `." +#: ../../content/applications/marketing/marketing_automation/getting_started/first_campaign.rst:59 +msgid "In the rule fields, customizable equations can be configured for Odoo to use when filtering who to include or exclude in this specific marketing campaign." msgstr "" -#: ../../content/applications/marketing/marketing_automation/getting_started/first_campaign.rst:65 -msgid ":guilabel:`Records` represent the number of contacts in the system that fit the specified criteria for a campaign." +#: ../../content/applications/marketing/marketing_automation/getting_started/first_campaign.rst:-1 +msgid "How the filter rule equation fields look in Odoo Marketing Automation campaigns." msgstr "" -#: ../../content/applications/marketing/marketing_automation/getting_started/first_campaign.rst:69 -msgid ":doc:`/applications/marketing/marketing_automation/getting_started/testing_running`" +#: ../../content/applications/marketing/marketing_automation/getting_started/first_campaign.rst:67 +msgid ":guilabel:`Records` refer to contacts in the system that fit the specified criteria for a campaign." msgstr "" #: ../../content/applications/marketing/marketing_automation/getting_started/first_campaign.rst:70 -msgid ":doc:`/applications/marketing/marketing_automation/getting_started/workflow_activities`" +msgid "Also, once :guilabel:`Add condition` is clicked, the ability to :guilabel:`Save as Favorite Filter` becomes available on the campaign form." +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/getting_started/first_campaign.rst:73 +msgid "There is also the option to match records with :guilabel:`all` or :guilabel:`any` of the rules configured in the :guilabel:`Filter` field." +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/getting_started/first_campaign.rst:76 +msgid "To choose either of those options, click :guilabel:`all` from the middle of the sentence \":guilabel:`Match records with all of the following rules`\" to reveal a drop-down menu with those options." +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/getting_started/first_campaign.rst:-1 +msgid "Match records with all or any of the rules in Filter field for marketing campaigns." +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/getting_started/first_campaign.rst:84 +msgid "When the first field of the rule equation is clicked, a nested drop-down menu of options appears on the screen where specific criteria is chosen based on needs of the campaign." +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/getting_started/first_campaign.rst:87 +msgid "The remaining fields on the rule equation further define the criteria, which is used to determine which records in the database to include or exclude in the execution of the campaign." +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/getting_started/first_campaign.rst:90 +msgid "To add another rule, either click the :guilabel:`➕ (plus sign)` icon to the right of the filtering rule, or click :guilabel:`New Rule` beneath the rule equation fields. When either are clicked, a new series of rule fields appears." +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/getting_started/first_campaign.rst:94 +msgid "To add a branch of multiple rules at the same time, click the :guilabel:`branch` icon, located to the right of the :guilabel:`➕ (plus sign)` icon. When clicked, two additional sub-rule equation fields appear beneath the initial rule." +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/getting_started/first_campaign.rst:-1 +msgid "Sample of how the rule branches look in the filter section of a marketing campaign." +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/getting_started/first_campaign.rst:102 +msgid "There is also the option to have the filter apply to :guilabel:`any` or :guilabel:`all` of the configured branch rules." +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/getting_started/first_campaign.rst:105 +msgid "For further information on marketing automation campaign filter configuration, refer to :doc:`this documentation page `." +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/getting_started/first_campaign.rst:109 +#: ../../content/applications/marketing/marketing_automation/getting_started/testing_running.rst:153 +msgid ":doc:`workflow_activities`" +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/getting_started/first_campaign.rst:110 +#: ../../content/applications/marketing/marketing_automation/getting_started/workflow_activities.rst:266 +msgid ":doc:`testing_running`" msgstr "" #: ../../content/applications/marketing/marketing_automation/getting_started/target_audience.rst:3 @@ -1711,183 +1834,500 @@ msgid "Testing/running campaigns" msgstr "" #: ../../content/applications/marketing/marketing_automation/getting_started/testing_running.rst:5 -msgid "Odoo gives users the ability to test marketing campaigns (and mailings) before officially running them." +msgid "The Odoo *Marketing Automation* app allows users to test marketing campaigns (and mailings) before officially running them to check for errors and correct any mistakes before it reaches its target audience." msgstr "" -#: ../../content/applications/marketing/marketing_automation/getting_started/testing_running.rst:8 -msgid "First, open the :menuselection:`Marketing Automation` application, and select the desired campaign, which reveals that campaign's detail form." +#: ../../content/applications/marketing/marketing_automation/getting_started/testing_running.rst:10 +msgid "Test campaigns" msgstr "" -#: ../../content/applications/marketing/marketing_automation/getting_started/testing_running.rst:11 -msgid "On the campaign detail form, make sure the campaign already has activities configured (or build a campaign by following the directions here on :doc:`this documentation `)." +#: ../../content/applications/marketing/marketing_automation/getting_started/testing_running.rst:12 +msgid "To test a marketing campaign, open the :menuselection:`Marketing Automation app`, and select the desired campaign to test, which reveals the campaign's detail form." msgstr "" #: ../../content/applications/marketing/marketing_automation/getting_started/testing_running.rst:15 -msgid "To start a test, click the :guilabel:`Launch a Test` button at the top of the campaign form." +msgid "On the campaign detail form, make sure the campaign already has activities configured in the workflow (or build a campaign by following the directions on :doc:`this documentation `)." +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/getting_started/testing_running.rst:20 +msgid "Testing marketing automation campaigns is meant to be performed in the production version of the database. Duplicate (or trial) databases have limited email sending capabilities." +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/getting_started/testing_running.rst:23 +msgid "To start a test, click the :guilabel:`Launch a Test` button at the top of the campaign form, to the right of the :guilabel:`Start` button." msgstr "" #: ../../content/applications/marketing/marketing_automation/getting_started/testing_running.rst:-1 -msgid "Launch a test button in Odoo Marketing Automation." +msgid "Launch a test button on a campaign detail form in Odoo Marketing Automation." msgstr "" -#: ../../content/applications/marketing/marketing_automation/getting_started/testing_running.rst:21 -msgid "When clicked, a :guilabel:`Launch a test` pop-up window appears. In the drop-down field, choose an existing record (or create a new one) to run the test on. To create a brand new record, click the :guilabel:`Search More...` link at the bottom of the drop-down menu, and then click the :guilabel:`Create` button." +#: ../../content/applications/marketing/marketing_automation/getting_started/testing_running.rst:30 +msgid "When clicked, a :guilabel:`Launch a test` pop-up window appears." msgstr "" -#: ../../content/applications/marketing/marketing_automation/getting_started/testing_running.rst:26 -msgid "Doing so reveals a blank contact form, in which the :guilabel:`Name` and :guilabel:`Email` **must** be entered. When all the necessary information has been entered, click :guilabel:`Save`, and Odoo returns to the :guilabel:`Launch a test` pop-up, with that new record in the :guilabel:`Choose an existing record or create a new one to test` field." +#: ../../content/applications/marketing/marketing_automation/getting_started/testing_running.rst:-1 +msgid "Launch a test pop-up window that appears in Odoo Markting Automation." msgstr "" -#: ../../content/applications/marketing/marketing_automation/getting_started/testing_running.rst:31 -msgid "Once a record is selected, click :guilabel:`Continue`, and Odoo reveals the campaign test page." +#: ../../content/applications/marketing/marketing_automation/getting_started/testing_running.rst:36 +msgid "In the :guilabel:`Launch a test` pop-up window, click the :guilabel:`Pick or create a/an Contact to generate a Test Participant` field to reveal a drop-down menu of contacts. From this drop-down menu, select an existing contact (or create a new one) to run the test on." +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/getting_started/testing_running.rst:41 +msgid "Only one contact can be selected from the :guilabel:`Launch a test` pop-up window." +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/getting_started/testing_running.rst:43 +msgid "To create a new contact directly from the :guilabel:`Launch a test` pop-up window, start typing the name of the new contact in the blank field, and click :guilabel:`Create and edit...`." +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/getting_started/testing_running.rst:-1 +msgid "Typing in a new contact directly from the launch a test pop-up window in Odoo." +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/getting_started/testing_running.rst:50 +msgid "Doing so reveals a blank :guilabel:`Create Record` pop-up form, in which the necessary contact information (:guilabel:`Email`, :guilabel:`Mobile`, etc.) *must* be entered, in order for the test to work. When the necessary information is entered, click :guilabel:`Save & Close`." +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/getting_started/testing_running.rst:-1 +msgid "A blank contact form from a launch test pop-up window in Odoo Marketing Automation." +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/getting_started/testing_running.rst:58 +msgid "When all the necessary fields have been entered, click :guilabel:`Save & Close` to return to the :guilabel:`Launch a test` pop-up window." +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/getting_started/testing_running.rst:61 +msgid "Once a contact is selected, click :guilabel:`Launch` to reveal the campaign test page." msgstr "" #: ../../content/applications/marketing/marketing_automation/getting_started/testing_running.rst:-1 msgid "Test screen in Odoo Marketing Automation." msgstr "" -#: ../../content/applications/marketing/marketing_automation/getting_started/testing_running.rst:37 +#: ../../content/applications/marketing/marketing_automation/getting_started/testing_running.rst:67 msgid "On the campaign test page, the name of the :guilabel:`Record` being tested is visible, along with the precise time this test workflow was started in the :guilabel:`Workflow Started On` field. Beneath that, in the :guilabel:`Workflow` section is the first activity (or activities) in the workflow that's being tested." msgstr "" -#: ../../content/applications/marketing/marketing_automation/getting_started/testing_running.rst:42 +#: ../../content/applications/marketing/marketing_automation/getting_started/testing_running.rst:72 msgid "To start a test, click the :guilabel:`Run` button, represented by a :guilabel:`▶️ (play button)` icon beside the first activity in the workflow. When clicked, the page reloads, and Odoo shows the various results (and analytics) connected to that specific activity as they occur, in real-time." msgstr "" +#: ../../content/applications/marketing/marketing_automation/getting_started/testing_running.rst:77 +msgid "If a child activity is scheduled beneath a parent activity, that child activity will be revealed slightly indented in the workflow, once that parent activity has been run, via the :guilabel:`▶️ (play button)` icon." +msgstr "" + #: ../../content/applications/marketing/marketing_automation/getting_started/testing_running.rst:-1 msgid "Workflow test progress in Odoo Marketing Automation." msgstr "" -#: ../../content/applications/marketing/marketing_automation/getting_started/testing_running.rst:50 -msgid "Once all the workflow activities are completed, the test will end, and move to the :guilabel:`Completed` stage. To stop a test before all the workflow activities are completed, click the :guilabel:`Stop` button in the upper-left corner of the campaign test page." +#: ../../content/applications/marketing/marketing_automation/getting_started/testing_running.rst:85 +msgid "Once all the workflow activities are completed, the test ends, and the status bar (in the upper-right corner) moves to the :guilabel:`Completed` stage." +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/getting_started/testing_running.rst:88 +msgid "To stop a test before all the workflow activities are completed, click the :guilabel:`Stop` button in the upper-left corner of the campaign test page." +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/getting_started/testing_running.rst:92 +msgid "Run campaigns" +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/getting_started/testing_running.rst:94 +msgid "To run a campaign, navigate to :menuselection:`Marketing Automation app`, and select the desired campaign to run." +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/getting_started/testing_running.rst:97 +msgid "On the campaign detail form, with all the desired activities ready in the :guilabel:`Workflow` section, click :guilabel:`Start` in the upper-left corner to officially run the campaign to the configured target audience specified on the campaign detail form." +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/getting_started/testing_running.rst:101 +msgid "Clicking :guilabel:`Start` launches the campaign, and the status bar of the campaign switches to :guilabel:`Running`, which is located in the upper-right corner of the campaign detail form." +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/getting_started/testing_running.rst:-1 +msgid "The status of a marketing campaign changing to running in the upper-right corner." +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/getting_started/testing_running.rst:109 +msgid "If some participants are already running on a campaign, and was stopped for any reason, clicking the :guilabel:`Start` button again prompts a pop-up warning. This warning advises the user to click an :guilabel:`Update` button to apply any modifications made to the campaign." +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/getting_started/testing_running.rst:-1 +msgid "The workflow has been modified warning pop-up window of a marketing campaign form." +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/getting_started/testing_running.rst:117 +msgid "Be aware that participants that had already gone through an entire campaign in its original state **can** be reintroduced into the newly-modified campaign, and new traces could be created for them." +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/getting_started/testing_running.rst:121 +msgid "Then, as the mailings and actions are triggered in the :guilabel:`Workflow`, the various stats and data related to each activity appear in each activity block. There is also a series of stat-related smart buttons that appear at the top of the campaign detail form, as well." +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/getting_started/testing_running.rst:125 +msgid "These analytical smart buttons will *also* populate with real-time data as the campaign progresses: :guilabel:`Templates`, :guilabel:`Clicks`, :guilabel:`Tests`, :guilabel:`Participants`." +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/getting_started/testing_running.rst:-1 +msgid "The row of smart buttons that appear in a currently running marketing campaign in Odoo." +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/getting_started/testing_running.rst:133 +msgid "Stop campaigns" +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/getting_started/testing_running.rst:135 +msgid "To stop a campaign that's currently running, navigate to the :menuselection:`Marketing Automation app`, and select the desired campaign to stop. On the campaign detail form, click the :guilabel:`Stop` button in the upper-left corner." +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/getting_started/testing_running.rst:-1 +msgid "The stop button on a typical campaign detail form in Odoo Marketing Automation application." +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/getting_started/testing_running.rst:143 +msgid "When clicked, the campaign is officially stopped, and the status changes to :guilabel:`Stopped` in the upper-right corner of the campaign detail form." +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/getting_started/testing_running.rst:-1 +msgid "Marketing campaign's stopped status on a campaign detail form in Odoo Marketing Automation." +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/getting_started/testing_running.rst:151 +msgid ":doc:`first_campaign`" +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/getting_started/testing_running.rst:152 +#: ../../content/applications/marketing/marketing_automation/getting_started/workflow_activities.rst:188 +msgid ":doc:`target_audience`" msgstr "" #: ../../content/applications/marketing/marketing_automation/getting_started/workflow_activities.rst:3 -msgid "Marketing activities" +msgid "Campaign workflow activities" msgstr "" #: ../../content/applications/marketing/marketing_automation/getting_started/workflow_activities.rst:5 -msgid "When creating a campaign in the *Marketing Automation* app, users can plan marketing activities, such as email or SMS campaigns." +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." msgstr "" -#: ../../content/applications/marketing/marketing_automation/getting_started/workflow_activities.rst:8 -msgid "To get started, navigate to the bottom of a marketing automation campaign detail form, and click :guilabel:`Add New Activity`. 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/getting_started/workflow_activities.rst:10 +msgid "Add workflow activities" msgstr "" -#: ../../content/applications/marketing/marketing_automation/getting_started/workflow_activities.rst:13 -msgid "The following fields are available in the :guilabel:`Create Activities` pop-up window (when :guilabel:`Add New Activity` is clicked):" +#: ../../content/applications/marketing/marketing_automation/getting_started/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`." +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/getting_started/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." msgstr "" #: ../../content/applications/marketing/marketing_automation/getting_started/workflow_activities.rst:-1 -msgid "An activity template in Odoo Marketing Automation." -msgstr "" - -#: ../../content/applications/marketing/marketing_automation/getting_started/workflow_activities.rst:20 -msgid ":guilabel:`Activity Name`: the title of the activity." -msgstr "" - -#: ../../content/applications/marketing/marketing_automation/getting_started/workflow_activities.rst:21 -msgid ":guilabel:`Activity Type`: choose between `Email`, `Server Action` (internal Odoo operation), or `SMS`." +msgid "A workflow activity template pop-up window in Odoo Marketing Automation." msgstr "" #: ../../content/applications/marketing/marketing_automation/getting_started/workflow_activities.rst:23 -msgid ":guilabel:`Mail Template`: choose from pre-configured templates (or create a new one on-the-fly)." +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/getting_started/workflow_activities.rst:24 -msgid ":guilabel:`Trigger`: choose when this activity should be triggered." -msgstr "" - -#: ../../content/applications/marketing/marketing_automation/getting_started/workflow_activities.rst:25 -msgid ":guilabel:`Expiry Duration`: configure to stop the actions after a specific amount of time (after the scheduled date). When selected, a :guilabel:`Cancel after` field appears, in which the user can choose how many :guilabel:`Hours, Days, Weeks, or Months` they want the actions to cease after the initial date." -msgstr "" - -#: ../../content/applications/marketing/marketing_automation/getting_started/workflow_activities.rst:29 -msgid ":guilabel:`Activity Filter`: domain related to this activity (and all subsequent child activities)." +#: ../../content/applications/marketing/marketing_automation/getting_started/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/getting_started/workflow_activities.rst:31 -msgid ":guilabel:`Applied Filter`: activity will *only* be performed if it satisfies the specified domain (filter)." +msgid "Activity types" msgstr "" -#: ../../content/applications/marketing/marketing_automation/getting_started/workflow_activities.rst:34 -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/getting_started/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`." +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/getting_started/workflow_activities.rst:36 +msgid "The field below the :guilabel:`Activity Type` changes, depending on the chosen :guilabel:`Activity Type`." msgstr "" #: ../../content/applications/marketing/marketing_automation/getting_started/workflow_activities.rst:40 -msgid "Workflow activity" +msgid "Email activity" msgstr "" #: ../../content/applications/marketing/marketing_automation/getting_started/workflow_activities.rst:42 -msgid "Once an activity is saved, the :guilabel:`Workflow Activity` section appears at the bottom of the marketing automation campaign form. Each activity is displayed as a line graph." +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." msgstr "" -#: ../../content/applications/marketing/marketing_automation/getting_started/workflow_activities.rst:45 -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." +#: ../../content/applications/marketing/marketing_automation/getting_started/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." msgstr "" -#: ../../content/applications/marketing/marketing_automation/getting_started/workflow_activities.rst:48 -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." +#: ../../content/applications/marketing/marketing_automation/getting_started/workflow_activities.rst:-1 +msgid "The create and edit email drop-down option on create activities pop-up window." +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/getting_started/workflow_activities.rst:54 +msgid "In that pop-up window, proceed to create and configure the new email template." +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/getting_started/workflow_activities.rst:-1 +msgid "The create marketing template email pop-up window in Odoo Marketing Automation." +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/getting_started/workflow_activities.rst:61 +msgid "Server action activity" +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/getting_started/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/getting_started/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/getting_started/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/getting_started/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/getting_started/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/getting_started/workflow_activities.rst:-1 +msgid "The new button found on a server action pop-up in Odoo marketing automation application." +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/getting_started/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." +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/getting_started/workflow_activities.rst:89 +msgid "SMS activity" +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/getting_started/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/getting_started/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/getting_started/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." +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/getting_started/workflow_activities.rst:-1 +msgid "The create marketing template pop-up window to create a SMS template on-the-fly." +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/getting_started/workflow_activities.rst:111 +msgid "Trigger" +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/getting_started/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." +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/getting_started/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." +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/getting_started/workflow_activities.rst:-1 +msgid "A list of the trigger options available on the workflow activities pop-up form." +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/getting_started/workflow_activities.rst:125 +msgid "The trigger options are as follows:" +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/getting_started/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." +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/getting_started/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." +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/getting_started/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." +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/getting_started/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." +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/getting_started/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." +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/getting_started/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." +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/getting_started/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." +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/getting_started/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." +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/getting_started/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/getting_started/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/getting_started/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/getting_started/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." +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/getting_started/workflow_activities.rst:153 +msgid "Expiry duration" +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/getting_started/workflow_activities.rst:155 +msgid "Next, on the :guilabel:`Create Activities` pop-up form is the :guilabel:`Expiry Duration` option." +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/getting_started/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)." +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/getting_started/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." +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/getting_started/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/getting_started/workflow_activities.rst:168 +msgid "Activity and applied filters" +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/getting_started/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/getting_started/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/getting_started/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/getting_started/workflow_activities.rst:-1 +msgid "How to add an activity filter to a workflow activity in Odoo Marketing Automation." +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/getting_started/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." +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/getting_started/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)." +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/getting_started/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." +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/getting_started/workflow_activities.rst:202 +msgid "Workflow activity" +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/getting_started/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." msgstr "" #: ../../content/applications/marketing/marketing_automation/getting_started/workflow_activities.rst:-1 msgid "Typical workflow activity in Odoo Marketing Automation." msgstr "" -#: ../../content/applications/marketing/marketing_automation/getting_started/workflow_activities.rst:56 -msgid "If the :guilabel:`Activity Type` of the activity is set to :guilabel:`Email`, there are more in-depth analytics beneath the activity graph data, detailing how many emails have been :guilabel:`Sent`, and what percentage of those have been :guilabel:`Clicked`, :guilabel:`Replied` to, or :guilabel:`Bounced`." +#: ../../content/applications/marketing/marketing_automation/getting_started/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." msgstr "" -#: ../../content/applications/marketing/marketing_automation/getting_started/workflow_activities.rst:62 +#: ../../content/applications/marketing/marketing_automation/getting_started/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." +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/getting_started/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`." +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/getting_started/workflow_activities.rst:225 msgid "Child activities" msgstr "" -#: ../../content/applications/marketing/marketing_automation/getting_started/workflow_activities.rst:64 -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 automation form." +#: ../../content/applications/marketing/marketing_automation/getting_started/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." msgstr "" -#: ../../content/applications/marketing/marketing_automation/getting_started/workflow_activities.rst:68 -msgid "Child activities are sub-activities that are connected to (and triggered by) the activity above it, which is also known as its *parent activity*." +#: ../../content/applications/marketing/marketing_automation/getting_started/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." msgstr "" -#: ../../content/applications/marketing/marketing_automation/getting_started/workflow_activities.rst:71 -msgid "Odoo provides a number of triggering options to launch a child activity - all of which depend on the trigger configurations related to the parent activity. Under the desired parent activity, hover over :guilabel:`Add child activity`, and select any of the following triggers:" +#: ../../content/applications/marketing/marketing_automation/getting_started/workflow_activities.rst:-1 +msgid "A typical child activity indented beneath its parent activity." msgstr "" -#: ../../content/applications/marketing/marketing_automation/getting_started/workflow_activities.rst:75 -msgid ":guilabel:`Add Another Activity`: instantly add another activity." +#: ../../content/applications/marketing/marketing_automation/getting_started/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/getting_started/workflow_activities.rst:76 -msgid ":guilabel:`Opened`: the next activity will be triggered if the (email) recipient opens the mailing." +#: ../../content/applications/marketing/marketing_automation/getting_started/workflow_activities.rst:-1 +msgid "The various child activity trigger options in the workflow section of a campaign." msgstr "" -#: ../../content/applications/marketing/marketing_automation/getting_started/workflow_activities.rst:78 +#: ../../content/applications/marketing/marketing_automation/getting_started/workflow_activities.rst:247 +msgid "Select any of the following child activity triggers:" +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/getting_started/workflow_activities.rst:249 +msgid ":guilabel:`Add Another Activity`: instantly adds another activity." +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/getting_started/workflow_activities.rst:250 +msgid ":guilabel:`Opened`: the next activity will be triggered if the recipient opens the mailing." +msgstr "" + +#: ../../content/applications/marketing/marketing_automation/getting_started/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/getting_started/workflow_activities.rst:80 +#: ../../content/applications/marketing/marketing_automation/getting_started/workflow_activities.rst:253 msgid ":guilabel:`Replied`: the next activity will be triggered if the recipient replies to the mailing." msgstr "" -#: ../../content/applications/marketing/marketing_automation/getting_started/workflow_activities.rst:81 +#: ../../content/applications/marketing/marketing_automation/getting_started/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/getting_started/workflow_activities.rst:83 +#: ../../content/applications/marketing/marketing_automation/getting_started/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/getting_started/workflow_activities.rst:85 +#: ../../content/applications/marketing/marketing_automation/getting_started/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." msgstr "" -#: ../../content/applications/marketing/marketing_automation/getting_started/workflow_activities.rst:87 +#: ../../content/applications/marketing/marketing_automation/getting_started/workflow_activities.rst:260 msgid ":guilabel:`Bounced`: the next activity will be triggered if the mailing is bounced (not sent)." msgstr "" -#: ../../content/applications/marketing/marketing_automation/getting_started/workflow_activities.rst:89 -msgid "Once a trigger is selected, the user can configure the child activity (it has the same configuration options as a regular activity), and click :guilabel:`Save & Close` to finish creating the child activity, which will then be displayed in the :guilabel:`Workflow` section, in a slightly indented position beneath its parent activity." +#: ../../content/applications/marketing/marketing_automation/getting_started/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." msgstr "" #: ../../content/applications/marketing/sms_marketing.rst:8 @@ -2778,274 +3218,490 @@ msgid "Social marketing essentials" msgstr "" #: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:5 -msgid "Odoo's *Social Marketing* helps content marketers create and schedule posts, manage various social media accounts, analyze content effectiveness, and engage directly with social media followers in one, centralized location." +msgid "Odoo's *Social Marketing* application helps content marketers create and schedule posts, manage various social media accounts, analyze content effectiveness, and engage directly with social media followers in one, centralized location." msgstr "" #: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:10 -msgid "Add social media accounts" +msgid "Social media accounts" msgstr "" #: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:12 -msgid "In order to create posts, each social media account must be added as a stream in the Odoo *Social Marketing* application." +msgid "In order to create social posts and analyze content with Odoo *Social Marketing*, social media accounts **must** be added as a *stream* on the application's main dashboard." msgstr "" #: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:16 -msgid "Add a social media stream" +msgid "Be aware that personal profiles **cannot** be added as a stream. The main use of Odoo *Social Marketing* is to manage and analyze business accounts on social media platforms." msgstr "" -#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:18 -msgid "Add a social media account as a stream by navigating to :menuselection:`Social Marketing` and then select the :guilabel:`Add A Stream` button located in the upper left corner" +#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:20 +msgid "Odoo *Social Marketing* has some limitations in regards to social media accounts. For example, Odoo **cannot** handle a large quantity of various pages (e.g. ~40 pages) under the same company. The same limitations are present in a multi-company environment because of how the API is constructed." msgstr "" -#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:21 -msgid "When :guilabel:`Add A Stream` is clicked, the following pop-up appears, displaying the different social media outlets to choose from." -msgstr "" - -#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:-1 -msgid "View of the pop-up that appears when 'Add a Stream' is selected in Odoo." +#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:26 +msgid "In multi-company environments, if every company doesn't activate a page at once, it will result in a permission error." msgstr "" #: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:29 -msgid "Additional social media outlet options are available depending on your version of Odoo." +msgid "For example, if Company 1 is the only company selected from the main Odoo dashboard, and activates *Facebook Page 1* and *Facebook Page 2*, then those pages will be accesible on the *Social Marketing* dashboard." msgstr "" -#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:31 -msgid "From this pop-up, select a social media option: :guilabel:`Facebook`, :guilabel:`LinkedIn`, or :guilabel:`Twitter`." -msgstr "" - -#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:34 -msgid "Then, Odoo navigates directly to that specific social media outlet's authorization page, where permission must be granted, in order for Odoo to add that particular social media account to the *Social Marketing* application as a stream on the main dashboard of the app." -msgstr "" - -#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:39 -msgid "A Facebook page can be added as long as the Facebook account that grants permission is the administrator for the page. Also, different pages can be added for different streams." -msgstr "" - -#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:42 -msgid "Once permission is granted, Odoo navigates back to the :guilabel:`Feed` on the main :guilabel:`Social Marketing` dashboard, and a new column with that account's posts are automatically added." -msgstr "" - -#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:46 -msgid "From here, new accounts and/or streams can be added and managed at any time." -msgstr "" - -#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:-1 -msgid "Example of how a populated stream-filled dashboard looks in Odoo Social Marketing" -msgstr "" - -#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:53 -msgid "Adding social media accounts to the feed also links that specific social media platform's KPIs (if the platform has them). To get redirected to the statistics and metrics related to any social account, click on :guilabel:`Insights`." +#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:33 +msgid "However, if on that same database, the user adds Company 2 from the company drop-down menu in the header, and attempts to add those same streams, it results in a permission error." msgstr "" #: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:0 -msgid "The insights link that can be accessed for each social media stream added in Odoo." +msgid "View of the permission error that appears when incorrectly attempting to add stream." msgstr "" -#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:62 -msgid "Create and publish social media posts in Odoo" +#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:41 +msgid "Social media streams" msgstr "" -#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:64 -msgid "To create content for social media accounts in the :menuselection:`Social Marketing` application, click the :guilabel:`New Post` button located in the upper-left corner of the main dashboard, or navigate to :menuselection:`Posts --> Create` from the header menu." -msgstr "" - -#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:68 -msgid "Either route reveals a blank post template page that can be customized and configured in a number of different ways." +#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:43 +msgid "To add a social media business account as a stream, navigate to :menuselection:`Social Marketing app` and select the :guilabel:`Add A Stream` button located in the upper-left corner. Doing so reveals an :guilabel:`Add a Stream` pop-up window." msgstr "" #: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:-1 -msgid "How to create a social media post directly through Odoo" +msgid "View of the pop-up window that appears when Add a Stream is selected in Odoo." msgstr "" -#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:76 -msgid "Post template" +#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:51 +msgid "In the :guilabel:`Add a Stream` pop-up window, choose to :guilabel:`Link a new account` for a business from any of the following popular social media platforms: :guilabel:`Facebook`, :guilabel:`Instagram`, :guilabel:`LinkedIn`, :guilabel:`Twitter`, and :guilabel:`YouTube`." msgstr "" -#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:78 -msgid "The post template page has many different options avaiable." +#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:55 +msgid "After clicking the desired social media outlet from the :guilabel:`Add a Stream` pop-up window, Odoo navigates directly to that specific social media outlet's authorization page, where permission must be granted, in order for Odoo to add that particular social media account as a stream to the *Social Marketing* application." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:-1 +msgid "Sample of a populated social marketing dashboard with social media streams and content." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:64 +msgid "Once permission is granted, Odoo navigates back to the :guilabel:`Feed` on the main :guilabel:`Social Marketing` dashboard, and a new column, with that account's posts, is added. Accounts/streams can be added at any time." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:69 +msgid "A :guilabel:`Facebook` page can be added as long as the :guilabel:`Facebook` account that grants permission is the administrator for the page. It should also be noted that different pages can be added for different streams." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:74 +msgid ":guilabel:`Instagram` accounts are added through a :guilabel:`Facebook` login because it uses the same API. This means, an :guilabel:`Instagram` account needs to be linked to a :guilabel:`Facebook` account in order for it to show up as a stream in Odoo." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:79 +msgid "Posts" msgstr "" #: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:81 -msgid "'Your Post' section" +msgid "Clicking on a post from a social media stream reveals a pop-up window, showcasing the content of that specific post, along with all the engagement data related to it (e.g. likes, comments, etc.)." msgstr "" -#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:83 -msgid "The first option is the :guilabel:`Post on` field. This is where it's determined on what social media account(s), or on which website(s) via push notification, this post will be published." +#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:-1 +msgid "Sample of a social media post's pop-up window in Odoo Social Marketing application." msgstr "" -#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:87 -msgid "In order for the :guilabel:`Push Notification` option to appear, make sure the *Enable Web Push Notifications* feature is enabled in the *Website* app. To do that, navigate to :menuselection:`Website --> Configuration --> Settings`, activate :guilabel:`Enable Web Push Notifications`, fill out the corresponding fields, and click :guilabel:`Save`." +#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:88 +msgid "If desired, the user can leave a new comment of the post from the post's pop-up window, by typing one in the :guilabel:`Write a comment...` field, and clicking :guilabel:`Enter` to post that comment." msgstr "" -#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:92 -msgid "Odoo automatically provides every available social media account that's been linked to the database as an option in this section, as well." +#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:93 +msgid "Create leads from comments" msgstr "" -#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:96 -msgid "If a social media account hasn't been added as a stream to the *Social Marketing* application, it will not appear as an option on the post template." +#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:95 +msgid "Odoo *Social Marketing* also provides the ability to create leads directly from social media comments." msgstr "" -#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:99 -msgid "Next, there's the :guilabel:`Message` field. This is where the main content of the post is created." +#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:98 +msgid "To create a lead from a comment left on a social media post, click on the desired post from the dashboard to reveal that post's specific pop-up window. Then, scroll to the desired comment, and click the :guilabel:`three vertical dots` icon to the right of that comment." msgstr "" -#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:101 -msgid "Type the desired message for the post in this field. To the right, as the :guilabel:`Message` field is populated, Odoo displays visual samples of how the post will look on all the previously selected social media accounts from the :guilabel:`Post on` field above." +#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:102 +msgid "Doing so reveals a drop-down menu with the option: :guilabel:`Create Lead`." msgstr "" -#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:106 -msgid "Emojis can also be added directly to the text in the :guilabel:`Message` field. Just click the :guilabel:`emoji (smiley face) icon`, located on the line of the :guilabel:`Message` field to the far right. Clicking this icon reveals a drop-down containing numerous emojis to choose from." +#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:-1 +msgid "The drop-down menu beside a comment revealing the option to create a lead." msgstr "" -#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:110 -msgid "If images are to be used in the post, click the :guilabel:`ATTACH IMAGES` link beneath the :guilabel:`Message` field, and Odoo reveals a pop-up window. In this pop-up, the desired image must be chosen, and then uploaded." +#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:108 +msgid "Upon clicking :guilabel:`Create Lead` from the comment's drop-down menu, a :guilabel:`Conver Post to Lead` pop-up window appears." msgstr "" -#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:114 -msgid "A preview of the entire post, text and image (if applicable), is instantly displayed in the visual preview of the post." +#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:-1 +msgid "The convert post to lead pop-up window that appears in Odoo Social Marketing." msgstr "" -#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:117 -msgid "Next, there's the option to attach this post to a specific marketing campaign in the database in the :guilabel:`Campaign` field. Click the blank line next to :guilabel:`Campaign` to reveal the previously configured campaigns to choose from." +#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:115 +msgid "In this pop-up window, select to either: :guilabel:`Create a new customer`, :guilabel:`Link to an existing customer`, or :guilabel:`Do not link to a customer`." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:119 +msgid "If :guilabel:`Link to an existing customer` is selected, a new :guilabel:`Customer` field appears beneath those options, wherein a customer can be chosen to be linked to this lead." msgstr "" #: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:122 -msgid "A new campaign can be created, as well, by typing the name of the new campaign on the blank :guilabel:`Campaign` field, and selecting :guilabel:`Create` from the drop-down field menu. Or, select :guilabel:`Create and edit` from the menu to further customize that newly-created campaign." +msgid "Once the desired selection has been made, click the :guilabel:`Convert` button at the bottom of the :guilabel:`Convert Post to Lead` pop-up window. Doing so reveals a fresh lead detail form, where the necessary information can be entered and processed." msgstr "" -#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:128 -msgid "A social post does *not* need to be attached to a campaign." +#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:-1 +msgid "New lead detail form generated from a social media comment in Odoo Social Marketing." msgstr "" -#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:130 -msgid "Then, in the :guilabel:`When` field, choose either :guilabel:`Send Now` to have Odoo publish the post immediately, or :guilabel:`Schedule later` to have Odoo publish the post at a later date and time." +#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:131 +msgid "Insights" msgstr "" -#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:134 -msgid "If :guilabel:`Schedule later` is selected, Odoo reveals a new field beneath it (the :guilabel:`Scheduled post date` field). Clicking that empty field reveals a pop-up calendar, in which a future date and time is designated. At which time, Odoo will promptly publish the post on the pre-determined social media accounts." +#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:133 +msgid "When a social media account stream is added to the *Social Marketing* dashboard, each stream also displays and links that specific social media platform's KPIs (if the platform has them)." msgstr "" -#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:139 -msgid "Click on the desired date to schedule the post for that day. Then, either select and customize the default time in the :guilabel:`Scheduled post date` field manually. Or, adjust the desired post time, by clicking the :guilabel:`scheduling (clock) icon` located on the calendar pop-up, and choose the desired time for Odoo to publish this post on that future date." +#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:136 +msgid "To get redirected to the statistics and metrics related to any social media account's KPIs, click on the :guilabel:`Insights` link, located at the top of each stream." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:-1 +msgid "Visual of how the Insights link appears on the dashboard of the Social Marketing app." msgstr "" #: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:144 -msgid "If scheduling a post, remember to hit :guilabel:`Schedule` in the upper left of the post template. Doing so, locks in that specific date/time for Odoo to send the post, and it changes the status of the post to :guilabel:`Scheduled`." +msgid "In a multi-company environment, if not *all* pages are selected, de-authentication happens." msgstr "" -#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:149 -msgid "Also, when :guilabel:`Schedule` is clicked, a number of analytical smart buttons appear on the post page. Each one offers up a detailed anaylsis of the corresponding metric (e.g. :guilabel:`Leads`, :guilabel:`Revenues`, etc.). These same smart buttons appear when a post is officially published, as well." +#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:146 +msgid "For example, if the companies have 3 *Facebook* pages, but only grant access to 1, and try to grant access to another at a later date, they will be de-authenticated, and access to the initial page's insights/analytics will be lost." msgstr "" -#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:155 -msgid "'Web Notification Options' section" +#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:150 +msgid "So, be sure to add *all* pages for *all* companies in a multi-company environment to avoid this issue. If a page gets de-autenticated, simply remove the stream, and re-establish it." msgstr "" -#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:157 -msgid "If any :guilabel:`Push Notifications` are selected in the :guilabel:`Post on` field, Odoo provides another section of settings/options at the bottom of the post template. It should be noted that *none* of these fields are required." +#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:154 +msgid "Create and post social media content" msgstr "" -#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:161 -msgid "The first field is for a :guilabel:`Push Notification Title`. This is text that is displayed as the title of the push notification whenever it's sent. Odoo displays a visual preview of this title, if one is created." +#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:156 +msgid "Odoo *Social Marketing* offers the ability to create and post content for social media accounts directly through the application." msgstr "" -#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:165 -msgid "To designate a specific page on the website that should trigger this push notification, enter that page's URL in the :guilabel:`Push Target URL` field. Then, once a visitor reaches that specific page, Odoo will display the push notification." +#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:159 +msgid "To create content for social media accounts, navigated to the :menuselection:`Social Marketing app`, and click :guilabel:`New Post` located in the upper-right corner of the *Social Marketing* dashboard." msgstr "" -#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:169 -msgid "Below that field is the option to add a custom :guilabel:`Push Icon Image`. This is an icon that appears beside the push notification. By default, Odoo uses a \"smiley face\" as the icon." +#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:-1 +msgid "New Post button on the main dashboard of the Odoo Social Marketing application." msgstr "" -#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:172 -msgid "To upload a new image, click the :guilabel:`Edit (pencil) icon` when the :guilabel:`Push Icon Image` field is hovered over with the cursor. Then, proceed to locate and upload the desired image, and Odoo automatically displays a preview of how the icon will appear on the push notification." +#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:167 +msgid "Or, navigate to :menuselection:`Social Marketing app --> Posts` and click the :guilabel:`New` button." msgstr "" -#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:176 -msgid "Next, there is the option to :guilabel:`Send at Visitors' Timezone`. If enabled, Odoo will send it at the appropriate, pre-determined time, taking the visitor's location into consideration." +#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:-1 +msgid "New button on the Social Posts page in the Odoo Social Marketing application." msgstr "" -#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:180 -msgid "Save, post, and test notification options" +#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:174 +msgid "Either route reveals a blank social media post detail form that can be customized and configured in a number of different ways." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:-1 +msgid "Blank social media post detail page in Odoo Social Marketing." msgstr "" #: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:182 -msgid "When all the modifications have been made, and the post is completed, either click :guilabel:`Save` to save the post as a *Draft*. Or, if the post is ready to be published immediately, click :guilabel:`Post`, and Odoo automatically publishes the post on the pre-determined social media accounts." +msgid "Post detail form" msgstr "" -#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:187 -msgid "There is also the option to :guilabel:`Test Notification`, if a :guilabel:`Push Notification` was selected in the :guilabel:`Post on` field. Clicking that, provides a quick example of how the notification will appear for visitors." +#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:184 +msgid "The social media post detail form in Odoo *Social Marketing* has many different configurable options available." msgstr "" -#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:192 -msgid "Social post status bar" +#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:188 +msgid "Company" msgstr "" -#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:194 -msgid "In the top-right of the :guilabel:`Post Template` page is the :guilabel:`Status Bar`. This displays the current status of the post." +#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:190 +msgid "If working in a multi-company environment, the first field in the :guilabel:`Your Post` section of the social media post detail form is :guilabel:`Company`. In this field, select the company that should be connected to this specific social media post." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:195 +msgid "Post on" msgstr "" #: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:197 -msgid "When :guilabel:`Save` is clicked, the post is in the *Draft* status." -msgstr "" - -#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:199 -msgid "If the post is scheduled to be sent at a future date/time, and the :guilabel:`Schedule` button has been clicked, the status of the post is *Scheduled*." +msgid "If working in a single-company environment, the first field in the :guilabel:`Your Post` section of the social media post detail form is :guilabel:`Post on`. In this field, determine which social media outlets (streams) this post is intended to be posted on, and/or which website's visitors this post should be sent to, via push notification, by checking the box beside the desired option(s)." msgstr "" #: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:202 -msgid "If the post is in the process of currently being published or sent, the status of the post is *Posting*. And, lastly, if the post has already been published or sent, the status is *Posted*." +msgid "Odoo automatically provides every available social media account that's been linked to the database as an option in this section. If a social media account hasn't been added as a stream to the *Social Marketing* application, it will **not** appear as an option on the post template." msgstr "" #: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:206 +msgid "Multiple social media outlets (streams) and websites can be selected in the :guilabel:`Post on` field. At least **one** option in the :guilabel:`Post on` field *must* be selected." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:210 +msgid "In order for the :guilabel:`Push Notification` option to appear on the social media post detail form in Odoo *Social Marketing*, make sure the *Enable Web Push Notifications* feature is enabled in the *Website* app." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:214 +msgid "To do that, navigate to :menuselection:`Website app --> Configuration --> Settings`, activate :guilabel:`Enable Web Push Notifications`, fill out the corresponding fields, and click :guilabel:`Save`." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:219 +msgid "Message" +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:221 +msgid "Next, there's the :guilabel:`Message` field. This is where the main content of the post is created." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:223 +msgid "In the :guilabel:`Message` field, type in the desired message for the social post. After typing, click away from the :guilabel:`Message` field to reveal visual samples of how the post will look on all the previously selected social media accounts (and/or websites, as push notifications)." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:-1 +msgid "Sample social media post with visual samples of how it will appear on social media outlets." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:232 +msgid "Emojis can also be added directly to the text in the :guilabel:`Message` field. Just click the :guilabel:`🙂 (smiley face)` icon, located on the line of the :guilabel:`Message` field to the far right. Clicking this icon reveals a drop-down menu containing numerous emojis to choose from." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:237 +msgid "If :guilabel:`Twitter` is chosen in the :guilabel:`Post on` field, a character counter appears beneath the :guilabel:`Message` field." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:241 +msgid "Attach Images" +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:243 +msgid "If images are to be used in the post, click the :guilabel:`Attach Images` button, in the :guilabel:`Attach Images` field, located beneath the :guilabel:`Message` field. When clicked, Odoo reveals a pop-up window. In this pop-up window, select the desired image from the hard drive, and upload it." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:248 +msgid "After successfully uploading and attaching the desired image, Odoo reveals a new preview of the social media post, complete with the newly-added image, on the right side of the detail form." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:-1 +msgid "Visualized samples of post with newly-attached images in Odoo Social Marketing." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:256 +msgid "Campaign" +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:258 +msgid "Next, there is the :guilabel:`Campaign` field. This non-required field provides the options to attach this post to a specific marketing campaign." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:261 +msgid "To add this post to a pre-existing campaign, click the empty :guilabel:`Campaign` field to reveal a drop-down menu, containing all the existing campaigns in the database. Select the desired campaign from this drop-down menu to add this post to that campaign." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:265 +msgid "To create a new campaign directly from the social media post detail form, start typing the name of the new campaign in the blank :guilabel:`Campaign` field, and select either :guilabel:`Create` or :guilabel:`Create and edit...`." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:-1 +msgid "Drop-down menu options of Create or Create and edit in the Campaign field." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:273 +msgid "Clicking :guilabel:`Create` creates the campaign, which can be edited/customized later." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:275 +msgid "Clicking :guilabel:`Create and edit...` creates the campaign, and reveals a :guilabel:`Create Campaign` pop-up form, wherein the :guilabel:`Campaign Identifier`, :guilabel:`Responsible`, and :guilabel:`Tags` can be instantly configured." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:-1 +msgid "Create campaign pop-up window that appears on a social media post detail form." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:283 +msgid "When all the desired settings have been entered, click :guilabel:`Save & Close` to save the campaign and return to the social media post detail form." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:287 +msgid "When" +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:289 +msgid "Then, in the :guilabel:`When` field, choose either :guilabel:`Send Now` to have Odoo publish the post immediately, or :guilabel:`Schedule later` to have Odoo publish the post at a later date and time." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:293 +msgid "If :guilabel:`Schedule later` is selected, a new :guilabel:`Scheduled Date` field appears. Clicking the empty field reveals a pop-up calendar, in which a future date and time can be designated." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:-1 +msgid "Schedule date pop-up window that appears on social media post detail form in Odoo." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:300 +msgid "After selecting a desired date and time, click :guilabel:`Apply`. Then, Odoo will promptly publish the post at that specific date and time on the pre-detemined social media account(s)." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:304 +msgid "If scheduling a post, the :guilabel:`Post` button at the top of the social media post detail form changes to :guilabel:`Schedule`. Be sure to click :guilabel:`Schedule` after completing the social media post detail form." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:308 +msgid "Doing so, locks in that specific date/time for Odoo to send the post, and it changes the status of the post to :guilabel:`Scheduled`." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:312 +msgid "Push Notification Options" +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:314 +msgid "If one (or multiple) :guilabel:`[Push Notification]` options are chosen in the :guilabel:`Post on` field, a specific :guilabel:`Push Notification Options` section appears at the bottom of the social media post detail form." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:-1 +msgid "Push notification options section on a social media post detail form." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:322 +msgid "It should be noted that *none* of these fields are required." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:324 +msgid "The first field in this section is :guilabel:`Notification Title`. In this field, there is the option to add a custom title to the push notification that will be sent." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:327 +msgid "To designate a specific page on the website that should trigger this push notification, enter that page's URL in the :guilabel:`Target URL` field. Then, once a visitor reaches that specific page, Odoo will display the push notification." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:331 +msgid "Below that field is the option to add a custom :guilabel:`Icon Image` to the push notification. This is an icon that appears beside the push notification." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:334 +msgid "To upload a new image, click the :guilabel:`✏️ (pencil) icon` when hovering over the :guilabel:`Icon Image` camera icon. Doing so reveals a pop-up window, in which the desired icon image can be located on the hard drive, and subsequently uploaded." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:338 +msgid "Once that's complete, Odoo automatically updates the visual preview of how the icon appears on the push notification." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:342 +msgid "Next, if the post is scheduled to be posted later, there is the option to ensure the post is sent in the visitor's timezone, by enabling the :guilabel:`Local Time` option. If enabled, Odoo will send it at the appropriate, pre-determined time, taking the visitor's location into consideration." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:0 +msgid "The Local Time option in the Push Notification Options section of features." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:351 +msgid "Then, there is the :guilabel:`Match all records` field. This field provides the ability to target a specific group of recipients in the database, based on certain criteria, and can be applied to match :guilabel:`all` or :guilabel:`any` of the rules." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:355 +msgid "To utilize this field, click the :guilabel:`+ Add condition` button, which reveals an equation-like rule field." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:358 +msgid "In this equation-like rule field, specifiy the specific criteria Odoo should take into account when sending this post to a particular target audience." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:-1 +msgid "Push notification conditions set up to match a specific amount of records in the database." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:365 +msgid "To add an additional rule, click the :guilabel:`➕ (plus sign) icon` to the far-right of the rule." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:367 +msgid "To add a branch (series of additional rules based on the previous rule, to further specify a target audience), click the unique :guilabel:`branch icon`, located to the right of the :guilabel:`➕ (plus sign) icon`." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:371 +msgid "Lastly, click the :guilabel:`🗑️ (trash can) icon` to delete any rule." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:373 +msgid "The size of the specified target audience of recipients is represented by the number of :guilabel:`Records` displayed beneath the rules." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:377 msgid "Posts page" msgstr "" -#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:208 -msgid "To see a complete overview of posts, go to Odoo :menuselection:`Social Marketing`, and click :menuselection:`Posts` in the header menu. Here, every post that has been created and posted with Odoo is available." +#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:379 +msgid "To see a complete overview of posts, go to Odoo :menuselection:`Social Marketing app --> Posts`. Here, on the :guilabel:`Social Posts` page, every post that has been created and posted with Odoo can be seen and accessed." msgstr "" -#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:212 -msgid "There are four different view options for :guilabel:`Posts` page data: *kanban*, *calendar*, *list*, and *pivot*. The view options are located in the upper right corner of the :guilabel:`Posts` page, beneath the search bar." +#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:383 +msgid "There are four different view options for the :guilabel:`Social Posts` page data: *kanban*, *calendar*, *list*, and *pivot*." msgstr "" -#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:218 +#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:386 +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:220 -msgid "By default, Odoo displays the posts in a kanban view. The information on this page can be sorted even further, via the :guilabel:`Filters` and :guilabel:`Group by` drop-down menu." +#: ../../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 "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:397 +msgid "The kanban view is represented by an :guilabel:`inverted bar graph icon` in the upper-right corner." msgstr "" #: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:0 msgid "Kanban view of the posts page in the Odoo Social Marketing application." msgstr "" -#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:227 +#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:404 msgid "Calendar view" msgstr "" -#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:229 -msgid "The calendar view option displays a visual representation 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." +#: ../../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 "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:411 +msgid "Clicking on a date reveals a blank social media post detail form, in which a social media post can be created, and Odoo will post it on that specific date/time." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:414 +msgid "The calendar view is represented by a :guilabel:`calendar icon` in the upper-right corner." msgstr "" #: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:0 msgid "Example of the calendar view in Odoo Social Marketing." msgstr "" -#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:239 -msgid "The list view option is similar to the kanban option, but instead of individual blocks, all the post information is displayed in a clear, list layout. Each line of the list displays the :guilabel:`Social Accounts`, :guilabel:`Message`, and :guilabel:`Status` of every post." +#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:422 +msgid "The list view option is similar to the kanban option, but instead of individual blocks, all post information is displayed in a clear, list layout. Each line of the list displays the :guilabel:`Social Accounts`, :guilabel:`Message`, and :guilabel:`Status` of every post." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:426 +msgid "There is also a helpful left sidebar that organizes all posts by :guilabel:`Status` and lists all connected :guilabel:`Social Accounts`, as well." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:429 +msgid "The list view is represented by four vertical lines in the upper-right corner." msgstr "" #: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:0 msgid "View of the list option on the posts page in Odoo Social Marketing." msgstr "" -#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:247 +#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:435 msgid "Pivot view" msgstr "" -#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:249 +#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:437 msgid "The pivot view option provides a fully customizable grid table, where different measures of data can be added and analyzed." msgstr "" @@ -3053,111 +3709,107 @@ msgstr "" msgid "View of the pivot option on the posts page in Odoo Social Marketing." msgstr "" -#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:256 -msgid "The pivot view option provides numerous analytical options, allowing for in-depth, detailed analysis of various posts." +#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:444 +msgid "The pivot view option provides numerous analytical options, allowing for in-depth, detailed analysis of various posts and metrics." msgstr "" -#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:259 -msgid "Click on any :guilabel:`+ (plus sign) icon` next to a line in the pivot table to reveal more metric options to add to the grid." +#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:447 +msgid "Click on any :guilabel:`➕ (plus sign) icon` next to a line in the pivot table to reveal more metric options to add to the grid." msgstr "" -#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:262 -msgid "While in the pivot view, the option to :guilabel:`Insert in Spreadsheet` is available, located to the right of the :guilabel:`Measures` drop-down." +#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:450 +msgid "While in the pivot view, the option to :guilabel:`Insert in Spreadsheet` is available, located to the right of the :guilabel:`Measures` drop-down menu, in the upper-left corner of the :guilabel:`Social Posts` page." msgstr "" -#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:265 -msgid "When clicked, a pop-up appears, where the option to add this information to a current spreadsheet is available. The option to create a new spreadsheet for this information on-the-fly is also available in this pop-up, as well." +#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:454 +msgid "Next to the :guilabel:`Insert in Spreadsheet` are three options, specific to the pivot view." msgstr "" -#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:269 -msgid "Next to the :guilabel:`Insert in Spreadsheet` are three view options, specific to the pivot view." +#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:456 +msgid "From left to right, those options are:" msgstr "" -#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:272 -msgid "From left to right, the options are:" -msgstr "" - -#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:274 +#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:458 msgid ":guilabel:`Flip Axis`, which switches the *X* and *Y* axis in the grid table." msgstr "" -#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:275 +#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:459 msgid ":guilabel:`Expand All`, which expands each line in the grid, revealing more detailed information related to it." msgstr "" -#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:277 +#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:461 msgid ":guilabel:`Download`, which, when clicked, instantly downloads the pivot table as a spreadsheet." msgstr "" -#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:281 +#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:465 msgid "Visitors" msgstr "" -#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:283 -msgid "To see a complete overview of all the people who have visited the website(s) connected to the database, navigate to :menuselection:`Social Marketing --> Visitors` in the header menu." +#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:467 +msgid "To see a complete overview of all the people who have visited the website(s) connected to the database, navigate to :menuselection:`Social Marketing app --> Visitors`." msgstr "" #: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:-1 msgid "View of the Visitors page in the Odoo Social Marketing application." msgstr "" -#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:290 -msgid "Here, Odoo provides a detailed layout of all the visitors' pertinent information in a default kanban view. This same information can be sorted via the :guilabel:`Filters` and :guilabel:`Group By` options." +#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:474 +msgid "Here, Odoo provides a detailed layout of all the visitors' pertinent information in a default kanban view. If visitors already have contact information in the database, the option to send them an :guilabel:`Email` and/or an :guilabel:`SMS` is available." msgstr "" -#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:294 -msgid "The visitor data can also be viewed as a list or a graph. Those view options are located in the upper-right corner of the :guilabel:`Visitors` page beneath the search bar." +#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:478 +msgid "This same visitor data can also be viewed as a list or a graph. Those view options are located in the upper-right corner of the :guilabel:`Visitors` page." msgstr "" -#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:298 +#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:482 msgid "Social media page" msgstr "" -#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:300 -msgid "Go to :menuselection:`Configuration --> Social Media` to see a collection of all social media options: :guilabel:`Facebook`, :guilabel:`LinkedIn`, :guilabel:`Twitter`, and :guilabel:`Push Notifications`." +#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:484 +msgid "Another way to quickly link social media accounts to Odoo *Social Marketing* can be done on the :guilabel:`Social Media` page. To access the :guilabel:`Social Media` page, navigate to :menuselection:`Social Marketing app --> Configuration --> Social Media`." +msgstr "" + +#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:488 +msgid "On the :guilabel:`Social Media` page there is a collection of all social media options, each complete with a :guilabel:`Link account` button: :guilabel:`Facebook`, :guilabel:`Instagram`, :guilabel:`LinkedIn`, :guilabel:`Twitter`, :guilabel:`YouTube`, and :guilabel:`Push Notifications`." msgstr "" #: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:-1 msgid "View of the social media page in the Odoo Social Marketing application." msgstr "" -#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:308 -msgid "If no account has been linked to any particular social media, click :guilabel:`Link Account` to proceed through the linking process." -msgstr "" - -#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:312 +#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:497 msgid "Social accounts page" msgstr "" -#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:314 -msgid "To see a list of all social accounts linked to the database, go to :menuselection:`Configuration --> Social Accounts`. This page will display the :guilabel:`Medium Name` and the :guilabel:`Social Media` platform it is associated with." +#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:499 +msgid "To see a list of all social accounts and websites linked to the database, go to :menuselection:`Social Marketing app --> Configuration --> Social Accounts`. This :guilabel:`Social Accounts` display the :guilabel:`Name`, the :guilabel:`Handle/Short Name`, the :guilabel:`Social Media` platform, who it was :guilabel:`Created by`, and the :guilabel:`Company` to which it is associated." msgstr "" #: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:-1 msgid "View of the social accounts page in the Odoo Social Marketing application." msgstr "" -#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:322 -msgid "To edit/modify any social accounts, simply select the desired account from the list on this page, and proceed to make any adjustments necessary. Don't forget to hit :guilabel:`Save` to secure any changes." +#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:509 +msgid "To edit/modify any of the social accounts on this page, simply select the desired account from the list on this page, and proceed to make any adjustments necessary." msgstr "" -#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:327 +#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:513 msgid "Social streams page" msgstr "" -#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:329 -msgid "Navigate to :menuselection:`Configuration --> Social Streams` to reveal a separate page containing all of the social media streams that have been added to the main dashboard of the *Social Marketing* app, accessible via the :guilabel:`Feed` option in the header menu." +#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:515 +msgid "To view a separate page with all the social media streams that have been added to the main *Social Marketing* dashboard, navigate to :menuselection:`Social Marketing app --> Configuration --> Social Streams`." msgstr "" -#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:337 -msgid "Here, the social stream information is organized in a list with the :guilabel:`Social Media`, the :guilabel:`Title` of the stream, and the :guilabel:`Type` of the stream (e.g. :guilabel:`Posts`, :guilabel:`Keyword`, etc.)." +#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:523 +msgid "Here, the social stream information is organized in a list with the :guilabel:`Social Media`, the :guilabel:`Title` of the stream, the :guilabel:`Type` of the stream (e.g. :guilabel:`Posts`, :guilabel:`Keyword`, etc.), who it was :guilabel:`Created by`, and the :guilabel:`Company` to which it is associated." msgstr "" -#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:341 -msgid "To modify any stream's information, simply click the desired stream from the list, and proceed to make any necessary adjustments. Don't forget to hit :guilabel:`Save` to secure any changes." +#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:528 +msgid "To modify any stream's information, simply click the desired stream from the list, and proceed to make any necessary adjustments." msgstr "" -#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:345 +#: ../../content/applications/marketing/social_marketing/essentials/social_essentials.rst:532 msgid ":doc:`/applications/marketing/social_marketing/essentials/social_campaigns`" msgstr "" @@ -3181,6 +3833,10 @@ msgstr "" 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." msgstr "" +#: ../../content/applications/marketing/surveys/create.rst:13 +msgid "Getting started" +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." msgstr "" diff --git a/locale/sources/productivity.pot b/locale/sources/productivity.pot index 37c2712a7..0a2aa953e 100644 --- a/locale/sources/productivity.pot +++ b/locale/sources/productivity.pot @@ -8,7 +8,7 @@ msgid "" msgstr "" "Project-Id-Version: Odoo saas-16.1\n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2023-12-19 13:26+0000\n" +"POT-Creation-Date: 2024-01-19 10:30+0000\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME \n" "Language-Team: LANGUAGE \n" @@ -502,129 +502,125 @@ msgid "Overview" msgstr "" #: ../../content/applications/productivity/discuss/overview/get_started.rst:3 -msgid "Get Started with Discuss" +msgid "Get started with Discuss" msgstr "" #: ../../content/applications/productivity/discuss/overview/get_started.rst:5 -msgid "Discuss allows you to bring all of your company’s communication together through messages, notes, and chat. Share information, projects, files, prioritize tasks, and stay connected with colleagues and partners throughout applications. Forge better relationships, increase productivity and transparency by promoting a convenient way of communicating." +msgid "Odoo *Discuss* is an internal communication app that allows users to connect through messages, notes, and file sharing, either through a persistent chat window that works across applications, or through the dedicated *Discuss* dashboard." msgstr "" -#: ../../content/applications/productivity/discuss/overview/get_started.rst:13 -msgid "Choose your notifications preference" +#: ../../content/applications/productivity/discuss/overview/get_started.rst:12 +msgid "Choose notifications preference" msgstr "" -#: ../../content/applications/productivity/discuss/overview/get_started.rst:15 -msgid "Access your *Preferences* and choose how you would like your notifications to be handled." +#: ../../content/applications/productivity/discuss/overview/get_started.rst:14 +msgid "Access user-specific preferences for the *Discuss* app by navigating to :menuselection:`Settings app --> Users --> User --> Preferences tab`." msgstr "" #: ../../content/applications/productivity/discuss/overview/get_started.rst:-1 -msgid "View of the preferences page for Odoo Discuss" +msgid "View of the Preferences tab for Odoo Discuss." msgstr "" -#: ../../content/applications/productivity/discuss/overview/get_started.rst:23 -msgid "By default, the field is set as *Handle by Emails* making messages, notes, and notifications where you were mentioned or that you follow, to be sent through email. By choosing *Handle in Odoo*, they are shown in the *Inbox*." +#: ../../content/applications/productivity/discuss/overview/get_started.rst:21 +msgid "By default, the :guilabel:`Notification` field is set as :guilabel:`Handle by Emails`. With this setting enabled, a notification email will be sent by Odoo every time a message is sent from the chatter, a note is sent with an `@` mention (from chatter), or a notification is sent for a record that the user follows. Something that triggers a notification is changing of the stage (if an email\\ is configured to be sent, for example if the task is set to :guilabel:`Done`)." msgstr "" -#: ../../content/applications/productivity/discuss/overview/get_started.rst:24 -msgid "Messages can then be *Marked as Todo*, *Replied*, or *Marked as Read*." +#: ../../content/applications/productivity/discuss/overview/get_started.rst:27 +msgid "By choosing :guilabel:`Handle in Odoo`, the above notifications are shown in the *Discuss* app's *inbox*. Messages can have the following actions taken on them: respond with an emoji by clicking :guilabel:`Add a Reaction`, or reply to the message by clicking on :guilabel:`Reply`. Additional actions may include starring the message by clicking :guilabel:`Marked as Todo`, or pinning the message by selecting :guilabel:`Pin` or even mark the message as unread by selecting :guilabel:`Marked as unread`." msgstr "" #: ../../content/applications/productivity/discuss/overview/get_started.rst:-1 -msgid "View of an inbox message and its action options in Odoo Discuss" -msgstr "" - -#: ../../content/applications/productivity/discuss/overview/get_started.rst:30 -msgid "The messages tagged as *Mark as Todo* are also shown in *Starred*, while the ones *Marked as Read* are moved to *History*." -msgstr "" - -#: ../../content/applications/productivity/discuss/overview/get_started.rst:-1 -msgid "View of messages marked as todo in Odoo Discuss" +msgid "View of an inbox message and its action options in Odoo Discuss." msgstr "" #: ../../content/applications/productivity/discuss/overview/get_started.rst:38 -msgid "Start Chatting" +msgid "Clicking :guilabel:`Mark as Todo` on a message causes it to appear on the :guilabel:`Starred` page, while clicking :guilabel:`Mark as Read` moves the message to :guilabel:`History`." msgstr "" -#: ../../content/applications/productivity/discuss/overview/get_started.rst:40 -msgid "The first time you log in to your account, OdooBot sends you a message asking for permission to receive desktop notifications to chats. If accepted, you receive push notifications to the messages sent to you despite of where you are in Odoo." +#: ../../content/applications/productivity/discuss/overview/get_started.rst:-1 +msgid "View of messages marked as todo in Odoo Discuss." +msgstr "" + +#: ../../content/applications/productivity/discuss/overview/get_started.rst:46 +msgid "Start chatting" +msgstr "" + +#: ../../content/applications/productivity/discuss/overview/get_started.rst:48 +msgid "The first time a user logs in to their account, OdooBot sends a message asking for permission to send desktop notifications for chats. If accepted, the user will receive push notifications on their desktop for the messages they receive, regardless of where the user is in Odoo." msgstr "" #: ../../content/applications/productivity/discuss/overview/get_started.rst:-1 msgid "View of the messages under the messaging menu emphasizing the request for push\n" -"notifications for Odoo Discuss" +"notifications for Odoo Discuss." msgstr "" -#: ../../content/applications/productivity/discuss/overview/get_started.rst:50 -msgid "To stop receiving desktop notifications, reset the notifications settings of your browser." -msgstr "" - -#: ../../content/applications/productivity/discuss/overview/get_started.rst:52 -msgid "To start a chat, click on *New Message* on the *Messaging Menu*, or go to *Discuss* and send a *Direct Message*." -msgstr "" - -#: ../../content/applications/productivity/discuss/overview/get_started.rst:-1 -msgid "View of discuss’s panel emphasizing the titles channels and direct messages in Odoo Discuss" +#: ../../content/applications/productivity/discuss/overview/get_started.rst:58 +msgid "To stop receiving desktop notifications, reset the notifications settings of the browser." msgstr "" #: ../../content/applications/productivity/discuss/overview/get_started.rst:60 -msgid "You can also create :doc:`public and private channels `." -msgstr "" - -#: ../../content/applications/productivity/discuss/overview/get_started.rst:63 -msgid "Mentions in the chat and on the Chatter" -msgstr "" - -#: ../../content/applications/productivity/discuss/overview/get_started.rst:66 -msgid "To mention a user within a chat or the chatter type *@user-name*; to refer to a channel, type *#channel-name*." -msgstr "" - -#: ../../content/applications/productivity/discuss/overview/get_started.rst:68 -msgid "A notification is sent to the user mentioned either to his *Inbox* or through email, depending on his settings." +msgid "To start a chat, go to the :menuselection:`Discuss` app and click on the :guilabel:`+ (plus)` icon next to :guilabel:`Direct Messages` or :guilabel:`Channels` in the left menu of the dashboard." msgstr "" #: ../../content/applications/productivity/discuss/overview/get_started.rst:-1 -msgid "View of a couple of chat window messages for Odoo Discuss" +msgid "View of Discuss's panel emphasizing the titles channels and direct messages in Odoo\n" +"Discuss." +msgstr "" + +#: ../../content/applications/productivity/discuss/overview/get_started.rst:69 +msgid "A company can also easily create :doc:`public and private channels `." +msgstr "" + +#: ../../content/applications/productivity/discuss/overview/get_started.rst:73 +msgid "Mentions in the chat and on the chatter" msgstr "" #: ../../content/applications/productivity/discuss/overview/get_started.rst:75 -msgid "When a user is mentioned, the search list (list of names) suggests values first based on the task’s followers, and secondly on *Employees*. If the record being searched does not match with either a follower or employee, the scope of the search becomes all partners." +msgid "To mention a user within a chat or the chatter, type `@user-name`; to refer to a channel, type `#channel-name`. The user mentioned will be notified in their *inbox* or through an email, depending on their communication settings." msgstr "" -#: ../../content/applications/productivity/discuss/overview/get_started.rst:80 -msgid "Chat status" +#: ../../content/applications/productivity/discuss/overview/get_started.rst:-1 +msgid "View of a couple of chat window messages for Odoo Discuss." msgstr "" -#: ../../content/applications/productivity/discuss/overview/get_started.rst:82 -msgid "It is helpful to see what colleagues are up to and how quickly they can respond to messages by checking their *Status*. The status is shown on the left side of a contact’s names on Discuss’ sidebar and on the *Messaging menu*." -msgstr "" - -#: ../../content/applications/productivity/discuss/overview/get_started.rst:86 -msgid "Green = online" -msgstr "" - -#: ../../content/applications/productivity/discuss/overview/get_started.rst:87 -msgid "Orange = away" -msgstr "" - -#: ../../content/applications/productivity/discuss/overview/get_started.rst:88 -msgid "White = offline" +#: ../../content/applications/productivity/discuss/overview/get_started.rst:84 +msgid "When a user is mentioned, the search list (list of names) suggests values first based on the task's followers, and secondly on employees. If the record being searched does not match with either a follower or employee, the scope of the search becomes all partners." msgstr "" #: ../../content/applications/productivity/discuss/overview/get_started.rst:89 +msgid "User status" +msgstr "" + +#: ../../content/applications/productivity/discuss/overview/get_started.rst:91 +msgid "It is helpful to see what colleagues are up to and how quickly they can respond to messages by checking their *status*. The status is shown on the left side of a contact's name on the :guilabel:`Discuss` sidebar, on the *messaging menu* and when listed in the *chatter*." +msgstr "" + +#: ../../content/applications/productivity/discuss/overview/get_started.rst:95 +msgid "Green = online" +msgstr "" + +#: ../../content/applications/productivity/discuss/overview/get_started.rst:96 +msgid "Orange = away" +msgstr "" + +#: ../../content/applications/productivity/discuss/overview/get_started.rst:97 +msgid "White = offline" +msgstr "" + +#: ../../content/applications/productivity/discuss/overview/get_started.rst:98 msgid "Airplane = out of the office" msgstr "" #: ../../content/applications/productivity/discuss/overview/get_started.rst:-1 -msgid "View of the contacts’ status for Odoo Discuss" +msgid "View of the contacts' status for Odoo Discuss." msgstr "" -#: ../../content/applications/productivity/discuss/overview/get_started.rst:97 -#: ../../content/applications/productivity/discuss/overview/plan_activities.rst:250 -msgid ":doc:`team_communication`" +#: ../../content/applications/productivity/discuss/overview/get_started.rst:106 +msgid ":doc:`/applications/productivity/discuss/overview/team_communication`" msgstr "" -#: ../../content/applications/productivity/discuss/overview/get_started.rst:98 -msgid ":doc:`/applications/general/email_communication/email_servers`" +#: ../../content/applications/productivity/discuss/overview/get_started.rst:107 +msgid ":doc:`/applications/productivity/discuss/overview/plan_activities`" msgstr "" #: ../../content/applications/productivity/discuss/overview/plan_activities.rst:3 @@ -928,6 +924,10 @@ msgstr "" msgid ":doc:`get_started`" msgstr "" +#: ../../content/applications/productivity/discuss/overview/plan_activities.rst:250 +msgid ":doc:`team_communication`" +msgstr "" + #: ../../content/applications/productivity/discuss/overview/team_communication.rst:3 msgid "Use channels for team communication" msgstr "" diff --git a/locale/sources/sales.pot b/locale/sources/sales.pot index caeb047de..391cb9f8d 100644 --- a/locale/sources/sales.pot +++ b/locale/sources/sales.pot @@ -8,7 +8,7 @@ msgid "" msgstr "" "Project-Id-Version: Odoo saas-16.1\n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2023-12-19 13:26+0000\n" +"POT-Creation-Date: 2024-01-19 10:30+0000\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME \n" "Language-Team: LANGUAGE \n" @@ -42,14 +42,10 @@ msgid "Convert leads into opportunities" msgstr "" #: ../../content/applications/sales/crm/acquire_leads/convert.rst:5 -msgid "The system can generate leads instead of opportunities, in order to add a qualification step before converting a *Lead* into an *Opportunity* and assigning to the right sales people." +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." msgstr "" #: ../../content/applications/sales/crm/acquire_leads/convert.rst:9 -msgid "You can activate this mode from the CRM Settings. It applies to all your sales channels by default. But you can make it specific for specific channels from their configuration form." -msgstr "" - -#: ../../content/applications/sales/crm/acquire_leads/convert.rst:14 #: ../../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 @@ -76,56 +72,132 @@ msgstr "" #: ../../content/applications/sales/point_of_sale/shop/barcode.rst:10 #: ../../content/applications/sales/rental.rst:20 #: ../../content/applications/sales/sales/invoicing/proforma.rst:14 -#: ../../content/applications/sales/sales/products_prices/products/product_images.rst:13 -#: ../../content/applications/sales/sales/products_prices/products/variants.rst:23 +#: ../../content/applications/sales/sales/products_prices/products/product_images.rst:14 +#: ../../content/applications/sales/sales/products_prices/products/variants.rst:34 #: ../../content/applications/sales/sales/send_quotations/quote_template.rst:14 #: ../../content/applications/sales/subscriptions/closing.rst:31 #: ../../content/applications/sales/subscriptions/upselling.rst:25 msgid "Configuration" msgstr "" -#: ../../content/applications/sales/crm/acquire_leads/convert.rst:16 -msgid "For this feature to work, go to :menuselection:`CRM --> Configuration --> Settings` and activate the *Leads* feature." +#: ../../content/applications/sales/crm/acquire_leads/convert.rst:11 +msgid "To activate the *Leads* setting, navigate to :menuselection:`CRM app --> Configuration --> Settings` and check the box labeled, :guilabel:`Leads`. Then, click :guilabel:`Save`." msgstr "" -#: ../../content/applications/sales/crm/acquire_leads/convert.rst:22 -msgid "You will now have a new submenu *Leads* under *Leads* where they will aggregate." +#: ../../content/applications/sales/crm/acquire_leads/convert.rst:-1 +msgid "Leads setting on CRM configuration page." msgstr "" -#: ../../content/applications/sales/crm/acquire_leads/convert.rst:29 +#: ../../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." +msgstr "" + +#: ../../content/applications/sales/crm/acquire_leads/convert.rst:-1 +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`." +msgstr "" + +#: ../../content/applications/sales/crm/acquire_leads/convert.rst:35 msgid "Convert a lead into an opportunity" msgstr "" -#: ../../content/applications/sales/crm/acquire_leads/convert.rst:31 -msgid "When you click on a *Lead* you will have the option to convert it to an opportunity and decide if it should still be assigned to the same channel/person and if you need to create a new customer." +#: ../../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." msgstr "" -#: ../../content/applications/sales/crm/acquire_leads/convert.rst:38 -msgid "If you already have an opportunity with that customer Odoo will automatically offer you to merge with that opportunity. In the same manner, Odoo will automatically offer you to link to an existing customer if that customer already exists." +#: ../../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." msgstr "" -#: ../../content/applications/sales/crm/acquire_leads/convert.rst:44 -msgid "Merge opportunities" +#: ../../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:46 -msgid "Odoo will also automatically propose to merge opportunities if they have the same email address. When merging opportunities, Odoo merges the information into the opportunity which was created first, giving priority to the information present on the first opportunity." +#: ../../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 "No information is lost: data from the other opportunity is logged in the chatter and the information fields for easy access." +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:57 -msgid "Would you find a duplicate yourself, ...you can also merge opportunities or leads even if the system doesn't propose it." +#: ../../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." msgstr "" -#: ../../content/applications/sales/crm/acquire_leads/convert.rst:60 -msgid "Here’s how, from the list view. Select the opportunities or leads you want to merge and the action button will appear. Then, you can select merge." +#: ../../content/applications/sales/crm/acquire_leads/convert.rst:59 +msgid "If the lead has already been assigned to a salesperson or a team, these fields automatically populate with that information." msgstr "" -#: ../../content/applications/sales/crm/acquire_leads/convert.rst:67 -msgid "It is also possible to merge more than 2 opportunities or leads." +#: ../../content/applications/sales/crm/acquire_leads/convert.rst:-1 +msgid "Create opportunity pop-up." +msgstr "" + +#: ../../content/applications/sales/crm/acquire_leads/convert.rst:66 +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." +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." +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." +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." +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." msgstr "" #: ../../content/applications/sales/crm/acquire_leads/generate_leads.rst:3 @@ -3808,269 +3880,367 @@ msgid "Amazon Connector" msgstr "" #: ../../content/applications/sales/sales/amazon_connector/features.rst:3 -msgid "Amazon Connector Features" +msgid "Amazon Connector features" msgstr "" #: ../../content/applications/sales/sales/amazon_connector/features.rst:5 -msgid "The **Amazon Connector** synchronizes the orders between Amazon and your Odoo database, which reduces considerably the amount of time spent on your Amazon Seller Central dashboard, making your daily routine a lot easier." +msgid "The *Amazon Connector* synchronizes orders between Amazon and Odoo, which considerably reduces the amount of time spent manually entering Amazon orders (from the Amazon Seller account) into Odoo. It also allows users to accurately keep track of Amazon sales in Odoo." msgstr "" #: ../../content/applications/sales/sales/amazon_connector/features.rst:10 -msgid "Supported Features" +msgid "Supported features" msgstr "" #: ../../content/applications/sales/sales/amazon_connector/features.rst:12 -msgid "The connector is able to:" +msgid "The Amazon Connector is able to:" msgstr "" #: ../../content/applications/sales/sales/amazon_connector/features.rst:14 -msgid "Synchronize (Amazon to Odoo) all confirmed orders (both FBA and FBM) and their order items which include:" +msgid "Synchronize (Amazon to Odoo) all confirmed orders (both FBA and FBM), and their order items, which include:" msgstr "" #: ../../content/applications/sales/sales/amazon_connector/features.rst:17 -msgid "the product’s name, description and quantity" +msgid "product name, description, and quantity" msgstr "" #: ../../content/applications/sales/sales/amazon_connector/features.rst:18 -msgid "the shipping costs for the product" +msgid "shipping costs for the product" msgstr "" #: ../../content/applications/sales/sales/amazon_connector/features.rst:19 -msgid "the gift wrapping charges" +msgid "gift wrapping charges" msgstr "" #: ../../content/applications/sales/sales/amazon_connector/features.rst:21 -msgid "Create on Odoo any missing partner related to an order (contact types supported: contact and delivery)." +msgid "Create any missing partner related to an order in Odoo (contact types supported: contact and delivery address)." msgstr "" -#: ../../content/applications/sales/sales/amazon_connector/features.rst:23 -msgid "Notify Amazon of a shipping confirmed on Odoo (FBM) in order to get paid." -msgstr "" - -#: ../../content/applications/sales/sales/amazon_connector/features.rst:25 -msgid "Support multiple seller accounts." +#: ../../content/applications/sales/sales/amazon_connector/features.rst:24 +msgid "Notify Amazon of confirmed shipment in Odoo (FBM) to get paid." msgstr "" #: ../../content/applications/sales/sales/amazon_connector/features.rst:26 +msgid "Support multiple seller accounts." +msgstr "" + +#: ../../content/applications/sales/sales/amazon_connector/features.rst:28 msgid "Support multiple marketplaces per seller account." msgstr "" -#: ../../content/applications/sales/sales/amazon_connector/features.rst:29 +#: ../../content/applications/sales/sales/amazon_connector/features.rst:30 +msgid "The following table lists capabilities provided by Odoo when using the Amazon Connector:" +msgstr "" + +#: ../../content/applications/sales/sales/amazon_connector/features.rst:33 msgid "Fulfilled By Amazon (FBA)" msgstr "" -#: ../../content/applications/sales/sales/amazon_connector/features.rst:29 +#: ../../content/applications/sales/sales/amazon_connector/features.rst:33 msgid "Fulfilled By Merchant (FBM)" msgstr "" -#: ../../content/applications/sales/sales/amazon_connector/features.rst:31 +#: ../../content/applications/sales/sales/amazon_connector/features.rst:35 msgid "**Orders**" msgstr "" -#: ../../content/applications/sales/sales/amazon_connector/features.rst:31 -msgid "Synchronize shipped and canceled orders" -msgstr "" - -#: ../../content/applications/sales/sales/amazon_connector/features.rst:31 -msgid "Synchronize unshipped and canceled orders" -msgstr "" - -#: ../../content/applications/sales/sales/amazon_connector/features.rst:34 -msgid "**Shipping**" -msgstr "" - -#: ../../content/applications/sales/sales/amazon_connector/features.rst:34 -msgid "Charges" +#: ../../content/applications/sales/sales/amazon_connector/features.rst:35 +msgid "Synchronize shipped and canceled orders." msgstr "" #: ../../content/applications/sales/sales/amazon_connector/features.rst:35 -msgid "Delivery created" -msgstr "" - -#: ../../content/applications/sales/sales/amazon_connector/features.rst:37 -msgid "**Gift Wrapping**" -msgstr "" - -#: ../../content/applications/sales/sales/amazon_connector/features.rst:37 -#: ../../content/applications/sales/sales/amazon_connector/features.rst:43 -msgid "Handled by Amazon" -msgstr "" - -#: ../../content/applications/sales/sales/amazon_connector/features.rst:37 -msgid "Gift wrapping charges" +msgid "Synchronize unshipped and canceled orders." msgstr "" #: ../../content/applications/sales/sales/amazon_connector/features.rst:38 -msgid "Gift message" +msgid "**Shipping**" msgstr "" -#: ../../content/applications/sales/sales/amazon_connector/features.rst:40 -msgid "**Stock Management**" +#: ../../content/applications/sales/sales/amazon_connector/features.rst:38 +msgid "Shipping cost is computed by Amazon, and included in the synchronized order." msgstr "" -#: ../../content/applications/sales/sales/amazon_connector/features.rst:40 -msgid "One stock move created per sales order item" +#: ../../content/applications/sales/sales/amazon_connector/features.rst:38 +msgid "Shipping cost is computed by Amazon and included in the synchronized orders." msgstr "" -#: ../../content/applications/sales/sales/amazon_connector/features.rst:40 -msgid "Handled by the delivery" +#: ../../content/applications/sales/sales/amazon_connector/features.rst:42 +msgid "Shipping done by Amazon." msgstr "" -#: ../../content/applications/sales/sales/amazon_connector/features.rst:43 -msgid "**Confirmation**" -msgstr "" - -#: ../../content/applications/sales/sales/amazon_connector/features.rst:43 -msgid "Notify Amazon when confirming delivery" +#: ../../content/applications/sales/sales/amazon_connector/features.rst:42 +msgid "A delivery order is automatically created in Odoo for each new order. Once it has been processed in Odoo, the status is then synchronized in Amazon." msgstr "" #: ../../content/applications/sales/sales/amazon_connector/features.rst:48 -msgid "The connector is designed to synchronize orders' data as detailed above. Other actions, such as downloading monthly fees reports, handling disputes, or issuing refunds must be managed from Amazon Seller Central, as usual." +msgid "**Gift Wrapping**" msgstr "" -#: ../../content/applications/sales/sales/amazon_connector/features.rst:55 -msgid "Supported Marketplaces" +#: ../../content/applications/sales/sales/amazon_connector/features.rst:48 +#: ../../content/applications/sales/sales/amazon_connector/features.rst:59 +msgid "Handled by Amazon." msgstr "" -#: ../../content/applications/sales/sales/amazon_connector/features.rst:57 -msgid "The Amazon Connector supports all the current marketplaces. If a marketplace is not listed in your Amazon marketplaces, you can :ref:`add a new marketplace `." +#: ../../content/applications/sales/sales/amazon_connector/features.rst:48 +msgid "Cost is computed by Amazon, and included in the synchronized order. Gift message is added on a line of the order and on the delivery order. Then it is up to the user." msgstr "" -#: ../../content/applications/sales/sales/amazon_connector/features.rst:63 -#: ../../content/applications/sales/sales/amazon_connector/manage.rst:132 -msgid ":doc:`setup`" +#: ../../content/applications/sales/sales/amazon_connector/features.rst:54 +msgid "**Stock Management**" +msgstr "" + +#: ../../content/applications/sales/sales/amazon_connector/features.rst:54 +msgid "Managed by Amazon, and synchronized with a virtual location to follow it in Odoo." +msgstr "" + +#: ../../content/applications/sales/sales/amazon_connector/features.rst:54 +msgid "Managed in Odoo Inventory app, and synchronized with Amazon." +msgstr "" + +#: ../../content/applications/sales/sales/amazon_connector/features.rst:59 +msgid "**Delivery Notifications**" +msgstr "" + +#: ../../content/applications/sales/sales/amazon_connector/features.rst:59 +msgid "Send by Amazon, based on delivery status synchronized from Odoo." msgstr "" #: ../../content/applications/sales/sales/amazon_connector/features.rst:64 +msgid "The Amazon Connector is designed to synchronize the data of sales orders. Other actions, such as downloading monthly fees reports, handling disputes, or issuing refunds, **must** be managed from the *Amazon Seller Central*, as usual." +msgstr "" + +#: ../../content/applications/sales/sales/amazon_connector/features.rst:71 +msgid "Supported marketplaces" +msgstr "" + +#: ../../content/applications/sales/sales/amazon_connector/features.rst:73 +msgid "The Amazon Connector supports all the current marketplaces." +msgstr "" + +#: ../../content/applications/sales/sales/amazon_connector/features.rst:75 +msgid "If a marketplace is not listed in your Amazon marketplaces, it's possible to :ref:`add a new marketplace `." +msgstr "" + +#: ../../content/applications/sales/sales/amazon_connector/features.rst:79 +#: ../../content/applications/sales/sales/amazon_connector/manage.rst:175 +#: ../../content/applications/sales/sales/ebay_connector/linking_listings.rst:16 +#: ../../content/applications/sales/sales/ebay_connector/manage.rst:30 +#: ../../content/applications/sales/sales/ebay_connector/troubleshooting.rst:8 +msgid ":doc:`setup`" +msgstr "" + +#: ../../content/applications/sales/sales/amazon_connector/features.rst:80 #: ../../content/applications/sales/sales/amazon_connector/setup.rst:155 +#: ../../content/applications/sales/sales/ebay_connector/linking_listings.rst:17 +#: ../../content/applications/sales/sales/ebay_connector/setup.rst:17 +#: ../../content/applications/sales/sales/ebay_connector/troubleshooting.rst:9 msgid ":doc:`manage`" msgstr "" #: ../../content/applications/sales/sales/amazon_connector/manage.rst:3 -msgid "Manage Amazon orders in Odoo" +msgid "Amazon order management" msgstr "" #: ../../content/applications/sales/sales/amazon_connector/manage.rst:6 -msgid "Synchronization of orders" +msgid "Order synchronization" msgstr "" #: ../../content/applications/sales/sales/amazon_connector/manage.rst:8 -msgid "Orders are automatically fetched from Amazon and synchronized in Odoo at regular intervals. The synchronization is based on the Amazon status: only orders whose status has changed since the last synchronization are fetched from Amazon. For **FBA** (Fulfilled by Amazon), only **Shipped** and **Canceled** orders are fetched. For **FBM** (Fulfilled by Merchant), the same is done for **Unshipped** and **Canceled** orders. For each synchronized order, a sales order and a customer are created in Odoo if they are not yet registered." +msgid "Orders are automatically fetched from Amazon, and synchronized in Odoo, at regular intervals." +msgstr "" + +#: ../../content/applications/sales/sales/amazon_connector/manage.rst:10 +msgid "The synchronization is based on the Amazon status: only orders whose status has changed since the last synchronization are fetched from Amazon. This includes changes on either end (Amazon or Odoo)." +msgstr "" + +#: ../../content/applications/sales/sales/amazon_connector/manage.rst:13 +msgid "For *FBA* (Fulfilled by Amazon), only *Shipped* and *Canceled* orders are fetched." msgstr "" #: ../../content/applications/sales/sales/amazon_connector/manage.rst:15 -msgid "When an order is canceled in Amazon and was already synchronized in Odoo, the corresponding sales order is automatically canceled in Odoo." +msgid "For *FBM* (Fulfilled by Merchant), the same is done for *Unshipped* and *Canceled* orders. For each synchronized order, a sales order and customer are created in Odoo (if the customer is not already registered in the database)." msgstr "" -#: ../../content/applications/sales/sales/amazon_connector/manage.rst:19 -msgid "To force the synchronization of an order whose status has not changed since the last synchronization, activate the :ref:`developer mode `, navigate to your Amazon account and modify the date under :menuselection:`Orders Follow-up --> Last Order Sync`. Pick a date anterior to the last status change of the order that you wish to synchronize and save." +#: ../../content/applications/sales/sales/amazon_connector/manage.rst:20 +msgid "When an order is canceled in Amazon, and was already synchronized in Odoo, the corresponding sales order is automatically canceled in Odoo." msgstr "" -#: ../../content/applications/sales/sales/amazon_connector/manage.rst:25 -msgid "To synchronize immediately the orders of your Amazon account switch to :ref:`developer mode `, head to your Amazon account and click on **SYNC ORDERS**. The same can be done with pickings by clicking on **SYNC PICKINGS**." +#: ../../content/applications/sales/sales/amazon_connector/manage.rst:24 +msgid "Force synchronization" +msgstr "" + +#: ../../content/applications/sales/sales/amazon_connector/manage.rst:26 +msgid "In order to force the synchronization of an order, whose status has **not** changed since the previous synchronization, start by activating the :ref:`developer mode `. This includes changes on either end (Amazon or Odoo)." msgstr "" #: ../../content/applications/sales/sales/amazon_connector/manage.rst:30 +msgid "Then, navigate to the Amazon account in Odoo (:menuselection:`Sales app --> Configuration --> Settings --> Connectors --> Amazon Sync --> Amazon Accounts`), and modify the date under :menuselection:`Orders Follow-up --> Last Order Sync`." +msgstr "" + +#: ../../content/applications/sales/sales/amazon_connector/manage.rst:34 +msgid "Be sure to pick a date that occurs prior to the last status change of the desired order to synchronize and save. This will ensure synchronization occurs correctly." +msgstr "" + +#: ../../content/applications/sales/sales/amazon_connector/manage.rst:39 +msgid "To immediately synchronize the orders of an Amazon account, switch to :ref:`developer mode `, head to the Amazon account in Odoo, and click :guilabel:`Sync Orders`. The same can be done with pickings by clicking :guilabel:`Sync Pickings`." +msgstr "" + +#: ../../content/applications/sales/sales/amazon_connector/manage.rst:44 msgid "Manage deliveries in FBM" msgstr "" -#: ../../content/applications/sales/sales/amazon_connector/manage.rst:32 -msgid "When a **FBM** (Fulfilled by Merchant) order is synchronized in Odoo, a picking is created along with the sales order and the customer. You can either ship all the ordered products to your customer at once or ship products partially by using backorders." -msgstr "" - -#: ../../content/applications/sales/sales/amazon_connector/manage.rst:36 -msgid "When a picking related to the order is confirmed, a notification is sent to Amazon who will, in turn, notify the customer that the order (or a part of it) is on its way." -msgstr "" - -#: ../../content/applications/sales/sales/amazon_connector/manage.rst:40 -msgid "Amazon requires to provide a tracking reference with each delivery. You'll need to assign a carrier. If the carrier doesn't automatically provide a tracking reference, you'll need to set one manually. This concerns all marketplaces." -msgstr "" - -#: ../../content/applications/sales/sales/amazon_connector/manage.rst:45 -msgid "If your chosen carrier isn't one supported by Odoo, you can still create a carrier bearing its name (e.g. create a carrier named `Colissimo`). This name is case insensitive, but be careful about typos, as Amazon won't recognize them." -msgstr "" - -#: ../../content/applications/sales/sales/amazon_connector/manage.rst:48 -msgid "Create a delivery carrier named `Self Delivery` to inform Amazon that you make your own deliveries. You still have to enter a tracking reference." +#: ../../content/applications/sales/sales/amazon_connector/manage.rst:46 +msgid "Whenever an FBM (Fulfilled by Merchant) order is synchronized in Odoo, a picking is instantly created in the *Inventory* app, along with a sales order and customer record. Then, decide to either ship all the ordered products to the customer at once, or ship products partially using backorders." msgstr "" #: ../../content/applications/sales/sales/amazon_connector/manage.rst:50 -msgid "Keep in mind that the customer is notified by email about the delivery, and the carrier and tracking reference are displayed in the email to the customer." +msgid "When a picking related to the order is confirmed, a notification is then sent to Amazon, who, in turn, notifies the customer that the order (or a part of it) is on its way." msgstr "" #: ../../content/applications/sales/sales/amazon_connector/manage.rst:54 -msgid ":doc:`/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/third_party_shipper`" +msgid "Amazon requires users to provide a tracking reference with each delivery. This is needed to assign a carrier." msgstr "" #: ../../content/applications/sales/sales/amazon_connector/manage.rst:57 +msgid "If the carrier doesn't automatically provide a tracking reference, one must be set manually. This rule applies to all Amazon marketplaces." +msgstr "" + +#: ../../content/applications/sales/sales/amazon_connector/manage.rst:61 +msgid "If the chosen carrier isn't supported by Odoo, a carrier with the same name can still be created (e.g. create a carrier named `easyship`). The name used is **not** case sensitive, but be mindful to avoid typos. If there are typos, Amazon will **not** recognize them. Next, create a delivery carrier named `Self Delivery` to inform Amazon that the user will make the deliveries. Even with this route, a tracking reference still **must** be entered. Remember, the customer is notified by email about the delivery, and the carrier, along with the tracking reference, are displayed in the email to the customer." +msgstr "" + +#: ../../content/applications/sales/sales/amazon_connector/manage.rst:70 +msgid ":doc:`../../../inventory_and_mrp/inventory/shipping_receiving/setup_configuration/third_party_shipper`" +msgstr "" + +#: ../../content/applications/sales/sales/amazon_connector/manage.rst:73 msgid "Follow deliveries in FBA" msgstr "" -#: ../../content/applications/sales/sales/amazon_connector/manage.rst:59 -msgid "When a **FBA** (Fulfilled by Amazon) order is synchronized in Odoo, a stock move is recorded for each sales order item so that it is saved in your system. Inventory managers can find such moves in :menuselection:`Inventory --> Reporting --> Product Moves`. They pick up products in a specific inventory location called **Amazon**. This location represents your stock in Amazon's warehouses and allows you to manage the stock of your products under the FBA program." +#: ../../content/applications/sales/sales/amazon_connector/manage.rst:75 +msgid "When an FBA (Fulfilled by Amazon) order is synchronized in Odoo, a stock move is recorded in the *Inventory* app for each sales order item. That way, it's saved in the system." msgstr "" -#: ../../content/applications/sales/sales/amazon_connector/manage.rst:66 -msgid "To follow your Amazon (FBA) stock in Odoo, you can make an inventory adjustment after replenishing it. You can also trigger an automated replenishment from reordering rules on the Amazon location." +#: ../../content/applications/sales/sales/amazon_connector/manage.rst:78 +msgid "Inventory managers can access these stock moves by navigating to :menuselection:`Inventory app --> Reporting --> Moves History`." msgstr "" -#: ../../content/applications/sales/sales/amazon_connector/manage.rst:71 -msgid "The Amazon location is configurable by Amazon account managed in Odoo. All accounts of the same company use the same location by default. It is however possible to follow the stock by marketplace. First, remove the marketplace for which you want to follow the stock separately from the list of synchronized marketplaces. Then, create another registration for this account and remove all marketplaces, except the one to isolate from the others. Finally, assign another stock location to the second registration of your account." +#: ../../content/applications/sales/sales/amazon_connector/manage.rst:81 +msgid "For FBA orders, the stock move is automatically created in Odoo by the Amazon connector, thanks to the shipping status of Amazon. When sending new products to Amazon, the user should manually create a picking (delivery order) to transfer these products from their warehouse to the Amazon location." msgstr "" -#: ../../content/applications/sales/sales/amazon_connector/manage.rst:79 -msgid "Issue invoices and register payments" +#: ../../content/applications/sales/sales/amazon_connector/manage.rst:86 +msgid "To follow *Amazon (FBA)* stock in Odoo, make an inventory adjustment after replenishing stock. An automated replenishment from reordering rules can also be triggered on the Amazon location." msgstr "" -#: ../../content/applications/sales/sales/amazon_connector/manage.rst:82 +#: ../../content/applications/sales/sales/amazon_connector/manage.rst:89 +msgid "The Amazon location is configurable by accessing the Amazon account managed in Odoo. To access Amazon accounts in Odoo navigate to :menuselection:`Sales app --> Configuration --> Settings --> Connectors --> Amazon Sync --> Amazon Accounts`." +msgstr "" + +#: ../../content/applications/sales/sales/amazon_connector/manage.rst:93 +msgid "All accounts of the same company use the same Amazon location, by default. However, it is possible to follow the stock filtered by marketplace." +msgstr "" + +#: ../../content/applications/sales/sales/amazon_connector/manage.rst:96 +msgid "To do that, first remove the marketplace, where the desired stock to follow separately can be found, from the list of synchronized marketplaces, which can be found by navigating to :menuselection:`Sales app --> Configuration --> Settings --> Connectors --> Amazon Sync --> Amazon Accounts`." +msgstr "" + +#: ../../content/applications/sales/sales/amazon_connector/manage.rst:101 +msgid "Next, create another registration for this account, and remove all marketplaces--- **except** the marketplace this is desired to be isolated from the others." +msgstr "" + +#: ../../content/applications/sales/sales/amazon_connector/manage.rst:104 +msgid "Lastly, assign another stock location to the second registration of the account." +msgstr "" + +#: ../../content/applications/sales/sales/amazon_connector/manage.rst:107 +msgid "Invoice and register payments" +msgstr "" + +#: ../../content/applications/sales/sales/amazon_connector/manage.rst:110 msgid "Issue invoices" msgstr "" -#: ../../content/applications/sales/sales/amazon_connector/manage.rst:84 -msgid "Sending invoices to Amazon customers directly from Odoo is not feasible due to Amazon's policy of not sharing customer email addresses. Instead, it is possible to manually upload the invoices generated on Odoo to the Amazon backend." -msgstr "" - -#: ../../content/applications/sales/sales/amazon_connector/manage.rst:88 -msgid "In addition, for your B2B clients, it is currently required to manually retrieve VAT numbers from the Amazon backend before creating the invoice in Odoo." -msgstr "" - -#: ../../content/applications/sales/sales/amazon_connector/manage.rst:92 -msgid "For :doc:`TaxCloud <../../../finance/accounting/taxes/taxcloud>` users: invoices created from Amazon sales orders are **not** synchronized with TaxCloud, since Amazon already includes them in its own tax report to TaxCloud. (decommissioning TaxCloud integration in Odoo 17+)" -msgstr "" - -#: ../../content/applications/sales/sales/amazon_connector/manage.rst:97 -msgid "Register payments" -msgstr "" - -#: ../../content/applications/sales/sales/amazon_connector/manage.rst:99 -msgid "As customers pay Amazon as an intermediary, creating a dedicated *Bank* journal (for example, named `Amazon payments`) with a dedicated *Bank and Cash* intermediary account is recommended." -msgstr "" - -#: ../../content/applications/sales/sales/amazon_connector/manage.rst:102 -msgid "In addition, as Amazon makes a single monthly payment, selecting all the invoices linked to a single payment is necessary when registering payments. Use the dedicated `Amazon payments` :guilabel:`Journal` and select :guilabel:`Batch Deposit` as the :guilabel:`Payment Method`. Then, select all the payments generated and click :menuselection:`Actions --> Create batch payment --> Validate`." -msgstr "" - -#: ../../content/applications/sales/sales/amazon_connector/manage.rst:109 -msgid "The same can be done with vendor bills from Amazon dedicated to commissions. When the balance is received in the bank account at the end of the month and the banks statements are recorded, credit the Amazon intermediary account by the amount received." -msgstr "" - -#: ../../content/applications/sales/sales/amazon_connector/manage.rst:114 -msgid "Follow your Amazon sales in sales reporting" +#: ../../content/applications/sales/sales/amazon_connector/manage.rst:112 +msgid "Due to Amazon's policy of not sharing customer email addresses, it is **not** possible to send invoices directly to Amazon customers from Odoo. However, it **is** possible to manually upload the generated invoices from Odoo to the Amazon back-end." msgstr "" #: ../../content/applications/sales/sales/amazon_connector/manage.rst:116 -msgid "As a sales team is set on your account under the tab **Order Follow-up**, this helps you give quick glances at the figures in just a few clicks in Sales reporting. By default, your account's sales team is shared between all of your company's accounts." +msgid "Additionally, for B2B clients, it is currently required to manually retrieve VAT numbers from the Amazon back-end **before** creating an invoice in Odoo." msgstr "" #: ../../content/applications/sales/sales/amazon_connector/manage.rst:120 -msgid "If you wish, you can change the sales team on your account for another to perform a separate reporting for the sales of this account." +msgid "For :doc:`TaxCloud <../../../finance/accounting/taxes/taxcloud>` users: invoices created from Amazon sales orders are **not** synchronized with TaxCloud, since Amazon already includes them in its own tax report to TaxCloud." msgstr "" -#: ../../content/applications/sales/sales/amazon_connector/manage.rst:124 -msgid "It is also possible to perform reporting on a per-marketplace basis in a similar fashion. First, remove the marketplace you wish to track separately from the list of synchronized marketplaces. Then, create another registration for this account and remove all marketplaces, except the one to isolate from the others. Finally, assign another sales team to one of the two registrations of your account." +#: ../../content/applications/sales/sales/amazon_connector/manage.rst:125 +msgid "TaxCloud integration will be decommissioned in Odoo 17+." msgstr "" -#: ../../content/applications/sales/sales/amazon_connector/manage.rst:131 +#: ../../content/applications/sales/sales/amazon_connector/manage.rst:128 +msgid "Register payments" +msgstr "" + +#: ../../content/applications/sales/sales/amazon_connector/manage.rst:130 +msgid "Since customers pay Amazon as an intermediary, creating a dedicated *Bank* journal (e.g. named `Amazon Payments`), with a dedicated *Bank and Cash* intermediary account is recommended." +msgstr "" + +#: ../../content/applications/sales/sales/amazon_connector/manage.rst:133 +msgid "Additionally, as Amazon makes a single monthly payment, selecting all the invoices linked to a single payment is necessary when registering payments." +msgstr "" + +#: ../../content/applications/sales/sales/amazon_connector/manage.rst:136 +msgid "To do that, use the appropriate :guilabel:`Journal` dedicated to Amazon payments, and select :guilabel:`Batch Deposit` as the :guilabel:`Payment Method`." +msgstr "" + +#: ../../content/applications/sales/sales/amazon_connector/manage.rst:139 +msgid "Then, select all the generated payments, and click :menuselection:`Actions --> Create batch payment --> Validate`." +msgstr "" + +#: ../../content/applications/sales/sales/amazon_connector/manage.rst:143 +msgid "This same action can be performed with vendor bills from Amazon dedicated to commissions." +msgstr "" + +#: ../../content/applications/sales/sales/amazon_connector/manage.rst:145 +msgid "When the balance is received in the bank account at the end of the month, and the bank statements are recorded, credit the Amazon intermediary account by the amount received." +msgstr "" + +#: ../../content/applications/sales/sales/amazon_connector/manage.rst:149 +msgid "Follow Amazon sales in sales reporting" +msgstr "" + +#: ../../content/applications/sales/sales/amazon_connector/manage.rst:151 +msgid "On the Amazon account profile in Odoo , a sales team is set under the :guilabel:`Order Follow-up` tab." +msgstr "" + +#: ../../content/applications/sales/sales/amazon_connector/manage.rst:154 +msgid "This gives quick access to important metrics related to sales reporting. By default, the Amazon account's sales team is shared between all of the company's accounts." +msgstr "" + +#: ../../content/applications/sales/sales/amazon_connector/manage.rst:157 +msgid "If desired, the sales team on the account can be changed for another, in order to perform a separate reporting for the sales of this account." +msgstr "" + +#: ../../content/applications/sales/sales/amazon_connector/manage.rst:161 +msgid "It is also possible to perform reporting on a per-marketplace basis." +msgstr "" + +#: ../../content/applications/sales/sales/amazon_connector/manage.rst:163 +msgid "First, remove the desired marketplace from the list of synchronized marketplaces." +msgstr "" + +#: ../../content/applications/sales/sales/amazon_connector/manage.rst:165 +msgid "To access the list of synchronized marketplaces in Odoo, navigate to :menuselection:`Sales app --> Configuration --> Settings --> Connectors --> Amazon Sync --> Amazon Accounts`." +msgstr "" + +#: ../../content/applications/sales/sales/amazon_connector/manage.rst:168 +msgid "Then, create another registration for this account, and remove all other marketplaces **except** the one to isolate." +msgstr "" + +#: ../../content/applications/sales/sales/amazon_connector/manage.rst:171 +msgid "Lastly, assign another sales team to one of the two registrations of the account." +msgstr "" + +#: ../../content/applications/sales/sales/amazon_connector/manage.rst:174 #: ../../content/applications/sales/sales/amazon_connector/setup.rst:154 msgid ":doc:`features`" msgstr "" @@ -4220,7 +4390,6 @@ msgid "All marketplaces are supported by the Amazon Connector. To add a new mark msgstr "" #: ../../content/applications/sales/sales/amazon_connector/setup.rst:131 -#: ../../content/applications/sales/sales/ebay_connector/setup.rst:118 msgid "Activate the :ref:`developer mode `." msgstr "" @@ -4252,208 +4421,974 @@ msgstr "" msgid "eBay Connector" msgstr "" +#: ../../content/applications/sales/sales/ebay_connector/linking_listings.rst:3 +msgid "Linking existing listings" +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/linking_listings.rst:5 +msgid "Once the eBay account is linked existing listings from within the eBay seller account need to be added manually to the Odoo product listings." +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/linking_listings.rst:8 +msgid "The process will be as follows: - Turn off eBay scheduled actions - Add products and link listings - Turn on eBay scheduled actions" +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/linking_listings.rst:14 +#: ../../content/applications/sales/sales/ebay_connector/manage.rst:28 +#: ../../content/applications/sales/sales/ebay_connector/setup.rst:15 +#: ../../content/applications/sales/sales/ebay_connector/troubleshooting.rst:6 +msgid "To learn more about the eBay connector visit these pages as well:" +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/linking_listings.rst:18 +#: ../../content/applications/sales/sales/ebay_connector/manage.rst:32 +#: ../../content/applications/sales/sales/ebay_connector/setup.rst:19 +msgid ":doc:`troubleshooting`" +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/linking_listings.rst:21 +msgid "Turn off eBay scheduled actions" +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/linking_listings.rst:23 +msgid "To start linking existing listings in eBay, first turn off the eBay notifications in the scheduled actions in Odoo. The reason for this is so that no orders or eBay data syncs during this process. The :guilabel:`Scheduled Actions` can be accessed by first activating :ref:`developer mode `. After doing so, go to :menuselection:`Settings --> Technical --> Automation --> Scheduled Actions`." +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/linking_listings.rst:30 +msgid ":doc:`../../../general/developer_mode` must be activated to ensure the technical menu appears for the user." +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/linking_listings.rst:33 +msgid "Disabling scheduled actions enables users to sync and validate eBay data before receiving orders. The following are descriptions of scheduled actions that need to be temporarily deactivated:" +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/linking_listings.rst:36 +msgid ":guilabel:`eBay: get new orders`: eBay pushes new orders not already in Odoo (based on :guilabel:`client_order_reference`, or :guilabel:`sales order reference` field). This command also updates existing orders, where changes we made in eBay. New and updated orders are then placed in draft mode. Customers will be created if they are not already in Odoo." +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/linking_listings.rst:40 +msgid ":guilabel:`eBay: synchronize stock`: eBay displays Odoo's stock on hand." +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/linking_listings.rst:41 +msgid ":guilabel:`eBay: update categories`: eBay will push updated monthly categories (only up to fourth layer; a manual update required for the rest)." +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/linking_listings.rst:44 +msgid "To toggle off the eBay notification, select the entry from the :guilabel:`Scheduled Actions` list. Then, on the page, click the :guilabel:`Active` toggle button to turn it off." +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/linking_listings.rst:48 +msgid "Sync eBay categories" +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/linking_listings.rst:50 +msgid "To ensure that Odoo's eBay products have all the categories available on eBay, the eBay categories should be synced to Odoo next." +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/linking_listings.rst:53 +msgid "Navigate to :menuselection:`Settings --> Technical --> Automation --> Scheduled Actions`. Click into the scheduled action labeled: :guilabel:`Ebay: update categories` and then click :guilabel:`Run Manually`. This action will populate the :menuselection:`Sales --> Configuration --> eBay Categories` menu item with all standard eBay product categories." +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/linking_listings.rst:59 +msgid "Odoo only recognizes eBay category paths up to four layers deep. If a product has a listing of more than four, the category field will only populate up to the fourth layer." +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/linking_listings.rst:62 +msgid "If product categories beyond four paths are required, users need to manually add those paths. This has historically been done by getting a list of all product categories beyond 4 paths, manually importing them into the Product Category model in Odoo, then linking them individually to the product." +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/linking_listings.rst:67 +msgid "Users can import the remaining product categories into the eBay product categories manually using using the :guilabel:`Action` menu and :guilabel:`Import` feature." +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/linking_listings.rst:71 +msgid "Link eBay listings" +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/linking_listings.rst:73 +msgid "To add eBay listings in Odoo, either manually add products, using a listing ID, or establish an automatic listing link between Odoo and eBay." +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/linking_listings.rst:77 +msgid "For more information on listing a product from scratch visit: :ref:`How to list a product? `" +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/linking_listings.rst:81 +msgid "Manual listing link" +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/linking_listings.rst:83 +msgid "To add an eBay listing to products in Odoo, begin by going to :menuselection:`Sales app --> Products --> Products` and selecting the desired product. Click on :guilabel:`Sell on eBay` (either in the :guilabel:`eBay` tab or under the :guilabel:`Product name`). Select :guilabel:`Save` if necessary." +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/linking_listings.rst:87 +msgid "Still the product form, click :guilabel:`link to listing` in the top menu and enter in listing ID from eBay in the pop up (the listing ID is in the eBay product URL)." +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/linking_listings.rst:91 +msgid "An example URL would be as such: `www.ebay.com/itm/272222656444?hash=item3f61bc17bb:g:vJ0AAOSwslJizv8u`. The listing ID is `272222656444` in this case. Once the listing ID has been entered the eBay listing information will sync into Odoo." +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/linking_listings.rst:97 +msgid "Turn on eBay scheduled Actions" +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/linking_listings.rst:99 +msgid "The next step is to turn on the eBay notifications in the scheduled actions in Odoo so that orders and data are exchanged. The :guilabel:`Scheduled Actions` can be accessed by first activating :ref:`developer mode ` and go to :menuselection:`Settings --> Technical --> Automation --> Scheduled Actions`." +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/linking_listings.rst:104 +msgid "Turning on the following scheduled actions allows users to sync and validate eBay data automatically." +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/linking_listings.rst:107 +msgid ":guilabel:`eBay: get new orders`: eBay will push all new orders not already in Odoo (based on client_order_reference, or sales order reference field), and will update orders if there has been a change from eBay. Orders will be put in draft mode. Customers will be created if they are not already in Odoo." +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/linking_listings.rst:111 +msgid ":guilabel:`eBay: synchronize stock`: eBay will display the stock on hand in Odoo." +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/linking_listings.rst:112 +msgid ":guilabel:`eBay: update categories`: eBay will push updated monthly categories (only up to fourth layer, will need to manually update the rest)." +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/linking_listings.rst:116 +msgid "If an order comes in and the listing from the order is not linked to a product, eBay will create a consumable product.product in its place. These consumables should be altered on the *Sales Order* while in draft state to represent a storable product, and then the user can link to the listing as they come in." +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/linking_listings.rst:122 +#: ../../content/applications/sales/sales/ebay_connector/troubleshooting.rst:127 +msgid ":doc:`/applications/sales/sales/ebay_connector/manage`" +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/linking_listings.rst:123 +#: ../../content/applications/sales/sales/ebay_connector/manage.rst:153 +msgid ":doc:`/applications/sales/sales/ebay_connector/troubleshooting`" +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/linking_listings.rst:124 +#: ../../content/applications/sales/sales/ebay_connector/manage.rst:155 +#: ../../content/applications/sales/sales/ebay_connector/troubleshooting.rst:129 +msgid ":doc:`/applications/sales/sales/ebay_connector/setup`" +msgstr "" + #: ../../content/applications/sales/sales/ebay_connector/manage.rst:3 msgid "How to list a product?" msgstr "" -#: ../../content/applications/sales/sales/ebay_connector/manage.rst:6 -msgid "Listing without variation" +#: ../../content/applications/sales/sales/ebay_connector/manage.rst:7 +msgid "In order to list a product on eBay and Odoo there are two methods in Odoo to do so:" msgstr "" -#: ../../content/applications/sales/sales/ebay_connector/manage.rst:8 -msgid "In order to list a product, you need to check the **use eBay** field on a product form. The eBay tab will be available." +#: ../../content/applications/sales/sales/ebay_connector/manage.rst:9 +msgid "Make a product in Odoo and list the item eBay." +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/manage.rst:11 +msgid "Click :guilabel:`List Item on eBay` in the top menu of the product template. The product template can be accessed by navigating to :menuselection:`Sales app --> Products --> Product` and selecting the individual product." msgstr "" #: ../../content/applications/sales/sales/ebay_connector/manage.rst:14 -msgid "When the **Use Stock Quantity** field is checked, the quantity sets on eBay will be the Odoo **Forecast Quantity**." +msgid "List the item on eBay, then create the product in Odoo, and finally link product to the item on eBay." msgstr "" #: ../../content/applications/sales/sales/ebay_connector/manage.rst:17 -msgid "The **Description Template** allows you to use templates for your listings. The default template only use the **eBay Description** field of the product. You can use html inside the **Description Template** and in the **eBay Description**." +msgid "Click :guilabel:`Link With Existing eBay Listing` in the top menu on the product template.The product template can be accessed by navigating to :menuselection:`Sales app --> Product --> Product` and selecting the individual product." msgstr "" -#: ../../content/applications/sales/sales/ebay_connector/manage.rst:21 -msgid "To use pictures in your listing, you need to add them as **Attachments** on the product template." +#: ../../content/applications/sales/sales/ebay_connector/manage.rst:22 +msgid "If an order comes in and the listing from the order is not linked to a product, eBay will create a consumable product.product in its place. These consumables should be altered on the *sales order* while in draft state to represent a storable product, and then the user can link to the listing as they come in." msgstr "" -#: ../../content/applications/sales/sales/ebay_connector/manage.rst:24 -msgid "Listing with variations" -msgstr "" - -#: ../../content/applications/sales/sales/ebay_connector/manage.rst:26 -msgid "When the **use eBay** on a product with variations is checked and with **Fixed Price** as **Listing Type**, the eBay form is slightly different. In the variants array, you can choose which variant will be listed on eBay as well as set the price and the quantity for each variant." +#: ../../content/applications/sales/sales/ebay_connector/manage.rst:31 +#: ../../content/applications/sales/sales/ebay_connector/setup.rst:18 +#: ../../content/applications/sales/sales/ebay_connector/troubleshooting.rst:10 +msgid ":doc:`linking_listings`" msgstr "" #: ../../content/applications/sales/sales/ebay_connector/manage.rst:35 -msgid "Listing with item specifics" +msgid "Listing without variation" msgstr "" #: ../../content/applications/sales/sales/ebay_connector/manage.rst:37 -msgid "In order to add item specifics, you should create a product attribute with one value in the **Variants** tab on the product form." +msgid "Access the product template by navigating to :menuselection:`Sales app --> Products --> Product` and selecting the individual product." msgstr "" -#: ../../content/applications/sales/sales/ebay_connector/manage.rst:44 -msgid "Product Identifiers" +#: ../../content/applications/sales/sales/ebay_connector/manage.rst:40 +msgid "In order to list a product, select the :guilabel:`Sell on eBay` field on a product template. :guilabel:`Sell on eBay` is either in an :guilabel:`eBay` tab or under the :guilabel:`Product name`. Click :guilabel:`Save` if necessary." msgstr "" -#: ../../content/applications/sales/sales/ebay_connector/manage.rst:46 -msgid "Products identifiers such as EAN, UPC, Brand or MPN are required in most of the eBay category. The module manages the EAN and UPC identifiers with the **Barcode** field of the product variant. If the **Barcode** field is empty or is value is not valid, the EAN and UPC values will be set as 'Does not apply' as recommended by eBay. The Brand and MPN values are working as item specifics and should be define in the **Variants** tab on the product form. If these values are not set, 'Does not apply' will be used for the eBay listing." +#: ../../content/applications/sales/sales/ebay_connector/manage.rst:-1 +msgid "The eBay template form listed in the product template in Odoo." +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/manage.rst:48 +msgid "When the :guilabel:`Use Stock Quantity` field is checked, the quantity set on eBay will be the Odoo *Forecast Quantity* (Odoo *Inventory* app)." +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/manage.rst:51 +msgid "The :guilabel:`Description Template` allows the administrator to use templates in listings. The default template only use the :guilabel:`eBay Description` field of the product. HTML can be used inside the :guilabel:`Description Template` and in the :guilabel:`eBay Description` in Odoo 14. Starting in Odoo 15, the powerbox feature is available to use in the template and description. Simply type a forward slash `/` to reveal a menu with formatting, layout, and text options. To add an image, type `/image`." +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/manage.rst:58 +msgid "To use images in the listing, another option is to add them as *Attachments* on the product template." +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/manage.rst:62 +msgid "For more information on template configuration in Odoo visit: :doc:`../../../general/email_communication/email_template`." +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/manage.rst:66 +msgid "Listing with variations" +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/manage.rst:68 +msgid "When the :guilabel:`Sell on eBay` is checked on a product containing variations with :guilabel:`Fixed Price` as :guilabel:`Listing Type`, the eBay form is slightly different. Go to the :guilabel:`Variants` tab to or click :guilabel:`Configure Variants` in the top menu to configure the variant settings. Pricing can be configured for each variation." +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/manage.rst:73 +msgid "When the :guilabel:`Listing Type` is changed to :guilabel:`Fixed Price`, Odoo presents a variant table at the bottom of the :guilabel:`eBay` tab, in which the :guilabel:`Fixed Price` can be entered, and the decision to :guilabel:`Publish on eBay` can be made for specific variants, along with other options." +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/manage.rst:-1 +msgid "The fixed price listing type in the eBay tab on a product form in Odoo sales." +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/manage.rst:83 +msgid "Product identifiers" +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/manage.rst:85 +msgid "Products identifiers such as EAN, UPC, Brand or MPN are required in most of the eBay categories." +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/manage.rst:88 +msgid "EAN and UPC identifiers" +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/manage.rst:90 +msgid "The module manages the EAN and UPC identifiers with the :guilabel:`Barcode` field of the product variant. If the :guilabel:`Barcode` field is empty or is value is not valid, the EAN and UPC values will be set as 'Does not apply' as recommended by eBay." +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/manage.rst:94 +msgid "Barcodes can be found on the product template, under the the :guilabel:`General Information` tab. Access the product template, first, by navigating to :menuselection:`Sales app --> Products --> Product` and selecting the individual product." +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/manage.rst:99 +msgid "Listing with item specifics" +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/manage.rst:101 +msgid "In order to add item specifics, one should create a product attribute with a single value in the :guilabel:`Attributes & Variants` tab on the product form. Examples of item specifics include: `MPN` or `Brand`. The Brand and MPN values are working as item specifics and should be defined in the :guilabel:`Attributes & Variants` tab on the product form. If these values are not set, 'Does not apply' will be used for the eBay listing." +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/manage.rst:108 +msgid "Process invoices and payments" +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/manage.rst:111 +msgid "Posting payment" +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/manage.rst:113 +msgid "When eBay orders are placed they are always paid for up front, via the eBay site. At no point will users pay for items on eBay through Odoo. Therefore, once orders are synced into Odoo from eBay they are already paid for. Odoo's invoicing and payment functionalities are not utilized. However, invoices need to be created and marked as Paid to “close” the *Sales Order*." +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/manage.rst:118 +msgid "Users can opt to mass create and post invoices in batches. To do so, navigate to Quotations in the list view by going to :menuselection:`Sales app --> Orders --> Quotations`. In the upper right corner, select the list view icon. Hover over the icons to reveal the name of each. Then check the boxes on the left that invoices should be made for and go to the :guilabel:`Action` menu or ⚙️ [Gear icon] . Click on :guilabel:`Create Invoices`." +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/manage.rst:124 +msgid "A pop-up will appear and click on the :guilabel:`Create and view invoice` button. A new screen will populate with the newly created invoices. Next, select all of them by clicking on the box icon next to :guilabel:`Number` in the header row of the list, this will select all the records. Then navigate to the :guilabel:`Action` menu and click :guilabel:`Post entries`. Following this step, a pop-up will appear and click on :guilabel:`Post journal entries`. This will take the invoices out of *draft* and set them to *posted*." +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/manage.rst:132 +msgid "Reconciling payments" +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/manage.rst:134 +msgid "Users typically utilize PayPal to receive payment from eBay, and then send lump sums from PayPal into their bank account. To reconcile this income, users can reconcile the one PayPal transfer with all related invoices." +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/manage.rst:138 +msgid "First navigate to the :guilabel:`Accounting Dashboard` by going to the :menuselection:`Accounting app --> Dashboard --> Bank`. :guilabel:`Create` a new transaction and enter the :guilabel:`Label` as `eBay Sales`. Fill out the :guilabel:`Amount` and enter a :guilabel:`Statement` date in. Click on :guilabel:`Create and edit`." +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/manage.rst:143 +msgid "For the :guilabel:`Ending Balance` field, enter the same account that was entered for the :guilabel:`Amount` above. Click on :guilabel:`Save`. Next, open the new balance that needs to be reconciled. Under the tab marked: :guilabel:`Match Existing Entries` select the entries that are included in this balance." +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/manage.rst:148 +msgid "After adding all the necessary entries, click :guilabel:`Validate` to complete the reconciliation. To verify the payment, navigate to :menuselection:`Customers --> Invoices` and select the desired customer invoice. The *Paid* label should appear under the :guilabel:`Payment Status` column." +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/manage.rst:154 +#: ../../content/applications/sales/sales/ebay_connector/troubleshooting.rst:128 +msgid ":doc:`/applications/sales/sales/ebay_connector/linking_listings`" msgstr "" #: ../../content/applications/sales/sales/ebay_connector/setup.rst:3 -msgid "How to configure eBay in Odoo?" +msgid "eBay connector setup" msgstr "" #: ../../content/applications/sales/sales/ebay_connector/setup.rst:6 -msgid "Create eBay tokens" +msgid "Overview" msgstr "" #: ../../content/applications/sales/sales/ebay_connector/setup.rst:8 -msgid "In order to create your tokens, you need to create a developer account on the `developer portal `_. Once you are logged in, you can create **Sandbox Keys** and **Production Keys** by clicking on the adequate buttons." -msgstr "" - -#: ../../content/applications/sales/sales/ebay_connector/setup.rst:16 -msgid "After the creation of the keys, you can get the user token. To do so, click on the **Get a User Token** link in the bottom of the page. Go through the form, log in with you eBay account and you will get the keys and token needed to configure the module in Odoo." +msgid "Odoo's eBay connector allows eBay listings to connect with Odoo products. Once connected, :doc:`updates to the listings ` can be made in Odoo or in eBay. When an item sells on eBay, draft *sales orders* are created in Odoo for the user to review and confirm. Once the sales order is confirmed, Odoo *Inventory* and *Sales* apps function standard to pull products out of inventory, and allow the user to create invoices." msgstr "" #: ../../content/applications/sales/sales/ebay_connector/setup.rst:22 -msgid "Set up tokens in Odoo?" +msgid "eBay - Odoo linked fields" msgstr "" #: ../../content/applications/sales/sales/ebay_connector/setup.rst:24 -msgid "To set up the eBay integration, go to :menuselection:`Sales --> Configuration --> Settings`." +msgid "The following are eBay product details. Each of these eBay fields update corresponding fields in Odoo." +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/setup.rst:27 +msgid "eBay URL" +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/setup.rst:28 +msgid "eBay status" msgstr "" #: ../../content/applications/sales/sales/ebay_connector/setup.rst:29 -msgid "First choose if you want to use the production or the sandbox eBay Site. Then fill in the fields **Developer Key**, **Token**, **App Key**, **Cert Key**. Apply the changes." +msgid "Quantity sold" +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/setup.rst:30 +msgid "Start date" +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/setup.rst:31 +msgid "Title" +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/setup.rst:32 +msgid "Subtitle" msgstr "" #: ../../content/applications/sales/sales/ebay_connector/setup.rst:33 -msgid "Once the page is reloaded, you need to synchronize information from eBay. Push on **Sync countries and currencies**, then you can fill in all the other fields." +msgid "Item condition" +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/setup.rst:34 +msgid "Category" +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/setup.rst:35 +msgid "Category 2" msgstr "" #: ../../content/applications/sales/sales/ebay_connector/setup.rst:36 -msgid "When all the fields are filled in, you can synchronize the categories and the policies by clicking on the adequate buttons." +msgid "Store category" +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/setup.rst:37 +msgid "Store category 2" +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/setup.rst:38 +msgid "Payment policy" +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/setup.rst:39 +msgid "Seller profiles" msgstr "" #: ../../content/applications/sales/sales/ebay_connector/setup.rst:40 -msgid "Accept account deletion notifications" +msgid "Postal code" +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/setup.rst:41 +msgid "Shipping policy" msgstr "" #: ../../content/applications/sales/sales/ebay_connector/setup.rst:42 -msgid "Since September 2021, **eBay requires supporting customer account deletion/closure notifications**. As such, when eBay receives an account request for deletion, all eBay partners must confirm the reception of the request and take further action if necessary." +msgid "Listing type (fixed price or auction)" +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/setup.rst:44 +msgid "Starting price for Auction" +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/setup.rst:45 +msgid "Buy it now price" msgstr "" #: ../../content/applications/sales/sales/ebay_connector/setup.rst:46 -msgid "Odoo has a notification endpoint to receive those notifications, confirm the reception of the request, and handle the first set of actions to anonymize the account details in **Contacts** and remove the customer's access to the portal." +msgid "Fixed Price amount" +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/setup.rst:48 +msgid "Use stock quantity" +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/setup.rst:49 +msgid "Quantity on eBay" +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/setup.rst:50 +msgid "Duration" msgstr "" #: ../../content/applications/sales/sales/ebay_connector/setup.rst:51 -msgid "Make sure to correctly :ref:`set up your subscription to the marketplace account deletion notifications ` as eBay may temporarily disable the related eBay account until the subscription is completed." +msgid "Allow best offer" +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/setup.rst:52 +msgid "Private listing" +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/setup.rst:53 +msgid "eBay description" +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/setup.rst:54 +msgid "eBay product image" +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/setup.rst:55 +msgid "Country" msgstr "" #: ../../content/applications/sales/sales/ebay_connector/setup.rst:58 -msgid "Retrieve endpoint details from Odoo" +msgid "eBay terms" msgstr "" #: ../../content/applications/sales/sales/ebay_connector/setup.rst:60 -msgid "The endpoint details can be found in :menuselection:`Sales --> Configuration --> Settings --> eBay`. Click on *Generate Token* to retrieve your **Verification Token**." +msgid "*Variations* group multiple products into one, with variation (or variant) options. Variations can sync to Odoo's attributes and values. Variations will appear in drop down menus near the top of the page when viewing an eBay listing. These are comparable to product variants in Odoo." msgstr "" #: ../../content/applications/sales/sales/ebay_connector/setup.rst:-1 -msgid "Button to generate an eBay verification token in Odoo" +msgid "An example on eBay of the variations that can be added to a product." msgstr "" -#: ../../content/applications/sales/sales/ebay_connector/setup.rst:70 -msgid "Subscribe to account deletion notifications" -msgstr "" - -#: ../../content/applications/sales/sales/ebay_connector/setup.rst:72 -msgid "Log in on the `developer portal of eBay `_ and go to **Alerts & Notifications**." +#: ../../content/applications/sales/sales/ebay_connector/setup.rst:68 +msgid "*Item specifics*, located at the bottom of the listing, detail product-specific information. These specifics don't sync with Odoo fields by default; a development is required to link these fields." msgstr "" #: ../../content/applications/sales/sales/ebay_connector/setup.rst:-1 -msgid "Overview of the Alerts & Notifications dashboard of eBay" +msgid "Item specifics listed on an eBay product." msgstr "" -#: ../../content/applications/sales/sales/ebay_connector/setup.rst:79 -msgid "To subscribe to deletion/closure notifications, eBay needs a few details:" +#: ../../content/applications/sales/sales/ebay_connector/setup.rst:75 +msgid "*Sandbox* and *Production* are terms that are used to categorize the eBay environments as either still in development/testing (*Sandbox*) or for use in the real instance of the database with real customer information/dataset (*Production*). It is recommended to start first in the *Sandbox* to test, and then following the processes below, create a *Production* instance." msgstr "" #: ../../content/applications/sales/sales/ebay_connector/setup.rst:81 -msgid "An **email address** to send notifications to if the endpoint is unreachable." +msgid "eBay's sandbox environment can be accessed by navigating to `eBay's sandbox portal `_ at `https://sandbox.ebay.com/`. eBay's production environment can be accessed by navigating to `eBay.com portal `_ or `https://www.ebay.com/`." msgstr "" -#: ../../content/applications/sales/sales/ebay_connector/setup.rst:82 -msgid "The **endpoint details**:" +#: ../../content/applications/sales/sales/ebay_connector/setup.rst:87 +msgid "The environment selection **must** remain the same for all environment settings on eBay and on Odoo throughout this setup." msgstr "" -#: ../../content/applications/sales/sales/ebay_connector/setup.rst:84 -msgid "The URL to Odoo's account deletion notification endpoint" +#: ../../content/applications/sales/sales/ebay_connector/setup.rst:91 +msgid "eBay actions available on Odoo" msgstr "" -#: ../../content/applications/sales/sales/ebay_connector/setup.rst:85 -msgid "A verification token" -msgstr "" - -#: ../../content/applications/sales/sales/ebay_connector/setup.rst:-1 -msgid "Dedicated fields to enter the endpoint details" -msgstr "" - -#: ../../content/applications/sales/sales/ebay_connector/setup.rst:92 -msgid "You can edit the last two fields once the email address field is filled out." +#: ../../content/applications/sales/sales/ebay_connector/setup.rst:93 +msgid "The following are built-in actions in Odoo that add or update eBay listings:" msgstr "" #: ../../content/applications/sales/sales/ebay_connector/setup.rst:95 -msgid "Verify the connectivity with the endpoint" +msgid "**List**/ **Link**: generate a new eBay listing with an Odoo product by clicking :guilabel:`List Item on eBay` or :guilabel:`Link With Existing eBay Listing`." msgstr "" #: ../../content/applications/sales/sales/ebay_connector/setup.rst:97 -msgid "After setting the retrieved endpoint details in eBay's dashboard, consider testing the connectivity with the **Send Test Notification** button." +msgid ":guilabel:`Revise item` button: after making changes to an eBay listing in Odoo, save the record, and then click the :guilabel:`Revise Item` in Odoo to update the eBay listing." msgstr "" -#: ../../content/applications/sales/sales/ebay_connector/setup.rst:100 -msgid "You should get the following confirmation message: \"A test notification was sent successfully!\"" +#: ../../content/applications/sales/sales/ebay_connector/setup.rst:99 +msgid "**Relist**: if an item's listing was ended early or :guilabel:`auto-relist` was not selected, a user can relist the item from Odoo. The start date will reset." msgstr "" -#: ../../content/applications/sales/sales/ebay_connector/setup.rst:-1 -msgid "Button to send test notification" +#: ../../content/applications/sales/sales/ebay_connector/setup.rst:101 +msgid ":guilabel:`End item's listing` button: end a listing on eBay directly from Odoo." msgstr "" -#: ../../content/applications/sales/sales/ebay_connector/setup.rst:107 -msgid "Using the updated synchronisation method" +#: ../../content/applications/sales/sales/ebay_connector/setup.rst:102 +msgid "**Unlink product listings**: users can unlink a product from the eBay listing; the listing will stay intact on eBay." msgstr "" -#: ../../content/applications/sales/sales/ebay_connector/setup.rst:109 -msgid "If you have a lot of products, the eBay API can sometimes refuse some synchronization calls due to a time-based limit on the number of requests that eBay enforces." +#: ../../content/applications/sales/sales/ebay_connector/setup.rst:106 +msgid "Setup required on Odoo prior to eBay setup" +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/setup.rst:108 +msgid "To link eBay with Odoo, install the eBay module by navigating to the Odoo dashboard and clicking into the :guilabel:`Apps` application. Search the term `eBay` and install the `eBay Connector` module." msgstr "" #: ../../content/applications/sales/sales/ebay_connector/setup.rst:112 -msgid "To fix this issue, a new implementation mechanism has been developed; however this updated mechanism is disabled by default to avoid having the 2 systems running in parallel in existing installations." +msgid "The following items must be configured before eBay is set up:" msgstr "" -#: ../../content/applications/sales/sales/ebay_connector/setup.rst:116 -msgid "To switch to the new synchronization mechanism:" +#: ../../content/applications/sales/sales/ebay_connector/setup.rst:114 +msgid "In Odoo, create and configure products that are intended to be listed in eBay. eBay does not import new products into Odoo. All products must first be created in Odoo, and then linked to listings." msgstr "" -#: ../../content/applications/sales/sales/ebay_connector/setup.rst:119 -msgid "Go to :menuselection:`Settings --> Technical --> Scheduled Actions`" -msgstr "" - -#: ../../content/applications/sales/sales/ebay_connector/setup.rst:120 -msgid "Archive the old synchronization actions (both are named *Ebay: update product status*)" +#: ../../content/applications/sales/sales/ebay_connector/setup.rst:118 +msgid "Odoo does not allow multiple eBay listings to be linked per product in Odoo. If the company sells the same product for multiple listings, follow these instructions:" msgstr "" #: ../../content/applications/sales/sales/ebay_connector/setup.rst:121 -msgid "Activate the new synchronization actions (*Ebay: get new orders* which runs every 15min by default and *Ebay: synchronise stock (for 'get new orders' synchronisation)* which runs once a day per default)" -msgstr "" - -#: ../../content/applications/sales/sales/ebay_connector/setup.rst:124 -msgid "Ensure that the **Next Execution Date** for both these actions are in the near future" +msgid "Set up one *base* product (noted in the :guilabel:`Component` field of the :abbr:`BoM (Bill of Materials)`) from which all eBay listings will pull from. This will be a storable product so stock can be kept. Highlighted in green below, this product will be included in the kit on each subsequent “linked” product below." msgstr "" #: ../../content/applications/sales/sales/ebay_connector/setup.rst:126 -msgid "Starting with the next execution date, the new method will be used instead of the old one." +msgid "Set up 2+ *linked* products (noted in the :guilabel:`Product` field of the :abbr:`BoM (Bill of Materials)`, one for each eBay listing. The product type will be determined by the company's accounting settings, as explained in the Odoo documentation. Highlighted in yellow below, each product should have a :guilabel:`BoM type` equal to :guilabel:`Kit` and have the base product as a :guilabel:`Component` of the kit. When this linked eBay product is sold, the delivery order created will have the base product listed in lieu of the linked product." +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/setup.rst:0 +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/`" +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/setup.rst:140 +msgid "eBay does not automatically create invoices for eBay orders that get pushed into Odoo. Set invoicing policy on eBay products: invoicing policy will dictate when the product can be invoiced. Since most eBay users collect payment before the product is shipped, “invoice on ordered” will allow users to mass create invoices for eBay orders every day." +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/setup.rst:144 +msgid "Set the :guilabel:`Outgoing Shipments` route for the warehouse to :guilabel:`Deliver goods directly (1 step)`." +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/setup.rst:148 +msgid "When the :guilabel:`Outgoing Shipments` route is set to two or three steps, a known bug occurs: eBay wrongly marks orders as delivered when the pick operation in Odoo is confirmed. The expected behavior is to mark orders as delivered **after** the *delivery order* is confirmed. This mislabeling prevents tracking numbers in eBay from being imported onto the delivery order." +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/setup.rst:152 +msgid "If the Accounting/Invoicing apps are installed, practice registering payment and reconciling invoices created from eBay orders with incoming eBay money." +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/setup.rst:156 +msgid ":doc:`../../..//finance/accounting/bank/reconciliation`" +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/setup.rst:158 +msgid "Generate a marketplace account deletion/closure notification token. To begin, navigate to :menuselection:`Sales app --> Configuration --> Settings`. Under the :guilabel:`eBay` heading, change the mode to :guilabel:`Production`, and input random text values for the :guilabel:`Production Cert Key`. Then click the :guilabel:`Generate Token` button under the :guilabel:`eBay Marketplace Account Deletion/Closure Notifications` section. This token will be used during the setup on eBay for the deletion/closure notifications configuration." +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/setup.rst:-1 +#: ../../content/applications/sales/sales/ebay_connector/troubleshooting.rst:-1 +msgid "Generate a verification token in Odoo." +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/setup.rst:170 +msgid "Set up on eBay" +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/setup.rst:173 +msgid "Set up eBay developer account" +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/setup.rst:175 +msgid "To start, create an eBay developer account via `eBay's developer portal `_. This site requires a different login and password than the eBay account, though the same email address can be used to register. The verification to create a developer account is around 24 hours." +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/setup.rst:181 +msgid "Set up eBay keyset" +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/setup.rst:183 +msgid "Once the eBay developer account is created, set up an application on `eBay's developer portal `_. Next, navigate to the :guilabel:`Hi [username]` heading at top right of screen, then from the drop-down menu options, click :guilabel:`Application Keysets`. Doing so opens a pop-up that prompts the user to :guilabel:`Enter Application Title` (up to fifty characters), and choose a development environment (:guilabel:`Sandbox` or :guilabel:`Production`). These two fields generate first keyset. This application title is not saved until the keyset is generated. Click on :guilabel:`Create a keyset` to generate the keyset." +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/setup.rst:192 +msgid "The newly created *production keyset* is disabled by default. Activate it by subscribing to the eBay Marketplace 'account deletion or closure notifications' or by applying to eBay for an exemption. Once enabled, the database can make 5000 calls per day using this keyset." +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/setup.rst:-1 +msgid "Disabled keyset present after creating a keyset." +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/setup.rst:201 +msgid "Configure account deletion / notification settings (Production)" +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/setup.rst:203 +msgid "To configure notifications or delete the database on a production environment, navigate to the `eBay developer portal `_. Configure the account deletion/notification settings in eBay by navigating to the `Hi [username]` at top right of screen, then :guilabel:`Application Keysets`." +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/setup.rst:208 +msgid "Next, click the :guilabel:`marketplace deletion/account closure notification` option under the :guilabel:`Production` keyset column. Enter an email under :guilabel:`Email to notify if marketplace account deletion notification endpoint is down`. Click :guilabel:`Save` to enable the email." +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/setup.rst:212 +msgid "Following this action, enter the :guilabel:`Marketplace account deletion notification endpoint` URL provided by Odoo. This HTTPs endpoint is found in Odoo by navigating to :menuselection:`Sales app --> Configuration --> Settings`, in the :guilabel:`eBay Marketplace Account Deletion/Closure Notifications` field." +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/setup.rst:217 +msgid "Clicking the :guilabel:`Generate Token` button in Odoo below this field creates a verification token for the eBay production environment. In Odoo, :guilabel:`Copy` the newly created token and navigate to eBay to fill in the :guilabel:`Verification token` field. Click :guilabel:`Save` to enable the :guilabel:`Event Notification Delivery Method`." +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/setup.rst:-1 +msgid "Configuring account deletion / notification settings in eBay." +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/setup.rst:226 +msgid "After completing the above fields, click :guilabel:`Send Test Notification` to test the new notifications. Proceed to the next step when the green check mark appears. Revisit the above settings if the test post is not as expected." +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/setup.rst:230 +msgid "After configuring notification settings, go back to the :menuselection:`Application Keys` page to generate production keysets." +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/setup.rst:234 +msgid "Creating the keyset" +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/setup.rst:236 +msgid "A successful setup of the notifications enables the ability to create Production Keysets which are needed in the remainder of the Odoo configuration. Navigate back to the :menuselection:`Application Keys` page generate a production keyset." +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/setup.rst:240 +msgid "The administrator is prompted to :menuselection:`Confirm the Primary Contact`. Enter or confirm the account owner (the person legally responsible for the eBay API License Agreement). Fill out :guilabel:`First Name`, :guilabel:`Last Name`, :guilabel:`Email`, :guilabel:`Phone`. Then, select either the :guilabel:`Individual` or :guilabel:`Business` options." +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/setup.rst:246 +msgid "The provided email address or phone number does **not** have to match the account's. eBay uses this information to contacting the business or individual in case of issues with user tokens. Additional contacts can be added from the :guilabel:`Profile & Contacts` page on eBay." +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/setup.rst:250 +msgid "Click on :guilabel:`Continue to Create Keys` to confirm the primary contact. The :guilabel:`Application Keys` populates in a new screen and an email is also sent to the developer account. An :guilabel:`App ID (Client ID)`, :guilabel:`Dev ID`, and :guilabel:`Cert ID (Client Secret)` all populate." +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/setup.rst:-1 +msgid "Application keys are populated after creating the app in eBay." +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/setup.rst:259 +msgid "Copy these values down as they will be input into Odoo later in the process." +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/setup.rst:262 +msgid "Create eBay user token" +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/setup.rst:264 +msgid "Now, create a *user token* in eBay by navigating to the `Hi [username]` at top right of screen, then :guilabel:`User Access Tokens`." +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/setup.rst:-1 +msgid "Generate user token s on the eBay developer console." +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/setup.rst:271 +msgid "Select the correct :guilabel:`Environment`: :guilabel:`Sandbox` for testing or :guilabel:`Production` for the live database. Maintain the same selection for all environment settings on both eBay and Odoo." +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/setup.rst:275 +msgid "Next, select the radio button labeled :guilabel:`Auth'n'Auth`." +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/setup.rst:277 +msgid "Choose :guilabel:`Sign in to Production` or :guilabel:`Sign in to Sandbox` to get a user token in the chosen environment. This button varies based on the selection made above for either :guilabel:`Sandbox` or :guilabel:`Production`." +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/setup.rst:281 +msgid "Doing so triggers a a pop-up window to :guilabel:`Confirm your Legal Address`. Complete the required fields, which are :guilabel:`First Name`, :guilabel:`Last Name`, :guilabel:`Primary Email`, :guilabel:`Legal Address`, and :guilabel:`Account Type`. For :guilabel:`Account Type`, select either :guilabel:`Individual` or :guilabel:`Business`. To complete the confirmation, click :guilabel:`Sign into eBay to get a Token`." +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/setup.rst:288 +msgid "eBay will contact this individual or business should there be any issues with the application keys. Other contacts can be added on the :menuselection:`Profile & Contacts` eBay page." +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/setup.rst:291 +msgid "The administrator will be redirected to either a sandbox or production sign-in page for eBay. This login is different than the eBay developer's console, it is the eBay account where the items will be sold on. This email and/or login can differ from the eBay developer account." +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/setup.rst:295 +msgid "Enter the :guilabel:`Email` or :guilabel:`Username` for the eBay account and sign into the eBay account." +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/setup.rst:299 +msgid "Should an additional user be needed for the sandbox simulation, a test user needs to be created. Visit `eBay's Register for Sandbox form `_. Detailed instructions can be found on eBay's help pages: `Create a test Sandbox user `_." +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/setup.rst:305 +msgid "Grant application access" +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/setup.rst:307 +msgid "After signing into the production or sandbox environment, eBay presents the administrator with an *agreement* to grant access to the user's eBay data." +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/setup.rst:310 +msgid "Clicking :guilabel:`Agree` allows eBay to link the eBay account with the *application programming interface* (API). This agreement can be changed at any time by visiting eBay's account preferences." +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/setup.rst:314 +msgid "eBay has a timed sequence between signing in and agreeing to the terms for the :abbr:`API (Application Programming Interface)` linkage to the account. Once complete a :guilabel:`User Token` will populate on the :menuselection:`User Tokens` page." +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/setup.rst:318 +msgid "A :guilabel:`User Token` will populate on the screen. Make sure to copy this token down as it will be used in the next steps along with the :guilabel:`Application Keyset`." +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/setup.rst:-1 +msgid "Generated user token and API explorer link on the eBay developer console." +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/setup.rst:326 +msgid "Signing in to the eBay account is necessary to create to the token. The eBay developer can also revoke the token by clicking on the :guilabel:`Revoke a Token` link." +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/setup.rst:330 +msgid "API explorer" +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/setup.rst:332 +msgid "Now that the :guilabel:`Application Keyset` and :guilabel:`User Token` have been created, a test can be executed via the `API Explorer `_ to ensure that the :abbr:`API (Application Programming Interface)` is configured correctly. This test will execute a simple search using the :abbr:`API (Application Programming Interface)`." +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/setup.rst:338 +msgid "To begin the :abbr:`API (Application Programming Interface)` test, click on :guilabel:`Get OAuth Application Token`. This will populate the key into the :guilabel:`Token` field." +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/setup.rst:341 +msgid "A basic search function is set to execute. Click on :guilabel:`Execute` to complete the test. A successful test will respond with a :guilabel:`Call Response` of `200 OK` with a corresponding :guilabel:`Time`." +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/setup.rst:346 +msgid "Entering credentials into Odoo" +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/setup.rst:348 +msgid "The previously copied :guilabel:`User Token` and :guilabel:`Application Keyset` are now ready to be entered into the Odoo database." +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/setup.rst:351 +msgid "Navigate back the eBay settings in Odoo (:menuselection:`Sales app --> Configuration --> Settings --> eBay`) and paste the following credentials from eBay into the corresponding fields in Odoo." +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/setup.rst:358 +msgid "Platform" +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/setup.rst:359 +msgid "Dev Key/ID" +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/setup.rst:360 +msgid "Token" +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/setup.rst:361 +msgid "App Key/ID" +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/setup.rst:362 +msgid "Cert Key/ID" +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/setup.rst:363 +msgid "eBay" +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/setup.rst:364 +msgid "Dev ID" +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/setup.rst:365 +msgid "User Token" +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/setup.rst:366 +msgid "App ID (Client ID)" +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/setup.rst:367 +msgid "Cert ID (Client Secret)" +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/setup.rst:368 +#: ../../content/applications/sales/sales/products_prices/products/product_images.rst:102 +msgid "Odoo" +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/setup.rst:369 +msgid "Developer Key" +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/setup.rst:370 +msgid "Production/Sandbox Token" +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/setup.rst:371 +msgid "Production/Sandbox App Key" +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/setup.rst:372 +msgid "Production/Sandbox Cert Key" +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/setup.rst:375 +msgid "The :guilabel:`Application Keyset` can be accessed by going to `eBay's developer portal `_ and navigate to the `Hi [username]` at top right of screen, then click on :guilabel:`Application Keysets`. Get to the *User Token* in eBay by navigating to the `Hi [username]` at top right of screen, then :guilabel:`User Access Tokens` and click on :guilabel:`Sign in to Sandbox`. The :guilabel:`User Token` can also be accessed by clicking on :guilabel:`User Tokens` from the :menuselection:`Application Keys` page." +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/setup.rst:382 +msgid "Confirm that the setup is correct by saving the credentials in Odoo. Once the initial setup is complete, a new menu tab in products will appear called `eBay` with the option to :guilabel:`Sell on eBay`. See the :doc:`manage` documentation on how to list products." +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/setup.rst:387 +msgid "Sync product categories by clicking :guilabel:`Product Categories`. After syncing, a new menu item, `eBay Category`, appears available for products to be configured with. These eBay categories are imported from the Odoo database and are available when listing an item on eBay through Odoo." +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/setup.rst:393 +msgid "If Product Categories beyond four paths are required, users will need to manually add those paths. This has historically been done by getting a list of all product categories beyond four paths, manually importing them into the Product Category model in Odoo, and then linking them individually to the product." +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/setup.rst:399 +msgid "Now that the setup is complete, proceed to either:" +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/setup.rst:401 +msgid ":doc:`Create listings `" +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/setup.rst:402 +msgid ":doc:`Link existing listings `" +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/troubleshooting.rst:3 +msgid "Troubleshooting eBay connector" +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/troubleshooting.rst:13 +msgid "Accept account deletion notifications" +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/troubleshooting.rst:15 +msgid "Since September 2021, **eBay requires supporting customer account deletion/closure notifications**. As such, when eBay receives an account request for deletion, all eBay partners must confirm the reception of the request and take further action if necessary." +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/troubleshooting.rst:19 +msgid "Odoo has a notification endpoint to receive those notifications, confirm the reception of the request, and handle the first set of actions to anonymize the account details in *Contacts* and remove the customer's access to the portal." +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/troubleshooting.rst:24 +msgid "Make sure to correctly :ref:`set up the subscription to the marketplace account deletion notifications ` as eBay may temporarily disable the related eBay account until the subscription is completed." +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/troubleshooting.rst:29 +msgid "Verify the installation of Odoo is up to date" +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/troubleshooting.rst:31 +msgid "In order to activate the endpoint, the module *eBay Connector - Account Deletion* must be installed. If the Odoo database was first created after September 2021, the module is installed automatically and the administrator can proceed to the :ref:`next step `." +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/troubleshooting.rst:36 +msgid "Update Odoo to the latest release" +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/troubleshooting.rst:38 +msgid "The notification endpoint is made available through a new Odoo module; to be able to install it, the administrator must make sure that the Odoo source code is up-to-date." +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/troubleshooting.rst:41 +msgid "If the company uses Odoo on Odoo.com or Odoo.sh platform, the code is already up-to-date, so proceed to the next step." +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/troubleshooting.rst:43 +msgid "If the company uses Odoo with an on-premise setup or through a partner, then the administrator must update the installation as detailed in :doc:`this documentation page ` or by contacting an integrating partner." +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/troubleshooting.rst:48 +msgid "Update the list of available modules" +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/troubleshooting.rst:50 +msgid "New modules must be *discovered* by the Odoo instance to be available in the :menuselection:`Apps` menu." +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/troubleshooting.rst:53 +msgid "To do so, activate the :ref:`developer mode `, and go to :menuselection:`Apps -> Update Apps List`. A wizard will ask for confirmation." +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/troubleshooting.rst:57 +msgid "Install the eBay Connector - Account Deletion update" +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/troubleshooting.rst:60 +msgid "**Never** install new modules in the production database without testing them in a duplicate or staging environment. For Odoo.com customers, a duplicate database can be created from the database management page. For Odoo.sh users, the administrator should use a staging or duplicate database. For on-premise users, the administrator should use a staging environment - contact the integrating partner for more information regarding how to test a new module in a particular setup." +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/troubleshooting.rst:67 +msgid "To install the module, go to the :menuselection:`Apps` menu, remove the `Apps` search facet and search for `eBay`. If the module *eBay Connector - Account Deletion* is present and marked as installed, the Odoo database is already up-to-date and the administrator can proceed with the next step. If it is not yet installed, install it now." +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/troubleshooting.rst:75 +msgid "Retrieve endpoint details from Odoo" +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/troubleshooting.rst:77 +msgid "The endpoint details can be found in :menuselection:`Sales --> Configuration --> Settings --> eBay`. First, input random text values for the :guilabel:`Production App Key` and for the :guilabel:`Production Cert Key`. Click on :guilabel:`Generate Token` to retrieve the :guilabel:`Verification Token`." +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/troubleshooting.rst:89 +msgid "Subscribe to account deletion notifications" +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/troubleshooting.rst:91 +msgid "Navigate to the `eBay developer portal `_. Configure the account deletion/notification settings in eBay by navigating to the `Hi [username]` at the top right of screen, then go to :guilabel:`Alerts & Notifications`." +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/troubleshooting.rst:-1 +msgid "Overview of the Alerts & Notifications dashboard of eBay" +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/troubleshooting.rst:99 +msgid "To subscribe to deletion/closure notifications, eBay needs a few details:" +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/troubleshooting.rst:101 +msgid "An *email address* to send notifications to if the endpoint is unreachable." +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/troubleshooting.rst:102 +msgid "The *endpoint details*:" +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/troubleshooting.rst:104 +msgid "The URL to Odoo's account deletion notification endpoint" +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/troubleshooting.rst:105 +msgid "A verification token" +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/troubleshooting.rst:-1 +msgid "Dedicated fields to enter the endpoint details" +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/troubleshooting.rst:112 +msgid "The administrator can edit the last two fields once the email address field is filled out." +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/troubleshooting.rst:115 +msgid "Verify the connectivity with the endpoint" +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/troubleshooting.rst:117 +msgid "After setting the retrieved endpoint details in eBay's dashboard, consider testing the connectivity with the :guilabel:`Send Test Notification` button." +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/troubleshooting.rst:120 +msgid "The following confirmation message should be received: \"A test notification was sent successfully!\"" +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/troubleshooting.rst:-1 +msgid "Button to send test notification" msgstr "" #: ../../content/applications/sales/sales/invoicing.rst:5 @@ -7112,455 +8047,855 @@ msgid "Manage your products" msgstr "" #: ../../content/applications/sales/sales/products_prices/products/import.rst:3 -msgid "How to import Products with Categories and Variants" +msgid "Import products" msgstr "" #: ../../content/applications/sales/sales/products_prices/products/import.rst:5 -msgid "Import templates are provided in the **Import Tool** of the most common data to import (contacts, products, bank statements, etc.). You can open them with any spreadsheet software (Microsoft Office, OpenOffice, Google Drive, etc.)." +msgid "Odoo *Sales* provides a template for importing products with categories and variants, which can be opened and edited with any spreadsheet software (Microsoft Excel, OpenOffice, Google Sheets, etc.)." msgstr "" -#: ../../content/applications/sales/sales/products_prices/products/import.rst:11 -msgid "How to customize the file" +#: ../../content/applications/sales/sales/products_prices/products/import.rst:8 +msgid "When this spreadsheet is filled out properly, it can be quickly uploaded to the Odoo database. When uploaded, those products are instantly added, accessible, and editable in the product catalog." msgstr "" -#: ../../content/applications/sales/sales/products_prices/products/import.rst:13 -msgid "Remove columns you don't need. However, we advise you to not remove the *ID* column (see why below)." +#: ../../content/applications/sales/sales/products_prices/products/import.rst:12 +msgid "Import template" msgstr "" -#: ../../content/applications/sales/sales/products_prices/products/import.rst:15 -msgid "Set a unique ID to every single record by dragging down the ID sequencing." -msgstr "" - -#: ../../content/applications/sales/sales/products_prices/products/import.rst:16 -msgid "Don't change the labels of columns you want to import. Otherwise, Odoo won't recognize them anymore, and you will have to map them on your own in the import screen." +#: ../../content/applications/sales/sales/products_prices/products/import.rst:14 +msgid "In order to import products with categories and variants, the *Import Template for Products* **must** be downloaded. Once downloaded, the template can be adjusted and customized, and then uploaded back into the Odoo database." msgstr "" #: ../../content/applications/sales/sales/products_prices/products/import.rst:18 -msgid "Feel free to add new columns, but the fields need to exist in Odoo. If Odoo fails in matching the column name with a field, you can match it manually when importing by browsing a list of available fields." +msgid "To download the necessary import template, navigate to :menuselection:`Sales app --> Products --> Products`. On the :guilabel:`Products` page, click the :guilabel:`⚙️ (gear)` icon in the upper-left corner. Doing so reveals a drop-down menu." msgstr "" -#: ../../content/applications/sales/sales/products_prices/products/import.rst:24 -msgid "Why an “ID” column?" +#: ../../content/applications/sales/sales/products_prices/products/import.rst:22 +msgid "From this drop-down menu, select the :guilabel:`Import records` option." msgstr "" -#: ../../content/applications/sales/sales/products_prices/products/import.rst:26 -msgid "The ID is a truly unique identifier for the line item. Feel free to use one from your previous software to ease the transition into Odoo." +#: ../../content/applications/sales/sales/products_prices/products/import.rst:-1 +msgid "The Import records option selectable from the gear icon on the Products page in Odoo Sales." msgstr "" -#: ../../content/applications/sales/sales/products_prices/products/import.rst:29 -msgid "Setting an ID is not mandatory when importing, but it helps in many cases:" -msgstr "" - -#: ../../content/applications/sales/sales/products_prices/products/import.rst:31 -msgid "Update imports: you can import the same file several times without creating duplicates." -msgstr "" - -#: ../../content/applications/sales/sales/products_prices/products/import.rst:32 -msgid "Import relation fields (see here below)." +#: ../../content/applications/sales/sales/products_prices/products/import.rst:28 +msgid "Selecting :guilabel:`Import records` reveals a separate page with a link to download the :guilabel:`Import Template for Products`. Click that link to download the template." msgstr "" #: ../../content/applications/sales/sales/products_prices/products/import.rst:35 -msgid "How to import relation fields" +msgid "Once the template download is complete, open the spreadsheet file to customize it." msgstr "" -#: ../../content/applications/sales/sales/products_prices/products/import.rst:37 -msgid "An Odoo object is always related to many other objects (e.g., a product is linked to product categories, attributes, vendors, etc.). To import those relations, you need to import the records of the related object first from their own list menu." +#: ../../content/applications/sales/sales/products_prices/products/import.rst:38 +msgid "Customize product import template" msgstr "" -#: ../../content/applications/sales/sales/products_prices/products/import.rst:41 -msgid "You can do this using the name of the related record or its ID. The ID is expected when two records have the same name. In such a case, add \" / ID\" at the end of the column title (e.g., for product attributes: Product Attributes / Attribute / ID)." +#: ../../content/applications/sales/sales/products_prices/products/import.rst:40 +msgid "When the import template has been downloaded and opened, it's time to modify its contents. However, before any changes are made, there are a few elements to keep in mind during the process:" msgstr "" -#: ../../content/applications/sales/sales/products_prices/products/product_images.rst:3 -msgid "Automatically get product images with Google Images" +#: ../../content/applications/sales/sales/products_prices/products/import.rst:43 +msgid "Feel free to remove any columns that aren't deemed necessary. But, it is *strongly* advised that the :guilabel:`Internal Reference` column remains." msgstr "" -#: ../../content/applications/sales/sales/products_prices/products/product_images.rst:5 -msgid "The product images are very useful in Odoo, for example, to quickly find a product or check if you scanned the right one, but it can be a bit painful to set up especially if you have a lot of products. **Google Custom Search** allows finding images automatically for your product, based on their barcode, keeping your focus on what matters in your business." +#: ../../content/applications/sales/sales/products_prices/products/import.rst:46 +msgid "While it's not mandatory, having a unique identifier (e.g. `FURN_001`) in the :guilabel:`Internal Reference` column for each product can be helpful in many cases. This can even be from previous software spreadsheets to ease the transition into Odoo." msgstr "" -#: ../../content/applications/sales/sales/products_prices/products/product_images.rst:15 -msgid "This functionnality requires configuration both on Google and on Odoo." +#: ../../content/applications/sales/sales/products_prices/products/import.rst:50 +msgid "For example, when updating imported products, the same file can be imported several times without creating duplicates, thus enhancing the efficiency and simplicity of imported product management." msgstr "" -#: ../../content/applications/sales/sales/products_prices/products/product_images.rst:17 -msgid "With a free Google account, you can get up to 100 free images per day. If you need a higher rate, you'll have to upgrade to a billing account." +#: ../../content/applications/sales/sales/products_prices/products/import.rst:52 +msgid "Do **not** change the labels of columns that are meant to be imported. Otherwise, Odoo won't recognize them, forcing the user to map them on the import screen manually." msgstr "" -#: ../../content/applications/sales/sales/products_prices/products/product_images.rst:23 -msgid "Google API dashboard" +#: ../../content/applications/sales/sales/products_prices/products/import.rst:54 +msgid "Feel free to add new columns to the template spreadsheet, if desired. However, to be added, those fields **must** exist in Odoo. If Odoo can't match the column name with a field, it can be matched manually during the import process." msgstr "" -#: ../../content/applications/sales/sales/products_prices/products/product_images.rst:25 -msgid "Go to the `Google Cloud Platform API & Services `_ page to generate Google Custom Search API credentials. Log in with your Google account." +#: ../../content/applications/sales/sales/products_prices/products/import.rst:58 +msgid "During the import process of the completed template, Odoo reveals a page showcasing all the elements of the newly-configured product template spreadsheet, separated by :guilabel:`File Column`, :guilabel:`Odoo Field`, and :guilabel:`Comments`." msgstr "" -#: ../../content/applications/sales/sales/products_prices/products/product_images.rst:28 -msgid "Select or create an API project to store the credentials. Give it an explicit name (e.g. Odoo Images)." +#: ../../content/applications/sales/sales/products_prices/products/import.rst:62 +msgid "To manually match a column name with a field in Odoo, click the :guilabel:`Odoo Field` drop-down menu next to the :guilabel:`File Column` that needs a manual adjustment, and select the appropriate field from that drop-down menu." msgstr "" -#: ../../content/applications/sales/sales/products_prices/products/product_images.rst:31 -msgid "In the credentials section, click on **Create Credentials** and select **API Keys**." +#: ../../content/applications/sales/sales/products_prices/products/import.rst:0 +msgid "The Odoo Field drop-down menu next to a Field Column that needs to be manually adjusted." msgstr "" -#: ../../content/applications/sales/sales/products_prices/products/product_images.rst:0 -msgid "API & Services page on Google Cloud Platform" +#: ../../content/applications/sales/sales/products_prices/products/import.rst:71 +msgid "Import product template spreadsheet" msgstr "" -#: ../../content/applications/sales/sales/products_prices/products/product_images.rst:37 -msgid "Save your **API Key**. You'll need it for the next step in Odoo!" +#: ../../content/applications/sales/sales/products_prices/products/import.rst:73 +msgid "After customizing the product template spreadsheet, return to the Odoo product import page, where the template download link is found, and click the :guilabel:`Upload File` button in the upper-left corner." msgstr "" -#: ../../content/applications/sales/sales/products_prices/products/product_images.rst:39 -msgid "Use the search bar to look for **Google Custom Search API** and select it." +#: ../../content/applications/sales/sales/products_prices/products/import.rst:-1 +msgid "The upload file button on the import products template download page in Odoo Sales." msgstr "" -#: ../../content/applications/sales/sales/products_prices/products/product_images.rst:0 -msgid "Search bar containing \"Custom Search API\" on Google Cloud Platform" +#: ../../content/applications/sales/sales/products_prices/products/import.rst:81 +msgid "Then, a pop-up window appears, in which the completed product template spreadsheet file should be selected and uploaded to Odoo." msgstr "" -#: ../../content/applications/sales/sales/products_prices/products/product_images.rst:45 -msgid "Enable the API." +#: ../../content/applications/sales/sales/products_prices/products/import.rst:84 +msgid "After that, Odoo reveals a page showcasing all the elements of the newly-configured product template spreadsheet, separated by :guilabel:`File Column`, :guilabel:`Odoo Field`, and :guilabel:`Comments`." msgstr "" -#: ../../content/applications/sales/sales/products_prices/products/product_images.rst:0 -msgid "\"Custom Search API\" tile with Enable button highlighted on Google Cloud Platform" +#: ../../content/applications/sales/sales/products_prices/products/import.rst:-1 +msgid "The import a file page in Odoo Sales after a product template has been uploaded." msgstr "" -#: ../../content/applications/sales/sales/products_prices/products/product_images.rst:54 -msgid "Google Programmable Search dashboard" +#: ../../content/applications/sales/sales/products_prices/products/import.rst:91 +msgid "From here, the :guilabel:`File Column` can be manually assigned to an :guilabel:`Odoo Field`, if necessary." msgstr "" -#: ../../content/applications/sales/sales/products_prices/products/product_images.rst:56 -msgid "Go to `Google Programmable Search Engine `_ and click on **Get Started**. Log in with your Google account." +#: ../../content/applications/sales/sales/products_prices/products/import.rst:94 +msgid "To make sure everything is appropriate, and all the columns and fields are lined up accurately, click the :guilabel:`Test` button in the upper-left corner." msgstr "" -#: ../../content/applications/sales/sales/products_prices/products/product_images.rst:0 -msgid "Google Programmable Search Engine page with the **Get Started** button on the up-right\n" -"of the page" +#: ../../content/applications/sales/sales/products_prices/products/import.rst:97 +msgid "If everything is lined up and applied correctly, Odoo reveals a blue banner at the top of the page, informing the user that :guilabel:`Everything seems valid`." msgstr "" -#: ../../content/applications/sales/sales/products_prices/products/product_images.rst:64 -msgid "Fill the language and the name of the search engine. Give it an explicit name (e.g. Odoo Images)." +#: ../../content/applications/sales/sales/products_prices/products/import.rst:-1 +msgid "The everything seems valid message that appears if file columns are entered correctly." msgstr "" -#: ../../content/applications/sales/sales/products_prices/products/product_images.rst:68 -msgid "Google doesn't allow to create a search engine without having entered at least one specific site to search on. You can put any website (e.g. www.google.com) for this step, we will remove it later." +#: ../../content/applications/sales/sales/products_prices/products/import.rst:104 +msgid "If there are any errors, Odoo reveals a red banner at the top of the page, with instructions of where to locate the specific issues, and how to fix them." msgstr "" -#: ../../content/applications/sales/sales/products_prices/products/product_images.rst:72 -msgid "Validate the form by clicking on **Create**. Then, go to the edition mode of the search engine that you created (either by clicking on **Control Panel** on the confirmation page or by clicking on the name of your Search Engine on the Home page)." +#: ../../content/applications/sales/sales/products_prices/products/import.rst:-1 +msgid "The import error message that appears if file columns don't match an Odoo Field." msgstr "" -#: ../../content/applications/sales/sales/products_prices/products/product_images.rst:76 -msgid "In the **basics** tab, make sure to enable **Image search**, **SafeSearch** and **Search the entire web**." +#: ../../content/applications/sales/sales/products_prices/products/import.rst:111 +msgid "Once those errors are fixed, click :guilabel:`Test` again to ensure all necessary issues have been remedied appropriately." msgstr "" -#: ../../content/applications/sales/sales/products_prices/products/product_images.rst:80 -msgid "Once **Search the entire web** is enabled, you can safely delete the site that you put at the previous step." +#: ../../content/applications/sales/sales/products_prices/products/import.rst:114 +msgid "If additional product template spreadsheets need to be uploaded, click the :guilabel:`Load File` button, select the desired product template spreadsheet, and repeat the process." msgstr "" -#: ../../content/applications/sales/sales/products_prices/products/product_images.rst:83 -msgid "Save your **Search Engine Id**. You’ll need it for the next step in Odoo!" +#: ../../content/applications/sales/sales/products_prices/products/import.rst:117 +msgid "When everything is ready, click the :guilabel:`Import` button." msgstr "" -#: ../../content/applications/sales/sales/products_prices/products/product_images.rst:88 -msgid "Odoo" +#: ../../content/applications/sales/sales/products_prices/products/import.rst:119 +msgid "When clicked, Odoo instantly imports those products, and reveals the main :guilabel:`Products` page, with a pop-up message in the upper-right corner. This pop-up message informs the user how many products were successfully imported." msgstr "" -#: ../../content/applications/sales/sales/products_prices/products/product_images.rst:90 -msgid "Go to :menuselection:`Settings --> General Settings --> Integrations`, activate **Google Images** and save." +#: ../../content/applications/sales/sales/products_prices/products/import.rst:-1 +msgid "The pop-up window that appears after a successful product import process in Odoo Sales." msgstr "" -#: ../../content/applications/sales/sales/products_prices/products/product_images.rst:93 -msgid "Go back to :menuselection:`Settings --> General Settings--> Integrations`, enter your **API Key** and **Search Engine ID** in **Google Images** settings and save again." +#: ../../content/applications/sales/sales/products_prices/products/import.rst:127 +msgid "At this point, all the newly-imported products are accessible and editable via the :guilabel:`Products` page." msgstr "" -#: ../../content/applications/sales/sales/products_prices/products/product_images.rst:99 -msgid "Automatically get your product images in Odoo" +#: ../../content/applications/sales/sales/products_prices/products/import.rst:131 +msgid "Import relation fields, attributes, and variants" msgstr "" -#: ../../content/applications/sales/sales/products_prices/products/product_images.rst:101 -msgid "The action to automatically get your product images in Odoo appears in any Products or Product Variants list view. Here is a step-by-step guide from the Inventory app." +#: ../../content/applications/sales/sales/products_prices/products/import.rst:133 +msgid "It's important to note that an Odoo object is always related to many other objects. For example, a product is linked to product categories, attributes, vendors, and things of this nature. These links/connections are known as relations." msgstr "" -#: ../../content/applications/sales/sales/products_prices/products/product_images.rst:104 -msgid "Go to the Products menu (:menuselection:`Products --> Products` or :menuselection:`Products --> Product Variants`) from any application that uses products like Inventory or Sales." +#: ../../content/applications/sales/sales/products_prices/products/import.rst:138 +msgid "In order to import product relations, the records of the related object **must** be imported *first* from their own list menu." msgstr "" -#: ../../content/applications/sales/sales/products_prices/products/product_images.rst:107 -msgid "On the list view, select the products that needs an image." +#: ../../content/applications/sales/sales/products_prices/products/import.rst:142 +msgid "Relation fields" msgstr "" -#: ../../content/applications/sales/sales/products_prices/products/product_images.rst:110 -msgid "Only the 10,000 first selected products or product variants will be processed." +#: ../../content/applications/sales/sales/products_prices/products/import.rst:144 +msgid "On product forms in Odoo, there are a number of fields that can be modified and customized at any time. These fields are found under every tab on a product form. While these fields are easily editable directly on the product form, they can also be modified via a product import." msgstr "" -#: ../../content/applications/sales/sales/products_prices/products/product_images.rst:113 -msgid "Only the products or product variants with a barcode and without an image will be processed." +#: ../../content/applications/sales/sales/products_prices/products/import.rst:148 +msgid "As mentioned, relation fields of this nature can **only** be imported for products if they already exist in the database. For example, if a user attempts to import a product with a *Product Type*, it can only be one of the preconfigured product types existing in the database (e.g. *Storable Product*, *Consumable*, etc.)." msgstr "" -#: ../../content/applications/sales/sales/products_prices/products/product_images.rst:114 -msgid "If you select a product that has one or more variants from the Products view, each variant matching the previous criteria will be processed." +#: ../../content/applications/sales/sales/products_prices/products/import.rst:153 +msgid "To import information for a relation field on a product import template spreadsheet, add the name of the field as a column name/title on the spreadsheet. Then, on the appropriate product line, add the desired relation field option." msgstr "" -#: ../../content/applications/sales/sales/products_prices/products/product_images.rst:117 -msgid "In the action menu, select **Get Pictures from Google Images** and validate by clicking on **Get picture**." +#: ../../content/applications/sales/sales/products_prices/products/import.rst:157 +msgid "When all desired relation field information has been entered, save the spreadsheet, and import it to the database, per the process mentioned above (:menuselection:`Sales app --> Products --> Products --> ⚙️ (gear) icon --> Import records --> Upload File`)." msgstr "" -#: ../../content/applications/sales/sales/products_prices/products/product_images.rst:120 -msgid "You should see your images appearing incrementally." +#: ../../content/applications/sales/sales/products_prices/products/import.rst:161 +msgid "Once the spreadsheet with the newly-configured relation field information has been uploaded, click :guilabel:`Import`, and Odoo returns to the :guilabel:`Products` page." msgstr "" -#: ../../content/applications/sales/sales/products_prices/products/product_images.rst:123 -msgid "Only the 10 first images are fetched immediatly. If you selected more than 10, the rest will be fetched as a background job." +#: ../../content/applications/sales/sales/products_prices/products/import.rst:164 +msgid "When the newly-changed/modified products, complete with the new relation field information, has been imported and uploaded, that new information can be found on the :guilabel:`Products` page." msgstr "" -#: ../../content/applications/sales/sales/products_prices/products/product_images.rst:125 -msgid "The background job process about 100 images in a minute. If you reach the quota authorized by Google (either with a free or a paid plan), the background job will put itself on hold for 24 hours and continue where it stopped the day before." +#: ../../content/applications/sales/sales/products_prices/products/import.rst:168 +msgid "Attributes and values" msgstr "" -#: ../../content/applications/sales/sales/products_prices/products/product_images.rst:130 -msgid "`Create, modify, or close your Google Cloud Billing account `_" +#: ../../content/applications/sales/sales/products_prices/products/import.rst:170 +msgid "Odoo also allows users to import product attributes and values that can be used for products that already exist in the database, and/or with imported products." msgstr "" +#: ../../content/applications/sales/sales/products_prices/products/import.rst:173 +msgid "To import attributes and values, a separate spreadsheet or CSV file dedicated to attributes and values **must** be imported and uploaded before they can be used for other products." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/import.rst:176 +msgid "The column names/titles of the attributes and values spreadsheet should be as follows: :guilabel:`Attribute`, :guilabel:`Display Type`, :guilabel:`Variant Creation Mode`, and :guilabel:`Values / Value`." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/import.rst:-1 +msgid "An attributes and values spreadsheet template for imports." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/import.rst:184 +msgid ":guilabel:`Attribute`: name of the attribute (e.g. `Size`)." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/import.rst:185 +msgid ":guilabel:`Display Type`: display type used in the product configurator. There are three display type options:" +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/import.rst:188 +msgid ":guilabel:`Radio`: values displayed as radio buttons" +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/import.rst:189 +msgid ":guilabel:`Selection`: values displayed in a selection list" +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/import.rst:190 +msgid ":guilabel:`Color`: values denoted as a color selection" +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/import.rst:192 +msgid ":guilabel:`Variant Creation Mode`: how the variants are created when applied to a product. There are three variant creation mode options:" +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/import.rst:195 +msgid ":guilabel:`Instantly`: all possible variants are created as soon as the attribute, and its values, are added to a product" +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/import.rst:197 +msgid ":guilabel:`Dynamically`: each variant is created **only** when its corresponding attributes and values are added to a sales order" +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/import.rst:199 +msgid ":guilabel:`Never`: variants are **never** created for the attribute" +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/import.rst:202 +msgid "The :guilabel:`Variants Creation Mode` **cannot** be changed once the attribute is used on at least one product." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/import.rst:205 +msgid ":guilabel:`Values/Value`: values pertaining to the corresponding attribute. If there are multiple values for the same attribute, the values need to be in individual lines on the spreadsheet." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/import.rst:208 +msgid "Once the desired attributes and values have been entered and saved in the spreadsheet, it's time to import and upload it into Odoo. To do that, navigate to :menuselection:`Sales app --> Configuration --> Attributes --> ⚙️ (gear) icon --> Import records --> Upload File`." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/import.rst:212 +msgid "Once the spreadsheet with the newly-configured attributes and values has been uploaded, click :guilabel:`Import`, and Odoo returns to the :guilabel:`Attributes` page. That's where those newly-added attributes and values can be found and edited, if necessary." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/import.rst:216 +msgid "As mentioned previously, when attributes and values have been added to the Odoo database, they can be used for existing or imported products." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/import.rst:220 #: ../../content/applications/sales/sales/products_prices/products/variants.rst:3 +#: ../../content/applications/sales/sales/products_prices/products/variants.rst:174 msgid "Product variants" msgstr "" +#: ../../content/applications/sales/sales/products_prices/products/import.rst:222 +msgid "When product attributes and values are configured in the database, they can be used on product import spreadsheets to add more information and detail to products being imported." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/import.rst:225 +msgid "To import products with product attributes and values, the product import template spreadsheet must be configured with specific :guilabel:`Product Attributes / Attribute`, :guilabel:`Product Attributes / Values`, and :guilabel:`Name` columns." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/import.rst:229 +msgid "There can be other columns, as well, but these columns are **required** in order to properly import products with specific variants." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/import.rst:-1 +msgid "Product variants spreadsheet with product attributes and variants for import purposes." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/import.rst:236 +msgid ":guilabel:`Name`: product name" +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/import.rst:237 +msgid ":guilabel:`Product Attributes / Attribute`: name of attribute" +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/import.rst:238 +msgid ":guilabel:`Product Attributes / Values`: values pertaining to the corresponding attribute" +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/import.rst:241 +msgid "To import multiple values, separate them by *just* a comma, **not** a comma followed by a space, in the product import template spreadsheet (e.g. `furniture,couch,home`)." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/import.rst:244 +msgid "When the desired products and product variants have been entered and saved in the spreadsheet, it's time to import and upload them into Odoo. To do that, navigate to :menuselection:`Sales app --> Products --> Products --> ⚙️ (gear) icon --> Import records --> Upload File`." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/import.rst:248 +msgid "Once the spreadsheet with the newly-configured products and product variants has been uploaded, click :guilabel:`Import`, and Odoo returns to the :guilabel:`Products` page. That's where the newly-added products can be found." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/import.rst:252 +msgid "To view and modify the attributes and variants on any products, select the desired product from the :guilabel:`Products` page, and click the :guilabel:`Attributes \\& Variants` tab." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/import.rst:256 +msgid ":doc:`variants`" +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/product_images.rst:3 +msgid "Product images with Google Images" +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/product_images.rst:5 +msgid "Having appropriate product images in Odoo is useful for a number of reasons. However, if a lot of products need images, assigning them can become incredibly time-consuming." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/product_images.rst:8 +msgid "Fortunately, by configuring the *Google Custom Search* API within an Odoo database, finding product images for products (based on their barcode) is extremely efficient." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/product_images.rst:16 +msgid "In order to utilize *Google Custom Search* within an Odoo database, both the database and the Google API must be properly configured." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/product_images.rst:20 +msgid "Free Google accounts allow users to select up to 100 free images per day. If a higher amount is needed, a billing upgrade is required." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/product_images.rst:26 +msgid "Google API dashboard" +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/product_images.rst:28 +msgid "Go to the `Google Cloud Platform API & Services `_ page to generate Google Custom Search API credentials. Then, log in with a Google account. Next, agree to their :guilabel:`Terms of Service` by checking the box, and clicking :guilabel:`Agree and Continue`." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/product_images.rst:32 +msgid "From here, select (or create) an API project to store the credentials. Start by giving it a memorable :guilabel:`Project Name`, select a :guilabel:`Location` (if any), then click :guilabel:`Create`." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/product_images.rst:35 +msgid "With the :guilabel:`Credentials` option selected in the left sidebar, click :guilabel:`Create Credentials`, and select :guilabel:`API key` from the drop-down menu." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/product_images.rst:0 +msgid "API & Services page on Google Cloud Platform." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/product_images.rst:42 +msgid "Doing so reveals an :guilabel:`API key created` pop-up window, containing a custom :guilabel:`API key`. Copy and save :guilabel:`Your API key` in the pop-up window -- it will be used later. Once the key is copied (and saved for later use), click :guilabel:`Close` to remove the pop-up window." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/product_images.rst:0 +msgid "The API key created pop-up window that appears." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/product_images.rst:50 +msgid "On this page, search for `Custom Search API`, and select it." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/product_images.rst:0 +msgid "Search bar containing \"Custom Search API\" on Google Cloud Platform." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/product_images.rst:56 +msgid "From the :guilabel:`Custom Search API` page, enable the API by clicking :guilabel:`Enable`." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/product_images.rst:0 +msgid "\"Custom Search API\" page with Enable button highlighted on Google Cloud Platform." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/product_images.rst:65 +msgid "Google Programmable Search dashboard" +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/product_images.rst:67 +msgid "Next, go to `Google Programmable Search Engine `_, and click either of the :guilabel:`Get started` buttons. Log in with a Google account, if not already logged in." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/product_images.rst:0 +msgid "Google Programmable Search Engine page with the Get Started buttons." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/product_images.rst:75 +msgid "On the :guilabel:`Create a new search engine` form, fill out the name of the search engine, along with what the engine should search, and be sure to enable :guilabel:`Image Search` and :guilabel:`SafeSearch`." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/product_images.rst:0 +msgid "Create new search engine form that appears with search engine configurations." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/product_images.rst:83 +msgid "Validate the form by clicking :guilabel:`Create`." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/product_images.rst:84 +msgid "Doing so reveals a new page with the heading: :guilabel:`Your new search engine has been created`." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/product_images.rst:0 +msgid "The Your New Search Engine Has Been Created page that appears with copy code." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/product_images.rst:91 +msgid "From this page, click :guilabel:`Customize` to open the :menuselection:`Overview --> Basic` page. Then, copy the ID in the :guilabel:`Search engine ID` field. This ID is needed for the Odoo configuration." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/product_images.rst:0 +msgid "Basic overview page with search engine ID field." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/product_images.rst:104 +msgid "In the Odoo database, go to the :menuselection:`Settings app` and scroll to the :guilabel:`Integrations` section. From here, check the box beside :guilabel:`Google Images`. Then, click :guilabel:`Save`." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/product_images.rst:0 +msgid "The Google Images setting in the Odoo Settings app page." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/product_images.rst:112 +msgid "Next, return to the :menuselection:`Settings app`, and scroll to the :guilabel:`Integrations` section. Then, enter the :guilabel:`API Key` and :guilabel:`Search Engine ID` in the fields beneath the :guilabel:`Google Images` feature." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/product_images.rst:115 +msgid "Click :guilabel:`Save`." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/product_images.rst:120 +msgid "Product images in Odoo with Google Custom Search API" +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/product_images.rst:122 +msgid "Adding images to products in Odoo can be done on any product or product variant. This process can be completed in any Odoo application that provides access to product pages (e.g. *Sales* app, *Inventory* app, etc.)." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/product_images.rst:126 +msgid "Below is a step-by-step guide detailing how to utilize the *Google Custom Search API* to assign images to products in Odoo using the Odoo *Sales* application:" +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/product_images.rst:129 +msgid "Navigate to the :guilabel:`Products` page in the *Sales* app (:menuselection:`Sales app --> Products --> Products`). Or, navigate to the :guilabel:`Product Variants` page in the *Sales* app (:menuselection:`Sales app --> Products --> Product Variants`)." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/product_images.rst:132 +msgid "Select the desired product that needs an image." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/product_images.rst:135 +msgid "Only products (or product variants) that have a barcode, but **not** an image, are processed." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/product_images.rst:137 +msgid "If a product with one or more variants is selected, each variant that matches the aforementioned criteria is processed." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/product_images.rst:140 +msgid "Click the :guilabel:`Action ⚙️ (gear)` icon on the product page, and select :guilabel:`Get Pictures from Google Images` from the menu that pops up." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/product_images.rst:0 +msgid "The Get Pictures from Google Images option from the Action drop-down menu in Odoo." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/product_images.rst:147 +msgid "On the pop-up window that appears, click :guilabel:`Get Pictures`." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/product_images.rst:0 +msgid "The pop-up that appears in which the user should click Get Picture in Odoo Sales." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/product_images.rst:153 +msgid "Once clicked, the image(s) will appear incrementally." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/product_images.rst:156 +msgid "Only the first 10 images are fetched immediately. If you selected more than 10, the rest are fetched as a background job." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/product_images.rst:159 +msgid "The background job processes about 100 images in a minute. If the quota authorized by Google (either with a free or a paid plan) is reached, the background job puts itself on hold for 24 hours. Then, it will continue where it stopped the day before." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/product_images.rst:164 +msgid "`Create, modify, or close your Google Cloud Billing account `_" +msgstr "" + #: ../../content/applications/sales/sales/products_prices/products/variants.rst:5 -msgid "Product variants are used to give single products a variety of different characteristics, such as size and color. Products using variants can be managed at the product template level (for all attributes and variants of that product), and/or at the variant level (for individual variants)." +msgid "Product variants are used to give single products a variety of different characteristics and options for customers to choose from, such as size, style, or color, just to name a few." msgstr "" -#: ../../content/applications/sales/sales/products_prices/products/variants.rst:9 -msgid "As an example, a company selling t-shirts may have the following product:" -msgstr "" - -#: ../../content/applications/sales/sales/products_prices/products/variants.rst:11 -msgid "T-shirt" +#: ../../content/applications/sales/sales/products_prices/products/variants.rst:8 +msgid "Products variants can be managed via their individual product template, or by navigating to either the :guilabel:`Product Variants` or :guilabel:`Attributes` page. All of these options are located within the Odoo *Sales* application." msgstr "" #: ../../content/applications/sales/sales/products_prices/products/variants.rst:13 +msgid "An apparel company has the following variant breakdown for one their best-selling t-shirts:" +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/variants.rst:15 +msgid "Unisex Classic Tee" +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/variants.rst:17 msgid "Color: Blue, Red, White, Black" msgstr "" -#: ../../content/applications/sales/sales/products_prices/products/variants.rst:14 -#: ../../content/applications/sales/sales/products_prices/products/variants.rst:131 +#: ../../content/applications/sales/sales/products_prices/products/variants.rst:18 msgid "Size: S, M, L, XL, XXL" msgstr "" -#: ../../content/applications/sales/sales/products_prices/products/variants.rst:16 -msgid "In this example, the **T-Shirt** is the product template, and **T-Shirt, S, Blue** is a product variant. **Color** and **size** are the attributes. **S** and **Blue** are values." +#: ../../content/applications/sales/sales/products_prices/products/variants.rst:20 +msgid "Here, the **T-shirt** is the product template, and **T-shirt: Blue, S** is a specific product variant." msgstr "" -#: ../../content/applications/sales/sales/products_prices/products/variants.rst:19 -msgid "The above example has a total of 20 different product variants (5 sizes x 4 colors). Each one of these has its own inventory, sales, etc." +#: ../../content/applications/sales/sales/products_prices/products/variants.rst:23 +msgid "**Color** and **Size** are *attributes*, and the corresponding options (like **Blue** and **S**) are *values*." msgstr "" #: ../../content/applications/sales/sales/products_prices/products/variants.rst:26 -msgid "Activating product variants" +msgid "In this instance, there is a total of twenty different product variants: four **Color** options multiplied by five **Size** options. Each variant has its own inventory count, sales totals, and other similar records in Odoo." msgstr "" -#: ../../content/applications/sales/sales/products_prices/products/variants.rst:28 -msgid "To use product variants, go to :menuselection:`Sales --> Configuration --> Settings --> Product Catalog`, and enable the :guilabel:`Variants` feature. Finally, click :guilabel:`Save` to apply the setting." +#: ../../content/applications/sales/sales/products_prices/products/variants.rst:31 +msgid ":doc:`/applications/websites/ecommerce/managing_products/variants`" msgstr "" -#: ../../content/applications/sales/sales/products_prices/products/variants.rst:-1 -msgid "Activating product variants." -msgstr "" - -#: ../../content/applications/sales/sales/products_prices/products/variants.rst:37 -msgid "Creating attributes" +#: ../../content/applications/sales/sales/products_prices/products/variants.rst:36 +msgid "To use product variants, the *Variants* setting **must** be activated in the Odoo *Sales* application." msgstr "" #: ../../content/applications/sales/sales/products_prices/products/variants.rst:39 -msgid "Attributes need to be created before product variants can be set up. Attributes can be accessed via :menuselection:`Sales --> Configuration --> Products --> Attributes`." +msgid "To do that, go to :menuselection:`Sales app --> Configuration --> Settings`, and locate the :guilabel:`Product Catalog` section at the top of the page." msgstr "" -#: ../../content/applications/sales/sales/products_prices/products/variants.rst:43 +#: ../../content/applications/sales/sales/products_prices/products/variants.rst:42 +msgid "In that section, check the box to enable the :guilabel:`Variants` feature." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/variants.rst:-1 +msgid "Activating product variants on the Settings page of the Odoo Sales application." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/variants.rst:48 +msgid "Then, click :guilabel:`Save` at the top of the :guilabel:`Settings` page." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/variants.rst:51 +msgid "Attributes" +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/variants.rst:53 +msgid "Before product variants can be set up, attributes **must** be created. To create, manage, and modify attributes, navigate to :menuselection:`Sales app --> Configuration --> Attributes`." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/variants.rst:57 msgid "The order of attributes on the :guilabel:`Attributes` page dictates how they appear on the :guilabel:`Product Configurator`, :guilabel:`Point of Sale` dashboard, and :guilabel:`eCommerce` pages." msgstr "" -#: ../../content/applications/sales/sales/products_prices/products/variants.rst:47 -msgid "To create a new attribute, click :guilabel:`Create`. First, choose an attribute name, such as \"Color\" or \"Size.\"" +#: ../../content/applications/sales/sales/products_prices/products/variants.rst:61 +msgid "To create a new attribute from the :guilabel:`Attributes` page, click :guilabel:`New`. Doing so reveals a blank attributes form that can be customized and configured in a number of ways." msgstr "" #: ../../content/applications/sales/sales/products_prices/products/variants.rst:-1 -msgid "Attribute creation window." +msgid "A blank attribute creation form in the Odoo Sales application." msgstr "" -#: ../../content/applications/sales/sales/products_prices/products/variants.rst:54 -msgid "Then, select a :guilabel:`Display Type`, which determines how this product will be shown on the :guilabel:`eCommerce` page, :guilabel:`Point of Sale` dashboard, and :guilabel:`Product Configurator`." -msgstr "" - -#: ../../content/applications/sales/sales/products_prices/products/variants.rst:58 -msgid ":guilabel:`Radio`: options appear in a bullet style list." -msgstr "" - -#: ../../content/applications/sales/sales/products_prices/products/variants.rst:59 -msgid ":guilabel:`Select`: options appear in a dropdown menu." -msgstr "" - -#: ../../content/applications/sales/sales/products_prices/products/variants.rst:60 -msgid ":guilabel:`Color`: options appear as small colored squares, which reflect any HTML color codes set." -msgstr "" - -#: ../../content/applications/sales/sales/products_prices/products/variants.rst:-1 -msgid "Display Types on Product Configurator." -msgstr "" - -#: ../../content/applications/sales/sales/products_prices/products/variants.rst:67 -msgid "The :guilabel:`Variants Creation Mode` informs Odoo when to automatically create a new variant once an attribute is added to a product." +#: ../../content/applications/sales/sales/products_prices/products/variants.rst:68 +msgid "First, create an :guilabel:`Attribute Name`, such as `Color` or `Size`." msgstr "" #: ../../content/applications/sales/sales/products_prices/products/variants.rst:70 -msgid ":guilabel:`Instantly`: creates all possible variants as soon as attributes and values are added to a product template." -msgstr "" - -#: ../../content/applications/sales/sales/products_prices/products/variants.rst:72 -msgid ":guilabel:`Dynamically`: creates variants only when corresponding attributes and values are added to a sales order." +msgid "Next, in the optional :guilabel:`Category` field, select a category from a drop-down menu to group similar attributes under the same section for added specificity and organization." msgstr "" #: ../../content/applications/sales/sales/products_prices/products/variants.rst:74 -msgid ":guilabel:`Never`: never automatically creates variants." +msgid "To view the details related to the attribute category selected, click the internal link :guilabel:`➡️ (arrow)` icon to the far-right of the :guilabel:`Category` field. Doing so reveals that attribute category's detail form." msgstr "" -#: ../../content/applications/sales/sales/products_prices/products/variants.rst:77 -msgid "Once added to a product, an attribute's :guilabel:`Variants Creation Mode` cannot be edited." -msgstr "" - -#: ../../content/applications/sales/sales/products_prices/products/variants.rst:79 -msgid "Values should be added to an attribute before saving, but more values can be added at any time, if needed. To add a value, click :guilabel:`Add a line`. From there, you can:" +#: ../../content/applications/sales/sales/products_prices/products/variants.rst:-1 +msgid "A standard attribute category detail page accessible via its internal link arrow icon." msgstr "" #: ../../content/applications/sales/sales/products_prices/products/variants.rst:82 -msgid "Type in the value's name." +msgid "Here, the :guilabel:`Category Name` and :guilabel:`Sequence` is displayed at the top. Followed by :guilabel:`Related Attributes` associated with the category. These attributes can be dragged-and-dropped into a desirable order of priority." msgstr "" -#: ../../content/applications/sales/sales/products_prices/products/variants.rst:83 -msgid "Check a box to indicate whether or not the value is custom (i.e. the customer provides unique specifications)." +#: ../../content/applications/sales/sales/products_prices/products/variants.rst:86 +msgid "Attributes can be directly added to the category, as well, by clicking :guilabel:`Add a line`." msgstr "" -#: ../../content/applications/sales/sales/products_prices/products/variants.rst:85 -msgid "Specifically for colors, add an HTML color code to make it even easier for salespeople and customers to know what they're selecting." +#: ../../content/applications/sales/sales/products_prices/products/variants.rst:89 +msgid "To create an attribute category directly from this field, start typing the name of the new category, then select either :guilabel:`Create` or :guilabel:`Create and edit...` from the drop-down menu that appears." msgstr "" -#: ../../content/applications/sales/sales/products_prices/products/variants.rst:88 -msgid "A color code can be selected either by dragging the slider around or by entering a specific HTML color code (e.g. #FF0077)." +#: ../../content/applications/sales/sales/products_prices/products/variants.rst:93 +msgid "Clicking :guilabel:`Create` creates the category, which can be modified later. Clicking :guilabel:`Create and edit...` creates the category and reveals a :guilabel:`Create Category` pop-up window, in which the new attribute category can be configured and customized." msgstr "" -#: ../../content/applications/sales/sales/products_prices/products/variants.rst:-1 -msgid "Selecting a color." -msgstr "" - -#: ../../content/applications/sales/sales/products_prices/products/variants.rst:95 -msgid "Finally, click :guilabel:`Save` to finish creating the attribute." -msgstr "" - -#: ../../content/applications/sales/sales/products_prices/products/variants.rst:98 -msgid "Attributes can also be created directly from the product template by adding a new line and typing the name into the :guilabel:`Variants` tab." +#: ../../content/applications/sales/sales/products_prices/products/variants.rst:97 +msgid "Beneath the :guilabel:`Category` field are the :guilabel:`Display Type` options. The :guilabel:`Display Type` determines how this product is shown on the online store, :guilabel:`Point of Sale` dashboard, and :guilabel:`Product Configurator`." msgstr "" #: ../../content/applications/sales/sales/products_prices/products/variants.rst:101 -msgid "After an attribute is added to a product, a new tab appears on the attribute's page called :guilabel:`Related Products`. This tab lists every product in the database that is currently using the attribute." +msgid "The :guilabel:`Display Type` options are:" +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/variants.rst:103 +msgid ":guilabel:`Radio`: options appear in a bullet-style list on the product page of the online store." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/variants.rst:104 +msgid ":guilabel:`Pills`: options appear as selectable buttons on the product page of the online store." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/variants.rst:105 +msgid ":guilabel:`Select`: options appear in a drop-down menu on the product page of the online store." msgstr "" #: ../../content/applications/sales/sales/products_prices/products/variants.rst:106 -msgid "Creating product variants" +msgid ":guilabel:`Color`: options appear as small, colored squares, which reflect any HTML color codes set, on the product page of the online store." msgstr "" -#: ../../content/applications/sales/sales/products_prices/products/variants.rst:108 -msgid "After creating an attribute, use the attribute to create a product variant by going to :menuselection:`Sales --> Products --> Products`. Then, select an existing product and click :guilabel:`Edit`, or create a new product by clicking :guilabel:`Create`." +#: ../../content/applications/sales/sales/products_prices/products/variants.rst:-1 +msgid "Display Types on Product Configurator on the online store in Odoo." msgstr "" -#: ../../content/applications/sales/sales/products_prices/products/variants.rst:112 -msgid "The :guilabel:`Variants` smart button at the top of the product template indicates the number of currently configured variants on the product." +#: ../../content/applications/sales/sales/products_prices/products/variants.rst:113 +msgid "The :guilabel:`Variants Creation Mode` field informs Odoo when to automatically create a new variant once an attribute is added to a product." msgstr "" -#: ../../content/applications/sales/sales/products_prices/products/variants.rst:115 -msgid "To add a new variant, click on the :guilabel:`Variants` tab, then click on :guilabel:`Add a line` to add any attributes and values. When all the attributes and values have been added, click :guilabel:`Save`." +#: ../../content/applications/sales/sales/products_prices/products/variants.rst:116 +msgid ":guilabel:`Instantly`: creates all possible variants as soon as attributes and values are added to a product template." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/variants.rst:118 +msgid ":guilabel:`Dynamically`: creates variants **only** when corresponding attributes and values are added to a sales order." msgstr "" #: ../../content/applications/sales/sales/products_prices/products/variants.rst:120 -msgid "Similar product variant creation processes are accessible through the Purchase, Inventory, and eCommerce applications." +msgid ":guilabel:`Never (option)`: never automatically creates variants." msgstr "" -#: ../../content/applications/sales/sales/products_prices/products/variants.rst:124 -msgid "Managing product exclusions" +#: ../../content/applications/sales/sales/products_prices/products/variants.rst:123 +msgid "Once added to a product, an attribute's :guilabel:`Variants Creation Mode` cannot be edited." msgstr "" -#: ../../content/applications/sales/sales/products_prices/products/variants.rst:126 -msgid "The following examples are all based on a product template that has two attributes:" +#: ../../content/applications/sales/sales/products_prices/products/variants.rst:125 +msgid "Lastly, the :guilabel:`eCommerce Filter Visibility` field determines whether these attribute options are visible to the customer on the front-end, as they shop on the online store." msgstr "" #: ../../content/applications/sales/sales/products_prices/products/variants.rst:128 -msgid "T-Shirt" +msgid ":guilabel:`Visible`: the attribute values are visible to customers on the front-end." msgstr "" -#: ../../content/applications/sales/sales/products_prices/products/variants.rst:130 -msgid "Color: Blue, Red, White" +#: ../../content/applications/sales/sales/products_prices/products/variants.rst:129 +msgid ":guilabel:`Hidden`: the attribute values are hidden from customers on the front-end." msgstr "" -#: ../../content/applications/sales/sales/products_prices/products/variants.rst:133 -msgid "With the above product template, there are 15 different t-shirt variants in three different colors and five different sizes. If the white t-shirts are not available in the XXL size, then that variant can be deactivated." +#: ../../content/applications/sales/sales/products_prices/products/variants.rst:132 +msgid "Attribute values" +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/variants.rst:134 +msgid "Attribute values should be added to the :guilabel:`Attribute Values` tab. Values can be added to an attribute at any time, if needed." msgstr "" #: ../../content/applications/sales/sales/products_prices/products/variants.rst:137 -msgid "To deactivate a particular product variant, go to :menuselection:`Sales --> Products --> Products` and select the relevant product. Next, click on the :guilabel:`Configure` button next to the relevant attribute value. Then select the relevant value (in this example, the :guilabel:`White Color` attribute), and then click on :guilabel:`Edit`." +msgid "To add a value, click :guilabel:`Add a line` in the :guilabel:`Attribute Values` tab." msgstr "" -#: ../../content/applications/sales/sales/products_prices/products/variants.rst:142 -msgid "In the :guilabel:`Exclude for` section, click :guilabel:`Add a line` and select any product(s) and/or specific attribute values that are currently unavailable. Finally, click :guilabel:`Save` to apply the setting, and Odoo will automatically show the product variant as unavailable on the eCommerce page." +#: ../../content/applications/sales/sales/products_prices/products/variants.rst:139 +msgid "Then, enter the name of the value in the :guilabel:`Value` column. Next, check the box in the :guilabel:`Is custom value` column, if the value is custom (i.e. the customer gets to provide unique specifications that are specific to this particular value)." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/variants.rst:144 +msgid "If the :guilabel:`Display Type` - :guilabel:`Color` option is selected, the option to add an HTML color code will appear to the far-right of the value line, to make it easier for salespeople and customers to know exactly what color option they're choosing." msgstr "" #: ../../content/applications/sales/sales/products_prices/products/variants.rst:-1 -msgid "Excluding attributes." +msgid "Attribute values tab when add a line is clicked, showing the custom columns." msgstr "" #: ../../content/applications/sales/sales/products_prices/products/variants.rst:152 -msgid "Setting a price per variant" -msgstr "" - -#: ../../content/applications/sales/sales/products_prices/products/variants.rst:154 -msgid "Extra costs can be added to a product's standard price for specific product variants." -msgstr "" - -#: ../../content/applications/sales/sales/products_prices/products/variants.rst:156 -msgid "To do this, open :menuselection:`Sales --> Products --> Products`, and click on the relevant product. Next, click on :guilabel:`Configure Variants` to access the list of product variant values." -msgstr "" - -#: ../../content/applications/sales/sales/products_prices/products/variants.rst:160 -msgid "Then, click on a variant value, and :guilabel:`Edit`. In the :guilabel:`Value Price Extra` field, type in the additional cost for this particular value. This amount is added to the standard price. Finally, click :guilabel:`Save` to apply the extra price to the value." +msgid "To choose a color, click the blank circle in the :guilabel:`Color` column, which reveals an HTML color selector pop-up window." msgstr "" #: ../../content/applications/sales/sales/products_prices/products/variants.rst:-1 -msgid "Value Price Extra setting." +msgid "Selecting a color from the HTML color pop-up window that appears on attribute form." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/variants.rst:159 +msgid "In this pop-up window, select a specific color by dragging the color slider to a particular hue, and clicking on the color portion directly on the color gradient window." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/variants.rst:162 +msgid "Or, choose a specific color by clicking the *dropper* icon, and selecting a desired color that's currently clickable on the screen." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/variants.rst:166 +msgid "Attributes can also be created directly from the product template by adding a new line and typing the name into the :guilabel:`Variants` tab." msgstr "" #: ../../content/applications/sales/sales/products_prices/products/variants.rst:169 +msgid "Once an attribute is added to a product, that product is listed and accessible, via the attribute's :guilabel:`Related Products` smart button. That button lists every product in the database currently using that attribute." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/variants.rst:176 +msgid "Once an attribute is created, use the attribute (and its values) to create a product variant. To do that, go to :menuselection:`Sales app --> Products --> Products`, and select an existing product to view that desired product's form. Or, click :guilabel:`Create` to create a new product, to which a product variant can be added." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/variants.rst:181 +msgid "On the product form, click the :guilabel:`Attributes \\& Variants` tab to view, manage, and modify attributes and values for the product." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/variants.rst:-1 +msgid "The attributes and values tab on a typical product form in Odoo Sales." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/variants.rst:188 +msgid "To add an attribute to a product, and subsequent attribute values, click :guilabel:`Add a line` in the :guilabel:`Attributes \\& Variants` tab. Then, choose the desired attribute from the drop-down menu that appears." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/variants.rst:193 +msgid "Attributes can be created directly from the :guilabel:`Attributes \\& Variants` tab of a product form. To do that, start typing the name of the new attribute in the blank field, and select either :guilabel:`Create` or :guilabel:`Create and edit...` from the mini drop-down menu that appears." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/variants.rst:198 +msgid "Clicking :guilabel:`Create` creates the attribute, which can be customized later. Clicking :guilabel:`Create and edit...` creates the attribute, and a :guilabel:`Create Attribute` pop-up form appears. In the pop-up form, proceed to modify the attribute in a number of ways." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/variants.rst:202 +msgid "Once an attribute is selected in the :guilabel:`Attribute` column, proceed to select the specific attribute values to apply to the product, via the drop-down menu available in the :guilabel:`Values` column." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/variants.rst:207 +msgid "There is no limit to how many values can be added." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/variants.rst:210 +msgid "Similar product variant creation processes are accessible through the Purchase, Inventory, and eCommerce applications." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/variants.rst:214 +msgid "Configure variants" +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/variants.rst:216 +msgid "To the far-right of the attribute line is a :guilabel:`Configure` button. When clicked, Odoo reveals a separate page showcasing those specific :guilabel:`Product Variant Values`." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/variants.rst:-1 +msgid "The Product Variant Values page accessible via the Configure button on a product form." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/variants.rst:223 +msgid "Here, the specific :guilabel:`Value` name, :guilabel:`HTML Color Index` (if applicable), and :guilabel:`Value Price Extra` are viewable." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/variants.rst:227 +msgid "The :guilabel:`Value Price Extra` represents the increase in the sales price if the attribute is selected." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/variants.rst:230 +msgid "When a value is clicked on the :guilabel:`Product Variant Values` page, Odoo reveals a separate page, detailing that value's related details." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/variants.rst:-1 +msgid "A Product Variant Values page accessible via the Product Variants Values general page." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/variants.rst:237 +msgid "On the specific product variant detail page, the :guilabel:`Value` and :guilabel:`Value Price Extra` fields can be found, along with an :guilabel:`Exclude for` field." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/variants.rst:240 +msgid "In the :guilabel:`Exclude for` field, different :guilabel:`Product Templates` and specific :guilabel:`Attribute Values` can be added. When added, this specific attribute value will be excluded from those specific products." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/variants.rst:245 +msgid "Variants smart button" +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/variants.rst:247 +msgid "When a product has attributes and variants configured in its :guilabel:`Attributes \\& Variants` tab, a :guilabel:`Variants` smart button appears at the top of the product form. The :guilabel:`Variants` smart button indicates how many variants are currently configured for that specific product." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/variants.rst:-1 +msgid "The variants smart button at the top of the product form in Odoo Sales." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/variants.rst:255 +msgid "When the :guilabel:`Variants` smart button is clicked, Odoo reveals a separate page showcasing all the specific product variant combinations configured for that specific product." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/variants.rst:-1 +msgid "The variants page accessible via the variants smart button on the product form in Odoo." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/variants.rst:263 msgid "Impact of variants" msgstr "" -#: ../../content/applications/sales/sales/products_prices/products/variants.rst:171 -msgid ":guilabel:`Barcode`: barcodes are associated with each variant instead of the product template. Each individual variant can have its own unique barcode/SKU." +#: ../../content/applications/sales/sales/products_prices/products/variants.rst:265 +msgid "In addition to offering more detailed product options to customers, product variants have their own impacts that can be taken advantage of throughout the Odoo database." msgstr "" -#: ../../content/applications/sales/sales/products_prices/products/variants.rst:174 -msgid ":guilabel:`Price`: every product variant has its own public price, which is the sum of the product template price and any extra charges for particular attributes. For example, a red shirt's cost is $23 because the shirt's template price is $20, plus an additional $3 for the red color variant. Pricelist rules can be configured to apply to the product template or to the variant." +#: ../../content/applications/sales/sales/products_prices/products/variants.rst:268 +msgid ":guilabel:`Barcode`: barcodes are associated with each variant, instead of the product template. Each individual variant can have its own unique barcode/SKU." msgstr "" -#: ../../content/applications/sales/sales/products_prices/products/variants.rst:180 +#: ../../content/applications/sales/sales/products_prices/products/variants.rst:270 +msgid ":guilabel:`Price`: every product variant has its own public price, which is the sum of the product template price *and* any extra charges for particular attributes." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/variants.rst:274 +msgid "A red shirt's sales price is $23 -- because the shirt's template price is $20, plus an additional $3 for the red color variant. Pricelist rules can be configured to apply to the product template, or to the variant." +msgstr "" + +#: ../../content/applications/sales/sales/products_prices/products/variants.rst:278 msgid ":guilabel:`Inventory`: inventory is counted for each individual product variant. On the product template form, the inventory reflects the sum of all variants, but the actual inventory is computed by individual variants." msgstr "" -#: ../../content/applications/sales/sales/products_prices/products/variants.rst:184 +#: ../../content/applications/sales/sales/products_prices/products/variants.rst:281 msgid ":guilabel:`Picture`: each product variant can have its own specific picture." msgstr "" -#: ../../content/applications/sales/sales/products_prices/products/variants.rst:187 +#: ../../content/applications/sales/sales/products_prices/products/variants.rst:284 msgid "Changes to the product template automatically apply to every variant of that product." msgstr "" +#: ../../content/applications/sales/sales/products_prices/products/variants.rst:287 +msgid ":doc:`import`" +msgstr "" + #: ../../content/applications/sales/sales/products_prices/returns.rst:3 msgid "Returns and refunds" msgstr "" diff --git a/locale/sources/services.pot b/locale/sources/services.pot index fd0ff49b6..d2f61f760 100644 --- a/locale/sources/services.pot +++ b/locale/sources/services.pot @@ -8,7 +8,7 @@ msgid "" msgstr "" "Project-Id-Version: Odoo saas-16.1\n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2023-12-19 13:26+0000\n" +"POT-Creation-Date: 2024-01-19 10:30+0000\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME \n" "Language-Team: LANGUAGE \n" @@ -2537,7 +2537,7 @@ msgid "Project settings" msgstr "" #: ../../content/applications/services/project/project_management.rst:58 -msgid "`Odoo Tutorials: Customize your project `_" +msgid "`Odoo Tutorials: Customize projects `_" msgstr "" #: ../../content/applications/services/project/project_management.rst:61 diff --git a/locale/sources/websites.pot b/locale/sources/websites.pot index a84f40eb3..0bcd08bbb 100644 --- a/locale/sources/websites.pot +++ b/locale/sources/websites.pot @@ -8,7 +8,7 @@ msgid "" msgstr "" "Project-Id-Version: Odoo saas-16.1\n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2023-12-19 13:26+0000\n" +"POT-Creation-Date: 2024-01-19 10:30+0000\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME \n" "Language-Team: LANGUAGE \n" @@ -20,6 +20,206 @@ msgstr "" msgid "Websites" msgstr "" +#: ../../content/applications/websites/blog.rst:3 +msgid "Blog" +msgstr "" + +#: ../../content/applications/websites/blog.rst:5 +msgid "**Odoo Blog** allows you to create and manage blog posts on your website to engage your audience and build a community." +msgstr "" + +#: ../../content/applications/websites/blog.rst:9 +msgid "If the Blog module is not yet installed, click :guilabel:`+New` on the website builder, select :guilabel:`Blog Post`, and click :guilabel:`Install`." +msgstr "" + +#: ../../content/applications/websites/blog.rst:13 +msgid "Creating a blog" +msgstr "" + +#: ../../content/applications/websites/blog.rst:15 +msgid "To create or edit a blog, go to :menuselection:`Website --> Configuration --> Blogs: Blogs`. Click :guilabel:`New`, and enter the :guilabel:`Blog Name` and the :guilabel:`Blog Subtitle`." +msgstr "" + +#: ../../content/applications/websites/blog.rst:18 +msgid "The :guilabel:`Blog` menu item is added to your website's menu the first time you create a blog and gathers all your blogs." +msgstr "" + +#: ../../content/applications/websites/blog.rst:22 +msgid "Adding a blog post" +msgstr "" + +#: ../../content/applications/websites/blog.rst:24 +msgid "Go to your website, click :guilabel:`+New` in the top-right corner, and select :guilabel:`Blog Post`. In the pop-up, **select the blog** where the post should appear, write the post's :guilabel:`Title`, and :guilabel:`Save`. You can then write the post's content and customize the page using the website builder." +msgstr "" + +#: ../../content/applications/websites/blog.rst:30 +msgid "Illustrate your articles with copyright-free images from :doc:`Unsplash `." +msgstr "" + +#: ../../content/applications/websites/blog.rst:32 +msgid "Type `/` in the text editor to format and add elements to your text." +msgstr "" + +#: ../../content/applications/websites/blog.rst:35 +msgid "Don't forget to toggle the :guilabel:`Unpublished` switch in the top-right corner to publish your post." +msgstr "" + +#: ../../content/applications/websites/blog.rst:39 +msgid "Using tags" +msgstr "" + +#: ../../content/applications/websites/blog.rst:41 +msgid "Tags let visitors filter all posts sharing the same tag. By default, they are displayed at the bottom of posts, but can also be displayed on the blog's main page. To do so, click :menuselection:`Edit --> Customize` and enable the :guilabel:`Sidebar`. By default, the sidebar's :guilabel:`Tags List` is enabled." +msgstr "" + +#: ../../content/applications/websites/blog.rst:46 +msgid "To create a tag, go to :menuselection:`Website --> Configuration --> Blogs: Tags` and click :guilabel:`New`. Fill in the:" +msgstr "" + +#: ../../content/applications/websites/blog.rst:49 +msgid ":guilabel:`Name`" +msgstr "" + +#: ../../content/applications/websites/blog.rst:50 +msgid ":guilabel:`Category`: tag categories let you group tags displayed on the sidebar by theme." +msgstr "" + +#: ../../content/applications/websites/blog.rst:51 +msgid ":guilabel:`Used in`: to apply the tag to existing blog posts, click :guilabel:`Add a line`, select the posts, and click :guilabel:`Select`." +msgstr "" + +#: ../../content/applications/websites/blog.rst:54 +msgid "You can add and create tags directly from posts by clicking :menuselection:`Edit --> Customize` and select the post's cover. Under :guilabel:`Tags`, click :guilabel:`Choose a record...`, and select or create a tag." +msgstr "" + +#: ../../content/applications/websites/blog.rst:-1 +msgid "Adding a tag to a blog post" +msgstr "" + +#: ../../content/applications/websites/blog.rst:62 +msgid "To manage tag categories, go to :menuselection:`Website --> Configuration --> Blogs: Tag Categories`." +msgstr "" + +#: ../../content/applications/websites/blog.rst:66 +msgid "Customizing blog homepages" +msgstr "" + +#: ../../content/applications/websites/blog.rst:68 +msgid "Customize the content of blog homepages by opening a blog homepage and clicking :menuselection:`Edit --> Customize`." +msgstr "" + +#: ../../content/applications/websites/blog.rst:72 +msgid "Settings apply to **all** blogs homepages." +msgstr "" + +#: ../../content/applications/websites/blog.rst:74 +msgid ":guilabel:`Top Banner`: :guilabel:`Name/Latest Post` displays the title of the latest post on the top banner, while :guilabel:`Drop Zone for Building Blocks` removes the top banner and lets you use any building block instead." +msgstr "" + +#: ../../content/applications/websites/blog.rst:78 +msgid ":guilabel:`Layout`: organizes posts as a :guilabel:`Grid` or :guilabel:`List`." +msgstr "" + +#: ../../content/applications/websites/blog.rst:80 +msgid ":guilabel:`Cards`: adds a *card* effect." +msgstr "" + +#: ../../content/applications/websites/blog.rst:81 +msgid ":guilabel:`Increase Readability`: improves the text's readability." +msgstr "" + +#: ../../content/applications/websites/blog.rst:83 +msgid ":guilabel:`Sidebar`: displays a sidebar containing an :guilabel:`About us` section." +msgstr "" + +#: ../../content/applications/websites/blog.rst:85 +msgid ":guilabel:`Archives`: allows visitors to select a month and filter all posts created during that month." +msgstr "" + +#: ../../content/applications/websites/blog.rst:87 +msgid ":guilabel:`Follow Us`: displays links to your social media networks. They can be configured using the Social Media building block somewhere on your website." +msgstr "" + +#: ../../content/applications/websites/blog.rst:89 +msgid ":guilabel:`Tags List`: displays all tags related to a blog. Visitors can select a tag to filter all related posts." +msgstr "" + +#: ../../content/applications/websites/blog.rst:92 +msgid ":guilabel:`Posts List`: :guilabel:`Cover` displays the posts' images, and :guilabel:`No Cover` hides them." +msgstr "" + +#: ../../content/applications/websites/blog.rst:95 +msgid ":guilabel:`Author`: displays the posts' authors." +msgstr "" + +#: ../../content/applications/websites/blog.rst:96 +msgid ":guilabel:`Comments/Views Stats`: displays the posts' number of comments and views." +msgstr "" + +#: ../../content/applications/websites/blog.rst:97 +msgid ":guilabel:`Teaser & Tags`: displays the posts' first sentences and tags." +msgstr "" + +#: ../../content/applications/websites/blog.rst:100 +msgid "Customizing blog posts" +msgstr "" + +#: ../../content/applications/websites/blog.rst:102 +msgid "Customize posts by opening a blog post and clicking :menuselection:`Edit --> Customize`." +msgstr "" + +#: ../../content/applications/websites/blog.rst:105 +msgid "Settings apply to **all** posts." +msgstr "" + +#: ../../content/applications/websites/blog.rst:107 +msgid ":guilabel:`Layout`: :guilabel:`Title Inside Cover` displays the title inside the cover image, and :guilabel:`Title above Cover` displays it above." +msgstr "" + +#: ../../content/applications/websites/blog.rst:110 +msgid ":guilabel:`Increase Readability`: increases the text's readability." +msgstr "" + +#: ../../content/applications/websites/blog.rst:112 +msgid ":guilabel:`Sidebar`: displays the :guilabel:`Sidebar` and additional options:" +msgstr "" + +#: ../../content/applications/websites/blog.rst:114 +msgid ":guilabel:`Archive`: allows visitors to select a month and filter all posts created during that month." +msgstr "" + +#: ../../content/applications/websites/blog.rst:116 +msgid ":guilabel:`Author`: displays the post's author and creation date." +msgstr "" + +#: ../../content/applications/websites/blog.rst:117 +msgid ":guilabel:`Blog List`: displays links to all your blogs." +msgstr "" + +#: ../../content/applications/websites/blog.rst:118 +msgid ":guilabel:`Share Links`: displays share buttons to several social networks." +msgstr "" + +#: ../../content/applications/websites/blog.rst:119 +msgid ":guilabel:`Tags`: displays the post's tags." +msgstr "" + +#: ../../content/applications/websites/blog.rst:121 +msgid ":guilabel:`Breadcrumb`: displays the path to the post." +msgstr "" + +#: ../../content/applications/websites/blog.rst:123 +msgid ":guilabel:`Bottom`: :guilabel:`Next Article` displays the next post at the bottom, and :guilabel:`Comments` enable visitors to comment on the post." +msgstr "" + +#: ../../content/applications/websites/blog.rst:126 +msgid ":guilabel:`Select To Tweet`: visitors are offered to tweet the text they select." +msgstr "" + +#: ../../content/applications/websites/blog.rst:129 +msgid "Use :ref:`Plausible ` to keep track of the traffic on your blog." +msgstr "" + #: ../../content/applications/websites/ecommerce.rst:8 msgid "eCommerce" msgstr "" @@ -3012,26 +3212,26 @@ msgid "If this channel should only be available to site visitors in specific cou msgstr "" #: ../../content/applications/websites/livechat.rst:185 -msgid "In order to track the geographical location of visitors, :guilabel:`GeoIP` must be installed on the database. While this feature is installed by default on *Odoo Online*, *On-Premise* databases will require additional :doc:`setup steps `." +msgid "In order to track the geographical location of visitors, :guilabel:`GeoIP` must be installed on the database. While this feature is installed by default on *Odoo Online*, *On-Premise* databases will require additional :doc:`setup steps `." msgstr "" -#: ../../content/applications/websites/livechat.rst:191 +#: ../../content/applications/websites/livechat.rst:190 msgid "Widget" msgstr "" -#: ../../content/applications/websites/livechat.rst:193 +#: ../../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." msgstr "" -#: ../../content/applications/websites/livechat.rst:197 +#: ../../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." msgstr "" -#: ../../content/applications/websites/livechat.rst:201 +#: ../../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." msgstr "" -#: ../../content/applications/websites/livechat.rst:204 +#: ../../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." msgstr "" @@ -3039,23 +3239,23 @@ msgstr "" msgid "View of the widget tab for Odoo Live Chat." msgstr "" -#: ../../content/applications/websites/livechat.rst:213 +#: ../../content/applications/websites/livechat.rst:212 msgid "Participate in a conversation" msgstr "" -#: ../../content/applications/websites/livechat.rst:215 +#: ../../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." msgstr "" -#: ../../content/applications/websites/livechat.rst:220 +#: ../../content/applications/websites/livechat.rst:219 msgid "Set an online chat name" msgstr "" -#: ../../content/applications/websites/livechat.rst:222 +#: ../../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." msgstr "" -#: ../../content/applications/websites/livechat.rst:225 +#: ../../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." msgstr "" @@ -3063,11 +3263,11 @@ msgstr "" msgid "View of the My Profile option in Odoo." msgstr "" -#: ../../content/applications/websites/livechat.rst:234 +#: ../../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:238 +#: ../../content/applications/websites/livechat.rst:237 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 "" @@ -3075,15 +3275,15 @@ msgstr "" msgid "View of user profile in Odoo, emphasizing the Online Chat name field." msgstr "" -#: ../../content/applications/websites/livechat.rst:247 +#: ../../content/applications/websites/livechat.rst:246 msgid "Join or leave a channel" msgstr "" -#: ../../content/applications/websites/livechat.rst:249 +#: ../../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." msgstr "" -#: ../../content/applications/websites/livechat.rst:252 +#: ../../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." msgstr "" @@ -3091,19 +3291,19 @@ msgstr "" msgid "View of a channel form and the option to join a channel for Odoo Live Chat." msgstr "" -#: ../../content/applications/websites/livechat.rst:260 +#: ../../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." msgstr "" -#: ../../content/applications/websites/livechat.rst:264 +#: ../../content/applications/websites/livechat.rst:263 msgid "Manage live chat requests" msgstr "" -#: ../../content/applications/websites/livechat.rst:266 +#: ../../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." msgstr "" -#: ../../content/applications/websites/livechat.rst:271 +#: ../../content/applications/websites/livechat.rst:270 msgid "Conversations can also be accessed by clicking the :guilabel:`Conversations` icon in the menu bar." msgstr "" @@ -3111,7 +3311,7 @@ msgstr "" msgid "View of the menu bar in Odoo emphasizing the conversations icon." msgstr "" -#: ../../content/applications/websites/livechat.rst:278 +#: ../../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." msgstr "" @@ -3119,15 +3319,15 @@ msgstr "" msgid "View of the discuss application with a message sent through live chat in Odoo." msgstr "" -#: ../../content/applications/websites/livechat.rst:285 +#: ../../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." msgstr "" -#: ../../content/applications/websites/livechat.rst:289 +#: ../../content/applications/websites/livechat.rst:288 msgid ":doc:`Get Started with Discuss `" msgstr "" -#: ../../content/applications/websites/livechat.rst:290 +#: ../../content/applications/websites/livechat.rst:289 msgid ":doc:`/applications/websites/livechat/responses`" msgstr "" @@ -3824,6 +4024,94 @@ msgstr "" msgid "Discover the best **Open-Source Website Builder** and learn how to build beautiful websites that convert visitors into leads or revenues." msgstr "" +#: ../../content/applications/websites/website/configuration/address_autocomplete.rst:3 +msgid "Address autocomplete" +msgstr "" + +#: ../../content/applications/websites/website/configuration/address_autocomplete.rst:5 +msgid "You can use the Google Places API on your website to ensure that your users' delivery addresses exist and are understood by the carrier. The Google Places API allows developers to access detailed information about places using HTTP requests. The autocompletion predicts a list of places when the user starts typing the address." +msgstr "" + +#: ../../content/applications/websites/website/configuration/address_autocomplete.rst:-1 +msgid "Address autocomplete example" +msgstr "" + +#: ../../content/applications/websites/website/configuration/address_autocomplete.rst:13 +msgid "`Google Maps Platform `_" +msgstr "" + +#: ../../content/applications/websites/website/configuration/address_autocomplete.rst:14 +msgid "`Google Developers Documentation: Google Places API `_" +msgstr "" + +#: ../../content/applications/websites/website/configuration/address_autocomplete.rst:18 +msgid "To do so, go to :menuselection:`Website --> Configuration --> Settings` and enable :guilabel:`Address Autocomplete` in the :guilabel:`SEO` section." +msgstr "" + +#: ../../content/applications/websites/website/configuration/address_autocomplete.rst:-1 +msgid "Enable address autocomplete" +msgstr "" + +#: ../../content/applications/websites/website/configuration/address_autocomplete.rst:24 +msgid "Insert your :guilabel:`Google Places API key` in the :guilabel:`API Key` field. If you don't have one, create yours on the `Google Cloud Console `_ and follow these steps." +msgstr "" + +#: ../../content/applications/websites/website/configuration/address_autocomplete.rst:28 +msgid "Step 1: Enable the Google Places API" +msgstr "" + +#: ../../content/applications/websites/website/configuration/address_autocomplete.rst:30 +msgid "**Create a New Project:**" +msgstr "" + +#: ../../content/applications/websites/website/configuration/address_autocomplete.rst:32 +msgid "To enable the **Google Places API**, you first need to create a project. To do so, click :guilabel:`Select a project` in the top left corner, :guilabel:`New Project`, and follow the prompts to set up your project." +msgstr "" + +#: ../../content/applications/websites/website/configuration/address_autocomplete.rst:34 +msgid "**Enable the Google Places API:**" +msgstr "" + +#: ../../content/applications/websites/website/configuration/address_autocomplete.rst:36 +msgid "Go to the :guilabel:`Enabled APIs & Services` and click :guilabel:`+ ENABLE APIS AND SERVICES.` Search for :guilabel:`\"Places API\"` and select it. Click on the :guilabel:`\"Enable\"` button." +msgstr "" + +#: ../../content/applications/websites/website/configuration/address_autocomplete.rst:39 +msgid "Google's pricing depends on the number of requests and their complexity." +msgstr "" + +#: ../../content/applications/websites/website/configuration/address_autocomplete.rst:42 +msgid "Step 2: Create API Credentials" +msgstr "" + +#: ../../content/applications/websites/website/configuration/address_autocomplete.rst:44 +msgid "Go to `APIs & Services --> Credentials `_." +msgstr "" + +#: ../../content/applications/websites/website/configuration/address_autocomplete.rst:46 +msgid "**Create credentials:**" +msgstr "" + +#: ../../content/applications/websites/website/configuration/address_autocomplete.rst:48 +msgid "To create your credentials, go to :guilabel:`Credentials`, click :guilabel:`Create Credentials`, and select :guilabel:`API key`." +msgstr "" + +#: ../../content/applications/websites/website/configuration/address_autocomplete.rst:50 +msgid "Restrict the API Key (Optional)" +msgstr "" + +#: ../../content/applications/websites/website/configuration/address_autocomplete.rst:52 +msgid "For security purposes, you can restrict the usage of your API key. You can go to the :guilabel:`API restrictions` section to specify which APIs your key can access. For the Google Places API, you can restrict it to only allow requests from specific websites or apps." +msgstr "" + +#: ../../content/applications/websites/website/configuration/address_autocomplete.rst:57 +msgid "Save Your API Key: Copy your API key and securely store it." +msgstr "" + +#: ../../content/applications/websites/website/configuration/address_autocomplete.rst:58 +msgid "Do not share it publicly or expose it in client-side code." +msgstr "" + #: ../../content/applications/websites/website/configuration/cookies_bar.rst:3 msgid "Cookies bar" msgstr "" @@ -4122,78 +4410,6 @@ msgstr "" msgid "Other reporting data such as eCommerce dashboard data, online sales analyses and visitors can be grouped by website if necessary. Click :guilabel:`Group by --> Website`." msgstr "" -#: ../../content/applications/websites/website/configuration/on-premise_geo-ip-installation.rst:3 -msgid "Geo IP Installation (On-Premises Database)" -msgstr "" - -#: ../../content/applications/websites/website/configuration/on-premise_geo-ip-installation.rst:6 -msgid "Installation" -msgstr "" - -#: ../../content/applications/websites/website/configuration/on-premise_geo-ip-installation.rst:8 -msgid "Download both the GeoLite2 City and Country `databases `_. You should end up with two files called :file:`GeoLite2-City.mmdb` and :file:`GeoLite2-Country.mmdb`." -msgstr "" - -#: ../../content/applications/websites/website/configuration/on-premise_geo-ip-installation.rst:12 -msgid "Move the files to the folder :file:`/usr/share/GeoIP/`." -msgstr "" - -#: ../../content/applications/websites/website/configuration/on-premise_geo-ip-installation.rst:19 -msgid "Restart the server" -msgstr "" - -#: ../../content/applications/websites/website/configuration/on-premise_geo-ip-installation.rst:22 -msgid "If you don't want to locate the geoip database in :file:`/usr/share/GeoIP/`, use the :option:`--geoip-city-db ` and :option:`--geoip-country-db ` options of the Odoo command line interface. These options take the absolute path to the GeoIP database file and use it as the GeoIP database. For example:" -msgstr "" - -#: ../../content/applications/websites/website/configuration/on-premise_geo-ip-installation.rst:33 -msgid ":doc:`CLI documentation `." -msgstr "" - -#: ../../content/applications/websites/website/configuration/on-premise_geo-ip-installation.rst:36 -msgid "Test GeoIP Geolocation In Odoo Website" -msgstr "" - -#: ../../content/applications/websites/website/configuration/on-premise_geo-ip-installation.rst:38 -msgid "Edit a web page to include some geo-ip information such as the country name of the current request IP address. To do so:" -msgstr "" - -#: ../../content/applications/websites/website/configuration/on-premise_geo-ip-installation.rst:41 -msgid "Go to your website. Open the web page that you want to test ``GeoIP``." -msgstr "" - -#: ../../content/applications/websites/website/configuration/on-premise_geo-ip-installation.rst:42 -msgid "Choose :menuselection:`Customize --> HTML/CSS/JS Editor`." -msgstr "" - -#: ../../content/applications/websites/website/configuration/on-premise_geo-ip-installation.rst:43 -msgid "Add the following piece of XML in the page :" -msgstr "" - -#: ../../content/applications/websites/website/configuration/on-premise_geo-ip-installation.rst:49 -msgid "Save and refresh the page." -msgstr "" - -#: ../../content/applications/websites/website/configuration/on-premise_geo-ip-installation.rst:51 -msgid "Geo-ip is working if you read your country name displayed in bold in the middle of the page." -msgstr "" - -#: ../../content/applications/websites/website/configuration/on-premise_geo-ip-installation.rst:53 -msgid "In case you read \"**geoip failure**\" instead then the geolocalization failed. The common causes are:" -msgstr "" - -#: ../../content/applications/websites/website/configuration/on-premise_geo-ip-installation.rst:55 -msgid "The browsing IP address is the localhost (``127.0.0.1``) or a local area network one. If you don't know, you can access your website using mobile data." -msgstr "" - -#: ../../content/applications/websites/website/configuration/on-premise_geo-ip-installation.rst:57 -msgid "You are using a reverse-proxy (apache, nginx) in front of Odoo but didn't start Odoo with the proxy-mode enabled. See :option:`proxy mode `." -msgstr "" - -#: ../../content/applications/websites/website/configuration/on-premise_geo-ip-installation.rst:59 -msgid "The GeoIP database is corrupt, missing or unaccessible. In such case a warning was logged in the server logs." -msgstr "" - #: ../../content/applications/websites/website/configuration/recaptcha.rst:3 msgid "reCAPTCHA v3 on forms" msgstr ""