NextERP/documentation
5
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

[I18N] *: export latest terms

Browse Source 
As per usual, leave off developer.pot and contributing.pot since we
don't translate them (not useful, can't really contribute to/dev in
Odoo without knowing English)

closes odoo/documentation#11326

X-original-commit: d683e94e85
Signed-off-by: Tiffany Chang (tic) <tic@odoo.com>
This commit is contained in:
Tiffany Chang (tic) 2024-11-04 09:01:36 +00:00
parent dc20497ab1
commit c05edbc9b2
9 changed files with 2223 additions and 1891 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

152
locale/sources/administration.pot
View File

@ -8,7 +8,7 @@ msgid ""
msgstr ""
"Project-Id-Version: Odoo 17.0\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2024-10-07 08:27+0000\n"
"POT-Creation-Date: 2024-11-04 11:48+0000\n"
"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
"Language-Team: LANGUAGE <LL@li.org>\n"
@ -994,7 +994,7 @@ msgid "Here is a pseudo-implementation example:"
msgstr ""
#: ../../content/administration/odoo_sh/advanced/submodules.rst:6
#: ../../content/administration/odoo_sh/getting_started/settings.rst:229
#: ../../content/administration/odoo_sh/getting_started/settings.rst:249
msgid "Submodules"
msgstr ""
@ -2936,122 +2936,154 @@ msgid "Production and staging builds are excluded, visitors can only see their s
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/settings.rst:221
msgid "Custom domains"
msgid "GitHub commit statuses"
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/settings.rst:223
msgid "To configure additional domains please refer to the corresponding branch's :ref:`settings tab <odoosh-gettingstarted-branches-tabs-settings>`."
msgid "This option enables Odoo.sh to push commit statuses to your GitHub repository when a build is created or updated. It requires a GitHub token with permissions to push commit statuses to the repository. Refer to `GitHub's documentation on personal access tokens <https://docs.github.com/en/authentication/keeping-your-account-and-data-secure/managing-your-personal-access-tokens>`_ for instructions to create yours."
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/settings.rst:231
msgid "Configure the deploy keys for the private repositories you use as submodules in your branches to allow Odoo.sh to download them."
#: ../../content/administration/odoo_sh/getting_started/settings.rst:229
msgid "GitHub's **fine-grained personal tokens** have an expiration date and will be disabled if they fail to update the commit status. You can replace the token at any time on Odoo.sh."
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/settings.rst:232
msgid "The commit statuses pushed to GitHub can have the following contexts:"
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/settings.rst:234
msgid ":guilabel:`ci/odoo.sh (dev)`: status of a development build"
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/settings.rst:235
msgid "These settings are required for **private repositories** only. If you are looking on how to set up your submodules, instructions are available in the chapter :ref:`Submodules <odoosh-advanced-submodules>` of this documentation."
msgid ":guilabel:`ci/odoo.sh (staging)`: status of a staging build"
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/settings.rst:242
msgid "When a repository is private, it is not possible to publicly download its branches and revisions. For that reason, you need to configure a deploy key for Odoo.sh, so the remote Git server allows our platform to download the revisions of this private repository."
#: ../../content/administration/odoo_sh/getting_started/settings.rst:236
msgid ":guilabel:`ci/odoo.sh (production)`: status of a production build"
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/settings.rst:247
msgid "To configure the deploy key for a private repository, proceed as follows:"
#: ../../content/administration/odoo_sh/getting_started/settings.rst:237
msgid ":guilabel:`ci/odoo.sh (test_ci)`: testing the token from the Settings page will push a test status on the last commit of your repository"
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/settings.rst:249
msgid "in the input, paste the SSH URL of your private sub-repository and click on *Add*,"
#: ../../content/administration/odoo_sh/getting_started/settings.rst:241
msgid "Custom domains"
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/settings.rst:243
msgid "To configure additional domains please refer to the corresponding branch's :ref:`settings tab <odoosh-gettingstarted-branches-tabs-settings>`."
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/settings.rst:251
msgid "e.g. *git@github.com:USERNAME/REPOSITORY.git*"
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/settings.rst:252
msgid "it can be another Git server than Github, such as Bitbucket, Gitlab or even your own self-hosted server"
msgid "Configure the deploy keys for the private repositories you use as submodules in your branches to allow Odoo.sh to download them."
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/settings.rst:255
msgid "copy the public key,"
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/settings.rst:257
msgid "it should look like *ssh-rsa some...random...characters...here...==*"
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/settings.rst:259
msgid "in the settings of the private sub-repository, add the public key amongst the deploy keys."
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/settings.rst:261
msgid "Github.com: :menuselection:`Settings --> Deploy keys --> Add deploy key`"
msgid "These settings are required for **private repositories** only. If you are looking on how to set up your submodules, instructions are available in the chapter :ref:`Submodules <odoosh-advanced-submodules>` of this documentation."
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/settings.rst:262
msgid "Bitbucket.com: :menuselection:`Settings --> Access keys --> Add key`"
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/settings.rst:263
msgid "Gitlab.com: :menuselection:`Settings --> Repository --> Deploy Keys`"
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/settings.rst:264
msgid "Self-hosted: append the key to the git user’s authorized_keys file in its .ssh directory"
msgid "When a repository is private, it is not possible to publicly download its branches and revisions. For that reason, you need to configure a deploy key for Odoo.sh, so the remote Git server allows our platform to download the revisions of this private repository."
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/settings.rst:267
msgid "Storage Size"
msgid "To configure the deploy key for a private repository, proceed as follows:"
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/settings.rst:269
msgid "This section shows the storage size used by your project."
msgid "in the input, paste the SSH URL of your private sub-repository and click on *Add*,"
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/settings.rst:274
msgid "Storage size is computed as follows:"
#: ../../content/administration/odoo_sh/getting_started/settings.rst:271
msgid "e.g. *git@github.com:USERNAME/REPOSITORY.git*"
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/settings.rst:276
msgid "the size of the PostgreSQL database"
#: ../../content/administration/odoo_sh/getting_started/settings.rst:272
msgid "it can be another Git server than Github, such as Bitbucket, Gitlab or even your own self-hosted server"
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/settings.rst:278
msgid "the size of the disk files available in your container: database filestore, sessions storage directory..."
#: ../../content/administration/odoo_sh/getting_started/settings.rst:275
msgid "copy the public key,"
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/settings.rst:277
msgid "it should look like *ssh-rsa some...random...characters...here...==*"
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/settings.rst:279
msgid "in the settings of the private sub-repository, add the public key amongst the deploy keys."
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/settings.rst:281
msgid "In case you want to analyze disk usage, you can run the tool `ncdu <https://dev.yorhel.nl/ncdu/man>`_ in your Web Shell."
msgid "Github.com: :menuselection:`Settings --> Deploy keys --> Add deploy key`"
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/settings.rst:282
msgid "Bitbucket.com: :menuselection:`Settings --> Access keys --> Add key`"
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/settings.rst:283
msgid "Gitlab.com: :menuselection:`Settings --> Repository --> Deploy Keys`"
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/settings.rst:284
msgid "Should your production database size grow to exceed what's provisioned in your subscription, it will automatically be synchronized with it."
msgid "Self-hosted: append the key to the git user’s authorized_keys file in its .ssh directory"
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/settings.rst:288
msgid "Database Workers"
#: ../../content/administration/odoo_sh/getting_started/settings.rst:287
msgid "Storage Size"
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/settings.rst:290
msgid "Additional database workers can be configured here. More workers help increase the load your production database is able to handle. If you add more, it will automatically be synchronized with your subscription."
#: ../../content/administration/odoo_sh/getting_started/settings.rst:289
msgid "This section shows the storage size used by your project."
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/settings.rst:294
msgid "Storage size is computed as follows:"
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/settings.rst:296
msgid "the size of the PostgreSQL database"
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/settings.rst:298
msgid "Adding more workers will not magically solve all performance issues. It only allows the server to handle more connections at the same time. If some operations are unusually slow, it's most likely a problem with the code, if it's not due to your own customizations you can open a ticket `here <https://www.odoo.com/help>`_."
msgid "the size of the disk files available in your container: database filestore, sessions storage directory..."
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/settings.rst:301
msgid "In case you want to analyze disk usage, you can run the tool `ncdu <https://dev.yorhel.nl/ncdu/man>`_ in your Web Shell."
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/settings.rst:304
msgid "Should your production database size grow to exceed what's provisioned in your subscription, it will automatically be synchronized with it."
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/settings.rst:308
msgid "Database Workers"
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/settings.rst:310
msgid "Additional database workers can be configured here. More workers help increase the load your production database is able to handle. If you add more, it will automatically be synchronized with your subscription."
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/settings.rst:318
msgid "Adding more workers will not magically solve all performance issues. It only allows the server to handle more connections at the same time. If some operations are unusually slow, it's most likely a problem with the code, if it's not due to your own customizations you can open a ticket `here <https://www.odoo.com/help>`_."
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/settings.rst:324
msgid "Staging Branches"
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/settings.rst:306
#: ../../content/administration/odoo_sh/getting_started/settings.rst:326
msgid "Additional staging branches allow you to develop and test more features at the same time. If you add more, it will automatically be synchronized with your subscription."
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/settings.rst:313
#: ../../content/administration/odoo_sh/getting_started/settings.rst:333
msgid "Activation"
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/settings.rst:315
#: ../../content/administration/odoo_sh/getting_started/settings.rst:335
msgid "Shows the status of the project's activation. You can change the project's activation code if needed."
msgstr ""
@ -3143,11 +3175,11 @@ msgid "As the update notification must be able to reach Odoo's subscription vali
msgstr ""
#: ../../content/administration/on_premise.rst:64
msgid "`services.odoo.com` on port `443` (or `80`)"
msgid "Odoo 18.0 and above: `services.odoo.com` on port `443` (or `80`)"
msgstr ""
#: ../../content/administration/on_premise.rst:65
msgid "for older deployments, `services.openerp.com` on port `443` (or `80`)"
msgid "Odoo 17.0 and below: `services.openerp.com` on port `443` (or `80`)"
msgstr ""
#: ../../content/administration/on_premise.rst:67

1436
locale/sources/finance.pot
View File

File diff suppressed because it is too large Load Diff

46
locale/sources/general.pot
View File

@ -8,7 +8,7 @@ msgid ""
msgstr ""
"Project-Id-Version: Odoo 17.0\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2024-09-24 10:43+0000\n"
"POT-Creation-Date: 2024-11-04 11:48+0000\n"
"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
"Language-Team: LANGUAGE <LL@li.org>\n"
@ -1972,7 +1972,7 @@ msgid "`CloudFlare DNS <https://support.cloudflare.com/hc/en-us/articles/3600190
msgstr ""
#: ../../content/applications/general/email_communication/email_domain.rst:144
msgid "`Google Domains <https://support.google.com/domains/answer/3290350?hl=en>`_"
msgid "`Squarespace DNS records <https://support.squarespace.com/hc/en-us/articles/360002101888-Adding-custom-DNS-records-to-your-Squarespace-managed-domain>`_"
msgstr ""
#: ../../content/applications/general/email_communication/email_domain.rst:145
@ -2366,6 +2366,46 @@ msgstr ""
msgid "These parameters are only used to prevent the creation of new records. They **do not prevent replies** from being added to the chatter."
msgstr ""
#: ../../content/applications/general/email_communication/email_servers_inbound.rst:322
msgid "Allow alias domain system parameter"
msgstr ""
#: ../../content/applications/general/email_communication/email_servers_inbound.rst:324
msgid "Incoming aliases are set in the Odoo database to create records by receiving incoming emails. To view aliases set in the Odoo database, first activate the :ref:`developer mode <developer-mode>`. Then, go to :menuselection:`Settings app --> Technical --> Aliases`."
msgstr ""
#: ../../content/applications/general/email_communication/email_servers_inbound.rst:328
msgid "The following system parameter, `mail.catchall.domain.allowed`, set with allowed alias domain values, separated by commas, filters out correctly addressed emails to aliases. Setting the domains for which the alias can create a ticket, lead, opportunity, etc., eliminates false positives where email addresses with only the prefix alias, not the domain, are present."
msgstr ""
#: ../../content/applications/general/email_communication/email_servers_inbound.rst:333
msgid "In some instances, matches have been made in the Odoo database when an email is received with the same alias prefix and a different domain on the incoming email address. This is true in the sender, recipient, and :abbr:`CC (Carbon Copy)` email addresses of an incoming email."
msgstr ""
#: ../../content/applications/general/email_communication/email_servers_inbound.rst:338
msgid "When Odoo receives emails with the `commercial` prefix alias in the sender, recipient, or :abbr:`CC (Carbon Copy)` email addresses (e.g. commercial\\@example.com), the database falsely treats the email as the full `commercial` alias, with a different domain, and therefore, creates a ticket/lead/opportunity/etc."
msgstr ""
#: ../../content/applications/general/email_communication/email_servers_inbound.rst:343
msgid "To add the `mail.catchall.domain.allowed` system parameter, first, activate the :ref:`developer mode <developer-mode>`. Then, go to :menuselection:`Settings app --> Technical --> System Parameters`. Click :guilabel:`New`. Then, type in `mail.catchall.domain.allowed` for the :guilabel:`Key` field."
msgstr ""
#: ../../content/applications/general/email_communication/email_servers_inbound.rst:347
msgid "Next, for the :guilabel:`Value` field, add the domains separated by commas. Manually :icon:`fa-cloud-upload` :guilabel:`(Save)`, and the system parameter takes immediate effect."
msgstr ""
#: ../../content/applications/general/email_communication/email_servers_inbound.rst:-1
msgid "mail.catchall.domain.allowed system parameter set."
msgstr ""
#: ../../content/applications/general/email_communication/email_servers_inbound.rst:354
msgid "Local-part based incoming detection"
msgstr ""
#: ../../content/applications/general/email_communication/email_servers_inbound.rst:356
msgid "When creating a new alias, there is an option to enable :guilabel:`Local-part based incoming detection`. If enabled, Odoo only requires the local-part to match for routing an incoming email. If this feature is turned off, Odoo requires the whole email address to match for routing an incoming email."
msgstr ""
#: ../../content/applications/general/email_communication/email_servers_outbound.rst:3
msgid "Manage outbound messages"
msgstr ""
@ -4985,7 +5025,7 @@ msgid "Edit the printer connected to the IoT box."
msgstr ""
#: ../../content/applications/general/iot/config/troubleshooting.rst:100
msgid "Epson and Star receipt printers and Zebra label printers do not need a driver to work. Make sure that no driver is selected for those printers."
msgid "Epson receipt printers and Zebra label printers do not need a driver to work. Make sure that no driver is selected for those printers."
msgstr ""
#: ../../content/applications/general/iot/config/troubleshooting.rst:104

273
locale/sources/hr.pot
View File

@ -8,7 +8,7 @@ msgid ""
msgstr ""
"Project-Id-Version: Odoo 17.0\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2024-10-07 08:27+0000\n"
"POT-Creation-Date: 2024-11-04 11:48+0000\n"
"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
"Language-Team: LANGUAGE <LL@li.org>\n"
@ -1169,7 +1169,7 @@ msgid "To filter the results in the overview dashboard, or to present different
msgstr ""
#: ../../content/applications/hr/attendances.rst:166
#: ../../content/applications/hr/payroll/reporting.rst:276
#: ../../content/applications/hr/payroll/reporting.rst:190
msgid "Filters"
msgstr ""
@ -7512,6 +7512,14 @@ msgstr ""
msgid ":doc:`payroll/reporting`"
msgstr ""
#: ../../content/applications/hr/payroll.rst:966
msgid ":doc:`payroll/work_entry_analysis`"
msgstr ""
#: ../../content/applications/hr/payroll.rst:967
msgid ":doc:`payroll/salary_attachment`"
msgstr ""
#: ../../content/applications/hr/payroll/contracts.rst:5
msgid "Every employee in Odoo is required to have a contract in order to be paid. A contract outlines the terms of an employee's position, their compensation, working hours, and any other details about their position."
msgstr ""
@ -8698,7 +8706,6 @@ msgid "To sort the entries by a specific column, such as :guilabel:`Net Wage`, c
msgstr ""
#: ../../content/applications/hr/payroll/reporting.rst:160
#: ../../content/applications/hr/payroll/reporting.rst:225
msgid "To export the data in an XLSX format, click the :guilabel:`Download xlsx` button, represented by a :guilabel:`⬇️ (down arrow above a horizontal bar)` icon, located at the far-right of the available icons. The information is then downloaded into a spreadsheet."
msgstr ""
@ -8715,106 +8722,22 @@ msgid "The view of data sent to a spreadsheet."
msgstr ""
#: ../../content/applications/hr/payroll/reporting.rst:181
msgid "If the *Documents* app is **not** installed, the :guilabel:`Insert in Spreadsheet` option places the newly-created spreadsheet in the *Dashboards* app."
msgid "If the **Documents** app is **not** installed, the :guilabel:`Insert in Spreadsheet` option places the newly-created spreadsheet in the **Dashboards** app."
msgstr ""
#: ../../content/applications/hr/payroll/reporting.rst:184
msgid "If the *Documents* application **is** installed, the spreadsheet has the option to be stored in either the *Dashboards* app or *Documents* app."
msgid "If the **Documents** application *is* installed, the spreadsheet has the option to be stored in either the **Dashboards** app or **Documents** app."
msgstr ""
#: ../../content/applications/hr/payroll/reporting.rst:188
msgid "Work entry analysis"
msgstr ""
#: ../../content/applications/hr/payroll/reporting.rst:190
msgid "The default :guilabel:`Work entry analysis` report provides an overview of the validated work entries for the current month. To view this report, navigate to :menuselection:`Payroll app --> Reporting --> Work Entry Analysis`."
msgstr ""
#: ../../content/applications/hr/payroll/reporting.rst:194
msgid "The work entries appear in a pivot table, with the default filters of `Current month: (Month)(Year)` and `Validated`. The various types of :doc:`work_entries` are listed on the left-hand side (x-axis), while the :guilabel:`Total` values appear along the top (the y-axis)."
msgstr ""
#: ../../content/applications/hr/payroll/reporting.rst:198
msgid "To change the displayed view, click the :guilabel:`➕ (plus)` icon next to the word :guilabel:`Total`, then click on one of the grouping options. The available options are :guilabel:`Work Entry Type`, :guilabel:`Employee`, and :guilabel:`Department`. If in a multi-company database, a :guilabel:`Company` option also appears."
msgstr ""
#: ../../content/applications/hr/payroll/reporting.rst:203
msgid "To add a new group to sort the data, click :guilabel:`Add Custom Group`, then click one of the presented options."
msgstr ""
#: ../../content/applications/hr/payroll/reporting.rst:207
msgid "Wherever a :guilabel:`➕ (plus)` icon appears on a pivot table, the information can be further grouped. Click on a :guilabel:`➕ (plus)` icon to reveal the available grouping options."
msgstr ""
#: ../../content/applications/hr/payroll/reporting.rst:210
msgid "Click on a :guilabel:`➖ (minus)` icon anywhere on the pivot table to remove that respective grouping."
msgstr ""
#: ../../content/applications/hr/payroll/reporting.rst:213
msgid "It is possible to compare the current :guilabel:`Work entry analysis` report to the previous month or the previous year. To view these comparisons, click the :guilabel:`⬇️ (down arrow)` icon in the search bar to reveal the various :ref:`filter <payroll/filters>` and grouping options."
msgstr ""
#: ../../content/applications/hr/payroll/reporting.rst:217
msgid "In the section titled :guilabel:`Comparison`, click on either :guilabel:`Current Month: Previous Period` or :guilabel:`Current Month: Previous Year`. The report updates and displays the previous time period values, as well as the :guilabel:`Variation` between the two."
msgstr ""
#: ../../content/applications/hr/payroll/reporting.rst:-1
msgid "A pivot table comparing the work entries of the current month and the previous month."
msgstr ""
#: ../../content/applications/hr/payroll/reporting.rst:229
msgid "The data can also be inserted into a spreadsheet. Click the :guilabel:`Insert in Spreadsheet` button and a :guilabel:`Select a spreadsheet to insert your (type of report)` pop-up window appears, asking which spreadsheet to place the information in. Select an existing spreadsheet or dashboard, or select a new :guilabel:`Blank spreadsheet`. Click the :guilabel:`Confirm` button to move to a spreadsheet view with the report added to it."
msgstr ""
#: ../../content/applications/hr/payroll/reporting.rst:236
msgid "The work entry analysis spreadsheet is :ref:`stored in the same locations <payroll/doc-storage>` as a pivot table."
msgstr ""
#: ../../content/applications/hr/payroll/reporting.rst:240
msgid "Salary attachment report"
msgstr ""
#: ../../content/applications/hr/payroll/reporting.rst:242
msgid "The :guilabel:`Salary Attachment Report` shows all deductions or allocations per employee, such as child support payments and wage garnishments. To view this report, navigate to :menuselection:`Payroll app --> Reporting --> Salary Attachment Report`."
msgstr ""
#: ../../content/applications/hr/payroll/reporting.rst:-1
msgid "View the Attachment of Salary report that shows all salary garnishments."
msgstr ""
#: ../../content/applications/hr/payroll/reporting.rst:250
msgid "The employees are listed in the left-side column, while the different deductions are listed in the top row, organized by deduction and monthly individual payslips."
msgstr ""
#: ../../content/applications/hr/payroll/reporting.rst:253
msgid "The report can be exported as an XLSX file, or inserted into a spreadsheet, using the corresponding buttons at the top."
msgstr ""
#: ../../content/applications/hr/payroll/reporting.rst:256
msgid "Click the :guilabel:`Measures` button to reveal the options of what data can be displayed. :guilabel:`Assignment of salary`, :guilabel:`Attachment of salary`, :guilabel:`Child support`, and :guilabel:`Count` can all be selected or deselected by clicking on the item. If an item has a checkmark next to it, that information is displayed."
msgstr ""
#: ../../content/applications/hr/payroll/reporting.rst:-1
msgid "Select the options to be displayed in the Salary Attachment Report."
msgstr ""
#: ../../content/applications/hr/payroll/reporting.rst:265
msgid "The :guilabel:`Salary Attachment Report` can be compared to the report for the previous time period or the previous year. To view these comparisons, click the :guilabel:`⬇️ (down arrow)` icon in the search bar to reveal the various :ref:`filter <payroll/filters>` and grouping options."
msgstr ""
#: ../../content/applications/hr/payroll/reporting.rst:269
msgid "In the section titled :guilabel:`Comparison`, click on either :guilabel:`Payslip End Date: Previous Period` or :guilabel:`Payslip End Date: Previous Year`. The report updates and displays the previous time period values, as well as the :guilabel:`Variation` between the two."
msgstr ""
#: ../../content/applications/hr/payroll/reporting.rst:278
#: ../../content/applications/hr/payroll/reporting.rst:192
msgid "At the top of each report, the default filters are shown inside the :guilabel:`Search...` box."
msgstr ""
#: ../../content/applications/hr/payroll/reporting.rst:280
#: ../../content/applications/hr/payroll/reporting.rst:194
msgid "Click the :guilabel:`⬇️ (down arrow)` icon in the search bar to display the available :guilabel:`Filters`. Filters show information that match the specific filter parameters."
msgstr ""
#: ../../content/applications/hr/payroll/reporting.rst:284
#: ../../content/applications/hr/payroll/reporting.rst:198
msgid "The :guilabel:`Work Entries Analysis` report has two default filters, the `Current month:(Month) (Year)` filter, and the `Validated` filter."
msgstr ""
@ -8822,38 +8745,106 @@ msgstr ""
msgid "Filters enabled for the Work Entries Analysis report."
msgstr ""
#: ../../content/applications/hr/payroll/reporting.rst:291
#: ../../content/applications/hr/payroll/reporting.rst:205
msgid "The :guilabel:`Payroll` report has only one default filter, the `Last 365 Days Payslip` filter."
msgstr ""
#: ../../content/applications/hr/payroll/reporting.rst:293
#: ../../content/applications/hr/payroll/reporting.rst:207
msgid "The :guilabel:`Salary Attachment Report` has only one default filter, the `Payslip End Date: (Year)` filter."
msgstr ""
#: ../../content/applications/hr/payroll/reporting.rst:296
#: ../../content/applications/hr/payroll/reporting.rst:210
msgid "All reports can include custom filters, or group information, by different metrics (employee, department, company, etc.)."
msgstr ""
#: ../../content/applications/hr/payroll/reporting.rst:299
#: ../../content/applications/hr/payroll/reporting.rst:213
msgid "Some reports have the option to compare the current report to the previous time period or year (a :guilabel:`Comparison` option)."
msgstr ""
#: ../../content/applications/hr/payroll/reporting.rst:302
#: ../../content/applications/hr/payroll/reporting.rst:216
msgid "Click on a parameter to select it and activate it. The report is immediately updated with the new parameters."
msgstr ""
#: ../../content/applications/hr/payroll/reporting.rst:305
#: ../../content/applications/hr/payroll/reporting.rst:219
msgid "The updated report can be set as a *favorite* report, meaning the parameters are stored for quick access in the future. To do that, click :guilabel:`Save the current search`, under the :guilabel:`Favorites` section, located in the search bar drop-down mega menu of filter options. Doing so reveals two options and a :guilabel:`Save` button."
msgstr ""
#: ../../content/applications/hr/payroll/reporting.rst:310
#: ../../content/applications/hr/payroll/reporting.rst:224
msgid "To set the current report as the default configuration when the report is accessed, check the box next to :guilabel:`Default filter`. If the current report should be accessible to everyone in the database, check the box next to :guilabel:`Share`."
msgstr ""
#: ../../content/applications/hr/payroll/reporting.rst:314
#: ../../content/applications/hr/payroll/reporting.rst:228
msgid "Finally, click :guilabel:`Save`, which saves the currently configured report. Then, it appears beneath the :guilabel:`Favorites` in the search bar drop-down mega menu of filter options."
msgstr ""
#: ../../content/applications/hr/payroll/salary_attachment.rst:3
msgid "Salary attachment report"
msgstr ""
#: ../../content/applications/hr/payroll/salary_attachment.rst:5
msgid "*Salary attachments* in Odoo refer to a portion of an employee's earnings that are designated for a specific purpose, both voluntary and involuntary. These can include contributions to a retirement plan, repayment of a loan, wage garnishments, or child support."
msgstr ""
#: ../../content/applications/hr/payroll/salary_attachment.rst:9
msgid "Voluntary salary attachments, such as repaying a loan, or contributing to a charity on a monthly basis, are considered *Assignments of Salary* in Odoo. Salary attachments that are required, such as a lawsuit settlement repayment, or repaying a tax lien, are considered *Attachments of Salary* in Odoo. Child support payments have their own category, and are simply referred to as *Child Support* in Odoo."
msgstr ""
#: ../../content/applications/hr/payroll/salary_attachment.rst:15
msgid "To view this report, navigate to :menuselection:`Payroll app --> Reporting --> Salary Attachment Report`. The :guilabel:`Salary Attachment Report` shows all deductions or allocations per employee, organized by payslip, in a default pivot table. The default filter is the end of the current year (:guilabel:`Payslip End Date: (year)`). The employees populate the rows, while the various deductions populate the columns, organized by type of deduction, and further grouped by individual payslip."
msgstr ""
#: ../../content/applications/hr/payroll/salary_attachment.rst:22
msgid "The default report contains **all** payslips for the current year, so the report typically contains a large number of columns. This could make it difficult to view all the data at once, as the report may be very wide and require scrolling to view all the data."
msgstr ""
#: ../../content/applications/hr/payroll/salary_attachment.rst:26
msgid "To view a condensed version of salary attachments, and have all the salary attachment columns visible on one page, click the :icon:`fa-minus-square-o` :guilabel:`Total` icon at the top of the report, above the various payslips."
msgstr ""
#: ../../content/applications/hr/payroll/salary_attachment.rst:30
msgid "This presents the salary attachments for the current year, and only displays three columns, :guilabel:`Attachment of Salary`, :guilabel:`Assignment of Salary`, and :guilabel:`Child Support.`"
msgstr ""
#: ../../content/applications/hr/payroll/salary_attachment.rst:33
msgid "Each entry displays the total amount paid for each specific type of salary attachment, for each employee."
msgstr ""
#: ../../content/applications/hr/payroll/salary_attachment.rst:-1
msgid "The Attachment of Salary report that shows all salary garnishments in a condensed view."
msgstr ""
#: ../../content/applications/hr/payroll/salary_attachment.rst:39
msgid "The report can be downloaded as an XLSX file, or :doc:`inserted into a spreadsheet <../../productivity/spreadsheet/insert>` using the corresponding buttons at the top."
msgstr ""
#: ../../content/applications/hr/payroll/salary_attachment.rst:42
msgid "Click the :guilabel:`Measures` button to reveal the options of what data is displayed. :guilabel:`Assignment of salary`, :guilabel:`Attachment of salary`, and :guilabel:`Child support` are all selected and visible, by default, while the :guilabel:`Count` option is not."
msgstr ""
#: ../../content/applications/hr/payroll/salary_attachment.rst:46
msgid "Click an option to either show or hide that particular metric. A :icon:`fa-check` :guilabel:`(checkmark)` icon indicates the data is visible."
msgstr ""
#: ../../content/applications/hr/payroll/salary_attachment.rst:50
msgid "Compare to previous year"
msgstr ""
#: ../../content/applications/hr/payroll/salary_attachment.rst:52
msgid "The :guilabel:`Salary Attachment Report` can be compared to the report for the previous time period or the previous year."
msgstr ""
#: ../../content/applications/hr/payroll/salary_attachment.rst:55
msgid "To view these comparisons, click the :icon:`fa-caret-down` :guilabel:`(down arrow)` icon in the search bar, then click either :guilabel:`Payslip End Date: Previous Period` or :guilabel:`Payslip End Date: Previous Year`, beneath the :icon:`fa-adjust` :guilabel:`Comparison` column."
msgstr ""
#: ../../content/applications/hr/payroll/salary_attachment.rst:59
msgid "The report updates and displays the current time period values, and the previous time period values, as well as the :guilabel:`Variation` between the two, in a percentage."
msgstr ""
#: ../../content/applications/hr/payroll/salary_attachment.rst:-1
msgid "The salary attachment report modified to compare to the previous year."
msgstr ""
#: ../../content/applications/hr/payroll/work_entries.rst:5
msgid "Work entries are created automatically in the *Payroll* app, based on the employee's :ref:`salary structure type <payroll/structure-types>`, and from the *Planning*, *Attendances*, and *Time Off* applications."
msgstr ""
@ -8919,7 +8910,7 @@ msgid ":guilabel:`Employee`: select the employee the work entry is for, using th
msgstr ""
#: ../../content/applications/hr/payroll/work_entries.rst:62
msgid ":guilabel:`Work Entry Type`: select the :ref:`work entry type <payroll/work-entries-config>` using the drop-down menu."
msgid ":guilabel:`Work Entry Type`: select the :ref:`work entry type <payroll/work-entries>` using the drop-down menu."
msgstr ""
#: ../../content/applications/hr/payroll/work_entries.rst:64
@ -9234,6 +9225,86 @@ msgstr ""
msgid ":ref:`Configure work entries <payroll/work-entries-config>`"
msgstr ""
#: ../../content/applications/hr/payroll/work_entry_analysis.rst:3
msgid "Work entry analysis"
msgstr ""
#: ../../content/applications/hr/payroll/work_entry_analysis.rst:5
msgid "The default *Work Entries Analysis* report provides an overview of the validated work entries for the current month. To view this report, navigate to :menuselection:`Payroll app --> Reporting --> Work Entry Analysis`."
msgstr ""
#: ../../content/applications/hr/payroll/work_entry_analysis.rst:9
msgid "The work entries appear in a pivot table, with the default filters of :guilabel:`Current month: (Month)(Year)` and :guilabel:`Validated`. The various types of :doc:`work_entries` populate the rows, while the :guilabel:`Total` values populate the only visible column."
msgstr ""
#: ../../content/applications/hr/payroll/work_entry_analysis.rst:13
msgid "To change the displayed information, click :icon:`fa-plus-square` :guilabel:`Total` above the main column, revealing a drop-down menu of available metrics. Click on one of the available groupings, and the data is further organized by that selected metric. The default options are :guilabel:`Work Entry Type`, :guilabel:`Employee`, and :guilabel:`Department`. If in a multi-company database, a :guilabel:`Company` option also appears."
msgstr ""
#: ../../content/applications/hr/payroll/work_entry_analysis.rst:20
msgid "Work entry analysis comparison"
msgstr ""
#: ../../content/applications/hr/payroll/work_entry_analysis.rst:22
msgid "It is possible to compare the work entries from one time period to a previous time period. To view this comparison, first navigate to :menuselection:`Payroll app --> Reporting --> Work Entry Analysis`."
msgstr ""
#: ../../content/applications/hr/payroll/work_entry_analysis.rst:26
msgid "Next, click the :icon:`fa-caret-down` :guilabel:`(down arrow)` icon in the search bar, revealing a drop-down menu. Under the :icon:`fa-adjust` :guilabel:`Comparison` section, click on either :guilabel:`Current Month: Previous Period` or :guilabel:`Current Month: Previous Year`."
msgstr ""
#: ../../content/applications/hr/payroll/work_entry_analysis.rst:30
msgid "The report updates and displays the data for the current time period, data for the selected previous time period, as well as the :guilabel:`Variation` between the two, in a percentage."
msgstr ""
#: ../../content/applications/hr/payroll/work_entry_analysis.rst:-1
msgid "A pivot table comparing the work entries of the current month and the previous month."
msgstr ""
#: ../../content/applications/hr/payroll/work_entry_analysis.rst:37
msgid "If no work entries for a specific :ref:`work entry type <payroll/work-entries>` are logged for the time period, it does **not** appear on the report. That does **not** mean the work entry type does not exist, or is not configured."
msgstr ""
#: ../../content/applications/hr/payroll/work_entry_analysis.rst:41
msgid "Additionally, if the default :guilabel:`Current month: (Month)(Year)` filter is removed from the search bar, the :guilabel:`Comparison` column does **not** appear; there must be a time-frame selected to view the :guilabel:`Comparison` column."
msgstr ""
#: ../../content/applications/hr/payroll/work_entry_analysis.rst:46
msgid "Use case: overtime report comparison"
msgstr ""
#: ../../content/applications/hr/payroll/work_entry_analysis.rst:48
msgid "It is possible to alter the *Work Entries Analysis* report to show a comparison of only overtime work entries, grouped by employee, for a specific time period. To view this data, first navigate to the default *Work entry analysis* report by going to :menuselection:`Payroll app --> Reporting --> Work Entry Analysis`."
msgstr ""
#: ../../content/applications/hr/payroll/work_entry_analysis.rst:53
msgid "Next, click the :icon:`fa-caret-down` :guilabel:`(down arrow)` icon in the search bar, revealing a drop-down menu. Under the :icon:`fa-filter` :guilabel:`Filters` column, click :guilabel:`Add Custom Filter`, and a :guilabel:`Add Custom Filter` pop-up window appears."
msgstr ""
#: ../../content/applications/hr/payroll/work_entry_analysis.rst:57
msgid "Using the drop-down menu, select :guilabel:`Work Entry Type` for the first field, leave the middle field as-is (with :guilabel:`is in` populating the field), and select :guilabel:`Overtime Hours` for the last field. Click :guilabel:`Add`, and all other work entry types disappear, and :guilabel:`Overtime Hours` appear in the sole row."
msgstr ""
#: ../../content/applications/hr/payroll/work_entry_analysis.rst:62
msgid "To compare overtime from the current month to the previous month, to see which month had more overtime logged, click the :icon:`fa-caret-down` :guilabel:`(down arrow)` icon again in the search bar. Under the :icon:`fa-adjust` :guilabel:`Comparison` section, click :guilabel:`Current Month: Previous Period`. Click away from the drop-down menu to close it."
msgstr ""
#: ../../content/applications/hr/payroll/work_entry_analysis.rst:67
msgid "Now, the report displays the :guilabel:`Overtime Hours` for the current month and the previous month, along with the :guilabel:`Variation`, in a percentage."
msgstr ""
#: ../../content/applications/hr/payroll/work_entry_analysis.rst:70
msgid "To view which employees received the most overtime, click :icon:`fa-plus-square` :guilabel:`Overtime Hours`, revealing a drop-down menu of options. Click :guilabel:`Employee`, and all employees with overtime work entries for either the current or previous month appears."
msgstr ""
#: ../../content/applications/hr/payroll/work_entry_analysis.rst:74
msgid "In this example, it can be determined that :guilabel:`Marc Demo` worked the most overtime in :guilabel:`August 2024`, whereas :guilabel:`Beth Evans` worked the most overtime hours in :guilabel:`September 2024`. Additionally, :guilabel:`Mitchell Admin` had the largest variation change, with a :guilabel:`-100%` change from :guilabel:`August 2024` to :guilabel:`September 2024`."
msgstr ""
#: ../../content/applications/hr/payroll/work_entry_analysis.rst:-1
msgid "A pivot table comparing the overtime from September 2024 with August 2024."
msgstr ""
#: ../../content/applications/hr/recruitment.rst:5
msgid "Recruitment"
msgstr ""

812
locale/sources/inventory_and_mrp.pot
View File

File diff suppressed because it is too large Load Diff

187
locale/sources/marketing.pot
View File

@ -8,7 +8,7 @@ msgid ""
msgstr ""
"Project-Id-Version: Odoo 17.0\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2024-08-21 11:43+0000\n"
"POT-Creation-Date: 2024-11-04 11:48+0000\n"
"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
"Language-Team: LANGUAGE <LL@li.org>\n"
@ -75,7 +75,7 @@ msgstr ""
#: ../../content/applications/marketing/email_marketing.rst:64
#: ../../content/applications/marketing/email_marketing.rst:736
#: ../../content/applications/marketing/social_marketing/social_posts.rst:52
#: ../../content/applications/marketing/surveys.rst:145
#: ../../content/applications/marketing/surveys.rst:172
msgid "List view"
msgstr ""
@ -7277,11 +7277,11 @@ msgstr ""
msgid "`Odoo Tutorials: Surveys <https://www.odoo.com/slides/surveys-62>`_"
msgstr ""
#: ../../content/applications/marketing/surveys.rst:19
#: ../../content/applications/marketing/surveys.rst:46
msgid "Dashboard"
msgstr ""
#: ../../content/applications/marketing/surveys.rst:21
#: ../../content/applications/marketing/surveys.rst:48
msgid "Upon opening the *Surveys* application, Odoo presents the main dashboard of the *Surveys* application, otherwise known as the :guilabel:`Surveys` page."
msgstr ""
@ -7289,87 +7289,87 @@ msgstr ""
msgid "The Odoo Surveys application dashboard in the default Kanban view."
msgstr ""
#: ../../content/applications/marketing/surveys.rst:29
#: ../../content/applications/marketing/surveys.rst:56
msgid "The *Surveys* dashboard can be accessed at any time throughout the application by clicking :menuselection:`Surveys` from the header menu."
msgstr ""
#: ../../content/applications/marketing/surveys.rst:32
#: ../../content/applications/marketing/surveys.rst:59
msgid "In the upper-left corner, there is a :guilabel:`New` button. When clicked, Odoo presents a blank survey form that can be used to create a survey."
msgstr ""
#: ../../content/applications/marketing/surveys.rst:35
#: ../../content/applications/marketing/surveys.rst:62
msgid "On the dashboard, all the surveys that have been created in the database are displayed in a default Kanban view."
msgstr ""
#: ../../content/applications/marketing/surveys.rst:38
#: ../../content/applications/marketing/surveys.rst:65
msgid "From left-to-right, after the survey name, the user who is responsible for it, and the month it was created, each line on the *Surveys* dashboard shows the following:"
msgstr ""
#: ../../content/applications/marketing/surveys.rst:41
#: ../../content/applications/marketing/surveys.rst:68
msgid "Number of :guilabel:`Questions` in that particular survey"
msgstr ""
#: ../../content/applications/marketing/surveys.rst:42
#: ../../content/applications/marketing/surveys.rst:69
msgid ":guilabel:`Average Duration` of the survey (how long it typically takes a participant to complete)"
msgstr ""
#: ../../content/applications/marketing/surveys.rst:43
#: ../../content/applications/marketing/surveys.rst:70
msgid "Number of :guilabel:`Registered` participants for the survey"
msgstr ""
#: ../../content/applications/marketing/surveys.rst:44
#: ../../content/applications/marketing/surveys.rst:71
msgid "Number of times that particular survey has been :guilabel:`Completed`"
msgstr ""
#: ../../content/applications/marketing/surveys.rst:45
#: ../../content/applications/marketing/surveys.rst:72
msgid "Percentage and data bar showcasing how many people have :guilabel:`Passed` or become :guilabel:`Certified`"
msgstr ""
#: ../../content/applications/marketing/surveys.rst:49
#: ../../content/applications/marketing/surveys.rst:76
msgid "The :guilabel:`Passed` percentage and bar **only** appears when a *Required Score* has been configured for that particular survey."
msgstr ""
#: ../../content/applications/marketing/surveys.rst:52
#: ../../content/applications/marketing/surveys.rst:79
msgid "The :guilabel:`Certified` percentage and bar **only** appears if that particular survey has the *Is a Certification* option enabled on the survey form."
msgstr ""
#: ../../content/applications/marketing/surveys.rst:55
#: ../../content/applications/marketing/surveys.rst:82
msgid "If neither :guilabel:`Passed` nor :guilabel:`Certified` appear on the line, that indicates the survey is without a *Required Score* and was not enabled with the *Is a Certification* option."
msgstr ""
#: ../../content/applications/marketing/surveys.rst:58
#: ../../content/applications/marketing/surveys.rst:85
msgid "Number of :guilabel:`Courses` related to that survey, which **only** appears if more than one course has been created and attached to a single survey"
msgstr ""
#: ../../content/applications/marketing/surveys.rst:62
#: ../../content/applications/marketing/surveys.rst:89
msgid "A half-trophy background image behind the survey name indicates that the survey is a *Certification*."
msgstr ""
#: ../../content/applications/marketing/surveys.rst:65
#: ../../content/applications/marketing/surveys.rst:92
msgid "To the far-right of those data points on the survey lines, located on the *Surveys* application dashboard, are a collection of buttons."
msgstr ""
#: ../../content/applications/marketing/surveys.rst:68
#: ../../content/applications/marketing/surveys.rst:95
msgid "Those buttons are as follows:"
msgstr ""
#: ../../content/applications/marketing/surveys.rst:70
#: ../../content/applications/marketing/surveys.rst:97
msgid ":guilabel:`Share`: click to reveal a :guilabel:`Share a Survey` pop-up form that can be used to invite potential participants to the survey - complete with a :guilabel:`Survey Link` that can be copied and sent to potential participants, and a :guilabel:`Send by Email` toggle switch."
msgstr ""
#: ../../content/applications/marketing/surveys.rst:74
#: ../../content/applications/marketing/surveys.rst:101
msgid "When the :guilabel:`Send by Email` toggle is active (green switch), additional fields appear, in which :guilabel:`Recipients`, :guilabel:`Additional Emails`, and a :guilabel:`Subject` can be added to the email."
msgstr ""
#: ../../content/applications/marketing/surveys.rst:78
#: ../../content/applications/marketing/surveys.rst:105
msgid "Below that, a dynamic email template, complete with a :guilabel:`Start Certification` button appears, which can be modified, as well, if needed."
msgstr ""
#: ../../content/applications/marketing/surveys.rst:81
#: ../../content/applications/marketing/surveys.rst:108
msgid ":guilabel:`Attachments` can be added to the email, as well as an :guilabel:`Answer deadline` can be set, if needed."
msgstr ""
#: ../../content/applications/marketing/surveys.rst:84
#: ../../content/applications/marketing/surveys.rst:111
#: ../../content/applications/marketing/surveys/create.rst:299
msgid "Once modifications are complete, click :guilabel:`Send` to send that email invite to all the email addresses/contacts listed in the :guilabel:`Recipients` field."
msgstr ""
@ -7379,59 +7379,59 @@ msgstr ""
msgid "The 'Share a Survey' pop-up window in Odoo Surveys with the Send by Email toggled on."
msgstr ""
#: ../../content/applications/marketing/surveys.rst:92
#: ../../content/applications/marketing/surveys.rst:119
msgid "The default :guilabel:`Mail Template` for survey invites can be edited by navigating to :menuselection:`Settings --> Technical --> Email Templates` and searching for `Survey: Invite`."
msgstr ""
#: ../../content/applications/marketing/surveys.rst:96
#: ../../content/applications/marketing/surveys.rst:123
msgid "The :guilabel:`Send by Email` toggle switch is **not** present when the survey line has zero questions."
msgstr ""
#: ../../content/applications/marketing/surveys.rst:99
#: ../../content/applications/marketing/surveys.rst:126
msgid "The :guilabel:`Survey Link` only appears when the survey's *Access Mode* is set to *Anyone with the link*."
msgstr ""
#: ../../content/applications/marketing/surveys.rst:102
#: ../../content/applications/marketing/surveys.rst:129
msgid "The :guilabel:`Additional Emails` field only appears when the survey's *Require Login* field is **not** active."
msgstr ""
#: ../../content/applications/marketing/surveys.rst:105
#: ../../content/applications/marketing/surveys.rst:132
msgid ":guilabel:`Test`: click to take a test version of the survey in a new tab, from the point-of-view of a survey participant, in order to check for any errors or inconsistencies."
msgstr ""
#: ../../content/applications/marketing/surveys.rst:107
#: ../../content/applications/marketing/surveys.rst:134
msgid ":guilabel:`See results`: click to reveal a new tab showcasing detailed metrics and graphical representations of all survey participants, questions, and responses for deeper analysis."
msgstr ""
#: ../../content/applications/marketing/surveys.rst:109
#: ../../content/applications/marketing/surveys.rst:136
msgid ":guilabel:`Start Live Session`: click to initiate a *Live session* survey, and reveal a session manager window in a new tab. This button is **not** present for surveys that have enabled the *Is a Certification* option on the survey form."
msgstr ""
#: ../../content/applications/marketing/surveys.rst:112
#: ../../content/applications/marketing/surveys.rst:139
msgid ":guilabel:`End Live Session`: click to end a *Live session* survey that has been officially started. This button option **only** appears on survey lines that have previously initiated a live session."
msgstr ""
#: ../../content/applications/marketing/surveys.rst:116
#: ../../content/applications/marketing/surveys.rst:143
msgid "Above the buttons that are located to the far-right of the survey lines, a :guilabel:`⋮ (three dots)` icon appears when the cursor hovers over that particular line. When the :guilabel:`⋮ (three dots)` icon is clicked, a drop-down menu with some configuration-related options appear:"
msgstr ""
#: ../../content/applications/marketing/surveys.rst:120
#: ../../content/applications/marketing/surveys.rst:147
msgid "The options are:"
msgstr ""
#: ../../content/applications/marketing/surveys.rst:122
#: ../../content/applications/marketing/surveys.rst:149
msgid ":guilabel:`Edit Survey`: when clicked, Odoo reveals the survey form for that particular survey, which can then be modified in a number of different ways."
msgstr ""
#: ../../content/applications/marketing/surveys.rst:124
#: ../../content/applications/marketing/surveys.rst:151
msgid ":guilabel:`Share`: when clicked, Odoo reveals the :guilabel:`Share a Survey` pop-up form that can be used to invite potential participants to the survey."
msgstr ""
#: ../../content/applications/marketing/surveys.rst:126
#: ../../content/applications/marketing/surveys.rst:153
msgid ":guilabel:`Delete`: when clicked, Odoo presents a pop-up window, wherein the user **must** confirm they want to delete the survey entirely, which they can do by clicking the :guilabel:`Delete` button at the bottom of the pop-up window."
msgstr ""
#: ../../content/applications/marketing/surveys.rst:129
#: ../../content/applications/marketing/surveys.rst:156
msgid ":guilabel:`Color`: users can opt to choose a color to add to the survey line on the dashboard for added organizational purposes, if needed."
msgstr ""
@ -7439,7 +7439,7 @@ msgstr ""
msgid "The three-dot drop-down menu of options that appears on the Odoo Surveys dashboard."
msgstr ""
#: ../../content/applications/marketing/surveys.rst:136
#: ../../content/applications/marketing/surveys.rst:163
msgid "Beneath the buttons that are located to the far-right of the survey lines, there is an *Activities* button, represented by a :guilabel:`🕘 (clock)` icon. When clicked, a mini pop-up window appears, from which activities related to that particular survey can be scheduled and customized."
msgstr ""
@ -7447,11 +7447,11 @@ msgstr ""
msgid "The Schedule Activities drop-down menu that appears on the Odoo Surveys dashboard."
msgstr ""
#: ../../content/applications/marketing/surveys.rst:147
#: ../../content/applications/marketing/surveys.rst:174
msgid "The *Surveys* dashboard is shown in the Kanban view, by default, but there is also a list view option available in the upper-right corner, represented by a :guilabel:`≣ (bars)` icon."
msgstr ""
#: ../../content/applications/marketing/surveys.rst:150
#: ../../content/applications/marketing/surveys.rst:177
msgid "When the :guilabel:`≣ (bars)` icon is clicked, the survey related data is displayed in a list view."
msgstr ""
@ -7459,43 +7459,43 @@ msgstr ""
msgid "The list view option located on the Odoo Surveys application dashboard."
msgstr ""
#: ../../content/applications/marketing/surveys.rst:156
#: ../../content/applications/marketing/surveys.rst:183
msgid "The columns shown on the *Surveys* app dashboard, while in list view, are as follows:"
msgstr ""
#: ../../content/applications/marketing/surveys.rst:158
#: ../../content/applications/marketing/surveys.rst:185
msgid ":guilabel:`Survey Title`"
msgstr ""
#: ../../content/applications/marketing/surveys.rst:159
#: ../../content/applications/marketing/surveys.rst:186
msgid ":guilabel:`Responsible`"
msgstr ""
#: ../../content/applications/marketing/surveys.rst:160
#: ../../content/applications/marketing/surveys.rst:187
msgid ":guilabel:`Average Duration`"
msgstr ""
#: ../../content/applications/marketing/surveys.rst:161
#: ../../content/applications/marketing/surveys.rst:188
msgid ":guilabel:`Registered`"
msgstr ""
#: ../../content/applications/marketing/surveys.rst:162
#: ../../content/applications/marketing/surveys.rst:189
msgid ":guilabel:`Success Ratio (%)`"
msgstr ""
#: ../../content/applications/marketing/surveys.rst:163
#: ../../content/applications/marketing/surveys.rst:190
msgid ":guilabel:`Avg Score (%)`"
msgstr ""
#: ../../content/applications/marketing/surveys.rst:166
#: ../../content/applications/marketing/surveys.rst:193
msgid "Additional columns can be added to the *Surveys* application dashboard, while in list view, by clicking the *additional options* drop-down menu, located to the far-right of the column titles, represented by a :guilabel:`(slider with two dots)` icon."
msgstr ""
#: ../../content/applications/marketing/surveys.rst:171
#: ../../content/applications/marketing/surveys.rst:198
msgid "Activities view"
msgstr ""
#: ../../content/applications/marketing/surveys.rst:173
#: ../../content/applications/marketing/surveys.rst:200
msgid "To have the *Surveys* application dashboard display nothing but the activities associated to the surveys in the database, click the :guilabel:`🕘 (clock)` icon to the far-right of the other view options, located in the upper-right corner."
msgstr ""
@ -7503,18 +7503,80 @@ msgstr ""
msgid "The activities view option located on the Odoo Surveys dashboard."
msgstr ""
#: ../../content/applications/marketing/surveys.rst:181
#: ../../content/applications/marketing/surveys.rst:208
msgid "Doing so reveals a table with rows and columns. The rows show the different surveys in the database, and the columns depict the various activity types."
msgstr ""
#: ../../content/applications/marketing/surveys.rst:185
#: ../../content/applications/marketing/surveys.rst:212
msgid "A new survey cannot be created in this view, as it is solely for the purpose of creating and viewing scheduled activities."
msgstr ""
#: ../../content/applications/marketing/surveys.rst:216
#: ../../content/applications/marketing/surveys/create.rst:3
msgid "Create surveys"
msgstr ""
#: ../../content/applications/marketing/surveys.rst:218
msgid "Learn about all the different options and configurations that can be utilized when creating a survey in Odoo."
msgstr ""
#: ../../content/applications/marketing/surveys.rst:222
msgid ":doc:`surveys/create`"
msgstr ""
#: ../../content/applications/marketing/surveys.rst:225
#: ../../content/applications/marketing/surveys/scoring.rst:3
msgid "Scoring surveys"
msgstr ""
#: ../../content/applications/marketing/surveys.rst:227
msgid "Discover how to measure a survey participant's performance, or overall satisfaction, with Odoo's detailed (and fully customizable) survey scoring options."
msgstr ""
#: ../../content/applications/marketing/surveys.rst:231
msgid ":doc:`surveys/scoring`"
msgstr ""
#: ../../content/applications/marketing/surveys.rst:234
#: ../../content/applications/marketing/surveys/questions.rst:3
#: ../../content/applications/marketing/surveys/questions.rst:64
msgid "Create questions"
msgstr ""
#: ../../content/applications/marketing/surveys.rst:236
msgid "With Odoo *Surveys*, there are many question types and options to choose from, providing the ability to create any kind of unique survey, questionnarire, and/or certification."
msgstr ""
#: ../../content/applications/marketing/surveys.rst:240
msgid ":doc:`surveys/questions`"
msgstr ""
#: ../../content/applications/marketing/surveys.rst:243
#: ../../content/applications/marketing/surveys/live_session.rst:3
msgid "Live Session surveys"
msgstr ""
#: ../../content/applications/marketing/surveys.rst:245
msgid "The *Live Session* survey option available in Odoo can enhance in-person demonstrations and presentations, where participants' real-time responses can be used to dictate where the conversation goes next."
msgstr ""
#: ../../content/applications/marketing/surveys.rst:250
msgid ":doc:`surveys/live_session`"
msgstr ""
#: ../../content/applications/marketing/surveys.rst:253
#: ../../content/applications/marketing/surveys/analysis.rst:3
msgid "Survey analysis"
msgstr ""
#: ../../content/applications/marketing/surveys.rst:255
msgid "Once the surveys start to come in, it is time to analyze the responses from your participants. Fortuantely, the in-depth reporting pages and options available in Odoo *Surveys* provide countless ways to examine everything related to surveys, and their submitted responses."
msgstr ""
#: ../../content/applications/marketing/surveys.rst:260
msgid ":doc:`surveys/analysis`"
msgstr ""
#: ../../content/applications/marketing/surveys/analysis.rst:5
msgid "After surveys have been created and sent to participants, it is only a matter of time before the responses start to come in. When they do, it is important to know where and how to analyze them in the Odoo *Surveys* application."
msgstr ""
@ -7806,10 +7868,6 @@ msgstr ""
msgid ":doc:`scoring`"
msgstr ""
#: ../../content/applications/marketing/surveys/create.rst:3
msgid "Create surveys"
msgstr ""
#: ../../content/applications/marketing/surveys/create.rst:5
msgid "To create a survey in the Odoo *Surveys* application, navigate to :menuselection:`Surveys app --> New` to reveal a blank survey form."
msgstr ""
@ -8193,10 +8251,6 @@ msgstr ""
msgid ":doc:`questions`"
msgstr ""
#: ../../content/applications/marketing/surveys/live_session.rst:3
msgid "Live Session surveys"
msgstr ""
#: ../../content/applications/marketing/surveys/live_session.rst:5
msgid "With the Odoo *Surveys* application, users can enhance in-person demonstrations and presentations with the *Live Session* feature."
msgstr ""
@ -8397,11 +8451,6 @@ msgstr ""
msgid "Repeat this process until the survey is complete."
msgstr ""
#: ../../content/applications/marketing/surveys/questions.rst:3
#: ../../content/applications/marketing/surveys/questions.rst:64
msgid "Create questions"
msgstr ""
#: ../../content/applications/marketing/surveys/questions.rst:5
msgid "In Odoo *Surveys*, crafting and tailoring survey questions is crucial for :doc:`creating and customizing surveys <../surveys/create>`."
msgstr ""
@ -8751,10 +8800,6 @@ msgstr ""
msgid "Survey text colors are directly linked to the colors used for the :doc:`website theme <../../websites/website/web_design/themes>`."
msgstr ""
#: ../../content/applications/marketing/surveys/scoring.rst:3
msgid "Scoring surveys"
msgstr ""
#: ../../content/applications/marketing/surveys/scoring.rst:5
msgid "To measure a survey participant's performance, knowledge, or overall satisfaction, Odoo ascribes points to survey answers. At the end of the survey, these points are summed up, resulting in the participant's final score."
msgstr ""

295
locale/sources/productivity.pot
View File

@ -8,7 +8,7 @@ msgid ""
msgstr ""
"Project-Id-Version: Odoo 17.0\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2024-10-07 08:27+0000\n"
"POT-Creation-Date: 2024-11-04 11:48+0000\n"
"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
"Language-Team: LANGUAGE <LL@li.org>\n"
@ -2401,7 +2401,7 @@ msgid "Three tabs are available: :ref:`Tags <documents/tags>`, :ref:`Access Righ
msgstr ""
#: ../../content/applications/productivity/documents.rst:58
#: ../../content/applications/productivity/sign.rst:290
#: ../../content/applications/productivity/sign.rst:293
msgid "Tags"
msgstr ""
@ -3695,254 +3695,258 @@ msgid "Document traceability and inalterability (any alteration made to a signed
msgstr ""
#: ../../content/applications/productivity/sign.rst:61
msgid ":doc:`Documentation for Germany <sign/germany>`"
msgstr ""
#: ../../content/applications/productivity/sign.rst:64
msgid "United States of America"
msgstr ""
#: ../../content/applications/productivity/sign.rst:63
#: ../../content/applications/productivity/sign.rst:66
msgid "The `ESIGN Act (Electronic Signatures in Global and National Commerce Act) <https://www.fdic.gov/regulations/compliance/manual/10/X-3.1.pdf>`_, at the interstate and international levels, and the `UETA (Uniform Electronic Transactions Act) <https://www.uniformlaws.org/committees/community-home/librarydocuments?communitykey=2c04b76c-2b7d-4399-977e-d5876ba7e034&tab=librarydocuments>`_, at the state level, provide the legal framework for electronic signatures. Note that `Illinois <https://www.ilga.gov/legislation/ilcs/ilcs5.asp?ActID=89&>`_ and `New York <https://its.ny.gov/electronic-signatures-and-records-act-esra>`_ have not adopted the UETA, but similar acts instead."
msgstr ""
#: ../../content/applications/productivity/sign.rst:72
#: ../../content/applications/productivity/sign.rst:75
msgid "Overall, to be recognized as valid, electronic signatures have to meet five criteria:"
msgstr ""
#: ../../content/applications/productivity/sign.rst:74
#: ../../content/applications/productivity/sign.rst:77
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:76
#: ../../content/applications/productivity/sign.rst:79
msgid "The signer must first express or imply their **consent to conduct business electronically**."
msgstr ""
#: ../../content/applications/productivity/sign.rst:77
#: ../../content/applications/productivity/sign.rst:80
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:79
#: ../../content/applications/productivity/sign.rst:82
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:81
#: ../../content/applications/productivity/sign.rst:84
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:86
#: ../../content/applications/productivity/sign.rst:89
msgid "Other countries"
msgstr ""
#: ../../content/applications/productivity/sign.rst:88
#: ../../content/applications/productivity/sign.rst:91
msgid ":doc:`Algeria <sign/algeria>`"
msgstr ""
#: ../../content/applications/productivity/sign.rst:89
#: ../../content/applications/productivity/sign.rst:92
msgid ":doc:`Angola <sign/angola>`"
msgstr ""
#: ../../content/applications/productivity/sign.rst:90
#: ../../content/applications/productivity/sign.rst:93
msgid ":doc:`Argentina <sign/argentina>`"
msgstr ""
#: ../../content/applications/productivity/sign.rst:91
#: ../../content/applications/productivity/sign.rst:94
msgid ":doc:`Australia <sign/australia>`"
msgstr ""
#: ../../content/applications/productivity/sign.rst:92
#: ../../content/applications/productivity/sign.rst:95
msgid ":doc:`Azerbaijan <sign/azerbaijan>`"
msgstr ""
#: ../../content/applications/productivity/sign.rst:93
#: ../../content/applications/productivity/sign.rst:96
msgid ":doc:`Bangladesh <sign/bangladesh>`"
msgstr ""
#: ../../content/applications/productivity/sign.rst:94
#: ../../content/applications/productivity/sign.rst:97
msgid ":doc:`Brazil <sign/brazil>`"
msgstr ""
#: ../../content/applications/productivity/sign.rst:95
#: ../../content/applications/productivity/sign.rst:98
msgid ":doc:`Canada <sign/canada>`"
msgstr ""
#: ../../content/applications/productivity/sign.rst:96
#: ../../content/applications/productivity/sign.rst:99
msgid ":doc:`Chile <sign/chile>`"
msgstr ""
#: ../../content/applications/productivity/sign.rst:97
#: ../../content/applications/productivity/sign.rst:100
msgid ":doc:`China <sign/china>`"
msgstr ""
#: ../../content/applications/productivity/sign.rst:98
#: ../../content/applications/productivity/sign.rst:101
msgid ":doc:`Colombia <sign/colombia>`"
msgstr ""
#: ../../content/applications/productivity/sign.rst:99
#: ../../content/applications/productivity/sign.rst:102
msgid ":doc:`Dominican Republic <sign/dominican_republic>`"
msgstr ""
#: ../../content/applications/productivity/sign.rst:100
#: ../../content/applications/productivity/sign.rst:103
msgid ":doc:`Ecuador <sign/ecuador>`"
msgstr ""
#: ../../content/applications/productivity/sign.rst:101
#: ../../content/applications/productivity/sign.rst:104
msgid ":doc:`Egypt <sign/egypt>`"
msgstr ""
#: ../../content/applications/productivity/sign.rst:102
#: ../../content/applications/productivity/sign.rst:105
msgid ":doc:`Ethiopia <sign/ethiopia>`"
msgstr ""
#: ../../content/applications/productivity/sign.rst:103
#: ../../content/applications/productivity/sign.rst:106
msgid ":doc:`Guatemala <sign/guatemala>`"
msgstr ""
#: ../../content/applications/productivity/sign.rst:104
#: ../../content/applications/productivity/sign.rst:107
msgid ":doc:`Hong Kong <sign/hong_kong>`"
msgstr ""
#: ../../content/applications/productivity/sign.rst:105
#: ../../content/applications/productivity/sign.rst:108
msgid ":doc:`India <sign/india>`"
msgstr ""
#: ../../content/applications/productivity/sign.rst:106
#: ../../content/applications/productivity/sign.rst:109
msgid ":doc:`Indonesia <sign/indonesia>`"
msgstr ""
#: ../../content/applications/productivity/sign.rst:107
#: ../../content/applications/productivity/sign.rst:110
msgid ":doc:`Iran <sign/iran>`"
msgstr ""
#: ../../content/applications/productivity/sign.rst:108
#: ../../content/applications/productivity/sign.rst:111
msgid ":doc:`Iraq <sign/iraq>`"
msgstr ""
#: ../../content/applications/productivity/sign.rst:109
#: ../../content/applications/productivity/sign.rst:112
msgid ":doc:`Israel <sign/israel>`"
msgstr ""
#: ../../content/applications/productivity/sign.rst:110
#: ../../content/applications/productivity/sign.rst:113
msgid ":doc:`Japan <sign/japan>`"
msgstr ""
#: ../../content/applications/productivity/sign.rst:111
#: ../../content/applications/productivity/sign.rst:114
msgid ":doc:`Kazakhstan <sign/kazakhstan>`"
msgstr ""
#: ../../content/applications/productivity/sign.rst:112
#: ../../content/applications/productivity/sign.rst:115
msgid ":doc:`Kenya <sign/kenya>`"
msgstr ""
#: ../../content/applications/productivity/sign.rst:113
#: ../../content/applications/productivity/sign.rst:116
msgid ":doc:`Kuwait <sign/kuwait>`"
msgstr ""
#: ../../content/applications/productivity/sign.rst:114
#: ../../content/applications/productivity/sign.rst:117
msgid ":doc:`Malaysia <sign/malaysia>`"
msgstr ""
#: ../../content/applications/productivity/sign.rst:115
#: ../../content/applications/productivity/sign.rst:118
msgid ":doc:`Mexico <sign/mexico>`"
msgstr ""
#: ../../content/applications/productivity/sign.rst:116
#: ../../content/applications/productivity/sign.rst:119
msgid ":doc:`Morocco <sign/morocco>`"
msgstr ""
#: ../../content/applications/productivity/sign.rst:117
#: ../../content/applications/productivity/sign.rst:120
msgid ":doc:`New Zealand <sign/new_zealand>`"
msgstr ""
#: ../../content/applications/productivity/sign.rst:118
#: ../../content/applications/productivity/sign.rst:121
msgid ":doc:`Nigeria <sign/nigeria>`"
msgstr ""
#: ../../content/applications/productivity/sign.rst:119
#: ../../content/applications/productivity/sign.rst:122
msgid ":doc:`Norway <sign/norway>`"
msgstr ""
#: ../../content/applications/productivity/sign.rst:120
#: ../../content/applications/productivity/sign.rst:123
msgid ":doc:`Oman <sign/oman>`"
msgstr ""
#: ../../content/applications/productivity/sign.rst:121
#: ../../content/applications/productivity/sign.rst:124
msgid ":doc:`Pakistan <sign/pakistan>`"
msgstr ""
#: ../../content/applications/productivity/sign.rst:122
#: ../../content/applications/productivity/sign.rst:125
msgid ":doc:`Peru <sign/peru>`"
msgstr ""
#: ../../content/applications/productivity/sign.rst:123
#: ../../content/applications/productivity/sign.rst:126
msgid ":doc:`Philippines <sign/philippines>`"
msgstr ""
#: ../../content/applications/productivity/sign.rst:124
#: ../../content/applications/productivity/sign.rst:127
msgid ":doc:`Qatar <sign/qatar>`"
msgstr ""
#: ../../content/applications/productivity/sign.rst:125
#: ../../content/applications/productivity/sign.rst:128
msgid ":doc:`Russia <sign/russia>`"
msgstr ""
#: ../../content/applications/productivity/sign.rst:126
#: ../../content/applications/productivity/sign.rst:129
msgid ":doc:`Saudi Arabia <sign/saudi_arabia>`"
msgstr ""
#: ../../content/applications/productivity/sign.rst:127
#: ../../content/applications/productivity/sign.rst:130
msgid ":doc:`Singapore <sign/singapore>`"
msgstr ""
#: ../../content/applications/productivity/sign.rst:128
#: ../../content/applications/productivity/sign.rst:131
msgid ":doc:`South Africa <sign/south_africa>`"
msgstr ""
#: ../../content/applications/productivity/sign.rst:129
#: ../../content/applications/productivity/sign.rst:132
msgid ":doc:`South Korea <sign/south_korea>`"
msgstr ""
#: ../../content/applications/productivity/sign.rst:130
#: ../../content/applications/productivity/sign.rst:133
msgid ":doc:`Switzerland <sign/switzerland>`"
msgstr ""
#: ../../content/applications/productivity/sign.rst:131
#: ../../content/applications/productivity/sign.rst:134
msgid ":doc:`Thailand <sign/thailand>`"
msgstr ""
#: ../../content/applications/productivity/sign.rst:132
#: ../../content/applications/productivity/sign.rst:135
msgid ":doc:`Turkey <sign/turkey>`"
msgstr ""
#: ../../content/applications/productivity/sign.rst:133
#: ../../content/applications/productivity/sign.rst:136
msgid ":doc:`Ukraine <sign/ukraine>`"
msgstr ""
#: ../../content/applications/productivity/sign.rst:134
#: ../../content/applications/productivity/sign.rst:137
msgid ":doc:`United Arab Emirates <sign/united_arab_emirates>`"
msgstr ""
#: ../../content/applications/productivity/sign.rst:135
#: ../../content/applications/productivity/sign.rst:138
msgid ":doc:`United Kingdom <sign/united_kingdom>`"
msgstr ""
#: ../../content/applications/productivity/sign.rst:136
#: ../../content/applications/productivity/sign.rst:139
msgid ":doc:`Uzbekistan <sign/uzbekistan>`"
msgstr ""
#: ../../content/applications/productivity/sign.rst:137
#: ../../content/applications/productivity/sign.rst:140
msgid ":doc:`Vietnam <sign/vietnam>`"
msgstr ""
#: ../../content/applications/productivity/sign.rst:140
#: ../../content/applications/productivity/sign.rst:143
msgid "Send a document to sign"
msgstr ""
#: ../../content/applications/productivity/sign.rst:143
#: ../../content/applications/productivity/sign.rst:146
msgid "One-time signature"
msgstr ""
#: ../../content/applications/productivity/sign.rst:145
#: ../../content/applications/productivity/sign.rst:148
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 <sign/fields>` in your document. You can modify the :ref:`role <sign/role>` assigned to a field by clicking on it and selecting the one you want."
msgstr ""
#: ../../content/applications/productivity/sign.rst:150
#: ../../content/applications/productivity/sign.rst:153
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 ""
@ -3950,84 +3954,84 @@ msgstr ""
msgid "Signature status"
msgstr ""
#: ../../content/applications/productivity/sign.rst:158
#: ../../content/applications/productivity/sign.rst:161
msgid "Validity dates and reminders"
msgstr ""
#: ../../content/applications/productivity/sign.rst:160
#: ../../content/applications/productivity/sign.rst:163
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:166
#: ../../content/applications/productivity/sign.rst:169
#: ../../content/applications/productivity/spreadsheet/templates.rst:3
msgid "Templates"
msgstr ""
#: ../../content/applications/productivity/sign.rst:168
#: ../../content/applications/productivity/sign.rst:171
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 <sign/fields>`. You can modify the :ref:`role <sign/role>` of a field by clicking on it and selecting the one you want."
msgstr ""
#: ../../content/applications/productivity/sign.rst:173
#: ../../content/applications/productivity/sign.rst:176
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:179
#: ../../content/applications/productivity/sign.rst:182
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:184
#: ../../content/applications/productivity/sign.rst:187
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:193
#: ../../content/applications/productivity/sign.rst:196
msgid "Roles"
msgstr ""
#: ../../content/applications/productivity/sign.rst:195
#: ../../content/applications/productivity/sign.rst:198
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:199
#: ../../content/applications/productivity/sign.rst:202
msgid "Roles are available by going to :menuselection:`Sign --> Configuration --> Roles`."
msgstr ""
#: ../../content/applications/productivity/sign.rst:201
#: ../../content/applications/productivity/sign.rst:204
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:209
#: ../../content/applications/productivity/sign.rst:212
msgid "Secured identification"
msgstr ""
#: ../../content/applications/productivity/sign.rst:211
#: ../../content/applications/productivity/sign.rst:214
msgid "As the owner of a document, you may request an :guilabel:`Extra Authentication Step` through :ref:`SMS verification <sign/sms>` or via :ref:`Itsme® <sign/itsme>` (available in Belgium and the Netherlands). Both authentication options require :ref:`credits <iap/buying_credits>`. If you do not have any credits left, the authentication steps will be skipped."
msgstr ""
#: ../../content/applications/productivity/sign.rst:217
#: ../../content/applications/productivity/sign.rst:220
msgid ":doc:`In-App Purchase (IAP) <../essentials/in_app_purchase>`"
msgstr ""
#: ../../content/applications/productivity/sign.rst:218
#: ../../content/applications/productivity/sign.rst:221
msgid ":doc:`SMS pricing and FAQ <../marketing/sms_marketing/pricing_and_faq>`"
msgstr ""
#: ../../content/applications/productivity/sign.rst:223
#: ../../content/applications/productivity/sign.rst:226
msgid "SMS verification"
msgstr ""
#: ../../content/applications/productivity/sign.rst:225
#: ../../content/applications/productivity/sign.rst:228
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:229
#: ../../content/applications/productivity/sign.rst:232
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:233
#: ../../content/applications/productivity/sign.rst:236
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:237
#: ../../content/applications/productivity/sign.rst:240
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 ""
@ -4035,27 +4039,27 @@ msgstr ""
msgid "Add a hash to your document"
msgstr ""
#: ../../content/applications/productivity/sign.rst:245
#: ../../content/applications/productivity/sign.rst:248
msgid "This feature is enabled by default."
msgstr ""
#: ../../content/applications/productivity/sign.rst:246
#: ../../content/applications/productivity/sign.rst:249
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:252
#: ../../content/applications/productivity/sign.rst:255
msgid "Itsme®"
msgstr ""
#: ../../content/applications/productivity/sign.rst:254
#: ../../content/applications/productivity/sign.rst:257
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:257
#: ../../content/applications/productivity/sign.rst:260
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:262
#: ../../content/applications/productivity/sign.rst:265
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 ""
@ -4063,19 +4067,19 @@ msgstr ""
msgid "select customer identified with itsme®"
msgstr ""
#: ../../content/applications/productivity/sign.rst:268
#: ../../content/applications/productivity/sign.rst:271
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:273
#: ../../content/applications/productivity/sign.rst:276
msgid "Signatory hash"
msgstr ""
#: ../../content/applications/productivity/sign.rst:275
#: ../../content/applications/productivity/sign.rst:278
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:280
#: ../../content/applications/productivity/sign.rst:283
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 ""
@ -4083,31 +4087,31 @@ msgstr ""
msgid "Adding the visual security frame to a signature."
msgstr ""
#: ../../content/applications/productivity/sign.rst:292
#: ../../content/applications/productivity/sign.rst:295
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:295
#: ../../content/applications/productivity/sign.rst:298
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:299
#: ../../content/applications/productivity/sign.rst:302
msgid "To apply a tag to a document, use the dropdown list available in your document."
msgstr ""
#: ../../content/applications/productivity/sign.rst:302
#: ../../content/applications/productivity/sign.rst:305
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:307
#: ../../content/applications/productivity/sign.rst:310
msgid "Sign order"
msgstr ""
#: ../../content/applications/productivity/sign.rst:309
#: ../../content/applications/productivity/sign.rst:312
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:312
#: ../../content/applications/productivity/sign.rst:315
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` switch 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 ""
@ -4115,71 +4119,71 @@ msgstr ""
msgid "Toggle the switch to specify the signing order."
msgstr ""
#: ../../content/applications/productivity/sign.rst:320
#: ../../content/applications/productivity/sign.rst:323
msgid "Each recipient receives the signature request notification only once the previous recipient has completed their action."
msgstr ""
#: ../../content/applications/productivity/sign.rst:326
#: ../../content/applications/productivity/sign.rst:329
msgid "Field types"
msgstr ""
#: ../../content/applications/productivity/sign.rst:328
#: ../../content/applications/productivity/sign.rst:331
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:332
#: ../../content/applications/productivity/sign.rst:335
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:336
#: ../../content/applications/productivity/sign.rst:339
msgid "To create and edit field types, go to :menuselection:`Sign --> Configuration --> Settings --> Edit field types`."
msgstr ""
#: ../../content/applications/productivity/sign.rst:339
#: ../../content/applications/productivity/sign.rst:342
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:342
#: ../../content/applications/productivity/sign.rst:345
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:345
#: ../../content/applications/productivity/sign.rst:348
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:347
#: ../../content/applications/productivity/sign.rst:350
msgid ":guilabel:`Text`: users enter text on a single line."
msgstr ""
#: ../../content/applications/productivity/sign.rst:348
#: ../../content/applications/productivity/sign.rst:351
msgid ":guilabel:`Multiline Text`: users enter text on multiple lines."
msgstr ""
#: ../../content/applications/productivity/sign.rst:349
#: ../../content/applications/productivity/sign.rst:352
msgid ":guilabel:`Checkbox`: users can tick a box (e.g., to mark their approval or consent)."
msgstr ""
#: ../../content/applications/productivity/sign.rst:350
#: ../../content/applications/productivity/sign.rst:353
msgid ":guilabel:`Selection`: users choose a single option from a variety of options."
msgstr ""
#: ../../content/applications/productivity/sign.rst:352
#: ../../content/applications/productivity/sign.rst:355
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:357
#: ../../content/applications/productivity/sign.rst:360
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:361
#: ../../content/applications/productivity/sign.rst:364
msgid "Auto-completed values are suggestions and can be modified as required by the person signing the document."
msgstr ""
#: ../../content/applications/productivity/sign.rst:364
#: ../../content/applications/productivity/sign.rst:367
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:370
#: ../../content/applications/productivity/sign.rst:373
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 ""
@ -4218,6 +4222,7 @@ msgstr ""
#: ../../content/applications/productivity/sign/ecuador.rst:18
#: ../../content/applications/productivity/sign/egypt.rst:17
#: ../../content/applications/productivity/sign/ethiopia.rst:17
#: ../../content/applications/productivity/sign/germany.rst:19
#: ../../content/applications/productivity/sign/guatemala.rst:17
#: ../../content/applications/productivity/sign/hong_kong.rst:17
#: ../../content/applications/productivity/sign/india.rst:20
@ -4271,6 +4276,7 @@ msgstr ""
#: ../../content/applications/productivity/sign/ecuador.rst:20
#: ../../content/applications/productivity/sign/egypt.rst:19
#: ../../content/applications/productivity/sign/ethiopia.rst:19
#: ../../content/applications/productivity/sign/germany.rst:21
#: ../../content/applications/productivity/sign/guatemala.rst:19
#: ../../content/applications/productivity/sign/hong_kong.rst:19
#: ../../content/applications/productivity/sign/india.rst:22
@ -4339,6 +4345,7 @@ msgstr ""
#: ../../content/applications/productivity/sign/ecuador.rst:31
#: ../../content/applications/productivity/sign/egypt.rst:30
#: ../../content/applications/productivity/sign/ethiopia.rst:30
#: ../../content/applications/productivity/sign/germany.rst:32
#: ../../content/applications/productivity/sign/guatemala.rst:30
#: ../../content/applications/productivity/sign/hong_kong.rst:30
#: ../../content/applications/productivity/sign/india.rst:34
@ -4392,6 +4399,7 @@ msgstr ""
#: ../../content/applications/productivity/sign/ecuador.rst:33
#: ../../content/applications/productivity/sign/egypt.rst:32
#: ../../content/applications/productivity/sign/ethiopia.rst:32
#: ../../content/applications/productivity/sign/germany.rst:34
#: ../../content/applications/productivity/sign/guatemala.rst:32
#: ../../content/applications/productivity/sign/hong_kong.rst:32
#: ../../content/applications/productivity/sign/india.rst:36
@ -4445,6 +4453,7 @@ msgstr ""
#: ../../content/applications/productivity/sign/ecuador.rst:35
#: ../../content/applications/productivity/sign/egypt.rst:34
#: ../../content/applications/productivity/sign/ethiopia.rst:34
#: ../../content/applications/productivity/sign/germany.rst:36
#: ../../content/applications/productivity/sign/guatemala.rst:34
#: ../../content/applications/productivity/sign/hong_kong.rst:34
#: ../../content/applications/productivity/sign/india.rst:38
@ -4498,6 +4507,7 @@ msgstr ""
#: ../../content/applications/productivity/sign/ecuador.rst:37
#: ../../content/applications/productivity/sign/egypt.rst:36
#: ../../content/applications/productivity/sign/ethiopia.rst:36
#: ../../content/applications/productivity/sign/germany.rst:38
#: ../../content/applications/productivity/sign/guatemala.rst:36
#: ../../content/applications/productivity/sign/hong_kong.rst:36
#: ../../content/applications/productivity/sign/india.rst:40
@ -4551,6 +4561,7 @@ msgstr ""
#: ../../content/applications/productivity/sign/ecuador.rst:39
#: ../../content/applications/productivity/sign/egypt.rst:38
#: ../../content/applications/productivity/sign/ethiopia.rst:38
#: ../../content/applications/productivity/sign/germany.rst:40
#: ../../content/applications/productivity/sign/guatemala.rst:38
#: ../../content/applications/productivity/sign/hong_kong.rst:38
#: ../../content/applications/productivity/sign/india.rst:42
@ -4604,6 +4615,7 @@ msgstr ""
#: ../../content/applications/productivity/sign/ecuador.rst:43
#: ../../content/applications/productivity/sign/egypt.rst:42
#: ../../content/applications/productivity/sign/ethiopia.rst:42
#: ../../content/applications/productivity/sign/germany.rst:44
#: ../../content/applications/productivity/sign/guatemala.rst:42
#: ../../content/applications/productivity/sign/hong_kong.rst:42
#: ../../content/applications/productivity/sign/india.rst:46
@ -4657,6 +4669,7 @@ msgstr ""
#: ../../content/applications/productivity/sign/ecuador.rst:45
#: ../../content/applications/productivity/sign/egypt.rst:44
#: ../../content/applications/productivity/sign/ethiopia.rst:44
#: ../../content/applications/productivity/sign/germany.rst:46
#: ../../content/applications/productivity/sign/guatemala.rst:44
#: ../../content/applications/productivity/sign/hong_kong.rst:44
#: ../../content/applications/productivity/sign/india.rst:48
@ -4710,6 +4723,7 @@ msgstr ""
#: ../../content/applications/productivity/sign/ecuador.rst:47
#: ../../content/applications/productivity/sign/egypt.rst:46
#: ../../content/applications/productivity/sign/ethiopia.rst:46
#: ../../content/applications/productivity/sign/germany.rst:48
#: ../../content/applications/productivity/sign/guatemala.rst:46
#: ../../content/applications/productivity/sign/hong_kong.rst:46
#: ../../content/applications/productivity/sign/india.rst:50
@ -4763,6 +4777,7 @@ msgstr ""
#: ../../content/applications/productivity/sign/ecuador.rst:48
#: ../../content/applications/productivity/sign/egypt.rst:47
#: ../../content/applications/productivity/sign/ethiopia.rst:47
#: ../../content/applications/productivity/sign/germany.rst:49
#: ../../content/applications/productivity/sign/guatemala.rst:47
#: ../../content/applications/productivity/sign/hong_kong.rst:47
#: ../../content/applications/productivity/sign/india.rst:51
@ -4816,6 +4831,7 @@ msgstr ""
#: ../../content/applications/productivity/sign/ecuador.rst:49
#: ../../content/applications/productivity/sign/egypt.rst:48
#: ../../content/applications/productivity/sign/ethiopia.rst:48
#: ../../content/applications/productivity/sign/germany.rst:50
#: ../../content/applications/productivity/sign/guatemala.rst:48
#: ../../content/applications/productivity/sign/hong_kong.rst:48
#: ../../content/applications/productivity/sign/india.rst:52
@ -4869,6 +4885,7 @@ msgstr ""
#: ../../content/applications/productivity/sign/ecuador.rst:51
#: ../../content/applications/productivity/sign/egypt.rst:50
#: ../../content/applications/productivity/sign/ethiopia.rst:50
#: ../../content/applications/productivity/sign/germany.rst:52
#: ../../content/applications/productivity/sign/guatemala.rst:50
#: ../../content/applications/productivity/sign/hong_kong.rst:50
#: ../../content/applications/productivity/sign/india.rst:54
@ -4922,6 +4939,7 @@ msgstr ""
#: ../../content/applications/productivity/sign/ecuador.rst:54
#: ../../content/applications/productivity/sign/egypt.rst:53
#: ../../content/applications/productivity/sign/ethiopia.rst:53
#: ../../content/applications/productivity/sign/germany.rst:55
#: ../../content/applications/productivity/sign/guatemala.rst:53
#: ../../content/applications/productivity/sign/hong_kong.rst:53
#: ../../content/applications/productivity/sign/india.rst:57
@ -4979,6 +4997,7 @@ msgstr ""
#: ../../content/applications/productivity/sign/ecuador.rst:59
#: ../../content/applications/productivity/sign/egypt.rst:58
#: ../../content/applications/productivity/sign/ethiopia.rst:58
#: ../../content/applications/productivity/sign/germany.rst:60
#: ../../content/applications/productivity/sign/guatemala.rst:58
#: ../../content/applications/productivity/sign/hong_kong.rst:58
#: ../../content/applications/productivity/sign/india.rst:62
@ -5032,6 +5051,7 @@ msgstr ""
#: ../../content/applications/productivity/sign/ecuador.rst:61
#: ../../content/applications/productivity/sign/egypt.rst:60
#: ../../content/applications/productivity/sign/ethiopia.rst:60
#: ../../content/applications/productivity/sign/germany.rst:62
#: ../../content/applications/productivity/sign/guatemala.rst:60
#: ../../content/applications/productivity/sign/hong_kong.rst:60
#: ../../content/applications/productivity/sign/india.rst:64
@ -5085,6 +5105,7 @@ msgstr ""
#: ../../content/applications/productivity/sign/ecuador.rst:63
#: ../../content/applications/productivity/sign/egypt.rst:62
#: ../../content/applications/productivity/sign/ethiopia.rst:62
#: ../../content/applications/productivity/sign/germany.rst:64
#: ../../content/applications/productivity/sign/guatemala.rst:62
#: ../../content/applications/productivity/sign/hong_kong.rst:62
#: ../../content/applications/productivity/sign/india.rst:66
@ -5138,6 +5159,7 @@ msgstr ""
#: ../../content/applications/productivity/sign/ecuador.rst:65
#: ../../content/applications/productivity/sign/egypt.rst:64
#: ../../content/applications/productivity/sign/ethiopia.rst:64
#: ../../content/applications/productivity/sign/germany.rst:66
#: ../../content/applications/productivity/sign/guatemala.rst:64
#: ../../content/applications/productivity/sign/hong_kong.rst:64
#: ../../content/applications/productivity/sign/india.rst:68
@ -5190,6 +5212,7 @@ msgstr ""
#: ../../content/applications/productivity/sign/dominican_republic.rst:73
#: ../../content/applications/productivity/sign/ecuador.rst:73
#: ../../content/applications/productivity/sign/ethiopia.rst:72
#: ../../content/applications/productivity/sign/germany.rst:74
#: ../../content/applications/productivity/sign/guatemala.rst:72
#: ../../content/applications/productivity/sign/hong_kong.rst:72
#: ../../content/applications/productivity/sign/iran.rst:71
@ -5736,6 +5759,42 @@ msgstr ""
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 Ethiopia, 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/germany.rst:5
msgid "Odoo Sign legality in Germany"
msgstr ""
#: ../../content/applications/productivity/sign/germany.rst:7
msgid ":doc:`Odoo Sign <../sign>` is your trusted partner for secure, efficient, and legally compliant electronic signatures in Germany."
msgstr ""
#: ../../content/applications/productivity/sign/germany.rst:11
msgid "Legal framework for electronic signatures in Germany"
msgstr ""
#: ../../content/applications/productivity/sign/germany.rst:13
msgid "In Germany, electronic signatures are regulated under `eIDAS Regulation No. 910/2014 <https://eur-lex.europa.eu/legal-content/EN/TXT/?uri=uriserv%3AOJ.L_.2014.257.01.0073.01.ENG>`_ and the `Trust Services Act <https://www.gesetze-im-internet.de/vdg/BJNR274510017.html>`_. The law establishes the legal basis for acknowledging electronic records, contracts, and digital signatures. The key points of the law include:"
msgstr ""
#: ../../content/applications/productivity/sign/germany.rst:23
msgid "**Qualified signature**: there are certain use cases that require a qualified signature issued by a trust service provider."
msgstr ""
#: ../../content/applications/productivity/sign/germany.rst:27
msgid "How Odoo Sign complies with German regulations"
msgstr ""
#: ../../content/applications/productivity/sign/germany.rst:29
msgid "Odoo Sign ensures full compliance with the Electronic Signature Law of Germany by incorporating the following features:"
msgstr ""
#: ../../content/applications/productivity/sign/germany.rst:57
msgid "While Odoo Sign is broadly applicable, there are certain exceptions where electronic signatures may not be suitable or legally recognized in Germany:"
msgstr ""
#: ../../content/applications/productivity/sign/germany.rst:68
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 Germany, 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/guatemala.rst:5
msgid "Odoo Sign legality in Guatemala"
msgstr ""

254
locale/sources/sales.pot
View File

@ -8,7 +8,7 @@ msgid ""
msgstr ""
"Project-Id-Version: Odoo 17.0\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2024-09-24 10:43+0000\n"
"POT-Creation-Date: 2024-11-04 11:48+0000\n"
"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
"Language-Team: LANGUAGE <LL@li.org>\n"
@ -54,13 +54,14 @@ msgstr ""
#: ../../content/applications/sales/point_of_sale/combos.rst:16
#: ../../content/applications/sales/point_of_sale/configuration.rst:6
#: ../../content/applications/sales/point_of_sale/configuration.rst:52
#: ../../content/applications/sales/point_of_sale/configuration/epos_printers.rst:10
#: ../../content/applications/sales/point_of_sale/employee_login.rst:13
#: ../../content/applications/sales/point_of_sale/payment_methods/terminals.rst:13
#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/adyen.rst:20
#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/ingenico.rst:15
#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/mercado_pago.rst:20
#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/razorpay.rst:12
#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/six.rst:14
#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/six.rst:16
#: ../../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
@ -5318,29 +5319,28 @@ msgstr ""
msgid "ePOS printers are designed to work seamlessly with Point of Sale systems. Once connected, these devices automatically share information, allowing for direct printing of tickets from the POS system to the ePOS printer."
msgstr ""
#: ../../content/applications/sales/point_of_sale/configuration/epos_printers.rst:10
msgid "Epson printers using Wi-Fi/Ethernet connections and following the `EPOS SDK Javascript protocol <https://download4.epson.biz/sec_pubs/pos/reference_en/technology/epson_epos_sdk.html>`_ are compatible with Odoo **without** needing an :doc:`IoT Box </applications/general/iot/devices/printer>`."
#: ../../content/applications/sales/point_of_sale/configuration/epos_printers.rst:12
msgid "To use an ePos printer in Point of Sale:"
msgstr ""
#: ../../content/applications/sales/point_of_sale/configuration/epos_printers.rst:14
msgid "Thermal printers using ESC/POS or StarPRNT protocol are compatible **with** an :doc:`IoT Box </applications/general/iot/devices/printer>`."
msgid ":ref:`Access the POS settings <configuration/settings>`."
msgstr ""
#: ../../content/applications/sales/point_of_sale/configuration/epos_printers.rst:15
msgid "Activate the :guilabel:`ePos Printer` feature."
msgstr ""
#: ../../content/applications/sales/point_of_sale/configuration/epos_printers.rst:16
msgid "Epson printers using only USB connections are compatible **with** an :doc:`IoT Box </applications/general/iot/devices/printer>`."
msgid "Fill in the field with your ePos IP address."
msgstr ""
#: ../../content/applications/sales/point_of_sale/configuration/epos_printers.rst:18
msgid "Epson printers that connect via Bluetooth are **not compatible**."
msgstr ""
#: ../../content/applications/sales/point_of_sale/configuration/epos_printers.rst:21
msgid ":doc:`https`"
#: ../../content/applications/sales/point_of_sale/configuration/epos_printers.rst:-1
msgid "setting to enable the ePos printer feature"
msgstr ""
#: ../../content/applications/sales/point_of_sale/configuration/epos_printers.rst:22
#: ../../content/applications/sales/point_of_sale/configuration/https.rst:22
msgid ":doc:`epos_ssc`"
msgid "When the printer connects to a network, it automatically prints a ticket with its IP address."
msgstr ""
#: ../../content/applications/sales/point_of_sale/configuration/epos_printers.rst:25
@ -5427,6 +5427,31 @@ msgstr ""
msgid "Epson TM-U220 family (incompatible ePOS software)"
msgstr ""
#: ../../content/applications/sales/point_of_sale/configuration/epos_printers.rst:56
msgid "Epson printers using Wi-Fi/Ethernet connections and following the `EPOS SDK Javascript protocol <https://download4.epson.biz/sec_pubs/pos/reference_en/technology/epson_epos_sdk.html>`_ are compatible with Odoo **without** needing an :doc:`IoT Box </applications/general/iot/devices/printer>`."
msgstr ""
#: ../../content/applications/sales/point_of_sale/configuration/epos_printers.rst:60
msgid "Thermal printers using ESC/POS or StarPRNT protocol are compatible **with** an :doc:`IoT Box </applications/general/iot/devices/printer>`."
msgstr ""
#: ../../content/applications/sales/point_of_sale/configuration/epos_printers.rst:62
msgid "Epson printers using only USB connections are compatible **with** an :doc:`IoT Box </applications/general/iot/devices/printer>`."
msgstr ""
#: ../../content/applications/sales/point_of_sale/configuration/epos_printers.rst:64
msgid "Epson printers that connect via Bluetooth are **not compatible**."
msgstr ""
#: ../../content/applications/sales/point_of_sale/configuration/epos_printers.rst:67
msgid ":doc:`https`"
msgstr ""
#: ../../content/applications/sales/point_of_sale/configuration/epos_printers.rst:68
#: ../../content/applications/sales/point_of_sale/configuration/https.rst:22
msgid ":doc:`epos_ssc`"
msgstr ""
#: ../../content/applications/sales/point_of_sale/configuration/epos_ssc.rst:5
msgid "Self-signed certificate for ePOS printers"
msgstr ""
@ -5910,7 +5935,6 @@ msgstr ""
#: ../../content/applications/sales/point_of_sale/payment_methods.rst:25
#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/adyen.rst:84
#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/ingenico.rst:50
#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/six.rst:63
#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/worldline.rst:81
msgid "Once the payment method is created, you can select it in your POS settings. To do so, go to the :ref:`POS' settings <configuration/settings>`, click :guilabel:`Edit`, and add the payment method under the :guilabel:`Payments` section."
msgstr ""
@ -5975,6 +5999,26 @@ msgstr ""
msgid "Once the terminal is configured, you can :doc:`create the corresponding payment method and add it to the POS <../payment_methods>`."
msgstr ""
#: ../../content/applications/sales/point_of_sale/payment_methods/terminals.rst:37
msgid "Pay with a payment terminal"
msgstr ""
#: ../../content/applications/sales/point_of_sale/payment_methods/terminals.rst:39
msgid "When processing a payment, select the terminal's 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.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.rst:0
msgid "This option is only available after receiving an error message informing you that the connection failed."
msgstr ""
#: ../../content/applications/sales/point_of_sale/payment_methods/terminals.rst:48
msgid "To cancel the payment request, click on :guilabel:`Cancel`."
msgstr ""
#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/adyen.rst:3
msgid "Adyen"
msgstr ""
@ -6070,7 +6114,7 @@ msgstr ""
#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/adyen.rst:73
#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/ingenico.rst:41
#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/razorpay.rst:30
#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/six.rst:53
#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/six.rst:55
#: ../../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
@ -6086,39 +6130,6 @@ msgstr ""
msgid "Finally, fill in the mandatory fields with your :ref:`Adyen API key <adyen/api>`, :ref:`Adyen Terminal Identifier <adyen/identifier>`, and :guilabel:`Adyen Merchant Account`."
msgstr ""
#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/adyen.rst:89
#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/ingenico.rst:55
#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/razorpay.rst:56
#: ../../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 ""
#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/adyen.rst:91
msgid "When processing a payment, select :guilabel:`Adyen` as the payment method. Check the amount and click on :guilabel:`Send`. Once the payment is successful, the status changes to :guilabel:`Payment Successful`."
msgstr ""
#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/adyen.rst:0
#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/razorpay.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/razorpay.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 ""
#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/adyen.rst:100
msgid "To cancel the payment request, click on :guilabel:`cancel`."
msgstr ""
#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/ingenico.rst:3
msgid "Ingenico"
msgstr ""
@ -6187,26 +6198,6 @@ msgstr ""
msgid "Enable the payment terminal :ref:`in the application settings <configuration/settings>` and :doc:`create the related payment method <../../payment_methods>`. Set the journal type as :guilabel:`Bank` and select :guilabel:`Ingenico` in the :guilabel:`Use a Payment Terminal` field. Then, select your terminal device in the :guilabel:`Payment Terminal Device` field."
msgstr ""
#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/ingenico.rst:57
msgid "In your *PoS interface*, when processing a payment, select a *Payment Method* using a payment terminal. Check that the amount in the tendered column is the one that has to be sent to the payment terminal and click on *Send*. When the payment is successful, the status will change to *Payment Successful*."
msgstr ""
#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/ingenico.rst:66
msgid "If you want to cancel the payment request, click on cancel. You can still retry to send the payment request."
msgstr ""
#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/ingenico.rst:69
msgid "If there is any issue with the payment terminal, you can still force the payment using the *Force Done*. This will allow you to validate the order in Odoo even if the connection between the terminal and Odoo has issues."
msgstr ""
#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/ingenico.rst:75
msgid "This option will only be available if you received an error message telling you the connection failed."
msgstr ""
#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/ingenico.rst:78
msgid "Once your payment is processed, on the payment record, you’ll find the type of card that has been used and the transaction ID."
msgstr ""
#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/mercado_pago.rst:3
msgid "Mercado Pago"
msgstr ""
@ -6340,23 +6331,7 @@ msgstr ""
msgid "Select the payment method by going to the :ref:`POS' settings <configuration/settings>` and adding it to the payment method under the :guilabel:`Payment Methods` field of the :guilabel:`Payment` section."
msgstr ""
#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/mercado_pago.rst:101
msgid "Paying with a payment terminal"
msgstr ""
#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/mercado_pago.rst:103
msgid "When processing a payment, select your Mercado Pago payment method, check the amount, and click :guilabel:`Send`. Once the payment is successful, the status changes to :guilabel:`Payment Successful`."
msgstr ""
#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/mercado_pago.rst:108
msgid "In case of connection issues between Odoo and the payment terminal, force the payment by clicking :guilabel:`Force Done`, which allows you to validate the order. This option is only available after receiving an error message informing you that the connection failed."
msgstr ""
#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/mercado_pago.rst:111
msgid "To cancel the payment request, click :guilabel:`Cancel`."
msgstr ""
#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/mercado_pago.rst:114
#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/mercado_pago.rst:99
msgid "Any action made on the terminal should trigger a notification on the POS interface. Ensure the :ref:`webhook secret key <pos-mercado-pago-credentials>` is correctly configured if you are not notified."
msgstr ""
@ -6421,7 +6396,6 @@ msgid "Set the :guilabel:`Razorpay Allowed Payment Modes` according to your need
msgstr ""
#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/razorpay.rst:0
#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/razorpay.rst:-1
msgid "Razorpay connection form"
msgstr ""
@ -6433,11 +6407,7 @@ msgstr ""
msgid "Once the payment method is created, you can enable it for your POS. To do so, go to the :ref:`POS' settings <configuration/settings>` and add the payment method under the :guilabel:`Payment` section."
msgstr ""
#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/razorpay.rst:58
msgid "When processing a payment, select the Razorpay payment method. Check the amount and click :guilabel:`Send`. Once the payment is successful, the status changes to :guilabel:`Payment Successful`. To cancel the payment request, click :guilabel:`Cancel`."
msgstr ""
#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/razorpay.rst:70
#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/razorpay.rst:56
msgid "The terminal must have at least a 10% battery level to use it."
msgstr ""
@ -6446,38 +6416,42 @@ msgid "SIX"
msgstr ""
#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/six.rst:5
msgid "Connecting a **SIX payment terminal** allows you to offer a fluid payment flow to your customers and ease the work of your cashiers."
msgid "Connecting a SIX payment terminal allows you to offer a fluid payment flow to your customers and ease the work of your cashiers."
msgstr ""
#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/six.rst:9
msgid "Even though Worldline has acquired SIX Payment Services and both companies use Yomani payment terminals, the firmware they run is different. Terminals received from Worldline are, therefore, not compatible with this integration."
msgid "Starting in July 2022, it will **not** be possible anymore to connect and use a Six payment terminal in PoS."
msgstr ""
#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/six.rst:17
msgid "Install the POS IoT Six module"
#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/six.rst:11
msgid "Even though Worldline has recently acquired SIX Payment Services and both companies use Yomani payment terminals, the firmware they run is different. Terminals received from Worldline are therefore not compatible with this integration."
msgstr ""
#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/six.rst:19
msgid "Install the POS IoT Six module"
msgstr ""
#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/six.rst:21
msgid "To activate the POS IoT Six module, go to :guilabel:`Apps`, remove the :guilabel:`Apps` filter, and search for **POS IoT Six**. This module adds the necessary driver and interface to your database to detect Six terminals."
msgstr ""
#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/six.rst:24
#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/six.rst:26
msgid "This module replaces the **POS Six** module."
msgstr ""
#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/six.rst:27
#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/six.rst:29
msgid "Connect an IoT box"
msgstr ""
#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/six.rst:29
#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/six.rst:31
msgid "Connecting a Six payment terminal to Odoo is requires :doc:`using a Raspberry Pi or virtual (for Windows OS only) IoT box </applications/general/iot/config/connect>`."
msgstr ""
#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/six.rst:33
#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/six.rst:35
msgid "Configure the terminal ID"
msgstr ""
#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/six.rst:35
#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/six.rst:37
msgid "Navigate to your IoT Box homepage, where you can find the :guilabel:`Six payment terminal` field once your database server is connected to the IoT box. Click :guilabel:`Configure`, fill in the :guilabel:`Terminal ID` field with the ID received from Six, and click :guilabel:`Connect`. Your Six terminal ID should appear in the :guilabel:`Current Terminal Id` section."
msgstr ""
@ -6485,7 +6459,7 @@ msgstr ""
msgid "Setting the Six terminal ID"
msgstr ""
#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/six.rst:43
#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/six.rst:45
msgid "Odoo automatically restarts the IoT box when the Six terminal ID is configured. If your Six terminal is online, it will be automatically detected and connected to the database. Check the IoT box homepage under the :guilabel:`Payments` section to confirm the connection."
msgstr ""
@ -6493,7 +6467,7 @@ msgstr ""
msgid "Confirming the connection to the Six payment terminal"
msgstr ""
#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/six.rst:55
#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/six.rst:57
msgid "Enable the payment terminal :ref:`in the application settings <configuration/settings>` and :doc:`create the related payment method <../../payment_methods>`. Set the journal type as :guilabel:`Bank` and select :guilabel:`SIX IOT` in the :guilabel:`Use a Payment Terminal` field. Then, select your terminal device in the :guilabel:`Payment Terminal Device` field."
msgstr ""
@ -6501,31 +6475,6 @@ msgstr ""
msgid "Creating a new payment method for the SIX payment terminal"
msgstr ""
#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/six.rst:70
msgid "When processing a payment, select :ref:`your Six payment method <six/configure>` in the :guilabel:`Payment Method` section and click :guilabel:`Send`. To cancel the payment request, click :guilabel:`Cancel`. Once the payment is successful, the status switches to :guilabel:`Payment Successful`."
msgstr ""
#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/six.rst:-1
msgid "Paying with Six"
msgstr ""
#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/six.rst:79
#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/worldline.rst:101
msgid "Once your payment is processed, the type of card used and the transaction ID appear on the payment record."
msgstr ""
#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/six.rst:81
msgid "The language used for error messages is the same as the Six terminal. Configure the terminal to change the language or contact Six."
msgstr ""
#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/six.rst:83
msgid "By default, the port used by the Six terminal is `7784`."
msgstr ""
#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/six.rst:86
msgid "If there are connection issues between the payment terminal and Odoo, you can still force the payment validation in Odoo using the :guilabel:`Force Done` button."
msgstr ""
#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/stripe.rst:3
msgid "Stripe"
msgstr ""
@ -6644,43 +6593,31 @@ msgstr ""
msgid "To add a **payment method** to your point of sale, go to :menuselection:`Point of Sale --> Configuration --> Settings`. Select the POS, scroll down to the :guilabel:`Payments` section, and add your payment method for **Stripe** in the :guilabel:`Payment Methods` field."
msgstr ""
#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/stripe.rst:95
msgid "When processing a payment, select :guilabel:`Stripe` as the payment method. Check the amount and click :guilabel:`Send`. Once the payment is successful, the status changes to :guilabel:`Payment Successful`. To cancel the payment request, click :guilabel:`cancel`."
msgstr ""
#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/stripe.rst:104
msgid "The terminal must have at least 10% battery level to use it."
msgstr ""
#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/stripe.rst:105
msgid "The device does not work for payments under €0.50."
msgstr ""
#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/stripe.rst:108
#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/stripe.rst:93
msgid "Troubleshooting"
msgstr ""
#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/stripe.rst:111
#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/stripe.rst:96
msgid "Payment terminal unavailable in your Stripe account"
msgstr ""
#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/stripe.rst:113
#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/stripe.rst:98
msgid "If the payment terminal is unavailable in your Stripe account, you must add it manually:"
msgstr ""
#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/stripe.rst:115
#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/stripe.rst:100
msgid "Log into your `Stripe's dashboard <https://dashboard.stripe.com>`_ and go to :menuselection:`Stripe dashboard --> Payments --> Readers --> Locations`;"
msgstr ""
#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/stripe.rst:117
#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/stripe.rst:102
msgid "Add a location by clicking the :guilabel:`+ New` button or selecting an already created location;"
msgstr ""
#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/stripe.rst:118
#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/stripe.rst:103
msgid "Click the :guilabel:`+ New` button in the :guilabel:`Readers` box and fill in the required information."
msgstr ""
#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/stripe.rst:122
#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/stripe.rst:107
msgid "You must provide a **registration code**. To retrieve that code, swipe right on your device, enter the admin PIN code (by default: `07139`), validate, and click :guilabel:`Generate a registration code`."
msgstr ""
@ -6720,11 +6657,6 @@ msgstr ""
msgid "Once the payment method is created, you can select it in your POS settings. To do so, go to the :ref:`POS' settings <configuration/settings>` and add the payment method under the :guilabel:`Payment` section."
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 ""
@ -6861,10 +6793,6 @@ msgstr ""
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 <configuration/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 ""
@ -6965,18 +6893,6 @@ msgstr ""
msgid "Set a fixed IP to your IoT Box’s router to prevent losing the connexion."
msgstr ""
#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/worldline.rst:98
msgid "When processing a payment, select *Worldline* as payment method. Check the amount and click on *Send*. Once the payment is successful, the status changes to *Payment Successful*."
msgstr ""
#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/worldline.rst:108
msgid "In case of connexion issues between Odoo and the payment terminal, force the payment by clicking on *Force Done*, which allows you to validate the order. This option is only available after receiving an error message informing you that the connection failed."
msgstr ""
#: ../../content/applications/sales/point_of_sale/payment_methods/terminals/worldline.rst:111
msgid "To cancel the payment request, click on **cancel**."
msgstr ""
#: ../../content/applications/sales/point_of_sale/pricing.rst:5
msgid "Pricing features"
msgstr ""
@ -13934,7 +13850,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/products/variants`"
msgid ":ref:`ecommerce/products/product-variants`"
msgstr ""
#: ../../content/applications/sales/sales/products_prices/products/variants.rst:36

659
locale/sources/websites.pot
View File

File diff suppressed because it is too large Load Diff