diff --git a/locale/sources/administration.pot b/locale/sources/administration.pot index 2a51ba3e2..40ccb406e 100644 --- a/locale/sources/administration.pot +++ b/locale/sources/administration.pot @@ -8,7 +8,7 @@ msgid "" msgstr "" "Project-Id-Version: Odoo 17.0\n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2024-06-24 07:08+0000\n" +"POT-Creation-Date: 2024-07-23 13:30+0000\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME \n" "Language-Team: LANGUAGE \n" @@ -507,7 +507,7 @@ msgstr "" #: ../../content/administration/odoo_online.rst:3 #: ../../content/administration/supported_versions.rst:29 #: ../../content/administration/upgrade.rst:81 -#: ../../content/administration/upgrade.rst:299 +#: ../../content/administration/upgrade.rst:296 msgid "Odoo Online" msgstr "" @@ -723,7 +723,7 @@ msgstr "" #: ../../content/administration/odoo_sh.rst:5 #: ../../content/administration/supported_versions.rst:30 #: ../../content/administration/upgrade.rst:111 -#: ../../content/administration/upgrade.rst:310 +#: ../../content/administration/upgrade.rst:307 msgid "Odoo.sh" msgstr "" @@ -3025,7 +3025,7 @@ msgstr "" #: ../../content/administration/on_premise.rst:5 #: ../../content/administration/upgrade.rst:136 -#: ../../content/administration/upgrade.rst:333 +#: ../../content/administration/upgrade.rst:330 msgid "On-premise" msgstr "" @@ -5467,46 +5467,46 @@ msgid "Upgrading the production database" msgstr "" #: ../../content/administration/upgrade.rst:273 -msgid "Once the :ref:`tests ` are completed and you are confident that the upgraded database can be used as your main database without any issues, it is time to plan the go-live day. It can be planned in coordination with Odoo's upgrade support analysts by `submitting a ticket for an issue related to my future upgrade (I am testing an upgrade) `_." +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." msgstr "" -#: ../../content/administration/upgrade.rst:279 +#: ../../content/administration/upgrade.rst:276 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:282 +#: ../../content/administration/upgrade.rst:279 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:288 +#: ../../content/administration/upgrade.rst:285 msgid "Going into production without first testing may lead to:" msgstr "" -#: ../../content/administration/upgrade.rst:290 +#: ../../content/administration/upgrade.rst:287 msgid "Users failing to adjust to the changes and new features" msgstr "" -#: ../../content/administration/upgrade.rst:291 +#: ../../content/administration/upgrade.rst:288 msgid "Business interruptions (e.g., no longer having the possibility to validate an action)" msgstr "" -#: ../../content/administration/upgrade.rst:292 +#: ../../content/administration/upgrade.rst:289 msgid "Poor customer experience (e.g., an eCommerce website that does not work correctly)" msgstr "" -#: ../../content/administration/upgrade.rst:294 +#: ../../content/administration/upgrade.rst:291 msgid "The process of upgrading a production database is similar to upgrading a test database with a few exceptions." msgstr "" -#: ../../content/administration/upgrade.rst:301 +#: ../../content/administration/upgrade.rst:298 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:306 +#: ../../content/administration/upgrade.rst:303 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:312 +#: ../../content/administration/upgrade.rst:309 msgid "The process is similar to :ref:`obtaining an upgraded test database ` on the :guilabel:`Production` branch." msgstr "" @@ -5514,98 +5514,98 @@ msgstr "" msgid "View from the upgrade tab" msgstr "" -#: ../../content/administration/upgrade.rst:318 +#: ../../content/administration/upgrade.rst:315 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:324 +#: ../../content/administration/upgrade.rst:321 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:328 +#: ../../content/administration/upgrade.rst:325 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:335 +#: ../../content/administration/upgrade.rst:332 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:342 +#: ../../content/administration/upgrade.rst:339 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:349 +#: ../../content/administration/upgrade.rst:346 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:353 +#: ../../content/administration/upgrade.rst:350 msgid "In case of an issue with your production database, you can request the assistance of Odoo by `submitting a ticket for an issue related to my upgrade (production) `_." msgstr "" -#: ../../content/administration/upgrade.rst:360 +#: ../../content/administration/upgrade.rst:357 msgid "Service-level agreement (SLA)" msgstr "" -#: ../../content/administration/upgrade.rst:362 +#: ../../content/administration/upgrade.rst:359 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:365 +#: ../../content/administration/upgrade.rst:362 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:370 +#: ../../content/administration/upgrade.rst:367 msgid "Upgrade services covered by the SLA" msgstr "" -#: ../../content/administration/upgrade.rst:372 +#: ../../content/administration/upgrade.rst:369 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:375 +#: ../../content/administration/upgrade.rst:372 msgid "the upgrade of all **standard applications**;" msgstr "" -#: ../../content/administration/upgrade.rst:376 +#: ../../content/administration/upgrade.rst:373 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:378 +#: ../../content/administration/upgrade.rst:375 msgid "the upgrade of all **developments and customizations covered by a maintenance of customizations subscription**." msgstr "" -#: ../../content/administration/upgrade.rst:381 +#: ../../content/administration/upgrade.rst:378 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:385 +#: ../../content/administration/upgrade.rst:382 msgid "Upgrade services not covered by the SLA" msgstr "" -#: ../../content/administration/upgrade.rst:387 +#: ../../content/administration/upgrade.rst:384 msgid "The following upgrade-related services are **not** included:" msgstr "" -#: ../../content/administration/upgrade.rst:389 +#: ../../content/administration/upgrade.rst:386 msgid "the **cleaning** of pre-existing data and configurations while upgrading;" msgstr "" -#: ../../content/administration/upgrade.rst:390 +#: ../../content/administration/upgrade.rst:387 msgid "the upgrade of **custom modules created in-house or by third parties**, including Odoo partners;" msgstr "" -#: ../../content/administration/upgrade.rst:391 +#: ../../content/administration/upgrade.rst:388 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:394 +#: ../../content/administration/upgrade.rst:391 msgid "**training** on using the upgraded version's features and workflows." msgstr "" -#: ../../content/administration/upgrade.rst:397 +#: ../../content/administration/upgrade.rst:394 msgid ":doc:`Odoo.sh documentation `" msgstr "" -#: ../../content/administration/upgrade.rst:398 +#: ../../content/administration/upgrade.rst:395 msgid ":doc:`Supported Odoo versions `" msgstr "" diff --git a/locale/sources/essentials.pot b/locale/sources/essentials.pot index 751b09c17..90857fb57 100644 --- a/locale/sources/essentials.pot +++ b/locale/sources/essentials.pot @@ -8,7 +8,7 @@ msgid "" msgstr "" "Project-Id-Version: Odoo 17.0\n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2024-06-24 07:08+0000\n" +"POT-Creation-Date: 2024-07-23 13:30+0000\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME \n" "Language-Team: LANGUAGE \n" @@ -467,107 +467,107 @@ msgstr "" msgid ":doc:`../sales/crm/optimize/utilize_activities`" msgstr "" -#: ../../content/applications/essentials/contacts.rst:3 +#: ../../content/applications/essentials/contacts.rst:5 msgid "Contacts" msgstr "" -#: ../../content/applications/essentials/contacts.rst:5 +#: ../../content/applications/essentials/contacts.rst:7 msgid "The *Contacts* application comes installed on all Odoo databases. Contacts are created for customers the company does business with through Odoo. A contact is a repository of vital business information, facilitating communication and business transactions." msgstr "" -#: ../../content/applications/essentials/contacts.rst:10 +#: ../../content/applications/essentials/contacts.rst:12 msgid "Contact form" msgstr "" -#: ../../content/applications/essentials/contacts.rst:12 +#: ../../content/applications/essentials/contacts.rst:14 msgid "To create a new contact, navigate to the :menuselection:`Contacts app`, and click :guilabel:`Create`. A new form appears where various contact information can be added." msgstr "" -#: ../../content/applications/essentials/contacts.rst:16 +#: ../../content/applications/essentials/contacts.rst:18 msgid "Contact type" msgstr "" -#: ../../content/applications/essentials/contacts.rst:18 +#: ../../content/applications/essentials/contacts.rst:20 msgid "Odoo allows for both :guilabel:`Individual` and :guilabel:`Company` contacts. Select either :guilabel:`Individual` or :guilabel:`Company`, depending on the type of contact that is being added." msgstr "" -#: ../../content/applications/essentials/contacts.rst:22 +#: ../../content/applications/essentials/contacts.rst:24 msgid "Name" msgstr "" -#: ../../content/applications/essentials/contacts.rst:24 +#: ../../content/applications/essentials/contacts.rst:26 msgid "First, fill in the name of the :guilabel:`Individual` or :guilabel:`Company`. This is how the name appears throughout the database. This field is **mandatory**." msgstr "" -#: ../../content/applications/essentials/contacts.rst:28 +#: ../../content/applications/essentials/contacts.rst:30 msgid ":guilabel:`Individual` contacts can have a :guilabel:`Company` contact linked to it. After selecting :guilabel:`Individual`, a new :guilabel:`Company Name...` field appears below the first name field." msgstr "" -#: ../../content/applications/essentials/contacts.rst:33 +#: ../../content/applications/essentials/contacts.rst:35 msgid "Address" msgstr "" -#: ../../content/applications/essentials/contacts.rst:35 +#: ../../content/applications/essentials/contacts.rst:37 msgid "Next, enter the :guilabel:`Address` of the :guilabel:`Company` or :guilabel:`Individual`." msgstr "" -#: ../../content/applications/essentials/contacts.rst:38 +#: ../../content/applications/essentials/contacts.rst:40 msgid "If the :guilabel:`Individual` option is chosen, then the *type of address* can be chosen from a drop-down menu. Options for this drop-down menu include: :guilabel:`Contact`, :guilabel:`Invoice Address`, :guilabel:`Delivery Address`, :guilabel:`Other Address`, and :guilabel:`Private Address`." msgstr "" -#: ../../content/applications/essentials/contacts.rst:44 +#: ../../content/applications/essentials/contacts.rst:46 msgid "Additional fields" msgstr "" -#: ../../content/applications/essentials/contacts.rst:46 +#: ../../content/applications/essentials/contacts.rst:48 msgid "Additional details are included on the initial form. The following fields are available:" msgstr "" -#: ../../content/applications/essentials/contacts.rst:48 +#: ../../content/applications/essentials/contacts.rst:50 msgid ":guilabel:`VAT`: Value Added Tax number." msgstr "" -#: ../../content/applications/essentials/contacts.rst:49 +#: ../../content/applications/essentials/contacts.rst:51 msgid ":guilabel:`Citizen Identification`: citizen or government identification number (only available on :guilabel:`Individual`)." msgstr "" -#: ../../content/applications/essentials/contacts.rst:51 +#: ../../content/applications/essentials/contacts.rst:53 msgid ":guilabel:`Job Position`: list the job position of the :guilabel:`Individual` (only available on :guilabel:`Individual`)." msgstr "" -#: ../../content/applications/essentials/contacts.rst:53 +#: ../../content/applications/essentials/contacts.rst:55 msgid ":guilabel:`Phone`: list phone number (with country code). Make a call, send an SMS, or WhatsApp message by hovering over the field on the saved form, and clicking the desired option." msgstr "" -#: ../../content/applications/essentials/contacts.rst:55 +#: ../../content/applications/essentials/contacts.rst:57 msgid ":guilabel:`Mobile`: list mobile phone number (with country code). Make a call, send an SMS, or WhatsApp message by hovering over the field on the saved form, and clicking on the desired option." msgstr "" -#: ../../content/applications/essentials/contacts.rst:57 +#: ../../content/applications/essentials/contacts.rst:59 msgid ":guilabel:`Email`: enter the email address with the domain." msgstr "" -#: ../../content/applications/essentials/contacts.rst:58 +#: ../../content/applications/essentials/contacts.rst:60 msgid ":guilabel:`Website`: enter the full website address, starting with `http` or `https`." msgstr "" -#: ../../content/applications/essentials/contacts.rst:59 +#: ../../content/applications/essentials/contacts.rst:61 msgid ":guilabel:`Title`: select :guilabel:`Doctor`, :guilabel:`Madam`, :guilabel:`Miss`, :guilabel:`Mister`, :guilabel:`Professor`, or create a new one directly from this field." msgstr "" -#: ../../content/applications/essentials/contacts.rst:61 +#: ../../content/applications/essentials/contacts.rst:63 msgid ":guilabel:`Tags`: enter preconfigured tags by typing them in the field, or clicking the drop-down menu, and selecting one. To create a new one, type the new tag in the field, and click :guilabel:`Create` from the resulting drop-down menu." msgstr "" -#: ../../content/applications/essentials/contacts.rst:66 +#: ../../content/applications/essentials/contacts.rst:68 msgid "Contacts & Addresses tab" msgstr "" -#: ../../content/applications/essentials/contacts.rst:68 +#: ../../content/applications/essentials/contacts.rst:70 msgid "At the bottom of the contact form are several tabs. On the :guilabel:`Contacts & Addresses` tab, contacts can be added that are associated with a :guilabel:`Company` and related addresses. For example, a specific contact person for the company can be listed here." msgstr "" -#: ../../content/applications/essentials/contacts.rst:72 +#: ../../content/applications/essentials/contacts.rst:74 msgid "Multiple addresses can be added on both :guilabel:`Individual` and :guilabel:`Company` contacts. To do so, click :guilabel:`Add` in the :guilabel:`Contacts & Addresses` tab. Doing so reveals a :guilabel:`Create Contact` pop-up form, in which additional addresses can be configured." msgstr "" @@ -575,31 +575,31 @@ msgstr "" msgid "Add a contact/address to the contact form." msgstr "" -#: ../../content/applications/essentials/contacts.rst:80 +#: ../../content/applications/essentials/contacts.rst:82 msgid "On the :guilabel:`Create Contact` pop-up form, start by clicking the default :guilabel:`Other Address` field at the top to reveal a drop-down menu of address-related options." msgstr "" -#: ../../content/applications/essentials/contacts.rst:83 +#: ../../content/applications/essentials/contacts.rst:85 msgid "Select any of the following options:" msgstr "" -#: ../../content/applications/essentials/contacts.rst:85 +#: ../../content/applications/essentials/contacts.rst:87 msgid ":guilabel:`Contact`: adds another contact to the existing contact form." msgstr "" -#: ../../content/applications/essentials/contacts.rst:86 +#: ../../content/applications/essentials/contacts.rst:88 msgid ":guilabel:`Invoice Address`: adds a specific invoice address to the existing contact form." msgstr "" -#: ../../content/applications/essentials/contacts.rst:87 +#: ../../content/applications/essentials/contacts.rst:89 msgid ":guilabel:`Delivery Address`: adds a specific delivery address to the existing contact form." msgstr "" -#: ../../content/applications/essentials/contacts.rst:88 +#: ../../content/applications/essentials/contacts.rst:90 msgid ":guilabel:`Other Address`: adds an alternate address to the existing contact form." msgstr "" -#: ../../content/applications/essentials/contacts.rst:89 +#: ../../content/applications/essentials/contacts.rst:91 msgid ":guilabel:`Private Address`: adds a private address to the existing contact form." msgstr "" @@ -607,214 +607,298 @@ msgstr "" msgid "Create a new contact/address on a contact form." msgstr "" -#: ../../content/applications/essentials/contacts.rst:95 +#: ../../content/applications/essentials/contacts.rst:97 msgid "Once an option is selected, enter the corresponding contact information that should be used for the specified address type." msgstr "" -#: ../../content/applications/essentials/contacts.rst:98 +#: ../../content/applications/essentials/contacts.rst:100 msgid "Add the :guilabel:`Contact Name`, :guilabel:`Address`, :guilabel:`Email`, along with the :guilabel:`Phone` and/or :guilabel:`Mobile` numbers below." msgstr "" -#: ../../content/applications/essentials/contacts.rst:101 +#: ../../content/applications/essentials/contacts.rst:103 msgid "Set the :guilabel:`Job Position`, which appears if the :guilabel:`Contact` address type has been selected. This is similar to the :guilabel:`Individual` contact." msgstr "" -#: ../../content/applications/essentials/contacts.rst:104 +#: ../../content/applications/essentials/contacts.rst:106 msgid "To add a note, click on the text field next to :guilabel:`Notes`, and write anything that is applicable to the customer or contact." msgstr "" -#: ../../content/applications/essentials/contacts.rst:107 +#: ../../content/applications/essentials/contacts.rst:109 msgid "Then, click :guilabel:`Save & Close` to save the address, and close the :guilabel:`Create Contact` window. Or, click :guilabel:`Save & New` to save the address, and immediately input another one." msgstr "" -#: ../../content/applications/essentials/contacts.rst:111 +#: ../../content/applications/essentials/contacts.rst:113 msgid "Sales & Purchase tab" msgstr "" -#: ../../content/applications/essentials/contacts.rst:113 +#: ../../content/applications/essentials/contacts.rst:115 msgid "Next, is the :guilabel:`Sales & Purchases` tab, which only appears when the *Sales*, *Purchase*, **or** *Point of Sale* applications are installed." msgstr "" -#: ../../content/applications/essentials/contacts.rst:116 +#: ../../content/applications/essentials/contacts.rst:118 msgid "The :guilabel:`Fiscal Position` can be set on the :guilabel:`Sales & Purchases` tab. Select a :guilabel:`Fiscal Position` from the drop-down menu." msgstr "" -#: ../../content/applications/essentials/contacts.rst:120 +#: ../../content/applications/essentials/contacts.rst:122 msgid "Sales section" msgstr "" -#: ../../content/applications/essentials/contacts.rst:122 +#: ../../content/applications/essentials/contacts.rst:124 msgid "Under the :guilabel:`Sales` heading, a specific :guilabel:`Salesperson` can be assigned to a contact. To do that, click the :guilabel:`Salesperson` drop-down field, and select one. Create a new :guilabel:`Salesperson` by typing the user's name, and making the appropriate selection." msgstr "" -#: ../../content/applications/essentials/contacts.rst:126 +#: ../../content/applications/essentials/contacts.rst:128 msgid "Certain :guilabel:`Payment Terms`, or a certain :guilabel:`Pricelist`, can also be set, if needed. Click the drop-down menu next to :guilabel:`Payment Terms`, and change it to one of the preselected :guilabel:`Payment Terms`, or :guilabel:`Create` a new one. Select the :guilabel:`Pricelist` drop-down menu to choose the appropriate :guilabel:`Pricelist`." msgstr "" -#: ../../content/applications/essentials/contacts.rst:131 +#: ../../content/applications/essentials/contacts.rst:133 msgid "Click into the :guilabel:`Delivery Method` field to select an option from the drop-down menu." msgstr "" -#: ../../content/applications/essentials/contacts.rst:134 +#: ../../content/applications/essentials/contacts.rst:136 msgid "Point Of Sale section" msgstr "" -#: ../../content/applications/essentials/contacts.rst:136 +#: ../../content/applications/essentials/contacts.rst:138 msgid "Under the :guilabel:`Point Of Sale` heading, enter a :guilabel:`Barcode` that can be used to identify the contact. Use the :guilabel:`Loyalty Points` field to track points the user won as part of a *Loyalty Program*." msgstr "" -#: ../../content/applications/essentials/contacts.rst:141 +#: ../../content/applications/essentials/contacts.rst:143 msgid "Purchase section" msgstr "" -#: ../../content/applications/essentials/contacts.rst:143 +#: ../../content/applications/essentials/contacts.rst:145 msgid "Specify :guilabel:`Payment Terms`, :guilabel:`1099 Box` information, and a preferred :guilabel:`Payment Method` here. A :guilabel:`Receipt Reminder` can be set here, as well." msgstr "" -#: ../../content/applications/essentials/contacts.rst:147 +#: ../../content/applications/essentials/contacts.rst:149 msgid "Misc section" msgstr "" -#: ../../content/applications/essentials/contacts.rst:149 +#: ../../content/applications/essentials/contacts.rst:151 msgid "Under the :guilabel:`Misc.` heading, use :guilabel:`Reference` field to add any additional information for this contact. If this contact should only be accessible for one company in a multi-company database, select it from the :guilabel:`Company` field drop-down list. Use the :guilabel:`Website` drop-down menu to restrict the publishing of this contact to one website (if working on a database with multiple websites). Select one or more :guilabel:`Website Tags` to assist in filtering published customers on the `/customers` website page. Select an :guilabel:`Industry` for this contact from the drop-down menu. Use the :guilabel:`SLA Policies` field to assign a *Helpdesk* SLA policy to this contact." msgstr "" -#: ../../content/applications/essentials/contacts.rst:159 +#: ../../content/applications/essentials/contacts.rst:161 msgid "Accounting tab" msgstr "" -#: ../../content/applications/essentials/contacts.rst:161 +#: ../../content/applications/essentials/contacts.rst:163 msgid "The :guilabel:`Accounting` tab appears when the *Accounting* application is installed. Here, a user can add any related :guilabel:`Bank Accounts`, or set default :guilabel:`Accounting entries`." msgstr "" -#: ../../content/applications/essentials/contacts.rst:164 +#: ../../content/applications/essentials/contacts.rst:166 msgid "Under the :guilabel:`Miscellaneous` heading, use the :guilabel:`LEI` field to enter a Legal Entity Identifier, if necessary." msgstr "" -#: ../../content/applications/essentials/contacts.rst:168 +#: ../../content/applications/essentials/contacts.rst:170 msgid "Internal Notes tab" msgstr "" -#: ../../content/applications/essentials/contacts.rst:170 +#: ../../content/applications/essentials/contacts.rst:172 msgid "Following the :guilabel:`Accounting` tab is the :guilabel:`Internal Notes` tab, where notes can be left on this contact form, just like on the contact form noted above." msgstr "" -#: ../../content/applications/essentials/contacts.rst:174 +#: ../../content/applications/essentials/contacts.rst:176 msgid "Partner Assignment tab" msgstr "" -#: ../../content/applications/essentials/contacts.rst:176 +#: ../../content/applications/essentials/contacts.rst:178 msgid "Next is the :guilabel:`Partner Assignment` tab, which by default, includes a :guilabel:`Geolocation` section, and other partner options, including :guilabel:`Partner Activation` and :guilabel:`Partner Review` configurations. These are **only** present when the *Resellers* module is installed." msgstr "" -#: ../../content/applications/essentials/contacts.rst:181 +#: ../../content/applications/essentials/contacts.rst:183 msgid "Follow the :doc:`Resellers documentation <../sales/crm/track_leads/resellers>` for more information on publishing partners on the website." msgstr "" -#: ../../content/applications/essentials/contacts.rst:185 +#: ../../content/applications/essentials/contacts.rst:187 msgid "Membership tab" msgstr "" -#: ../../content/applications/essentials/contacts.rst:187 +#: ../../content/applications/essentials/contacts.rst:189 msgid "Finally, there is the :guilabel:`Membership` tab on contact forms, which can help users manage any memberships that are being offered to this specific contact. It should be noted that this tab **only** appears when the *Members* application is installed." msgstr "" -#: ../../content/applications/essentials/contacts.rst:192 +#: ../../content/applications/essentials/contacts.rst:194 msgid "Activate membership" msgstr "" -#: ../../content/applications/essentials/contacts.rst:194 +#: ../../content/applications/essentials/contacts.rst:196 msgid "To activate a contact's membership, click :guilabel:`Buy Membership` in the :guilabel:`Membership` tab of a contact form. On the pop-up window that appears, select a :guilabel:`Membership` from the drop-down menu. Then, configure a :guilabel:`Member Price`. Click :guilabel:`Invoice Membership` when both fields are filled in." msgstr "" -#: ../../content/applications/essentials/contacts.rst:199 +#: ../../content/applications/essentials/contacts.rst:201 msgid "Alternatively, to offer a free membership, tick the :guilabel:`Free Member` checkbox, in the :guilabel:`Membership` tab of a contact form." msgstr "" -#: ../../content/applications/essentials/contacts.rst:203 -msgid "Publish members directory" -msgstr "" - #: ../../content/applications/essentials/contacts.rst:205 -msgid "To publish a list of active members on the website, the *Online Members Directory* application must first be :ref:`installed `. After installing the module, add the `/members` page to the website's menu by :doc:`editing the website menu <../websites/website/pages/menus>`." +msgid "Follow the :doc:`Members documentation <../sales/members>` for more information on publishing members on the website." msgstr "" -#: ../../content/applications/essentials/contacts.rst:210 -msgid "Publish individual members" -msgstr "" - -#: ../../content/applications/essentials/contacts.rst:212 -msgid "Return to :menuselection:`CRM app --> Sales --> Customers`, and click the Kanban card for a member. Click the :guilabel:`Go to Website` smart button at the top of the page to open the member's webpage." -msgstr "" - -#: ../../content/applications/essentials/contacts.rst:216 -msgid "After making any necessary changes to the page, click :guilabel:`Save`. At the top of the page, slide the :guilabel:`Unpublished` toggle to the active, :guilabel:`Published` position." -msgstr "" - -#: ../../content/applications/essentials/contacts.rst:219 -msgid "Repeat these steps for all members." -msgstr "" - -#: ../../content/applications/essentials/contacts.rst:222 +#: ../../content/applications/essentials/contacts.rst:209 msgid "Smart buttons" msgstr "" -#: ../../content/applications/essentials/contacts.rst:224 +#: ../../content/applications/essentials/contacts.rst:211 msgid "At the top of the contact form, there are some additional options available, known as *smart buttons*." msgstr "" -#: ../../content/applications/essentials/contacts.rst:227 +#: ../../content/applications/essentials/contacts.rst:214 msgid "Here, Odoo displays a variety of records, related to this contact, that were created on other apps. Odoo integrates information from every single app, so there are many smart buttons." msgstr "" -#: ../../content/applications/essentials/contacts.rst:231 +#: ../../content/applications/essentials/contacts.rst:218 msgid "For example, there is an :guilabel:`Opportunities` smart button, where all the opportunities related to this customer from the *CRM* app are accessible." msgstr "" -#: ../../content/applications/essentials/contacts.rst:235 +#: ../../content/applications/essentials/contacts.rst:222 msgid "If the corresponding applications are installed, their related smart buttons appear automatically on a contact form." msgstr "" -#: ../../content/applications/essentials/contacts.rst:238 +#: ../../content/applications/essentials/contacts.rst:225 msgid "A user can see any :guilabel:`Meetings`, :guilabel:`Sales`, :guilabel:`POS Orders`, :guilabel:`Subscriptions`, project :guilabel:`Tasks`, and the :guilabel:`More` smart button reveals additional options, via a drop-down menu. A user can even quickly access :guilabel:`Purchases`, :guilabel:`Helpdesk` tasks, :guilabel:`On-time Rate` for deliveries, :guilabel:`Invoiced` information, :guilabel:`Vendor Bills`, and the :guilabel:`Partner Ledger` connected to this contact." msgstr "" -#: ../../content/applications/essentials/contacts.rst:244 +#: ../../content/applications/essentials/contacts.rst:231 msgid "Deliveries, documents, loyalty cards, and direct debits are *also* linked to smart buttons, like this, should there be any outstanding/on-file for this contact." msgstr "" -#: ../../content/applications/essentials/contacts.rst:247 +#: ../../content/applications/essentials/contacts.rst:234 msgid "If the contact is a partner, the user can visit their partner page on the Odoo-built website by clicking the :guilabel:`Go to Website` smart button." msgstr "" -#: ../../content/applications/essentials/contacts.rst:251 +#: ../../content/applications/essentials/contacts.rst:238 msgid "Archive contacts" msgstr "" -#: ../../content/applications/essentials/contacts.rst:253 +#: ../../content/applications/essentials/contacts.rst:240 msgid "If a user decides they no longer want to have this contact active, the record can be archived. To do that, go to the :icon:`fa-cog` :guilabel:`Action` menu at the top of the contact form, and click :guilabel:`Archive`." msgstr "" -#: ../../content/applications/essentials/contacts.rst:257 +#: ../../content/applications/essentials/contacts.rst:244 msgid "Then, click :guilabel:`OK` from the resulting :guilabel:`Confirmation` pop-up window." msgstr "" -#: ../../content/applications/essentials/contacts.rst:259 +#: ../../content/applications/essentials/contacts.rst:246 msgid "With this contact successfully archived, as indicated by a banner at the top, they do not show up in the main contacts page, but they can still be searched for with the :guilabel:`Archived` filter." msgstr "" -#: ../../content/applications/essentials/contacts.rst:263 +#: ../../content/applications/essentials/contacts.rst:250 msgid "A contact can be *unarchived*, if the user decides to work with them again. To do that, just click the :icon:`fa-cog` :guilabel:`Action` menu again at the top of the archived contact form, and click :guilabel:`Unarchive`. Upon doing so, the :guilabel:`Archived` banner is removed, and the contact is restored." msgstr "" -#: ../../content/applications/essentials/contacts.rst:269 +#: ../../content/applications/essentials/contacts.rst:256 msgid ":doc:`Add different addresses in CRM <../sales/sales/send_quotations/different_addresses>`" msgstr "" -#: ../../content/applications/essentials/contacts.rst:270 +#: ../../content/applications/essentials/contacts.rst:257 msgid "`Odoo's eLearning Contacts tutorial `_" msgstr "" +#: ../../content/applications/essentials/contacts/merge.rst:3 +msgid "Merge contacts" +msgstr "" + +#: ../../content/applications/essentials/contacts/merge.rst:5 +msgid "Odoo's *Contacts* application allows user's to merge duplicate contacts, without losing any information in the process. This keeps the database organized, and prevents contacts from being contacted by more than one salesperson." +msgstr "" + +#: ../../content/applications/essentials/contacts/merge.rst:12 +msgid "Merge duplicate contacts" +msgstr "" + +#: ../../content/applications/essentials/contacts/merge.rst:15 +msgid "Merging is an irreversible action. Do **not** merge contacts unless absolutely certain they should be combined." +msgstr "" + +#: ../../content/applications/essentials/contacts/merge.rst:18 +msgid "Navigate to the :menuselection:`Contacts app`, and select the :icon:`oi-view-list` :guilabel:`(list)` icon. Select two or more duplicate contacts from the list, and tick the checkbox (on the far-left) for the contacts that should be merged. Then, click the :icon:`fa-cog` :guilabel:`Actions` icon, and select :guilabel:`Merge` from the resulting drop-down menu." +msgstr "" + +#: ../../content/applications/essentials/contacts/merge.rst:-1 +msgid "The merge contacts option in the Contacts application." +msgstr "" + +#: ../../content/applications/essentials/contacts/merge.rst:27 +msgid "This opens the :guilabel:`Merge` pop-up window. From here, review the details of the contacts before confirming they should be merged. If any contacts in the list should **not** be merged, click the :icon:`fa-times` :guilabel:`(delete)` icon at the far right of the contact." +msgstr "" + +#: ../../content/applications/essentials/contacts/merge.rst:32 +msgid "Click the individual contact to open the record for that contact, and view additional information." +msgstr "" + +#: ../../content/applications/essentials/contacts/merge.rst:-1 +msgid "The merge pop-up window in the Contacts application." +msgstr "" + +#: ../../content/applications/essentials/contacts/merge.rst:39 +msgid "Click the :guilabel:`Destination Contact` field, and select an option from the drop-down list. This field defaults to the contact record that was created first in the system." +msgstr "" + +#: ../../content/applications/essentials/contacts/merge.rst:42 +msgid "After confirming the information on the pop-up window, click :guilabel:`Merge Contacts`." +msgstr "" + +#: ../../content/applications/essentials/contacts/merge.rst:45 +msgid "Deduplicate contacts" +msgstr "" + +#: ../../content/applications/essentials/contacts/merge.rst:47 +msgid "After the merge is finished, a pop-up window appears confirming it is complete. This pop-up window also contains a :guilabel:`Deduplicate the other Contacts` button. This feature searches for duplicated records, based on selected criteria, and merges them automatically, or after manual approval." +msgstr "" + +#: ../../content/applications/essentials/contacts/merge.rst:52 +msgid "Click the :guilabel:`Deduplicate the other Contacts` button to open the :guilabel:`Deduplicate Contacts` pop-up window." +msgstr "" + +#: ../../content/applications/essentials/contacts/merge.rst:55 +msgid "Select one or more fields to be used in the search for duplicated records. Duplicated contacts can be searched, based on the following criteria:" +msgstr "" + +#: ../../content/applications/essentials/contacts/merge.rst:58 +msgid ":guilabel:`Email`" +msgstr "" + +#: ../../content/applications/essentials/contacts/merge.rst:59 +msgid ":guilabel:`Name`" +msgstr "" + +#: ../../content/applications/essentials/contacts/merge.rst:60 +msgid ":guilabel:`Is Company`" +msgstr "" + +#: ../../content/applications/essentials/contacts/merge.rst:61 +msgid ":guilabel:`VAT`" +msgstr "" + +#: ../../content/applications/essentials/contacts/merge.rst:62 +msgid ":guilabel:`Parent Company`" +msgstr "" + +#: ../../content/applications/essentials/contacts/merge.rst:65 +msgid "If more than one field is selected, only records that have **all** fields in common are suggested as duplicates." +msgstr "" + +#: ../../content/applications/essentials/contacts/merge.rst:68 +msgid "If necessary, select criteria to be used to exclude potential duplicates from the search. Potential duplicates can be excluded from the search, based on the following criteria:" +msgstr "" + +#: ../../content/applications/essentials/contacts/merge.rst:71 +msgid ":guilabel:`A user associated to the contact`" +msgstr "" + +#: ../../content/applications/essentials/contacts/merge.rst:72 +msgid ":guilabel:`Journal Items associated to the contact`" +msgstr "" + +#: ../../content/applications/essentials/contacts/merge.rst:74 +msgid "After confirming the search criteria, click either :guilabel:`Merge with Manual Check`, :guilabel:`Merge Automatically`, or :guilabel:`Merge Automatically all process`." +msgstr "" + +#: ../../content/applications/essentials/contacts/merge.rst:77 +msgid "If :guilabel:`Merge with Manual Check` is selected, complete the merge by following the :ref:`steps above `." +msgstr "" + #: ../../content/applications/essentials/export_import_data.rst:3 msgid "Export and import data" msgstr "" diff --git a/locale/sources/finance.pot b/locale/sources/finance.pot index 898c02550..c63c0ee21 100644 --- a/locale/sources/finance.pot +++ b/locale/sources/finance.pot @@ -8,7 +8,7 @@ msgid "" msgstr "" "Project-Id-Version: Odoo 17.0\n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2024-06-24 07:08+0000\n" +"POT-Creation-Date: 2024-07-23 13:30+0000\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME \n" "Language-Team: LANGUAGE \n" @@ -66,7 +66,7 @@ msgid ":doc:`Cash basis `" msgstr "" #: ../../content/applications/finance/accounting.rst:82 -#: ../../content/applications/finance/fiscal_localizations/kenya.rst:107 +#: ../../content/applications/finance/fiscal_localizations/kenya.rst:143 msgid "Multi-company" msgstr "" @@ -1968,7 +1968,7 @@ msgid "Taxes" msgstr "" #: ../../content/applications/finance/accounting/customer_invoices.rst:109 -#: ../../content/applications/finance/fiscal_localizations/france.rst:96 +#: ../../content/applications/finance/fiscal_localizations/france.rst:101 msgid "15" msgstr "" @@ -3878,7 +3878,7 @@ msgstr "" #: ../../content/applications/finance/accounting/payments/checks.rst:93 #: ../../content/applications/finance/accounting/payments/checks.rst:104 #: ../../content/applications/finance/accounting/payments/checks.rst:123 -#: ../../content/applications/finance/fiscal_localizations/france.rst:88 +#: ../../content/applications/finance/fiscal_localizations/france.rst:93 msgid "Debit" msgstr "" @@ -3890,7 +3890,7 @@ msgstr "" #: ../../content/applications/finance/accounting/payments/checks.rst:93 #: ../../content/applications/finance/accounting/payments/checks.rst:104 #: ../../content/applications/finance/accounting/payments/checks.rst:123 -#: ../../content/applications/finance/fiscal_localizations/france.rst:90 +#: ../../content/applications/finance/fiscal_localizations/france.rst:95 msgid "Credit" msgstr "" @@ -4433,8 +4433,8 @@ msgstr "" #: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:94 #: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:278 -#: ../../content/applications/finance/fiscal_localizations/france.rst:240 -#: ../../content/applications/finance/fiscal_localizations/france.rst:240 +#: ../../content/applications/finance/fiscal_localizations/france.rst:245 +#: ../../content/applications/finance/fiscal_localizations/france.rst:245 msgid "0" msgstr "" @@ -4481,8 +4481,8 @@ msgstr "" #: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:98 #: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:284 #: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:286 -#: ../../content/applications/finance/fiscal_localizations/france.rst:88 -#: ../../content/applications/finance/fiscal_localizations/france.rst:111 +#: ../../content/applications/finance/fiscal_localizations/france.rst:93 +#: ../../content/applications/finance/fiscal_localizations/france.rst:116 msgid "12" msgstr "" @@ -4670,7 +4670,7 @@ msgstr "" #: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:243 #: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:290 #: ../../content/applications/finance/accounting/get_started/avg_price_valuation.rst:292 -#: ../../content/applications/finance/fiscal_localizations/france.rst:242 +#: ../../content/applications/finance/fiscal_localizations/france.rst:247 msgid "1" msgstr "" @@ -5717,7 +5717,7 @@ msgstr "" #: ../../content/applications/finance/fiscal_localizations/argentina.rst:254 #: ../../content/applications/finance/fiscal_localizations/brazil.rst:221 #: ../../content/applications/finance/fiscal_localizations/chile.rst:278 -#: ../../content/applications/finance/fiscal_localizations/france.rst:194 +#: ../../content/applications/finance/fiscal_localizations/france.rst:199 #: ../../content/applications/finance/fiscal_localizations/india.rst:101 #: ../../content/applications/finance/fiscal_localizations/peru.rst:308 msgid "Journals" @@ -8829,7 +8829,7 @@ msgid "1,000" msgstr "" #: ../../content/applications/finance/accounting/taxes.rst:97 -#: ../../content/applications/finance/fiscal_localizations/france.rst:84 +#: ../../content/applications/finance/fiscal_localizations/france.rst:89 msgid "10" msgstr "" @@ -9516,7 +9516,7 @@ msgstr "" #: ../../content/applications/finance/fiscal_localizations/colombia.rst:33 #: ../../content/applications/finance/fiscal_localizations/ecuador.rst:46 #: ../../content/applications/finance/fiscal_localizations/egypt.rst:16 -#: ../../content/applications/finance/fiscal_localizations/france.rst:182 +#: ../../content/applications/finance/fiscal_localizations/france.rst:187 #: ../../content/applications/finance/fiscal_localizations/hong_kong.rst:14 #: ../../content/applications/finance/fiscal_localizations/india.rst:16 #: ../../content/applications/finance/fiscal_localizations/italy.rst:17 @@ -9565,7 +9565,7 @@ msgstr "" #: ../../content/applications/finance/fiscal_localizations/colombia.rst:35 #: ../../content/applications/finance/fiscal_localizations/ecuador.rst:48 #: ../../content/applications/finance/fiscal_localizations/egypt.rst:18 -#: ../../content/applications/finance/fiscal_localizations/france.rst:59 +#: ../../content/applications/finance/fiscal_localizations/france.rst:64 #: ../../content/applications/finance/fiscal_localizations/hong_kong.rst:16 #: ../../content/applications/finance/fiscal_localizations/india.rst:18 #: ../../content/applications/finance/fiscal_localizations/italy.rst:19 @@ -12262,7 +12262,7 @@ msgid "Select your country's fiscal localization package in Odoo Accounting." msgstr "" #: ../../content/applications/finance/fiscal_localizations.rst:37 -#: ../../content/applications/finance/fiscal_localizations/france.rst:59 +#: ../../content/applications/finance/fiscal_localizations/france.rst:64 msgid "Use" msgstr "" @@ -14211,7 +14211,7 @@ msgstr "" #: ../../content/applications/finance/fiscal_localizations/australia.rst:230 #: ../../content/applications/finance/fiscal_localizations/australia.rst:234 #: ../../content/applications/finance/fiscal_localizations/australia.rst:238 -#: ../../content/applications/finance/fiscal_localizations/kenya.rst:229 +#: ../../content/applications/finance/fiscal_localizations/kenya.rst:262 #: ../../content/applications/finance/fiscal_localizations/switzerland.rst:114 #: ../../content/applications/finance/fiscal_localizations/switzerland.rst:116 #: ../../content/applications/finance/fiscal_localizations/switzerland.rst:118 @@ -16866,7 +16866,7 @@ msgstr "" #: ../../content/applications/finance/fiscal_localizations/brazil.rst:470 #: ../../content/applications/finance/fiscal_localizations/chile.rst:595 #: ../../content/applications/finance/fiscal_localizations/colombia.rst:344 -#: ../../content/applications/finance/fiscal_localizations/kenya.rst:337 +#: ../../content/applications/finance/fiscal_localizations/kenya.rst:370 #: ../../content/applications/finance/fiscal_localizations/mexico.rst:348 msgid "Credit notes" msgstr "" @@ -17361,7 +17361,7 @@ msgid "The official currency rate is provided by `Chilean mindicador.cl ` the **France - Adding Mandatory Invoice Mentions (Decree no. 2022-1299)** (`l10n_fr_invoice_addr`) module to comply with the `local legislation `_." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/france.rst:13 msgid "FEC - Fichier des Écritures Comptables" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/france.rst:10 +#: ../../content/applications/finance/fiscal_localizations/france.rst:15 msgid "An FEC :dfn:`Fichier des Écritures Comptables` audit file contains all the accounting data and entries recorded in all the accounting journals for a financial year. The entries in the file must be arranged in chronological order." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/france.rst:14 +#: ../../content/applications/finance/fiscal_localizations/france.rst:19 msgid "Since January 1st, 2014, every French company is required to produce and transmit this file upon request by the tax authorities for audit purposes." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/france.rst:18 +#: ../../content/applications/finance/fiscal_localizations/france.rst:23 msgid "FEC Import" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/france.rst:20 +#: ../../content/applications/finance/fiscal_localizations/france.rst:25 msgid "To make the onboarding of new users easier, Odoo Enterprise's French :ref:`fiscal localization package ` includes the **FEC Import** feature (module name: ``l10n_fr_fec_import``), which enables the import of existing FEC files from older software." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/france.rst:24 +#: ../../content/applications/finance/fiscal_localizations/france.rst:29 msgid "To enable this feature, go to :menuselection:`Accounting --> Configuration --> Settings --> Accounting Import`, enable **FEC Import**, and *Save*." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/france.rst:27 +#: ../../content/applications/finance/fiscal_localizations/france.rst:32 msgid "Next, go to :menuselection:`Accounting --> Configuration --> FEC Import`, upload your FEC file, and click on *Import*." msgstr "" @@ -20568,536 +20572,536 @@ msgstr "" msgid "Should multiple files contain any \"Reports à Nouveaux\" (RAN) with the starting balance of the year, you might need to cancel those entries in the User Interface. Odoo makes those entries (RAN) useless." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/france.rst:38 +#: ../../content/applications/finance/fiscal_localizations/france.rst:43 msgid "File formats" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/france.rst:40 +#: ../../content/applications/finance/fiscal_localizations/france.rst:45 msgid "FEC files can only be in CSV format, as the XML format is not supported." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/france.rst:44 +#: ../../content/applications/finance/fiscal_localizations/france.rst:49 msgid "The FEC CSV file has a plain text format representing a data table, with the first line being a header and defining the list of fields for each entry, and each following line representing one accounting entry, in no predetermined order." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/france.rst:48 +#: ../../content/applications/finance/fiscal_localizations/france.rst:53 msgid "Our module expects the files to meet the following technical specifications:" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/france.rst:50 +#: ../../content/applications/finance/fiscal_localizations/france.rst:55 msgid "**Encoding**: UTF-8, UTF-8-SIG and iso8859_15." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/france.rst:51 +#: ../../content/applications/finance/fiscal_localizations/france.rst:56 msgid "**Separator**: any of these: `;` or `|` or `,` or `TAB`." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/france.rst:52 +#: ../../content/applications/finance/fiscal_localizations/france.rst:57 msgid "**Line terminators**: both CR+LF (`\\\\r\\\\n`) and LF (`\\\\n`) character groups are supported." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/france.rst:53 +#: ../../content/applications/finance/fiscal_localizations/france.rst:58 msgid "**Date format**: `%Y%m%d`" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/france.rst:56 +#: ../../content/applications/finance/fiscal_localizations/france.rst:61 msgid "Fields description and use" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/france.rst:59 +#: ../../content/applications/finance/fiscal_localizations/france.rst:64 msgid "#" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/france.rst:59 +#: ../../content/applications/finance/fiscal_localizations/france.rst:64 msgid "Field name" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/france.rst:59 +#: ../../content/applications/finance/fiscal_localizations/france.rst:64 msgid "Format" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/france.rst:61 +#: ../../content/applications/finance/fiscal_localizations/france.rst:66 msgid "01" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/france.rst:61 +#: ../../content/applications/finance/fiscal_localizations/france.rst:66 msgid "JournalCode" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/france.rst:61 +#: ../../content/applications/finance/fiscal_localizations/france.rst:66 msgid "Journal Code" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/france.rst:61 +#: ../../content/applications/finance/fiscal_localizations/france.rst:66 msgid "`journal.code` and `journal.name` if `JournalLib` is not provided" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/france.rst:61 -#: ../../content/applications/finance/fiscal_localizations/france.rst:64 #: ../../content/applications/finance/fiscal_localizations/france.rst:66 +#: ../../content/applications/finance/fiscal_localizations/france.rst:69 #: ../../content/applications/finance/fiscal_localizations/france.rst:71 -#: ../../content/applications/finance/fiscal_localizations/france.rst:73 -#: ../../content/applications/finance/fiscal_localizations/france.rst:75 +#: ../../content/applications/finance/fiscal_localizations/france.rst:76 #: ../../content/applications/finance/fiscal_localizations/france.rst:78 -#: ../../content/applications/finance/fiscal_localizations/france.rst:81 +#: ../../content/applications/finance/fiscal_localizations/france.rst:80 +#: ../../content/applications/finance/fiscal_localizations/france.rst:83 #: ../../content/applications/finance/fiscal_localizations/france.rst:86 -#: ../../content/applications/finance/fiscal_localizations/france.rst:93 -#: ../../content/applications/finance/fiscal_localizations/france.rst:104 +#: ../../content/applications/finance/fiscal_localizations/france.rst:91 +#: ../../content/applications/finance/fiscal_localizations/france.rst:98 +#: ../../content/applications/finance/fiscal_localizations/france.rst:109 msgid "Alphanumeric" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/france.rst:64 +#: ../../content/applications/finance/fiscal_localizations/france.rst:69 msgid "02" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/france.rst:64 +#: ../../content/applications/finance/fiscal_localizations/france.rst:69 msgid "JournalLib" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/france.rst:64 +#: ../../content/applications/finance/fiscal_localizations/france.rst:69 msgid "Journal Label" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/france.rst:64 +#: ../../content/applications/finance/fiscal_localizations/france.rst:69 msgid "`journal.name`" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/france.rst:66 +#: ../../content/applications/finance/fiscal_localizations/france.rst:71 msgid "03" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/france.rst:66 +#: ../../content/applications/finance/fiscal_localizations/france.rst:71 msgid "EcritureNum" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/france.rst:66 +#: ../../content/applications/finance/fiscal_localizations/france.rst:71 msgid "Numbering specific to each journal sequence number of the entry" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/france.rst:66 +#: ../../content/applications/finance/fiscal_localizations/france.rst:71 msgid "`move.name`" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/france.rst:69 +#: ../../content/applications/finance/fiscal_localizations/france.rst:74 msgid "04" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/france.rst:69 +#: ../../content/applications/finance/fiscal_localizations/france.rst:74 msgid "EcritureDate" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/france.rst:69 +#: ../../content/applications/finance/fiscal_localizations/france.rst:74 msgid "Accounting entry Date" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/france.rst:69 -#: ../../content/applications/finance/fiscal_localizations/france.rst:84 +#: ../../content/applications/finance/fiscal_localizations/france.rst:74 +#: ../../content/applications/finance/fiscal_localizations/france.rst:89 msgid "`move.date`" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/france.rst:69 -#: ../../content/applications/finance/fiscal_localizations/france.rst:84 -#: ../../content/applications/finance/fiscal_localizations/france.rst:96 -#: ../../content/applications/finance/fiscal_localizations/france.rst:99 +#: ../../content/applications/finance/fiscal_localizations/france.rst:74 +#: ../../content/applications/finance/fiscal_localizations/france.rst:89 +#: ../../content/applications/finance/fiscal_localizations/france.rst:101 +#: ../../content/applications/finance/fiscal_localizations/france.rst:104 msgid "Date (yyyyMMdd)" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/france.rst:71 +#: ../../content/applications/finance/fiscal_localizations/france.rst:76 msgid "05" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/france.rst:71 -#: ../../content/applications/finance/fiscal_localizations/france.rst:186 +#: ../../content/applications/finance/fiscal_localizations/france.rst:76 +#: ../../content/applications/finance/fiscal_localizations/france.rst:191 msgid "CompteNum" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/france.rst:71 +#: ../../content/applications/finance/fiscal_localizations/france.rst:76 msgid "Account Number" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/france.rst:71 +#: ../../content/applications/finance/fiscal_localizations/france.rst:76 msgid "`account.code`" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/france.rst:73 +#: ../../content/applications/finance/fiscal_localizations/france.rst:78 msgid "06" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/france.rst:73 +#: ../../content/applications/finance/fiscal_localizations/france.rst:78 msgid "CompteLib" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/france.rst:73 +#: ../../content/applications/finance/fiscal_localizations/france.rst:78 msgid "Account Label" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/france.rst:73 +#: ../../content/applications/finance/fiscal_localizations/france.rst:78 msgid "`account.name`" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/france.rst:75 +#: ../../content/applications/finance/fiscal_localizations/france.rst:80 msgid "07" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/france.rst:75 +#: ../../content/applications/finance/fiscal_localizations/france.rst:80 msgid "CompAuxNum" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/france.rst:75 +#: ../../content/applications/finance/fiscal_localizations/france.rst:80 msgid "Secondary account Number (accepts null)" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/france.rst:75 +#: ../../content/applications/finance/fiscal_localizations/france.rst:80 msgid "`partner.ref`" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/france.rst:78 +#: ../../content/applications/finance/fiscal_localizations/france.rst:83 msgid "08" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/france.rst:78 +#: ../../content/applications/finance/fiscal_localizations/france.rst:83 msgid "CompAuxLib" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/france.rst:78 +#: ../../content/applications/finance/fiscal_localizations/france.rst:83 msgid "Secondary account Label (accepts null)" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/france.rst:78 +#: ../../content/applications/finance/fiscal_localizations/france.rst:83 msgid "`partner.name`" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/france.rst:81 +#: ../../content/applications/finance/fiscal_localizations/france.rst:86 msgid "09" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/france.rst:81 +#: ../../content/applications/finance/fiscal_localizations/france.rst:86 msgid "PieceRef" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/france.rst:81 +#: ../../content/applications/finance/fiscal_localizations/france.rst:86 msgid "Document Reference" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/france.rst:81 +#: ../../content/applications/finance/fiscal_localizations/france.rst:86 msgid "`move.ref` and `move.name` if `EcritureNum` is not provided" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/france.rst:84 +#: ../../content/applications/finance/fiscal_localizations/france.rst:89 msgid "PieceDate" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/france.rst:84 +#: ../../content/applications/finance/fiscal_localizations/france.rst:89 msgid "Document Date" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/france.rst:86 +#: ../../content/applications/finance/fiscal_localizations/france.rst:91 msgid "11" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/france.rst:86 +#: ../../content/applications/finance/fiscal_localizations/france.rst:91 msgid "EcritureLib" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/france.rst:86 +#: ../../content/applications/finance/fiscal_localizations/france.rst:91 msgid "Account entry Label" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/france.rst:86 +#: ../../content/applications/finance/fiscal_localizations/france.rst:91 msgid "`move_line.name`" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/france.rst:88 +#: ../../content/applications/finance/fiscal_localizations/france.rst:93 msgid "Debit amount" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/france.rst:88 +#: ../../content/applications/finance/fiscal_localizations/france.rst:93 msgid "`move_line.debit`" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/france.rst:88 -#: ../../content/applications/finance/fiscal_localizations/france.rst:90 -#: ../../content/applications/finance/fiscal_localizations/france.rst:101 -#: ../../content/applications/finance/fiscal_localizations/france.rst:111 +#: ../../content/applications/finance/fiscal_localizations/france.rst:93 +#: ../../content/applications/finance/fiscal_localizations/france.rst:95 +#: ../../content/applications/finance/fiscal_localizations/france.rst:106 +#: ../../content/applications/finance/fiscal_localizations/france.rst:116 msgid "Float" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/france.rst:90 -#: ../../content/applications/finance/fiscal_localizations/france.rst:114 +#: ../../content/applications/finance/fiscal_localizations/france.rst:95 +#: ../../content/applications/finance/fiscal_localizations/france.rst:119 msgid "13" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/france.rst:90 +#: ../../content/applications/finance/fiscal_localizations/france.rst:95 msgid "Credit amount (Field name \"Crédit\" is not allowed)" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/france.rst:90 +#: ../../content/applications/finance/fiscal_localizations/france.rst:95 msgid "`move_line.credit`" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/france.rst:93 +#: ../../content/applications/finance/fiscal_localizations/france.rst:98 msgid "14" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/france.rst:93 +#: ../../content/applications/finance/fiscal_localizations/france.rst:98 msgid "EcritureLet" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/france.rst:93 +#: ../../content/applications/finance/fiscal_localizations/france.rst:98 msgid "Accounting entry cross reference (accepts null)" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/france.rst:93 +#: ../../content/applications/finance/fiscal_localizations/france.rst:98 msgid "`move_line.fec_matching_number`" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/france.rst:96 +#: ../../content/applications/finance/fiscal_localizations/france.rst:101 msgid "DateLet" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/france.rst:96 +#: ../../content/applications/finance/fiscal_localizations/france.rst:101 msgid "Accounting entry date (accepts null)" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/france.rst:96 -#: ../../content/applications/finance/fiscal_localizations/france.rst:99 +#: ../../content/applications/finance/fiscal_localizations/france.rst:101 +#: ../../content/applications/finance/fiscal_localizations/france.rst:104 msgid "unused" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/france.rst:99 +#: ../../content/applications/finance/fiscal_localizations/france.rst:104 msgid "16" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/france.rst:99 +#: ../../content/applications/finance/fiscal_localizations/france.rst:104 msgid "ValidDate" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/france.rst:99 +#: ../../content/applications/finance/fiscal_localizations/france.rst:104 msgid "Accounting entry validation date" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/france.rst:101 +#: ../../content/applications/finance/fiscal_localizations/france.rst:106 msgid "17" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/france.rst:101 +#: ../../content/applications/finance/fiscal_localizations/france.rst:106 msgid "Montantdevise" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/france.rst:101 +#: ../../content/applications/finance/fiscal_localizations/france.rst:106 msgid "Currency amount (accepts null)" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/france.rst:101 +#: ../../content/applications/finance/fiscal_localizations/france.rst:106 msgid "`move_line.amount_currency`" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/france.rst:104 +#: ../../content/applications/finance/fiscal_localizations/france.rst:109 msgid "18" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/france.rst:104 +#: ../../content/applications/finance/fiscal_localizations/france.rst:109 msgid "Idevise" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/france.rst:104 +#: ../../content/applications/finance/fiscal_localizations/france.rst:109 msgid "Currency identifier (accepts null)" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/france.rst:104 +#: ../../content/applications/finance/fiscal_localizations/france.rst:109 msgid "`currency.name`" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/france.rst:108 +#: ../../content/applications/finance/fiscal_localizations/france.rst:113 msgid "These two fields can be found in place of the others in the sence above." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/france.rst:111 +#: ../../content/applications/finance/fiscal_localizations/france.rst:116 msgid "Montant" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/france.rst:111 +#: ../../content/applications/finance/fiscal_localizations/france.rst:116 msgid "Amount" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/france.rst:111 +#: ../../content/applications/finance/fiscal_localizations/france.rst:116 msgid "`move_line.debit` or `move_line.credit`" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/france.rst:114 +#: ../../content/applications/finance/fiscal_localizations/france.rst:119 msgid "Sens" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/france.rst:114 +#: ../../content/applications/finance/fiscal_localizations/france.rst:119 msgid "Can be \"C\" for Credit or \"D\" for Debit" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/france.rst:114 +#: ../../content/applications/finance/fiscal_localizations/france.rst:119 msgid "determines `move_line.debit` or `move_line.credit`" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/france.rst:114 +#: ../../content/applications/finance/fiscal_localizations/france.rst:119 msgid "Char" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/france.rst:119 +#: ../../content/applications/finance/fiscal_localizations/france.rst:124 msgid "Implementation details" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/france.rst:121 +#: ../../content/applications/finance/fiscal_localizations/france.rst:126 msgid "The following accounting entities are imported from the FEC files: **Accounts, Journals, Partners**, and **Moves**." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/france.rst:124 +#: ../../content/applications/finance/fiscal_localizations/france.rst:129 msgid "Our module determines the encoding, the line-terminator character, and the separator that are used in the file." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/france.rst:127 +#: ../../content/applications/finance/fiscal_localizations/france.rst:132 msgid "A check is then performed to see if every line has the correct number of fields corresponding to the header." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/france.rst:130 +#: ../../content/applications/finance/fiscal_localizations/france.rst:135 msgid "If the check passes, then the file is read in full, kept in memory, and scanned. Accounting entities are imported one type at a time, in the following order." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/france.rst:134 +#: ../../content/applications/finance/fiscal_localizations/france.rst:139 msgid "Accounts" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/france.rst:136 +#: ../../content/applications/finance/fiscal_localizations/france.rst:141 msgid "Every accounting entry is related to an account, which should be determined by the field `CompteNum`." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/france.rst:140 +#: ../../content/applications/finance/fiscal_localizations/france.rst:145 msgid "Code matching" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/france.rst:142 +#: ../../content/applications/finance/fiscal_localizations/france.rst:147 msgid "Should a similar account code already be present in the system, the existing one is used instead of creating a new one." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/france.rst:145 +#: ../../content/applications/finance/fiscal_localizations/france.rst:150 msgid "Accounts in Odoo generally have a number of digits that are default for the fiscal localization. As the FEC module is related to the French localization, the default number of relevant digits is 6." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/france.rst:148 +#: ../../content/applications/finance/fiscal_localizations/france.rst:153 msgid "This means that the account codes the trailing zeroes are right-trimmed, and that the comparison between the account codes in the FEC file and the ones already existing in Odoo is performed only on the first six digits of the codes." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/france.rst:153 +#: ../../content/applications/finance/fiscal_localizations/france.rst:158 msgid "The account code `65800000` in the file is matched against an existing `658000` account in Odoo, and that account is used instead of creating a new one." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/france.rst:157 +#: ../../content/applications/finance/fiscal_localizations/france.rst:162 msgid "Reconcilable flag" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/france.rst:159 +#: ../../content/applications/finance/fiscal_localizations/france.rst:164 msgid "An account is technically flagged as *reconcilable* if the first line in which it appears has the `EcritureLet` field filled out, as this flag means that the accounting entry is going to be reconciled with another one." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/france.rst:165 +#: ../../content/applications/finance/fiscal_localizations/france.rst:170 msgid "In case the line somehow has this field not filled out, but the entry still has to be reconciled with a payment that hasn't yet been recorded, this isn't a problem anyway; the account is flagged as reconcilable as soon as the import of the move lines requires it." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/france.rst:170 +#: ../../content/applications/finance/fiscal_localizations/france.rst:175 msgid "Account type and Templates matching" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/france.rst:172 +#: ../../content/applications/finance/fiscal_localizations/france.rst:177 msgid "As the **type** of the account is not specified in the FEC format, **new** accounts are created with the default type *Current Assets* and then, at the end of the import process, they are matched against the installed Chart of Account templates. Also, the *reconcile* flag is also computed this way." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/france.rst:177 +#: ../../content/applications/finance/fiscal_localizations/france.rst:182 msgid "The match is done with the left-most digits, starting by using all digits, then 3, then 2." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/france.rst:182 +#: ../../content/applications/finance/fiscal_localizations/france.rst:187 #: ../../content/applications/finance/fiscal_localizations/united_arab_emirates.rst:54 msgid "Code" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/france.rst:182 +#: ../../content/applications/finance/fiscal_localizations/france.rst:187 msgid "Full comparison" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/france.rst:182 +#: ../../content/applications/finance/fiscal_localizations/france.rst:187 msgid "3-digits comparison" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/france.rst:182 +#: ../../content/applications/finance/fiscal_localizations/france.rst:187 msgid "2-digits comparison" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/france.rst:184 +#: ../../content/applications/finance/fiscal_localizations/france.rst:189 #: ../../content/applications/finance/payment_providers/authorize.rst:82 msgid "Template" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/france.rst:184 -#: ../../content/applications/finance/fiscal_localizations/france.rst:184 +#: ../../content/applications/finance/fiscal_localizations/france.rst:189 +#: ../../content/applications/finance/fiscal_localizations/france.rst:189 msgid "`400000`" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/france.rst:184 +#: ../../content/applications/finance/fiscal_localizations/france.rst:189 msgid "`400`" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/france.rst:184 -#: ../../content/applications/finance/fiscal_localizations/france.rst:186 +#: ../../content/applications/finance/fiscal_localizations/france.rst:189 +#: ../../content/applications/finance/fiscal_localizations/france.rst:191 msgid "`40`" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/france.rst:186 -#: ../../content/applications/finance/fiscal_localizations/france.rst:186 +#: ../../content/applications/finance/fiscal_localizations/france.rst:191 +#: ../../content/applications/finance/fiscal_localizations/france.rst:191 msgid "`40100000`" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/france.rst:186 +#: ../../content/applications/finance/fiscal_localizations/france.rst:191 msgid "`401`" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/france.rst:188 +#: ../../content/applications/finance/fiscal_localizations/france.rst:193 msgid "**Result**" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/france.rst:188 +#: ../../content/applications/finance/fiscal_localizations/france.rst:193 msgid "Match **found**" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/france.rst:191 +#: ../../content/applications/finance/fiscal_localizations/france.rst:196 msgid "The type of the account is then flagged as *payable* and *reconcilable* as per the account template." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/france.rst:196 +#: ../../content/applications/finance/fiscal_localizations/france.rst:201 msgid "Journals are also checked against those already existing in Odoo to avoid duplicates, also in the case of multiple FEC files imports." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/france.rst:199 +#: ../../content/applications/finance/fiscal_localizations/france.rst:204 msgid "Should a similar journal code already be present in the system, the existing one is used instead of creating a new one." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/france.rst:202 +#: ../../content/applications/finance/fiscal_localizations/france.rst:207 msgid "New journals have their name prefixed by the string ``FEC-``." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/france.rst:205 +#: ../../content/applications/finance/fiscal_localizations/france.rst:210 msgid "`ACHATS` -> `FEC-ACHATS`" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/france.rst:207 +#: ../../content/applications/finance/fiscal_localizations/france.rst:212 msgid "The journals are *not* archived, the user is entitled to handle them as he wishes." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/france.rst:210 +#: ../../content/applications/finance/fiscal_localizations/france.rst:215 msgid "Journal type determination" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/france.rst:212 +#: ../../content/applications/finance/fiscal_localizations/france.rst:217 msgid "The journal type is also not specified in the format (as per the accounts) and therefore it is at first created with the default type `general`." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/france.rst:215 +#: ../../content/applications/finance/fiscal_localizations/france.rst:220 msgid "At the end of the import process, the type is determined as per these rules regarding related moves and accounts:" msgstr "" @@ -21129,364 +21133,364 @@ msgstr "" msgid "`general`: for everything else." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/france.rst:231 +#: ../../content/applications/finance/fiscal_localizations/france.rst:236 msgid "A minimum of three moves is necessary for journal type identification." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/france.rst:232 +#: ../../content/applications/finance/fiscal_localizations/france.rst:237 msgid "A threshold of 70% of moves must correspond to a criteria for a journal type to be determined." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/france.rst:235 +#: ../../content/applications/finance/fiscal_localizations/france.rst:240 msgid "Suppose we are analyzing the moves that share a certain `journal_id`." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/france.rst:238 -#: ../../content/applications/finance/fiscal_localizations/france.rst:269 +#: ../../content/applications/finance/fiscal_localizations/france.rst:243 +#: ../../content/applications/finance/fiscal_localizations/france.rst:274 msgid "Moves" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/france.rst:238 +#: ../../content/applications/finance/fiscal_localizations/france.rst:243 msgid "Count" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/france.rst:238 +#: ../../content/applications/finance/fiscal_localizations/france.rst:243 msgid "Percentage" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/france.rst:240 +#: ../../content/applications/finance/fiscal_localizations/france.rst:245 msgid "that have a sale account line and no purchase account line" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/france.rst:242 +#: ../../content/applications/finance/fiscal_localizations/france.rst:247 msgid "that have a purchase account line and no sale account line" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/france.rst:242 +#: ../../content/applications/finance/fiscal_localizations/france.rst:247 msgid "25%" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/france.rst:244 +#: ../../content/applications/finance/fiscal_localizations/france.rst:249 msgid "that have a liquidity account line" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/france.rst:244 +#: ../../content/applications/finance/fiscal_localizations/france.rst:249 msgid "3" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/france.rst:244 +#: ../../content/applications/finance/fiscal_localizations/france.rst:249 msgid "**75%**" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/france.rst:246 +#: ../../content/applications/finance/fiscal_localizations/france.rst:251 msgid "**Total**" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/france.rst:246 +#: ../../content/applications/finance/fiscal_localizations/france.rst:251 msgid "4" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/france.rst:246 +#: ../../content/applications/finance/fiscal_localizations/france.rst:251 msgid "100%" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/france.rst:249 +#: ../../content/applications/finance/fiscal_localizations/france.rst:254 msgid "The journal `type` would be `bank`, because the bank moves percentage (75%) exceeds the threshold (70%)." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/france.rst:253 +#: ../../content/applications/finance/fiscal_localizations/france.rst:258 msgid "Partners" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/france.rst:255 +#: ../../content/applications/finance/fiscal_localizations/france.rst:260 msgid "Each partner keeps its `Reference` from the field `CompAuxNum`." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/france.rst:259 +#: ../../content/applications/finance/fiscal_localizations/france.rst:264 msgid "These fields are searchable, in line with former FEC imports on the accounting expert's side for fiscal/audit purposes." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/france.rst:264 +#: ../../content/applications/finance/fiscal_localizations/france.rst:269 msgid "Users can merge partners with the Data Cleaning App, where Vendors and Customers or similar partner entries may be merged by the user, with assistance from the system that groups them by similar entries." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/france.rst:271 +#: ../../content/applications/finance/fiscal_localizations/france.rst:276 msgid "Entries are immediately posted and reconciled after submission, using the `EcritureLet` field to do the matching between the entries themselves." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/france.rst:274 +#: ../../content/applications/finance/fiscal_localizations/france.rst:279 msgid "The `EcritureNum` field represents the name of the moves. We noticed that sometimes it may not be filled out. In this case, the field `PieceRef` is used." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/france.rst:278 +#: ../../content/applications/finance/fiscal_localizations/france.rst:283 msgid "Rounding issues" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/france.rst:280 +#: ../../content/applications/finance/fiscal_localizations/france.rst:285 msgid "There is a rounding tolerance with a currency-related precision on debit and credit (i.e., 0.01 for EUR). Under this tolerance, a new line is added to the move, named *Import rounding difference*, targeting the accounts:" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/france.rst:284 +#: ../../content/applications/finance/fiscal_localizations/france.rst:289 msgid "`658000` Charges diverses de gestion courante, for added debits" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/france.rst:285 +#: ../../content/applications/finance/fiscal_localizations/france.rst:290 msgid "`758000` Produits divers de gestion courante, for added credits" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/france.rst:288 +#: ../../content/applications/finance/fiscal_localizations/france.rst:293 msgid "Missing move name" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/france.rst:290 +#: ../../content/applications/finance/fiscal_localizations/france.rst:295 msgid "Should the `EcritureNum` not be filled out, it may also happen that the `PieceRef` field is also not suited to determine the move name (it may be used as an accounting move line reference) leaving no way to actually find which lines are to be grouped in a single move, and effectively impeding the creation of balanced moves." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/france.rst:295 +#: ../../content/applications/finance/fiscal_localizations/france.rst:300 msgid "One last attempt is made, grouping all lines from the same journal and date (`JournalLib`, `EcritureDate`). Should this grouping generate balanced moves (sum(credit) - sum(debit) = 0), then each different combination of journal and date creates a new move." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/france.rst:300 +#: ../../content/applications/finance/fiscal_localizations/france.rst:305 msgid "`ACH` + `2021/05/01` --> new move on journal `ACH` with name `20210501`." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/france.rst:302 +#: ../../content/applications/finance/fiscal_localizations/france.rst:307 msgid "Should this attempt fail, the user is prompted an error message with all the move lines that are supposedly unbalanced." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/france.rst:308 +#: ../../content/applications/finance/fiscal_localizations/france.rst:313 msgid "If a line has the partner information specified, the information is copied to the accounting move itself if the targeted Journal is of type *payable* or *receivable*." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/france.rst:312 +#: ../../content/applications/finance/fiscal_localizations/france.rst:317 msgid "Export" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/france.rst:314 +#: ../../content/applications/finance/fiscal_localizations/france.rst:319 msgid "If you have installed the French :ref:`fiscal localization package `, you should be able to download the FEC. To do so, go to :menuselection:`Accounting --> Reporting --> France --> FEC`." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/france.rst:320 +#: ../../content/applications/finance/fiscal_localizations/france.rst:325 msgid "If you do not see the submenu **FEC**, go to :menuselection:`Apps`, remove the *Apps* filter, then search for the module named **France-FEC** and make sure it is installed." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/france.rst:325 +#: ../../content/applications/finance/fiscal_localizations/france.rst:330 msgid "`Official Technical Specification (fr) `_" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/france.rst:327 +#: ../../content/applications/finance/fiscal_localizations/france.rst:332 msgid "`Test-Compta-Demat (Official FEC Testing tool) `_" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/france.rst:331 +#: ../../content/applications/finance/fiscal_localizations/france.rst:336 msgid "French Accounting Reports" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/france.rst:333 +#: ../../content/applications/finance/fiscal_localizations/france.rst:338 msgid "If you have installed the French Accounting, you will have access to some accounting reports specific to France:" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/france.rst:336 +#: ../../content/applications/finance/fiscal_localizations/france.rst:341 msgid "Bilan comptable" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/france.rst:337 +#: ../../content/applications/finance/fiscal_localizations/france.rst:342 msgid "Compte de résultats" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/france.rst:338 +#: ../../content/applications/finance/fiscal_localizations/france.rst:343 msgid "Plan de Taxes France" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/france.rst:341 +#: ../../content/applications/finance/fiscal_localizations/france.rst:346 msgid "Get the VAT anti-fraud certification with Odoo" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/france.rst:343 +#: ../../content/applications/finance/fiscal_localizations/france.rst:348 msgid "As of January 1st 2018, a new anti-fraud legislation comes into effect in France and DOM-TOM. This new legislation stipulates certain criteria concerning the inalterability, security, storage and archiving of sales data. These legal requirements are implemented in Odoo, version 9 onward, through a module and a certificate of conformity to download." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/france.rst:350 +#: ../../content/applications/finance/fiscal_localizations/france.rst:355 msgid "Is my company required to use anti-fraud software?" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/france.rst:352 +#: ../../content/applications/finance/fiscal_localizations/france.rst:357 msgid "Your company is required to use an anti-fraud cash register software like Odoo (CGI art. 286, I. 3° bis) if:" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/france.rst:355 +#: ../../content/applications/finance/fiscal_localizations/france.rst:360 msgid "You are taxable (not VAT exempt) in France or any DOM-TOM," msgstr "" -#: ../../content/applications/finance/fiscal_localizations/france.rst:356 +#: ../../content/applications/finance/fiscal_localizations/france.rst:361 msgid "Some of your customers are private individuals (B2C)." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/france.rst:358 +#: ../../content/applications/finance/fiscal_localizations/france.rst:363 msgid "This rule applies to any company size. Auto-entrepreneurs are exempted from VAT and therefore are not affected." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/france.rst:362 +#: ../../content/applications/finance/fiscal_localizations/france.rst:367 msgid "Get certified with Odoo" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/france.rst:364 +#: ../../content/applications/finance/fiscal_localizations/france.rst:369 msgid "Getting compliant with Odoo is very easy." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/france.rst:366 +#: ../../content/applications/finance/fiscal_localizations/france.rst:371 msgid "Your company is requested by the tax administration to deliver a certificate of conformity testifying that your software complies with the anti-fraud legislation. This certificate is granted by Odoo SA to Odoo Enterprise users `here `_. If you use Odoo Community, you should :doc:`upgrade to Odoo Enterprise ` or contact your Odoo service provider." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/france.rst:373 +#: ../../content/applications/finance/fiscal_localizations/france.rst:378 msgid "In case of non-conformity, your company risks a fine of €7,500." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/france.rst:375 +#: ../../content/applications/finance/fiscal_localizations/france.rst:380 msgid "To get the certification, just follow the following steps:" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/france.rst:377 +#: ../../content/applications/finance/fiscal_localizations/france.rst:382 msgid "If you use **Odoo Point of Sale**, :ref:`install ` the **France - VAT Anti-Fraud Certification for Point of Sale (CGI 286 I-3 bis)** module by going to :menuselection:`Apps`, removing the *Apps* filter, then searching for *l10n_fr_pos_cert*, and installing the module." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/france.rst:381 +#: ../../content/applications/finance/fiscal_localizations/france.rst:386 msgid "Make sure a country is set on your company, otherwise your entries won’t be encrypted for the inalterability check. To edit your company’s data, go to :menuselection:`Settings --> Users & Companies --> Companies`. Select a country from the list; Do not create a new country." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/france.rst:385 +#: ../../content/applications/finance/fiscal_localizations/france.rst:390 msgid "Download the mandatory certificate of conformity delivered by Odoo SA `here `__." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/france.rst:389 +#: ../../content/applications/finance/fiscal_localizations/france.rst:394 msgid "To install the module in any system created before December 18th 2017, you should update the modules list. To do so, activate the :ref:`developer mode `. Then go to the *Apps* menu and press *Update Modules List* in the top-menu." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/france.rst:393 +#: ../../content/applications/finance/fiscal_localizations/france.rst:398 msgid "In case you run Odoo on-premise, you need to update your installation and restart your server beforehand." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/france.rst:395 +#: ../../content/applications/finance/fiscal_localizations/france.rst:400 msgid "If you have installed the initial version of the anti-fraud module (prior to December 18th 2017), you need to update it. The module's name was *France - Accounting - Certified CGI 286 I-3 bis*. After an update of the modules list, search for the updated module in *Apps*, select it and click *Upgrade*. Finally, make sure the following module *l10n_fr_sale_closing* is installed." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/france.rst:404 +#: ../../content/applications/finance/fiscal_localizations/france.rst:409 msgid "Anti-fraud features" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/france.rst:406 +#: ../../content/applications/finance/fiscal_localizations/france.rst:411 msgid "The anti-fraud module introduces the following features:" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/france.rst:408 +#: ../../content/applications/finance/fiscal_localizations/france.rst:413 msgid "**Inalterability**: deactivation of all the ways to cancel or modify key data of POS orders, invoices and journal entries;" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/france.rst:410 +#: ../../content/applications/finance/fiscal_localizations/france.rst:415 msgid "**Security**: chaining algorithm to verify the inalterability;" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/france.rst:411 +#: ../../content/applications/finance/fiscal_localizations/france.rst:416 msgid "**Storage**: automatic sales closings with computation of both period and cumulative totals (daily, monthly, annually)." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/france.rst:415 +#: ../../content/applications/finance/fiscal_localizations/france.rst:420 msgid "Inalterability" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/france.rst:417 +#: ../../content/applications/finance/fiscal_localizations/france.rst:422 msgid "All the possible ways to cancel and modify key data of paid POS orders, confirmed invoices and journal entries are deactivated, if the company is located in France or in any DOM-TOM." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/france.rst:423 +#: ../../content/applications/finance/fiscal_localizations/france.rst:428 msgid "If you run a multi-companies environment, only the documents of such companies are impacted." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/france.rst:426 +#: ../../content/applications/finance/fiscal_localizations/france.rst:431 msgid "Security" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/france.rst:428 +#: ../../content/applications/finance/fiscal_localizations/france.rst:433 msgid "To ensure inalterability, every order or journal entry is encrypted upon validation. This number (or hash) is calculated from the key data of the document as well as from the hash of the precedent documents." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/france.rst:433 +#: ../../content/applications/finance/fiscal_localizations/france.rst:438 msgid "The module introduces an interface to test the data inalterability. If any information is modified on a document after its validation, the test will fail. The algorithm recomputes all the hashes and compares them against the initial ones. In case of failure, the system points out the first corrupted document recorded in the system." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/france.rst:439 +#: ../../content/applications/finance/fiscal_localizations/france.rst:444 msgid "Users with *Manager* access rights can launch the inalterability check. For POS orders, go to :menuselection:`Point of Sales --> Reporting --> French Statements`. For invoices or journal entries, go to :menuselection:`Invoicing/Accounting --> Reporting --> French Statements`." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/france.rst:446 +#: ../../content/applications/finance/fiscal_localizations/france.rst:451 msgid "Storage" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/france.rst:448 +#: ../../content/applications/finance/fiscal_localizations/france.rst:453 msgid "The system also processes automatic sales closings on a daily, monthly and annual basis. Such closings distinctly compute the sales total of the period as well as the cumulative grand totals from the very first sales entry recorded in the system." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/france.rst:454 +#: ../../content/applications/finance/fiscal_localizations/france.rst:459 msgid "Closings can be found in the *French Statements* menu of Point of Sale, Invoicing and Accounting apps." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/france.rst:459 +#: ../../content/applications/finance/fiscal_localizations/france.rst:464 msgid "Closings compute the totals for journal entries of sales journals (Journal Type = Sales)." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/france.rst:461 +#: ../../content/applications/finance/fiscal_localizations/france.rst:466 msgid "For multi-companies environments, such closings are performed by company." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/france.rst:463 +#: ../../content/applications/finance/fiscal_localizations/france.rst:468 msgid "POS orders are posted as journal entries at the closing of the POS session. Closing a POS session can be done anytime. To prompt users to do it on a daily basis, the module prevents from resuming a session opened more than 24 hours ago. Such a session must be closed before selling again." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/france.rst:469 +#: ../../content/applications/finance/fiscal_localizations/france.rst:474 msgid "A period’s total is computed from all the journal entries posted after the previous closing of the same type, regardless of their posting date. If you record a new sales transaction for a period already closed, it will be counted in the very next closing." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/france.rst:476 +#: ../../content/applications/finance/fiscal_localizations/france.rst:481 msgid "For test & audit purposes such closings can be manually generated in the :ref:`developer mode `." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/france.rst:478 +#: ../../content/applications/finance/fiscal_localizations/france.rst:483 msgid "Then go to :menuselection:`Settings --> Technical --> Automation --> Scheduled Actions`." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/france.rst:481 +#: ../../content/applications/finance/fiscal_localizations/france.rst:486 msgid "Responsibilities" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/france.rst:483 +#: ../../content/applications/finance/fiscal_localizations/france.rst:488 msgid "Do not uninstall the module! If you do so, the hashes will be reset and none of your past data will be longer guaranteed as being inalterable." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/france.rst:486 +#: ../../content/applications/finance/fiscal_localizations/france.rst:491 msgid "Users remain responsible for their Odoo instance and must use it with due diligence. It is not permitted to modify the source code which guarantees the inalterability of data." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/france.rst:490 +#: ../../content/applications/finance/fiscal_localizations/france.rst:495 msgid "Odoo absolves itself of all and any responsibility in case of changes in the module’s functions caused by 3rd party applications not certified by Odoo." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/france.rst:494 +#: ../../content/applications/finance/fiscal_localizations/france.rst:499 msgid "More Information" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/france.rst:496 +#: ../../content/applications/finance/fiscal_localizations/france.rst:501 msgid "You can find more information about this legislation in the following official documents." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/france.rst:500 +#: ../../content/applications/finance/fiscal_localizations/france.rst:505 msgid "`Frequently Asked Questions `_" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/france.rst:502 +#: ../../content/applications/finance/fiscal_localizations/france.rst:507 msgid "`Official Statement `_" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/france.rst:504 +#: ../../content/applications/finance/fiscal_localizations/france.rst:509 msgid "`Item 88 of Finance Law 2016 `_" msgstr "" @@ -21715,7 +21719,7 @@ msgid "German Tax Accounting Standards: Odoo's guide to GoBD Compliance" msgstr "" #: ../../content/applications/finance/fiscal_localizations/germany.rst:173 -msgid "**GoBD** stands for `Grundsätze zur ordnungsmäßigen Führung und Aufbewahrung von Büchern, Aufzeichnungen und Unterlagen in elektronischer Form sowie zum Datenzugriff `_. In short, it is a **guideline for the proper management and storage of books, records, and documents in electronic form, as well as for data access**, that is relevant for the German tax authority, tax declaration, and balance sheet." +msgid "**GoBD** stands for `Grundsätze zur ordnungsmäßigen Führung und Aufbewahrung von Büchern, Aufzeichnungen und Unterlagen in elektronischer Form sowie zum Datenzugriff `_. In short, it is a **guideline for the proper management and storage of books, records, and documents in electronic form, as well as for data access**, that is relevant for the German tax authority, tax declaration, and balance sheet." msgstr "" #: ../../content/applications/finance/fiscal_localizations/germany.rst:180 @@ -24369,11 +24373,7 @@ msgid "To initialize the OSCU:" msgstr "" #: ../../content/applications/finance/fiscal_localizations/kenya.rst:39 -msgid "Go to the :guilabel:`eTIMS` tab." -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/kenya.rst:40 -msgid "Fill in the :guilabel:`eTIMS Branch Code` and :guilabel:`Serial Number` of the device." +msgid "Go to :menuselection:`Settings --> General Settings` and scroll down to the :guilabel:`Kenya eTIMS Integration` section." msgstr "" #: ../../content/applications/finance/fiscal_localizations/kenya.rst:41 @@ -24381,236 +24381,292 @@ msgid "Set the :guilabel:`eTIMS Server Mode` to :guilabel:`Test` for the initial msgstr "" #: ../../content/applications/finance/fiscal_localizations/kenya.rst:42 -msgid "Tick the **user agreement** and click :guilabel:`Initialize OSCU`." +msgid "Enter the :guilabel:`Serial Number` of the device and tick the two check boxes." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/kenya.rst:45 +#: ../../content/applications/finance/fiscal_localizations/kenya.rst:43 +msgid "Click :guilabel:`Initialize OSCU`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/kenya.rst:46 msgid "Three server modes are available:" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/kenya.rst:47 +#: ../../content/applications/finance/fiscal_localizations/kenya.rst:48 msgid ":guilabel:`Demo`: Designed for demo purposes; it uses mock data and does not require an initialized OSCU;" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/kenya.rst:49 +#: ../../content/applications/finance/fiscal_localizations/kenya.rst:50 msgid ":guilabel:`Test`: Used to test the connection to eTIMS;" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/kenya.rst:50 +#: ../../content/applications/finance/fiscal_localizations/kenya.rst:51 msgid ":guilabel:`Production`: Used for live databases that are ready to send data." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/kenya.rst:53 -msgid "If your device has **already been initialized** (through another ERP, for example), enable the :doc:`../../general/developer_mode`, go to the :guilabel:`eTIMS` tab, and enter the key obtained through a previous initialization in the :guilabel:`Device Communication Key` field. Click :guilabel:`Save manually`, then :guilabel:`Initialize OSCU` (which may take a moment to become available)." +#: ../../content/applications/finance/fiscal_localizations/kenya.rst:54 +msgid "If your device has **already been initialized** (through another ERP, for example), enable the :doc:`../../general/developer_mode`. Then, in the :guilabel:`Kenya eTIMS Integration` section, enter the ID of the unit in the :guilabel:`Unit ID` field and the key obtained through a previous initialization in the :guilabel:`CMC Key` field. Click :guilabel:`Save` when done." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/kenya.rst:60 -msgid "eTIMS codes" -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/kenya.rst:62 -msgid "Common standard codes are **automatically** fetched from the KRA eTIMS API servers every two days. To fetch them manually, proceed as follows:" -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/kenya.rst:65 -#: ../../content/applications/finance/fiscal_localizations/kenya.rst:84 -#: ../../content/applications/finance/fiscal_localizations/kenya.rst:98 -#: ../../content/applications/finance/fiscal_localizations/kenya.rst:296 -msgid "Enable the :doc:`../../general/developer_mode`." +#: ../../content/applications/finance/fiscal_localizations/kenya.rst:59 +msgid "Once the **OSCU module** has been :ref:`initialized `, an OSCU serial number is generated for each company on that database with its **country** set to :guilabel:`Kenya`. The serial number is generated based on the VAT number of the company (regardless of its validity). It is a unique and sequential serial number starting with the prefix `ODOO` followed by the company's **VAT number** and a sequence of numbers." msgstr "" #: ../../content/applications/finance/fiscal_localizations/kenya.rst:66 -msgid "Go to :menuselection:`Settings --> Technical --> Automation: Scheduled Actions` and search for :guilabel:`KE eTIMS: Fetch KRA standard codes`." +msgid "Registering on eTIMS" msgstr "" #: ../../content/applications/finance/fiscal_localizations/kenya.rst:68 -#: ../../content/applications/finance/fiscal_localizations/kenya.rst:87 -#: ../../content/applications/finance/fiscal_localizations/kenya.rst:299 +msgid "Taxpayers *must* sign up and create an account on the `KRA portal `_. If you do not have an account yet:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/kenya.rst:71 +msgid "Sign up, enter your **PIN**, and verify that all information is correct, including your phone number, email address, and postal address. Correct any errors on the `iTax page `_." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/kenya.rst:74 +msgid "An :abbr:`OTP (One-time Password)` is sent to the phone number provided. Unblock promotional messages if you do not receive it." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/kenya.rst:76 +msgid "Upload the **business owner ID** *or* **director's ID** (as listed on iTax), along with the filled-out and signed **commitment form** ." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/kenya.rst:78 +msgid "On the **eTIMS dashboard**, click :guilabel:`Service request` at the top of the page. Select :guilabel:`OSCU` as the **eTIMS type**, enter `Odoo KE LTD` as the third-party integrator, and enter your company's OSCU serial number retrieved earlier." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/kenya.rst:83 +msgid "Service request approvals are usually quick. If there's a delay, contact the eTIMS operation or KRA office." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/kenya.rst:86 +msgid "Commitment form" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/kenya.rst:88 +msgid "Part 1: Fill in the taxpayer's information." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/kenya.rst:89 +msgid "Part 2: Fill in the business owner's *or* director's information." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/kenya.rst:90 +msgid "Part 3: Fill in your unique serial number found in Odoo." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/kenya.rst:91 +msgid "Part 4: Tick **OSCU**, enter Odoo KE LTD PIN `PO52112956W`, and enter the Odoo version you're using (17.0 or onwards)." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/kenya.rst:93 +msgid "Part 5: Check the mandatory boxes, enter a date, and sign." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/kenya.rst:96 +msgid "eTIMS codes" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/kenya.rst:98 +msgid "Common standard codes are **automatically** fetched from the KRA eTIMS API servers every two days. To fetch them manually, proceed as follows:" +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/kenya.rst:101 +#: ../../content/applications/finance/fiscal_localizations/kenya.rst:120 +#: ../../content/applications/finance/fiscal_localizations/kenya.rst:134 +#: ../../content/applications/finance/fiscal_localizations/kenya.rst:329 +msgid "Enable the :doc:`../../general/developer_mode`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/kenya.rst:102 +msgid "Go to :menuselection:`Settings --> Technical --> Automation: Scheduled Actions` and search for :guilabel:`KE eTIMS: Fetch KRA standard codes`." +msgstr "" + +#: ../../content/applications/finance/fiscal_localizations/kenya.rst:104 +#: ../../content/applications/finance/fiscal_localizations/kenya.rst:123 +#: ../../content/applications/finance/fiscal_localizations/kenya.rst:332 msgid "Click the action in the list, then click :guilabel:`Run Manually` to fetch the codes." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/kenya.rst:70 -msgid "Go to :menuselection:`Accounting --> Vendors --> KE OSCU Codes` to view the complete list of fetched OSCU codes." +#: ../../content/applications/finance/fiscal_localizations/kenya.rst:106 +msgid "Go to :menuselection:`Accounting --> Configuration --> KE OSCU Codes` to view the complete list of fetched OSCU codes." msgstr "" #: ../../content/applications/finance/fiscal_localizations/kenya.rst:-1 msgid "List of fetched OSCU codes." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/kenya.rst:79 +#: ../../content/applications/finance/fiscal_localizations/kenya.rst:115 msgid "UNSPSC codes" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/kenya.rst:81 +#: ../../content/applications/finance/fiscal_localizations/kenya.rst:117 msgid "The KRA needs UNSPSC codes for a product to be **registered**. UNSPSC codes are **automatically** fetched from the KRA eTIMS API servers every day. To fetch them manually, proceed as follows:" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/kenya.rst:85 +#: ../../content/applications/finance/fiscal_localizations/kenya.rst:121 msgid "Go to :menuselection:`Settings --> Technical --> Automation: Scheduled Actions` and search for :guilabel:`KE eTIMS: Fetch UNSPSC codes from eTIMS`." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/kenya.rst:89 -msgid "Go to :menuselection:`Accounting --> Vendors --> KE UNSPSC Codes` to view the complete list of fetched UNSPSC codes." +#: ../../content/applications/finance/fiscal_localizations/kenya.rst:125 +msgid "Go to the **product form**, and in the :guilabel:`Accounting` tab, click the :guilabel:`UNSPSC Category` field to view the complete list of fetched UNSPSC codes." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/kenya.rst:93 +#: ../../content/applications/finance/fiscal_localizations/kenya.rst:129 msgid "Notices" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/kenya.rst:95 +#: ../../content/applications/finance/fiscal_localizations/kenya.rst:131 msgid "Notices are **automatically** fetched from the KRA eTIMS API servers every day. To fetch them **manually**, proceed as follows:" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/kenya.rst:99 +#: ../../content/applications/finance/fiscal_localizations/kenya.rst:135 msgid "Go to :menuselection:`Settings --> Technical --> Automation: Scheduled Actions` and search for :guilabel:`KE eTIMS: Fetch KRA notices from eTIMS`." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/kenya.rst:101 +#: ../../content/applications/finance/fiscal_localizations/kenya.rst:137 msgid "Click the action in the list, then click :guilabel:`Run Manually` to fetch the notices." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/kenya.rst:103 -msgid "Go to :menuselection:`Accounting --> Vendors --> KE OSCU Notices` to view the complete list of fetched notices." +#: ../../content/applications/finance/fiscal_localizations/kenya.rst:139 +msgid "Go to :menuselection:`Accounting --> Configuration --> KE OSCU Notices` to view the complete list of fetched notices." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/kenya.rst:112 +#: ../../content/applications/finance/fiscal_localizations/kenya.rst:148 msgid ":doc:`../../general/companies`" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/kenya.rst:114 +#: ../../content/applications/finance/fiscal_localizations/kenya.rst:150 msgid "If you have :ref:`multiple companies `, you can centralize and manage them all on a single Odoo database. The KRA identifies and differentiates the **main** company from its **subsidiaries** by using IDs. Furthermore, subsidiaries are classified as **branches** of the main company." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/kenya.rst:119 -msgid "To configure the company ID, open the **Settings** app, click :guilabel:`Update Info` in the :guilabel:`Companies` section, then click the :guilabel:`eTIMS` tab. The **main company** has a branch ID equal to `00` in a multi-company environment. Companies that are *not* the main company have a branch ID other than `00` and are assigned an ID by the KRA." +#: ../../content/applications/finance/fiscal_localizations/kenya.rst:155 +msgid "To configure the company's ID, open the **Settings** app, click :guilabel:`Update Info` in the :guilabel:`Companies` section, and search for the :guilabel:`eTIMS Branch Code` field. The **main company** has a branch ID equal to `00` in a multi-company environment. Companies that are *not* the main company have a branch ID other than `00` and are assigned an ID by the KRA." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/kenya.rst:124 +#: ../../content/applications/finance/fiscal_localizations/kenya.rst:160 msgid "To add a branch, go to the :guilabel:`Branches` tab in the **company settings** and click :guilabel:`Add a line`." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/kenya.rst:127 +#: ../../content/applications/finance/fiscal_localizations/kenya.rst:163 msgid "To fetch the **branch ID** from the KRA for your non-main companies, ensure the main company has a Kenyan :guilabel:`Tax ID` and the OSCU device has been :ref:`initialized `. Then, go to the :guilabel:`Branches` tab and click :guilabel:`Populate from KRA`." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/kenya.rst:132 +#: ../../content/applications/finance/fiscal_localizations/kenya.rst:168 msgid "The KRA considers each **place of supply** as a separate branch (ID)." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/kenya.rst:133 +#: ../../content/applications/finance/fiscal_localizations/kenya.rst:169 msgid "The **OSCU** device must be :ref:`initialized independently ` for each branch." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/kenya.rst:-1 -msgid "\"Populate from KRA\" button for branches." -msgstr "" - -#: ../../content/applications/finance/fiscal_localizations/kenya.rst:140 +#: ../../content/applications/finance/fiscal_localizations/kenya.rst:173 msgid "Contact branch ID" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/kenya.rst:142 +#: ../../content/applications/finance/fiscal_localizations/kenya.rst:175 msgid "To attribute a branch ID to a contact, access the contact form, go to the :guilabel:`Accounting` tab, and enter the branch code in the :guilabel:`eTIMS Branch Code` field." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/kenya.rst:146 +#: ../../content/applications/finance/fiscal_localizations/kenya.rst:179 msgid "By default, contacts' branch IDs are set to `OO`." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/kenya.rst:149 +#: ../../content/applications/finance/fiscal_localizations/kenya.rst:182 msgid "KRA sequences" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/kenya.rst:152 +#: ../../content/applications/finance/fiscal_localizations/kenya.rst:185 msgid "Odoo invoice sequences and KRA sequences are **different**." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/kenya.rst:154 +#: ../../content/applications/finance/fiscal_localizations/kenya.rst:187 msgid "In Odoo, invoice sequences depend on the **main company**. Main companies can see the invoices of branches, but branches **cannot** see the main company's invoices or those of other branches." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/kenya.rst:157 +#: ../../content/applications/finance/fiscal_localizations/kenya.rst:190 msgid "The KRA needs **independent** sequences per branch. Therefore, Odoo manages sequences individually per branch." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/kenya.rst:161 +#: ../../content/applications/finance/fiscal_localizations/kenya.rst:194 msgid "If you have a main company with two branches, the invoice sequence would be the following:" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/kenya.rst:163 -#: ../../content/applications/finance/fiscal_localizations/kenya.rst:169 +#: ../../content/applications/finance/fiscal_localizations/kenya.rst:196 +#: ../../content/applications/finance/fiscal_localizations/kenya.rst:202 msgid "Creating an invoice on **branch 1**: INV/2024/00001;" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/kenya.rst:164 +#: ../../content/applications/finance/fiscal_localizations/kenya.rst:197 msgid "Creating an invoice on **branch 2**: INV/2024/00002;" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/kenya.rst:165 +#: ../../content/applications/finance/fiscal_localizations/kenya.rst:198 msgid "Creating an invoice on the **main company**: INV/2024/00003." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/kenya.rst:167 +#: ../../content/applications/finance/fiscal_localizations/kenya.rst:200 msgid "This is how Odoo manages sequences to be compliant with the KRA regulations:" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/kenya.rst:170 +#: ../../content/applications/finance/fiscal_localizations/kenya.rst:203 msgid "Creating an invoice on **branch 2**: INV/2024/00001;" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/kenya.rst:171 +#: ../../content/applications/finance/fiscal_localizations/kenya.rst:204 msgid "Creating an invoice on the **main company**: INV/2024/00001." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/kenya.rst:174 +#: ../../content/applications/finance/fiscal_localizations/kenya.rst:207 msgid "Insurance" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/kenya.rst:176 -msgid "For **health service providers**, you can send insurance information about the main and branch companies and update it in eTIMS. To do so, open the **Settings** app, click :guilabel:`Update Info` in the :guilabel:`Companies` section, and in the :guilabel:`eTIMS` tab, fill in the fields related to your company: :guilabel:`Insurance Code`, :guilabel:`Insurance Name`, and :guilabel:`Insurance Rate`." +#: ../../content/applications/finance/fiscal_localizations/kenya.rst:209 +msgid "For **health service providers**, you can send insurance information about the main and branch companies and update it in eTIMS. To do so, go to :menuselection:`Accounting --> Configuration --> Settings`, scroll to the :guilabel:`Kenya eTIMS Integration` section, and fill in the :guilabel:`Code`, :guilabel:`Name`, and :guilabel:`Rate` fields. Click :guilabel:`Send Insurance Details` when done." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/kenya.rst:185 +#: ../../content/applications/finance/fiscal_localizations/kenya.rst:218 msgid "Product registration" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/kenya.rst:187 +#: ../../content/applications/finance/fiscal_localizations/kenya.rst:220 msgid "The KRA requires **products to be registered** first before conducting business operations (such as stock movements, :abbr:`BOM (Bill of Materials)`, customer invoices, etc.). For a product to be registered, the following fields must be defined on the product form:" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/kenya.rst:191 +#: ../../content/applications/finance/fiscal_localizations/kenya.rst:224 msgid "In the :guilabel:`General Information` tab: :guilabel:`Cost`." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/kenya.rst:192 +#: ../../content/applications/finance/fiscal_localizations/kenya.rst:225 msgid "In the :guilabel:`Accounting` tab:" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/kenya.rst:194 +#: ../../content/applications/finance/fiscal_localizations/kenya.rst:227 msgid ":guilabel:`Packaging Unit`;" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/kenya.rst:195 +#: ../../content/applications/finance/fiscal_localizations/kenya.rst:228 msgid ":guilabel:`Packaging Quantity`;" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/kenya.rst:196 +#: ../../content/applications/finance/fiscal_localizations/kenya.rst:229 msgid ":guilabel:`Origin Country`;" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/kenya.rst:197 +#: ../../content/applications/finance/fiscal_localizations/kenya.rst:230 msgid ":guilabel:`eTIMS Product Type`;" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/kenya.rst:198 +#: ../../content/applications/finance/fiscal_localizations/kenya.rst:231 msgid ":guilabel:`Insurance Applicable`;" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/kenya.rst:199 +#: ../../content/applications/finance/fiscal_localizations/kenya.rst:232 msgid ":ref:`UNSPSC Category `." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/kenya.rst:201 +#: ../../content/applications/finance/fiscal_localizations/kenya.rst:234 msgid "If the elements above are defined, the product is automatically registered while sending the operation to the KRA. If not, you will be alerted by a yellow banner at the top of the screen inviting you to check the missing elements." msgstr "" @@ -24618,75 +24674,75 @@ msgstr "" msgid "Product registration template." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/kenya.rst:209 +#: ../../content/applications/finance/fiscal_localizations/kenya.rst:242 msgid "Stock movements" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/kenya.rst:211 +#: ../../content/applications/finance/fiscal_localizations/kenya.rst:244 msgid "All **stock movements** must be sent to the KRA. They do not require an invoice if they are internal operations or stock adjustments; therefore, Odoo automatically sends them if at least one of the following conditions are met:" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/kenya.rst:215 +#: ../../content/applications/finance/fiscal_localizations/kenya.rst:248 msgid "No contact is set for the move;" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/kenya.rst:216 +#: ../../content/applications/finance/fiscal_localizations/kenya.rst:249 msgid "The contact is your main company or a branch of the main company." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/kenya.rst:218 +#: ../../content/applications/finance/fiscal_localizations/kenya.rst:251 msgid "If the stock moves are **external operations** (e.g., to contacts that are not part of the main company or its branches), the stock moves are automatically sent *after* the invoice is sent to eTIMS." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/kenya.rst:223 +#: ../../content/applications/finance/fiscal_localizations/kenya.rst:256 msgid "The stock move must be confirmed before sending the invoice to eTIMS." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/kenya.rst:224 +#: ../../content/applications/finance/fiscal_localizations/kenya.rst:257 msgid "The product(s) must be :ref:`registered ` for the stock move to be sent to eTIMS. If the product has not been registered yet, a yellow banner will prompt the products' registration." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/kenya.rst:231 +#: ../../content/applications/finance/fiscal_localizations/kenya.rst:264 msgid "Odoo automatically fetches new vendor bills from eTIMS every day. You need to confirm the fetched vendor bills and send the confirmation to the KRA. To confirm a vendor bill, it must be linked to one or several confirmed purchase order line(s)." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/kenya.rst:237 +#: ../../content/applications/finance/fiscal_localizations/kenya.rst:270 msgid "In the case of purchases (not customs imports), the steps to link purchase order lines with bills are the following:" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/kenya.rst:240 +#: ../../content/applications/finance/fiscal_localizations/kenya.rst:273 msgid "Go to :menuselection:`Accounting --> Vendors --> Bills`. The vendor bill is fetched from the KRA servers. The JSON file is available in the chatter of the vendor bill if needed." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/kenya.rst:243 +#: ../../content/applications/finance/fiscal_localizations/kenya.rst:276 msgid "Odoo looks at the :guilabel:`Tax ID` (PIN) of the vendor (partner);" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/kenya.rst:245 +#: ../../content/applications/finance/fiscal_localizations/kenya.rst:278 msgid "If it is unknown, a new contact (partner) is created." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/kenya.rst:246 +#: ../../content/applications/finance/fiscal_localizations/kenya.rst:279 msgid "If it is known and the branch ID is the same, Odoo uses the known contact." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/kenya.rst:248 +#: ../../content/applications/finance/fiscal_localizations/kenya.rst:281 msgid "In the fetched bill from the KRA, select the :guilabel:`Product`. Each vendor bill *must* contain a product to be confirmed and sent to eTIMS later on." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/kenya.rst:250 +#: ../../content/applications/finance/fiscal_localizations/kenya.rst:283 msgid "Odoo checks existing purchase order lines matching the product(s) entered at the previous step and the partner (if any). Click the :guilabel:`Purchase Order Line` field, and select the correct related purchase order line(s) matching the product(s). The quantities on the bill *must* be the same as the received quantities indicated on the purchase order." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/kenya.rst:255 +#: ../../content/applications/finance/fiscal_localizations/kenya.rst:288 msgid "If no existing purchase order line matches the lines of the fetched bill, click :guilabel:`Create Purchase Order` and create a purchase order based on the unmatched line(s). :guilabel:`Validate` the resulting stock move and :guilabel:`Confirm` the bill." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/kenya.rst:259 +#: ../../content/applications/finance/fiscal_localizations/kenya.rst:292 msgid "Set a method in the :guilabel:`eTIMS Payment Method` field.." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/kenya.rst:260 +#: ../../content/applications/finance/fiscal_localizations/kenya.rst:293 msgid "Once all steps are completed, click :guilabel:`Send to eTIMS` to send the vendor bill. When the vendor bill has been confirmed on eTIMS, the **KRA invoice number** can be found in the :guilabel:`eTIMS Details` tab." msgstr "" @@ -24694,120 +24750,120 @@ msgstr "" msgid "Bill registration steps." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/kenya.rst:268 +#: ../../content/applications/finance/fiscal_localizations/kenya.rst:301 msgid "Invoicing" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/kenya.rst:271 +#: ../../content/applications/finance/fiscal_localizations/kenya.rst:304 msgid "The KRA does *not* accept sales if the product is not in stock." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/kenya.rst:273 +#: ../../content/applications/finance/fiscal_localizations/kenya.rst:306 msgid "This is the **advised sales flow** in Odoo when selling:" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/kenya.rst:275 +#: ../../content/applications/finance/fiscal_localizations/kenya.rst:308 msgid "Create a **sales order**." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/kenya.rst:276 +#: ../../content/applications/finance/fiscal_localizations/kenya.rst:309 msgid ":guilabel:`Validate` the delivery." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/kenya.rst:277 +#: ../../content/applications/finance/fiscal_localizations/kenya.rst:310 msgid ":guilabel:`Confirm` the invoice." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/kenya.rst:278 +#: ../../content/applications/finance/fiscal_localizations/kenya.rst:311 msgid "Click :guilabel:`Send and print`, and then enable :guilabel:`Send to eTIMS`." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/kenya.rst:279 +#: ../../content/applications/finance/fiscal_localizations/kenya.rst:312 msgid "Click :guilabel:`Send & print` to send the invoice." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/kenya.rst:281 +#: ../../content/applications/finance/fiscal_localizations/kenya.rst:314 msgid "Once the invoice has been sent and signed by the KRA, the following information can be found on it:" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/kenya.rst:284 +#: ../../content/applications/finance/fiscal_localizations/kenya.rst:317 msgid "**KRA invoice number**;" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/kenya.rst:285 +#: ../../content/applications/finance/fiscal_localizations/kenya.rst:318 msgid "Mandatory KRA invoice fields, such as **SCU information**, **date**, **SCU ID**, **receipt number**, **item count**, **internal date**, and **receipt signature**;" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/kenya.rst:287 +#: ../../content/applications/finance/fiscal_localizations/kenya.rst:320 msgid "The **KRA tax table**;" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/kenya.rst:288 +#: ../../content/applications/finance/fiscal_localizations/kenya.rst:321 msgid "A unique **KRA QR code** for the signed invoice." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/kenya.rst:291 +#: ../../content/applications/finance/fiscal_localizations/kenya.rst:324 msgid "Imports" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/kenya.rst:293 +#: ../../content/applications/finance/fiscal_localizations/kenya.rst:326 msgid "Customs import codes are **automatically** fetched from the KRA eTIMS API servers every day. To fetch them manually, proceed as follows:" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/kenya.rst:297 +#: ../../content/applications/finance/fiscal_localizations/kenya.rst:330 msgid "Go to :menuselection:`Settings --> Technical --> Automation: Scheduled Actions` and search for :guilabel:`KE eTIMS: Receive Customs Imports from the OSCU`." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/kenya.rst:301 +#: ../../content/applications/finance/fiscal_localizations/kenya.rst:334 msgid "Go to :menuselection:`Accounting --> Vendors --> Customs Imports` to view the imported codes." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/kenya.rst:303 +#: ../../content/applications/finance/fiscal_localizations/kenya.rst:336 msgid "The following steps are required to send and have **customs imports** signed by the KRA:" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/kenya.rst:305 +#: ../../content/applications/finance/fiscal_localizations/kenya.rst:338 msgid "Go to :menuselection:`Accounting --> Vendors --> Customs Imports`; The customs import is fetched automatically from the KRA." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/kenya.rst:307 +#: ../../content/applications/finance/fiscal_localizations/kenya.rst:340 msgid "Match the imported item with an existing registered product in the :guilabel:`Product` field (or create a product if no related product exists)." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/kenya.rst:309 +#: ../../content/applications/finance/fiscal_localizations/kenya.rst:342 msgid "Set a vendor in the :guilabel:`Partner` field." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/kenya.rst:310 +#: ../../content/applications/finance/fiscal_localizations/kenya.rst:343 msgid "Based on the partner, match the imported item with its related purchase order (see :ref:`purchase steps `). The stock must be correctly adjusted when the customs import is approved." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/kenya.rst:314 +#: ../../content/applications/finance/fiscal_localizations/kenya.rst:347 msgid "If no related purchase order exists, create one and :guilabel:`Confirm` it. Then, confirm the delivery by clicking :guilabel:`Receive Products`, then :guilabel:`Validate` on the purchase order." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/kenya.rst:318 +#: ../../content/applications/finance/fiscal_localizations/kenya.rst:351 msgid "Click :guilabel:`Match and Approve` or :guilabel:`Match and Reject`, depending on the situation of the goods." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/kenya.rst:322 +#: ../../content/applications/finance/fiscal_localizations/kenya.rst:355 msgid "The JSON file received from the KRA is attached to the chatter of the customs import." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/kenya.rst:325 +#: ../../content/applications/finance/fiscal_localizations/kenya.rst:358 msgid "BOM" msgstr "" -#: ../../content/applications/finance/fiscal_localizations/kenya.rst:327 +#: ../../content/applications/finance/fiscal_localizations/kenya.rst:360 msgid "The KRA requires all BOMs to be sent to them. To send BOMs to eTIMS, the product and its components *must* be :ref:`registered `. To access a product's BOM, click on the product and then click the :guilabel:`Bill of Materials` smart button." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/kenya.rst:331 -msgid "Fill in the KRA's required fields in the :guilabel:`KRA eTIMS details` section of the :guilabel:`Accounting` tab, then click :guilabel:`Send to eTIMS`. The successful sending of the BOM is confirmed in the chatter, where you can also find the sent information in an attached JSON file." +#: ../../content/applications/finance/fiscal_localizations/kenya.rst:364 +msgid "Make sure the :ref:`KRA's required fields ` are filled in the :guilabel:`KRA eTIMS details` section of the :guilabel:`Accounting` tab in the product form, and click :guilabel:`Send to eTIMS`. The successful sending of the BOM is confirmed in the chatter, where you can also find the sent information in an attached JSON file." msgstr "" -#: ../../content/applications/finance/fiscal_localizations/kenya.rst:339 -msgid "The KRA does not accept credit notes with quantities or prices higher than the initial invoice. When reversing the invoice, a KRA reason must be indicated: in the credit note form, go to the :guilabel:`eTIMS Details` tab, select the :guilabel:`eTIMS Credit Note Reason`, and then select the invoice number in the :guilabel:`Reversal of` field." +#: ../../content/applications/finance/fiscal_localizations/kenya.rst:372 +msgid "The KRA does not accept credit notes with quantities or prices higher than the initial invoice. When creating a credit note, a KRA reason must be indicated: In the credit note form, go to the :guilabel:`eTIMS Details` tab, select the :guilabel:`eTIMS Credit Note Reason`, and then select the invoice number in the :guilabel:`Reversal of` field." msgstr "" #: ../../content/applications/finance/fiscal_localizations/luxembourg.rst:3 diff --git a/locale/sources/general.pot b/locale/sources/general.pot index 21c2689c0..cfd329ae6 100644 --- a/locale/sources/general.pot +++ b/locale/sources/general.pot @@ -8,7 +8,7 @@ msgid "" msgstr "" "Project-Id-Version: Odoo 17.0\n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2024-06-24 07:08+0000\n" +"POT-Creation-Date: 2024-07-23 13:30+0000\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME \n" "Language-Team: LANGUAGE \n" @@ -249,23 +249,23 @@ msgstr "" msgid "For more information on pricing, see `Odoo's pricing `_ page." msgstr "" -#: ../../content/applications/general/companies.rst:137 +#: ../../content/applications/general/companies.rst:139 msgid "Employee access" msgstr "" -#: ../../content/applications/general/companies.rst:139 +#: ../../content/applications/general/companies.rst:141 msgid "Once companies are created, manage the employees' :doc:`Access Rights ` for *Multi Companies*." msgstr "" -#: ../../content/applications/general/companies.rst:142 +#: ../../content/applications/general/companies.rst:144 msgid "To access the *Access Rights*, navigate to :menuselection:`Settings app --> Users section --> Manage Users`." msgstr "" -#: ../../content/applications/general/companies.rst:145 +#: ../../content/applications/general/companies.rst:147 msgid "From the :guilabel:`Users` page, select a user from the list to modify. Then, either change the fields for :guilabel:`Allowed Companies` or :guilabel:`Default Company`." msgstr "" -#: ../../content/applications/general/companies.rst:148 +#: ../../content/applications/general/companies.rst:150 msgid "Multiple companies can be set for :guilabel:`Allowed Companies`, and *only one* can be set as the :guilabel:`Default Company`." msgstr "" @@ -274,40 +274,40 @@ msgid "View of an user form emphasizing the multi companies field under the acce "in Odoo." msgstr "" -#: ../../content/applications/general/companies.rst:156 +#: ../../content/applications/general/companies.rst:158 msgid "If an administrator has multiple companies activated on the database, and is editing a record, the editing occurs on the record's related company." msgstr "" -#: ../../content/applications/general/companies.rst:160 +#: ../../content/applications/general/companies.rst:162 msgid "If editing a sale order issued under `JS Store US`, while working on the `JS Store Belgium` environment, the changes are applied under `JS Store US` (the company from which the sale order was issued)." msgstr "" -#: ../../content/applications/general/companies.rst:164 +#: ../../content/applications/general/companies.rst:166 msgid "When creating a record, the company taken into account is:" msgstr "" -#: ../../content/applications/general/companies.rst:166 +#: ../../content/applications/general/companies.rst:168 msgid "The current company selected in the company selector, in the upper-right hand of the screen (the one that is highlighted/active)" msgstr "" -#: ../../content/applications/general/companies.rst:169 -#: ../../content/applications/general/companies.rst:173 +#: ../../content/applications/general/companies.rst:171 +#: ../../content/applications/general/companies.rst:175 msgid "**OR**" msgstr "" -#: ../../content/applications/general/companies.rst:171 +#: ../../content/applications/general/companies.rst:173 msgid "No company is set (because none is set on the product and contact forms, for example)" msgstr "" -#: ../../content/applications/general/companies.rst:175 +#: ../../content/applications/general/companies.rst:177 msgid "The company set is the company linked to the document (the same as if a record is being edited)" msgstr "" -#: ../../content/applications/general/companies.rst:178 +#: ../../content/applications/general/companies.rst:180 msgid "Document format" msgstr "" -#: ../../content/applications/general/companies.rst:180 +#: ../../content/applications/general/companies.rst:182 msgid "To set document formats according to each company, *activate* and *select* the respective company, and, under the :menuselection:`Settings app --> Companies section`, click on :guilabel:`Configure Document Layout` and edit the information as needed." msgstr "" @@ -315,71 +315,72 @@ msgstr "" msgid "View of the settings page emphasizing the document layout field in Odoo." msgstr "" -#: ../../content/applications/general/companies.rst:188 +#: ../../content/applications/general/companies.rst:190 msgid ":guilabel:`Company Details` can be edited on the document layout. By default, this field is populated from the company information listed, when navigating here: :menuselection:`Settings app --> Companies section --> Manage Companies`, and select a company from the list." msgstr "" -#: ../../content/applications/general/companies.rst:193 +#: ../../content/applications/general/companies.rst:197 +#: ../../content/applications/general/multi_company.rst:77 msgid "Inter-company transactions" msgstr "" -#: ../../content/applications/general/companies.rst:195 +#: ../../content/applications/general/companies.rst:199 msgid "First, activate the :ref:`developer mode `. Then, make sure each one of the companies is properly set in relation to:" msgstr "" -#: ../../content/applications/general/companies.rst:198 +#: ../../content/applications/general/companies.rst:202 msgid ":doc:`Chart of Accounts <../finance/accounting/get_started/chart_of_accounts>`" msgstr "" -#: ../../content/applications/general/companies.rst:199 +#: ../../content/applications/general/companies.rst:203 msgid ":doc:`Taxes <../finance/accounting/taxes>`" msgstr "" -#: ../../content/applications/general/companies.rst:200 +#: ../../content/applications/general/companies.rst:204 msgid ":doc:`Fiscal Positions <../finance/accounting/taxes/fiscal_positions>`" msgstr "" -#: ../../content/applications/general/companies.rst:201 +#: ../../content/applications/general/companies.rst:205 msgid ":doc:`Journals <../finance/accounting/bank>`" msgstr "" -#: ../../content/applications/general/companies.rst:202 +#: ../../content/applications/general/companies.rst:206 msgid ":doc:`Fiscal Localizations <../finance/fiscal_localizations>`" msgstr "" -#: ../../content/applications/general/companies.rst:203 +#: ../../content/applications/general/companies.rst:207 msgid ":doc:`Pricelists <../sales/sales/products_prices/prices/pricing>`" msgstr "" -#: ../../content/applications/general/companies.rst:205 +#: ../../content/applications/general/companies.rst:209 msgid "Next, navigate to :menuselection:`Settings app --> Companies section --> Manage Companies`. Then, select the desired company from the list. On the company form, select the :guilabel:`Inter-Company Transactions` tab, on the individual company's detail form." msgstr "" -#: ../../content/applications/general/companies.rst:209 +#: ../../content/applications/general/companies.rst:213 msgid "With the respective company activated and selected, choose one of the following :guilabel:`Rule` options:" msgstr "" -#: ../../content/applications/general/companies.rst:212 +#: ../../content/applications/general/companies.rst:216 msgid ":guilabel:`Do not synchronize`: do not synchronize any inter-company transactions." msgstr "" -#: ../../content/applications/general/companies.rst:213 +#: ../../content/applications/general/companies.rst:217 msgid ":guilabel:`Synchronized invoice/bills`: generates a bill/invoice when a company confirms a bill/invoice for the selected company." msgstr "" -#: ../../content/applications/general/companies.rst:215 +#: ../../content/applications/general/companies.rst:219 msgid ":guilabel:`Synchronize Sales Order`: generates a drafted sales order using the selected company warehouse, when a sales order is confirmed for the selected company. If, instead of a drafted sales order, it should be validated, enable :guilabel:`Automatic Validation`.\\*" msgstr "" -#: ../../content/applications/general/companies.rst:218 +#: ../../content/applications/general/companies.rst:222 msgid ":guilabel:`Synchronize Purchase Order`: generates a drafted purchase order using the selected company warehouse, when a purchase order is confirmed for the selected company. If, instead of a drafted purchase order, it should be validated, enable :guilabel:`Automatic Validation`.\\*" msgstr "" -#: ../../content/applications/general/companies.rst:221 +#: ../../content/applications/general/companies.rst:225 msgid ":guilabel:`Synchronize Sales and Purchase Order`: generates a drafted purchase/sales order using the selected company warehouse, when a sales/purchase order is confirmed for the selected company. If, instead of a drafted purchase/sales order, it should be validated, enable :guilabel:`Automatic Validation`.\\*" msgstr "" -#: ../../content/applications/general/companies.rst:226 +#: ../../content/applications/general/companies.rst:230 msgid "\\* The given option needs to be selected, so :guilabel:`Automatic Validation` appears in the configuration." msgstr "" @@ -387,27 +388,27 @@ msgstr "" msgid "View of the settings page emphasizing the inter company transaction field in Odoo." msgstr "" -#: ../../content/applications/general/companies.rst:234 +#: ../../content/applications/general/companies.rst:238 msgid "Products **must** be configured as :guilabel:`Can be sold` and shared between the companies. See :doc:`../inventory_and_mrp/inventory/product_management/product_tracking/type`." msgstr "" -#: ../../content/applications/general/companies.rst:238 +#: ../../content/applications/general/companies.rst:242 msgid ":guilabel:`Synchronize invoice/bills`: an invoice posted on `JS Store Belgium`, for `JS Store US`, automatically creates a vendor bill, and generates a drafted purchase/sales order using the selected company warehouse, when a sales/purchase order is confirmed for the selected company. If, instead of a drafted purchase/sales order, it should be validated, enable :guilabel:`Automatic Validation`." msgstr "" -#: ../../content/applications/general/companies.rst:244 +#: ../../content/applications/general/companies.rst:248 msgid ":guilabel:`Synchronize sales/purchase order`: when a sale order for `JS Store US` is confirmed on `JS Store Belgium`, a purchase order on `JS Store Belgium` is automatically created (and confirmed, if the :guilabel:`Automatic Validation` feature was enabled)." msgstr "" -#: ../../content/applications/general/companies.rst:249 +#: ../../content/applications/general/companies.rst:253 msgid "Remember to test all workflows as a user *other* than the administrator." msgstr "" -#: ../../content/applications/general/companies.rst:252 +#: ../../content/applications/general/companies.rst:256 msgid ":doc:`Multi-company Guidelines <../../developer/howtos/company>`" msgstr "" -#: ../../content/applications/general/companies.rst:253 +#: ../../content/applications/general/companies.rst:257 msgid ":doc:`../finance/accounting/get_started/multi_currency`" msgstr "" @@ -3258,7 +3259,7 @@ msgid "Google Translate present in an Odoo database's chatter." msgstr "" #: ../../content/applications/general/integrations/google_translate.rst:123 -msgid ":ref:`language/change-user-language`" +msgid ":ref:`language/install`" msgstr "" #: ../../content/applications/general/integrations/mail_plugins.rst:5 @@ -4293,6 +4294,66 @@ msgstr "" msgid "Once set up is done, a new :abbr:`PoS (Point of Sale)` session can be launched." msgstr "" +#: ../../content/applications/general/iot/config/ssh_connect.rst:3 +msgid "Connect an IoT box via SSH" +msgstr "" + +#: ../../content/applications/general/iot/config/ssh_connect.rst:8 +msgid "To provide an |SSH| connection to an Internet of Things (IoT) box, a password needs to be generated." +msgstr "" + +#: ../../content/applications/general/iot/config/ssh_connect.rst:11 +msgid "This feature should **only** be utilized with trusted parties, as it provides administrative access to the |iot| box, which can create security issues." +msgstr "" + +#: ../../content/applications/general/iot/config/ssh_connect.rst:14 +msgid "Managing an |SSH| connection is **not** covered under the standard scope of Odoo support. Visit the `Odoo Support `_ page for additional information about what is covered." +msgstr "" + +#: ../../content/applications/general/iot/config/ssh_connect.rst:18 +msgid "First, navigate to the :menuselection:`IoT app --> IoT Boxes`. Click on the IP address of the appropriate |iot| box." +msgstr "" + +#: ../../content/applications/general/iot/config/ssh_connect.rst:22 +msgid "If the desired |iot| box does not appear, see :doc:`troubleshooting` for additional steps." +msgstr "" + +#: ../../content/applications/general/iot/config/ssh_connect.rst:24 +msgid "At the bottom of the |iot| box pop-up window, click :guilabel:`Remote Debug`. This opens the :guilabel:`Remote Debugging` pop-up window." +msgstr "" + +#: ../../content/applications/general/iot/config/ssh_connect.rst:-1 +msgid "The Remote Debugging password generation window." +msgstr "" + +#: ../../content/applications/general/iot/config/ssh_connect.rst:31 +msgid "Click :guilabel:`Generate password`." +msgstr "" + +#: ../../content/applications/general/iot/config/ssh_connect.rst:34 +msgid "After the password has been generated from the :guilabel:`Remote Debugging` pop-up window, the information **must** be recorded immediately. Once this window is closed, there is no current method for looking up this information." +msgstr "" + +#: ../../content/applications/general/iot/config/ssh_connect.rst:38 +msgid "Enter the :guilabel:`Authentication Token` provided by the user attempting to connect to the |iot| box." +msgstr "" + +#: ../../content/applications/general/iot/config/ssh_connect.rst:41 +msgid "Click :guilabel:`Enable Remote Debugging`." +msgstr "" + +#: ../../content/applications/general/iot/config/ssh_connect.rst:44 +msgid ":doc:`connect`" +msgstr "" + +#: ../../content/applications/general/iot/config/ssh_connect.rst:45 +msgid ":doc:`troubleshooting`" +msgstr "" + +#: ../../content/applications/general/iot/config/ssh_connect.rst:46 +msgid ":doc:`updating_iot`" +msgstr "" + #: ../../content/applications/general/iot/config/troubleshooting.rst:3 #: ../../content/applications/general/iot/config/windows_iot.rst:127 msgid "Troubleshooting" @@ -5755,7 +5816,7 @@ msgstr "" #: ../../content/applications/general/iot/devices/camera.rst:12 #: ../../content/applications/general/iot/devices/footswitch.rst:14 -#: ../../content/applications/general/iot/devices/printer.rst:11 +#: ../../content/applications/general/iot/devices/printer.rst:14 #: ../../content/applications/general/iot/devices/scale.rst:22 #: ../../content/applications/general/iot/devices/screen.rst:18 msgid "Connection" @@ -5806,12 +5867,10 @@ msgid "On a quality check form, the :guilabel:`Type` of check can also be specif msgstr "" #: ../../content/applications/general/iot/devices/camera.rst:58 -#: ../../content/applications/general/iot/devices/printer.rst:70 msgid ":doc:`/applications/inventory_and_mrp/quality/quality_management/quality_control_points`" msgstr "" #: ../../content/applications/general/iot/devices/camera.rst:59 -#: ../../content/applications/general/iot/devices/printer.rst:71 msgid ":doc:`/applications/inventory_and_mrp/quality/quality_management/quality_alerts`" msgstr "" @@ -5838,7 +5897,7 @@ msgstr "" #: ../../content/applications/general/iot/devices/camera.rst:82 #: ../../content/applications/general/iot/devices/footswitch.rst:52 #: ../../content/applications/general/iot/devices/measurement_tool.rst:92 -#: ../../content/applications/general/iot/devices/printer.rst:95 +#: ../../content/applications/general/iot/devices/printer.rst:98 msgid ":ref:`workcenter_iot`" msgstr "" @@ -5947,7 +6006,7 @@ msgid "Measurement tool input in the Odoo database." msgstr "" #: ../../content/applications/general/iot/devices/measurement_tool.rst:58 -#: ../../content/applications/general/iot/devices/printer.rst:60 +#: ../../content/applications/general/iot/devices/printer.rst:62 msgid "Quality control points can also be accessed by navigating to :menuselection:`IoT App --> Devices`, then select the device. There is a :guilabel:`Quality Control Points` tab, where they can be added with the device." msgstr "" @@ -5956,10 +6015,12 @@ msgid "On a quality check detail form, the :guilabel:`Type` of check can also be msgstr "" #: ../../content/applications/general/iot/devices/measurement_tool.rst:68 +#: ../../content/applications/general/iot/devices/printer.rst:73 msgid ":doc:`../../../inventory_and_mrp/quality/quality_management/quality_control_points`" msgstr "" #: ../../content/applications/general/iot/devices/measurement_tool.rst:69 +#: ../../content/applications/general/iot/devices/printer.rst:74 msgid ":doc:`../../../inventory_and_mrp/quality/quality_management/quality_alerts`" msgstr "" @@ -5987,43 +6048,43 @@ msgstr "" msgid "Connect a printer" msgstr "" -#: ../../content/applications/general/iot/devices/printer.rst:5 +#: ../../content/applications/general/iot/devices/printer.rst:8 msgid "Printer installation can be done in a few easy steps. The printer can be used to print receipts, labels, orders, or even reports from the different Odoo apps. In addition, printer actions can be assigned as an *action on a trigger* during the manufacturing process, or added onto a quality control point or a quality check." msgstr "" -#: ../../content/applications/general/iot/devices/printer.rst:13 -msgid "The :abbr:`IoT (Internet of Things)` box supports printers connected through :abbr:`USB (Universal Serial Bus)`, network connection, or Bluetooth. `Supported printers `__ are detected automatically, and appear in the :guilabel:`Devices` list of the *IoT app*." +#: ../../content/applications/general/iot/devices/printer.rst:16 +msgid "The |iot| box supports printers connected through |usb|, network connection, or Bluetooth. `Supported printers `__ are detected automatically, and appear in the :guilabel:`Devices` list of the *IoT* app." msgstr "" #: ../../content/applications/general/iot/devices/printer.rst:-1 msgid "The printer as it would appear in the IoT app devices list." msgstr "" -#: ../../content/applications/general/iot/devices/printer.rst:23 -msgid "The printer can take up to two minutes to appear in the *IoT app* devices list." +#: ../../content/applications/general/iot/devices/printer.rst:25 +msgid "Printers can take up to two minutes to appear in the *IoT* app :guilabel:`Devices` list." msgstr "" -#: ../../content/applications/general/iot/devices/printer.rst:26 +#: ../../content/applications/general/iot/devices/printer.rst:28 msgid "Link printer" msgstr "" -#: ../../content/applications/general/iot/devices/printer.rst:29 +#: ../../content/applications/general/iot/devices/printer.rst:31 msgid "Link printer to work orders" msgstr "" -#: ../../content/applications/general/iot/devices/printer.rst:31 +#: ../../content/applications/general/iot/devices/printer.rst:33 msgid "*Work Orders* can be linked to printers, via a quality control point, to print labels for manufactured products." msgstr "" -#: ../../content/applications/general/iot/devices/printer.rst:34 +#: ../../content/applications/general/iot/devices/printer.rst:36 msgid "In the *Quality app*, a device can be set up on a quality control point. To do that, go to the :menuselection:`Quality app --> Quality Control --> Control Points`, and open the desired control point to which the printer will be linked." msgstr "" -#: ../../content/applications/general/iot/devices/printer.rst:39 +#: ../../content/applications/general/iot/devices/printer.rst:41 msgid "A *Manufacturing Operation* and *Work Order Operation* need to be attached to a quality control point before the :guilabel:`Type` field allows for the :guilabel:`Print Label` option to be selected." msgstr "" -#: ../../content/applications/general/iot/devices/printer.rst:43 +#: ../../content/applications/general/iot/devices/printer.rst:45 msgid "From here, edit the control point, by selecting the :guilabel:`Type` field, and selecting :guilabel:`Print Label` from the drop-down menu of options. Doing so reveals a field called :guilabel:`Device`, where the attached *device* can be selected. :guilabel:`Save` the changes, if required." msgstr "" @@ -6031,62 +6092,82 @@ msgstr "" msgid "This is the quality control point setup." msgstr "" -#: ../../content/applications/general/iot/devices/printer.rst:52 +#: ../../content/applications/general/iot/devices/printer.rst:54 msgid "The printer can now be used with the selected quality control point. When the quality control point is reached during the manufacturing process, the database presents the option to print labels for a specific product." msgstr "" -#: ../../content/applications/general/iot/devices/printer.rst:65 -msgid "On a quality check detail form, the :guilabel:`Type` of check can also be specified to :guilabel:`Print Label`. To create new quality checks, navigate to :menuselection:`Quality app --> Quality Control --> Quality Checks --> New`." +#: ../../content/applications/general/iot/devices/printer.rst:67 +msgid "On a quality check detail form, the :guilabel:`Type` of check can also be specified to :guilabel:`Print Label`. To create :doc:`new quality checks <../../../inventory_and_mrp/quality/quality_management/quality_checks>`, navigate to :menuselection:`Quality app --> Quality Control --> Quality Checks --> New`." msgstr "" -#: ../../content/applications/general/iot/devices/printer.rst:74 -msgid "Link a printer to a work center in the Manufacturing app" +#: ../../content/applications/general/iot/devices/printer.rst:77 +msgid "Link a printer to a work center" msgstr "" -#: ../../content/applications/general/iot/devices/printer.rst:76 +#: ../../content/applications/general/iot/devices/printer.rst:79 msgid "To link a printer to an action, it first needs to be configured on a work center. To do that, navigate to :menuselection:`Manufacturing app --> Configuration --> Work Centers`. From here, select the desired work center in which the printer will be used. Next, add the device in the :guilabel:`IoT Triggers` tab, under the :guilabel:`Device` column, by selecting :guilabel:`Add a Line`." msgstr "" -#: ../../content/applications/general/iot/devices/printer.rst:82 +#: ../../content/applications/general/iot/devices/printer.rst:85 msgid "Then, the printer can be linked to either of the following options in the :guilabel:`Actions` drop-down menu: :guilabel:`Print Labels`, :guilabel:`Print Operation`, or :guilabel:`Print Delivery Slip`. A key can also be added to trigger the action." msgstr "" -#: ../../content/applications/general/iot/devices/printer.rst:87 +#: ../../content/applications/general/iot/devices/printer.rst:90 msgid "The first listed trigger on the form will be chosen first. So, the order matters, and these triggers can be dragged into any order." msgstr "" -#: ../../content/applications/general/iot/devices/printer.rst:91 +#: ../../content/applications/general/iot/devices/printer.rst:94 msgid "On the :guilabel:`Work Order` screen, a status graphic indicates whether the database is correctly connected to the printer." msgstr "" -#: ../../content/applications/general/iot/devices/printer.rst:98 +#: ../../content/applications/general/iot/devices/printer.rst:103 msgid "Link printer to reports" msgstr "" -#: ../../content/applications/general/iot/devices/printer.rst:100 -msgid "It's also possible to link a type of report to a certain printer. In the *IoT app*, go to the :guilabel:`Devices` menu, and select the desired printer that needs to be configured." +#: ../../content/applications/general/iot/devices/printer.rst:105 +msgid "It is possible to link report types to a specific printer. In the *IoT* app, go to the :guilabel:`Devices` menu, and select the desired printer to be configured." msgstr "" -#: ../../content/applications/general/iot/devices/printer.rst:103 -msgid "From here, click :guilabel:`Edit`, go to the :guilabel:`Printer Reports` tab, and select :guilabel:`Add a line`. In the window that appears, check all the types of :guilabel:`Reports` that should be linked to this printer." +#: ../../content/applications/general/iot/devices/printer.rst:108 +msgid "From here, go to the :guilabel:`Printer Reports` tab, and click :guilabel:`Add a line`. In the window that appears, check all the types of :guilabel:`Reports` that should be linked to this printer." msgstr "" #: ../../content/applications/general/iot/devices/printer.rst:-1 -msgid "The printer devices listed in the IoT Devices menu." +msgid "The list of reports assigned to a printer in the IoT app." msgstr "" -#: ../../content/applications/general/iot/devices/printer.rst:111 -msgid "Now, each time :guilabel:`Print` is selected in the control panel, instead of downloading a PDF, a pop-up appears which displays all the printer(s) linked to the report. Then Odoo sends the report to the selected printer(s), and automatically prints it." +#: ../../content/applications/general/iot/devices/printer.rst:117 +msgid "Reports can also be configured in the *Technical* menu of the *Settings* app, while in :ref:`debug mode `. To do that, navigate to :menuselection:`Settings App --> Technical --> Actions: Reports`. From here, select the desired report from the list. Then, an :guilabel:`IoT Device` can be set on the report." msgstr "" -#: ../../content/applications/general/iot/devices/printer.rst:116 +#: ../../content/applications/general/iot/devices/printer.rst:122 +msgid "The first time a linked report is selected to print, a :guilabel:`Select Printers` pop-up window appears. Tick the checkbox next to the correct printer for the report, and click :guilabel:`Print`. At that point, the report is linked to the printer." +msgstr "" + +#: ../../content/applications/general/iot/devices/printer.rst:127 +msgid "Clear device printer cache" +msgstr "" + +#: ../../content/applications/general/iot/devices/printer.rst:129 +msgid "After a printer is linked to print a report, the setting is saved in a browser's cache. This means a user can have different devices saved in their cache for different reports, based on the device they use to access Odoo. It also means different users can have a report automatically printed from different printers, based on their preferences." +msgstr "" + +#: ../../content/applications/general/iot/devices/printer.rst:134 +msgid "To unlink a report from a printer, navigate to :menuselection:`IoT app --> Clear Selected Devices`. This generates a list of reports that are linked to a printer on the current device. Click the :guilabel:`Unlink` button next to each report to remove the link." +msgstr "" + +#: ../../content/applications/general/iot/devices/printer.rst:139 +msgid "This step **only** prevents the report from automatically printing to the listed printer from the current browser. The report is still :ref:`linked ` on the device, under the :guilabel:`Printer Reports` tab." +msgstr "" + +#: ../../content/applications/general/iot/devices/printer.rst:-1 +msgid "A list of reports currently linked to a printer in the IoT app." +msgstr "" + +#: ../../content/applications/general/iot/devices/printer.rst:148 msgid ":doc:`POS Order Printing <../../../sales/point_of_sale/restaurant/kitchen_printing>`" msgstr "" -#: ../../content/applications/general/iot/devices/printer.rst:119 -msgid "Reports can also be configured in the :guilabel:`Technical Menu` while in :ref:`debug mode `. To do that, navigate to :menuselection:`Settings App --> Technical Menu --> Actions --> Reports`. From here, the individual report can be found in this list, where the :guilabel:`IoT Device` can be set on the report." -msgstr "" - #: ../../content/applications/general/iot/devices/scale.rst:3 msgid "Connect a scale" msgstr "" @@ -6281,6 +6362,134 @@ msgstr "" msgid "Open the screen form view by accessing :menuselection:`IoT app --> Devices --> Customer Display`. This allows the user to choose a particular website URL to display on the screen using the :guilabel:`Display URL` field." msgstr "" +#: ../../content/applications/general/multi_company.rst:3 +msgid "Multi-company" +msgstr "" + +#: ../../content/applications/general/multi_company.rst:7 +msgid "In Odoo, multiple companies can exist within a single database. This allows for some data to be shared among companies, while still maintaining some level of separation between entities." +msgstr "" + +#: ../../content/applications/general/multi_company.rst:10 +msgid "Before deciding to use the multi-company feature, there are several factors to consider." +msgstr "" + +#: ../../content/applications/general/multi_company.rst:13 +msgid "Multi-company is **only** available in *One App Free* databases, or with `Custom `_ plans." +msgstr "" + +#: ../../content/applications/general/multi_company.rst:17 +msgid "Accessing multiple companies" +msgstr "" + +#: ../../content/applications/general/multi_company.rst:19 +msgid "The list of :ref:`companies an employee has access to ` in a |mcd| can be found at the top-right of the main Odoo menu bar, where the active company is listed. Click on the company name to reveal a list of all allowed companies. To switch to a different company, click on the company name in the drop-down menu. To enable multiple companies at once, tick the checkbox next to each desired company name." +msgstr "" + +#: ../../content/applications/general/multi_company.rst:29 +msgid "An example of the list of companies a user has access to when logged into a database." +msgstr "" + +#: ../../content/applications/general/multi_company.rst:29 +msgid "An example of a user with access to multiple companies. The current company is My Company (San Francisco), while My Company (Chicago) is also active." +msgstr "" + +#: ../../content/applications/general/multi_company.rst:33 +msgid "The database may refresh after each checkbox is ticked." +msgstr "" + +#: ../../content/applications/general/multi_company.rst:38 +msgid "Multiple active companies" +msgstr "" + +#: ../../content/applications/general/multi_company.rst:40 +msgid "If more than one company is active at a time, one company is highlighted in purple, and is listed on the menu bar. This is the considered the *current* company." +msgstr "" + +#: ../../content/applications/general/multi_company.rst:43 +msgid "When creating a new record, the current company is added to the record in the *Company* field, except under the following circumstances:" +msgstr "" + +#: ../../content/applications/general/multi_company.rst:46 +msgid "The *Company* field for a new product, or a new contact, is left blank." +msgstr "" + +#: ../../content/applications/general/multi_company.rst:47 +msgid "If there is a related document already in the system, the *Company* field on the new record defaults to the same company." +msgstr "" + +#: ../../content/applications/general/multi_company.rst:51 +msgid "Mitchell Admin has multiple companies enabled, but the current company is `My Company (Chicago)`. When he creates a new product record, the :guilabel:`Company` field is left blank by default." +msgstr "" + +#: ../../content/applications/general/multi_company.rst:54 +msgid "When he creates a new sales team, the :guilabel:`Company` field automatically defaults to `My Company (Chicago)`." +msgstr "" + +#: ../../content/applications/general/multi_company.rst:58 +msgid "Sharing data" +msgstr "" + +#: ../../content/applications/general/multi_company.rst:60 +msgid "In a |mcd|, certain records are able to be utilized by all of the companies (or several, based on permissions)." +msgstr "" + +#: ../../content/applications/general/multi_company.rst:64 +msgid "Products" +msgstr "" + +#: ../../content/applications/general/multi_company.rst:66 +msgid "In an |mcd|, new products are created with the :ref:`Company field ` blank, by default. If the *Company* field remains blank, the product is shared across all companies." +msgstr "" + +#: ../../content/applications/general/multi_company.rst:70 +msgid "Contacts" +msgstr "" + +#: ../../content/applications/general/multi_company.rst:72 +msgid "Similar to products, contact records are shared across companies, by default. To limit access to a single company, click the :ref:`Company field ` on a contact form, and select a company to assign the contact to." +msgstr "" + +#: ../../content/applications/general/multi_company.rst:79 +msgid "The :ref:`Inter-Company Transactions ` feature allows for one company in the database to sell or purchase goods and services from another company within the same database. Counterpart documents for orders and invoices can be automatically generated and synchronized, depending on the configuration settings." +msgstr "" + +#: ../../content/applications/general/multi_company.rst:85 +msgid "To ensure inter-company transactions are handled appropriately, certain configurations, such as fiscal positions and localizations, need to be accurately assigned. See :ref:`Inter-Company Transactions ` for additional information." +msgstr "" + +#: ../../content/applications/general/multi_company.rst:90 +msgid "Use cases" +msgstr "" + +#: ../../content/applications/general/multi_company.rst:93 +msgid "Multinational companies" +msgstr "" + +#: ../../content/applications/general/multi_company.rst:95 +msgid "A multinational retail chain, which operates in the United States and Canada, needs to manage transactions in both USD and CAD currencies." +msgstr "" + +#: ../../content/applications/general/multi_company.rst:98 +msgid "Additionally, because both countries have different tax laws and regulations, it is in the best interest of the customer to utilize the multi-company feature." +msgstr "" + +#: ../../content/applications/general/multi_company.rst:101 +msgid "This allows for inter-company transactions they need to manage inventory moves across international borders, while making it simple to sell to customers in both countries in their own currency." +msgstr "" + +#: ../../content/applications/general/multi_company.rst:105 +msgid "Separate processes" +msgstr "" + +#: ../../content/applications/general/multi_company.rst:107 +msgid "A small furniture company is developing a new line of products that require a separate procurement, inventory, and manufacturing process. The new products are drastically different from the existing catalog. The company is considering utilizing the multi-company feature to treat this new line as a different entity." +msgstr "" + +#: ../../content/applications/general/multi_company.rst:112 +msgid "To keep their database from becoming overly complex, the furniture company does not need to add an entirely new company. Instead, they can take advantage of existing features, such as :doc:`analytic accounting <../finance/accounting/reporting/analytic_accounting>`, and multiple warehouses, to manage the new product line, without having to overly complicate transactions." +msgstr "" + #: ../../content/applications/general/users.rst:5 #: ../../content/applications/general/users/access_rights.rst:32 msgid "Users" @@ -6543,103 +6752,151 @@ msgid ":doc:`companies`" msgstr "" #: ../../content/applications/general/users/2fa.rst:3 -msgid "Two-factor Authentication" +msgid "Two-factor authentication" msgstr "" -#: ../../content/applications/general/users/2fa.rst:5 -msgid "Two-factor authentication (\"2FA\") is a good way to improve the security of an account, to make it less likely that an other person will manage to log in instead of you." +#: ../../content/applications/general/users/2fa.rst:8 +msgid "*Two-factor authentication (2FA)* is a way to improve security, and prevent unauthorized persons from accessing user accounts." msgstr "" -#: ../../content/applications/general/users/2fa.rst:9 -msgid "Practically, it means storing a secret inside an *authenticator* (usually your cell phone) and exchanging a code from the authenticator when you try to log in." +#: ../../content/applications/general/users/2fa.rst:11 +msgid "Practically, |2fa| means storing a secret inside an *authenticator*, usually on a mobile phone, and exchanging a code from the authenticator when trying to log in." msgstr "" -#: ../../content/applications/general/users/2fa.rst:13 -msgid "This means an attacker needs *both* to have guessed (or found) your password and to access (or steal) your authenticator, a more difficult proposition than either one or the other." +#: ../../content/applications/general/users/2fa.rst:14 +msgid "This means an unauthorized user would need to guess the account password *and* have access to the authenticator, which is a more difficult proposition." msgstr "" #: ../../content/applications/general/users/2fa.rst:18 msgid "Requirements" msgstr "" -#: ../../content/applications/general/users/2fa.rst:20 -msgid "These lists are just examples, they are not endorsements of any specific software." +#: ../../content/applications/general/users/2fa.rst:21 +msgid "These lists are just examples. They are **not** endorsements of any specific software." msgstr "" #: ../../content/applications/general/users/2fa.rst:23 -msgid "If you don't already have one, you will need to choose an authenticator." +msgid "Phone-based authenticators are the easiest and most commonly used. Examples include:" +msgstr "" + +#: ../../content/applications/general/users/2fa.rst:25 +msgid "`Authy `_" msgstr "" #: ../../content/applications/general/users/2fa.rst:26 -msgid "Phone-based authenticators are the easiest and most common so we will assume you'll pick and install one on your phone, examples include `Authy `_, `FreeOTP `_, `Google Authenticator `_, `LastPass Authenticator `_, `Microsoft Authenticator `_, ...; password managers also commonly include :abbr:`2FA (two-factor authentication)` support e.g. `1Password `_, `Bitwarden `_, ..." +msgid "`FreeOTP `_" msgstr "" -#: ../../content/applications/general/users/2fa.rst:39 -msgid "For the sake of demonstration we will be using Google Authenticator (not because it is any good but because it is quite common)." +#: ../../content/applications/general/users/2fa.rst:27 +msgid "`Google Authenticator `_" msgstr "" -#: ../../content/applications/general/users/2fa.rst:43 -msgid "Setting up two-factor authentication" +#: ../../content/applications/general/users/2fa.rst:28 +msgid "`LastPass Authenticator `_" msgstr "" -#: ../../content/applications/general/users/2fa.rst:45 -msgid "Once you have your authenticator of choice, go to the Odoo instance you want to setup :abbr:`2FA (two-factor authentication)`, then open :guilabel:`Preferences` (or :guilabel:`My Profile`):" +#: ../../content/applications/general/users/2fa.rst:29 +msgid "`Microsoft Authenticator `_" msgstr "" -#: ../../content/applications/general/users/2fa.rst:52 -msgid "Open the :guilabel:`Account Security` tab, then click the :guilabel:`Enable two-factor authentication` button:" +#: ../../content/applications/general/users/2fa.rst:32 +msgid "Password managers are another option. Common examples include:" msgstr "" -#: ../../content/applications/general/users/2fa.rst:58 -msgid "Because this is a security-sensitive action, you will need to input your password:" +#: ../../content/applications/general/users/2fa.rst:34 +msgid "`1Password `_" +msgstr "" + +#: ../../content/applications/general/users/2fa.rst:35 +msgid "`Bitwarden `_," +msgstr "" + +#: ../../content/applications/general/users/2fa.rst:38 +msgid "The remainder of this document uses Google Authenticator as an example, as it is one of the most commonly used. This is **not** an endorsement of the product." +msgstr "" + +#: ../../content/applications/general/users/2fa.rst:42 +msgid "Two-factor authentication setup" +msgstr "" + +#: ../../content/applications/general/users/2fa.rst:44 +msgid "After selecting an authenticator, log in to Odoo, then click the profile avatar in the upper-right corner, and select :guilabel:`My Profile` from the resulting drop-down menu." +msgstr "" + +#: ../../content/applications/general/users/2fa.rst:47 +msgid "Click the :guilabel:`Account Security` tab, then slide the :guilabel:`Two-Factor Authentication` toggle to *active*." +msgstr "" + +#: ../../content/applications/general/users/2fa.rst:53 +msgid "This generates a :guilabel:`Security Control` pop-up window that requires password confirmation to continue. Enter the appropriate password, then click :guilabel:`Confirm Password`. Next, a :guilabel:`Two-Factor Authentication Activation` pop-up window appears, with a |QR|." +msgstr "" + +#: ../../content/applications/general/users/2fa.rst:61 +msgid "Using the desired authenticator application, scan the |QR| when prompted." msgstr "" #: ../../content/applications/general/users/2fa.rst:64 -msgid "After which you will see this screen with a barcode:" +msgid "If scanning the screen is not possible (e.g. the setup is being completed on the *same* device as the authenticator application), clicking the provided :guilabel:`Cannot scan it?` link, or copying the secret to manually set up the authenticator, is an alternative." msgstr "" -#: ../../content/applications/general/users/2fa.rst:69 -msgid "In most applications, you can simply *scan the barcode* via the authenticator of your choice, the authenticator will then take care of all the setup:" +#: ../../content/applications/general/users/2fa.rst:74 +msgid "Afterwards, the authenticator should display a *verification code*." msgstr "" -#: ../../content/applications/general/users/2fa.rst:78 -msgid "If you can not scan the screen (e.g. because you are doing this set-up on the same phone as the authenticator application), you can click the provided link, or copy the secret to manually set-up your authenticator:" +#: ../../content/applications/general/users/2fa.rst:79 +msgid "Enter the code into the :guilabel:`Verification Code` field, then click :guilabel:`Activate`." msgstr "" -#: ../../content/applications/general/users/2fa.rst:89 -msgid "Once this is done, the authenticator should display a *verification code* with some useful identifying information (e.g. the domain and login for which the code is):" -msgstr "" - -#: ../../content/applications/general/users/2fa.rst:96 -msgid "You can now input the code into the :guilabel:`Verification Code` field, then click the :guilabel:`Enable two-factor authentication` button." -msgstr "" - -#: ../../content/applications/general/users/2fa.rst:100 -msgid "Congratulation, your account is now protected by two-factor authentication!" -msgstr "" - -#: ../../content/applications/general/users/2fa.rst:107 +#: ../../content/applications/general/users/2fa.rst:85 msgid "Logging in" msgstr "" -#: ../../content/applications/general/users/2fa.rst:109 -msgid "You should now :guilabel:`Log out` to follow along." +#: ../../content/applications/general/users/2fa.rst:87 +msgid "To confirm |2fa| setup is complete, log out of Odoo." msgstr "" -#: ../../content/applications/general/users/2fa.rst:111 -msgid "On the login page, input the username and password of the account for which you set up :abbr:`2FA (two-factor authentication)`, rather than immediately enter Odoo you will now get a second log-in screen:" +#: ../../content/applications/general/users/2fa.rst:89 +msgid "On the login page, input the username and password, then click :guilabel:`Log in`. On the :guilabel:`Two-factor Authentication` page, input the code provided by the chosen authenticator in the :guilabel:`Authentication Code` field, then click :guilabel:`Log in`." msgstr "" -#: ../../content/applications/general/users/2fa.rst:118 -msgid "Get your authenticator, input the code it provides for the domain and account, validate, and you're now in." +#: ../../content/applications/general/users/2fa.rst:-1 +msgid "The login page with 2fa enabled." msgstr "" -#: ../../content/applications/general/users/2fa.rst:121 -msgid "And that's it. From now on, unless you disable :abbr:`2FA (two-factor authentication)` you will have a two-step log-in process rather than the old one-step process." +#: ../../content/applications/general/users/2fa.rst:98 +msgid "If a user loses access to their authenticator, an administrator **must** deactivate |2fa| on the account before the user can log in." +msgstr "" + +#: ../../content/applications/general/users/2fa.rst:102 +msgid "Enforce two-factor authentication" +msgstr "" + +#: ../../content/applications/general/users/2fa.rst:104 +msgid "To enforce the use of |2fa| for all users, first navigate to :menuselection:`Main Odoo Dashboard --> Apps`. Remove the :guilabel:`Apps` filter from the :guilabel:`Search...` bar, then search for `2FA by mail`." +msgstr "" + +#: ../../content/applications/general/users/2fa.rst:108 +msgid "Click :guilabel:`Install` on the Kanban card for the :guilabel:`2FA by mail` module." +msgstr "" + +#: ../../content/applications/general/users/2fa.rst:-1 +msgid "The 2FA by mail module in the Apps directory." +msgstr "" + +#: ../../content/applications/general/users/2fa.rst:114 +msgid "After installation is complete, go to :guilabel:`Settings app: Permissions`. Tick the checkbox labeled, :guilabel:`Enforce two-factor authentication`. Then, use the radio buttons to choose whether to apply this setting to :guilabel:`Employees only`, or :guilabel:`All users`." +msgstr "" + +#: ../../content/applications/general/users/2fa.rst:119 +msgid "Selecting :guilabel:`All users` applies the setting to portal users, in addition to employees." +msgstr "" + +#: ../../content/applications/general/users/2fa.rst:-1 +msgid "The enforce two factor setting in the Settings application." msgstr "" #: ../../content/applications/general/users/2fa.rst:125 -msgid "Don't lose your authenticator, if you do, you will need an *Odoo Administrator* to disable :abbr:`2FA (two-factor authentication)` on the account." +msgid "Click :guilabel:`Save` to commit any unsaved changes." msgstr "" #: ../../content/applications/general/users/access_rights.rst:3 @@ -6983,6 +7240,7 @@ msgid "Application ID and OAuth 2.0 authorization endpoint (v2) credentials." msgstr "" #: ../../content/applications/general/users/azure.rst:114 +#: ../../content/applications/general/users/facebook.rst:111 msgid "Odoo setup" msgstr "" @@ -7054,6 +7312,166 @@ msgstr "" msgid "Accept Microsoft conditions for permission access to your account information." msgstr "" +#: ../../content/applications/general/users/facebook.rst:3 +msgid "Facebook sign-in authentication" +msgstr "" + +#: ../../content/applications/general/users/facebook.rst:5 +msgid "The *Facebook* OAuth sign-in function allows Odoo users to sign in to their database with their Facebook account." +msgstr "" + +#: ../../content/applications/general/users/facebook.rst:9 +msgid "Databases housed on Odoo.com should **not** use OAuth login for the owner or administrator of the database, as it would unlink the database from their Odoo.com account. If OAuth is setup for that user, the database can no longer be duplicated, renamed, or otherwise managed from the Odoo.com portal." +msgstr "" + +#: ../../content/applications/general/users/facebook.rst:15 +msgid "Meta for Developers setup" +msgstr "" + +#: ../../content/applications/general/users/facebook.rst:17 +msgid "Go to `Meta for Developers `_ and log in. Click :guilabel:`My Apps`. On the :guilabel:`Apps` page, click :guilabel:`Create App`." +msgstr "" + +#: ../../content/applications/general/users/facebook.rst:20 +msgid "On the :guilabel:`Use cases` page, select :guilabel:`Authenticate and request data from users with Facebook Login`, then click :guilabel:`Next`." +msgstr "" + +#: ../../content/applications/general/users/facebook.rst:23 +msgid "In the :guilabel:`Add an app name` field, enter `Odoo Login OAuth`, or a similar title." +msgstr "" + +#: ../../content/applications/general/users/facebook.rst:26 +msgid "The :guilabel:`App contact email` automatically defaults to the email address associated with the Meta account. If this email address is not regularly monitored, it may be wise to use another email address." +msgstr "" + +#: ../../content/applications/general/users/facebook.rst:30 +msgid "Click :guilabel:`Next`. Review the :guilabel:`Publishing requirements`, the :guilabel:`Meta Platform Terms`, and :guilabel:`Developer Policies`. Then, click :guilabel:`Create app`." +msgstr "" + +#: ../../content/applications/general/users/facebook.rst:34 +msgid "Clicking :guilabel:`Create app` may require password re-entry." +msgstr "" + +#: ../../content/applications/general/users/facebook.rst:37 +msgid "Customize app" +msgstr "" + +#: ../../content/applications/general/users/facebook.rst:39 +msgid "After the new app is created, the :guilabel:`Dashboard` page appears, with a list of steps to be completed before the app can be published. From here, click :guilabel:`Customize adding a Facebook Login button`." +msgstr "" + +#: ../../content/applications/general/users/facebook.rst:-1 +msgid "The App Dashboard in the Meta for developers platform." +msgstr "" + +#: ../../content/applications/general/users/facebook.rst:47 +msgid "On the :guilabel:`Customize` page, click :guilabel:`Settings`." +msgstr "" + +#: ../../content/applications/general/users/facebook.rst:49 +msgid "In the :guilabel:`Valid OAuth Redirect URIs` field, enter `https:///auth_oauth/signin`, replacing `` with the URL of the applicable database." +msgstr "" + +#: ../../content/applications/general/users/facebook.rst:53 +msgid "If a database has the URL `https://example.odoo.com`, the URL `https://example.odoo.com/auth_oauth/signin` would be entered in the :guilabel:`Valid OAuth Redirect URIs` field." +msgstr "" + +#: ../../content/applications/general/users/facebook.rst:57 +msgid "Click :guilabel:`Save changes` when finished." +msgstr "" + +#: ../../content/applications/general/users/facebook.rst:60 +msgid "Configure settings" +msgstr "" + +#: ../../content/applications/general/users/facebook.rst:62 +msgid "At the far left of the page, click :menuselection:`App settings --> Basic`. This page contains additional settings that are required before the app can be submitted for approval." +msgstr "" + +#: ../../content/applications/general/users/facebook.rst:65 +msgid "In the :guilabel:`Privacy Policy URL` field, enter `https://www.odoo.com/privacy`." +msgstr "" + +#: ../../content/applications/general/users/facebook.rst:68 +msgid "``_ is the default privacy policy for databases hosted on Odoo.com." +msgstr "" + +#: ../../content/applications/general/users/facebook.rst:70 +msgid "Click the :guilabel:`App Icon` field to open a file upload window. From here, select and upload an app icon." +msgstr "" + +#: ../../content/applications/general/users/facebook.rst:73 +msgid "In the :guilabel:`User data deletion` field, enter `https://www.odoo.com/documentation/17.0/administration/odoo_accounts.html`." +msgstr "" + +#: ../../content/applications/general/users/facebook.rst:77 +msgid "This document provides instructions on how a user can delete their Odoo account." +msgstr "" + +#: ../../content/applications/general/users/facebook.rst:79 +msgid "Lastly, click the :guilabel:`Category` field, and select :guilabel:`Business and pages` from the drop-down menu." +msgstr "" + +#: ../../content/applications/general/users/facebook.rst:82 +msgid "Click :guilabel:`Save changes`." +msgstr "" + +#: ../../content/applications/general/users/facebook.rst:-1 +msgid "An exampled of the Basic Settings page in the Meta for developers platform." +msgstr "" + +#: ../../content/applications/general/users/facebook.rst:91 +msgid "Capture app ID" +msgstr "" + +#: ../../content/applications/general/users/facebook.rst:93 +msgid "After the app is created, and approved, select and copy the :guilabel:`App ID`. Paste this information on a clipboard or notepad file, as it is needed in a later step to complete the setup." +msgstr "" + +#: ../../content/applications/general/users/facebook.rst:97 +msgid "Publish" +msgstr "" + +#: ../../content/applications/general/users/facebook.rst:99 +msgid "On the left side of the page, click :guilabel:`Publish`. Depending on the status of the connected Facebook account, additional verification and testing steps may be required, and are listed on this page." +msgstr "" + +#: ../../content/applications/general/users/facebook.rst:103 +msgid "After reviewing the information, click :guilabel:`Publish`." +msgstr "" + +#: ../../content/applications/general/users/facebook.rst:106 +msgid "Additional information regarding Meta App Development, including further details on building, testing, and use cases, can be found in the `Meta for developers documentation `_." +msgstr "" + +#: ../../content/applications/general/users/facebook.rst:113 +msgid "First, activate :ref:`Developer mode `." +msgstr "" + +#: ../../content/applications/general/users/facebook.rst:115 +msgid "Navigate to the :menuselection:`Settings app`, and scroll down to the :guilabel:`Integrations` section. There, tick the checkbox labeled, :guilabel:`OAuth Authentication`. Click :guilabel:`Save`." +msgstr "" + +#: ../../content/applications/general/users/facebook.rst:-1 +msgid "The enable OAuth setting in the Settings app." +msgstr "" + +#: ../../content/applications/general/users/facebook.rst:122 +msgid "Then, sign in to the database once the login screen loads." +msgstr "" + +#: ../../content/applications/general/users/facebook.rst:124 +msgid "After successfully logging in, navigate to :menuselection:`Settings app --> Users & Companies --> OAuth Providers`. Click :guilabel:`Facebook Graph`." +msgstr "" + +#: ../../content/applications/general/users/facebook.rst:127 +msgid "In the :guilabel:`Client ID` field, enter the :ref:`App ID ` from the previous section, then tick the :guilabel:`Allowed` checkbox." +msgstr "" + +#: ../../content/applications/general/users/facebook.rst:-1 +msgid "The Facebook Graph record in Odoo." +msgstr "" + #: ../../content/applications/general/users/google.rst:3 msgid "Google Sign-In Authentication" msgstr "" @@ -7223,59 +7641,64 @@ msgid "`Google Cloud Platform Console Help - Setting up OAuth 2.0 ` and :ref:`install ` additional languages to allow users to manage the database in another language or to :doc:`translate <../../websites/website/configuration/translate>` your website." msgstr "" -#: ../../content/applications/general/users/language.rst:9 -msgid "Load your desired language" +#: ../../content/applications/general/users/language.rst:13 +msgid "Add languages" msgstr "" -#: ../../content/applications/general/users/language.rst:11 -msgid "The first thing to do is to load your desired language on your Odoo instance." +#: ../../content/applications/general/users/language.rst:15 +msgid "To download additional languages:" msgstr "" -#: ../../content/applications/general/users/language.rst:14 -msgid "From the general dashboard click on the **Settings** app; on the top left of the page select :menuselection:`Translations --> Load a Translation`, select a language to install and click on **LOAD.**" +#: ../../content/applications/general/users/language.rst:17 +msgid "either click the profile icon in the upper-right corner, select :menuselection:`My profile`, and click the :icon:`fa-globe` (:guilabel:`globe`) icon next to the :guilabel:`Language` field;" msgstr "" -#: ../../content/applications/general/users/language.rst:23 -msgid "If you check the \"Websites to translate\" checkbox you will have the option to change the navigation language on your website." +#: ../../content/applications/general/users/language.rst:19 +msgid "or go to the **Settings** app, and click :guilabel:`Add Languages` in the :guilabel:`Languages` section." msgstr "" -#: ../../content/applications/general/users/language.rst:29 -msgid "Change your language" +#: ../../content/applications/general/users/language.rst:22 +msgid "You can then select the languages you want from the dropdown menu and click :guilabel:`Add`." msgstr "" -#: ../../content/applications/general/users/language.rst:31 -msgid "You can change the language to the installed language by going to the drop-down menu at the top right side of the screen, choose **Preferences**." +#: ../../content/applications/general/users/language.rst:25 +msgid ":doc:`Translations <../../websites/website/configuration/translate>`" msgstr "" -#: ../../content/applications/general/users/language.rst:38 -msgid "Then change the Language setting to your installed language and click **SAVE.**" +#: ../../content/applications/general/users/language.rst:32 +msgid "To select their preferred language, users can click the profile icon in the upper-right corner, go to :menuselection:`My profile`, and select a :guilabel:`Language` in the dropdown list." msgstr "" -#: ../../content/applications/general/users/language.rst:44 -msgid "Open a new menu to view the changes." -msgstr "" - -#: ../../content/applications/general/users/language.rst:47 +#: ../../content/applications/general/users/language.rst:36 msgid "Change another user's language" msgstr "" +#: ../../content/applications/general/users/language.rst:38 +msgid "To change the database language for a user:" +msgstr "" + +#: ../../content/applications/general/users/language.rst:40 +msgid "Go to the :guilabel:`Settings` app and click :guilabel:`Manage Users` in the :guilabel:`Users` section." +msgstr "" + +#: ../../content/applications/general/users/language.rst:43 +msgid "Click on the user whose language you want to change." +msgstr "" + +#: ../../content/applications/general/users/language.rst:45 +msgid "Go to the :guilabel:`Preferences` tab and select a previously :ref:`installed language ` from the :guilabel:`Language` dropdown menu." +msgstr "" + #: ../../content/applications/general/users/language.rst:49 -msgid "Odoo also gives you the possibility for each user to choose his preferred language." -msgstr "" - -#: ../../content/applications/general/users/language.rst:52 -msgid "To change the language for a different user, choose :menuselection:`Users --> Users` from the Settings app. Here you have a list of all users and you can choose the user who you'd like to change the language for. Select the user and click on **Edit** in the top left corner. Under Preferences you can change the Language to any previously installed language and click **SAVE.**" -msgstr "" - -#: ../../content/applications/general/users/language.rst:63 -msgid ":doc:`../../websites/website/configuration/translate`" +msgid "Emails and documents will be sent to the user in the selected language." msgstr "" #: ../../content/applications/general/users/ldap.rst:3 diff --git a/locale/sources/hr.pot b/locale/sources/hr.pot index 4ff4fcef1..9aca3d2d7 100644 --- a/locale/sources/hr.pot +++ b/locale/sources/hr.pot @@ -8,7 +8,7 @@ msgid "" msgstr "" "Project-Id-Version: Odoo 17.0\n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2024-06-24 07:08+0000\n" +"POT-Creation-Date: 2024-07-23 13:30+0000\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME \n" "Language-Team: LANGUAGE \n" @@ -22,7 +22,6 @@ msgstr "" #: ../../content/applications/hr/appraisals.rst:5 #: ../../content/applications/hr/appraisals.rst:52 -#: ../../content/applications/hr/appraisals.rst:174 msgid "Appraisals" msgstr "" @@ -40,6 +39,7 @@ msgstr "" #: ../../content/applications/hr/appraisals.rst:20 #: ../../content/applications/hr/attendances.rst:59 +#: ../../content/applications/hr/attendances/kiosks.rst:22 #: ../../content/applications/hr/frontdesk.rst:15 #: ../../content/applications/hr/time_off.rst:31 msgid "Configuration" @@ -50,7 +50,7 @@ msgid "The :guilabel:`Configuration` menu in the *Appraisals* application is whe msgstr "" #: ../../content/applications/hr/appraisals.rst:27 -#: ../../content/applications/hr/fleet.rst:14 +#: ../../content/applications/hr/fleet.rst:13 #: ../../content/applications/hr/lunch.rst:15 #: ../../content/applications/hr/payroll.rst:15 #: ../../content/applications/hr/recruitment.rst:35 @@ -234,345 +234,15 @@ msgstr "" msgid "In previous versions of Odoo, this section was referred to as :guilabel:`Surveys`." msgstr "" -#: ../../content/applications/hr/appraisals.rst:176 -msgid "Navigate to the main *Appraisals* dashboard by opening the :guilabel:`Appraisals` application. The :guilabel:`Appraisals` dashboard is the default view." +#: ../../content/applications/hr/appraisals.rst:174 +msgid ":doc:`appraisals/new_appraisals`" msgstr "" -#: ../../content/applications/hr/appraisals.rst:179 -msgid "To view the dashboard at any point in the application, navigate to :menuselection:`Appraisals application --> Appraisals`." -msgstr "" - -#: ../../content/applications/hr/appraisals.rst:182 -msgid "All appraisals are displayed on the dashboard in a Kanban view, by default, with a list of groupings on the left side of the dashboard, including :guilabel:`Company`, :guilabel:`Department`, and :guilabel:`Status`." -msgstr "" - -#: ../../content/applications/hr/appraisals.rst:186 -msgid "Click any grouping option to view appraisals for **only** the chosen selection." -msgstr "" - -#: ../../content/applications/hr/appraisals.rst:189 -msgid "Only groupings with multiple selections appear in the list. For example, if a database only has one company, the :guilabel:`Company` grouping does **not** appear, since there is no other company to select." -msgstr "" - -#: ../../content/applications/hr/appraisals.rst:193 -msgid "Each appraisal card displays the following information:" -msgstr "" - -#: ../../content/applications/hr/appraisals.rst:195 -msgid ":guilabel:`Name`: the employee's name." -msgstr "" - -#: ../../content/applications/hr/appraisals.rst:196 -msgid ":guilabel:`Department`: the department the employee is associated with." -msgstr "" - -#: ../../content/applications/hr/appraisals.rst:197 -msgid ":guilabel:`Company`: the company the employee works for. This only appears in a multi-company database." -msgstr "" - -#: ../../content/applications/hr/appraisals.rst:199 -msgid ":guilabel:`Date`: the date the appraisal was requested, or is scheduled for in the future." -msgstr "" - -#: ../../content/applications/hr/appraisals.rst:200 -msgid ":guilabel:`Activities`: any activities that are scheduled for the appraisal, such as :guilabel:`Meetings` or :guilabel:`Phone Calls.` If no activities are scheduled, an activity can be scheduled from the :guilabel:`🕘 (clock)` icon, located in the bottom-left corner of an appraisal card." -msgstr "" - -#: ../../content/applications/hr/appraisals.rst:204 -msgid ":guilabel:`Manager`: the employee's manager, indicated by the profile icon in the bottom-right corner of an appraisal card." -msgstr "" - -#: ../../content/applications/hr/appraisals.rst:206 -msgid ":guilabel:`Status banner`: the status of the appraisal. A banner appears if an appraisal is marked as either :guilabel:`Canceled` or :guilabel:`Done`. If no banner is present, that means the appraisal has not happened, or has not been scheduled yet." -msgstr "" - -#: ../../content/applications/hr/appraisals.rst:210 -msgid "To view the details of any appraisal, click on the card to open the appraisal form." -msgstr "" - -#: ../../content/applications/hr/appraisals.rst:-1 -msgid "The Appraisals dashboard with each appraisal in its own box." -msgstr "" - -#: ../../content/applications/hr/appraisals.rst:217 -msgid "New appraisal" -msgstr "" - -#: ../../content/applications/hr/appraisals.rst:219 -msgid "To create a new appraisal, click the :guilabel:`New` button at the top of the :guilabel:`Appraisals` dashboard to load a blank appraisal form. Then, enter the following information on the form:" -msgstr "" - -#: ../../content/applications/hr/appraisals.rst:222 -msgid ":guilabel:`Name`: enter the employee's name." -msgstr "" - -#: ../../content/applications/hr/appraisals.rst:223 -msgid ":guilabel:`Manager`: select the employee's manager from the drop-down menu. The manager is responsible for completing the :guilabel:`Manager's Feedback` section of the appraisal. This field auto-populates after the employee is selected, if they have a manager set on their employee profile." -msgstr "" - -#: ../../content/applications/hr/appraisals.rst:227 -msgid ":guilabel:`Appraisal Date`: the current date is automatically entered in this field. This field is automatically updated once the appraisal is completed or canceled, with the corresponding date of completion or cancellation." -msgstr "" - -#: ../../content/applications/hr/appraisals.rst:230 -msgid ":guilabel:`Department`: select the employee's department from the drop-down menu. This field auto-populates after the employee is selected, if they have a department set on their employee profile." -msgstr "" - -#: ../../content/applications/hr/appraisals.rst:233 -msgid ":guilabel:`Company`: select the employee's company from the drop-down menu. This field auto-populates after the employee is selected, if they have a company set on their employee profile." -msgstr "" - -#: ../../content/applications/hr/appraisals.rst:238 -msgid "The only required fields for the appraisal form are the employee's :guilabel:`Name`, the :guilabel:`Manager`, and the :guilabel:`Company`." -msgstr "" - -#: ../../content/applications/hr/appraisals.rst:241 -msgid "Once the form is complete, click the :guilabel:`Confirm` button to confirm the appraisal request." -msgstr "" - -#: ../../content/applications/hr/appraisals.rst:243 -msgid "Once confirmed, the employee receives an email stating that an appraisal was requested, and is then prompted to schedule an appraisal date." -msgstr "" - -#: ../../content/applications/hr/appraisals.rst:246 -msgid "The status changes to :guilabel:`Confirmed`, and the :guilabel:`Employee's Feedback` section of the :guilabel:`Appraisal` tab is grayed out. The information in that section only appears after the self-assessment is published by the employee. The :guilabel:`Final Rating` field also appears once the appraisal request is confirmed." -msgstr "" - -#: ../../content/applications/hr/appraisals.rst:251 -msgid "If there are any existing appraisals for the employee, an :guilabel:`Appraisal` smart button appears at the top of the page, listing the total number of appraisals there are for the employee." -msgstr "" - -#: ../../content/applications/hr/appraisals.rst:255 -msgid "Ask for feedback" -msgstr "" - -#: ../../content/applications/hr/appraisals.rst:257 -msgid "As part of the appraisal process, the manager can request feedback on an employee from anyone in the company. Feedback is usually requested from co-workers and other people who interact with, or work with, the employee. This is to get a more well-rounded view of the employee, and aid in the manager's overall assessment." -msgstr "" - -#: ../../content/applications/hr/appraisals.rst:262 -msgid "To request feedback, the appraisal **must** be confirmed. Once confirmed, an :guilabel:`Ask Feedback` button appears at the top of the form." -msgstr "" - -#: ../../content/applications/hr/appraisals.rst:265 -msgid "When the :guilabel:`Ask Feedback` button is clicked, an :guilabel:`Ask Feedback` email pop-up form appears, using the :guilabel:`Appraisal: Ask Feedback` email template, which sends the :guilabel:`360 Feedback` survey." -msgstr "" - -#: ../../content/applications/hr/appraisals.rst:269 -msgid "Enter the employees being asked to complete the survey in the :guilabel:`Recipients` field. Multiple employees may be selected." -msgstr "" - -#: ../../content/applications/hr/appraisals.rst:272 -msgid "The email template has dynamic placeholders to personalize the message. Add any additional text to the email, if desired." -msgstr "" - -#: ../../content/applications/hr/appraisals.rst:275 -msgid "If required, an :guilabel:`Answer Deadline` can be added, as well." -msgstr "" - -#: ../../content/applications/hr/appraisals.rst:277 -msgid "If any attachments are needed, click the :guilabel:`Attachments` button, and a file explorer window appears. Navigate to the file(s), select them, then click :guilabel:`Open`." -msgstr "" - -#: ../../content/applications/hr/appraisals.rst:280 -msgid "When the email is ready to send, click :guilabel:`Send.`" -msgstr "" - -#: ../../content/applications/hr/appraisals.rst:-1 -msgid "The email pop-up when requesting feedback from other employees." -msgstr "" - -#: ../../content/applications/hr/appraisals.rst:287 -msgid "Appraisal form" -msgstr "" - -#: ../../content/applications/hr/appraisals.rst:289 -msgid "Once an appraisal is confirmed, the next steps are for the employee to fill out the self-assessment, after which the manager completes their assessment." -msgstr "" - -#: ../../content/applications/hr/appraisals.rst:295 -msgid "Employee's feedback" -msgstr "" - -#: ../../content/applications/hr/appraisals.rst:297 -msgid "To complete their portion of feedback, employees should navigate to the main :menuselection:`Appraisals application` dashboard, where the only entries visible are appraisals for the employee, themselves, and/or anyone they manage and have to provide manager feedback for." -msgstr "" - -#: ../../content/applications/hr/appraisals.rst:301 -msgid "Click on the appraisal to open the appraisal form. Enter responses in the :guilabel:`Employee's Feedback` section, under the :guilabel:`Appraisal` tab." -msgstr "" - -#: ../../content/applications/hr/appraisals.rst:304 -msgid "When completed, click the :guilabel:`Not Visible to Manager` toggle (the default setting once an appraisal is confirmed). When clicked, the toggle changes to :guilabel:`Visible to Manager`." -msgstr "" - -#: ../../content/applications/hr/appraisals.rst:-1 -msgid "The feedback section for the employee with the toggle button highlighted." -msgstr "" - -#: ../../content/applications/hr/appraisals.rst:314 -msgid "Manager's feedback" -msgstr "" - -#: ../../content/applications/hr/appraisals.rst:316 -msgid "After the employee has completed the :guilabel:`Employee's Feedback` section, under the :guilabel:`Appraisal` tab, it is time for the manager to fill out the :guilabel:`Manager's Feedback` section." -msgstr "" - -#: ../../content/applications/hr/appraisals.rst:320 -msgid "The manager enters their responses in the fields in the :ref:`same manner as the employee `." -msgstr "" - -#: ../../content/applications/hr/appraisals.rst:323 -msgid "When the feedback section is completed, click the :guilabel:`Not Visible to Employee` toggle (the default setting once an appraisal is confirmed). When clicked, the toggle changes to :guilabel:`Visible to Employee`." -msgstr "" - -#: ../../content/applications/hr/appraisals.rst:-1 -msgid "The feedback section for both employees and managers. The toggle buttons are highlighted." -msgstr "" - -#: ../../content/applications/hr/appraisals.rst:332 -#: ../../content/applications/hr/recruitment/add-new-applicants.rst:167 -msgid "Skills tab" -msgstr "" - -#: ../../content/applications/hr/appraisals.rst:334 -msgid "Part of an appraisal is evaluating an employee's skills, and tracking their progress over time. The :guilabel:`Skills` tab of the appraisal form auto-populates with the skills from the :doc:`employee form <../hr/employees/new_employee>`, once an appraisal is confirmed." -msgstr "" - -#: ../../content/applications/hr/appraisals.rst:338 -msgid "Each skill is grouped with like skills, and the :guilabel:`Skill Level`, :guilabel:`Progress`, and :guilabel:`Justification` are displayed for each skill." -msgstr "" - -#: ../../content/applications/hr/appraisals.rst:341 -msgid "Update any skills, or add any new skills to the :guilabel:`Skills` tab." -msgstr "" - -#: ../../content/applications/hr/appraisals.rst:343 -msgid "If a skill level has increased, a reason for the improved rating can be entered into the :guilabel:`Justification` field, such as `took a fluency language test` or `received Javascript certification`." -msgstr "" - -#: ../../content/applications/hr/appraisals.rst:347 -msgid "Refer to the :ref:`Create a new employee ` document for detailed instructions on adding or updating a skill." -msgstr "" - -#: ../../content/applications/hr/appraisals.rst:350 -msgid "After an appraisal is completed, and the skills have been updated, the next time an appraisal is confirmed, the updated skills populate the :guilabel:`Skills` tab." -msgstr "" - -#: ../../content/applications/hr/appraisals.rst:-1 -msgid "The skills tab of an appraisal form, all filled out." -msgstr "" - -#: ../../content/applications/hr/appraisals.rst:358 -msgid "Private note tab" -msgstr "" - -#: ../../content/applications/hr/appraisals.rst:360 -msgid "If managers want to leave notes that are only visible to other managers, they can be entered in the :guilabel:`Private Note` tab. The employee being evaluated does **not** have access to this tab, and the tab does **not** appear on their appraisal." -msgstr "" - -#: ../../content/applications/hr/appraisals.rst:365 -#: ../../content/applications/hr/recruitment.rst:533 -msgid "Schedule a meeting" -msgstr "" - -#: ../../content/applications/hr/appraisals.rst:367 -msgid "Once both portions of an appraisal are completed (the :ref:`employee ` and :ref:`manager ` feedback sections), it is time for the employee and manager to meet and discuss the appraisal." -msgstr "" - -#: ../../content/applications/hr/appraisals.rst:371 -msgid "A meeting can be scheduled in one of two ways: either from the *Appraisals* application dashboard, or from an individual appraisal card." -msgstr "" - -#: ../../content/applications/hr/appraisals.rst:374 -msgid "To schedule an appraisal from the dashboard of the *Appraisals* application, first navigate to :menuselection:`Appraisals application --> Appraisals`." -msgstr "" - -#: ../../content/applications/hr/appraisals.rst:377 -msgid "Click the :guilabel:`🕘 (clock)` icon, beneath the appraisal date on the desired appraisal card, and a :guilabel:`Schedule Activity` pop-up window appears. Then, click :guilabel:`+ Schedule an activity` to create a blank activity form." -msgstr "" - -#: ../../content/applications/hr/appraisals.rst:381 -msgid "Select :guilabel:`Meeting` for the :guilabel:`Activity Type` from the drop-down menu. Doing so causes the form to change, so only the :guilabel:`Activity Type` and :guilabel:`Summary` fields appear." -msgstr "" - -#: ../../content/applications/hr/appraisals.rst:385 -msgid "If scheduling an activity other than a meeting, such as a :guilabel:`Call` or a :guilabel:`To-Do`, the fields that appear on the :guilabel:`Schedule Activity` pop-up form change, accordingly." -msgstr "" - -#: ../../content/applications/hr/appraisals.rst:389 -msgid "The :guilabel:`🕘 (clock)` icon may appear as a number of different icons, depending on what, if any, scheduled activities are in place, and the color represents their corresponding due dates." -msgstr "" - -#: ../../content/applications/hr/appraisals.rst:392 -msgid "If no activities are scheduled, that is represented by a gray :guilabel:`🕘 (clock)` icon." -msgstr "" - -#: ../../content/applications/hr/appraisals.rst:394 -msgid "However, if a specific activity is scheduled, the icon may appear as a :guilabel:`📞 (phone)` icon for a phone call, a :guilabel:`👥 (group of people)` icon for a meeting, and so on." -msgstr "" - -#: ../../content/applications/hr/appraisals.rst:397 -msgid "The color of the icon indicates the status; a green icon means an activity is scheduled in the future, and a red icon means the activity is past due." -msgstr "" - -#: ../../content/applications/hr/appraisals.rst:400 -msgid "For more details on activities, refer to the :doc:`../essentials/activities` document." -msgstr "" - -#: ../../content/applications/hr/appraisals.rst:0 -msgid "The appraisal cards with the various activity icons highlighted." -msgstr "" - -#: ../../content/applications/hr/appraisals.rst:406 -msgid "Enter a brief description in the :guilabel:`Summary` field of the :guilabel:`Schedule Activity` pop-up window, such as `Annual Appraisal for (Employee)`." -msgstr "" - -#: ../../content/applications/hr/appraisals.rst:409 -msgid "Next, click the :guilabel:`Open Calendar` button. From the calendar page that appears, navigate to, and double-click on, the desired date and time for the meeting." -msgstr "" - -#: ../../content/applications/hr/appraisals.rst:412 -msgid "Doing so opens a :guilabel:`New Event` pop-up form. From this pop-up form, make any desired modifications, such as designating a :guilabel:`Start` time, or giving a :guilabel:`Name` to the meeting." -msgstr "" - -#: ../../content/applications/hr/appraisals.rst:416 -msgid "Add the appraisee in the :guilabel:`Attendees` section, and include anyone else who should be in the meeting, if necessary." -msgstr "" - -#: ../../content/applications/hr/appraisals.rst:419 -msgid "To make the meeting a video call, instead of an in-person meeting, click :guilabel:`+ Odoo meeting`, and a :guilabel:`Videocall URL` link appears in the field." -msgstr "" - -#: ../../content/applications/hr/appraisals.rst:422 -msgid "Once all the desired changes are complete, click :guilabel:`Save & Close`." -msgstr "" - -#: ../../content/applications/hr/appraisals.rst:424 -msgid "The meeting now appears on the calendar, and the invited parties are informed, via email." -msgstr "" - -#: ../../content/applications/hr/appraisals.rst:-1 -msgid "The meeting form with all information entered for Ronnie Hart's annual appraisal." -msgstr "" - -#: ../../content/applications/hr/appraisals.rst:430 -msgid "The other way to schedule a meeting is from the individual appraisal form. To do this, navigate to the :menuselection:`Appraisal application` dashboard, then click on an appraisal card." -msgstr "" - -#: ../../content/applications/hr/appraisals.rst:433 -msgid "Next, click on the :guilabel:`Meeting` smart button, and the calendar loads. Follow the same directions above to create the meeting." -msgstr "" - -#: ../../content/applications/hr/appraisals.rst:437 -msgid "If no meetings are scheduled, the :guilabel:`Meeting` smart button reads :guilabel:`No Meeting`." -msgstr "" - -#: ../../content/applications/hr/appraisals.rst:440 +#: ../../content/applications/hr/appraisals.rst:175 msgid ":doc:`appraisals/goals`" msgstr "" -#: ../../content/applications/hr/appraisals.rst:441 +#: ../../content/applications/hr/appraisals.rst:176 msgid ":doc:`appraisals/reporting`" msgstr "" @@ -688,12 +358,365 @@ msgstr "" msgid "To mark a goal as `Done` from the goal card itself, click on a goal card to open that goal's form. Then, click the :guilabel:`Mark as Done` button in the top-left of the form. When clicked, a green :guilabel:`Done` banner appears in the top-right corner of the goal form." msgstr "" +#: ../../content/applications/hr/appraisals/new_appraisals.rst:3 +msgid "New appraisals" +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:5 +msgid "To create a new appraisal for an employee, first navigate to the main *Appraisals* dashboard by opening the :menuselection:`Appraisals` app. The :guilabel:`Appraisals` dashboard is the default view." +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:10 +msgid "Appraisals dashboard" +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:12 +msgid "All appraisals are displayed on the dashboard in a default Kanban view, with a list of groupings on the left side of the dashboard, including :guilabel:`COMPANY`, :guilabel:`DEPARTMENT`, and :guilabel:`STATUS`." +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:16 +msgid "Click any grouping option to view appraisals for **only** the chosen selection." +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:19 +msgid "Only groupings with multiple selections appear in the list. For example, if a database only has one company, the :guilabel:`COMPANY` grouping does **not** appear, since there is no other company to select." +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:23 +msgid "Each appraisal card displays the following information:" +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:25 +msgid "**Name**: the employee's name." +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:26 +msgid "**Department**: the department the employee is associated with." +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:27 +msgid "**Company**: the company the employee works for. This only appears in a multi-company database." +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:29 +msgid "**Date**: the date the appraisal was requested, or is scheduled for in the future." +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:30 +msgid "**Activities**: any :doc:`activities <../../essentials/activities>` that are scheduled for the appraisal, such as *Meetings* or *Phone Calls*." +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:32 +msgid "**Manager**: the employee's manager, indicated by the profile icon in the bottom-right corner of an appraisal card." +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:34 +msgid "**Status banner**: the status of the appraisal. A banner appears if an appraisal is marked as either *Canceled* or *Done*. If no banner is present, that means the appraisal has not happened, or has not been scheduled yet." +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:38 +msgid "To view the details of any appraisal, click on the card to open the appraisal form." +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:-1 +msgid "The Appraisals dashboard with each appraisal in its own box." +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:45 +msgid "Create an appraisal" +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:47 +msgid "To create a new appraisal, click the :guilabel:`New` button in the upper-left corner of the :guilabel:`Appraisals` dashboard. Doing so reveals a blank appraisal form. After entering a name in the first blank field, proceed to enter the following information on the form:" +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:51 +msgid ":guilabel:`Manager`: select the employee's manager from the drop-down menu. The manager is responsible for completing the *Manager's Feedback* section of the appraisal. This field auto-populates after the employee is selected, if they have a manager set on their employee profile." +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:55 +msgid ":guilabel:`Appraisal Date`: the current date is automatically entered in this field. This field is automatically updated once the appraisal is completed or cancelled, with the corresponding date of completion or cancellation." +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:58 +msgid ":guilabel:`Department`: select the employee's department from the drop-down menu. This field auto-populates after the employee is selected, if they have a department set on their employee profile." +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:61 +msgid ":guilabel:`Company`: select the employee's company from the drop-down menu. This field auto-populates after the employee is selected, if they have a company set on their employee profile." +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:66 +msgid "The only required fields for the appraisal form are the employee's name, the :guilabel:`Manager`, and the :guilabel:`Company`." +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:69 +msgid "Once the form is complete, click the :guilabel:`Confirm` button to confirm the appraisal request." +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:71 +msgid "Once confirmed, the employee receives an email stating that an appraisal was requested, and is then prompted to schedule an appraisal date." +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:74 +msgid "The status changes to :guilabel:`Confirmed`, and the :guilabel:`Employee's Feedback` section of the :guilabel:`Appraisal` tab is grayed out. The information in that section only appears after the self-assessment is published by the employee. The :guilabel:`Final Rating` field also appears once the appraisal request is confirmed." +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:79 +msgid "If there are any existing appraisals for the employee, an :guilabel:`Appraisal` smart button appears at the top of the page, listing the total number of appraisals there are for the employee." +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:83 +msgid "Ask for feedback" +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:85 +msgid "As part of the appraisal process, the manager can request feedback on an employee from anyone in the company. Feedback is usually requested from co-workers and other people who interact with, or work with, the employee. This is to get a more well-rounded view of the employee, and aid in the manager's overall assessment." +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:90 +msgid "To request feedback, the appraisal **must** be confirmed. Once confirmed, an :guilabel:`Ask Feedback` button appears at the top of the form." +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:93 +msgid "When the :guilabel:`Ask Feedback` button is clicked, an :guilabel:`Ask Feedback` email pop-up form appears, using the :guilabel:`Appraisal: Ask Feedback` email template, which sends the :guilabel:`360 Feedback` survey." +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:97 +msgid "Enter the employees being asked to complete the survey in the :guilabel:`Recipients` field. Multiple employees may be selected." +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:100 +msgid "The email template has dynamic placeholders to personalize the message. Add any additional text to the email, if desired." +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:103 +msgid "If required, an :guilabel:`Answer Deadline` can be added, as well." +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:105 +msgid "If any attachments are needed, click the :icon:`fa-paperclip` :guilabel:`Attachments` button, and a file explorer window appears. Navigate to the file(s), select them, then click :guilabel:`Open`." +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:108 +msgid "When the email is ready to send, click :guilabel:`Send.`" +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:-1 +msgid "The email pop-up when requesting feedback from other employees." +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:115 +msgid "Appraisal form" +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:117 +msgid "Once an appraisal is confirmed, the next steps require the employee to fill out the self-assessment, after which the manager completes their assessment." +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:123 +msgid "Employee's feedback" +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:125 +msgid "To complete their portion of feedback, employees should navigate to the main :menuselection:`Appraisals application` dashboard, where the only entries visible are appraisals for the employee, themselves, and/or anyone they manage and have to provide manager feedback for." +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:129 +msgid "Click on the appraisal to open the appraisal form. Enter responses in the :guilabel:`Employee's Feedback` section, under the :guilabel:`Appraisal` tab." +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:132 +msgid "When completed, click the :guilabel:`Not Visible to Manager` toggle (the default setting once an appraisal is confirmed). When clicked, the toggle changes to :guilabel:`Visible to Manager`." +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:-1 +msgid "The feedback section for the employee with the toggle button highlighted." +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:142 +msgid "Manager's feedback" +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:144 +msgid "After the employee has completed the :guilabel:`Employee's Feedback` section, under the :guilabel:`Appraisal` tab, it is time for the manager to fill out the :guilabel:`Manager's Feedback` section." +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:148 +msgid "The manager enters their responses in the fields in the :ref:`same manner as the employee `." +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:151 +msgid "When the feedback section is completed, click the :guilabel:`Not Visible to Employee` toggle (the default setting once an appraisal is confirmed). When clicked, the toggle changes to :guilabel:`Visible to Employee`." +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:-1 +msgid "The feedback section for both employees and managers. The toggle buttons are highlighted." +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:160 +#: ../../content/applications/hr/recruitment/add-new-applicants.rst:167 +msgid "Skills tab" +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:162 +msgid "Part of an appraisal is evaluating an employee's skills, and tracking their progress over time. The :guilabel:`Skills` tab of the appraisal form auto-populates with the skills from the :ref:`employee form `, once an appraisal is confirmed." +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:166 +msgid "Each skill is grouped with like skills, and the :guilabel:`Skill Level`, :guilabel:`Progress`, and :guilabel:`Justification` are displayed for each skill." +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:169 +msgid "Update any skills, or add any new skills to the :guilabel:`Skills` tab." +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:171 +msgid "If a skill level has increased, a reason for the improved rating can be entered into the :guilabel:`Justification` field, such as `took a fluency language test` or `received Javascript certification`." +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:176 +msgid "Refer to the :ref:`Create a new employee ` document for detailed instructions on adding or updating a skill." +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:179 +msgid "After an appraisal is completed, and the skills have been updated, the next time an appraisal is confirmed, the updated skills populate the :guilabel:`Skills` tab." +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:-1 +msgid "The skills tab of an appraisal form, all filled out." +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:187 +msgid "The :guilabel:`Skills` tab can be modified **after** the employee and their manager have met and discussed the employee's appraisal." +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:190 +msgid "This is a common situation as the manager may not have all the necessary information to properly assess and update the employee's skills before meeting." +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:194 +msgid "Private Note tab" +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:196 +msgid "If managers want to leave notes that are only visible to other managers, they can be entered in the :guilabel:`Private Note` tab. This can be done before or after meeting with the employee to discuss the appraisal." +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:200 +msgid "The employee being evaluated does **not** have access to this tab, and the tab does **not** appear on their appraisal." +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:204 +msgid "Schedule a meeting" +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:206 +msgid "Once both portions of an appraisal are completed (the :ref:`employee ` and :ref:`manager ` feedback sections), it is time for the employee and manager to meet and discuss the appraisal." +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:210 +msgid "A meeting can be scheduled in one of two ways: either from the *Appraisals* application dashboard, or from an individual appraisal card." +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:213 +msgid "To schedule an appraisal from the dashboard of the *Appraisals* application, first navigate to :menuselection:`Appraisals app --> Appraisals`." +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:216 +msgid "Click the :icon:`fa-clock-o` :guilabel:`(clock)` icon, beneath the appraisal date on the desired appraisal card, and a pop-up window appears. Then, click :icon:`fa-plus` :guilabel:`Schedule an activity` to create an activity from a :guilabel:`Schedule Activity` pop-up form that appears." +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:220 +msgid "Select :guilabel:`Meeting` for the :guilabel:`Activity Type` from the drop-down menu. Doing so causes the form to change, so only the :guilabel:`Activity Type` and :guilabel:`Summary` fields appear." +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:224 +msgid "Enter a brief description in the :guilabel:`Summary` field of the :guilabel:`Schedule Activity` pop-up form, such as `Annual Appraisal for (Employee)`." +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:227 +msgid "Next, click the :guilabel:`Open Calendar` button. From the calendar page that appears, navigate to, and double-click on, the desired date and time for the meeting." +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:230 +msgid "Doing so opens a :guilabel:`New Event` pop-up form. From this pop-up form, make any desired modifications, such as designating a :guilabel:`Start` time, or modifying the default :guilabel:`Title` to the meeting." +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:234 +msgid "Add the appraisee in the :guilabel:`Attendees` section, and include anyone else who should also be in the meeting, if necessary." +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:237 +msgid "To make the meeting a video call, instead of an in-person meeting, click :icon:`fa-plus` :guilabel:`Odoo meeting`, and a :guilabel:`Videocall URL` link appears in the field." +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:240 +msgid "Once all the desired changes are complete, click :guilabel:`Save & Close`." +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:242 +msgid "The meeting now appears on the calendar, and the invited parties are informed, via email." +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:-1 +msgid "The meeting form with all information entered for Ronnie Hart's annual appraisal." +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:248 +msgid "The other way to schedule a meeting is from the individual appraisal form. To do this, navigate to the :menuselection:`Appraisal app` dashboard, then click on an appraisal card." +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:251 +msgid "Next, click on the :icon:`fa-calendar` :guilabel:`Meeting` smart button, and the calendar loads. Follow the same directions above to create the meeting." +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:254 +msgid "For more detailed information on how to schedule activities, refer to the :doc:`activities <../../essentials/activities>` documentation." +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:258 +msgid "If no meetings are scheduled, the :guilabel:`Meeting` smart button reads :guilabel:`No Meeting`." +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:261 +msgid "Complete an appraisal" +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:263 +msgid "After the appraisal is complete, and both the manager and employee have met to discuss the appraisal, the appraisal can be marked as *Done*. When completed, click the :guilabel:`Mark as Done` button on the appraisal form, located in the top-left corner." +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:267 +msgid "Once the appraisal is marked as *Done*, the :guilabel:`Mark as Done` button disappears, and a :guilabel:`Reopen` button appears." +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:271 +msgid "Modifications are **not** possible once the appraisal is marked as done." +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:273 +msgid "To make any changes to an appraisal that is marked as *Done*, click the :guilabel:`Reopen` button." +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:276 +msgid "Then, click the :guilabel:`Confirm` button that appears, and make any modifications needed. Once all modifications are complete, click the the :guilabel:`Mark as Done` button again." +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:280 +msgid ":doc:`../appraisals/goals`" +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:281 +msgid ":doc:`../appraisals/reporting`" +msgstr "" + #: ../../content/applications/hr/appraisals/reporting.rst:3 -#: ../../content/applications/hr/attendances.rst:433 +#: ../../content/applications/hr/attendances.rst:279 #: ../../content/applications/hr/frontdesk.rst:210 #: ../../content/applications/hr/payroll/reporting.rst:3 -#: ../../content/applications/hr/referrals.rst:329 -#: ../../content/applications/hr/time_off.rst:595 +#: ../../content/applications/hr/referrals.rst:261 +#: ../../content/applications/hr/time_off.rst:477 msgid "Reporting" msgstr "" @@ -911,228 +934,76 @@ msgstr "" msgid "Modes" msgstr "" -#: ../../content/applications/hr/attendances.rst:71 -msgid ":guilabel:`Kiosk Mode`: using the drop-down menu, select how an employee checks in when using a kiosk. Options are :guilabel:`Barcode/RFID`, :guilabel:`Barcode/RFID and Manual Selection`, or :guilabel:`Manual Selection`." -msgstr "" - -#: ../../content/applications/hr/attendances.rst:76 -msgid "The *Barcode* application **does not** need to be installed to use one of the Barcode/RFID settings." -msgstr "" - -#: ../../content/applications/hr/attendances.rst:79 +#: ../../content/applications/hr/attendances.rst:69 msgid ":guilabel:`Attendances from Backend`: activate this selection to allow users to check in and out directly from the Odoo database. If this is not activated, users must use a kiosk to check in and out of work." msgstr "" -#: ../../content/applications/hr/attendances.rst:86 -msgid "Kiosk settings" -msgstr "" - -#: ../../content/applications/hr/attendances.rst:88 -msgid "This section only needs to be configured if employees use kiosks for checking in and out. If kiosks are **not** being used, modifying any of these fields does **not** adversely affect the *Attendances* application." -msgstr "" - -#: ../../content/applications/hr/attendances.rst:92 -msgid ":guilabel:`Barcode Source`: this setting appears **only** if either of the two Barcode/RFID selections were configured for the :ref:`Kiosk Mode ` setting. Select how barcodes are scanned at the kiosk, either with a dedicated barcode :guilabel:`Scanner`, or the device's :guilabel:`Front Camera`, or :guilabel:`Back Camera`." -msgstr "" - -#: ../../content/applications/hr/attendances.rst:96 -msgid ":guilabel:`Employee PIN Identification`: activate this option if employees should use a unique PIN to check in. PINs are configured on each individual employee record. Refer to the :doc:`../hr/employees/new_employee` documentation for more information on setting up PINs." -msgstr "" - -#: ../../content/applications/hr/attendances.rst:99 -msgid ":guilabel:`Display Time`: set the duration (in seconds) the check in and check out confirmation screen remains on the kiosk before going back to the main check in screen." -msgstr "" - -#: ../../content/applications/hr/attendances.rst:101 -msgid ":guilabel:`Attendance Kiosk Url`: Odoo generates a unique web address (URL) to use a device as a kiosk without having to sign in to the Odoo database. When setting up a kiosk device, navigate to this unique web address in a web browser to present the Attendances application kiosk." -msgstr "" - -#: ../../content/applications/hr/attendances.rst:106 -msgid "These kiosk URLs are **not** secured with any type of access code. Anyone who has the URL can access the Attendances application kiosk. If the URL is compromised for any reason, such as in the event of a security breach, click :guilabel:`Generate a new Kiosk Mode URL`, located beneath the link, to generate a new URL and update the kiosk accordingly." -msgstr "" - -#: ../../content/applications/hr/attendances.rst:112 +#: ../../content/applications/hr/attendances.rst:74 msgid "Extra hours" msgstr "" -#: ../../content/applications/hr/attendances.rst:114 +#: ../../content/applications/hr/attendances.rst:76 msgid "This section specifies how extra time is calculated, including when extra time is counted and what time is not logged." msgstr "" -#: ../../content/applications/hr/attendances.rst:117 +#: ../../content/applications/hr/attendances.rst:79 msgid ":guilabel:`Count of Extra Hours`: enable this box to allow employees to log extra hours beyond their set working hours (sometimes referred to as *overtime*). Activating this selection displays the following settings as well. If this is not activated, no other configurations appear." msgstr "" -#: ../../content/applications/hr/attendances.rst:121 +#: ../../content/applications/hr/attendances.rst:83 msgid ":guilabel:`Start From`: the current date is automatically entered in this field. If desired, click on this field and use the calendar selector to modify the start date on which extra hours are logged." msgstr "" -#: ../../content/applications/hr/attendances.rst:124 +#: ../../content/applications/hr/attendances.rst:86 msgid ":guilabel:`Tolerance Time In Favor Of Company`: enter the amount of time, in minutes, that is **not** counted towards an employee's overtime. When an employee checks out, and the extra time logged is below the specified minutes, the extra time is **not** counted as overtime for the employee." msgstr "" -#: ../../content/applications/hr/attendances.rst:128 +#: ../../content/applications/hr/attendances.rst:90 msgid ":guilabel:`Tolerance Time In Favor Of Employee`: enter the amount of time, in minutes, that an employee is given, that does **not** adversely affect their attendance if they log less time than their working hours. When an employee checks out, and the total time logged for the day is less than their specified working hours and less than this specified grace period, they are **not** penalized for their reduced hours." msgstr "" -#: ../../content/applications/hr/attendances.rst:135 +#: ../../content/applications/hr/attendances.rst:97 msgid "A company sets both of the :guilabel:`Tolerance` fields to `15` minutes, and the working hours for the entire company are set from 9:00 AM to 5:00 PM." msgstr "" -#: ../../content/applications/hr/attendances.rst:138 +#: ../../content/applications/hr/attendances.rst:100 msgid "If an employee checks in at 9:00 AM, and checks out at 5:14 PM, the extra 14 minutes are **not** counted towards their overtime." msgstr "" -#: ../../content/applications/hr/attendances.rst:141 +#: ../../content/applications/hr/attendances.rst:103 msgid "If an employee checks in at 9:05 AM, and checks out at 4:55 PM, even though they logged a total of 10 minutes less than their full working hours, they are **not** penalized for this discrepancy." msgstr "" -#: ../../content/applications/hr/attendances.rst:145 +#: ../../content/applications/hr/attendances.rst:107 msgid ":guilabel:`Display Extra Hours`: activate this box to display the extra hours logged by an employee when they check out with a kiosk, or when a user checks out in the database." msgstr "" -#: ../../content/applications/hr/attendances.rst:149 +#: ../../content/applications/hr/attendances.rst:111 msgid "Employees are still able to log overtime hours even if the :guilabel:`Count of Extra Hours` option is not activated. The difference is that when :guilabel:`Count of Extra Hours` is activated, the extra hours can be :ref:`deducted from an approved time off request `." msgstr "" -#: ../../content/applications/hr/attendances.rst:157 -msgid "Kiosk mode" -msgstr "" - -#: ../../content/applications/hr/attendances.rst:159 -msgid "Some companies may opt to use a dedicated device (a laptop or desktop PC, a tablet, or a mobile phone) for employees to check in and check out from. Kiosk mode is used for these scenarios." -msgstr "" - -#: ../../content/applications/hr/attendances.rst:163 -msgid "If users check in and out using either a badge or an RFID, then an accessible device in kiosk mode **must** be available to check in and check out using these two methods." -msgstr "" - -#: ../../content/applications/hr/attendances.rst:166 -msgid "Entering kiosk mode is only available for users with specific :ref:`access rights `." -msgstr "" - -#: ../../content/applications/hr/attendances.rst:169 -msgid "Kiosk mode can be activated in three different ways:" -msgstr "" - -#: ../../content/applications/hr/attendances.rst:171 -msgid "Navigate to the :guilabel:`Attendances` application, and click :guilabel:`Kiosk Mode` in the top menu. The device then enters kiosk mode." -msgstr "" - -#: ../../content/applications/hr/attendances.rst:173 -msgid "Navigate to the :menuselection:`Attendances application --> Configuration`. In the :guilabel:`Kiosk Settings` section, click on the link in the :guilabel:`Attendance Kiosk Url` field. A new tab opens in kiosk mode. It is recommended to close the database tab to keep the database secure." -msgstr "" - -#: ../../content/applications/hr/attendances.rst:177 -msgid "Navigate to the :menuselection:`Attendances application --> Configuration`. In the :guilabel:`Kiosk Settings` section, click :guilabel:`Copy` next to the link beneath the :guilabel:`Attendance Kiosk Url` field. Paste this URL into a web browser on the kiosk device and navigate to it." -msgstr "" - -#: ../../content/applications/hr/attendances.rst:-1 -msgid "The Attendances Kiosk URL field in the settings section of the Attendances application." -msgstr "" - -#: ../../content/applications/hr/attendances.rst:186 -msgid "As a security measure, once a device is in kiosk mode, it is not possible to exit kiosk mode and go back into the database without signing back in. To exit kiosk mode, click the back button in the web browser. This logs the user out of the database, and returns to the main log in screen. This adds an extra layer of security, preventing anyone from accessing the database." -msgstr "" - -#: ../../content/applications/hr/attendances.rst:192 -msgid "Badge" -msgstr "" - -#: ../../content/applications/hr/attendances.rst:194 -msgid "To check in or out using a badge, tap the :guilabel:`📷 (camera) Tap to scan` image in the center of the kiosk. Then, scan the barcode on the badge using the method configured in the :ref:`kiosk settings ` section of the configuration menu. Options are a dedicated barcode scanning device, or the kiosk's front or back camera. Once the barcode is scanned, the employee is checked in or out, and a :ref:`confirmation message ` appears with all the check in or check out information." -msgstr "" - -#: ../../content/applications/hr/attendances.rst:-1 -msgid "The Attendances Kiosk view displaying the scan badge image." -msgstr "" - -#: ../../content/applications/hr/attendances.rst:206 -msgid "RFID" -msgstr "" - -#: ../../content/applications/hr/attendances.rst:208 -msgid "To check in or out using an RFID key fob, simply scan the fob with an RFID reader. Once scanned, the employee is then either checked in or checked out, and a :ref:`confirmation message ` appears with all the check in or check out information." -msgstr "" - -#: ../../content/applications/hr/attendances.rst:213 -msgid "Manually" -msgstr "" - -#: ../../content/applications/hr/attendances.rst:215 -msgid "Users who do not have a scannable badge or an RFID fob can manually check in and out at a kiosk. Tap the :guilabel:`Identify Manually` button on the kiosk, and a screen with all the employees that can be checked in or out appears. This is the same view as in the *Employees* application dashboard. Tap on the person, and they are either checked in or checked out, and a :ref:`confirmation message ` appears." -msgstr "" - -#: ../../content/applications/hr/attendances.rst:221 -msgid "When a large number of employees appear in the list, making scrolling inefficient, there are two ways to quickly find a specific person:" -msgstr "" - -#: ../../content/applications/hr/attendances.rst:224 -msgid ":guilabel:`Search...`: tap on the :guilabel:`Search...` field and enter the person's name. As the name is typed in, the matching results are displayed on the screen." -msgstr "" - -#: ../../content/applications/hr/attendances.rst:226 -msgid ":guilabel:`Department`: to quickly filter the presented employees, tap on a department to display only those employees that are part of that department. The :guilabel:`Departments` are listed on the left side of the screen, and the number at the end of each department indicates how many employees are part of the department, and is displayed when selected." -msgstr "" - -#: ../../content/applications/hr/attendances.rst:232 -msgid "PIN" -msgstr "" - -#: ../../content/applications/hr/attendances.rst:234 -msgid "If the :guilabel:`Employee PIN Identification` option was activated in the :ref:`kiosk settings ` section of the configuration menu, the employee is prompted to enter a PIN when manually checking in or out." -msgstr "" - -#: ../../content/applications/hr/attendances.rst:238 -msgid "After the employee is selected, a number pad appears with a message. When checking in, :guilabel:`(Employee) Welcome! Please enter your PIN to check in` appears above the numbers. When checking out, :guilabel:`(Employee) Want to check out? Please enter your PIN to check out` appears above the numbers." -msgstr "" - -#: ../../content/applications/hr/attendances.rst:243 -msgid "Tap in the PIN using the number pad, then tap :guilabel:`OK` when done. The employee is then checked in or out, and a :ref:`confirmation message ` appears." -msgstr "" - -#: ../../content/applications/hr/attendances.rst:-1 -msgid "The pop-up that appears when prompted to enter a pin." -msgstr "" - -#: ../../content/applications/hr/attendances.rst:253 -msgid "Confirmation message" -msgstr "" - -#: ../../content/applications/hr/attendances.rst:255 -msgid "When an employee checks in or out, a confirmation message appears with all the check in or check out information. When checking in, a welcome message appears, as well as the date and time of check in. An :guilabel:`Hours Previously Today: HH:MM` field also appears, displaying any time already logged for that employee for the day. If no time has already been logged, the value displayed is `00:00`. Beneath the message is an :guilabel:`OK` button. To exit the screen before the preset time in the kiosk, tap the :guilabel:`OK` button." -msgstr "" - -#: ../../content/applications/hr/attendances.rst:262 -msgid "When checking out, the screen displays a goodbye message, with the date and time of check out, and the total hours logged for the day. Beneath the message is a :guilabel:`Goodbye` button. To exit the screen before the preset time, tap the :guilabel:`Goodbye` button." -msgstr "" - -#: ../../content/applications/hr/attendances.rst:-1 -msgid "The goodbye message with all the employee's check out information." -msgstr "" - -#: ../../content/applications/hr/attendances.rst:271 -#: ../../content/applications/hr/time_off.rst:551 +#: ../../content/applications/hr/attendances.rst:117 +#: ../../content/applications/hr/time_off.rst:433 msgid "Overview" msgstr "" -#: ../../content/applications/hr/attendances.rst:273 +#: ../../content/applications/hr/attendances.rst:119 msgid "When entering the *Attendances* application, the :guilabel:`Overview` dashboard is presented, containing all the check in and check out information for the signed in user. If the user has specific :ref:`access rights ` and/or are :ref:`approvers ` for specific employees, then those additional employee's check in and check out information is also visible on the :guilabel:`Overview` dashboard." msgstr "" -#: ../../content/applications/hr/attendances.rst:280 +#: ../../content/applications/hr/attendances.rst:126 msgid "Views" msgstr "" -#: ../../content/applications/hr/attendances.rst:282 +#: ../../content/applications/hr/attendances.rst:128 msgid "To change the view from the default Gantt chart to a list view, click the :guilabel:`List` icon in the top right of the dashboard, beneath the user's photo. To switch back to the Gantt chart, click the :guilabel:`Gantt` button, located next to the :guilabel:`List` button." msgstr "" -#: ../../content/applications/hr/attendances.rst:286 +#: ../../content/applications/hr/attendances.rst:132 msgid "The default view presents the current day's information. To present the information for the :guilabel:`Week`, :guilabel:`Month`, or :guilabel:`Year`, click on the :guilabel:`Day` button to reveal a drop-down, displaying those other options. Select the desired view, and the dashboard updates, presenting the selected information. To change the :guilabel:`Day`, :guilabel:`Week`, :guilabel:`Month`, or :guilabel:`Year` presented, click the :guilabel:`← (left arrow)` or :guilabel:`→ (right arrow)` buttons on either side of the drop-down menu. To jump back to a view containing the current day, click the :guilabel:`Today` button. This refreshes the dashboard, presenting information containing the current day's information." msgstr "" -#: ../../content/applications/hr/attendances.rst:295 +#: ../../content/applications/hr/attendances.rst:141 msgid "In the :guilabel:`Day` view, the column for the current hour is highlighted in yellow. If the :guilabel:`Week` or :guilabel:`Month` view is selected, the column for the current day is highlighted. If the :guilabel:`Year` view is selected, the current month is highlighted." msgstr "" @@ -1141,148 +1012,148 @@ msgid "The overview dashboard presenting the information for the week, with the "highlighted." msgstr "" -#: ../../content/applications/hr/attendances.rst:304 +#: ../../content/applications/hr/attendances.rst:150 msgid "Any entries that have errors appear in red, indicating they need to be resolved by a user with the proper :ref:`access rights ` and/or are :ref:`approvers ` for the employee(s) with the errors." msgstr "" -#: ../../content/applications/hr/attendances.rst:311 +#: ../../content/applications/hr/attendances.rst:157 msgid "Filters and groups" msgstr "" -#: ../../content/applications/hr/attendances.rst:313 +#: ../../content/applications/hr/attendances.rst:159 msgid "To filter the results in the overview dashboard, or to present different groups of information, click the :guilabel:`🔻 (triangle drop down)` button in the right side of the :guilabel:`Search` bar above the dashboard, and select one of the available :guilabel:`Filters` or :guilabel:`Group By` options. There are several pre-configured filters and groups to choose from, as well as an option to create custom ones." msgstr "" -#: ../../content/applications/hr/attendances.rst:320 +#: ../../content/applications/hr/attendances.rst:166 #: ../../content/applications/hr/payroll/reporting.rst:276 msgid "Filters" msgstr "" -#: ../../content/applications/hr/attendances.rst:322 +#: ../../content/applications/hr/attendances.rst:168 msgid "The default filters that can be selected are:" msgstr "" -#: ../../content/applications/hr/attendances.rst:324 +#: ../../content/applications/hr/attendances.rst:170 msgid ":guilabel:`My Attendances`: this filter only presents the user's attendance data." msgstr "" -#: ../../content/applications/hr/attendances.rst:325 +#: ../../content/applications/hr/attendances.rst:171 msgid ":guilabel:`My Team`: this filter presents the attendance data for the user's team." msgstr "" -#: ../../content/applications/hr/attendances.rst:326 +#: ../../content/applications/hr/attendances.rst:172 msgid ":guilabel:`At Work`: this filter displays the attendance data for everyone currently checked in." msgstr "" -#: ../../content/applications/hr/attendances.rst:327 +#: ../../content/applications/hr/attendances.rst:173 msgid ":guilabel:`Errors`: this filter displays any entries with :ref:`errors ` that need to be resolved." msgstr "" -#: ../../content/applications/hr/attendances.rst:329 +#: ../../content/applications/hr/attendances.rst:175 msgid ":guilabel:`Check In`: this filter has a drop-down to further select a specific time period. Select the desired time period from the options presented, a specific month, quarter, or year." msgstr "" -#: ../../content/applications/hr/attendances.rst:331 +#: ../../content/applications/hr/attendances.rst:177 msgid ":guilabel:`Last 7 days`: this filter presents the attendance data for the last seven days." msgstr "" -#: ../../content/applications/hr/attendances.rst:332 +#: ../../content/applications/hr/attendances.rst:178 msgid ":guilabel:`Add Custom Filter`: create a custom filter using the pop-up that appears when this is selected." msgstr "" -#: ../../content/applications/hr/attendances.rst:336 +#: ../../content/applications/hr/attendances.rst:182 msgid "Groups" msgstr "" -#: ../../content/applications/hr/attendances.rst:338 +#: ../../content/applications/hr/attendances.rst:184 msgid "The default groups that can be selected are:" msgstr "" -#: ../../content/applications/hr/attendances.rst:340 +#: ../../content/applications/hr/attendances.rst:186 msgid ":guilabel:`Check In`: this grouping presents a drop-down menu containing the following time period options: :guilabel:`Year`, :guilabel:`Quarter`, :guilabel:`Month`, :guilabel:`Week`, and :guilabel:`Day`. Selected the time period to display all the check-in information, grouped by the selected time period." msgstr "" -#: ../../content/applications/hr/attendances.rst:344 +#: ../../content/applications/hr/attendances.rst:190 msgid ":guilabel:`Employee`: this group presents the attendance data organized by employee." msgstr "" -#: ../../content/applications/hr/attendances.rst:345 +#: ../../content/applications/hr/attendances.rst:191 msgid ":guilabel:`Check Out`: this grouping presents a drop-down menu containing the following time period options: :guilabel:`Year`, :guilabel:`Quarter`, :guilabel:`Month`, :guilabel:`Week`, and :guilabel:`Day`. Selected the time period to display all the check-out information, grouped by the selected time period." msgstr "" -#: ../../content/applications/hr/attendances.rst:349 +#: ../../content/applications/hr/attendances.rst:195 msgid ":guilabel:`Add Custom Group`: this option displays a drop-down menu with a variety of options to group the attendance data by, including :guilabel:`City`, :guilabel:`Country`, :guilabel:`Mode`, and :guilabel:`IP Address`." msgstr "" -#: ../../content/applications/hr/attendances.rst:356 +#: ../../content/applications/hr/attendances.rst:202 msgid "Attendance log details" msgstr "" -#: ../../content/applications/hr/attendances.rst:358 +#: ../../content/applications/hr/attendances.rst:204 msgid "Odoo captures various time and location details when a user checks in and out. The specific details provided are determined by the method the user checked in and out." msgstr "" -#: ../../content/applications/hr/attendances.rst:361 +#: ../../content/applications/hr/attendances.rst:207 msgid "To view the specific check in and/or check out details for an employee, click on an individual entry in the overview dashboard." msgstr "" -#: ../../content/applications/hr/attendances.rst:364 +#: ../../content/applications/hr/attendances.rst:210 msgid "A detailed attendance log for the user appears in a pop-up window. To close the detailed attendance log, click the :guilabel:`Save & Close` button in the bottom-left corner of the form." msgstr "" -#: ../../content/applications/hr/attendances.rst:367 +#: ../../content/applications/hr/attendances.rst:213 msgid "The detailed attendance log contains the following information:" msgstr "" -#: ../../content/applications/hr/attendances.rst:370 +#: ../../content/applications/hr/attendances.rst:216 msgid "Main details" msgstr "" -#: ../../content/applications/hr/attendances.rst:372 +#: ../../content/applications/hr/attendances.rst:218 msgid ":guilabel:`Employee`: the name of the employee." msgstr "" -#: ../../content/applications/hr/attendances.rst:373 +#: ../../content/applications/hr/attendances.rst:219 msgid ":guilabel:`Check In`: the date and time the employee checked in." msgstr "" -#: ../../content/applications/hr/attendances.rst:374 +#: ../../content/applications/hr/attendances.rst:220 msgid ":guilabel:`Check Out`: the date and time the employee checked out. This only appears if the employee has checked out." msgstr "" -#: ../../content/applications/hr/attendances.rst:376 +#: ../../content/applications/hr/attendances.rst:222 msgid ":guilabel:`Worked Hours`: the total amount of time the employee logged for the day, in an hour and minute format (HH:MM). This value calculates all the checks in and check outs for the day, if the employee checked in and out multiple times." msgstr "" -#: ../../content/applications/hr/attendances.rst:379 +#: ../../content/applications/hr/attendances.rst:225 msgid ":guilabel:`Extra Hours`: any extra hours the employee logged that is beyond their expected working hours." msgstr "" -#: ../../content/applications/hr/attendances.rst:383 +#: ../../content/applications/hr/attendances.rst:229 msgid "Check in/check out details" msgstr "" -#: ../../content/applications/hr/attendances.rst:385 +#: ../../content/applications/hr/attendances.rst:231 msgid "The following information appears for both the :guilabel:`Check In` and :guilabel:`Check Out` sections." msgstr "" -#: ../../content/applications/hr/attendances.rst:388 +#: ../../content/applications/hr/attendances.rst:234 msgid ":guilabel:`Mode`: the method with which the attendance information was gathered. :guilabel:`Systray` is displayed if the employee logged in and out :ref:`directly from the database `, :guilabel:`Manual` is displayed if the employee logged in and out :ref:`using an attendance kiosk `." msgstr "" -#: ../../content/applications/hr/attendances.rst:392 +#: ../../content/applications/hr/attendances.rst:238 msgid ":guilabel:`IP Address`: the IP address for the computer the employee used to log in or out." msgstr "" -#: ../../content/applications/hr/attendances.rst:393 +#: ../../content/applications/hr/attendances.rst:239 msgid ":guilabel:`Browser`: the web browser the employee used to log in or out." msgstr "" -#: ../../content/applications/hr/attendances.rst:394 +#: ../../content/applications/hr/attendances.rst:240 msgid ":guilabel:`Localization`: the city and country associated with the computer's IP address." msgstr "" -#: ../../content/applications/hr/attendances.rst:395 +#: ../../content/applications/hr/attendances.rst:241 msgid ":guilabel:`GPS Coordinates`: the specific coordinates when the user logged in or out. To view the specific coordinates on a map, click the :guilabel:`→ View on Maps` button beneath the :guilabel:`GPS Coordinates`. This opens a map in a new browser tab, with the specific location pointed out." msgstr "" @@ -1290,20 +1161,20 @@ msgstr "" msgid "The detailed information for an attendance entry." msgstr "" -#: ../../content/applications/hr/attendances.rst:405 +#: ../../content/applications/hr/attendances.rst:251 #: ../../content/applications/hr/lunch/orders.rst:84 msgid "Errors" msgstr "" -#: ../../content/applications/hr/attendances.rst:407 +#: ../../content/applications/hr/attendances.rst:253 msgid "Entries that contain an error appear on the overview dashboard in red. In the :guilabel:`Gantt view`, the entry appears with a red background. If in the :guilabel:`List view`, the entry text appears in red." msgstr "" -#: ../../content/applications/hr/attendances.rst:411 +#: ../../content/applications/hr/attendances.rst:257 msgid "An error typically occurs when an employee has checked in but has not checked out within the last 24 hours, or when an employee has a check in and check out period spanning over 16 hours." msgstr "" -#: ../../content/applications/hr/attendances.rst:414 +#: ../../content/applications/hr/attendances.rst:260 msgid "To fix the error, the attendance entry must be modified or deleted. Click on the entry to reveal a pop-up containing the details for that particular entry. To modify the :guilabel:`Check In` and/or :guilabel:`Check Out` information, click on the :guilabel:`Check In` or :guilabel:`Check Out` field and a calendar selector appears. Click on the desired date, then use the time selector beneath the calendar to select the specific time for the entry. When the information is correct, click :guilabel:`Apply.`" msgstr "" @@ -1312,35 +1183,35 @@ msgid "The pop-up that allows for modifications to an attendance entry with an e "selector is shown, and the time selector is highlighted." msgstr "" -#: ../../content/applications/hr/attendances.rst:426 +#: ../../content/applications/hr/attendances.rst:272 msgid "When all the information on the pop-up is correct, click :guilabel:`Save & Close`. When the entry no longer has an error, the entry appears in gray instead of red." msgstr "" -#: ../../content/applications/hr/attendances.rst:429 +#: ../../content/applications/hr/attendances.rst:275 msgid "To delete an entry, click :guilabel:`Remove` on the pop-up instead of making modifications to the entry." msgstr "" -#: ../../content/applications/hr/attendances.rst:435 +#: ../../content/applications/hr/attendances.rst:281 msgid "To view attendance reports, click :guilabel:`Reporting` in the top menu. The default report displays each employee's attendance information for the past 3 months, in a :guilabel:`Line Chart`." msgstr "" -#: ../../content/applications/hr/attendances.rst:438 +#: ../../content/applications/hr/attendances.rst:284 msgid "The default view is a :guilabel:`Graph`. To view the data in a pivot table, click the :guilabel:`Pivot Table` button on the top right of the report. To switch back to the graph view, click the :guilabel:`Graph` button, located next to the :guilabel:`Pivot Table` button." msgstr "" -#: ../../content/applications/hr/attendances.rst:442 +#: ../../content/applications/hr/attendances.rst:288 msgid "To present different information, adjust the :ref:`filters and groups ` in the same way as in the :guilabel:`Overview` dashboard." msgstr "" -#: ../../content/applications/hr/attendances.rst:445 +#: ../../content/applications/hr/attendances.rst:291 msgid "The data can be presented in either a :guilabel:`Bar Chart`, :guilabel:`Line Chart`, :guilabel:`Pie Chart`, :guilabel:`Stacked` chart, or in :guilabel:`Descending` or :guilabel:`Ascending` order. To change the view to any of these charts, click the corresponding button above the displayed chart." msgstr "" -#: ../../content/applications/hr/attendances.rst:449 +#: ../../content/applications/hr/attendances.rst:295 msgid "To change the :guilabel:`Measures`, click the :guilabel:`Measures` button and select the desired measure from the drop-down menu." msgstr "" -#: ../../content/applications/hr/attendances.rst:452 +#: ../../content/applications/hr/attendances.rst:298 msgid "The report can also be inserted into a spreadsheet. Click the :guilabel:`Insert in Spreadsheet` button and a pop-up appears. Select the desired spreadsheet, and click :guilabel:`Confirm`." msgstr "" @@ -1348,11 +1219,15 @@ msgstr "" msgid "The default report view, with all the optional view buttons highlighted." msgstr "" -#: ../../content/applications/hr/attendances.rst:460 +#: ../../content/applications/hr/attendances.rst:306 msgid ":doc:`attendances/check_in_check_out`" msgstr "" -#: ../../content/applications/hr/attendances.rst:461 +#: ../../content/applications/hr/attendances.rst:307 +msgid ":doc:`attendances/kiosks`" +msgstr "" + +#: ../../content/applications/hr/attendances.rst:308 msgid ":doc:`attendances/hardware`" msgstr "" @@ -1438,69 +1313,352 @@ msgstr "" msgid "Hardware" msgstr "" -#: ../../content/applications/hr/attendances/hardware.rst:6 -msgid "Kiosk management" -msgstr "" - -#: ../../content/applications/hr/attendances/hardware.rst:8 -msgid "A kiosk is a self-service station that allows employees to check in and check out for work shifts." +#: ../../content/applications/hr/attendances/hardware.rst:5 +msgid "Employees who are **not** database users, and therefore, do **not** have access to the *Attendances* app, must sign in and out of work using a kiosk. The following are the physical requirements for setting up a kiosk." msgstr "" #: ../../content/applications/hr/attendances/hardware.rst:10 -msgid "There are two ways to set up a kiosk:" +msgid "Kiosk devices" msgstr "" #: ../../content/applications/hr/attendances/hardware.rst:12 -msgid "**Laptop and desktop PC**" -msgstr "" - -#: ../../content/applications/hr/attendances/hardware.rst:14 -msgid "Running a kiosk in a web browser is the cheapest and most flexible option. You can print employee badges with any thermal or inkjet printer compatible with your web browser." +msgid "A kiosk is a self-service station, where employees can :ref:`check in and out of work ` with either a :ref:`badge ` or an :ref:`RFID key fob `. Typically, these devices are dedicated as kiosks only, but any device with an internet browser is able to be set up as a kiosk." msgstr "" #: ../../content/applications/hr/attendances/hardware.rst:17 -msgid "**Tablet and mobile phone (Android or iOS)**" +msgid "A kiosk is used by navigating to the webpage specified in the :ref:`configuration ` section of the *Attendances* app." msgstr "" -#: ../../content/applications/hr/attendances/hardware.rst:19 -msgid "Tablets and mobile phones take up much less space, and their touchscreens are easy to use. Consider putting them in a secure stand at the front desk or mounting them securely on a wall." +#: ../../content/applications/hr/attendances/hardware.rst:20 +msgid "Kiosks are set up using one of the following types of devices:" +msgstr "" + +#: ../../content/applications/hr/attendances/hardware.rst:22 +msgid "Laptop or Desktop computer" msgstr "" #: ../../content/applications/hr/attendances/hardware.rst:23 -msgid "We recommend using an iPad together with the `Heckler Design WindFall Stand `_" +msgid "Tablet" +msgstr "" + +#: ../../content/applications/hr/attendances/hardware.rst:24 +msgid "Mobile phone (Android or iOS)" msgstr "" #: ../../content/applications/hr/attendances/hardware.rst:27 -msgid "RFID key fob readers" +msgid "Touchscreens are easy to use, and tablets and mobile phones take up less space. That's why most consider using a smaller device with a touchscreen as a kiosk." msgstr "" -#: ../../content/applications/hr/attendances/hardware.rst:29 -msgid "Employees can scan personal RFID key fobs with an RFID reader to manage check-ins and check-outs quickly and easily." +#: ../../content/applications/hr/attendances/hardware.rst:30 +msgid "It is recommended to place kiosks on a secure stand, or mount them securely on a wall." msgstr "" -#: ../../content/applications/hr/attendances/hardware.rst:-1 -msgid "An RFID key fob is placed on an RFID reader" +#: ../../content/applications/hr/attendances/hardware.rst:35 +msgid "Badges" msgstr "" -#: ../../content/applications/hr/attendances/hardware.rst:38 -msgid "We recommend using the `Neuftech USB RFID Reader `_." +#: ../../content/applications/hr/attendances/hardware.rst:37 +msgid "Badges are a way for employees to quickly sign in and out from a kiosk, as badges are scanned by the kiosk's camera to quickly identify the employee." msgstr "" -#: ../../content/applications/hr/attendances/hardware.rst:41 -#: ../../content/applications/hr/attendances/hardware.rst:57 -msgid "An IoT box is **not** required." +#: ../../content/applications/hr/attendances/hardware.rst:40 +msgid "To generate a badge, first navigate to the :menuselection:`Employees app`. Next, click on the desired employee card to open the employee's form, then click the :guilabel:`HR Settings` tab." msgstr "" -#: ../../content/applications/hr/attendances/hardware.rst:44 -msgid "Barcode scanners" +#: ../../content/applications/hr/attendances/hardware.rst:43 +msgid "Under the :guilabel:`ATTENDANCE/POINT OF SALE/MANUFACTURING` section, there is a :guilabel:`Badge ID` field. If this field is blank, click :guilabel:`Generate` at the end of the :guilabel:`Badge ID` line, and the field is automatically populated with a new badge ID number. Then, click :guilabel:`Print Badge` at the end of the badge ID number to create a PDF file of the badge." msgstr "" -#: ../../content/applications/hr/attendances/hardware.rst:46 -msgid "Employees can scan the barcode on their employee badges to manage check-ins and check-outs quickly and easily. The kiosk mode works with most USB barcode scanners connected directly to a computer. Bluetooth barcode scanners are also supported natively." +#: ../../content/applications/hr/attendances/hardware.rst:48 +msgid "If a badge ID number is already present on the employee form, there is no :guilabel:`Generate` button, only a :guilabel:`Print Badge` button." msgstr "" #: ../../content/applications/hr/attendances/hardware.rst:51 -msgid "We recommend using the `Honeywell product line `_. If the barcode scanner is connected directly to a computer, it must be configured to use the computer's keyboard layout." +msgid "The employee's badge contains the employee's photo, name, job position, company logo, and a barcode that can be scanned at a kiosk to check in and out." +msgstr "" + +#: ../../content/applications/hr/attendances/hardware.rst:54 +msgid "Badges can be printed for employees using any thermal or inkjet printer." +msgstr "" + +#: ../../content/applications/hr/attendances/hardware.rst:-1 +msgid "A badge for an employee that is created from the Employees app." +msgstr "" + +#: ../../content/applications/hr/attendances/hardware.rst:61 +msgid "Badges are **not** required, as employees can manually identify themselves on the kiosk." +msgstr "" + +#: ../../content/applications/hr/attendances/hardware.rst:64 +msgid "Barcode scanners" +msgstr "" + +#: ../../content/applications/hr/attendances/hardware.rst:66 +msgid "When using badges to check in and out, the barcode **must** be scanned to identify the employee. This can be done with the kiosk's camera, if one is available on the device." +msgstr "" + +#: ../../content/applications/hr/attendances/hardware.rst:69 +msgid "If a camera is **not** available on the kiosk device, an external barcode scanner must be used to scan badges." +msgstr "" + +#: ../../content/applications/hr/attendances/hardware.rst:72 +msgid "Kiosks work with most USB barcode scanners. Bluetooth barcode scanners are also supported for devices without USB ports, or if a wireless connection is desired." +msgstr "" + +#: ../../content/applications/hr/attendances/hardware.rst:75 +msgid "Follow the manufacturer's instructions on the barcode scanner to properly connect the barcode scanner to the kiosk device." +msgstr "" + +#: ../../content/applications/hr/attendances/hardware.rst:79 +msgid "If the barcode scanner is connected directly to a computer, it :doc:`must be configured <../../inventory_and_mrp/barcode/setup/hardware>` to use the computer's keyboard layout." +msgstr "" + +#: ../../content/applications/hr/attendances/hardware.rst:83 +msgid "An IoT box is **not** required to use a barcode scanner." +msgstr "" + +#: ../../content/applications/hr/attendances/hardware.rst:88 +msgid "RFID key fob readers" +msgstr "" + +#: ../../content/applications/hr/attendances/hardware.rst:90 +msgid "Instead of using a :ref:`badge `, employees can scan a personal RFID key fob with an RFID reader to check in and out of work." +msgstr "" + +#: ../../content/applications/hr/attendances/hardware.rst:93 +msgid "It is **required** to purchase *both* RFID key fobs and an RFID reader to use this method to check in and out. Follow the manufacturer's directions to install the RFID reader, and set up the RFID key fob." +msgstr "" + +#: ../../content/applications/hr/attendances/hardware.rst:-1 +msgid "An RFID key fob is placed on an RFID reader." +msgstr "" + +#: ../../content/applications/hr/attendances/hardware.rst:103 +msgid "A recommended RFID reader is the `Neuftech USB RFID Reader `_." +msgstr "" + +#: ../../content/applications/hr/attendances/hardware.rst:107 +msgid "An IoT box is **not** required to use RFID key fobs." +msgstr "" + +#: ../../content/applications/hr/attendances/kiosks.rst:3 +msgid "Kiosks" +msgstr "" + +#: ../../content/applications/hr/attendances/kiosks.rst:5 +msgid "Odoo's *Attendances* app allows employees to check in and out of work directly from the database, or from a kiosk." +msgstr "" + +#: ../../content/applications/hr/attendances/kiosks.rst:8 +msgid "A kiosk is a :doc:`dedicated device ` (a PC, tablet, or mobile phone) for employees to use when they check in and out." +msgstr "" + +#: ../../content/applications/hr/attendances/kiosks.rst:11 +msgid "Kiosks are needed for employees who do **not** have access to the database." +msgstr "" + +#: ../../content/applications/hr/attendances/kiosks.rst:13 +msgid "Only employees with access to the database can check in and out from the *Attendances* app, and they are referred to as *users*." +msgstr "" + +#: ../../content/applications/hr/attendances/kiosks.rst:17 +msgid "If employees :ref:`check in and out ` using a badge or an RFID, then an :doc:`accessible device ` in :ref:`Kiosk Mode ` **must** be available in order to use these two methods." +msgstr "" + +#: ../../content/applications/hr/attendances/kiosks.rst:24 +msgid "There are only a few configurations needed to use kiosks in the *Attendances* application. Navigate to :menuselection:`Attendances app --> Configuration` to access the :guilabel:`Settings` page to configure the :ref:`attendances/kiosk-mode` and the :ref:`attendances/kiosk-settings`." +msgstr "" + +#: ../../content/applications/hr/attendances/kiosks.rst:28 +msgid "Once all desired settings have been configured, click the :guilabel:`Save` button on the :guilabel:`Settings` page, to activate and enable them." +msgstr "" + +#: ../../content/applications/hr/attendances/kiosks.rst:34 +msgid "Kiosk Mode section" +msgstr "" + +#: ../../content/applications/hr/attendances/kiosks.rst:36 +msgid "Using the drop-down menu, select how an employee checks in when using a kiosk. Options are :guilabel:`Barcode/RFID`, :guilabel:`Barcode/RFID and Manual Selection`, or :guilabel:`Manual Selection`." +msgstr "" + +#: ../../content/applications/hr/attendances/kiosks.rst:41 +msgid "The *Barcode* application **does not** need to be installed to use one of the Barcode/RFID settings." +msgstr "" + +#: ../../content/applications/hr/attendances/kiosks.rst:47 +msgid "Kiosk Settings section" +msgstr "" + +#: ../../content/applications/hr/attendances/kiosks.rst:49 +msgid "The various settings in the :guilabel:`Kiosk Settings` section determine how employees check in and out with kiosks." +msgstr "" + +#: ../../content/applications/hr/attendances/kiosks.rst:52 +msgid ":guilabel:`Barcode Source`: this setting **only** appears if one of the two *Barcode/RFID* selections were configured for the :ref:`Kiosk Mode ` setting." +msgstr "" + +#: ../../content/applications/hr/attendances/kiosks.rst:55 +msgid "If available, select how barcodes are scanned at the kiosk, via one of the drop-down menu options. Barcodes can be scanned with a dedicated :guilabel:`Scanner`, or with a device's camera (:guilabel:`Front Camera` or :guilabel:`Back Camera`)." +msgstr "" + +#: ../../content/applications/hr/attendances/kiosks.rst:58 +msgid ":guilabel:`Employee PIN Identification`: tick this checkbox if employees should use a unique PIN to check in. PINs are configured on each individual employee record. Refer to the :ref:`new employee documentation ` documentation for more information on setting up PINs." +msgstr "" + +#: ../../content/applications/hr/attendances/kiosks.rst:62 +msgid ":guilabel:`Display Time`: determine how many seconds a check-in/check-out confirmation message remains on the kiosk screen before returning to the main check in screen." +msgstr "" + +#: ../../content/applications/hr/attendances/kiosks.rst:64 +msgid ":guilabel:`Attendance Kiosk Url`: Odoo generates a unique web address (URL) to use a device as a kiosk, without having to sign in to the Odoo database. When setting up a kiosk device, navigate to this unique web address in a web browser to present the *Attendances* app kiosk." +msgstr "" + +#: ../../content/applications/hr/attendances/kiosks.rst:69 +msgid "These kiosk URLs are **not** secured with any type of access code. Anyone who has the URL can access the *Attendances* app kiosk. If the URL is compromised for any reason, such as in the event of a security breach, click :guilabel:`Generate a new Kiosk Mode URL`, located beneath the link, to generate a new URL, and update the kiosk, accordingly." +msgstr "" + +#: ../../content/applications/hr/attendances/kiosks.rst:75 +msgid "Kiosk mode" +msgstr "" + +#: ../../content/applications/hr/attendances/kiosks.rst:77 +msgid "Entering *Kiosk Mode* is **only** available for users with specific :ref:`access rights `." +msgstr "" + +#: ../../content/applications/hr/attendances/kiosks.rst:80 +msgid "*Kiosk Mode* can be activated in two different ways:" +msgstr "" + +#: ../../content/applications/hr/attendances/kiosks.rst:82 +msgid "Navigate to the :menuselection:`Attendances app`, and click :guilabel:`Kiosk Mode` in the top menu. The device then signs out of Odoo and enters *Kiosk Mode*." +msgstr "" + +#: ../../content/applications/hr/attendances/kiosks.rst:84 +msgid "Navigate to the :menuselection:`Attendances app --> Configuration`. In the :guilabel:`Kiosk Settings` section, use the link in the :guilabel:`Attendance Kiosk Url` field to open *Kiosk Mode* on any device." +msgstr "" + +#: ../../content/applications/hr/attendances/kiosks.rst:-1 +msgid "The Attendances Kiosk URL field in the settings section of the Attendances application." +msgstr "" + +#: ../../content/applications/hr/attendances/kiosks.rst:92 +msgid "As a security measure, once a device is in *Kiosk Mode*, it is not possible to go back into the database without signing back in." +msgstr "" + +#: ../../content/applications/hr/attendances/kiosks.rst:96 +msgid "At any time, a new kiosk URL can be generated, if needed. Click the :icon:`fa-refresh` :guilabel:`Generate a new Kiosk Mode URL`" +msgstr "" + +#: ../../content/applications/hr/attendances/kiosks.rst:99 +msgid "To exit *Kiosk Mode*, just close the tab in the web browser or return to the main log-in screen of Odoo." +msgstr "" + +#: ../../content/applications/hr/attendances/kiosks.rst:105 +msgid "Check in and out with a kiosk" +msgstr "" + +#: ../../content/applications/hr/attendances/kiosks.rst:108 +msgid "Badge" +msgstr "" + +#: ../../content/applications/hr/attendances/kiosks.rst:110 +msgid "To check in or out using a badge, tap the :icon:`fa-camera` :guilabel:`Tap to scan` image in the center of the kiosk." +msgstr "" + +#: ../../content/applications/hr/attendances/kiosks.rst:-1 +msgid "The Attendances Kiosk view displaying the scan badge image." +msgstr "" + +#: ../../content/applications/hr/attendances/kiosks.rst:117 +msgid "Then, scan the barcode on the badge using the method configured in the :ref:`Kiosk Settings ` section of the configuration menu." +msgstr "" + +#: ../../content/applications/hr/attendances/kiosks.rst:120 +msgid "Once the barcode is scanned, the employee is checked in or out, and a :ref:`confirmation message ` appears with all the information." +msgstr "" + +#: ../../content/applications/hr/attendances/kiosks.rst:124 +msgid "RFID" +msgstr "" + +#: ../../content/applications/hr/attendances/kiosks.rst:126 +msgid "To check in or out using an RFID key fob, simply scan the fob with an RFID reader." +msgstr "" + +#: ../../content/applications/hr/attendances/kiosks.rst:128 +msgid "Once scanned, the employee is either checked in or checked out, and a :ref:`confirmation message ` appears with all the information." +msgstr "" + +#: ../../content/applications/hr/attendances/kiosks.rst:132 +msgid "Manually" +msgstr "" + +#: ../../content/applications/hr/attendances/kiosks.rst:134 +msgid "Users who do not have a scannable badge, or an RFID fob, can manually check in and out at a kiosk." +msgstr "" + +#: ../../content/applications/hr/attendances/kiosks.rst:136 +msgid "Tap the :guilabel:`Identify Manually` button on the kiosk, and a screen appears with all the employees that can be checked in or out. The *Employees* application dashboard has the same display." +msgstr "" + +#: ../../content/applications/hr/attendances/kiosks.rst:139 +msgid "Tap on a person to check them in or out, and a :ref:`confirmation message ` appears." +msgstr "" + +#: ../../content/applications/hr/attendances/kiosks.rst:142 +msgid "There are two ways to quickly find a specific person:" +msgstr "" + +#: ../../content/applications/hr/attendances/kiosks.rst:144 +msgid ":guilabel:`Search...`: tap on the :guilabel:`Search...` field, and enter the desired person's name. As the name is typed in, the matching results are displayed on the screen." +msgstr "" + +#: ../../content/applications/hr/attendances/kiosks.rst:146 +msgid ":guilabel:`Department`: tap on any desired selection in the :guilabel:`Department` section, located on the left-side of the screen, to **only** view employees from that specific department. The number at the end of each listed :guilabel:`Department` represents how many employees that department has." +msgstr "" + +#: ../../content/applications/hr/attendances/kiosks.rst:152 +msgid "PIN" +msgstr "" + +#: ../../content/applications/hr/attendances/kiosks.rst:154 +msgid "If the :guilabel:`Employee PIN Identification` checkbox was ticked in the :ref:`Kiosk Settings ` section of the configuration menu, the employee is prompted to enter a PIN when manually checking in or out." +msgstr "" + +#: ../../content/applications/hr/attendances/kiosks.rst:158 +msgid "After the employee is selected, a number pad appears with a message. When checking in, :guilabel:`(Employee) Welcome! Please enter your PIN to check in` appears above the numbers. When checking out, :guilabel:`(Employee) Want to check out? Please enter your PIN to check out` appears above the numbers." +msgstr "" + +#: ../../content/applications/hr/attendances/kiosks.rst:163 +msgid "Tap in the PIN using the number pad, then tap :guilabel:`OK` when done. The employee is then checked in or out, and a :ref:`confirmation message ` appears." +msgstr "" + +#: ../../content/applications/hr/attendances/kiosks.rst:-1 +msgid "The pop-up that appears when prompted to enter a pin." +msgstr "" + +#: ../../content/applications/hr/attendances/kiosks.rst:173 +msgid "Confirmation message" +msgstr "" + +#: ../../content/applications/hr/attendances/kiosks.rst:175 +msgid "When an employee checks in or out, a confirmation message appears, with all the check in or check out information. When checking in, a welcome message appears, as well as the date and time of check in." +msgstr "" + +#: ../../content/applications/hr/attendances/kiosks.rst:179 +msgid "An :guilabel:`Hours Previously Today: HH:MM` field also appears, displaying any time that has already been logged for that employee for the day. If no time has been logged, the value displayed is: `00:00`. Beneath the message is an :guilabel:`OK` button." +msgstr "" + +#: ../../content/applications/hr/attendances/kiosks.rst:183 +msgid "To exit the screen before the preset time in the kiosk, tap the :guilabel:`OK` button." +msgstr "" + +#: ../../content/applications/hr/attendances/kiosks.rst:185 +msgid "When checking out, the screen displays a goodbye message, with the date and time of check out, and the total hours logged for the day. Beneath the message is a :guilabel:`Goodbye` button. To exit the screen before the preset time, tap the :guilabel:`Goodbye` button." +msgstr "" + +#: ../../content/applications/hr/attendances/kiosks.rst:-1 +msgid "The goodbye message with all the employee's check out information." msgstr "" #: ../../content/applications/hr/employees.rst:7 @@ -2299,475 +2457,493 @@ msgid "Fleet" msgstr "" #: ../../content/applications/hr/fleet.rst:7 -msgid "This document outlines all of the configurations and settings for the *Fleet* application, including :ref:`settings `, :ref:`manufacturers `, :ref:`vehicle models `, and :ref:`model categories `." +msgid "This document outlines the configurations and settings for the *Fleet* application, for both :ref:`settings ` and :ref:`manufacturers `." msgstr "" -#: ../../content/applications/hr/fleet.rst:16 -msgid "To access the settings menu, go to :menuselection:`Fleet application --> Configuration --> Settings`. There are only two settings that need configuration, the vehicle contract end date alert delay, and a new vehicle request limit." +#: ../../content/applications/hr/fleet.rst:15 +msgid "To access the settings menu, go to :menuselection:`Fleet app --> Configuration --> Settings`. Only two settings need configuration: :guilabel:`End Date Contract Alert` and :guilabel:`New Vehicle Request`." msgstr "" #: ../../content/applications/hr/fleet.rst:-1 msgid "Settings available for the Fleet application." msgstr "" -#: ../../content/applications/hr/fleet.rst:25 +#: ../../content/applications/hr/fleet.rst:24 msgid "End Date Contract Alert" msgstr "" -#: ../../content/applications/hr/fleet.rst:27 -msgid "The :guilabel:`End Date Contract Alert` field defines an alert delay for the persons responsible for vehicle contracts. The responsible person(s) will receive an email informing them a vehicle contract is about to expire in the number of days defined in this field." +#: ../../content/applications/hr/fleet.rst:26 +msgid "The :guilabel:`End Date Contract Alert` field how many days before the end of a vehicle contract an alert should be sent. The responsible people 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.rst:32 +#: ../../content/applications/hr/fleet.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.rst:36 +#: ../../content/applications/hr/fleet.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.rst:39 +#: ../../content/applications/hr/fleet.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.rst:46 +#: ../../content/applications/hr/fleet.rst:45 msgid "New Vehicle Request" msgstr "" -#: ../../content/applications/hr/fleet.rst:48 +#: ../../content/applications/hr/fleet.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.rst:55 +#: ../../content/applications/hr/fleet.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.rst:62 +#: ../../content/applications/hr/fleet.rst:61 msgid "Manufacturers" msgstr "" -#: ../../content/applications/hr/fleet.rst:64 +#: ../../content/applications/hr/fleet.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.rst:68 -msgid "The manufacturers appear in a list view in alphabetical order. Each manufacturer's card lists how many specific models are configured for each particular manufacturer. Odoo comes with forty six pre-configured :ref:`models ` from four major auto manufacturers and one major bicycle manufacturer: Audi, BMW, Mercedes, Opel (cars), and Eddy Merckx (bicycle)." +#: ../../content/applications/hr/fleet.rst:67 +msgid "The manufacturers appear in an alphabetical list. Each manufacturer's card lists how many specific models are configured for each particular manufacturer. Odoo comes with forty-six preconfigured :doc:`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.rst:-1 msgid "Manufacturer card with the amount of models listed." msgstr "" -#: ../../content/applications/hr/fleet.rst:78 +#: ../../content/applications/hr/fleet.rst:77 msgid "Add a manufacturer" msgstr "" -#: ../../content/applications/hr/fleet.rst:80 +#: ../../content/applications/hr/fleet.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.rst:88 -msgid "Vehicle Models" +#: ../../content/applications/hr/fleet.rst:85 +msgid ":doc:`fleet/models`" msgstr "" -#: ../../content/applications/hr/fleet.rst:90 -msgid "Many manufacturers have a variety of models that they produce. When adding a vehicle to the fleet, it is important to specify the vehicle model being added. Odoo comes with pre-configured car models from four major auto manufacturers, and one pre-configured bicycle model from one bicycle manufacturer: Audi, BMW, Mercedes, Opel (cars), and Eddy Merckx (bicycle). If a vehicle *other* than the pre-configured models from these manufacturers are part of a fleet, the model (and/or manufacturer) needs to be added to the database." -msgstr "" - -#: ../../content/applications/hr/fleet.rst:98 -msgid "Preconfigured Models" -msgstr "" - -#: ../../content/applications/hr/fleet.rst:100 -msgid "The following models are pre-loaded in Odoo and do not need to be added to the database:" -msgstr "" - -#: ../../content/applications/hr/fleet.rst:103 -msgid "AUDI" -msgstr "" - -#: ../../content/applications/hr/fleet.rst:103 -msgid "BMW" -msgstr "" - -#: ../../content/applications/hr/fleet.rst:103 -msgid "Eddy Merckx" -msgstr "" - -#: ../../content/applications/hr/fleet.rst:103 -msgid "Mercedes" -msgstr "" - -#: ../../content/applications/hr/fleet.rst:103 -msgid "Opel" -msgstr "" - -#: ../../content/applications/hr/fleet.rst:105 -msgid "A1" -msgstr "" - -#: ../../content/applications/hr/fleet.rst:105 -msgid "Serie 1" -msgstr "" - -#: ../../content/applications/hr/fleet.rst:105 -msgid "SanRemo76" -msgstr "" - -#: ../../content/applications/hr/fleet.rst:105 -msgid "Class A" -msgstr "" - -#: ../../content/applications/hr/fleet.rst:105 -msgid "Agilia" -msgstr "" - -#: ../../content/applications/hr/fleet.rst:107 -msgid "A3" -msgstr "" - -#: ../../content/applications/hr/fleet.rst:107 -msgid "Serie 3" -msgstr "" - -#: ../../content/applications/hr/fleet.rst:107 -msgid "Class B" -msgstr "" - -#: ../../content/applications/hr/fleet.rst:107 -msgid "Ampera" -msgstr "" - -#: ../../content/applications/hr/fleet.rst:109 -msgid "A4" -msgstr "" - -#: ../../content/applications/hr/fleet.rst:109 -msgid "Serie 5" -msgstr "" - -#: ../../content/applications/hr/fleet.rst:109 -msgid "Class C" -msgstr "" - -#: ../../content/applications/hr/fleet.rst:109 -msgid "Antara" -msgstr "" - -#: ../../content/applications/hr/fleet.rst:111 -msgid "A5" -msgstr "" - -#: ../../content/applications/hr/fleet.rst:111 -msgid "Serie 6" -msgstr "" - -#: ../../content/applications/hr/fleet.rst:111 -msgid "Class CL" -msgstr "" - -#: ../../content/applications/hr/fleet.rst:111 -msgid "Astra" -msgstr "" - -#: ../../content/applications/hr/fleet.rst:113 -msgid "A6" -msgstr "" - -#: ../../content/applications/hr/fleet.rst:113 -msgid "Serie 7" -msgstr "" - -#: ../../content/applications/hr/fleet.rst:113 -msgid "Class CLS" -msgstr "" - -#: ../../content/applications/hr/fleet.rst:113 -msgid "AstraGTC" -msgstr "" - -#: ../../content/applications/hr/fleet.rst:115 -msgid "A7" -msgstr "" - -#: ../../content/applications/hr/fleet.rst:115 -msgid "Serie Hybrid" -msgstr "" - -#: ../../content/applications/hr/fleet.rst:115 -msgid "Class E" -msgstr "" - -#: ../../content/applications/hr/fleet.rst:115 -msgid "Combo Tour" -msgstr "" - -#: ../../content/applications/hr/fleet.rst:117 -msgid "A8" -msgstr "" - -#: ../../content/applications/hr/fleet.rst:117 -msgid "Serie M" -msgstr "" - -#: ../../content/applications/hr/fleet.rst:117 -msgid "Class GL" -msgstr "" - -#: ../../content/applications/hr/fleet.rst:117 -msgid "Corsa" -msgstr "" - -#: ../../content/applications/hr/fleet.rst:119 -msgid "Q3" -msgstr "" - -#: ../../content/applications/hr/fleet.rst:119 -msgid "Serie X" -msgstr "" - -#: ../../content/applications/hr/fleet.rst:119 -msgid "Class GLK" -msgstr "" - -#: ../../content/applications/hr/fleet.rst:119 -msgid "Insignia" -msgstr "" - -#: ../../content/applications/hr/fleet.rst:121 -msgid "Q5" -msgstr "" - -#: ../../content/applications/hr/fleet.rst:121 -msgid "Serie Z4" -msgstr "" - -#: ../../content/applications/hr/fleet.rst:121 -msgid "Class M" -msgstr "" - -#: ../../content/applications/hr/fleet.rst:121 -msgid "Meriva" -msgstr "" - -#: ../../content/applications/hr/fleet.rst:123 -msgid "Q7" -msgstr "" - -#: ../../content/applications/hr/fleet.rst:123 -msgid "Class R" -msgstr "" - -#: ../../content/applications/hr/fleet.rst:123 -msgid "Mokka" -msgstr "" - -#: ../../content/applications/hr/fleet.rst:125 -msgid "TT" -msgstr "" - -#: ../../content/applications/hr/fleet.rst:125 -msgid "Class S" -msgstr "" - -#: ../../content/applications/hr/fleet.rst:125 -msgid "Zafira" -msgstr "" - -#: ../../content/applications/hr/fleet.rst:127 -msgid "Class SLK" -msgstr "" - -#: ../../content/applications/hr/fleet.rst:127 -msgid "Zafira Tourer" -msgstr "" - -#: ../../content/applications/hr/fleet.rst:129 -msgid "Class SLS" -msgstr "" - -#: ../../content/applications/hr/fleet.rst:135 -msgid "Add a new model" -msgstr "" - -#: ../../content/applications/hr/fleet.rst:137 -msgid "New vehicle models can easily be added to the database. To add a new model, navigate to :menuselection:`Fleet app --> Configuration --> Vehicle Models`. Click :guilabel:`Create` and a vehicle model form will load. Enter the following information on the form, then click :guilabel:`Save`. Be advised, some fields are specific to Belgian based companies, so not all fields or sections may be visible depending on the location of the company." -msgstr "" - -#: ../../content/applications/hr/fleet.rst:143 -msgid ":guilabel:`Model name`: enter the model name in the field." -msgstr "" - -#: ../../content/applications/hr/fleet.rst:144 -msgid ":guilabel:`Manufacturer`: select the manufacturer from the drop-down menu. If the manufacturer is not configured, type in the manufacturer and then click :guilabel:`Create` or :guilabel:`Create & Edit`." -msgstr "" - -#: ../../content/applications/hr/fleet.rst:147 -msgid ":guilabel:`Vehicle Type`: select one of two preconfigured vehicle types, either :guilabel:`Car` or :guilabel:`Bike`, from the drop-down menu. The vehicle types are hardcoded in Odoo and are integrated with the *Payroll* application since vehicles can be part of an employee's benefits. Adding additional vehicle types is not possible as it will affect payroll." -msgstr "" - -#: ../../content/applications/hr/fleet.rst:151 -msgid ":guilabel:`Category`: select the category the vehicle is categorized under from the drop-down menu. To create a new category, type in the category and then click :guilabel:`Create (new category)`." -msgstr "" - -#: ../../content/applications/hr/fleet.rst:156 -msgid "When the manufacturer is selected, the logo for the manufacturer will automatically load in the image box in the top right corner." -msgstr "" - -#: ../../content/applications/hr/fleet.rst:160 -msgid "Information tab" -msgstr "" - -#: ../../content/applications/hr/fleet.rst:163 -msgid "Model" -msgstr "" - -#: ../../content/applications/hr/fleet.rst:165 -msgid ":guilabel:`Seats Number`: enter how many passengers the vehicle can accommodate." -msgstr "" - -#: ../../content/applications/hr/fleet.rst:166 -msgid ":guilabel:`Doors Number`: enter the number of doors the vehicle has." -msgstr "" - -#: ../../content/applications/hr/fleet.rst:167 -msgid ":guilabel:`Color`: enter the color of the vehicle." -msgstr "" - -#: ../../content/applications/hr/fleet.rst:168 -msgid ":guilabel:`Model Year`: enter the year the vehicle was manufactured." -msgstr "" - -#: ../../content/applications/hr/fleet.rst:169 -msgid ":guilabel:`Trailer Hitch`: check this box if the vehicle has a trailer hitch installed." -msgstr "" - -#: ../../content/applications/hr/fleet.rst:172 -#: ../../content/applications/hr/payroll.rst:398 -msgid "Salary" -msgstr "" - -#: ../../content/applications/hr/fleet.rst:175 -msgid "The :guilabel:`Salary` section only appears for Belgian-based companies, and only if the company has their localization setting set to Belgium. The cost values are all **monthly** with the exception of the :guilabel:`Catalog Value (VAT Incl.)`." -msgstr "" - -#: ../../content/applications/hr/fleet.rst:179 -msgid ":guilabel:`Can be requested`: check this box if employees can request this model vehicle." -msgstr "" - -#: ../../content/applications/hr/fleet.rst:180 -msgid ":guilabel:`Catalog Value (VAT Incl.)`: enter the :abbr:`MSRP (Manufacturer's Suggested Retail Price)` for the vehicle at the time of purchase or lease." -msgstr "" - -#: ../../content/applications/hr/fleet.rst:182 -msgid ":guilabel:`C02 fee`: this value is automatically calculated based on Belgian laws and regulations, and cannot be modified. The value is based on the value entered in the :guilabel:`CO2 Emissions` field in the :guilabel:`Engine` section of the vehicle form." -msgstr "" - -#: ../../content/applications/hr/fleet.rst:187 -msgid "Modifying the :guilabel:`CO2 Emissions` field will adjust the value in the :guilabel:`CO2 fee` field." -msgstr "" - -#: ../../content/applications/hr/fleet.rst:190 -msgid ":guilabel:`Cost (Depreciated)`: enter the monthly cost for the vehicle, which appears in the salary configurator that is available to a future employee when they are offered a job position. This value impacts the gross and net salary of the employee who is assigned to the vehicle. This figure is depreciated over time according to local tax laws. The :guilabel:`Cost (Depreciated)` does not depreciate automatically on the *vehicle model*, it only depreciates based on the *contract* linked to a specific vehicle and not on the general model." -msgstr "" - -#: ../../content/applications/hr/fleet.rst:196 -msgid ":guilabel:`Total Cost (Depreciated)`: this value is the :guilabel:`Cost (Depreciated)` and the :guilabel:`C02 fee` fields combined, and also is depreciated over time." -msgstr "" - -#: ../../content/applications/hr/fleet.rst:200 -msgid "Engine" -msgstr "" - -#: ../../content/applications/hr/fleet.rst:202 -msgid ":guilabel:`Fuel Type`: select the type of fuel the vehicle uses form the drop-down menu. The options are :guilabel:`Diesel`, :guilabel:`Gasoline`, :guilabel:`Hybrid Diesel`, :guilabel:`Hybrid Gasoline`, :guilabel:`Plug-in Hybrid Diesel`, :guilabel:`Plug-in Hybrid Gasoline`, :guilabel:`CNG`, :guilabel:`LPG`, :guilabel:`Hydrogen`, or :guilabel:`Electric`." -msgstr "" - -#: ../../content/applications/hr/fleet.rst:206 -msgid ":guilabel:`CO2 Emissions`: enter the average carbon dioxide emissions the vehicle produces in grams per kilometer (g/km). This information is provided by the car manufacturer." -msgstr "" - -#: ../../content/applications/hr/fleet.rst:208 -msgid ":guilabel:`CO2 Standard`: enter the standard amount of carbon dioxide in grams per kilometer (g/km) for a similar sized vehicle." -msgstr "" - -#: ../../content/applications/hr/fleet.rst:210 -msgid ":guilabel:`Transmission`: select the transmission type from the drop-down menu, either :guilabel:`Manual` or :guilabel:`Automatic`." -msgstr "" - -#: ../../content/applications/hr/fleet.rst:212 -msgid ":guilabel:`Power`: if the vehicle is electric or hybrid, enter the power the vehicle uses in kilowatts (kW)." -msgstr "" - -#: ../../content/applications/hr/fleet.rst:214 -msgid ":guilabel:`Horsepower`: enter the vehicle's horsepower in this field." -msgstr "" - -#: ../../content/applications/hr/fleet.rst:215 -#: ../../content/applications/hr/fleet/new_vehicle.rst:290 -msgid ":guilabel:`Horsepower Taxation`: enter the amount that is taxed based on the size of the vehicle's engine. This is determined by local taxes and regulations, and varies depending on the location. It is recommended to check with the accounting department to ensure this value is correct." -msgstr "" - -#: ../../content/applications/hr/fleet.rst:218 -msgid ":guilabel:`Tax Deduction`: this field auto-populates according to the engine specifications, and cannot be modified. The percentage is based on the localization settings and local tax laws." -msgstr "" - -#: ../../content/applications/hr/fleet.rst:222 -msgid "Vendors tab" -msgstr "" - -#: ../../content/applications/hr/fleet.rst:224 -msgid "Vehicle specific vendors, such as car dealerships, are not listed separately from other vendors. The vendors that a vehicle can be purchased from also appear in the list of vendors used by the *Purchase* app." -msgstr "" - -#: ../../content/applications/hr/fleet.rst:228 -msgid "The vendor(s) the vehicle can be purchased from may be added in this tab. To add a vendor, click :guilabel:`Add`, and a pop-up loads with a list of all the vendors currently in the database. Select the vendor to add by clicking the checkbox next to the vendor name, then click :guilabel:`Select`. There is no limit to the number of vendors that can be added to this list." -msgstr "" - -#: ../../content/applications/hr/fleet.rst:233 -msgid "If a vendor is not in the database, add a vendor by clicking :guilabel:`Create`. A vendor form will load. Enter the information in the vendor tab, then click :guilabel:`Save & Close` to add the vendor and close the window, or :guilabel:`Save & New` to add the current vendor and create another new vendor." -msgstr "" - -#: ../../content/applications/hr/fleet.rst:-1 -msgid "Vendor form to fill out when adding a new vendor." -msgstr "" - -#: ../../content/applications/hr/fleet.rst:245 -msgid "Model Category" -msgstr "" - -#: ../../content/applications/hr/fleet.rst:247 -msgid "To best organize a fleet, it is recommended to have vehicle models housed under a specific category, to more easily see what kinds of vehicles are in the fleet. Model categories are set on the :ref:`vehicle model form `." -msgstr "" - -#: ../../content/applications/hr/fleet.rst:251 -msgid "To view all the models currently set up, navigate to :menuselection:`Fleet application --> Configuration --> Model Category`. All models are displayed in a list view." -msgstr "" - -#: ../../content/applications/hr/fleet.rst:255 -msgid "Add a new model category" -msgstr "" - -#: ../../content/applications/hr/fleet.rst:257 -msgid "To add a new category, click :guilabel:`Create`. A new entry line appears at the bottom of the list. Type in the new category, then click :guilabel:`Save` to save the entry." -msgstr "" - -#: ../../content/applications/hr/fleet.rst:260 -msgid "To reorganize how the categories appear in the list, click on the up and down arrows to the left of the category to be moved, and drag the line to the desired position. The order of the list does not affect the database in any way. However, it may be preferable to view the vehicle categories in a specific order, for example, by size, or the numbers of passengers the vehicle can carry." -msgstr "" - -#: ../../content/applications/hr/fleet.rst:-1 -msgid "List view of the models in the fleet." -msgstr "" - -#: ../../content/applications/hr/fleet.rst:270 +#: ../../content/applications/hr/fleet.rst:86 msgid ":doc:`fleet/new_vehicle`" msgstr "" -#: ../../content/applications/hr/fleet.rst:271 +#: ../../content/applications/hr/fleet.rst:87 msgid ":doc:`fleet/service`" msgstr "" +#: ../../content/applications/hr/fleet/models.rst:3 +msgid "Vehicle models" +msgstr "" + +#: ../../content/applications/hr/fleet/models.rst:5 +msgid "When adding a vehicle to the fleet, specify the vehicle model to maintain updated records, which keeps track of specific details, like maintenance schedules and parts compatibility." +msgstr "" + +#: ../../content/applications/hr/fleet/models.rst:8 +msgid "Odoo comes with preconfigured car models from four major auto manufacturers: Audi, BMW, Mercedes, and Opel." +msgstr "" + +#: ../../content/applications/hr/fleet/models.rst:11 +msgid "If a new vehicle model joins the fleet, and it is not one of the preconfigured models from these manufacturers, the model (and/or manufacturer) **must** be :ref:`added to the database `." +msgstr "" + +#: ../../content/applications/hr/fleet/models.rst:16 +msgid "Preconfigured models" +msgstr "" + +#: ../../content/applications/hr/fleet/models.rst:18 +msgid "The following models are preconfigured in Odoo, and do not need to be added to the database:" +msgstr "" + +#: ../../content/applications/hr/fleet/models.rst:21 +msgid "AUDI" +msgstr "" + +#: ../../content/applications/hr/fleet/models.rst:21 +msgid "BMW" +msgstr "" + +#: ../../content/applications/hr/fleet/models.rst:21 +msgid "Mercedes" +msgstr "" + +#: ../../content/applications/hr/fleet/models.rst:21 +msgid "Opel" +msgstr "" + +#: ../../content/applications/hr/fleet/models.rst:23 +msgid "A1" +msgstr "" + +#: ../../content/applications/hr/fleet/models.rst:23 +msgid "Serie 1" +msgstr "" + +#: ../../content/applications/hr/fleet/models.rst:23 +msgid "Class A" +msgstr "" + +#: ../../content/applications/hr/fleet/models.rst:23 +msgid "Agilia" +msgstr "" + +#: ../../content/applications/hr/fleet/models.rst:25 +msgid "A3" +msgstr "" + +#: ../../content/applications/hr/fleet/models.rst:25 +msgid "Serie 3" +msgstr "" + +#: ../../content/applications/hr/fleet/models.rst:25 +msgid "Class B" +msgstr "" + +#: ../../content/applications/hr/fleet/models.rst:25 +msgid "Ampera" +msgstr "" + +#: ../../content/applications/hr/fleet/models.rst:27 +msgid "A4" +msgstr "" + +#: ../../content/applications/hr/fleet/models.rst:27 +msgid "Serie 5" +msgstr "" + +#: ../../content/applications/hr/fleet/models.rst:27 +msgid "Class C" +msgstr "" + +#: ../../content/applications/hr/fleet/models.rst:27 +msgid "Antara" +msgstr "" + +#: ../../content/applications/hr/fleet/models.rst:29 +msgid "A5" +msgstr "" + +#: ../../content/applications/hr/fleet/models.rst:29 +msgid "Serie 6" +msgstr "" + +#: ../../content/applications/hr/fleet/models.rst:29 +msgid "Class CL" +msgstr "" + +#: ../../content/applications/hr/fleet/models.rst:29 +msgid "Astra" +msgstr "" + +#: ../../content/applications/hr/fleet/models.rst:31 +msgid "A6" +msgstr "" + +#: ../../content/applications/hr/fleet/models.rst:31 +msgid "Serie 7" +msgstr "" + +#: ../../content/applications/hr/fleet/models.rst:31 +msgid "Class CLS" +msgstr "" + +#: ../../content/applications/hr/fleet/models.rst:31 +msgid "AstraGTC" +msgstr "" + +#: ../../content/applications/hr/fleet/models.rst:33 +msgid "A7" +msgstr "" + +#: ../../content/applications/hr/fleet/models.rst:33 +msgid "Serie Hybrid" +msgstr "" + +#: ../../content/applications/hr/fleet/models.rst:33 +msgid "Class E" +msgstr "" + +#: ../../content/applications/hr/fleet/models.rst:33 +msgid "Combo Tour" +msgstr "" + +#: ../../content/applications/hr/fleet/models.rst:35 +msgid "A8" +msgstr "" + +#: ../../content/applications/hr/fleet/models.rst:35 +msgid "Serie M" +msgstr "" + +#: ../../content/applications/hr/fleet/models.rst:35 +msgid "Class GL" +msgstr "" + +#: ../../content/applications/hr/fleet/models.rst:35 +msgid "Corsa" +msgstr "" + +#: ../../content/applications/hr/fleet/models.rst:37 +msgid "Q3" +msgstr "" + +#: ../../content/applications/hr/fleet/models.rst:37 +msgid "Serie X" +msgstr "" + +#: ../../content/applications/hr/fleet/models.rst:37 +msgid "Class GLK" +msgstr "" + +#: ../../content/applications/hr/fleet/models.rst:37 +msgid "Insignia" +msgstr "" + +#: ../../content/applications/hr/fleet/models.rst:39 +msgid "Q5" +msgstr "" + +#: ../../content/applications/hr/fleet/models.rst:39 +msgid "Serie Z4" +msgstr "" + +#: ../../content/applications/hr/fleet/models.rst:39 +msgid "Class M" +msgstr "" + +#: ../../content/applications/hr/fleet/models.rst:39 +msgid "Meriva" +msgstr "" + +#: ../../content/applications/hr/fleet/models.rst:41 +msgid "Q7" +msgstr "" + +#: ../../content/applications/hr/fleet/models.rst:41 +msgid "Class R" +msgstr "" + +#: ../../content/applications/hr/fleet/models.rst:41 +msgid "Mokka" +msgstr "" + +#: ../../content/applications/hr/fleet/models.rst:43 +msgid "TT" +msgstr "" + +#: ../../content/applications/hr/fleet/models.rst:43 +msgid "Class S" +msgstr "" + +#: ../../content/applications/hr/fleet/models.rst:43 +msgid "Zafira" +msgstr "" + +#: ../../content/applications/hr/fleet/models.rst:45 +msgid "Class SLK" +msgstr "" + +#: ../../content/applications/hr/fleet/models.rst:45 +msgid "Zafira Tourer" +msgstr "" + +#: ../../content/applications/hr/fleet/models.rst:47 +msgid "Class SLS" +msgstr "" + +#: ../../content/applications/hr/fleet/models.rst:53 +msgid "Add a new model" +msgstr "" + +#: ../../content/applications/hr/fleet/models.rst:55 +msgid "To add a new vehicle model, navigate to :menuselection:`Fleet app --> Configuration --> Models: Models`. Click :guilabel:`New`, and in a new vehicle model form, enter the following information on the form." +msgstr "" + +#: ../../content/applications/hr/fleet/models.rst:60 +msgid "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/models.rst:63 +msgid ":guilabel:`Model name`: enter the model name in the field." +msgstr "" + +#: ../../content/applications/hr/fleet/models.rst:64 +msgid ":guilabel:`Manufacturer`: select the manufacturer from the drop-down menu. If the manufacturer is not configured, type in the manufacturer, and click :guilabel:`Create` or :guilabel:`Create and edit..`." +msgstr "" + +#: ../../content/applications/hr/fleet/models.rst:69 +msgid "When the manufacturer is selected, if it is one of the default manufacturers in *Odoo*, the logo for the manufacturer automatically loads in the image box in the top-right corner." +msgstr "" + +#: ../../content/applications/hr/fleet/models.rst:72 +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 affects payroll." +msgstr "" + +#: ../../content/applications/hr/fleet/models.rst:76 +msgid ":guilabel:`Category`: select a category for the vehicle 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/models.rst:80 +msgid "Information tab" +msgstr "" + +#: ../../content/applications/hr/fleet/models.rst:82 +msgid "In the :guilabel:`Information` tab, specify details about the car model, such as the car size, passenger capacity, cost settings (applicable to the Belgium localization only), and engine information." +msgstr "" + +#: ../../content/applications/hr/fleet/models.rst:87 +msgid "Model section" +msgstr "" + +#: ../../content/applications/hr/fleet/models.rst:89 +msgid ":guilabel:`Seats Number`: enter how many passengers the vehicle can accommodate." +msgstr "" + +#: ../../content/applications/hr/fleet/models.rst:90 +msgid ":guilabel:`Doors Number`: enter the number of doors the vehicle has." +msgstr "" + +#: ../../content/applications/hr/fleet/models.rst:91 +msgid ":guilabel:`Color`: enter the color of the vehicle." +msgstr "" + +#: ../../content/applications/hr/fleet/models.rst:92 +msgid ":guilabel:`Model Year`: enter the year the vehicle was manufactured." +msgstr "" + +#: ../../content/applications/hr/fleet/models.rst:93 +msgid ":guilabel:`Trailer Hitch`: tick this checkbox if the vehicle has a trailer hitch installed." +msgstr "" + +#: ../../content/applications/hr/fleet/models.rst:96 +msgid "Salary section" +msgstr "" + +#: ../../content/applications/hr/fleet/models.rst:99 +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/models.rst:103 +msgid ":guilabel:`Can be requested`: tick this checkbox if employees can request this model vehicle, if a vehicle is part of their employee contract." +msgstr "" + +#: ../../content/applications/hr/fleet/models.rst:105 +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/models.rst:107 +msgid ":guilabel:`C02 fee`: represents the carbon dioxide emission fee paid to the Belgian government. This value is automatically calculated, based on Belgian laws and regulations, and **cannot** be modified. The value is based on the figure entered in the :guilabel:`CO2 Emissions` field (in the :guilabel:`Engine` section of the :guilabel:`Information` tab) on the vehicle form." +msgstr "" + +#: ../../content/applications/hr/fleet/models.rst:113 +msgid "Modifying the :guilabel:`CO2 Emissions` field adjusts the value in the :guilabel:`CO2 fee` field." +msgstr "" + +#: ../../content/applications/hr/fleet/models.rst:115 +msgid ":guilabel:`Cost (Depreciated)`: enter the monthly vehicle cost, which appears in the salary configurator for future employees. This value impacts the gross and net salary of the employee 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." +msgstr "" + +#: ../../content/applications/hr/fleet/models.rst:120 +msgid ":guilabel:`Total Cost (Depreciated)`: this value is the combination of the :guilabel:`Cost (Depreciated)` and the :guilabel:`C02 fee` fields. It also depreciated over time." +msgstr "" + +#: ../../content/applications/hr/fleet/models.rst:124 +msgid "Engine" +msgstr "" + +#: ../../content/applications/hr/fleet/models.rst:126 +msgid ":guilabel:`Fuel Type`: select the type of fuel the vehicle uses from the drop-down menu. The options are :guilabel:`Diesel`, :guilabel:`Gasoline`, :guilabel:`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/models.rst:130 +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/models.rst:132 +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/models.rst:134 +msgid ":guilabel:`Transmission`: select :guilabel:`Manual` or :guilabel:`Automatic` transmission from the drop-down menu." +msgstr "" + +#: ../../content/applications/hr/fleet/models.rst:136 +msgid ":guilabel:`Power`: if the vehicle is electric or hybrid, enter the power the vehicle uses in kilowatts (kW)." +msgstr "" + +#: ../../content/applications/hr/fleet/models.rst:138 +msgid ":guilabel:`Horsepower`: enter the vehicle's horsepower in this field." +msgstr "" + +#: ../../content/applications/hr/fleet/models.rst:139 +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/models.rst:143 +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/models.rst:147 +msgid "Vendors tab" +msgstr "" + +#: ../../content/applications/hr/fleet/models.rst:149 +msgid "Specify the vendors a vehicle can be purchased from in this tab. With proper setup, requests for quotations for vehicles can be easily created through Odoo's *Purchase* app." +msgstr "" + +#: ../../content/applications/hr/fleet/models.rst:152 +msgid "To add a vendor, click :guilabel:`Add`, which opens an :guilabel:`Add: Vendors` pop-up window, with a list of all the vendors currently in the database. Add a vendor by ticking 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/models.rst:157 +msgid "If a vendor is not in the database, add a vendor by clicking :guilabel:`New` in the bottom-left of the :guilabel:`Add: Vendors` pop-up window. In the :guilabel:`Create Vendors` form that appears, enter the necessary information, then click :guilabel:`Save & Close` to add the vendor, or click :guilabel:`Save & New` to add the current vendor and create another new vendor." +msgstr "" + +#: ../../content/applications/hr/fleet/models.rst:-1 +msgid "Vendor form to fill out when adding a new vendor." +msgstr "" + +#: ../../content/applications/hr/fleet/models.rst:169 +msgid "Model category" +msgstr "" + +#: ../../content/applications/hr/fleet/models.rst:171 +msgid "To best organize a fleet, it is recommended to have vehicle models housed under a specific category, to 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/models.rst:175 +msgid "Odoo does **not** come with any models preconfigured; all models **must** be added." +msgstr "" + +#: ../../content/applications/hr/fleet/models.rst:177 +msgid "To view any models currently set up in the database, navigate to :menuselection:`Fleet app --> Configuration --> Models: Categories`. All models are displayed in a list view." +msgstr "" + +#: ../../content/applications/hr/fleet/models.rst:181 +msgid "Add a new model category" +msgstr "" + +#: ../../content/applications/hr/fleet/models.rst:183 +msgid "To add a new category, click the :guilabel:`New` button in the top-left corner of the :guilabel:`Categories` page. A new entry line appears at the bottom of the list. Type in the new category, then either click :guilabel:`Save`, or click anywhere on the screen, to save the entry." +msgstr "" + +#: ../../content/applications/hr/fleet/models.rst:187 +msgid "To reorganize how the categories appear in the list, click on the :icon:`oi-draggable` :guilabel:`(draggable)` icon to the left of any desired category name, and drag the line to the desired position." +msgstr "" + +#: ../../content/applications/hr/fleet/models.rst:191 +msgid "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/models.rst:-1 +msgid "List view of the models in the fleet." +msgstr "" + #: ../../content/applications/hr/fleet/new_vehicle.rst:3 msgid "New vehicles" msgstr "" @@ -3155,6 +3331,10 @@ msgstr "" msgid "Fiscality" msgstr "" +#: ../../content/applications/hr/fleet/new_vehicle.rst:290 +msgid ":guilabel:`Horsepower Taxation`: enter the amount that is taxed based on the size of the vehicle's engine. This is determined by local taxes and regulations, and varies depending on the location. It is recommended to check with the accounting department to ensure this value is correct." +msgstr "" + #: ../../content/applications/hr/fleet/new_vehicle.rst:295 msgid "Contract" msgstr "" @@ -3369,7 +3549,6 @@ msgid ":guilabel:`Job Position`: enter the vendor's job position in this field. msgstr "" #: ../../content/applications/hr/fleet/service.rst:148 -#: ../../content/applications/hr/lunch.rst:89 msgid ":guilabel:`Phone`: enter the vendor's phone number in this field." msgstr "" @@ -4311,199 +4490,22 @@ msgid "The translation text box, with the current language highlighted, and the msgstr "" #: ../../content/applications/hr/lunch.rst:56 -msgid "Vendors" -msgstr "" - -#: ../../content/applications/hr/lunch.rst:58 -msgid "Before food can be ordered, the restaurants that make the food, referred to as *vendors* in Odoo, **must** be configured." -msgstr "" - -#: ../../content/applications/hr/lunch.rst:61 -msgid "First navigate to :menuselection:`Lunch app --> Configuration: Vendors`, and all currently configured vendors for the *Lunch* app appear in a default Kanban view. To change to a list view, click the :guilabel:`≣ (four horizontal lines)` icon in the top-right corner." -msgstr "" - -#: ../../content/applications/hr/lunch.rst:65 -msgid "To add a new vendor, click the :guilabel:`New` button in the top-left corner, and a new lunch supplier form loads." -msgstr "" - -#: ../../content/applications/hr/lunch.rst:68 -msgid "Fill out the following fields on the form." -msgstr "" - -#: ../../content/applications/hr/lunch.rst:71 -msgid "Vendor information" -msgstr "" - -#: ../../content/applications/hr/lunch.rst:73 -msgid ":guilabel:`Vendor`: enter a name for the vendor." -msgstr "" - -#: ../../content/applications/hr/lunch.rst:74 -msgid ":guilabel:`Vendor`: select the vendor from the drop-down menu. If the vendor has not already been entered in the system, type in the vendor name and click either :guilabel:`Create \"vendor\"` to add them, or :guilabel:`Create and edit...` to create the vendor and edit the vendor form. The vendor form allows for more detail, aside from the name, to be entered, such as contact information." -msgstr "" - -#: ../../content/applications/hr/lunch.rst:80 -msgid "If a selection is made to the drop-down :guilabel:`Vendor` field, the text :guilabel:`Vendor` field (above the drop-down :guilabel:`Vendor` field) updates with the name of the vendor chosen from the drop-down menu." -msgstr "" - -#: ../../content/applications/hr/lunch.rst:84 -msgid "The list of vendors that is presented in the drop-down menu is pulled from the *Contacts* application." -msgstr "" - -#: ../../content/applications/hr/lunch.rst:87 -msgid ":guilabel:`Address`: enter the vendor's address in the various fields in this section." -msgstr "" - -#: ../../content/applications/hr/lunch.rst:88 -msgid ":guilabel:`Email`: enter the vendor's email in this field." -msgstr "" - -#: ../../content/applications/hr/lunch.rst:90 -msgid ":guilabel:`Company`: if this vendor is only available to a specific company, select the company from the drop-down menu. If this field is left blank, the vendor's items are available to **all** companies." -msgstr "" - -#: ../../content/applications/hr/lunch.rst:-1 -msgid "The top portion of the vendor form filled out." -msgstr "" - -#: ../../content/applications/hr/lunch.rst:101 -msgid "Availability" -msgstr "" - -#: ../../content/applications/hr/lunch.rst:103 -msgid "The :guilabel:`AVAILABILITY` section presents a table with two rows. The days of the week populate the top row, and the bottom row has checkboxes. Check the corresponding box for each day of the week the vendor is available." -msgstr "" - -#: ../../content/applications/hr/lunch.rst:107 -msgid "By default, Monday through Friday have checkmarks." -msgstr "" - -#: ../../content/applications/hr/lunch.rst:-1 -msgid "The default view of the availability section, with Mon-Fri enabled." -msgstr "" - -#: ../../content/applications/hr/lunch.rst:114 -#: ../../content/applications/hr/lunch/orders.rst:5 -msgid "Orders" -msgstr "" - -#: ../../content/applications/hr/lunch.rst:116 -msgid ":guilabel:`Delivery`: using the drop-down menu, select either :guilabel:`Delivery` if the vendor delivers food to the office, or :guilabel:`No Delivery` if ordered food must be picked up." -msgstr "" - -#: ../../content/applications/hr/lunch.rst:118 -msgid ":guilabel:`Location`: select which locations are able to order from this vendor. Multiple locations can be selected. If this field is left blank, **all** locations can order from the vendor." -msgstr "" - -#: ../../content/applications/hr/lunch.rst:123 -msgid "By default, an `HQ Office` location is created by default when creating a database, and is available to select from the list." -msgstr "" - -#: ../../content/applications/hr/lunch.rst:126 -msgid ":guilabel:`Send Order By`: click the radio button to select how orders are sent to the vendor. The available options are :guilabel:`Phone` or :guilabel:`Email`." -msgstr "" - -#: ../../content/applications/hr/lunch.rst:128 -msgid ":guilabel:`Order Time`: this field appears if :guilabel:`Email` is selected for :guilabel:`Send Order By`. Enter the time that an order must be emailed for the order to be accepted. Enter the time in a `HH:MM` format, then select either :guilabel:`AM` or :guilabel:`PM` from the drop-down next to the time field." -msgstr "" - -#: ../../content/applications/hr/lunch.rst:-1 -msgid "The orders section of a vendor form, with all fields filled out." -msgstr "" - -#: ../../content/applications/hr/lunch.rst:140 -msgid "Extras" -msgstr "" - -#: ../../content/applications/hr/lunch.rst:142 -msgid "When ordering an item in the *Lunch* app, it is possible to show extra items that can be added to an order, sometimes referred to as *add-ons*. These can be configured in any manner that suits the products being offered." -msgstr "" - -#: ../../content/applications/hr/lunch.rst:146 -msgid "By default, Odoo allows for three types of extra items, which can be thought of as *categories*. By default, the first type or *category* of add-ons is labeled `Extras`, the second is labeled `Beverages`, and the third is labeled `Extra Label 3`." -msgstr "" - -#: ../../content/applications/hr/lunch.rst:151 -msgid "When configuring the extras, it is important to keep in mind that all the extras configured will appear for **every item** offered by the vendor. That means that only items which apply to **all** products from the vendor should be added." -msgstr "" - -#: ../../content/applications/hr/lunch.rst:158 -msgid "Configure extras" -msgstr "" - -#: ../../content/applications/hr/lunch.rst:160 -msgid "Enter the following information for each of the three available extra sections:" -msgstr "" - -#: ../../content/applications/hr/lunch.rst:162 -msgid ":guilabel:`Extra (#) Label`: enter a name for the type of extra, such as `Toppings` or `Beverages`. This can be thought of as a *category*." -msgstr "" - -#: ../../content/applications/hr/lunch.rst:164 -msgid ":guilabel:`Extra (#) Quantity`: select how the extras are allowed to be selected. The options are:" -msgstr "" - -#: ../../content/applications/hr/lunch.rst:166 -msgid ":guilabel:`None or More`: select this if the user is not required to select anything." -msgstr "" - -#: ../../content/applications/hr/lunch.rst:167 -msgid ":guilabel:`One or More`: select this to **require** the user to make at least one selection." -msgstr "" - -#: ../../content/applications/hr/lunch.rst:168 -msgid ":guilabel:`Only One`: select this to **require** the user to make only one selection." -msgstr "" - -#: ../../content/applications/hr/lunch.rst:171 -msgid "Add extras" -msgstr "" - -#: ../../content/applications/hr/lunch.rst:173 -msgid "After the labels and quantities have been configured for an extra category, the individual extra items must be added for each category." -msgstr "" - -#: ../../content/applications/hr/lunch.rst:176 -msgid "Click :guilabel:`Add a line` at the bottom of the list that appears on the right-hand side of the extra category. Enter the :guilabel:`Name` and :guilabel:`Price` for each item being added. The price can remain at `$0.00` if there is no cost. This is common for items like disposable silverware or condiments." -msgstr "" - -#: ../../content/applications/hr/lunch.rst:182 -msgid "For a pizzeria that only offers personal pies, see their extras configured as follows:" -msgstr "" - -#: ../../content/applications/hr/lunch.rst:184 -msgid "The first extra is configured for the various toppings they offer. The :guilabel:`Extra 1 Label` is set to `Toppings`, and the :guilabel:`Extra 1 Quantity` is set to :guilabel:`None or More`. The various toppings are then added, with their corresponding costs." -msgstr "" - -#: ../../content/applications/hr/lunch.rst:0 -msgid "The first of the extras configured for pizza toppings." -msgstr "" - -#: ../../content/applications/hr/lunch.rst:192 -msgid "The pizzeria also offers a free beverage with any purchase. To set this up, the :guilabel:`Extra 2 Label` is set to `Beverages`, and the :guilabel:`Extra 1 Quantity` is set to :guilabel:`Only One`. The various beverage choices are added, and the cost for each remains zero." -msgstr "" - -#: ../../content/applications/hr/lunch.rst:0 -msgid "The second of the extras configured for a free beverage with purchase." -msgstr "" - -#: ../../content/applications/hr/lunch.rst:201 msgid "Locations" msgstr "" -#: ../../content/applications/hr/lunch.rst:203 +#: ../../content/applications/hr/lunch.rst:58 msgid "By default, Odoo creates an `HQ Office` location when the *Lunch* application is installed. If a company has more than one location, they must be configured." msgstr "" -#: ../../content/applications/hr/lunch.rst:206 +#: ../../content/applications/hr/lunch.rst:61 msgid "To add a location, navigate to :menuselection:`Lunch app --> Configuration: Locations`. The currently configured locations appear in a list view. Click the :guilabel:`New` button in the top-left corner and a blank line appears beneath the last location in the list." msgstr "" -#: ../../content/applications/hr/lunch.rst:210 +#: ../../content/applications/hr/lunch.rst:65 msgid "Enter the name of the location in the field. Next, click into the :guilabel:`Address` field to the right of the name, and enter the location's address. It is possible to enter multiple lines in the address field." msgstr "" -#: ../../content/applications/hr/lunch.rst:214 +#: ../../content/applications/hr/lunch.rst:69 msgid "Repeat this for all locations that need to be added." msgstr "" @@ -4511,52 +4513,52 @@ msgstr "" msgid "A list view of the locations with the new button highlighted." msgstr "" -#: ../../content/applications/hr/lunch.rst:221 +#: ../../content/applications/hr/lunch.rst:76 #: ../../content/applications/hr/referrals/alerts.rst:3 msgid "Alerts" msgstr "" -#: ../../content/applications/hr/lunch.rst:223 +#: ../../content/applications/hr/lunch.rst:78 msgid "It is possible to set up alerts that can either be displayed in the *Lunch* app, or be sent to specific employees via the *Discuss* app." msgstr "" -#: ../../content/applications/hr/lunch.rst:226 +#: ../../content/applications/hr/lunch.rst:81 msgid "No alerts are pre-configured by default. To set up an alert, navigate to :menuselection:`Lunch app --> Configuration: Alerts`. Click the :guilabel:`New` button in the top-left corner and a blank lunch alert form loads. Enter the following information on the form:" msgstr "" -#: ../../content/applications/hr/lunch.rst:230 +#: ../../content/applications/hr/lunch.rst:85 msgid ":guilabel:`Alert Name`: enter a name for the alert. This should be short and descriptive, such as `New Lunch Vendor` or `Order by 11`. This field is **required**." msgstr "" -#: ../../content/applications/hr/lunch.rst:232 +#: ../../content/applications/hr/lunch.rst:87 msgid ":guilabel:`Display`: select whether the alert is visible in the *Lunch* app (:guilabel:`Alert in app)` or sent to employees via the *Discuss* app in a chat window (:guilabel:`Chat notification`)." msgstr "" -#: ../../content/applications/hr/lunch.rst:235 +#: ../../content/applications/hr/lunch.rst:90 msgid ":guilabel:`Recipients`: this field only appears if :guilabel:`Chat notification` is selected for the :guilabel:`Display` option. Select who receives the chat alert. The options are: :guilabel:`Everyone`, :guilabel:`Employee who ordered last week`, :guilabel:`Employee who ordered last month`, or :guilabel:`Employee who ordered last year`." msgstr "" -#: ../../content/applications/hr/lunch.rst:240 +#: ../../content/applications/hr/lunch.rst:95 msgid ":guilabel:`Location`: select the locations the alert should appear for from the drop-down menu. Multiple locations can be selected. This field is **required**, therefore, if the alert applies to all locations, select all the locations from the drop-down menu." msgstr "" -#: ../../content/applications/hr/lunch.rst:243 +#: ../../content/applications/hr/lunch.rst:98 msgid ":guilabel:`Show Until`: if the alert should expire on a specific date, select the date from the calendar picker." msgstr "" -#: ../../content/applications/hr/lunch.rst:245 +#: ../../content/applications/hr/lunch.rst:100 msgid ":guilabel:`Active`: this option is on (appears green) by default. To turn off the alert, click the toggle so that it no longer appears green." msgstr "" -#: ../../content/applications/hr/lunch.rst:247 +#: ../../content/applications/hr/lunch.rst:102 msgid ":guilabel:`Message`: Enter the alert message in this field. This field is **required**." msgstr "" -#: ../../content/applications/hr/lunch.rst:248 +#: ../../content/applications/hr/lunch.rst:103 msgid ":guilabel:`Notification Time`: select the days of the week the alert should be sent. By default, all seven days are active. Click on a checkbox to change the setting from active to inactive." msgstr "" -#: ../../content/applications/hr/lunch.rst:251 +#: ../../content/applications/hr/lunch.rst:106 msgid "If :guilabel:`Chat notification` was selected for the :guilabel:`Display` option, a :guilabel:`Time` field also appears. Enter the time the chat message should be sent. Next, select if the time is either :guilabel:`AM` or :guilabel:`PM` using the drop-down menu to the right of the :guilabel:`Time` field." msgstr "" @@ -4565,19 +4567,23 @@ msgid "An alert form with all of the information filled out for a chat alert sen "asking employees to submit orders by 11:30 AM." msgstr "" -#: ../../content/applications/hr/lunch.rst:262 +#: ../../content/applications/hr/lunch.rst:117 +msgid ":doc:`lunch/vendors`" +msgstr "" + +#: ../../content/applications/hr/lunch.rst:118 msgid ":doc:`lunch/products`" msgstr "" -#: ../../content/applications/hr/lunch.rst:263 +#: ../../content/applications/hr/lunch.rst:119 msgid ":doc:`lunch/orders`" msgstr "" -#: ../../content/applications/hr/lunch.rst:264 +#: ../../content/applications/hr/lunch.rst:120 msgid ":doc:`lunch/user-accounts`" msgstr "" -#: ../../content/applications/hr/lunch.rst:265 +#: ../../content/applications/hr/lunch.rst:121 msgid ":doc:`lunch/management`" msgstr "" @@ -4813,6 +4819,11 @@ msgstr "" msgid ":doc:`user-accounts`" msgstr "" +#: ../../content/applications/hr/lunch/orders.rst:5 +#: ../../content/applications/hr/lunch/vendors.rst:76 +msgid "Orders" +msgstr "" + #: ../../content/applications/hr/lunch/orders.rst:7 msgid "When the *Lunch* application is opened, the :guilabel:`Order Your Lunch` dashboard loads. This view is also accessed by navigating to :menuselection:`Lunch app --> My Lunch --> New Order`." msgstr "" @@ -5263,6 +5274,206 @@ msgstr "" msgid "It is **not** possible to modify any product-related records." msgstr "" +#: ../../content/applications/hr/lunch/vendors.rst:3 +msgid "Vendors" +msgstr "" + +#: ../../content/applications/hr/lunch/vendors.rst:5 +msgid "Before :doc:`products can be added ` to the *Lunch* app, the restaurants that provide the food **must** be configured." +msgstr "" + +#: ../../content/applications/hr/lunch/vendors.rst:8 +msgid "To add a new vendor, first navigate to :menuselection:`Lunch app --> Configuration --> Vendors`. Here, all currently configured vendors for the *Lunch* app appear in a default Kanban view. To change to a list view, click the :icon:`oi-view-list` :guilabel:`(list)` icon in the top-right corner." +msgstr "" + +#: ../../content/applications/hr/lunch/vendors.rst:14 +msgid "No vendors are preconfigured in the *Lunch* app, so all vendors **must** be added to the database." +msgstr "" + +#: ../../content/applications/hr/lunch/vendors.rst:17 +msgid "To add a new vendor, click the :guilabel:`New` button in the top-left corner, and a new lunch supplier form loads." +msgstr "" + +#: ../../content/applications/hr/lunch/vendors.rst:20 +msgid "Fill out the following fields on the vendor form:" +msgstr "" + +#: ../../content/applications/hr/lunch/vendors.rst:22 +msgid ":ref:`Vendor information `" +msgstr "" + +#: ../../content/applications/hr/lunch/vendors.rst:23 +msgid ":ref:`Availability `" +msgstr "" + +#: ../../content/applications/hr/lunch/vendors.rst:24 +msgid ":ref:`Orders `" +msgstr "" + +#: ../../content/applications/hr/lunch/vendors.rst:25 +msgid ":ref:`Extras `" +msgstr "" + +#: ../../content/applications/hr/lunch/vendors.rst:30 +msgid "Vendor information" +msgstr "" + +#: ../../content/applications/hr/lunch/vendors.rst:32 +msgid ":guilabel:`Vendor`: enter a name for the vendor." +msgstr "" + +#: ../../content/applications/hr/lunch/vendors.rst:33 +msgid ":guilabel:`Vendor` (beneath the line for vendor name): select the vendor from the drop-down menu. If the vendor has not already been entered in the system, type in the vendor name, and click either :guilabel:`Create \"new vendor name\"` to add them. Alternatively, click :guilabel:`Create and edit...` to create the vendor, and edit the vendor form. The vendor form allows for more detail, aside from the name, to be entered, such as contact information." +msgstr "" + +#: ../../content/applications/hr/lunch/vendors.rst:40 +msgid "If a selection is made to the drop-down :guilabel:`Vendor` field, the :guilabel:`Vendor` text field (above, for the vendor's name) updates with the name of the vendor chosen from the drop-down menu." +msgstr "" + +#: ../../content/applications/hr/lunch/vendors.rst:44 +msgid "The list of vendors that is presented in the drop-down menu is pulled from the *Contacts* application." +msgstr "" + +#: ../../content/applications/hr/lunch/vendors.rst:47 +msgid ":guilabel:`Address`: enter the vendor's address in the various fields." +msgstr "" + +#: ../../content/applications/hr/lunch/vendors.rst:48 +msgid ":guilabel:`Email`: enter the vendor's email." +msgstr "" + +#: ../../content/applications/hr/lunch/vendors.rst:49 +msgid ":guilabel:`Phone`: enter the vendor's phone number." +msgstr "" + +#: ../../content/applications/hr/lunch/vendors.rst:50 +msgid ":guilabel:`Company`: if this vendor is only available to a specific company, select the company from the drop-down menu. If this field is left blank, the vendor's items are available to **all** companies." +msgstr "" + +#: ../../content/applications/hr/lunch/vendors.rst:-1 +msgid "The top portion of the vendor form filled out." +msgstr "" + +#: ../../content/applications/hr/lunch/vendors.rst:61 +msgid "Availability" +msgstr "" + +#: ../../content/applications/hr/lunch/vendors.rst:63 +msgid "The :guilabel:`AVAILABILITY` section presents a table with two rows. The days of the week populate the top row, and the bottom row has checkboxes. Tick the corresponding checkbox for each day of the week the vendor is available." +msgstr "" + +#: ../../content/applications/hr/lunch/vendors.rst:67 +msgid "By default, Monday through Friday are ticked." +msgstr "" + +#: ../../content/applications/hr/lunch/vendors.rst:-1 +msgid "The default view of the availability section, with Mon-Fri enabled." +msgstr "" + +#: ../../content/applications/hr/lunch/vendors.rst:78 +msgid "The :guilabel:`ORDERS` section of the vendor form details which locations the vendor is available for, in addition to how and when orders are placed and received." +msgstr "" + +#: ../../content/applications/hr/lunch/vendors.rst:81 +msgid ":guilabel:`Delivery`: using the drop-down menu, select :guilabel:`Delivery` if the vendor delivers to the office, or select :guilabel:`No Delivery` if orders must be picked up." +msgstr "" + +#: ../../content/applications/hr/lunch/vendors.rst:83 +msgid ":guilabel:`Location`: select which locations are able to order from this vendor. Multiple locations can be selected. If this field is left blank, **all** locations can order from the vendor." +msgstr "" + +#: ../../content/applications/hr/lunch/vendors.rst:88 +msgid "An `HQ Office` location is created by default when creating a database, and is available to select from the list." +msgstr "" + +#: ../../content/applications/hr/lunch/vendors.rst:91 +msgid ":guilabel:`Send Order By`: click the radio button to select how orders are sent to the vendor. The available options are :guilabel:`Phone` or :guilabel:`Email`." +msgstr "" + +#: ../../content/applications/hr/lunch/vendors.rst:93 +msgid ":guilabel:`Order Time`: this field **only** appears if :guilabel:`Email` is selected in the :guilabel:`Send Order By` field. Enter the time that an order must be emailed for it to be accepted. Enter the time in the following format: `HH:MM`. Then select either :guilabel:`AM` or :guilabel:`PM` from the drop-down menu, next to the time field." +msgstr "" + +#: ../../content/applications/hr/lunch/vendors.rst:-1 +msgid "The orders section of a vendor form, with all fields filled out." +msgstr "" + +#: ../../content/applications/hr/lunch/vendors.rst:105 +msgid "Extras" +msgstr "" + +#: ../../content/applications/hr/lunch/vendors.rst:107 +msgid "When ordering an item in the *Lunch* app, optional extra items, sometimes referred to as *add-ons*, can be shown. These can be configured in any manner that suits the products being offered." +msgstr "" + +#: ../../content/applications/hr/lunch/vendors.rst:110 +msgid "By default, Odoo allows for three types of extra items, which can be thought of as *categories*. By default, the first type (or *category*) of add-ons is labeled `Extras`, the second is labeled `Beverages`, and the third is labeled `Extra Label 3`." +msgstr "" + +#: ../../content/applications/hr/lunch/vendors.rst:115 +msgid "When configuring the extras, it is important to keep in mind that all the extras configured appear for **every item** offered by the vendor. That means that only items which apply to **all** products from the vendor should be added." +msgstr "" + +#: ../../content/applications/hr/lunch/vendors.rst:122 +msgid "Configure extras" +msgstr "" + +#: ../../content/applications/hr/lunch/vendors.rst:124 +msgid "Enter the following information for each of the three available extra sections:" +msgstr "" + +#: ../../content/applications/hr/lunch/vendors.rst:126 +msgid ":guilabel:`Extra (#) Label`: enter a name for the type of extra, such as `Toppings`. This can be thought of as a *category*." +msgstr "" + +#: ../../content/applications/hr/lunch/vendors.rst:128 +msgid ":guilabel:`Extra (#) Quantity`: select how the extras are selected. The options are:" +msgstr "" + +#: ../../content/applications/hr/lunch/vendors.rst:130 +msgid ":guilabel:`None or More`: select this if the user is not required to make a selection." +msgstr "" + +#: ../../content/applications/hr/lunch/vendors.rst:131 +msgid ":guilabel:`One or More`: select this to **require** the user to make **at least one** selection." +msgstr "" + +#: ../../content/applications/hr/lunch/vendors.rst:132 +msgid ":guilabel:`Only One`: select this to **require** the user to **make only one** selection." +msgstr "" + +#: ../../content/applications/hr/lunch/vendors.rst:135 +msgid "Add extras" +msgstr "" + +#: ../../content/applications/hr/lunch/vendors.rst:137 +msgid "After the labels and quantities have been configured for an extra category, the individual extra items must be added for each category." +msgstr "" + +#: ../../content/applications/hr/lunch/vendors.rst:140 +msgid "Click :guilabel:`Add a line` at the bottom of the list that appears on the right-hand side of the extra category. Enter the :guilabel:`Name` and :guilabel:`Price` for each item being added. The price can remain at `$0.00` if there is no cost. This is common for items like disposable silverware or condiments." +msgstr "" + +#: ../../content/applications/hr/lunch/vendors.rst:146 +msgid "For a pizzeria that only offers personal pizzas, see their extras configured as follows:" +msgstr "" + +#: ../../content/applications/hr/lunch/vendors.rst:148 +msgid "The first extra is configured for the various toppings they offer. The :guilabel:`Extra 1 Label` is set to `Toppings`, and the :guilabel:`Extra 1 Quantity` is set to :guilabel:`None or More`. The various toppings are then added, with their corresponding costs." +msgstr "" + +#: ../../content/applications/hr/lunch/vendors.rst:0 +msgid "The first of the extras configured for pizza toppings." +msgstr "" + +#: ../../content/applications/hr/lunch/vendors.rst:156 +msgid "The pizzeria also offers a free beverage with any purchase. To set this up, the :guilabel:`Extra 2 Label` is set to `Beverages`, and the :guilabel:`Extra 1 Quantity` is set to :guilabel:`Only One`. The various beverage choices are added, and the cost for each remains zero." +msgstr "" + +#: ../../content/applications/hr/lunch/vendors.rst:0 +msgid "The second of the extras configured for a free beverage with purchase." +msgstr "" + #: ../../content/applications/hr/payroll.rst:5 #: ../../content/applications/hr/payroll.rst:81 #: ../../content/applications/hr/payroll/reporting.rst:31 @@ -5741,6 +5952,10 @@ msgstr "" msgid "New working schedule form." msgstr "" +#: ../../content/applications/hr/payroll.rst:398 +msgid "Salary" +msgstr "" + #: ../../content/applications/hr/payroll.rst:403 msgid "Structure types" msgstr "" @@ -8355,11 +8570,11 @@ msgid ":ref:`Second Interview `" msgstr "" #: ../../content/applications/hr/recruitment.rst:194 -msgid ":ref:`Contract Proposal `" +msgid ":doc:`Contract Proposal `" msgstr "" #: ../../content/applications/hr/recruitment.rst:195 -msgid ":ref:`Contract Signed `" +msgid ":ref:`Contract Signed `" msgstr "" #: ../../content/applications/hr/recruitment.rst:197 @@ -8419,6 +8634,7 @@ msgid "The plus sign to click to add a new column to the Kanban stages." msgstr "" #: ../../content/applications/hr/recruitment.rst:249 +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:223 msgid "Modify stage" msgstr "" @@ -8641,7 +8857,6 @@ msgid "Email templates use dynamic placeholders to personalize the email to the msgstr "" #: ../../content/applications/hr/recruitment.rst:471 -#: ../../content/applications/hr/recruitment.rst:802 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 "" @@ -8687,343 +8902,43 @@ msgid "An applicant's card moves from one stage to another by using the click an msgstr "" #: ../../content/applications/hr/recruitment.rst:521 -msgid "The :guilabel:`First Interview` stage can be modified so when the applicant's card moves to the :guilabel:`First Interview` stage, an email is automatically sent to the applicant stating an interview is requested. In this pre-configured email template, a link to the recruiting team's calendar appears, allowing the applicant to schedule their interview." +msgid "The :guilabel:`First Interview` stage can be modified, so when the applicant's card moves to the :guilabel:`First Interview` stage, an email is automatically sent to the applicant, stating an interview is requested, and :ref:`requests the applicant to schedule their interview `." msgstr "" #: ../../content/applications/hr/recruitment.rst:526 msgid ":ref:`Edit ` the :guilabel:`First Interview` stage, and select the :guilabel:`Recruitment: Schedule Interview` for the :guilabel:`Email Template` field, to automate this action." msgstr "" -#: ../../content/applications/hr/recruitment.rst:535 -msgid "An interview can be scheduled in one of two ways: either manually by the recruitment team, or by the applicant themselves." -msgstr "" - -#: ../../content/applications/hr/recruitment.rst:538 -msgid "If the :guilabel:`First Interview` stage was modified to send the :guilabel:`Recruitment: Schedule Interview` email template when an applicant reaches that stage, the applicant received a link to the recruitment team's calendar, and can schedule the interview on their own. The recruitment team's availability is reflected in the calendar." -msgstr "" - -#: ../../content/applications/hr/recruitment.rst:543 -msgid "If the interview needs to be scheduled by the recruitment team, they should reach out to the applicant for a date and time that works. 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:550 -msgid "The meeting smart button displays :guilabel:`No Meeting` if no meetings are currently scheduled. For new applicants who are new to the :guilabel:`First Interview` stage, this is the default." -msgstr "" - -#: ../../content/applications/hr/recruitment.rst:553 -msgid "If there is one meeting already scheduled, the smart button displays :guilabel:`1 Meeting`, with the date of the upcoming meeting beneath it. If more than one meeting is scheduled, the button displays :guilabel:`Next Meeting`, with the date of the first upcoming meeting beneath it." -msgstr "" - -#: ../../content/applications/hr/recruitment.rst:557 -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 are visible on the calendar." -msgstr "" - -#: ../../content/applications/hr/recruitment.rst:563 -msgid "The default view is the :guilabel:`Week` view. To change the calendar view, click the :guilabel:`Week` button, then select the desired view from the drop-down menu. The other options are either :guilabel:`Day`, :guilabel:`Month`, or :guilabel:`Year`." -msgstr "" - -#: ../../content/applications/hr/recruitment.rst:567 -msgid "An option to display or hide weekends is available. Click the :guilabel:`Week` button, then click :guilabel:`Show weekends` to deactivate it (the default is to show weekends). If a check mark is next to :guilabel:`Show weekends`, weekends are visible. If there is no check mark, weekends are hidden." -msgstr "" - -#: ../../content/applications/hr/recruitment.rst:572 -msgid "To change the displayed date range for the calendar, either use the :icon:`fa-arrow-left` :guilabel:`(left arrow)`, :icon:`fa-arrow-right` :guilabel:`(Right arrow)`, 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:581 -msgid "To add a meeting to the calendar when in the day or week view, 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. A meeting can also be added in this view by clicking on the day *and* the time slot the meeting is to take place." -msgstr "" - -#: ../../content/applications/hr/recruitment.rst:586 -msgid "Both methods cause a :ref:`New Event ` pop up window to appear." -msgstr "" - -#: ../../content/applications/hr/recruitment.rst:591 -msgid "New event pop-up window" -msgstr "" - -#: ../../content/applications/hr/recruitment.rst:593 -msgid "Enter the information on the form. The only required fields to enter are the :guilabel:`Meeting Title`, and the :guilabel:`Start` and :guilabel:`End` fields. Once the card details are entered, click :guilabel:`Save & Close` to save the changes and create the interview." -msgstr "" - -#: ../../content/applications/hr/recruitment.rst:597 -msgid "The fields available to populate or modify on the :guilabel:`New Event` card are as follows:" -msgstr "" - -#: ../../content/applications/hr/recruitment.rst:599 -msgid ":guilabel:`Meeting Title`: 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:602 -msgid ":guilabel:`Start` and :guilabel:`End`: select the start and end date and times for the meeting. Click on one of the fields and a calendar pop-up window appears. Select both the start and end date and times, then click :guilabel:`Apply`." -msgstr "" - -#: ../../content/applications/hr/recruitment.rst:605 -msgid ":guilabel:`All Day`: if the meeting is an all-day interview, check the box. If this box is checked, the :guilabel:`Start` and :guilabel:`End` fields are hidden from view." -msgstr "" - -#: ../../content/applications/hr/recruitment.rst:607 -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:609 -msgid ":guilabel:`Videocall URL`: if the meeting is virtual, or if there is a virtual option available, click :guilabel:`+ Odoo meeting` and a URL is automatically created for the meeting and populates the field." -msgstr "" - -#: ../../content/applications/hr/recruitment.rst:612 -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:620 -msgid "More options" -msgstr "" - -#: ../../content/applications/hr/recruitment.rst:622 -msgid "To add additional information to the meeting, click the :guilabel:`More Options` button in the lower-right corner of the pop-up window. Enter any of the following additional fields:" -msgstr "" - -#: ../../content/applications/hr/recruitment.rst:625 -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. The default length of a meeting is one hour." -msgstr "" - -#: ../../content/applications/hr/recruitment.rst:628 -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`. Several additional fields appear when this is enabled:" -msgstr "" - -#: ../../content/applications/hr/recruitment.rst:632 -msgid ":guilabel:`Timezone`: using the drop-down menu, select the :guilabel:`Timezone` for the meetings." -msgstr "" - -#: ../../content/applications/hr/recruitment.rst:634 -msgid ":guilabel:`Repeat`: using the drop-down menu, select when the meetings repeat. The available options are :guilabel:`Daily`, :guilabel:`Weekly`, :guilabel:`Monthly`, :guilabel:`Yearly`, or :guilabel:`Custom`. If :guilabel:`Custom` is selected, a :guilabel:`Repeat Every` field appears beneath it, along with another time frequency parameter (:guilabel:`Days`, :guilabel:`Weeks`, :guilabel:`Months`, or :guilabel:`Years`). Enter a number in the blank field, then select the time period using the drop-down menu." -msgstr "" - -#: ../../content/applications/hr/recruitment.rst:640 -msgid ":guilabel:`Repeat on`: if :guilabel:`Weekly` is selected for the :guilabel:`Repeat` field, the :guilabel:`Repeat on` field appears. Click on the corresponding day to select it." -msgstr "" - -#: ../../content/applications/hr/recruitment.rst:642 -msgid ":guilabel:`Day of Month`: if :guilabel:`Monthly` is selected for the :guilabel:`Repeat` field, the :guilabel:`Day of Month` field appears. Using the drop-down menu, select either :guilabel:`Date of month` or :guilabel:`Day of month`. If :guilabel:`Date of month` is selected, enter the date the meeting repeats. If :guilabel:`Day of month` is selected, use the drop-down menus to determine the frequency. Select either :guilabel:`First`, :guilabel:`Second`, :guilabel:`Third`, :guilabel:`Fourth`, or :guilabel:`Last` for the first drop-down menu, then select the day (:guilabel:`Monday`, :guilabel:`Tuesday`, etc.) in the second drop-down menu." -msgstr "" - -#: ../../content/applications/hr/recruitment.rst:649 -msgid ":guilabel:`Until`: using the drop-down menu, select when the meetings stop repeating. The available options are :guilabel:`Number of repetitions`, :guilabel:`End date`, and :guilabel:`Forever`. If :guilabel:`Number of repetitions` is selected, enter the number of total meetings to occur in the blank field. If :guilabel:`End date` is selected, specify the date using the calendar pop-up window, or type in a date in a XX/XX/XXXX format. :guilabel:`Forever` schedules meetings indefinitely." -msgstr "" - -#: ../../content/applications/hr/recruitment.rst:656 -msgid ":guilabel:`Location`: enter the location for the meeting." -msgstr "" - -#: ../../content/applications/hr/recruitment.rst:657 -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:659 -msgid ":guilabel:`Appointment`: if an appointment is associated with this meeting, select it form the drop-down menu, or create a new appointment by typing in the appointment name, then click :guilabel:`Create & Edit...`. A :guilabel:`Create Appointment` form loads. Enter the information on the form, then click :guilabel:`Save & Close`." -msgstr "" - -#: ../../content/applications/hr/recruitment.rst:663 -msgid ":guilabel:`Privacy`: select if the organizer appears either :guilabel:`Available` or :guilabel:`Busy` for the duration of the meeting, using the drop-down menu. Next, select the visibility of this meeting, using the drop-down menu to the right of the first selection. 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:670 -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:672 -msgid ":guilabel:`Reminders`: select a reminder from the drop-down menu. Default 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 alerts the meeting participants of the meeting via the selected option at the specified time. Multiple reminders can be selected in this field." -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:683 -msgid "Send meeting to attendees" -msgstr "" - -#: ../../content/applications/hr/recruitment.rst:685 -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 from the expanded :guilabel:`Event Form` (what is seen when the :guilabel:`More Options` button is clicked on in the event pop-up window)." -msgstr "" - -#: ../../content/applications/hr/recruitment.rst:689 -msgid "To send the meeting via email, click the :icon:`fa-envelope` :guilabel:`Email` button next to the list of attendees. A :guilabel:`Contact Attendees` email configurator pop-up window 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:`Attachments` 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:702 -msgid "To send the meeting via text message, click the :icon:`fa-mobile` :guilabel:`SMS` button next to the list of attendees. A :guilabel:`Send SMS Text Message` pop-up appears." -msgstr "" - -#: ../../content/applications/hr/recruitment.rst:705 -msgid "At the top, a blue box appears if any attendees do not have valid mobile numbers, and lists how many records are invalid. If a contact does not have a valid mobile number listed, click :guilabel:`Close`, and edit the attendee's record, then redo these steps." -msgstr "" - -#: ../../content/applications/hr/recruitment.rst:709 -msgid "When no warning message appears, type in the message to be sent to the attendees in the :guilabel:`Message` field. to add any emojis to the message, click the :guilabel:`Add Emoji` icon on the right-side of the pop-up window." -msgstr "" - -#: ../../content/applications/hr/recruitment.rst:713 -msgid "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:723 -msgid "Sending text messages is not a default capability with Odoo. To send text messages, credits are required, which need to be purchased. For more information on IAP credits and plans, refer to the :doc:`../essentials/in_app_purchase` documentation." -msgstr "" - -#: ../../content/applications/hr/recruitment.rst:730 +#: ../../content/applications/hr/recruitment.rst:533 msgid "Second interview" msgstr "" -#: ../../content/applications/hr/recruitment.rst:732 +#: ../../content/applications/hr/recruitment.rst:535 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:737 -msgid "When the applicant's card moves to the :guilabel:`Second Interview` stage, there are no automatic activities or emails configured for this stage. The recruiter can now :ref:`schedule a second interview ` with the applicant, following the same process as the first interview." +#: ../../content/applications/hr/recruitment.rst:540 +msgid "When the applicant's card moves to the :guilabel:`Second Interview` stage, there are no automatic activities or emails configured. The recruiter can now :doc:`schedule a second interview ` with the applicant, following the same process as the first interview." msgstr "" -#: ../../content/applications/hr/recruitment.rst:745 -msgid "Contract proposal" +#: ../../content/applications/hr/recruitment.rst:546 +msgid "recruitment/new_job" msgstr "" -#: ../../content/applications/hr/recruitment.rst:747 -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." +#: ../../content/applications/hr/recruitment.rst:547 +msgid "recruitment/add-new-applicants" msgstr "" -#: ../../content/applications/hr/recruitment.rst:752 -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. Most fields are pre-populated with information from the job position. If any necessary fields are blank, enter the relevant information in the fields." +#: ../../content/applications/hr/recruitment.rst:548 +msgid "recruitment/schedule_interviews" msgstr "" -#: ../../content/applications/hr/recruitment.rst:758 -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, any fields related to vehicles do not appear on the pop-up window." +#: ../../content/applications/hr/recruitment.rst:549 +msgid "recruitment/offer_job_positions" msgstr "" -#: ../../content/applications/hr/recruitment.rst:764 -msgid "Universal fields" -msgstr "" - -#: ../../content/applications/hr/recruitment.rst:766 -msgid "The following fields appear for all offers sent to applicants regardless of localization settings." -msgstr "" - -#: ../../content/applications/hr/recruitment.rst:768 -msgid ":guilabel:`Contract Template`: the template currently being used to populate the :guilabel:`Generate a Simulation Link` pop-up window. To modify the template, click the :guilabel:`Internal link` icon to the right of the drop-down arrow. Make any changes, then click :guilabel:`Save & Close`. A different :guilabel:`Contract Template` can be selected using the drop-down menu." -msgstr "" - -#: ../../content/applications/hr/recruitment.rst:773 -msgid ":guilabel:`Job Position`: the name of the :guilabel:`Job Position` being offered to the applicant. The selections available in the drop-down menu correspond to the :guilabel:`Job Positions` configured on the main *Recruitment* dashboard." -msgstr "" - -#: ../../content/applications/hr/recruitment.rst:776 -msgid ":guilabel:`Job Title`: the specific name of the position being offered to the applicant." -msgstr "" - -#: ../../content/applications/hr/recruitment.rst:777 -msgid ":guilabel:`Department`: the :guilabel:`Department` the job position falls under." -msgstr "" - -#: ../../content/applications/hr/recruitment.rst:778 -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:782 -msgid ":guilabel:`Yearly Cost`: the annual salary being offered." -msgstr "" - -#: ../../content/applications/hr/recruitment.rst:783 -msgid ":guilabel:`Link Expiration Date`: job offers are only valid for a specific period of time. The default expiration date is 30 days. Modify the expiration date, if desired." -msgstr "" - -#: ../../content/applications/hr/recruitment.rst:787 -msgid "Send offer" -msgstr "" - -#: ../../content/applications/hr/recruitment.rst:789 -msgid "When the information is all updated, click :guilabel:`Send By Email` to send the offer to the applicant." -msgstr "" - -#: ../../content/applications/hr/recruitment.rst:792 -msgid "If the applicant does not have an email address listed on their applicant card, a warning appears in a red box at the bottom of the :guilabel:`Generate a Simulation Link` pop-up window, stating :guilabel:`The applicant does not have a valid email set. The Offer Link won't be able to be completed.` Click :guilabel:`Discard`, enter an email on the applicant's card, then click the :guilabel:`Generate Offer` button again." -msgstr "" - -#: ../../content/applications/hr/recruitment.rst:798 -msgid "An email pop-up window loads. The default :guilabel:`Recruitment: Your Salary Package` email template is used, and the :guilabel:`Recipients`, :guilabel:`Subject`, and email body are pre-populated based on the email template." -msgstr "" - -#: ../../content/applications/hr/recruitment.rst:806 -msgid "Once the email is ready to send, click :guilabel:`Send`." -msgstr "" - -#: ../../content/applications/hr/recruitment.rst:809 -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:817 -msgid "Configure your package" -msgstr "" - -#: ../../content/applications/hr/recruitment.rst:819 -msgid "The email template includes a :guilabel:`Configure your package` button. This link takes the applicant to a webpage where they can modify the proposed salary package, and enter their personal information." -msgstr "" - -#: ../../content/applications/hr/recruitment.rst:823 -msgid "Once the applicant is hired, the personal information entered on the webpage is imported to their employee record, when created." -msgstr "" - -#: ../../content/applications/hr/recruitment.rst:826 -msgid "If applicable, the applicant can modify their salary package. This option is not available for all localizations. Depending on where the company is located, this option may not be available." -msgstr "" - -#: ../../content/applications/hr/recruitment.rst:829 -msgid "Once all the information is completed, the applicant accepts the offer by clicking the :guilabel:`Review Contract & Sign` button to accept the contract and sign it using the *Sign* application." -msgstr "" - -#: ../../content/applications/hr/recruitment.rst:836 -msgid "Contract signed" -msgstr "" - -#: ../../content/applications/hr/recruitment.rst:838 -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:845 -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:848 -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:856 -msgid "Create employee" -msgstr "" - -#: ../../content/applications/hr/recruitment.rst:858 -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:863 -msgid "Fill out the rest of the form. For detailed information on the fields, refer to the :doc:`employees/new_employee` documentation. When done, the employee record is saved in the *Employees* app." +#: ../../content/applications/hr/recruitment.rst:550 +msgid "recruitment/refuse_applicant" msgstr "" #: ../../content/applications/hr/recruitment/add-new-applicants.rst:3 @@ -9395,6 +9310,190 @@ msgstr "" msgid "Proceed to fill out the modal interview form as a typical survey. For specific directions on how to create a survey, refer to the :doc:`survey essentials <../../marketing/surveys/create>` document, which provides step-by-step instructions on how to create and configure a survey." msgstr "" +#: ../../content/applications/hr/recruitment/offer_job_positions.rst:3 +msgid "Offer job positions" +msgstr "" + +#: ../../content/applications/hr/recruitment/offer_job_positions.rst:5 +msgid "Once an applicant has successfully passed the various interview stages, the recruitment team is ready to send an offer for employment. The next step is to send the applicant a contract." +msgstr "" + +#: ../../content/applications/hr/recruitment/offer_job_positions.rst:9 +msgid "Refer to the :doc:`recruitment <../recruitment>` documentation for details on the various stages of the recruitment process." +msgstr "" + +#: ../../content/applications/hr/recruitment/offer_job_positions.rst:13 +msgid "Contract proposal" +msgstr "" + +#: ../../content/applications/hr/recruitment/offer_job_positions.rst:15 +msgid "When an offer is ready to be sent, first open the applicant's card by navigating to the :menuselection:`Recruitment app`, and clicking on the desired job position card." +msgstr "" + +#: ../../content/applications/hr/recruitment/offer_job_positions.rst:18 +msgid "From the resulting :guilabel:`Job Positions` Kanban view, the corresponding applicant card can be dragged-and-dropped to the :guilabel:`Contract Proposal` stage. Or, click into the desired applicant's card, and click the :guilabel:`Contract Proposal` stage, located in the status bar in the top-right of the applicant's form." +msgstr "" + +#: ../../content/applications/hr/recruitment/offer_job_positions.rst:23 +msgid "The next step is to send an offer to the applicant. Start by selecting the desired applicant's card to open their applicant form." +msgstr "" + +#: ../../content/applications/hr/recruitment/offer_job_positions.rst:26 +msgid "On the applicant's form, click the :guilabel:`Generate Offer` button. A :guilabel:`Generate a Simulation Link` pop-up window appears." +msgstr "" + +#: ../../content/applications/hr/recruitment/offer_job_positions.rst:29 +msgid "Most fields are pre-populated with information from the job position. If any necessary fields are blank, or if any information needs to be updated, enter, or update, the relevant information in the corresponding fields." +msgstr "" + +#: ../../content/applications/hr/recruitment/offer_job_positions.rst:34 +msgid "Depending on the localization setting for the company, and which applications are installed, some fields may not appear in the :guilabel:`Generate a Simulation Link` pop-up window." +msgstr "" + +#: ../../content/applications/hr/recruitment/offer_job_positions.rst:37 +msgid "For example, if the *Fleet* application is **not** installed, any fields related to vehicles do **not** appear." +msgstr "" + +#: ../../content/applications/hr/recruitment/offer_job_positions.rst:41 +msgid "Universal fields" +msgstr "" + +#: ../../content/applications/hr/recruitment/offer_job_positions.rst:43 +msgid "The following fields appear in the :guilabel:`Generate a Simulation Link` pop-up window, regardless of the localization." +msgstr "" + +#: ../../content/applications/hr/recruitment/offer_job_positions.rst:46 +msgid ":guilabel:`Contract Template`: the template currently being used to populate the :guilabel:`Generate a Simulation Link` pop-up window. Use the drop-down menu to select a different :guilabel:`Contract Template`, if desired." +msgstr "" + +#: ../../content/applications/hr/recruitment/offer_job_positions.rst:51 +msgid "To modify the template, hover over the current template name, and click the :icon:`oi-launch` :guilabel:`Internal link` icon that appears to the right of the field. Make any desired changes, then click :guilabel:`Save & Close`." +msgstr "" + +#: ../../content/applications/hr/recruitment/offer_job_positions.rst:55 +msgid ":guilabel:`Job Position`: the name of the :guilabel:`Job Position` being offered to the applicant. The selections available in the drop-down menu correspond to the job position configured on the main *Recruitment* dashboard." +msgstr "" + +#: ../../content/applications/hr/recruitment/offer_job_positions.rst:58 +msgid ":guilabel:`Job Title`: the selected :guilabel:`Job Position` populates this field, by default. The title can be modified to suit the specific applicant's position and provide more details." +msgstr "" + +#: ../../content/applications/hr/recruitment/offer_job_positions.rst:62 +msgid "An applicant is offered a marketing manager job at a shoe company, specifically for the children's line." +msgstr "" + +#: ../../content/applications/hr/recruitment/offer_job_positions.rst:65 +msgid "The :guilabel:`Job Position` selected from the drop-down menu is `Marketing Manager`, and the :guilabel:`Job Title` is modified for their specific responsibilities, `Marketing Manager: Children's Shoes`." +msgstr "" + +#: ../../content/applications/hr/recruitment/offer_job_positions.rst:69 +msgid ":guilabel:`Department`: the department the job position falls under." +msgstr "" + +#: ../../content/applications/hr/recruitment/offer_job_positions.rst:70 +msgid ":guilabel:`Contract Start Date`: the date the contract takes effect. The default date is the current date. To modify the date, click on the displayed date to reveal a calendar popover window. Navigate to the desired month, then click the day to select the date." +msgstr "" + +#: ../../content/applications/hr/recruitment/offer_job_positions.rst:73 +msgid ":guilabel:`Yearly Cost`: the annual salary being offered." +msgstr "" + +#: ../../content/applications/hr/recruitment/offer_job_positions.rst:74 +msgid ":guilabel:`Link Expiration Date`: the number of days the job offer is valid. The default expiration date is `30` days. Modify the expiration date, if desired." +msgstr "" + +#: ../../content/applications/hr/recruitment/offer_job_positions.rst:78 +msgid "Send offer" +msgstr "" + +#: ../../content/applications/hr/recruitment/offer_job_positions.rst:80 +msgid "Once the :guilabel:`Generate a Simulation Link` pop-up window is complete, click :guilabel:`Send By Email` to reveal an email pop-up window." +msgstr "" + +#: ../../content/applications/hr/recruitment/offer_job_positions.rst:84 +msgid "If the applicant does not have an email address listed on their applicant card, a warning appears in a red box at the bottom of the :guilabel:`Generate a Simulation Link` pop-up window, stating: :guilabel:`The applicant does not have a valid email set. The Offer Link won't be able to be completed.` Click :guilabel:`Discard`, then enter an email on the applicant's card. Once an email is entered, click the :guilabel:`Generate Offer` button, and the email pop-up window loads again." +msgstr "" + +#: ../../content/applications/hr/recruitment/offer_job_positions.rst:90 +msgid "The default :guilabel:`Recruitment: Your Salary Package` email template is used (set in the :guilabel:`Load template` field), and the :guilabel:`Recipients`, :guilabel:`Subject`, and email body are pre-populated based on the email template." +msgstr "" + +#: ../../content/applications/hr/recruitment/offer_job_positions.rst:94 +msgid "If any attachments need to be added, click the :icon:`fa-paperclip` :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 :icon:`fa-paperclip` :guilabel:`Attachments` button." +msgstr "" + +#: ../../content/applications/hr/recruitment/offer_job_positions.rst:99 +msgid "Once the email is ready to send, click :guilabel:`Send`. The email pop-up window closes, and an :guilabel:`Offers` smart button appears at the top of the applicant's card." +msgstr "" + +#: ../../content/applications/hr/recruitment/offer_job_positions.rst:103 +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, and they can actually sign the offer. The applicant does **not** need any software installed to sign the offer." +msgstr "" + +#: ../../content/applications/hr/recruitment/offer_job_positions.rst:-1 +msgid "Send an email to the applicant with a link to the offered salary." +msgstr "" + +#: ../../content/applications/hr/recruitment/offer_job_positions.rst:112 +msgid "Configure your package" +msgstr "" + +#: ../../content/applications/hr/recruitment/offer_job_positions.rst:114 +msgid "If applicable, the applicant can modify their salary package. This option is not available for all localizations. Depending on where the company is located, this option may not be available." +msgstr "" + +#: ../../content/applications/hr/recruitment/offer_job_positions.rst:117 +msgid "The email template includes a :guilabel:`Configure your package` button. This link takes the applicant to a webpage, where they can modify the proposed salary package, and enter their personal information." +msgstr "" + +#: ../../content/applications/hr/recruitment/offer_job_positions.rst:121 +msgid "Once the applicant is hired, the personal information entered on the webpage is imported to their employee record, when created." +msgstr "" + +#: ../../content/applications/hr/recruitment/offer_job_positions.rst:124 +msgid "Once all the information is completed, the applicant can then accept the offer by clicking the :guilabel:`Review Contract & Sign` button to accept the contract, and sign it using the *Sign* application." +msgstr "" + +#: ../../content/applications/hr/recruitment/offer_job_positions.rst:131 +msgid "Contract signed" +msgstr "" + +#: ../../content/applications/hr/recruitment/offer_job_positions.rst:133 +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. This stage is folded in the Kanban view, by default." +msgstr "" + +#: ../../content/applications/hr/recruitment/offer_job_positions.rst:137 +msgid "To move the applicant to that stage, drag-and-drop the applicant's card to the :guilabel:`Contract Signed` stage. If the stage is not visible, click the :icon:`fa-ellipsis-h` :guilabel:`(ellipsis)` button to the right of :guilabel:`Contract Proposal` on the applicant's form, and click :guilabel:`Contract Signed` from the resulting drop-down menu." +msgstr "" + +#: ../../content/applications/hr/recruitment/offer_job_positions.rst:142 +msgid "Once the applicant is moved to the :guilabel:`Contract Signed` stage, a green :guilabel:`HIRED` banner appears in the top-right of the applicant's card and form." +msgstr "" + +#: ../../content/applications/hr/recruitment/offer_job_positions.rst:-1 +msgid "Hired banner in the top right corner of applicant card." +msgstr "" + +#: ../../content/applications/hr/recruitment/offer_job_positions.rst:150 +msgid "Create employee" +msgstr "" + +#: ../../content/applications/hr/recruitment/offer_job_positions.rst:152 +msgid "Once the applicant has been hired, the next step is to create their employee record. Click the :guilabel:`Create Employee` button in the top-left corner of the hired applicant's form." +msgstr "" + +#: ../../content/applications/hr/recruitment/offer_job_positions.rst:155 +msgid "An employee form appears, with information from the applicant's card, and the employee contract." +msgstr "" + +#: ../../content/applications/hr/recruitment/offer_job_positions.rst:157 +msgid "Fill out the rest of the employee form. For detailed information on the fields, refer to the :doc:`../employees/new_employee` documentation." +msgstr "" + +#: ../../content/applications/hr/recruitment/offer_job_positions.rst:160 +msgid "Once completed, the employee record is saved in the *Employees* app." +msgstr "" + #: ../../content/applications/hr/recruitment/refuse_applicant.rst:3 msgid "Refuse applicants" msgstr "" @@ -9591,6 +9690,343 @@ msgstr "" msgid "All applicants that have been refused for the job position appear on the :guilabel:`Applications` page for that position, organized by the stage they were in when they were refused." msgstr "" +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:3 +msgid "Schedule interviews" +msgstr "" + +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:5 +msgid "Schedule in-person, virtual, and phone interviews with Odoo through the *Recruitment* app." +msgstr "" + +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:7 +msgid "An interview can be scheduled in one of two ways: either by the :ref:`recruitment team `, or by the :ref:`applicant `." +msgstr "" + +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:14 +msgid "Recruitment team scheduled interviews" +msgstr "" + +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:16 +msgid "When an applicant reaches the interview stage, the recruitment team should schedule the interview, by first coordinating a suitable date and time with the applicant and interviewers." +msgstr "" + +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:19 +msgid "To schedule the interview, navigate to the applicant's card, by first going to the :menuselection:`Recruitment app`, and clicking the relevant job card. This opens the :guilabel:`Applications` page for that job position. Then, click the desired applicant's card to view their detailed applicant form." +msgstr "" + +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:24 +msgid "To schedule an phone, virtual, or in-person interview, click the :guilabel:`No Meeting` smart button at the top of the applicant's record." +msgstr "" + +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:28 +msgid "The *Meetings* smart button displays :guilabel:`No Meeting` if no meetings are currently scheduled. For applicants who are new to the :guilabel:`First Interview` stage, this is the default." +msgstr "" + +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:32 +msgid "If there is one meeting already scheduled, the smart button displays *1 Meeting*, with the date of the upcoming meeting beneath it. If more than one meeting is scheduled, the button displays *Next Meeting*, with the date of the first upcoming meeting beneath it." +msgstr "" + +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:36 +msgid "Clicking the *Meetings* smart button loads a calendar, showing the scheduled meetings and events for the currently signed-in user, as well as the employees who are listed under the :guilabel:`Attendees` section, located to the right of the calendar." +msgstr "" + +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:40 +msgid "To change the currently loaded meetings and events being displayed, uncheck an attendee whose calendar events are to be hidden. Only the checked attendees are visible on the calendar." +msgstr "" + +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:-1 +msgid "The calendar view, highlighting how to change the displayed meetings." +msgstr "" + +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:47 +msgid "To add a meeting to the calendar when in the *Day* or *Week* view, click on the start time of the meeting and drag down to the end time. Doing so selects the date, time, and the length of the meeting." +msgstr "" + +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:51 +msgid "A meeting can also be added in this view by clicking on the desired day *and* time slot." +msgstr "" + +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:53 +msgid "Both methods cause a :ref:`New Event ` pop-up window to appear." +msgstr "" + +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:59 +msgid "New event pop-up window" +msgstr "" + +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:61 +msgid "Clicking a grid, corresponding with the time and date, opens the :guilabel:`New Event` pop-up window to schedule a meeting." +msgstr "" + +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:64 +msgid "Enter the information on the form. The only required fields to enter are a title for the meeting, along with the :guilabel:`Start` (and end date/time) fields." +msgstr "" + +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:67 +msgid "Once the card details are entered, click :guilabel:`Save & Close` to save the changes and create the interview." +msgstr "" + +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:70 +msgid "After entering in a required name for the meeting, the fields available to modify on the :guilabel:`New Event` card are as follows:" +msgstr "" + +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:73 +msgid ":guilabel:`Meeting Title`: 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/schedule_interviews.rst:76 +msgid ":guilabel:`Start`: start and end date and times for the meeting. Clicking either of these fields opens a calendar pop-up window. Click :guilabel:`Apply` to close the window." +msgstr "" + +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:78 +msgid ":guilabel:`All Day`: tick the box to schedule an all-day interview. If this box is ticked, the :guilabel:`Start` field changes to :guilabel:`Start Date`." +msgstr "" + +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:80 +msgid ":guilabel:`Attendees`: select the people who should attend the meeting. The default employee listed is the person who created the meeting. Add as many other people as desired." +msgstr "" + +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:82 +msgid ":guilabel:`Videocall URL`: if the meeting is virtual, or if there is a virtual option available, click :icon:`fa-plus` :guilabel:`Odoo meeting`, and a URL is automatically created for the meeting, which populates the field." +msgstr "" + +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:85 +msgid ":guilabel:`Description`: enter a brief description in this field. There is an option to enter formatted text, such as numbered lists, headings, tables, links, photos, and more. Use the powerbox feature, by typing a `/` to reveal a list of options." +msgstr "" + +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:89 +msgid "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/schedule_interviews.rst:94 +msgid "More options" +msgstr "" + +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:96 +msgid "To add additional information to the meeting, click the :guilabel:`More Options` button in the lower-right corner of the :ref:`New Event ` pop-up window. Enter any of the following additional fields:" +msgstr "" + +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:100 +msgid ":guilabel:`Duration`: this field auto populates based on the :guilabel:`Start` (and end) date and time. If the meeting time is adjusted, this field automatically adjusts to the correct duration length. The default length of a meeting is one hour." +msgstr "" + +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:103 +msgid ":guilabel:`Recurrent`: if the meeting should repeat at a selected interval (not typical for a first interview), tick the checkbox next to :guilabel:`Recurrent`. Several additional fields appear when this is enabled:" +msgstr "" + +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:107 +msgid ":guilabel:`Timezone`: using the drop-down menu, select the :guilabel:`Timezone` for the recurrent meetings." +msgstr "" + +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:109 +msgid ":guilabel:`Repeat`: choose :guilabel:`Daily`, :guilabel:`Weekly`, :guilabel:`Monthly`, :guilabel:`Yearly`, or :guilabel:`Custom` recurring meetings. If :guilabel:`Custom` is selected, a :guilabel:`Repeat Every` field appears beneath it, along with another time frequency parameter (:guilabel:`Days`, :guilabel:`Weeks`, :guilabel:`Months`, or :guilabel:`Years`). Enter a number in the blank field, then select the time period using the drop-down menu." +msgstr "" + +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:114 +msgid ":guilabel:`Repeat on`: enabled when the :guilabel:`Weekly` option is selected in the :guilabel:`Repeat` field. Choose the day the weekly meeting falls on." +msgstr "" + +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:116 +msgid ":guilabel:`Day of Month`: configure the two drop-down menu options to select a specific day of the month, irrespective of the date (e.g. the first Tuesday of every month). To set a specific calendar date, choose :guilabel:`Date of Month` and enter the calendar date in the field (e.g. `15` to set the meeting to occur on the fifteenth of every month)." +msgstr "" + +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:120 +msgid ":guilabel:`Until`: using the drop-down menu, select when the meetings stop repeating. The available options are :guilabel:`Number of repetitions`, :guilabel:`End date`, and :guilabel:`Forever`. If :guilabel:`Number of repetitions` is selected, enter the number of total meetings to occur in the blank field to the right. If :guilabel:`End date` is selected, specify the date using the calendar pop-up window, or type in a date in a XX/XX/XXXX format. :guilabel:`Forever` schedules meetings indefinitely." +msgstr "" + +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:127 +msgid ":guilabel:`Location`: enter the location for the meeting." +msgstr "" + +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:128 +msgid ":guilabel:`Tags`: select any tags for the meeting using the drop-down menu, or add a new tag by typing in the tag and clicking :guilabel:`Create \"tag\"`. There is no limit to the number of tags that can be used." +msgstr "" + +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:131 +msgid ":guilabel:`Appointment`: if an appointment is associated with this meeting, select it from the drop-down menu, or create a new appointment by typing in the appointment name, then clicking :guilabel:`Create & Edit...` from the resulting drop-down men. A :guilabel:`Create Appointment` form loads. Enter the information on the form, then click :guilabel:`Save & Close`." +msgstr "" + +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:135 +msgid ":guilabel:`Privacy`: select if the organizer appears either :guilabel:`Available` or :guilabel:`Busy` for the duration of the meeting. Next, select the visibility of this meeting, using the drop-down menu to the right of the first selection. 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/schedule_interviews.rst:142 +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/schedule_interviews.rst:144 +msgid ":guilabel:`Reminders`: select a reminder from the drop-down menu. Default options include :guilabel:`Notification`, :guilabel:`Email`, and :guilabel:`SMS Text Message`, each with a specific time period before the event (hours, days, etc). The chosen reminder chosen alerts the meeting participants of the meeting, via the selected option at the specified time. Multiple reminders can be selected in this field." +msgstr "" + +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:-1 +msgid "A new meeting card with all the details populated, and ready to save." +msgstr "" + +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:155 +msgid "Send meeting to attendees" +msgstr "" + +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:157 +msgid "Once changes have been entered on the :ref:`New Event ` pop-up window, and the meeting details are correct, the meeting can be sent to the attendees, via email or text message, from the expanded event form (what is seen when the :guilabel:`More Options` button is clicked on in the :guilabel:`New Event` pop-up window)." +msgstr "" + +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:162 +msgid "To send the meeting via email, click the :icon:`fa-envelope` :guilabel:`Email` button next to the :guilabel:`Attendees` field on the expanded meeting form." +msgstr "" + +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:165 +msgid "A :guilabel:`Contact Attendees` email configurator pop-up window appears. A pre-formatted email, using the default :guilabel:`Calendar: Event Update` email template, populates the email body field." +msgstr "" + +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:168 +msgid "The followers of the job application, as well as the user who created the meeting, are added as :guilabel:`Recipients` by default. If needed, 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:`Attachments` 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/schedule_interviews.rst:-1 +msgid "Enter the information to send the event via email." +msgstr "" + +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:178 +msgid "To send the meeting via text message, click the :icon:`fa-mobile` :guilabel:`SMS` button next to the :guilabel:`Attendees` field on the expanded meeting form. A :guilabel:`Send SMS Text Message` pop-up window appears." +msgstr "" + +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:182 +msgid "At the top, a blue banner appears if any attendees do not have valid mobile numbers, and lists how many records are invalid. If a contact does not have a valid mobile number listed, click :guilabel:`Close`, and edit the attendee's record, then redo these steps." +msgstr "" + +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:186 +msgid "When no warning message appears, type in the message to be sent to the attendees in the :guilabel:`Message` field. To add any emojis to the message, click the :icon:`oi-smile-add` :guilabel:`(smile add)` icon on the right-side of the pop-up window." +msgstr "" + +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:190 +msgid "The number of characters, and amount of text messages required to send the message (according to GSM7 criteria) appears beneath the :guilabel:`Message` field. 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/schedule_interviews.rst:-1 +msgid "Send a text message to the attendees of the meeting." +msgstr "" + +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:200 +msgid "Sending text messages is **not** a default capability with Odoo. To send text messages, credits are required, which need to be purchased. For more information on IAP credits and plans, refer to the :doc:`../../essentials/in_app_purchase` documentation." +msgstr "" + +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:207 +msgid "Applicant scheduled interviews" +msgstr "" + +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:209 +msgid "By default, the recruitment interview stages are **not** set up for applicants to schedule their own interviews." +msgstr "" + +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:212 +msgid "However, if the :guilabel:`First Interview` or :guilabel:`Second Interview` stages are modified to send the :guilabel:`Recruitment: Schedule Interview` email template when an applicant reaches that stage, the applicant receives a link to the recruitment team's calendar, and can schedule the interview on their own. The recruitment team's availability is reflected in the calendar." +msgstr "" + +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:217 +msgid "In order for applicants to be able to schedule their own interviews, a :ref:`stage must first be modified ` in the *Recruitment* app." +msgstr "" + +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:225 +msgid "To modify either the :guilabel:`First Interview` or :guilabel:`Second Interview` stage, first navigate to the main :menuselection:`Recruitment` app dashboard. Next, click on the desired job card to navigate to the :guilabel:`Applications` page for that job position." +msgstr "" + +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:229 +msgid "Hover over the name of the stage, and a :icon:`fa-cog` :guilabel:`(gear)` icon appears in the upper-right hand side of the stage name. Click the :icon:`fa-cog` :guilabel:`(gear)` icon, and a drop-down menu appears. Then, click on the :guilabel:`Edit` option, and an :guilabel:`Edit: (Stage)` form appears." +msgstr "" + +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:-1 +msgid "The drop-down that appears after clicking the cog." +msgstr "" + +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:238 +msgid "The :guilabel:`Email Template` field is blank, by default. Using the drop-down menu, select :guilabel:`Recruitment: Schedule interview` for the :guilabel:`Email Template` field, then click :guilabel:`Save & Close` when done." +msgstr "" + +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:-1 +msgid "The Recruitment: Schedule Interview email template populating the Email Template field." +msgstr "" + +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:247 +msgid "Send email" +msgstr "" + +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:249 +msgid "After either the :guilabel:`First Interview` or :guilabel:`Second Interview` stages are :ref:`modified to send the ` :guilabel:`Recruitment: Schedule interview` email to the applicant upon moving their applicant card to one of those stages, the following email is received by the applicant:" +msgstr "" + +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:254 +msgid "`Subject: Can we plan an interview together for your (Job Position) application?`" +msgstr "" + +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:256 +msgid "`Congratulations! Your application is really interesting and we'd like to plan an interview with you. Can you please use the button below to schedule it with one of our recruiters?`" +msgstr "" + +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:260 +msgid "`Plan my interview`" +msgstr "" + +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:263 +msgid "Schedule interview" +msgstr "" + +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:265 +msgid "When the applicant received the email, they click the :guilabel:`Plan my interview` button at the bottom of the email. This navigates the applicant to a private online scheduling page, which is **only** accessible through the emailed link." +msgstr "" + +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:269 +msgid "This page displays the :guilabel:`MEETING DETAILS` on the right side of the screen. This includes the format and length of the meeting. In this example. the interview is virtual (:icon:`fa-video-camera` :guilabel:`Online`) and the duration is a half hour (:icon:`fa-clock-o` :guilabel:`30 minutes`)." +msgstr "" + +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:274 +msgid "First, if there is an option of who to meet with, the user selects who they are scheduling their meeting with, by clicking on their icon and name. If only one person is available to interview the applicant, this step is not available. If the applicant does not wish to chose an interviewer, they can just click :guilabel:`See all availabilities` :icon:`fa-arrow-right`." +msgstr "" + +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:-1 +msgid "The first screen seen after clicking 'Plan my interview', where the applicant selects their\n" +"interviewer." +msgstr "" + +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:285 +msgid "If the applicant selects an interviewer, the applicant is shown a :guilabel:`Select a date & time` page, and **only** sees the dates and times that specific person is available. In addition, that interviewer's information (name, email, and phone number) appears on the right-side of the screen, under the heading :guilabel:`OPERATOR`, located beneath the :guilabel:`MEETING DETAILS`." +msgstr "" + +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:290 +msgid "If the applicant clicks :guilabel:`See all availabilities` :icon:`fa-arrow-right` instead, or if there are no interviewer options available, the user is navigated to the same :guilabel:`Select a date & time` page, but there is no :guilabel:`OPERATOR` section visible." +msgstr "" + +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:294 +msgid "Then the applicant clicks on an available day on the calendar, signified by a square around the date. Once a day is selected, they click on one of the available times to select that date and time." +msgstr "" + +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:-1 +msgid "The calendar screen with dates and times to schedule an interview." +msgstr "" + +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:302 +msgid "Be sure to check the :guilabel:`Timezone` field, beneath the calendar, to ensure it is set to the correct time zone. Changing the time zone may alter the available times presented." +msgstr "" + +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:305 +msgid "Once the date and time are selected, the applicant is navigated to an :guilabel:`Add more details about you` page. This page asks the applicant to enter their :guilabel:`Full name`, :guilabel:`Email`, and :guilabel:`Phone number`. The contact information entered on this form is how the applicant is contacted to remind them about the scheduled interview." +msgstr "" + +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:310 +msgid "When everything is entered on the :guilabel:`Add more details about you` page, the applicant clicks the :guilabel:`Confirm Appointment` button, and the interview is scheduled." +msgstr "" + +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:-1 +msgid "The confirmation page with all the details for the interview displayed." +msgstr "" + +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:317 +msgid "After confirming the interview, the applicant is taken to a confirmation page, where all the details of the interview are displayed. The option to add the meeting to the applicant's personal calendars is available, through the :guilabel:`Add to iCal/Outlook` and :guilabel:`Add to Google Agenda` buttons, beneath the interview details." +msgstr "" + +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:322 +msgid "The applicant is also able to cancel or reschedule the interview, if necessary, with the :guilabel:`Cancel/Reschedule` button." +msgstr "" + #: ../../content/applications/hr/referrals.rst:5 msgid "Referrals" msgstr "" @@ -9607,43 +10043,43 @@ msgstr "" msgid "Users with either :guilabel:`Referral User`, :guilabel:`Officer`, or :guilabel:`Administrator` access rights for the *Recruitment* application have access to the *Referrals* application. Only users with :guilabel:`Administrator` access rights for the *Recruitment* application have access to the :ref:`reporting ` and configurations menus. For more information on users and access rights, refer to these documents: :doc:`../general/users` and :doc:`../general/users/access_rights`." msgstr "" -#: ../../content/applications/hr/referrals.rst:26 +#: ../../content/applications/hr/referrals.rst:28 msgid "Onboarding" msgstr "" -#: ../../content/applications/hr/referrals.rst:28 +#: ../../content/applications/hr/referrals.rst:30 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:34 +#: ../../content/applications/hr/referrals.rst:36 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:37 +#: ../../content/applications/hr/referrals.rst:39 msgid "The text that appears on each slide is as follows:" msgstr "" -#: ../../content/applications/hr/referrals.rst:39 +#: ../../content/applications/hr/referrals.rst:41 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:41 +#: ../../content/applications/hr/referrals.rst:43 msgid ":guilabel:`Browse through open job positions, promote them on social media, or refer friends.`" msgstr "" -#: ../../content/applications/hr/referrals.rst:42 +#: ../../content/applications/hr/referrals.rst:44 msgid ":guilabel:`Collect points and exchange them for awesome gifts in the shop.`" msgstr "" -#: ../../content/applications/hr/referrals.rst:43 +#: ../../content/applications/hr/referrals.rst:45 msgid ":guilabel:`Compete against your colleagues to build the best justice league!`" msgstr "" -#: ../../content/applications/hr/referrals.rst:46 +#: ../../content/applications/hr/referrals.rst:48 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:53 +#: ../../content/applications/hr/referrals.rst:55 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 "" @@ -9651,27 +10087,27 @@ msgstr "" msgid "An onboarding slide with the skip and next buttons visible at the bottom." msgstr "" -#: ../../content/applications/hr/referrals.rst:62 +#: ../../content/applications/hr/referrals.rst:64 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:68 +#: ../../content/applications/hr/referrals.rst:70 msgid "Modifying onboarding slides" msgstr "" -#: ../../content/applications/hr/referrals.rst:70 +#: ../../content/applications/hr/referrals.rst:72 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." msgstr "" -#: ../../content/applications/hr/referrals.rst:76 +#: ../../content/applications/hr/referrals.rst:78 msgid "Make any changes to the message in the :guilabel:`Text` field. A :guilabel:`Company` may be selected, as well. However, if this field is populated, that slide is *only* displayed for that particular company." msgstr "" -#: ../../content/applications/hr/referrals.rst:81 +#: ../../content/applications/hr/referrals.rst:83 msgid "The :guilabel:`Company` field only appears when in a multi-company database." msgstr "" -#: ../../content/applications/hr/referrals.rst:83 +#: ../../content/applications/hr/referrals.rst:85 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 "" @@ -9679,7 +10115,7 @@ msgstr "" msgid "An onboarding slide in edit mode, with the main fields highlighted." msgstr "" -#: ../../content/applications/hr/referrals.rst:94 +#: ../../content/applications/hr/referrals.rst:96 msgid "The sequence in which the slides appear can be changed from the *Onboarding* dashboard. Click the :guilabel:`(six small gray boxes)` icon to the left of the the slide text, and drag the slide to the desired position." msgstr "" @@ -9687,23 +10123,23 @@ msgstr "" msgid "The onboarding slides in a list, with the drag and drop arrows highlighted." msgstr "" -#: ../../content/applications/hr/referrals.rst:105 +#: ../../content/applications/hr/referrals.rst:107 msgid "Hired referrals" msgstr "" -#: ../../content/applications/hr/referrals.rst:107 +#: ../../content/applications/hr/referrals.rst:109 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:110 +#: ../../content/applications/hr/referrals.rst:112 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:114 +#: ../../content/applications/hr/referrals.rst:116 msgid "Below this message are five avatar thumbnails to choose from. If an avatar has already been assigned to a referral, the thumbnail is grayed out, and the name that the avatar has been chosen for appears beneath the avatar. Click on an available avatar to select it." msgstr "" -#: ../../content/applications/hr/referrals.rst:118 +#: ../../content/applications/hr/referrals.rst:120 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 "" @@ -9712,27 +10148,27 @@ msgid "The hired screen. A selection of avatars are presented to chose from, wit "chosen are greyed out." msgstr "" -#: ../../content/applications/hr/referrals.rst:129 +#: ../../content/applications/hr/referrals.rst:131 msgid "Modify friends" msgstr "" -#: ../../content/applications/hr/referrals.rst:131 +#: ../../content/applications/hr/referrals.rst:133 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:138 +#: ../../content/applications/hr/referrals.rst:140 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:143 +#: ../../content/applications/hr/referrals.rst:145 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:148 +#: ../../content/applications/hr/referrals.rst:150 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:153 +#: ../../content/applications/hr/referrals.rst:155 msgid "The referral friend form automatically saves, but can be saved manually at any time by clicking the *Save manually* option, represented by a :guilabel:`(cloud upload)` icon, located in the top-left corner. To cancel any changes made, click the :guilabel:`✖️ (Discard all changes)` icon to delete any changes, and revert to the original content." msgstr "" @@ -9740,136 +10176,52 @@ msgstr "" msgid "A friend form in edit mode." msgstr "" -#: ../../content/applications/hr/referrals.rst:163 -#: ../../content/applications/hr/referrals.rst:293 +#: ../../content/applications/hr/referrals.rst:165 +#: ../../content/applications/hr/referrals.rst:225 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:167 +#: ../../content/applications/hr/referrals.rst:169 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:172 -msgid "Referral points" -msgstr "" - -#: ../../content/applications/hr/referrals.rst:174 -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:179 -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:183 -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:189 -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:194 -msgid "My referrals" -msgstr "" - -#: ../../content/applications/hr/referrals.rst:196 -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:200 -msgid "A successful referral displays a green :guilabel:`Hired` banner in the top-right corner of the card. Referrals that are in process display a purple :guilabel:`In Progress` banner in the top-right corner." -msgstr "" - -#: ../../content/applications/hr/referrals.rst:204 -msgid "Each referral card lists the name of the applicant, the subject/application title (as it appears on the applicant card in the *Recruitment* app), the name of the job position, the person responsible for filling the role (recruiter), and the points earned. For referrals that have been hired, the selected avatar also appears on the card." -msgstr "" - -#: ../../content/applications/hr/referrals.rst:-1 -msgid "Two referral cards, one hired and one in-progress." -msgstr "" - -#: ../../content/applications/hr/referrals.rst:214 -msgid "Points" -msgstr "" - -#: ../../content/applications/hr/referrals.rst:216 -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:220 -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:224 -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:229 -msgid "The pre-configured point structure for referrals is as follows:" -msgstr "" - -#: ../../content/applications/hr/referrals.rst:231 -msgid ":guilabel:`Initial Qualification`: 1 point" -msgstr "" - -#: ../../content/applications/hr/referrals.rst:232 -msgid ":guilabel:`First Interview`: 20 points" -msgstr "" - -#: ../../content/applications/hr/referrals.rst:233 -msgid ":guilabel:`Second Interview`: 9 points" -msgstr "" - -#: ../../content/applications/hr/referrals.rst:234 -msgid ":guilabel:`Contract Proposal`: 5 points" -msgstr "" - -#: ../../content/applications/hr/referrals.rst:235 -msgid ":guilabel:`Contract Signed`: 50 points" -msgstr "" - -#: ../../content/applications/hr/referrals.rst:237 -msgid "The total points earned for a referral that is hired is 85 points. Modifications of the points earned for each stage are done in the *Recruitment* application. Refer to the :ref:`Recruitment ` documentation to modify the points for each stage." -msgstr "" - -#: ../../content/applications/hr/referrals.rst:244 +#: ../../content/applications/hr/referrals.rst:176 msgid "Levels" msgstr "" -#: ../../content/applications/hr/referrals.rst:246 +#: ../../content/applications/hr/referrals.rst:178 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:250 +#: ../../content/applications/hr/referrals.rst:182 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:253 +#: ../../content/applications/hr/referrals.rst:185 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:260 +#: ../../content/applications/hr/referrals.rst:192 msgid "Modify levels" msgstr "" -#: ../../content/applications/hr/referrals.rst:262 +#: ../../content/applications/hr/referrals.rst:194 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:269 +#: ../../content/applications/hr/referrals.rst:201 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, then make modifications." msgstr "" -#: ../../content/applications/hr/referrals.rst:272 +#: ../../content/applications/hr/referrals.rst:204 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:278 +#: ../../content/applications/hr/referrals.rst:210 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:283 +#: ../../content/applications/hr/referrals.rst:215 msgid "The level form saves automatically, but can be saved manually at any time by clicking the *save manually* option, represented by a :guilabel:`(cloud upload)` icon, located in the top-left corner. To cancel any changes made, click the :guilabel:`✖️ (Discard all changes)` icon to delete any changes, and revert to the original content." msgstr "" @@ -9877,23 +10229,23 @@ msgstr "" msgid "A level form in edit mode." msgstr "" -#: ../../content/applications/hr/referrals.rst:297 +#: ../../content/applications/hr/referrals.rst:229 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:302 +#: ../../content/applications/hr/referrals.rst:234 msgid "Level up" msgstr "" -#: ../../content/applications/hr/referrals.rst:304 +#: ../../content/applications/hr/referrals.rst:236 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:309 +#: ../../content/applications/hr/referrals.rst:241 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:313 +#: ../../content/applications/hr/referrals.rst:245 msgid "Leveling up does not cost the user any points, the user simply needs to earn the specified amount of points required." msgstr "" @@ -9902,39 +10254,43 @@ msgid "A 'Click to level up!' appears beneath the user's image, and a large 'Lev "above their image." msgstr "" -#: ../../content/applications/hr/referrals.rst:322 +#: ../../content/applications/hr/referrals.rst:254 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:331 +#: ../../content/applications/hr/referrals.rst:263 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:336 +#: ../../content/applications/hr/referrals.rst:268 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:342 +#: ../../content/applications/hr/referrals.rst:274 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:347 +#: ../../content/applications/hr/referrals.rst:279 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:354 +#: ../../content/applications/hr/referrals.rst:286 msgid "The spreadsheet is stored in the *Documents* application. This application needs to be installed to use the :guilabel:`Insert in Spreadsheet` option." msgstr "" -#: ../../content/applications/hr/referrals.rst:358 +#: ../../content/applications/hr/referrals.rst:290 msgid ":doc:`referrals/share_jobs`" msgstr "" -#: ../../content/applications/hr/referrals.rst:359 +#: ../../content/applications/hr/referrals.rst:291 +msgid ":doc:`referrals/points`" +msgstr "" + +#: ../../content/applications/hr/referrals.rst:292 msgid ":doc:`referrals/rewards`" msgstr "" -#: ../../content/applications/hr/referrals.rst:360 +#: ../../content/applications/hr/referrals.rst:293 msgid ":doc:`referrals/alerts`" msgstr "" @@ -10022,6 +10378,98 @@ msgstr "" msgid "This prevents the alert from appearing again, even when opening the *Referrals* application for the first time in a new session." msgstr "" +#: ../../content/applications/hr/referrals/points.rst:3 +msgid "Referral points" +msgstr "" + +#: ../../content/applications/hr/referrals/points.rst:5 +msgid "The *Referrals* application allows employees to earn points that are then exchanged for :doc:`rewards `." +msgstr "" + +#: ../../content/applications/hr/referrals/points.rst:8 +msgid "Current referral points can be viewed on the main *Referrals* app dashboard, which appears when the application is opened, after the :ref:`onboarding ` slides have been viewed or skipped." +msgstr "" + +#: ../../content/applications/hr/referrals/points.rst:12 +msgid "At the top, a summary of the user's current points is displayed. The left side of the summary displays the :guilabel:`Total` points earned, and the right side displays the points that are available :guilabel:`To Spend`." +msgstr "" + +#: ../../content/applications/hr/referrals/points.rst:16 +msgid "To view the various referral stages, and their respective earned points, click one of the referral statuses beneath the avatar. The options are: :guilabel:`Referrals`, :guilabel:`Ongoing`, and :guilabel:`Successful`." +msgstr "" + +#: ../../content/applications/hr/referrals/points.rst:20 +msgid "The current number of referrals that are still active in the recruitment pipeline, but have not yet been hired or refused, appear above :guilabel:`Ongoing`. The number of referrals that have been hired, appear above :guilabel:`Successful`. The total number of referrals, both the ongoing and successful referrals combined, appears above :guilabel:`Referrals`." +msgstr "" + +#: ../../content/applications/hr/referrals/points.rst:26 +msgid "My referrals" +msgstr "" + +#: ../../content/applications/hr/referrals/points.rst:28 +msgid "To see all the referrals, both ongoing and successful, click :guilabel:`Referrals`. The :guilabel:`My Referral` screen page displays all the referrals, with each individual referral housed in its own referral card." +msgstr "" + +#: ../../content/applications/hr/referrals/points.rst:32 +msgid "A successful referral displays a white :icon:`fa-check` :guilabel:`Hired` badge in the top-right corner of the card, along with a vertical green stripe on the left-side of the card. Referrals that are in process have a purple :guilabel:`In Progress` badge in the top-right corner." +msgstr "" + +#: ../../content/applications/hr/referrals/points.rst:36 +msgid "Each referral card lists the name of the applicant, the subject/application title as it appears on the applicant card in the *Recruitment* app, the name of the job position, the person responsible for filling the role (i.e. the recruiter), and the points earned." +msgstr "" + +#: ../../content/applications/hr/referrals/points.rst:40 +msgid "For referrals that have been hired, the selected avatar also appears on the card." +msgstr "" + +#: ../../content/applications/hr/referrals/points.rst:-1 +msgid "Two referral cards, one hired and one in-progress." +msgstr "" + +#: ../../content/applications/hr/referrals/points.rst:47 +msgid "Points" +msgstr "" + +#: ../../content/applications/hr/referrals/points.rst:49 +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/points.rst:53 +msgid "On each individual referral card, beneath the points earned, is a progress bar 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/points.rst:57 +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 :icon:`fa-check` :guilabel:`(checkmark)` appears next to the stage." +msgstr "" + +#: ../../content/applications/hr/referrals/points.rst:62 +msgid "The preconfigured point structure for referrals is as follows:" +msgstr "" + +#: ../../content/applications/hr/referrals/points.rst:64 +msgid ":guilabel:`Initial Qualification`: 1 point" +msgstr "" + +#: ../../content/applications/hr/referrals/points.rst:65 +msgid ":guilabel:`First Interview`: 20 points" +msgstr "" + +#: ../../content/applications/hr/referrals/points.rst:66 +msgid ":guilabel:`Second Interview`: 9 points" +msgstr "" + +#: ../../content/applications/hr/referrals/points.rst:67 +msgid ":guilabel:`Contract Proposal`: 5 points" +msgstr "" + +#: ../../content/applications/hr/referrals/points.rst:68 +msgid ":guilabel:`Contract Signed`: 50 points" +msgstr "" + +#: ../../content/applications/hr/referrals/points.rst:70 +msgid "The default total points earned for a referral that is hired is 85 points. Modifications of the points earned for each stage are made in the *Recruitment* application. Refer to the :ref:`Recruitment ` documentation to modify the points for each stage." +msgstr "" + #: ../../content/applications/hr/referrals/rewards.rst:3 msgid "Rewards" msgstr "" @@ -10317,7 +10765,7 @@ msgid "Odoo's *Time Off* application serves as a centralized hub for all time-of msgstr "" #: ../../content/applications/hr/time_off.rst:10 -msgid "Users can :doc:`request time off <../hr/time_off/request_time_off>`, and see an overview of their requests and time off balances. Managers can :ref:`allocate time off ` to individuals, teams, or the whole company, and :ref:`approve time off requests `." +msgid "Users can :doc:`request time off <../hr/time_off/request_time_off>`, and see an overview of their requests and time off balances. Managers can :doc:`allocate time off ` to individuals, teams, or the whole company, and :ref:`approve time off requests `." msgstr "" #: ../../content/applications/hr/time_off.rst:15 @@ -10828,188 +11276,46 @@ msgid "The Mandatory Days section with three configured days." msgstr "" #: ../../content/applications/hr/time_off.rst:435 -msgid "Allocate time off" -msgstr "" - -#: ../../content/applications/hr/time_off.rst:437 -msgid "Once time off types and accrual plans have been configured, the next step is to allocate, or give, time off to employees. This section is only visible to users who have either :guilabel:`Time Off Officer` or :guilabel:`Administrator` access rights for the *Time Off* application." -msgstr "" - -#: ../../content/applications/hr/time_off.rst:441 -msgid "To create a new allocation, navigate to :menuselection:`Time Off app --> Management --> Allocations`." -msgstr "" - -#: ../../content/applications/hr/time_off.rst:444 -msgid "This presents a list of all current allocations, including their respective statuses." -msgstr "" - -#: ../../content/applications/hr/time_off.rst:446 -msgid "Click :guilabel:`New` to allocate time off, and a blank allocation form appears." -msgstr "" - -#: ../../content/applications/hr/time_off.rst:448 -msgid "After entering a name for the allocation on the first blank field of the form, enter the following information:" -msgstr "" - -#: ../../content/applications/hr/time_off.rst:451 -msgid ":guilabel:`Time Off Type`: using the drop-down menu, select the type of time off that is being allocated to the employees." -msgstr "" - -#: ../../content/applications/hr/time_off.rst:453 -msgid ":guilabel:`Allocation Type`: select either :guilabel:`Regular Allocation` or :guilabel:`Accrual Allocation`. If the allocation is **not** based on an accrual plan, select :guilabel:`Regular Allocation`." -msgstr "" - -#: ../../content/applications/hr/time_off.rst:456 -msgid ":guilabel:`Accrual Plan`: if :guilabel:`Accrual Allocation` is selected for the :guilabel:`Allocation Type`, the :guilabel:`Accrual Plan` field appears. Using the drop-down menu, select the accrual plan with which the allocation is associated. An accrual plan **must** be selected for an :guilabel:`Accrual Allocation`." -msgstr "" - -#: ../../content/applications/hr/time_off.rst:460 -msgid ":guilabel:`Validity Period/Start Date`: if :guilabel:`Regular Allocation` is selected for the :guilabel:`Allocation Type`, this field is labeled :guilabel:`Validity Period`. If :guilabel:`Accrual Allocation` is selected for the :guilabel:`Allocation Type`, this field is labeled :guilabel:`Start Date`." -msgstr "" - -#: ../../content/applications/hr/time_off.rst:465 -msgid "The current date populates the first date field by default. To select another date, click on the pre-populated date to reveal a popover calendar window. Navigate to the desired start date for the allocation, and click on the date to select it." -msgstr "" - -#: ../../content/applications/hr/time_off.rst:469 -msgid "If the allocation expires, select the expiration date in the next date field. If the time off does *not* expire, leave the second date field blank. `No Limit` appears in the field if no date is selected." -msgstr "" - -#: ../../content/applications/hr/time_off.rst:473 -msgid "If :guilabel:`Accrual Allocation` is selected for the :guilabel:`Allocation Type`, this second field is labeled :guilabel:`Run until`." -msgstr "" - -#: ../../content/applications/hr/time_off.rst:475 -msgid ":guilabel:`Allocation`: enter the amount of time that is being allocated to the employees. This field displays the time in either :guilabel:`Hours` or :guilabel:`Days`, depending on how the selected :ref:`Time Off Type ` is configured (in hours or days)." -msgstr "" - -#: ../../content/applications/hr/time_off.rst:478 -msgid ":guilabel:`Mode`: using the drop-down menu, select how the allocation is assigned. This selection determines who receives the time off allocation. The options are :guilabel:`By Employee`, :guilabel:`By Company`, :guilabel:`By Department`, or :guilabel:`By Employee Tag`." -msgstr "" - -#: ../../content/applications/hr/time_off.rst:482 -msgid "Depending on what is selected for the :guilabel:`Mode`, this following field is labeled either: :guilabel:`Employees`, :guilabel:`Company`, :guilabel:`Department`, or :guilabel:`Employee Tag`." -msgstr "" - -#: ../../content/applications/hr/time_off.rst:485 -msgid "Using the drop-down menu, indicate the specific employees, company, department, or employee tags who are receiving this time off." -msgstr "" - -#: ../../content/applications/hr/time_off.rst:488 -msgid "Multiple selections can be made for either :guilabel:`Employees` or :guilabel:`Employee Tag`." -msgstr "" - -#: ../../content/applications/hr/time_off.rst:490 -msgid "Only one selection can be made for the :guilabel:`Company` or :guilabel:`Department`." -msgstr "" - -#: ../../content/applications/hr/time_off.rst:491 -msgid ":guilabel:`Add a reason...`: if any description or note is necessary to explain the time off allocation, enter it in this field at the bottom of the form." -msgstr "" - -#: ../../content/applications/hr/time_off.rst:-1 -msgid "A new allocation form with all the fields filled out for the annual two week vacation\n" -"granted to all employees." -msgstr "" - -#: ../../content/applications/hr/time_off.rst:502 -msgid "Request allocation" -msgstr "" - -#: ../../content/applications/hr/time_off.rst:504 -msgid "If an employee has used all their time off, or is going to run out of time off, they can request an allocation for additional time. Allocations can be requested in one of two ways, either from the :ref:`Dashboard ` or the :ref:`My Allocations ` view." -msgstr "" - -#: ../../content/applications/hr/time_off.rst:508 -msgid "To create a new allocation request, click either the :guilabel:`New Allocation Request` button on the main *Time Off* dashboard, or the :guilabel:`New` button in the :guilabel:`My Allocations` list view. Both buttons open a new allocation request form." -msgstr "" - -#: ../../content/applications/hr/time_off.rst:513 -msgid "Both :guilabel:`New` buttons open a :guilabel:`New Allocation` request form, but when requested from the :guilabel:`Dashboard`, the form appears in a modal. When requested from the :guilabel:`My Allocations` list view, the screen navigates to a new allocation request page, instead." -msgstr "" - -#: ../../content/applications/hr/time_off.rst:518 -msgid "Enter the following information on the :guilabel:`New Allocation` request form:" -msgstr "" - -#: ../../content/applications/hr/time_off.rst:520 -msgid ":guilabel:`Time Off Type`: select the type of time off being requested for the allocation from the drop-down menu. After a selection is made, the title updates with the time off type." -msgstr "" - -#: ../../content/applications/hr/time_off.rst:522 -msgid ":guilabel:`Validity Period`: this field **only** appears if requesting an allocation with a time off type that has the :guilabel:`Take Time Off in` field :ref:`configured ` to either :guilabel:`Day` or :guilabel:`Half Day`. This field does **not** appear if the :guilabel:`Take Time Off in` field is set to :guilabel:`Hours`." -msgstr "" - -#: ../../content/applications/hr/time_off.rst:527 -msgid "Using the calendar selector, select a start and end date the allocation is valid for. By default, the current date populates the first field, and :guilabel:`No Limit` populates the second field." -msgstr "" - -#: ../../content/applications/hr/time_off.rst:530 -msgid "Adjust both of these dates, if desired." -msgstr "" - -#: ../../content/applications/hr/time_off.rst:531 -msgid ":guilabel:`Allocation`: enter the amount of time being requested in this field. The format is presented in either days or hours, depending on how the time off type is configured. Once this field is populated, the name of the allocation request is updated to include the amount of time being requested." -msgstr "" - -#: ../../content/applications/hr/time_off.rst:535 -msgid ":guilabel:`Add a reason...`: enter a description for the allocation request. This should include any details that managers and approvers may need in order to approve the request." -msgstr "" - -#: ../../content/applications/hr/time_off.rst:538 -msgid "If the request was created from the :guilabel:`Dashboard`, click the :guilabel:`Save & Close` button to save the information and submit the request." -msgstr "" - -#: ../../content/applications/hr/time_off.rst:541 -msgid "If the form was completed from the :guilabel:`My Allocations` list view, the information is automatically saved as it is entered. However, the form can be saved manually at any time by clicking the *save manually* button, represented by a :guilabel:`(cloud upload)` icon." -msgstr "" - -#: ../../content/applications/hr/time_off.rst:-1 -msgid "An allocation request form filled out for an employee requesting an additional week of\n" -"sick time." -msgstr "" - -#: ../../content/applications/hr/time_off.rst:553 msgid "To view a color-coded schedule of the user's time off, and/or of the team managed by them, navigate to :menuselection:`Time Off app --> Overview`. This presents a calendar with the default filter of `My Team`, in a month view." msgstr "" -#: ../../content/applications/hr/time_off.rst:557 +#: ../../content/applications/hr/time_off.rst:439 msgid "To change the time period displayed, click on the :guilabel:`Month` button to reveal a drop-down menu. Then, select either :guilabel:`Day`, :guilabel:`Week`, or :guilabel:`Year` to present the calendar in that corresponding view." msgstr "" -#: ../../content/applications/hr/time_off.rst:561 +#: ../../content/applications/hr/time_off.rst:443 msgid "To navigate forward or backward in time, in the selected increment (:guilabel:`Month`, :guilabel:`Week`, etc.), click the :guilabel:`← (left arrow)` or :guilabel:`→ (right arrow)` to move either forward or backward in that specified amount of time." msgstr "" -#: ../../content/applications/hr/time_off.rst:565 +#: ../../content/applications/hr/time_off.rst:447 msgid "For example, if :guilabel:`Month` is selected, the arrows adjust the view by one month." msgstr "" -#: ../../content/applications/hr/time_off.rst:567 +#: ../../content/applications/hr/time_off.rst:449 msgid "To return to a view containing the current day, click the :guilabel:`Today` button at any time." msgstr "" -#: ../../content/applications/hr/time_off.rst:569 +#: ../../content/applications/hr/time_off.rst:451 msgid "Team members are listed alphabetically on individual lines, and their requested time off, regardless of the status (*validated* or *to approve*), is visible on the calendar." msgstr "" -#: ../../content/applications/hr/time_off.rst:572 +#: ../../content/applications/hr/time_off.rst:454 msgid "Each employee is color-coded. The employee's color is selected at random, and does *not* correspond to the type of time off they requested." msgstr "" -#: ../../content/applications/hr/time_off.rst:575 +#: ../../content/applications/hr/time_off.rst:457 msgid "The status of the time off is represented by the color detail of the request, either appearing solid (*validated*) or striped (*to approve*)." msgstr "" -#: ../../content/applications/hr/time_off.rst:578 +#: ../../content/applications/hr/time_off.rst:460 msgid "The number of days or hours requested is written on the request (if there is enough space)." msgstr "" -#: ../../content/applications/hr/time_off.rst:580 +#: ../../content/applications/hr/time_off.rst:462 msgid "At the bottom of the calendar, in the :guilabel:`Total` line, a bar graph shows how many people are projected to be out on any given day. The number on each individual bar represents the number of employees out for those highlighted days." msgstr "" -#: ../../content/applications/hr/time_off.rst:584 +#: ../../content/applications/hr/time_off.rst:466 msgid "Click on a time off entry to view the details for the specific time off entry. The total number of hours or days are listed, along with the start and end time of the time off. To view the details of the time off request in a modal, click the :guilabel:`View` button." msgstr "" @@ -11017,31 +11323,31 @@ msgstr "" msgid "Overview of the user's team, with time off requests shown." msgstr "" -#: ../../content/applications/hr/time_off.rst:597 +#: ../../content/applications/hr/time_off.rst:479 msgid "The reporting feature allows users to view time off for their team, either by employee or type of time off. This allows users to see which employees are taking time off, how much time off they are taking, and what time off types are being used." msgstr "" -#: ../../content/applications/hr/time_off.rst:601 +#: ../../content/applications/hr/time_off.rst:483 msgid "Any report can be added to a spreadsheet through the *Insert in Spreadsheet* button that appears in the top-left of a report. If the *Documents* application is installed, an option to add the report to a spreadsheet appears. If not, the report can be added to a *Dashboard*." msgstr "" -#: ../../content/applications/hr/time_off.rst:606 +#: ../../content/applications/hr/time_off.rst:488 msgid "By employee" msgstr "" -#: ../../content/applications/hr/time_off.rst:608 +#: ../../content/applications/hr/time_off.rst:490 msgid "To view a report of employee time off requests, navigate to :menuselection:`Time Off app --> Reporting --> by Employee`." msgstr "" -#: ../../content/applications/hr/time_off.rst:611 +#: ../../content/applications/hr/time_off.rst:493 msgid "The default report presents the current year's data in a list view, displaying all the employees in alphabetical order. Each employee's line is collapsed by default. To expand a line, click anywhere on the line." msgstr "" -#: ../../content/applications/hr/time_off.rst:615 +#: ../../content/applications/hr/time_off.rst:497 msgid "The view expands, and has the time off requests organized by time off type. Click anywhere on a time off type line to expand it, and view all the individual time off requests that fall under that type." msgstr "" -#: ../../content/applications/hr/time_off.rst:618 +#: ../../content/applications/hr/time_off.rst:500 msgid "The information shown in the list includes: the :guilabel:`Employee` name, :guilabel:`Number of Days` off requested, the :guilabel:`Start Date`, :guilabel:`End Date`, :guilabel:`Status`, and :guilabel:`Description`." msgstr "" @@ -11049,7 +11355,7 @@ msgstr "" msgid "Report of time off, shown by each employee in a list view." msgstr "" -#: ../../content/applications/hr/time_off.rst:626 +#: ../../content/applications/hr/time_off.rst:508 msgid "The report can be displayed in other ways, as well. Click the corresponding button option in the top-right corner of the page to view the data in that specific way. The various options are a :guilabel:`List` (the default view), :guilabel:`Graph`, :guilabel:`Pivot` table, or :guilabel:`Calendar` view." msgstr "" @@ -11057,19 +11363,19 @@ msgstr "" msgid "The various other views highlighted, for the employee time off report." msgstr "" -#: ../../content/applications/hr/time_off.rst:635 +#: ../../content/applications/hr/time_off.rst:517 msgid "When a selection has been made, additional options appear for that particular selection. For more detailed information on the reports and their various options, refer to the :doc:`reporting <../essentials/reporting>` documentation." msgstr "" -#: ../../content/applications/hr/time_off.rst:640 +#: ../../content/applications/hr/time_off.rst:522 msgid "By type" msgstr "" -#: ../../content/applications/hr/time_off.rst:642 +#: ../../content/applications/hr/time_off.rst:524 msgid "To view a list of all time off, organized by time off type, navigate to :menuselection:`Time Off app --> Reporting --> by Type`. This shows all time off requests in a default bar chart." msgstr "" -#: ../../content/applications/hr/time_off.rst:645 +#: ../../content/applications/hr/time_off.rst:527 msgid "Hover over a bar to view the :guilabel:`Duration (Days)` of that specific time off type." msgstr "" @@ -11078,34 +11384,180 @@ msgid "The various time off types, and how many days requested, in a bar chart. "highlighted in a red box." msgstr "" -#: ../../content/applications/hr/time_off.rst:652 +#: ../../content/applications/hr/time_off.rst:534 msgid "Click on a bar to go to a detailed list view of all the time off requests for that time off type." msgstr "" -#: ../../content/applications/hr/time_off.rst:654 +#: ../../content/applications/hr/time_off.rst:536 msgid "Each request is listed, with the following information displayed: the :guilabel:`Employee`, :guilabel:`Number of Days`, :guilabel:`Request Type`, :guilabel:`Start Date`, :guilabel:`End Date`, :guilabel:`Status`, and the :guilabel:`Description`." msgstr "" -#: ../../content/applications/hr/time_off.rst:658 +#: ../../content/applications/hr/time_off.rst:540 msgid "The report can be displayed in other ways, as well. Click the corresponding button option in the top-right corner of the page to view the data in that way. The various options are a :guilabel:`Graph` (the default view), :guilabel:`List`, or :guilabel:`Pivot` table." msgstr "" -#: ../../content/applications/hr/time_off.rst:662 +#: ../../content/applications/hr/time_off.rst:544 msgid "When a selection has been made, additional options appear for that particular selection. For more detailed information on the reports, and their various options, refer to the :doc:`reporting <../essentials/reporting>` documentation." msgstr "" -#: ../../content/applications/hr/time_off.rst:667 +#: ../../content/applications/hr/time_off.rst:549 +msgid ":doc:`time_off/allocations`" +msgstr "" + +#: ../../content/applications/hr/time_off.rst:550 msgid ":doc:`time_off/request_time_off`" msgstr "" -#: ../../content/applications/hr/time_off.rst:668 +#: ../../content/applications/hr/time_off.rst:551 msgid ":doc:`time_off/my_time`" msgstr "" -#: ../../content/applications/hr/time_off.rst:669 +#: ../../content/applications/hr/time_off.rst:552 msgid ":doc:`time_off/management`" msgstr "" +#: ../../content/applications/hr/time_off/allocations.rst:3 +msgid "Allocations" +msgstr "" + +#: ../../content/applications/hr/time_off/allocations.rst:5 +msgid "Once :ref:`time off types ` and :ref:`accrual plans ` have been configured, the next step is to *allocate*, or give, time off to employees." +msgstr "" + +#: ../../content/applications/hr/time_off/allocations.rst:9 +msgid "The *Allocations* section of the *Time Off* app is **only** visible to users who have either :guilabel:`Time Off Officer` or :guilabel:`Administrator` access rights for the *Time Off* application. For more information on access rights, refer to the :doc:`access rights <../../general/users/access_rights/>` documentation." +msgstr "" + +#: ../../content/applications/hr/time_off/allocations.rst:15 +msgid "Allocate time off" +msgstr "" + +#: ../../content/applications/hr/time_off/allocations.rst:17 +msgid "To create a new allocation, navigate to :menuselection:`Time Off app --> Management --> Allocations`." +msgstr "" + +#: ../../content/applications/hr/time_off/allocations.rst:20 +msgid "This presents a list of all current allocations, including their respective statuses." +msgstr "" + +#: ../../content/applications/hr/time_off/allocations.rst:22 +msgid "Click :guilabel:`New` to allocate time off, and a blank allocation form appears." +msgstr "" + +#: ../../content/applications/hr/time_off/allocations.rst:24 +msgid "After entering a name for the allocation on the first blank field of the form, enter the following information:" +msgstr "" + +#: ../../content/applications/hr/time_off/allocations.rst:27 +msgid ":guilabel:`Time Off Type`: using the drop-down menu, select the type of time off that is being allocated to the employees." +msgstr "" + +#: ../../content/applications/hr/time_off/allocations.rst:29 +msgid ":guilabel:`Allocation Type`: select either :guilabel:`Regular Allocation` or :guilabel:`Accrual Allocation`. If the allocation is **not** based on an :ref:`accrual plan `, select :guilabel:`Regular Allocation`." +msgstr "" + +#: ../../content/applications/hr/time_off/allocations.rst:32 +msgid ":guilabel:`Accrual Plan`: if :guilabel:`Accrual Allocation` is selected for the :guilabel:`Allocation Type`, the :guilabel:`Accrual Plan` field appears. Using the drop-down menu, select the accrual plan with which the allocation is associated. An accrual plan **must** be selected for an :guilabel:`Accrual Allocation`." +msgstr "" + +#: ../../content/applications/hr/time_off/allocations.rst:36 +msgid ":guilabel:`Validity Period/Start Date`: if :guilabel:`Regular Allocation` is selected for the :guilabel:`Allocation Type`, this field is labeled :guilabel:`Validity Period`. If :guilabel:`Accrual Allocation` is selected for the :guilabel:`Allocation Type`, this field is labeled :guilabel:`Start Date`." +msgstr "" + +#: ../../content/applications/hr/time_off/allocations.rst:41 +msgid "The current date populates the first date field, by default. To select another date, click on the pre-populated date to reveal a popover calendar window. Navigate to the desired start date for the allocation, and click on the date to select it." +msgstr "" + +#: ../../content/applications/hr/time_off/allocations.rst:45 +msgid "If the allocation expires, select the expiration date in the next date field. If the time off does *not* expire, leave the second date field blank. :guilabel:`No Limit` appears in the field if no date is selected." +msgstr "" + +#: ../../content/applications/hr/time_off/allocations.rst:49 +msgid "If :guilabel:`Accrual Allocation` is selected for the :guilabel:`Allocation Type`, this second field is labeled :guilabel:`Run until`." +msgstr "" + +#: ../../content/applications/hr/time_off/allocations.rst:51 +msgid ":guilabel:`Allocation`: enter the amount of time that is being allocated to the employees. This field displays the time in either :guilabel:`Hours` or :guilabel:`Days`, depending on how the selected :ref:`Time Off Type ` is configured." +msgstr "" + +#: ../../content/applications/hr/time_off/allocations.rst:54 +msgid ":guilabel:`Mode`: using the drop-down menu, select how the allocation is assigned. This selection determines who receives the time off allocation. The options are :guilabel:`By Employee`, :guilabel:`By Company`, :guilabel:`By Department`, or :guilabel:`By Employee Tag`." +msgstr "" + +#: ../../content/applications/hr/time_off/allocations.rst:58 +msgid "Depending on what is selected for the :guilabel:`Mode`, the following field is labeled either: :guilabel:`Employees`, :guilabel:`Company`, :guilabel:`Department`, or :guilabel:`Employee Tag`." +msgstr "" + +#: ../../content/applications/hr/time_off/allocations.rst:61 +msgid "Using the drop-down menu, indicate the specific employees, company, department, or employee tags receiving this time off." +msgstr "" + +#: ../../content/applications/hr/time_off/allocations.rst:64 +msgid "Multiple selections can be made for either :guilabel:`Employees` or :guilabel:`Employee Tag`." +msgstr "" + +#: ../../content/applications/hr/time_off/allocations.rst:66 +msgid "Only one selection can be made for the :guilabel:`Company` or :guilabel:`Department`." +msgstr "" + +#: ../../content/applications/hr/time_off/allocations.rst:67 +msgid ":guilabel:`Add a reason...`: if any description or note is necessary to explain the time off allocation, enter it in this field at the bottom of the form." +msgstr "" + +#: ../../content/applications/hr/time_off/allocations.rst:-1 +msgid "A new allocation form with all the fields filled out for the annual two week vacation\n" +"granted to all employees." +msgstr "" + +#: ../../content/applications/hr/time_off/allocations.rst:78 +msgid "Request allocation" +msgstr "" + +#: ../../content/applications/hr/time_off/allocations.rst:80 +msgid "If an employee has used all their time off, or will run out of time off, they can request an allocation for additional time. Allocations can be requested in one of two ways, either from the :ref:`Dashboard ` or the :ref:`My Allocations ` view." +msgstr "" + +#: ../../content/applications/hr/time_off/allocations.rst:84 +msgid "To create a new allocation request, click either the :guilabel:`New Allocation Request` button on the main *Time Off* dashboard, or the :guilabel:`New` button in the :guilabel:`My Allocations` list view. Both buttons open a new allocation request form." +msgstr "" + +#: ../../content/applications/hr/time_off/allocations.rst:89 +msgid "Both options open a new allocation request form, but when requested from the :guilabel:`Dashboard`, the form appears in a pop-up window. When requested from the :guilabel:`My Allocations` list view, the screen navigates to a new allocation request page, instead." +msgstr "" + +#: ../../content/applications/hr/time_off/allocations.rst:94 +msgid "Enter the following information on the new allocation request form:" +msgstr "" + +#: ../../content/applications/hr/time_off/allocations.rst:96 +msgid ":guilabel:`Time Off Type`: select the type of time off being requested for the allocation from the drop-down menu. After a selection is made, the title updates with the time off type." +msgstr "" + +#: ../../content/applications/hr/time_off/allocations.rst:98 +msgid ":guilabel:`Validity Period`: using the calendar selector, select a start and end date the allocation is valid for. By default, the current date populates the first field, and :guilabel:`No Limit` populates the second field. Adjust both of these dates, if desired." +msgstr "" + +#: ../../content/applications/hr/time_off/allocations.rst:101 +msgid ":guilabel:`Allocation`: enter the amount of time being requested in this field. The format is presented in either :guilabel:`Days` or :guilabel:`Hours`, depending on how the :guilabel:`Time Off Type` is configured. Once this field is populated, the name of the allocation request is updated to include the amount of time being requested." +msgstr "" + +#: ../../content/applications/hr/time_off/allocations.rst:105 +msgid ":guilabel:`Add a reason...`: enter a description for the allocation request. This should include any details that approvers may need to approve the request." +msgstr "" + +#: ../../content/applications/hr/time_off/allocations.rst:108 +msgid "If the request was created from the :guilabel:`Dashboard`, click the :guilabel:`Save & Close` button on the :guilabel:`New Allocation` pop-up window to save the information and submit the request." +msgstr "" + +#: ../../content/applications/hr/time_off/allocations.rst:111 +msgid "If the form was completed from the :guilabel:`My Allocations` list view, the information is automatically saved as it is entered. However, the form can be saved manually at any time by clicking the :icon:`fa-cloud-upload` :guilabel:`(cloud upload)` icon." +msgstr "" + +#: ../../content/applications/hr/time_off/allocations.rst:-1 +msgid "An allocation request form filled out for an employee requesting an additional week of\n" +"sick time." +msgstr "" + #: ../../content/applications/hr/time_off/management.rst:3 msgid "Management" msgstr "" diff --git a/locale/sources/inventory_and_mrp.pot b/locale/sources/inventory_and_mrp.pot index 2827ee95f..baf9bc73d 100644 --- a/locale/sources/inventory_and_mrp.pot +++ b/locale/sources/inventory_and_mrp.pot @@ -8,7 +8,7 @@ msgid "" msgstr "" "Project-Id-Version: Odoo 17.0\n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2024-06-24 07:08+0000\n" +"POT-Creation-Date: 2024-07-23 13:30+0000\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME \n" "Language-Team: LANGUAGE \n" @@ -502,7 +502,6 @@ msgstr "" #: ../../content/applications/inventory_and_mrp/barcode/operations/barcode_nomenclature.rst:195 #: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:189 #: ../../content/applications/inventory_and_mrp/barcode/operations/gs1_nomenclature.rst:189 -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/warehouses_locations.rst:20 msgid "Location" msgstr "" @@ -1161,16 +1160,14 @@ msgstr "" #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/cluster_picking.rst:48 #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/cross_dock.rst:18 #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/putaway.rst:21 -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/putaway.rst:104 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/putaway.rst:106 #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/wave_transfers.rst:16 -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/create_a_second_warehouse.rst:13 #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/cycle_counts.rst:15 #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/resupply_warehouses.rst:11 -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/scrap_inventory.rst:27 -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_locations.rst:15 -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/warehouses_locations.rst:46 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_locations.rst:8 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/warehouses.rst:12 #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/integrating_landed_costs.rst:20 -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:38 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:44 #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/removal_strategies.rst:45 #: ../../content/applications/inventory_and_mrp/manufacturing/advanced_configuration/work_order_dependencies.rst:13 #: ../../content/applications/inventory_and_mrp/manufacturing/subcontracting.rst:52 @@ -1182,7 +1179,6 @@ msgstr "" #: ../../content/applications/inventory_and_mrp/manufacturing/subcontracting/subcontracting_resupply.rst:40 #: ../../content/applications/inventory_and_mrp/manufacturing/workflows/allocation.rst:21 #: ../../content/applications/inventory_and_mrp/manufacturing/workflows/byproducts.rst:21 -#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/use_mps.rst:11 #: ../../content/applications/inventory_and_mrp/manufacturing/workflows/work_center_time_off.rst:15 #: ../../content/applications/inventory_and_mrp/purchase/manage_deals/calls_for_tenders.rst:26 #: ../../content/applications/inventory_and_mrp/purchase/manage_deals/control_bills.rst:17 @@ -2704,8 +2700,8 @@ msgid "When no route is selected, Odoo selects the :guilabel:`Route` specified i msgstr "" #: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/reordering_rules.rst:233 -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:209 -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:228 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:215 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:234 msgid "Manual" msgstr "" @@ -2830,7 +2826,6 @@ msgid "In Odoo, there are two strategies for automatically replenishing inventor msgstr "" #: ../../content/applications/inventory_and_mrp/inventory/product_management/product_replenishment/strategies.rst:16 -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/warehouses_locations.rst:6 msgid "Terminology" msgstr "" @@ -7924,14 +7919,18 @@ msgid "To begin, go to the `Bpost website `_ accounts." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/bpost.rst:37 msgid "After completing the setup, get the Bpost account ID and passphrase, by navigating to the :guilabel:`Shipping Manager` menu item." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/bpost.rst:36 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/bpost.rst:42 msgid "On the :guilabel:`Shipping Manager` page, go to the :guilabel:`Admin` tab, then the :guilabel:`General Settings` tab, to find the :guilabel:`Account ID` and :guilabel:`Passphrase` needed to configure Odoo's shipping method." msgstr "" @@ -7939,83 +7938,83 @@ msgstr "" msgid "In the *Admin* tab, show the Account ID and Passphrase." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/bpost.rst:45 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/bpost.rst:51 msgid "Configure Bpost shipping method" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/bpost.rst:47 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/bpost.rst:53 msgid "With those necessary credentials, configure the Bpost shipping method in Odoo by going to :menuselection:`Inventory app --> Configuration --> Shipping Methods`." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/bpost.rst:50 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/bpost.rst:56 msgid "On the :guilabel:`Shipping Methods` page, click :guilabel:`Create`." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/bpost.rst:52 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/bpost.rst:58 msgid "In the :guilabel:`Provider` field, select :guilabel:`Bpost` from the drop-down menu. Doing so reveals the :guilabel:`Bpost Configuration` tab at the bottom of the form, where the Bpost credentials can be entered." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/bpost.rst:56 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/bpost.rst:62 msgid "For details on configuring the other fields on the shipping method, such as :guilabel:`Delivery Product`, refer to the :doc:`Configure third-party carrier ` documentation." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/bpost.rst:60 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/bpost.rst:66 msgid "To generate Bpost :doc:`shipping labels ` through Odoo, ensure the :guilabel:`Integration Level` option is set to :guilabel:`Get Rate and Create Shipment`." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/bpost.rst:63 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/bpost.rst:69 msgid "In the :guilabel:`Bpost Configuration` tab, complete the following fields:" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/bpost.rst:65 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/bpost.rst:71 msgid ":guilabel:`Bpost Account Number` (required field): enter the company's unique :ref:`account ID ` from the Bpost website." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/bpost.rst:67 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/bpost.rst:73 msgid ":guilabel:`Passphrase` (required field): enter the :ref:`passphrase ` from the Bpost website." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/bpost.rst:69 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/bpost.rst:75 msgid ":guilabel:`Bpost Delivery Nature`: select either :guilabel:`Domestic` or :guilabel:`International` shipping services. Choosing :guilabel:`Domestic` shows the :guilabel:`Options` section, while :guilabel:`International` enables the :guilabel:`Bpost Shipment Type` and :guilabel:`Bpost Parcel Return Instructions` fields." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/bpost.rst:73 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/bpost.rst:79 msgid ":guilabel:`Bpost Package Type`: select the type of shipping service from the drop-down menu." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/bpost.rst:75 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/bpost.rst:81 msgid "For `domestic delivery `_, the options are: :guilabel:`bpack 24h Pro`, :guilabel:`bpack 24h business`, or :guilabel:`bpack Bus`." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/bpost.rst:80 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/bpost.rst:86 msgid "For `international delivery `_, the options are: :guilabel:`bpack World Express Pro`, :guilabel:`bpack World Business`, or :guilabel:`bpack Europe Business`." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/bpost.rst:83 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/bpost.rst:89 msgid ":guilabel:`Bpost Shipment Type` (required field): for international deliveries, declare the type of goods in the package as :guilabel:`SAMPLE`, :guilabel:`GIFT`, :guilabel:`GOODS`, :guilabel:`DOCUMENTS`, or :guilabel:`OTHER`." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/bpost.rst:86 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/bpost.rst:92 msgid ":guilabel:`Bpost Parcel Return Address`: return address when an international shipment fails to deliver. Select from the drop-down menu: :guilabel:`Destroy`, :guilabel:`Return to sender by air`, or :guilabel:`Return to sender by road`." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/bpost.rst:89 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/bpost.rst:95 msgid ":guilabel:`Label Type`: choose :guilabel:`A6` or :guilabel:`A4` label sizes from the drop-down menu." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/bpost.rst:91 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/bpost.rst:97 msgid ":guilabel:`Label Format`: choose :guilabel:`PDF` or :guilabel:`PNG` from the drop-down menu." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/bpost.rst:93 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/bpost.rst:99 msgid "For domestic deliveries, these features are available in the :guilabel:`Options` section:" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/bpost.rst:95 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/bpost.rst:101 msgid "Enable the :guilabel:`Delivery on Saturday` feature to include Saturdays as possible delivery dates. Depending on the :guilabel:`Bpost Package Type` selected, this option might incur additional costs to the company." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/bpost.rst:98 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/bpost.rst:104 msgid "Enable the :guilabel:`Generate Return Label` feature to automatically print a return label upon validating the delivery order." msgstr "" @@ -8763,30 +8762,66 @@ msgid "Additionally, the tracking number is now available." msgstr "" #: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/sendcloud_shipping.rst:217 -msgid "When return labels are created, Sendcloud will automatically charge the configured Sendcloud account." +msgid "When return labels are created, Sendcloud automatically charges the configured Sendcloud account." msgstr "" #: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/sendcloud_shipping.rst:221 -msgid "FAQ" +msgid "Shipping rules" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/sendcloud_shipping.rst:224 -msgid "Shipment is too heavy" +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/sendcloud_shipping.rst:223 +msgid "Optionally, create shipping rules to automatically generate shipping labels tailored to different product needs. For example, a shipping rule can be created for customers shipping expensive jewelry items to purchase insurance." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/sendcloud_shipping.rst:226 -msgid "If the shipment is too heavy for the Sendcloud service that is configured, then the weight is split to simulate multiple packages. Products will need to be put in different :guilabel:`Packages` to :guilabel:`Validate` the transfer and generate labels." +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/sendcloud_shipping.rst:227 +msgid "To use shipping rules, navigate to :menuselection:`Inventory app --> Configuration --> Delivery: Shipping Methods`, and select the intended `Sendcloud` shipping method." msgstr "" #: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/sendcloud_shipping.rst:230 +msgid "Under the :guilabel:`Sendcloud Configuration` tab, in the :guilabel:`OPTIONS` section, choose the kind of shipments the shipping rules apply to, via the :guilabel:`Use Sendcloud shipping rules` field." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/sendcloud_shipping.rst:234 +msgid "From here, choose either: :guilabel:`Shipping` to customers, :guilabel:`Returns` from customers, or :guilabel:`Both`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/sendcloud_shipping.rst:-1 +msgid "Use Shipping Rules field." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/sendcloud_shipping.rst:241 +msgid "Then, in the Sendcloud website, navigate to :menuselection:`Settings --> Shipping rules`. Create a new shipping rule by clicking :guilabel:`Create New`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/sendcloud_shipping.rst:244 +msgid "In the :guilabel:`Actions` section, set a :guilabel:`Condition` to determine when the rule applies. Then, configure what to do when packages meet the condition." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/sendcloud_shipping.rst:248 +msgid "`Create shipping rules on Sendcloud `_" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/sendcloud_shipping.rst:252 +msgid "FAQ" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/sendcloud_shipping.rst:255 +msgid "Shipment is too heavy" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/sendcloud_shipping.rst:257 +msgid "If the shipment is too heavy for the Sendcloud service that is configured, then the weight is split to simulate multiple packages. Products will need to be put in different :guilabel:`Packages` to :guilabel:`Validate` the transfer and generate labels." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/sendcloud_shipping.rst:261 msgid ":guilabel:`Rules` can also be set up in Sendcloud to use other shipping methods when the weight is too heavy. However, note that these rules will not apply to the shipping price calculation on the calculation on the sales order." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/sendcloud_shipping.rst:235 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/sendcloud_shipping.rst:266 msgid "Personal carrier contract" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/sendcloud_shipping.rst:237 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/sendcloud_shipping.rst:268 msgid "Use custom prices from a direct carrier contract, via CSV upload, by first logging into Sendcloud, navigating to :menuselection:`Settings --> Carriers --> My contracts`, and then selecting the intended contract." msgstr "" @@ -8794,11 +8829,11 @@ msgstr "" msgid "Navigate to the contracts section in Sendcloud." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/sendcloud_shipping.rst:245 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/sendcloud_shipping.rst:276 msgid "Under the :guilabel:`Contract prices` section, click :guilabel:`Download CSV` and fill out the contract prices in the :guilabel:`price` column of the CSV file template." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/sendcloud_shipping.rst:249 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/sendcloud_shipping.rst:280 msgid "Ensure the CSV file includes the correct prices to avoid any inaccuracies." msgstr "" @@ -8806,35 +8841,35 @@ msgstr "" msgid "Show sample contract CSV from Sendcloud, highlighting the price column." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/sendcloud_shipping.rst:255 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/sendcloud_shipping.rst:286 msgid ":guilabel:`Upload` the completed CSV file to Sendcloud, then click :guilabel:`Save these prices`." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/sendcloud_shipping.rst:258 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/sendcloud_shipping.rst:289 msgid "`Sendcloud: How to upload contract prices with carriers `_" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/sendcloud_shipping.rst:262 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/sendcloud_shipping.rst:293 msgid "Measuring volumetric weight" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/sendcloud_shipping.rst:264 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/sendcloud_shipping.rst:295 msgid "Many carriers have several measures for weight. There is the actual weight of the products in the parcel, and there is the *volumetric weight* (:dfn:`Volumetric weight is the volume that a package occupies when in transit. In other words it is the physical size of a package`)." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/sendcloud_shipping.rst:269 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/sendcloud_shipping.rst:300 msgid "Check to see if selected carrier(s) already have defined formulas to compute the volumetric weight." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/sendcloud_shipping.rst:273 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/sendcloud_shipping.rst:304 msgid "`Sendcloud: How to calculate & automate parcel volumetric weight `_" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/sendcloud_shipping.rst:277 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/sendcloud_shipping.rst:308 msgid "Unable to calculate shipping rate" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/sendcloud_shipping.rst:279 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/sendcloud_shipping.rst:310 msgid "First, verify that the product being shipped has a weight that is supported by the selected shipping method. If this is set, then verify that the destination country (from the customer address) is supported by the carrier. The country of origin (warehouse address) should also be supported by the carrier." msgstr "" @@ -9809,6 +9844,216 @@ msgstr "" msgid ":guilabel:`Duties paid by`: Select whether duties or other fees are charged to the :guilabel:`Sender` or :guilabel:`Recipient` of the order." msgstr "" +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/zebra.rst:3 +msgid "Zebra label configuration" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/zebra.rst:7 +msgid "In Odoo, labels printed in the Zebra Programming Language (ZPL) file format are designed to fit a four-by-six inch label. To resize (or reformat) text to fit a variety of |ZPL| label sizes, :ref:`navigate to the ZPL label view `, and alter the |ZPL| code." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/zebra.rst:13 +msgid "When customizing code in Odoo, please note that upgrading the database to newer versions may break custom |ZPL| code. **Customers are responsible for maintaining their custom code**." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/zebra.rst:16 +msgid "Refer to the following sections for explanations, and example code, for frequently requested Zebra label customizations." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/zebra.rst:19 +msgid ":ref:`Adjust margins `" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/zebra.rst:20 +msgid ":ref:`Enlarge/minimize barcodes `" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/zebra.rst:21 +msgid ":ref:`Rotate elements `" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/zebra.rst:26 +msgid "Navigate to ZPL label view" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/zebra.rst:28 +msgid "To begin customizing a Zebra label in Odoo, turn on :ref:`developer mode `, and on the main Odoo dashboard, type `Reports`. From the search results that appear in the resulting pop-up window, choose :guilabel:`Settings / Technical / Reporting / Reports` to open the :guilabel:`Reports` page." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/zebra.rst:34 +msgid "To manually navigate to the :guilabel:`Reports` page, go to :menuselection:`Settings app --> Technical --> Reporting: Reports`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/zebra.rst:-1 +msgid "Show global search result for \"Reports\"." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/zebra.rst:41 +msgid "On the :guilabel:`Reports` page, in the :guilabel:`Search...` bar, type `ZPL`, and hit :kbd:`Enter`. Upon doing so, Odoo presents a list of available Zebra labels in Odoo. Select the desired Zebra label from the list to modify it on a separate page." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/zebra.rst:46 +msgid "Printable ZPL labels in Odoo:" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/zebra.rst:48 +msgid ":ref:`lot/serial number `" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/zebra.rst:49 +msgid "operation type" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/zebra.rst:50 +msgid "package barcode" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/zebra.rst:51 +msgid ":ref:`product label `" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/zebra.rst:52 +msgid "product packaging" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/zebra.rst:53 +msgid "finished product (Odoo *Manufacturing* app required)" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/zebra.rst:55 +msgid "Next, click the :icon:`fa-code` :guilabel:`Qweb Views` smart button, and choose the desired label :doc:`view <../../../../../developer/reference/user_interface/view_records>`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/zebra.rst:62 +msgid "Show Qweb smart button on the Lot and Serial Number (ZPL) report." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/zebra.rst:62 +msgid "**Lot and Serial Number (ZPL)** report, highlighting the Qweb smart button." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/zebra.rst:64 +msgid "On the resulting view form, go to the :guilabel:`Architecture` tab to view the |ZPL| code." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/zebra.rst:67 +msgid "To ensure the customization is **not** overwritten during an update, click the :icon:`fa-bug` :guilabel:`(bug)` icon on the view page. Then, select the :guilabel:`View Metadata` option from the resulting drop-down menu, in order to open the :guilabel:`View Metadata` pop-up window. Then, ensure the :guilabel:`No Update` field is set to :guilabel:`true (change)`. Click :guilabel:`Ok` to exit the :guilabel:`View Metadata` pop-up window." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/zebra.rst:-1 +msgid "Architecture tab in the view." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/zebra.rst:80 +msgid "Adjust margin" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/zebra.rst:82 +msgid "Text gets cut off from standard |ZPL| labels printed in Odoo when the line exceeds fifty-five characters. To fit long product names, or lot numbers, on a single line, adjust the margin." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/zebra.rst:85 +msgid "To begin, navigate to the :ref:`ZPL code of the label ` in the :guilabel:`Architecture` tab. In the |ZPL| code for product labels, look for the `^FT` command, which specifies where to start placing the text, or graphic element, on the label. The two numbers immediately following `^FT` define the x-coordinate and y-coordinate in dots (:dfn:`similar to pixels for printers`) from the left and top margins." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/zebra.rst:92 +msgid "When customizing lot/serial number labels, look for the `^FO` command, instead of `^FT`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/zebra.rst:96 +msgid "The following is an example where the product's name gets cut off with Odoo's default |ZPL| formatting. In the **Fixed** tab, the x-coordinate of the starting position of the label is changed from `^FT100,80` to `^FT0,80`, to fit the entire name." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/zebra.rst:102 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/zebra.rst:150 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/zebra.rst:203 +msgid "Default" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/zebra.rst:0 +msgid "Example barcode label with the product name cut off." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/zebra.rst:108 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/zebra.rst:123 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/zebra.rst:156 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/zebra.rst:172 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/zebra.rst:209 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/zebra.rst:225 +msgid "**Code**:" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/zebra.rst:117 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/zebra.rst:166 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/zebra.rst:219 +msgid "Modified" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/zebra.rst:0 +msgid "Example barcode label with the product name margin adjusted to the left." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/zebra.rst:135 +msgid "Resize barcode" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/zebra.rst:137 +msgid "To adjust the size of the barcode to scale, begin by navigating to the :ref:`ZPL code of the label ` in the :guilabel:`Architecture` tab. Look for the `^FO` command (typically in the third line), which is the starting point of the margin for the barcode." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/zebra.rst:141 +msgid "The `^BY` command configures barcode size, and takes three numbers: bar width, width of wide bars relative to narrow bars, and bar height. By default, |ZPL| code in Odoo uses `^BY3`, setting the bar width to three dots, a typical size that is easy for barcode scanners to read." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/zebra.rst:146 +msgid "To shrink the barcode to scale, `^BY3` is reduced to `^BY2`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/zebra.rst:0 +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/zebra.rst:0 +msgid "Example barcode label." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/zebra.rst:0 +msgid "Example barcode label with the barcode size reduced." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/zebra.rst:185 +msgid "Rotate elements" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/zebra.rst:187 +msgid "To rotate elements in |ZPL|, begin by navigating to the :ref:`ZPL code of the label ` in the :guilabel:`Architecture` tab." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/zebra.rst:190 +msgid "The `^BC` command's first parameter (:dfn:`information that affects the behavior of the command`) defines the rotation of an item, which can be:" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/zebra.rst:193 +msgid "`N`: display normally" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/zebra.rst:194 +msgid "`R`: rotate 90 degrees" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/zebra.rst:195 +msgid "`I`: rotate 180 degrees" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/zebra.rst:196 +msgid "`B`: rotate 270 degrees" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/zebra.rst:199 +msgid "To rotate the barcode, `^BCN` is changed to `^BCB`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/zebra.rst:0 +msgid "Example barcode label with the barcode rotated." +msgstr "" + #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage.rst:5 msgid "Warehouses and storage" msgstr "" @@ -10649,59 +10894,59 @@ msgstr "" msgid "Some examples of putaway rules." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/putaway.rst:97 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/putaway.rst:99 msgid "Storage categories" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/putaway.rst:99 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/putaway.rst:101 msgid "A *storage category* is an extra location attribute. Storage categories allow the user to define the quantity of products that can be stored in the location, and how the location will be selected with putaway rules." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/putaway.rst:106 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/putaway.rst:108 msgid "To enable storage categories, go to :menuselection:`Inventory app --> Configuration --> Settings`, and activate the :guilabel:`Storage Categories` feature in the :guilabel:`Warehouse` section. Then, click :guilabel:`Save`." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/putaway.rst:111 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/putaway.rst:113 msgid "The :guilabel:`Storage Locations` feature **must** be enabled to enable :guilabel:`Storage Categories`." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/putaway.rst:115 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/putaway.rst:117 msgid "Define storage category" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/putaway.rst:117 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/putaway.rst:119 msgid "To create a storage category, go to :menuselection:`Inventory app --> Configuration --> Storage Categories` and click :guilabel:`Create`." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/putaway.rst:120 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/putaway.rst:122 msgid "On the storage category form, type a name for the :guilabel:`Storage Category` field." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/putaway.rst:122 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/putaway.rst:124 msgid "Options are available to limit the capacity by weight, by product, or by package type. The :guilabel:`Allow New Product` field defines when the location is considered available to store a product:" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/putaway.rst:126 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/putaway.rst:128 msgid ":guilabel:`If location is empty`: a product can be added there only if the location is empty." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/putaway.rst:127 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/putaway.rst:129 msgid ":guilabel:`If products are the same`: a product can be added there only if the same product is already there." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/putaway.rst:129 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/putaway.rst:131 msgid ":guilabel:`Allow mixed products`: several different products can be stored in this location at the same time." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/putaway.rst:133 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/putaway.rst:135 msgid "Create putaway rules for pallet-stored items and ensure real-time storage capacity checks by creating the `High Frequency pallets` storage category." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/putaway.rst:136 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/putaway.rst:138 msgid "Name the :guilabel:`Storage Category`, and select :guilabel:`If all products are same` in the :guilabel:`Allow New Product` field." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/putaway.rst:139 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/putaway.rst:141 msgid "Then, define package capacity in the :guilabel:`Capacity by Package` tab, specifying the number of packages for the designated :guilabel:`Package Type` and setting a maximum of `2.00` `Pallets` for a specific location." msgstr "" @@ -10709,15 +10954,15 @@ msgstr "" msgid "Create a storage category on the page." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/putaway.rst:147 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/putaway.rst:149 msgid "Once the storage category settings are saved, the storage category can be linked to a location." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/putaway.rst:149 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/putaway.rst:151 msgid "To do that, navigate to the location by going to :menuselection:`Inventory app --> Configuration --> Locations`, and select the location. Click :guilabel:`Edit` and select the created category in the :guilabel:`Storage Category` field." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/putaway.rst:154 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/putaway.rst:156 msgid "Assign the `High Frequency pallets` storage category to the `WH/Stock/pallets/PAL 1` sub-location." msgstr "" @@ -10725,27 +10970,27 @@ msgstr "" msgid "When a Storage Category is created, it can be linked to a warehouse location." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/putaway.rst:162 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/putaway.rst:164 msgid "Storage categories in putaway rules" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/putaway.rst:164 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/putaway.rst:166 msgid "To continue the example from above, apply the `High Frequency Pallets` on the `PAL1` and `PAL2` locations and :ref:`rework the putaway rules ` as follows:" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/putaway.rst:167 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/putaway.rst:169 msgid "Assume one pallet of lemonade cans is received:" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/putaway.rst:169 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/putaway.rst:171 msgid "If PAL1 and PAL2 are empty, the pallet will be redirected to WH/Stock/Pallets/PAL1." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/putaway.rst:170 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/putaway.rst:172 msgid "If PAL1 is full, the pallet will be redirected to WH/Stock/Pallets/PAL2." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/putaway.rst:171 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/putaway.rst:173 msgid "If PAL1 and 2 are full, the pallet will be redirected to WH/Stock/Pallets." msgstr "" @@ -10830,7 +11075,7 @@ msgid "New warehouse form." msgstr "" #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/stock_warehouses.rst:76 -msgid ":doc:`Warehouse configurations <../inventory_management/warehouses_locations>`" +msgid ":doc:`Warehouse configurations <../inventory_management/warehouses>`" msgstr "" #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/advanced_operations_warehouse/stock_warehouses.rst:77 @@ -11109,10 +11354,164 @@ msgstr "" msgid "To view all wave transfers and their statuses, go to :menuselection:`Inventory --> Operations --> Wave Transfers`. Wave transfers can also be viewed in the :guilabel:`Barcode` app by going to :menuselection:`Barcode --> Batch Transfers`." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management.rst:5 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management.rst:6 msgid "Inventory management" msgstr "" +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management.rst:8 +msgid "In the Odoo *Inventory* app, :doc:`warehouses ` handle the broader organization and distribution of stock across different physical sites, while :doc:`locations ` provide a more detailed breakdown within each warehouse for efficient item management." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management.rst:13 +msgid "This document serves as an introduction to the terminology and concepts necessary to master *Inventory*. For specific instructions and examples of how things work, refer to individual documentation pages." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management.rst:18 +msgid "`Odoo Tutorials: Warehouses & Locations `_" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management.rst:21 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/warehouses.rst:3 +msgid "Warehouses" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management.rst:23 +msgid ":doc:`Warehouses ` represent a physical place, with a physical address, where a company's items are stored." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management.rst:26 +msgid "Configure :doc:`routes ` in a warehouse to control how products move to customers, from vendors, within the warehouse, or :doc:`between warehouses `." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management.rst:31 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_locations.rst:3 +msgid "Locations" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management.rst:33 +msgid ":doc:`Locations ` refer to specific areas within a warehouse, such as shelves, floors, or aisles. These are sub-divisions within a warehouse, and are unique to that warehouse. Users can create and manage numerous locations within a single warehouse to organize inventory more precisely." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management.rst:39 +msgid ":doc:`inventory_management/use_locations`" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management.rst:40 +msgid ":doc:`inventory_management/count_products`" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management.rst:41 +msgid ":doc:`inventory_management/cycle_counts`" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management.rst:42 +msgid ":doc:`inventory_management/scrap_inventory`" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management.rst:47 +msgid "Location types" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management.rst:49 +msgid "*Location types* in Odoo help categorize and manage where products are, and what actions need to be taken with them. By default, on the :menuselection:`Inventory app --> Configuration --> Locations` page, only internal locations are displayed." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management.rst:53 +msgid "To view the seven location types in Odoo, select any location, and in the :guilabel:`Location Type` field, there are:" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management.rst:56 +msgid ":guilabel:`Vendor Location`: defines an area where products purchased from vendors originate. Items here are **not** in stock." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management.rst:59 +msgid ":guilabel:`View`: used to organize and structure the warehouse hierarchy. For example, the view location `WH` (short for warehouse) groups all internal locations, such as `Stock`, receiving docks, quality checkpoints, and packing areas to show they all belong to the same warehouse." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management.rst:64 +msgid "View locations should **not** contain products, but it is possible to move them there." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management.rst:66 +msgid ":guilabel:`Internal Location`: storage locations within the warehouse. Items stored in these locations are accounted for in :doc:`inventory valuation `." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management.rst:70 +msgid ":guilabel:`Customer Location`: where sold products are tracked; items here are no longer in stock." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management.rst:72 +msgid ":guilabel:`Inventory Loss`: counterpart location to consume missing items or create stock, accounting for discrepancies." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management.rst:75 +msgid "In Odoo, examples of inventory loss locations are *Inventory Adjustment*, used to account for discrepancies during an inventory count, and *Scrap*, which is where damaged goods are sent to account for inventory losses." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management.rst:80 +msgid "`Virtual Locations/Inventory Adjustment` is a location with the :guilabel:`Inventory Loss` type. The database shows `65` units in `WH/Stock`, but an inventory check reveals `60`. To correct the quantity, five units are moved from `WH/Stock` to `Virtual Locations/Inventory Adjustment`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management.rst:0 +msgid "Product ends up in Virtual Locations/Inventory Adjustment." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management.rst:89 +msgid ":guilabel:`Production`: where raw materials are consumed, and :doc:`manufactured products <../../manufacturing>` are created." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management.rst:92 +msgid ":guilabel:`Transit Location`: used for inter-company or inter-warehouse operations to track products shipped between different addresses, such as :ref:`Physical Locations/Inter-warehouse transit `." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management.rst:-1 +msgid "List of locations in Odoo." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management.rst:103 +msgid "In Odoo, location types are color-coded:" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management.rst:102 +msgid "**Red**: internal locations" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management.rst:103 +msgid "**Blue**: view locations" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management.rst:104 +msgid "**Black**: external locations (including inventory loss, vendor, and customer locations)." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management.rst:107 +msgid "View locations in Odoo" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management.rst:109 +msgid "Odoo databases include pre-configured view locations to organize the hierarchy of locations. These provide helpful context, and distinguish between internal and external locations." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management.rst:112 +msgid "*Physical locations* serve as an umbrella for external locations, without changing a product's inventory value. (Inventory valuation changes occur when products move from internal to external locations)." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management.rst:119 +msgid "When moving products in warehouses `WH` and `WH2`, the items are not in either warehouse, but still belong to the company. While in transit, they are placed in the `Inter-warehouse transit` location, a :guilabel:`Transit Location` type." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management.rst:123 +msgid "This location is under the view location, `Physical Locations`, indicating that `Inter-warehouse transit` is outside of a warehouse, but still part of the company. Doing so does not affect the inventory valuation of the products." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management.rst:127 +msgid "*Partner locations* group customer and vendor locations (external locations) together. Transfers to these locations affect inventory valuation." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management.rst:129 +msgid "*Virtual locations* are locations that do **not** exist physically, but it is where items that are not in inventory can be placed. These can be items that are no longer in inventory due to loss, or other factors." +msgstr "" + #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/count_products.rst:3 msgid "Inventory adjustments" msgstr "" @@ -11383,199 +11782,6 @@ msgstr "" msgid ":doc:`cycle_counts`" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/create_a_second_warehouse.rst:3 -msgid "Create a second warehouse" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/create_a_second_warehouse.rst:5 -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/warehouses_locations.rst:11 -msgid "In Odoo *Inventory*, a *warehouse* is a physical building or space where items are stored. By default, each Odoo database has one warehouse already pre-configured, with the address set as the company's address." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/create_a_second_warehouse.rst:9 -msgid "However, it is possible to set up multiple additional warehouses, and transfer stored items between them." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/create_a_second_warehouse.rst:15 -msgid "To create a second warehouse, the *Storage Locations* feature must be enabled. To enable this feature, navigate to :menuselection:`Inventory app --> Configuration --> Settings`. Under the :guilabel:`Warehouse` section, tick the checkbox next to :guilabel:`Storage Locations`, and :guilabel:`Save` changes." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/create_a_second_warehouse.rst:-1 -msgid "Warning pop-up window for creating a second warehouse before enabling Storage Locations." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/create_a_second_warehouse.rst:25 -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/warehouses_locations.rst:97 -msgid "Creating a second warehouse without first enabling the *Storage Locations* feature triggers a :guilabel:`Warning` pop-up window. It indicates creating a second warehouse automatically activates the *Storage Locations* setting." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/create_a_second_warehouse.rst:30 -msgid "Create new warehouse" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/create_a_second_warehouse.rst:32 -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/warehouses_locations.rst:70 -msgid "To create a new warehouse, navigate to :menuselection:`Inventory app --> Configuration --> Warehouses`, and click :guilabel:`New`. Doing so opens a blank warehouse creation form." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/create_a_second_warehouse.rst:35 -msgid "Fill out the following fields as necessary:" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/create_a_second_warehouse.rst:37 -msgid ":guilabel:`Warehouse`: the full name of the warehouse." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/create_a_second_warehouse.rst:38 -msgid ":guilabel:`Short Name`: the abbreviated code used to identify the warehouse, i.e. `WH2` (the short name for the default warehouse in Odoo is `WH`)." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/create_a_second_warehouse.rst:40 -msgid ":guilabel:`Company`: the company that owns the warehouse. This can be set as the company that owns the Odoo database or the company of a customer or vendor." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/create_a_second_warehouse.rst:42 -msgid ":guilabel:`Address`: the address where the warehouse is located. By default, this is set to the company's address in the database." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/create_a_second_warehouse.rst:-1 -msgid "Filled out warehouse name and address settings on warehouse creation form." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/create_a_second_warehouse.rst:49 -msgid "Under the :guilabel:`Warehouse Configuration` tab, configure the warehouse's main workflow in the :guilabel:`Shipments` section, and set available replenishment methods in the :guilabel:`Resupply` section." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/create_a_second_warehouse.rst:54 -msgid "The :guilabel:`Shipments` and :guilabel:`Resupply` sections only appear if the :guilabel:`Multi-Step Routes` checkbox is enabled in :menuselection:`Inventory app --> Configuration --> Settings`, under the :guilabel:`Warehouse` heading. For more information about routes and how they work in Odoo, see :ref:`Using Routes and Pull/Push Rules `." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/create_a_second_warehouse.rst:59 -msgid "In the :guilabel:`Shipments` section, choose between one, two, or three-step processes for both incoming and outgoing shipments." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/create_a_second_warehouse.rst:62 -msgid "In the :guilabel:`Resupply` section, edit the following settings:" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/create_a_second_warehouse.rst:64 -msgid ":guilabel:`Dropship Subcontractors`: enable this feature to coordinate with vendors, and have components dropshipped directly to subcontractors for manufacturing." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/create_a_second_warehouse.rst:66 -msgid ":guilabel:`Resupply Subcontractors`: allow subcontractors to be resupplied with goods from this warehouse." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/create_a_second_warehouse.rst:68 -msgid ":guilabel:`Manufacture to Resupply`: when products are manufactured, they can be delivered to this warehouse." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/create_a_second_warehouse.rst:70 -msgid ":guilabel:`Manufacture`: the route that should be followed when manufacturing goods inside the warehouse. Choose from one, two, and three-step production." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/create_a_second_warehouse.rst:72 -msgid ":guilabel:`Buy to Resupply`: when products are purchased, they can be delivered to this warehouse." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/create_a_second_warehouse.rst:73 -msgid ":guilabel:`Resupply From`: Check the box next to the other warehouses from which this warehouse can replenish products. If the current warehouse does not have the stock, it can also pull products from these selected warehouses in the database. Automatic resupply routes will be created accordingly." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/create_a_second_warehouse.rst:-1 -msgid "Filled out Warehouse Configuration tab settings on warehouse creation form." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/create_a_second_warehouse.rst:82 -msgid "Once ready, click :guilabel:`Save` to save the new warehouse's settings." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/create_a_second_warehouse.rst:85 -msgid "Add inventory to a new warehouse" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/create_a_second_warehouse.rst:87 -msgid "If a new warehouse is created to represent a real-world storage location with existing stock, update the warehouse's stock using an inventory adjustment." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/create_a_second_warehouse.rst:91 -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/cycle_counts.rst:123 -msgid ":doc:`count_products`" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/create_a_second_warehouse.rst:93 -msgid "To perform an inventory adjustment, navigate to :menuselection:`Inventory app --> Operations --> Physical Inventory`, and click :guilabel:`New`. Doing so adds a new line at the bottom of the list of inventory adjustments." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/create_a_second_warehouse.rst:97 -msgid "Configure the line by filling out the following fields as necessary:" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/create_a_second_warehouse.rst:99 -msgid ":guilabel:`Location`: the location where the product is currently stored in the new warehouse. This can be set as the overall warehouse, or a location within the warehouse." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/create_a_second_warehouse.rst:101 -msgid ":guilabel:`Product`: the product being added to inventory." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/create_a_second_warehouse.rst:102 -msgid ":guilabel:`Lot/Serial Number`: the lot that the product belongs to or the serial number used to identify it, if the product is tracked." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/create_a_second_warehouse.rst:104 -msgid ":guilabel:`On Hand Quantity`: the total quantity of the product stored in the location for which inventory is being adjusted. For a new warehouse or location where a count or a prior inventory adjustment has not taken place, this should be set to `0.00`." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/create_a_second_warehouse.rst:107 -msgid ":guilabel:`UoM`: the unit of measure (UoM) used for counting the product." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/create_a_second_warehouse.rst:108 -msgid ":guilabel:`Counted Quantity`: the amount of the product being added to inventory." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/create_a_second_warehouse.rst:109 -msgid ":guilabel:`Difference`: the difference between the on-hand and counted quantities. This automatically updates to reflect the value entered in the :guilabel:`Counted Quantity` column." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/create_a_second_warehouse.rst:111 -msgid ":guilabel:`Scheduled Date`: the date selected for the next inventory count for this product." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/create_a_second_warehouse.rst:112 -msgid ":guilabel:`User`: the user who recorded the inventory adjustment in the database." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/create_a_second_warehouse.rst:-1 -msgid "Filled out inventory adjustment line for product in new warehouse." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/create_a_second_warehouse.rst:118 -msgid "Once each line for the products being added to the new warehouse is configured, click :guilabel:`Apply` on each line to apply the new inventory counts." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/create_a_second_warehouse.rst:121 -msgid "The values in the :guilabel:`On Hand Quantity` column update to reflect those in the :guilabel:`Counted Quantity` column, and the products added appear in the new warehouse's stock." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/create_a_second_warehouse.rst:125 -msgid "If products tracked using a lot number or serial number are added without specifying the tracking number, a :guilabel:`Tracked Products in Inventory Adjustment` pop-up window appears upon clicking :guilabel:`Apply` on that product's line." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/create_a_second_warehouse.rst:129 -msgid "The pop-up indicates tracked products were added, but the lots/serial numbers were not defined. To apply the adjustment without the numbers, click :guilabel:`Apply`. To add the numbers before applying, click :guilabel:`Discard`, and add the numbers. Then, once ready, click :guilabel:`Apply` again." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/create_a_second_warehouse.rst:0 -msgid "Tracked Products in Inventory Adjustment pop-up window." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/create_a_second_warehouse.rst:139 -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_locations.rst:118 -msgid ":doc:`warehouses_locations`" -msgstr "" - #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/cycle_counts.rst:3 msgid "Cycle counts" msgstr "" @@ -11700,6 +11906,10 @@ msgstr "" msgid "Once all necessary changes have been made, click :guilabel:`Save`." msgstr "" +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/cycle_counts.rst:123 +msgid ":doc:`count_products`" +msgstr "" + #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/cycle_counts.rst:124 msgid ":doc:`use_locations`" msgstr "" @@ -11789,30 +11999,18 @@ msgid "*Virtual locations* in Odoo are **not** real, physical spaces in a wareho msgstr "" #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/scrap_inventory.rst:23 -msgid "For more information about virtual locations, see the documentation about the different types of :ref:`locations `." +msgid "For more information about virtual locations, see the documentation about the different types of :ref:`location types `." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/scrap_inventory.rst:29 -msgid "To use locations in warehouse, including a virtual scrap location, the *Storage Locations* feature must first be enabled." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/scrap_inventory.rst:32 -msgid "To do so, navigate to :menuselection:`Inventory app --> Configuration --> Settings`, and scroll down to the :guilabel:`Warehouse` section. Tick the checkbox next to :guilabel:`Storage Locations` to enable the feature, and click :guilabel:`Save`." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/scrap_inventory.rst:-1 -msgid "Enabled Storage Locations setting in Inventory app settings." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/scrap_inventory.rst:41 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/scrap_inventory.rst:27 msgid "Scrap from stock" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/scrap_inventory.rst:43 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/scrap_inventory.rst:29 msgid "To create a new scrap order (SP) for an in-stock product, navigate to :menuselection:`Inventory app --> Operations --> Scrap`, and click :guilabel:`New`. This opens a new |SP| form." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/scrap_inventory.rst:46 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/scrap_inventory.rst:32 msgid "Click the drop-down menu in the :guilabel:`Product` field, and select the product that should be scrapped from inventory. In the :guilabel:`Quantity` field, change the value to the quantity of the product that should be scrapped (by default, this value is set to `1.00`)." msgstr "" @@ -11820,19 +12018,19 @@ msgstr "" msgid "Filled out new scrap order form with product details." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/scrap_inventory.rst:54 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/scrap_inventory.rst:40 msgid "The :guilabel:`Source Location` defaults to the location where the product is currently stored. The :guilabel:`Scrap Location` defaults to the designated scrap location (:guilabel:`Virtual Locations/Scrap`). Either of these locations can be changed by selecting a different location from their respective drop-down menus." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/scrap_inventory.rst:59 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/scrap_inventory.rst:45 msgid "If the scrapping is tied to a specific existing operation, specify the operation in the :guilabel:`Source Document` field." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/scrap_inventory.rst:62 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/scrap_inventory.rst:48 msgid "The :guilabel:`Company` field displays the company whose warehouse this product belongs to. If a replenishment rule is set up for the product being scrapped, and if the product should be replenished, tick the checkbox for :guilabel:`Replenish Quantities`." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/scrap_inventory.rst:66 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/scrap_inventory.rst:52 msgid "Once ready, click :guilabel:`Validate` to complete the new |SP|. Once validated, a :guilabel:`Product Moves` smart button appears at the top of the form. Click the smart button to view the details of the scrap operation." msgstr "" @@ -11840,15 +12038,15 @@ msgstr "" msgid "Product Moves smart button on new scrap order form." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/scrap_inventory.rst:75 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/scrap_inventory.rst:61 msgid "To view the all-time total quantities of scrapped items, navigate to :menuselection:`Inventory app --> Configuration --> Locations`. Click the :guilabel:`x (remove)` button on the :guilabel:`Internal` filter in the :guilabel:`Search...` bar, to display virtual locations." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/scrap_inventory.rst:79 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/scrap_inventory.rst:65 msgid "Select the :guilabel:`Virtual Locations/Scrap` location. From the :guilabel:`Scrap` location's form, click the :guilabel:`Current Stock` smart button, at the top of the form." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/scrap_inventory.rst:82 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/scrap_inventory.rst:68 msgid "A list of all scrapped products, and their quantities, is displayed." msgstr "" @@ -11856,15 +12054,15 @@ msgstr "" msgid "Current Stock list of all scrapped products in virtual scrap location." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/scrap_inventory.rst:89 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/scrap_inventory.rst:75 msgid "Scrap from an existing operation" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/scrap_inventory.rst:91 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/scrap_inventory.rst:77 msgid "Scrap orders (SPs) can *also* be created from existing operations, such as receipts, delivery orders, and internal transfers, before they are entered into, or removed from, stock for an operation." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/scrap_inventory.rst:95 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/scrap_inventory.rst:81 msgid "To scrap a product during an operation, navigate to the :menuselection:`Inventory app`. From the :guilabel:`Inventory Overview`, click the :guilabel:`# To Process` button on an operation's task card (i.e. the :guilabel:`Receipts` task card)." msgstr "" @@ -11872,11 +12070,11 @@ msgstr "" msgid "# To Process button on Receipts task card on Inventory Overview page." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/scrap_inventory.rst:103 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/scrap_inventory.rst:89 msgid "Then, select an operation to process from the resulting list of existing orders. Doing so opens that operation's form." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/scrap_inventory.rst:106 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/scrap_inventory.rst:92 msgid "Click the :icon:`fa-cog` :guilabel:`(cog)` icon, and select :guilabel:`Scrap` from the resulting drop-down menu. This opens a :guilabel:`Scrap Products` pop-up window." msgstr "" @@ -11884,19 +12082,19 @@ msgstr "" msgid "Scrap Products pop-up window on operation form." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/scrap_inventory.rst:113 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/scrap_inventory.rst:99 msgid "From this pop-up window, click the drop-down menu in the :guilabel:`Product` field, and select the products from the operation that should be scrapped. Adjust the value in the :guilabel:`Quantity` field, if necessary." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/scrap_inventory.rst:117 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/scrap_inventory.rst:103 msgid "If the :guilabel:`Product` selected is tracked using a lot or serial number, a :guilabel:`Lot/Serial` field appears. Specify the tracking number in that field." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/scrap_inventory.rst:120 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/scrap_inventory.rst:106 msgid "The :guilabel:`Source Location` and :guilabel:`Scrap Location` can be changed, if needed. If a replenishment rule is set up for the product being scrapped, and if the product should be replenished, tick the checkbox for :guilabel:`Replenish Quantities`." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/scrap_inventory.rst:124 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/scrap_inventory.rst:110 msgid "Once ready, click :guilabel:`Scrap Products`. A :guilabel:`Scraps` smart button appears at the top of the operation form. Click this smart button to view the details of all scrap orders created from this specific operation." msgstr "" @@ -11904,117 +12102,109 @@ msgstr "" msgid "Scraps smart button showing all scrap orders from operation." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_locations.rst:3 -msgid "Locations" -msgstr "" - #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_locations.rst:5 -msgid "In Odoo *Inventory*, a *location* is a specific space within a warehouse. This can be a shelf, room, aisle, rack, bin, etc." +msgid "A *location* is a specific space within a warehouse. This can be a shelf, room, aisle, etc." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_locations.rst:8 -msgid "There are also external and virtual locations. For example, customer locations, and locations specifically designated as \"virtual\", instead of real, physical locations." +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_locations.rst:10 +msgid "To create specific storage locations, enable the *Storage Locations* feature by going to :menuselection:`Inventory app --> Configuration --> Settings`. In the :guilabel:`Warehouses` section, tick the :guilabel:`Storage Locations` checkbox. Then, click :guilabel:`Save`." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_locations.rst:11 -msgid "Locations allow for the storage of products in designated areas of the warehouse, to help track inventory accurately." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_locations.rst:17 -msgid "To specify storage locations, the *Storage Locations* setting must be enabled. To do so, navigate to :menuselection:`Inventory app --> Configuration --> Settings`, and scroll down to the :guilabel:`Warehouse` section. Tick the checkbox next to :guilabel:`Storage Locations` to enable the feature, and click :guilabel:`Save`." +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_locations.rst:15 +msgid "Typically, the :guilabel:`Storage Locations` feature is used with :doc:`Multi-Step Routes `, which controls how products move between locations." msgstr "" #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_locations.rst:-1 -msgid "Enabled Storage Location setting in Inventory app settings." +msgid "Show Storage Locations feature." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_locations.rst:26 -msgid "Once the :guilabel:`Storage Locations` feature is enabled, two additional internal link options appear below it: :guilabel:`Locations` and :guilabel:`Putaway Rules`. Click :guilabel:`Locations` to open a list of all existing locations in the warehouse." +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_locations.rst:23 +msgid "Create new location" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_locations.rst:31 -msgid "Create a new location inside a warehouse" +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_locations.rst:25 +msgid "After enabling *Storage Locations*, go to :menuselection:`Inventory app --> Configuration --> Locations`." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_locations.rst:33 -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/warehouses_locations.rst:104 -msgid "To create a new location inside a warehouse, navigate to :menuselection:`Inventory app --> Configuration --> Locations`. Doing so opens a list of all existing locations. Click :guilabel:`New` to open a new location creation form." +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_locations.rst:-1 +msgid "List of internal locations." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_locations.rst:37 -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/warehouses_locations.rst:108 -msgid "In the :guilabel:`Location Name` field, assign a name for the new location. In the :guilabel:`Parent Location` field, assign the location that this new location exists in." +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_locations.rst:32 +msgid "On this page, click :guilabel:`New`. The new location form can then be configured as follows:" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_locations.rst:41 -msgid "A new location `Gate 1` is created. Its parent location is `Dispatch Zone`. In the :guilabel:`Parent Location` for `Gate 1`, select `Dispatch Zone`." +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_locations.rst:34 +msgid ":guilabel:`Location Name`: recognizable name of the location." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_locations.rst:44 -msgid "In the :guilabel:`Additional Information` section, fill out the necessary details for the new location." +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_locations.rst:35 +msgid ":guilabel:`Parent Location`: the location within which the new location exists. After the location is created, it is listed on the :guilabel:`Locations` page using a *location hierarchy*, to describe how a specific location fits within larger areas of the warehouse." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_locations.rst:40 +msgid "In `WH/Stock/Zone A/Refrigerator 1`, \"Refrigerator 1\" is the location name, \"Zone A\" is the parent location, and everything before it is the path showing where this spot is within the warehouse." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_locations.rst:45 +msgid "Additional Information section" msgstr "" #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_locations.rst:47 -msgid "In the :guilabel:`Location Type` field, select which type of location this is. There are seven different types of locations to choose from:" +msgid "In addition to the required fields above, configure the following location fields to ensure the location serves its intended purpose in the database:" msgstr "" #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_locations.rst:50 -msgid ":guilabel:`Vendor Location`: virtual location representing the source location for products coming from vendors." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_locations.rst:52 -msgid ":guilabel:`View`: virtual location used to create a hierarchical structure for a warehouse; aggregates its child locations. **Should not directly contain products**." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_locations.rst:54 -msgid ":guilabel:`Internal Location`: physical location inside a warehouse." +msgid ":guilabel:`Location Type`: from the drop-down menu, choose :guilabel:`Vendor Location`, :guilabel:`View`, :guilabel:`Internal Location`, :guilabel:`Customer Location`, :guilabel:`Inventory Loss`, :guilabel:`Production`, or :guilabel:`Transit Location` to categorize the location. For details on each location type, refer to the :ref:`Location Types section `." msgstr "" #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_locations.rst:55 -msgid ":guilabel:`Customer Location`: virtual location representing the destination location for products sent to customers." +msgid ":guilabel:`Storage Category`: only available with the :ref:`Storage Categories ` feature enabled in :menuselection:`Inventory app --> Configuration --> Settings`." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_locations.rst:57 -msgid ":guilabel:`Inventory Loss`: virtual location serving as a counterpart for inventory operations. Used to correct stock levels of physical inventory." +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_locations.rst:58 +msgid ":guilabel:`Company`: the company the location belongs to." msgstr "" #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_locations.rst:59 -msgid ":guilabel:`Production`: virtual counterpart location for production operations. This location consumes components and produces finished products." +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_locations.rst:77 +msgid ":guilabel:`Is a Scrap Location?`: tick this checkbox to allow for scrapped/damaged goods to be stored in this location." msgstr "" #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_locations.rst:61 -msgid ":guilabel:`Transit Location`: counterpart location that should be used in inter-company or inter-warehouse operations." +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_locations.rst:79 +msgid ":guilabel:`Is a Return Location?`: tick this checkbox to allow products to be returned to this location." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_locations.rst:63 +msgid ":guilabel:`Barcode`: used with the *Barcode* app, enter the barcode to :ref:`identify actions ` at this location when scanned." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_locations.rst:65 +msgid ":guilabel:`Replenish Location`: used for :doc:`configuring routes `, tick this checkbox to set the location as a destination for receiving products from *Buy*, *Manufacture*, or other procurement routes, ensuring products are correctly supplied to the warehouse." msgstr "" #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_locations.rst:-1 msgid "Additional Information section of new location creation form." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_locations.rst:68 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_locations.rst:73 msgid "Configure the remaining fields in the :guilabel:`Additional Information` section as follows:" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_locations.rst:70 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_locations.rst:75 msgid ":guilabel:`Company`: the company whose warehouse the location is inside of. Leave this field blank if this location is shared between companies." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_locations.rst:72 -msgid ":guilabel:`Is a Scrap Location?`: tick this checkbox to allow for scrapped/damaged goods to be stored in this location." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_locations.rst:74 -msgid ":guilabel:`Is a Return Location?`: tick this checkbox to allow products to be returned to this location." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_locations.rst:76 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_locations.rst:81 msgid ":guilabel:`Barcode`: the barcode assigned to the location." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_locations.rst:77 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_locations.rst:82 msgid ":guilabel:`Replenish Location`: tick this checkbox to get all quantities to replenish at this location." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_locations.rst:80 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_locations.rst:85 msgid "In the :guilabel:`Cyclic Counting` section, change the value in the :guilabel:`Inventory Frequency (Days)` field from the default `0`, if necessary." msgstr "" @@ -12022,36 +12212,68 @@ msgstr "" msgid "Cyclic Counting section of new location creation form." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_locations.rst:87 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_locations.rst:92 msgid "When different than `0`, the inventory count dates for products stored at this location are automatically set at the defined frequency." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_locations.rst:90 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_locations.rst:95 msgid "In the :guilabel:`Logistics` section, in the :guilabel:`Removal Strategy` field, click the drop-down menu and select the :doc:`removal strategy <../removal_strategies>` for how items should be removed from this location." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_locations.rst:97 -msgid "Create location hierarchies" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_locations.rst:99 -msgid "The *Parent Location* setting on the new location form allows for a location to exist within a warehouse, or below another location." -msgstr "" - #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_locations.rst:102 -msgid "Every location can serve as a parent location, and every parent location can have multiple locations within it, allowing for the creation of a hierarchical structure." +msgid "Cyclic Counting section" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_locations.rst:106 -msgid "Location hierarchy could be organized so that a small refrigerator is located on a specific shelf, which is located in the warehouse." +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_locations.rst:104 +msgid "To schedule regular inventory counts at this location, set the :guilabel:`Inventory Frequency (Days)` field to the desired interval. By default, it is set to `0` (no scheduled counts)." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_locations.rst:-1 -msgid "Location hierarchy of small refrigerator, on a shelf in a warehouse." +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_locations.rst:107 +msgid "For example, setting this field to `30`, schedules a count every thirty days. For more specifics on setting up and using this feature, refer to the :doc:`Cycle Counts documentation `." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_locations.rst:113 -msgid "To create the location hierarchy in the example above (`WH/Stock/Shelf 2/Small Refrigerator`), set the warehouse stock as the parent of the shelf, and the shelf as the parent of the small refrigerator. This can be adapted to a hierarchy of any magnitude." +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_locations.rst:110 +msgid "The :guilabel:`Last Effective Inventory` field displays the date the last inventory count at this location occurred. When scheduled inventory counts are enabled, the :guilabel:`Next Expected Inventory` field displays the date of the next inventory count." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_locations.rst:115 +msgid "With inventory counts scheduled to occur every `30` days, and the :guilabel:`Last Effective Inventory` count occurring on July 16, the :guilabel:`Next Expected Inventory` is August 15." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_locations.rst:0 +msgid "Show Cyclic Count section of the locations form." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_locations.rst:123 +msgid "Logistics section" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_locations.rst:125 +msgid "In the :guilabel:`Logistics` section of the locations form, optionally select a :guilabel:`Removal Strategy` to determine the order and priority of how products are picked from inventory. The options are: :guilabel:`First In First Out (FIFO)`, :guilabel:`Last In First Out (LIFO)`, :guilabel:`Closest Location`, and :guilabel:`First Expiry First Out (FEFO)`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_locations.rst:131 +msgid ":doc:`../removal_strategies`" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_locations.rst:134 +msgid "Current stock at location" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_locations.rst:136 +msgid "To view the current stock at a single location, go to :menuselection:`Inventory app --> Configuration --> Locations`, and select the desired location." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_locations.rst:139 +msgid "Next, click the :guilabel:`Current Stock` smart button to get a list of all products at the location." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_locations.rst:143 +msgid "A list of current stock at `Shelf 1` consists of `266` cabinets and `39` desks." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_locations.rst:0 +msgid "Show stock at Shelf 1." msgstr "" #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_routes.rst:5 @@ -12576,108 +12798,88 @@ msgstr "" msgid "After the scheduler runs, a delivery order and receipt will be created for the outgoing and incoming warehouses, respectively. Both the delivery order and receipt should be processed using the same method as detailed above." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/warehouses_locations.rst:3 -msgid "Manage warehouses and locations" +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/warehouses.rst:5 +msgid "In the Odoo *Inventory* app, a *warehouse* is a physical space with an address for storing items, such as a storage facility, distribution center, or physical store." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/warehouses_locations.rst:9 -msgid "Warehouse" +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/warehouses.rst:8 +msgid "Each database has a pre-configured warehouse with the company's address. Users can set up multiple warehouses, and :doc:`create stock moves ` between them." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/warehouses_locations.rst:15 -msgid "Multiple warehouses can be set up in Odoo, and stock moves can be created between warehouses." +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/warehouses.rst:14 +msgid "To create or manage warehouses, go to :menuselection:`Inventory app --> Configuration --> Warehouses`." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/warehouses_locations.rst:22 -msgid "In Odoo *Inventory*, a *location* is a specific space within a warehouse. This can be a shelf, room, aisle, rack, bin, etc. Locations allow for the storage of products in designated areas of the warehouse, to help track inventory accurately." +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/warehouses.rst:17 +msgid "Then, select an existing warehouse, or create a new one by clicking :guilabel:`New`. Doing so opens the warehouse form, which contains the following fields:" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/warehouses_locations.rst:26 -msgid "A location is only part of *one* warehouse, and can **not** be linked to multiple warehouses. As many locations can be configured as needed under one warehouse." +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/warehouses.rst:20 +msgid ":guilabel:`Warehouse` (*required field*): the full name of the warehouse." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/warehouses_locations.rst:29 -msgid "There are three types of locations in Odoo *Inventory*:" +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/warehouses.rst:21 +msgid ":guilabel:`Short Name` (*required field*): the abbreviated code for the warehouse (maximum five characters). The short name for the default warehouse in Odoo is `WH`." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/warehouses_locations.rst:31 -msgid "**Physical Locations**: internal locations within a single warehouse owned by the company. This can include shipping and loading docks, aisles, shelves, storage areas, and more." +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/warehouses.rst:25 +msgid "The :guilabel:`Short Name` appears on warehouse documents, so it is recommended to use an memorable one, like \"WH[first letters of location]\" (e.g. `WHA`, `WHB`, etc.)." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/warehouses_locations.rst:33 -msgid "**Partner Locations**: external locations, such as designated spaces in a customer or vendor's warehouse. They are similar to physical locations, but they are **not** owned by the user's company." +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/warehouses.rst:28 +msgid ":guilabel:`Address` (*required field*): the address of the warehouse. To change the warehouse address when creating two or more warehouses, hover over the field, and click the :icon:`fa-arrow-right` :guilabel:`(right arrow)`." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/warehouses_locations.rst:36 -msgid "**Virtual Locations**: this type of location does not exist as a physical space, but products can be \"stored\" here when they are not physically in an inventory yet. *Inventory Loss* and *Procurements* are examples of virtual locations, for products that are lost or in transit to the warehouse." +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/warehouses.rst:31 +msgid ":guilabel:`Company` (*required field*): the company that owns the warehouse; this can be set as the company that owns the Odoo database, or the company of a customer or vendor." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/warehouses_locations.rst:41 -msgid "Every location within a warehouse can serve as a parent location, and every parent location can have multiple locations within it, allowing for the creation of a hierarchical structure. This allows for more detailed levels of analysis of the stock operations and the organization of the warehouses." +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/warehouses.rst:33 +msgid ":guilabel:`Intrastat region`: :doc:`region name <../../../../finance/accounting/reporting/intrastat>` required for companies in the European Union." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/warehouses_locations.rst:48 -msgid "For companies with one warehouse, no additional settings are required to activate before editing the warehouse." +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/warehouses.rst:38 +msgid "The options below are available **only** when the *Multi-Step Routes* feature is enabled in :menuselection:`Inventory app --> Configuration --> Settings`." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/warehouses_locations.rst:51 -msgid "For companies with multiple warehouses, and to create locations within a warehouse, the *Storage Locations* feature must be enabled." +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/warehouses.rst:41 +msgid ":guilabel:`Incoming Shipments`: select the option to receive products from the warehouse in :doc:`one <../../shipping_receiving/daily_operations/receipts_delivery_one_step>`, :doc:`two <../../shipping_receiving/daily_operations/receipts_delivery_two_steps>`, or :doc:`three <../../shipping_receiving/daily_operations/receipts_three_steps>` steps." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/warehouses_locations.rst:54 -msgid "To do so, navigate to :menuselection:`Inventory app --> Configuration --> Settings`, and scroll down to the :guilabel:`Warehouse` section. Tick the :guilabel:`Storage Locations` checkbox to enable the feature, and click :guilabel:`Save`." +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/warehouses.rst:46 +msgid ":guilabel:`Outgoing Shipments`: select the option to deliver products from the warehouse in :doc:`one <../../shipping_receiving/daily_operations/receipts_delivery_one_step>`, :doc:`two <../../shipping_receiving/daily_operations/receipts_delivery_two_steps>`, or :doc:`three <../../shipping_receiving/daily_operations/delivery_three_steps>` steps." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/warehouses_locations.rst:-1 -msgid "Storage Locations feature enabled in the Inventory app settings." +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/warehouses.rst:51 +msgid ":guilabel:`Dropship Subcontractors`: available with the *Subcontracting* feature enabled in :menuselection:`Manufacturing app --> Configuration --> Settings`. Tick this checkbox to purchase components from vendors, and dropship them to subcontractors." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/warehouses_locations.rst:63 -msgid "To manage warehouse *routes*, such as two-and-three-step receipts and deliveries, enable the *Multi-Step Routes* feature from the *Inventory* app settings, as well. For more on routes, see :doc:`use_routes`." +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/warehouses.rst:54 +msgid ":guilabel:`Resupply Subcontractors`: available with the *Subcontracting* feature, tick this checkbox to supply subcontractors with raw materials stored in *this* specific warehouse." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/warehouses_locations.rst:68 -msgid "Create a new warehouse" +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/warehouses.rst:56 +msgid ":guilabel:`Manufacture to Resupply`: tick this checkbox to allow for items to be manufactured in this warehouse." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/warehouses_locations.rst:73 -msgid "Begin by assigning a :guilabel:`Warehouse Name`, and a :guilabel:`Short Name`. The :guilabel:`Short Name` field is limited to a **five** character maximum." +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/warehouses.rst:58 +msgid ":guilabel:`Manufacture`: choose whether to manufacture products in :doc:`one <../../../manufacturing/basic_setup/one_step_manufacturing>`, :doc:`two <../../../manufacturing/basic_setup/two_step_manufacturing>`, or :doc:`three steps <../../../manufacturing/basic_setup/three_step_manufacturing>`." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/warehouses_locations.rst:-1 -msgid "New warehouse creation form name configuration fields." +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/warehouses.rst:62 +msgid ":guilabel:`Buy to Resupply`: tick this checkbox to allow for purchased products to be delivered to the warehouse." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/warehouses_locations.rst:81 -msgid "The :guilabel:`Short Name` appears on transfer orders and other warehouse documents. Odoo recommends using an understandable one like `WH/[first letters of location]`." +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/warehouses.rst:64 +msgid ":guilabel:`Resupply From`: available with multiple warehouses in the database, select warehouses to pull stock *from* to fulfill orders." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/warehouses_locations.rst:84 -msgid "For example, a warehouse named `Warehouse #2` might have the :guilabel:`Short Name` `WH2` (the short name for the default warehouse in Odoo is `WH`)." +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/warehouses.rst:68 +msgid ":doc:`Use inventory adjustments to add stock to new warehouses `" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/warehouses_locations.rst:87 -msgid "Once the warehouse is created, navigate back to the :menuselection:`Inventory` dashboard. New operations for the newly created warehouse are automatically generated there." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/warehouses_locations.rst:90 -msgid "For more on creating new warehouses, see :doc:`create_a_second_warehouse`." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/warehouses_locations.rst:-1 -msgid "Inventory app dashboard displaying new transfers for the new warehouse." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/warehouses_locations.rst:102 -msgid "Create a new location" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/warehouses_locations.rst:111 -msgid "For more on locations, see :doc:`use_locations`." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/warehouses_locations.rst:-1 -msgid "New warehouse location creation form." +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management/warehouses.rst:-1 +msgid "Example warehouse form." msgstr "" #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation.rst:5 @@ -12906,38 +13108,54 @@ msgid "This document is focused on the proper setup of automatic inventory valua msgstr "" #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:30 -msgid "Switching to automatic inventory valuation **does not** create journal entries for existing stock, potentially leading to discrepancies between stock valuation and accounting journals." +msgid "Switching from manual to automatic inventory valuation may cause discrepancies between stock valuation and accounting journals." msgstr "" #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:33 -msgid "To manually post journal entries for existing stock, navigate to :menuselection:`Inventory app --> Reporting --> Valuation` for a list of current stock and its value. Then, :doc:`post a journal entry <../../../../finance/accounting/vendor_bills>` for each existing item." +msgid "One `successful strategy `_ for switching to automated valuation:" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:35 +msgid "Clear existing stock (possibly with an :doc:`inventory adjustment <../inventory_management/count_products>`)" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:37 +msgid "Change the inventory valuation method to *Automatic*" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:38 +msgid "Return the existing stock, with the original monetary value (using an inventory adjustment)" msgstr "" #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:40 -msgid "To properly set up automatic inventory valuation, follow these steps in Odoo:" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:42 -msgid ":ref:`Install Accounting app and enable specific settings `" -msgstr "" - -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:44 -msgid ":ref:`Set Automatic inventory valuation on product categories `" +msgid "Once the existing stock is recovered, the Odoo *Accounting* app automatically generates the journal entries to corresponding stock valuation records." msgstr "" #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:46 +msgid "To properly set up automatic inventory valuation, follow these steps in Odoo:" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:48 +msgid ":ref:`Install Accounting app and enable specific settings `" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:50 +msgid ":ref:`Set Automatic inventory valuation on product categories `" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:52 msgid ":ref:`Set costing method `" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:51 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:57 msgid "Accounting setup" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:53 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:59 msgid "To use automatic inventory valuation, install the *Accounting* app. Next, go to :menuselection:`Accounting app --> Configuration --> Settings`, and in the :guilabel:`Stock Valuation` section, tick the :guilabel:`Automatic Accounting` checkbox. Then, click :guilabel:`Save`." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:59 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:65 msgid "Enabling :guilabel:`Automatic Accounting` shows the previously invisible *Inventory Valuation* field on a product category." msgstr "" @@ -12945,23 +13163,23 @@ msgstr "" msgid "Automatic Accounting feature in Stock Valuation section of Settings page." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:66 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:72 msgid "Refer to the :ref:`Expense ` and :ref:`Stock input/output ` sections of documentation for details on configuring the accounting journals shown." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:73 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:79 msgid "Product category setup" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:75 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:81 msgid "After :ref:`enabling inventory valuation `, the next step is to set the product category to use automatic inventory valuation." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:78 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:84 msgid "Go to :menuselection:`Inventory app --> Configuration --> Product Categories`, and select the desired product category. In the :guilabel:`Inventory Valuation` section, set the :guilabel:`Inventory Valuation` field to :guilabel:`Automated`. Repeat this step for every product category intending to use automatic inventory valuation." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:84 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:90 msgid "After enabling automatic accounting, each new stock move layer (SVL), that is created during inventory valuation updates, generates a journal entry." msgstr "" @@ -12969,63 +13187,63 @@ msgstr "" msgid "Inventory Valuation field on the product category, with its various stock accounts." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:94 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:100 msgid "Costing method" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:96 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:102 msgid "After :ref:`enabling inventory valuation `, the *costing method* for calculating and recording inventory costs is defined on the product category in Odoo." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:100 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:106 msgid "Go to :menuselection:`Inventory app --> Configuration --> Product Categories` and select the desired product category. In the :guilabel:`Inventory Valuation` section, select the appropriate :guilabel:`Costing Method`:" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:104 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:110 msgid ":guilabel:`Standard Price`: the default costing method in Odoo. The cost of the product is manually defined on the product form, and this cost is used to compute the valuation. Even if the purchase price on a purchase order differs, the valuation will still use the cost defined on the product form." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:108 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:114 msgid ":guilabel:`Average Cost (AVCO)`: calculates the valuation of a product based on the average cost of that product, divided by the total number of available stock on-hand. With this costing method, inventory valuation is *dynamic*, and constantly adjusts based on the purchase price of products." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:113 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:119 msgid "When choosing :guilabel:`Average Cost (AVCO)` as the :guilabel:`Costing Method`, changing the numerical value in the :guilabel:`Cost` field for products in the respective product category creates a new record in the *Inventory Valuation* report to adjust the value of the product. The :guilabel:`Cost` amount will then automatically update based on the average purchase price both of inventory on hand and the costs accumulated from validated purchase orders." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:119 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:125 msgid ":guilabel:`First In First Out (FIFO)`: tracks the costs of incoming and outgoing items in real-time and uses the real price of the products to change the valuation. The oldest purchase price is used as the cost for the next good sold until an entire lot of that product is sold. When the next inventory lot moves up in the queue, an updated product cost is used based on the valuation of that specific lot. This method is arguably the most accurate inventory valuation method for a variety of reasons, however, it is highly sensitive to input data and human error." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:127 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:133 msgid "Changing the costing method greatly impacts inventory valuation. It is highly recommended to consult an accountant first before making any adjustments here." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:131 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:137 msgid ":doc:`using_inventory_valuation`" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:133 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:139 msgid "When the :guilabel:`Costing Method` is changed, products already in stock that were using the :guilabel:`Standard` costing method **do not** change value; rather, the existing units keep their value, and any product moves from then on affect the average cost, and the cost of the product will change. If the value in the :guilabel:`Cost` field on a product form is changed manually, Odoo generates a corresponding record in the *Inventory Valuation* report." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:140 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:146 msgid "It is possible to use different valuation settings for different product categories." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:145 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:151 msgid "Types of accounting" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:147 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:153 msgid "With automated inventory valuation set up, the generated journal entries depend on the chosen accounting mode: *Continental* or *Anglo-Saxon*." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:151 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:157 msgid "Verify the accounting mode by activating the :ref:`developer-mode`, and navigating to :menuselection:`Accounting app --> Configuration --> Settings`." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:154 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:160 msgid "Then, in the :guilabel:`Search...` bar, look for `Anglo-Saxon Accounting`, to see if the feature is enabled. If it is **not** enabled, *Continental* accounting mode is in use." msgstr "" @@ -13033,49 +13251,49 @@ msgstr "" msgid "Show the Anglo-Saxon accounting mode feature." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:161 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:167 msgid "In *Anglo-Saxon* accounting, the costs of goods sold (COGS) are reported when products are sold or delivered. This means the cost of a good is only recorded as an expense when a customer is invoiced for a product." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:165 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:171 msgid "So, for **manual** valuation method, set the *Expense Account* to *Stock Valuation* for the current asset type; for **automatic** valuation method, set the *Expense Account* to an *Expenses* or a *Cost of Revenue* type (e.g. *Cost of Production*, *Cost of Goods Sold*, etc.)." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:169 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:175 msgid "In *Continental* accounting, the cost of a good is reported as soon as a product is received into stock. Because of this, the *Expense Account* can be set to **either** *Expenses* or a *Cost of Revenue* type, however, it is more commonly set to an *Expenses* account." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:173 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:179 msgid "Refer to the :ref:`Expense ` and :ref:`Stock input/output ` sections for details on configuring each account type." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:180 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:186 msgid "Expense account" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:182 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:188 msgid "To configure the *expense account*, which is used in both manual and automatic inventory valuation, go to the :guilabel:`Account Properties` section of the intended product category (:menuselection:`Inventory app --> Configuration --> Product Categories`). Then, choose an existing account from the :guilabel:`Expense Account` drop-down menu." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:187 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:193 msgid "To ensure the chosen account is the correct :guilabel:`Type,` click the |right arrow| icon to the right of the account. Then, set the account type based on the information below." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:192 -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:260 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:198 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:266 msgid "Anglo-Saxon" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:196 -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:223 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:202 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:229 msgid "Automated" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:198 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:204 msgid "In Anglo-Saxon accounting for automated inventory valuation, set the :guilabel:`Expense Account` to the `Expenses` account. Then, click the |right arrow| icon to the right of the account." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:202 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:208 msgid "In the pop-up window, choose :guilabel:`Expenses` or :guilabel:`Cost of Revenue` from the :guilabel:`Type` drop-down menu." msgstr "" @@ -13083,7 +13301,7 @@ msgstr "" msgid "Show **Expense Account** field, and external link icon." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:211 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:217 msgid "To configure the :guilabel:`Expense Account`, choose :guilabel:`Stock Valuation` from the field's drop-down menu. Verify the account's type by clicking the |right arrow| icon, and then ensure the :guilabel:`Type` is :guilabel:`Current Assets`." msgstr "" @@ -13091,49 +13309,49 @@ msgstr "" msgid "Show the **Expense Account** field." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:219 -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:278 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:225 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:284 msgid "Continental" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:225 -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:230 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:231 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:236 msgid "Set the :guilabel:`Expense Account` to the :guilabel:`Expenses` or :guilabel:`Cost of Revenue` account type." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:236 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:242 msgid "Stock input/output (automated only)" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:238 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:244 msgid "To configure the :guilabel:`Stock Input Account` and :guilabel:`Stock Output Account`, go to :menuselection:`Inventory app --> Configuration --> Product Categories` and select the desired product category." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:242 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:248 msgid "In the :guilabel:`Inventory Valuation` field, select :guilabel:`Automated`. Doing so makes the :guilabel:`Account Stock Properties` section appear. These accounts are defined as follows:" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:245 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:251 msgid ":guilabel:`Stock Valuation Account`: when automated inventory valuation is enabled on a product, this account will hold the current value of the products." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:247 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:253 msgid ":guilabel:`Stock Journal`: accounting journal where entries are automatically posted when a product's inventory valuation changes." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:249 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:255 msgid ":guilabel:`Stock Input Account`: counterpart journal items for all incoming stock moves will be posted in this account, unless there is a specific valuation account set on the source location. This is the default value for all products in a given category, and can also be set directly on each product." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:253 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:259 msgid ":guilabel:`Stock Output Account`: counterpart journal items for all outgoing stock moves will be posted in this account, unless there is a specific valuation account set on the destination location. This is the default value for all products in a given category, and can also be set directly on each product." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:262 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:268 msgid "In Anglo-Saxon accounting, the :guilabel:`Stock Input Account` and :guilabel:`Stock Output Account` are set to *different* :guilabel:`Current Assets` accounts. This way, delivering products and invoicing the customer balance the *Stock Output* account, while receiving products and billing vendors balance the *Stock Input* account." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:267 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:273 msgid "To modify the account type, go to the click the |right arrow| icon to the right of the stock input/output account. In the pop-up window, choose :guilabel:`Current Assets` from the :guilabel:`Type` drop-down menu." msgstr "" @@ -13141,15 +13359,15 @@ msgstr "" msgid "Display account setup page, highlighting the **Type** field." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:275 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:281 msgid "The *Stock Input* account is set to `Stock Interim (Received)`, a *Current Asset* account type." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:280 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:286 msgid "In Continental accounting, the :guilabel:`Stock Input Account` and :guilabel:`Stock Output Account` are set to **the same** :guilabel:`Current Assets` account. That way, one account can be balanced when items are bought and sold." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:285 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:291 msgid "The stock input and output accounts are both set to `Stock Interim (Received)`, a :guilabel:`Current Assets` account type. They can also be set to the `Stock Interim (Delivered)`, as long as the input and output accounts are assigned to the **same** account." msgstr "" @@ -13157,23 +13375,23 @@ msgstr "" msgid "Show the Stock Input and Output accounts." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:295 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:301 msgid "Inventory valuation reporting" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:297 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:303 msgid "To start, go to :menuselection:`Accounting app --> Reporting --> Balance Sheet`. Click the :guilabel:`Current Assets` line item to unfold the drop-down menu, and look for the nested :guilabel:`Stock Valuation`, :guilabel:`Stock Interim (Received)`, and :guilabel:`Stock Interim (Delivered)` lines." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:303 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:309 msgid "At the top of the dashboard, click the :guilabel:`As of [date]` button to display accounting records up to a specified date." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:307 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:313 msgid ":ref:`Stock accounts and what they do `" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:308 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:314 msgid ":doc:`../../../../finance/accounting/get_started/cheat_sheet`" msgstr "" @@ -13181,11 +13399,11 @@ msgstr "" msgid "See the full inventory valuation breakdown in Odoo Accounting app." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:314 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:320 msgid "Access more specific information by clicking the :icon:`fa-ellipsis-v` :guilabel:`(ellipsis)` icon to the right of the desired journal. Select :guilabel:`General Ledger` to see a list of all of the journal entries, where each line item's :icon:`fa-ellipsis-v` :guilabel:`(ellipsis)` icon can be clicked to reveal the :guilabel:`View Journal Entry` option to open the individualized journal entry." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:320 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.rst:326 msgid "Additionally, annotations to the :guilabel:`Balance Sheet` can be added by choosing :guilabel:`Annotate`, filling in the text box, and clicking :guilabel:`Save`." msgstr "" @@ -14276,7 +14494,7 @@ msgid ":guilabel:`Unit`: the unit of measure of the product." msgstr "" #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/reporting/locations.rst:40 -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/reporting/stock.rst:52 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/reporting/stock.rst:51 msgid "Click the buttons to the right of each row item to access additional information:" msgstr "" @@ -14485,7 +14703,7 @@ msgid ":guilabel:`Status`: indicates the move status, which can be :guilabel:`Do msgstr "" #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/reporting/moves_history.rst:42 -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/reporting/stock.rst:66 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/reporting/stock.rst:65 msgid "Search options" msgstr "" @@ -14494,12 +14712,12 @@ msgid "Use the following search options to customize the :guilabel:`Moves Histor msgstr "" #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/reporting/moves_history.rst:49 -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/reporting/stock.rst:70 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/reporting/stock.rst:69 msgid "Filters" msgstr "" #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/reporting/moves_history.rst:51 -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/reporting/stock.rst:72 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/reporting/stock.rst:71 msgid "The :guilabel:`Filters` section allows users to search among pre-made and custom filters to find specific stock records." msgstr "" @@ -14540,7 +14758,7 @@ msgid ":guilabel:`Last 3 Months`: show records from the last three months." msgstr "" #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/reporting/moves_history.rst:68 -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/reporting/stock.rst:113 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/reporting/stock.rst:112 msgid "Group By" msgstr "" @@ -14577,7 +14795,7 @@ msgid ":guilabel:`Batch Transfer`: group records by :doc:`batch <../advanced_ope msgstr "" #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/reporting/moves_history.rst:87 -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/reporting/stock.rst:125 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/reporting/stock.rst:124 msgid "Favorites" msgstr "" @@ -14590,12 +14808,12 @@ msgid "Optionally, tick the :guilabel:`Default filter` checkbox to make this cur msgstr "" #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/reporting/moves_history.rst:96 -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/reporting/stock.rst:134 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/reporting/stock.rst:133 msgid "Lastly, click the :guilabel:`Save` button." msgstr "" #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/reporting/moves_history.rst:99 -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/reporting/stock.rst:137 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/reporting/stock.rst:136 msgid ":doc:`../../../../essentials/search`" msgstr "" @@ -14624,74 +14842,74 @@ msgid "On the stock report, the left sidebar includes several groupings to narro msgstr "" #: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/reporting/stock.rst:26 -msgid "The :guilabel:`Warehouse` grouping is only available when there are multiple warehouses in the database. Refer to the :doc:`../inventory_management/create_a_second_warehouse` documentation for more details." +msgid "The :guilabel:`Warehouse` grouping is only available when there are multiple warehouses in the database. Refer to the :doc:`../inventory_management/warehouses` documentation for more details." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/reporting/stock.rst:30 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/reporting/stock.rst:29 msgid "In the report itself, the columns represent:" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/reporting/stock.rst:32 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/reporting/stock.rst:31 msgid ":guilabel:`Product`: name of the product." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/reporting/stock.rst:33 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/reporting/stock.rst:32 msgid ":guilabel:`Unit Cost`: average inventory valuation per unit, adjusted based on the cost to purchase and/or manufacture the product." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/reporting/stock.rst:35 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/reporting/stock.rst:34 msgid ":guilabel:`Total Value`: Total inventory valuation of the product, calculated by multiplying unit cost by on-hand quantity." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/reporting/stock.rst:39 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/reporting/stock.rst:38 msgid ":ref:`Compute average cost inventory valuation per unit `" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/reporting/stock.rst:40 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/reporting/stock.rst:39 msgid ":doc:`Inventory valuation methods <../inventory_valuation/inventory_valuation_config>`" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/reporting/stock.rst:42 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/reporting/stock.rst:41 msgid ":guilabel:`On Hand`: current quantity of products. Click the :icon:`fa-pencil` :guilabel:`(pencil)` icon to :doc:`modify the on-hand quantity <../inventory_management/count_products>`." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/reporting/stock.rst:45 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/reporting/stock.rst:44 msgid ":guilabel:`Free to Use`: on-hand quantity that are **not** reserved for delivery or manufacturing orders, and are available to sell or use." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/reporting/stock.rst:47 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/reporting/stock.rst:46 msgid ":guilabel:`Incoming`: items expected to arrive at the warehouse. Number of products is based on quantities in confirmed purchase orders." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/reporting/stock.rst:49 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/reporting/stock.rst:48 msgid ":guilabel:`Outgoing`: items expected to leave the warehouse or be consumed in manufacturing orders. Number of products is based on quantities in confirmed sales or manufacturing orders." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/reporting/stock.rst:54 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/reporting/stock.rst:53 msgid ":guilabel:`History`: access the stock move history of the product, displaying information about the quantity and description of why the product was moved from one location to another." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/reporting/stock.rst:56 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/reporting/stock.rst:55 msgid ":guilabel:`Replenishment`: access the :doc:`reordering rules <../../product_management/product_replenishment/reordering_rules>` page for the product to create or manage methods of procuring the product." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/reporting/stock.rst:59 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/reporting/stock.rst:58 msgid ":guilabel:`Locations`: break down of on-hand quantity at multiple storage locations. Only available when the product is stored in multiple locations." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/reporting/stock.rst:61 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/reporting/stock.rst:60 msgid ":guilabel:`Forecast`: access the forecasted report to view on-hand, incoming, and outgoing quantities. Report also contains links to confirmed purchase, sales, or manufacturing orders. Only available when there are confirmed sales, purchase, or manufacturing orders for the product." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/reporting/stock.rst:75 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/reporting/stock.rst:74 msgid ":guilabel:`Published`: display products published on the website. Only available with the *Website* app installed." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/reporting/stock.rst:77 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/reporting/stock.rst:76 msgid ":guilabel:`Available in POS`: display products available through the *Point of Sale* app." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/reporting/stock.rst:78 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/reporting/stock.rst:77 msgid ":guilabel:`Available in Self`: display products available in self order through the *Point of Sale* app. Appears in the search because the :guilabel:`Available in Self Order` checkbox was ticked in the :guilabel:`Point of Sale` section of a product form's :guilabel:`Sales` tab. The option is only available when the :guilabel:`Available in POS` checkbox is ticked." msgstr "" @@ -14699,63 +14917,63 @@ msgstr "" msgid "In the Sales tab of a product form, showing *Available in Self Order* setting." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/reporting/stock.rst:87 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/reporting/stock.rst:86 msgid ":guilabel:`Not available in Self`: display products available in *PoS*, but not available in self order." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/reporting/stock.rst:91 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/reporting/stock.rst:90 msgid "`Configure PoS products `_" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/reporting/stock.rst:93 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/reporting/stock.rst:92 msgid ":guilabel:`Can be Sold`: display products that can be sold to customers. Appears in the search because the :guilabel:`Can be Sold` checkbox is ticked on the product form." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/reporting/stock.rst:95 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/reporting/stock.rst:94 msgid ":guilabel:`Can be Purchased`: display products that can be bought from vendors. Appears in the search because the :guilabel:`Can be Purchased` checkbox is ticked on the product form." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/reporting/stock.rst:97 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/reporting/stock.rst:96 msgid ":guilabel:`Can be Recurring`: show subscription products, indicated by ticking the :guilabel:`Recurring` checkbox on the product form. Only available with the *Subscription* app activated." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/reporting/stock.rst:100 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/reporting/stock.rst:99 msgid ":guilabel:`Can be Rented`: show products that can be loaned to customers for a certain time. Appears in the search because the :guilabel:`Can be Rented` checkbox was ticked on the product form. Only available with the *Rental* app installed." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/reporting/stock.rst:103 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/reporting/stock.rst:102 msgid ":guilabel:`Can be Subcontracted`: display products that can be produced by a :doc:`third-party manufacturer <../../../manufacturing/subcontracting/subcontracting_basic>`. Available only with the *Manufacturing* app installed." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/reporting/stock.rst:107 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/reporting/stock.rst:106 msgid ":guilabel:`Can be Expensed`: show items that can be expensed. Only available with the *Expenses* app installed." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/reporting/stock.rst:111 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/reporting/stock.rst:110 msgid ":doc:`../../product_management/product_tracking/type`" msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/reporting/stock.rst:115 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/reporting/stock.rst:114 msgid "The :guilabel:`Group By` section allows users to add pre-made and custom groupings to the search results." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/reporting/stock.rst:118 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/reporting/stock.rst:117 msgid ":guilabel:`Product Type`: group items by :doc:`product type <../../product_management/product_tracking/type>`." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/reporting/stock.rst:120 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/reporting/stock.rst:119 msgid ":guilabel:`Product Category`: group items by product category. To configure these, go to :menuselection:`Inventory app --> Configuration --> Products: Product Categories`." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/reporting/stock.rst:122 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/reporting/stock.rst:121 msgid ":guilabel:`POS Product Category`: group items by :doc:`point of sale product categories <../../../../sales/point_of_sale/configuration>`." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/reporting/stock.rst:127 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/reporting/stock.rst:126 msgid "To save the current applied filters and groupbys, so the same information can be easily accessed after closing this page, click :guilabel:`Save current search`." msgstr "" -#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/reporting/stock.rst:130 +#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/reporting/stock.rst:129 msgid "Optionally, tick the :guilabel:`Default filter` checkbox to make this current view the default filter when opening the stock report. Or tick the :guilabel:`Shared` checkbox to make the search option available to other users." msgstr "" @@ -16908,6 +17126,238 @@ msgstr "" msgid "The section above provides instructions for creating a basic |BOM| that allows a product to be manufactured in Odoo. However, it is by no means an exhaustive summary of all the options available when configuring a |BOM|. For more information about bills of materials, see the documentation on how to :doc:`create a bill of materials `." msgstr "" +#: ../../content/applications/inventory_and_mrp/manufacturing/basic_setup/mo_costs.rst:3 +msgid "Manufacturing order costs" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/basic_setup/mo_costs.rst:11 +msgid "The ability to accurately calculate the cost of manufacturing a product is critical when determining product profitability. Odoo's *Manufacturing* app simplifies this calculation by automatically calculating the cost to complete each manufacturing order (MO), as well as the average production cost of a product, based on all completed |MOs|." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/basic_setup/mo_costs.rst:17 +msgid "Odoo's Manufacturing app distinguishes between the *manufacturing order cost* and the *real cost* of an |MO|." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/basic_setup/mo_costs.rst:20 +msgid "The |MO| cost represents how much it *should* cost to complete an |MO|, based on the configuration of the product's bill of materials (BoM). This takes into account the cost and quantity of components, as well as the cost of completing the necessary operations." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/basic_setup/mo_costs.rst:24 +msgid "The real cost represents how much it *actually* costs to complete the |MO|. A few factors can cause the real cost to differ from the |MO| cost. For example, an operation may take longer to complete than estimated, a greater component quantity might be needed than was specified on the |BoM|, or the price of components may change during manufacturing." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/basic_setup/mo_costs.rst:30 +msgid "Cost configuration" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/basic_setup/mo_costs.rst:32 +msgid "Odoo computes |MO| costs based on the configuration of the |BoM| used to manufacture a product. This includes the cost and quantity of components and operations listed on the |BoM|, in addition to the operating costs of the work centers where those operations are carried out." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/basic_setup/mo_costs.rst:37 +msgid "Component cost" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/basic_setup/mo_costs.rst:39 +msgid "Component cost is calculated automatically, based on the average purchase cost of a component across all purchase orders (POs). To view a component's cost, navigate to :guilabel:`Inventory app --> Products --> Products`, and select a component product. The cost is displayed in the :guilabel:`Cost` field of the :guilabel:`General Information` tab, on the component's product form." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/basic_setup/mo_costs.rst:44 +msgid "It is possible to set the cost of a component manually, by clicking the :guilabel:`Cost` field on the component's product form, and entering a value. However, any future |POs| for the component override a value entered manually, resetting the :guilabel:`Cost` field back to an automatically computed value." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/basic_setup/mo_costs.rst:50 +msgid "Work center cost" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/basic_setup/mo_costs.rst:52 +msgid "To set the operating cost for a specific work center, navigate to :menuselection:`Manufacturing app --> Configuration --> Work Centers`, and select a work center." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/basic_setup/mo_costs.rst:55 +msgid "To set the operating cost for the work center, as a whole, enter a value in the :guilabel:`per workcenter` field, located beside the :guilabel:`Cost per hour` section on the work center's :guilabel:`General Information` tab. This operating cost is used regardless of how many employees are working at the work center at any given time." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/basic_setup/mo_costs.rst:60 +msgid "To set the operating cost for the work center based on the number of employees working there at a given time, enter a value in the :guilabel:`per employee` field, located beside the :guilabel:`Cost per hour` section on the work center's :guilabel:`General Information` tab. For example, if `25.00` is entered in the :guilabel:`per employee` field, it costs $25.00 per hour for *each* employee working at the work center." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/basic_setup/mo_costs.rst:66 +msgid "Note that, if values are entered in both the :guilabel:`per workcenter` *and* :guilabel:`per employee` fields, the value in the :guilabel:`per workcenter` field takes precedence, and the value in the :guilabel:`per employee` field is ignored." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/basic_setup/mo_costs.rst:71 +msgid "It is also possible to set a per hour cost for specific employees, by navigating to the :menuselection:`Employees` app, selecting an employee, clicking the :guilabel:`HR Settings` tab on their employee form, and entering a value in the :guilabel:`Hourly Cost` field." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/basic_setup/mo_costs.rst:75 +msgid "Just like the *per workcenter* field on a work center form, the :guilabel:`Hourly Cost` field on an employee's form overrides the *per employee* field on a work center form." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/basic_setup/mo_costs.rst:78 +msgid "However, the *per workcenter* field takes precedence over both the *per employee* field on the workcenter form *and* the :guilabel:`Hourly Cost` field on the employee form." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/basic_setup/mo_costs.rst:82 +msgid "|BoM| cost" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/basic_setup/mo_costs.rst:84 +msgid "Configuring a |BoM| so Odoo can accurately calculate the cost of |MOs| that use it requires two steps. First, components **must** be added, and the required quantity specified. Second, operations **must** be added, along with the work centers where they are carried out." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/basic_setup/mo_costs.rst:88 +msgid "Begin by navigating to :menuselection:`Manufacturing app --> Products --> Bills of Materials`. Select a |BoM|, or create a new one by clicking :guilabel:`New`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/basic_setup/mo_costs.rst:91 +msgid "In the :guilabel:`Components` tab of the |BoM| form, add each component by clicking :guilabel:`Add a line`, selecting the component from the drop-down menu in the :guilabel:`Component` column, and entering the quantity in the :guilabel:`Quantity` column." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/basic_setup/mo_costs.rst:95 +msgid "In the :guilabel:`Operations` tab, add an operation by clicking :guilabel:`Add a line` to open the :guilabel:`Create Operations` pop-up window. Enter a title for the operation in the :guilabel:`Operation` field." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/basic_setup/mo_costs.rst:99 +msgid "Select the :guilabel:`Work Center` where the operation is carried out. Then, add a :guilabel:`Default Duration`, which is the estimated amount of time the operation takes to complete." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/basic_setup/mo_costs.rst:102 +msgid "By default, the :guilabel:`Duration Computation` field is set to :guilabel:`Set duration manually`, which means that the number entered in :guilabel:`Default Duration` field is always used as the expected duration of the operation." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/basic_setup/mo_costs.rst:106 +msgid "Selecting :guilabel:`Compute based on tracked time` causes Odoo to automatically compute the default duration based on a certain number of work orders, which is set in the :guilabel:`Based on` field. Before there are work orders to compute this duration, the value in the :guilabel:`Default Duration` field is used instead." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/basic_setup/mo_costs.rst:111 +msgid "The hourly cost of operating the work center, and the duration of the operation, are used to calculate the operation's cost." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/basic_setup/mo_costs.rst:114 +msgid "Finally, click :guilabel:`Save & Close` to add the operation to the |BoM|, and close the :guilabel:`Create Operations` pop-up window. Alternatively, click :guilabel:`Save & New` to add the operation to the |BoM|, and open a blank :guilabel:`Create Operations` pop-up window to add another operation." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/basic_setup/mo_costs.rst:120 +msgid "For a full overview of |BoM| configuration, see the documentation on :doc:`bills of materials `." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/basic_setup/mo_costs.rst:124 +msgid "|MO| overview" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/basic_setup/mo_costs.rst:126 +msgid "Each |MO| has an *overview* page, which lists a variety of information about the |MO|, including |MO| cost and real cost. To view the overview for an |MO|, navigate to :menuselection:`Manufacturing app --> Operations --> Manufacturing Orders`, and select an |MO|. Then, click the :icon:`fa-bars` :guilabel:`Overview` smart button at the top of the |MO|." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/basic_setup/mo_costs.rst:131 +msgid "Both the |MO| cost and real cost take into account the cost and quantity of components, as well as the cost of completing each work order. The overview page lists a row for each of these values, with the sum of them listed at the bottom of the :guilabel:`MO Cost` and :guilabel:`Real Cost` columns." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/basic_setup/mo_costs.rst:135 +msgid "Before work begins on an |MO|, the :guilabel:`MO Cost` and :guilabel:`Real Cost` columns display the same costs. This is the *estimated* cost of completing the |MO|." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/basic_setup/mo_costs.rst:138 +msgid "However, once work commences, the values in the :guilabel:`Real Cost` column may begin to diverge from the values in the :guilabel:`MO Cost` column. This happens if a different component quantity is used than was listed on the |MO|, or if the duration of a work order is different than expected." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/basic_setup/mo_costs.rst:142 +msgid "Once the |MO| has been completed by clicking :guilabel:`Produce All`, the values in the :guilabel:`MO Cost` column update to match those displayed in the :guilabel:`Real Cost` column." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/basic_setup/mo_costs.rst:-1 +msgid "The MO Overview page." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/basic_setup/mo_costs.rst:150 +msgid "Average manufacturing cost" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/basic_setup/mo_costs.rst:152 +msgid "In addition to the cost of each individual |MO| for a product, Odoo also tracks the average cost of manufacturing the product, taking into account the cost of every completed |MO|. To view this, navigate to :menuselection:`Inventory app --> Products --> Products`, and select a product." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/basic_setup/mo_costs.rst:156 +msgid "The manufacturing cost of the product is displayed per unit of measure in the :guilabel:`Cost` field, located in the :guilabel:`General Information` tab. The value continues to update as the costs of additional |MOs| are factored into the average cost." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/basic_setup/mo_costs.rst:160 +msgid "To the right of the :guilabel:`Cost` field is a :guilabel:`Compute Price from BoM` button, which only appears for products with at least one |BoM|. Click this button to reset the cost of the product to the expected cost, which only takes into account the components and operations listed on the |BoM|." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/basic_setup/mo_costs.rst:167 +msgid "Be aware that clicking :guilabel:`Compute Price from BoM` does not set the price permanently. The cost continues to update based on the average of the |BoM| price and the real cost of any future |MOs|." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/basic_setup/mo_costs.rst:171 +msgid "Example workflow: manufacturing cost" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/basic_setup/mo_costs.rst:174 +msgid "Golf product manufacturer *Fairway Fields* produces a variety of golf products, including an indoor *putting green*. They have configured a |BoM| for the putting green, so Odoo automatically calculates the manufacturing cost of each putting green |MO|." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/basic_setup/mo_costs.rst:178 +msgid "The |BoM| lists two components:" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/basic_setup/mo_costs.rst:180 +msgid "One unit of *green felt*, which costs $20.00." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/basic_setup/mo_costs.rst:181 +msgid "One unit of a *rubber pad*, which costs $30.00." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/basic_setup/mo_costs.rst:183 +msgid "The |BoM| also lists four operations, all of which are carried out at *Assembly Station 1*, which has an hourly operating cost of $30.00. Those operations are as follows:" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/basic_setup/mo_costs.rst:186 +msgid "*Cut felt*: default duration of seven minutes, for a total cost of $3.50." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/basic_setup/mo_costs.rst:187 +msgid "*Cut rubber pad*: default duration of five minutes, for a total cost of $2.50." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/basic_setup/mo_costs.rst:188 +msgid "*Attach pad to felt*: default duration of 15 minutes, for a total cost of $7.50." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/basic_setup/mo_costs.rst:189 +msgid "*Cut holes*: default duration of three minutes, for a total cost of $1.50." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/basic_setup/mo_costs.rst:191 +msgid "Altogether, the components required to produce one putting green cost $50.00, and the operations required cost $15.00, for a total manufacturing cost of $65.00. This cost is reflected in the :guilabel:`Cost` field on the putting green's product form." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/basic_setup/mo_costs.rst:195 +msgid "Fairway Fields confirms an |MO| for one putting green. Before manufacturing starts, the |MO| overview lists a cost of `$65.00` in both the :guilabel:`MO Cost` and :guilabel:`Real Cost` fields." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/basic_setup/mo_costs.rst:-1 +msgid "The MO Overview page for one putting green, before production starts." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/basic_setup/mo_costs.rst:203 +msgid "Manufacturing begins, and the operations take ten minutes longer than expected, for a total manufacturing time of 40 minutes. This deviation from the |BoM| is reflected on the |MO| overview, which now lists a :guilabel:`Real Cost` of `$70.00`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/basic_setup/mo_costs.rst:-1 +msgid "The MO Overview page for one putting green, during production." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/basic_setup/mo_costs.rst:211 +msgid "Once manufacturing is finished, and the |MO| is marked as *Done*, the |MO| overview updates again, so the values in the :guilabel:`MO Cost` and :guilabel:`Real Cost` columns match, each displaying a value of `$70.00`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/basic_setup/mo_costs.rst:215 +msgid "On the putting green's product page, the :guilabel:`Cost` field now displays a cost of `$67.50`, the average of the original cost of $65.00 and the real cost of $70.00 from the |MO|." +msgstr "" + #: ../../content/applications/inventory_and_mrp/manufacturing/basic_setup/one_step_manufacturing.rst:3 msgid "One-step manufacturing" msgstr "" @@ -18998,6 +19448,245 @@ msgstr "" msgid "The Product Moves page for an MO with by-products." msgstr "" +#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/continuous_improvement.rst:3 +msgid "Continuous product improvement" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/continuous_improvement.rst:13 +msgid "*Continuous improvement* is a general philosophy intended to help individuals and organizations constantly improve themselves and the work they produce." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/continuous_improvement.rst:16 +msgid "There are a variety of different methodologies that fall under the umbrella of continuous improvement. These include kaizen, six sigma, and lean, among others. While the specific steps of each method differ, their goal remains the same: implement a process by which improvement is a perpetual goal, rather than a one-time accomplishment." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/continuous_improvement.rst:21 +msgid "The sections below contain details about how Odoo can be used to implement four general steps common to many of the most popular continuous improvement strategies, with links to documentation about configuring the necessary features. The final section details how a specific company might configure these Odoo implementations within their organization." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/continuous_improvement.rst:26 +msgid ":ref:`manufacturing/workflows/ci-identify`" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/continuous_improvement.rst:27 +msgid ":ref:`manufacturing/workflows/ci-suggest`" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/continuous_improvement.rst:28 +msgid ":ref:`manufacturing/workflows/ci-implement`" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/continuous_improvement.rst:29 +msgid ":ref:`manufacturing/workflows/ci-review`" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/continuous_improvement.rst:32 +msgid "Continuous improvement is not a one-size-fits-all methodology. While most strategies include between four and six steps, proper implementation requires developing a system tailored to the specific needs of each company." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/continuous_improvement.rst:36 +msgid "This is not a limitation, but rather a benefit, as it makes the methodology flexible enough to adapt to almost any use case. Odoo, in particular, adapts well to this flexibility, as it can be configured to meet the needs of almost any workflow." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/continuous_improvement.rst:40 +msgid "As such, it is important to remember the content below only provides *examples* of how Odoo *might* be used. They should be viewed as more of a starting point, rather than a concrete outline that every organization must follow." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/continuous_improvement.rst:47 +msgid "Identify problems" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/continuous_improvement.rst:49 +msgid "Before improvement can begin, it is necessary to determine where improvement is necessary. This is where identifying problems comes into play. Two of the best Odoo apps for identifying problems with products or processes are *Helpdesk* and *Quality*." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/continuous_improvement.rst:54 +msgid "Helpdesk" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/continuous_improvement.rst:56 +msgid "The *Helpdesk* app is useful for receiving feedback from outside of the organization, like from clients or customers. This is accomplished by implementing one (or more) of the methods for :doc:`receiving tickets <../../../services/helpdesk/overview/receiving_tickets>`, including email aliases, live chat conversations, and website forms." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/continuous_improvement.rst:61 +msgid "Using these methods, customers can submit feedback about problems, which is then reviewed by a member of a :doc:`helpdesk team <../../../services/helpdesk>`. Depending on the outcome of the review, the team member may decide to take further action to ensure the issue is addressed. This can include creating a :doc:`quality alert <../../quality/quality_management/quality_alerts>`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/continuous_improvement.rst:67 +#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/continuous_improvement.rst:93 +#: ../../content/applications/inventory_and_mrp/quality.rst:7 +msgid "Quality" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/continuous_improvement.rst:69 +msgid "The *Quality* app is useful for receiving feedback from *within* the organization, like from employees." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/continuous_improvement.rst:72 +msgid "One method for accomplishing this is to set up a :doc:`quality control point <../../quality/quality_management/quality_control_points>` (QCP). A |QCP| is used to automatically create quality checks at regular intervals, prompting employees to inspect, and confirm, the quality of a product." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/continuous_improvement.rst:77 +msgid "If an issue is found, an employee can then create a :doc:`quality alert <../../quality/quality_management/quality_alerts>` to notify a quality team. Quality alerts can also be created independent of a |QCP|, in the event that an employee discovers an issue without being prompted to check for one. This is a great way for customer support employees to notify a quality team of an issue brought to their attention by a customer ticket." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/continuous_improvement.rst:86 +msgid "Suggest improvements" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/continuous_improvement.rst:88 +msgid "Once a problem is identified, the next step is to put forward ideas for how to address the problem. As with identifying problems, the *Quality app* is also useful for suggesting improvements. In addition, the *PLM* (*Product Lifecycle Management*) app can be used for this purpose, as well." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/continuous_improvement.rst:95 +msgid "When creating a :doc:`quality alert <../../quality/quality_management/quality_alerts>` to bring an issue to the attention of a quality team, the :guilabel:`Corrective Actions` and :guilabel:`Preventive Actions` tabs can be used to provide feedback about how the issue can be addressed." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/continuous_improvement.rst:100 +msgid "The :guilabel:`Corrective Actions` tab is used to suggest a method for fixing items affected by the issue. For example, `Screw the bolts on tighter, so the seat stays in place`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/continuous_improvement.rst:103 +msgid "The :guilabel:`Preventive Actions` tab is used to suggest a method for preventing the issue from occurring in the future. For example, `Do not tighten the screws too much, or they will be stripped`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/continuous_improvement.rst:107 +msgid "The quality team that reviews the alert sees these suggested actions, and can take them into account when deciding how to address the issue." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/continuous_improvement.rst:111 +#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/continuous_improvement.rst:132 +msgid "PLM" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/continuous_improvement.rst:113 +msgid "The |PLM| app is used to manage the lifecycle of a product from its introduction through each successive version. As such, it is useful for testing ideas for product improvements." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/continuous_improvement.rst:116 +msgid "Using :doc:`engineering change orders <../../plm/manage_changes/engineering_change_orders>`, product management teams can create new iterations of product |BoMs|, adding or removing specific components or operations, as needed. The products created using these |BoMs| are put through a review process to confirm the effectiveness of the changes." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/continuous_improvement.rst:124 +msgid "Implement strategies" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/continuous_improvement.rst:126 +msgid "Implementing strategies involves putting the proposed solutions from the suggest improvements step into action. The |PLM| app continues to be useful during this step, as it can be configured to make |BoM| updates. The *Field Service* app can also be used by certain companies to make improvements to products that have already been sold to customers." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/continuous_improvement.rst:134 +msgid "Once |BoM| changes have gone through the proper review process, they can be approved, and the updated |BoM| put into use. This is accomplished by configuring one of the |ECO| review stages to :ref:`apply the changes ` made to the |BoM|, at which point the updated |BoM| becomes available for new |MOs|." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/continuous_improvement.rst:139 +msgid "Product |BoMs| can continue to be updated, as needed. The :doc:`version control <../../plm/manage_changes/version_control>` features of the |PLM| app allow for easy management of all versions of a given |BoM|." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/continuous_improvement.rst:144 +msgid "Field Service" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/continuous_improvement.rst:146 +msgid "The |PLM| app is a great way to make changes to product |BoMs|. However, these changes only affect products produced using the new |BoM|. If a defective product has already been sold to a customer, it may be necessary to repair (or update) that product." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/continuous_improvement.rst:150 +msgid "In such a case, the *Field Service* app can be used to schedule :doc:`onsite interventions <../../../services/field_service/onsite_interventions>`. These interventions allow service technicians (or other employees) to be sent to a customer's location to address an issue with a product." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/continuous_improvement.rst:158 +msgid "Review actions" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/continuous_improvement.rst:160 +msgid "Reviewing actions is where the \"continuous\" part of continuous improvement comes into play, as it allows an organization to evaluate the decisions made in the previous steps. As such, this step is, essentially, returning to the beginning of the process, so that additional problems can be identified and addressed." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/continuous_improvement.rst:165 +msgid "This means that the *Helpdesk* and *Quality* apps should be used again to receive customer and employee feedback. Another app that may be useful at this stage is the *Surveys* app." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/continuous_improvement.rst:169 +msgid "Surveys" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/continuous_improvement.rst:171 +msgid "After implementing changes to a product or process, it may be wise to solicit customers for their feedback directly, rather than waiting to hear from them of their own volition. This may bring to light feedback that customers may have otherwise neglected to share." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/continuous_improvement.rst:175 +msgid "One of the best ways to accomplish this is through the :doc:`Surveys <../../../marketing/surveys>` app. Creating a survey, and sending it to customers who receive an updated product, increases the likelihood of receiving relevant feedback about the product." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/continuous_improvement.rst:179 +msgid "Example workflow: coat rack product improvement" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/continuous_improvement.rst:182 +msgid "*Wood Hut* is a manufacturer of fine wood products. They are committed to manufacturing products of the highest-possible quality, and are always looking for ways to improve the products they sell, along with the processes used to create them." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/continuous_improvement.rst:186 +msgid "Wood Hut uses the Odoo platform to manage every element of their production, fulfillment, and customer satisfaction processes. They have developed a custom product improvement workflow that incorporates the Helpdesk, Quality, PLM, and Manufacturing apps." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/continuous_improvement.rst:190 +msgid "One of Wood Hut's most popular products is their *coat rack*. It's made entirely of oak, and customers describe it as \"sleek and elegant.\" However, recent customer feedback about the coat rack has brought attention to quality issues that necessitate revising the current manufacturing process." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/continuous_improvement.rst:195 +msgid "The product revision workflow begins when the customer service team receives a ticket in the Helpdesk app from a customer having problems with the coat rack she purchased. The customer, Abigail Peterson, has found that her coat rack falls over when more than five coats are hanging from it. This is a major issue, as the coat rack has enough dowels for six coats." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/continuous_improvement.rst:-1 +msgid "A Helpdesk ticket about an issue with the coat rack product." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/continuous_improvement.rst:204 +msgid "Marc, the customer service employee assigned to the helpdesk ticket, opens the Quality app, and creates a new quality alert. He tags the *Production Quality Team* and assigns Julie Andreson as the quality employee responsible for the alert." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/continuous_improvement.rst:208 +msgid "Julie reviews the alert, and consults with her team about the best course of action. They decide that it is necessary to revise the product's |BoM| to prevent the issue from occurring in the future, which Julie notes in the :guilabel:`Corrective Actions` tab of the quality alert." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/continuous_improvement.rst:-1 +msgid "A quality alert created about the issue with the coat rack product." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/continuous_improvement.rst:216 +msgid "Then, Julie messages product engineer, Joe Kazan in the chatter of the quality alert to bring it to his attention. Joe opens the |PLM| app and creates a new |ECO|, noting the problem with the coat rack, and suggesting that a change to the product's |BoM| may be necessary." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/continuous_improvement.rst:-1 +msgid "An ECO created to update the coat rack product's BoM." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/continuous_improvement.rst:224 +msgid "Joe clicks :guilabel:`Start Revision`, and then the :guilabel:`Revision` smart button to open version two of the coat rack's |BoM|. This |BoM| was created alongside the |ECO|, and remains archived until it is approved." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/continuous_improvement.rst:228 +msgid "After some testing, Joe discovers that adding a metal *support rod* to the coat rack strengthens it, allowing the rack to hold six or more coats without falling over. He updates the |BoM| to include the support rod as one of the components, and adds an extra operation to make sure it is installed during the manufacturing process. Finally, he leaves a message in the chatter of the |ECO|, letting his manager, Jose, know that it is ready for review." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/continuous_improvement.rst:-1 +msgid "The coat rack BoM, updated to add an extra component and operation." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/continuous_improvement.rst:238 +msgid "Jose reviews the changes, and confirms they are an effective method for addressing the problem with the coat rack. He moves the |ECO| to the *Approved* stage, which makes version two of the coat rack |BoM| the current version." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/continuous_improvement.rst:242 +msgid "Now, each time an |MO| is created to produce a coat rack, the updated |BoM| is automatically selected. Wood Hut begins producing the improved coat rack, and customer feedback confirms that the new version has addressed the problem with its predecessor." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/continuous_improvement.rst:246 +msgid "Using the Odoo platform, Wood Hut has implemented an end-to-end product improvement process. Since the essential elements of this process (customer feedback, quality control, etc.) are always functioning, it can be reused to continuously update products and processes." +msgstr "" + #: ../../content/applications/inventory_and_mrp/manufacturing/workflows/manufacturing_backorders.rst:3 msgid "Manufacturing backorders" msgstr "" @@ -19136,6 +19825,174 @@ msgstr "" msgid "After the final work order for the backorder |MO| has been completed, the |MO| can be closed by clicking the :guilabel:`Close Production` button at the bottom of the work order's card." msgstr "" +#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/oee.rst:3 +msgid "Overall equipment effectiveness" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/oee.rst:9 +msgid "In Odoo's *Manufacturing* app, *overall equipment effectiveness* (OEE) represents the amount of time a work center is fully productive. |OEE| is displayed as a percentage of the total time a work center is active." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/oee.rst:13 +msgid "Fully productive time is considered to be time when the work center is operational **and** processing work orders that have not exceeded their *expected duration*." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/oee.rst:16 +msgid "|OEE| helps manufacturing teams understand the efficiency of work centers, and the causes of manufacturing downtime." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/oee.rst:20 +msgid "Since |OEE| tracks work center productivity, using it requires enabling the work centers feature in the settings of the Manufacturing app." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/oee.rst:23 +msgid "To do so, navigate to :menuselection:`Manufacturing app --> Configuration --> Settings`, and tick the checkbox next to :guilabel:`Work Orders`, under the :guilabel:`Operations` heading. Then, click :guilabel:`Save`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/oee.rst:28 +msgid "Efficiency standards" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/oee.rst:30 +msgid "For |OEE| to accurately reflect the percentage of fully productive time for a work center, the work center **must** be properly configured with the correct productivity metrics. These include the work center's *time efficiency*, *capacity*, and *OEE target*." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/oee.rst:35 +msgid "Time efficiency" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/oee.rst:37 +msgid "Time efficiency represents the efficiency of a work center when processing work orders, and is represented as a percentage. A time efficiency value of 100% signifies that the work center processes work orders at the speed of the expected duration, as listed on a product's |BoM|. A value less than or greater than 100% signifies that the work center processes work orders slower or faster than an operation's expected duration, respectively." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/oee.rst:43 +msgid "To set the time efficiency for a work center, navigate to :menuselection:`Manufacturing app --> Configuration --> Work Centers`, and select a work center. On the :guilabel:`General Information` tab, enter a numerical value in the :guilabel:`Time Efficiency` field." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/oee.rst:48 +msgid "Manufacturing a *chair* product requires two operations: *cut* and *assemble*. The product's |BoM| lists an expected duration of 30 minutes for each operation." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/oee.rst:51 +msgid "The cut operation is carried out at the *cut station* work center, which has a time efficiency value of 50%. This means it takes twice as long to complete the operation, for a total time of one hour." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/oee.rst:55 +msgid "The assemble operation is carried out at the *assembly line* work center, which has a time efficiency value of 200%. This means it takes half as long to complete the operation, for a total time of 15 minutes." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/oee.rst:60 +msgid "Capacity" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/oee.rst:62 +msgid "Capacity represents how many units of a product can be produced in parallel at a work center. The duration of work orders for multiple units increases or decreases, based on how many units the work center can handle." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/oee.rst:66 +msgid "To set the capacity for a work center, navigate to :menuselection:`Manufacturing app --> Configuration --> Work Centers`, and select a work center. On the :guilabel:`General Information` tab, enter a numerical value in the :guilabel:`Capacity` field." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/oee.rst:71 +msgid "A *drill station* work center has a capacity of one unit. An |MO| is confirmed for 10 units of a *chair*, a product manufactured using the drill station." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/oee.rst:74 +msgid "Since there are ten times as many units to produce than the work center can handle at once, the operation time is ten times the duration listed on the product's |BoM|." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/oee.rst:78 +msgid "|OEE| target" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/oee.rst:80 +msgid "The |OEE| target is the goal for how much of a work center's operating time should be fully productive time. It is displayed as a percentage, and should only be set as high as `100%`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/oee.rst:83 +msgid "To set the |OEE| target for a work center, navigate to :menuselection:`Manufacturing app --> Configuration --> Settings --> Work Centers`, and select a work center. On the :guilabel:`General Information` tab, enter a numerical value of `100.00` or less in the :guilabel:`OEE Target` field." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/oee.rst:88 +msgid "Calculating |OEE|" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/oee.rst:90 +msgid "|OEE| is represented as a percentage value between zero and 100. The value signifies the amount of time that a work center was fully productive. The remainder signifies the amount of time that the work center was operating at less than full efficiency. This can occur for a number of reasons, including *reduced speed*, *material availability*, and *equipment failure*." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/oee.rst:96 +msgid "Fully productive time" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/oee.rst:98 +msgid "For a work center to be considered fully productive, it must be able to receive work orders, have the components necessary to process work orders, and be operating within the expected duration of the work order it is processing." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/oee.rst:103 +msgid "An *assembly line* work center is not blocked, and receives a work order to assemble a *bicycle*. The required components are available, so production begins as soon as they are picked and delivered to the work center. The work order has an expected duration of 30 minutes, and is completed in 27 minutes. All of this time is considered fully productive time." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/oee.rst:109 +msgid "Reduced speed" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/oee.rst:111 +msgid "When a work center is operating at reduced speed, it means that it is processing a work order that has exceeded its expected duration. While the work center may be operational, this is not considered fully productive time." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/oee.rst:116 +msgid "A *cutting station* work center receives a work order to cut boards for a *table*. The expected duration of the work order is 15 minutes. The work order ends up taking 18 minutes to complete. The work center is considered to have been operating at reduced speed during the three minutes that exceeded the expected duration." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/oee.rst:122 +msgid "Material availability" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/oee.rst:124 +msgid "Material availability refers to situations where a work center is able to accept a work order, but the required components are not available. This can occur because the components are not in stock, or are reserved for a different order." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/oee.rst:129 +msgid "Manufacturing of a *bench* requires 20 units of *wood*. A manufacturing order (MO) is confirmed for 10 units of the bench, but there is not enough wood in stock to begin manufacturing. The time it takes to acquire the wood is recorded as material availability downtime." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/oee.rst:134 +msgid "Equipment failure" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/oee.rst:136 +msgid "Equipment failure signifies any period of time when a work center is unusable due to maintenance issues with its equipment. This can be due to equipment breaking down, or when a work center is shut down for scheduled maintenance. In these cases, a work center can be blocked using a :doc:`maintenance request <../../maintenance/maintenance_requests>`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/oee.rst:142 +msgid "The drill at a *drill station* work center breaks down, causing the work center to be unusable. A maintenance request is created to fix the drill, and the work center is blocked from receiving work orders. It takes two hours to fix the drill, and make the work center available again. This two-hour period is recorded as equipment failure downtime." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/oee.rst:148 +msgid "|OEE| reporting" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/oee.rst:150 +msgid "To view |OEE| reporting metrics for every work center, navigate to :menuselection:`Manufacturing app --> Reporting --> Overall Equipment Effectiveness`. This page shows the metrics for each work center with |OEE| data." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/oee.rst:154 +msgid "Alternatively, to see |OEE| reporting metrics for a single work center, navigate to :menuselection:`Manufacturing app --> Configuration --> Work Centers`, and select a work center. At the top of the work center's form, click the :icon:`fa-pie-chart` :guilabel:`OEE` smart button." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/oee.rst:158 +msgid "By default, the main |OEE| reporting page shows data in a bar chart, while the page for a specific work center shows it in a pie chart. To select a different chart type on either page, click the :icon:`fa-bar-chart` :guilabel:`(bar chart)`, :icon:`fa-line-chart` :guilabel:`(line chart)`, or :icon:`fa-pie-chart` :guilabel:`(pie chart)` button above the displayed chart." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/oee.rst:163 +msgid "It is also possible to see |OEE| data in a pivot view, or a list displaying each time entry, by clicking the :icon:`oi-view-pivot` :guilabel:`(pivot view)` or :icon:`oi-view-list` :guilabel:`(list view)` buttons at the top-right corner of the page." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/oee.rst:-1 +msgid "The dashboard of the OEE report." +msgstr "" + #: ../../content/applications/inventory_and_mrp/manufacturing/workflows/scrap_manufacturing.rst:3 msgid "Scrap during manufacturing" msgstr "" @@ -19149,7 +20006,7 @@ msgid "By default, scrapping a component or finished product removes it from phy msgstr "" #: ../../content/applications/inventory_and_mrp/manufacturing/workflows/scrap_manufacturing.rst:17 -msgid "For more information, see the documentation about the different types of :ref:`locations `." +msgid "For more information, see the documentation about the different types of :doc:`locations <../../inventory/warehouses_storage/inventory_management>`." msgstr "" #: ../../content/applications/inventory_and_mrp/manufacturing/workflows/scrap_manufacturing.rst:20 @@ -19415,99 +20272,285 @@ msgid "In some cases, components may be unusable after the unbuilding process is msgstr "" #: ../../content/applications/inventory_and_mrp/manufacturing/workflows/use_mps.rst:3 -msgid "Use the Master Production Schedule" +msgid "Master production schedule" msgstr "" -#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/use_mps.rst:7 -msgid "The Master Production Schedule (MPS) is a valuable tool to plan your production based on your demand forecast." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/use_mps.rst:13 -msgid "Go to the :menuselection:`Manufacturing app --> Configuration --> Settings` and activate the Master Production Schedule feature before hitting save." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/use_mps.rst:17 -msgid "In the MPS settings, you can define the time range of your MPS (month/week/day) and the number of periods you want to display at all times." +#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/use_mps.rst:16 +msgid "In Odoo's *Manufacturing* app, the *master production schedule* (MPS) is used to manually plan manufacturing orders (MOs) and purchase orders (POs), based on forecasted quantities of products and components." msgstr "" #: ../../content/applications/inventory_and_mrp/manufacturing/workflows/use_mps.rst:20 -msgid "Now, go to :menuselection:`Planning --> Master Production Schedule` and click on *add a product*. You can now define your safety stock target (= the stock you want to have on hand at the end of the period) and the minimum and maximum quantities that must or can be replenished in each period." +msgid "By considering the impact of confirmed |MOs| and |POs|, along with manually adjusted demand forecasts, the |MPS| can be used to manage long-term product replenishment. This ensures the continued availability of the necessary products and components." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/use_mps.rst:24 +msgid "Since the |MPS| allows for manual intervention, it is useful for replenishing products where the demand of existing sales orders (SOs) does **not** reflect probable future demand." msgstr "" #: ../../content/applications/inventory_and_mrp/manufacturing/workflows/use_mps.rst:28 -msgid "In the MPS view, you can decide which information you would like to display by clicking on *rows*. For instance, the *Actual demand* will show you which quantity of products has already been ordered for the period, or *Available to Promise*, what can still be sold during that same period (what you plan to replenish - what is already sold during the period). You can also decide to hide rows if you like." +msgid "A retail store sells artificial *Christmas trees* during the holiday season. It is currently September, and the store has less than ten Christmas tree |MOs| confirmed for the month of December." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/use_mps.rst:32 +msgid "Despite the number of confirmed |MOs|, the procurement manager knows that the demand for Christmas trees in December is going to be much higher, once the holiday season starts. As a result, they manually enter a greater demand in the |MPS|, so they can properly replenish the product in time for the increase in customer demand." msgstr "" #: ../../content/applications/inventory_and_mrp/manufacturing/workflows/use_mps.rst:38 -msgid "Estimate your demand and launch replenishment" +msgid "It is essential to remember that the |MPS| is a **MANUAL** tool. Adding a product to the |MPS| does not cause it to be manufactured or purchased automatically. The |MPS| simply suggests the amount of the product that should be replenished, but requires user input to create the |MOs| or |POs| that are used to replenish it." msgstr "" -#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/use_mps.rst:40 -msgid "The next step is to estimate the demand for the chosen period. This is done in the *Forecasted Demand* Row. You can easily, at any time, compare the demand forecast with the actual demand (= confirmed sales). The demand forecast for a finished product will impact the indirect demand for its components." +#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/use_mps.rst:43 +msgid "For this reason, it is recommended that the |MPS| **NOT** be used alongside reordering rules for the same product. Because reordering rules are an automated workflow, they conflict with the manual replenishment method of |MPS|. Using both, in unison, can lead to inaccurate forecasts and the creation of unnecessary replenishment orders." msgstr "" -#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/use_mps.rst:48 -msgid "Once the forecasted demand has been set, the quantity to replenish for the different periods will automatically be computed. The replenishments you are supposed to launch based on your lead times (vendor lead time or manufacturing lead time) are then displayed in green. You can now launch the replenishment by clicking on the replenish button." +#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/use_mps.rst:49 +msgid "Enable and configure |MPS|" msgstr "" -#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/use_mps.rst:54 -msgid "Depending on the configuration of the product (buy vs. manufacture), requests for quotations or manufacturing orders will be created. You can easily access those by clicking on the *Actual Replenishment* cell." +#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/use_mps.rst:51 +msgid "To use the |MPS| feature, navigate to :menuselection:`Manufacturing app --> Configuration --> Settings`, and tick the :guilabel:`Master Production Schedule` checkbox in the :guilabel:`Planning` section. Finally, click :guilabel:`Save`." msgstr "" -#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/use_mps.rst:61 -msgid "In case you manually edit the *Suggested Replenishment* quantity, a small cross will appear on the left hand side of the cell. In case you want to go back to the automatically computed value given by Odoo, simply click the cross." +#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/use_mps.rst:55 +msgid "After enabling the :guilabel:`Master Production Schedule` feature, two new fields appear under it on the :guilabel:`Settings` page: :guilabel:`Time Range` and :guilabel:`Number of Columns`." msgstr "" -#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/use_mps.rst:67 -msgid "Cells color signification" +#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/use_mps.rst:58 +msgid "The :guilabel:`Time Range` field is used to select the period of time over which planning takes place, and offers three options: :guilabel:`Monthly`, :guilabel:`Weekly`, and :guilabel:`Daily`. For example, if :guilabel:`Monthly` is selected, the |MPS| plans the production requirements of products and components on a monthly basis." msgstr "" -#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/use_mps.rst:69 -msgid "The cells, which are part of the *Suggested Replenishment* line, can take different colors depending on the situation:" +#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/use_mps.rst:63 +msgid "The :guilabel:`Number of Columns` field is used to specify the quantity of the selected :guilabel:`Time Range` units shown on the |MPS| page. For example, if the :guilabel:`Time Range` field is set to :guilabel:`Monthly`, and `12` is entered in the :guilabel:`Number of Columns` field, the |MPS| shows one column for the next 12 months, starting with the current month." msgstr "" -#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/use_mps.rst:72 -msgid "**Green**: quantity of products which should be replenished to reach the expected safety stock considering the demand forecast and the indirect demand forecast." +#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/use_mps.rst:68 +msgid "If the values of the :guilabel:`Time Range` or :guilabel:`Number of Columns` fields are altered, click :guilabel:`Save` again to save the changes." msgstr "" -#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/use_mps.rst:74 -msgid "**Grey**: replenishment order has already been generated, and its quantity still matches current data." +#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/use_mps.rst:-1 +msgid "The MPS setting in the Manufacturing app's settings." msgstr "" #: ../../content/applications/inventory_and_mrp/manufacturing/workflows/use_mps.rst:76 -msgid "**Red**: replenishment order has already been generated, and its quantity was too high considering current data." +msgid "|MPS| dashboard" msgstr "" #: ../../content/applications/inventory_and_mrp/manufacturing/workflows/use_mps.rst:78 -msgid "**Orange**: replenishment order has already been generated, and its quantity was too low considering current data." +msgid "To open the |MPS|, navigate to :menuselection:`Manufacturing app --> Planning --> Master Production Schedule`. The |MPS| view appears as follows:" msgstr "" -#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/use_mps.rst:80 -msgid "The *Forecasted stock* line can also contain red cells, which means the stock will be negative during the period in question." +#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/use_mps.rst:-1 +msgid "The Master Production Schedule in the Manufacturing app." msgstr "" -#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/use_mps.rst:84 -msgid "What if I have underestimated the demand?" +#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/use_mps.rst:85 +msgid "The grey column on the left side of the screen shows a section for every product added to the |MPS|, with each product section being broken down into smaller rows. The information shown in the rows depends on the filters selected in the :guilabel:`Search...` bar drop-down menu at the top of the page. The default categories that appear in the rows are:" msgstr "" -#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/use_mps.rst:86 -msgid "You can still increase the demand forecast. It will impact the quantity to replenish. The cell will become orange, and you’ll be able to launch a new replenishment." -msgstr "" - -#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/use_mps.rst:91 -msgid "What if I have overestimated the demand?" +#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/use_mps.rst:90 +msgid ":guilabel:`[Product] by [unit]` :icon:`fa-area-chart`: the forecasted stock quantity at the beginning of each time period. :guilabel:`[Product]` and :icon:`fa-area-chart` are selectable buttons which open the product's page, or the forecast report for the product, respectively." msgstr "" #: ../../content/applications/inventory_and_mrp/manufacturing/workflows/use_mps.rst:93 -msgid "You can decrease the demand forecast. The cell will become red to inform you that you’ve ordered more than planned. If you’re still able to do it, you can cancel some RFQ or MO manually." +msgid ":guilabel:`- Forecasted Demand`: the demand forecast, which is entered manually. This represents an estimate of the demand for the product during each time period." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/use_mps.rst:95 +msgid ":guilabel:`- Indirect Demand Forecast`: while this is a default category, it **only** appears for products that are components of other products. It represents the demand for the component from existing MOs." msgstr "" #: ../../content/applications/inventory_and_mrp/manufacturing/workflows/use_mps.rst:98 -msgid "What if I wrongly added a product to the MPS?" +msgid ":guilabel:`+ Suggested Replenishment`: the quantity of the product that is suggested to be replenished through |MOs| or |POs|. To the right of the category title is a :guilabel:`Replenish` button, which is used to manually replenish the product, based on the quantity suggested to be replenished." msgstr "" -#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/use_mps.rst:100 -msgid "You can easily remove a product from the MPS by clicking the small bin on the right of its name." +#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/use_mps.rst:0 +msgid "The Replenish button on the \"+ Suggested Replenishment\" row." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/use_mps.rst:107 +msgid "The \"Replenish\" button on the \"+ Suggested Replenishment\" row." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/use_mps.rst:109 +msgid ":guilabel:`= Forecasted Stock`: the quantity of the product forecasted to be in stock at the end of each time period, assuming that suggested replenishment numbers are fulfilled." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/use_mps.rst:112 +msgid "Altogether, these default categories form an equation:" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/use_mps.rst:114 +msgid "\\text{Forecasted Demand} + \\text{Suggested Replenishment} = \\text{Forecasted Stock}\n" +"\n" +"" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/use_mps.rst:117 +msgid "In the case of components, the :guilabel:`Indirect Demand Forecast` is taken into account as well." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/use_mps.rst:119 +msgid "The :guilabel:`- Forecasted Demand` and :guilabel:`+ Suggested Replenishment` fields can be edited for any of the time periods to the right of the product column. Doing so changes the equation, and updates the value displayed in the :guilabel:`Forecasted Stock` field." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/use_mps.rst:123 +msgid "Changing the value in the :guilabel:`+ Suggested Replenishment` field also makes an :icon:`fa-times` :guilabel:`(reset)` button appear to the left of the field. Click the :icon:`fa-times` :guilabel:`(reset)` button next to the field to reset its value back to the one calculated by the |MPS|." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/use_mps.rst:129 +msgid "While the |MPS| can be used with only the default categories enabled, it is advisable to also enable the :guilabel:`Actual Demand` category. This is done by clicking the :icon:`fa-caret-down` :guilabel:`(down arrow)` on the right side of the :guilabel:`Search...` bar, and enabling the :guilabel:`Actual Demand` option under the :guilabel:`Rows` header." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/use_mps.rst:134 +msgid "With the :guilabel:`Actual Demand` option enabled, the :guilabel:`- Forecasted Demand` category changes to the :guilabel:`- Actual / Forecasted Demand` category. In addition to the manually entered forecasted demand, this category also displays the confirmed demand for the product, which is based on confirmed |SOs|." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/use_mps.rst:139 +msgid "Each column to the right of the products column lists one unit of the time period selected in the *Time Range* field on the *Manufacturing* app *Settings* page (ex. months). The number of time period columns corresponds to the value entered in the *Number of Columns* field." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/use_mps.rst:143 +msgid "The first time period column represents the current time period. For example, if the |MPS| is configured to use months, the first column displays data for the current month. On this first column, the :guilabel:`+ Suggested Replenishment` field appears in one of five colors:" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/use_mps.rst:147 +msgid ":guilabel:`Green`: a replenishment order must be generated to keep stock at the :guilabel:`Safety Stock Target`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/use_mps.rst:149 +msgid ":guilabel:`Gray`: a replenishment order has already been generated to keep stock at the :guilabel:`Safety Stock Target`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/use_mps.rst:151 +msgid ":guilabel:`Yellow`: a replenishment order has already been generated, but the quantity it was created for is not enough to keep stock at the :guilabel:`Safety Stock Target`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/use_mps.rst:153 +msgid ":guilabel:`Red`: a replenishment order has already been generated, but the quantity it was created for puts the amount of stock above the :guilabel:`Safety Stock Target`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/use_mps.rst:156 +msgid "The :guilabel:`+ Suggested Replenishment` field appears white, if no replenishment order has been generated, and it is not necessary to generate one at the current moment." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/use_mps.rst:160 +msgid "Add a product" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/use_mps.rst:162 +msgid "To use |MPS| to manage the replenishment of a product, navigate to :menuselection:`Manufacturing app --> Planning --> Master Production Schedule`. At the top of the |MPS| page, click :guilabel:`Add a Product` to open the :guilabel:`Add a Product` pop-up window." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/use_mps.rst:167 +msgid "Products **must** be properly configured to be replenished through the |MPS|." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/use_mps.rst:169 +msgid "In the case of manufactured products, the *Manufacture* route must be selected in the *Routes* section of the *Inventory* tab, on the product's form." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/use_mps.rst:172 +msgid "In the case of products that are purchased, the *Buy* route must be selected in the *Routes* section of the *Inventory* tab, on the product's form. Additionally, a vendor and the price they sell the product for must also be specified on the *Purchase* tab." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/use_mps.rst:176 +msgid "On the pop-up window, select the product to add in the :guilabel:`Product` drop-down menu. If the product is replenished through manufacturing, select the product's |BoM| in the :guilabel:`Bill of Materials` field." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/use_mps.rst:181 +msgid "Selecting a BoM when adding a product to the |MPS| also adds any components listed on the BoM. If it is not necessary to manage the replenishment of components through the |MPS|, simply leave the :guilabel:`Bill of Materials` field blank." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/use_mps.rst:185 +msgid "If the database is configured with multiple warehouses, a :guilabel:`Production Warehouse` field appears on the :guilabel:`Add a Product` pop-up window. Use this field to specify which warehouse the product is replenished to." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/use_mps.rst:189 +msgid "In the :guilabel:`Safety Stock Target` field, specify the minimum quantity of the product that should be kept available for orders at all times. For example, if there should always be 20 units of the product available for order fulfillment, enter `20` in the :guilabel:`Safety Stock Target` field." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/use_mps.rst:194 +msgid "In the :guilabel:`Minimum to Replenish` field, enter the minimum product quantity for orders created to replenish the product. For example, if `5` is entered in this field, replenishment orders for the product include a minimum of five units." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/use_mps.rst:198 +msgid "In the :guilabel:`Maximum to Replenish` field, enter the maximum product quantity for orders created to replenish the product. For example, if `100` is entered in this field, replenishment orders for the product include a maximum of 100 units." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/use_mps.rst:202 +msgid "Finally, click :guilabel:`Save` to add the product to the |MPS|. The product now appears on the |MPS| page each time it is opened. If a |BoM| was selected in the :guilabel:`Bill of Materials` field of the :guilabel:`Add a Product` pop-up window, any components listed on the |BoM| appear on the page, as well." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/use_mps.rst:-1 +msgid "The Add a Product pop-up window in the MPS." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/use_mps.rst:212 +msgid "Edit a product" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/use_mps.rst:214 +msgid "After adding a product to the |MPS|, it may be necessary to change the replenishment values entered on the :guilabel:`Add a Product` pop-up window. To do so, click the :guilabel:`# ≤…≤ #` button to the immediate right of the :guilabel:`Replenish` button, on the :guilabel:`+ Suggested Replenishment` row, below the product's name." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/use_mps.rst:220 +msgid "The first and second number displayed on the :guilabel:`# ≤…≤ #` button correspond to the values entered in the :guilabel:`Minimum to Replenish` and :guilabel:`Maximum to Replenish` fields when adding the product to the |MPS|." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/use_mps.rst:224 +msgid "For example, if `5` was entered in the :guilabel:`Minimum to Replenish` field, and `100` was entered in the :guilabel:`Maximum to Replenish` field, the button appears as :guilabel:`5 ≤…≤ 100`." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/use_mps.rst:228 +msgid "Clicking the :guilabel:`# ≤…≤ #` button opens the :guilabel:`Edit Production Schedule` pop-up window. This pop-up window is the same as the :guilabel:`Add a Product` pop-up window, except that the :guilabel:`Product` and :guilabel:`Bill of Materials` fields cannot be edited." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/use_mps.rst:232 +msgid "On the :guilabel:`Edit Production Schedule` pop-up window, enter the desired values in the :guilabel:`Safety Stock Target`, :guilabel:`Minimum to Replenish`, and :guilabel:`Maximum to Replenish` fields. Then, click :guilabel:`Save` to save the changes." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/use_mps.rst:237 +msgid "Remove a product" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/use_mps.rst:239 +msgid "To remove a product from the |MPS|, tick the checkbox to the left of its name. Then, click the :icon:`fa-cog` :guilabel:`Actions` button at the top of the screen, and select :guilabel:`Delete` from the resulting drop-down menu. Finally, click :guilabel:`Ok` on the :guilabel:`Confirmation` pop-up window." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/use_mps.rst:244 +msgid "Deleting a product from the |MPS| removes it, along with all of its data. If the product is re-added, its replenishment values must be reconfigured." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/use_mps.rst:248 +msgid "|MPS| replenishment" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/use_mps.rst:250 +msgid "Products in the |MPS| can be replenished in one of three ways:" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/use_mps.rst:252 +msgid "Click the :guilabel:`Replenish` button at the top of the screen to generate replenishment orders for every product below its :guilabel:`Safety Stock Target` for the current month." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/use_mps.rst:254 +msgid "Click the :guilabel:`Replenish` button on the right side of the :guilabel:`+ Suggested Replenishment` row of a specific product, to generate a replenishment order for that specific product." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/use_mps.rst:257 +msgid "Tick the checkbox to the left of the product name of one or more products. Then, click the :icon:`fa-cog` :guilabel:`Actions` button at the top of the screen, and select :guilabel:`Replenish` from the resulting drop-down menu. Doing so generates a replenishment order for each selected product." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/use_mps.rst:262 +msgid "The type of replenishment order generated corresponds to the route selected on the *Inventory* tab of the product's form:" +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/use_mps.rst:265 +msgid "If the *Buy* route is selected, an |RfQ| is generated to replenish the product. |RfQs| can be selected by navigating to the :menuselection:`Purchase` app. Any |RfQ| generated by the |MPS| lists :guilabel:`MPS` in its :guilabel:`Source Document` field." +msgstr "" + +#: ../../content/applications/inventory_and_mrp/manufacturing/workflows/use_mps.rst:268 +msgid "If the *Manufacture* route is selected, an |MO| is generated to replenish the product. |MOs| can be selected by navigating to :menuselection:`Manufacturing app --> Operations --> Manufacturing Orders`. Any |MO| generated by the |MPS| lists :guilabel:`MPS` in its :guilabel:`Source Document` field." msgstr "" #: ../../content/applications/inventory_and_mrp/manufacturing/workflows/work_center_time_off.rst:3 @@ -22321,10 +23364,6 @@ msgstr "" msgid "Set a product's units of measure using your own units in Odoo Purchase" msgstr "" -#: ../../content/applications/inventory_and_mrp/quality.rst:7 -msgid "Quality" -msgstr "" - #: ../../content/applications/inventory_and_mrp/quality.rst:9 msgid "**Odoo Quality** helps ensure product quality throughout manufacturing processes and inventory movements. Conduct quality checks, automate quality inspection frequency, and create quality alerts when issues arise." msgstr "" diff --git a/locale/sources/marketing.pot b/locale/sources/marketing.pot index c7cff8f52..093c16300 100644 --- a/locale/sources/marketing.pot +++ b/locale/sources/marketing.pot @@ -8,7 +8,7 @@ msgid "" msgstr "" "Project-Id-Version: Odoo 17.0\n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2024-06-24 07:08+0000\n" +"POT-Creation-Date: 2024-07-23 13:30+0000\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME \n" "Language-Team: LANGUAGE \n" @@ -355,7 +355,7 @@ msgid "When all desired options are configured, click :guilabel:`Save` to save t msgstr "" #: ../../content/applications/marketing/email_marketing.rst:274 -#: ../../content/applications/marketing/events.rst:79 +#: ../../content/applications/marketing/events.rst:89 msgid "Settings" msgstr "" @@ -2016,15 +2016,15 @@ msgstr "" msgid "`Odoo Tutorials: Events `_" msgstr "" -#: ../../content/applications/marketing/events.rst:37 +#: ../../content/applications/marketing/events.rst:47 msgid "Events dashboard" msgstr "" -#: ../../content/applications/marketing/events.rst:39 +#: ../../content/applications/marketing/events.rst:49 msgid "When the *Events* application is opened, Odoo reveals the main :guilabel:`Events` dashboard, which can be viewed in a number of different ways. Those different view options are accessible from the :guilabel:`Events` dashboard in the upper-right corner, via a series of view-related icon buttons." msgstr "" -#: ../../content/applications/marketing/events.rst:43 +#: ../../content/applications/marketing/events.rst:53 msgid "By default, the :guilabel:`Events` dashboard is displayed in the :icon:`oi-view-kanban` :guilabel:`Kanban` view, which is populated with a variety of pipeline stages." msgstr "" @@ -2032,19 +2032,19 @@ msgstr "" msgid "Overview of events setting with the kanban view in Odoo Events." msgstr "" -#: ../../content/applications/marketing/events.rst:50 +#: ../../content/applications/marketing/events.rst:60 msgid "This view showcases all the events in the database in their respective stages. By default, the stages are: :guilabel:`New`, :guilabel:`Booked`, :guilabel:`Announced`, :guilabel:`Ended`, and :guilabel:`Cancelled`." msgstr "" -#: ../../content/applications/marketing/events.rst:55 +#: ../../content/applications/marketing/events.rst:65 msgid "The :guilabel:`Ended` and :guilabel:`Cancelled` stages are folded, by default, and located to the right of the other stages." msgstr "" -#: ../../content/applications/marketing/events.rst:58 +#: ../../content/applications/marketing/events.rst:68 msgid "On each event card, find the scheduled date of the event, the name of the event, the location, the number of expected :guilabel:`Attendees`, any scheduled activities related to the event, the status of the event, and the person responsible for the event." msgstr "" -#: ../../content/applications/marketing/events.rst:62 +#: ../../content/applications/marketing/events.rst:72 msgid "To quickly add a new event to a pipeline, click the :icon:`fa-plus` :guilabel:`(plus)` icon at the top of the stage to which the event should be added to reveal a blank Kanban card to fill out." msgstr "" @@ -2052,27 +2052,27 @@ msgstr "" msgid "Typical blank kanban card to fill out in the Odoo Events application." msgstr "" -#: ../../content/applications/marketing/events.rst:69 +#: ../../content/applications/marketing/events.rst:79 msgid "In this blank Kanban card, enter the name of :guilabel:`Event`, along with the start and end :guilabel:`Date` and time." msgstr "" -#: ../../content/applications/marketing/events.rst:72 +#: ../../content/applications/marketing/events.rst:82 msgid "Then, either click :guilabel:`Add` to add it to the stage and edit it later, or click :guilabel:`Edit` to add the event to stage and edit its configurations on a separate page." msgstr "" -#: ../../content/applications/marketing/events.rst:75 +#: ../../content/applications/marketing/events.rst:85 msgid "Each event card can be dragged-and-dropped into any stage on the Kanban pipeline, providing easy organizational access." msgstr "" -#: ../../content/applications/marketing/events.rst:81 +#: ../../content/applications/marketing/events.rst:91 msgid "To access the event settings and feature options in Odoo *Events*, navigate to :menuselection:`Events app --> Configuration --> Settings`. From here, tick the checkboxes beside the desired settings and/or features, and click :guilabel:`Save` to activate them." msgstr "" -#: ../../content/applications/marketing/events.rst:86 +#: ../../content/applications/marketing/events.rst:96 msgid "Events section" msgstr "" -#: ../../content/applications/marketing/events.rst:88 +#: ../../content/applications/marketing/events.rst:98 msgid "In the :guilabel:`Events` section of the :guilabel:`Settings` page, there are selectable features that can be enabled to add various elements to events created with the Odoo *Events* application." msgstr "" @@ -2080,43 +2080,43 @@ msgstr "" msgid "The Events section on the Odoo Events settings page in the Odoo Events application." msgstr "" -#: ../../content/applications/marketing/events.rst:95 +#: ../../content/applications/marketing/events.rst:105 msgid "The :guilabel:`Schedule & Tracks` feature allows users to manage and publish a schedule with tracks for events. *Tracks* is a catch-all term that refers to talks, lectures, demonstrations, presentations, and other similar elements that users may choose to include as part of an event." msgstr "" -#: ../../content/applications/marketing/events.rst:99 +#: ../../content/applications/marketing/events.rst:109 msgid "When the :guilabel:`Schedule & Tracks` feature is enabled, two additional fields appear beneath it: :guilabel:`Live Broadcast` and :guilabel:`Event Gamification`." msgstr "" -#: ../../content/applications/marketing/events.rst:102 +#: ../../content/applications/marketing/events.rst:112 msgid "The :guilabel:`Live Broadcast` feature lets users air tracks online, via a *YouTube* integration." msgstr "" -#: ../../content/applications/marketing/events.rst:104 +#: ../../content/applications/marketing/events.rst:114 msgid "The :guilabel:`Event Gamification` feature lets users share a quiz after any event track, in order for attendees to gauge how much they learned from the track they just saw/heard. Companies can also benefit from this feature, in that the subsequent responses and results of the quizzes can help determine where a company's strengths and weaknesses are, when it comes to their presentations." msgstr "" -#: ../../content/applications/marketing/events.rst:109 +#: ../../content/applications/marketing/events.rst:119 msgid "Next, is the :guilabel:`Online Exhibitors` feature. This feature allows users to display sponsors and exhibitors on event pages, which can serve as a valuable incentive to encourage partners and businesses to participate in the event." msgstr "" -#: ../../content/applications/marketing/events.rst:113 +#: ../../content/applications/marketing/events.rst:123 msgid "The :guilabel:`Jitsi Server Domain` field represents an external conferencing service that is integrated with Odoo. It is what is used to create and host virtual conferences, community rooms, and other similar elements for events." msgstr "" -#: ../../content/applications/marketing/events.rst:117 +#: ../../content/applications/marketing/events.rst:127 msgid "The :guilabel:`Community Chat Rooms` feature allows users to create virtual conference rooms for event attendees, providing them with a centralized place to meet and discuss anything related to the event." msgstr "" -#: ../../content/applications/marketing/events.rst:121 +#: ../../content/applications/marketing/events.rst:131 msgid "Lastly, there is the :guilabel:`Booth Management` feature. This feature provides users with the ability to create and manage event booths and booth reservations. When enabled, users can create different booth tiers, with individual price points, and sell them to interested parties." msgstr "" -#: ../../content/applications/marketing/events.rst:126 +#: ../../content/applications/marketing/events.rst:136 msgid "Registration section" msgstr "" -#: ../../content/applications/marketing/events.rst:128 +#: ../../content/applications/marketing/events.rst:138 msgid "The :guilabel:`Registration` section of the :guilabel:`Settings` page provides selectable settings that are directly related to event registration." msgstr "" @@ -2124,19 +2124,19 @@ msgstr "" msgid "The Registration section in the Odoo Events settings page in the Odoo Events application." msgstr "" -#: ../../content/applications/marketing/events.rst:135 +#: ../../content/applications/marketing/events.rst:145 msgid "The :guilabel:`Tickets` setting allows users to sell event tickets, via standard sales orders." msgstr "" -#: ../../content/applications/marketing/events.rst:137 +#: ../../content/applications/marketing/events.rst:147 msgid "The :guilabel:`Online Ticketing` setting creates a selectable *Event Ticket* product type on product forms, which provides users with the ability to sell event tickets online, via their website/eCommerce store." msgstr "" -#: ../../content/applications/marketing/events.rst:142 +#: ../../content/applications/marketing/events.rst:152 msgid "Attendance section" msgstr "" -#: ../../content/applications/marketing/events.rst:144 +#: ../../content/applications/marketing/events.rst:154 msgid "In the :guilabel:`Attendance` section of the :guilabel:`Settings` page, there is a selectable setting that is directly related to how attendees can attend/enter the event." msgstr "" @@ -2144,67 +2144,66 @@ msgstr "" msgid "The Attendance section in the Odoo Events Settings page in the Odoo Events application." msgstr "" -#: ../../content/applications/marketing/events.rst:151 +#: ../../content/applications/marketing/events.rst:161 msgid "The :guilabel:`Use Event Barcode` setting, when activated, enables barcode (and QR code) scanning for attendees to enter the event. This provides attendees with quick access, and helps Odoo users easily track, manage, and analyze all event attendees." msgstr "" -#: ../../content/applications/marketing/events.rst:155 +#: ../../content/applications/marketing/events.rst:165 msgid "The :guilabel:`Barcode Nomenclature` field, beneath the :guilabel:`Use Event Barcode` setting, is set to :guilabel:`Default Nomenclature`, by default, but can be changed at any time." msgstr "" -#: ../../content/applications/marketing/events.rst:159 +#: ../../content/applications/marketing/events.rst:169 #: ../../content/applications/marketing/events/create_events.rst:3 msgid "Create events" msgstr "" -#: ../../content/applications/marketing/events.rst:161 +#: ../../content/applications/marketing/events.rst:171 msgid "With Odoo *Events*, events can be manually created from scratch or built off of pre-made templates. Once launched, the *Events* application then integrates with the *Website* app for the front-end promotion and registration of the event for attendees, the *Sales* app for the purchasing ability of paid tickets, and the *CRM* application through customizable lead generation rules." msgstr "" -#: ../../content/applications/marketing/events.rst:167 +#: ../../content/applications/marketing/events.rst:177 msgid ":doc:`events/create_events`" msgstr "" -#: ../../content/applications/marketing/events.rst:170 +#: ../../content/applications/marketing/events.rst:180 #: ../../content/applications/marketing/events/sell_tickets.rst:3 msgid "Sell event tickets" msgstr "" -#: ../../content/applications/marketing/events.rst:172 +#: ../../content/applications/marketing/events.rst:182 msgid "Create custom ticket tiers (with various price points) for potential event attendees to choose from, directly on the event template form, under the *Tickets* tab." msgstr "" -#: ../../content/applications/marketing/events.rst:175 +#: ../../content/applications/marketing/events.rst:185 msgid "Odoo simplifies the ticket-purchasing process by providing plenty of payment method options, as well." msgstr "" -#: ../../content/applications/marketing/events.rst:179 +#: ../../content/applications/marketing/events.rst:189 msgid ":doc:`events/sell_tickets`" msgstr "" -#: ../../content/applications/marketing/events.rst:182 -#: ../../content/applications/marketing/events/track_manage_talks.rst:3 +#: ../../content/applications/marketing/events.rst:192 msgid "Track and manage talks" msgstr "" -#: ../../content/applications/marketing/events.rst:184 +#: ../../content/applications/marketing/events.rst:194 msgid "Discover how to access various event tracks (talks, presentations, etc.), view entire agendas, and learn how attendees can propose talks for the event." msgstr "" -#: ../../content/applications/marketing/events.rst:188 +#: ../../content/applications/marketing/events.rst:198 msgid ":doc:`events/track_manage_talks`" msgstr "" -#: ../../content/applications/marketing/events.rst:191 +#: ../../content/applications/marketing/events.rst:201 #: ../../content/applications/marketing/events/event_templates.rst:3 msgid "Event templates" msgstr "" -#: ../../content/applications/marketing/events.rst:193 +#: ../../content/applications/marketing/events.rst:203 msgid "Discover the process to customize and configure event templates, which can be used to expedite the event-creation process." msgstr "" -#: ../../content/applications/marketing/events.rst:197 +#: ../../content/applications/marketing/events.rst:207 msgid ":doc:`events/event_templates`" msgstr "" @@ -2727,9 +2726,324 @@ msgid "Sending emails from Odoo is subject to a daily limit, which, by default, msgstr "" #: ../../content/applications/marketing/events/create_events.rst:431 +#: ../../content/applications/marketing/events/event_tracks.rst:310 msgid ":doc:`track_manage_talks`" msgstr "" +#: ../../content/applications/marketing/events/event_booths.rst:3 +msgid "Event booths" +msgstr "" + +#: ../../content/applications/marketing/events/event_booths.rst:5 +msgid "The Odoo *Events* application provides users with the ability to create event booths, sell their availability, and manage their reservations." +msgstr "" + +#: ../../content/applications/marketing/events/event_booths.rst:9 +#: ../../content/applications/marketing/events/event_tracks.rst:12 +#: ../../content/applications/marketing/events/sell_tickets.rst:18 +#: ../../content/applications/marketing/marketing_automation.rst:44 +msgid "Configuration" +msgstr "" + +#: ../../content/applications/marketing/events/event_booths.rst:11 +msgid "In order to create, sell, and manage booths for events, the *Booth Management* feature must be activated." +msgstr "" + +#: ../../content/applications/marketing/events/event_booths.rst:14 +msgid "To do that, navigate to :menuselection:`Events app --> Configuration --> Settings`, and tick the :guilabel:`Booth Management` checkbox. Then, click :guilabel:`Save`." +msgstr "" + +#: ../../content/applications/marketing/events/event_booths.rst:-1 +msgid "The Booth Management setting in the Odoo Events application." +msgstr "" + +#: ../../content/applications/marketing/events/event_booths.rst:22 +msgid "When the :guilabel:`Booth Management` setting is activated, a new :doc:`Product Type <../../inventory_and_mrp/inventory/product_management/product_tracking/type>` becomes available on all product forms: *Event Booth*." +msgstr "" + +#: ../../content/applications/marketing/events/event_booths.rst:26 +msgid "This is important because every created booth **must** be assigned a *Booth Category* on their respective booth form, and every booth category **must** have an *Event Booth* product assigned to it." +msgstr "" + +#: ../../content/applications/marketing/events/event_booths.rst:31 +msgid "Booth categories" +msgstr "" + +#: ../../content/applications/marketing/events/event_booths.rst:33 +msgid "With the *Booth Management* setting activated in the *Events* app, the *Booth Categories* option appears in the :guilabel:`Configuration` menu." +msgstr "" + +#: ../../content/applications/marketing/events/event_booths.rst:36 +msgid "To access the :guilabel:`Booth Category` dashboard, go to :menuselection:`Events app --> Configuration --> Booth Categories`, which reveals a list of all created booth categories." +msgstr "" + +#: ../../content/applications/marketing/events/event_booths.rst:-1 +msgid "The Booth Category page in the Odoo Events application." +msgstr "" + +#: ../../content/applications/marketing/events/event_booths.rst:43 +msgid "On the :guilabel:`Booth Category` page, the following information for each booth category is listed:" +msgstr "" + +#: ../../content/applications/marketing/events/event_booths.rst:45 +msgid ":guilabel:`Name`: the name of the booth category." +msgstr "" + +#: ../../content/applications/marketing/events/event_booths.rst:46 +msgid ":guilabel:`Create Sponsor`: if checked, booking this booth category creates a sponsor for the user." +msgstr "" + +#: ../../content/applications/marketing/events/event_booths.rst:48 +msgid ":guilabel:`Product`: the *Event Booth* product associated with that specific booth category." +msgstr "" + +#: ../../content/applications/marketing/events/event_booths.rst:49 +msgid ":guilabel:`Price`: the price of a booth in that booth category." +msgstr "" + +#: ../../content/applications/marketing/events/event_booths.rst:51 +msgid "When the :icon:`oi-settings-adjust` :guilabel:`(settings)` icon, located to the far-right of the column titles, is clicked, a drop-down menu of additional column options appears. From the resulting drop-down menu, tick the checkbox beside :guilabel:`Sponsor Level` and/or :guilabel:`Sponsor Type` to reveal those columns on the :guilabel:`Booth Category` page." +msgstr "" + +#: ../../content/applications/marketing/events/event_booths.rst:56 +msgid "To edit an existing booth category, select it from the list, and proceed to make any desired modifications from the event category form." +msgstr "" + +#: ../../content/applications/marketing/events/event_booths.rst:60 +msgid "Create booth category" +msgstr "" + +#: ../../content/applications/marketing/events/event_booths.rst:62 +msgid "To create a booth category from the :guilabel:`Booth Category` page, click the :guilabel:`New` button in the upper-left corner to reveal a blank booth category form." +msgstr "" + +#: ../../content/applications/marketing/events/event_booths.rst:-1 +msgid "A typical booth category form in the Odoo Events application." +msgstr "" + +#: ../../content/applications/marketing/events/event_booths.rst:69 +msgid "Start by entering a name for the booth category in the top :guilabel:`Booth Category` field. This is a **requried** field." +msgstr "" + +#: ../../content/applications/marketing/events/event_booths.rst:72 +msgid "To add a corresponding image to the booth category (e.g. a sample photo of how the booth looks), click the :icon:`fa-pencil` :guilabel:`(pencil)` icon that appears when the cursor hovers over the camera placeholder in the upper-right corner of the booth category form. When clicked, proceed to upload the desired image to the booth category form, if needed." +msgstr "" + +#: ../../content/applications/marketing/events/event_booths.rst:77 +msgid "In the :guilabel:`Booth Details` section, users **must** assign a :guilabel:`Product` to the category, and it **must** have *Event Booth* set as the *Product Type* on the product form." +msgstr "" + +#: ../../content/applications/marketing/events/event_booths.rst:80 +msgid "And, regardless of the listed price on the *Event Booth* product chosen, the user can input a custom :guilabel:`Price` to be applied for this booth category in the field below." +msgstr "" + +#: ../../content/applications/marketing/events/event_booths.rst:83 +msgid "In the :guilabel:`Sponsorship` section, there is a :guilabel:`Create Sponsor` checkbox option. With that checkbox ticked, whenever a booth belonging to this category is booked, the user is created as an official *Sponsor* of the event." +msgstr "" + +#: ../../content/applications/marketing/events/event_booths.rst:87 +msgid "When the :guilabel:`Create Sponsor` checkbox is ticked, two additional fields appear beneath it: :guilabel:`Sponsor Level` and :guilabel:`Sponsor Type`." +msgstr "" + +#: ../../content/applications/marketing/events/event_booths.rst:91 +msgid ":guilabel:`Sponsor Level` and :guilabel:`Sponsor Type` are purely to distinguish different distinctions of sponsors. For example, if a sponsor has been attached to a company for multiple years, they would be granted a higher level (e.g. *Gold* level), which provides them with immediate credability and status. Whereas, conversely, a relatively new sponsor would be granted a lower level (e.g. *Bronze* level), which coincides with its own credability and status." +msgstr "" + +#: ../../content/applications/marketing/events/event_booths.rst:97 +msgid "Select a desired level of sponsorship from the :guilabel:`Sponsor Level` drop-down field." +msgstr "" + +#: ../../content/applications/marketing/events/event_booths.rst:100 +msgid "To modify any existing :guilabel:`Sponsor Level`, select it from the drop-down field, then click the :icon:`fa-arrow-right` :guilabel:`(right arrow)` that appears at the end of the line. Doing so opens a separate page, wherein the :guilabel:`Sponsor Level` name and :guilabel:`Ribbon Style` can be changed, if necessary." +msgstr "" + +#: ../../content/applications/marketing/events/event_booths.rst:105 +msgid "Users can also create a new :guilabel:`Sponsor Level`, by typing in the name of the new level, and clicking :guilabel:`Create and edit...` from the resulting drop-down menu." +msgstr "" + +#: ../../content/applications/marketing/events/event_booths.rst:109 +msgid "Clicking :guilabel:`Create` from the resulting drop-down menu in this instance creates the sponsor level, but doesn't immediately prompt the user to further configure it, via a :guilabel:`Create Sponsor Level` pop-up window." +msgstr "" + +#: ../../content/applications/marketing/events/event_booths.rst:113 +msgid "Doing so reveals a :guilabel:`Create Sponsor Level` pop-up window." +msgstr "" + +#: ../../content/applications/marketing/events/event_booths.rst:-1 +msgid "The Create Sponsor Level pop-up window that appears in the Odoo Events application." +msgstr "" + +#: ../../content/applications/marketing/events/event_booths.rst:119 +msgid "From this pop-up window, confirm the newly-created :guilabel:`Sponsor Level`, and decide what kind of :guilabel:`Ribbon Style` should be applied, if any. The :guilabel:`Ribbon Style` options available in that drop-down field are: :guilabel:`No Ribbon`, :guilabel:`Gold`, :guilabel:`Silver`, and :guilabel:`Bronze`." +msgstr "" + +#: ../../content/applications/marketing/events/event_booths.rst:124 +msgid "If one is selected, that :guilabel:`Ribbon Style` appears with the sponsor's name on the event website." +msgstr "" + +#: ../../content/applications/marketing/events/event_booths.rst:127 +msgid "On the booth category form, beneath those sections (:guilabel:`Booth Details` and :guilabel:`Sponsorship`), there is the :guilabel:`Description` tab. In this tab, proceed to enter any vital information related to the booth category that would be important for any potential booth-buyer to know about (e.g., the square footage, any amenities, size of display screen, etc.)." +msgstr "" + +#: ../../content/applications/marketing/events/event_booths.rst:133 +msgid "Add booth to an event" +msgstr "" + +#: ../../content/applications/marketing/events/event_booths.rst:135 +msgid "In order to add a booth to an event, navigate to an existing event form, via :menuselection:`Events app --> Events`, and select the desired event from the :guilabel:`Events` dashboard. Or, click :guilabel:`New` to open a blank event form." +msgstr "" + +#: ../../content/applications/marketing/events/event_booths.rst:139 +msgid "From the event form, to access the *Booths* for that specific event, click the :guilabel:`Booths` smart button at the top of the page." +msgstr "" + +#: ../../content/applications/marketing/events/event_booths.rst:142 +msgid "The :guilabel:`Booths` page is displayed in a Kanban view, by default, with two different stages: :guilabel:`Available` and :guilabel:`Unavailable`." +msgstr "" + +#: ../../content/applications/marketing/events/event_booths.rst:146 +msgid "The :guilabel:`Booths` page of an event is also viewable in a :icon:`oi-view-list` :guilabel:`List` view, :icon:`fa-area-chart` :guilabel:`Graph` view, and :icon:`oi-view-pivot` :guilabel:`Pivot` view. All of which are accessible, via their icons, in the upper-right corner of the :guilabel:`Booths` page." +msgstr "" + +#: ../../content/applications/marketing/events/event_booths.rst:151 +msgid "The booths present in the :guilabel:`Available` stage are still available for people to purchase for the event. The booths present in the :guilabel:`Unavailable` stage have already been purchased, and are no longer available." +msgstr "" + +#: ../../content/applications/marketing/events/event_booths.rst:155 +msgid "To modify any existing booth, simply click the desired booth from the :guilabel:`Booths` page, and proceed to make any necessary changes from the booth form. Or, create a new one, by clicking the :guilabel:`New` button in the upper-left corner to reveal a blank booth form." +msgstr "" + +#: ../../content/applications/marketing/events/event_booths.rst:160 +msgid "Booth form" +msgstr "" + +#: ../../content/applications/marketing/events/event_booths.rst:162 +msgid "The booth form in Odoo *Events* lets users customize and configure event booths in a number of different ways." +msgstr "" + +#: ../../content/applications/marketing/events/event_booths.rst:-1 +msgid "Typical booth form in the Odoo Events application." +msgstr "" + +#: ../../content/applications/marketing/events/event_booths.rst:169 +msgid "Start by typing in a :guilabel:`Name` for the booth. This is a **required** field." +msgstr "" + +#: ../../content/applications/marketing/events/event_booths.rst:171 +msgid "Then, apply a :guilabel:`Booth Category` to the booth. This is a **required** field." +msgstr "" + +#: ../../content/applications/marketing/events/event_booths.rst:174 +msgid "A new :guilabel:`Booth Category` can be created from this field, by typing in the name of the new category, and clicking :guilabel:`Create and edit...` from the resulting drop-down menu. Doing so reveals a :guilabel:`Create Booth Category` pop-up window, with all the standard fields found on a common booth category form." +msgstr "" + +#: ../../content/applications/marketing/events/event_booths.rst:179 +msgid "Simply clicking :guilabel:`Create` from the resulting drop-down menu creates the category, but does not reveal the :guilabel:`Create Booth Category` pop-up window. The category would have to be modified later, via the *Booth Categories* page (:menuselection:`Events app --> Configuration --> Booth Categories`)." +msgstr "" + +#: ../../content/applications/marketing/events/event_booths.rst:184 +msgid "Upon selecting a pre-existing :guilabel:`Booth Category`, two additional, non-modifiable fields appear: :guilabel:`Product` and :guilabel:`Price`. Both fields represent their respective selections for that specific booth category." +msgstr "" + +#: ../../content/applications/marketing/events/event_booths.rst:188 +msgid "When a person purchases a booth rental through the event website, the subsequent renter-related fields on the form auto-populate, based on the information provided by the purchaser during the online transaction. The booth also automatically changes its status from *Available* to *Unavailable*." +msgstr "" + +#: ../../content/applications/marketing/events/event_booths.rst:193 +msgid "However, if the rental of a booth is conducted in any other way (e.g., in person, via sales order, etc.), the :guilabel:`Renter`, :guilabel:`Renter Name`, :guilabel:`Renter Email`, and :guilabel:`Renter Phone` fields can be entered in manually." +msgstr "" + +#: ../../content/applications/marketing/events/event_booths.rst:197 +msgid "The status of the booth (:guilabel:`Available` or :guilabel:`Unavailable`) can also be changed manually, either by clicking the appropriate status from the status bar present on the booth form, or by dragging-and-dropping the desired booth into the appropriate stage, via the *Booths* page Kanban view." +msgstr "" + +#: ../../content/applications/marketing/events/event_booths.rst:203 +msgid "Sell event booths" +msgstr "" + +#: ../../content/applications/marketing/events/event_booths.rst:205 +msgid "With event booths configured on the event form, via the event-specific *Booths* pages, Odoo presents them on the event website, via the *Get A Booth* event subheader link." +msgstr "" + +#: ../../content/applications/marketing/events/event_booths.rst:208 +msgid "To access the *Get A Booth* page on the event website, open the :menuselection:`Events app`, and select the desired event from the :guilabel:`Events` dashboard. From the event form, click the :guilabel:`Go to Website` smart button to be taken to the Odoo-built event website." +msgstr "" + +#: ../../content/applications/marketing/events/event_booths.rst:212 +msgid "If the event subheader menu (with the :guilabel:`Get A Booth` option) is *not* showing up on the event website, there are two ways to make it appear." +msgstr "" + +#: ../../content/applications/marketing/events/event_booths.rst:215 +msgid "While on the event website, enter the edit mode by clicking the :guilabel:`Edit` button in the upper-right corner. Then, click into the :guilabel:`Customize` tab of the resulting sidebar of web design tools." +msgstr "" + +#: ../../content/applications/marketing/events/event_booths.rst:219 +msgid "In the :guilabel:`Customize` tab, click the toggle switch for :guilabel:`Sub-Menu (Specific)`, and click :guilabel:`Save`. Doing so reveals the event subheader menu with various options." +msgstr "" + +#: ../../content/applications/marketing/events/event_booths.rst:222 +msgid "Alternatively, enter :doc:`Debug mode <../../general/developer_mode>`, and open the specific event form in the the *Events* application." +msgstr "" + +#: ../../content/applications/marketing/events/event_booths.rst:225 +msgid "On the event form, with *Debug mode* on, an array of subheader menu options appears. Tick the checkbox for :guilabel:`Website Submenu`, in order for the submenu to appear on the event website. Doing so also ticks every other submenu-related checkbox automatically." +msgstr "" + +#: ../../content/applications/marketing/events/event_booths.rst:229 +msgid "At this point, proceed to choose which options to keep on the event subheader menu. In this case, make sure the :guilabel:`Booth Register` checkbox is ticked." +msgstr "" + +#: ../../content/applications/marketing/events/event_booths.rst:232 +msgid "From there, click the :guilabel:`Get A Booth` event subheader menu option. Doing so reveals the :guilabel:`Get A Booth` page, showcasing all the configured event booths that were created on the event form." +msgstr "" + +#: ../../content/applications/marketing/events/event_booths.rst:-1 +msgid "Typical Get A Booth page on the event website via the Odoo Events app." +msgstr "" + +#: ../../content/applications/marketing/events/event_booths.rst:240 +msgid "From here, the visitor can select their desired booth option, then :guilabel:`Location`. Next, they would click the :guilabel:`Book my Booth(s)` button, located at the bottom of the :guilabel:`Get A Booth` page." +msgstr "" + +#: ../../content/applications/marketing/events/event_booths.rst:244 +msgid "Doing so reveals a :guilabel:`Contact Details` page, wherein they fill out either *Contact Details* or *Sponsor Details*, depending on how the booth was configured on the event form. The fields present on this form vary, depending on whether its meant for a basic contact or an event sponsor." +msgstr "" + +#: ../../content/applications/marketing/events/event_booths.rst:249 +msgid "If the selected booth has the *Create Sponsor* checkbox ticked, this page reads as *Sponsor Details*." +msgstr "" + +#: ../../content/applications/marketing/events/event_booths.rst:252 +msgid "The information provided on this details page is used to auto-populate the renter-related information on the booth form on the event form in the *Events* application." +msgstr "" + +#: ../../content/applications/marketing/events/event_booths.rst:255 +msgid "Once the necessary information has been entered, the visitor then clicks the :guilabel:`Go to Payment` at the bottom of the page, and proceeds to complete the typical checkout process." +msgstr "" + +#: ../../content/applications/marketing/events/event_booths.rst:258 +msgid "Upon a successful payment confirmation, that selected booth automatically moves to the *Unavailable* stage on the event-specific *Booths* page in the *Events* application (accessible via the *Booths* smart button on the event form)." +msgstr "" + +#: ../../content/applications/marketing/events/event_booths.rst:262 +msgid "Also, the provided *Sponsor* information (if applicable) and *Sales Order* information are accessible from the specific event form, via their respective smart buttons that appear at the top of the form." +msgstr "" + +#: ../../content/applications/marketing/events/event_booths.rst:267 +msgid "Click the *Sponsors* smart button to modify any information about the sponsor, if necessary." +msgstr "" + +#: ../../content/applications/marketing/events/event_booths.rst:270 +#: ../../content/applications/marketing/events/event_templates.rst:217 +#: ../../content/applications/marketing/events/event_tracks.rst:309 +#: ../../content/applications/marketing/events/sell_tickets.rst:143 +msgid ":doc:`create_events`" +msgstr "" + +#: ../../content/applications/marketing/events/event_booths.rst:271 +msgid ":doc:`sell_tickets`" +msgstr "" + #: ../../content/applications/marketing/events/event_templates.rst:5 msgid "The Odoo *Events* application provides the ability to customize and configure event templates, which can be used to expedite the event-creation process." msgstr "" @@ -2982,9 +3296,347 @@ msgstr "" msgid "Any of these pre-configured settings related to the selected event template chosen in the :guilabel:`Template` field on an event form can be modified, as desired." msgstr "" -#: ../../content/applications/marketing/events/event_templates.rst:217 -#: ../../content/applications/marketing/events/sell_tickets.rst:143 -msgid ":doc:`create_events`" +#: ../../content/applications/marketing/events/event_tracks.rst:3 +msgid "Event tracks" +msgstr "" + +#: ../../content/applications/marketing/events/event_tracks.rst:5 +msgid "Odoo *Events* provides the ability to create, schedule, and manage talks, lectures, demonstrations, presentations, etc., which known as *Tracks* in Odoo." +msgstr "" + +#: ../../content/applications/marketing/events/event_tracks.rst:8 +msgid "The Odoo *Events* application also has an option to allow event attendees to propose talks (tracks) for an event, which can then be approved (or disapproved)." +msgstr "" + +#: ../../content/applications/marketing/events/event_tracks.rst:14 +msgid "First, there are some settings that need to be enabled, in order to get the most out of event tracks." +msgstr "" + +#: ../../content/applications/marketing/events/event_tracks.rst:17 +msgid "To do that, navigate to :menuselection:`Events app --> Configuration --> Settings`, and tick the checkbox beside the :guilabel:`Schedule & Tracks` setting. Doing so provides the ability to manage and publish an event schedule with various tracks." +msgstr "" + +#: ../../content/applications/marketing/events/event_tracks.rst:21 +msgid "Also, when that setting checkbox is ticked, two additional setting options appear beneath it: :guilabel:`Live Broadcast` and :guilabel:`Event Gamification`." +msgstr "" + +#: ../../content/applications/marketing/events/event_tracks.rst:-1 +msgid "The Schedule and Tracks setting in the Odoo Events app, along with corresponding options." +msgstr "" + +#: ../../content/applications/marketing/events/event_tracks.rst:28 +msgid "The :guilabel:`Live Broadcast` option provides the ability to air tracks online through a *YouTube* integration." +msgstr "" + +#: ../../content/applications/marketing/events/event_tracks.rst:31 +msgid "The :guilabel:`Event Gamification` options provides the ability to share a quiz with track attendees once the track is over, in order to test how much they learned." +msgstr "" + +#: ../../content/applications/marketing/events/event_tracks.rst:35 +msgid "With the :guilabel:`Event Gamification` setting enabled, an :guilabel:`Add Quiz` button appears on track forms, providing the ability to :ref:`quickly create a quiz ` specific to the topic related to that particular track." +msgstr "" + +#: ../../content/applications/marketing/events/event_tracks.rst:39 +msgid "Once all desired settings have been enabled, be sure to click the :guilabel:`Save` button in the upper-left corner of the :guilabel:`Settings` page." +msgstr "" + +#: ../../content/applications/marketing/events/event_tracks.rst:43 +msgid "Event Tracks page" +msgstr "" + +#: ../../content/applications/marketing/events/event_tracks.rst:45 +msgid "To access, modify, and/or create tracks for an event, first navigate to a preconfigured event, or :doc:`create a new one ` from the *Events* application." +msgstr "" + +#: ../../content/applications/marketing/events/event_tracks.rst:48 +msgid "To do that, navigate to :menuselection:`Events app`, and either select a pre-existing event from the :guilabel:`Events` dashboard, or create a new one by clicking :guilabel:`New`." +msgstr "" + +#: ../../content/applications/marketing/events/event_tracks.rst:51 +msgid "Once on the desired event form, click into the :guilabel:`Tracks` smart button at the top of the form." +msgstr "" + +#: ../../content/applications/marketing/events/event_tracks.rst:55 +msgid "If the :guilabel:`Tracks` smart button is not readily available, click the :guilabel:`More` :icon:`fa-sort-desc` drop-down menu to reveal hidden smart buttons. Then, click :guilabel:`Tracks` from the resulting drop-down menu." +msgstr "" + +#: ../../content/applications/marketing/events/event_tracks.rst:59 +msgid "Clicking the :guilabel:`Tracks` smart button reveals the :guilabel:`Event Tracks` page for that particular event, which presents all the tracks (both scheduled and proposed) for the event, if there are any." +msgstr "" + +#: ../../content/applications/marketing/events/event_tracks.rst:-1 +msgid "Typical event tracks page for an event in the Odoo Events application." +msgstr "" + +#: ../../content/applications/marketing/events/event_tracks.rst:67 +msgid "The tracks are presented in a default :icon:`oi-view-kanban` :guilabel:`(Kanban)` view, but there is also the option to view these tracks in a :icon:`oi-view-list` :guilabel:`(List)`, :icon:`oi-view-cohort` :guilabel:`(Gantt)` chart, :icon:`fa-calendar-check-o` :guilabel:`(Calendar)`, :icon:`fa-area-chart` :guilabel:`(Graph)`, or :icon:`fa-clock-o` :guilabel:`(Activity)` view. All of which are accessible in the upper-right corner of the :guilabel:`Tracks` page." +msgstr "" + +#: ../../content/applications/marketing/events/event_tracks.rst:74 +msgid "In the default :icon:`oi-view-kanban` :guilabel:`(Kanban)` view, the tracks are categorized into different stages. The default stages are: :guilabel:`Proposal`, :guilabel:`Confirmed`, :guilabel:`Announced`, :guilabel:`Published`, :guilabel:`Refused` (collapsed stage), and :guilabel:`Cancelled` (collapsed stage). All of which can be edited, if needed." +msgstr "" + +#: ../../content/applications/marketing/events/event_tracks.rst:80 +msgid "To edit a stage, hover over the stage name, click the :icon:`fa-cog` :guilabel:`(Settings)` icon, and select :guilabel:`Edit` from the resulting drop-down menu." +msgstr "" + +#: ../../content/applications/marketing/events/event_tracks.rst:83 +msgid "Clicking into a track from the :guilabel:`Event Tracks` page reveals the track form for that particular track." +msgstr "" + +#: ../../content/applications/marketing/events/event_tracks.rst:87 +msgid "Create event track" +msgstr "" + +#: ../../content/applications/marketing/events/event_tracks.rst:89 +msgid "From the :guilabel:`Event Tracks` page, click :guilabel:`New` in the upper-left corner to reveal a blank event track form to create an event track." +msgstr "" + +#: ../../content/applications/marketing/events/event_tracks.rst:-1 +msgid "Typical event track form in the Odoo Events application." +msgstr "" + +#: ../../content/applications/marketing/events/event_tracks.rst:96 +msgid "Start by giving this track a :guilabel:`Title`. This field is **required** by Odoo." +msgstr "" + +#: ../../content/applications/marketing/events/event_tracks.rst:98 +msgid "Then, if desired, add an accompanying image to the track via the :icon:`fa-pencil` :guilabel:`(pencil)` icon that appears when the cursor hovers over the :icon:`fa-camera` :guilabel:`(camera)` icon in the upper-right corner of the form. When clicked, proceed to upload the desired image for the track. This image appears on the front-end of the event website, on this specific tracks webpage." +msgstr "" + +#: ../../content/applications/marketing/events/event_tracks.rst:104 +msgid "Next, enter a :guilabel:`Track Date` and time for the track, and designate a :guilabel:`Location` where the talk is planning to be held." +msgstr "" + +#: ../../content/applications/marketing/events/event_tracks.rst:108 +msgid "To access a complete list of locations for event tracks, which can be modified (and added to) at any time, navigate to :menuselection:`Events app --> Configuration --> Track Locations`." +msgstr "" + +#: ../../content/applications/marketing/events/event_tracks.rst:111 +msgid "Then, add a :guilabel:`Duration` to the track (in minutes)." +msgstr "" + +#: ../../content/applications/marketing/events/event_tracks.rst:113 +msgid "If the *Live Broadcast* setting has been enabled in the *Events* app settings, the option to add a corresponding link in the :guilabel:`YouTube Video Link` field is available." +msgstr "" + +#: ../../content/applications/marketing/events/event_tracks.rst:116 +msgid "If the :guilabel:`Always Wishlisted` checkbox is ticked, the talk is automatically set as a favorite for each registered event attendee." +msgstr "" + +#: ../../content/applications/marketing/events/event_tracks.rst:119 +msgid "Assign someone to be in charge of managing this track in the :guilabel:`Responsible` field. By default, the person who initially created the track is assigned." +msgstr "" + +#: ../../content/applications/marketing/events/event_tracks.rst:122 +msgid "Then, ensure the track is applied to the correct event in the :guilabel:`Event` field. By default, this field is auto-populated with the event related to the *Event Tracks* page the track was originally created from." +msgstr "" + +#: ../../content/applications/marketing/events/event_tracks.rst:126 +msgid "Next, choose to add existing tags, or create new ones, to further organize the track. These tags, and their corresponding tag categories are utilized on the event specific website - mainly on the *Talks* web page on the event website, via the drop-down filter menus." +msgstr "" + +#: ../../content/applications/marketing/events/event_tracks.rst:130 +msgid "Beneath that general information section, there are three tabs: :ref:`Speaker `, :ref:`Description `, and :ref:`Interactivity `." +msgstr "" + +#: ../../content/applications/marketing/events/event_tracks.rst:137 +msgid "Speaker tab" +msgstr "" + +#: ../../content/applications/marketing/events/event_tracks.rst:139 +msgid "The :guilabel:`Speaker` tab on an event track form is filled with various fields related to the specific speaker who is planning to conduct/host the track." +msgstr "" + +#: ../../content/applications/marketing/events/event_tracks.rst:-1 +msgid "The Speaker tab on an event track form in the Odoo Events application." +msgstr "" + +#: ../../content/applications/marketing/events/event_tracks.rst:147 +msgid "Contact Details section" +msgstr "" + +#: ../../content/applications/marketing/events/event_tracks.rst:149 +msgid "In the :guilabel:`Contact Details` section, proceed to use the :guilabel:`Contact` drop-down field to select an existing contact from the database as the main point of contact for the talk." +msgstr "" + +#: ../../content/applications/marketing/events/event_tracks.rst:152 +msgid "If this contact is not yet in the database, type in the name of the contact, and click :guilabel:`Create` to create and edit the contact form later, or click :guilabel:`Create and edit...` to be taken to that new contact's contact form, where the rest of their pertinent information can be entered." +msgstr "" + +#: ../../content/applications/marketing/events/event_tracks.rst:157 +msgid "The :guilabel:`Contact Email` and :guilabel:`Contact Phone` fields are greyed-out and populated with the information found on that chosen contact's contact form. These fields are not modifiable once the :guilabel:`Contact` field is selected." +msgstr "" + +#: ../../content/applications/marketing/events/event_tracks.rst:162 +msgid "Speaker Bio section" +msgstr "" + +#: ../../content/applications/marketing/events/event_tracks.rst:164 +msgid "In the :guilabel:`Speaker Bio` section, proceed to enter information related to the specific speaker scheduled to conduct/host the track. This section may auto-populate based on the :guilabel:`Contact` selected in the :guilabel:`Contact Details` section. If not, enter information in the necessary fields." +msgstr "" + +#: ../../content/applications/marketing/events/event_tracks.rst:170 +msgid "This information appears on the front-end of the event website, on the specific track webpage, providing more information about the speaker to the track attendees." +msgstr "" + +#: ../../content/applications/marketing/events/event_tracks.rst:173 +msgid "Start by entering a :guilabel:`Name`, :guilabel:`Email`, and :guilabel:`Phone` number for the speaker." +msgstr "" + +#: ../../content/applications/marketing/events/event_tracks.rst:176 +msgid "Next, if desired, add an image to appear alongside the speaker biogrpahy on the event website, via the :icon:`fa-pencil` :guilabel:`(pencil)` icon that appears when the cursor hovers over the :icon:`fa-camera` :guilabel:`(camera)` icon. When clicked, proceed to upload the desired image for the speaker." +msgstr "" + +#: ../../content/applications/marketing/events/event_tracks.rst:181 +msgid "Then, enter a :guilabel:`Job Position` for the designated speaker, followed by the :guilabel:`Company Name` associated with the speaker." +msgstr "" + +#: ../../content/applications/marketing/events/event_tracks.rst:184 +msgid "In the :guilabel:`Biography` field, proceed to enter in a custom biography with any speaker-related information." +msgstr "" + +#: ../../content/applications/marketing/events/event_tracks.rst:190 +#: ../../content/applications/marketing/surveys/create.rst:258 +#: ../../content/applications/marketing/surveys/questions.rst:198 +msgid "Description tab" +msgstr "" + +#: ../../content/applications/marketing/events/event_tracks.rst:192 +msgid "The :guilabel:`Description` tab of an event track form is a blank text field, in which a description of the track can be entered. The information entered here appears on the specific track page on the event website." +msgstr "" + +#: ../../content/applications/marketing/events/event_tracks.rst:199 +msgid "Interactivity tab" +msgstr "" + +#: ../../content/applications/marketing/events/event_tracks.rst:201 +msgid "The :guilabel:`Interactivity` tab on an event track form features a single option at first: :guilabel:`Magic Button`." +msgstr "" + +#: ../../content/applications/marketing/events/event_tracks.rst:-1 +msgid "The Interactivity tab on an event track form in the Odoo Events application." +msgstr "" + +#: ../../content/applications/marketing/events/event_tracks.rst:208 +msgid "When the checkbox beside :guilabel:`Magic Button` is ticked, Odoo displays a *call to action* button to attendees on the track sidebar, while the track is taking place." +msgstr "" + +#: ../../content/applications/marketing/events/event_tracks.rst:211 +msgid "With that checkbox ticked, three more options appear, all of which are related to the :guilabel:`Magic Button`:" +msgstr "" + +#: ../../content/applications/marketing/events/event_tracks.rst:214 +msgid ":guilabel:`Button Title`: enter a title to appear on the button for attendees." +msgstr "" + +#: ../../content/applications/marketing/events/event_tracks.rst:215 +msgid ":guilabel:`Button Target URL`: enter a URL that leads attendees, who click the button, to a specific page." +msgstr "" + +#: ../../content/applications/marketing/events/event_tracks.rst:217 +msgid ":guilabel:`Show Button`: enter a number in the field, and the button will appear that number of :guilabel:`minutes after Track start`." +msgstr "" + +#: ../../content/applications/marketing/events/event_tracks.rst:221 +msgid "The magic button **only** appears if there is more than one published track." +msgstr "" + +#: ../../content/applications/marketing/events/event_tracks.rst:226 +msgid "Add Quiz button" +msgstr "" + +#: ../../content/applications/marketing/events/event_tracks.rst:228 +msgid "The :guilabel:`Add Quiz` button **only** appears on event track forms if the *Event Gamification* setting is enabled in the Odoo *Events* settings." +msgstr "" + +#: ../../content/applications/marketing/events/event_tracks.rst:231 +msgid "To add a quiz to the event track, click the :guilabel:`Add Quiz` button. Doing so reveals a separate page where an event track quiz can be created and configured." +msgstr "" + +#: ../../content/applications/marketing/events/event_tracks.rst:-1 +msgid "The Add Quiz page in the Odoo Events application for an event track." +msgstr "" + +#: ../../content/applications/marketing/events/event_tracks.rst:238 +msgid "Start by entering a title for the quiz in the blank field at the top of the page. Then, if participants should be allowed to try the quiz multiple times, tick the checkbox beside :guilabel:`Allow multiple tries`." +msgstr "" + +#: ../../content/applications/marketing/events/event_tracks.rst:242 +msgid "The :guilabel:`Event` and :guilabel:`Event Track` fields are non-modifiable, and show the corresponding event and track this quiz is associated with." +msgstr "" + +#: ../../content/applications/marketing/events/event_tracks.rst:245 +msgid "To add questions to the quiz, click :guilabel:`Add a line` beneath the :guilabel:`Question` column. Doing so reveals a :guilabel:`Create Questions` pop-up window." +msgstr "" + +#: ../../content/applications/marketing/events/event_tracks.rst:-1 +msgid "The Create Questions pop-up window on an event-specific track quiz in the Odoo Events app." +msgstr "" + +#: ../../content/applications/marketing/events/event_tracks.rst:253 +msgid "**All** track quiz questions are multiple choice." +msgstr "" + +#: ../../content/applications/marketing/events/event_tracks.rst:255 +msgid "From the pop-up window, enter the question in the blank field at the top. Then, click :guilabel:`Add a line` to add answer options. Upon clicking :guilabel:`Add a line`, a new line appears, in which an answer option can be entered." +msgstr "" + +#: ../../content/applications/marketing/events/event_tracks.rst:259 +msgid "Once an answer option has been entered, proceed to designate whether it is the :guilabel:`Correct` response, by ticking the checkbox in the :guilabel:`Correct` column." +msgstr "" + +#: ../../content/applications/marketing/events/event_tracks.rst:262 +msgid "Then, there is the option to add a point value in the :guilabel:`Points` column." +msgstr "" + +#: ../../content/applications/marketing/events/event_tracks.rst:264 +msgid "And, if there are any additional comments that should accompany an answer option, type them into the :guilabel:`Extra Comment` field." +msgstr "" + +#: ../../content/applications/marketing/events/event_tracks.rst:268 +msgid "The :guilabel:`Correct`, :guilabel:`Points`, and :guilabel:`Extra Comment` fields are all optional." +msgstr "" + +#: ../../content/applications/marketing/events/event_tracks.rst:271 +msgid "Repeat this process for all the answer options." +msgstr "" + +#: ../../content/applications/marketing/events/event_tracks.rst:273 +msgid "To remove an answer option, click the :icon:`fa-trash-o` :guilabel:`(trash can)` icon on the far-right." +msgstr "" + +#: ../../content/applications/marketing/events/event_tracks.rst:276 +msgid "Once all desired answer options (and their configurations) are complete, click :guilabel:`Save & Close` to save the question, close the pop-up window, and return to the track quiz form. Or, click :guilabel:`Save & New` to save this question, and instantly start creating another question on a new :guilabel:`Create Questions` pop-up form." +msgstr "" + +#: ../../content/applications/marketing/events/event_tracks.rst:281 +msgid "To remove any question from the quiz, click the :icon:`fa-trash-o` :guilabel:`(trash can)` icon on the far-right of the question line." +msgstr "" + +#: ../../content/applications/marketing/events/event_tracks.rst:285 +msgid "Publish event track" +msgstr "" + +#: ../../content/applications/marketing/events/event_tracks.rst:287 +msgid "Once all the desired configurations are complete on an event track form, click the desired stage it should be in from the status bar in the upper-right corner (e.g. :guilabel:`Confirmed`, :guilabel:`Announced`, etc.)." +msgstr "" + +#: ../../content/applications/marketing/events/event_tracks.rst:292 +msgid "The stage of a track can also be changed from the :guilabel:`Event Tracks` page, where the desired track card can be dragged-and-dropped into the appropriate Kanban stage." +msgstr "" + +#: ../../content/applications/marketing/events/event_tracks.rst:295 +msgid "If an event track has *not* been published yet, and it is moved to the :guilabel:`Published` stage, Odoo automatically publishes the track on the event website." +msgstr "" + +#: ../../content/applications/marketing/events/event_tracks.rst:298 +msgid "An event track can *also* be published by opening the desired event track form, and clicking the :guilabel:`Go to Website` smart button. Then, in order for the track page to be viewable (and accessible) for event attendees, toggle the :icon:`fa-toggle-off` :guilabel:`Unpublished` switch at the top of the page to :icon:`fa-toggle-on` :guilabel:`Published`; thus turning it from red to green, and making it accessible for attendees." +msgstr "" + +#: ../../content/applications/marketing/events/event_tracks.rst:-1 +#: ../../content/applications/marketing/events/track_manage_talks.rst:-1 +msgid "The track-related event submenu options on an event website built with Odoo Events." msgstr "" #: ../../content/applications/marketing/events/sell_tickets.rst:5 @@ -3003,12 +3655,6 @@ msgstr "" msgid "To learn more about how to create custom tickets (and ticket tiers) for events, check out the :doc:`create_events` documentation." msgstr "" -#: ../../content/applications/marketing/events/sell_tickets.rst:18 -#: ../../content/applications/marketing/events/track_manage_talks.rst:9 -#: ../../content/applications/marketing/marketing_automation.rst:44 -msgid "Configuration" -msgstr "" - #: ../../content/applications/marketing/events/sell_tickets.rst:20 msgid "In order to sell event tickets in Odoo, some settings must first be enabled." msgstr "" @@ -3137,189 +3783,165 @@ msgstr "" msgid "Then, once the purchase is complete on the front-end of the website, the subsequent sales order is instantly accessible in the back-end of the database." msgstr "" +#: ../../content/applications/marketing/events/track_manage_talks.rst:3 +msgid "Talks, proposals, and agenda" +msgstr "" + #: ../../content/applications/marketing/events/track_manage_talks.rst:5 -msgid "With Odoo Events, it's possible to provide attendees with the power to propose presenters to speak at events." +msgid "With Odoo *Events*, users can utilize a fully-integrated event website, where attendees can quickly access various tracks (talks, presentations, etc.), view entire agendas, and propose talks for the event." msgstr "" -#: ../../content/applications/marketing/events/track_manage_talks.rst:11 -msgid "First, go to :menuselection:`Events --> Configuration --> Settings` and enable :guilabel:`Schedule & Tracks`." +#: ../../content/applications/marketing/events/track_manage_talks.rst:10 +msgid "Event website" msgstr "" -#: ../../content/applications/marketing/events/track_manage_talks.rst:14 -msgid "When that feature is enabled, two more options become available: *Live Broadcast* and *Event Gamification*." +#: ../../content/applications/marketing/events/track_manage_talks.rst:12 +msgid "To access an event website, navigate to the specific event form in the Odoo *Events* app, and click the :guilabel:`Go to Website` smart button. Or, while on the Odoo-built website for the company, click the :guilabel:`Events` header option, and select the desired event to view that event's website." msgstr "" #: ../../content/applications/marketing/events/track_manage_talks.rst:17 -msgid ":guilabel:`Live Broadcast` allows for the airing of tracks online through a YouTube integration." +msgid "On the event website, there is an event-specific subheader menu with different options to choose from." msgstr "" -#: ../../content/applications/marketing/events/track_manage_talks.rst:19 -msgid ":guilabel:`Event Gamification` allows for the sharing of a quiz with your attendees, once a track (talk) is over." +#: ../../content/applications/marketing/events/track_manage_talks.rst:20 +msgid "With the *Schedule & Tracks* setting enabled in the Odoo *Events* app, the following links are automatically added to the subheader menu, located on the event website: :guilabel:`Talks`, :guilabel:`Talk Proposals`, and :guilabel:`Agenda`." msgstr "" -#: ../../content/applications/marketing/events/track_manage_talks.rst:23 -msgid ":guilabel:`Event Gamification` isn't necessary for tracks to appear on the event page on the website, but it can enhance the engagement and overall enjoyablity of the event for attendees." -msgstr "" - -#: ../../content/applications/marketing/events/track_manage_talks.rst:27 -msgid "Talks, talk proposals, and agenda" -msgstr "" - -#: ../../content/applications/marketing/events/track_manage_talks.rst:29 -msgid "Once those two features are enabled, the following links are automatically added to the sub-header menu, located on the event page on the website: :guilabel:`Talks`, :guilabel:`Talk Proposals`, and :guilabel:`Agenda`. Any attendee can freely access these menu items and their corresponding content." +#: ../../content/applications/marketing/events/track_manage_talks.rst:28 +msgid "To enable the :guilabel:`Schedule & Tracks` setting, navigate to :menuselection:`Events app --> Configuration --> Settings`, tick the checkbox beside :guilabel:`Schedule & Tracks`, and click :guilabel:`Save`." msgstr "" #: ../../content/applications/marketing/events/track_manage_talks.rst:33 -msgid "The :guilabel:`Talks` link takes the attendee to a page full of all the talks for that event." +msgid "Talks page" msgstr "" #: ../../content/applications/marketing/events/track_manage_talks.rst:35 -msgid "The :guilabel:`Talks Proposals` link takes the attendee to a form page, where they can propose talks for the event." -msgstr "" - -#: ../../content/applications/marketing/events/track_manage_talks.rst:38 -msgid "The :guilabel:`Agenda` link takes the attendee to a page with all the talks for the event, but in a calendar/time-slot format." +msgid "The :guilabel:`Talks` link takes the attendee to a page filled with all the planned tracks for the event." msgstr "" #: ../../content/applications/marketing/events/track_manage_talks.rst:-1 -msgid "View of the published website and the talks, talk proposals, and agenda in Odoo Events" +msgid "The Talks page on an event website built through the Odoo Events application." msgstr "" -#: ../../content/applications/marketing/events/track_manage_talks.rst:46 -msgid "Manage talk proposals" +#: ../../content/applications/marketing/events/track_manage_talks.rst:42 +msgid "At the top of :guilabel:`Talks` page, there are drop-down filter menus beside a :guilabel:`Search a talk...` search bar." msgstr "" -#: ../../content/applications/marketing/events/track_manage_talks.rst:48 -msgid "When attendees fill out and submit a talk proposal form on the website, a new :guilabel:`Proposal` is instantly created in the back end for the event." +#: ../../content/applications/marketing/events/track_manage_talks.rst:45 +msgid "The first drop-down filter menu (with the starting title: :guilabel:`Favorites`) is the only drop-down filter menu that appears by default. When clicked, the resulting menu presents two options: :guilabel:`Favorites` and :guilabel:`All Talks`." +msgstr "" + +#: ../../content/applications/marketing/events/track_manage_talks.rst:49 +msgid "Selecting :guilabel:`Favorites` shows *only* the tracks that have been favorited by the attendee." msgstr "" #: ../../content/applications/marketing/events/track_manage_talks.rst:52 -msgid "All talks (Proposals, Confirmed, Announced, etc.) are accessible via the :guilabel:`Tracks` smart button on the event form." +msgid "If no tracks have been favorited, and the :guilabel:`Favorites` filter is selected, Odoo presents all the event tracks." +msgstr "" + +#: ../../content/applications/marketing/events/track_manage_talks.rst:55 +msgid "Selecting :guilabel:`All Talks` shows *all* the tracks, regardless if they have been favorited or not." +msgstr "" + +#: ../../content/applications/marketing/events/track_manage_talks.rst:58 +msgid "The other drop-down filter menus that appear on this page are related to any configured tags (and tag categories) created for event tracks in the backend." +msgstr "" + +#: ../../content/applications/marketing/events/track_manage_talks.rst:62 +msgid "To add tags and tag categories to track forms, open a desired event track form, and start typing a new tag in the :guilabel:`Tags` field. Then, click :guilabel:`Create and edit...` from the resulting drop-down menu." +msgstr "" + +#: ../../content/applications/marketing/events/track_manage_talks.rst:66 +msgid "Doing so reveals a :guilabel:`Create Tags` pop-up form." msgstr "" #: ../../content/applications/marketing/events/track_manage_talks.rst:-1 -msgid "View of the talks' proposals page emphasizing the column proposal in Odoo Events." +msgid "The Create Tags pop-up form that coincides with drop-down filter menus on Talks page." msgstr "" -#: ../../content/applications/marketing/events/track_manage_talks.rst:59 -msgid "If a proposal is accepted, move the :guilabel:`Event Track` to the appropriate stage in the Kanban view (e.g. `Confirmed`, etc.). Then, go to that particular event's template form, and click the :guilabel:`Go to Website` smart button to reach that specific talk's page on the website." +#: ../../content/applications/marketing/events/track_manage_talks.rst:72 +msgid "From here, users see the recently added tag in the :guilabel:`Tag Name` field. Beneath that, there is an option to add a specific :guilabel:`Color Index` to the tag for added organization." msgstr "" -#: ../../content/applications/marketing/events/track_manage_talks.rst:63 -msgid "In the upper right corner, toggle the switch from :guilabel:`Unpublished` to :guilabel:`Published`, and the talk is instantly accessible on the website." +#: ../../content/applications/marketing/events/track_manage_talks.rst:75 +msgid "Lastly, there is the :guilabel:`Category` field, where users can either select a pre-existing category for this new tag, or create a new one." msgstr "" -#: ../../content/applications/marketing/events/track_manage_talks.rst:67 -msgid "Without publishing a talk, attendees will never be able to access it." -msgstr "" - -#: ../../content/applications/marketing/events/track_manage_talks.rst:-1 -msgid "View of the website page to publish a proposed talk for Odoo Events." -msgstr "" - -#: ../../content/applications/marketing/events/track_manage_talks.rst:74 -msgid "Attendees list and attendance" -msgstr "" - -#: ../../content/applications/marketing/events/track_manage_talks.rst:76 -msgid "Once attendees have registered for a specific event, they are added to the :guilabel:`Attendee List` for that event, which is accessible via the :guilabel:`Attendees` smart button on the event template form, or :menuselection:`Reporting --> Attendees` and sorted by event." +#: ../../content/applications/marketing/events/track_manage_talks.rst:78 +msgid "All options in the :guilabel:`Category` field for tags appear as their own drop-down filter menu on the :guilabel:`Talks` page, located on the event website." msgstr "" #: ../../content/applications/marketing/events/track_manage_talks.rst:81 -msgid "When an attendee arrives at the event, they will be marked as attending (:guilabel:`Confirmed Attendance`), and the status of that attendee will change to :guilabel:`Attended.`" +msgid "Beneath the drop-down filter menus at the top of the :guilabel:`Talks` page, there is a list of planned tracks for the specific event, organized by day." msgstr "" -#: ../../content/applications/marketing/events/track_manage_talks.rst:-1 -msgid "Overview of events with the kanban view in Odoo Events." +#: ../../content/applications/marketing/events/track_manage_talks.rst:84 +#: ../../content/applications/marketing/events/track_manage_talks.rst:141 +msgid "If an attendee wishes to favorite a track, they can click the :icon:`fa-bell-o` :guilabel:`(empty bell)` icon, located to the right of the track title. Attendees will know a track has been favorited when they notice the icon has been changed to :icon:`fa-bell` :guilabel:`(filled bell)` icon." msgstr "" #: ../../content/applications/marketing/events/track_manage_talks.rst:88 -msgid "When analyzing an :guilabel:`Attendees list`, Odoo provides different ways to view the information. Each view option presents the same information, but in a slightly different layout. To change the view, click on the icons in the upper right hand of the screen." +msgid "Favoriting a track this way places it on the list of :guilabel:`Favorites`, which is accessible from the default drop-down filter menu, located at the top of the :guilabel:`Talks` page." +msgstr "" + +#: ../../content/applications/marketing/events/track_manage_talks.rst:92 +msgid "Talk Proposals page" +msgstr "" + +#: ../../content/applications/marketing/events/track_manage_talks.rst:94 +msgid "The :guilabel:`Talk Proposals` link takes attendees to a page on the event website, wherein they can formerly submit a proposal for a talk (:dfn:`track`) for the event, via a custom online form." msgstr "" #: ../../content/applications/marketing/events/track_manage_talks.rst:-1 -msgid "Various view options on the attendees list page." -msgstr "" - -#: ../../content/applications/marketing/events/track_manage_talks.rst:96 -msgid "In the :guilabel:`Kanban` view, it can be confirmed whether the attendees have already paid or remain unpaid." -msgstr "" - -#: ../../content/applications/marketing/events/track_manage_talks.rst:99 -msgid "The :guilabel:`List` view provides information in a more traditional list formation." +msgid "The Talk Proposals page on the event website built with the Odoo Events application." msgstr "" #: ../../content/applications/marketing/events/track_manage_talks.rst:101 -msgid "The :guilabel:`Calendar` view provides a clear schedule visualization of which attendees are arriving on specific dates of the event." +msgid "In addition to the form, an introduction to the page, along with any other pertinent information related to the types of talks the event will feature can be added, if needed." msgstr "" #: ../../content/applications/marketing/events/track_manage_talks.rst:104 -msgid "The :guilabel:`Graph` view provides graphical representations of that event's attendees, along with numerous filters and customizable measures for deeper analysis." +msgid "The talk proposal form can be modified in a number of different ways, via the web builder tools, accessible by clicking :guilabel:`Edit` while on the specific page." msgstr "" #: ../../content/applications/marketing/events/track_manage_talks.rst:107 -msgid "The :guilabel:`Cohort` view lays out attendee data to better analyze the number of registration dates." +msgid "Then, proceed to edit any of the default fields, or add new forms with the :guilabel:`Form` building block (located in the :guilabel:`Blocks` section of the web builder tools sidebar)." msgstr "" -#: ../../content/applications/marketing/events/track_manage_talks.rst:111 -msgid "Tickets sold through sales orders validate attendees as soon as the quotation is confirmed." +#: ../../content/applications/marketing/events/track_manage_talks.rst:110 +msgid "Once all the necessary information is entered into the form, the attendees just need to click the :guilabel:`Submit Proposal` button." msgstr "" -#: ../../content/applications/marketing/events/track_manage_talks.rst:114 -msgid "Manage registrations" +#: ../../content/applications/marketing/events/track_manage_talks.rst:113 +msgid "Then, that talk, and all the information entered on the form, can be accessed on the :guilabel:`Event Tracks` page for that specific event in the :guilabel:`Proposal` stage, which is accessible via the :guilabel:`Tracks` smart button on the event form." msgstr "" -#: ../../content/applications/marketing/events/track_manage_talks.rst:116 -msgid "Upon selecting an attendee, Odoo reveals that specific attendee's detail form." +#: ../../content/applications/marketing/events/track_manage_talks.rst:117 +msgid "At that point, an internal user can review the proposed talk, and choose to accept or deny the proposal." msgstr "" -#: ../../content/applications/marketing/events/track_manage_talks.rst:118 -msgid "From here, event badges can be sent manually, by selecting :guilabel:`Send By Email`. The :guilabel:`Attendee` can also be marked as :guilabel:`Attended`, or the registration can be canceled altogether via the :guilabel:`Cancel Registration` button." +#: ../../content/applications/marketing/events/track_manage_talks.rst:120 +msgid "If accepted, the internal user can then move the track to the next appropriate stage in the Kanban pipeline on the :guilabel:`Event Tracks` page for the event. Then, they can open that track form, and click the :guilabel:`Go to Website` smart button to reveal that track's page on the event website." +msgstr "" + +#: ../../content/applications/marketing/events/track_manage_talks.rst:125 +msgid "From there, they can toggle the :guilabel:`Unpublished` switch in the header to :guilabel:`Published`, which allows all event attendees to view and access the talk." +msgstr "" + +#: ../../content/applications/marketing/events/track_manage_talks.rst:129 +msgid "Agenda page" +msgstr "" + +#: ../../content/applications/marketing/events/track_manage_talks.rst:131 +msgid "The :guilabel:`Agenda` link takes attendees to a page on the event website, showcasing an event calendar, depicting when (and where) events are taking place for that specific event." msgstr "" #: ../../content/applications/marketing/events/track_manage_talks.rst:-1 -msgid "View of an attendee form emphasizing the send by email and cancel registration in Odoo\n" -"Events." +msgid "The event Agenda page on the event website built with the Odoo Events application." msgstr "" -#: ../../content/applications/marketing/events/track_manage_talks.rst:128 -msgid "Lead Generation Rules" -msgstr "" - -#: ../../content/applications/marketing/events/track_manage_talks.rst:130 -msgid "With Odoo, leads can be generated from events." -msgstr "" - -#: ../../content/applications/marketing/events/track_manage_talks.rst:132 -msgid "To create and configure a :guilabel:`Lead Generation Rule` related to events, navigate to :menuselection:`Events app --> Configuration --> Lead Generation`." -msgstr "" - -#: ../../content/applications/marketing/events/track_manage_talks.rst:135 -msgid "On the :guilabel:`Lead Generation Rule` page, every configured :guilabel:`Lead Generation Rule` can be found, along with pertinent data related to those rules." -msgstr "" - -#: ../../content/applications/marketing/events/track_manage_talks.rst:-1 -msgid "How the Lead Generation Rule page looks in Odoo Events." -msgstr "" - -#: ../../content/applications/marketing/events/track_manage_talks.rst:142 -msgid "To create a new :guilabel:`Lead Generation Rule`, click :guilabel:`Create`, and fill out the :guilabel:`Lead Generation Rule` form." -msgstr "" - -#: ../../content/applications/marketing/events/track_manage_talks.rst:-1 -msgid "How the Lead Generation Rule template looks in Odoo Events." -msgstr "" - -#: ../../content/applications/marketing/events/track_manage_talks.rst:149 -msgid "After naming the rule, configure *how* the lead should be created (either :guilabel:`Per Attendee` or :guilabel:`Per Order`), and *when* they should be created, (when :guilabel:`Attendees are created`, when :guilabel:`Attendees are confirmed`, or when :guilabel:`Attendees attended` the event)." -msgstr "" - -#: ../../content/applications/marketing/events/track_manage_talks.rst:154 -msgid "In the :guilabel:`For any of these Events` section, there are fields to attach this rule to any specific event categories, company, and/or event. To add even more specificity to the rule, a domain filter rule can be configured to ensure the rule only applies to a specific target audience of attendees (found in the :guilabel:`If the Attendees meet these Conditions` section)." -msgstr "" - -#: ../../content/applications/marketing/events/track_manage_talks.rst:159 -msgid "Lastly, in the :guilabel:`Lead Default Values` section, designate a :guilabel:`Lead Type`, then assign it to a specific :guilabel:`Sales Team` (and/or :guilabel:`Salesperson`), and attach tags to the rule, if necessary." +#: ../../content/applications/marketing/events/track_manage_talks.rst:138 +msgid "Clicking any track on the calendar takes the attendee to that specific track's detail page on the event website." msgstr "" #: ../../content/applications/marketing/marketing_automation.rst:5 @@ -7098,11 +7720,6 @@ msgstr "" msgid ":doc:`live_session`" msgstr "" -#: ../../content/applications/marketing/surveys/create.rst:258 -#: ../../content/applications/marketing/surveys/questions.rst:198 -msgid "Description tab" -msgstr "" - #: ../../content/applications/marketing/surveys/create.rst:260 msgid "In this non-required tab, users can enter a custom description about the survey, along with any explanations or guidance that a survey participant may need in order to properly participate (and complete) the survey." msgstr "" diff --git a/locale/sources/productivity.pot b/locale/sources/productivity.pot index e742fdb4d..daa9ceea1 100644 --- a/locale/sources/productivity.pot +++ b/locale/sources/productivity.pot @@ -8,7 +8,7 @@ msgid "" msgstr "" "Project-Id-Version: Odoo 17.0\n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2024-06-24 07:08+0000\n" +"POT-Creation-Date: 2024-07-23 13:30+0000\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME \n" "Language-Team: LANGUAGE \n" @@ -635,6 +635,362 @@ msgstr "" msgid ":guilabel:`Synchronize all existing events`: sync all events on *Microsoft Outlook Calendar* and/or Odoo calendar." msgstr "" +#: ../../content/applications/productivity/data_cleaning.rst:3 +msgid "Data Cleaning" +msgstr "" + +#: ../../content/applications/productivity/data_cleaning.rst:5 +msgid "The Odoo *Data Cleaning* app keeps the database neat and organized throughout the use of its provided features:" +msgstr "" + +#: ../../content/applications/productivity/data_cleaning.rst:8 +msgid ":ref:`Deduplicates `: merges or removes duplicate entries to ensure data is unique." +msgstr "" + +#: ../../content/applications/productivity/data_cleaning.rst:10 +msgid ":ref:`Recycles `: identifies outdated records to either archive or delete them." +msgstr "" + +#: ../../content/applications/productivity/data_cleaning.rst:12 +msgid ":ref:`Merges `: combines multiple similar entries into one streamlined record." +msgstr "" + +#: ../../content/applications/productivity/data_cleaning.rst:14 +msgid ":ref:`Formats `: standardizes text data by finding and replacing it according to specified needs." +msgstr "" + +#: ../../content/applications/productivity/data_cleaning.rst:17 +msgid "Through customizable automated rules (or manual praxis), individual records and accompanying text data in the database will remain up-to-date and consistently formatted, tailored to company specifications." +msgstr "" + +#: ../../content/applications/productivity/data_cleaning.rst:24 +msgid "Install modules" +msgstr "" + +#: ../../content/applications/productivity/data_cleaning.rst:26 +msgid "The *Data Cleaning* application consists of several modules. :ref:`Install ` the following to access all available features:" +msgstr "" + +#: ../../content/applications/productivity/data_cleaning.rst:33 +#: ../../content/applications/productivity/voip/axivox/call_queues.rst:30 +#: ../../content/applications/productivity/whatsapp.rst:273 +#: ../../content/applications/productivity/whatsapp.rst:677 +msgid "Name" +msgstr "" + +#: ../../content/applications/productivity/data_cleaning.rst:34 +msgid "Technical name" +msgstr "" + +#: ../../content/applications/productivity/data_cleaning.rst:35 +#: ../../content/applications/productivity/documents.rst:91 +msgid "Description" +msgstr "" + +#: ../../content/applications/productivity/data_cleaning.rst:36 +msgid ":guilabel:`Data Recycle`" +msgstr "" + +#: ../../content/applications/productivity/data_cleaning.rst:37 +msgid "`data_recycle`" +msgstr "" + +#: ../../content/applications/productivity/data_cleaning.rst:38 +msgid "Base module to enable the recycle feature, available on Odoo Community edition." +msgstr "" + +#: ../../content/applications/productivity/data_cleaning.rst:39 +msgid ":guilabel:`Data Cleaning`" +msgstr "" + +#: ../../content/applications/productivity/data_cleaning.rst:40 +msgid "`data_cleaning`" +msgstr "" + +#: ../../content/applications/productivity/data_cleaning.rst:41 +msgid "Enables field cleaning feature to format text data across multiple records, available **only** on Odoo Enterprise edition." +msgstr "" + +#: ../../content/applications/productivity/data_cleaning.rst:43 +msgid ":guilabel:`Data Cleaning (merge)`" +msgstr "" + +#: ../../content/applications/productivity/data_cleaning.rst:44 +msgid "`data_merge`" +msgstr "" + +#: ../../content/applications/productivity/data_cleaning.rst:45 +msgid "Enables the deduplication feature to find similar (or duplicate) records, and merge them, available **only** on Odoo Enterprise edition." +msgstr "" + +#: ../../content/applications/productivity/data_cleaning.rst:53 +msgid ":guilabel:`CRM Deduplication`" +msgstr "" + +#: ../../content/applications/productivity/data_cleaning.rst:54 +msgid "`data_merge_crm`" +msgstr "" + +#: ../../content/applications/productivity/data_cleaning.rst:55 +msgid "Enables the deduplication feature on the *CRM* app, and uses the :doc:`CRM default merging feature <../sales/crm/pipeline/merge_similar>`." +msgstr "" + +#: ../../content/applications/productivity/data_cleaning.rst:57 +msgid ":guilabel:`Helpdesk Merge action`" +msgstr "" + +#: ../../content/applications/productivity/data_cleaning.rst:58 +msgid "`data_merge_helpdesk`" +msgstr "" + +#: ../../content/applications/productivity/data_cleaning.rst:59 +msgid "Enables the merge feature for the *Helpdesk* app." +msgstr "" + +#: ../../content/applications/productivity/data_cleaning.rst:60 +msgid ":guilabel:`Project Merge action`" +msgstr "" + +#: ../../content/applications/productivity/data_cleaning.rst:61 +msgid "`data_merge_project`" +msgstr "" + +#: ../../content/applications/productivity/data_cleaning.rst:62 +msgid "Enables the merge feature for the *Projects* app." +msgstr "" + +#: ../../content/applications/productivity/data_cleaning.rst:63 +msgid ":guilabel:`UTM Deduplication`" +msgstr "" + +#: ../../content/applications/productivity/data_cleaning.rst:64 +msgid "`data_merge_utm`" +msgstr "" + +#: ../../content/applications/productivity/data_cleaning.rst:65 +msgid "Enables the merge feature for the *UTM Tracker* app." +msgstr "" + +#: ../../content/applications/productivity/data_cleaning.rst:66 +msgid ":guilabel:`WMS Accounting Merge`" +msgstr "" + +#: ../../content/applications/productivity/data_cleaning.rst:67 +msgid "`data_merge_stock_account`" +msgstr "" + +#: ../../content/applications/productivity/data_cleaning.rst:68 +msgid "Creates a warning in cases of products merging that may affect inventory valuation, if the *Inventory* app is installed." +msgstr "" + +#: ../../content/applications/productivity/data_cleaning.rst:74 +msgid "Deduplication" +msgstr "" + +#: ../../content/applications/productivity/data_cleaning.rst:76 +msgid "On the :guilabel:`Duplicates` dashboard (:menuselection:`Data Cleaning app --> Deduplication`), Odoo suggests groups of similar records to be :ref:`merged ` by matching conditions within the records set by the :ref:`deduplication rules `." +msgstr "" + +#: ../../content/applications/productivity/data_cleaning.rst:-1 +msgid "Deduplication dashboard in the Data Cleaning application." +msgstr "" + +#: ../../content/applications/productivity/data_cleaning.rst:85 +msgid "The :guilabel:`RULE` sidebar lists each of the active deduplication rules, and displays the total number of duplicates detected beside each rule." +msgstr "" + +#: ../../content/applications/productivity/data_cleaning.rst:88 +msgid "By default, the :guilabel:`All` rule is selected. Displayed records are grouped by their rule, with a :guilabel:`Similarity` rating (out of 100%) in the list view, with the following columns:" +msgstr "" + +#: ../../content/applications/productivity/data_cleaning.rst:91 +msgid ":guilabel:`Created On`: the date and time the original record was created." +msgstr "" + +#: ../../content/applications/productivity/data_cleaning.rst:92 +msgid ":guilabel:`Name`: the name or title of the original record." +msgstr "" + +#: ../../content/applications/productivity/data_cleaning.rst:93 +msgid ":guilabel:`Field Values`: the original record's values for the fields used to detect duplicates." +msgstr "" + +#: ../../content/applications/productivity/data_cleaning.rst:94 +msgid ":guilabel:`Used In`: lists other models referencing the original record." +msgstr "" + +#: ../../content/applications/productivity/data_cleaning.rst:95 +msgid ":guilabel:`ID`: the original record's unique ID." +msgstr "" + +#: ../../content/applications/productivity/data_cleaning.rst:96 +msgid ":guilabel:`Is Master`: the duplicates are merged into the *master* record. There can be **one** master record in a grouping of similar records." +msgstr "" + +#: ../../content/applications/productivity/data_cleaning.rst:99 +msgid "Select a specific rule in the :guilabel:`RULE` sidebar to filter the duplicate records." +msgstr "" + +#: ../../content/applications/productivity/data_cleaning.rst:104 +msgid "Merge duplicate records" +msgstr "" + +#: ../../content/applications/productivity/data_cleaning.rst:106 +msgid "To merge records, first choose a *master* record within the grouping of similar records. The master record acts as the base, at which any additional information from similar records are merged into." +msgstr "" + +#: ../../content/applications/productivity/data_cleaning.rst:109 +msgid "Optionally, no master record can be set, leaving Odoo to choose a record at random to merge into." +msgstr "" + +#: ../../content/applications/productivity/data_cleaning.rst:111 +msgid "Next, click the :guilabel:`Merge` button at the top of the similar records grouping. Then, click :guilabel:`Ok` to confirm the merge." +msgstr "" + +#: ../../content/applications/productivity/data_cleaning.rst:114 +msgid "Once a record is merged, a message is logged in the chatter of the master record, describing the merge. Certain records, like *Project* tasks, are logged in the chatter with a link to the old record for a convenient reference." +msgstr "" + +#: ../../content/applications/productivity/data_cleaning.rst:119 +msgid "Discard groupings by clicking the :guilabel:`DISCARD` button. Upon doing so, the grouping is hidden from the list and archived." +msgstr "" + +#: ../../content/applications/productivity/data_cleaning.rst:122 +msgid "View discarded groupings by selecting the :guilabel:`Discarded` filter from the :ref:`Search... ` bar." +msgstr "" + +#: ../../content/applications/productivity/data_cleaning.rst:128 +msgid "Deduplication rules" +msgstr "" + +#: ../../content/applications/productivity/data_cleaning.rst:130 +msgid "The :guilabel:`Deduplication Rules` page (:menuselection:`Data Cleaning app --> Configuration --> Rules: Deduplication`) is where the conditions for records to be detected as duplicates can be set." +msgstr "" + +#: ../../content/applications/productivity/data_cleaning.rst:133 +msgid "These rules can be configured for each model in the database, and with varying levels of specificity." +msgstr "" + +#: ../../content/applications/productivity/data_cleaning.rst:137 +msgid "The deduplication rules run once every day, by default, as part of a scheduled action chron (*Data Merge: Find Duplicate Records*). However, each rule can be :ref:`ran manually ` anytime." +msgstr "" + +#: ../../content/applications/productivity/data_cleaning.rst:142 +msgid "Modify a deduplication rule" +msgstr "" + +#: ../../content/applications/productivity/data_cleaning.rst:144 +msgid "Select a default rule to edit, or create a new rule by clicking on the :guilabel:`New` button, on the :guilabel:`Deduplication Rules` page (:menuselection:`Data Cleaning app --> Configuration --> Rules: Deduplication`)." +msgstr "" + +#: ../../content/applications/productivity/data_cleaning.rst:148 +msgid "First, choose a :guilabel:`Model` for this rule to target. Selecting a model updates the rule title to the chosen model." +msgstr "" + +#: ../../content/applications/productivity/data_cleaning.rst:151 +msgid "Optionally, configure a :guilabel:`Domain` to specify the records eligible for this rule. The number of eligible records is shown in the :icon:`oi-arrow-right` :guilabel:`# record(s)` link." +msgstr "" + +#: ../../content/applications/productivity/data_cleaning.rst:154 +msgid "Depending on the selected :guilabel:`Model`, the :guilabel:`Duplicate Removal` field appears. Choose whether to :guilabel:`Archive` or :guilabel:`Delete` merged records." +msgstr "" + +#: ../../content/applications/productivity/data_cleaning.rst:157 +msgid "Next, select a :guilabel:`Merge Mode`:" +msgstr "" + +#: ../../content/applications/productivity/data_cleaning.rst:159 +msgid ":guilabel:`Manual`: requires each duplicate grouping to be manually merged, also enables the :guilabel:`Notify Users` field." +msgstr "" + +#: ../../content/applications/productivity/data_cleaning.rst:161 +msgid ":guilabel:`Automatic`: automatically merges duplicate groupings, without notifying users, based on the records with a similarity percentage above the threshold set in the :guilabel:`Similarity Threshold` field." +msgstr "" + +#: ../../content/applications/productivity/data_cleaning.rst:165 +msgid "Enable the :guilabel:`Active` toggle to start capturing duplicates with this rule as soon as it is saved." +msgstr "" + +#: ../../content/applications/productivity/data_cleaning.rst:168 +msgid "Lastly, create at least one deduplication rule in the :guilabel:`Deduplication Rules` field, by clicking :guilabel:`Add a line`, under the :guilabel:`Unique ID Field` column." +msgstr "" + +#: ../../content/applications/productivity/data_cleaning.rst:171 +msgid "Select a field in the model from the :guilabel:`Unique ID Field` drop-down menu. This field is referenced for similar records." +msgstr "" + +#: ../../content/applications/productivity/data_cleaning.rst:173 +msgid "Select a matching condition in the :guilabel:`Match If` field to apply the deduplication rule, depending on the text in the :guilabel:`Unique ID Field`:" +msgstr "" + +#: ../../content/applications/productivity/data_cleaning.rst:176 +msgid ":guilabel:`Exact Match`: the characters in the text match exactly." +msgstr "" + +#: ../../content/applications/productivity/data_cleaning.rst:177 +msgid ":guilabel:`Case/Accent Insensitive Match`: the characters in the text match, regardless of casing and language-specific accent differences." +msgstr "" + +#: ../../content/applications/productivity/data_cleaning.rst:181 +msgid "The rule does **not** capture duplicates without at least one deduplication rule set in the :guilabel:`Deduplication Rules` field." +msgstr "" + +#: ../../content/applications/productivity/data_cleaning.rst:185 +msgid "A few more fields are available for an advanced configuration." +msgstr "" + +#: ../../content/applications/productivity/data_cleaning.rst:187 +msgid "If on a multi-company database, the :guilabel:`Cross-Company` field is available. When enabled, duplicates across different companies are suggested." +msgstr "" + +#: ../../content/applications/productivity/data_cleaning.rst:190 +msgid "Activate :ref:`developer-mode` to display the :guilabel:`Suggestion Threshold` field. Duplicates with a similarity below the threshold set in this field are **not** suggested." +msgstr "" + +#: ../../content/applications/productivity/data_cleaning.rst:193 +msgid "With the rule's configuration complete, either close the rule form, or :ref:`run the rule manually ` to instantly capture duplicate records." +msgstr "" + +#: ../../content/applications/productivity/data_cleaning.rst:199 +msgid "Manually run a deduplication rule" +msgstr "" + +#: ../../content/applications/productivity/data_cleaning.rst:201 +msgid "To manually run a specific deduplication rule at any time, navigate to :menuselection:`Data Cleaning app --> Configuration --> Rules: Deduplication`, and select the rule to run." +msgstr "" + +#: ../../content/applications/productivity/data_cleaning.rst:204 +msgid "Then, on the rule form, select the :guilabel:`Deduplicate` button on the top-left. Upon doing so, the :icon:`fa-clone` :guilabel:`Duplicates` smart button displays the number of duplicates captured." +msgstr "" + +#: ../../content/applications/productivity/data_cleaning.rst:207 +msgid "Click on the :icon:`fa-clone` :guilabel:`Duplicates` smart button to manage these records." +msgstr "" + +#: ../../content/applications/productivity/data_cleaning.rst:212 +msgid "Recycle records" +msgstr "" + +#: ../../content/applications/productivity/data_cleaning.rst:214 +msgid "On the :guilabel:`Field Recycle Records` dashboard (:menuselection:`Data Cleaning app --> Recycle Records`), Odoo detects records that can be archived or deleted, by matching conditions within the records set by the recycle record's rules." +msgstr "" + +#: ../../content/applications/productivity/data_cleaning.rst:221 +msgid "Field cleaning" +msgstr "" + +#: ../../content/applications/productivity/data_cleaning.rst:223 +msgid "On the :guilabel:`Field Cleaning Records* dashboard (:menuselection:`Data Cleaning app --> Field Cleaning`), Odoo suggests formatting changes to data in fields of a record, to follow a convention set by the field cleaning rules." +msgstr "" + +#: ../../content/applications/productivity/data_cleaning.rst:230 +msgid "Merge action manager" +msgstr "" + +#: ../../content/applications/productivity/data_cleaning.rst:232 +msgid "The :guilabel:`Merge Action Manager` (:menuselection:`Data Cleaning app --> Configuration --> Merge Action Manager`) enables or disables the *Merge* action available in the *Actions* menu for models in the database." +msgstr "" + #: ../../content/applications/productivity/discuss.rst:6 msgid "Discuss" msgstr "" @@ -1462,28 +1818,28 @@ msgid "`Odoo Documents: product page `_" msgstr "" #: ../../content/applications/productivity/documents.rst:11 -msgid "`Odoo Tutorials: Documents basics [video] `_" +msgid "`Odoo Tutorials: Documents basics [video] `_" msgstr "" -#: ../../content/applications/productivity/documents.rst:13 -msgid "`Odoo Tutorials: Using Documents with your Accounting App [video] `_" +#: ../../content/applications/productivity/documents.rst:12 +msgid "`Odoo Tutorials: Using Documents with your Accounting App [video] `_" msgstr "" -#: ../../content/applications/productivity/documents.rst:16 +#: ../../content/applications/productivity/documents.rst:15 #: ../../content/applications/productivity/voip/axivox/axivox_config.rst:17 #: ../../content/applications/productivity/voip/onsip.rst:33 msgid "Configuration" msgstr "" -#: ../../content/applications/productivity/documents.rst:18 -msgid "By going to :menuselection:`Documents --> Configuration --> Settings`, you can enable the centralization of files attached to a specific area of your activity. For example, by ticking :guilabel:`Human Resources`, your HR documents are automatically available in the HR workspace, while documents related to Payroll are automatically available in the Payroll sub-workspace . You can change the default workspace using the dropdown menu and edit its properties by clicking the internal link button (:guilabel:`➔`)." +#: ../../content/applications/productivity/documents.rst:17 +msgid "By going to :menuselection:`Documents --> Configuration --> Settings`, you can enable the centralization of files attached to a specific area of your activity. For example, by ticking :guilabel:`Human Resources`, your HR documents are automatically available in the HR workspace, while documents related to Payroll are automatically available in the Payroll sub-workspace. You can change the default workspace using the dropdown menu and edit its properties by clicking the :icon:`fa-arrow-right` (:guilabel:`Internal link`) icon." msgstr "" #: ../../content/applications/productivity/documents.rst:-1 msgid "Enable the centralization of files attached to a specific area of your activity." msgstr "" -#: ../../content/applications/productivity/documents.rst:29 +#: ../../content/applications/productivity/documents.rst:28 msgid "If you enable the centralization of your accounting files and documents, it is necessary to click on :guilabel:`Journals` and define each journal independently to allow automatic synchronization." msgstr "" @@ -1491,256 +1847,332 @@ msgstr "" msgid "Enable the centralization of files attached to your accounting." msgstr "" -#: ../../content/applications/productivity/documents.rst:36 +#: ../../content/applications/productivity/documents.rst:35 msgid "If you select a new workspace, existing documents are not moved. Only newly created documents will be found under the new workspace." msgstr "" -#: ../../content/applications/productivity/documents.rst:42 +#: ../../content/applications/productivity/documents.rst:41 msgid "Workspaces" msgstr "" -#: ../../content/applications/productivity/documents.rst:44 -msgid "Workspaces are hierarchical folders having their own set of tags and :ref:`actions `. Default workspaces exist, but you can create your own by going to :menuselection:`Documents --> Configuration --> Workspaces` and clicking :guilabel:`New`. On the new page, fill in the following information:" +#: ../../content/applications/productivity/documents.rst:43 +msgid "Workspaces are hierarchical folders having their own set of :ref:`tags ` and :ref:`actions `. Default workspaces exist, but you can create your own by going to :menuselection:`Documents --> Configuration --> Workspaces` and clicking :guilabel:`New`. On the new page, fill in the following information:" msgstr "" -#: ../../content/applications/productivity/documents.rst:49 +#: ../../content/applications/productivity/documents.rst:48 msgid ":guilabel:`Name`" msgstr "" -#: ../../content/applications/productivity/documents.rst:50 -msgid ":guilabel:`Parent Workspace`: if you want to create a sub-workspace, select its :guilabel:`Parent Workspace`" +#: ../../content/applications/productivity/documents.rst:49 +msgid ":guilabel:`Parent Workspace`: if you want to create a sub-workspace, select its :guilabel:`Parent Workspace`." msgstr "" -#: ../../content/applications/productivity/documents.rst:54 -#: ../../content/applications/productivity/sign.rst:236 +#: ../../content/applications/productivity/documents.rst:52 +msgid "Three tabs are available: :ref:`Tags `, :ref:`Access Rights `, and :ref:`Description `." +msgstr "" + +#: ../../content/applications/productivity/documents.rst:58 +#: ../../content/applications/productivity/sign.rst:250 msgid "Tags" msgstr "" -#: ../../content/applications/productivity/documents.rst:56 +#: ../../content/applications/productivity/documents.rst:60 msgid "Tags are used within workspaces to add a level of differentiation between documents. They are organized per category, and filters can be used to sort them." msgstr "" -#: ../../content/applications/productivity/documents.rst:59 -msgid "Tags can be created from the :guilabel:`Tags` tab. Click :guilabel:`Add a line`, create the :guilabel:`Tag Category`, and :guilabel:`Name` your tags." -msgstr "" - #: ../../content/applications/productivity/documents.rst:63 -msgid "The tags of a parent workspace apply to the child workspaces automatically;" -msgstr "" - -#: ../../content/applications/productivity/documents.rst:64 -msgid "Tags can be created and modified by going to :menuselection:`Configuration --> Tags`;" -msgstr "" - -#: ../../content/applications/productivity/documents.rst:65 -msgid "Tags can also be created or edited by clicking the gear icon :guilabel:`⚙` on the left menu." +msgid "From the :guilabel:`Tags` tab, click :guilabel:`Add a line`, create the :guilabel:`Tag Category`, and :guilabel:`Name` your tags." msgstr "" #: ../../content/applications/productivity/documents.rst:67 -msgid "An **email alias** can be used to automatically send received documents to a specific workspace based on the tag assigned. To create an email alias:" +msgid "The tags of a parent workspace apply to the child workspaces automatically;" +msgstr "" + +#: ../../content/applications/productivity/documents.rst:68 +msgid "Tags can be created and modified by going to :menuselection:`Documents --> Configuration --> Tags`;" msgstr "" #: ../../content/applications/productivity/documents.rst:70 -msgid "Select the tag and the corresponding workspace where the document should be directed in the left column of your dashboard." +msgid "Tags can also be created or edited by clicking the :icon:`fa-gear` (:guilabel:`gear`) icon on the left panel;" msgstr "" -#: ../../content/applications/productivity/documents.rst:73 -msgid "Next to the :guilabel:`Upload` button, click the down arrow, and then click :guilabel:`Share`." +#: ../../content/applications/productivity/documents.rst:72 +msgid "An :ref:`email alias ` can be used to automatically send received documents to a specific workspace based on the tag assigned." msgstr "" -#: ../../content/applications/productivity/documents.rst:75 -msgid "In the new window, click :guilabel:`Download and Upload` and enter the email alias where documents should be sent." -msgstr "" - -#: ../../content/applications/productivity/documents.rst:79 +#: ../../content/applications/productivity/documents.rst:78 msgid "Access rights" msgstr "" -#: ../../content/applications/productivity/documents.rst:81 -msgid "To manage your workspace access rights, go to :menuselection:`Documents --> Configuration --> Workspaces`, open the workspace you want to edit, and go to the :guilabel:`Access Rights` tab. You can add :guilabel:`Write Groups` that can view, create, and edit the workspace's documents. You can also add :guilabel:`Read Groups` that can only view the workspace's documents." +#: ../../content/applications/productivity/documents.rst:80 +msgid "To manage your workspace access rights, go to the :guilabel:`Access Rights` tab. You can add :guilabel:`Write Groups` that can view, create, and edit the workspace's documents. You can also add :guilabel:`Read Groups` that only view the workspace's documents." msgstr "" -#: ../../content/applications/productivity/documents.rst:87 -msgid "Description" +#: ../../content/applications/productivity/documents.rst:85 +msgid "Enable :guilabel:`Own Documents Only` to limit :guilabel:`Read Groups` and :guilabel:`Write Groups` to the documents of which they are owner." msgstr "" -#: ../../content/applications/productivity/documents.rst:89 -msgid "You can add descriptive information to your workspace by going to :menuselection:`Documents --> Configuration --> Workspaces`, opening the workspace you want to describe and going to the :guilabel:`Description` tab." +#: ../../content/applications/productivity/documents.rst:93 +msgid "You can add descriptive information to your workspace by going to the :guilabel:`Description` tab." msgstr "" -#: ../../content/applications/productivity/documents.rst:94 -msgid "Workspaces can also be created and edited by clicking the gear icon :guilabel:`⚙` on the left menu." +#: ../../content/applications/productivity/documents.rst:96 +msgid "Workspaces can also be created and edited by clicking the :icon:`fa-gear` (:guilabel:`gear`) icon on the left panel." msgstr "" -#: ../../content/applications/productivity/documents.rst:0 -msgid "Create sub-workspaces from the left menu" -msgstr "" - -#: ../../content/applications/productivity/documents.rst:101 +#: ../../content/applications/productivity/documents.rst:102 msgid "Documents management" msgstr "" -#: ../../content/applications/productivity/documents.rst:103 -msgid "When selecting or opening a document, the right panel displays different options. On the top, additional options might be available: :guilabel:`Download`, :guilabel:`Share`, :guilabel:`Replace`, :guilabel:`Lock` or :guilabel:`Split`. It is also possible to :guilabel:`Open chatter` or use the :guilabel:`Move to trash` option." +#: ../../content/applications/productivity/documents.rst:104 +msgid "When selecting or opening a document, the right panel displays different options, including, for example:" msgstr "" -#: ../../content/applications/productivity/documents.rst:-1 -msgid "right panel options" +#: ../../content/applications/productivity/documents.rst:107 +msgid ":icon:`fa-download` (:guilabel:`Download`);" +msgstr "" + +#: ../../content/applications/productivity/documents.rst:108 +msgid ":icon:`fa-share-alt` (:guilabel:`Share this selection`): a share URL is copied to your clipboard;" +msgstr "" + +#: ../../content/applications/productivity/documents.rst:109 +msgid ":icon:`fa-retweet` (:guilabel:`Replace`): select a new file to replace the existing one. Scroll down to the bottom of the right panel to see the :guilabel:`History` and :guilabel:`restore`, :guilabel:`download`, or :guilabel:`delete` the document;" msgstr "" #: ../../content/applications/productivity/documents.rst:112 -msgid "Then, you can modify the name of your file by clicking on :guilabel:`Name`. A :guilabel:`Contact` or an :guilabel:`Owner` can be assigned. The related :guilabel:`Workspace` can be modified and it is possible to access the related :guilabel:`Journal Entry` or add :guilabel:`Tags`." +msgid ":icon:`fa-unlock` (:guilabel:`Lock`);" msgstr "" -#: ../../content/applications/productivity/documents.rst:117 -msgid "The :guilabel:`Contact` is the person related to the document and assigned to it. He can only view the document and not modify it. I.e.: an existing supplier in your database is the contact for their bill." +#: ../../content/applications/productivity/documents.rst:113 +msgid ":icon:`fa-scissors` (:ref:`Split `)." msgstr "" -#: ../../content/applications/productivity/documents.rst:120 -msgid "The person who creates a document is, by default :guilabel:`Owner` of it and has complete rights to it. It is possible to replace the owner of a document. I.e., an employee must be owner of a document to be able to see it in \"My Profile\"." +#: ../../content/applications/productivity/documents.rst:115 +msgid "You can also :icon:`fa-comments` :guilabel:`Open chatter` or delete the document by clicking the :icon:`fa-trash` (:guilabel:`Move to trash`) icon." msgstr "" -#: ../../content/applications/productivity/documents.rst:124 +#: ../../content/applications/productivity/documents.rst:119 +msgid "Items moved to the trash are permanently deleted after 30 days." +msgstr "" + +#: ../../content/applications/productivity/documents.rst:121 +msgid "To modify the name of your file, click on :guilabel:`Name`. A :guilabel:`Contact` or an :guilabel:`Owner` can be assigned. The related :guilabel:`Workspace` can be modified and it is possible to access the related :guilabel:`Journal Entry` or add :guilabel:`Tags`." +msgstr "" + +#: ../../content/applications/productivity/documents.rst:126 +msgid "The :guilabel:`Contact` is a person related to the document who only has read :ref:`access rights ` to the document, e.g., an existing supplier in your database;" +msgstr "" + +#: ../../content/applications/productivity/documents.rst:129 +msgid "The creator of a document is automatically assigned as its :guilabel:`Owner` and is granted full access rights to it. To replace the owner of a document, select the required user from the dropdown list in the :guilabel:`Owner` field." +msgstr "" + +#: ../../content/applications/productivity/documents.rst:134 +msgid "An employee must be a user and the owner of a document to view it in **My Profile**." +msgstr "" + +#: ../../content/applications/productivity/documents.rst:136 msgid "Different :ref:`Actions ` are available at the bottom of the right panel, depending on the workspace where your document is stored." msgstr "" -#: ../../content/applications/productivity/documents.rst:128 +#: ../../content/applications/productivity/documents.rst:142 msgid "Split PDF documents" msgstr "" -#: ../../content/applications/productivity/documents.rst:130 -msgid "Select the PDF you want to split, and click the scissors icon. A new view displays all the pages of the document." +#: ../../content/applications/productivity/documents.rst:144 +msgid "Select the PDF you want to split, and click the :icon:`fa-scissors` (:guilabel:`scissors`) icon. A new view displays all the pages of the document." msgstr "" -#: ../../content/applications/productivity/documents.rst:133 -msgid "By default, each page of the document will be split when clicking :guilabel:`Split`. To remove a split between two pages, click on the scissors icon." +#: ../../content/applications/productivity/documents.rst:147 +msgid "By default, all pages are split when you click :guilabel:`Split`. To remove a split between two pages, click the :icon:`fa-scissors` (:guilabel:`scissors`) icon." msgstr "" #: ../../content/applications/productivity/documents.rst:-1 msgid "split your documents" msgstr "" -#: ../../content/applications/productivity/documents.rst:140 -msgid "To merge documents from your dashboard, select them and click the scissors icon. Click on the scissors between the two documents and click :guilabel:`Split` to merge the documents." +#: ../../content/applications/productivity/documents.rst:154 +msgid "To merge documents from your dashboard, select them and click the :icon:`fa-scissors` (:guilabel:`scissors`) icon. Click on the scissors between the two documents and click :guilabel:`Split` to merge the documents." msgstr "" -#: ../../content/applications/productivity/documents.rst:144 +#: ../../content/applications/productivity/documents.rst:159 msgid "Additional features" msgstr "" -#: ../../content/applications/productivity/documents.rst:146 -msgid "Select a workspace and click the arrow next to the :guilabel:`Upload` button to access additional features:" +#: ../../content/applications/productivity/documents.rst:161 +msgid "Select a workspace and click the :icon:`fa-caret-down` (:guilabel:`down arrow`) next to the :guilabel:`Upload` button to access additional features:" msgstr "" -#: ../../content/applications/productivity/documents.rst:150 +#: ../../content/applications/productivity/documents.rst:165 msgid "Request" msgstr "" -#: ../../content/applications/productivity/documents.rst:152 -msgid "You can create \"missing documents\" and organize them as documents, to remind users to download them." +#: ../../content/applications/productivity/documents.rst:167 +msgid "You can request files and organize them as documents to remind users to download them." msgstr "" -#: ../../content/applications/productivity/documents.rst:154 -msgid "Select the workspace where the file should be stored, click :guilabel:`Upload`, then :guilabel:`Request`. Add the :guilabel:`Document Name`, select the person you need it from in the :guilabel:`Request To` field, fill in the :guilabel:`Due Date In`, confirm the :guilabel:`Workspace`, the document should belong to, and add :guilabel:`Tags` and a :guilabel:`Note`, if needed. Then, click :guilabel:`Request`. A placeholder for the missing document is created in the workspace." +#: ../../content/applications/productivity/documents.rst:169 +msgid "Select the workspace where the file should be stored, click the :icon:`fa-caret-down` (:guilabel:`down arrow`) next to the :guilabel:`Upload` button, then :guilabel:`Request`. Add the :guilabel:`Document Name` and select the person you need it from in the :guilabel:`Request To` field. You can also fill in the :guilabel:`Due Date In`, confirm the :guilabel:`Workspace` the document should belong to, and add :guilabel:`Tags` and a :guilabel:`Message`. Then, click :guilabel:`Request`. A placeholder for the missing document is created in the workspace." msgstr "" -#: ../../content/applications/productivity/documents.rst:161 +#: ../../content/applications/productivity/documents.rst:176 msgid "When your document is available, click the placeholder to upload it." msgstr "" -#: ../../content/applications/productivity/documents.rst:163 -msgid "You can see all missing documents by going to the **Activity** view and to the :guilabel:`Requested Document` column." +#: ../../content/applications/productivity/documents.rst:178 +msgid "You can see all missing documents by going to the **Activity** view and the :guilabel:`Requested Document` column." msgstr "" -#: ../../content/applications/productivity/documents.rst:167 -msgid "From the :guilabel:`Activity` view, you can send a **reminder email** to users from whom you are expecting a document. Go to the :guilabel:`Requested Document` column, click on ⋮ and :guilabel:`Document Request: Reminder`." -msgstr "" - -#: ../../content/applications/productivity/documents.rst:171 -msgid "Click on a date to see the details of a specific request. You can update it by clicking on the pen icon, :guilabel:`Preview` the content of the reminder email, or :guilabel:`Send Now` to send a reminder email." +#: ../../content/applications/productivity/documents.rst:182 +msgid "From the :guilabel:`Activity` view, you can send a **reminder email** to users from whom you are expecting a document. Go to the :guilabel:`Requested Document` column and click the :icon:`fa-ellipsis-v` (:guilabel:`ellipsis`) icon, and :guilabel:`Document Request: Reminder`. Click on a date to see the details of a specific request. You can update it by clicking on the :icon:`fa-pencil` (:guilabel:`pen`) icon, :guilabel:`Preview` the content of the reminder email, or :guilabel:`Send Now` to send a reminder email." msgstr "" #: ../../content/applications/productivity/documents.rst:0 msgid "send a reminder email from the Activity view" msgstr "" -#: ../../content/applications/productivity/documents.rst:179 +#: ../../content/applications/productivity/documents.rst:195 msgid "Add a link" msgstr "" -#: ../../content/applications/productivity/documents.rst:181 -msgid "To add a link to your documents dashboard, click on :guilabel:`Add a Link`, enter the :guilabel:`URL`, and :guilabel:`Name` it." +#: ../../content/applications/productivity/documents.rst:197 +msgid "To add a link to your documents dashboard, click :guilabel:`Add a Link`, enter the :guilabel:`URL`, and :guilabel:`Name` it." msgstr "" -#: ../../content/applications/productivity/documents.rst:185 +#: ../../content/applications/productivity/documents.rst:201 msgid "Share" msgstr "" -#: ../../content/applications/productivity/documents.rst:187 -msgid "You can create a share link to a document or all documents of a workspace. It allows anyone to download the file(s) or upload files to a workspace." +#: ../../content/applications/productivity/documents.rst:203 +msgid "You can make a document or a workspace accessible to anyone by sharing a URL." msgstr "" -#: ../../content/applications/productivity/documents.rst:190 -msgid "To do so, select the workspace or the document and click the arrow next to the :guilabel:`Upload` button then :guilabel:`Share`. On the pop-up, the share :guilabel:`URL` is displayed. :guilabel:`Copy` it to share it with anyone. :guilabel:`Name` the share link and set a validity date for the URL by filling in the :guilabel:`Valid Until` field. Tick the :guilabel:`Include Sub Folders` box if you also want to share a workspace's sub-folders. To let users upload their own documents, select :guilabel:`Download and Upload`." +#: ../../content/applications/productivity/documents.rst:206 +msgid "Share a document" msgstr "" -#: ../../content/applications/productivity/documents.rst:198 -msgid "It is possible to only share one or more documents (without their workspace) by selecting them and clicking :guilabel:`Share`." +#: ../../content/applications/productivity/documents.rst:208 +msgid "To generate a **share link** to a document, select the document, click the :icon:`fa-caret-down` (:guilabel:`down arrow`) next to the :guilabel:`Upload` button, and click :guilabel:`Share`." msgstr "" -#: ../../content/applications/productivity/documents.rst:202 +#: ../../content/applications/productivity/documents.rst:211 +msgid "In the pop-up, you can :guilabel:`Name` the share link, set a validity date by filling in the :guilabel:`Valid Until` field, and if you own more than one site, select the :guilabel:`Website` you want so the right domain name is reflected in the URL." +msgstr "" + +#: ../../content/applications/productivity/documents.rst:215 +msgid "Click :guilabel:`Copy` or :guilabel:`Share` to send the URL to whomever you want." +msgstr "" + +#: ../../content/applications/productivity/documents.rst:218 +msgid "You can also generate a share URL by selecting the document, going to the right panel, and clicking the :icon:`fa-share-alt` (:guilabel:`Share this selection`) icon." +msgstr "" + +#: ../../content/applications/productivity/documents.rst:222 +msgid "Share a workspace" +msgstr "" + +#: ../../content/applications/productivity/documents.rst:224 +msgid "You can share a link to a workspace and allow users to :guilabel:`Download` its content or :guilabel:`Download and Upload` files to it." +msgstr "" + +#: ../../content/applications/productivity/documents.rst:227 +msgid "To do so, go to the left column of your dashboard. In the :guilabel:`Workspace` section, select the workspace to share, and possibly one or several tags that will be automatically added to the uploaded documents. Then, click the :icon:`fa-caret-down` (:guilabel:`down arrow`) next to the :guilabel:`Upload` button and :guilabel:`Share`." +msgstr "" + +#: ../../content/applications/productivity/documents.rst:232 +msgid "In the pop-up, a share :guilabel:`URL` you can :guilabel:`Copy` is displayed. You can :guilabel:`Name` your share link, set a validity date by filling in the :guilabel:`Valid Until` field, tick the :guilabel:`Include Sub Folders` box if you want to share the workspace's sub-folders, and if you own more than one site, select the :guilabel:`Website` you want so the share link reflects the right domain name." +msgstr "" + +#: ../../content/applications/productivity/documents.rst:238 +msgid "Then, allow users to either :guilabel:`Download` files from your workspace, or to :ref:`Download and Upload ` files to it." +msgstr "" + +#: ../../content/applications/productivity/documents.rst:242 +msgid "The links added to your workspace using the :ref:`Add a Link ` option cannot be shared and are, therefore, excluded;" +msgstr "" + +#: ../../content/applications/productivity/documents.rst:244 +msgid "When tags are applied to a shared workspace, users can exclusively access the documents associated with those tags." +msgstr "" + +#: ../../content/applications/productivity/documents.rst:250 +msgid "Upload by email" +msgstr "" + +#: ../../content/applications/productivity/documents.rst:252 +msgid "Select the :guilabel:`Download and Upload` option to enable users to upload their files to your workspace using an :guilabel:`Email Alias`. To create the email alias, enter its name in the :guilabel:`Email Alias` field. The :doc:`domain name <../general/email_communication/email_servers>` should be set by default, but you can modify it by clicking it." +msgstr "" + +#: ../../content/applications/productivity/documents.rst:257 +msgid "The documents sent to this email alias are uploaded to the workspace using the chosen :ref:`tags `." +msgstr "" + +#: ../../content/applications/productivity/documents.rst:261 +msgid "By default, the :guilabel:`Document Owner` is the person who uploads a file to a workspace, but you can select another user. You can also set a :guilabel:`Contact`, usually an external person, such as a partner." +msgstr "" + +#: ../../content/applications/productivity/documents.rst:264 +msgid "Enable :guilabel:`Create a new activity` to automatically create an activity when a document is uploaded. Select the :guilabel:`Activity type` from the dropdown list and set the :guilabel:`Due Date In` field. You can also add a :guilabel:`Summary` and a :guilabel:`Responsible` person assigned to the activity." +msgstr "" + +#: ../../content/applications/productivity/documents.rst:270 +msgid "Go to :menuselection:`Configuration --> Share & Emails` to see and manage your share links. Select a line and click :guilabel:`Delete` to disable the URL. People who have received this link will no longer be able to access the document(s) or workspace." +msgstr "" + +#: ../../content/applications/productivity/documents.rst:275 msgid "New spreadsheet" msgstr "" -#: ../../content/applications/productivity/documents.rst:204 +#: ../../content/applications/productivity/documents.rst:277 msgid "To create a new :doc:`spreadsheet `, click :guilabel:`New Spreadsheet`. You can select a :guilabel:`Blank spreadsheet` or an :doc:`existing template `." msgstr "" -#: ../../content/applications/productivity/documents.rst:210 +#: ../../content/applications/productivity/documents.rst:283 msgid "Workflow actions" msgstr "" -#: ../../content/applications/productivity/documents.rst:212 -msgid "Workflow actions help manage documents and overall business operations. These are automated actions that can be created and customized for each workspace. With a single click you can, for example, create, move, sign, and add tags to a document, and process bills." +#: ../../content/applications/productivity/documents.rst:285 +msgid "Workflow actions help manage documents and overall business operations. These are automated actions that can be created and customized for each workspace. With a single click you can, for example, create, move, sign, add tags to a document, and process bills." msgstr "" -#: ../../content/applications/productivity/documents.rst:216 -msgid "These workflow actions appear on the right panel when a document meets the set criteria." +#: ../../content/applications/productivity/documents.rst:289 +msgid "When a document meets the set criteria, these workflow actions appear on the right panel." msgstr "" -#: ../../content/applications/productivity/documents.rst:219 +#: ../../content/applications/productivity/documents.rst:292 msgid "Create workflow actions" msgstr "" -#: ../../content/applications/productivity/documents.rst:221 -msgid "To create workflow actions, go to :menuselection:`Documents --> Configuration --> Actions` and click :guilabel:`New`." +#: ../../content/applications/productivity/documents.rst:294 +msgid "To update an existing workflow action or create a new one, go to :menuselection:`Documents --> Configuration --> Actions` and click :guilabel:`New`." msgstr "" -#: ../../content/applications/productivity/documents.rst:225 +#: ../../content/applications/productivity/documents.rst:298 msgid "An action applies to all **sub-workspaces** under the :guilabel:`Related Workspace` you selected." msgstr "" -#: ../../content/applications/productivity/documents.rst:228 +#: ../../content/applications/productivity/documents.rst:301 msgid "Set the conditions" msgstr "" -#: ../../content/applications/productivity/documents.rst:230 -msgid "You can :guilabel:`Create` a new :guilabel:`Action` or edit an existing one. You can define the :guilabel:`Action Name` and then set the conditions that trigger the appearance of the action button (:guilabel:`▶`) on the right-side panel when selecting a file." +#: ../../content/applications/productivity/documents.rst:303 +msgid "Define the :guilabel:`Action Name` and then set the conditions that trigger the appearance of the :icon:`fa-play` (:guilabel:`play`) icon on the right-side panel when selecting a file." msgstr "" -#: ../../content/applications/productivity/documents.rst:234 +#: ../../content/applications/productivity/documents.rst:306 msgid "There are three basic types of conditions you can set:" msgstr "" -#: ../../content/applications/productivity/documents.rst:236 -msgid ":guilabel:`Tags`: you can use the :guilabel:`Contains` and :guilabel:`Does not contain` conditions, meaning the files *must have* or *must not have* the tags set here." +#: ../../content/applications/productivity/documents.rst:308 +msgid ":guilabel:`Tags`: you can use the :guilabel:`Contains` and :guilabel:`Does not contain` conditions, meaning the files *must have* or *must not have* the tags set here;" msgstr "" -#: ../../content/applications/productivity/documents.rst:239 -msgid ":guilabel:`Contact`: the files must be associated with the contact set here." +#: ../../content/applications/productivity/documents.rst:311 +msgid ":guilabel:`Contact`: the files must be associated with the contact set here;" msgstr "" -#: ../../content/applications/productivity/documents.rst:241 +#: ../../content/applications/productivity/documents.rst:313 msgid ":guilabel:`Owner`: the files must be associated with the owner set here." msgstr "" @@ -1748,23 +2180,23 @@ msgstr "" msgid "Example of a workflow action's basic condition in Odoo Documents" msgstr "" -#: ../../content/applications/productivity/documents.rst:247 +#: ../../content/applications/productivity/documents.rst:319 msgid "If you do not set any conditions, the action button appears for all files inside the selected workspace." msgstr "" -#: ../../content/applications/productivity/documents.rst:251 +#: ../../content/applications/productivity/documents.rst:323 msgid "Advanced condition type: domain" msgstr "" -#: ../../content/applications/productivity/documents.rst:254 +#: ../../content/applications/productivity/documents.rst:326 msgid "It is recommended to have some knowledge of Odoo development to configure *Domain* filters properly." msgstr "" -#: ../../content/applications/productivity/documents.rst:257 -msgid "The :ref:`developer mode ` needs to be activated to access the :guilabel:`Domain` condition from the :guilabel:`Actions` tab. Once done, select the :guilabel:`Domain` condition type and click :guilabel:`Add condition`." +#: ../../content/applications/productivity/documents.rst:329 +msgid "The :ref:`developer mode ` needs to be activated to access the :guilabel:`Domain` condition from the :guilabel:`Actions` tab. Once done, select the :guilabel:`Domain` condition type and click :guilabel:`New Rule`." msgstr "" -#: ../../content/applications/productivity/documents.rst:261 +#: ../../content/applications/productivity/documents.rst:333 msgid "To create a rule, you typically select a :guilabel:`field`, an :guilabel:`operator`, and a :guilabel:`value`. For example, if you want to add a workflow action to all the PDF files inside a workspace, set the :guilabel:`field` to *Mime Type*, the :guilabel:`operator` to *contains*, and the pdf :guilabel:`value`." msgstr "" @@ -1772,95 +2204,99 @@ msgstr "" msgid "Example of a workflow action's domain condition in Odoo Documents" msgstr "" -#: ../../content/applications/productivity/documents.rst:269 -msgid "Click :guilabel:`Add New Rule` (plus icon) and :guilabel:`Add branch` to add conditions and sub-conditions. You can then specify if your rule should match :guilabel:`all` or :guilabel:`any` conditions. You can also edit the rule directly using the :guilabel:`Code editor`." +#: ../../content/applications/productivity/documents.rst:341 +msgid "Click the :icon:`fa-plus` (:guilabel:`Add New Rule`) icon and the :icon:`fa-sitemap` (:guilabel:`Add branch`) icon to add conditions and sub-conditions. You can then specify if your rule should match :guilabel:`all` or :guilabel:`any` conditions. You can also edit the rule directly using the :guilabel:`Code editor`." msgstr "" -#: ../../content/applications/productivity/documents.rst:274 +#: ../../content/applications/productivity/documents.rst:347 msgid "Configure the actions" msgstr "" -#: ../../content/applications/productivity/documents.rst:276 +#: ../../content/applications/productivity/documents.rst:349 msgid "Select the :guilabel:`Actions` tab to set up your action. You can simultaneously:" msgstr "" -#: ../../content/applications/productivity/documents.rst:278 -msgid "**Set Contact**: add a contact to the file, or replace an existing contact with a new one." +#: ../../content/applications/productivity/documents.rst:351 +msgid "**Move to Workspace**: move the file to any workspace;" msgstr "" -#: ../../content/applications/productivity/documents.rst:279 -msgid "**Set Owner**: add an owner to the file, or replace an existing owner with a new one." -msgstr "" - -#: ../../content/applications/productivity/documents.rst:280 -msgid "**Move to Workspace**: move the file to any workspace." -msgstr "" - -#: ../../content/applications/productivity/documents.rst:281 +#: ../../content/applications/productivity/documents.rst:352 msgid "**Create**: create one of the following items attached to the file in your database:" msgstr "" -#: ../../content/applications/productivity/documents.rst:283 -msgid "**Link to record**: link the document to a record (i.e. link to a vehicle in Fleet);" +#: ../../content/applications/productivity/documents.rst:354 +msgid "**Link to record**: create a link between a document and a record from a specific model;" msgstr "" -#: ../../content/applications/productivity/documents.rst:284 +#: ../../content/applications/productivity/documents.rst:355 msgid "**Product template**: create a product you can edit directly;" msgstr "" -#: ../../content/applications/productivity/documents.rst:285 +#: ../../content/applications/productivity/documents.rst:356 msgid "**Task**: create a Project task you can edit directly;" msgstr "" -#: ../../content/applications/productivity/documents.rst:286 +#: ../../content/applications/productivity/documents.rst:357 msgid "**Signature PDF template**: create a new Sign template to send out;" msgstr "" -#: ../../content/applications/productivity/documents.rst:287 -msgid "**PDF to sign**: create a PDF to sign;" +#: ../../content/applications/productivity/documents.rst:358 +msgid "**PDF to sign**: create a Sign template to sign directly;" msgstr "" -#: ../../content/applications/productivity/documents.rst:288 +#: ../../content/applications/productivity/documents.rst:359 msgid "**Applicant**: create a new HR application you can edit directly;" msgstr "" -#: ../../content/applications/productivity/documents.rst:289 +#: ../../content/applications/productivity/documents.rst:360 msgid "**Vendor bill**: create a vendor bill using OCR and AI to scrape information from the file content;" msgstr "" -#: ../../content/applications/productivity/documents.rst:291 -msgid "**Customer invoice**: create a customer invoice using OCR and AI to scrape information from the file;" +#: ../../content/applications/productivity/documents.rst:362 +msgid "**Customer invoice**: create an invoice using OCR and AI to scrape information from the file;" msgstr "" -#: ../../content/applications/productivity/documents.rst:293 +#: ../../content/applications/productivity/documents.rst:363 msgid "**Vendor credit note**: create a vendor credit note using OCR and AI to scrape information from the file;" msgstr "" -#: ../../content/applications/productivity/documents.rst:295 +#: ../../content/applications/productivity/documents.rst:365 msgid "**Credit note**: create a customer credit note using OCR and AI to scrape information from the file;" msgstr "" -#: ../../content/applications/productivity/documents.rst:297 -msgid "**Miscellaneous Operations**: create a record in :guilabel:`Miscellaneous Operations` in Accounting;" +#: ../../content/applications/productivity/documents.rst:367 +msgid "**Miscellaneous Operations**: create an entry in the Miscellaneous Operations journal;" msgstr "" -#: ../../content/applications/productivity/documents.rst:299 -msgid "**Bank Statement**: create a Bank Statement in Finance;" +#: ../../content/applications/productivity/documents.rst:368 +msgid "**Bank Statement**: import a bank statement;" msgstr "" -#: ../../content/applications/productivity/documents.rst:300 -msgid "**Expense**: create an expense automatically based on a file's content." +#: ../../content/applications/productivity/documents.rst:369 +msgid "**Purchase Receipt**: create a vendor receipt;" msgstr "" -#: ../../content/applications/productivity/documents.rst:302 +#: ../../content/applications/productivity/documents.rst:370 +msgid "**Expense**: create an HR expense." +msgstr "" + +#: ../../content/applications/productivity/documents.rst:372 +msgid "**Set Contact**: add a contact to the file, or replace an existing contact with a new one;" +msgstr "" + +#: ../../content/applications/productivity/documents.rst:373 +msgid "**Set Owner**: add an owner to the file, or replace an existing owner with a new one;" +msgstr "" + +#: ../../content/applications/productivity/documents.rst:374 msgid "**Set Tags**: add, remove, and replace any number of tags;" msgstr "" -#: ../../content/applications/productivity/documents.rst:303 +#: ../../content/applications/productivity/documents.rst:375 msgid "**Activities - Mark all as Done**: mark all activities linked to the file as done;" msgstr "" -#: ../../content/applications/productivity/documents.rst:304 +#: ../../content/applications/productivity/documents.rst:376 msgid "**Activities - Schedule Activity**: create a new activity linked to the file as configured in the action. You can choose to set the activity on the document owner." msgstr "" @@ -1868,15 +2304,15 @@ msgstr "" msgid "Example of a workflow action Odoo Documents" msgstr "" -#: ../../content/applications/productivity/documents.rst:311 +#: ../../content/applications/productivity/documents.rst:383 msgid "Digitize documents with AI and optical character recognition (OCR)" msgstr "" -#: ../../content/applications/productivity/documents.rst:313 +#: ../../content/applications/productivity/documents.rst:385 msgid "Documents available in the Finance workspace can be digitized. Select the document to digitize, click :guilabel:`Create Bill`, :guilabel:`Create Customer Invoice`, or :guilabel:`Create credit note`, and then click :guilabel:`Send for Digitization`." msgstr "" -#: ../../content/applications/productivity/documents.rst:318 +#: ../../content/applications/productivity/documents.rst:390 msgid ":doc:`AI-powered document digitization <../finance/accounting/vendor_bills/invoice_digitization>`" msgstr "" @@ -2682,98 +3118,142 @@ msgid "Documents signed via the Sign app are valid electronic signatures in the msgstr "" #: ../../content/applications/productivity/sign.rst:28 +msgid "The below information has no legal value; it is only provided for general informational purposes. As laws governing electronic signatures rapidly evolve, we cannot guarantee that all information is up-to-date. We advise contacting a local attorney for legal advice regarding electronic signature compliance and validity." +msgstr "" + +#: ../../content/applications/productivity/sign.rst:34 msgid "European Union" msgstr "" -#: ../../content/applications/productivity/sign.rst:30 +#: ../../content/applications/productivity/sign.rst:36 msgid "The `eIDAS regulation `_ establishes the framework for electronic signatures in the `27 member states of the European Union `_. It distinguishes three types of electronic signatures:" msgstr "" -#: ../../content/applications/productivity/sign.rst:35 +#: ../../content/applications/productivity/sign.rst:41 msgid "Simple electronic signatures" msgstr "" -#: ../../content/applications/productivity/sign.rst:36 +#: ../../content/applications/productivity/sign.rst:42 msgid "Advanced electronic signatures" msgstr "" -#: ../../content/applications/productivity/sign.rst:37 +#: ../../content/applications/productivity/sign.rst:43 msgid "Qualified electronic signatures" msgstr "" -#: ../../content/applications/productivity/sign.rst:39 +#: ../../content/applications/productivity/sign.rst:45 msgid "Odoo generates the first type, **simple electronic signatures**; these signatures are legally valid in the EU, as stated in the eIDAS regulation." msgstr "" -#: ../../content/applications/productivity/sign.rst:42 +#: ../../content/applications/productivity/sign.rst:48 msgid "Electronic signatures may not be automatically recognized as valid. You may need to bring supporting evidence of a signature's validity. While the Sign app provides a simple electronic signature, some supporting evidence is automatically collected during the signature process, such as:" msgstr "" -#: ../../content/applications/productivity/sign.rst:47 +#: ../../content/applications/productivity/sign.rst:53 msgid "Email and SMS validation (if enabled)" msgstr "" -#: ../../content/applications/productivity/sign.rst:48 +#: ../../content/applications/productivity/sign.rst:54 msgid "Strong identity proof through itsme® (available in Belgium and the Netherlands)" msgstr "" -#: ../../content/applications/productivity/sign.rst:49 +#: ../../content/applications/productivity/sign.rst:55 msgid "Timestamped, IP and geographically traceable access logs to the documents and their associated signatures" msgstr "" -#: ../../content/applications/productivity/sign.rst:51 +#: ../../content/applications/productivity/sign.rst:57 msgid "Document traceability and inalterability (any alteration made to a signed document is detected by Odoo with the use of cryptographic proofs)" msgstr "" -#: ../../content/applications/productivity/sign.rst:55 +#: ../../content/applications/productivity/sign.rst:61 msgid "United States of America" msgstr "" -#: ../../content/applications/productivity/sign.rst:57 +#: ../../content/applications/productivity/sign.rst:63 msgid "The `ESIGN Act (Electronic Signatures in Global and National Commerce Act) `_, at the interstate and international levels, and the `UETA (Uniform Electronic Transactions Act) `_, at the state level, provide the legal framework for electronic signatures. Note that `Illinois `_ and `New York `_ have not adopted the UETA, but similar acts instead." msgstr "" -#: ../../content/applications/productivity/sign.rst:66 +#: ../../content/applications/productivity/sign.rst:72 msgid "Overall, to be recognized as valid, electronic signatures have to meet five criteria:" msgstr "" -#: ../../content/applications/productivity/sign.rst:68 +#: ../../content/applications/productivity/sign.rst:74 msgid "The signer must show a clear **intent to sign**. For example, using a mouse to draw a signature can show intent. The signer must also have the option to opt out of the electronic document." msgstr "" -#: ../../content/applications/productivity/sign.rst:70 +#: ../../content/applications/productivity/sign.rst:76 msgid "The signer must first express or imply their **consent to conduct business electronically**." msgstr "" -#: ../../content/applications/productivity/sign.rst:71 +#: ../../content/applications/productivity/sign.rst:77 msgid "**The signature must be clearly attributed**. In Odoo, metadata, such as the signer's IP address, is added to the signature, which can be used as supporting evidence." msgstr "" -#: ../../content/applications/productivity/sign.rst:73 +#: ../../content/applications/productivity/sign.rst:79 msgid "**The signature must be associated with the signed document**, for example, by keeping a record detailing how the signature was captured." msgstr "" -#: ../../content/applications/productivity/sign.rst:75 +#: ../../content/applications/productivity/sign.rst:81 msgid "Electronically signed documents need to be **retained and stored** by all parties involved; for example, by providing the signer either a fully-executed copy or the possibility to download a copy." msgstr "" -#: ../../content/applications/productivity/sign.rst:80 -msgid "The above information has no legal value; it is only provided for general informational purposes. As laws governing electronic signatures rapidly evolve, we cannot guarantee that all information is up-to-date. We advise contacting a local attorney for legal advice regarding electronic signature compliance and validity." +#: ../../content/applications/productivity/sign.rst:86 +msgid "Other countries" msgstr "" -#: ../../content/applications/productivity/sign.rst:86 -msgid "Send a document to sign" +#: ../../content/applications/productivity/sign.rst:88 +msgid ":doc:`Australia `" msgstr "" #: ../../content/applications/productivity/sign.rst:89 -msgid "One-time signature" +msgid ":doc:`Brazil `" +msgstr "" + +#: ../../content/applications/productivity/sign.rst:90 +msgid ":doc:`Canada `" msgstr "" #: ../../content/applications/productivity/sign.rst:91 -msgid "You can click :guilabel:`Upload a PDF to sign` from your dashboard for a one-time signature. Select your document, open it, and drag and drop the required :ref:`fields ` in your document. You can modify the :ref:`role ` assigned to a field by clicking on it and selecting the one you want." +msgid ":doc:`China `" +msgstr "" + +#: ../../content/applications/productivity/sign.rst:92 +msgid ":doc:`India `" +msgstr "" + +#: ../../content/applications/productivity/sign.rst:93 +msgid ":doc:`Japan `" +msgstr "" + +#: ../../content/applications/productivity/sign.rst:94 +msgid ":doc:`Mexico `" +msgstr "" + +#: ../../content/applications/productivity/sign.rst:95 +msgid ":doc:`Russia `" msgstr "" #: ../../content/applications/productivity/sign.rst:96 +msgid ":doc:`South Korea `" +msgstr "" + +#: ../../content/applications/productivity/sign.rst:97 +msgid ":doc:`United Kingdom `" +msgstr "" + +#: ../../content/applications/productivity/sign.rst:100 +msgid "Send a document to sign" +msgstr "" + +#: ../../content/applications/productivity/sign.rst:103 +msgid "One-time signature" +msgstr "" + +#: ../../content/applications/productivity/sign.rst:105 +msgid "You can click :guilabel:`Upload a PDF to sign` from your dashboard for a one-time signature. Select your document, open it, and drag and drop the required :ref:`fields ` in your document. You can modify the :ref:`role ` assigned to a field by clicking on it and selecting the one you want." +msgstr "" + +#: ../../content/applications/productivity/sign.rst:110 msgid "When ready, click :guilabel:`Send`, and fill in the required fields. Once sent, your document remains available. Go to :menuselection:`Documents --> All Documents` to see your document and the status of the signatures." msgstr "" @@ -2781,84 +3261,84 @@ msgstr "" msgid "Signature status" msgstr "" -#: ../../content/applications/productivity/sign.rst:104 +#: ../../content/applications/productivity/sign.rst:118 msgid "Validity dates and reminders" msgstr "" -#: ../../content/applications/productivity/sign.rst:106 +#: ../../content/applications/productivity/sign.rst:120 msgid "You can set **validity dates** on limited-duration agreement documents or send **automatic email reminders** to obtain signatures on time. From your dashboard, click :guilabel:`Send` on your document. On the new page, go to the :guilabel:`Options` section and fill in the :guilabel:`Valid Until` and :guilabel:`Reminder` fields." msgstr "" -#: ../../content/applications/productivity/sign.rst:112 +#: ../../content/applications/productivity/sign.rst:126 #: ../../content/applications/productivity/spreadsheet/templates.rst:3 msgid "Templates" msgstr "" -#: ../../content/applications/productivity/sign.rst:114 +#: ../../content/applications/productivity/sign.rst:128 msgid "You can create document templates when you have to send the same document several times. From your dashboard, click :guilabel:`Upload a PDF template`. Select the document and add the required :ref:`fields `. You can modify the :ref:`role ` of a field by clicking on it and selecting the one you want." msgstr "" -#: ../../content/applications/productivity/sign.rst:119 +#: ../../content/applications/productivity/sign.rst:133 msgid "Click :guilabel:`Template Properties` to add :guilabel:`Tags` to your template, define a :guilabel:`Signed Document Workspace`, add :guilabel:`Signed Document Tags`, set a :guilabel:`Redirect Link` that will be available in the signature confirmation message received after the signature, or define :guilabel:`Authorized Users` if you want to restrict the use of your template to specific authorized users or groups." msgstr "" -#: ../../content/applications/productivity/sign.rst:125 +#: ../../content/applications/productivity/sign.rst:139 msgid "Your templates are visible by default on your dashboard. You can click :guilabel:`Send` to quickly send a document template to a signer or :guilabel:`Sign Now` if you are ready to sign your document immediately." msgstr "" -#: ../../content/applications/productivity/sign.rst:130 +#: ../../content/applications/productivity/sign.rst:144 msgid "You can **create a template from a document that was previously sent**. To do so, go to :menuselection:`Documents --> All Documents`. On the document you want to retrieve, click on the the vertical ellipsis (:guilabel:`⋮`), then :guilabel:`Template`. Click on the vertical ellipsis (:guilabel:`⋮`) again, then :guilabel:`Restore`. Your document now appears on your dashboard next to your other templates." msgstr "" -#: ../../content/applications/productivity/sign.rst:139 +#: ../../content/applications/productivity/sign.rst:153 msgid "Roles" msgstr "" -#: ../../content/applications/productivity/sign.rst:141 +#: ../../content/applications/productivity/sign.rst:155 msgid "Each field in a Sign document is related to a role corresponding to a specific person. When a document is being signed, the person assigned to the role must fill in their assigned fields and sign it." msgstr "" -#: ../../content/applications/productivity/sign.rst:145 +#: ../../content/applications/productivity/sign.rst:159 msgid "Roles are available by going to :menuselection:`Sign --> Configuration --> Roles`." msgstr "" -#: ../../content/applications/productivity/sign.rst:147 +#: ../../content/applications/productivity/sign.rst:161 msgid "It is possible to update existing roles or to create new roles by clicking on :guilabel:`New`. Choose a :guilabel:`Role Name`, add an :guilabel:`Extra Authentication Step` to confirm the identity of the signing person, and if the document can be reassigned to another contact, select :guilabel:`Change Authorized` for the role. A :guilabel:`Color` can also be chosen for the role. This color can help understand which roles are responsible for which field when configuring a template." msgstr "" -#: ../../content/applications/productivity/sign.rst:155 +#: ../../content/applications/productivity/sign.rst:169 msgid "Secured identification" msgstr "" -#: ../../content/applications/productivity/sign.rst:157 +#: ../../content/applications/productivity/sign.rst:171 msgid "As the owner of a document, you may request an :guilabel:`Extra Authentication Step` through :ref:`SMS verification ` or via :ref:`Itsme® ` (available in Belgium and the Netherlands). Both authentication options require :ref:`credits `. If you do not have any credits left, the authentication steps will be skipped." msgstr "" -#: ../../content/applications/productivity/sign.rst:163 +#: ../../content/applications/productivity/sign.rst:177 msgid ":doc:`In-App Purchase (IAP) <../essentials/in_app_purchase>`" msgstr "" -#: ../../content/applications/productivity/sign.rst:164 +#: ../../content/applications/productivity/sign.rst:178 msgid ":doc:`SMS pricing and FAQ <../marketing/sms_marketing/pricing/pricing_and_faq>`" msgstr "" -#: ../../content/applications/productivity/sign.rst:169 +#: ../../content/applications/productivity/sign.rst:183 msgid "SMS verification" msgstr "" -#: ../../content/applications/productivity/sign.rst:171 +#: ../../content/applications/productivity/sign.rst:185 msgid "Go to :menuselection:`Sign --> Configuration --> Roles`. Click in the :guilabel:`Extra Authentication Step` column for the role, and select :guilabel:`Unique Code Via SMS`." msgstr "" -#: ../../content/applications/productivity/sign.rst:175 +#: ../../content/applications/productivity/sign.rst:189 msgid "Before being able to send SMS Text Messages, you need to register your phone number. To do so, go to :menuselection:`Sign --> Configuration --> Settings` and click :guilabel:`Buy credits` under :guilabel:`Authenticate by SMS`." msgstr "" -#: ../../content/applications/productivity/sign.rst:179 +#: ../../content/applications/productivity/sign.rst:193 msgid "Go to the document to sign, add the field for which the SMS verification is required, for example, the :guilabel:`Signature` field, and click :guilabel:`Send`. On the new page, select the :guilabel:`customer` and click :guilabel:`Send`." msgstr "" -#: ../../content/applications/productivity/sign.rst:183 +#: ../../content/applications/productivity/sign.rst:197 msgid "The person signing the document fills in the :guilabel:`Signature` field, then :guilabel:`Sign`, and clicks :guilabel:`Validate & Send Completed Document`. A :guilabel:`Final Validation` page pops up where to add their phone number. One-time codes are sent by SMS." msgstr "" @@ -2866,27 +3346,27 @@ msgstr "" msgid "Add a hash to your document" msgstr "" -#: ../../content/applications/productivity/sign.rst:191 +#: ../../content/applications/productivity/sign.rst:205 msgid "This feature is enabled by default." msgstr "" -#: ../../content/applications/productivity/sign.rst:192 +#: ../../content/applications/productivity/sign.rst:206 msgid "As soon as the :guilabel:`Extra Authentication Step` applies to a role, this validation step is requested for any field assigned to this role." msgstr "" -#: ../../content/applications/productivity/sign.rst:198 +#: ../../content/applications/productivity/sign.rst:212 msgid "Itsme®" msgstr "" -#: ../../content/applications/productivity/sign.rst:200 +#: ../../content/applications/productivity/sign.rst:214 msgid "Itsme® authentication can be used to allow signatories to provide their identity using itsme®. This feature is only available in **Belgium** and the **Netherlands**." msgstr "" -#: ../../content/applications/productivity/sign.rst:203 +#: ../../content/applications/productivity/sign.rst:217 msgid "The feature can be enabled in :guilabel:`Sign Settings` and applies automatically to the :guilabel:`Customer (identified with itsme®)` role. To enable it for other roles, go to :menuselection:`Sign --> Configuration --> Roles`. Click in the :guilabel:`Extra Authentication Step` column for the role, and select :guilabel:`Via itsme®`." msgstr "" -#: ../../content/applications/productivity/sign.rst:208 +#: ../../content/applications/productivity/sign.rst:222 msgid "Go to the document that needs to be signed and add the :guilabel:`Signature` field. Switch to any role configured to use the feature, and click :guilabel:`Validate` and :guilabel:`Send`." msgstr "" @@ -2894,19 +3374,19 @@ msgstr "" msgid "select customer identified with itsme®" msgstr "" -#: ../../content/applications/productivity/sign.rst:214 +#: ../../content/applications/productivity/sign.rst:228 msgid "Upon signing the document, the signer completes the :guilabel:`Signature` field and proceeds by clicking on :guilabel:`Validate & Send Completed Document`, triggering a :guilabel:`Final verification` page where authentication via itsme® is required." msgstr "" -#: ../../content/applications/productivity/sign.rst:219 +#: ../../content/applications/productivity/sign.rst:233 msgid "Signatory hash" msgstr "" -#: ../../content/applications/productivity/sign.rst:221 +#: ../../content/applications/productivity/sign.rst:235 msgid "Each time someone signs a document, a **hash** - a unique digital signature of the operation - is generated to ensure traceability, integrity, and inalterability. This process guarantees that any changes made after a signature is affixed can be easily detected, maintaining the document's authenticity and security throughout its lifecycle." msgstr "" -#: ../../content/applications/productivity/sign.rst:226 +#: ../../content/applications/productivity/sign.rst:240 msgid "A visual security frame displaying the beginning of the hash is added to the signatures. Internal users can hide or show it by turning the :guilabel:`Frame` option on or off when signing the document." msgstr "" @@ -2914,103 +3394,103 @@ msgstr "" msgid "Adding the visual security frame to a signature." msgstr "" -#: ../../content/applications/productivity/sign.rst:238 +#: ../../content/applications/productivity/sign.rst:252 msgid "Tags can be used to categorize and organize documents, allowing users to quickly search for and filter documents based on specific criteria." msgstr "" -#: ../../content/applications/productivity/sign.rst:241 +#: ../../content/applications/productivity/sign.rst:255 msgid "You can manage tags by going to :menuselection:`Configuration --> Tags`. To create a tag, click :guilabel:`New`. On the new line, add the :guilabel:`Tag Name` and select a :guilabel:`Color Index` for your tag." msgstr "" -#: ../../content/applications/productivity/sign.rst:245 +#: ../../content/applications/productivity/sign.rst:259 msgid "To apply a tag to a document, use the dropdown list available in your document." msgstr "" -#: ../../content/applications/productivity/sign.rst:248 +#: ../../content/applications/productivity/sign.rst:262 msgid "You can modify the tags of a signed document by going to :menuselection:`Documents --> All Documents`, clicking the vertical ellipsis (:guilabel:`⋮`) on your document, then :guilabel:`Details`, and modifying your :guilabel:`Tags`." msgstr "" -#: ../../content/applications/productivity/sign.rst:253 +#: ../../content/applications/productivity/sign.rst:267 msgid "Sign order" msgstr "" -#: ../../content/applications/productivity/sign.rst:255 +#: ../../content/applications/productivity/sign.rst:269 msgid "When a document needs to be signed by different parties, the signing order lets you control the order in which your recipients receive it for signature." msgstr "" -#: ../../content/applications/productivity/sign.rst:258 +#: ../../content/applications/productivity/sign.rst:272 msgid "After uploading a PDF with at least two signature fields with two different roles and clicking :guilabel:`Send`, toggle the :guilabel:`Specify Signing Order` button and search for the signer's name or email information to add them. You can decide on the signing order by typing **1** or **2** in the first column." msgstr "" -#: ../../content/applications/productivity/sign.rst:263 +#: ../../content/applications/productivity/sign.rst:277 msgid "Each recipient receives the signature request notification only once the previous recipient has completed their action." msgstr "" -#: ../../content/applications/productivity/sign.rst:267 +#: ../../content/applications/productivity/sign.rst:281 msgid "`Odoo Quick Tips: Sign order [video] `_" msgstr "" -#: ../../content/applications/productivity/sign.rst:272 +#: ../../content/applications/productivity/sign.rst:286 msgid "Field types" msgstr "" -#: ../../content/applications/productivity/sign.rst:274 +#: ../../content/applications/productivity/sign.rst:288 msgid "Fields are used in a document to indicate what information must be completed by the signers. You can add fields to your document simply by dragging and dropping them for the left column into your document." msgstr "" -#: ../../content/applications/productivity/sign.rst:278 +#: ../../content/applications/productivity/sign.rst:292 msgid "Various field types can be used to sign documents (placeholder, autocompletion, etc.). By configuring your own field types, also known as signature item types, the signing process can be even faster for your customers, partners, and employees." msgstr "" -#: ../../content/applications/productivity/sign.rst:282 +#: ../../content/applications/productivity/sign.rst:296 msgid "To create and edit field types, go to :menuselection:`Sign --> Configuration --> Settings --> Edit field types`." msgstr "" -#: ../../content/applications/productivity/sign.rst:285 +#: ../../content/applications/productivity/sign.rst:299 msgid "You can select an existing field by clicking on it, or you can :guilabel:`Create` a new one. First, edit the :guilabel:`Field Name`. Then, select a :guilabel:`Field Type`:" msgstr "" -#: ../../content/applications/productivity/sign.rst:288 +#: ../../content/applications/productivity/sign.rst:302 msgid ":guilabel:`Signature`: users are asked to enter their signature either by drawing it, generating an automatic one based on their name, or uploading a local file (usually an image). Each subsequent :guilabel:`Signature` field type then reuses the data entered in the first field." msgstr "" -#: ../../content/applications/productivity/sign.rst:291 +#: ../../content/applications/productivity/sign.rst:305 msgid ":guilabel:`Initial`: users are asked to enter their initials, in a similar way to the :guilabel:`Signature` field." msgstr "" -#: ../../content/applications/productivity/sign.rst:293 +#: ../../content/applications/productivity/sign.rst:307 msgid ":guilabel:`Text`: users enter text on a single line." msgstr "" -#: ../../content/applications/productivity/sign.rst:294 +#: ../../content/applications/productivity/sign.rst:308 msgid ":guilabel:`Multiline Text`: users enter text on multiple lines." msgstr "" -#: ../../content/applications/productivity/sign.rst:295 +#: ../../content/applications/productivity/sign.rst:309 msgid ":guilabel:`Checkbox`: users can tick a box (e.g., to mark their approval or consent)." msgstr "" -#: ../../content/applications/productivity/sign.rst:296 +#: ../../content/applications/productivity/sign.rst:310 msgid ":guilabel:`Selection`: users choose a single option from a variety of options." msgstr "" -#: ../../content/applications/productivity/sign.rst:298 +#: ../../content/applications/productivity/sign.rst:312 msgid "The :guilabel:`Auto-fill Partner Field` setting is used to automatically fill in a field during the signature process. It uses the value of one of the fields on the contact (`res.partner`) model of the person signing the document. To do so, enter the contact model field's technical name." msgstr "" -#: ../../content/applications/productivity/sign.rst:303 +#: ../../content/applications/productivity/sign.rst:317 msgid "To know the technical name of a field, enable developer mode and hover your mouse on the question mark next to the field." msgstr "" -#: ../../content/applications/productivity/sign.rst:307 +#: ../../content/applications/productivity/sign.rst:321 msgid "Auto-completed values are suggestions and can be modified as required by the person signing the document." msgstr "" -#: ../../content/applications/productivity/sign.rst:310 +#: ../../content/applications/productivity/sign.rst:324 msgid "The size of the fields can also be changed by editing the :guilabel:`Default Width` and :guilabel:`Default Height`. Both sizes are defined as a percentage of the full page expressed as a decimal, with 1 equalling the full page's width or height. By default, the width of new fields you create is set to 15% (0.150) of a full page's width, while their height is set to 1.5% (0.015) of a full page's height." msgstr "" -#: ../../content/applications/productivity/sign.rst:316 +#: ../../content/applications/productivity/sign.rst:330 msgid "Next, write a :guilabel:`Tip`. Tips are displayed inside arrows on the left-hand side of the user's screen during the signing process to help them understand what the step entails (e.g., \"Sign here\" or “Fill in your birthdate”). You can also use a :guilabel:`Placeholder` text to be displayed inside the field before it is completed." msgstr "" @@ -3018,6 +3498,609 @@ msgstr "" msgid "Tip and placeholder example in Odoo Sign" msgstr "" +#: ../../content/applications/productivity/sign/australia.rst:5 +msgid "Odoo Sign legality in Australia" +msgstr "" + +#: ../../content/applications/productivity/sign/australia.rst:7 +msgid ":doc:`Odoo Sign <../sign>` is your trusted partner for secure, efficient, and legally compliant electronic signatures in Australia." +msgstr "" + +#: ../../content/applications/productivity/sign/australia.rst:11 +msgid "Legal framework for electronic signatures in Australia" +msgstr "" + +#: ../../content/applications/productivity/sign/australia.rst:13 +msgid "In Australia, electronic signatures are regulated under the `Electronic Transactions Act (ETA) `_, the `Electronic Transactions Regulations (ETR) `_ and local regulations in each state. The law governs transactions performed through electronic means and the use of electronic signatures. The key points of the law include:" +msgstr "" + +#: ../../content/applications/productivity/sign/australia.rst:19 +#: ../../content/applications/productivity/sign/brazil.rst:18 +#: ../../content/applications/productivity/sign/canada.rst:18 +#: ../../content/applications/productivity/sign/china.rst:17 +#: ../../content/applications/productivity/sign/india.rst:20 +#: ../../content/applications/productivity/sign/japan.rst:18 +#: ../../content/applications/productivity/sign/mexico.rst:19 +#: ../../content/applications/productivity/sign/russia.rst:20 +#: ../../content/applications/productivity/sign/south_korea.rst:18 +#: ../../content/applications/productivity/sign/united_kingdom.rst:22 +msgid "**Legal recognition**: electronic signatures are legally equivalent to handwritten signatures if they meet certain criteria." +msgstr "" + +#: ../../content/applications/productivity/sign/australia.rst:21 +#: ../../content/applications/productivity/sign/brazil.rst:20 +#: ../../content/applications/productivity/sign/canada.rst:20 +#: ../../content/applications/productivity/sign/china.rst:19 +#: ../../content/applications/productivity/sign/india.rst:22 +#: ../../content/applications/productivity/sign/japan.rst:20 +#: ../../content/applications/productivity/sign/mexico.rst:21 +#: ../../content/applications/productivity/sign/russia.rst:22 +#: ../../content/applications/productivity/sign/south_korea.rst:20 +#: ../../content/applications/productivity/sign/united_kingdom.rst:24 +msgid "**Reliability and security**: electronic signatures must be created with a secure method that can reliably identify the signatory and ensure the integrity of the signed document." +msgstr "" + +#: ../../content/applications/productivity/sign/australia.rst:25 +msgid "How Odoo Sign complies with Australian regulations" +msgstr "" + +#: ../../content/applications/productivity/sign/australia.rst:27 +msgid "Odoo Sign ensures full compliance with the Electronic Signature Law of Australia by incorporating the following features:" +msgstr "" + +#: ../../content/applications/productivity/sign/australia.rst:30 +#: ../../content/applications/productivity/sign/brazil.rst:35 +#: ../../content/applications/productivity/sign/canada.rst:33 +#: ../../content/applications/productivity/sign/china.rst:29 +#: ../../content/applications/productivity/sign/india.rst:34 +#: ../../content/applications/productivity/sign/japan.rst:31 +#: ../../content/applications/productivity/sign/mexico.rst:33 +#: ../../content/applications/productivity/sign/russia.rst:35 +#: ../../content/applications/productivity/sign/south_korea.rst:33 +#: ../../content/applications/productivity/sign/united_kingdom.rst:37 +msgid "**Secure signature creation**: Odoo Sign utilizes advanced cryptographic techniques to ensure the authenticity and integrity of electronic signatures." +msgstr "" + +#: ../../content/applications/productivity/sign/australia.rst:32 +#: ../../content/applications/productivity/sign/brazil.rst:37 +#: ../../content/applications/productivity/sign/canada.rst:35 +#: ../../content/applications/productivity/sign/china.rst:31 +#: ../../content/applications/productivity/sign/india.rst:36 +#: ../../content/applications/productivity/sign/japan.rst:33 +#: ../../content/applications/productivity/sign/mexico.rst:35 +#: ../../content/applications/productivity/sign/russia.rst:37 +#: ../../content/applications/productivity/sign/south_korea.rst:35 +#: ../../content/applications/productivity/sign/united_kingdom.rst:39 +msgid "**Third-party signature authenticator**: Odoo Online serves as an independent validation mechanism that adds an extra layer of security to the procurement process." +msgstr "" + +#: ../../content/applications/productivity/sign/australia.rst:34 +#: ../../content/applications/productivity/sign/brazil.rst:39 +#: ../../content/applications/productivity/sign/canada.rst:37 +#: ../../content/applications/productivity/sign/china.rst:33 +#: ../../content/applications/productivity/sign/india.rst:38 +#: ../../content/applications/productivity/sign/japan.rst:35 +#: ../../content/applications/productivity/sign/mexico.rst:37 +#: ../../content/applications/productivity/sign/russia.rst:39 +#: ../../content/applications/productivity/sign/south_korea.rst:37 +#: ../../content/applications/productivity/sign/united_kingdom.rst:41 +msgid "**Audit trails**: detailed audit logs are maintained to provide evidence of the signing process, including timestamps, IP addresses, and identity verification." +msgstr "" + +#: ../../content/applications/productivity/sign/australia.rst:36 +#: ../../content/applications/productivity/sign/brazil.rst:41 +#: ../../content/applications/productivity/sign/canada.rst:39 +#: ../../content/applications/productivity/sign/china.rst:35 +#: ../../content/applications/productivity/sign/india.rst:40 +#: ../../content/applications/productivity/sign/japan.rst:37 +#: ../../content/applications/productivity/sign/mexico.rst:39 +#: ../../content/applications/productivity/sign/russia.rst:41 +#: ../../content/applications/productivity/sign/south_korea.rst:39 +#: ../../content/applications/productivity/sign/united_kingdom.rst:43 +msgid "**Cryptographic traceability and immutability**: Odoo Sign ensures that any operation is logged securely. An audit log provides full transparency to all parties while preserving private data." +msgstr "" + +#: ../../content/applications/productivity/sign/australia.rst:38 +#: ../../content/applications/productivity/sign/brazil.rst:43 +#: ../../content/applications/productivity/sign/canada.rst:41 +#: ../../content/applications/productivity/sign/china.rst:37 +#: ../../content/applications/productivity/sign/india.rst:42 +#: ../../content/applications/productivity/sign/japan.rst:39 +#: ../../content/applications/productivity/sign/mexico.rst:41 +#: ../../content/applications/productivity/sign/russia.rst:43 +#: ../../content/applications/productivity/sign/south_korea.rst:41 +#: ../../content/applications/productivity/sign/united_kingdom.rst:45 +msgid "**Multiple authentication means**: authentication by SMS, email, geoIP or handwritten electronic signature." +msgstr "" + +#: ../../content/applications/productivity/sign/australia.rst:42 +#: ../../content/applications/productivity/sign/brazil.rst:47 +#: ../../content/applications/productivity/sign/canada.rst:45 +#: ../../content/applications/productivity/sign/china.rst:40 +#: ../../content/applications/productivity/sign/india.rst:46 +#: ../../content/applications/productivity/sign/japan.rst:43 +#: ../../content/applications/productivity/sign/mexico.rst:45 +#: ../../content/applications/productivity/sign/russia.rst:47 +#: ../../content/applications/productivity/sign/south_korea.rst:45 +#: ../../content/applications/productivity/sign/united_kingdom.rst:49 +msgid "Types of documents you can sign with Odoo Sign" +msgstr "" + +#: ../../content/applications/productivity/sign/australia.rst:44 +#: ../../content/applications/productivity/sign/brazil.rst:49 +#: ../../content/applications/productivity/sign/canada.rst:47 +#: ../../content/applications/productivity/sign/china.rst:42 +#: ../../content/applications/productivity/sign/india.rst:48 +#: ../../content/applications/productivity/sign/japan.rst:45 +#: ../../content/applications/productivity/sign/mexico.rst:47 +#: ../../content/applications/productivity/sign/russia.rst:49 +#: ../../content/applications/productivity/sign/south_korea.rst:47 +#: ../../content/applications/productivity/sign/united_kingdom.rst:51 +msgid "Odoo Sign is versatile and can be used for a wide range of documents, including but not limited to:" +msgstr "" + +#: ../../content/applications/productivity/sign/australia.rst:46 +#: ../../content/applications/productivity/sign/brazil.rst:51 +#: ../../content/applications/productivity/sign/canada.rst:49 +#: ../../content/applications/productivity/sign/china.rst:44 +#: ../../content/applications/productivity/sign/india.rst:50 +#: ../../content/applications/productivity/sign/japan.rst:47 +#: ../../content/applications/productivity/sign/mexico.rst:49 +#: ../../content/applications/productivity/sign/russia.rst:51 +#: ../../content/applications/productivity/sign/south_korea.rst:49 +#: ../../content/applications/productivity/sign/united_kingdom.rst:53 +msgid "**Contracts and agreements**: business contracts, employment agreements, and service contracts." +msgstr "" + +#: ../../content/applications/productivity/sign/australia.rst:47 +#: ../../content/applications/productivity/sign/brazil.rst:52 +#: ../../content/applications/productivity/sign/canada.rst:50 +#: ../../content/applications/productivity/sign/china.rst:45 +#: ../../content/applications/productivity/sign/india.rst:51 +#: ../../content/applications/productivity/sign/japan.rst:48 +#: ../../content/applications/productivity/sign/mexico.rst:50 +#: ../../content/applications/productivity/sign/russia.rst:52 +#: ../../content/applications/productivity/sign/south_korea.rst:50 +#: ../../content/applications/productivity/sign/united_kingdom.rst:54 +msgid "**Financial documents**: loan agreements, investment documents, and financial reports." +msgstr "" + +#: ../../content/applications/productivity/sign/australia.rst:48 +#: ../../content/applications/productivity/sign/brazil.rst:53 +#: ../../content/applications/productivity/sign/canada.rst:51 +#: ../../content/applications/productivity/sign/china.rst:46 +#: ../../content/applications/productivity/sign/india.rst:52 +#: ../../content/applications/productivity/sign/japan.rst:49 +#: ../../content/applications/productivity/sign/mexico.rst:51 +#: ../../content/applications/productivity/sign/russia.rst:53 +#: ../../content/applications/productivity/sign/south_korea.rst:51 +#: ../../content/applications/productivity/sign/united_kingdom.rst:55 +msgid "**HR documents**: employee onboarding forms, non-disclosure agreements (NDAs), and performance reviews." +msgstr "" + +#: ../../content/applications/productivity/sign/australia.rst:50 +#: ../../content/applications/productivity/sign/brazil.rst:55 +#: ../../content/applications/productivity/sign/canada.rst:53 +#: ../../content/applications/productivity/sign/china.rst:47 +#: ../../content/applications/productivity/sign/india.rst:54 +#: ../../content/applications/productivity/sign/japan.rst:51 +#: ../../content/applications/productivity/sign/mexico.rst:53 +#: ../../content/applications/productivity/sign/russia.rst:55 +#: ../../content/applications/productivity/sign/south_korea.rst:53 +#: ../../content/applications/productivity/sign/united_kingdom.rst:57 +msgid "**Commercial transactions**: purchase orders, sales agreements, and supplier contracts." +msgstr "" + +#: ../../content/applications/productivity/sign/australia.rst:53 +#: ../../content/applications/productivity/sign/brazil.rst:58 +#: ../../content/applications/productivity/sign/canada.rst:56 +#: ../../content/applications/productivity/sign/china.rst:50 +#: ../../content/applications/productivity/sign/india.rst:57 +#: ../../content/applications/productivity/sign/japan.rst:54 +#: ../../content/applications/productivity/sign/mexico.rst:56 +#: ../../content/applications/productivity/sign/russia.rst:58 +#: ../../content/applications/productivity/sign/south_korea.rst:56 +#: ../../content/applications/productivity/sign/united_kingdom.rst:60 +msgid "Potential exceptions" +msgstr "" + +#: ../../content/applications/productivity/sign/australia.rst:55 +msgid "While Odoo Sign is broadly applicable, there are certain exceptions where electronic signatures may not be suitable or legally recognized in Australia:" +msgstr "" + +#: ../../content/applications/productivity/sign/australia.rst:58 +#: ../../content/applications/productivity/sign/brazil.rst:63 +#: ../../content/applications/productivity/sign/canada.rst:61 +#: ../../content/applications/productivity/sign/china.rst:55 +#: ../../content/applications/productivity/sign/india.rst:62 +#: ../../content/applications/productivity/sign/japan.rst:59 +#: ../../content/applications/productivity/sign/mexico.rst:61 +#: ../../content/applications/productivity/sign/russia.rst:63 +#: ../../content/applications/productivity/sign/south_korea.rst:61 +#: ../../content/applications/productivity/sign/united_kingdom.rst:65 +msgid "**Wills and trusts**: documents related to inheritance, wills, and trusts often require handwritten signatures." +msgstr "" + +#: ../../content/applications/productivity/sign/australia.rst:60 +#: ../../content/applications/productivity/sign/brazil.rst:65 +#: ../../content/applications/productivity/sign/canada.rst:63 +#: ../../content/applications/productivity/sign/china.rst:56 +#: ../../content/applications/productivity/sign/india.rst:64 +#: ../../content/applications/productivity/sign/japan.rst:61 +#: ../../content/applications/productivity/sign/mexico.rst:63 +#: ../../content/applications/productivity/sign/russia.rst:65 +#: ../../content/applications/productivity/sign/south_korea.rst:63 +#: ../../content/applications/productivity/sign/united_kingdom.rst:67 +msgid "**Real estate transactions**: some property transactions may still require notarized handwritten signatures." +msgstr "" + +#: ../../content/applications/productivity/sign/australia.rst:62 +#: ../../content/applications/productivity/sign/brazil.rst:67 +#: ../../content/applications/productivity/sign/canada.rst:65 +#: ../../content/applications/productivity/sign/china.rst:57 +#: ../../content/applications/productivity/sign/india.rst:66 +#: ../../content/applications/productivity/sign/japan.rst:63 +#: ../../content/applications/productivity/sign/mexico.rst:65 +#: ../../content/applications/productivity/sign/russia.rst:67 +#: ../../content/applications/productivity/sign/south_korea.rst:65 +#: ../../content/applications/productivity/sign/united_kingdom.rst:69 +msgid "**Government forms**: specific government forms and applications may mandate physical signatures." +msgstr "" + +#: ../../content/applications/productivity/sign/australia.rst:64 +#: ../../content/applications/productivity/sign/brazil.rst:69 +#: ../../content/applications/productivity/sign/canada.rst:67 +#: ../../content/applications/productivity/sign/china.rst:59 +#: ../../content/applications/productivity/sign/india.rst:68 +#: ../../content/applications/productivity/sign/japan.rst:65 +#: ../../content/applications/productivity/sign/mexico.rst:67 +#: ../../content/applications/productivity/sign/russia.rst:69 +#: ../../content/applications/productivity/sign/south_korea.rst:67 +#: ../../content/applications/productivity/sign/united_kingdom.rst:71 +msgid "Disclaimer" +msgstr "" + +#: ../../content/applications/productivity/sign/australia.rst:66 +msgid "The information provided on this page is for general informational purposes only and does not constitute legal advice. While Odoo Sign complies with the Electronic Signature Law of Australia, users should consult with legal professionals to ensure specific document types and use cases meet all legal requirements. Compliance with additional industry-specific regulations may also be necessary." +msgstr "" + +#: ../../content/applications/productivity/sign/australia.rst:72 +#: ../../content/applications/productivity/sign/brazil.rst:77 +#: ../../content/applications/productivity/sign/canada.rst:75 +#: ../../content/applications/productivity/sign/china.rst:66 +#: ../../content/applications/productivity/sign/india.rst:76 +#: ../../content/applications/productivity/sign/japan.rst:73 +#: ../../content/applications/productivity/sign/mexico.rst:75 +#: ../../content/applications/productivity/sign/russia.rst:77 +#: ../../content/applications/productivity/sign/south_korea.rst:75 +#: ../../content/applications/productivity/sign/united_kingdom.rst:79 +msgid "*Last updated: June 19, 2024*" +msgstr "" + +#: ../../content/applications/productivity/sign/brazil.rst:5 +msgid "Odoo Sign legality in Brazil" +msgstr "" + +#: ../../content/applications/productivity/sign/brazil.rst:7 +msgid ":doc:`Odoo Sign <../sign>` is your trusted partner for secure, efficient, and legally compliant electronic signatures in Brazil." +msgstr "" + +#: ../../content/applications/productivity/sign/brazil.rst:11 +msgid "Legal framework for electronic signatures in Brazil" +msgstr "" + +#: ../../content/applications/productivity/sign/brazil.rst:13 +msgid "In Brazil, electronic signatures are regulated under the `Brazilian Civil Code `_ and the Provisional Executive Act 2.200-2 (EA 2200) regulations. The law governs transactions performed through electronic means and the use of electronic signatures. The key points of the law include:" +msgstr "" + +#: ../../content/applications/productivity/sign/brazil.rst:22 +msgid "**Infraestrutura de Chaves Públicas Brasileira (ICP-Brazil)**: Brazil maintains its own public key infrastructure (PKI) for digital certificates called “Infraestrutura de Chaves Públicas Brasileira”. These are digital signature certificates or “seals” that serve as proof of identity of an individual for a certain purpose that can be used in special cases to provide additional security. These certificates are issued by Certification Authorities and are required by law for the signature of specific acts." +msgstr "" + +#: ../../content/applications/productivity/sign/brazil.rst:30 +msgid "How Odoo Sign complies with Brazilian regulations" +msgstr "" + +#: ../../content/applications/productivity/sign/brazil.rst:32 +msgid "Odoo Sign ensures full compliance with the Electronic Signature Law of Brazil by incorporating the following features:" +msgstr "" + +#: ../../content/applications/productivity/sign/brazil.rst:60 +msgid "While Odoo Sign is broadly applicable, there are certain exceptions where electronic signatures may not be suitable or legally recognized in Brazil:" +msgstr "" + +#: ../../content/applications/productivity/sign/brazil.rst:71 +msgid "The information provided on this page is for general informational purposes only and does not constitute legal advice. While Odoo Sign complies with the Electronic Signature Law of Brazil, users should consult with legal professionals to ensure specific document types and use cases meet all legal requirements. Compliance with additional industry-specific regulations may also be necessary." +msgstr "" + +#: ../../content/applications/productivity/sign/canada.rst:5 +msgid "Odoo Sign legality in Canada" +msgstr "" + +#: ../../content/applications/productivity/sign/canada.rst:7 +msgid ":doc:`Odoo Sign <../sign>` is your trusted partner for secure, efficient, and legally compliant electronic signatures in Canada." +msgstr "" + +#: ../../content/applications/productivity/sign/canada.rst:11 +msgid "Legal framework for electronic signatures in Canada" +msgstr "" + +#: ../../content/applications/productivity/sign/canada.rst:13 +msgid "In Canada, electronic signatures are regulated under the `Personal Information Protection and Electronic Documents Act (PIPEDA) `_ and local regulations. The law establishes electronic equivalents to paper-based documents and signatures at the federal level. The key points of the law include:" +msgstr "" + +#: ../../content/applications/productivity/sign/canada.rst:22 +msgid "**Secure electronic signature**: the law recognizes digital signature certificates or “seals” that serve as proof of identity of an individual for a certain purpose that can be used in special cases to provide additional security. These certificates are issued by Certification Authorities and are required by law for the signature of specific acts." +msgstr "" + +#: ../../content/applications/productivity/sign/canada.rst:28 +msgid "How Odoo Sign complies with Canadian regulations" +msgstr "" + +#: ../../content/applications/productivity/sign/canada.rst:30 +msgid "Odoo Sign ensures full compliance with the Electronic Signature Law of Canada by incorporating the following features:" +msgstr "" + +#: ../../content/applications/productivity/sign/canada.rst:58 +msgid "While Odoo Sign is broadly applicable, there are certain exceptions where electronic signatures may not be suitable or legally recognized in Canada:" +msgstr "" + +#: ../../content/applications/productivity/sign/canada.rst:69 +msgid "The information provided on this page is for general informational purposes only and does not constitute legal advice. While Odoo Sign complies with the Electronic Signature Law of Canada, users should consult with legal professionals to ensure specific document types and use cases meet all legal requirements. Compliance with additional industry-specific regulations may also be necessary." +msgstr "" + +#: ../../content/applications/productivity/sign/china.rst:5 +msgid "Odoo Sign legality in China" +msgstr "" + +#: ../../content/applications/productivity/sign/china.rst:7 +msgid ":doc:`Odoo Sign <../sign>` is your trusted partner for secure, efficient, and legally compliant electronic signatures in China." +msgstr "" + +#: ../../content/applications/productivity/sign/china.rst:11 +msgid "Legal framework for electronic signatures in China" +msgstr "" + +#: ../../content/applications/productivity/sign/china.rst:13 +msgid "In China, electronic signatures are regulated under the Electronic Signature Law (ESL) of the People's Republic of China, enacted in 2005 and amended in 2015. The law provides the foundation for the use and legal recognition of electronic signatures. The key points of the ESL include:" +msgstr "" + +#: ../../content/applications/productivity/sign/china.rst:21 +msgid "**Certification Authorities (CAs)**: the law recognizes electronic signatures supported by digital certificates issued by accredited Certification Authorities (CAs)." +msgstr "" + +#: ../../content/applications/productivity/sign/china.rst:25 +msgid "How Odoo Sign complies with Chinese regulations" +msgstr "" + +#: ../../content/applications/productivity/sign/china.rst:27 +msgid "Odoo Sign ensures full compliance with the Electronic Signature Law of China by incorporating the following features:" +msgstr "" + +#: ../../content/applications/productivity/sign/china.rst:52 +msgid "While Odoo Sign is broadly applicable, there are certain exceptions where electronic signatures may not be suitable or legally recognized in China:" +msgstr "" + +#: ../../content/applications/productivity/sign/china.rst:61 +msgid "The information provided on this page is for general informational purposes only and does not constitute legal advice. While Odoo Sign complies with the Electronic Signature Law of China, users should consult with legal professionals to ensure specific document types and use cases meet all legal requirements. Compliance with additional industry-specific regulations may also be necessary." +msgstr "" + +#: ../../content/applications/productivity/sign/india.rst:5 +msgid "Odoo Sign legality in India" +msgstr "" + +#: ../../content/applications/productivity/sign/india.rst:7 +msgid ":doc:`Odoo Sign <../sign>` is your trusted partner for secure, efficient, and legally compliant electronic signatures in India." +msgstr "" + +#: ../../content/applications/productivity/sign/india.rst:11 +msgid "Legal framework for electronic signatures in India" +msgstr "" + +#: ../../content/applications/productivity/sign/india.rst:13 +msgid "In India, electronic signatures are regulated under the `Information Technology Act (ITA) `_, the `Indian Contract Act (ICA) `_ and the Electronic Signature or Electronic Authentication Technique and Procedure Rules (ESEATPR). The law provides the foundation for the use and legal recognition of electronic signatures. The key points of the law include:" +msgstr "" + +#: ../../content/applications/productivity/sign/india.rst:24 +msgid "**Digital signature certificates**: the law recognizes digital signature certificates that serve as proof of identity of an individual for a certain purpose that can be used in special cases to provide additional security." +msgstr "" + +#: ../../content/applications/productivity/sign/india.rst:29 +msgid "How Odoo Sign complies with Indian regulations" +msgstr "" + +#: ../../content/applications/productivity/sign/india.rst:31 +msgid "Odoo Sign ensures full compliance with the Electronic Signature Law of India by incorporating the following features:" +msgstr "" + +#: ../../content/applications/productivity/sign/india.rst:59 +msgid "While Odoo Sign is broadly applicable, there are certain exceptions where electronic signatures may not be suitable or legally recognized in India:" +msgstr "" + +#: ../../content/applications/productivity/sign/india.rst:70 +msgid "The information provided on this page is for general informational purposes only and does not constitute legal advice. While Odoo Sign complies with the Electronic Signature Law of India, users should consult with legal professionals to ensure specific document types and use cases meet all legal requirements. Compliance with additional industry-specific regulations may also be necessary." +msgstr "" + +#: ../../content/applications/productivity/sign/japan.rst:5 +msgid "Odoo Sign legality in Japan" +msgstr "" + +#: ../../content/applications/productivity/sign/japan.rst:7 +msgid ":doc:`Odoo Sign <../sign>` is your trusted partner for secure, efficient, and legally compliant electronic signatures in Japan." +msgstr "" + +#: ../../content/applications/productivity/sign/japan.rst:11 +msgid "Legal framework for electronic signatures in Japan" +msgstr "" + +#: ../../content/applications/productivity/sign/japan.rst:13 +msgid "In Japan, electronic signatures are regulated under the `Act on Electronic Signatures and Certification Business (E-signature Act) `_ published in the official gazette on May 31, 2000. The law provides the foundation for the use and legal recognition of electronic signatures. The key points of the E-signature Act include:" +msgstr "" + +#: ../../content/applications/productivity/sign/japan.rst:22 +msgid "**Certification Businesses (CBs)**: the law recognizes electronic signatures supported by digital certificates issued by accredited CBs." +msgstr "" + +#: ../../content/applications/productivity/sign/japan.rst:26 +msgid "How Odoo Sign complies with Japanese regulations" +msgstr "" + +#: ../../content/applications/productivity/sign/japan.rst:28 +msgid "Odoo Sign ensures full compliance with the Electronic Signature Law of Japan by incorporating the following features:" +msgstr "" + +#: ../../content/applications/productivity/sign/japan.rst:56 +msgid "While Odoo Sign is broadly applicable, there are certain exceptions where electronic signatures may not be suitable or legally recognized in Japan:" +msgstr "" + +#: ../../content/applications/productivity/sign/japan.rst:67 +msgid "The information provided on this page is for general informational purposes only and does not constitute legal advice. While Odoo Sign complies with the Electronic Signature Law of Japan, users should consult with legal professionals to ensure specific document types and use cases meet all legal requirements. Compliance with additional industry-specific regulations may also be necessary." +msgstr "" + +#: ../../content/applications/productivity/sign/mexico.rst:5 +msgid "Odoo Sign legality in Mexico" +msgstr "" + +#: ../../content/applications/productivity/sign/mexico.rst:7 +msgid ":doc:`Odoo Sign <../sign>` is your trusted partner for secure, efficient, and legally compliant electronic signatures in Mexico." +msgstr "" + +#: ../../content/applications/productivity/sign/mexico.rst:11 +msgid "Legal framework for electronic signatures in Mexico" +msgstr "" + +#: ../../content/applications/productivity/sign/mexico.rst:13 +msgid "In Mexico, electronic signatures are regulated under the `Mexican Civil Code `_ and the `Commercial Code `_, as well as the civil codes of each state. The law governs transactions performed through electronic means and the use of electronic signatures. The key points of the law include:" +msgstr "" + +#: ../../content/applications/productivity/sign/mexico.rst:23 +msgid "**NORMA Oficial Mexicana NOM-151-SCFI-2016 (NOM 151)**: establishes the requirements for the conservation of data messages and digitization of documents with full guarantees of integrity. It also establishes the certification and time stamping requirements for certain documents." +msgstr "" + +#: ../../content/applications/productivity/sign/mexico.rst:28 +msgid "How Odoo Sign complies with Mexican regulations" +msgstr "" + +#: ../../content/applications/productivity/sign/mexico.rst:30 +msgid "Odoo Sign ensures full compliance with the Electronic Signature Law of Mexico by incorporating the following features:" +msgstr "" + +#: ../../content/applications/productivity/sign/mexico.rst:58 +msgid "While Odoo Sign is broadly applicable, there are certain exceptions where electronic signatures may not be suitable or legally recognized in Mexico:" +msgstr "" + +#: ../../content/applications/productivity/sign/mexico.rst:69 +msgid "The information provided on this page is for general informational purposes only and does not constitute legal advice. While Odoo Sign complies with the Electronic Signature Law of Mexico, users should consult with legal professionals to ensure specific document types and use cases meet all legal requirements. Compliance with additional industry-specific regulations may also be necessary." +msgstr "" + +#: ../../content/applications/productivity/sign/russia.rst:5 +msgid "Odoo Sign legality in Russia" +msgstr "" + +#: ../../content/applications/productivity/sign/russia.rst:7 +msgid ":doc:`Odoo Sign <../sign>` is your trusted partner for secure, efficient, and legally compliant electronic signatures in Russia." +msgstr "" + +#: ../../content/applications/productivity/sign/russia.rst:11 +msgid "Legal framework for electronic signatures in Russia" +msgstr "" + +#: ../../content/applications/productivity/sign/russia.rst:13 +msgid "In Russia, electronic signatures are regulated under the `Federal Law No. 63-FZ as of 6 April 2011 \"On electronic signature\" `_ and the `Civil Code of the Russian Federation `_. The law provides the foundation for the use and legal recognition of electronic signatures. The key points of the law include:" +msgstr "" + +#: ../../content/applications/productivity/sign/russia.rst:24 +msgid "**Qualified electronic signatures**: the law recognizes digital signature certificates that serve as proof of identity of an individual for a certain purpose that can be used in special cases to provide additional security. These certificates are issued by Certification Authorities and are required by law for the signature of specific acts." +msgstr "" + +#: ../../content/applications/productivity/sign/russia.rst:30 +msgid "How Odoo Sign complies with Russian regulations" +msgstr "" + +#: ../../content/applications/productivity/sign/russia.rst:32 +msgid "Odoo Sign ensures full compliance with the Electronic Signature Law of Russia by incorporating the following features:" +msgstr "" + +#: ../../content/applications/productivity/sign/russia.rst:60 +msgid "While Odoo Sign is broadly applicable, there are certain exceptions where electronic signatures may not be suitable or legally recognized in Russia:" +msgstr "" + +#: ../../content/applications/productivity/sign/russia.rst:71 +msgid "The information provided on this page is for general informational purposes only and does not constitute legal advice. While Odoo Sign complies with the Electronic Signature Law of Russia, users should consult with legal professionals to ensure specific document types and use cases meet all legal requirements. Compliance with additional industry-specific regulations may also be necessary." +msgstr "" + +#: ../../content/applications/productivity/sign/south_korea.rst:5 +msgid "Odoo Sign legality in South Korea" +msgstr "" + +#: ../../content/applications/productivity/sign/south_korea.rst:7 +msgid ":doc:`Odoo Sign <../sign>` is your trusted partner for secure, efficient, and legally compliant electronic signatures in South Korea." +msgstr "" + +#: ../../content/applications/productivity/sign/south_korea.rst:11 +msgid "Legal framework for electronic signatures in South Korea" +msgstr "" + +#: ../../content/applications/productivity/sign/south_korea.rst:13 +msgid "In South Korea, electronic signatures are regulated under the `Digital Signature Act `_ and the `Framework Act on Electronic Documents and Transactions of Korea `_. The law governs transactions performed through electronic means and the use of electronic signatures. The key points of the law include:" +msgstr "" + +#: ../../content/applications/productivity/sign/south_korea.rst:22 +msgid "**Electronic signature certification services**: the law recognizes digital signature certificates or “seals” that serve as proof of identity of an individual for a certain purpose that can be used in special cases to provide additional security. These certificates are issued by Certification Authorities and are required by law for the signature of specific acts." +msgstr "" + +#: ../../content/applications/productivity/sign/south_korea.rst:28 +msgid "How Odoo Sign complies with South Korean regulations" +msgstr "" + +#: ../../content/applications/productivity/sign/south_korea.rst:30 +msgid "Odoo Sign ensures full compliance with the Electronic Signature Law of South Korea by incorporating the following features:" +msgstr "" + +#: ../../content/applications/productivity/sign/south_korea.rst:58 +msgid "While Odoo Sign is broadly applicable, there are certain exceptions where electronic signatures may not be suitable or legally recognized in South Korea:" +msgstr "" + +#: ../../content/applications/productivity/sign/south_korea.rst:69 +msgid "The information provided on this page is for general informational purposes only and does not constitute legal advice. While Odoo Sign complies with the Electronic Signature Law of South Korea, users should consult with legal professionals to ensure specific document types and use cases meet all legal requirements. Compliance with additional industry-specific regulations may also be necessary." +msgstr "" + +#: ../../content/applications/productivity/sign/united_kingdom.rst:5 +msgid "Odoo Sign legality in the United Kingdom" +msgstr "" + +#: ../../content/applications/productivity/sign/united_kingdom.rst:7 +msgid ":doc:`Odoo Sign <../sign>` is your trusted partner for secure, efficient, and legally compliant electronic signatures in the United Kingdom." +msgstr "" + +#: ../../content/applications/productivity/sign/united_kingdom.rst:11 +msgid "Legal framework for electronic signatures in the United Kingdom" +msgstr "" + +#: ../../content/applications/productivity/sign/united_kingdom.rst:13 +msgid "In the United Kingdom, electronic signatures are regulated under Electronic Communications Act (ECA), and the `UK version `_ of Regulation (EU) No 910/2014 of the European Parliament and of the Council of 23 July 2014 on electronic identification and trust services for electronic transactions in the internal market (eIDAS) as amended by the `Electronic Identification and Trust Services for Electronic Transactions `_ (Amendment) (EU Exit) Regulations 2019 (SI 2019/89) (the “UK eIDAS Regulation”). The law provides the foundation for the use and legal recognition of electronic signatures. The key points of the law include:" +msgstr "" + +#: ../../content/applications/productivity/sign/united_kingdom.rst:26 +msgid "**Digital signature certificates**: the law recognizes digital signature certificates that serve as proof of identity of an individual for a certain purpose that can be used in special cases to provide additional security. These certificates are issued by Certification Authorities and are required by law for the signature of specific acts." +msgstr "" + +#: ../../content/applications/productivity/sign/united_kingdom.rst:32 +msgid "How Odoo Sign complies with the United Kingdom regulations" +msgstr "" + +#: ../../content/applications/productivity/sign/united_kingdom.rst:34 +msgid "Odoo Sign ensures full compliance with the Electronic Signature Law of the United Kingdom by incorporating the following features:" +msgstr "" + +#: ../../content/applications/productivity/sign/united_kingdom.rst:62 +msgid "While Odoo Sign is broadly applicable, there are certain exceptions where electronic signatures may not be suitable or legally recognized in the United Kingdom:" +msgstr "" + +#: ../../content/applications/productivity/sign/united_kingdom.rst:73 +msgid "The information provided on this page is for general informational purposes only and does not constitute legal advice. While Odoo Sign complies with the Electronic Signature Law of the United Kingdom, users should consult with legal professionals to ensure specific document types and use cases meet all legal requirements. Compliance with additional industry-specific regulations may also be necessary." +msgstr "" + #: ../../content/applications/productivity/spreadsheet.rst:6 msgid "Spreadsheet" msgstr "" @@ -6114,7 +7197,7 @@ msgid "Odoo VoIP (Voice over Internet Protocol) can be set up to work together w msgstr "" #: ../../content/applications/productivity/voip/axivox/axivox_config.rst:12 -msgid "To use this service, `contact Axivox `_ to open an account. Before doing so, verify that Axivox covers the company's area, along with the areas the company's users wish to call." +msgid "To use this service, `contact Axivox `_ to open an account. Before doing so, verify that Axivox covers the company's area, along with the areas the company's users wish to call." msgstr "" #: ../../content/applications/productivity/voip/axivox/axivox_config.rst:19 @@ -6233,12 +7316,6 @@ msgstr "" msgid "To add a call queue in Axivox, navigate to the `Axivox management console `_. In the left menu, click :guilabel:`Queues`. Next, click :guilabel:`Add a queue`. Doing so reveals a blank :guilabel:`New queue` form with various fields to fill out." msgstr "" -#: ../../content/applications/productivity/voip/axivox/call_queues.rst:30 -#: ../../content/applications/productivity/whatsapp.rst:273 -#: ../../content/applications/productivity/whatsapp.rst:677 -msgid "Name" -msgstr "" - #: ../../content/applications/productivity/voip/axivox/call_queues.rst:32 msgid "Once the :guilabel:`New queue` page appears, enter the :guilabel:`Name` of the queue." msgstr "" diff --git a/locale/sources/sales.pot b/locale/sources/sales.pot index 75e536b0e..e2740152c 100644 --- a/locale/sources/sales.pot +++ b/locale/sources/sales.pot @@ -8,7 +8,7 @@ msgid "" msgstr "" "Project-Id-Version: Odoo 17.0\n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2024-06-24 07:08+0000\n" +"POT-Creation-Date: 2024-07-23 13:30+0000\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME \n" "Language-Team: LANGUAGE \n" @@ -60,6 +60,7 @@ msgstr "" #: ../../content/applications/sales/point_of_sale/payment_methods/terminals/six.rst:14 #: ../../content/applications/sales/point_of_sale/payment_methods/terminals/stripe.rst:19 #: ../../content/applications/sales/point_of_sale/payment_methods/terminals/vantiv.rst:17 +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/viva_wallet.rst:13 #: ../../content/applications/sales/point_of_sale/payment_methods/terminals/worldline.rst:16 #: ../../content/applications/sales/point_of_sale/pricing/cash_rounding.rst:17 #: ../../content/applications/sales/point_of_sale/pricing/electronic_labels.rst:16 @@ -138,7 +139,7 @@ msgid "To merge this lead with an existing similar lead or opportunity, select : msgstr "" #: ../../content/applications/sales/crm/acquire_leads/convert.rst:64 -#: ../../content/applications/sales/crm/pipeline/merge_similar.rst:37 +#: ../../content/applications/sales/crm/pipeline/merge_similar.rst:38 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 "" @@ -785,116 +786,148 @@ msgid "After selecting a product, update the :guilabel:`Quantity`, if necessary. msgstr "" #: ../../content/applications/sales/crm/acquire_leads/send_quotes.rst:97 -msgid "To remove a line from the quotation, click the :guilabel:`🗑️ (trash can)` icon." +msgid "To remove a line from the quotation, click the :icon:`fa-trash-o` :guilabel:`(trash can)` icon." msgstr "" #: ../../content/applications/sales/crm/acquire_leads/send_quotes.rst:99 -msgid "Repeat the steps above until the quotation is complete." +msgid "To organize products into sections click :guilabel:`Add a section` and type a name for the section. Then, click the :icon:`oi-draggable` :guilabel:`(drag)` icon to the left of the name and drag to move the section to the appropriate location. Move each product using the same method to finish organizing the quotation order lines." msgstr "" -#: ../../content/applications/sales/crm/acquire_leads/send_quotes.rst:102 +#: ../../content/applications/sales/crm/acquire_leads/send_quotes.rst:-1 +msgid "Categories are used to create separate sections on the order lines of a quote." +msgstr "" + +#: ../../content/applications/sales/crm/acquire_leads/send_quotes.rst:109 +msgid "Product catalog" +msgstr "" + +#: ../../content/applications/sales/crm/acquire_leads/send_quotes.rst:111 +msgid "To quickly add numerous products to the quotation, click the :guilabel:`Catalog` button to open the product catalog." +msgstr "" + +#: ../../content/applications/sales/crm/acquire_leads/send_quotes.rst:114 +msgid "All products in the database are listed as cards and can be sorted in the left panel by :guilabel:`Product Category` and :guilabel:`Attributes`." +msgstr "" + +#: ../../content/applications/sales/crm/acquire_leads/send_quotes.rst:-1 +msgid "The product catalog displays all products as cards." +msgstr "" + +#: ../../content/applications/sales/crm/acquire_leads/send_quotes.rst:121 +msgid "To add a product, click the :icon:`fa-shopping-cart` :guilabel:`Add` button on the product card. Set the quantity of the item using the :icon:`fa-plus` :guilabel:`(add)` or :icon:`fa-minus` :guilabel:`(subtract)` buttons, or type the quantity in the number field between the two buttons. To remove an item, click the :icon:`fa-trash` :guilabel:`Remove` button on the product card." +msgstr "" + +#: ../../content/applications/sales/crm/acquire_leads/send_quotes.rst:-1 +msgid "The purple add and subtract buttons are used to set the quantity of an item." +msgstr "" + +#: ../../content/applications/sales/crm/acquire_leads/send_quotes.rst:130 +msgid "Once all product quantities are set, click the :guilabel:`Back to Quotation` button to return to the quotation. The items selected in the product catalog now appear in the :guilabel:`Order Lines` tab." +msgstr "" + +#: ../../content/applications/sales/crm/acquire_leads/send_quotes.rst:134 msgid "Preview and send quotation" msgstr "" -#: ../../content/applications/sales/crm/acquire_leads/send_quotes.rst:104 +#: ../../content/applications/sales/crm/acquire_leads/send_quotes.rst:136 msgid "To see a preview of the quotation as the customer will see it, click the :guilabel:`Preview` button. Doing so opens a preview in the :guilabel:`Customer Portal`." msgstr "" -#: ../../content/applications/sales/crm/acquire_leads/send_quotes.rst:107 +#: ../../content/applications/sales/crm/acquire_leads/send_quotes.rst:139 msgid "After reviewing the customer preview, click :guilabel:`Return to edit mode` to return to the quotation form in the backend." msgstr "" -#: ../../content/applications/sales/crm/acquire_leads/send_quotes.rst:110 +#: ../../content/applications/sales/crm/acquire_leads/send_quotes.rst:142 msgid "When the quotation is ready to deliver to the customer, click the :guilabel:`Send by Email` button." msgstr "" -#: ../../content/applications/sales/crm/acquire_leads/send_quotes.rst:112 +#: ../../content/applications/sales/crm/acquire_leads/send_quotes.rst:144 msgid "Doing so opens a pop-up window with a pre-configured email message. Information from the quotation, including the contact information, total cost, and quotation title are be imported from the quotation." msgstr "" -#: ../../content/applications/sales/crm/acquire_leads/send_quotes.rst:116 +#: ../../content/applications/sales/crm/acquire_leads/send_quotes.rst:148 msgid "A PDF of the quotation is added as an attachment to the email." msgstr "" -#: ../../content/applications/sales/crm/acquire_leads/send_quotes.rst:119 +#: ../../content/applications/sales/crm/acquire_leads/send_quotes.rst:151 msgid "A pre-loaded template is used to create the email message. To alter the template, click the internal link to the right of the :guilabel:`Load template` field, located at the bottom of the email pop-up window." msgstr "" -#: ../../content/applications/sales/crm/acquire_leads/send_quotes.rst:123 +#: ../../content/applications/sales/crm/acquire_leads/send_quotes.rst:155 msgid "To select a new template, select an option from the :guilabel:`Load template` drop-down menu." msgstr "" -#: ../../content/applications/sales/crm/acquire_leads/send_quotes.rst:125 +#: ../../content/applications/sales/crm/acquire_leads/send_quotes.rst:157 msgid "Proceed to make any necessary changes to the email, then click :guilabel:`Send`. A copy of the message is added to the *Chatter* of the of the record." msgstr "" -#: ../../content/applications/sales/crm/acquire_leads/send_quotes.rst:128 +#: ../../content/applications/sales/crm/acquire_leads/send_quotes.rst:160 msgid "After a quotation is sent, the originating opportunity's :guilabel:`Quotations` smart button updates with a new count. This quotation, and all other quotations can be accessed through this smart button at the top of the opportunity in the *CRM* app." msgstr "" -#: ../../content/applications/sales/crm/acquire_leads/send_quotes.rst:132 +#: ../../content/applications/sales/crm/acquire_leads/send_quotes.rst:164 msgid "Any quotations attached to the opportunity that are confirmed, and have therefore been converted to sales orders, will be deducted from the number listed on the :guilabel:`Quotations` smart button. Instead, the value of the sales order will appear in the :guilabel:`Orders` smart button located in the same control panel." msgstr "" -#: ../../content/applications/sales/crm/acquire_leads/send_quotes.rst:138 +#: ../../content/applications/sales/crm/acquire_leads/send_quotes.rst:170 msgid "Mark an opportunity won or lost" msgstr "" -#: ../../content/applications/sales/crm/acquire_leads/send_quotes.rst:140 +#: ../../content/applications/sales/crm/acquire_leads/send_quotes.rst:172 msgid "In order to keep the pipeline up to date and accurate, opportunities need to be identified as *won* or *lost* once a customer has responded to a quotation." msgstr "" -#: ../../content/applications/sales/crm/acquire_leads/send_quotes.rst:143 +#: ../../content/applications/sales/crm/acquire_leads/send_quotes.rst:175 msgid "To mark an opportunity as *won* or *lost*, return to the opportunity using the breadcrumbs at the top-left of the quotation form. Or navigate to :menuselection:`CRM app --> Sales --> My Pipeline` and click on the correct opportunity to open it." msgstr "" -#: ../../content/applications/sales/crm/acquire_leads/send_quotes.rst:147 +#: ../../content/applications/sales/crm/acquire_leads/send_quotes.rst:179 msgid "At the top-left of the form, click on either the :guilabel:`Won` or :guilabel:`Lost` button." msgstr "" -#: ../../content/applications/sales/crm/acquire_leads/send_quotes.rst:149 +#: ../../content/applications/sales/crm/acquire_leads/send_quotes.rst:181 msgid "If the opportunity is marked *won*, a green :guilabel:`Won` banner is added to the record, and it is moved to the :guilabel:`Won` stage." msgstr "" -#: ../../content/applications/sales/crm/acquire_leads/send_quotes.rst:152 +#: ../../content/applications/sales/crm/acquire_leads/send_quotes.rst:184 msgid "Marking an opportunity as *lost*, via the :guilabel:`Lost` button opens a :guilabel:`Mark Lost` pop-up window, where a :guilabel:`Lost Reason` can be entered." msgstr "" -#: ../../content/applications/sales/crm/acquire_leads/send_quotes.rst:155 +#: ../../content/applications/sales/crm/acquire_leads/send_quotes.rst:187 msgid "From the :guilabel:`Lost Reason` drop-down field, choose an existing lost reason. If no applicable reason is available, create a new one by entering it into the :guilabel:`Lost Reason` field, and clicking :guilabel:`Create`." msgstr "" -#: ../../content/applications/sales/crm/acquire_leads/send_quotes.rst:160 +#: ../../content/applications/sales/crm/acquire_leads/send_quotes.rst:192 msgid "It's best practice to try and use pre-configured :guilabel:`Lost Reason` values as much as possible or to limit the creation of new values only to sales team leads. Using consistent values for this parameter will make pipeline analysis easier and more accurate when filtering for the :guilabel:`Lost Reason` parameter." msgstr "" -#: ../../content/applications/sales/crm/acquire_leads/send_quotes.rst:165 +#: ../../content/applications/sales/crm/acquire_leads/send_quotes.rst:197 msgid "To set up new values for this field, navigate to :menuselection:`CRM --> Configuration --> Lost Reasons`, and click both :guilabel:`New`and :guilabel:`Save` for each new entry added to the list." msgstr "" -#: ../../content/applications/sales/crm/acquire_leads/send_quotes.rst:169 +#: ../../content/applications/sales/crm/acquire_leads/send_quotes.rst:201 msgid "Additional notes and comments can be added in the :guilabel:`Closing Note` field." msgstr "" -#: ../../content/applications/sales/crm/acquire_leads/send_quotes.rst:171 +#: ../../content/applications/sales/crm/acquire_leads/send_quotes.rst:203 #: ../../content/applications/sales/crm/pipeline/lost_opportunities.rst:34 -#: ../../content/applications/sales/crm/pipeline/lost_opportunities.rst:188 +#: ../../content/applications/sales/crm/pipeline/lost_opportunities.rst:192 msgid "When all the desired information has been entered in the :guilabel:`Mark Lost` pop-up window, click :guilabel:`Mark as Lost`." msgstr "" -#: ../../content/applications/sales/crm/acquire_leads/send_quotes.rst:174 +#: ../../content/applications/sales/crm/acquire_leads/send_quotes.rst:206 msgid "Upon clicking :guilabel:`Mark as Lost`, the pop-up window disappears, and Odoo returns to the opportunity form, where a new red :guilabel:`Lost` banner is now present in the upper-right corner of the opportunity." msgstr "" -#: ../../content/applications/sales/crm/acquire_leads/send_quotes.rst:178 +#: ../../content/applications/sales/crm/acquire_leads/send_quotes.rst:210 msgid "Once an opportunity is marked as *lost*, it is no longer considered active, and it is removed from the pipeline." msgstr "" -#: ../../content/applications/sales/crm/acquire_leads/send_quotes.rst:181 +#: ../../content/applications/sales/crm/acquire_leads/send_quotes.rst:213 msgid "In order to view a *lost* opportunity from the pipeline, click the :guilabel:`down arrow icon` to the right of the search bar, and select either :guilabel:`Lost` or :guilabel:`Archived` from the drop-down menu that appears." msgstr "" -#: ../../content/applications/sales/crm/acquire_leads/send_quotes.rst:186 +#: ../../content/applications/sales/crm/acquire_leads/send_quotes.rst:218 msgid "While opportunities that have been marked as *lost* are considered *Archived*, be advised that, in order for an opportunity to be included as *lost* in reporting, it **must** be specifically marked as *lost*, not *Archived*." msgstr "" @@ -1738,6 +1771,7 @@ msgstr "" #: ../../content/applications/sales/crm/performance/expected_revenue_report.rst:118 #: ../../content/applications/sales/crm/performance/forecast_report.rst:85 #: ../../content/applications/sales/crm/track_leads/unattended_leads_report.rst:145 +#: ../../content/applications/sales/members/members_analysis.rst:39 msgid "View results" msgstr "" @@ -1964,6 +1998,7 @@ msgid "Click the |pivot| to change to the pivot view, or the |list| to change to msgstr "" #: ../../content/applications/sales/crm/performance/forecast_report.rst:99 +#: ../../content/applications/sales/members/members_analysis.rst:49 msgid "The :ref:`pivot view ` can be used to view and analyze data in a more in-depth manner. Multiple measures can be selected, and data can be viewed by month, and by opportunity stage." msgstr "" @@ -2593,6 +2628,7 @@ msgid "On the list view, clicking :guilabel:`New` closes the list, and opens the msgstr "" #: ../../content/applications/sales/crm/performance/win_loss.rst:396 +#: ../../content/applications/sales/crm/track_leads/marketing_attribution.rst:77 msgid "Create reports" msgstr "" @@ -3002,7 +3038,7 @@ msgid "Buttons from the top of an opportunity record with the lost button emphas msgstr "" #: ../../content/applications/sales/crm/pipeline/lost_opportunities.rst:22 -#: ../../content/applications/sales/crm/pipeline/lost_opportunities.rst:181 +#: ../../content/applications/sales/crm/pipeline/lost_opportunities.rst:185 msgid "This opens the :guilabel:`Mark Lost` pop-up window. From the :guilabel:`Lost Reason` drop-down menu, choose an existing lost reason. If no applicable reason is available, create a new one by entering it into the :guilabel:`Lost Reason` field, and clicking :guilabel:`Create`." msgstr "" @@ -3026,51 +3062,55 @@ msgstr "" msgid "A lost opportunity with the lost banner added." msgstr "" -#: ../../content/applications/sales/crm/pipeline/lost_opportunities.rst:51 +#: ../../content/applications/sales/crm/pipeline/lost_opportunities.rst:49 +msgid "To mark an *inactive* (archived) opportunity as lost, set the :guilabel:`Probability` field to `0` percent." +msgstr "" + +#: ../../content/applications/sales/crm/pipeline/lost_opportunities.rst:55 msgid "Create/edit lost reasons" msgstr "" -#: ../../content/applications/sales/crm/pipeline/lost_opportunities.rst:53 +#: ../../content/applications/sales/crm/pipeline/lost_opportunities.rst:57 msgid "To create a new lost reason, or edit an existing one, navigate to :menuselection:`CRM app --> Configuration --> Lost Reasons`." msgstr "" -#: ../../content/applications/sales/crm/pipeline/lost_opportunities.rst:56 +#: ../../content/applications/sales/crm/pipeline/lost_opportunities.rst:60 msgid "To edit an existing lost reason:" msgstr "" -#: ../../content/applications/sales/crm/pipeline/lost_opportunities.rst:58 +#: ../../content/applications/sales/crm/pipeline/lost_opportunities.rst:62 msgid "Click on the reason to be edited to highlight it." msgstr "" -#: ../../content/applications/sales/crm/pipeline/lost_opportunities.rst:59 +#: ../../content/applications/sales/crm/pipeline/lost_opportunities.rst:63 msgid "Change the selected lost reason by editing the :guilabel:`Description` field." msgstr "" -#: ../../content/applications/sales/crm/pipeline/lost_opportunities.rst:60 +#: ../../content/applications/sales/crm/pipeline/lost_opportunities.rst:64 msgid "When finished, click :guilabel:`Save` in the upper-left corner." msgstr "" -#: ../../content/applications/sales/crm/pipeline/lost_opportunities.rst:62 +#: ../../content/applications/sales/crm/pipeline/lost_opportunities.rst:66 msgid "To create a new lost reason:" msgstr "" -#: ../../content/applications/sales/crm/pipeline/lost_opportunities.rst:64 +#: ../../content/applications/sales/crm/pipeline/lost_opportunities.rst:68 msgid "Click :guilabel:`New` in the upper-left corner of the :guilabel:`Lost Reasons` page." msgstr "" -#: ../../content/applications/sales/crm/pipeline/lost_opportunities.rst:65 +#: ../../content/applications/sales/crm/pipeline/lost_opportunities.rst:69 msgid "In the new blank line, click in the :guilabel:`Description` field, then type the new lost reason." msgstr "" -#: ../../content/applications/sales/crm/pipeline/lost_opportunities.rst:66 +#: ../../content/applications/sales/crm/pipeline/lost_opportunities.rst:70 msgid "When finished, click :guilabel:`Save`." msgstr "" -#: ../../content/applications/sales/crm/pipeline/lost_opportunities.rst:69 +#: ../../content/applications/sales/crm/pipeline/lost_opportunities.rst:73 msgid "View lost opportunities" msgstr "" -#: ../../content/applications/sales/crm/pipeline/lost_opportunities.rst:71 +#: ../../content/applications/sales/crm/pipeline/lost_opportunities.rst:75 msgid "To retrieve lost opportunities in Odoo *CRM*, open the :menuselection:`CRM app`. On the main :guilabel:`Pipeline` dashboard, click into the :guilabel:`Search...` bar at the top of the page, and remove all of the default filters." msgstr "" @@ -3078,23 +3118,23 @@ msgstr "" msgid "Search bar with lost filter emphasized." msgstr "" -#: ../../content/applications/sales/crm/pipeline/lost_opportunities.rst:79 +#: ../../content/applications/sales/crm/pipeline/lost_opportunities.rst:83 msgid "Open the :guilabel:`Filters` drop-down menu, by clicking the :guilabel:`🔻(triangle pointed down)` icon to the right of the :guilabel:`Search...` bar to open the drop-down menu containing :guilabel:`Filters`, :guilabel:`Group By`, and :guilabel:`Favorites` options, designated into respective columns." msgstr "" -#: ../../content/applications/sales/crm/pipeline/lost_opportunities.rst:84 +#: ../../content/applications/sales/crm/pipeline/lost_opportunities.rst:88 msgid "Select the :guilabel:`Lost` option from the :guilabel:`Filters` section. Upon selecting :guilabel:`Lost`, only the opportunities marked as `Lost` appear on the :guilabel:`Pipeline` page." msgstr "" -#: ../../content/applications/sales/crm/pipeline/lost_opportunities.rst:88 +#: ../../content/applications/sales/crm/pipeline/lost_opportunities.rst:92 msgid "Sort opportunities by lost reason" msgstr "" -#: ../../content/applications/sales/crm/pipeline/lost_opportunities.rst:90 +#: ../../content/applications/sales/crm/pipeline/lost_opportunities.rst:94 msgid "To filter opportunities by a specific lost reason, click the :guilabel:`🔻(triangle pointed down)` icon to the right of the :guilabel:`Search...` bar again to open the drop-down menu. In addition to the :guilabel:`Lost` filter, under the :guilabel:`Filters` column, click :guilabel:`Add Custom Filter`, which opens an :guilabel:`Add Custom Filter` pop-up window." msgstr "" -#: ../../content/applications/sales/crm/pipeline/lost_opportunities.rst:95 +#: ../../content/applications/sales/crm/pipeline/lost_opportunities.rst:99 msgid "On the :guilabel:`Add Custom Filter` pop-up window, click in the first field, and type `Lost Reason` in the :guilabel:`Search...` bar, or scroll to search through the list to locate it. Then, click into the next field, and select :guilabel:`=` from the drop-down menu. Click into the third field, and select a lost reason from the drop-down menu. Finally, click :guilabel:`Add`." msgstr "" @@ -3102,7 +3142,7 @@ msgstr "" msgid "Search bar with custom filter added for lost reason." msgstr "" -#: ../../content/applications/sales/crm/pipeline/lost_opportunities.rst:105 +#: ../../content/applications/sales/crm/pipeline/lost_opportunities.rst:109 msgid "To view results for more than one lost reason, select the operator :guilabel:`is in` in the second field of the custom filter in the :guilabel:`Add Custom Filter` pop-up window. Choosing this operator makes it possible to choose multiple lost reasons in the third field." msgstr "" @@ -3110,27 +3150,27 @@ msgstr "" msgid "Add Custom Filter pop-up with multiple lost reasons selected." msgstr "" -#: ../../content/applications/sales/crm/pipeline/lost_opportunities.rst:114 +#: ../../content/applications/sales/crm/pipeline/lost_opportunities.rst:118 msgid "Restore lost opportunities" msgstr "" -#: ../../content/applications/sales/crm/pipeline/lost_opportunities.rst:116 +#: ../../content/applications/sales/crm/pipeline/lost_opportunities.rst:120 msgid "To restore a lost opportunity, open the :menuselection:`CRM app` to reveal the :guilabel:`Pipeline` dashboard. Or, navigate to :menuselection:`CRM app --> Sales --> My Pipeline`. From here, click the :guilabel:`🔻(triangle pointed down)` icon to the right of the :guilabel:`Search...` bar to open the drop-down menu that contains :guilabel:`Filters`, :guilabel:`Group By`, and :guilabel:`Favorites` columns." msgstr "" -#: ../../content/applications/sales/crm/pipeline/lost_opportunities.rst:122 +#: ../../content/applications/sales/crm/pipeline/lost_opportunities.rst:126 msgid "Under the :guilabel:`Filters` column, select :guilabel:`Lost`. Doing so reveals all the lost opportunities on the :guilabel:`Pipeline` page." msgstr "" -#: ../../content/applications/sales/crm/pipeline/lost_opportunities.rst:126 +#: ../../content/applications/sales/crm/pipeline/lost_opportunities.rst:130 msgid "To see all opportunities in the database, remove the default :guilabel:`My Pipeline` filter from the :guilabel:`Search...` bar." msgstr "" -#: ../../content/applications/sales/crm/pipeline/lost_opportunities.rst:129 +#: ../../content/applications/sales/crm/pipeline/lost_opportunities.rst:133 msgid "Then, click on the Kanban card of the desired lost opportunity to restore, which opens that opportunity's detail form." msgstr "" -#: ../../content/applications/sales/crm/pipeline/lost_opportunities.rst:132 +#: ../../content/applications/sales/crm/pipeline/lost_opportunities.rst:136 msgid "From the lost opportunity's detail form, click :guilabel:`Restore` in the upper-left corner. Doing so removes the red :guilabel:`Lost` banner from the opportunity form, signifying the opportunity has been restored." msgstr "" @@ -3138,23 +3178,23 @@ msgstr "" msgid "Lost opportunity with emphasis on the Restore button." msgstr "" -#: ../../content/applications/sales/crm/pipeline/lost_opportunities.rst:141 +#: ../../content/applications/sales/crm/pipeline/lost_opportunities.rst:145 msgid "Restore multiple opportunities at once" msgstr "" -#: ../../content/applications/sales/crm/pipeline/lost_opportunities.rst:143 +#: ../../content/applications/sales/crm/pipeline/lost_opportunities.rst:147 msgid "To restore multiple opportunities at once, navigate to the main :guilabel:`Pipeline` dashboard in the *CRM* app, open the :guilabel:`Filters` drop-down menu, and select the :guilabel:`Lost` option." msgstr "" -#: ../../content/applications/sales/crm/pipeline/lost_opportunities.rst:146 +#: ../../content/applications/sales/crm/pipeline/lost_opportunities.rst:150 msgid "Next, select the list view option, represented by the :guilabel:`≣ (list)` icon in the upper-right corner. Doing so places all the opportunities from the :guilabel:`Pipeline` page in a list view. With the list view chosen, select the checkbox to the left of each opportunity to be restored." msgstr "" -#: ../../content/applications/sales/crm/pipeline/lost_opportunities.rst:150 +#: ../../content/applications/sales/crm/pipeline/lost_opportunities.rst:154 msgid "Once the desired opportunities have been selected, click the :guilabel:`⚙️ Actions` drop-down menu at the top of the :guilabel:`Pipeline` page. From the :guilabel:`⚙️ Actions` drop-down menu, select :guilabel:`Unarchive`." msgstr "" -#: ../../content/applications/sales/crm/pipeline/lost_opportunities.rst:154 +#: ../../content/applications/sales/crm/pipeline/lost_opportunities.rst:158 msgid "Doing so removes those selected opportunities from the :guilabel:`Pipeline` page because they no longer fit the :guilabel:`Lost` filter criteria. Delete the :guilabel:`Lost` filter from the search bar to reveal these newly-restored opportunities." msgstr "" @@ -3162,71 +3202,71 @@ msgstr "" msgid "Action button from list view with the Unarchive option emphasized." msgstr "" -#: ../../content/applications/sales/crm/pipeline/lost_opportunities.rst:163 +#: ../../content/applications/sales/crm/pipeline/lost_opportunities.rst:167 msgid "Manage lost leads" msgstr "" -#: ../../content/applications/sales/crm/pipeline/lost_opportunities.rst:165 +#: ../../content/applications/sales/crm/pipeline/lost_opportunities.rst:169 msgid "If *Leads* are enabled on a database, they can be marked as *lost* in the same manner as opportunities. Leads use the same :ref:`lost reasons ` as opportunities." msgstr "" -#: ../../content/applications/sales/crm/pipeline/lost_opportunities.rst:169 +#: ../../content/applications/sales/crm/pipeline/lost_opportunities.rst:173 msgid "To enable leads, navigate to :menuselection:`CRM app --> Configuration --> Settings` and check the :guilabel:`Leads` checkbox. Then, click :guilabel:`Save`. This adds a new :guilabel:`Leads` menu to the header menu bar at the top of the page." msgstr "" -#: ../../content/applications/sales/crm/pipeline/lost_opportunities.rst:174 +#: ../../content/applications/sales/crm/pipeline/lost_opportunities.rst:178 msgid "Mark a lead as lost" msgstr "" -#: ../../content/applications/sales/crm/pipeline/lost_opportunities.rst:176 +#: ../../content/applications/sales/crm/pipeline/lost_opportunities.rst:180 msgid "To mark a lead as lost, navigate to :menuselection:`CRM app --> Leads`, and select a lead from the list. Doing so reveals that lead's detail form." msgstr "" -#: ../../content/applications/sales/crm/pipeline/lost_opportunities.rst:179 +#: ../../content/applications/sales/crm/pipeline/lost_opportunities.rst:183 msgid "Then, click :guilabel:`Lost`, located at the top of the lead's detail form." msgstr "" -#: ../../content/applications/sales/crm/pipeline/lost_opportunities.rst:185 +#: ../../content/applications/sales/crm/pipeline/lost_opportunities.rst:189 msgid "Additional notes and comments can be added below the lost reason designated in the :guilabel:`Closing Note` field." msgstr "" -#: ../../content/applications/sales/crm/pipeline/lost_opportunities.rst:192 +#: ../../content/applications/sales/crm/pipeline/lost_opportunities.rst:196 msgid "Restore lost leads" msgstr "" -#: ../../content/applications/sales/crm/pipeline/lost_opportunities.rst:194 +#: ../../content/applications/sales/crm/pipeline/lost_opportunities.rst:198 msgid "To restore a lost lead, navigate to :menuselection:`CRM app --> Leads`, then click the :guilabel:`🔻 (triangle pointed down)` icon to the right of the :guilabel:`Search...` bar to open the drop-down menu that contains the :guilabel:`Filters`, :guilabel:`Group By`, and :guilabel:`Favorites` columns." msgstr "" -#: ../../content/applications/sales/crm/pipeline/lost_opportunities.rst:198 +#: ../../content/applications/sales/crm/pipeline/lost_opportunities.rst:202 msgid "Under the :guilabel:`Filters` column, select :guilabel:`Lost`. Doing so reveals all the lost leads on the :guilabel:`Leads` page." msgstr "" -#: ../../content/applications/sales/crm/pipeline/lost_opportunities.rst:201 +#: ../../content/applications/sales/crm/pipeline/lost_opportunities.rst:205 msgid "Then, click on the desired lost lead to restore, which opens that lead's detail form." msgstr "" -#: ../../content/applications/sales/crm/pipeline/lost_opportunities.rst:203 +#: ../../content/applications/sales/crm/pipeline/lost_opportunities.rst:207 msgid "From the lost lead's detail form, click :guilabel:`Restore` in the upper-left corner. Doing so removes the red :guilabel:`Lost` banner from the lead form, signifying the lead has been restored." msgstr "" -#: ../../content/applications/sales/crm/pipeline/lost_opportunities.rst:207 +#: ../../content/applications/sales/crm/pipeline/lost_opportunities.rst:211 msgid "Restore multiple leads at once" msgstr "" -#: ../../content/applications/sales/crm/pipeline/lost_opportunities.rst:209 +#: ../../content/applications/sales/crm/pipeline/lost_opportunities.rst:213 msgid "To restore multiple leads at once, navigate to :menuselection:`CRM app --> Leads`, open the :guilabel:`Filters` drop-down menu, and select the :guilabel:`Lost` option. Select the checkbox to the left of each lead to be restored." msgstr "" -#: ../../content/applications/sales/crm/pipeline/lost_opportunities.rst:213 +#: ../../content/applications/sales/crm/pipeline/lost_opportunities.rst:217 msgid "Once the desired leads have been selected, click the :guilabel:`⚙️ Actions` drop-down menu at the top of the :guilabel:`Leads` page. From the :guilabel:`⚙️ Actions` drop-down menu, select :guilabel:`Unarchive`." msgstr "" -#: ../../content/applications/sales/crm/pipeline/lost_opportunities.rst:217 +#: ../../content/applications/sales/crm/pipeline/lost_opportunities.rst:221 msgid "Doing so removes those selected leads from the :guilabel:`Leads` page because they no longer fit the :guilabel:`Lost` filter criteria. Delete the :guilabel:`Lost` filter from the :guilabel:`Search...` bar to reveal these newly-restored leads." msgstr "" -#: ../../content/applications/sales/crm/pipeline/lost_opportunities.rst:222 +#: ../../content/applications/sales/crm/pipeline/lost_opportunities.rst:226 msgid ":doc:`../performance/win_loss`" msgstr "" @@ -3379,26 +3419,26 @@ msgid "Comparing similar leads and opportunities" msgstr "" #: ../../content/applications/sales/crm/pipeline/merge_similar.rst:28 -msgid "To compare the details of similar leads/opportunities, navigate to :menuselection:`CRM app --> Pipeline` or :menuselection:`CRM app --> Leads`. Open a lead or opportunity, and click the Doing so opens a Kanban view that only displays similar leads/opportunities. Click on a card to view the details for the lead/opportunity, and confirm if they should be merged." +msgid "To compare the details of similar leads/opportunities, navigate to :menuselection:`CRM app --> Pipeline` or :menuselection:`CRM app --> Leads`. Open a lead or opportunity, and click the :guilabel:`Similar Leads` smart button. Doing so opens a Kanban view that only displays similar leads/opportunities. Click on a card to view the details for the lead/opportunity, and confirm if they should be merged." msgstr "" -#: ../../content/applications/sales/crm/pipeline/merge_similar.rst:34 +#: ../../content/applications/sales/crm/pipeline/merge_similar.rst:35 msgid "Merging similar leads and opportunities" msgstr "" -#: ../../content/applications/sales/crm/pipeline/merge_similar.rst:42 -msgid "After confirming that the leads/opportunities should be merged, return to the Kanban view using the breadcrumb link, or by clicking the :guilabel:`Similar Leads` smart button. Click the :guilabel:`≣ (view list)` icon to change to list view." +#: ../../content/applications/sales/crm/pipeline/merge_similar.rst:43 +msgid "After confirming that the leads/opportunities should be merged, return to the Kanban view using the breadcrumb link, or by clicking the :guilabel:`Similar Leads` smart button. Click the :icon:`oi-view-list` :guilabel:`(list)` icon to change to list view." msgstr "" -#: ../../content/applications/sales/crm/pipeline/merge_similar.rst:46 -msgid "Check the box on the left of the page for the leads/opportunities to be merged. Then, click the :guilabel:`⚙️ Actions` icon at the top of the page, to reveal a drop-down menu. From that drop-down menu, select the :guilabel:`Merge` option to merge the selected opportunities or leads." +#: ../../content/applications/sales/crm/pipeline/merge_similar.rst:47 +msgid "Check the box on the left of the page for the leads/opportunities to be merged. Then, click the :icon:`fa-cog` :guilabel:`Actions` icon at the top of the page, to reveal a drop-down menu. From that drop-down menu, select the :guilabel:`Merge` option to merge the selected opportunities or leads." msgstr "" -#: ../../content/applications/sales/crm/pipeline/merge_similar.rst:50 -msgid "When :guilabel:`Merge` is selected from the :guilabel:`⚙️ Actions` drop-down menu, a :guilabel:`Merge` pop-up modal appears. In that pop-up modal, under the :guilabel:`Assign opportunities to` heading, select a :guilabel:`Salesperson` and :guilabel:`Sales Team` from the appropriate drop-down menus." +#: ../../content/applications/sales/crm/pipeline/merge_similar.rst:52 +msgid "When :guilabel:`Merge` is selected from the :icon:`fa-cog` :guilabel:`Actions` drop-down menu, a :guilabel:`Merge` pop-up modal appears. In that pop-up modal, under the :guilabel:`Assign opportunities to` heading, select a :guilabel:`Salesperson` and :guilabel:`Sales Team` from the appropriate drop-down menus." msgstr "" -#: ../../content/applications/sales/crm/pipeline/merge_similar.rst:55 +#: ../../content/applications/sales/crm/pipeline/merge_similar.rst:57 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 "" @@ -3406,59 +3446,59 @@ msgstr "" msgid "List of similar leads and opportunities selected for merge in the CRM app." msgstr "" -#: ../../content/applications/sales/crm/pipeline/merge_similar.rst:63 +#: ../../content/applications/sales/crm/pipeline/merge_similar.rst:65 msgid "Merging is an irreversible action. Do **not** merge leads/opportunities unless absolutely certain they should be combined." msgstr "" -#: ../../content/applications/sales/crm/pipeline/merge_similar.rst:67 +#: ../../content/applications/sales/crm/pipeline/merge_similar.rst:69 msgid "When leads/opportunities should not be merged" msgstr "" -#: ../../content/applications/sales/crm/pipeline/merge_similar.rst:69 +#: ../../content/applications/sales/crm/pipeline/merge_similar.rst:71 msgid "There may be instances where a similar lead or opportunity is identified, but should *not* be merged. These circumstances vary, based on the processes of the sales team and organization. Some potential scenarios are listed below." msgstr "" -#: ../../content/applications/sales/crm/pipeline/merge_similar.rst:74 +#: ../../content/applications/sales/crm/pipeline/merge_similar.rst:76 msgid "Lost leads" msgstr "" -#: ../../content/applications/sales/crm/pipeline/merge_similar.rst:76 +#: ../../content/applications/sales/crm/pipeline/merge_similar.rst:78 msgid "If a lead/opportunity has been marked as :doc:`lost `, it can still be merged with an active lead or opportunity. The resulting lead/opportunity is marked active, and added to the pipeline." msgstr "" -#: ../../content/applications/sales/crm/pipeline/merge_similar.rst:81 +#: ../../content/applications/sales/crm/pipeline/merge_similar.rst:83 msgid "Different contact within an organization" msgstr "" -#: ../../content/applications/sales/crm/pipeline/merge_similar.rst:83 +#: ../../content/applications/sales/crm/pipeline/merge_similar.rst:85 msgid "Leads/opportunities from the same organization, but with different points of contact, may not have the same needs. In this case, it is beneficial to *not* merge these records, though assigning the same salesperson, or sales team, can prevent duplicated work and miscommunication." msgstr "" -#: ../../content/applications/sales/crm/pipeline/merge_similar.rst:88 +#: ../../content/applications/sales/crm/pipeline/merge_similar.rst:90 msgid "Existing duplicates with more than one salesperson" msgstr "" -#: ../../content/applications/sales/crm/pipeline/merge_similar.rst:90 +#: ../../content/applications/sales/crm/pipeline/merge_similar.rst:92 msgid "If more than one lead/opportunity exists in the database, there may be multiple salespeople assigned to them, who are actively working on them independently. While these leads/opportunities may need to be managed separately, it is recommended that any affected salespeople be tagged in an internal note for visibility." msgstr "" -#: ../../content/applications/sales/crm/pipeline/merge_similar.rst:96 +#: ../../content/applications/sales/crm/pipeline/merge_similar.rst:98 msgid "Contact information is similar but not exact" msgstr "" -#: ../../content/applications/sales/crm/pipeline/merge_similar.rst:98 +#: ../../content/applications/sales/crm/pipeline/merge_similar.rst:100 msgid "Similar leads and opportunities are identified by comparing the email addresses and phone numbers of the associated contacts. However, if the email address is *similar*, but not *exact*, they may need to remain independent." msgstr "" -#: ../../content/applications/sales/crm/pipeline/merge_similar.rst:103 +#: ../../content/applications/sales/crm/pipeline/merge_similar.rst:105 msgid "Three different leads were added to the pipeline and assigned to different salespeople. They were identified as *Similar Leads* due to the email addresses of the contacts." msgstr "" -#: ../../content/applications/sales/crm/pipeline/merge_similar.rst:106 +#: ../../content/applications/sales/crm/pipeline/merge_similar.rst:108 msgid "Two of the leads appear to come from the same individual, `Robin`, and have identical email addresses. These leads should be merged." msgstr "" -#: ../../content/applications/sales/crm/pipeline/merge_similar.rst:109 +#: ../../content/applications/sales/crm/pipeline/merge_similar.rst:111 msgid "The third lead has the same email domain, but the address is different, as is the contact name. While this lead is most likely from the same organization, it is from a different contact, and should **not** be merged." msgstr "" @@ -3710,6 +3750,178 @@ msgstr "" msgid "To manually assign leads to this sales team, click on the :guilabel:`Assign Leads` button at the top of the sales team configuration page. This will assign any leads that are currently unassigned and match this team's specified domain." msgstr "" +#: ../../content/applications/sales/crm/track_leads/marketing_attribution.rst:3 +msgid "Marketing attribution reports" +msgstr "" + +#: ../../content/applications/sales/crm/track_leads/marketing_attribution.rst:5 +msgid "Use the Odoo *CRM* app to compile a *marketing attribution report*, which analyzes the source of leads, and groups them in such a way as to calculate marketing's overall impact on lead generation, attribution, won rate, and more." +msgstr "" + +#: ../../content/applications/sales/crm/track_leads/marketing_attribution.rst:10 +msgid "Leads Analysis dashboard" +msgstr "" + +#: ../../content/applications/sales/crm/track_leads/marketing_attribution.rst:12 +msgid "Begin by navigating to the :guilabel:`Leads Analysis` dashboard by going to :menuselection:`CRM app --> Reporting --> Leads`." +msgstr "" + +#: ../../content/applications/sales/crm/track_leads/marketing_attribution.rst:16 +msgid "Reports can also be run on the :menuselection:`CRM app --> Leads` dashboard, which is **only** accessible if the *Leads* feature has been activated on the *Settings* page." +msgstr "" + +#: ../../content/applications/sales/crm/track_leads/marketing_attribution.rst:19 +msgid "If the *Leads* feature has **not** been activated, the :menuselection:`CRM app --> Sales --> My Pipeline` dashboard can also be used to run reports." +msgstr "" + +#: ../../content/applications/sales/crm/track_leads/marketing_attribution.rst:22 +msgid "Both dashboards contain the necessary *Filters* and *Group By* criteria to run an attribution report." +msgstr "" + +#: ../../content/applications/sales/crm/track_leads/marketing_attribution.rst:26 +msgid ":doc:`Convert leads into opportunities <../acquire_leads/convert>`" +msgstr "" + +#: ../../content/applications/sales/crm/track_leads/marketing_attribution.rst:27 +msgid ":doc:`Create leads <../acquire_leads/email_manual>`" +msgstr "" + +#: ../../content/applications/sales/crm/track_leads/marketing_attribution.rst:-1 +msgid "Open the CRM app and click on the Reporting tab at the top of the page, then click Leads." +msgstr "" + +#: ../../content/applications/sales/crm/track_leads/marketing_attribution.rst:33 +msgid "The :icon:`fa-area-chart` :guilabel:`(graph)` view is shown, by default, with :guilabel:`Active or Inactive` and :guilabel:`Created on: [current year]` filters active in the :guilabel:`Search...` bar. The graph visualization displays the number of leads generated, by month and by sales team, with each sales team attributed to its own color per month shown." +msgstr "" + +#: ../../content/applications/sales/crm/track_leads/marketing_attribution.rst:38 +msgid "Switch the view to the :icon:`oi-view-list` :guilabel:`(list)` option, by clicking the respective icon located at the top-right of the dashboard. This allows leads to easily be displayed in the grouping set by the *Group By* parameters." +msgstr "" + +#: ../../content/applications/sales/crm/track_leads/marketing_attribution.rst:-1 +msgid "Click the button with four horizontal lines on the top right of the Leads Analysis page." +msgstr "" + +#: ../../content/applications/sales/crm/track_leads/marketing_attribution.rst:47 +msgid "Add UTM parameters" +msgstr "" + +#: ../../content/applications/sales/crm/track_leads/marketing_attribution.rst:49 +msgid "*Urchin Tracking Modules (UTMs)* are snippets of text embedded in URLs that are used to track visitor data. This includes parameters relating to how a visitor reached the link, such as the type of website visited, and/or marketing campaign the visit came from." +msgstr "" + +#: ../../content/applications/sales/crm/track_leads/marketing_attribution.rst:53 +msgid "Odoo can use these UTMs as parameters in the marketing attribution report to track the metrics and performance of marketing campaigns." +msgstr "" + +#: ../../content/applications/sales/crm/track_leads/marketing_attribution.rst:57 +msgid "Create UTMs" +msgstr "" + +#: ../../content/applications/sales/crm/track_leads/marketing_attribution.rst:59 +msgid "The :doc:`link tracker <../../../websites/website/reporting/link_tracker>` in Odoo can be used to create and configure UTMs." +msgstr "" + +#: ../../content/applications/sales/crm/track_leads/marketing_attribution.rst:62 +msgid "UTMs can also be automatically generated by the :doc:`Email Marketing <../../../marketing/email_marketing>` and :doc:`Marketing Automation <../../../marketing/marketing_automation>` apps." +msgstr "" + +#: ../../content/applications/sales/crm/track_leads/marketing_attribution.rst:66 +msgid "The UTM parameters used in a marketing attribution report are *Medium*, *Source*, and *Campaign*, in descending order of coverage." +msgstr "" + +#: ../../content/applications/sales/crm/track_leads/marketing_attribution.rst:69 +msgid "*Medium* is the UTM with the widest coverage, and is used to identify the medium used to access the link. This can include mediums such as social media, email, or cost per click (CPC)." +msgstr "" + +#: ../../content/applications/sales/crm/track_leads/marketing_attribution.rst:71 +msgid "*Source* is more narrow, and is used to identify the source of traffic. For example, the name of a website, search engine used, or a specific social media platform." +msgstr "" + +#: ../../content/applications/sales/crm/track_leads/marketing_attribution.rst:73 +msgid "*Campaign* is the most narrow, and can track specific marketing campaigns by name. This can include a contest or product name, type of sale, etc." +msgstr "" + +#: ../../content/applications/sales/crm/track_leads/marketing_attribution.rst:79 +msgid "To start creating a report, click the :icon:`fa-caret-down` :guilabel:`(down arrow)` to the right of the :guilabel:`Search...` bar to see the list of filtering and grouping parameters." +msgstr "" + +#: ../../content/applications/sales/crm/track_leads/marketing_attribution.rst:82 +msgid ":guilabel:`Filters`, located in the left column of the search options, can be used to keep only the results that fit the filter. For example, selecting the :guilabel:`Won` filter only shows leads that have been won in the attribution report." +msgstr "" + +#: ../../content/applications/sales/crm/track_leads/marketing_attribution.rst:86 +msgid ":guilabel:`Group By`, found in the middle column, is used to organize the results into groups, and can be used with or without filters." +msgstr "" + +#: ../../content/applications/sales/crm/track_leads/marketing_attribution.rst:-1 +msgid "Select any number of filters and groups in the search options." +msgstr "" + +#: ../../content/applications/sales/crm/track_leads/marketing_attribution.rst:94 +msgid "Setting multiple :guilabel:`Group By` options creates nested groups, according to which option is selected first. For example, selecting :guilabel:`Medium`, followed by :guilabel:`Source`, and then :guilabel:`Campaign`, in :guilabel:`Group By` column, sorts all results *first* by medium, *then* by the specific sources in each medium, followed by the campaigns in each source." +msgstr "" + +#: ../../content/applications/sales/crm/track_leads/marketing_attribution.rst:99 +msgid "This can be verified by looking at the direction, and order, of the selections in the group tile that appears in the :guilabel:`Search...` bar." +msgstr "" + +#: ../../content/applications/sales/crm/track_leads/marketing_attribution.rst:0 +msgid "The text in the tile is `Country > City`, showing that city is a subgroup of country." +msgstr "" + +#: ../../content/applications/sales/crm/track_leads/marketing_attribution.rst:107 +msgid "For a useful first report:" +msgstr "" + +#: ../../content/applications/sales/crm/track_leads/marketing_attribution.rst:109 +msgid "#. From the :guilabel:`Filters` column, select the :guilabel:`Active` filter to view only leads that are still marked as active. #. From the :guilabel:`Group By` column, select (in this specific order) :guilabel:`Source`, followed by the :guilabel:`City` or :guilabel:`Country`, depending on which grouping is more relevant." +msgstr "" + +#: ../../content/applications/sales/crm/track_leads/marketing_attribution.rst:-1 +msgid "Each lead is now sorted by source, followed by city or country." +msgstr "" + +#: ../../content/applications/sales/crm/track_leads/marketing_attribution.rst:119 +msgid "This report contains all active leads, grouped first by the source of the lead, then by the city or country each lead is from. This is useful to see the density of active opportunities sorted by location." +msgstr "" + +#: ../../content/applications/sales/crm/track_leads/marketing_attribution.rst:123 +msgid "With this data, marketing campaigns, such as conferences or billboards, can be targeted to the locations generating the largest amount of potential revenue. Similarly, more attention can be put toward increasing outreach in locations where existing marketing campaigns are less effective." +msgstr "" + +#: ../../content/applications/sales/crm/track_leads/marketing_attribution.rst:129 +msgid "Export reports" +msgstr "" + +#: ../../content/applications/sales/crm/track_leads/marketing_attribution.rst:131 +msgid "To set the measures of the report, begin by navigating to the :icon:`oi-view-pivot` :guilabel:`(pivot view)` on the :guilabel:`Leads Analysis` dashboard." +msgstr "" + +#: ../../content/applications/sales/crm/track_leads/marketing_attribution.rst:134 +msgid "Click the :guilabel:`Measures` button to view the available measures of the report. Select the desired measures from the drop-down menu (multiple measures can be selected), and verify the measures, filters, and groups are all displayed correctly in the pivot table. This ensures the data is ready for export." +msgstr "" + +#: ../../content/applications/sales/crm/track_leads/marketing_attribution.rst:139 +msgid "To quickly export the data in a list, as a .xlsx file, navigate to the :icon:`oi-view-list` :guilabel:`(list view)`. Click on the :guilabel:`Actions` :icon:`fa-cog` :guilabel:`(gear)` icon, located to the right of :guilabel:`Lead Analysis` in the top-left of the page, and click :icon:`fa-upload` :guilabel:`Export All`. The report downloads automatically as a .xlsx file." +msgstr "" + +#: ../../content/applications/sales/crm/track_leads/marketing_attribution.rst:144 +msgid "For more export options, the report can be exported to the Odoo *Documents* app. From the :icon:`oi-view-list` :guilabel:`(list view)` of :guilabel:`Leads Analysis` page, begin by clicking the :guilabel:`Actions` :icon:`fa-cog` :guilabel:`(gear)` icon again. Now, navigate to :icon:`fa-table` :guilabel:`Spreadsheet`, and click :icon:`oi-view-list` :guilabel:`Insert list in spreadsheet`. A pop-up window titled, :guilabel:`Select a spreadsheet to insert your list.` appears." +msgstr "" + +#: ../../content/applications/sales/crm/track_leads/marketing_attribution.rst:150 +msgid "The report can be renamed using the `Name of the list` field, if desired. The number of items on the report can be set with the field labeled: `Insert the first _ records of the list`. Next, select either a new :guilabel:`Blank spreadsheet`, or export into an existing spreadsheet. Finally, click the :guilabel:`Confirm` button." +msgstr "" + +#: ../../content/applications/sales/crm/track_leads/marketing_attribution.rst:-1 +msgid "Set the name, number of records, and location of the export in the option menu." +msgstr "" + +#: ../../content/applications/sales/crm/track_leads/marketing_attribution.rst:159 +msgid "To export the report as a .xlsx file, for use in an external spreadsheets program, click the :guilabel:`Actions` :icon:`fa-cog` :guilabel:`(gear)` icon, and select the :icon:`fa-upload` :guilabel:`Export All` option. If prompted, choose a file location, name the file, then click :guilabel:`Save`." +msgstr "" + #: ../../content/applications/sales/crm/track_leads/quality_leads_report.rst:3 msgid "Quality leads report" msgstr "" @@ -4289,6 +4501,190 @@ msgstr "" msgid ":doc:`Activities <../../../essentials/activities>`" msgstr "" +#: ../../content/applications/sales/members.rst:5 +msgid "Members" +msgstr "" + +#: ../../content/applications/sales/members.rst:7 +msgid "The *Members* application is where all operations related to memberships can be configured and managed. The *Members* app integrates with the *Sales* and *Accounting* applications to sell and invoice memberships directly to customers." +msgstr "" + +#: ../../content/applications/sales/members.rst:12 +msgid "Membership products" +msgstr "" + +#: ../../content/applications/sales/members.rst:14 +msgid "To create a new membership product, navigate to :menuselection:`Members app --> Configuration --> Membership Products`, and click :guilabel:`New` to open a blank product record." +msgstr "" + +#: ../../content/applications/sales/members.rst:17 +msgid "Complete the blank form with the necessary information, including the :guilabel:`Membership Duration`." +msgstr "" + +#: ../../content/applications/sales/members.rst:21 +msgid "Membership products require a start and end date, as they are used to determine :ref:`membership status `. Membership products can be sold *before* their active start date." +msgstr "" + +#: ../../content/applications/sales/members.rst:-1 +msgid "A new membership product in the members app." +msgstr "" + +#: ../../content/applications/sales/members.rst:29 +msgid "Membership products can be added to a sales order, and invoiced as regular products or subscriptions." +msgstr "" + +#: ../../content/applications/sales/members.rst:33 +msgid "Activate a membership" +msgstr "" + +#: ../../content/applications/sales/members.rst:35 +msgid "To activate a membership from the *Contacts* application, navigate to :menuselection:`Contacts app`, and click on a contact to open that specific contact's detail form." +msgstr "" + +#: ../../content/applications/sales/members.rst:38 +msgid "From the resulting contact form, open the :guilabel:`Membership` tab, and click :guilabel:`Buy Membership`." +msgstr "" + +#: ../../content/applications/sales/members.rst:41 +msgid "On the :guilabel:`Join Membership` pop-up window that appears, select a :guilabel:`Membership` from the drop-down menu. Then, configure a :guilabel:`Member Price`." +msgstr "" + +#: ../../content/applications/sales/members.rst:44 +msgid "Click :guilabel:`Invoice Membership` when both fields are filled in. Doing so reveals a :guilabel:`Membership Invoices` page, wherein invoices can be confirmed and completed." +msgstr "" + +#: ../../content/applications/sales/members.rst:47 +msgid "Alternatively, to offer a free membership, tick the :guilabel:`Free Member` checkbox, in the :guilabel:`Membership` tab of a contact form." +msgstr "" + +#: ../../content/applications/sales/members.rst:53 +msgid "Membership status" +msgstr "" + +#: ../../content/applications/sales/members.rst:55 +msgid "The :guilabel:`Current Membership Status` is listed on the :guilabel:`Membership` tab of each contact record:" +msgstr "" + +#: ../../content/applications/sales/members.rst:58 +msgid ":guilabel:`Non Member`: a partner who has **not** applied for membership." +msgstr "" + +#: ../../content/applications/sales/members.rst:59 +msgid ":guilabel:`Cancelled Member`: a member who has cancelled their membership." +msgstr "" + +#: ../../content/applications/sales/members.rst:60 +msgid ":guilabel:`Old Member`: a member whose membership end date has passed." +msgstr "" + +#: ../../content/applications/sales/members.rst:61 +msgid ":guilabel:`Waiting Member`: a member who has applied for membership, but whose invoice has not yet been created." +msgstr "" + +#: ../../content/applications/sales/members.rst:63 +msgid ":guilabel:`Invoiced Member`: a member whose invoice has been created, but has not been paid." +msgstr "" + +#: ../../content/applications/sales/members.rst:64 +msgid ":guilabel:`Paid Member`: a member who has paid the membership fee." +msgstr "" + +#: ../../content/applications/sales/members.rst:67 +msgid "Publish members directory" +msgstr "" + +#: ../../content/applications/sales/members.rst:69 +msgid "To publish a list of active members on the website, the *Online Members Directory* application must first be :ref:`installed `. After installing the module, add the `/members` page to the website's menu by :doc:`editing the website menu <../websites/website/pages/menus>`." +msgstr "" + +#: ../../content/applications/sales/members.rst:-1 +msgid "The Online Members directory module in Odoo." +msgstr "" + +#: ../../content/applications/sales/members.rst:78 +msgid "Publish individual members" +msgstr "" + +#: ../../content/applications/sales/members.rst:80 +msgid "Return to :menuselection:`CRM app --> Sales --> Customers`, and click the Kanban card for a member. From the resulting customer form that appears, click the :guilabel:`Go to Website` smart button at the top of the page to open the member's webpage." +msgstr "" + +#: ../../content/applications/sales/members.rst:84 +msgid "Click the :icon:`fa-pencil` :guilabel:`Edit` button to reveal a sidebar of editing tools. After making any necessary changes to the page, click :guilabel:`Save`. At the top of the page, slide the :guilabel:`Unpublished` toggle to the active, :guilabel:`Published` position." +msgstr "" + +#: ../../content/applications/sales/members.rst:88 +msgid "Repeat these steps for all desired members." +msgstr "" + +#: ../../content/applications/sales/members/members_analysis.rst:3 +msgid "Members analysis" +msgstr "" + +#: ../../content/applications/sales/members/members_analysis.rst:9 +msgid "The *Members Analysis* report provides a detailed overview of all memberships sold and managed within the *Members* application." +msgstr "" + +#: ../../content/applications/sales/members/members_analysis.rst:12 +msgid "To access the *Memberships Analysis* report, navigate to :menuselection:`Members app --> Reporting`." +msgstr "" + +#: ../../content/applications/sales/members/members_analysis.rst:15 +msgid "Navigate the report" +msgstr "" + +#: ../../content/applications/sales/members/members_analysis.rst:17 +msgid "The default *Members Analysis* report displays a bar chart, measuring the :guilabel:`Quantity` of memberships against the amount of :guilabel:`Revenue Done`. The data is grouped by the assigned salesperson, then by the month the membership begins." +msgstr "" + +#: ../../content/applications/sales/members/members_analysis.rst:-1 +msgid "A sample of the members analysis report." +msgstr "" + +#: ../../content/applications/sales/members/members_analysis.rst:25 +msgid "Additional :ref:`Group By ` options include the following:" +msgstr "" + +#: ../../content/applications/sales/members/members_analysis.rst:27 +msgid ":guilabel:`Salesperson`: the internal user in charge of the contact. This information is managed in the *Salesperson* field on the *Sales & Purchase* tab on the contact's record." +msgstr "" + +#: ../../content/applications/sales/members/members_analysis.rst:29 +msgid ":guilabel:`Associated Partner`: the contact listed as the *Associated Member* on the *Membership* tab on the contact's record." +msgstr "" + +#: ../../content/applications/sales/members/members_analysis.rst:31 +msgid ":guilabel:`Membership Product`: the type of membership assigned to a contact. This includes both purchased memberships and free memberships." +msgstr "" + +#: ../../content/applications/sales/members/members_analysis.rst:33 +msgid ":guilabel:`Current Membership State`: the status of the membership." +msgstr "" + +#: ../../content/applications/sales/members/members_analysis.rst:34 +msgid ":guilabel:`Company`: the company the membership is purchased through. This option only appears in multi-company databases." +msgstr "" + +#: ../../content/applications/sales/members/members_analysis.rst:36 +msgid ":guilabel:`Month`: the month the membership began." +msgstr "" + +#: ../../content/applications/sales/members/members_analysis.rst:41 +msgid "Click the :icon:`fa-area-chart` :guilabel:`(graph)` icon to change to graph view. Then, click the corresponding icon at the top of the report to switch to a :icon:`fa-bar-chart` :guilabel:`(bar chart)`, :icon:`fa-line-chart` :guilabel:`(line chart)`, or :icon:`fa-pie-chart` :guilabel:`(pie chart)`." +msgstr "" + +#: ../../content/applications/sales/members/members_analysis.rst:46 +msgid "Click the |pivot| to change to the pivot view." +msgstr "" + +#: ../../content/applications/sales/members/members_analysis.rst:54 +msgid ":ref:`search/custom-filters`" +msgstr "" + +#: ../../content/applications/sales/members/members_analysis.rst:55 +msgid ":ref:`search/favorites`" +msgstr "" + #: ../../content/applications/sales/point_of_sale.rst:6 msgid "Point of Sale" msgstr "" @@ -5267,10 +5663,14 @@ msgid ":doc:`Vantiv configuration `" msgstr "" #: ../../content/applications/sales/point_of_sale/payment_methods/terminals.rst:28 +msgid ":doc:`Viva Wallet configuration `" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals.rst:29 msgid ":doc:`Worldline configuration `" msgstr "" -#: ../../content/applications/sales/point_of_sale/payment_methods/terminals.rst:30 +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals.rst:31 msgid "Once the terminal is configured, you can :doc:`create the corresponding payment method and add it to the POS <../payment_methods>`." msgstr "" @@ -5371,6 +5771,7 @@ msgstr "" #: ../../content/applications/sales/point_of_sale/payment_methods/terminals/six.rst:53 #: ../../content/applications/sales/point_of_sale/payment_methods/terminals/stripe.rst:22 #: ../../content/applications/sales/point_of_sale/payment_methods/terminals/vantiv.rst:20 +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/viva_wallet.rst:81 #: ../../content/applications/sales/point_of_sale/payment_methods/terminals/worldline.rst:72 msgid "Configure the payment method" msgstr "" @@ -5388,6 +5789,7 @@ msgstr "" #: ../../content/applications/sales/point_of_sale/payment_methods/terminals/six.rst:68 #: ../../content/applications/sales/point_of_sale/payment_methods/terminals/stripe.rst:93 #: ../../content/applications/sales/point_of_sale/payment_methods/terminals/vantiv.rst:41 +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/viva_wallet.rst:123 #: ../../content/applications/sales/point_of_sale/payment_methods/terminals/worldline.rst:96 msgid "Pay with a payment terminal" msgstr "" @@ -5398,11 +5800,13 @@ msgstr "" #: ../../content/applications/sales/point_of_sale/payment_methods/terminals/adyen.rst:0 #: ../../content/applications/sales/point_of_sale/payment_methods/terminals/stripe.rst:0 +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/viva_wallet.rst:0 msgid "In case of connection issues between Odoo and the payment terminal, force the payment by clicking on :guilabel:`Force Done`, which allows you to validate the order." msgstr "" #: ../../content/applications/sales/point_of_sale/payment_methods/terminals/adyen.rst:0 #: ../../content/applications/sales/point_of_sale/payment_methods/terminals/stripe.rst:0 +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/viva_wallet.rst:0 msgid "This option is only available after receiving an error message informing you that the connection failed." msgstr "" @@ -5631,6 +6035,7 @@ msgid "Click :guilabel:`Don't forget to complete Stripe connect before using thi msgstr "" #: ../../content/applications/sales/point_of_sale/payment_methods/terminals/stripe.rst:-1 +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/viva_wallet.rst:-1 msgid "payment method creation form" msgstr "" @@ -5691,6 +6096,7 @@ msgid "You must enter the admin PIN code to access your payment terminal setting msgstr "" #: ../../content/applications/sales/point_of_sale/payment_methods/terminals/stripe.rst:86 +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/viva_wallet.rst:116 msgid "Link the payment method to a POS" msgstr "" @@ -5775,9 +6181,150 @@ msgid "Once the payment method is created, you can select it in your POS setting msgstr "" #: ../../content/applications/sales/point_of_sale/payment_methods/terminals/vantiv.rst:43 +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/viva_wallet.rst:125 msgid "When processing a payment, select the related payment method. Check the amount and click on :guilabel:`Send`. Once the payment is successful, the status changes to :guilabel:`Payment Successful`." msgstr "" +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/viva_wallet.rst:3 +msgid "Viva Wallet" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/viva_wallet.rst:5 +msgid "Connecting a **Viva Wallet** :doc:`payment terminal <../terminals>` allows you to offer a fluid payment flow to your customers and ease the work of your cashiers." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/viva_wallet.rst:9 +msgid "Viva Wallet lets you turn your phone into a mobile card reader: `Tap On Phone `_." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/viva_wallet.rst:15 +msgid "Start by creating your Viva Wallet account on `Viva Wallet's website `_." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/viva_wallet.rst:18 +msgid "Locate your Viva Wallet credentials" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/viva_wallet.rst:20 +msgid "When configuring Viva Wallet in Point of Sale, you need to use specific credentials that are available in your Viva Wallet account. These credentials include your :ref:`Merchant ID `, :ref:`API key `, :ref:`POS API credentials `, and :ref:`Terminal ID ` number." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/viva_wallet.rst:28 +msgid "Merchant ID and API key" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/viva_wallet.rst:30 +msgid "Locate your `Merchant ID and API key following the Viva documentation `_. Then, save the keys and paste them into the Odoo :guilabel:`Merchant ID` and :guilabel:`API Key` fields :ref:`when creating the payment method `." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/viva_wallet.rst:-1 +msgid "merchant ID and API key fields" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/viva_wallet.rst:39 +msgid "These credentials are used for APIs that authenticate with Basic Auth." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/viva_wallet.rst:44 +msgid "POS API credentials" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/viva_wallet.rst:46 +msgid "Locate and generate your `POS API credentials following the Viva documentation `_. Then, save the keys and paste them in the Odoo :guilabel:`Client secret` and :guilabel:`Client ID` fields :ref:`when creating the payment method `." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/viva_wallet.rst:52 +msgid "These credentials are only displayed once. Ensure you keep a copy to secure them." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/viva_wallet.rst:-1 +msgid "Client secret and client ID fields" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/viva_wallet.rst:58 +msgid "These credentials are used for Android and iOS POS Activation requests, as well as the Cloud Terminal API." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/viva_wallet.rst:64 +msgid "Terminal ID" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/viva_wallet.rst:66 +msgid "Your terminal ID number is used to identify your terminal. To find it:" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/viva_wallet.rst:68 +msgid "Go to your Viva Wallet account and select the relevant account." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/viva_wallet.rst:69 +msgid "Go to :menuselection:`Sales --> Physical payments --> Card terminals` in the navigation menu." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/viva_wallet.rst:71 +msgid "The terminal ID number is located under the :guilabel:`Terminal ID (TID)` column. Save it to paste it into the :guilabel:`Terminal ID` field :ref:`when creating the payment method `." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/viva_wallet.rst:-1 +msgid "Viva terminal ID" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/viva_wallet.rst:83 +msgid ":doc:`Activate the POS Viva Wallet module <../../../../general/apps_modules>` to enable the payment terminal." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/viva_wallet.rst:85 +msgid ":doc:`Create the related payment method <../../payment_methods>` by going to :menuselection:`Point of Sale --> Configuration --> Payment Methods` and clicking :guilabel:`New`." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/viva_wallet.rst:88 +msgid "Set the journal type as :guilabel:`Bank`." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/viva_wallet.rst:89 +msgid "Select :guilabel:`Viva Wallet` in the :guilabel:`Use a Payment Terminal` field." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/viva_wallet.rst:90 +msgid "Fill in the mandatory fields with your:" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/viva_wallet.rst:92 +msgid ":ref:`Merchant ID and API key `" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/viva_wallet.rst:93 +msgid ":ref:`Client ID and Client secret `" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/viva_wallet.rst:94 +msgid ":ref:`Terminal ID `" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/viva_wallet.rst:96 +msgid "Save the form and copy the generated webhook URL from the :guilabel:`Viva Wallet Webhook Endpoint` field. This URL is necessary :ref:`when configuring the webhook `." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/viva_wallet.rst:106 +msgid "Configure the webhook" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/viva_wallet.rst:108 +msgid "Webhooks allow you to receive real-time notifications whenever a transaction occurs within your Viva Wallet account. Set them up for `payment transactions following the Viva documentation `_." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/viva_wallet.rst:113 +msgid "`Setting up webhooks `_" +msgstr "" + +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/viva_wallet.rst:118 +msgid "You can select the payment method in your POS settings once the payment method is created. To do so, go to the :ref:`POS' settings ` and add the payment method under the :guilabel:`Payment methods` field of the :guilabel:`Payment` section." +msgstr "" + +#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/viva_wallet.rst:134 +msgid "To cancel the payment request, click :guilabel:`cancel`." +msgstr "" + #: ../../content/applications/sales/point_of_sale/payment_methods/terminals/worldline.rst:3 msgid "Worldline" msgstr "" @@ -7411,7 +7958,7 @@ msgid ":doc:`../../../inventory_and_mrp/inventory/shipping_receiving/setup_confi msgstr "" #: ../../content/applications/sales/point_of_sale/shop/ship_later.rst:29 -msgid ":doc:`../../../inventory_and_mrp/inventory/warehouses_storage/inventory_management/warehouses_locations`" +msgid ":doc:`../../../inventory_and_mrp/inventory/warehouses_storage/inventory_management/warehouses`" msgstr "" #: ../../content/applications/sales/point_of_sale/shop/ship_later.rst:34 @@ -7940,110 +8487,125 @@ msgid "Send by Amazon, based on delivery status synchronized from Odoo." msgstr "" #: ../../content/applications/sales/sales/amazon_connector/features.rst:66 +#: ../../content/applications/sales/sales/amazon_connector/manage.rst:20 +msgid "The stock synchronization does **not** currently support selling the same product as :abbr:`FBM (Fulfilled By Merchant)` *and* :abbr:`FBA (Fulfilled By Amazon)`." +msgstr "" + +#: ../../content/applications/sales/sales/amazon_connector/features.rst:69 +#: ../../content/applications/sales/sales/amazon_connector/manage.rst:23 +msgid "At times, when stock is sent for all products, it triggers a stock problem with Amazon, where Amazon incorrectly thinks the :abbr:`FBM (Fulfilled By Merchant)` product has some quantity in :abbr:`FBM (Fulfilled By Merchant)`." +msgstr "" + +#: ../../content/applications/sales/sales/amazon_connector/features.rst:73 +#: ../../content/applications/sales/sales/amazon_connector/manage.rst:27 +msgid "As a result, Amazon then sells it as :abbr:`FBM (Fulfilled By Merchant)`, instead of taking from their own warehouse. Odoo developers are currently working on resolving this issue to avoid future discrepancies." +msgstr "" + +#: ../../content/applications/sales/sales/amazon_connector/features.rst:78 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 +#: ../../content/applications/sales/sales/amazon_connector/features.rst:83 msgid "As of February 19, 2024, in North American marketplaces, :abbr:`FBA (Fulfilled by Amazon)` orders created with the *Amazon Connector*, do not get the customer's name passed onto the sales/delivery order in Odoo. This is due to the fact that Amazon now calculates, and remits, sales tax on behalf of sellers. In other words, personally identifiable customer information is not transmitted to the seller any longer, after a :abbr:`FBA (Fulfilled by Amazon)` order." msgstr "" -#: ../../content/applications/sales/sales/amazon_connector/features.rst:80 +#: ../../content/applications/sales/sales/amazon_connector/features.rst:92 msgid "Supported marketplaces" msgstr "" -#: ../../content/applications/sales/sales/amazon_connector/features.rst:82 +#: ../../content/applications/sales/sales/amazon_connector/features.rst:94 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:86 +#: ../../content/applications/sales/sales/amazon_connector/features.rst:98 msgid "**North America region**" msgstr "" -#: ../../content/applications/sales/sales/amazon_connector/features.rst:88 +#: ../../content/applications/sales/sales/amazon_connector/features.rst:100 msgid "Canada" msgstr "" -#: ../../content/applications/sales/sales/amazon_connector/features.rst:88 +#: ../../content/applications/sales/sales/amazon_connector/features.rst:100 msgid "Amazon.ca" msgstr "" -#: ../../content/applications/sales/sales/amazon_connector/features.rst:90 +#: ../../content/applications/sales/sales/amazon_connector/features.rst:102 msgid "Mexico" msgstr "" -#: ../../content/applications/sales/sales/amazon_connector/features.rst:90 +#: ../../content/applications/sales/sales/amazon_connector/features.rst:102 msgid "Amazon.com.mx" msgstr "" -#: ../../content/applications/sales/sales/amazon_connector/features.rst:92 +#: ../../content/applications/sales/sales/amazon_connector/features.rst:104 msgid "US" msgstr "" -#: ../../content/applications/sales/sales/amazon_connector/features.rst:92 +#: ../../content/applications/sales/sales/amazon_connector/features.rst:104 msgid "Amazon.com" msgstr "" -#: ../../content/applications/sales/sales/amazon_connector/features.rst:96 +#: ../../content/applications/sales/sales/amazon_connector/features.rst:108 msgid "**Europe region**" msgstr "" -#: ../../content/applications/sales/sales/amazon_connector/features.rst:98 +#: ../../content/applications/sales/sales/amazon_connector/features.rst:110 msgid "Germany" msgstr "" -#: ../../content/applications/sales/sales/amazon_connector/features.rst:98 +#: ../../content/applications/sales/sales/amazon_connector/features.rst:110 msgid "Amazon.de" msgstr "" -#: ../../content/applications/sales/sales/amazon_connector/features.rst:100 +#: ../../content/applications/sales/sales/amazon_connector/features.rst:112 msgid "Spain" msgstr "" -#: ../../content/applications/sales/sales/amazon_connector/features.rst:100 +#: ../../content/applications/sales/sales/amazon_connector/features.rst:112 msgid "Amazon.es" msgstr "" -#: ../../content/applications/sales/sales/amazon_connector/features.rst:102 +#: ../../content/applications/sales/sales/amazon_connector/features.rst:114 msgid "France" msgstr "" -#: ../../content/applications/sales/sales/amazon_connector/features.rst:102 +#: ../../content/applications/sales/sales/amazon_connector/features.rst:114 msgid "Amazon.fr" msgstr "" -#: ../../content/applications/sales/sales/amazon_connector/features.rst:104 +#: ../../content/applications/sales/sales/amazon_connector/features.rst:116 msgid "UK" msgstr "" -#: ../../content/applications/sales/sales/amazon_connector/features.rst:104 +#: ../../content/applications/sales/sales/amazon_connector/features.rst:116 msgid "Amazon.co.uk" msgstr "" -#: ../../content/applications/sales/sales/amazon_connector/features.rst:106 +#: ../../content/applications/sales/sales/amazon_connector/features.rst:118 msgid "Italy" msgstr "" -#: ../../content/applications/sales/sales/amazon_connector/features.rst:106 +#: ../../content/applications/sales/sales/amazon_connector/features.rst:118 msgid "Amazon.it" msgstr "" -#: ../../content/applications/sales/sales/amazon_connector/features.rst:108 +#: ../../content/applications/sales/sales/amazon_connector/features.rst:120 msgid "Netherlands" msgstr "" -#: ../../content/applications/sales/sales/amazon_connector/features.rst:108 +#: ../../content/applications/sales/sales/amazon_connector/features.rst:120 msgid "Amazon.nl" msgstr "" -#: ../../content/applications/sales/sales/amazon_connector/features.rst:112 -#: ../../content/applications/sales/sales/amazon_connector/manage.rst:196 +#: ../../content/applications/sales/sales/amazon_connector/features.rst:124 +#: ../../content/applications/sales/sales/amazon_connector/manage.rst:208 #: ../../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:113 +#: ../../content/applications/sales/sales/amazon_connector/features.rst:125 #: ../../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 @@ -8075,203 +8637,203 @@ msgstr "" 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:20 +#: ../../content/applications/sales/sales/amazon_connector/manage.rst:32 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:24 +#: ../../content/applications/sales/sales/amazon_connector/manage.rst:36 msgid "Force synchronization" msgstr "" -#: ../../content/applications/sales/sales/amazon_connector/manage.rst:26 +#: ../../content/applications/sales/sales/amazon_connector/manage.rst:38 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 +#: ../../content/applications/sales/sales/amazon_connector/manage.rst:42 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 +#: ../../content/applications/sales/sales/amazon_connector/manage.rst:46 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 +#: ../../content/applications/sales/sales/amazon_connector/manage.rst:51 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 +#: ../../content/applications/sales/sales/amazon_connector/manage.rst:56 msgid "Manage deliveries in FBM" msgstr "" -#: ../../content/applications/sales/sales/amazon_connector/manage.rst:46 +#: ../../content/applications/sales/sales/amazon_connector/manage.rst:58 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 +#: ../../content/applications/sales/sales/amazon_connector/manage.rst:62 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 +#: ../../content/applications/sales/sales/amazon_connector/manage.rst:66 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 +#: ../../content/applications/sales/sales/amazon_connector/manage.rst:69 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 +#: ../../content/applications/sales/sales/amazon_connector/manage.rst:73 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 +#: ../../content/applications/sales/sales/amazon_connector/manage.rst:82 msgid ":doc:`../../../inventory_and_mrp/inventory/shipping_receiving/setup_configuration/third_party_shipper`" msgstr "" -#: ../../content/applications/sales/sales/amazon_connector/manage.rst:75 +#: ../../content/applications/sales/sales/amazon_connector/manage.rst:87 msgid "Manage errors when synchronizing deliveries" msgstr "" -#: ../../content/applications/sales/sales/amazon_connector/manage.rst:77 +#: ../../content/applications/sales/sales/amazon_connector/manage.rst:89 msgid "Sometimes, Amazon can fail to correctly process all the information sent by Odoo. In this case, Odoo sends an email listing all the shipments that failed and the errors Amazon sent with them. In addition, these shipments are flagged with a :guilabel:`Synchronization with Amazon failed` tag." msgstr "" -#: ../../content/applications/sales/sales/amazon_connector/manage.rst:81 +#: ../../content/applications/sales/sales/amazon_connector/manage.rst:93 msgid "Usually, the error can be corrected directly in the Amazon backend or in Odoo. If the problem is corrected in Odoo, synchronize the shipment again using the :guilabel:`Retry Amazon Sync` button." msgstr "" -#: ../../content/applications/sales/sales/amazon_connector/manage.rst:85 +#: ../../content/applications/sales/sales/amazon_connector/manage.rst:97 msgid "It might happen that Odoo receives a notification from Amazon saying that some delivery information was not processed, but without specifying which shipments were affected. In that case, all the shipments in an unknown state will be treated as if they failed to synchronize. Once Odoo receives a notification from Amazon saying that a shipment was processed, its tag will change to :guilabel:`Synchronized with Amazon`. To speed up this process, on your Amazon account, click on :guilabel:`Sync Orders` to manually synchronize these orders, or click on :guilabel:`Recover Order` and enter the relevant Amazon Order Reference." msgstr "" -#: ../../content/applications/sales/sales/amazon_connector/manage.rst:94 +#: ../../content/applications/sales/sales/amazon_connector/manage.rst:106 msgid "Follow deliveries in FBA" msgstr "" -#: ../../content/applications/sales/sales/amazon_connector/manage.rst:96 +#: ../../content/applications/sales/sales/amazon_connector/manage.rst:108 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:99 +#: ../../content/applications/sales/sales/amazon_connector/manage.rst:111 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:102 +#: ../../content/applications/sales/sales/amazon_connector/manage.rst:114 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:107 +#: ../../content/applications/sales/sales/amazon_connector/manage.rst:119 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:110 +#: ../../content/applications/sales/sales/amazon_connector/manage.rst:122 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:114 +#: ../../content/applications/sales/sales/amazon_connector/manage.rst:126 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:117 +#: ../../content/applications/sales/sales/amazon_connector/manage.rst:129 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:122 +#: ../../content/applications/sales/sales/amazon_connector/manage.rst:134 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:125 +#: ../../content/applications/sales/sales/amazon_connector/manage.rst:137 msgid "Lastly, assign another stock location to the second registration of the account." msgstr "" -#: ../../content/applications/sales/sales/amazon_connector/manage.rst:128 +#: ../../content/applications/sales/sales/amazon_connector/manage.rst:140 msgid "Invoice and register payments" msgstr "" -#: ../../content/applications/sales/sales/amazon_connector/manage.rst:131 +#: ../../content/applications/sales/sales/amazon_connector/manage.rst:143 msgid "Issue invoices" msgstr "" -#: ../../content/applications/sales/sales/amazon_connector/manage.rst:133 +#: ../../content/applications/sales/sales/amazon_connector/manage.rst:145 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:137 +#: ../../content/applications/sales/sales/amazon_connector/manage.rst:149 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:141 +#: ../../content/applications/sales/sales/amazon_connector/manage.rst:153 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:146 +#: ../../content/applications/sales/sales/amazon_connector/manage.rst:158 msgid "TaxCloud integration will be decommissioned in Odoo 17+." msgstr "" -#: ../../content/applications/sales/sales/amazon_connector/manage.rst:149 +#: ../../content/applications/sales/sales/amazon_connector/manage.rst:161 msgid "Register payments" msgstr "" -#: ../../content/applications/sales/sales/amazon_connector/manage.rst:151 +#: ../../content/applications/sales/sales/amazon_connector/manage.rst:163 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:154 +#: ../../content/applications/sales/sales/amazon_connector/manage.rst:166 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:157 +#: ../../content/applications/sales/sales/amazon_connector/manage.rst:169 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:160 +#: ../../content/applications/sales/sales/amazon_connector/manage.rst:172 msgid "Then, select all the generated payments, and click :menuselection:`Actions --> Create batch payment --> Validate`." msgstr "" -#: ../../content/applications/sales/sales/amazon_connector/manage.rst:164 +#: ../../content/applications/sales/sales/amazon_connector/manage.rst:176 msgid "This same action can be performed with vendor bills from Amazon dedicated to commissions." msgstr "" -#: ../../content/applications/sales/sales/amazon_connector/manage.rst:166 +#: ../../content/applications/sales/sales/amazon_connector/manage.rst:178 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:170 +#: ../../content/applications/sales/sales/amazon_connector/manage.rst:182 msgid "Follow Amazon sales in sales reporting" msgstr "" -#: ../../content/applications/sales/sales/amazon_connector/manage.rst:172 +#: ../../content/applications/sales/sales/amazon_connector/manage.rst:184 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:175 +#: ../../content/applications/sales/sales/amazon_connector/manage.rst:187 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:178 +#: ../../content/applications/sales/sales/amazon_connector/manage.rst:190 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:182 +#: ../../content/applications/sales/sales/amazon_connector/manage.rst:194 msgid "It is also possible to perform reporting on a per-marketplace basis." msgstr "" -#: ../../content/applications/sales/sales/amazon_connector/manage.rst:184 +#: ../../content/applications/sales/sales/amazon_connector/manage.rst:196 msgid "First, remove the desired marketplace from the list of synchronized marketplaces." msgstr "" -#: ../../content/applications/sales/sales/amazon_connector/manage.rst:186 +#: ../../content/applications/sales/sales/amazon_connector/manage.rst:198 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:189 +#: ../../content/applications/sales/sales/amazon_connector/manage.rst:201 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:192 +#: ../../content/applications/sales/sales/amazon_connector/manage.rst:204 msgid "Lastly, assign another sales team to one of the two registrations of the account." msgstr "" -#: ../../content/applications/sales/sales/amazon_connector/manage.rst:195 +#: ../../content/applications/sales/sales/amazon_connector/manage.rst:207 #: ../../content/applications/sales/sales/amazon_connector/setup.rst:154 msgid ":doc:`features`" msgstr "" @@ -8595,12 +9157,12 @@ msgid ":doc:`/applications/sales/sales/ebay_connector/manage`" msgstr "" #: ../../content/applications/sales/sales/ebay_connector/linking_listings.rst:122 -#: ../../content/applications/sales/sales/ebay_connector/manage.rst:153 +#: ../../content/applications/sales/sales/ebay_connector/manage.rst:160 msgid ":doc:`/applications/sales/sales/ebay_connector/troubleshooting`" msgstr "" #: ../../content/applications/sales/sales/ebay_connector/linking_listings.rst:123 -#: ../../content/applications/sales/sales/ebay_connector/manage.rst:155 +#: ../../content/applications/sales/sales/ebay_connector/manage.rst:162 #: ../../content/applications/sales/sales/ebay_connector/troubleshooting.rst:129 msgid ":doc:`/applications/sales/sales/ebay_connector/setup`" msgstr "" @@ -8656,30 +9218,34 @@ 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)." +msgid "When the :guilabel:`Use Stock Quantity` field is checked, the quantity set on eBay is 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`." +msgid "The policies need to be set in order to be able to list on eBay. A value must be selected for the following fields :guilabel:`Payment Policy`, :guilabel:`Return Policy`, and :guilabel:`Shipping Policy`. The options are imported from the eBay database. If no option appears, they can be imported by navigating to :menuselection:`Sales app --> Configuration --> Settings --> eBay`, and clicking on the :guilabel:`Policies` button in the :guilabel:`Synchronization` field. This button **only** appears once the production and sandbox credentials have been set." 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." +msgid "The :guilabel:`Description Template` allows the administrator to use templates in listings. The default template only uses 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:62 +#: ../../content/applications/sales/sales/ebay_connector/manage.rst:65 +msgid "To use images in the listing, an image needs to be added as one of the *Attachments* on the product template." +msgstr "" + +#: ../../content/applications/sales/sales/ebay_connector/manage.rst:69 msgid "For more information on template configuration in Odoo visit: :doc:`../../../general/companies/email_template`." msgstr "" -#: ../../content/applications/sales/sales/ebay_connector/manage.rst:66 +#: ../../content/applications/sales/sales/ebay_connector/manage.rst:73 msgid "Listing with variations" msgstr "" -#: ../../content/applications/sales/sales/ebay_connector/manage.rst:68 +#: ../../content/applications/sales/sales/ebay_connector/manage.rst:75 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 +#: ../../content/applications/sales/sales/ebay_connector/manage.rst:80 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 "" @@ -8687,75 +9253,75 @@ msgstr "" 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 +#: ../../content/applications/sales/sales/ebay_connector/manage.rst:90 msgid "Product identifiers" msgstr "" -#: ../../content/applications/sales/sales/ebay_connector/manage.rst:85 +#: ../../content/applications/sales/sales/ebay_connector/manage.rst:92 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 +#: ../../content/applications/sales/sales/ebay_connector/manage.rst:95 msgid "EAN and UPC identifiers" msgstr "" -#: ../../content/applications/sales/sales/ebay_connector/manage.rst:90 +#: ../../content/applications/sales/sales/ebay_connector/manage.rst:97 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 +#: ../../content/applications/sales/sales/ebay_connector/manage.rst:101 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 +#: ../../content/applications/sales/sales/ebay_connector/manage.rst:106 msgid "Listing with item specifics" msgstr "" -#: ../../content/applications/sales/sales/ebay_connector/manage.rst:101 +#: ../../content/applications/sales/sales/ebay_connector/manage.rst:108 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 +#: ../../content/applications/sales/sales/ebay_connector/manage.rst:115 msgid "Process invoices and payments" msgstr "" -#: ../../content/applications/sales/sales/ebay_connector/manage.rst:111 +#: ../../content/applications/sales/sales/ebay_connector/manage.rst:118 msgid "Posting payment" msgstr "" -#: ../../content/applications/sales/sales/ebay_connector/manage.rst:113 +#: ../../content/applications/sales/sales/ebay_connector/manage.rst:120 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 +#: ../../content/applications/sales/sales/ebay_connector/manage.rst:125 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 +#: ../../content/applications/sales/sales/ebay_connector/manage.rst:131 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 +#: ../../content/applications/sales/sales/ebay_connector/manage.rst:139 msgid "Reconciling payments" msgstr "" -#: ../../content/applications/sales/sales/ebay_connector/manage.rst:134 +#: ../../content/applications/sales/sales/ebay_connector/manage.rst:141 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 +#: ../../content/applications/sales/sales/ebay_connector/manage.rst:145 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 +#: ../../content/applications/sales/sales/ebay_connector/manage.rst:150 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 +#: ../../content/applications/sales/sales/ebay_connector/manage.rst:155 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/manage.rst:161 #: ../../content/applications/sales/sales/ebay_connector/troubleshooting.rst:128 msgid ":doc:`/applications/sales/sales/ebay_connector/linking_listings`" msgstr "" @@ -9528,11 +10094,11 @@ msgstr "" msgid "If :guilabel:`Based on Delivered Quantity (Manual)` is chosen as the :guilabel:`Invoicing Policy`, an invoice will **not** be able to be created." msgstr "" -#: ../../content/applications/sales/sales/invoicing/down_payment.rst:86 +#: ../../content/applications/sales/sales/invoicing/down_payment.rst:88 msgid "Example: request 50% down payment" msgstr "" -#: ../../content/applications/sales/sales/invoicing/down_payment.rst:89 +#: ../../content/applications/sales/sales/invoicing/down_payment.rst:91 msgid "The following example involves a 50% amount down payment on a product (:guilabel:`Cabinet with Doors`) with :guilabel:`Ordered quantities` as the :guilabel:`Invoicing Policy`." msgstr "" @@ -9540,8 +10106,8 @@ msgstr "" msgid "Cabinet with doors product form showcasing various details and fields." msgstr "" -#: ../../content/applications/sales/sales/invoicing/down_payment.rst:97 -#: ../../content/applications/sales/sales/invoicing/down_payment.rst:260 +#: ../../content/applications/sales/sales/invoicing/down_payment.rst:99 +#: ../../content/applications/sales/sales/invoicing/down_payment.rst:335 #: ../../content/applications/sales/sales/invoicing/expense.rst:255 #: ../../content/applications/sales/sales/invoicing/milestone.rst:238 #: ../../content/applications/sales/sales/invoicing/proforma.rst:71 @@ -9549,15 +10115,15 @@ msgstr "" msgid ":doc:`invoicing_policy`" msgstr "" -#: ../../content/applications/sales/sales/invoicing/down_payment.rst:99 +#: ../../content/applications/sales/sales/invoicing/down_payment.rst:101 msgid "First, navigate to :menuselection:`Sales app --> New`, and add a :guilabel:`Customer` to the quotation." msgstr "" -#: ../../content/applications/sales/sales/invoicing/down_payment.rst:102 +#: ../../content/applications/sales/sales/invoicing/down_payment.rst:104 msgid "Then, click :guilabel:`Add a product` in the :guilabel:`Order Lines` tab, and select the :guilabel:`Cabinet with Doors` product." msgstr "" -#: ../../content/applications/sales/sales/invoicing/down_payment.rst:105 +#: ../../content/applications/sales/sales/invoicing/down_payment.rst:107 msgid "When the order is confirmed (via the :guilabel:`Confirm` button), the quotation turns into a sales order. Once this occurs, create and view the invoice by clicking :guilabel:`Create Invoice`." msgstr "" @@ -9565,27 +10131,29 @@ msgstr "" msgid "Cabinet with doors sales order that's been confirmed in the Odoo Sales application." msgstr "" -#: ../../content/applications/sales/sales/invoicing/down_payment.rst:112 +#: ../../content/applications/sales/sales/invoicing/down_payment.rst:114 msgid "Next, on the :guilabel:`Create invoices` pop-up window that appears, select :guilabel:`Down payment (percentage)`, and type `50` in the :guilabel:`Down Payment Amount` field." msgstr "" -#: ../../content/applications/sales/sales/invoicing/down_payment.rst:116 +#: ../../content/applications/sales/sales/invoicing/down_payment.rst:118 +#: ../../content/applications/sales/sales/invoicing/down_payment.rst:264 msgid "The :guilabel:`Income Account` and :guilabel:`Customer Taxes` fields are *not* required fields, and they will *not* appear if they've already been preconfigured in previous down payment requests." msgstr "" -#: ../../content/applications/sales/sales/invoicing/down_payment.rst:120 +#: ../../content/applications/sales/sales/invoicing/down_payment.rst:122 +#: ../../content/applications/sales/sales/invoicing/down_payment.rst:268 msgid "For more information, check out the documentation on :ref:`customer taxes modification on down payments ` and :ref:`income account modification on down payments `." msgstr "" -#: ../../content/applications/sales/sales/invoicing/down_payment.rst:124 +#: ../../content/applications/sales/sales/invoicing/down_payment.rst:126 msgid "Lastly, click :guilabel:`Create Draft Invoice` to create and view the invoice draft." msgstr "" -#: ../../content/applications/sales/sales/invoicing/down_payment.rst:126 +#: ../../content/applications/sales/sales/invoicing/down_payment.rst:128 msgid "Clicking :guilabel:`Create Draft Invoice` reveals the draft invoice, which includes the down payment as a :guilabel:`Product` in the :guilabel:`Invoice Lines` tab." msgstr "" -#: ../../content/applications/sales/sales/invoicing/down_payment.rst:129 +#: ../../content/applications/sales/sales/invoicing/down_payment.rst:131 msgid "From there, the invoice can be confirmed and posted by clicking :guilabel:`Confirm`. Confirming the invoice changes the status from :guilabel:`Draft` to :guilabel:`Posted`. It also reveals a new series of buttons at the top of the page." msgstr "" @@ -9593,7 +10161,7 @@ msgstr "" msgid "A sample draft invoice with down payment mentioned in Odoo Sales." msgstr "" -#: ../../content/applications/sales/sales/invoicing/down_payment.rst:137 +#: ../../content/applications/sales/sales/invoicing/down_payment.rst:139 msgid "From those buttons, the payment can be registered by clicking :guilabel:`Register Payment`." msgstr "" @@ -9601,27 +10169,29 @@ msgstr "" msgid "Showcase of the Register Payment button on a confirmed customer invoice." msgstr "" -#: ../../content/applications/sales/sales/invoicing/down_payment.rst:143 -msgid "Doing so reveals a :guilabel:`Register Payment` pop-up form, which is auto-populated with the necessary information. Confirm the information provided is correct and make any necessary adjustments. When ready, click the :guilabel:`Create Payment` button." +#: ../../content/applications/sales/sales/invoicing/down_payment.rst:145 +msgid "Doing so reveals a :guilabel:`Register Payment` pop-up form, which is auto-populated with the necessary information. Confirm the information provided is correct, and make any necessary adjustments. When ready, click the :guilabel:`Create Payment` button." msgstr "" #: ../../content/applications/sales/sales/invoicing/down_payment.rst:-1 msgid "Showcase of the Register Payment pop-up window with create payment button." msgstr "" -#: ../../content/applications/sales/sales/invoicing/down_payment.rst:151 +#: ../../content/applications/sales/sales/invoicing/down_payment.rst:153 +#: ../../content/applications/sales/sales/invoicing/down_payment.rst:291 msgid "After clicking :guilabel:`Create Payment`, Odoo reveals the customer invoice, now with a green :guilabel:`In Payment` banner in the upper-right corner." msgstr "" +#: ../../content/applications/sales/sales/invoicing/down_payment.rst:-1 #: ../../content/applications/sales/sales/invoicing/down_payment.rst:-1 msgid "Customer Invoice with a green In Payment banner located in the upper-right corner." msgstr "" -#: ../../content/applications/sales/sales/invoicing/down_payment.rst:158 +#: ../../content/applications/sales/sales/invoicing/down_payment.rst:160 msgid "Now, when the customer wants to pay the remaining amount of the order, another invoice must be created. To do that, return to the sales order, via the breadcrumb links." msgstr "" -#: ../../content/applications/sales/sales/invoicing/down_payment.rst:161 +#: ../../content/applications/sales/sales/invoicing/down_payment.rst:163 msgid "Back on the sales order, a new :guilabel:`Down Payments` section is present in the :guilabel:`Order Lines` tab, along with the down payment that was just invoiced and posted." msgstr "" @@ -9629,11 +10199,11 @@ msgstr "" msgid "The down payments section in the order lines tab of a sales order." msgstr "" -#: ../../content/applications/sales/sales/invoicing/down_payment.rst:168 +#: ../../content/applications/sales/sales/invoicing/down_payment.rst:170 msgid "Next, click the :guilabel:`Create Invoice` button." msgstr "" -#: ../../content/applications/sales/sales/invoicing/down_payment.rst:170 +#: ../../content/applications/sales/sales/invoicing/down_payment.rst:172 msgid "On the :guilabel:`Create invoices` pop-up window that appears, there are two new fields: :guilabel:`Already invoiced` and :guilabel:`Amount to invoice`." msgstr "" @@ -9641,23 +10211,23 @@ msgstr "" msgid "The deduct down payment option on the create invoices pop up in Odoo Sales." msgstr "" -#: ../../content/applications/sales/sales/invoicing/down_payment.rst:177 +#: ../../content/applications/sales/sales/invoicing/down_payment.rst:179 msgid "If the remaining amount is ready to be paid, select the :guilabel:`Regular Invoice` option. Odoo will create an invoice for the exact amount needed to complete the total payment, as indicated in the :guilabel:`Amount to invoice` field." msgstr "" -#: ../../content/applications/sales/sales/invoicing/down_payment.rst:181 +#: ../../content/applications/sales/sales/invoicing/down_payment.rst:183 msgid "Once ready, click :guilabel:`Create Draft Invoice`." msgstr "" -#: ../../content/applications/sales/sales/invoicing/down_payment.rst:183 +#: ../../content/applications/sales/sales/invoicing/down_payment.rst:185 msgid "Doing so reveals another :guilabel:`Customer Invoice Draft` page, listing *all* the invoices for that specific sales order in the :guilabel:`Invoice Lines` tab. Each invoice line item displays all the necessary information related to each invoice." msgstr "" -#: ../../content/applications/sales/sales/invoicing/down_payment.rst:187 +#: ../../content/applications/sales/sales/invoicing/down_payment.rst:189 msgid "To complete the flow, click :guilabel:`Confirm`, which changes the status of the invoice from :guilabel:`Draft` to :guilabel:`Posted`. Then, click :guilabel:`Register Payment`." msgstr "" -#: ../../content/applications/sales/sales/invoicing/down_payment.rst:190 +#: ../../content/applications/sales/sales/invoicing/down_payment.rst:192 msgid "Once again, the :guilabel:`Register Payment` appears, with all fields auto-populated with the necessary information, including the remaining amount left to be paid on the order." msgstr "" @@ -9665,7 +10235,7 @@ msgstr "" msgid "The second register payment pop-up form in Odoo sales." msgstr "" -#: ../../content/applications/sales/sales/invoicing/down_payment.rst:197 +#: ../../content/applications/sales/sales/invoicing/down_payment.rst:199 msgid "After confirming that information, click :guilabel:`Create Payment`. Doing so reveals the final :guilabel:`Customer Invoice` with a green :guilabel:`In Payment` banner in the upper-right corner. Also, both down payments are present in the :guilabel:`Invoice Lines` tab." msgstr "" @@ -9673,39 +10243,107 @@ msgstr "" msgid "The second down payment invoice with in payment banner in Odoo Sales." msgstr "" -#: ../../content/applications/sales/sales/invoicing/down_payment.rst:205 +#: ../../content/applications/sales/sales/invoicing/down_payment.rst:207 msgid "At this point, the flow is now complete." msgstr "" -#: ../../content/applications/sales/sales/invoicing/down_payment.rst:208 +#: ../../content/applications/sales/sales/invoicing/down_payment.rst:210 msgid "This flow is also possible with the :guilabel:`Fixed amount` down payment option." msgstr "" -#: ../../content/applications/sales/sales/invoicing/down_payment.rst:211 -msgid "If a down payment is used with a product that has a :guilabel:`Delivered quantities` invoicing policy, the down payments will **not** be able to be deducted when it comes time to invoice the customer." +#: ../../content/applications/sales/sales/invoicing/down_payment.rst:213 +msgid "If a down payment is used with a product that has a :guilabel:`Delivered quantities` invoicing policy, and the cost of the product *exceeds* the 50% down payment (as in most cases), a regular invoice is created." msgstr "" -#: ../../content/applications/sales/sales/invoicing/down_payment.rst:215 -msgid "This is because, due to the invoicing policy, the product(s) would have to be delivered *before* creating the final invoice." +#: ../../content/applications/sales/sales/invoicing/down_payment.rst:217 +msgid "However, for products that cost *less* than the 50% down payment, the down payments will **not** be able to be deducted when it comes time to invoice the customer." msgstr "" -#: ../../content/applications/sales/sales/invoicing/down_payment.rst:218 +#: ../../content/applications/sales/sales/invoicing/down_payment.rst:220 +msgid "This is because the product(s) would have to be delivered *before* creating the final invoice due to Odoo not allowing negative totals for invoices." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/down_payment.rst:223 msgid "If nothing has been delivered, a :guilabel:`Credit Note` is created, which cancels the draft invoice that was created after the down payment." msgstr "" -#: ../../content/applications/sales/sales/invoicing/down_payment.rst:221 +#: ../../content/applications/sales/sales/invoicing/down_payment.rst:226 msgid "To utilize the :guilabel:`Credit Note` option, the *Inventory* application must be installed, in order to confirm the delivery. Otherwise, the delivered quantity can be entered manually directly on the sales order." msgstr "" -#: ../../content/applications/sales/sales/invoicing/down_payment.rst:228 +#: ../../content/applications/sales/sales/invoicing/down_payment.rst:233 +msgid "Example: request 100% down payment" +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/down_payment.rst:235 +msgid "The process of requesting a 100% down payment is similar to the process of setting up a :ref:`50% down payment `, but with fewer steps." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/down_payment.rst:239 +msgid "A 100% down payment is **not** the same as a full payment of the sales order." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/down_payment.rst:241 +msgid "A sales order paid through the regular invoice process will not allow any additional invoices to be generated, and **will not** display the *Create Invoice* button on the Sales Order." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/down_payment.rst:244 +msgid "Following this example **will** cause the *Create Invoice* button to be displayed on the Sales Order. This is because Odoo expects another invoice to be created after the down payment to complete payment of the sales order." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/down_payment.rst:248 +msgid "The *Solar Panel Installation* product is being used in this example." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/down_payment.rst:250 +msgid "To configure a 100% down payment, begin by navigating to :menuselection:`Sales app --> New`, and add a :guilabel:`Customer` to the quote." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/down_payment.rst:253 +msgid "Next, click :guilabel:`Add a product` in the :guilabel:`Order Lines` tab, and select the `Solar Panel Installation` product." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/down_payment.rst:256 +msgid "Upon clicking the :guilabel:`Confirm` button, the quotation turns into a sales order. At that point, an invoice can now be created by clicking :guilabel:`Create Invoice` in the top-left corner." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/down_payment.rst:259 +msgid "On the :guilabel:`Create invoices` pop-up window that appears, select :guilabel:`Down payment (percentage)`, and type `100` in the :guilabel:`Down Payment Amount` field. Then, if desired, select an :guilabel:`Income Account` and :guilabel:`Customer Taxes` in their respective fields." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/down_payment.rst:-1 +msgid "The Down payment (percentage) option selected with 100% set as the Down Payment." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/down_payment.rst:276 +msgid "Next, click :guilabel:`Create Draft Invoice` to create an invoice draft. This will also bring the draft invoice into view, which includes the :guilabel:`Down payment` as a :guilabel:`Product` in the :guilabel:`Invoice Lines` tab." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/down_payment.rst:280 +msgid "The invoice can now be confirmed and posted by clicking :guilabel:`Confirm`. Confirming the invoice changes the status from :guilabel:`Draft` to :guilabel:`Posted`. It also reveals a new series of buttons at the top of the page." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/down_payment.rst:284 +msgid "The payment can be registered by clicking the :guilabel:`Register Payment` button." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/down_payment.rst:286 +msgid "Doing so reveals a :guilabel:`Register Payment` pop-up form, which is auto-populated with the necessary information. Confirm the information provided is correct and make any necessary adjustments. When ready, click the :guilabel:`Create Payment` button." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/down_payment.rst:298 +msgid "The process is now complete, and the 100% down payment has been successfully applied." +msgstr "" + +#: ../../content/applications/sales/sales/invoicing/down_payment.rst:303 msgid "Customer taxes modification on down payments" msgstr "" -#: ../../content/applications/sales/sales/invoicing/down_payment.rst:230 +#: ../../content/applications/sales/sales/invoicing/down_payment.rst:305 msgid "To adjust the income account and customer taxes attached to a down payment, navigate to the :guilabel:`Products` page (:menuselection:`Sales app --> Products --> Products`), search for the `Down Payment` product in the search bar, and select it to reveal the product detail page." msgstr "" -#: ../../content/applications/sales/sales/invoicing/down_payment.rst:234 +#: ../../content/applications/sales/sales/invoicing/down_payment.rst:309 msgid "On the :guilabel:`Down Payment` product page, in the :guilabel:`General Information` tab, the customer taxes can be modified in the :guilabel:`Customer Taxes` field." msgstr "" @@ -9714,19 +10352,19 @@ msgstr "" msgid "How to modify the income account link to down payments." msgstr "" -#: ../../content/applications/sales/sales/invoicing/down_payment.rst:244 +#: ../../content/applications/sales/sales/invoicing/down_payment.rst:319 msgid "Income account modification on down payments" msgstr "" -#: ../../content/applications/sales/sales/invoicing/down_payment.rst:246 +#: ../../content/applications/sales/sales/invoicing/down_payment.rst:321 msgid "To change or adjust the income account attached to the :guilabel:`Down Payment` product page, the *Accounting* app **must** be installed." msgstr "" -#: ../../content/applications/sales/sales/invoicing/down_payment.rst:249 +#: ../../content/applications/sales/sales/invoicing/down_payment.rst:324 msgid "With the *Accounting* app installed, the :guilabel:`Accounting` tab becomes available on the product page. That tab will **not** be accessible without the *Accounting* app installed." msgstr "" -#: ../../content/applications/sales/sales/invoicing/down_payment.rst:252 +#: ../../content/applications/sales/sales/invoicing/down_payment.rst:327 msgid "In the :guilabel:`Accounting` tab, the income account can be changed in the :guilabel:`Income Account` field, located in the :guilabel:`Receivables` section." msgstr "" @@ -12143,7 +12781,7 @@ msgid ":doc:`/applications/sales/sales/products_prices/prices/currencies`" msgstr "" #: ../../content/applications/sales/sales/products_prices/prices/pricing.rst:485 -msgid ":doc:`/applications/websites/ecommerce/managing_products/price_management`" +msgid ":doc:`/applications/websites/ecommerce/products/price_management`" msgstr "" #: ../../content/applications/sales/sales/products_prices/products.rst:5 @@ -12690,7 +13328,7 @@ msgid "In this instance, there is a total of twenty different product variants: msgstr "" #: ../../content/applications/sales/sales/products_prices/products/variants.rst:31 -msgid ":doc:`/applications/websites/ecommerce/managing_products/variants`" +msgid ":doc:`/applications/websites/ecommerce/products/variants`" msgstr "" #: ../../content/applications/sales/sales/products_prices/products/variants.rst:36 @@ -14647,7 +15285,7 @@ msgstr "" #: ../../content/applications/sales/subscriptions/closing.rst:105 #: ../../content/applications/sales/subscriptions/renewals.rst:85 #: ../../content/applications/sales/subscriptions/reports.rst:406 -#: ../../content/applications/sales/subscriptions/scheduled_actions.rst:182 +#: ../../content/applications/sales/subscriptions/scheduled_actions.rst:186 #: ../../content/applications/sales/subscriptions/upselling.rst:107 msgid ":doc:`../subscriptions`" msgstr "" @@ -14656,7 +15294,7 @@ msgstr "" #: ../../content/applications/sales/subscriptions/closing.rst:106 #: ../../content/applications/sales/subscriptions/renewals.rst:86 #: ../../content/applications/sales/subscriptions/reports.rst:407 -#: ../../content/applications/sales/subscriptions/scheduled_actions.rst:183 +#: ../../content/applications/sales/subscriptions/scheduled_actions.rst:187 #: ../../content/applications/sales/subscriptions/upselling.rst:108 msgid ":doc:`plans`" msgstr "" @@ -14665,7 +15303,7 @@ msgstr "" #: ../../content/applications/sales/subscriptions/closing.rst:107 #: ../../content/applications/sales/subscriptions/renewals.rst:87 #: ../../content/applications/sales/subscriptions/reports.rst:408 -#: ../../content/applications/sales/subscriptions/scheduled_actions.rst:184 +#: ../../content/applications/sales/subscriptions/scheduled_actions.rst:188 #: ../../content/applications/sales/subscriptions/upselling.rst:109 msgid ":doc:`products`" msgstr "" @@ -15977,18 +16615,26 @@ msgid "Odoo uses the information in the :guilabel:`Recurring Plan` field to upda msgstr "" #: ../../content/applications/sales/subscriptions/scheduled_actions.rst:110 -msgid "If there is no payment provider set up, Odoo does **not** create an invoice, and the customer is not charged. Instead, the subscription is processed as a free recurring product, and is reflected as such in the *chatter* of the subscription sales order. When this occurs, the following message appears: `Automatic renewal succeeded. Free subscription. Next invoice:[date]. No email sent.`" +msgid "If the product invoicing policy is set to *Based on Delivered Quantities (Manual)*, and the delivered quantity is `0`, Odoo does **not** create an invoice, and the customer is not charged." msgstr "" -#: ../../content/applications/sales/subscriptions/scheduled_actions.rst:115 +#: ../../content/applications/sales/subscriptions/scheduled_actions.rst:113 +msgid "Instead, the subscription is processed as a free recurring product, and is reflected as such in the *chatter* of the subscription sales order." +msgstr "" + +#: ../../content/applications/sales/subscriptions/scheduled_actions.rst:116 +msgid "When this occurs, the following message appears: `Automatic renewal succeeded. Free subscription. Next invoice:[date]. No email sent.`" +msgstr "" + +#: ../../content/applications/sales/subscriptions/scheduled_actions.rst:119 msgid "Once the invoice for the subscription sales order is created, the invoice can be viewed by clicking the :guilabel:`Invoices` smart button that appears at the top of the subscription sales order." msgstr "" -#: ../../content/applications/sales/subscriptions/scheduled_actions.rst:118 +#: ../../content/applications/sales/subscriptions/scheduled_actions.rst:122 msgid "An email is sent to the customer notifying them of the recurring subscription charge, *if* there is a :guilabel:`Payment Token` on the account." msgstr "" -#: ../../content/applications/sales/subscriptions/scheduled_actions.rst:121 +#: ../../content/applications/sales/subscriptions/scheduled_actions.rst:125 msgid "To check if there is a :guilabel:`Payment Token`, open the :guilabel:`Other Info` tab, and look at the :guilabel:`Payment Token` field, under the :guilabel:`Subscription` section." msgstr "" @@ -15996,47 +16642,47 @@ msgstr "" msgid "The Payment Token field under the Other Info tab on a subscription sales order form." msgstr "" -#: ../../content/applications/sales/subscriptions/scheduled_actions.rst:128 -msgid "If there is no :guilabel:`Payment Token` (i.e. payment provider is `Bank Transfer`), the invoice is created and sent to the customer. The payment **must** be registered manually in this case." +#: ../../content/applications/sales/subscriptions/scheduled_actions.rst:132 +msgid "If there is no :guilabel:`Payment Token`, the invoice is created, and sent to the customer. The payment **must** be registered manually in this case." msgstr "" -#: ../../content/applications/sales/subscriptions/scheduled_actions.rst:132 +#: ../../content/applications/sales/subscriptions/scheduled_actions.rst:136 msgid "Closing invoices" msgstr "" -#: ../../content/applications/sales/subscriptions/scheduled_actions.rst:134 +#: ../../content/applications/sales/subscriptions/scheduled_actions.rst:138 msgid "The :guilabel:`Sale Subscription: generate recurring invoices and payments` scheduled action also has the ability to close a subscription, if the following conditions are met:" msgstr "" -#: ../../content/applications/sales/subscriptions/scheduled_actions.rst:137 +#: ../../content/applications/sales/subscriptions/scheduled_actions.rst:141 msgid "If the subscription has no :guilabel:`Payment Token`, create and post the invoice." msgstr "" -#: ../../content/applications/sales/subscriptions/scheduled_actions.rst:138 +#: ../../content/applications/sales/subscriptions/scheduled_actions.rst:142 msgid "If the subscription has a :guilabel:`Payment Token`, try to charge." msgstr "" -#: ../../content/applications/sales/subscriptions/scheduled_actions.rst:140 +#: ../../content/applications/sales/subscriptions/scheduled_actions.rst:144 msgid "If the charge is successful, create and post the invoice." msgstr "" -#: ../../content/applications/sales/subscriptions/scheduled_actions.rst:141 +#: ../../content/applications/sales/subscriptions/scheduled_actions.rst:145 msgid "If the charge fails, send reminders periodically." msgstr "" -#: ../../content/applications/sales/subscriptions/scheduled_actions.rst:143 +#: ../../content/applications/sales/subscriptions/scheduled_actions.rst:147 msgid "Close the subscription if it continues to fail for more than fourteen days." msgstr "" -#: ../../content/applications/sales/subscriptions/scheduled_actions.rst:146 +#: ../../content/applications/sales/subscriptions/scheduled_actions.rst:150 msgid "Subscriptions expiration" msgstr "" -#: ../../content/applications/sales/subscriptions/scheduled_actions.rst:148 +#: ../../content/applications/sales/subscriptions/scheduled_actions.rst:152 msgid "The :guilabel:`Sale Subscription: subscriptions expiration` scheduled action checks for all other conditions that may cause a subscription to close automatically. If certain conditions are met, the scheduled action closes that subscription." msgstr "" -#: ../../content/applications/sales/subscriptions/scheduled_actions.rst:152 +#: ../../content/applications/sales/subscriptions/scheduled_actions.rst:156 msgid "First, the :guilabel:`Sale Subscription: subscriptions expiration` scheduled action checks to see if the end date has passed, which is configured on the subscription sales order." msgstr "" @@ -16044,11 +16690,11 @@ msgstr "" msgid "The expiration date on a subscription sales order in Odoo Subscriptions." msgstr "" -#: ../../content/applications/sales/subscriptions/scheduled_actions.rst:159 +#: ../../content/applications/sales/subscriptions/scheduled_actions.rst:163 msgid "Then, the :guilabel:`Sale Subscription: subscriptions expiration` scheduled action checks if the invoice has not been paid within the payment terms deadline." msgstr "" -#: ../../content/applications/sales/subscriptions/scheduled_actions.rst:162 +#: ../../content/applications/sales/subscriptions/scheduled_actions.rst:166 msgid "To access the invoices attached to a subscription, access the sales order for the subscription product, and click the :guilabel:`Invoices` smart button. Then, look at the :guilabel:`Invoice Date` column." msgstr "" @@ -16056,7 +16702,7 @@ msgstr "" msgid "The Invoice Date column on subscriptions invoice page in Odoo Subscriptions app." msgstr "" -#: ../../content/applications/sales/subscriptions/scheduled_actions.rst:170 +#: ../../content/applications/sales/subscriptions/scheduled_actions.rst:174 msgid "Unpaid subscriptions with an :guilabel:`Invoice Date` that are past the determined number of days in the :guilabel:`Automatic Closing` field of a :guilabel:`Recurring Plan` are automatically closed by the :guilabel:`Sale Subscription: subscriptions expiration` scheduled action." msgstr "" @@ -16064,11 +16710,11 @@ msgstr "" msgid "The Automatic Closing field on a Recurring Plan form in Odoo Subscriptions." msgstr "" -#: ../../content/applications/sales/subscriptions/scheduled_actions.rst:178 +#: ../../content/applications/sales/subscriptions/scheduled_actions.rst:182 msgid "For example, if the next invoice date is July 1st, and the :guilabel:`Automatic Closing` is set to '30 Days', the scheduled action would close the subscription on August 1st." msgstr "" -#: ../../content/applications/sales/subscriptions/scheduled_actions.rst:185 +#: ../../content/applications/sales/subscriptions/scheduled_actions.rst:189 msgid ":doc:`automatic_alerts`" msgstr "" diff --git a/locale/sources/services.pot b/locale/sources/services.pot index 66e438c58..461e5dfda 100644 --- a/locale/sources/services.pot +++ b/locale/sources/services.pot @@ -8,7 +8,7 @@ msgid "" msgstr "" "Project-Id-Version: Odoo 17.0\n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2024-06-24 07:08+0000\n" +"POT-Creation-Date: 2024-07-23 13:30+0000\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME \n" "Language-Team: LANGUAGE \n" @@ -45,15 +45,16 @@ msgid ":doc:`../../inventory_and_mrp/inventory`" msgstr "" #: ../../content/applications/services/field_service/default_warehouse.rst:16 +#: ../../content/applications/services/field_service/worksheets.rst:15 #: ../../content/applications/services/helpdesk/overview/help_center.rst:14 #: ../../content/applications/services/planning.rst:29 -#: ../../content/applications/services/project/project_management.rst:17 +#: ../../content/applications/services/project/project_management.rst:19 #: ../../content/applications/services/project/tasks/recurring_tasks.rst:13 msgid "Configuration" msgstr "" #: ../../content/applications/services/field_service/default_warehouse.rst:18 -msgid "To set up a user default warehouse, the :doc:`storage locations ` feature needs to be activated in the **Inventory** app. It is also necessary to have more than one warehouse in your database." +msgid "To set up a user default warehouse, the :doc:`storage locations <../../inventory_and_mrp/inventory/warehouses_storage/inventory_management/use_locations>` feature needs to be activated in the **Inventory** app. It is also necessary to have more than one warehouse in your database." msgstr "" #: ../../content/applications/services/field_service/default_warehouse.rst:23 @@ -61,7 +62,7 @@ msgid "You can either set it up :ref:`for your profile My Tasks --> Map`. To create your itinerary, Odoo sorts out your field service tasks based on their :guilabel:`Planned Date` to show the way from one location to the next." msgstr "" -#: ../../content/applications/services/field_service/planning_itinerary.rst:30 +#: ../../content/applications/services/field_service/planning_itinerary.rst:28 msgid "To open your itinerary on the Google Maps website or app, click :guilabel:`View in Google Maps`. Google Maps includes your current location as a starting point for your itinerary." msgstr "" -#: ../../content/applications/services/field_service/planning_itinerary.rst:34 +#: ../../content/applications/services/field_service/planning_itinerary.rst:32 msgid "By default, the map shows today’s tasks. Remove the :guilabel:`Today` filter in the search bar to display all tasks. Your tasks are then sorted by date in the left column." msgstr "" -#: ../../content/applications/services/field_service/planning_itinerary.rst:36 +#: ../../content/applications/services/field_service/planning_itinerary.rst:34 msgid "Click your task in the left column or the map pin to display the task's details. From there, you can :guilabel:`Open` the task or click :guilabel:`Navigate to` to get an itinerary from your current location to this specific task's location." msgstr "" -#: ../../content/applications/services/helpdesk.rst:7 +#: ../../content/applications/services/field_service/worksheets.rst:3 +msgid "Worksheets" +msgstr "" + +#: ../../content/applications/services/field_service/worksheets.rst:5 +msgid "**Worksheets** help your field service workers perform and report their on-site tasks. They can feature various information, such as instructions, to-do lists, etc. You can also format your worksheet using checkboxes, bullet points, blank fields to fill in, HTML, and add files, images, links, and more." +msgstr "" + +#: ../../content/applications/services/field_service/worksheets.rst:10 +msgid "It is common for businesses to have their workers perform the same type of field service repeatedly. Making custom **worksheet templates** eliminates the need to recreate the same worksheet each time you plan a similar field service task." +msgstr "" + +#: ../../content/applications/services/field_service/worksheets.rst:17 +msgid "To use worksheets in Field Service, go to :menuselection:`Field Service --> Configuration --> Settings`, enable the :guilabel:`Worksheets` feature, and click :guilabel:`Save`." +msgstr "" + +#: ../../content/applications/services/field_service/worksheets.rst:21 +msgid "Worksheet templates are designed using **Studio**. Enabling the :guilabel:`Worksheets` feature automatically installs the **Studio** app, which may impact your price plan." +msgstr "" + +#: ../../content/applications/services/field_service/worksheets.rst:25 +msgid "Create a worksheet template" +msgstr "" + +#: ../../content/applications/services/field_service/worksheets.rst:27 +msgid "To create your **worksheet templates**, go to :menuselection:`Field Service --> Configuration --> Worksheet Templates`. Click :guilabel:`New` and give your worksheet template a name. Manually save, then click :guilabel:`Design Template` to open **Studio** and customize your worksheet template." +msgstr "" + +#: ../../content/applications/services/field_service/worksheets.rst:31 +msgid "In Studio, drag and drop the desired fields from the left column into your worksheet on the right. To rearrange the fields on the worksheet, drag and drop them in the desired order. Click a field to customize its :ref:`properties `." +msgstr "" + +#: ../../content/applications/services/field_service/worksheets.rst:35 +msgid "When your worksheet template is complete, click :guilabel:`Close` in the top right corner of the page to leave **Studio**." +msgstr "" + +#: ../../content/applications/services/field_service/worksheets.rst:39 +msgid ":doc:`Fields and widgets in Studio <../../studio/fields>`" +msgstr "" + +#: ../../content/applications/services/field_service/worksheets.rst:42 +msgid "Add a worksheet template to a field service task" +msgstr "" + +#: ../../content/applications/services/field_service/worksheets.rst:44 +msgid "Go to your field service task, select a :guilabel:`Worksheet Template`, and click :guilabel:`Save`." +msgstr "" + +#: ../../content/applications/services/field_service/worksheets.rst:46 +msgid "By default, the :guilabel:`Default Worksheet` template is selected. To define another default worksheet template, click the :guilabel:`➔` (:guilabel:`Internal link`) icon that appears when you hover your mouse over the :guilabel:`Project` field on the task form." +msgstr "" + +#: ../../content/applications/services/field_service/worksheets.rst:-1 +msgid "Mouse on project name to setup default worksheet template" +msgstr "" + +#: ../../content/applications/services/field_service/worksheets.rst:54 +msgid "Then, in the :guilabel:`Settings` tab, scroll down to the :guilabel:`Field service` section and select the :guilabel:`Worksheet Template` you want to set up as default." +msgstr "" + +#: ../../content/applications/services/field_service/worksheets.rst:58 +msgid "Use worksheets on site" +msgstr "" + +#: ../../content/applications/services/field_service/worksheets.rst:60 +msgid "To complete the worksheet on site, access the task and click the :guilabel:`Worksheet` smart button." +msgstr "" + +#: ../../content/applications/services/field_service/worksheets.rst:63 +msgid "As soon as you save a worksheet, the label of the :guilabel:`Worksheet` smart button on the task changes to :guilabel:`Worksheet Complete` instead, even if some fields are left blank." +msgstr "" + +#: ../../content/applications/services/field_service/worksheets.rst:66 +msgid "Any field defined as :guilabel:`Required` has to be filled for a worksheet to be saved." +msgstr "" + +#: ../../content/applications/services/helpdesk.rst:6 msgid "Helpdesk" msgstr "" -#: ../../content/applications/services/helpdesk.rst:9 +#: ../../content/applications/services/helpdesk.rst:8 msgid "Odoo *Helpdesk* is a ticketing-based customer support application. Multiple teams can be configured and managed in one dashboard, each with their own pipeline for tickets submitted by customers. Pipelines are organized in customizable stages that enable teams to track, prioritize, and solve customer issues quickly and efficiently." msgstr "" -#: ../../content/applications/services/helpdesk.rst:15 +#: ../../content/applications/services/helpdesk.rst:14 msgid "Create a Helpdesk team" msgstr "" -#: ../../content/applications/services/helpdesk.rst:17 +#: ../../content/applications/services/helpdesk.rst:16 msgid "To view or modify *Helpdesk* teams, go to :menuselection:`Helpdesk app --> Configuration --> Helpdesk Teams`. To create a new team, click the :guilabel:`New` button in the top-left of the dashboard." msgstr "" @@ -248,11 +317,11 @@ msgstr "" msgid "View of the Helpdesk teams page in Odoo Helpdesk." msgstr "" -#: ../../content/applications/services/helpdesk.rst:25 +#: ../../content/applications/services/helpdesk.rst:24 msgid "On the blank Helpdesk team form, enter a :guilabel:`Name` for the new team. Then, enter a description of the team in the field below the team name, if desired. To change the company this team is assigned to, select it from the :guilabel:`Company` drop-down menu." msgstr "" -#: ../../content/applications/services/helpdesk.rst:30 +#: ../../content/applications/services/helpdesk.rst:29 msgid "The team description is published on the public facing :doc:`website form `, where customers and portal users submit tickets. The description included in this field should **not** include any information that is for internal use only." msgstr "" @@ -260,63 +329,63 @@ msgstr "" msgid "View of a Helpdesk team's website form displaying the team description." msgstr "" -#: ../../content/applications/services/helpdesk.rst:40 +#: ../../content/applications/services/helpdesk.rst:39 msgid "Visibility & Assignment" msgstr "" -#: ../../content/applications/services/helpdesk.rst:42 +#: ../../content/applications/services/helpdesk.rst:41 msgid "The *Visibility* settings alter which internal users and portal users have access to this team and its tickets. The *Assignment* settings alter how users are assigned to handle each ticket." msgstr "" -#: ../../content/applications/services/helpdesk.rst:46 +#: ../../content/applications/services/helpdesk.rst:45 msgid "Determine team visibility" msgstr "" -#: ../../content/applications/services/helpdesk.rst:48 +#: ../../content/applications/services/helpdesk.rst:47 msgid "Under the :guilabel:`Visibility` section, select one of the following options to determine who can view this team and its tickets:" msgstr "" -#: ../../content/applications/services/helpdesk.rst:51 +#: ../../content/applications/services/helpdesk.rst:50 msgid ":guilabel:`Invited internal users (private)`: internal users can access the team and the tickets they are following. This access can be modified on each ticket individually by adding or removing the user as a follower. Internal users are considered *invited* once they are added as followers to an individual ticket, or :ref:`to the team itself `." msgstr "" -#: ../../content/applications/services/helpdesk.rst:55 +#: ../../content/applications/services/helpdesk.rst:54 msgid ":guilabel:`All internal users (company)`: all internal users can access the team and all of its tickets." msgstr "" -#: ../../content/applications/services/helpdesk.rst:57 +#: ../../content/applications/services/helpdesk.rst:56 msgid ":guilabel:`Invited portal users and all internal users (public)`: all internal users can access the team and all of its tickets. Portal users can only access the tickets they are following." msgstr "" -#: ../../content/applications/services/helpdesk.rst:61 +#: ../../content/applications/services/helpdesk.rst:60 msgid "A `Customer Support` team, meant to handle general shipping and product issues, would have the visibility set on :guilabel:`Invited portal users and all internal users`." msgstr "" -#: ../../content/applications/services/helpdesk.rst:64 +#: ../../content/applications/services/helpdesk.rst:63 msgid "At the same time, a `Financial Services` team handling tickets related to accounting or tax information would only need to be visible to :guilabel:`Invited internal users`." msgstr "" -#: ../../content/applications/services/helpdesk.rst:68 +#: ../../content/applications/services/helpdesk.rst:67 msgid "A team's visibility can be altered after the initial configuration. However, if the team changes from public access to either private or company-only access, portal users are removed as followers from both the team, and from individual tickets." msgstr "" -#: ../../content/applications/services/helpdesk.rst:75 +#: ../../content/applications/services/helpdesk.rst:74 msgid "Follow all team's tickets" msgstr "" -#: ../../content/applications/services/helpdesk.rst:77 +#: ../../content/applications/services/helpdesk.rst:76 msgid "If a user should be notified about any updates regarding tickets for this team, select their name from the :guilabel:`Followers` drop-down menu, located in the :guilabel:`Follow All Team's Tickets` field. Multiple users can be selected to follow a single team." msgstr "" -#: ../../content/applications/services/helpdesk.rst:82 +#: ../../content/applications/services/helpdesk.rst:81 msgid "External contacts can be selected in the :guilabel:`Followers` field. If the team's visibility is set to :guilabel:`Invited internal users (private)`, followers are notified about updates to the team's tickets, but are **not** able to view them in the portal." msgstr "" -#: ../../content/applications/services/helpdesk.rst:87 +#: ../../content/applications/services/helpdesk.rst:86 msgid "Automatically assign new tickets" msgstr "" -#: ../../content/applications/services/helpdesk.rst:89 +#: ../../content/applications/services/helpdesk.rst:88 msgid "When tickets are received, they need to be assigned to a member of the team. This is done either manually on each ticket individually, or through :guilabel:`Automatic Assignment`. Check the :guilabel:`Automatic Assignment` checkbox to enable this feature for the team." msgstr "" @@ -325,68 +394,68 @@ msgid "View of a Helpdesk team settings page emphasizing the automatic assignmen "Helpdesk." msgstr "" -#: ../../content/applications/services/helpdesk.rst:98 +#: ../../content/applications/services/helpdesk.rst:97 msgid "As soon as :guilabel:`Automatic Assignment` has been enabled, additional fields appear." msgstr "" -#: ../../content/applications/services/helpdesk.rst:100 +#: ../../content/applications/services/helpdesk.rst:99 msgid "Select one of the following assignment methods, based on how the workload should be allocated across the team:" msgstr "" -#: ../../content/applications/services/helpdesk.rst:103 +#: ../../content/applications/services/helpdesk.rst:102 msgid ":guilabel:`Each user is assigned an equal number of tickets`: tickets are assigned to team members based on total ticket count, regardless of the number of open or closed tickets they are currently assigned." msgstr "" -#: ../../content/applications/services/helpdesk.rst:106 +#: ../../content/applications/services/helpdesk.rst:105 msgid ":guilabel:`Each user has an equal number of open tickets`: tickets are assigned to team members based on how many open tickets they are currently assigned." msgstr "" -#: ../../content/applications/services/helpdesk.rst:110 +#: ../../content/applications/services/helpdesk.rst:109 msgid "When :guilabel:`Each user is assigned an equal number of tickets` is selected, the overall number of tickets assigned to team members is the same, but it does **not** consider the current workload." msgstr "" -#: ../../content/applications/services/helpdesk.rst:114 +#: ../../content/applications/services/helpdesk.rst:113 msgid "When :guilabel:`Each user has an equal number of open tickets` is selected, it ensures a balanced workload among team members, as it takes the current number of active tickets into account." msgstr "" -#: ../../content/applications/services/helpdesk.rst:117 +#: ../../content/applications/services/helpdesk.rst:116 msgid "Finally, add the :guilabel:`Team Members` who are to be assigned tickets for this team. Leave the field empty to include all employees who have the proper assignments and access rights configured in their user account settings." msgstr "" -#: ../../content/applications/services/helpdesk.rst:122 +#: ../../content/applications/services/helpdesk.rst:121 msgid "If an employee has time off scheduled in the *Time Off* application, they are **not** assigned tickets during that time. If no employees are available, the system looks ahead until there is a match." msgstr "" -#: ../../content/applications/services/helpdesk.rst:127 +#: ../../content/applications/services/helpdesk.rst:126 msgid ":ref:`Manage users `" msgstr "" -#: ../../content/applications/services/helpdesk.rst:128 +#: ../../content/applications/services/helpdesk.rst:127 msgid ":doc:`Access rights <../general/users/access_rights>`" msgstr "" -#: ../../content/applications/services/helpdesk.rst:131 +#: ../../content/applications/services/helpdesk.rst:130 msgid "Create or modify stages" msgstr "" -#: ../../content/applications/services/helpdesk.rst:133 +#: ../../content/applications/services/helpdesk.rst:132 msgid "*Stages* are used to organize the *Helpdesk* pipeline and track the progress of tickets. Stages are customizable, and can be renamed to fit the needs of each team." msgstr "" -#: ../../content/applications/services/helpdesk.rst:137 +#: ../../content/applications/services/helpdesk.rst:136 msgid ":ref:`Developer mode ` **must** be activated to access the stages menu. To activate developer mode, go to :menuselection:`Settings app --> General Settings --> Developer Tools`, and click :guilabel:`Activate the developer mode`." msgstr "" -#: ../../content/applications/services/helpdesk.rst:141 +#: ../../content/applications/services/helpdesk.rst:140 msgid "To view or modify *Helpdesk* stages, go to :menuselection:`Helpdesk app --> Configuration --> Stages`." msgstr "" -#: ../../content/applications/services/helpdesk.rst:144 +#: ../../content/applications/services/helpdesk.rst:143 msgid "The default list view on the :guilabel:`Stages` page displays the stages currently available in *Helpdesk*. They are listed in the order they appear in the pipeline." msgstr "" -#: ../../content/applications/services/helpdesk.rst:147 -msgid "To change the order of the stages, click the :guilabel:`(six square)` icon, to the left of the stage name, and drag it to the desired place on the list." +#: ../../content/applications/services/helpdesk.rst:146 +msgid "To change the order of the stages, click the :icon:`oi-draggable` :guilabel:`(drag)` icon, to the left of the stage name, and drag it to the desired place on the list." msgstr "" #: ../../content/applications/services/helpdesk.rst:-1 @@ -394,15 +463,15 @@ msgid "View of the stage list page emphasizing the buttons used to change the or "appear in the list." msgstr "" -#: ../../content/applications/services/helpdesk.rst:156 +#: ../../content/applications/services/helpdesk.rst:155 msgid "Change the stage order on the Kanban view of a *Helpdesk* team's pipeline by dragging and dropping individual columns." msgstr "" -#: ../../content/applications/services/helpdesk.rst:159 +#: ../../content/applications/services/helpdesk.rst:158 msgid "To create a new stage, click the :guilabel:`New` button at the top-left of the stage list. Doing so reveals a blank stage form." msgstr "" -#: ../../content/applications/services/helpdesk.rst:162 +#: ../../content/applications/services/helpdesk.rst:161 msgid "Choose a :guilabel:`Name` for the new stage, and add a description, if desired. Then, proceed to fill out the remaining fields following the steps below." msgstr "" @@ -410,20 +479,20 @@ msgstr "" msgid "View of a stage's settings page in Odoo Helpdesk." msgstr "" -#: ../../content/applications/services/helpdesk.rst:170 +#: ../../content/applications/services/helpdesk.rst:169 msgid "Add email and SMS templates to stages" msgstr "" -#: ../../content/applications/services/helpdesk.rst:172 +#: ../../content/applications/services/helpdesk.rst:171 msgid "When an :guilabel:`Email Template` is added to a stage, an email is automatically sent to the customer when a ticket reaches that specific stage in the pipeline. Likewise, adding an :guilabel:`SMS Template` triggers an SMS text message to send to the customer." msgstr "" -#: ../../content/applications/services/helpdesk.rst:177 +#: ../../content/applications/services/helpdesk.rst:176 msgid "SMS Text Messaging is an :doc:`In-App Purchase (IAP) ` service that requires prepaid credits to work. Refer to `SMS Pricing FAQ `_ for additional information." msgstr "" -#: ../../content/applications/services/helpdesk.rst:181 -msgid "To select an existing email template, select it from the :guilabel:`Email Template` field. Click on the :guilabel:`→ (Internal Link)` icon to the right of the field to edit the chosen template." +#: ../../content/applications/services/helpdesk.rst:180 +msgid "To select an existing email template, select it from the :guilabel:`Email Template` field. Click on the :icon:`oi-arrow-right` :guilabel:`(right arrow)` icon to the right of the field to edit the chosen template." msgstr "" #: ../../content/applications/services/helpdesk.rst:184 @@ -487,7 +556,7 @@ msgid "View a specific team's pipeline by navigating to :menuselection:`Helpdesk msgstr "" #: ../../content/applications/services/helpdesk.rst:230 -msgid "Select a stage to fold temporarily, then click the :guilabel:`⚙️ (gear)` icon, and select :guilabel:`Fold`." +msgid "Select a stage to fold temporarily, then click the :icon:`fa-gear` :guilabel:`(gear)` icon, and select :guilabel:`Fold` from the drop-down menu." msgstr "" #: ../../content/applications/services/helpdesk.rst:-1 @@ -499,6 +568,22 @@ msgid "Manually folding a stage from the Kanban view is temporary and does **not msgstr "" #: ../../content/applications/services/helpdesk.rst:242 +msgid "Merge tickets" +msgstr "" + +#: ../../content/applications/services/helpdesk.rst:244 +msgid "If duplicate tickets are found in *Helpdesk*, they can be combined into a single ticket using the *merge* feature." +msgstr "" + +#: ../../content/applications/services/helpdesk.rst:248 +msgid "The *merge* feature is **only** accessible if the :doc:`Data Cleaning <../productivity/data_cleaning>` application is installed on the database." +msgstr "" + +#: ../../content/applications/services/helpdesk.rst:251 +msgid "To merge two or more tickets, navigate to :menuselection:`Helpdesk app --> Tickets --> All Tickets`. Identify the tickets to be merged, and tick the checkbox at the far-left of each ticket to select them. Then, click the :icon:`fa-cog` :guilabel:`Actions` icon, and select :guilabel:`Merge` from the drop-down menu. Doing so opens a new page where the selected tickets are listed with their :guilabel:`Similarity` rating. From here, click either :ref:`Merge ` to combine the tickets, or :guilabel:`DISCARD`." +msgstr "" + +#: ../../content/applications/services/helpdesk.rst:259 msgid "`Odoo Tutorials: Helpdesk `_" msgstr "" @@ -3302,11 +3387,11 @@ msgstr "" msgid "`Odoo Tutorials: Kanban Project Management `_" msgstr "" -#: ../../content/applications/services/project/project_management.rst:19 +#: ../../content/applications/services/project/project_management.rst:21 msgid "Open the **Project** app and click :guilabel:`Create` to start a new project. Enter a :guilabel:`Name` for your project and click :guilabel:`Create Project`." msgstr "" -#: ../../content/applications/services/project/project_management.rst:22 +#: ../../content/applications/services/project/project_management.rst:24 msgid "You can customize your existing **projects** from the dashboard by clicking the drop-down toggle button (:guilabel:`⋮`) on your project's **card**." msgstr "" @@ -3314,59 +3399,59 @@ msgstr "" msgid "Project card" msgstr "" -#: ../../content/applications/services/project/project_management.rst:29 +#: ../../content/applications/services/project/project_management.rst:31 msgid "This enables a new menu divided into four parts:" msgstr "" -#: ../../content/applications/services/project/project_management.rst:31 +#: ../../content/applications/services/project/project_management.rst:33 msgid ":guilabel:`View`: see an overview of your project's components, such as its :guilabel:`Tasks`, :guilabel:`Milestones` and :guilabel:`Project Updates`. Depending on which apps you have activated, more options may be available, such as :guilabel:`Documents`. All uploaded files can be found under this menu, as well as in the **Documents** app, under :guilabel:`Projects`;" msgstr "" -#: ../../content/applications/services/project/project_management.rst:35 +#: ../../content/applications/services/project/project_management.rst:37 msgid ":guilabel:`Reporting`: analyze your project's progress and profitability through graphics and statistics;" msgstr "" -#: ../../content/applications/services/project/project_management.rst:37 +#: ../../content/applications/services/project/project_management.rst:39 msgid "**Color**: make a line of color appear on the left side of the card so that your project is more recognizable;" msgstr "" -#: ../../content/applications/services/project/project_management.rst:39 +#: ../../content/applications/services/project/project_management.rst:41 msgid ":guilabel:`Settings`: you can change the following:" msgstr "" -#: ../../content/applications/services/project/project_management.rst:41 +#: ../../content/applications/services/project/project_management.rst:43 msgid "the :guilabel:`Name` of the project;" msgstr "" -#: ../../content/applications/services/project/project_management.rst:42 +#: ../../content/applications/services/project/project_management.rst:44 msgid "the :guilabel:`Name of the tasks` found under that project;" msgstr "" -#: ../../content/applications/services/project/project_management.rst:43 +#: ../../content/applications/services/project/project_management.rst:45 msgid "the :guilabel:`Customer` for whom the project is intended;" msgstr "" -#: ../../content/applications/services/project/project_management.rst:44 +#: ../../content/applications/services/project/project_management.rst:46 msgid "the :guilabel:`Tags` used for filtering;" msgstr "" -#: ../../content/applications/services/project/project_management.rst:45 +#: ../../content/applications/services/project/project_management.rst:47 msgid "the :guilabel:`Company` responsible for the project;" msgstr "" -#: ../../content/applications/services/project/project_management.rst:46 +#: ../../content/applications/services/project/project_management.rst:48 msgid "the employee designated as :guilabel:`Project Manager`;" msgstr "" -#: ../../content/applications/services/project/project_management.rst:47 +#: ../../content/applications/services/project/project_management.rst:49 msgid "the :guilabel:`Planned Date` of the project;" msgstr "" -#: ../../content/applications/services/project/project_management.rst:48 +#: ../../content/applications/services/project/project_management.rst:50 msgid "the total :guilabel:`Allocated Hours` for that project." msgstr "" -#: ../../content/applications/services/project/project_management.rst:50 +#: ../../content/applications/services/project/project_management.rst:52 msgid "Additionally, you can mark the project as :guilabel:`Favorite`, allowing you to find it using the :guilabel:`My Favorites` filter on the Kanban view;" msgstr "" @@ -3374,76 +3459,28 @@ msgstr "" msgid "Project settings" msgstr "" -#: ../../content/applications/services/project/project_management.rst:58 +#: ../../content/applications/services/project/project_management.rst:60 msgid "`Odoo Tutorials: Customize projects `_" msgstr "" -#: ../../content/applications/services/project/project_management.rst:61 +#: ../../content/applications/services/project/project_management.rst:63 msgid "Further settings are available under the :guilabel:`Settings` tab. Most of them are *only* available depending on the activated apps." msgstr "" -#: ../../content/applications/services/project/project_management.rst:65 +#: ../../content/applications/services/project/project_management.rst:67 msgid "Scheduling activities" msgstr "" -#: ../../content/applications/services/project/project_management.rst:67 +#: ../../content/applications/services/project/project_management.rst:69 msgid "You can schedule **activities** (ex. :guilabel:`Call`, :guilabel:`Meeting`, etc.) per project by clicking on the **clock** icon on a project. Doing so opens a list with already scheduled activities and allows planning **new** activities by clicking :guilabel:`+ Schedule an activity`. On the pop-up window, select the :guilabel:`Activity Type`, enter a :guilabel:`Summary` for that activity, a :guilabel:`Due Date`, and assign it to an employee. According to the :guilabel:`Activity Type`, you may have **additional options** available." msgstr "" -#: ../../content/applications/services/project/project_management.rst:75 +#: ../../content/applications/services/project/project_management.rst:77 msgid "If an activity is **already** scheduled, the icon may change to a **phone**, **group of people**, or other." msgstr "" #: ../../content/applications/services/project/tasks.rst:5 -msgid "Tasks" -msgstr "" - -#: ../../content/applications/services/project/tasks/email_alias.rst:3 -msgid "Create Project's Tasks from an Email Alias" -msgstr "" - -#: ../../content/applications/services/project/tasks/email_alias.rst:5 -msgid "When you already have an email address that customers know from the top of their heads, changing it is the last thing you want to do. Instead, link that address to your project and transform those conversations into structured work. It automatically creates a task in the first stage of a project." -msgstr "" - -#: ../../content/applications/services/project/tasks/email_alias.rst:11 -msgid "Set up an incoming email server" -msgstr "" - -#: ../../content/applications/services/project/tasks/email_alias.rst:14 -msgid "On the *Settings* application, enable *External Email Servers* and define the incoming email alias you would like to use." -msgstr "" - -#: ../../content/applications/services/project/tasks/email_alias.rst:15 -msgid "**For more information**: :doc:`/applications/general/email_communication/email_servers`" -msgstr "" - -#: ../../content/applications/services/project/tasks/email_alias.rst:18 -msgid "Configure the email alias in your project" -msgstr "" - -#: ../../content/applications/services/project/tasks/email_alias.rst:22 -msgid "Now that you have the incoming email server set up, go to :menuselection:`Project --> Configuration --> Projects --> Edit`. Under the *Emails* tab, define the wanted email alias and choose the policy to receive a message." -msgstr "" - -#: ../../content/applications/services/project/tasks/email_alias.rst:23 -msgid "In addition, you can now directly set it when creating a new project." -msgstr "" - -#: ../../content/applications/services/project/tasks/email_alias.rst:-1 -msgid "In the settings of your project, define the emails alias under the tab email in Odoo Project" -msgstr "" - -#: ../../content/applications/services/project/tasks/email_alias.rst:30 -msgid "All the recipients of the email (To/Cc/Bcc) are automatically added as followers of the task." -msgstr "" - -#: ../../content/applications/services/project/tasks/email_alias.rst:32 -msgid "The email can be seen under the name of your project on the dashboard." -msgstr "" - -#: ../../content/applications/services/project/tasks/email_alias.rst:-1 -msgid "View of the email alias chosen on the dashboard view in Odoo Project" +msgid "Task management" msgstr "" #: ../../content/applications/services/project/tasks/recurring_tasks.rst:3 @@ -3506,6 +3543,326 @@ msgstr "" msgid "**To stop** the recurrence, open the last task in recurrence and press the :guilabel:`Recurrent` button next to the :guilabel:`Planned date`." msgstr "" +#: ../../content/applications/services/project/tasks/task_creation.rst:3 +msgid "Task creation" +msgstr "" + +#: ../../content/applications/services/project/tasks/task_creation.rst:5 +msgid "Tasks in Odoo Project can be created manually or automatically, including from emails or website forms." +msgstr "" + +#: ../../content/applications/services/project/tasks/task_creation.rst:9 +msgid "Manual task creation" +msgstr "" + +#: ../../content/applications/services/project/tasks/task_creation.rst:11 +msgid "Open the Project app and choose the desired project. Create a new task by doing one of the following:" +msgstr "" + +#: ../../content/applications/services/project/tasks/task_creation.rst:14 +msgid "Clicking the :icon:`fa-plus` (:guilabel:`plus`) button in the upper left corner. This creates a new task in the first stage of your Kanban view." +msgstr "" + +#: ../../content/applications/services/project/tasks/task_creation.rst:16 +msgid "Pressing the :icon:`fa-plus` (:guilabel:`plus`) button next to the Kanban stage name. This creates a new task in this Kanban stage." +msgstr "" + +#: ../../content/applications/services/project/tasks/task_creation.rst:19 +msgid "Fill in the :guilabel:`Task Title` and add one or more :guilabel:`Assignees`, then click :guilabel:`Add`." +msgstr "" + +#: ../../content/applications/services/project/tasks/task_creation.rst:23 +msgid "Task configuration" +msgstr "" + +#: ../../content/applications/services/project/tasks/task_creation.rst:25 +msgid "Click the task to open it. The task form includes the following fields that you can fill in:" +msgstr "" + +#: ../../content/applications/services/project/tasks/task_creation.rst:27 +msgid ":guilabel:`Task Title`: title of the task." +msgstr "" + +#: ../../content/applications/services/project/tasks/task_creation.rst:28 +msgid ":icon:`fa-star-o` (:guilabel:`Star`): click the :icon:`fa-star-o` (:guilabel:`star`) icon to mark the task as high priority. The icon will turn yellow. Click it again to remove the high priority." +msgstr "" + +#: ../../content/applications/services/project/tasks/task_creation.rst:30 +msgid ":guilabel:`Project`: the project that this task belongs to." +msgstr "" + +#: ../../content/applications/services/project/tasks/task_creation.rst:31 +msgid ":guilabel:`Assignees`: the person(s) in charge of handling the work on this task." +msgstr "" + +#: ../../content/applications/services/project/tasks/task_creation.rst:32 +msgid ":guilabel:`Tags`: custom labels allowing to categorize and filter your tasks." +msgstr "" + +#: ../../content/applications/services/project/tasks/task_creation.rst:33 +msgid ":guilabel:`Customer`: the person or company that will be billed for this task. This field only appears in tasks that belong to billable projects." +msgstr "" + +#: ../../content/applications/services/project/tasks/task_creation.rst:35 +msgid ":guilabel:`Sales Order Item`: this can be either the sales order that was used to create this task, or a sales order that was linked to this task manually. This field only appears in tasks linked to billable projects." +msgstr "" + +#: ../../content/applications/services/project/tasks/task_creation.rst:38 +msgid ":guilabel:`Allocated Time`: the amount of time that the work on this task is expected to last, tracked by timesheets." +msgstr "" + +#: ../../content/applications/services/project/tasks/task_creation.rst:40 +msgid ":guilabel:`Deadline`: the expected end date of the task. Once this field is filled in, you can also add a start date to designate the entire time frame of the tasks' duration." +msgstr "" + +#: ../../content/applications/services/project/tasks/task_creation.rst:45 +msgid "You can also create new tasks by switching to the list or Gantt view and clicking :guilabel:`New`." +msgstr "" + +#: ../../content/applications/services/project/tasks/task_creation.rst:47 +msgid "The following fields can also be edited directly from the Kanban view without opening the individual task: :icon:`fa-star-o` (**priority**), :guilabel:`Allocated hours`, :guilabel:`Assignees`, and **task status**. You can also **color code** or :guilabel:`Set a Cover image` to your task by clicking the :icon:`fa-ellipsis-v` (**vertical ellipsis**)." +msgstr "" + +#: ../../content/applications/services/project/tasks/task_creation.rst:51 +msgid "You can use the following keyboard shortcuts in the task title to configure new tasks (modify the values in the examples below according to your needs):" +msgstr "" + +#: ../../content/applications/services/project/tasks/task_creation.rst:54 +msgid "**30h**: to allocate 30 hours to the task." +msgstr "" + +#: ../../content/applications/services/project/tasks/task_creation.rst:55 +msgid "**#tags**: to add tags to the task." +msgstr "" + +#: ../../content/applications/services/project/tasks/task_creation.rst:56 +msgid "**@user**: to assign the task to a user." +msgstr "" + +#: ../../content/applications/services/project/tasks/task_creation.rst:57 +msgid "**!**: to star the task as high priority." +msgstr "" + +#: ../../content/applications/services/project/tasks/task_creation.rst:59 +msgid "Along with using the correct format, follow this order: the task's name, followed by the allocated time, the tags, the assignee, and then the priority." +msgstr "" + +#: ../../content/applications/services/project/tasks/task_creation.rst:62 +msgid "For example, if you want to create a task named \"Prepare workshop\", allocate 5h hours to it, add the \"School\" tag, assign it to Audrey and set its priority to :guilabel:`High`, enter the following task title: Prepare workshop 5h #school @Audrey !" +msgstr "" + +#: ../../content/applications/services/project/tasks/task_creation.rst:0 +msgid "Using keyboard shortcuts to create a task in Project." +msgstr "" + +#: ../../content/applications/services/project/tasks/task_creation.rst:70 +msgid "Creating tasks from an email alias" +msgstr "" + +#: ../../content/applications/services/project/tasks/task_creation.rst:72 +msgid "This feature allows for project tasks to be automatically created once an email is delivered to a designated email address." +msgstr "" + +#: ../../content/applications/services/project/tasks/task_creation.rst:75 +msgid "To configure it, open the Project app, then click the :icon:`fa-ellipsis-v` (:guilabel:`vertical ellipsis`) icon next to the desired project's name. Select :guilabel:`Settings`, then open the :guilabel:`Settings` tab." +msgstr "" + +#: ../../content/applications/services/project/tasks/task_creation.rst:79 +msgid "Fill in the :guilabel:`Create tasks by sending an email to` field as follows:" +msgstr "" + +#: ../../content/applications/services/project/tasks/task_creation.rst:81 +msgid "**Section of the alias before the @ symbol**: type the name of the email alias, e.g. `contact`, `help`, `jobs`." +msgstr "" + +#: ../../content/applications/services/project/tasks/task_creation.rst:83 +msgid "**Domain**: in most cases, this is filled in by default with your :doc:`domain <../../../general/email_communication/email_servers>`." +msgstr "" + +#: ../../content/applications/services/project/tasks/task_creation.rst:85 +msgid "**Accept Emails From**: refine the senders whose emails will create tasks in the project." +msgstr "" + +#: ../../content/applications/services/project/tasks/task_creation.rst:-1 +msgid "View of the email alias chosen on the dashboard view in Odoo Project" +msgstr "" + +#: ../../content/applications/services/project/tasks/task_creation.rst:90 +msgid "Once configured, the email alias can be seen under the name of your project on the Kanban dashboard." +msgstr "" + +#: ../../content/applications/services/project/tasks/task_creation.rst:92 +msgid "When an email is sent to the alias, the email is automatically converted into a project task. The following rules apply:" +msgstr "" + +#: ../../content/applications/services/project/tasks/task_creation.rst:95 +msgid "The email sender is displayed in the :guilabel:`Customer` field." +msgstr "" + +#: ../../content/applications/services/project/tasks/task_creation.rst:96 +msgid "The email subject is displayed in the :guilabel:`Task Title` field." +msgstr "" + +#: ../../content/applications/services/project/tasks/task_creation.rst:97 +msgid "The email body is displayed in the :guilabel:`Description` field." +msgstr "" + +#: ../../content/applications/services/project/tasks/task_creation.rst:98 +msgid "The whole content of the email is additionally displayed in the **chatter**." +msgstr "" + +#: ../../content/applications/services/project/tasks/task_creation.rst:99 +msgid "All the recipients of the email (To/Cc/Bcc) that are Odoo users are automatically added as **followers** of the task." +msgstr "" + +#: ../../content/applications/services/project/tasks/task_creation.rst:103 +msgid "Creating tasks from a website form" +msgstr "" + +#: ../../content/applications/services/project/tasks/task_creation.rst:105 +msgid "If you have the Website app installed in your database, you can configure any form on your website to trigger the creation of tasks in a project." +msgstr "" + +#: ../../content/applications/services/project/tasks/task_creation.rst:108 +msgid "Go to the website page where you wish to add the the form and :ref:`add the Form building block `." +msgstr "" + +#: ../../content/applications/services/project/tasks/task_creation.rst:110 +msgid "In the website editor, edit the following fields:" +msgstr "" + +#: ../../content/applications/services/project/tasks/task_creation.rst:112 +msgid ":guilabel:`Action`: select :guilabel:`Create a Task`." +msgstr "" + +#: ../../content/applications/services/project/tasks/task_creation.rst:113 +msgid ":guilabel:`Project`: choose the project that you want the new tasks to be created in." +msgstr "" + +#: ../../content/applications/services/project/tasks/task_creation.rst:115 +msgid ":ref:`Customize the form `." +msgstr "" + +#: ../../content/applications/services/project/tasks/task_creation.rst:117 +msgid "When the form is submitted, it automatically creates a project task. The task's content is defined by the form's corresponding fields." +msgstr "" + +#: ../../content/applications/services/project/tasks/task_creation.rst:121 +msgid ":doc:`Dynamic website content <../../../websites/website/web_design/building_blocks/dynamic_content>`" +msgstr "" + +#: ../../content/applications/services/project/tasks/task_stages_statuses.rst:3 +msgid "Task stages and statuses" +msgstr "" + +#: ../../content/applications/services/project/tasks/task_stages_statuses.rst:6 +msgid "Task stages" +msgstr "" + +#: ../../content/applications/services/project/tasks/task_stages_statuses.rst:8 +msgid "Task stages are displayed as columns in the project's Kanban view, and allow you to update the progress of its tasks with a drag-and-drop. In most projects, the stages will be akin to **New**, **In progress**, **Backlog**, etc." +msgstr "" + +#: ../../content/applications/services/project/tasks/task_stages_statuses.rst:12 +msgid "By default, task stages are project-specific but can be shared across multiple projects that follow the same workflow." +msgstr "" + +#: ../../content/applications/services/project/tasks/task_stages_statuses.rst:16 +msgid "Creating task stages" +msgstr "" + +#: ../../content/applications/services/project/tasks/task_stages_statuses.rst:18 +msgid "Odoo Project doesn’t provide default stages but instead allows you to create custom stages tailored to your specific business needs. You are prompted to do so immediately after :ref:`creating a new project `." +msgstr "" + +#: ../../content/applications/services/project/tasks/task_stages_statuses.rst:22 +msgid "To create a stage, type its name into the :guilabel:`Stage...` field, then click :guilabel:`Add`." +msgstr "" + +#: ../../content/applications/services/project/tasks/task_stages_statuses.rst:25 +msgid "Click :guilabel:`See examples` to find ideas for stage names applicable to your line of business." +msgstr "" + +#: ../../content/applications/services/project/tasks/task_stages_statuses.rst:28 +msgid "Editing task stages" +msgstr "" + +#: ../../content/applications/services/project/tasks/task_stages_statuses.rst:30 +msgid "To edit the task stage, click the :icon:`fa-cog` (:guilabel:`cog`) icon next to its name. From there, click one of the following:" +msgstr "" + +#: ../../content/applications/services/project/tasks/task_stages_statuses.rst:33 +msgid ":guilabel:`Fold`: to hide the task stage and all of the tasks in this stage from the Kanban view." +msgstr "" + +#: ../../content/applications/services/project/tasks/task_stages_statuses.rst:34 +msgid ":guilabel:`Edit`:" +msgstr "" + +#: ../../content/applications/services/project/tasks/task_stages_statuses.rst:36 +msgid ":guilabel:`Name`: to change the name of the stage." +msgstr "" + +#: ../../content/applications/services/project/tasks/task_stages_statuses.rst:37 +msgid ":guilabel:`SMS/Email Template`: to automatically send an email or SMS notification to the customer when a task reaches this stage." +msgstr "" + +#: ../../content/applications/services/project/tasks/task_stages_statuses.rst:39 +msgid ":guilabel:`Folded in Kanban`: to hide the task stage and all of the tasks in this stage from the Kanban view." +msgstr "" + +#: ../../content/applications/services/project/tasks/task_stages_statuses.rst:41 +msgid ":guilabel:`Projects`: to share this task stage between several projects." +msgstr "" + +#: ../../content/applications/services/project/tasks/task_stages_statuses.rst:42 +msgid ":guilabel:`Automations`: to create :doc:`custom rules that trigger automatic actions <../../../studio/automated_actions>` (e.g., creating activities, adding followers, or sending webhook notifications). Note that this will activate Studio in your database, which may impact your pricing plan." +msgstr "" + +#: ../../content/applications/services/project/tasks/task_stages_statuses.rst:47 +msgid ":guilabel:`Delete`: to delete this stage." +msgstr "" + +#: ../../content/applications/services/project/tasks/task_stages_statuses.rst:48 +msgid ":guilabel:`Archive/Unarchive all`: to archive or unarchive all of the tasks in this stage." +msgstr "" + +#: ../../content/applications/services/project/tasks/task_stages_statuses.rst:51 +msgid "Task statuses" +msgstr "" + +#: ../../content/applications/services/project/tasks/task_stages_statuses.rst:53 +msgid "Task statuses are used to track the status of tasks within the Kanban stage, as well as to close the task when it’s done or canceled. Unlike Kanban stages, they cannot be customized; five task statuses exist in Odoo and are used as follows:" +msgstr "" + +#: ../../content/applications/services/project/tasks/task_stages_statuses.rst:57 +msgid ":guilabel:`In Progress`: this is the default state of all tasks, meaning that work required for the task to move to the next Kanban stage is ongoing." +msgstr "" + +#: ../../content/applications/services/project/tasks/task_stages_statuses.rst:59 +msgid ":guilabel:`Changes Requested`: to highlight that changes, either requested by the customer or internally, are needed before the task is moved to the next Kanban stage." +msgstr "" + +#: ../../content/applications/services/project/tasks/task_stages_statuses.rst:61 +msgid ":guilabel:`Approved`: to highlight that the task is ready to be moved to the next stage." +msgstr "" + +#: ../../content/applications/services/project/tasks/task_stages_statuses.rst:62 +msgid ":guilabel:`Canceled`: to cancel the task." +msgstr "" + +#: ../../content/applications/services/project/tasks/task_stages_statuses.rst:63 +msgid ":guilabel:`Done`: to close the task once it's been completed." +msgstr "" + +#: ../../content/applications/services/project/tasks/task_stages_statuses.rst:67 +msgid "The :guilabel:`Changes Requested` and :guilabel:`Approved` task statuses are cleared as soon as the task is moved to another Kanban stage. The task status reverts to the default :guilabel:`In Progress` status so that :guilabel:`Changes Requested` or :guilabel:`Approved` status can be applied again once the necessary work has been completed in this Kanban stage." +msgstr "" + +#: ../../content/applications/services/project/tasks/task_stages_statuses.rst:71 +msgid "The :guilabel:`Done` and :guilabel:`Canceled` statuses are independent from the Kanban stage. Once a task is marked as :guilabel:`Done` or :guilabel:`Canceled`, it is closed. If needed, it can be reopened by changing its status." +msgstr "" + #: ../../content/applications/services/timesheets.rst:8 msgid "Timesheets" msgstr "" diff --git a/locale/sources/studio.pot b/locale/sources/studio.pot index dfec9b099..1af208143 100644 --- a/locale/sources/studio.pot +++ b/locale/sources/studio.pot @@ -8,7 +8,7 @@ msgid "" msgstr "" "Project-Id-Version: Odoo 17.0\n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2024-05-31 09:59+0000\n" +"POT-Creation-Date: 2024-07-23 13:30+0000\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME \n" "Language-Team: LANGUAGE \n" @@ -20,46 +20,174 @@ msgstr "" msgid "Studio" msgstr "" -#: ../../content/applications/studio.rst:17 -msgid "Studio is a toolbox that allows you to customize Odoo without coding knowledge. For example, you can, on any app, add or modify:" -msgstr "" - -#: ../../content/applications/studio.rst:20 -msgid ":doc:`Fields `" +#: ../../content/applications/studio.rst:18 +msgid "Studio is a toolbox that allows you to customize Odoo without coding knowledge. For example, you can, in any app, add or modify:" msgstr "" #: ../../content/applications/studio.rst:21 -msgid ":doc:`Views `" +msgid ":doc:`Fields `" msgstr "" #: ../../content/applications/studio.rst:22 -msgid ":doc:`Models `" +msgid ":doc:`Views `" msgstr "" #: ../../content/applications/studio.rst:23 -msgid ":doc:`Automated actions `" +msgid ":doc:`Models `" msgstr "" #: ../../content/applications/studio.rst:24 -msgid ":doc:`PDF reports `" +msgid ":doc:`Automated actions `" msgstr "" #: ../../content/applications/studio.rst:25 -msgid "Approval rules" +msgid ":doc:`PDF reports `" msgstr "" #: ../../content/applications/studio.rst:26 +msgid ":doc:`Approval rules `" +msgstr "" + +#: ../../content/applications/studio.rst:27 msgid "Security rules" msgstr "" -#: ../../content/applications/studio.rst:28 -msgid "Or you can :doc:`build an app from scratch `." +#: ../../content/applications/studio.rst:29 +msgid "You can also :doc:`build an app from scratch `." msgstr "" -#: ../../content/applications/studio.rst:31 +#: ../../content/applications/studio.rst:33 +msgid "To access Studio, navigate to the app and model you want to modify, then click the **Toggle Studio** button, or vice versa." +msgstr "" + +#: ../../content/applications/studio.rst:36 +msgid "To close Studio, click :guilabel:`Close` in the upper right corner." +msgstr "" + +#: ../../content/applications/studio.rst:39 msgid "`Odoo Tutorials: Studio `_" msgstr "" +#: ../../content/applications/studio/approval_rules.rst:3 +msgid "Approval rules" +msgstr "" + +#: ../../content/applications/studio/approval_rules.rst:5 +msgid "Studio approval rules are used to automate approval processes for actions. They allow you to define the criteria for when an approval is required before an action can be performed using a button." +msgstr "" + +#: ../../content/applications/studio/approval_rules.rst:9 +msgid "Configuration" +msgstr "" + +#: ../../content/applications/studio/approval_rules.rst:11 +msgid "To add approval rules, proceed as follows:" +msgstr "" + +#: ../../content/applications/studio/approval_rules.rst:13 +msgid ":ref:`Open Studio ` and switch to the required :doc:`view `." +msgstr "" + +#: ../../content/applications/studio/approval_rules.rst:14 +msgid "Select the button for which you want to add approval rules." +msgstr "" + +#: ../../content/applications/studio/approval_rules.rst:15 +msgid "In the :guilabel:`Properties` tab on the left, enable the :guilabel:`Set approval rules` feature." +msgstr "" + +#: ../../content/applications/studio/approval_rules.rst:17 +msgid "Specify the :guilabel:`Allowed Group` to limit the approval permission to a specific user group." +msgstr "" + +#: ../../content/applications/studio/approval_rules.rst:19 +msgid "Select the :guilabel:`Responsible` user to create an activity for a specific user when approval is requested from them." +msgstr "" + +#: ../../content/applications/studio/approval_rules.rst:21 +msgid "Select the :guilabel:`Users to notify` via internal note." +msgstr "" + +#: ../../content/applications/studio/approval_rules.rst:22 +msgid "Add a :guilabel:`Description` to be displayed in the :ref:`Approval dialog `." +msgstr "" + +#: ../../content/applications/studio/approval_rules.rst:24 +msgid "Optionally, you can also add conditions for the approval rule to be applied by clicking the :icon:`fa-filter` (:guilabel:`filter`) icon next to the :guilabel:`Allowed Group` field." +msgstr "" + +#: ../../content/applications/studio/approval_rules.rst:27 +msgid "To add another rule, click :guilabel:`Add an approval rule`. When there are multiple approval rules, you can:" +msgstr "" + +#: ../../content/applications/studio/approval_rules.rst:30 +msgid "enable :guilabel:`Exclusive Approval` to require approvers to be different users;" +msgstr "" + +#: ../../content/applications/studio/approval_rules.rst:31 +msgid "change the :guilabel:`Notification Order` of the approval rule so that the :guilabel:`Responsible` and :guilabel:`Users to notify` are only notified when the previous rule has been approved, and their approval is required. If the approval rules have the same :guilabel:`Notification Order`, all users are notified at the same time when the first approval is requested." +msgstr "" + +#: ../../content/applications/studio/approval_rules.rst:36 +msgid "Click the :icon:`fa-trash` (:guilabel:`trash`) icon next to the :guilabel:`Allowed Group` field to delete the approval rule." +msgstr "" + +#: ../../content/applications/studio/approval_rules.rst:40 +msgid "You can create :ref:`user groups ` specifically for approvals." +msgstr "" + +#: ../../content/applications/studio/approval_rules.rst:45 +msgid "Use" +msgstr "" + +#: ../../content/applications/studio/approval_rules.rst:47 +msgid "Once approval rules have been defined for a button:" +msgstr "" + +#: ../../content/applications/studio/approval_rules.rst:49 +msgid "A **user avatar** icon is displayed next to the button's label for each approval rule that has been defined." +msgstr "" + +#: ../../content/applications/studio/approval_rules.rst:0 +msgid "Confirm button with approval for purchase orders" +msgstr "" + +#: ../../content/applications/studio/approval_rules.rst:55 +msgid "When an unauthorized user clicks the button, an error message is displayed in the top-right corner and an activity is created for the user specified in the :guilabel:`Responsible` field." +msgstr "" + +#: ../../content/applications/studio/approval_rules.rst:57 +msgid "Only users from the group defined in the :guilabel:`Allowed Group` field are authorized to approve or reject the action." +msgstr "" + +#: ../../content/applications/studio/approval_rules.rst:60 +msgid "Authorized users can:" +msgstr "" + +#: ../../content/applications/studio/approval_rules.rst:62 +msgid "approve and perform the action by clicking the button;" +msgstr "" + +#: ../../content/applications/studio/approval_rules.rst:63 +msgid "approve the action and allow another user to perform it by clicking the **user avatar** icon next to the button's label, then clicking the :icon:`fa-check` (:guilabel:`Approve`) button in the dialog that opens;" +msgstr "" + +#: ../../content/applications/studio/approval_rules.rst:66 +msgid "reject the action by clicking the **user avatar** icon next to the button's label, then clicking the :icon:`fa-times` (:guilabel:`Reject`) button in the dialog that opens." +msgstr "" + +#: ../../content/applications/studio/approval_rules.rst:-1 +msgid "Approval dialog" +msgstr "" + +#: ../../content/applications/studio/approval_rules.rst:73 +msgid "The user who approved/rejected the action can revoke their decision by clicking the **user avatar** icon next to the button's label, then clicking the :icon:`fa-undo` (:guilabel:`Revoke`) button." +msgstr "" + +#: ../../content/applications/studio/approval_rules.rst:76 +msgid "Approvals are tracked in the record's chatter. An approval entry is also created every time a Studio approval-related action is performed. To access the approval entries, :doc:`activate the developer mode ` and go to :menuselection:`Settings --> Technical --> Studio Approval Entries`." +msgstr "" + #: ../../content/applications/studio/automated_actions.rst:3 msgid "Automation rules" msgstr "" diff --git a/locale/sources/websites.pot b/locale/sources/websites.pot index 82dd476a5..f2eb566f1 100644 --- a/locale/sources/websites.pot +++ b/locale/sources/websites.pot @@ -8,7 +8,7 @@ msgid "" msgstr "" "Project-Id-Version: Odoo 17.0\n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2024-06-24 07:08+0000\n" +"POT-Creation-Date: 2024-07-23 13:30+0000\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME \n" "Language-Team: LANGUAGE \n" @@ -296,12 +296,11 @@ msgid "To change the default behavior, go to :menuselection:`Website --> Configu msgstr "" #: ../../content/applications/websites/ecommerce/checkout_payment_shipping/cart.rst:28 -msgid "If a product has :doc:`optional products <../managing_products/cross_upselling>`, the **dialog box** will always appear." +msgid "If a product has :doc:`optional products <../products/cross_upselling>`, the **dialog box** will always appear." msgstr "" #: ../../content/applications/websites/ecommerce/checkout_payment_shipping/cart.rst:32 -#: ../../content/applications/websites/ecommerce/managing_products/products.rst:20 -msgid ":doc:`../managing_products/catalog`" +msgid ":doc:`../products/catalog`" msgstr "" #: ../../content/applications/websites/ecommerce/checkout_payment_shipping/cart.rst:37 @@ -546,7 +545,7 @@ msgid ":doc:`../checkout_payment_shipping/checkout`" msgstr "" #: ../../content/applications/websites/ecommerce/checkout_payment_shipping/payments.rst:14 -#: ../../content/applications/websites/ecommerce/managing_products/price_management.rst:94 +#: ../../content/applications/websites/ecommerce/products/price_management.rst:94 #: ../../content/applications/websites/website/configuration.rst:5 #: ../../content/applications/websites/website/configuration/cookies_bar.rst:15 #: ../../content/applications/websites/website/reporting/link_tracker.rst:10 @@ -659,7 +658,7 @@ msgid ":doc:`../../../inventory_and_mrp/inventory/shipping_receiving/setup_confi msgstr "" #: ../../content/applications/websites/ecommerce/checkout_payment_shipping/shipping.rst:57 -#: ../../content/applications/websites/ecommerce/managing_products/products.rst:203 +#: ../../content/applications/websites/ecommerce/products.rst:205 msgid "Website availability" msgstr "" @@ -1053,896 +1052,896 @@ msgstr "" msgid "It is possible to link your Odoo website with :ref:`analytics/plausible` and :ref:`analytics/google-analytics`." msgstr "" -#: ../../content/applications/websites/ecommerce/managing_products.rst:5 +#: ../../content/applications/websites/ecommerce/products.rst:5 #: ../../content/applications/websites/website/web_design/building_blocks/dynamic_content.rst:76 msgid "Products" msgstr "" -#: ../../content/applications/websites/ecommerce/managing_products/catalog.rst:3 -msgid "Catalog" -msgstr "" - -#: ../../content/applications/websites/ecommerce/managing_products/catalog.rst:5 -msgid "The eCommerce catalog is the equivalent of your physical store shelves: it allows customers to see what you have to offer. Clear categories, available options, sorting, and navigation threads help you structure it efficiently." -msgstr "" - -#: ../../content/applications/websites/ecommerce/managing_products/catalog.rst:10 -msgid "Categorize the product catalog" -msgstr "" - -#: ../../content/applications/websites/ecommerce/managing_products/catalog.rst:12 -msgid "In Odoo, there is a **specific category model** for your eCommerce. Using eCommerce categories for your products allows you to add a navigation menu on your eCommerce page. Visitors can then use it to view all products under the category they select." -msgstr "" - -#: ../../content/applications/websites/ecommerce/managing_products/catalog.rst:16 -msgid "To do so, go to :menuselection:`Website --> eCommerce --> Products`, select the product you wish to modify, click on the :guilabel:`Sales` tab, and select the :guilabel:`Categories` you want under :guilabel:`eCommerce Shop`." -msgstr "" - -#: ../../content/applications/websites/ecommerce/managing_products/catalog.rst:-1 -msgid "eCommerce categories under the \"Sales\" tab" -msgstr "" - -#: ../../content/applications/websites/ecommerce/managing_products/catalog.rst:25 -msgid "A single product can appear under multiple eCommerce categories." -msgstr "" - -#: ../../content/applications/websites/ecommerce/managing_products/catalog.rst:27 -msgid "When your product's categories are configured, go to your **main shop page** and click on :menuselection:`Edit --> Customize tab`. In the :guilabel:`Categories` option, you can either enable a menu on the :guilabel:`Left`, on the :guilabel:`Top`, or both. If you select the :guilabel:`Left` category, the option :guilabel:`Collapsable Category Recursive` appears and allows to render the :guilabel:`Left` category menu collapsable." -msgstr "" - -#: ../../content/applications/websites/ecommerce/managing_products/catalog.rst:-1 -msgid "Categories options for your eCommerce website" -msgstr "" - -#: ../../content/applications/websites/ecommerce/managing_products/catalog.rst:38 -msgid ":doc:`products`" -msgstr "" - -#: ../../content/applications/websites/ecommerce/managing_products/catalog.rst:43 -msgid "Browsing" -msgstr "" - -#: ../../content/applications/websites/ecommerce/managing_products/catalog.rst:45 -msgid "The eCommerce category is the first tool to organize and split your products. However, if you need an extra level of categorization in your catalog, you can activate various **filters** such as attributes or sort-by search." -msgstr "" - -#: ../../content/applications/websites/ecommerce/managing_products/catalog.rst:50 -msgid "Attributes" -msgstr "" - -#: ../../content/applications/websites/ecommerce/managing_products/catalog.rst:52 -msgid "Attributes refer to **characteristics** of a product, such as **color** or **material**, whereas variants are the different combinations of attributes. :guilabel:`Attributes and Variants` can be found under :menuselection:`Website --> eCommerce --> Products`, select your product, and :guilabel:`Attributes & Variants` tab." -msgstr "" - -#: ../../content/applications/websites/ecommerce/managing_products/catalog.rst:58 -#: ../../content/applications/websites/ecommerce/managing_products/variants.rst:15 -msgid ":doc:`../../../sales/sales/products_prices/products/variants`" -msgstr "" - -#: ../../content/applications/websites/ecommerce/managing_products/catalog.rst:-1 -msgid "Attributes and variants of your product" -msgstr "" - -#: ../../content/applications/websites/ecommerce/managing_products/catalog.rst:64 -msgid "To enable **attribute filtering**, go to your **main shop page**, click on :menuselection:`Edit --> Customize tab` and select either :guilabel:`Left`, :guilabel:`Top`, or both. Additionally, you can also enable :guilabel:`Price Filtering` to enable price filters." -msgstr "" - -#: ../../content/applications/websites/ecommerce/managing_products/catalog.rst:69 -msgid ":guilabel:`Price Filter` works independently from **attributes** and, therefore, can be enabled on its own if desired." -msgstr "" - -#: ../../content/applications/websites/ecommerce/managing_products/catalog.rst:73 -msgid "You can use **attribute filters** even if you do not work with product variants. When adding attributes to your products, make sure only to specify *one* value per attribute. Odoo does not create variants if no combination is possible." -msgstr "" - -#: ../../content/applications/websites/ecommerce/managing_products/catalog.rst:78 -msgid "Sort-by search" -msgstr "" - -#: ../../content/applications/websites/ecommerce/managing_products/catalog.rst:80 -msgid "It is possible to allow the user to manually **sort the catalog** using the search bar. From your **main shop page**, click on :menuselection:`Edit --> Customize tab`; you can enable or disable the :guilabel:`Sort-By` option as well as the :guilabel:`Layout` button. You can also select the :guilabel:`Default Sort` of the :guilabel:`Sort-By` button. The default sort applies to *all* categories." -msgstr "" - -#: ../../content/applications/websites/ecommerce/managing_products/catalog.rst:86 -msgid "The **sorting** options are:" -msgstr "" - -#: ../../content/applications/websites/ecommerce/managing_products/catalog.rst:88 -msgid "Featured" -msgstr "" - -#: ../../content/applications/websites/ecommerce/managing_products/catalog.rst:89 -msgid "Newest Arrivals" -msgstr "" - -#: ../../content/applications/websites/ecommerce/managing_products/catalog.rst:90 -msgid "Name (A-Z)" -msgstr "" - -#: ../../content/applications/websites/ecommerce/managing_products/catalog.rst:91 -msgid "Price - Low to High" -msgstr "" - -#: ../../content/applications/websites/ecommerce/managing_products/catalog.rst:92 -msgid "Price - High to Low" -msgstr "" - -#: ../../content/applications/websites/ecommerce/managing_products/catalog.rst:94 -msgid "In addition, you can **manually edit** the catalog's order of a product by going to **the main shop page** and clicking on the product. Under the :guilabel:`Product` section of the :guilabel:`Customize` section, you can rearrange the order by clicking on the arrows. `<<` `>>` move the product to the **extreme** right or left, and `<` `>` move the product by **one** row to the right or left. It is also possible to change the catalog's order of products in :menuselection:`Website --> eCommerce --> Products` and drag-and-dropping the products within the list." -msgstr "" - -#: ../../content/applications/websites/ecommerce/managing_products/catalog.rst:-1 -msgid "Product rearrangement in the catalog" -msgstr "" - -#: ../../content/applications/websites/ecommerce/managing_products/catalog.rst:107 -msgid "Page design" -msgstr "" - -#: ../../content/applications/websites/ecommerce/managing_products/catalog.rst:110 -msgid "Category page" -msgstr "" - -#: ../../content/applications/websites/ecommerce/managing_products/catalog.rst:112 -msgid "You can customize the layout of the category page using the website builder." -msgstr "" - -#: ../../content/applications/websites/ecommerce/managing_products/catalog.rst:115 -msgid "Editing the layout of the category page is global; editing one category layout affects *all* category pages." -msgstr "" - -#: ../../content/applications/websites/ecommerce/managing_products/catalog.rst:118 -msgid "To do so, go on to your :menuselection:`Category page --> Edit --> Customize`. Here, you can choose the layout, the number of columns to display the products, etc. The :guilabel:`Product Description` button makes the product description visible from the category page, underneath the product picture." -msgstr "" - -#: ../../content/applications/websites/ecommerce/managing_products/catalog.rst:-1 -msgid "Layout options of the category pages." -msgstr "" - -#: ../../content/applications/websites/ecommerce/managing_products/catalog.rst:127 -msgid "You can choose the size of the grid, but be aware that displaying too many products may affect performance and page loading speed." -msgstr "" - -#: ../../content/applications/websites/ecommerce/managing_products/catalog.rst:131 -msgid "Product highlight" -msgstr "" - -#: ../../content/applications/websites/ecommerce/managing_products/catalog.rst:133 -msgid "You can highlight products to make them more visible on the category or product page. On the page of your choice, go to :menuselection:`Edit --> Customize` and click on the product to highlight. In the :guilabel:`Product` section, you can choose the size of the product image by clicking on the grid, and you can also add a **ribbon** or :guilabel:`Badge`. This displays a banner across the product's image, such as:" -msgstr "" - -#: ../../content/applications/websites/ecommerce/managing_products/catalog.rst:139 -msgid "Sale;" -msgstr "" - -#: ../../content/applications/websites/ecommerce/managing_products/catalog.rst:140 -msgid "Sold out;" -msgstr "" - -#: ../../content/applications/websites/ecommerce/managing_products/catalog.rst:141 -msgid "Out of stock;" -msgstr "" - -#: ../../content/applications/websites/ecommerce/managing_products/catalog.rst:142 -msgid "New." -msgstr "" - -#: ../../content/applications/websites/ecommerce/managing_products/catalog.rst:144 -msgid "Alternatively, you can activate the :doc:`developer mode <../../../general/developer_mode>` on the **product's template**, and under the :guilabel:`Sales` tab, change or create the ribbon from the :guilabel:`Ribbon` field." -msgstr "" - -#: ../../content/applications/websites/ecommerce/managing_products/catalog.rst:149 -msgid "The :doc:`developer mode <../../../general/developer_mode>` is only intended for experienced users who wish to have access to advanced tools. Using the **developer mode** is *not* recommended for regular users." -msgstr "" - -#: ../../content/applications/websites/ecommerce/managing_products/catalog.rst:-1 -msgid "Ribbon highlight" -msgstr "" - -#: ../../content/applications/websites/ecommerce/managing_products/catalog.rst:158 -msgid "Additional features" -msgstr "" - -#: ../../content/applications/websites/ecommerce/managing_products/catalog.rst:160 -msgid "You can access and enable additional feature buttons such as **add to cart**, **comparison list**, or a **wishlist**. To do so, go to your **main shop page**, and at the end of the :guilabel:`Products Page` category, click on the feature buttons you wish to use. All three buttons appear when hovering the mouse over a product's image." -msgstr "" - -#: ../../content/applications/websites/ecommerce/managing_products/catalog.rst:165 -msgid ":guilabel:`Add to Cart`: adds a button to :doc:`add the product to the cart <../checkout_payment_shipping/cart>`;" -msgstr "" - -#: ../../content/applications/websites/ecommerce/managing_products/catalog.rst:167 -msgid ":guilabel:`Comparison List`: adds a button to **compare** products based on their price, variant, etc.;" -msgstr "" - -#: ../../content/applications/websites/ecommerce/managing_products/catalog.rst:169 -msgid ":guilabel:`Wishlist Button`: adds a button to **wishlist** the product." -msgstr "" - -#: ../../content/applications/websites/ecommerce/managing_products/catalog.rst:-1 -msgid "Feature buttons for add to cart, comparison list, and wishlist" -msgstr "" - -#: ../../content/applications/websites/ecommerce/managing_products/catalog.rst:-1 -msgid "Appearance of buttons when hoovering over the mouse" -msgstr "" - -#: ../../content/applications/websites/ecommerce/managing_products/catalog.rst:180 -#: ../../content/applications/websites/ecommerce/managing_products/products.rst:112 -msgid "Add content" -msgstr "" - -#: ../../content/applications/websites/ecommerce/managing_products/catalog.rst:182 -msgid "You can use **building blocks** to add content on the category page, with a variety of blocks ranging from :guilabel:`Structure` to :guilabel:`Dynamic Content`. Specific areas are defined to use blocks are defined and highlighted on the page when **dragging-and-dropping** a block." -msgstr "" - -#: ../../content/applications/websites/ecommerce/managing_products/catalog.rst:-1 -msgid "Building blocks areas" -msgstr "" - -#: ../../content/applications/websites/ecommerce/managing_products/catalog.rst:190 -msgid "If you drop a building block **on top** of the product list, it creates a new category header specific to *that* category." -msgstr "" - -#: ../../content/applications/websites/ecommerce/managing_products/catalog.rst:192 -msgid "If you drop a building **on the top** or **bottom** of the page, it becomes visible on *all* category pages." -msgstr "" - -#: ../../content/applications/websites/ecommerce/managing_products/catalog.rst:196 -msgid "Adding content to an eCommerce category page is beneficial in terms of **SEO** strategy. Using **keywords** linked to the products or the eCommerce categories improves organic traffic. Additionally, each category has its own specific URL that can be pointed to and is indexed by search engines." -msgstr "" - -#: ../../content/applications/websites/ecommerce/managing_products/cross_upselling.rst:3 -msgid "Cross-selling and upselling" -msgstr "" - -#: ../../content/applications/websites/ecommerce/managing_products/cross_upselling.rst:5 -msgid "Any sales process is an opportunity to maximize revenues. **Cross-selling and upselling** are sales techniques consisting in selling customers additional or more expensive products and services than what they were originally shopping for. It is a great way to maximize the value of each one of your customers." -msgstr "" - -#: ../../content/applications/websites/ecommerce/managing_products/cross_upselling.rst:10 -msgid "**Cross-selling** can be done via **two** features:" -msgstr "" - -#: ../../content/applications/websites/ecommerce/managing_products/cross_upselling.rst:12 -msgid ":ref:`Optional products ` upon **adding to cart**;" -msgstr "" - -#: ../../content/applications/websites/ecommerce/managing_products/cross_upselling.rst:13 -msgid ":ref:`Accessory products ` on the **checkout page**." -msgstr "" - -#: ../../content/applications/websites/ecommerce/managing_products/cross_upselling.rst:15 -msgid "**Upselling** is only done via :ref:`alternative products ` on the **product page**." -msgstr "" - -#: ../../content/applications/websites/ecommerce/managing_products/cross_upselling.rst:19 -msgid ":doc:`catalog`" -msgstr "" - -#: ../../content/applications/websites/ecommerce/managing_products/cross_upselling.rst:22 -msgid "Cross-selling" -msgstr "" - -#: ../../content/applications/websites/ecommerce/managing_products/cross_upselling.rst:27 -msgid "Optional products" -msgstr "" - -#: ../../content/applications/websites/ecommerce/managing_products/cross_upselling.rst:29 -msgid "**Optional products** are suggested when customers click :guilabel:`Add to cart`, either from the **product page** or **catalog page**. Upon clicking, a pop-up window opens with the **optional products** displayed in the :guilabel:`Available Options` section." -msgstr "" - -#: ../../content/applications/websites/ecommerce/managing_products/cross_upselling.rst:-1 -msgid "Optional products cross-selling" -msgstr "" - -#: ../../content/applications/websites/ecommerce/managing_products/cross_upselling.rst:37 -msgid "To enable **optional products** go to :menuselection:`Website --> eCommerce --> Products`, select a product, go to the :guilabel:`Sales` tab, and enter the products you wish to feature in the :guilabel:`Optional Products` field. Optional products are **linked** to the product(s) they are set up with on the **product template**. They only appear when that product is added to the cart." -msgstr "" - -#: ../../content/applications/websites/ecommerce/managing_products/cross_upselling.rst:43 -msgid "You can also access the :guilabel:`Sales` tab of the **product template** by selecting a product on your **main shop page** and clicking :guilabel:`Product` in the top-right corner." -msgstr "" - -#: ../../content/applications/websites/ecommerce/managing_products/cross_upselling.rst:49 -msgid "Accessory products" -msgstr "" - -#: ../../content/applications/websites/ecommerce/managing_products/cross_upselling.rst:51 -msgid "**Accessory products** are displayed in the :guilabel:`Suggested Accessories` section before processing to checkout at the :guilabel:`Review Order` step." -msgstr "" - -#: ../../content/applications/websites/ecommerce/managing_products/cross_upselling.rst:-1 -msgid "Suggested accessories at checkout during cart review" -msgstr "" - -#: ../../content/applications/websites/ecommerce/managing_products/cross_upselling.rst:58 -msgid "To enable **accessory products**, go to :menuselection:`Website --> eCommerce --> Products`, select a product, go to the :guilabel:`Sales` tab, and enter the products you wish to feature in the :guilabel:`Accessory Products` field. Suggested accessory products are **linked** to the product(s) they are set up with on the **product template**. They only appear when that product is at the checkout process review." -msgstr "" - -#: ../../content/applications/websites/ecommerce/managing_products/cross_upselling.rst:65 -msgid "Upselling" -msgstr "" - -#: ../../content/applications/websites/ecommerce/managing_products/cross_upselling.rst:70 -msgid "Alternative products" -msgstr "" - -#: ../../content/applications/websites/ecommerce/managing_products/cross_upselling.rst:72 -msgid "**Alternative products** are suggested on the **product page** and usually incentivize customers to buy a more expensive variant or product than the one they were initially shopping for." -msgstr "" - -#: ../../content/applications/websites/ecommerce/managing_products/cross_upselling.rst:-1 -msgid "Alternative products on the product page" -msgstr "" - -#: ../../content/applications/websites/ecommerce/managing_products/cross_upselling.rst:79 -msgid "To enable **alternative products**, go to :menuselection:`Website --> eCommerce --> Products`, select a product, go to the :guilabel:`Sales` tab, and enter the products you wish to feature in the :guilabel:`Alternative Products` field. Then, go to the related **product page** by clicking :guilabel:`Go To Website`, and click :menuselection:`Edit`. Stay on the :guilabel:`Blocks` tab, and scroll down to the :guilabel:`Dynamic Content` section. Then, drag and drop the :guilabel:`Products` building block anywhere on the **product page**." -msgstr "" - -#: ../../content/applications/websites/ecommerce/managing_products/cross_upselling.rst:86 -msgid "When placed, in :guilabel:`Edit` mode, click the **block** to access various settings for that :guilabel:`Products` building block. In the :guilabel:`Filter` field, select :guilabel:`Alternative Products`. You can configure several additional settings, such as how many elements are displayed (:guilabel:`Fetched Elements`), the :guilabel:`Template` used, etc." -msgstr "" - -#: ../../content/applications/websites/ecommerce/managing_products/price_management.rst:3 -msgid "Price management" -msgstr "" - -#: ../../content/applications/websites/ecommerce/managing_products/price_management.rst:5 -msgid "Odoo offers multiple options to select the price displayed on your website, as well as condition-specific prices based on set criteria." -msgstr "" - -#: ../../content/applications/websites/ecommerce/managing_products/price_management.rst:9 -msgid "Taxes" -msgstr "" - -#: ../../content/applications/websites/ecommerce/managing_products/price_management.rst:12 -msgid "Tax configuration" -msgstr "" - -#: ../../content/applications/websites/ecommerce/managing_products/price_management.rst:14 -msgid "To add a tax on a product, you can either set a tax in the :guilabel:`Customer Taxes` field of the **product template** or use :doc:`fiscal positions `." -msgstr "" - -#: ../../content/applications/websites/ecommerce/managing_products/price_management.rst:19 -msgid ":doc:`/applications/finance/accounting/taxes`" -msgstr "" - -#: ../../content/applications/websites/ecommerce/managing_products/price_management.rst:20 -msgid ":doc:`/applications/finance/accounting/taxes/avatax`" -msgstr "" - -#: ../../content/applications/websites/ecommerce/managing_products/price_management.rst:21 -msgid ":doc:`/applications/finance/accounting/taxes/fiscal_positions`" -msgstr "" - -#: ../../content/applications/websites/ecommerce/managing_products/price_management.rst:24 -msgid "Tax display" -msgstr "" - -#: ../../content/applications/websites/ecommerce/managing_products/price_management.rst:26 -msgid "Choosing the displayed price tax usually depends on a country's regulations or the type of customers **(B2B vs. B2C)**. To select the type of price displayed, go to :menuselection:`Website --> Configuration --> Settings`, scroll down to the :guilabel:`Shop - Products` category, and select :guilabel:`Tax Excluded` or :guilabel:`Tax Included`." -msgstr "" - -#: ../../content/applications/websites/ecommerce/managing_products/price_management.rst:31 -msgid ":guilabel:`Tax Excluded`: the price displayed on the website is **tax-excluded**, and the tax is computed at the cart-review step;" -msgstr "" - -#: ../../content/applications/websites/ecommerce/managing_products/price_management.rst:33 -msgid ":guilabel:`Tax Included`: the price displayed on the website is **tax-included**." -msgstr "" - -#: ../../content/applications/websites/ecommerce/managing_products/price_management.rst:36 -msgid "This setting is **global**, and the tax-display type is the same for (all of) your website(s). It is, therefore, not possible to select different tax displays for different websites. This may be a significant point of consideration when implementing a database with multiple ecommerce websites aimed at varying customer types (i.e., B2B and B2C)." -msgstr "" - -#: ../../content/applications/websites/ecommerce/managing_products/price_management.rst:41 -msgid "You can choose to display the type of pricing next to the product price by going to :menuselection:`Website --> Site --> Homepage --> Shop`, selecting a product, and then :menuselection:`Edit --> Customize tab` and enabling :guilabel:`Tax Indication`." -msgstr "" - -#: ../../content/applications/websites/ecommerce/managing_products/price_management.rst:-1 -msgid "Tax type displayed on the product page" -msgstr "" - -#: ../../content/applications/websites/ecommerce/managing_products/price_management.rst:50 -msgid ":doc:`/applications/finance/accounting/taxes/B2B_B2C`" -msgstr "" - -#: ../../content/applications/websites/ecommerce/managing_products/price_management.rst:53 -msgid "Price per unit" -msgstr "" - -#: ../../content/applications/websites/ecommerce/managing_products/price_management.rst:55 -msgid "It is possible to display a :doc:`price per unit ` on the product page. To do that, go to :menuselection:`Website --> Configuration --> Settings` and enable :guilabel:`Product Reference Price` under the :guilabel:`Shop - Products` section. When enabled, ensure an amount is set in the :guilabel:`Base Unit Count` field of the **product template**, and in the :guilabel:`Sales Price`." -msgstr "" - -#: ../../content/applications/websites/ecommerce/managing_products/price_management.rst:-1 -msgid "Cost per unit pricing on the product template" -msgstr "" - -#: ../../content/applications/websites/ecommerce/managing_products/price_management.rst:66 -msgid "The price per unit of measure can be found above the :guilabel:`Add to Cart` button on the product page." -msgstr "" - -#: ../../content/applications/websites/ecommerce/managing_products/price_management.rst:-1 -msgid "Cost per unit pricing on the product page" -msgstr "" - -#: ../../content/applications/websites/ecommerce/managing_products/price_management.rst:74 -msgid "Pay attention that having the price per unit may be **mandatory** in some countries." -msgstr "" - -#: ../../content/applications/websites/ecommerce/managing_products/price_management.rst:77 -msgid ":doc:`/applications/inventory_and_mrp/inventory/product_management/product_replenishment/uom`" -msgstr "" - -#: ../../content/applications/websites/ecommerce/managing_products/price_management.rst:82 -msgid "Price configuration: pricelists" -msgstr "" - -#: ../../content/applications/websites/ecommerce/managing_products/price_management.rst:84 -msgid "Pricelists are the primary tool to manage prices on your eCommerce. They allow you to define website-specific prices - different from the price on the product template - based on the **country group**, **currency**, **minimum quantity**, **period**, or **variant**. You can create as many pricelists as needed, but it is mandatory to have at least one pricelist configured per website. If no custom pricelists are added, Odoo defaults to the **Public Pricelist** for all websites." -msgstr "" - -#: ../../content/applications/websites/ecommerce/managing_products/price_management.rst:91 -#: ../../content/applications/websites/ecommerce/managing_products/price_management.rst:119 -msgid ":doc:`/applications/sales/sales/products_prices/prices/pricing`" -msgstr "" - -#: ../../content/applications/websites/ecommerce/managing_products/price_management.rst:96 -msgid "Pricelists can be found under :menuselection:`Website --> eCommerce --> Pricelists`, but must first be activated. For that, head to :menuselection:`Website --> Configuration --> Settings` and scroll down to the :guilabel:`Shop - Products` section. There, you can find two options:" -msgstr "" - -#: ../../content/applications/websites/ecommerce/managing_products/price_management.rst:100 -msgid ":guilabel:`Multiple prices per product`;" -msgstr "" - -#: ../../content/applications/websites/ecommerce/managing_products/price_management.rst:101 -msgid ":guilabel:`Advanced price rules (discounts, formulas)`." -msgstr "" - -#: ../../content/applications/websites/ecommerce/managing_products/price_management.rst:103 -msgid "The **first** option allows you to set different prices per customer *segment*, i.e., registered customers, gold customers, regular customers, etc. The **second** option allows you to set *price change* rules such as **discounts**, **margins**, **roundings**, etc." -msgstr "" - -#: ../../content/applications/websites/ecommerce/managing_products/price_management.rst:108 -msgid "Foreign currency" -msgstr "" - -#: ../../content/applications/websites/ecommerce/managing_products/price_management.rst:110 -msgid "If you are selling in **multiple currencies** and have pricelists in foreign currencies, customers can select their corresponding pricelist anywhere on the :guilabel:`Shop` page from the drop-down menu next to the **search bar**." -msgstr "" - -#: ../../content/applications/websites/ecommerce/managing_products/price_management.rst:-1 -msgid "Pricelists selection" -msgstr "" - -#: ../../content/applications/websites/ecommerce/managing_products/price_management.rst:120 -msgid ":doc:`/applications/sales/sales/products_prices/prices/currencies`" -msgstr "" - -#: ../../content/applications/websites/ecommerce/managing_products/price_management.rst:123 -msgid "Permanent discount" -msgstr "" - -#: ../../content/applications/websites/ecommerce/managing_products/price_management.rst:125 -msgid "If you have permanently reduced the price of a product, a popular means to attract customers is the **strikethrough** strategy. The strategy consists in displaying the previous price crossed out and the **new discounted price** next to it." -msgstr "" - -#: ../../content/applications/websites/ecommerce/managing_products/price_management.rst:-1 -msgid "Price strikethrough" -msgstr "" - -#: ../../content/applications/websites/ecommerce/managing_products/price_management.rst:133 -msgid "To display a 'striked' price, enable the :guilabel:`Comparison Price` option under :menuselection:`Website --> Configuration --> Settings --> Shop - Products category`. Then, head to the product's template (:menuselection:`Website --> eCommerce --> Products`), and in the :guilabel:`Compare to Price` field, enter the **new** price." -msgstr "" - -#: ../../content/applications/websites/ecommerce/managing_products/products.rst:3 -msgid "Product management" -msgstr "" - -#: ../../content/applications/websites/ecommerce/managing_products/products.rst:5 +#: ../../content/applications/websites/ecommerce/products.rst:7 msgid "Odoo allows you to create, import, and manage your products' pages all within the **Website** app." msgstr "" -#: ../../content/applications/websites/ecommerce/managing_products/products.rst:8 +#: ../../content/applications/websites/ecommerce/products.rst:10 msgid "Add products to the catalog" msgstr "" -#: ../../content/applications/websites/ecommerce/managing_products/products.rst:10 +#: ../../content/applications/websites/ecommerce/products.rst:12 msgid "To add a product to your catalog, you can either do it in:" msgstr "" -#: ../../content/applications/websites/ecommerce/managing_products/products.rst:12 +#: ../../content/applications/websites/ecommerce/products.rst:14 msgid "From anywhere on your website, click :menuselection:`+ New --> Product`. Enter the name of your product, and :guilabel:`Save`;" msgstr "" -#: ../../content/applications/websites/ecommerce/managing_products/products.rst:14 +#: ../../content/applications/websites/ecommerce/products.rst:16 msgid ":menuselection:`Website --> eCommerce --> Products --> Create`;" msgstr "" -#: ../../content/applications/websites/ecommerce/managing_products/products.rst:15 +#: ../../content/applications/websites/ecommerce/products.rst:17 msgid "or by :ref:`importing data ` using XLSX or CSV files. To do so, go to :menuselection:`Website --> eCommerce --> Products`. Click on :guilabel:`Favorites` and :ref:`Import records `." msgstr "" -#: ../../content/applications/websites/ecommerce/managing_products/products.rst:21 -#: ../../content/applications/websites/ecommerce/managing_products/variants.rst:16 -msgid ":doc:`../../../sales/sales/products_prices/products/import`" +#: ../../content/applications/websites/ecommerce/products.rst:22 +msgid ":doc:`products/catalog`" msgstr "" -#: ../../content/applications/websites/ecommerce/managing_products/products.rst:22 -msgid ":doc:`Product-related documentation <../../../sales/sales>`" +#: ../../content/applications/websites/ecommerce/products.rst:23 +msgid ":doc:`../../sales/sales/products_prices/products/import`" msgstr "" -#: ../../content/applications/websites/ecommerce/managing_products/products.rst:25 +#: ../../content/applications/websites/ecommerce/products.rst:24 +msgid ":doc:`Product-related documentation <../../sales/sales>`" +msgstr "" + +#: ../../content/applications/websites/ecommerce/products.rst:27 msgid "Publish" msgstr "" -#: ../../content/applications/websites/ecommerce/managing_products/products.rst:27 +#: ../../content/applications/websites/ecommerce/products.rst:29 msgid "Upon creation, products are defaulted as :guilabel:`Unpublished` in your eCommerce catalog. To make a product visible to visitors, go to :menuselection:`Website --> Site --> Homepage`, click on your **main shop** page, select the product, and enable it as :guilabel:`Published` in the top-right corner." msgstr "" -#: ../../content/applications/websites/ecommerce/managing_products/products.rst:33 +#: ../../content/applications/websites/ecommerce/products.rst:35 msgid "To publish **large batches** of products, the most convenient fashion is to go to :menuselection:`Website --> eCommerce --> Products`. Here, remove the :guilabel:`Published` filter by clicking on the :guilabel:`x` right to it, and then select the :guilabel:`List` view. Next, click the :guilabel:`dropdown toggle` button (located right below the :guilabel:`List` button) and enable :guilabel:`Is published`. Click the :guilabel:`Is Published` column to re-order it either by **published** or **unpublished** products. Finally, select the products to publish by ticking their box on the extreme-right, and tick any box of the selected products in the :guilabel:`Is Published` column to publish them all." msgstr "" -#: ../../content/applications/websites/ecommerce/managing_products/products.rst:-1 +#: ../../content/applications/websites/ecommerce/products.rst:-1 msgid "List and dropdown toggle buttons" msgstr "" -#: ../../content/applications/websites/ecommerce/managing_products/products.rst:47 +#: ../../content/applications/websites/ecommerce/products.rst:49 msgid "Product page design" msgstr "" -#: ../../content/applications/websites/ecommerce/managing_products/products.rst:49 +#: ../../content/applications/websites/ecommerce/products.rst:51 msgid "Once a product is created, you can access its **product page** through the :guilabel:`Shop` page by clicking on the product, and then clicking :guilabel:`Edit`. Here, you can change the page's **additional functions**, **layout**, **add content**, etc. Note that **enabled functions** apply to *all* product pages." msgstr "" -#: ../../content/applications/websites/ecommerce/managing_products/products.rst:57 +#: ../../content/applications/websites/ecommerce/products.rst:59 msgid "Additional functions" msgstr "" -#: ../../content/applications/websites/ecommerce/managing_products/products.rst:59 +#: ../../content/applications/websites/ecommerce/products.rst:61 msgid "In the **website builder** window, click :guilabel:`Customize` to enable additional functions:" msgstr "" -#: ../../content/applications/websites/ecommerce/managing_products/products.rst:61 +#: ../../content/applications/websites/ecommerce/products.rst:63 msgid ":guilabel:`Customers: Rating` allows customers to submit :ref:`product reviews `; :guilabel:`Share` adds social media and email icon buttons to share the product via those channels;" msgstr "" -#: ../../content/applications/websites/ecommerce/managing_products/products.rst:64 +#: ../../content/applications/websites/ecommerce/products.rst:66 msgid ":guilabel:`Select Quantity`: if enabled, allows to choose the quantity added to cart;" msgstr "" -#: ../../content/applications/websites/ecommerce/managing_products/products.rst:65 +#: ../../content/applications/websites/ecommerce/products.rst:67 msgid ":guilabel:`Tax Indication`: notifies if the price is **VAT included** or **excluded**;" msgstr "" -#: ../../content/applications/websites/ecommerce/managing_products/products.rst:66 +#: ../../content/applications/websites/ecommerce/products.rst:68 msgid ":guilabel:`Variants`: shows all possible :doc:`variants ` of the product as a :guilabel:`Products List`; :guilabel:`Options` as selectable options to compose the variant yourself;" msgstr "" -#: ../../content/applications/websites/ecommerce/managing_products/products.rst:70 +#: ../../content/applications/websites/ecommerce/products.rst:72 msgid ":guilabel:`Cart`: :guilabel:`Buy Now` adds a :ref:`checkout button ` taking the customer directly to the checkout page; :guilabel:`Wishlist` allows to add the product to a wishlist;" msgstr "" -#: ../../content/applications/websites/ecommerce/managing_products/products.rst:73 +#: ../../content/applications/websites/ecommerce/products.rst:75 msgid ":guilabel:`Specification`: allows you to select where the :guilabel:`Specifications` section is displayed. This option displays a list of all variant attributes and values of a product, but only works for products *with* variants." msgstr "" -#: ../../content/applications/websites/ecommerce/managing_products/products.rst:78 +#: ../../content/applications/websites/ecommerce/products.rst:80 msgid "To allow **wishlists**, the option must be enabled in :menuselection:`Website --> Configuration --> Settings --> Shop - Products`;" msgstr "" -#: ../../content/applications/websites/ecommerce/managing_products/products.rst:80 -msgid "To access the :guilabel:`Variants` options, the :doc:`Product Variants <../../../sales/sales/products_prices/products/variants>` option must first be enabled under :menuselection:`Website --> Configuration --> Settings --> Shop - Products`." +#: ../../content/applications/websites/ecommerce/products.rst:82 +msgid "To access the :guilabel:`Variants` options, the :doc:`Product Variants <../../sales/sales/products_prices/products/variants>` option must first be enabled under :menuselection:`Website --> Configuration --> Settings --> Shop - Products`." msgstr "" -#: ../../content/applications/websites/ecommerce/managing_products/products.rst:85 +#: ../../content/applications/websites/ecommerce/products.rst:87 msgid "Layout" msgstr "" -#: ../../content/applications/websites/ecommerce/managing_products/products.rst:87 +#: ../../content/applications/websites/ecommerce/products.rst:89 msgid "Within the same :guilabel:`Customize` tab as the :ref:`functions `, the layout configuration can be changed according to your needs." msgstr "" -#: ../../content/applications/websites/ecommerce/managing_products/products.rst:90 +#: ../../content/applications/websites/ecommerce/products.rst:92 msgid ":guilabel:`Images Width`: changes the width of the product images displayed on the page;" msgstr "" -#: ../../content/applications/websites/ecommerce/managing_products/products.rst:91 +#: ../../content/applications/websites/ecommerce/products.rst:93 msgid ":guilabel:`Layout`: the :guilabel:`Carousel` layout displays a large, main image with smaller ones underneath; whereas the :guilabel:`Grid` displays four images in a square layout (see pictures below);" msgstr "" -#: ../../content/applications/websites/ecommerce/managing_products/products.rst:94 +#: ../../content/applications/websites/ecommerce/products.rst:96 msgid ":guilabel:`Image Zoom`: choose which image zooms are available, either :guilabel:`Pop-up on Click`, when hovering over the image (:guilabel:`Magnifier on hover`), on :guilabel:`Both`, or :guilabel:`None`;" msgstr "" -#: ../../content/applications/websites/ecommerce/managing_products/products.rst:97 +#: ../../content/applications/websites/ecommerce/products.rst:99 msgid ":guilabel:`Thumbnails`: decide how the thumbnails should be aligned, either **vertically** (:guilabel:`Left`), or **horizontally** (:guilabel:`Right`);" msgstr "" -#: ../../content/applications/websites/ecommerce/managing_products/products.rst:99 +#: ../../content/applications/websites/ecommerce/products.rst:101 msgid ":guilabel:`Main Image`: click :guilabel:`Replace` to change the product's main image;" msgstr "" -#: ../../content/applications/websites/ecommerce/managing_products/products.rst:100 +#: ../../content/applications/websites/ecommerce/products.rst:102 msgid ":guilabel:`Extra Images`: click :guilabel:`Add` or :guilabel:`Remove all` to add or remove extra product images. You can also add images and videos via **URL**." msgstr "" -#: ../../content/applications/websites/ecommerce/managing_products/products.rst:104 +#: ../../content/applications/websites/ecommerce/products.rst:106 msgid "Images must either be in PNG or JPG format. To trigger the zoom, the image has to be bigger than 1024x1024." msgstr "" -#: ../../content/applications/websites/ecommerce/managing_products/products.rst:-1 +#: ../../content/applications/websites/ecommerce/products.rst:-1 msgid "Product images layout" msgstr "" -#: ../../content/applications/websites/ecommerce/managing_products/products.rst:114 +#: ../../content/applications/websites/ecommerce/products.rst:114 +#: ../../content/applications/websites/ecommerce/products/catalog.rst:180 +msgid "Add content" +msgstr "" + +#: ../../content/applications/websites/ecommerce/products.rst:116 msgid "You can use **building blocks** (:menuselection:`Edit --> Blocks`) to add content to your product page. These blocks can be used to add extra text and picture galleries, features such as :guilabel:`Call to Actions`, :guilabel:`Comparisons`, etc." msgstr "" -#: ../../content/applications/websites/ecommerce/managing_products/products.rst:118 +#: ../../content/applications/websites/ecommerce/products.rst:120 msgid "Depending on *where* you drop the **building block**, it may be available either on the product page *only*, or on the *whole* website. **Building blocks** dropped at the very top or very bottom of the page are available on the *whole* website, where **building blocks** put underneath the product description are only displayed on the *product* page *(see image below)*." msgstr "" -#: ../../content/applications/websites/ecommerce/managing_products/products.rst:-1 +#: ../../content/applications/websites/ecommerce/products.rst:-1 msgid "Building blocks on product page" msgstr "" -#: ../../content/applications/websites/ecommerce/managing_products/products.rst:128 +#: ../../content/applications/websites/ecommerce/products.rst:130 msgid "Download link" msgstr "" -#: ../../content/applications/websites/ecommerce/managing_products/products.rst:130 +#: ../../content/applications/websites/ecommerce/products.rst:132 msgid "To add a downloadable file (ex.: user's manual, notice of use, etc.) on the product page, drag and drop a :guilabel:`Text` block from :menuselection:`Edit --> Blocks` on the page. Once placed, click within the :guilabel:`Text` block, and under the :guilabel:`Inline Text` section, select either :menuselection:`Insert Media --> Documents` or :guilabel:`Insert or edit link` and enter the URL in the :guilabel:`Your URL` field." msgstr "" -#: ../../content/applications/websites/ecommerce/managing_products/products.rst:137 +#: ../../content/applications/websites/ecommerce/products.rst:139 msgid "The difference with :ref:`digital files ` is that digital files can only be downloaded *after* checkout." msgstr "" -#: ../../content/applications/websites/ecommerce/managing_products/products.rst:-1 +#: ../../content/applications/websites/ecommerce/products.rst:-1 msgid "Media and link buttons" msgstr "" -#: ../../content/applications/websites/ecommerce/managing_products/products.rst:147 +#: ../../content/applications/websites/ecommerce/products.rst:149 msgid "Digital files" msgstr "" -#: ../../content/applications/websites/ecommerce/managing_products/products.rst:149 +#: ../../content/applications/websites/ecommerce/products.rst:151 msgid "Should your product be sold with a certificate, manual user, or any other relevant document, it is possible to add a download link for customers at the end of the checkout. To do that, first enable :guilabel:`Digital Content` under :menuselection:`Website --> Configuration --> Settings --> Shop - Checkout Process`. Then, on the **product's template**, click on :menuselection:`More --> Digital Files` and :guilabel:`Create` a new file." msgstr "" -#: ../../content/applications/websites/ecommerce/managing_products/products.rst:-1 +#: ../../content/applications/websites/ecommerce/products.rst:-1 msgid "Digital Files menu" msgstr "" -#: ../../content/applications/websites/ecommerce/managing_products/products.rst:159 +#: ../../content/applications/websites/ecommerce/products.rst:161 msgid "For the configuration:" msgstr "" -#: ../../content/applications/websites/ecommerce/managing_products/products.rst:161 +#: ../../content/applications/websites/ecommerce/products.rst:163 msgid ":guilabel:`Name`: the name of your file;" msgstr "" -#: ../../content/applications/websites/ecommerce/managing_products/products.rst:162 +#: ../../content/applications/websites/ecommerce/products.rst:164 msgid ":guilabel:`Type:` select if it is either a **file** or a **URL**. Accordingly, you either have a :guilabel:`File Content (base64)` field to upload your file, or a :guilabel:`URL` field to enter your URL." msgstr "" -#: ../../content/applications/websites/ecommerce/managing_products/products.rst:165 +#: ../../content/applications/websites/ecommerce/products.rst:167 msgid ":guilabel:`Website`: the website on which that file is *available*. If you want it available for *all* websites, leave it empty." msgstr "" -#: ../../content/applications/websites/ecommerce/managing_products/products.rst:168 +#: ../../content/applications/websites/ecommerce/products.rst:170 msgid "The file is then available after checkout in the :guilabel:`Sales Orders` section, found on the customer's portal." msgstr "" -#: ../../content/applications/websites/ecommerce/managing_products/products.rst:172 +#: ../../content/applications/websites/ecommerce/products.rst:174 msgid "Product configuration" msgstr "" -#: ../../content/applications/websites/ecommerce/managing_products/products.rst:175 +#: ../../content/applications/websites/ecommerce/products.rst:177 msgid "Multiple languages" msgstr "" -#: ../../content/applications/websites/ecommerce/managing_products/products.rst:177 +#: ../../content/applications/websites/ecommerce/products.rst:179 msgid "If multiple languages are available on your website and you wish to have the product's information translated, it is necessary to encode this translated information in the **product's template**. Fields with multiple languages available are identifiable by their abbreviation language (ex. :abbr:`EN (English)`) next to their field." msgstr "" -#: ../../content/applications/websites/ecommerce/managing_products/products.rst:-1 +#: ../../content/applications/websites/ecommerce/products.rst:-1 msgid "Field translation" msgstr "" -#: ../../content/applications/websites/ecommerce/managing_products/products.rst:186 +#: ../../content/applications/websites/ecommerce/products.rst:188 msgid "The **eCommerce-related** fields to translate are:" msgstr "" -#: ../../content/applications/websites/ecommerce/managing_products/products.rst:188 +#: ../../content/applications/websites/ecommerce/products.rst:190 msgid ":guilabel:`Product name`;" msgstr "" -#: ../../content/applications/websites/ecommerce/managing_products/products.rst:189 +#: ../../content/applications/websites/ecommerce/products.rst:191 msgid ":guilabel:`Out-of-Stock Message` (under the :guilabel:`Sales` tab);" msgstr "" -#: ../../content/applications/websites/ecommerce/managing_products/products.rst:190 +#: ../../content/applications/websites/ecommerce/products.rst:192 msgid ":guilabel:`Sales Description` (under the :guilabel:`Sales` tab);" msgstr "" -#: ../../content/applications/websites/ecommerce/managing_products/products.rst:193 -msgid "Having untranslated content on a web page may be detrimental to the user experience and :doc:`SEO <../../../websites/website/pages/seo>`." +#: ../../content/applications/websites/ecommerce/products.rst:195 +msgid "Having untranslated content on a web page may be detrimental to the user experience and :doc:`SEO <../../websites/website/pages/seo>`." msgstr "" -#: ../../content/applications/websites/ecommerce/managing_products/products.rst:196 +#: ../../content/applications/websites/ecommerce/products.rst:198 msgid "To check the language(s) of your website, go to :menuselection:`Website --> Configuration --> Settings --> Website Info section`." msgstr "" -#: ../../content/applications/websites/ecommerce/managing_products/products.rst:200 -msgid ":doc:`../../../websites/website/pages/seo`" +#: ../../content/applications/websites/ecommerce/products.rst:202 +msgid ":doc:`../../websites/website/pages/seo`" msgstr "" -#: ../../content/applications/websites/ecommerce/managing_products/products.rst:205 +#: ../../content/applications/websites/ecommerce/products.rst:207 msgid "A product can be set available on either *one* or *all* websites, but it is not possible to select *some* websites and not others. To define a product's availability, go to :menuselection:`Website --> eCommerce --> Products`, select your product, and in the :guilabel:`Sales` tab, click the :guilabel:`Website` you wish the product to be available on. Leave the field empty for the products to be available on *all* websites." msgstr "" -#: ../../content/applications/websites/ecommerce/managing_products/products.rst:212 +#: ../../content/applications/websites/ecommerce/products.rst:214 msgid "Stock management" msgstr "" -#: ../../content/applications/websites/ecommerce/managing_products/products.rst:214 +#: ../../content/applications/websites/ecommerce/products.rst:216 msgid "Under the :menuselection:`Website --> Configuration --> Settings --> Shop - Products`, you can enable and configure inventory management options." msgstr "" -#: ../../content/applications/websites/ecommerce/managing_products/products.rst:218 +#: ../../content/applications/websites/ecommerce/products.rst:220 msgid "To display the stock level on the product page, the :guilabel:`Product Type` on the **product's form** must be set to :guilabel:`Storable` (only available when the **Inventory** app is installed)." msgstr "" -#: ../../content/applications/websites/ecommerce/managing_products/products.rst:223 +#: ../../content/applications/websites/ecommerce/products.rst:225 msgid "Inventory" msgstr "" -#: ../../content/applications/websites/ecommerce/managing_products/products.rst:225 +#: ../../content/applications/websites/ecommerce/products.rst:227 msgid "In the :guilabel:`Inventory Defaults` sub-section, you can select the eCommerce selling strategy of products:" msgstr "" -#: ../../content/applications/websites/ecommerce/managing_products/products.rst:228 +#: ../../content/applications/websites/ecommerce/products.rst:230 msgid ":guilabel:`Warehouse`: if you have multiple warehouses, you can define the warehouse associated to your website. If you have multiple websites, you can select a different one per website;" msgstr "" -#: ../../content/applications/websites/ecommerce/managing_products/products.rst:230 +#: ../../content/applications/websites/ecommerce/products.rst:232 msgid ":guilabel:`Out-of-Stock (Continue Selling)`: enabling it allows customers to continue placing orders even when the product is **out-of-stock**. Leave it unchecked to **prevent orders**;" msgstr "" -#: ../../content/applications/websites/ecommerce/managing_products/products.rst:233 +#: ../../content/applications/websites/ecommerce/products.rst:235 msgid ":guilabel:`Show Available Qty`: enabling it displays the available quantity left under a specified threshold on the product page. The available quantity is calculated based on the 'On hand' quantity minus the quantity already reserved for outgoing transfers." msgstr "" -#: ../../content/applications/websites/ecommerce/managing_products/products.rst:238 +#: ../../content/applications/websites/ecommerce/products.rst:240 msgid ":ref:`Allow only selected customers to buy `" msgstr "" -#: ../../content/applications/websites/ecommerce/managing_products/products.rst:241 +#: ../../content/applications/websites/ecommerce/products.rst:243 msgid "Selling as kit" msgstr "" -#: ../../content/applications/websites/ecommerce/managing_products/products.rst:243 +#: ../../content/applications/websites/ecommerce/products.rst:245 msgid "If you are selling non-prepackaged kits (i.e., the kits are made of individual products), we recommend you read the related documentation to keep track of your stock." msgstr "" -#: ../../content/applications/websites/ecommerce/managing_products/products.rst:247 -msgid ":doc:`../../../inventory_and_mrp/manufacturing/advanced_configuration/kit_shipping`" +#: ../../content/applications/websites/ecommerce/products.rst:249 +msgid ":doc:`../../inventory_and_mrp/manufacturing/advanced_configuration/kit_shipping`" msgstr "" -#: ../../content/applications/websites/ecommerce/managing_products/products.rst:250 +#: ../../content/applications/websites/ecommerce/products.rst:252 msgid "Product comparison" msgstr "" -#: ../../content/applications/websites/ecommerce/managing_products/products.rst:252 +#: ../../content/applications/websites/ecommerce/products.rst:254 msgid "You can enable a **product comparison tool** for your eCommerce by going to :menuselection:`Website --> Configuration --> Settings --> Shop - Products`, and ticking :guilabel:`Product Comparison Tool`. This tool allows to save products' **specifications** and compare them against each other on a single page." msgstr "" -#: ../../content/applications/websites/ecommerce/managing_products/products.rst:257 +#: ../../content/applications/websites/ecommerce/products.rst:259 msgid "On the product page, scroll down to the :guilabel:`Specifications` section and click :guilabel:`Compare`. Repeat the same process for all products you wish to compare. Then, click the :guilabel:`Compare` button of the pop-up window at the bottom of the page to reach the comparison summary." msgstr "" -#: ../../content/applications/websites/ecommerce/managing_products/products.rst:263 -msgid "The :guilabel:`Product Comparison Tool` can only be used if :doc:`attributes ` are set on the **product's template**." +#: ../../content/applications/websites/ecommerce/products.rst:265 +msgid "The :guilabel:`Product Comparison Tool` can only be used if :doc:`attributes ` are set on the **product's template**." msgstr "" -#: ../../content/applications/websites/ecommerce/managing_products/products.rst:-1 +#: ../../content/applications/websites/ecommerce/products.rst:-1 msgid "Product comparison window" msgstr "" -#: ../../content/applications/websites/ecommerce/managing_products/variants.rst:3 +#: ../../content/applications/websites/ecommerce/products/catalog.rst:3 +msgid "Catalog" +msgstr "" + +#: ../../content/applications/websites/ecommerce/products/catalog.rst:5 +msgid "The eCommerce catalog is the equivalent of your physical store shelves: it allows customers to see what you have to offer. Clear categories, available options, sorting, and navigation threads help you structure it efficiently." +msgstr "" + +#: ../../content/applications/websites/ecommerce/products/catalog.rst:10 +msgid "Categorize the product catalog" +msgstr "" + +#: ../../content/applications/websites/ecommerce/products/catalog.rst:12 +msgid "In Odoo, there is a **specific category model** for your eCommerce. Using eCommerce categories for your products allows you to add a navigation menu on your eCommerce page. Visitors can then use it to view all products under the category they select." +msgstr "" + +#: ../../content/applications/websites/ecommerce/products/catalog.rst:16 +msgid "To do so, go to :menuselection:`Website --> eCommerce --> Products`, select the product you wish to modify, click on the :guilabel:`Sales` tab, and select the :guilabel:`Categories` you want under :guilabel:`eCommerce Shop`." +msgstr "" + +#: ../../content/applications/websites/ecommerce/products/catalog.rst:-1 +msgid "eCommerce categories under the \"Sales\" tab" +msgstr "" + +#: ../../content/applications/websites/ecommerce/products/catalog.rst:25 +msgid "A single product can appear under multiple eCommerce categories." +msgstr "" + +#: ../../content/applications/websites/ecommerce/products/catalog.rst:27 +msgid "When your product's categories are configured, go to your **main shop page** and click on :menuselection:`Edit --> Customize tab`. In the :guilabel:`Categories` option, you can either enable a menu on the :guilabel:`Left`, on the :guilabel:`Top`, or both. If you select the :guilabel:`Left` category, the option :guilabel:`Collapsable Category Recursive` appears and allows to render the :guilabel:`Left` category menu collapsable." +msgstr "" + +#: ../../content/applications/websites/ecommerce/products/catalog.rst:-1 +msgid "Categories options for your eCommerce website" +msgstr "" + +#: ../../content/applications/websites/ecommerce/products/catalog.rst:38 +#: ../../content/applications/websites/ecommerce/products/variants.rst:14 +msgid ":doc:`../products`" +msgstr "" + +#: ../../content/applications/websites/ecommerce/products/catalog.rst:43 +msgid "Browsing" +msgstr "" + +#: ../../content/applications/websites/ecommerce/products/catalog.rst:45 +msgid "The eCommerce category is the first tool to organize and split your products. However, if you need an extra level of categorization in your catalog, you can activate various **filters** such as attributes or sort-by search." +msgstr "" + +#: ../../content/applications/websites/ecommerce/products/catalog.rst:50 +msgid "Attributes" +msgstr "" + +#: ../../content/applications/websites/ecommerce/products/catalog.rst:52 +msgid "Attributes refer to **characteristics** of a product, such as **color** or **material**, whereas variants are the different combinations of attributes. :guilabel:`Attributes and Variants` can be found under :menuselection:`Website --> eCommerce --> Products`, select your product, and :guilabel:`Attributes & Variants` tab." +msgstr "" + +#: ../../content/applications/websites/ecommerce/products/catalog.rst:58 +#: ../../content/applications/websites/ecommerce/products/variants.rst:15 +msgid ":doc:`../../../sales/sales/products_prices/products/variants`" +msgstr "" + +#: ../../content/applications/websites/ecommerce/products/catalog.rst:-1 +msgid "Attributes and variants of your product" +msgstr "" + +#: ../../content/applications/websites/ecommerce/products/catalog.rst:64 +msgid "To enable **attribute filtering**, go to your **main shop page**, click on :menuselection:`Edit --> Customize tab` and select either :guilabel:`Left`, :guilabel:`Top`, or both. Additionally, you can also enable :guilabel:`Price Filtering` to enable price filters." +msgstr "" + +#: ../../content/applications/websites/ecommerce/products/catalog.rst:69 +msgid ":guilabel:`Price Filter` works independently from **attributes** and, therefore, can be enabled on its own if desired." +msgstr "" + +#: ../../content/applications/websites/ecommerce/products/catalog.rst:73 +msgid "You can use **attribute filters** even if you do not work with product variants. When adding attributes to your products, make sure only to specify *one* value per attribute. Odoo does not create variants if no combination is possible." +msgstr "" + +#: ../../content/applications/websites/ecommerce/products/catalog.rst:78 +msgid "Sort-by search" +msgstr "" + +#: ../../content/applications/websites/ecommerce/products/catalog.rst:80 +msgid "It is possible to allow the user to manually **sort the catalog** using the search bar. From your **main shop page**, click on :menuselection:`Edit --> Customize tab`; you can enable or disable the :guilabel:`Sort-By` option as well as the :guilabel:`Layout` button. You can also select the :guilabel:`Default Sort` of the :guilabel:`Sort-By` button. The default sort applies to *all* categories." +msgstr "" + +#: ../../content/applications/websites/ecommerce/products/catalog.rst:86 +msgid "The **sorting** options are:" +msgstr "" + +#: ../../content/applications/websites/ecommerce/products/catalog.rst:88 +msgid "Featured" +msgstr "" + +#: ../../content/applications/websites/ecommerce/products/catalog.rst:89 +msgid "Newest Arrivals" +msgstr "" + +#: ../../content/applications/websites/ecommerce/products/catalog.rst:90 +msgid "Name (A-Z)" +msgstr "" + +#: ../../content/applications/websites/ecommerce/products/catalog.rst:91 +msgid "Price - Low to High" +msgstr "" + +#: ../../content/applications/websites/ecommerce/products/catalog.rst:92 +msgid "Price - High to Low" +msgstr "" + +#: ../../content/applications/websites/ecommerce/products/catalog.rst:94 +msgid "In addition, you can **manually edit** the catalog's order of a product by going to **the main shop page** and clicking on the product. Under the :guilabel:`Product` section of the :guilabel:`Customize` section, you can rearrange the order by clicking on the arrows. `<<` `>>` move the product to the **extreme** right or left, and `<` `>` move the product by **one** row to the right or left. It is also possible to change the catalog's order of products in :menuselection:`Website --> eCommerce --> Products` and drag-and-dropping the products within the list." +msgstr "" + +#: ../../content/applications/websites/ecommerce/products/catalog.rst:-1 +msgid "Product rearrangement in the catalog" +msgstr "" + +#: ../../content/applications/websites/ecommerce/products/catalog.rst:107 +msgid "Page design" +msgstr "" + +#: ../../content/applications/websites/ecommerce/products/catalog.rst:110 +msgid "Category page" +msgstr "" + +#: ../../content/applications/websites/ecommerce/products/catalog.rst:112 +msgid "You can customize the layout of the category page using the website builder." +msgstr "" + +#: ../../content/applications/websites/ecommerce/products/catalog.rst:115 +msgid "Editing the layout of the category page is global; editing one category layout affects *all* category pages." +msgstr "" + +#: ../../content/applications/websites/ecommerce/products/catalog.rst:118 +msgid "To do so, go on to your :menuselection:`Category page --> Edit --> Customize`. Here, you can choose the layout, the number of columns to display the products, etc. The :guilabel:`Product Description` button makes the product description visible from the category page, underneath the product picture." +msgstr "" + +#: ../../content/applications/websites/ecommerce/products/catalog.rst:-1 +msgid "Layout options of the category pages." +msgstr "" + +#: ../../content/applications/websites/ecommerce/products/catalog.rst:127 +msgid "You can choose the size of the grid, but be aware that displaying too many products may affect performance and page loading speed." +msgstr "" + +#: ../../content/applications/websites/ecommerce/products/catalog.rst:131 +msgid "Product highlight" +msgstr "" + +#: ../../content/applications/websites/ecommerce/products/catalog.rst:133 +msgid "You can highlight products to make them more visible on the category or product page. On the page of your choice, go to :menuselection:`Edit --> Customize` and click on the product to highlight. In the :guilabel:`Product` section, you can choose the size of the product image by clicking on the grid, and you can also add a **ribbon** or :guilabel:`Badge`. This displays a banner across the product's image, such as:" +msgstr "" + +#: ../../content/applications/websites/ecommerce/products/catalog.rst:139 +msgid "Sale;" +msgstr "" + +#: ../../content/applications/websites/ecommerce/products/catalog.rst:140 +msgid "Sold out;" +msgstr "" + +#: ../../content/applications/websites/ecommerce/products/catalog.rst:141 +msgid "Out of stock;" +msgstr "" + +#: ../../content/applications/websites/ecommerce/products/catalog.rst:142 +msgid "New." +msgstr "" + +#: ../../content/applications/websites/ecommerce/products/catalog.rst:144 +msgid "Alternatively, you can activate the :doc:`developer mode <../../../general/developer_mode>` on the **product's template**, and under the :guilabel:`Sales` tab, change or create the ribbon from the :guilabel:`Ribbon` field." +msgstr "" + +#: ../../content/applications/websites/ecommerce/products/catalog.rst:149 +msgid "The :doc:`developer mode <../../../general/developer_mode>` is only intended for experienced users who wish to have access to advanced tools. Using the **developer mode** is *not* recommended for regular users." +msgstr "" + +#: ../../content/applications/websites/ecommerce/products/catalog.rst:-1 +msgid "Ribbon highlight" +msgstr "" + +#: ../../content/applications/websites/ecommerce/products/catalog.rst:158 +msgid "Additional features" +msgstr "" + +#: ../../content/applications/websites/ecommerce/products/catalog.rst:160 +msgid "You can access and enable additional feature buttons such as **add to cart**, **comparison list**, or a **wishlist**. To do so, go to your **main shop page**, and at the end of the :guilabel:`Products Page` category, click on the feature buttons you wish to use. All three buttons appear when hovering the mouse over a product's image." +msgstr "" + +#: ../../content/applications/websites/ecommerce/products/catalog.rst:165 +msgid ":guilabel:`Add to Cart`: adds a button to :doc:`add the product to the cart <../checkout_payment_shipping/cart>`;" +msgstr "" + +#: ../../content/applications/websites/ecommerce/products/catalog.rst:167 +msgid ":guilabel:`Comparison List`: adds a button to **compare** products based on their price, variant, etc.;" +msgstr "" + +#: ../../content/applications/websites/ecommerce/products/catalog.rst:169 +msgid ":guilabel:`Wishlist Button`: adds a button to **wishlist** the product." +msgstr "" + +#: ../../content/applications/websites/ecommerce/products/catalog.rst:-1 +msgid "Feature buttons for add to cart, comparison list, and wishlist" +msgstr "" + +#: ../../content/applications/websites/ecommerce/products/catalog.rst:-1 +msgid "Appearance of buttons when hoovering over the mouse" +msgstr "" + +#: ../../content/applications/websites/ecommerce/products/catalog.rst:182 +msgid "You can use **building blocks** to add content on the category page, with a variety of blocks ranging from :guilabel:`Structure` to :guilabel:`Dynamic Content`. Specific areas are defined to use blocks are defined and highlighted on the page when **dragging-and-dropping** a block." +msgstr "" + +#: ../../content/applications/websites/ecommerce/products/catalog.rst:-1 +msgid "Building blocks areas" +msgstr "" + +#: ../../content/applications/websites/ecommerce/products/catalog.rst:190 +msgid "If you drop a building block **on top** of the product list, it creates a new category header specific to *that* category." +msgstr "" + +#: ../../content/applications/websites/ecommerce/products/catalog.rst:192 +msgid "If you drop a building **on the top** or **bottom** of the page, it becomes visible on *all* category pages." +msgstr "" + +#: ../../content/applications/websites/ecommerce/products/catalog.rst:196 +msgid "Adding content to an eCommerce category page is beneficial in terms of **SEO** strategy. Using **keywords** linked to the products or the eCommerce categories improves organic traffic. Additionally, each category has its own specific URL that can be pointed to and is indexed by search engines." +msgstr "" + +#: ../../content/applications/websites/ecommerce/products/cross_upselling.rst:3 +msgid "Cross-selling and upselling" +msgstr "" + +#: ../../content/applications/websites/ecommerce/products/cross_upselling.rst:5 +msgid "Any sales process is an opportunity to maximize revenues. **Cross-selling and upselling** are sales techniques consisting in selling customers additional or more expensive products and services than what they were originally shopping for. It is a great way to maximize the value of each one of your customers." +msgstr "" + +#: ../../content/applications/websites/ecommerce/products/cross_upselling.rst:10 +msgid "**Cross-selling** can be done via **two** features:" +msgstr "" + +#: ../../content/applications/websites/ecommerce/products/cross_upselling.rst:12 +msgid ":ref:`Optional products ` upon **adding to cart**;" +msgstr "" + +#: ../../content/applications/websites/ecommerce/products/cross_upselling.rst:13 +msgid ":ref:`Accessory products ` on the **checkout page**." +msgstr "" + +#: ../../content/applications/websites/ecommerce/products/cross_upselling.rst:15 +msgid "**Upselling** is only done via :ref:`alternative products ` on the **product page**." +msgstr "" + +#: ../../content/applications/websites/ecommerce/products/cross_upselling.rst:19 +msgid ":doc:`catalog`" +msgstr "" + +#: ../../content/applications/websites/ecommerce/products/cross_upselling.rst:22 +msgid "Cross-selling" +msgstr "" + +#: ../../content/applications/websites/ecommerce/products/cross_upselling.rst:27 +msgid "Optional products" +msgstr "" + +#: ../../content/applications/websites/ecommerce/products/cross_upselling.rst:29 +msgid "**Optional products** are suggested when customers click :guilabel:`Add to cart`, either from the **product page** or **catalog page**. Upon clicking, a pop-up window opens with the **optional products** displayed in the :guilabel:`Available Options` section." +msgstr "" + +#: ../../content/applications/websites/ecommerce/products/cross_upselling.rst:-1 +msgid "Optional products cross-selling" +msgstr "" + +#: ../../content/applications/websites/ecommerce/products/cross_upselling.rst:37 +msgid "To enable **optional products** go to :menuselection:`Website --> eCommerce --> Products`, select a product, go to the :guilabel:`Sales` tab, and enter the products you wish to feature in the :guilabel:`Optional Products` field. Optional products are **linked** to the product(s) they are set up with on the **product template**. They only appear when that product is added to the cart." +msgstr "" + +#: ../../content/applications/websites/ecommerce/products/cross_upselling.rst:43 +msgid "You can also access the :guilabel:`Sales` tab of the **product template** by selecting a product on your **main shop page** and clicking :guilabel:`Product` in the top-right corner." +msgstr "" + +#: ../../content/applications/websites/ecommerce/products/cross_upselling.rst:49 +msgid "Accessory products" +msgstr "" + +#: ../../content/applications/websites/ecommerce/products/cross_upselling.rst:51 +msgid "**Accessory products** are displayed in the :guilabel:`Suggested Accessories` section before processing to checkout at the :guilabel:`Review Order` step." +msgstr "" + +#: ../../content/applications/websites/ecommerce/products/cross_upselling.rst:-1 +msgid "Suggested accessories at checkout during cart review" +msgstr "" + +#: ../../content/applications/websites/ecommerce/products/cross_upselling.rst:58 +msgid "To enable **accessory products**, go to :menuselection:`Website --> eCommerce --> Products`, select a product, go to the :guilabel:`Sales` tab, and enter the products you wish to feature in the :guilabel:`Accessory Products` field. Suggested accessory products are **linked** to the product(s) they are set up with on the **product template**. They only appear when that product is at the checkout process review." +msgstr "" + +#: ../../content/applications/websites/ecommerce/products/cross_upselling.rst:65 +msgid "Upselling" +msgstr "" + +#: ../../content/applications/websites/ecommerce/products/cross_upselling.rst:70 +msgid "Alternative products" +msgstr "" + +#: ../../content/applications/websites/ecommerce/products/cross_upselling.rst:72 +msgid "**Alternative products** are suggested on the **product page** and usually incentivize customers to buy a more expensive variant or product than the one they were initially shopping for." +msgstr "" + +#: ../../content/applications/websites/ecommerce/products/cross_upselling.rst:-1 +msgid "Alternative products on the product page" +msgstr "" + +#: ../../content/applications/websites/ecommerce/products/cross_upselling.rst:79 +msgid "To enable **alternative products**, go to :menuselection:`Website --> eCommerce --> Products`, select a product, go to the :guilabel:`Sales` tab, and enter the products you wish to feature in the :guilabel:`Alternative Products` field. Then, go to the related **product page** by clicking :guilabel:`Go To Website`, and click :menuselection:`Edit`. Stay on the :guilabel:`Blocks` tab, and scroll down to the :guilabel:`Dynamic Content` section. Then, drag and drop the :guilabel:`Products` building block anywhere on the **product page**." +msgstr "" + +#: ../../content/applications/websites/ecommerce/products/cross_upselling.rst:86 +msgid "When placed, in :guilabel:`Edit` mode, click the **block** to access various settings for that :guilabel:`Products` building block. In the :guilabel:`Filter` field, select :guilabel:`Alternative Products`. You can configure several additional settings, such as how many elements are displayed (:guilabel:`Fetched Elements`), the :guilabel:`Template` used, etc." +msgstr "" + +#: ../../content/applications/websites/ecommerce/products/price_management.rst:3 +msgid "Price management" +msgstr "" + +#: ../../content/applications/websites/ecommerce/products/price_management.rst:5 +msgid "Odoo offers multiple options to select the price displayed on your website, as well as condition-specific prices based on set criteria." +msgstr "" + +#: ../../content/applications/websites/ecommerce/products/price_management.rst:9 +msgid "Taxes" +msgstr "" + +#: ../../content/applications/websites/ecommerce/products/price_management.rst:12 +msgid "Tax configuration" +msgstr "" + +#: ../../content/applications/websites/ecommerce/products/price_management.rst:14 +msgid "To add a tax on a product, you can either set a tax in the :guilabel:`Customer Taxes` field of the **product template** or use :doc:`fiscal positions `." +msgstr "" + +#: ../../content/applications/websites/ecommerce/products/price_management.rst:19 +msgid ":doc:`/applications/finance/accounting/taxes`" +msgstr "" + +#: ../../content/applications/websites/ecommerce/products/price_management.rst:20 +msgid ":doc:`/applications/finance/accounting/taxes/avatax`" +msgstr "" + +#: ../../content/applications/websites/ecommerce/products/price_management.rst:21 +msgid ":doc:`/applications/finance/accounting/taxes/fiscal_positions`" +msgstr "" + +#: ../../content/applications/websites/ecommerce/products/price_management.rst:24 +msgid "Tax display" +msgstr "" + +#: ../../content/applications/websites/ecommerce/products/price_management.rst:26 +msgid "Choosing the displayed price tax usually depends on a country's regulations or the type of customers **(B2B vs. B2C)**. To select the type of price displayed, go to :menuselection:`Website --> Configuration --> Settings`, scroll down to the :guilabel:`Shop - Products` category, and select :guilabel:`Tax Excluded` or :guilabel:`Tax Included`." +msgstr "" + +#: ../../content/applications/websites/ecommerce/products/price_management.rst:31 +msgid ":guilabel:`Tax Excluded`: the price displayed on the website is **tax-excluded**, and the tax is computed at the cart-review step;" +msgstr "" + +#: ../../content/applications/websites/ecommerce/products/price_management.rst:33 +msgid ":guilabel:`Tax Included`: the price displayed on the website is **tax-included**." +msgstr "" + +#: ../../content/applications/websites/ecommerce/products/price_management.rst:36 +msgid "This setting is **global**, and the tax-display type is the same for (all of) your website(s). It is, therefore, not possible to select different tax displays for different websites. This may be a significant point of consideration when implementing a database with multiple ecommerce websites aimed at varying customer types (i.e., B2B and B2C)." +msgstr "" + +#: ../../content/applications/websites/ecommerce/products/price_management.rst:41 +msgid "You can choose to display the type of pricing next to the product price by going to :menuselection:`Website --> Site --> Homepage --> Shop`, selecting a product, and then :menuselection:`Edit --> Customize tab` and enabling :guilabel:`Tax Indication`." +msgstr "" + +#: ../../content/applications/websites/ecommerce/products/price_management.rst:-1 +msgid "Tax type displayed on the product page" +msgstr "" + +#: ../../content/applications/websites/ecommerce/products/price_management.rst:50 +msgid ":doc:`/applications/finance/accounting/taxes/B2B_B2C`" +msgstr "" + +#: ../../content/applications/websites/ecommerce/products/price_management.rst:53 +msgid "Price per unit" +msgstr "" + +#: ../../content/applications/websites/ecommerce/products/price_management.rst:55 +msgid "It is possible to display a :doc:`price per unit ` on the product page. To do that, go to :menuselection:`Website --> Configuration --> Settings` and enable :guilabel:`Product Reference Price` under the :guilabel:`Shop - Products` section. When enabled, ensure an amount is set in the :guilabel:`Base Unit Count` field of the **product template**, and in the :guilabel:`Sales Price`." +msgstr "" + +#: ../../content/applications/websites/ecommerce/products/price_management.rst:-1 +msgid "Cost per unit pricing on the product template" +msgstr "" + +#: ../../content/applications/websites/ecommerce/products/price_management.rst:66 +msgid "The price per unit of measure can be found above the :guilabel:`Add to Cart` button on the product page." +msgstr "" + +#: ../../content/applications/websites/ecommerce/products/price_management.rst:-1 +msgid "Cost per unit pricing on the product page" +msgstr "" + +#: ../../content/applications/websites/ecommerce/products/price_management.rst:74 +msgid "Pay attention that having the price per unit may be **mandatory** in some countries." +msgstr "" + +#: ../../content/applications/websites/ecommerce/products/price_management.rst:77 +msgid ":doc:`/applications/inventory_and_mrp/inventory/product_management/product_replenishment/uom`" +msgstr "" + +#: ../../content/applications/websites/ecommerce/products/price_management.rst:82 +msgid "Price configuration: pricelists" +msgstr "" + +#: ../../content/applications/websites/ecommerce/products/price_management.rst:84 +msgid "Pricelists are the primary tool to manage prices on your eCommerce. They allow you to define website-specific prices - different from the price on the product template - based on the **country group**, **currency**, **minimum quantity**, **period**, or **variant**. You can create as many pricelists as needed, but it is mandatory to have at least one pricelist configured per website. If no custom pricelists are added, Odoo defaults to the **Public Pricelist** for all websites." +msgstr "" + +#: ../../content/applications/websites/ecommerce/products/price_management.rst:91 +#: ../../content/applications/websites/ecommerce/products/price_management.rst:119 +msgid ":doc:`/applications/sales/sales/products_prices/prices/pricing`" +msgstr "" + +#: ../../content/applications/websites/ecommerce/products/price_management.rst:96 +msgid "Pricelists can be found under :menuselection:`Website --> eCommerce --> Pricelists`, but must first be activated. For that, head to :menuselection:`Website --> Configuration --> Settings` and scroll down to the :guilabel:`Shop - Products` section. There, you can find two options:" +msgstr "" + +#: ../../content/applications/websites/ecommerce/products/price_management.rst:100 +msgid ":guilabel:`Multiple prices per product`;" +msgstr "" + +#: ../../content/applications/websites/ecommerce/products/price_management.rst:101 +msgid ":guilabel:`Advanced price rules (discounts, formulas)`." +msgstr "" + +#: ../../content/applications/websites/ecommerce/products/price_management.rst:103 +msgid "The **first** option allows you to set different prices per customer *segment*, i.e., registered customers, gold customers, regular customers, etc. The **second** option allows you to set *price change* rules such as **discounts**, **margins**, **roundings**, etc." +msgstr "" + +#: ../../content/applications/websites/ecommerce/products/price_management.rst:108 +msgid "Foreign currency" +msgstr "" + +#: ../../content/applications/websites/ecommerce/products/price_management.rst:110 +msgid "If you are selling in **multiple currencies** and have pricelists in foreign currencies, customers can select their corresponding pricelist anywhere on the :guilabel:`Shop` page from the drop-down menu next to the **search bar**." +msgstr "" + +#: ../../content/applications/websites/ecommerce/products/price_management.rst:-1 +msgid "Pricelists selection" +msgstr "" + +#: ../../content/applications/websites/ecommerce/products/price_management.rst:120 +msgid ":doc:`/applications/sales/sales/products_prices/prices/currencies`" +msgstr "" + +#: ../../content/applications/websites/ecommerce/products/price_management.rst:123 +msgid "Permanent discount" +msgstr "" + +#: ../../content/applications/websites/ecommerce/products/price_management.rst:125 +msgid "If you have permanently reduced the price of a product, a popular means to attract customers is the **strikethrough** strategy. The strategy consists in displaying the previous price crossed out and the **new discounted price** next to it." +msgstr "" + +#: ../../content/applications/websites/ecommerce/products/price_management.rst:-1 +msgid "Price strikethrough" +msgstr "" + +#: ../../content/applications/websites/ecommerce/products/price_management.rst:133 +msgid "To display a 'striked' price, enable the :guilabel:`Comparison Price` option under :menuselection:`Website --> Configuration --> Settings --> Shop - Products category`. Then, head to the product's template (:menuselection:`Website --> eCommerce --> Products`), and in the :guilabel:`Compare to Price` field, enter the **new** price." +msgstr "" + +#: ../../content/applications/websites/ecommerce/products/variants.rst:3 msgid "Product variants" msgstr "" -#: ../../content/applications/websites/ecommerce/managing_products/variants.rst:5 +#: ../../content/applications/websites/ecommerce/products/variants.rst:5 msgid "Product variants are variations, such as different colors, materials, etc., of the same product. These variations can differ in price and availability from the product. Product variants can either be :doc:`created <../../../sales/sales/products_prices/products/variants>` or :doc:`imported <../../../sales/sales/products_prices/products/import>`." msgstr "" -#: ../../content/applications/websites/ecommerce/managing_products/variants.rst:10 +#: ../../content/applications/websites/ecommerce/products/variants.rst:10 msgid "To use product variants, enable them under :menuselection:`Website --> Configuration --> Settings`, in the :guilabel:`Shop - Products` section." msgstr "" -#: ../../content/applications/websites/ecommerce/managing_products/variants.rst:14 -msgid ":doc:`../managing_products/products`" +#: ../../content/applications/websites/ecommerce/products/variants.rst:16 +msgid ":doc:`../../../sales/sales/products_prices/products/import`" msgstr "" -#: ../../content/applications/websites/ecommerce/managing_products/variants.rst:19 +#: ../../content/applications/websites/ecommerce/products/variants.rst:19 msgid "Product configurator" msgstr "" -#: ../../content/applications/websites/ecommerce/managing_products/variants.rst:21 +#: ../../content/applications/websites/ecommerce/products/variants.rst:21 msgid "Adding attributes and values to a product template allows the enabling of the **product configurator** on the product page. Customers use it to configure and select the product variant of their choice; or in the case of multiple attributes, combine those to create a specific variant." msgstr "" -#: ../../content/applications/websites/ecommerce/managing_products/variants.rst:-1 +#: ../../content/applications/websites/ecommerce/products/variants.rst:-1 msgid "Variants configurator" msgstr "" -#: ../../content/applications/websites/ecommerce/managing_products/variants.rst:29 +#: ../../content/applications/websites/ecommerce/products/variants.rst:29 msgid "The **display type** of each attribute used in the product configurator can be edited through the **website builder** by clicking :menuselection:`Edit --> Customize` on the product page, and then clicking on one of the attributes. You can then select between four options:" msgstr "" -#: ../../content/applications/websites/ecommerce/managing_products/variants.rst:33 +#: ../../content/applications/websites/ecommerce/products/variants.rst:33 msgid ":guilabel:`Radio`" msgstr "" -#: ../../content/applications/websites/ecommerce/managing_products/variants.rst:34 +#: ../../content/applications/websites/ecommerce/products/variants.rst:34 msgid ":guilabel:`Pills`" msgstr "" -#: ../../content/applications/websites/ecommerce/managing_products/variants.rst:35 +#: ../../content/applications/websites/ecommerce/products/variants.rst:35 msgid ":guilabel:`Select`" msgstr "" -#: ../../content/applications/websites/ecommerce/managing_products/variants.rst:36 +#: ../../content/applications/websites/ecommerce/products/variants.rst:36 msgid ":guilabel:`Color`" msgstr "" -#: ../../content/applications/websites/ecommerce/managing_products/variants.rst:-1 +#: ../../content/applications/websites/ecommerce/products/variants.rst:-1 msgid "Display type options for attributes" msgstr "" -#: ../../content/applications/websites/ecommerce/managing_products/variants.rst:44 +#: ../../content/applications/websites/ecommerce/products/variants.rst:44 msgid "Alternatively, the **display type** can be edited through :menuselection:`Website --> eCommerce --> Attributes`, selecting an **attribute**, and then choosing a :guilabel:`Display Type`; or through the **product template** by going to :menuselection:`eCommerce --> Products`, selecting a product, and then clicking :guilabel:`Attributes and Variants`." msgstr "" -#: ../../content/applications/websites/ecommerce/managing_products/variants.rst:50 +#: ../../content/applications/websites/ecommerce/products/variants.rst:50 msgid "Specific combinations of values can be excluded from the product configurator. This way, customers are unable to select the excluded combination of values. To do so, go to :menuselection:`Website --> eCommerce --> Products`, select a product, and go to :guilabel:`Attributes and Variants`. Then, click on an **attribute**, select a **value**, and in the :guilabel:`Exclude for` section, select a :guilabel:`Product Template` and the :guilabel:`Attribute Values` to exclude." msgstr "" -#: ../../content/applications/websites/ecommerce/managing_products/variants.rst:58 +#: ../../content/applications/websites/ecommerce/products/variants.rst:58 msgid "Product specifications" msgstr "" -#: ../../content/applications/websites/ecommerce/managing_products/variants.rst:60 +#: ../../content/applications/websites/ecommerce/products/variants.rst:60 msgid "Values used for each attribute are displayed as a **specification list** at the bottom of the product page. To be visible, the **specification list** must first be enabled on the product page by going to :menuselection:`Edit --> Customize` and selecting a placement for the field :guilabel:`Specification`." msgstr "" -#: ../../content/applications/websites/ecommerce/managing_products/variants.rst:-1 +#: ../../content/applications/websites/ecommerce/products/variants.rst:-1 msgid "Specifications list on the product page" msgstr "" -#: ../../content/applications/websites/ecommerce/managing_products/variants.rst:70 +#: ../../content/applications/websites/ecommerce/products/variants.rst:70 msgid "The product **specification list** can also be used on products without variants. For that, make sure to have no values combination. Products with single values for their attributes do not generate variants." msgstr "" -#: ../../content/applications/websites/ecommerce/managing_products/variants.rst:75 +#: ../../content/applications/websites/ecommerce/products/variants.rst:75 msgid "Filter catalog by attributes" msgstr "" -#: ../../content/applications/websites/ecommerce/managing_products/variants.rst:77 +#: ../../content/applications/websites/ecommerce/products/variants.rst:77 msgid "Customers **can** filter the **catalog** based on product attributes and values, allowing them to :ref:`filter ` the catalog based only on the attribute(s) of their choice." msgstr "" -#: ../../content/applications/websites/ecommerce/managing_products/variants.rst:80 +#: ../../content/applications/websites/ecommerce/products/variants.rst:80 msgid "To enable **attributes filtering**, go to :menuselection:`Edit --> Customize` from your **main shop page** and click on one of the :guilabel:`Categories` in the left column. Here, enable either :guilabel:`Left`, :guilabel:`Top`, or **both**, in the :guilabel:`Attributes` field." msgstr "" -#: ../../content/applications/websites/ecommerce/managing_products/variants.rst:-1 +#: ../../content/applications/websites/ecommerce/products/variants.rst:-1 msgid "Categories buttons" msgstr "" @@ -3055,7 +3054,7 @@ msgid "To configure the remaining tabs on the channel detail form (:ref:`Operato msgstr "" #: ../../content/applications/websites/livechat.rst:48 -msgid "The channel detail form for any channel can be accessed by navigating back to the :guilabel:`Website Live Chat Channels` dashboard, via the breadcrumbs. Find the Kanban card for the appropriate live chat channel, hover over it, and then click on the :guilabel:`⋮ (three dots)` icon to open the drop-down menu. Click :guilabel:`Configure Channel` to open the channel detail form." +msgid "The channel detail form for any channel can be accessed by navigating back to the :guilabel:`Website Live Chat Channels` dashboard, via the breadcrumbs. Find the Kanban card for the appropriate live chat channel, hover over it, and then click on the :icon:`fa-ellipsis-v` :guilabel:`(vertical ellipsis)` icon to open the drop-down menu. Click :guilabel:`Configure Channel` to open the channel detail form." msgstr "" #: ../../content/applications/websites/livechat.rst:57 @@ -3115,7 +3114,7 @@ msgid "Change the text in the :guilabel:`Notification text` field to update the msgstr "" #: ../../content/applications/websites/livechat.rst:113 -msgid "The :guilabel:`Livechat Button Color` alters the color of the live chat button as it appears on the website. To change the color, click on a color bubble to open the color selection window, then click and drag the circle along the color gradient. Click out of the selection window once complete. Click the :guilabel:`🔁 (refresh)` icon to the right of the color bubbles to reset the colors to the default selection." +msgid "The :guilabel:`Livechat Button Color` alters the color of the live chat button as it appears on the website. To change the color, click on a color bubble to open the color selection window, then click and drag the circle along the color gradient. Click out of the selection window once complete. Click the :icon:`fa-refresh` :guilabel:`(refresh)` icon to the right of the color bubbles to reset the colors to the default selection." msgstr "" #: ../../content/applications/websites/livechat.rst:120 @@ -3259,117 +3258,25 @@ msgid "View of the widget tab for Odoo Live Chat." msgstr "" #: ../../content/applications/websites/livechat.rst:243 -msgid "Participate in a conversation" -msgstr "" - -#: ../../content/applications/websites/livechat.rst:245 -msgid "As explained above, *operators* are the users who respond to live chat requests from customers. The information below outlines the necessary steps for operators participating in live chat conversations on an Odoo database." -msgstr "" - -#: ../../content/applications/websites/livechat.rst:250 -msgid "Set an online chat name" -msgstr "" - -#: ../../content/applications/websites/livechat.rst:252 -msgid "Before participating in a live chat, operators may choose to update their *Online Chat Name*. This is the name that is displayed to site visitors in the live chat conversation." -msgstr "" - -#: ../../content/applications/websites/livechat.rst:255 -msgid "To update the :guilabel:`Online Chat Name`, click on the user avatar in the top-right corner of any page in the database. Select :guilabel:`My Profile` from the drop-down menu to open the profile page. On the right side of the :guilabel:`Preferences` tab, locate the :guilabel:`Online Chat Name` field, and enter a preferred name." -msgstr "" - -#: ../../content/applications/websites/livechat.rst:260 -msgid "If a user's :guilabel:`Online Chat Name` is not set, the name displayed defaults to the user's name that is designated on their profile page." -msgstr "" - -#: ../../content/applications/websites/livechat.rst:264 -msgid "A user has their full name as their :guilabel:`User Name`, but they do not want to include their last name in a live chat conversation. They would then set their :guilabel:`Online Chat Name` to include only their first name." -msgstr "" - -#: ../../content/applications/websites/livechat.rst:0 -msgid "View of user profile in Odoo, emphasizing the Online Chat name field." -msgstr "" - -#: ../../content/applications/websites/livechat.rst:273 -msgid "Set online chat languages" -msgstr "" - -#: ../../content/applications/websites/livechat.rst:275 -msgid "If an operator speaks multiple languages, they can add this information to their user profile. This information can then be used to determine what conversations the operator is assigned. A visitor's language is determined, via their browser's language settings." -msgstr "" - -#: ../../content/applications/websites/livechat.rst:279 -msgid "To add *Online Chat Languages*, click on the user avatar in the top-right corner of any page in the database. Select :guilabel:`My Profile` from the drop-down menu to open the profile page. On the right side of the :guilabel:`Preferences` tab, click into the :guilabel:`Online Chat Language` field, and select one or more languages from the drop-down menu." -msgstr "" - -#: ../../content/applications/websites/livechat.rst:285 -msgid "Conversations are assigned to operators based on a number of criteria, including availability and the number of ongoing conversations. While the operator's main language and additional languages are taken into consideration, they do **not** supersede all other criteria." -msgstr "" - -#: ../../content/applications/websites/livechat.rst:290 -msgid "Join or leave a channel" -msgstr "" - -#: ../../content/applications/websites/livechat.rst:292 -msgid "To join a live chat channel, go to the :menuselection:`Live Chat app --> Channels`, and click the :guilabel:`Join` button on the Kanban card for the appropriate channel." -msgstr "" - -#: ../../content/applications/websites/livechat.rst:295 -msgid "Any channel where the user is currently active shows a :guilabel:`Leave` button. Click this button to disconnect from the channel." -msgstr "" - -#: ../../content/applications/websites/livechat.rst:-1 -msgid "View of a channel form and the option to join a channel for Odoo Live Chat." -msgstr "" - -#: ../../content/applications/websites/livechat.rst:303 -msgid "Operators that do not show any activity in Odoo for more than thirty minutes are considered disconnected, and subsequently removed from the channel." -msgstr "" - -#: ../../content/applications/websites/livechat.rst:307 -msgid "Manage live chat requests" -msgstr "" - -#: ../../content/applications/websites/livechat.rst:309 -msgid "When an operator is active in a channel, chat windows open in the bottom-right corner of the screen, no matter where they are in the database. They can participate in conversations without leaving their current location." -msgstr "" - -#: ../../content/applications/websites/livechat.rst:314 -msgid "Conversations can also be accessed by clicking the :guilabel:`(comments)` icon in the menu bar. bar." -msgstr "" - -#: ../../content/applications/websites/livechat.rst:0 -msgid "View of the menu bar in Odoo emphasizing the comments icon." -msgstr "" - -#: ../../content/applications/websites/livechat.rst:321 -msgid "Live chat conversations can also be viewed by navigating to :menuselection:`Discuss app`. New conversations appear in bold under the :guilabel:`LIVECHAT` heading, located along the left panel." -msgstr "" - -#: ../../content/applications/websites/livechat.rst:-1 -msgid "View of the discuss application with a message sent through live chat in Odoo." -msgstr "" - -#: ../../content/applications/websites/livechat.rst:328 -msgid "Click on a conversation in the left panel to select it. This opens the conversation. From this view, an operator can participate in the chat the same as they would in the normal chat window." -msgstr "" - -#: ../../content/applications/websites/livechat.rst:332 msgid ":doc:`../productivity/discuss`" msgstr "" -#: ../../content/applications/websites/livechat.rst:333 +#: ../../content/applications/websites/livechat.rst:244 msgid ":doc:`livechat/responses`" msgstr "" -#: ../../content/applications/websites/livechat.rst:334 +#: ../../content/applications/websites/livechat.rst:245 msgid ":doc:`livechat/ratings`" msgstr "" -#: ../../content/applications/websites/livechat.rst:335 +#: ../../content/applications/websites/livechat.rst:246 msgid ":doc:`livechat/chatbots`" msgstr "" +#: ../../content/applications/websites/livechat.rst:247 +msgid ":doc:`livechat/participate`" +msgstr "" + #: ../../content/applications/websites/livechat/chatbots.rst:3 msgid "Chatbots" msgstr "" @@ -3383,7 +3290,7 @@ msgid "Chatbots can be customized to fill various roles, from customer support, msgstr "" #: ../../content/applications/websites/livechat/chatbots.rst:-1 -#: ../../content/applications/websites/livechat/responses.rst:-1 +#: ../../content/applications/websites/livechat/responses.rst:0 msgid "View of the chat window with a helpdesk ticket created in Odoo Live Chat." msgstr "" @@ -3675,6 +3582,118 @@ msgstr "" msgid ":doc:`Live chat channel rules `" msgstr "" +#: ../../content/applications/websites/livechat/participate.rst:3 +msgid "Participate in live chat" +msgstr "" + +#: ../../content/applications/websites/livechat/participate.rst:5 +msgid "*Operators* are the users who respond to live chat requests from customers and website visitors. The information below outlines the necessary steps for operators participating in live chat conversations on an Odoo database." +msgstr "" + +#: ../../content/applications/websites/livechat/participate.rst:10 +msgid "Set an online chat name" +msgstr "" + +#: ../../content/applications/websites/livechat/participate.rst:12 +msgid "Before participating in a live chat, operators may choose to update their *Online Chat Name*. This is the name displayed to site visitors in the live chat conversation." +msgstr "" + +#: ../../content/applications/websites/livechat/participate.rst:15 +msgid "To update the *Online Chat Name*, click on the user avatar in the top-right corner of any page in the database. Select :guilabel:`My Profile` from the drop-down menu to open the profile page. On the right side of the :guilabel:`Preferences` tab, locate the :guilabel:`Online Chat Name` field, and enter a preferred name." +msgstr "" + +#: ../../content/applications/websites/livechat/participate.rst:20 +msgid "If a user's :guilabel:`Online Chat Name` is not set, the name displayed defaults to the user's name that is designated on their profile page." +msgstr "" + +#: ../../content/applications/websites/livechat/participate.rst:24 +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 "" + +#: ../../content/applications/websites/livechat/participate.rst:0 +msgid "View of user profile in Odoo, emphasizing the Online Chat name field." +msgstr "" + +#: ../../content/applications/websites/livechat/participate.rst:33 +msgid "Set online chat languages" +msgstr "" + +#: ../../content/applications/websites/livechat/participate.rst:35 +msgid "If an operator speaks multiple languages, they can add this information to their user profile. This information can then be used to determine which conversations the operator is assigned. A visitor's language is determined via their browser's language settings." +msgstr "" + +#: ../../content/applications/websites/livechat/participate.rst:40 +msgid "Conversations are assigned to operators based on a number of criteria, including availability and the number of ongoing conversations. While the operator's main language and additional languages are taken into consideration, they do **not** supersede all other criteria." +msgstr "" + +#: ../../content/applications/websites/livechat/participate.rst:44 +msgid "To add *Online Chat Languages*, click on the user avatar in the top-right corner of any page in the database. Select :guilabel:`My Profile` from the drop-down menu to open the profile page. On the right side of the :guilabel:`Preferences` tab, click into the :guilabel:`Online Chat Language` field, and select one or more languages from the drop-down menu." +msgstr "" + +#: ../../content/applications/websites/livechat/participate.rst:50 +msgid "Only :doc:`languages <../../general/users/language>` that are enabled on the database can be selected in the :guilabel:`Online Chat Language` field." +msgstr "" + +#: ../../content/applications/websites/livechat/participate.rst:54 +msgid "Join or leave a channel" +msgstr "" + +#: ../../content/applications/websites/livechat/participate.rst:56 +msgid "To join a live chat channel, go to the :menuselection:`Live Chat app --> Channels`, and click the :guilabel:`Join` button on the Kanban card for the appropriate channel." +msgstr "" + +#: ../../content/applications/websites/livechat/participate.rst:59 +msgid "Any channel where the user is currently active shows a :guilabel:`Leave` button. Click this button to disconnect from the channel." +msgstr "" + +#: ../../content/applications/websites/livechat/participate.rst:-1 +msgid "View of a channel form and the option to join a channel for Odoo Live Chat." +msgstr "" + +#: ../../content/applications/websites/livechat/participate.rst:67 +msgid "Operators that do not show any activity in Odoo for more than thirty minutes are considered disconnected, and subsequently removed from the channel." +msgstr "" + +#: ../../content/applications/websites/livechat/participate.rst:71 +msgid "Manage live chat requests" +msgstr "" + +#: ../../content/applications/websites/livechat/participate.rst:73 +msgid "When an operator is active in a channel, chat windows open in the bottom-right corner of the screen, no matter where they are in the database. This allows them to access other pages and apps, while still participating in the conversation." +msgstr "" + +#: ../../content/applications/websites/livechat/participate.rst:78 +msgid "Conversations can also be accessed by clicking the :icon:`fa-comments` :guilabel:`(messages)` icon in the menu bar." +msgstr "" + +#: ../../content/applications/websites/livechat/participate.rst:0 +msgid "View of the menu bar in Odoo emphasizing the comments icon." +msgstr "" + +#: ../../content/applications/websites/livechat/participate.rst:85 +msgid "Live chat conversations can also be viewed by navigating to the :menuselection:`Discuss app`. New conversations appear in bold under the :guilabel:`LIVECHAT` heading, located along the left panel." +msgstr "" + +#: ../../content/applications/websites/livechat/participate.rst:-1 +msgid "View of the discuss application with a message sent through live chat in Odoo." +msgstr "" + +#: ../../content/applications/websites/livechat/participate.rst:92 +msgid "Click on a conversation in the left panel to select it. This opens the conversation. From this view, an operator can participate in the chat the same as they would in the normal chat window." +msgstr "" + +#: ../../content/applications/websites/livechat/participate.rst:96 +msgid ":doc:`../../productivity/discuss`" +msgstr "" + +#: ../../content/applications/websites/livechat/participate.rst:97 +msgid ":doc:`../livechat`" +msgstr "" + +#: ../../content/applications/websites/livechat/participate.rst:98 +msgid ":doc:`../livechat/responses`" +msgstr "" + #: ../../content/applications/websites/livechat/ratings.rst:3 msgid "Ratings" msgstr "" @@ -4114,7 +4133,7 @@ msgid "Commands and canned responses" msgstr "" #: ../../content/applications/websites/livechat/responses.rst:5 -msgid "In the Odoo *Live Chat* application, *commands* allow the user to perform specific actions both inside the chat window, and through other Odoo applications. The *Live Chat* app also includes *canned responses*. These are customized, pre-configured substitutions that allow users to replace shortcut entries in place of longer, well-thought out responses to some of the most common questions and comments." +msgid "In the Odoo *Live Chat* application, *commands* allow the user to perform specific actions both inside the chat window, and through other Odoo applications. The *Live Chat* app also includes *canned responses*. These are customized, preconfigured substitutions that allow users to replace shortcut entries in place of longer, well-thought out responses to some of the most common questions and comments." msgstr "" #: ../../content/applications/websites/livechat/responses.rst:11 @@ -4126,38 +4145,42 @@ msgid "Execute a command" msgstr "" #: ../../content/applications/websites/livechat/responses.rst:17 -msgid "Live chat *commands* are keywords that trigger pre-configured actions. When a live chat *operator* is participating in a conversation with a customer or website visitor, they can execute a command by typing `/`, followed by the command." +msgid "Live chat *commands* are keywords that trigger preconfigured actions. When a live chat *operator* is participating in a conversation with a customer or website visitor, they can execute a command by typing `/`, followed by the command." msgstr "" #: ../../content/applications/websites/livechat/responses.rst:21 -msgid "Commands, and the resulting actions, are only visible in the conversation window for the live chat operator. A customer will not see any commands that an operator uses in a conversation from their view of the chat." +msgid "Commands, and the resulting actions, are only visible in the conversation window for the live chat operator. A customer does not see any commands that an operator uses in a conversation from their view of the chat." msgstr "" -#: ../../content/applications/websites/livechat/responses.rst:29 +#: ../../content/applications/websites/livechat/responses.rst:26 +msgid "During a conversation with a customer, a live chat operator executes the command to :ref:`create a ticket `. After entering the command, `/ticket`, the system automatically creates a ticket with the information from the conversation. It also includes a link to the new ticket, so the operator can go there directly to add any additional information, if necessary." +msgstr "" + +#: ../../content/applications/websites/livechat/responses.rst:35 msgid "More information about each available command can be found below." msgstr "" -#: ../../content/applications/websites/livechat/responses.rst:32 +#: ../../content/applications/websites/livechat/responses.rst:38 msgid "Help" msgstr "" -#: ../../content/applications/websites/livechat/responses.rst:34 +#: ../../content/applications/websites/livechat/responses.rst:40 msgid "If an operator types `/help` in the chat window, an informative message that includes the potential entry types an operator can make is displayed." msgstr "" -#: ../../content/applications/websites/livechat/responses.rst:37 +#: ../../content/applications/websites/livechat/responses.rst:43 msgid "Type `@username` to mention a user in the conversation. A notification will be sent to that user's inbox or email, depending on their notification settings." msgstr "" -#: ../../content/applications/websites/livechat/responses.rst:39 +#: ../../content/applications/websites/livechat/responses.rst:45 msgid "Type `#channel` to mention a *Discuss* channel." msgstr "" -#: ../../content/applications/websites/livechat/responses.rst:40 +#: ../../content/applications/websites/livechat/responses.rst:46 msgid "Type `/command` to execute a command." msgstr "" -#: ../../content/applications/websites/livechat/responses.rst:41 +#: ../../content/applications/websites/livechat/responses.rst:47 msgid "Type `:shortcut` to insert a :ref:`canned response `." msgstr "" @@ -4165,40 +4188,36 @@ msgstr "" msgid "View of the message generated from using the /help command in Odoo Live Chat." msgstr "" -#: ../../content/applications/websites/livechat/responses.rst:48 +#: ../../content/applications/websites/livechat/responses.rst:54 msgid ":doc:`/applications/productivity/discuss`" msgstr "" -#: ../../content/applications/websites/livechat/responses.rst:49 +#: ../../content/applications/websites/livechat/responses.rst:55 msgid ":doc:`/applications/productivity/discuss/team_communication`" msgstr "" -#: ../../content/applications/websites/livechat/responses.rst:52 -msgid "Helpdesk & Helpdesk search" -msgstr "" - -#: ../../content/applications/websites/livechat/responses.rst:54 -msgid "The `/helpdesk` and `/helpdesk_search` commands allow operators to both create helpdesk tickets directly from a conversation, and search through existing tickets by keyword or ticket number." -msgstr "" - #: ../../content/applications/websites/livechat/responses.rst:58 -msgid "The `/helpdesk` and `/helpdesk_search` commands can only be used if the *Helpdesk* app has been installed, and *Live Chat* has been activated on a *Helpdesk* team. To activate :guilabel:`Live Chat`, go to :menuselection:`Helpdesk application --> Configuration --> Teams`, and select a team. Scroll to the :guilabel:`Channels` section and check the box labeled :guilabel:`Live Chat`." +msgid "Ticket & search tickets" +msgstr "" + +#: ../../content/applications/websites/livechat/responses.rst:60 +msgid "The `/ticket` and `/search_tickets` commands allow operators to create helpdesk tickets directly from a conversation, and search through existing tickets by keyword or ticket number." msgstr "" #: ../../content/applications/websites/livechat/responses.rst:64 +msgid "The `/ticket` and `/search_tickets` commands can **only** be used if the *Helpdesk* app has been installed, and *Live Chat* has been activated on a *Helpdesk* team. To activate *Live Chat*, go to :menuselection:`Helpdesk app --> Configuration --> Helpdesk Teams`, and select a team. Scroll to the :guilabel:`Channels` section, and check the box labeled, :guilabel:`Live Chat`." +msgstr "" + +#: ../../content/applications/websites/livechat/responses.rst:72 msgid "Create a ticket from a live chat" msgstr "" -#: ../../content/applications/websites/livechat/responses.rst:66 -msgid "If an operator types `/helpdesk` in the chat window, the conversation is used to create a *Helpdesk* ticket." +#: ../../content/applications/websites/livechat/responses.rst:74 +msgid "If an operator types `/ticket` in the chat window, the conversation is used to create a *Helpdesk* ticket." msgstr "" -#: ../../content/applications/websites/livechat/responses.rst:70 -msgid "In version 16.3, the command to create a new ticket is `/ticket`. This only applies to databases running version 16.3." -msgstr "" - -#: ../../content/applications/websites/livechat/responses.rst:73 -msgid "After entering the `/helpdesk` command, type a title for the ticket into the chat window, then press `Enter`." +#: ../../content/applications/websites/livechat/responses.rst:77 +msgid "After entering the `/ticket` command, type a title for the ticket into the chat window, then press `Enter`." msgstr "" #: ../../content/applications/websites/livechat/responses.rst:-1 @@ -4206,32 +4225,28 @@ msgstr "" msgid "View of the results from a helpdesk search in a Live Chat conversation." msgstr "" -#: ../../content/applications/websites/livechat/responses.rst:80 +#: ../../content/applications/websites/livechat/responses.rst:84 msgid "The newly created ticket will be added to the *Helpdesk* team that has live chat enabled. If more than one team has live chat enabled, the ticket will automatically be assigned based on the team's priority." msgstr "" -#: ../../content/applications/websites/livechat/responses.rst:84 +#: ../../content/applications/websites/livechat/responses.rst:88 msgid "The transcript from the conversation will be added to the new ticket, under the :guilabel:`Description` tab." msgstr "" -#: ../../content/applications/websites/livechat/responses.rst:87 -msgid "To access the new ticket, click on the link in the chat window, or go to the :menuselection:`Helpdesk app` and click the :guilabel:`Tickets` button on the kanban card for the appropriate team." +#: ../../content/applications/websites/livechat/responses.rst:91 +msgid "To access the new ticket, click on the link in the chat window, or go to the :menuselection:`Helpdesk app`, and click the :guilabel:`Tickets` button on the Kanban card for the appropriate team." msgstr "" -#: ../../content/applications/websites/livechat/responses.rst:92 +#: ../../content/applications/websites/livechat/responses.rst:96 msgid "Search for a ticket from a live chat" msgstr "" -#: ../../content/applications/websites/livechat/responses.rst:94 -msgid "If an operator types `/helpdesk_search` in the chat window, they can search through *Helpdesk* tickets by ticket number or keyword." -msgstr "" - #: ../../content/applications/websites/livechat/responses.rst:98 -msgid "In version 16.3, the command to search through *Helpdesk* tickets is `/search_tickets`. This only applies to databases running version 16.3." +msgid "If an operator types `/search_tickets` in the chat window, they can search through *Helpdesk* tickets, either by ticket number or keyword." msgstr "" #: ../../content/applications/websites/livechat/responses.rst:101 -msgid "After entering the `/helpdesk_search` command, type a keyword or ticket number, then press `Enter`. If one or more related tickets are found, a list of links will be generated in the conversation window." +msgid "After entering the `/search_tickets` command, type a keyword or ticket number, then press :kbd:`Enter`. If one or more related tickets are found, a list of links is generated in the conversation window." msgstr "" #: ../../content/applications/websites/livechat/responses.rst:110 @@ -4243,7 +4258,7 @@ msgid "History" msgstr "" #: ../../content/applications/websites/livechat/responses.rst:115 -msgid "If an operator types `/history` in the chat window, it will generate a list of the most recent pages the visitor has viewed on the website (up to 15)." +msgid "Typing `/history` in the chat window generates a list of the most recent pages the visitor has viewed on the website (up to fifteen pages)." msgstr "" #: ../../content/applications/websites/livechat/responses.rst:-1 @@ -4303,38 +4318,42 @@ msgid "Canned responses" msgstr "" #: ../../content/applications/websites/livechat/responses.rst:163 -msgid "*Canned responses* are customizable inputs where a *shortcut* stands in for a longer response. An operator will enter the shortcut, and it will automatically be replaced by the expanded *substitution* response in the conversation." +msgid "*Canned responses* are customizable inputs, where a typed shortcut populates a longer response. A user enters a keyword *shortcut*, which is then automatically replaced by the expanded *substitution* response. The shortcut is the keyword or key phrase that is to be replaced. The substitution is the longer message that replaces the shortcut." msgstr "" -#: ../../content/applications/websites/livechat/responses.rst:168 +#: ../../content/applications/websites/livechat/responses.rst:171 msgid "Create canned responses" msgstr "" -#: ../../content/applications/websites/livechat/responses.rst:170 +#: ../../content/applications/websites/livechat/responses.rst:173 msgid "To create a new canned response, go to :menuselection:`Live Chat app --> Configuration --> Canned Responses --> New`." msgstr "" -#: ../../content/applications/websites/livechat/responses.rst:173 -msgid "From here, type the shortcut command into the :guilabel:`Shortcut` field." +#: ../../content/applications/websites/livechat/responses.rst:176 +msgid "Type a shortcut command in the :guilabel:`Shortcut` field. Next, click the :guilabel:`Substitution` field, and type the message that should replace the shortcut." msgstr "" -#: ../../content/applications/websites/livechat/responses.rst:175 -msgid "Then, click into the :guilabel:`Substitution` field, and enter the custom message that will be sent to visitors in place of the shortcut. Click :guilabel:`Save`." +#: ../../content/applications/websites/livechat/responses.rst:180 +msgid "Try to connect the shortcut to the topic of the substitution. Not only does this make it easier to use the responses, it prevents the list of responses from becoming disorganized and overwhelming." msgstr "" -#: ../../content/applications/websites/livechat/responses.rst:179 -msgid "Try to connect the shortcut to the topic of the substitution. The easier it is for the operators to remember, the easier it will be to use the canned responses in conversations." +#: ../../content/applications/websites/livechat/responses.rst:184 +msgid "In the :guilabel:`Description` field, add any information that provides context for this response, such as guidelines for when it should or should not be used." msgstr "" -#: ../../content/applications/websites/livechat/responses.rst:183 +#: ../../content/applications/websites/livechat/responses.rst:187 +msgid "The :guilabel:`Last Used` field keeps track of the date and time each response was most recently used. This field **cannot** be edited." +msgstr "" + +#: ../../content/applications/websites/livechat/responses.rst:191 msgid "Use canned responses in a live chat conversation" msgstr "" -#: ../../content/applications/websites/livechat/responses.rst:185 +#: ../../content/applications/websites/livechat/responses.rst:193 msgid "To use a canned response during a live chat conversation, type a colon (`:`) into the chat window, followed by the shortcut." msgstr "" -#: ../../content/applications/websites/livechat/responses.rst:189 +#: ../../content/applications/websites/livechat/responses.rst:197 msgid "An operator is chatting with a visitor. As soon as they type `:` they would see a list of available responses. They can manually select one from the list, or continue to type. If they want to use the canned response `'I am sorry to hear that.'`, they would type `:sorry`." msgstr "" @@ -4342,7 +4361,7 @@ msgstr "" msgid "View of a chat window and the use of a canned response in Odoo Live Chat." msgstr "" -#: ../../content/applications/websites/livechat/responses.rst:198 +#: ../../content/applications/websites/livechat/responses.rst:206 msgid "Typing `:` into a chat window on its own will generate a list of available canned responses. Responses can be manually selected from the list, in addition to the use of shortcuts." msgstr "" @@ -5009,7 +5028,7 @@ msgid "Odoo allows you to create multiple websites from the same database. This msgstr "" #: ../../content/applications/websites/website/configuration/multi_website.rst:11 -msgid "Each website can be designed and configured independently with its own :doc:`domain name `, :doc:`theme <../web_design/themes>`, :doc:`pages <../pages>`, :doc:`menus <../pages/menus>`, :doc:`languages `, :doc:`products <../../ecommerce/managing_products/products>`, assigned sales team, etc. They can also :ref:`share content and pages `." +msgid "Each website can be designed and configured independently with its own :doc:`domain name `, :doc:`theme <../web_design/themes>`, :doc:`pages <../pages>`, :doc:`menus <../pages/menus>`, :doc:`languages `, :doc:`products <../../ecommerce/products>`, assigned sales team, etc. They can also :ref:`share content and pages `." msgstr "" #: ../../content/applications/websites/website/configuration/multi_website.rst:18 @@ -5310,7 +5329,7 @@ msgstr "" #: ../../content/applications/websites/website/configuration/spam_protection.rst:72 #: ../../content/applications/websites/website/configuration/spam_protection.rst:127 -#: ../../content/applications/websites/website/configuration/translate.rst:95 +#: ../../content/applications/websites/website/configuration/translate.rst:60 msgid "Click :guilabel:`Save`." msgstr "" @@ -5415,137 +5434,125 @@ msgid "Translations" msgstr "" #: ../../content/applications/websites/website/configuration/translate.rst:5 -msgid "The contents of your website pages (i.e., text strings) can be translated into different languages directly on your website." +msgid "Your website is displayed in the language that matches your visitor’s browser. If the browser’s language has not been installed and added to your website, the content is shown in the :ref:`default language `. When additional languages are installed, users can choose their preferred language using the :ref:`language selector `." msgstr "" -#: ../../content/applications/websites/website/configuration/translate.rst:8 -msgid "Your website is displayed in the language that matches the visitor's browser's language, unless that particular language has not been installed. In this case, the website is displayed in the :ref:`default language `. The visitor can still select another language in the language menu." +#: ../../content/applications/websites/website/configuration/translate.rst:10 +msgid "The :ref:`Translate ` feature on your website allows automatic translation of standard terms and provides a tool for manual content translation." msgstr "" #: ../../content/applications/websites/website/configuration/translate.rst:14 -msgid "Installing languages" +msgid "Install languages" msgstr "" #: ../../content/applications/websites/website/configuration/translate.rst:16 -msgid "To translate your website, you first have to add the required languages:" +msgid "To allow translation of your website, you must first :doc:`install <../../../general/users/language>` the required languages and add them to your website. To do so, go to :menuselection:`Website --> Configuration --> Settings` and click :guilabel:`Install languages` in the :guilabel:`Website info` section. In the dialog box that opens, select the :guilabel:`Languages` you want from the dropdown menu, tick the required :guilabel:`Websites to translate`, and click :guilabel:`Add`." msgstr "" -#: ../../content/applications/websites/website/configuration/translate.rst:18 -msgid "Go to your website." -msgstr "" - -#: ../../content/applications/websites/website/configuration/translate.rst:19 -msgid "Scroll to the bottom of the page to the **language menu**." -msgstr "" - -#: ../../content/applications/websites/website/configuration/translate.rst:20 -msgid "Click the language and select :guilabel:`Add a language`." -msgstr "" - -#: ../../content/applications/websites/website/configuration/translate.rst:0 -msgid "Add a language to your website." -msgstr "" - -#: ../../content/applications/websites/website/configuration/translate.rst:25 -msgid "Click the :guilabel:`Languages` field and select the required language from the drop-down list. Repeat this step for each additional language." +#: ../../content/applications/websites/website/configuration/translate.rst:22 +msgid "To edit your website's languages, go to :menuselection:`Website –> Configuration –> Settings` and add/remove the required languages in/from the :guilabel:`Languages` field in the :guilabel:`Website info` section." msgstr "" #: ../../content/applications/websites/website/configuration/translate.rst:27 -msgid "Click the :guilabel:`Add` button." +msgid "Alternatively, once the languages have been installed, you can add them from the :ref:`language selector `. You might then need to refresh your page to see the new language." msgstr "" -#: ../../content/applications/websites/website/configuration/translate.rst:30 -msgid "You can also edit your website's languages from the backend, in the :guilabel:`Settings`. Go to :menuselection:`Website –> Configuration –> Settings` and add/remove the required languages in the :guilabel:`Languages` field, in the :guilabel:`Website info` section." -msgstr "" - -#: ../../content/applications/websites/website/configuration/translate.rst:37 +#: ../../content/applications/websites/website/configuration/translate.rst:34 msgid "Default language" msgstr "" -#: ../../content/applications/websites/website/configuration/translate.rst:39 -msgid "If the language of the visitor's browser is not installed on your website, the content is displayed in the default language." +#: ../../content/applications/websites/website/configuration/translate.rst:36 +msgid "When multiple languages are available on your website, you can set a default language to be used if the visitor’s browser language is not available. To do so, go to :menuselection:`Website –-> Configuration -–> Settings`, and select a language in the :guilabel:`Default` field." msgstr "" -#: ../../content/applications/websites/website/configuration/translate.rst:42 -msgid "To define a default language, go to :menuselection:`Website –> Configuration –> Settings`, and select a language in the :guilabel:`Default` field." +#: ../../content/applications/websites/website/configuration/translate.rst:41 +msgid "This field is only visible if multiple languages have been installed and added to your website." msgstr "" #: ../../content/applications/websites/website/configuration/translate.rst:46 -msgid "This field is visible only if multiple languages are already configured for your website." +msgid "Language selector" msgstr "" -#: ../../content/applications/websites/website/configuration/translate.rst:49 -msgid "Translating the contents" +#: ../../content/applications/websites/website/configuration/translate.rst:48 +msgid "Your website’s visitors can switch languages using the language selector, available by default in the :guilabel:`Copyright` section at the bottom of the page. To edit the language selector menu:" msgstr "" #: ../../content/applications/websites/website/configuration/translate.rst:51 -msgid "Once the languages have been added, you can translate the contents of your website. To do so, go to your website, select the language from the language menu and click the :guilabel:`Translate` button on the right part of the task bar to activate the **translation mode**." +msgid "Go to your website and click :guilabel:`Edit`;" msgstr "" -#: ../../content/applications/websites/website/configuration/translate.rst:-1 -msgid "Translate button" +#: ../../content/applications/websites/website/configuration/translate.rst:52 +msgid "Click the language selector available in the :guilabel:`Copyright` block and go to the :guilabel:`Copyright` section of the website builder;" msgstr "" -#: ../../content/applications/websites/website/configuration/translate.rst:58 -msgid "As a result:" -msgstr "" - -#: ../../content/applications/websites/website/configuration/translate.rst:60 -msgid "Text strings that have already been translated are highlighted in green;" -msgstr "" - -#: ../../content/applications/websites/website/configuration/translate.rst:61 -msgid "Text strings that need to be translated are highlighted in yellow." -msgstr "" - -#: ../../content/applications/websites/website/configuration/translate.rst:-1 -msgid "Text to be translated highlighted in yellow" -msgstr "" - -#: ../../content/applications/websites/website/configuration/translate.rst:66 -msgid "You can then replace the original text with the translation by clicking the block, editing its contents and saving." -msgstr "" - -#: ../../content/applications/websites/website/configuration/translate.rst:70 -msgid "Once the languages have been installed, you can also translate some items (e.g., the product's name and description) from the backend (e.g., in the product template). To do so, click the language code (e.g., :guilabel:`EN`) next to the text you want to translate (e.g., the product name) and add the translation." -msgstr "" - -#: ../../content/applications/websites/website/configuration/translate.rst:0 -msgid "Translate product-related items." -msgstr "" - -#: ../../content/applications/websites/website/configuration/translate.rst:78 -msgid "You can also :doc:`export/import translations <../../../../developer/howtos/translations>` to translate multiple items (e.g., product names and descriptions) in one go." -msgstr "" - -#: ../../content/applications/websites/website/configuration/translate.rst:82 -msgid "Language selector menu" -msgstr "" - -#: ../../content/applications/websites/website/configuration/translate.rst:84 -msgid "To add a language selector menu:" -msgstr "" - -#: ../../content/applications/websites/website/configuration/translate.rst:86 -msgid "Go to your website and click :guilabel:`Edit`." -msgstr "" - -#: ../../content/applications/websites/website/configuration/translate.rst:87 -msgid "Select the block where you want to add the language selector menu (e.g., the header)." -msgstr "" - -#: ../../content/applications/websites/website/configuration/translate.rst:88 -msgid "Select the :guilabel:`Customize` tab." -msgstr "" - -#: ../../content/applications/websites/website/configuration/translate.rst:89 -msgid "In the :guilabel:`Navbar` section, set the :guilabel:`Language selector` field to either :guilabel:`Dropdown` or :guilabel:`Inline`." +#: ../../content/applications/websites/website/configuration/translate.rst:54 +msgid "Set the :guilabel:`Language selector` field to either :guilabel:`Dropdown` or :guilabel:`Inline`. Click :guilabel:`None` if you do not want to display the :guilabel:`Language selector`;" msgstr "" #: ../../content/applications/websites/website/configuration/translate.rst:0 msgid "Add a language selector menu." msgstr "" +#: ../../content/applications/websites/website/configuration/translate.rst:63 +msgid "You can also add the :guilabel:`Language Selector` to the :guilabel:`Header` of your page. To do so, click the :guilabel:`Header` block and go to the :guilabel:`Navbar` section to edit the :guilabel:`Language Selector`." +msgstr "" + +#: ../../content/applications/websites/website/configuration/translate.rst:70 +msgid "Translate your website" +msgstr "" + +#: ../../content/applications/websites/website/configuration/translate.rst:72 +msgid "Select your desired language from the language selector to see your content in another language. Then, click the :guilabel:`Translate` button in the top-right corner to manually activate the translation mode so that you can translate what has not been translated automatically by Odoo." +msgstr "" + +#: ../../content/applications/websites/website/configuration/translate.rst:76 +msgid "Translated text strings are highlighted in green; text strings that were not translated automatically are highlighted in yellow." +msgstr "" + +#: ../../content/applications/websites/website/configuration/translate.rst:-1 +msgid "Entering the translation mode" +msgstr "" + +#: ../../content/applications/websites/website/configuration/translate.rst:82 +msgid "In this mode, you can only translate text. To change the page's structure, you must edit the master page, i.e., the page in the original language of the database. Any changes made to the master page are automatically applied to all translated versions." +msgstr "" + +#: ../../content/applications/websites/website/configuration/translate.rst:86 +msgid "To replace the original text with the translation, click the block, edit its contents, and save." +msgstr "" + +#: ../../content/applications/websites/website/configuration/translate.rst:89 +msgid "When a website supports multiple languages, the content is accessible through different URLs, depending on the language selected. For example, `https://www.mywebsite.com/shop/product/my-product-1` is the URL to the master page, in English, while `https://www.mywebsite.com/fr_FR/shop/product/mon-produit-1` is the URL to the French version of the same page." +msgstr "" + +#: ../../content/applications/websites/website/configuration/translate.rst:96 +msgid "Once the desired language is installed, you can translate some items from the backend (e.g., the product's name in the product form). To do so, click the language code (e.g., :guilabel:`EN`) next to the text you want to translate and add the translation." +msgstr "" + +#: ../../content/applications/websites/website/configuration/translate.rst:101 +msgid "Content visibility by language" +msgstr "" + +#: ../../content/applications/websites/website/configuration/translate.rst:103 +msgid "You can hide content (such as images or videos, for example) depending on the language. To do so:" +msgstr "" + +#: ../../content/applications/websites/website/configuration/translate.rst:105 +msgid "Click :guilabel:`Edit` and select an element of your website;" +msgstr "" + +#: ../../content/applications/websites/website/configuration/translate.rst:106 +msgid "Go to the :guilabel:`Text - Image` section and :guilabel:`Visibility`;" +msgstr "" + +#: ../../content/applications/websites/website/configuration/translate.rst:107 +msgid "Click :guilabel:`No condition` and select :guilabel:`Conditionally` instead;" +msgstr "" + +#: ../../content/applications/websites/website/configuration/translate.rst:108 +msgid "Go to :guilabel:`Languages` to configure the condition(s) to apply by selecting :guilabel:`Visible for` or :guilabel:`Hidden for`, and click :guilabel:`Choose a record` to decide which languages are impacted." +msgstr "" + #: ../../content/applications/websites/website/mail_groups.rst:3 msgid "Mail groups" msgstr "" @@ -6569,7 +6576,7 @@ msgid "Use the conditional visibility to display site elements to specific audie msgstr "" #: ../../content/applications/websites/website/reporting/link_tracker.rst:52 -msgid "For each parameter available in the :ref:`Visibility ` section, you can choose :guilabel:`Visible for` or :guilabel:`Hidden for` and select the record you want from the dropdown list." +msgid "For each parameter available in the :ref:`Visibility ` section, you can choose :guilabel:`Visible for` or :guilabel:`Hidden for` and select the record you want from the dropdown list." msgstr "" #: ../../content/applications/websites/website/reporting/link_tracker.rst:57 @@ -6609,54 +6616,54 @@ msgid "Building blocks" msgstr "" #: ../../content/applications/websites/website/web_design/building_blocks.rst:7 -msgid "Building blocks let you design your website quickly by dragging and dropping them onto your web pages. Four types of building blocks are available depending on their use: :guilabel:`Structure`, :guilabel:`Features`, :guilabel:`Dynamic Content`, and :guilabel:`Inner Content`." +msgid "Building blocks let you design your website quickly by dragging and dropping them onto your web pages. Four types of building blocks are available depending on their use: :doc:`Structure `, :doc:`Features `, :doc:`Dynamic Content `, and :doc:`Inner Content `." msgstr "" -#: ../../content/applications/websites/website/web_design/building_blocks.rst:12 -msgid "`Odoo Tutorial: Design your first webpage `_" +#: ../../content/applications/websites/website/web_design/building_blocks.rst:14 +msgid "`Odoo Tutorial: Design your first webpage `_" msgstr "" -#: ../../content/applications/websites/website/web_design/building_blocks.rst:15 +#: ../../content/applications/websites/website/web_design/building_blocks.rst:19 msgid "Adding a building block" msgstr "" -#: ../../content/applications/websites/website/web_design/building_blocks.rst:17 +#: ../../content/applications/websites/website/web_design/building_blocks.rst:21 msgid "To add a building block to your website page, click :guilabel:`Edit`, select the desired building block, and drag and drop it to your page. You can add as many blocks as needed." msgstr "" -#: ../../content/applications/websites/website/web_design/building_blocks.rst:20 +#: ../../content/applications/websites/website/web_design/building_blocks.rst:24 msgid "To edit the content of a building block, click on it and go to the :guilabel:`Customize` tab, where available features depend on the block you selected." msgstr "" -#: ../../content/applications/websites/website/web_design/building_blocks.rst:24 +#: ../../content/applications/websites/website/web_design/building_blocks.rst:28 msgid "Color preset and background" msgstr "" -#: ../../content/applications/websites/website/web_design/building_blocks.rst:26 +#: ../../content/applications/websites/website/web_design/building_blocks.rst:30 msgid "You can customize and apply color presets to building blocks. To proceed, select a building block, go to the :guilabel:`Customize` tab, click the :guilabel:`Background` button, and select a :guilabel:`Preset`." msgstr "" -#: ../../content/applications/websites/website/web_design/building_blocks.rst:30 +#: ../../content/applications/websites/website/web_design/building_blocks.rst:34 msgid "When you modify a color preset, all elements using it are automatically updated to match the new configuration." msgstr "" -#: ../../content/applications/websites/website/web_design/building_blocks.rst:34 +#: ../../content/applications/websites/website/web_design/building_blocks.rst:38 msgid ":doc:`Website themes `" msgstr "" -#: ../../content/applications/websites/website/web_design/building_blocks.rst:37 +#: ../../content/applications/websites/website/web_design/building_blocks.rst:41 msgid "Layout: grid and columns" msgstr "" -#: ../../content/applications/websites/website/web_design/building_blocks.rst:39 -msgid "You can choose between two layout styles for most building blocks: grid or columns (cols). To change the default layout, go to the :guilabel:`Customize` tab. Under the :guilabel:`Banner` section, select :guilabel:`Grid` or :guilabel:`Cols` as the :guilabel:`Layout`." +#: ../../content/applications/websites/website/web_design/building_blocks.rst:43 +msgid "You can choose between two layout styles for most building blocks: :ref:`grid ` or :ref:`columns (cols) `. To change the default layout, go to the :guilabel:`Customize` tab. Under the :guilabel:`Banner` section, select :guilabel:`Grid` or :guilabel:`Cols` as the :guilabel:`Layout`." msgstr "" -#: ../../content/applications/websites/website/web_design/building_blocks.rst:44 +#: ../../content/applications/websites/website/web_design/building_blocks.rst:51 msgid "Grid" msgstr "" -#: ../../content/applications/websites/website/web_design/building_blocks.rst:46 +#: ../../content/applications/websites/website/web_design/building_blocks.rst:53 msgid "The :guilabel:`Grid` layout allows you to reposition and resize elements, such as images or text, by dragging and dropping them." msgstr "" @@ -6664,7 +6671,7 @@ msgstr "" msgid "When the grid layout is selected, choose an image and drag and drop it where needed." msgstr "" -#: ../../content/applications/websites/website/web_design/building_blocks.rst:53 +#: ../../content/applications/websites/website/web_design/building_blocks.rst:60 msgid "Position images behind the text by using the above/below icons." msgstr "" @@ -6672,40 +6679,40 @@ msgstr "" msgid "Positioning an image behind text" msgstr "" -#: ../../content/applications/websites/website/web_design/building_blocks.rst:59 +#: ../../content/applications/websites/website/web_design/building_blocks.rst:68 msgid "Cols" msgstr "" -#: ../../content/applications/websites/website/web_design/building_blocks.rst:61 -msgid "Choosing the :guilabel:`Cols` layout allows you to determine the number of elements per line within the block." +#: ../../content/applications/websites/website/web_design/building_blocks.rst:70 +msgid "Choosing the :guilabel:`Cols` layout allows you to determine the number of elements per line within the block. To do so, select the block to modify, click the :guilabel:`Cols` :guilabel:`Layout`, and adjust the number." +msgstr "" + +#: ../../content/applications/websites/website/web_design/building_blocks.rst:74 +msgid "By default, **on mobile devices**, one element is visible per line to ensure that content remains easily readable and accessible on smaller screens. To adjust the value, click the :icon:`fa-mobile` (:guilabel:`mobile icon`) at the top of the website editor and adapt the number of columns." msgstr "" #: ../../content/applications/websites/website/web_design/building_blocks.rst:-1 -msgid "Setting the number columns" +msgid "Adjust the number of images per line on mobile view." msgstr "" -#: ../../content/applications/websites/website/web_design/building_blocks.rst:68 -msgid "On mobile devices, only one element per column is used by default for better visibility. You can adjust this value by using the :guilabel:`Mobile Preview` mode." -msgstr "" - -#: ../../content/applications/websites/website/web_design/building_blocks.rst:72 +#: ../../content/applications/websites/website/web_design/building_blocks.rst:82 #: ../../content/applications/websites/website/web_design/building_blocks.rst:-1 msgid "Duplicating a building block" msgstr "" -#: ../../content/applications/websites/website/web_design/building_blocks.rst:74 +#: ../../content/applications/websites/website/web_design/building_blocks.rst:84 msgid "You can duplicate a building block by clicking on the duplicate icon. Once duplicated, the new block appears on your website beneath the original one." msgstr "" -#: ../../content/applications/websites/website/web_design/building_blocks.rst:81 +#: ../../content/applications/websites/website/web_design/building_blocks.rst:91 msgid "Reordering a building block" msgstr "" -#: ../../content/applications/websites/website/web_design/building_blocks.rst:83 +#: ../../content/applications/websites/website/web_design/building_blocks.rst:93 msgid "To reorder a building block, select it and click the up arrow to move it before the previous block or click the down arrow to move it after." msgstr "" -#: ../../content/applications/websites/website/web_design/building_blocks.rst:86 +#: ../../content/applications/websites/website/web_design/building_blocks.rst:96 msgid "You can also use the drag-and-drop icon to move a block manually." msgstr "" @@ -6713,15 +6720,35 @@ msgstr "" msgid "Reordering building blocks" msgstr "" -#: ../../content/applications/websites/website/web_design/building_blocks.rst:94 +#: ../../content/applications/websites/website/web_design/building_blocks.rst:102 +msgid "Saving a custom building block" +msgstr "" + +#: ../../content/applications/websites/website/web_design/building_blocks.rst:104 +msgid "You can save a customized building block and reuse it elsewhere. To do so, select it, navigate to the :guilabel:`Customize` tab, and click the :icon:`fa-floppy-o` (:guilabel:`floppy disk`) icon to save it." +msgstr "" + +#: ../../content/applications/websites/website/web_design/building_blocks.rst:-1 +msgid "Saving a building block" +msgstr "" + +#: ../../content/applications/websites/website/web_design/building_blocks.rst:111 +msgid "Saved building blocks are available in the :guilabel:`Custom` section of the :guilabel:`Blocks` tab. Click the :icon:`fa-pencil` (:guilabel:`pen`) icon to edit their name." +msgstr "" + +#: ../../content/applications/websites/website/web_design/building_blocks.rst:-1 +msgid "Custom section with saved building blocks" +msgstr "" + +#: ../../content/applications/websites/website/web_design/building_blocks.rst:120 msgid "Visibility" msgstr "" -#: ../../content/applications/websites/website/web_design/building_blocks.rst:97 +#: ../../content/applications/websites/website/web_design/building_blocks.rst:123 msgid "Visibility on desktop/mobile" msgstr "" -#: ../../content/applications/websites/website/web_design/building_blocks.rst:99 +#: ../../content/applications/websites/website/web_design/building_blocks.rst:125 msgid "You can hide specific elements depending on the visitor's device. To do so, select the element to hide, and in the :guilabel:`Customize` tab, scroll down to :guilabel:`Visibility`, and click the :guilabel:`Show/Hide on Mobile` or the :guilabel:`Show/Hide on Desktop` icon." msgstr "" @@ -6729,52 +6756,48 @@ msgstr "" msgid "Click the \"show/hide on mobile\" icons to show or hide some elements on mobile." msgstr "" -#: ../../content/applications/websites/website/web_design/building_blocks.rst:107 -msgid "Click the phone icon at the top of the configurator to preview how your website would look on a mobile device." +#: ../../content/applications/websites/website/web_design/building_blocks.rst:133 +msgid "Click the :icon:`fa-mobile` (:guilabel:`mobile`) icon at the top of the configurator to preview how your website would look on a mobile device." msgstr "" #: ../../content/applications/websites/website/web_design/building_blocks.rst:0 msgid "Mobile phone preview icon" msgstr "" -#: ../../content/applications/websites/website/web_design/building_blocks.rst:114 +#: ../../content/applications/websites/website/web_design/building_blocks.rst:140 msgid "Conditional visibility" msgstr "" -#: ../../content/applications/websites/website/web_design/building_blocks.rst:116 +#: ../../content/applications/websites/website/web_design/building_blocks.rst:142 msgid "You can also hide or show building blocks using other conditions. To do so, select an element, go to :guilabel:`Visibility`, click :guilabel:`No condition`, and select :guilabel:`Conditionally` instead. Then, configure the condition(s) to apply by selecting :guilabel:`Visible for` or :guilabel:`Hidden for` and which :guilabel:`Records` will be impacted." msgstr "" -#: ../../content/applications/websites/website/web_design/building_blocks.rst:122 +#: ../../content/applications/websites/website/web_design/building_blocks.rst:148 msgid ":doc:`Link Tracker <../reporting/link_tracker>`" msgstr "" -#: ../../content/applications/websites/website/web_design/building_blocks.rst:125 +#: ../../content/applications/websites/website/web_design/building_blocks.rst:151 msgid "Invisible elements" msgstr "" -#: ../../content/applications/websites/website/web_design/building_blocks.rst:127 +#: ../../content/applications/websites/website/web_design/building_blocks.rst:153 msgid "Depending on the visibility settings, some elements can become hidden from your current view. To make a building block visible again, go to the :guilabel:`Invisible Elements` section at the bottom of the configurator and select a building block." msgstr "" -#: ../../content/applications/websites/website/web_design/building_blocks.rst:132 -msgid "Saving a custom building block" +#: ../../content/applications/websites/website/web_design/building_blocks.rst:158 +msgid "Mobile view customization" msgstr "" -#: ../../content/applications/websites/website/web_design/building_blocks.rst:134 -msgid "You can save a customized building block and reuse it elsewhere. To do so, select it, navigate to the :guilabel:`Customize` tab, and click the floppy disk icon to save it." +#: ../../content/applications/websites/website/web_design/building_blocks.rst:160 +msgid "You can customize building block elements for the mobile view without impacting the desktop view. To do so, open the website editor, click the :icon:`fa-mobile` (:guilabel:`mobile`) icon at the top, and select the building block element. Then, you can:" msgstr "" -#: ../../content/applications/websites/website/web_design/building_blocks.rst:-1 -msgid "Saving a building block" +#: ../../content/applications/websites/website/web_design/building_blocks.rst:164 +msgid "reorder the elements by clicking the :icon:`fa-angle-left` :icon:`fa-angle-right` (:guilabel:`left/right arrow`) icons;" msgstr "" -#: ../../content/applications/websites/website/web_design/building_blocks.rst:140 -msgid "Saved building blocks are available in the :guilabel:`Custom` section of the :guilabel:`Blocks` tab. Click the pen icon to edit their name." -msgstr "" - -#: ../../content/applications/websites/website/web_design/building_blocks.rst:-1 -msgid "Custom section with saved building blocks" +#: ../../content/applications/websites/website/web_design/building_blocks.rst:166 +msgid "edit the :ref:`Cols ` and :ref:`Visibility ` features in the :guilabel:`Customize` tab of the website editor." msgstr "" #: ../../content/applications/websites/website/web_design/building_blocks/dynamic_content.rst:3