[I18N] *: export 16.0 source terms

This commit is contained in:
Martin Trigaux 2022-12-23 10:35:59 +01:00
parent bf2d3d9ed2
commit 6a56842e1f
11 changed files with 7083 additions and 4384 deletions

View File

@ -8,7 +8,7 @@ msgid ""
msgstr ""
"Project-Id-Version: Odoo 16.0\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2022-11-17 09:28+0000\n"
"POT-Creation-Date: 2022-12-23 09:13+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"
@ -1008,7 +1008,7 @@ msgid "Instead of using the repository as described above, the 'deb' packages fo
msgstr ""
#: ../../content/administration/install/install.rst:186
msgid "Odoo 16.0 'deb' package currently supports `Debian 11 (Bullseye)`_, `Ubuntu 22.04 (Jammy)`_ or above."
msgid "Odoo 16 'deb' package currently supports `Debian 11 (Bullseye)`_, `Ubuntu 22.04 (Jammy)`_ or above."
msgstr ""
#: ../../content/administration/install/install.rst:189
@ -1040,7 +1040,7 @@ msgid "Instead of using the repository as described above, the 'rpm' packages fo
msgstr ""
#: ../../content/administration/install/install.rst:227
msgid "Odoo 16.0 'rpm' package supports Fedora 36."
msgid "Odoo 16 'rpm' package supports Fedora 36."
msgstr ""
#: ../../content/administration/install/install.rst:229
@ -3176,7 +3176,7 @@ msgstr ""
#: ../../content/administration/odoo_sh/advanced/submodules.rst:9
#: ../../content/administration/odoo_sh/getting_started/branches.rst:7
#: ../../content/administration/odoo_sh/getting_started/builds.rst:9
#: ../../content/administration/odoo_sh/getting_started/first_module.rst:7
#: ../../content/administration/odoo_sh/getting_started/first_module.rst:6
#: ../../content/administration/odoo_sh/getting_started/online-editor.rst:9
#: ../../content/administration/odoo_sh/getting_started/settings.rst:7
#: ../../content/administration/odoo_sh/getting_started/status.rst:7
@ -3194,7 +3194,7 @@ msgid "The base is an Ubuntu system, where all of Odoo's required dependencies,
msgstr ""
#: ../../content/administration/odoo_sh/advanced/containers.rst:14
msgid "If your project requires additional Python dependencies, or more recent releases, you can define a :file:`requirements.txt` file in the root of your branches listing them. The platform will take care to install these dependencies in your containers. `The pip requirements specifiers <https://pip.pypa.io/en/stable/reference/pip_install/#requirement-specifiers>`_ documentation can help you write a :file:`requirements.txt` file. To have a concrete example, check out the `requirements.txt file of Odoo <https://github.com/odoo/odoo/blob/14.0/requirements.txt>`_."
msgid "If your project requires additional Python dependencies, or more recent releases, you can define a :file:`requirements.txt` file in the root of your branches listing them. The platform will take care to install these dependencies in your containers. `The pip requirements specifiers <https://pip.pypa.io/en/stable/reference/pip_install/#requirement-specifiers>`_ documentation can help you write a :file:`requirements.txt` file. To have a concrete example, check out the `requirements.txt file of Odoo <https://github.com/odoo/odoo/blob/16.0/requirements.txt>`_."
msgstr ""
#: ../../content/administration/odoo_sh/advanced/containers.rst:22
@ -3488,8 +3488,8 @@ msgstr ""
#: ../../content/administration/odoo_sh/advanced/submodules.rst:82
#: ../../content/administration/odoo_sh/advanced/submodules.rst:94
#: ../../content/administration/odoo_sh/getting_started/first_module.rst:358
#: ../../content/administration/odoo_sh/getting_started/first_module.rst:487
#: ../../content/administration/odoo_sh/getting_started/first_module.rst:364
#: ../../content/administration/odoo_sh/getting_started/first_module.rst:502
msgid "Replace"
msgstr ""
@ -4524,15 +4524,15 @@ msgstr ""
msgid "If you plan to make it your production, unlink your former database from the subscription, and register the newly imported database. Read the :doc:`database registration documentation <../../maintain/on_premise>` for instructions."
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/first_module.rst:4
#: ../../content/administration/odoo_sh/getting_started/first_module.rst:3
msgid "Your first module"
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/first_module.rst:9
#: ../../content/administration/odoo_sh/getting_started/first_module.rst:8
msgid "This chapter helps you to create your first Odoo module and deploy it in your Odoo.sh project."
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/first_module.rst:11
#: ../../content/administration/odoo_sh/getting_started/first_module.rst:10
msgid "This tutorial requires :ref:`you created a project on Odoo.sh <odoosh-gettingstarted-create>`, and you know your Github repository's URL."
msgstr ""
@ -4703,7 +4703,7 @@ msgid "Stage the changes to be committed"
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/first_module.rst:164
#: ../../content/administration/odoo_sh/getting_started/first_module.rst:392
#: ../../content/administration/odoo_sh/getting_started/first_module.rst:399
msgid "Commit your changes"
msgstr ""
@ -4720,8 +4720,8 @@ msgid "The above command is explained in the section :ref:`Commit & Push your ch
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/first_module.rst:186
#: ../../content/administration/odoo_sh/getting_started/first_module.rst:380
#: ../../content/administration/odoo_sh/getting_started/first_module.rst:406
#: ../../content/administration/odoo_sh/getting_started/first_module.rst:387
#: ../../content/administration/odoo_sh/getting_started/first_module.rst:413
msgid "Or, from your computer terminal:"
msgstr ""
@ -4749,267 +4749,279 @@ msgstr ""
msgid "If your Odoo.sh project is configured to install your module automatically, you will directly see it amongst the database apps. Otherwise, it will be available in the apps to install."
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/first_module.rst:222
#: ../../content/administration/odoo_sh/getting_started/first_module.rst:223
msgid "You can then play around with your module, create new records and test your features and buttons."
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/first_module.rst:226
#: ../../content/administration/odoo_sh/getting_started/first_module.rst:227
msgid "Test with the production data"
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/first_module.rst:228
#: ../../content/administration/odoo_sh/getting_started/first_module.rst:229
msgid "You need to have a production database for this step. You can create it if you do not have it yet."
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/first_module.rst:230
#: ../../content/administration/odoo_sh/getting_started/first_module.rst:231
msgid "Once you tested your module in a development build with the demo data and believe it is ready, you can test it with the production data using a staging branch."
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/first_module.rst:233
#: ../../content/administration/odoo_sh/getting_started/first_module.rst:234
msgid "You can either:"
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/first_module.rst:235
#: ../../content/administration/odoo_sh/getting_started/first_module.rst:236
msgid "Make your development branch a staging branch, by drag and dropping it onto the *staging* section title."
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/first_module.rst:240
#: ../../content/administration/odoo_sh/getting_started/first_module.rst:242
msgid "Merge it in an existing staging branch, by drag and dropping it onto the given staging branch."
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/first_module.rst:245
#: ../../content/administration/odoo_sh/getting_started/first_module.rst:289
#: ../../content/administration/odoo_sh/getting_started/first_module.rst:247
#: ../../content/administration/odoo_sh/getting_started/first_module.rst:293
msgid "You can also use the :code:`git merge` command to merge your branches."
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/first_module.rst:247
#: ../../content/administration/odoo_sh/getting_started/first_module.rst:249
msgid "This will create a new staging build, which will duplicate the production database and make it run using a server updated with your latest changes of your branch."
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/first_module.rst:253
#: ../../content/administration/odoo_sh/getting_started/first_module.rst:297
#: ../../content/administration/odoo_sh/getting_started/first_module.rst:255
#: ../../content/administration/odoo_sh/getting_started/first_module.rst:301
msgid "Once the database ready, you can access it using the *Connect* button."
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/first_module.rst:258
#: ../../content/administration/odoo_sh/getting_started/first_module.rst:300
#: ../../content/administration/odoo_sh/getting_started/first_module.rst:260
#: ../../content/administration/odoo_sh/getting_started/first_module.rst:304
msgid "Install your module"
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/first_module.rst:260
#: ../../content/administration/odoo_sh/getting_started/first_module.rst:262
msgid "Your module will not be installed automatically, you have to install it from the apps menu. Indeed, the purpose of the staging build is to test the behavior of your changes as it would be on your production, and on your production you would not like your module to be installed automatically, but on demand."
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/first_module.rst:264
#: ../../content/administration/odoo_sh/getting_started/first_module.rst:267
msgid "Your module may not appear directly in your apps to install either, you need to update your apps list first:"
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/first_module.rst:266
#: ../../content/administration/odoo_sh/getting_started/first_module.rst:270
msgid "Activate the :ref:`developer mode <developer-mode>`"
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/first_module.rst:267
#: ../../content/administration/odoo_sh/getting_started/first_module.rst:271
msgid "in the apps menu, click the *Update Apps List* button,"
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/first_module.rst:268
#: ../../content/administration/odoo_sh/getting_started/first_module.rst:272
msgid "in the dialog that appears, click the *Update* button."
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/first_module.rst:273
#: ../../content/administration/odoo_sh/getting_started/first_module.rst:277
msgid "Your module will then appear in the list of available apps."
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/first_module.rst:279
#: ../../content/administration/odoo_sh/getting_started/first_module.rst:283
msgid "Deploy in production"
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/first_module.rst:281
#: ../../content/administration/odoo_sh/getting_started/first_module.rst:285
msgid "Once you tested your module in a staging branch with your production data, and believe it is ready for production, you can merge your branch in the production branch."
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/first_module.rst:284
#: ../../content/administration/odoo_sh/getting_started/first_module.rst:288
msgid "Drag and drop your staging branch on the production branch."
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/first_module.rst:291
#: ../../content/administration/odoo_sh/getting_started/first_module.rst:295
msgid "This will merge the latest changes of your staging branch in the production branch, and update your production server with these latest changes."
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/first_module.rst:302
#: ../../content/administration/odoo_sh/getting_started/first_module.rst:306
msgid "Your module will not be installed automatically, you have to install it manually as explained in the :ref:`above section about installing your module in staging databases <odoosh-gettingstarted-firstmodule-productiondata-install>`."
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/first_module.rst:308
#: ../../content/administration/odoo_sh/getting_started/first_module.rst:312
msgid "Add a change"
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/first_module.rst:310
#: ../../content/administration/odoo_sh/getting_started/first_module.rst:314
msgid "This section explains how to add a change in your module by adding a new field in a model and deploy it."
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/first_module.rst:314
#: ../../content/administration/odoo_sh/getting_started/first_module.rst:319
msgid "From the Odoo.sh editor,"
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/first_module.rst:313
#: ../../content/administration/odoo_sh/getting_started/first_module.rst:318
msgid "browse to your module folder *~/src/user/my_module*,"
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/first_module.rst:314
#: ../../content/administration/odoo_sh/getting_started/first_module.rst:319
msgid "then, open the file *models/models.py*."
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/first_module.rst:319
#: ../../content/administration/odoo_sh/getting_started/first_module.rst:325
msgid "Or, from your computer,"
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/first_module.rst:317
#: ../../content/administration/odoo_sh/getting_started/first_module.rst:322
msgid "use the file browser of your choice to browse to your module folder *~/src/odoo-addons/my_module*,"
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/first_module.rst:318
#: ../../content/administration/odoo_sh/getting_started/first_module.rst:324
msgid "then, open the file *models/models.py* using the editor of your choice, such as *Atom*, *Sublime Text*, *PyCharm*, *vim*, ..."
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/first_module.rst:321
#: ../../content/administration/odoo_sh/getting_started/first_module.rst:327
msgid "Then, after the description field"
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/first_module.rst:327
#: ../../content/administration/odoo_sh/getting_started/first_module.rst:333
msgid "Add a datetime field"
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/first_module.rst:333
#: ../../content/administration/odoo_sh/getting_started/first_module.rst:339
msgid "Then, open the file *views/views.xml*."
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/first_module.rst:335
#: ../../content/administration/odoo_sh/getting_started/first_module.rst:462
#: ../../content/administration/odoo_sh/getting_started/first_module.rst:341
#: ../../content/administration/odoo_sh/getting_started/first_module.rst:477
msgid "After"
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/first_module.rst:341
#: ../../content/administration/odoo_sh/getting_started/first_module.rst:439
#: ../../content/administration/odoo_sh/getting_started/first_module.rst:456
#: ../../content/administration/odoo_sh/getting_started/first_module.rst:468
#: ../../content/administration/odoo_sh/getting_started/first_module.rst:347
#: ../../content/administration/odoo_sh/getting_started/first_module.rst:454
#: ../../content/administration/odoo_sh/getting_started/first_module.rst:471
#: ../../content/administration/odoo_sh/getting_started/first_module.rst:483
msgid "Add"
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/first_module.rst:347
#: ../../content/administration/odoo_sh/getting_started/first_module.rst:353
msgid "These changes alter the database structure by adding a column in a table, and modify a view stored in database."
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/first_module.rst:350
#: ../../content/administration/odoo_sh/getting_started/first_module.rst:356
msgid "In order to be applied in existing databases, such as your production database, these changes requires the module to be updated."
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/first_module.rst:353
#: ../../content/administration/odoo_sh/getting_started/first_module.rst:359
msgid "If you would like the update to be performed automatically by the Odoo.sh platform when you push your changes, increase your module version in its manifest."
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/first_module.rst:356
#: ../../content/administration/odoo_sh/getting_started/first_module.rst:362
msgid "Open the module manifest *__manifest__.py*."
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/first_module.rst:364
#: ../../content/administration/odoo_sh/getting_started/first_module.rst:493
#: ../../content/administration/odoo_sh/getting_started/first_module.rst:370
#: ../../content/administration/odoo_sh/getting_started/first_module.rst:508
msgid "with"
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/first_module.rst:370
#: ../../content/administration/odoo_sh/getting_started/first_module.rst:376
msgid "The platform will detect the change of version and trigger the update of the module upon the new revision deployment."
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/first_module.rst:372
#: ../../content/administration/odoo_sh/getting_started/first_module.rst:379
msgid "Browse to your Git folder."
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/first_module.rst:374
#: ../../content/administration/odoo_sh/getting_started/first_module.rst:381
msgid "Then, from an Odoo.sh terminal:"
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/first_module.rst:386
#: ../../content/administration/odoo_sh/getting_started/first_module.rst:393
msgid "Then, stage your changes to be committed"
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/first_module.rst:398
#: ../../content/administration/odoo_sh/getting_started/first_module.rst:405
msgid "Push your changes:"
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/first_module.rst:400
#: ../../content/administration/odoo_sh/getting_started/first_module.rst:407
msgid "From an Odoo.sh terminal:"
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/first_module.rst:412
#: ../../content/administration/odoo_sh/getting_started/first_module.rst:419
msgid "The platform will then create a new build for the branch *feature-1*."
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/first_module.rst:417
#: ../../content/administration/odoo_sh/getting_started/first_module.rst:424
msgid "Once you tested your changes, you can merge your changes in the production branch, for instance by drag-and-dropping the branch on the production branch in the Odoo.sh interface. As you increased the module version in the manifest, the platform will update the module automatically and your new field will be directly available. Otherwise you can manually update the module within the apps list."
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/first_module.rst:423
#: ../../content/administration/odoo_sh/getting_started/first_module.rst:430
msgid "Use an external Python library"
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/first_module.rst:425
#: ../../content/administration/odoo_sh/getting_started/first_module.rst:432
msgid "If you would like to use an external Python library which is not installed by default, you can define a *requirements.txt* file listing the external libraries your modules depends on."
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/first_module.rst:428
#: ../../content/administration/odoo_sh/getting_started/first_module.rst:436
msgid "It is not possible to install or upgrade system packages on an Odoo.sh database (e.g., apt packages). However, under specific conditions, packages can be considered for installation. This also applies to **Python modules** requiring system packages for their compilation, and **third-party Odoo modules**."
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/first_module.rst:440
msgid "**PostgreSQL extensions** are not supported on Odoo.sh."
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/first_module.rst:441
msgid "For more information, consult our `FAQ <https://www.odoo.sh/faq#install_dependencies>`_."
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/first_module.rst:443
msgid "The platform will use this file to automatically install the Python libraries your project needs."
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/first_module.rst:430
#: ../../content/administration/odoo_sh/getting_started/first_module.rst:445
msgid "The feature is explained in this section by using the `Unidecode library <https://pypi.python.org/pypi/Unidecode>`_ in your module."
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/first_module.rst:433
#: ../../content/administration/odoo_sh/getting_started/first_module.rst:448
msgid "Create a file *requirements.txt* in the root folder of your repository"
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/first_module.rst:435
#: ../../content/administration/odoo_sh/getting_started/first_module.rst:450
msgid "From the Odoo.sh editor, create and open the file ~/src/user/requirements.txt."
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/first_module.rst:437
#: ../../content/administration/odoo_sh/getting_started/first_module.rst:452
msgid "Or, from your computer, create and open the file ~/src/odoo-addons/requirements.txt."
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/first_module.rst:445
#: ../../content/administration/odoo_sh/getting_started/first_module.rst:460
msgid "Then use the library in your module, for instance to remove accents from characters in the name field of your model."
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/first_module.rst:448
#: ../../content/administration/odoo_sh/getting_started/first_module.rst:463
msgid "Open the file *models/models.py*."
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/first_module.rst:450
#: ../../content/administration/odoo_sh/getting_started/first_module.rst:465
msgid "Before"
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/first_module.rst:483
#: ../../content/administration/odoo_sh/getting_started/first_module.rst:498
msgid "Adding a Python dependency requires a module version increase for the platform to install it."
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/first_module.rst:485
#: ../../content/administration/odoo_sh/getting_started/first_module.rst:500
msgid "Edit the module manifest *__manifest__.py*"
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/first_module.rst:499
#: ../../content/administration/odoo_sh/getting_started/first_module.rst:514
msgid "Stage and commit your changes:"
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/first_module.rst:507
#: ../../content/administration/odoo_sh/getting_started/first_module.rst:522
msgid "Then, push your changes:"
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/first_module.rst:509
#: ../../content/administration/odoo_sh/getting_started/first_module.rst:524
msgid "In an Odoo.sh terminal:"
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/first_module.rst:515
#: ../../content/administration/odoo_sh/getting_started/first_module.rst:530
msgid "In your computer terminal:"
msgstr ""
@ -6045,7 +6057,7 @@ msgid "Selecting My Databases under my profile"
msgstr ""
#: ../../content/administration/upgrade/odoo_online.rst:14
msgid "Click on the action settings icon next to your main database and select the *Upgrade* option."
msgid "Click on the up arrow button next to your main database name to proceed to the test upgrade."
msgstr ""
#: ../../content/administration/upgrade/odoo_online.rst:0
@ -6053,18 +6065,18 @@ msgid "Selecting the action settings icon"
msgstr ""
#: ../../content/administration/upgrade/odoo_online.rst:19
msgid "In the pop-up message that will appear, select Test Upgrade."
msgid "In the pop-up message that appears, select the target version and then :guilabel:`Test` as purpose."
msgstr ""
#: ../../content/administration/upgrade/odoo_online.rst:0
msgid "Selecting test upgrade"
#: ../../content/administration/upgrade/odoo_online.rst:23
msgid "The :guilabel:`Production` purpose doesn't appear if you didn't test your upgraded database at least once."
msgstr ""
#: ../../content/administration/upgrade/odoo_online.rst:24
#: ../../content/administration/upgrade/odoo_online.rst:26
msgid "This triggers the automated upgrade process. A confirmation email is then sent to you with the the link to the upgraded database or to provide information if the upgrade failed."
msgstr ""
#: ../../content/administration/upgrade/odoo_online.rst:28
#: ../../content/administration/upgrade/odoo_online.rst:30
msgid "You can also see and access your test database from your *My Databases* page."
msgstr ""

View File

@ -8,7 +8,7 @@ msgid ""
msgstr ""
"Project-Id-Version: Odoo 16.0\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2022-11-17 09:28+0000\n"
"POT-Creation-Date: 2022-12-23 09:13+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"
@ -16,20 +16,141 @@ msgstr ""
"Content-Type: text/plain; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"
#: ../../content/contributing.rst:7
#: ../../content/contributing.rst:6
msgid "Contributing"
msgstr ""
#: ../../content/contributing.rst:9
msgid "First, **thank you** for landing here and helping us improve Odoo!"
#: ../../content/contributing.rst:8
msgid "First off, **thank you** for landing here and considering contributing to Odoo!"
msgstr ""
#: ../../content/contributing.rst:11
msgid "This documentation section is intended as a guide to making contributions for first-timers and veterans."
#: ../../content/contributing.rst:10
msgid "This documentation serves as a guide for first-timer and veteran contributors. As an open-core project, Odoo accepts contributions from everyone, Odoo employees and members of the Odoo community alike. The Odoo community comprises users, developers, and other interested parties who contribute their time and expertise."
msgstr ""
#: ../../content/contributing.rst:14
msgid "As an open-core project, Odoo accepts contributions from everyone, Odoo employees and members of the Odoo community alike, in all of its open-source `GitHub repositories <https://github.com/orgs/odoo/repositories>`_."
#: ../../content/contributing.rst:15
msgid "Depending on your skill set and interest, there are many ways to contribute to Odoo. The table below lists the most important of them."
msgstr ""
#: ../../content/contributing.rst:23
msgid "Contribution"
msgstr ""
#: ../../content/contributing.rst:24
msgid "Description"
msgstr ""
#: ../../content/contributing.rst:25
msgid "Resources"
msgstr ""
#: ../../content/contributing.rst:26
msgid "Target Audience"
msgstr ""
#: ../../content/contributing.rst:27
msgid "Join the community"
msgstr ""
#: ../../content/contributing.rst:28
msgid "Participate in discussions on the forums, help answer questions, and assist other members of the Odoo community."
msgstr ""
#: ../../content/contributing.rst:30
msgid "`Odoo forums <https://www.odoo.com/forum>`_"
msgstr ""
#: ../../content/contributing.rst:31
msgid "Anyone interested in Odoo"
msgstr ""
#: ../../content/contributing.rst:32
msgid "Submit bug reports"
msgstr ""
#: ../../content/contributing.rst:33
msgid "Help improve the stability of Odoo by reporting the bugs that you discover in :doc:`supported versions </administration/maintain/supported_versions>` directly to Odoo support. Make sure to include as many details (version, environment, test scenario...) as possible. If you don't have the Odoo Enterprise license required for contacting the support, open a new issue on the GitHub repository of Odoo."
msgstr ""
#: ../../content/contributing.rst:38
msgid "`Odoo support <https://www.odoo.com/help>`_"
msgstr ""
#: ../../content/contributing.rst:39
msgid "`Issue tracker on GitHub <https://github.com/odoo/odoo/issues>`_"
msgstr ""
#: ../../content/contributing.rst:40
msgid "Users of Odoo"
msgstr ""
#: ../../content/contributing.rst:41
msgid "Translate Odoo"
msgstr ""
#: ../../content/contributing.rst:42
msgid "Translate the user interface and documentation of Odoo into different languages."
msgstr ""
#: ../../content/contributing.rst:43
msgid "`Odoo project on Transifex <https://explore.transifex.com/odoo/>`_"
msgstr ""
#: ../../content/contributing.rst:44
msgid "Anyone fluent in multiple languages"
msgstr ""
#: ../../content/contributing.rst:45
msgid "Contribute to the codebase"
msgstr ""
#: ../../content/contributing.rst:46
msgid "Submit pull requests to the Odoo GitHub repositories to fix bugs, add new features, or improve the performance and reliability of the product. You can also review and comment on pull requests from other contributors. By contributing to the codebase, you can make a direct and lasting impact on the quality and features of Odoo."
msgstr ""
#: ../../content/contributing.rst:50
msgid ":doc:`Guide: Contributing to the codebase <contributing/development>`"
msgstr ""
#: ../../content/contributing.rst:51
msgid ":doc:`Developer tutorials </developer/howtos>`"
msgstr ""
#: ../../content/contributing.rst:52
#: ../../content/contributing.rst:65
msgid "Developers with experience in Python and web development"
msgstr ""
#: ../../content/contributing.rst:53
msgid "Contribute to the documentation"
msgstr ""
#: ../../content/contributing.rst:54
msgid "Submit corrections and improvements to the Odoo documentation. The product evolves fast, and it can be challenging to consistently reflect these changes in the documentation. By updating the documentation, you can help many users find their way in Odoo."
msgstr ""
#: ../../content/contributing.rst:57
msgid ":doc:`Guide: Contributing to the documentation <contributing/documentation>`"
msgstr ""
#: ../../content/contributing.rst:58
msgid "Anyone interested in improving the Odoo documentation"
msgstr ""
#: ../../content/contributing.rst:59
msgid "Create custom modules"
msgstr ""
#: ../../content/contributing.rst:60
msgid "Develop new modules to extend the functionality of Odoo. Custom modules can be made available for free or paid on the Odoo App Store or on any other Odoo modules library. By creating custom modules and making them available to others, you can help grow the Odoo ecosystem and provide additional value to users of the platform."
msgstr ""
#: ../../content/contributing.rst:64
msgid "`Odoo Apps Store <https://apps.odoo.com/apps>`_"
msgstr ""
#: ../../content/contributing.rst:68
msgid "It is mainly Odoo employees who develop new features for the codebase and write new content for the documentation. Be sure to discuss any idea for a new feature or page with the Odoo team so they can give you the green light before you begin working on it. Some features may already be in development on their side, and only approved features can be merged."
msgstr ""
#: ../../content/contributing/development.rst:6
@ -273,7 +394,7 @@ msgid "New primary views do not require the inherit suffix as those are new reco
msgstr ""
#: ../../content/contributing/development/coding_guidelines.rst:393
#: ../../content/contributing/documentation.rst:204
#: ../../content/contributing/documentation.rst:223
#: ../../content/contributing/documentation/rst_cheat_sheet.rst:879
#: ../../content/contributing/documentation/rst_cheat_sheet.rst:881
#: ../../content/contributing/documentation/rst_cheat_sheet.rst:897
@ -1005,7 +1126,7 @@ msgid "Double-check your :abbr:`PR (Pull Request)` and, when ready, click again
msgstr ""
#: ../../content/contributing/documentation.rst:114
#: ../../content/contributing/documentation.rst:396
#: ../../content/contributing/documentation.rst:417
msgid "You're done! If your changes are approved straight away they will appear in the documentation the very next day. It may also be the case that the reviewer has a question or a remark, so make sure to check your notifications or your emails, depending on your account settings."
msgstr ""
@ -1038,10 +1159,10 @@ msgid "Verify that `the installation folder of Git is included in your system's
msgstr ""
#: ../../content/contributing/documentation.rst:144
#: ../../content/contributing/documentation.rst:169
#: ../../content/contributing/documentation.rst:317
#: ../../content/contributing/documentation.rst:172
#: ../../content/contributing/documentation.rst:337
#: ../../content/contributing/documentation.rst:368
#: ../../content/contributing/documentation.rst:357
#: ../../content/contributing/documentation.rst:388
msgid "Execute the following commands in a terminal:"
msgstr ""
@ -1054,190 +1175,203 @@ msgid "As stated earlier, our documentation (in all its versions) is maintained
msgstr ""
#: ../../content/contributing/documentation.rst:161
msgid "Prior to submitting a modification, you need to make a copy of the sources and download that copy on your machine."
msgid "Prior to submitting a modification, you need to make a copy of the sources and download that copy on your machine. Git's CLI (:dfn:`command-line interface`) allows downloading the sources by passing an URL to its :command:`git clone` command. You must choose the protocol of the URL depending on what you want to do with the sources: choose HTTPS if you intend to only build the documentation locally; choose SSH if you plan on proposing content changes."
msgstr ""
#: ../../content/contributing/documentation.rst:164
msgid "Go to `github.com/odoo/documentation <https://github.com/odoo/documentation>`_ and click on the **Fork** button in the top right corner."
#: ../../content/contributing/documentation.rst:167
msgid "Go to `github.com/odoo/documentation <https://github.com/odoo/documentation>`_ and click on the **Fork** button in the top right corner. If you work at Odoo, skip this step."
msgstr ""
#: ../../content/contributing/documentation.rst:177
msgid "If you do not have edit rights on the repository owned by Odoo, replace \"odoo\" with your Github username in the URL of the command above. If you do have edit rights, it is not necessary to fork the repository."
#: ../../content/contributing/documentation.rst:176
msgid "Clone with HTTPS"
msgstr ""
#: ../../content/contributing/documentation.rst:181
#: ../../content/contributing/documentation.rst:183
#: ../../content/contributing/documentation.rst:197
msgid "Replace `<username>` with your GitHub username. If you work at Odoo, replace it with `odoo`."
msgstr ""
#: ../../content/contributing/documentation.rst:186
msgid "Clone with SSH"
msgstr ""
#: ../../content/contributing/documentation.rst:189
msgid "Make sure that you `registered your SSH key on GitHub <https://docs.github.com/en/authentication/connecting-to-github-with-ssh>`_."
msgstr ""
#: ../../content/contributing/documentation.rst:200
msgid "In order to ease the collaboration between writers coming from many different systems and teams, execute the following group of commands that correspond to your :abbr:`OS (Operating System)` in a terminal."
msgstr ""
#: ../../content/contributing/documentation.rst:185
#: ../../content/contributing/documentation.rst:204
msgid "Windows:"
msgstr ""
#: ../../content/contributing/documentation.rst:193
#: ../../content/contributing/documentation.rst:212
msgid "Linux or Mac OS:"
msgstr ""
#: ../../content/contributing/documentation.rst:206
#: ../../content/contributing/documentation.rst:225
msgid "Because the documentation is written in :abbr:`RST (reStructuredText)`, it needs to be built (:dfn:`converted to HTML`) in order to display nicely. This is done by the documentation generator which takes the original :abbr:`RST (reStructuredText)` files as input, transforms the markups in a human-readable format, and outputs HTML files to be read in your web browser."
msgstr ""
#: ../../content/contributing/documentation.rst:211
#: ../../content/contributing/documentation.rst:230
msgid "The documentation generator that we use is called `Sphinx <http://www.sphinx-doc.org/en/master/>`_. and is written in `Python <https://en.wikipedia.org/wiki/Python_(programming_language)>`_. You have to install Python in order to use Sphinx. For the record, Sphinx is the program and Python the programming language, but you do not need to know much more about them so don't panic!"
msgstr ""
#: ../../content/contributing/documentation.rst:216
#: ../../content/contributing/documentation.rst:235
msgid "Python comes with its own package manager: `pip <https://en.wikipedia.org/wiki/Pip_(package_manager)>`_. It allows installing Python dependencies in a single command."
msgstr ""
#: ../../content/contributing/documentation.rst:220
#: ../../content/contributing/documentation.rst:239
msgid "Download and install the recommended release (`see README file <https://github.com/odoo/documentation/tree/16.0/README.md>`_) of **Python 3** on your machine."
msgstr ""
#: ../../content/contributing/documentation.rst:222
#: ../../content/contributing/documentation.rst:242
msgid "Make sure to have **pip** installed on your machine (on Windows, you can install pip alongside Python)."
msgstr ""
#: ../../content/contributing/documentation.rst:224
#: ../../content/contributing/documentation.rst:244
msgid "Execute the following commands in a terminal to verify that both installations finished successfully:"
msgstr ""
#: ../../content/contributing/documentation.rst:232
#: ../../content/contributing/documentation.rst:252
msgid "Execute the following commands in a terminal to install the Python dependencies of the documentation:"
msgstr ""
#: ../../content/contributing/documentation.rst:241
#: ../../content/contributing/documentation.rst:261
msgid "Depending on your :abbr:`OS (Operating System)`, you may need to run the commands ``python`` and ``pip`` instead of ``python3`` and ``pip3``"
msgstr ""
#: ../../content/contributing/documentation.rst:247
#: ../../content/contributing/documentation.rst:267
msgid "Make"
msgstr ""
#: ../../content/contributing/documentation.rst:249
#: ../../content/contributing/documentation.rst:269
msgid "`Make <https://en.wikipedia.org/wiki/Make_(software)>`_ is a tool that packs a bunch of command-lines into one to be easier to remember and to type. In our case, it is used to execute complex Sphinx build commands by using a single and simpler one instead."
msgstr ""
#: ../../content/contributing/documentation.rst:253
#: ../../content/contributing/documentation.rst:273
msgid "Download and install **Make** on your machine."
msgstr ""
#: ../../content/contributing/documentation.rst:254
#: ../../content/contributing/documentation.rst:274
msgid "Verify that `the installation folder of Make is included in your system's PATH variable <win-add-to-path_>`_."
msgstr ""
#: ../../content/contributing/documentation.rst:260
#: ../../content/contributing/documentation.rst:280
msgid "pngquant"
msgstr ""
#: ../../content/contributing/documentation.rst:262
#: ../../content/contributing/documentation.rst:282
msgid "`pngquant <https://pngquant.org/>`_ is a tool that we use to compress PNG images so that the documentation does not end up weighting several Gigabytes in a few year span."
msgstr ""
#: ../../content/contributing/documentation.rst:265
#: ../../content/contributing/documentation.rst:285
msgid "Download and install **pngquant** on your machine."
msgstr ""
#: ../../content/contributing/documentation.rst:266
#: ../../content/contributing/documentation.rst:286
msgid "Verify that `the installation folder of pngquant is included in your system's PATH variable <win-add-to-path_>`_."
msgstr ""
#: ../../content/contributing/documentation.rst:272
#: ../../content/contributing/documentation.rst:292
msgid "Prepare your version"
msgstr ""
#: ../../content/contributing/documentation.rst:274
msgid "Now that your machine is all set up, it is time to do the same for your version of the documentation files. As it would not be convenient to have several people working on the version 13.0 in parallel (conflicts of content would occur all the time), and in order to be able to create a :abbr:`PR (Pull Request)`, you must `create a new branch <https://www.atlassian.com/git/tutorials/using-branches>`_ starting from the branch 13.0. In other words, you copy the entirety of this versions files and give it another name. For this example, we will go with ``13.0-my_contribution``."
#: ../../content/contributing/documentation.rst:294
msgid "Now that your machine is all set up, it is time to do the same for your version of the documentation files. As it would not be convenient to have several people working on the version 16.0 in parallel (conflicts of content would occur all the time), and in order to be able to create a :abbr:`PR (Pull Request)`, you must `create a new branch <https://www.atlassian.com/git/tutorials/using-branches>`_ starting from the branch 16.0. In other words, you copy the entirety of this versions files and give it another name. For this example, we will go with ``16.0-my_contribution``."
msgstr ""
#: ../../content/contributing/documentation.rst:282
#: ../../content/contributing/documentation.rst:302
msgid "Execute the following commands in a terminal to..."
msgstr ""
#: ../../content/contributing/documentation.rst:284
#: ../../content/contributing/documentation.rst:304
msgid "Navigate to the documentation folder:"
msgstr ""
#: ../../content/contributing/documentation.rst:290
msgid "Switch to the version 13.0:"
msgstr ""
#: ../../content/contributing/documentation.rst:296
msgid "Create your own branch which will be a copy of 13.0:"
msgstr ""
#: ../../content/contributing/documentation.rst:305
msgid "Perform your changes"
msgstr ""
#: ../../content/contributing/documentation.rst:307
msgid "You can now perform any change you want to the documentation files. These changes must be compliant with :abbr:`RST (reStructuredText)` syntax (see :doc:`documentation/rst_cheat_sheet`) and with our :doc:`content <documentation/content_guidelines>` and :doc:`RST <documentation/rst_guidelines>` guidelines."
msgstr ""
#: ../../content/contributing/documentation.rst:313
msgid "If your changes include the addition of a new image, for instance :file:`my-image.png`, proceed as follows:"
#: ../../content/contributing/documentation.rst:310
msgid "Switch to the version 16.0:"
msgstr ""
#: ../../content/contributing/documentation.rst:316
msgid "Make sure that the image is in ``.png`` format."
msgstr ""
#: ../../content/contributing/documentation.rst:324
msgid "Delete :file:`my-image.png`."
msgid "Create your own branch which will be a copy of 16.0:"
msgstr ""
#: ../../content/contributing/documentation.rst:325
msgid "Rename :file:`my-image-fs8.png` to :file:`my-image.png`."
msgid "Perform your changes"
msgstr ""
#: ../../content/contributing/documentation.rst:326
msgid "If your changes include renaming or moving an RST file to a new location, follow the `manual for redirect rules <https://github.com/odoo/documentation/tree/13.0/redirects/MANUAL.md>`_ to create the appropriate redirect rule(s)."
#: ../../content/contributing/documentation.rst:327
msgid "You can now perform any change you want to the documentation files. These changes must be compliant with :abbr:`RST (reStructuredText)` syntax (see :doc:`documentation/rst_cheat_sheet`) and with our :doc:`content <documentation/content_guidelines>` and :doc:`RST <documentation/rst_guidelines>` guidelines."
msgstr ""
#: ../../content/contributing/documentation.rst:333
msgid "Preview your changes"
msgid "If your changes include the addition of a new image, for instance :file:`my-image.png`, proceed as follows:"
msgstr ""
#: ../../content/contributing/documentation.rst:335
msgid "To preview your changes in a generated documentation, proceed as follows:"
#: ../../content/contributing/documentation.rst:336
msgid "Make sure that the image is in ``.png`` format."
msgstr ""
#: ../../content/contributing/documentation.rst:344
msgid "Delete :file:`my-image.png`."
msgstr ""
#: ../../content/contributing/documentation.rst:345
msgid "Rename :file:`my-image-fs8.png` to :file:`my-image.png`."
msgstr ""
#: ../../content/contributing/documentation.rst:346
msgid "You can omit the :command:`make clean` command when no recent change has been made to the hierarchy of documentation files."
msgstr ""
#: ../../content/contributing/documentation.rst:349
msgid "Fix any error or warning shown in the logs of the build."
msgstr ""
#: ../../content/contributing/documentation.rst:350
msgid "Open the file :file:`documentation/_build/html/index.html` with your default web browser."
msgid "If your changes include renaming or moving an RST file to a new location, follow the `manual for redirect rules <https://github.com/odoo/documentation/tree/16.0/redirects/MANUAL.md>`_ to create the appropriate redirect rule(s)."
msgstr ""
#: ../../content/contributing/documentation.rst:353
msgid "Preview your changes"
msgstr ""
#: ../../content/contributing/documentation.rst:355
msgid "To preview your changes in a generated documentation, proceed as follows:"
msgstr ""
#: ../../content/contributing/documentation.rst:366
msgid "You can omit the :command:`make clean` command when no recent change has been made to the hierarchy of documentation files."
msgstr ""
#: ../../content/contributing/documentation.rst:369
msgid "Fix any error or warning shown in the logs of the build."
msgstr ""
#: ../../content/contributing/documentation.rst:370
msgid "Open the file :file:`documentation/_build/html/index.html` with your default web browser."
msgstr ""
#: ../../content/contributing/documentation.rst:373
msgid "These steps have for only purpose to show you the final results of your changes. They have no impact on the documentation source files."
msgstr ""
#: ../../content/contributing/documentation.rst:359
#: ../../content/contributing/documentation.rst:379
msgid "Submit your changes"
msgstr ""
#: ../../content/contributing/documentation.rst:362
#: ../../content/contributing/documentation.rst:382
msgid "We expect you to have basic knowledge of Git, which should be enough to cover the basic flow of a one-time contribution. If you plan on submitting several contributions, work on older versions of the documentation or perform any other advanced action, we recommend you to be confident with Git. Help yourself with `this manual of Git <https://www.atlassian.com/git>`_ and `this interactive tutorial <https://learngitbranching.js.org/>`_."
msgstr ""
#: ../../content/contributing/documentation.rst:376
#: ../../content/contributing/documentation.rst:396
msgid "Go to `github.com/odoo/documentation/pulls <https://github.com/odoo/documentation/pulls>`_ and click on the **New pull request** button."
msgstr ""
#: ../../content/contributing/documentation.rst:381
#: ../../content/contributing/documentation.rst:401
msgid "If you forked the base repository in the section :ref:`contributing/fetch-sources`, click on the link **compare across forks** If not, skip this step."
msgstr ""
#: ../../content/contributing/documentation.rst:386
msgid "In the dropdown for the selection of the base branch (i.e., the version of the documentation that your changes concern), make sure to select the version that your changes target (here **13.0**)."
#: ../../content/contributing/documentation.rst:406
msgid "In the dropdown for the selection of the base branch (i.e., the version of the documentation that your changes concern), make sure to select the version that your changes target (here **16.0**)."
msgstr ""
#: ../../content/contributing/documentation.rst:391
#: ../../content/contributing/documentation.rst:412
msgid "Double-check your :abbr:`PR (Pull Request)` and, when ready, click again on the **Create pull request** button to submit your changes for review by a redactor at Odoo."
msgstr ""
@ -2477,11 +2611,11 @@ msgid "Absolute:"
msgstr ""
#: ../../content/contributing/documentation/rst_guidelines.rst:39
msgid "``https://odoo.com/documentation/master/applications/sales/sales/products_prices/prices.html``"
msgid "``https://odoo.com/documentation/16.0/applications/sales/sales/products_prices/prices.html``"
msgstr ""
#: ../../content/contributing/documentation/rst_guidelines.rst:40
msgid "``https://odoo.com/documentation/master/applications/sales/sales/products_prices/products/variants.html``"
msgid "``https://odoo.com/documentation/16.0/applications/sales/sales/products_prices/products/variants.html``"
msgstr ""
#: ../../content/contributing/documentation/rst_guidelines.rst:42

File diff suppressed because it is too large Load Diff

File diff suppressed because it is too large Load Diff

View File

@ -8,7 +8,7 @@ msgid ""
msgstr ""
"Project-Id-Version: Odoo 16.0\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2022-11-17 09:28+0000\n"
"POT-Creation-Date: 2022-12-23 09:13+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"
@ -707,103 +707,103 @@ msgid "Developer Mode (debug mode)"
msgstr ""
#: ../../content/applications/general/developer_mode.rst:7
msgid "The developer mode (or debug mode) gives you access to extra and advanced tools."
msgid "The developer mode (or debug mode) unlocks access to extra and advanced tools in Odoo. There are several ways to activate the developer mode: through the :ref:`settings <general/developer_mode/settings>`, the :ref:`browser extension <general/developer_mode/browser-extension>`, through the :ref:`command palette <general/developer_mode/command-palette>` or the :ref:`URL <general/developer_mode/url>`."
msgstr ""
#: ../../content/applications/general/developer_mode.rst:10
#: ../../content/applications/general/developer_mode.rst:17
msgid "Activate through the Settings"
msgstr ""
#: ../../content/applications/general/developer_mode.rst:12
msgid "Go to :menuselection:`Settings --> Activate the developer mode`."
#: ../../content/applications/general/developer_mode.rst:19
msgid "The debug mode can be activated in the Odoo database settings. Go to :menuselection:`Settings --> General Settings --> Developer Tools` and click on :guilabel:`Activate the developer mode`. At least one application needs to be installed for the :guilabel:`Developer Tools` section to appear in the :guilabel:`Settings` module."
msgstr ""
#: ../../content/applications/general/developer_mode.rst:None
msgid "Overview of the debug options under settings in Odoo"
msgid "Overview of the debug options under settings in Odoo."
msgstr ""
#: ../../content/applications/general/developer_mode.rst:19
msgid "*Activate the developer mode (with assets)* is used by developers; *Activate the developer mode (with tests assets)* is used by developers and testers."
#: ../../content/applications/general/developer_mode.rst:29
msgid ":guilabel:`Activate the developer mode (with assets)` is used by developers; :guilabel:`Activate the developer mode (with tests assets)` is used by developers and testers."
msgstr ""
#: ../../content/applications/general/developer_mode.rst:22
msgid "Once activated, the *Deactivate the developer mode* option becomes available."
#: ../../content/applications/general/developer_mode.rst:32
msgid "Once activated, the :guilabel:`Deactivate the developer mode` option becomes available."
msgstr ""
#: ../../content/applications/general/developer_mode.rst:25
msgid "Activate through a browser extension"
#: ../../content/applications/general/developer_mode.rst:37
msgid "Activate through the browser extension"
msgstr ""
#: ../../content/applications/general/developer_mode.rst:28
msgid "Go to the settings and extensions of your web browser, and search for *Odoo Debug*. Once the extension is installed, a new icon will be shown on your toolbar."
#: ../../content/applications/general/developer_mode.rst:39
msgid "Within a web browser, navigate to the browser settings and extensions and search for the `Odoo Debug` extension. Once the extension is installed, a new icon will be shown on the browser's toolbar."
msgstr ""
#: ../../content/applications/general/developer_mode.rst:30
#: ../../content/applications/general/developer_mode.rst:43
msgid "For the *Odoo Debug* extension, a single click enables a normal version of the mode, while a double click enables it with assets. To deactivate it, use a single click."
msgstr ""
#: ../../content/applications/general/developer_mode.rst:None
msgid "View of odoos debug icon in a chromes toolbar"
msgid "View of Odoo's debug icon in a Google Chrome toolbar."
msgstr ""
#: ../../content/applications/general/developer_mode.rst:37
#: ../../content/applications/general/developer_mode.rst:53
msgid "Activate through the command palette"
msgstr ""
#: ../../content/applications/general/developer_mode.rst:39
msgid "The command palette tool has a command to activate the debug mode: open it with the keyboard shortcut `ctrl+k`, then type `debug`: a command will show up to activate the debug mode."
#: ../../content/applications/general/developer_mode.rst:55
msgid "In Odoo, the command palette tool has a command to activate the debug mode. First, open the command palette tool with the keyboard shortcut `ctrl+k` and then type `debug`. A command will show up to activate the debug mode."
msgstr ""
#: ../../content/applications/general/developer_mode.rst:None
msgid "Command palette with debug command"
msgid "Command palette with debug command."
msgstr ""
#: ../../content/applications/general/developer_mode.rst:48
#: ../../content/applications/general/developer_mode.rst:68
msgid "Activate through the URL"
msgstr ""
#: ../../content/applications/general/developer_mode.rst:50
msgid "In the URL, add ``?debug=1`` or ``?debug=true`` after *web*. To deactivate the debug mode, add `?debug=0` instead."
#: ../../content/applications/general/developer_mode.rst:70
msgid "The debug mode can also be activated by adding an extra query string to the database's URL. In the URL, add `?debug=1` or `?debug=true` after `/web`. To deactivate the debug mode, change the value to `?debug=0` instead."
msgstr ""
#: ../../content/applications/general/developer_mode.rst:None
msgid "Overview of an url with the debug mode command added in Odoo"
msgid "Overview of a URL with the debug mode command added."
msgstr ""
#: ../../content/applications/general/developer_mode.rst:58
#: ../../content/applications/general/developer_mode.rst:79
msgid "Additional modes are available for developers: `?debug=assets` enables the :ref:`assets mode <frontend/framework/assets_debug_mode>`, and `?debug=tests` enables the :ref:`tests mode <frontend/framework/tests_debug_mode>`."
msgstr ""
#: ../../content/applications/general/developer_mode.rst:65
msgid "Locate the mode tools"
#: ../../content/applications/general/developer_mode.rst:86
msgid "Locate the developer mode tools"
msgstr ""
#: ../../content/applications/general/developer_mode.rst:67
msgid "The Developer mode tools can be accessed from the *Open Developer Tools* button, located on the header of your pages. This menu contains additional tools that are useful to understand or edit technical data, such as the views or the actions. It contains some useful menu items such as:"
msgstr ""
#: ../../content/applications/general/developer_mode.rst:72
msgid "edit action"
msgstr ""
#: ../../content/applications/general/developer_mode.rst:73
msgid "manage filters"
msgstr ""
#: ../../content/applications/general/developer_mode.rst:74
msgid "edit the current view"
msgstr ""
#: ../../content/applications/general/developer_mode.rst:75
msgid "see the `fields view get`"
msgstr ""
#: ../../content/applications/general/developer_mode.rst:76
msgid "and much more."
#: ../../content/applications/general/developer_mode.rst:88
msgid "Once developer mode is activated, the developer mode tools can be accessed from the :guilabel:`Open Developer Tools` button, the bug icon located in the header of the Odoo database."
msgstr ""
#: ../../content/applications/general/developer_mode.rst:None
msgid "Overview of a console page and the debug icon being shown in Odoo"
msgid "Overview of a console page and the debug icon being shown in Odoo."
msgstr ""
#: ../../content/applications/general/developer_mode.rst:95
msgid "This menu contains additional tools that are useful to understand or edit technical data, such as the views or actions of a page. On a page that has filters, actions, and view options, the developer mode tools contain some useful menu items such as:"
msgstr ""
#: ../../content/applications/general/developer_mode.rst:99
msgid ":guilabel:`Edit Action`"
msgstr ""
#: ../../content/applications/general/developer_mode.rst:100
msgid ":guilabel:`Manage Filters`"
msgstr ""
#: ../../content/applications/general/developer_mode.rst:101
msgid "Edit the current view (e.g. Kanban, List, Graph, etc.)"
msgstr ""
#: ../../content/applications/general/developer_mode.rst:102
msgid "See the :guilabel:`Fields View Get`"
msgstr ""
#: ../../content/applications/general/digest_emails.rst:3
@ -1067,211 +1067,239 @@ msgid "Email Communication"
msgstr ""
#: ../../content/applications/general/email_communication/email_domain.rst:3
msgid "Sending emails with Odoo"
msgid "Send an email with Odoo"
msgstr ""
#: ../../content/applications/general/email_communication/email_domain.rst:6
msgid "Using your email domain in Odoo"
msgid "Use an email domain in Odoo"
msgstr ""
#: ../../content/applications/general/email_communication/email_domain.rst:8
msgid "Documents in Odoo (a CRM opportunity, a sales order, an invoice ...) have a discussion thread, called *chatter*."
msgid "Documents in Odoo (such as a CRM opportunity, a sales order, an invoice, etc.) have a discussion thread, called *chatter*."
msgstr ""
#: ../../content/applications/general/email_communication/email_domain.rst:11
msgid "When you post a message in the chatter, this message is sent by email to the followers of the document. If a follower replies to the message, the reply updates the chatter, and Odoo relays the reply to the followers."
msgid "When a database user posts a message in the chatter, this message is sent by email to the followers of the document. If a follower replies to the message, the reply updates the chatter, and Odoo relays the reply to the followers as a notification."
msgstr ""
#: ../../content/applications/general/email_communication/email_domain.rst:15
msgid "Emails from your users to partners (customers, vendors) are sent from the email address of your users. Similarly, emails from partners to users are sent from the email address of the partners. This allows you to recognize at a glance who sent an email relayed by Odoo."
msgid "Messages sent in the chatter from internal database users to external users (such as partners, customers, or vendors) are relayed on behalf of the database users. Messages sent back to the chatter from external users will appear in the chatter from their respective email addresses, or as they are listed in their Contacts record."
msgstr ""
#: ../../content/applications/general/email_communication/email_domain.rst:19
msgid "If your database is hosted on our cloud (Odoo Online or Odoo.sh), it is not necessary to add an outgoing email server to send emails from your custom domain. You can enjoy this feature by using the default Odoo email server."
#: ../../content/applications/general/email_communication/email_domain.rst:20
msgid "If the Odoo database is hosted on the cloud (Odoo Online or Odoo.sh), it is not necessary to add an outgoing email server to send emails from a custom domain."
msgstr ""
#: ../../content/applications/general/email_communication/email_domain.rst:24
msgid "The Odoo server is subject to a daily email limit to prevent abuse. The default limit is 200 emails sent per day for databases with an Enterprise subscription. This limit can be increased under certain conditions. See our :doc:`FAQ <faq>` or contact support for more information."
msgid "The Odoo server is subject to a daily email limit to prevent abuse. The default limit is 200 emails sent per day for databases with an **Enterprise** subscription. This limit can be increased under certain conditions. See the :doc:`FAQ <faq>` or contact support for more information."
msgstr ""
#: ../../content/applications/general/email_communication/email_domain.rst:29
msgid "However, it is recommended that you configure your domain name to ensure that emails from your users reach your partners, rather than being considered spam."
msgid "To ensure that emails sent to and from the chatter reach their intended contacts, instead of being considered spam, Odoo recommends configuring the domain name."
msgstr ""
#: ../../content/applications/general/email_communication/email_domain.rst:32
msgid "For the same reason, we recommend that you always give your users an email address from a domain you manage, rather than a generic email address (gmail.com, outlook.com, etc.)."
msgid "For the same reason, Odoo also recommends giving each database user an email address from the configured domain, rather than a generic email address domain (such as gmail.com, outlook.com, etc.)."
msgstr ""
#: ../../content/applications/general/email_communication/email_domain.rst:38
#: ../../content/applications/general/email_communication/email_domain.rst:39
msgid "Be SPF compliant"
msgstr ""
#: ../../content/applications/general/email_communication/email_domain.rst:40
msgid "The Sender Policy Framework (SPF) protocol allows the owner of a domain name to specify which servers are allowed to send email from that domain. When a server receives an incoming email, it checks whether the IP address of the sending server is on the list of allowed IPs according to the SPF record of the sender."
#: ../../content/applications/general/email_communication/email_domain.rst:41
msgid "The Sender Policy Framework (SPF) protocol allows the owner of a domain name to specify which servers are allowed to send emails from that domain. When a server receives an incoming email, it checks if the IP address of the sending server is on the list of allowed IPs according to the sender's :abbr:`SPF (Sender Policy Framework)` record."
msgstr ""
#: ../../content/applications/general/email_communication/email_domain.rst:46
msgid "The SPF verification is performed on the domain mentioned in the Return-Path field of the email. In the case of an email sent by Odoo, this domain corresponds to the value of the `mail.catchall.domain` key in the database system parameters."
#: ../../content/applications/general/email_communication/email_domain.rst:47
msgid "The :abbr:`SPF (Sender Policy Framework)` verification is performed on the domain mentioned in the `Return-Path` field of the email. In the case of an email sent by Odoo, this domain corresponds to the value of the `mail.catchall.domain` key in the database system parameters."
msgstr ""
#: ../../content/applications/general/email_communication/email_domain.rst:50
#: ../../content/applications/general/email_communication/email_domain.rst:51
msgid "See the :ref:`documentation on incoming emails <email_communication/inbound_messages>`."
msgstr ""
#: ../../content/applications/general/email_communication/email_domain.rst:52
msgid "The SPF policy of a domain is set using a TXT record. How to create or modify a TXT record depends on the provider hosting the DNS zone of your domain name. In order for the verification to work properly, each domain can only have one SPF record."
#: ../../content/applications/general/email_communication/email_domain.rst:53
msgid "The :abbr:`SPF (Sender Policy Framework)` policy of a domain is set using a TXT record. The way to create or modify a TXT record depends on the provider hosting the :abbr:`DNS (Domain Name System)` zone of the domain name. In order for the verification to work properly, each domain can only have one :abbr:`SPF (Sender Policy Framework)` record."
msgstr ""
#: ../../content/applications/general/email_communication/email_domain.rst:56
msgid "If your domain name does not yet have an SPF record, the content of the record to create is as follows:"
msgstr ""
#: ../../content/applications/general/email_communication/email_domain.rst:59
msgid "``v=spf1 include:_spf.odoo.com ~all``"
#: ../../content/applications/general/email_communication/email_domain.rst:58
msgid "If the domain name does not yet have an :abbr:`SPF (Sender Policy Framework)` record, the content of the record to create it is as follows:"
msgstr ""
#: ../../content/applications/general/email_communication/email_domain.rst:61
msgid "If your domain name already has an SPF record, you need to update this record (and do not create a new one)."
msgid "`v=spf1 include:_spf.odoo.com ~all`"
msgstr ""
#: ../../content/applications/general/email_communication/email_domain.rst:66
msgid "If your TXT record is `v=spf1 include:_spf.google.com ~all`, you need to edit it to add `include:_spf.odoo.com`: `v=spf1 include:_spf.odoo.com include:_spf.google.com ~all`"
#: ../../content/applications/general/email_communication/email_domain.rst:63
msgid "If the domain name already has an :abbr:`SPF (Sender Policy Framework)` record, the record must be updated (and do not create a new one)."
msgstr ""
#: ../../content/applications/general/email_communication/email_domain.rst:69
msgid "You can check if your SPF record is valid with a free tool like `MXToolbox SPF <https://mxtoolbox.com/spf.aspx>`_."
#: ../../content/applications/general/email_communication/email_domain.rst:68
msgid "If the TXT record is `v=spf1 include:_spf.google.com ~all`, edit it to add `include:_spf.odoo.com`: `v=spf1 include:_spf.odoo.com include:_spf.google.com ~all`"
msgstr ""
#: ../../content/applications/general/email_communication/email_domain.rst:75
msgid "Enable DKIM"
#: ../../content/applications/general/email_communication/email_domain.rst:71
msgid "Check if the :abbr:`SPF (Sender Policy Framework)` record is valid with a free tool like `MXToolbox SPF <https://mxtoolbox.com/spf.aspx>`_."
msgstr ""
#: ../../content/applications/general/email_communication/email_domain.rst:77
msgid "The DomainKeys Identified Mail (DKIM) allows you to authenticate your emails with a digital signature."
msgid "Enable DKIM"
msgstr ""
#: ../../content/applications/general/email_communication/email_domain.rst:79
msgid "When sending an email, the Odoo server includes a unique DKIM signature in the headers. The recipient's server decrypts this signature using the DKIM record in your domain name. If the signature and the key contained in the record match, this guarantees that your message is authentic and has not been altered during transport."
msgid "The DomainKeys Identified Mail (DKIM) allows a user to authenticate emails with a digital signature."
msgstr ""
#: ../../content/applications/general/email_communication/email_domain.rst:84
msgid "To enable DKIM, you must add a CNAME record to the DNS zone of your domain name:"
#: ../../content/applications/general/email_communication/email_domain.rst:82
msgid "When sending an email, the Odoo server includes a unique :abbr:`DKIM (DomainKeys Identified Mail)` signature in the headers. The recipient's server decrypts this signature using the :abbr:`DKIM (DomainKeys Identified Mail)` record in the database's domain name. If the signature and the key contained in the record match, this guarantees that the message is authentic and has not been altered during transport."
msgstr ""
#: ../../content/applications/general/email_communication/email_domain.rst:86
msgid "``odoo._domainkey IN CNAME odoo._domainkey.odoo.com.``"
#: ../../content/applications/general/email_communication/email_domain.rst:88
msgid "To enable :abbr:`DKIM (DomainKeys Identified Mail)`, add a :abbr:`CNAME (Canonical Name)` record to the :abbr:`DNS (Domain Name System)` zone of the domain name:"
msgstr ""
#: ../../content/applications/general/email_communication/email_domain.rst:89
msgid "If your domain name is `mycompany.com`, you need to create a subdomain `odoo._domainkey.mycompany.com` whose canonical name is `odoo._domainkey.odoo.com.`."
#: ../../content/applications/general/email_communication/email_domain.rst:91
msgid "`odoo._domainkey IN CNAME odoo._domainkey.odoo.com.`"
msgstr ""
#: ../../content/applications/general/email_communication/email_domain.rst:92
msgid "How to create or modify a CNAME record depends on the provider hosting the DNS zone of your domain name. The most common providers are list below."
#: ../../content/applications/general/email_communication/email_domain.rst:94
msgid "If the domain name is `mycompany.com`, make sure to create a subdomain `odoo._domainkey.mycompany.com` whose canonical name is `odoo._domainkey.odoo.com.`."
msgstr ""
#: ../../content/applications/general/email_communication/email_domain.rst:95
msgid "You can check if your DKIM record is valid with a free tool like `DKIM Core <https://dkimcore.org/tools/>`_. If a selector is asked, enter `odoo`."
msgstr ""
#: ../../content/applications/general/email_communication/email_domain.rst:99
msgid "Check your DMARC policy"
#: ../../content/applications/general/email_communication/email_domain.rst:97
msgid "The way to create or modify a :abbr:`CNAME (Canonical Name)` record depends on the provider hosting the :abbr:`DNS (Domain Name System)` zone of the domain name. The most common providers are :ref:`listed below <email_communication/SPFDKIM_common_providers>`."
msgstr ""
#: ../../content/applications/general/email_communication/email_domain.rst:101
msgid "The Domain-based Message Authentication, Reporting & Conformance (DMARC) is a protocol that unifies SPF and DKIM. The instructions contained in the DMARC record of a domain name tell the destination server what to do with an incoming email that fails the SPF and/or DKIM check."
msgid "Check if the :abbr:`DKIM (DomainKeys Identified Mail)` record is valid with a free tool like `DKIM Core <https://dkimcore.org/tools/>`_. If a selector is asked, enter `odoo`."
msgstr ""
#: ../../content/applications/general/email_communication/email_domain.rst:105
msgid "There are three DMARC policies: - ``p=none`` - ``p=quarantine`` - ``p=reject``"
msgid "Check the DMARC policy"
msgstr ""
#: ../../content/applications/general/email_communication/email_domain.rst:110
msgid "``p=quarantine`` and ``p=reject`` instruct the server that receives an email to quarantine that email or ignore it if the SPF and/or DKIM check fails."
#: ../../content/applications/general/email_communication/email_domain.rst:107
msgid "The Domain-based Message Authentication, Reporting, & Conformance (DMARC) record is a protocol that unifies :abbr:`SPF (Sender Policy Framework)` and :abbr:`DKIM (DomainKeys Identified Mail)`. The instructions contained in the :abbr:`DMARC (Domain-based Message Authentication, Reporting, & Conformance)` record of a domain name tell the destination server what to do with an incoming email that fails the :abbr:`SPF (Sender Policy Framework)` and/or :abbr:`DKIM (DomainKeys Identified Mail)` check."
msgstr ""
#: ../../content/applications/general/email_communication/email_domain.rst:113
msgid "If your domain name uses DMARC and has defined one of these policies, it is therefore imperative to be SPF compliant or to enable DKIM."
#: ../../content/applications/general/email_communication/email_domain.rst:114
msgid "There are three :abbr:`DMARC (Domain-based Message Authentication, Reporting, & Conformance)` policies:"
msgstr ""
#: ../../content/applications/general/email_communication/email_domain.rst:117
msgid "Yahoo or AOL are examples of email providers with a DMARC policy set to ``p=reject``. We strongly advise against using an *@yahoo.com* or *@aol.com* address for your users. These emails will never reach their recipient."
msgid "`p=none`"
msgstr ""
#: ../../content/applications/general/email_communication/email_domain.rst:118
msgid "`p=quarantine`"
msgstr ""
#: ../../content/applications/general/email_communication/email_domain.rst:119
msgid "`p=reject`"
msgstr ""
#: ../../content/applications/general/email_communication/email_domain.rst:121
msgid "``p=none`` is used for the domain owner to receive reports about entities using their domain. It should not impact the deliverability if the DMARC check fails."
msgid "`p=quarantine` and `p=reject` instruct the server that receives an email to quarantine that email or ignore it if the :abbr:`SPF (Sender Policy Framework)` and/or :abbr:`DKIM (DomainKeys Identified Mail)` check fails."
msgstr ""
#: ../../content/applications/general/email_communication/email_domain.rst:124
msgid "You can check the DMARC record of a domain name with a tool like `MXToolbox DMARC <https://mxtoolbox.com/DMARC.aspx>`_."
msgstr ""
#: ../../content/applications/general/email_communication/email_domain.rst:127
msgid "If one of your partners, customer or vendor, uses DMARC and has defined one of these policies, the Odoo server cannot relay emails from this partner to your users."
#: ../../content/applications/general/email_communication/email_domain.rst:125
msgid "If the domain name uses :abbr:`DMARC (Domain-based Message Authentication, Reporting, & Conformance)` and has defined one of these policies, the domain must be :abbr:`SPF (Sender Policy Framework)` compliant or enable :abbr:`DKIM (DomainKeys Identified Mail)`."
msgstr ""
#: ../../content/applications/general/email_communication/email_domain.rst:130
msgid "You need to :ref:`handle user notifications in Odoo <discuss_app/notification_preferences>`, or replace the email address of the partner with a default email address."
msgid "Yahoo or AOL are examples of email providers with a :abbr:`DMARC (Domain-based Message Authentication, Reporting, & Conformance)` policy set to `p=reject`. Odoo strongly advises against using an *@yahoo.com* or *@aol.com* address for the database users. These emails will never reach their recipient."
msgstr ""
#: ../../content/applications/general/email_communication/email_domain.rst:136
msgid "SPF, DKIM & DMARC documentation of common providers"
msgstr ""
#: ../../content/applications/general/email_communication/email_domain.rst:138
msgid "`OVH DNS <https://docs.ovh.com/us/en/domains/web_hosting_how_to_edit_my_dns_zone/>`_"
#: ../../content/applications/general/email_communication/email_domain.rst:135
msgid "`p=none` is used for the domain owner to receive reports about entities using their domain. It should not impact the deliverability if the :abbr:`DMARC (Domain-based Message Authentication, Reporting, & Conformance)` check fails."
msgstr ""
#: ../../content/applications/general/email_communication/email_domain.rst:139
msgid "`OVH SPF <https://docs.ovh.com/us/en/domains/web_hosting_the_spf_record/>`_"
msgstr ""
#: ../../content/applications/general/email_communication/email_domain.rst:140
msgid "`GoDaddy TXT record <https://www.godaddy.com/help/add-a-txt-record-19232>`_"
msgstr ""
#: ../../content/applications/general/email_communication/email_domain.rst:141
msgid "`GoDaddy SPF <https://www.godaddy.com/help/add-an-spf-record-19218>`_"
msgid "Check the :abbr:`DMARC (Domain-based Message Authentication, Reporting, & Conformance)` record of a domain name with a tool like `MXToolbox DMARC <https://mxtoolbox.com/DMARC.aspx>`_."
msgstr ""
#: ../../content/applications/general/email_communication/email_domain.rst:142
msgid "`GoDaddy DKIM <https://www.godaddy.com/help/add-a-cname-record-19236>`_"
msgstr ""
#: ../../content/applications/general/email_communication/email_domain.rst:143
msgid "`NameCheap <https://www.namecheap.com/support/knowledgebase/article.aspx/317/2237/how-do-i-add-txtspfdkimdmarc-records-for-my-domain/>`_"
msgstr ""
#: ../../content/applications/general/email_communication/email_domain.rst:144
msgid "`CloudFlare DNS <https://support.cloudflare.com/hc/en-us/articles/360019093151>`_"
msgstr ""
#: ../../content/applications/general/email_communication/email_domain.rst:145
msgid "`Google Domains <https://support.google.com/domains/answer/3290350?hl=en>`_"
msgid "If a partner, customer, or vendor, uses :abbr:`DMARC (Domain-based Message Authentication, Reporting, & Conformance)` and has defined one of these policies, the Odoo server cannot relay emails from this partner to the database users."
msgstr ""
#: ../../content/applications/general/email_communication/email_domain.rst:146
msgid "`Azure DNS <https://docs.microsoft.com/en-us/azure/dns/dns-getstarted-portal>`_"
msgstr ""
#: ../../content/applications/general/email_communication/email_domain.rst:148
msgid "To fully test your configuration, the tool `Mail-Tester <https://www.mail-tester.com/>`_ will give you a full overview of the content and configuration you have in one email sent! Mail-Tester can also be used for other lesser known providers."
msgid "To solve this issue, :ref:`handle user notifications in Odoo <discuss_app/notification_preferences>`, or replace the email address of the partner with a default email address."
msgstr ""
#: ../../content/applications/general/email_communication/email_domain.rst:153
msgid "Use a default email address"
msgid "SPF, DKIM & DMARC documentation of common providers"
msgstr ""
#: ../../content/applications/general/email_communication/email_domain.rst:155
msgid "To force the email address from which emails are sent, you need to create the following key in the System Parameters of the database:"
msgid "`OVH DNS <https://docs.ovh.com/us/en/domains/web_hosting_how_to_edit_my_dns_zone/>`_"
msgstr ""
#: ../../content/applications/general/email_communication/email_domain.rst:156
msgid "`OVH SPF <https://docs.ovh.com/us/en/domains/web_hosting_the_spf_record/>`_"
msgstr ""
#: ../../content/applications/general/email_communication/email_domain.rst:157
msgid "`GoDaddy TXT record <https://www.godaddy.com/help/add-a-txt-record-19232>`_"
msgstr ""
#: ../../content/applications/general/email_communication/email_domain.rst:158
msgid "If ``mail.default.from`` is set, and contains a full email address, all outgoing emails are sent from the given address. This is a requirement to use `Outlook with Odoo <https://docs.microsoft.com/en-us/exchange/mail-flow-best-practices/how-to-set-up-a-multifunction-device-or-application-to-send-email-using-microsoft-365-or-office-365#option-1-authenticate-your-device-or-application-directly-with-a-microsoft-365-or-office-365-mailbox-and-send-mail-using-smtp-auth-client-submission>`_."
msgid "`GoDaddy SPF <https://www.godaddy.com/help/add-an-spf-record-19218>`_"
msgstr ""
#: ../../content/applications/general/email_communication/email_domain.rst:159
msgid "`GoDaddy DKIM <https://www.godaddy.com/help/add-a-cname-record-19236>`_"
msgstr ""
#: ../../content/applications/general/email_communication/email_domain.rst:160
msgid "`NameCheap <https://www.namecheap.com/support/knowledgebase/article.aspx/317/2237/how-do-i-add- txtspfdkimdmarc-records-for-my-domain/>`_"
msgstr ""
#: ../../content/applications/general/email_communication/email_domain.rst:162
msgid "You access the **System Parameters** in :ref:`developer mode <developer-mode>` in the :menuselection:`Settings --> Technical --> Parameters --> System Parameters` menu."
msgid "`CloudFlare DNS <https://support.cloudflare.com/hc/en-us/articles/360019093151>`_"
msgstr ""
#: ../../content/applications/general/email_communication/email_domain.rst:163
msgid "`Google Domains <https://support.google.com/domains/answer/3290350?hl=en>`_"
msgstr ""
#: ../../content/applications/general/email_communication/email_domain.rst:164
msgid "`Azure DNS <https://docs.microsoft.com/en-us/azure/dns/dns-getstarted-portal>`_"
msgstr ""
#: ../../content/applications/general/email_communication/email_domain.rst:166
msgid "To fully test the configuration, use the `Mail-Tester <https://www.mail-tester.com/>`_ tool, which gives a full overview of the content and configuration in one sent email. Mail-Tester can also be used for other, lesser-known providers."
msgstr ""
#: ../../content/applications/general/email_communication/email_domain.rst:171
msgid "Use a default email address"
msgstr ""
#: ../../content/applications/general/email_communication/email_domain.rst:173
msgid "Access the :guilabel:`System Parameters` by activating :ref:`developer mode <developer-mode>` and going to :menuselection:`Settings --> Technical --> Parameters --> System Parameters` menu."
msgstr ""
#: ../../content/applications/general/email_communication/email_domain.rst:176
msgid "To force the email address from which emails are sent, a combination of the following keys needs to be set in the system parameters of the database:"
msgstr ""
#: ../../content/applications/general/email_communication/email_domain.rst:179
msgid "`mail.default.from`: accepts the local part or a complete email address as value"
msgstr ""
#: ../../content/applications/general/email_communication/email_domain.rst:180
msgid "`mail.default.from_filter`: accepts a domain name or a full email address as value"
msgstr ""
#: ../../content/applications/general/email_communication/email_domain.rst:183
msgid "The `mail.default.from_filter` works only for `odoo-bin` configurations, otherwise this parameter can be set using the `from_filter` field on `ir.mail_server`."
msgstr ""
#: ../../content/applications/general/email_communication/email_domain.rst:186
msgid "If the email address of the author does not match `mail.default.from_filter`, the email address is replaced by `mail.default.from` (if it contains a full email address) or a combination of `mail.default.from` and `mail.catchall.domain`."
msgstr ""
#: ../../content/applications/general/email_communication/email_domain.rst:190
msgid "If the `from_filter` contains a full email address, and if the `mail.default.from` is the same as this address, then all of the email addresses that are different from `mail.default.from` will be encapsulated in `mail.default.from`."
msgstr ""
#: ../../content/applications/general/email_communication/email_servers.rst:3
@ -1439,34 +1467,34 @@ msgid "**Original messages**: Several business objects have their own alias to c
msgstr ""
#: ../../content/applications/general/email_communication/email_servers.rst:140
msgid "Sales Channel (to create Leads or Opportunities in `Odoo CRM <https://www.odoo.com/page/crm>`__),"
msgstr ""
#: ../../content/applications/general/email_communication/email_servers.rst:141
msgid "Support Channel (to create Tickets in `Odoo Helpdesk <https://www.odoo.com/page/helpdesk>`__),"
msgid "Sales Channel (to create Leads or Opportunities in `Odoo CRM <https://www.odoo.com/page/ crm>`__),"
msgstr ""
#: ../../content/applications/general/email_communication/email_servers.rst:142
msgid "Support Channel (to create Tickets in `Odoo Helpdesk <https://www.odoo.com/page/helpdesk>`__),"
msgstr ""
#: ../../content/applications/general/email_communication/email_servers.rst:143
msgid "Projects (to create new Tasks in `Odoo Project <https://www.odoo.com/page /project-management>`__),"
msgstr ""
#: ../../content/applications/general/email_communication/email_servers.rst:144
#: ../../content/applications/general/email_communication/email_servers.rst:145
msgid "Job Positions (to create Applicants in `Odoo Recruitment <https://www.odoo.com/page /recruitment>`__),"
msgstr ""
#: ../../content/applications/general/email_communication/email_servers.rst:146
#: ../../content/applications/general/email_communication/email_servers.rst:147
msgid "etc."
msgstr ""
#: ../../content/applications/general/email_communication/email_servers.rst:148
#: ../../content/applications/general/email_communication/email_servers.rst:149
msgid "Depending on the mail server, there might be several methods to fetch emails. The easiest and most recommended method is to manage one email address per Odoo alias in the mail server."
msgstr ""
#: ../../content/applications/general/email_communication/email_servers.rst:151
#: ../../content/applications/general/email_communication/email_servers.rst:152
msgid "Create the corresponding email addresses in the mail server (catchall@, bounce@, sales@, etc.)."
msgstr ""
#: ../../content/applications/general/email_communication/email_servers.rst:152
#: ../../content/applications/general/email_communication/email_servers.rst:153
msgid "Set the :guilabel:`Alias Domain` name in :menuselection:`Settings --> General Settings --> Discuss`."
msgstr ""
@ -1503,22 +1531,58 @@ msgid "This value can be changed in :ref:`developer mode <developer-mode>`. Go t
msgstr ""
#: ../../content/applications/general/email_communication/email_servers.rst:191
msgid "Set up different dedicated servers for transactional and mass mails"
msgid "Utilizing the From Filter on an outgoing email server"
msgstr ""
#: ../../content/applications/general/email_communication/email_servers.rst:193
msgid "In Odoo a separate Mail Transfer Agent (MTA) server can be used for transactional emails and mass mailings. Example: Use Postmark or SendinBlue for transactional emails, and Amazon SES, Mailgun or Sendgrid for mass mailings."
msgid "The :guilabel:`FROM Filtering` field allows for the use of a specific outgoing email server depending on the :guilabel:`From` email address or domain that Odoo is sending on behalf of. This setting can be used to improve the deliverability or sending success rate of emails sent from the database. Setting the :guilabel:`FROM Filtering` field can also be used to send from different domains in a multi-company environment. Access this field in Odoo by navigating to :menuselection:`Settings --> Custom Mail Servers --> Outgoing Mail Servers --> New`."
msgstr ""
#: ../../content/applications/general/email_communication/email_servers.rst:198
msgid "A default outgoing email server is already configured. Do not create an alternative one unless a specific external outgoing email server is needed for technical reasons."
#: ../../content/applications/general/email_communication/email_servers.rst:None
msgid "Outgoing email server settings and the FROM filter settings."
msgstr ""
#: ../../content/applications/general/email_communication/email_servers.rst:201
msgid "To do this, first activate the :ref:`developer mode <developer-mode>`, and then go to :menuselection:`Settings --> Technical --> Outgoing` email servers. There, create two email MTA server settings; one for the transactional emails and one for the mass mailing server. Make sure to give priority to the transactional server over the mass mailing server by providing a lower priority number for the transactional MTA server."
#: ../../content/applications/general/email_communication/email_servers.rst:204
msgid "When an email is sent from Odoo while the :guilabel:`FROM Filtering` field is set, an email server is chosen in the following sequence:"
msgstr ""
#: ../../content/applications/general/email_communication/email_servers.rst:207
msgid "First, Odoo searches for an email server that has the same :guilabel:`FROM Filtering` value as the :guilabel:`From` value (email address) defined in the outgoing email. For example, if the :guilabel:`From` value (email address) is `test\\@example.com`, only the email servers that have the :guilabel:`FROM Filtering` value equal to `test\\@example.com` are returned."
msgstr ""
#: ../../content/applications/general/email_communication/email_servers.rst:211
msgid "However, if no email servers are found that use the :guilabel:`From` value, then Odoo searches for an email server that has the same *domain* as the :guilabel:`From` value (email address) defined in the outgoing email. For example, if the :guilabel:`From` email address is `test\\@example.com`, only the email servers that have the :guilabel:`FROM Filtering` value equal to `example.com` are returned."
msgstr ""
#: ../../content/applications/general/email_communication/email_servers.rst:217
msgid "If no email servers are found after checking for the domain, then Odoo returns all email servers that do not have any :guilabel:`FROM Filtering` value(s) set."
msgstr ""
#: ../../content/applications/general/email_communication/email_servers.rst:220
msgid "Should this query return no results, then Odoo performs a search for an email server using the system parameter: `mail.default.from`. First, the email address listed attempts to match an email server, and then the domain attempts to find a match. If no email server is found, Odoo returns the first outgoing email server (sorted by priority)."
msgstr ""
#: ../../content/applications/general/email_communication/email_servers.rst:226
msgid "If several email servers are found, then Odoo uses the first one according to its priority. For example, if there are two email servers, one with a priority of `10` and the other with a priority of `20`, then the email server with a priority of `10` is used first."
msgstr ""
#: ../../content/applications/general/email_communication/email_servers.rst:231
msgid "Set up different dedicated servers for transactional and mass mails"
msgstr ""
#: ../../content/applications/general/email_communication/email_servers.rst:233
msgid "In Odoo a separate Mail Transfer Agent (MTA) server can be used for transactional emails and mass mailings. Example: Use Postmark or SendinBlue for transactional emails, and Amazon SES, Mailgun or Sendgrid for mass mailings."
msgstr ""
#: ../../content/applications/general/email_communication/email_servers.rst:238
msgid "A default outgoing email server is already configured. Do not create an alternative one unless a specific external outgoing email server is needed for technical reasons."
msgstr ""
#: ../../content/applications/general/email_communication/email_servers.rst:241
msgid "To do this, first activate the :ref:`developer mode <developer-mode>`, and then go to :menuselection:`Settings --> Technical --> Outgoing` email servers. There, create two email MTA server settings; one for the transactional emails and one for the mass mailing server. Make sure to give priority to the transactional server over the mass mailing server by providing a lower priority number for the transactional MTA server."
msgstr ""
#: ../../content/applications/general/email_communication/email_servers.rst:247
msgid "Now, go to :menuselection:`Email Marketing --> Settings` and enable :guilabel:`Dedicated Server`. With these settings, Odoo uses the server with the lower priority for transactional emails, and the server here selected for mass mails. Note that in this case, the domain's Sender Policy Framework (SPF) records must be set to include both transactional and mass mail servers."
msgstr ""

View File

@ -8,7 +8,7 @@ msgid ""
msgstr ""
"Project-Id-Version: Odoo 16.0\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2022-11-17 09:28+0000\n"
"POT-Creation-Date: 2022-12-23 09:13+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"
@ -367,7 +367,6 @@ msgstr ""
#: ../../content/applications/inventory_and_mrp/inventory/shipping/operation/multipack.rst:13
#: ../../content/applications/inventory_and_mrp/inventory/shipping/setup/delivery_method.rst:17
#: ../../content/applications/inventory_and_mrp/inventory/shipping/setup/third_party_shipper.rst:14
#: ../../content/applications/inventory_and_mrp/manufacturing/management/kit_shipping.rst:27
#: ../../content/applications/inventory_and_mrp/manufacturing/management/subcontracting.rst:23
#: ../../content/applications/inventory_and_mrp/manufacturing/management/use_mps.rst:9
msgid "Configuration"
@ -5070,196 +5069,232 @@ msgstr ""
msgid "Manufacturing several different products simultaneously at the same work center is a common issue for manufacturing companies. Although in practice, employees can manufacture the goods at another work center instead of waiting for one to be available, it's not always simple to have visibility on which work center is busy and plan resources accordingly in real-time."
msgstr ""
#: ../../content/applications/inventory_and_mrp/manufacturing/management/alternative_wc.rst:11
#: ../../content/applications/inventory_and_mrp/manufacturing/management/alternative_wc.rst:10
msgid "With Odoo, you can configure alternative work centers to solve this issue. This automatically checks which work center is busy and which equivalent ones are free, and schedules orders and maintenance accordingly."
msgstr ""
#: ../../content/applications/inventory_and_mrp/manufacturing/management/alternative_wc.rst:15
#: ../../content/applications/inventory_and_mrp/manufacturing/management/alternative_wc.rst:14
msgid "This way, your process becomes more efficient, as work center utilisation is optimised."
msgstr ""
#: ../../content/applications/inventory_and_mrp/manufacturing/management/alternative_wc.rst:19
#: ../../content/applications/inventory_and_mrp/manufacturing/management/alternative_wc.rst:17
msgid "Configure your Work Centers"
msgstr ""
#: ../../content/applications/inventory_and_mrp/manufacturing/management/alternative_wc.rst:21
msgid "First, go to the :menuselection:`Manufacturing app --> Configuration --> Settings`. Then, enable the Work Orders feature and hit save."
#: ../../content/applications/inventory_and_mrp/manufacturing/management/alternative_wc.rst:19
msgid "First, go to the :menuselection:`Manufacturing app --> Configuration --> Settings`. Then, enable the :guilabel:`Work Orders` feature and hit :guilabel:`Save`."
msgstr ""
#: ../../content/applications/inventory_and_mrp/manufacturing/management/alternative_wc.rst:None
msgid "work order settings ticked"
msgid "Work order settings ticked in Odoo Manufacturing."
msgstr ""
#: ../../content/applications/inventory_and_mrp/manufacturing/management/alternative_wc.rst:29
#: ../../content/applications/inventory_and_mrp/manufacturing/management/alternative_wc.rst:26
msgid "Now, go to :menuselection:`Configuration --> Work Centers` and create two new work centers. Add the second work center as an alternative to the first one and vice versa."
msgstr ""
#: ../../content/applications/inventory_and_mrp/manufacturing/management/alternative_wc.rst:38
msgid "Next, go to :menuselection:`Products --> Bills of Materials`, choose your product, and add these work centers to the operations of your BOM."
#: ../../content/applications/inventory_and_mrp/manufacturing/management/alternative_wc.rst:None
msgid "Create a secondary work center as an alternate to the first."
msgstr ""
#: ../../content/applications/inventory_and_mrp/manufacturing/management/alternative_wc.rst:48
#: ../../content/applications/inventory_and_mrp/manufacturing/management/alternative_wc.rst:33
msgid "Next, go to :menuselection:`Products --> Bills of Materials`, choose your product, and add these work centers to the operations of your :abbr:`BoM (Bill of Materials)`."
msgstr ""
#: ../../content/applications/inventory_and_mrp/manufacturing/management/alternative_wc.rst:None
msgid "Add work centers to Bill of Materials operations."
msgstr ""
#: ../../content/applications/inventory_and_mrp/manufacturing/management/alternative_wc.rst:41
msgid "Create your Work Orders"
msgstr ""
#: ../../content/applications/inventory_and_mrp/manufacturing/management/alternative_wc.rst:50
msgid "Now that everything is configured, you can create your *Work Orders*. Go to :menuselection:`Operations --> Manufacturing Orders`, and hit **Create**. There, add your product to your manufacturing order and plan it. You can then retrieve them from the Work Orders list view, under Operations > Work Orders."
#: ../../content/applications/inventory_and_mrp/manufacturing/management/alternative_wc.rst:43
msgid "Now that everything is configured, you can create your *Work Orders*."
msgstr ""
#: ../../content/applications/inventory_and_mrp/manufacturing/management/alternative_wc.rst:55
#: ../../content/applications/inventory_and_mrp/manufacturing/management/alternative_wc.rst:45
msgid "Go to :menuselection:`Operations --> Manufacturing Orders`, and hit :guilabel:`Create`. There, add your product to your manufacturing order and plan it. You can then retrieve them from the :guilabel:`Work Orders` list view, under :menuselection:`Operations > Work Orders`."
msgstr ""
#: ../../content/applications/inventory_and_mrp/manufacturing/management/alternative_wc.rst:49
msgid "Each new *Work Order*, which will be created before the end of the first one, will be scheduled at the alternative work center you configured, as shown below."
msgstr ""
#: ../../content/applications/inventory_and_mrp/manufacturing/management/alternative_wc.rst:64
#: ../../content/applications/inventory_and_mrp/manufacturing/management/alternative_wc.rst:None
msgid "Work order creation and scheduling."
msgstr ""
#: ../../content/applications/inventory_and_mrp/manufacturing/management/alternative_wc.rst:57
msgid "Keep in mind that, if you add time after production to your work center, you may have work orders scheduled for your alternative work center even if the usual one is free."
msgstr ""
#: ../../content/applications/inventory_and_mrp/manufacturing/management/bill_configuration.rst:3
msgid "Create Bills of Materials"
msgid "Create a bill of materials"
msgstr ""
#: ../../content/applications/inventory_and_mrp/manufacturing/management/bill_configuration.rst:5
msgid "A *Bill of Materials* is a document defining the quantity of each component required to make or deliver a finished product. Additionally, it can also include various operations and individual step guidelines needed to complete a production process."
msgid "A *Bill of Materials* (or *BoM* for short) is a document that defines the quantity of each component required to make or deliver a finished product. It can also include various operations and the individual step guidelines needed to complete a production process."
msgstr ""
#: ../../content/applications/inventory_and_mrp/manufacturing/management/bill_configuration.rst:10
msgid "With Odoo's MRP solution, multiple BOMs can also be linked to each product, so that even product variants can have their *own* tailored BOM."
#: ../../content/applications/inventory_and_mrp/manufacturing/management/bill_configuration.rst:9
msgid "In Odoo Manufacturing, multiple :abbr:`BoMs (Bills of Materials)` can be linked to each product, so that even product variants can have their own tailored :abbr:`BoMs (Bills of Materials)`."
msgstr ""
#: ../../content/applications/inventory_and_mrp/manufacturing/management/bill_configuration.rst:13
msgid "This will help you to optimize your manufacturing process and save time as a result."
#: ../../content/applications/inventory_and_mrp/manufacturing/management/bill_configuration.rst:12
msgid "Correctly setting up a :abbr:`BoM (Bill of Materials)` helps optimize the manufacturing process and save time."
msgstr ""
#: ../../content/applications/inventory_and_mrp/manufacturing/management/bill_configuration.rst:17
msgid "Setting up a BoM"
#: ../../content/applications/inventory_and_mrp/manufacturing/management/bill_configuration.rst:16
msgid "Set up a bill of baterials (BoM)"
msgstr ""
#: ../../content/applications/inventory_and_mrp/manufacturing/management/bill_configuration.rst:18
msgid "The simplest BoM set up is one without operations or instructions. In this case, you will manage your production using Manufacturing Orders only."
msgid "The simplest :abbr:`BoM (Bill of Materials)` setup is one without operations or instructions, only components. In this case, the production is solely managed using *Manufacturing Orders*."
msgstr ""
#: ../../content/applications/inventory_and_mrp/manufacturing/management/bill_configuration.rst:22
msgid "To create a BoM from the Manufacturing module, go to :menuselection:`Products --> Bills of Materials`. If you click **Create**, the first thing you'll have to do is to specify the final product. For an existing product, simply select it from the list, or create a new one on the spot. Note that if you go through the product form to create your BOM, the product will already be set for you."
#: ../../content/applications/inventory_and_mrp/manufacturing/management/bill_configuration.rst:21
msgid "To create a :abbr:`BoM (Bill of Materials)` from the :guilabel:`Manufacturing` module, go to :menuselection:`Products --> Bills of Materials`. Then, click :guilabel:`Create`. Next, specify the :guilabel:`Product`."
msgstr ""
#: ../../content/applications/inventory_and_mrp/manufacturing/management/bill_configuration.rst:27
msgid "For a standard Bill of Material, keep the default *BoM* type, which is *Manufacture this Product*. Now specify the various components that make up the production of your final product and their respective quantities. You can create components as you go, on the BOM, or create products beforehand, by going to the :menuselection:`Top Menu --> Products --> Create`, and add them later on."
#: ../../content/applications/inventory_and_mrp/manufacturing/management/bill_configuration.rst:26
msgid "A :abbr:`BoM (Bill of Materials)` can also be created directly from the product form, in which case the :guilabel:`Product` field is pre-filled."
msgstr ""
#: ../../content/applications/inventory_and_mrp/manufacturing/management/bill_configuration.rst:37
msgid "The destination location should **not** be a scrap location. A scrap location is where you put products that you don't need."
#: ../../content/applications/inventory_and_mrp/manufacturing/management/bill_configuration.rst:29
msgid "For a standard :abbr:`BoM (Bill of Materials)`, set the :guilabel:`BoM Type` to :guilabel:`Manufacture this Product`. Then, click :guilabel:`Add a Line` to specify the various components that make up the production of the final product and their respective quantities. New components can be created quickly through the :abbr:`BoM (Bill of Materials)`, or can be created beforehand in :menuselection:`Manufacturing --> Products --> Products --> Create`. Finally, click :guilabel:`Save` to finish creating the :abbr:`BoM (Bill of Materials)`."
msgstr ""
#: ../../content/applications/inventory_and_mrp/manufacturing/management/bill_configuration.rst:None
msgid "Set up a Bill of Materials."
msgstr ""
#: ../../content/applications/inventory_and_mrp/manufacturing/management/bill_configuration.rst:41
msgid "Using the same BoM to describe Variants"
msgid "Specify a bill of materials (BoM) for a product variant"
msgstr ""
#: ../../content/applications/inventory_and_mrp/manufacturing/management/bill_configuration.rst:43
msgid "As suggested above, you can use *BOMs* for specific *Product Variants*. Once the various attributes have been configured on the product form, there are two ways to configure the appropriate BoM for the respective product combination."
msgid ":abbr:`BoMs (Bills of Materials)` can also be assigned to specific *Product Variants*, with two setup options available to choose from."
msgstr ""
#: ../../content/applications/inventory_and_mrp/manufacturing/management/bill_configuration.rst:47
msgid "Either create one BoM per variant, by specifying the Product Variant in the dedicated field below the product name. Or use one BOM, that contains all of the components and for each component, indicate which variant it applies to, using the *Apply on Variants* column, as shown below."
msgid "In order to assign :abbr:`BoMs (Bills of Materials)` to product variants, the product's variant attributes must already be configured on the product form."
msgstr ""
#: ../../content/applications/inventory_and_mrp/manufacturing/management/bill_configuration.rst:57
msgid "Adding Operations"
#: ../../content/applications/inventory_and_mrp/manufacturing/management/bill_configuration.rst:50
msgid "The first method is to create one :abbr:`BoM (Bill of Materials)` per variant by creating a new :abbr:`BoM (Bill of Materials)` and specifying the :guilabel:`Product Variant`. The second method is to create one master :abbr:`BoM (Bill of Materials)` that contains all of the components, and specify which variant each component applies to using the :guilabel:`Apply on Variants` column."
msgstr ""
#: ../../content/applications/inventory_and_mrp/manufacturing/management/bill_configuration.rst:59
msgid "You can also add operations to your *BoM*, if you want workers to follow instructions or register time spent. To use this feature, enable the *Work Orders* feature in the *Manufacturing* app settings, as shown below."
#: ../../content/applications/inventory_and_mrp/manufacturing/management/bill_configuration.rst:None
msgid "Product Variants in the Bill of Materials."
msgstr ""
#: ../../content/applications/inventory_and_mrp/manufacturing/management/bill_configuration.rst:60
msgid "Set up operations"
msgstr ""
#: ../../content/applications/inventory_and_mrp/manufacturing/management/bill_configuration.rst:62
msgid "Add an :guilabel:`Operation` to a :abbr:`BoM (Bill of Materials)` to specify instructions for production and register time spent on an operation. To use this feature, first enable the :guilabel:`Work Orders` feature in :menuselection:`Manufacturing --> Configuration --> Settings --> Operations`."
msgstr ""
#: ../../content/applications/inventory_and_mrp/manufacturing/management/bill_configuration.rst:67
msgid "Each operation is unique as it is always linked to only one BOM. This being said, Operations Operations can be re-used when configuring a new BOM, with the *Copy Existing Operations* feature."
msgid "Then, when creating a new :abbr:`BoM (Bill of Materials)`, click on the :guilabel:`Operations` tab and click :guilabel:`Add a line` to add a new operation. In the :guilabel:`Create Operations` box, give the operation a name, specify the :guilabel:`Work Center` and duration settings. Like components, Odoo gives the option to specify a product variant in the :guilabel:`Apply on Variants` field so the operation only applies to that variant. Finally, click :guilabel:`Save & Close`."
msgstr ""
#: ../../content/applications/inventory_and_mrp/manufacturing/management/bill_configuration.rst:74
msgid "Finally, just like for components, operations can also be variant specific only, as shown below."
msgid "Each operation is unique, as it is always exclusively linked to one :abbr:`BoM (Bill of Materials)`. Operations can be reused when configuring a new :abbr:`BoM (Bill of Materials)`, with the :guilabel:`Copy Existing Operations` feature."
msgstr ""
#: ../../content/applications/inventory_and_mrp/manufacturing/management/bill_configuration.rst:82
msgid "Adding By-Products"
#: ../../content/applications/inventory_and_mrp/manufacturing/management/bill_configuration.rst:None
msgid "Copy Existing Operations feature."
msgstr ""
#: ../../content/applications/inventory_and_mrp/manufacturing/management/bill_configuration.rst:84
msgid "A *by-product* is a product that is produced on top of the main product of a *BoM*. As opposed to the primary product, there can be more than one on a BOM."
#: ../../content/applications/inventory_and_mrp/manufacturing/management/bill_configuration.rst:83
msgid "Add by-products to a bill of materials (BoM)"
msgstr ""
#: ../../content/applications/inventory_and_mrp/manufacturing/management/bill_configuration.rst:87
msgid "To add *by-products* to a *BoM*, you will first need to enable the by-product feature from the *Manufacturing* app settings."
#: ../../content/applications/inventory_and_mrp/manufacturing/management/bill_configuration.rst:85
msgid "A *By-Product* is a residual product that is created during production in addition to the main product of a :abbr:`BoM (Bill of Materials)`. Unlike the primary product, there can be more than one by-product on a :abbr:`BoM (Bill of Materials)`."
msgstr ""
#: ../../content/applications/inventory_and_mrp/manufacturing/management/bill_configuration.rst:93
msgid "Once the feature is enabled, you can add *by-products* to your *BoMs*. Note that if you have Operations, you'll need to specify in which operation the by-product is produced."
#: ../../content/applications/inventory_and_mrp/manufacturing/management/bill_configuration.rst:89
msgid "To add by-products to a :abbr:`BoM (Bill of Materials)`, first enable the :guilabel:`By-Products` feature in :menuselection:`Manufacturing --> Configuration --> Settings --> Operations`."
msgstr ""
#: ../../content/applications/inventory_and_mrp/manufacturing/management/bill_configuration.rst:92
msgid "Once the feature is enabled, you can add by-products to a :abbr:`BoM (Bill of Materials)` by clicking on the :guilabel:`Operations` tab and clicking :guilabel:`Add a line`. Then, name the by-product and indicate the :guilabel:`Quantity` and the :guilabel:`Unit of Measure`. If the :abbr:`BoM (Bill of Materials)` has configured operations, specify exactly which operation the by-product is produced from in the :guilabel:`Produced in Operation` field. Finally, click :guilabel:`Save`."
msgstr ""
#: ../../content/applications/inventory_and_mrp/manufacturing/management/kit_shipping.rst:3
msgid "Kits"
msgid "Use kits"
msgstr ""
#: ../../content/applications/inventory_and_mrp/manufacturing/management/kit_shipping.rst:5
msgid "A *kit* is a set of components that are not pre-assembled or mixed. This is useful for selling but also for creating cleaner and more effective *BOMs*. To use kits, you need both the Manufacturing and Inventory apps to be installed."
msgid "A *kit* is a set of unassembled components. Kits may be sold as products, but are also useful tools for managing more complex bills of materials (BoMs). To use kits, the :guilabel:`Manufacturing` and :guilabel:`Inventory` applications need to be installed."
msgstr ""
#: ../../content/applications/inventory_and_mrp/manufacturing/management/kit_shipping.rst:10
msgid "Manage Stock of Component Products"
msgid "Create the kit as a product"
msgstr ""
#: ../../content/applications/inventory_and_mrp/manufacturing/management/kit_shipping.rst:12
msgid "If you want to assemble kits as they are ordered, managing stock of the kit components only, you will use a *Kit BoM* Type without any manufacturing operations."
msgid "To use a kit as a sellable product or simply as a component organization tool, the kit should first be created as a product. To create a kit product, go to :menuselection:`Manufacturing or Inventory --> Products --> Products`, and then click :guilabel:`Create`."
msgstr ""
#: ../../content/applications/inventory_and_mrp/manufacturing/management/kit_shipping.rst:15
msgid "A product using a *Kit BoM* will appear as a single line item on a quotation and a sales order, but will generate a delivery order with one line item for each of the components of the kit. In the examples below, the first image shows a sales order for the kit *Custom Computer Kit*, while the second image shows the corresponding delivery order."
#: ../../content/applications/inventory_and_mrp/manufacturing/management/kit_shipping.rst:16
msgid "Next, set the :guilabel:`Product Type` to :guilabel:`Storable Product`: this allows for management of kit inventory. The :guilabel:`Route` designation under the :guilabel:`Inventory` tab does not matter, since Odoo uses the routes of the kit's components for replenishment purposes. All other parameters for the kit product may be modified according to preference. Finally, click :guilabel:`Save`."
msgstr ""
#: ../../content/applications/inventory_and_mrp/manufacturing/management/kit_shipping.rst:29
msgid "From the *Products menu* in either the *Inventory* or *Manufacturing* app, create each component product (as you would with any other product), then create the top-level, or kit product. Because you cannot track the stock of kit products, the *Product Type* should be set to *Consumable*. However, if you are using Anglo-Saxon accounting, and you would like COGS to be posted when invoicing your kits (and only for this reason), the storable product type should selected instead. Because a kit product cannot be purchased, *Can be Purchased* should be unchecked. The route of the kit product in the *Inventory* Tab does not really matter, as, for replenishment, only the route of the components that will be taken into account only."
#: ../../content/applications/inventory_and_mrp/manufacturing/management/kit_shipping.rst:22
msgid "The kit's components must also be configured as products via :menuselection:`Manufacturing or Inventory --> Products --> Products`. These components require no specific configuration."
msgstr ""
#: ../../content/applications/inventory_and_mrp/manufacturing/management/kit_shipping.rst:26
msgid "Set up the kit BoM"
msgstr ""
#: ../../content/applications/inventory_and_mrp/manufacturing/management/kit_shipping.rst:28
msgid "After fully configuring the kit product and its components, create a :abbr:`BoM (Bill of Materials)` for the kit product. Go to :menuselection:`Manufacturing --> Products --> Bills of Materials`, and then click :guilabel:`Create`. Next, set the :guilabel:`Product` field to the previously configured kit product. Then, set the :guilabel:`BoM Type` to :guilabel:`Kit`. Finally, add each component and specify its quantity. Make sure to :guilabel:`Save` the changes."
msgstr ""
#: ../../content/applications/inventory_and_mrp/manufacturing/management/kit_shipping.rst:None
msgid "Kit selection on the bill of materials."
msgstr ""
#: ../../content/applications/inventory_and_mrp/manufacturing/management/kit_shipping.rst:38
msgid "All other parameters on the kit product may be modified according to your preference. The component products require no particular configuration."
msgid "If the kit is solely being used as a sellable product, then only components need to be added under the :guilabel:`Components` tab, and configuring manufacturing operations is not necessary."
msgstr ""
#: ../../content/applications/inventory_and_mrp/manufacturing/management/kit_shipping.rst:41
msgid "Once the products are configured, create a *bill of materials* for the kit product. Add each component and its quantity. Select the *BoM Type* Kit. All other options may be left with their default values."
#: ../../content/applications/inventory_and_mrp/manufacturing/management/kit_shipping.rst:42
msgid "When a kit is sold as a product, it appears as a single line item on the quotation and sales order. However, on delivery orders, each component of the kit is listed."
msgstr ""
#: ../../content/applications/inventory_and_mrp/manufacturing/management/kit_shipping.rst:46
msgid "Use kits to manage complex BoMs"
msgstr ""
#: ../../content/applications/inventory_and_mrp/manufacturing/management/kit_shipping.rst:48
msgid "Manage Stock of Kit Product and Component Products"
msgid "Kits are also used to manage *multilevel* :abbr:`BoMs (Bills of Materials)`. These are products that contain other products as components and therefore require nested :abbr:`BoMs (Bills of Materials)`. Incorporating pre-configured kits into multilevel :abbr:`BoMs (Bills of Materials)` allows for cleaner organization of bundled products. Under :guilabel:`Components`, list a kit as a component in a higher-level product's :abbr:`BoM (Bills of Material)` to eliminate the need to add the kit's parts individually. Any :guilabel:`BoM Type` can be used for the higher-level product's :abbr:`BoM (Bill of Materials)`."
msgstr ""
#: ../../content/applications/inventory_and_mrp/manufacturing/management/kit_shipping.rst:50
msgid "If you want to manage the stock of the *top-level kit product*, you will use a standard *BoM Type* manufacture or subcontracting instead. In this case you will either buy the final product from your subcontractor, or make it yourself through a manufacturing order."
#: ../../content/applications/inventory_and_mrp/manufacturing/management/kit_shipping.rst:None
msgid "Kit as a component in a multilevel bill of materials."
msgstr ""
#: ../../content/applications/inventory_and_mrp/manufacturing/management/kit_shipping.rst:54
msgid "In that case the product type will be storable, and the BOM type either 'Manufacture this product' or 'Subcontracting' as shown below."
#: ../../content/applications/inventory_and_mrp/manufacturing/management/kit_shipping.rst:60
msgid "To access a comprehensive overview of the multilevel :abbr:`BoM's (Bill of Material's)` components, click on the :guilabel:`Structure & Cost` smart button. Sublevel :abbr:`BoMs (Bills of Materials)` can be expanded and viewed from this report."
msgstr ""
#: ../../content/applications/inventory_and_mrp/manufacturing/management/kit_shipping.rst:62
msgid "Build a cleaner BOM"
#: ../../content/applications/inventory_and_mrp/manufacturing/management/kit_shipping.rst:None
msgid "Expanded kit in the Structure and Cost report."
msgstr ""
#: ../../content/applications/inventory_and_mrp/manufacturing/management/kit_shipping.rst:64
msgid "As suggested above, a kit BOM can also simply be used to manage a more complex BOM."
#: ../../content/applications/inventory_and_mrp/manufacturing/management/kit_shipping.rst:68
msgid "When creating a manufacturing order for a product with a multilevel :abbr:`BoM (Bill of Materials)`, the kit product automatically expands to show all components. Any operations in the kit's :abbr:`BoM (Bill of Materials)` are also added to the list of work orders on the manufacturing order."
msgstr ""
#: ../../content/applications/inventory_and_mrp/manufacturing/management/kit_shipping.rst:66
msgid "Imagine the Custom Computer parts above were part of another final product. It would be much clearer and simpler if the BOMs were added together (as shown below) instead of adding all the individual parts one by one."
msgstr ""
#: ../../content/applications/inventory_and_mrp/manufacturing/management/kit_shipping.rst:73
msgid "This is even better illustrated when looking at the BOM Structure Report, where it is easy to expand and hide specific kit level or sub-assembly type BOMs."
msgstr ""
#: ../../content/applications/inventory_and_mrp/manufacturing/management/kit_shipping.rst:79
msgid "On the creation of the manufacturing order, the BOM will automatically expand to show all top level and kit level components. You can go back to the BOM at any point though as it remains available on the form view of your manufacturing order."
msgstr ""
#: ../../content/applications/inventory_and_mrp/manufacturing/management/kit_shipping.rst:86
msgid "Finally, note that if there were any Operations in the Kit BOM, these would also simply be added in to the work order list of the main component."
#: ../../content/applications/inventory_and_mrp/manufacturing/management/kit_shipping.rst:74
msgid "Kits are primarily used to bundle components together for organization or sale. To manage multilevel products that require manufactured subcomponents, refer to :doc:`this documentation <sub_assemblies>` on sub-assemblies."
msgstr ""
#: ../../content/applications/inventory_and_mrp/manufacturing/management/product_variants.rst:3

File diff suppressed because it is too large Load Diff

View File

@ -8,7 +8,7 @@ msgid ""
msgstr ""
"Project-Id-Version: Odoo 16.0\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2022-11-17 09:28+0000\n"
"POT-Creation-Date: 2022-12-23 09:13+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"
@ -21,6 +21,7 @@ msgid "Marketing"
msgstr ""
#: ../../content/applications/marketing/marketing_automation.rst:8
#: ../../content/applications/marketing/marketing_automation/getting_started/first_campaign.rst:3
msgid "Marketing Automation"
msgstr ""
@ -34,75 +35,445 @@ msgid "Advanced"
msgstr ""
#: ../../content/applications/marketing/marketing_automation/advanced/understanding_metrics.rst:3
msgid "Understanding Metrics"
msgid "Understanding metrics"
msgstr ""
#: ../../content/applications/marketing/marketing_automation/advanced/understanding_metrics.rst:4
msgid "Metrics are values that help you measure progress and can be a powerful way of linking your employees to goals."
#: ../../content/applications/marketing/marketing_automation/advanced/understanding_metrics.rst:5
msgid "Metrics are detailed statistics that measure the progress (and success) of marketing campaigns. When creating marketing activities in a workflow, Odoo will visually display various metrics related to the campaign with graphs and data."
msgstr ""
#: ../../content/applications/marketing/marketing_automation/advanced/understanding_metrics.rst:9
msgid "When you create a workflow in Odoo, its visual content already shows metrics in a graph form and in numbers."
msgstr ""
#: ../../content/applications/marketing/marketing_automation/advanced/understanding_metrics.rst:10
msgid "Lets consider the example below:"
msgid "Consider the following example:"
msgstr ""
#: ../../content/applications/marketing/marketing_automation/advanced/understanding_metrics.rst:None
#: ../../content/applications/marketing/marketing_automation/advanced/understanding_metrics.rst:None
#: ../../content/applications/marketing/marketing_automation/advanced/understanding_metrics.rst:None
#: ../../content/applications/marketing/marketing_automation/advanced/understanding_metrics.rst:0
#: ../../content/applications/marketing/marketing_automation/advanced/understanding_metrics.rst:None
msgid "Metrics in Odoo Marketing Automation"
msgid "An example of a marketing automation campaign in Odoo."
msgstr ""
#: ../../content/applications/marketing/marketing_automation/advanced/understanding_metrics.rst:15
msgid "In this case, the :guilabel:`Target` of this campaign is set to :guilabel:`Lead/Opportunity` and was narrowed down to only focus on the Leads (or Opportunities) whose :guilabel:`Tag Name` contain a value of `product` and they *also* have an email address set up in the database."
msgstr ""
#: ../../content/applications/marketing/marketing_automation/advanced/understanding_metrics.rst:19
msgid "The *Target* - business object - is *Lead/Opportunity* and was narrowed down to the ones whose *Tag Name* contain the description “Product”, and have an email address set."
msgid "Beneath the filter nodes, Odoo will display how many records in the database fall into the previously-specified criteria filter. In this example, there are 18 records in the database that match the criteria."
msgstr ""
#: ../../content/applications/marketing/marketing_automation/advanced/understanding_metrics.rst:20
msgid "A total number of 20 records match the criteria."
#: ../../content/applications/marketing/marketing_automation/advanced/understanding_metrics.rst:None
msgid "Lead generation filters used to refine records on marketing automation campaigns in Odoo."
msgstr ""
#: ../../content/applications/marketing/marketing_automation/advanced/understanding_metrics.rst:28
msgid "Out of those 20 records, 25 have become participants, in other words, they have matched the criteria."
#: ../../content/applications/marketing/marketing_automation/advanced/understanding_metrics.rst:27
msgid "At the top of the marketing automation form, there are a series of smart buttons. The :guilabel:`Participations` smart button in this example indicates that, out of those 18 records, 25 have become participants. In other words, they have matched the criteria, and have already interacted with the campaign in one way or another."
msgstr ""
#: ../../content/applications/marketing/marketing_automation/advanced/understanding_metrics.rst:36
msgid "Every time the system runs, updating numbers and triggering actions, it will look at the *Target* model and check if new records have been added or modified, keeping the flow up-to-date."
#: ../../content/applications/marketing/marketing_automation/advanced/understanding_metrics.rst:33
msgid ":guilabel:`Records` represent a real-time number. Therefore, while the workflow is running, changes in opportunity records (deletions, additions, adjustments) may occur. This means there will be real-time updates to the number of :guilabel:`Records`, but such updates do *not* change the number of :guilabel:`Participants`, as the metric *will not* exclude opportunities that have already been set as :guilabel:`Participants` before - Odoo will just add new ones. That's why the number of :guilabel:`Records` can be different from the number of :guilabel:`Participants` from time to time."
msgstr ""
#: ../../content/applications/marketing/marketing_automation/advanced/understanding_metrics.rst:41
msgid "The filter here is applied to *all* activities. Leads that lose the tag in the meantime will be excluded from later activities."
#: ../../content/applications/marketing/marketing_automation/advanced/understanding_metrics.rst:None
msgid "Difference between real-time record count and total participants on a markeing campaign."
msgstr ""
#: ../../content/applications/marketing/marketing_automation/advanced/understanding_metrics.rst:45
msgid "*Records* is a real-time number, therefore while the workflow is running, changes in opportunity records can be made - delete, add, adjustment - updating the number of records, but not changing the number of participants, as the metric *will not* exclude opportunities that have been set as participants before. It will just add new ones. For this reason, the number of *Records* can be different from the number of *Participants*."
msgid "Whenever the system runs, updating numbers and triggering actions, it will look at the :guilabel:`Target` model, and check if new :guilabel:`Records` have been added (or modified), which always keeps the flow up-to-date."
msgstr ""
#: ../../content/applications/marketing/marketing_automation/advanced/understanding_metrics.rst:50
msgid "The filter here is applied to *all* activities. Leads that lose that specific :guilabel:`Tag` in the meantime will be excluded from later activities."
msgstr ""
#: ../../content/applications/marketing/marketing_automation/advanced/understanding_metrics.rst:54
msgid "Filters can also be applied to individual activities, in the :guilabel:`Domain` section of the activity pop-up form. Use this feature to specify an individual filter that will only be performed if the records satisfy *both* filter criteria - the activity filter and its specific domain filter."
msgstr ""
#: ../../content/applications/marketing/marketing_automation/advanced/understanding_metrics.rst:59
msgid "(*Example*: when configuring an SMS activity, make sure a certain phone number is set, in order to avoid triggering a SMS that would never be sent.)"
msgstr ""
#: ../../content/applications/marketing/marketing_automation/advanced/understanding_metrics.rst:0
msgid "You can also have filters applied to activities individually, under *Domain*. A useful feature to specify an individual filter that will only be performed if the records satisfied both filters, the activity and its domain one."
msgid "A relevant targeting filter that applies to a type of individual activity."
msgstr ""
#: ../../content/applications/marketing/marketing_automation/advanced/understanding_metrics.rst:0
msgid "Example: for an activity sending an SMS, you could make sure a phone number is set to avoid triggering a SMS that would never be sent and crash."
#: ../../content/applications/marketing/marketing_automation/advanced/understanding_metrics.rst:66
msgid ":guilabel:`Success` represents the number of times the searching for participants - who match the criteria filter(s) of that activity - was performed successfully, in relation to the total number of participants. If a participant does *not* match the conditions, it will be added to :guilabel:`Rejected`."
msgstr ""
#: ../../content/applications/marketing/marketing_automation/advanced/understanding_metrics.rst:64
msgid "*Success* is the number of times the searching for participants - that match the filter(s) of that activity - was performed successfully in relation to the total number of participants."
msgstr ""
#: ../../content/applications/marketing/marketing_automation/advanced/understanding_metrics.rst:65
msgid "If a participant does not match the conditions, it will be added to *Rejected*."
msgstr ""
#: ../../content/applications/marketing/marketing_automation/advanced/understanding_metrics.rst:71
msgid "Hovering over the graph, you can see the number of successful and rejected participants, per day, for the last 15 days."
#: ../../content/applications/marketing/marketing_automation/advanced/understanding_metrics.rst:None
msgid "Overview showing participants who do or do not match filtering criteria on an activity."
msgstr ""
#: ../../content/applications/marketing/marketing_automation/advanced/understanding_metrics.rst:75
msgid "Every time a new record is added to the *Target* model, it will be automatically added to the workflow, and, it will start the workflow from the beginning (parent action)."
msgid "Hovering over the graph, Odoo displays the number of successful and rejected participants, per day, over the last 15 days."
msgstr ""
#: ../../content/applications/marketing/marketing_automation/advanced/understanding_metrics.rst:79
msgid "Whenever a new record is added to the :guilabel:`Target` model, it will automatically be added to the workflow, and it will start the workflow from the beginning (:guilabel:`Parent Action`)."
msgstr ""
#: ../../content/applications/marketing/marketing_automation/getting_started.rst:5
msgid "Getting Started"
msgstr ""
#: ../../content/applications/marketing/marketing_automation/getting_started/first_campaign.rst:5
msgid "The Odoo Marketing Automation app automates a variety of marketing tasks by combining specific rules and filters to generate timed actions. Instead of manually having to build each stage of a campaign (such as a series of timed massmails), the Marketing Automation app allows marketers to build the entire campaign, and all of its stages, in one place on one dashboard."
msgstr ""
#: ../../content/applications/marketing/marketing_automation/getting_started/first_campaign.rst:11
msgid "Create a campaign"
msgstr ""
#: ../../content/applications/marketing/marketing_automation/getting_started/first_campaign.rst:13
msgid "To create a new automated marketing campaign, open the :guilabel:`Marketing Automation` app and click :guilabel:`Create`. On the :guilabel:`Campaign` page, there are the following smart buttons and fields:"
msgstr ""
#: ../../content/applications/marketing/marketing_automation/getting_started/first_campaign.rst:None
msgid "A dashboard showing the creation of a new marketing automation campaign in Odoo."
msgstr ""
#: ../../content/applications/marketing/marketing_automation/getting_started/first_campaign.rst:21
msgid ":guilabel:`Templates`: represents the number of pre-configured mail templates being used in this particular campaign. (Templates can always be created on-the-fly as well)."
msgstr ""
#: ../../content/applications/marketing/marketing_automation/getting_started/first_campaign.rst:23
msgid ":guilabel:`SMS`: represents the number of personalized SMS messages connected to this campaign."
msgstr ""
#: ../../content/applications/marketing/marketing_automation/getting_started/first_campaign.rst:24
msgid ":guilabel:`Clicks`: represents the number of times attached links have been clicked by recipients of this campaign."
msgstr ""
#: ../../content/applications/marketing/marketing_automation/getting_started/first_campaign.rst:26
msgid ":guilabel:`Participants`: represents the number of contacts that have directly participated in this campaign."
msgstr ""
#: ../../content/applications/marketing/marketing_automation/getting_started/first_campaign.rst:28
msgid ":guilabel:`Target`: this field is a drop-down menu to choose which model is targeted by this campaign (i.e., by Contacts, Sales Order, Lead/Opportunity, etc.)."
msgstr ""
#: ../../content/applications/marketing/marketing_automation/getting_started/first_campaign.rst:32
msgid "Campaign filters"
msgstr ""
#: ../../content/applications/marketing/marketing_automation/getting_started/first_campaign.rst:34
msgid "To add a filter to the target audience, click :guilabel:`Add Filter`, and a node field will appear. In the node field, a custom equation can be configured for Odoo to use when filtering who to include (and exclude) in this specific marketing campaign."
msgstr ""
#: ../../content/applications/marketing/marketing_automation/getting_started/first_campaign.rst:None
msgid "A filter node in Odoo Marketing Automation."
msgstr ""
#: ../../content/applications/marketing/marketing_automation/getting_started/first_campaign.rst:42
msgid "When the first field of the node is clicked, a nested drop-down menu of options appears on the screen where specific criteria is chosen based on needs of the campaign. The remaining fields on the node further define the criteria which determines which records to include (or exclude) in the execution of the campaign."
msgstr ""
#: ../../content/applications/marketing/marketing_automation/getting_started/first_campaign.rst:47
msgid "To add another node, simply click the :guilabel:`+ (plus sign)` icon to the right of the filtering rule. To add a branch of multiple nodes at the same time, click the :guilabel:`... (ellipses)` icon."
msgstr ""
#: ../../content/applications/marketing/marketing_automation/getting_started/first_campaign.rst:51
msgid "For further information on filters, refer to :doc:`this documentation page <target_audience>`."
msgstr ""
#: ../../content/applications/marketing/marketing_automation/getting_started/first_campaign.rst:54
msgid ":guilabel:`Records` represent the number of contacts in the system that fit the specified criteria for a campaign."
msgstr ""
#: ../../content/applications/marketing/marketing_automation/getting_started/first_campaign.rst:58
msgid ":doc:`testing_running`"
msgstr ""
#: ../../content/applications/marketing/marketing_automation/getting_started/first_campaign.rst:59
msgid ":doc:`workflow_activities`"
msgstr ""
#: ../../content/applications/marketing/marketing_automation/getting_started/target_audience.rst:3
msgid "Target an audience"
msgstr ""
#: ../../content/applications/marketing/marketing_automation/getting_started/target_audience.rst:5
msgid "Delivering marketing campaigns to the *right* audience is paramount when trying to grow a business. The :guilabel:`Odoo Marketing Automation` application helps marketers to do just that by providing filtering tools, that can be as simple or as complex as necessary, to reach the right customers at the right time."
msgstr ""
#: ../../content/applications/marketing/marketing_automation/getting_started/target_audience.rst:11
msgid "Work with target filters"
msgstr ""
#: ../../content/applications/marketing/marketing_automation/getting_started/target_audience.rst:13
msgid "When configuring the filters on a marketing campaign, there are some options that have an arrow icon beside them. The arrow signifies that the filter has more refined parameters within it."
msgstr ""
#: ../../content/applications/marketing/marketing_automation/getting_started/target_audience.rst:None
#: ../../content/applications/marketing/marketing_automation/getting_started/target_audience.rst:None
msgid "The drop-down filter menu in the Marketing Automation application."
msgstr ""
#: ../../content/applications/marketing/marketing_automation/getting_started/target_audience.rst:20
msgid "Filters can be extended by adding *branches* and *nodes*. A *node* adds another filtering parameter to a group of targeting conditions (e.g. a new line), and a *branch* creates a narrowly refined cluster of parameters, allowing filters to be grouped with *Any* or *All* statements."
msgstr ""
#: ../../content/applications/marketing/marketing_automation/getting_started/target_audience.rst:24
msgid "Every time a new branch is created, there are two options:"
msgstr ""
#: ../../content/applications/marketing/marketing_automation/getting_started/target_audience.rst:26
msgid "Either the records can match :guilabel:`ALL` criteria for the upcoming rules (an AND statement where all criteria must match)."
msgstr ""
#: ../../content/applications/marketing/marketing_automation/getting_started/target_audience.rst:29
msgid "Or, the records can match :guilabel:`ANY` criteria for the upcoming rules (an OR statement where only one of the criteria must match)."
msgstr ""
#: ../../content/applications/marketing/marketing_automation/getting_started/target_audience.rst:32
msgid "To change between these two options, simply click the drop-down arrow icon in the green box and select :guilabel:`Any` or :guilabel:`All`."
msgstr ""
#: ../../content/applications/marketing/marketing_automation/getting_started/target_audience.rst:35
msgid "To add a node, click on the :guilabel:`+ (plus sign icon)` and to add another branch click on the :guilabel:`... (ellipses icon)`. To exclude a :guilabel:`node` (or a :guilabel:`branch`), click on :guilabel:`x (delete)`."
msgstr ""
#: ../../content/applications/marketing/marketing_automation/getting_started/target_audience.rst:44
msgid "Use cases"
msgstr ""
#: ../../content/applications/marketing/marketing_automation/getting_started/target_audience.rst:46
msgid "The following scenarios below outline different combinations of filters a marketing campaign might commonly use."
msgstr ""
#: ../../content/applications/marketing/marketing_automation/getting_started/target_audience.rst:50
msgid "Scenario #1: Narrow the target down to new opportunities in the pipeline"
msgstr ""
#: ../../content/applications/marketing/marketing_automation/getting_started/target_audience.rst:52
msgid "While in Edit mode on a campaign template form, select the :guilabel:`Target` field, and click :guilabel:`Search More` from the drop-down menu. Then, search for :guilabel:`Lead/Opportunity` and select it."
msgstr ""
#: ../../content/applications/marketing/marketing_automation/getting_started/target_audience.rst:56
msgid "Next, click :guilabel:`Add Filter` in the :guilabel:`Filter` field. Click on the default :guilabel:`ID` filter option in the first portion of the filter equation. Doing so reveals a drop-down menu full of filter options. From this drop-down, scroll down (or search for) :guilabel:`Type`."
msgstr ""
#: ../../content/applications/marketing/marketing_automation/getting_started/target_audience.rst:61
msgid "Keep the second portion of the filter equation on the default :guilabel:`= (equal sign)`."
msgstr ""
#: ../../content/applications/marketing/marketing_automation/getting_started/target_audience.rst:63
msgid "Then, change the third (and final) portion of the filter equation from :guilabel:`Lead` to :guilabel:`Opportunity`. The number of :guilabel:`Records` that fit this specific filter equation will change as the equation is customized."
msgstr ""
#: ../../content/applications/marketing/marketing_automation/getting_started/target_audience.rst:67
#: ../../content/applications/marketing/marketing_automation/getting_started/target_audience.rst:103
msgid "Add another node to this filter by clicking the :guilabel:`+ (plus sign)` to the right of the equation."
msgstr ""
#: ../../content/applications/marketing/marketing_automation/getting_started/target_audience.rst:70
msgid "With \"new\" opportunities being the target of this filter, the second node will focus on only locating opportunities that are in the :guilabel:`New` stage of the pipeline. To do that, select the default :guilabel:`ID` from the first portion of the second filter equation, and scroll down (or search for) :guilabel:`Stage` from the field drop-down menu."
msgstr ""
#: ../../content/applications/marketing/marketing_automation/getting_started/target_audience.rst:75
msgid "Once again, leave the second portion of the filter equation on :guilabel:`= (equal sign)`."
msgstr ""
#: ../../content/applications/marketing/marketing_automation/getting_started/target_audience.rst:77
msgid "Lastly, highlight the default value in the third (and final) portion of the second filter equation and type in :guilabel:`New`. With that completed, Odoo will only target opportunities that are in the \"New\" stage of the pipeline."
msgstr ""
#: ../../content/applications/marketing/marketing_automation/getting_started/target_audience.rst:None
msgid "A standard scenario using filters in the Odoo Marketing Automation app."
msgstr ""
#: ../../content/applications/marketing/marketing_automation/getting_started/target_audience.rst:86
msgid "Scenario #2: Narrow the target down to the event attendees that purchased a specific ticket"
msgstr ""
#: ../../content/applications/marketing/marketing_automation/getting_started/target_audience.rst:88
msgid "While in Edit mode on a campaign template form, select the :guilabel:`Target` field, and click :guilabel:`Search More` from the drop-down menu. Then, scroll down (or search for) :guilabel:`Event` and select it."
msgstr ""
#: ../../content/applications/marketing/marketing_automation/getting_started/target_audience.rst:92
msgid "Next, click :guilabel:`Add Filter` in the :guilabel:`Filter` field. Click on the default :guilabel:`ID` filter option in the first portion of the filter equation. Doing so reveals a drop-down menu full of filter options. From this drop-down, scroll down (or search for) :guilabel:`Event`."
msgstr ""
#: ../../content/applications/marketing/marketing_automation/getting_started/target_audience.rst:97
msgid "Click the the default :guilabel:`= (equal sign)` in the second portion of the filter equation. This reveals a drop-down menu. On this menu, select :guilabel:`contains`."
msgstr ""
#: ../../content/applications/marketing/marketing_automation/getting_started/target_audience.rst:100
msgid "In the third (and final) empty portion of the filter equation, type in the name of the event(s) that you would like Odoo to consider for this campaign filter."
msgstr ""
#: ../../content/applications/marketing/marketing_automation/getting_started/target_audience.rst:106
msgid "The second node will focus on targeting this campaign to attendees who purchase a specific type of ticket to the aforementioned event(s) in the first filter equation. To do that, select the default :guilabel:`ID` from the first portion of the second filter equation, and scroll down (or search for) :guilabel:`Event Ticket` from the field drop-down menu. Then, in that same drop-down menu, select :guilabel:`Name`."
msgstr ""
#: ../../content/applications/marketing/marketing_automation/getting_started/target_audience.rst:112
msgid "Once again, click the the default :guilabel:`= (equal sign)` in the second portion of the filter equation, and select :guilabel:`contains`."
msgstr ""
#: ../../content/applications/marketing/marketing_automation/getting_started/target_audience.rst:115
msgid "Lastly, in the third (and final) portion of the second filter equation, which will be blank, type in the name of the ticket type that should be used for the filter. In this case, :guilabel:`Standard` is the name of the event ticket type for this sample filter."
msgstr ""
#: ../../content/applications/marketing/marketing_automation/getting_started/target_audience.rst:None
msgid "An event ticket filter in the Odoo Marketing Automation application."
msgstr ""
#: ../../content/applications/marketing/marketing_automation/getting_started/testing_running.rst:3
msgid "Testing and running a campaign"
msgstr ""
#: ../../content/applications/marketing/marketing_automation/getting_started/testing_running.rst:5
msgid "Odoo gives users the ability to test marketing campaigns (and mailings) before officially running them."
msgstr ""
#: ../../content/applications/marketing/marketing_automation/getting_started/testing_running.rst:8
msgid "First, open the :guilabel:`Marketing Automation` application and click on a campaign. Make sure the campaign already has activities configured on it (or build a campaign by following the directions here on :doc:`this documentation <workflow_activities>`). To start a test, click the :guilabel:`Launch a Test` button at the top of the template form."
msgstr ""
#: ../../content/applications/marketing/marketing_automation/getting_started/testing_running.rst:None
msgid "Launch a test button in Odoo Marketing Automation."
msgstr ""
#: ../../content/applications/marketing/marketing_automation/getting_started/testing_running.rst:17
msgid "When clicked, a pop-up window appears. In the dropdown field choose a specific record to run the test on, or create a brand new record by clicking the :guilabel:`Search More...` link at the bottom of the dropdown menu, and then click the :guilabel:`Create` button."
msgstr ""
#: ../../content/applications/marketing/marketing_automation/getting_started/testing_running.rst:21
msgid "Once the record is selected, click :guilabel:`Continue`, and Odoo will redirect to the campaign test page."
msgstr ""
#: ../../content/applications/marketing/marketing_automation/getting_started/testing_running.rst:None
msgid "Test screen in Odoo Marketing Automation."
msgstr ""
#: ../../content/applications/marketing/marketing_automation/getting_started/testing_running.rst:28
msgid "Here, the name of the :guilabel:`Record` being tested is visible, along with the precise time this test workflow was started. Beneath that is the first activity (or activities) in the workflow."
msgstr ""
#: ../../content/applications/marketing/marketing_automation/getting_started/testing_running.rst:31
msgid "To start a test, click the :guilabel:`Run` icon beside the first activity in the workflow. When clicked, the page will reload, and Odoo will show the various results (and analytics) connected to that specific activity."
msgstr ""
#: ../../content/applications/marketing/marketing_automation/getting_started/testing_running.rst:None
msgid "Workflow test progress in Odoo Marketing Automation."
msgstr ""
#: ../../content/applications/marketing/marketing_automation/getting_started/testing_running.rst:39
msgid "Once all the workflow activities are completed, the test will end and be moved to the :guilabel:`Completed` stage. To stop a test before all the workflow activities are completed, click the :guilabel:`Stop` button."
msgstr ""
#: ../../content/applications/marketing/marketing_automation/getting_started/workflow_activities.rst:3
msgid "Marketing activities"
msgstr ""
#: ../../content/applications/marketing/marketing_automation/getting_started/workflow_activities.rst:5
msgid "When creating a campaign in the :guilabel:`Marketing Automation` app, users can plan marketing activities such as email or SMS campaigns. To get started, navigate to the :guilabel:`Workflow` area, and click :guilabel:`Add New Activity`. A blank activity template will appear where parameters can be set for that specific activity."
msgstr ""
#: ../../content/applications/marketing/marketing_automation/getting_started/workflow_activities.rst:10
msgid "When :guilabel:`Add New Activity` is selected, a blank activity template will appear with the following customizable fields:"
msgstr ""
#: ../../content/applications/marketing/marketing_automation/getting_started/workflow_activities.rst:None
msgid "An activity template in Odoo Marketing Automation."
msgstr ""
#: ../../content/applications/marketing/marketing_automation/getting_started/workflow_activities.rst:17
msgid ":guilabel:`Activity Name`: the title of the activity."
msgstr ""
#: ../../content/applications/marketing/marketing_automation/getting_started/workflow_activities.rst:18
msgid ":guilabel:`Activity Type`: choose between Email, Server Action (internal Odoo operation), or SMS."
msgstr ""
#: ../../content/applications/marketing/marketing_automation/getting_started/workflow_activities.rst:19
msgid ":guilabel:`Mail Template`: choose from pre-configured templates (or create a new one on-the-fly)."
msgstr ""
#: ../../content/applications/marketing/marketing_automation/getting_started/workflow_activities.rst:20
msgid ":guilabel:`Trigger`: choose when this activity should be triggered."
msgstr ""
#: ../../content/applications/marketing/marketing_automation/getting_started/workflow_activities.rst:21
msgid ":guilabel:`Expiry Duration`: configure to stop the actions after a specific amount of time (after the scheduled date). When selected, a :guilabel:`Cancel after` field appears, in which the user can choose how many :guilabel:`Hours, Days, Weeks, or Months` they want the actions to cease after the initial date."
msgstr ""
#: ../../content/applications/marketing/marketing_automation/getting_started/workflow_activities.rst:25
msgid ":guilabel:`Activity Filter`: domain related to this activity (and all subsequent Child Activities)."
msgstr ""
#: ../../content/applications/marketing/marketing_automation/getting_started/workflow_activities.rst:27
msgid ":guilabel:`Applied Filter`: activity will *only* be performed if it satisfies the specified domain (filter)."
msgstr ""
#: ../../content/applications/marketing/marketing_automation/getting_started/workflow_activities.rst:30
msgid "After the activity's settings are fully configured, click :guilabel:`Save & Close` to finish creating the activity."
msgstr ""
#: ../../content/applications/marketing/marketing_automation/getting_started/workflow_activities.rst:34
msgid "Workflow activity"
msgstr ""
#: ../../content/applications/marketing/marketing_automation/getting_started/workflow_activities.rst:36
msgid "Once saved, the :guilabel:`Workflow Activity` will appear in Odoo, where each activity will be shown as a graph by default. The configured trigger time for that activity can be found to the left of the :guilabel:`Workflow Activity` card."
msgstr ""
#: ../../content/applications/marketing/marketing_automation/getting_started/workflow_activities.rst:40
msgid "In the :guilabel:`Workflow Activity` section, there is also the number of activities that are successful or rejected. The :guilabel:`Success` and :guilabel:`Rejected` numbers are color-coded in the graph for easy reference (in green and red, respectively)."
msgstr ""
#: ../../content/applications/marketing/marketing_automation/getting_started/workflow_activities.rst:None
msgid "Typical workflow activity in Odoo Marketing Automation."
msgstr ""
#: ../../content/applications/marketing/marketing_automation/getting_started/workflow_activities.rst:49
msgid "If the :guilabel:`Activity Type` of the activity is set to :guilabel:`Email`, there are more in-depth analytics beneath the :guilabel:`Workflow Activity` data detailing how many emails have been :guilabel:`Sent`, and what percentage of those have been :guilabel:`Clicked`, :guilabel:`Replied` to, or :guilabel:`Bounced`."
msgstr ""
#: ../../content/applications/marketing/marketing_automation/getting_started/workflow_activities.rst:55
msgid "Child activities"
msgstr ""
#: ../../content/applications/marketing/marketing_automation/getting_started/workflow_activities.rst:57
msgid "Odoo also has the option to :guilabel:`Add Child Activity`. *Child Activities* are sub-activities that are connected to (and triggered by) the activity above it, which is also known as its *Parent Activity*."
msgstr ""
#: ../../content/applications/marketing/marketing_automation/getting_started/workflow_activities.rst:61
msgid "Odoo provides a number of triggering options to launch a :guilabel:`Child Activity` - all of which depend on the trigger configurations related to the parent activity. Under the desired parent activity, hover over :guilabel:`Add child activity`, and select the trigger:"
msgstr ""
#: ../../content/applications/marketing/marketing_automation/getting_started/workflow_activities.rst:65
msgid ":guilabel:`Add Another Activity`: instantly add another activity."
msgstr ""
#: ../../content/applications/marketing/marketing_automation/getting_started/workflow_activities.rst:66
msgid ":guilabel:`Opened`: the next activity will be triggered if the (email) recipient opens the mailing."
msgstr ""
#: ../../content/applications/marketing/marketing_automation/getting_started/workflow_activities.rst:68
msgid ":guilabel:`Not Opened`: the next activity will be triggered if the recipient does not open the mailing."
msgstr ""
#: ../../content/applications/marketing/marketing_automation/getting_started/workflow_activities.rst:70
msgid ":guilabel:`Replied`: the next activity will be triggered if the recipient replies to the mailing."
msgstr ""
#: ../../content/applications/marketing/marketing_automation/getting_started/workflow_activities.rst:71
msgid ":guilabel:`Not Replied`: the next activity will be triggered if the recipient does not reply to the mailing."
msgstr ""
#: ../../content/applications/marketing/marketing_automation/getting_started/workflow_activities.rst:73
msgid ":guilabel:`Clicked`: the next activity will be triggered if the recipient clicks on a link included in the mailing."
msgstr ""
#: ../../content/applications/marketing/marketing_automation/getting_started/workflow_activities.rst:75
msgid ":guilabel:`Not Clicked`: the next activity will be triggered if the recipient does not click on a link included in the mailing."
msgstr ""
#: ../../content/applications/marketing/marketing_automation/getting_started/workflow_activities.rst:77
msgid ":guilabel:`Bounced`: the next activity will be triggered if the mailing is bounced (not sent)."
msgstr ""
#: ../../content/applications/marketing/marketing_automation/getting_started/workflow_activities.rst:79
msgid "Once a trigger is selected, the user can configure the child activity (it has the same configuration options as a regular activity) and click :guilabel:`Save & Close`` to finish creating the child activity."
msgstr ""
#: ../../content/applications/marketing/sms_marketing.rst:8

View File

@ -8,7 +8,7 @@ msgid ""
msgstr ""
"Project-Id-Version: Odoo 16.0\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2022-11-17 09:28+0000\n"
"POT-Creation-Date: 2022-12-23 09:13+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"
@ -470,7 +470,6 @@ msgid "Internet of Things (IoT)"
msgstr ""
#: ../../content/applications/productivity/iot/config.rst:5
#: ../../content/applications/productivity/mail_plugins/gmail.rst:6
#: ../../content/applications/productivity/mail_plugins/outlook.rst:6
msgid "Configuration"
msgstr ""
@ -1285,120 +1284,146 @@ msgstr ""
msgid "Gmail Plugin"
msgstr ""
#: ../../content/applications/productivity/mail_plugins/gmail.rst:8
msgid "The Gmail :doc:`Mail Plugin <../mail_plugins>` needs to be configured both on Odoo and Gmail."
#: ../../content/applications/productivity/mail_plugins/gmail.rst:5
msgid "The *Gmail Plugin* integrates an Odoo database with a Gmail inbox, so users can keep track of all their work between Gmail and Odoo, without losing any information."
msgstr ""
#: ../../content/applications/productivity/mail_plugins/gmail.rst:13
#: ../../content/applications/productivity/mail_plugins/outlook.rst:13
msgid "Enable Mail Plugin"
#: ../../content/applications/productivity/mail_plugins/gmail.rst:9
msgid "Odoo Online users"
msgstr ""
#: ../../content/applications/productivity/mail_plugins/gmail.rst:11
msgid "For databases hosted on Odoo Online (or Odoo.sh), follow the steps below to configure the Gmail Plugin."
msgstr ""
#: ../../content/applications/productivity/mail_plugins/gmail.rst:15
#: ../../content/applications/productivity/mail_plugins/outlook.rst:15
msgid "First, you need to enable the *Mail Plugin* feature in your database. Go to :menuselection:`Settings --> General Settings --> Integrations`, enable *Mail Plugin*, and *Save* the configuration."
msgstr ""
#: ../../content/applications/productivity/mail_plugins/gmail.rst:21
#: ../../content/applications/productivity/mail_plugins/gmail.rst:94
msgid "Install the Gmail Plugin"
msgstr ""
#: ../../content/applications/productivity/mail_plugins/gmail.rst:23
msgid "Open the `Gmail Plugin Apps Script project <https://script.google.com/d/1n7cxtaR4fGXKcP0RwinNQmL8S4FhVqpo-ZZ_cUAhYuuDpZAP_CnHE_7q/edit>`_."
#: ../../content/applications/productivity/mail_plugins/gmail.rst:17
msgid "First, log in to the Gmail account that the user wishes to connect to Odoo."
msgstr ""
#: ../../content/applications/productivity/mail_plugins/gmail.rst:19
msgid "From the Gmail inbox, click the plus sign icon on the right side panel to get add-ons. If the side panel is not visible, click on the arrow icon at the bottom right corner of the inbox to reveal it."
msgstr ""
#: ../../content/applications/productivity/mail_plugins/gmail.rst:None
msgid "Plus sign icon on the Gmail inbox side panel."
msgstr ""
#: ../../content/applications/productivity/mail_plugins/gmail.rst:26
msgid "Verify you are logged in using the Google account you want to install the plugin on."
msgid "Then, use the search bar to search for `Odoo` and locate the :guilabel:`Odoo Inbox Addin`."
msgstr ""
#: ../../content/applications/productivity/mail_plugins/gmail.rst:28
msgid "Click on *Publish* then *Deploy from manifest...*"
#: ../../content/applications/productivity/mail_plugins/gmail.rst:None
msgid "Odoo Inbox Addin on Google Workspace Marketplace."
msgstr ""
#: ../../content/applications/productivity/mail_plugins/gmail.rst:0
msgid "Deploying from manifest the Gmail Plugin from the Apps Script project"
#: ../../content/applications/productivity/mail_plugins/gmail.rst:32
msgid "Or, go directly to the :guilabel:`Odoo Inbox Addin` page on the `Google Workspace Marketplace <https://workspace.google.com/marketplace/app/odoo_inbox_addin/873497133275>`_."
msgstr ""
#: ../../content/applications/productivity/mail_plugins/gmail.rst:35
msgid "Make sure you are using the legacy editor; otherwise the *Deploy from manifest* functionality may not be available."
msgid "Once the plugin is located, click :guilabel:`Install`. Then, click :guilabel:`Continue` to start the installation."
msgstr ""
#: ../../content/applications/productivity/mail_plugins/gmail.rst:0
msgid "Using the legacy editor in the Gmail Plugin Apps Script project"
#: ../../content/applications/productivity/mail_plugins/gmail.rst:38
msgid "Next, select which Gmail account the user wishes to connect to Odoo. Then click :guilabel:`Allow` to let Odoo access the Google account. Google will then show a pop-up window confirming that the installation was successful."
msgstr ""
#: ../../content/applications/productivity/mail_plugins/gmail.rst:42
msgid "Click on *Install add-on*. A \"Deployment installed\" notification should appear. You can then click on *Close*."
#: ../../content/applications/productivity/mail_plugins/gmail.rst:43
#: ../../content/applications/productivity/mail_plugins/gmail.rst:131
msgid "Configure the Odoo database"
msgstr ""
#: ../../content/applications/productivity/mail_plugins/gmail.rst:0
msgid "Installing the Gmail Plugin from the Apps Script project"
#: ../../content/applications/productivity/mail_plugins/gmail.rst:45
#: ../../content/applications/productivity/mail_plugins/gmail.rst:133
msgid "The :guilabel:`Mail Plugin` feature must be enabled in the Odoo database in order to use the Gmail Plugin. To enable the feature, go to :menuselection:`Settings --> General Settings`. Under the :guilabel:`Integrations` section, activate :guilabel:`Mail Plugin`, and then click :guilabel:`Save`."
msgstr ""
#: ../../content/applications/productivity/mail_plugins/gmail.rst:52
msgid "Configure your Gmail mailbox"
#: ../../content/applications/productivity/mail_plugins/gmail.rst:None
#: ../../content/applications/productivity/mail_plugins/gmail.rst:None
msgid "The Mail Plugin feature in the Settings."
msgstr ""
#: ../../content/applications/productivity/mail_plugins/gmail.rst:54
msgid "Open any email in your Gmail mailbox. On the right-side panel, click on the Odoo icon and then *Authorize Access*."
#: ../../content/applications/productivity/mail_plugins/gmail.rst:55
#: ../../content/applications/productivity/mail_plugins/gmail.rst:143
msgid "Configure the Gmail inbox"
msgstr ""
#: ../../content/applications/productivity/mail_plugins/gmail.rst:0
msgid "Authorizing access to the Gmail Plugin"
#: ../../content/applications/productivity/mail_plugins/gmail.rst:57
#: ../../content/applications/productivity/mail_plugins/gmail.rst:145
msgid "In the Gmail inbox, a purple Odoo icon is now visible on the right side panel. Click on the Odoo icon to open up the Odoo plugin window. Then, click on any email in the inbox. Click :guilabel:`Authorize Access` in the plugin window to grant Odoo access to the Gmail inbox."
msgstr ""
#: ../../content/applications/productivity/mail_plugins/gmail.rst:61
msgid "Choose the right Google account."
#: ../../content/applications/productivity/mail_plugins/gmail.rst:None
#: ../../content/applications/productivity/mail_plugins/gmail.rst:None
msgid "The Authorize Access button in the right sidebar of the Odoo plugin panel."
msgstr ""
#: ../../content/applications/productivity/mail_plugins/gmail.rst:0
msgid "Choosing your Google account"
#: ../../content/applications/productivity/mail_plugins/gmail.rst:65
#: ../../content/applications/productivity/mail_plugins/gmail.rst:153
msgid "Next, click :guilabel:`Login`. Then, enter the URL of the Odoo database that the user wishes to connect to the Gmail inbox, and log in to the database."
msgstr ""
#: ../../content/applications/productivity/mail_plugins/gmail.rst:67
msgid "Allow the Gmail Plugin to access some of your data."
msgstr ""
#: ../../content/applications/productivity/mail_plugins/gmail.rst:0
msgid "Allowing the Gmail Plugin to access Google data"
#: ../../content/applications/productivity/mail_plugins/gmail.rst:69
#: ../../content/applications/productivity/mail_plugins/gmail.rst:157
msgid "Use the general URL for the database, not the URL of a specific page in the database. For example, use `https://mycompany.odoo.com`, not `https://mycompany.odoo.com/web#cids=1&action=menu`."
msgstr ""
#: ../../content/applications/productivity/mail_plugins/gmail.rst:73
#: ../../content/applications/productivity/mail_plugins/outlook.rst:68
msgid "The right-side panel can now display **Company Insights**. At the bottom, click on *Login*."
#: ../../content/applications/productivity/mail_plugins/gmail.rst:161
msgid "Finally, click :guilabel:`Allow` to let Gmail access the Odoo database. The browser will then show a :guilabel:`Success!` message. After that, close the window. The Gmail inbox and Odoo database are now connected."
msgstr ""
#: ../../content/applications/productivity/mail_plugins/gmail.rst:0
#: ../../content/applications/productivity/mail_plugins/outlook.rst:0
msgid "Logging in your Odoo database"
#: ../../content/applications/productivity/mail_plugins/gmail.rst:78
msgid "Odoo On-Premise users"
msgstr ""
#: ../../content/applications/productivity/mail_plugins/gmail.rst:80
#: ../../content/applications/productivity/mail_plugins/outlook.rst:75
msgid "Only a limited amount of *Company Insights* (*Lead Enrichment*) requests are available as a trial. This feature requires :ref:`prepaid credits <mail_plugins/pricing>`."
msgid "For databases hosted on servers other than Odoo Online (or Odoo.sh), follow the steps below to configure the Gmail Plugin."
msgstr ""
#: ../../content/applications/productivity/mail_plugins/gmail.rst:83
#: ../../content/applications/productivity/mail_plugins/outlook.rst:93
msgid "Enter your Odoo database URL and click on *Login*."
msgstr ""
#: ../../content/applications/productivity/mail_plugins/gmail.rst:0
#: ../../content/applications/productivity/mail_plugins/outlook.rst:0
msgid "Entering your Odoo database URL"
#: ../../content/applications/productivity/mail_plugins/gmail.rst:84
msgid "As part of their security guidelines, Google requires add-on creators to provide a list of URLs that can be used in actions and redirections launched by the add-on. This protects users by ensuring, for example, that no add-on redirects users toward a malicious website. (Read more on `Google Apps Script <https://developers.google.com/apps-script/manifest/allowlist-url>`_.)"
msgstr ""
#: ../../content/applications/productivity/mail_plugins/gmail.rst:89
#: ../../content/applications/productivity/mail_plugins/outlook.rst:105
msgid "If you aren't logged into your database, enter your credentials."
msgid "Since Odoo can only list the `odoo.com` domain and not every on-premise customer's unique server domain, on-premise customers cannot install the Gmail Plugin from the Google Workspace Marketplace."
msgstr ""
#: ../../content/applications/productivity/mail_plugins/gmail.rst:91
msgid "Click on *Allow* to let the Gmail Plugin connect to your database."
#: ../../content/applications/productivity/mail_plugins/gmail.rst:96
msgid "First, access the `GitHub repository <https://github.com/odoo/mail-client-extensions>`_ for the Odoo Mail Plugins. Next, click on the green :guilabel:`Code` button. Then, click :guilabel:`Download ZIP` to download the Mail Plugin files onto the user's computer."
msgstr ""
#: ../../content/applications/productivity/mail_plugins/gmail.rst:0
msgid "Allowing the Gmail Plugin to connect to a database"
#: ../../content/applications/productivity/mail_plugins/gmail.rst:None
msgid "Download the ZIP file from the Odoo GitHub repository for Mail Plugins."
msgstr ""
#: ../../content/applications/productivity/mail_plugins/gmail.rst:104
msgid "Open the ZIP file on the computer. Then, go to :menuselection:`mail-client-extensions-master --> gmail --> src --> views`, and open the :file:`login.ts` file using any text editor software, such as Notepad (Windows), TextEdit (Mac), or Visual Studio Code."
msgstr ""
#: ../../content/applications/productivity/mail_plugins/gmail.rst:108
msgid "Delete the following three lines of text from the :file:`login.ts` file:"
msgstr ""
#: ../../content/applications/productivity/mail_plugins/gmail.rst:116
msgid "This removes the `odoo.com` domain constraint from the Gmail Plugin program."
msgstr ""
#: ../../content/applications/productivity/mail_plugins/gmail.rst:118
msgid "Next, in the ZIP file, go to :menuselection:`mail-client-extensions-master --> gmail`, and open the file called :guilabel:`README`. Follow the instructions in the :guilabel:`README` file to push the Gmail Plugin files as a Google Project."
msgstr ""
#: ../../content/applications/productivity/mail_plugins/gmail.rst:123
msgid "The computer must be able to run Linux commands in order to follow the instructions on the :guilabel:`README` file."
msgstr ""
#: ../../content/applications/productivity/mail_plugins/gmail.rst:126
msgid "After that, share the Google Project with the Gmail account that the user wishes to connect to Odoo. Then, click :guilabel:`Publish` and :guilabel:`Deploy from manifest`. Lastly, click :guilabel:`Install the add-on` to install the Gmail Plugin."
msgstr ""
#: ../../content/applications/productivity/mail_plugins/outlook.rst:3
@ -1409,6 +1434,14 @@ msgstr ""
msgid "The Outlook :doc:`Mail Plugin <../mail_plugins>` needs to be configured both on Odoo and Outlook."
msgstr ""
#: ../../content/applications/productivity/mail_plugins/outlook.rst:13
msgid "Enable Mail Plugin"
msgstr ""
#: ../../content/applications/productivity/mail_plugins/outlook.rst:15
msgid "First, you need to enable the *Mail Plugin* feature in your database. Go to :menuselection:`Settings --> General Settings --> Integrations`, enable *Mail Plugin*, and *Save* the configuration."
msgstr ""
#: ../../content/applications/productivity/mail_plugins/outlook.rst:21
msgid "Install the Outlook Plugin"
msgstr ""
@ -1469,6 +1502,18 @@ msgstr ""
msgid "Odoo for Outlook add-in button"
msgstr ""
#: ../../content/applications/productivity/mail_plugins/outlook.rst:68
msgid "The right-side panel can now display **Company Insights**. At the bottom, click on *Login*."
msgstr ""
#: ../../content/applications/productivity/mail_plugins/outlook.rst:0
msgid "Logging in your Odoo database"
msgstr ""
#: ../../content/applications/productivity/mail_plugins/outlook.rst:75
msgid "Only a limited amount of *Company Insights* (*Lead Enrichment*) requests are available as a trial. This feature requires :ref:`prepaid credits <mail_plugins/pricing>`."
msgstr ""
#: ../../content/applications/productivity/mail_plugins/outlook.rst:79
msgid "If, after a short while, the panel is still empty, it is possible that your browser cookie settings prevented it from loading. Note that these settings also change if you are in \"Incognito\" mode on your browser."
msgstr ""
@ -1485,6 +1530,14 @@ msgstr ""
msgid "Once done, the Outlook panel needs to be opened again."
msgstr ""
#: ../../content/applications/productivity/mail_plugins/outlook.rst:93
msgid "Enter your Odoo database URL and click on *Login*."
msgstr ""
#: ../../content/applications/productivity/mail_plugins/outlook.rst:0
msgid "Entering your Odoo database URL"
msgstr ""
#: ../../content/applications/productivity/mail_plugins/outlook.rst:99
msgid "Click on *Allow* to open the pop-up window."
msgstr ""
@ -1493,6 +1546,10 @@ msgstr ""
msgid "New window pop-up warning"
msgstr ""
#: ../../content/applications/productivity/mail_plugins/outlook.rst:105
msgid "If you aren't logged into your database, enter your credentials."
msgstr ""
#: ../../content/applications/productivity/mail_plugins/outlook.rst:107
msgid "Click on *Allow* to let the Outlook Plugin connect to your database."
msgstr ""

View File

@ -8,7 +8,7 @@ msgid ""
msgstr ""
"Project-Id-Version: Odoo 16.0\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2022-11-17 09:28+0000\n"
"POT-Creation-Date: 2022-12-23 09:13+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"
@ -50,17 +50,18 @@ msgid "You can activate this mode from the CRM Settings. It applies to all your
msgstr ""
#: ../../content/applications/sales/crm/acquire_leads/convert.rst:14
#: ../../content/applications/sales/crm/acquire_leads/lead_mining.rst:8
#: ../../content/applications/sales/crm/acquire_leads/lead_mining.rst:10
#: ../../content/applications/sales/crm/optimize/gamification.rst:11
#: ../../content/applications/sales/crm/optimize/partner_autocomplete.rst:9
#: ../../content/applications/sales/crm/performance/google_spreadsheets.rst:10
#: ../../content/applications/sales/crm/track_leads/lead_scoring.rst:12
#: ../../content/applications/sales/crm/track_leads/prospect_visits.rst:12
#: ../../content/applications/sales/point_of_sale/advanced_pricing_features/loyalty.rst:9
#: ../../content/applications/sales/point_of_sale/overview/getting_started.rst:14
#: ../../content/applications/sales/point_of_sale/overview/getting_started.rst:10
#: ../../content/applications/sales/point_of_sale/payment/adyen.rst:9
#: ../../content/applications/sales/point_of_sale/payment/ingenico.rst:12
#: ../../content/applications/sales/point_of_sale/payment/six.rst:16
#: ../../content/applications/sales/point_of_sale/payment/stripe.rst:12
#: ../../content/applications/sales/point_of_sale/payment/vantiv.rst:13
#: ../../content/applications/sales/point_of_sale/payment/worldline.rst:12
#: ../../content/applications/sales/point_of_sale/restaurant/restaurant.rst:14
@ -258,61 +259,117 @@ msgstr ""
msgid "Lead mining"
msgstr ""
#: ../../content/applications/sales/crm/acquire_leads/lead_mining.rst:4
msgid "In any business, getting quality leads is essential to keep the business growing. Lead mining allows you to generate leads from scratch directly from your database. Target your leads based on a set of criteria such as the country, the size of the company, the industry your leads are coming from to make them relevant to your business."
#: ../../content/applications/sales/crm/acquire_leads/lead_mining.rst:5
msgid "Lead mining is a feature that allows CRM users to generate new leads directly into their Odoo database. To ensure lead qualification, lead mining output is determined by a variety of filtering criteria, such as the country, the company size, and the industry."
msgstr ""
#: ../../content/applications/sales/crm/acquire_leads/lead_mining.rst:10
msgid "For this feature to work, go to :menuselection:`CRM --> Configuration --> Settings` and activate the **Lead Mining** feature."
#: ../../content/applications/sales/crm/acquire_leads/lead_mining.rst:12
msgid "To get started, go to :menuselection:`CRM --> Configuration --> Settings` and activate :guilabel:`Lead Mining`."
msgstr ""
#: ../../content/applications/sales/crm/acquire_leads/lead_mining.rst:17
msgid "Start generating leads"
#: ../../content/applications/sales/crm/acquire_leads/lead_mining.rst:None
msgid "Activate lead mining in Odoo CRM settings."
msgstr ""
#: ../../content/applications/sales/crm/acquire_leads/lead_mining.rst:18
msgid "You will now have a new button **Generate Leads** available in your pipeline. You are also able to create lead mining requests from the :menuselection:`Configuration --> Lead Mining Requests` and through :menuselection:`Leads --> Leads` where you have the **Generate Leads** button."
#: ../../content/applications/sales/crm/acquire_leads/lead_mining.rst:20
msgid "Generate leads"
msgstr ""
#: ../../content/applications/sales/crm/acquire_leads/lead_mining.rst:27
msgid "From there, click on the **Generate Leads** button, a window where you will be able to pick your criteria will pop up."
#: ../../content/applications/sales/crm/acquire_leads/lead_mining.rst:22
msgid "After the :guilabel:`Lead Mining` setting is activated, a new button called :guilabel:`Generate Leads` is available to use in the :guilabel:`CRM` pipeline. Lead mining requests are also available through :menuselection:`CRM --> Configuration --> Lead Mining Requests`, or through :menuselection:`CRM --> Leads --> Leads` where the :guilabel:`Generate Leads` button is also available."
msgstr ""
#: ../../content/applications/sales/crm/acquire_leads/lead_mining.rst:34
msgid "When choosing to target Companies and their contacts you can choose the contacts you are getting based on Role or Seniority. When getting contact information make sure to be aware of the latest EU regulation, get more information about General Data Protection Regulation on `Odoo GDPR <http://odoo.com/gdpr>`__,"
#: ../../content/applications/sales/crm/acquire_leads/lead_mining.rst:None
msgid "The Generate Leads button to use the lead mining feature."
msgstr ""
#: ../../content/applications/sales/crm/acquire_leads/lead_mining.rst:32
msgid "Click on the :guilabel:`Generate Leads` button, and a window will appear offering a variety of criteria by which to generate leads."
msgstr ""
#: ../../content/applications/sales/crm/acquire_leads/lead_mining.rst:None
msgid "The pop-up window with the selection criteria in order to generate leads in Odoo."
msgstr ""
#: ../../content/applications/sales/crm/acquire_leads/lead_mining.rst:39
msgid "You can decide to filter the leads you are getting depending on the size (number of employees) of the companies. You can pick the countries your leads are coming from. It is possible to pick multiple countries. You can pick the industries your leads are coming from. It is possible to pick multiple industries."
msgid "Choose to generate leads for :guilabel:`Companies` to get company information only, or choose :guilabel:`Companies and their Contacts` to get company information as well as individual employee contact information. When targeting :guilabel:`Companies and their Contacts`, there is an option to filter contacts based on :guilabel:`Role` or :guilabel:`Seniority`."
msgstr ""
#: ../../content/applications/sales/crm/acquire_leads/lead_mining.rst:43
msgid "You can choose the salesperson and the Salesteam the lead will be assigned to. You can also add tags to track your generated leads."
#: ../../content/applications/sales/crm/acquire_leads/lead_mining.rst:44
msgid "Additional filtering options include:"
msgstr ""
#: ../../content/applications/sales/crm/acquire_leads/lead_mining.rst:46
msgid ":guilabel:`Size`: filter leads based on the number of employees at the company"
msgstr ""
#: ../../content/applications/sales/crm/acquire_leads/lead_mining.rst:47
msgid "The generated leads will have the name of the company."
msgid ":guilabel:`Countries`: filter leads based on the country (or countries) they are located in"
msgstr ""
#: ../../content/applications/sales/crm/acquire_leads/lead_mining.rst:48
msgid ":guilabel:`States`: further filter leads based on the state they are located in, if applicable"
msgstr ""
#: ../../content/applications/sales/crm/acquire_leads/lead_mining.rst:49
msgid ":guilabel:`Industries`: filter leads based on the specific industry they work in"
msgstr ""
#: ../../content/applications/sales/crm/acquire_leads/lead_mining.rst:50
msgid ":guilabel:`Sales Team`: choose which Sales Team the leads will be assigned to"
msgstr ""
#: ../../content/applications/sales/crm/acquire_leads/lead_mining.rst:51
msgid ":guilabel:`Salesperson`: choose which person(s) on the Sales Team the leads will be assigned to"
msgstr ""
#: ../../content/applications/sales/crm/acquire_leads/lead_mining.rst:52
msgid ":guilabel:`Default Tags`: choose which tags are applied directly to the leads once found"
msgstr ""
#: ../../content/applications/sales/crm/acquire_leads/lead_mining.rst:55
msgid "Make sure to be aware of the latest EU regulations when receiving contact information. Get more information about the General Data Protection Regulation on `Odoo GDPR <http://odoo.com/gdpr>`_."
msgstr ""
#: ../../content/applications/sales/crm/acquire_leads/lead_mining.rst:59
#: ../../content/applications/sales/crm/optimize/partner_autocomplete.rst:36
msgid "Pricing"
msgstr ""
#: ../../content/applications/sales/crm/acquire_leads/lead_mining.rst:51
msgid "This is an In-App Purchase feature, each generated lead will cost you one credit. If you choose to get contact information each contact will also cost you one additional credit. Here is the pricing for this `feature <https://iap.odoo.com/iap/in-app-services/167?>`__, To buy credits you can either go to :menuselection:`CRM --> Configuration --> Settings --> Buy Credits`; or go to :menuselection:`Settings --> Contacts --> Odoo IAP --> View my Services`."
#: ../../content/applications/sales/crm/acquire_leads/lead_mining.rst:61
msgid "Lead mining is an *In-App Purchase* feature and each generated lead costs one credit."
msgstr ""
#: ../../content/applications/sales/crm/acquire_leads/lead_mining.rst:65
msgid "The blue box will automatically tell you how many credits are going to be consumed."
#: ../../content/applications/sales/crm/acquire_leads/lead_mining.rst:63
msgid "Choosing to generate :guilabel:`Companies and their Contacts` costs one additional credit for each contact generated."
msgstr ""
#: ../../content/applications/sales/crm/acquire_leads/lead_mining.rst:68
msgid "If you are on Odoo Online and have the Enterprise version, you benefit from free trial credits to test the feature."
#: ../../content/applications/sales/crm/acquire_leads/lead_mining.rst:67
msgid "See here for full pricing information: `Lead Generation by Odoo IAP <https://iap.odoo.com/iap/ in-app-services/167?>`_."
msgstr ""
#: ../../content/applications/sales/crm/acquire_leads/lead_mining.rst:72
msgid ":doc:`In-App Purchases (IAP) </applications/general/in_app_purchase>`"
#: ../../content/applications/sales/crm/acquire_leads/lead_mining.rst:70
msgid "To buy credits, navigate to :menuselection:`CRM --> Configuration --> Settings`. In the :guilabel:`Lead Generation` section, under the :guilabel:`Lead Mining` feature, click on :guilabel:`Buy Credits`."
msgstr ""
#: ../../content/applications/sales/crm/acquire_leads/lead_mining.rst:None
msgid "Buy credits from the lead mining settings."
msgstr ""
#: ../../content/applications/sales/crm/acquire_leads/lead_mining.rst:78
msgid "Credits may also be purchased by navigating to the :menuselection:`Settings --> General Settings`. In the :guilabel:`In-App Purchases` section, under the :guilabel:`Odoo IAP` feature, click on :guilabel:`View My Services`."
msgstr ""
#: ../../content/applications/sales/crm/acquire_leads/lead_mining.rst:None
msgid "Buy credits in the Odoo IAP settings."
msgstr ""
#: ../../content/applications/sales/crm/acquire_leads/lead_mining.rst:88
msgid "Users of Odoo Online (SaaS) Enterprise automatically have free trial credits in their database to test any IAP features."
msgstr ""
#: ../../content/applications/sales/crm/acquire_leads/lead_mining.rst:92
msgid ":doc:`../../../general/in_app_purchase`"
msgstr ""
#: ../../content/applications/sales/crm/acquire_leads/send_quotes.rst:3
@ -1493,163 +1550,203 @@ msgid "Getting started"
msgstr ""
#: ../../content/applications/sales/point_of_sale/overview/getting_started.rst:5
msgid "When working with a Point of Sale application, employees want a simple, and user-friendly solution. A solution that works online or offline and with any device."
msgid "**Point of Sale** is a fully integrated application that allows you to sell products (online or offline) with any device. It also automatically registers product moves in your stock, gives you real-time statistics, and consolidations across all shops."
msgstr ""
#: ../../content/applications/sales/point_of_sale/overview/getting_started.rst:9
msgid "A Point of Sale system is a fully integrated application that allows any transaction, automatically registers product moves in your stock, and gives you real-time statistics and consolidations across all shops."
#: ../../content/applications/sales/point_of_sale/overview/getting_started.rst:13
msgid "Make products available"
msgstr ""
#: ../../content/applications/sales/point_of_sale/overview/getting_started.rst:17
msgid "Make products available in the PoS"
msgstr ""
#: ../../content/applications/sales/point_of_sale/overview/getting_started.rst:19
msgid "To make products available for sale, go to :menuselection:`Point of Sale --> Products --> Products` and open a product. In the *Point of Sale* tab, enable *Available in Point of Sale*."
#: ../../content/applications/sales/point_of_sale/overview/getting_started.rst:15
msgid "To make products available for sale, go to :menuselection:`Point of Sale --> Products --> Products`, and select a product to open the product form. In the :guilabel:`Sales` tab, enable :guilabel:`Available in POS`."
msgstr ""
#: ../../content/applications/sales/point_of_sale/overview/getting_started.rst:None
msgid "Product form. Making the product available in PoS."
msgid "Making a product available in your POS."
msgstr ""
#: ../../content/applications/sales/point_of_sale/overview/getting_started.rst:28
msgid "You can also define if the product has to be weighted or not."
#: ../../content/applications/sales/point_of_sale/overview/getting_started.rst:24
msgid "Configure payment methods"
msgstr ""
#: ../../content/applications/sales/point_of_sale/overview/getting_started.rst:31
msgid "Configure your payment methods"
#: ../../content/applications/sales/point_of_sale/overview/getting_started.rst:26
msgid "To add a payment method, you first need to create it. Go to :menuselection:`Point of Sale --> Configuration --> Payment Methods --> Create`, and set a name. Check :guilabel:`Identify Customer` to allow this payment method *exclusively* for registered customers."
msgstr ""
#: ../../content/applications/sales/point_of_sale/overview/getting_started.rst:33
msgid "To add a payment method, you first need to create it. Go to :menuselection:`Point of Sale --> Configuration --> Payment Methods` and click on create. Then, you can name your payment method and set it up."
#: ../../content/applications/sales/point_of_sale/overview/getting_started.rst:30
msgid "Then, select the :guilabel:`Journal`. Choose :guilabel:`Cash` to use this payment method for cash payments, or :guilabel:`Bank` to use it for card payments."
msgstr ""
#: ../../content/applications/sales/point_of_sale/overview/getting_started.rst:None
msgid "Creating a new payment method for a Point of Sale."
msgid "Creating a new payment method for a POS."
msgstr ""
#: ../../content/applications/sales/point_of_sale/overview/getting_started.rst:41
msgid "Selecting a :guilabel:`bank` journal automatically adds the :guilabel:`Use a Payment Terminal` field in which you can add your terminal's information."
msgstr ""
#: ../../content/applications/sales/point_of_sale/overview/getting_started.rst:43
msgid "Dont forget your credentials for methods using a payment terminal."
msgid "Credentials are mandatory to use a payment terminal. To learn how to configure the different terminals, check out the following documentation pages:"
msgstr ""
#: ../../content/applications/sales/point_of_sale/overview/getting_started.rst:45
msgid "Now, you can select the payment method in your PoS settings. To do so, go to :menuselection:`Point of Sale --> Configuration --> Point of Sale` and open the PoS in which you want to include the payment method. Then, add the payment method."
#: ../../content/applications/sales/point_of_sale/overview/getting_started.rst:46
msgid ":doc:`Adyen configuration <../payment/adyen>`"
msgstr ""
#: ../../content/applications/sales/point_of_sale/overview/getting_started.rst:None
msgid "Making the payment method available in a point of sale."
#: ../../content/applications/sales/point_of_sale/overview/getting_started.rst:47
msgid ":doc:`Vantiv configuration <../payment/vantiv>`"
msgstr ""
#: ../../content/applications/sales/point_of_sale/overview/getting_started.rst:55
msgid "*Configuration* is the menu where you can edit all your point of sale settings. Some more features are available for restaurants."
#: ../../content/applications/sales/point_of_sale/overview/getting_started.rst:48
msgid ":doc:`Ingenico configuration <../payment/ingenico>`"
msgstr ""
#: ../../content/applications/sales/point_of_sale/overview/getting_started.rst:59
msgid "Your first PoS session"
#: ../../content/applications/sales/point_of_sale/overview/getting_started.rst:49
msgid ":doc:`Six configuration <../payment/six>`"
msgstr ""
#: ../../content/applications/sales/point_of_sale/overview/getting_started.rst:62
msgid "Your first order"
#: ../../content/applications/sales/point_of_sale/overview/getting_started.rst:50
msgid ":doc:`Worldline configuration <../payment/worldline>`"
msgstr ""
#: ../../content/applications/sales/point_of_sale/overview/getting_started.rst:64
msgid "Open a new session from the dashboard by clicking on *New Session*."
#: ../../content/applications/sales/point_of_sale/overview/getting_started.rst:52
msgid "Once the payment method is created, you can select it in your POS settings. To do so, go to :menuselection:`Point of Sale --> Configuration --> Settings`. Select a POS for which you wish to make the payment method available in the :guilabel:`Point of Sale` field, and add the payment method(s) under the :guilabel:`Payment` section."
msgstr ""
#: ../../content/applications/sales/point_of_sale/overview/getting_started.rst:None
msgid "Launching a new session."
#: ../../content/applications/sales/point_of_sale/overview/getting_started.rst:58
msgid "POS sessions"
msgstr ""
#: ../../content/applications/sales/point_of_sale/overview/getting_started.rst:63
msgid "Start a session"
msgstr ""
#: ../../content/applications/sales/point_of_sale/overview/getting_started.rst:65
msgid "From the **POS dashboard**, click :guilabel:`New Session` and at the :guilabel:`Opening Cash Control` screen, click :guilabel:`Open Session` to start a POS session, or click :guilabel:`Continue Selling` if the session is already opened."
msgstr ""
#: ../../content/applications/sales/point_of_sale/overview/getting_started.rst:70
msgid "After the loading screen, you arrive on the PoS interface."
msgid "Multiple users can be connected to the same session at the same time. However, the session can only be opened once on the same browser."
msgstr ""
#: ../../content/applications/sales/point_of_sale/overview/getting_started.rst:73
msgid "Click products to add them to the cart. To change the **quantity**, click :guilabel:`Qty` and enter the number of products using the keypad. To add a **discount** or modify the product **price**, click respectively :guilabel:`% Disc` or :guilabel:`Price` and enter the amounts."
msgstr ""
#: ../../content/applications/sales/point_of_sale/overview/getting_started.rst:77
msgid "Once an order is completed, proceed to checkout by clicking :guilabel:`Payment`. Select the **payment method**, enter the received amount, and click :guilabel:`Validate`. Click :guilabel:`New Order` to move on to the next customer."
msgstr ""
#: ../../content/applications/sales/point_of_sale/overview/getting_started.rst:None
msgid "Point of sale dashboard."
msgid "POS session interface."
msgstr ""
#: ../../content/applications/sales/point_of_sale/overview/getting_started.rst:76
msgid "Once an order is completed, you can register the payment. All the available payment methods appear on the left of the screen. Select the payment method and enter the received amount. Then, you can validate the payment."
msgstr ""
#: ../../content/applications/sales/point_of_sale/overview/getting_started.rst:82
#: ../../content/applications/sales/point_of_sale/overview/getting_started.rst:86
msgid "You can use both `,` and `.` on your keyboard as decimal separators."
msgstr ""
#: ../../content/applications/sales/point_of_sale/overview/getting_started.rst:85
#: ../../content/applications/sales/point_of_sale/overview/getting_started.rst:87
msgid "**Cash** is selected by default if you enter the amount without choosing a payment method."
msgstr ""
#: ../../content/applications/sales/point_of_sale/overview/getting_started.rst:91
msgid "Return and refund products"
msgstr ""
#: ../../content/applications/sales/point_of_sale/overview/getting_started.rst:87
msgid "Having a well-thought-out return policy is key to keep customers satisfied and make the process of accepting returns and refunds easy for you."
#: ../../content/applications/sales/point_of_sale/overview/getting_started.rst:93
msgid "To return and refund a product,"
msgstr ""
#: ../../content/applications/sales/point_of_sale/overview/getting_started.rst:90
msgid "To do that, from the PoS interface, select the product and quantity (with the +/- button) that the customer wants to return. For multiple products, repeat the process individually."
#: ../../content/applications/sales/point_of_sale/overview/getting_started.rst:95
msgid ":ref:`start a session <pos/start-session>` from the **POS dashboard**;"
msgstr ""
#: ../../content/applications/sales/point_of_sale/overview/getting_started.rst:None
msgid "Refunding a product with the point of sale app."
#: ../../content/applications/sales/point_of_sale/overview/getting_started.rst:96
msgid "click :guilabel:`Refund` and select the corresponding order;"
msgstr ""
#: ../../content/applications/sales/point_of_sale/overview/getting_started.rst:97
msgid "When on the payment interface, the total is negative. To end the refund, process the payment and validate it."
msgid "select the product and the quantity to refund using the keypad;"
msgstr ""
#: ../../content/applications/sales/point_of_sale/overview/getting_started.rst:98
msgid "click :guilabel:`Refund` to go back to the previous screen;"
msgstr ""
#: ../../content/applications/sales/point_of_sale/overview/getting_started.rst:99
msgid "once the order is completed, click :guilabel:`Payment` to proceed to the refund;"
msgstr ""
#: ../../content/applications/sales/point_of_sale/overview/getting_started.rst:100
msgid "click :guilabel:`Validate` and :guilabel:`New Order` to move on to the next customer."
msgstr ""
#: ../../content/applications/sales/point_of_sale/overview/getting_started.rst:None
msgid "Giving back money to customer in Odoo Point of Sale."
msgstr ""
#: ../../content/applications/sales/point_of_sale/overview/getting_started.rst:105
msgid "Close the PoS session"
msgid "refund view from a POS"
msgstr ""
#: ../../content/applications/sales/point_of_sale/overview/getting_started.rst:107
msgid "To close your session at the end of the day, click on the close button on the upper right corner of your screen and confirm. Now, close the session on the dashboard view."
msgid "You can filter the **orders list** by :guilabel:`Receipt Number`, :guilabel:`Date` or :guilabel:`Customer` using the search bar."
msgstr ""
#: ../../content/applications/sales/point_of_sale/overview/getting_started.rst:109
msgid "You can also refund a product by selecting the returned product from an open session, and setting a negative quantity that equals the number of returned products. To do so, click :guilabel:`Qty` and :guilabel:`+/-`, followed by the quantity of returned products."
msgstr ""
#: ../../content/applications/sales/point_of_sale/overview/getting_started.rst:114
msgid "Close the POS session"
msgstr ""
#: ../../content/applications/sales/point_of_sale/overview/getting_started.rst:116
msgid "To close your session, click :guilabel:`Close` in the upper right corner of your screen; doing so opens the :guilabel:`Closing Control` pop-up screen. From this screen, you can retrieve various information:"
msgstr ""
#: ../../content/applications/sales/point_of_sale/overview/getting_started.rst:120
msgid "the number of orders made and the total amount made during the session;"
msgstr ""
#: ../../content/applications/sales/point_of_sale/overview/getting_started.rst:121
msgid "the expected amounts grouped by payment method."
msgstr ""
#: ../../content/applications/sales/point_of_sale/overview/getting_started.rst:123
msgid "Before closing this window, count your cash using the calculator icon. Doing so opens a pop-up window that computes the total amount in the cash drawer depending on the coins and bills counted and added manually. Then, click :guilabel:`Confirm` or :guilabel:`Discard` to close the window. The computed amount is set in the :guilabel:`Counted` column, and the :guilabel:`Money Details` are specified in the **Notes** section."
msgstr ""
#: ../../content/applications/sales/point_of_sale/overview/getting_started.rst:None
msgid "How to close a point of sale session."
msgid "How to close a POS session."
msgstr ""
#: ../../content/applications/sales/point_of_sale/overview/getting_started.rst:115
msgid "Its strongly advised to close your PoS session at the end of each day."
msgstr ""
#: ../../content/applications/sales/point_of_sale/overview/getting_started.rst:117
msgid "Once a session is closed, you can see a summary of all transactions per payment method. Then, click on a line to see all orders that were paid during your PoS session. If everything is correct, validate the session and post the closing entries."
msgstr ""
#: ../../content/applications/sales/point_of_sale/overview/getting_started.rst:None
msgid "Point of sale sales report before closing the session."
msgstr ""
#: ../../content/applications/sales/point_of_sale/overview/getting_started.rst:126
msgid "To connect the PoS hardware with an Odoo IoT Box, please refer to these docs: :doc:`Connect an IoT Box to your database </applications/productivity/iot/config/connect>` and :doc:`Use the IoT Box for the PoS </applications/productivity/iot/config/pos>`."
msgstr ""
#: ../../content/applications/sales/point_of_sale/overview/getting_started.rst:132
msgid "View your statistics"
msgstr ""
#: ../../content/applications/sales/point_of_sale/overview/getting_started.rst:134
msgid "Keeping track of your sales is essential to get meaningful statistics. Thats why Odoo provides analyzes about your sales."
#: ../../content/applications/sales/point_of_sale/overview/getting_started.rst:133
msgid "Once you are done controlling the amounts, click :guilabel:`Close Session` to close and go back to the **POS dashboard**."
msgstr ""
#: ../../content/applications/sales/point_of_sale/overview/getting_started.rst:137
msgid "To access your statistics, go to :menuselection:`Point of Sales --> Reporting --> Orders`. There, you can see various statistics in graph or pivot form."
msgid "You can let the session open by clicking :guilabel:`Backend` or abort and keep selling by clicking :guilabel:`Discard`."
msgstr ""
#: ../../content/applications/sales/point_of_sale/overview/getting_started.rst:None
msgid "Orders analysis with pivot view of the point of sale reporting feature."
#: ../../content/applications/sales/point_of_sale/overview/getting_started.rst:139
msgid "Depending on your setup, you might only be allowed to close a session if the expected cash revenue equals the counted cash. To close it anyway, click :guilabel:`Ok` at the :guilabel:`Payments Difference` screen."
msgstr ""
#: ../../content/applications/sales/point_of_sale/overview/getting_started.rst:144
msgid "It is strongly advised to close your POS session at the end of each day."
msgstr ""
#: ../../content/applications/sales/point_of_sale/overview/getting_started.rst:145
msgid "You can also access them through the dashboard."
msgid "To look at all your previous sessions, go to :menuselection:`Point of Sale --> Orders --> Sessions`."
msgstr ""
#: ../../content/applications/sales/point_of_sale/overview/getting_started.rst:None
msgid "Accessing orders analysis via the point of sale dashboard. Reporting feature on the PoS form."
#: ../../content/applications/sales/point_of_sale/overview/getting_started.rst:149
msgid "View statistics"
msgstr ""
#: ../../content/applications/sales/point_of_sale/overview/getting_started.rst:151
msgid "To access your statistics, go to :menuselection:`Point of Sale --> Reporting --> Orders`. Or, from the **POS dashboard**, click the vertical ellipsis (:guilabel:`⋮`) button, :guilabel:`Reporting`, and :guilabel:`Orders`."
msgstr ""
#: ../../content/applications/sales/point_of_sale/overview/getting_started.rst:155
msgid "These statistics are available in a graph or pivot view that you can filter or group depending on your needs."
msgstr ""
#: ../../content/applications/sales/point_of_sale/overview/https.rst:3
@ -1734,6 +1831,7 @@ msgstr ""
#: ../../content/applications/sales/point_of_sale/payment/adyen.rst:19
#: ../../content/applications/sales/point_of_sale/payment/ingenico.rst:36
#: ../../content/applications/sales/point_of_sale/payment/stripe.rst:15
#: ../../content/applications/sales/point_of_sale/payment/worldline.rst:65
msgid "Configure the payment method"
msgstr ""
@ -1783,20 +1881,53 @@ msgid "To find this number, go to your **Adyen account**. Then, go to :menuselec
msgstr ""
#: ../../content/applications/sales/point_of_sale/payment/adyen.rst:59
msgid "Add a new payment method"
msgid "Set the Event URLs"
msgstr ""
#: ../../content/applications/sales/point_of_sale/payment/adyen.rst:61
msgid "To add a new **payment method** to a point of sale, go to :menuselection:`Point of Sale --> Configuration --> Point of Sale`. Then, select the POS and go to :menuselection:`Payments --> Payment Methods`, and add your new method for Adyen."
msgid "For Odoo to know when a payment is made, you must set the terminal **Event URLs**. To do so,"
msgstr ""
#: ../../content/applications/sales/point_of_sale/payment/adyen.rst:63
msgid "log in to `Adyen's website <https://www.adyen.com/>`_;"
msgstr ""
#: ../../content/applications/sales/point_of_sale/payment/adyen.rst:64
msgid "go to :menuselection:`Adyen's dashboard --> Point of Sale --> Terminals` and select the connected terminal;"
msgstr ""
#: ../../content/applications/sales/point_of_sale/payment/adyen.rst:66
msgid "from the terminal settings, click :guilabel:`Integrations`;"
msgstr ""
#: ../../content/applications/sales/point_of_sale/payment/adyen.rst:67
msgid "set the :guilabel:`Switch to decrypted mode to edit this setting` field as :guilabel:`Decrypted`;"
msgstr ""
#: ../../content/applications/sales/point_of_sale/payment/adyen.rst:68
msgid "click the **pencil icon** button and enter your server address, followed by `/pos_adyen/notification` in the :guilabel:`Event URLs` field; and"
msgstr ""
#: ../../content/applications/sales/point_of_sale/payment/adyen.rst:70
msgid "click :guilabel:`Save` at the bottom of the screen to save the changes."
msgstr ""
#: ../../content/applications/sales/point_of_sale/payment/adyen.rst:73
msgid "Add a new payment method"
msgstr ""
#: ../../content/applications/sales/point_of_sale/payment/adyen.rst:75
msgid "To add a new **payment method** to a point of sale, go to :menuselection:`Point of Sale --> Configuration --> Point of Sale`. Then, select the POS and go to :menuselection:`Payments --> Payment Methods`, and add your new method for Adyen."
msgstr ""
#: ../../content/applications/sales/point_of_sale/payment/adyen.rst:80
#: ../../content/applications/sales/point_of_sale/payment/ingenico.rst:53
#: ../../content/applications/sales/point_of_sale/payment/stripe.rst:86
#: ../../content/applications/sales/point_of_sale/payment/worldline.rst:88
msgid "Pay with a payment terminal"
msgstr ""
#: ../../content/applications/sales/point_of_sale/payment/adyen.rst:68
#: ../../content/applications/sales/point_of_sale/payment/adyen.rst:82
msgid "When processing a payment, select :guilabel:`Adyen` as the payment method. Check the amount and click on :guilabel:`Send`. Once the payment is successful, the status changes to :guilabel:`Payment Successful`."
msgstr ""
@ -1805,10 +1936,11 @@ msgid "In case of connexion issues between Odoo and the payment terminal, force
msgstr ""
#: ../../content/applications/sales/point_of_sale/payment/adyen.rst:0
#: ../../content/applications/sales/point_of_sale/payment/stripe.rst:0
msgid "This option is only available after receiving an error message informing you that the connection failed."
msgstr ""
#: ../../content/applications/sales/point_of_sale/payment/adyen.rst:77
#: ../../content/applications/sales/point_of_sale/payment/adyen.rst:91
msgid "To cancel the payment request, click on :guilabel:`cancel`."
msgstr ""
@ -1817,6 +1949,7 @@ msgid "Ingenico"
msgstr ""
#: ../../content/applications/sales/point_of_sale/payment/ingenico.rst:5
#: ../../content/applications/sales/point_of_sale/payment/stripe.rst:5
#: ../../content/applications/sales/point_of_sale/payment/worldline.rst:5
msgid "Connecting a payment terminal allows you to offer a fluid payment flow to your customers and ease the work of your cashiers."
msgstr ""
@ -1936,6 +2069,150 @@ msgstr ""
msgid "If there is any issue with the payment terminal, you can still force the payment using the :guilabel:`Force Done` button. This will allow you to validate the order in Odoo even if there are connection issues between the payment terminal and Odoo."
msgstr ""
#: ../../content/applications/sales/point_of_sale/payment/stripe.rst:3
msgid "Stripe"
msgstr ""
#: ../../content/applications/sales/point_of_sale/payment/stripe.rst:9
msgid ":doc:`Use Stripe as payment provider. <../../../finance/payment_providers/stripe>`"
msgstr ""
#: ../../content/applications/sales/point_of_sale/payment/stripe.rst:17
msgid "Activate **Stripe** in the settings by going to :menuselection:`Point of Sale --> Configuration --> Settings --> Payment Terminals` and enabling :guilabel:`Stripe`."
msgstr ""
#: ../../content/applications/sales/point_of_sale/payment/stripe.rst:20
msgid "Then, create the payment method:"
msgstr ""
#: ../../content/applications/sales/point_of_sale/payment/stripe.rst:22
msgid "Go to :menuselection:`Point of Sale --> Configuration --> Payment Methods`, click :guilabel:`Create`, and complete the :guilabel:`Method` field with your payment method's name;"
msgstr ""
#: ../../content/applications/sales/point_of_sale/payment/stripe.rst:24
msgid "Set the :guilabel:`Journal` field as :guilabel:`Bank` and the :guilabel:`Use a Payment Terminal` field as :guilabel:`Stripe`;"
msgstr ""
#: ../../content/applications/sales/point_of_sale/payment/stripe.rst:26
msgid "Enter your payment terminal serial number in the :guilabel:`Stripe Serial Number` field;"
msgstr ""
#: ../../content/applications/sales/point_of_sale/payment/stripe.rst:27
msgid "Click :guilabel:`Don't forget to complete Stripe connect before using this payment method.`"
msgstr ""
#: ../../content/applications/sales/point_of_sale/payment/stripe.rst:None
msgid "payment method creation form"
msgstr ""
#: ../../content/applications/sales/point_of_sale/payment/stripe.rst:34
msgid "Click :guilabel:`Identify Customer` to allow this payment method **exclusively** for identified customers. For any unidentified customers to be able to pay with Stripe, leave the :guilabel:`Identify Customer` field unchecked."
msgstr ""
#: ../../content/applications/sales/point_of_sale/payment/stripe.rst:37
msgid "The :guilabel:`Outstanding Account` and the :guilabel:`Intermediary Account` can stay empty to use the default accounts."
msgstr ""
#: ../../content/applications/sales/point_of_sale/payment/stripe.rst:39
msgid "Find your payment terminal serial number under the device or on `Stripe's dashboard <https://dashboard.stripe.com>`_."
msgstr ""
#: ../../content/applications/sales/point_of_sale/payment/stripe.rst:43
msgid "Connect Stripe to Odoo"
msgstr ""
#: ../../content/applications/sales/point_of_sale/payment/stripe.rst:45
msgid "Click :guilabel:`Connect Stripe`. Doing so redirects you automatically to a configuration page. Fill in all the information to create your Stripe account and link it with Odoo. Once the forms are completed, the API keys (:guilabel:`Publishable Key` and :guilabel:`Secret Key`) can be retrieved on **Stripe's** website. To do so, click :guilabel:`Get your Secret and Publishable keys`, click the keys to copy them, and paste them into the corresponding fields in Odoo. Your terminal is ready to be configured in a POS."
msgstr ""
#: ../../content/applications/sales/point_of_sale/payment/stripe.rst:None
msgid "stripe connection form"
msgstr ""
#: ../../content/applications/sales/point_of_sale/payment/stripe.rst:57
msgid "When you use **Stripe** exclusively in Point of Sale, you only need the **Secret Key** to use your terminal."
msgstr ""
#: ../../content/applications/sales/point_of_sale/payment/stripe.rst:59
msgid "When you use Stripe as **payment provider**, the :guilabel:`State` can stay set as :guilabel:`Disabled`."
msgstr ""
#: ../../content/applications/sales/point_of_sale/payment/stripe.rst:61
msgid "For databases hosted **On-Premise**, the :guilabel:`Connect Stripe` button does not work. To retrieve the API keys manually, log in to your `Stripe dashboard <https://dashboard.stripe.com>`_, type `API` in the search bar, and click :guilabel:`Developers > API`."
msgstr ""
#: ../../content/applications/sales/point_of_sale/payment/stripe.rst:67
msgid "Configure the payment terminal"
msgstr ""
#: ../../content/applications/sales/point_of_sale/payment/stripe.rst:69
msgid "Swipe right on your payment terminal, click :guilabel:`Settings`, enter the admin PIN code, validate and select your network."
msgstr ""
#: ../../content/applications/sales/point_of_sale/payment/stripe.rst:73
msgid "The device must be connected to a secured WI-FI network."
msgstr ""
#: ../../content/applications/sales/point_of_sale/payment/stripe.rst:74
msgid "Your Odoo database and payment terminal must share the same network."
msgstr ""
#: ../../content/applications/sales/point_of_sale/payment/stripe.rst:75
msgid "You must enter the admin PIN code to access your payment terminal settings. By default, this code is `07139`."
msgstr ""
#: ../../content/applications/sales/point_of_sale/payment/stripe.rst:79
msgid "Link the payment method to a POS"
msgstr ""
#: ../../content/applications/sales/point_of_sale/payment/stripe.rst:81
msgid "To add a **payment method** to your point of sale, go to :menuselection:`Point of Sale --> Configuration --> Settings`. Select the POS, scroll down to the :guilabel:`Payments` section, and add your payment method for **Stripe** in the :guilabel:`Payment Methods` field."
msgstr ""
#: ../../content/applications/sales/point_of_sale/payment/stripe.rst:88
msgid "When processing a payment, select :guilabel:`Stripe` as the payment method. Check the amount and click :guilabel:`Send`. Once the payment is successful, the status changes to :guilabel:`Payment Successful`. To cancel the payment request, click :guilabel:`cancel`."
msgstr ""
#: ../../content/applications/sales/point_of_sale/payment/stripe.rst:0
msgid "In case of connection issues between Odoo and the payment terminal, force the payment by clicking on :guilabel:`Force Done`, which allows you to validate the order."
msgstr ""
#: ../../content/applications/sales/point_of_sale/payment/stripe.rst:97
msgid "The terminal must have at least 10% battery level to use it."
msgstr ""
#: ../../content/applications/sales/point_of_sale/payment/stripe.rst:98
msgid "The device does not work for payments under €0.50."
msgstr ""
#: ../../content/applications/sales/point_of_sale/payment/stripe.rst:101
msgid "Troubleshooting"
msgstr ""
#: ../../content/applications/sales/point_of_sale/payment/stripe.rst:104
msgid "Payment terminal unavailable in your Stripe account"
msgstr ""
#: ../../content/applications/sales/point_of_sale/payment/stripe.rst:106
msgid "If the payment terminal is unavailable in your Stripe account, you must add it manually:"
msgstr ""
#: ../../content/applications/sales/point_of_sale/payment/stripe.rst:108
msgid "Log into your `Stripe's dashboard <https://dashboard.stripe.com>`_ and go to :menuselection:`Stripe dashboard --> Payments --> Readers --> Locations`;"
msgstr ""
#: ../../content/applications/sales/point_of_sale/payment/stripe.rst:110
msgid "Add a location by clicking the :guilabel:`+ New` button or selecting an already created location;"
msgstr ""
#: ../../content/applications/sales/point_of_sale/payment/stripe.rst:111
msgid "Click the :guilabel:`+ New` button in the :guilabel:`Readers` box and fill in the required information."
msgstr ""
#: ../../content/applications/sales/point_of_sale/payment/stripe.rst:115
msgid "You must provide a **registration code**. To retrieve that code, swipe right on your device, enter the admin PIN code (by default: `07319`), validate, and click :guilabel:`Generate a registration code`."
msgstr ""
#: ../../content/applications/sales/point_of_sale/payment/vantiv.rst:3
msgid "Vantiv"
msgstr ""
@ -2470,59 +2747,83 @@ msgid "Odoo Point of Sale only support the *Add a rounding line* rounding strate
msgstr ""
#: ../../content/applications/sales/point_of_sale/shop/invoice.rst:3
msgid "Invoice from the PoS interface"
msgid "Invoice issuance"
msgstr ""
#: ../../content/applications/sales/point_of_sale/shop/invoice.rst:5
msgid "Some of your customers might request an invoice when buying from your Point of Sale, you can easily manage it directly from the PoS interface."
msgid "In Point of Sale, you can issue and print invoices upon payment at the cash register or retrieve all the past invoiced orders."
msgstr ""
#: ../../content/applications/sales/point_of_sale/shop/invoice.rst:9
msgid "Activate invoicing"
msgid "Set a customer"
msgstr ""
#: ../../content/applications/sales/point_of_sale/shop/invoice.rst:11
msgid "Go to :menuselection:`Point of Sale --> Configuration --> Point of Sale` and select your Point of Sale:"
msgid "First, you need to open a session and set your customer. Open the **POS interface** by going to :menuselection:`Point of Sale --> New session --> Open session`. Then, click :guilabel:`Customer` to access the list of **customers**."
msgstr ""
#: ../../content/applications/sales/point_of_sale/shop/invoice.rst:17
msgid "Under the *Bills & Receipts* you will see the invoicing option, tick it. Don't forget to choose in which journal the invoices should be created."
#: ../../content/applications/sales/point_of_sale/shop/invoice.rst:None
msgid "customer selection and creation button"
msgstr ""
#: ../../content/applications/sales/point_of_sale/shop/invoice.rst:19
msgid "From there, you can either set an existing customer by clicking their name or create a new one by clicking :guilabel:`Create`. Doing so opens a customer creation form to fill in with their information. Click :guilabel:`Save` to validate and set this new customer."
msgstr ""
#: ../../content/applications/sales/point_of_sale/shop/invoice.rst:24
msgid "You can also **edit** a customer's information by clicking :guilabel:`Details`."
msgstr ""
#: ../../content/applications/sales/point_of_sale/shop/invoice.rst:25
msgid "Select a customer"
msgid "If you did not set your customer during the order, you can do so at the payment screen by clicking :guilabel:`Customer`."
msgstr ""
#: ../../content/applications/sales/point_of_sale/shop/invoice.rst:27
msgid "From your session interface, use the customer button"
#: ../../content/applications/sales/point_of_sale/shop/invoice.rst:29
msgid "Invoice a customer"
msgstr ""
#: ../../content/applications/sales/point_of_sale/shop/invoice.rst:32
msgid "You can then either select an existing customer and set it as your customer or create a new one by using this button."
#: ../../content/applications/sales/point_of_sale/shop/invoice.rst:31
msgid "Once an order is done, click :guilabel:`Payment` to move to the **payment screen**. Click :guilabel:`Invoice` underneath the customer's name to enable issuing and printing invoices upon payment."
msgstr ""
#: ../../content/applications/sales/point_of_sale/shop/invoice.rst:38
msgid "You will be invited to fill out the customer form with its information."
#: ../../content/applications/sales/point_of_sale/shop/invoice.rst:None
msgid "button to generate an invoice in POS"
msgstr ""
#: ../../content/applications/sales/point_of_sale/shop/invoice.rst:41
msgid "Invoice your customer"
#: ../../content/applications/sales/point_of_sale/shop/invoice.rst:39
msgid "Select the payment method and click :guilabel:`Validate`. The **invoice** is automatically issued and ready to be downloaded and/or printed."
msgstr ""
#: ../../content/applications/sales/point_of_sale/shop/invoice.rst:43
msgid "From the payment screen, you now have an invoice option, use the button to select it and validate."
msgid ":doc:`../overview/getting_started`"
msgstr ""
#: ../../content/applications/sales/point_of_sale/shop/invoice.rst:49
msgid "You can then print the invoice and move on to your next order."
msgstr ""
#: ../../content/applications/sales/point_of_sale/shop/invoice.rst:52
#: ../../content/applications/sales/point_of_sale/shop/invoice.rst:46
msgid "Retrieve invoices"
msgstr ""
#: ../../content/applications/sales/point_of_sale/shop/invoice.rst:54
msgid "Once out of the PoS interface (:menuselection:`Close --> Confirm` on the top right corner) you will find all your orders in :menuselection:`Point of Sale --> Orders --> Orders` and under the status tab you will see which ones have been invoiced. When clicking on a order you can then access the invoice."
#: ../../content/applications/sales/point_of_sale/shop/invoice.rst:48
msgid "To retrieve invoices from the **POS dashboard**,"
msgstr ""
#: ../../content/applications/sales/point_of_sale/shop/invoice.rst:50
msgid "access all orders made through your POS by going to :menuselection:`Point of Sale --> Orders --> Orders`;"
msgstr ""
#: ../../content/applications/sales/point_of_sale/shop/invoice.rst:52
msgid "to access an order's invoice, open the **order form** by selecting the order, then click :guilabel:`Invoice`."
msgstr ""
#: ../../content/applications/sales/point_of_sale/shop/invoice.rst:None
msgid "invoice smart button from an order form"
msgstr ""
#: ../../content/applications/sales/point_of_sale/shop/invoice.rst:60
msgid "**Invoiced orders** can be identified by the :guilabel:`Invoiced` status in the :guilabel:`Status` column;"
msgstr ""
#: ../../content/applications/sales/point_of_sale/shop/invoice.rst:62
msgid "You can filter the list of orders to invoiced orders by clicking :guilabel:`Filters` and :guilabel:`Invoiced`."
msgstr ""
#: ../../content/applications/sales/point_of_sale/shop/multicashiers.rst:3
@ -4570,6 +4871,102 @@ msgstr ""
msgid "Changes to the product template automatically apply to every variant of that product."
msgstr ""
#: ../../content/applications/sales/sales/products_prices/returns.rst:3
msgid "Process returns and refunds"
msgstr ""
#: ../../content/applications/sales/sales/products_prices/returns.rst:5
msgid "The :guilabel:`Sales` app provides two different ways to process returns based on whether an invoice has been sent or not."
msgstr ""
#: ../../content/applications/sales/sales/products_prices/returns.rst:9
msgid "Before invoicing"
msgstr ""
#: ../../content/applications/sales/sales/products_prices/returns.rst:11
msgid "Returns are completed using *Reverse Transfers* when a customer decides to return a product before an invoice has been sent or validated."
msgstr ""
#: ../../content/applications/sales/sales/products_prices/returns.rst:15
msgid "In order to use Reverse Transfers, the :guilabel:`Inventory` app must also be installed."
msgstr ""
#: ../../content/applications/sales/sales/products_prices/returns.rst:17
msgid "To start a return, open the :guilabel:`Sales` app, navigate to the customer's sales order, and click on the :guilabel:`Delivery` smart button to open the associated delivery order."
msgstr ""
#: ../../content/applications/sales/sales/products_prices/returns.rst:20
msgid "On the validated delivery order, click :guilabel:`Return` to open the :guilabel:`Reverse Transfer` pop-up window. By default, the :guilabel:`Quantity` matches the validated quantities from the delivery order. Update the quantities if necessary. Click on the trash icon next to a line item to remove it from the return."
msgstr ""
#: ../../content/applications/sales/sales/products_prices/returns.rst:None
msgid "The \"Reverse Transfer\" pop-up window, to make a return before invoicing the customer."
msgstr ""
#: ../../content/applications/sales/sales/products_prices/returns.rst:29
msgid "Next, click :guilabel:`Return` to confirm the return. This generates a new warehouse operation for the incoming returned product(s). Upon receiving the return, the warehouse team validates the warehouse operation. Then, on the original sales order, the :guilabel:`Delivered` quantity will reflect the difference between the initial validated quantities and the returned quantities."
msgstr ""
#: ../../content/applications/sales/sales/products_prices/returns.rst:None
msgid "The updated \"Delivered\" quantity on the sales order after the reverse transfer."
msgstr ""
#: ../../content/applications/sales/sales/products_prices/returns.rst:38
msgid "When an invoice is created, the customer receives an invoice only for the products they are keeping."
msgstr ""
#: ../../content/applications/sales/sales/products_prices/returns.rst:42
msgid "After invoicing"
msgstr ""
#: ../../content/applications/sales/sales/products_prices/returns.rst:44
msgid "Sometimes, customers return an item after they receive and/or pay for their invoice. In these cases, a return using only *Reverse Transfers* is impossible since validated or sent invoices cannot be changed. However, *Reverse Transfers* can be used in conjunction with *Credit Notes* to complete the customer's return."
msgstr ""
#: ../../content/applications/sales/sales/products_prices/returns.rst:49
msgid "To start a return, navigate to the relevant sales order. If there is a payment registered on the sales order, then the payment details will appear in the Chatter, and the invoice (accessible through the :guilabel:`Invoices` smart button) will have a green banner across it."
msgstr ""
#: ../../content/applications/sales/sales/products_prices/returns.rst:53
msgid "From the sales order, click on the :guilabel:`Delivery` smart button to view the validated delivery order. Then, click :guilabel:`Return` to open the :guilabel:`Reverse Transfer` pop-up window. Next, edit the :guilabel:`Product` or :guilabel:`Quantity` as needed for the return, and then click :guilabel:`Return`. This generates a new warehouse operation for the incoming returned product(s), which is validated by the warehouse team once the return is received. Then, on the sales order, the :guilabel:`Delivered` quantity will reflect the difference between the initial validated quantities and the returned quantities."
msgstr ""
#: ../../content/applications/sales/sales/products_prices/returns.rst:61
msgid "Since the returned products have already been paid for, the validated invoice must be modified to reflect the return. Navigate to the relevant invoice (from the sales order, click on the :guilabel:`Invoices` smart button). Then, click on the :guilabel:`i` icon next to the :guilabel:`Paid` line at the bottom of the invoice to open the :guilabel:`Payment Info` window. Next, click :guilabel:`Unreconcile`."
msgstr ""
#: ../../content/applications/sales/sales/products_prices/returns.rst:None
msgid "The \"Unreconcile\" button."
msgstr ""
#: ../../content/applications/sales/sales/products_prices/returns.rst:71
msgid "After the invoice is unreconciled, the options for :guilabel:`Send & Print` and :guilabel:`Register Payment` become available again alongside a note that there are outstanding payments for the customer."
msgstr ""
#: ../../content/applications/sales/sales/products_prices/returns.rst:75
msgid "To process a refund, click :guilabel:`Add Credit Note` from the validated invoice."
msgstr ""
#: ../../content/applications/sales/sales/products_prices/returns.rst:None
msgid "The \"Credit Note\" pop-up window, to issue a credit to the customer after invoicing."
msgstr ""
#: ../../content/applications/sales/sales/products_prices/returns.rst:81
msgid "Choose whether to issue a :guilabel:`Partial Refund`, :guilabel:`Full Refund`, or :guilabel:`Full refund and new draft invoice`. The :guilabel:`Partial Refund` option creates a draft credit note that can be edited before posting. The :guilabel:`Full refund and new draft invoice` option validates the credit note and duplicates the original invoice as a new draft."
msgstr ""
#: ../../content/applications/sales/sales/products_prices/returns.rst:86
msgid "A :guilabel:`Reason` for the credit and a :guilabel:`Specific Journal` to use to process the credit can also be specified. If a :guilabel:`Specific Reversal Date` is selected, then a :guilabel:`Refund Date` must also be selected."
msgstr ""
#: ../../content/applications/sales/sales/products_prices/returns.rst:90
msgid "After the information is filled, click :guilabel:`Reverse`. Then, for a :guilabel:`Partial Refund` or :guilabel:`Full refund and new draft invoice`, :guilabel:`Edit` the draft as needed, and finally, click :guilabel:`Confirm`."
msgstr ""
#: ../../content/applications/sales/sales/products_prices/returns.rst:None
msgid "The \"outstanding payments\" banner."
msgstr ""
#: ../../content/applications/sales/sales/products_prices/taxes.rst:5
msgid "Set taxes"
msgstr ""

View File

@ -8,7 +8,7 @@ msgid ""
msgstr ""
"Project-Id-Version: Odoo 16.0\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2022-11-17 09:28+0000\n"
"POT-Creation-Date: 2022-12-23 09:13+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"
@ -1833,7 +1833,7 @@ msgid "robots.txt"
msgstr ""
#: ../../content/applications/websites/website/optimize/seo.rst:623
msgid "When indexing your website, search engines take a first look at the general indexing rules of the a``/robots.txt`` file (allowed robots, sitemap path, etc.). Odoo automatically creates it. Its content is:"
msgid "When indexing your website, search engines take a first look at the general indexing rules of the ``/robots.txt`` file (allowed robots, sitemap path, etc.). Odoo automatically creates it. Its content is:"
msgstr ""
#: ../../content/applications/websites/website/optimize/seo.rst:627