khanh.pndc/odoo-docs
1
0
Fork 0
mirror of https://github.com/odoo/documentation.git synced 2026-01-02 17:59:20 +07:00
Code Issues Packages Projects Releases Wiki Activity

[I18N] *: re-export pot files

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#13142

Signed-off-by: Tiffany Chang (tic) <tic@odoo.com>
This commit is contained in:
Tiffany Chang (tic)
2025-04-30 10:43:37 +02:00
parent 23f5c373b7
commit b9a658e23d
5 changed files with 1118 additions and 733 deletions
Download Patch File Download Diff File Expand all files Collapse all files

179
locale/sources/administration.pot
View File

@@ -8,7 +8,7 @@ msgid ""
msgstr ""
"Project-Id-Version: Odoo 16.0\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2025-03-27 08:53+0000\n"
"POT-Creation-Date: 2025-04-30 07:56+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"
@@ -91,12 +91,12 @@ msgid "Transferring an on-premise database"
msgstr ""
#: ../../content/administration/hosting.rst:17
#: ../../content/administration/hosting.rst:90
#: ../../content/administration/hosting.rst:92
msgid "To Odoo Online"
msgstr ""
#: ../../content/administration/hosting.rst:20
#: ../../content/administration/hosting.rst:93
#: ../../content/administration/hosting.rst:95
msgid "Odoo Online is *not* compatible with **non-standard apps**."
msgstr ""
@@ -117,11 +117,12 @@ msgid "Use the database manager to grab a *dump with filestore*."
msgstr ""
#: ../../content/administration/hosting.rst:26
msgid "`Submit a support ticket <https://www.odoo.com/help>`_ including the following:"
#: ../../content/administration/hosting.rst:98
msgid "`Create a support ticket <https://www.odoo.com/help-form>`_ including the following:"
msgstr ""
#: ../../content/administration/hosting.rst:28
#: ../../content/administration/hosting.rst:98
#: ../../content/administration/hosting.rst:100
msgid "your **subscription number**,"
msgstr ""
@@ -134,22 +135,22 @@ msgid "the **dump** as an attachment or as a link to the file (required for 60 M
msgstr ""
#: ../../content/administration/hosting.rst:32
#: ../../content/administration/hosting.rst:105
#: ../../content/administration/hosting.rst:107
msgid "Odoo then makes sure the database is compatible before putting it online. In case of technical issues during the process, Odoo might contact you."
msgstr ""
#: ../../content/administration/hosting.rst:36
#: ../../content/administration/hosting.rst:109
msgid "If you have time constraints, `submit a support ticket <https://www.odoo.com/help>`_ as soon as possible to schedule the transfer."
#: ../../content/administration/hosting.rst:111
msgid "If you have time constraints, `create a support ticket <https://www.odoo.com/help-form>`_ as soon as possible to schedule the transfer."
msgstr ""
#: ../../content/administration/hosting.rst:40
#: ../../content/administration/hosting.rst:77
#: ../../content/administration/hosting.rst:78
msgid "To Odoo.sh"
msgstr ""
#: ../../content/administration/hosting.rst:42
#: ../../content/administration/hosting.rst:83
#: ../../content/administration/hosting.rst:85
msgid "Follow the instructions found in :ref:`the Import your database section <odoo_sh_import_your_database>` of the Odoo.sh *Create your project* documentation."
msgstr ""
@@ -166,77 +167,73 @@ msgid "Transferring an online database running on Odoo 16.3 would require first
msgstr ""
#: ../../content/administration/hosting.rst:59
msgid "Click the gear icon (:guilabel:`⚙`) next to the database name on the `Odoo Online database manager <https://www.odoo.com/my/databases/>`_ to display its version number."
msgid "Click the :icon:`fa-gear` (:guilabel:`gear`) button next to the database name on the `Odoo Online database manager <https://www.odoo.com/my/databases/>`_ to display its version number."
msgstr ""
#: ../../content/administration/hosting.rst:63
msgid "If there is an active Odoo subscription linked to the database being migrated, reach out to the Customer Service Manager or `submit a support ticket <https://www.odoo.com/help>`_ to complete the subscription transfer."
msgid "If there is an active Odoo subscription linked to the database being migrated, reach out to the Customer Service Manager or `contact Odoo support <https://www.odoo.com/help>`_ to complete the subscription transfer."
msgstr ""
#: ../../content/administration/hosting.rst:68
#: ../../content/administration/hosting.rst:118
#: ../../content/administration/hosting.rst:120
msgid "To on-premise"
msgstr ""
#: ../../content/administration/hosting.rst:70
#: ../../content/administration/hosting.rst:79
msgid "Sign in to `the Odoo Online database manager <https://www.odoo.com/my/databases/>`_ and click the gear icon (:guilabel:`⚙`) next to the database name to :guilabel:`Download` a backup. If the download fails due to the file being too large, `contact Odoo support <https://www.odoo.com/help>`_."
#: ../../content/administration/hosting.rst:80
msgid "Download a database backup by signing in to `the Odoo Online database manager <https://www.odoo.com/my/databases/>`_, clicking the :icon:`fa-gear` (:guilabel:`gear`) button next to the database name, then selecting :icon:`fa-cloud-download` :guilabel:`Download`. If the download fails due to the file being too large, `contact Odoo support <https://www.odoo.com/help>`_."
msgstr ""
#: ../../content/administration/hosting.rst:74
#: ../../content/administration/hosting.rst:121
#: ../../content/administration/hosting.rst:75
#: ../../content/administration/hosting.rst:123
msgid "Restore the database from the database manager on your local server using the backup."
msgstr ""
#: ../../content/administration/hosting.rst:87
#: ../../content/administration/hosting.rst:89
msgid "Transferring an Odoo.sh database"
msgstr ""
#: ../../content/administration/hosting.rst:95
#: ../../content/administration/hosting.rst:97
msgid "Uninstall all **non-standard apps** in a staging build before doing it in the production build."
msgstr ""
#: ../../content/administration/hosting.rst:96
msgid "`Create a support ticket <https://www.odoo.com/help>`_ including the following:"
msgstr ""
#: ../../content/administration/hosting.rst:99
#: ../../content/administration/hosting.rst:101
msgid "the **URL** you want to use for the database (e.g., `company.odoo.com`),"
msgstr ""
#: ../../content/administration/hosting.rst:100
#: ../../content/administration/hosting.rst:102
msgid "which **branch** should be migrated,"
msgstr ""
#: ../../content/administration/hosting.rst:101
#: ../../content/administration/hosting.rst:103
msgid "in which **region** you want the database to be hosted (Americas, Europe, or Asia),"
msgstr ""
#: ../../content/administration/hosting.rst:102
#: ../../content/administration/hosting.rst:104
msgid "which user(s) will be the **administrator(s)**, and"
msgstr ""
#: ../../content/administration/hosting.rst:103
#: ../../content/administration/hosting.rst:105
msgid "**when** (and in which timezone) you want the database to be up and running."
msgstr ""
#: ../../content/administration/hosting.rst:111
#: ../../content/administration/hosting.rst:113
msgid "Select the **region** closest to most of your users to reduce latency."
msgstr ""
#: ../../content/administration/hosting.rst:112
#: ../../content/administration/hosting.rst:114
msgid "Future **administrator(s)** must have an Odoo.com account."
msgstr ""
#: ../../content/administration/hosting.rst:113
#: ../../content/administration/hosting.rst:115
msgid "The **date and time** you want the database to be up and running are helpful to organize the switch from the Odoo.sh server to the Odoo Online servers."
msgstr ""
#: ../../content/administration/hosting.rst:115
#: ../../content/administration/hosting.rst:117
msgid "Databases are **not reachable** during their migration."
msgstr ""
#: ../../content/administration/hosting.rst:120
#: ../../content/administration/hosting.rst:122
msgid "Download a :ref:`backup of your Odoo.sh production database <odoo_sh_branches_backups>`."
msgstr ""
@@ -576,7 +573,11 @@ msgstr ""
msgid ":ref:`odoo_online/users`"
msgstr ""
#: ../../content/administration/odoo_online.rst:43
#: ../../content/administration/odoo_online.rst:39
msgid ":ref:`odoo_online/web-services`"
msgstr ""
#: ../../content/administration/odoo_online.rst:44
#: ../../content/administration/odoo_sh/getting_started/branches.rst:293
#: ../../content/administration/odoo_sh/getting_started/settings.rst:123
#: ../../content/administration/odoo_sh/getting_started/settings.rst:168
@@ -584,92 +585,92 @@ msgstr ""
msgid "Upgrade"
msgstr ""
#: ../../content/administration/odoo_online.rst:45
#: ../../content/administration/odoo_online.rst:46
msgid "Trigger a database upgrade."
msgstr ""
#: ../../content/administration/odoo_online.rst:48
#: ../../content/administration/odoo_online.rst:49
msgid "For more information about the upgrade process, check out the :ref:`Odoo Online upgrade documentation <upgrade-request-test>`."
msgstr ""
#: ../../content/administration/odoo_online.rst:54
#: ../../content/administration/odoo_online.rst:55
msgid "Duplicate"
msgstr ""
#: ../../content/administration/odoo_online.rst:56
#: ../../content/administration/odoo_online.rst:57
msgid "Create an exact copy of the database, which can be used to perform testing without compromising daily operations."
msgstr ""
#: ../../content/administration/odoo_online.rst:60
#: ../../content/administration/odoo_online.rst:61
msgid "By checking :guilabel:`For testing purposes`, all external actions (emails, payments, delivery orders, etc.) are disabled by default on the duplicated database."
msgstr ""
#: ../../content/administration/odoo_online.rst:62
#: ../../content/administration/odoo_online.rst:63
msgid "Duplicated databases expire automatically after 15 days."
msgstr ""
#: ../../content/administration/odoo_online.rst:63
#: ../../content/administration/odoo_online.rst:64
msgid "A maximum of five duplicates can be made per database. Under extraordinary circumstances, contact `support <https://www.odoo.com/help>`_ to raise the limit."
msgstr ""
#: ../../content/administration/odoo_online.rst:69
#: ../../content/administration/odoo_online.rst:70
msgid "Rename"
msgstr ""
#: ../../content/administration/odoo_online.rst:71
#: ../../content/administration/odoo_online.rst:72
msgid "Rename the database and its URL."
msgstr ""
#: ../../content/administration/odoo_online.rst:76
#: ../../content/administration/odoo_online.rst:77
msgid "Download"
msgstr ""
#: ../../content/administration/odoo_online.rst:78
#: ../../content/administration/odoo_online.rst:79
msgid "Download a ZIP file containing a backup of the database."
msgstr ""
#: ../../content/administration/odoo_online.rst:81
#: ../../content/administration/odoo_online.rst:82
msgid "Databases are backed up daily as per the `Odoo Cloud Hosting SLA <https://www.odoo.com/cloud-sla>`_."
msgstr ""
#: ../../content/administration/odoo_online.rst:87
#: ../../content/administration/odoo_online.rst:88
msgid "Domain names"
msgstr ""
#: ../../content/administration/odoo_online.rst:89
#: ../../content/administration/odoo_online.rst:90
msgid "Use a custom :doc:`domain name </applications/websites/website/configuration/domain_names>` to access the database via another URL."
msgstr ""
#: ../../content/administration/odoo_online.rst:93
#: ../../content/administration/odoo_online.rst:94
msgid "You can :ref:`register a domain name for free <domain-name/register>`."
msgstr ""
#: ../../content/administration/odoo_online.rst:98
#: ../../content/administration/odoo_online.rst:99
msgid "Tags"
msgstr ""
#: ../../content/administration/odoo_online.rst:100
#: ../../content/administration/odoo_online.rst:101
msgid "Add tags to easily identify and sort your databases."
msgstr ""
#: ../../content/administration/odoo_online.rst:103
#: ../../content/administration/odoo_online.rst:104
msgid "You can search for tags in the search bar."
msgstr ""
#: ../../content/administration/odoo_online.rst:108
#: ../../content/administration/odoo_online.rst:109
#: ../../content/administration/odoo_sh/getting_started/branches.rst:550
msgid "Delete"
msgstr ""
#: ../../content/administration/odoo_online.rst:110
#: ../../content/administration/odoo_online.rst:111
msgid "Delete a database instantly."
msgstr ""
#: ../../content/administration/odoo_online.rst:113
#: ../../content/administration/odoo_online.rst:114
msgid "Deleting a database means that all data is permanently lost. The deletion is instant and applies to all users. It is recommended to create a backup of the database before deleting it."
msgstr ""
#: ../../content/administration/odoo_online.rst:116
#: ../../content/administration/odoo_online.rst:117
msgid "Carefully read the warning message and only proceed if the implications of deleting a database are fully understood."
msgstr ""
@@ -677,31 +678,31 @@ msgstr ""
msgid "The warning message displayed before deleting a database"
msgstr ""
#: ../../content/administration/odoo_online.rst:123
#: ../../content/administration/odoo_online.rst:124
msgid "Only an administrator can delete a database."
msgstr ""
#: ../../content/administration/odoo_online.rst:124
#: ../../content/administration/odoo_online.rst:125
msgid "The database name is immediately made available to anyone."
msgstr ""
#: ../../content/administration/odoo_online.rst:125
#: ../../content/administration/odoo_online.rst:126
msgid "Deleting a database if it has expired or is linked to a subscription is impossible. In that case, contact `Odoo Support <https://www.odoo.com/help>`_."
msgstr ""
#: ../../content/administration/odoo_online.rst:131
#: ../../content/administration/odoo_online.rst:132
msgid "Contact us"
msgstr ""
#: ../../content/administration/odoo_online.rst:133
#: ../../content/administration/odoo_online.rst:134
msgid "Access the `Odoo.com support page <https://www.odoo.com/help>`_ with the database's details already pre-filled."
msgstr ""
#: ../../content/administration/odoo_online.rst:139
#: ../../content/administration/odoo_online.rst:140
msgid "Invite / remove users"
msgstr ""
#: ../../content/administration/odoo_online.rst:141
#: ../../content/administration/odoo_online.rst:142
msgid "To invite users, fill out the new user's email address and click :guilabel:`Invite`. To add multiple users, click :guilabel:`Add more users`."
msgstr ""
@@ -709,18 +710,34 @@ msgstr ""
msgid "Inviting a user on a database"
msgstr ""
#: ../../content/administration/odoo_online.rst:147
#: ../../content/administration/odoo_online.rst:148
msgid "To remove users, select them and click :guilabel:`Remove`."
msgstr ""
#: ../../content/administration/odoo_online.rst:150
#: ../../content/administration/odoo_online.rst:151
msgid ":doc:`/applications/general/users`"
msgstr ""
#: ../../content/administration/odoo_online.rst:151
#: ../../content/administration/odoo_online.rst:152
msgid ":doc:`odoo_accounts`"
msgstr ""
#: ../../content/administration/odoo_online.rst:157
msgid "Web Services"
msgstr ""
#: ../../content/administration/odoo_online.rst:159
msgid "In order to programmatically retrieve the list of the databases displayed in the `database manager <https://www.odoo.com/my/databases>`_, call the method `list` of the model `odoo.database` via a :doc:`Web Service </developer/howtos/web_services>` call."
msgstr ""
#: ../../content/administration/odoo_online.rst:163
msgid "Inspired from the examples provided in the :doc:`Web Services </developer/howtos/web_services>` section, this is how to retrieve this list with the library ``xmlrpc.client``::"
msgstr ""
#: ../../content/administration/odoo_online.rst:176
msgid "And here is the equivalent example with JSON-RPC::"
msgstr ""
#: ../../content/administration/odoo_sh.rst:5
#: ../../content/administration/supported_versions.rst:30
#: ../../content/administration/upgrade.rst:22
@@ -3596,7 +3613,7 @@ msgid "We'll use 8 workers + 1 for cron. We'll also use a monitoring system to m
msgstr ""
#: ../../content/administration/on_premise/deploy.rst:243
msgid "RAM = 9 * ((0.8*150) + (0.2*1024)) ~= 3Go RAM for Odoo"
msgid "RAM = 9 * ((0.8*150) + (0.2*1024)) ~= 3GB RAM for Odoo"
msgstr ""
#: ../../content/administration/on_premise/deploy.rst:245
@@ -4109,46 +4126,34 @@ msgid "Supported Browsers"
msgstr ""
#: ../../content/administration/on_premise/deploy.rst:884
msgid "Odoo supports all the major desktop and mobile browsers available on the market, as long as they are supported by their publishers."
msgid "Odoo supports the latest version of the following browsers."
msgstr ""
#: ../../content/administration/on_premise/deploy.rst:887
msgid "Here are the supported browsers:"
msgstr ""
#: ../../content/administration/on_premise/deploy.rst:889
#: ../../content/administration/on_premise/deploy.rst:886
msgid "Google Chrome"
msgstr ""
#: ../../content/administration/on_premise/deploy.rst:890
#: ../../content/administration/on_premise/deploy.rst:887
msgid "Mozilla Firefox"
msgstr ""
#: ../../content/administration/on_premise/deploy.rst:891
#: ../../content/administration/on_premise/deploy.rst:888
msgid "Microsoft Edge"
msgstr ""
#: ../../content/administration/on_premise/deploy.rst:892
#: ../../content/administration/on_premise/deploy.rst:889
msgid "Apple Safari"
msgstr ""
#: ../../content/administration/on_premise/deploy.rst:894
msgid "Please make sure your browser is up-to-date and still supported by its publisher before filing a bug report."
msgstr ""
#: ../../content/administration/on_premise/deploy.rst:899
msgid "Since Odoo 13.0, ES6 is supported. Therefore, IE support is dropped."
msgstr ""
#: ../../content/administration/on_premise/deploy.rst:902
#: ../../content/administration/on_premise/deploy.rst:892
msgid "to have multiple Odoo installations use the same PostgreSQL database, or to provide more computing resources to both software."
msgstr ""
#: ../../content/administration/on_premise/deploy.rst:905
#: ../../content/administration/on_premise/deploy.rst:895
msgid "technically a tool like socat_ can be used to proxy UNIX sockets across networks, but that is mostly for software which can only be used over UNIX sockets"
msgstr ""
#: ../../content/administration/on_premise/deploy.rst:909
#: ../../content/administration/on_premise/deploy.rst:899
msgid "or be accessible only over an internal packet-switched network, but that requires secured switches, protections against `ARP spoofing`_ and precludes usage of WiFi. Even over secure packet-switched networks, deployment over HTTPS is recommended, and possible costs are lowered as \"self-signed\" certificates are easier to deploy on a controlled environment than over the internet."
msgstr ""

170
locale/sources/finance.pot
View File

@@ -8,7 +8,7 @@ msgid ""
msgstr ""
"Project-Id-Version: Odoo 16.0\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2025-03-27 08:53+0000\n"
"POT-Creation-Date: 2025-04-30 07:56+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"
@@ -5466,6 +5466,7 @@ msgid ":doc:`Internal transfers <payments/internal_transfers>`"
msgstr ""
#: ../../content/applications/finance/accounting/payments.rst:19
#: ../../content/applications/finance/accounting/vendor_bills.rst:119
msgid ":doc:`bank/reconciliation`"
msgstr ""
@@ -5622,7 +5623,6 @@ msgid ":guilabel:`Mark as fully paid`: Select an account in the :guilabel:`Post
msgstr ""
#: ../../content/applications/finance/accounting/payments.rst:-1
#: ../../content/applications/finance/accounting/vendor_bills.rst:-1
msgid "register a partial payment"
msgstr ""
@@ -10565,151 +10565,167 @@ msgid "Vendor bills"
msgstr ""
#: ../../content/applications/finance/accounting/vendor_bills.rst:7
msgid "In Odoo, we can register vendor bills **manually** or **automatically**, while the **Aged Payable report** provides an overview of all outstanding bills to help us pay the correct amounts on time."
msgid "Vendor bills can be registered either **manually** or **automatically** in Odoo. The :ref:`Aged Payable report <accounting/vendor_bills/age-payable-report>` provides an overview of all outstanding bills to help ensure timely payment of the correct amounts."
msgstr ""
#: ../../content/applications/finance/accounting/vendor_bills.rst:12
msgid "Tutorial `Registering a vendor bill <https://www.odoo.com/slides/slide/registering-a-vendor-bill-1683?fullscreen=1>`_"
msgid "Tutorial `Registering a vendor bill <https://www.odoo.com/slides/slide/register-a-vendor-bill-6582>`_"
msgstr ""
#: ../../content/applications/finance/accounting/vendor_bills.rst:13
msgid ":doc:`/applications/inventory_and_mrp/purchase/manage_deals/manage`"
msgstr ""
#: ../../content/applications/finance/accounting/vendor_bills.rst:16
#: ../../content/applications/finance/accounting/vendor_bills.rst:18
msgid "Bill creation"
msgstr ""
#: ../../content/applications/finance/accounting/vendor_bills.rst:19
#: ../../content/applications/finance/accounting/vendor_bills.rst:23
msgid "Manually"
msgstr ""
#: ../../content/applications/finance/accounting/vendor_bills.rst:21
msgid "Create a vendor bill manually by going to :menuselection:`Accounting --> Vendors --> Bills` and clicking :guilabel:`Create`."
msgstr ""
#: ../../content/applications/finance/accounting/vendor_bills.rst:25
msgid "Automatically"
msgid "To create a vendor bill manually, go to :menuselection:`Accounting --> Vendors --> Bills` and click :guilabel:`New`."
msgstr ""
#: ../../content/applications/finance/accounting/vendor_bills.rst:27
msgid "Vendor bills can be automatically created by **sending an email** to an :ref:`email alias <invoice-digitization/email-alias>` associated with the purchase journal, or by **uploading a PDF** in :menuselection:`Accounting --> Vendors --> Bills` and then clicking :guilabel:`Upload`."
#: ../../content/applications/finance/accounting/vendor_bills.rst:29
msgid "Alternatively, it is possible to create a vendor bill from the Accounting dashboard:"
msgstr ""
#: ../../content/applications/finance/accounting/vendor_bills.rst:31
msgid "either click :guilabel:`Create Manually` on the :guilabel:`Vendor Bills` journal;"
msgstr ""
#: ../../content/applications/finance/accounting/vendor_bills.rst:32
msgid "Bill completion"
msgid "or click the :icon:`fa-ellipsis-v` :guilabel:`(vertical ellipsis)` icon of the :guilabel:`Vendor Bills` journal, then :guilabel:`Bill` under the :guilabel:`New` section."
msgstr ""
#: ../../content/applications/finance/accounting/vendor_bills.rst:34
msgid "Whether the bill is created manually or automatically, make sure the following fields are appropriately completed:"
#: ../../content/applications/finance/accounting/vendor_bills.rst:38
msgid "Automatically"
msgstr ""
#: ../../content/applications/finance/accounting/vendor_bills.rst:37
msgid ":guilabel:`Vendor`: Odoo automatically fills some information based on the vendor's registered information, previous purchase orders, or bills."
msgstr ""
#: ../../content/applications/finance/accounting/vendor_bills.rst:39
msgid ":guilabel:`Bill Reference`: add the sales order reference provided by the vendor and is used to do the :ref:`matching <accounting/payments/matching>` when you receive the products."
msgstr ""
#: ../../content/applications/finance/accounting/vendor_bills.rst:41
msgid ":guilabel:`Auto-Complete`: select a past bill/purchase order to automatically complete the document. The :guilabel:`Vendor` field should be completed prior to completing this field."
msgstr ""
#: ../../content/applications/finance/accounting/vendor_bills.rst:43
msgid ":guilabel:`Bill Date`: is the issuance date of the document."
msgstr ""
#: ../../content/applications/finance/accounting/vendor_bills.rst:44
msgid ":guilabel:`Accounting Date`: is the date on which the document is registered in your accounting."
#: ../../content/applications/finance/accounting/vendor_bills.rst:40
msgid "Vendor bills can be automatically created by **sending an email** to an :ref:`email alias <invoice-digitization/email-alias>` associated with the purchase journal, or by **uploading a PDF** in :menuselection:`Accounting --> Vendors --> Bills` and then clicking :guilabel:`Upload`."
msgstr ""
#: ../../content/applications/finance/accounting/vendor_bills.rst:45
msgid ":guilabel:`Payment Reference`: when registering the payment, it is automatically indicated in the :guilabel:`Memo` field."
msgid "Once the bill is uploaded, the PDF document appears on the right side of the screen, making it easy to fill in the bill information."
msgstr ""
#: ../../content/applications/finance/accounting/vendor_bills.rst:47
msgid ":guilabel:`Recipient Bank`: to indicate to which account number the payment has to be made."
msgid "Bills can be :doc:`digitized <vendor_bills/invoice_digitization>` for automatic completion."
msgstr ""
#: ../../content/applications/finance/accounting/vendor_bills.rst:48
msgid ":guilabel:`Due Date` or :guilabel:`Terms` to pay the bill."
msgid "Services such as digitizing scanned or PDF vendor bills in Odoo require :doc:`In-App Purchase (IAP) </applications/essentials/in_app_purchase>` credit or tokens."
msgstr ""
#: ../../content/applications/finance/accounting/vendor_bills.rst:49
msgid ":guilabel:`Journal`: select in which journal the bill should be recorded and the :doc:`Currency <get_started/multi_currency>`."
#: ../../content/applications/finance/accounting/vendor_bills.rst:54
msgid "Bill completion"
msgstr ""
#: ../../content/applications/finance/accounting/vendor_bills.rst:56
msgid "Whether the bill is created manually or automatically, make sure the following fields are appropriately completed:"
msgstr ""
#: ../../content/applications/finance/accounting/vendor_bills.rst:59
msgid ":guilabel:`Vendor`: Odoo automatically fills in some information based on the information on the vendor's contact record as well as previous purchase orders and bills."
msgstr ""
#: ../../content/applications/finance/accounting/vendor_bills.rst:61
msgid ":guilabel:`Bill Reference`: Add the sales order reference provided by the vendor. This field is used to :ref:`match <accounting/payments/matching>` the products when they are received."
msgstr ""
#: ../../content/applications/finance/accounting/vendor_bills.rst:63
msgid ":guilabel:`Auto-Complete`: Select a past bill/purchase order to complete the document automatically. The :guilabel:`Vendor` field should be completed before completing this field."
msgstr ""
#: ../../content/applications/finance/accounting/vendor_bills.rst:65
msgid ":guilabel:`Bill Date`: Select the document's issuance date."
msgstr ""
#: ../../content/applications/finance/accounting/vendor_bills.rst:66
msgid ":guilabel:`Accounting Date`: Update the document's accounting registration date if needed."
msgstr ""
#: ../../content/applications/finance/accounting/vendor_bills.rst:67
msgid ":guilabel:`Payment Reference`: Automatically indicated in the :guilabel:`Memo` field when"
msgstr ""
#: ../../content/applications/finance/accounting/vendor_bills.rst:68
msgid "registering the payment."
msgstr ""
#: ../../content/applications/finance/accounting/vendor_bills.rst:69
msgid ":guilabel:`Recipient Bank`: Indicates the account number to which the payment will be made. This field is required when paying via batch payment files (such as NACHA and :doc:`SEPA <payments/pay_sepa>`)."
msgstr ""
#: ../../content/applications/finance/accounting/vendor_bills.rst:72
msgid ":guilabel:`Due Date` or :guilabel:`Terms` for paying the bill."
msgstr ""
#: ../../content/applications/finance/accounting/vendor_bills.rst:73
msgid ":guilabel:`Journal`: Select which journal should record the bill and in which :doc:`currency <get_started/multi_currency>`."
msgstr ""
#: ../../content/applications/finance/accounting/vendor_bills.rst:-1
msgid "filling the vendor bill"
msgstr ""
#: ../../content/applications/finance/accounting/vendor_bills.rst:56
msgid "Bills can be :doc:`digitized <vendor_bills/invoice_digitization>` for automatic completion by clicking :guilabel:`Send for Digitization`."
#: ../../content/applications/finance/accounting/vendor_bills.rst:80
msgid "Multiple bills for the same purchase order may be issued if the vendor is on back-order and sends invoices as products are shipped or if the vendor sends partial bills or requests a deposit. In this case, multiple bills may have the same :guilabel:`Bill Reference`."
msgstr ""
#: ../../content/applications/finance/accounting/vendor_bills.rst:58
msgid "If you upload the bill, the PDF document is displayed on the right of the screen, allowing you to easily fill in the bill information."
msgstr ""
#: ../../content/applications/finance/accounting/vendor_bills.rst:62
#: ../../content/applications/finance/accounting/vendor_bills.rst:87
msgid "Bill confirmation"
msgstr ""
#: ../../content/applications/finance/accounting/vendor_bills.rst:64
msgid "Click :guilabel:`Confirm` when the document is completed. The status of your document changes to :guilabel:`Posted` and a journal entry is generated based on the configuration on the invoice."
#: ../../content/applications/finance/accounting/vendor_bills.rst:89
msgid "Click :guilabel:`Confirm` when the document is completed. The status changes to :guilabel:`Posted`, and a journal entry is generated based on the vendor bill information."
msgstr ""
#: ../../content/applications/finance/accounting/vendor_bills.rst:68
msgid "Once confirmed, it is no longer possible to update it. Click :guilabel:`Reset to draft` if changes are required."
#: ../../content/applications/finance/accounting/vendor_bills.rst:93
msgid "Once confirmed, a vendor bill can no longer be updated. Click :guilabel:`Reset to draft` if changes are required."
msgstr ""
#: ../../content/applications/finance/accounting/vendor_bills.rst:72
msgid "Bill Payment"
#: ../../content/applications/finance/accounting/vendor_bills.rst:99
msgid "Payment and reconciliation"
msgstr ""
#: ../../content/applications/finance/accounting/vendor_bills.rst:74
msgid "Upon payment of the vendor bill, click on :guilabel:`Register Payment` to open a new payment window."
#: ../../content/applications/finance/accounting/vendor_bills.rst:101
msgid "To register a payment, click on :guilabel:`Register Payment`. In the :guilabel:`Register Payment` window, select the :guilabel:`Journal`, the :guilabel:`Payment Method`, the :guilabel:`Amount`, and the :guilabel:`Currency`."
msgstr ""
#: ../../content/applications/finance/accounting/vendor_bills.rst:76
msgid "Select the :guilabel:`Journal`, the :guilabel:`Payment Method`, the :guilabel:`Amount` you wish to pay (full or partial payment), and the :guilabel:`Currency`. In the case of a partial payment (when the :guilabel:`Amount` paid is less than the total remaining amount on the vendor bill), the :guilabel:`Payment Difference` field displays the outstanding balance. You have two options:"
#: ../../content/applications/finance/accounting/vendor_bills.rst:105
msgid "When the :guilabel:`Amount` paid is less than the total remaining amount on the vendor bill, the payment is :ref:`partial <accounting/payments/partial-payment>`, and the :guilabel:`Payment Difference` field displays the outstanding balance."
msgstr ""
#: ../../content/applications/finance/accounting/vendor_bills.rst:82
msgid ":guilabel:`Keep open`: to keep the bill open and mark it with a :guilabel:`Partial` banner;"
#: ../../content/applications/finance/accounting/vendor_bills.rst:109
msgid "The :guilabel:`Memo` field is filled automatically if the :guilabel:`Payment Reference` has been set correctly on the vendor bill. If the field is empty, select the vendor invoice number as a reference."
msgstr ""
#: ../../content/applications/finance/accounting/vendor_bills.rst:83
msgid ":guilabel:`Mark as fully paid`: In this case, select an account in the :guilabel:`Post Difference In` field and change the :guilabel:`Label` if needed. A journal entry will be created to balance the account receivable with the selected account."
#: ../../content/applications/finance/accounting/vendor_bills.rst:113
msgid "Then click :guilabel:`Create payment`. An :guilabel:`In Payment`/:guilabel:`Partial` banner appears on the bill until it is :doc:`reconciled <bank/reconciliation>` and its status updates to :guilabel:`Paid`."
msgstr ""
#: ../../content/applications/finance/accounting/vendor_bills.rst:90
msgid "The :guilabel:`Memo` field is filled automatically if the :guilabel:`Payment Reference` has been set correctly in the vendor bill. If the field is empty, select the vendor invoice number as a reference."
#: ../../content/applications/finance/accounting/vendor_bills.rst:118
msgid ":doc:`payments`"
msgstr ""
#: ../../content/applications/finance/accounting/vendor_bills.rst:94
msgid "Once confirmed, an :guilabel:`In Payment` banner appears on the bill until it is :doc:`reconciled <bank/reconciliation>`."
msgstr ""
#: ../../content/applications/finance/accounting/vendor_bills.rst:98
#: ../../content/applications/finance/accounting/vendor_bills.rst:124
msgid "Aged payable report"
msgstr ""
#: ../../content/applications/finance/accounting/vendor_bills.rst:100
msgid "To get an overview of your open vendor bills and their related due dates, you can use the **Aged Payable report**. Go to :menuselection:`Accounting --> Reporting --> Partner Reports: Aged payable`."
#: ../../content/applications/finance/accounting/vendor_bills.rst:126
msgid "To get an overview of the open vendor bills and their due dates, go to :menuselection:`Accounting --> Reporting --> Aged payable`."
msgstr ""
#: ../../content/applications/finance/accounting/vendor_bills.rst:104
msgid "Click on a vendor's name to open up the details of all outstanding bills, the amounts due, the due dates, etc."
#: ../../content/applications/finance/accounting/vendor_bills.rst:129
msgid "Click the :icon:`fa-caret-right` :guilabel:`(right arrow)` icon next to a vendor to view the details of all their outstanding bills, including the due dates and amounts."
msgstr ""
#: ../../content/applications/finance/accounting/vendor_bills.rst:108
msgid "By clicking the :guilabel:`Save` button, you can export the information available on the screen as a PDF or XLSX file and save it in the folder of your choice."
msgstr ""
#: ../../content/applications/finance/accounting/vendor_bills.rst:110
msgid "You might receive several bills for the same purchase order if your vendor is in back-order and is sending you invoices as they ship the products, or if your vendor is sending you a partial bill or asking for a deposit."
#: ../../content/applications/finance/accounting/vendor_bills.rst:133
msgid "Click :guilabel:`PDF` or :guilabel:`XLSX` to generate a PDF or XLSX file, respectively."
msgstr ""
#: ../../content/applications/finance/accounting/vendor_bills/assets.rst:3

385
locale/sources/inventory_and_mrp.pot
View File

@@ -8,7 +8,7 @@ msgid ""
msgstr ""
"Project-Id-Version: Odoo 16.0\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2025-03-27 08:53+0000\n"
"POT-Creation-Date: 2025-04-30 07:56+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"
@@ -4746,130 +4746,137 @@ msgid "Inbound and outbound flows"
msgstr ""
#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations.rst:8
msgid "There are several ways to handle how a warehouse receives products (receipts) and ships products (deliveries). Depending on several factors, such as the type of products stocked and sold, warehouse size, and the amount of daily confirmed receipts and delivery orders, the way products are handled when coming in and out of the warehouse can vary a lot. Different settings can be configured for receipts and deliveries; they do not have to be configured to have the same number of steps."
msgid "Configuring inbound and outbound flows in Odoo is key to optimizing efficiency, traceability, and cost. Warehouse managers must balance speed and control, choosing between a streamlined process or added checkpoints."
msgstr ""
#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations.rst:12
msgid "Odoo offers one-step, two-step, and three-step flows, with more steps providing greater control but increasing operations. The best setup depends on quality checks, packaging, and warehouse size."
msgstr ""
#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations.rst:15
msgid "`Using Routes (eLearning Tutorial) <https://www.odoo.com/slides/slide/using-routes-1018>`_"
msgid "This guide helps businesses determine the most suitable configuration."
msgstr ""
#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations.rst:16
msgid "`Push & Pull Rules (eLearning Tutorial) <https://www.odoo.com/slides/slide/push-pull-rules-1024>`_"
msgstr ""
#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations.rst:20
msgid "Choosing the right inventory flow to handle receipts and deliveries"
msgstr ""
#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations.rst:22
msgid "By default, Odoo handles shipping and receiving in three different ways: in one, two, or three steps. The simplest configuration is one step, which is the default. Each additional step required for a warehouse for either the receiving or shipping process will add an additional layer of operations to perform before a product is either received or shipped. These configurations depend entirely on the requirements for the products stored, such as performing quality checks on received products, or using special packaging on shipped products."
msgstr ""
#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations.rst:30
#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations.rst:18
msgid "One-step flow"
msgstr ""
#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations.rst:20
msgid "The *one-step inventory flow* is the simplest option, with minimal handling steps and the least traceability. In this setup, products move directly from vendors to stock or from stock to customers, with Odoo only tracking when items enter or leave the warehouse. This makes it ideal for businesses with high-volume, low-risk products or fast-moving operations where additional validation steps aren’t necessary."
msgstr ""
#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations.rst:26
msgid "**Receiving**: Products go directly into stock."
msgstr ""
#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations.rst:27
msgid "**Shipping**: Products ship directly from stock."
msgstr ""
#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations.rst:28
msgid "**Best for**: Small warehouses, low stock levels, and non-perishable items, where minimal processing is needed before products are stored or shipped."
msgstr ""
#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations.rst:32
msgid "The receiving and shipping rules for a one-step configuration are as follows:"
msgstr ""
#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations.rst:34
msgid "**Receipt**: Receive products directly into stock. No intermediate steps between receipt and stock occur, such as a transfer to a quality control location."
msgstr ""
#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations.rst:36
msgid "**Shipping**: Ship products directly from stock. No intermediate steps between stock and shipping occur, such as a transfer to a packing location."
msgstr ""
#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations.rst:38
msgid "Can only be used if not using :abbr:`FIFO (First In, First Out)`, :abbr:`LIFO (Last In, First Out)`, or :abbr:`FEFO (First Expired, First Out)` removal strategies."
msgstr ""
#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations.rst:40
msgid "Receipts and/or deliveries are handled quickly."
msgstr ""
#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations.rst:41
msgid "Recommended for small warehouses with low stock levels, and for non-perishable items."
msgstr ""
#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations.rst:42
msgid "Items are received or shipped directly into/from stock."
msgstr ""
#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations.rst:45
msgid ":doc:`daily_operations/receipts_delivery_one_step`"
msgstr ""
#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations.rst:48
#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations.rst:35
msgid "Two-step flow"
msgstr ""
#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations.rst:37
msgid "A *two-step flow* adds an input or output area for processing products before storage or shipment. Incoming goods can be unboxed and inspected before shelving, while outgoing shipments are sorted and consolidated before dispatch. This setup improves efficiency by assigning storage teams to picking and stocking, while dedicated teams handle unboxing, (possibly) packing, and final verification to reduce order fulfillment errors."
msgstr ""
#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations.rst:43
msgid "**Receiving**: Products move to an *input* area before being transferred into stock."
msgstr ""
#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations.rst:45
msgid "Until transferred, received products are not automatically reserved for manufacturing, shipping, or other operations."
msgstr ""
#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations.rst:48
msgid "**Shipping**: Products move to an *output* before shipping to allow for :doc:`sorting or consolidation <picking_methods>`."
msgstr ""
#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations.rst:50
msgid "The receiving and shipping rules for a two-step configuration are as follows:"
msgid "**Best for**: Large warehouses, high stock levels, bulky items, and workflows that separate receiving from storage to improve organization and efficiency."
msgstr ""
#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations.rst:52
msgid "**Input + stock**: Bring products to an input location *before* moving into stock. Products can be organized by different internal storage locations, such as various shelves, freezers, and locked areas, before being stocked in the warehouse."
msgstr ""
#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations.rst:55
msgid "**Pick + ship**: Bring products to an output location before shipping. Packages can be organized by different carriers or shipping docks before being shipped."
msgstr ""
#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations.rst:57
msgid "Minimum requirement to use lot numbers or serial numbers to track products with a :abbr:`FIFO (First In, First Out)`, :abbr:`LIFO (Last In, First Out)` or :abbr:`FEFO (First Expired, First Out)` removal strategy."
msgstr ""
#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations.rst:60
msgid "Recommended for larger warehouses with high stock levels, or when stocking large items (such as mattresses, large furniture, heavy machinery, etc.)."
msgstr ""
#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations.rst:62
#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations.rst:83
msgid "Products received will not be available for manufacturing, shipping, etc., until they are transferred into stock."
msgstr ""
#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations.rst:66
#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations.rst:54
msgid ":doc:`daily_operations/receipts_delivery_two_steps`"
msgstr ""
#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations.rst:69
#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations.rst:57
msgid "Three-step flow"
msgstr ""
#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations.rst:59
msgid "A three-step flow builds on the two-step process by adding a quality check and packing area, enforcing stricter processes and improving oversight."
msgstr ""
#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations.rst:63
msgid "While this setup enhances process control, separating picking and packing requires validation at each step. If the same person handles both, it may cause redundancy and slow operations."
msgstr ""
#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations.rst:66
msgid "Quality checks and packing do not require a three-step flow. Enable :doc:`quality control points <../../quality/quality_management/quality_control_points>` separately or activate the :ref:`Packages feature <inventory/warehouses_storage/enable-package>` in Odoo to incorporate these processes without adding extra transfer steps."
msgstr ""
#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations.rst:71
msgid "The receiving and shipping rules for a three-step configuration are as follows:"
msgid "**Receiving**: Products follow a structured process: *input area* → *quality control* → *stock*."
msgstr ""
#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations.rst:73
msgid "**Input + quality + stock**: Receive products at the input location, transfer them to a quality control area, and move the ones that pass inspection into stock."
#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations.rst:72
msgid "**Shipping**: Products are *picked*, *packed*, and then *shipped*, ensuring proper handling and organization."
msgstr ""
#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations.rst:75
msgid "**Pick + pack + ship**: Pick products according to their removal strategy, pack them in a dedicated packing area, and bring them to an output location for shipping."
#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations.rst:74
msgid "**Best for**: Very large warehouses with strict quality control requirements, dedicated picking and packing workflows, and a need for clear traceability across multiple handling stages. Suitable when multiple teams manage different steps before products are stocked or shipped."
msgstr ""
#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations.rst:77
msgid "Can be used when tracking products by lot or serial numbers when using a :abbr:`FIFO (First In, First Out)`, :abbr:`LIFO (Last In, First Out)`, or :abbr:`FEFO (First Expired, First Out)` removal strategy."
msgstr ""
#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations.rst:80
msgid "Recommended for very large warehouses with very high stock levels."
msgstr ""
#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations.rst:81
msgid "Required for any warehouse needing to perform quality control inspections before receiving items into stock."
msgstr ""
#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations.rst:87
#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations.rst:79
msgid ":doc:`daily_operations/receipts_three_steps`"
msgstr ""
#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations.rst:88
#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations.rst:80
msgid ":doc:`daily_operations/delivery_three_steps`"
msgstr ""
#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations.rst:83
msgid "Add-ons"
msgstr ""
#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations.rst:85
msgid "To optimize each flow, Odoo provides additional features that can enhance the process."
msgstr ""
#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations.rst:88
msgid "Storage"
msgstr ""
#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations.rst:90
msgid "To organize and store products efficiently, use:"
msgstr ""
#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations.rst:111
msgid "Delivery"
msgstr ""
#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations.rst:113
msgid "Tailor the outgoing shipment process to fit the business needs. Picking methods and removal strategies control how products are reserved for orders, while cross-docking and dropshipping determine how they move. Configuring these options in Odoo ensures visibility into product movement and confirms that items reach customers efficiently."
msgstr ""
#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations.rst:141
msgid "Customization"
msgstr ""
#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations.rst:143
msgid "Odoo's flexible framework enables businesses to tailor workflows to match specific operational needs."
msgstr ""
#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/daily_operations/cross_dock.rst:3
msgid "Organize a cross-dock in a warehouse"
msgstr ""
@@ -8144,39 +8151,191 @@ msgid ":doc:`multipack`"
msgstr ""
#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/dhl_credentials.rst:3
msgid "How to get DHL credentials for integration with Odoo?"
msgid "DHL integration"
msgstr ""
#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/dhl_credentials.rst:5
msgid "In order to use the Odoo DHL API, you will need:"
msgstr ""
#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/dhl_credentials.rst:7
msgid "A DHL.com SiteID"
msgstr ""
#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/dhl_credentials.rst:9
msgid "A DHL Password"
msgid "DHL is one of the shipping carriers for which a *shipping connector* is available in Odoo's **Inventory** app. By enabling the shipping connector in the app's settings, and configuring at least one *shipping method*, the process of :doc:`calculating shipping rates <../setup_configuration>` and :doc:`generating shipping labels <labels>` is greatly simplified."
msgstr ""
#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/dhl_credentials.rst:11
msgid "A DHL Account Number"
msgstr ""
#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/dhl_credentials.rst:15
msgid "Getting SiteID and password for countries other than United States (UK and Rest of the world)"
msgid "While a variety of shipping connectors are available for different carriers, this documentation details the configuration settings specific to integrating DHL. For instructions on configuring the integration settings common to all shippers, see the documentation on :doc:`third-party shippers <third_party_shipper>`."
msgstr ""
#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/dhl_credentials.rst:17
msgid "You should contact DHL account manager and request integration for XML Express API. The presales should provide you live credentials."
msgid "Enable DHL shipping connector"
msgstr ""
#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/dhl_credentials.rst:20
msgid "Getting SiteID and Password for United States"
#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/dhl_credentials.rst:19
msgid "Before creating a DHL shipping method, enable the carrier's shipping connector. To do so, navigate to :menuselection:`Inventory app --> Configuration --> Settings`."
msgstr ""
#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/dhl_credentials.rst:22
msgid "You need to write to xmlrequests@dhl.com along with your full Account details like account number, region, address, etc. to get API Access."
msgid "Scroll down to the :guilabel:`Shipping Connectors` section, and tick the checkbox next to :guilabel:`DHL Express Connector`. Finally, click :guilabel:`Save` to apply the changes."
msgstr ""
#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/dhl_credentials.rst:25
msgid "Once the connector has been enabled, a :icon:`fa-arrow-right` :guilabel:`DHL Shipping Methods` link appears below the setting. Click the link to open a page showing all shipping methods configured for DHL."
msgstr ""
#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/dhl_credentials.rst:30
msgid "Configure DHL shipping method"
msgstr ""
#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/dhl_credentials.rst:32
msgid "After enabling the shipping connector for DHL, shipping methods can be configured for the carrier. Once configured, a shipping method can be added as a line item to sales orders (SOs), which allows for automatic computation of shipping rates, and generation of shipping labels."
msgstr ""
#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/dhl_credentials.rst:36
msgid "To create a new DHL shipping method, navigate to :menuselection:`Inventory app --> Configuration --> Settings`. In the :guilabel:`Shipping Connectors` section, select the :guilabel:`DHL Shipping Methods` link below the :guilabel:`DHL Express Connector` checkbox."
msgstr ""
#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/dhl_credentials.rst:41
msgid "It is also possible to see existing shipping methods for every carrier, by navigating to :menuselection:`Inventory app --> Configuration --> Shipping Methods`."
msgstr ""
#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/dhl_credentials.rst:44
msgid "Click :guilabel:`New` to open a blank shipping method form. If a shipping method has already been created, it can be selected from this screen."
msgstr ""
#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/dhl_credentials.rst:-1
msgid "The form for a DHL shipping method."
msgstr ""
#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/dhl_credentials.rst:51
msgid "General information"
msgstr ""
#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/dhl_credentials.rst:53
msgid "Begin configuring the shipping method by entering its title in the :guilabel:`Shipping Method` field."
msgstr ""
#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/dhl_credentials.rst:56
msgid "In the :guilabel:`Provider` drop-down menu, select the :guilabel:`DHL` option. After doing so, a new :guilabel:`DHL Configuration` tab appears at the bottom of the form."
msgstr ""
#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/dhl_credentials.rst:59
msgid "All other fields in this section are identical on the shipping method forms for each shipping carrier. See the documentation on :doc:`third-party shippers <third_party_shipper>` for instructions on how to properly configure them."
msgstr ""
#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/dhl_credentials.rst:64
msgid "DHL Configuration"
msgstr ""
#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/dhl_credentials.rst:66
msgid "The :guilabel:`DHL Configuration` tab on the shipping method form is used to connect the user's DHL account to Odoo, and configure the shipping method's details."
msgstr ""
#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/dhl_credentials.rst:70
msgid "DHL SiteID, password, and account number"
msgstr ""
#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/dhl_credentials.rst:72
msgid "A DHL SiteID, password, and account number are used to link a DHL account with third-party services, like Odoo's **Inventory** app."
msgstr ""
#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/dhl_credentials.rst:76
msgid "The SiteID and password are different credentials than the ones used to log in to a DHL account."
msgstr ""
#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/dhl_credentials.rst:78
msgid "Here are two ways to obtain these DHL account credentials:"
msgstr ""
#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/dhl_credentials.rst:80
msgid "**If a DHL Express account is available**: Log into the `DHL Developer portal <https://developer.dhl.com/api-reference/dhl-express-mydhl-api#get-started-section/ user-guide%get-access>`_, and then `request a DHL API account number <https://developer.dhl. com/form/dhl-express-onboarding>`_."
msgstr ""
#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/dhl_credentials.rst:84
msgid "**If a DHL Express account is unavailable**: Follow DHL's steps to `obtain a DHL Express account <https://developer.dhl.com/api-reference/dhl-express-mydhl-api#get-started-section/user-guide%get- access:~:text=around%20the%20world.-,User%20Guide,-Get%20Access>`_, and then follow the steps in the previous bullet."
msgstr ""
#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/dhl_credentials.rst:89
msgid "Once the developer portal account has been confirmed, log in to the portal using the username and password. Click on the user avatar in the top-right corner of the screen to open the user dashboard."
msgstr ""
#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/dhl_credentials.rst:92
msgid "On the dashboard, click on the :guilabel:`Apps` tab, and select an app. In the :guilabel:`Credentials` section, click the :guilabel:`Show key` button below the :guilabel:`API Key` and :guilabel:`API Secret` fields."
msgstr ""
#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/dhl_credentials.rst:96
msgid "Return to the shipping method form in the Odoo database. Enter the *DHL API Key* in the :guilabel:`DHL SiteID` field, and the *API Secret* in the :guilabel:`DHL Password` field."
msgstr ""
#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/dhl_credentials.rst:100
msgid "Shipping details"
msgstr ""
#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/dhl_credentials.rst:102
msgid "The rest of the fields in the :guilabel:`DHL Configuration` tab are used to configure the shipping method itself:"
msgstr ""
#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/dhl_credentials.rst:105
msgid ":guilabel:`Region`: the region in which the shipping method is used."
msgstr ""
#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/dhl_credentials.rst:106
msgid ":guilabel:`DHL Product`: the shipping service purchased from DHL (e.g. Express Worldwide)."
msgstr ""
#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/dhl_credentials.rst:107
msgid ":guilabel:`DHL Package Type`: the type of DHL package used for delivery (e.g. DHL Box)."
msgstr ""
#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/dhl_credentials.rst:108
msgid ":guilabel:`Package Weight Unit`: the unit of measure used to display package weight."
msgstr ""
#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/dhl_credentials.rst:109
msgid ":guilabel:`Package Dimension Unit`: the unit of measure used to display package size."
msgstr ""
#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/dhl_credentials.rst:110
msgid ":guilabel:`Label Format`: the file format used to generate shipping labels."
msgstr ""
#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/dhl_credentials.rst:111
msgid ":guilabel:`Label Template`: the paper size used to print shipping labels."
msgstr ""
#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/dhl_credentials.rst:114
msgid "Before selecting service options for a shipping method, make sure those services are actually available for the DHL account. Available services depend on the contract negotiated with DHL."
msgstr ""
#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/dhl_credentials.rst:118
msgid "Options"
msgstr ""
#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/dhl_credentials.rst:120
msgid "Additional settings are available in the :guilabel:`Options` section at the bottom of the :guilabel:`DHL Configuration` tab:"
msgstr ""
#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/dhl_credentials.rst:123
msgid ":guilabel:`Generate Return Label`: Enable this option to automatically generate a return label after validating a delivery order."
msgstr ""
#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/dhl_credentials.rst:125
msgid ":guilabel:`Dutiable Material`: Enable this option if the shipping method is liable to customs or other duties."
msgstr ""
#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/dhl_credentials.rst:129
msgid "Turn on the DHL Connection"
msgstr ""
#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/dhl_credentials.rst:131
msgid "Once the DHL connection is set up, use the buttons at the top of the form to turn on or debug the connection."
msgstr ""
#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/dhl_credentials.rst:134
msgid "**Unpublished/Published**: turns the connection on or off."
msgstr ""
#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/dhl_credentials.rst:135
msgid "**Test Environment/Production Environment**: sets whether requests actually get sent to DHL."
msgstr ""
#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/dhl_credentials.rst:136
msgid "**No Debug/Debug Requests**: determines whether error logging occurs for requests to DHL."
msgstr ""
#: ../../content/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/invoicing.rst:3
@@ -9664,26 +9823,26 @@ msgid "View locations in Odoo"
msgstr ""
#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management.rst:109
msgid "Odoo databases include pre-configured view locations to organize the hierarchy of locations. These provide helpful context, and distinguish between internal and external locations."
msgid "Odoo databases include preconfigured view locations to organize the hierarchy of locations. These provide helpful context, and distinguish between internal and external locations."
msgstr ""
#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management.rst:112
msgid "*Physical locations* serve as an umbrella for external locations, without changing a product's inventory value. (Inventory valuation changes occur when products move from internal to external locations)."
msgid "*Physical locations* group internal locations—such as secondary warehouses and subcontractor sites. Because :doc:`inventory valuation <../product_management/inventory_valuation/inventory_valuation_config>` changes only when goods move from internal to external locations, Odoo uses physical locations to track stock that is off-site or in transit without affecting valuation."
msgstr ""
#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management.rst:119
#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management.rst:121
msgid "When moving products in warehouses `WH` and `WH2`, the items are not in either warehouse, but still belong to the company. While in transit, they are placed in the `Inter-warehouse transit` location, a :guilabel:`Transit Location` type."
msgstr ""
#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management.rst:123
#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management.rst:125
msgid "This location is under the view location, `Physical Locations`, indicating that `Inter-warehouse transit` is outside of a warehouse, but still part of the company. Doing so does not affect the inventory valuation of the products."
msgstr ""
#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management.rst:127
#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management.rst:129
msgid "*Partner locations* group customer and vendor locations (external locations) together. Transfers to these locations affect inventory valuation."
msgstr ""
#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management.rst:129
#: ../../content/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_management.rst:131
msgid "*Virtual locations* are locations that do **not** exist physically, but it is where items that are not in inventory can be placed. These can be items that are no longer in inventory due to loss, or other factors."
msgstr ""

468
locale/sources/marketing.pot
View File

@@ -8,7 +8,7 @@ msgid ""
msgstr ""
"Project-Id-Version: Odoo 16.0\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2025-01-27 14:31+0000\n"
"POT-Creation-Date: 2025-04-30 07:56+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"
@@ -353,7 +353,7 @@ msgid "View of how recipient filters can be customized in Odoo Email Marketing."
msgstr ""
#: ../../content/applications/marketing/email_marketing.rst:260
#: ../../content/applications/marketing/events/event_essentials.rst:193
#: ../../content/applications/marketing/events/event_essentials.rst:195
msgid "Some sub-menu options in the first rule field allow for a second choice to provide even more specificity."
msgstr ""
@@ -945,6 +945,7 @@ msgid "Create event booths, sell their availability, and manage reservations wit
msgstr ""
#: ../../content/applications/marketing/events/event_booths.rst:9
#: ../../content/applications/marketing/events/event_tracks.rst:14
#: ../../content/applications/marketing/events/sell_tickets.rst:10
#: ../../content/applications/marketing/events/track_manage_talks.rst:9
msgid "Configuration"
@@ -1302,75 +1303,75 @@ msgstr ""
msgid "Overview of events setting with the kanban view in Odoo Events."
msgstr ""
#: ../../content/applications/marketing/events/event_essentials.rst:36
#: ../../content/applications/marketing/events/event_essentials.rst:38
msgid "Create a new event"
msgstr ""
#: ../../content/applications/marketing/events/event_essentials.rst:38
#: ../../content/applications/marketing/events/event_essentials.rst:40
msgid "To create an event, click :guilabel:`Create` from the Events dashboard. Odoo will then direct the page to a blank event template form."
msgstr ""
#: ../../content/applications/marketing/events/event_essentials.rst:41
#: ../../content/applications/marketing/events/event_essentials.rst:43
msgid "From the event form, fill out the necessary fields, either by choosing from existing data in the Odoo database or by creating and editing new field data. Key information to enter for the event includes:"
msgstr ""
#: ../../content/applications/marketing/events/event_essentials.rst:45
#: ../../content/applications/marketing/events/event_essentials.rst:47
msgid ":guilabel:`Event Name`: give the event a title."
msgstr ""
#: ../../content/applications/marketing/events/event_essentials.rst:46
#: ../../content/applications/marketing/events/event_essentials.rst:48
msgid ":guilabel:`Date`: when the event is scheduled to take place (expressed in your local timezone on the form view)."
msgstr ""
#: ../../content/applications/marketing/events/event_essentials.rst:48
#: ../../content/applications/marketing/events/event_essentials.rst:50
msgid ":guilabel:`Display Timezone`: indicates the timezone in which the event dates/times will be displayed on the website."
msgstr ""
#: ../../content/applications/marketing/events/event_essentials.rst:50
#: ../../content/applications/marketing/events/event_essentials.rst:52
msgid ":guilabel:`Template`: choose from a pre-built event template or build a custom one and connect it here."
msgstr ""
#: ../../content/applications/marketing/events/event_essentials.rst:52
#: ../../content/applications/marketing/events/event_essentials.rst:54
msgid ":guilabel:`Tags`: add tags to indicate briefly what the event is for (e.g. `tradeshow`). Tags help better organize event cards in the kanban and are useful when using search filters during reporting periods."
msgstr ""
#: ../../content/applications/marketing/events/event_essentials.rst:55
#: ../../content/applications/marketing/events/event_essentials.rst:57
msgid ":guilabel:`Organizer`: detail the organizer(s) for the event. This field is usually the company that owns the Odoo database, or a vendor."
msgstr ""
#: ../../content/applications/marketing/events/event_essentials.rst:57
#: ../../content/applications/marketing/events/event_essentials.rst:59
msgid ":guilabel:`Responsible`: name the point person who is responsible for organizing the event."
msgstr ""
#: ../../content/applications/marketing/events/event_essentials.rst:58
#: ../../content/applications/marketing/events/event_essentials.rst:60
msgid ":guilabel:`Website`: indicate which Odoo website(s) the event event should be published to."
msgstr ""
#: ../../content/applications/marketing/events/event_essentials.rst:59
#: ../../content/applications/marketing/events/event_essentials.rst:61
msgid ":guilabel:`Venue`: list the venue details here if it's a new record, or choose from an existing location."
msgstr ""
#: ../../content/applications/marketing/events/event_essentials.rst:61
#: ../../content/applications/marketing/events/event_essentials.rst:63
msgid ":guilabel:`Limit Registrations`: when enabled, this setting caps the attendee registrations to a specified amount"
msgstr ""
#: ../../content/applications/marketing/events/event_essentials.rst:63
#: ../../content/applications/marketing/events/event_essentials.rst:65
msgid ":guilabel:`Autoconfirmation`: when enabled, this setting skips the confirmation request that gets sent by email to event registrants, and automatically confirms their registration."
msgstr ""
#: ../../content/applications/marketing/events/event_essentials.rst:66
#: ../../content/applications/marketing/events/event_essentials.rst:68
msgid "Once the fields in the event form are set, move on to the :guilabel:`Tickets` and :guilabel:`Communication` tabs, and optionally the :guilabel:`Questions` tab if registrations should require additional information."
msgstr ""
#: ../../content/applications/marketing/events/event_essentials.rst:71
#: ../../content/applications/marketing/events/event_essentials.rst:73
msgid "Add and sell event tickets"
msgstr ""
#: ../../content/applications/marketing/events/event_essentials.rst:73
#: ../../content/applications/marketing/events/event_essentials.rst:75
msgid "Under the :guilabel:`Tickets` tab, add line items for each type of ticket the event plans to offer. Here, determine the ticket price, start/end dates for registrations, as well as the maximum number of tickets that can be sold."
msgstr ""
#: ../../content/applications/marketing/events/event_essentials.rst:77
#: ../../content/applications/marketing/events/event_essentials.rst:79
msgid "If selling tickets isn't necessary for the event, a simple :guilabel:`Registration` button will be displayed on the event's page by default."
msgstr ""
@@ -1378,19 +1379,19 @@ msgstr ""
msgid "View of the ticket tab in Odoo Events."
msgstr ""
#: ../../content/applications/marketing/events/event_essentials.rst:85
#: ../../content/applications/marketing/events/event_essentials.rst:87
msgid "Send automated emails, text, and social posts to event attendees"
msgstr ""
#: ../../content/applications/marketing/events/event_essentials.rst:87
#: ../../content/applications/marketing/events/event_essentials.rst:89
msgid "Under the :guilabel:`Communication` tab, configure personalized email, SMS, or social post messages to keep in touch with event attendees. For each communication, click :guilabel:`Add a line` in the :guilabel:`Communication` tab form, and then choose (or create) a communications template using the drop-down menu under the :guilabel:`Template` column."
msgstr ""
#: ../../content/applications/marketing/events/event_essentials.rst:92
#: ../../content/applications/marketing/events/event_essentials.rst:94
msgid "Next, define the :guilabel:`Interval` and :guilabel:`Unit` of time for how often the communication should be sent; use these time fields to specify the frequency of :guilabel:`Hours`, :guilabel:`Days`, :guilabel:`Weeks`, or :guilabel:`Months` communications should be sent. There is also the option to send communications `Immediately` after a specified :guilabel:`Trigger` is activated."
msgstr ""
#: ../../content/applications/marketing/events/event_essentials.rst:98
#: ../../content/applications/marketing/events/event_essentials.rst:100
msgid "In the last column, determine the :guilabel:`Trigger` which controls how and when the communication is sent. For this action, choose between: :guilabel:`Before the event`, :guilabel:`After each registration`, or :guilabel:`After the event`."
msgstr ""
@@ -1398,27 +1399,27 @@ msgstr ""
msgid "View of the communication tab in Odoo Events."
msgstr ""
#: ../../content/applications/marketing/events/event_essentials.rst:107
#: ../../content/applications/marketing/events/event_essentials.rst:109
msgid "Attach a questionnaire to event registrations"
msgstr ""
#: ../../content/applications/marketing/events/event_essentials.rst:109
#: ../../content/applications/marketing/events/event_essentials.rst:111
msgid "Implementing a questionnaire during event sign up is an effective way to gauge the wants, needs, and interests of the event's attendees ahead of time. Questionnaires also act as informative analytics tools for reporting periods before (or after) events take place."
msgstr ""
#: ../../content/applications/marketing/events/event_essentials.rst:113
#: ../../content/applications/marketing/events/event_essentials.rst:115
msgid "To create a questionnaire, from the :guilabel:`Events` application, navigate to :menuselection:`Configuration --> Settings` and then enable the :guilabel:`Questions` setting."
msgstr ""
#: ../../content/applications/marketing/events/event_essentials.rst:116
#: ../../content/applications/marketing/events/event_essentials.rst:118
msgid "With the setting enabled, questions and answers can now be added (and recorded) under the the :guilabel:`Questions` tab back on the event form. For each question, specify if it should only be asked once with the :guilabel:`Ask once per order` checkbox, or if the question requires a :guilabel:`Mandatory Answer`, which will make the question required for registration."
msgstr ""
#: ../../content/applications/marketing/events/event_essentials.rst:122
#: ../../content/applications/marketing/events/event_essentials.rst:124
msgid "If the :guilabel:`Once per order` checkbox is enabled, then a single registration for 3 event attendees will show the questionnaire only once."
msgstr ""
#: ../../content/applications/marketing/events/event_essentials.rst:125
#: ../../content/applications/marketing/events/event_essentials.rst:127
msgid "There are two :guilabel:`Question Types` to choose from: :guilabel:`Selection` and :guilabel:`Text Input`. The :guilabel:`Selection` type, allows attendees to select an answer from pre-configured options, which are entered in the :guilabel:`Answers` tab below. The :guilabel:`Text Input` type allows attendees to write in their own answer to the question in a text box."
msgstr ""
@@ -1426,19 +1427,19 @@ msgstr ""
msgid "View of an event form, open the questions tab, and add a question."
msgstr ""
#: ../../content/applications/marketing/events/event_essentials.rst:135
#: ../../content/applications/marketing/events/event_essentials.rst:137
msgid "Log internal notes or add ticket instructions"
msgstr ""
#: ../../content/applications/marketing/events/event_essentials.rst:137
#: ../../content/applications/marketing/events/event_essentials.rst:139
msgid "In the :guilabel:`Notes` tab, there is the option to add a :guilabel:`Note` and/or :guilabel:`Ticket instructions`."
msgstr ""
#: ../../content/applications/marketing/events/event_essentials.rst:140
#: ../../content/applications/marketing/events/event_essentials.rst:142
msgid "Under :guilabel:`Note`, internal notes can be left (such as: to-do lists, contact information, etc.) for event staff to reference. In the :guilabel:`Ticket instructions` field, helpful information for staff and attendees can be shared (like, directions to the venue, opening/closing times, etc.)"
msgstr ""
#: ../../content/applications/marketing/events/event_essentials.rst:146
#: ../../content/applications/marketing/events/event_essentials.rst:148
msgid "Type `/` in either text field (:guilabel:`Note` or :guilabel:`Ticket instructions`) to reveal a sub-menu of :guilabel:`Structure` options. These options provide various formatting options to ensure vital internal information is organized for event staff to review."
msgstr ""
@@ -1446,35 +1447,35 @@ msgstr ""
msgid "View of the Notes tab in Odoo Events."
msgstr ""
#: ../../content/applications/marketing/events/event_essentials.rst:155
#: ../../content/applications/marketing/events/event_essentials.rst:157
msgid "Invite attendees to the event"
msgstr ""
#: ../../content/applications/marketing/events/event_essentials.rst:157
#: ../../content/applications/marketing/events/event_essentials.rst:159
msgid "To invite people to an event, click the :guilabel:`Invite` button located in the top left corner of the event form."
msgstr ""
#: ../../content/applications/marketing/events/event_essentials.rst:160
#: ../../content/applications/marketing/events/event_essentials.rst:162
msgid "Inside the invite template form, are options to sent email or SMS invites. Each message can be fully customized, and recipients can be added."
msgstr ""
#: ../../content/applications/marketing/events/event_essentials.rst:163
#: ../../content/applications/marketing/events/event_essentials.rst:165
msgid "Adding a :guilabel:`Subject` line for the invite message is required, but the :guilabel:`Preview Text` field is optional. The :guilabel:`Preview Text` is a catchy preview sentence meant to encourage recipients to open the email."
msgstr ""
#: ../../content/applications/marketing/events/event_essentials.rst:168
#: ../../content/applications/marketing/events/event_essentials.rst:170
msgid "In most cases, the :guilabel:`Preview Text` is displayed next to the subject. Keep this field empty to ensure the first characters of the email content appear, instead."
msgstr ""
#: ../../content/applications/marketing/events/event_essentials.rst:172
#: ../../content/applications/marketing/events/event_essentials.rst:174
msgid "Select invitees and configure recipient filters"
msgstr ""
#: ../../content/applications/marketing/events/event_essentials.rst:174
#: ../../content/applications/marketing/events/event_essentials.rst:176
msgid "In the middle of the invitation form, find and click the :guilabel:`Recipients` field, to reveal a drop-down menu of recipient options. These choices represent where Odoo will find the desired recipients' information."
msgstr ""
#: ../../content/applications/marketing/events/event_essentials.rst:178
#: ../../content/applications/marketing/events/event_essentials.rst:180
msgid "Once an option from this menu is selected (e.g. :guilabel:`Applicant`, :guilabel:`Contact`, :guilabel:`Event Registration`, :guilabel:`Lead/Opportunity`, etc.), Odoo will send the invitation to all recipients who match that initial rule. Additional rules can be added to narrow down the target recipients, by clicking :guilabel:`Add Filter`."
msgstr ""
@@ -1482,19 +1483,19 @@ msgstr ""
msgid "View of the add filter button beneath the recipients field in Odoo Events."
msgstr ""
#: ../../content/applications/marketing/events/event_essentials.rst:187
#: ../../content/applications/marketing/events/event_essentials.rst:189
msgid "Clicking :guilabel:`Add Filter` reveals three fields, formatted like an equation. To reveal the sub-menu options, click each field, and make the desired selections, until the preferred configuration has been acheived. The number of :guilabel:`Records` that match the rule(s) are indicated to the right of the :guilabel:`Recipients` field, in green."
msgstr ""
#: ../../content/applications/marketing/events/event_essentials.rst:196
#: ../../content/applications/marketing/events/event_essentials.rst:198
msgid "To the right of each rule, are :guilabel:`x`, :guilabel:`+`, and :guilabel:`...` icons. The :guilabel:`x` icon deletes a specific node (line) of the rule. The :guilabel:`+` icon adds a node (line) to the rule. And, the :guilabel:`...` icon adds a branch to the node. A branch means two additional, indented sub-nodes are added to the rule, providing even more specificity to the line above it."
msgstr ""
#: ../../content/applications/marketing/events/event_essentials.rst:203
#: ../../content/applications/marketing/events/event_essentials.rst:205
msgid "Build a custom event invite"
msgstr ""
#: ../../content/applications/marketing/events/event_essentials.rst:205
#: ../../content/applications/marketing/events/event_essentials.rst:207
msgid "In the :guilabel:`Mail Body` tab, there are a number of pre-configured message templates to choose from. Select the desired template, and modify every element of its design details with Odoo's drag-and-drop web builder, located on the right sidebar."
msgstr ""
@@ -1502,71 +1503,71 @@ msgstr ""
msgid "View of the drag and drop building blocks used to customize event invite emails."
msgstr ""
#: ../../content/applications/marketing/events/event_essentials.rst:214
#: ../../content/applications/marketing/events/event_essentials.rst:216
msgid "To build an email event invite from scratch, select the :guilabel:`Plain Text` template, and Odoo will provide a blank email canvas, which can be customized either by using the frontend rich text editor that accepts slash (`/`) commands, or the XML code editor when :ref:`developer mode <developer-mode>` is engaged and the :guilabel:`</>` icon is pressed."
msgstr ""
#: ../../content/applications/marketing/events/event_essentials.rst:220
#: ../../content/applications/marketing/events/event_essentials.rst:222
msgid "The :guilabel:`Mail Body` tab (and template options), are only available if the event invite :guilabel:`Mailing Type` is designated as an :guilabel:`Email`. If :guilabel:`SMS` is the :guilabel:`Mailing Type`, a :guilabel:`SMS Content` tab (consisting of a blank text space), is available, instead."
msgstr ""
#: ../../content/applications/marketing/events/event_essentials.rst:226
#: ../../content/applications/marketing/events/event_essentials.rst:228
msgid "Modify event invite settings"
msgstr ""
#: ../../content/applications/marketing/events/event_essentials.rst:228
#: ../../content/applications/marketing/events/event_essentials.rst:230
msgid "The options under the :guilabel:`Settings` tab are different, depending on the specified :guilabel:`Mailing Type`."
msgstr ""
#: ../../content/applications/marketing/events/event_essentials.rst:231
#: ../../content/applications/marketing/events/event_essentials.rst:233
msgid "If the :guilabel:`Email` option is selected as the :guilabel:`Mailing Type`, an employee can be designated as the :guilabel:`Responsible`, meaning that person is the one responsible for this particular invite message. :guilabel:`Send From` and :guilabel:`Reply To` email aliases can be designated here, as well."
msgstr ""
#: ../../content/applications/marketing/events/event_essentials.rst:236
#: ../../content/applications/marketing/events/event_essentials.rst:238
msgid "Also, if any specific documents are required (or helpful) for this event invite, they can be sent along with this email, by clicking :guilabel:`ATTACH A FILE`, and adding the appropriate document(s)."
msgstr ""
#: ../../content/applications/marketing/events/event_essentials.rst:240
#: ../../content/applications/marketing/events/event_essentials.rst:242
msgid "If the :guilabel:`SMS` option is selected as the :guilabel:`Mailing Type`, a :guilabel:`Responsible` can be designated, and the option to :guilabel:`Include an opt-out link` is available."
msgstr ""
#: ../../content/applications/marketing/events/event_essentials.rst:244
#: ../../content/applications/marketing/events/event_essentials.rst:246
msgid "Send event invitations to recipients"
msgstr ""
#: ../../content/applications/marketing/events/event_essentials.rst:246
#: ../../content/applications/marketing/events/event_essentials.rst:248
msgid "If the selected :guilabel:`Mailing Type` is :guilabel:`Email`, there are three options to send the invite: :guilabel:`Send`, :guilabel:`Schedule`, and :guilabel:`Test`."
msgstr ""
#: ../../content/applications/marketing/events/event_essentials.rst:249
#: ../../content/applications/marketing/events/event_essentials.rst:251
msgid "The :guilabel:`Send` option sends the invite right away. The :guilabel:`Schedule` option reveals a pop-up, in which a scheduled date/time can be selected for the email to be sent. The :guilabel:`Test` option reveals a :guilabel:`Test Mailing` pop-up, where specific recipient email addresses can be entered for Odoo to send them the current version of the mailing for review before officially sending it out to prospective event attendees."
msgstr ""
#: ../../content/applications/marketing/events/event_essentials.rst:255
#: ../../content/applications/marketing/events/event_essentials.rst:257
msgid "If the selected :guilabel:`Mailing Type` is :guilabel:`SMS`, there are four options to send the invite: :guilabel:`Put in Queue`, :guilabel:`Send Now`, :guilabel:`Schedule`, and :guilabel:`Test`."
msgstr ""
#: ../../content/applications/marketing/events/event_essentials.rst:258
#: ../../content/applications/marketing/events/event_essentials.rst:260
msgid "The :guilabel:`Put in Queue` option schedules an SMS message to all recipients (that match the designated rules, if any) in the near future. Clicking :guilabel:`Put in Queue` reveals a pop-up, requiring confirmation. When confirmed, a blue banner appears on the event invite template form, indicating that the SMS will be sent later that day."
msgstr ""
#: ../../content/applications/marketing/events/event_essentials.rst:264
#: ../../content/applications/marketing/events/event_essentials.rst:266
msgid "The :guilabel:`Send Now`, :guilabel:`Schedule`, and :guilabel:`Test` options all function the same way for both :guilabel:`Mailing Type` options."
msgstr ""
#: ../../content/applications/marketing/events/event_essentials.rst:268
#: ../../content/applications/marketing/events/event_essentials.rst:270
msgid "Publish events"
msgstr ""
#: ../../content/applications/marketing/events/event_essentials.rst:270
#: ../../content/applications/marketing/events/event_essentials.rst:272
msgid "Until an event is published, it will remain hidden from public view on the website and registering for it will not be possible. To publish an event, navigate to it either from the backend of Odoo through the :guilabel:`Events` application, or access the hidden event page through the frontend as either a priveliged user or administrator."
msgstr ""
#: ../../content/applications/marketing/events/event_essentials.rst:275
#: ../../content/applications/marketing/events/event_essentials.rst:277
msgid "If navigating from the backend, go to the event form, and click the :guilabel:`Go to Website` smart button to reach the event page on the website (on the frontend). If starting from the frontend, simply navigate to the event page that needs to be published."
msgstr ""
#: ../../content/applications/marketing/events/event_essentials.rst:279
#: ../../content/applications/marketing/events/event_essentials.rst:281
msgid "No matter the route, an event page can only be published from the frontend. In the upper right corner of the event page on the website, toggle the switch from the red :guilabel:`Unpublished` status to the green :guilabel:`Published` status. Doing so instantly makes the event page accessible to the public on the website."
msgstr ""
@@ -1574,6 +1575,343 @@ msgstr ""
msgid "View of a website page and the option to publish the event in Odoo Events."
msgstr ""
#: ../../content/applications/marketing/events/event_tracks.rst:3
msgid "Event tracks"
msgstr ""
#: ../../content/applications/marketing/events/event_tracks.rst:5
msgid "In Odoo, *Tracks* is a term used for talks, lectures, demonstrations, presentations, etc. that occur at an event."
msgstr ""
#: ../../content/applications/marketing/events/event_tracks.rst:8
msgid "With the **Events** application, create, schedule, and manage tracks for any event."
msgstr ""
#: ../../content/applications/marketing/events/event_tracks.rst:10
msgid "There is also the option to allow attendees to propose talks (tracks) for an event, which can then be approved or denied."
msgstr ""
#: ../../content/applications/marketing/events/event_tracks.rst:16
msgid "Navigate to :menuselection:`Events app --> Configuration --> Settings`, and tick the :guilabel:`Schedule & Tracks` checkbox."
msgstr ""
#: ../../content/applications/marketing/events/event_tracks.rst:19
msgid "When that checkbox is ticked, two additional setting options appear: :guilabel:`Live Broadcast` and :guilabel:`Event Gamification`."
msgstr ""
#: ../../content/applications/marketing/events/event_tracks.rst:-1
msgid "The Schedule and Tracks setting in the Odoo Events app, along with corresponding options."
msgstr ""
#: ../../content/applications/marketing/events/event_tracks.rst:26
msgid "The :guilabel:`Live Broadcast` option provides the ability to air tracks online, through a YouTube integration."
msgstr ""
#: ../../content/applications/marketing/events/event_tracks.rst:29
msgid "The :guilabel:`Event Gamification` option provides the ability to share a quiz with attendees once the track is over."
msgstr ""
#: ../../content/applications/marketing/events/event_tracks.rst:33
msgid "With the :guilabel:`Event Gamification` setting enabled, an :guilabel:`Add Quiz` button appears on track forms."
msgstr ""
#: ../../content/applications/marketing/events/event_tracks.rst:36
msgid "Once all desired settings have been enabled, click :guilabel:`Save`."
msgstr ""
#: ../../content/applications/marketing/events/event_tracks.rst:39
msgid "Event Tracks page"
msgstr ""
#: ../../content/applications/marketing/events/event_tracks.rst:41
msgid "To access, modify, and/or create tracks for an event, navigate to a preconfigured event, or :ref:`create a new one <events/create-event>`."
msgstr ""
#: ../../content/applications/marketing/events/event_tracks.rst:44
msgid "On the desired event form, click the :guilabel:`Tracks` smart button at the top of the form."
msgstr ""
#: ../../content/applications/marketing/events/event_tracks.rst:47
msgid "If the :guilabel:`Tracks` smart button is not readily available, click the :guilabel:`More` :icon:`fa-sort-desc` drop-down menu to reveal hidden smart buttons. Then, click :guilabel:`Tracks` from the resulting drop-down menu."
msgstr ""
#: ../../content/applications/marketing/events/event_tracks.rst:51
msgid "Clicking the :guilabel:`Tracks` smart button reveals the :guilabel:`Event Tracks` page, with all the tracks (both scheduled and proposed) for the event, if there are any."
msgstr ""
#: ../../content/applications/marketing/events/event_tracks.rst:-1
msgid "Typical event tracks page for an event in the Odoo Events application."
msgstr ""
#: ../../content/applications/marketing/events/event_tracks.rst:58
msgid "The tracks are presented in a default :icon:`oi-view-kanban` :guilabel:`(Kanban)` view, but there is the option to view these tracks in a :icon:`oi-view-list` :guilabel:`(List)`, :icon:`oi-view-cohort` :guilabel:`(Gantt)` chart, :icon:`fa-calendar-check-o` :guilabel:`(Calendar)`, :icon:`fa-area-chart` :guilabel:`(Graph)`, or :icon:`fa-clock-o` :guilabel:`(Activity)` view. All of which are accessible in the upper-right corner."
msgstr ""
#: ../../content/applications/marketing/events/event_tracks.rst:64
msgid "In the default :icon:`oi-view-kanban` :guilabel:`(Kanban)` view, the tracks are categorized into different stages. The default stages are: :guilabel:`Proposal`, :guilabel:`Confirmed`, :guilabel:`Announced`, :guilabel:`Published`, :guilabel:`Refused` (collapsed stage), and :guilabel:`Cancelled` (collapsed stage). All of which can be edited, if needed."
msgstr ""
#: ../../content/applications/marketing/events/event_tracks.rst:70
msgid "To edit a stage, hover over the stage name, click the :icon:`fa-cog` :guilabel:`(gear)` icon, and select :guilabel:`Edit Stage` from the resulting drop-down menu."
msgstr ""
#: ../../content/applications/marketing/events/event_tracks.rst:73
msgid "Clicking into a track from the :guilabel:`Event Tracks` page reveals the track form for that particular track."
msgstr ""
#: ../../content/applications/marketing/events/event_tracks.rst:77
msgid "Create event track"
msgstr ""
#: ../../content/applications/marketing/events/event_tracks.rst:79
msgid "From the :guilabel:`Event Tracks` page, click :guilabel:`New` in the upper-left corner to reveal a blank event track form to create an event track."
msgstr ""
#: ../../content/applications/marketing/events/event_tracks.rst:-1
msgid "Typical event track form in the Odoo Events application."
msgstr ""
#: ../../content/applications/marketing/events/event_tracks.rst:86
msgid "Start by giving the track a :guilabel:`Title`. This field is **required** by Odoo."
msgstr ""
#: ../../content/applications/marketing/events/event_tracks.rst:88
msgid "If desired, add an accompanying image to the track, via the :icon:`fa-pencil` :guilabel:`(pencil)` icon that appears when the cursor hovers over the :icon:`fa-camera` :guilabel:`(camera)` icon. When clicked, upload the desired image for the track. This image appears on the event website, on this specific track's page."
msgstr ""
#: ../../content/applications/marketing/events/event_tracks.rst:93
msgid "Enter a :guilabel:`Track Date` and time for the track, and designate a :guilabel:`Location` where the talk is planning to be held."
msgstr ""
#: ../../content/applications/marketing/events/event_tracks.rst:97
msgid "To access a complete list of locations for event tracks, which can be modified at any time, navigate to :menuselection:`Events app --> Configuration --> Track Locations`."
msgstr ""
#: ../../content/applications/marketing/events/event_tracks.rst:100
msgid "Add a :guilabel:`Duration` to the track (in hours)."
msgstr ""
#: ../../content/applications/marketing/events/event_tracks.rst:102
msgid "If the *Live Broadcast* setting is enabled, the option to add a corresponding link in the :guilabel:`YouTube Video Link` field is available."
msgstr ""
#: ../../content/applications/marketing/events/event_tracks.rst:105
msgid "If the :guilabel:`Always Wishlisted` checkbox is ticked, the talk is automatically set as a favorite for each registered event attendee."
msgstr ""
#: ../../content/applications/marketing/events/event_tracks.rst:108
msgid "Assign someone to be in charge of managing this track in the :guilabel:`Responsible` field. By default, the person who created the track is assigned."
msgstr ""
#: ../../content/applications/marketing/events/event_tracks.rst:111
msgid "Ensure the track is applied to the correct event in the :guilabel:`Event` field. By default, this field is auto-populated with the event related to the *Event Tracks* page the track was created from."
msgstr ""
#: ../../content/applications/marketing/events/event_tracks.rst:115
msgid "Choose to add existing :guilabel:`Tags`, or create new ones, to further organize the track. These tags, and their corresponding categories, are utilized on the event specific website."
msgstr ""
#: ../../content/applications/marketing/events/event_tracks.rst:118
msgid "Beneath that general information section, there are three tabs: :ref:`Speaker <events/track-speaker-tab>`, :ref:`Description <events/track-description-tab>`, and :ref:`Interactivity <events/track-interactivity-tab>`."
msgstr ""
#: ../../content/applications/marketing/events/event_tracks.rst:125
msgid "Speaker tab"
msgstr ""
#: ../../content/applications/marketing/events/event_tracks.rst:127
msgid "The :guilabel:`Speaker` tab on an event track form has fields related to the specific speaker/host of the track."
msgstr ""
#: ../../content/applications/marketing/events/event_tracks.rst:-1
msgid "The Speaker tab on an event track form in the Odoo Events application."
msgstr ""
#: ../../content/applications/marketing/events/event_tracks.rst:135
msgid "Contact details"
msgstr ""
#: ../../content/applications/marketing/events/event_tracks.rst:137
msgid "In the :guilabel:`Contact Details` section, use the :guilabel:`Contact` drop-down field to select an existing contact from the database as the main point of contact for the talk."
msgstr ""
#: ../../content/applications/marketing/events/event_tracks.rst:140
msgid "If this contact is not in the database, type in the name of the contact, and click :guilabel:`Create [contact name]`, to create and edit the contact form later, or click :guilabel:`Create and edit...` to be taken to that new contact's contact form, where the rest of their pertinent information can be entered."
msgstr ""
#: ../../content/applications/marketing/events/event_tracks.rst:145
msgid "The :guilabel:`Contact Email` and :guilabel:`Contact Phone` fields are populated with the information found on that chosen contact's contact form. These fields are not modifiable once the :guilabel:`Contact` is selected."
msgstr ""
#: ../../content/applications/marketing/events/event_tracks.rst:150
msgid "Speaker bio"
msgstr ""
#: ../../content/applications/marketing/events/event_tracks.rst:152
msgid "In the :guilabel:`Speaker Bio` section, enter information related to the speaker. Portions of this section may auto-populate, based on the :guilabel:`Contact` selected in the :guilabel:`Contact Details` section. If not, enter information in the necessary fields."
msgstr ""
#: ../../content/applications/marketing/events/event_tracks.rst:157
msgid "This information appears on the event website, on the specific track page."
msgstr ""
#: ../../content/applications/marketing/events/event_tracks.rst:159
msgid "Enter a :guilabel:`Name`, :guilabel:`Email`, and :guilabel:`Phone` number for the speaker."
msgstr ""
#: ../../content/applications/marketing/events/event_tracks.rst:161
msgid "If desired, add an image to appear alongside the speaker biography on the event website, via the :icon:`fa-pencil` :guilabel:`(pencil)` icon that appears when the cursor hovers over the :icon:`fa-camera` :guilabel:`(camera)` icon. When clicked, upload the desired image for the speaker."
msgstr ""
#: ../../content/applications/marketing/events/event_tracks.rst:165
msgid "Enter a :guilabel:`Job Position` for the designated speaker, and the :guilabel:`Company Name` associated with the speaker."
msgstr ""
#: ../../content/applications/marketing/events/event_tracks.rst:168
msgid "In the :guilabel:`Biography` field, enter a custom biography with any speaker-related information."
msgstr ""
#: ../../content/applications/marketing/events/event_tracks.rst:173
#: ../../content/applications/marketing/surveys/create.rst:193
msgid "Description tab"
msgstr ""
#: ../../content/applications/marketing/events/event_tracks.rst:175
msgid "The :guilabel:`Description` tab of an event track form is a blank text field, in which a description of the track can be entered. The information entered here appears on the specific track page on the event website."
msgstr ""
#: ../../content/applications/marketing/events/event_tracks.rst:182
msgid "Interactivity tab"
msgstr ""
#: ../../content/applications/marketing/events/event_tracks.rst:184
msgid "The :guilabel:`Interactivity` tab on an event track form only has a single option at first: :guilabel:`Magic Button`."
msgstr ""
#: ../../content/applications/marketing/events/event_tracks.rst:-1
msgid "The Interactivity tab on an event track form in the Odoo Events application."
msgstr ""
#: ../../content/applications/marketing/events/event_tracks.rst:191
msgid "When the :guilabel:`Magic Button` checkbox is ticked, Odoo displays a *call-to-action* button to attendees on the track sidebar, while the track is taking place."
msgstr ""
#: ../../content/applications/marketing/events/event_tracks.rst:194
msgid "With that checkbox ticked, three more options appear, all of which are related to the :guilabel:`Magic Button`:"
msgstr ""
#: ../../content/applications/marketing/events/event_tracks.rst:197
msgid ":guilabel:`Button Title`: Enter a title to appear on the button for attendees."
msgstr ""
#: ../../content/applications/marketing/events/event_tracks.rst:198
msgid ":guilabel:`Button Target URL`: Enter a URL that leads attendees to a specific page."
msgstr ""
#: ../../content/applications/marketing/events/event_tracks.rst:199
msgid ":guilabel:`Button appears`: Enter a number in the field, and the button appears that number of :guilabel:`minutes after track starts`."
msgstr ""
#: ../../content/applications/marketing/events/event_tracks.rst:203
msgid "The magic button **only** appears if there is more than one published track."
msgstr ""
#: ../../content/applications/marketing/events/event_tracks.rst:208
msgid "Add Quiz button"
msgstr ""
#: ../../content/applications/marketing/events/event_tracks.rst:210
msgid "The :guilabel:`Add Quiz` button **only** appears on event track forms if the *Event Gamification* setting is enabled."
msgstr ""
#: ../../content/applications/marketing/events/event_tracks.rst:213
msgid "To add a quiz to the event track, click the :guilabel:`Add Quiz` button to reveal a separate page, where an event track quiz can be configured."
msgstr ""
#: ../../content/applications/marketing/events/event_tracks.rst:-1
msgid "The Add Quiz page in the Odoo Events application for an event track."
msgstr ""
#: ../../content/applications/marketing/events/event_tracks.rst:220
msgid "Enter a title for the quiz in the blank field at the top of the page."
msgstr ""
#: ../../content/applications/marketing/events/event_tracks.rst:222
msgid "If participants can try the quiz multiple times, tick the :guilabel:`Allow multiple tries` checkbox."
msgstr ""
#: ../../content/applications/marketing/events/event_tracks.rst:224
msgid "The :guilabel:`Event` and :guilabel:`Event Track` fields are non-modifiable, and show the corresponding event and track the quiz is associated with."
msgstr ""
#: ../../content/applications/marketing/events/event_tracks.rst:227
msgid "To add questions to the quiz, click :guilabel:`Add a line` beneath the :guilabel:`Question` column to reveal a :guilabel:`Create Questions` pop-up window."
msgstr ""
#: ../../content/applications/marketing/events/event_tracks.rst:-1
msgid "The Create Questions pop-up window on an event-specific track quiz in the Odoo Events app."
msgstr ""
#: ../../content/applications/marketing/events/event_tracks.rst:235
msgid "**All** track quiz questions are multiple choice."
msgstr ""
#: ../../content/applications/marketing/events/event_tracks.rst:237
msgid "From the pop-up window, enter the question in the blank field at the top. Then, click :guilabel:`Add a line`, and a new line appears, in which an answer option can be entered."
msgstr ""
#: ../../content/applications/marketing/events/event_tracks.rst:240
msgid "Once an answer option has been entered, designate whether it is the :guilabel:`Correct` response, by ticking the checkbox in the :guilabel:`Correct` column. If it is incorrect, leave the checkbox unticked."
msgstr ""
#: ../../content/applications/marketing/events/event_tracks.rst:244
msgid "There is also the option to add a point value to each answer option in the :guilabel:`Points` column."
msgstr ""
#: ../../content/applications/marketing/events/event_tracks.rst:247
msgid "If there are any additional comments that should accompany an answer option, type them into the :guilabel:`Extra Comment` field."
msgstr ""
#: ../../content/applications/marketing/events/event_tracks.rst:251
msgid "The :guilabel:`Points` and :guilabel:`Extra Comment` fields are optional."
msgstr ""
#: ../../content/applications/marketing/events/event_tracks.rst:253
msgid "Repeat this process for all answer options."
msgstr ""
#: ../../content/applications/marketing/events/event_tracks.rst:255
msgid "To remove an answer option, click the :icon:`fa-trash-o` :guilabel:`(trash can)` icon on the far-right of the desired answer line."
msgstr ""
#: ../../content/applications/marketing/events/event_tracks.rst:258
msgid "Once all answer options are complete, click :guilabel:`Save & Close` to save the question, close the pop-up window, and return to the track quiz form. Or, click :guilabel:`Save & New` to save this question, and instantly start creating another question on a new :guilabel:`Create Questions` pop-up form."
msgstr ""
#: ../../content/applications/marketing/events/event_tracks.rst:264
msgid "Publish event track"
msgstr ""
#: ../../content/applications/marketing/events/event_tracks.rst:266
msgid "Once all desired configurations are complete on an event track form, click the desired stage it should be in from the status bar in the upper-right corner (e.g. :guilabel:`Confirmed`, :guilabel:`Announced`, etc.)."
msgstr ""
#: ../../content/applications/marketing/events/event_tracks.rst:271
msgid "The stage of a track can also be changed from the *Event Tracks* page, where the desired track card can be dragged-and-dropped into the appropriate Kanban stage."
msgstr ""
#: ../../content/applications/marketing/events/event_tracks.rst:274
msgid "If an event track has *not* been published yet, and it is moved to the :guilabel:`Published` stage, Odoo automatically publishes the track on the event website."
msgstr ""
#: ../../content/applications/marketing/events/event_tracks.rst:277
msgid "An event track can also be published by opening the desired event track form, and clicking the :guilabel:`Go to Website` smart button. Then, toggle the :icon:`fa-toggle-off` :guilabel:`Unpublished` switch at the top of the page to :icon:`fa-toggle-on` :guilabel:`Published`; thus turning it from red to green, and making it accessible for attendees."
msgstr ""
#: ../../content/applications/marketing/events/event_tracks.rst:283
msgid ":doc:`track_manage_talks`"
msgstr ""
#: ../../content/applications/marketing/events/sell_tickets.rst:3
msgid "Sell tickets"
msgstr ""
@@ -4650,10 +4988,6 @@ msgstr ""
msgid "Customize the :guilabel:`Session Code` here; this code is needed for participants to access the live session survey. Reward participants for quick answers by selecting the checkbox labeled :guilabel:`Reward quick answers`. By checking it, attendees will get more points if they answer quickly."
msgstr ""
#: ../../content/applications/marketing/surveys/create.rst:193
msgid "Description tab"
msgstr ""
#: ../../content/applications/marketing/surveys/create.rst:195
msgid "Back on the main survey template page is the :guilabel:`Description` tab, where a custom description of the survey can be added. This is displayed beneath the title on the survey's homepage, which is on the front end of the website made through the Odoo :guilabel:`Website` app."
msgstr ""

649
locale/sources/sales.pot
View File

File diff suppressed because it is too large Load Diff